YAML - How to test YAML locally before commit

Have you tried trouble shooting?
Trouble shooting doc
Yes - I tried reading the docs available, getting started guides, looking through the logs with debug enabled, but I did not see a way to run, or rerun a yaml build at the command line.
Agent Version and Platform
Version of your agent? 2.102.0/2.100.1/...
image: microsoft/vsts-agent:ubuntu-16.04-docker-17.06.0-ce-standard
OS of the machine running the agent? OSX/Windows/Linux/...
Linux docker image:
image: microsoft/vsts-agent:ubuntu-16.04-docker-17.06.0-ce-standard
VSTS Type and Version
VisualStudio.com
If VisualStudio.com, what is your account name? https://metabolondev.visualstudio.com
What's not working?
Unable to find out how to test YAML files locally before committing.
Agent and Worker's Diagnostic Logs
n/a

@jhgoodwin what kind of testing you are trying to do? just validate syntax or verify the function?

We have a few stories on our backlog to address these scenarios starting with linting, then preview what if, and then finally a private buddy build you can run before committing the yaml (run locally but cooperates with the service - not offline).
I'm going to close since this is a multi-stage set of work and it's not an issue.  rest assured it's something we want to and will solve.  It's just not ready yet.

@bryanmacfarlane what feed is most likely to have the updates related to this work announced? I'd be glad to try it when it's available.

This increases the development cycle and prevents fast experimental changes to Build pipelines. :|
The issue is closed as "multi-stage set of work" but not a single related issue was linked to this one (so that users can subscribe). :(

I have to say, it would be  game changing  if Azure Pipeline does provide such feature.
A use case is that sometimes it's not the ymal file that has issues, but still the CI or CD gets failed. Just like this issue on Vuejs:
https://github.com/vuejs/vue-cli/issues/2404
This issue has been bothering me and many others for a very long time, but nobody can give a proper answer because sometimes it's ymal file, sometimes it's the OS environment, and sometimes it's vuejs.
So, a more important issue is whether we can test the whole CI or CD process locally.  We cannot just commit something and hope this time it would work. That's painful.

@bryanmacfarlane Perhaps I'm just failing to do something simple, but how do I find the docs you are referring to? I checked in that folder, but after a long time, there are no changes. I tried searching for branches with yaml in the name, but still not seeing anything. From what you are saying, it seems like I must be missing something obvious.

Since that early post, yaml stuff was moved to here:
https://github.com/Microsoft/azure-pipelines-yaml/tree/master/design
The documentation since then was integrated into the official docs, e.g.
https://docs.microsoft.com/en-us/azure/devops/pipelines/process/phases?view=azure-devops&tabs=yaml

Now that YAML pipelines have been made the default, how about giving us the opportunity to test them locally.  The "create, run, inevitable failure, hand hack, fail, try to guess what the issue is, hand hack fail" cycle is much slower than the previous, very easy to understand GUI driven system.

Makes me want to keep my career from getting sucked into more of that stuff

Note that test before commit does not necessarily mean run them locally.  The former is much more valuable in finding issues early.

The only workaround for now is just to use cakebuild.net  It would be so nice if the M$ give us a solution to run the build locally based on the yaml.

@bryanmacfarlane how would I test before commit without running them locally, however?

Is there a way to reopen this @bryanmacfarlane?

It is my understanding many of the Azure DevOps contributors have been retasked to GitHub related assignments. Unless there's a big change in priority, the chance of this getting work is all but zero. The thing that baffles me is how they iterated on the pipeline w/o this. Whether tasks or pipelines, I can't conceive why anyone would want to add/commit/push every time they try to change the system. I'm starting to think I need to have my team use Fake and Paket scripts w/ defined stages where auth happens when leveraging the build agent. The pain and suffering of defining build yaml is just too high as is.

I totally aggree, that this is very painfull.
But I fear we need to consider the requested issue to be a new maybe quite complex feature.
Here I found a similar feature request:
https://developercommunity.visualstudio.com/content/idea/366517/ability-to-test-yaml-builds-locally.html --> please upvote it.

I used to define my entire build with msbuild. IT aquired nugets+dependencies, build solutions, signed files, build installers, packed and pushed nugets and artifacts. The world was happy and I could run it on my machine and on the build machine.
I never really understood why there were all the other pipeline tasks!
Recently though this is becoming hard to maintain! Its seems that new functionality we want to use in builds is only supported in pipeline tasks and I can't call it directly from msbuild.
Cry.
It is very wrong to have to define a build that I want to do the exact same thing in two different ways to be able to run it locally and on build machines!!!!!!!!!
Architectural fail. :)

We have a few stories on our backlog to address these scenarios starting with linting, then preview what if, and then finally a private buddy build you can run before committing the yaml (run locally but cooperates with the service - not offline).
I'm going to close since this is a multi-stage set of work and it's not an issue. rest assured it's something we want to and will solve. It's just not ready yet.

Any update on this?  If you don't like azure pipelines for dev/test cycles, I'd work out some alternate arrangement and just use pipelines as a way to kick it off on another computer, but put all the tasks and such inside your own code.
Doing it this way would also make your platform easier to port to another provider should the need arise.

We have a few stories on our backlog to address these scenarios starting with linting, then preview what if, and then finally a private buddy build you can run before committing the yaml (run locally but cooperates with the service - not offline).
I'm going to close since this is a multi-stage set of work and it's not an issue. rest assured it's something we want to and will solve. It's just not ready yet.

Any update on this? It would be useful to run this on a local machine; until that is arranged, azure pipelines are practically useless for me and probably many other Linux CLI guys...

Check this out - https://docs.microsoft.com/en-us/azure/devops/release-notes/2020/sprint-165-update#preview-fully-parsed-yaml-document-without-committing-or-running-the-pipeline

Check this out - https://docs.microsoft.com/en-us/azure/devops/release-notes/2020/sprint-165-update#preview-fully-parsed-yaml-document-without-committing-or-running-the-pipeline

OOOoo! So they now have an API exposed for this ... and just need to add some entrypoint into their website UI. Nice -- nearly there, now.
Aside: it's also lol that this issue was closed in 2018 and in 2020 we're all still talking in it.... 🤔 🤔

We have a few stories on our backlog to address these scenarios starting with linting, then preview what if, and then finally a private buddy build you can run before committing the yaml (run locally but cooperates with the service - not offline).
I'm going to close since this is a multi-stage set of work and it's not an issue. rest assured it's something we want to and will solve. It's just not ready yet.

Any update on this? It would be useful to run this on a local machine; until that is arranged, azure pipelines are practically useless for me and probably many other Linux CLI guys...

Check this out - https://docs.microsoft.com/en-us/azure/devops/release-notes/2020/sprint-165-update#preview-fully-parsed-yaml-document-without-committing-or-running-the-pipeline

Hi guys, I have tried using the api, but I keep getting a timeout error, it would be nice to see other experiences (hopefully successful ones), perhaps I am missing something, not a lot in the doc.

Check this out - https://docs.microsoft.com/en-us/azure/devops/release-notes/2020/sprint-165-update#preview-fully-parsed-yaml-document-without-committing-or-running-the-pipeline

OOOoo! So they now have an API exposed for this ... and just need to add some entrypoint into their website UI. Nice -- nearly there, now.
Aside: it's also lol that this issue was closed in 2018 and in 2020 we're all still talking in it.... 🤔 🤔

Just noticed that this is actually closed lol I don't think this issue is resolved yet!

Does anyone know if this is planned to be added into the vscode addon? - Could be awesome to be able to test your pipeline directly in vscode.
Also - We use a lot of templates, how would one upload those to the api?

i am deploying .net core app on Azure container Registry and fixing the failure with each commit is just mind-boggling

It's been 2 years since, and nothing has been announced? Could we at least reopen the issue to track the request, or at least open a new one?

Can we please reopen this?

The contributors are too busy working on the github actions which seems to have this. My advice would be to use that, or else to move away from using tasks and instead use local make-style builds, only using the actions to invoke them.
It's absurd that incremental, local testing is so foreign to Microsoft, but it is what it is.

The speed at which we are supposed to rewrite our projects to suit the latest flavour is ridiculous.

Hi everyone, please feel free to create an issue in https://github.com/Microsoft/azure-pipelines-yaml to get right eyes on it. This repo is mostly for pipeline tasks, so it could be more forward way to track progress regarding this feature.

Raised a ticket on issue in here:
https://developercommunity.visualstudio.com/idea/1302759/yaml-how-to-test-yaml-locally-before-commit.html

Raised a ticket on issue in here:
https://developercommunity.visualstudio.com/idea/1302759/yaml-how-to-test-yaml-locally-before-commit.html

