Tr/show config

PR Type
enhancement, bug_fix

Description

Updated the 'model_turbo' configuration in configuration.toml to 'gpt-4o'.
Enhanced model handling in various tools by adding or removing explicit model type parameters.
Updated forbidden configuration keys in utils.py to include 'ALLOWED_REPOS' and 'APP_NAME'.

Changes walkthrough 📝
Relevant filesEnhancement

utils.pyUpdate Forbidden Configuration Keys

pr_agent/algo/utils.py
Updated the list of forbidden keys in the configuration display function to include 'ALLOWED_REPOS' and 'APP_NAME'.

+1/-1

pr_code_suggestions.pyRefactor Model Handling in Code Suggestions

pr_agent/tools/pr_code_suggestions.py
Removed explicit model type parameter from retry_with_fallback_models function calls.  Added explicit model specification for self-reflection on suggestions to use the turbo model.

+5/-5

pr_description.pySimplify Model Specification in PR Description Tool

pr_agent/tools/pr_description.py
Simplified the call to retry_with_fallback_models by removing the explicit model type parameter.

+1/-1

pr_questions.pyEnhance Model Specification in PR Questions Tool

pr_agent/tools/pr_questions.py
Added explicit model type parameter to retry_with_fallback_models function call.

+2/-1

pr_reviewer.pySimplify Model Handling in PR Reviewer Tool

pr_agent/tools/pr_reviewer.py
Removed the model type parameter from the retry_with_fallback_models function call.

+1/-1

Configuration changes

configuration.tomlUpdate Turbo Model Configuration

pr_agent/settings/configuration.toml
Updated the 'model_turbo' configuration to a new model version 'gpt-4o'.

+1/-1

💡 PR-Agent usage:
Comment /help on the PR to get a list of all available PR-Agent tools and their descriptions

/review auto_approve

/review

/describe

Failed to generate code suggestions for PR

Failed to generate code suggestions for PR

Failed to generate code suggestions for PR

Failed to generate code suggestions for PR

Failed to generate code suggestions for PR

Failed to generate code suggestions for PR

Generating PR code suggestions
Work in progress ...

Preparing PR description...

