Doris on es 聚合下推

Proposed changes
support pushdown aggregate operator to ES
https://github.com/apache/incubator-doris/issues/6989
Types of changes
What types of changes does your code introduce to Doris?
Put an x in the boxes that apply

[ ] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation Update (if none of the other choices apply)
[ ] Code refactor (Modify the code structure, format the code, etc...)
[x] Optimization. Including functional usability improvements and performance improvements.
[ ] Dependency. Such as changes related to third-party components.
[ ] Other.

Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

[x] I have created an issue on (Fix #ISSUE) and described the bug/feature there in detail
[x] Compiling and unit tests pass locally with my changes
[x] I have added tests that prove my fix is effective or that my feature works
[ ] If these changes need document changes, I have updated the document
[ ] Any dependent changes have been merged

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

@Userwhite As discussed in our online meeting，we should move the predicate-transform from BE (backends) to FE (frontends) which would contribute significant  effect  for subsequent planning and extension. We will continue to pay more attention  and participate in this PR

OK, I know it. I will deal with it recently. Now nothing has done because I am busy in the last and this week😂

@Userwhite As discussed in our online meeting，we should move the predicate-transform from BE (backends) to FE (frontends) which would contribute significant effect for subsequent planning and extension. We will continue to pay more attention and participation in this PR

OK, I know it. I will deal with it recently. Now nothing has done because I am busy in the last and this week😂

Recently, I want to do the generate DSL up to FE, and I also want to support aggregation push down. Can we communicate on wechat? my wechat is<PHONE_NUMBER>9. @Userwhite

This PR has not been updated for a long time.
There could be many reasons.
If it's caused by there are no maintainers to push or ignore this PR, I'm sorry.
If you contact maintainer or want to continue this PR, feel free to @me or @other maintainers.


chore: refactor readme

Summary
This PR refactors a bit the README.md of the npm package:

it adds installation and usage examples
it moves the documentation paragraph up
it moves the traits of Biome after the documentation:

I removed the part about other tools
I added a trait about not needing Node.js to function

Test Plan
Proof read

What about a link to the playground?

What about a link to the playground?

I don't know how to present it and where. Any suggestion?


alternative prioritization rules in RankIpAddress

Trying a different ranking algorithm, to give a large boost to addresses that are associated with the same NIC as the default router, and eliminate some other special-case tests for 172.30., 192.168.1., etc. Related to SimpleTCP issue #14 as tracked on GItHub.

Inviting comment, any changes / refinements needed? Treat as a starting point if you wish, and change as you see fit. Meanwhile I am not using SimpleTCP in our present implementation, but it does look like a good piece of code and I'm glad to contribute to it whether or not you merge this.

Hey! Sorry, fully intend to merge this - just need to run it on a couple of our in-use apps to make sure it doesn't break the obvious use cases, will try to do that in the next couple days.

I noticed I had neglected to include a fix for @BrandonPotter's final remark on the related issue #14, with a potential uncaught exception. I added that to my branch now, but I'm not sure if it will show up here, and I already merged the PR so... I can open a second PR and attach to the same issue, I guess?


[FLINK-36741][cdc][transform] Fix the precision of decimal has been lost when use transform

The precision and scale of Decimal has been lost when use FlinkCDC transform to project express or alias.
The fields of this table are as follows:

Column Name
Data Type

id
int

name
string

age
int

address
string

deposit
decimal(10,2)

weight
double

height
double

The projection rule of this pipeline are as follows:
projection: id, upper(name) as name, age + 1 as newage, deposit as deposits, weight / (height * height) as bmi

The parsed data types are as follows:

Column Name
Data Type

id
int

name
string

newage
int

deposits
decimal(19,0)

bmi
double

The expected data type of deposits should be decimal(10,2).
I have fixed it, and I will pull request.

I remember that similar things happen to VARCHAR (and other types with variable precisions). Any chance this PR has fixed these cases, too?

Add convertCalciteRelDataType in DataTypeConverter.
Modify testGenerateProjectionColumns in TransformParserTest to verify the repair.
This PR fixed all data type which has precision or length.

@yuxiqian @leonardBang @lvyanquan PTAL

Resolved conflicts. CC @yuxiqian

Could @aiwenmo also summarise what issue does this PR fixes, by changing PR title and description? Obviously this fixes more than just DecimalType precision issue, and most part of description is irrelevant.

1.Add convertCalciteRelDataType in DataTypeConverter.
2.Add the convert of precision in DataTypeConverter.convertCalciteType.
3.Use DecimalData instead of BigDecimal in YAML task.
4.Optimize the strategy of SqlToRelConverter.
5.Fix the precision and length of data type has been lost in TransformTable.getRowType.
6.Modify testGenerateProjectionColumns in TransformParserTest to verify the repair.
7.Add testComplicatedUdfReturnTypes to verify the repair when using udf.


_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+0 :ok:
shelldocs
0m  0s
Shelldocs was not available.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

_ branch-2 Compile Tests _

+0 :ok:
mvndep
0m 15s
Maven dependency ordering for branch

_ Patch Compile Tests _

+0 :ok:
mvndep
0m  6s
Maven dependency ordering for patch

+1 :green_heart:
shellcheck
0m  0s
There were no new shellcheck issues.

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

_ Other Tests _

+0 :ok:
asflicense
0m  1s
ASF License check generated no output?

8m 31s

Subsystem
Report/Notes

Docker
ClientAPI=1.40 ServerAPI=1.40 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2597/1/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/2597

Optional Tests
dupname asflicense shellcheck shelldocs

uname
Linux a73b757cfcd2 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:41:39 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / 69f282e21a

Max. process+thread count
41 (vs. ulimit of 12500)

modules
C:  U:

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2597/1/console

versions
git=2.17.1 maven=3.6.3 shellcheck=0.4.6

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.


New version Helper

When the new version is approximately released?

Hi @resand,
I will try to do my best to release the new version by the end of May 😄

😮 Excellent! Thank you for your master work

You're welcome! I'm glad you like CoreDataHelper 😀


riscv64: Implement SIMD shifts, v{all,any}_true and vhigh_bits

👋 Hey,
This PR implements lowerings for SIMD shifts, and a few boolean operations ( v{all,any}_true/vhigh_bits).
The implementation for shifts is fairly straightforward, but the boolean operations don't have a equivalent instruction, so we need to do some different operations.

This is somewhat weird, I ran it a few times yesterday and it always got canceled. I tested today in my own branch, and it worked, and I just reran CI here and it worked again.
I also tested running the CI tests on my machine and it only used ~500MB, so I'm not entirely sure what is going on. I thought we didn't run any pooling tests on CI due to QEMU issues?
I'm going to tentatively merge this and if it causes issues again, we should revert it and look at it again.


Remove deprecated dependency @types/rdf-js

npm WARN deprecated<EMAIL_ADDRESS>This is a stub types definition. rdf-js provides its own type definitions, so you do not need this installed.

Thank you for opening this issue. Wha a coincidence that less than an hour prior #34 was opened to fix that.
About the warning; it is harmless, generated when a package is removed from DefinitelyTyped in favour of externally managed declarations. We moved to @rdfjs/types) but all packages continue to work to keep backwards compatibility

Should be fixed #38


.m4a File Format Not Supported for Playback

Does not support .m4a audio file playback, resulting in errors or undefined behavior when attempting to load and play files with this format. This issue impacts users who rely on .m4a files for audio content and prefer not to convert them due to timing inconsistencies that conversions often introduce.
Request: Please add support for .m4a format to ensure seamless playback. .m4a is widely used, and native support on both iOS and Android should make this addition feasible.
@dcvz

fill in the issue template


Allow user to choose whether or not the parent view controller should be scaled

This is a fantastic library, but for my case, I didn't want the fromVC (Parent View Controller) to scale because it looked awkward given my situation. The following code is completely backwards compatible, so anyone gets these changes won't see their code break.
I contemplated whether I should simply ask the user if they want the parent view controller to be scaled or if I should allow them to pass in a CGFloat which defines the scale (by default, you choose 0.85, but the user would be able to choose 1, 0.90, 0.50, etc.). I decided to go against that because while it is simple to introduce, I'd like to think the library as it stands is pretty awesome :).

This does not seem to be needed anymore since setting pushBackScale to 1 has the same effect.


musl: 1.2.2 -> 1.2.3

Description of changes
https://www.openwall.com/lists/musl/2022/04/07/1
cc @NixOS/static
Previous upgrade: #117375
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

cc @TredwellGit @thoughtpolice from mentions on previous updates, in case interested.

https://git.musl-libc.org/cgit/musl/tree/WHATSNEW?h=v1.2.3#n2293 for changes.
Notably adds some functions that are sometimes needed to be patched around previously: qsort_r, and to a lesser extent, pthread_getname_np.
On phone so not sure trust the results, but searching tree for mentions/patches for these only turns up some Darwin issues?
Anyway not sure the testing plan?
I know folks care about static builds in general and specifically Haskell.  I used to throw this at my hydra+builders for these upgrades but don't have that infra presently and not sure warrants such a use of our NixOS builders re:hydra job there.  Is very useful to see fallout before/after building all the things, and testing pkgsMusl as well as pkgsStatic.
@ofborg build pkgsMusl.gdb pkgsMusl.valgrind

aarch64-linux build failed on ofborg https://logs.nix.ci/?key=nixos/nixpkgs.168207&attempt_id=6e85695e-ba6d-452f-b741-5947598267a1

Haskell in pkgsMusl and pkgsStatic seems to work as expected on x86_64-linux at least.

Haskell in pkgsMusl and pkgsStatic seems to work as expected on x86_64-linux at least.

Can confirm: I built a bunch of complex Haskell programs using pkgsStatic.

aarch64-linux build failed on ofborg https://logs.nix.ci/?key=nixos/nixpkgs.168207&attempt_id=6e85695e-ba6d-452f-b741-5947598267a1

This seems to be unrelated to this patch — I can reproduce it on the parent commit.

That particular failure was introduced in https://github.com/NixOS/nixpkgs/pull/149482.  But pkgsMusl.stdenv hasn't worked at all on aarch64-linux since https://github.com/NixOS/nixpkgs/pull/57339.

