TagBot trigger issue

This issue is used to trigger TagBot; feel free to unsubscribe.
If you haven't already, you should update your TagBot.yml to include issue comment triggers.
Please see this post on Discourse for instructions and more details.
If you'd like for me to do this for you, comment TagBot fix on this issue.
I'll open a PR within a few hours, please be patient!

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/25734

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/27318

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/27318

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/28891

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/28891

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/29183

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/31352

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/34081

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/36904

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/41476

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/43336

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/50122

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/50749

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/50910

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/52379

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/64601

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/65879

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/71231

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/84644

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/110888

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.


Doesn't work on ionic 2

Tried it on ionic 2. Still show scroll instead of expanding

I'm going to need more information than this I'm afraid. Please could you share your code or put together an app that reproduces the issue, along with the version of the ionic cli you are using.

Really sorry about that. It suddenly works after I rebuild my app the second time. You may close this.


set securityContext.runAsNonRoot value to true

Reported by SAST tool:
Sigma main event: The Kubernetes container is allowed to run as the root user. This may allow attackers to gain the root privileges of the host when the container is compromised.
remediation: Explicitly set the 'securityContext.runAsNonRoot' value to 'true' to prevent the container from running as a root-level user.
JIRA: OSPRH-9907

/hold
we are in code freeze

/unhold

@gthiemonge: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name 	Commit 	Details 	Required 	Rerun command
ci/prow/octavia-operator-build-deploy-kuttl 	0658fe2 link 	true 	/test octavia-operator-build-deploy-kuttl
Full PR test history. Your PR dashboard.

error: build error: Failed to push image: trying to reuse blob sha256:4d5d1cbd7ece41ce278c26338e01e2b82e1861b820ca052da9f3e0b16815358f at destination: pinging container registry quay.rdoproject.org: Get "https://quay.rdoproject.org/v2/": dial tcp <IP_ADDRESS>:443: i/o timeout

/test octavia-operator-build-deploy-kuttl

lgtm

/lgtm


Invalid or unknown key

What happened?
I'm trying to test one of the examples with no success so far with the message "Invalid or unknown key"
Steps to reproduce
My gcloud account is signed in locally and I've configured the project according to this page https://www.pulumi.com/docs/get-started/gcp/begin/
    public static void main(String[] args) {
        Pulumi.run(ctx -> {

            // Create a Bucket object
            var bucketObject = new BucketObject("index.html", BucketObjectArgs.builder()
                    .bucket("test")
                    .source(new FileAsset(loadFileFromResources("index.html").getAbsolutePath()))
                    .build()
            );

            ctx.export("bucketEndpoint", Output.format("http://storage.googleapis.com/%s/%s", "test", bucketObject.name()));

   }

Expected Behavior
A working deployment of anything
Actual Behavior
I'm running into this ominous error that doesn't give me enough hints to know where to look at.
  gcp:storage:BucketObject (index.html):
    error: could not validate provider configuration: 1 error occurred:
        * Invalid or unknown key

I've also tried Cloud Run deployments with the same result and I've also tried the verbose argument without any further logs provided.
What could it be and what key it is talking about?
Output of pulumi about
CLI
Version      3.43.0
Go Version   go1.19.1
Go Compiler  gc
Plugins
NAME  VERSION
java  unknown
Host
OS       Microsoft Windows 11 Pro
Version  10.0.22621 Build 22621
Arch     x86_64
This project is written in java: executable='C:\Program Files\Java\jdk-11.0.2\bin\java.exe' version='java 11.0.2 2019-01-15 LTS
Java(TM) SE Runtime Environment 18.9 (build 11.0.2+9-LTS)
Java HotSpot(TM) 64-Bit Server VM 18.9 (build 11.0.2+9-LTS, mixed mode)' java='C:\Program Files\Java\jdk-11.0.2\bin\java.exe' javac='11.0.2'
Current Stack: demo-develop
Found no resources associated with demo-develop
Found no pending operations associated with demo-develop
Backend
Name           DESKTOP-O7MCMUT
URL            file://~
User           DESKTOP-O7MCMUT\Marian
Organizations
No dependencies found
Additional context
No response
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

It turned out the cause was within my config.
I was using the project id instead of the project name
Pulumi.demo-develop.yaml
encryptionsalt: ...
config:
  gcp:project: my-project-name
  gcp:region: us-central1

Would be nice to have an improved error message or support of both the id and the name

Hi @mklueh - thank you for the update and glad you made it work!
I do not believe that we would be able to make project name work for a configuration, as it can be changed at any time - however, we can add a caveat to the installation docs to hopefully avoid confusion in the future.


recency test on inserted_timestamp

change recency test to be on inserted_timestamp. New records won't always be grabbed during the runs but we expect the runs to update the inserted_timestamp each time.

You're right that this test only really checks if ' the model recently run successfully'. We expect new data every epoch, so ~2.5 days, but the issue is if we don't get anything in that window then we can't retrieve it since those calls only return data for the current epoch. During an epoch it would insert the same data again, and there shouldn't be any changes (besides a very small percentage of stake accts that go through merges/splits) -- my thought was this would address that issue of confirming the API calls are working properly, and then we can fix it before the next epoch starts.

If it is ~2.5 days then can we also have recency test on _inserted_timestamp of 3 or 4 days or would that not be useful?

I dont think it would be useful. The inserted_timestamp test would alert before the one for _inserted_timestamp, and also by the time the '_inserted_timestamp' alerts we'd be out of luck because the epoch is passed.


Script to run owner commands on all contracts on all chains of a given deployment

We frequently need to adjust configurations on the contracts which have the onlyOwner modifier.
In order to save time, provide a script which consumes a config with the parameters to configure and the deployment directory and execute the configuraition with the owner key on all chains.

closing in favor of #972


when running project report error

ModuleNotFoundError: No module named 'toolkit.sequence_tagging'
From:
File "./apiCore.py", line 26, in
from toolkit.sequence_tagging import text2entity

It's seems like missing requirements.txt

Hi, there, the package is used to tag potential entities. You are free to remove it.


Audio devices don't actually change on linux

I'm on arch linux 64 bit, using teams git up to date. When changing the input/output devices (in teams settings/devices), they don't actually change. I was able to resolve the problem by manually changing the devices to the correct ones in pauvucontrol, however it did cause a lot of problems since I have never messed around with my audio devices since installing.

Could you please reach out to Product Support channels.

Could you please reach out to Product Support channels.


[SPARK-30516][SQL] statistic estimation of FileScan should take partitionFilters into account

What changes were proposed in this pull request?
Refine FileScan.estimateStatistics to take partitionFilters into account.
Why are the changes needed?
Currently, FileScan.estimateStatistics does not take partitionFilters into account, which may lead to bigger sizeInBytes. It should be reasonable to change it to involve partitionFilters when estimating the statistics.
Does this PR introduce any user-facing change?
no
How was this patch tested?
existing unit tests.

retest this please

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/22462/
Test PASSed.

Test build #117702 has started for PR 27213 at commit e948650.

Test build #117702 has finished for PR 27213 at commit e948650.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/117702/
Test PASSed.

cc @cloud-fan

Test build #117797 has started for PR 27213 at commit 95d59a3.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/22560/
Test PASSed.

Test build #117799 has started for PR 27213 at commit 86b9043.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/22562/
Test PASSed.

Test build #117799 has finished for PR 27213 at commit 86b9043.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/117799/
Test FAILed.

retest this please

Test build #117803 has started for PR 27213 at commit 86b9043.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/22566/
Test PASSed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/117803/
Test FAILed.

Test build #117797 has finished for PR 27213 at commit 95d59a3.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/117797/
Test PASSed.

Could you add some tests for this improvement?

Test build #118147 has started for PR 27213 at commit 2e210a0.

Could you add some tests for this improvement?

@ Added one test, please help review. thanks.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/22909/
Test PASSed.

Test build #118147 has finished for PR 27213 at commit 2e210a0.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/118147/
Test PASSed.

cc @cloud-fan


Post/Page/User/Game/Comment Edit View Jumping

When the edit view is larger than the screen, typing characters makes the browser focus jump around.

This is super annoying.

This should be fixed.


The paper key you entered had an invalid version.

Hi, I think I've found a bug while trying to recover my account.  I've been trying various words for a paper key, and got most of the errors listed https://github.com/keybase/kbfs/blob/master/vendor/github.com/keybase/client/go/libkb/passphrase_helper.go along the way,
This means all my words are now valid, go version reports version 1.8.3, and fuse <IP_ADDRESS>.  The message I cannot get past is:
"It looks like there was a typo. The paper key you entered had an invalid version. Please try again."
I see that this is produced conditional on if version != PaperKeyVersion.  Any help appreciated.

It's a mistake on your part, but @patrickxb can clarify further.

Hi Max and thanks for getting back to me so fast.  I'll be patient and wait because there's a 6 hour time difference!

@alxbuilder are you still having trouble?


Rotate Box Gesture problem

Gesture Listener not working with rotated box.
Its been observed if I rotate the widget 90 degrees the gesture is been picked only from the 0,0 position. If the user does not click at this position the widget do not get clicked
The part that is highlighted as grey is only clickable

   RotatedBox(
                              quarterTurns: 3,
                              child: TextButton(
                                onPressed: (){
                                  print("test");
                                  Get.toNamed(HomeShowAllRoute);
                                },
                                child: Text("Test", style: themeData.textTheme.headline1,),
                              ),
                            ),

Hi @parmarravi
I tested this on the latest stable and master channel using the sample code below and it is not reproducible.
Can you please provide a minimal reproducible code that captures the problem and does not include any third party plugin, as well as your flutter doctor -v?

sample code
import 'package:flutter/material.dart';

const Color darkBlue = Color.fromARGB(255, 18, 32, 47);

void main() {
  runApp(MyApp());
}

class MyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      theme: ThemeData.dark().copyWith(
        scaffoldBackgroundColor: darkBlue,
      ),
      debugShowCheckedModeBanner: false,
      home: Scaffold(
        body: Center(
          child: MyWidget(),
        ),
      ),
    );
  }
}

