fix issue #870, support Statement#execute for SELECT_FOR_UPDATE

Signed-off-by: hongwei yi<EMAIL_ADDRESS>
Ⅰ. Describe what this PR did
support Statement#execute for SELECT_FOR_UPDATE
Ⅱ. Does this pull request fix one issue?

fixes #870
Ⅲ. Why don't you add test cases (unit test/integration test)?
I've tested this in seata-examples. BTW, Seata need more test cases in the project.
Ⅳ. Describe how to verify it
Connection conn = dataSourceProxy.getConnection();
Statement stmt = conn.createStatement();
stmt.execute("select * from table where id=? for update");
Ⅴ. Special notes for reviews

Codecov Report

Merging #875 into develop will decrease coverage by 0.03%.
The diff coverage is 0%.

@@              Coverage Diff              @@
##             develop     #875      +/-   ##
=============================================
- Coverage      38.71%   38.67%   -0.04%
  Complexity      1026     1026
=============================================
  Files            220      220
  Lines           8498     8498
  Branches        1023     1023
=============================================
- Hits            3290     3287       -3
- Misses          4821     4823       +2
- Partials         387      388       +1

Impacted Files
Coverage Δ
Complexity Δ

...ta/rm/datasource/exec/SelectForUpdateExecutor.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

...a/io/seata/rm/datasource/exec/ExecuteTemplate.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

...o/seata/server/coordinator/DefaultCoordinator.java
52.14% <0%> (-1.43%)
16% <0%> (ø)

...eata/server/store/FileTransactionStoreManager.java
53% <0%> (-0.5%)
15% <0%> (ø)

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 0b2c3bd...5783318. Read the comment docs.

RootContext.bind("123456:8091");
DataSourceProxy dataSourceProxy = (DataSourceProxy)storageContext.getBean("accountDataSourceProxy");
Connection conn = dataSourceProxy.getConnection();
PreparedStatement stmt=conn.prepareStatement("select * from account_tbl where id=36 for update");
stmt.execute();


Flow <= 0.47 requires libelf

Running flow <= 0.47 in Docker containers is quirky because of it's requirement on libelf.
This requirement has been removed in 0.48.

Fixed by #10


firebase_admob plugin displays smart banner at top instead of bottom

firebase_admob's show() method by default sets the anchorType to AnchorType.bottom. However, this setting isn't being honored on iOS 8, 9, and 10. iOS 11 and 12 appear to work fine.
About 10% of the time, it works as expected. 🤔
Steps to Reproduce

Run the below sample code on iOS 8-10.
The banner should be at the bottom.
Instead, the banner is at the top.

import 'package:firebase_admob/firebase_admob.dart';
import 'package:flutter/material.dart';

void main() => runApp(MyApp());

class MyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      home: MainPage(),
    );
  }
}

class MainPage extends StatefulWidget {
  @override
  MainPageState createState() => MainPageState();
}

class MainPageState extends State<MainPage> {
  BannerAd _bannerAd;

  @override
  void initState() {
    super.initState();
    FirebaseAdMob.instance.initialize(appId: FirebaseAdMob.testAppId);
  }

  @override
  Widget build(BuildContext context) {
    _bannerAd ??= createBannerAd();
    _bannerAd..load()..show();
    return Container();
  }

  BannerAd createBannerAd() {
    return BannerAd(
      adUnitId: BannerAd.testAdUnitId,
      size: AdSize.smartBanner,
      listener: (MobileAdEvent event) {
        print('BannerAd event $event');
      },
    );
  }
}

Logs

[✓] Flutter (Channel stable, v1.0.0, on Mac OS X 10.14.2 18C54, locale en-US)
    • Flutter version 1.0.0 at /Users/westy92/Source/flutter
    • Framework revision 5391447fae (8 weeks ago), 2018-11-29 19:41:26 -0800
    • Engine revision 7375a0f414
    • Dart version 2.1.0 (build 2.1.0-dev.9.4 f9ebf21297)

[✓] Android toolchain - develop for Android devices (Android SDK 28.0.3)
    • Android SDK at /Users/westy92/Library/Android/sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-28, build-tools 28.0.3
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1248-b01)
    • All Android licenses accepted.

[✓] iOS toolchain - develop for iOS devices (Xcode 10.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 10.1, Build version 10B61
    • ios-deploy 1.9.4
    • CocoaPods version 1.6.0.beta.2

[✓] Android Studio (version 3.3)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 31.3.3
    • Dart plugin version 182.5124
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1248-b01)

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

[✓] Connected device (1 available)
    • Seth's iPod touch • <redacted> • ios • iOS 9.3.5

• No issues found!

Below are simulators, in order: iOS 8.4, 9.3, 10.3.1, 11.4, 12.1.

We see this behavior as well.
Would be great when it could be fixed soon.
Regards,
Florian

@sdolsky Using "add reaction" on the initial comment would increase priority.

Also encountering this issue with last dev versions

i have this problem too!

Same here!

Any news?

Finally I found the solution. The main reason of the problem translatesAutoresizingMaskIntoConstraints property is setting to NO on pre ios 11. And location calculations will not be apply in this layout.
Move the following code line _banner.translatesAutoresizingMaskIntoConstraints = NO;  to inside of the if (@available(ios 11.0, *)) statement in FLTMobileAd.m file.
_banner.translatesAutoresizingMaskIntoConstraints = NO;
UIView *screen = [FLTMobileAd rootViewController].view;
[screen addSubview:_banner];
#if defined(__IPHONE_11_0) && (__IPHONE_OS_VERSION_MAX_ALLOWED >= __IPHONE_11_0)
if (@available(ios 11.0, *)) {
UILayoutGuide *guide = screen.safeAreaLayoutGuide;
[NSLayoutConstraint activateConstraints:@[
[_banner.centerXAnchor constraintEqualToAnchor:guide.centerXAnchor],
[_banner.bottomAnchor
constraintEqualToAnchor:_anchorType == 0 ? guide.bottomAnchor : guide.topAnchor
constant:_anchorOffset]
]];
} else {
[self placeBannerPreIos11];
}
To
UIView *screen = [FLTMobileAd rootViewController].view;
[screen addSubview:_banner];
#if defined(__IPHONE_11_0) && (__IPHONE_OS_VERSION_MAX_ALLOWED >= __IPHONE_11_0)
if (@available(ios 11.0, *)) {
_banner.translatesAutoresizingMaskIntoConstraints = NO;
UILayoutGuide *guide = screen.safeAreaLayoutGuide;
[NSLayoutConstraint activateConstraints:@[
[_banner.centerXAnchor constraintEqualToAnchor:guide.centerXAnchor],
[_banner.bottomAnchor
constraintEqualToAnchor:_anchorType == 0 ? guide.bottomAnchor : guide.topAnchor
constant:_anchorOffset]
]];
} else {
[self placeBannerPreIos11];
}
For more information about this property you can visit the link below.
https://developer.apple.com/documentation/uikit/uiview/1622572-translatesautoresizingmaskintoco
And the result

Great find! 🎉

The open PR looks promising! Hoping it gets some attention. 🤞

I had the same problem (on ios 10), the banner that should be placed at the centered at the bottom is appearing in top left corner. After a while when the ad changes to the next, it gets its position fixed.
I was wondering why this project does not offer a way to place ads inside the widget tree.
That would be a huge improvement.

@westy92
This issue has been moved to https://github.com/FirebaseExtended/flutterfire/issues/467. Any further collaboration will be done there.

Since firebase_admob issues require work on the Flutter side as well as the plugin side these issues will remain open here as well until resolved.

Hi @westy92
I see there's an open issue addressing the case you described.
Please follow up on that issue,
I'm closing the current one as duplicate.
If you disagree please write in the comments
and I will reopen it.
Thank you

@westy92
This issue has been moved to FirebaseExtended/flutterfire#467. Any further collaboration will be done there.