PR Description updated to latest commit (https://github.com/Codium-ai/pr-agent/commit/c3dca2ef5ae4027502eeb77eb9911cbf767aab9b)

[ ] Copy walkthrough table to "Files Changed" Tab

Preparing review...

Persistent review updated to latest commit https://github.com/Codium-ai/pr-agent/commit/c3dca2ef5ae4027502eeb77eb9911cbf767aab9b

Preparing answer...

It can be invoked manually by commenting on any PR:
/test component_name

where 'component_name' is the name of a specific component in the PR. To get a list of the components that changed in the PR, use the analyze tool.
Language that are currently supported: Python, Java, C++, JavaScript, TypeScript.
Configuration options:

num_tests: number of tests to generate. Default is 3.
testing_framework: the testing framework to use. If not set, for Python it will use pytest, for Java it will use JUnit, for C++ it will use Catch2, and for JavaScript and TypeScript it will use jest.
avoid_mocks: if set to true, the tool will try to avoid using mocks in the generated tests. Note that even if this option is set to true, the tool might still use mocks if it cannot generate a test without them. Default is true.
extra_instructions: Optional extra instructions to the tool. For example: "use the following mock injection scheme: ...".
file: in case there are several components with the same name, you can specify the relevant file.
class_name: in case there are several components with the same name in the same file, you can specify the relevant class name.

See more information about the test tool in the docs.

Generating tests for 'run' ✏
Work in progress ...

Generating PR code suggestions
Work in progress ...

PR-Agent: Missing component name in test command: /test <component_name>.Running automatically on the largest changed component.

 ✨ Test tool usage guide:
The test tool generate tests for a selected component, based on the PR code changes.
It can be invoked manually by commenting on any PR:
/test component_name

where 'component_name' is the name of a specific component in the PR. To get a list of the components that changed in the PR, use the analyze tool.
Language that are currently supported: Python, Java, C++, JavaScript, TypeScript.
Configuration options:

num_tests: number of tests to generate. Default is 3.
testing_framework: the testing framework to use. If not set, for Python it will use pytest, for Java it will use JUnit, for C++ it will use Catch2, and for JavaScript and TypeScript it will use jest.
avoid_mocks: if set to true, the tool will try to avoid using mocks in the generated tests. Note that even if this option is set to true, the tool might still use mocks if it cannot generate a test without them. Default is true.
extra_instructions: Optional extra instructions to the tool. For example: "use the following mock injection scheme: ...".
file: in case there are several components with the same name, you can specify the relevant file.
class_name: in case there are several components with the same name in the same file, you can specify the relevant class name.

See more information about the test tool in the docs.

PR-Agent: Missing component name in test command: /test <component_name>.Running automatically on the largest changed component.

 ✨ Test tool usage guide:
The test tool generate tests for a selected component, based on the PR code changes.
It can be invoked manually by commenting on any PR:
/test component_name

where 'component_name' is the name of a specific component in the PR. To get a list of the components that changed in the PR, use the analyze tool.
Language that are currently supported: Python, Java, C++, JavaScript, TypeScript.
Configuration options:

num_tests: number of tests to generate. Default is 3.
testing_framework: the testing framework to use. If not set, for Python it will use pytest, for Java it will use JUnit, for C++ it will use Catch2, and for JavaScript and TypeScript it will use jest.
avoid_mocks: if set to true, the tool will try to avoid using mocks in the generated tests. Note that even if this option is set to true, the tool might still use mocks if it cannot generate a test without them. Default is true.
extra_instructions: Optional extra instructions to the tool. For example: "use the following mock injection scheme: ...".
file: in case there are several components with the same name, you can specify the relevant file.
class_name: in case there are several components with the same name in the same file, you can specify the relevant class name.

See more information about the test tool in the docs.

Generating tests for 'run' ✏
Work in progress ...

PR-Agent: Missing component name in test command: /test <component_name>.Running automatically on the largest changed component.

 ✨ Test tool usage guide:
The test tool generate tests for a selected component, based on the PR code changes.
It can be invoked manually by commenting on any PR:
/test component_name

where 'component_name' is the name of a specific component in the PR. To get a list of the components that changed in the PR, use the analyze tool.
Language that are currently supported: Python, Java, C++, JavaScript, TypeScript.
Configuration options:

num_tests: number of tests to generate. Default is 3.
testing_framework: the testing framework to use. If not set, for Python it will use pytest, for Java it will use JUnit, for C++ it will use Catch2, and for JavaScript and TypeScript it will use jest.
avoid_mocks: if set to true, the tool will try to avoid using mocks in the generated tests. Note that even if this option is set to true, the tool might still use mocks if it cannot generate a test without them. Default is true.
extra_instructions: Optional extra instructions to the tool. For example: "use the following mock injection scheme: ...".
file: in case there are several components with the same name, you can specify the relevant file.
class_name: in case there are several components with the same name in the same file, you can specify the relevant class name.

See more information about the test tool in the docs.

PR-Agent: Missing component name in test command: /test <component_name>.Running automatically on the largest changed component.

 ✨ Test tool usage guide:
The test tool generate tests for a selected component, based on the PR code changes.
It can be invoked manually by commenting on any PR:
/test component_name

where 'component_name' is the name of a specific component in the PR. To get a list of the components that changed in the PR, use the analyze tool.
Language that are currently supported: Python, Java, C++, JavaScript, TypeScript.
Configuration options:

num_tests: number of tests to generate. Default is 3.
testing_framework: the testing framework to use. If not set, for Python it will use pytest, for Java it will use JUnit, for C++ it will use Catch2, and for JavaScript and TypeScript it will use jest.
avoid_mocks: if set to true, the tool will try to avoid using mocks in the generated tests. Note that even if this option is set to true, the tool might still use mocks if it cannot generate a test without them. Default is true.
extra_instructions: Optional extra instructions to the tool. For example: "use the following mock injection scheme: ...".
file: in case there are several components with the same name, you can specify the relevant file.
class_name: in case there are several components with the same name in the same file, you can specify the relevant class name.

See more information about the test tool in the docs.

Generating tests for 'run' ✏
Work in progress ...

PR-Agent: Missing component name in test command: /test <component_name>.Running automatically on the largest changed component.

 ✨ Test tool usage guide:
The test tool generate tests for a selected component, based on the PR code changes.
It can be invoked manually by commenting on any PR:
/test component_name

where 'component_name' is the name of a specific component in the PR. To get a list of the components that changed in the PR, use the analyze tool.
Language that are currently supported: Python, Java, C++, JavaScript, TypeScript.
Configuration options:

num_tests: number of tests to generate. Default is 3.
testing_framework: the testing framework to use. If not set, for Python it will use pytest, for Java it will use JUnit, for C++ it will use Catch2, and for JavaScript and TypeScript it will use jest.
avoid_mocks: if set to true, the tool will try to avoid using mocks in the generated tests. Note that even if this option is set to true, the tool might still use mocks if it cannot generate a test without them. Default is true.
extra_instructions: Optional extra instructions to the tool. For example: "use the following mock injection scheme: ...".
file: in case there are several components with the same name, you can specify the relevant file.
class_name: in case there are several components with the same name in the same file, you can specify the relevant class name.

See more information about the test tool in the docs.

PR-Agent: Missing component name in test command: /test <component_name>.Running automatically on the largest changed component.

 ✨ Test tool usage guide:
The test tool generate tests for a selected component, based on the PR code changes.
It can be invoked manually by commenting on any PR:
/test component_name

where 'component_name' is the name of a specific component in the PR. To get a list of the components that changed in the PR, use the analyze tool.
Language that are currently supported: Python, Java, C++, JavaScript, TypeScript.
Configuration options:

num_tests: number of tests to generate. Default is 3.
testing_framework: the testing framework to use. If not set, for Python it will use pytest, for Java it will use JUnit, for C++ it will use Catch2, and for JavaScript and TypeScript it will use jest.
avoid_mocks: if set to true, the tool will try to avoid using mocks in the generated tests. Note that even if this option is set to true, the tool might still use mocks if it cannot generate a test without them. Default is true.
extra_instructions: Optional extra instructions to the tool. For example: "use the following mock injection scheme: ...".
file: in case there are several components with the same name, you can specify the relevant file.
class_name: in case there are several components with the same name in the same file, you can specify the relevant class name.

See more information about the test tool in the docs.

Generating tests for 'run' ✏
Work in progress ...

PR-Agent: Missing component name in test command: /test <component_name>.Running automatically on the largest changed component.

 ✨ Test tool usage guide:
The test tool generate tests for a selected component, based on the PR code changes.
It can be invoked manually by commenting on any PR:
/test component_name

where 'component_name' is the name of a specific component in the PR. To get a list of the components that changed in the PR, use the analyze tool.
Language that are currently supported: Python, Java, C++, JavaScript, TypeScript.
Configuration options:

num_tests: number of tests to generate. Default is 3.
testing_framework: the testing framework to use. If not set, for Python it will use pytest, for Java it will use JUnit, for C++ it will use Catch2, and for JavaScript and TypeScript it will use jest.
avoid_mocks: if set to true, the tool will try to avoid using mocks in the generated tests. Note that even if this option is set to true, the tool might still use mocks if it cannot generate a test without them. Default is true.
extra_instructions: Optional extra instructions to the tool. For example: "use the following mock injection scheme: ...".
file: in case there are several components with the same name, you can specify the relevant file.
class_name: in case there are several components with the same name in the same file, you can specify the relevant class name.

See more information about the test tool in the docs.

Generating tests for 'run' ✏
Work in progress ...

PR-Agent: Missing component name in test command: /test <component_name>.Running automatically on the largest changed component.

 ✨ Test tool usage guide:
The test tool generate tests for a selected component, based on the PR code changes.
It can be invoked manually by commenting on any PR:
/test component_name

where 'component_name' is the name of a specific component in the PR. To get a list of the components that changed in the PR, use the analyze tool.
Language that are currently supported: Python, Java, C++, JavaScript, TypeScript.
Configuration options:

num_tests: number of tests to generate. Default is 3.
testing_framework: the testing framework to use. If not set, for Python it will use pytest, for Java it will use JUnit, for C++ it will use Catch2, and for JavaScript and TypeScript it will use jest.
avoid_mocks: if set to true, the tool will try to avoid using mocks in the generated tests. Note that even if this option is set to true, the tool might still use mocks if it cannot generate a test without them. Default is true.
extra_instructions: Optional extra instructions to the tool. For example: "use the following mock injection scheme: ...".
file: in case there are several components with the same name, you can specify the relevant file.
class_name: in case there are several components with the same name in the same file, you can specify the relevant class name.

See more information about the test tool in the docs.

Generating tests for 'run' ✏
Work in progress ...

PR-Agent: Missing component name in test command: /test <component_name>.Running automatically on the largest changed component.

 ✨ Test tool usage guide:
The test tool generate tests for a selected component, based on the PR code changes.
It can be invoked manually by commenting on any PR:
/test component_name

where 'component_name' is the name of a specific component in the PR. To get a list of the components that changed in the PR, use the analyze tool.
Language that are currently supported: Python, Java, C++, JavaScript, TypeScript.
Configuration options:

num_tests: number of tests to generate. Default is 3.
testing_framework: the testing framework to use. If not set, for Python it will use pytest, for Java it will use JUnit, for C++ it will use Catch2, and for JavaScript and TypeScript it will use jest.
avoid_mocks: if set to true, the tool will try to avoid using mocks in the generated tests. Note that even if this option is set to true, the tool might still use mocks if it cannot generate a test without them. Default is true.
extra_instructions: Optional extra instructions to the tool. For example: "use the following mock injection scheme: ...".
file: in case there are several components with the same name, you can specify the relevant file.
class_name: in case there are several components with the same name in the same file, you can specify the relevant class name.

See more information about the test tool in the docs.

Generating tests for 'run' ✏
Work in progress ...

PR-Agent: Missing component name in test command: /test <component_name>.Running automatically on the largest changed component.

 ✨ Test tool usage guide:
The test tool generate tests for a selected component, based on the PR code changes.
It can be invoked manually by commenting on any PR:
/test component_name

where 'component_name' is the name of a specific component in the PR. To get a list of the components that changed in the PR, use the analyze tool.
Language that are currently supported: Python, Java, C++, JavaScript, TypeScript.
Configuration options:

num_tests: number of tests to generate. Default is 3.
testing_framework: the testing framework to use. If not set, for Python it will use pytest, for Java it will use JUnit, for C++ it will use Catch2, and for JavaScript and TypeScript it will use jest.
avoid_mocks: if set to true, the tool will try to avoid using mocks in the generated tests. Note that even if this option is set to true, the tool might still use mocks if it cannot generate a test without them. Default is true.
extra_instructions: Optional extra instructions to the tool. For example: "use the following mock injection scheme: ...".
file: in case there are several components with the same name, you can specify the relevant file.
class_name: in case there are several components with the same name in the same file, you can specify the relevant class name.

See more information about the test tool in the docs.

PR-Agent: Missing component name in test command: /test <component_name>.Running automatically on the largest changed component.

 ✨ Test tool usage guide:
The test tool generate tests for a selected component, based on the PR code changes.
It can be invoked manually by commenting on any PR:
/test component_name

where 'component_name' is the name of a specific component in the PR. To get a list of the components that changed in the PR, use the analyze tool.
Language that are currently supported: Python, Java, C++, JavaScript, TypeScript.
Configuration options:

num_tests: number of tests to generate. Default is 3.
testing_framework: the testing framework to use. If not set, for Python it will use pytest, for Java it will use JUnit, for C++ it will use Catch2, and for JavaScript and TypeScript it will use jest.
avoid_mocks: if set to true, the tool will try to avoid using mocks in the generated tests. Note that even if this option is set to true, the tool might still use mocks if it cannot generate a test without them. Default is true.
extra_instructions: Optional extra instructions to the tool. For example: "use the following mock injection scheme: ...".
file: in case there are several components with the same name, you can specify the relevant file.
class_name: in case there are several components with the same name in the same file, you can specify the relevant class name.

See more information about the test tool in the docs.

PR-Agent: Missing component name in test command: /test <component_name>.Running automatically on the largest changed component.

 ✨ Test tool usage guide:
The test tool generate tests for a selected component, based on the PR code changes.
It can be invoked manually by commenting on any PR:
/test component_name

where 'component_name' is the name of a specific component in the PR. To get a list of the components that changed in the PR, use the analyze tool.
Language that are currently supported: Python, Java, C++, JavaScript, TypeScript.
Configuration options:

num_tests: number of tests to generate. Default is 3.
testing_framework: the testing framework to use. If not set, for Python it will use pytest, for Java it will use JUnit, for C++ it will use Catch2, and for JavaScript and TypeScript it will use jest.
avoid_mocks: if set to true, the tool will try to avoid using mocks in the generated tests. Note that even if this option is set to true, the tool might still use mocks if it cannot generate a test without them. Default is true.
extra_instructions: Optional extra instructions to the tool. For example: "use the following mock injection scheme: ...".
file: in case there are several components with the same name, you can specify the relevant file.
class_name: in case there are several components with the same name in the same file, you can specify the relevant class name.

See more information about the test tool in the docs.

PR-Agent: Missing component name in test command: /test <component_name>.Running automatically on the largest changed component.

 ✨ Test tool usage guide:
The test tool generate tests for a selected component, based on the PR code changes.
It can be invoked manually by commenting on any PR:
/test component_name

where 'component_name' is the name of a specific component in the PR. To get a list of the components that changed in the PR, use the analyze tool.
Language that are currently supported: Python, Java, C++, JavaScript, TypeScript.
Configuration options:

num_tests: number of tests to generate. Default is 3.
testing_framework: the testing framework to use. If not set, for Python it will use pytest, for Java it will use JUnit, for C++ it will use Catch2, and for JavaScript and TypeScript it will use jest.
avoid_mocks: if set to true, the tool will try to avoid using mocks in the generated tests. Note that even if this option is set to true, the tool might still use mocks if it cannot generate a test without them. Default is true.
extra_instructions: Optional extra instructions to the tool. For example: "use the following mock injection scheme: ...".
file: in case there are several components with the same name, you can specify the relevant file.
class_name: in case there are several components with the same name in the same file, you can specify the relevant class name.

See more information about the test tool in the docs.

Generating tests for 'run' ✏
Work in progress ...


Revert "Add support for Monday as first day of the week"

Reverts tjohnn/vuejs-datetimepicker#11

Hi @zerok , It seems some dependencies are missing in your commit.
And part of my aim is to reduce dependencies on the plugin so the users will not have to go through the stress of npm problem at times. But if the dependency is worth it please add it to the package.json file and commit again.
Thanks.

date-fns does not seem to be in the dependencies, can you add it or I should?

Oh okay sorry for the confusion. It maybe it was throwing error due to an error in my set up.
Thanks.

Ah ok 🙂 But why did you then reverted my changes again? 😉

Haha.. I will add it back in a moment

Can you please confirm if everything is  as supposed, I hope I have not messed up any of your changes


Connection to Redis Cluster in Minikube

Hello Alec, I have a problem connecting to a local Redis cluster created in Minikube. If the problem isn't on Fred's side let me know :)
The setup is relatively simple: there's a single LoadBalancer exposed via minikube tunnel that redirects to a cluster node, and the cluster itself isn't accessible from outside (so the nodes can only talk to each other and the load balancer). Here's the commands I used:
Using redis-cli on the host with load balancer IP <IP_ADDRESS> like so:
redis-cli -c -h <IP_ADDRESS> -a $REDIS_PASSWORD CLUSTER NODES
Warning: Using a password with '-a' or '-u' option on the command line interface may not be safe.
aceb5bf17a706440a297c5be764f4e4b6a60eb61 <IP_ADDRESS>:6379@16379 slave 16da11b0423cafe75261b5adbc2eb13a90358cc5 0<PHONE_NUMBER>716 2 connected
a67bf5b0d784c9be05fba218bdc456b484f37c86 <IP_ADDRESS>:6379@16379 myself,slave 2008db068b8a58a28595b37060d52d3736d04a6d 0<PHONE_NUMBER>000 1 connected
a10e1fe9800e7fb2a376f5ec5e1734658b15c6c9 <IP_ADDRESS>:6379@16379 master - 0<PHONE_NUMBER>000 3 connected 10923-16383
2008db068b8a58a28595b37060d52d3736d04a6d <IP_ADDRESS>:6379@16379 master - 0<PHONE_NUMBER>000 1 connected 0-5460
53cf7c4159f5896deb1c42478c82a6404ac5f56e <IP_ADDRESS>:6379@16379 slave a10e1fe9800e7fb2a376f5ec5e1734658b15c6c9 0<PHONE_NUMBER>000 3 connected
16da11b0423cafe75261b5adbc2eb13a90358cc5 :0@0 master,noaddr -<PHONE_NUMBER>731<PHONE_NUMBER>730 2 disconnected 5461-10922

