CWE-362 - anyio Race Condition

chore:	Fixes CWE-362 - anyio Race Condition.
Affected versions of this package are vulnerable to Race Condition in
_eventloop.get_asynclib() that cause crashes when multiple event loops
of the same backend are running in separate threads and simultaneously
attempting to use AnyIO for the first time.

What this PR does / why we need it:
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Type of changes
Please delete options that are not relevant.

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

Feature/Issue validation/testing:
Please describe the tests that you ran to verify your changes and relevant result summary. Provide instructions so it can be reproduced.
Please also list any relevant details for your test configuration.

[ ] Test A

[ ] Test B

Logs

Special notes for your reviewer:

Please confirm that if this PR changes any image versions, then that's the sole change this PR makes.

Checklist:

[ ] Have you added unit/e2e tests that prove your fix is effective or that this feature works?
[ ] Has code been commented, particularly in hard-to-understand areas?
[ ] Have you made corresponding changes to the documentation?

Release note:

Re-running failed tests

/rerun-all - rerun all failed workflows.
/rerun-workflow <workflow name> - rerun a specific failed workflow. Only one workflow name can be specified. Multiple /rerun-workflow commands are allowed per comment.

Building h5py requires pkg-config unless the HDF5 path is explicitly specified using the environment variable HDF5_DIR. For more information and details, see https://docs.h5py.org/en/stable/build.html#custom-installation

It is fixed as part of https://github.com/kserve/kserve/pull/3598/files#diff-a4f8129d1b3802e812533311dccd5fed46eb3d88c6a899c90fe9bcf431399ac6R19

Closing, if the alert is still valid, will send a PR later.


Take multiple Pictures

hi, i would like to take multiple pictures with your CameraActivity. At the moment i Build an Intent with CameraActivity.IntentBuilder, start the Intent with startActivityForResult and get the Picture in onActivityResult. But i can only take one Picture on every startActivityForResult().
Maybe it's possible to set an int "maxPictures" on CameraActivity.IntentBuilder and receive all Pictures as String-Array in onActivityResult? The CameraActivity should return all Picture-Paths if the "maxPictures"-Value is reached or the User has pressed the return-Button.
Are you interested in this feature? And if you're interested, how would you implement this feature?

Are you interested in this feature?

It's not an itch that I need to scratch at the present time, if that is what you mean.

how would you implement this feature?

Off the cuff, it might require a substantial rewrite of the library. Your proposed API seems reasonable, but there is a fair bit of code that assumes that we are only taking one picture at a time.

Ok, we will solve it ourselves. Thank you!


Added handling of libinput gesture events

This PR adds handling of libinput gesture events with API for gesture.swipe and gesture.pinch.

This looks good so far. But is missing the actual handling of the touch signals in compositor/seat.c. I think I've implemented everything that can be passed to wl programs, but maybe the protocol has been updated since. If the programs can't catch these and are mainly meant for compositor to be read the bool return value doesn't really make sense as the input won't go to client anyways.

I'm working on it. Will push it in coming days.

@Hummer12007 any updates?? can I be of any help?

Oh, that reminds me. I'll take a look at during the week.

Any updates?

I forgot about it before, but it's definitely postponed now (as sway is probably migrating off wlc).


Changing save and manual linting to async mode, to prevent UI freeze.

Adapted all modes of linting to use the queue.Daemon task queue,
including 'load/save', 'save only' and 'manual'. This prevents slow
linters from blocking the interface (e.g. pylint).

I believe this solves https://github.com/SublimeLinter/SublimeLinter3/pull/152 and https://github.com/SublimeLinter/SublimeLinter3/issues/267.
The Travis build is failing. The thing is: I can't get it to work on my computer, even on the current master branch. I must be doing something wrong. For some reason, it seems the pep257 command is trying to decode the commands.py file as ascii.

:+1:

:+1: Need this! It's very annoying when linting freeze Sublime Text.

:+1:

Just gave this a go locally, works really well. No more UI lockups while saving. :ok_hand:

++

:+1:

Sorry, life got in the way, and SL/you suffered. Thank you for your contribution!


Commit breaks tests

This commit https://github.com/jenkinsci/puppet-jenkins/commit/a2e21e8733909799bb5285230234892858712a9a adds test but without puppet_helper.groovy implementation breaks beaker tests as there is no implementation

Fixed by https://github.com/jenkinsci/puppet-jenkins/pull/752


how know my fastadapter is in fillter ?

There is any way to know list is in filltering ?
i want to add item to list only when user close all search.
Thanks

@SeyedAliFarjaD the easiest is to just get the ItemFilter from the ItemAdapter and check if the constraint is null or empty

something like this
TextUtils.isEmpty(((ItemAdapter.ItemFilter)fastItemAdapter.getItemFilter()).getConstraint().toString())

Thank you.


[RC3] Inline Rename crashes with MissingMethodException

This is what happens if Inline Rename is enabled:

@Pilchie any ideas? I updated Roslyn packages to the latest available 2.0.0-rc4-61327-05. VS loads slightly older ones:

OK, I tried all 2.0.0-rc4-61324-XX packages available on https://dotnet.myget.org/feed/roslyn/package/nuget/Microsoft.CodeAnalysis and no one contained exactly same binaries as RC3 loads from c:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\Common7\IDE\CommonExtensions\Microsoft\ManagedLanguages\VBCSharp\LanguageServices\ (I've compared SHA-1 hashes).

Updating System.Immutable.Collections package to 1.3.1, which is loaded by RC3 has not helped either.

I'm out of ideas.

@KevinRansom didn't you say that this was caused by an issue with a System.Collections.Immutable version number?

Yes ... it looks that way.  We need to ensure that we are using the exact same version as the RTM bits.  I seem to recall that Roslyn may have rolled back a change for RC3 ... and we probably didn't.  We will have to drill in to see if this issue repro's on RTM.  if it does we will need to figure out what to do.

cc @jasonmalinowski for FYI

This is a breaking change that Roslyn did in roslyn/commit@806a804bd18c19f39b98871be07241398f6ab7d0. We rolled it back because it broke TypeScript. Upgrading to newer packages and updating code accordingly should be sufficient to unblock this.

And yes, the exception is confusing: "missing method" in this case means it can't find the property getter that is matching by return type, since the return type got changed.

As I already wrote, updating System.Immutable.Collections had not helped. Anyone, try it again, maybe I'm doing something wrong.

@vasily-kirichenko It may require us generating a build with internal bits to get Roslyn references "right".  @KevinRansom is looking into doing this over the weekend to see if we can get something working by next week.  If we can get a successful build with no regressions from RC3 + VSIX, then we'll try to make a case to get this in for RTM...such a change would be subject to review in our shiproom.

@cartermp Interesting thing's just happened: I was on my fix-quick-info branch and Inline Rename worked OK on RC3 (Ctrl+F5). However, on vs2017-rtm branch it's crashed.

The difference is this:

And of course these

I'm just very surprised that it works with rc2 Roslyn packages, but does not with the latest rc3.

It was explained to me like this ...

In November Roslyn made an API breaking change.
F# built against the updated (with breaking change) APIs
In January the breaking change was rolled back in the RC3 branch.
We didn't discover that because of the same reason we had to ship the update MSI and VSIX
separately.

Over the weekend I will update the references to the correct set, re-enable the feature, and hopefully get the change approved for RTM ... however there really is no guarantee of that.
I hope this helps with understanding what has happened.

It may require us generating a build with internal bits to get Roslyn references "right".

Maybe create a sub repository containing proper roslyn binaries, that you at msft could grab directly, no nuget involved, as I suspect do TS and Python teams? I doubt anybody would against it, because the binaries are already published via that myget feed (the problem is that there are no exactly same versions as VS uses).

Everything we need should be published on myget.  Roslyn has daily builds pushed to myget.  Anyway -I'm not too worried that we can get it sorted now we know what the issue is.

Because changing Roslyn references to the correct version breaks Find All References, this is going to go into a microupdate for VS 2017.  We're too deep into the RTM stabilization period to get the changes needed to un-break Inline Rename, address the issue in Find All References, and test again for ensuring there are no regressions.

Fixed in master.


fix(ssa refactor): Ignore array out of bounds errors when enable_side_effects is false

Description