This increases the development cycle and prevents fast experimental changes to Build pipelines. :|
The issue is closed as "multi-stage set of work" but not a single related issue was linked to this one (so that users can subscribe). :(

Dude, it's always been like this.  Xml builds, "new scriptable builds" now yaml builds.   You'd think the company that started with interpreted BASIC REPL would understand that developers want to get stuff working on their own computer first before putting on the server.   It honestly boggles the mind.   It's a cultural issue that I don't see changing unfortunately.

I think the concept of running a YAML pipeline locally is getting conflated with the concept of testing a YAML pipeline before committing it.
The ability to run a pipeline locally is not only a much larger feature to implement, it's also less desirable because your local machine won't be able to give an accurate impression of whether the pipeline will run on the cloud. It's also irrelevant to me because I always edit YAML pipelines directly in DevOps where I'm going to run them. The feature of just getting to test a pipeline before committing it seems like it would be as easy to implement as adding a "run" button that's the same as "save and run" without the save. DevOps can already run your pipeline for you, so how hard can it be to let you run a pipeline that hasn't been committed yet?
Because it would be a better feature and a more likely one to get implemented, I think we should focus our efforts on just asking for a way to test pipelines before committing rather than a way to run pipelines locally.

What is needed is to do all this work locally on your computer without using azure pipelines.  Just like I can build a visual studio solution locally or in pipeline.   The fact that Microsoft build systems never provided a way of running the scripts locally, whether it was xaml based, then vNext, and now yml is just a perpetuation of a bad decision made a long time ago.
Fundamental tenet of any system on the cloud or build system is that the developer ought to be able to run it locally, unless there is some kind of technical reason such as it being impossible... special hardware, etc.  And even those should be able to provisionable as needed.
The solution right now is to decouple from the yaml system as much as possible, placing as much of the logic as possible in poweshell scripts which can be run in any container.   That way when the build system changes again, majority of the logic that's on powershell scripts doesn't have to get rewritten.
Issue can be closed.

At the moment we actively use powershell scripts as a "replacement" for yaml, but unfortunately - yaml cannot be completely replaced with powershell - there are always native yaml mistakes, like forgetting amount of tabs, spaces inconsistency, incorrect variables / parameters usage.
We have also build system which takes quite long time to execute (for example over 1 hour), and then testing yaml syntax gets crazy if you need to fix it on same place multiple times. Luckily we've invented nooperation for powershell script - build system would just print what it about to do. But then need to run yaml with special parameter turned on.
I guess best approach would be that yaml would always execute powershell script with "-noop" command line argument first, and after that without that parameter. "-noop" would just verify that everything that was scheduled to be executed, will be executed.
Suspect it would be useful to have this interop yaml - powershell by default on, with built-in check box (like "verify execution flow" or "no operation")

What is needed is to do all this work locally on your computer without using azure pipelines. Just like I can build a visual studio solution locally or in pipeline. The fact that Microsoft build systems never provided a way of running the scripts locally, whether it was xaml based, then vNext, and now yml is just a perpetuation of a bad decision made a long time ago.
Fundamental tenet of any system on the cloud or build system is that the developer ought to be able to run it locally, unless there is some kind of technical reason such as it being impossible... special hardware, etc. And even those should be able to provisionable as needed.
The solution right now is to decouple from the yaml system as much as possible, placing as much of the logic as possible in poweshell scripts which can be run in any container. That way when the build system changes again, majority of the logic that's on powershell scripts doesn't have to get rewritten.
Issue can be closed.

Was this in response to what I said? I'm not sure I understand what you're saying and why. The issue has been closed for a long time


tortoisebeacon: remove mockery and move mocks to a separate directory

Motivation
I initially made this refactoring in ssz branch. Because sszgen can't work if in the same module other module imported in a different way, e.g. one file imports "time" and another time "time".
I also replaced it by mockgen, since it is better to use single mock module across the same repo.
Closes # https://github.com/spacemeshos/go-spacemesh/issues/2604
Changes

Test Plan

TODO

[ ] Explain motivation or link existing issue(s)
[ ] Test changes and document test plan
[ ] Update documentation as needed

DevOps Notes

[x] This PR does not require configuration changes (e.g., environment variables, GitHub secrets, VM resources)
[x] This PR does not affect public APIs
[x] This PR does not rely on a new version of external services (PoET, elasticsearch, etc.)
[x] This PR does not make changes to log messages (which monitoring infrastructure may rely on)

bors merge

bors merge


[Bug]: useBeforeUnload TypeScript issue

Which Remix packages are impacted?

[ ] remix (Remix core)
[ ] create-remix
[ ] @remix-run/architect
[ ] @remix-run/cloudflare-workers
[ ] @remix-run/dev
[ ] @remix-run/express
[ ] @remix-run/netlify
[ ] @remix-run/node
[X] @remix-run/react
[ ] @remix-run/serve
[ ] @remix-run/server-runtime
[ ] @remix-run/vercel

What version of Remix are you using?
1.1.1
What version of Node are you using? Minimum supported version is 14.
16.13.1
Steps to Reproduce
Use useBeforeUnload like so:
useBeforeUnload(
    useCallback((e) => {
      e.preventDefault();
      e.returnValue = "";
    }, [])
  );

Expected Behavior
There is no type error
Actual Behavior
Error: Argument of type '(e: any) => void' is not assignable to parameter of type '() => any'.ts(2345)

I'd love to open a PR and fix if yall are open to contribution here

Merged 🥳 https://github.com/remix-run/remix/pull/1723


Fix multiple lists in navbar.

There's a bug in the current version's navbar : it displays several lists with a single item in each instead of a single list with several items (which I believe is the intended behaviour).
This commit just moves the ng-repeat directive to the li level to fix it.

Good catch. Thank you!


KISS doesn't respect RPATH/RUNPATH

[x] Does this issue occur in master?

Description
KISS doesn't check the RPATH/RUNPATH of executables which leads it to falsely add some packages as dependencies. Eg, if nss is installed in /usr/lib and firefox is installed in /usr/lib/firefox with bundled nss/nspr, kiss will add a dependency on nss for firefox
Error message
/home/build/kiss/reproducer/zlib-bundle $ kiss b
-> Building: explicit: zlib-bundle
-> Checking for pre-built dependencies
-> zlib-bundle Reading sources
-> zlib-bundle Verifying sources
-> zlib-bundle Building package (1/1)
-> zlib-bundle Extracting sources
-> zlib-bundle Starting build
-> zlib-bundle Successfully built package
-> zlib-bundle Generating manifest
-> zlib-bundle Stripping binaries and libraries
strip -s -R .comment -R .note /tmp/817/pkg/zlib-bundle/usr/lib/ineedzlib/libz.so.1.2.12
strip -s -R .comment -R .note /tmp/817/pkg/zlib-bundle/usr/lib/ineedzlib/ineedzlib.so
strip -s -R .comment -R .note /tmp/817/pkg/zlib-bundle/usr/lib/ineedzlib/ineedzlib
-> zlib-bundle looking for dependencies (using readelf)
--- /tmp/817/tmp/zlib-bundle-depends
+++ /tmp/817/tmp/zlib-bundle-depends-fixed
@@ -0,0 +1 @@
+zlib
-> zlib-bundle Generating manifest
-> zlib-bundle Generating etcsums
-> zlib-bundle Creating tarball
-> zlib-bundle Successfully created tarball
-> Install built packages? [zlib-bundle]
-> Continue?: Press Enter to continue or Ctrl+C to abort

Package
#!/bin/sh -e

mkdir -p "$1/usr/lib/ineedzlib"

cd "$1/usr/lib/ineedzlib"

$CC -shared -o libz.so.1.2.12 -fPIC -x c - <<EOF
void *gzopen(void) { return (void *) gzopen; }
EOF

ln -s libz.so.1.2.12 libz.so

$CC -shared -o ineedzlib.so libz.so -Wl,-rpath=/usr/lib/ineedzlib -x c - <<EOF
void call(void) { void *gzopen(void); gzopen(); }
EOF

$CC -o ineedzlib ineedzlib.so -Wl,-rpath=/usr/lib/ineedzlib -x c - <<EOF
int main(void) { void call(void); call(); }
EOF

The issue is similar to https://github.com/kiss-community/kiss/issues/20
See https://github.com/kiss-community/repo/pull/86#issuecomment-1234069350
CC @illiliti @ioraff @cemkeylan

I thought we solved this issue when multilib support was added. Apparently not.

I thought we solved this issue when multilib support was added. Apparently not.

The exact commit didn't propagate to upstream KISS, it was fixed in a different way with dependency rework by dylan. Multilib still works fine tho

Is there a way to actually determine the full path of a linked shared library?

Is there a way to actually determine the full path of a linked shared library?

Running ldd seems to give the correct paths, not sure what's going wrong in KISS code

Okay, I see the issue now. The directory where you are building the package is not part of the rpath. So ldd fails to locate the shared library. When the library can't be located in the rpath it fallsback to the zlib installed on the system, that's how rpath works. Going to the package directory and adding it to the LD_LIBRARY_PATH seems to resolve it. However, I'm not sure how reliable this solution is.

Ahh, that explains the firefox bug aswell. /usr/lib/firefox is originally present with nss inside of it, and firefox's rpath is set to that dir regardless of build config, so kiss detects that nss instead of the one in /usr/lib

http://blog.tremily.us/posts/rpath/

The relevant linker flags are -rpath and --enable-new-dtags. Without --enable-new-dtags, you'll just set the RPATH flag, which is probably not what you want. With --enable-new-dtags, you'll set both RPAH and RUNPATH to the same value. From ld(1):

The DT_RPATH entries are ignored if DT_RUNPATH entries exist.

so setting both is the same as just setting RUNPATH (except for tools like chrpath which are only designed to handle a single tag). You can use readelf to see if the tags were set:

Should the fix account for such cases?
Dynamic section at offset 0x2de0 contains 26 entries:
  Tag        Type                         Name/Value
 0x0000000000000001 (NEEDED)             Shared library: [./Library rpath: [asdfaffqfewffsd].so]
 0x0000000000000001 (NEEDED)             Shared library: [libc.so.6]
 0x000000000000000f (RPATH)              Library rpath: [/tmp/test]
 0x000000000000000c (INIT)               0x1000
 0x000000000000000d (FINI)               0x1134
 0x0000000000000019 (INIT_ARRAY)         0x3dd0

This part could probably benefit from being written in C

λ readelf -d /usr/bin/llvm-readelf

Dynamic section at offset 0x1c7ca0 contains 32 entries:
  Tag        Type                         Name/Value
 0x0000000000000001 (NEEDED)             Shared library: [libLLVM-14.so]
 0x0000000000000001 (NEEDED)             Shared library: [libstdc++.so.6]
 0x0000000000000001 (NEEDED)             Shared library: [libm.so.6]
 0x0000000000000001 (NEEDED)             Shared library: [libgcc_s.so.1]
 0x0000000000000001 (NEEDED)             Shared library: [libc.so.6]
 0x000000000000000f (RPATH)              Library rpath: [$ORIGIN/../lib]

$ORIGIN needs to be handled too


ALL tests in gRPC Master Linux broken

Happening for a few last builds in https://grpc-testing.appspot.com/job/gRPC_master_linux/2357/testReport/junit/(root)/aggregate_tests/run_tests_python_linux_dbg_native/
Most likely a side effect of https://github.com/grpc/grpc/pull/10967?
2017-05-10 03:01:04,275 URL being requested: GET https://www.googleapis.com/discovery/v1/apis/bigquery/v2/rest
2017-05-10 03:01:04,298 URL being requested: POST https://www.googleapis.com/bigquery/v2/projects/grpc-testing/datasets/jenkins_test_results/tables?alt=json
2017-05-10 03:01:04,298 Attempting refresh to obtain initial access_token
2017-05-10 03:01:04,335 Encountered 403 Forbidden with reason "insufficientPermissions"
2017-05-10 03:01:04,337 URL being requested: POST https://www.googleapis.com/bigquery/v2/projects/grpc-testing/datasets/jenkins_test_results/tables/master_linux_basic/insertAll?alt=json
2017-05-10 03:01:04,344 Encountered 403 Forbidden with reason "forbidden"
Error in creating table: master_linux_basic. Err: <HttpError 403 when requesting https://www.googleapis.com/bigquery/v2/projects/grpc-testing/datasets/jenkins_test_results/tables?alt=json returned "Insufficient Permission">
Error inserting rows to the table master_linux_basic

Ok removed --bq_result_table master_linux_basic from the Job config for now (that should fix the breakage)
To be able to authenticate with bigquery with regular linux workers, one needs to add a scope at VM creation time.

https://github.com/grpc/grpc/blob/master/tools/gce/create_linux_performance_worker.sh#L54

I removed the flag from the other Linux master jobs as well. I missed the BQ scope being missing from the regular workers, since I tested this on a custom GCE instance. Thanks!


[Enhancement] Make the Explore consistent width

Hi, please assign this to me.
I'd like to make the explore input more consistent so it has the same width with the profile to have a better UI.

@leonyangela go ahead

Hi @SwanandD121, thanks for assigning me, it's already in PR #68, thank you, cheers.

merged


Disable "ENTER" button functionality on input boxes

It's doing something like submitting the form, which causes random dice rolls to happen when you don't want that.

This has been added in 4ea310d, This is likely a browser-specific problem, so I can't promise it will work in everything.


Integration of paddle2coreml tool into FastDeploy

PR types(PR类型)

Description
This pull request adds the paddle2coreml tool to the FastDeploy project. With this integration, users will be able to use a single command to convert their PaddlePaddle models to CoreML models.
The environment preparation steps for using paddle2coreml tool are included in the documentation. Additionally, an example usage command is provided in the documentation with notes on the parameters.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.lishicheng03 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.You have signed the CLA already but the status is still pending? Let us recheck it.


Code Coverage

Work in progress. I'm just opening this PR early to test out changes to the CI.

Codecov Report

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

@@          Coverage Diff           @@
##             main     #47   +/-   ##
======================================
  Coverage        ?   0.69%
======================================
  Files           ?      18
  Lines           ?    3315
  Branches        ?    1860
======================================
  Hits            ?      23
  Misses          ?    3287
  Partials        ?       5

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Add CardStackStateManager

Replace CardStackState implementation with CardStackStateManager. This is an internal change only
Make topCardIndex = nil instead of 0 if there is no top card
Merge SwipeCardStackSpec.swift and SwipeCardStackSpec+SwipeCardDelegate.swift files

Codecov Report

Merging #36 into master will decrease coverage by 1.52%.
The diff coverage is 77.55%.

@@            Coverage Diff             @@
##           master      #36      +/-   ##
==========================================
- Coverage   80.38%   78.85%   -1.53%
==========================================
  Files          14       14
  Lines         734      719      -15
==========================================
- Hits          590      567      -23
- Misses        144      152       +8

Impacted Files
Coverage Δ

...ources/Shuffle/SwipeCardStack/SwipeCardStack.swift
100% <100%> (ø)
:arrow_up:

Sources/Shuffle/SwipeCard/SwipeCard.swift
100% <100%> (ø)
:arrow_up:

Sources/Shuffle/SwipeCard/SwipeView.swift
100% <100%> (ø)
:arrow_up:

Sources/Shuffle/Animator.swift
53.84% <40%> (ø)
:arrow_up:

...Shuffle/SwipeCardStack/CardStackStateManager.swift
57.89% <57.89%> (ø)


App uninstall

Hi can give any brief documentation about app uninstall process. to remove the liquid files from store.

I don't think this is possible. Once the uninstall happens the token for the shop should not work. I don't think what you're asking is possible.


[AIRFLOW-4766] Add autoscaling option to DataprocClusterCreateOperator

Make sure you have checked all steps below.
Jira

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

https://issues.apache.org/jira/browse/AIRFLOW-XXX
In case you are fixing a typo in the documentation you can prepend your commit with [AIRFLOW-XXX], code changes always need a Jira issue.
In case you are proposing a fundamental code change, you need to create an Airflow Improvement Proposal (AIP).
In case you are adding a dependency, check if the license complies with the ASF 3rd Party License Policy.

Description

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

Tests

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

Commits

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

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

Documentation

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

All the public functions and the classes in the PR contain docstrings that explain what it does
If you implement backwards incompatible changes, please leave a note in the Updating.md so we can assign it to a appropriate release

Code Quality

[ ] Passes flake8

Codecov Report

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

@@            Coverage Diff            @@
##             master      #90   +/-   ##
=========================================
  Coverage          ?   78.98%
=========================================
  Files             ?      482
  Lines             ?    30214
  Branches          ?        0
=========================================
  Hits              ?    23866
  Misses            ?     6348
  Partials          ?        0

Impacted Files
Coverage Δ

...xample_dags/example_gcp_dataproc_create_cluster.py
0% <0%> (ø)

airflow/contrib/operators/dataproc_operator.py
83.95% <100%> (ø)

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 68e8c99...7eba26d. Read the comment docs.

@mik-laj, @potiuk should we merge those changes?

You should create a PR in Apache repository. :-D


Add to odh-env-users

Hi
I'd greatly appreciate getting access to the aicoe-osc-demo.
Thanks

Hi @Madhumithran - I invited you to aicoe as well odh.  please let me know what aspects of OS-Climate you are interested in.  If you provide your email address, I can share some on-boarding resources.


Replace the object structuring from JSON style to a dot notation

Currently, if we ever have data like this
{
  Contact: {
    Address: 0,
    Phone: 0
  }
}

and when we try this import-export plugin, it returns it in this form:
Contact
{Address:0,Phone:0}

This is good, but making it return like this would be better:
Contact.Address, Contact.Phone
0, 0

Your issue would be to convert it to this.

Check this for reference: https://stackoverflow.com/questions/33005575/how-to-convert-json-object-structure-to-dot-notation

Also check out: https://github.com/EdisonPeM/strapi-plugin-import-export-content/issues/65


Update codeblocks in Livepeer Studio docs to reflect SDK documentation

Currently, the path between the docs and the SDK is not clear -- it's mentioned in a few places, but there's no clear point of handoff. To reduce this confusion (and prevent users from having to review two sets of docs) we should update the code blocks to include livepeerjs, fetch and curl.
There are some places where there isn't livepeerjs code that is applicable, and in those places we should keep the existing javascript code. Ex. list all assets.

Remove curl


Bump dcos-docs

Bump dcos/dcos-docs
Joel Hamill:
format
updated aws advanced URLs

🙏🏼

Joel

On Aug 11, 2016, at 10:39 AM, Thomas Rampelberg<EMAIL_ADDRESS>wrote:
Merged #770.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.


fix(explore): clean data when hidding control

SUMMARY

This PR solves the problem that form data will not be cleared when hiding a control via dynamic controls (e.g. orderBy). These are what I did:

Make a control whose visibility is false doesn't return null in parent component rendering,  but returns null in child component and resets the control value in child component useEffect.
Since it still renders in component trees and we need to make it behave the same as HiddenControl (don't be counted and don't display)
Clean unused code
Add more tests for this part

BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

before
https://user-images.githubusercontent.com/11830681/156961016-9d8dd5b8-2a5f-489d-9c77-84931290f38c.mov
after
https://user-images.githubusercontent.com/11830681/156961432-3d09802e-1c01-43f8-8df2-9b465ed0a4e5.mov
TESTING INSTRUCTIONS

Create a Timeseries chart
Add one METRIC
Add one SORT BY
Uncheck SORT DESCENDING
Run query
Remove SORT BY
Run query
view the query

ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Required feature flags:
[ ] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

[ ] Migration is atomic, supports rollback & is backwards-compatible
[ ] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[ ] Introduces new feature or API
[ ] Removes existing feature or API

Hi @stephenLYZ , I tested this PR in my local, but the order direction checkbox is gone when I put an ad-hoc metric.
https://user-images.githubusercontent.com/2016594/161234452-618c3c9c-78ca-4d49-9c02-f3b78255804d.mov

Hi @stephenLYZ , I tested this PR in my local, but the order direction checkbox is gone when I put an ad-hoc metric.
order.direction.gone.mov

Fixed.


split specs in multiple chunks of 5000 specs

I tested on the big vCenter, specs size of 5000 always works

Codecov Report

Merging #158 into master will increase coverage by 0.02%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #158      +/-   ##
==========================================
+ Coverage   93.73%   93.76%   +0.02%
==========================================
  Files           4        4
  Lines         543      545       +2
==========================================
+ Hits          509      511       +2
  Misses         34       34

Impacted Files
Coverage Δ

vmware_exporter/vmware_exporter.py
92.99% <100%> (+0.02%)
:arrow_up:

Continue to review full report at Codecov.

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

Missing the unit tests. Sorry i do that asap


No able to create contract using this .sol project

Please provide us with the following information:

This issue is for a: (mark with an x)
- [ ] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

Any log messages given by the failure

Expected/desired behavior

OS and Version?

Windows 7, 8 or 10. Linux (which distribution). macOS (Yosemite? El Capitan? Sierra?)

Versions

Mention any other details that might be useful

Thanks! We'll be in touch soon.

What's the errors you are seeing?

No response, closing the issue. Will re-open if the issue persists.


let matchdg decorate other trainers

https://github.com/marrlab/DomainLab/blob/a28f60ab505cbd2e74767920e6e8b830b4df35a5/domainlab/algos/trainers/train_matchdg.py#L94C27-L94C27

Merge pull request https://github.com/marrlab/DomainLab/pull/684 from marrlab/matchdg_decorate_trainers
6792158


Volume of a sphere

Title of article
Write a Python program to compute the volume of the Sphere
Takes the length of radius
Uses the formula to calculate the volume
Return the value
Volume of a sphere = radius * radius * radius  * 4/3  * π
Additional information
Example:
radius = 8
Volume of a sphere = 8^3 * π * 4/3 = 2144.66 (round to 2 decimal places)
Programme:
Radius : 8

Volume : 2144.66

Code of Conduct

[X] I have read and agree to the Codinasion project's Code of Conduct

Could I claim this issue?


Http request to Neptune server failed: HTTPRequestTimeout().

It seems that I could not connect to neptune server.

Sorry,  My server loses its connection to the Internet.
Issue Closed.

thanks @Solacex


added tauri apps prerequisites

There should have been some more packages included, my bad. As per the reasoning, I've been working on these two projects:

https://github.com/tsimouris/youtube-tv
https://github.com/tsimouris/twitch-tv

Just need to configure the icons now and work on the tauri bundrer, for flatpak support that is. For now though AppImages can be used.

If the flatpak issue is resolved then we won't these packages?

True, the solution is rather temporary till the flatpak bundler is ready; at that point these should be part of the flatpak dependencies

Looks like AppImage might also be a solution? In any case, I don't think we need native support for this. Most people will want to use Flatpak, and that would be the preferred solution.


[ENH] Add MultiplexTransformer

Reference Issues/PRs
Related to #2670 and #2459.  Note this implementation is meant to be very similar to how MultiplexForecaster currently works - see #2458 making use of the _DelegatedTransformer in #2612
What does this implement/fix? Explain your changes.
With MultiplexTransformer one now in theory has a new way to multiplex over multiple transformers.  (Note one could optionally include various transformers with the pre-existing OptionalPassthrough but MultiplexTransformer should be useful when people want exactly one transformer.
Does your contribution introduce a new dependency? If yes, which one?
No
What should a reviewer concentrate their feedback on?
As it stands - it seems the easiest use case is to bundle MultiplexTransformer into either TransformedTargetForecaster or ForecastingPipeline and then evaluate which transformer is best using ForecastingGridCV.  However - one might imagine that you could wish to use MultiplexTransformer outside of the forecasting context.  Which begs the question - is it worth building some sort of GridSearch functionality into transformers as well? If so - what might be the best way to "evaluate" which transformer is best? Just wondering if this would be worth opening an issue for.
For all contributions

[x] I've added unit tests and made sure they pass locally.
[x] The PR title starts with either [ENH], [MNT], [DOC], or [BUG] indicating whether the PR topic is related to enhancement, maintenance, documentation, or bug.

For new estimators
I guess this is technically a new estimator.... I did not do these things.  But, I can. Lmk!

[x] I've added the estimator to the online documentation.
[ ] I've updated the existing example notebooks or provided a new one to showcase how my estimator works.

Which begs the question - is it worth building some sort of GridSearch functionality into transformers as well? If so - what might be the best way to "evaluate" which transformer is best? Just wondering if this would be worth opening an issue for.

That's an interesting question.
I think the natural use case of MultiplexTransformer etc is together with GridSearch.
The non-obvious observation is that the multiplexer can be separated from grid search, and perhaps should, because - as you say! - transformers appear in pipelines of different estimator types.
For me, the key argument whether to separate or merge would be "parsimony of specification" and avoiding "proliferation of classes" (these two design principles do not always give the same answer).
Do you have any arguments or examples in favour of certain merges?

And clearly there is an ongoing effort to expand the pipelining functionality to other applications as well!  I didn't mean to suggest there wasn't - just suggesting that a more general GridSearch functionality should maybe be part of that conversation too! :)

I was just wondering if a more general GridSearch functionality should maybe be part of that conversation too! :)