all works as expected.
Trying to connect to the same cluster with Fred (env variable REDIS_URI is the LoadBalancer IP):
let config = RedisConfig {
            server: ServerConfig::new_clustered([(dotenv!("REDIS_URI").to_string(), 6379 as u16)].to_vec()),
            fail_fast: true,
            pipeline: true,
            blocking: Blocking::Block,
            username: None,
            password: Some(dotenv!("REDIS_PASSWD").to_string()),
            tls: None,
            tracing: false
        };
        println!("Creating client...");
        let client = RedisClient::new(config);
        println!("Created client!");

        let policy = ReconnectPolicy::default();

        tokio::spawn(client
            .on_error()
            .for_each(|e| async move {
                println!("Client received connection error: {:?}", e);
            }));

        println!("Checked errors...");

        tokio::spawn(client
            .on_reconnect()
            .for_each(move |client| async move {
                println!("Client {} reconnected.", client.id());
                // select the database each time we connect or reconnect
                let _ = client.select(REDIS_SESSION_DB).await;
            }));

        println!("Checked reconnections...");

        client.connect(Some(policy));
        println!("Trying to connect Redis...");
        client.wait_for_connect().await.unwrap();
        println!("Redis connected!");

makes it throw this error:
Client received connection error: Redis Error - kind: IO, details: Os { code: 113, kind: HostUnreachable, message: "No route to host" }

Given that the info about nodes in cluster is gathered with CLUSTER NODES (per https://docs.rs/fred/latest/fred/types/enum.ServerConfig.html#variant.Clustered), I assume passing a single IP is fine.
I guess this is some kind of a DNS/redirect resolution problem. I see that you're currently working on supporting custom DNS resolvers on the client, could this be related?
Keep up the great work, this is probably the best Redis driver for Rust at the moment!
P.S. When do you plan to release Streams functionality by the way (in terms of time)?

Here's the commands and Helm .yaml file I used if you'd like to replicate my setup:
helm repo add bitnami https://charts.bitnami.com/bitnami
helm install redis-name -f redis.yaml bitnami/redis-cluster

redis.yaml

Hi @ConstBur, thanks for the kind words. In my last couple roles my team and I had to spend a lot of long nights fighting Elasticache and I'm hoping this library helps people avoid some of those issues.
Regarding the issue you mentioned - a couple things jump out at me.
Can you try enabling trace logs (RUST_LOG=fred=trace)? I'm particularly interested in either of the log lines in this block: https://github.com/aembke/fred.rs/blob/main/src/protocol/types.rs#L1719-L1738. There should be several of them in the logs, likely 1 + the number of main/primary cluster nodes.
Also, fred does a bit more than redis-cli when it sets up cluster connections. Once it reads the response to CLUSTER NODES it will try to connect to all of the primary/main cluster nodes in parallel, and that error could be coming from any of those connection attempts.
Here's what I suspect is happening.

REDIS_URI contains the 10.x address you showed above, which is reachable from outside minikube/virtualbox (where fred is running), and is likely the IP of virtualbox's network interface on the host.
Fred connects and runs CLUSTER NODES successfully on the node specified from REDIS_URI since that 10.x address is reachable from the host where fred is running.
The response from the server to the CLUSTER NODES command contains IP addresses for the other nodes, but where the IP in each line is the IP of the node inside virtualbox.
Fred fails connecting to the other cluster nodes and returns that error.

I've only ever seen minikube run with virtualbox, so I'm assuming that's how it's being done here, but if that's not the case this might not be correct. If that is the case though (or if your load balancer acts like virtualbox) then it's likely those <IP_ADDRESS>/8 addresses (from the CLUSTER NODES example) are only reachable from inside virtualbox (since virtualbox runs its own virtual network inside the guest machine), and they're being returned to fred (running outside virtualbox) - and fred can't reach them because it's not using the same network as the guest VM.
In terms of testing/fixing that... I don't have a great answer. I had a similar issue the other day when I switched to CircleCI from TravisCI. CircleCI runs remote docker engines with a different networking layer, and all my CI jobs starting failing on the sentinel tests because the sentinel servers were running on the remote docker engine. To fix that I had to move the tests inside docker so they could reach the IP addresses returned from the sentinel nodes inside docker, but otherwise there was no way to reach them. You might have to do something similar here (work outside minikube, but write a script to build and run inside minikube).
On the other hand, I can see this being a common issue with k8s and minikube becoming so popular, and while it might not be an issue in production (since presumably your Rust code would run in the cluster as well), it definitely seems like an issue with active development/testing.
I use minikube extensively in my current role and a lot of very smart people have built a ton of infrastructure to get around this issue, so I can say from experience that it's not easy. Redis is a particularly nasty example of this because of how it redirects clients around with IP addresses, and this implementation decision on Redis' part assumes a lot about the network layer and DNS layer on both the client and server. With modern container systems, or systems like minikube (or anything that does its own networking), a lot of these assumptions are just not reliable anymore.
I'll have to think on this a bit though since there doesn't seem to be an easy answer here. I'm torn between a new feature to disable auto-discovering the cluster nodes or some mechanism to allow callers to rewrite IP addresses (in this case rewriting the 172.x addresses with your 10.x address - which should fix this assuming the ports are different).
In terms of stream support - I'm looking to get that released in the next couple of weeks. I'm almost done with 5.0.0 (currently on the feat/resp3-support branch) and then streams are next up right after that. Version 5 is a major rewrite with traits instead of my unsustainable attempts to get by with Deref to dedup functionality, and it should set up a nice foundation for both low level X* command support and a higher level client that looks more like a Kafka client.

TLDR: I think the issue is due to the IP addresses from the CLUSTER NODES response only being reachable from inside minikube (where the cluster is running).
In terms of fixing or working around it (in order of complexity):

Switch to a centralized server instead of a cluster inside minikube (this is what we do at work)
Write a script such that you can work outside minikube but build and run inside minikube on demand. One of my coworkers did this and it was... not easy.
Do something fancy to map those <IP_ADDRESS>/8 addresses back to the minikube network interface (as seen by the host).
Change the load balancer to rewrite IP addresses. This is likely very complicated though and requires intelligent modifications to payloads in-flight. It also might not even work if ports collide in the CLUSTER NODES response.

In the meantime I'll look into a one-size-fits-all solution that can be added to Fred if possible, since this is probably a common issue.

Wow, that's a very detailed response, thank you very much!
I run minikube with Docker driver on Linux, but I guess that shouldn't matter for the network-related problems like this. Looks like your diagnosis is right, there seems to be no other reason why Fred can't connect to the cluster.
I've tried adding RUST_LOG=fred=trace to cargo run but strangely no tracing logs actually appeared. Maybe I did something wrong, still investigating...
I have a server that I can use for hosting Kubernetes, so I'll try setting that up in the meantime.
Should I leave this issue open until there's a solution found/README note written?

Oh that's good news if you're using the docker driver on linux. You have much more control over how the networking is set up in that case. You could probably dockerize the build command you use and everything would likely work (assuming you run the docker command with the same network as your minikube cluster).
Regarding the logs issue - try adding log and pretty_env_logger to your toml, then make sure you have pretty_env_logger::init() at the top of your main function.
I'll edit my comment to reflect the fact that you're using docker, since things are bit different in that case.
In the end though the general idea of using a central load balancer with redis tends not to work very well. Redis will tell clients to connect to specific IP addresses, and when you're using any form of a reverse proxy that tends not to work. Elasticache (the AWS managed Redis service) does quite a bit of work to make this smooth for callers, but from what I understand they had to customize both Redis and their load balancer to do what you're looking to do.

@ConstBur I wrote two docs that will probably help answer some of your questions. They're currently on the feat/resp3-support branch, but should be in main within a week or so.
https://github.com/aembke/fred.rs/blob/feat/resp3-support/FAQ.md
https://github.com/aembke/fred.rs/blob/feat/resp3-support/tests/minikube.md
Also, I just went ahead and did the streams interface with this next release, so that should be up on crates.io in the near future.

Holy crap, you explained everything like I'm 5 and in great detail at the same time! Alright, I'm definitely switching to a centralized server then since I can.
Logs now work, but not much interesting appears in them:
DEBUG fred::multiplexer::commands > fred-QI3tx0wN23: Initializing connections...
DEBUG fred::protocol::connection  > fred-QI3tx0wN23: Attempting to read cluster state from <IP_ADDRESS>:6379
TRACE fred::protocol::types       > fred-QI3tx0wN23: Using <IP_ADDRESS> among 1 possible socket addresses for <IP_ADDRESS>:6379
DEBUG fred::protocol::connection  > fred-QI3tx0wN23: Error creating connection to <IP_ADDRESS>:6379 => Redis Error - kind: IO, details: Os { code: 110, kind: TimedOut, message: "Connection timed out" }
DEBUG fred::multiplexer::utils    > fred-QI3tx0wN23: Emitting connect error: Redis Error - kind: Unknown, details: Could not read cluster state from any known node in the cluster.
DEBUG fred::multiplexer::utils    > fred-QI3tx0wN23: Emitting connect error: Redis Error - kind: Unknown, details: Could not read cluster state from any known node in the cluster.

I'll close this issue then, everything's clear now. Can't wait for the next release!
Thanks very much again for the docs and streams! :)


Mostly functioning sequence scraper

In this change, I added a little nodejs project which loops through a bunch of the sequence URLs, pulls their data, converts it to JSON, then writes them to a unique file in the src/main/webapp/sequences directory.
If you wanna try it yourself:

install nodejs

Then, in cygwin/terminal:

cd webscraping/node
npm install  [installs dependencies cheerio and request]
node driver.js  [runs scraper script]
checkout the src/main/webapp/sequences directory which will now contain all (48) of the scraped sequences
to check that it's working properly, you can compare SOEN-General-Coop.json with the old equivalent file: defaultSequence.json. They should be the same, semantically

quick disclaimer: this is not yet perfect.


CSP - style-src 'unsafe-inline' should not be required

