Stale externally shared files - better description required

remove them from the drive / sharepoint or  remove the sharing???

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

ID: 0192fe47-4af3-0a7b-74a1-efbe7ad7536a
Version Independent ID: 34ff03e6-aadf-638d-1b9f-30b999b19240
Content: Policy template reference in Cloud App Security
Content Source: CloudAppSecurityDocs/policy-template-reference.md
Service: cloud-app-security
GitHub Login: @rkarlin
Microsoft Alias: rkarlin

@bakerm00 Hi, thanks for your feedback. You are right, it doesn't remove the file or the sharing - I have updated the article. You should see the change within the next day.

just to clarify your response - if it doesn't remove the external sharing - what is the point in the policy?

@bakerm00 It's a baseline template, you can add the required action based on your organization's policy.

I don't believe this policy checks if a file has been opened either.


Letters Shared Between Two Words

Before jumping into Pr first comment for assign.
Problem statement : Create a function that returns the number of characters shared between two words.
Probelm Link :  https://edabit.com/challenge/qeCS48GXtK9NJLc9C
Choose one Cateorgy - Very Easy, Easy, Medium, Hard, Very Hard, Expert
question category : Hard

Before submitting a PR please Check some details.

[x] fileName formet should be in camelcase
example- returnTheNextNumber.py
[x]  Choose label for Problem , example- "good first issue", "easy"
[x]  In file there should be problem statement and link to problem

/* Problem-Task : This program will add two numbers
 * Problem Link : https://edabit.com/challenge/SFzHtm63XT6EYNHWY
*/
int main() {
    int bla;
    return 0;
}

This repository is vaild for HacktoberFest2020
Read before making PR - How to contribute on Github
Good Luck,

I would like to work on it.

pls assign me this issue


Is it normal that a thread can get the lock before lease time had past?

sequenceDiagram
    thread 1->>+redisson: try get lock, wait 20, lease time 20
    redisson-->>-thread 1: ok

    thread 1->>thread 1:runs for 15 seconds

    thread 2->>+redisson: try get lock, wait 20, lease time 20
    redisson-->>-thread 2: immediate ok

    note over redisson,thread 2:is this normal? lease time has not past yet<br>shouldn't thread 2 wait for 5 seconds then get the lock?

https://github.com/cuipengfei/Spikes/blob/22a9896137dd62bda5f030f5a3d33c67fba67310/jpa/spring-jdbc-distributed-lock-issue/src/test/java/com/github/spring/example/LockTest.java#L38C9-L49
the above junit test can reproduce this.
docker run -p 6379:6379 -d redis:7.0.12 --requirepass "mypass"
# start this docker container before running the above junit test

If I run these 2 threads in 2 jvms, then the lease thread 2 can only get lock after lease time is past.
But if I run them in the same jvm, then thread 2 can get lock before lease time is past.
Is this by design?

RLock object is re-entrant. Same thread can get acquire the same lock multiple times. You can check that the second thread is the same thread.

https://github.com/cuipengfei/Spikes/blob/22a9896137dd62bda5f030f5a3d33c67fba67310/jpa/spring-jdbc-distributed-lock-issue/src/test/java/com/github/spring/example/LockTest.java#L38C9-L49

It is not.
You can run this code to reproduce: https://github.com/cuipengfei/Spikes/blob/22a9896137dd62bda5f030f5a3d33c67fba67310/jpa/spring-jdbc-distributed-lock-issue/src/test/java/com/github/spring/example/LockTest.java#L38C9-L49
This code's log output shows thread numbers, they are different.

Just ran the junit test again, it is strange, this time thread 2 only gets the lock after lease time of thread 1 is past, which makes sense.
Not sure why the results were different previously.

Unable to reproduce with the code below.
        Thread t1 = new Thread() {
            @Override
            public void run() {
                RLock lock = redisson.getLock("lock");
                try {
                    if (lock.tryLock(20, 20, TimeUnit.SECONDS)) {
                        System.out.println("acquired " + Instant.now() + " " + Thread.currentThread().getName());
                    } else {
                        System.out.println("unable to acquire " + Instant.now() + " " + Thread.currentThread().getName());
                    }
                } catch (InterruptedException e) {
                    throw new RuntimeException(e);
                }
            }
        };

        Thread t2 = new Thread() {
            @Override
            public void run() {
                RLock lock = redisson.getLock("lock");
                try {
                    if (lock.tryLock(20, 20, TimeUnit.SECONDS)) {
                        System.out.println("acquired " + Instant.now() + " " + Thread.currentThread().getName());
                    } else {
                        System.out.println("unable to acquire " + Instant.now() + " " + Thread.currentThread().getName());
                    }
                } catch (InterruptedException e) {
                    throw new RuntimeException(e);
                }
            }
        };

        t1.start();
        t2.start();

        Thread.sleep(60000);

Unable to reproduce with the code below.
        Thread t1 = new Thread() {
            @Override
            public void run() {
                RLock lock = redisson.getLock("lock");
                try {
                    if (lock.tryLock(20, 20, TimeUnit.SECONDS)) {
                        System.out.println("acquired " + Instant.now() + " " + Thread.currentThread().getName());
                    } else {
                        System.out.println("unable to acquire " + Instant.now() + " " + Thread.currentThread().getName());
                    }
                } catch (InterruptedException e) {
                    throw new RuntimeException(e);
                }
            }
        };

        Thread t2 = new Thread() {
            @Override
            public void run() {
                RLock lock = redisson.getLock("lock");
                try {
                    if (lock.tryLock(20, 20, TimeUnit.SECONDS)) {
                        System.out.println("acquired " + Instant.now() + " " + Thread.currentThread().getName());
                    } else {
                        System.out.println("unable to acquire " + Instant.now() + " " + Thread.currentThread().getName());
                    }
                } catch (InterruptedException e) {
                    throw new RuntimeException(e);
                }
            }
        };

        t1.start();
        t2.start();

        Thread.sleep(60000);

I can not reproduce this again with my own code either.
I guess the first time when I saw this issue, there might be something wrong with my code or env.
Should be ok to close this ticket.

https://stackoverflow.com/questions/76856466/spring-integration-distributed-locks-conceptual-consistency-of-ttl-as-compared
@mrniko  @jackygurui   It would be much appreciated if you could take a look at the above stackoverflow question, which is trying to find out the design rationale of Redisson's lease time vs Spring Integration's TTL.
I have written down my own interpretation in the SO question, it could very well be off the mark since I am not that famaliar with the source code of both libs. Would be great to get your thoughts on this question.


feat(tier4_planning_launch): generalize launch files

Signed-off-by: Takayuki Murooka<EMAIL_ADDRESS>Description
Updated tier4_planning_launch so that tier4_planning_launch will be product-agnostic.
Not all parameters may be extracted in planning.launch.xml, but most of them which are important to be product-agnostic were extracted.

Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[x] I've confirmed the contribution guidelines.
[x] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[x] The PR follows the pull request guidelines.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.

After all checkboxes are checked, anyone who has write access can merge the PR.

Sorry, I forgot to add these parameters, which I removed from launch
https://github.com/autowarefoundation/autoware.universe/pull/770/commits/0b2e36fb74554bb42f7109a2b97811a877f2d466

With this commit,

Added default parameters of declare_parameter of cpp files in launch config file.
Copied launch config file to obstacle_stop_planner package's config file.
https://github.com/autowarefoundation/autoware.universe/pull/770/commits/1cf1d0a25907bae846312d2802e626691434104f

I verified this PR with the following one, removing default parameters of declare_parameter.
https://github.com/autowarefoundation/autoware.universe/pull/772
Now it's ready to merge.

@kenji-miyake

It seems some default values have changed, so users who directly refer here should take care of them.
Lemme check.
enable_slow_down, motion_velocity_smoother_type, use_surround_obstacle_checker, bt_tree_config_file can be changed.
Is this what you are concerning about?

No, this part.

Right. Thanks for your comment.

@takayuki5168 Do you undo some of the parameters that have been changed?

@yukkysaito
Then planning package's parameters and launcher's parameters differs. Is that OK?


NoSemicolonsRule: don't report when semicolon is before annotation/comment/kdoc and lambda

Fixes #825

Thanks!


Missing link to fips_config documentation

Checklist

[x] documentation is added or updated
[ ] tests are added or updated

This pull request is ready to merge

Merged. Thanks!


implement validation for GatewayClass resource

This currently comprises only of an immutability check for
spec.controller field. This can expanded in future.

What type of PR is this?

/kind feature
What this PR does / why we need it:
This validation is a pre-requisite for #189. Once this is merged in, we can start enforcing this using a validation webhook.
Which issue(s) this PR fixes:

None
Does this PR introduce a user-facing change?:

NONE

xref https://github.com/kubernetes/kubernetes/issues/65973

@robscott @jpeach Should we be implementing this validation for v1alpha1 and v1alpha2 both?

I made the mistake of pushing to this repo and creating this PR. This results in a protected branch and I can't force-push a protected branch so I'm going to close this. I've opened up https://github.com/kubernetes-sigs/gateway-api/pull/663 to continue the work here. Apologies for the inconvenience.
/close