Thanks all! :+1:


use extract expected assertions errors in jasmine

https://github.com/facebook/jest/pull/3843

Codecov Report

Merging #3875 into master will increase coverage by 0.09%.
The diff coverage is 8.33%.

@@            Coverage Diff             @@
##           master    #3875      +/-   ##
==========================================
+ Coverage   57.58%   57.67%   +0.09%
==========================================
  Files         195      195
  Lines        6792     6781      -11
  Branches        6        6
==========================================
  Hits         3911     3911
+ Misses       2878     2867      -11
  Partials        3        3

Impacted Files
Coverage Δ

.../src/legacy_code_todo_rewrite/jest-adapter-init.js
0% <0%> (ø)
:arrow_up:

packages/jest-jasmine2/src/setup-jest-globals.js
0% <0%> (ø)
:arrow_up:

...st-matchers/src/extractExpectedAssertionsErrors.js
13.33% <0%> (ø)
:arrow_up:

packages/jest-jasmine2/src/queueRunner.js
100% <100%> (ø)
:arrow_up:

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 8b224cf...fce3a30. Read the comment docs.


Switching to managed code version of functionsnethost

Pulling in changes from feature branch to main.
The PR branch was created from the feature branch and then rebased on top of main. Only conflicts were the in the DotnetWorker.csproj and DotnetWorker.Grpc.csproj, I took the feature branch version during rebase. Updated these 2 files later to reflect the new version numbers we want.
I may create another PR just to adjust the version numbers of the packages when we are ready to release.

I may create another PR just to adjust the version numbers of the packages when we are ready to release.

Rebased on main again this morning.


1.0.0-rc.1 Progress bar can't have a percentage based size

I used to be able to set a percentage based size for a CircularProgress component. This allowed me to create a screen that was mostly a CircularProgress for my /callback page. It still works but the CircularProgress spins around a point near the top of its component not the center.

[x] I have searched the issues of this repository and believe that this is not a duplicate.

This is what I was doing and no longer works. If there is a better way to do this please let me know.
  <CircularProgress size="50%" color="secondary"/>

Your Environment

Tech
Version

Material-UI
1.0.0-rc.1

React
16.3.2

UPDATE: This is working in some places in my code but not others, so it is probably just me. Will investigate and close this issue if I am right.

The issue was using the CircularProgress by percentage within a Grid component. I have removed the Grid and am just rendering the CircularProgress and it now works.


Revendor<EMAIL_ADDRESS>and add restore and migrate operations

What this PR does / why we need it:
Vendor gardener version 1.6.0 and add and implement restore and migrate operations to the actuator.
Which issue(s) this PR fixes:
Part of #1631
Special notes for your reviewer:
None
Release note:

Vendored gardener v1.6.0.
Added implementation for `Restore` and `Migrate` operations.

/lgtm should we change this to a normal PR then?

Want to test out the entire migration just in case, but I'll do it a bit later today if that's ok.

Please take your time.


Add LightsOut-Fwiffo

Closes #4620

Using rawgit works but the author will need to update the netkan after every release.
@rkagerer wouldn't it be better if you use the releases page.

He wants to just have a single repository.

Confirmed, I am fine updating netkan after each release.  Now that I'm starting to get a better understanding of how netkan/ckan works, perhaps at some point in the future I'll get things set up more traditionally, but this is fine for now.  Appreciate your help.

Ok then, merging with my thanks


Allow multiple credentials secrets in single namespace

Summary
This PR allows the usage of mutiple build secrets per SCM type, host or repository.
It supports the ssh-auth and basic-auth type secrets.
Secrets must have the appstudio.redhat.com/credentials: scm and appstudio.redhat.com/scm.host labels, as well as might have an optional appstudio.redhat.com/scm.repository annotation value.
The best suitable one is selected, if none match then fallback is GitHub APP secret in the global namespace.
Known limitations:

GitHub dropped the login + password auth, seems only tokens are possible for now;
SSH key login isn't supported by any client, will need to find the way to perform authentication using it.

Issue to Fix
https://issues.redhat.com/browse/SVPI-745
How to test
Prerequisites:

GitHub organization
PAT with repo, user, org permissions;
Quay organization and repository with OAuth app enabled, known OAuth token for it.
Build-service fork and custom image. (typically, mshaposh/build-controller:latest is what in th PR)
Openshift cluster

Installation

Get the latest version of infra-deployments

Create hack/preview.env from template.
Set the necessary fields:
// local name of the fork fremote
export MY_GIT_FORK_REMOTE=mshaposh
...
// GH org and token
export MY_GITHUB_ORG=mshaposhnik-org
export MY_GITHUB_TOKEN=ghp_psj......
...
// Quay org and token
export IMAGE_CONTROLLER_QUAY_ORG=uy7c
export IMAGE_CONTROLLER_QUAY_TOKEN=J8cM177j6......
...
// Build service image and tag
export BUILD_SERVICE_IMAGE_REPO=mshaposh/build-controller
export BUILD_SERVICE_IMAGE_TAG=latest

Make sure oc is logged into a cluster, run from the infra-deployment project root:
./hack/bootstrap-cluster.sh preview --keycloak --toolchain
Make sure no fundamental errors during installlation.

Testing

Create application from minimal template:

oc create -f - << EOF
apiVersion: appstudio.redhat.com/v1alpha1
kind: Application
metadata:
annotations:
name: go-application-sample
namespace: default
spec:
appModelRepository:
  url: ''
displayName: go-application-sample
gitOpsRepository:
  url: ''
EOF

Wait it for resolve (must have status similar to this:)
 conditions:
    - lastTransitionTime: '2024-02-15T11:56:37Z'
      message: Application has been successfully created
      reason: OK
      status: 'True'
      type: Created
  devfile: |
    metadata:
      attributes:
        appModelRepository.context: /
        appModelRepository.url: https://github.com/mshaposhnik-org/go-application-sample-N6juw-marry-sign
        gitOpsRepository.context: ./
        gitOpsRepository.url: https://github.com/mshaposhnik-org/go-application-sample-N6juw-marry-sign
      name: go-application-sample
    schemaVersion: 2.2.0

Create the SCM secret  (set or omit the repository annotation) :