please do not make cyclic reference because [FirebaseExtended/flutterfire#467] refers to this bug report https://github.com/FirebaseExtended/flutterfire/issues/467#issuecomment-541444232 .  noise .. :(

i have this problem too!

@inuyashaaa : i integrated fix, suggested somewhere here in forked repo https://github.com/izinin/flutterfire.git ,try this in pubspec.yaml (below) I hope in new version admob_firebase the issue will be fixed officially:
diff:

firebase_admob: ^0.9.0+10

workaround for

https://github.com/FirebaseExtended/flutterfire/pull/45/files

adjusting adBanner https://github.com/flutter/flutter/issues/14222

firebase_admob: #^0.9.0+10
git:

 url: https://github.com/izinin/flutterfire.git

 path: packages/firebase_admob

 ref: admob_fix_missplaced_banner

Any updates?

@dayron9110
this issue is a duplicate, please follow up here

How Can I fix this issue? @iapicca


Add support for #![no_std] to the wasmtime crate

This commit is the final technical piece of #8341 which makes the wasmtime crate itself compatible with #![no_std]. This means that the crate can now be compiled on targets that don't have std when the activated features are a subset of {runtime, gc, component-model}. Support for Wasmtime requires an implementation of wasmtime-platform.h which is something I'd like to also start moving to release artifacts after this as well.
This PR is split into a series of commits with the final one being the "big one" and the others are minor refactorings leading up to it. The major changes made here are:

The "custom" platform of Wasmtime is now enabled by default if nothing else is applicable. This means that there's no opt-in required for no_std support.
Embedders can now define a custom feature detection function, for example "does this host support AVX". This is because the default implementation uses the standard library while that's not available with no_std.
Internal idioms in wasmtime have change to be similar to previous commits for wasmtime-environ and other crates, for example. For example imports come from core and alloc and there's a custom prelude for core + alloc bits and pieces.
Wasmtime now unconditionally uses hashbrown::HashMap for some items such as Linker and GC sets.
The wasmtime crate has a few "custom synchronization primitives" which have real implementations backed by other crates in std mode or "dummy" implementations in no_std mode that effectively assert for no contention. This might require updates to wasmtime-platform.h in the future instead.
Libcall intrinsics for float-related functionality are implemented with the libm crate in no_std mode. In std mode they still use standard library methods.

The main remaining piece I'd like to tackle after this is an update of the no_std documentation for Wasmtime. The page is outdated now and could use some updates. I'll also note that I still have yet to test all these changes beyond what CI is already doing. We don't actually test no_std mode in CI, only that it builds. If anything comes up though I'll work through that in follow-ups.

(Taking a look, might be a little while to get through everything here)


Is it possible to lower TX power?

Would love to have the option to TX below "low" power, In the mw without creating harmonics

duplicate #290


Overwrite ips which should be routed in wireguard config

Your current version takes all ips which the client has to access and put them into AllowedIPs. It would be nice to overwrite them. So e.g instead of:

<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS> and many more in same range

Simply <IP_ADDRESS>/8 if needed
e.g ConfigKey OverwriteAllowedIPs= <IP_ADDRESS>/8, <IP_ADDRESS>/16
I hope its understandable

So there are a couple problems with this suggestion, first off if you supply a /8 it means you're effectively capturing that entire range making it unusable for any other application which might not be super great for users who run services on their own internal networks.
Its best to be as specific as possible when capturing IPv4 routes.
Secondly, there is no good mechanism to determine what routes would overlap well instead of capturing massive blocks.
Thirdly, you can already do this by creating a road warrior sort of config where you capture all routes <IP_ADDRESS>/0 and then define specific MFA routes later as MFA routes take precedence.
Im going to mark this as not-planned as Its not something I want to add to the project for these reasons.


Using ATSS to train the VOC data set loss has always been NAN

atss_r50_fpn_1x_coco.py
base = [
'../base/datasets/voc0712.py',
'../base/schedules/schedule_1x.py', '../base/default_runtime.py'
]
The loss is ;
lr: 1.000e-02, eta: 17:28:39, time: 0.231, data_time: 0.004, memory: 2024, loss_cls: 21.8341, loss_bbox: nan, loss_centerness: nan, loss: nan

ATSS might be unstable with small dataset. You may consider use it with an ATSS detector pre-trained on COCO.


Error while using DinD

Hi,
I am trying to run a workflow with container  as below. I need to run the workflow inside a container because I want to add the custom image for each workflow.
runs-on: Self-Hosted-runner
  container:
             image: busybox:latest
  steps:

Using below for registering my action-runners:
apiVersion: actions.summerwind.dev/v1alpha1
kind: RunnerDeployment
metadata:
  name: ghe-runner-deployment
spec:
  replicas: 2
  template:
    spec:
      enterprise: deutsche-bank
      dockerdWithinRunnerContainer: true
      resources:
        limits:
          cpu: "4000m"
          memory: "2Gi"
        requests:
          cpu: "200m"
          memory: "200Mi"
      volumeMounts:
      - mountPath: /runner
        name: runner
      volumes:
      - name: runner
        emptyDir: {}

while running the workflow the container starts successfully from the runner but the github actions fails
complete log for workflow below
2021-02-18T09:29:53.2256348Z ##[section]Starting: Request a runner to run this job
2021-02-18T09:29:53.2921546Z Can't find any online and idle self-hosted runner in current repository that matches the required labels: 'dind'
2021-02-18T09:29:53.4427859Z Found online and idle self-hosted runner in current repository's organization/enterprise account that matches the required labels: 'dind'
2021-02-18T09:29:53.8062202Z ##[section]Finishing: Request a runner to run this job
2021-02-18T09:30:22.6419896Z Current runner version: '2.277.1'
2021-02-18T09:30:22.6425803Z Runner name: 'ghe-runner-deployment-6gpv5-hlshn'
2021-02-18T09:30:22.6426860Z Runner group name: 'Default'
2021-02-18T09:30:22.6429017Z Machine name: 'ghe-runner-deployment-6gpv5-hlshn'
2021-02-18T09:30:22.6433802Z ##[group]GITHUB_TOKEN Permissions
2021-02-18T09:30:22.6435715Z Actions: write
2021-02-18T09:30:22.6436500Z Checks: write
2021-02-18T09:30:22.6437079Z Contents: write
2021-02-18T09:30:22.6438012Z Deployments: write
2021-02-18T09:30:22.6438646Z Issues: write
2021-02-18T09:30:22.6439217Z Metadata: read
2021-02-18T09:30:22.6440225Z OrganizationPackages: write
2021-02-18T09:30:22.6440975Z Packages: write
2021-02-18T09:30:22.6441784Z PullRequests: write
2021-02-18T09:30:22.6442488Z RepositoryProjects: write
2021-02-18T09:30:22.6443451Z SecurityEvents: write
2021-02-18T09:30:22.6444130Z Statuses: write
2021-02-18T09:30:22.6444884Z ##[endgroup]
2021-02-18T09:30:22.6449864Z Prepare workflow directory
2021-02-18T09:30:22.7688846Z Prepare all required actions
2021-02-18T09:30:22.7704422Z Getting action download info
2021-02-18T09:30:23.1508318Z Download action repository 'actions/checkout@v2'
2021-02-18T09:30:23.6749615Z Download action repository 'actions/setup-java@v1'
2021-02-18T09:30:24.6977212Z ##[group]Checking docker version
2021-02-18T09:30:24.6985720Z ##[command]/usr/local/bin/docker version --format '{{.Server.APIVersion}}'
2021-02-18T09:30:25.5563257Z Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
2021-02-18T09:30:25.5565015Z '
2021-02-18T09:30:25.5656484Z ##[error]Exit code 1 returned from process: file name '/usr/local/bin/docker', arguments 'version --format '{{.Server.APIVersion}}''.
2021-02-18T09:30:25.5758953Z ##[error]Value cannot be null. (Parameter 'network')
2021-02-18T09:30:25.5776354Z Cleaning up orphan processes

@sandeepraj-chandrakant-bhandari-db Hey! I think I'm not expert in GitHub Actions itself but this seems like due to that the busyboxy image doesn't have nodejs installed. nodejs is required by acrious action like checkout. So.. could you try using another container image that does have nodejs (or anything your action needs)?

@mumoshu sorry attached wrong logs. correcting it above.

Probably you missed specifying the dind runner image we publish on docker hub, in your runner spec (or runner deployment's spec template) image field? By default every runner creates the pod from the runner image without dind.

@mumoshu Yes, thank you.. It worked.. But ran into the same problem that I pasted before.
2021-02-18T09:46:24.6174979Z ##[section]Starting: Request a runner to run this job
2021-02-18T09:46:24.7283478Z Can't find any online and idle self-hosted runner in current repository that matches the required labels: 'dind1'
2021-02-18T09:46:24.9474878Z Found online and idle self-hosted runner in current repository's organization/enterprise account that matches the required labels: 'dind1'
2021-02-18T09:46:25.2941224Z ##[section]Finishing: Request a runner to run this job
2021-02-18T09:46:54.3789707Z Current runner version: '2.277.1'
2021-02-18T09:46:54.3797585Z Runner name: 'foobar-group-runnerdeploy-75n5r-wmkbx'
2021-02-18T09:46:54.3799699Z Runner group name: 'Default'
2021-02-18T09:46:54.3803166Z Machine name: 'foobar-group-runnerdeploy-75n5r-wmkbx'
2021-02-18T09:46:54.3807982Z ##[group]GITHUB_TOKEN Permissions
2021-02-18T09:46:54.3810912Z Actions: write
2021-02-18T09:46:54.3811863Z Checks: write
2021-02-18T09:46:54.3812900Z Contents: write
2021-02-18T09:46:54.3813885Z Deployments: write
2021-02-18T09:46:54.3814788Z Issues: write
2021-02-18T09:46:54.3815428Z Metadata: read
2021-02-18T09:46:54.3816497Z OrganizationPackages: write
2021-02-18T09:46:54.3817267Z Packages: write
2021-02-18T09:46:54.3817965Z PullRequests: write
2021-02-18T09:46:54.3819081Z RepositoryProjects: write
2021-02-18T09:46:54.3820054Z SecurityEvents: write
2021-02-18T09:46:54.3820989Z Statuses: write
2021-02-18T09:46:54.3821894Z ##[endgroup]
2021-02-18T09:46:54.3827056Z Prepare workflow directory
2021-02-18T09:46:54.4917361Z Prepare all required actions
2021-02-18T09:46:54.4933430Z Getting action download info
2021-02-18T09:46:54.7940279Z Download action repository 'actions/checkout@v2'
2021-02-18T09:46:55.4463222Z Download action repository 'actions/setup-java@v1'
2021-02-18T09:46:56.1372869Z ##[group]Checking docker version
2021-02-18T09:46:56.1382491Z ##[command]/usr/local/bin/docker version --format '{{.Server.APIVersion}}'
2021-02-18T09:46:56.2013254Z '1.40'
2021-02-18T09:46:56.2037753Z Docker daemon API version: '1.40'
2021-02-18T09:46:56.2039073Z ##[command]/usr/local/bin/docker version --format '{{.Client.APIVersion}}'
2021-02-18T09:46:56.2575580Z '1.40'
2021-02-18T09:46:56.2612669Z Docker client API version: '1.40'
2021-02-18T09:46:56.2623744Z ##[endgroup]
2021-02-18T09:46:56.2625163Z ##[group]Clean up resources from previous jobs
2021-02-18T09:46:56.2632304Z ##[command]/usr/local/bin/docker ps --all --quiet --no-trunc --filter "label=60e226"
2021-02-18T09:46:56.3108641Z ##[command]/usr/local/bin/docker network prune --force --filter "label=60e226"
2021-02-18T09:46:56.4223742Z ##[endgroup]
2021-02-18T09:46:56.4224366Z ##[group]Create local container network
2021-02-18T09:46:56.4232807Z ##[command]/usr/local/bin/docker network create --label 60e226 github_network_4f7a224d0c30462aa0c518ef5525ad49
2021-02-18T09:46:56.5604632Z 9b3946b7bf3ecfe801169c9aaf0b8babd27943b9f18dfe31d387c2fa0cc572d3
2021-02-18T09:46:56.5633885Z ##[endgroup]
2021-02-18T09:46:56.5642111Z ##[group]Starting job container
2021-02-18T09:46:56.5648285Z ##[command]/usr/local/bin/docker pull busybox:latest
2021-02-18T09:46:57.6170009Z latest: Pulling from library/busybox
2021-02-18T09:46:57.9250127Z 4c892f00285e: Pulling fs layer
2021-02-18T09:46:58.3275338Z 4c892f00285e: Verifying Checksum
2021-02-18T09:46:58.3279767Z 4c892f00285e: Download complete
2021-02-18T09:46:58.5021144Z 4c892f00285e: Pull complete
2021-02-18T09:46:58.5161741Z Digest: sha256:e1488cb900233d035575f0a7787448cb1fa93bed0ccc0d4efc1963d7d72a8f17
2021-02-18T09:46:58.5257437Z Status: Downloaded newer image for busybox:latest
2021-02-18T09:46:58.5271602Z docker.io/library/busybox:latest
2021-02-18T09:46:58.5333115Z ##[command]/usr/local/bin/docker create --name 9c4e526f4d2341bdbb77374d28b5cb79_busyboxlatest_47dbb4 --label 60e226 --workdir /__w/artifactory-example-pipeline/artifactory-example-pipeline --network github_network_4f7a224d0c30462aa0c518ef5525ad49  -e "HOME=/github/home" -e GITHUB_ACTIONS=true -e CI=true -v "/var/run/docker.sock":"/var/run/docker.sock" -v "/runner/_work":"/__w" -v "/runner/externals":"/__e":ro -v "/runner/_work/_temp":"/__w/_temp" -v "/runner/_work/_actions":"/__w/_actions" -v "/runner/_work/_tool":"/__w/_tool" -v "/runner/_work/_temp/_github_home":"/github/home" -v "/runner/_work/_temp/_github_workflow":"/github/workflow" --entrypoint "tail" busybox:latest "-f" "/dev/null"
2021-02-18T09:46:59.5226468Z 2850241ded25f5e39321a8c26da7f44c15859f05473255a056cbebceb703dec1
2021-02-18T09:46:59.5239043Z ##[command]/usr/local/bin/docker start 2850241ded25f5e39321a8c26da7f44c15859f05473255a056cbebceb703dec1
2021-02-18T09:47:00.0585063Z 2850241ded25f5e39321a8c26da7f44c15859f05473255a056cbebceb703dec1
2021-02-18T09:47:00.0624650Z ##[command]/usr/local/bin/docker ps --all --filter id=2850241ded25f5e39321a8c26da7f44c15859f05473255a056cbebceb703dec1 --filter status=running --no-trunc --format "{{.ID}} {{.Status}}"
2021-02-18T09:47:00.1044683Z 2850241ded25f5e39321a8c26da7f44c15859f05473255a056cbebceb703dec1 Up Less than a second
2021-02-18T09:47:00.1094174Z ##[command]/usr/local/bin/docker inspect --format "{{range .Config.Env}}{{println .}}{{end}}" 2850241ded25f5e39321a8c26da7f44c15859f05473255a056cbebceb703dec1
2021-02-18T09:47:00.1506589Z HOME=/github/home
2021-02-18T09:47:00.1509102Z GITHUB_ACTIONS=true
2021-02-18T09:47:00.1510419Z CI=true
2021-02-18T09:47:00.1511489Z PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
2021-02-18T09:47:00.1576686Z ##[endgroup]
2021-02-18T09:47:00.1577942Z ##[group]Waiting for all services to be ready
2021-02-18T09:47:00.1580036Z ##[endgroup]
2021-02-18T09:47:00.1918871Z ##[group]Run actions/checkout@v2
2021-02-18T09:47:00.1926501Z with:
2021-02-18T09:47:00.1927724Z   repository: hk-test-org/artifactory-example-pipeline
2021-02-18T09:47:00.1930391Z   token: ***
2021-02-18T09:47:00.1931117Z   ssh-strict: true
2021-02-18T09:47:00.1932195Z   persist-credentials: true
2021-02-18T09:47:00.1934174Z   clean: true
2021-02-18T09:47:00.1934908Z   fetch-depth: 1
2021-02-18T09:47:00.1935625Z   lfs: false
2021-02-18T09:47:00.1936319Z   submodules: false
2021-02-18T09:47:00.1937307Z ##[endgroup]
2021-02-18T09:47:00.1976576Z ##[command]/usr/local/bin/docker exec  2850241ded25f5e39321a8c26da7f44c15859f05473255a056cbebceb703dec1 sh -c "cat /etc/*release | grep ^ID"
2021-02-18T09:47:00.4978966Z OCI runtime exec failed: exec failed: container_linux.go:349: starting container process caused "no such file or directory": unknown
2021-02-18T09:47:00.5180270Z Post job cleanup.
2021-02-18T09:47:00.5188419Z ##[command]/usr/local/bin/docker exec  2850241ded25f5e39321a8c26da7f44c15859f05473255a056cbebceb703dec1 sh -c "cat /etc/*release | grep ^ID"
2021-02-18T09:47:00.8353122Z OCI runtime exec failed: exec failed: container_linux.go:349: starting container process caused "no such file or directory": unknown
2021-02-18T09:47:00.8841988Z Stop and remove container: 9c4e526f4d2341bdbb77374d28b5cb79_busyboxlatest_47dbb4
2021-02-18T09:47:00.8846847Z ##[command]/usr/local/bin/docker rm --force 2850241ded25f5e39321a8c26da7f44c15859f05473255a056cbebceb703dec1
2021-02-18T09:47:01.1561181Z 2850241ded25f5e39321a8c26da7f44c15859f05473255a056cbebceb703dec1
2021-02-18T09:47:01.1621989Z Remove container network: github_network_4f7a224d0c30462aa0c518ef5525ad49
2021-02-18T09:47:01.1628492Z ##[command]/usr/local/bin/docker network rm github_network_4f7a224d0c30462aa0c518ef5525ad49
2021-02-18T09:47:01.2819139Z github_network_4f7a224d0c30462aa0c518ef5525ad49
2021-02-18T09:47:01.2900856Z Cleaning up orphan processes

the container is created with external mounts which should contain the node binaries. Below is from log of container creation
 /usr/local/bin/docker create --name 9c4e526f4d2341bdbb77374d28b5cb79_busyboxlatest_47dbb4 --label 60e226 --workdir /__w/artifactory-example-pipeline/artifactory-example-pipeline --network github_network_4f7a224d0c30462aa0c518ef5525ad49  -e "HOME=/github/home" -e GITHUB_ACTIONS=true -e CI=true -v "/var/run/docker.sock":"/var/run/docker.sock" -v "/runner/_work":"/__w" -v "/runner/externals":"/__e":ro -v "/runner/_work/_temp":"/__w/_temp" -v "/runner/_work/_actions":"/__w/_actions" -v "/runner/_work/_tool":"/__w/_tool" -v "/runner/_work/_temp/_github_home":"/github/home" -v "/runner/_work/_temp/_github_workflow":"/github/workflow" --entrypoint "tail" busybox:latest "-f" "/dev/null"

@mumoshu I am facing similar issue as in the thread https://github.com/summerwind/actions-runner-controller/issues/60
I tried to change the actions/checkout@v2 to actions/checkout@v1 and this action worked.
But now facing same issue in other actions like actions/setup-java@v1.
Is there any solution for this yet?

@sandeepraj-chandrakant-bhandari-db Honestly I haven't tested the dockerdWithinRunnerContainer option recently so our dind dockerfile and controller may be not working well together now...?
Well anyway, I thought #60 was about /runner not properly mounted to docker-in-docker-in-docker containers created by the checkout action. Does it the case for you, too? From the logs you've shared, looks no - or am I missing something...?

What I don't get is why usr/local/bin/docker exec  2850241ded25f5e39321a8c26da7f44c15859f05473255a056cbebceb703dec1 sh -c "cat /etc/*release | grep ^ID" fails with the no such file or directory error. Does it actually run on a busybox container?

@mumoshu it is failing because it is not getting externals mount which is mounted while starting this container. the file it is trying to access is actually the one's from the mounts created during container creation. Highlighted below. Not sure what is difference between checkout action version 1 and version 2 as it may same be the fix for al the actions
/usr/local/bin/docker create --name 9c4e526f4d2341bdbb77374d28b5cb79_busyboxlatest_47dbb4 --label 60e226 --workdir /__w/artifactory-example-pipeline/artifactory-example-pipeline --network github_network_4f7a224d0c30462aa0c518ef5525ad49  -e "HOME=/github/home" -e GITHUB_ACTIONS=true -e CI=true -v "/var/run/docker.sock":"/var/run/docker.sock" -v "/runner/_work":"/__w" -v "/runner/externals":"/__e":ro -v "/runner/_work/_temp":"/__w/_temp" -v "/runner/_work/_actions":"/__w/_actions" -v "/runner/_work/_tool":"/__w/_tool" -v "/runner/_work/_temp/_github_home":"/github/home" -v "/runner/_work/_temp/_github_workflow":"/github/workflow" --entrypoint "tail" busybox:latest "-f" "/dev/null"

@mumoshu I was wrong.. The file with release was expected and when I changed the container to ubuntu it worked. thanks for the help


Decouple justification and finalization processing

More readable and saves a few lines.

I hope someone can figure out another name than previous_previous_justified_epoch. 😆

I guess antepenultimate_justified_epoch is slightly better :)

I'm pretty sure we used to do it in a similar way but this was seen as difficult to analyze because we were changing things around in the state before running the comparisons..


Develop patch for pack

I wish I could develop a patch (expansion) for an existing packs. For example, if I have installed a Jira package and are creating some workflows with Jira actions, I want to export those workflows to a separate package that users can install as a patch for an existing Jira package. ie after installing the patch package, all actions/workflows from it should be under the Jira package, without losing existing actions in the Jira package.
Is there any way to do that?

It sounds like you want to fork the Jira pack and then add your new actions to that forked repo. And then instead of running st2 pack install jira you and your users can run st2 pack install https://github.com/yourusername/stackstorm-jira

Your other option is to write a new pack and set the original jira pack as a dependency in the pack.yaml (https://docs.stackstorm.com/packs.html#pack-dependencies).

@chris3081 I can't put new actions in the Jira pack without losing/spoiling existing actions.


Expand messages in errors thrown in IModelDb.Elements

Changes to errors thrown by insertElement, updateElement and deleteElement in IModelDb:

IModelError is now thrown instead of Error.
message and metaData now contains info relevant to the error.
message format is now more inline with other iModelDb errors.

In general, I think our subclasses of Error are problematic and we should work towards eliminating them rather than propagating them. For one thing, the "hierarchy" of them is confusing and typeof tests are the root of lots of problems. Also, they can't be thrown from native code, which is why I purposely left these of type Error rather than IModelError with the hope of eventually eliminating IModelError entirely.
In particular the errorNumber field of IModelError is not helpful. It is vestige of the C++ world where passing strings is inefficient. It does serve the purpose of providing a key that programmers can use to determine if the exception is expected so they can recover, but uniqueness is vague and problematic. Further, the "message" field is only useful to programmers in debuggers (or potentially in logs) because it can't be localized. Metadata is fine, but can become voluminous in when people just blindly log exceptions. For debugging, there's a calltrace so metadata isn't explicitly necessary for context.
I know you didn't want to open up a whole discussion of exception handling, but I wanted to explain why what you're changing is the way it is. If we had a magic wand and could rewind time, i would suggest we create an ITwinError interface:
export interface ITwinError {
    namespace: string;   // Localization namespace
    errorKey: string; // unique key for error, within namespace
    message: string; // explanation of what went wrong. (Should provide some format for localization, like ITwinLocalization.getLocalizedKeys but the opposite way)
    metadata?: LoggingMetaData;
}

and a set of static functions in an ITwinError namespace for dealing with them. We'd eliminate all of our classes derived from Error.
Or something like that.

@kabentley I agree with you on the subclasses of Error and would like to try and avoid them as much as possible. @GytisCepk can you use Error directly?

The existing code uses Error, this changes it to use IModelError. Certainly we can add metadata without changing the type, but i presume @GytisCepk thought that what was there was inconsistent with other code.

As for introducing a new type Keith, do you see a way for us to migrate to just use Error instead? I'd prefer if possible to not introduce a new version that we'd need to shift everyone to over time.

I think there's probably a way to do it without too much pain, but it would be a breaking change to existing code, so not possible without a major version. I think someone could define the ITwinError interface we want and we could start using it for new code (particularly in new iTS code).

@aruniverse let's get this on the backlog, I think this is worth cleaning up due to the confusion around IModelError and other statuses (which most are really no longer valid after we split out all of the client libraries in 3.0).

@mergifyio backport release/4.5.x


Update status of track

This issue is part of the migration to v3. You can read full details about the various changes here.
There are several new features in Exercism v3 for tracks to build. To selectively enable these features on the Exercism v3 website, each track must keep track of the status of the following features:

Concept Exercises have been built
A test runner has been implemented
A representer has been implemented
An analyzer has been implemented

The status of these features is specified in the top-level "status" field in the track's config.json, as specified in the spec.
Goal
The "status" field in the config.json file should be updated to indicate the status of the features for this track. The list of features is defined in the spec.
Example
{
  "status": {
    "concept_exercises": true,
    "test_runner": true,
    "representer": false,
    "analyzer": false
  }
}

Tracking
https://github.com/exercism/v3-launch/issues/12

@kotp, I think we can close this. We only have a test runner, and that's currently enabled.
From the track config,
  "status": {
    "concept_exercises": false,
    "test_runner": true,
    "representer": false,
    "analyzer": false
  }


Prims Algorithm to calculate MST  in a graph using priority queue.

💥 Proposal
Hi
I am a participant in GSsoc. Priority Queue is a very important data structure that helps in optimizing space and time complexity of algorithms. Prims Algorithms using Priority Queue can be applied to solve MST problems real quick.
Please assign this issue to me.
Have you read the Contributing Guidelines on Pull Requests?
Yes
/assign

/assign

linked #3486


Allow treatment of non-uniform assemblies in the uniform mesh converter

Description
The uniform mesh module was updated to treat the conversion of non-uniform assemblies in the core model (using the nonUniformAssemFlags setting). In this change, a new branch of code is introduced within the UniformMeshConverter that short cuts the entire new reactor creation and entire reactor remeshing/data mapping when the nonUniformAssemFlags is provided by the user. This new feature allows for significant acceleration of the reactor unification because only a subset of all the assemblies need to be converted.

Checklist

[x] This PR has only one purpose or idea.
[x] Tests have been added/updated to verify that the new/changed code works.

[x] The code style follows good practices.
[x] The commit message(s) follow good practices.

[x] The release notes (location doc/release/0.X.rst) are up-to-date with any bug fixes or new features.
[x] The documentation is still up-to-date in the doc folder.
[x] The dependencies are still up-to-date in setup.py.

Thanks @albeanth - I refactored the code changes to just be in the UniformMeshConverter and added a simple test that executes the conversion using the nonUniformAssemFlags on the test reactor for code coverage. We have more in-depth coverage internally though!


Hangs on stop()

Hi!
Sometimes our application hangs on stop()
kazoo (2.6.1)
timeout=1
(gdb) py-bt
Traceback (most recent call first):
  <built-in method acquire of _thread.lock object at remote 0x7fac03095df0>
  File "/usr/lib/python3.6/threading.py", line 1072, in _wait_for_tstate_lock
    elif lock.acquire(block, timeout):
  File "/usr/lib/python3.6/threading.py", line 1056, in join
    self._wait_for_tstate_lock()
  File "/opt/yandex/pgsync/lib/python3.6/site-packages/kazoo/protocol/connection.py", line 193, in stop
    self._connection_routine.join()
  File "/opt/yandex/pgsync/lib/python3.6/site-packages/kazoo/client.py", line 528, in _safe_close
    if not self._connection.stop(timeout):
  File "/opt/yandex/pgsync/lib/python3.6/site-packages/kazoo/client.py", line 635, in stop
    self._safe_close()
  File "/opt/yandex/pgsync/lib/python3.6/site-packages/pgsync/zk.py", line 165, in __del__
    self._zk.stop()

I've also came across this issue, in my case the problem was in race after AUTH_FAILED error, here is a fix - #688
And here is a gist with details - https://gist.github.com/azat/bc7aaea1c32a4f1ea75ad646d26280e9


cmd/search: use new Fedora package search

pkgdb has been put into read-only mode,
so it won't be updated for new Fedora releases
going forward. Use apps.fedoraproject.org/packages instead.
Signed-off-by: Bob W. Hogg<EMAIL_ADDRESS>
[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.
[x] Have you successfully run brew tests with your changes locally?

See https://fedoraproject.org/wiki/Infrastructure/WhatHappenedToPkgdb if you're interested in why it's getting decommissioned.

Thanks again @rwhogg!


It keeps spinning after choosing "receive newsletter"

Describe the bug
It keeps spinning after choosing "receive newsletter"
Steps to reproduce the behavior
1.Navigate to https://arcade.makecode.com/beta#
2.Sign in account----->My Profile
3.Choose "I would like to receive the Makecode newsletter"
Actual behavior
It keeps spinning after choosing "receive newsletter". It can restore if refreshing the page.

Additional context
1.OS: Windows(rs6)
2.arcade version: 1.7.22
3.Microsoft MakeCode version: 7.3.23

@Sheila111 do you see any errors in the dev console, or failed network requests?

@eanders-ms  Maybe it can help you to analyze: arcade.makecode.com-1638324275996.log

Thanks, looks like a problem with state patching. We're going to have to replace that system soon.

@eanders-ms I was looking into this -- what do you think is wrong with the state patching???? is this a normal issue with it?

The whole json patch approach to changing settings is full of pitfalls. We just need to be able to set the value authoritatively, without delicate handling of the whole state blob. I plan to fix this in the new year! Every value in the user preferences blob needs to exist in its own record in the backend. It's fine to represent it as a single data structure in the client, but we have to store it in a destructured format in the backend. That's the long-term fix to this issue. Doesn't help much now though. Do you have a repro?

ah I see okay no I was just looking through the logs / code to see what parts were squeaky and thought I should ask you first :) will try for a repro

repro is:

delete your account
Sign in
Click the sign in button


usage of computeSpillmat

Hi Dr.Robinson!
Thanks for your time in advance. I am writing to inquire about the usage of computeSpillmat(). Now I have multiple fcs files, each one is a single stained control. My questions are:

In the vignette it says "Computes a spillover matrix from priorly identified single-positive populations". are priorly identified single-positive populations equivalent of these single stained samples?
To compute a spillover matrix based on these, do I import all these fcs files into a flowset, then construct a SCE, and then input this sce into computeSpillmat()?
These single stained control only cover a subset of all antibodies used in the panel - how does this affect spillover matrix and the effect of compensation?

Thanks again!

I would say almost, but not entirely. In theory, yes, single-positive population X = single-stained beads stained for X. However, even single-stains may be subject to spillover due to measurement sensitivity (affecting +/-1 mass channels), and one cannot be sure the staining is 100%, so there might be events that are all negative. Thus, we propose a standard debarcoding procedure (assignPrelim() -> estCutoffs() -> applyCutoffs()) to arrive at clean single-stained populations.

Yes, you could read all samples into a flowSet via e.g. read.flowSet(list.files("dir", "\\.fcs$", full.names = TRUE), truncate_max_range = FALSE, transformation = FALSE); then construct the SCE using prepData. This will place all samples in a single object, with unique identifiers in cell metadata column sample_id.

The most accurate answer is "it depends". We have seen that certain interactions tend to give quite notable spillover (>2%), while other do not (<0.1%). You will be given a warning about interactions where no spillover could be estimated. E.g., say you are missing single-stained beads for X100 (metal X, mass 100): The warning will say something like "Compensation might be inaccurate. Couldn't estimate spillover for X100 -> A99, B101 (+/-1); C116 (+16); D80, E120, F125 (isotopes)" - this of course depends on the the panel. Depending on which interactions are covered, the overall compensation should be okay, even when not complete, and in any case better than no compensation at all.


[SUPPORT] Hudi CLI bundle not working

Tips before filing an issue

Have you gone through our FAQs?

Join the mailing list to engage in conversations and get faster support at<EMAIL_ADDRESS>

If you have triaged this as a bug, then file an issue directly.

Describe the problem you faced
When using hudi-cli-with-bundle.sh to start Hudi CLI, many commands would fail immediately due to error below:
24/01/26 00:22:51 INFO InputStreamConsumer: Error: Failed to load org.apache.hudi.cli.commands.SparkMain: org/apache/hudi/common/engine/HoodieEngineContext
24/01/26 00:22:51 INFO InputStreamConsumer: 24/01/26 00:22:51 INFO ShutdownHookManager: Shutdown hook called
24/01/26 00:22:51 INFO InputStreamConsumer: 24/01/26 00:22:51 INFO ShutdownHookManager: Deleting directory /mnt/tmp/spark-5465e2a8-7b9a-4cf1-b46a-afec9f50d860
Failed to clean hoodie dataset

Note the error message is also very limited. It seems the stacktrace has been truncated
To Reproduce
Steps to reproduce the behavior:

Create a Hudi table
Configure Spark/Hadoop/Hudi classpath for CLI and start CLI with hudi-cli-with-bundle.sh
Connect to Hudi table with command connect --path <table_path>
Run cleans run

Expected behavior
I believe there are 2 problems here:

CLI bundle should be working
When CLI fails, the stacktrace/error message shouldn't be truncated for debugging purposes
The second problem is the more concerning one to me now. I'd be happy to dive deeper and debug but currently I can't debug effectively due to limited error message

Environment Description

Hudi version : 0.14.1 (I've tested with both EMR and OSS Hudi 0.14.1)

Spark version : 3.5.0

Hive version : 3.1.3

Hadoop version : 3.3.6

Storage (HDFS/S3/GCS..) : S3

Running on Docker? (yes/no) : no

Additional context
Add any other context about the problem here.
Stacktrace
See above

@CTTY I was trying to reproduce this issue, but got into some other setup issue. Will get back to you soon on this.

test

test

Getting the similar error while running the commit rollback
commit rollback --commit<PHONE_NUMBER>1846380
24/04/08 23:22:02 INFO InputStreamConsumer: Apr 08, 2024 11:22:02 PM org.apache.spark.launcher.Log4jHotPatchOption staticJavaAgentOption
24/04/08 23:22:02 INFO InputStreamConsumer: WARNING: spark.log4jHotPatch.enabled is set to true, but /usr/share/log4j-cve-2021-44228-hotpatch/jdk17/Log4jHotPatchFat.jar does not exist at the configured location
24/04/08 23:22:02 INFO InputStreamConsumer:
24/04/08 23:22:03 INFO InputStreamConsumer: Error: Failed to load org.apache.hudi.cli.commands.SparkMain: org/apache/hudi/common/engine/HoodieEngineContext
24/04/08 23:22:03 INFO InputStreamConsumer: 24/04/08 23:22:03 INFO ShutdownHookManager: Shutdown hook called
24/04/08 23:22:03 INFO InputStreamConsumer: 24/04/08 23:22:03 INFO ShutdownHookManager: Deleting directory /mnt/tmp/spark-272bb6ef-f858-42a6-b9d0-9614f1f36371
24/04/08 23:22:03 INFO HoodieTableMetaClient: Loading HoodieTableMetaClient from s3://mansipp-emr-dev/hudi_cli_migration/tables/mor/mansipp_hudi_mor_table_2/
24/04/08 23:22:03 INFO HoodieTableConfig: Loading table properties from s3://mansipp-emr-dev/hudi_cli_migration/tables/mor/mansipp_hudi_mor_table_2/.hoodie/hoodie.properties
24/04/08 23:22:03 INFO S3NativeFileSystem: Opening 's3://mansipp-emr-dev/hudi_cli_migration/tables/mor/mansipp_hudi_mor_table_2/.hoodie/hoodie.properties' for reading
24/04/08 23:22:03 INFO HoodieTableMetaClient: Finished Loading Table of type MERGE_ON_READ(version=1, baseFileFormat=PARQUET) from s3://mansipp-emr-dev/hudi_cli_migration/tables/mor/mansipp_hudi_mor_table_2/
Commit<PHONE_NUMBER>1846380 failed to roll back```


Checking the the DNS PTR of a IPv6 address

Goss supports the checking of a reverse-DNS record of a IPv4 address fine.
But it fails for a IPv6 address like this (using goss 0.3.6):
dns:
  PTR:2001:4860:4860::8888:
    resolvable: true
    server: <IP_ADDRESS>
    addrs:
    - "google-public-dns-a.google.com."

It looks like the key parser doesn't expect IP addresses with colons:
https://github.com/aelsabbahy/goss/blob/2506b9448a4ec97f92c2c8556efdd52741658899/system/dns.go#L38-L41
Perhaps there also also code parts that need to be changed.

I think I have a fix for this. However, the dnstest.io records I was using seem to be down. Do you know a good public set of DNS records I can add as a CI test for goss?
I need records to replace the following tests + adding a test for the PTR reverse lookup scenario:
https://github.com/aelsabbahy/goss/blob/ad19527be8bc93bcee84a17ee686c4f5745aee85/integration-tests/goss/goss-shared.yaml#L71-L139

In my experience, the Google public DNS servers heavily filter DNS records. Thus, they are quite unreliable for such tests and e.g. DNSBL queries.
More reliable are the Quad9 and OpenDNS servers, e.g.:
$ dig +short @<IP_ADDRESS> dnstest.io caa
0 issuewild ";"
0 issue "comodoca.com"
0 issue "letsencrypt.org"
$ dig +short @<IP_ADDRESS> dnstest.io caa
0 issue "comodoca.com"
0 issue "letsencrypt.org"
0 issuewild ";"

For the reverse-PTR scenario I would use a well known address - e.g. the address of a public DNS server (cf. my original report).
$ dig +short @<IP_ADDRESS>  -x 2001:4860:4860::8888
google-public-dns-a.google.com.
$ dig +short @<IP_ADDRESS>  -x 2001:4860:4860::8888
google-public-dns-a.google.com.

Will take a look at the dnstest.io records / DNS servers. They were "just working:TM:", haven't been on them for s while.


Unknown variable 'default'

Hi!
I am currently trying out your knative example and added the following line to the Background section, because I currently do not have a broker running on my cluster.
Background:     Given Knative event consumer timeout is 20000 ms     Given create Knative broker default     Given Knative broker default is running     Given variable id is "citrus:randomNumber(4)"
I get the following exception on the step:
'[test-knative-eventing-c351hg2cjbf9cuksbe10-snsdn test-1]   And send Knative event                                                                                # org.citrusframework.yaks.knative.SendEventSteps.createEvent(io.cucumber.datatable.DataTable)
[test-knative-eventing-c351hg2cjbf9cuksbe10-snsdn test-1]       com.consol.citrus.exceptions.TestCaseFailedException: Unknown variable 'default'
[test-knative-eventing-c351hg2cjbf9cuksbe10-snsdn test-1]       at com.consol.citrus.DefaultTestCase.executeAction(DefaultTestCase.java:144)
[test-knative-eventing-c351hg2cjbf9cuksbe10-snsdn test-1]       at com.consol.citrus.DefaultTestCaseRunner.run(DefaultTestCaseRunner.java:125)
[test-knative-eventing-c351hg2cjbf9cuksbe10-snsdn test-1]       at org.citrusframework.yaks.knative.SendEventSteps.sendEventRequest(SendEventSteps.java:149)
[test-knative-eventing-c351hg2cjbf9cuksbe10-snsdn test-1]       at org.citrusframework.yaks.knative.SendEventSteps.createEvent(SendEventSteps.java:121)
[test-knative-eventing-c351hg2cjbf9cuksbe10-snsdn test-1]       at ✽.send Knative event(classpath:org/citrusframework/yaks/knative-eventing.feature:15)
[test-knative-eventing-c351hg2cjbf9cuksbe10-snsdn test-1] Caused by: com.consol.citrus.exceptions.CitrusRuntimeException: Unknown variable 'default''
The name of the variable "default" is the name of the namespace I run the test in.
Is this a bug or an application error from me?

I think the error is in another step in the feature file - probably in step "And send Knative event"
Please have a look on something like ${default}. Is there anything like that in your in your feature file?

Here is the whole code of the feature file
Feature: Knative eventing
Background:
Given Knative event consumer timeout is 20000 ms
Given create Knative broker default
Given Knative broker default is running
Given variable id is "citrus:randomNumber(4)"
Given Knative namespace default
Scenario: Service trigger
Given create Knative event consumer service hello-service
Given create Knative trigger hello-service-trigger on service hello-service with filter on attributes
| type   | service-greeting |
| source | https://github.com/citrusframework/yaks |
When Knative event data: {"msg": "Hello Knative!"}
And send Knative event
| type            | service-greeting |
| source          | https://github.com/citrusframework/yaks |
| subject         | hello service |
| id              | say-hello-${id} |
Then expect Knative event data: {"msg": "Hello Knative!"}
And verify Knative event
| type            | service-greeting |
| source          | https://github.com/citrusframework/yaks |
| subject         | hello service |
| id              | say-hello-${id} |
Scenario: Channel subscription
Given create Knative channel hello-channel
Given create Knative event consumer service hello-service
Given subscribe service hello-service to Knative channel hello-channel
Given create Knative trigger hello-channel-trigger on channel hello-channel with filter on attributes
| type   | channel-greeting |
| source | https://github.com/citrusframework/yaks |
When Knative event data: {"msg": "Hello Knative!"}
And send Knative event
| type            | channel-greeting |
| source          | https://github.com/citrusframework/yaks |
| subject         | hello channel |
| id              | say-hello-${id} |
Then expect Knative event data: {"msg": "Hello Knative!"}
And verify Knative event
| type            | channel-greeting |
| source          | https://github.com/citrusframework/yaks |
| subject         | hello channel |
| id              | say-hello-${id} |
I ran the code from a new machine and I still get the same error.

I probably have found the issue. It is the way the broker Url is constructed when using plain Kubernetes in https://github.com/citrusframework/yaks/blob/main/java/steps/yaks-knative/src/main/java/org/citrusframework/yaks/knative/KnativeSettings.java#L146
The namespace is added as variable syntax with ${%s} which leads to the error.
Can you please try to explicitly set the YAKS_KNATIVE_BROKER_URL env setting in yaks-config.yaml to something like http://broker-ingress.knative-eventing.svc.cluster.local/default/default


0.7.7 breaks lookup field functionality

Starting with 0.7.7, when using a lookup field type only the "List" output types are working, in all other cases "--auto--" is displayed. It seems that the newly introduced function doesn't account for rawValues which aren't an array for example when using one of the summarisation functions.

could you paste the definition of your lookup field ?
(located in the frontmatter of the fileclass file, under fields)

I’m AfK at the moment but I’m pretty sure the summarisation isn’t working at all no matter the input (for example count of results in lookup). Only the list of files output is working in the latest version. If you cannot replicate the issue I’ll post an example in a few days.

Hi Mathieu,
I've setup a test vault with 2 classes, Project and Task. Task has one boolean field "Done" and a file field in which you can select the project. In de Project class I've create 2 lookup fields with the following definition:
  - name: Tasks
    type: Lookup
    options:
      autoUpdate: false
      outputType: LinksList
      builtinSummarizingFunction: Count
      customListFunction: page.file.name
      customSummarizingFunction: return pages.length
      targetFieldName: Project
      dvQueryString: dv.pages().where(p => p.fileClass == "Task")
    path: ""
    id: 2nAJnd
  - name: TasksDone
    type: Lookup
    options:
      autoUpdate: false
      outputType: BuiltinSummarizing
      builtinSummarizingFunction: Count
      customListFunction: page.file.name
      customSummarizingFunction: return pages.length
      dvQueryString: dv.pages().where(p => p.fileClass == "Task")
      targetFieldName: Project
      summarizedFieldName: Done

The "Tasks" lookup shows the links to the tasks which reference the project.
The "TasksDone" lookup shows "--auto--" or Empty in the frontmatter.
In version 0.7.6 the "TasksDone" lookup shows the count of done tasks.

To add to this.
Lookup fields with a built-in or custom summary function show up as follows

Frontmatter: null
Note Field Modal: "--auto--"
Class Table View: as expected.

Sure, unfortunately the issue is still there. I did some debugging and the issue seem to be with the new renderMultiFilesFields in note.ts. This was introduced in 0.7.7 to render, among others, the Lookup field type. The regex only matches "array" like strings but the result of a summarisation is not array formatted.
https://github.com/mdelobelle/metadatamenu/blob/8378f179a8f617fe2f3af927a2bdd4986ed5cf3a/src/note/note.ts#L70

@renekalff  can you test the last beta release? https://github.com/mdelobelle/metadatamenu/releases/tag/0.8.0-beta-5 ?

Yes! That seems to fix the issue.


Antibody details pages shows list of target species (under target antigen) without commas

example: mouserathumancatcow
for AB_3064655

this is what I see here


Custom achievement for winner of tournament

And for other finalist
E.g.
"Winner of Shoot One Out For Dave tournament"

This could be interesting
gib

Was kinda inactive but we're making some progress here -


terraform-providers: bump versions and add selvpc

Motivation for this change
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Assured whether relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

@stephengroat could you rebase this and solve the conflict?


Keep extra pokemon in our bag so we can do smarter things later

Short Description:
Don't release pokemon unless we have limited space based on an optional config. Allows us to do smarter things later, like keep enough to evolve in batch with an egg.

Looks like some bad commits got merged in here

bleh - sorry - bad pull - will fix

This looks great. Just curious on @douglascamata's thoughts on the event

Thanks!

LGTM.  It's the same pattern as with the items.
However, I find them both a little chatty... perhaps we can turn down the frequency of the messages?

As we talked in Slack, the message should only be displayed when at least ONE is recycled by the task.

@douglascamata @knobunc @TheSavior Thanks for the feedback - removed the spammy messages as discussed.

I think you should separate between min_empty_space for bag storage and Pokemon storage. Also, the min_empty_space is defined under config of RecycleItem.

👍

Feedback from @XtrmJosh and @douglascamata incorporated!

@thebigjc I'll take a look tomorrow's morning. Too late for me, sorry.

No worries. Shouldn't take more than a minute.
On Wed, Aug 10, 2016, 8:05 PM Douglas Camata<EMAIL_ADDRESS>wrote:

@thebigjc https://github.com/thebigjc I'll take a look tomorrow's
morning. Too late for me, sorry.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/PokemonGoF/PokemonGo-Bot/pull/3317#issuecomment-239041501,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAS_LW7xq8q2cLTt4HPQnMECUBtTOrQyks5qemc4gaJpZM4JgSJV
.

@thebigjc solve merge conflicts please, this LGTM already!

@douglascamata done! Ready for you to merge!

@TheSavior Addressed your two points

@thebigjc Why did you close this? Do we not need this anymore?

@TheSavior Mostly frustration. I had a 4 line code change doing something exactly the same way as running code that turned into a 25 comment back and forth refactoring code I hadn't planned on touching, and the delays on the back-and-forths resulted in many merge conflicts as much more complex changes were coming through. There are much more interesting features to work on than something this simple and stacking all these changes into this PR isn't how I would like to spend my limited time.


Basis.toAxisAngle return NaN as angle

Godot version
4.0.dev #b3df275
System information
MacOS 11.6
Issue description
When the rotation angle is very small, the angle returned is NaN.
Steps to reproduce
In c++:
Basis bugNan(1.00000024, 0 , 0.000100001693, 0, 1, 0, -0.000100009143, 0, 1.00000024);
bugNan.get_axis_angle(axis, angle);
print_line(angle) // NaN

Minimal reproduction project
No response

@TokageItLab did the quaternion verseion of this.

Yeah I recall that I changed it to return an initial Quaternion Quaternion(0, 0, 0, 1) when AxisAngle is very small.

I found the issue in Basis, I will open a PR. The  arcos() function receive a value greater than one, so it returns NaN,  I clamped the value to avoid the issue. I was wondering if we could put a debug code to find this kind of problem for arcos/arcsin.


fix: Added spinner as loading state for user authentication

Related to #1809
Added the Spinner icon to indicate to user that the wallet is loading while finishing user authentication.
This was added as a temporary fix; in the future, the loading state should be the skeleton loaders for the corresponding page.
Signed-off-by: heidihan0000<EMAIL_ADDRESS>https://user-images.githubusercontent.com/44453261/180890467-3c834808-9927-44da-8038-708ed41b7a58.mov

Recordings:
Sign up + signout:
https://user-images.githubusercontent.com/44453261/181064473-f8d23da8-ac12-4d55-8296-02fd9d7d37e6.mov
Sign in + sign out:
https://user-images.githubusercontent.com/44453261/181064557-d90dff4f-fbcc-428f-a77d-916586dd5701.mov
Refresh:
https://user-images.githubusercontent.com/44453261/181064618-559adb51-9e51-41c1-a392-e23fdfee610a.mov
Open from new tab:
https://user-images.githubusercontent.com/44453261/181064657-4ee73e72-e6a5-42f8-8cf8-f33bbade1ef3.mov
From OIDC issuance:
https://user-images.githubusercontent.com/44453261/181065166-6a6fbe05-11a3-49a8-be8d-f9c70a8598ae.mov


Children of Ur

Should be listed as a clone/remake of Glitch.
The repository linked is archived, and the current repository is on gitlab.

Thank you for the update. https://gitlab.com/ChildrenOfUr seems to be a collection of about 30 different git repositories. I guess not all of them are needed to run Children of Ur (server, browser client). Do you maybe know which of these are used for the current running version of the game at https://game.childrenofur.com/ ?

This should be the server repository and this should be the client repository.
There are several other repos you'd probably need if you actually wanted to try running your own server, like cou_login and authServer for example.

Thank you for all the information. I modified the entry. The changes will be pushed to Github at the next possibility.


Cycle detection

A file like this results in a recursive cycle when resolving the item's value:
<xigt-corpus>
    <igt>
        <tier type="words" id="a" segmentation="a">
            <item id="a1" segmentation="a1"/>
        </tier>
    </igt>
</xigt-corpus>

Currently only query.descendants() has cycle detection. Make sure the other alignment expression resolution functions do, too.

query.ancestors() definitely needs cycle detection; it will loop forever on e.g. resolving children in phrase structure tiers.

@curtosis, thanks for the comment, and sorry for my late response. Did you come across this problem in real data? If so, can you share a problematic example instance?


Build a more organized outline for docs

The current docs organization was hastily pulled together from what was available in the repo at the time, plus minor updates to content.
To aid discoverability and reduce repetition, I'd like to re-organize the docs files. We can start by discussing here and developing an outline, and then start implementing.

This should be treated as a story with a set of related issues for the various underlying efforts.

Agreed! The purpose of this issue was more for discussion about the outline as a whole, before breaking it up into smaller tasks and tying them to related code/design/etc. efforts. It's more about the organization than as a starting point for the actual writing.
However, since there's been no discussion, I guess I'll just start breaking it up.

I've broken out the major implementation sections into separate issues. PRs for each of these should include links added to the appropriate section of the Quick Start, because at the moment, it's our main intro. When all of these sections are ready, we can create the Implementation Intro section of the outline, and adapt the Quick Start/Test Drive content to match that outline.
Here's a handy list of the issues to complete for this first round:

[ ] Backends & Authentication (high priority) #600
[ ] Widgets #619
[ ] Collections #679
[ ] Configuration #685
[ ] Installation #731


generate the packages with correct dependencies

I made a similar script which generates nuget nuspec and packages with correct dependencies:
https://gist.github.com/smoothdeveloper/994522269a0a04c275c9
In this repository it is mentioned:

The nuspec files are currently being generated by a quick-and-dirty C# app that I wrote, which is not ready to be shared with the world :)

I think the fsharp script in my gist could replace that C# app which is not published, so I just wanted to share it for other users that might want to use it in case this repository doesn't get updated with future release or if they want to use it with older releases.

I continued smoothdeveloper's works : https://github.com/fpellet/convertToNuGet
I added a script to facilitate run and added external nuget support (EntityFramework)


Fixed caching issue in UMDFastBindingObject::FindOrCreateExtendableItemName

FName::IsValid() is generally intended for validating whether memory corruption occurred in an FName, and a default-initialized FName satisfies this check. As a result, every call to UMDFastBindingObject::FindOrCreateExtendableItemName added the value "None" to the map.
Switching this to Result.IsNone() resolved the issue.

I discovered I was using FName::IsValid() incorrectly in another spot the other day and had the thought "oh god, in how many places have I used that?"
Nice find, thanks for the fix


Previous implementation segfaulted with ruby 1.9.2-p290.

This implementation should also be slightly more efficient as there is no lexical conversion to and from strings.

Thank you!


Update dir.md

Hey there! Great question bonuses are essential for new players because they provide a solid starting point, helping to boost their bankroll without major risks upfront. For example, with the 1win casino bonus , new players in Malaysia can kick off their journey with a massive 500% bonus, reaching up to 15,200 RM. This offer is fantastic because it not only adds extra funds for exploring the platform but also gives players a real chance to understand the games without immediately putting a lot on the line. Plus, 1Win offers diverse promotions like deposit bonuses and an Express bonus for sports betting, adding variety to keep things exciting.


update conda-forge install procedure

What does this implement/fix? Explain your changes.
people were complaining on a mailing list about the current way to install rdkit

superseded by https://github.com/rdkit/rdkit/pull/3593


⚠ Bofrost.es has degraded performance

In 04f80e3, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1411 ms

Resolved: Bofrost.es performance has improved in 3d356c9.


Add RISCV to standard set of architectures for incremental buildbots

I think this will unbreak the incremental buildbots

@swift-ci please smoke test

@swift-ci please smoke test

You could also remove these two lines and always just build the default set of architectures.

You could also remove these two lines and always just build the default set of architectures.

You're right, we should probably just do that instead. We're not likely to save ourselves much build time by limiting the architectures, but we will cause ourselves surprises like this.


[BUG] ZHA aquara pressure sensor is not updating

Describe the bug
I'm seeing update messages in the debug logs, but in the pressure is not updating in the ui
Expected behavior
measurements in the UI should match values in the logs.
Screenshots

.
Additional context
{
  "node_descriptor": "NodeDescriptor(byte1=2, byte2=64, mac_capability_flags=128, manufacturer_code=4151, maximum_buffer_size=127, maximum_incoming_transfer_size=100, server_mask=0, maximum_outgoing_transfer_size=100, descriptor_capability_field=0)",
  "endpoints": {
    "1": {
      "profile_id": 260,
      "device_type": "0x0302",
      "in_clusters": [
        "0x0000",
        "0x0001",
        "0x0003",
        "0x0402",
        "0x0403",
        "0x0405",
        "0xffff"
      ],
      "out_clusters": [
        "0x0000",
        "0x0004",
        "0xffff"
      ]
    }
  },
  "manufacturer": "LUMI",
  "model": "lumi.weather",
  "class": "zhaquirks.xiaomi.aqara.weather.Weather2"
}

2021-01-31 21:27:36 DEBUG (MainThread) [zigpy.zcl] [0x0006:1:0x0403] ZCL deserialize: <ZCLHeader frame_control=<FrameControl frame_type=GLOBAL_COMMAND manufacturer_specific=False is_reply=False disable_default_response=True> manufacturer=None tsn=143 command_id=Command.Report_Attributes>
2021-01-31 21:27:36 DEBUG (MainThread) [zigpy.zcl] [0x0006:1:0x0403] ZCL request 0x000a: [[Attribute(attrid=0, value=<TypeValue type=int16s, value=136>), Attribute(attrid=20, value=<TypeValue type=int8s, value=-1>), Attribute(attrid=16, value=<TypeValue type=int16s, value=1360>)]]
2021-01-31 21:27:36 DEBUG (MainThread) [zigpy.zcl] [0x0006:1:0x0403] Attribute report received: measured_value=136, 20=-1, 16=1360

ah, after a bit of digging it appears values outside of the documented range are intentionally ignored  see #296. Given that the sensor appears to be generating useful data < 300hPa, and that the original issue the invalid data was -1, I think expanding the lower bound of acceptable values to 0 makes sense

What are you doing with that sensor?

I got some vacuum storage bags to keep my 3d printing filament dry, and I was curious just how strong a vacuum you could actually pull with the plastic hand pump.

@dmulcahey I guess in https://github.com/zigpy/zha-device-handlers/pull/296 the concern was the reporting of -1 values. I guess accepting the pressure reports bellow 30hPa should be fine, even though it is outside of the manufacturer specs?


deploy a public itsyou.online service on better locations & equipmen

redundant 3 locations
secure mongodb (on encrypted fs or other way?)
needs to come on our DNS infrastructure

And deploy a staging.itsyou.online


Allow Avatar Dynamics to control face expressions

As showcased in the official Avatar Dynamics demonstration video ( https://twitter.com/VRChat/status/1471953215382069254 at 0:19 ), face expressions could be triggered by Avatar Dynamics in some capacity.
Allow Avatar Dynamics to control the face expressions of the avatar.

Done


API: added OpenAPI document 2nd PR

Moved stalled PR https://github.com/tiiuae/vmd/pull/24 from a fork into a branch inside the repository. This was done so more team members could make commits to the PR.
Open items from previous PR

[x] https://github.com/tiiuae/vmd/pull/24#discussion_r1142197766
[x] https://github.com/tiiuae/vmd/pull/24#discussion_r1142179683
[x] https://github.com/tiiuae/vmd/pull/24#discussion_r1142205650
[x] https://github.com/tiiuae/vmd/pull/24#discussion_r1142210296
[x] https://github.com/tiiuae/vmd/pull/24#discussion_r1142212084

@baz2142 's commit before @juliuskoskela 's commits can't be signed anymore without rewriting the history. I'll merge this now bypassing branch protections.


Was able to trigger hundreds of emails

Hey, so I wanted to open this task because in messing with the api I accidentally triggered hundreds of emails to myself, and b/c you're sending them directly from @zulip.com I don't know if this is the sort of thing you want to prevent, in order to avoid domain reputation issues (like, gmail starting to send emails from zulip to spam.)
Basically I accidentally called init from zulip-js in a react loop, so it got called hundreds of times before the api rate limit kicked in. That part is well and good, I think, but because I was using username/password (or maybe this also would have happened with api key), each of those init calls triggered a "New login from Chrome on macOS" email. They're slowly filtering into my gmail account in batches of 20-30 at a time.
Some possible thoughts:
1/ Should that email should have been sent so frequently?
2/ Should be a circuit breaker on email sends
3/ Should automatic mail from zulip be sent from something like a zulipmail.com domain?
4/ Or maybe this isn't that big of a deal

@meitros do you know what API endpoint you were using?  I would not except normal API usage to ever generate that notice.

Closing due to lack of reply and no known mechanism through which the API can generate those "new login" emails without forking Zulip.


Update dependencies

Could you actually bump to 1.0.4 if you have a chance?
Added another small fix :D


Upload image from Browse [Drag&Drop] display image as file link

Jodit Version:  3.3.13
Browser:
OS:  Linux
Code
when try to upload image from Drag & drop button  with my custom upload URL , it display image as link [ anchor tag ] , not img src tag ,

![image](https://user-images.githubusercontent.com/11550708/71622922-c589cd80-2be1-11ea-8421-1d12641382c5.png)

Example :
-  this url of my image [ https://drive.google.com/uc?export=view&id=1C2kClzCxngAMLy_6Jw3v9FSjhOY0GbnZ ]
- i uploaded my image from my local device and return URL of uploaded image  [Browse Button]
- jodit editor upload my image as anchor tag not img tag

Example of my configration

 uploader: {
        url: 'https://mz-backend.herokuapp.com/builder/api/storage/upload/multiple',
        // url: 'https://mz-backend.herokuapp.com/builder/api/storage/local/uploadMultipleFiles',
        // url: 'https://xdsoft.net/jodit/connector/index.php?action=fileUpload',
        // format: 'json',
        filesVariableName: function(e){return "files"},

        insertImageAsBase64URI: false,
        imagesExtensions: [
            "jpg",
            "png",
            "jpeg",
            "gif"
          ],
        withCredentials: true,
        headers: {
           "Authorization": 'Bearer eyJ.l3Q'
        },

        prepareData: function (data) {
            console.log(data);
            data.append('id', 24);
            return data;
        },
        isSuccess: function (resp) {
            console.log('0>>>'+JSON.stringify(resp[0]));
            return resp;
        },
        process: function (resp) {
            console.log('s>>>'+JSON.stringify(resp[0]));
            return {
                files: [''],
                baseurl: resp[0].fileDownloadUri,
                error: resp[0].fileType,
                msg: resp[0].size
            };
        },

    },

}

so what's needed to display image in editor  ?

Expected behavior:
Actual behavior:

Hi,

isSuccess - should return Boolean
process

process: function (resp) {
            return {
                files: ['file.txt', 'example.png'],
                isImages: [false, true]
                baseurl: resp[0].fileDownloadUri,
                error: resp[0].fileType,
                msg: resp[0].size
            };
        },

by default isImages - [false, false]


patch/dependabot

Create dependabot.yml

Codecov Report

Merging #33 (245600c) into master (416dc6c) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##            master       #33   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            4         4
  Lines          157       157
=========================================
  Hits           157       157

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 416dc6c...245600c. Read the comment docs.


[Fix] ThemeTabBarAppearancePicker Not Found

Added ThemeTabBarAppearancePicker.swift to project files to address class not found error

@wxxsw, can you add "@objc" modifier at UINavigationBarAppearance extension?

@wxxsw, can you add "@objc" modifier at UINavigationBarAppearance extension?

done


[RFC] Changes to connections spec and implementation

This will be a long one, please bear with me 😅 .
All ideas here are mostly relevant to pagination, and thus only the connections part of the Relay spec.
After much thought, going over #41, #58, #91, connection.js & the connection spec, and implementing the spec's algorithms for RethinkDB. I've come to a couple of ideas that I would love to hear some comments on (both from the community and the spec and GraphQL.js implementors).
If the ideas expressed here are of interest, I'd be honored to submit a PR.
Let's start with the simple ones:
Spec:

The spec doesn't require that the cursor field be non-null for the edge type. Should every node have a cursor? It would make sense that if a node exists then there is a unique opaque identifier that can serve as a cursor. Which brings me to the next thought...
In #41 @olegilyenko brought up the idea of nodeType being always nullable in the implementation. Would it make more sense for the node field in edges to be non-null?
In the same vein as the 2 previous thoughts, would it make more sense that the edges field of a connection be a non-null list of non-null edges (currently it is a list of edges)? pageInfo is required and its fields hasNextPage and hasPreviousPage are required as well but these lose all meaning if the edges field can be null.
Finally (regarding the spec), I propose a few changes to the pagination algorithms in the spec to support bidirectional pagination as discussed in #58. The algorithm is described at the end of this post.

Implementation:

Implement any or all of the changes mentioned above.
Currently first and last are validated in arrayconnection.js (i.e., in the implementation of the paging algorithm). Would it make more sense to have this validation happen at the schema level (what I think the spec intends) by implementing an UnsignedInt scalar and using that as arguments in forwardConnectionArgs, backwardsConnectionArgs and connectionArgs?
Would it be useful to implement a function that validates a schema by making sure that the cursor type used to query connections is the same as the cursor type that the connection's edges has?
The spec notes that a cursor can be any scalar that serializes to a string. Currently, this implementation forces cursors to be a string. Expanding on #91, would it make sense to add a cursorType parameter to connectionDefinitions that would then use the given cursor type instead of a GraphQLString? forwardConnectionArgs, backwardsConnectionArgs and connectionArgs could then be returned from connectionDefinitions with the appropriate cursor type (removing the need of the previous thought of adding a schema validator... as long as the developer does use the returned objects).

And that's it! Again, I will most likely be implementing most of these for our backend so I wouldn't mind at all to submit a PR. Also, I do understand that these might not be useful to others but I thought they could be so I wanted to hear people's thoughts.
Thanks for reading this huge wall of text. Please comment, criticize, and ask away! 🍺
Pagination Algorithm
... finally, here's the updated pagination algorithm. It should prove trivial to implement with any database as long as there is a way to get the count of records (I successfully implemented it in RethinkDB and can post that source code here if people want to see it). This would solve #58.
Arguments: allEdges, after, before, first, last

Initialize edges to be allEdges.
Let count be the number of elements in edges.
Let afterIndex be the index of the edge in edges whose cursor is equal to the after argument or -1 if not found.
If afterIndex is not -1:

Remove all elements of edges before and including afterIndex.

Let beforeIndex be the index of the edge in edges whose cursor is equal to the before argument or -1 if not found.
If before is set:

Remove all elements of edges after and including beforeIndex.

Let beforeCount be the number of elements in edges.
If first is set:

If first is less than 0: (this check wouldn't be necessary if we ensure first is non-negative)

Throw an error.

If edges has length greater than than first:

Slice edges to be of length first by removing edges from the end of edges.

Let actualFirst be the number of elements in edges.
If last is set:

If last is less than 0: (this check wouldn't be necessary if we ensure first is non-negative)

Throw an error.

If edges has length greater than than last:

Slice edges to be of length last by removing edges from the start of edges.

Let actualLast be the number of elements in edges.
If afterIndex is not -1:

Let hasPreviousPage be true.

If afterIndex is -1:

If beforeIndex is 0:
Let hasPreviousPage be false.
If beforeIndex is not 0:

If actualFirst is greater than actualLast:
Let hasPreviousPage be true.

If actualFirst is less than or equal to actualLast:

Let hasPreviousPage be false.

If afterIndex is equal to count - 1:

Let hasNextPage be false.

If afterIndex is not equal to count - 1.

If beforeIndex is not -1:

Let hasNextPage be true.

If beforeIndex is -1:

If actualFirst is less than beforeCount:
Let hasNextPage be true.

If actual first is greater than or equal to beforeCount:

Let hasNextPage to be false.

Returns: edges, hasPreviousPage, and hasNextPage.
There might be a more succinct way to write the algorithm but I'm 100% sure this works and I used the one from the spec as a baseline.

Any update on this?

Regarding the non-nullability suggestions, that would mean that any error resolving any node within an edge in a connection would always propagate to invalidate the entire connection, and that there would be no flexibility on the implementing side to relax that behaviour while still conforming.
As far as I know, right now nothing prevents a schema from asserting non-nullability for those fields on a particular edge type, if it wants or needs to. But to enforce that at the spec level for all edge types seems particularly restrictive in a very brittle way.

@erydo, that's a very good point! I do agree that having the errors invalidate the entire connection is undesirable. Perhaps the non-nullability suggestions aren't very good. 😅


GUI

Please add a app/GUI
Please create a telegram so ppl can discuss.
Thanks

gui is not planned
telegram group is https://t.me/rv_magisk


[#34] Add info field

#34
Here's what I came up with. Would appreciate any pointers to code/tests

[x] Add Info struct
[x]  Add Contact struct
[x]  Add  License struct
[x]  Fix make test build and test failures

Thanks for the PR! I've addressed the required changes in the issue.

Hi @wafflespeanut am running into some more issues with the borrow,  :D  Need some help yet again :)
I am actually confused about these,
https://github.com/wafflespeanut/paperclip/blob/4bb46bd853a2a01e9882a0da3e03ad5c6cb84db2/src/v2/codegen/state.rs#L428
https://github.com/wafflespeanut/paperclip/blob/4bb46bd853a2a01e9882a0da3e03ad5c6cb84db2/src/v2/codegen/state.rs#L468
and
argo clippy --all -- -D clippy::all
    Checking paperclip v0.3.0 (/Users/manoj/OSS/rust/paperclip)
error[E0609]: no field `name` on type `std::cell::Ref<'_, std::option::Option<v2::codegen::CrateMeta>>`
   --> src/v2/codegen/state.rs:335:32
    |
335 |                     name: meta.name.as_ref().unwrap(),
    |                                ^^^^ unknown field

error[E0609]: no field `version` on type `std::cell::Ref<'_, std::option::Option<v2::codegen::CrateMeta>>`
   --> src/v2/codegen/state.rs:336:52
    |
336 |                     version: &format!("{:?}", meta.version.as_ref().unwrap()),
    |                                                    ^^^^^^^ unknown field

error[E0609]: no field `is_cli` on type `std::cell::Ref<'_, std::option::Option<v2::codegen::CrateMeta>>`
   --> src/v2/codegen/state.rs:365:33
    |
365 |             .map(|m| m.borrow().is_cli)
    |                                 ^^^^^^ unknown field

So, the changes depend on the types. Previously it was Option<Rc<RefCell<CrateMeta>>>, but now it's Rc<RefCell<Option<CrateMeta>>>. So, infer_crate_meta function's return type now changes to the new type. And currently, we do...
// deal with option first followed by refcell borrow
if let Some(foo) = /* crate meta */ {
    let meta = m.borrow(); // or borrow_mut();
    ...
}

But now, this will become:
let borrow = /* refcell borrow first */;
// then go for option deref
if let Some(m) = borrow {
    ...
}

Does this make sense?

So, the changes depend on the types. Previously it was Option<Rc<RefCell<CrateMeta>>>, but now it's Rc<RefCell<Option<CrateMeta>>>. So, infer_crate_meta function's return type now changes to the new type. And currently, we do...
// deal with option first followed by refcell borrow
if let Some(foo) = /* crate meta */ {
    let meta = m.borrow(); // or borrow_mut();
    ...
}

But now, this will become:
let borrow = /* refcell borrow first */;
// then go for option deref
if let Some(m) = borrow {
    ...
}

Does this make sense?

@wafflespeanut so this means the function's return type would NOT be a Result ? 🤔

So I attempted again, and now ending up with 👇  - @wafflespeanut
error[E0594]: cannot assign to `self.crate_meta` which is behind a `&` reference
   --> src/v2/codegen/state.rs:377:9
    |
376 |     pub fn set_meta(&self, meta: CrateMeta) {
    |                     ----- help: consider changing this to be a mutable reference: `&mut self`
377 |         self.crate_meta = Rc::new(RefCell::new(Some(meta)));
    |         ^^^^^^^^^^^^^^^ `self` is a `&` reference, so the data it refers to cannot be written

error[E0594]: cannot assign to `self.crate_meta` which is behind a `&` reference
   --> src/v2/codegen/state.rs:377:9
    |
376 |     pub fn set_meta(&self, meta: CrateMeta) {
    |                     ----- help: consider changing this to be a mutable reference: `&mut self`
377 |         self.crate_meta = Rc::new(RefCell::new(Some(meta)));
    |         ^^^^^^^^^^^^^^^ `self` is a `&` reference, so the data it refers to cannot be written

error[E0596]: cannot borrow `*m` as mutable, as it is behind a `&` reference
   --> src/v2/codegen/state.rs:437:24
    |
436 |         if let Some(m) = cm.as_ref() {
    |                     - help: consider changing this to be a mutable reference: `&mut v2::codegen::CrateMeta`
437 |             let meta = &mut *m;
    |                        ^^^^^^^ `m` is a `&` reference, so the data it refers to cannot be borrowed as mutable

error[E0596]: cannot borrow `*m` as mutable, as it is behind a `&` reference
   --> src/v2/codegen/state.rs:437:24
    |
436 |         if let Some(m) = cm.as_ref() {
    |                     - help: consider changing this to be a mutable reference: `&mut v2::codegen::CrateMeta`
437 |             let meta = &mut *m;
    |                        ^^^^^^^ `m` is a `&` reference, so the data it refers to cannot be borrowed as mutable

@wafflespeanut not sure whats wrong, but am getting different test failures than on the ci 🤔

@hindenbug Please post the errors? If it's about mismatching JSON, then I'm guessing it's because of UUID, in which case you can delete Cargo.lock (in root) and try it again.

@wafflespeanut Thanks, removing Cargo.lock helps.

getting this strange error, what could I be doing wrong here 🤔
---- test_root_mod stdout ----
thread 'test_root_mod' panicked at 'missing file: Os { code: 2, kind: NotFound, message: "No such file or directory" }', src/libcore/result.rs:1165:5
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace.

failures:
    test_root_mod

test result: FAILED. 17 passed; 1 failed; 0 ignored; 0 measured; 0 filtered out

error: test failed, to rerun pass '-p paperclip --test test_k8s'
The command "cargo test --all --all-features" exited with 101.
$ cd tests/test_k8s && cargo check
error: failed to parse manifest at `/home/travis/build/wafflespeanut/paperclip/tests/test_k8s/Cargo.toml`

Caused by:
  Error parsing major identifier for key `package.version`
The command "cd tests/test_k8s && cargo check" exited with 101.

Okay, looks like that's going beyond the scope of this PR, for which I may have to do a workaround for now. I'll take care of this. Thank you for all your hard work! :smile:

Thanks @wafflespeanut for your patience and guidance :smiley:


8 byte alignment in image_sizing

I believe this should fix #50 .
@drbitboy let me know if you think there are side effects or if rounding up to 8 should happen in other sections as well.

Nice.  This is more or less what I was thinking, and it should do the trick.
Let me ponder some more tomorrow.

Not gonna lie, I found this on stackoverflow and I was happy about it enough :D

github copilot suggestion:
// macro to align data to 64-bit boundary
#define ALIGN2(x) (((x) + 7) & ~7)


Fix bug where job deploys with count 0 hang.

Jobs with count 0 do not produce deployments and therefore when
performing a deployment with a count of zero Levant would hang
attempting to track a deployment which would never occur. This
introduces a checker to see whether the job has any taskgroups
with a count greater than zero.
Closes #243

@mdcollins05 sorry for the delay but this should fix the issue you raised. I'll get this merged and released tomorrow.

Awesome! Thanks


created github pages directory

added a site directory with documentation of the Message Broker.
also create the relevant GitHub Actions to deploy it and keep it up to date with dependabot

It looks like the site build is failing due to a missing /site/package-lock.json. If you run the build locally and commit the resulting package-lock.json it should resolve this issue.


Not working in Chrome 87 on MacOS 10.14.6

I'm no longer getting channel points redeemed automatically.

Also not working in Vivaldi 3.5.2115.81 on Windows 10.

Google Chrome 87.0.4280.88, Windows 10  (19041.685)
Same problem

Firefox 84.0 on Ubuntu, same issue.

I made patch https://github.com/trmcnvn/twitch-channel-points/pull/16


IBUS-WARNING

On Ubuntu 16.04 after 'npm run dev':
(electron:7538): IBUS-WARNING **: Unable to connect to ibus: Could not connect: Connection refused (node:7504) DeprecationWarning: Chunk.modules is deprecated. Use Chunk.getNumberOfModules/mapModules/forEachModule/containsModule instead.     at /home/kurisu/zap-desktop/node_modules/extract-text-webpack-plugin/index.js:271:24     at /home/kurisu/zap-desktop/node_modules/async/dist/async.js:3060:16     at eachOfArrayLike (/home/kurisu/zap-desktop/node_modules/async/dist/async.js:1003:9)     at eachOf (/home/kurisu/zap-desktop/node_modules/async/dist/async.js:1051:5)     at Object.eachLimit (/home/kurisu/zap-desktop/node_modules/async/dist/async.js:3122:5)     at ExtractTextPlugin.<anonymous> (/home/kurisu/zap-desktop/node_modules/extract-text-webpack-plugin/index.js:268:10)     at Compilation.applyPluginsAsyncSeries (/home/kurisu/zap-desktop/node_modules/tapable/lib/Tapable.js:142:13)     at Compilation.seal (/home/kurisu/zap-desktop/node_modules/webpack/lib/Compilation.js:580:8)     at /home/kurisu/zap-desktop/node_modules/webpack/lib/Compiler.js:510:16     at /home/kurisu/zap-desktop/node_modules/tapable/lib/Tapable.js:225:11 balance error:  { Error: expected 1 macaroon, got 0     at /home/kurisu/zap-desktop/node_modules/grpc/src/node/src/client.js:554:15 code: 2, metadata: Metadata { _internal_repr: {} } } payments error:  { Error: expected 1 macaroon, got 0     at /home/kurisu/zap-desktop/node_modules/grpc/src/node/src/client.js:554:15 code: 2, metadata: Metadata { _internal_repr: {} } } invoices error:  { Error: expected 1 macaroon, got 0     at /home/kurisu/zap-desktop/node_modules/grpc/src/node/src/client.js:554:15 code: 2, metadata: Metadata { _internal_repr: {} } }

Do you have you run ./node_modules/.bin/electron-rebuild and do you have LND running?

Yes LND is running
2017-08-29 22:09:18.156 [WRN] LTND: open /home/kurisu/.lnd/lnd.conf: no such file or directory 2017-08-29 22:09:18.156 [INF] LTND: Version 0.3.0-alpha 2017-08-29 22:09:18.156 [INF] CHDB: Checking for schema update: latest_version=0, db_version=0 2017-08-29 22:09:18.159 [INF] LTND: Primary chain is set to: bitcoin 2017-08-29 22:09:18.980 [INF] LNWL: Opened wallet 2017-08-29 22:09:19.020 [INF] LNWL: Established connection to RPC server localhost:18334 2017-08-29 22:09:19.916 [INF] LNWL: The wallet has been unlocked without a time limit 2017-08-29 22:09:19.916 [INF] LNWL: Catching up block hashes to height 1180518, this will take a while... 2017-08-29 22:09:19.920 [INF] LTND: LightningWallet opened 2017-08-29 22:09:19.943 [INF] RPCS: gRPC proxy started at localhost:8080 2017-08-29 22:09:19.943 [INF] RPCS: RPC server listening on <IP_ADDRESS>:10009 2017-08-29 22:09:19.943 [INF] LTND: Waiting for chain backend to finish sync, start_height=1180518
2017-08-29 22:12:00.867 [INF] LNWL: Done catching up block hashes 2017-08-29 22:12:00.869 [INF] LNWL: Started rescan from block<PHONE_NUMBER>00069d79fc4a599dff2c8b9152813b469b49d856b86ad9a23cd402 (height 1180518) for 0 addresses 2017-08-29 22:12:00.870 [INF] LNWL: Finished rescan for 0 addresses (synced to block<PHONE_NUMBER>00069d79fc4a599dff2c8b9152813b469b49d856b86ad9a23cd402, height 1180518) 2017-08-29 22:12:00.870 [INF] LNWL: Catching up block hashes to height 1180518, this might take a while 2017-08-29 22:12:00.872 [INF] LNWL: Done catching up block hashes 2017-08-29 22:12:01.028 [INF] LTND: Chain backend is fully synced (end_height=1180518)! 2017-08-29 22:12:01.072 [INF] LNWL: Established connection to RPC server localhost:18334 2017-08-29 22:12:01.072 [INF] HSWC: Starting HTLC Switch 2017-08-29 22:12:01.072 [INF] NTFN: New block epoch subscription 2017-08-29 22:12:01.073 [INF] DISC: Authenticated Gossiper is starting 2017-08-29 22:12:01.073 [INF] NTFN: New block epoch subscription 2017-08-29 22:12:01.073 [INF] CRTR: FilteredChainView starting 2017-08-29 22:12:01.114 [INF] LNWL: Established connection to RPC server localhost:18334 2017-08-29 22:12:01.115 [INF] CRTR: Prune tip for Channel Graph: height=1180518, hash=000000000000069d79fc4a599dff2c8b9152813b469b49d856b86ad9a23cd402 2017-08-29 22:12:01.115 [INF] CRTR: Filtering chain using 0 channels active 2017-08-29 22:12:01.115 [DBG] CRTR: Updating chain filter with new UTXO's: [] 2017-08-29 22:12:01.115 [INF] CMGR: Server listening on [::]:9735

Ahh! I ran with --no-macaroons and it works!!

"Ahh! I ran with --no-macaroons and it works!!" - This is not the best practice...


OnSuccessStepId not working in New-DbaAgentJobStep

Before submitting a bug report:

[x] Ensure you are able to reproduce it on the latest released version (we release often)
[x] Verified this bug is not already reported in an issue
[x] Verified errors are not related to permissions
[x] Can reproduce in a clean PowerShell session (clean = powershell -NoProfile)

Steps to Reproduce
New-DbaAgentJob -SqlInstance $myserver -Job "myTestJob"
New-DbaAgentJobStep -SqlInstance $myserver -Job "myTestJob" -StepId 1 -Subsystem TransactSql -StepName "myFirstStep" -Command "select 'oh, hello'" -OnSuccessAction GoToStep -OnSuccessStepId 2

Expected Behavior
Job step should be created.
Actual Behavior
Job step creation fails:
WARNING: [13:21:37][New-DbaAgentJobStep] Parameter OnSuccessStepId can only be used with OnSuccessAction 'GoToStep'.
Environmental data

PowerShell:
Name                           Value

PSVersion                      5.1.14409.1012
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.14409.1012
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>

SQL Server:
Microsoft SQL Server 2017 (RTM-CU11) (KB4462262) - 14.0.3038.14 (X64)
Sep 14 2018 13:53:44
Copyright (C) 2017 Microsoft Corporation
Developer Edition (64-bit) on Windows Server 2016 Standard 10.0  (Build 14393: ) (Hypervisor)

I will investigate this. Seems like a check is done incorrectly.

I've got a pull request almost done for it. I think one of the operators needs to be switched, but also I think we only want a step ID if the action is "GoToStep", not "GoToNextStep".

#4313


[Documentation] How to calculate block hash and block body hash.

It is my understanding that the block hash is the hash of the header of a block;
the hash of the header would be the one to be later included in the next block header as prev_hash field(null in case the block in question is genesis ?)
the header of a block includes as a field the hash of the body in the cddl commented with ; merkle triple root
in the source the best I could find is hashAlonzoTxSeq
where it seems the hash of the block body is calculated as something like this
hash(
    hash( toCbor( bodies ) ) +
    hash( toCbor( witnesses ) ) +
    hash( toCbor( meatadata ) ) +
    hash( toCbor( isValidSet ) )
)

( where "+" is the concatenation of bytestrings )
Questions

is my understanding of the block_hash being different than block_body_hash correct?

the Hash type kinda hides the hash algorithm, is it safe to assume we are talking of blake2b with digest of 32 bytes?

what is the ; merkle triple root comment for? I see 4 parts being hashed in hashAlonzoTxSeq. are the transactions bodies hashed as a merkle tree? or just as a cbor array of tx bodies?

CBOR can represent the same data in many ways, is there a standard encoding for the block elements?

is my understanding of the block_hash being different than block_body_hash correct?

I think so. I don't see where you got the variable name block_hash from, but yes, each block header body contains a field prev_hash which is a hash of the previous block header (and yes, each block header body contains a hash of its body, more on that below). The types in Figure 53 of the shelly ledger spec (hopefully) make this clear.

the Hash type kinda hides the hash algorithm, is it safe to assume we are talking of blake2b with digest of 32 bytes?

That's correct. all the crypto primitives are explained in appendix A of the shelley ledger spec.

what is the ; merkle triple root comment for? I see 4 parts being hashed in hashAlonzoTxSeq. are the transactions bodies hashed as a merkle tree? or just as a cbor array of tx bodies?

It's more like a merkle bonsai :) , and "triple" should be replace by "quadruple" (it used to be a triple up until the Alonzo era, when the "is valid" flags were introduced to transactions). so yes, it's just the hash of four concatenated hashes. the idea being, for example, you could throw away the witnesses after you've checked them and only need the hash to verify stuff.

CBOR can represent the same data in many ways, is there a standard encoding for the block elements?

Nope. There is such as thing an canonical CBOR, but we explicitly chose not to use it for hashes on user-supplied data. For the block body hash, you need to concatenate the exact CBOR bytes supplied by the SPO for each of the four components.

For the block body hash, you need to concatenate the exact CBOR bytes supplied by the SPO for each of the four components.

If I build a block on my own will any other node be able to indipendently verify my block?

If I build a block on my own will any other node be able to indipendently verify my block?

yes! provided that the node in question does not re-serialise the block when computing the hash. that's the heart of the issue being discussed in https://github.com/input-output-hk/cardano-ledger/issues/2943.


Architectural redesign

We should change the architectural design of the entire framework.
Before we had 4 layers in mind, each one on top of the other representing a dependence (i.e., the next layer depends on the previous one):

SoleData, for data manipulation and wrangling;
SoleModels, for models, meta-models, etc;
SolePostProcessing, for post-processing needs such as interpretability;
SoleDeploy, to deploy models.

Now the entire architecture should be redesigned in the following repositories:

SoleBase, which should include SoleData, SoleLogics (i.e., logics like HS and variants), and SoleModels;
SoleModelling, for putting beautifully altogether to do modelling tasks;
SolePostProcessing, as before;
Sole, which encompasses all.

The dependence order should be maintained as before, that is, Sole depends on SolePostProcessing that depends on SoleModelling which depends on SoleBase.
Finally, at this point of our understanding of the problem on how to do things elegantly,  other two repositories should be made:

SoleVisualization, for beautiful visualizations of all kinds of things in the framework;
SoleDeploy, to deploy models, as before.

Concluding, this issue represents a major change, and should probably represent the first release of the framework.

It should also be desirable to have a package called SoleUtils that, to some extent, contains heterogeneous utilities (i.e., applicable to many cases, not to specific ones, if possible). For example, it could contain the Loggers.