Derivative w.r.t initial conditions?

Thanks a lot for your work! I wonder if it could support taking derivative w.r.t initial conditions, such as u0 = param([1.0, 1.0]), rather than p = param([1.5, 1.0, 3.0, 1.0]).
Today I noticed that the code in README.md cannot run properly because of some update of upstream packages, so I cannot make an example of taking derivative w.r.t initial conditions now. Last time I tried it, it throws error.

This was recently added, but then DiffEq v6.0's big update came out which caused a bit of havoc here. We are looking over this in the next few days.

This should work now. Let me know if you run into any issues.

Hi, Chris. It seems that the derivative w.r.t initial conditions is still not working. In the following code, grad_ode(x) and grads[x] just give all 1.0.
using DiffEqFlux
using DifferentialEquations
using Flux
using Flux.Tracker

const N = 4

net = Chain(Dense(N, N, relu), Dense(N, N))
tspan = (0.0, 1.0)
ode(x) = neural_ode(net, x, tspan, Tsit5(), saveat = (tspan[2],), save_start = false)
grad_ode(x) = gradient(xx->sum(ode(xx)), x; nest = true)[1]

x = param(randn(Float32, N))
print(grad_ode(x))

grads = gradient(()->sum(ode(x)), params(x))
print(grads[x])

Environments:
Windows 10, Julia 1.1.1
[aae7a2af] DiffEqFlux v0.5.2
[0c46a032] DifferentialEquations v6.6.0
[587475ba] Flux v0.8.3

Sorry that I have been not following the development of DiffEqFlux for a long time. It has gone through many updates, and I didn't try if it works in the past. Thanks for your help!

saveat at only the final time is a little odd. The following code is more standard and works:
using DiffEqFlux
using DifferentialEquations
using Flux
using Flux.Tracker

const N = 4

net = Chain(Dense(N, N, relu), Dense(N, N))
tspan = (0.0, 1.0)
ode(x) = neural_ode(net, x, tspan, Tsit5(), save_everystep=false,save_start=false)
grad_ode(x) = gradient(xx->sum(ode(xx)), x; nest = true)[1]

x = param(randn(Float32, N))
print(grad_ode(x))

grads = gradient(()->sum(ode(x)), params(x))
print(grads[x])

I don't know why yours doesn't though... peculiar.

Thanks! It works now. That's really a subtle behavior.

Yeah, I'm re-opening the issue to find out why that occurs, but for now there is a workaround. The workaround is more standard way of writing that for DiffEq users, so this is not the highest priority, but I'd like to get it fixed anyways.

Today the code cannot work again. The error message is
ERROR: MethodError: Cannot `convert` an object of type DataStructures.BinaryHeap{Float32,DataStructures.GreaterThan} to an object of type DataStructures.BinaryHeap{Float64,DataStructures.GreaterThan}

Environments:
Windows 10, Julia 1.1.1
[aae7a2af] DiffEqFlux v0.6.1
[0c46a032] DifferentialEquations v6.6.0
[587475ba] Flux v0.8.3

BTW, I'm doing research on physics+ML, where there are some complicated use of ODE and autodiff. such complicated operations seldom exist in 'ordinary' ML fields like CV, so there seems to be few developers aware of them. AFAIK, at present no ML framework can do d^2 y / dx^2 where y is something like sum(ode(x)), with reasonable memory usage (adjoint or checkpoint). In physics, such operation is used to calculate the kinetic energy.
I'm willing to implement it by myself (only in spare times, as making computer wheels is not the major work in our physics department), and I feel Julia's concept of interoperating ODE and autodiff packages by multiple dispatch is really promising and eases the development. However, the huge amount of error message forbids me to debug, which reminds me of C++ STL templates. Maybe I would take some time to understand the codebases of DifferentialEquations.jl and Flux.jl. Anyway, thanks for your great work!

You accidentally made a Float64 value instead of a Float32 value in your setup. Check all of your things for Float64's. Any 1e0 should be 1f0. Let me know when you find out what it is so I can try to intercept this with a better error message.

ok, I change to tspan = (0f0, 1f0) and it works. Thank you!

For me, both alternatives work with the latest master of OrdinaryDiffEq. Maybe a side-effect of the latest changes in tstop_saveat_disc_handling?

Yeah, looks like it's fixed. That change in OrdinaryDiffEq fixed a lot of these small AD issues.


Run tox cuda unit tests in a single serial process

Summary
CUDA running out of memory when tests are run in parallel. Make it serial to see if it improves.
Details and comments

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.09%) to 87.303%

Totals

Change from base Build<PHONE_NUMBER>:
0.09%

Covered Lines:
2998

Relevant Lines:
3434

💛  - Coveralls


update to myshenin master, add base64 decode to body

This change is

index.js, line 4 at r2 (raw file):
Previously, msakauye (Mark) wrote…
why toLocaleLowerCase for one string and toLowerCase for the other? shouldn't those both match up?

good question, that is how I received it from remote.  I don't see how locale would fit into this header name.

index.js, line 4 at r2 (raw file):
Previously, tony-aq (Tony Knight) wrote…
good question, that is how I received it from remote.  I don't see how locale would fit into this header name.

https://github.com/myshenin/aws-lambda-multipart-parser/blob/master/index.js#L4
I'd be willing to change both toLowerCase() if you agree


Wagtail CMS grid at DjangoPackages

Hello guys! I'm just released https://github.com/MechanisM/wagtail-constance
And also created Wagtail CMS grid at https://www.djangopackages.com/grids/g/wagtail-cms/
I think it would be great to have a list of all available apps built for wagtail.

Nice! I've added it to the wiki page at https://github.com/torchbox/wagtail/wiki/Contributed-apps-and-website-code. Having a grid on djangopackages.com is a good idea too - I would suggest announcing it on the Google group.


Logback FILE appender doesn't work with defined logging.path in configuration server

I tried to configure FILE appender using config server but it doesn't work as I expected.
Config server contains application.yaml file with property logging.path: '/tmp'.
Application has logback-spring.xml file:
<?xml version="1.0" encoding="UTF-8"?>
<configuration>

    <property name="LOG_FILE" value="${LOG_PATH:-/other}/spring.log"/>

    <include resource="org/springframework/boot/logging/logback/defaults.xml"/>
    <include resource="org/springframework/boot/logging/logback/file-appender.xml"/>

    <root level="INFO">
        <appender-ref ref="FILE"/>
    </root>

</configuration>

When application startup before loading properties from config server all logs go to /other/spring.log file. After load properties from config server logs go to proper directory /tmp/spring.log.
The problem is that I cannot specify default value on production.
Is it possible to initialize appender after load properties from config server?

I don't know there is much we can do to hold off the appended from being initialized.  Logging to file is not something we would recommend for cloud apps anyways.  If you find a solution that works for you please let us know.


Material Design: Themed App Icon

On Android 13, using themed app icons makes StreetMeasure stick out like a sore thumb compared to StreetComplete who supports it.
It would be nice if there could be an option to enable a themed app icon to remedy this.
I am sorry I cannot provide a pull request, for I have no coding skills.
here is the documentation on how to do it nonetheless:
https://developer.android.com/develop/ui/views/launch/icon_design_adaptive

You mean the monochrome icon, right?

That is indeed what I'm talking about.

The problem is that the current icon doesn't really work well in monochrome. It'd need to be changed. Just the ruler perhaps, rotated into the same way as the road in the background?

It might just work, but additionnal testing needs to be made to ensure that the icon is visible no matter what the user-defined theme is.

Or like this, it's closer to the normal variant. It looks worse, but what can you do with monochrome...

Thank you for being so swift with this issue 👍


Read "Cloud" configuration for WorkloadIdentityCredential from environment variable

Feature Request
As far as I see on the WorkloadIdentityCredential the options ClientID and TenantID are read from environment variables by default. (AZURE_CLIENT_ID, AZURE_TENANT_ID)
I would propose to also support reading the environment variable AZURE_CLOUD_NAME to set the option ClientOptions.Cloud configuration automatically. I would also propose to align with the azure-cli environment variable AZURE_CLOUD_NAME, which supports the value AzureCloud, AzureChinaCloud and AzureUSGovernment: https://learn.microsoft.com/en-us/cli/azure/azure-cli-configuration#cli-configuration-values-and-environment-variables

Nevermind, I think I have overlooked the AZURE_AUTHORITY_HOST which is already present for this purpose.


Change images dynamically

Is there a way how to change images dynamically in the CarouselView on button click ? Let's say I'm on the second image and then I click on the button under the carousel and it changes all images to the other ones that I'll have in array of their IDs. It moves on to the first one as well.

you can make multiple arrays of Id's and switch between them when you press
the button. Pick image id from switched array inside your imagelistener.
On Thu, May 25, 2017 at 2:56 PM, Róbert Vangor<EMAIL_ADDRESS>wrote:

Is there a way how to change images dynamically in the CarouselView on
button click ? Let's say I'm on second image and then I click on the button
under the carousel and it changes all images to the other ones that I'll
have in array of their IDs. It moves on to the first one as well.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/sayyam/carouselview/issues/68, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAk1-e_-f-OQ-bFfwNUExue1wgAtdjD7ks5r9VBbgaJpZM4NmMOe
.

--
Best Regards,
Sayyam Mehmood | Mobile Application Developer
Mobile | +923344298234
Skype | sayyam.mehmood

I tried that and it doesn't work.  @sayyam

    int[] redImages = {R.drawable.red1, R.drawable.red2};
    int[] blackImages = {R.drawable.black1, R.drawable.black2};

    carouselView = (CarouselView) findViewById(R.id.carouselView);
    carouselView.setPageCount(2);

    carouselView.setImageListener(blackListener);

    black = findViewById(R.id.blackColor);
    red = findViewById(R.id.redColor);

    black.setOnClickListener(new View.OnClickListener() {
        @Override
        public void onClick(View v) {
            carouselView.setImageListener(blackListener);
        }
    });

    red.setOnClickListener(new View.OnClickListener() {
        @Override
        public void onClick(View v) {
            carouselView.setImageListener(redListener);
        }
    });

    ImageListener blackListener = new ImageListener() {
        @Override
        public void setImageForPosition(int position, ImageView imageView) {
            imageView.setImageResource(blackImages[position]);
        }
    };

    ImageListener redListener = new ImageListener() {
        @Override
        public void setImageForPosition(int position, ImageView imageView) {
            imageView.setImageResource(redImages[position]);
        }
    };

Ok I found a solution. Each time you set Image listener, you have to do a stePageCount() as well. That would be
  red.setOnClickListener(new View.OnClickListener() {
        @Override
        public void onClick(View v) {
            carouselView.setImageListener(redListener);
            carouselView.setPageCount(numberOfImages);
        }
    });


