Test / fix e2e overlapping reports

Description
Because we use a function to wrap the JWP and Cleeng scenarios, the CodeceptJS run workers' reporting fails. The reporter instance exists only once for each worker and it creates two Allure runs within the same instance because of the duplicate Feature(`subscription - ${providerName}`) calls.
I've played with data-driven tests, but this will run all steps sequentially.
The easiest fix was to either remove the Feature and Before calls from the runTestSuite functions so it only creates 1 test run.
After this change, the Allure reporting will show all the scenarios before this was the last one completed.

https://github.com/codeceptjs/allure-legacy/blob/8c31bd2d0736487edaa7d92a813562b2571cef49/index.js#L180-L182
Calls:
Allure.prototype.startSuite = function(suiteName, timestamp) {
    this.suites.unshift(new Suite(suiteName, timestamp));
};

Allure.prototype.endSuite = function(timestamp) {
    var suite = this.getCurrentSuite();

    suite.end(timestamp);
    if(suite.hasTests()) {
        writer.writeSuite(this.options.targetDir, suite);
    }
    this.suites.shift();
};

The culprit... This function only returns the first suite:
Allure.prototype.getCurrentSuite = function() {
    return this.suites[0];
};

I was playing with a different idea.
It is possible to customise the parallel execution of tests in CodeceptJS. Creating a folder for all integration tests and running these with different configurations would be a nice and scalable solution.

platforms/web/test-e2e/tests/integrations
platforms/web/test-e2e/tests/integrations/login_test.ts
platforms/web/test-e2e/tests/integrations/register_test.ts
platforms/web/test-e2e/tests/integrations/payment_test.ts
platforms/web/test-e2e/tests/integrations/subscription_test.ts

These suites will have to be split for two integration options:
const integrations = ['jpw', 'cleeng'];

// Create two configs and inject the integration (name for now)
const configs = integrations.map((integrationName) => ({
  inject: {
    integrationName,
  },
}));

// for each integration, spawn a worker and register the test group containing all integration tests
// can also be split over multiple workers...
for (const config of configs) {
  const worker = workers.spawn();
  worker.addTests(testGroups[0]);
  worker.addConfig(config);
}

The rest of the files are spread over multiple workers like normal and don't need any special configuration.

I was playing with a different idea.

This looks promising and more maintainable to me. Any downsides?

@ChristiaanScheermeijer This looks promising and more maintainable to me. Any downsides?

I was playing with this yesterday and I got it (almost) working. The run workers script does feel a bit too custom because I have to trick codecept into duplicating the integration tests with a different config.
The biggest downside is that the e2e tests will only test 1 integration when you run them via the UI or with steps (easier to debug). This is because the run-workers script changes the codecept config before spawning them.
This is what I got so far:
I created two integration configurations because injection works via require and no inline objects :')

The codecept config can either have a predefined include, or we need to ignore the tests by default (when running steps or UI):
    },
  },
  include: {
    I: './utils/steps_file.ts',
    integration: `./configs/jwp`,
  },
  bootstrap: null,

The run-workers script creates two config groups with overrides:
// Create two configs and inject the integration (name for now)
const configs = integrations.map((integrationName) => ({
  include: {
    integration: `./configs/${integrationName}`,
  },
}));

Currently, 4 workers are spawned, but this needs to be worked out a bit more:
for (const config of configs) {
  for (const group of testGroups) {
    const worker = workers.spawn();
    worker.addTests(group);
    worker.addConfig(config);
    worker.addOptions({ config: __dirname + '/codecept.desktop.ts', verbose: true });
  }
}

The challenge here is to balance everything out. If we only create two workers for the integrations, the rest of the tests are distributed over the remainder of the workers.
However, we could also run the non-integration tests on the integration-configured worker...

@dbudzins do you think this idea still has potential? We are looking into optimizing the e2e tests (duration), but this might change based on this outcome.

@dbudzins do you think this idea still has potential? We are looking into optimizing the e2e tests (duration), but this might change based on this outcome.

Hm, it's getting a bit fiddly now.... it looks like just splitting the files fixes the reporting issue. It's kinda annoying, but seems like a quick easy fix: https://github.com/jwplayer/ott-web-app/pull/503
For whatever reason it also looks like they still won't run in parallel, but since there are a lot of tests to run, I think this will shake out in the wash.
What do you think?

@dbudzins As of now, I'm doubting between keeping it "as is" or proceeding with #503. I can pick up on #503, submit a PR and close this one?

@ChristiaanScheermeijer any preference here?


Update bazel and deps

This modernizes the bazel setup to support 7.x, still using the WORKSPACE

@rodaine could you take a look at this one? I just rebased but looks like you need to approve the CI run

thanks! pushed a fix for that failure, hopefully that's the only one!

green 🎉


Reduce exceptions when executing intrinsic functions

Whenever MSBuild is trying to interpret an expression string like $(Property.Substring(0, 2)) it will first try to reflect invoke Substring with string arguments new []{"0", "2"}, have the invoke throw a MethodMissingException because there is no String.Substring(string, string) method, and then try to eventually coerce the arguments into new []{0, 2} and invoke Substring again, which would now succeed.
This is slow, and makes it hard to debug VS or MSBuild.
We should redo the logic to avoid the exception. Maybe directly reflect into the receiver's type and match the method instead of first blindly calling it with strings.
The caveat here is the nature of data. If most of the time builds end up calling intrinsic functions which only take strings, then the current "exceptional" code would actually be faster than reflecting into the receiver to find the proper argument types. We should first build an empty console project and some real, big projects to get a sense of the landscape.

It might also be interesting to build a cache, so the first time we see Substring we do the slow path but the next time we see it, we try the thing that worked last time first and fall back to the slow path.
We could also potentially build our knowledge of these functions--right now we don't know much about the functions we can call, which is nice from a layering perspective but we could probably have higher performance if we had more knowledge of common calls.

Going to dupe this against https://github.com/Microsoft/msbuild/issues/2217 which has more context.


Add note for unsupported infra

What?

refactor retries function to remove duplicate defaults and global variables (commit 1)
Add pagerduty note when infrastructure is unsupported for investigation (commit 2)

Why?

General maintainance
Make it clear why CAD didn't run on a CHGM for GCP clusters

Great job!
/lgtm


npx react-native run-ios --configuration Release error if :hermes_enabled => true

Description
If we activate Hermes for iOS :hermes_enabled => true after clean up pod folder, delete Podfile.lock and run again pod install. If we try to run npx react-native run-ios --configuration Release we get the issue bellow, everything works in debug mode and also everything works if we :hermes_enabled => false.

React Native version:
System:
    OS: macOS 11.2.3
    CPU: (8) x64 Intel(R) Core(TM) i7-7700 CPU @ 3.60GHz
    Memory: 62.48 MB / 16.00 GB
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 12.18.4 - /usr/local/bin/node
    Yarn: 1.22.5 - ~/.yarn/bin/yarn
    npm: 6.14.6 - /usr/local/bin/npm
    Watchman: 4.9.0 - /usr/local/bin/watchman
  Managers:
    CocoaPods: 1.10.1 - /Users/felipesantos/.rvm/gems/ruby-2.7.0/bin/pod
  SDKs:
    iOS SDK:
      Platforms: iOS 14.4, DriverKit 20.2, macOS 11.1, tvOS 14.3, watchOS 7.2
    Android SDK:
      API Levels: 22, 23, 25, 26, 27, 29
      Build Tools: 23.0.1, 24.0.1, 25.0.0, 25.0.2, 26.0.2, 26.0.3, 27.0.2, 27.0.3, 28.0.1, 28.0.2, 28.0.3, 29.0.0, 29.0.2, 29.0.3, 30.0.2
      System Images: android-23 | Intel x86 Atom_64, android-23 | Google APIs Intel x86 Atom_64, android-26 | Google Play Intel x86 Atom, android-28 | Google APIs Intel x86 Atom, android-29 | Google APIs Intel x86 Atom, android-29 | Google Play Intel x86 Atom, android-29 | Google Play Intel x86 Atom_64, android-30 | Google Play Intel x86 Atom
      Android NDK: Not Found
  IDEs:
    Android Studio: 4.0 AI-193.69<IP_ADDRESS>26763
    Xcode: 12.4/12D4e - /usr/bin/xcodebuild
  Languages:
    Java: 1.8.0_265 - /usr/bin/javac
  npmPackages:
    @react-native-community/cli: Not Found
    react: 17.0.1 => 17.0.1
    react-native: 0.64.0 => 0.64.0
    react-native-macos: Not Found
  npmGlobalPackages:
    *react-native*: Not Found

Steps To Reproduce

upgrade to RN 0.64.0
delete node_modules and Pod folder, delete Podfile.lock and yarn.lock files
execute yarn install
execute pod install
open xcode and Clean Build Folder
build app on xcode
if previous steps was successfully executable run npx react-native run-ios --configuration Release

Expected Results

Build successfully
A Library/Developer/Xcode/DerivedData/something/Build/Products/Release-iphonesimulator folder, should be created with a file.app on it. That file is a release variant and we can drag and drop it on a simulator.

Snack, code example, screenshot, or link to a repository:
N/A

Maybe we have to add hermes engine into the *-Bridging-Header.h file?

Does this also occur on 0.63, or is the problem with Hermes new to 0.64?

Does this also occur on 0.63, or is the problem with Hermes new to 0.64?

It's happening only with Hermes new to 0.64... Also if we deactivate Hermes on 0.64 it works fine

i have longer time to build release in Jenkins up to 56 minutes per build, with Hermes enabled and RN 0.64

Does this also occur on 0.63, or is the problem with Hermes new to 0.64?

iOs only got Hermes support in .64 https://reactnative.dev/docs/hermes#ios


TypeError: Cannot read properties of undefined (reading '0') in devContainersSpecCLI.js

https://github.com/devcontainers/cli/issues/699
Affects all tags latest, 3, 3.0, 3.0.0, empty. Cloning the repo locally solves the problem for some reasons.

Resolved in v3.1.0


Should audit RPC command be authenticated?

It currently is authenticated because it was originally intended for guardian ui. But all this command does is sum up publicly available information, so I don't think it should be authenticated at all.

dev call: making this public could make it easier to DOS federation because it requires potentially expensive DB operations


Implement get_actual_qos() for subscriptions

Currently, publishers have the get_actual_qos() feature/function. It would make sense for subscriptions to have them, too.

Refactored to avoid duplicate code. Thanks!

CI: https://github.com/ros2/rmw/pull/177#issuecomment-501261185


webview_flutter shows white screen on Android 5.1.1 devices when resumed app second time

Steps to Reproduce

I'm using flutter v1.10.12 and plugins tag video_player-v0.10.3+3.

Why do you use these versions ?
I have to avoid #47164

Create an app with webview_flutter
Run on an Android 5.1.1 device
Navigate to the webview page.
Press Home button and the app become background, then press the app icon to resume the app.
Do step 4 again