apiVersion: v1
kind: Secret
metadata:
  namespace: default
  name: test-scm-secret
  labels:
    appstudio.redhat.com/credentials: scm
    appstudio.redhat.com/scm.host: github.com
  annotations:
    appstudio.redhat.com/scm.repository: mshaposhnik/*
type: kubernetes.io/basic-auth
stringData:
  password: Z2hw....
EOF

Create component:

oc create -f - << EOF
apiVersion: appstudio.redhat.com/v1alpha1
kind: Component
metadata:
  name: go-component-sample
  namespace: default
  annotations:
    build.appstudio.openshift.io/request: "configure-pac"
    image.redhat.com/generate: '{"visibility": "public"}'
spec:
  componentName: go-sample-component-name
  application: go-application-sample
  source:
    git:
      url: https://github.com/mshaposhnik/devfile-sample-go-basic.git
EOF

It must resolve status:
status:
  conditions:
    - lastTransitionTime: '2024-02-15T12:36:44Z'
      message: GitOps resource generated successfully
      reason: OK
      status: 'True'
      type: GitOpsResourcesGenerated
    - lastTransitionTime: '2024-02-15T12:36:44Z'
      message: Component has been successfully created
      reason: OK
      status: 'True'
      type: Created

PR to repository must be submitted.

/retest

/retest

/test build-service-e2e

/retest

/retest

/test build-service-e2e


version=unknown

I've tried adding miniver here: https://github.com/instagrambot/instabot/pull/578/files
basnijholt-macbook ➜  instabot git:(version)  pip install .
Processing /Users/basnijholt/Downloads/instabot
Installing collected packages: instabot
  Running setup.py install for instabot ... done
Successfully installed instabot-unknown
basnijholt-macbook ➜  instabot git:(version)  python -c 'import instabot; print(instabot.__version__)'
unknown

Do you have any idea why it doesn't work?

I fixed it by doing this.
I've opened #7 to implement the same change here.

Thanks for the report!.
Not sure why this doesn't work; I will look into it.

I understand now. miniver uses annotated tags to determine the version from git, however instabot uses unannotated tags.
The difference is essentially that annotated tags store metadata like the person who created it, time of creation etc., whereas unannotated tags do not.
AFAIK the recommended way to tag versions is using annotated tags. I often use unannotated tags to mark work in progress stuff, or to easily move around in the git history, and using these shouldn't affect the version....

the --tags flag will get git describe to use unannotated tags to determine a description.

Here's a stack overflow question that discusses this.
I'm pretty convinced that using annotated tags is the Right Way, however even large projects like scikit-learn had this problem during their development, and such projects should still be able to profit from miniver.

I think in the end we shouldn't allow unannotated tags to denote versions.
Miniver is an opinionated tool. If someone's project really wants to use unannotated tags for their versions, then they should modify the source. I can add a section to the README and a patch that can be applied to allow unannotated tags.


Point cloud compensate in empty area

Describe the bug
Points are filled in the empty area which is a disturbance in some high-accuracy applications.
To Reproduce
Expected behavior
Add a 'high accuracy' parameter or related ways to turn off the compensate feature.
Logs
Screenshots

In the situation up, the points between the arm should not exist

Also in this situation, the left side of box is empty but filled with points by sdk
Desktop (please complete the following information):

OS with Version: Ubuntu 18.04
SDK Version:  1.4.1
Firmware version: rgb: 1.6.102, depth: 1.6.75

Additional context

Hi @qm13,
Why the issue is closed? Is there any comments/solution for this?

@fi6 Does the issue solved?


Deprecation warnings using mock_dynamodb2 with python 3.8.2

Behaviour
When I use mock_dynamodb2 with python 3.8.2 I get deprecation warnings.
Versions
$ pipenv run pip freeze | grep -E 'moto|boto'
boto==2.49.0
boto3==1.13.5
botocore==1.16.5
moto==1.3.14
$ pipenv run python -V
Python 3.8.2

Moto was installed using Pipenv
Example
Given the following pytest file...
import os
import pytest
import boto3
from moto import mock_dynamodb2

os.environ['AWS_ACCESS_KEY_ID'] = 'testing'
os.environ['AWS_SECRET_ACCESS_KEY'] = 'testing'
os.environ['AWS_SECURITY_TOKEN'] = 'testing'
os.environ['AWS_SESSION_TOKEN'] = 'testing'

@pytest.fixture
def ddb(scope='function'):
    with mock_dynamodb2():
        return boto3.client('dynamodb',
                            region_name='eu-west-1',
                            aws_access_key_id='testing',
                            aws_secret_access_key='testing',
                            aws_session_token='testing')

@mock_dynamodb2
def test_listing_tables(ddb):
    # table_name = 'temp-{}'.format(str(uuid4()))
    ddb.create_table(
        AttributeDefinitions=[
            {
                'AttributeName': 'Artist',
                'AttributeType': 'S',
            },
            {
                'AttributeName': 'SongTitle',
                'AttributeType': 'S',
            }
        ],
        KeySchema=[
            {
                'AttributeName': 'Artist',
                'KeyType': 'HASH',
            },
            {
                'AttributeName': 'SongTitle',
                'KeyType': 'RANGE',
            }
        ],
        ProvisionedThroughput={
            'ReadCapacityUnits': 5,
            'WriteCapacityUnits': 5,
        },
        TableName='Music',
    )
    assert ddb.list_tables()['TableNames'] == ['Music']

Deprecation warnings when I run pytest
$ pipenv run pytest
======================================================================================= test session starts =======================================================================================
platform darwin -- Python 3.8.2, pytest-5.4.1, py-1.8.1, pluggy-0.13.1
rootdir: /Users/adrian/code/mowat27/learn/aws/ddbmock, inifile: pytest.ini
collected 1 item

test/test_put_and_scan.py .                                                                                [100%]

======================================================================================== warnings summary =========================================================================================
/Users/adrian/.local/share/virtualenvs/ddbmock-o4qurhhV/lib/python3.8/site-packages/boto/plugin.py:40
  /Users/adrian/.local/share/virtualenvs/ddbmock-o4qurhhV/lib/python3.8/site-packages/boto/plugin.py:40: DeprecationWarning: the imp module is deprecated in favour of importlib; see the module's documentation for alternative uses
    import imp

/Users/adrian/.local/share/virtualenvs/ddbmock-o4qurhhV/lib/python3.8/site-packages/moto/cloudformation/parsing.py:407
  /Users/adrian/.local/share/virtualenvs/ddbmock-o4qurhhV/lib/python3.8/site-packages/moto/cloudformation/parsing.py:407: DeprecationWarning: Using or importing the ABCs from 'collections' instead of from 'collections.abc' is deprecated since Python 3.3, and in 3.9 it will stop working
    class ResourceMap(collections.Mapping):

-- Docs: https://docs.pytest.org/en/latest/warnings.html
================================================================================== 1 passed, 2 warnings in 2.86s ==================================================================================

Expected behaviour
No warnings
This is annoying but not critical at the moment.  I'd like to keep my project up to date with future python releases though.
Related issues
A search for DeprecationWarning in open issues yielded no results.  Sorry if I missed something.

If anyone else is having this problem, note that you can work around this by changing the imports in your test suite to supress the warnings
import warnings

with warnings.catch_warnings():
     warnings.filterwarnings("ignore", category=DeprecationWarning)
     import boto3
     from moto import mock_dynamodb2

or by using pytest.ini
[pytest]
filterwarnings =
    ignore::DeprecationWarning:moto.*:
    ignore::DeprecationWarning:boto.*:

Thanks for raising this, and for providing a workaround, @mowat27. Marking this as an enhancement.

Hi @bblommers, it looks like the issue was already fixed on the master  #2624
Maybe it is time for a new release again?

This should now be fixed as of moto >= 1.3.16.

I am using moto v1.3.16, installed with pipenv, and this warning still appears. In my case I'm using mock_s3.
  /usr/local/lib/python3.8/site-packages/boto/plugin.py:40: DeprecationWarning: the imp module is deprecated in favour of importlib; see the module's documentation for alternative uses
    import imp

-- Docs: https://docs.pytest.org/en/stable/warnings.html


Add free Ghidra course from Hackaday

Hackday and I have put together a free Ghidra course which can be seen here:

https://hackaday.io/course/172292-introduction-to-reverse-engineering-with-ghidra
Github Repo
Youtube Playlist

This may be worth adding to the list, let me know if you have any questions!

Hey wrongbaud,
first of all thank you for putting together this free course :-). I think that looks like a nice addition to the list.

I think the course contents are neat for beginners, and I do like the focus on Ghidra in general. However, I have to say that I don't see it being a good fit to an awesome list that purely focuses on embedded/IoT with the course being x86 exclusive.


Remove azure-cosmos-spark_3_2-12 from parent pom identifiers

@alzimmermsft and I chatted and com.azure.cosmos.spark:azure-cosmos-spark_3_2-12 needs to be kept in the valid_parents, since it's being used as a parent to the other spark libraries and removing it from the parent_pom_identifiers is the right call. Things in parent_pom_identifiers won't get scanned for dependencies which is the problem that we're running into. Cosmos added com.azure:azure-cosmos-test as a dependency for com.azure.cosmos.spark:azure-cosmos-spark_3_2-12 and because this was in the parent_pom_identifiers, it wasn't getting scanned and added to the from source pom.
We believe this change to be safe and, for testing, I'm going to run the CI pipelines for

Core - pass
Cosmos - The build job test matrix passes. I won't be waiting for the emulator runs to finish, they don't matter for this change.
ResourceManager - pass
Spring - pass
Template - pass
AppConfiguration - pass

which should hopefully ferret out any issues that might exist.

I'm merging without waiting for requirements. Nothing runs automatically with these changes and I've linked the CI runs I ran against this PR, and their results, in the description. Also, @alzimmermsft approved the changes and he's the only other one that knows this file.


loss['coor_loss']无法反向传播

您好，在我按照您的步骤训练时出现了如下错误：
RuntimeError: one of the variables needed for gradient computation has been modified by an inplace operation: [torch.cuda.FloatTensor [1, 32, 1]], which is output 0 of IndexPutBackward, is at version 2; expected version 1 instead. Hint: enable anomaly detection to find the operation that failed to compute its gradient, with torch.autograd.set_detect_anomaly(True).
当我去掉
loss['coor_loss'].mean()*coor_weight
这句代码时就可以正常训练了，请问这是什么原因呢

i also have the problem, and i do this as you say. now it works.  But i am stll trobuled by this problem. i have no idea about it.
The error i encountered can be seen in the picture below.


[Cognitive - Form Recognizer] REST API Review - v3.0-preview.3

Change Scope
This section will help us focus on the specific parts of your API that are new or have been modified. Please share a link to the design document for the new APIs, a link to the previous Open API document (swagger) if applicable, and the root paths that have been updated.

Design Document: See https://github.com/Azure/azure-rest-api-specs-pr/pull/6302 for internal discussions.
Previous Open API Doc: https://github.com/Azure/azure-rest-api-specs/blob/main/specification/cognitiveservices/data-plane/FormRecognizer/preview/2022-01-30-preview/FormRecognizer.json
Updated paths: None
Detailed changes

[Breaking Change] Renamed boundingBox to polygon to support non-quadrilateral polygon regions.
[Breaking Change] Removed entity recognition.
[Breaking Change] Changed some properties to optional to support analyzing documents without rendering or field extraction.
[Bug Fix] Renamed DocumentLanguage.languageCode to locale to reflect actual service behavior.
Add support for HEIF image format.
Add support for docx/xlsx/pptx/html file formats for prebuilt-read without bounding boxes.
Add paragraph detection, with role classification for prebuilt-{layout,document}.
Add support for table caption/footnotes.
Add support for parsed address fields.

API Stewardship Review: 8-Jun-22
The majority of this review was done on PR #19301 and was reviewed and approved by @johanste and @markweitzel


feat: Linux build doc

Please add a linux build step-by-step :+1:

This project is abandoned. It hasn't been updated in a year.


pdf2svg: migrate back to core

Turns out pdf2svg no longer depends on GTK+ or X11 (and previously did this only by mistake).
See also the related PR Homebrew/homebrew#41065.

Thanks for the migration. I estimate that currently about one-third of the formulas in homebrew-x11 doesn't belong there given that neither gtk+ nor gtk+3 depends on x11...

I agree, that seems quite likely. I'm only migrating this one because that's the only one I use from homebrew-x11 and because I was encouraged to do so in Homebrew/homebrew-x11#96. :smiley_cat:

Thanks for the pull request! 🎉 Homebrew depends on contributions from community members like you and we're grateful for your support.


Daniil: Watch xeotek.com

Daniil requests the watch of the watch_keyword xeotek\.com. See the MS search here and the Stack Exchange search here.

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

Later added affiliation and mod edited; so this shouldn't be watched IMO.


Constructor.java:42-45: Continue enable 'spring-fat'...

The puzzle 329-93a273ea from #329 has to be resolved:
https://github.com/objectionary/opeo-maven-plugin/blob/c2af3985f231c712e8b53ede8b6e102a3747c6d4/src/main/java/org/eolang/opeo/ast/Constructor.java#L42-L45
The puzzle was created by @volodya-lombrozo on 12-Jul-24.
Estimate: 90 minutes,  role: DEV.
If you have any technical questions, don't ask me, submit new tickets instead. The task will be "done" when the problem is fixed and the text of the puzzle is removed from the source code. Here is more about PDD and about me.

@0pdd the puzzle #361 is still not solved.

@0pdd 2 puzzles #361, #363 are still not solved.

@0pdd 3 puzzles #361, #363, #366 are still not solved.

@rultor release, tag is 0.3.1, title is Version 0.3.1.

@rultor release, tag is 0.3.1, title is Version 0.3.1.

@volodya-lombrozo OK, I will release it now. Please check the progress here

@rultor release, tag is 0.3.1, title is Version 0.3.1.

@volodya-lombrozo Done! FYI, the full log is here (took me 10min)


vendor/Expectation.php autocompletion docblock generation has wrong typehint on default values

Hi @olivernybroe!
I've added a custom expectation in my laravel-expectations plugin, like this one
expect()->extend('toBeAbleTo', function (string $ability, $arguments): Expectation {...});

and it generates a correct docblock in vendor/Expectation.php
@method \Pest\Expectation toBeAbleTo(string $ability,  $arguments)
but, as toBeAbleTo maps also laravel's $user->can('ability', $model) and $user->can('ability') is should have this signature:
expect()->extend('toBeAbleTo', function (string $ability, array|mixed $arguments = []): Expectation {...});

because of pestphp requirements, I'm still (:cry:) bound to php7.3, so the best I can do is:
expect()->extend('toBeAbleTo', function (string $ability, $arguments = []): Expectation {...});

unfortunately this one generates a misleading dockblock:
@method \Pest\Expectation toBeAbleTo(string $ability, array $arguments = [])
it autocompletes like this:

and give this warning:

the best solution I can think of is to add a little docblock before the extend declaration:
/*
 * Assert that the given User is authorized to do something
 *
 * @param array|mixed $arguments
 */
