[Bug]: Can't set border radius using an image

What happened?
It is impossible with the current state of the lenra components to use the border radius with an image. The container will properly use the radius but the image will just overflow in the corners.
A solution could be to use the Container.decoration.image property to assign an image to a container, then the border radius will work properly and we will still be able to customize the image.
Another solution would be to implement the ClipRRect widget that properly clips its child such as an image. This brings a new component on Lenra that is not straightforward to find but it could be used for other things than images (even though I can't think of any for the moment).

After some research and testing, it seems quite hard with the current way we handle the widgets on lenra_ui_runner to add a LenraImage into the Container.decoration.image property. Because a BoxDecoration is parsed by the props_parser, it is impossible to set the image property as a Child widget. It will be parsed as a property which required to redefine the whole LenraImage parsing file into the props_parser. Then, the image that is expected by the BoxDecoration.image is not a LenraImage nor a Image.network, it requires a DecorationImage with a NetworkImage as a child (note the difference between Image.network and NetworkImage, these are not the same widgets).
TLDR: We would need to create a specific DecorationImage + NetworkImage parsing which would differ from the LenraImage definition, which may confuse users.
The ClipRRect seems to be a good solution compared to the previous one but according to developers, the ClipRRect is needs much more computing power so this might be bad for apps that use a lot of image clipping. It also adds a new component to Lenra which could be avoided.
We need to discuss this issue with the team. @lenra-io/devs

This problem is linked to this issue: https://github.com/lenra-io/lenra_cli/issues/270


Upgrade GCP BOM to 26.32.0

Roll forward #30324
Improved the bomupgrader script to consider the dependencies with "// Keep version consistent with the version in ...", specifically several google-api dependencies.
Please add a meaningful description for your change here

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.

CC: @damccorm @dhruvdua  will wait until postcommit run

datastore-proto-client 2.18 removed databaseId  causing compile failure. Fixing...


Add get_text_separator parameter to BSHTMLLoader

By default get_text doesn't separate content of different HTML tag.
Adding option for specifying separator helps with document splitting.

@hwchase17 please approve one more time, I fixed linting issues and add test


improve structure of application

Hi!, really nice work you have here. I suggest you work to improve the structure of the application, you can try using classes and helper methods to get things more organized, that'll reduce the number of files you need, and keep everything organized and easy to understand.
Also, it seems like the requirements.txt file has some unneeded dependencies in it, whoever made it must have unknowingly added them to it. For example the requirements file specifies Django as a dependency and i don't see any reference to django in your code base. You should look into that as well.

I would be willing to work on all these issues mentioned if you can assign it to me


Feature/track dbt environment

creates an invocation_env table with an environment column. This value is set by the DBT_INVOCATION_ENV environment variable

TODO: Change the event schema branch from feature/track_dbt_environment to master before merging? Still unclear on a reasonable way of doing this


Alternatives to xstream?

XStream seems to be the one thing that forces a build to use the ScalaJSBundlerPlugin (this caught me when initially trying the library).
Is there a specific reason that XStream was chosen over something like Monix?

Yeah, I get asked this a lot since XStream.js is not native to Scala. My two primary criteria for a streaming solution are:

Conceptually simple. XStream streams are synchronous, "hot" / multicast (executed only once per event, not once per event per listener). There are no schedulers, execution contexts, backpressure strategies / etc. It is very beginner-friendly.

Small download size. XStream is less than 40KB in production. For comparison, as far as I can tell Monix is around 200KB, which is significantly more. Not just because of the download latency, but because all that code needs to be unzipped, parsed and loaded into memory. Especially on mobile devices that's a big problem. Monix is modular, so it might be possible to reduce download size by only requiring the monix-reactive package, but I didn't have the time to try that.

It helps that XStream was built specifically for Cycle.js, a use case that is very similar to Laminar. Here its author who also has significant experience with RxJS explains why he decided to go that way:
https://staltz.com/why-we-built-xstream.html
https://staltz.com/why-we-actually-built-xstream.html
https://staltz.com/cold-and-hot-callbacks.html

Because XStream is so simple and lightweight, if we ever come up with a way to use different streaming solutions in Laminar (relevant discussion), it will probably be a good lowest common denominator due to lower overhead.

One more thing – in the next version of Laminar I will try to make it impossible to forget to unsubscribe from a stream. So the stream.addListener(listener) method will gain another implicit parameter, something like subscriptionLifecycleContext which could for example be a Laminar element. Then the subscription will be cancelled when said element gets unmounted.
With XStream, I can do this reliably because I can modify the XStream.scala interface to suit my needs. In Monix, from my understanding the only thing we could do is add an optional syntax for the same (example) which still leaves the original .subscribe/.addListener method exposed for abuse.

On the other hand, what I don't like about XStream:

It looks weird to Scala people, that could hurt adoption of Laminar
Writing a typed interface to it was annoying. I would prefer a native Scala solution

I'm not 100% locked to XStream, but it seems like the most compelling solution to me at the moment. I am especially on the lookout for a single solution that will have both streaming and state management functionality like Felix described here: https://github.com/OutWatch/outwatch/issues/96#issuecomment-346654224

btw is there an issue with requiring ScalaJSBundlerPlugin? I was under the impression that any real world Scala.js project will end up using it to get some JS dependency or other... For building SPAs I figured that would be mostly inevitable.

It feels like the plugin alters the build in a non-transparent way (requirement of installing yarn, changing artifact paths etc). Maybe it's just me; I'm still quite unfamiliar with Scala/JS but is hoping to use it for a mobile first web-app soon. It's not a deal breaker but it'd feel nicer if the toolchain was 100% Scala.
Thanks for the links, very interesting read! So streams being hot is desired in order to avoid the retriggering of side-effects when connecting observers to some stream that is side effecting. Is that a correct interpretation? Does that relate somehow to push- vs pull-basedness of streams? Monix should be push by default if I'm not mistaken.
Not having to deal with an execution context is nice, and not having to unsubscribe listeners is nice too! It does feels a bit strange to add this to the façade layer since it effectively alters the perceivable behaviour of the underlying library, but at the same time it feels practical.
Another approach would be fully abstract away the underlying stream library and require only those abstractions in the binding API. This decoupling would also make it possible to try different libraries without touching the surface area. Maybe something like https://github.com/lihaoyi/scala.rx would work. Seeing as its only dependency is the Scala library I (perhaps naïvely) imagine it would be a very lightweight solution in terms of added kB.

So streams being hot is desired in order to avoid the retriggering of side-effects when connecting observers to some stream that is side effecting. Is that a correct interpretation?

Not exactly. Each listener would still be triggered once. A stream being hot means that non-side-effecting operators are also executed only once per event. So if you have myStream = otherStream.map(foo), and otherStream emits an event: if myStream is a cold stream, foo will be executed as many times as myStream has listeners, whereas if myStream was hot it would execute only once, and only if myStream has any listeners.
The benefit of hot streams is that it's more forgiving. If you have a side effect (such as local state mutation) in your .map somewhere it will still work like you'd expect, even though your expectation is technically incorrect for the FRP paradigm. FS2 library for example is on the opposite side of the spectrum. I haven't looked too deeply, but I think instead of using hot streams it lets you achieve safety by encoding side effects of your streams in types... or something like that.
Pretty sure XStream is also a push based system. IIRC a pull based system is where your observers actively query their dependencies for current state instead of listening to incoming changes, a very different system.

It does feels a bit strange to add this to the façade layer since it effectively alters the perceivable behaviour of the underlying library, but at the same time it feels practical.

This is exactly how I feel as well. I like to think that perhaps xstream.js might have had this feature itself, if Javascript had implicits.
I am also considering a separate wrapper layer like you said, but realistically it will not be able to offer interop between underlying libraries as those are too different once you get past the simple .map/.filter mechanics.

Regarding Scala.rx specifically, I looked into it again yesterday, and realized that it uses Scala's WeakReference to prevent memory leaks. Meanwhile, I think Scala.js does not really support weak references – the WeakReference class is stubbed to provide a strong reference due to lack of native WeakReference support in JS, as far as I can tell. So it's possible that Scala.rx requires even more careful memory management in Scala.js than its docs suggest (actually, cc @fdietze – this could be relevant to your Duality fork, or maybe you know something I don't).
Another issue is that Scala.rx does not support empty vars / observables, so you can't really do streams with it, you can only represent time-varying values aka state. While it is definitely possible to modify Laminar to work like that, typical user code would look quite a bit different. Not a deal breaker, but something to consider carefully.

After looking at Scala.rx and reactive-core, I think Laminar would work best if we had a library that covered both state management and event propagation, but would also have more manual memory management (meaning that each listener/observer needs an implicit LifecycleContext, which Laminar would provide). As opposed to relying on WeakReference-s. That could potentially solve both FRP glitches and automatic memory management.
However, as far as I can tell, there is unfortunately no such library. I am building Laminar in order to build things with it, so as much as I'd love to implement such a library myself, I don't think I'll have the time anytime soon. It might be possible to fork either scala.rx or reactive-core to achieve this, but that's still a lot of time.

I'm not 100% locked to XStream, but it seems like the most compelling solution to me at the moment. I am especially on the lookout for a single solution that will have both streaming and state management functionality like Felix described here: https://github.com/OutWatch/outwatch/issues/96#issuecomment-346654224

Sadly, I doubt that there will exist a library which does event-propagation and state-management well any time soon. Thats why we're trying to implement type-classes for both (https://github.com/fdietze/outwatch/blob/typeclass/nomad/src/main/scala/nomad/core.scala) and let the user decide if they want to use either

Two separate libraries (two apis + more payload)
Only Event-propagation / streaming like rxjs, xstream, monix (frp glitches if used for state-management / rendering UI https://github.com/monix/monix/issues/467, https://github.com/OutWatch/outwatch/issues/96#issuecomment-346957347. Always needs to be started with a default value, else UI is in an undefined state: https://github.com/OutWatch/outwatch/issues/137)
Only State-Managemnt like scala.rx (few operators, dataflow-graph-overhead - which is probably neglible in web-applications). To be fair, scala.rx was not only developed for state-management and brings some operators for handling events. It's pretty usable for event-management but lacks lots of operators that rxjs/monix provide. I'm using it in my projects for over a year now. I think these kinds of libraries are the most promising ones, if you one wants to use only one library.

Regarding Scala.rx specifically, I looked into it again yesterday, and realized that it uses Scala's WeakReference to prevent memory leaks. Meanwhile, I think Scala.js does not really support weak references – the WeakReference class is stubbed to provide a strong reference due to lack of native WeakReference support in JS, as far as I can tell. So it's possible that Scala.rx requires even more careful memory management in Scala.js than its docs suggest (actually, cc @fdietze – this could be relevant to your Duality fork, or maybe you know something I don't).

I'm not aware of anything like this. Could you please point me to the code?

One more thing – in the next version of Laminar I will try to make it impossible to forget to unsubscribe from a stream. So the stream.addListener(listener) method will gain another implicit parameter, something like subscriptionLifecycleContext which could for example be a Laminar element. Then the subscription will be cancelled when said element gets unmounted.

Just to mention, the same is implemented in outwatch (https://github.com/OutWatch/outwatch/blob/4a2f0469a043d8ea65ffd2a7b125e16d00f5c42f/src/main/scala/outwatch/dom/helpers/Snabbdom.scala#L111), but this covers only one part of the possible leaks (ideas: https://github.com/OutWatch/outwatch/issues/121).

However, as far as I can tell, there is unfortunately no such library. I am building Laminar in order to build things with it, so as much as I'd love to implement such a library myself, I don't think I'll have the time anytime soon. It might be possible to fork either scala.rx or reactive-core to achieve this, but that's still a lot of time.

scala.rx has a small and simple code-base and was easy to fork for me (https://github.com/fdietze/duality). I'm very open to discuss the direction of this project, maybe we can achieve something useful together. 😉

Just to mention, the same is implemented in outwatch

Yep, to that extent it is also already implemented in Laminar, even managed subscriptions (ReactiveElement.subscribe), but the problem is that managed subscriptions are opt-in, the user can still trivially bypass it because the underlying streaming library does not require a lifecycle context for creating subscriptions. I want to make it impossible to create a subscription without specifying when it should be destroyed at the same time.

Regarding weakrefs:
https://github.com/scala-js/scala-js/blob/master/javalanglib/src/main/scala/java/lang/ref/WeakReference.scala
https://github.com/scala-js/scala-js/pull/170 <-- here the description essentially says that weak refs are not weak.
I think WeakReference can potentially be implemented using Javascript's WeakMap such that you would be putting weakrefs into keys.

I am still trying to figure out how Scala.rx handles propagations to avoid glitches or excessive recomputing.
I think it should be possible to define a very simple propagation method where the changes in a Var propagate to child Rx-s until they meet an Rx that depends on multiple parents. Then when there is nothing left to do the propagation "continues" by computing those multi-parent Rx-s and continues on to their children using the same logic.
Lastly, when the change was propagated through the whole graph, only then we fire any triggers on the graph, in the order in which the propagation encountered them.
I think this could be a very predictable propagation technique assuming that it actually works on complicated graphs (even including partially recursive ones, I guess). I do expect unexpected behaviour in certain edge cases e.g. if you specify a trigger that updates the same graph that you've just finished propagating. Not sure if those issues would be solvable. Maybe such weirdly recursive code should just not exist.

Here is the implementation of the Algorithm in scala.rx: https://github.com/lihaoyi/scala.rx/blob/master/scalarx/shared/src/main/scala/rx/Core.scala#L119

Regarding WeakRefs in scala.rx:
I digged a bit deeper and found this: https://github.com/lihaoyi/scala.rx/issues/21#issuecomment-174139432

Hrm. Well, then it means you need to remember to kill observers manually... I guess?
I did read Scala.rx propagation algorithm but its plain-English approximation is eluding me. It seems to be some kind of breadth-first search that doesn't really help solve redundant updates of Rx-s in principle, it only removes redundancies when firing triggers. I could be wrong, it's hard for me to read.

Despite my best judgement I went and tried my hand at making a very simple state propagation lib: https://github.com/raquo/laminar/pull/8 As if I didn't dig enough rabbit holes for myself... I guess I'll be adding more tests to it to see how it handles edge cases, and if that works out I might implement memory management for it and integrate it into Laminar.

Hrm. Well, then it means you need to remember to kill observers manually... I guess?

Can you please try to produce such a leak in scala.rx? I'm interested. As far as I understood, this should not be possible.
I'll take a look into the scala.rx propagation algorithm soon.
What was your motivation for a new project instead of building on scala.rx? Understanding the principles? Because it could be possible that you end up building a clone. In my opinion scala.rx got a lot of design decisions right. The readme is worth a read. You can probably reuse some tests.
The motivation for my fork were bidirectional state operators and to drastically simplify the code base (also for understanding what's happening).

Can you please try to produce such a leak in scala.rx? I'm interested. As far as I understood, this should not be possible.

Sorry, I only have time to armchair this :(, stretching myself very thin as it is. Having looked at Scala.rx code, I see that its Dynamic Rx-s keep track of both upstream, downstream, and observers. On the surface it seems like nothing in that graph will be garbage collected unless each and every of those Scala.rx objects has no outside references to it (which might as well be never).
But, I could be wrong. It's hard to understand what exactly Scala.rx does with its upstream/downstream properties. It... seems to clear and re-calculate them on every propagation or something like that. Maybe that dark magic is what effectively substitutes for weak refs, but I honestly can't tell at this point. It doesn't seem like it should be possible.

What was your motivation for a new project instead of building on scala.rx? Understanding the principles?

Yes, mostly that, and random curiosity. The approach I'm trying is different from Scala.rx though, I guess it's closest to the "static dataflow graph" Li Haoyi mentioned in Scala.rx readme (which I've read many times). He dismisses that approach as too constrained, but I think having constraints on how you define state transitions could actually be beneficial, it might force you to separate state vs streams more cleanly in your code.
Apart from that, I just plain don't understand how Scala.rx propagation and memory management works, and there is no explanation for that in the docs other than a couple very simple examples and a mention of "best effort" (but no guarantee) to avoid redundant computation. And the tests don't seem to exercise memory management other than what's mentioned in the readme, which is not my concern.

I'm not sure how I feel about bidirectional operators. They're definitely useful but they break unidirectional dataflow, which is one of those constraints that I think is very useful. In react.js for example you pass down Signals (props in React terms) to child components, but child components can not write to parent's Signals (parent's state in React terms) directly, they can only expose Streams (fire callbacks in React terms). That works very nicely, even if some boilerplate is required to connect cyclical Signal (state) dependencies via streams.
Bidirectional operators feel more like Angular's two-way data binding (with the addition of project functions) which to me has proven less maintainable than react's way.

The next version of Laminar will use Airstream instead of XStream, see #8. As that's settled for now I'll close this issue. We can still have discussions about streaming libraries or Airstream's shortcomings in new issues.


create mini web page to show registration is working correctly

Replicate this page for verification on the endpoint to be served.

No longer required as this should be part of the new dev server


Tables won't create on Multisite (wpms)

WordPress cannot create table for WPMS when trying to create a network.
Using Docker for OSX, version
$ git log -1
commit c1aa147615a3cf0f2f02fa73e72abf44eace9599 (HEAD -> master, origin/master, origin/HEAD)

docker-compose.override.yml:
version: '3'
services:
  phpfpm:
    extra_hosts:
      - "multisite.local:<IP_ADDRESS>"

Site runs fine in standard mode. Once activating network mode (subdomains) and adding defines to wp-config.php, the database goes away.
Running database repair outputs:
wp_1_posts: Table 'wordpress.wp_1_posts' doesn't exist
wp_1_comments: Table 'wordpress.wp_1_comments' doesn't exist
wp_1_links: Table 'wordpress.wp_1_links' doesn't exist
wp_1_options: Table 'wordpress.wp_1_options' doesn't exist
wp_1_postmeta: Table 'wordpress.wp_1_postmeta' doesn't exist
wp_1_terms: Table 'wordpress.wp_1_terms' doesn't exist
wp_1_term_taxonomy: Table 'wordpress.wp_1_term_taxonomy' doesn't exist
wp_1_term_relationships: Table 'wordpress.wp_1_term_relationships' doesn't exist
wp_1_termmeta: Table 'wordpress.wp_1_termmeta' doesn't exist
wp_1_commentmeta: Table 'wordpress.wp_1_commentmeta' doesn't exist

Looks like there are no permissions for WP to write to the database. Nothing useful in debug.log.
Can anyone duplicate this? Wondering if it's a local-to-me issue or bug.

If you change your DB user to root as opposed to wordpress, does that help?

@indietravel are you still experiencing this issue?

Sorry for the tardy response; just carved out time to test this morning. Confirming that this is no longer an issue for me (latest versions of everything).


Handle grayscale images as training data.

This PR allows to create a dataset with grayscale images (1 channel).

Add a color parameter in the tool im2rec, to choose color mode (color, or grayscale)
Decode rec dataset without forcing color mode (so, keep the color mode of the encoded data)
Substract mean on 1 channel only for grayscale image
#805

LGTM, @winstywang can you do a review on this and merge?

I'm OK with other parts

@Nzeuwik Thank for the contribution! can you make the enhancement @winstywang mentioned? This would be a great addition to the data loader. please also add your name to https://github.com/dmlc/mxnet/blob/master/CONTRIBUTORS.md

OK, merge this in for now. Let us make the non-greyscale on another PR

Hi, sorry for the late answer. I'm going to work on the enhancement @winstywang mentioned, and will do another PR for it.
A separate PR seems better, as it also implies some changes in the way the images are read/processed in the tool im2rec to handle rgba images correctly.


FAQ Page needs reworking

The current state of the FAQ page is a temporary fix. Until the FAQ is approved by the TC I cannot add direct questions onto the website. Once this takes place, the most important questions should be listed on the website with a link to the complete FAQ hosted in Google Docs.

FAQ has been reworked. It may still require a bit of updating, but PR #86 fixes this issue.

The new FAQ syntax worked locally, but not on the site, so the FAQ needs to be reworked again.

You might need to add a markdown processor to your Jekyll config. See https://docs.github.com/en/pages/setting-up-a-github-pages-site-with-jekyll/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll


Current version in master not loading

When i checkout the current master and add it to my project i get this error:
Error: cannot import name ImageSpecField

When i checkout the 1.1 branch imagekit does load as expected.

In 1.X, the class was imagekit.models.ImageSpec, but in the 2.0 alpha, we moved it to imagekit.models.fields.ImageSpecField.  We're still working on 2.0 so it's in the development branch but master is still 1.X, so if you're referencing the 2.0 documentation but using the 1.X code, things won't quite line up.

Where would i be able to find the 1.1 docs? It's not enough to use the different ImageSpec as methods like Fill have changed as well it seems.
I was using the 2.0 branch but currently that gives me this error:
'ImageSpecFieldFile' object has no attribute 'field'

So that's not working either

Ah, I must've introduced that issue yesterday. Could you open a new issue for that?
@bryanveloso It looks like readthedocs is building from develop instead of master. Could you fix that?

@tijs In the meantime, the old README might help. Sorry about this.

No problem mate, i switched to 1.1 successfully with some code digging. I'll open that issue and then let you work on 2.0 in peace and switch when you ready ;)


Big route53 accounts may cause dnsprovider to hit rate limits

 Issue by justinsb
Tuesday Jan 10, 2017 at 15:00 GMT
Originally opened as https://github.com/kubernetes/kubernetes/issues/39674

The route53 dnsprovider doesn't implement filtering.  On Route53, there is a 5 request per second rate limit (per AWS account): http://docs.aws.amazon.com/Route53/latest/DeveloperGuide/DNSLimitations.html
With pagination, it is very likely that we will issue more than 5 requests per second just listing resource records for a big zone.
We need to implement filtering.

 Comment by chrislovecnm
Wednesday Jan 11, 2017 at 19:05 GMT

@justinsb can you provide more details on the code base this is coming from?

 Comment by chrislovecnm
Wednesday Jan 11, 2017 at 19:07 GMT

cc: @kubernetes/sig-aws-misc

 Comment by justinsb
Wednesday Jan 11, 2017 at 19:44 GMT

@chrislovecnm  https://github.com/kubernetes/kubernetes/tree/master/federation/pkg/dnsprovider/providers/aws/route53

 Comment by chrislovecnm
Thursday Feb 16, 2017 at 20:16 GMT

FYI
Top three API calls that we are getting.  I am uncertain if we are using the PRs on this ticket.

ListHostedZonesByName
ChangeResourceRecordSet
ListResourceRecordSets

 Comment by quinton-hoole
Friday Sep 08, 2017 at 00:55 GMT

I think we need to fix this before GA of federation. Prioritizing accordingly.

 Comment by fejta-bot
Monday Jan 08, 2018 at 17:25 GMT

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Prevent issues from auto-closing with an /lifecycle frozen comment.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle stale

cc @justinsb


initial commit of agency regions as GeoJSON

Adding ageny regions from http://nepanode.anl.gov

Since I can't preview these changes, and http://nepanode.anl.gov isn't loading for me, mind giving a quick description of what this is?

@konlone NEPAnode is now a dead project - but these are all GeoJSON exports from official agency sources


Add a Gitter chat badge to README.md

pygeo/pycmbs now has a Chat Room on Gitter
@bulli92 has just created a chat room. You can visit it here: https://gitter.im/pygeo/pycmbs.
This pull-request adds this badge to your README.md:

If my aim is a little off, please let me know.
Happy chatting.
PS: Click here if you would prefer not to receive automatic pull-requests from Gitter in future.

Coverage remained the same at 60.22% when pulling 2a811819635bc50eb541e70094969021d42b3257 on gitter-badger:gitter-badge into c802cf1fc8737c98e83c0e942451720fce03b860 on pygeo:master.

not needed


[Habit info] 'Progress' section on 'Habit info' page does not correspond to the mock up

Environment: Windows 10 Home v. 22H2, Chrome 128.0.6613.115 .
Reproducible: always.
Build found: 25.09.2024
Preconditions

User is signed in
User has at least one habit
'My Habits' tab is opened

Steps to reproduce

Click on the pencil icon on any habit card in progress
Scroll down to the 'Progress' section

Actual result
The calendar displays days as square-shaped icons. The progress bar not on the same horizontal level with the calendar.

Expected result
According to the mockup, the calendar should display days as circlular icons.  The progress bar needs to be aligned on the same horizontal level with the calendar.
Mockup: https://www.figma.com/proto/092AhCGadc1Hq8nAysxmYB/ITA-Greencity-УБС?node-id=37844-154515&node-type=frame&t=Cdu9uBULw8qe91h7-1&scaling=min-zoom&content-scaling=fixed&page-id=12201%3A8
User story and test case links

It was decided to unify the date icons on the habit page according to 'my space' on this mockup: https://www.figma.com/design/092AhCGadc1Hq8nAysxmYB/ITA-Greencity-УБС?node-id=49255-18557&node-type=frame&t=iLzGsL9bodTwfeUg-0


PIM Program

So i want to make a program that take the armor of the player and put it in a chest
This is my code but it does not work
could some one make me a code that work!
pim = peripheral.wrap("right")
while true do
pim.pushItemIntoSlot("NORTH",4,1,1)
end
but when i reboot i have a error code and i don't know what to do!

Direwolf did this in a previous season of Forgecraft the pastebin link is http://pastebin.com/KqGYdQrU this takes armour and hotbar and places it in an chest next to the PIM it also does the reverse the video is https://youtu.be/jG5A9J3Gh4A?t=19m45s

What you're saying is pretty much "I did something and now it doesn't work". Give more details, like how you set the computer + PIM up, what exactly your code is and what error you get. Else it's pretty much impossible for others to see what you did wrong.

Here is a picture of my code that i made yesturday!


Version numbers

I cannot install v0.2.10 (and a couple of other versions) using pip because I get the following error
WARNING: Discarding https://files.pythonhosted.org/packages/14/d7/59e58f912339c6f9a74857c22a46214790df41e29196e949f4bdae7045ab/mpi4jax-0.2.10.tar.gz#sha256=1356f3deda93635dacac43babd5f8f42937146ff33506376e5919ae10047edbb (from https://pypi.org/simple/mpi4jax/) (requires-python:>=3.6). Requested mpi4jax from https://files.pythonhosted.org/packages/14/d7/59e58f912339c6f9a74857c22a46214790df41e29196e949f4bdae7045ab/mpi4jax-0.2.10.tar.gz#sha256=1356f3deda93635dacac43babd5f8f42937146ff33506376e5919ae10047edbb has inconsistent version: filename has '0.2.10', but metadata has '0.0.0'

When I try installing it directly from the repo (python3 -m pip install --upgrade git+https://github.com/PhilipVinc/mpi4jax.git@v0.2.10), pip thinks it got version 0.0.0, so it is not accepted by anything that depends on it.

Hi Attila,
What platform are you on and what is the version of your python and pip?
I cannot reproduce locally on Fedora or MacOs, with python 3.8/3.9 and a freshly updated pip (python -m pip install -U pip).
@dionhaefner I think this is related to the automatic generation of the version number... do you have any idea of what is going on?

Related: pip#7179.
Upon inspecting our wheels on Pypi, it turns out that the [egg_info] tag_build field is declared but not populated in setup.cfg...

@attila-i-szabo
pip install git+https://github.com/PhilipVinc/mpi4jax#0.2.10
should work, however.

I'm on Ubuntu 18.04, python3.6, freshly upgraded pip (21.0.1). I don't have access to the pip command directly and I use a venv (institutional rules...). The command you sent does install v0.2.10, but calls it v0.0.0

I'll have a look tomorrow, sounds like the metadata is still not propagated correctly in our wheels, which pip recently started to enforce.

@attila-i-szabo which version of setuptools are you using?

I use the latest setuptools (54.0.0). Turns out the installation works with my original command on python3.8 and the installed library gets the correct version number.

Since neither of us has been able to reproduce this behavior, this is getting a bit tricky to debug. I've tried several old versions of pip and setuptools, on Python 3.6 and recent versions, but everything worked fine.
My suspicion is that you have some path confusion going on where you accidentally used an outdated pip or setuptools. Either way, I have hardened the version detection in #50 which should make this more robust in older setups.
It seems like the issue is resolved for now?

Yes, it's resolved for me with using python3.8. In case that's a useful data point, the default installation had pip 20.3.3 and setuptools 39.0.1 on python3.6.

Let's close this for now, feel free to re-open if you encounter it again with the next release.


Add CS, CSdg and CCZ gates to the CNOTDihedral class

Summary
close #8520
following PR #8583
Details and comments
Add CS, CSdg and CCZ gates to the CNOTDihedral class.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

29 of 32 (90.63%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.02%) to 84.239%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

qiskit/quantum_info/operators/dihedral/dihedral_circuits.py
29
32
90.63%

Totals

Change from base Build<PHONE_NUMBER>:
0.02%

Covered Lines:
57215

Relevant Lines:
67920

💛  - Coveralls

Thank you @nkanazawa1989 and @itoko for your reviews!
I think that this PR is ready to go now. @ikkoham - could you please approve & merge it?


quarterly report

Also, I’m interested in detail such as:

Where do you get your tuning data from?
How much data points do you have? How large and complex are those examples?
At what rate did you see improvements when tuning an existing model?
How did you verify correctness?
Did you measure performance, and if so, what were the results?

@chunhualiao @peihunglin @LChenGit
I just wrote some potential answers for these five questions. If there is any questions, please let me know.
For 1:
Our original Fortran code comes from the Fortran code in codeparrot/github-code: https://huggingface.co/datasets/codeparrot/github-code
For 2:
We have a total of $2529$ data points (data/F2C_dialogue_25K.json), each corresponding to a multi-turn dialogue. The number of dialogue turns ranges from $5$ to $17$. These dialogues document the process of translating and refining the original Fortran code. The final Fortran-C++ code pairs are located in data/readable_format.
For 3:
As the training steps increase, the changes in training loss are shown in the training_log folder.
For 4:
To ensure the accuracy of the dataset, we performed checks on the code within the dataset using Compilation Error Checking, Execution Error Checking, and Paired Output Checking.
Compilation Error Checking
The Fortran and C++ code, with unit test cases inserted, are checked using the g++ and gfortran compilers.
Execution Error Checking
The compilable code is executed to check for any errors at this step.
Paired Output Checking
In this step, we ask GPT-4 to check if the outputs of the Fortran and C++ are the same.
For 5:
We used four metrics to evaluate the model's performance on the Fortran-C++ translation task, including CodeBLEU Score, Compilation Check, Execution Test Evaluation, and Manual Investigation. The results are shown in the overleaf table 1 and table 2.

@chunhualiao @peihunglin @LChenGit
I just wrote some potential answers for these five questions. If there is any questions, please let me know.
For 1:
Our original Fortran code comes from the Fortran code in codeparrot/github-code: https://huggingface.co/datasets/codeparrot/github-code
For 2:
We have a total of 2529 data points (data/F2C_dialogue_25K.json), each corresponding to a multi-turn dialogue. The number of dialogue turns ranges from 5 to 17 . These dialogues document the process of translating and refining the original Fortran code. The final Fortran-C++ code pairs are located in data/readable_format.
For 3:
As the training steps increase, the changes in training loss are shown in the training_log folder.
For 4:
To ensure the accuracy of the dataset, we performed checks on the code within the dataset using Compilation Error Checking, Execution Error Checking, and Paired Output Checking.
Compilation Error Checking
The Fortran and C++ code, with unit test cases inserted, are checked using the g++ and gfortran compilers.
Execution Error Checking
The compilable code is executed to check for any errors at this step.
Paired Output Checking
In this step, we ask GPT-4 to check if the outputs of the Fortran and C++ are the same.
For 5:
We used four metrics to evaluate the model's performance on the Fortran-C++ translation task, including CodeBLEU Score, Compilation Check, Execution Test Evaluation, and Manual Investigation. The results are shown in the overleaf table 1 and table 2.

Hey Team @chunhualiao @peihunglin @LChenGit !  Please let me know if you need other new information or you have questions related to this reply for the presentation on Tuesday.

@bin123apple  Your answer to Q3 is not clear: At what rate did you see improvements when tuning an existing model?
" the changes in training loss are shown in the training_log folder."  Your answer raises more questions than addressing a question.  How many files are in the folder and how many lines each file has? which file and which line should I look at?  What changes are you talking about? How should I extract a rate from the changes of this folder?
The expected answer may be a ratio between the fine-tuned vs. baseline model using some accuracy metrics, such as your Table 1 or Table 2 metrics.  You can compute the ratio in the tables, like what we did in last year's paper.

OKOK, I thought the "rate" means "speed".
Here is the

ratio between the fine-tuned vs. baseline model

For F2C++ Dataset:

Model
CodeBLEU Ratio (w ft/ wo ft)
Compilation Ratio  (w ft/ wo ft)

DeepSeek-Coder 6.7B
$1.5521$
∞

Codellama 13B
$1.7933$
∞

StarCoder 15.5B
$1.7283$
∞

For translated HumanEval:

Model
CodeBLEU Ratio (w ft/ wo ft)
Compilation Ratio (w ft/ wo ft)
Execution Ratio (w ft/ wo ft)

DeepSeek-Coder 6.7B
$3.1104$
∞
∞

Codellama 13B
$0.8013$
∞
∞

StarCoder 15.5B
$3.3087$
∞
∞

$ means us dollar by default. Why do you use $ to include numbers?
Please add the non-infinite ratios into the paper' tables.
On Mon, Aug 12, 2024 at 10:16 PM Bin Lei @.***> wrote:

OKOK, I thought the "rate" means "speed".
Here is the
ratio between the fine-tuned vs. baseline model
For F2C++ Dataset:
Model CodeBLEU Ratio (w ft/ wo ft) Compilation Ratio (w ft/ wo ft)
DeepSeek-Coder 6.7B $1.5521$ ∞
Codellama 13B $1.7933$ ∞
StarCoder 15.5B $1.7283$ ∞
For translated HumanEval:
Model CodeBLEU Ratio (w ft/ wo ft) Compilation Ratio (w ft/ wo ft) Execution
Ratio (w ft/ wo ft)
DeepSeek-Coder 6.7B $3.1104$ ∞ ∞
Codellama 13B $0.8013$ ∞ ∞
StarCoder 15.5B $3.3087$ ∞ ∞
—
Reply to this email directly, view it on GitHub
https://github.com/bin123apple/Fortran2Cpp/issues/49#issuecomment-2285356233,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAMNIRSWTLA52IVCX4TBLOTZRGJEFAVCNFSM6AAAAABMI7JQPOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOBVGM2TMMRTGM
.
You are receiving this because you were mentioned.Message ID:
@.***>

Finish quarterly report.


Please switch to new Wuffs decoder in Skia

@nigeltao tells me it's ready for us to try.
This is something @abarth has asked us for as well.

@chinmaygarde or @jason-simmons would be the person to make the actual switch.  (FYI @cbracken)

Disabled in flutter/engine#7785 to fix flutter/flutter#27718.

(Turns out Skia's implementation is not ready yet; we aren't sure exactly when this will be done.)

FYI: I've been updating Skia bug: Replace GIF codec code with Wuffs version to include more specific bugs that are currently blocking it. Sorry for the churn.

Disabled in flutter/engine#7785 to fix #27718.

FWIW, #27718 looks like it's about PNG decoding, but Wuffs' enabled-ness shouldn't affect PNG decoding, only GIF decoding.
Hey, if the bisect fingers a Wuffs-related change, then it's hard to argue with that. It's just puzzling.

My understanding is that with https://github.com/flutter/engine/pull/7991 customer: solaris is unblocked for now.  customer: fuchsia still requires this eventually.

@eseidelGoogle, customer:solaris is indeed unblocked (label can be removed). Thanks!

I think it'd be safe to try again. Here's the current status:

we are uploading decoding results to gold.skia.org, so we'll know if the output changes
likewise, we're uploading decoding times to perf.skia.org, so we'll know if there's a perf regression
the windows build errors have been resolved
we haven't seen any fuzzing bugs in a little while (last one fixed Feb 20)
SkWuffsCodec handles color correction now
there are still a couple of bugs blocking the main one, but I think they're either not a big deal or shouldn't affect flutter (last I checked, flutter was calling SkCodec::getPixels, which is unaffected by this bug)

@LeonScroggins wonderful!
Since you mention you are tracking performance numbers, do you happen to have performance numbers of this codec relative to the previous one?

Perf is set up to alert us to regressions for running the same combination of parameters. There's probably a way to compare across configs, but I'm not sure how to do that. I don't have performance numbers handy, but it has generally been faster.

@jason-simmons will take another look at this after our next stable build is out the door.


Update terraform-aws-blueprints to v4.12.1

Which issue is resolved by this Pull Request:
This fixes the issue that create_namespace does not work.
Description of your changes:
Updated dependency.
Testing:

[ ] Unit tests pass
[x] e2e tests pass

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@surajkota  The  issue you mentioned was exactly the motivation for this fix.


32-bit random data corruption

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

$ go version
go version go1.15.6 linux/arm

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="arm"
GOBIN=""
GOCACHE="/home/pi-star/.cache/go-build"
GOENV="/home/pi-star/.config/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="arm"
GOHOSTOS="linux"
GOINSECURE=""
GOMODCACHE="/home/pi-star/go/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/home/pi-star/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/local/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/local/go/pkg/tool/linux_arm"
GCCGO="gccgo"
GOARM="6"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/home/pi-star/go/src/github.com/golang/32bit-bug/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 -marm -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build227798987=/tmp/go-build -gno-record-gcc-switches"

What did you do?

While running a 32-bit golang executable random data corruption may occur. Here is an example Kubernetes issue which is able to reproduce the problem with 32-bit arm and 386:
https://github.com/kubernetes/kubernetes/issues/97685
The unit test is compiled and attached as a standalone example here:
32bit-bug.tar.gz
Test code, commands, armv6 binaries, and relevant objdump data is available in above tarball.
If the test is compiled without optimizations the test will pass (on arm at least).
(edit: remove link to aarch64 issue)
What did you expect to see?
$ ./passing-arm32-test
PASS

What did you see instead?
$ ./failing-arm32-test
--- FAIL: TestSampler (1.06s)
    sample_and_watermark_test.go:48: t0=2021-01-07 11:24:28.746138334 -0700 MST m=+0.016036811
panic: that was a bad year!: 0011-12-20 14:41:53.017034732 -0728 LMT [recovered]
	panic: that was a bad year!: 0011-12-20 14:41:53.017034732 -0728 LMT

goroutine 19 [running]:
testing.tRunner.func1.1(0x374e38, 0x122d068)
	/usr/local/go/src/testing/testing.go:1072 +0x264
testing.tRunner.func1(0x1082380)
	/usr/local/go/src/testing/testing.go:1075 +0x364
panic(0x374e38, 0x122d068)
	/usr/local/go/src/runtime/panic.go:969 +0x158
github.com/golang/32bit-bug.(*sampleAndWaterMarkObserverGenerator).quantize(0x10a6150, 0x103edec, 0x103ed78, 0x14a13f43, 0x0, 0x654a80, 0x80c40200, 0x434e01)
	/home/pi-star/go/src/github.com/golang/32bit-bug/sample_and_watermark.go:99 +0x164
github.com/golang/32bit-bug.(*sampleAndWaterMarkHistograms).innerSet.func1(0x10b8080, 0x103edec, 0x103edd0, 0x103ee00, 0x103edc4, 0x103ee48)
	/home/pi-star/go/src/github.com/golang/32bit-bug/sample_and_watermark.go:175 +0xb4
github.com/golang/32bit-bug.(*sampleAndWaterMarkHistograms).innerSet(0x10b8080, 0x103ee48)
	/home/pi-star/go/src/github.com/golang/32bit-bug/sample_and_watermark.go:204 +0x70
github.com/golang/32bit-bug.(*sampleAndWaterMarkHistograms).Set(0x10b8080, 0x0, 0x3ff00000)
	/home/pi-star/go/src/github.com/golang/32bit-bug/sample_and_watermark.go:155 +0x54
github.com/golang/32bit-bug.TestSampler(0x1082380)
	/home/pi-star/go/src/github.com/golang/32bit-bug/sample_and_watermark_test.go:57 +0x454
testing.tRunner(0x1082380, 0x3ea0c4)
	/usr/local/go/src/testing/testing.go:1123 +0xbc
created by testing.(*T).Run
	/usr/local/go/src/testing/testing.go:1168 +0x220

Thanks @rkojedzinszky @neolit123 @MikeSpreitzer @brandond @liggitt for help reporting & investigating

Thanks @rkojedzinszky @neolit123 @MikeSpreitzer @brandond @liggitt for help reporting & investigating

Is this still reproducible with a compiler built after CL 274026?
If not, it may be a duplicate of #42876.

Is this still reproducible with a compiler built after CL 274026?
If not, it may be a duplicate of #42876.

Hrm, but that wouldn't explain a repro on 386.

Hrm, but that wouldn't explain a repro on 386.

I can reproduce on 386.
It does not reproduce with GOGC=off.
Looks like something is getting clobbered. If I print out the good and bad time structs in hex, I get
85432914 bff5fbf2 0013edd9 00000000 0868a6c0    // good
0a44bde4 0a44bd70 0f446329 00000000 0868a6c0   // bad

The first 2 words there are valid pointers to the heap. Not sure about the 3rd one.
I think this only happens on 32-bit because on 32-bit the time.Time structure is not SSA-able (and thus is always in memory and copied using duffcopy) but on 64-bit it is SSA-able (and thus can live in registers).
I belive the bad code is in (*sampleAndWaterMarkHistograms).innerSet.func1, although I'm not sure yet. My guess is that the return value from Now is somehow getting clobbered before we can copy it out of the outargs region.
Still looking.

I can reproduce on 386.
It does not reproduce with GOGC=off.
Looks like something is getting clobbered. If I print out the good and bad time structs in hex, I get
85432914 bff5fbf2 0013edd9 00000000 0868a6c0    // good
0a44bde4 0a44bd70 0f446329 00000000 0868a6c0   // bad

The first 2 words there are valid pointers to the heap. Not sure about the 3rd one.
I think this only happens on 32-bit because on 32-bit the time.Time structure is not SSA-able (and thus is always in memory and copied using duffcopy) but on 64-bit it is SSA-able (and thus can live in registers).
I belive the bad code is in (*sampleAndWaterMarkHistograms).innerSet.func1, although I'm not sure yet. My guess is that the return value from Now is somehow getting clobbered before we can copy it out of the outargs region.
Still looking.

FWIW, moving the time struct into func1 seems to prevent it from getting clobbered. The in-tree fix using this approach is at https://github.com/brandond/kubernetes/commit/1a4e511830a482897c586f767bf32cad479fdae4

FWIW, moving the time struct into func1 seems to prevent it from getting clobbered. The in-tree fix using this approach is at https://github.com/brandond/kubernetes/commit/1a4e511830a482897c586f767bf32cad479fdae4

I think I see the problem. We have (irrelevant code elided):
v52 (176) = InterCall <mem> [24] v49 v51  // Call to Now (sample_and_watermark.go, 3rd line of (*sampleAndWaterMarkHistograms).innerSet.func1)
v53 (?) = OffPtr <*time.Time> [4] v2 // address of return value of Now (in outargs section - very volatile!)
v54 (176) = Move <mem> {time.Time} [20] v15 v53 v52 // save it to destination (v15, the heap storage for the `when` variable)
v60 (177) = Move <mem> {time.Time} [20] v59 v15 v58 // copy from `when` to a temporary (v59, address of a stack slot)
v64 (177) = Move <mem> {time.Time} [20] v53 v63 v62 // copy from temporary (v63, == v59) to the outargs section
v65 (177) = StaticCall <mem> {"".(*sampleAndWaterMarkObserverGenerator).quantize} [32] v64 // call `quantize`

That's all fine. But then we run the opt pass, which has this rule:
(Move {t} [n] dst1 src1 move:(Move {t} [n] dst2 _ mem))
	&& move.Uses == 1
	&& isSamePtr(dst1, dst2) && disjoint(src1, n, dst2, n)
	&& clobber(move)
	=> (Move {t} [n] dst1 src1 mem)

Which basically says, if you're moving from a to b, and then b to c, might as well move directly from a to c.
But, that rule isn't valid if a is a volatile location. We need to get data out of a ASAP.
(Volatile here means can get clobbered by a call.)
After the opt pass, we have the same code, except v60 copies from v53 instead of v15. Which is bad, because that source is the volatile memory area. It's only a problem if there is an intervening call. In this case there is one, but only if the write barrier is enabled. So the corruption doesn't happen until the write barrier is turned on. (The write barrier replaces v54 with a bunch of code that may call runtime.typedmemmove.)
I think the right fix is to add an extra condition to the move optimization rule to disable it if the source is a volatile region.

I think I see the problem. We have (irrelevant code elided):
v52 (176) = InterCall <mem> [24] v49 v51  // Call to Now (sample_and_watermark.go, 3rd line of (*sampleAndWaterMarkHistograms).innerSet.func1)
v53 (?) = OffPtr <*time.Time> [4] v2 // address of return value of Now (in outargs section - very volatile!)
v54 (176) = Move <mem> {time.Time} [20] v15 v53 v52 // save it to destination (v15, the heap storage for the `when` variable)
v60 (177) = Move <mem> {time.Time} [20] v59 v15 v58 // copy from `when` to a temporary (v59, address of a stack slot)
v64 (177) = Move <mem> {time.Time} [20] v53 v63 v62 // copy from temporary (v63, == v59) to the outargs section
v65 (177) = StaticCall <mem> {"".(*sampleAndWaterMarkObserverGenerator).quantize} [32] v64 // call `quantize`

That's all fine. But then we run the opt pass, which has this rule:
(Move {t} [n] dst1 src1 move:(Move {t} [n] dst2 _ mem))
	&& move.Uses == 1
	&& isSamePtr(dst1, dst2) && disjoint(src1, n, dst2, n)
	&& clobber(move)
	=> (Move {t} [n] dst1 src1 mem)

Which basically says, if you're moving from a to b, and then b to c, might as well move directly from a to c.
But, that rule isn't valid if a is a volatile location. We need to get data out of a ASAP.
(Volatile here means can get clobbered by a call.)
After the opt pass, we have the same code, except v60 copies from v53 instead of v15. Which is bad, because that source is the volatile memory area. It's only a problem if there is an intervening call. In this case there is one, but only if the write barrier is enabled. So the corruption doesn't happen until the write barrier is turned on. (The write barrier replaces v54 with a bunch of code that may call runtime.typedmemmove.)
I think the right fix is to add an extra condition to the move optimization rule to disable it if the source is a volatile region.

I have a small repro that also works on 64 bit.
It's been broken since 1.12.
@gopherbot please open backport issues.

I have a small repro that also works on 64 bit.
It's been broken since 1.12.
@gopherbot please open backport issues.

Thanks @randall77 for the fast analysis & fix!

Thanks @randall77 for the fast analysis & fix!


need to import numpy as np for np.zeros

Without this, examples/ex08.py raises
NameError: name 'np' is not defined


Improve help texts

This address the minor issues raised in https://github.com/lxc/lxd/issues/2627.
I've updated the relevant source file and then ran $ make update-pot. Frankly I'm not sure that is it. I feel the other three *.po need some love too.

This pull request didn't trigger Jenkins as its author isn't in the whitelist.
An organization member must perform one of the following:

To have this branch tested by Jenkins, use the "ok to test" command.
To have a one time test done, use the "test this please" command.

Those commands are simple Github comments of the format: "jenkins: COMMAND"

jenkins: test this please


Documentation referring to "aihwkit.simulator.devices" which does not exist

Description
The documentation on this page: https://aihwkit.readthedocs.io/en/latest/design.html, describing how the AI HW Kit is built refers to a number of modules in each section. The link to the devices section is non-functional, and on further inspection such a module does not seem to exist (any longer?).
How to reproduce
The broken link/erroneous referral can be found here: https://aihwkit.readthedocs.io/en/latest/design.html#python-simulator-abstraction-layer
Expected behavior
Probably a removal of the referral and replacement text with how the new version actually works.
Other information
I'm not 100% sure if this is where I should be reporting documentation problems, so please close the issue if this isn't the right place. Thanks.

Thanks for reporting this. We will fix this issue.

The correction is included in the PR 601 above.   Let us know if you have any questions.  Thanks.


Fix git tag group ignore git tag prefix issue - #357

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
This pr should fix #357.

Hi @nimrodkor, we'd like to use yor in our projects but we've encountered some bugs, would you please review this pr when you have time? Thanks!

Hello? Is this project still actively maintained?

Sorry for the long response times, it's been holiday season with some extra vacation here :) @lonegunmanb

Sorry for the long response times, it's been holiday season with some extra vacation here :) @lonegunmanb

Nice! I've created a tool named yorbox which I believe can be used along with yor in our projects. yor would be a vital part of our modules, thank you for your great job!


Disable anonymous read-only API port

This commit disables the anonymous (non-authenticated) read-only API
port, which is insecure, and adjusts the Heapster and metrics-server
configuration to take this into account.
Fixes: #36
Fixes: https://github.com/scality/metal-k8s/issues/36
See: https://github.com/kubernetes-incubator/kubespray/issues/2550#issuecomment-377145148
See: 71206ef027347d4386f0109aa88848929c10a42c
See: https://github.com/scality/metal-k8s/commit/71206ef027347d4386f0109aa88848929c10a42c#diff-384fbcda7fecbabd124cf2ccae3167cdR9

I tried testing this branch with a fresh 3 node install the below in Firefox when trying to connect to the ui. Perhaps this is an unintended side effect of disabling the read only port?
  |
-- | --
paths |
0 | "/apis"
1 | "/apis/"
2 | "/apis/apiextensions.k8s.io"
3 | "/apis/apiextensions.k8s.io/v1beta1"
4 | "/healthz"
5 | "/healthz/etcd"
6 | "/healthz/ping"
7 | "/healthz/poststarthook/generic-apiserver-start-informers"
8 | "/healthz/poststarthook/start-apiextensions-controllers"
9 | "/healthz/poststarthook/start-apiextensions-informers"
10 | "/metrics"
11 | "/openapi/v2"
12 | "/swagger-2.0.0.json"
13 | "/swagger-2.0.0.pb-v1"
14 | "/swagger-2.0.0.pb-v1.gz"
15 | "/swagger.json"
16 | "/swaggerapi"
17 | "/version"

Ugh, you're right! Seems like a blocker to me :smile: (and shows once again we need some kind of conformance tests...)

Looks like this may be caused by #55 or something else, not sure current master works...

So, well, no, it makes sense. The change is not due to this PR, but due to the switch to Kubernetes 1.10 through #55. In 1.10, the /ui shortcut no longer exists, and one needs to use the full service URL, see the first Note in https://github.com/kubernetes/dashboard/blob/9485b641b0cc6008c2fbd5f5e1a927a3b40ef255/README.md#getting-started
I guess this should be documented now, and maybe we should add the required annotations to the Dashboard service such that the URL is displayed in kubectl cluster-info.

Ahh I see and yeah it works just fine with that URL! But yeah it would be a good idea to get it documented and added to the required annotations.
I agree with the conformance tests aswell. We could do a single node deployment with EVE and an open stack worker to test deployment then run at least some basic conformance tests.


Reduce the run time of tests

Some tests take a long time to run, making them harder to use for regression testing. We should look for opportunities to reduce the execution time while retaining enough coverage.

Thread dimensions uses a kernel (clear_memory_kernel) to memset an enormous buffer before running each "real" kernel. Changing this to a clEnqueueWriteBuffer would improve runtimes considerably.
(I have this already as a patch and will be more than happy to provide).

That sounds great! One could probably use clEnqueueFillBuffer as well. Maybe worth creating a separate issue for this one.


fix(engine): close file when untar

/ok-to-test

@nikpivkin Please add a test for this.

@bcrochet What's the test supposed to check? I just added file closing.

@bcrochet What's the test supposed to check? I just added file closing.

Fair enough. Thanks for the submission.


Add a WLM role to be used by Flux

Define the capabilities that a WLM such as Flux would need to interact with the DataWorkflowServices API and a Rabbit system.

Should a WLM be allowed to query PersistentStorageInstances?  It seems like it ought to be able to [get, list, watch] them, but I'm not sure why it would do that.

See the matching doc update in https://github.com/NearNodeFlash/NearNodeFlash.github.io/pull/62


Errors uploading an allowlist or setting a key are silently ignored

Fixed

Turns out this isn’t fixed.  The problem is that https://github.com/Zondax/ledger-substrate-rs/blob/master/src/substrate.rs#L216 only logs retcode, even though a return code other than NoError is an error condition.


Split classes etc. into separate files

To make it easier to maintain, the DiceRoller and DiceRoll classes should be split into their own files.
It would probably also be best to split the utility methods into their own (And maybe even the notation parsing), rather than as a property on the DiceRoller objects.

Completed in pull request #69 And will go out in v3.0.0


B 19821 sit auth date to db int

Do not merge before https://github.com/transcom/mymove/pull/12593
Agility ticket
Summary
The point of this story is to store the SIT authorized end date value in the database so that it can be sent to Homesafe. Previously, this SIT authorized end date was just being calculated on the front end but not stored anywhere.
The sitStatus holds most of the frontend calculations, with pkg/services/sit_status/shipment_sit_status.go being where a lot of the meat and potatoes are for the SIT panel on the MTO page.
The work here captures that SIT authorized end date value (sitStatus.CurrentSIT.SITAuthorizedEndDate) and stores it in the mto_shipments table in either the origin_sit_auth_end_date column or the dest_sit_auth_end_date column, dependent on whether sitStatus.CurrentSIT is Origin or Destination. Logic was added to the handlers for updating a service item (when the TOO approves the service items, this populates the SIT panel initially), a SIT extension creation and approval by the TOO, and approval of a SIT extension request from the prime.
We also now return the SIT authorized end date stored on the shipment in the response for the prime v1, v2, and v3 getMoveTaskOrder endpoints. SIT entry date was already being included in the response for this endpoint at the service item level. Now, HSC will have both the SIT start date and SIT authorized end date available to them which is what the feature is all about.
How to test
Origin:

As a customer, create a new move with shipments.
Counsel the move, approve as TOO
As the prime, request origin SIT. Make sure the SIT entry date is earlier than the current day you are testing AND the departure date is later than the current day.
On the MTO page, approve the origin SIT service items. If your SIT panel on the MTO page does not say "Current location: origin SIT" you can modify the SIT entry date on the service item below to be a date preceding the current day.
Check the mto_shipments table. You should see the origin_sit_auth_end_date value in the database populated with a value that matches what you see on the MTO page SIT panel for SIT authorized end date.
Edit the SIT authorized end date or the Total days of SIT approved fields and make sure if the SIT authorized end date changes, that change is also reflected in the database.
Call the prime getMoveTaskOrder endpoint for the move you created (prime v1, v2, or v3). Ensure that you see originSitAuthEndDate in the response, as well as an accurate sitEntryDate under the DOFSIT service item.

Request SIT Extension
8. As the prime, find the shipment you created for your new move that still has the current location as origin SIT.
9. "Request SIT Extension" as the prime
10. Go back to the MTO page as the TOO
11. Find the Review request next to "Additional Days Requested"

12. Reject the SIT extension. You can change the dates on the modal, but rejecting should NOT update the SIT auth end date or allowed days.
13. As the prime, request another SIT extension.
14. As the TOO, modify the SIT auth end date or days allowed and approve the extension.
15. Call the prime getMoveTaskOrder endpoint for the move you created (prime v1, v2, or v3). Ensure that you see originSitAuthEndDate in the response, as well as an accurate sitEntryDate under the DOFSIT service item.
Destination:

As a customer, create a new move with shipments.
Counsel the move, approve as TOO
As the prime, request destination SIT. Make sure the SIT entry date is earlier than the current day you are testing AND the departure date is later than the current day.
On the MTO page, approve the destination SIT service items. If your SIT panel on the MTO page does not say "Current location: destination SIT" you can modify the SIT entry date on the service item below to be a date preceding the current day.
Check the mto_shipments table. You should see the dest_sit_auth_end_date value in the database populated with a value that matches what you see on the MTO page SIT panel for SIT authorized end date.
Edit the SIT authorized end date or the Total days of SIT approved fields and make sure if the SIT authorized end date changes, that change is also reflected in the database.
Call the prime getMoveTaskOrder endpoint for the move you created (prime v1, v2, or v3). Ensure that you see destinationSitAuthEndDate in the response, as well as an accurate sitEntryDate under the DDFSIT  service item.

Request SIT Extension
8. As the prime, find the shipment you created for your new move that still has the current location as destination SIT.
9. "Request SIT Extension" as the prime
10. Go back to the MTO page as the TOO
11. Find the Review request next to "Additional Days Requested"

12. Reject the SIT extension. You can change the dates on the modal, but rejecting should NOT update the SIT auth end date or allowed days.
13. As the prime, request another SIT extension.
14. As the TOO, modify the SIT auth end date or days allowed and approve the extension.
15. Call the prime getMoveTaskOrder endpoint for the move you created (prime v1, v2, or v3). Ensure that you see originSitAuthEndDate in the response, as well as an accurate sitEntryDate under the DOFSIT service item.

Ran into an issue in your first scenario. Here's how to replicate:

change auth end date in SIT panel (changes in db are good)
change SIT entry date for origin 1st day SIT, change reflect in SIT panel but does not update the database

Need to also update SIT auth end date in the database when the SIT entry date update handler fires.

Great catch, fixing now

Ran into an issue in your first scenario. Here's how to replicate:

change auth end date in SIT panel (changes in db are good)
change SIT entry date for origin 1st day SIT, change reflect in SIT panel but does not update the database

Need to also update SIT auth end date in the database when the SIT entry date update handler fires.

Should be working now


Respect the exception mask in storage::ObjectReadStream.

The storage::ObjectReadStream class should respect the exception mask. Errors should be reported using exceptions if the exception mask is set. If the exception mask is not set then we should set the correct iostream bits and save the full status in a member variable.

This was fixed as part of #1753 and #1750.


Make CI fail on first error and not have to finish the job to fail

Summary
This makes intermediate functions in testbuild.sh do return $fail which will make the script abort when run with -x as it is done during CI build. Currently the build will only fail at the end of all build jobs once it reaches exit $fail. This should make PRs fail faster.
Impact
CI
Testing
CI from this PR. Note that master is currently not passing CI, we just didn't knew it because of this problem: https://github.com/apache/incubator-nuttx-testing/pull/62

I think this is intentional so that we can see all the failures in the build and not just the last one.  I don't have strong opinion about changing it, but I think this is working as expected.

@liuguo09 I think you added this logic.  Any thoughts?

No problem if you prefer to leave it as it is. I just think it could speed up review process.

I think it could behave this way: 1) if it is a coding style error or a warning was promoted to error, then the building system should carry on. 2) if it is a real compilation error then it could stop to save processing time and let others PR to finish faster.

Sometime, the change may introduce the break in the multiple locations. If we terminate the build when the first error hit, we have to fix the error one by one which make the recovery process become much longer and painful, then more PR will be blocked for long time.

I understand the usefulness of having this continue to run, I'm not opposed.
However, do note that what I'm actually fixing here is the behavior of -x parameter, which is actually used on CI. Maybe the -x is to have the script abort on other errors, but with -x I would expect any build failure to abort the script. In other words, maybe the path is merge this PR and then remove -x from the workflow.

I understand the usefulness of having this continue to run, I'm not opposed.
However, do note that what I'm actually fixing here is the behavior of -x parameter, which is actually used on CI. Maybe the -x is to have the script abort on other errors, but with -x I would expect any build failure to abort the script. In other words, maybe the path is merge this PR and then remove -x from the workflow.

Yes, it will be good that we remove -x from the workflow together with this path.

I understand the usefulness of having this continue to run, I'm not opposed.
However, do note that what I'm actually fixing here is the behavior of -x parameter, which is actually used on CI. Maybe the -x is to have the script abort on other errors, but with -x I would expect any build failure to abort the script. In other words, maybe the path is merge this PR and then remove -x from the workflow.

Yes, it will be good that we remove -x from the workflow together with this path.

@btashton sounds also OK to you?

Sounds good to me.

Ok, I removed the -x and updated the PR description/commit msg.

LGTM, @btashton please merge it if you don't have the furture concern.

@btashton @v01d Yes, it's intentional to cover all possible failures at first time to ease development, as @xiaoxiang781216 shows more info in comments.


Training Quality Object

Description

Add in a deepClone utility, as I needed to copy a structured object in the fromJSON method. I create a deepClone of the passed in json prior to everything else, this way we don't need to worry messing with the JSON messing with our net.
I also added in a training quality object to the net, which gets imported/exported in JSON form. This will give information on how the train method performed on it's last run, as well as for any training sets used.
Motivation and Context

issue
How Has This Been Tested?

Added in a new test for .trainingQuality, can run yarn test to see it work.
Screenshots (if appropriate):
Types of changes

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

Author's Checklist:

[x] My code focuses on the main motivation and avoids scope creep.
[x] My code passes current tests and adds new tests where possible.
[x] My code is SOLID and DRY.
[x] I have updated the documentation as needed.

Reviewer's Checklist:

[ ] I kept my comments to the author positive, specific, and productive.
[ ] I tested the code and didn't find any new problems.
[ ] I think the motivation is good for the project.
[ ] I think the code works to satisfies the motivation.

I say lets us a simple enough library, that is specific to this requirement.  If we end up needing to a lot of the functionality that lodash provides, we can migrate to it, but for the time being lets just use a simple lib and that way we don't own it.

so all training sets, period, will be saved on the net?

couldn't that be optional?  It seems like some scenarios where we have millions of training items will potentially cause an issue.

Its each training set, or each time you run train

So if you're running train a million times, then it would be somewhat of a problem

"training items" meaning a single training set with a million or more items

Too far from source.  Perhaps better suited as an add-on or extension?


Error: decorated type deeper than introspection query

I have a data structure that corresponds to GeoJSON Multipolygon, which is:
[[[[Float!]!]!]!]!
However I get the error: decorated type deeper than introspection query
I presume it has to do with the nested array. Is there a way to introspect this kind of data structure, without losing introspection on the whole graph?
Here is a type with a field (multipolygon) that produces the issue
type GeoJSON {
  type: String!
  boundingbox: [Float!]
  point: [Float!]
  multipoint: [[Float!]!]
  linestring: [[Float!]!]
  multilinestring: [[[Float!]!]!]
  polygon: [[[Float!]!]!]
  multipolygon: [[[[Float!]!]!]!]
}

The problem starts on field multipolygon. If I erase this, everything works the way it should.

I think this is a problem with your client library, what are you using? most introspection queries stop or 4 or 5 levels deep

@vektah I am using Insomnia. I should file an issue with them then.


Automated Package Upgrade

:tada: This PR is included in version 25.3.503 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Cannot read properties of undefined (reading 'getCell')

Does this issue occur when all extensions are disabled?: Yes/No

VS Code Version: 1.66-insider
OS Version: Windows 11

I started seeing this in developer tools today, no repro though
Callstack:
Cannot read properties of undefined (reading 'getCell'): TypeError: Cannot read properties of undefined (reading 'getCell')
    at w._matches (vscode-file://vscode-app/c:/Users/huer/AppData/Local/Programs/Microsoft%20VS%20Code%20Insiders/resources/app/out/vs/workbench/workbench.desktop.main.js:1272:1791)
    at w.detect (vscode-file://vscode-app/c:/Users/huer/AppData/Local/Programs/Microsoft%20VS%20Code%20Insiders/resources/app/out/vs/workbench/workbench.desktop.main.js:1272:1366)
    at D._provideLinks (vscode-file://vscode-app/c:/Users/huer/AppData/Local/Programs/Microsoft%20VS%20Code%20Insiders/resources/app/out/vs/workbench/workbench.desktop.main.js:1248:9236)
    at D.provideLinks (vscode-file://vscode-app/c:/Users/huer/AppData/Local/Programs/Microsoft%20VS%20Code%20Insiders/resources/app/out/vs/workbench/workbench.desktop.main.js:1248:8763)
    at vscode-file://vscode-app/c:/Users/huer/AppData/Local/Programs/Microsoft%20VS%20Code%20Insiders/resources/app/node_modules.asar/xterm/lib/xterm.js:1:39100
    at Array.forEach (<anonymous>)
    at t._askForLink (vscode-file://vscode-app/c:/Users/huer/AppData/Local/Programs/Microsoft%20VS%20Code%20Insiders/resources/app/node_modules.asar/xterm/lib/xterm.js:1:38962)
    at t._onHover (vscode-file://vscode-app/c:/Users/huer/AppData/Local/Programs/Microsoft%20VS%20Code%20Insiders/resources/app/node_modules.asar/xterm/lib/xterm.js:1:38509)
    at t._onMouseMove (vscode-file://vscode-app/c:/Users/huer/AppData/Local/Programs/Microsoft%20VS%20Code%20Insiders/resources/app/node_modules.asar/xterm/lib/xterm.js:1:38369)

/duplicate #145508


CntkEmitter has not supported operator [UpSampling2D]

Platform (like ubuntu 16.04/win10): Ubuntu 16.04
Python version: python 3.5
Source framework with version (like Tensorflow 1.4.1 with GPU): tensorflow 1.60 with GPU
Destination framework with version (like CNTK 2.3 with GPU): CNTK 2.5.1 with GPU
I met the problem as title CntkEmitter has not supported operator [UpSampling2D]

@kitstar I searched the internet, and can we use this way?
import cntk
import numpy as np
def UpSampling2D(x, size = (1, 3, 3)):
kernel = cntk.constant(value = np.ones(size, dtype=np.float32))
return cntk.convolution_transpose(kernel, x, auto_padding = [False], strides = size)

Hi @HanYuanyuaner , seems we can have a try. I will ping you as soon as it implemented. Thanks.

Hi @HanYuanyuaner , I found there is a upsampling implementation in cntk emit. Could you share your original model for us to refine the parser part.


[Feature] Name of document in Menu Bar

When you have many open documents and right click on the menu bar they are all called "Google Drive". It would be nice if the name of the document appeared there so it would be easier to switch between docs

Think this is a duplicate of #44


upgrade to jts 1.16.0 and protobuf-java 3.6.1

We use your library successfully here: https://github.com/graphhopper/graphhopper/pull/1572 Thanks!
Now we need to upgrade to the latest JTS 0.16.0, because JTS 0.15.1 and 0.16.0 are slightly different for certain method signatures and we can only upgrade if we upgrade all our dependencies that use it :)
Additionally protobuf-java has a new release 3.6.1 (from 31 Jul 2018) which is e.g. used from osm binary. But we can also keep it at 3.5.1

Please see https://github.com/wdtinc/mapbox-vector-tile-java/issues/32#issuecomment-479069089
Android JTS 1.16+ compatibility remains the same(?) forcing Java 8 and Android N (--min-api 24).
Related to https://github.com/locationtech/jts/issues/145

这是来自QQ邮箱的自动回复邮件。

您好，您的邮件已收到。


Nodes on testnet doesn't accept reservations

It waits until deployment timeouts (15 mins)
example wid: https://explorer.testnet.grid.tf/api/v1/reservations/workloads/490477

72CP8QPhMSpF7MbSvNR1TYZFbTnbRiuyvq5xwcoRNAib

seems provisiond panics, and is stuck in a restart loop. Relevant logs:
...
  | 2020-10-12 11:11:21 | [+] provisiond: 2020-10-12T09:11:21Z info starting provision module broker=unix:///var/run/redis.sock
-- | -- | --
  |   | 2020-10-12 11:11:21 | [+] provisiond: 2020-10-12T09:11:21Z info restart detected, keep reservation cache intact
  |   | 2020-10-12 11:11:21 | [+] flistd: 2020-10-12T09:11:21Z debug running cleaner job
  |   | 2020-10-12 11:11:18 | [-] provisiond: 	/home/runner/work/zos/zos/cmds/provisiond/main.go:164 +0xff0
  |   | 2020-10-12 11:11:18 | [-] provisiond: main.main()
  |   | 2020-10-12 11:11:18 | [-] provisiond: 	/home/runner/work/zos/zos/pkg/provision/engine.go:138 +0xbd1
  |   | 2020-10-12 11:11:18 | [-] provisiond: github.com/threefoldtech/zos/pkg/provision.(*Engine).Run(0xc000406000, 0x1088360, 0xc00003a800, 0x0, 0x0)
  |   | 2020-10-12 11:11:18 | [-] provisiond: 	/home/runner/work/zos/zos/pkg/provision/engine.go:205 +0x174
  |   | 2020-10-12 11:11:18 | [-] provisiond: github.com/threefoldtech/zos/pkg/provision.(*Engine).provision(0xc000406000, 0x1088360, 0xc00003a800, 0xc00058cf00, 0x0, 0xc0005d3c00)
  |   | 2020-10-12 11:11:18 | [-] provisiond: 	/home/runner/work/zos/zos/pkg/provision/primitives/container.go:109
  |   | 2020-10-12 11:11:18 | [-] provisiond: github.com/threefoldtech/zos/pkg/provision/primitives.(*Provisioner).containerProvision(...)
  |   | 2020-10-12 11:11:18 | [-] provisiond: 	/home/runner/work/zos/zos/pkg/provision/primitives/container.go:172 +0xa1d
  |   | 2020-10-12 11:11:18 | [-] provisiond: github.com/threefoldtech/zos/pkg/provision/primitives.(*Provisioner).containerProvisionImpl(0xc00079e960, 0x1088360, 0xc00003a800, 0xc00058cf00, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, ...)
  |   | 2020-10-12 11:11:18 | [-] provisiond: 	/home/runner/work/zos/zos/pkg/provision/primitives/crypto.go:39 +0x345
  |   | 2020-10-12 11:11:18 | [-] provisiond: github.com/threefoldtech/zos/pkg/provision/primitives.decryptSecret(0xc0005e0000, 0xa0, 0xc0004d6028, 0x3, 0x1, 0x1073060, 0xc00000e030, 0x8, 0x4, 0x0, ...)
  |   | 2020-10-12 11:11:18 | [-] provisiond: 	/home/runner/work/zos/zos/pkg/stubs/identity_stub.go:45 +0x355
  |   | 2020-10-12 11:11:18 | [-] provisiond: github.com/threefoldtech/zos/pkg/stubs.(*IdentityManagerStub).DecryptECDH(0xc000352948, 0xc0005680a0, 0x50, 0xa0, 0xc0006af6c0, 0x20, 0x40, 0x0, 0x0, 0x4760bc, ...)
  |   | 2020-10-12 11:11:18 | [-] provisiond: goroutine 1 [running]:
  |   | 2020-10-12 11:11:18 | [-] provisiond:
  |   | 2020-10-12 11:11:18 | [-] provisiond: panic: not a function
  |   | 2020-10-12 11:11:18 | [+] networkd: 2020-10-12T09:11:18Z info check if interface has a cable plugged in iface=b-NFFfnKSqqFxDm
  |   | 2020-10-12 11:11:18 | [+] networkd: 2020-10-12T09:11:18Z info check if interface has a cable plugged in iface=b-G6i28tC2UBNyU
  |   | 2020-10-12 11:11:18 | [+] networkd: 2020-10-12T09:11:18Z info interface is not plugged in, skipping interface=b-HiB2BGoT9Pqzn
  |   | 2020-10-12 11:11:13 | [+] networkd: 2020-10-12T09:11:13Z info check if interface has a cable plugged in iface=b-HiB2BGoT9Pqzn
  |   | 2020-10-12 11:11:13 | [+] networkd: 2020-10-12T09:11:13Z info check if interface has a cable plugged in iface=b-EmszGGwsUacmE
  |   | 2020-10-12 11:11:13 | [+] networkd: 2020-10-12T09:11:13Z info interface is not plugged in, skipping interface=b-Ha467CygvG52h
  |   | 2020-10-12 11:11:10 | [+] provisiond: 2020-10-12T09:11:10Z info start provisioning reservation duration=2562047h47m16.854775807s expired=false id=490520-1 tag= to-delete=false type=container
  |   | 2020-10-12 11:11:10 | [+] provisiond: 2020-10-12T09:11:10Z info provision statistics container=21 cru=26 delegateDomain=0 hru=5130 k8sVM=4 mru=31 network=169 proxy=0 reverseProxy=0 sru=221 subdomain=0 volume=15 zDBNamespace=12
  |   | 2020-10-12 11:11:10 | [+] provisiond: 2020-10-12T09:11:10Z info reservation have already been processed id=476445-1
  |   | 2020-10-12 11:11:10 | [+] provisiond: 2020-10-12T09:11:10Z info start provisioning reservation duration=2562047h47m16.854775807s expired=false id=476445-1 tag= to-delete=false type=container
  |   | 2020-10-12 11:11:10 | [+] provisiond: 2020-10-12T09:11:10Z info reservation have already been processed id=472733-6
  |   | 2020-10-12 11:11:10 | [+] provisiond: 2020-10-12T09:11:10Z info start provisioning reservation duration=2562047h47m16.854775807s expired=false id=472733-6 tag= to-delete=false type=volume
  |   | 2020-10-12 11:11:10 | [+] provisiond: 2020-10-12T09:11:10Z info reservation have already been processed id=474441-1
  |   | 2020-10-12 11:11:10 | [+] provisiond: 2020-10-12T09:11:10Z info start provisioning reservation duration=2562047h47m16.854775807s expired=false id=474441-1 tag= to-delete=false type=volume
  |   | 2020-10-12 11:11:10 | [+] provisiond: 2020-10-12T09:11:10Z info reservation have already been processed id=472725-6
  |   | 2020-10-12 11:11:10 | [+] provisiond: 2020-10-12T09:11:10Z info start provisioning reservation duration=2562047h47m16.854775807s expired=false id=472725-6 tag= to-delete=false type=volume
...

~ # identityd -v
Version: v0.4.0 @Revision: 60e0f395ce91eb018523b1abed1f5054356d5432 (dirty-repo)

seems some manual update of identityd was made on this node. we manually fixed the problem


Better logging of what went wrong.

Every now and then I get the "Could not build the build-info object" error in my Jenkins pipeline. However I actually suspect that it is not the building-part that is the problem but rather the publishing. I have no way of telling because the logging will default to "Could not build the build-info object" even if an exception occurs in sendBuildInfo.

@mathiasi,
I'd expect to see which method throw the exception in the exception stacktrace.
Any idea why you do not see a stacktrace in the build log?

@mathiasi,
I'm closing this one for now, but do let us know if you'd like to continue working on it.


Table: add aria-label and aria-labelledby

Description
Added support for aria-label and aria-labelledby for table using properties labelled and labelledby respectively
Related Issue
Motivation and Context
Missing aria-label and aria-labelledby support in table
How Has This Been Tested?
I have run all test cases locally . Added new test cases to check new changes
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have read the CONTRIBUTING document.

@icaraps  Please review.
For added properties, Do we require any documentation change.


Does not close out window or save token after login

Window is redirected and displays some response object. The token is never saved and window remains open after login.

I have the same problem using electron.

I'm using electron and have the issue too... any feedback ?

@Fairen @jackel27 there is a fix for this:
https://github.com/hypertd/twitch-node-sdk/commit/c015703b1ff73904417e8ae69c61174bb4f49ac1
I will be submitting a pull request if @hypertd doesnt, but it would be awesome if @Spiffyk implemented it.


Adds split and tabedit mappings. Adopted by fzf.vim

This PR adds mappings for open in split, vsplit and new tab.
The mappings were adopted by fzf and vim-clap.
 opens in new horizontal split.
 opens in new vertical split.
 opens in new tab.

Sorry, hate to be pedantic about the spacing :laughing:
After that I'll merge. Thanks for the PRs!!

Awesome! Thanks.


UI should not be selectable unless it is tagged so

I have something like this in my app
.notSelectable {
	-webkit-touch-callout: none;
	-webkit-user-select: none;
	-khtml-user-select: none;
	-moz-user-select: none;
	-ms-user-select: none;
	user-select: none;
}

.selectable {
	-webkit-touch-callout: text;
	-webkit-user-select: text;
	-khtml-user-select: text;
	-moz-user-select: text;
	-ms-user-select: text;
	user-select: text;
}

Thanks ! Would you like to test it on Windows, Linux, and OSX and make a PR ?

As I am not a user of this project, sorry for the drive-by comment, I am not sure how this would be implemented, "unless it is tagged so" how does this impact what a user does? Does it mean they add a class or a property to a component or call a method in an api?

@fabrixxm Could you answer this please ?


Unable to disable proxy with proxy: false

Per documentation:

The proxy is configured in the root configuration under proxy. These are options that are set when deploying the application, not when booting the proxy.
They are application-specific, so they are not shared when multiple applications run on the same proxy.
The proxy is enabled by default on the primary role but can be disabled by setting proxy: false.

This doesn't work, because the code that actually disables the proxy lives in Kamal::Configuration::Role#initialize_specialized_proxy, and it only takes role proxy configuration into account, not the top-level root configuration.
As a workaround, you can disable the proxy in servers:
servers:
  web:
    hosts:
      - <IP_ADDRESS>
    proxy: false

See also https://github.com/basecamp/kamal/issues/1133#issuecomment-2429097515 and https://github.com/basecamp/kamal/issues/1133#issuecomment-2548971210

See also #1133 (comment)

He's right. I've given in to using Kamal the way it's intended; much easier that way. The proxy doesn't add any noticeable latency and is an essential component for zero-downtime deploys.
I'm closing this issue so it doesn't clutter up the project.


HIP sample module_api hangs or crashes.

Trying to run the /opt/rocm/hip/samples/0_Intro/module_api/ sample fails. It either hangs or crashes.

Wrong repo.


Double tap on History and Browse not working as intended

Steps to reproduce

Open the App(the obvious)
Select History on the bottom navigation
Tap once again while on anime history and then try again while on manga history
Do the same thing on the browse tab, anime sources and manga sources

Expected behavior

Double tap on history while on anime plays the last episode watched, and.double.tap on manga history should open the last chapter read.
Double tap browse anime sources should open search in anime sources, double tap on browse manga sources should open search in the manga sources.

Actual behavior

Double tap on history only plays last anime episode, independent on. Whether the current history on screen is anime or manga.
Double tap on browse opens search in anime sources independent of whether on screen source page in anime or manga, or anime extension list or manga extension list or migrate pages.

Crash logs
No response
Aniyomi version
r7479
Android version
Android 11
Device
Realme X
Other details
No response
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] If this is an issue with an official extension, I should be opening an issue in the extensions repository.
[X] If this is an issue with an official manga extension and this issue can be replicated in the Tachiyomi app, that I should be opening an issue in Tachiyomi's extensions repository.
[X] I have gone through the FAQ and troubleshooting guide.
[X] I have updated the app to version <IP_ADDRESS>.
[X] I have updated all installed extensions.
[X] I will fill out all of the requested information in this form.

Tbh, I haven't gone through FAQ but I don't think this would be there. If it is do tell me. Thanks


drop support for EL7

Should resolve the https://github.com/voxpupuli/puppet-epel/pull/159 spec failures.


It was working and now it is not working.

https://pastebin.com/VXUX19M8
can someone put the glasses on and update the version?
to you-know-what-page

I will fix it and publish on curseforge.

Good luck!

'It was working and now it is not working': An erectile dysfunction tale™

Of course. Look on the crash log. Dont be mad bro, maybe this time you will comeback ™

I need an update via cf, the license does not indicate anything that publishing was prohibited? you have a pain in your ass but you do nothing? ; v
https://user-images.githubusercontent.com/97899734/150265890-7fff595b-137c-4de3-86a6-3b5960d29440.mp4

There is nothing preventing you from re-distributing Astromine, but just remember that we would be happy if your releases could be provided under a different name or equivalent as that could confuse users from the official releases. Of course, legally speaking you have no obligation in doing this.
The future of Astromine is unknown and we are unable to provide any details on that subject

Thanks for the information, I want to live in harmony, nor do I want to do
something that others will be dissatisfied with. If you find a moment you
could at least build and publish version 1.16.5 on cf, I really care about
this modification, its only ten minutes,
Thanks,
(>^-^<)
W dniu czw., 20.01.2022 o 07:13 shedaniel @.***>
napisał(a):

Closed #424 https://github.com/Mixinors/Astromine/issues/424.
—
Reply to this email directly, view it on GitHub
https://github.com/Mixinors/Astromine/issues/424#event-5922417813, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AXK5JVVDDAX3RB4SPLXIIY3UW6RXLANCNFSM5MIIUHSA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you modified the open/close state.Message
ID: @.***>

the mod knows when it works by knowing when it workn't.


Abort/timeout long running requests

Currently long running requests may continue to consume a large amount resources, while the original request already timed-out in a http-layer above. We should add a configurable timeout to abort requests in quickwit
There are two different timeouts configured:
Tonic  Timeout
tonic timeouts return errors like:
{
  "message": "internal error: `Timeout expired`"
}

This timeout is originating here:
let timeout_channel = Timeout::new(node.channel(), Duration::from_secs(30));
let search_client = create_search_client_from_channel(
    grpc_addr,
    timeout_channel,
    max_message_size,
);
Some(Change::Insert(grpc_addr, search_client))

Tower Timeout
There's another similar timeout, from tower
{
  "message": "internal error: `request timed out`"
{

The tower timeout is defined here:
/// Creates a channel from a socket address.
///
/// The function is marked as `async` because it requires an executor (`connect_lazy`).
pub async fn make_channel(socket_addr: SocketAddr) -> Channel {
    let uri = Uri::builder()
        .scheme("http")
        .authority(socket_addr.to_string())
        .path_and_query("/")
        .build()
        .expect("provided arguments should be valid");
    Endpoint::from(uri)
        .connect_timeout(Duration::from_secs(5))
        .timeout(Duration::from_secs(30))
        .connect_lazy()
}

The behavior of timeouts also differs currently on the dispatch type, local dispatch never times out.
Retries
The current behavior is to retry directly after a timeout (cluster_client.rs::leaf_search). This could add additional load on a overloaded node.
The first step would be to properly transform the error type to keep the semantics

Fixed by https://github.com/quickwit-oss/quickwit/pull/5402


Create CI workflow with GitHub Actions

Create CI workflow with GitHub Actions which:

Builds the encoder and decoder for Android
Builds the Android APK and uploads it to GitHub as build artifact and on releases

GitHub Actions needs to be enabled here: https://github.com/google/lyra/actions. In the mean time an example run can be found here.
Update: Removed the Linux build for now and cleaned up commits. A Linux build will be added in another PR since the specific version requirement makes it a little more complex.

Thanks for your review! I think I implemented or answered all your suggestions and questions, please resolve the conversation if that's done satisfactory.
As of the Linux job, I was indeed looking into installing that specific Clang version. To confirm: the latest stable release (11.1.0) won't cut it and https://github.com/llvm/llvm-project/commit/96ef4f307df27f4e0946eb344bac2703017ad073 is needed specifically?

As of the Linux job, I was indeed looking into installing that specific Clang version. To confirm: the latest stable release (11.1.0) won't cut it and llvm/llvm-project@96ef4f3 is needed specifically?

Oh, wow, thanks for looking into that.
Yes, using that specific SHA would be ideal.


npm install<EMAIL_ADDRESS>not working

Hi Team,
It seems npm install<EMAIL_ADDRESS>is not working, giving below error.

Can anyone help ?
cc @rektdeckard

The package has been moved under our NPM workspace. It is now @phosphor-icons/react.


workspaces: fix outdated namespace reference

Workspaces is deployed in the workspaces-system namespace, not the konflux-workspaces namespace.  Update argocd's reference so that it doesn't have to manage a namespace that will never be populated.

/lgtm

/assign @zregvart

/approve