Expected results:
The web content should be there.
Actual results:
Only white screen with the app bar. The web content was gone. And I can't find anything abnormal in the logcat.

Logs

[✓] Flutter (Channel unknown, v1.10.12, on Mac OS X 10.15.1 19B88, locale en-CN)
    • Flutter version 1.10.12 at /Users/zhanglei/Library/flutter
    • Framework revision 0e605cc4dd (3 months ago), 2019-10-04 07:52:15 -0700
    • Engine revision 759d3dba25
    • Dart version 2.6.0 (build 2.6.0-dev.0.0 7a7dcd1ed9)

[!] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
    • Android SDK at /Users/zhanglei/Android/sdk/android-sdk-macosx
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-29, build-tools 29.0.2
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b49-5587405)
    ! Some Android licenses not accepted.  To resolve this, run: flutter doctor --android-licenses

[✓] Xcode - develop for iOS and macOS (Xcode 11.3.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 11.3.1, Build version 11C504
    • CocoaPods version 1.8.4

[✓] Android Studio (version 3.5)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 40.1.2
    • Dart plugin version 191.8423
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b49-5587405)

[✓] VS Code (version 1.32.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 2.21.1

[!] Connected device
    ! No devices available

same problem, but i used mapview
Flutter 1.9.1+hotfix.105-pre.4 • channel unknown • unknown source Framework • revision 7c7d9a910f (2 months ago) • 2020-02-06 18:45:31 +0800 Engine • revision 9b92c0d7d8 Tools • Dart 2.5.0

android 5.1.1、5.0 all have this problem
Besides，after show white screen，swith screen to landscape，platformView will display again 😂

@WeiCongcong
Since I don't have Android 5.0 or 5.1 device to replicate this issue to see if it's still valid using latest Flutter version, I tried the official webview_flutter plugin example on Android Emulators 5.0 and 5.1 and didn't notice white screen while putting the app in background and then resuming the app by bringing it to foreground in debug and release mode.
48867_5.0.mov.zip
48867_5.1.mov.zip

flutter doctor -v
[✓] Flutter (Channel stable, 1.22.4, on Mac OS X 10.15.4 19E2269 darwin-x64,
    locale en-IN)
    • Flutter version 1.22.4 at /Users/dhs/documents/Fluttersdk/flutter
    • Framework revision 1aafb3a8b9 (3 weeks ago), 2020-11-13 09:59:28 -0800
    • Engine revision 2c956a31c0
    • Dart version 2.10.4

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.0)
    • Android SDK at /Users/dhs/Library/Android/sdk
    • Platform android-30, build-tools 30.0.0
    • Java binary at: /Applications/Android
      Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build
      1.8.0_242-release-1644-b3-6222593)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 12.0.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 12.0.1, Build version 12A7300
    • CocoaPods version 1.9.3

[✓] Android Studio (version 4.0)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 46.0.2
    • Dart plugin version 193.7361
    • Java version OpenJDK Runtime Environment (build
      1.8.0_242-release-1644-b3-6222593)

[✓] VS Code (version 1.51.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.16.0

[✓] Connected device (2 available)
    • Android SDK built for x86 64 (mobile) • emulator-5554
      • android-x64 • Android 5.1.1 (API 22) (emulator)
    • iPhone SE (2nd generation) (mobile)   •
      6C85835D-FBFD-4AB3-8DE8-B4FAD35E5367 • ios         •
      com.apple.CoreSimulator.SimRuntime.iOS-14-0 (simulator)

• No issues found!

With the issue not replicable, I am going ahead and closing this as fixed. If you disagree, write in comments and I'll reopen it.
Thanks.

@darshankawar
I've been using my own WebView plugin on Android devices for a year.  The problem might be fixed in the recent flutter or plugin versions. Thank you for your information.


Reuse ports in xds_end2end_test

The first commit reverts #20772.  The second commit adds a new mechanism for reusing ports between tests, so that the maximum number of ports used is now no greater than is needed for any one test.

Known issues: #20792 #20759

Please make sure this passes internally :)

I did; it works fine.


CI Working Group meeting minutes 2020-04-01

CI Working Group meeting minutes 2020-04-01. Trying out a new approach of submitting PRs from a dedicated branch instead of just working in the master for my fork, hopefully that doesn't cause problems.

Thanks @jfpanisset


Get all information when the target is a group

Currently we get name, contact number, last seen, status and groups in common if the target is a contact.
We should extract all such information possible if the target is a group

May I please be assigned this issue


Remove deprecated properties in Mason Generator

Removed the deprecated no longer supported attributes

This might be a misunderstanding. They aren't deprecated. The properties have been moved from DirectoryGeneratorTarget to the generate method.
That was already done in 718d8981

Ohh yeah I see
I pulled the current master and got the error.


Mip can be set with filter

Close #105
Allows firmware to set mip with filtered restriction.

Thanks for the changes :) There is only a minor typo, I can fix it and merge if that's good for you.
Just to clarify, does this close #105 or not? The PR description is not super clear on that point (it says both closes #105 and that it doesn't).

Yes we can close it, sorry I didn't update the description, but the second bug was caused by something else so I did another issue and PR for it (see #115)


Chat : first message sent is not decrypted

if it is impossible to avoid it, we could send an empty message to setup the connexion before the user send his first message.

see alos https://github.com/TalaoDAO/AltMe/issues/2248


Polymer should set failed Array JSON parse back to undefined, not null

I think this line, https://github.com/Polymer/polymer/blob/master/src/micro/attributes.html#L211, should set the value to undefined, not null. Setting it to null will cause observers to run and is somewhat incompatible with the Object parsing code right above. If I understand that code correctly, if an Object parse fails it has the potential to leave the value undefined. @kevinpschaaf

@robdodson Is this still an issue for you in Polymer 2?


Extension causes high cpu load

ms-vsliveshare.vsliveshare-unresponsive.cpuprofile.txt

Issue Type: Performance
Extension Name: vsliveshare
Extension Version: 0.3.1326
OS Version: Darwin x64 18.2.0
VSCode version: 1.32.1

:warning: Make sure to attach this file from your home-directory: /Users/anonymous/ms-vsliveshare.vsliveshare-unresponsive.cpuprofile.txt :warning:
Find more details here: https://github.com/Microsoft/vscode/wiki/Explain:-extension-causes-high-cpu-load

@assemmarwan Thanks for reporting this issue.
Can you please attach this file from your home-directory: /Users/anonymous/ms-vsliveshare.vsliveshare-unresponsive.cpuprofile.tx

Hello,
It's already available at the first line if the issue.

Yup, thanks for pointing this out.
It turns out that Live Share extension registers source map support and that causes perf hit for when an error happens in VSCode extension host. We're investigating alternatives.

We believe this issue is fixed by a combination of 2 changes:

We switched to webpack to avoid excessive loading of many small modules.
We resolved an issue related to the use of the source-map-support module that made some errors result in an infinite loop processing the stack.

The first fix is already available in the latest version of the extension in the marketplace. The second fix will be available in the update to be published tomorrow.


Jitter for the shootretry controller

How to categorize this issue?

/area robustness
/kind enhancement
What would you like to be added:
The shootretry controller is responsible for automatically retrying failed Shoots after the configured retry period (default: 10m): https://github.com/gardener/gardener/blob/1b86da72dd4196ec694b58e81636e34c765b47c5/pkg/controllermanager/controller/shoot/shoot_retry_control.go#L124-L140
It would be great if it would incorporate a random jitter duration on top of the configured retry period, similar to how we already do it for many other controllers.
Why is this needed:
When a lot of Shoots are in Failed state (e.g., because there were IaaS/DNS provider rate limits) and gardenlet reconciles them more or less at the same time (maybe because it was down or restarted due to VPA) then they might end up with very similar lastOperation.lastUpdateTime values.
This results in the shootretry controller marking them for retry at more or less the same time. This will cause a lot of simultaneous reconciliations which might again cause the same problems (rate limits?) as before. Hence, it might take an unnecessary long while until the clusters become healthy again.

/assign


苹果Mac M2机子能玩吗？

后续会不会支持下苹果环境？

"Yes, it has been tested and runs on Mac, including M1 and Intel. Since we lack M2/M3 machines, we're hoping someone could assist with testing."

Confirmed to be working in M2

Confirmed to be working in M2

Thank you for confirming that!


New Wallet and Coins are gone

I noticed ont explorer is down too. I am guessing network down?

Yes.It's under maintainance.

This is still a problem. Unable to get coins to show up.


S3 URI parser

Is your feature request related to a problem? Please describe.
I'd like to parse S3 URI to get region, bucket, etc.
Describe the solution you'd like
A parser API like in .NET and Java
Describe alternatives you've considered
I can parse it manually but it might break sometime.

Hi @dvirtz ,
This sounds like a reasonable enough feature request, I just don't know when we could get around to making it happen, we do take PRs though, in case you already have an idea on how to implement it.

My idea is to reuse the parsing from Http::URI class and copy the other logic from the .NET and Java implementations. Does that sound ok?

sounds good to me, could you try making a pr so we can review it?

started a PR at https://github.com/aws/aws-sdk-cpp/pull/1523

@KaibaLopez any update on this? Almost every other language AWS Sdk contains this utility. I don't understand why the cpp sdk is lagging so far behind.

This is not something we plan on adding to the sdk. I would suggest using regex for this


resin-supervisor-disk: Fix repository grep

Instead of doing "docker images " and then grep for what we are
interested in, we should just do a "docker images" and search through that output.
The issue we are trying to fix is that on different build Operating Systems, "docker images"
will prepend the string "docker.io" to this command's output so our current way we grep will
just return nothing.
fixes #14
Signed-off-by: Florin Sarbu<EMAIL_ADDRESS>

@agherzan @telphan @petrosagg

Yeah, certain packagers decide to modify docker to do non-standard behaviour which breaks things :|
ie you can do:
docker pull resin/amd64-supervisor:1.4.0
docker images resin/amd64-supervisor

and have it return nothing, because they rewrite one command but not the other..
This can be fixed by using the official docker packages from https://docs.docker.com/engine/installation/
My main issue with having to do the separate grep is that docker images | grep resin/amd64-supervisor will also return testregistry.com/resin/amd64-supervisor and some-repo:resin/amd64-supervisor as well as taking longer when there are loads of images (eg on a build server)

So to narrow it down even further, we could make sure we grep for resin/target_repository so we skip the testregistry.com entry from your example above.
About taking longer when there are many images, how long can that take? I'm sure in the overall build process that does not add up too consistently build time wise.

I'm generally trying to avoid greps and other substitutions that can get us into silent troubles generally (which is kinda what this is at its roots).
Now here is what I found:

running "docker run --rm -ti docker.io/ubuntu:14.04 /bin/bash" on a system which reports the images as "ubuntu                        14.04               63e3c10217b8        6 months ago        188.3 MB" works fine. So basically it works with or withour the "docker.io/" part
Running the above command would work on a system like fedora too.