expect()->extend('toBeAbleTo', function (string $ability, $arguments = []): Expectation {...});

but it is not parsed (still? :smile: )
Let me know if you need more info!
PhpStorm version: 2021.2.2
Pest Plugin version: 1.2.0

Hey @fabio-ivona,
The issue here is that your docblock has to be on your function, not on the function call 👍
So changing the code to the following works.
expect()->extend(
    'toBeAbleTo',
    /**
     * @param array|mixed $arguments
     */
    function (string $ability, $arguments = []): Expectation {
        return $this;
    }
);

TIL: docblock can be put inside a function 🤯

@fabio-ivona your docblock is invalid 😉
It needs two * for it to be a valid docblock 👍


[feat]: Auto Commenting feature for PR Raised

This feature aims to address the problem of delayed and inconsistent communication following the raising of PRs. By automatically commenting on PRs as soon as they are raised, it ensures that contributors receive immediate feedback and acknowledgment for their efforts. This fosters a positive and supportive environment for collaboration, encouraging continued participation and engagement from contributors.

@mdazfar2 please assign me this issue


Duplicating cells causes duplicate cell_ids in Jupyter Notebooks with nbformat >= 4.5

After editing some notebooks with VS Code Stable, including copy-and-paste (c and v keys) to duplicate some cells, I got errors from jupyter nbconvert saying:
[NbConvertApp] ERROR | Notebook JSON is invalid: Non-unique cell id '82f5d8f1' detected. Corrected to '96e5d841'.

I suspect that this is because https://github.com/microsoft/vscode/pull/134835 hasn't landed yet and I'm not using Insiders. But in a quick skim of the code for that PR, I'm not certain this case is handled.
I may have a chance to test on Insiders later to be able to confirm; for now this can be a placeholder for anyone else who encounters this issue.
Simple test case: create test.ipynb with:
{
 "cells": [
  {
   "cell_type": "markdown",
   "metadata": {},
   "source": [
    "Test notebook"
   ],
   "id": "1"
  }
 ],
 "metadata": {
  "language_info": {
   "name": "python"
  },
  "orig_nbformat": 4
 },
 "nbformat": 4,
 "nbformat_minor": 5
}

Open in VS Code, select the cell, press c (no modifiers) and then v. Save, and observe that both cells have "id": "1". This violates the spec, see the questions there.

This is no longer an issue,


backend_importWallet rpc call not worked

backend_importWallet not worked correctly
Added name & description fields
Related to #31

@dulanov Did we decide not to use JSON list for params?
re: https://github.com/ethereumproject/emerald-wallet/issues/66#issuecomment-302839999

@elaineo it's ok to use an object not wrapped in list according JSON RPC 2 specification, @r8d8 implemented it as is without problem.

@elaineo but conceptually better to use array, because often it is necessary to add additional parameters, such as the password: ..., "params":[{"from":"0x6a7cc99d37e28059306ce7f14ad99d671e7db6c0","to":"0xa7cb60a1014b4b8e3dc9fb22facfdf6edbf08109","gas":"0x021000","gasPrice":"0x02540be400","value":"0x1000000de0b6b3a7640000"}, "1234567890"], ...


Warnings logged on build that toolchain version is not supported

Am using ESP-IDF as of the date of this issue.  I got a warning that my toolchain was not supported.  Great that there is a check.  However, after installing the latest toolchain, I continue to get the same error.  Here is a text capture of what I am seeing:
$ xtensa-esp32-elf-gcc --version
xtensa-esp32-elf-gcc (crosstool-NG crosstool-ng-1.22.0-61-gab8375a) 5.2.0
Copyright (C) 2015 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

$ make
WARNING: Toolchain version is not supported:
Expected to see version: crosstool-NG crosstool-ng-1.22.0-61-gab8375a
Please check ESP-IDF setup instructions and update the toolchain, or proceed at your own risk.
/home/kolban/esp32/esptest/esp-idf/make/project.mk:445: WARNING: Compiler version is not supported:
Expected to see version(s): 5.2.0
Please check ESP-IDF setup instructions and update the toolchain, or proceed at your own risk.

As you can see, the execution of my xtensa-esp32-elf-gcc is producing the version that appears to be expected but yet the error is still logged.

You may want to check the output of the actual commands on your system since your output seems to show null for both items
https://github.com/espressif/esp-idf/blob/master/make/project.mk#L432

This is on Linux, yes? I remember Ubuntu, but which version?
Despite the warning, does the build run correctly? There is a bug that if the path to the toolchain needs to be set in menuconfig, it will print a warning like this before the path is configured. However it looks like the toolchain is already on your PATH, so it may be something else in this case.

@nkolban  do you only get this the first time you run 'make'?

This isn't working right for me either - and now I see why. I'm racing out the door but here's the fix:
TOOLCHAIN_COMMIT_DESC := $(shell $(CC) --version | sed -E -n 's|xtensa-esp32-elf-gcc.*\ \(([^)]*).*|\1|gp')
TOOLCHAIN_GCC_VER := $(shell $(CC) --version | sed -E -n 's|xtensa-esp32-elf-gcc.*\ \(.*\)\ (.*)|\1|gp')

Why? Because if you're using Windows executables it reports with .exe:
$ xtensa-esp32-elf-gcc --version
xtensa-esp32-elf-gcc.exe (crosstool-NG crosstool-ng-1.22.0-61-gab8375a) 5.2.0
Copyright (C) 2015 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Thanks @MartyMacGyver . We'll have a fix for Windows version detection out shortly.

@projectgus
The make appears clean ... i.e. it runs to complete.
If I then run make clean and make again, the warnings are still present.

OK, thanks @nkolban for the update. We have a fix for both these issues (warning on a clean build, warning on Windows) which will be merged shortly.

The fix should be one and the same.

They're not, but they're similar.

I have boiled it down to on linux
export CONFIG_TOOLPREFIX=$(pwd)/xtensa-esp32-elf/bin/xtensa-esp32-elf-
before I ran
make duktape_configure and
make
then it sorted it out for me.

Thanks for that extra detail @Frida854 .
There's a fix in the pipeline for this warning, which is two different underlying issues depending on platform:

Windows doesn't detect toolchain correctly
If the toolchain needs to be set in menuconfig before it works (ie not in PATH, or has a different prefix to the default prefix), then the warning appears on a clean build (until after "menuconfig" or "defconfig") has run.)


#getUnloadedWorlds() returning ALL worlds.

As I found out this evening (and as discussed on the dev IRC) Sponge.getServer().getUnloadedWorlds() returns the WorldProperties for all worlds regardless of whether they're actually unloaded or not.
As IRC user "blood|wrk" pointed out there seems to be a state check missing within the function .
I've created a code snippet too.

Also included in the snippet is that I think some stuff around these methods is rather confusing.

Worlds have an isLoaded function which suggests that a World could be unloaded regardless of whether it's been stored or just retrieved which is misleading since one can't retrieve unloaded World references. Just keep them from when they were loaded which I would consider bad coding style.
#getWorlds only returns loaded worlds while suggesting that it returns all worlds.
#getWorld returns Optional.empty() for unloaded worlds. (JD only implicitly states that !loaded equals not existing)
If this issue is fixed there's no (single) method of getting all worlds regardless of loading status.

I would recommend providing three methods for this: getLoadedWorlds(), getUnloadedWorlds() and getWorlds and I would also suggest either renaming isLoaded to isStillLoaded (or something like this) or allowing #getWorld to return unloaded Worlds aswell.
The whole latter part is of course just a recommendation or a wish to consider this opinion but I guess that there're developers out there who might think the same.

Just a reminder for others: This is not fixed in API 5 (MC 1.10.2)

https://github.com/SpongePowered/SpongeCommon/commit/79410aa688649c96d60507df7e190f5985906379
https://github.com/SpongePowered/SpongeCommon/commit/5b0e8eacadf1c3bccd5d2a7871c8a33cc17c7b88


Missing building and running instructions for ios & android

Information about how to compile & run this app in this repo is missing (in CONTRIBUTING.md or README.md files)
The Pull Request #38 contain build Instructions for IOS app.
I helped 2 people that had problems to build this project (IOS & Android)
https://github.com/MohGovIL/hamagen-react-native/issues/178
https://github.com/MohGovIL/hamagen-react-native/issues/139
Adding instructions will make it easier to start hacking on the project for new contributors.
it's also recommended to include minimum version requirement (or at least tested on) for Android Studio/Xcode

Is there a plan to update the README with build instructions?

Is there a plan to update the README with build instructions?
Yes, we plan to publish this soon.

@kaplanlior  would you mind merging #235  into this issue ? I already started a sample example for building over debian.