Absolutely!
Though, I would have done this by know if I knew what the best architecture would be.
My favoured option right now is to do it via a generic benchmark utility, which is called internally and dispatches by estimator type internally.
Although, that would heavily depend on progress in the benchmarking workstream, and at least some amount of design discussion imo.

Yea I knew the tests were failing!  I sort of buried the reference to that  in the bottom of my essay on GridSearch. But..... they aren't failing now!
And regarding opening an issue - I agree it would be a better place for this discussion. I can do that, though wondering if it might be worth waiting until the benchmarking workstream is more established as part of a 'benchmarking wishlist'?

@fkiraly, I totally agree - I do think that it makes sense to use MultiplexTransformers with some sort of a GridSearch, but does it have to be the forecasting one?  I guess to me the fact that if you want to do a grid search you are forced into a choice - either use the sklearn GridSearch, or you can use the GridSearch functionality under forecasting -> model selection seems odd.

I think the "natural" way based on the current design would be to wrap parts of a pipeline possibly in multiplexers, and then use the type of grid search that is specific for the estimator type. E.g., MultiplexTransformer in a TransformedTargetForecaster, and then the forecaster grid search.

Idk, I guess it was striking me as somewhat strange to have these 2 different ways of approaching GridSearch when one might expect a more unified approach?