class MyWidget extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return RotatedBox(
      quarterTurns: 3,
      child: TextButton(
        onPressed: () {
          print("test");
        },
        child: const Text(
          "Test",
          style: TextStyle(
            color: Colors.white,
            fontSize: 30,
          ),
        ),
      ),
    );
  }
}

flutter doctor -v
[✓] Flutter (Channel stable, 2.5.3, on macOS 11.6.1 20G224 darwin-x64, locale en-US)
    • Flutter version 2.5.3 at /Users/flo/development/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 18116933e7 (6 weeks ago), 2021-10-15 10:46:35 -0700
    • Engine revision d3ea636dc5
    • Dart version 2.14.4

[!] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
    • Android SDK at /Users/flo/Library/Android/sdk
    • Platform android-31, build-tools 31.0.0
    • Java binary at: /Applications/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7281165)
    ! Some Android licenses not accepted.  To resolve this, run: flutter doctor --android-licenses

[✓] Xcode - develop for iOS and macOS
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 13.0, Build version 13A5212g
    • CocoaPods version 1.11.0

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2020.3)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7281165)

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

[✓] Connected device (4 available)
    • Android SDK built for x86 (mobile) • emulator-5554                        • android-x86    • Android 11 (API 30) (emulator)
    • iPhone 12 Pro Max (mobile)         • 98CBBFB1-4069-4A28-B7F7-138911ACBE72 • ios            •
      com.apple.CoreSimulator.SimRuntime.iOS-15-0 (simulator)
    • macOS (desktop)                    • macos                                • darwin-x64     • macOS 11.6.1 20G224 darwin-x64
    • Chrome (web)                       • chrome                               • web-javascript • Google Chrome 93.0.4577.63

! Doctor found issues in 1 category.

[✓] Flutter (Channel master, 2.6.0-12.0.pre.801, on macOS 11.6.1 20G224 darwin-x64, locale en-US)
    • Flutter version 2.6.0-12.0.pre.801 at /Users/flo/fvm/versions/master
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 7cb0da154a (2 hours ago), 2021-11-23 00:33:03 -0500
    • Engine revision 7d4107a84d
    • Dart version 2.16.0 (build 2.16.0-36.0.dev)
    • DevTools version 2.8.0

[!] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
    • Android SDK at /Users/flo/Library/Android/sdk
    • Platform android-31, build-tools 31.0.0
    • Java binary at: /Applications/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7281165)
    ! Some Android licenses not accepted.  To resolve this, run: flutter doctor --android-licenses

[✓] Xcode - develop for iOS and macOS (Xcode 13.0)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • CocoaPods version 1.11.0

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2020.3)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7281165)

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

[✓] Connected device (4 available)
    • Android SDK built for x86 (mobile) • emulator-5554                        • android-x86    • Android 11 (API 30) (emulator)
    • iPhone 12 Pro Max (mobile)         • 98CBBFB1-4069-4A28-B7F7-138911ACBE72 • ios            • com.apple.CoreSimulator.SimRuntime.iOS-15-0 (simulator)
    • macOS (desktop)                    • macos                                • darwin-x64     • macOS 11.6.1 20G224 darwin-x64
    • Chrome (web)                       • chrome                               • web-javascript • Google Chrome 93.0.4577.63

! Doctor found issues in 1 category.

Thank you

Sure. Have u clicked to bottom text  b instead of above letters .  The entire text is not clickable only top portion is clickable

Hi @parmarravi, the sample code you provided does not represent the image you included, there is no Button Text Widget in the sample code. Can you provide the code so I can replicate on my end?

okay


{usage} expansion in custom usage no longer works

Since 0.9.0's introduction of bpaf::doc::Doc, I don't see how to do the {usage} expansion that used to be possible. There are a couple examples in the repo, but they're broken.
(btw, looks like the v0.9.0 tag doesn't appear to have been pushed yet)
$ git describe --dirty
v0.8.1-162-gcd5920f
$ rg '\{usage\}'
bpaf_derive/src/top_tests.rs
95:        #[bpaf(options, usage("App: {usage}"))]
107:                .usage("App: {usage}")

examples/customize_help.rs
14:        .usage("You can call it with following flags: {usage}")

Changelog.md
228:- templated usage string: can use "{usage}" in custom overrides
$ cargo run --example customize_help -- --help
    Finished dev [unoptimized + debuginfo] target(s) in 0.07s
     Running `target/debug/examples/customize_help --help`
I am a program and I do things

You can call it with following flags: {usage}

Sometimes they even work.

Available options:
    -d          Release the dragon
    -h, --help  Prints help information

Beware `-d`, dragons be here

I knew I forgot something :)
Main motivation for {usage} expansion was to include application name in the command line, now this is done automatically so most people won't need it. For those who still want it - there's with_usage which gives you a document for original usage and lets you compose the new usage string using that. Please let me know if something is still missing.
https://docs.rs/bpaf/latest/bpaf/struct.OptionParser.html#method.with_usage
I'll look into updating examples.

Tags should be up to date, at least pushing them one more time does nothing...
% git push origin v0.9.0 bpaf_derive-v0.5.0
Everything up-to-date

https://github.com/pacak/bpaf/tags

I knew I forgot something :)

I know that feeling well...

Main motivation for {usage} expansion was to include application name in the command line, now this is done automatically so most people won't need it. For those who still want it - there's with_usage which gives you a document for original usage and lets you compose the new usage string using that. Please let me know if something is still missing.

Oh, I missed with_usage, will try, thanks.
I'm not seeing the application name in the command line by default, though, e.g. if I omit my custom usage (https://github.com/scottlamb/moonfire-nvr/commit/4cbaf178b0ff8f2064650404d0b1a32182fe3698) I just see this:
Moonfire NVR: security camera network video recorder.

Usage: COMMAND ...

Tags should be up to date, at least pushing them one more time does nothing...

Oh, I think it's that unlike earlier tags, it's not an "annotated" tag, so git describe doesn't use it by default.

It will not show up in the tests because tests don't know the app name (unless you specify it yourself with set_name, but it will show up when you run it. That's what I see when I run the link you posted.

https://docs.rs/bpaf/latest/bpaf/struct.Args.html#method.set_name

There's a few things you can simplify a bit with new features:
fn parse_db_dir() -> impl Parser<std::path::PathBuf> {
    bpaf::long("db-dir")
        .help(format!(
            "Directory holding the SQLite3 index database.\nDefault: `{}`",
            DEFAULT_DB_DIR
        ))
        .argument::<std::path::PathBuf>("PATH")
        .fallback_with(|| Ok::<_, std::convert::Infallible>(DEFAULT_DB_DIR.into()))
}

fn parse_db_dir() -> impl Parser<std::path::PathBuf> {
    bpaf::long("db-dir")
        .help("Directory holding the SQLite3 index database.")
        .argument::<std::path::PathBuf>("PATH")
        .fallback(DEFAULT_DB_DIR.into())
        .debug_fallback()
}

Hmm... I wonder it it makes sense to add debug_fallback to fallback_with...

Well, with regular fallback there's always a fallback value I can display, fallback_with is allowed to fail...


Graph ScheduleItems

The first output should only be a unique key for a ScheduleItem. This diff refactors some parts of the scheduler that treat it as the only output.

Makes sense


Escaped Strings in JSON Header

Absolute path to gfxr trace file verified as accepted by chocolatey-installed jq under ARM64 Windows 11 Powershell.
Fixes #1014

CI gfxreconstruct build queued with queue ID 29728.

CI gfxreconstruct build # 2462 running.

CI gfxreconstruct build # 2462 passed.


multi method resolver

update the resolver interface to support multiple methods per resolver as an option.
enforced interface compliance for resolvers in the sdk.

Codecov Report

Merging #332 (29ae6ab) into main (a9e587d) will increase coverage by 0.01%.
The diff coverage is 82.35%.

@@            Coverage Diff             @@
##             main     #332      +/-   ##
==========================================
+ Coverage   57.16%   57.16%   +0.01%
==========================================
  Files          51       51
  Lines        6148     6149       +1
==========================================
+ Hits         3514     3515       +1
  Misses       1974     1974
  Partials      660      660

Impacted Files
Coverage Δ

did/resolver.go
62.50% <62.50%> (+0.80%)
:arrow_up:

did/key.go
72.87% <100.00%> (ø)

did/peer.go
65.58% <100.00%> (ø)

did/pkh.go
73.10% <100.00%> (ø)

did/web.go
70.34% <100.00%> (ø)


TextureButton in ScrollContainer can not be scrolled via dragging on touch screen device

Godot version:

2.1 stable official download
3.0 stable official download
OS/device including version:
Windows 10 x64
Android 7.1.2 - Moto G 2nd gen GPU: Adreno 305
Issue description:

Using a TextureButton (and probably any other button type too) does not scroll when used inside ScrollContainer/VBoxContainer when dragged on a touch screen device. Should be able to drag the button up and down without activating the "pressed" signal. That signal is currently correctly not activating. It is the dragging to scroll that is not working.
This makes ScrollContainer of limited use currently. I am working on a workaround for this by rolling my own texture button class. Will post when it is ready.
Steps to reproduce:
See attached simple project (Godot v3) that demonstrates the problem. Export it to Android. Dragging when holding down the text Label nodes work fine. Dragging does not work when holding down TextureButton (the ScrollContainer contents does not move). Press the button to quit the application.
Minimal reproduction project:

g3scrolltest.zip

Uncheck Control/Focus/Stop Mouse in Inspector panel with 2.1.x
Change Control/Mouse/Filter to Pass in Inspector panel with 3.0

Thanks for taking the time to look at this issue. I had not actually seen that option. But, although your suggestions allows the button to be scrolled while dragged, as soon as you let go, it is selected anyway. It I were to have several buttons in a ScrollContainer and I wanted to drag and scroll to one out of view, I would not be able to do so without the button being dragged activating.

If anyone else is having this issue, I have worked around it by creating my own plugin. It doesn't do all the things that TextureButton does, but it's good enough for my needs (just supports drag (without activating) and select). It is for Godot v3.
Instructions: create a directory called "addons" in your project dir (if you don't already have one). Extract zip in there. Add a "ScrollTextureButton" node (you should find it as a child of "TextureRect"). Assign your own function to the signal "Pressed".
ScrollTextureButton.zip

I was also struggling with this issue, however my workaround is a little more direct.
I both connect the "button_down" and "button_up" signals and check if the parent Scrollcontainer scroll_vertical value has changed between the press and release signal.
Not really elegant ( traversing up the hierarchy ) but it works fine
For 2.1 use the get_v_scroll accessor

@wombatwingdings
#17081 solved your problem which button is pressed after scrolling.
and this was cherry-picked to 3.0.3.
so, can this be closed?

@volzhs
It does sound like it is fixed. I can't test myself until 3.0.3 is released as I haven't got round to building Godot from source yet. Will test and close when it is available, but also happy for it to be closed before hand.

@wombatwingdings we can close after releasing 3.0.3 than. :)

OK, I can now build Godot from source. I can confirm that the issue is fixed in 3.1 trunk.

my solution for this problem:
func _input(event):
	var v_bar_lenght = $ScrollContainer.get_v_scrollbar().get_instance_id()
		if event is InputEventScreenDrag:
			if (event.relative.y > 1):
				bar_swipe -= 20
				bar_swipe = clamp(bar_swipe, 0, 140)
				if bar_swipe >= v_bar_lenght:
					bar_swipe = v_bar_lenght
				$ScrollContainer.set_v_scroll(bar_swipe)

			if (event.relative.y < 0):
				bar_swipe += 20
				bar_swipe = clamp(bar_swipe, 0, 140)
				$ScrollContainer.set_v_scroll(bar_swipe)

Scene structure:
|--> CanvasLayer
|--> PanelContainer
|--> VBoxContainer

If anyone is still having issues with texture buttons in scroll containers on mobile, I was able to resolve my issue of scrolling working but the buttons being tricky to select by increasing the scroll container deadzone to ~25.
The scene structure is:
|--> Scroll Container
|--> VBoxContainer
|--> Texture Button


Lidar rays as state input

I found the state (the input to the deep-Q network) in the ROS2 version weird and confusing. As the documentation says and what is implemented in ROS 1 versions, the state supposed to be a vector by size 26 including 24 rays of lidar. However, in the ROS2 implementation, just min range and arg min of the lidar are extracted and the state is just a vector by size 4! Could you please explain what is going on?

yes i too have the same doubt.
how the vector value from lidar is considered in the input state?
here is my input state value.

Sorry about the discrepancy between the eManual descriptions and the ROS2 source code.
The ROS2 code had been modified to use the distance and angle of the goal position, and those of the nearest obstacle (from the scan data) as an input state o.
I'm currently reviewing the machine learning code as well as the documentations.
Thank you.


waffle_pi cartographer failing

I am running the Turtlebot3 in a gazebo environment with ros foxy on Ubuntu 20.04. While the Burger model is running fine within cartographer as far as i can tell (i let it run for over an hour), the waffle_pi model starts behaving weird some minutes after the start of cartographer:

I tried this on the ros2, ros2-devel and foxy-devel branch - all waffle_pi models behave the same way.

Hi,
It looks like the Rviz has some issue with filtering the IMU sensor data.
Could you turn off the imu data option and see if it fixes the issue?
https://github.com/ROBOTIS-GIT/turtlebot3/blob/foxy-devel/turtlebot3_cartographer/config/turtlebot3_lds_2d.lua#L52

Yes, turning off the imu data option clearly helps. But is the IMU sensor data different between the burger and the waffle_pi model?

No, both Burger and Waffle Pi use the identical IMU as they are using the IMU on OpenCR1.0 board.

But where is the difference then? Burger model is running fine with IMU data option turned on while waffle_pi is not?

There was a missing imu joint in the sdf file and this PR(#133) will fix the issue in the gazebo.

After seeing that you merged the PR into branch ros2-devel, i switched to this branch, pulled (i did see the change in the 4 sdf files),  turned IMU data back on in the cartographer config and ran my usual setup:

ros2 launch turtlebot3_gazebo turtlebot3_world.launch.py
ros2 run turtlebot3_gazebo turtlebot3_drive
ros2 launch turtlebot3_cartographer cartographer.launch.py use_sim_time:=True

in parallel terminals. While the bot moved very well and avoided objects as intended before the change, it now starts after a short time (usually under one minute) to move backwards, collide with the walls and flip over and over.
If i switch to the burger model in all 3 terminals and run the same commands it still behaves as expected.

@GrueneNeun
Thanks for the update.
I'm currently checking on the Waffle Pi. I'll update the package when the issue is resolved.

After this commit the waffle_pi behaves nearly as in the beginning - it avoids objects as expected, but the cartographer does the same flipping as before. Turning off the IMU option in cartographer still helps.

After this commit the waffle_pi behaves nearly as in the beginning - it avoids objects as expected, but the cartographer does the same flipping as before. Turning off the IMU option in cartographer still helps.

@GrueneNeun
Thank you for the feedback.
I'll run the simulation again and see if I can reproduce the problem.
Happy New Year!

@GrueneNeun
Thank you for the feedback.
I'll run the simulation again and see if I can reproduce the problem.
Happy New Year!

It seems i indeed forgot to update the turtlebot3 package - now everything runs as expected.
Thank you for your efforts ;)

It seems i indeed forgot to update the turtlebot3 package - now everything runs as expected.
Thank you for your efforts ;)


AWS PriceInfo reset ProductFamily and add NextToken logic

AWS 드라이버 특이사항

기존 ProductFamily : AmazonEC2 → CPU Credits ~ System Operation 변경
기존 NextToken 인자 값 고려 X → NextToken 값이 있다면 세팅 후 다음 상품 정보 조회

ListProductFamily

ProductFamily 변경
ProductFamily 목록
"productFamily": "CPU Credits",
"productFamily": "Compute Instance (bare metal)",
"productFamily": "Compute Instance",
"productFamily": "Dedicated Host",
"productFamily": "EBS direct API Requests",
"productFamily": "Elastic Graphics",
"productFamily": "Fast Snapshot Restore",
"productFamily": "Fee",
"productFamily": "Load Balancer",
"productFamily": "Load Balancer-Application",
"productFamily": "Load Balancer-Network",
"productFamily": "NAT Gateway",
"productFamily": "Provisioned Throughput",
"productFamily": "Storage Snapshot",
"productFamily": "Storage",
"productFamily": "System Operation",

GetPriceInfo

ServiceCode → AmazonEC2 고정

Filter 조건으로 ProductFamily 설정

NextToken

product 조회 시 NextToken값 세팅 x → 결과 목록 100개 출력
NextToken값이 있다면 값 설정 후 loop반복
NextToken값이 없어질 때 까지 loop 반복

AWS Driver Details

Existing ProductFamily : AmazonEC2 → CPU Credits ~ System Operation
Consider the existing NextToken factor value X → NextToken value, if any, set up and look up the next product information

ListProductFamily

ProductFamily Reset
ProductFamily Lists
"productFamily": "CPU Credits",
"productFamily": "Compute Instance (bare metal)",
"productFamily": "Compute Instance",
"productFamily": "Dedicated Host",
"productFamily": "EBS direct API Requests",
"productFamily": "Elastic Graphics",
"productFamily": "Fast Snapshot Restore",
"productFamily": "Fee",
"productFamily": "Load Balancer",
"productFamily": "Load Balancer-Application",
"productFamily": "Load Balancer-Network",
"productFamily": "NAT Gateway",
"productFamily": "Provisioned Throughput",
"productFamily": "Storage Snapshot",
"productFamily": "Storage",
"productFamily": "System Operation",

GetPriceInfo

ServiceCode → AmazonEC2 fixation

Set ProductFamily as Filter condition

NextToken

NextToken value setting x → output 100 results list when looking up product
If there is a NextToken value, set the value and repeat loop
Repeat loop until NextToken value disappears

Holding this PR until AdminWeb has been Tested


Infinite loop trying to decompile Fanatic

DS gets into an infinite loop and assigns a ton of memory trying to decompile fanatic.
https://gm48.net/game/348/fanatic

Something similar happens with blabbering-buccaneers, but there the loop wasn't infinite; just took a really long while.
https://gm48.net/game/1922/blabbering-buccaneers


Improve RRTMGP.jl performance

TODO: set target?

Targets:
RRTMGP shortwave solve time on (1) V100 for 131,658 cols at 0.98 sec
RRTMGP longwave solve time on (1) V100 for 131,658 cols at 0.85 sec
These targets needs to be adjusted appropriately for P100 and A100 GPUs