[release-v1.4] Knative error extensions (#2374)

backport

/cherry-pick release-v1.3

/retest

/retest

  *[2022-08-23T15:45:01Z]NoClusters: No clusters in pool are ready to be claimed

/test 46-test-conformance-aws-ocp-46

  *[2022-08-24T12:38:06Z]NoClusters: No clusters in pool are ready to be claimed

/retest


drivers: clock_control: Clarify allowed calling context of API functions

Clarified that clock_control_off and clock_control_async_on can be called from any context since they are non-blocking.
Additionally, fixed:
drivers: clock_control: Remove false description of clock_control_async_on
Description of clock_control_async_on contained information about
delayed start which is not supported by this function call.
Given that https://github.com/zephyrproject-rtos/zephyr/pull/20710#discussion_r348153385, I've updated function descriptions to explicitly state that they can be called from any context.

@nordic-krch can you please fix the gitlint issue?

@carlescufi done.


fix: blurry text on browser zoom

If you zoom out in the browser on some devices, floating items are blurred.
description of the issue: https://github.com/floating-ui/floating-ui/issues/779
mention of blurriness in floating-ui docs: https://floating-ui.com/docs/misc#subpixel-and-accelerated-positioning

x and y can contain fractional numbers (decimal), so there will be blurring unless we place it evenly on the device’s pixel grid. The rounding method above ensures the floating element is positioned optimally for the screen.

fixing with basic floating-ui example: https://floating-ui.com/docs/react#positioning

@ayoung19 Thanks for the PR, but to achieve the desired effect, you can use transform={false} instead, the transform prop allows users to choose their preferred positioning method (transform or top/left) (see: https://headlessui-float.vercel.app/react/other-options.html#position-mode), so I will close this PR for now 😅.

ah got it, totally missed that option. i think the default should be false because if we want the normal correct behavior we have to put transform={false} everywhere and it's not really clear that the reason for that is to make it not blurry

OK, I'll do some research to see if this adjustment is a breaking change.


OpenCensus strips off annotations before sending

What happened:
Traces with annotations that worked before using the OpenCensus agent no longer have annotations after passing through the OpenCensus agent.
What you expected to happen:
I expected all the relevant trace information to be passed forward to the relevant backends.
** How could we fix **
Looked at the OpenCensus agent source, and this seems to be the issue. Either have to code it, wait, or not use it.
How to reproduce it (as minimally and precisely as possible):
Send traces with annotations directly into Stackdriver, note that the annotations show up, and then run the same traces through the OC agent and then into Stackdriver, and note the missing annotations.

OpenCensus agent has not implemented transfer of annotations at the time of this comment.


"failed to get git config safe.directory" during setup

Description
Hello :)
I tried to setup gitea locally on my windows machine for testing, but I encountered the following error during setup:
routers/init.go:73:mustInitCtx() [F] code.gitea.io/gitea/modules/git.InitFull(ctx) failed: failed to get git config safe.directory, err: exit status 6 - error: invalid pattern: *
 - error: invalid pattern: *

Below, I tried to find out where this error could come from
C:\Users\sebas>git config --get safe.directory
K:/dev/wikiextractor

C:\Users\sebas>git config --global --list
filter.lfs.clean=git-lfs clean -- %f
filter.lfs.smudge=git-lfs smudge -- %f
filter.lfs.process=git-lfs filter-process
filter.lfs.required=true
user.name=Sebastian
<EMAIL_ADDRESS>safe.directory=F:/xampp.old/htdocs/adrema
safe.directory=K:/AI/stable-diffusion-webui
safe.directory=K:/GitHub/rmmagent
safe.directory=K:/dev/wikiextractor

C:\Users\sebas>git --version
git version 2.43.0

with little success
Gitea Version
1.22.3-gogit-windows-4.0-amd64
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
https://gist.github.com/TheMcSebi/b42a342c39aa32e8b630aca5aac902ad
Screenshots

Git Version
2.43.0
Operating System
Windows 11 23H2
How are you running Gitea?
Downloaded the amd64 gogit exe from github, ran it from cmd using "gitea web"
Database
PostgreSQL

It seems to be a git's bug.
Could you try git 2.43.4 and/or some latest git (2.47.0)?

More details:

Gitea uses its own git config (not the current user's)
Gitea tries to do git config --global --get \* to check whether the safe.directory is correctly configured.

Thank you, that solved the issue.
Apparently I've unknowingly been using some git executable that came with devkitPro for ages.
Thanks again for the quick support and your work on this great project!

More details:

Gitea uses its own git config (not the current user's)
Gitea tries to do git config --global --get safe.directory \* to check whether the safe.directory is correctly configured. The wildcard is escaped as a regexp.

Maybe Windows or GitForWindows doesn't handle the \* correctly.

MSYS2 git(v2.47.0)
Git for Windows git(v2.47.0.windows.1),
after running git config --global --get safe.directory \*, both show error: invalid pattern: *
Using msys2's git, gitea cannot start after initialization, the error is failed to get git config safe.directory, err: exit status 6 - error: invalid pattern: *
Using Git for Windows, gitea works fine after initialization

I couldn't find anything related to this issue on the git-for-windows github issues.
Do you think it would be helpful if I created a bug report over there or if I create a pull request to the gitea docs repo to mention this dependency?

Maybe send an issue to git-for-windows is better according to https://github.com/go-gitea/gitea/issues/32237#issuecomment-2407943663.

I couldn't find anything related to this issue on the git-for-windows github issues. Do you think it would be helpful if I created a bug report over there or if I create a pull request to the gitea docs repo to mention this dependency?

This maybe a problem with git based on cygwin rather than git-for-windows, according to this msys2 documentation


Year needs to be dynamic in footer

Is your feature request related to a problem? Please describe.

Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

Hello @thestarsahil please assign this issue to me under gssoc 24

This season we are looking for major problem and solution containing level 3
Please look onto some other major problem


Add further numpy support

Extend current python bindings to be able to not only receive numpy arrays but also return numpy arrays.

Closed via #103


Add datadog spans for file I/O and XLSX parsing

Ticket #1676
Description
Uses the dd-trace library to capture custom spans for potentially expensive file I/O and XLSX parsing operations.
Screenshots / Demo Video
This should help fill in some of the gaps in these Datadog traces.

Testing

Boot up reporter locally
Using any valid sample data, generate either the treasury report or audit reports
Verify that behaviour remains unchanged

@TylerHendrickson I wonder if we can point development instances to the "sandbox" environment on datadog?  That might be a useful way to validate that behaviour hasn't been broken.
Automated and Unit Tests

~Added Unit tests~

Manual tests for Reviewer

[x] Added steps to test feature/functionality manually

Checklist

[x] Provided ticket and description
[x] Provided screenshots/demo
[x] Provided testing information
~Provided adequate test coverage for all new code~
[x] Added PR reviewers

@ajhyndman re

@TylerHendrickson I wonder if we can point development instances to the "sandbox" environment on datadog? That might be a useful way to validate that behaviour hasn't been broken.

Yeah, please feel free to generate personal DD credentials and use them in your dev instance while you're debugging something. I hesitate to do this by default on all dev instances (for one, it would require hard-coding the DD creds to the repository; for another, it could easily get expensive, especially since most people probably won't be looking at Datadog during development), and would prefer to refer to the Staging environment (tagged with env:staging) for regression analysis.

@TylerHendrickson great, actually this makes a ton of sense.  Thanks!


Consuming ResultSet more than once

Inside QueryExecutionListener.afterQuery, we have access to the ExecutionInfo.getResult(). Sometimes, this is a ResultSet. However, if you consume the ResultSet in the listener (e.g. to log the query results), then the real application usage of the ResultSet will fail because the ResultSet cannot be consumed more than once.
Some JDBC drivers implement scrollable result sets, so with those it might be possible to use ResultSet.beforeFirst(), but many JDBC drivers are not scrollable.
To solve this, I came up with a ResultSet proxy that caches the results of methods such as ResultSet.getString(int columnIndex) so that the ResultSet can be consumed more than once.
See here for the implementation and here is a main method that demonstrates how it can be used.
Would you be interested in merging this proxy into the datasource-proxy project, as an alternative implementation of JdbcProxyFactory? I will be able to write some decent test coverage for it before then of course, just seeing if you are interested first.

Hi @theangrydev
Thanks for the proposal. I checked your implementation and I like the idea!!
This would be a good alternative strategy for JdbcProxyFactory.
Please create a pull request and I'll be happy to merge it.
Thanks a lot,

merged via ed6318f
Thanks for PR!!

I have released datasource-proxy 1.4 and this feature is included.


Can not import

This is what I get.

PS C:\Users\outasi\Documents> ffpass import -d C:\Users\outasi\Documents -f pass.csv Firefox password database is empty. Please create it from Firefox.

I used the wrong path, sorry.


[native_assets_builder] Implement equals and hashCode on asset paths

Thanks for your contribution! Please replace this text with a description of what this PR is changing or adding and why, list any relevant issues, and review the contribution guidelines below.

[x] I’ve reviewed the contributor guide and applied the relevant portions to this PR.

Contribution guidelines:

See our contributor guide for general expectations for PRs.
Larger or significant changes should be discussed in an issue before creating a PR.
Contributions to our repos should follow the Dart style guide and use dart format.
Most changes should add an entry to the changelog and may need to rev the pubspec package version.
Changes to packages require corresponding tests.

Note that many Dart repos have a weekly cadence for reviewing PRs - please allow for some latency before initial review feedback.

@dcharkes

@dcharkes, does this require version change or change-log entry?

@dcharkes, does this require version change or change-log entry?

Added a skip.
There's also a formatting error:
Run dart format --output=none --set-exit-if-changed .
  dart format --output=none --set-exit-if-changed .
  shell: /usr/bin/bash -e {0}
  env:
    DART_HOME: /opt/hostedtoolcache/dart/3.3.1/x64
    PUB_CACHE: /home/runner/.pub-cache
Changed lib/src/model/kernel_assets.dart
Formatted 45 files (1 changed) in 0.49 seconds.
Error: Process completed with exit code 1.

There's also a formatting error:

Right. Forgot I'm not on Flutter repo :)

coverage: 93.216% (+2.5%) from 90.766%
when pulling c491d9a5103a3bbd0d7f531bd7bd02ccd9fc0730 on knopp:path_equality
into 7eefc74aef681571604e76e6578c63e23bba9a41 on dart-lang:main.


Escape the TUI log lines in ANSI color mode

This PR escapes the log line in the useAnsi branch of LogView.WriteString. Without this escape, substrings that match [\w+] are interpreted by regions and cause display issues.

This PR can be tested by running process compose with the following config:

Good catch @enobayram!
Thank you for the PR!

And thank you for reviewing and merging it quickly! (Not to mention developing this excellent utility :slightly_smiling_face:)


add a .editorconfig file?

https://editorconfig.org/

If we add that, we also want to exclude it from being packaged via a MANIFEST.in entry.


feat(storage): enable preload for log store and dynamic filter

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?
enable preload for those executor:

cmd scan
log store reader
streaming dynamic filter
streaming source reader

Checklist

[ ] I have written necessary rustdoc comments
[ ] I have added necessary unit tests and integration tests
[ ] I have added test labels as necessary. See details.
[ ] I have added fuzzing tests or opened an issue to track them. (Optional, recommended for new SQL features #7934).
[ ] My PR contains breaking changes. (If it deprecates some features, please create a tracking issue to remove them in the future).
[ ] All checks passed in ./risedev check (or alias, ./risedev c)
[ ] My PR changes performance-critical code. (Please run macro/micro-benchmarks and show the results.)

[ ] My PR contains critical fixes that are necessary to be merged into the latest release. (Please check out the details)

Documentation

[ ] My PR needs documentation updates. (Please use the Release note section below to summarize the impact on users)

Release note
If this PR includes changes that directly affect users or other significant modifications relevant to the community, kindly draft a release note to provide a concise summary of these changes. Please prioritize highlighting the impact these changes will have on users.

+1 for the idea that backfilling uses read rather than streaming_read to prefetch because the backfilling workload differs from the normal batch query, it will cancel on each barrier. Using streaming_read for backfilling could cause high
instantaneous connection number.

@Little-Wallace @chenzl25 @hzxa21
Hello everyone, thanks for your work on this PR. I'll be updating the related documentation, and could you please let me know the parts that require updates on the doc side? Thanks in advance!

@Little-Wallace @huangjw806 Can we cherry-pick this PR into 1.5.2?


[Regression] all --vars of run_results artifact are casted to str but they were not before

Is this a regression in a recent version of dbt-core?

[X] I believe this is a regression in dbt-core functionality
[X] I have searched the existing issues, and I could not find an existing issue for this regression

Current Behavior
Our dbt retry using a variable from CLI of type INT are failing because during the retry dbt sees it as STR.
I compared the run_results.json from dbt 1.8 to run_results.json from dbt 1.7 and I can see that the one from 1.8 have all the vars as STR whereas from 1.7 they kept their original type.
Expected/Previous Behavior
vars in run_results.json should keep the same type as the one give through the CLI
Steps To Reproduce

with dbt 1.8, run a dbt run command with a variable of type int
look at the run_results.json artifact

Relevant log output
No response
Environment
- OS:MacOS Sonoma 14.5
- Python: Python 3.10.11
- dbt (working version): 1.7
- dbt (regression version): 1.8

Which database adapter are you using with dbt?
redshift
Additional Context
I believe the regression is caused by this PR that applies the scrubbing function to ALL cli variables whereas this function cast its input to str systematically
def scrub_secrets(msg: str, secrets: List[str]) -> str:
    scrubbed = str(msg)

    for secret in secrets:
        scrubbed = scrubbed.replace(secret, "*****")

    return scrubbed

Thanks for reporting this @fabientra and identifying the originating PR 👑
I was able to reproduce this (see details in "Reprex" below).
Possible fix
A possible fix might be leaving msg as-if here unless there were any secrets scrubbed:
def scrub_secrets(msg: str, secrets: List[str]) -> str:
    scrubbed = str(msg)

    for secret in secrets:
        scrubbed = scrubbed.replace(secret, "*****")

    return msg if str(msg) == scrubbed else scrubbed

i.e. just replace the return statement here with this:
    return msg if str(msg) == scrubbed else scrubbed

Of course you'll probably still get an error during dbt retry if you included a secret within your --vars, but that's acceptable because:

we'd hope folks don't include secrets in --vars, and
we explicitly don't want to write out secrets in plain text (which would be required for retry).

Reprex

Start with a models/my_model.sql like this:
{% if execute %}
  {{ exceptions.raise_compiler_error("Force a failure") }}
{% endif %}

{% if not var("id") is number %}
  {{ exceptions.raise_compiler_error("var('id') is not a number") }}
{% endif %}

select 1 as id

And try to run it like this (which will yield an error):
dbt run -s my_model --vars '{"id": 2}'

Then remove these first 3 lines from models/my_model.sql so that it no longer will error this specific way:
{% if execute %}
  {{ exceptions.raise_compiler_error("Force a failure") }}
{% endif %}

And retry it:
dbt retry

For completeness, we'd probably want to update the type hints as well:
def scrub_secrets(msg: Any, secrets: List[str]) -> Any:

Thank you for the fix @dbeatty10 :)


Bug: not authorized to perform datasets-version-endpoint

Bug Description

Am trying to test the data validation story.
Have assumed the role below by from the Data Services AWS Account.
How to Reproduce**

aws lambda invoke --function-name nonprod-datasets-version-endpoint --invocation-type RequestResponse --payload '{"httpMethod": "POST", "body": {"id": "c5e3eca777dd11eba52553fff40505df", "metadata-url": "https://s3.console.aws.amazon.com/s3/object/data-lake-test-bn?region=ap-southeast-2&prefix=data_lake_test/checksum_validation_review/collection.json", "type": "RASTER"}}' --region ap-southeast-2 /dev/stdout

An error occurred (AccessDeniedException) when calling the Invoke operation: User: arn:aws:sts::632223577832:assumed-role/nonprod-geospatial-data-lake-use-usersrole18D0AA3B-L1BSHG3ZPQJL/datalake-user is not authorized to perform: lambda:InvokeFunction on resource: arn:aws:lambda:ap-southeast-2:632223577832:function:nonprod-datasets-version-endpoint
Try to include any stack traces or debugging info.

Software and OS versions

OS: Ubuntu 18.04 VM on my Mac

Environment: LINZ Mobility
Relevant Software Versions: <!-- e.g. aws --version -->

Additional context

Now ressolved with new authenticaion methods


add Arisa Fukuzaki in src/profiles and src/images

Let me know if the image is not following the format🙏

You're right! Good catch and I fixed it, thanks ;)


Fixes PBXObject equality

Resolves #223
This makes PBXObject conform to Equatable which then calls out to an instance method that all subclasses override. When we move to Sourcery we can remove all of this

This change is

@yonaskolb, apparently there are some tests that are failing:


Intermittent Failures or Delays in Build and Run Action

Description:

Steps to reproduce:
Affected Versions:
OS, DB, other environment details and versions:
Related Issues (optional):
Ref: https://discord.com/channels/955510916064092180/1280067954708578404/1280067954708578404
Suggested Labels (optional):

Suggested Assignees (optional):

I think, I have found the cause of this issue. The server starting seems to fail frequently if the Runtime Services panel is already open in VSCode. When you close the panel before hitting Build + Run the server starts fine.

Closing this as it is not a bug.


Docker updates

Overview

Updates docker-compose setup
adds environment variable support to configuration

Related Issue / Discussion
NA
Additional Information
NA
Contributions and Licensing
(as per https://github.com/geopython/pycsw/blob/master/CONTRIBUTING.rst#contributions-and-licensing)

[x] I'd like to contribute [feature X|bugfix Y|docs|something else] to pycsw. I confirm that my contributions to pycsw will be compatible with the pycsw license guidelines at the time of contribution.
[x] I have already previously agreed to the pycsw Contributions and Licensing Guidelines

@ricardogsilva any idea why Travis did not run on this PR?

Now the codecov checks pass, but Travis still does not run.

OK looks like Travis ran (weird, was not shown as running).


Add TCP Fast Open support

This is a preliminary effort to add TCP Fast Open support to libuv. It compiles, but it might be completely broken at the moment.
I am submitting this as PR to get a feedback if this is heading into right direction, or it should be rewritten in a completely different way.

Is this still open? Should be reviewed and closed or merged

LGTM
@saghul Any thoughts?

Hi, @oerdnj. Great work and it seems stalled now. Would you mind me picking this up and push forward basing on your work?

@oyyd Sure, I would be delighted if somebody would finish the work into mergeable state. Thanks!

@oerdnj @oyyd  Any update ?  or maybe @oerdnj can write some guite to help people understand how to finihish this work.

@patrickkh7788 No. I found it was a lot more complicated than imagined :-(

I might need it for another different DNS server I am working on, so I’ll take a look (or somebody from my team will).
--
Ondřej Surý<EMAIL_ADDRESS>
On 3 Mar 2019, at 13:00, Ouyang Yadong<EMAIL_ADDRESS>wrote:
@patrickkh7788 No. I found it was a lot more complicated than imagined :-(
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

JFTR The MSG_FASTOPEN is not available on macOS (although it defines TCP_FASTOPEN, and the test is broken because of that, so I have to check how to enable TFO on macOS yet.

@oerdnj macOS use connectx with flags CONNECT_DATA_IDEMPOTENT to indicate a socket use TFO.
See http://www.manpagez.com/man/2/connectx/ and
https://github.com/facebook/folly/blob/95ceac6552694ee1dc4f6f289a408aa9eeabc262/folly/detail/SocketFastOpen.cpp#L68

@oerdnj  Do you think I can use this patch on linux/android without problem ?

Well, the first iteration might be just a no-op on macOS, right?

Has TFO actually been enabled by default on any major browser (or OS)? FWIW, QUIC should have a similar feature.
Ref:
https://github.com/curl/curl/issues/3662#issuecomment-471315063

QUIC doesn't really seem related to this libuv change, except for the perspective of QUIC perhaps lessening the desire to make TCP faster.

@vcunat I mention QUIC because the claimed difficulty with deploying TCP Fast Open is sometimes given as a reason behind the QUIC design. Similar benefits, different design. E.g. https://www.nanog.org/sites/default/files/Paasch_Network_Support.pdf
I'm not trying to argue against TFO. Merely providing context.

@oerdnj
I try apply the patch to the recent  v1.30.1, seems not work anymore.  can you rebase this PR to made it mergeable into  v1.30.1?

@oerdnj
I apply your patch ( https://gist.github.com/patrickkh7788/e8724c4424fb8c9fad45ca832e5e90ad )  on libuv v1.30.1,  when I call the uv_write, the data is send twice.  can you take a look at this ?

@oerdnj
Hi,   Ondřej Surý, thanks for the nice work.
I try cherry pick your branch into last release version, it work on my local server address.
when I try connect to a real nginx server.   the write callback return UV_EALREADY ( connection already in progress).  have you ever got this problem ?
The uv_tcp_connect callback has no error, and it cost 0ms to connected.  but when I try write I get UV_EALREADY.  (test on linux)

I rebased the branch on top of current v1.x branch, cleaned up the code a little bit and pushed.  The commit message isn't up to par with current standard, but the code is there and it compiles.
It has been a long time since I first worked on this, so the only teeny-tiny problem is that the test fails, so it might not work at all :)
not ok 276 - tcp_fastopen_open
# exit code 6
# Output from process `tcp_fastopen_open`: (no output)
Output from process `tcp_fastopen_open`:
# uv_write error: address family not supported
# Assertion failed in test/test-tcp-fastopen.c on line 119: 0

Ok, now the test if fixed.  The sendto() can return EINPROGRESS in which case it submitted a data-less SYN packet to get the cookie, so the sendto() needs to be repeated.  After the fix the test works as expected.

Almost there .. ;)

Any updates on this PR?
This will be very useful for us to add support for TCP Fast Open in Node.js

My recollection (it's been a while) is that this PR is unlikely to get merged anytime soon because:

TFO is effectively Linux-only at the moment, and

Even on Linux it's not always usable/enabled/etc.

Libraries not supporting a feature because it's not commonly used?  Isn't that a circular argument?

I’ve seen the discussion about TFO for njs, so I guess I can rebase this on top of current v1.x and try to get this merged again.

I’ve seen the discussion about TFO for njs, so I guess I can rebase this on top of current v1.x and try to get this merged again.

Great! Thanks @oerdnj . That would be really helpful!

Libraries not supporting a feature because it's not commonly used? Isn't that a circular argument?

No, because that's not the argument. Libuv is a platform abstraction layer. If Linux is the only platform that implements TFO, then it makes no sense to support that in libuv because there's nothing to abstract.
The fact that it doesn't even always work on Linux is just icing on the cake.

I see that Windows support is also available. https://learn.microsoft.com/en-us/windows/win32/api/Mswsock/nc-mswsock-lpfn_connectex

TIL! This doesn't sound very promising, however:
Note that to make use of fast opens, you should use [ConnectEx](https://learn.microsoft.com/en-us/windows/desktop/api/Mswsock/nc-mswsock-lpfn_connectex) to make the initial connection, and specify data in that function's lpSendBuffer parameter to be transferred during the handshake process. Some of the data in lpSendBuffer will be transferred under the Fast Open protocol.

So seentially we could only support that if you call uv_write before uv_connect actually does the connecting... sounds pretty clunky to use IMHO.

TIL! This doesn't sound very promising, however:
Note that to make use of fast opens, you should use [ConnectEx](https://learn.microsoft.com/en-us/windows/desktop/api/Mswsock/nc-mswsock-lpfn_connectex) to make the initial connection, and specify data in that function's lpSendBuffer parameter to be transferred during the handshake process. Some of the data in lpSendBuffer will be transferred under the Fast Open protocol.

So seentially we could only support that if you call uv_write before uv_connect actually does the connecting... sounds pretty clunky to use IMHO.

There are already places with delayed syscalls, aren’t they? We can delay the connect system call until the first write happens.

There are already places with delayed syscalls, aren’t they? We can delay the connect system call until the first write happens.

That could work!

We can delay the connect system call until the first write happens.

Can you elaborate on how that would work? I can parse that sentence in multiple ways, none which seem feasible or desirable.

I'd assume it means to do something like:
h = uv_tcp_init(...);
uv_tcp_fastopen(h, 1);
uv_connect(...)
uv_write(...)
# connect would happen when uv_write is called, on Windows at least

I'd assume it means to do something like:
h = uv_tcp_init(...);
uv_tcp_fastopen(h, 1);
uv_connect(...)
uv_write(...)
# connect would happen when uv_write is called, on Windows at least

Well, in fact, the PR already does that on Linux. It just have been so long, that I've forgotten what I did here :).

Yeah, that was one of the possible interpretations. :-)
Okay, I see a couple of problems with that:

undesirable: also needs to special-case connect + read; more special cases == more ugly

undesirable: breaks code that only starts writing from uv_connect_cb; makes uv_tcp_fastopen() not a drop-in replacement

undesirable: delaying the connect() call regresses handshake performance

IMO, it'd be best to go in the write-before-connect direction. Clunky but no other undesirable attributes.

Yeah, that was one of the possible interpretations. :-)
Okay, I see a couple of problems with that:

undesirable: also needs to special-case connect + read; more special cases == more ugly

The only special case needed would be that you need to start writing (uv_write()) before you start reading (uv_read_start()), otherwise TFO would be ineffective.
Note: uv_try_write() should always fail in not connected yet, so we can process the connect failures.

undesirable: breaks code that only starts writing from uv_connect_cb; makes uv_tcp_fastopen() not a drop-in replacement

Why? The uv_connect() would call the callback immediately (without calling system connect()), so in fact, it would be a drop in replacement.

undesirable: delaying the connect() call regresses handshake performance

Can you elaborate a bit more? I don't understand what you mean here.

IMO, it'd be best to go in the write-before-connect direction. Clunky but no other undesirable attributes.

Pretty much all downstream code currently is structured like this:
uv_connect(connect_req, handle, [](...) {
  uv_write(...);
  // or:
  uv_read_start(...);
});

That won't work if  the connect req doesn't do anything until the first uv_read_start() or uv_write().

At the moment uv_tcp_connect() calls connect() straight away. The kernel performs the TCP handshake in the background. The connections are ready by the time they're needed.
With your proposal, the connect() call isn't done until the request is sent. That adds latency.


sync with base

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.0 out of 2 committers have signed the CLA.:x: Rocky:x: rocky-pengRocky seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.


Error Registering Routines

Not sure if this is a client library or the Google Assistant Action:
When a user tries to set up a routine the app unexpectedly exits when trying to register the routine with the following message appears in the Google Assistant Action log:

MalformedResponse at expected_inputs[0].possible_intents[0].input_value_data: Not allowed to register updates for Routines for non-preview app

This error does not occur when I have testing enabled but is consistently reproduced on the live version of the app.
I am using the standard syntax to register the routine:
conv.ask(new RegisterUpdate({
intent: `[INTENT_NAME]`,
frequency: `ROUTINES`,
}))

Hi, what locale are you using for your action? It may not be available yet for public distribution for your locale.

I am in en/us

I have the same issue (also en/us). It's working in test mode, but when deploying to the alpha channel the error mentioned above appears in the logs. However, it's possible to add routines with the "Add" button on the action page even when using the alpha channel.

That is a perfect description of what I've experienced. Have you been in contact with anyone at Google about this?

No, I just saw the error appearing in the alpha channel and this issue is the only result that comes up when googling the error message from the logs. I'm not sure but I think it worked a couple of days ago when I first pushed it to alpha.


multi-trial NAS notebook error

Describe the issue:
I want to run multi-trial NAS mnist. But I get error.
It always stop in "Connecting IPC pipe...".
And when run nni/examples/notebooks/Retiarii_example_multi-trial_NAS.ipynb have the same problem.
The log are as fallow:
C:\Users\HYC.conda\envs\NNI\python.exe D:/nni-master/examples/nas/multi-trial/mnist/search.py
[2022-04-03 16:21:36] INFO (nni.experiment/MainThread) Creating experiment, Experiment ID: upehs0kw
[2022-04-03 16:21:36] INFO (nni.experiment/MainThread) Connecting IPC pipe...
FATAL: unknown start_mode:
usage: node main.js --port  --mode     <local/remote/pai/kubeflow/frameworkcontroller/aml/adl/hybrid/dlc> --start_mode <new/resume> --experiment_id  --foreground <true/false>
Environment:

NNI version:2.6.1
Training service (local|remote|pai|aml|etc):local
Client OS:Windows
Server OS (for remote mode only):
Python version:3.7
PyTorch/TensorFlow version:1.10.2
Is conda/virtualenv/venv used?:
Is running in Docker?:Pycharm

Have you installed NNI from source? The command line of node.js changed recently, but it hasn't been released yet. So if you are simply running v2.6.1, it shouldn't have any effect on you.
I suggest setting up a completely new virtual environment and try again.


Submission Package bug - diagnosis-sample mapping

Describe the bug
CDS found that some samples had multiple diagnoses associated with them in the diagnosis-sample mapping. They expect a sample to only have one diagnosis.
For example:
in the diagnosis-sample mapping table:

diagnosis_id
sample_id

DG__BS_1GFP3T8N__0
BS_1GFP3T8N

DG__BS_1GFP3T8N__1
BS_1GFP3T8N

DG__BS_1GFP3T8N__2
BS_1GFP3T8N

and in the diagnosis table

diagnosis_id
primary_diagnosis
participant_id

DG__BS_1GFP3T8N__0
Craniopharyngioma
PT_P1F0AHMT

DG__BS_1GFP3T8N__1
High-grade glioma/astrocytoma (WHO grade III/IV)
PT_P1F0AHMT

DG__BS_1GFP3T8N__2
Low-grade glioma/astrocytoma (WHO grade I/II)
PT_P1F0AHMT

Is this expected and true?
Expected behavior
from the cds team:

If this is expected (e.g. because of heterogeneity in the tumor), would it be possible to modify the sample_ids so that there could be 1:1 mapping of sample ID : diagnosis ID?
If the participant_age_at_collection and the anatomic_site of a set of samples was the same, but they each had a unique diagnosis, could a secondary user infer that the tumor was heterogenous for tumor grade or type?

Version ID
0.9.0
Effected file(s)

[ ] sample
[ ] participant
[X] diagnosis
[X] diagnosis_sample_mapping
[ ] file
[ ] file_sample_participant_map
[ ] genomic_info

In the diagnosis-sample mapping table in the dataservice, there's only one diagnosis for the sample reported here:

"uuid"
"created_at"
"modified_at"
"diagnosis_id"
"biospecimen_id"
"kf_id"
"visible"
"external_id"

"d6f341b1-181c-4c16-8c03-fe67fbf89d91"
"2022-11-14 19:53:36.137852"
"2022-11-14 19:53:36.137858"
"DG_0AVDZAEV"
"BS_1GFP3T8N"
"BD_GN55SCK8"
1
"1104392-PT_P1F0AHMT-High-grade glioma/astrocytoma (WHO grade III/IV)-6432"

likeiwse, in the histologies file, there is only the mapping bewtween this sample and High-grade glioma/astrocytoma (WHO grade III/IV)

I've pinned down where this is happening and can confirm that this is a bug in assigning diagnoses.
One of the things we account for is diagnoses that have multiple, semicolon ; delimited, diagnoses inside them. in splitting these diagnoses and then joining them back to the larger diagnoses table here,  split diagnoses are assigned to samples and participant based on table index.
This caused the issue here because some diagnoses, before this splitting operation, had the same table index. So, when the splitting happened and then was joined to the table on index, some diagnoses that should not have been joined to a split diagnosis, were.
The fix for this is to reset the index of the diagnosis table before any joining operations.


Swipe/drag functionality still present even if “unslick” slick-slider at a given breakpoint is used.

I want to destroy the complete functionality of my slick-slider starting at a given breakpoint. My current solution does work - but the drag/swipe functionality is still present. Is there a way to completely remove the functionality or is this a bug?
var slickSettings = {
  mobileFirst: true,
  infinite: false,
  slidesToShow: 2,
  focusOnSelect: true,
  responsive: [
          {
            breakpoint: 520,
            settings: {
              slidesToShow: 3
            }
          },
          {
            breakpoint: 980,
            settings: 'unslick'
          }]
};
$('#slick').slick(slickSettings);

@nulleinssoftwaresolutions How about setting the option draggable: false at the given breakpoint?


Source code origin question

Hi Rinck,
I encountered the same code, at least in its initial form, released in the same year but under the GPL3 license - https://github.com/hvanderlaan/ubuntu-unattended
The only trace to your work is a comment in the script "# copy the netson seed file to the iso", while the seed file is named differently. Wondering what is the netson seed, I found your repository. It looks like your repository was the origin of the hvanderlaan repository but I do not see any credits in his repository... Can you please comment?
Thanks,
Michael

Hi Michael,
the source is indeed mine originally (excluding all the great pull requests I have received and merged over the years) so a reference to this repository would seem like the right thing to do for @hvanderlaan .
As for the seed file you are referring to, this is https://github.com/netson/ubuntu-unattended/blob/master/netson.seed and is a file which contains all the answers to the questions asked during install.
Hope that helps!
Regards,
Rinck


Open-weight model release?

Thanks for your nice work.
Do you have plans to release any of the finetuned Llama2-70B models? We are interested in trying them out on other tasks not covered in the paper, but we do not have the computational resources to reproduce the finetuning runs ourselves.

@daphnei Thank you so much for reaching out! May I ask what specific Llama2-70B model you are referring to? Could you share me the name of the model as well as which paper it is from. Thanks!!


Accessing to object field does not prevent from Error - TS6133 error (declared but its value is never read)

TypeScript Version:  2.6.2 and 2.7.0-dev.20171221
Code
let myComponent: MyComponent;
...
myComponent = TestBed.createComponent(MyComponent).componentInstance;
...
myComponent.detectChanges();

Expected behavior:
No errors
Actual behavior:
error TS6133: 'myComponent' is declared but its value is never read.

I can't reproduce that error with just that code, could you provide a complete example that fails on its own?

Thank you for the quick response.
It was my fault, sorry for disturbing.
During to reproducing this error by creating a short Plunk I found a bug in my code relates to this issue. So it was my mistake.
Thanks.


About improving texture resolution

Hi, which parameter should I change if I want to increase the resolution of the generated texture?
Or is there any other way to improve the resolution and quality of the final textured 3D models?
Thanks!

Hi,
Thanks for your interest in our work.
We've added uv_res as an argument parameter when running our code. The default value is set to 512, but you can adjust it to 1024 or other resolutions. It will work in arbitrary resolutions, but you may need to adjust some U-Net layer configurations if the results are not good. Also, you'll need more computational resource (GPU memory) to run our code in higher resolution.
Here is the argument option for uv_res:
https://github.com/postech-ami/Paint-it/blob/d7494e6660f2964aa03956d81505b07787260ccb/paint_it.py#L59
and this will affect two parts of our code:
https://github.com/postech-ami/Paint-it/blob/d7494e6660f2964aa03956d81505b07787260ccb/paint_it.py#L144
and
https://github.com/postech-ami/Paint-it/blob/d7494e6660f2964aa03956d81505b07787260ccb/paint_it.py#L166
Hope this answers your question.

Please reopen this issue if you need more help regarding this.


Feature✨- User Profile eg. /adamcogan

As a logged in user
I should be able to see my profile
So that I can see my activity

History (1 point): view the rules I have viewed
Likes (5 points): view the rules I have liked and disliked
Read (5 points): view the rules I have read
Comments (5 points): view the rules I have commented on
Bookmarks (1 point): view the rules I have bookmarked (Note: Bookmarks are just a type of Tag)
Other Tags (1 point): view the custom tags
My Edits (10 points): New and edited rules I have made
Gamification: for the time being a simple rating based on points for the above

-a
www.adamcogan.com
AB#59360

To: @adamcogan
cc: @christianmorfordwaitessw
Hi Adam,
This issue was split into 2 seperate issues.
User Profiles - #233
Gamification - #232
-Brady


Run Nodejs and postgres on same server

This will increase security since we don't need to add credentials in this case.

See installation notes


Implementation of a custom grid for TikZPlot class from reporting module

The goal of this issue is to implement an attributes that control the size of the grid and the gap between subplots

Done


Clipboard copy allow paste with styles and allow paste between multiple instances of editor in Android and IOS

Is there an existing issue for this?

[X] I have searched the existing issues

Use case
I don't have a solution, in an old version I made some random modifications that worked
Proposal
When copying text that has a style, paste the text with the style and not just the text without a style, do this with the clipboard to make it possible to copy between instances of flutter quill

I don't think it is in scope of support


Moved docs about publishing a release to Wiki

Since the previous location is not reachable anymore, this is the correct one.

Codecov Report

Merging #1786 into canary will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           canary   #1786   +/-   ##
======================================
  Coverage    78.7%   78.7%
======================================
  Files           6       6
  Lines         263     263
======================================
  Hits          207     207
  Misses         56      56

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 de3b1c8...798fbfe. Read the comment docs.


Are BBS dependencies strictly required?

Recently reworking integration tests in the resolver plugins that pull from the main branch, I ran into the following error:
Traceback (most recent call last):
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aries_cloudagent/__main__.py", line 74, in <module>
    main(sys.argv)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aries_cloudagent/__main__.py", line 71, in main
    run(args)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aries_cloudagent/__main__.py", line 64, in run
    run_command(command, args)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aries_cloudagent/commands/__init__.py", line 36, in run_command
    module = load_command(command) or load_command("help")
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aries_cloudagent/commands/__init__.py", line 31, in load_command
    return import_module(module_path)
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/importlib/__init__.py", line 126, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 994, in _gcd_import
  File "<frozen importlib._bootstrap>", line 971, in _find_and_load
  File "<frozen importlib._bootstrap>", line 955, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 665, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 678, in exec_module
  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aries_cloudagent/commands/start.py", line 16, in <module>
    from ..core.conductor import Conductor
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aries_cloudagent/core/conductor.py", line 17, in <module>
    from ..config.default_context import ContextBuilder
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aries_cloudagent/config/default_context.py", line 16, in <module>
    from ..ledger.indy import IndySdkLedgerPool, IndySdkLedgerPoolProvider
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aries_cloudagent/ledger/indy.py", line 29, in <module>
    from ..wallet.indy import IndySdkWallet
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aries_cloudagent/wallet/indy.py", line 20, in <module>
    from ..did.did_key import DIDKey
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aries_cloudagent/did/did_key.py", line 7, in <module>
    from ..vc.ld_proofs.constants import DID_V1_CONTEXT_URL
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aries_cloudagent/vc/ld_proofs/__init__.py", line 1, in <module>
    from .ld_proofs import sign, verify, derive
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aries_cloudagent/vc/ld_proofs/ld_proofs.py", line 7, in <module>
    from .ProofSet import ProofSet
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aries_cloudagent/vc/ld_proofs/ProofSet.py", line 10, in <module>
    from .purposes.ProofPurpose import ProofPurpose
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aries_cloudagent/vc/ld_proofs/purposes/__init__.py", line 1, in <module>
    from .ProofPurpose import ProofPurpose
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aries_cloudagent/vc/ld_proofs/purposes/ProofPurpose.py", line 8, in <module>
    from ..suites import LinkedDataProof
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aries_cloudagent/vc/ld_proofs/suites/__init__.py", line 6, in <module>
    from .BbsBlsSignatureProof2020 import BbsBlsSignatureProof2020
  File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aries_cloudagent/vc/ld_proofs/suites/BbsBlsSignatureProof2020.py", line 7, in <module>
    from ursa_bbs_signatures import (
ModuleNotFoundError: No module named 'ursa_bbs_signatures'

It would seem that installing requirements from requirements.bbs.txt is required; is this intentional?
To reproduce, the following docker file may be used:
FROM bcgovimages/von-image:py36-1.15-1

RUN pip install git+https://github.com/hyperledger/aries-cloudagent-python@main

ENTRYPOINT ["/bin/bash", "-c", "aca-py \"$@\"", "--"]

I then built and ran the container with:
$ docker build -t acapy-test .
$ docker run --rm -it acapy-test start -it http <IP_ADDRESS> 3000 -ot http -e http://localhost:3000 --no-ledger

cc @TimoGlastra

... or pip install aries-cloudagent[indy, bbs]@git+https://github.com/hyperledger/aries-cloudagent-python@main
(not sure of the exact syntax, but the "extras" need to be specified)

It is definitely the intention it can be run without BBS, therefore the separate requirements.bbs.txt. Will look into this today


docs: update pod-gateway documentation supporting multiple DNS servers

Description of the change
Update the documentation with multiple DNS servers for the pod-gateway chart (feature implemented with https://github.com/angelnu/gateway-admision-controller/pull/144).
Checklist

[X] Title of the PR conforms to the Conventional Commits standard.
[X] Scope of the of the PR title contains the chart name.
[x] Chart version in Chart.yaml has been bumped according to Semantic Versioning.
[x] Chart artifacthub.io/changes changelog annotation has been updated in Chart.yaml. See Artifact Hub documentation for more info.
[X] Variables have been documented in the values.yaml file.

Thanks @zebrapurring


Balance of tokens in /account/balance

Atm the /balance/account only shows balance of Mina, and tokens are not included. That seems to be the case for both MinaMesh and Rosetta Ocaml. I think it would be fairly easy to add token balance support for historical lookup modifying the query maybe_account_balance_info.sql to:
SELECT DISTINCT ON (t.value)
  b.height,
  b.global_slot_since_genesis AS block_global_slot_since_genesis,
  balance,
  nonce,
  timing_id,
  t.value
FROM
  blocks b
  INNER JOIN accounts_accessed ac ON ac.block_id=b.id
  INNER JOIN account_identifiers ai ON ai.id=ac.account_identifier_id
  INNER JOIN public_keys pks ON ai.public_key_id=pks.id
  INNER JOIN tokens t ON ai.token_id=t.id
WHERE
  pks.value=$1
  AND b.height<=$2
  AND b.chain_status='canonical'
  -- AND t.value=$3
ORDER BY
  t.value, b.height DESC

which should give each token balance for the given account per row.
For the frontier balance lookup, the graphql would probably be something like this:
query QueryAllBalances($publicKey: PublicKey!) {
  accounts(publicKey: $publicKey) {
    tokenId
    nonce
    balance {
      total
      liquid
      locked
    }
  }
}

This a good candidate for future work. AFAIK no user complained about missing this feature, but it's good to have it planned.


ShouldAllBeEquivalentTo a single object instead of IEnumerable

An overload of ShouldAllBeEquivalentTo method asserting all elements of given enumerable are equivalent to given object would be awsome.
public static void ShouldAllBeEquivalentTo<T>(this IEnumerable<T> subject, T expectation, Func<EquivalencyAssertionOptions<T>, EquivalencyAssertionOptions<T>> config, string because = "", params object[] reasonArgs)
{
    // ..
}

I'm not aware of a better way using Fluent Assertions, this is how I currently implement the assertion using ShouldAllBeEquivalentTo;
Model expectedModel = new Model { One = 1, Two = "2", Three = 3, Four = 4M };
IEnumerable<Model> expectedModels = Enumerable.Repeat(expectedModel, 2);

models.ShouldAllBeEquivalentTo(expectedModels);

Thanks for the suggestion, but IMO it's a pretty rare situation. Shouldn't be difficult to create your own extension method for that. Unless you submit a PR of course ;-)

Hey @dennisdoomen. Thanks for reply. I ended up creating my own extension. I agree that it's a rare situation, I just been into one of those rares tho.
Planning to work for a PR in the following days.


[Identity] Many more sugesstions

Original issue: https://github.com/Draylar/identity/issues/138

I like the patrol captain one, it would be nice if as a captain you could make illagers follow you

Just to keep track of this:
Still missing are:

Instead of normal food, zombies should recover hunger points by dealing melee attacks to non-undead mobs, with 1 hunger point being filled for every damage point done
Illager identities can equip the ominous banner to become a patrol captain, when the R key is pressed the horn sound plays, and patrol members are spawned in to ally the player
Nocturnal & undead mobs can only sleep during the day


chatflow network deployment results in error

SDK installed with the latest binary for macOS
SDK version: JSX Version: v10.5rc1-45-g753dcb54

The following error occured: {"error":"invalid account address: horizon error: \"Resource Missing\" - check horizon.Error.Problem for more information"}

Earlier today I also received a similar error message with included this "horizon error" message when someone was using the kosmos shell to create his farm.  He sent a screen shot:

The executed code was:
j.clients.explorer.default_addr_set('explorer.grid.tf')
explorer = j.clients.explorer.explorer
farm = explorer.farms.new()
farm.name = 'dec_hk_t1'
farm.threebot_id = j.me.tid
wallet_address = farm.wallet_addresses.new()
wallet_address.asset = 'TFT'
wallet_address.address = '0150e156f3650986ecbbf6013c3c7d81ada901d308d031a73fe1a482a07e11682e6f0cf2963913'
farm.email =<EMAIL_ADDRESS>farm_id = explorer.farms.register(farm)
print(farm_id)

I have asked him to sent me the output of j.me but did not receive an answer.

wallet_address.address = '0150e156f3650986ecbbf6013c3c7d81ada901d308d031a73fe1a482a07e11682e6f0cf2963913'
This is a tfchain address, we don't support that anymore. We are migrated to stellar now so this should be a valid stellar address.

Okay - clear - we should have communicated that....  This is a farmer that had trouble over the last coupe of days getting 3sdk installed - now it's working and he cannot register - has to have a stellar wallet....  Okay - I'll let him know.


Replace Gulp with Webpack

I have replaced the functionality of Gulp with Webpack. I haven't integrated babel yet but it will be needed when we start on React. I can do this in a separate PR to begin our react branch or either @artitudinale1 or @silver_wedding can if you want?
Here are the tasks:
npm start = run app with hot loading (i.e. auto-refresh when you change files)
npm run build = compile the app for production into the dist folder
npm run serve = serve the compiled version of the app (to preview before deploy)
npm run deploy = compiles the app to dist and deploys it to gh-pages on the origin remote
npm run deploy:prod = as above but on the upstream remote
There is also a npm run gh-pages but it would be better to use the deploy task to make sure the compiled app is up-to-date

Sorry meant to do this on the main repo lol


[Angular-NgRx-SCSS] Audit app for any architectural improvements and features that are incomplete

Acceptance
As either a write up in Google Docs or as comments on this issue, please provide us with:

Any bugs you find clicking through the app
Any architectural issues you see with components, their styles, or general cleanup required

Notes
See #489 for a good example

Project setup

README doesn't mention having to run build:libs before the app is ready to run. Ideally it should be included as a prestart script

App issues

[ ] the main page doesn't have any loading indicator (like loading skeleton on angular-apollo-tailwind)
[ ] general note - there are no loading indicators across the whole app
[ ] same as https://github.com/thisdot/starter.dev-github-showcases/issues/489#issuecomment-1192909847

on http://localhost:4200/tvanantwerp page the link to the website is treated as a local link rather than a global link

On the repo page (eg. http://localhost:4200/thisdot/starter.dev):

[ ] issues tab doesn't show proper data

[ ] refreshing the issues/pull requests page breaks the page navigation

clicking on a different tab navigates to eg. http://localhost:4200/issues instead of http://localhost:4200/thisdot/starter.dev/issues

note: it works properly before refreshing

[ ] routing paths should follow the same convention as original GH eg. http://localhost:4200/thisdot/starter.dev/pull-requests should be http://localhost:4200/thisdot/starter.dev/pulls

[ ] navigation on pull requests page doesn't work (no new pages are shown) - couldn't test issues as the whole tab is not working atm

[ ] in tree view when navigating the tree the root README is still shown.

[ ] It should not be shown if a given directory doesn't contain a readme file
[ ] if a subdirectory contains a README file then this one should be shown instead of the root one

[ ] label and sort dropdowns don't show any options to choose

[ ] clicking on the x on the label and sort dropdowns doesn't close the dropdown (but it should)
[ ] clicking on the Readme button in the about section should scroll the page to the README section

Code improvement ideas

[ ] app state for the most part doesn't need to be globally defined. Each sub-feature should be able to load necessary data for a given sub-page eg. repository should probably be added to a state via RepositoryModule

[ ] in some cases an app level state is beneficial as it is probably a good idea to load the authenticated user from the top of the app

[ ] IMO we should split profile and authenticated user into separate state slices. Authenticated user should be available always and currently when refreshing the profile page it is not loaded
[ ] the root src folder contains a mix of feature and technical directories. IMO it would be better to keep the root level directory structure focused on features only and split into technical directories ie. state, services, components further down the structure

probably the routing can be a source of truth for how we split the feature directories
any shared components can be (optionally) extracted into a library, but we can also think of shared as the same level as any other feature

[ ]the routing structure will probably benefit from a bit of restructuring.

my suggested structure

/ root - layout component (top nav + content below) - load authenticated user
  - /:owner (user module) - load profile
    - /:repo (repository module) - load repo
      - /issues (repo issues component) - load issues
      - /pulls (repo pulls component) - load pulls
      - /code (redirect to ./)
      - / (repo code component) - load tree structure - NOTE: use full path matching in the router configuration
      - / (file explorer module) - I think if we set it as prefix patch matching it should work nicely
        - /tree/:path
        - /blob/:path
    - / (profile component) - NOTE: use full path matching in the router configuration
  - / (top repositories module) - NOTE: use full path matching in the router configuration

Did not get all of these created into new issues, but did make some that were directly related to getting the main app functionality working: #833 , #834, #835.


made label to the left of numerical readout, allowed font resizing

Description
Redesigning Standard Display Item
Changes made:

Label is not positioned to the left of the numerical readout.
Label and Numerical Readout are in the same font size.
Text size is made customizable, range: (10, 30)

N/A
Developer Testing
Here's what I did to test my changes:

Run python launcher.py
Select "Add Item" > "Standard Display Item"

Reviewer Testing

Here's what you should do to quickly validate my changes:

You will see that the label is positioned to the left of the numerical readout.
You can change the font size in the parameters section
The sparkline plot is togglable.

This change is

@BluCodeGH @Lucifersan is the default font size of 25 good, or should it be 10?

Hey, I made the change- the widget now resizes vertically whenever the sparkline plot is hidden/shown. As for the minimum size of the sparkline plot, I think it's to ensure that the plot can be plotted.

When the sparkline is turned off the number appears below the label? Also why are there still 6 significant digits?


Update ls.blur-up.js - Add webP to image types

This small change allows one to have different types low resolution images.
<picture>
    <source
        data-srcset=" ... webp images ..."
        data-lowsrc="low_res.webp"  <---
        type="image/webp"/>

    <source
        data-srcset=" ... jpeg images ..."
        data-lowsrc="low_res.jpg"  <---
        type="image/jpeg"/>

    <img class="lazyload" data-sizes="auto" />
</picture>

Sadly this won't cut it. Because this would mean that webp not supporting browser would also load webp.

True. My fault. Tested with an old browser now. Sorry for the inconvenience.
Is there a way to acomplish this
'

Yes, I see two possibilities:

instead of building a blur up img structure, build a blur up ´picture`.
make the supported types regexp public and let it to the dev to do some feature detection or browser sniffing so he can extend it.

Thanky you very much for the suggestions. Option 1) seems fine.
Will close this thread and delete the branch.


Use latest patch versions for testing and default version

This is a followup PR to what was discussed at https://github.com/python-cmake-buildsystem/python-cmake-buildsystem/pull/306#issuecomment-1015978067.
This updates the ci builds to use the latest patch release of each python minor release and also updates the default built to the latest patch release of the latest python minor version currently supported (3.9).

@jcfr The protected branch rules seem to specify that runs of Python 3.8.5 are required to pass prior to merging and same with python 3.9.10. The ci is being updated here to trigger runs of Python 3.8.12 and Python 3.9.10 instead, so updating of the required checks will likely need to be updated each time the latest version of the patch release to test is updated. This will be one update step to consider each time this happens.

All set. Required checks have been updated.

so updating of the required checks will likely need to be updated each time the latest version of the patch release to test is
updated. This will be one update step to consider each time this happens.

Reviewing https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions , I couldn't find a way to specify these outside of the project settings.
Something that could be listed in the maintainers guide ....

We could also remove the status check but I would rather being explicit and support the auto-merge feature .... https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request#about-auto-merge


Profile for nomeata

I'd like to have my profile on ghuser.io, thanks!

 I'll look into it later today.

fixed :)

LGTM, thanks! :-)


Admin panel work

Help is appreciated.
Currently we have the following design:

The task is to port https://demo.bitcartcc.com design or similar to vuetify.
Screen of old admin:

Card texts might be fixed to be more fit in this design in both dark and light modes.
After finishing design, actual functionality should be added, loading data from Backend API.

Admin panel has evolved a lot, it is now better than the old one. But any ideas or help in improving it is welcome.


Update to testjob_template parameters' comments

Fixes https://github.com/AdoptOpenJDK/openjdk-tests/issues/2546

Hello @smlambert, I have created a PR for this task. Kindly assist with reviewing for a possible merge or update.
Thanks.

I have signed the ECA. Thanks

Hello @smlambert, please this PR has not yet been merged.

I am well aware @Martins-O-U - PRs in this repo require 2 reviewers.  I am waiting on a 2nd review before it is merged.  You can still count it towards your contributions (as per the note in the outreachy slack channel).


GRG - Can't create GRG in Portal 10.3.1 with SAML authentication

Widget
GRG
Version of widget
Pre Release
Bug or Enhancement
Bug
Repo Steps or Enhancement details
When I was testing this in the disconnected lab in holistic this afternoon, I ran into an error where I was unable to actually create the GRG. I was able to use the config UI that @kgonzago wrapped up today, and I was able to draw the outline rectangles using the "create GRG by area" workflow. However, I was unable to actually create the GRG, the button itself didn't appear to work. When I dug into Fiddler to look at the error, I received this message below (click on the picture to enhance):

I'm not sure what "input unit vs spatial reference unit" or "linear vs angular" specifically means, or whether it is a problem with the widget or a problem with the basemap we were using in this particular portal, but I wanted to post this issue because it seems to be a javascript issue and the basemap we were using was one of the default ones in portal (sample world cities), which uses web mercator.
@lfunkhouser FYI

Update: when I run the Create GRG By Point workflow, I'm able to click on the create GRG button, see the Publish GRG to Portal button, and publish the GRG to my portal, however the graphic doesn't appear in the widget, nor does the feature service appear in the web map in portal once it has been published. My guess here is that the starting point when you are creating a GRG by Point is persisting, but the graphic itself doesn't appear.

I've been able to narrow down this issue to an issue with configuring Web AppBuilder in a disconnected environment, not with the widget itself- closing out issue.


Service Fabric Managed Clusters - API version 2024-11-01-preview

ARM (Control Plane) API Specification Update Pull Request

[!TIP]
Overwhelmed by all this guidance? See the Getting help section at the bottom of this PR description.

PR review workflow diagram
Please understand this diagram before proceeding. It explains how to get your PR approved & merged.

Purpose of this PR
What's the purpose of this PR? Check the specific option that applies. This is mandatory!

[ ] New resource provider.
[x] New API version for an existing resource provider. (If API spec is not defined in TypeSpec, the PR should have been created in adherence to OpenAPI specs PR creation guidance).
[ ] Update existing version for a new feature. (This is applicable only when you are revising a private preview API version.)
[ ] Update existing version to fix OpenAPI spec quality issues in S360.
[ ] Convert existing OpenAPI spec to TypeSpec spec (do not combine this with implementing changes for a new API version).
[ ] Other, please clarify:

edit this with your clarification

Due diligence checklist
To merge this PR, you must go through the following checklist and confirm you understood
and followed the instructions by checking all the boxes:

[x] I confirm this PR is modifying Azure Resource Manager (ARM) related specifications, and not data plane related specifications.
[x] I have reviewed following Resource Provider guidelines, including
ARM resource provider contract and
REST guidelines (estimated time: 4 hours).
I understand this is required before I can proceed to the diagram Step 2, "ARM API changes review", for this PR.

Additional information

 Viewing API changes
For convenient view of the API changes made by this PR, refer to the URLs provided in the table
in the Generated ApiView comment added to this PR. You can use ApiView to show API versions diff.

Suppressing failures
If one or multiple validation error/warning suppression(s) is detected in your PR, please follow the
suppressions guide to get approval.

Getting help

First, please carefully read through this PR description, from top to bottom. Please fill out the Purpose of this PR and Due diligence checklist.
If you don't have permissions to remove or add labels to the PR, request write access per aka.ms/azsdk/access#request-access-to-rest-api-or-sdk-repositories
To understand what you must do next to merge this PR, see the Next Steps to Merge comment. It will appear within few minutes of submitting this PR and will continue to be up-to-date with current PR state.
For guidance on fixing this PR CI check failures, see the hyperlinks provided in given failure
and https://aka.ms/ci-fix.
For help with ARM review (PR workflow diagram Step 2), see https://aka.ms/azsdk/pr-arm-review.
If the PR CI checks appear to be stuck in queued state, please add a comment with contents /azp run.
This should result in a new comment denoting a PR validation pipeline has started and the checks should be updated after few minutes.
If the help provided by the previous points is not enough, post to https://aka.ms/azsdk/support/specreview-channel and link to this PR.

API change check
APIView has identified API level changes in this PR and created following API reviews.
Microsoft.ServiceFabric

Please fix the errors here - https://github.com/Azure/azure-rest-api-specs/pull/31678/checks?check_run_id=33550207799

intake for breaking change approval: https://msazure.visualstudio.com/One/_workitems/edit/30463370
this was already approved in the previous preview api version:
swagger pr: https://github.com/Azure/azure-rest-api-specs/pull/30941
previous intake: https://msazure.visualstudio.com/One/_workitems/edit/29878519

Breaking changes previously reviewed and approved in #30941


Further specify how to publish website

Coverage remained the same at 90.427% when pulling b9184f7b06073172ac42b21ee961bdfad0ef9f88 on torkelrogstad:2019-05-15-website-publishing into 37c8018e8e37b3461384f98638672fc6eafe43cb on bitcoin-s:master.


azure-cosmosdb-table 1.0.6 needs to be deprecated

Track 2 SDKs for table storage have been released and we want to encourage customers to use the new packages. To that end, all existing track 1 packages need to be deprecated.
azure-cosmosdb-table 1.0.6 needs to be deprecated as per our guidelines for GA releases.

Your guidelines for GA releases link isn't public.  If this is getting deprecated, what is replacing it?
Also your public tutorial docs are still using this package.  https://docs.microsoft.com/en-us/azure/cosmos-db/table/how-to-use-python

Hi Michael, thanks for your comments and for the link to the doc that needs updating. The tables package has been replaced with a newer version. You can read the GA announcement blog post for more details.


Add an alternate set of strong name signed glimpse packages to nuget

The only glimpse packages currently available in nugget are not strong name signed. If someone requires strong name signed assemblies in their project, I believe their options are:

Get a copy of the source and rebuild the desired packages with strong name signing
Download the desired glimpse packages from nuget and use a tool like Brutal Strong Name Signer to sign the assemblies.

Neither option is great. Both are time consuming and have to be repeated for any new version of glimpse.
The ask here is to generate both signed & unsigned assemblies and host both on nuget.
From what I can tell, Glimpse currently depends on the following packages which do not have strong names:

Antlr4.StringTemplate
Tavis.UriTemplates

We'd likely need versions of these dependencies with strong name signatures in order to compile Glimpse.Core.
Alternatively, perhaps the signing can be pushed to the ilmerge stage for Glimpse.Core which might remove the need for its dependencies to be strong name signed? I'm not 100% sure about this alternative.
Btw, the StackExchange.Redis package is an example of a project that does this:

http://www.nuget.org/packages/StackExchange.Redis/
http://www.nuget.org/packages/StackExchange.Redis.StrongName

I'd wish to have signed Glimpse too, but project owners have different point of view: #324, #879

Hi @ryandle,
As I've mentioned in the past, I don't have a problem shipping *.StrongName packages to MyGet. I don't think the update to our default.ps1 script would be that difficult.
Would you like to update it, and we can take your PR?

@nikmd23, the problem is not only Glimpse itself, but I also have to recompile from sources every plugin that I use, because packaged plugin versions depend on unsigned Glimpse.Core.dll. Packages work well until I want to write some extension, like custom security policy - so I need signed Glimpse for my code and unsigned for plugins, or recompile pligins.
Maybe I missed something, but could you point out changes, that solves signing problem anyhow?
I don't want to seem unthankfull, Glimpse is great, I love it, but multiple projects resignig an recompiling is a piece of pain.

@nikmd23 sigh, sorry, I thought I searched for related issues before opening this one but I clearly did not.
The MyGet proposal works for me and I'll try to take a stab at it.
Out of curiosity, why not put it on nuget.org? From reading the previous discussions on this topic, it looks like the primary concern is glimpse extensions taking a dependency on the strong named version (and the headaches that would come with that.) Is hosting it on MyGet a way to discourage this behavior, or is there more to it that I'm missing?

@ryandle, yes, the idea behind hosting it on NuGet is to discourage this becoming the default behavior, while still offering a (partial?) solution for people in your shoes.


Cannot add multiple relations to ParseRole

Environment Setup
Parse Server 2.2.2
Steps to reproduce
I'm not 100% sure wether this is a bug or intended behavior, so please correct me if I'm wrong.
I've a huge cloud function to setup my initial roles. At line 386 I add 2 relations to the "customer" role ("admin" role AND "merchant" role).
But when looking at my DB (_Join:roles:_Role collection) after running the function, it seems that only the 1st relation between the "customer" and "admin" role has been set (customerRole.getRoles().add(globAdminRole);) but NOT the 2nd relation between "customer" and "merchant" role (customerRole.getRoles().add(globMerchantRole);)
From what I understand when reading the docs I would assume that if I call the add() function twice it would add both relations.
(sidenote)
I could work around that for now by adding both relations as an array like this:
customerRole.getRoles().add([globAdminRole, globMerchantRole]);

Logs/Trace

Yeah this is an issue with the JS-SDK, use your workaround for now. cc: @andrewimm


Add unit test for remediation with non-ascii data

When a remediation command is printed that manipulates non-ascii but totally valid utf-8 filenames, leapp should not give out any tracebacks upon report generation.
Related-to: OAMG-8629

/rerun

/rerun 1052


Make SMES 2x better

About the PR

Made SMES twice as good, most notably in terms of capacity.
Why / Balance

power goes out pretty much every shift for like 10-15 minutes and that sucks
Technical details

Media

[X] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Breaking changes

Changelog

:cl:

tweak: SMES are now twice as good, meaning Engineering has more time to set up power! Rejoice!

need the #goob as this is in core files


ReferenceError: bYRotation is not defined

I need this npm module in a project and just tried it before using by copying the code provided in the example, my App.js is simple and looks like this: `import React from 'react';
import { StyleSheet, Text, View, TouchableOpacity } from 'react-native';
import CardFlip from 'react-native-card-flip';
export default class App extends React.Component {
render() {
return (

<CardFlip style={styles.cardContainer} ref={(card) => this.card = card} >
<TouchableOpacity style={styles.card} onPress={() => this.card.flip()} >AB
<TouchableOpacity style={styles.card} onPress={() => this.card.flip()} >CD

);
}
}
const styles = StyleSheet.create({
container: {
flex: 1,
backgroundColor: '#fff',
alignItems: 'center',
justifyContent: 'center',
},
});
`
But on simulator it gives the following error:
ReferenceError: bYRotation is not defined
and it marks the following lines:
` });
262 | } else {
263 |   // cardB Y-rotation

264 |   bYRotation = rotation.y.interpolate({
| ^  265 |     inputRange: [0, 50, 100, 150],
266 |     outputRange: ["0deg", "-180deg", "0deg", "180deg"],
267 |     extrapolate: "clamp"`

I am guessing it's some issues with the this module.

I'm having the same issue


fix: empty metadata caused treesitter directives like offset to be ignored

this commit fixes the vim.treesitter.get_node_text from ignoring the offset and possibly other directives like gsub as well.
the reason for this change is that metadata in query:iter_captures was only available if the capture_id is 1 and was reset to an empty table for the captures after that but wasn't replenished and remained empty.
assume that you have a treesitter injection in a rust macro. here's what it would look like
(macro_invocation
(scoped_identifier
path: (identifier) @path (#eq? @path "sqlx")
name: (identifier) @name (#match? @name "^query.*")
)
(token_tree
(raw_string_literal) @injection.content
(#set! injection.language "sql")
(#set! injection.include-children)
)
(#offset! @injection.content 0 3 0 -2)
)
a raw string in rust looks like this r#"select * from "user";"#
in the #offset! directive raw string start and end identifiers (#r" and "#) are offsetted and what remains is the inner sql.
this offset information is set to the metadata for query.get_node_text to use.
however, it's not available when it needs to be used. in query:iter_captures you get @path capture first then you get @name capture and finally @injection.content capture. metadata is only available in @path capture. which is when the capture_id is 1
this commit sets this to an outside variable and makes it always available.
maybe treesitter needs to fix this as a bug. I don't know honestly.
makes https://github.com/jmbuhr/otter.nvim/issues/79 redundant.
probably fixes https://github.com/jmbuhr/otter.nvim/issues/72 and https://github.com/jmbuhr/otter.nvim/issues/37

Good catch, and thank you for your contribution! I think we are close to getting the complete fix.
It looks like the node that has the metadata does not necessarily have id 1. For example, if I take the test.ts example from the other issue:
const vert = glsl`
 void main() {
   gl_Position = vec4(0.0, 0.0, 0.0, 1.0);
 }
`;

const foo = html`

hello

`;

const bar = css`
 .foo {
   color: rgb(0, 0, 0);
 }
`;

const lua = lua`
local foo = "bar"
print(foo)
`;

with :lua require'otter'.activate({'html', 'css', 'lua'}) and print in each loop iteration
    vim.print(id)
    vim.print(name)
    vim.print(maybemetadata)
    vim.print("----")

:messages
3
injection.language
{
  [2] = {
    range = { 0, 18, 4, 0 }
  }
}
----
2
injection.content
{}
----
3
injection.language
{
  [2] = {
    range = { 6, 17, 10, 0 }
  }
}
----
2
injection.content
{}
----

using the metadata any time the table is not empty with
    if next(maybemetadata) ~= nil then
      metadata = maybemetadata
    end

instead of checking the id works for the example, but like you pointed out on reddit may be a problem for cases where it actually has to reset to be empty. Need to check if we have access to those groups of captures that should share the same metadata.

I think we can reset the metadata on id = 1 and keep adding each key from maybemetadata to metadata.

I think I got it, in the nvim docs there is Query:iter_matches() right below iter_caputures. So if we go by matches we should have the captures belonging to the same match in one iteration of the outer loop and the captures in the inner loop of the example in the docs:
        for pattern, match, metadata in cquery:iter_matches(tree:root(), bufnr, first, last) do
          for id, node in pairs(match) do
            local name = query.captures[id]
            -- `node` was captured by the `name` capture in the match

            local node_data = metadata[id] -- Node level metadata

            -- ... use the info here ...
          end
        end

I think every match starts with id=1 and goes on. we can just reset at id = 1. I might be wrong though.

In the example the id with the metadata seems to be 3, followed by the node that needs the data with id 2 :see_no_evil:

  local metadata = {}
  for id, node, maybemetadata in query:iter_captures(root, main_nr) do
    if id == 1 then
      metadata = maybemetadata
    end
    vim.tbl_extend("force", metadata, maybemetadata)

could you add the last line and try that test again?

maybe using the matches properly will also resolve some hacks I have in determine_language, where I'm getting elements from the metadata with a hardcoded 2, which feels brittle.

that does not work, as there is never and id 1 in the example, it starts with 3 :D

well that's odd :D

I think I've fixed it. not much by editing existing code in otter.nvim but rather rewriting treesitter's iter_captures method.
local function iter_captures(node, source, query)
  if type(source) == "number" and source == 0 then
    source = api.nvim_get_current_buf()
  end

  local raw_iter = node:_rawquery(query.query, true, 0, -1)
  local clean_metadata = false
  local metadata = {}
  local function iter(end_line)
    local capture, captured_node, match = raw_iter()
    if clean_metadata then
      metadata = {}
      clean_metadata = false
    end

    if match ~= nil then
      local active = query:match_preds(match, match.pattern, source)
      match.active = active
      if not active then
        return iter(end_line) -- tail call: try next match
      end
      query:apply_directives(match, match.pattern, source, metadata)
    else
      -- clean metadata for the next match, if there is one.
      -- but do it the next loop, so that we can still use it
      clean_metadata = true
    end
    return capture, captured_node, metadata
  end
  return iter
end

I put the metadata outside of the iter function and only cleaned it after match was nil. but the function still needs to return the metadata so I do it on the next loop.
and here's how it can be used
  for id, node, metadata in iter_captures(root, main_nr, query) do

it's not a query method but a function that takes query as input.
tested it with that ts file you've given and it creates quoteless files without the need to strip the quote characters.

very nice. I have also confirmed that it still works for the existing cases. Is this ready to be merged from your side?

I'd say yes, I'm okay with it if you're okay with it. It's been working in embedded sql in rust pretty good so far. Is there any changes you want me to do?

ok, I'll merge then and maybe refactor some code later to be less reliant on treesitter internals under the assumption that those are less stable under future releases than the public api.

oh and can you send me an example rust file with the embeds working, such that I can also validate it when I do a refactor?

well rust doesn't really have an official sql embed but I added this injection:
;queries/rust/injections.scm

(macro_invocation
 (scoped_identifier
    path: (identifier) @path (#eq? @path "sqlx")
    name: (identifier) @name (#match? @name "^query.*")
 )
 (token_tree
   (raw_string_literal) @injection.content
 )
 (#set! injection.language "sql")
 (#set! injection.include-children)
 (#offset! @injection.content 0 3 0 -2)
)

and although this is not a real rust file, treesitter is happy enough for otter to work:(provided that you set sqls with a database table named "user")
fn main()
    let username = "otter"
    let email = "nvim"
    let password_hash = "pw"

    let user_id = sqlx::query_scalar!(
        r#"
        INSERT INTO "user" (username, email, password_hash)
            VALUES ($1, $2, $3)
        RETURNING
            user_id;
        "#,
        username,
        email,
        password_hash
    )
}

but I think you can write a unit test that just sees if the input and output is as expected, output being the file with just the embedded part and rest just white space.


nitrogen8mm-dwe: not expanding the data partition to its fullest extend, stuck in 196M

[ereski] This issue has attached support thread https://jel.ly.fish/#/6c67e5b0-519e-465e-baf3-0c3678075c96

This issue will be fixed by https://github.com/balena-os/balena-fsl-arm/pull/85
Issue is present only if a balena image is used with a vanilla bootloader, an u-boot without resin_ environment.

Fixed in latest release


az login fails if password contains ")"

Describe the bug
Test 1
If you run az login with a password that contains closing parenthesis ), it will throw the following error.
az login --service-principal -u "<app id>" -p ")" --tenant "<tenant id>"

Error
--tenant was unexpected at this time.

Test 2
If you run with a password containing a closing parenthesis that is padded with other characters, you get an error that whatever is after the closing parenthesis is "unexpected at this time":
az login --service-principal -u "<app id>" -p  "1ab)2ab" --tenant "<tenant id>"

Error
2ab was unexpected at this time.

Note
I only tested this using service principal since I can't test this on username and password workflow, but it might be affected as well.
Related command
az login --service-principal -u "<app id>" -p ")" --tenant "<tenant id>"

Errors
az : --tenant was unexpected at this time.

Issue script & Debug output
No useful debug output.
Expected behavior
Should not throw an error if ) character is in the password.
Environment Summary

azure-cli                         2.58.0 *

core                              2.58.0 *
telemetry                          1.1.0

Extensions:
azure-devops                       1.0.0

Dependencies:
msal                              1.26.0
azure-mgmt-resource             23.1.0b2

Python location 'C:\Program Files\Microsoft SDKs\Azure\CLI2\python.exe'
Extensions directory 'C:\Program Files\Common Files\AzureCliExtensionDirectory'

Python (Windows) 3.11.7 (tags/v3.11.7:fa7a6f2, Dec  4 2023, 19:24:49) [MSC v.1937 64 bit (AMD64)]

Legal docs and information: aka.ms/AzureCliLegal

Additional context
No response

Thank you for opening this issue, we will look into it.

Same issue as https://github.com/Azure/azure-cli/issues/25173. Seems like a PowerShell issue.

See https://github.com/Azure/azure-cli/issues/15529


Code completion for magic commands.

This PR enables code completion for magic commands, using https://github.com/microsoft/jupyter-core/pull/77. This PR is marked as draft until https://github.com/microsoft/jupyter-core/pull/77 completes and a new Microsoft.Jupyter.Core release is pushed to nuget.org.

Marking as ready now that the Microsoft.Jupyter.Core package reference includes https://github.com/microsoft/jupyter-core/pull/77, and now that unit tests have been added.


[vite:react-babel] Duplicate plugin/preset detected.

Describe the bug
I'm trying to start up my first vite-react project with follow config:
import { defineConfig } from 'vite';
import react from '@vitejs/plugin-react';

// https://vitejs.dev/config/
export default defineConfig({
    plugins: [
        react({
            babel: {
                plugins: [['@babel/plugin-transform-react-jsx', {}]],
            },
        }),
    ],
});

But I got this error report:
[vite:react-babel] Duplicate plugin/preset detected.
If you'd like to use two separate instances of a plugin,
they need separate names, e.g.

  plugins: [
    ['some-plugin', {}],
    ['some-plugin', {}, 'some unique name'],
  ]

Duplicates detected are:
...

and my configuration works well in vite@4, the error only happenned in vite@3
Reproduction
see reproduce steps
Steps to reproduce

Create vite project by using following command

npm create vite@3 my-vite-project --template react

modify vite.config.js

import { defineConfig } from 'vite';
import react from '@vitejs/plugin-react';

// https://vitejs.dev/config/
export default defineConfig({
    plugins: [
        react({
            babel: {
                plugins: [['@babel/plugin-transform-react-jsx', {}]],
            },
        }),
    ],
});

then run build

npm i
npm run build

System Info
vite/3.2.5 win32-x64 node-v14.18.0
@vitejs/plugin-react: ^2.2.0 => 2.2.0

Used Package Manager
npm
Logs
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

Why do you need to add that babel plugin? It's already handled by the @vitejs/plugin-react

Why do you need to add that babel plugin? It's already handled by the @vitejs/plugin-react

I want to use jsx syntax in .js file that vitejs doesn't support by default.

Closing as I don't think this is a bug and it's responded here as well.
https://github.com/vitejs/vite-plugin-react/discussions/72#discussion-4701576