Is there any possibility to add support for scrict csp scenarios?
The insertion of the inline style element into the header (https://github.com/kutlugsahin/smooth-dnd/blob/master/src/styles.ts) enforces me to enable style-src 'unsafe-inline' in my csp definition.
I tried to add the hash value of this element to the csp but this solution does not work in Firefox and Edge. It would be great if it wouldn't be necessary to add unsafe-inline to my csp.

@rogeru: I migrated to another dnd library

@daubli thanks for letting me know. Can I ask which library you migrated to?


Nonce generation

Multiply by 10 - Fixes different Time-zones issue

The nonce uses DateTime.UtcNow and should be unaffected by time zones. I'm worried that this is simply a hack to work around the underlying problem, which may re-appear. Is it possible to remove the * 10 and record your screen and debug through the code and post a video of the problem?

The first number has 19 digits, the second 18. Does this error happen if
you re-generate new API keys?
-- Jeff
On Wed, Mar 28, 2018 at 12:56 PM, Marco Carola<EMAIL_ADDRESS>wrote:

[image: image]
https://user-images.githubusercontent.com/6436248/38050207-23ba73fc-32c2-11e8-8310-d65eb2cebc14.png
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/jjxtra/ExchangeSharp/pull/79#issuecomment-376997886,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABNoGFKHnslvjIeKVi2RaCBVG3jHKGnnks5ti9zzgaJpZM4S-2KY
.

@jjxtra Thanks ! Is the above picture enough, or you really need a video ?

Picture is fine. Does it work if you generate new API keys?
-- Jeff
On Wed, Mar 28, 2018 at 1:29 PM, Marco Carola<EMAIL_ADDRESS>wrote:

@jjxtra https://github.com/jjxtra Thanks ! Is the above picture enough,
or you really need a video ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/jjxtra/ExchangeSharp/pull/79#issuecomment-377007470,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABNoGF2dB3zPm8J85IuUkgrKCnGZWURVks5ti-SggaJpZM4S-2KY
.

thanks @jjxtra ! It worked ! My guess is that somehow Keys generated before Summer time change (last sunday) might lead to wrong generation of bounces after that event. Does this make sense in your opinion ? :/ Take care !

I'm not sure this is the problem. I have API keys from several months ago
on Poloniex and they work fine.
-- Jeff
On Wed, Mar 28, 2018 at 2:18 PM, Marco Carola<EMAIL_ADDRESS>wrote:

thanks @jjxtra https://github.com/jjxtra ! It worked ! My guess is that
somehow Keys generated before Summer time change (last sunday) might lead
to wrong generation of bounces after that event. Does this make sense in
your opinion ? :/ Take care !
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/jjxtra/ExchangeSharp/pull/79#issuecomment-377021930,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABNoGOM-fQypmnXCt3bytrf9rvJfpS-Hks5ti-_5gaJpZM4S-2KY
.


⚠ ClamAV has degraded performance

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

HTTP code: 200
Response time: 497 ms

Resolved: ClamAV performance has improved in ef8971d after 10 minutes.


Duplicated InfiniteData for react-query v4 in infiniteQueries

What version of kubb is running?
No response
What platform is your computer?
No response
What version of external packages are you using(@tanstack-query, MSW, React, Vue, ...)
No response
What steps can reproduce the bug?

Open kubb example from site https://codesandbox.io/p/devbox/wispy-rgb-sgm8cw?embed=1
Find file useFindPetsByStatusHook.ts
Write on both of the file

type A = typeof useFindPetsByStatusHookInfinite<
  InfiniteData<FindPetsByStatus['response']>
>;

type B = ReturnType<A>;

type C = B['data'];

InfiniteData duplicates:

How often does this bug happen?
Every time
What is the expected behavior?
InfiniteData not duplicates
Swagger/OpenAPI file?
In sandbox
Additional information
I think problem with UseInfiniteQueryResult and TData = InfiniteData<FindPetsByStatus['response']>. Using both duplicates InfiniteData
try without InfiniteData:
type A = typeof useFindPetsByStatusHookInfinite<FindPetsByStatus['response']>;

type B = ReturnType<A>;

type C = B['data'];

Working fine!

KUB-10

@RabbitShare This has been resolved as part of Kubb v2.28.1


Directives support

Maybe need to handle @skip and @include as optional variables.

Done in 0.8.0 :)


Add way to track symbols with missing minutes

Some symbols have days but not minutes, track the last date with minutes to avoid hitting the endpoint getting empty results using up daily calls,

Dowlooader figures it out now.


ci: updated the package-lock.json to fix the audit failures

vulnerability report before the update is as follows

Project Name
Vulnerability Level
Description

@instana/core
None
No vulnerabilities found

@instana/serverless
None
No vulnerabilities found

@instana/autoprofile
None
No vulnerabilities found

@instana/opentelemetry-sampler
None
No vulnerabilities found

@instana/shared-metrics
Moderate
Denial of service while parsing a tar file due to lack of folders count validation - Details

@instana/azure-container-services
None
No vulnerabilities found

@instana/opentelemetry-exporter
None
No vulnerabilities found

@instana/aws-lambda
None
No vulnerabilities found

@instana/aws-fargate
None
No vulnerabilities found

instana-aws-lambda-auto-wrap
None
No vulnerabilities found

@instana/collector
None
No vulnerabilities found

@instana/google-cloud-run
None
No vulnerabilities found

@instana/metrics-util
None
No vulnerabilities found

There was a moderate severity vulnerability detected in "shared-metrics" related to tar package version 6.2.0, which could lead to denial of service due to insufficient validation of folder counts when parsing a tar file.

ci: updated the package-lock.json to fix the audit failures #1106

Please use fix(security). We can ship this this as a security bug fix.


add vGPU monitor container

related issue: #11
add vGPU monitor container to be able to collect metrics. Including:

HostCoreUtilization: host GPUs' utilization
HostGPUMemoryUsage: host GPUs' memory usage
vGPU_device_memory_limit_in_bytes: containers' GPU memory limits
vGPU_device_memory_usage_in_bytes: containers' GPU memory usage

/lgtm


Get prod ready devops 284

Apologies for these wayard PRs - I was not paying attention when creating them i our forked repo. Also, thanks for this. We are testing out for use, happy to contribute if needed just -> @aflansburg


Don't hardcode version in the install curl/wget instructions

changed to use master in path to install.sh instead a version number so that this command can be generic to get the latest master version of the install script

Master branch is not stable enough.

@Claire the hardcoded version number is extremely intentional; master is often broken. Sometimes I break it on purpose just to help make sure that nobody is consuming it directly.


step3

Hi:
I tried to run your DIC code based on Matlab using your sample data and it got warning in step3。
warning：Problem zipping [1] to [2] . Continuing without zipping
An undefined function or variable is found by looking at the function:'patchPathAngles'.
The result of 3D reconstruction is no  stitches.
I hope I can get your help?
Yours,
Sk Ma

Hi,
The sample data includes only 2 cameras (1 pair) which results in 1 surface, therefore you cannot stitch it to anything.
When you have your own data with more than 1 stereo pair you can try stitching, but this is not mandatory. You can always skip the stitching and continue to Step 4 to process the results.
I will add a clarification to emphasize that.
Thanks,
Dana

Hi，
I analyzed two 2DDIC results based on the samples you provided. During the stitching process, the overlapping part could be eliminated, but there would be a gap in the middle, which did not become a whole.
Could you please provide the code of "patchPathAngles" function in"[A]=patchPathAngles(F1,V1,ind1,isClosedLoop); "
Yours,
Sk Ma