Problem*
When enable_side_effects is false, we are meant to be in a false branch of an if that was not taken, so we should ignore side effects causing the program to fail, such as array out of bounds errors. I've added a check for this to only panic for array index of out of bounds errors if enable side effects is not known to be false.
This fixes the bug in #1629 but means the issue will still appear if the if uses a witness as its condition, as it would not be known to be false. I've changed the logic to only panic if enable_side_effects is known to be true rather than not known to be false.
Resolves #1629
Summary*

Documentation

[ ] This PR requires documentation updates when merged.

[ ] I will submit a noir-lang/docs PR.

[ ] I will request for and support Dev Rel's help in documenting this PR.

Additional Context

PR Checklist*

[x] I have tested the changes locally.
[x] I have formatted the changes with Prettier and/or cargo fmt on default settings.

Hmm interesting problem, longer term we may have to ignore even more array out of bounds I guess you're implying? LGTM

Cool that change makes sense to me

Maybe a comment about the logic that led here? Probably surprising that it's usually ignored at first read

Also now I guess we want an issue for infrastructure for detecting if both sides would have an error, possibly a conservative setting that doesn't allow an error on either side but that I'm more speculative on

detecting if both sides would have an error, possibly a conservative setting that doesn't allow an error on either side but that I'm more speculative on

What do you mean by both sides here?

Deleted that comment, thought this came up more generally


Revert "Allocation rewrite"

Reverts vespa-engine/vespa#2963
@smorgrav
Broke the build.

Please review after the fact.

👍


Native file dialog extended - support

Another day another PR 😄
This solution works on linux (test on SteamDeck) with bundled dbus in this PR but if I try used system-sdk on macOS its failed. For now is working  on all native platforms (Windows/linux/macos) but problem will be probably with cross-compile because that task need system-sdk libs.

FWIW I have some NFD-extended bindings here that I'm using in a project https://github.com/hazeycode/znfd/blob/main/src/nfd.zig
It handles UTF-16 mode and doesn't involve translate-c

Nice 👍  we can combine your lib + dbus in system-sdk and zig-gamedev has new lib ;)

Closing this PR but in near feature a make new try with @hazeycode nfd + dbus in systemsdk


.editorconfig not working as intended - softTabs looks like it's being set, but isn't

My .editorconfig wasn't properly working on Atom (works on Sublime Text), so I wanted to try to debug what could be causing the issue.
From what I gathered it looked like the everything was working fine. Logging the TextEditor object shows that this package looks like it's setting the correct properties, but for some reason Atom itself isn't recognizing the change and shows some discrepancies inside the object:

Running the getSoftTabs() method in the console returns a false:

I was able to enable soft tabs through the console, if I did a atom.workspace.getActiveTextEditor().setSoftTabs(true);

Not sure how to fix this though. This looks like an Atom bug. Any thoughts?

Hi @mven - thank you very much for that report! :candy:
In my experience the Atom-platform can be considered as fairly stable.
I could imagine that this issue may be caused by a wrong sequence of events, namely the softtabs-setting may be overwritten after the editorconfig-package initially set it right. We have to do further investigations on this, if possible i will pick this issue up for the upcoming patch-release!

I have currently exactly the same issue.

Okay @mven - i guess i figured this one out. Editorconfig seems only working properly if the Core-Setting "Tab Type" of your Editor is set to "auto".
If this setting is set to any specific value, it overrides the editorconfig-changes in the last second. 😁
Please do me the favor to verify that finding! 🙏
So how going on with this. I can currently imagine two Options:

Inform the User with a Info-Notification (probably also offering to fix the setting)
Leave a "Warning" in the console (which will probably be seen if a user starts searching for the fault)

I am sorry, i made a mistake - unfortunately my previous answer is not solving the problem. I do further investigations. I beg your pardon for the noise.

Okay it seems i finally got to the ground of the problem, which is a call of TextEditor.handleTokenization being invoked by the displayBuffer. This overrides the Tab-settings. Since i couldn't figure out when this is being invoked and how to prevent it, i decided to override it as a first patch.
So this behavior is now confirmed and pinned down by specs (in the draft https://github.com/florianb/atom-editorconfig/tree/iss70).
I guess this will need a fix in the TextEditor-implementation - until this has be done i will block the handleTokenization-function to keep this issue fixed.

This bug is issue seems to be part of a more complex malfunction. I move its solution into a separate issue #81 and therefore close this issue. I'd appreciate if follow that issue, too.
Thanks for your patience. ☕

Great, thanks. I'll follow that issue.


Closing does not update the status

Firstly, thanks for a great plugin, but when closing the blind, the spinning/loading icon does not stop even if I update send 2 to myBlind/GET/positionState, any idea what could be causing this?

not an issue, sorry, all I had to do was to update the currentPosition to be the same as the targetPosition when the action is completed, works like a charm ;-)

Im not sure in which cases HomeKit needs the positionState. In my case it is absolutely the same you wrote above. When I set a new target position in HomeKit the plugin sends out the value via MQTT. When my blind reaches the target position it sends out the same position value as the current one and the spinnig/loading icon stops. However the positionState works as well. You can take a look in the log while controlling your blind. :)


Adds GenPath, providing an ad-hoc mechanism of controlling arbitrary Path generation

Given some A such that Arbitrary[A] and Show[A], provides Arbitrary[GenPath[B,T,S,A]] which will generate an arbitrary Path[B,T,S] using the string representation of arbitrary As for the segments.
Allows for different segment generation schemes by changing the type of A. The default arbitrary instances for Path use a random string.

Otherwise, LGTM!

@jedesah Ok, all set. Thanks for the quick turnaround on review!

The label is already set to ready but :+1:


[ci] Update .vsts-ci.yml for Azure Pipelines

Upgrade Azure VM Scale Set to use Mariner (Azure Linux) systems.

I've been requested by the service team within the company to upgrade the OS of Azure Virtual Machine Scale Set (VMSS) from open-source Ubuntu image to an Azure native Linux version called Mariner...
Since upgrading is simply not feasible. I have to shut down the old VMSS and create a new one using the Mariner system.
I'm almost done with only one CI test reporting segmentation fault. I'm trying to fix that.

It is weird that cpp tests sometimes randomly segmentation faults. Note that even though we are using the Mariner image for VMSS, we still use docker to pull the Ubuntu image within the VMSS and run the tests on the same Ubuntu container as before.
https://dev.azure.com/lightgbm-ci/lightgbm-ci/_build/results?buildId=15574&view=logs&j=c1aa5445-36f0-58f5-2c69-68691d629457&t=c07c8f5b-ba24-5225-6ddc-80219dbcdc35

an Azure native Linux version called Mariner.

Got it, ok! I guess that's this? https://github.com/microsoft/CBL-Mariner
No problem, like you said...we run all the Linux tests in containers, so hopefully it shouldn't be too disruptive.

It is weird that cpp tests sometimes randomly segmentation faults

Thanks very much for providing that link to the CI run you're talking about! Yeah, I'm not sure if that's related to this change or not. There's been a very low level of activity in the repo over the last few weeks...I haven't seen that specific job segfault in other commits outside this PR, but there also just have not been very many CI runs recently.
I think it's ok to merge this and see if we observe more such problems. If we do that, can you leave the existing hosted runner VM running for a week or two so that we'd be able to switch back if the segfaults become more common?

Got it, ok! I guess that's this? https://github.com/microsoft/CBL-Mariner

Yes.
But I've debug this using a VM with the same setting as the VMSS and found that the segmentation fault happens very frequently. I'm afraid that wouldn't be acceptable. Hopefully I can find some more time to fix the issue.
It is weird because I'm debugging using a docker container created from an Ubuntu 22.04 image within the Mariner system, which is the same as our previous VMSS in CI.
I've manually triggered CI on master branch for several times yesterday and found no segmentation fault problems.

I've manually triggered CI on master branch for several times yesterday and found no segmentation fault problems.

Oh! Ok you're right, that's a serious problem and we should figure it out before merging. Thank you for being so thorough!
Let me know if there's anything I can do to help.

The root cause is the sanitizers in clang. Here is a very minimal reproducible case
int main(int argc, char** argv) {
  return 0;
}

Even this program compiled with clang++ and -fsanitize=address flag causes segmentation fault on the Ubuntu container started by the Mariner system.
Do you have any suggestion on this? @jameslamb @guolinke @jmoralez @StrikerRUS