Current status:
We are currently at 1.05 sec for the shortwave solver with 131,658 cols on a A100

https://github.com/CliMA/RRTMGP.jl/pull/434

Restructure Source structs https://github.com/CliMA/RRTMGP.jl/pull/436

Simplify type parameters for AtmosphericState https://github.com/CliMA/RRTMGP.jl/pull/437

Always inline and remove use of StepRange https://github.com/CliMA/RRTMGP.jl/pull/438

Restructure LookUpCld to reduce metadata size https://github.com/CliMA/RRTMGP.jl/pull/442

Ease register pressure in GasOptics.jl https://github.com/CliMA/RRTMGP.jl/pull/443

Split shortwave optics function https://github.com/CliMA/RRTMGP.jl/pull/445

Restructure LookUp tables https://github.com/CliMA/RRTMGP.jl/pull/449

Add lower bound for cumulative optical thickness https://github.com/CliMA/RRTMGP.jl/pull/448

https://github.com/CliMA/RRTMGP.jl/pull/453

Add CloudState https://github.com/CliMA/RRTMGP.jl/pull/454

https://github.com/CliMA/RRTMGP.jl/pull/531

https://github.com/CliMA/RRTMGP.jl/pull/532

Change data layout for sources https://github.com/CliMA/RRTMGP.jl/pull/534

Change data layouts for pressure, temperature, col_dry and relative humidity https://github.com/CliMA/RRTMGP.jl/pull/535

Change data layout for Vmr https://github.com/CliMA/RRTMGP.jl/pull/536


[Fix_3473] Fixing build

Fixes https://github.com/apache/incubator-kie-kogito-runtimes/issues/3473

Seems pretty straightforward, thank you! @elguardian can you please prioritize reviewing this one? Thanks!

merged. no need to wait for any longer.


Preserve folder hierarchies on the platform

My team would find the previously requested behaviour in dnanexus/dxWDL#168 very useful.
We are investigating switching over to WDL workflows and are almost there for one of our pipelines. However, one of the problems is that whilst the '--stage-relative-output-folder' argument allows specifying the relative output folder per task for all files produced by that task, it does not allow for individual files to be placed in different directories.
It would be very helpful if the platform allowed for this behaviour through specification in the outputs section of each WDL task, rather than needing to create a separate reorg app (this just adds to the code base that needs to be maintained and means that files are only moved to the correct location at the end of the workflow rather than at the point of delocalisation).
I noticed it has been several years since the last comment on closed issue dnanexus/dxWDL#168 and was hoping you would be able to provide an update as to whether the exploratory work went anywhere and whether the professional services department decided that this functionality would be useful to incorporate into the dxCompiler.
Many thanks!

Directory output feature from WDL 2.0 is supported:
https://github.com/dnanexus/dxCompiler/blob/develop/doc/ExpertOptions.md#directory-outputs

Hi Stanley, I did try to use this but I wasn't able to get it to work. I will give it another try and let you know if I am still having issues.

Hi Rachel you may find the test case helpful as template:
https://github.com/dnanexus/dxCompiler/tree/develop/test/wdl_2_0
We include the tests from the test folder for our integration test so all tests will have to pass in order for the dxCompiler possible. Please make sure that the latest release is used for compile since the directory output support is relatively new.

Hi Stanley,
Thanks for sharing this. It doesn't look like there is a way to be able to
use the Directory outputs to output the files to a specific directory but
then to still be able to specify individual files from that task as inputs
to the next task - is that correct or is there a way to do this?
Many thanks,
Rachel
On Tue, 10 Jan 2023, 22:05 Stanley Lan, @.***> wrote:

Hi Rachel you may find the test case helpful as template:
https://github.com/dnanexus/dxCompiler/tree/develop/test/wdl_2_0
We include the tests from the test folder for our integration test so all
tests will have to pass in order for the dxCompiler possible. Please make
sure that the latest release is used for compile since the directory output
support is relatively new.
—
Reply to this email directly, view it on GitHub
https://github.com/dnanexus/dxCompiler/issues/415#issuecomment-1377954043,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGJK3KUWACRXQ4XCMWCI7ZTWRXMJPANCNFSM6AAAAAATVPLZFA
.
You are receiving this because you authored the thread.Message ID:
@.***>

Could you elaborate what specifically does not work?
The expected and tested behavior is that the code in the task organizes the outputs on a worker into directories - according to the logic of the given task. Like the following:
mkdir outputs/folder_{1..4}
for i in {1..4};
do
echo "Hello" > outputs/folder${i}/my_file_${i}
done

then make your task's outputs look like that:
output {
    Directory outdir = "outputs/"
  }

your next task will have Directory inputs "outputs/"
Where does this behavior break for you?

I think Rachel's goal is to be able to specify (or find a way to specify) one individual file from a task directory output and use it as the input for the next task.
I don't believe such feature is supported by either WDL or dxCompiler/executor. If it is directory output the task generates, that output can only be passed as directory as input for the downstream task(s) via WDL. I can't find any case in the WDL spec that allows pick-and-choose among the directory outputs:
https://github.com/openwdl/wdl/blob/main/versions/development/SPEC.md

My goal is to be able to specify relative output locations for individual files.
Using directory as an output would not work because in my case I am using both WDL tasks and native applets imported as WDL tasks (these have file inputs) in my workflow. The native applets require file inputs whereas the outputs from the previous task passed as inputs to the next task would be directories. It isn't feasible to go through and change all our existing apps to take a different input given the lengthy validation / release / quality management process we have to go through to make changes in a clinical setting. Also dependent upon the task you may not necessarily always want the outputs in the same directory. We would also only want the next task/ app to run if the inputs consisted of all the required files - i.e. the input files exist. If you were to run a workflow that took a directory input, it could be that a previous task/app finished but did not output all the required files for the next task to run (not all required files exist within that directory). With a directory input the next task would still run and fail with an internal error as opposed to just failing to start. This incurs a cost to the customer. Not only that but if you want to group all files within one directory, e.g. a 'bams' directory and there are multiple bams within that directory (e.g. across many samples), specifying that directory as input would mean that all filees within that directory would be uploaded to the worker, again incurring greater cost and a greater runtime for the app despite potentially only needing a single file from that directory. In my case I would be running many concurrent workflows - the app would have no way of knowing which bam file would be the correct one to use for the command, i.e. the bam file that was specific to just that workflow.
I know it is possible to output files from a task to a specific subdirectory using the '--stage-relative-output-folder' argument however this specifies the output directory for all files output by that task and this is not always desirable and doesn't allow to specify output locations for individual files within that task (which is something that is possible and we already do for native applets).
The behaviour makes WDL workflows inflexible in comparison to native workflows and I think there would be benefit to the user in supporting the relative output locations specified within the task output section being reflected within the project heirarchy / relative to the specified destination folder.
I also know that a reorg app is an option however this is also not ideal as it only moves the files at the end of the completion of the workflow.
When compiling/ running a workflow using Cromwell, if a relative output location is specified within the task for an output file e.g. "output/file.txt", the file is then placed within an output directory relative to the execution directory. Is it not possible to replicate similar behaviour but relative to the project for the dxCompiler?

If it is the individual output file among the output directory that your downstream / native app needs, can you declare a File output along with the directory output in the (upstream) task?
That way you get both the output directory as well as the individual output File from the task, and the later can be used as input for downstream.

Hi, I suppose this would be possible however it can be misleading as we have multiple apps that output files into the same folder - if a folder is declared as an output from one file I don't think it would be clear which files from within that folder came from that app and which came from a different app. I think that behaviour allowing you to specify relative output for individual files is the desired behaviour as it is explicit.


toMatchInlineSnapshot doesn't work with template literal tags, again