Yes, I think ultimately, having similar syntax for grid search and multiplexer would be the best end state. Having the same dunder symbol but dispatching by type comes close.

@miraep8, do you also want to open an issue on generic grid search and/or generic multiplexer?

@fkiraly, sure I will open one either this evening or tomorrow.  Still working on the bug, hope to have that wrapped up early next week as well.

my conjecture with the bug: this is a confusion between transformers_ and _transformers.
_transformers is the "always name/estimator pair" version of transformers, not fitted.
transformers_ is the fitted/fittable copy.
The get_params etc should refer to _transformers, not transformers_, I think?

That is a reasonable conjecture, unfortunately I don't think it fixes the problem. This might be due to some confusion on my part though.
In my implementation of MultiplexTransformer I was only using transformers_ not _transformers. I am open to adding _transformers as well, but I guess I am a bit confused why this would be needed for MultiplexTransformer and not MultiplexForecaster (ie, I went back and looked at that code and I think you only use forecasters_ there, never _forecasters....?)
Personally, I think that the issue is coming up because we are using the TransformerFitTransformPanelUnivariateWithClassY on MultiplexTransfomer when it is wrapping Imputer which should only be applied to series data, not panel data.  I would have thought that copying the tags from Imputer as we do in init would filter out this scenario from being applied, but clearly that is not the case.  Been looking more about how the scenarios are selected and/or if there is another tag that should be applied to MultiplexTransformer to fix this!

In my implementation of MultiplexTransformer I was only using transformers_ not _transformers. I am open to adding _transformers as well, but I guess I am a bit confused why this would be needed for MultiplexTransformer and not MultiplexForecaster (ie, I went back and looked at that code and I think you only use forecasters_ there, never _forecasters....?)

Yes, you are right - only one of these is needed, since there is only one transformer that needs to be fitted.
Btw, if I were to implement it today, I would make _transformers a property, like _steps in _Pipeline. That would avoid the write to self which I think is unnecessary.

For the record: the bug was due to a clash of the reserved variable transformers_  from BaseTransformer with the (obvious named) transformer_ that @miraep8 introduced.
That is a bit unfortunate, @miraep8 had no other way to know than reading the entirety of BaseTransformer which is nothing we can ask of an implementer.
I have tried to address the issue of "reserved variables are not known to the implementer" in PR https://github.com/alan-turing-institute/sktime/pull/2769

Explanation why it happened only for the fixture "with y": the reason was not the y, but that X was a panel (not just a single series). Because of that, the transformer vectorization would kick in, and that in turn would use the reserved transformers_ attribute and write to it.
I guess that highlights a good choice of scenarios, since they cover a bit, but also it highlights the difficulty to identify the condition in the scenario that causes the breakage, if there are multiple unique aspects to a scenario.

I thought we had a design policy about not changing user provided attributes, ie transformers.

That's correct ... ish.
We follow the scikit-learn design, where nothing must change init arguments (more precisely, their copies written to self to attributes of the same name), except the set_params interface, which is the dedicated interface point for changing those in an existing estimator instance.

@miraep8, tests were failing on main, not sure why - I think we should reopen and check

Ok!  Sounds reasonable to me.  Can you point me to where these tests are failing and I will take a look?

Ah, nevermind I see what you mean.

I suspect it is an interaction with the changes to the metrics, where the default setting for MAPE has been changed from symmetric to asymmetric
the changes to metrics are coming from the deprecation/removal actions prior to 0.12.0 release, and I merged them at the same time


Add List.takeWhile builtin function

We should totally promote this to a List.takeWhile builtin!
Add Json.takeWhile to the List builtins.

@rtfeldman how should we handle the isEscapeSequence? I assume we wouldn't want that in a List builtin. So I guess we need the predicate to handle variable lengths, so would takeWhile: List a, (List a -> {taken: a, rest : a}) -> {taken: a, rest: a} be ok?
takeWhile = \list, predicate ->
    helper = \{ taken, rest } ->
        when rest is
            [a, b, ..] ->
                if isEscapeSequence a b then
                    helper {
                        taken: taken |> List.append a |> List.append b,
                        rest: List.drop rest 2,
                    }
                else if predicate a then
                    helper {
                        taken: List.append taken a,
                        rest: List.dropFirst rest,
                    }
                else
                    { taken, rest }

            [a, ..] if predicate a ->
                helper {
                    taken: List.append taken a,
                    rest: List.dropFirst rest,
                }

            _ -> { taken, rest }

    helper { taken: [], rest: list }

isEscapeSequence : U8, U8 -> Bool
isEscapeSequence = \a, b ->
    when P a b is
        P '\\' 'b' -> Bool.true # Backspace
        P '\\' 'f' -> Bool.true # Form feed
        P '\\' 'n' -> Bool.true # Newline
        P '\\' 'r' -> Bool.true # Carriage return
        P '\\' 't' -> Bool.true # Tab
        P '\\' '"' -> Bool.true # Double quote
        P '\\' '\\' -> Bool.true # Backslash
        _ -> Bool.false

I would like to implement this as my first contribution. Could you please assign it to me?
I would appreciate a pointer to where the code should be placed.

We decided to not implement takeWhile as described in the Github issue, and instead decided to add a more traditional boolean-based takeWhile.
See this thread on Zulip for more info: https://roc.zulipchat.com/#narrow/stream/316715-contributing/topic/List.2EtakeWhile/near/351350051


Added schema version 201508.

Hi @PaoloPia, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by Microsoft and real humans are currently evaluating your PR.
TTYL, MSBOT;


Bug with Portable Tanks

I am running your current Beta 2.0 files on a private server with friends. We can't wait for the final release.
But I noticed a bug with the Portable Tank. If you right click a TFC barrel with the tank in hand it will transfer the liquid to the barrel but not remove it from the tank. So you basically can infinite fill your barrels with it.
You might able to prevent this through the use of the TechNodeFirmaCraft mod. I am one of the devs for MyTown protectections. Did you want me to submit a PR for it?
Also do you want me to throw up some other problems we have found here on the issues?
Lastly, is there a way to get access to your ATLauncher Dev builds directly? I have used the XMLs to figure out what you are using, but it would be nice to have a more direct access to it if you allow it.

Yes please submit any issues you have, it would be greatly appreciated. As for the barrels, I'm sure a PR would be useful, my collaborator deals with that as I'm not a programmer. If you can pop on the technode IRC that would probably be the easiest way. I can also get your IGN and put you in the Tester group for access to dev build.

We've disabled interaction between OpenBlocks tanks, Mek portable tanks and the barrels and vessels via the TNFC mod. Thanks.


no MatomoTracker.matomoObserver,

Describe the bug
In your migration guide on pub.dev you write for 4.0.0 that we have to set the MatomoTracker.matomoObserver,
But it is not existing :D
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

The example project is quite explicit https://github.com/Floating-Dartists/matomo-tracker/blob/main/example/lib/main.dart#L45


Added functionality to TeacherAdmin and StudentAdmin components on client side to send request to server. Server endpoints for adding parent teacher student to db built out.

Nope. Fix logic. Students should be from Student table, not a role in the Users.


Is it necessary to manually generate worker.jsbundle?

This file does not seem to be getting generated when I test on device, though it works when the packager is loaded via a URL rather than a file.

Unfortunately it is.

I also found that I had to rename the worker to worker.ios.js to avoid breaking the convention used by the packager.


Update web-app-routing.md

@sabbour
Can you review the proposed changes?
When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

Duplicate of https://github.com/MicrosoftDocs/azure-docs/pull/108699


https://graph.microsoft.com/v1.0/reports/getEmailActivityUserCounts(period='D7') does not work in MS Graph Explorer

Describe the bug
When making the following call using MS Graph Explorer its trying to redirect to download the report. It looks like MS Graph Explorer is not doing the redirect.
GET https://graph.microsoft.com/v1.0/reports/getEmailActivityUserCounts(period='D7')
https://docs.microsoft.com/en-us/graph/api/reportroot-getemailactivityusercounts?view=graph-rest-1.0#response
If successful, this method returns a 302 Found response that redirects to a preauthenticated download URL for the report. That URL can be found in the Location header in the response.
Expected behavior
MS Graph Explorer to perform the redirect and download the report (CSV)
Desktop (please complete the following information):