I have added the missing function "patchPathAngles" to the library (it's under MultiDIC/lib_ext/GIBBON/lib/).
Please let me know if the issue has been resolved after that.


⚠ Bio Links has degraded performance

In 8f91979, Bio Links (https://bio.rheinklang.events/links) experienced degraded performance:

HTTP code: 200
Response time: 7640 ms

Resolved: Bio Links performance has improved in 2e9b6b9 after 38 minutes.


Upload on main folder not possible / sub folder working fine

My project has the following structure:

main folder
-- index.php

css folder
-- style.css

When changing and saving style.css the upload is working fine (1). Where else changing and saving index.php leads to an error (2) which I do not unterstand. Here are the logs for both cases:
(1)
[09-19 23:24:25] [debug] > PASV
[09-19 23:24:25] [debug] < '227 Entering Passive Mode (192,162,84,123,175,238).\r\n'
[09-19 23:24:25] [debug] > STOR css/style2.css
[09-19 23:24:25] [debug] < '150 Opening BINARY mode data connection for css/style2.css\r\n'
[09-19 23:24:25] [debug] < '226 Transfer complete\r\n'
[09-19 23:24:25] [debug] set remote time(local)<PHONE_NUMBER>000
[09-19 23:24:25] [debug] > MFMT<PHONE_NUMBER>2425 css/style.css
[09-19 23:24:25] [debug] < '213 Modify=20190919212425; css/style.css\r\n'
[09-19 23:24:25] [info] local ➞ remote c:\DEV\xxx\css\style.css
(2)
[09-19 23:25:24] [debug] > MKD .
[09-19 23:25:24] [debug] < '550 .: File already exists\r\n'
[09-19 23:25:24] [error] Error: .: File already exists
at v (c:\Users\xxx.vscode\extensions\liximomo.sftp-1.12.8-debug\dist\extension.js:70:110899)
at d. (c:\Users\xxx.vscode\extensions\liximomo.sftp-1.12.8-debug\dist\extension.js:70:111622)
at d.emit (events.js:182:13)
at d.module.exports.d._write (c:\Users\xxx.vscode\extensions\liximomo.sftp-1.12.8-debug\dist\extension.js:70:124444)
at doWrite (_stream_writable.js:410:12)
at writeOrBuffer (_stream_writable.js:394:5)
at d.Writable.write (_stream_writable.js:294:11)
at Socket.p (c:\Users\xxx.vscode\extensions\liximomo.sftp-1.12.8-debug\dist\extension.js:70:113993)
at Socket.emit (events.js:182:13)
at addChunk (_stream_readable.js:283:12)
at readableAddChunk (_stream_readable.js:264:11)
at Socket.Readable.push (_stream_readable.js:219:10)
at TCP.onStreamRead [as onread] (internal/stream_base_commons.js:94:17) download c:\DEV\xxx\test.php
For debug logging I used https://github.com/liximomo/vscode-sftp/tree/debug-pacakge
May be the error is in fornt of the screen. I don't get it. Thanks!

I need the full logs.

[09-20 08:19:20] [info] [file-save] c:\DEV\uploadtest\css\style.css
[09-20 08:19:20] [trace] handle upload file for c:\DEV\uploadtest\css\style.css
[09-20 08:19:20] [debug] > PASV
[09-20 08:19:20] [debug] < '227 Entering Passive Mode (192,162,84,123,175,220).\r\n'
[09-20 08:19:20] [debug] > LIST .
[09-20 08:19:20] [debug] < '150 Opening BINARY mode data connection for file list\r\n'
[09-20 08:19:20] [debug] < '226 Transfer complete\r\n'
[09-20 08:19:20] [debug] > PASV
[09-20 08:19:20] [debug] < '227 Entering Passive Mode (192,162,84,123,176,191).\r\n'
[09-20 08:19:20] [debug] > STOR css/style.css
[09-20 08:19:20] [debug] < '150 Opening BINARY mode data connection for css/style.css\r\n'
[09-20 08:19:20] [debug] < '226 Transfer complete\r\n'
[09-20 08:19:20] [debug] > MFMT<PHONE_NUMBER>1920 css/style.css
[09-20 08:19:20] [debug] < '213 Modify=20190920061920; css/style.css\r\n'
[09-20 08:19:20] [info] local ➞ remote c:\DEV\uploadtest\css\style.css
[09-20 08:19:33] [info] [file-save] c:\DEV\uploadtest\index.php
[09-20 08:19:33] [trace] handle upload file for c:\DEV\uploadtest\index.php
[09-20 08:19:33] [debug] > PASV
[09-20 08:19:33] [debug] < '227 Entering Passive Mode (192,162,84,123,176,146).\r\n'
[09-20 08:19:33] [debug] > LIST .
[09-20 08:19:33] [debug] < '150 Opening BINARY mode data connection for file list\r\n'
[09-20 08:19:33] [debug] < '226 Transfer complete\r\n'
[09-20 08:19:33] [debug] > MKD .
[09-20 08:19:33] [debug] < '550 .: The file already exists\r\n'
[09-20 08:19:33] [error] Error: .: The file already exists
at v (c:\Users\xxx.vscode\extensions\liximomo.sftp-1.12.9\dist\extension.js:70:110952)
at d. (c:\Users\xxx.vscode\extensions\liximomo.sftp-1.12.9\dist\extension.js:70:111675)
at d.emit (events.js:182:13)
at d.module.exports.d._write (c:\Users\xxx.vscode\extensions\liximomo.sftp-1.12.9\dist\extension.js:70:124497)
at doWrite (_stream_writable.js:410:12)
at writeOrBuffer (_stream_writable.js:394:5)
at d.Writable.write (_stream_writable.js:294:11)
at Socket.p (c:\Users\xxx.vscode\extensions\liximomo.sftp-1.12.9\dist\extension.js:70:114046)
at Socket.emit (events.js:182:13)
at addChunk (_stream_readable.js:283:12)
at readableAddChunk (_stream_readable.js:264:11)
at Socket.Readable.push (_stream_readable.js:219:10)
at TCP.onStreamRead [as onread] (internal/stream_base_commons.js:94:17) download c:\DEV\uploadtest\index.php

I mean all logs from the startup.

Final response: Seemed to have been a wrong configuration on my side. It's working now. Sorry for the circumstances :(


Fix checkbox initial values on group permission edit form on Django 1.10

Fixes #2962
Django 1.10 changed the internal representation of initial values of ModelChoiceFields; they are now model instances rather than IDs. This broke the format_permissions tag, which inspected the initial value of the field in order to reconstruct it as checkboxes. This internal poking-around is now avoided entirely, by setting GroupForm to use the CheckboxSelectMultiple widget itself; format_permissions simply has to reorganise those checkboxes appropriately, rather than building them from first principles.
IMPORTANT: The new form rendering relies on the plain-checkbox-label style added in a0efc0d10e176b52822376a7ff78ff5a0c61b90d. When backporting to stable/1.6.x, the CSS rule from there will need to be added to _forms.scss.

I've tested it on Django 1.10 and 1.9.9 version and on our master and stable/1.6 branches. Looks good to me!
Merged into:

master in 8a41baa87d79afe58f33394656dbc8b7fc8fd858 (release notes) + 49dae4ee10b05bebcf3def98e66b248f380f3260
stable/1.6 in 8dad5047c752edda556a591ee6c612691140cec0 (release notes) + d195bd3e261c97e6d5341de914595376d19bc011 (styles) + 7b5d7c8bc46c8713bcfce7c296113865060395b8

Thanks!


Variable explorer not opening pandas dataframe when using spyder-kernels in virtual environment

Description
What steps will reproduce the problem?

import pandas as pd
df = pd.DataFrame({"a":range(10),"b":range(10)})

Try to open df by double clicking on the DataFrame in the variable explorer.
This was previously working fine. I believe that a recent install of spyder-kernels to my virtual environment caused this problem, but I'm not sure how.
To avoid having to install spyder in every virtual environment I works with, I just install spyder-kernels in the venv, launch spyder from my base environment, and point the python interpreter to the python instance inside my venv. This process has been working fine, until I just had to a create a new venv for a project.  I repeated this process and am now getting this error.
This only happens when the python interpreter is pointing to my venv interpreter, not base spyder.
Quick googling seems like this may be related to incompatible versions of ipykernel and spyder-kernels (?)
https://github.com/python-poetry/poetry/issues/2133
-version of spyder-kernels = 1.9.3
-version of ipykernel: 5.3.4, which was installed with spyder-kernels
Traceback
  File "/Users/lmariano/.pyenv/versions/3.7.7/lib/python3.7/site-packages/pandas/core/generic.py", line 5272, in __getattr__
    if self._info_axis._can_hold_identifiers_and_holds_name(name):
  File "/Users/lmariano/.pyenv/versions/3.7.7/lib/python3.7/site-packages/pandas/core/generic.py", line 5272, in __getattr__
    if self._info_axis._can_hold_identifiers_and_holds_name(name):
  File "/Users/lmariano/.pyenv/versions/3.7.7/lib/python3.7/site-packages/pandas/core/generic.py", line 5272, in __getattr__
    if self._info_axis._can_hold_identifiers_and_holds_name(name):
  [Previous line repeated 993 more times]
  File "/Users/lmariano/.pyenv/versions/3.7.7/lib/python3.7/site-packages/pandas/core/generic.py", line 493, in _info_axis
    return getattr(self, self._info_axis_name)
  File "/Users/lmariano/.pyenv/versions/3.7.7/lib/python3.7/site-packages/pandas/core/generic.py", line 5270, in __getattr__
    return object.__getattribute__(self, name)
  File "pandas/_libs/properties.pyx", line 63, in pandas._libs.properties.AxisProperty.__get__
  File "/Users/lmariano/.pyenv/versions/3.7.7/lib/python3.7/site-packages/pandas/core/generic.py", line 5270, in __getattr__
    return object.__getattribute__(self, name)
RecursionError: maximum recursion depth exceeded while calling a Python object

Versions

Spyder version: 4.1.4
Python version: 3.7.7
Qt version: 5.12.9
PyQt5 version: 5.12.3
Operating System: Darwin 19.6.0

Dependencies

# Mandatory:
applaunchservices >=0.1.7      :  0.2.1 (OK)
atomicwrites >=1.2.0           :  1.4.0 (OK)
chardet >=2.0.0                :  3.0.4 (OK)
cloudpickle >=0.5.0            :  1.5.0 (OK)
diff_match_patch >=20181111    :  20200713 (OK)
intervaltree                   :  None (OK)
IPython >=4.0                  :  7.16.1 (OK)
jedi =0.17.1                   :  0.17.1 (OK)
nbconvert >=4.0                :  5.6.1 (OK)
numpydoc >=0.6.0               :  1.1.0 (OK)
parso =0.7.0                   :  0.7.0 (OK)
pexpect >=4.4.0                :  4.8.0 (OK)
pickleshare >=0.4              :  0.7.5 (OK)
psutil >=5.3                   :  5.7.2 (OK)
pygments >=2.0                 :  2.6.1 (OK)
pylint >=1.0                   :  2.5.3 (OK)
pyls >=0.34.0;<1.0.0           :  0.34.1 (OK)
qdarkstyle >=2.8               :  2.8.1 (OK)
qtawesome >=0.5.7              :  0.7.2 (OK)
qtconsole >=4.6.0              :  4.7.5 (OK)
qtpy >=1.5.0                   :  1.9.0 (OK)
sphinx >=0.6.6                 :  3.1.2 (OK)
spyder_kernels >=1.9.2;<1.10.0 :  1.9.2 (OK)
watchdog                       :  None (OK)
zmq >=17                       :  19.0.1 (OK)

# Optional:
cython >=0.21                  :  None (OK)
matplotlib >=2.0.0             :  None (OK)
numpy >=1.7                    :  1.19.0 (OK)
pandas >=0.13.1                :  1.0.5 (OK)
scipy >=0.17.0                 :  1.5.1 (OK)
sympy >=0.7.3                  :  None (OK)

I believe that I solved this problem:
The problem is that spyder-kernels seems to not be compatible with the latest version of cloudpickle, which is 1.5.0, released Jul 1, 2020.
I reverted back to the previous version, 1.4.1, and the variable explorer now works as expects.

I believe that I identified the source of the problem.
I think that the latest version of spyder-kernels is not compatible with the latest version of pandas. The latest version of pandas is 1.1.1, but I also encounter this error using 1.1.0 - The most up-to-date version of pandas that does not cause this problem is 1.0.5.

Hi @laurajanem,
So you could fix your problem by upgrading pandas to 1.1.1? I'm not encountering this error in 1.0.5

Yes, but the issue is that both the .venv I'm working in, where I have
installed spyder-kernels and the base spyder environment have to have
matching pandas versions, or at least compatible versions. I did a fresh
install of spyder today, just to see if there was something wrong there,
and it auto-installs with pandas 1.0.5.
It's definitely a hazard of trying to get around having to do the full
Spyder install in every single venv I am working on - by only installing
spyder-kernels in the .venv and opening Spyder in a different
environment, I know I'm asking for trouble, but this stumped me for awhile.
I'd love for there to be a way to not have to do this at all.
On Mon, Aug 24, 2020 at 4:13 PM Stephannie Jimenez Gacha <
<EMAIL_ADDRESS>wrote:

Hi @laurajanem https://github.com/laurajanem,
So you could fix your problem by upgrading pandas to 1.1.1? I'm not
encountering this error in 1.0.5
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/spyder-ide/spyder/issues/13620#issuecomment-679341651,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEFQKPLDGYR4FEU2X45Y5W3SCLCV3ANCNFSM4QJWOKHA
.

We are currently working on Spyder installers, to avoid this type of errors. As your error is already fixed I will go ahead and close this issue.
Thanks for reporting!

@laurajanem, thanks for reporting. I think this is a serious issue.
@steff456, even with the installers, people can create a new environment with an unmatching Pandas version and connect Spyder to it. So I think we need to look further at this problem.
Were you able to reproduce it following @laurajanem instructions?

Downgrading spyder-kernels to 1.9.1 and pandas to 1.0.5 solved it for me.

@jafetgado, thanks for the feedback. However, I think this is not an issue with spyder-kernels but it's caused a mismatch between the Pandas version used in Spyder and the one used by the kernel.

@ccordoba12 I was able to reproduce this error by creating a new environment with the latest version of pandas

@steff456, please use cloudpickle to serialize a dataframe with Pandas 1.1.1 and try to deserialize it with Pandas 1.0.5 to see if you get the same error. Examples of how to do that can be found here
https://github.com/cloudpipe/cloudpickle#examples
That's basically what we do when asking the kernel to send us a value to display it in our dataframe viewer.
If you're able to do that, we could report the problem to the Pandas team in a way that doesn't depend on Spyder, to see if they can fix it.

@ccordoba12 if I have my spyder environment with pandas 1.1.1 and connect it to a kernel with pandas 1.0.5 it works as expected and the error doesn't exist. I think we need to bump our version of pandas for avoiding this error and we can report this problem to pandas so they can be aware of this behavior.

I agree, thanks for your help @steff456!


allow for merge config during copying

I like to add some config values during the snaketool config step

Thank you so much for the contribution!


Use Flate2 for encoding

Thus uses flat2 for encoding instead of the deflate crate.
Since flat2 defaults to using miniz_oxide, this shares the same underlying compression library as the decoding.
See issue #242
I'm not sure this is the right solution, and it does not full handle all the compression options (Huffman and Rle just use "fast" mode).

In fact, this change actually allows us to add a plaintext compression level because flate2 does support it!

Looks okay. I don't particularly like the deprecation but it seems harmless enough. (Note: if we had a compression level 'plaintext'—or as deflate calls it's unimplemented option: _ForceStored—and this would have removed it, I would have vetoed; but alas, we do not). Definitely a maintenance win.

If there is a need for RLE and huffman only it should be pretty easy to add support for it to flate2 as it's already supported by the back-ends I think. (RLE maybe via a window size 1 if there is no explicit option for it). Not sure where one would want to use the huffman only variant though, it doesn't have much purpose, RLE may have a slight use for compression speed I suppose.

Don't feel compelled to do so based on this singular data point, I don't quite see their purpose either. No users wants RLE-only (unless they targeted non-compliant decoders for some reason?)—they want speed. If anything then the encoder should just switch to rle-only based on the speed setting. If it's actually so much faster.

The fastest approach is probably going to be fpnge's strategy of using specially constructed Huffman tables so that the resulting codes are conducive to vectorized encoding. However, it does bake in some assumptions about the kind of filters that PNG uses, so it might not be suited to a generic compression library.


SwiftPM dependency management

For usage with SwiftPM, I found that the package dependencies directly references RxSwift and ReactiveSwift even though we don't use the reactive extensions.
I wonder if there is any way to remove these dependencies and add them just in need?

Maybe similar to: https://github.com/Moya/Moya/issues/2214


Paginator component

Paginator component

I didn't really see an easy way to add to this PR without creating a new branch and a PR from that branch so #8 closes this one as well. However, your component is merged in! Thank you for the help!


[Jolla phone] Back button does not work when accessing the verion information

I use a Jolla phone, I can use both SailfishOS and Android apps.
When I searched the Andstatus version I was using I tried to leave the page.
Impossible, neither Gesture based commands nor pushing the arrow back button would
let me go back, so I had to Force close the App and reopen it.

version v.17.0 (124)

Reading the article I would say that if this is the biggest problem then AndStatus is compatible with Jolla phone :-)