Describe the bug
I got used to behavior is that pressing u does nothing most of the time. The most annoying thing is that it's always saying that snapshot is successfully updated, even if it doesn't for some reason :(
So now I encountered behavior where vitests doesn't update even with -u flag.
It should've been fixed previously https://github.com/vitest-dev/vitest/issues/723
Reproduction
https://stackblitz.com/edit/vitest-dev-vitest-hwjahu?file=test%2Fsuite.test.ts,package.json&initialPath=__vitest__
But the example object can be simplified.
System Info
System:
    OS: Linux 5.0 undefined
    CPU: (4) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 0 Bytes / 0 Bytes
    Shell: 1.0 - /bin/jsh
  Binaries:
    Node: 16.14.2 - /usr/local/bin/node
    Yarn: 1.22.10 - /usr/local/bin/yarn
    npm: 7.17.0 - /usr/local/bin/npm
  npmPackages:
    vitest: 0.23.2 => 0.23.2

Used Package Manager
npm
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

Yeah, Vitest has this RegExp to detect snapshots:
https://github.com/vitest-dev/vitest/blob/95da4d66933db46da368d5d66f422afd26fba4c1/packages/vitest/src/integrations/snapshot/port/inlineSnapshot.ts#L74
So, if you add a comment it doesn't work. PR welcome.

@sheremet-va thanks! I'll take into whats happened with previous regexp.
BUT why does Vitest tell me that snapshot was successfully updated, when it wasn't? Isn't that misleading? I was already discussing that before, that it shouldn't show all-green and then red on next run without -u.

BUT why does Vitest tell me that snapshot was successfully updated, when it wasn't? Isn't that misleading? I was already discussing that before, that it shouldn't show all-green and then red on next run without -u.

It didn't detect any snapshots actually, so it just showed you default message. I am not against "no snapshots found" message in this case. And show a number of updated snapshots.

Hey @sheremet-va, is this issue still open? If so, can I work on it?

Hey @sheremet-va, is this issue still open? If so, can I work on it?

No, I think it was fixed, but we forgot to close the issue since it's not linked automatically


zipkin tracing: support to make the envoy as the independent hop for tracing

Commit Message: zipkin tracing: support to make the envoy as the independent hop for tracing
Additional Description:
In the previous implementation of zipkin tracer, the inbound envoy will generates server span and the outbound envoy will generates client span. By this way, in the sidecar mode, envoy is treated as part of the app. But in the gateway mode, the zipkin couldn't work correctly.
This PR added a new option to make the envoy worked as independent hop for zipkin tracing. In this new implementation, envoy can work correctly in both sidecar mode and gateway mode.
And this PR will close #22944.
Risk Level: Low, zipkin only updates.
Testing: Unit tests.
Docs Changes: n/a.
Release Notes: Added
Platform Specific Features: n/a.

/retest

/retest

friendly ping @adisuissa

High-level question: is it correct to think that this flag should be true by default? (i.e., if we were to have a runtime guard around it, will it make sense to have it set to true eventually)

IMO, it should be true. But I am afraid there will be many users will be affected. I'm not sure if many people have gotten used to the original model.

It is still somewhat not clear to me and could be due to my misunderstanding of zipkin and tracing.
Is this field separating server and client spans?

In the privious implementation, the zinkin tracer create only one span (server span for inbound, client span for outbound) for a request. The inbound proxy and outbond proxy constitute a complete span pair.
This implementation couldn't work properly in gateway mode. And if inbound traffic routing or outbound traffic routing is disabled, the trace chain couldn't be generated correctly.
And in the new implementaion, if the independent_proxy is set to true (and start child span should be set to true also), the inbound proxy will create a complete span pair for a request independently. The outbound proxy will create a complete span pair indepentdently also.
Inbound proxy and outbound proxy will no longer be bound.

friendly ping @adisuissa

the previous assign is failed  🤣

the previous assign is failed  🤣

In the privious implementation, the zinkin tracer create only one span (server span for inbound, client span for outbound) for a request. The inbound proxy and outbond proxy constitute a complete span pair.
This implementation couldn't work properly in gateway mode. And if inbound traffic routing or outbound traffic routing is disabled, the trace chain couldn't be generated correctly.
And in the new implementaion, if the independent_proxy is set to true (and start child span should be set to true also), the inbound proxy will create a complete span pair for a request independently. The outbound proxy will create a complete span pair indepentdently also. Inbound proxy and outbound proxy will no longer be bound.

Thanks for the explanation. In this case, the name of the field could probably be improved to explain this behavior.
Something in the lines of split_in_out_spans or something that explains what this function does would improve the usability of this feature.
I would suggest adding when the value should be set (i.e., when the proxy is used as a gateway) in the comments.

In the privious implementation, the zinkin tracer create only one span (server span for inbound, client span for outbound) for a request. The inbound proxy and outbond proxy constitute a complete span pair.
This implementation couldn't work properly in gateway mode. And if inbound traffic routing or outbound traffic routing is disabled, the trace chain couldn't be generated correctly.
And in the new implementaion, if the independent_proxy is set to true (and start child span should be set to true also), the inbound proxy will create a complete span pair for a request independently. The outbound proxy will create a complete span pair indepentdently also. Inbound proxy and outbound proxy will no longer be bound.

Thanks for the explanation. In this case, the name of the field could probably be improved to explain this behavior. Something in the lines of split_in_out_spans or something that explains what this function does would improve the usability of this feature. I would suggest adding when the value should be set (i.e., when the proxy is used as a gateway) in the comments.

Got it. I will update it tomorrow.


S3 PutObjectAsync() throws on duplicate trailing header key when SDK retries the request

Describe the bug
S3 PutObjectAsync() throws:
System.ArgumentException: An item with the same key has already been added. Key: x-amz-checksum-crc32c

This consistently happens when:

ChecksumAlgorithm is set to ChecksumAlgorithm.CRC32C or any other additional checksum algorithm
Checksum is calculated by SDK and send via trailing headers, no pre-calculated value is provided
SDK retries the request (e.g. first request fails due to timeout or some other transient error)

Expected Behavior
PutObjectAsync() with checksum algorithm (e.g. CRC32C) can be retried by SDK without throwing exception.
Current Behavior
IAmazonS3.PutObjectAsync() with ChecksumAlgorithm set to CRC32C throws System.ArgumentException when the request is retried by SDK:
Stack trace:
System.ArgumentException: An item with the same key has already been added. Key: x-amz-checksum-crc32c
   at System.Collections.Generic.Dictionary`2.TryInsert(TKey key, TValue value, InsertionBehavior behavior)
   at System.Collections.Generic.Dictionary`2.Add(TKey key, TValue value)
   at Amazon.Runtime.Internal.Util.ChecksumUtils.SetRequestChecksum(IRequest request, String checksumAlgorithm, Boolean fallbackToMD5)
   at Amazon.Runtime.Internal.ChecksumHandler.PreInvoke(IExecutionContext executionContext)
   at Amazon.Runtime.Internal.ChecksumHandler.InvokeAsync[T](IExecutionContext executionContext)
   at Amazon.Runtime.Internal.CredentialsRetriever.InvokeAsync[T](IExecutionContext executionContext)
   at Amazon.Runtime.Internal.RetryHandler.InvokeAsync[T](IExecutionContext executionContext)
   at Amazon.Runtime.Internal.RetryHandler.InvokeAsync[T](IExecutionContext executionContext)
   at Amazon.Runtime.Internal.CallbackHandler.InvokeAsync[T](IExecutionContext executionContext)
   at Amazon.Runtime.Internal.CallbackHandler.InvokeAsync[T](IExecutionContext executionContext)
   at Amazon.S3.Internal.AmazonS3ExceptionHandler.InvokeAsync[T](IExecutionContext executionContext)
   at Amazon.Runtime.Internal.ErrorCallbackHandler.InvokeAsync[T](IExecutionContext executionContext)
   at Amazon.Runtime.Internal.MetricsHandler.InvokeAsync[T](IExecutionContext executionContext)

Reproduction Steps
using Amazon.Runtime;
using Amazon.S3;
using Amazon.S3.Model;

// Credentials taken from ENV
var s3 = new AmazonS3Client(new AmazonS3Config
{
    // Unrealistic timeout so SDK will do a retry
    Timeout = TimeSpan.FromMilliseconds(1),
    RetryMode = RequestRetryMode.Standard,
    MaxErrorRetry = 1
});

// Replace the bucket name with some existing writable bucket
const string bucketName = "SOME_BUCKET";
const string objectKey = "s3-retry-bug";

// Random data;
var data = new byte[1024];
Random.Shared.NextBytes(data);

try
{
    await s3.PutObjectAsync(new PutObjectRequest
    {
        BucketName = bucketName,
        Key = objectKey,
        ChecksumAlgorithm = ChecksumAlgorithm.CRC32C,
        InputStream = new MemoryStream(data)
    });
}
catch (ArgumentException)
{
    Console.WriteLine("Bug reproduced");
}

Possible Solution
I think the exception is thrown from here: https://github.com/aws/aws-sdk-net/blob/a55fc1e7cc85d1c3f09965af12676e973679724a/sdk/src/Core/Amazon.Runtime/Internal/Util/ChecksumUtils.cs#L83-L83
It could probably work if it either checks if the key already exists, or use a setter instead of  Add().
Additional Information/Context
No response
AWS .NET SDK and/or Package version used
AWSSDK.S3 3.7.305.7
Targeted .NET Platform
.NET 7
Operating System and version
mcr.microsoft.com/dotnet/aspnet:7.0 running in AWS EKS

Thanks for reporting this problem, we merged a fix earlier today and it's included in the last version of the S3 package (3.7.305.19 as of today).


⚠ ClamAV has degraded performance

In 4681677, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 40 ms

Resolved: ClamAV performance has improved in 1f64d28.


Generic IP Camera stream source frame-rate

Home Assistant release with the issue:
0.96.5

Last working Home Assistant release (if known):
N/A
Operating environment (Hass.io/Docker/Windows/etc.):
Virtualbox VM (Linux/hass.io)
https://github.com/home-assistant/hassos/releases/download/1.12/hassos_ova-1.12.vmdk

Component/platform:
https://www.home-assistant.io/components/stream/
https://www.home-assistant.io/components/generic/

Description of problem:
Camera Stream from Generic IP camera "stream_source" playing at higher framerate than the source, then "stuttering", before continuing again (at higher framerate).  I get a similar "high-speed" playback issue with my "ring" camera, but this is a separate issue probably.
I only have one other camera brand, but this does not seem to suffer this issue.
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
  - platform: generic
    name: Pool
    still_image_url: http://<IP_ADDRESS>/webcapture.jpg?command=snap&channel=1
    stream_source: rtsp://<IP_ADDRESS>:554/user=admin_password=tlJwpbo6_channel=1_stream=0.sdp?real_stream

  - platform: generic
    name: Upper Front Yard
    still_image_url: http://<IP_ADDRESS>/webcapture.jpg?command=snap&channel=1
    stream_source: rtsp://<IP_ADDRESS>:554/user=admin_password=tlJwpbo6_channel=1_stream=0.sdp?real_stream

  - platform: generic
    name: Back Yard
    still_image_url: http://<IP_ADDRESS>/webcapture.jpg?command=snap&channel=1
    stream_source: rtsp://<IP_ADDRESS>:554/user=admin_password=tlJwpbo6_channel=1_stream=0.sdp?real_stream

Traceback (if applicable):

Additional information:
Streams are fine in other streaming utilities/applications
Have tried various resolution/framerate configs on the cameras.
I initially thought it could be a performance issue, as hass.io was running on a PI, but I have since moved it over to a VM running on a suitably powerful host, with the same issue.

Any feedback here?

@tiaanv - The stream component does not change the frame rate of the video feed, or even decode it.  It just re-packages the video.  Is the video playback visibly faster, or does it just constantly buffer?  Can you try calling the camera.record service and see if the same issue occurs in the recorded video file?  If so, please upload the video somewhere and provide a link.

Thx Jason.  Will follow your suggestions and see if this is just the way the stream is playing back.  The video is visibly faster.
Get Outlook for Androidhttps://aka.ms/ghei36

From: Jason Hunter<EMAIL_ADDRESS>Sent: Wednesday, October 2, 2019 9:25:01 PM
To: home-assistant/home-assistant<EMAIL_ADDRESS>Cc: Tiaan Viljoen<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [home-assistant/home-assistant] Generic IP Camera stream source frame-rate (#25706)
@tiaanvhttps://github.com/tiaanv - The stream component does not change the frame rate of the video feed, or even decode it. It just re-packages the video. Is the video playback visibly faster, or does it just constantly buffer? Can you try calling the camera.record service and see if the same issue occurs in the recorded video file? If so, please upload the video somewhere and provide a link.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/home-assistant/home-assistant/issues/25706?email_source=notifications&email_token=ABD4JJSS2SNL7BZBMDSZNA3QMTYQ3A5CNFSM4IJJWSV2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEAF4I3Q#issuecomment-537642094, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ABD4JJTBF23GVWNPRE74UULQMTYQ3ANCNFSM4IJJWSVQ.


Test that demonstrates a false negative when the --only-use-input-alleles...

argument is present, and a tentative fix.
Although my change to AlleleParser.cpp fixes this particular case, I am not entirely confident that it is the right thing to do.  @ekg your comment directly below my fix ("this needs to be fixed in a big way") seems to imply a solution, but I'm not familiar enough with the code to know exactly what needs to be done.
I have confirmed that with this change, only the variations in the variant-input file are outputted when the --only-use-input-alleles argument is present.  But if there is a better solution, please point me in the right direction and I will be happy to update this pull request.

The problem generally is that there isn't a nice framework to hold the input alleles and their equivalencies in the alignments together.
I'm not sure this is the right fix, but maybe I misunderstand what you've done.
Sorry for such a long delay in reply here.

Thanks @jcallaway - and with a test! I am closing the PR, but your fix is noted and may get merged at some point.


Added $emitters for eventMouseover() and eventMouseout() events

Updated documentation accordingly

Having them as $emitters allows you to use component methods and edit component data. For example, if I want to remember the ID of the last element that was moused over, I obviously can't use the config to say this.lastMouseover = event.id, but even this.$emit() won't work.
Per the Fullcalendar docs, within eventClick, eventMouseover, and eventMouseout, this is bound to the triggering event's <div> element. You already solved this problem by binding this (i.e. the Vue component instance) to self before defining the methods, so self.$emit() gives the expected result

You can use the config prop for that example though.
You can use an arrow function in your config object as the this uses lexical scoping and is bound to the surrounding scope (the Vue component instance)
config: {
  eventMouseout() {
    // this is bound to the triggering event's <div> element.
    console.log(this)
  },
  eventMouseover: (event) => {
    // this is bound to the Vue component instance
    this.lastMouseover = event.title
  },
},

https://codesandbox.io/s/01zvym22n0

Ahh yes, good catch! So if you don't mind me asking, what's the advantage then of $emiting any of the events or even hooks? I think this is what you were referring to in your first comment -- it seems odd that it's not all or nothing. Having them as $emits is more understandable overall and imo more the Vue way, but you're right, leaving them in config is perhaps more sustainable

There is a forecast for the next release including new events?

@ezracelli When I started this wrapper, my use case was quite simple and I only really needed to emit a small number of events, but since this wrapper has been picked up by the community we have a wider range of requirements and that's when I added the config prop as a more scalable way of managing the events. I didn't remove the old emitted events as I didn't want to introduce breaking changes.
I also don't want you to think the work you did in the PR would be a waste or not appreciated, so I thought I would raise this question to gain a new perspectives on this plugin's design.
@luizguilhermefr I will create a new release now.

Yes that makes a lot of sense. Thank you for explaining!

is this getting merged soon?


Blobs and Artifacts don't have namespaces

Perhaps that's good, because it enable sharing, but it might also be a security issue? The namespace is very big for UUIDs, so probably not a problem, but if you can guess the URL of an image that might be a problem. I am unsure of the correct resolution here.

I think maybe I should go half way -- namespaces for artifacts, but not for blobs. You need to know a blobs UUID to use it, so the namespace doesn't add much there. This opens the way for artifacts to share blobs later in a possible future.

Actually, I think the sharing of blobs will matter for CI performance, otherwise we'll be downloading the test images over and over (each test is in its own namespace) and we'll be slower and run out of disk.

Actually, I am flopping back on blobs. CI wont break, because we pre-load the images we need into the shared namespace (sharedwithall). Detecting a reused blob would be complicated, and is therefore against the ethos of Shaken Fist. We can always add it as an optimization later if it turns out to really be nessesary.


Sass compilation breaks if include background-image urls

Problem
When I try to use a simple background image in my sass code background-image: url('pattern-01-white-flowers.png'); I get the following error message:
Failed to compile.

undefined
./assets/styles/theme.scss (../node_modules/css-loader??ref--12-1!../node_modules/postcss-loader/lib??postcss!../node_modules/sass-loader/lib/loader.js??ref--12-3!./assets/styles/theme.scss)
Module not found: Error: Can't resolve './pattern-01-white-flowers.png' in '/Volumes/T5/Sites/sitename/src/assets/styles'
 @ ../node_modules/css-loader??ref--12-1!../node_modules/postcss-loader/lib??postcss!../node_modules/sass-loader/lib/loader.js??ref--12-3!./assets/styles/theme.scss 7:34150-34191
 @ ./assets/styles/theme.scss
 @ ./assets/scripts/layout/theme.js
 @ multi<EMAIL_ADDRESS>./assets/scripts/layout/theme.js

My guess is Webpack parser is trying to process this image into the bundle too.
The image being referenced from that code was added to src/assets/images on my local project.
Thanks!

Try taking it out of your sass file and into your markup to use liquid for relative linking:

That should work!

Check out https://github.com/Shopify/slate/wiki/Slate Tools#how-to-prevent-webpack-from-parsing-some-liquid-methods-and-filters
In your case for local development and Shopify's asset URLs, this adjustment should do the trick:
background-image: url({{ 'pattern-01-white-flowers.png' | asset_url }});


Add jsonlint-py maker

ref http://deron.meranda.us/python/demjson/
It is installed as jsonlint-py on Debian like to not conflict with PHP jsonlint

Merged in 4428d7c, thanks!

Thanks!


[Feature] Does it support ChatGPT Plus subscribed via iOS?

I have subscribed ChatGPT Plus via ChatGPT iOS application. But seems it was not support in ChatGPT-Next-Web. If I switch the model to GPT-4, it returned the following error:
{
"error": {
"message": "The model: gpt-4 does not exist",
"type": "invalid_request_error",
"param": null,
"code": "model_not_found"
}
}
I have also generated a new API key, but still the issue remains.
Does it support this scenario? Or will it support it?

https://github.com/Yidadaa/ChatGPT-Next-Web/blob/main/docs/faq-en.md#how-to-access-the-gpt-4-api

ChatGPT Plus !== GPT 4 API


property: default queries create the property values.

Without this, it is necessary to query an algorithm before setting the default property query.  With this, the value will be created and the default will work.
Fixes #14516

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

24 hours has passed since 'approval: done' was set, but this PR has failing CI tests.  Once the tests pass it will get moved to 'approval: ready to merge' automatically, alternatively please review and set the label manually.

Test failure might be relevant.  Will investigate tomorrow.

Missed a free in the test.  Rereview needed.

Merged to master, thanks for the reviews.


Changed the way to detect if a valid TLSConfig has been set

closes #26793
closes #26781
- What I did
Replace the check for nil TLSClientConfig (which is changed by go for a default structure on http request) by checking the pointer DialTLS pointer in the transport struct
- How to verify it
Tried to run the client example
Signed-off-by: Alexandre ACEBEDO<EMAIL_ADDRESS>

@aacebedo thanks :angel:. There is a golint error though :
19:28:37 Errors from golint:
19:28:37 client/transport.go:26:10: if block ends with a return statement, so drop this else and outdent its block

/cc @runcom @stevvooe

I'll test this out and report back

Wow ! Such a fast answer :)
I've corrected the commit. lint is not complaining anymore

@aacebedo seems like you forgot a return statement:
19:57:02 client/transport.go:32: missing return at end of function

BTW, this is not working
$ docker pull busybox
Using default tag: latest
Warning: failed to get default registry endpoint from daemon (TLSConfig unavailable). Using system default: https://index.docker.io/v1/
TLSConfig unavailable

Yahi, works like charm - thanks @aacebedo
LGTM

looks like a related test failure:
20:55:35 ----------------------------------------------------------------------
20:55:35 FAIL: docker_cli_run_test.go:2631: DockerSuite.TestRunTLSverify
20:55:35
20:55:35 docker_cli_run_test.go:2641:
20:55:35     result.Assert(c, icmd.Expected{ExitCode: 1, Err: "error during connect"})
20:55:35 /go/src/github.com/docker/docker/pkg/integration/cmd/command.go:90:
20:55:35     t.Fatalf("at %s:%d\n%s", filepath.Base(file), line, err.Error())
20:55:35 ... Error: at docker_cli_run_test.go:2641
20:55:35
20:55:35 Command: /go/src/github.com/docker/docker/bundles/1.13.0-dev/binary-client/docker --tlsverify=false ps
20:55:35 ExitCode: 0, Error: %!s(<nil>)
20:55:35 Stdout: CONTAINER ID        IMAGE               COMMAND             CREATED             STATUS              PORTS               NAMES
20:55:35
20:55:35 Stderr:
20:55:35
20:55:35 Failures:
20:55:35 ExitCode was 0 expected 1
20:55:35 Expected stderr to contain "error during connect"
20:55:35
20:55:35
20:55:35
20:55:35 ----------------------------------------------------------------------
20:55:35 ----------------------------------------------------------------------
20:55:35 FAIL: docker_cli_run_test.go:2631: DockerSuite.TestRunTLSverify
20:55:35
20:55:35 docker_cli_run_test.go:2641:
20:55:35     result.Assert(c, icmd.Expected{ExitCode: 1, Err: "error during connect"})
20:55:35 /go/src/github.com/docker/docker/pkg/integration/cmd/command.go:90:
20:55:35     t.Fatalf("at %s:%d\n%s", filepath.Base(file), line, err.Error())
20:55:35 ... Error: at docker_cli_run_test.go:2641
20:55:35
20:55:35 Command: /go/src/github.com/docker/docker/bundles/1.13.0-dev/binary-client/docker --tlsverify=false ps
20:55:35 ExitCode: 0, Error: %!s(<nil>)
20:55:35 Stdout: CONTAINER ID        IMAGE               COMMAND             CREATED             STATUS              PORTS               NAMES
20:55:35
20:55:35 Stderr:
20:55:35
20:55:35 Failures:
20:55:35 ExitCode was 0 expected 1
20:55:35 Expected stderr to contain "error during connect"
20:55:35
20:55:35
20:55:35
20:55:35 ----------------------------------------------------------------------

@stevvooe can you please take a look at this

See https://github.com/docker/docker/issues/26781#issuecomment-248790243. This PR doesn't fix the issue.
Closing.


Import optional packages in a nicer way

🚀 Feature
I would like to suggest to implement a context manager class in order to handle optional imports better. With the context manager implemented, importing optional packages and deferring raising ModuleNotFoundError will look like:
with ContextManager() as cm:
    import torchvision  # doesn't raise `ModuleNotFoundError` here even if it fails.

class SomeClass:
    def __init__(self, ...):
        cm.check()  # raises `ModuleNotFoundError` if `import torchvision` failed.
        ...

Motivation
The suggested context manager reduces duplicate information in the codebase. Currently, there are redundant lines such as try: ... except ModuleNotFoundErorr: ..., _PACKAGE_AVAILABLE and raise ModuleNotFoundError(...).
Example
https://github.com/PyTorchLightning/pytorch-lightning-bolts/blob/4d254fde6112b21436003028d553a726bf7ea6ef/pl_bolts/datamodules/cifar10_datamodule.py#L12-L20
https://github.com/PyTorchLightning/pytorch-lightning-bolts/blob/4d254fde6112b21436003028d553a726bf7ea6ef/pl_bolts/datamodules/cifar10_datamodule.py#L86-L89

Pitch
Here is a minimal example of context manager and its usage.
Example
class ContextManager:
    def __init__(self):
        self.exc = None

    def __enter__(self):
        return self

    def __exit__(self, exc_type, exc_value, traceback):
        self.exc = exc_type, exc_value, traceback
        return True  # Ignores exception if True and reraises exception if False

    def check(self):
        if self.exc is not None:
            exc_type, exc_value, traceback = self.exc
            raise exc_type(exc_value).with_traceback(traceback)

print("Try to import.")
with ContextManager() as cm:
    import aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

print("Tried to import.")
cm.check()

Try to import.
Tried to import.
Traceback (most recent call last):
  File "main.py", line 22, in <module>
    cm.check()
  File "main.py", line 15, in check
    raise exc_type(exc_value).with_traceback(traceback)
  File "main.py", line 19, in <module>
    import aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
ModuleNotFoundError: No module named 'aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa'

Alternatives
As suggested in https://github.com/PyTorchLightning/pytorch-lightning-bolts/pull/338#discussion_r518756049 by @Borda, we could define global variables like _TORCHVISION_AVAILABLE in pl_bolts/__init__.py, but in that way, we will have to add new variables like _NEW_PACKAGE_AVAILABLE as we add new optional packages to Bolts.
See also
Built-in Types - Context Manager Types
Stack Overflow - How to safely handle an exception inside a context manager
Other comments
We can implement the suggested context manager in PL and use it from Bolts. If it should be implemented in PL, could you transfer this issue to PL repo? GitHub Docs - Transferring an issue to another repository
Let me know if it sounds reasonable or too much engineering!

I would agree with the first usage example, define _TORCHVISION_AVAILABLE in relevant upper level init or even in pl_bolts.__init__ but then we do not need to define extra Contex class, then the limiting importing is handled inside
https://github.com/PyTorchLightning/pytorch-lightning-bolts/blob/f00e85dd204fa2434c47d9ae20614b0a2baeb1f0/pl_bolts/utils/warnings.py#L7
but looking at it again, it looks cute: @ananyahjha93  what do you think?

Found some related PRs in other repos, so let me leave them here:

https://github.com/optuna/optuna/pull/1315 <- This is pretty much the same as what I am suggesting here.
https://github.com/tensorflow/datasets/pull/1947

@ananyahjha93 Any thoughts on this? :]