OS: Windows 11
Browser: Issue occurs in both Edge and Chrome
Version 99.0.1150.39

Additional context
There is also an issue with loading the "Modify Permissions" for "https://graph.microsoft.com/v1.0/reports/getEmailActivityUserCounts(period='D7')"
Workaround is to use "https://graph.microsoft.com/v1.0/reports/getEmailActivityUserCounts" to load the Modify Permissions

@irvinesunday Please see permissions problem mentioned in this issue.

@willfiddes,
Queries that result in a redirect to a download URL do not work on Graph Explorer due CORS policy. The query will however work in a backend service or API client like Postman. For now, Graph Explorer will only display this information when such a query is encountered.
Also, thank you for reporting the permissions problem. We have a fix that is being tracked here: https://github.com/microsoftgraph/microsoft-graph-devx-api/pull/948


Four questions about using proovread on Hst

Hi @thackl ,
I want to use proofread on correction the human transcriptome pacbio long reads, and I am confused with several questions.

Can I use the cutadapt to get the quality trimmed and error corrected reads? (cutadapt -q 30,30 -m 50 -o read_PE1.fq -p read_PE2.fq CL12R_1.fastq CL12R_2.fastq) ? Is the quality score and the length limitation are ok for the short reads?
For the running time, based on my long reads file (4 Gb file), If I want to run the program more effectively and I wonder I should set the chunk sizes 20M to get about 200 files or set 1G to get about 4 files? I use a 20M file to test the running time, and I wait for several hours but have not got the result yet, so do you have any suggestions?
I will use the corrected long reads to identify the new isoforms and fusion genes, so I should use the output file '.trimmed.fq' to do the next analysis?
For the evaluation of the corrected long reads, I am a little confused about some concepts. I can calculate the reads number in the output '.trimmed.fq' file and compare this reads number with the raw long reads number, so I can have a general idea that how many reads have been corrected. This is a performance measure. I wonder for the raw and corrected long reads, how can I know the mapping rate change information? I mean for raw the reads as lots of errors existed in, the mapping rate (mapping on the genome) should be lower than the corrected reads. And is this a necessary value to evaluate the correction performance? Can you explain some detail information for the evaluation measures?

I feel so sorry to ask these questions and some question maybe a little stupid. and I will really really appreciate for your help.
Regards,
Nestor

Really appreciate for your help! And I still have a question that how to check improved error rates with minimap2.
I used minimap2 to map pacbio raw reads, trimmed reads and untrimmed reads,
for raw reads, output log file show
mapped 291643 sequences
for trimmed reads, output log file show
mapped 252915 sequences
for untrimmed reads, output log file show
mapped 283248 sequences
Do you think it's a little strange that after correction, less reads mapping to the genome (it means the mapping rates decreased after correction)?
And for the mapping error rates change, do you have any idea that how to check it?
For correction step, my output after each iteration:
Running task bwa-sr-1
Masked : 36.2%
Running task bwa-sr-2
Masked : 48.3%
Running task bwa-sr-3
Masked : 53.4%
Running task bwa-sr-4
Masked : 64.7%
Running task bwa-sr-5
Masked : 67.4%
Running task bwa-sr-finish
Masked : 53.8%
How do you think this result, and is this good enough for the later analysis?
Thanks, really hope your reply.
Nestor


Add Yeoman generator

Check also https://github.com/amwmedia/plop and https://github.com/dchrzanowski/mtml

Also interesting https://github.com/lerna/lerna/tree/master/commands/create


moving to new grpc version crash at grpc::internal::BlockingUnaryCallImpl<>::BlockingUnaryCallImpl()

Hi,
What version of gRPC and what language are you using?
gRPC version v1.38.0-pre1
Language: C++
What operating system (Linux, Windows,...) and version?
Ubuntu 18.04.5 LTSh
What runtime / compiler are you using (e.g. python version or version of gcc)
g++ (Ubuntu 7.5.0-3ubuntu1~18.04) 7.5.0
BTW, also fails when building with ICC (intel compiler)
What did you do?
I was trying to move FWD with grpc version. built version v1.38.0-pre1 (also tried v1.39.0). used to have v1.17.0 and it worked fine.
My code:
  Result reply;
  ClientContext context;
  LOG(INFO) << "call PushWork rpc";
  Status status = _control_stub->PushWork(&context, desc, &reply);
  LOG(INFO) << "returned PushWork rpc";
  if (status.ok()) {
    return true;
  } else {
    LOG(ERROR) << status.error_code() << ": " << status.error_message();
    return false;
  }

What did you expect to see?
RPC Call Success
What did you see instead?
It seems that I have the following crash when issuing the first rpc call on the stub:
ubuntu:~/vascale$ ./distributor.sh
I1005 09:45:33.227728 15271 main.cpp:39] create and start server...
I1005 09:45:33.227814 15271 distributor_data_service_impl.cpp:47] Test! create data packet for testing
I1005 09:45:33.233847 15271 distributor_data_service_impl.cpp:49] Test! setting data
I1005 09:45:33.240685 15271 distributor_run.cpp:49] Registering data service
I1005 09:45:33.240705 15271 distributor_run.cpp:53] distributor data service ip:port : <IP_ADDRESS>:8081
D1005 09:45:33.241049961   15271 ev_posix.cc:169]            Using polling engine: epollex
D1005 09:45:33.241113307   15271 dns_resolver.cc:338]        Using native dns resolver
I1005 09:45:33.241175075   15271 server_builder.cc:280]      Synchronous server.  I saw the following issue 20781 but couldn't understand what's wrong in my existing code.
Was there an API change? is there a build flag /lib linkage that I'm missing?
Thanks in advance!
Yair

@ynahum Could you give us a small reproducible code so that we can take a look at? Also a crash call-stack looks a bit off to me because it contains sync_posix.cc but gRPC already started using sync_abseil.cc on Linux so there might be some misconfiguration on your build setup.


emerge-gitclone: add support for pure git refs (dev images)

This change adds support for checking out git refs. It is useful for using dev containers on development OS images.
For releases and for nightly builds, the OS version always corresponds to a tag in the scripts repo. emerge-gitclone uses the OS version to check out that tag. this works well for versions like e.g.

alpha-3549.0.0
3552.0.0+nightly-20230323-2100

because corresponding tags exist in the scripts repository.
However, a development OS image build (e.g. built on a dev machine, or via CI) might use a version like e.g.

alpha-3549.0.0-3-g7f21ab30
3552.0.0+nightly-20230323-2100-4-g5d72f4ee

This version is generated by the SDK container using
   git describe --tags

in https://github.com/flatcar/scripts/blob/main/sdk_lib/sdk_container_common.sh#L49 .
emerge-gitclone will fail in that case because there is no tag of that name in the scripts repo.
This change detects git refs appended to OS release versions. It extracts the git ref and uses the ref instead of a tag for checking out the correct scripts repo version.

Looks good, some whitespace nitpicks. You are probably writing too much bash. ;)

I do indeed! Thanks for your suggestions, I've merged them and will suqsh-merge the PR now.


[Bug]: data file is empty after Export  Result Set

ODC version
432
obloader/obdumper 4311
OB version
independent
What happened?
data file is empty after Export  Result Set

What did you expect to happen?
data file has 100 rows reference export log
How can we reproduce it (as minimally and precisely as possible)?
create new Export  Result Set tickets
select data source: oboracle_3233, select database: ZEYANG
enter  query SQL: select * from non_partrange_list_nopri
after export click dowload and check data file
Anything else we need to know?
No response

pass


Replacing a corrupted file with new one on public FTP - user request

The user Alexander Guojonsson has identified a problem with one of his submitted files and has uploaded a replacement file onto our private FTP. This now needs to be moved onto the public FTP.
private FTP Directory: Guðjónsson_GCST90088598
file hecksum: 1ade54716c1968f0983abac00a88dc01
public FTP directory: GCST90088001-GCST90089000/GCST90088598/

closing due to duplicate ticket gwas-user-requests#48


Sky shaders do not correctly respect 'use in sky only' property

Godot version
4.0 alpha 2
System information
WIndows 10, Nvidia GTX 1070, Vulkan renderer
Issue description
When using a sky shader that only uses light0, If there is more than one DirectionalLight3D node in a scene, and one has the 'use in sky only' property enabled, the shader will disinherit that light, and assign the next light in the scene that does not have that property enabled as light0. This would seem like correct behaviour, as typically sky and scene lighting should be matched, but as I've detailed here, this can cause issues when the shader modifies lightx values.
To allow greater artistic flexibility with regards to scene lighting, and combat lighting discontinuity described in the discussion above, sky shaders should instead retain inheritance from lights with the 'use in sky only' toggle enabled.
Steps to reproduce

Add WorldEnvironment and two or more DirectionalLight3D nodes to a scene, these can be separate or parented
Add geometry nodes to test lighting
Add sky shader to WorldEnvironment
Toggle 'use in sky only' on in properties of first DirectionalLight3D

Minimal reproduction project
Minimal reproduction exceeds Github's file size restrictions, upload is here: https://www.dropbox.com/s/ltlqhjn4yesflqk/4.0_test_lighting.zip?dl=0

I'm not totally certain what the issue is here. There was a bug with "use in sky only" that was fixes earlier today (https://github.com/godotengine/godot/pull/58175), could that be the root cause?
Are you suggesting that if there are two lights in the scene, the sky shader should prioritize lights that are marked as "use in sky only" instead of taking the first light in the scene tree?

I am having trouble reproducing this exact issue in a clean project. I will try again with your MRP and see if I can reproduce.

Please let me know if you're still having trouble reproducing - I can try recording a video displaying the issue on the MRP if this would help.

On closer inspection, I can reproduce using Alpha 2, but it is already fixed in master (499eec13a3660f6f05a6212be97ea164fd98b519).
It was probably fixed by either https://github.com/godotengine/godot/pull/58175 or https://github.com/godotengine/godot/pull/57104
Closing as it is already fixed. It should be working fine for alpha 3 :)


How to swap image on click.

Currently, if I want to switch to a different image I am first destroying the previous image viewer and creating the new one.
Is there any way to switch to a different image without destroying the viewer?
My code:
ImagePanel.prototype.removeMap = function(){
    if(this.viewer){
        this.viewer.destroy();
    }
}

ImagePanel.prototype.setMap = function(){
    this.removeMap();
    this.viewer = new OpenSeadragon({
        id: "mapid",
        showNavigator: true,
        zoomInButton: 'zoomIn',
        zoomOutButton: 'zoomOut',
        homeButton: 'home',
        showFullPageControl: false,
        useCanvas: false,
        visibilityRatio: 1,
        tileSources: {
            type: 'legacy-image-pyramid',
            levels:[{
                url: url,
                height: 889,
                width:  600
            },
            {
                url: url2,
                height: 2201,
                width:  1485
            },
            {
                url: url3,
                height: 4402,
                width:  2970
            }
        ]

        }
    });
}