Security problems

GP 449 and 446

and 450 and 451

https://github.com/ledgerleapllc/devxdao-backend/pull/100


Integrated reference doc experience design

One outcome from a recent docs jam was that we identified that a design exercise needs to occur to implement a more integrated reference doc experience for:
APIs
We are inconsistent with how we handle APIs; in the Blockchain API case we use OpenAPI and can hand off to ReDoc, as we are here: https://blockstack.github.io/stacks-blockchain-api/
However we also have a Node RPC API that we document by hand/totally inline: https://docs.blockstack.org/references/stacks-rpc-api
CLIs
Currently we have a take on this but it has problems: https://docs.blockstack.org/references/blockstack-cli
JS Libraries
We're sending users over to a Typedoc site, but Typedoc can export JSON and Markdown we think, so how would we surface library functions in our docs?

I would build something similar to the clarity reference integration for the typedoc json, if you don't have any other input


Sentiment poll and small feedback thread

Please leave an emoji reaction to this comment to let me know how you feel about this repo's solution as a shape of solving some use cases for "open-stylable" Shadow Roots
Feel free to just drop comments small comments here as well if you need just a little bit more but don't feel like it's worth an issue of its own.

I think that people end up with the Shadow DOM (and thus the current problem case) because there's no way to write basic modular markup and style those modular structures.
In my case, I often simply want a form of "namespacing" for plain, light DOM structures and selectors. (For which people invented class naming conventions like BEM, I guess.) I wrote about it here: How do you make components?

will be green

It's part of a bigger story I developed as OOHTML and it goes with a JavaScript implementation that lets us play with the idea.

My feedback:

I like the general shape of the API. Using media queries is an interesting way to do this. I've also seen other ideas like using @layer. I'm not sure which one is better than the other, I don't have any opinions on that.
I can't use a polyfill that requires JavaScript because that will lead to FOUC (flash of unstyled content) with DSD (declarative shadow DOM). I consider this a hard-requirement for me, so I simply don't use shadow DOM for non-enhancement use-cases until this is fixed at the platform level. So I can't give feedback on the JS library for this reason.
Some concern that Apple will not like this proposal for 2 reasons:
a. They have said that they cannot have selectors that are cross-root. Does this proposal introduce this problem?
b. In the past Apple has objected to any proposal that breaks hard encapsulation. I think this proposal does so, as the component author does not opt-in to styles coming into the SD. Have you spoken to Apple representatives and gotten their thumbs up on this idea?

Just want to reply to a few things in case there's confusion

I like the general shape of the API. Using media queries is an interesting way to do this. I've also seen other ideas like using @layer. I'm not sure which one is better than the other, I don't have any opinions on that.

A real proposal (probably) wouldn't use @media, I mentioned this in my blog post and again in this episode of our podcast (jump to about 42minutes in or search for "How would you describe this, Mia?" if you prefer the transcript).  The idea is simply that it would be an at rule, and you probably need to be able to express in that rule which things it applies to (ie, the page, the roots, certain roots, etc)

I can't use a polyfill that requires JavaScript because that will lead to FOUC (flash of unstyled content) with DSD (declarative shadow DOM). I consider this a hard-requirement for me, so I simply don't use shadow DOM for non-enhancement use-cases until this is fixed at the platform level. So I can't give feedback on the JS library for this reason.

This kind of feedback is why i created this sentiment poll. I understand that not everyone can actually use it.  An emjoi isn't accurate, but feedback, but they're easy enough.

Some concern that Apple will not like this proposal for 2 reasons:
a. They have said that they cannot have selectors that are cross-root. Does this proposal introduce this problem?
b. In the past Apple has objected to any proposal that breaks hard encapsulation. I think this proposal does so, as the component author does not opt-in to styles coming into the SD. Have you spoken to Apple representatives and gotten their thumbs up on this idea?

I haven't talked to anyone no, but it's not a proposal. The last thing wasn't a proposal either. They are us trying to figure out what we want, and what is going to work for developers. It might be one of these, or something else.  If people have this problem, and they  can use this, then it should help them and there is nothing to object to because it is literally how things already work.  I can say that if we approach the problem with some data showing that this is actually a useful and necessary kind of thing to a lot of people, this is just an easier discussion than if we are speculating.

In this thread: https://mastodon.social/@westbrook/111745107269022735 and this accidentally detached thread: https://mastodon.social/@westbrook/111745113717336060 I attempted to gather a handful of user stories that I think apply to this space. Is the lack of response a judgment of the problem space? Likely not. Is it a judgment of my "brand reach"? Likely so. There are a million things that could be done in this space, but I feel you'd have a hard time finding one that serves enough use cases for it to get traction here.
As far as the user stories, I think that this takes a run at:

As a custom element consumer, I want to be able to take full control of the visual delivery of the elements that I consume so that I can have them delivered exactly as I’d like.

and

As a custom element consumer, I want to style the contents of a shadow root with “natural selectors” instead of CSS Custom Properties and CSS Parts so that I don’t need to learn additional CSS syntax to style the content therein.

and

As a custom element consumer, I want my styles (without directly addressing specific content) to apply to the contents of the elements I consume so that CSS that I’ve already written can apply to the shadow root content.

However, the more I think about them the more I'm struck by their being a theoretical extension of

As an application author, I want to structure my content with s without being bound to the encapsulation realities of shadow DOM so I can reduce the HTML that I repeat but still have all of the styles I have already written apply to it.

Wherein in all likelihood the developer doesn't actually want a "component" with Shadow DOM.
By the time you get to this space, it feels much more like the developer is grasping at the closest things to "templating" in the platform and then angry about the platform not actually having templating and then venting about that in the form of saying that Shadow DOM should have an expanded feature set. Simply stated:
Do "component" consumers want "open-stylable shadow roots" or do they simply want packageable templating?
Maybe there is a world wherein one is the other and both, but it seems like we're stretching for APIs because "this is all we have" rather than driving for the actual APIs we want here. I love Shadow DOM, love writing elements with Shadow DOM, and benefit greatly from the way it separates the concerns of my applications, and most of the reasons begin to fall apart when allowing a consumer to address styles and functionality against those DOM trees beyond my blessing. Would my work have more consumers were this sort of approach possible? Maybe. Would the added costs of maintaining a larger API surface balance that out? Likely not.

I do not think it directly serves any of the above use cases, but as I hear the conversations and possible paths to addressing the space go back and forth, I am quite interested in the ability to share/transport @layers. In that way, I wonder if in a non-Shadow DOM-centric manner the @layer spec has room to grow to a place wherein we could opt-in to applying an @layer in place of the user agent stylesheet, not just after the user agent. Possibly something that was sanitized to only element and platform attribute selectors. In that way, you could do something like:
@layer USER-AGENT-REPLACEMENT {
    input[type="button"] {
        background: blue;
    }
}

And, FINALLY have control over not just the same in third-party shadow roots, but also the ever-elusive:
<input type="file" />

Then app authors would have a path to cajoling the contents of shadow root to look a specific way, but the component author would still win when they apply DOM-tree local styles and no specific API (CSS Custom Properties or ::part()s) for consumers to explicitly customize that content.

I tend to agree with @Westbrook's take. In general, I think that there are 2 use cases at odds here:

As a component author working on an enterprise-y platform experience, I want to completely lock down my API surface so that my customers don't shoot themselves in the foot and complain when I break them by changing my internals (aka <video controls> use case)
As a component consumer working on a fast-paced consumer-facing experience where I own the whole frontend, I want to add a shadow-using component and have it "just work" with my existing global styles (e.g. Bootstrap) with zero changes required from the stylesheet author

This proposal actively harms the first use case (by allowing consumers to override e.g. closed roots) and it doesn't help the second (since the stylesheet author needs to make changes). Maybe there is some other middle-ground use case that is served by it, but as Westbrook said, you probably just want templating or compile-time framework "slots" at that point. (At least then you would also get "scoped slots" [i.e. lists/virtual lists] to boot.)

@nolanlawson your 2nd bullet was, I agree, a potential issue.  You can do that with half-light now

@Westbrook I can't make you able to replace UA sheets, but I did introduce layering!


Ensure $convert template providers read from cache

Description
When receiving many $convert-data requests concurrently it is possible for many template providers to be created. Each template provider has a cache where the contents of the template are cached. In the case where the templates have not yet been cached or the cache has expired, and when receiving many requests at once, it is possible for each template provider to request template data from the ACR which results in a lot of pulls from the ACR. To address this, we will be caching the template provider and limiting the number of threads that can create a new template provider to 1. This ensures that at most only one provider will be created and will read from the ACR. All other requests will read from the cache.
Related issues
Addresses work item#104027.
Testing
Before change:
Created a console app that sends 1000 concurrent $convert-data requests.
The application code was observed to pull the same image from ACR many times and was eventually blocked from reading from ACR. Many $convert-data requests fail with HTTP 500 errors when unable to pull from ACR
After change:
Send 1000 $convert-data requests
The application code reads from ACR once and all $convert-data requests are fulfilled.
Semver Change (docs)
Patch

/azp run


fix deb packaging systemd files

fix #14995

Gah good catch, LGTM

@tianon I think @eolamey really gets all the credits here!  Perhaps we should send out MobyDock plushies :+1:

Hahaha, actually, you all deserve credits :) Less than 30 minutes from bug report to fix, on a saturday... <3

ping @calavera to cherry-pick into release branch

cherry-picked


Does this library support client credentials flow? If so are there any samples for the same?

Does this library support client credentials flow? If so are there any samples for the same?
Please complete all sections.
Configuration

Provider Gem: omniauth-*
Ruby Version: ``
Framework: ``
Platform: ``

Expected Behavior
Tell us what should happen.
Actual Behavior
Tell us what happens instead.
Steps to Reproduce
Please list all steps to reproduce the issue.

If you're referring to the PKCE flow, omniauth-oauth2 supports this as of  1.7.0

If you're referring to the PKCE flow, omniauth-oauth2 supports this as of  1.7.0


changing images

Signed-off-by: Justin Woo<EMAIL_ADDRESS>

@justin, did you also delete the old images?  Or are the new images merely using the same names?  Either is fine.  Would just prefer to not leave orphaned images in there bloating it up.


weird error that idk how to fix

i tried multiple things including reinstalling python and the sniper, but get this error message:

Can you upload you config files to this issue? Something's amiss with the timing selection, usually a result of user error.

This is caused by the coolkidmacho api, i can look into providing a better error message later.

@Kqzz Could you rename this to CKM API failing to fetch droptime? Current issue name isn't very descriptive. Thanks.