So here is my proposal: modify all the repositories references to resin.io/resin/yyy . This should work for any system.

My last comment was about pull but it seems it doesn't apply on images command too. Sadly.

LGTM


Support default AV1 output option

This should work:
-c:v libaom-av1 -pix_fmt yuv420p -vf "pad=width={W}:height={H}:x=0:y=0:color=black"

When using those parameters, the encoding will fail. FFmpeg told me that the codec is experimental and in order to use it, you have to put -strict -2.

Oh, true! We probably should mark it as experimental or just defer this.


Use appropriate registry keys for x64/x86 systems

On x64 systems HKLM...\WOW6432... holds the alias values. So the code has to decide if this key or (on x86) the original one should be used.

@ManniAT Thanks for the contribution, however have a read of #2.
If you are having problems, make sure you set the alias


gitlab: Fix event_name -> object_kind defaulting.

94457732c178 changed this from:
event_name = payload.get("event_name", payload.get("object_kind")).tame(check_string)

...to:
event_name = payload.get("event_name", payload["object_kind"]).tame(check_string)

Which causes a failure when event_name exists but object_kind does
not, since the default is evaluated first.
Switch to an if statement to clarify the fallbacks better.

Screenshots and screen captures:
Self-review checklist

[x] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[ ] Explains differences from previous plans (e.g., issue description).
[ ] Highlights technical choices and bugs encountered.
[ ] Calls out remaining decisions and concerns.
[ ] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[x] Each commit is a coherent idea.
[x] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[ ] Visual appearance of the changes.
[ ] Responsiveness and internationalization.
[ ] Strings and tooltips.
[ ] End-to-end functionality of buttons, interactions and flows.
[ ] Corner cases, error conditions, and easily imagined bugs.

lgtm; but I guess we can merge after one of the other reviewers replies.


Implement ppermute for soft_pmap

(using pshuffle which is just a light wrapper on ppermute).
def f(a):
  return jax.lax.pshuffle(a, "i", [5, 6, 1, 0, 4, 2, 7, 3])

jax.soft_pmap(f, "i")(jnp.arange(8))

crashes with this error
NotImplementedError: split_axis for ppermute not implemented. Open a feature request!

I would very much like to have this, as it would allow us to test the correctness of scaling our distributed algorithm implementation without needing to actually have a large number of devices.

soft_pmap was deleted in jax 0.3.18. This issue is therefore stale...


autoscaling enabled is broken in current chart.

With the following values provided for auto scaling I receive the following error when attempting to deploy to Google Kuberentes Engine running the latest version. If I disable autoscaling everything works fine but I would like to have this feature enabled.
Values Yaml:
autoscaling:
  enabled: true
  minReplicas: 1
  maxReplicas: 5
  targetCPUUtilizationPercentage: 80
  metrics:
  - type: Resource
    resource:
      name: cpu
      target:
        type: Utilization
        averageUtilization: 80

GKE Error:

Error: unable to build kubernetes objects from release manifest: unable to recognize "": no matches for kind "HorizontalPodAutoscaler" in version "autoscaling/v2beta2"

Odd, I'm not sure what's going on here. In brief, the chart relies on the Capabilities object to see whether it should use v1 or v2. That's presumably just checking the same information displayed by kubectl api-versions. Although that indicates this should be supported, it doesn't work for me either, but in a different way.
For me, the chart tries to create an autoscaling/v2beta2 HPA, but GKE somehow converts this to autoscaling/v1:
$ helm upgrade skulking-moose-f skulking-moose.yaml kong/kong | grep -B1 HorizontalPodAutoscaler
apiVersion: autoscaling/v2beta2
kind: HorizontalPodAutoscaler

$ kubectl get HorizontalPodAutoscaler skulking-moose-kong -o yaml | grep apiVersion
apiVersion: autoscaling/v1

The same occurs if I try and remove the resource and create it manually from a file, so that doesn't appear to be anything Helm's somehow doing.
Can you confirm your exact version and api-versions? This was taken from a slightly earlier master patch version, but I didn't see anything different when updating to v1.15.11-gke.9:
$ kubectl version
Client Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.0", GitCommit:"9e991415386e4cf155a24b1da15becaa390438d8", GitTreeState:"clean", BuildDate:"2020-03-25T14:58:59Z", GoVersion:"go1.13.8", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"15+", GitVersion:"v1.15.9-gke.26", GitCommit:"525ce678faa2b28483fa9569757a61f92b7b0988", GitTreeState:"clean", BuildDate:"2020-03-06T18:47:39Z", GoVersion:"go1.12.12b4", Compiler:"gc", Platform:"linux/amd64"}

$ kubectl api-versions | grep autoscaling
autoscaling.internal.knative.dev/v1alpha1
autoscaling/v1
autoscaling/v2beta1
autoscaling/v2beta2
internal.autoscaling.k8s.io/v1alpha1

https://issuetracker.google.com/issues/135624588#comment13 indicates that 1.15 should indeed support this, and api-versions appears to agree in my case. However, it's a new feature as of 1.15, so it's possible that there are still some edge case bugs. Are you able to reach out to Google support to try and determine what's going on?

Closing this due to no activity. Please re-open if needed.
This might be a duplciate of #129.


WIP - masking

Fixes https://github.com/Volumetrics-io/mrjs/issues/282
Fixes #338

base setup - need to debug image disappearing, saving spot

related to https://github.com/Volumetrics-io/mrjs/issues/336

putting a pause on this one until after the hackathon

putting a pause on this until after @takahirox 's optimization / determination for stenciling // clipping clean-up

closing this since takahiro's taking it over


Auditing improvement: Asserting assumptions about equal gas costs

Description
add constraint to ensure those opcodes' (CALLDATACOPY, CODECOPY, RETURNDATACOPY and MCOPY) constant gas cost is same,  in case some of them diff in the future, can detect that in time.
Issue Link
[link issue here]
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Contents

I don't think we need to do this.  It is fact that they are equal Now.  For future, you should add assert eq in other places like bus mapping.   You pr adds runtime cost.

assert this in near gas cost function.   (eth-types?)


Cannot import name 'SklearnClassifier'

I followed the Setup instruction using pip to install this toolbox on the Jupyter Notebook 6.0.2. But when I run examples with Python 3, it has error.
from sklearn.svm import SVC
import numpy as np
from art.attacks import FastGradientMethod
from art.classifiers import SklearnClassifier
from art.utils import load_mnist
ImportError:  cannot import name 'SklearnClassifier' .
Did anyone occur this before?

Hi @yzhang017 Thank you very much for using ART and raising this question!

I have  the latest version of Anaconda on Windows 10 and run pip command in the Anaconda prompt.

Could you please run pip freeze and post its output? Could you also show how you run the examples?

The following is the output from pip freeze:
absl-py==0.7.1
ad3==2.2.1
Adversarial-Robustness-Toolbox==0.9.0
aiohttp==3.5.4
anaconda-client==1.7.2
anaconda-navigator==1.9.7
asn1crypto==1.2.0
astor==0.7.1
async-timeout==3.0.1
attrs==19.3.0
backcall==0.1.0
backports.functools-lru-cache==1.6.1
backports.tempfile==1.0
backports.weakref==1.0.post1
beautifulsoup4==4.8.1
bleach==3.1.0
certifi==2019.9.11
cffi==1.13.2
chardet==3.0.4
Click==7.0
clyent==1.2.2
colorama==0.4.1
conda==4.7.12
conda-build==3.0.22
conda-package-handling==1.6.0
conda-verify==3.4.2
cryptography==2.8
cvxopt==1.2.0
cycler==0.10.0
decorator==4.4.1
defusedxml==0.6.0
discord.py==1.2.3
entrypoints==0.3
filelock==3.0.12
future==0.18.2
gast==0.2.2
glob2==0.7
grpcio==1.19.0
idna==2.8
idna-ssl==1.1.0
importlib-metadata==0.23
ipykernel==5.1.3
ipython==7.9.0
ipython-genutils==0.2.0
ipywidgets==7.5.1
jedi==0.15.1
Jinja2==2.10.3
joblib==0.14.0
jsonschema==3.2.0
jupyter==1.0.0
jupyter-client==5.3.4
jupyter-console==6.0.0
jupyter-core==4.6.1
jupytext==1.2.4
Keras==2.0.9
Keras-Applications==1.0.7
Keras-Preprocessing==1.0.9
kiwisolver==1.1.0
Markdown==3.1
MarkupSafe==1.1.1
matplotlib==3.1.1
menuinst==1.4.16
mistune==0.8.4
mkl-fft==1.0.15
mkl-random==1.1.0
mkl-service==2.3.0
mock==2.0.0
more-itertools==7.2.0
multidict==4.5.2
nbconvert==5.6.1
nbformat==4.4.0
networkx==2.4
notebook==6.0.2
numpy==1.17.3
olefile==0.46
opencv-python==<IP_ADDRESS>
pandas==0.25.3
pandocfilters==1.4.2
parso==0.5.1
pbr==5.1.3
pickleshare==0.7.5
Pillow==6.2.1
pkginfo==<IP_ADDRESS>
prometheus-client==0.7.1
prompt-toolkit==2.0.10
protobuf==3.7.0
psutil==5.6.5
pycosat==0.6.3
pycparser==2.19
Pygments==2.4.2
pyOpenSSL==19.1.0
pyparsing==2.4.5
pyrsistent==0.15.5
PySocks==1.7.1
pystruct==0.3.2
python-dateutil==2.8.1
pytz==2019.3
pywin32==223
pywinpty==0.5.5
PyYAML==5.1.2
pyzmq==18.1.0
qtconsole==4.6.0
QtPy==1.9.0
requests==2.22.0
ruamel-yaml==0.15.46
scikit-learn==0.21.3
scikit-multiflow==0.4.1
scipy==1.3.2
Send2Trash==1.5.0
six==1.13.0
sortedcontainers==2.1.0
soupsieve==1.9.5
tensorboard==1.13.1
tensorflow==1.13.1
tensorflow-estimator==1.13.0
termcolor==1.1.0
terminado==0.8.3
testfixtures==6.10.2
testpath==0.4.4
tornado==6.0.3
tqdm==4.38.0
traitlets==4.3.3
typing-extensions==3.7.4
urllib3==1.24.2
wcwidth==0.1.7
webencodings==0.5.1
websockets==6.0
widgetsnbextension==3.5.1
win-inet-pton==1.1.0
wincertstore==0.2
yarl==1.3.0
zipp==0.6.0
Note: you may need to restart the kernel to use updated packages.
Could not parse requirement: -umpy
Could not parse requirement: -illow
Here is the code I run in jupyter notebook and the error:
from sklearn.svm import SVC
from sklearn.metrics import accuracy_score,classification_report,confusion_matrix
from sklearn.preprocessing import StandardScaler
from art.attacks import FastGradientMethod
from art.classifiers import SklearnClassifier