Hi @rr9845 @gkorland , see these instructions. I'll update CONTRIBUTING.md after your review/feedback.
Install steps
Create a development environment for React Native (follow this guide)
In short: Node, Java and Android development environment
Clone HaMagen code
git clone https://github.com/MohGovIL/hamagen-react-native.git
On Mac:
npm install  or yarn install
On Linux (see #244 ):
npm install --ignore-scripts or yarn install --ignore-scripts
Open the project in Android studio to install gradle dependencies or run ./android/gradlew
Create keystore.properties in android folder with the content:
HAMAGEN_DEBUG_KEYSTORE_PATH = ../path/to/debug.keystore
HAMAGEN_DEBUG_STORE_PASSWORD= debug store password
HAMAGEN_DEBUG_KEY_ALIAS= debug key alias
HAMAGEN_DEBUG_KEY_PASSWORD= debug key password

HAMAGEN_KEYSTORE_PATH = ../path/to/release.keystore
HAMAGEN_STORE_PASSWORD= release store password
HAMAGEN_KEY_ALIAS= release key alias
HAMAGEN_KEY_PASSWORD= release key password

Create debug.keystore key using this link or use this command:

keytool -genkey -v -keystore debug.keystore -alias [alias_name] -keyalg RSA -keysize 2048 -validity 10000

add android/app/src/main/res/values/secrets.xml with the content:
<?xml version="1.0" encoding="utf-8"?>
<resources>
    <string name="google_maps_api_key">GOOGLE_MAPS_API_KEY</string>
</resources>

(If you don't have a key, just change the placeholder to something else. It would only effect  the base map).

Run yarn android or npm run android and enjoy

@kaplanlior that is a good start , better then before and better(?) then nothing .
Assume the other person has no clue, has zero devops skills and just wish to build an apk and install on his phone / anbox to have fun.
There are a few  minor issues :
For instance I doubt that you really need android studio and that it is not enough to install the android [command line tools[(https://developer.android.com/studio#downloads) and then using the sdk manager to install the sdk
like that :
# download commandlinetools-linux-6609375_latest.zip to ~/
unzip -x commandlinetools-linux-6609375_latest.zip
tools/bin/sdkmanager --sdk_root=/home/$USER/android_root/ --install "build-tools;28.0.3"
export ANDROID_SDK_ROOT=/home/$USER/android_root/

in regards of react_native ,  based on the react link you used , one should be using snap to install node, but I belive it would be enough to install npm (sudo apt-get install npm)  and run npm install -f expo-cli (correct me if I'm wrong).
running npm install --ignore-scripts stil warn about peer issues - should they be manually installed via npm --save-dev depname ? should they be ignored ? etc.
keystore.properties  mention release.keystore, how is that file created (that should be answered in the md) ?
keystore.properties has paths , are they absolute ? are they relative ? should they be enclosed in quotation marks ? (that should be answered in the md)
You say run the script gradlew from android studio, why ? it's a shell script, why not run it from bash ?
Shouldn't there be some mentioning how rn-contact-tracing is being pulled for this project to build ?
It might be best to take a clean vm of Debian buster or whatever is your favorite distribution ,setup the envoirment and then document each step you did to make it work.  you might like to copy/paste what I already started for Debian in #235 for debian setup.
EOBE.  (Errors , Ommisions and bugs are expected here).

See comment https://github.com/MohGovIL/hamagen-react-native/issues/235#issuecomment-671762989
for some issues which apply to above instructions as well.
The secrets.xml step can be avoided completely by: #277
There more issues with above instructions, will update this comment later...
@rr9845 28 is target version (should be at least 29 by now...), not minimum version (minSdkVersion) which is 21.


Will be the new release?

Will be the new release?

The 2nd preview of the book was superseded by the 1st edition. Here's the page for the 1st edition of the book:
https://developer.xamarin.com/guides/xamarin-forms/creating-mobile-apps-xamarin-forms/
Here's the GitHub repo with the code for the 1st edition:
https://github.com/xamarin/xamarin-forms-book-samples
There are currently no plans for a 2nd edition. Instead, much information on Xamarin.Forms can be found on the website:
https://developer.xamarin.com/guides/#xamarin-forms


Beds mod

Recreate the Beds plugin using unified_inventory  and formspec

Mod in testing stage

Relates to #50

Beds mod part is finished, at least for now. It would be nice to come back later to clean up anything and maybe make it into a mod that extends mtg beds and allow people to easily install it with any compatible game without a hassle. Going to close this now though.


pull request for e2e test at 11/15/2016 07:26:13

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

optest/docs/updated_at.md
:white_check_mark:Succeeded

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


addFriend only works to accept friend requests but not send them.

Hello,
Im having some trouble using the addFriend method for sending friend requests. It just doesnt do anything. It does work for accepting pending invites, though.
Could anyone help me out?
Thanks

Turns out my account was limited. Sorry guys!


Bring up active web server in GCP

Various links:
https://console.cloud.google.com/home/dashboard?project=shelby-co-backend-prototype
https://shelby-co-backend-prototype.wm.r.appspot.com/books/CGaBFBWaiieGxTIwyDeZ
https://console.cloud.google.com/firestore/data/Book/CGaBFBWaiieGxTIwyDeZ?project=shelby-co-backend-prototype
https://cloud.google.com/nodejs/getting-started
https://shell.cloud.google.com/?show=ide%2Cterminal
Firestore in us-west3

PS C:\Users\chris\Documents\Github\shelby-co-employment-screener> npm start
npm ERR! Missing script: "start"
npm ERR!
npm ERR! Did you mean one of these?
npm ERR! npm star # Mark your favorite packages
npm ERR! npm stars # View packages marked as favorites
npm ERR!
npm ERR! To see a list of scripts, run:
npm ERR! npm run
npm ERR!  C:\Users\chris\AppData\Local\npm-cache_logs\2021-08-31T16_20_21_428Z-debug.log
PS C:\Users\chris\Documents\Github\shelby-co-employment-screener> node app.js
Example app listening at http://localhost:80

https://console.cloud.google.com/errors/CMa8lpKAjJPGaA?time=P1D&project=shelby-co-e-screener-dev

https://cloud.google.com/functions/docs/monitoring/logging
https://cloud.google.com/logging/docs/setup/nodejs
gcloud app deploy --verbosity=info


Dx nala tests

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

Project coverage is 84.31%. Comparing base (0e77f29) to head (0e87513).
Report is 4 commits behind head on stage.

Additional details and impacted files
@@           Coverage Diff           @@
##            stage      #56   +/-   ##
=======================================
  Coverage   84.31%   84.31%
=======================================
  Files          11       11
  Lines        2735     2735
=======================================
  Hits         2306     2306
  Misses        429      429

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


Remove version: taers232c.GAMADV-XTD3 version 6.70.02

[Automated] It returns code over 400 in all urls
Microsoft Reviewers: Open in CodeFlow

For moderators
This account is automated by Github Actions and the source code was created by CoolPlayLin. If you have any questions about any pull request, don't hesitate to ping Exorcism0666.

[!warning]
With the new version of Komac, numerous Pull Requests may contain bugs or unwanted elements. If such issues arise, please tag russellbanks so that these bugs can be addressed in future updates.

[!important]
Please carefully review these Pull Request before merging. If it is a Pull Request for removing incorrect content and the URLs are issue, free upon manual checking, please close this Pull Request directly. (It is best to inform Exorcism0666 of the closure.)

良い一日をお過ごしください！

URL: https://github.com/taers232c/GAMADV-XTD3/releases/download/V6.70.02/gamadv-xtd3-6.70.02-windows-x86_64.msi
Response status code does not indicate success: 404 (Not Found).
(Automated message - build 871)


Upgrade Blueprint Writer

Description
Resolves #19595

I revamped the Blueprint writer, addressing issues with the cycle numbers in the filenames, the writer putting the wrong path into root files, and other issues. I made the writer use relay::io::blueprint::save_mesh() to save data, and added options so that users can pass options to that function through the writer. I also did lots of code cleanup and simplification. I added (commented) future support for yaml and json outputs when a conduit bug is addressed.

Type of change

[x] Bug fix~~
[x] New feature~~
[ ] Documentation update
[ ] Other

How Has This Been Tested?

Built and ran on rzhound toss4. Added new tests. All old and new tests pass.
Reminders:

Please follow the style guidelines of this project.
Please perform a self-review of your code before submitting a PR and asking others to review it.
Please assign reviewers (see VisIt's PR procedures for more information).

Checklist:

[x] I have commented my code where applicable.~~
[x] I have updated the release notes.~~
[ ] I have made corresponding changes to the documentation.
[ ] I have added debugging support to my changes.
[x] I have added tests that prove my fix is effective or that my feature works.~~
[x] I have confirmed new and existing unit tests pass locally with my changes.~~
[x] I have added new baselines for any new tests to the repo.~~
[ ] I have NOT made any changes to protocol or public interfaces in an RC branch.~~

Does this break protocol? There might be a tool somewhere that helps us test this.

I think you want dump_protocol in src/tools/dev. Run it I think on old and new versions of VisIt and compare results. If they differ...you've got a problem I think...well, most likely. Its possible that dump_protocol includes state objects that aren't ever really used in the protocol.

@JustinPrivitera how would you feel about adding some CI for this for RC merges? Run the tool against some base output for RC branch and if there are diffs, flag the PR?

I would think that would be a great idea, and would be happy to do it if I knew how. Any chance you could show me?

Sure. But, now that I am thinking about it, I think our first step might have to be to investigate that protocol test we have and confirm its really doing what we think its doing. I worry it may have fallen out of data w.r.t. the actual state objects VisIt is passing around between components. It may require manual intervention to update it each time a new state object is added. I honestly don't know. That step alone may involve more effort than I had in my mind's eye when suggesting it.

merge w/ develop in #19735


expr: explicit SIMD

I've been working with some other database things recently and it seems that Rust compiler cannot automatically vectorize array-array operation.
https://godbolt.org/z/G8WMr4acY
Probably we should bring back the portable SIMD expressions framework?

Bounds checking does not allow the compiler to auto-vectorize.
Try and test
res = vec::from_iter(a.iter().zip(b.iter()).map())

yeah it works! https://godbolt.org/z/eG61feTM4 I'll check if binary operations are actually vectorized in RisingLight later...

You can check them via cargo bench --bench array. It would be obvious which operations are vectorized and which are not.

I still prefer auto-vectorization over explicit SIMD, because usually compilers do it better than humans and it makes code cleaner. However, as mentioned above, auto-vectorization requires special craft of codes. There are plenty of things that prevent SIMD, e.g. bound check, branching. AKAIK, there's also no way to hint or ensure auto-vectorization for a piece of code in Rust, i.e. no equivalent for #pragma clang loop vectorize(enable).

Yep, I also think auto vectorization

… is good

https://matklad.github.io/2023/04/09/can-you-trust-a-compiler-to-optimize-your-code.html
:p


About Realestate10K original videos

Do you have a script for downloading the original videos in Realestate10K? Or, after downloading videos, what should I pay attention to in order to proceed with the subsequent processing operations on the dataset?

Hi, Did you manage to solve the issue?

Hi, Did you manage to solve the issue?

Refer to https://github.com/cashiwamochi/RealEstate10K_Downloader

@hehao13 @Yaomingshuai @ReinaKousaka
Do you know the original resolution of videos in Realestate10K?
1280x720?


Localize dashboard Controls folder

Part of #955, I'm purposely not bunching every file change together 1) to reduce the size of this PR, and 2) because I'm worried that we'll end up with a lot of merge conflicts if the PR sits for a while, considering that almost every razor file is going to be touched.
This localizes all razor components inside Components/Controls and enables localization.

Good call, thanks @drewnoakes


File unchanged after switching branches in workSpace

Issue Type: Bug

open project by using workspace file
git checkout [another branch]
file in workspace not change

VS Code version: Code 1.23.1 (d0182c3417d225529c6d5ad24b7572815d0de9ac, 2018-05-10T17:11:17.614Z)
OS version: Windows_NT x64 6.1.7601

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz (4 x 2400)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: disabled_softwarerasterization: unavailable_softwarevideo_decode: enabledvideo_encode: enabledvpx_decode: unavailable_softwarewebgl: enabledwebgl2: enabled

Memory (System)
7.88GB (1.32GB free)

Process Argv
C:\Program Files\Microsoft VS Code\Code.exe D:\workspace\project\act.code-workspace

Screen Reader
no

VM
0%

Extensions (34)

Extension
Author (truncated)
Version

html-snippets
abu
0.2.1

Bookmarks
ale
0.19.1

copy-relative-path
ale
0.0.2

npm-intellisense
chr
1.3.0

path-intellisense
chr
1.4.2

bracket-pair-colorizer
Coe
1.0.50

jquerysnippets
don
0.0.1

vscode-html-css
ecm
0.2.0

json-tools
eri
1.0.2

prettier-vscode
esb
1.3.1

auto-close-tag
for
0.5.6

auto-rename-tag
for
0.0.15

terminal
for
0.0.10

vue-snippets
hol
0.1.5

beautify
Hoo
1.3.0

smarty
imp
0.3.0

path-autocomplete
ion
1.9.0

fecs
Mar
0.10.0

vscode-autoprefixer
mrm
2.1.2

vscode-language-pack-zh-hans
MS-
1.23.5

python
ms-
2018.4.0

vetur
oct
0.12.3

tsimporter
pmn
1.2.14

vscode-icons
rob
7.23.0

vue-vscode-extensionpack
sdr
0.1.2

vue-vscode-snippets
sdr
1.3.0

autoimport
ste
1.5.3

json-schema-validator
tbe
0.1.0

python
tht
0.2.3

vscode-status-bar-format-toggle
tom
1.3.0

vscode-todo-highlight
way
0.5.12

vscode-jumpy
wma
0.3.1

JavaScriptSnippets
xab
1.6.0

html-css-class-completion
Zig
1.17.1

(2 theme extensions excluded)

VS Code is using different file watching strategies depending on your OS and your setup.
First thing to check:

[ ] I verified that the issue still reproduces in our insiders version (https://code.visualstudio.com/insiders/)
[ ] I verified that this issue is happening outside of a node_modules folder. Our file watcher ignores this folder!

To find out more about this issue, please first answer this:

[ ] What OS are you on
[ ] Does this happen from an empty workspace, a single-folder workspace or a multi-root workspace?
[ ] Do you have files.useExperimentalFileWatcher: true configured in settings?
[ ] What is your configured files.watcherExclude setting?

Then please answer the following depending on your setup:

[ ] It reproduces with any folder or workspace you open
[ ] The files/folders you open are on your local disk and not on a network share nor a UNC drive
[ ] The files/folders you open are not behind a symbolic link
[ ] The folder(s) opened use the exact same casing as they are on disk
[ ] It reproduces when I make a change to the file from another VS Code window (either from the editor or the file explorer)

Then please attach the output of our development console

run code --verbose from the command line
perform the action that causes you to not see the file change in VS Code
attach the output from the console (Help > Toggle Developer Tools > Console)

Thanks for taking the time to fill out this questionnaire.


Add support for cv2.BORDER_CONSTANT mode to several transforms

Hi there!
I've added support of cv2.BORDER_CONSTANT mode for Rotate, ShiftScaleRotate, OpticalDistortion, GridDistortion, ElasticTransform transforms (similar to PadIfNeeded).
I've tested it manually, works ok

./albumentations/augmentations/functional.py:781:120: E501 line too long (122 > 119 characters)
please correct error before review


The main differences between the prompt template and the prompt_FC template.

What are the main differences in details between the prompt template and the prompt_FC template? Please describe specifically.

Which prompt_FC template are you referring to?

What is the fundamental difference between minicpm.py aminicpm_fc.py inoss_model directory?

minicpm.py is for the model in prompting mode, while minicpm_fc.py is for the model in function calling mode. It's the same logic for ChatGPT or Claude in prompt vs FC mode, except since it's an OSS model, we have to do some special treatment to apply its chat template.

FC means the model supports native tool use. For example, for gpt in FC mode, it means we supply the function choices in the tools section: https://platform.openai.com/docs/guides/function-calling
while gpt in prompt mode just means we are using the model's normal text generation capability; it's also a walk-around for models that's don't natively support tool use: https://platform.openai.com/docs/guides/text-generation/quickstart

There is also a more detailed explanation in https://github.com/ShishirPatil/gorilla/blob/main/berkeley-function-call-leaderboard/CONTRIBUTING.md


Add more detail on releases to README

Add more detail to the README.md where releases are found and also add
the documentation for how to use the new auto-completion capabilities
provided by urfave and enabled in a recent PR.
Signed-off-by: Phil Estes<EMAIL_ADDRESS>(Related to comment in #3706)

Codecov Report

Merging #3712 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           master   #3712   +/-   ##
======================================
  Coverage    42.1%   42.1%
======================================
  Files         129     129
  Lines       14307   14307
======================================
  Hits         6024    6024
  Misses       7383    7383
  Partials      900     900

Flag
Coverage Δ

#linux
45.61% <ø> (ø)
:arrow_up:

#windows
37.05% <ø> (ø)
:arrow_up:

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 309c9c2...e33f703. Read the comment docs.

LGTM

LGTM

LGTM


When debugging NodeJS code, can not step into functions

VSCode Version: 1.8.1
OS Version: macOS Sierra

Steps to Reproduce:

Open project
Setup breakpoint
Click "Start Debugging" button
Code stop at the breakpoint
Click the "Step Into" button, the code will execute until next breakpoint.

Anyone meet this issue?

@foogao do you have a watch expression? If yes, please delete them and see whether problem disappears.

@weinand yes, i have some watch expressions, just remove them, works now. thanks
But why? "Watch expression" should be a common scenario, right? Is this a bug?

@foogao yes, this is a bug. Dup of https://github.com/Microsoft/vscode/issues/15253

@weinand OK, got it, thanks


Timeout waiting fot cluster operator, install failed on AWS. OCP 4.2 works on same account.

Please find the log bundle here:
https://drive.google.com/open?id=1EuEWy1KhoM1uLk0iemBMqGohw7blcEV1
Please notify me after the download.

kubelet.service: Failed at step EXEC spawning /usr/bin/hyperkube: No such file or directory

Right, MCD binary didn't get extracted properly. This would be resolved by https://github.com/openshift/machine-config-operator/pull/1301


Bug: Only works on mobile if no YAML

Describe the Bug
On mobile, Linter does not do anything when activated if there is existing frontmatter.
How to Reproduce
Steps to reproduce the behavior:

Create a new document in Obsidian mobile
Optionally create some content that Linter could fix
Invoke Linter via "Lint File"
It will perform its rules
Change things that would cause it to perform rules again (put blank lines in YAML, make changes that would cause the "date modified" field to change, whatever)
Invoke Linter again
Nothing happens

Tested with YAML Timestamp and Compact YAML
Expected Behavior
Linter's rules take effect
Device

[ ] Desktop
[x] Mobile

Additional Context
Cannot reproduce on desktop, only mobile. Tested on iPad.

More info: When I invoke Linter via the "Linter: Lint the current file" command when there is existing YAML, an error is generated: "An error occurred during linting. See console for details"

Do you mind providing the exact file contents to reproduce the issue? It sounds like an issue with the rule maybe not working on iOS, which woukd be odd, but I would need to see the console output to be sure.

This may be related to #367

Here's the console output.

Thanks! This looks like it is something iOS specific. What are your rule settings for yaml timestamp? Is that the only active rule? If not, can you test it as the only active rule to see if that rule is the problem?

I've uninstalled and reinstalled Linter, and re-enabled all the rules that I think I had active before, and I can no longer reproduce the issue. I'll let you know if it reappears.

Gotcha. That is good. Hopefully it stays gone.

If this is not able to be reproduced by the end of the week, I will go ahead and close this since it is no longer reproducible. Please let me know if this would be an issue for some reason.

It looks like this is no longer reprodcible, so I am going to go ahead and close this issue. Feel free to reopen this if it starts happening again.


SpanByte.ToByteArray() returns only the first 16 byte of the data if not used are reference

When iterating through entries in the log like
                using (IFasterScanIterator<SpanByte, SpanByte> iterator = kv.Log.Scan(kv.Log.BeginAddress, kv.Log.TailAddress))
                {
                    while (iterator.GetNext(out RecordInfo recordInfo))
                    {
                            // processing entry
                    }
                }

If I use process like
                        SpanByte keyObj = iterator.GetKey();
                        Console.WriteLine("Key: " + Encoding.ASCII.GetString(keyObj.ToByteArray()));

then I get back only the first 16 byte of the data, and some junk bytes (probably pointer value, or irrelevant part of the memory, which may cause memory access violation exception).
If It process it like
                        ref SpanByte keyObj = ref iterator.GetKey();
                        Console.WriteLine("Key: " + Encoding.ASCII.GetString(keyObj.ToByteArray()));

then it works fine.
Anyways, this is not working if I use it as an out parameter, then I get only the first 16 bytes again:
                    while (iterator.GetNext(out RecordInfo recordInfo, out SpanByte keyObj, out SpanByte valueObj))
                    {
                        Console.WriteLine("Key: " + Encoding.ASCII.GetString(keyObj.ToByteArray()));
                    }

and reffing didn't help either:
                    while (iterator.GetNext(out RecordInfo recordInfo, out SpanByte keyObj, out SpanByte valueObj))
                    {
                        ref SpanByte refKeyObj = ref keyObj;
                        Console.WriteLine("Key: " + Encoding.ASCII.GetString(refKeyObj.ToByteArray()));
                    }

This means either SpanByte ToByteArray() method gets the data the wrong way if not referenced, or can not be used as out parameter.

Yes, that's the way SpanByte works. It's not a bug. Varlen structs are like pointers, your can only access them via ref variable. The overloads with out will not work. If this is not acceptable, you can use Memory, or byte[] via object log.

The reason we have ref GetKey etc is exactly for this reason, to be able to work with varlen structs.

I kept an eye on the source of the SpanByte and thought this is somehow normal, but this still means it can not be used the way I described above, it may help to someone, and may avoid confusion why it is not working right if they try get it through the iterator out parameter.
Btw iterator may have a ref parameter instead, or in addition.

The reason we have ref GetKey etc is exactly for this reason, to be able to work with varlen structs.

Ok if this was planned, then this is a non-issue.

Iterator ref parameter will not help. It has to be a ref return variable, for varlen to work correctly. We might add a warning of someone uses the out version with SpanByte.

Anyways, this is not working if I use it as an out parameter, then I get only the first 16 bytes again:
                    while (iterator.GetNext(out RecordInfo recordInfo, out SpanByte keyObj, out SpanByte valueObj))
                    {
                        Console.WriteLine("Key: " + Encoding.ASCII.GetString(keyObj.ToByteArray()));
                    }

FYI, if you do the above with SpanByte you will get an exception saying it is not supported (not first 16 bytes).
System.NotSupportedException: 'Use GetNext(out RecordInfo) to retrieve references to key/value'.

It's fine for me, but it was a bit confusing. I know the project is still in progress, but without complete documentation this may cause some confusion. I've noticed I can use SpanByte only if reffed, so I've been using it since the beginning with ref.
Btw it caused some problem when I tried to make extension for SpanByte, and I just couldn't pass it anyhow to the extension method, because couldn't read only the first 16 bytes even if it was ref. This way a few days ago, I don't really remember how I did it, I may try again, because adding SetString() and GetString() would be nice, since keys are usually strings, but better to store them as byte[]. It is not a big problem, though, conversion in place is not a biggie.

Non-power-users should avoid SpanByte and use Memory<T> which behaves identically to normal C# types. SpanByte is a rather unique construct (pointer-based) that cannot be ever accessed in a non-ref setting, and as a return parameter it has to be a ref return value, not a ref or out param.


Complete Menu

Hello buddy, awesome tool you have created here,  congratz, i have a question, why i cant see the menu as you have the example on the git, if i dont use any tags its gives me only configuration or authentication, im missing somenthing? thanks in advance

Hey!
Thanks for the feedback, appreciate it.
You have to press Enter again. In the videos the Configuration and Authentication Menus weren't introduced yet.


Fix smoke tests

Details
Smoke tests are failing since https://apm-ci.elastic.co/job/library/job/apm-aws-lambda-smoketests-mbp/job/main/12/
Fixing it to have a green baseline for https://github.com/elastic/apm-aws-lambda/pull/370
Related Issues

https://github.com/elastic/apm-aws-lambda/pull/370

:green_heart: Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

Start Time: 2023-01-26T11:34:57.585+0000

Duration: 7 min 50 sec

Test stats :test_tube:

Test
Results

Failed
0

Passed
208

Skipped
2

Total
210

:robot: GitHub comments
Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

/test : Re-trigger the build.

run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

See https://apm-ci.elastic.co/job/library/job/apm-aws-lambda-smoketests-mbp/job/PR-371/ for successful runs

Has become obsolete because of https://github.com/elastic/apm-aws-lambda/pull/370


Impossible to create an aspect DataJobInfo using the REST API

Describe the bug
It seems that the type information cannot be set which blocks the creation of the object
To Reproduce
I get either a 500: "org.springframework.web.client.HttpClientErrorException$UnprocessableEntity: 422 Failed to validate record with class com.linkedin.datajob.DataJobInfo: ERROR :: /type :: union type is not backed by a DataMap or null.
[
    {
        "aspect": {
            "__type": "DataJobInfo",
            "name": "ingest",
			"description": "ingest data from src-ext_SFTP_test-jmc-02 into s3://ce00/test-perf-nifi",
			"type": "OTHERS"
        },
        "entityType": "dataJob",
        "entityUrn": "urn:li:dataJob:(urn:li:dataFlow:(urn:li:dataPlatform:nifi-zds1,test-jmc-02--to--myBucket,PROD),ingest)"
    }
]

or a 400 Bad request
[
    {
        "aspect": {
            "__type": "DataJobInfo",
            "name": "ingest",
			"description": "ingest data from src-ext_SFTP_test-jmc-02 into s3://ce00/test-perf-nifi",
			"type": {"string": "test"}
        },
        "entityType": "dataJob",
        "entityUrn": "urn:li:dataJob:(urn:li:dataFlow:(urn:li:dataPlatform:nifi-zds1,test-jmc-02--to--myBucket,PROD),ingest)"
    }
]

[
    {
        "aspect": {
            "__type": "DataJobInfo",
            "name": "ingest",
			"description": "ingest data from src-ext_SFTP_test-jmc-02 into s3://ce00/test-perf-nifi",
			"type": {"AzkabanJobType": "COMMAND"}
        },
        "entityType": "dataJob",
        "entityUrn": "urn:li:dataJob:(urn:li:dataFlow:(urn:li:dataPlatform:nifi-zds1,test-jmc-02--to--myBucket,PROD),ingest)"
    }
]

This was tested on datahub demo environment this day.
Expected behavior
I would like to create a DataJobInfo in order to set custom properties.
Desktop (please complete the following information):

Browser [e.g. chrome, firefox]
Version [/openapi/v3/api-docs -- v0.8.40]

Additional context
Seems similar to anomaly: https://github.com/datahub-project/datahub/issues/4289

I suspect that issue is due to the aspect that you were setting, use DataJobProperties instead as DataJobInfo deprecated.
[
{
"aspect": {
"__type": "DataJobProperties",
"name": "ingest",
"description": "ingest data from src-ext_SFTP_test-jmc-02 into s3://ce00/test-perf-nifi",
"type": {"string": "test"}
},
"entityType": "dataJob",
"entityUrn": "urn:li:dataJob:(urn:li:dataFlow:(urn:li:dataPlatform:nifi-zds1,test-jmc-02--to--myBucket,PROD),ingest)"
}
]
Please go through this class for reference com.linkedin.datahub.graphql.generated.DataJobInfo

Tanks for your reply.
Type: DataJobProperties didn't work. "EditableDataJobProperties" does, but I couldn't pass any "customProperties" attributes (or name). It should if I look at the java class you gave me...
Still, I managed to leave a comment.
Lineage vizualisation is not too nice, as I can't see the job title, and i really need custom attributes on this object.
Thanks for the tips though.
I didn't start using graphQL API (only openAPI). I'l try that next, but still, it would have been simpler for me to keep using openAPI.

I didn't get anychance with graphiQL interface.
Only the comment can be updated.

Hi @nmolinier  this seems like a troubleshooting issue, rather than a bug. We're happy to provide community support on our Slack channel, but currently reserve git issues for bugs. If you’d like to submit this as a feature request, please use our portal here: https://feature-requests.datahubproject.io/
If you're still having trouble, please join us at [slack.datahubproject.io](https://slack.datahubproject.io) and we can troubleshoot there. For now, I'm going to close this issue.

Hi @laulpogan ,
I don't understand how this can be seen as something else but a bug or a regression. As of today, neither openApi nor graphQlApi accessible through the solution allow the capability to set custom properties on datajob anymore.
Could you please reopen and try to reproduce the bug. Do I need to provide additional inputs ?


[azure-identity-cpp] publish version 1.3.0

Update vcpkg ports for Azure SDK release. This release may contain multiple ports.

Adding azure-identity to release
cc: @antkmsft, @schaabs, @ahsonkhan, @rickwinter, @vhvb1989, @gearama

@antkmsft I would like to ask what is the reason for introducing openssl into this port?

Hi @FrankXie05, openssl is there to support ClientCertificateCredential (to deal with certificates): https://github.com/Azure/azure-sdk-for-cpp/releases/tag/azure-identity_1.3.0

@antkmsft Very sorry I forgot this PR, I will re-pull to the latest master branch (because this PR is nine days old). 😬

LGTM.

@FrankXie05, @JackBoosY Can we get this PR merged now?


Adding READ_WRITE option for meassurements

Please, could it be possible to add READ_WRITE option to meassurements?
    /begin MEASUREMENT Signal1 "FreeRTOS"
      UBYTE FreeRTOS_ENUM_Signal1  0 0 0 1
      ECU_ADDRESS<PHONE_NUMBER>
      READ_WRITE
      SYMBOL_LINK "Signal1 " 0
    /end MEASUREMENT

I assume you mean you would want a way to create new measurements that are set to READ_WRITE, since READ_WRITE is not an issue during update and merging.
In principle this would not be difficult, but I'm not enthusiastic about adding a bunch of additional command line options to enable this for each different way of creating measurements. It also looks like tools consuming a2l files can easily convert existing measurements from read-only to read-write, so this would not be particularly valuable. As far as I know the quick conversion of existing measurements is the intended use-case of the READ_WRITE tag, while a CHARACTERISTIC should be used in all other cases.
Overall, I'm currently not inclined to do this.
How do you think this should work? What workflow requires you to create a writable measurement rather than a characteristic?

I may have misunderstood characteristics and meassurements concepts. We are working in a project with CANoe where we have a lot of legacy a2l files. Those files have lots of meassurements configured for read write access.
So the idea is to use characteristics instead meassurements?
At this time we are using a script to add read write tags to meassurements, but I understood that it was better to have this feature in a2ltool.


feat(Accordion): new component

Accordion
✨ Introducing a new component for the NuxtLabs UI : Toggleable Accordion Panels! 🎉
📝 This pull request introduces the Disclosure component from the Headless UI library. It enables the display of interactive accordion panels for hiding and revealing content.

🚀 Key features of this component include:

Customizable labels, leading icons, and content for each panel.
Options to enable/disable individual panels.
Control over the initial open/closed state of the panels.
Ability to change the color and size of the accordion panels.
Flexible icon customization for opening and closing the panels.
Support for disabling specific panels.
Option to open all panels by default.
Slots for customizing the button and content items.

❤ Please review the changes in this PR and provide feedback.
Resolves #156

I had a quick look and I would rather call this component Accordion :)
Also, what would you think of using the UButton for the triggers? It would allow to handle all the styling and the props like here https://github.com/nuxtlabs/ui/blob/dev/src/runtime/components/overlays/Notification.vue#L83 without configuring everything like the sizes, icons, etc.

I had a quick look and I would rather call this component Accordion :)
Also, what would you think of using the UButton for the triggers? It would allow to handle all the styling and the props like here https://github.com/nuxtlabs/ui/blob/dev/src/runtime/components/overlays/Notification.vue#L83 without configuring everything like the sizes, icons, etc.

You're right, I don't like the name Disclosure It's nice to be an accordion. I will work on these changes.

@benjamincanac done
Do you think we need to add as props for the content of the accordion?

@benjamincanac
Can we review this to work on new components like breadcrumbs ?

I've taken the liberty to make a few changes to your PR. Let me know what you think!

@benjamincanac
Nice changes. But what if we make the default variant 'soft' and add this example of the default 'soft' style to showcase an alternative accordion design?

I just have an issue with the disabled field on an item that doesn't get forwarded to the Button.

I will check it

Changing the as property from template to div in <HDisclosureButton as="div"> makes it work correctly

I fixed it by passing the disabled prop to the DisclosureButton which works with as="template".
Do you still see an issue?

I've updated the default slot example from your proposal.

@benjamincanac
disabled It's working well. I updated the default solot example and added the default variant soft. I think it looks very nice, rather than solid.

I agree, just pushed some changes too. Let me know 😊

I agree, just pushed some changes too. Let me know 😊
Nice tweak! ❤

Let's merge this then!

Nice component !
Is it possible to add an option that would let us choose if opening a panel should close the others or not ?
I have a usecase in which that would be helpful.
btw, thanks a lot for this amazing UI module !!! you guys are amazing

@mathieunicolas
Yes, it's existied!

You can open all items by enabling default-open props.

Chechout here: https://ui.nuxtlabs.com/elements/accordion#open

Or open a specific item by passing defaultOpen in the items array.

Check it out here: https://ui.nuxtlabs.com/elements/accordion#usage

Hi @Haythamasalama thanks for your quick reply !
My question was about the behaviour of the accordion when you click on a panel to open it : it would be nice to have the previously opened one automatically closing, so you always have one panel opened !
For example :

all panels are closed
you click panel 2, it opens
you click panel 3, it opens, and panel 2 closes

@mathieunicolas
Open issue with this description


BIN_PATH should be more flexible

If you changed the file:
https://github.com/stnolting/neo430/blob/master/sw/common/Makefile#L32
to
BIN_PATH ?= /mnt/c/msp430-gcc-<IP_ADDRESS>_linux64/bin
It would make it easier for the user to override the directory where the msp430-elf-gcc executable is found.  On linux they can just set the path using:
$ export BIN_PATH=/home/joe_user/ti_7/ccsv7/tools/compiler/msp430-gcc-<IP_ADDRESS>_linux64/bin
$ cd blink_led/
$ make clean all

Memory utilization:
   text	   data	    bss	    dec	    hex	filename
    590	      0	      0	    590	    24e	main.elf
Installing application image to rtl/core/neo430_application_image.vhd
Final executable size (bytes):
596
$

Good idea! ;)
I will change that for the makefiles and also for the batch compilation scripts.


feat: support return list and dict structure from api ListVariable

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

[x] N
[ ] Y

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

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

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

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

[x] N
[ ] Y

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

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

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

116 of 134 (86.57%)  changed or added relevant lines in 3 files are covered.
91 unchanged lines in 8 files lost coverage.
Overall coverage decreased (-0.02%) to 71.076%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

kclvm/query/src/selector.rs
73
91
80.22%

Files with Coverage Reduction
New Missed Lines
%

kclvm/ast/src/token.rs
1
58.9%

kclvm/ast/src/ast.rs
2
83.51%

kclvm/sema/src/core/symbol.rs
3
47.18%

kclvm/ast/src/config.rs
7
0.0%

kclvm/query/src/selector.rs
7
81.3%

kclvm/tools/src/LSP/src/hover.rs
12
90.0%

kclvm/tools/src/LSP/src/completion.rs
24
89.17%

kclvm/sema/src/ty/mod.rs
35
77.32%

Totals

Change from base Build<PHONE_NUMBER>:
-0.02%

Covered Lines:
53874

Relevant Lines:
75798

💛  - Coveralls


Refactor test framework to support Prod & Int environments.

Description
I recommend going through the commits when reviewing which is easier that looking at all the changes at once.
NOTE 1: This PR is not fully ready yet. Still need to refactor the remaining tests; but I wanted to share the framework changes asap. I'll be adding more commits.
NOTE 2: Some functional tests might fail in this PR.
Motivation and Context
Our E2E tests today are being run on every PR, targeting the Konductor prod endpoints which is not what we want. This change support testing our dev branches against the integration environment of the edge.
One more change is required to start running our latest release of Alloy against Konductor Prod. (In Progress)
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[x] Improvement (non-breaking change which does not add functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[ ] I have signed the Adobe Open Source CLA or I'm an Adobe employee.
[ ] I have submitted a documentation pull request or no changes are needed.
[ ] I have made any necessary test changes and all tests pass.
[ ] I have run the Sandbox successfully.

Added 3 more commits to fix the remaining tests. I'd like to merge this change so that any eng working on tests can base their work on it.


SdlRouterService crashes if SDL app sets targetSdkVersion to 31, and running on Android 12

Bug Report
SdlRouterService causes crash if the SDL app sets targetSdkVersion to 31, and running on Android 12.
Reproduction Steps

open app's build.gradle, and change targetSdkVersion to 31.
build the app, and run on Android 12 beta 5 device

Expected Behavior
The app should run normally even if the app's targetSdkVersion is 31. Please note that sdl_java_suite library's targetSdkVersion (which is 30 in release/5.3.0_RC branch) will be overridden by app's targetSdkVersion.
Observed Behavior
The app crashes by fatal exception below:
    E/AndroidRuntime: FATAL EXCEPTION: main
    ... <snip>
     Caused by: java.lang.IllegalArgumentException: net.shiniwa.mytestapp: Targeting S+ (version 31 and above) requires that one of FLAG_IMMUTABLE or FLAG_MUTABLE be specified when creating a PendingIntent.
    Strongly consider using FLAG_IMMUTABLE, only use FLAG_MUTABLE if some functionality depends on the PendingIntent being mutable, e.g. if it needs to be used with inline replies or bubbles.
        at android.app.PendingIntent.checkFlags(PendingIntent.java:375)
        at android.app.PendingIntent.getActivityAsUser(PendingIntent.java:458)
        at android.app.PendingIntent.getActivity(PendingIntent.java:444)
        at android.app.PendingIntent.getActivity(PendingIntent.java:408)
        at com.smartdevicelink.transport.SdlRouterService.enterForeground(SdlRouterService.java:1524)
        at com.smartdevicelink.transport.SdlRouterService.onCreate(SdlRouterService.java:1142)
        at android.app.ActivityThread.handleCreateService(ActivityThread.java:4491)

OS & Version Information

Android Version: Android 12 beta 5 (SPB5.210812.002)
SDL Android Version: release/5.3.0_RC branch (commit #60230823b341eb9e2e95f2c0649a322c7d5b9db1)
Testing Against: the crash has nothing to do with head unit, but you have to at least setup bluetooth pairing with head unit.

Test Case, Sample Code, and / or Example App
PR will be submitted later.

Hi @RHenigan,
Do you know the plan about when the minor release (5.3.1?) will be released?
I would like to know the specific plan about when sdl_java_suite library officially supports Android 12.

We don't yet have a date for release, and are still working toward full compatibility.

Fixed in #1771


Remove unused constants from FHIRDbConstants

Describe the bug
Following the connection refactor work in #1144 there are likely to be constants in FHIRDbConstants which are no longer used. These can be removed.

Were these already removed?

Not yet.

@punktilious Can i take this to learn more about this repo ?

Sure, go for it!


differentiate cookiecutter-help from help

#1168

Thank you!
I recommend also putting a few lines in the README.md about the Makefiles. For example:
# Makefiles

This repo contains 2 Makefiles:
- `Makefile`: (description...)
- `project.Makefile`: (description...)

How people can use the Makefiles: (including prerequisites and examples)

@turbomam, are you open to me adding a commit to this branch, that contains such a blurb in the README? I could do it during the 2-3pm PT hour.

I just did it, but you can enhance it if you want

digging up some evidence :-)

I hadn't committed. Which means you still have an opportunity to improve the branch.
I asked for your review on

https://github.com/microbiomedata/nmdc-schema/pull/1213