If needed I can add the error message.

That'd definitely be helpful. No reason to return html in an API. You definitely want to return a logical error message across all endpoints, and not just let the code error and give some html.

Sounds good, the error is commonly caused by names that are not cached. Will be fixed within 24 hours.

Coolkidmacho api SUCKS
rip teun api
peet private api on top 😼

Coolkidmacho api SUCKS
rip teun api
peet private api on top 😼

Some can add my API as a backup or something

Sounds good, the error is commonly caused by names that are not cached. Will be fixed within 24 hours.

Fixed.

Sounds good, the error is commonly caused by names that are not cached. Will be fixed within 24 hours.

Fixed.

Non-cached names still seem to return a HTML error page (http://api.coolkidmacho.com/droptime/123). I think it would be better, if you could return json data with the error message

Definitely, @coolkidmacho you should implement this.

Definitely, @coolkidmacho you should implement this.

Done

Definitely, @coolkidmacho you should implement this.

Done

Takes 3 days to do that . ShitAPI
peet api on top
rip teun api 🕊

Sounds good, the error is commonly caused by names that are not cached. Will be fixed within 24 hours.

Fixed.

Thx so much.

Close this when you get a chance, @Kqzz


Improve Example Picker XP

Old version:

My opinion is that is too complex.
Subject to discussion by @edewit @quintesse @ALRubinger @gastaldi

Added the "Already decided" runtime filter, but it works a lot simpler then in the old version. It will filter the mission list to all missions that are available for that runtime and dropdowns for the runtime will be pre-selected with the runtime that the user is filtering on.


Add params_to_tune for new NNs (RNNModel, MLPModel)

🚀 Feature Request
Add params_to_tune for new NNs (rnn, mlp).
Proposal
Sources:

pycaret

mlp

kats

lstm

Suggested grid for RNNModel:
{
    "num_layers": IntUniformDistribution(1, 3, step=1),
    "hidden_size": IntUniformDistribution(4, 64, step=4),
    "lr": LogUniformDistribution(1e-4, 1e-2),
}

Suggested grid for MLPModel:
{
    "num_layers": IntUniformDistribution(1, 3, step=1),
    "hidden_size": IntUniformDistribution(4, 64, step=4),
    "lr": LogUniformDistribution(1e-4, 1e-2),
}

To discuss:

Is tuning lr necessary?
It is unclear how to parameterize MLPModel parameter hidden_size because it accepts list of sizes for the layers. Even if we come up with parametrization it is unclear how to implement it because it is expected that we have a complete set of parameter values. We can use CategoricalDistribution but it seems not very effective.

Test cases
Look at https://github.com/tinkoff-ai/etna/issues/1184.
Additional context
No response

Is tuning lr necessary? - I think it's ok for now but may be can make lr a little bit wider from the left
we can add context size for rnn

Closed by #1218.


Gradle HTTP client does not retry network issues that occur during SSL handshake

Gradle uses Apache HTTP client for dependency repository and build cache access and inherits its built-in request retry behaviour.  This behaviour is implemented by DefaultHttpRequestRetryHandler which treats all exceptions as retriable except the following:

InterruptedIOException.class
UnknownHostException.class
ConnectException.class
SSLException.class

This strategy does not account for read timeouts that can happen as part of the SSL handshake process, manifesting as an SSLException with a SocketTimeoutException cause.
It's possible that this is mitigated for dependency resolution and publishing activities by use of NetworkingIssueVerifier, which seems to be an application level retry component.
Expected Behavior
Network transmission faults during the SSL handshake process should be retried.
Current Behavior
Network transmission faults during the SSL handshake process are not retried, at least for the HTTP build cache service.
Context
When this occurs, the remote build cache is disabled for the rest of the build potentially causing build time regressions.
Steps to Reproduce
To reproduce, a cache server that simply doesn't respond after accepting the start of the SSL handshake is required.
Your Environment
Client side behaviour observed with JDK 1.8.0_342-b07.

Note: the fallback logic should also be improved:

https://github.com/gradle/gradle/issues/28865


bufio: Scanner.Scan panics on poorly behaved io.Reader during an error

What version of Go are you using (go version)?

$ go version
go version go1.14 darwin/amd64

Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/Users/neilpa/Library/Caches/go-build"
GOENV="/Users/neilpa/Library/Application Support/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOINSECURE=""
GONOPROXY=""
GONOSUMDB=""
GOOS="darwin"
GOPATH="/Users/neilpa/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/local/Cellar/go/1.14/libexec"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/local/Cellar/go/1.14/libexec/pkg/tool/darwin_amd64"
GCCGO="gccgo"
AR="ar"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
GOMOD="/Users/neilpa/code/go-iris/go.mod"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/f2/vxszd7l136nbnp3g_tx_g2n40000gp/T/go-build872804308=/tmp/go-build -gno-record-gcc-switches -fno-common"
GOROOT/bin/go version: go version go1.14 darwin/amd64
GOROOT/bin/go tool compile -V: compile version go1.14
uname -v: Darwin Kernel Version 18.7.0: Thu Jan 23 06:52:12 PST 2020; root:xnu-4903.278.25~1/RELEASE_X86_64
ProductName:	Mac OS X
ProductVersion:	10.14.6
BuildVersion:	18G3020
lldb --version: lldb-1<IP_ADDRESS>
Apple Swift version 5.1.2 (swiftlang-1100.0.278 clang-1<IP_ADDRESS>)

What did you do?
If an io.Reader incorrectly returns -1 for bytes read along with an error from Read, bufio.Scanner will panic indexing the slice here.
Here's a simple repro on the go playground
This was discovered with a real project that's exposing native serial port APIs as io.Readers. There's PRs open fix the implemenation, however, it may be useful for bufio.Scanner to be resilient to this failure mode. Especially since golang.org/x/sys/unix.Read can return negative values under error, as is the case here.
What did you expect to see?
The error from the Read call to bubble up and be returned from Scanner.Err().
What did you see instead?
The scanner panics
panic: runtime error: slice bounds out of range [5:4]

goroutine 1 [running]:
bufio.(*Scanner).Scan(0x41a750, 0x40c178, 0x41a748, 0x1)
	/usr/local/go/src/bufio/scan.go:145 +0xc60
main.main()
	/tmp/sandbox512182328/prog.go:26 +0x200

I don't think it's necessary for bufio.Scanner to avoid panicking when passed an io.Reader that doesn't implement the contract described at https://golang.org/pkg/io/#Reader.  It's important that the standard library avoid corrupting memory or otherwise behaving unpredictably.  It's not essential to avoid panicking when given invalid input.

I made an edit to my original report that I do wan to explicitly call out. This is ostensibly a wrapper of golang.org/x/sys/unix.Read which can return negative values on error. I'd imagine this isn't the only instance where someone is wrapping that into an io.Reader and blindly returning the results.

This is a tricky one. Normally I agree with @ianlancetaylor , and this case is no exception, but then there's this comment in the code:
		// Finally we can read some input. Make sure we don't get stuck with
		// a misbehaving Reader. Officially we don't need to do this, but let's
		// be extra careful: Scanner is for safe, simple jobs.

That tells me that it's worth adding the check on the next line for a non-negative n.

OK, sent CL 225357.


Verification on Windows report

On the Verification step where you open the OpenOCD connection, I've noted the following:
The command labeled as for *nix: openocd -f interface/stlink-v2-1.cfg -f target/stm32f3x.cfg works on Windows, although with a warning to use stlink.cfg, ie without the -v2-1, and the one labeled for windows doesn't work; it raises this error:
$: The term '$' is not recognized as the name of a cmdlet, function, script file, or operable pr ogram.

In this case the $ is meant to indicate that this line is a command for you to execute; you shouldn't actually type the $. It's used because on UNIX/Linux/Mac shells a $ symbol is the historical prompt symbol.
On windows as on *nix you should just run the command itself: openocd -s C:\OpenOCD\share\scripts -f interface/stlink-v2-1.cfg -f target/stm32f3x.cfg

Thank you very much. Either command now works for me.


Remove dependencies on providers and support unknown ones

Hey Jon,
thanks a lot for your awesome library, i been using it for a couple of years in my projects!
With your latest version 7, the changes to the way DesignTimeServices could be handed into the Compare-Method broke compatibility with Firebird .NET provider and probably others as only three Providers (SQLite, SQL-Server & Postgres) are known to your library.
This Pull-Request changes the implementation of the factory to be a little more eager in trying to create an appropriate DatabaseModelFactory and also removes dependencies on the other providers as this is imo unncessary ballast for your library.
Feel free to leave your comments, glad to hear your feedback!

Hi @lweberprb,
Just to be clear, are you saying that this will automatically find the correct scaffolding service based on your DbContext? That sounds very useful. I see that you still have a "Your database provider isn't supported" exception so does this suggest it might not work?

It will indeed try to resolve the appropriate DatabaseModelFactory based on your DbContext instance. The exception is there if we are unable to call the contructor of the DatabaseModelFactory implementation of the provider. With this PR it is possible to construct all implementations that offer a default constructor or a constructor that accepts a scaffolding logger.

But you are right, the exception message might be misleading in this case. It would probably be better to throw something in the means of "Unable to construct DatabaseModelFactory of provider X, due to unknown contructor paramter combination" or something like this.

Thanks @lweberprb, your code is a much better of my idea of handing other EF Core database types (see issue #22). Nice trick to load the assembly - super cool.
Now my problem is that my 'dev' branch contains code for issue #21 and #25 (version 6.0.2) and holds the the code ready for .NET 8. The simplest way to do this is to merge your PR to 'main', merge to 'dev' and release this feature in .NET 8 . The downside is .NET 8 isn't out until November 14, 2023. I can create a prerelease NuGet of this library using 8.0.0-rc.1, but you don't get the final .NET 8 version until end of November.
Any comments?

Hi all
Jumping in here since I had the same challenges as @lweberprb and the intention (but not yet the time) to come up with an issue.
Initially i had the Idea to pull IDatabaseModelFactory from the design service context according to the Documentation. Unfortunately, this is not working anymore (documentation issue https://github.com/dotnet/EntityFramework.Docs/issues/4454 is placed).
After that, I was looking how EfCore is resolving design services and found DesignTimeServicesBuilder. I made an example how to use the builder here.
The builder has come challenges:

The builder uses reflection to find design services in different assemblies. To ensure equal behavior like e.g. EfCore CLI some further investigation is needed.
Maybe the design services must be referenced differently (see: https://learn.microsoft.com/en-us/ef/core/cli/services#referencing-microsoftentityframeworkcoredesign)
A IOperationReporter must be implemented, since the EfCore implementations are internal.

All in all the solution of @lweberprb is probably the more straightforward. In any case:

Would it not be more future proof to look for IDatabaseModelFactory implementations instead the base class?
Maybe use the design service stack like described here and create instances with ActivatorUtilities.CreateInstance?

Since the merge request is now merged: @JonPSmith I let the descision up to you if you want to follow up this in a separate issue.

Hi @bgrauer-atacom,
Thanks for letting me know the the creation of a IDatabaseModelFactory for a specific database has changed in .NET 8. All my tests using SqlServer failed because the SqlServerDatabaseModelFactory has changed (now needs the IRelationalTypeMappingSource as the third parameter), but
But this clearly shows that if I want to this library to that supports any database that EF Core can access, then I have a common approach. Problem is that each database can have different parameters in its IDatabaseModelFactory. For instance the  MySqlDatabaseModelFactory has a third parameter of type IMySqlOptions.
So, is it seem impossible to make this library that will work all database types.
Any comments from @bgrauer-atacom and @lweberprb??

Hmm, changes in the providers IDatabaseModelFactory are to be expected. Maybe the CompareWithEfDb method should accept a IDatabaseModelFactory instance? The Caller is therefore responsible for creating the instance and the library can just use it.
Could be a new overload that skips the libraries internal resolver methods for creating a particular instance.
Another idea could be, to resolve the constructors paramaters by reflection also. I.e. collect the necessary types and resolve these via the DbContext IServiceProvider. Might be worth a try although this might get rather complex for such a simple task.

So, is it seem impossible to make this library that will work all database types.

From my understanding this should be possible when the library interacts with the design libraries like the EFCore CLI tools do.
Lets take Scaffolding as an example / inspiration:

When executing: dotnet ef dbcontext scaffold initially a lot magic happens . For us relevant:

Project path / assembly path is evaluated
Startup project path / startup project assembly is evaluated
Provider is read from arguments

The CLI tool gets the design assembly from the target project and invokes scaffolding. At that point the design service stack is created , built and used.

Putting all together:
// This happens in the test project
var dbContextBuilder = new DbContextOptionsBuilder<MyDbContext>();
dbContextBuilder.UseSqlite("Data Source=:memory:");
var dbContext = new MyDbContext(dbContextBuilder.Options);

// TODO: Maybe implement handler actions for logging purposes?
// HINT: The classes are only available when including the design package like this:
// https://learn.microsoft.com/en-us/ef/core/cli/services#referencing-microsoftentityframeworkcoredesign
var reporter = new OperationReporter(new OperationReportHandler());

// REVIEW: According to my understanding the assembly is where the DBContext is
var assembly = typeof(MyDbContext).Assembly;

// REVIEW: This is not the same behaviour as in the CLI but we don't know the real startup project. Using the test project
// assembly as stratup assembly hand enables the possibility to define design services inside of the test project for test purposes.
var startupAssembly = Assembly.GetEntryAssembly() ?? assembly;

// HINT: The classes are only available when including the design package like this:
// https://learn.microsoft.com/en-us/ef/core/cli/services#referencing-microsoftentityframeworkcoredesign
var builder = new DesignTimeServicesBuilder(assembly, startupAssembly, reporter, Array.Empty<string>());
var serviceProvider = builder.Build(dbContext);

var modelFactory = serviceProvider.GetRequiredService<IDatabaseModelFactory>();

If you don't want to undo https://github.com/JonPSmith/EfCore.SchemaCompare/issues/4, you could also put the service stack together using reflection:
/ / This happens in the test project
var dbContextBuilder = new DbContextOptionsBuilder<MyDbContext>();
dbContextBuilder.UseSqlite("Data Source=:memory:");
var dbContext = new MyDbContext(dbContextBuilder.Options);

// REVIEW: According to my understanding the assembly is where the DBContext is
var assembly = typeof(MyDbContext).Assembly;

// REVIEW: This is not the same behaviour as in the CLI but we don't know the real startup project. Using the test project
// assembly as stratup assembly hand enables the possibility to define design services inside of the test project for test purposes.
var startupAssembly = Assembly.GetEntryAssembly() ?? assembly;

try
{
    // REVIEW: In my case, the assembly was loaded correct. Unsure if this works in all cases.
    var designAssembly = Assembly.Load("Microsoft.EntityFrameworkCore.Design");

    var reportHandlerType = designAssembly.GetType("Microsoft.EntityFrameworkCore.Design.OperationReportHandler")
        ?? throw new InvalidOperationException("Unable to create an 'OperationReportHandler' instance. Are you using a supported EntityFrameworkCore version?");
    // TODO: Maybe implement handler actions for logging purposes?
    var reportHandler = Activator.CreateInstance(reportHandlerType, null, null, null, null);

    var reporterType = designAssembly.GetType("Microsoft.EntityFrameworkCore.Design.Internal.OperationReporter")
        ?? throw new InvalidOperationException("Unable to create an 'OperationReporter' instance. Are you using a supported EntityFrameworkCore version?");
    var reporter = Activator.CreateInstance(reporterType, reportHandler);

    var serviceBuilderType = designAssembly.GetType($"Microsoft.EntityFrameworkCore.Design.Internal.DesignTimeServicesBuilder")
        ?? throw new InvalidOperationException("Unable to create an 'DesignTimeServicesBuilder' instance. Are you using a supported EntityFrameworkCore version?");
    var serviceBuilder = Activator.CreateInstance(serviceBuilderType, assembly, startupAssembly, reporter, Array.Empty<string>());

    var serviceProvider = (IServiceProvider?) serviceBuilderType.GetMethods()
        .Where(x => {
            if (x.Name != "Build")
            {
                return false;
            }
            var pars = x.GetParameters();
            if(pars.Length != 1)
            {
                return false;
            }
            return pars[0].ParameterType.Name == "DbContext";
        })
        .FirstOrDefault()
        ?.Invoke(serviceBuilder, new object[] { dbContext })
        ?? throw new InvalidOperationException("Unable to bild design time service provider. Are you using a supported EntityFrameworkCore version?"); ;

    var modelFactory = serviceProvider.GetRequiredService<IDatabaseModelFactory>();
}
catch (FileNotFoundException ex)
{
    throw new InvalidOperationException($"Your startup project '{startupAssembly.GetName()}' doesn't reference " +
        "Microsoft.EntityFrameworkCore.Design. This package is required for the SchemaCompare to work. " +
        "Ensure your startup project is correct, install the package, and try again.", ex);
}

Hi @bgrauer-atacom,
Thanks again for another way to get the scaffolding that I hadn't thought of. So, just to be clear you have looked at the program used in the  dotnet ef dbcontext scaffold command and pulled out the code inside to get the model factory. Therefore, this should work for any EF Core database provider. It that correct?
I tried your code on my unit tests and it worked. I tried both of your code approaches and I thought that the second version makes it easier to create a new version when the next .NET is released every year. (I'm retired now but I want to make sure my libraries are available in the latest .NET releases and help people who ask about how to use my libraries).
I need a bit more work on this, but I will release a prerelease NuGet of this lib if you check it out (PS. The code in the 'dev' branch at the moment.
Thanks again.
PS. Could you send me a link to the dotnet ef dbcontext scaffold program as using internal code can change.

Hi guys,
I have released EfCore.SchemaCompare 8.0.0-rc2-0002 for people to try this.
@bgrauer-atacom, I tried the shorter version with full Microsoft.EntityFrameworkCore.Design but my tests shows that the user must have the Microsoft.EntityFrameworkCore.Design in the caller's app. Therefore I went for the longer version, which allows me to update the Microsoft.EntityFrameworkCore.Design without having hand-change the .csprog file.
I'm now asking to try this out and let me know if is a problem.

PS. The code in in the main branch now

Hi @JonPSmith
Sorry for my really bad response time.
First of all: Thanks for the changes. I really like your decision to use full reflection. (You are still referencing Microsoft.EntityFrameworkCore.Design. I think this is not necessary anymore.)
Regarding dotnet ef dbcontext scaffold:

The entry point is here: https://github.com/dotnet/efcore/blob/release/8.0/src/dotnet-ef/Program.cs
The CLI mechanism executes DbContextScaffoldCommand.Execute
The command creates a ReflectionOperationExecutor (here).
The command executes the executor.
The executor creates an instance of OperationExecutor an OperationExecutor+ScaffoldContext with reflection where then the scaffolding is done with the design dlls located inside of the project.

(Disclaimer: This is what i found out by "reading code". There might be some wrong assumptions due to the complexity.)
Testing
Unfortunately, i am unable to test the newest Nuget version (8.0.0), since a database provider i use (Firebird) in my current projects does not yet support .NET 8 and EF 8.
I took the repo and rolled back to .NET/EF 7 for tests and had no breaking issues related to loading design services.
One minor thing: When the design DLLs are missing and the library is executed from a unit test (Visual Studio 17.8.1) i get following Exception-Message:
Your startup project 'testhost, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' doesn't reference Microsoft.EntityFrameworkCore.Design. This package is required for the SchemaCompare to work. Ensure your startup project is correct, install the package, and try again.

It seems, that the entry assembly does not provide much helpful information unless someone does this inside of the test project.

Hi @bgrauer-atacom,
Thanks for the extra info, but I'm not sure in your Testing section. I found that having the Microsoft.EntityFrameworkCore.Design of the EfCore.SchemaCompare didn't work on its own, and the caller has to have the Microsoft.EntityFrameworkCore.Design too. Is that what you see too?

Yes. The package Microsoft.EntityFrameworkCore.Design must somehow end up in the build output. Otherwise we would not be able to load the assembly.
This happens either by removing
<PrivateAssets>all</PrivateAssets>
<IncludeAssets>runtime; build; native; contentfiles; analyzers; buildtransitive</IncludeAssets>

inside of the library project or by referencing the library inside of the test project.
I prefer the current solution since this is more near to the behavior of the CLI and gives the user more freedom which design library he wants to use.
Maybe there is a better solution but i am not an msbuild or Nuget expert.

Another thing I i experienced while looking thru Ef libraries is, that they do not pin the version of the EF libraries:

https://github.com/npgsql/efcore.pg/blob/main/src/EFCore.PG/EFCore.PG.csproj#L16
https://github.com/dotnet/efcore/blob/main/src/EFCore.Sqlite.Core/EFCore.Sqlite.Core.csproj#L20

This is probably a good thing to avoid dependency conflicts?

Good, we are in sync on this. I will keep with the current arrangement.

Another thing...

I define the NuGet by version as each NET release often add new features / changes. EF Core NET 8 has new features and some subtle changes to existing methods.


Docs on fail-fast doesn't indicate that it can be an expression

Code of Conduct

[X] I have read and agree to the GitHub Docs project's Code of Conduct

What article on docs.github.com is affected?
https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstrategyfail-fast
What part(s) of the article would you like to see updated?
jobs.<job_id>.strategy.fail-fast appears to accept expressions (not just booleans) per the context availability docs. It would be much appreciated if the fail-fast docs are further clarified to avoid confusion.
See examples in the wild: https://github.com/search?q=path%3A.github%2Fworkflows+"fail-fast%3A+%24{{"&type=code
Additional information
No response

Thanks for opening this issue and for including examples to verify your statement! You or anyone else is welcome to open a PR to update the documentation around fail-fast (e.g. content/actions/learn-github-actions/contexts.md and data/reusables/actions/jobs/section-using-a-build-matrix-for-your-jobs-failfast.md).


make mentor application form more attractive.

hi @mohityadav0903 , Rajagopalan this side.
I would like to take up this issue of making the mentor login form more attractive.
Kindly assign the same to me.

@rv602  you can start working  on this issue.

hey @rv602 it's been more than one month. wru?


Pasting text from Windows to xrdp session has double line breaks

Basically, having the same issue as this SO post: https://superuser.com/questions/1156974/double-new-line-when-copy-to-konsole-on-xrdp
However, the suggested fixes do not work. They break using Enter key on the keyboard when trying to use things like sudo, I cannot hit enter to send my password.

xrdp 0.9.20

Duplicate of #1746.
I'm pretty sure this is a bug on our side rather than anything to do with terminal settings. I've not had the time to look at it yet though.

Closing, as a duplicate.


[7.x] [POC] Add allowedExceptions to queued jobs

This PR does 2 things:
1- Adds a UUID to job payload.
2- Adds a maxExceptions to the payload.
maxExceptions is set by defining a $allowedExceptions property in the jobs class.
Each time the job fails with an unhandled exception, the worker will check for the maximum exceptions allowed and fail the job if it exceeds this limit and ignore the attempts.
So if $allowedExceptions = 2 and $tries = 10. The worker will retry the job 10 times if it was released without an exception, but only 2 times if it was released with an exception.

What is a use case?

@antonkomarev it's to solve this problem a bit differently and across all drivers: https://github.com/laravel/framework/pull/31537

Will the job be released instantly, or is it possible to set amount of seconds?

@andershagbard you can use --delay or delaySeconds to control the delay.

Hm, any example how to achieve requeue functionality with that? I mean when a job is released and it's not a "real" attempt but throttling attempt I don't want to increment job's attemps.


Fix broken warning message

If you click pick with nothing selected, there should be an error message popup explaining that nothing will happen. This is currently broken because of an issue with the picker-ui.js logic
this is not defined, so it should be self at that scope.

Thanks, and apologies for the late merge!


[W5.11][W13-A2]Toh Jing Jie Jasmund

-Add function and find function made case-insensitive
First letter is automatically capitalised while the rest in lowercase
-List of people will be sorted each time a new person is added
Sorted according to name in ascending order

@jasmoon
Some comments added. Please ack & close the PR after reading comments.


feat(blockifier): limit characters in cairo1 revert trace

This change is

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#1469
#1468  👈
#1461
#1460
#1459
#1458
#1457
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @dorimedini-starkware and the rest of your teammates on  Graphite

crates/blockifier/src/execution/stack_trace.rs line 278 at r4 (raw file):

 .expect("Stack has at least two frames at this point.")

I'd rather not use expect her.

crates/blockifier/src/execution/stack_trace.rs line 205 at r3 (raw file):
Previously, dorimedini-starkware wrote…
this is getting a bit ugly... both the stack and the failure reason can hit this limit, we may need to truncate them both.
when would we realistically have a trace longer than 15K chars?
anyway, modified, LMK what you think

I guess I didn't think it was going to be that complicated.
but if you already wrote it lets keep it.

crates/blockifier/src/execution/stack_trace_test.rs line 851 at r6 (raw file):

    assert!(
        format!("{}", extract_trailing_cairo1_revert_trace(&next_call_info)).len()
            <= TRACE_LENGTH_CAP

Is putting the actual string here bad?
as it is written the length is the only thing being tested.
Code quote:
        format!("{}", extract_trailing_cairo1_revert_trace(&next_call_info)).len()
            <= TRACE_LENGTH_CAP


Getting login_required after login

I've tried jinsta -u username -p password -w ./jinsta_data and I get
? Enter sms / email code: 402138
info:    starting with timeline feed
(node:22695) UnhandledPromiseRejectionWarning: IgLoginRequiredError: GET /api/v1/fbsearch/suggested_searches/?type=users - 403 Forbidden; login_required
    at Request.handleResponseError (/home/imkimchi/.nvm/versions/node/v11.13.0/lib/node_modules/jinsta/node_modules/instagram-private-api/dist/core/request.js:93:24)
    at Request.send (/home/imkimchi/.nvm/versions/node/v11.13.0/lib/node_modules/jinsta/node_modules/instagram-private-api/dist/core/request.js:49:28)
(node:22695) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:22695) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
(node:22695) UnhandledPromiseRejectionWarning: IgLoginRequiredError: POST /api/v1/feed/timeline/ - 403 Forbidden; login_required
    at Request.handleResponseError (/home/imkimchi/.nvm/versions/node/v11.13.0/lib/node_modules/jinsta/node_modules/instagram-private-api/dist/core/request.js:93:24)
    at Request.send (/home/imkimchi/.nvm/versions/node/v11.13.0/lib/node_modules/jinsta/node_modules/instagram-private-api/dist/core/request.js:49:28)
(node:22695) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 2)

tried multiple times deleting cookies and stuffs but still not working! any ideas?

Same here.
node index.js
info:    session expired, going for relogin
info:    starting with timeline feed
(node:10936) UnhandledPromiseRejectionWarning: IgLoginRequiredError: POST /api/v1/feed/timeline/ - 403 Forbidden; login_required
    at Request.handleResponseError (C:\Users\viniciussantiago\Documents\jinstabot\node_modules\instagram-private-api\dist\core\request.js:93:24)
    at Request.send (C:\Users\viniciussantiago\Documents\jinstabot\node_modules\instagram-private-api\dist\core\request.js:49:28)
    at async TimelineFeed.request (C:\Users\viniciussantiago\Documents\jinstabot\node_modules\instagram-private-api\dist\feeds\timeline.feed.js:59:26)
From previous event:
    at processImmediate (internal/timers.js:439:21)
From previous event:
    at Function.executeRequestsFlow (C:\Users\viniciussantiago\Documents\jinstabot\node_modules\instagram-private-api\dist\services\simulate.service.js:49:24)
    at SimulateService.postLoginFlow (C:\Users\viniciussantiago\Documents\jinstabot\node_modules\instagram-private-api\dist\services\simulate.service.js:59:32)
    at login (C:\Users\viniciussantiago\Documents\jinstabot\node_modules\jinsta\dist\session.js:140:19)
    at runNextTicks (internal/process/task_queues.js:58:5)
    at processImmediate (internal/timers.js:412:9)
(node:10936) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:10936) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
(node:10936) UnhandledPromiseRejectionWarning: IgLoginRequiredError: POST /api/v1/feed/timeline/ - 403 Forbidden; login_required
    at Request.handleResponseError (C:\Users\viniciussantiago\Documents\jinstabot\node_modules\instagram-private-api\dist\core\request.js:93:24)
    at Request.send (C:\Users\viniciussantiago\Documents\jinstabot\node_modules\instagram-private-api\dist\core\request.js:49:28)
    at async TimelineFeed.request (C:\Users\viniciussantiago\Documents\jinstabot\node_modules\instagram-private-api\dist\feeds\timeline.feed.js:59:26)
    at async TimelineFeed.items (C:\Users\viniciussantiago\Documents\jinstabot\node_modules\instagram-private-api\dist\feeds\timeline.feed.js:74:26)
    at async mediaFeed (C:\Users\viniciussantiago\Documents\jinstabot\node_modules\jinsta\dist\features\utils.js:24:19)
    at async timeline (C:\Users\viniciussantiago\Documents\jinstabot\node_modules\jinsta\dist\features\timeline.js:31:10)
    at async run (C:\Users\viniciussantiago\Documents\jinstabot\node_modules\jinsta\dist\main.js:56:5)
(node:10936) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 2)

------------- EDIT ----------
Ok, just got it to work, as @breuerfelix said in https://github.com/breuerfelix/jinsta/issues/29#issuecomment-544458213_ :

if the mentioned PR is merged, try the following:
run jinsta with jinsta -r -s my_seed -u bla -p bla
if you use advanced config set config.reset = true and config.seed = 'my_seed'
try if it works :)
you have to use -r or config.reset only if you choose a new seed key because this means to reset the old session and generate a new one
if it does work out, try to get the value when you experience a block.
if it is 30 for example, run the bot twice a day with a limit of 20 and increment this each day by 2 to 5 and see if you hit the limit again
try to reuse your old seed keys from time to time and increase their limit aswell, i would like to know if instagram saves the device id with the interaction limit

I just added to my code those following lines:
config.reset = true;
config.seed = '123456';

And now it's working. I'm using advanced mode to start.
Hope it helps.

yuup changing seed actually worked!

i dont know why this really happened... but good to know that changing the seed is working :)


AMD: incorrect module build, no module name

Can you please fix the AMD error (by grunt usage), because there isn't any name given for that module.
// AMD. Register as an anonymous module.
define(['jquery', 'jquery-mousewheel'], factory);
to
define('datetimepicker', ['jquery', 'jquery-mousewheel'], factory);
in line 10 in jquery.datetimepicker.js and line 586 build/jquery.datetimepicker.full.js

or pls add a version, maybe as build/jquery.datetimepicker.full.amdnamed.js or so..., which contains this adaption. So that I can use bower without modification in that case.

How is this not added after 2 years, it's such a simple and necessary change.


[Map] DM-Heavy Metal III

Hash: 754e6cdffaf28b0ba7a183c203a33f5c00d2218f
Current name: DM-Heavy Metal III
From the readme, the author's name is  Rudi the Searcher
Player Count = 2-4

Fixed


feat(Traefik Hub): add APICatalogItem and ManagedSubscription support

What does this PR do?
This PR brings the new resources (CRD, RBAC, webhook) required by Traefik Hub for:

APICatalogItem: Define who can see APIs in the API catalog.
ManagedSubscription: Declare which Application can consume which API and how much.

These 2 resources replaces the now deprecated APIAccess resource. The APIAccess used to represent simultaneously what you can see and consume.
Motivation
Bring the new Traefik Hub CRDs for managing subscription and catalog entries.
More

[ ] ~Yes, I updated the tests accordingly~
[x] Yes, I updated the schema accordingly
[x] Yes, I ran make test and all the tests passed

@mloiseleur As discussed, I have added the AIService CRD and the support for ManagedSubscription's claims validation. I let review it one more time.


When creating new user from backend it redirects to view page and it doesn't exist.

Hello @yeesoft !
I saw an error, when I try to create a new user directly from backend, after created it redirects to view page and it doesn't exists. I think that to keep things how everything is programmed we should make it redirect to update page as every other forms after saving them.
Regards,
José

fixed


Node16 becoming deprecated, need new version that utilizes Node20

Received a warning that Node16 actions are deprecated and need to update to Node20
For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

I'm receiving this error message too:
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20<EMAIL_ADDRESS>

I'm receiving this error message too:
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: Azure/functions-action@v1. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

Has there been any movement on this? I'm also running into this error:
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: azure/functions-action@238dc3c45bb1b04e5d16ff9e75cddd1d86753bd6. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Much more urgent now

Is there any update about this?

Interested too when the update is going to come

there are a few open PRs on this - any update on merging them?

Is there any update on this ?

Update to Node 20 is part of PR https://github.com/Azure/functions-action/pull/229

Can we please get the new release version?

@PatelAman18, latest v1 has all the changes now.


As a customer, I should be able to manage my shopping cart

As a customer, I should be able to manage my shopping cart.

Acceptance Criteria

After adding items to my order, they are displayed in the shopping cart.
More items of the same type can be added to the shopping cart.
Items can be removed from the shopping cart.

[ ] #17
[ ] #18
[ ] #19

[ ] #17
[ ] #18
[ ] #19


Twitter Meta Tags

Hi Everyone,
playing around with the meta tags codex generates I found the following:
https://github.com/jakewies/hugo-theme-codex/blob/a9a6f0c92ba89408a0527c5440ff21b30e382e10/layouts/_default/baseof.html#L22
As per the twitter card documentation this value should not be the url but the @username of content creator
https://developer.twitter.com/en/docs/tweets/optimize-with-cards/overview/markup
On a similar note the twitter:site meta tag should not be a url either but @username of website.
https://github.com/jakewies/hugo-theme-codex/blob/a9a6f0c92ba89408a0527c5440ff21b30e382e10/layouts/_default/baseof.html#L21
Obviously both can, in many cases, be the same @username.
I would be happy to discuss and implement something to make the use of twitter tags more in line with the official twitter documentation.
As I am not deeply familiar with project layout or hugo templating in general I would love some help to get me started.
I will try to take a first stab at it later today.
From my understanding this would be require changes along the lines of

Introduce new settings twitter_author_handle and twitter_site_handle
Changing _default/basof.html to prefer the new settings for both fields and falling back to the twitter setting to not introduce backwards breaking changes
Updating the documentation to explain the new behaviour

The twitter link used in the social icons should, from my understanding, not be affected by this at all.

I invested some time into getting Twitter and Facebook metadata right, which is available as a theme component here, it might offer some pointers into getting things right in Codex. For my personal site I opted to override baseof.html and use the component directly since I already had things set up for it from the previous theme I used.

This is interesting. I didn't realize we were doing things improperly. Thanks a ton for pointing this out @ProfessorLogout. It looks like we'll have to make some adjustments to config.toml, as right now we're only requiring the url to the user's Twitter profile. We also have to keep in mind that some people who use the theme may not have a twitter account at all.
@msfjarvis I'm poking through hugo-social-metadata and I would really like to use it in this theme. I've never configured a Hugo theme using modules before. It should be possible to use your lib in this project, yes?

@msfjarvis I'm poking through hugo-social-metadata and I would really like to use it in this theme. I've never configured a Hugo theme using modules before. It should be possible to use your lib in this project, yes?

I know that you can use a go.mod file to load themes into a site, but I'm not sure if that resolves dependencies recursively as well, or whether Hugo will fetch theme dependencies for users who either subtree merge or submodule their themes. Probably need to research a bit.

@ProfessorLogout I spazzed out and didn't read the rest of your comment. I would love for you to take a stab. I can help you of course. Right now all this info lives in layouts/_default/baseof.html, which I believe you've already figured that out. We can use @msfjarvis project as reference and improve the implementation ourselves. What do you think?

As mentioned in the PR:
Long term I would like to decouple meta tags from the social icons and introduce the ability to change them per post.
Not limited to the two twitter tags changed here.
This would be similar to @msfjarvis efforts with hugo-social-metadata but based on my experience with opengraph.
What would you think is the better approach:

Contributing in hugo-social-metadata and trying to get the package included here (or at least mentioned in README.md for new users)
Contributing here and re-implementing some parts of @msfjarvis previous work

I would love to have social metadata managed in a module such as your hugo-social-metadata @msfjarvis, and then we can consume that in this project. I've taken a look at #86 from @ProfessorLogout and I think it will get us over the hump right now. I agree that long term we should find a better solution. It's becoming a little messy in config.toml.
I am going to merge the PR and open a new issue regarding improvements to the metadata and loop you both in. Sound good?


Unknown types found

I've added a custom chain in app/lib/page/profile/settings/remoteNodeListPage.dart using Polkawallet-Flutter https://github.com/polkawallet-io/polkawallet-flutter, but when I run the app in Android Studio it's giving an error that I haven't defined the custom types (i.e. RoamingOperatorIndex, etc):
[ +130 ms] I/chromium(12339): [INFO:CONSOLE(23)] "2020-05-13 13:18:37        API/INIT: Error: FATAL: Unable to initialize the API: createType(RoamingOperatorIndex):: Cannot construct unknown type RoamingOperatorIndex", source:  (23)
[+34304 ms] I/chromium(12339): [INFO:CONSOLE(23)] "2020-05-13 13:19:11          API-WS: disconnected from wss://testnet-frankfurt-v0.1.0-alpha.datahighway.com code: '1006' reason: ''", source:  (23)
[+3186 ms] I/chromium(12339): [INFO:CONSOLE(23)] "2020-05-13 13:19:15        API/INIT: Connection to new genesis detected, re-initializing", source:  (23)
[+8748 ms] I/chromium(12339): [INFO:CONSOLE(23)] "Unknown types found, no types for MiningSpeedBoostConfigurationHardwareMining,

Where can I defined the custom types in the Polkawallet-Flutter codebase for connecting to a custom chain?
(i.e. in Polkadot.js Apps I just go to https://polkadot.js.org/apps/#/settings/developer, and paste my custom types there)
FYI, these are my custom types: https://github.com/DataHighway-DHX/node/blob/master/custom_types.json

You may find lib/js_service_kusama and lib/js_service_acala in branch develop, that's because the app doesn't handle Types itself, it runs js SDK in a hidden webview to codec the substrate types. So we have a polkadot.js for KUSAMA, and another polkadot.js for Acala.
For your case, you need to use a customized polkadot.js sdk with your custom_types.json built in, as acala.js did.


对比 Contrast (AEGHB-232)

100 devices are networked to send and receive data to the server using espmesh or espnow.Which is better?

@LYL14 Could you detail describe the scenario?

If your 100 devices want to access the remote cloud directly, it's recommend to use esp-mesh-lite. If only 1 device can access the remote cloud, this device will work as a gateway, and in the local network, it will communicate with other devices by esp-now.

@LYL14  Closing this issue since there has been no update on this. Please feel free to reopen if required.


screw_your_friends.py

funny prank code using python

Merge my request

@Princekumaraj
Don't worry it will be approved soon as you may know their are a lot PR's right now and also it's a one month program so don't worry it will be approved as soon as possible also I can't merge all PR's blindly as it may result in the repo being excluded from the program like many other repo so be patient full you PR will be accepted soon. Happy Hactoberfest

bro it shows ur project is excluded from hacktoberfest2021. why ?

@Princekumaraj
Actually this repo is now been excluded from hactoberfest I was fearing that it will happen eventually their can be any reason like a lot of spam PR’s so it can’t be helped but yeah it’s a one month long program so their is a lot of time to do more PR’s on many different repo’s. So, yeah Happy Hactoberfest

add labels of hacktoberfest and hacktoberfest2021 and hacktoberfest-accepted

now u can merge my file dude


Blinkenlights

Blinkenlights feature, as discussed in issue #766

Guess we are good to land this. Some small coding style changes to fix and we can merge this:
Messages

========

mpf/config_players/blinkenlight_player.py

  Line: 2

    pylint: unused-import / Unused deepcopy imported from copy

  Line: 4

    pylint: unused-import / Unused RGBColor imported from mpf.core.rgb_color

  Line: 5

    pylint: unused-import / Unused Util imported from mpf.core.utility_functions

  Line: 29

    pylint: protected-access / Access to a protected member _restart of a client class (col 12)

  Line: 31

    pylint: no-self-use / Method could be a function (col 4)

  Line: 36

    pylint: no-self-use / Method could be a function (col 4)

  Line: 41

    pylint: no-self-use / Method could be a function (col 4)

mpf/devices/blinkenlight.py

  Line: 3

    pylint: unused-import / Unused partial imported from functools

  Line: 7

    pylint: unused-import / Unused ColorException imported from mpf.core.rgb_color

  Line: 13

    pep8: E302 / expected 2 blank lines, found 1 (col 1)

    pep8: E302 / expected 2 blank lines, found 1 (col 1)

  Line: 30

    pep257: D102 / Missing docstring in public method

  Line: 33

    pylint: attribute-defined-outside-init / Attribute '_color_duration' defined outside __init__ (col 8)

  Line: 34

    pylint: attribute-defined-outside-init / Attribute '_cycle_duration' defined outside __init__ (col 8)

  Line: 35

    pep8: E501 / line too long (150 > 120 characters) (col 121)

  Line: 36

    pep8: E501 / line too long (126 > 120 characters) (col 121)

  Line: 38

    pyflakes: F821 / undefined name 'NoReturn' (col 66)

  Line: 42

    pylint: missing-function-docstring / Missing function or method docstring (col 4)

    pep257: D102 / Missing docstring in public method

  Line: 43

    pep8: E501 / line too long (197 > 120 characters) (col 121)

  Line: 47

    pep8: N803 / argument name 'newValue' should be lowercase (col 27)

    pep8: N803 / argument name 'newValue' should be lowercase (col 27)

    pylint: invalid-name / Argument name "newValue" doesn't conform to '^[a-z_][a-z0-9]*((_[a-z0-9]+)*)?$' pattern (col 4)

  Line: 54

    pylint: missing-function-docstring / Missing function or method docstring (col 4)

    pep257: D102 / Missing docstring in public method

  Line: 58

    pylint: missing-function-docstring / Missing function or method docstring (col 4)

    pep257: D102 / Missing docstring in public method

  Line: 63

    pep8: E303 / too many blank lines (2) (col 5)

    pep8: E303 / too many blank lines (2) (col 5)

  Line: 72

    pylint: missing-function-docstring / Missing function or method docstring (col 4)

    pep257: D102 / Missing docstring in public method

  Line: 79

    pylint: missing-function-docstring / Missing function or method docstring (col 4)

    pep257: D102 / Missing docstring in public method

  Line: 84

    pylint: missing-function-docstring / Missing function or method docstring (col 4)

    pep257: D102 / Missing docstring in public method

Looking good.  Well I haven't had time to look at mine any further, and you have already solved the problems, so I'll bow out here on fixes.  I think it is looking great with Jan's comments there.
Jan, how do we pull this down to run against our local machine?  I'd love to pull it down and test it out with Monitor to see how its works.  Or do we have to have it merged before that can be done?

Jan, how do we pull this down to run against our local machine? I'd love to pull it down and test it out with Monitor to see how its works. Or do we have to have it merged before that can be done?

I roughly explained this in my video on the IDE setup. Short:

git clone https://github.com/densminger/mpf.git (clone Daves repo)
cd mpf (change into new dir)
git checkout blinkenlights (change to daves branch)
pip3 install -e . (install in dev mode)

There are other ways with multiple remotes in one checkout but those are a bit tricky to use unless you are very familiar with the inner workings of git.

I roughly explained this in my video on the IDE setup. Short:
* git clone https://github.com/densminger/mpf.git (clone Daves repo)

* cd mpf (change into new dir)

* git checkout blinkenlights (change to daves branch)

* pip3 install -e . (install in dev mode)

There are other ways with multiple remotes in one checkout but those are a bit tricky to use unless you are very familiar with the inner workings of git.

Haven't watched that one yet (in my saved for later on YouTube), and I love the content!!!  I will check it out to make sure I understand the ins and outs.  But basically same as getting my local, just swapping the steps for Dave, and then do mine to switch back.  Makes perfect sense!

So here's an example of some of the "weirdness" that might happen:
Let's say the blinkenlight has cycle_duration=1s (that is, each cycle lasts 1 second, regardless of how many colors the blinkenlight has).  In this case, the blinkenlight's cycle would look like this:
|       1s      |       1s      |       1s      |       1s      |
|-------|-------|-------|-------|-------|-------|-------|-------|
|  red  |  off  |  red  |  off  |  red  |  off  |  red  |  off  |

If green color is added to the blinkenlight (this assumes off_when_multiple=false), the cycle would look like this:
|       1s      |       1s      |       1s      |       1s      |
|-------|-------|-------|-------|-------|-------|-------|-------|
|  red  | green |  red  | green |  red  | green |  red  | green |

Then a third color (blue) is added:
|       1s      |       1s      |       1s      |       1s      |
|  r |  g  |  b |  r |  g  |  b |  r |  g  |  b |  r |  g  |  b |

Note that each color now is only 1/3 of a second long, since there are three of them per cycle now.
Now, let's say blue is removed from the blinkenlight, while the blinkenlight is currently showing a blue color:
|       1s      |       1s      |       1s      |       1s      |
|  r |  g  |  b |  r |  g  | b|g|  red  | green |  red  | green |
        blue is removed here ^

Notice how blue is displayed when the color is removed, and the light immediately switches to green, since green should be displayed at that point in time now that the blinkenlight only has 2 colors.  So the end result is green "flashes" very briefly before red is displayed again and the red/green cycle starts.
I hope this makes sense.  It's predictable, and I think if I was playing the game and saw this happen I would understand what happened and why the color change occurred like that.

So here's an example of some of the "weirdness" that might happen:
Let's say the blinkenlight has cycle_duration=1s (that is, each cycle lasts 1 second, regardless of how many colors the blinkenlight has). The blinkenlight only has one color (red). In this case, the blinkenlight's cycle would look like this:
|       1s      |       1s      |       1s      |       1s      |
|-------|-------|-------|-------|-------|-------|-------|-------|
|  red  |  off  |  red  |  off  |  red  |  off  |  red  |  off  |

If green color is added to the blinkenlight (this assumes off_when_multiple=false), the cycle would look like this:
|       1s      |       1s      |       1s      |       1s      |
|-------|-------|-------|-------|-------|-------|-------|-------|
|  red  | green |  red  | green |  red  | green |  red  | green |

Then a third color (blue) is added:
|       1s      |       1s      |       1s      |       1s      |
|  r |  g  |  b |  r |  g  |  b |  r |  g  |  b |  r |  g  |  b |

Note that each color now is only 1/3 of a second long, since there are three of them per cycle now.
Now, let's say blue is removed from the blinkenlight, while the blinkenlight is currently showing a blue color:
|       1s      |       1s      |       1s      |       1s      |
|  r |  g  |  b |  r |  g  | b|g|  red  | green |  red  | green |
        blue is removed here ^

Notice how blue is displayed when the color is removed, and the light immediately switches to green, since green should be displayed at that point in time now that the blinkenlight only has 2 colors. So the end result is green "flashes" very briefly before red is displayed again and the red/green cycle starts.
I hope this makes sense. It's predictable, and I think if I was playing the game and saw this happen I would understand what happened and why the color change occurred like that.

Agreed. It definitely works this way :-). I guess we should add the ordering by priority in blinkenlights_player and with that we should be good to go.

I think this is ready to go.

@densminger Looks like it needs a couple of cleanup items to pass the Travis CI build test.  All looks like general formatting and consistency stuff.  Once that's cleaned up, it should pass all three tests and get the green check mark.  Great work!
mpf/config_players/blinkenlight_player.py
  Line: 28
    pylint: missing-function-docstring / Missing function or method docstring (col 4)
    pep257: D102 / Missing docstring in public method
  Line: 34
    pylint: missing-function-docstring / Missing function or method docstring (col 4)
    pep257: D102 / Missing docstring in public method
  Line: 40
    pylint: missing-function-docstring / Missing function or method docstring (col 4)
    pep257: D102 / Missing docstring in public method

mpf/devices/blinkenlight.py
  Line: 15
    pylint: ungrouped-imports / Imports from package typing are not grouped (col 4)
  Line: 45
    pep8: E502 / the backslash is redundant between brackets (col 50)
    pep8: E502 / the backslash is redundant between brackets (col 50)
  Line: 53
    pep257: D401 / First line should be in imperative mood; try rephrasing (found 'Number')
  Line: 65
    pep257: D401 / First line should be in imperative mood; try rephrasing (found 'The')
  Line: 97
    pep257: D300 / Use """triple double quotes""" (found "-quotes)
  Line: 104
    pep257: D401 / First line should be in imperative mood (perhaps 'Remove', not 'Removes')

Green check!

Sweet!!!

I've been playing with this, and I have a question.  Right now, a blinkenlight is a SystemWideDevice object.  As such, it exists at a machine level, and the blinkenlight_player has no concept of a game or player state.  So, when a mode adds a color to a mode, and the player's ball drains, that blinkenlight will continue to flash unless the mode specifically tells it to remove its colors when the mode ends (and it would have to "remember" which colors were active when it restarts).  My question is, is this ok, or should I change the blinkenlight to be a LogicBlock instead so it can use the persist_state functionality of logic blocks?  It's not exactly a logic block since it interfaces with hardware (lights) so I don't know if this is a good fit or not.

I was looking at the same thing when I saw your edit. Agreed, just need to use that to cancel when mode ends there and it clears the stack for it's called keys.
As for starting back up, is there a scenario where it would need to do that? I would assume my shot would be in a state that it's profile calls a specific show. So if the shot is in that state when the mode starts again, it should automatically be calling the show, and adding it back to the stack.

Good point.  I think it's ok to not remember state.  I have it working so that when mode ends it removes the mode's colors automatically.  I changed the removeall action to remove_all (to make it consistent with other actions in mpf that use underscores) and I added another action called remove_mode that will remove all the colors added by the calling mode (just in case you want to remove all colors at a point other than when they're automatically removed at mode stop).
Thanks for your input, it helps a lot!
I'll push these changes shortly.

Edit: I just realized that the ConfigPlayer class has a mode_stop method. I'm guessing I could override that method and unload the blinkenlight when modes end. I would just need to keep track of which mode added which colors. So there's likely enough functionality already in ConfigPlayer to handle this correctly.

We already got a way to handle this. It is called "clear_context“. That is called when modes are unloaded, shows are stopped and in any other case. You can have a look at LightPlayer. It is similar to your approach but covers aboslutely everything in MPF. Also you probably do need the change in Blinkenlight with that.

Got it. Thanks, Jan.  I changed it to use clear_context instead.  So blinkenlight colors are removed when the associated mode/context ends.  Example, mode1 adds blue and green, mode2 adds red.  When mode2 ends, red will automatically be removed from the blinkenlight, and when mode1 ends, blue and green will be removed.  However, a caveat to this is, the colors are also removed when a show ends.  So, if a show uses blinkenlights: to add a color to a blinkenlight, then the color will only flash while the show is active, and as soon as that show ends, the blinkenlight's colors will be removed.  I am guessing this is ok, just needs to be documented?  Let the user know that if they want a blinkenlight's color to remain active for a mode, the mode should add the color to the blinkenlight via a blinkenlight_player and not a through a show.  Speaking of which, I'm working on the documentation as well.
I also renamed the key parameter in blinkenlight_player to label instead, because I think that's clearer to the end-user as to its purpose.  Finally, I added an express config for blinkenlight_player which does the add action with a uuid/random label.

@atummons Ok, both of your fixes have been pushed.  I changed the _validate_type_color method a little from what you suggested since it didn't require everything you said.  I added tests for both the bug/typo you found, as well as the tokens, so these things should continue to work in the future.

Renamed label back to key as per Jan's suggestion. @atummons, this will mean you'll need to change your code that you're using for testing as well, just fyi.

Awesome work! I'll get latest on your repo and continue to play around with my test machine.

Looks great! Everything works on my end. It's ready to go as far as I'm concerned.

Thanks for testing and confirming. This has been an awesome collaboration! Thanks @densminger @atummons .

Edit: So it looks like the "stop/remove" express config option will only remove colors that were added without a key (that is, colors that were added with the express config method, or colors that were added without specifying a key). This makes sense, I just need to update the documentation to reflect that.

Yeah exactly. My theory is that 99% of the users will have maximum one color per mode.


dist of NiiVue contains incorrect browser polyfills

Context
We are tracing a rare bug where the mere inclusion of NiiVue into a project already using hammer.js and cornerstone-tools breaks cornerstone.
Bug
The build of @niivue/niivue adds polyfills to the dist/index.js file. These polyfills are both activated incorrectly and also implemented incorrectly. I have<EMAIL_ADDRESS>installed using npm. Here are the contents of<EMAIL_ADDRESS>lines 17562 to 17567:
      if (!Array.forEach) {
        Array.prototype.forEach = function(fn) {
          for (var i2 = 0; i2 < this.length; i2++)
            fn(this[i2], i2, this);
        };
      }

The expression !Array.forEach does not correctly check for whether the polyfill is necessary.

The function Array.prototype.forEach is 2-arity: the second parameter is an option parameter used as the value for this. https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/forEach#thisarg

// ECMAScript 2009 class definition
function Foo() {
  this.hello = { value: "hello" }
}

Foo.prototype = {
  printHello: function() {
    console.log(this.hello.value)
  }
}

var foo = new Foo();

[foo].forEach(Foo.prototype.printHello, foo)  // prints "hello"

// poisonous polyfill
Array.prototype.forEach = function(fn) {
  for (var i2 = 0; i2 < this.length; i2++)
    fn(this[i2], i2, this);
};

[foo].forEach(Foo.prototype.printHello, foo)  // Uncaught TypeError: this.hello is undefined

Proposed solution: NiiVue should not be distributed with polyfills. The inclusion of polyfills should be done by the main application.

@jennydaman , yes this does indeed look like an odd bug. I believe once we remove the noExternal property from tsup.config.ts this issue will be resolved.
Perhaps an intermediate "quick fix" is to have separate tsup configs. One responsible for building a version that supports our tests (simulating using niivue in an end-user application), and another tsup config for building the library so that it can be imported into other projects without errors like this. It also reduces the dist/index.js output file from 4.67 MB to 965 KB.


show analysis flavor

closes #1711
please review and merge #1709 first
Checklist

[x] No CHANGELOG update needed

[x] No new tests needed

[x] No documentation update needed

mistakenly opened against master and GH is confused.


Bugfix: Fix crash when updating post with same clientPostId

Problem Description
The would crash when there were two posts with the same clientPostId in different conversations (which is allowed), and one received an update for post1 while being in the metisContext of post2. This happened due to a small bug in the implementation.
This closes #241
Changes

Fixed bug
Added test

Steps for testing
Follow steps described in issue and see that the crash no longer happens:

Steps to reproduce the behavior:

Login as test_user_1 on TS1
Interactive Learning WS24/25 course
Go to channel #random (I think this is required to load the message in this chat)
Go back to Conversation Overview
Open DM with test_user_20
On the web app, as test_user_20

Go to same course and #random
Scroll up to post "testmessage" from Test User 16 Artemis with timestamp 2024-11-03
Show replies
Mark the second reply as resolving (or not resolving)

Android app crashes

I think the changes in MetisStorageServiceImpl were introduced in https://github.com/ls1intum/artemis-android/pull/124. Did you check if the live insertion still works?

Yep, just checked locally that the live insertion still works. The bugfix for this PR is actually just the change in line 504. The other three changes in the MetisStorageServiceImpl file were just refactoring, but the logic should be the same. Please correct me if I overlooked something 😅

Okay sounds good :)
Just wanted to make sure as I recalled changing something there a while ago. I also checked and there seems to be no issue with the live insertion, so I think it's fine 😁


(doc) Add new value accepted by -proc: option

Without explicit -proc, javac complains about its future:
[INFO] Compiling 5 source files with javac [debug release 17] to target/test-classes
[INFO] Annotation processing is enabled because one or more processors were found
  on the class path. A future release of javac may disable annotation processing
  unless at least one processor is specified by name (-processor), or a search
  path is specified (--processor-path, --processor-module-path), or annotation
  processing is enabled explicitly (-proc:only, -proc:full).
  Use -Xlint:-options to suppress this message.
  Use -proc:none to disable annotation processing.

Current parameter's javadoc suggests that only only and none are allowed. This parameter however is not validated by m-compiler-p. This is also not validated by plexus-compiler.

[x] I hereby declare this contribution to be licenced under the Apache License Version 2.0, January 2004

Duplicate of

#200


feat: added ukrainian vocab

Added ukrainian vocab to allow use handwritten UA datasets

@holyCowMp3 entry in docs missing see: https://github.com/mindee/doctr/pull/1687/files
:)

 Do we need to add the generic cyrrilic letters as well?

Yes please :)