Please provide a screenshot where you have the crash.
Does the window asking you to send crash report to AndStatus team, opens after a crash?

There is no specific error message it just showed the information of the version of AndStatus but nothing else.
I have not seen any window asking me to send crash report yet. It simply gives you two options: Wait or Close Andstatus.

I would like to see how that screen looks on your phone.
Try different options,  maybe you will be able to send crash report... although I don't think that I will be able to fix the problem. But maybe somebody else, who has this device...

Now that I have wifi I am going to download a screenshot app for Jolla. right now I am unable to use Twitter in Andstatus. Gnusocial.de loads fine. Let me take the screenshots for you. Just cradhed again but no crash report. Is there a way to force a crash report if it does not show up automatically?

Aha, so now I got this:

Timeline loads Ok for Gnusocial.de
Timeline for Twitter loads also, but when we see Twitter timeline at some point (when, please describe!)  AndStatus freezes
Please note that this is not crash but freeze. I think this is why you don't get any crash notification.

What should I do when my only interaction with AndStatus is freezing? :(

@SebasFC Can you use PC to capture Android logs to figure out at which operation the freeze occurs?

Some clues for those who will decide to investigate this compatibility problem.

AndStatus actively uses multithreading and the fact that Android supports multitasking.
This didn't produce any problems on Android devices so far.
The only weak place is access to a database: it doesn't handle concurrent requests good enough. This is why (almost?) all database requests are asynchronous (I.e. in separate threads)
One may decrease probability of freezes by disabling AndStatus sync in a background  (Turn off "Sync while using AndStatus" option)


[W10H01] Add TrialOfTheDreamsTest

This tests the class TrialOfTheDreams.java
It uses a SecureRandom to create a random byte[] and tests if student's submession will find it. It takes time limit into account.

At this point you could just use a fixed byte[]

At this point you could just use a fixed byte[]

Originally the idea was to be able to test with differenet lengths of byte[] :P

Then do that. Just don't set the seed inside the byte[] generator and use a RepeatedTest

@HasanAjami does it compile right now? If so I'll check it out and approve for now.

@HasanAjami does it compile right now? If so I'll check it out and approve for now.

yesss it should be working well. Thank you for reviewing <3


Cleanup old Flutter recipes

There's been some refactors to the recipes where old infra configs are no longer used. We should remove these to cleanup the codebase.

https://flutter-review.googlesource.com/c/infra/+/15262
https://flutter-review.googlesource.com/c/infra/+/15261
https://flutter-review.googlesource.com/c/infra/+/15263
https://flutter-review.googlesource.com/c/recipes/+/15280


Resolve statsd ip on boot

this will prevent a dns lookup per metric

Decided to do this upstream in https://github.com/github/statsd-ruby/pull/11. Will update the existing :git dependency in here.


Add support for uploading CareSens meters via USB cable (UPLOAD-315)

Addresses:

UPLOAD-315

Ticket has been approved, so test suffixes have been removed. Ready for final check.


Add information about DEVELOPER_ERROR

This seems to be quite common error if you've misconfigured your Android app.

Thanks! I've added a nit review.

Nevermind, I've made the change myself. Thanks again :)

Thanks! :)


Licensing Section is incorrect

When working with Microsoft support, we found out that having the content in a workspace that's in a Power BI Premium capacity was insufficient. If you have the "install app automatically" box checked, you ALSO have to make sure that all viewers have the "Power BI (free)" license. Otherwise they will see the "This content isn't available" screen.
See also this thread: https://community.powerbi.com/t5/Service/Power-BI-Premium-Embed-SharePoint-Online/td-p/230064

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

ID: 0fc5abbd-e082-d1e1-109d-6f6cec8854a1
Version Independent ID: f8affce3-98f2-0cc6-b4de-d9af7ced0fbe
Content: Embed with report web part in SharePoint Online - Power BI
Content Source: powerbi-docs/service-embed-report-spo.md
Service: powerbi
GitHub Login: @markingmyname
Microsoft Alias: maghan

Thanks for your comment, @dejadee. We’ve forwarded your feedback to the writer, who should respond to this thread.

@dejadee Thank you for your feedback! We will investigate and get back to you with the relevant info.

@dejadee,
sorry for the delayed response.
does this note that is already in the article, not suffice?

@markingmyname,
The note is sort of misleading. In the scenario I've outlined in my original comment--Power BI Premium capacity workspace, "install app automatically" is checked--if a user does not have a Power Bi (free) license, but is given a link to the Power BI app then upon logging into Power BI, they are automatically assigned a Power BI (free) license so they can view the app without any issues. So the user "has access to the Power BI app."
But suppose that same user didn't click on the link directly to the Power BI app (or another user in the same group that the app is shared with). Suppose they are trying to view the app report which is embedded in SharePoint. In this scenario, they will NOT be automatically assigned a Power BI license. So they get a "this content isn't unavailable" error. That is, until an administrator manually assigns them a Power BI (free) license. Because this is a manual step that has to happen for the functionality described in the article, I think it should be added to the list of steps in the "Grant access to reports" section. Or at least in the "Known issues and limitations" section.

@dejadee
Thank you for clarifying that in more details.
I am in current discussions about this scenario.  Once I have an update I will let you know.
Again, thank you for bringing this to our attention.

Hi @dejadee,
I wanted to inform you that there will be no changes made to the article at this time.
the information is clear that you have to have access to both Power BI and SP to access the app.
If you feel this needs more clarification from the Product Group, please select the Product issue button.
Thank you.

We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion, and we will reopen the issue.


Hide the cursor

This project is very nice, and it has replaced less in my daily use, many thanks!
There's a minor thing that bothers me: what's the use of the cursor in a pager? It'd be nice to be able to hide it... Does this sound like something doable?

I grew fond of the cursor to select text, so I'm closing this.


text format serialization and deserialization

text format is very useful for debugging, or for cross language, human readable,, type safe, configuration files:
https://developers.google.com/protocol-buffers/docs/reference/cpp/google.protobuf.text_format
example of text format
https://github.com/BVLC/caffe/blob/master/models/bvlc_reference_caffenet/solver.prototxt
usage
let message = newTest1()
message.a = 150

## serialize
let data = protoToText(message)
echo data # a : 150
echo message # would use `$` as alias to serializeText

## deserialize
let message2 = Test1.deserializeText(data)
assert message2 == message

## serialize with option
let data = serializeText(message, oneline = false)

WORKAROUND
same as https://github.com/msoucy/dproto/issues/71#issuecomment-365172146 : shell out to protoc eg:
## serializeText
serialize message to /tmp/z01.pb
protoc --decode=Test1 --proto_path=tests/t29_nimpb/ tests/t29_nimpb/test1.proto < /tmp/z01.pb > /tmp/z01.txt
read /tmp/z01.txt

## deserializeText
TODO

workaround is not great, as not as efficient, and requires passing the proto file; the proper solution should involve using reflection

This could be a nice addition. Need to take a look at some point.


Updates README with echo

At first I thought this package only covered gin because thats all the README talks about; however, it also has echoaudit

my commit is signed?
https://github.com/metal-toolbox/auditevent/pull/233/commits/808bca7604757bc7f9852366df08aa029f681d2e

	* failed to parse signature: asn1: structure error: tags don't match (16 vs {class:0 tag:13 length:77 isCompound:true}) {optional:false explicit:false application:false private:false defaultValue:<nil> tag:<nil> stringType:0 timeType:0 set:false omitEmpty:false} ContentInfo @2

🥇

Closing after spending like 30 minutes trying to correctly setup PGP and failing.


Unhandled Exception under Xamarin.iOS

I'm using your latest version of this plugin and under iOS I don't get it to work. It always throws an unhandled exception, which I can't catch, without any information.
I'm running Xamarin.Forms 1.3.1 in the TestApplication I made to show the problem.
In this code it doesn't even execute the button clicked event. Am I doing something wrong?
I noticed, that when I install the plugin via nuget package manager, in the iOS project the wrong Toast.Forms.Plugin.Abstractions.dll gets referenced (its referencing the pcl version) and the Toast.Forms.Plugin.iOS.dll is not referenced at all. So I added them by myself. May this be the problem?
AppDelegate.cs

using Foundation;
using Toasts.Forms.Plugin.iOS;
using UIKit;

namespace XFTest.iOS
{
    [Register("AppDelegate")]
    public partial class AppDelegate : global::Xamarin.Forms.Platform.iOS.FormsApplicationDelegate
    {
        public override bool FinishedLaunching(UIApplication app, NSDictionary options)
        {
            global::Xamarin.Forms.Forms.Init();
            ToastNotificatorImplementation.Init();
            LoadApplication(new App());

            return base.FinishedLaunching(app, options);
        }
    }
}

App.cs

using Xamarin.Forms;

namespace XFTest
{
    public class App : Application
    {
        public App()
        {
            // The root page of your application
            MainPage = new TestPage();
        }
    }
}

TestPage.cs