Sure, the easiest way is to just call viewer.open with whatever you would otherwise put in the tileSources property. This closes whatever image you currently have and opens the new one (without destroying the viewer).
For a more advanced/involved version, you can do a crossfade like so: https://codepen.io/iangilman/pen/YXRLea


Create string table for squad names

Reduce amount of redundancy and make it easier to update group names by create a string table for reference https://community.bistudio.com/wiki/Stringtable.xml

I do not think that a string table is necessary for this.  Its main purpose is implementing multiple languages, so if anything, a file should be made to define group names.  However, I do not see what is stopping mission makers from just updating the group names in the eden editor.


ci: fix AWS EKS K8s versions comment

The plague of copy/pasting strikes again...

This PR does not need to run any CI. It's arguable if it even needs any reviews. Marking ready-to-merge right away :D


Does the frontend crash after a malicious scan of ports?

After letting my frontend run on the Raspberry Pi a long time, the frontend may crash. It fails with a bunch of the following error messages:

What's happening is that something is trying to access some really weird URLs in the frontend: "/boot.ini" and "/etc/passwd". Since my RPi has not been locked down (i.e. its wifi connection is enabled and I didn't do any security configuration related to its internet connection), this seems likely to be some kind of attacker trying to see if my RPi's port 3000 (where the React dev server runs the frontend when I call yarn start) is exposing filesystem access. The sequence of unprintable bytes is: "%f8%80%80%80%ae%f8%80%80%80%ae", which is repeated with / as a separator. This looks like garbage, and the fact that the bytes are repeated doesn't seem like an attack which would break a Node.js server handling untrusted inputs (though maybe it could break something else?); when I did a google search, only two results showed up, both of the same email thread from the Linux mailing list fa.linux.kernel , where it's provided just as an example sequence of bytes in a discussion about how UTF-8 single-byte sequences might be rendered. If I instead search this sequence in hex formatting (\xf8 instead of %f8), I get two results: one is an error log which is apparently published online from some obscure company (seems like a security hole to me), where a server running phpMyAdmin reports that a client in 2017 tried to access a bunch of invalid URLs all within the same second but was denied: \xf8\x80\x80\x80\xae\xf8\x80\x80\x80\xae, Documentation.html, phpinfo.php, etc. The other is some anonymously-uploaded pcap recording in 2018 named "challengeCopy.pcap" generated by the "Acme Vulnerbilty Scaning Service" (including those spelling errors) which tried to access the same URL I in the error message from my RPi: "</\xf8\x80\x80\x80\xae\xf8\x80\x80\x80\xae repeated a bunch of times>/boot.ini". If I search "Acme Vulnerbilty Scaning Service", I get just 4 results, one of which is this previous search result, and the other three of which are duplicate results (on different paginations) of a single yolo.pcap file submitted in 2019 to the "MyCERT Pcap Analyzer" hosted by "The Honeynet Project", which appears to be a security research organization running honeypots. In the log for this file, it seems that the "Acme Vulnerbilty Scaning Service" is trying to access a very large number of different files, including the boot.ini as one of its first files (see the HTTP tab of https://pcap.honeynet.org.my/v1/submission/view.php?id=1725&dp-7-page=6&dp-2-page=1&dp-1-page=8).
From this investigation, it seems pretty clear that my RPi was attacked by a scanner (which has not been publicly described or reported) which tries to access a very large number of URLs to try to find vulnerabilities. This is a great warning sign that if we ever do open up any of our ports for remote access to the ventilator, we will need to add strong security protections, or else the frontend will be subject to attacks from the internet.
In this case, I don't have a very strong explanation for why the frontend would crash if a remote attacker tried to access a forbidden route. When I try to run wget localhost:3000/static/%f8%80%80%80%ae, the React dev server reports the same URIError but the frontend doesn't crash. It's certainly possible that the events are actually independent - that even if there is no attacker, the frontend might still crash after a long time. I'll have to continue trying to run the frontend for a long time to see what happens - next time I'll turn off wifi to remove that variable to see whether I can reproduce the crash, and I'll check to see if the Chrome DevTools console reports anything.

Solution: if we ever open wifi, we should close port 80 to the outside world. If we ever need to make the frontend and/or websocket available to the outside world, we should use a non-standard port (maybe even randomizing upon each run of the deploy script, and displaying it in the setting). Related term: "port knocking" (requires connection to ports in a certain order before access is granted) would secure against broad port scans

For now, as part of defense-in-depth we should add some functionality to our deploy_lock.sh scripts to close all ports to the outside world, even though we're also disabling wifi. In that script we should probably also add some comment about the need for port knocking if we ever open up a port to the outside world, as well as linking to this issue on things to consider before opening up any port to the outside world.


Throttle Customer.io API requests from this console command.

What's this PR do?
This pull request throttles the northstar:fix-sms-status Artisan command to 10 requests/second, in order to keep us well under the rate-limit for the Customer.io "get attributes" endpoint that it relies on for logging user details:
[2021-05-05 19:25:59] qa.ERROR: Client error: `GET https://beta-api.customer.io/v1/api/customers/56e96b3b469c64d8578b608b/attributes` resulted in a `429 Too Many Requests` response:
{"errors":[{"detail":"rate limited to 10 requests per 1s (reference 01F4YZWZX7NRJTKSN2BVW2ECY8)","status":"429"}]}
 {"exception":"[object] (GuzzleHttp\\Exception\\ClientException(code: 429): Client error: `GET https://beta-api.customer.io/v1/api/customers/56e96b3b469c64d8578b608b/attributes` resulted in a `429 Too Many Requests` response:
{\"errors\":[{\"detail\":\"rate limited to 10 requests per 1s (reference 01F4YZWZX7NRJTKSN2BVW2ECY8)\",\"status\":\"429\"}]}

How should this be reviewed?
👀
Any background context you want to provide?
A potentially more robust option would be to create a queued job that we kick off from this command, and then rate-limit that job to our "global" Customer.io throughput there. However, this "beta" API has it's own separate (much lower) rate limit, so we'd also need a separate BetaCustomerIoRateLimit middleware... and that just seems like a lot for a one-off script!
Relevant tickets
References Pivotal #177986264.
Checklist

[ ] This PR has been added to the relevant Pivotal card.
[ ] Documentation added for new features/changed endpoints.
[ ] Added appropriate feature/unit tests.
[ ] If new attributes were added to users, there is a corresponding PR to surface these in Aurora.
[ ] If new attributes were added to users, then the data team already knows about these changes.

Going to ping @weerd and @mendelB on this, since it's a quick addendum to #1189!

so we'd also need a separate BetaCustomerIoRateLimit middleware... and that just seems like a lot for a one-off script!

Agreed!


probe-run does NOT quit when Ctrl-C pressed

Describe the bug
When I launched a simple blinky program with infinite loop, probe-run v0.2.0 does NOT quit when Ctrl-C pressed，but if I switched back to v0.1.9, everything works fine.
Maybe something wrong with the signal-hook crate?

I am seeing this as well on Windows. As a workaround, in Powershell or Windows-CMD you can use Ctrl+Break to force-close probe-run

I am seeing this as well on Windows. As a workaround, in Powershell or Windows-CMD you can use Ctrl+Break to force-close probe-run

I'm using a Mac, perhaps the Ctrl-C of probe-run 0.2.0 does not work on macOS?


feat!: define Str as a wrapper type

Ideally, this change should not impact the performance.

Comparing results between 'main' and 'Current_run'
Host 'Raspberry-beetle' with 4 'aarch64' processors with 7 GB memory, running:
#1796 SMP PREEMPT Fri Sep 13 14:39:41 BST 2024

MyBenchmark
lipsum metrics
Time (wall clock): results within specified thresholds, fold down for details.

Time (wall clock) (Î¼s) *
p0
p25
p50
p75
p90
p99
p100
Samples

main
25
25
25
25
25
32
32
100

Current_run
25
25
25
25
25
26
26
100

Î
0
0
0
0
0
-6
-6
0

Improvement %
0
0
0
0
0
19
19
0

lipsum-zh metrics
Time (wall clock): results within specified thresholds, fold down for details.

Time (wall clock) (ns) *
p0
p25
p50
p75
p90
p99
p100
Samples

main
3326
3332
3336
3348
3361
3391
3398
100

Current_run
3320
3326
3328
3332
3336
3422
3548
100

Î
-6
-6
-8
-16
-25
31
150
0

Improvement %
0
0
0
0
1
-1
-4
0

medium-fragment metrics
Time (wall clock): results within specified thresholds, fold down for details.

Time (wall clock) (Î¼s) *
p0
p25
p50
p75
p90
p99
p100
Samples

main
74
74
74
74
75
75
75
100

Current_run
75
76
76
76
76
76
76
100

Î
1
2
2
2
1
1
1
0

Improvement %
-1
-3
-3
-3
-1
-1
-1
0

small-fragment metrics
Time (wall clock): results within specified thresholds, fold down for details.

Time (wall clock) (ns) *
p0
p25
p50
p75
p90
p99
p100
Samples

main
8077
8110
8135
8151
8172
8233
8442
100

Current_run
8221
8258
8274
8282
8290
8315
8360
100

Î
144
148
139
131
118
82
-82
0

Improvement %
-2
-2
-2
-2
-1
-1
1
0

strong metrics
Time (wall clock): results within specified thresholds, fold down for details.

Time (wall clock) (Î¼s) *
p0
p25
p50
p75
p90
p99
p100
Samples

main
38
38
38
38
38
38
41
100

Current_run
38
38
38
38
38
38
39
100

Î
0
0
0
0
0
0
-2
0

Improvement %
0
0
0
0
0
0
5
0

tiny-fragment metrics
Time (wall clock): results within specified thresholds, fold down for details.

Time (wall clock) (ns) *
p0
p25
p50
p75
p90
p99
p100
Samples

main
822
823
824
827
830
843
863
100

Current_run
858
862
863
865
866
874
883
100

Î
36
39
39
38
36
31
20
0

Improvement %
-4
-5
-5
-5
-4
-4
-2
0

The benchmark results were a little bit slow on some benchmarks. All of them have tag attributes, so I think the code related to attributes is the cause.


couldn't create console

Problem encountered on https://dotnet.microsoft.com/en-us/learn/dotnet/hello-world-tutorial/create
Operating System: windows
Provide details about the problem you're experiencing. Include your operating system version, exact error message, code sample, and anything else that is relevant.PS C:\Program Files\Microsoft Visual Studio\2022\Professional>  dotnet new console -o MyApp -f net7.0
Template "Console App" could not be created.
Failed to create template.
Details: Access to the path 'C:\Program Files\Microsoft Visual Studio\2022\Professioal  dotnet new console -o MyApp -f net7.0

@wretched420 maybe it's an issue on where you're trying to create the project. Have you tried changing the folder to see if it would allow you to create the project? Typically, you don't want to create new projects under the Program Files folder.


fix(providers): unifying Solana chain_id

Description
We have two chain IDs for the Solana mainnet:

solana-mainnet
solana:4sgjmw1sunhzsxgspuhpqldx6wiyjntz

We should unify the Solana mainnet chain IDs into the single standardized solana:4sgjmw1sunhzsxgspuhpqldx6wiyjntz.
This PR adds the solana-mainnet alias for the solana:4sgjmw1sunhzsxgspuhpqldx6wiyjnt to support clients that already using the solana-mainnet, but moving forward with the unified solana:4sgjmw1sunhzsxgspuhpqldx6wiyjnt for all providers.
This will solve the load balancing for the Solana chain as well.
Slack thread context.
How Has This Been Tested?
Integration test for the Solana chain.

Due Diligence

[ ] Breaking change
[ ] Requires a documentation update
[ ] Requires a e2e/integration test update

LGTM assuming Omnia supports solana:4sgjmw1sunhzsxgspuhpqldx6wiyjntz chain ID

Omnia is using sol for the solana endpoint, that doesn't changed in the PR.
solana:4sgjmw1sunhzsxgspuhpqldx6wiyjntz is ours chain_id.


Hi Kurt212. Mind sharing how you did this?

Or some resources I can use to get started. I know Python but not by heart :-)

And sorry for creating a PR, but only way I could comment on this.

Hi there!
Glad you that found my small project interesting for learning :)
Looks like I disabled issues in this repository... not I enabled them
I would suggest you to close this PR and create a new issue where I can share some information