p_screen param from get_screen_* funcs now default to the current screen

With this PR, and a multi-monitor setup, the get_screen_* funcs get (by default) the position/size/dpi from the current screen, instead of getting (by default) the position/size/dpi from the first monitor.

Let's merge for testing, though it might introduce some bugs (or make existing bugs visible), let's see :)


Support JSON Schema

Just tossing this idea out there. Saw this article today and also had to use jsoncompare.com.
I haven't put much additional thought into the idea but figured it's worth a discussion.

I think that such a feature needs to be done behind another app, not as a part of JSONCompare.


Packages in /vendor not autocompleting

After using dep init I don't get autocomplete results for packages inside vendor directory. The program still builds and runs fine and is using the code in vendor as I would expect. If I rename vendor to vendored then the autocomplete works fine.
Running go version go1.10.4 darwin/amd64

Thank you for the report. However, I don't have experience with dep, so please bear with me. Can you clarify what you mean by "I don't get autocomplete results for packages inside vendor directory."?
For example, I'm imagining a layout like:
a.go    // import "b"
vendor/b/b.go

Are you saying that you don't get autocompletions for b.* while editing a.go? Or do you mean you don't get completions at all while editing vendor/b/b.go? Or something else entirely?
Perhaps a standalone example would be helpful.

I had a similar problem and what worked for me is go get ./vendor/.... After running it I've got packages in $GOPATH/pkg/myarch/mypkg/vendor/... and completion started working.