using Toasts.Forms.Plugin.Abstractions;
using Xamarin.Forms;

namespace XFTest
{
    public class TestPage : ContentPage
    {
        public TestPage()
        {
            var layout = new StackLayout();

            var button = new Button
            {
                Text = "Notifier"
            };
            button.Clicked += ButtonOnClicked;

            layout.Children.Add(button);

            Content = layout;
        }

        private async void ButtonOnClicked(object sender, EventArgs eventArgs)
        {
            var notifier = DependencyService.Get<IToastNotificator>();

            bool tapped = await notifier.Notify(ToastNotificationType.Info, "Test", "test", TimeSpan.FromSeconds(5));
        }
    }
}

///Edit: I installed it with the console and now I get this exception:
System.NotImplementedException: The requested feature is not implemented
The Toasts.Forms.Plugin.Abstractions.dll is referenced wrong again. It's the PCL profile one. Not the Monotouch10.
///Edit2: When I add the correct references the DependecyService.Get is working. But when I try to display an toast notification I get an Unhandled.Exception of type System.NullReferenceExcpetion: Object reference not set to an instance of an object

seems like incorrect nuget package, it doesn't add a reference to Toasts.Forms.Plugin.iOS.dll for ios project. I'll release <IP_ADDRESS> once I find the reason why.

@EgorBo I tested <IP_ADDRESS> and in my Test Project it works. I'm gonna test it in my actual application now

@De4th69 there is already <IP_ADDRESS> with small fix for ios (in some cases description may disappear)


S3 Scan Source partition supplier creates partitions in memory and a failure causes no partitions to be created

Is your feature request related to a problem? Please describe.
As a user of s3 scan, I have a bucket with 100 million objects. The current s3 scan source is not able to handle this many objects, as it is bottlenecked by returning all objects as a list of partitions in the supplier, which can lead to out of memory errors. Additionally, if there are any failures in s3 scan supplier, no partitions will get created because all partitions are returned from the supplier before they are created in the coordination store.
Describe the solution you'd like
I would like the PartitionSupplier functions to be able to pass partitions back to the source coordinator for creation. So as objects are found during a scan, instead of holding them all in memory, the call to create the partition would be made right after the object is found from scanning.
Describe alternatives you've considered (Optional)
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

@graytaylor0 , Are you planning on working this?

@dlvenable I am not planning on working this right now

Encountered what I think to be this issue, would there be logs available in the CloudWatch logs to verify if I'm falling into this situation?


Missing index actions

https://github.com/obsidiansystems/beam-automigrate/blob/93f86a29b81150ac356107b82225ac7f151d6e51/src/Database/Beam/AutoMigrate/Types.hs#L213 does not currently represent creating/dropping an index (though it does for constraints)

I ended up getting confused as to how to properly do this as well. I tried a couple of different things, including somehow tracking migrations in the same way beam-migrate, but at the end of it, I used the following snippet and manually added indices after running any automatically created migrations:
createIndex
  :: forall be db tbl ty
   . Beamable tbl
  => DatabaseEntity be db (TableEntity tbl)
  -> (TableSettings tbl -> TableField tbl ty)
  -> PgCommandSyntax
createIndex table column =
  let tName = table ^. dbEntityDescriptor . dbEntityName
      settings = dbTableSettings $ table ^. dbEntityDescriptor
      cName = column settings ^. fieldName
   in PgCommandSyntax PgCommandTypeDdl $ emit $ T.encodeUtf8
        ( "CREATE INDEX IF NOT EXISTS " <> sqlEscaped (tName <> "_" <> cName) <>
          " ON " <> sqlEscaped tName <> " (" <> sqlEscaped cName <> ");\n"
        )

Doesn't feel like the right solution but a potential workaround until something better makes its way upstream?


Fixed some things

Fixed the link for info in the embed and automatically add applications.commands scope to a bot so ppl dont have to send the invite link with applications.commands scope

So how long will it take until Dan will merge it


Add test for getter syntax

These maybe unneeded given the Lens test but I though it would be nice to have them

Good idea.


Tipbot becomes unable to sort after a while

@tipbot balance
13000
@tipboth rank
.....          2000
....           1500
....
This is after quite a bit of tipping back and forth.

We ran into this problem too. Fixed in #8

Fixed via @heythisisnate 's commit. Thx!


Some of the UI cypress tests fail occasionally

I think these failures are due to the page not loading fast enough. We should see if mocha/cypress has a timeout/wait option or retry option.

@agduncan94 makes sense, could you add an example or two of the kind of error that shows up so we can recognize/search for it when it occurs?

https://travis-ci.org/ga4gh/dockstore-ui/jobs/183375643

  1) Dockstore Tool Details Change tab to labels:

     CypressError: Timed out retrying: cy.click() failed because this element is not visible:

...

This element is not visible because it's parent:
 has CSS property: 'display: none'

Fix this problem, or use {force: true} to disable error checking.