feat comment mention

Add MentionView
Improve Mention styles
Add useHover and mention calculation
Update MentionView with simplied logic
Replace suggestion with autocomplete plugin
Refactor MentionLilst
[ ] cancel on first space not working properly for suggestions ?

@Yxwww I have opened up #109 that can come into here after your review.
It requires a few of the updates in https://github.com/curvenote/schema/pull/36


is possible using cmd name restart in case the order is changed in upstream tunasync?

is possible using cmd name restart in case the order is changed in upstream tunasync?
Originally posted by @zxkane in https://github.com/tuna/opentuna/pull/103#discussion_r494193783

Yes, will do when tunasync releases


Initial implementation of periodic worker which consists of:

AWS Lambda
AWS CloudWatch Event
AWS IAM Role

@arief-halim please review again; I've removed the require additional policy variable


LoadMode.CUSTOM cannot select tags

https://github.com/astronomer/astronomer-cosmos/blob/d28d3df7eacac74d0fbb016be70434bcc30c51be/cosmos/dbt/graph.py#L314C17-L314C25
load_via_custom_parser hard codes DbtNode.tags attribute to be an empty list
        for model_name, model in models:
           config = {item.split(":")[0]: item.split(":")[-1] for item in model.config.config_selectors}
           node = DbtNode(
               unique_id=f"{model.type.value}.{self.project.project_name}.{model_name}",
               resource_type=DbtResourceType(model.type.value),
               depends_on=list(model.config.upstream_models),
               file_path=Path(
                   model.path.as_posix().replace(
                       self.render_config.project_path.as_posix(), self.execution_config.project_path.as_posix()
                   )
               ),
               tags=[],
               config=config,
           )

This causes _is_tags_subset to return False every time
    def _is_tags_subset(self, node: DbtNode) -> bool:
      """Checks if the node's tags are a subset of the config's tags."""
      if not (set(self.config.tags) <= set(node.tags)):
          return False
      return True

because set(node.tags) is always empty.

@adammarples I just checked on the main branch, and the latest versions of Cosmos, both 1.2.5 and 1.3.0a2 should have this fixed:
https://github.com/astronomer/astronomer-cosmos/blob/173436552c8362e229258386e63ceb395fa33a44/cosmos/dbt/graph.py#L112
Could you upgrade and confirm if it works as expected, please?

Hi @tatiana this is not a problem with DBT_LS but with load via custom parser https://github.com/astronomer/astronomer-cosmos/blob/2878d6accc2a725502158247dbd1af7ac37b4449/cosmos/dbt/graph.py#L314 which is still there in 1.2.5 etc

HI @adammarples , please, could you confirm if this is still an issue in Cosmos 1.4?
Would you like to contribute to the fix?


[8.x] Allow transaction retries when savepoints disabled

In my use case, I disabled MySQL savepoints to allow DB::transaction() to retry in deadlock scenarios. However, the current logic throws the exception even though it's seemingly not necessary when savepoints are disabled. Since there is only one transaction open in MySQL, the entire transaction can be rolled back and replayed. So we check to see if the query grammar supports savepoints before throwing.

Tests broken.

After more testing, I found a different workaround and this is not necessary


Return proper error in case Android device does not have required capabilities

Proposal is to add a new error message to thaliMobileNativeWrapper.start that is returned if capabilities don't match.

@yaronyg: Let me know what you think about this or if I have overlooked and this is already specified, but my brain just doesn't remember..

This is what the networkChanged event is for. It specifies what technologies are available and identifies what requirement level we have for each. So, for example, if we get anything but ON or DO_NOT_CARE then we have a problem and know we can't run on that device. So the real question is - do we have a test for this where we turn off bluetooth or wifi or whatever and see if we get the right result back? We could at least test that on Android.

Thanks for reminding that networkChanged is the "public API" for this functionality. I added a basic test at https://github.com/thaliproject/Thali_CordovaPlugin/pull/612/commits/ece3ba07697fefbb09157c7f99e564b7cf4db2f2 which seems to work on a device that doesn't support the BLE as we require.

@vjrantal So does that mean we can now close this?

Yes. I think the basic test covers it.


Symbol artboards not collapsing

After organising symbols on the Symbols page, all artboards were collapsed (which was really useful).
This is no longer the case.
THX

@cpshanley I am going to guess you were using titles? I just resolved a bug introduced with Sketch 53; title group now requires fixGeometryWithOptions instead of resizeToFitChildrenWithOption. I just fixed this in 15.9. Can you confirm?

Brilliant. Works a treat. Terrific plugin. Cheers.


Should the Emscripten library_webgpu be used instead?

Copying it from the master Emscripten branch to get the latest binding? Google was a little concerned about having multiple bindings. I started using this version at the beginning because it's convenient to be able to modify it. I haven't studied the two in comparison to see what the advantages are otherwise. The Emscripten library_webgpu version does seem to be lagging behind the current spec, it doesn't appear to have the GPUPresentationContext functions and still has the swap chain.

We have been discussing this bindings project with Google before. The current Emscripten bindings are a bit verbose, not geared as aggressively towards tiny code size, performance and minimal generated garbage in mind as I would have liked, hence starting this one.
That is not to say that the upstream bindings would be somehow bad - just that I did not find using it preferable. That could be due to having grown quite particular to how the existing WebGL bindings layer should look for best results to my liking, and expecting the same for my WebGPU bindings library.
The major design difference is that upstream Emscripten bindings library utilizes ref-counting, so C/C++ side needs to do more manual releasing of object refcounts in certain cases. This bindings layer uses traditional WebGL/OpenGL-style delete functions without reference counters, and aims to minimize the need to manually remember to delete different objects with explicit API calls. (hence e.g. the submit_one_and_destroy() style of API)
Both bindings have a current drawback that they lack test cases, hence the outdatedness of upstream Emscripten library showing, and also the silly typos/mistakes like you are seeing in this library. (great work reporting these!)
The upstream Emscripten bindings layer has a goal to be compatible with native Dawn API, so that one can co-target Dawn and WebGPU from the same codebase. This bindings library does not have that goal. Also the upstream bindings layer provides a C++ class-based API, which this library does not pursue.
Last time I looked, the Emscripten bindings library did not have completed the context initialization sequence, but expected a preinitialized Module['preinitializedWebGPUDevice'] WebGPU device to have been created via manual JS code. So there are currently no "self-contained" C examples to use the upstream Emscripten bindings layer.
Also both libraries have different sets of missing items/TODOs atm.
Also since this bindings library does not aim for Dawn native compatibility, I have taken liberties with the API design in places to ease/improve marshalling. Beyond the non-refcounting aspect and functions such as wgpu_queue_submit_one_and_destroy(), the examples that come to mind so far:

struct ABI layout differs from the WebIDL in certain places to simplify padding and 32-bit wide reads from JS, and to help polymorphed descriptor reads,
64-bit integers are not used in some function calls, but doubles are used instead, supporting only up to 2^53 large integers, (which should be plenty enough - BigInts could be used in the future)
some descriptor structs are removed, and instead the functions take the descriptor args flattened as function parameters, see e.g. wgpu_queue_write_texture() and wgpu_queue_copy_external_image_to_texture(). This is done to simplify marshalling, though could come back to bite, but not much of an issue atm since backwards compatibility is not yet a thing. (we'll see how these live)
accessing buffer mappings is done via a custom API to avoid memcpy width problems and allow windowed reads and writes. See the vertex_buffer example, and wgpu_buffer_get_mapped_range(), wgpu_buffer_read_mapped_range() and wgpu_buffer_write_mapped_range() functions. That populates a several MB vertex buffer by having just a few hundred KBs of Wasm heap size.
currently, a random set of custom API functions, like wgpu_enum_to_string(), wgpu_get_num_live_objects(), wgpu_object_destroy(), wgpu_is_valid_object(), wgpu_is_*() are provided.

I'll close this issue, since the intent here is not for the upstream Emscripten bindings layer to replace this bindings layer. At the moment the intent is neither to have this bindings library replace the upstream Emscripten bindings layer (mainly because of the Dawn incompatibility, but also because I don't know if I will have the cycles to step up to own maintainership if I did push this upstream), although that thought was briefly entertained in one call with Google.


Getting "Cannot read property 'hasDescendants' of undefined"

at Assertion.descendants (/Users/matthew.spence/Projects/tripapplite/node_modules/chai-enzyme/build/assertions/descendants.js:13:22)
      at Assertion.<anonymous> (/Users/matthew.spence/Projects/tripapplite/node_modules/chai-enzyme/build/index.js:139:19)
      at Assertion.ctx.(anonymous function) [as descendants] (/Users/matthew.spence/Projects/tripapplite/node_modules/chai/lib/chai/utils/addMethod.js:41:25)
      at Context.<anonymous> (/Users/matthew.spence/Projects/tripapplite/app/assets/javascripts/tripapp_specs_mocha.js:218703:53)
      at callFn (/Users/matthew.spence/Projects/tripapplite/node_modules/mocha/lib/runnable.js:250:21)
      at Test.Runnable.run (/Users/matthew.spence/Projects/tripapplite/node_modules/mocha/lib/runnable.js:243:7)
      at Runner.runTest (/Users/matthew.spence/Projects/tripapplite/node_modules/mocha/lib/runner.js:373:10)
      at /Users/matthew.spence/Projects/tripapplite/node_modules/mocha/lib/runner.js:451:12
      at next (/Users/matthew.spence/Projects/tripapplite/node_modules/mocha/lib/runner.js:298:14)
      at /Users/matthew.spence/Projects/tripapplite/node_modules/mocha/lib/runner.js:308:7