ImportError                               Traceback (most recent call last)
 in
4
5 from art.attacks import FastGradientMethod
----> 6 from art.classifiers import SklearnClassifier
ImportError: cannot import name 'SklearnClassifier'

Thank you! I see that you have installed Adversarial-Robustness-Toolbox==0.9.0. The support for scikit-learn has been introduced with ART v1.0. If you upgrade your installation of ART to v1.0 the error should disappear.

Thank you so much. It fixed. Actually, I installed the ART yesterday, so I did not realize it needs to be upgraded.


Allow show_to_nations to be [] or ""

What
Describe what you have changed and why.

show_to_nations can now be in array or string format.
The reason for this change is that is easy to format the YAML incorrectly for single entries.
It should prevent us from getting these errors.

Co-authored-by: Rob Nichols @reggieb<EMAIL_ADDRESS>How to review
:ship: Since this service is continuously deployed, all testing must be done
before the pull request is merged. :ship:

Review the code
Run the tests

Links
Trello

@gclssvglx Looking at this again. The let refactoring makes sense here because the splitting out of the nation parameter requires the parameter locale_results_link_fixture to be modified. So it is an appropriate time to make the change as it makes modifying locale_results_link_fixture within the spec, so that both the %w[Wales] and "Wales" forms of nation are tested, much cleaner.

No problem @reggieb - was just a suggestion.


Support for Feature Services from Feast

Would be interesting to catalog FeatureService from Feast too
Context

Feast now has the concept of feature services which are composed of feature views. This is an important component because certain models can use a set of features defined in a feature services. In fact, feature views are upstream for feature services

keep fresh

keep fresh

Keep fresh


bug(extensions): ignored breakpoints

Issue
Breakpoints where ignored when debugging.
For more details see #152.
Checklist

Code is easy to understand
No obvious errors or bugs
CI/CD Pipelines did run successfully
Tests were implemented
Documentation was created

Codecov Report
Patch and project coverage have no change.

Comparison is base (c38ee16) 63.27% compared to head (663f7be) 63.27%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #227   +/-   ##
=======================================
  Coverage   63.27%   63.27%
=======================================
  Files          14       14
  Lines         305      305
  Branches       40       40
=======================================
  Hits          193      193
  Misses         72       72
  Partials       40       40

Flag
Coverage Δ

unittests
63.27% <ø> (ø)

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

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

@rami-nk can you please try if the breakpoints work? I thought I had it, but then it only worked in the resolveCustomTextEditor method and not in the activate method. Now it should work in both, but I am a little unsure.


Wrong post url if using -web.path-prefix options

Silencing alerts always failed, turns out that the web ui post to "/api/alerts" instead of "/prefix/api/alerts"
EDIT: Forget to mention that I'm using v 0.4.0

ran into the same thing, this is fixed in master already though.

Yes, fixed in master.


Add Filters on PagedTable As tabs

@salaboy, @nmirasch
Shouldn't org.uberfire.ext.services.backend.preferences.UserDataGridPreferencesServiceImpl be deleted and use of org.uberfire.ext.services.backend.preferences.UserPreferencesServiceImpl be used instead now? (following on from @bxf12315's work)

@manstis yes.. that's the idea.. I'm not sure  @bxf12315 will do that adaptation later .. as far as I know he was planing to do that.

@Salaboy  @nmirasch
As Salaboy said , we can use UserPreferencesServiceImpl instead of old code UserDataGridPreferencesServiceImpl. It is work.


ListK Slides

I'm back :-p ... I'm preparing the ListK + SequenceK slides for a new video.
@MaureenElsberry @raulraja could you please review my broken English and my monadic thoughts?

@javipacheco!!!!!!!!!!! Yes, I'll review and then have you review again to make sure I don't strip out any engineer speak. ;) Thanks!


itemDisplaySize offsets bounty status overlay

When the itemDisplaySize is changed (settings item size slider) the bounty status .svg is offset because of the size change.

Fixed in latest (upcoming) push.


LOOT by realAppID

This request introduces a new command LOOT@
LOOT@  realappIDs
loot only the assets whose realappID is in the list realappIDs.
(typical example is to loot from my trading bot only the cards for the current steam sale)
I may be missing a "wantedTypes: BotConfig.LootableTypes" for the GetMyInventory function.
It's present in the LOOT function (responseLoot), but not in the LOOT^ function (responseAdvancedLoot), I don't know if I should use it.
Notice that there are a lot of code duplication: responseLoot, responseAdvancedLoot and now this new command have roughly the same code. I would be willing to do the refactoring if you give me the prototypes of the function.
Notice that I also have another branch, called ListInventory, with a new command "LIST" that lists your inventory (helpful in conjunction with this). ListInventory is WIP for now.
E.

I have done the requested changes.
Your remark about the lock should also apply to the function ResponseAdvancedLoot, doesn't it ?

yes I tried before pushing the modifications, everything worked OK.

Your remark about the lock should also apply to the function ResponseAdvancedLoot, doesn't it ?

Yes, you can change it as part of this PR, or I'll change it myself afterwards.


build: add scoop and nfpms

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 76.054%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
5574

Relevant Lines:
7329

💛  - Coveralls


Add Sphinx setup

Related: #677
Run make docs to generate HTML documentation under docs/build. (Right now the build emits a lot of warnings.)
Run make clean-docs to clean generated docs files.

Could we also have it publish the sphinx docs to the GH pages branch? We can do that in a follow-on PR, but having that automated publishing would be really nice!

Could we also have it publish the sphinx docs to the GH pages branch?

Definitely, this is the upcoming item on the list.


Waiting for releasing the official code

Hi,
Thanks for your great work! I'm wondering when will you release the code? Hoping it will come soon~

Hi @DingYikang ! Thank you for your interest! We plan to release the code in a few months(by the end of November this year).


feat: support string interpolation of encrypted variables

https://issues.redhat.com/browse/AAP-22487
We can now support
"{{ some_encrypted_variable }}"

and also
"Some {{ some_encrypted_variable }}"

Since we do decryption earlier than the substitution, we may not need to check wether the string is encrypt again in https://github.com/mkanoor/ansible-rulebook/blob/213545c6ee53bd3b452cde8ad162d4d629c23f4c/ansible_rulebook/util.py#L69

@bzwei These relates to variables that don't go thru Jinja substitution because the vaulted strings are directly embedded in the rulebook like here


HHH-11587 - Reordering items in List throws a constraint violation

https://hibernate.atlassian.net/browse/HHH-11587
Replacement for this PR.

https://github.com/hibernate/hibernate-orm/pull/1879 should fix the issue highlighted by @gbadner

superseded by https://github.com/hibernate/hibernate-orm/pull/1879


Feature request: smooth scroll behaviour

Setting scroll-behaviour to smooth will enable smooth scrolling when scrolling happens due to navigation or CSSOM scrolling APIs. In my opinion it is clearer if a user scrolls to the section where he needs to be instead of the instant scoll.
The scroll behaviour can be set on :root or on every element (not inherited by default). Maybe make a variable, so this behaviour can easily be turned off if needed?
Currently only Chrome and Firefox support this feature, but it's more like an enhancement so I don't think this is an issue.
Demo: https://codepen.io/MartijnCuppens/pen/bYjEby?editors=1100
More info: https://developer.mozilla.org/en-US/docs/Web/CSS/scroll-behavior
Support: https://caniuse.com/#feat=css-scroll-behavior

Thanks, but we'll pass on this for now.


operators hive-operator (2.4.3206-b0714a7)

Update Hive community operator channel(s) [['ocm-2.4']] to 2.4.3206-b0714a7

/retest

/merge possible

/merge possible

Future us-
The commit hash (b0714a7) for this bundle does not exist in the hive repo. This happened because we were having problems with the centos base image, so we committed a temporary Dockerfile change locally and used bundle-gen's --hive-repo option to pick it up, causing bundle-gen to use the commit count/hash from the local repo, which never existed upstream. I confirmed that b0714a7 is a direct descendant of 7048523b00b44034ed71cf13d2104fddd1d96371. The delta was

A backport of the bundle-gen.py tool. No impact on the build.
The following delta to the Dockerfile:

diff --git a/Dockerfile b/Dockerfile
index f89191f4b..1f5ea81ad 100644
--- a/Dockerfile
+++ b/Dockerfile
@@ -4,7 +4,7 @@ WORKDIR /go/src/github.com/openshift/hive
 COPY . .
 RUN make build

-FROM quay.io/centos/centos:8
+FROM quay.io/centos/centos:stream8

 # CentOS images do not get updates as they are meant to mirror ISO content, and thus this update
 # is strongly recommended for security updates.


How to get XmlText from XmlNode?

How can you get the XmlText from an XmlNode? I don't see a clear way to do that.

So this seems to work:
XmlNode1.SelectSingleNode('text()', XmlNode2);
DNXmlNode2.AsXmlText.Value
Is that the best way? Seems circuitous.

That is the only way. SelectSingleNode will return an XmlNode. An XmlNode can be XmlText, XmlElement etc. Because we do not have explicit conversions in AL, we added them as methods to the type.


I can't find dwLocalPlayer anywhere...

Maybe I just didn't do something correctly, but I can't find dwLocalPlayer offset anywhere. Is it maybe supposed to be called something else?

https://github.com/a2x/cs2-dumper/blob/85e6224275f6f9f8c7f6b00ee33f5ffe260dd492/generated/offsets.hpp#L19

Thank you!


fix: load hrp before deserializing genesis payload to take hrp effect

What this PR does / why we need it:
fix: load hrp before deserializing genesis payload to take hrp effect
Which docs this PR relation:
N/A
Which toolchain this PR adaption:
N/A
No Breaking Change
Special notes for your reviewer:
This is an internal bug and fix doesn't take any changes to toolchains and docs.
hrp should load firstly before deserializing genesis cause Address maybe in service genesis payload may need hrp

We should add unit test for this PR which avoid running failures due to some breaking changes in future

We should add unit test for this PR which avoid running failures due to some breaking changes in future

So as I think. The problem is not to add test, but where to add?

We should add unit test for this PR which avoid running failures due to some breaking changes in future

So as I think. The problem is not to add test, but where to add?

The point of testing is to match field, so i think it's just a matter of ensuring that the serialized Metadata json string can read the fields.
Can we add it to types/metadata.rs？

We should add unit test for this PR which avoid running failures due to some breaking changes in future

So as I think. The problem is not to add test, but where to add?

The point of testing is to match field, so i think it's just a matter of ensuring that the serialized Metadata json string can read the fields.
Can we add it to types/metadata.rs？

The hrp can only be set once, which means if I set hrp to sth. like 'meow', the following address's hrp have to be 'meow'
However cargo test is designed to run parelly and each test case must not relate to others.
I don't wan't to set test thread to 1.
And if I set hrp, other tests shall fail.
Thus.....you see the 'crippled' test cases...