@trinitum that should read go install ./vendor/...

@trinitum @myitcv I tried those but they didn't seem to work for me

that should read go install ./vendor/...

This works. I cannot guarantee, but I think the issue started when I moved to go 1.11.

the go install ./vendor/... works on me, thanks @trinitum

go install ./vendor/...
Is this the only way to solve this?
I think gocode should have some "build-in" support for vendor folder dependencies. I am using glide, which will put all deps into vendor folder. Gocode will not index any file from the vendor folder.  What about provide a parameter allow me add additional package path?

Hi folks. I found this bug trying to find the solution to this issue.
go install ./vendor/... approach worked for me too.

I don't think we will be working on adding improvements to handle vendor directories. If the go install ./vendor/... approach works for you, then I would suggest that as the fix. If anyone would like to create a PR for this, I would be happy to take a look.

I agree with @seagle0128, and the go install solution didn't work for me either.

https://github.com/mdempsky/gocode/commit/a07fefd98fdcd9d2c16aa3f61d8e89eda396bf99 should fix this bug. Please let me know if it works for you.

Thank you @stamblerre, it does indeed fix the issue for me!


The order of the search results is wrong

I set my ldap server to return search results as alpha-ascend.
But the client search results is not ordered, could you fix it?

You will need to provide a more detailed description of the problem.