Can you provide a bit of the code you used to get this error, and which versions of chai-enzyme and enzyme and chai and mocha you are using?

I'm closing this because it's not clear what's causing this, or what versions are being used, feel free to re-open when there is a more detailed bug report.

Sorry, might have time to look at this today, will reopen with more info when I can


Following the issue #93 adding prettier to the project

In #93 pre-commit hooks have been added but for consistent formatting adding prettier is necessary and configuring the prettier to work with lint-staged and pre-commit hooks
@MAVRICK-1 I would like to work on the this issue under gssoc

@AvdhutPailwan don't make a separate PR  for this include this in #118 , i will mark it level3

@AvdhutPailwan don't make a separate PR  for this include this in #118 , i will mark it level3

Okay

@AvdhutPailwan but i will check it after , 18 . won't be available for few days

@AvdhutPailwan but i will check it after , 18 . won't be available for few days

I am already done ✅


fmt(printer): print check results as a table

Formats outcomes into a table
Signed-off-by: Sanya Kochhar<EMAIL_ADDRESS>

Unfortunately tabwriter is enforcing this spacing, do we want it or should we abandon this change for now?


Localised interpolation

Currently paths are interpolated at the same threshold everywhere. Would be beneficial to have localised interpolation so that large SVG's that only distort in certain areas (like a smudging tool) can have improved performance.

This could possibly work by still interpolating the points, but only outputting the points needed in the SVG. In other words, if an interpolated point is still in the same position it was in when it was interpolated, then don't output it.
This does bring up a lot of issues, such as having to retain positions of points before and after interpolation, and defining "same position" (for example, if all points around the interpolated point are affine transformed, then the point still doesn't need to be outputted even though it is technically not in the same position).


add Functions for plugin

I added a few optional functions for the plugin, making it possible to use the username instead of the fullname and adding support for gravatar.

I was informed that I made some mistakes, so I’ll close this pull request and submit a new one at a later time.


Map of boathouses

I was looking at some of the stuff Mystic River's flagging program has. https://mysticriver.org/boatingadvisory and I really liked the map.
Can we create a map of boathouses using a tool that lets you put pins on a map? We already have geocoordinates in the database. Might be interesting to add.

I'll work on this one

I'll work on this one

Good progress on this so far. A couple more updates and it will be perfect 🎊

Good progress on this so far. A couple more updates and it will be perfect 🎊

Pull request 163 has made it even better

Really like where this is right now. Closing it. Thanks so much for your work here.


feature/custom-classnames – added ability to add custom classes

Coverage decreased (-0.5%) to 99.204% when pulling 444ed6d8e308c2cdfb3c6c92f900cf623932c212 on ibm-gpn:feature/custom-classnames into d0bbe8d3f9fb6e39775a86802b65ecff587be462 on bkrem:master.

Thank you for adding these two props @deshaser! :)
Apologies for the wait, I've been hammering away on the v2 branch for the past few weeks, which included integrating this feature ahead of v2 finally landing in master in the coming days.
In order to align with the upcoming v2 API, I've adjusted the prop naming slightly:
- rename `className` -> `svgClassName`
- rename `pathClass` -> `pathClassFunc`

I'll follow up here once this change has been published in a release.

Published as v1.17.0 🚀


🚧 Dev ➾ skip FLAKY test in jest plugin - only the tests matching a test pattern will run inside of a test partition

🔗 Epic|Feature Link
No response
🚥 Definition of Done

[ ] 🎯 Planning and Design
[ ] 🏎 Dev Implementation Complete
[ ] ♾ PR Merged
[ ] 🏆 Product Acceptance

🧰 Work Description
Skip the FLAKY test in jest plugin - only the tests matching a test pattern will run inside of a test partition
✅ To Do
skip FLAKY test in jest plugin - only the tests matching a test pattern will run inside of a test partitionSkipthe
⚖ Acceptance Criteria
✨ Functional:

[ ] cicd passes
[ ]

🔭 Scope
🙅♂ Out of Scope:

...

other plugins
Code of Conduct

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

done


setTestEventCode should be optional, but it isn't

In the docs, it says that setTestEventCode is optional, but when removed, it returns error stating that test_event_code cannot be null. Does it make sense to add that to the call only if its provided? If I remove setTestEventCode like so, it throws an error requiring the code.
This does not work, but should if its optional:
$eventRequest = $tiktok->events()
            ->setEventSource(\Msaaq\TikTok\Enums\EventSource::WEB);
            //->setTestEventCode('TEST01234');

I spent a whole day trying to figure it out, and since this was not fixed for almost a year now here's a solution I used to patch it:

Install composer require cweagans/composer-patches:~2.0

Create a file in your project root -> patches/msaaq/tiktok-php-sdk/optional-test-event-code.patch with the following content:

Index: src/Requests/EventRequest.php
IDEA additional info:
Subsystem: com.intellij.openapi.diff.impl.patch.CharsetEP
<+>UTF-8
===================================================================
diff --git a/src/Requests/EventRequest.php b/src/Requests/EventRequest.php
--- a/src/Requests/EventRequest.php
+++ b/src/Requests/EventRequest.php	(date<PHONE_NUMBER>886)
@@ -53,14 +53,19 @@
         foreach ($events as $key => $event) {
             $events[$key] = $event->toArray();
         }
-
-        $request = $this->http->post('/event/track/', [
+
+        $requestData = [
             'event_source' => $this->event_source->value,
             'event_source_id' => $this->event_source_id,
-            'test_event_code' => $this->test_event_code,
-
+
             'data' => $events,
-        ]);
+        ];
+
+        if ($this->test_event_code !== null) {
+            $requestData['test_event_code'] = $this->test_event_code;
+        }
+
+        $request = $this->http->post('/event/track/', $requestData);

         $request->onError(function ($request) {
             throw new \Exception($request->json('message'));

Add this to your composer.json:

    "patches": {
      "msaaq/tiktok-php-sdk": {
        "Make test_event_code optional": "patches/msaaq/tiktok-php-sdk/optional-test-event-code.patch"
      }
    }

In terminal:

cd vendor/msaaq/tiktok-php-sdk
patch -p1 < ../../../patches/msaaq/tiktok-php-sdk/optional-test-event-code.patch

If it works, the patch will be automatically applied when you run composer install or composer update from now on. Since you already applied it manually above (to debug) it will not be re-applied but the procedure remains the same for other patches. To easily make the patch use PHPStorm: make changes to the vendor file you want to change, open local file history and there will be a patch button which will automatically create the patch content for you.

Hope that helps. Really unfortunate when such an easy fix to a very critical issue is not applied by the team who built it, but hey, this is why we use Github.


ngen failed to compile FSharp.Compiler.Private.dll

Error compiling ...\packages\FSharp.Compiler.Tools\tools\FSharp.Compiler.Private.dll: Invalid access to memory location. (Exception from HRESULT: 0x800703E6)
1>Uninstalling assembly e:\hg\klsrl.core\packages\FSharp.Compiler.Tools\tools\FSharp.Compiler.Private.dll because of an error during compilation: Invalid access to memory location. (Exception from HRESULT: 0x800703E6)
Invalid access to memory location. (Exception from HRESULT: 0x800703E6)

Repeatable?

Yes.

I'll try at home, maybe it's the antivirus again.

Everything is OK at home.


feat: disable wakelock optionally

Closes #113

@Hwan-seok Thank you for the PR, we need to optionally disable Wakelock in _switchToFullscreen and _exitFullscreen as-well. As there are formatting issues in the PR, we are manually adding the fix.

Sure, Thanks.


Iteration Planning

In this session, Active members discuss about the content of the next iteration.
https://github.com/ev3dev-lang-java/ev3dev-lang-java/milestone/10
In the backlog exist a set of issues categorised in the following areas:

Infrastructure
Internal Refactoring
Design
Performance
ROS
Communications

We should discuss about that backlog to define the issues to include. Exist issues in others iterations or without any iteration assigned:
https://github.com/ev3dev-lang-java/ev3dev-lang-java/issues?q=is%3Aopen+is%3Aissue+no%3Amilestone
https://github.com/ev3dev-lang-java/ev3dev-lang-java/issues?q=is%3Aopen+is%3Aissue+milestone%3Av1.0.0
It could be interesting the discussion.

If you are interested, you could discuss the new issues to be included in the next iteration:
@lycos44, @aivars-sablis, @jweijers, @jartu

Hi mates,
my proposal for this iteration is:

Infrastructure

https://github.com/ev3dev-lang-java/ev3dev-lang-java/issues/479 establish a physical environment to test Bricks/Sensors in a fast way. Current model is not fast. I mix bricks for personal projects and testing purposes. Besides, it is necessary to add the complexity of different Debian distros.
https://github.com/ev3dev-lang-java/ev3dev-lang-java/issues/466 it is a great opportunity to use common Java infrastructure
https://github.com/ev3dev-lang-java/openjdk-ev3/issues/23 Try to compile again OpenJDK 10 with the Docker image FROM debian:8.9 for Debian Jessie support

Internal Refactoring

https://github.com/ev3dev-lang-java/ev3dev-lang-java/issues/443 Close the development of common library with support for Debian Jessie & Stretch and testing. Increase Coverage.
https://github.com/ev3dev-lang-java/ev3dev-lang-java/issues/436,
https://github.com/ev3dev-lang-java/ev3dev-lang-java/issues/437,
https://github.com/ev3dev-lang-java/ev3dev-lang-java/issues/358 Internal refactoring

New features

https://github.com/CONNEX-AB-Delivery-System/DS-DeliveryTruck/issues/1 Add Mindsensors LineReaderV2 support
https://github.com/ev3dev-lang-java/ev3dev-lang-java/issues/483 Add Mindsensors MotorMultiplexer support

Performance

https://github.com/ev3dev-lang-java/ev3dev-lang-java/issues/212,
https://github.com/ev3dev-lang-java/ev3dev-lang-java/issues/270 Add support on Installer/Template to offer more memory for EV3 Brick
https://github.com/ev3dev-lang-java/ev3dev-lang-java/issues/444,
https://github.com/ev3dev-lang-java/ev3dev-lang-java/issues/445 Study the way to offer an alternative to current FatJar solution

Communication

https://github.com/ev3dev-lang-java/ev3dev-lang-java/issues/202 To Add articles about the usage of the project.

What is your opinion?

Fixed planning


PHOENIX-6102 Better isolation for CI jobs an ASF Jenkins

run post-commit tests in Docker
also don't mask Hadoop exception when tests break on anonymous unix user

Tested on https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-experiment/
We lose 5-10 minutes on not having a maven cache, but we are guaranteed not to have conflicts with installed modules either.


Gaurav user

This request basically moves our dev branch to our master, which we're not ready to do at this time.