@Borda @ananyahjha93  Can I give it a go for this? otherwise, I'll restart to work on #338 defining global variables like _TORCHVISION_AVAILABLE in pl_bolts/__init__.py for now without implementing the context manager suggested here.

I start playing with conditional imports at https://github.com/PyTorchLightning/pytorch-lightning/pull/4859 https://github.com/PyTorchLightning/pytorch-lightning/pull/4860 but it seems it does not work as I would expect, happy to hear some suggestions :]


Use Kubernetes YAML files to automate creation of containers

Instead of providing instructions for user and updating it every time there's a change, we can generate YAML files on current podman containers using
podman generate kube

and use them to build new containers using
podman play kude [Kubefile.yml]

There's Distrobox that has command distrobox-assemble that can be used for normal containers. There's currently a issue for dual boot users that while resizing a partiiton, it might throw RLIMIT_NOFILE error.
https://github.com/89luca89/distrobox/issues/827


/Trade quality of life

🚀 Feature Proposal
There are times where you might be copying a list of items to trade from another command, this could be a completed trade e.g.
"ghosts are spooky#1111 sold 2x Amulet of glory (t4), 1x Amulet of glory(2), 1x Amulet of glory (t3), 1x Amulet of glory(6), 1x Amulet of glory to xx in return for No items."
or if you're doing a bank text export and filtering.
As it stands, to '/trade items: x,y,z' would not allow me to copy the above message and paste in, as it handles 1 amulet of glory (t4) not 1x amulet of glory (t4)
It would be great if the /trade items: can handle items: "Nx Item" where N is a number, x is the letter 'x' and Item is item name.
This also applies to other items: sub-commands e.g. /sacrifice items:

I don't think this is a necessary feature. I understand why you'd copy someone's trade command, not their sacrifice.
You could just copy the command from the initial /trade or /sacrifice
example:

@LuxrayElite I was doing bank searches and trying to sacrifice from text lists. understood on being able to copy from commands, but it would just be a nice QoL if easy to parse.

Done in next udpate


Missing Search Bar on Blog Page

Describe the bug
The Blog page of the PetMe website does not have a search bar, making it difficult for users to find specific blog posts. This can lead to frustration and make it harder for users to navigate the website and find the content they are looking for.
To Reproduce
Steps to reproduce the behavior:

Go to 'https://akshitagupta15june.github.io/PetMe/'
Click on 'Blogs' in the navbar
See error

Expected behavior
We should consider adding a search bar to the Blog page to make it easier for users to search for specific blog posts by keywords or topics.
Additional context
Proposed Solution: Add a search bar to the Blog page to allow users to search for specific blog posts based on keywords or topics. This will improve the user experience and make it easier for users to navigate the website and find the content they are looking for.

hello sir can you assign me this issue i will make sure this task to be done very fast

Hello @raslene5 I am interested to contribute

Added the search button with

for not present and if the text is present in it then


widthPercent not changing bar width

Changing the widthPercent prop doesn't affect bar width in bar charts.
In BarChart.js, not sure why these lines don't work:
let widthPercent = this.props.data.widthPercent || 0.5;
if (widthPercent > 1) widthPercent = 1;
if (widthPercent < 0) widthPercent = 0;

Oh, I know why. That's an easy fix :)


PID-13 not repeatable

I am seeing the same issue for PID-13. Your example messages doesn't have repeating but in Epic they do. I am going to update using your change but just thought you should know.

Originally posted by @camila8 in https://github.com/microsoft/FHIR-Converter/issues/47#issuecomment-664443578

Thanks for raising the issue. It has been fixed in the commit ed99dcf


PostgreSQLSeverity.error : Unsupported authentication type 10, closing connection

Hi, I'm using postgresql v13.0 x64. The library is giving me the following error:
 PostgreSQLException (PostgreSQLSeverity.error : Unsupported authentication type 10, closing connection. )