I use openldap as ldap server.
If i use this command
ldapsearch -b "ou=staff,dc=example,dc=com" -S "uid"

the results will be sorted by the attribute "uid" as alpha-ascend.
But when I use node-ldapjs, I the search can't do this.
Is there any way?

In your example, openldap is sorting the results client-side.  You could accomplish the same thing by collecting search results and sorting them after the fact.  Alternatively, the control to request server-side-sorting might also be useful, provided your server supports it.

I got it, I will sort it myself.
Thanks a lot!

@yockliu Did you get this solved? If yes, how?

⚠ This issue has been locked due to age. If you have encountered a recent
problem that seems to be covered by this issue, please open a new issue.
Please include a minimal reproducible example
when opening a new issue.


[Backport] Deleted CAPR machines reappear after some time if deleted via node via Cluster Explorer

Backport for https://github.com/rancher/rancher/issues/43680

Closing this backport as the timeline for implementing this is unclear and it may affect whether it will be backported. It can be reopened as needed.


PMLTQ integration with nice icon (see kontext)

in case we provide links to pmltq, icons should be the same as in kontext

duplicate of #359


Change flags to be Windows friendlier

The dotted flags we currently use (-collectors.enabled etc) don't play nice with how Powershell tokenizes stuff, so users need to quote the flags ("-collectors.enabled"). (See also #91)
Since starting the exporter from Powershell is a pretty standard use-case, platform coherence and compatibility seems more important than imitating other (primarily Linux-focused) parts of the ecosystem.
One stumbling block here is that the logging library we use (github.com/prometheus/common/log) defines its own flags as part of initialization. So just changing our flags would lead to a mix, which would be worse.
I'm not aware of any way to change the flags already set by another package, but maybe it is possible? Another possibility would be to have a patch on the log library, but I'm not too keen on diverging there.