People encountered the same issue here
https://stackoverflow.com/questions/77548589/compiling-a-minimal-cpp-program-with-fsanitize-address-causes-immediate-segfa

hmmmm I wasn't able to reproduce that with clang 14.0.0 (the version I see in those logs from the failed build) on godbolt (https://godbolt.org/z/MYx84dcv3) or in docker locally on my mac.
docker run \
  --rm \
  -it ubuntu:latest \
  /bin/bash

apt-get update
apt-get install -y \
    clang-14

cat << EOF >test.cpp
int main(int argc, char** argv) {
  return 0;
}
EOF

clang++-14 -Wall -O3 -fsanitize=address -o test.o ./test.cpp
./test.o
echo $?
# 0

Maybe this hack to allow the use of sudo is causing problems?
https://github.com/microsoft/LightGBM/blob/074b3e885503dfcb12a05268d6f4169054b15264/.vsts-ci.yml#L138-L140
Like maybe Mariner (or the docker repackaged for Mariner's tndf package manager) has a slightly different security model and that somehow shows up as a segfault?

I have another idea too... maybe it's because Mariner is using such an old version of the Docker Engine API?
On a failed build on the new runner (build link), I see the following:
/usr/bin/docker version --format '{{.Server.APIVersion}}'
'1.41'
Docker daemon API version: '1.41'
/usr/bin/docker version --format '{{.Client.APIVersion}}'
'1.41'
Docker client API version: '1.41'

On the most recent build of master (from few hours ago), which was successful and ran on the existing hosted runner not using Mariner (build link), I see:
/usr/bin/docker version --format '{{.Server.APIVersion}}'
'1.43'
Docker daemon API version: '1.43'
/usr/bin/docker version --format '{{.Client.APIVersion}}'
'1.43'
Docker client API version: '1.43'

The first release of v1.41 of the Docker Engine API was in May 2019 (https://github.com/moby/moby/pull/39208). That series ran until... February 2021, I think? (https://github.com/moby/moby/pull/42063).
v1.43 is the most recent version of the Docker Engine API (https://docs.docker.com/engine/api/version-history/).

Just tried with clang++17 and the issue disappear. I'll upgrade clang to use clang-17.

Just tried with clang++17 and the issue disappear. I'll upgrade clang to use clang-17

Ok I think that's alright for this.

The version of Docker could also be a potential reason. But given that we are urgent to migrate to Mariner, I'll upgrade the clang for now to quickly solve this issue, and investigate with the docker version later on.

Yeah I think that's ok! I understand it's something Microsoft considers time-sensitive.
And we get so much more test coverage per commit by having that hosted runner than we'd be able to with only free-tier resources...I think it's worth it.

Failure of gpu_source task with clang 17.
https://dev.azure.com/lightgbm-ci/lightgbm-ci/_build/results?buildId=15598&view=logs&j=582743ec-83fe-58c4-937e-4197b5816801
Retrigger to see if we can reproduce this error...
If this occurs frequently, I will restrict the usage of clang 17 to only the cpp tests task.

I found that without -DUSE_GPU=ON and with device_type=cpu, the test_engine.py can sometimes consume up to 70% of the 8GB memory in the container.
I guess that with device_type=gpu and gpu_use_dp=true, the memory consumption is going to reach the total memory on the VM. That's why the tasks sometimes fails.

I'll double the RAM of the VMSS...

reach the total memory on the VM. That's why the tasks sometimes fails.

interesting! So then could we revert the use of clang-17, to avoid the extra complexity in CI scripts?

So then could we revert the use of clang-17, to avoid the extra complexity in CI scripts?

Perhaps not. Because we are having two issues here

The segmentation fault in cpp_tests is due to the issue of using clang 14 with sanitizers using the Mariner VMSS.
The OOM is another issue due to the test_model_size test case consumes almost the full capacity of RAM in VM.

So we have to keep the clang 17 for Mariner VMSS and double the RAM in the VMSS.

Oh I see. Ok no problem.

Note that the Mariner image does not natively contain docker and git, so we installed these using the cloud-init tool to install docker and git when every VM is created in the VMSS. However, this doesn't seems to be 100% successful.
For example, this job fails with an undefined reference to git
https://dev.azure.com/lightgbm-ci/lightgbm-ci/_build/results?buildId=15608&view=logs&j=11c46b0e-4322-5d4e-fafd-abe3157be7c4
But according to the jobs we've run so far, I think this only occurs rarely (less than 1 in 10 times of the Azure Pipeline runs). So maybe we can ignore this for now and to merge the changes. And leave a better initialization of VMs in the future. WDYT? @jameslamb

I'll double the RAM of the VMSS...

Previously we have 8GB RAN for each VM (as well as previous VMSS using Ubuntu images). And now we have 16GB RAM. I see that large RAM do bring stability of the CI jobs.
Manually triggered 5 pipeline runs using the VMSS with 16GB RAM, and 4 out of 5 are succeed. Only one fails due to the initialization issue (did not successfully install git). However, the initialization issue rarely happens.


ClassNotFoundException when running maven plugin in non-forked mode

I configured the maven plugin as follows,
            <plugin>
                <groupId>org.mock-server</groupId>
                <artifactId>mockserver-maven-plugin</artifactId>
                <version>3.9.1</version>
                <configuration>
                    <serverPort>9090</serverPort>
                    <proxyPort>9091</proxyPort>
                    <logLevel>DEBUG</logLevel>
                    <!--<initializationClass>org.mockserver.maven.ExampleInitializationClass</initializationClass>-->
                </configuration>
                <executions>
                    <execution>
                        <id>pre-integration-test</id>
                        <phase>pre-integration-test</phase>
                        <goals>
                            <goal>start</goal>
                        </goals>
                    </execution>
                    <execution>
                        <id>post-integration-test</id>
                        <phase>post-integration-test</phase>
                        <goals>
                            <goal>stop</goal>
                        </goals>
                    </execution>
                </executions>
            </plugin>

and added a callback class as this
public class HelloCallback implements ExpectationCallback {

    public HelloCallback() {

    }

    @Override
    public HttpResponse handle(HttpRequest httpRequest) {
        for (Parameter parameter : httpRequest.getQueryStringParameters()) {
            if ("name".equals(parameter.getName())) {
                return response()
                        .withHeaders(new Header("Content-Type", "text/plain; charset=utf-8"))
                        .withBody("hello " + parameter.getName());
            }
        }
        return response()
                .withStatusCode(400)
                .withHeaders(new Header("Content-Type", "text/plain; charset=utf-8"))
                .withBody("Name not set!");
    }
}

and mocked the expectation in my test as this
    MockServerClient mockHello;

    @Before
    public void init() {
        mockHello = new MockServerClient("localhost", 9090);
        // Dynamic mocking
        mockHello.when(
                request()
                        .withMethod("GET")
                        .withPath("/hello"))
                .callback(callback().withCallbackClass(HelloCallback.class.getCanonicalName()));
    }

But when I build the project, maven complained java.lang.ClassNotFoundException
Is this a bug in the plugin?  Do we have a working example that I can reference?

@ryan-ju Is there any more info to that exception? I'm getting java.lang.ClassNotFoundException: com.jcraft.jzlib.Inflater, which seems to be a dependency of netty. Running mockserver on the command line and manually including the jzlib jar in the classpath does work, but I'm struggling with how to get those dependencies injected into the mockserver that is started by the maven build.

Sorry for the delay I've been busy on other projects. There are a number of integration tests that also act as example projects for the maven plugin.  Please see: https://github.com/jamesdbloom/mockserver/tree/master/mockserver-maven-plugin-integration-tests/src/integration-tests for the scenarios.  I suspect the specific scenario you are interested in is: https://github.com/jamesdbloom/mockserver/tree/master/mockserver-maven-plugin-integration-tests/src/integration-tests/mockserver-initializer-main-classpath or: https://github.com/jamesdbloom/mockserver/tree/master/mockserver-maven-plugin-integration-tests/src/integration-tests/mockserver-initializer-test-classpath depending on whether your org.mockserver.maven.ExampleInitializationClass is in the main or test classpath.
If these examples still don't resolve your issue please comment back and I'll look into it.  Any addition access you can give me to the project or information about how your classpath is structured could help.

I don't believe com.jcraft.jzlib.Inflater is used by Netty and I can't find any jzlib or jcraft dependencies for any part of Netty or the MockServer.  Do you have more information on this?

@jamesdbloom I worked around this by disabling gzip compression in my api calls, since that's what seemed to require the jcraft lib. I'm not sure why I thought it was related to this issue. It clearly isn't.

If you are still having issues with missing dependencies you may need to specifically add the dependency to the main or test classpath.  It may be that the class you are looking for is somehow included into the maven build in a non-standard way.  I current add all test classpath and main classpath artefacts as follows (see org.mockserver.maven.MockServerAbstractMojo):
/**
 * The main classpath location of the project using this plugin
 */
@Parameter(property = "project.compileClasspathElements", required = true, readonly = true)
protected List<String> compileClasspath;

/**
 * The test classpath location of the project using this plugin
 */
@Parameter(property = "project.testClasspathElements", required = true, readonly = true)
protected List<String> testClasspath;

private ClassLoader setupClasspath() throws MalformedURLException {
    if (compileClasspath != null && testClasspath != null) {
        URL[] urls = new URL[compileClasspath.size() + testClasspath.size()];
        for (int i = 0; i < compileClasspath.size(); i++) {
            urls[i] = new File(compileClasspath.get(i)).toURI().toURL();
        }
        for (int i = compileClasspath.size(); i < compileClasspath.size() + testClasspath.size(); i++) {
            urls[i] = new File(testClasspath.get(i - compileClasspath.size())).toURI().toURL();
        }

        ClassLoader contextClassLoader = URLClassLoader.newInstance(urls, Thread.currentThread().getContextClassLoader());
        Thread.currentThread().setContextClassLoader(contextClassLoader);
        return contextClassLoader;
    }
    return null;
}

Which version of maven are you using?  It may also be caused by your version of maven not correctly populating project.compileClasspathElements or project.testClasspathElements.  I can see some bugs relating to this in Maven 2.0 such as http://jira.codehaus.org/browse/MNG-1246

I'm going to close this issue, if you have more information that identifies a bug please open the issue again.


Do we really need introspect in this project.

I was exploring the source for the project and I see you guys are using Introspect, and wondering if it is really needed and same thing cannot be done without it?

Hey @TakasurAtWork, I decided Introspect is the most stable way of achieving this, you are always welcome to commit a PR if you have a solid workaround without it, have a nice day


Adopt a uniform toString() format

Fixes #232
Fixes #285
Fixes #220

In https://github.com/se-edu/addressbook-level4/issues/285#issuecomment-277497567 @damithc said:

It'll be good to have specialized methods for creating user visible message. Not sure where to put them though. May be give it a try and see where the PR takes us?

2 years later, now that we have moved all user-facing messages out of the model layer, the answer is obvious -- the logic layer, which together with the ui handles the user-facing parts of the application.


Logging support for HTTP server

Logging support (decoupled against HTTP implementation) for origin-sever.
Draft:
|+++++++++++++++++++|
| LogContextHandler | --> [InfoContext] + [ErrorContext] + [AccessContext] + [SyslogContext] + [StdoutContext]
|+++++++++++++++++++|

LogContextHandler;    // Global context handler object (interface)
LogContextHandler::InfoContext << "IP : " << std::to_string(_client_ip) << " ";     // operator<<(...) interface
LogContextHandler::InfoContext << "resource" << _client_access_resource << " ";
LogContextHandler::InfoContext::Flush();     // Writes to the file

( Similar implementation for other Context(s) )

Modification: Logging Context only consists of AccessContext and ErrorContext
ErrorContext: When a user-agent sends an invalid request OR server Failed to process the user-agent's request successfully, this context is fired.
AccessContext: If origin-server Successfully parsed the request from user-agent and sends a response successfully, this context is fired.
That's it, keep it simple and neat.
TODO:
Benchmark against Detached threads and Processing the Logging routine in the main process(by reordering Logging handlers at the end after sending a successful response to user-agent)

DONE!


UI-Change: Update datatype to make it consistent with JBoss and WebSphere

Context
The database type options in the solution are inconsistent with what're in JBoss and WebSphere.  The options should focus on database brand type, so that to remove confusion.
https://aka.ms/wls-vm-cluster

Follow-up task

[ ] The sentences and images in this javaee passwordless Configure passwordless database connections for Java apps on Oracle WebLogic Servers also need change.

Hello @edburns, could you review this PR?

Hello, @edburns
To my understanding, you thought that the consistency of Microsoft brand has a higher priority than the consistency between offers, right?

We also must make these brand changes for the labels for the non-passwordless connections.
I am not very sure about the intention of this sentence, could you give me more explanation?

...
In the Oracle User Story list o-152 as a Remote related link.

Feature created.


Install problem

Championify 2.0.8
macOS Sierra 10.12.6
League Of Legends 7.18 (but also 7.14-15-16-17)
After LOL introduced the ITEM CARD, I cant see in game the set created from Champioinify.
But Championify at open control what is imported and say LOCAL ITEM VERSION 7.18
I've tried to cancel lol and re-install it, but nothing.

You have your league Application selected correctly? Usually it's /Applications/League Of Legends.app

Stale, closing.


tegral-openapi-ktor form body content type

First of all my apologies if this is not the best place to do it, but I haven't found any other.
Second, thanks for this plugin. It's not easy to find a plugin for ktor that generates automatically the openUI documentation.
And then, to my question / issue.
I'm trying to describe in my API one endpoint which expect a form with several properties, one of them a File to upload and another one a JSON payload with information about that file.
Going through your documentation I've assumed that the way to define this is by
body {
    description = "Video to upload"
    required = true
    form {
    }
}

But I haven't found anywhere in the documentation or the code what I need to put within the "form" to define the properties expected in the body (in my case the File and the String with the payload). Am I in the right direction? Is there anything missing in the plugin? Am I missing something?
Thanks.

Hi! I'm not sure how your file is transmitted, but it could probably be something like this:
data class VideoUpload(
    val file: ByteArray, // I'm not sure what this should be or how this is transmitted
    val payload: String
)

body {
    // ...
    form {
        schema<VideoUpload>()
    }
}

This will not give you much information on the content of the payload, but it should be enough to make it work in Swagger. If you already have a data class that the properties get parsed into, you can use it as-is in your schema<>(). Otherwise, if you know the OpenAPI definition you may have to resort to building Swagger Core schemas, which give you all the flexibility of the original JSON files.
To be fair, I have never done things like file uploads with Swagger, so I'm not sure if I can be of much help here :/

Hi!
It is transmitted via a "multipart/form-data"
I have never done it before, that is why I don't know who to do it either :)
I found this page in swagger documentation in how to define it: https://swagger.io/docs/specification/2-0/file-upload/
It seems to be defined as a parameter of type form, but I don't see the way to do it with your library.

Hi!
It is transmitted via a "multipart/form-data"
I have never done it before, that is why I don't know who to do it either :)
I found this page in swagger documentation in how to define it: https://swagger.io/docs/specification/2-0/file-upload/
It seems to be defined as a parameter of type form, but I don't see the way to do it with your library.

I have found this way to do it:
body {
    description = "..."
    required = true
    "multipart/form-data" content {
        schema = MapSchema()
            .addProperty("file", FileSchema().description("The file to upload"))
            .addProperty("payload", JsonSchema().description("The payload"))
    }
}

which is what I was looking for and the resulting yaml file is in the same format as openAPI spec.
The only issue I have now is that I don't see how I can link an object to the JsonSchema like it can be done with
json { schema<RequestExample>() }

The only use of "linking a class" like this is for generating the schema. This is not needed if you manually create the schema like you're doing here.
If you mean adding an object as an example, this should still be doable via example = ... in the content { ... } block


RC tagging process doesn't follow semver2, confuses go modules

Describe the bug
Our RCs are tagged v1.2.3-rc4. However, rc4 isn't a semver identifier for "4th rc", it's a identifier for "pre-release of type rc4". This means the RC version is compared lexically, not numerically, which in turn means that rc10 is older than rc9 because 1 comes before 9. This makes go get downgrade to the wrong RC - I'm unsure on whether npm does.
Suggestions to fix are either v1.2.3-rc.4 (the bits after the dash are split by . and compared one by one) or v1.2.3-rc+4 (pre-release "rc", build 4) - both compare accurately, though I've tested neither.
This isn't normally a problem, except if we're at the tail end of a big reloaded project and are now poking at the release process.
Environment
N/A
To Reproduce
$ go get -d -u github.com/weaveworks/weave-gitops
go get: upgraded github.com/weaveworks/weave-gitops v0.7.0-rc11 => v0.7.0-rc9

Workaround
Open go.mod, change the version, and refresh go.sum with go mod tidy.
Or, go from rc9 to rca and do the alphabet instead.

The new instructions recommend rc.4


Inconsistent deploy success even with successful builds

Environment information
I can provide other details if needed, but having issues running command

Using custom image: public.ecr.aws/docker/library/node:18.17.0

Description
I have 30+ production branches on Amplify that have identical codebases. They are Gatsby JS sites which are fairly large and can take up to an hour each to build. They are connected to various webhooks to trigger rebuilds.
Since the Gen 2 dashboard has gone live we have been experiencing inconsistent deployments across these branches. Typically 4 or 5 out of the 30 branches will fail to deploy after the webhook is triggered, and manually rebuilding them off the same codebase will work inconsistently as well.
When I review the logs of the failed branches, there is nothing out of the ordinary there and no fatal error messages. The builds which fail to deploy end like this in their logs, which is identical to how the successful build logs finish
Completed phase: postBuild
Completed Frontend Build
Build completed successfully
Starting caching...
Creating cache artifact...
Created cache artifact
Uploading cache artifact...
Uploaded cache artifact
Caching completed
Starting build artifact upload process...
Uploading build artifact '__artifacts.zip'...
Build artifact upload completed
Starting environment caching...
Uploading environment cache artifact...
Uploaded environment cache artifact
Environment caching completed

Hey @AlexanderChiclana, thank you for reaching out. Could you provide us your App-Id and region?

Hey @AlexanderChiclana, thank you for reaching out. Could you provide us your App-Id and region?

thanks for the quick reply @ykethan
d3tqwuyiftpxq0
US East (Ohio)
us-east-2

@AlexanderChiclana 👋 , thanks for sharing the app information. We are investigating into it and will keep you posted with our findings.

@AlexanderChiclana 👋 , thanks for your continued patience. We have root caused the build failures for your app and the build process failed since the underlying build container ran out of memory. We have made improvements to the build process to surface the appropriate error message in the console and this should help with the debugging of the build failures.
Since your latest builds have completed successfully, can you please confirm if you are unblocked?

Closing this thread since we have improved the error message visibility in the console. Feel free to reopen this thread if the issue persists. Thanks!


Added projects aren't restored unless File -> Exit

When File -> Add Project Folder successfully adds a project, closing the window (Via cross or Alt + F4)it  means that the next time Atom is opened, the added project isn't present in Tree View.
However, shutting down Atom via File -> Exit successfully restores all added projects once Atom is reopened.
I thought adding a project folder should be considered a "permanent bookmark" and not be part of the session handling for open windows/tabs.
This is on Windows 7.

I realise now that atom-project-manager does exactly this. I expected the Add Project Folder to behave in the same way. Not sure what the purpose is otherwise.

@csholmq Which version of Atom are you using?
@maxbrunsfeld this issue sounds familiar, I think we've seen it before and that it was fixed. :older_man:

1.0.4 at the time of creating this ticket.

This is an issue for me too. I'm on Atom 1.1.0 on Windows 10. If I exit using File -> Exit, then the session is restored on next open. If I exit using the application's close button, then the session is not restored. Specifically, the project folders are still there, but none of the files or panes are restored. I just get my project tree on the left and an empty environment with no tabs open and only the one default pane.

This seems to be resolved for me on 1.1.0.

Confirmed fixed here too.


chore: make config.types to Vec<Type>

Issue Reference(s):
Partially Fixes #3164

Could you please explain what is high level goal in making such refactoring here? and how it relates to the another pr https://github.com/tailcallhq/tailcall/pull/3170
I think one of the goals of https://github.com/tailcallhq/tailcall/issues/3164 is to minimize or drop config entirely since and focus on ServiceDocument. In such a case is there any better option to implement the migration? Can we have a trait/s that could be implemented both by Config and ServiceDocument and gradually migrate to the abstraction?

@meskill we can have traits but it will just make stuff less maintainable
@tusharmath is thinking thinking to gradually convert structure config to that of service doc, later we can either drop config, or will have ability to throw better errors from config directly

@meskill we can have traits but it will just make stuff less maintainable
@tusharmath is thinking thinking to gradually convert structure config to that of service doc, later we can either drop config, or will have ability to throw better errors from config directly

Could you elaborate what do you mean by "traits making stuff less maintainable"?
With current approach I see the following issues:

this kind of migration will consist of multiple prs in similar manner where every pr does changes to the whole codebase
such prs also had to update json/yaml fixtures every time that expected to be dropped eventually anyway
that's literally sequence of breaking changes in the API from json/yaml on every pr to eventually drop the json/yaml support
in order to migrate to ServiceDocument or other representation you need one big pr once again

That's why I'm suggesting to consider different approaches like traits and/or intermediate types that could help in the migration process

We can first drop json yaml support from our CLI and update docs that should introduce one breaking change. The code then can continue getting refactored.
Json and Yaml aren't that used as much.
The whole codebase changes are another thing. I would solve that by adding a function that returns types and make the field private. Slowly do this for enums and unions also. Effectively turn config to actually internally embed a service doc directly.

We can first drop json yaml support from our CLI and update docs that should introduce one breaking change. The code then can continue getting refactored.
Json and Yaml aren't that used as much.
The whole codebase changes are another thing. I would solve that by adding a function that returns types and make the field private. Slowly do this for enums and unions also. Effectively turn config to actually internally embed a service doc directly.

That makes more sense.
I started to work on json/yaml removal

@meskill can you help with the fialing tests?
I guess just these 3 tests are failing.. I can't find the root cause for that

@meskill can you help with the fialing tests?
I guess just these 3 tests are failing.. I can't find the root cause for that

I see more than 3 tests failing and most of them I think failing because the change from BTreeMap to Vec changed the order of types in some cases

I see more than 3 tests failing and most of them I think failing because the change from BTreeMap to Vec changed the order of types in some cases

it's not because of the order, one N+1 test is failing and all from_json are failing
haven't checked for N+1 but for from_json I can't traceback to the root cause


Can't mount the mount...

If you cannot translate (that's italian) it says:

Cannot mount, only one socket bind is allowed, or something similar... pls could you fix?

If you cannot translate (that's italian) it says:
* Cannot mount, only one socket bind is allowed, or something similar... pls could you fix?

try manualy delete C:/Users/mfede/AppData/Local/Temp/mnt folder and reboot your PC

If this does not help, maybe another program block port 5572.
I my case it was "videostream", I uninstalled & rebooted, now all is fine.

please help, I already tried looking if some app is blocking the port but the only thing i saw that rclone is using the port as needed

please help, I already tried looking if some app is blocking the port but the only thing i saw that rclone is using the port as needed

Please do this steps:

restart application
try remount on fail(click mount button at right top corner)
send me a log /{USER_PATH}/sidenoder/debug_last.log

{
platform: 'win',
arch: 'x64',
version: '0.6.0',
sidenoderHome: 'C:/Users/Lee/sidenoder'
} win32 x64 [
'C:\Users\Lee\AppData\Local\Programs\sidenoder\sidenoder.exe'
]
icons list loaded
kmetas loaded
check_deps received adb
checkDeps()
check_deps received rclone
checkDeps()
{ cmd: 'C:\Users\Lee\sidenoder\rclone.exe --version' }
check_deps received zip
checkDeps()
{ cmd: 'C:\Users\Lee\sidenoder\7za.exe --help | findstr  "7-Zip"' }
check_deps received scrcpy
checkDeps()
{
cmd: 'C:\Users\Lee\Downloads\scrcpy-win64-v1.18\scrcpy.exe --version'
}
exec_stdout C:\Users\Lee\sidenoder\7za.exe --help | findstr  "7-Zip" 7-Zip (a) 19.00 (x64) : Copyright (c) 1999-2018 Igor Pavlov : 2019-02-21
7-Zip (a) 19.00 (x64) : Copyright (c) 1999-2018 Igor Pavlov : 2019-02-21
change_config received { key: 'donShown', val: true }
cfg.update donShown true
ERROR: exec_stderr C:\Users\Lee\Downloads\scrcpy-win64-v1.18\scrcpy.exe --version scrcpy 1.18
dependencies:

SDL 2.0.14
libavcodec 58.91.100
libavformat 58.45.100
libavutil 56.51.100

{ cmd: 'C:\Users\Lee\sidenoder\adb.exe start-server' }
exec_stdout C:\Users\Lee\sidenoder\rclone.exe --version rclone v1.55.1

os/type: windows
os/arch: amd64
go/version: go1.16.3
go/linking: dynamic
go/tags: cmount

checkMount()
Current version: 0.6.0
Github version: undefined
start rclone
ERROR: exec_stderr C:\Users\Lee\sidenoder\adb.exe start-server * daemon not running; starting now at tcp:5037

daemon started successfully

{ cmd: 'C:\Users\Lee\sidenoder\adb.exe --version' }
exec_stdout C:\Users\Lee\sidenoder\adb.exe --version Android Debug Bridge version 1.0.41
Version 31.0.2-7242960
Installed as C:\Users\Lee\sidenoder\adb.exe
trackDevices()
{ devices: [] }
{ devices: [] }
{ devices: [] }
ERROR: rclone error: Error: Command failed: "C:\Users\Lee\sidenoder\rclone.exe" mount --read-only --rc --rc-no-auth --config="C:\Users\Lee\sidenoder\rclone.conf" VRP_mirror06: "C:/Users/Lee/AppData/Local/Temp/mnt"
2021/09/10 19:35:11 NOTICE: Serving remote control on http://localhost:5572/
Cannot create WinFsp-FUSE file system: mount point in use.
2021/09/10 19:35:11 ERROR : Google drive root '': Mount failed
2021/09/10 19:35:11 Fatal error: failed to mount FUSE fs: mount stopped before calling Init: mount failed
at ChildProcess.exithandler (child_process.js:312:12)
at ChildProcess.emit (events.js:310:20)
at maybeClose (internal/child_process.js:1021:16)
at Process.ChildProcess._handle.onexit (internal/child_process.js:286:5) {

killed: false,
code: 1,
signal: null,
cmd: '"C:\Users\Lee\sidenoder\rclone.exe" mount --read-only --rc --rc-no-auth --config="C:\Users\Lee\sidenoder\rclone.conf" VRP_mirror06: "C:/Users/Lee/AppData/Local/Temp/mnt"'
}
{ devices: [] }
checkMount()
checkMount()
start rclone
ERROR: rclone error: Error: Command failed: "C:\Users\Lee\sidenoder\rclone.exe" mount --read-only --rc --rc-no-auth --config="C:\Users\Lee\sidenoder\rclone.conf" VRP_mirror06: "C:/Users/Lee/AppData/Local/Temp/mnt"
2021/09/10 19:35:30 NOTICE: Serving remote control on http://localhost:5572/
Cannot create WinFsp-FUSE file system: mount point in use.
2021/09/10 19:35:31 ERROR : Google drive root '': Mount failed
2021/09/10 19:35:31 Fatal error: failed to mount FUSE fs: mount stopped before calling Init: mount failed
at ChildProcess.exithandler (child_process.js:312:12)
at ChildProcess.emit (events.js:310:20)
at maybeClose (internal/child_process.js:1021:16)
at Process.ChildProcess._handle.onexit (internal/child_process.js:286:5) {

killed: false,
code: 1,
signal: null,
cmd: '"C:\Users\Lee\sidenoder\rclone.exe" mount --read-only --rc --rc-no-auth --config="C:\Users\Lee\sidenoder\rclone.conf" VRP_mirror06: "C:/Users/Lee/AppData/Local/Temp/mnt"'
}
checkMount()

Fixed it by deleting C:/Users/Lee/AppData/Local/Temp/mnt


Experimental branch

:white_check_mark: Build ServiceBusExplorer 4.0.83-PullRequest0105.6.build.139 completed (commit https://github.com/paolosalvatori/ServiceBusExplorer/commit/b4761e8ab2 by @SeanFeldman)


[Bug]: facing this problem processing full insar images upto 86

2024-12-17 03:05:09,271 - distributed.worker - ERROR - Compute Failed
Key:       ('transpose-vectorize_unwrap_pairs-vectorize_unwrap_pairs_0-mul-03c68123c6e6926e75a527cab96e521c', 0, 3, 0)
State:     executing
Task:  <Task ('transpose-vectorize_unwrap_pairs-vectorize_unwrap_pairs_0-mul-03c68123c6e6926e75a527cab96e521c', 0, 3, 0) _execute_subgraph(...)>
Exception: "ValueError('could not broadcast input array from shape (6,) into shape (126,)')"
Traceback: '  File "/home/ahmed/miniconda3/envs/pygmt/lib/python3.10/site-packages/numpy/lib/_function_base_impl.py", line 2397, in call\n    return self._call_as_normal(*args, **kwargs)\n  File "/home/ahmed/miniconda3/envs/pygmt/lib/python3.10/site-packages/numpy/lib/_function_base_impl.py", line 2390, in _call_as_normal\n    return self._vectorize_call(func=func, args=vargs)\n  File "/home/ahmed/miniconda3/envs/pygmt/lib/python3.10/site-packages/numpy/lib/_function_base_impl.py", line 2471, in _vectorize_call\n    res = self._vectorize_call_with_signature(func, args)\n  File "/home/ahmed/miniconda3/envs/pygmt/lib/python3.10/site-packages/numpy/lib/_function_base_impl.py", line 2531, in _vectorize_call_with_signature\n    output[index] = result\n'

It appears that you might not have enough interferogram pairs to successfully perform the 1D unwrapping.

Thank you very much, i will take a look at that


Find solution for command line arg escaping

It seems that julia -v=1.5.3 does not work properly because the command line splitting seems to recognize this as multiple arguments. julia "-v=1.5.3" does work, but is kind of annoying.
We should figure out whether there is some way to get julia -v=1.5.3 to work, or if that is not possible find some other syntax. Ideas could be an argument without the =, something like julia -useversion 1.5.3 or julia -v=1-5-3. The former is annoying because it doesn't jive with the rest of the julia command line args, the latter also just doesn't seem great...

One idea would be to follow rustup and use + for the version selector, i.e. julia +1.5 etc. That makes the version selector use its own command line syntax that is not in line with the pattern that is normally used by Julia, but myabe that is ok in the case of this version selector stuff.

I now implemented the rustup solution.


testdata - Add support for user authentication data

Description
Need to add support to testdata for user authentication data.  This would include:

Add support for users for authentication
Add support for secondary user instructions
Add support for nominated representatives

 [standards-testing]: testdata - Add support for user authentication data


expandable table to avoid space

Do we have any possibility to make it expandable so it won't take space on load but can be viewed by clicking on icon?

Pull reviewers stats
Pull reviewers stats
Table here

Hi @hidayt-rahman-qatalog thanks for your suggestion.
I liked this format a lot. I'll work on a version where the table is expanded by default and include and option to start collapsed.

Hi @hidayt-rahman-qatalog I took a different approach. Instead of making it collapsable, now in v2.4.0 the stats are published as a comment. This way it takes no space from description.

Thanks @manuelmhtr, I will try and see if its feasible for us or not.


Increase flexibility of prompted options

This adds a list of options to be bypassed so that some options can be bypassed even with no_input=False. This adds flexibility when triggering a cookiecutter project in a post_gen hook of another cookiecutter project.
Currently, the no_input parameter controls whether the user will be prompted for all or none of the options. This PR makes it so the user can be prompted for another percentage of the options.

[Current coverage][cc-pull] is 99.65%

Merging [#770][cc-pull] into [master][cc-base-branch] will decrease coverage by 0.34%

@@           master       #770   diff @@
========================================
  Files          13         13
  Lines         585        585
  Methods         0          0
  Messages        0          0
  Branches        0          0
========================================
- Hits          585        583     -2
- Misses          0          2     +2
  Partials        0          0

[][cc-pull]

Powered by Codecov. Last updated by [c5ebe69...ab2e618][cc-compare]
[cc-base-branch]: https://codecov.io/gh/audreyr/cookiecutter/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/audreyr/cookiecutter/compare/c5ebe696d9e21edcb3f9b7815cb320578af66c10...ab2e618f1a2bdc47b7077a53f798495af903417f
[cc-pull]: https://codecov.io/gh/audreyr/cookiecutter/pull/770?src=pr

Hi @mjsisley, can you give us an example of how this feature will be used? At first glance, this doesn't sounds widely applicable for core inclusion.

Sure,
This helps compose multiple cookiecutter projects. In cookiecutter-django's post_gen_project.py, cookiecutter-webpack is added to the project if it is selected as an option.
def add_webpack():
    """
    Adds webpack configuration using cookiecutter to install hzdg/cookiecutter-webpack
    """
    cookiecutter(
        'https://github.com/hzdg/cookiecutter-webpack.git',
        replay=False, overwrite_if_exists=True, output_dir='../',
        checkout='pydanny-django', no_input=True, extra_context={
            'project_name': '{{ cookiecutter.project_name }}',
            'repo_name': '{{ cookiecutter.project_slug }}',
            'repo_owner': '',
            'project_dir': '{{ cookiecutter.project_slug }}',
            'static_root': '{{ cookiecutter.project_slug }}/static/{{ cookiecutter.project_slug }}',
            'production_output_path': '{{ cookiecutter.project_slug }}/static/{{ cookiecutter.project_slug }}/dist/',
            'author_name': '{{ cookiecutter.author_name }}',
            'description': '{{ cookiecutter.description }}',
            'version': '{{ cookiecutter.version }}',
            'existing_project': 'y',
            'css_extension': 'sass',
            'use_ejs': 'n',
            'open_source_license': '{{ cookiecutter.open_source_license }}'
        })

It is possible that some options could apply to cookiecutter-webpack and not cookiecutter-django ('use_ejs' and maybe 'css_extensions' fit this description). It makes sense to prompt the user for these options only if webpack is selected as an option in cookiecutter-django. However, it doesn't make sense to prompt the user for the author_name and similar.
Without something like this PR, either all or none of the options will be prompted for toggled by the no_input flag. The bypass_options parameter gives more control when cookiecutter projects are started within another cookiecutter project.
(I'll add docs and get coverage to 100% if you want the PR)

Hmmm I can see how we accept a list of str for no_input and do not query those variables.

@hackebrot, to clarify... do you mean you "can see how we could accept..."? I first thought that you were saying that no_input already did that and that I missed something.
Assuming that is true, it would be better to have no_input handle a list of strings rather than add a parameter?

I'm thinking about ways to add this functionality w/o adding more optional parameters. Especially since this directly relates to no_input and maybe it makes sense to allow something like the following:
cookiecutter(
    'https://github.com/hzdg/cookiecutter-webpack.git',
    checkout='pydanny-django',
    no_input=['author_name'],
)

Why not just have cookiecutter-django's hook implement this?
On Jul 1, 2016 6:03 AM, "Raphael Pierzina"<EMAIL_ADDRESS>wrote:

I'm thinking about ways to add this functionality w/o adding more optional
parameters. Especially since this directly relates to no_input and maybe
it makes sense to allow something like the following:
cookiecutter(
'https://github.com/hzdg/cookiecutter-webpack.git',
checkout='pydanny-django',
no_input=['author_name'],
)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/audreyr/cookiecutter/pull/770#issuecomment-229802022,
or mute the thread
https://github.com/notifications/unsubscribe/AAD1ifTJr-yhgR9mxDbA3u5srJRRoLVTks5qRD0sgaJpZM4JB8Ge
.

@hackebrot, that makes a lot of sense... I can convert the PR to that if this is wanted.
@pydanny TL;DR I thought about this, but it seems that having no_input take a list of strings would be useful for some options, while implementing it in the hook makes sense for others. I could be wrong.
I think that you could use cookiecutter-django's hooks for certain items (things that apply to both cookiecutter-webpack and cookiecutter-django), but asking questions in cookiecutter-django that only apply to cookiecutter-webpack when webpack isn't selected would be annoying.
As an alternative, triggering more prompts one by one in cookiecutter-django's hooks to then set extra_content seems like it could be possible (and maybe is already implemented, I have not looked), but seems to me to be more work  than optionally letting no_input take a list of strings. I could be wrong.
I am not really sure how this project is governed but if you guys decide that you want this added then please let me know and I will clean up the PR (I don't want to take time cleaning it up and adding docs if you guys will reject it anyways).

Sorry, too much text. I think this PR allows increased flexibility when having a cookiecutter triggered in a post_gen hook, while not preventing anything from being done as it is now for those uninterested.
Will this PR be merged if I do the following?

no_input takes string, no bypass_options parameter added.
add docs
add tests/ coverage = 100%

Just give me a thumbs up and I'll get it together over the weekend.

See #848


Help me identify which forks/PRs are worth merging

Hey all! I'm an old colleague of @mzgoddard's, and he was kind enough to grant me maintainer rights on this repo to help clean up some of the backlog. Unfortunately I'm juggling a lot of projects, and do not have the time or background to thoroughly triage the issues and PRs open here.
Asking for help: If we can get consensus about which PRs or forks are commonly in use to work around issues, that'll give me the clarity I need to test and merge / release those PRs in the time I have available.
I'm also looking for other folks who have been iterating on this code who would be interested in helping to maintain it to clear out the issue backlog.
Thanks, :pray:

Evening! I had a look into https://github.com/mzgoddard/hard-source-webpack-plugin/issues/416 and the associated PR: https://github.com/mzgoddard/hard-source-webpack-plugin/pull/497. As far as I can tell, it's safe to merge. It's already being used in a separate npm package (2k weekly downloads), and the travis errors are the same as all the other PRs. I put a little more detail in a comment on the PR as well.


buggy implementation of getConsoleDir if var/ is not existing

We just had the case that our deployment failed after upgrading to Symfony3 in the clearCache step (composer postinstall).
The problem was that we didn't upload the var/ directory to the container and therefore the check in getConsoleDir -> useNewDirectoryStructure tries to use app/console instead of bin/console.
The implementation of getConsoleDir is less than ideal, IMHO. getConsoleDir should find a different check in which directory the console is. How about replacing that with this implementation?

    /**
     * Returns a relative path to the directory that contains the `console` command.
     *
     * @param Event  $event      The command event
     * @param string $actionName The name of the action
     *
     * @return string|null The path to the console directory, null if not found.
     */
    protected static function getConsoleDir(Event $event, $actionName)
    {
        $options = static::getOptions($event);
        $binDirExists = static::hasDirectory($event, 'symfony-bin-dir', $options['symfony-bin-dir'], $actionName);

        if ($binDirExists && file_exists($binDirExists.DIRECTORY_SEPARATOR.'console')) {
            return $options['symfony-bin-dir'];
        }

        return $options['symfony-app-dir'];
    }

Related: #248

👍

Closing this issue as this bundle is now deprecated. Symfony Flex replaces this bundle.


updated game color and search color

PR Description 📜
Please include summary related to the issue you have fixed and describe your PR in brief over here by specifying the issue number on which you were working below
The color of game name and search placeholder is invisible in light theme .so changed the colors.
Fixes # 2447

Mark the task you have completed ✅

[x] I follow CONTRIBUTING GUIDELINE & CODE OF CONDUCT of this project.
[x] I have performed a self-review of my own code or work.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generates no new warnings.
[x] I have followed proper naming convention showed in CONTRIBUTING GUIDELINE
[x] I have specified the respective issue number for which I have requested the new game.

Add your screenshots(Optional) 📸

Thank you soo much for contributing to our repository 💗

Thank you @Ashasindhu ,for creating the PR and contributing to our GameZone 💗
Review team will review the PR and will reach out to you soon! 😇
Make sure that you have marked all the tasks that you are done with ✅.
Thank you for your patience! 😀

Hey @Ashasindhu,
Please make sure to link the relevant issue using the appropriate syntax, such as "#issueNumber" 👀.
Follow the proper guideline and make a new PR again 😀.
Happy Hacking 💗

Thank you  @Ashasindhu , for your valuable time and contribution in our GameZone 💗.
It’s our GameZone, so Let’s build this GameZone altogether !!🤝
Hoping to see you soon with another PR again 😇
Wishing you all the best for your journey into Open Source🚀


Extend Console to configure idp based on templates

As a zitadel admin i want to be able to enable/disable identity providers and add some needed configuration based on the provider, so I do not have to know all information of a provider.
Acceptance Criteria

[ ] All possible providers are shown on the instance and organisation level
[ ] I can enable a new provider and have to add the needed information (e.b. client id, secret) on enabling
[ ] I can disable an enabled provider
[ ] I am able to upload a picture to the provider

@juergrinaldi can you please make a design for this

List shows already set up IDPs. If there are none, only the selection part below is showing.
Thought it would be helpful if users can submit wanted IDPs, so we can provide according to demand.

3. this step should include all data/inputs that are generally used within all selected IDPs.
4. we should pre-fill as many defaults as possible/viable through all of the steps.

5. following the previous screen are specific data for the selected IDPs. Each with an own step.
6. IF we want to include custom data mapping and/or show how the default mapping is, we should show this on a separate screen.

7. Because there can be a lot of attributes/permissions they are collapsable (but it probably make sense to show them per default).

8. after setting up your IDPs you land back at the starting page with all new IDPs "active/available" per default. via click on the icon you can deactivate it. (if it's critical we can show a 'are you sure?' prompt)
9. on hover we show a delete option. on click on the whole row we show the complete list of data/options for that IDP.
10. here is shown a reduced list of IDPs, according to the already set up ones, to reduce clutter. If users need to be able to set up multiple of the same IDP, the list will stay complete.

@hifabienne @livio-a I added my first draft, can you check if that is viable?

Looks good to me

The designs look great 👍 Also like the improvement of the active state!

Last missing piece will be addressed seperately #5455


Fix lwip interface enumerate with single interface

Under lwip, os_enumerate_interfaces() would fail if only a single interface is enabled by define.
In this situation NETIF_FOREACH define evaluates to an if statement, which results in the interface count limit check attempting to exit this if statement with a break.
As the limit check is redundant for a single interface, it is defined out.

Thank you for pointing this out @PharosMarcusB . Given there are other breaks as well, it would be better to eliminate the breaks entirely, so I just made a fix to that effect that is currently being reviewed internally. You should see it pushed to main within a few days. Thanks again!

Hi @PharosMarcusB - EtcPal <IP_ADDRESS> is available and includes the aforementioned fix. Could you please let us know if it works for your use case once you've tried it? Thanks!

@ChristianReese That seems to work just fine, thanks.

@PharosMarcusB Glad to help, and thanks for trying it out!


Change UPS remote tests to take into account business hours for delivery estimates

Summary
Time zone shiftiness going on:
[1] pry(main)> Date.today
=> Tue, 26 Apr 2016
[2] pry(main)> 3.business_days.from_now
=> 2016-05-02 09:00:00 +0000
[3] pry(main)> 3.business_days.after(Date.today)
=> Fri, 29 Apr 2016

from_now just adds the n days, whereas .after takes into account business hours, adding an extra day if the present time is past business hours (which is why it's flaky right now, since most of the time we're running our builds outside of business hours for the system (UTC)).
Carrier responses take into account business time and rolling forward, so we should too in our tests.
Fixes half of the red build - the other half is fixed by https://github.com/Shopify/active_shipping/pull/361
Review: @kmcphillips @RichardBlair @mdking @MalazAlamir

:shipit:

🚢


🐛: Page is not responsive in mobile view

:red_circle: Title : Page is not responsive in mobile view
:red_circle: Bug : not responsive in mobile view
:red_circle: Changes :  <we need to responsive it
Screenshots 📷

:white_check_mark: To be Mentioned while taking the issue :

Full name : Ramakrushna Biswal
What is your participant role?  GSSOC

Happy Contributing 🚀
All the best. Enjoy your open source journey ahead. 😎

@RamakrushnaBiswal website is updated already with responsiveness


Cucumber::Core::Test::Case#name ignores text after \n character

I am facing an issue if the scenario outline name spans more than one line. It appends 'Example {##}' after the end of first line, ignoring everything after line #1
I am writing my own formatter , and using the before_test_case method.
Thanks!

Can you give me a concrete example please?

Hi @mattwynne
In the example below, test_case.name would be "I can add a document with title longer than 25 characters but navigation bar"
and not
"I can add a document with title longer than 25 characters but navigation bar
would only display first 15 characters"
On the other hand, in scenario_name(name), name is "I can add a document with title longer than 25 characters but navigation bar
would only display first 15 characters"
Is this by design?
Scenario Outline: I can add a document with title longer than 25 characters but navigation bar   would only display first 15 characters     Given I am logged in as a user with role "<user_role>"     And I ...     And I ...     And I click the document list     And I upload a document with no title     And I ...     When I upload another document with title "A very very very very very very long title"     Then I should see link

Gherkin (v3/v4) clearly define the name of the scenario outline as the text after "Scenario Outline:" until the end of line. The text of the following lines until "Given" (or another keyword) is found, is the (optional) description of the scenario outline (or scenario, or feature etc they all have the same syntax with respect to name and description). See acceptance test feature file and the corresponding AST tree representation.
I do not understand what you mean by "scenario_name(name)".

Thank you @brasmusson. Is there a way to get the optional part of the description then?
Sorry for the brevity, but I meant the name parameter in this method returns the full name. http://www.rubydoc.info/gems/cucumber/Cucumber/Formatter/Html#scenario_name-instance_method

@na-na the methods on that formatter API are being deprecated. There is a way to get what you want, using events, but I need to know a bit more about your use-case.
Please can we continue this discussion on the https://gitter.im/cucumber/cucumber-ruby chat channel? Alternatively, you could open an issue on the front-end repo - the problem you're experiencing won't be fixed in the core I don't think.


Failed to find nanodegree

2019-10-10T14:15:40.923Z [info]: Start downloading Nanodegree nd001 from Udacity API
✖ Get Nanodegree nd001 information
✖ Get Nanodegree nd001 information
2019-10-10T14:15:42.344Z [error]: Failed to download course. See error below:
ERROR: Fail to find Nanodegree key nd001 in your profile. The key nd001 either doesn't exist or you don't have access to it.
STACK: Error: Fail to find Nanodegree key nd001 in your profile. The key nd001 either doesn't exist or you don't have access to it.
at downloadNanodegree (/home/atoz/.npm-global/lib/node_modules/udacimak/lib/commands/download/functions/downloadNanodegree.js:43:22)
at process._tickCallback (internal/process/next_tick.js:68:7)

@MakVihas
Do you have subscription for nd001?
Also, can you run udacimak listnd to see what NDs you have access to and if nd001 is listed?


App store showing open Button Instead of update button

Use case
==>Installed app in User's device with version 1.2.2 and released the Version 1.3 on the app Store.After the app is live on the App store ,User is presented with update dialog (HarpyAlertTypeForce) .
==> User clicked on the update button on the Alert and then user navigated to Appstore.
==> In Appstore the app is showing the open button instead of update
==> User clicked on the open Button shown in the app store .
==> App opens with the previous version .
as user clicked on open on the app store then it needs to check coming back to app that user updated the app or not .
BTW thanks for Developing the Harpy :)

Hi @deepak-tcy
This is an issue with Apple. For more details please refer to https://github.com/ArtSabintsev/Siren/issues/126.
In essence, the iTunes API is showing an update is available, however, Apple's CDNs have not propagated the executable to the App Store. This is an issue on Apple's end.
The best solution is to drive Harpy using a server-side configuration file that you edit as needed to turn on Harpy on the app side.
Closing the issue, but feel free to respond.

The best solution is to drive Harpy using a server-side configuration file that you edit as needed to turn on Harpy on the app side.

@ArtSabintsev how can I do that? Could you please provide an example? Thank you.

Also, I've seen that the issue is fixed for Swift version. Do you have a fix for Obj-C too?

@YGeorge this can be achieved with this line https://github.com/ArtSabintsev/Harpy/blob/master/Harpy/Harpy.h#L152, which I forgot to document in the README (I think)
As for the configuration file, there's no tutorial on how to do his. You will simply need to host a versioned JSON file on a server somewhere that you update whenever you want to conditionally turn Harpy on and off.

@ArtSabintsev but how can I connect Harpy with my json or API endpoint? Is it possible? Thanks for option with delay, but it won't help in my case :(

All you need to do is wrap Harpy around a boolean variable that is controlled by a JSON file on your server.