/lgtm


Feature/release 0.3.3

Bump kramdown-rfc2629 to 1.5.26
Update ietf-at version to 0.3.3

Codecov Report

Merging #73 (e2f7f6d) into main (28d5523) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #73   +/-   ##
=======================================
  Coverage   87.03%   87.03%
=======================================
  Files           9        9
  Lines         671      671
=======================================
  Hits          584      584
  Misses         87       87

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 28d5523...e2f7f6d. Read the comment docs.


Password requirement check

Provide props to specify min number of characters required in password and also how many special characters are needed. For example,
<sui-input type="password" minChar="6" requiredChar="['!@#$%^&*-_', 2]" />
Would only accept passwords with minimum 6 characters and contain 2 special characters from a list of !@#$%^&*-_.
Passwords that Fail
hell1122
helloagain!
hello
Passwords that Succeed
he!!oo
ilov3$$
@xist@nce

added features in #103 for min/max length of input.
features such as requiredChar can be done by declaring regex pattern in 'pattern' props


meta: simplify redis transaction

Codecov Report

Merging #1766 (bac4190) into main (8d0ee9f) will decrease coverage by 0.02%.
 Consider uploading reports for the commit d2c3f22 to get more accurate results

@@            Coverage Diff             @@
##             main    #1766      +/-   ##
==========================================
- Coverage   61.85%   61.83%   -0.03%
==========================================
  Files         135      135
  Lines       22876    22935      +59
==========================================
+ Hits        14151    14181      +30
- Misses       7134     7158      +24
- Partials     1591     1596       +5

Impacted Files
Coverage Δ

pkg/meta/redis.go
73.78% <77.92%> (+0.62%)
:arrow_up:

pkg/chunk/utils_unix.go
73.33% <0.00%> (-20.00%)
:arrow_down:

pkg/fuse/context.go
56.75% <0.00%> (-10.82%)
:arrow_down:

pkg/vfs/reader.go
80.29% <0.00%> (-4.38%)
:arrow_down:

pkg/chunk/cached_store.go
77.44% <0.00%> (-2.89%)
:arrow_down:

cmd/mount.go
67.96% <0.00%> (-2.63%)
:arrow_down:

cmd/format.go
60.89% <0.00%> (-1.69%)
:arrow_down:

pkg/meta/info.go
85.10% <0.00%> (-1.17%)
:arrow_down:

pkg/vfs/writer.go
78.64% <0.00%> (-1.02%)
:arrow_down:

pkg/chunk/disk_cache.go
78.88% <0.00%> (-0.98%)
:arrow_down:

... and 13 more

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 8d0ee9f...d2c3f22. Read the comment docs.


TypeScript would not resolve custom declaration file

Is this a bug report?
Yes
Did you try recovering your dependencies?
Yes
npm: 6.4.1
node: v8.11.2
Which terms did you search for in User Guide?
tsconfig.json
Environment
System:
OS: macOS 10.14.1
CPU: x64 Intel(R) Core(TM) i7-5557U CPU @ 3.10GHz
Binaries:
Node: 10.13.0 - ~/.nvm/versions/node/v10.13.0/bin/node
Yarn: 1.12.3 - /usr/local/bin/yarn
npm: 6.4.1 - ~/.nvm/versions/node/v10.13.0/bin/npm
Browsers:
Chrome: 70.0.3538.102
Firefox: 57.0
Safari: 12.0.1
npmPackages:
@types/react: ^16.7.6 => 16.7.6
@types/react-dom: ^16.0.9 => 16.0.9
react: ^16.6.3 => 16.6.3
react-dom: ^16.6.3 => 16.6.3
react-scripts: 2.1.1 => 2.1.1
npmGlobalPackages:
create-react-app: Not Found
Steps to Reproduce

Create a new CRA 2.1.1 project, rename jsx to tsx file
Add a package such as npm install airtable
Given airtable does not come with typescript declaration file, and there is no @types/airtable either, we have to hand create one, such as the following

// in src/airtable.d.ts
declare module 'airtable' {
    class Airtable {
        constructor(opts?: any)

        base(opts?: any): any
    }

    export default Airtable;
}

Try to create some logic to reference airtable, for example

import Airtable from `airtable`;

const table: Airtable = new Airtable();

Run the app

Expected Behavior
The code should compile.
Actual Behavior
I keep getting type error stating Could not find a declaration file for module 'airtable'., I tried to add custom typing setting such as typeRoots, and it didn't recongize it at all.
Reproducible Demo
https://github.com/tangentlin/cra2-ts-issue

I reproduced with your steps and it works fine for me. Can you upload an example project that cause the error?

@tangentlin Your issue might be related to this (https://stackoverflow.com/a/42702089/1957353)
From your example, try to move the import react statement into module declaration block.
declare module 'video-react' {

    import * as React from 'react';
    // ...
}

hope this help :)

Thanks @n3tr , that solves the problem.


Deconz devices disconnection every 30 minutes

Hello !
I am on Home Assistant and I have signal cuts between my Deconz key and all my sensors (Xiaomi Aqara opening sensor, Honeywell smoke detector, motion detector ...)
Home Assistant Core 0.113.0
Deconz 6.1.1
deConz Version 2.05.79 / 05/22/202
Firmware 26580700
Despite these last updates, I still have this disconnection reconnection problem for several weeks.
These outages occur approximately every 30 minutes.
I'm french, sorry for my english! and thank you for your help and advice :)

Duplicate of https://github.com/home-assistant/core/issues/37372

thanks, but this issue was closed 15 days ago when I looked ... apparently still not solved…. :'(

With 6.x.x the firmware work again because we fix the GLIBC version issue with the new flasher binary.
I can just provide updates and look that the binary inside work. I don't know why i.e. my conbee2 doesn't offer me a firmware update. Maybe the new firmware is only for tests and not for all

Thank you for your answer. I just updated the add-on to version 6.1.2. Unfortunately I still have the same problem but only one disconnection in an hour, to be continued ....

@pvizeli https://github.com/home-assistant/hassio-addons/issues/1347#issuecomment-664093542 say's it still fails. Check your PM on discord if you can:).
However, What version of deCONZ / Phoscon are you running? Phoscon mentions it at its gateway page.

hi,
i use :
Home Assistant Core 0.113.0
Deconz 6.1.1
deConz Version 2.05.79 / 05/22/2020
Firmware 26580700
I made the update but it does not seem to have been supported and stay permanently at deconz version 05/22/2020

Having same problem here, really frustrating :(

Hi,
I also have the same problem.
Disconnections approximately every hour.
I really tried everything to solve the problem.
DEBUG (MainThread) [pydeconz.websocket] Websocket starting
DEBUG (MainThread) [pydeconz.websocket] Reconnecting to deCONZ in 15.
DEBUG (MainThread) [pydeconz.websocket] Websocket starting
DEBUG (MainThread) [pydeconz.websocket] Websocket running

Home Assistant 0.112.4
HassOS 4.11
Raspberry Pi 3 Model B
ConBee II (Firmware 26580700)
deCONZ 6.2.3 (2.05.79)
ZigBee components:

TRÅDFRI bulb GU10 WS 400lm
TRÅDFRI Signal Repeater
Xiaomi Aqara (motion sensor, switch)

As i said before:
duplicate of https://github.com/home-assistant/core/issues/37372


Annotations missing

In the README file, it states:
The following annotations are currently supported:

@HxLocation
@HxPushUrl
@HxRedirect
@HxRefresh
@HxReplaceUrl
@HxReselect
@HxReswap
@HxRetarget
@HxTrigger
@HxTriggerAfterSettle
@HxTriggerAfterSwap

However, these annotations do not seem to be available in version 3.3.0.
Am I missing something?

These changes are part of the next version 3.4.0. You must pick the README.md that corresponds to the correct version.
https://github.com/wimdeblauwe/htmx-spring-boot/blob/3.3.0/README.md

It was a good reminder that I still needed to release 3.4.0 which I just did now: https://github.com/wimdeblauwe/htmx-spring-boot/releases/tag/3.4.0


Add button labels to the DB

The buttons in the DB all map to XBOX360 style names. In order to display a representation of the physical button on the device in the UI, a symbol name would be required for each mapped button. E.g.: "square", "green", etc.
I am not sure how this could be added to the current txt file in a way it could not intefere with the way it is parsed.
Is this something that has been considered before and would it make sense to add this to this lib?

This (and other extensions to the DB format) have been talked about in the SDL distribution list, so far no progress on it (that I know of).

What is the status of this? https://github.com/gabomdq/SDL_GameControllerDB/tree/buttons

@aaronfranke Very dead ;)


feat(iroh-willow): Event subscriptions

Description

Moves event subscription from a wrapper of the store into the EntryStorage trait
Adds persistent subscriptions, with interface - mostly - from https://github.com/earthstar-project/willow-rs/pull/21/
Exposes subscriptions over RPC
Adds client methods for subscriptions
Adds a smoke test

Notes & open questions
Should look into remaining differences between our trait and willow-rs with regard to event subscriptions, and see if anything from here should be proposed for change in the willow-rs trait. Notably:

subscribe_area  takes SubscribeOpts not QueryOpts, with option to ignore ingested event for some session id, and to receive only Ingested event. This lets me replace the previous impl easily in the WGPS impl, and it makes sense IMO.

Has a few TODOs on optimizing things.
Will need much more tests.
Replaces #2681 (had wrong branch)
Change checklist

[ ] Self-review.
[ ] Documentation updates following the style guide, if relevant.
[ ] Tests if relevant.
[ ] All breaking changes documented.

I think I've played with this enough in tauri-todos to confirm the subscription bits are working. Still need to take a look at the actual code, but honestly, that'll take a bit until I warm up to the codebase generally.


Support NavGraph

JetPack Navigation includes support for ViewModel (navGraphViewModels) which today is not supported by retained. I propose we include a retainInNavGraph that will cover this use case. We still need to study in which artefact it would be better to add this function (either create a new navigation artefact or include it as part of the main artefacts).

Basic support for NavGraph inside Fragments was added in #21 (thanks @tfcporciuncula). We still need to include support for @Composable in a new artefact: navigation-compose before closing this ticket.
The view support is still blocked by the crash that might come in the next fragment release.

We should include navGraph support in our docs.

Document is been worked on #34.


support base64 file input

hello,
jo supports base64 encoding with % prefix
jo user_id=1 tags=$(jo -a foo) type=1 data=%/path/to/file.bin

can httpie support this natively without needing jo ?

@engin HTTPie does not natively support base64 encoding. You could achieve the same result by combining http and base64, though:
$  http  httpbin.org/post  data=$(base64 < /path/to/file.bin)

Actually, httpie it chokes on the newlines that base64 produces, I managed to do it using openssl enc -A -base64.

@lapo-luchini base64 -w 0 would do as well


Push mobile alalytics sample -swift 3.0 convert error