I have not tired, but maybe we can just overwrite flag.CommandLine, as set here:
https://github.com/prometheus/common/blob/master/log/log.go#L72
documented here: https://golang.org/pkg/flag/#pkg-variables
 CommandLine is the default set of command-line flags, parsed from os.Args.

Otherwise I also think it's better to not do changes in prometheus.
If we cannot solve this, we should open a bug on prometheus/common about our use case.
I also noted their logger had notes about syslogging not working on windows, something that would be beneficial if we could get wired up, too.

Just read this on the Prometheus blog for the 2.0 series:

First, we moved to a new flag library, which uses the more common double-dash -- prefix for flags instead of the single dash Prometheus used so far.

So, this seems we can just move along with the rest then :)

I've been converting a few of the exporters in the Prometheus org to use Kingpin, so I'll do it here as well. With the double dashes, Powershell does not have the same parsing behaviour, so we'll be clear of the problems in #91 as well.
2.0 seems a bit aggressive, though, maybe 1.0? :)

Hehe, you are right. I was thinking 2.0 as in "prometheus 2.0", didn't reflect of our version numbering which would made more sense.
This is great news!

By the way, I haven't looked at if we need to do updates to be compatible with prometheus 2.0 (as in the exporter working with it), or if it is just api related internal changes.
I was thinking we should bump versioning to maybe 1.0 (or 2.0 to cause less confusion for end users?) when we are updated for prometheus 2.0

The exposition format is identical afaik, so we do not need to do anything there. I also do not think any other exporters plan any versioning bumps to indicate v2 compatibility.
I do think that we can consider ourselves stable enough for a 1.0 release pretty soon, though. After this flag change (which is a breaking change), I'm not aware of any other large changes we need to do. Agree?

The flags are breaking and warrants a major bump i think, yes. Okay, lets aim for a 1.0. Fixing the label