test: [M3-8619] - Fix Cypress test flake in create-linode-from-image.spec.ts

Description 📝
This fixes the intermittent test failures we've been seeing in create-linode-from-image.spec.ts, and possibly other specs, which occur when Cypress tries to select a region with a name that's similar to another region. Specifically, tests in this spec fail consistently when trying to select UK, London (eu-west) because UK, London 2 (gb-lon) also gets matched.
This issue was triggered by recent changes to our region select UI helpers, intended to facilitate region selection when Gecko is enabled (#10888).
Changes  🔄

Increases specificity of region selection RegEx to account for regions with similar names

Target release date 🗓
N/A
How to test 🧪
Reproduction steps
Check out develop and build Cloud via yarn && yarn build && yarn start:manager:ci, then:

Run CY_TEST_REGION='eu-west' yarn cy:run -s "cypress/e2e/core/images/create-linode-from-image.spec.ts"

ℹ CY_TEST_REGION forces Cypress to select the desired region every time -- normally, a random region is selected

Observe that all 3 tests fail every time

Verification steps
Check out this branch and build Cloud via yarn && yarn build && yarn start:manager:ci, then:

Run CY_TEST_REGION='eu-west' yarn cy:run -s "cypress/e2e/core/images/create-linode-from-image.spec.ts"
Run CY_TEST_REGION='gb-lon' yarn cy:run -s "cypress/e2e/core/images/create-linode-from-image.spec.ts"
Confirm that tests pass in both cases
Optionally confirm that test passes when Gecko LA is enabled and when it's disabled

I ran the spec 15 times in a row (with random regions) and all 3 tests passed every time.
As an Author I have considered 🤔
Check all that apply

[x] 👀 Doing a self review
[ ] ❔ Our contribution guidelines
[ ] 🤏 Splitting feature into small PRs
[x] ➕ Adding a changeset
[x] 🧪 Providing/Improving test coverage
[ ] 🔐 Removing all sensitive information from the code and PR description
[ ] 🚩 Using a feature flag to protect the release
[ ] 👣 Providing comprehensive reproduction steps
[ ] 📑 Providing or updating our documentation
[ ] 🕛 Scheduling a pair reviewing session
[ ] 📱 Providing mobile support
[ ] ♿  Providing accessibility support

Merging despite test failures:

Both failing tests are known to be flaky and aren't caused by this PR (one has an open PR of its own)
The tests this PR is meant to address are passing


[dv, fcov] Debug related coverage holes

@hcallahan-lowrisc assigned to all of these
The following debug related coverpoints are not yet being hit:

[ ] Some categories for single stepping over each instruction category - cp_single_step_instr - Orig Estimate 4. Remain 2022-07-28 2. Remain 4 2022-08-01. Remain 4 2022-08-03. Remain 1 2022-08-10.

[ ] CSRAccess
[ ] EBreakDbg
[ ] EBreakExc
[ ] ECall
[ ] MRet
[ ] DRet - Illegal bin?
[ ] WFI
[ ] Fence
[ ] FenceI
[ ] FetchError
[ ] CompressedIllegal
[ ] UncompressedIllegal
[ ] CSRIllegal
[ ] PrivIllegal

[ ] Hardware breakpoint triggered - cp_insn_trigger_enter_debug - Orig Estimate 8. Remain 8.
[ ] Hardware breakpoint on instruction that causes an exception cp_insn_trigger_exception - Orig Estimate 8. Remain 2022-07-28 6

Note for some of the single step instruction categories it's possible we simply cannot trigger the coverpoint for those. However from an initial look I think it should be possible for all of them (other than None)
Original HW/PM estimate 20

estimate 30
remaining 2022-07-27 16
remaining 2022-08-01 18
remaining 2022-08-03 18
remaining 2022-08-10 15

Update for 2022-07-27 : In progress for cp_single_step_instr 2 remaining
Also now 6 remaining for cp_insn_trigger_enter_debug

Update for 2022-08-01 : In progress for cp_single_step_instr, increased remaining to 4

Update for 2022-08-03 : In progress for cp_single_step_isntr, remaining still at 4, revised estimate up +4

Update for 2022-08-10 : In progress for cp_single_step_instr, remaining 1

Update for 2022-08-16 : In progress for cp_insn_trigger_* coverpoints, remaining 4 for each.
I'm working on a new directed stream for riscv_dv which inserts a short sequence of instructions which enable the trigger and set the address to a randomly-generated insn at the end of the stream. With appropriate randomization this should allow us to hit both coverpoints.

Update for 2022-08-23 : In progress for cp_insn_trigger_* coverpoints, remaining 2 for each.

Update for 2022-08-26 : In progress for cp_insn_trigger_* coverpoints, remaining 1 for each. Just need to do a little tidyup and create some PR's.


How to filtering photos with username and hashtag (both)?

Before submitting an issue, make sure you have:

[x] Updated to the lastest version v1.3.6
[x] Read the README and docs
[x] Searched the bugtracker for similar issues including closed ones
[x] Reviewed the sample code in tests and examples

Which client are you using?

[x] app (instagram_private_api/)
[ ] web (instagram_web_api/)

Purpose of your issue?

[ ] Bug report (encountered problems/errors)
[ ] Feature request (request for a new functionality)
[x] Question
[ ] Other

For a bug report, you must include the Python version used, code that will reproduce the error, and the error log/traceback.
Paste the output of python -V here: Python 3.6.1
Describe your issue
Hello. This is small question, I doesn't found on docs.
How to filtering photos with username and hashtag (both)? This package can do it? How?

You can't.


syslinux: fix GCC14 build issue

fixes #367703
based on a patch from Fedora 40 applied to OpenEmbedded Core (https://lists.openembedded.org/g/openembedded-core/topic/patch_syslinux_fix_build/105858862)
Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

see also: #367685


Confirmation Popup when switching Projects whether to use "This Window" or "New Window" like the one in Intellij IDEA

Type: Feature Request

Current Condition
When I want to open two new projects in VS Code, it feels a bit troublesome because I have to open a new window and then select the project folder. This workflow is a bit long. Maybe it would be nice to add a simple feature like in IntelliJ IDEA, so that it is easier to switch projects or open a new window with a different project.
Feature
Confirmation Popup when switching Projects whether to use "This Window" or "New Window" like the one in Intellij IDEA

Typically using Ctrl key when selecting a recent workspace to open allows to force a new window or same window.

Nice shortcut, I just found out about it.


UnknownOperationException after trying to send data

Hi!,
I'm trying to send data to an existing stream and I'm getting.
{ [UnknownOperationException: {"__type":"UnknownOperationException"}]
statusCode: 400,
name: 'UnknownOperationException',
message: '{"__type":"UnknownOperationException"}' }

There's not much information about the available operations. I assume that putRecord should be used based on a couple of issues submitted.
This is my code
kinesis.request('putRecord',
    {
        "a":"aa",
        "b":"bb",
        "c":[
            {
                "d":"dd",
        ]},
    {StreamName: 'streamName'}, function(err) {

    if (err) {
        console.log(err);
    }
});

What am I doing wrong?
Thanks.

The action name is PutRecord: http://docs.aws.amazon.com/kinesis/latest/APIReference/API_PutRecord.html
(note the capital P)

Thanks!


"setBlock() generated out of bounds range offset"

MapGenerator is slightly unstable and creates calls to setBlock() that generate out of bounds range offsets for placing blocks in the GridSpace. This results in 80 warnings spammed to the debug log, seems to work regardless but it needs to be removed

I'm really not sure if this was a problem to begin with. It makes sense that some gridobjects might have larger real world positions than the actual grid index they reside in, considering the grid coordinates are really only the bottom leftmost coordinate of the gridobject. Perhaps it could be a good check if we checked whether or not they were more than 1 entire gridspace off, and I'll be adding that functionality in a future commit but for now I have simply disabled this warning in commit ID 8506301ba04e3400e7365c8d3230588428203fef

Just did some testing, it appears that the offset check was assuming that the map was going to be 20x20 when in reality it is 20x20*2 because of the actual grid size spacing. fixed in d34deb8c62881121af00c44342653d74599349ce


Limitations

Know that I can use it I really enjoy Emojicode and after looking at the small amount of project existing, I saw web server and I was wondering why there some limitations? Not the most recent http, no css or javascript etc

Which web server are you referring to? We don't provide any, so I can't really answer your question. Generally speaking, JavaScript and CSS don't require web server support, though. Emojicode also does not prevent you from implementing HTTP/2, for example.

I took the webserver from xenthy on Github as an example, that's why. But how would you implement html 2.0 or javascript / css into an emojicode project? Because there is not a lot of documentation about more complex things like this

There is no inherent relation between front-end web technologies and Emojicode. Emojicode is a general-purpose programming language, not a web framework. Looking at xenthy's web server implementation, you could place HTML, CSS, and JavaScript files into a directory and access them via the browser, as you would do with an Apache server.


Nightly job don't trigger any more

There are commits / merges to main recently, but the last time the highly job runs was at 11-27-2022.
Most likely the GitHub token in nightly action expired.

Pushed an alternative approach, let's see if it works

The nightly job now runs and submits a ne test build to iOS AppStore.
Nice job.

Gonna keep this open for another day to see if skipping also still works


BlueLink: extend TLS Handshake timeout

possibly fix #17100
@andig I am not too happy with this change, as I had to create a separate http transport.
I did so, because I did not see any way to access the Fields of the existing Transport in our http client. The http client does only expose its transport as a RoundTripper interface, which effectively hides the fields.
Alternatively I could downcast the RoundTripper to http.Transport explicitly, but I was not sure if this is really better. What do you think?

found a more compact solution via type assertion.


Exception in the migration tool

When I run the migration tool on pkg/test_runner in the SDK, it throws an exception. The UI loads with --ignore-exceptions.
$ tools/sdks/dart-sdk/bin/dart --version
Dart SDK version: 2.12.0-0.0.dev (dev) (Thu Oct 29 12:24:51 2020 -0700) on "macos_x64"

$ tools/sdks/dart-sdk/bin/dart migrate pkg/test_runner
Migrating /Users/user/src/sdk/pkg/test_runner

See https://dart.dev/go/null-safety-migration for a migration guide.

Analyzing project...
[                                                                                ]Warning: Could not find the package configuration file.
  /Users/user/src/sdk/pkg/test_runner/.dart_tool/package_config.json

  Be sure to run `pub get` before examining the results of the migration.

[------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------\]No analysis issues found.

Generating migration suggestions...
[--------------------------------------------------------------------------\                                                                                ]Aborting migration due to an exception.  This most likely is due to a
bug in the migration tool.  Please consider filing a bug report at:

https://github.com/dart-lang/sdk/issues/new
To attempt to perform migration anyway, you may re-run with
--ignore-exceptions.

 This was from 2.12.0-0.0.dev.

I can still reproduce this with the latest code as of 5af2d78e75a45042f97b50fa01beb59af1dacbae.  Investigating now.

The problem turned out to be that the code being migrated contained a for-each loop where the loop variable was not local.  This infrequently-used corner of the language wasn't properly handled by the migration tool.  Working on a fix here: https://dart-review.googlesource.com/c/sdk/+/174565


Istio uninstallation cleans up Gateway created by net-istio.yaml

This might be an issue in operation not net-istio, but I report the issue here as a Knative user was confused.
Issue description

If we uninstalled Istio, Gateway (cluster-local-gateway, knative-ingress-gateway) in knative-serving namespace also gone as istioctl deletes CRD.

Step to reproduce the issue
1. Install istio by following doc
$ istioctl manifest apply -f istio-minimal-operator.yaml

2. Install Knative Serving and net-istio
$ kubectl apply --filename https://storage.googleapis.com/knative-nightly/serving/latest/serving-crds.yaml
$ kubectl apply --filename https://storage.googleapis.com/knative-nightly/serving/latest/serving-core.yaml
$ kubectl apply --filename https://storage.googleapis.com/knative-nightly/net-istio/latest/release.yaml

3. Knative app works fine
$ kn service create hello-example --image=gcr.io/knative-samples/helloworld-go

$ kubectl port-forward -n istio-system service/istio-ingressgateway  8000:80
Forwarding from <IP_ADDRESS>:8000 -> 8080
Forwarding from [::1]:8000 -> 8080
Handling connection for 8000

$ curl -H "Host: hello-example.default.example.com" localhost:8000
Hello World!

4. Re-installing Istio
Do not touch Knative, but just re-install Istio.
$ istioctl manifest generate -f istio-minimal-operator.yaml | kubectl delete -f -
$ istioctl manifest apply -f istio-minimal-operator.yaml

5. Knative becomes unreachable
Now, Knative app started unreachable.

port-forward starts producing following error

$ kubectl port-forward -n istio-system service/istio-ingressgateway  8000:80
Forwarding from <IP_ADDRESS>:8000 -> 8080
Forwarding from [::1]:8000 -> 8080
Handling connection for 8000
E0813 15:22:23.690783    4348 portforward.go:400] an error occurred forwarding 8000 -> 8080: error forwarding port 8080 to pod fb1991564571888471fc564b2a2fe08f528fea1ceeafe99db8fef57f4564a310, uid : exit status 1: 2020/08/13 06:22:23 socat[199389] E connect(5, AF=2 <IP_ADDRESS>:8080, 16): Connection refused
Handling connection for 8000

Access gets Empty reply from server.

$ curl -H "Host: hello-example.default.example.com" localhost:8000
curl: (52) Empty reply from server

Root cause of this issue
This is because Gateway in knative-serving ns was deleted in step-4. We need to re-install Gateways in net-istio.yaml.
cat <<EOF | kubectl apply -f -
apiVersion: networking.istio.io/v1alpha3
kind: Gateway
metadata:
  name: knative-ingress-gateway
  namespace: knative-serving
  labels:
    serving.knative.dev/release: "v20200811-4a3c487"
    networking.knative.dev/ingress-provider: istio
spec:
  selector:
    istio: ingressgateway
  servers:
  - port:
      number: 80
      name: http
      protocol: HTTP
    hosts:
    - "*"
---
apiVersion: networking.istio.io/v1alpha3
kind: Gateway
metadata:
  name: cluster-local-gateway
  namespace: knative-serving
  labels:
    serving.knative.dev/release: "v20200811-4a3c487"
    networking.knative.dev/ingress-provider: istio
spec:
  selector:
    istio: cluster-local-gateway
  servers:
  - port:
      number: 80
      name: http
      protocol: HTTP
    hosts:
    - "*"
EOF

I wonder that Gateway (cluster-local-gateway, knative-ingress-gateway) should not be included in net-istio.yaml, but net-istio controller should create it if not exist.

I wonder that Gateway (cluster-local-gateway, knative-ingress-gateway) should not be included in net-istio.yaml, but net-istio controller should create it if not exist.

Yes. Another scenario where this becomes a problem is when managing knative with gitops:

The gitops controller applies net-istio.yaml, which in turn creates the knative Gateway resources
The net-istio controller mutates the Gateway resources (e.g. adding TLS information for a ksvc).
At some point in the near future, the gitops controller re-applies net-istio.yaml. This may clobber mutations made by  the net-istio controller.

Also note that upgrading net-istio by applying a new version of the net-istio.yaml manifest can have the same effect. This is because some mutations (in my case TLS configuration as part of cert-namespace) are not compatible with a patch-strategic-merge. Therefore, I believe that the lifecycle of all Gateway resources should be managed by the net-istio controller and should not be included in net-istio.yaml.

Thank you so much @tshak That is great input.

/remove-lifecycle stale


deps: update actions/github-script action to v3.1.0

This PR contains the following updates:

Package
Type
Update
Change

actions/github-script
action
minor
v3.0.0 -> v3.1.0

Release Notes

actions/github-script
v3.1.0
Compare Source
This release adds the latest Octokit dependencies.
v3.0.2
Compare Source
I made an error in building v3.0.1, and this resolves that.
v3.0.1
Compare Source
This release bumps actions-core to 1.2.6.

Renovate configuration
📅 Schedule: At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

Codecov Report

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

@@             Coverage Diff              @@
##             reproduce       #3   +/-   ##
============================================
  Coverage             ?   69.90%
  Complexity           ?      220
============================================
  Files                ?       23
  Lines                ?     1668
  Branches             ?       46
============================================
  Hits                 ?     1166
  Misses               ?      457
  Partials             ?       45

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 97fbd5c...30f9db5. Read the comment docs.


Migrate to GINKO/v2

Signed-off-by: Carlos Eduardo Arango Gutierrez<EMAIL_ADDRESS>What type of PR is this?

What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #94
Special notes for your reviewer:

as part of investigating #101

/retest-required

/retest-required

/retest-required

Prow flake, run never started and hit the time limit

/assign @alculquicondor

/lgtm
/approve

/hold

/hold

Requested change is done ✅
/hold cancel

/lgtm
On Wed., Mar. 9, 2022, 5:28 p.m. Carlos Eduardo Arango Gutierrez, <
@.***> wrote:

/hold
Requested change is done ✅
/hold cancel
—
Reply to this email directly, view it on GitHub
https://github.com/kubernetes-sigs/kueue/pull/107#issuecomment-1063435737,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAJ5E6BNY7IGKFBTATT5J7LU7EQYXANCNFSM5QKXWKCQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were assigned.Message ID:
@.***>


Documentation

Writing some documentation for this package

Raw Markdown
Plan of the doc

- how to install the package?

```sh
pip install ...
```

- what does it do?

  - Provides a cli for building Jupyter extensions. There is 3 subcommands
    - `build`: Build the Jupyter extension JavaScript assets to be consumed by the Jupyter app
    - `develop`: Install the Jupyter extension JavaScript assets in dev mode for consumption in the Jupyter app. It similar to [_editable_ install mode of pip](https://setuptools.pypa.io/en/latest/userguide/development_mode.html).
    - `watch`: Automatically rebuild the development JavaScript assets when one file is changed to ease development.

  - Provides a NPM package manager: `jlpm`
  - [maybe] Provides a NPM package hosting JavaScript asset building configuration (aka `@jupyterlab/builder` see #16)

- how to uninstall the package?

```sh
pip uninstall ...
```

- how to contribute?

> You describe how to install it in development mode and how to test the package

Plan of the doc

how to install the package?

pip install ...

what does it do?

Provides a cli for building Jupyter extensions. There is 3 subcommands

build: Build the Jupyter extension JavaScript assets to be consumed by the Jupyter app
develop: Install the Jupyter extension JavaScript assets in dev mode for consumption in the Jupyter app. It similar to editable install mode of pip.
watch: Automatically rebuild the development JavaScript assets when one file is changed to ease development.

Provides a NPM package manager: jlpm

[maybe] Provides a NPM package hosting JavaScript asset building configuration (aka @jupyterlab/builder see #16)

how to uninstall the package?

pip uninstall ...

how to contribute?

You describe how to install it in development mode and how to test the package

Markdown tricks for GitHub:
Add links
text to display
Display code snippet :warning: only works in GitHub for issues and pull requests:
https://github.com/jupyterlab/jupyterlab-builder/blob/c04e4a2523df1ccbfc2d4bf9edb34cdd2bd25fb3/jupyter_builder/federated_extensions_requirements.py#L41-L50

[!Note]
This a note

[!WARNING]
This warning

Link to GitHub documentation: https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax

Closed by #22


Typo on the ToolTip text of the Connector field on the Email Account Wizard page in System Application

It should be Specifies instead. Found in 18.0.22893.23773

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.

Availability update: We will publish a fix for this issue in the next update for release 19.


Multi tenancy with Identity Manager

Hi, I want to try your solution, does this support the previous multi tenancy you talked about.

Yes it does. Identity Manager is metadata driven, so if the Tenant Id is a primitive type it will load on the user screens.


Obtaining an original length in DynRealDft struct

Hi,
I wondered if there is a way to obtain an original length from DynRealDft struct.
I need the information of the original length to do the ifft, but it is stored in a private variable, and I was wondering if there is a way to obtain them by api.
Right now, I can only find a way to read the length that is already halved, in which if I try to reconstruct the original length it can only be reconstructed in 50% probability.

I need the information of the original length to do the ifft, but it is stored in a private variable, and I was wondering if there is a way to obtain them by api.

Why do you need it? Can't you just call the .ifft() method?

@WalterSmuts
Thank you for the reply and sorry for the late response.
I am currently working on the field of X-ray absorption spectroscopy; we need to extract parameters from a theoretical formula that resembles sin waves. However, since it is not a pure sin wave nor a periodic data, we do a lot of post-processing on the frequency spectra we obtain from FFT.
For this purpose, I am converting DynRealDft to ndalgebra or ndarray. Right now, the original length is stored in other struct prior to the FFT so that I don't lose the information, but I was wondering if I could store and retrieve it from DynRealDft struct.
I am working on analytical method that uses

Closing this issue in favour of #4


Use primer/react-scripts toolchain

Part of the toolchain for component development

Before we start asking other teams to start using the toolchain,
we should use it in internal repos to test the experience

Replaces local storybook setup with primer/react-scripts. Still allows for project specific customisation. See .storybook/main.js and .storybook/preview.js
~The canary version is intentional, @primer/react-scripts is still a proof of concept and does not publish a stable version yet. The package name and script name might change.~ Now using stable version :)
Similar PR in memex: https://github.com/github/memex/pull/9638

Circular dependency problem:
@primer/react-scripts has a peer dependency on @primer/react, so when we import something from @primer/react in this repo (primer/react) it wouldn't exist because we don't want to install another copy of primer/react 😅
ModuleNotFoundError: Module not found: Error: Can't resolve '@primer/react/lib-esm/utils/story-helpers' in '/Users/sid/code/primer/react/node_modules/@primer/react-scripts/storybook'

@colebemis Do you know why CI is failing on this, looks like an unrelated change but it doens't fail on main 🤔
Could be because of a potential eslint version change?

@colebemis Do you know why CI is failing on this, looks like an unrelated change but it doens't fail on main 🤔
Could be because of a potential eslint version change?

Huh, I wonder if it's related to these changes: https://github.com/primer/react/pull/2083

Decided to use --legacy-peer-deps for docs until https://github.com/primer/doctocat/pull/454 is merged, will create another PR after doctocat release :)


spec: specify dataset naming for code generation

Additionally to just describing dataset naming in text file https://github.com/OpenLineage/OpenLineage/blob/main/spec/Naming.md
Specify them in a format that would allow us to generate classes for them in java and python clients. For example, let's say we have BigQueryDataset - instead of passing name and namespace we'd pass projectId, schema and table - just what we need to construct name.
This would make it easier for new integrations to correctly name datasets, and prevent mistakes between integrations.

https://github.com/OpenLineage/OpenLineage/issues/1681 is a duplicate, but a discussion is there


Better rendering of VS nodes when they are positioned in top to down manner

Operating system or device - Godot version:
72748d1363d090f33d5ca6b9c00142b5e8f7d78f
Issue description (what happened, and what was expected):
Currently VS layout force on programmer straight horizontal left to right positioning of VS nodes.
There is nothing wrong with that, but basically every VS script will also need to allow position nodes under each other (lets say new line), currently representation for this scenario is not very readable:

I think there are three ways of solving this,

Have lines connection that acts a little more like bezier curves:

When there is no way to avoid another VS node, line could get little more alpha in that part:

Dynamically move output connection points in response to VS node movement:

Obviously mix of those three would be the best.
Steps to reproduce:
Link to minimal example project (optional but very welcome):

It is better to be a way for nodes grouping (with a label node), too.

@alabd14313 you can make groups with functions and custom nodes, but this is unrelated to the issue in question.

I'll use bezier instead of cosine and make nodes sightly transparent so you
can see the connections on the back. Will also try to see if antialiasing
can be enabled..
On Aug 8, 2016 10:37 AM, "George Marques"<EMAIL_ADDRESS>wrote:

@alabd14313 https://github.com/alabd14313 you can make groups with
functions and custom nodes, but this is unrelated to the issue in question.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/godotengine/godot/issues/6069#issuecomment-238238690,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AF-Z27yZ20Y-2PO00iPT40EMvPb_GTtjks5qdzEYgaJpZM4JfAPn
.

I like flowchart but it looks like people don't like it and prefer a modern presentation

i guess this has been solved

Agree, it's a lot better now:

Btw, how are you seeing vs so faf?
On Jul 7, 2017 2:51 PM, "kubecz3k"<EMAIL_ADDRESS>wrote:
Agree, it's a lot better now:
[image: vs_connections]
https://user-images.githubusercontent.com/6129594/27970054-a30984a8-634d-11e7-8f92-36f196684815.png
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/godotengine/godot/issues/6069#issuecomment-313749706,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AF-Z24Mcu07Uxsl8sEPAa6j_FJF6Hisfks5sLnAjgaJpZM4JfAPn
.

@reduz looks very nice. I'm checking it from time to time, to report some new bugs :) But haven't done in it anything yet. Guess after porting project to 3.0 I will implement some small functionality purely in VS so I will be able to give better feedback. Also my personal hopes for using VS from my programmer perspective is to write most of the logic traditionally and link it visually in some specific scenarios, like AI based on some kind of visual FSM.


Creating a new rule overwrites the old one

If I create a new rule by clicking the + button

I can add information and save the rule. However, when I look at the list, the first rule in the list (ID=0) has been overwritten by the information I entered.

Retested and fixed.


Add a rule that requires styles to refer to elements by tag names if possible

Motivation
When styling elements in Svelte components, there are many options for referencing said elements. The simplest one, leading to the least amount of code is to simply refer to them by their tag name. I'd like to add a rule that enforces this if it is possible (i.e. if there are no duplicates of said element). This may dovetail nicely with no-unused-class-name and lead to code reduction
Description
For each CSS selector using a class, the rule would check the tag name for the element the class is referring to. If there aren't multiple elements with that same tag (or they all share the same class), the rule would trigger and recommend selecting by the tag name instead. The same would apply to IDs
Examples
Text 1

Text 2
Text 3

Text4
Text5

Additional comments
No response

Thank you for the rule proposal.
However, I'm not sure if the new rule is useful. I always use class selectors for styling :sweat_smile:
The proposed coding style seems like it would help reduce the amount of code, but I feel like there's a catch to changing the code. When adding new elements, the wrong style might be applied.
What do you think about that?

Hi,
yeah, this rule is definitely for everyone. You're right that there is a trade-off between minimizing the amount of code and ease of future changes.
I still see the value of having such a rule for those who want it. At the same time, I don't think the rule should ever be in the recommended set, that is for sure. What do you think?

I still see the value of having such a rule for those who want it.

Yeah, I think it's fine to have rules in this plugin if they can satisfy various preferences.
However, for users who prefer class selectors (like me), they'll want a rule to force the use of only class selectors.
Having these as two rules would cause them to conflict, so it needs to be implemented as one rule. In this case, I'm not sure how to design the rule options 😓
Do you have any ideas?

Hmm, so something like consistent-selector-style?
The trouble is, not all selectors are applicable in all situations - classes are I think universal, but there can only be one instance of a particular ID and tag selectors can only be used if there aren't any duplicate tags.
I can envision having an ordered list of preferences, so that with a list ["tag-name", "id", "class"], You'd get the following:

This is only a rough sketch and there are more different selectors, but what do you think about this general idea?

Thanks for your comment.
I think this is a good first rule design :+1:. If we get feedback from users after publishing the rule, we can redesign the options as needed.


Problem with getUniqueId() on iOS

Summary
I have been using version ^4.0.1 for a few months and then decided to update it to the latest one(^8.3.3). I use function getUniqueId to uniquely identify users but getUniqueId from version 4.0.1 and getUniqueId from version 8.3.3 give me different ids and basically all my users will lost their accounts.

Version
8.3.3

Affected OS
iOS

OS Version
14.5

Current behavior

getUniqueId returns differnt id on the latest version compare to 4.0.1
Expected behavior

getUniqueId should returns the same uid for the same device in the latest version as well

How can I achieve it?

Please search the issues list prior to logging duplicates #1317


New data: It's impossible to see value of "Sulfur emissions" for Greenland

the root cause is #1564

Retested. Fixed.


乱码

VSCode Version: Code 1.7.2 (7ba55c5860b152d999dda59393ca3ebeb1b5c85f, 2016-11-21T22:06:37.428Z)
OS Version: Windows_NT ia32 6.1.7601
Extensions:

Extension
Author
Version

Steps to Reproduce:

Title translated to: "Garbled"
Closing as not actionable.
Please provide information about the issue you are seeing, as well as screenshots showing what is going wrong.
Thanks.


How we can check payments for terraform deployments

Currently the contracts are available in the terraform.tfstate file. The contracts billing info should be available in graphql(?).
Can be added as a computed value to the resources.

Currently the contracts are available in the terraform.tfstate file. The contracts billing info should be available in graphql(?).
Can be added as a computed value to the resources.

hey, I haven't been able to find the contracts in my tfstate, which json path should they exist?
JFTR, I'm using provider version 1.0.0.

I found contract ids are the values mapped to node ids in the node_deployment_id object from tfstate:
    {
      "mode": "managed",
      "type": "grid_network",
      "name": "k8s_network",
      _REDACTED_
      "provider": "provider[\"registry.terraform.io/threefoldtech/grid\"]",
      "instances": [
        {
          "schema_version": 0,
          _REDACTED_
          "attributes": {
            "node_deployment_id": {
              "xxx": 3204,
              "xxx": 3205,
              "xxx": 3206
            },
            _REDACTED_

I'm using terragrunt, but you could adapt this script to terraform to get the total amounts billed per contract id; or just provide a $CONTRACTS_ARRAY variable:
#!/bin/bash

CONTRACTS_ARRAY=$(terragrunt run-all show -no-color -json 2> /dev/null | grep -v "INFO\|ERROR\|EOT" | jq '.values.root_module.resources[].values.node_deployment_id | to_entries[].value | tostring' 2>/dev/null | jq -cs | sed 's|"|\\"|g')

#CONTRACTS_ARRAY='[\"3047\", \"3048\", \"3049\", \"3050\", \"3051\", \"3052\"]'

cat > /tmp/$$.gql <<EOF
{ "query": "query MyQuery { contractBillReports(where: { contractID_in: ${CONTRACTS_ARRAY} }) { id amountBilled contractID discountReceived timestamp } }" }
EOF

curl -H 'Content-Type: application/json' -H 'Accept: application/json' \
  'https://graphql.grid.tf/graphql' \
  --data-binary @/tmp/$$.gql \
  -so /tmp/$$.gql.result.json

jq '.data.contractBillReports |
      def sum($k): group_by(.[$k])[]
      | map(.amountBilled | tonumber) as $billings
      | .[0] | . + {billed_total: $billings | add }
      | del(.discountReceived, .amountBilled, .id, .timestamp);
      sum("contractID")' \
     /tmp/$$.gql.result.json


XSOverlay notifications don't work

Version: VRCX 2021.08.15, Windows 10 Build 19043
When enabling XSOverlay Notifications in VRCX options, it does not work.
I tried to send notification manually like this from the console

AppApi.XSNotification('VRCX', 'test', 5, false);

and VRCX throws following exception:

System.IO.FileLoadException: "Could not load file or assembly "System.Runtime.CompilerServices.Unsafe, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" or one of it's dependences. The found Assembly's manifest definition does not match the Assembly reference. (Exception from HRESULT: 0x80131040)"

https://stackoverflow.com/questions/62764744/could-not-load-file-or-assembly-system-runtime-compilerservices-unsafe
Recompiling VRCX locally with Visual Studio 2019 & newest node.js fixes the issue for me, but both current releases on pupy-vrc & Natsumi-sama repos throw this error

Hmmm alright thanks I will keep an eye out for that one

Is this gonna be fixed?
When I recompiled by myself, vrcx didn't start at all

yea it's fixed just need to test things before doing a release


init

👷 Deploy Preview for hongdeyu processing.

Name
Link

🔨 Latest commit
ec64f38825d94dbe2c2821a46ef5e67272ed7eb4

🔍 Latest deploy log
https://app.netlify.com/sites/hongdeyu/deploys/670c65b434ce0d0008825aa6


Update CIP-82 to use CIP-88 namespace

CIP-88 issue: https://github.com/ceramicnetwork/CIP/issues/88

Yes good idea, I added the requirement to the header.

But do you mind also adding CIP-88 as part of this PR? Would be good if it's finable in the INDEX.md if it's a requirement here.

I could but I thought the flow would be first discussing/merging CIP 88 and then updating 82 and 85, no? Basically I'd like to make sure possible comments about 88 are addressed before making further changes to other CIPs.
I don't mind adding 88 in this PR if it makes things simpler, just want to make sure it doesn't slow the process down.

I think it's fine to merge drafts before much discussion. Drafts can always easily be updated with a new PR if needed.


Consider Typesense as a search/suggest backend

I finally spent some time looking into improvements to the search backend (see #43) and among the ones I have tried, Typesense did an exceptionally good job. It has native support for infix search (enabled on a per-field basis) and is incredibly fast. Also the search results in my tests have always been very good. Importing the whole RVK with almost 800k concepts takes about a minute on my local machine, and results in a memory usage of only ~300 MB (note that only ~150k of those concepts are fully indexed for search; the others are combined concepts where I only indexed the identifier and notation) with full infix-enabled search on all identifiers, labels, and notes. Most search queries take less than 100 ms (which could probably be improved with better configuration and not enabling infix search on notes).
There is a test script here: https://github.com/stefandesu/minisearch-test/blob/typesense/typesense.js
We could also use this for efficient creator search in mappings (#170) and even for combining search with filtering (#144).
Right now, I'm not sure how to best integrate Typesense with jskos-server. Ideally, I would offer it as kind of an alternative search backend, but without requiring it for full functionality, but that would increase complexity a lot. If we replaced our current search backend (queries to the MongoDB) with Typesense, we would reduce code complexity, but add a dependency without which jskos-server would not work. I guess we need to evaluate pros and cons for this.

Some helpful links:

Main site: https://typesense.org/
Self-hosting Typesense: https://typesense.org/docs/guide/install-typesense.html#📥-download-install
Server configuration: https://typesense.org/docs/0.23.1/api/server-configuration.html

As far as I can tell, the interesting options are api-key, data-dir, and api-port.

API reference: https://typesense.org/docs/0.23.1/api/collections.html

I think the main issue is keeping the Typesense collection in sync with the data in MongoDB (if we only use Typesense to enhance search). There is a tool that makes it easier, but for us to be able to use it, we would need nested indexed fields which is currently in the Typesense release candidate (see https://github.com/typesense/typesense/issues/227).


Override container entrypoint

Is there a way and/or would it be feasible to add a way to override the default entrypoint from the container image (or alternatively even just a flag to force empty it?)

Currently no (sorta), but it is already?.
This python library just passes fields on to the Chronos API. Here are the docs:
https://github.com/mesos/chronos/blob/c1348ddfd80eb8f888418805005066c230fc6ad2/docs/docs/api.md#job-configuration
Look at the shell arg, which defaults to true, which already overwrites the default entrypoint.
Is the default entrypoint of a container image currently getting in your way?

We are looking into making all of our runners act more consistently by overriding things and it is getting in our way in one of the runners, I could not quickly google a way to override the entrypoint for our chronos runner (but admittedly I have no experience with chronos). It seems this is already not a problem here, the behavior is what we're trying to sync to, so this is perfect.
Thanks for the response and sorry for the noise!


revertOnSpill doesn't work

On the demo page, the example for the revertOnSpilloption doesn't work for me.
Tested in Win 10 and Ubuntu with Firefox and Chromium.

I'm not sure if someone went ahead and fixed this issue, but it seems to be working fine for me with Windows 10 FireFox and Chrome as well as my Ubuntu machine on Chrome

For me, it still doesn't work, tested on Windows 10 and Android in Firefox and Chromium. The items jump back to the last container and not to the origin container.

The revertOnSpill is supposed to return the element to the last position it was in before the spill over not it's original position. It appears to be working correctly in your example above.

It looks like I misunderstood the description of this feature. I thought the items go back to the container where there were first listed and not just back to their last list position. That would be the feature I need...
My fault - sorry for that.


Panic when using ripgrep output in the v8 codebase

Using zf to filter ripgrep output in v8 exits with a panic & SIGABRT:
$ rg . . | zf
thread 708434 panic: reached unreachable code
fish: Process 30749, 'zf' from job 1, 'rg . . | zf' terminated by signal SIGABRT (Abort)

Hmm, it looks like it is failing in the ziglyph unicode normalizing.
Thank you for reporting, I will look into this more

Alright, it seems like part of the rg . . output is not valid unicode and ziglyph is assuming the input is valid
❯ rg . . | isutf8
(standard input): line 80163, char 101, byte 5832237: Expecting bytes in the following ranges: 00..7F C2..F4.

One problematic file is third_party/test262-harness/LICENSE. There are some other files that contain invalid utf8.
Are you building zf from source? Or do you use it packaged from some repository? I'll make a fix to catch this case. If you are using it from one of the repos I'll make a quick patch release

I also want to note that rg . . outputs over 6 million lines. At least for me (on a decently fast machine) zf is quite slow for filtering this. I do have plans for making zf faster in the future though
While zf is a general purpose fuzzy finder, it is specifically designed for filepath matching. Maybe another tool is better for filtering the output of rg . . (which isn't filepaths)? fzf worked well for me

I made a new release that contains this fix https://github.com/natecraddock/zf/releases/tag/0.9.1

Are you building zf from source?
@natecraddock I'm using the Homebrew package, looks like it's already got the new release. Just updated and the case above is working! Thanks for the quick fix! 🙏

zf ... is specifically designed for filepath matching
I'll bear this in mind, have used fzf for ages but I was exploring other options.

@natecraddock I've found another crash, this time when search for 262licen. Happy to open another issue if you want, but also happy to leave it if you'd rather stick to using zf for filepath matching only.

I've found another crash, this time when search for 262licen. Happy to open another issue if you want, but also happy to leave it if you'd rather stick to using zf for filepath matching only.

@doubledup Yes please report. I haven't experienced crashes with zf in over a year, so I'm always interested to know what might be broken. And just because you aren't using zf for a filepath doesn't mean I shouldn't fix it. I do want to support zf as a general-purpose fuzzy finder


Allow casting binary UUIDs

Currently, only dash-separated strings are allowed in UUID.cast/1. This adds the ability to pass 16 byte binaries. The same validation rules apply to both binaries and dash-separated strings.
Closes #2045

It seems that Postgres and Mysql don't actually validate that UUIDs conform to any particular spec, just that they are 16 bytes in total. If performance is a big deal here, do you think it's good enough to just validate length?

:heart: :green_heart: :blue_heart: :yellow_heart: :purple_heart:


Stepfunction Integration Permission not working

Description
Post to the start-stepfunction endpoint results in a permission error
Versions

Module version [Required]:

Terraform version: v1.3.5

Provider version(s):

provider registry.terraform.io/hashicorp/aws v4.51.0
provider registry.terraform.io/hashicorp/external v2.2.3
provider registry.terraform.io/hashicorp/local v2.3.0
provider registry.terraform.io/hashicorp/null v3.2.1
provider registry.terraform.io/hashicorp/random v3.4.3
provider registry.terraform.io/hashicorp/tls v4.0.4

Reproduction Code [Required]
Steps to reproduce the behavior:
Run the installation of the complete-http example.
Run curl -X POST {domain}/start-step-function -d {}
Expected behavior
Success message
Actual behavior
Failed error {"message":"Internal Server Error"}
Cloudwatch Output
<IP_ADDRESS> - - [24/Jan/2023:17:52:06 +0000] "POST POST /start-step-function HTTP/1.1" 500 35 fQke_hDCDoEEMpw= API Gateway doesn’t have permissions to assume the IAM role configured on the integration. Check the permissions and try again.

Please fill in the issue template to increase the chances of receiving an answer.
Verify that your API Gateway has required permissions, as the error message suggests.


slurm script for: configs/official/OLMo-7B.yaml

❓ The question
do you know the slurm script for configs/official/OLMo-7B.yaml?
looking for multi-node slurm script

I'm not sure what exact script was used, but something like https://github.com/allenai/OLMo/blob/main/scripts/lumi/mitchish70.sh may be adaptable to your purposes. That script does not set an architecture-related settings.

Thanks @2015aroras , two questions:

If I set micro_train_device batch size, this will over-ride the global batch size right?
what are these?

B"$PROJECT_DIR:$PROJECT_DIR"
-B"$FLASH_DIR:$FLASH_DIR"
-B"$SCRATCH_DIR:$SCRATCH_DIR"
-B /opt/cray:/opt/cray
-B /usr/lib64/libcxi.so.1:/usr/lib64/libcxi.so.1
-B /usr/lib64/libjson-c.so.3:/usr/lib64/libjson-c.so.3
$PROJECT_DIR/containers/$OLMO_CONTAINER \

The global batch size carries the size of the batch in the current step. We split a batch across our GPUs, so each device has a smaller 'device' batch size (global size / num devices). A GPU doesn't have enough memory to do the whole device batch in 1 forward + backward pass, so we split the device into multiple micro batches and do separate forward + backward passes. After all the micro batches are done, we do the optimizer step.
Overall, micro batch size is just about avoiding memory issues & getting good perf; it should not affect training results. You'll want the micro batch size to be a divisor of the device batch size.

Our slurm jobs run in singularity containers (maybe there are ways to use other types of containers in your system). The -B is mounting directories from outside the container into the container. $PROJECT_DIR/containers/$OLMO_CONTAINER is the location of the container


enabled custom rendering of schema action buttons

Rendering Action Buttons
The WidgetRegistry now can also create the buttons for the schema actions.
This allows to keep the buttons in the same style as the other widget (Bootstrap, Material ...etc).
Since I couldn't see any obvious reason to create an extra registry I did extend the DefaultWidgetRegistry to provide also the button-widgets.
Would be glad to see this coming

Example image of custom rendered action buttons

That's great! Thanks!
My internet connection is too bad this week (I am in vacation) so I am not able to publish a new release on NPM. Ping me next week if I forget.


FAILURE: Build failed with an exception.

FAILURE: Build failed with an exception.
* Where:
Build file '/Users/sandroarnaldodasilva/projetosflutter/colorsdj/android/build.gradle' line: 18

* What went wrong:
Could not compile build file '/Users/sandroarnaldodasilva/projetosflutter/colorsdj/android/build.gradle'.
> startup failed:
  build file '/Users/sandroarnaldodasilva/projetosflutter/colorsdj/android/build.gradle': 18: unexpected token: } @ line 18, column 1.
     }
     ^

  1 error

Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

Get more help at https://help.gradle.org

BUILD FAILED in 2s
Exception: Gradle task assembleDebug failed with exit code 1
Exited (sigterm)

Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, v1.17.5, on Mac OS X 10.15.5 19F101, locale pt-BR)

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.0)
[✓] Xcode - develop for iOS and macOS (Xcode 11.6)
[✓] Android Studio (version 4.0)
[✓] Connected device (1 available)

• No issues found!

buildscript {
    ext.kotlin_version = '1.3.50'
    repositories {
        google()
        jcenter()
    }

    dependencies {
        classpath 'com.android.tools.build:gradle:3.5.0'
        classpath "org.jetbrains.kotlin:kotlin-gradle-plugin:$kotlin_version"
        classpath 'com.google.gms:google-services:4.3.3'
    }
}

allprojects {
    repositories {
        google()
        jcenter()
        maven {
            url "https://maven.google.com" // Google's Maven repository
        }
    }
}

rootProject.buildDir = '../build'
subprojects {
    project.buildDir = "${rootProject.buildDir}/${project.name}"
}
subprojects {
    project.evaluationDependsOn(':app')
}

task clean(type: Delete) {
    delete rootProject.buildDir
}

Hi @sandroarnaldo,
There's seems to be an extra closing bracket per the error:
build file '/Users/sandroarnaldodasilva/projetosflutter/colorsdj/android/build.gradle': 18: unexpected token: } @ line 18, column 1.
     }
     ^

Also, this issue doesn't seem to be related to Firebase. If problem persists and there are no Firebase related plugin which is causing the issue, please consider opening issue in flutter/flutter repo (https://github.com/flutter/flutter/issues)
Closing this, as this doesn't seem to be an issue with any of the Firebase plugins. If you disagree, write in comments and I'll reopen.
Thanks.

I commented on line 18, and now there is another connection error with facebook login
FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':app:processDebugResources'.

A failure occurred while executing com.android.build.gradle.internal.tasks.Workers$ActionFacade
Android resource linking failed
/Users/sandroarnaldodasilva/projetosflutter/colorsdj/android/app/src/main/AndroidManifest.xml:13:9-14:60: AAPT: error: resource string/faceboook_app_id (aka br.com.colorsdj.colorsdj:string/faceboook_app_id) not found.

Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

Get more help at https://help.gradle.org

BUILD FAILED in 38s
The built failed likely due to AndroidX incompatibilities in a plugin. The tool is about to try using Jetfier to solve the incompatibility.
Building plugin cloud_firestore...
Exception: The plugin cloud_firestore could not be built due to the issue above.
Exited (sigterm)
buildscript {
ext.kotlin_version = '1.3.50'
repositories {
google()
jcenter()
}
dependencies {
    classpath 'com.android.tools.build:gradle:3.5.0'
    classpath "org.jetbrains.kotlin:kotlin-gradle-plugin:$kotlin_version"
    classpath 'com.google.gms:google-services:4.3.3'
}

}
allprojects {
repositories {
// google()  ////// line 18 unexpected token///////
jcenter()
maven {
url "https://maven.google.com" // Google's Maven repository
}
}
}
rootProject.buildDir = '../build'
subprojects {
project.buildDir = "${rootProject.buildDir}/${project.name}"
}
subprojects {
project.evaluationDependsOn(':app')
}
task clean(type: Delete) {
delete rootProject.buildDir
}

I/Choreographer(12658): Skipped 391 frames!  The application may be doing too much work on its main thread.
E/FirebaseInstanceId(12658): Topic sync or token retrieval failed on hard failure exceptions: AUTHENTICATION_FAILED. Won't retry the operation.
I/flutter (12658): Error signing in: PlatformException(sign_in_required, com.google.android.gms.common.api.ApiException: 4: 4: , null)
E/FirebaseInstanceId(12658): Topic sync or token retrieval failed on hard failure exceptions: AUTHENTICATION_FAILED. Won't retry the operation.
E/FirebaseInstanceId(12658): Topic sync or token retrieval failed on hard failure exceptions: AUTHENTICATION_FAILED. Won't retry the operation.
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, v1.17.5, on Mac OS X 10.15.5 19F101, locale pt-BR)
[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.0)
[✓] Xcode - develop for iOS and macOS (Xcode 11.6)
[✓] Android Studio (version 4.0)
[✓] Connected device (1 available)
• No issues found!


re-add support for istioctl manifest to read from stdin

In response to a cherrypick label: new pull request created: #21612


Creating a wrapper for dependency injection (mypy issue)

Hi!
To give some context first, I'm currently trying to use antidote in a web backend made by FastAPI, and i'm trying to couple it's dependency injection system, with the one from antidote. I'm doing it, as the DI from FastAPI is limited to injecting into routes only, which is not enough in my case.
I did try to create a wrapper, that would allow me to couple those systems, but mypy does not like my implementation:
from typing import Type, TypeVar

from antidote import world
from fastapi import Depends

T = TypeVar("T")

class InjectService:
    def __init__(self, service_type: Type[T]):
        self.service_type = service_type

    def __call__(self) -> T:
        return world.get(self.service_type)

async def example_route(service: IUserService = Depends(InjectService(IUserService))) -> None:
    pass

When trying to use the InjectService class, it shows the following error:
Only concrete class can be given where "Type[IUserService]" is expected mypy(error)

The issue does not seem to be related to FastAPI, as i'm just not able to create a definition, that would allow me to pass a class with @abstractmethod, even without TypeVar. Even replacing the Type[T] with Type[Any] does not allow me to pass the class.
Honestly, even though i tried, i cannot find out how you managed to create a type definition for world.get that does not make mypy scream at me when using a class with @abstractmethod :(
To give some more context, i would like to pass some data from fastapi dependencies (which would be in the __call__ method), to the injected service. For example the user that made the request, which would allow me to pass all the services that user, without the need to do that manually every time.
Is there maybe some way that would allow me to create such a wrapper? I did go through the docs, but i did not see anything that could help me. Thanks in advance :)

FWIW, @Finistere talked me through something similar in a discussion post

Hi!
Protocols are complex to use properly with @interface to be honest. Functions do not accept generic parameters so Antidote has to pass through __getitem__ with Type[T] to mimic that behavior. But the latter doesn't accept protocols as you've seen.
I played a bit with it, but all solutions have their own problems:

Just use Any, like FastAPI.
Either cast explicitly to Type[IUserService] or use an abstract class.
Hacky use of class generics. Not recommended.

from abc import ABC
from typing import Any, cast, Generic, Type, TypeVar

from fastapi import Depends
from typing_extensions import Protocol

from antidote import world

T = TypeVar("T")

class AbstractUserService(ABC):
    ...

class IUserService(Protocol):
    ...

# FastAPI Depends returns Any in all case, so whatever typing we may do it will be silently ignored.
def depends(dependency: object) -> Any:
    return Depends(lambda: world.get[object](dependency))

def typed_depends(dependency: Type[T]) -> T:
    return cast(T, Depends(lambda: world.get(dependency)))

class DependencyOf(Generic[T]):
    def param(self) -> T:
        # This is NOT part of the public API of Python
        dependency: object = get_args(self.__orig_class__)[0]  # type: ignore
        return cast(T, Depends(lambda: world.get[object](dependency)))

async def example_route(service: IUserService = depends(IUserService)) -> None:
    pass

async def example_route_v2(service: IUserService = typed_depends(AbstractUserService)
                           ) -> None:
    pass

async def example_route_v2b(service: IUserService = typed_depends(cast(Type[IUserService], IUserService))
                           ) -> None:
    pass

async def example_route_v3(service: IUserService = DependencyOf[IUserService]().param()) -> None:
    pass

Unfortunately there isn't a lot Antidote can do here.

Well, so Any it is :(
It's actually kinda sad to be honest. I did some more research on that topic, and i encountered some opened issues in mypy related to that topic: mypy #4717, mypy #1843, mypy #5374.
Seems that people from mypy think, that this use case is not common enough, which forces most of DI libraries for python to create some workarounds, or just don't support it at all, for example Injector #134.
I've tried to find some ways to implement some kind of workaround for my use case, but as you said, there no perfect solution at the moment, I guess I will have to use Any at the moment.
Thanks anyway for your help, it did give me some new ideas how to tackle this problem, just unsafe ones (that Any in this place will haunt me).
Closing the issue, as it's something more related to mypy than antidote.


add solarweb

RE-CHECK!

Automated adapter checker
ioBroker.fronius-solarweb

:thumbsup: No errors found

[ ] :eyes: [W156] Adapter should support admin 5 UI (jsonConfig)
[ ] :eyes: [W145] Each "common.news" should be translated into all supported languages (en, de, ru, pt, nl, fr, it, es, pl, zh-cn)
[ ] :eyes: [W145] Each "common.news" should be translated into all supported languages (en, de, ru, pt, nl, fr, it, es, pl, zh-cn)
[ ] :eyes: [W400] Cannot find "fronius-solarweb" in latest repository

Add comment "RE-CHECK!" to start check anew

Please translate the update news in future :-)
Welcome


Support for blend highlight property

There is not much to add to the title. :grimacing:

0f92ffac88
Update your plugin and close if satisfied.

Sorry for the late response. I just tested it and it works great. Thank you! :pray:


Implement Camera Messaging for MobileControl to include presets and multiple cameras

Need to add the ability for presets defined in config to be sent to MC server to allow for user defined preset data (mostly lables)

Moved to MC


[FEEDBACK]: dinger-completed project error

Type
Site Bug Report
Feedback
On startup of the project the following error is displayed
Screenshots
Paste relevant images or screenshots here

developer.tbd.website URL
No response
Browser
No response
Relevant log output
Unhandled Runtime Error
Error: Wrong tag

Call Stack
Object.decrypt
javascript\node_modules\.pnpm\@noble+ciphers<EMAIL_ADDRESS>(293:0)
XChaCha20Poly1305.eval
javascript\node_modules\.pnpm\@web5+crypto<EMAIL_ADDRESS>(18:0)
Generator.next
<anonymous>
eval
javascript\node_modules\.pnpm\@web5+crypto<EMAIL_ADDRESS>(7:0)
new Promise
<anonymous>
__awaiter
javascript\node_modules\.pnpm\@web5+crypto<EMAIL_ADDRESS>(3:0)
XChaCha20Poly1305.decrypt
javascript\node_modules\.pnpm\@web5+crypto<EMAIL_ADDRESS>(14:0)
AppDataVault.eval
javascript\node_modules\.pnpm\@web5+agent<EMAIL_ADDRESS>(90:62)
Generator.next
<anonymous>
fulfilled
javascript\node_modules\.pnpm\@web5+agent<EMAIL_ADDRESS>(4:42)

I think the application might have still been loading. The error seems to have gone away although a new error when trying to send a message occurs: TypeError: Cannot read properties of undefined (reading 'send')

ah interesting. can I have more info -- does the record.send() error show up on load or when you send a message to a user?

Run into the same issue. I believe  the root cause is that the protocol url and the schema are non existent/invalid (when viewed from browser I get 404 for both). There for the returned record in const record = await writeToDwn(ding); is undefined

I think this is fixed because I do a check to see if web5 is connected before it loads all the elements on the page, so no one can send a record before Web5 is fully initialized. If it still shows an issue, let me know.


Renaming Archive readers to loaders, and extractor to decompressor

Stack from ghstack:

-> #243

Note that the old ones are still functional, but excluded from the documentation and .pyi file. There is no deprecation warnings for them (we can add them after the first release).
Differential Revision: D34403884

@nivekt has imported this pull request.  If you are a Facebook employee, you can view this diff on Phabricator.

@nivekt has imported this pull request.  If you are a Facebook employee, you can view this diff on Phabricator.


Error: ngCompiler.ReflectorHost is not a constructor

Please provide us with the following information:

OS?

Mac OSX (Sierra)

Versions.

ngtools/webpack - 1.1.7

Repro steps.

git clone github.com/prsolucoes/angular2-starter-project
cd angular2-starter-project
npm install
npm start

The log given by the failure.
paulo@MacBook-Pro-de-Paulo:~/Developer/workspaces/node/angular2-starter-project (master) $ npm start

><EMAIL_ADDRESS>start /Users/paulo/Developer/workspaces/node/angular2-starter-project
> npm run ngc && concurrently -r "webpack-dev-server --config webpack.config.js" "node ./bin/ngc-watch.js"

><EMAIL_ADDRESS>ngc /Users/paulo/Developer/workspaces/node/angular2-starter-project
> ngc -p ./tsconfig.json

/Users/paulo/Developer/workspaces/node/angular2-starter-project/node_modules/@ngtools/webpack/src/plugin.js:127
        this._reflectorHost = new ngCompiler.ReflectorHost(this._program, this._compilerHost, this._angularCompilerOptions);
                              ^

TypeError: ngCompiler.ReflectorHost is not a constructor
    at AotPlugin._setupOptions (/Users/paulo/Developer/workspaces/node/angular2-starter-project/node_modules/@ngtools/webpack/src/plugin.js:127:31)
    at new AotPlugin (/Users/paulo/Developer/workspaces/node/angular2-starter-project/node_modules/@ngtools/webpack/src/plugin.js:35:14)
    at Object.<anonymous> (/Users/paulo/Developer/workspaces/node/angular2-starter-project/webpack/plugins.js:12:2)
    at Module._compile (module.js:556:32)
    at Object.Module._extensions..js (module.js:565:10)
    at Module.load (module.js:473:32)
    at tryModuleLoad (module.js:432:12)
    at Function.Module._load (module.js:424:3)
    at Module.require (module.js:483:17)
    at require (internal/module.js:20:19)
    at Object.<anonymous> (/Users/paulo/Developer/workspaces/node/angular2-starter-project/webpack.config.js:15:11)
    at Module._compile (module.js:556:32)
    at Object.Module._extensions..js (module.js:565:10)
    at Module.load (module.js:473:32)
    at tryModuleLoad (module.js:432:12)
    at Function.Module._load (module.js:424:3)

Mention any other details that might be useful.

My repository with the current problem:
https://github.com/prsolucoes/angular2-starter-project

My plugin initialization:
let ngtools = require('@ngtools/webpack');
module.exports = [
	new ngtools.AotPlugin({
		tsConfigPath: './tsconfig.json',
		baseDir: path.join(process.cwd(), 'src'),
		entryModule: path.join(process.cwd(), 'src', 'app', 'modules', 'app.module') + '#AppModule'
	}),
....

I think this is due to the angular 2.2.2 moving ReflectorHost to @angular/language-service.

I think you are correct. Because with version 2.2.1 everything is working fine :(

Intermediately fixed by https://github.com/angular/angular-cli/pull/3242, updating to angular-cli to "1.0.0-beta.21" as described here fixes aot compilation for now.

Thanks. But i dont use angular-cli. I have backed all angular2 deps to 2.2.1 version until it be solved.

@prsolucoes Yes, we also updated the peer dependency of the webpack plugin. This will be resolved properly in the future (next week, because this week is thanksgiving). In the meantime you have to use Angular v2.2.1. This is unfortunate and we're looking at long term solutions to prevent this in the future.

I'm not sure why HanZ closed this. Everything was working perfect for me with angular-cli-b21, this morning i update angular-cli-b22. I'm certain this has something to do with minor project configuration impedance, and you might like to call it a bug, no bug has ever stopped me before, so why would this one stop me now? And, no, I'm not rolling back any of dependencies, i keep everything on the bleeding edge.

I'm also seeing this issue with angular-cli 1.0.0-beta.22-1.

Same here with angular 2.3.0. Please re-open.

Also same problem.
Angular: 2.3.0
CLI: 1.0.0-beta.22-1

Same with my project too!
Angular: 2.3.0
CLI: 1.0.0-beta.22-1

@hansl any news on this

Same here, I don't think as correct @colemickens said in the other issue that is productive to close the issues when they are still actually issues, because people cannot track internal "tickets" of the team @hansl.
Please re-open or update the subscribers for the process.
In our team whoever did an npm install simply cannot work, even if he downgrades.

@jesselpalmer thanks for your fix, though for me if I do what you said, I get a unmet peer dependency (which is needed), warnings and at the end webpack is stops in 20%.
├──<EMAIL_ADDRESS>└── UNMET PEER DEPENDENCY<EMAIL_ADDRESS>npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none was installed.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none was installed.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none was installed.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none was installed.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none was installed.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none was installed.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none was installed.
➜  WebApp git:(version-update) ✗ npm start

><EMAIL_ADDRESS>start /Projects/Jexia/WebApp
> ng serve

** NG Live Development Server is running on http://localhost:4200. **
 10% building modules 2/2 modules 0 active(node:57199) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): Error: Error encountered resolving symbol values statically. Function calls are not supported. Consider replacing the function or lambda with a reference to an exported function (position 144:19 in the original .ts file), resolving symbol AppModule in /Projects/Jexia/WebApp/src/app/app.module.ts
 20% building modules 84/84 modules 0 active

Did the fix work to someone else also?

Same issue here..
I can't run my project and getting
ngCompiler.ReflectorHost is not a constructor
Using angular-cli": "1.0.0-beta.22-1 and angular 2.3.0

Same here with<EMAIL_ADDRESS>

I ran into this problem after updating angular-cli from beta.20-4 to beta.22-1. After running ng init and diffing package.json, I noticed that I had "@angular/compiler-cli" : "^2.2.4" in the dependencies object, and "@angular/compiler-cli" : "2.2.3" in the devDependencies object. I removed the entry from dependencies, and was able to run npm start.

@kevinsherman what version of angular are you using?

@Miced
"dependencies": {
   "@angular/common": "2.2.3",
   "@angular/compiler": "2.2.3",
   "@angular/core": "2.2.3",
   "@angular/forms": "2.2.3",
   "@angular/http": "2.2.3",
   "@angular/platform-browser": "2.2.3",
   "@angular/platform-browser-dynamic": "2.2.3",
   "@angular/router": "3.2.3",
   "@types/node": "^6.0.51",
   "bootstrap": "^3.3.7",
   "core-js": "^2.4.1",
   "font-awesome": "^4.7.0",
   "ng2-bootstrap": "^1.1.16",
   "rxjs": "5.0.0-beta.12",
   "ts-helpers": "^1.1.1",
   "zone.js": "^0.6.23"
 }

Seeing the same problem as above with both 2.2.4 and 2.2.3.

I was able to get the angular 2.3.0 working downgrading the angular-cli from version<EMAIL_ADDRESS>to version<EMAIL_ADDRESS>Now the error gone.

@reginaldocmrg WOW that worked!

How do you actually rollback, though?  I performed a global install of<EMAIL_ADDRESS>and still have .beta22!  I feel liked I'm negotiating with a cartoon.

I installed<EMAIL_ADDRESS>locally.

@Adrriver it worked well for me
sudo npm uninstall -g angular-cli
sudo npm install -g<EMAIL_ADDRESS>

@Adrriver solution works for me also...

I'm getting the same error but I'm not using angular-cli. I'm using webpack. My package.json looks like this
{
"version": "1.0.0",
"name": "sample",
"private": true,
"dependencies": {
"@angular/common": "~2.3.0",
"@angular/compiler": "~2.3.0",
"@angular/core": "~2.3.0",
"@angular/forms": "~2.3.0",
"@angular/http": "~2.3.0",
"@angular/platform-browser": "~2.3.0",
"@angular/platform-browser-dynamic": "~2.3.0",
"@angular/router": "~3.3.0",
"angular-in-memory-web-api": "~0.1.17",
"core-js": "^2.4.1",
"ionic-angular": "^2.0.0-rc.3",
"jquery": "^3.1.1",
"reflect-metadata": "^0.1.8",
"rxjs": "5.0.0-rc.4",
"systemjs": "0.19.40",
"typescript": "^2.1.4",
"zone.js": "^0.7.2"
},
"devDependencies": {
"@angular/compiler-cli": "^2.3.0",
"@ngtools/webpack": "^1.1.9",
"@types/jquery": "^2.0.34",
"angular2-template-loader": "0.6.0",
"html-webpack-plugin": "^2.24.1",
"raw-loader": "^0.5.1",
"ts-loader": "1.3.1",
"webpack": "2.1.0-beta.27"
}
}

@mahindar5 Error actually comes from webpack, either you use ng cli or not.

Hi @stanislavromanov  is there any workaround to fix this? Thanks

Tried all suggested solutions still nothing working.
@angular2.3
@ngtools/webpack 1.1.9

@daviddsingleton you need angular 2.2.4 (and 3.2.4 for router)

Same issue here with 1.0.0-beta.23, as in (#3501, #3467 and #3367). Besides the problem building, I do not know why UNMET PEER DEPENDENCY message when installing latest CLI release.

ng --version

angular-cli: 1.0.0-beta.23
node: 6.9.2
os: win32 x64

npm ls --depth=0

+-- UNMET PEER DEPENDENCY<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+-- UNMET PEER DEPENDENCY<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+-- UNMET PEER DEPENDENCY<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+-- UNMET PEER DEPENDENCY<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+-- UNMET PEER DEPENDENCY<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>`--<EMAIL_ADDRESS>
npm ERR! peer dep missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>npm ERR! peer dep missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>npm ERR! peer dep missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>npm ERR! peer dep missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>npm ERR! peer dep missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>npm ERR! peer dep missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>npm ERR! peer dep missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>npm ERR! peer dep missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>npm ERR! peer dep missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>

ng serve

ngCompiler.ReflectorHost is not a constructor
TypeError: ngCompiler.ReflectorHost is not a constructor
     at AotPlugin._setupOptions (.\node_modules\@ngtools\webpack\src\plugin.js:136:31)
     at new AotPlugin (.\node_modules\@ngtools\webpack\src\plugin.js:37:14)
     at Object.exports.getWebpackAotConfigPartial (.\node_modules\angular-cli\models\webpack-build-typescript.js:44:13)
     at new NgCliWebpackConfig (.\node_modules\angular-cli\models\webpack-config.js:25:42)
     at Class.run (.\node_modules\angular-cli\tasks\serve-webpack.js:20:22)
     at .\node_modules\angular-cli\commands\serve.js:108:26
     at process._tickCallback (internal/process/next_tick.js:103:7)

Has progress?i has same issuse,i used webpack(2.1.0-beta.25) @angular(2.2.3) @ngtools/webpack(1.1.9)

had the same problem with beta 24, try creating a new project , then copy your source folder to that new project. then modify config files as required. It worked for me.

I had the same issue; all that was required to fix it was to remove node_modules and run npm install.
If you're using yarn you need to remove both node_modules and yarn.lock and run yarn afterwards. I suspect a dependency of a dependency is fixed in a newer version and you just need to update it.

@mgol Thanks a lot, the problem was with yarn. I removed the yarn.lock and it's now working !

getting same error with angular 2.4.1 . Any specific details on which version of angular AOT works ?

@arunswaminathank Have you tried removing node_modules (and yarn.lock if you use yarn) and reinstalling dependencies?

Yes, I tried , still the same error
On 04-Jan-2017 5:04 PM, "Michał Gołębiowski"<EMAIL_ADDRESS>wrote:

@arunswaminathank https://github.com/arunswaminathank Have you tried
removing node_modules (and yarn.lock if you use yarn) and reinstalling
dependencies?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/angular/angular-cli/issues/3241#issuecomment-270351603,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ATftz-WUvXjQHyMBgMi-cPNyvpWl3NUtks5rO4OqgaJpZM4K6EUT
.

This is unreal. I can't build my project about 2 weeks. Every combination of versions gives different errors.

I'm using AOT with beta.24 and the below versions.
  "dependencies": {
    "@angular/common": "^2.4.0",
    "@angular/compiler": "^2.4.0",
    "@angular/core": "^2.4.0",
    "@angular/forms": "^2.4.0",
    "@angular/http": "^2.4.0",
    "@angular/platform-browser": "^2.4.0",
    "@angular/platform-browser-dynamic": "^2.4.0",
    "@angular/router": "^3.4.0",
    "core-js": "^2.4.1",
    "rxjs": "^5.0.1",
    "ts-helpers": "^1.1.1",
    "zone.js": "0.7.2"
  },
  "devDependencies": {
    "@angular/compiler-cli": "^2.4.0",
    "@types/jasmine": "2.5.38",
    "@types/node": "^6.0.42",
    "angular-cli": "1.0.0-beta.24",
    "codelyzer": "~2.0.0-beta.1",
    "jasmine-core": "2.5.2",
    "jasmine-spec-reporter": "2.5.0",
    "karma": "1.2.0",
    "karma-chrome-launcher": "^2.0.0",
    "karma-cli": "^1.0.1",
    "karma-jasmine": "^1.0.2",
    "karma-remap-istanbul": "^0.2.1",
    "protractor": "~4.0.13",
    "ts-node": "1.2.1",
    "tslint": "^4.0.2",
    "typescript": "~2.0.3"
  }

Let me try that today too. I put my prj on hold because of these issues like 3 weeks ago. Let's hope it'll work...

Still does not work.

Was there a fix for this? I am experience this as well :(

That's fixed pretty long time ago. My suggestion is to create a new project with beta.26 (the current version as I write this).

I update all package to last version,the issuse fixed.

I use this package.json and fixed!
"dependencies": {
"@angular/common": "4.0.0",
"@angular/compiler": "4.0.0",
"@angular/compiler-cli": "4.0.0",
"@angular/core": "4.0.0",
"@angular/forms": "4.0.0",
"@angular/http": "4.0.0",
"@angular/platform-browser": "4.0.0",
"@angular/platform-browser-dynamic": "4.0.0",
"@ionic-native/core": "3.4.2",
"@ionic-native/splash-screen": "3.4.2",
"@ionic-native/status-bar": "3.4.2",
"@ionic/storage": "2.0.1",
"ionic-angular": "3.0.1",
"ionicons": "3.0.0",
"rxjs": "5.1.1",
"sw-toolbox": "3.4.0",
"zone.js": "^0.8.4",
"@ionic-native/background-mode": "^3.4.4",
"@ionic-native/geolocation": "^3.4.4",
"@types/google-maps": "^3.2.0",
"angularfire2": "^2.0.0-beta.7",
"firebase": "^3.6.9",
"geofire": "^4.1.2"
},
"devDependencies": {
"@ionic/app-scripts": "1.3.0",
"typescript": "~2.2.1"
}


Implementation for Hazelcast based state store

Description
State store implementation for Hazelcast using its Map data structure
Issue reference
For issue #119
Checklist
Please make sure you've completed the relevant tasks for this PR, out of the following list:

[x] Code compiles correctly
[x] Created/updated tests
[ ] Extended the documentation

This PR has commits from the latest merged PR..

I took your branch locally, checking.


[Feature]: Custom tooltip on the table column

Is there an existing issue for this?

[X] I have searched the existing issues

Summary
I want to define custom tooltip value for specified column
Why should this be worked on?
I have table with customer data where are two columns "CustomerCode" and "CustomerName", I want just to display  "CustomerCode" column and show "CustomerName" in column tooltip - in my use case I will save space for other columns which will be visible without scrolling.

@tmdoit thanks for the feature request. Today the tooltip on the table widget is reserved for the overflowing content in every column, To change this behaviour we will need to align this requirement with all other open feature request. Allow us a while to prioritise this properly

@dilippitchika do you think we should pick this up, we could add this property for the tooltip for every column, if its empty we fallback to showing the default content

@somangshu added my thoughts in this loom. Can you check? If this is fine we can proceed.
https://www.loom.com/share/24844eb4f9bf4f44a05f9ea8abff8c48

@dilippitchika there is a bit of misunderstanding here.
While your point to add tooltips on the column header makes sense, OP is asking for custom tooltips on column value:

I want just to display "CustomerCode" column and show "CustomerName" in column tooltip - in my use case I will save space for other columns which will be visible without scrolling

Notice that the user is pointing to the row property which he want to show in the custom tooltip.
leaving a dev note here and adding this to the enhancement goals, lets discuss if required.
Dev Note:

[ ] Make a change in the column headers such that the overflowing content is visible in the tooltip upon hover on column header.
[ ] Add a property tooltip to column settings, if this is set, show the content as tooltip upon hover, else fallback to the default behaviour, i.e. the row content is shown as it is in the tooltip.

[ ] This property will have access to the currentRow.
[ ] This will not be available on autocomplete.
[ ] This will be an input control like computed value property.

Will this problem be relevant if we enable wrapping of text in the table column which seems like a much requested feature?

@Nikhil-Nandagopal This will still not solve for what the OP is asking, That is to show another column value in a required column as tooltip.
This is an easy fix and should not take more than a couple of days.

@tmdoit will you be ok to spend some time on a call to help me understand why this is essential? Plus also the workarounds you may have already thought of. If yes, you can block time here - https://calendly.com/dilip_pitchika


Relax assertions in sockaddr_storage_to_addr to match the documentation.

Fixes #1479

You'll need to rebase to fix the test failures.

Done.

Just one more thing: would you mind squashing your commits?

Done.

bors retry

Thanks.


feat(generated): update definition to 1.0.0-dev0.1.4

Automated PR triggered by new code generation.
feat(generated): update definition to 1.0.0-dev0.1.4
Generated SDK source code using:

Generator version 3.79.0
Specification version 1.0.0-dev0.1.4
Automation (cloudant-sdks) version 7d017eb

Opened in error, duplicate of #555


grouping api

This a first attempt at the grouping api I discussed in #49. It introduces a new Grouper object that supports iteration by group. I've written up a padded day-of-year grouper as a demo.
cc @dgergel, @jukent
closes #49

See the padded day-of-year grouper that already exists with the same name in #28. There is good functionality in the one you have here, but it should be built off of what's already in #28 given that that was already under development, this borrows logic from that one, and that PR was already ready to be merged.

@dgergel - yes, absolutely. The individual groupers are not the interesting part of this PR. The GroupedRegressor is the bit we should all take a look at to evaluate if it could work for our existing (e.g. BCSD/Zscore) or future implementations.

Merging as is so we can start playing with the new api. @dgergel, I've kept the separate namespaces for groupers and grouping for now. Eventually, those will probably be merged but for now, this gives us the option to proceed incrementally.


Unable to build application for web using babel-plugin-react-native-web

Bug

I recently upgraded to react-native-web 0.12.0 and react-native-svg 11.0.1. Unfortunately, it broke my build using metro and babel-plugin-react-native-web (0.12.0).
Downgrading to react-native-svg 10.0.1 and react-natibe-web 0.11.7 fixes the issue.
Looking at the built files, it appears that the published package does not allow the babel plugin for react native web to rewrite the require added by #1240:
// In lib/commonjs/ReactNativeSVG.web.js
[...]
var createElement=require('react-native').unstable_createElement||require('react-native').createElement;
[...]

Environment info

React native info output:
System:
    OS: macOS 10.15.3
    CPU: (12) x64 Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz
    Memory: 2.00 GB / 16.00 GB
    Shell: 5.7.1 - /usr/local/bin/zsh
  Binaries:
    Node: 12.14.1 - /var/folders/r_/4htv7dj10zjcpwslc3w0w1sh0000gp/T/yarn--1580943189690-0.6179425353021855/node
    Yarn: 1.16.0 - /var/folders/r_/4htv7dj10zjcpwslc3w0w1sh0000gp/T/yarn--1580943189690-0.6179425353021855/yarn
    npm: 6.13.4 - ~/.nvm/versions/node/v12.14.1/bin/npm
    Watchman: 4.9.0 - /usr/local/bin/watchman
  IDEs:
    Xcode: /undefined - /usr/bin/xcodebuild
  npmPackages:
    react: ^16.12.0 => 16.12.0
    react-native: ^0.61.5 => 0.61.5
✨  Done in 0.84s.

Library version: 11.0.1
Steps To Reproduce

Install metro
Add the babelconfig:

module.exports = {
  // The 'metro-react-native-babel-preset' preset is recommended to match React Native's packager
  presets: ['module:metro-react-native-babel-preset'],
  // Re-write paths to import only the modules needed by the app
  plugins: ['react-native-web']
};

Run metro build ./index.ts --platform web --out ./index.web.js

As long as index.ts uses react-native-svg, the output error is
Error: Unable to resolve module `../Components/AccessibilityInfo/AccessibilityInfo` from `node_modules/react-native/Libraries/react-native/react-native-implementation.js`:

I guess we should probably use this instead, and not support older versions of react-native-web anymore:
import { GestureResponderEvent, unstable_createElement as createElement } from 'react-native';

@xdmnl Can you try with the latest version?

Closing for now.


User should see payment api tx details in feed

Once user confirms TX is created and details sent to seller and saved in feed

[x] support saving extra information and calling seller callback url

[x] Add to feed item data field (SendLinkSummary.js onTransactionHash) the following data

[x] senderEmail - email entered by user
[x] senderName - name entered by user
[x] invoiceId - invoice # from seller read from link/qr
[x] sellerWebsite - website from seller read from link/qr
[x] sellerName - seller/store name read from link/qr

[x] When calling sendAmount (in SendLinkSummary.js) add parameter txIdentifier and pass invoiceId

In GoodWallet sendAmount when invoice is not empty use transferAndCall with txIdentifier hash (sha3) as data

[x] Send in callback url via POST

[x] senderEmail
[x] senderName
[x] Tx hash
[x] Invoice #

[x] show payment details in feed item and in feed item modal (FeedListItem.js, FeedModalItem.js)
User should see vendor details on his feed

[x] in feed item show under name of recipient, invoice id + seller website
[x] in feed modal also add invoice + website

[x] Seller should see payment extra details on his wallet. If you did task 3 correctly then seller wallet should receive the details of the tx.  the fields will be in feed item item.data (they are passed via the outbox mechanism)

[x] In feed item show under name of sender: invoiceId
[x] In feed item modal show: senderEmail + invoiceId

This is the design for the feed item.
If the vendor has a name set up, it should show the Vendor's name.
If they do not, it should show their website.

what about the feed modal? when user clicks on it
show the invoice id etc..

This is the design for the modal.
Vendor (seller) will see it green/credit, payer (sender) will see the same thing in red/debit.

@patpedrosa In the design of the feed item there doesn't seem to be an example of the invoice id, also wanted to point out that the icon that is being used in the example is the receiving one but the colors and negative transaction value makes it look like it is sending and not receiving

@TomasGonzalez i dont think its important to show the invoice id on the feed item.
The colors are not incorrect, this design is from the view point of the receiver, a similar design should be for the sender jsut with the send colors/icons

@patpedrosa though i'm not sure the design is optimal. it is kind of redundant to show the "To:" to the receiver and "from:" to the sender

@TomasGonzalez No invoice id on the feedd.

@TomasGonzalez

No invoice id on the feed.
The above shows a received transaction. For a sent transaction, meaning what the payer would see if they tapped it, the colors AND the icon are switched.

@sirpy Not sure what you mean by redundant. I don't see nay redundancies here.

@patpedrosa I think by redundant he means the from: in the modal. As the person viewing already knows that he's the sender.

@patpedrosa the receiver already knows who it is for... and the sender knows who is it from.

@sirpy

If the user is able to add custom name/email on our confirmation screen, I think they should be able to double-check the contact details they've provided to the Vendor.

Also, if they want to screenshot a transaction to send to the vendor as payment confirmation, it makes sense to surface all info needed for them to process the sale.
We can polish the design in the next UI and take in consideration multiple scenarios. For this version, our goal was to release fast, hence the "one-size fits all" receipt.

@sirpy this is the icon I was mentioning, I'm pretty sure is not the correct one It should be pointing up not down.

@TomasGonzalez You're correct. I thought we're talking about the modal.

@sirpy I'm having trouble retrieving the invoice id + seller website data from the feedItem, this is all the data I'm getting
action: undefined
animationExecuted: undefined
createdDate: "2021-11-16T17:03:25.491Z"
data:
amount: "3000"
endpoint:
address: undefined
avatar: undefined
displayName: "Ggfg vvvv"
[[Prototype]]: Object
message: "mnbvngc"
preMessageText: undefined
readMore: undefined
receiptHash: "0xc9254bf41118d0c81e77175b413ab7a51573f0564f390b8cef2c987b6d404372"
smallReadMore: undefined
subtitle: undefined
withdrawCode: undefined
[[Prototype]]: Object
date:<PHONE_NUMBER>000
displayType: "sendcompleted"
id: "0xc9254bf41118d0c81e77175b413ab7a51573f0564f390b8cef2c987b6d404372"
status: "completed"
type: "senddirect"
[[Prototype]]: Object

@sirpy It seems that the tasks that are marked as completed in this task are actually not implemented yet... Is there some open branch where I can continue from or should I implement from scratch?

@TomasGonzalez
I dont see that the tasks are checkmarked so why do you say they are marked as completed?
You need to create yourself a vendor payment request (see share/index.js) so you can test it
And complete all the tasks that are not checkmarked, write the vendor info to the feed item record, when payment request is fullfilled in the wallet

@sirpy I unchecked them. They were all checked up to the task opt to the Send in callback URL via POST.

@vldkh @johnsmith-gooddollar Just found out that the app crashes when the user refreshes the SendLinkSummary screen while processing a payment request.

@TomasGonzalez
need to improve how the transaction cards are displayed to the users on the Android App.
Environment:
Version 1.35.1-6 (2373)
Device:
Samsung S20 FE // Android 11
Attachments:

@TomasGonzalez
Need to fix this -

@patpedrosa @TomasGonzalez
Do we need to display avatars and names in feed transaction cards instead of 'Unknown'?

I uploaded a PR with the fix.


Typo in assembly reference name

Hi @nshampur, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. Real humans will now evaluate your PR.

TTYL, MSBOT;

@nshampur : Thanks for your contribution to the Azure documentation! The author, @christopheranderson, has been notified to review your proposed change.

@nshampur Thanks for the catch! #sign-off


[AC SMP merge] add inbound RPC support for SMP

Summary
This is the first of many PR's to change the SMP-SMP networking protocol from direct send ('fire and forget') to RPC.
This PR builds out the first basic workflow for SMP to (1) listen for and (2) handle inbound RPC requests from other nodes SMP.
(1) listening for inbound RPC requests:
Specific changes:

changing mempool.proto to support RPC requests and response for SMP
refactoring existing tests and existing networking code for SMP based on above proto changes
adding inbound RPC entrypoint for batched transaction submissions to SMP

(2) handling inbound RPC requests
Specific changes:

adding functionality in shared_mempool.rs to validate and add the transactions to local mempool

Description: with these changes, SMP tries to vm-validate and add transactions to local mempool. For now, it returns a dummy response to the sender via RPC callback.
Test Plan

For (1) listening for inbound RPC requests: Added unit test in network/src/validator_network/mempool.rs to test SMP receiving inbound RPC calls
For (2) handling inbound RPC requests: Logic for actually handling the transactions in the inbound RPC calls will be tested in integration tests in later PRs, once the outbound RPC calls are implemented
Refactored existing tests pass

:umbrella: The latest upstream changes (presumably fa05be911cd629778eeff1d87e079ff286bf2ba6) made this pull request unmergeable. Please resolve the merge conflicts.

:umbrella: The latest upstream changes (presumably 82a5bc89c41f43bf532bd3197cb9828cc2ca54b0) made this pull request unmergeable. Please resolve the merge conflicts.

Just a few nits and branch conflict but otherwise looks good!


Link in postal-address

When recieving an postal-address via Chat from our Bot. The address is highlighted as an link, the link however does not link to the postal-address but rather to https://hackathon.matchat.org/owner/

what exactly did the bot send as a message, this seems that our markdown parser interprets the message as some link, should it do that or what was the intended purpose of the message?

We accidentally sent the address in square brackets and didn't notice this got interpreted as markdown.
Issue can be closed! @MaxPodpera @quasarchimaere


Timeout Quiet Failure?

Right now the timeout method simply returns if there is nothing to timeout. Though, when that happens it is very likely a user side bug. Shouldn't we be a bit more verbose about it? Even if we don't throw an exception maybe at least a warning? I mean, e.g. passing sid==null doesn't make much sense.

I'm closing this until https://github.com/nats-io/node-nats/issues/32


SQL Builder Syntax

Hey there,
A year ago I browsed the internet looking for the closest thing to JOOQ / JET in TypeScript.
After a year, I can definitely say that Kysely is almost there :-).
I started using it again, and the biggest DX issue I have is how filters (ie. where clauses) are designed. Even with my IDE auto-completing fields, there's significant friction to type out a comma separated list of fields.
Here is an example from Jet (in Go):
stmt := SELECT(
    Actor.ActorID, Actor.FirstName, Actor.LastName, Actor.LastUpdate,  // or just Actor.AllColumns
    Film.AllColumns,
    Language.AllColumns.Except(Language.LastUpdate),  // all language columns except last_update
    Category.AllColumns,
).FROM(
    Actor.
        INNER_JOIN(FilmActor, Actor.ActorID.EQ(FilmActor.ActorID)).
        INNER_JOIN(Film, Film.FilmID.EQ(FilmActor.FilmID)).
        INNER_JOIN(Language, Language.LanguageID.EQ(Film.LanguageID)).
        INNER_JOIN(FilmCategory, FilmCategory.FilmID.EQ(Film.FilmID)).
        INNER_JOIN(Category, Category.CategoryID.EQ(FilmCategory.CategoryID)),
).WHERE(
    Language.Name.EQ(String("English")).
        AND(Category.Name.NOT_EQ(String("Action"))).
        AND(Film.Length.GT(Int(180))),
).ORDER_BY(
    Actor.ActorID.ASC(),
    Film.FilmID.ASC(),
)

And an example from JOOQ (in Java):
create.select()
      .from(BOOK)
      .where(BOOK.AUTHOR_ID.eq(1))
      .and(BOOK.TITLE.eq("1984"))
      .fetch();

The benefits you get from the builder syntax is clear -- you flow through your IDE's autocomplete as you continue to add clauses until you are ready to end your statement.
Would Kysely be interested in an API like this?

You should take a look at Drizzle. It's closer to what you're looking for.

you flow through your IDE's autocomplete as you continue to add clauses until you are ready to end your statement.

Your definition of flow is having to stop yourself to import something? 🙅

Your definition of flow is having to stop yourself to import something? 🙅

Not at all. Please don't misrepresent what I wrote and jump to a different conclusion. The fact that other popular libraries have this design is a good indicator of its value.

You should take a look at Drizzle. It's closer to what you're looking for.

Thanks for the pointer! I'll take a look.

Your definition of flow is having to stop yourself to import something? 🙅

Not at all. Please don't misrepresent what I wrote and jump to a different conclusion. The fact that other popular libraries have this design is a good indicator of its value.

Other languages have their own historical constraints and flavors. That doesn't mean that's good or bad.
A good API optimizes for readability - something that we do a lot more often than writing.
Your examples, especially the first one, are verbose, overly complex and distant from SQL.
Class & fluent interface overkill.

If anyone stumbles upon this issue, here's how you can write these in Kysely v0.24.2:
First example:
db
  .selectFrom('actor')
  .innerJoin('film_actor', 'actor.actor_id', 'film_actor.actor_id')
  .innerJoin('film', 'film.film_id', 'film_actor.film_id')
  .innerJoin('language', 'language.language_id', 'film.language_id')
  .innerJoin('film_category', 'film_category.film_id', 'film.film_id')
  .innerJoin(
    'category',
    'category.category_id',
    'film_category.category_id',
  )
  .where('language.name', '=', 'English')
  .where('category.name', '<>', 'Action')
  .where('film.length', '>', 180)
  .select([
    'actor.actor_id',
    'actor.first_name',
    'actor.last_name',
    'actor.last_update',
    'language.language_id',
    'language.name',
  ])
  .selectAll(['film', 'category'])
  .orderBy('actor.actor_id')
  .orderBy('film.film_id')

https://wirekang.github.io/kysely-playground/?p=f&i=-NSrEdU2eJOeCAcIqKow
Second example:
db
  .selectFrom('book')
  .where('book.author_id', '=', 1)
  .where('book.title', '=', '1984')
  .selectAll()

https://wirekang.github.io/kysely-playground/?p=f&i=-NSrF7UUu2OG4znrGwfh
In both of these, could also make a single .where invocation and use eb.and([...]) if wanted to be more explicit.


Pin ipex for release

What does this PR do?

We pin the ipex version for one last release that supports ipex/torch<2.3 (we should redirect users to it in later releases)
Before submitting

[ ] This PR fixes a typo or improves the docs (you can dismiss the other checks if that's the case).
[ ] Did you make sure to update the documentation with your changes?
[ ] Did you write any new necessary tests?

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.


SW-4813 Implemented hooks for planting site creation

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#2723  👈
#2720
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @tommylau523 and the rest of your teammates on  Graphite

Merge activity

Jun 11, 8:56 PM EDT: Graphite rebased this pull request as part of a merge.