when I open push mobile alaytics sample , I have to convert Swift 3.0.
but it has compile error.
sns.createPlatformEndpoint(request!).continueWith(executor: AWSExecutor.mainThreadExecutor(), block: { (task: AWSTask!) -> AnyObject! in
-> Generic parameter  'ResultType' could not inferred.

Hi,
This sample has not been updated yet for Swift 3 compatibility.
You can alternatively use Mobile Hub to generate a Swift 3 sample app that uses SNS and Mobile Analytics.


Migrate gce-production-4 to separate network and worker graphs

What is the problem that this PR is trying to fix?
The worker hosts in gce-production-4 are not using a layer of NAT hosts as with gce-production-5 and gce-staging-1.
What approach did you choose and why?
Create a new gce-production-net-4 terraform graph dir and migrate resources via helper scripts to/from gce-production-4.
How can you test this?
make plan && make apply until it's green

NOTE this is applied in production


Add bun as possible package manager

I just added bun as a possible package manager. Its soooo fast 🤩

Thank you for your contribution!


Application not sending messages

In February we deployed Company Communicator. It was working, and most users were receiving messages but there were some exceptions and for some users the messages was not delivered with error "App not installed" but in fact the application was installed. We performed  those steps:
https://github.com/OfficeDev/microsoft-teams-apps-company-communicator/issues/848#issuecomment-1231894640
Navigate to Azure portal and open company communicator deployed resource group
Click on “Storage account”
Expand “Tables” section
Open “AppConfig” table
Delete the second record where Rowkey is entered as “UserAppId”
But in our deployment there was no such key as “UserAppId” and so next we moved to this instruction:
https://github.com/OfficeDev/microsoft-teams-apps-company-communicator/issues/915#issuecomment-1321938761
Navigate to Azure portal and open company communicator deployed resource group
Click on “Storage account”
Expand “Tables” section
Open UserData Table
Except "AuthorData" please remove the remaining entities.
And after cleaning, the messages aren't received by any of our user. All are failing with error "App not installed".

Error as been fixed.


CII best practices badge

Can I convince someone here to try to get for d3.js a “best practices” badge from the Linux Foundation Core Infrastructure Initiative (CII)? I’m the technical lead of the badging project. Someone from the project simply needs to go here and click on “Get Your Badge Now!”:
https://bestpractices.coreinfrastructure.org/
It’s basically a web form, and it shouldn’t take more than hour to fill it in for Blender. It costs nothing. We can help you (if you’d like) once you get started. I’d be happy to answer questions, too.  Node.js already has a badge; other projects with the badge include curl, the Linux kernel, and OWASP ZAP.
Let me know. Thanks!!

Hi David. I appreciate the educational goals of the best-practices project, but I’m afraid I’m not currently willing to spend the time to fill out the form.

It's not really just educational, and we can help with the time.

Even if you did it by yourself, it should not take more than an hour.


no way to specify multiple platforms

Describe the bug
no way to specify multiple platforms in ".slsa-goreleaser.yml"
To Reproduce
# The OS to compile for. `GOOS` env variable will be set to this value.
goos: {{ .Os }}

# The architecture to compile for. `GOARCH` env variable will be set to this value.
goarch: {{ .Arch }}

Expected behavior
each builder will  set its platform
Screenshots
configfromstring: ".slsa-goreleaser.yml": yaml.Unmarshal: yaml: unmarshal errors:
  line 13: cannot unmarshal !!map into string
  line 16: cannot unmarshal !!map into string

Additional context
cant use more platforms via the file

figured it out


Authentication Api missing features marked as TODOs

Can I request that these features be implemented soon?
a. verifyEmailCode function
//TODO Transaction
//Token should expire after a certain period
b. verifyResetPasswordToken
// Has the token expired ?
//TODO delete token
I think they should be at a priority.
Thanks in advance

See https://github.com/FredericHeem/starhackit/pull/178


Update to Occlum 0.29.7

Fixes: #126

blocked by https://github.com/occlum/occlum/issues/1343

Hi. I have test with the change https://github.com/confidential-containers/guest-components/pull/315
also, after the refactoring of guest-components dep, it is need to regenerate a Cargo.lock file.

merged. please try this rev fe8fb1a

Thanks, I'll try asap

merged. please try this rev fe8fb1a

@Xynnn007 all green, thanks!


tf.nn.local_response_normalization lack validation for depth_radius on cpu

Click to expand!
Issue Type
Bug
Source
binary
Tensorflow Version
tf 2.10.0
Custom Code
Yes
OS Platform and Distribution
Linux Ubuntu 20.04
Mobile device
No response
Python version
No response
Bazel version
No response
GCC/Compiler version
No response
CUDA/cuDNN version
No response
GPU model and memory
No response
Current Behaviour?
tf.nn.local_response_normalization lack validation for depth_radius on cpu. depth_radius needs to be an integer as it is the half-width of the 1-D normalization window. However, on cpu it accepts value `0.1`. By contrast, on gpu it can throw error: `requires depth_radius in [1, 7]`.

Standalone code to reproduce the issue
import tensorflow as tf
input = tf.constant([[[[1.0, 2.0, 3.0, 4.0], [5.0, 6.0, 7.0, 8.0], [9.0, 10.0, 11.0, 12.0], [13.0, 14.0, 15.0, 16.0]]]])
depth_radius = 0.1
bias = 1.0
alpha = 0.5
beta = 0.5
with tf.device("cpu"):
    output = tf.nn.local_response_normalization(input=input, depth_radius=depth_radius, bias=bias, alpha=alpha, beta=beta)
    print(output) # pass

with tf.device("gpu"):
    output = tf.nn.local_response_normalization(input=input, depth_radius=depth_radius, bias=bias, alpha=alpha, beta=beta)
    print(output) # error

Relevant log output
tf.Tensor(
[[[[0.8164966 1.1547005 1.2792044 1.3333334]
   [1.3608277 1.3764944 1.3862065 1.3926213]
   [1.3970708 1.40028   1.4026688 1.4044938]
   [1.405919  1.4070529 1.4079696 1.4087214]]]], shape=(1, 1, 4, 4), dtype=float32)
tensorflow.python.framework.errors_impl.InvalidArgumentError: {{function_node __wrapped__LRN_device_/job:localhost/replica:0/task:0/device:GPU:0}} cuDNN requires depth_radius in [1, 7], got: 0 [Op:LRN]

@fuzzyswan,
I tried to execute the code with the alternative approach by providing the int for depth_radius and it is executing without any error. Kindly find the gist of it here.
Also please take a look at the office doc link for the reference. Thank you!

depth_radius
An optional int. Defaults to 5. 0-D. Half-width of the 1-D normalization window

Hi @tilakrayal ,
indeed depth_radius should be int according to documentation, however, input validity checking is missing on CPU and causing inconsistent behaviour on CPU and on GPU. Specifically, CPU accepts 0.1 which is not an integer, but GPU will not accept it. I think if the argument depth_radius has to be an integer, then on CPU the API should do proper checking to avoid API misuse.

@fuzzyswan,
Could you please take a look at this comment from the developer where it was mentioned that CPU and GPU gradients return different results if you pass invalid values to the output_image value. output_image must be the correct forward-pass output given the input_image, and if you pass an invalid value for output_image, the op has no well-defined semantics and let us know if this comment serves the purpose. Thank you!

hi @tilakrayal
I checked the issue you pointed but I think the problem I reported here is not related to gradient computation. Here, the problem is the lack of input validity checking in the forward pass. A simple data type check would help to reject invalid floating depth_radius, and no value validity checking is needed (which I assume would be costly).

@sushreebarsa,
I was able to reproduce the issue on tensorflow v2.10 and nightly. Kindly find the gist of it here.

Hi, Thanks for reporting the issue.
for CPU, for the argument depth_radius, we make conversion of given dtype to int using the function below.
https://github.com/tensorflow/tensorflow/blob/8b82a3001153f04fac08b6aa94d5cfbff45bdba0/tensorflow/python/eager/execute.py#L155-L164
So the depth_radius value 0.1 will become 0, and the result is as expected. Thanks!


Recognition using FIsherFaceRecogniser

This should be it but there can be need for more proper documentation.I wish to work on MTCNN and FaceNet.
It addresses #26

Will be updating your points.
Good work.

Thank you!!:)

Please add a readme file too in this
Explaining the process and output

Hiii i have added your points

They have been updated,thanks


CLOUD-51844 Replace RestTemplate to Jersey client

@akanto plz review

Jenkins build finished, all tests passed.
Refer to this link for build results: http://ci.sequenceiq.com/job/cloudbreak-pull-request/2023/

closing this now and please create a new one when the change will be ready


Any plan to release the trained VNLI model?

Hi,
Thanks for the excellent work! I have briefly read the code repository and paper, but I was unable find the training data and configuration files for training the End-to-end VNLI model. Would you kindly inform me if you have any plans to open source the the trained VNLI model mentioned in section 3.2?

Hi, thanks for the interest, we are working on the data-release + a public version for the end-to-end model. It will take time, and we will update. Thanks.

Hi, it's updated now in the project website, sorry for the delay, please ask if anything is unclear
CSV: https://seetrue.s3.amazonaws.com/wysiwyr_train.csv
Images: https://drive.google.com/file/d/1M1CKmYkIdpFYjCOc9JwXHP5Z7E91CJl3/view?usp=drive_link


Support estimated count with multiple schemas

The EstimateCount could be incorrect when the table lives in multiple schemas. Related to #19775.
See https://wiki.postgresql.org/wiki/Count_estimate:

If you don't need an exact count, the current statistic from the catalog table pg_class might be good enough and is much faster to retrieve for big tables.
SELECT reltuples AS estimate FROM pg_class WHERE relname = 'table_name';
Tables named "table_name" can live in multiple schemas of a database, in which case you get multiple rows for this query. To overcome ambiguity:
SELECT reltuples::bigint AS estimate FROM pg_class WHERE oid = 'schema_name.table_name'::regclass;

And it happened to me:

I don't think it's a bug, because it's correct in most cases. So I labeled this PR with kind/enhancement.

🎺 🤖


Fix entry category assignment in Reader

https://github.com/moov-io/ach/issues/1045

Nice fix, thank you!


Implementing Africa's Talking SMS API using Node JS

Article checklist
Formatting and structure checks

[x] Have you used the correct folder and file structure? - see Contribution Guidelines

[x] Is your article properly formatted in Markdown? - see Github Markdown guide

[x] Have you used our preferred heading structure? - H3 (###) and up

[x] Does your article follow any of the suggested structure formats? - see example formats

[x] Is your article over 750 words? - Tool: Wordcounter.net

[x] Is the article you are submitting an in-depth and unique article? Does it go beyond what is in the official docs and what is covered in other blog sites. See these articles as examples.

[x] Does your article provide enough value and detail about your topic? - Articles should be clear, accurate, and fully explained.

[x] Can your article be understood by beginners? - Assume the audience is smart but has no prior exposure to the common terminology in your article.

[x] Have you included a hero image that is 600x400 pixels, under 300KB in size, and have the copyright to use it? - Tools: Pixlr Image Editor for resizing and Unsplash for Creative Commons images

Grammar & plagiarism checks

[x] Have you spellchecked and grammar checked your article? - Tools: Write&Improve - ProWritingAid - Grammarly
[x] Please place your article through a 3rd party plagiarism checker. We suggest using Quetext, this tool is free and has a daily limit. We typically accept articles with 10% or less.
[x] Have you checked your article for readability? - Tool: Hemmingway
[x] Have you added sources for quotes and images that aren't yours?

Technical checks

[x] Are your code snippets properly formatted for syntax highlighting - see Syntax guide
[x] Have you checked your code runs correctly and you've highlighted all necessary dependencies for installation?
[x] Are the software programs and packages you're highlighting in your article up to date, using current versions and not deprecated?

Topic suggestion this closes
This closes #4994

This closes #4994

@ahmadmardeni1 I would love to review this article.

Hey @owinowendy You have to wait until the current PR assigned to you is published.

Plagiarism check is done.

Great tutorial @mwangiKibui

Hi @mwangiKibui
Good job on the article

@LinusMuema Thanks


VS Code Welcome page will open each time on load/reload regardless of "open on start" setting

When the AppMap extension is installed on VS Code - extension v0.127.0.  The welcome page will open no matter the status of the Appmap tutorial (completed or not) and regardless of the setting "show welcome page on startup" setting.
Here is a loom of the issue.
https://www.loom.com/share/0749ea5e5a354ee789fc35a1b6aa763c

Confirmed. AppMap extension causes Welcome page to always be shown.
Visual Studio Code
Version: 1.95.2
AppMap Extension
v0.131.1
Setup:

Create a new profile (Copy from: none, Source: none)
Activate new profile
Restart VS Code, or >Developer: Reload Window
Welcome page shown (expected)
Uncheck "Show welcome page on startup"
Close Welcome page
Restart VS Code, or >Developer: Reload Window
Welcome page is NOT shown (expected)

settings.json now contains:
{
    "workbench.startupEditor": "none"
}

extensions.json now contains:
[
    {
        "identifier": {
            "id": "appland.appmap",
            "uuid": "41d86b02-68d3-4049-9422-95da6d11cc2e"
        },
        "location": {
            "$mid": 1,
            "fsPath": "/Users/foo/.vscode/extensions/appland.appmap-0.131.1",
            "path": "/Users/foo/.vscode/extensions/appland.appmap-0.131.1",
            "scheme": "file"
        },
        "metadata": {
            "hasPreReleaseVersion": false,
            "id": "41d86b02-68d3-4049-9422-95da6d11cc2e",
            "installedTimestamp":<PHONE_NUMBER>367,
            "isPreReleaseVersion": false,
            "pinned": false,
            "publisherDisplayName": "AppMap",
            "publisherId": "f7f1004e-6038-49cd-a096-4e618fe53f77",
            "source": "gallery",
            "targetPlatform": "undefined",
            "updated": false
        },
        "relativeLocation": "appland.appmap-0.131.1",
        "version": "0.131.1"
    }
]

To reproduce:

Install AppMap extension
Restart VS Code, or >Developer: Reload Window
BUG: Welcome page is shown. ("Show welcome page on startup" is unchecked)

Again to confirm:

Uninstall AppMap extension
Restart VS Code, or >Developer: Reload Window
Welcome page is NOT shown (expected)

This is fixed by https://github.com/getappmap/vscode-appland/pull/1051


Expose LogDisplay options in registration api

Codecov Report

Merging #14 (19e6555) into main (f7d296a) will increase coverage by 0.09%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main      #14      +/-   ##
==========================================
+ Coverage   97.32%   97.41%   +0.09%
==========================================
  Files          12       12
  Lines         112      116       +4
  Branches       16       16
==========================================
+ Hits          109      113       +4
  Partials        3        3

Impacted Files
Coverage Δ

...sions.Logging/LogDisplayLoggerFactoryExtensions.cs
100.00% <100.00%> (ø)

...Rna.Extensions.Logging/LogDisplayLoggerProvider.cs
100.00% <100.00%> (ø)

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 f7d296a...19e6555. Read the comment docs.


Set up linters webpack and jest

In this milestone of Js capstone, we have :

Set up the linters, webpack and jest

Hi @ridabensalem
Your project is complete!  There is nothing else to say other than... it's time to merge it :shipit:
Congratulations! 🎉

Cheers and Happy coding!👏👏👏
Highlights
Professional PR :+1:
All Linter checks are passing :+1:
Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Please, remember to tag me in your question so I can receive the notification.

As described in the Code reviews limits policy  you have a limited number of reviews per project (check the exact number in your Dashboard). If you think that the code review was not fair, you can request a second opinion using this form.


Results not showing in GOLr

We were working on some examples in Noctua Form and graph editors with @tmushayahama and it seems there is a problem with GOLr-noctua. If we type "MGI:", we only have two results where you would expect much more:

@kltm your opinion ? Thanks

Hm. My initial reaction was that you've tripped over one of the many persistent AC bugs (there are tickets :), but further inspection seems to indicate something a little more interesting maybe.
Let's start working out from here.
http://noctua-amigo.berkeleybop.org/amigo/search/ontology
That should be the upstream source for entities in Noctua in general: http://noctua-golr.berkeleybop.org
After releasing all of the filters, we can see that "Ontology ID space" has no MGI IDs at all. Searching for "Csf3 Mmus", however, does give something with an MGI ID.
Clearing again, searching for "Mmus", and adding a negative filter for "PR" in "Ontology ID space", we are left with over 100k terms with namespaces like "MGI", "PR", and "RefSeq".
This behavior seems a little bit off to me.
Pinging @cmungall ; thinking about moving this over to NEO.


Greg/cherry/deposit

Addresses bugs in #200

@GregTheGreek I fixed the tests. Bloody hell it was a mess with those changes. Generally, we should keep deposit contract defaults in one place and in dev defaults, just extend with different bytecode


when transitions are triggered in inactive tabs they accumulate and can cause page freeze

A little background:
The app I'm working is used for monitoring. A common use case is to have a tab open for days.
I noticed that when a tab containing a d3 component becomes active again after a long time being inactive it causes the page to freeze.
I've managed to create a minimal test case demonstrating this: https://bl.ocks.org/guykr/5072b773cd67e6b0bff61dc00d6418f1
A note about why it's implemented this way:
I hijack the native requestAnimationFrame and simulate the tab being inactive to speed up the manifestation of this issue (Since the browser also throttles setInterval calls), but this can be reproduces without these measures by setting up a setInterval loop that schedules transitions, switching to another tab and then waiting for ~1 hour or so.
I'm aware the test case is extreme, but this happens in our app with much slower updates (and longer inactive periods)
Any ideas how this can be mitigated?
Thanks,
Guy
*not sure if this should go to d3-transition or here, but it seems related to #17

Don’t use setInterval to schedule your animations; use d3.interval instead, which will avoid scheduling the animations when the tab is backgrounded.


SQL Example can be added

For the document which shows Model Serving for Compute should also include Databricks SQL warehouse sample

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

ID: 2c2ae573-95d7-dea2-6f9f-18b7605d80fc
Version Independent ID: 2c2ae573-95d7-dea2-6f9f-18b7605d80fc
Content: External models in Databricks Model Serving - Azure Databricks
Content Source: databricks/generative-ai/external-models/index.md
Service: azure-databricks
GitHub Login: @mssaperla
Microsoft Alias: saperla

@ChetanKnowIt
Thanks for your feedback! We will investigate and update as appropriate.

@ChetanKnowIt
Thanks for your contribution. Please add your ideas in below link, so our production team can review it and update the same.
Ideas · Community (azure.com)


Pre public release polish

Allens suggestions in https://github.com/steamclock/netable/issues/56:

Some comments in the examples would help readability
Contributing links nowhere
Does the cocoapods instruction actually work yet?
The image is kind of huge - see Bluejay for a way to make this more reasonable
The "in-depth documentation" link goes nowhere currently.

Added some commentary to examples, but don't feel great about. They still feel sparse but I can't think of anything to add that doesn't seem redundant or obvious.
Removed contributing link, instead added CONTRIBUTING.md and CODE_OF_CONDUCT.md, copied straight from Bluejay.
Repo needs to be public to get Cocoapods set up, waiting for admin access to do so then it will be good to go.
Reduced image size by 70%.
Added in depth docs, will add a link to the GitHub pages link once I have admin access to create them.

@apike  you're listed in Bluejay's CONTRIBUTING.md as a point of contact, do you want the same for Netable in addition to me? Or does it make more sense to have @nbrooke?

Going to merge and let Allen review after again.


is there any option for batch processing?

Is there an option to multi process in a loop for all R1 and R2 fastq inside a folder? I have more than 1000 fastqs to process.. Would be tedious to process them one by one.

Thanks for the question.  It is easy to loop through files on the command-line.  See this reference for examples of writing loops in bash, and this reference for string (filename) manipulation.


feat(execution, JSON-RPC): error handling in execution

Pull Request type
Please check the type of change your PR introduces:

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no API changes)
[ ] Build-related changes
[ ] Documentation content changes
[ ] Other (please describe):

What is the current behavior?

Issue Number: N/A
What is the new behavior?

Does this introduce a breaking change?

[ ] Yes
[ ] No

Other information

This change is

crates/papyrus_execution/src/lib.rs line 468 at r1 (raw file):

        false,
    )?;
    let res: FeeEstimationResult = txs_execution_info