https://on.cypress.io/element-cannot-be-interacted-with

      at Object.cypressErr (http://localhost:9000/__cypress/static/js/cypress.js:5712:15)

      at Object.throwErr (http://localhost:9000/__cypress/static/js/cypress.js:5677:22)

      at Object.throwErrByPath (http://localhost:9000/__cypress/static/js/cypress.js:5704:21)

      at $Cy._retry (http://localhost:9000/__cypress/static/js/cypress.js:6635:26)

      at getCoords (http://localhost:9000/__cypress/static/js/cypress.js:7397:34)

      at $Cy.retry (http://localhost:9000/__cypress/static/js/cypress.js:7388:26)

      at http://localhost:9000/__cypress/static/js/cypress.js:6647:23

      at tryCatcher (http://localhost:9000/__cypress/static/js/vendor.js:42844:31)

      at Promise._settlePromiseFromHandler (http://localhost:9000/__cypress/static/js/vendor.js:40979:31)

      at Promise._settlePromiseAt (http://localhost:9000/__cypress/static/js/vendor.js:41055:18)

      at Promise._settlePromises (http://localhost:9000/__cypress/static/js/vendor.js:41171:14)

      at Async._drainQueue (http://localhost:9000/__cypress/static/js/vendor.js:38538:16)

      at Async._drainQueues (http://localhost:9000/__cypress/static/js/vendor.js:38548:10)

      at MutationObserver.Async.drainQueues (http://localhost:9000/__cypress/static/js/vendor.js:38376:14)

  2) Dockstore Tool Details Change tab to versions:

     CypressError: Timed out retrying: cy.click() failed because this element is not visible:

...

This element is not visible because it's parent:
 has CSS property: 'display: none'

Fix this problem, or use {force: true} to disable error checking.

https://on.cypress.io/element-cannot-be-interacted-with

      at Object.cypressErr (http://localhost:9000/__cypress/static/js/cypress.js:5712:15)

      at Object.throwErr (http://localhost:9000/__cypress/static/js/cypress.js:5677:22)

      at Object.throwErrByPath (http://localhost:9000/__cypress/static/js/cypress.js:5704:21)

      at $Cy._retry (http://localhost:9000/__cypress/static/js/cypress.js:6635:26)

      at getCoords (http://localhost:9000/__cypress/static/js/cypress.js:7397:34)

      at $Cy.retry (http://localhost:9000/__cypress/static/js/cypress.js:7388:26)

      at http://localhost:9000/__cypress/static/js/cypress.js:6647:23

      at tryCatcher (http://localhost:9000/__cypress/static/js/vendor.js:42844:31)

      at Promise._settlePromiseFromHandler (http://localhost:9000/__cypress/static/js/vendor.js:40979:31)

      at Promise._settlePromiseAt (http://localhost:9000/__cypress/static/js/vendor.js:41055:18)

      at Promise._settlePromises (http://localhost:9000/__cypress/static/js/vendor.js:41171:14)

      at Async._drainQueue (http://localhost:9000/__cypress/static/js/vendor.js:38538:16)

      at Async._drainQueues (http://localhost:9000/__cypress/static/js/vendor.js:38548:10)

      at MutationObserver.Async.drainQueues (http://localhost:9000/__cypress/static/js/vendor.js:38376:14)

  3) Dockstore Tool Details Change tab to files "before each" hook for "Should have Dockerfile tab selected":

     CypressError: Timed out retrying: cy.click() failed because this element is not visible:

...

This element is not visible because it's parent:
 has CSS property: 'display: none'

Fix this problem, or use {force: true} to disable error checking.

https://on.cypress.io/element-cannot-be-interacted-with

Because this error occured during a 'before each' hook we are skipping the remaining tests in the current suite: 'Change tab to files'

      at Object.cypressErr (http://localhost:9000/__cypress/static/js/cypress.js:5712:15)

      at Object.throwErr (http://localhost:9000/__cypress/static/js/cypress.js:5677:22)

      at Object.throwErrByPath (http://localhost:9000/__cypress/static/js/cypress.js:5704:21)

      at $Cy._retry (http://localhost:9000/__cypress/static/js/cypress.js:6635:26)

      at getCoords (http://localhost:9000/__cypress/static/js/cypress.js:7397:34)

      at $Cy.retry (http://localhost:9000/__cypress/static/js/cypress.js:7388:26)

      at http://localhost:9000/__cypress/static/js/cypress.js:6647:23

      at tryCatcher (http://localhost:9000/__cypress/static/js/vendor.js:42844:31)

      at Promise._settlePromiseFromHandler (http://localhost:9000/__cypress/static/js/vendor.js:40979:31)

      at Promise._settlePromiseAt (http://localhost:9000/__cypress/static/js/vendor.js:41055:18)

      at Promise._settlePromises (http://localhost:9000/__cypress/static/js/vendor.js:41171:14)

      at Async._drainQueue (http://localhost:9000/__cypress/static/js/vendor.js:38538:16)

      at Async._drainQueues (http://localhost:9000/__cypress/static/js/vendor.js:38548:10)

      at MutationObserver.Async.drainQueues (http://localhost:9000/__cypress/static/js/vendor.js:38376:14)

  4) Dockstore tool search page Select a tool Should have two tools (and a hidden row):

     CypressError: Timed out retrying: Not enough elements found. Found '2', expected '3'.

      at Object.cypressErr (http://localhost:9000/__cypress/static/js/cypress.js:5712:15)

      at Object.throwErr (http://localhost:9000/__cypress/static/js/cypress.js:5677:22)

      at Object.throwErrByPath (http://localhost:9000/__cypress/static/js/cypress.js:5704:21)

      at $Cy._retry (http://localhost:9000/__cypress/static/js/cypress.js:6635:26)

      at http://localhost:9000/__cypress/static/js/cypress.js:8769:28

      at tryCatcher (http://localhost:9000/__cypress/static/js/vendor.js:42844:31)

      at Promise._settlePromiseFromHandler (http://localhost:9000/__cypress/static/js/vendor.js:40979:31)

      at Promise._settlePromiseAt (http://localhost:9000/__cypress/static/js/vendor.js:41055:18)

      at Promise._settlePromises (http://localhost:9000/__cypress/static/js/vendor.js:41171:14)

      at Async._drainQueue (http://localhost:9000/__cypress/static/js/vendor.js:38538:16)

      at Async._drainQueues (http://localhost:9000/__cypress/static/js/vendor.js:38548:10)

      at MutationObserver.Async.drainQueues (http://localhost:9000/__cypress/static/js/vendor.js:38376:14)

  5) Dockstore tool search page Select a tool Select dockstore-tool-imports:

     CypressError: Timed out retrying: expected '
' to contain 'quay.io/dockstoretestuser2/dockstore-tool-imports '

      at Object.cypressErr (http://localhost:9000/__cypress/static/js/cypress.js:5712:15)

      at Object.throwErr (http://localhost:9000/__cypress/static/js/cypress.js:5677:22)

      at Object.throwErrByPath (http://localhost:9000/__cypress/static/js/cypress.js:5704:21)

      at $Cy._retry (http://localhost:9000/__cypress/static/js/cypress.js:6635:26)

      at http://localhost:9000/__cypress/static/js/cypress.js:8769:28

      at tryCatcher (http://localhost:9000/__cypress/static/js/vendor.js:42844:31)

      at Promise._settlePromiseFromHandler (http://localhost:9000/__cypress/static/js/vendor.js:40979:31)

      at Promise._settlePromiseAt (http://localhost:9000/__cypress/static/js/vendor.js:41055:18)

      at Promise._settlePromises (http://localhost:9000/__cypress/static/js/vendor.js:41171:14)

      at Async._drainQueue (http://localhost:9000/__cypress/static/js/vendor.js:38538:16)

      at Async._drainQueues (http://localhost:9000/__cypress/static/js/vendor.js:38548:10)

      at MutationObserver.Async.drainQueues (http://localhost:9000/__cypress/static/js/vendor.js:38376:14)

Still a thing? Otherwise, close

I think this is from UI1 so I don't think it is an issue.


ensureIndex(Whatever::someField) works incorrect with kotlin.serialization

Hello!
This code:
@Serializable
data class Whatever(
    @SerialName("some_field")
    val someField: String
)

val collection: CoroutineCollection<Whatever> = database.collection<Whatever>()

collection.ensureIndex(Whatever::someField)

Creates the index for someField, not for some_field.
Am I doing anything wrong? 🙂
The only one dependency is
implementation("org.litote.kmongo:kmongo-coroutine-serialization:4.1.2")

Upgrade to kmongo 4.1.3: it should work. Or, if you need to stay with 4.1.2, annotate someField with @MongoProperty("some_field")  (see https://github.com/Litote/kmongo/issues/224 for an explanation of the issue)

Thanks for the answer 🙂


Supported RESP Commands Info

Restructuring RespCommandInfo to read supported RESP commands info from JSON file (Garnet.server/Resp/RespCommandsInfo.json)
Adding support for specifying command info when registering custom commands (example implemented in GarnetServer, parsing custom command info from GarnetServer/CustomRespCommandsInfo.json)
Implementing COMMAND, COMMAND INFO & COMMAND COUNT RESP commands, matching information returned with Redis
Implementing serialization & deserialization of command info to/from JSON and to/from RESP
Adding CommandInfoUpdater tool for easily adding / removing supported commands & sub-commands info, generating an updated JSON file to replace RespCommandsInfo.json
Adding tests for new commands specified in #4

Few small nits for RESP writing/parsing parts, can be left as follow ups too.

Much appreciated @PaulusParssinen!


Update README with section on updating the CI image.

I forgot to add here that we need to occasionally update the image on GCP.

Thanks!


Only the current buffer is visible

Hi,
I just installed vim-buffet in neovim using vim-plug, after restarting neovim, the tabline appear, but it only showed with the active buffer only, not any other buffers.
I tested in vim 8.1 and it showed fine.
I'm using neovim 0.3.5.
Please tell me if I need to provide any more information, thanks.

@mnrce thanks for creating this issue and providing all the info. I'll be able to have a look into this in a week and will keep updating this issue.

@mnrce I have just tested with neovim v0.3.7 and it works fine. Can you please try upgrading neovim and see if the issue continues to appear?

I've just tested with neovim v0.3.7 and v0.4.0-1119-g8c7e41f59 and still had the same issue:

You can see that :ls show two buffers but the tabline only show one.

Thanks for posting the screenshot @mnrce. I think the problem is with another plugin. Are you using airline for statusline?

Thanks for posting the screenshot @mnrce. I think the problem is with another plugin. Are you using airline for statusline?

I'm using lightline for statusline.

@mnrce figured it out. So you probably have the Lightline Tabline enabled by default. The reason you see just one buffer, is that the Lightline Tabline actually shows the tabs and not buffers, and the tab just shows the current active buffer. All you need to do is just disable the Lightline Tabline, should be something like this:
let g:lightline.enable.tabline = 0

Please confirm that it worked for you, or let me know otherwise and let's continue investigating.

@mnrce figured it out. So you probably have the Lightline Tabline enabled by default. The reason you see just one buffer, is that the Lightline Tabline actually shows the tabs and not buffers, and the tab just shows the current active buffer. All you need to do is just disable the Lightline Tabline, should be something like this:
let g:lightline.enable.tabline = 0

Please confirm that it worked for you, or let me know otherwise and let's continue investigating.

It works now, thank you. I didn't know lightline has tabline, and for some reason it worked in vim but not neovim, so I didn't think lightline was the reason.

I am glad it worked for you @mnrce!
@EdgarOrtegaRamirez @nifoc could you please check if this works for you as well?

In my case this was the setting:
let g:lightline = {
      \ 'enable': {
      \   'tabline': 0
      \ },
      \ }

and this is how it looks

@EdgarOrtegaRamirez great, that's what it is supposed to look like. You can customize the colors the way you want as well as apply for fancy stuff like this. Note, the blue #-es are the Tabpages. So in your case you have 4 Tabpages, and currently Tabpage #3 is active.

In my case this was the setting:
let g:lightline = {
      \ 'enable': {
      \   'tabline': 0
      \ },
      \ }

and this is how it looks without any additional buffet config set

This is what worked for me. Perhaps we can leave this issue open as it's not as obvious to find.

@hrai, should I add this to README?

@hrai, https://github.com/bagrat/vim-buffet#faq

@baIIoon not sure why that didn't work for me.

@hrai, I updated the README, https://github.com/bagrat/vim-buffet/commit/27d5a452b214461ec78d0f5fc7704dc3ed6becc3. I don't have much experience with VimL to answer (clarify) that, so sorry!


Docs pass

Initial docs cleanup.
I'd suggest a lot of work on the v2_migration document; much of that can be moved to other files. That file should be small and concise with only the things the user needs to know to get their code to work on v2

🎉


Filter calculations animation

This component includes an animation that shows how filters are calculated.
I've used the react-slick package to help with the animation.
Installed the necessary dependencies and made small background color changes to Maya's FilterSizes component

Working on a small change to the buttons - gonna push the change in a bit

Getting this weird compilation error:
"Redundant alt attribute. Screen-readers already announce img tags as an image. You don’t need to use the words image, photo, or picture (or any specified custom words) in the alt prop  jsx-a11y/img-redundant-alt"
My alt message is "first example of feature pool calculation - shows how the first element of the feature map is calculated by taking the dot product of the filter and a portion of our image" and I need the word image to be in the alt message.

Oh yeah, I'm not a huge fan of how that is set up. You can disable that with eslint's disable features; see the ESLint docs for more information.

Just to summarize:

I understand that using react-slick is not ideal and will try to make my own carousel in the next week or so to replace it.
I used ESLint's no-alert method to get around the alert message I was getting for my images' alt messages.

Also we may want to discuss the visual presentation of the carousel - we may do this at the PM meeting or in some other form. Don't think that's a blocker to merge right now.

Also we may want to discuss the visual presentation of the carousel - we may do this at the PM meeting or in some other form. Don't think that's a blocker to merge right now.
What do you mean by this?

Ok sounds good! Aman you're good to merge, squash merge if you can 😄

I think Matt just meant that it might be worth investigating the best way of presenting the slides to get the process across. For example, right now, the slides just scroll through one by one, but it may be beneficial to lay out the slides side-by-side with some blurbs about the process at each step. We want to make sure that these learning labs help make the material intuitive 👍

We go through the process of calculation in-depth in our slides (taught in session 4b), and our idea was to have people first attend that session/go through the slides and then go through the Learning Lab!

Thanks for all your help and efforts! :D @malsf21 @krashanoff


GET Request with JSON Payload

Hey!
First of all, great job! Httpful is really very elegant and powerful.
Can httpful tperform a GET request with a JSON payload (JSON in the request body, not in the URL as a parameter)?

Just to let you know that what I was asking for and wanted to do was possible, just had to tweak it a bit more. Thanks!

@RacZo you violating HTTP/1.1 spec in your application? It is very intresting case, please, provide more information about.

Thanks @RacZo. @maxbaldin was right, that breaks the rules of HTTP. If HTTP doesn't support it, HTTPful doesn't either :-(.


Updated C28720

Updated to the new format, also reduced the hostility of the wording

Docs Build status updates of commit bd8b9a8:
:warning: Validation status: warnings

File
Status
Preview URL
Details

windows-driver-docs-pr/devtest/28720-banned-api-usage-use-updated-function-replacement.md
:warning:Warning

Details

windows-driver-docs-pr/devtest/28720-banned-api-usage-use-updated-function-replacement.md

Line 1, Column 1: [Warning: ms-date-missing - See documentation] Missing required attribute: 'ms.date'. A freshness date is required for this content set. Add a date in format MM/DD/YYYY.
Line 1, Column 1: [Warning: title-missing - See documentation] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 6, Column 13: [Warning: yaml-header-syntax-error] While parsing a block collection, did not find expected '-' indicator.
Line 1, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 61e7d83:
:warning: Validation status: warnings

File
Status
Preview URL
Details

windows-driver-docs-pr/devtest/28720-banned-api-usage-use-updated-function-replacement.md
:warning:Warning

Details

windows-driver-docs-pr/devtest/28720-banned-api-usage-use-updated-function-replacement.md

Line 1, Column 1: [Warning: ms-date-missing - See documentation] Missing required attribute: 'ms.date'. A freshness date is required for this content set. Add a date in format MM/DD/YYYY.
Line 1, Column 1: [Warning: title-missing - See documentation] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 6, Column 13: [Warning: yaml-header-syntax-error] While parsing a block collection, did not find expected '-' indicator.
Line 1, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit af5677a:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

windows-driver-docs-pr/devtest/28720-banned-api-usage-use-updated-function-replacement.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 2eb4096:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

windows-driver-docs-pr/devtest/28720-banned-api-usage-use-updated-function-replacement.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel