Add filters to transfermarket

Hey Fabian,
I know you are on vacation, enjoy the time! I just collect a few ideas here:
Add filters to transfermarket

show only players where market value is growing
show only players without other bids
show only players with own bid
show only players without injuries
show only players who are sold before the next matchday
show only players who are sold after the next matchday
show only players who are sold before the next market value update (22:00)
show only players who are sold after the next market value update (22:00)

Sort players on transfermarket:

Market value
Growth

Just some ideas, maybe you can evaluate if you find this also useful!
BR
Bastian

Hi @Quotic ,
I added some new filters.
Your requested filters
show only players who are sold before the next matchday
show only players who are sold after the next matchday
show only players who are sold before the next market value update (22:00)
show only players who are sold after the next market value update (22:00)

and sorting will need some more time.
But you can check the new filters already. Just visit https://kickbaseplus.fabian-fischer.com/#/transfermarket and let me know, what do you think.
Fabian

@fabfischer thanks for your work, this filters are very helpful. I will continue to share my ideas with you ;P

Hi @Quotic,
I pushed an update, which includes the filter and sorting. You can check it here: https://kickbaseplus.fabian-fischer.com
Please let me know what you think.
Fabian

Its perfect but in mobile version filter descriptions are too long. Maybe shorten description and remove "show only players who are sold "

Hi @Quotic ,
all filters should now be fully visible for mobile devices. . You can test it here: https://kickbaseplus.fabian-fischer.com

Hi @Quotic,
I released it with version 1.6 (#58), so I'm closing this issue.
you can test it here: https://kickbaseplus.fabian-fischer.com/
best,
Fabian


Added Link Type check and simplified floating link plugin

Extension of #5551
@zurfyx is this closer to what you were looking for? I certainly made it simple for the product side, but I'm not sure if there's a more optimal solution, or if this is overkill.
Also I noticed $getAncestor and $findMatchingParent are similar but I'm not sure if there's a distinct difference I'm not seeing.

So I ended up having to delve further into getNodesBetween to get around Lexical being incapable of selecting LineBreakNodes. The big issue I couldn't solve is when you select a LineBreakNode on the beginning or end of selection, lexical selects the entire paragraph node anyway.
So there's a weird case where you have a linebreak and a link, and if you select just the linebreak only, lexical thinks you're selecting the whole paragraph and, therefore, the link. I'm not sure how to work around this.

The selection issues should be solved by #6883, but this PR is quite stale and has conflicts. Please re-open if you intend to update it to work with the current version.


#1 Implement Miller-Rabin Primality Test

#1 Added miller-rabin primality test algorithm with big O of k * log^3(n). There are some issues with compiling to javascript, and it might be better to use the BigInt class at some point, depending on requirements.

https://blogs.scientificamerican.com/roots-of-unity/why-isnt-1-a-prime-number/
Please check this article. 1 is not a prime number. I think, you should also check this.

Thanks for the contribution.


dirs

"vite-plugin-components": "0.13.2",
viteComponents({
dirs: ['src/components', 'src/pages/**/components'],
customComponentResolvers: [VantResolver()],
}),
in 'src/components' ,  use parent directory as name for index components
but
use link 'src/pages/**/components'   can‘t  use parent directory as name for index components.
[Vue warn]: Failed to resolve component

We temporarily close this due to the lack of enough information. Please provide a minimal reproduction to reopen the issue. Thanks.
https://antfu.me/posts/why-reproductions-are-required


feat(terminal): add interface to open a remote terminal

Linking a pull request to #62 in the description of PR.
close #62

Do we want to have some error reporting? E.g. when device received RemoteTerminalRequest with hostname it cannot resolve.

At the moment only HTTP client errors cause the device to stop attempting to connect with the bridge, but no information is reported (since no interfaces to do so have been defined). @harlem88 @rbino do you think it could be a good idea to introduce this information exchange?


Modo inserir dados e tags

O modo inserir dados não fica sempre disponível. Como entra no modo editor? Para escrever o código?
Algumas tags em html, tem de inserir manualmente. O Emmet parece não estar achando as tags, como a tag p, h1, h2, etc... O DocType, cabeçalho, também não aparece no auto completar.

Hi, which version of VS Code are you using?
If you are using VS Code Insiders, the issue might be resolved in the next update; see https://github.com/microsoft/vscode/issues/172534 for reference.
\gifPlease

Thanks for reporting this issue! Unfortunately, it's hard for us to understand what issue you're seeing. Please help us out by providing a screen recording showing exactly what isn't working as expected. While we can work with most standard formats, .gif files are preferred as they are displayed inline on GitHub. You may find https://gifcap.dev helpful as a browser-based gif recording tool.
If the issue depends on keyboard input, you can help us by enabling screencast mode for the recording (Developer: Toggle Screencast Mode in the command palette). Lastly, please attach this file via the GitHub web interface as emailed responses will strip files out from the issue.
Happy coding!

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


Bump up pre-merge OS from ubuntu 16 to ubuntu 18 [skip ci]

As we are dropping support for ubuntu 16, and cudf is deprecating support for cuda 10.x
We are going to make our pre-merge pipeline to use ubuntu 18 + cuda11.0 as default env.
Tested in my forked repo. I will verify w/ a Test PR after this one got merged~

build

where did deprecate ubuntu 16 come from?

where did deprecate ubuntu 16 come from?

I was told recently, @sameerz can you help add some more context?

We will smoke test 16.04 but not do QA on it for the 0.5 release.


High level scope of library question

My boss just pointed this library out to me. We use another C++ library called Restbed (https://github.com/Corvusoft/restbed) to implement an integrated Internet server within our applications. Restbed only supports Basic & Digest Authentication when one is not using HTTPS under Windows. We want to support additional Authentication schemes, and my boss pointed at this library as a means of supporting more Authentication methods.
However, from what I can tell this library is for making requests and not receiving requests. Is that correct? This library is for creating a programmatic user making requests, and not making software that receives and responds to requests. Correct?

Exact. CPR is a simple wrapper around libcurl.
We are using mongoose as a server for testing our implementation.
You might want to have a look at it.


Unable to connect Remote Redis

While Trying to connect Remote Redis instance hosted on PCF Shared VM, its failing with time out error as below -
Redis error Error: connect ETIMEDOUT

as message states the redis commander container cannot talk to your redis server. Without further infos we cannot really help.
Therefore please check:

port configured is the port the redis server listens to
dns-name or ip given to redis commander as redis server is correct
dns-name can be resolved from inside the container
final ip address the server name resolves to can be reached from inside the container (ip route exists and no firewall is blocking communications)

Issue closed by now?

close (no feedback and unable to reproduce)


Specify shell version for shell plugin

I use dovecot on different OS and ran into a tiny problem trying to expand curly braces like
[shell]
    - ["mkdir -p test/{foo,bar}", Create some directories]

This works on e.g. macOS but not on Ubuntu due to the differences in the subprocess.call's default sh versions. What do you think of either using the current $SHELL as executable, or allowing to define a specific shell for a given command?
I would be happy to implement this if you think it's useful also for other dotbot users.

Using the current $SHELL seems reasonable.
A pull request would be appreciated!

Fixed in #100.


Helm upgrade fails to install clustertriggerauthentications crd

Report
Hi,
Not sure if this is the correct place for this however, here we go...
Helm upgrade from 2.0.0 to 2.2.0 fails to install (clustertriggerauthentications.keda.sh crd)
We're running keda v2.0.0 installed via helm 3 on v1.19.6 (AKS)

Installed using --set=installCRDs=true --set=podIdentity.activeDirectory.identity=<aad_identity>

Since the crd is missing pod fails to start.
(no matches for kind "ClusterTriggerAuthentication" in version "keda.sh/v1alpha1)
Expected Behavior
Missing components are installed and images are upgraded to the version specified.
Actual Behavior
Images get upgraded to the version specified.
Missing components are not installed, in this case clustertriggerauthentications.keda.sh is not installed.
If I manually install the missing crd, everything works as expected.
Steps to Reproduce the Problem

Ensure that keda crds are not already installed
helm install keda kedacore/keda -n keda --version=2.0.0 --set=installCRDs=true --set=podIdentity.activeDirectory.identity=<aad_identity> --debug
helm upgrade helm install keda kedacore/keda -n keda --version=2.2.0 --debug
check pod logs, check crd

Logs from KEDA operator
2021-03-26T14:47:51.962Z	INFO	controller-runtime.metrics	metrics server is starting to listen	{"addr": ":8080"}
2021-03-26T14:47:51.965Z	INFO	controllers.ScaledObject	Running on Kubernetes 1.19	{"version": "v1.19.6"}
2021-03-26T14:47:51.965Z	INFO	setup	Starting manager
2021-03-26T14:47:51.965Z	INFO	setup	KEDA Version: 2.2.0
2021-03-26T14:47:51.965Z	INFO	setup	Git Commit: 6dc4c3524ba6278276cd1338cc7e4e9a7dd88963
2021-03-26T14:47:51.965Z	INFO	setup	Go Version: go1.15.6
2021-03-26T14:47:51.965Z	INFO	setup	Go OS/Arch: linux/amd64
I0326 14:47:51.966071       1 leaderelection.go:243] attempting to acquire leader lease keda/operator.keda.sh...
2021-03-26T14:47:51.966Z	INFO	controller-runtime.manager	starting metrics server	{"path": "/metrics"}
I0326 14:48:09.381707       1 leaderelection.go:253] successfully acquired lease keda/operator.keda.sh
2021-03-26T14:48:09.381Z	INFO	controller	Starting EventSource	{"reconcilerGroup": "keda.sh", "reconcilerKind": "ScaledJob", "controller": "scaledjob", "source": "kind source: /, Kind="}
2021-03-26T14:48:09.381Z	INFO	controller	Starting EventSource	{"reconcilerGroup": "keda.sh", "reconcilerKind": "ClusterTriggerAuthentication", "controller": "clustertriggerauthentication", "source": "kind source: /, Kind="}
2021-03-26T14:48:09.381Z	INFO	controller	Starting EventSource	{"reconcilerGroup": "keda.sh", "reconcilerKind": "TriggerAuthentication", "controller": "triggerauthentication", "source": "kind source: /, Kind="}
2021-03-26T14:48:09.381Z	INFO	controller	Starting EventSource	{"reconcilerGroup": "keda.sh", "reconcilerKind": "ScaledObject", "controller": "scaledobject", "source": "kind source: /, Kind="}
2021-03-26T14:48:09.482Z	INFO	controller	Starting Controller	{"reconcilerGroup": "keda.sh", "reconcilerKind": "ScaledJob", "controller": "scaledjob"}
2021-03-26T14:48:10.285Z	ERROR	controller-runtime.source	if kind is a CRD, it should be installed before calling Start	{"kind": "ClusterTriggerAuthentication.keda.sh", "error": "no matches for kind \"ClusterTriggerAuthentication\" in version \"keda.sh/v1alpha1\""}
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func1
	/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.6.5/pkg/internal/controller/controller.go:143
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start
	/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.6.5/pkg/internal/controller/controller.go:184
sigs.k8s.io/controller-runtime/pkg/manager.(*controllerManager).startRunnable.func1
	/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.6.5/pkg/manager/internal.go:676
2021-03-26T14:48:10.285Z	INFO	controller	Starting workers	{"reconcilerGroup": "keda.sh", "reconcilerKind": "ScaledJob", "controller": "scaledjob", "worker count": 1}
2021-03-26T14:48:10.285Z	INFO	controller	Stopping workers	{"reconcilerGroup": "keda.sh", "reconcilerKind": "ScaledJob", "controller": "scaledjob"}

KEDA Version
2.2.0
Kubernetes Version
1.19
Platform
Microsoft Azure
Scaler Details
Azure Service Bus

Might be related to https://github.com/helm/helm/issues/6581

As a mitigation, you can manually install the CRD (https://github.com/kedacore/charts/blob/master/keda/crds/clustertriggerauthentications.yaml).

As per: https://helm.sh/docs/chart_best_practices/custom_resource_definitions/#install-a-crd-declaration-before-using-the-resource

There is no support at this time for upgrading or deleting CRDs using Helm. This was an explicit decision after much community discussion due to the danger for unintentional data loss. Furthermore, there is currently no community consensus around how to handle CRDs and their lifecycle. As this evolves, Helm will add support for those use cases.

It looks like we'll need to find a way around this.

This should be noted in upgrade notes as when installing through Helm this is technically a breaking change
Workaround: kubectl apply -f https://raw.githubusercontent.com/kedacore/charts/master/keda/crds/clustertriggerauthentications.yaml

I've opened https://github.com/kedacore/charts/issues/140 to fix this so that they are always added and I'll update the docs asap.
Sorry for the inconvenience. I wish Helm was handling this better.

Hi @tomkerkhove,
Hope you're well.
I can confirm the workaround works since I tested it before creating the ticket.
However, in this specific case we're not actually talking about a CRD upgrade using Helm since the actual CRD is missing to begin with. So my exception would be that if the CRD is not installed and keda has a hard dependency on it, exactly the situation we're facing now , it should be installed.
I would also argue that the user should have the possibility of forcing the upgrade of a CRD through Helm, using a specific switch (with full accountability of course on his end, knowing that the process is not supported and may potentially cause data lose).
Anyway that's just my point of view.
Let me know what you think.
Thanks for all your help and support.
Be safe!

Fully agree, but apparently Helm doesn't agree on that (see above).
I'm working on a fix for this in #141

This is fixed and available: https://github.com/kedacore/charts/releases/tag/v2.2.1
Sorry about this.

Install doc still references to this issue. But I assume this issue is fixed and workaround is not longer needed, right?

Yes, docs only refer to v2.1 or below. v2.2 normally doesn't point here.

Yes, docs only refer to v2.1 or below. v2.2 normally doesn't point here.

2.2 still points to here

Thanks for letting me know @maxisam!


uv pip compile <(echo foobar) reports "file not found", but it should work

Example:
$ uv-0.1.24 pip compile <(echo example)
Resolved 2 packages in 527ms
# This file was autogenerated by uv via the following command:
#    uv pip compile /proc/self/fd/11
example==0.1.0
six==1.16.0
    # via example
$ uv pip compile <(echo example)
error: File not found: `/proc/self/fd/11

git bisect suggests this was introduced in https://github.com/astral-sh/uv/commit/081f20c53ef6849c816cbe12e5dcf4bb7de575e1.

Thx!


1st test adding a battery status field -graphical only- not working

Extend OpenBot Android app showing the battery state of the serial connected MCU (arduino)

Ooops. This was pushed by mistake, as it is only a first graphical test. Sorry for that.

No problem, you can also keep this PR open. It will track the changes you make to your branch. Also make sure to add the GUI addition to the same file in the folder layout-land. This will make sure, the element is also there when you rotate the phone.


Generate Stylesheet with Color Variables

@microsoft-github-policy-service agree [company="{your company}"]

Can you explain how this will be used?

different way to represent RGB values. Instead of using three numbersCSS variables is when it comes to the colors of your design. Instead of copy and paste the same colors over and over again====hexagonical

https://gist.github.com/aeschli/8aa2f09d75d004c8b48a91ec1457008d is the output of that command.
We don't need the command in the product, it's just a helper I used to generate the gist above


CB-10622 Support any MRT qualifiers for Windows icons

JIRA CB-10622
This PR fixes copying MRT images with qualifiers other that scale-*
This is an alternative for #149

do we need to add scale 200/400 here: https://github.com/apache/cordova-windows/pull/159/files#diff-32bff2189ca335a5581636fff314a504R315

@nikhilkh, the items from this array is used only when icon is defined using width and height. As we decided to recommend using target to define icons, should we still continue supporting all available scales for width/height-defined icons?

Yup - now I understand - we need not need to add to that array.

Reviewed and verified on sample config/images :+1:


New file opening error doesn't wrap properly for very long lines

Was trying to open a private repo in github.dev:

We should allow words to break so they don't overflow

@Tyriar was this failure to open a file expected (you had the file open from a previous session and the file has since been deleted) or not (the GitHub Repositories extension failed to load etc)?

@joyceerhl delayed response but I'm pretty sure it was unexpected, I think connecting to the workspace failed (maybe my extension was disabled or something)

Since the top was hard to repro, verified by opening an image in the text editor and manually changing the dom:


RequiredIf validator does not work properly if field is Optional

↪ To Reproduce
Imagine, we have a data object with three fields
    #[Required]
    #[BooleanType]
    public bool $success;

    #[RequiredIf('success', 'false')]
    #[StringType]
    public string $error = '';

    #[RequiredIf('success', 'true')]
    #[IntegerType]
    public Optional|int $id;

The first one (success) represents the state of the data state, is it successful or not.
The second one (error) has to have a description if the state is not successful.
The third one (ID) has to contain the resulting value if the state is successful.
✏ Describe the bug
The error works as expected – it is required if success = false.
But the ID will produce no validation errors with data set ['success' => true], because of Optional (the rules set will contain 'Sometimes' rule, and because of it passesOptionalCheck will be failed, and field become not validatable)
✅ Expected behavior
The ID field should be provided only if the operation was successful.
It means on set like ['success' => false, 'error' => 'failed'], the ID is really Optional.
But on set ['success' => true] the validation should throw an exception because the ID is required on successful data set.
🖥 Versions
Laravel:
"name": "laravel/framework",
"version": "v9.52.10",
Laravel Data:
"name": "spatie/laravel-data",
"version": "3.6.0",
PHP:
8.1

Hi @akimkelar,
We cannot fix this in v3 since it would break a lot, automatically deducing these rules is really hard. I've added a test for v4 which we'll try to solve in that version.
In the meantime, you can always overwrite validation rules by implementing a custom rules method on the data class. Adding the correct rules over there is the easiest fix for now.


Visualize color opacity tokens in Storybook

Rename 'hex' to 'value' because 'hex' does not make sense for color opacity values.
The opacity is visualized in a native html table, because the docs addon does not seem to have a component of that sorts

Now that we have new function name for traversing the tokens, and also have renamed the info object, this PR is pretty much all wrong. Closing, will follow up in another one.


Add Symfony environment to commands executed in ScriptHandler

When using composer install command with --no-dev flag, ScriptHandler executes commands without specify environment.
So, if you have a development dependency in require-dev and this development bundle is loaded in AppKernel only for dev and test environment, when you execute install with --no-dev option you will get an error.
For example, I want to move "sensio/generator-bundle" from "require" to "require-dev" in composer.json, because of I don't want to this code generators be able in production servers.
"require-dev": {
    "sensio/generator-bundle": "~3.0"
},

In AppKernel this bundle is loaded only for dev and test Symfony environments.
if (in_array($this->getEnvironment(), ['dev', 'test'])) {
    $bundles[] = new Symfony\Bundle\DebugBundle\DebugBundle();
    $bundles[] = new Symfony\Bundle\WebProfilerBundle\WebProfilerBundle();
    $bundles[] = new Sensio\Bundle\DistributionBundle\SensioDistributionBundle();
    $bundles[] = new Sensio\Bundle\GeneratorBundle\SensioGeneratorBundle();
}

If I do this, when I execute composer install --no-dev command I get a ScriptHandler::clearCache error because it makes an "app/console cache:clear --no-warmup" without specify environment, so "dev".
> Sensio\Bundle\DistributionBundle\Composer\ScriptHandler::clearCache
Script Sensio\Bundle\DistributionBundle\Composer\ScriptHandler::clearCache handling the post-install-cmd event terminated with an exception

  [RuntimeException]
  An error occurred when executing the "'cache:clear --no-warmup'" command

Proposal
I propose a new option for script handler witch provides this feature in different ways:
You can specify env in composer.json extra:
"extra": {
    "symfony-env": "prod"
},

You can do it with an environment variable:
SYMFONY_ENV=prod composer install --no-dev

If we intend to support all environments installation, I'm 👍 for this

Thanks @HeahDude for your suggestions, I made the changes

LGTM 👍
What do you think @fabpot?

Closing this pull request as this bundle is now deprecated. Symfony Flex replaces this bundle.


Some more efforts on styling but a long way left to go.

Thanks Matt, love the coloring in the nav tabs!

Love you!!


[FEATURE REQUEST] Make the establishment of Trust for XSUAA switchable

Which area is mainly impacted
CLI in general
Requested Feature
Currently the Setup of an XSUAA instance in the plan apiaccess enforces the establishment of trust with an IdP see https://github.com/SAP-samples/btp-setup-automator/blob/main/libs/python/helperBtpTrust.py#L15.
This should be made switchable when defining the creation of a service instance for this plan. The use case file should offer the option to define if this establishment of trust with an IdP should be executed or not. This option should only be available and evaluated in this specific scenario.
Use Case/Scenario
Creation of a XSUAA instance with plan apiaccess
Would you like to support us?

[ ] Yes, I would like to support you

Anything else?
Additional information is available in the GitHub Discussion .

Enhancement is available in dev incl. image. The enhancement will be available in main with the next release.


Date saved but retrieved null in ElementCollection (or Embedded) property

I have an object of type Instance which contains an @ElementCollection of type Datapoint. Each datapoint has a timestamp and a value. In a test, I create some instances with their datapoints and save them, however, when I read any of those instances back from the database, the value for datapoints is set but the timestamp is null.
I am using:
Cassandra 3.11.2
Kundera 3.12
persistence.xml
    <persistence-unit name="cassandra_pu">
        <provider>com.impetus.kundera.KunderaPersistence</provider>
        <properties>
            <property name="kundera.nodes" value="localhost"/>
            <property name="kundera.port" value="9042"/>
            <property name="kundera.keyspace" value="d2lablite"/>
            <property name="kundera.dialect" value="cassandra"/>
            <property name="kundera.ddl.auto.prepare" value="create" />
            <property name="kundera.client.lookup.class" value="com.impetus.kundera.client.cassandra.dsdriver.DSClientFactory" />
        </properties>
    </persistence-unit>

Datapoint.java
@Embeddable
public class Datapoint {
    @Column(name="timestamp")
    @Temporal(TemporalType.TIMESTAMP)
    private java.util.Date timestamp;

    @Column(name="value")
    private double value;

    public Datapoint() { }

    // Getters, setters
}

Instance.java
@Entity
@Table(name="instances")
public class Instance {
    @Id
    @Column(name="uuid")
    private String uuid;

    @Column(name="param")
    private String param;

    @ElementCollection
    @Column(name="datapoints")
    private List<Datapoint> datapoints;

    @ElementCollection
    @Column(name="metadata")
    private Map<String, String> metadata;

    @Temporal(TemporalType.TIMESTAMP)
    @Column(name="date")
    private Date date;

    public Instance() { }
}

So what I do is:

Create an Instance, create a List<Datapoint>, set it to instance and persist the instance
Check via cqlsh that the instance is saved and all datapoints have the timestamp saved as well
Use the EntityManager's find method to fetch an instance by its uuid, and it contains all values, including the date column, and its datapoints contain their values but the timestamp field in every datapoint is null.

I have also tried to use @Embedded and only 1 Datapoint instead of a list and the result is the same,  timestamp is null.
What did I miss?

Hi @milosjajac,
I will try to replicate this on Monday.
-Dev

Hi @milosjajac, working fine for me.
public static void main(String[] args)
{
    Map<String, String> props = new HashMap<String, String>();
    props.put(CassandraConstants.CQL_VERSION, CassandraConstants.CQL_VERSION_3_0);
    EntityManagerFactory emf = Persistence.createEntityManagerFactory("issue_pu", props);

    EntityManager em = emf.createEntityManager();

    Datapoint dp1 = new Datapoint();
    dp1.setValue(10.01);
    dp1.setTimestamp(new Date());

    Datapoint dp2 = new Datapoint();
    dp2.setValue(11.01);
    dp2.setTimestamp(new Date());

    List<Datapoint> list = new ArrayList<>();
    list.add(dp1);
    list.add(dp2);

    Instance instance = new Instance();
    instance.setDatapoints(list);
    instance.setDate(new Date());
    instance.setParam("some-param");

    String id = UUID.randomUUID().toString();

    instance.setUuid(id);

    em.persist(instance);
    Instance inst = em.find(Instance.class, id);

    List<Datapoint> dps = inst.getDatapoints();

    for (Datapoint datapoint : dps)
    {
        System.out.println(datapoint.getTimestamp());
    }

 }

Hi @milosjajac,
Seems like an issue from Kundera side.

Hi @milosjajac,
This issue is fixed and will be available in the next Kundera release.


Allow multiple individual sinks for GpuValue

basically, every input value has to track compilations and generate a new input for every sink.
see this PR: https://github.com/vvvv/VL.Stride/pull/451

Demo for this in VL.Fuse\R&D_Issues\GpuInTwiceBug.vl

Double checked everything looks like at least the patch provided by kyle is working now although I have not specifically fixed anything might be a side effect of something else not sure, Do you have anything else to test this Kyle? Otherwise would close it.

For me the demo patch still shows the broken behavior.  Are you sure don't have part of the graph cached or something?

@tebjan Are you able to give any feedback on the updated demo patch?  \R&D_Issues\42#GpuInTwiceBug.vl
@texone mentioned he is stuck with this although had tried to copy your approach
It's quite a big limitation as it stands

Late reply because the GitHub notifications didn't reach me in the past weeks.
This topic sounds like something that @azeno is comfortable with. I've lost track of the code a little bit after the mentioned pull request. It's quite complex at the moment and for me hard to decipher. I think in VL.Stride it needs a cleanup and good code documentation so that fuse can follow the guidelines.
The main idea however is, that the shader compilation context is the identifier for one particular shader that gets built. It can be used as key for IDs, input pins and other things that have to be unique per shader. It can also help with gathering information that has to be shared between different nodes that aren't aware of each other, such as multiple from/to ShaderFX nodes that have to cooperate when a shader gets built.

Yes I was also rethinking this for materials as this seems to be the main usecase I would propse for materials we use semantics and materialextension and than override the shading stage to set the semantics currently every value would be recalculated even if it shares a lot of calculations with another node

Is it potentially possible to connect two material extensions?

Hmm not sure we're on the same page here. I thought this is about the constant buffers getting generated per sink and each source needs to keep track of?


The return type should be nullable in SessionsEmspRepository.getSession

Hi team,
Congratulations for the good job you're doing.
As I'm testing the library, I found some issues.
https://github.com/IZIVIA/ocpi-toolkit/blob/76cfc19987e5a57d1923f5d35fc5d9f983e94d84/ocpi-toolkit-2.2.1/src/main/kotlin/com/izivia/ocpi/toolkit/modules/sessions/repositories/SessionsEmspRepository.kt#L30
The return type should be nullable, because the session may not be found.

Hi, thanks for your report, you are right, it has to be fixed


Actual Changes

@choper725 @abapsheep
(1)
Someone using the "check_view_destroy" parameter of the _event method?
https://github.com/abap2UI5/abap2UI5/blob/c045cd1805ab79ddf6ba084c9a302e94bf78b876/src/02/z2ui5_if_client.intf.abap#L110
It is replaced now with the following control structure and i would delete this importing parameter soon:
https://github.com/abap2UI5/abap2UI5-samples/blob/ea41cf116ba350d732adda1ac9977ab7e61abedb/src/z2ui5_cl_demo_app_001.clas.abap#L32
This structure can now be extended with additonal control flags in the future.
(2)
It is now possible to send requests to the backend before the processing of the previous request is finished, as it is done here:
https://github.com/abap2UI5/abap2UI5-samples/blob/ea41cf116ba350d732adda1ac9977ab7e61abedb/src/z2ui5_cl_demo_app_059.clas.abap#L126
For example helpful when users make inputs and you want to show suggestion always on the latest changes of the input field.
Check demo 59:

(3)
We were running often into compatibility problems concerning the UI5 version. I adjusted now the abap2UI5 core apps that they are compatible from very low to very high UI5 releases and they are independent from UI5 and OpenUI5:

That's why i replaced for example the Illustrated Message in the Error Popup which is less beautiful but compatible to all UI5 versions:

Running now from the old version 1.6 to the newest 2.x (nightly).
(4)
Adjusted the sample section, all samples listed here are now also compatible to UI5/OpenUI5 and are release independent:

Version and release specific Samples are collected here:

I hope these changes reduce compatibility issues in the future.

thanks for the summery @oblomov-dev
i never used it, maybe beacuse i never knew what it does… :)
great feature to chain requests.. just the implementation is wierd, the cnt struc, there are other featurea to it ? or just abap bool value?
cant that feature be chained to the binding as a bool ?
one note on compatibility, chasing this project to be working on all sdk version, will be a hard task,
as we see the great sap are removing support for older versions every time.. just an idea of the path ahead i guess..

yes making it compatible to all ui5 sdk is indeed a hard task and will be not the plan :) i just wanted to make the core a bit more compatible and organize the samples that it is more obvious which sample is running where. we can then set up the lowest needed release from time to time in the future.
i have in mind to collect some control variables in this structure:
https://github.com/abap2UI5/abap2UI5/blob/570aebd68756d121b267f08f9ad4189a6f742ec8/src/02/z2ui5_if_types.intf.abap#L47
then it is also easily extendable in the future if more checks are needed (eg. display no busy indicator) and also other types than booleans are posssible.
technically i see no chance to import this value with the binding because it is event related and i need this information there.

maybe last_request ? or something along this line. ?

deleted the parameter with https://github.com/abap2UI5/abap2UI5/pull/984
yes it is named like this now:

@oblomov-dev
can you explain when the check_view_destroy does?

it destroy immediately the view (before sending the backend request). but to be honest, i don't know if this is really needed.

ohh, i built like 50 apps by now and never used it, never had any issues regarding destryoed view or something like that..

It's fine it's nothing about issues, it's just a visual effect.

i close this, just open a new one if there are more questions.


[consensus][spec] cleaning blockdata checks

Over a month old, no activity closing out, feel free to re-open.


Manually handle submodules

Should fix #24 (I hope)

@proudlygeek Looks alright to me. The failing tests don't seem to be related and is a broader thing we need to fix. What needs to be done here?

I've accepted the merge. It should fix our issues with the submodule checkout. I'll handle linting issues in other PRs.


Revert VPA flag and e2e test

VPA isn't updating deployment and update the pods directly. We need to revert allowVerticalScale flag addition and revert the e2e test because they don't resemble how VPA works

/cc @xinnywinne

/retest


Logo design for uabot

Hi, my name is Zuur W. I'm a graphic designer and I'd like to collaborate on your open source project and propose free logo/icon design for your project. If it's something you're interested in, please, let me know!
Best Regards
Zuur

No thank you.


Support for custom JUnit rule instead of RunWith

I am planning to use

Spring MVC - For Integration testing
NestedRunner - For nesting test cases
JUnitParams - For DDT
Assumes - for specifying test dependencies
Mockito - For mocking
PowerMockito - For any mocking abuse I may need to do (I mean class/static method mocking)
DBUnit - For fiddling with DB data

Spring MVC in the current milestone version (4.2.0.RC1 or > 4.2 whenever the release happens) uses rules instead of runner to support integration with other runners. PowerMock currently supports Rules. Mockito supports Rule in the current Beta version (2.0.17-beta)
However, AFAIK, all others does not support rules. It would be better if this library can implement the runner using Junit Rule instead of Runner so that it can be compatible with all other runners to make a full blown testing stack. Else, people need to hack around to get most out of Java test frameworks.
Reference:

Creating a custom runner for mockito
Nested Runners Example

My mind map on how to integrate all of these is listed here

Hi, I don't know if it will be helpfull, but I saw something similar :
http://blog.schauderhaft.de/2012/12/16/writing-parameterized-tests-with-junit-rules/
and the code is :
https://github.com/schauder/parameterizedTestsWithRules

I just tried to implement JUnitParams Rules instead of Runners . It's not possible to use method parameters of JUnit test methods. Therefore it's also impossible to use the existing JUnitParams implementation with Rules.

We also gave it a try some time ago. It is not possible. I am closing this issue.


[FIX]fix cidr func with const param

Proposed changes
in function_ipxx_cidr, if we use const param, here will make core in execute_impl with check_and_get_column
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run buildall

run buildall

run buildall


CookBook name,id and description changed to not be "meta"

About the PR

the id,the name and the description resolves #29374
Why / Balance

Becuse the name is a bit meta and this user requeted a change: https://github.com/space-wizards/space-station-14/issues/29374
Technical details

the id is changed to: BookHowToCookForFortySpacemen
Media

[ ] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Breaking changes

Changelog

Chef s cookbook now has a new name and slightly changed description
:cl:

tweak:Chef s CookBook is slightly changed.

again, you can leave the ID as it is, just change the name and decs

again, you can leave the ID as it is, just change the name and desc

at this point its personal lol.

dont edit the maps directly, just add it to migration

it shuld now be done.


Change the redis server version

I am facing the same issue ,what is mentioned in this https://github.com/Netflix/conductor/issues/93. So i am trying to change the version of redis server from 3.0.6 to 3.0.7.But couldnt find out a way  to do it in  the master branch.I need some help to resolve this issue.Following is the version it shows in the logs when i try to execute the "docker-compose up" command
dynomite_1          | [2017-06-28 02:17:41.329] stats_aggregate:744 skip aggregate of shadow to sum as generator is slow
dynomite_1          | [2017-06-28 02:17:41.329] core_process_messages:666 length of C2G_OutQ : 0
dynomite_1          | [2017-06-28 02:18:02.327] gossip_loop:792 Gossip is running ...
dynomite_1          | [2017-06-28 02:18:11.358] stats_aggregate:744 skip aggregate of shadow to sum as generator is slow
dynomite_1          | [2017-06-28 02:18:11.358] stats_swap:1580 skip swap of current 0x16c3c98 shadow 0x16c3cf8 as there is nothing new
dynomite_1          | [2017-06-28 02:18:11.358] core_process_messages:666 length of C2G_OutQ : 0
dynomite_1          | [2017-06-28 02:24:39.726] dn_print_run:206 dynomite-v0.5.8-3_RedefBuildBreak-119-g77fbbdc built for Linux 4.9.27-moby x86_64 started on pid 6
dynomite_1          | [2017-06-28 02:24:40.090] dn_print_run:211 run, rabbit run / dig that hole, forget the sun / and when at last the work is done / don't sit down / it's time to dig another one
dynomite_1          | [2017-06-28 02:24:40.090] dn_print_run:213
dynomite_1          |      #                                      m
dynomite_1          |   mmm#  m   m  mmmm    mmm   mmmmm  mmm    mm#mm   mmm
dynomite_1          |  #   #  \m m/  #   #  #   #  # # #    #      #    #   #
dynomite_1          |  #   #   #m#   #   #  #   #  # # #    #      #    #''''
dynomite_1          |  \#m##   \#    #   #   #m#   # # #  mm#mm    mm    #mm
dynomite_1          |          m/
dynomite_1          | [2017-06-28 02:24:40.090] conn_init:463 conn size 408
dynomite_1          | [2017-06-28 02:24:40.090] _dn_alloc:259 malloc(712) at 0x192b060 @ dyn_core.c:262
dynomite_1          | [2017-06-28 02:24:40.171] _dn_alloc:259 malloc(1600) at 0x192b560 @ dyn_conf.c:1707
dynomite_1          | [2017-06-28 02:24:40.171] _dn_alloc:259 malloc(48) at 0x192bbb0 @ ../dyn_array.c:64
dynomite_1          | [2017-06-28 02:24:40.171] conf_open:1732 opened conf 'conf/redis_single.yml'
dynomite_1          |                 _._
dynomite_1          |            _.-``__ ''-._
dynomite_1          |       _.-``    `.  `_.  ''-._           Redis 3.0.6 (00000000/0) 64 bit
dynomite_1          |   .-`` .-```.  ```\/    _.,_ ''-._
dynomite_1          |  (    '      ,       .-`  | `,    )     Running in standalone mode
dynomite_1          |  |`-._`-...-` __...-.``-._|'` _.-'|     Port: 22122
dynomite_1          |  |    `-._   `._    /     _.-'    |     PID: 5
dynomite_1          |   `-._    `-._  `-./  _.-'    _.-'
dynomite_1          |  |`-._`-._    `-.__.-'    _.-'_.-'|
dynomite_1          |  |    `-._`-._        _.-'_.-'    |           http://redis.io
dynomite_1          |   `-._    `-._`-.__.-'_.-'    _.-'
dynomite_1          |  |`-._`-._    `-.__.-'    _.-'_.-'|
dynomite_1          |  |    `-._`-._        _.-'_.-'    |
dynomite_1          |   `-._    `-._`-.__.-'_.-'    _.-'
dynomite_1          |       `-._    `-.__.-'    _.-'
dynomite_1          |           `-._        _.-'
dynomite_1          |               `-.__.-'
dynomite_1          |
dynomite_1          | 5:M 28 Jun 02:24:40.222 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
dynomite_1          | 5:M 28 Jun 02:24:40.222 # Server started, Redis version 3.0.6
dynomite_1          | 5:M 28 Jun 02:24:40.222 # WARNING you have Transparent Huge Pages (THP) support enabled in your kernel. This will create latency and memory usage issues with Redis. To fix this issue run the command 'echo never > /sys/kernel/mm/transparent_hugepage/enabled' as root, and add it to your /etc/rc.local in order to retain the setting after a reboot. Redis must be restarted after THP is disabled.

And it hangs with the following output

 is nothing new
dynomite_1          | [2017-06-28 07:07:53.638] core_process_messages:666 length of C2G_OutQ : 0
dynomite_1          | [2017-06-28 07:08:10.750] gossip_loop:792 Gossip is running ...
dynomite_1          | [2017-06-28 07:08:23.488] stats_aggregate:744 skip aggregate of shadow to sum as generator is slow
dynomite_1          | [2017-06-28 07:08:23.666] stats_swap:1580 skip swap of current 0x192dc98 shadow 0x192dcf8 as there is nothing new
dynomite_1          | [2017-06-28 07:08:23.666] core_process_messages:666 length of C2G_OutQ : 0
dynomite_1          | [2017-06-28 07:08:40.750] gossip_loop:792 Gossip is running ...
dynomite_1          | [2017-06-28 07:08:53.517] stats_aggregate:744 skip aggregate of shadow to sum as generator is slow
dynomite_1          | [2017-06-28 07:08:53.694] stats_swap:1580 skip swap of current 0x192dc98 shadow 0x192dcf8 as there is nothing new
dynomite_1          | [2017-06-28 07:08:53.694] core_process_messages:666 length of C2G_OutQ : 0
dynomite_1          | [2017-06-28 07:09:10.750] gossip_loop:792 Gossip is running ...
dynomite_1          | [2017-06-28 07:09:23.547] stats_aggregate:744 skip aggregate of shadow to sum as generator is slow
dynomite_1          | [2017-06-28 07:09:23.717] stats_swap:1580 skip swap of current 0x192dc98 shadow 0x192dcf8 as there is nothing new
dynomite_1          | [2017-06-28 07:09:23.717] core_process_messages:666 length of C2G_OutQ : 0
dynomite_1          | [2017-06-28 07:09:40.749] gossip_loop:792 Gossip is running ...
dynomite_1          | [2017-06-28 07:09:53.577] stats_aggregate:744 skip aggregate of shadow to sum as generator is slow
dynomite_1          | [2017-06-28 07:09:53.746] stats_swap:1580 skip swap of current 0x192dc98 shadow 0x192dcf8 as there is nothing new
dynomite_1          | [2017-06-28 07:09:53.746] core_process_messages:666 length of C2G_OutQ : 0
dynomite_1          | [2017-06-28 07:10:10.749] gossip_loop:792 Gossip is running ...
dynomite_1          | [2017-06-28 07:10:23.596] stats_aggregate:744 skip aggregate of shadow to sum as generator is slow
dynomite_1          | [2017-06-28 07:10:23.776] stats_swap:1580 skip swap of current 0x192dc98 shadow 0x192dcf8 as there is nothing new
dynomite_1          | [2017-06-28 07:10:23.776] core_process_messages:666 length of C2G_OutQ : 0
dynomite_1          | [2017-06-28 07:10:40.749] gossip_loop:792 Gossip is running ...
dynomite_1          | [2017-06-28 07:10:53.625] stats_aggregate:744 skip aggregate of shadow to sum as generator is slow
dynomite_1          | [2017-06-28 07:10:53.806] stats_swap:1580 skip swap of current 0x192dc98 shadow 0x192dcf8 as there is nothing new
dynomite_1          | [2017-06-28 07:10:53.806] core_process_messages:666 length of C2G_OutQ : 0
dynomite_1          | [2017-06-28 07:11:10.749] gossip_loop:792 Gossip is running ...
dynomite_1          | [2017-06-28 07:11:23.655] stats_aggregate:744 skip aggregate of shadow to sum as generator is slow
dynomite_1          | [2017-06-28 07:11:23.824] stats_swap:1580 skip swap of current 0x192dc98 shadow 0x192dcf8 as there is nothing new
dynomite_1          | [2017-06-28 07:11:23.824] core_process_messages:666 length of C2G_OutQ : 0
dynomite_1          | [2017-06-28 07:11:40.749] gossip_loop:792 Gossip is running ...
dynomite_1          | [2017-06-28 07:11:53.685] stats_aggregate:744 skip aggregate of shadow to sum as generator is slow
dynomite_1          | [2017-06-28 07:11:53.840] stats_swap:1580 skip swap of current 0x192dc98 shadow 0x192dcf8 as there is nothing new
dynomite_1          | [2017-06-28 07:11:53.840] core_process_messages:666 length of C2G_OutQ : 0
dynomite_1          | [2017-06-28 07:12:10.749] gossip_loop:792 Gossip is running ...
dynomite_1          | [2017-06-28 07:12:23.706] stats_aggregate:744 skip aggregate of shadow to sum as generator is slow
dynomite_1          | [2017-06-28 07:12:23.858] stats_swap:1580 skip swap of current 0x192dc98 shadow 0x192dcf8 as there is nothing new
dynomite_1          | [2017-06-28 07:12:23.858] core_process_messages:666 length of C2G_OutQ : 0

@sangeetanadgir the docker version should work as it is.


Unable to cancel request for *client.addQuery\n","stream":"stderr"

Setup

Rancher version: 2.6.2
Browser type & version: Safari

Describe the bug
we can't login/browse the Rancher, it's indefinitely loading, on the container logs we see only errors related to WebSocket disconnection and unable to communicate with k8s API
To Reproduce
No actual scenario to reproduce the issue
Result
Rancher UI indefinitely loading, not responding from the UI
Expected Result
Has to load the UI and make continuous connection with k8s api
Additional context
Infrastructure description:
The rancher container is running on a separate rke cluster on on-prem - RHEL (7.9)
The cluster was created through the Rancher - 3 Masters(Control plane, etcd, worker) and 10 Windows nodes
Kubernetes Version: v1.21.11 +rke
NAME STATUS ROLES AGE VERSION
master0-               Ready    controlplane,etcd   2y119d   v1.20.11
master1                 Ready    controlplane,etcd   2y119d   v1.20.11
master2.                Ready    controlplane,etcd   2y119d   v1.20.11
k8dev01-worker0       Ready    worker              2y119d   v1.20.11
k8dev01-worker1        Ready    worker              2y119d   v1.20.11
k8dev01-worker10      Ready    worker              704d     v1.20.11
k8dev01-worker2        Ready    worker              2y119d   v1.20.11
k8dev01-worker3         Ready    worker              2y119d   v1.20.11
k8dev01-worker4         Ready    worker              2y119d   v1.20.11
k8dev01-worker5         Ready    worker              2y119d   v1.20.11
k8dev01-worker6         Ready    worker              2y119d   v1.20.11
k8dev01-worker8         Ready    worker              705d     v1.20.11
k8dev01-worker9         Ready    worker              704d     v1.20.11
Logs: Cattle-cluster-agent
msg="Failed to dial steve aggregation server: websocket: close 1006 (abnormal closure): unexpected EOF"\n","stream":"stdou        t",
73049 {"log":"W0320 20:15:55.631076      56 transport.go:260] Unable to cancel request for *client.addQuery\n","stream":"stderr","time":"2024-03-20T20:15:55.631633189Z"}
73050 {"log":"time="2024-03-20T20:16:14Z" level=error msg="error syncing 'kong-data-plane-kong-validations': handler need-a-cert: services \"kong-data-plane-kong-validation-we        bhook\" not found, requeuing"\n","stream":"stdout","time":"2024-03-20T20:16:14.383951461Z"}
73051 {"log":"time="2024-03-20T20:16:14Z" level=error msg="error syncing 'elastic-webhook.k8s.elastic.co': handler need-a-cert: services \"elastic-webhook-server\" not found        , requeuing"\n","stream":"stdout","time":"2024-03-20T20:16:14.383981182Z"}
73052 {"log":"time="2024-03-20T20:16:14Z" level=error msg="error syncing 'kong-control-plane-kong-validations': handler need-a-cert: services \"kong-control-plane-kong-validat        ion-webhook\" not found, requeuing"\n","stream":"stdout","time":"2024-03-20T20:16:14.383985086Z"}
73053 {"log":"W0320 20:16:28.604042      56 transport.go:260] Unable to cancel request for *client.addQuery\n","stream":"stderr","time":"2024-03-20T20:16:28.604964764Z"}
73054 {"log":"W0320 20:16:47.513866      56 transport.go:260] Unable to cancel request for *client.addQuery\n","stream":"stderr","time":"2024-03-20T20:16:47.514916439Z"}
73055 {"log":"W0320 20:16:47.520376      56 transport.go:260] Unable to cancel request for *client.addQuery\n","stream":"stderr","time":"2024-03-20T20:16:47.52045307Z"}
73056 {"log":"W0320 20:16:47.548199      56 transport.go:260] Unable to cancel request for *client.addQuery\n","stream":"stderr","time":"2024-03-20T20:16:47.548262609

2.6.2 is no longer a supported version https://www.suse.com/lifecycle/#suse-rancher-prime. In all worlds you'll need to update to a newer, supported one.

Which is the suitable version which we avoid this issue I have observed that UI slowness issue is there in multiple versions.
Will you help me with that please ?

Responded in https://github.com/rancher/dashboard/issues/10769#issuecomment-2042916047


channels for python 2.7 broken?

Hi there,
I'm not sure if this Issue is correct here or If it should rather belong to asgiref.
it seems that asgiref==0.13.3 does not play well with channels==0.14.0.
The valid_channel_name function checks that the name of the channel is a proper six.text_type (which is unicode in python27). However the channel names, generated from channels are str not unicode. Python34 works fine as expected.

Interesting - channel names are meant to be unicode, so this is likely a bug in Channels surfaced by the more stringent check. I'll look into it later - what exactly is the stack trace you're getting looking like?

Here is a short exmaple stack trace.
__________________________________________________________
TestWebsocketConsumer.test_ws_disconnect
___________________________________________________________
tests/core/test_consumers.py:58: in test_ws_disconnect
    client.receive()  # Drop connected message
.tox/py27/local/lib/python2.7/site-packages/channels/tests/base.py:124: in receive
    message = self.get_next_message(self.reply_channel)
.tox/py27/local/lib/python2.7/site-packages/channels/tests/base.py:90: in get_next_message
    recv_channel, content = channel_layers[self.alias].receive_many([channel])
.tox/py27/local/lib/python2.7/site-packages/asgiref/inmemory.py:58: in receive_many
    assert all(self.valid_channel_name(channel) for channel in channels), "One or more channel names invalid"
E   AssertionError: One or more channel names invalid

Looking at it... could it be a problem in the test client?

Yeah  problem in the test client, it's my bad. :suspect:

@DebVortex If you could confirm latest master works fine for you I'll release it as a patch release later on

Master works perfectly fine! Thanks.

Fantastic, released in 0.14.1.


Add kinematics handling

Create code to take inputs and generate outputs, these outputs will be sent to output handling and eventually other handlers such as 3D handling and connection handling

Done.


485 anon vipps agreement min side

Page for viewing and editing anonymous Vipps agreements

closes #485

To test using EffektDonasjonDB_Dev:
Visit: http://localhost:3000/min-side/vipps-anonym?agreement-code=5cb135aa50aa190e3ff467d5173b94f1b9ff6f57

Tested on devices

[x] Desktop 💻
[x] Mobile 📱

Tests

[x] All tests are running ✔
[x] Test are updated 🧪
[x] Code Review 👩💻
[ ] QA 👌

⏲ Time spent on CR:
⏲ Time spent on QA:

Did we come up with anything in regards to the navigation, e.g. "Logg ut" button?

I will take a look at it now before merging


Perform Network Evaluation

Overhead and Bandwidth evaluation of the EdgeIO networking

measure #packets between two worker nodes in the same cluster.
measure #packets between two workers nodes in two different clusters (to see the overhead of the cluster orchestrators, if there is any)


CanvasKit backend should support PathMetrics

CanvasKit already exposes PathMetrics, it's just a matter of wiring it up to our CanvasKit backend

This was fixed in https://github.com/flutter/engine/pull/13760


Http Post with json string

How to pass json string as "string entity" to http post request?
Thanks in advance.

I have the same question, and how to solve it?


ci: allow using Vault instead of GitHub Secrets

Which problem does the PR fix?
Allow running Helm integration tests without using GitHub Secrets (see https://github.com/camunda/camunda/issues/18211 ) and instead is compatible with https://confluence.camunda.com/display/HAN/CI+Secrets+Self-Service

What's in this PR?

Checklist
Please make sure to follow our Contributing Guide.

Before opening the PR:

[ ] In the repo's root dir, run make go.update-golden-only.
[ ] There is no other open pull request for the same update/change.
[ ] Tests for charts are added (if needed).
[ ] In-repo documentation are updated (if needed).

After opening the PR:

[ ] Did you sign our CLA (Contributor License Agreement)? It will show once you open the PR.
[ ] Did all checks/tests pass in the PR?

The failing test appears to be unrelated. @cmur2 if this works for you, I'd be happy to merge it. Though it could be cool if we integrated our secrets into Vault as well.

if this works for you, I'd be happy to merge it

@jessesimpson36 it does work in my tests in https://github.com/camunda/camunda/actions/runs/9365058056/job/25779637999 so :+1: for merging


COBOL (first) - See informations carried by copybooks in the VS Code Outline view

Description of the enhancement requested
The VS Code Outline view displays a representation of the structure of a program, with sorting options.
Regarding copybooks, this view only displays the reference to the copybooks, but no information carried by the copybooks.
However, the COBOL Language Server seems to know these informations because it displays them when hovering with the mouse.
We would like the Outline view to display certain information contained in the copybooks, at a minimum:

paragraph and section names
levels 01 in data descriptions

This in a “resolved” way:

with replacing actions applied
with application of conditional compilation applied

If this could also be done with copybook cascade calls it would be a big plus...

Illustration with our “smart” development framework:

the program perform a LIRE-DM routine (read DM resource)
the program include the AAAPACCE copybook for generalized management of external resources access, (file, Db2 table, etc.)
this copybook include other specialized copybooks depending on the context, and this on several levels of include
the code for the LIRE-DM routine (Section) is found in one of the included copybooks, AAA5LSRU, which itself perform the LIRE-DM-PHYSIQUE routine, in AAA5LSF0 copybook

Having all these Sections / Paragraphs displayed in the Outline view would help in understanding the code workflow of the program, and help to identify these Sections / Paragraphs.
In actual use case below, the name of the copybook appears on the right side of the screen hardcopies.

Program (application level):

Informations in Outline view:

Copybooks (framework level):
Choice of logical acces, dependant of access type, (Read, Write...):

Choice of logical access, dependant of acces mode (Sequential, random, dynamic):

Choice of logical access, dependant of events driving:

Logical access, independant of resource organization:

Choice of physical access, dependant of resource oganization:

Physical access, dependant of resource organization:

PS:
Also, and most importantly, show the copybooks inclusion hierarchy in the Outline view.
In the example above, the inclusion hierarchy is as follows:

program, contains the PERFORM LIRE-DM statement

copybook AAAPACCE, generalized processing of a resource access

copybook AAA5L000, processing of a resource access in reading

copybook AAA5LS00, processing of a resource access in sequential reading

copybook AAA5LSRU, logical processing of a resource access in sequential reading with calculations of break keys, declares the LIRE-DM section which contains the PERFORM LIRE-DM-PHYSIQUE statement
copybook AAA5LSF0, physical processing of a resource access in sequential reading for a sequential file, declares the LIRE-DM-PHYSIQUE section


JWT authN policy for Gateway

https://github.com/istio/istio/issues/5074

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: quanjielin
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: kyessenov
Assign the PR to them by writing /assign @kyessenov in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

pilot/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@quanjielin: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
ea3fee759b43cfa9eea9af1d8d2566bd4f834b8b
link
/test istio-unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: quanjielin
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: costinm
Assign the PR to them by writing /assign @costinm in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

pilot/OWNERS
tests/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@quanjielin: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-presubmit.sh
ea3fee759b43cfa9eea9af1d8d2566bd4f834b8b
link
/test istio-presubmit

prow/istio-unit-tests.sh
553846304f97e6d96026acec92e53fe4edf075b4
link
/test istio-unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@quanjielin: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
553846304f97e6d96026acec92e53fe4edf075b4
link
/test istio-unit-tests

prow/istio-presubmit.sh
553846304f97e6d96026acec92e53fe4edf075b4
link
/test istio-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: quanjielin
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: costinm
Assign the PR to them by writing /assign @costinm in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@quanjielin: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-bookInfoTests.sh
731ea05a20d47e26690f06702655e5ca9be63ee5
link
/test e2e-bookInfo

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@quanjielin: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-bookInfoTests.sh
731ea05a20d47e26690f06702655e5ca9be63ee5
link
/test e2e-bookInfo

prow/e2e-bookInfoTests-v1alpha3.sh
731ea05a20d47e26690f06702655e5ca9be63ee5
link
/test e2e-bookInfo-envoyv2-v1alpha3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@quanjielin: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-bookInfoTests.sh
731ea05a20d47e26690f06702655e5ca9be63ee5
link
/test e2e-bookInfo

prow/e2e-bookInfoTests-v1alpha3.sh
731ea05a20d47e26690f06702655e5ca9be63ee5
link
/test e2e-bookInfo-envoyv2-v1alpha3

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
731ea05a20d47e26690f06702655e5ca9be63ee5
link
/test istio-pilot-e2e-envoyv2-v1alpha3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@quanjielin: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-bookInfoTests.sh
731ea05a20d47e26690f06702655e5ca9be63ee5
link
/test e2e-bookInfo

prow/e2e-bookInfoTests-v1alpha3.sh
731ea05a20d47e26690f06702655e5ca9be63ee5
link
/test e2e-bookInfo-envoyv2-v1alpha3

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
731ea05a20d47e26690f06702655e5ca9be63ee5
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/istio-pilot-e2e.sh
731ea05a20d47e26690f06702655e5ca9be63ee5
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: quanjielin
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: costinm
Assign the PR to them by writing /assign @costinm in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

pilot/OWNERS
tests/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@quanjielin: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-bookInfoTests.sh
731ea05a20d47e26690f06702655e5ca9be63ee5
link
/test e2e-bookInfo

prow/e2e-bookInfoTests-v1alpha3.sh
731ea05a20d47e26690f06702655e5ca9be63ee5
link
/test e2e-bookInfo-envoyv2-v1alpha3

prow/istio-pilot-e2e.sh
731ea05a20d47e26690f06702655e5ca9be63ee5
link
/test istio-pilot-e2e

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
22c5fab04ae6264e5da776ee6d272ad12d7ab785
link
/test istio-pilot-e2e-envoyv2-v1alpha3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@quanjielin: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
731ea05a20d47e26690f06702655e5ca9be63ee5
link
/test istio-pilot-e2e

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
22c5fab04ae6264e5da776ee6d272ad12d7ab785
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e-bookInfoTests.sh
22c5fab04ae6264e5da776ee6d272ad12d7ab785
link
/test e2e-bookInfo

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@quanjielin: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
731ea05a20d47e26690f06702655e5ca9be63ee5
link
/test istio-pilot-e2e

prow/e2e-bookInfoTests.sh
22c5fab04ae6264e5da776ee6d272ad12d7ab785
link
/test e2e-bookInfo

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
1891bc9cde4c7c65b73e45447c9e5e80615cc0db
link
/test istio-pilot-e2e-envoyv2-v1alpha3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@quanjielin: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-bookInfoTests.sh
22c5fab04ae6264e5da776ee6d272ad12d7ab785
link
/test e2e-bookInfo

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
1891bc9cde4c7c65b73e45447c9e5e80615cc0db
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/istio-pilot-e2e.sh
1891bc9cde4c7c65b73e45447c9e5e80615cc0db
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@quanjielin: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
1891bc9cde4c7c65b73e45447c9e5e80615cc0db
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/istio-pilot-e2e.sh
1891bc9cde4c7c65b73e45447c9e5e80615cc0db
link
/test istio-pilot-e2e

prow/e2e-bookInfoTests.sh
1891bc9cde4c7c65b73e45447c9e5e80615cc0db
link
/test e2e-bookInfo

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@quanjielin: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
1891bc9cde4c7c65b73e45447c9e5e80615cc0db
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/istio-pilot-e2e.sh
1891bc9cde4c7c65b73e45447c9e5e80615cc0db
link
/test istio-pilot-e2e

prow/e2e-bookInfoTests.sh
1891bc9cde4c7c65b73e45447c9e5e80615cc0db
link
/test e2e-bookInfo

prow/e2e-bookInfoTests-v1alpha3.sh
1891bc9cde4c7c65b73e45447c9e5e80615cc0db
link
/test e2e-bookInfo-envoyv2-v1alpha3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@quanjielin: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
1891bc9cde4c7c65b73e45447c9e5e80615cc0db
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/istio-pilot-e2e.sh
1891bc9cde4c7c65b73e45447c9e5e80615cc0db
link
/test istio-pilot-e2e

prow/e2e-bookInfoTests.sh
1891bc9cde4c7c65b73e45447c9e5e80615cc0db
link
/test e2e-bookInfo

prow/e2e-bookInfoTests-v1alpha3.sh
1891bc9cde4c7c65b73e45447c9e5e80615cc0db
link
/test e2e-bookInfo-envoyv2-v1alpha3

prow/e2e-simpleTests.sh
1891bc9cde4c7c65b73e45447c9e5e80615cc0db
link
/test e2e-simple

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: quanjielin
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: costinm
Assign the PR to them by writing /assign @costinm in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

istioctl/OWNERS
pilot/OWNERS
tests/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: quanjielin
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: costinm
Assign the PR to them by writing /assign @costinm in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

pilot/OWNERS
tests/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@quanjielin: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
1891bc9cde4c7c65b73e45447c9e5e80615cc0db
link
/test istio-pilot-e2e

prow/e2e-bookInfoTests.sh
1891bc9cde4c7c65b73e45447c9e5e80615cc0db
link
/test e2e-bookInfo

prow/e2e-bookInfoTests-v1alpha3.sh
1fb1bdad31395231e6520ba5745e21b1a62e4147
link
/test e2e-bookInfo-envoyv2-v1alpha3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@quanjielin: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-bookInfoTests.sh
1891bc9cde4c7c65b73e45447c9e5e80615cc0db
link
/test e2e-bookInfo

prow/e2e-bookInfoTests-v1alpha3.sh
1fb1bdad31395231e6520ba5745e21b1a62e4147
link
/test e2e-bookInfo-envoyv2-v1alpha3

prow/istio-pilot-e2e.sh
1fb1bdad31395231e6520ba5745e21b1a62e4147
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@quanjielin: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-bookInfoTests-v1alpha3.sh
1fb1bdad31395231e6520ba5745e21b1a62e4147
link
/test e2e-bookInfo-envoyv2-v1alpha3

prow/istio-pilot-e2e.sh
1fb1bdad31395231e6520ba5745e21b1a62e4147
link
/test istio-pilot-e2e

prow/istio-unit-tests.sh
cdddbbd179c557dba1631b54c35e2bd7f384ee51
link
/test istio-unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@quanjielin: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
1fb1bdad31395231e6520ba5745e21b1a62e4147
link
/test istio-pilot-e2e

prow/istio-unit-tests.sh
cdddbbd179c557dba1631b54c35e2bd7f384ee51
link
/test istio-unit-tests

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
cdddbbd179c557dba1631b54c35e2bd7f384ee51
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e-bookInfoTests-v1alpha3.sh
cdddbbd179c557dba1631b54c35e2bd7f384ee51
link
/test e2e-bookInfo-envoyv2-v1alpha3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@quanjielin: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
cdddbbd179c557dba1631b54c35e2bd7f384ee51
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e-bookInfoTests-v1alpha3.sh
cdddbbd179c557dba1631b54c35e2bd7f384ee51
link
/test e2e-bookInfo-envoyv2-v1alpha3

prow/istio-pilot-e2e.sh
cdddbbd179c557dba1631b54c35e2bd7f384ee51
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@quanjielin: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
cdddbbd179c557dba1631b54c35e2bd7f384ee51
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/istio-pilot-e2e.sh
cdddbbd179c557dba1631b54c35e2bd7f384ee51
link
/test istio-pilot-e2e

prow/e2e-bookInfoTests-v1alpha3.sh
fbd9965cd0b738a5d4a3702a988333543b427f26
link
/test e2e-bookInfo-envoyv2-v1alpha3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@quanjielin: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-bookInfoTests-v1alpha3.sh
fbd9965cd0b738a5d4a3702a988333543b427f26
link
/test e2e-bookInfo-envoyv2-v1alpha3

prow/istio-pilot-e2e.sh
fbd9965cd0b738a5d4a3702a988333543b427f26
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@quanjielin: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-bookInfoTests-v1alpha3.sh
fbd9965cd0b738a5d4a3702a988333543b427f26
link
/test e2e-bookInfo-envoyv2-v1alpha3

prow/istio-pilot-e2e.sh
fbd9965cd0b738a5d4a3702a988333543b427f26
link
/test istio-pilot-e2e

prow/istio-unit-tests.sh
9aa3ab1240aa035e74c24a59b705cc932b2d2bb7
link
/test istio-unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@quanjielin: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-bookInfoTests-v1alpha3.sh
fbd9965cd0b738a5d4a3702a988333543b427f26
link
/test e2e-bookInfo-envoyv2-v1alpha3

prow/istio-pilot-e2e.sh
fbd9965cd0b738a5d4a3702a988333543b427f26
link
/test istio-pilot-e2e

prow/istio-unit-tests.sh
9aa3ab1240aa035e74c24a59b705cc932b2d2bb7
link
/test istio-unit-tests

prow/e2e-simpleTests.sh
9aa3ab1240aa035e74c24a59b705cc932b2d2bb7
link
/test e2e-simple

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@quanjielin: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-bookInfoTests-v1alpha3.sh
fbd9965cd0b738a5d4a3702a988333543b427f26
link
/test e2e-bookInfo-envoyv2-v1alpha3

prow/istio-unit-tests.sh
9aa3ab1240aa035e74c24a59b705cc932b2d2bb7
link
/test istio-unit-tests

prow/e2e-simpleTests.sh
9aa3ab1240aa035e74c24a59b705cc932b2d2bb7
link
/test e2e-simple

prow/istio-pilot-e2e.sh
9aa3ab1240aa035e74c24a59b705cc932b2d2bb7
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@quanjielin: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
9aa3ab1240aa035e74c24a59b705cc932b2d2bb7
link
/test istio-unit-tests

prow/e2e-simpleTests.sh
9aa3ab1240aa035e74c24a59b705cc932b2d2bb7
link
/test e2e-simple

prow/istio-pilot-e2e.sh
9aa3ab1240aa035e74c24a59b705cc932b2d2bb7
link
/test istio-pilot-e2e

prow/e2e-bookInfoTests.sh
9aa3ab1240aa035e74c24a59b705cc932b2d2bb7
link
/test e2e-bookInfo

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@quanjielin: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-simpleTests.sh
9aa3ab1240aa035e74c24a59b705cc932b2d2bb7
link
/test e2e-simple

prow/e2e-bookInfoTests.sh
9aa3ab1240aa035e74c24a59b705cc932b2d2bb7
link
/test e2e-bookInfo

prow/istio-pilot-e2e.sh
008ce3a2a24508fffcdc170eeeaf02d8cdf7a897
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@quanjielin: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-simpleTests.sh
9aa3ab1240aa035e74c24a59b705cc932b2d2bb7
link
/test e2e-simple

prow/istio-pilot-e2e.sh
008ce3a2a24508fffcdc170eeeaf02d8cdf7a897
link
/test istio-pilot-e2e

prow/e2e-bookInfoTests.sh
008ce3a2a24508fffcdc170eeeaf02d8cdf7a897
link
/test e2e-bookInfo

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@quanjielin: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-simpleTests.sh
9aa3ab1240aa035e74c24a59b705cc932b2d2bb7
link
/test e2e-simple

prow/istio-pilot-e2e.sh
008ce3a2a24508fffcdc170eeeaf02d8cdf7a897
link
/test istio-pilot-e2e

prow/e2e-bookInfoTests.sh
008ce3a2a24508fffcdc170eeeaf02d8cdf7a897
link
/test e2e-bookInfo

prow/e2e-bookInfoTests-v1alpha3.sh
008ce3a2a24508fffcdc170eeeaf02d8cdf7a897
link
/test e2e-bookInfo-envoyv2-v1alpha3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@quanjielin: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-simpleTests.sh
9aa3ab1240aa035e74c24a59b705cc932b2d2bb7
link
/test e2e-simple

prow/istio-pilot-e2e.sh
008ce3a2a24508fffcdc170eeeaf02d8cdf7a897
link
/test istio-pilot-e2e

prow/e2e-bookInfoTests.sh
008ce3a2a24508fffcdc170eeeaf02d8cdf7a897
link
/test e2e-bookInfo

prow/e2e-bookInfoTests-v1alpha3.sh
008ce3a2a24508fffcdc170eeeaf02d8cdf7a897
link
/test e2e-bookInfo-envoyv2-v1alpha3

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
008ce3a2a24508fffcdc170eeeaf02d8cdf7a897
link
/test istio-pilot-e2e-envoyv2-v1alpha3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@quanjielin: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
008ce3a2a24508fffcdc170eeeaf02d8cdf7a897
link
/test istio-pilot-e2e

prow/e2e-bookInfoTests.sh
008ce3a2a24508fffcdc170eeeaf02d8cdf7a897
link
/test e2e-bookInfo

prow/e2e-bookInfoTests-v1alpha3.sh
008ce3a2a24508fffcdc170eeeaf02d8cdf7a897
link
/test e2e-bookInfo-envoyv2-v1alpha3

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
008ce3a2a24508fffcdc170eeeaf02d8cdf7a897
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e-simpleTests.sh
008ce3a2a24508fffcdc170eeeaf02d8cdf7a897
link
/test e2e-simple

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test istio-pilot-e2e-envoyv2-v1alpha3

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: quanjielin
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: costinm
Assign the PR to them by writing /assign @costinm in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

install/OWNERS
pilot/OWNERS
tests/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@quanjielin: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
008ce3a2a24508fffcdc170eeeaf02d8cdf7a897
link
/test istio-pilot-e2e

prow/e2e-bookInfoTests.sh
008ce3a2a24508fffcdc170eeeaf02d8cdf7a897
link
/test e2e-bookInfo

prow/e2e-bookInfoTests-v1alpha3.sh
008ce3a2a24508fffcdc170eeeaf02d8cdf7a897
link
/test e2e-bookInfo-envoyv2-v1alpha3

prow/e2e-simpleTests.sh
25dc4d3f9d9f30f19ff2c5ff90fee7439241cc8e
link
/test e2e-simple

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@quanjielin: PR needs rebase.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@quanjielin: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-simpleTests.sh
25dc4d3f9d9f30f19ff2c5ff90fee7439241cc8e
link
/test e2e-simple

prow/istio-pilot-e2e.sh
25dc4d3f9d9f30f19ff2c5ff90fee7439241cc8e
link
/test istio-pilot-e2e

prow/e2e-bookInfoTests.sh
25dc4d3f9d9f30f19ff2c5ff90fee7439241cc8e
link
/test e2e-bookInfo

prow/e2e-dashboard.sh
54ef64a32837b6e1c46946bce838f0e9bb535560
link
/test e2e-dashboard

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@quanjielin: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-simpleTests.sh
25dc4d3f9d9f30f19ff2c5ff90fee7439241cc8e
link
/test e2e-simple

prow/istio-pilot-e2e.sh
25dc4d3f9d9f30f19ff2c5ff90fee7439241cc8e
link
/test istio-pilot-e2e

prow/e2e-bookInfoTests.sh
25dc4d3f9d9f30f19ff2c5ff90fee7439241cc8e
link
/test e2e-bookInfo

prow/e2e-dashboard.sh
54ef64a32837b6e1c46946bce838f0e9bb535560
link
/test e2e-dashboard

prow/e2e-mixer-no_auth.sh
54ef64a32837b6e1c46946bce838f0e9bb535560
link
/test e2e-mixer-no_auth

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@quanjielin: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-simpleTests.sh
25dc4d3f9d9f30f19ff2c5ff90fee7439241cc8e
link
/test e2e-simple

prow/istio-pilot-e2e.sh
25dc4d3f9d9f30f19ff2c5ff90fee7439241cc8e
link
/test istio-pilot-e2e

prow/e2e-bookInfoTests.sh
25dc4d3f9d9f30f19ff2c5ff90fee7439241cc8e
link
/test e2e-bookInfo

prow/e2e-dashboard.sh
54ef64a32837b6e1c46946bce838f0e9bb535560
link
/test e2e-dashboard

prow/e2e-mixer-no_auth.sh
54ef64a32837b6e1c46946bce838f0e9bb535560
link
/test e2e-mixer-no_auth

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
54ef64a32837b6e1c46946bce838f0e9bb535560
link
/test istio-pilot-e2e-envoyv2-v1alpha3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@quanjielin: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
25dc4d3f9d9f30f19ff2c5ff90fee7439241cc8e
link
/test istio-pilot-e2e

prow/e2e-bookInfoTests.sh
25dc4d3f9d9f30f19ff2c5ff90fee7439241cc8e
link
/test e2e-bookInfo

prow/e2e-mixer-no_auth.sh
54ef64a32837b6e1c46946bce838f0e9bb535560
link
/test e2e-mixer-no_auth

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
54ef64a32837b6e1c46946bce838f0e9bb535560
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e-dashboard.sh
6fc015b6e913982f8a5ef6294ccf2074b0ade064
link
/test e2e-dashboard

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@quanjielin: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
25dc4d3f9d9f30f19ff2c5ff90fee7439241cc8e
link
/test istio-pilot-e2e

prow/e2e-bookInfoTests.sh
25dc4d3f9d9f30f19ff2c5ff90fee7439241cc8e
link
/test e2e-bookInfo

prow/e2e-dashboard.sh
6fc015b6e913982f8a5ef6294ccf2074b0ade064
link
/test e2e-dashboard

prow/istio-unit-tests.sh
d3c01acb09793a2b1d1baf17dccf031e7eb6c251
link
/test istio-unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@quanjielin: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
25dc4d3f9d9f30f19ff2c5ff90fee7439241cc8e
link
/test istio-pilot-e2e

prow/e2e-bookInfoTests.sh
25dc4d3f9d9f30f19ff2c5ff90fee7439241cc8e
link
/test e2e-bookInfo

prow/istio-unit-tests.sh
d3c01acb09793a2b1d1baf17dccf031e7eb6c251
link
/test istio-unit-tests

prow/e2e-dashboard.sh
d3c01acb09793a2b1d1baf17dccf031e7eb6c251
link
/test e2e-dashboard

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

it won't override tls settings on gateway.

@quanjielin: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
25dc4d3f9d9f30f19ff2c5ff90fee7439241cc8e
link
/test istio-pilot-e2e

prow/e2e-bookInfoTests.sh
25dc4d3f9d9f30f19ff2c5ff90fee7439241cc8e
link
/test e2e-bookInfo

prow/e2e-dashboard.sh
d3c01acb09793a2b1d1baf17dccf031e7eb6c251
link
/test e2e-dashboard

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
0ae0f658ab9aab6a974c5fe46c2a81c428a8260c
link
/test istio-pilot-e2e-envoyv2-v1alpha3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@quanjielin: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
25dc4d3f9d9f30f19ff2c5ff90fee7439241cc8e
link
/test istio-pilot-e2e

prow/e2e-bookInfoTests.sh
25dc4d3f9d9f30f19ff2c5ff90fee7439241cc8e
link
/test e2e-bookInfo

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
0ae0f658ab9aab6a974c5fe46c2a81c428a8260c
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e-dashboard.sh
0ae0f658ab9aab6a974c5fe46c2a81c428a8260c
link
/test e2e-dashboard

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@quanjielin: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
25dc4d3f9d9f30f19ff2c5ff90fee7439241cc8e
link
/test istio-pilot-e2e

prow/e2e-bookInfoTests.sh
25dc4d3f9d9f30f19ff2c5ff90fee7439241cc8e
link
/test e2e-bookInfo

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
0ae0f658ab9aab6a974c5fe46c2a81c428a8260c
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e-dashboard.sh
0ae0f658ab9aab6a974c5fe46c2a81c428a8260c
link
/test e2e-dashboard

prow/istio-unit-tests.sh
0c9a03d24d67ae2097dddfdf9eed2e38c19ded3c
link
/test istio-unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

@quanjielin: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
25dc4d3f9d9f30f19ff2c5ff90fee7439241cc8e
link
/test istio-pilot-e2e

prow/e2e-bookInfoTests.sh
25dc4d3f9d9f30f19ff2c5ff90fee7439241cc8e
link
/test e2e-bookInfo

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
0ae0f658ab9aab6a974c5fe46c2a81c428a8260c
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/istio-unit-tests.sh
0c9a03d24d67ae2097dddfdf9eed2e38c19ded3c
link
/test istio-unit-tests

prow/e2e-dashboard.sh
0c9a03d24d67ae2097dddfdf9eed2e38c19ded3c
link
/test e2e-dashboard

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test istio-unit-tests


👀 Data preview of table

In this PR, I create one route for getting the structure of a database with its tables and another route for getting a data preview of a table.

Also, please add:
http://localhost:3000
https://localhost:3000
to the CORS config, since it is the frontend port that request coming from.

Please add the data_catalog_items information into /data-source/

There already is a route to get all data catalog items: GET http://localhost:8000/data-catalog/


Fix issue #5076: Integration test github action

This pull request fixes #5076.
This issue has been successfully resolved. The PR effectively:

Separated the large eval-runner workflow into two distinct workflows:

A new integration-runner.yml for integration tests
The original eval-runner.yml now focused solely on SWE-Bench evaluation

Properly configured the triggers for the new integration-runner workflow to only execute:

When a PR is labeled with 'integration-test'
When manually triggered via workflow dispatch

Successfully moved all necessary prerequisites and configuration sections related to integration testing to the new workflow file while maintaining the functionality.

The solution meets all requirements specified in the original issue, particularly the important condition that the action should only run when labeled or manually triggered. The separation of concerns will make the workflows more maintainable and focused on their specific tasks.
Recommended for review and merge as this represents a clean separation of the evaluation workflows without changing their core functionality.
Automatic fix generated by OpenHands 🙌

To run this PR locally, use the following command:
docker run -it --rm   -p 3000:3000   -v /var/run/docker.sock:/var/run/docker.sock   --add-host host.docker.internal:host-gateway   -e SANDBOX_RUNTIME_CONTAINER_IMAGE=docker.all-hands.dev/all-hands-ai/runtime:eaf3057-nikolaik   --name openhands-app-eaf3057   docker.all-hands.dev/all-hands-ai/openhands:eaf3057

@openhands-agent The last run-integration-tests job, which was added by this PR, has failed. Use the github API to retrieve and read the job logs, and fix it.

I think enyst has eyes on this.

Also did you get Haiku and Deepseek setup? Referring to the description:
"Please note that Haiku and Deepseek would need to be set up, if we want to do this here. Deepseek has been set up in the past, but it's not working (key depleted?)."

Looks good! Just had a question for my own curiosity. Do you know the cost associated with running these integration tests daily for haiku and deepseek?

They're 6 tasks, each limited to 10 iterations max. 2/6 go on the internet. Nevertheless, the costs I'm seeing with Haiku are USD 0.02-0.05 per task.
Deepseek is lower.
I will fix this to display them all by default. I think it looks super reasonable, though?


FAQ menu is cut off for no reason

Where to find the issue

https://www.coronawarn.app/de/faq/results/
https://www.coronawarn.app/en/faq/results/

Describe the issue
The FAQ menu is sometimes cut off for no obvious reason:

Stepps to reproduce

Access e.g. https://www.coronawarn.app/de/faq/results/#interoperability_countries via a dekstop browser
See that the menu is cut off although there is enough space on the bottom available

Confirm fixed with https://github.com/corona-warn-app/cwa-website/pull/2698.

@Ein-Tim
Are you also seeing a horizontal scroll bar for the menu when you view https://www.coronawarn.app/de/faq/results/?

even when the browser window is very wide.

@Ein-Tim

I submitted https://github.com/corona-warn-app/cwa-website/issues/2701 for the horizontal scroll-bar issue. There is one long German word "Hintergrundaktualisierung" which caused this issue.


Max crawled file size

Adding max-file-size to prevent files above a certain size from being included in input:

Also adjusting command line args to kebab-case for consistency and supporting kebab-case or snake_case values in arcodeconf.yml

@alexdredmon If you like the PR I just submitted for improving .gitignore handling, I'd recommend you merge that, then update the resulting code so the max size filter is applied in the UploadedFileFilter.


use duecredit for citations of Python software

this one
https://github.com/duecredit/duecredit

closing because this is an issue related to the paper, and this is no longer the "paper" repository


Current master does not have get(descriptor, success) implementation

The current commit on the master branch doesn't have the get(descriptor, success) implementation for the datasource. If this is intentional, will you please let me know the reason? If it isn't, just let me know, and I will submit an pull request for it.

I must have been looking at the wrong commit. I see it now! Thanks!


WIP: Post sxt gui cleanup

Here's my local working branch. This is the branch I'm using on my local machine and where I install stx-gui.
Don't Merge

I have one more change on my local. Need to run more sanity checks on my side...

LGTM Getting caught up on the backlog


add auto crouch feature

automatically crouches in the air when jumping

amazing useless feature

^

Bunnyhop doesn't work for me since I use +crouchjump.
However, if bunnyhop crouched (and uncrouched) automatically, this would be nice.


Make web frontend optional

Is your feature request related to a problem? Please describe.
Some customers do not need the web interface, but the other automation components (i.e. tag-based attachment, association, and propagation) are very valuable. Additionally, several of the services that are used in the web interface aren't supported in GovCloud (CloudFront, AppSync).
Describe the feature you'd like
Make the web interface an optional component so that customers that don't require that functionality can opt out of deploying it. This should also help make this solution usable in GovCloud.
Additional context

+1

@senorkrabs Thanks for the request. We have added this in the backlog and will review for a future release.

+1 agreed.

We are investigating this feature request. Thanks for opening the issue.

We have developed this feature. It will be shipped in the next release.


Complete the restore of a cluster backed up with manta migrate backup

This depends on functionality added at https://github.com/eth-cscs/mesa/pull/4

done


Can't scroll inner listview when setenabled(false)

When there is an inner ListView, it is no longer scrollable if the SlidingUpPanelLayout.setEnabled(false) is called

Thx, that seems like a bug. Will fix for next release

This is also happening when using setTouchEnabled(false)

Actually, I thought about it more. Can't you just use setTouchEnabled?

Fixed in https://github.com/umano/AndroidSlidingUpPanel/commit/966fee4f049c43c1fded6371d1501d761f043395. Will be released in 3.3