We need the type explicitly here?
Consider
Suggestion:
fee_estimation_result


update dockerfile with non root user

For a better security, a non root user is created once the project is generated under which the application will run in container.

Fixed #22

Fixed #22


Unable to set focus for accessibility VoiceOver

Description
I'm trying to set the focus order of elements in my screen for voiceover to announce in my Swift+RN project, however there is no provision to do the same. I also wanted to discuss if there's any straightforward way to set the focus to an element when a page loads.
We have made multiple attempts to use useRef (Setting focus for accessibility in RN) and none of these seem to be working for us.
iOS uses accessibilityElements to do the same and allows us to set the order of elements. I'm trying to find something similar on React Native which would help me set the reference.
On the web, screen readers determine the flow of which things are read by looking at the DOM tree and going from top the bottom, and this is the way accessibility is managed in React DOM.
However, on the native side this doesn't seem to be the case.
iOS exposes some APIs to allow developers to control this order, but React Native doesn't seem to expose that to the Javascript side.
I am displaying a RN module using the bridge from Swift, as a ViewController.
React Native version:
react-native: 0.63.3 => 0.63.3
OS: macOS 10.15.7
Xcode: 12.2
Steps To Reproduce
Navigating to the next screen in my React Native project does not allow me to set the focus to the first element that I want and the focus is incorrect. In cases where a view is presented in top of another view, the focus falls to the background instead. There are also multiple other issues we face in terms of VoiceOver flexibility.
Expected Results
Be able to set the focus order explicitly, set focus on a particular element when we navigate to a new page.
Apart from these issues on iOS, we also face issues on our parallel Android + RN app, where we are missing Keyboard (Physical BT Keyboard) focus (something similar to what is already mentioned in this issue. The issue of setting focus on a new page persists too.

Facing the same problem. The ordering of my layout makes sense visually, but not for folks using Voiceover.

Looks like this has been an unresolved issue for a while, here's an issue with a bit more activity: https://github.com/react-native-community/discussions-and-proposals/issues/118

This issue should be resolved by #30888 once that issue is closed as part of the Improved React Native Accessibility Project

+1, would appreciate this addition.

@nickmcmillan try grouping your elements using a <ScrollView> instead of a <View> https://github.com/react-native-community/discussions-and-proposals/discussions/389#discussioncomment-7921439


🚀 Feature: Add a Vue integration for konami-emoji-blast

Bug Report Checklist

[X] I have pulled the latest main branch of the repository.
[X] I have searched for related issues and found none that matched my issue.

Overview
Splitting out of #317: this monorepo currently has a @konami-emoji-blast/react package that integrates konami-emoji-blast with Astro. Let's add an equivalent for Nuxt!
@danielroe drove creating https://github.com/danielroe/nuxt-emoji-blast, which prototypes it nicely. https://github.com/danielroe/nuxt-emoji-blast/blob/main/src/runtime/plugins/konami-code.client.ts in particular I think?
I have very little Vue experience so I'm not confident in these matters.
Additional Info
Note that this isn't a good first issue. It might end up being a tricky thing to implement, since you have to understand the equivalent of component/composable lifecycles in Vue (#322) and Nuxt.
Co-authored-by: @danielroe
💖

#317 -> #322 ended up just adding a Nuxt integration, not a Vue one. So this issue should remain open for a Vue integration.


Incorrect generation issue

Winless v1.3.0
When using the following pseudo class
.opacity(@op){
opacity:@op/100;
filter:alpha(opacity=@op);
}
If I use this pseudo in several places of the same file, only the first parameter is used in filter:alpha(opacity=xx);
I have a simple test case:
.opacity(@op){
opacity:@op/100;
filter:alpha(opacity=@op);
}
.test0 {
.opacity(0);
}
.test1 {
.opacity(90);
}
.test2 {
.opacity(70);
}
.test3 {
.opacity(0);
}
Generates ===>
.test0 {
opacity: 0;
filter: alpha(opacity=0);
}
.test1 {
opacity: 0.9;
filter: alpha(opacity=0);
}
.test2 {
opacity: 0.7;
filter: alpha(opacity=0);
}
.test3 {
opacity: 0;
filter: alpha(opacity=0);
}
====
opacity is OK
filter is not OK
Thanks for this very useful tool !

Having the same issue


incremental models on postgres are only fast if all CTEs are ephemeral

Describe the bug
When making a postgres-backed model incremental, you would expect the incremental loads of raw data to be faster. Instead, they get slower. However, once you set all the contribution CTEs (separate DBT files) to ephemeral, and make sure the CTEs are consumed in a row with one descendant only (i.e.: with a from b, b from c, c from d, d from source -- so that it can be inlined), you do get the performance benefits.
That means: Views are performance barriers that prevent the optimizer from pushing down the {{is_incremental}} stuff to the underlying queries from which the views are selected.
Maybe you could mention that in the documentation?
Steps To Reproduce
In as much detail as possible, please provide steps to reproduce the issue. Sample data that triggers the issue, example model code, etc is all very helpful here.
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots and log output
If applicable, add screenshots or log output to help explain your problem.
System information
Which database are you using dbt with?

[X] postgres
[ ] redshift
[ ] bigquery
[ ] snowflake
[ ] other (specify: ____________)

The output of dbt --version:
installed version: 0.17.1
   latest version: 0.17.2

Your version of dbt is out of date! You can find instructions for upgrading here:
https://docs.getdbt.com/docs/installation

Plugins:
  - postgres: 0.17.1
  - redshift: 0.17.1
  - snowflake: 0.17.1
  - bigquery: 0.17.1

The operating system you're using:
$ uname -a
Linux 21d117632cc9 5.3.0-55-generic #49-Ubuntu SMP Thu May 21 12:47:19 UTC 2020 x86_64 GNU/Linux
i.e. the official docker container for python:latest
The output of python --version:
Python 3.8.4
Additional context
Add any other context about the problem here.

Hey @TjrGithub, you've got a good point. Postgres is, structurally, a very different databases from the analytics-forward data warehouses with which we most often work. I'm not surprised to hear that Postgres' optimizer fails to push down filters into the underlying views; older versions of Postgres (<12) treated CTEs as optimization fences, too. This was one of the biggest innovations of Redshift's optimizer, in the early days of analytic databases.

Maybe you could mention that in the documentation?

I think this is a great idea! I'm going to transfer this issue to our docs.getdbt.com repo, since I don't foresee a code change in this one.


Port rabema

We might have missed rabema in #8
https://github.com/seqan/seqan/tree/develop/apps/rabema
The readme links to https://seqan.de/projects/rabema.html
The rabema website also contained the manual
Rabema was not on the old website:
https://marehr.github.io/old.seqan.de/applications/index.html
But it was on the older website:
https://web.archive.org/web/20141113031730/http://www.seqan.de/projects/rabema/

Here is a list of all applications present on the old old website but not on the old and not on the current website:
ALF, Breakpoint Calculator, DFI, Rabema, Insegt, PISAtoolbox, NGS Rai, SeqCons, SnpStore, SplazerS.

I created this list based on the make file from the respective repositories of the apps.

I'm confused what you mean with not seqan2 and seqan2. All these apps use seqan2.
Did you perhaps look at the SEQAN_APP_VERSION? This is the version of the app, not the library.

Indeed I looked at the 'SEQAN_APP_VERSION'
I'll port some more apps.


fixed rate limiter publish_rate_limit_test occasionally failing

@khodzha Thanks, looks good to me. Only change outside test is that we put a TRef in init, right? (which then just sits there)

yeah, that's right; also take a closer look at my 10.5 secs in test, i think that should be a correct value but I'm not sure

Let's see if this fixes tests on other PR.


charts: helm for installing manager

created a helm chart for installing the manager to used with:
helm install -g m4d

for testing purposes (to be optimized and put in the CI in a later phase):
cd charts
make run-integration-tests

Instead of duplicating default to nocrd, make default include crds + nocrd. A better name than nocrd will also be nice.

as default is the autogenerated directory I rather that crd and nocrd reference default as to the name nocrd I am fine with an alternative name as long as its' short :-)

as default is the autogenerated directory I rather that crd and nocrd reference default

I don't understand this statement. What do you mean "crd and nocrd reference default"? Also, I thought that only crds and rbac are auto generated now.

Please check why CI failed. Also update manager/README.md if and where needed.

Please check why CI failed. Also update manager/README.md if and where needed.

will do so when I manage to get the entire integration test working on helm, and then I will update the entire section addressing installation

The thing is that other devs deploy manager directly and now it will no longer work without first applying the crds. We need to reflect that somehow even if it's temporary.

The thing is that other devs deploy manager directly and now it will no longer work without first applying the crds. We need to reflect that somehow even if it's temporary.

the made the change, but IMHO the README provides little value and developers will typically rather read the code itself. please consider that we delete this file


Updating release doc with recent releases

Changes
This updates the release.md document with the most recent versions.
This should probably be generated (and auto-updated as well) as it seems a bit tedious to maintain — probably why it was not up-to-date 🙃 @tektoncd/core-maintainers
/kind docs
Submitter Checklist
As the author of this PR, please check off the items in this checklist:

[x] Has Docs if any changes are user facing, including updates to minimum requirements e.g. Kubernetes version bumps
[ ] Has Tests included if any functionality added or changed
[x] Follows the commit message standard
[x] Meets the Tekton contributor standards (including functionality, content, code)
[x] Has a kind label. You can add one by adding a comment on this PR that contains /kind <type>. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tep
[x] Release notes block below has been updated with any user facing changes (API changes, bug fixes, changes requiring upgrade notices or deprecation warnings). See some examples of good release notes.
[ ] Release notes contains the string "action required" if the change requires additional action from users switching to the new release

Release Notes
NONE

/kind doc

/kind documentation

I think the missed updates were my fault because I forgot to update my own PR https://github.com/tektoncd/pipeline/pull/6583

I'll close my PR as superseded by this one.

/lgtm


Please remove version constraint on effectful-core in *.cabal file

Unless there is a good reason to have it? It builds with the newer versions without a problem...

I updated the upper version bounds of effectful-core to allow the latest version.

Thanksies! Can you do the same for log-effectful?
On Sat, Aug 20, 2022 at 1:18 PM Mann mit Hut @.***>
wrote:

I updated the upper version bounds of effectful-core to allow the latest
version.
—
Reply to this email directly, view it on GitHub
https://github.com/haskell-effectful/time-effectful/issues/3#issuecomment-1221296210,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGKRDX3NK3YBO3RTFNVD47LV2C5H3ANCNFSM56V6DQ2A
.
You are receiving this because you authored the thread.Message ID:
@.***>


ARM email interval to 3d and add pull_request scope limit

Latest improvements:
MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Contribution checklist:

[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and have all been fixed in this PR.
[ ] The OpenAPI Hub was used for checking validation status and next steps.

ARM API Review Checklist

[ ] Service team MUST add the "WaitForARMFeedback" label if the management plane API changes fall into one of the below categories.
adding/removing APIs.
adding/removing properties.
adding/removing API-version.
adding a new service in Azure.

Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.

[ ] If you are blocked on ARM review and want to get the PR merged urgently, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
Please follow the link to find more details on API review process.

Automation for azure-sdk-for-python

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk


Add Recipe for Android Messages

Including unread message badge count

While the implementation for unread message count does work currently, it uses what looks like generated CSS classes, which is unreliable as they change when they build the CSS files again. I feel like there has to be a more robust method for getting the unread count. With that said, I think this should get merged, but a better solution should be considered for message count for the future.
Thanks for making the recipe @dweinber!

Agree, I'm not happy with the unread count but couldn't find something better so far. Definitely open to suggestions and will also look again if I can find a better way.

Please see my pull request @dweinber https://github.com/dweinber/franz-recipe-android-messages/pull/3 :)

When will this PR get accepted?

ping @adlk


v100 cannot calculate bf16

Hello, how do I modify the configuration if I want to use it on 32G v100?

Do you mean run.py line 39 error?
I tried:
with torch.cuda.amp.autocast(dtype=torch.float32):
but results are bad.

we added fp16 support fully working : https://github.com/Stability-AI/StableCascade/issues/125