Now, yesterday was working just fine, nothing was effectively changed... The code to connect is the simplest (I'm still drafting my app):
 var connection = PostgreSQLConnection('localhost', 5432, 'rnobrega', username: 'rnobrega', password: '...');
Now that is not working, I modified the files pg_hba.conf and postgresql.conf (password encryption to md5, listen_adressses = '*') to replace scram-sha-256 to md5 and still not working...
pg_hba.conf:

local   all             all                                     md5
# IPv4 local connections:
host    all             all             <IP_ADDRESS>/32            md5
# IPv6 local connections:
host    all             all             ::1/128                 md5
# Allow replication connections from localhost, by a user with the
# replication privilege.
local   replication     all                                     md5
host    replication     all             <IP_ADDRESS>/32            md5
host    replication     all             ::1/128                 md5
host    all             all             locahost                md5

any clues to what might be happening?

For reference: Postgres 13 gets scram-sha-256 as the default password_encryption value, and the current Dart library supports only md5. (SO thread)
If anybody wants to write support for the new hash, lib/src/connection_fsm.dart has the relevant authentication code, I'm happy to review PRs... :)

wondering has scram-sha-256 support now been added ?


Fix DefaultColumnWidth

This PR fixes DefaultColumnWidth type and implementation. Due to POI bug it returned baseColumnWidth, which is integer. This is a breaking change.
Fixes #943

This seems to be incorrect: when retrieving column width we should check first if the column width is set, otherwise if defaultColWidthspecified, if not, we should check baseColWidth or fallback to 8.43 otherwise

Failing test doesn't related to changes, seems https://github.com/nissl-lab/npoi/pull/1132 has the same issue with parallel test execution.
@lahma, @tonyqus, do you have any ideas how to fix it or maybe how to run IO tests sync?

Would it just make more sense in the test case (TestOpenFileThenSaveDelete) to check that neither of the assigned test files exist?  Honestly I don't fully understand the test case.
Assert.False(File.Exists(tempFile));
Assert.False(File.Exists(tempFile2));

Would it just make more sense in the test case (TestOpenFileThenSaveDelete) to check that neither of the assigned test files exist? Honestly I don't fully understand the test case.
Assert.False(File.Exists(tempFile));
Assert.False(File.Exists(tempFile2));

Yes, this test can be rewritten, but then another IO-dependent test can fail. We need to resolve it globally

I wouldn't trust the RunSerialyAndSweepTmpFilesAttribute at all, it's implementation looks quite fishy and expects that process-wide locks would work for test runners running multiple assemblies concurrently (they don'(. NUnit does not run tests concurrently by default so there's that too.
I'd say removing the attribute and adjusting the test case to check for specific items would be the way to go. Some cleanup logic could go somewhere like assembly fixture teardown.

LGTM


Websocket seems to not work

Hello,
I tried the mqtt_pub.dart test program with two MQTT brokers and the programm seems to block after Opening session.
PS C:\Users\[...]\mqtt\mqtt.dart\example\mqtt_pub> dart mqtt_pub.dart -U ws://test.mosquitto.org:8080/ -t hello -m bob
starting
[WebSocket] Connecting to ws://test.mosquitto.org:8080/
Opening session
>>> Type(1) Len(41) QoS(0) DUP(0) retain(0) <163906778173115100112360300001010410110810811199108111991070111191051081081129712110811197100>]

I forked the library and now mqtt-websockets works with http://test.mosquitto.org. It was because of the lack of the sec-protocole header in the HTTP Upgrade request.
I'll a pull request un few days

Thanks for raising and fixing the issue.


UPDATE HORION 1.20.41 or make it like horion and add some readable english text thnx

Make it more horion and add some english text please or you cab update the <IP_ADDRESS> horion to 1.20.41 and make it imgui supported thanks

第一，我没有1.20的客户端去反编译和调试。第二个我现在没有时间和兴趣去做这些，如果你仅是需要当前版本的英文版，可以去下载源代码，将相关中文字符串翻译成英文然后自行使用vs2022编译。
First, I don't have the 1.20 client to decompile and debug. Second, I don't have the time or interest to do this now. If you just need the English version of the current version, you can download the source code, translate the relevant Chinese strings into English, and then compile them with vs2022 by yourself.

第一，我没有1.20的客户端去反编译和调试。第二个我现在没有时间和兴趣去做这些，如果你仅是需要当前版本的英文版，可以去下载源代码，将相关中文字符串翻译成英文然后自行使用vs2022编译。 First, I don't have the 1.20 client to decompile and debug. Second, I don't have the time or interest to do this now. If you just need the English version of the current version, you can download the source code, translate the relevant Chinese strings into English, and then compile them with vs2022 by yourself.

There is a 1.20 Src, it's from Uffuso (his github user) and about the time and we are willing to wait and a lot of people will contribute to it if its updated to 1.20.41+


Etl rewritten and simplified

I completely re-thought the whole ETL library.
There are backwards incompatible changes hence the move to version 0.4.
There are no more special cases for multiple vs single datasets on input or output side.
The documentation has been updated to reflect all the simplified changes.
All Multiple... and Delegating... classes are gone! Have a look at how little code there is left in the atc.etl library!
The code can do everything that it could before plus:

it is now possible to specify the key for the dataset returned by an extractor (for use in multi-transform)
it is now possible to reference the result of previous extraction steps in case of complex extraction logic (we have seen examples in practice)
save_many now exists although I see no usecase for it.
All orchestration is now streamlined so any sequence of transform, load, extract steps can be orchestrated easily.
the examples are now executed as part of unit testing. They can then be inserted into the readme by a simple script.

@JeppeBlixen I would really appreciate your review since I think you use this in production, and some changes are non-compatible. I recently moved to fixed dependencies, so I know my system won't break, but yours might.


text() vertical align should use font baseline

The text() function has a valign() option for a text vertical alignment with 'bottom' as a default value. However this doesn't use the font baseline, unlike the imagettftext() function. As a result, the text is positioned differently depending on the character height. Try:

aaa
AAA
ÓÓÓ
yyy

There should be an option to enable the default imagettftext() vertical alignment mechanism.

@diverpl Have you tried forcing the driver to imagick? This seemed to respect the font baseline in my case.
I was experiencing a similar issue to yours where, if the line contained no characters with a higher height such as "b", "d", "l", "k", etc, it would not enforce the font baseline to create a proper line height.

This issue should be resolved as of version 3.


Ecto 2.1 support

Ecto 2.1 just came out and I wonder if it will be supported soon by ecto_enum?

+1. There are some features of Ecto 2.1 that I'd really like to use but this is currently holding me back.

This is just a version bump right?

Just released EctoEnum 1.0.1 which has Ecto 2.1 support. No huge change but at least removes the need for using override in mix.exs.


Services stop running after I logout system.

I buy a cheap vps and install linuxbrew in it.
But I find that when I logout the ssh, my homebrew service like nginx stop running.
I test this in my mac, the same result, when I logout my mac, I cannot visit the nginx website from my mobile phone.
How to make the homebrew services keep running even after logout the system?

Read the manpages for brew services. They specify that brew service start will start out as your user (so it won't work when that user is logged out). And sudo brew service start will start system wide


Support separate light/dark themes

I've migrated my programs.zed-editor to take advantage of #359 (thank you!) and had to override the light theme given currently catppuccin only supports a single "flavour" which is implicitly applied across both light and dark modes: https://github.com/samhh/dotfiles/commit/9ca1a63680ef71638ad9612c37181bef06fb4f29#diff-87b22b9d53b9e4c7e5bf904535ac70f0ef2566611199d4cf240ad1704423b58dR87-R89
Ideally, given the likes of Zed support specifying separate light and dark themes, we'd be able to optionally configure a different flavour for each. Presumably then there'd need to be some notion of a default where that dichotomy doesn't exist.

It would be cool to see this. Though it would be interesting. One thing to note is only some ports would be capable of using the dark/light themes. Which may make it hard to implement.
A potential idea would be to modify the catppuccinLib.mkCatppuccinOptions to handle this, however it would make a bit of a grey area around the global flavour option.
Prior art in userstyles:
https://github.com/catppuccin/userstyles/blob/f90308af39acd7843372d1134965a826d4aa5534/template/catppuccin.user.css#L13-14

in my opinion ports that support both light and dark themes should include latte as the light mode variant by default, but there should also be a global or local option to disable this (resulting in the global flavour option being used for both light and dark)
for example:
catppuccin.lightDarkEnable = true;
theme = {
  light = "Catppuccin Latte";
  dark = "Catppuccin " + catppuccinLib.mkUpper cfg.flavor;
};

catppuccin.lightDarkEnable = false;
theme = {
  dark = "Catppuccin " + catppuccinLib.mkUpper cfg.flavor;
  dark = "Catppuccin " + catppuccinLib.mkUpper cfg.flavor;
};

this could of course be shortened with an if statement but I don't know nix

in my opinion ports that support both light and dark themes should include latte as the light mode variant by default, but there should also be a global or local option to disable this (resulting in the global flavour option being used for both light and dark)
for example: catppuccin.lightDarkEnable = true;
theme = {
  light = "Catppuccin Latte";
  dark = "Catppuccin " + catppuccinLib.mkUpper cfg.flavor;
};

catppuccin.lightDarkEnable = false;
theme = {
  dark = "Catppuccin " + catppuccinLib.mkUpper cfg.flavor;
  dark = "Catppuccin " + catppuccinLib.mkUpper cfg.flavor;
};

this could of course be shortened with an if statement but I don't know nix

This seems like a weird solution to the problem. What if I use mocha as my dark theme and frappe as my light theme? That solution wouldn't work for me. The actual solution would be to add separate light and dark flavor options, and then a default flavor option for either light or dark wheb only one theme can be set.

@uncenter ah ok, wasn't aware anyone really did that - and that does make more sense. light mode flavour can fallback to the dark mode one when unset