Cirrus F30

Test and incorporate new F30 image and a fix for a very ugly google vs cloud-init race post-build.

Note: This one is waiting for #2561 to merge.

/hold

/hold cancel

@edsantiago while I'm finalizing this one,  IIRC there was some small typo or somesuch you wanted me to fix?

It was a trivial one: contrib/cirrus/setup_environment.sh, 'resuze' -> 'resize2fs'

@edsantiago thanks...got it.

@mheon @baude @giuseppe @edsantiago PTAL F30 is ready to go

LGTM

/hold

sigh
My old-friend, the "failure-to-expand disk" problem is back, now on F30 (previously was F29) :confused:

/me jumps up and down cursing: I thought I fixed the disk-space problem :sob:

Seems I did fix one disk-resize problem, but there is still some kind of race between google services and cloud-init.  I suspect it's over networking availability.  Attempting to duct-tape in an alternate cloud-init unit file.

:cry: nope, still didn't get it, cloud-seems more broken.

Okay, I think I got it finally...

...confirmed, probably fixed (based on 4/4 positive builds)

/hold cancel

disk space problem is fixed, but testing on F30 is failing (seems legit breakage).

vfs driver does not support mount options

Yeah, are people actually aware of this? It caused me a lot of grief with my skopeo tests. Basically, it means "you have to comment out the mountopt line in /etc/containers/storage.conf"

@edsantiago You mean mountopt = "nodev"?

@rhatdan It sounds like the default storage.conf is incompatible with VFS?

You mean mountopt = "nodev"?

Yes. Any attempt to use vfs fails unless you also delete or comment out that line.

@edsantiago thanks for jumping in on the failure cause.
Rebased this against #3239 to help confirm that works in F30 (here)

We could make podman smart enough to handle this, or force the user to do
Looks like this might be a bug, if you are just doing --storage-driver=vfs
According to the man pages.
man podman
...
       --storage-driver=value

       Storage driver.  The default storage driver for UID 0 is configured in /etc/containers/storage.conf
       ($HOME/.config/containers/storage.conf in rootless mode), and is vfs for non-root users when
       fuse-overlayfs is not available.  The STORAGE_DRIVER environment variable overrides the default.  The
       --storage-driver specified driver overrides all.

       **Overriding this option will cause the storage-opt settings in /etc/containers/storage.conf to be
       ignored.  The user must specify additional options via the --storage-opt flag.**

According to the last two lines, using a storage-driver should set the storage-opt to ""

Ahh okay there is a --storage-opt that's what Matt and I couldn't find.  In that case, @rhatdan fix in #3240 is the correct behavior.   I rebased this PR against Dan's fix PR, let's see if that gets us green CI...

Rebased against #3272 early, assuming it merges will make final testing here go faster.

/approve

/hold

/hold cancel

sigh I'm my own worst enemy...an image-changing PR merged: Need to rebuild and re-test images here, again.

/hold cancel

sigh conflicted on .cirrus.yml again.
Need to re-roll F30 images up again to grab @haircommander $CONMON_COMMIT update.
/hold

sorry @cevich !

@haircommander lol no worries, I've done this to myself about 50 times so far on this PR.  There are also a number of flakes/issues related to F30 so it's no biggie (chicken-and-egg problem of not having F30 in CI...but also blocking F30 testing in CI).

/hold cancel

This LGTM, but only on Monday. Let's not make any CI changes on a Friday, heh.

This LGTM, but only on Monday. Let's not make any CI changes on a Friday, heh.

:+1:
'cept I won't be here next week.
Also, at this late-stage, this PR may need to be manually merged as there's a bit of a catch-22:

We have current issues that affect F30 (blocking merge of this PR)
Not having F30 in CI is allowing new issues to merge in undetected

I'll monitor this in case a re-run can fix a test flake, otherwise the above will only get worse with time :confounded:

/lgtm


Add missing parenthesis

Fix Python SyntaxError by adding missing parenthesis!
Pls merge 🥺

Thank you for submitting this PR, and well-done for completing the Git workshop!


Make static binary CI integration test more reliable

Using the github flake input scheme such as with mach-nix often hits GitHub's API rate limit.
This can be avoided by exposing an environment with the dependencies for the integration tests as a dedicated shell output.

[x] Verify that CI passes.

Added a small improvement so we don't have to build our own version of pyarrow. But then I realized that we're using arrow 10. Which hasn't landed on nixpkgs master yet. The improvement is still worthwhile, so let's wait for the rebuild.

I enabled auto-merge here since this was really annoying today and shouldn't be blocking further work while most of everyone is on vacation.


PHOENIX-7402: Fix row getting expired partially even if updated within TTL

The issues that were identified:

The empty cells are not being persisted/collected during flushes and minor compactions which causes row to expire partially on next major compaction even if it was updated within TTL.
Removed preFlush hook from using CompactionScanner as we would need to retrieve PTable object in preFlush to pass onto CompactionScanner to determine the max lookback age and empty column family. As we need to use latest max lookback age always so, we would need to retrieve PTable by bypassing client cache and make RPC to SYSCAT RS.
For multi-column family, we need to handle the case that during major compactions we can be needed to retain empty column cells to close the gap b/w empty CF and non-empty CF. To know minimum number of empty column cells to retain for this purpose we need to do region level scan.
For minor compactions, because actual TTL is not known as getting View level TTL requires running queries on SYSCAT thus, we retain the empty cells which can't be safely discarded.

@kadirozde @virajjasani @tkhurana @jpisaac The PR is ready for review. Please review.
I plan to follow-up with a PR to avoid doing region level scan when major compacting empty CF of a multi-CF table. I have thought of an approach but need to do its feasibility analysis and get it more concrete so, maybe first we can merge this PR and then next I can follow-up with optimization. Thanks

@kadirozde @virajjasani @tkhurana @jpisaac The PR is ready for review. Please review.
I plan to follow-up with a PR to avoid doing region level scan when major compacting empty CF of a multi-CF table. I have thought of an approach but need to do its feasibility analysis and get it more concrete so, maybe first we can merge this PR and then next I can follow-up with optimization. Thanks

Sounds good.


Added Default favicon

I added a default favicon in the static folder. Let me know if this is the right one or if I added it correctly. Thanks!
This is related to this issue: https://github.com/CTFd/core-beta/issues/8

Added img folder to assets folder.
Configured Vite to copy the contents of img folder to static/assets folder.
Modified <Link/> href to look into /static/assets folder.

Verified if it is really looking into the intended folder to look into, which should be /themes/core-beta/static/assets/favicon.ico, by inserting a JS script in base.html and letting flask-jinja render it

The static files I don't think should have been deleted from here. Can you put them back?

Yeah I noticed that too. But I think it happens when vite recreates those static files, it creates a new hash on its name. So git thinks that it has been deleted I think. Not really sure, but I'll restore it instead.

This isn't right because you can't override it from the Admin Panel.
See https://github.com/CTFd/CTFd/blob/master/CTFd/themes/core/templates/base.html#L7.


Fixing layout of change commodity codes popup

Fields were misaligned horizontally.
Changed structure so they align

 [DIT] Bulk Edit - popups - commodity code (5.5)


is pattern matching does not work in conditional matching

This code should return false,
load "io".

function filter
    with ([x:%string, y:%string, z:%string]) %if x is z do
        return true.
    orwith _ do
        return false.
    end

print (filter ["a","b","c"]).

but it returns true so there is a problem with the conditional pattern match on strings.  The workaround is to replace the is operator with ==.

I may be a little confused here, but in this case you're treating z as a pattern, therefore shouldn't it need to be dereferenced?
For example, the following code works correctly:
load "io".

let x = "asteroid".
let y = ".*q.*".
let z = ".*a.*".

println(x is *z). -- prints "true"
println(x is *y). -- prints "false"

by extension, changing the conditional in the original snippit to %if x is *z do seems to fix the issue.
load "io".

function filter
    with ([x:%string, y:%string, z:%string]) %if x is *z do
        return true.
    orwith _ do
        return false.
    end

println (filter ["a","b","c"]). -- prints "false"
println (filter ["a","b","a"]). -- prints "true"

YES!!!!! It should be treated as a pattern not just a variable. Nice catch.  Feel free to close this (non-)issue :)

Oh fantastic! I'll close this.

That's strange. It seems to show up for me.
[image: image.png]
On Tue, May 25, 2021 at 7:12 AM Lutz Hamel @.***> wrote:

Weird, why doesn't this show up in the "closed issues" list for asteroid in
GitHub? Does anybody have any ideas?
Thanks,
Lutz
On Mon, May 24, 2021 at 8:07 PM Oliver Wendell McLaughlin <
@.***> wrote:

Closed #28 https://github.com/lutzhamel/asteroid/issues/28.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/lutzhamel/asteroid/issues/28#event-4789359492, or
unsubscribe
<
https://github.com/notifications/unsubscribe-auth/ADXERTZLVFBTB55WCKE4CITTPLS35ANCNFSM4TJDZURA
.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_lutzhamel_asteroid_issues_28-23issuecomment-2D847778904&d=DwMFaQ&c=dWz0sRZOjEnYSN4E4J0dug&r=KZrQclaD9arg93gbt2wrckCB_mO6B2xpiHjS6KBN-yI&m=iQnziexpMiZkpkT7uit5Eitl5Uz4UY24iXTSoIibbtg&s=itWA0C0tIuc2BT6cj1CsqWE3k8lOruQ_XsAz-RsFm-0&e=,
or unsubscribe
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_ALHRDMBRWOJZMCNJHKLKUDLTPOAZHANCNFSM4TJDZURA&d=DwMFaQ&c=dWz0sRZOjEnYSN4E4J0dug&r=KZrQclaD9arg93gbt2wrckCB_mO6B2xpiHjS6KBN-yI&m=iQnziexpMiZkpkT7uit5Eitl5Uz4UY24iXTSoIibbtg&s=IvYc8d0fzDsJHpxfrw5H20gplStuTgjIpuHlrQ688qw&e=
.

--
Timothy Colaneri, B.S.
Teaching Assistant
Dept. of Computer Science and Statistics
University of Rhode Island

I believe closed issues are still sorted by “Date opened” as opposed to “Date closed”. I see the issue in the closed tab, it’s just farther down.


♻ Who is on client work - Add authentication to prevent external access

Cc: @pierssinclairssw @adamcogan

Hi @ravidhaduk
Pain

As per our conversation, the response for query "Who is on client work" has a Clients column to list client names, which is confidential.
What code could be improved?

Authentication against external users should be implemented on this query.
Tasks

[ ] Add authentication for this command to prevent external users from getting the entire response

Screenshots

Figure: The main content on the response is client names
Definition of Done

[ ] All tasks are updated and closed
[ ] No high priority defects/bugs are on that user story
[ ] Code reviewed by one other team member (e.g. Checked by Bill)
[ ] All acceptance criteria have been met
[ ] Deployed to Dev
[ ] (If implemented) Pass automated UI testing
[ ] (If not implemented above) Do a manual test on all supported commands (at least one for each LUIS intent) against Dev
[ ] Complex code is documented (removing technical debt)
[ ] Deployed to Production
[ ] Add description about the changes for the PBI
[ ] Tick off the definition of done tasks in the PBI
[ ] (Optional) A Done Video, particularly for PBI with multiple stages

Thanks!

Duplicate of https://github.com/SSWConsulting/SSW.SophieBot/issues/485#issuecomment-1086974688. Closing


Disable iskra crossmint

Description

Remove Iskra Crossmint ID
Don't show the Crossmint button in Bridging > Not Started

Review Error for lauchness @ 2023-08-27 17:31:56 UTC
User failed mfa authentication, public email is not set on your github profile. see go/mfa-help


Run CI on x64 as well as arm64

At the moment the CI is only run on x64 architecture which should cover most development machines. However the Jetson devices run a arm64 CPU and are therefore not covered. To verify that there is no hidden platform dependency we should run on arm64 as well.
See also https://github.com/actions/setup-node

Turns out that running on arm64 is not possible at the moment (unless we go for self hosted runners). Therefore I will close this issue for now.
See also https://github.com/opendatacam/opendatacam/pull/341#issuecomment-749502480


Changes from update to Kivy 1.9

After updating to Kivy 1.9, kivy3 cameras are more zoomed in than they were in 1.8. Is there a quick alteration to kivy3 that I can make, or is there an update to kivy3 coming? In my case, I have the cameras moving around, and then I use the modelview and projection matrices to approximate 3d touch locations. I assumed that repositioning the camera would correct the zoom issue, but this caused problems with getting touch locations.

Hey. Haven't been working under project for a long-long time. Just launched it with kivy 1.9, everything looks neat as for me. That would be cool if you provide some detailed description of the problem, screenshots etc.


Feature/popup/confirm payment UI

Confirming payment

Update

Saving budget

I think that bolt11.js file is not used?

Forgot to remove it
Github delete file is not working from the UI, will do a commit later

@bumi is there anything left to be done on this?

ah, I think I missed your updates. I guess then feel free to merge it.


Bump packaging from 22.0 to 23.0 (#5336)

Pull request opened by the merge tool on behalf of #5336

Merged in d68be7f97ef8bf47abb381a74808a01ab7ed7a2e


Feature: add validation for contract definition id

What this PR changes/adds
Add validation for contract definition id
Why it does that
Validation of contract definition id by creation solves the problem in negotiation process when the id is not valid.
Further notes
Marking jersey-bean-validation helps for the correct validation of parameters.
Linked Issue(s)
Closes #1347
Checklist

[x] added appropriate tests?
[x] performed checkstyle check locally?
[x] added/updated copyright headers?
[x] documented public classes/methods?
[x] added/updated relevant documentation?
[x] added relevant details to the changelog? (skip with label no-changelog)
[x] formatted title correctly? (take a look at the CONTRIBUTING and styleguide for details)

Codecov Report

Merging #1372 (d59ed1d) into main (e4735bc) will decrease coverage by 56.20%.
The diff coverage is 0.00%.

@@              Coverage Diff              @@
##               main    #1372       +/-   ##
=============================================
- Coverage     67.60%   11.40%   -56.21%
- Complexity        0      488      +488
=============================================
  Files           716      717        +1
  Lines         15858    15889       +31
  Branches       1041     1041
=============================================
- Hits          10721     1812     -8909
- Misses         4663    13972     +9309
+ Partials        474      105      -369

Impacted Files
Coverage Δ

...spaceconnector/common/validator/UuidValidator.java
0.00% <0.00%> (ø)

...ontractdefinition/model/ContractDefinitionDto.java
0.00% <ø> (-100.00%)
:arrow_down:

.../eclipse/dataspaceconnector/spi/result/Result.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...eclipse/dataspaceconnector/spi/result/Failure.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...clipse/dataspaceconnector/spi/query/SortOrder.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...dataspaceconnector/spi/observe/ObservableImpl.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...paceconnector/common/stream/PartitionIterator.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...paceconnector/spi/command/BoundedCommandQueue.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...connector/boot/util/CyclicDependencyException.java
0.00% <0.00%> (-100.00%)
:arrow_down:

.../dataspaceconnector/iam/daps/DapsJwtDecorator.java
0.00% <0.00%> (-100.00%)
:arrow_down:

... and 476 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update e4735bc...d59ed1d. Read the comment docs.

Hi @paullatzelsperger the idea to validate the contractDefinitionId against the UUID was coming from @jimmarino please see the comments in issue #1347, maybe he has a reason why to use UUID. Otherwise I can revert the PR and check only if the ID contains any ":".

Hi @paullatzelsperger the idea to validate the contractDefinitionId against the UUID was coming from @jimmarino please see the comments in issue https://github.com/eclipse-dataspaceconnector/DataSpaceConnector/issues/1347, maybe he has a reason why to use UUID. Otherwise I can revert the PR and check only if the ID contains any ":".

@jimmarino never said to validate against a UUID, or a GUID.

Hi @paullatzelsperger the idea to validate the contractDefinitionId against the UUID was coming from @jimmarino please see the comments in issue #1347, maybe he has a reason why to use UUID. Otherwise I can revert the PR and check only if the ID contains any ":".

@jimmarino never said to validate against a UUID, or a GUID. Using a UUID is what we recommend, to ensure a high level of uniqueness, but APIs should never be opinionated like that unless there is a technical reason.

My understanding from his comment "The id should be a GUID (not URN) so +1 on adding validation in the API. ..." was that the id should be a GUID and should be validated in the API :-) But as I said if there are no special reason to use UUID of course I will remove the UUID validation and only check if id contains a ":"

But as I said if there are no special reason to use UUID of course I will remove the UUID validation and only check if id contains a ":"

@paullatzelsperger @jimmarino @tuncaytunc-zf Do we have to look also for other chars which should't be part of the ID?

But as I said if there are no special reason to use UUID of course I will remove the UUID validation and only check if id contains a ":"

@paullatzelsperger @jimmarino @tuncaytunc-zf Do we have to look also for other chars which should't be part of the ID?

none that I can think of, from a technical perspective.

Hi @paullatzelsperger the idea to validate the contractDefinitionId against the UUID was coming from @jimmarino please see the comments in issue #1347, maybe he has a reason why to use UUID. Otherwise I can revert the PR and check only if the ID contains any ":".

@jimmarino never said to validate against a UUID, or a GUID. Using a UUID is what we recommend, to ensure a high level of uniqueness, but APIs should never be opinionated like that unless there is a technical reason.

My understanding from his comment "The id should be a GUID (not URN) so +1 on adding validation in the API. ..." was that the id should be a GUID and should be validated in the API :-) But as I said if there are no special reason to use UUID of course I will remove the UUID validation and only check if id contains a ":"

I think this PR should be about 1-3 lines of code. We don't need to drag in validation dependencies into the core.

Will close this PR and implement just to check if the id contains any ":".


using inherits intead of util

See rdf-ext/rdf-ext#61

Test failed, but this is a problem of the folder-to-rdf dependency (0.3.0 -> 0.2.0). This must be fixed in another PR. The changes are straightforward, so merged it anyway.


Migrate relevant functionality from test262-parser.

This intentionally omits the changes necessary for hashbang. Once this work is complete, I will call on @adrianheine to apply their changes here, instead of test262-parser.
This updated changeset includes @adrianheine's latest work from test262-parser

@jugglinmike please hold off on merging this, I need to verify the contents property contains all of the expected test source code when handling hashbang tests

@rwaldron This made me think that an update to Test262's INTERPRETING.md was in order, but I don't think that's true because all of the relevant tests in Test262 have been authored to use the raw frontmatter flag.
That's good news for me because I was having a heck of a time writing clear instructions for Test262 consumers. I think it might also mean we can simplify your work here. We don't have to support rebuilding test code to wrangle the hashbang sequence with, e.g. includes and directive prologues. We just have to make sure the metadata is correctly parsed in tests that use a hashbang.
Does that sound right to you?

@jugglinmike I've removed the content normalization code and removed the tests that relied on that normalization. I've kept one test that documents the expected behavior—let me know if you want that removed as well.

@jugglinmike I've squashed 7 commits into 2. This is ready to go when you are. If we could get a release out today, that would be very cool :D

Rebased!

Nice work, Rick

(Tagged as v1.2.1 and published to npm)


send emails over SSL port 465

Can I send emails using the 465 port? I al ready have ssl certificate (comodo) also I have specified the ssl certificates manually in the docker compose file, now i can send emails using the port 587/25 with tls encryption but the ssl /465 port dont works.
Also for email clients I only able to use tls, how i can use ssl porperly?
what can i do?

I believe you cannot do it until #595 lands, or you have to build your own image (which is not that hard) to overwrite master.cf.
You need to add something like
smtps     inet  n       -       n       -       -       smtpd
  -o smtpd_tls_wrappermode=yes
  -o smtpd_sasl_auth_enable=yes

The only way to do it right now is to monkey-patch the master.cf file after container creation.
As @arneke mentioned, #595 adds support for this, however it won't get merged until I'm done making unit tests for it (However, I've run my private mailserver with the #595 patch for a month now, without problems, so it should work fine)

I've tried using @MadsRC's #595 to enable tls on port 465.
Using the configuration posted above I get this warning:
postconf: warning: unmatched request: "smtps     inet  n       -       n       -       -       smtpd"

Is this because you're parsing the script line by line?

@gustavotero7 @0xQSL I just created a PR #709 for this feature.
Waiting for @tomav to review and comment on it.

Merged, image building.


Add APCu stubs

see https://youtrack.jetbrains.com/issue/WI-28823
Can send photo of CLA, but where?

scan and email to<EMAIL_ADDRESS>

We've received the CLA. Thanks.

so that, when will pr have merged?

+1, need this as well. Please merge!

@klikh is there some plans to merge this for the next PhpStorm version ?


left_sidebar: Explicitly handle clicks on collapsible Views targets.

This simplifies the click-handler for expanding and collapsing the Views area by naming the two targets--the icon, and the heading--meant to handle expansion or collapse.
CZO discussion
Screenshots and screen captures:

Self-review checklist

[x] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[x] Explains differences from previous plans (e.g., issue description).
[x] Highlights technical choices and bugs encountered.
[x] Calls out remaining decisions and concerns.
[x] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[x] Each commit is a coherent idea.
[x] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[x] Visual appearance of the changes.
[x] Responsiveness and internationalization.
[x] Strings and tooltips.
[x] End-to-end functionality of buttons, interactions and flows.
[x] Corner cases, error conditions, and easily imagined bugs.

This is a lot easier to follow, thanks!


Sample configuration for IBMBlockCSI is outdated

I found several issues while trying to deploy it:

the default registry uses k8s.gcr.io, which has frozen for over a year
the image versions are outdated, some by a few patches like csi-node-driver-registrar and some several major versions like csi-provisioner

I could find no documentation about which versions of these images this project is compatible with, but we can hardly leave them on outdated versions forever. Could some documentation about this be added?

hi @bh-tt , not quite sure what you mean
we have several sidecars configured which are indeed hosted on k8s.gcr.io, but the operator is hosted on registry.connect.redhat.com and the subcomponents (driver and node) are hosted on quay.io
regarding the sidecar versions, we review the versions and update them from time to time as part of major releases only.
the current versions are those that the current release of the operator was tested and qualified for.

The k8s.gcr.io has been frozen for a while now, so it might be good to update those domains to the new domain.
Thank you for the response about the sidecar versions though, we will try to keep up with the sidecar versions as you update them.

thank you @bh-tt for raising this issue. we will be sure to update the sidecar registry to the new one, and try to update the sidecar versions themselves in the next major release

for future reference - https://kubernetes-csi.github.io/docs/sidecar-containers.html (links from this page point to new container registry and the latest versions)

fixed as part of 89cab99183207a52e14a8705565f02136c4851fa (next 1.12.0 release)


[Kubernetes - Windows Worker] default 2016-Datacenter-with-Containers image does not work with k8s 1.6

Is this a BUG REPORT or FEATURE REQUEST? (choose one):
BUG REPORT
Orchestrator and version (e.g. Kubernetes, DC/OS, Swarm)
deploy Kubernetes 1.6.2 with CLI
(Hybrid) deployment for Windows: master is Linux and agent is Windows
What happened:
I have deployed a Kubernetes (Hybrid) deployment for Windows with 1.6.2 with default 2016-Datacenter-with-Containers image in ARM template:
"agentWindowsPublisher": "MicrosoftWindowsServer",
"agentWindowsOffer": "WindowsServer",
"agentWindowsSku": "2016-Datacenter-with-Containers",
"agentWindowsVersion": "2016.127.20170411",
And then I am getting following error when deploy microsoft/aspnet on k8s cluster with "kubectl run aspnet --image microsoft/aspnet"
kubectl describe pod aspnet-xxx
Events:
FirstSeen     LastSeen        Count   From                    SubObjectPath   Type            Reason          Message

1m            1m              1       default-scheduler                       Normal          Scheduled       Successfully assigned iis-3512527085-gd346 to 29884acs9000
1m            1s              6       kubelet, 29884acs9000                   Warning         FailedSync      Error syncing pod, skipping: failed to "StartContainer" for "POD" with RunContainerError: "runContainer: docker: failed to parse docker version "17.03.1-ee-3": illegal zero-prefixed version component "03" in "17.03.1-ee-3""
What you expected to happen:
aspnet should work well on Windows agent
How to reproduce it (as minimally and precisely as possible):

deploy a Kubernetes (Hybrid) deployment for Windows with 1.6.2 with default 2016-Datacenter-with-Containers image in ARM template:
"agentWindowsPublisher": "MicrosoftWindowsServer",
"agentWindowsOffer": "WindowsServer",
"agentWindowsSku": "2016-Datacenter-with-Containers",
"agentWindowsVersion": "2016.127.20170411",
kubectl run aspnet --image microsoft/aspnet
kubectl describe pod aspnet-xxx

Anything else we need to know:
I have tested, 2016-Datacenter-with-Containers image version "2016.127.20170406" works well.

Please update to latest acs-engine. We have merged a fix for this. Though 1.6.2 is still having some issues.

Okay we patched our k8s zip file for windows and the latest acs-engine should work with 1.6.2 as well. Can you test and verify it is fixed @andyzhangx ?

@JackQuincy It's working now, thanks. I will close this issue.


Allow different cell types on the same CollectionView

There are a lot of use cases where not every item in a list has the same basic layout. For example your first or last item may allow adding/removing/frefresh, or you may have in-between headings. It might also be nice to have the last heading stay fixed on top of the List.
Note that it is not a good solution to build your own List to achieve these effects. I tried, but iOs get's VERY slow after just a few dozend items. See http://floriankugler.com/blog/2013/4/21/auto-layout-performance-on-ios

Here's a draft for a protocol change to implement cell types:
Native Bridge Protocol
In order to create the right number of items for different types, the native clients have to request the type for each item. For proper layouting, they also need to know the height of every item. They do so by sending an event named requestCellDescription with an index parameter that contains the index of the item which description is requested.
The JS side “answers” by sending a call operation describeCell with parameters index, type, and height. The type is represented by a sequentional integer number, starting from 0. If the JS side does not answer during the event processing, the native clients must fall back to 0 for the type and to the CollectionView's itemHeight property for the height.
When creating new reusable items, the native clients must specify the cell type by adding a parameter type to the createItem event.

Two issues with the current names:

events in Tabris.js are all lowercase, we should stick to this scheme
the current CollectionView protocol uses the term "item" instead of "cell"

Therefore I'd suggest to rename:

requestCellDescription to requestinfo
describeCell to describeItem

requestinfo all lower case? Or camelCase?

+1 for "item" name but juding from the above comment the decribeItem should be describeitem.

@jordiboehmelopez All events in Tabris.js are lowercase for compatibility with DOM events.

@mpost describeItem is a call, not an event. Those are usually camelCase.

makes sense i guess.

Renamed as suggested in the latest patch set of the draft in Gerrit https://gerrit.eclipsesource.com/#/c/5337/


Create graph repository

Acceptance criteria : should be able to perform basic crud operations.

I will start working on this.


colors.png image is missing

The markItUp plugin supports color selection in the BBCode example, but the icon 'colors.png' file is mission from the gem.

Nevermind. I didn't read far enough. For anyone else searching, the color palette in BBCode is actually an 'addon' that is downloaded separately from the core package.


Benchmarking Output Tokenizer

Summary

Add more tests to OutputTokenizer and benchmark.

Ticket:
What's Changed

Added

[x] add more tests for OutputTokenizer regexs
[x] add benchmark (using cargo bench)

benchmark result on M1 Max MacBook Pro with 1TB SSD and 32GB Unified Memory

test result: ok. 0 passed; 0 failed; 45 ignored; 0 measured; 0 filtered out; finished in 0.00s

     Running unittests src/main.rs (target/release/deps/wukong-ccf4d765631215d2)

running 0 tests

test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s

     Running benches/output_tokenizer_benchmark.rs (target/release/deps/output_tokenizer_benchmark-e4dc1219423a4b01)
tokenize long sentence  time:   [63.259 µs 63.436 µs 63.609 µs]
                        change: [-5.0021% -4.7469% -4.4920%] (p = 0.00 < 0.05)
                        Performance has improved.
Found 2 outliers among 100 measurements (2.00%)
  2 (2.00%) high mild

tokenize table output   time:   [98.439 µs 98.473 µs 98.505 µs]
                        change: [-6.8680% -6.5873% -6.3279%] (p = 0.00 < 0.05)
                        Performance has improved.
Found 7 outliers among 100 measurements (7.00%)
  2 (2.00%) high mild
  5 (5.00%) high severe

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: jk-gan
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

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

Benchmarking from Macbook Pro with Intel Core i5, 16GB Ram and 512G SSD.
test result: ok. 0 passed; 0 failed; 45 ignored; 0 measured; 0 filtered out; finished in 0.00s

     Running unittests src/main.rs (target/release/deps/wukong-e6506fbaebb03225)

running 0 tests

test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s

     Running benches/output_tokenizer_benchmark.rs (target/release/deps/output_tokenizer_benchmark-a51cafe09ceefee9)
tokenize long sentence  time:   [178.68 µs 179.59 µs 180.82 µs]
                        change: [-36.761% -31.450% -25.845%] (p = 0.00 < 0.05)
                        Performance has improved.
Found 10 outliers among 100 measurements (10.00%)
  2 (2.00%) high mild
  8 (8.00%) high severe

tokenize table output   time:   [214.95 µs 216.27 µs 218.08 µs]
                        change: [-5.4642% -3.0993% -0.1451%] (p = 0.02 < 0.05)
                        Change within noise threshold.
Found 11 outliers among 100 measurements (11.00%)
  6 (6.00%) high mild
  5 (5.00%) high severe

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: jk-gan, onimsha
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

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

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: jk-gan
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

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

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: jk-gan
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

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

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: jk-gan, onimsha
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

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

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: jk-gan
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

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

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: jk-gan
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

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

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: jk-gan, onimsha
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

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


[only v1.12.13+hotfix.3] Tapping with more than one finger (quickly) results in exception

How to reproduce:

Setup GestureDetector
Listen on tapUp
Quickly drum the tap area with more than one finger (not simultaneous tap but intermittent like for example index - middle - index - middle ... finger)

NOTE: Even though the drumming gesture is not common it can easily happen by misstake - that is how I found it on a normal tap area.
Easily reproducible on both Android and iOS:
import 'package:flutter/material.dart';
import 'package:flutter/widgets.dart';

void main() {
  runApp(MaterialApp(
    builder: (context, child) {
      return Tapper();
    },
  ));
}

class Tapper extends StatefulWidget {
  Tapper({Key key}) : super(key: key);

  @override
  State<StatefulWidget> createState() => _TapperViewState();
}

class _TapperViewState extends State<Tapper> {
  int _currentIndex = 1;

  @override
  Widget build(BuildContext context) {
    return Material(
      child: GestureDetector(
        onTapUp: (TapUpDetails details) => _onTapUp(context),
        child: ListView.builder(
          padding: const EdgeInsets.all(20),
          itemCount: _currentIndex,
          itemBuilder: (_, int index) {
            return Text(
              'MSG $index',
              textAlign: TextAlign.center,
              style: TextStyle(
                color: Colors.red,
              ),
            );
          },
        ),
      ),
    );
  }

  void _onTapUp(BuildContext context) {
    setState(() {
      _currentIndex++;
    });
  }
}

The error:
I/flutter ( 7522): NoSuchMethodError: The getter 'position' was called on null.
I/flutter ( 7522): Receiver: null
I/flutter ( 7522): Tried calling: position
I/flutter ( 7522):
I/flutter ( 7522): #0      Object.noSuchMethod (dart:core-patch/object_patch.dart:53:5)
I/flutter ( 7522): #1      TapGestureRecognizer.handleTapDown (package:flutter/src/gestures/tap.dart:457:28)
I/flutter ( 7522): #2      BaseTapGestureRecognizer._checkDown (package:flutter/src/gestures/tap.dart:256:5)
I/flutter ( 7522): #3      BaseTapGestureRecognizer.didExceedDeadline (package:flutter/src/gestures/tap.dart:227:5)
I/flutter ( 7522): #4      PrimaryPointerGestureRecognizer.didExceedDeadlineWithEvent (package:flutter/src/gestures/recognizer.dart:493:5)
I/flutter ( 7522): #5      PrimaryPointerGestureRecognizer.addAllowedPointer.<anonymous closure> (package:flutter/src/gestures/recognizer.dart:446:40)
I/flutter ( 7522): #6      _rootRun (dart:async/zone.dart:1122:38)
I/flutter ( 7522): #7      _CustomZone.run (dart:async/zone.dart:1023:19)
I/flutter ( 7522): #8      _CustomZone.runGuarded (dart:async/zone.dart:925:7)
I/flutter ( 7522): #9      _CustomZone.bindCallbackGuarded.<anonymous closure> (dart:async/zone.dart:965:23)
I/flutter ( 7522): #10     _rootRun (dart:async/zone.dart:1126:13)
I/flutter ( 7522): #11     _CustomZone.run (dart:async/zone.dart:1023:19)
I/flutter ( 7522): #12     _CustomZone.bindCallback.<anonymous closure> (dart:async/zon

Flutter doctor output:
[✓] Flutter (Channel beta, v1.12.13+hotfix.3, on Mac OS X 10.15.1 19B88, locale en-SE)
    • Flutter version 1.12.13+hotfix.3 at /Users/fredrik.dahlen/DEV/flutter
    • Framework revision 57f2df76d7 (4 days ago), 2019-12-05 21:23:21 -0800
    • Engine revision ac9391978e
    • Dart version 2.7.0

[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
    • Android SDK at /Users/fredrik.dahlen/Library/Android/sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-29, build-tools 29.0.2
    • ANDROID_HOME = /Users/fredrik.dahlen/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b49-5587405)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 11.2.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 11.2.1, Build version 11B500
    • CocoaPods version 1.8.4

[✓] Android Studio (version 3.5)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 42.0.1
    • Dart plugin version 191.8593
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b49-5587405)

[✓] VS Code (version 1.35.0)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.1.0

[✓] Connected device (3 available)
    • SM G930F                  • 988673304b32425853                       • android-arm64 • Android 8.0.0 (API 26)
    • Android SDK built for x86 • emulator-5554                            • android-x86   • Android 10 (API 29) (emulator)
    • Fredrik’s iPhone          • f6414d51c92a4d1e13c55cc0b2b04547651d022b • ios           • iOS 13.1.3

• No issues found!

Very likely related to:
https://github.com/flutter/flutter/issues/44144
But completely different way of provoking the error.

Hmm.
More investigating lead me to:
https://github.com/flutter/flutter/pull/45943
Seems to fix the issue.
Not able to reproduce this on Master channel.
@dkwingsmt How will this fix propagate down the channels?

Tested with master works as intended

flutter doctor -v
[√] Flutter (Channel master, v1.13.1-pre.80, on Microsoft Windows [Version 10.0.19013.1122], locale en-US)
    • Flutter version 1.13.1-pre.80 at C:\src\flutter
    • Framework revision 2fe9623c36 (2 hours ago), 2019-12-10 04:22:32 -0500
    • Engine revision 12bf95fd49
    • Dart version 2.7.0 (build 2.7.0-dev.2.1 8b8894648f)

[√] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
    • Android SDK at C:\Users\iapic\AppData\Local\Android\sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-29, build-tools 28.0.3
    • Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b03)
    • All Android licenses accepted.

[√] Chrome - develop for the web
    • Chrome at C:\Program Files (x86)\Google\Chrome\Application\chrome.exe

[√] Android Studio (version 3.5)
    • Android Studio at C:\Program Files\Android\Android Studio
    • Flutter plugin version 41.1.2
    • Dart plugin version 191.8593
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b03)

[√] VS Code, 64-bit edition (version 1.40.2)
    • VS Code at C:\Program Files\Microsoft VS Code
    • Flutter extension version 3.7.0

[√] Connected device (3 available)
    • Pixel 3a   • 965AY0WP5C • android-arm64  • Android 10 (API 29)
    • Chrome     • chrome     • web-javascript • Google Chrome 78.0.3904.108
    • Web Server • web-server • web-javascript • Flutter Tools

• No issues found!

@iapicca Should I close the issue?

Hi @ninnepinne
I'd keep it open for now, until the fix propagates;
I'll try to remember to check when the new release is out.
thanks for your efficiency

CC @dkwingsmt

I believe it should be fixed by that PR. I’m not familiar with our hotfix policy though, cc @Hixie

[√] Flutter (Channel stable, v1.12.13+hotfix.5, on Microsoft Windows [Version 10.0.16299.1296], locale zh-CN)
    • Flutter version 1.12.13+hotfix.5 at C:\ProgramFile_Developer\flutter
    • Framework revision 27321ebbad (2 weeks ago), 2019-12-10 18:15:01 -0800
    • Engine revision 2994f7e1e6
    • Dart version 2.7.0

have the same problem

[√] Flutter (Channel stable, v1.12.13+hotfix.5, on Microsoft Windows [Version 10.0.16299.1296], locale zh-CN)
    • Flutter version 1.12.13+hotfix.5 at C:\ProgramFile_Developer\flutter
    • Framework revision 27321ebbad (2 weeks ago), 2019-12-10 18:15:01 -0800
    • Engine revision 2994f7e1e6
    • Dart version 2.7.0

have the same problem

Have u solve it, v1.12.13+hotfix5 Same problem

@adigest @JohnSnooow
Beta channel v1.12.13+hotfix6 does not have this problem.
Let's hope hotfix6 reaches stable channel soon...

I'm going to close this issue, since it has been fixed (https://github.com/flutter/flutter/issues/46668#issuecomment-572651497).


RISC-V ISA Formal Specification as target

For reference: RISC-V ISA Formal Specification
The test environment is provided inside the target directory.
Suites rv32i, rv32ua, rv32uc, rv32uf, and rv32ui are currently supported by the formal model. Some tests in rv32i will not pass due to their usage of privileged CSRs (not yet implemented in the formal model).

Thanks for this Deborah.  I'm hoping someone else will review this - I'm outside my area of confidence.  Because I've merged two other commits, this pull request now has conflicts.  You should be able to resolve these by rebasing your branch on master and dealing with the conflicts. Almost certainly in the ChangeLog files, since git seems always to make a mess of these.

The dir name of the target/device needs to be more than just eg 'formal', it needs be something like SiFive_ISA_formal or something... so that it is distinguishable from the other 5 formal models...

Thanks for pointing that out, @simon5656! I've renamed it now.

Gah - we have conflicts again. Could you rebase and I'll merge it. Thanks

@jeremybennett done! Thanks for your help as always :)


Lesters/short tensor format as default

@bratseth Please review. Same as PR that was on 8 branch, but this includes a test on document/v1

👍


getPurchaseHistory() and getAvailablePurchases() are not resolved / rejected

Version of flutter_inapp_purchase
5.3.1
Platforms you faced the error (IOS or Android or both?)
both
Expected behavior
request should be resolved/rejected
Actual behavior
request not being resolved/rejected
Tested environment (Emulator? Real Device?)
Emulator and Real Device
Steps to reproduce the behavior
final history = await _iap.getPurchaseHistory();
final purchases = await _iap.getAvailablePurchases();
Similar issue
I think it is same issue as in React native this

The same problem on iPhone 14 ios 16.0 simulator, but on iPhone 8 ios 12.4 simulator it works

Same issue here and it appears to be happening only in sandbox environment. It works on our production build on iOS 15 & iOS 16 but not on the development build in sandbox environment on iOS 16.
I wrote a race condition hack to get around this:
List<PurchasedItem> storePurchases = [];

final result = await Future.any([
  _plugin.getAvailablePurchases(),
  Future.delayed(const Duration(seconds: 5))
]);

result != null ? storePurchases = result : storePurchases = [];

But this is still not ideal because you basically cannot retrieve available purchases on iOS 16 at the moment.

I have the same issue on iPhone 12 - iOS 16.
This happens when you are trying to call getPurchaseHistory() and getAvailablePurchases()  on a development build and you don't are not logged in with a sandbox tester account on your device. Looks like the plugin isn't handling the errors and exceptions thrown by the two of above mentioned methods.
I have added a hack to my initializer, basically a race condition that skips this check if it takes too long.
List<PurchasedItem> storePurchases = [];

final result = await Future.any([
  _plugin.getAvailablePurchases(),
  Future.delayed(const Duration(seconds: 5))
]);

result != null ? storePurchases = result : storePurchases = [];

I then went to Settings -> App Store -> Scroll down to "Sandbox Account" and enter your credentials. The methods should work fine then.
If I am understanding this issue correctly, this is impossible to happen on release build on AppStore because the user will be always signed in with his/her Apple ID.

final history = await FlutterInappPurchase.instance
            .getPurchaseHistory()
            .timeout(Duration(seconds: 5), onTimeout: () => []);

is another way to skip


Fix axis label sizes.

Is base_size the answer?
https://stackoverflow.com/questions/14942681/change-size-of-axes-title-and-labels-in-ggplot2
https://ggplot2.tidyverse.org/reference/ggtheme.html

Look at https://github.com/hrbrmstr/hrbrthemes/blob/master/R/ipsum.r for inspiration.


flashSettingsWithTimeout does not override default 10 second timeout

Hi there,
I'm not sure if I'm doing something wrong, but I've looked through the documentation and also tried it with the provided code snippet
let settings = NVFlashSettings.warm().flashSettingsWithTimeout(20000) // in milliseconds
for flashSettingsWithTimeout, and it does not seem to override the default 10 second timeout in the SDK. Here is the code I'm working with:
    var warm:UInt8 = 255;
    var cool:UInt8 = 125
   @IBAction func flashOn(sender:UIButton){
        let flashSettings = NVFlashSettings.customWarm(warm, cool: cool).flashSettingsWithTimeout(30000)
        for flash in appDelegate.flashService.connectedFlashes as! [NVFlash] {
            // toggle flash
            if (!flash.lit) {
                flash.beginFlash(flashSettings)
            } else {
                flash.endFlash()
            }
        }

    }

Any help is much appreciated!

The hardware will automatically shut the light off after a 10 second timeout. This is a safety mechanism in case there phone or Bluetooth stack ever gets in a hung state.
To flash longer than 10 seconds you'll have to periodically reset the timeout by calling beginFlash again. This will keep it lit continuously the most recent beginFlash times out, or a subsequent endFlash.
If your intent is a 20 second flash - this would be fine. However at approximately a minute the hardware starts getting hot and can behave unpredictably as it's only designed for short bursts. Also long flashes drain the battery really quickly.

thanks! this has been informative!


Skip version 2.2.0

We won't be able to publish 2.2.0 to npm, because of: #10

Not required as we will do #63 in the next release.


ZendeskExecution uses an invalid payload

Feature description
Send Zenduty webhook: {"service":"34wkwWLfa6fCacOfxFp7Rz","summary":"Namespace dev, Flow ID hello_zen, Execution ID 34wkwWLfa6fCacOfxFp7Rz, Execution Status SUCCESS. *<http://localhost:5173/ui/executions/dev/hello_zen/34wkwWLfa6fCacOfxFp7Rz|[dev] hello_zen ➛ SUCCESS>*\n> Succeded after 00:00:01.269","title":"Kestra flow failed"}
2023-10-16 21:01:26.022{"error": "Invalid payload"}

@iNikitaGricenko please check again -- I believe we need to use API integration rather than the Incident API for both ZendutyAlert and ZendutyExecution: https://docs.zenduty.com/docs/integrations
this is the best API reference for you: https://docs.zenduty.com/docs/api

Surprisingly, even explicitly overriding the payload doesn't work
id: failure_alert
namespace: dev.monitoring

tasks:
  - id: send_alert
    type: io.kestra.plugin.notifications.zenduty.ZendutyExecution
    url: https://www.zenduty.com/api/events/xxxxxxxxxxxxxxxxx/
    title: "Kestra flow failed"
    executionId: "{{ trigger.executionId }}"
    payload: |
      {
        "alert_type": "critical",
        "message": "Kestra workflow execution {{execution.id}} failed at {{ execution.startDate }}",
        "summary": "Namespace: {{flow.namespace}}\nFlow ID: {{flow.id}}\nExecution ID: {{execution.id}}\nExecution Status: FAILED\n\n[Link to the Execution page](http://localhost:8080/ui/executions/{{flow.namespace}}/{{flow.id}}/{{execution.id}})",
        "entity_id": "{{ execution.id }}"
      }

triggers:
  - id: failed_prod_workflows
    type: io.kestra.core.models.triggers.types.Flow
    conditions:
      - type: io.kestra.core.models.conditions.types.ExecutionStatusCondition
        in:
          - FAILED
          - WARNING
      - type: io.kestra.core.models.conditions.types.ExecutionNamespaceCondition
        namespace: dev
        prefix: true


plt.pcolormesh will infer interval breaks per default

Looking at some warnings in #3266 I saw that matplotlib will deprecate the old behaviour of pcolormesh when the shape of the data and the coordinates are equal (they silently cut a row and a column of the data). With the new behaviour they will interpolate the coordinates.
import numpy as np
import matplotlib.pyplot as plt

x = np.array([1, 2, 3])
y = np.array([1, 2, 3, 4, 5])

data = np.random.randn(*y.shape + x.shape)

f, axes = plt.subplots(1, 2)

for ax, shading, behavior in zip(axes, ["flat", "nearest"], ["old", "new"]):
  ax.pcolormesh(x, y, data, shading=shading, vmin=-0.75, vmax=0.75)
  ax.set_title(f"{behavior}: shading='{shading}'")

This is a good thing in general - we already do this for a long time with the infer_intervals keyword. Unfortunately they don't check if the data is monotonic (matplotlib/matplotlib#18317) which can lead to problems for maps (scitools/cartopy#1638). I don't think there is a need to do something right now - let's see what they think upstream.
This change was introduced in mpl 3.3.0

I have a similar issue with nonmonotonic coordinates (mapping a 2D image to a zenith-azimuth space). Solving this is easy when using Matplotlib's API directly, since I can compute mesh coordinates by myself and supply these as pcolormesh()'s x and y arguments; but I can't inject these into xarray's pcolormesh() function. Wouldn't allowing infer_interval=False and passing ordinary arrays as x and y be a good solution?

I have a similar issue with nonmonotonic coordinates (mapping a 2D image to a zenith-azimuth space). Solving this is easy when using Matplotlib's API directly, since I can compute mesh coordinates by myself and supply these as pcolormesh()'s x and y arguments; but I can't inject these into xarray's pcolormesh() function. Wouldn't allowing infer_interval=False and passing ordinary arrays as x and y be a good solution?

Another consequence is that this example in the docs is now meaningless / misleading. I've just come across the series of discussions in cartopy about this issue - it looks quite complex and I'm also not sure yet what to do in xarray in the mean time.

Wouldn't allowing infer_interval=False and passing ordinary arrays as x and y be a good solution?

I'm not sure what you mean by that? You can always set infer_interval=False at the xarray level?

I'm not sure what you mean by that? You can always set infer_interval=False at the xarray level?

Yes indeed, but you cannot pass Numpy arrays as the x and y parameters to set.


Add Dice Game

Related Issue

Info about Issue or bug

Closes: #[issue number that will be closed through this PR]
Describe the changes you've made
A clear and concise description of what you have done to successfully close your assigned issue. Any new files? or anything you feel to let us know!
Describe if there is any unusual behaviour of your code(Write NA if there isn't)
A clear and concise description of it.
Checklist:

[x] My code follows the style guidelines of this project.
[ ] I have performed a self-review of my own code.
[x] I have commented my code, particularly in hard-to-understand areas.
[ ] I have made corresponding changes to the documentation.
[ ] New and existing unit tests pass locally with my changes.

Screenshots
Put any screenshot(s) of the project here.

Done Mam :)

@iamrishavraj1 You haven't resolved the merge conflicts

@iamrishavraj1 You haven't resolved the merge conflict
Done Mam :)

Mam, Please Review My PR

Project is not visible at main page. Please look into it.
Link the issue no.
Squash the commits.
Let me know if needed any help.


Support for Team Drives

Team Drives is a recent feature for G Suite customers that is exposed through both v2 and v3 APIs, but applications must be enhanced in order to access Team Drives.
The model used by Google in their File Stream product is to have the Google Drive filesystem "root" contain two folders: "My Drive" and "Team Drives". skicka could use the same pattern, but it might be a better idea to add a new command-line option allowing a user to choose which Team Drive to root the [drive_path] argument in, as in skicka ls -t Wicked\ Widgets /Widget_One/

https://developers.google.com/drive/api/v3/enable-teamdrives


Switch go version management to gimme

This implementation aims to be independent of build env updates, although once gimme is shipped with the build image(s) we can then remove the presence check + download.  The disabling of gvm was required in order to have the correct go version activated, which I'm guessing will mean we may have to remove gvm entirely from the build env as well.
It's worth noting that the aliasing logic changes with this PR such that point releases such as 1.0 and 1.3 are now left alone rather than being "upgraded" to 1.0.3 and 1.3.3, respectively.  The reasoning here is that such point releases are legitimate binary releases, whereas version 1.2 will still be "upgraded" to 1.2.2 as there is no 1.2 binary release available (at least in the well-known download locations).
Example build in staging: https://staging.travis-ci.org/travis-repos/go-test-staging/builds/405600

Does this allow for Go tip?
On Sat, Jan 31, 2015 at 11:34 AM, Dan Buch<EMAIL_ADDRESS>wrote:

This implementation aims to be independent of build env updates, although once gimme is shipped with the build image(s) we can then remove the presence check + download.  The disabling of gvm was required in order to have the correct go version activated, which I'm guessing will mean we may have to remove gvm entirely from the build env as well.
It's worth noting that the aliasing logic changes with this PR such that point releases such as 1.0 and 1.3 are now left alone rather than being "upgraded" to 1.0.3 and 1.3.3, respectively.  The reasoning here is that such point releases are legitimate binary releases, whereas version 1.2 will still be "upgraded" to 1.2.2 as there is no 1.2 binary release available (at least in the well-known download locations).
Example build in staging: https://staging.travis-ci.org/travis-repos/go-test-staging/builds/405600
You can view, comment on, or merge this pull request online at:
https://github.com/travis-ci/travis-build/pull/375
-- Commit Summary --

Manage go versions with gimme
Test for existence of gimme executable differently
Try to figure out what's going on with gimme install
Apparently ~/bin does not exist yet (?)
Get more forceful with gvm + enable gimme version via eval
Enable go version prior to PATH and GOPATH settings
Extend condition for go_get_cmd to account for go1
Bump to gimme v0.2.2, omit gvm GOPATH entry
Updates specs per current method of installing with gimme
-- File Changes --
M lib/travis/build/script/go.rb (80)
M spec/build/script/go_spec.rb (32)
-- Patch Links --
https://github.com/travis-ci/travis-build/pull/375.patch
https://github.com/travis-ci/travis-build/pull/375.diff

Reply to this email directly or view it on GitHub:
https://github.com/travis-ci/travis-build/pull/375

yep, tip is explicitly handled in gimme
On Jan 30, 2015 6:42 PM, "Josh Kalderimis"<EMAIL_ADDRESS>wrote:

Does this allow for Go tip?
On Sat, Jan 31, 2015 at 11:34 AM, Dan Buch<EMAIL_ADDRESS>wrote:

This implementation aims to be independent of build env updates,
although once gimme is shipped with the build image(s) we can then remove
the presence check + download. The disabling of gvm was required in order
to have the correct go version activated, which I'm guessing will mean we
may have to remove gvm entirely from the build env as well.
It's worth noting that the aliasing logic changes with this PR such that
point releases such as 1.0 and 1.3 are now left alone rather than being
"upgraded" to 1.0.3 and 1.3.3, respectively. The reasoning here is that
such point releases are legitimate binary releases, whereas version 1.2
will still be "upgraded" to 1.2.2 as there is no 1.2 binary release
available (at least in the well-known download locations).
Example build in staging:
https://staging.travis-ci.org/travis-repos/go-test-staging/builds/405600
You can view, comment on, or merge this pull request online at:
https://github.com/travis-ci/travis-build/pull/375
-- Commit Summary --

Manage go versions with gimme
Test for existence of gimme executable differently
Try to figure out what's going on with gimme install
Apparently ~/bin does not exist yet (?)
Get more forceful with gvm + enable gimme version via eval
Enable go version prior to PATH and GOPATH settings
Extend condition for go_get_cmd to account for go1
Bump to gimme v0.2.2, omit gvm GOPATH entry
Updates specs per current method of installing with gimme
-- File Changes --
M lib/travis/build/script/go.rb (80)
M spec/build/script/go_spec.rb (32)
-- Patch Links --
https://github.com/travis-ci/travis-build/pull/375.patch
https://github.com/travis-ci/travis-build/pull/375.diff

Reply to this email directly or view it on GitHub:
https://github.com/travis-ci/travis-build/pull/375

—
Reply to this email directly or view it on GitHub
https://github.com/travis-ci/travis-build/pull/375#issuecomment-72290147
.

@joshk specifically, here: https://github.com/meatballhat/gimme/blob/de1e10e1b6ab5a90239d5b0408859f82b88d85b3/gimme#L146

HUZZAH! :+1:

most recent staging build: https://staging.travis-ci.org/travis-repos/go-test-staging/builds/405657

OMG!


[feature]Product page Improvement

Related Issue
closes #1041
Description
[Please include a brief description of the changes or features added]
Overall Product Page improvement:

Added JSON file to store product data
Added highlights section
On hover highlights about products appear
Added JS to fetch data and display through HTML
Added Search Bar
Modified Cart UI
Improved visibility of texts

Type of PR

[ ] Bug fix
[x] Feature enhancement
[ ] Documentation update
[x] Other (specify): addition of json file

Screenshots / videos (if applicable)
[Attach any relevant screenshots or videos demonstrating the changes]
BEFORE

AFTER

Checklist:

[X] I have performed a self-review of my code
[X] I have read and followed the Contribution Guidelines.
[X] I have tested the changes thoroughly before submitting this pull request.
[X] I have provided relevant issue numbers, screenshots, and videos after making the changes.
[X] I have commented my code, particularly in hard-to-understand areas.

Additional context:
[Include any additional information or context that might be helpful for reviewers.]

On adding a product the price is not increasing in cart. Same highlight is written for all the products. Search bar is also not working.

I haven’t worked on existing backend. I don’t have that skill. I only worked on Database part and Frontend

Can you please assign the labels?

But you can see that the cart was showing the total price on adding items but after merging your branch the amount is showing 0 only. Also as the search bar is not working so don't add it. I can see you have added option to like a product but on clicking it it is not working. And all the products can't have same highlights too.
I have not integrated any backend yet to the project it is entirely frontend based so where are you facing issues?

I will try to check these issues, and consult you if required.

https://github.com/Suchitra-Sahoo/AgriLearnNetwork/assets/146661411/dabcba40-e9ae-4955-a7fb-c50b9894ec44
I just checked and it is working completely,

pull all the changes from origin and make other corrections too as mentioned in previous review.

okay


tests: update several tests to test frames support

It looks replaced by https://github.com/OISF/suricata-verify/pull/609


Add a casting wrapper for different types

It should be straightforward to write a casting layer between the different interface types so that people can easily re-use Builder or Prebuilt instances across applications that might differ slightly in the types that they accept. A little bit more work to adapt one Matrix_ to another in the Builder, but it can be done by just inheriting from the "to" class while loading from the "from" class.

Probably need is_final and is_derived_from for the Matrix cast.

If is_same or is_derived_from, then the cast is a no-op.
If not is_final, we make a fake caster class that maps from one matrix to the other.
Otherwise, we give up.


waybar: 0.9.0 -> 0.9.1, fix build

Motivation for this change
ZHF: #80379
https://hydra.nixos.org/build/113067187

Also supersedes #78458 as date is needed to build waybar-0.9.1.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Following https://github.com/NixOS/nixpkgs/pull/78458#issuecomment-578585795, I'd prefer to name it howard-hinnant-date, as this seems to be the Repology meta name of the package?
Also could you, as you are already editing the package, add meta.homepage to Waybar?
Thanks for the fix and the upstream PRs!

Following #78458 (comment), I'd prefer to name it howard-hinnant-date, as this seems to be the Repology meta name of the package?

I agree, date seems to general for a package so specific

@erictapen fixed :)

When building with pulseaudio support it fails:
../src/modules/network.cpp:68:3: error: 'assert' was not declared in this scope
   68 |   assert(starts_with(read, category));
      |   ^~~~~~
../src/modules/network.cpp:6:1: note: 'assert' is defined in header '<cassert>'; did you forget to '#include <cassert>'?
    5 | #include "util/format.hpp"
  +++ |+#include <cassert>
    6 |
[51/74] Compiling C++ object<EMAIL_ADDRESS>
It works when backporting this patch: https://github.com/Alexays/Waybar/commit/129713fe1b8986fb4722b8e439b16508f063b3e7:
diff --git a/pkgs/applications/misc/waybar/default.nix b/pkgs/applications/misc/waybar/default.nix
index 69d6ff84268..d302b3c58c2 100644
--- a/pkgs/applications/misc/waybar/default.nix
+++ b/pkgs/applications/misc/waybar/default.nix
@@ -1,4 +1,4 @@
-{ stdenv, fetchFromGitHub, meson, pkgconfig, ninja, wrapGAppsHook
+{ stdenv, fetchFromGitHub, fetchpatch, meson, pkgconfig, ninja, wrapGAppsHook
 , wayland, wlroots, gtkmm3, libinput, libsigcxx, jsoncpp, fmt, scdoc, spdlog, gtk-layer-shell
 , howard-hinnant-date, cmake
 , traySupport  ? true,  libdbusmenu-gtk3
@@ -46,6 +46,13 @@
       "-Dsystemd=disabled"
     ];

+    patches = [
+      (fetchpatch {
+        url = "https://github.com/Alexays/Waybar/commit/129713fe1b8986fb4722b8e439b16508f063b3e7.patch";
+        sha256 = "1zphcyh0097c5m2s6p93i674q5im4zm8bp0hqb607afsk6vi2qd8";
+      })
+    ];
+
     meta = with stdenv.lib; {
       description = "Highly customizable Wayland bar for Sway and Wlroots based compositors";
       license = licenses.mit;

What did you do to invoke the command? When running nix-build -E 'with import ./. {}; waybar.override { pulseSupport = true; }', it results in the following derivation:
/nix/store/4a7ss18bwgn6biiggvmybx25cb9dfwzk-waybar-0.9.1

@eonpatapon Also the commit you mentioned is already present in 0.9.1.

I'm sorry I had some override in my overlay that I forgot about :(
The build works fine

Backported as 2fadc21e707dc65df2fd75c71a6d1e8d8aa091a5, 590c89b9fd115b6e6aab4a2d08c01286d198bbae.


bug: 392 limit filter query parameters to 50

New endpoints:
POST /api/investigations/filter
POST /api/alerts/filter
Request sample:
{
    "pageAble": {
        "page": 0,
        "size": 10,
        "sort": [
            "description,ASC"
        ]
    },
    "searchCriteria": {
        "filter": [
            "channel,EQUAL,SENDER,AND"
        ]
    }
}


Error Installing Plugin Grunt 0.4.5

Hi there,
I was trying to install this plugin on Grunt 0.4.5 version, but I can't. Some problems with fstream.
Please check the print screen attached.

Could you please check it?
Thanks.

You're using ancient Node and npm. Retry installation after upgrading them.

Your error log is very similar to npm/npm#8058's.

Going to close this. Will open if your problem persists.


Add a way to easily call a bean method when a camel lifecycle event happen

From https://github.com/apache/camel-k-runtime/issues/324
[ ] Make sure there is a JIRA issue filed for the change (usually before you start working on it).  Trivial changes like typos do not require a JIRA issue.  Your pull request should address just this issue, without pulling in other changes.
[ ] Each commit in the pull request should have a meaningful subject line and body.
[ ] If you're unsure, you can format the pull request title like [CAMEL-XXX] Fixes bug in camel-file component, where you replace CAMEL-XXX with the appropriate JIRA issue.
[ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[ ] Run mvn clean install -Psourcecheck in your module with source check enabled to make sure basic checks pass and there are no checkstyle violations. A more thorough check will be performed on your pull request automatically.
Below are the contribution guidelines:
https://github.com/apache/camel/blob/master/CONTRIBUTING.md

I wonder if the SPI interfaces should be named OnCamelContextXXX as OnContext may be a bit ambiguous for new users to Camel that by Context we mean CamelContext. The event classes are named CamelContextXXXEvent etc.

done


Need to add *.azureedge.net to the list of suffixes for Updates and Servicing

Customer reports that the DMPDOWNLOADER is try to get file from URL https://configmgrbits.azureedge.net/adminuicontent/ConfigMgr.AdminUIContent.cab            SMS_DMP_DOWNLOADER     02/07/2018 14:24:06      4944 (0x1350)
I believe this is the result of a recent change to the hosting of the CAB so the suffix is legit and just needs to be added.

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

ID: 26fc3067-8a85-2455-8b71-69cf46cbb7e0
Version Independent ID: a90ca598-c5fa-f245-eafc-0fd95f9eaca9
Content: Service connection point - Configuration Manager
Content Source: sccm/core/servers/deploy/configure/about-the-service-connection-point.md
Product: configuration-manager
GitHub Login: @aczechowski
Microsoft Alias: aaroncz

The change is already merged in the private repo (PR#2723). @aczechowski this issue can be closed.


Create search module

links to all the other submodules of the player
debut game
death date
list of teams the player played for
first name
last name

playerID
nameFirst
nameLast
Module URLs

Constants::ModuleUrls['Batting']

birth_date
debut_date
finalgame_date
death_date
list of teams played for


Logo source file?

Where can I find the source file (not png) of the project logo?
I would like to submit it to https://github.com/cjdowner/cryptocurrency-icons

I have made a vector version for you: https://github.com/atomiclabs/cryptocurrency-icons/issues/190


Unify block & doc comments.

This changes the behavior of block comments such that leading hash marks no longer mark a comment as being a documentation comment. Instead, all block comments are treated equally and users wishing to make a block comment a doc comment simply add an asterisk after the initial ###.

Released in v1.40.15.


How to calculate MOS_zscore in koniq10k datasets?

such as c1 = 0, c2 = 0, c3 = 25, c4 = 73, c5 = 7, c_total = 105, MOS = 3.83, SD = 0.53

In our downloaded score file, there's one column 'MOS_zscore' attached behind column SD, maybe you could refer to the published dataset to see if there's any update.

Yes, MOS_zscore = 77.38362, but I don not know how to calculate this Mark.
Another datasets maybe only give MOS mark，So I want to understand.
Thank for your replay！

This might be the post-processed MOS score, you can refer to their origin paper for an answer.

I read this paper already，but only got how to calculate MOS，not MOS_zscore.
Maybe I didn't see it O.O

image_name: the image file name
c1-c5: number of ratings for each ACR value
c_total: total number of judgments per image
MOS: Mean Opinion Scores of the 5-point ACR
SD: Standard Deviation of the MOS
MOS_zscore: ACR scores are first normalised for each user by z-scoring the user ratings

Hi, I am confused about the same issue. @wangbin2018 did you finally understand on how to calculate the MOS_zscore?


Cannot run BE locally

Hey @nivg1992
I tried to run the python service in a few ways...no luck.
Macbook Pro M2 PRO

docker run -e PF_DATA_FOLDER='/data' -p 5000:5000 -v ./data:/data nivg1992/faceplatform

Unable to find image 'nivg1992/faceplatform:latest' locally
latest: Pulling from nivg1992/faceplatform
docker: no matching manifest for linux/arm64/v8 in the manifest list entries.
See 'docker run --help'.

python3 -m "src.main"

Traceback (most recent call last):
  File "<frozen runpy>", line 198, in _run_module_as_main
  File "<frozen runpy>", line 88, in _run_code
  File "/Users/user/Desktop/development/faceplatform/src/main.py", line 11, in <module>
    from src.go2rtc_server_manager import Go2RTCServerManager
  File "/Users/user/Desktop/development/faceplatform/src/go2rtc_server_manager.py", line 6, in <module>
    import yaml
ModuleNotFoundError: No module named 'yaml'

poetry run python -m src.main
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File<EMAIL_ADDRESS>line 122, in spawn_main
    exitcode = _main(fd, parent_sentinel)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File<EMAIL_ADDRESS>line 131, in _main
    prepare(preparation_data)
  File<EMAIL_ADDRESS>line 244, in prepare
    _fixup_main_from_name(data['init_main_from_name'])
  File<EMAIL_ADDRESS>line 268, in _fixup_main_from_name
    main_content = runpy.run_module(mod_name,
                   ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "<frozen runpy>", line 226, in run_module
  File "<frozen runpy>", line 98, in _run_module_code
  File "<frozen runpy>", line 88, in _run_code
  File "/Users/user/Desktop/development/faceplatform/src/main.py", line 30, in <module>
    events_manager = EventsManager()
                     ^^^^^^^^^^^^^^^
  File "/Users/user/Desktop/development/faceplatform/src/utils/singleton.py", line 6, in get_instance
    instances[cls] = cls(*args, **kwargs)
                     ^^^^^^^^^^^^^^^^^^^^
  File "/Users/user/Desktop/development/faceplatform/src/events_manager.py", line 11, in __init__
    self.face_recognition = FaceRecognition()
                            ^^^^^^^^^^^^^^^^^
  File "/Users/user/Desktop/development/faceplatform/src/utils/singleton.py", line 6, in get_instance
    instances[cls] = cls(*args, **kwargs)
                     ^^^^^^^^^^^^^^^^^^^^
  File "/Users/user/Desktop/development/faceplatform/src/face_recognition.py", line 19, in __init__
    self.eventIdMapProccess = multiprocessing.Manager().dict()
                              ^^^^^^^^^^^^^^^^^^^^^^^^^
  File<EMAIL_ADDRESS>line 57, in Manager
    m.start()
  File<EMAIL_ADDRESS>line 562, in start
    self._process.start()
  File<EMAIL_ADDRESS>line 121, in start
    self._popen = self._Popen(self)
                  ^^^^^^^^^^^^^^^^^
  File<EMAIL_ADDRESS>line 289, in _Popen
    return Popen(process_obj)
           ^^^^^^^^^^^^^^^^^^
  File<EMAIL_ADDRESS>line 32, in __init__
    super().__init__(process_obj)
  File<EMAIL_ADDRESS>line 19, in __init__
    self._launch(process_obj)
  File<EMAIL_ADDRESS>line 42, in _launch
    prep_data = spawn.get_preparation_data(process_obj._name)
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File<EMAIL_ADDRESS>line 164, in get_preparation_data
    _check_not_importing_main()
  File<EMAIL_ADDRESS>line 140, in _check_not_importing_main
    raise RuntimeError('''
RuntimeError:
        An attempt has been made to start a new process before the
        current process has finished its bootstrapping phase.

        This probably means that you are not using fork to start your
        child processes and you have forgotten to use the proper idiom
        in the main module:

            if __name__ == '__main__':
                freeze_support()
                ...

        The "freeze_support()" line can be omitted if the program
        is not going to be frozen to produce an executable.

        To fix this issue, refer to the "Safe importing of main module"
        section in https://docs.python.org/3/library/multiprocessing.html

Traceback (most recent call last):
  File "<frozen runpy>", line 198, in _run_module_as_main
  File "<frozen runpy>", line 88, in _run_code
  File "/Users/user/Desktop/development/faceplatform/src/main.py", line 30, in <module>
    events_manager = EventsManager()
                     ^^^^^^^^^^^^^^^
  File "/Users/user/Desktop/development/faceplatform/src/utils/singleton.py", line 6, in get_instance
    instances[cls] = cls(*args, **kwargs)
                     ^^^^^^^^^^^^^^^^^^^^
  File "/Users/user/Desktop/development/faceplatform/src/events_manager.py", line 11, in __init__
    self.face_recognition = FaceRecognition()
                            ^^^^^^^^^^^^^^^^^
  File "/Users/user/Desktop/development/faceplatform/src/utils/singleton.py", line 6, in get_instance
    instances[cls] = cls(*args, **kwargs)
                     ^^^^^^^^^^^^^^^^^^^^
  File "/Users/user/Desktop/development/faceplatform/src/face_recognition.py", line 19, in __init__
    self.eventIdMapProccess = multiprocessing.Manager().dict()
                              ^^^^^^^^^^^^^^^^^^^^^^^^^
  File<EMAIL_ADDRESS>line 57, in Manager
    m.start()
  File<EMAIL_ADDRESS>line 566, in start
    self._address = reader.recv()
                    ^^^^^^^^^^^^^
  File<EMAIL_ADDRESS>line 250, in recv
    buf = self._recv_bytes()
          ^^^^^^^^^^^^^^^^^^
  File<EMAIL_ADDRESS>line 430, in _recv_bytes
    buf = self._recv(4)
          ^^^^^^^^^^^^^
  File<EMAIL_ADDRESS>line 399, in _recv
    raise EOFError
EOFError

Thanks @tamirhal

currently the docker doesn't supported arm64 (mac M processor), I will add it soon
2/3. did you run poetry install before?

Got it,
Yes i did


CI: match dispatch inputs in workflow_call

Unfortunately the previous fix didn't work. The json was evaluated anyway. So match the workflow_dispatch input structure in workflow_call.

Out of curiosity and sorry if I'm missing something obvious here: How/when do we trigger the workflow_call as opposed to the manual trigger?

There's a workflow in breez-sdk-docs here: https://github.com/breez/breez-sdk-docs/blob/main/.github/workflows/main.yml
It's used to create the packages so we can check whether the syntax of the snippets in the docs is ok.


Get tag from Github URL

This should work,
eget https://github.com/contour-terminal/contour/releases/tag/v<IP_ADDRESS>

There is already the --tag flag for this feature, so I don't see the point of supporting this.

less editing/typing


[CM-586] Do not resolve uid2 when running in privacy mode

https://liveintent.atlassian.net/browse/CM-586
Author Todo List:

[x] Add/adjust tests (if applicable)
[x] Build in CI passes
[x] Latest master revision is merged into the branch
[x] Self-Review
[x] Set Ready For Review status

Like the refactoring. 👍

Talked with Dejan and we are going to make a change in idres that will make the nonId/unifiedId handling cleaner. Will keep this unmerged until then


about hdf5 file

what should I do to get a pruned architecture? or after pruning, run a test ?

Working to use pth file only and remove the hdf5-related code


Update cn.js

update CN/ZH translation for version 2.0

Ignore the pipeline failure - it is to do with permissions and not the change itself


Request: option to shut down kernel

In the interactive python environment which opens at the right side of the screen when running code from a python file interactively, there is no option to shutdown the ipython kernel, only to restart it. Would be nice to add the option for shutting it down and have it reactivate automatically once new code is run on that interactive environment.

Thanks for the suggestion.
What's your reason for wanting to shut it down early?
Right now it shuts down when closing the interactive window.

Good to know, didn't realize closing it shuts down the process. The reason was basically to free resource usage after it's no longer needed in order to run something else in a different application while continuing writing in the editor, but closing it is good enough for that.


add leetcode 1178 solution

leetcode 1178
68 ms | 13.1 MB

I  resubmit your code to the leetcode, runtime is perfect! Thanks to your solution~

My pleasure


Install fails due to "pROC" dependency

pdstools version checks

[X] I have checked that this issue has not already been reported.

[X] I have confirmed this bug exists on the latest version of pdstools.

Issue description
Installing pdstools with "build_vignettes=TRUE" requires the "pROC" library to be preinstalled, so when running
"install_github("pegasystems/pega-datascientist-tools/r", build_vignettes=TRUE)" on a clean system fails the instalment. Seemingly the pROC is used in "adm-explained" notebook. See the error log:

Reproducible example
Run "install_github("pegasystems/pega-datascientist-tools/r", build_vignettes=TRUE)" without pROC library pre-installed.

Expected behavior
"install_github("pegasystems/pega-datascientist-tools/r", build_vignettes=TRUE)" should run without failure

Hey Anton, thanks, I'll move pROC from suggested to required imports in the R library.
BTW note that the python version is more actively being maintained these days than the R one.


support link in parentheses e.g. (http://example.com)

Alternative solution for https://github.com/liip/LiipUrlAutoConverterBundle/pull/22

hi, thanks for sending this pull request.
we are not really maintaining this library anymore because nobody at liip is currently using it. it is not up to date with recent symfony versions, not tested on php 7.1 or newer and so on. the travis-ci build fails for the antique php versions and obsolete symfony versions.
we plan to archive it soonish. would you want to take over maintenance? we could either give you the rights on this repo, or you fork and rename it and we point to your version from the readme...
in our opinion, the evolution should be to use an existing library for finding urls in text, or splitting out the logic implemented here into a library and have the bundle only integrate the library into symfony.

we archive this bundle because it should use a library instead of trying its own thing. feel free to use parts of this bundle for doing that if you want.


feat(protoc-gen-ng): add support for custom WKT

When using a service like https://buf.build there is no possibility to add custom well known types that are referenced from an import.
Adds the possibility to configure a custom WKT in the protoc-gen-ng config file

Hi @Grubana
first of all, I'm very sorry for a so later reply, which is normally not typical.
Thank you for the BUF tool, I haven't seen it before and thanks for adopting the project styles in your PRs.
From what I see from the changes the custom well-known types are coming from the config file?
  public customWellKnownTypes: {[key: string]: string};

So, the types will be listed inside this map under the type name as key and the type definition as the value? I'm sorry if the question seem dumb, just want to understand how the custom types get into the generator.
Thanks!


Infinite loop with DHCP Inform option

Hi. This issue relates to symptoms found in this RPi thread
In my own testing, on dhcpcd 9.4.0, running dhcpcd from the command line like:dhcpcd -B -s <IP_ADDRESS>/24 eth0 does cause the syslog to be filled with messages like:
Aug 16 14:56:49 meraki dhcpcd[361]: eth0: received approval for <IP_ADDRESS>
Aug 16 14:56:49 meraki dhcpcd[361]: eth0: received approval for <IP_ADDRESS>
Aug 16 14:56:49 meraki dhcpcd[361]: eth0: received approval for <IP_ADDRESS>
In addition, the device sends repeated DHCPINFORM (and ARP announcements) at a high frequency.
I did some debugging and it seems that with the first DHCP ACK, dhcp_bind calls ipv4_applyaddr which adds the address to the kernel. There is a handler for the kernel response dhcp_handleifa which calls dhcp_inform again, continuing the cycle.
Another phenomena I have noticed is that future DHCP ACKS are processed both by the newly opened UDP socket and the bpf filter, which keeps getting closed by dhcp_bind and reopened by dhcp_inform
I will try to contribute a fix but I would appreciate help solving this in a way that won't introduce a regression, since I am not familiar with dhcpcd's code.

Hello - I've just found this while searching the cause of the 8/second log entries I see when using the recommended inform <ipv4 addr> option (instead of static ip; i.e.
# edit /etc/dhcpcd.conf; added 2 lines
# interface wlan0
# inform <IP_ADDRESS>/24

After save & reboot:
$ journalctl -f | grep wlan0
Mar 26 07:15:17 raspberrypi0w dhcpcd[568]: wlan0: received approval for <IP_ADDRESS>
Mar 26 07:15:17 raspberrypi0w dhcpcd[568]: wlan0: received approval for <IP_ADDRESS>
Mar 26 07:15:17 raspberrypi0w dhcpcd[568]: wlan0: received approval for <IP_ADDRESS>
Mar 26 07:15:17 raspberrypi0w dhcpcd[568]: wlan0: received approval for <IP_ADDRESS>
Mar 26 07:15:17 raspberrypi0w dhcpcd[568]: wlan0: received approval for <IP_ADDRESS>
Mar 26 07:15:17 raspberrypi0w dhcpcd[568]: wlan0: received approval for <IP_ADDRESS>
Mar 26 07:15:17 raspberrypi0w dhcpcd[568]: wlan0: received approval for <IP_ADDRESS>
Mar 26 07:15:17 raspberrypi0w dhcpcd[568]: wlan0: received approval for <IP_ADDRESS>

Pleased to see you've already patched this, but surprised to see that the latest available ver of dhcpcd in RPi OS bullseye is:
$ dhcpcd --version
dhcpcd 8.1.2
Copyright (c) 2006-2019 Roy Marples
Compiled in features: INET ARP ARPing IPv4LL INET6 DHCPv6 AUTH

Couple of questions maybe you can answer:

Any idea why RPi is so far behind? 8.1.2 ==> 9.4.0 seems far behind.
Any chance of pushing your changes to an earlier (downstream?) version??

Please also note this is also related to a discussion of an issue I opened re RPi OS documentation.
Thnx 4 all,
~S


feat: sbb-link now implements LinkButtonInterface

Preflight Checklist

[x] I have read the Contributing Guidelines for this project.
[x] I agree to follow the Code of Conduct that this project adheres to.
[x] I have searched the pull request tracker for a Pull Request (PR) that matches the one I want to submit, without success.

Issue
This PR Closes #
Pull request checklist
Please check if your PR fulfills the following requirements:

[x] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been reviewed and added / updated if needed (for bug fixes / features)
[x] Build (yarn build) was run locally and any changes were pushed
[x] Lint (yarn lint) has passed locally and any fixes were made for failures

Changes
Changes in this pull request:

src/global/interfaces/link-button-properties.ts

two new interface have been added (LinkProperties and ButtonProperties); each of them has some required attribute (eg. href for link and name for button);
the LinkButtonProperties interface extends both, plus the AccessibilityProperties interface;
methods getLinkButtonBaseAttributeList(...) and getLinkButtonAttributeList(...) have now a safe check to avoid undefined attributes (eg. class='undefined'), see also this link;

src/components/sbb-link/sbb-link.tsx

the component now implements LinkButtonProperties;
icon prop has been renamed to iconName to be more consistent;
props have been reordered:

required props due first point of previous list have also 'undefined' as type (eg. @Prop() public href: string | undefined;);
optional props have no default anymore (eg. since iconPlacement is used only if an icon is provided and since there's no CSS rule for start value, the default start value has been removed);

src/components/sbb-link/sbb-link.stories.js: parameters have been reordered and categorized;
src/components/sbb-link/sbb-link.spec.ts: test fixed with icon cases;
src/components/sbb-link/sbb-link.custom.d.ts: no need for optional modifier.

Browsers
I tested the build on the following browsers:

[x] Firefox Desktop
[x] Chrome Desktop
[x] Edge Desktop
[ ] Safari Desktop
[ ] Chrome Mobile
[ ] Safari Mobile

Screen readers
I tested the build on the following browsers:

[ ] JAWS Firefox Desktop
[ ] JAWS Chrome Desktop
[ ] NVDA Firefox Desktop
[ ] NVDA Chrome Desktop
[ ] VoiceOver Safari Desktop
[ ] VoiceOver Chrome Desktop
[ ] VoiceOver Safari Mobile
[ ] Android Accessibility Suite Chrome Mobile

Pull request type

Please check the type of change your PR introduces:

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] Documentation content changes
[ ] Other (please describe):

Does this introduce a breaking change?

[x] Yes
[ ] No

icon property in sbb-link is now iconName
Other information

Codecov Report

Merging #1344 (1422bf1) into master (ab917b0) will increase coverage by 1.69%.
The diff coverage is 88.23%.

@@            Coverage Diff             @@
##           master    #1344      +/-   ##
==========================================
+ Coverage   54.85%   56.54%   +1.69%
==========================================
  Files          49       53       +4
  Lines        1659     1749      +90
  Branches      406      431      +25
==========================================
+ Hits          910      989      +79
- Misses        671      681      +10
- Partials       78       79       +1

Impacted Files
Coverage Δ

src/components/sbb-card-badge/sbb-card-badge.tsx
88.88% <ø> (ø)

...c/components/sbb-card-product/sbb-card-product.tsx
64.19% <ø> (ø)

src/components/sbb-footer/sbb-footer.tsx
87.50% <ø> (ø)

src/components/sbb-link-list/sbb-link-list.tsx
88.23% <ø> (ø)

...c/components/sbb-toggle-check/sbb-toggle-check.tsx
66.66% <66.66%> (ø)

src/components/sbb-title/sbb-title.tsx
88.88% <84.61%> (+2.22%)
:arrow_up:

src/components/sbb-link/sbb-link.tsx
89.65% <88.88%> (-1.78%)
:arrow_down:

src/components/sbb-icon/sbb-icon.tsx
91.66% <91.66%> (ø)

src/components/sbb-teaser/sbb-teaser.tsx
91.66% <91.66%> (ø)

src/components/sbb-button/sbb-button.tsx
91.17% <100.00%> (ø)

... and 1 more

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Incompatibility with tibble>=2.0.0

After upgrading to tibble 2.0.1 for another library read_feather is giving this error:
Error: evaluation nested too deeply: infinite recursion / options(expressions=)?
Has anyone seen this before? do we just need to recompile feather or is it not compatible with this new version?

I am having the same issue

@scworland-usgs @alexmac I observed this too in many projects I work on. I believe that the breaking changes in tibble 2.0.0 are why the maintainers came back here to release feather 0.3.2. Could you try upgrading to feather 0.3.2 and see if it solves the problem? It did for me!
@hadley @hadley I think this issue can be closed.

Thanks @jameslamb — we should probably do a minor release of feather than encodes this dependency in the DESCRIPTION so that tibble gets automatically updated.

@hadley is #375 the right place to add the version floor? Or do you want to do a minor release before dealing with that PR?


dropdown in table header

Hi folks. Today I had the idea of putting a dropdow inside a table thead th in order to create a filter. Result is pretty sweet. Ok, the dropdow was not created to be put there, but hey, it works.
So, whats my goal here: it works; it doesn't look pretty while working. What you guys thing about having it as a supported functionality for dropdown, with neat looks (table wise) and all?

We don't want to be creating specific designs for dropdowns based on where they appear. Instead if there is a specific style you want. Add it in your own style.css.


Decouple Eclipse workspace clean from Bazel workspace clean

In BazelBuilder, we implemented the Eclipse Workspace clean such that it triggers a Bazel workspace clean ("bazel clean").
https://github.com/salesforce/bazel-eclipse/blob/master/plugin-core/src/main/java/com/salesforce/bazel/eclipse/builder/BazelBuilder.java#L181
That seemed correct, but in hindsight is not. The clean operation in the Maven world is a common thing to do. In Bazel, it is something you almost never do. It is very expensive. If you are working in a large Bazel monorepo, with only a handful of packages imported into Eclipse, the blast radius of your Bazel clean is the entire monorepo not just the Eclipse imported packages.
When a user elects to do a Clean... in Eclipse, I think the intent is to wipe out the state of the Eclipse workspace and rebuild that state. This is about recomputing all the Bazel Classpath Containers, which will then trigger JDT to re-evaluate each project. This does not require an invocation of 'bazel clean'.
We should:

decouple bazel clean from Eclipse clean by default
implement a pref (default off) that allows a user to invoke bazel clean from Eclipse clean.

Over time, we can learn if users feel like this coupling should be enabled by default. I categorized this as a User Feature, but it is arguably a Bug as "Eclipse Clean..." is pretty miserable right now.

As of PR #192 bazel clean is no longer run when Elipse clean is invoked. The pref to toggle this behavior is not implemented yet.

Dropping the toggle feature. Closing this issue as implemented.


rm @Ignore from twofer tests

I'm new to Kotlin, especially testing. But shouldn't all the tests be enabled by default?

Hi @sh2244 - we only enable the first test by default 🙂
This is done deliberately in order to allow users to build up their solution iteratively 🙂

No worries, I just sed them out :-) You're welcome to close the issue.
ssed -i '/@Ignore/d' src/test/kotlin/*.kt

Thanks @sh2244 - if you spot anything else odd, let me know and feel free to open any PRs! :slightly_smiling_face:


CPU Spike when ManualResetEventSlim Times Out

http://i.imgur.com/5WXVsQT.png
A CPU Spike is occuring on the if (!connectDoneEvent.Wait(_connectTimeout)) if inside of CreateTcpConnection() in HTTPRequest.cs.
Not too sure if its just happening to me or not.

Wrong XNet haha sorry


[1.12] Sophisticated Wolves: Dog treats and carrying cages don't work

Issue Description
Whenever I try to give my dogs treats or put them in carrier cages in the Sophisticated Wolves mod, I can't do either of those.
Relevant mods:
Sophisticated Wolves
Reproduction Steps

Tame a wolf or spawn a sophisticated wolf.
Try to give the dog a treat or try to put it in a carrier cage by right clicking the dog while holding the item.

Screenshots / Videos

Can confirm. Log spams with the following when attempting to feed a Dog Treat to a vanilla Wolf:
[11:45:24] [Server thread/FATAL] [net.minecraft.server.MinecraftServer]: Error executing task
java.util.concurrent.ExecutionException: java.lang.NoClassDefFoundError: com/attributestudios/wolfarmor/api/util/Capabilities
	at java.util.concurrent.FutureTask.report(Unknown Source) ~[?:1.8.0_251]
	at java.util.concurrent.FutureTask.get(Unknown Source) ~[?:1.8.0_251]
	at net.minecraft.util.Util.func_181617_a(SourceFile:47) [h.class:?]
	at net.minecraft.server.MinecraftServer.func_71190_q(MinecraftServer.java:723) [MinecraftServer.class:?]
	at net.minecraft.server.MinecraftServer.func_71217_p(MinecraftServer.java:668) [MinecraftServer.class:?]
	at net.minecraft.server.integrated.IntegratedServer.func_71217_p(IntegratedServer.java:185) [chd.class:?]
	at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:526) [MinecraftServer.class:?]
	at java.lang.Thread.run(Unknown Source) [?:1.8.0_251]
Caused by: java.lang.NoClassDefFoundError: com/attributestudios/wolfarmor/api/util/Capabilities
	at sophisticated_wolves.compatibility.CompatibilityWolfArmor.copyWolfItems(CompatibilityWolfArmor.java:66) ~[CompatibilityWolfArmor.class:?]
	at sophisticated_wolves.item.ItemDogTreat.func_111207_a(ItemDogTreat.java:52) ~[ItemDogTreat.class:?]
	at net.minecraft.item.ItemStack.func_111282_a(ItemStack.java:391) ~[aip.class:?]
	at net.minecraft.entity.player.EntityPlayer.func_190775_a(EntityPlayer.java:1220) ~[aed.class:?]
	at net.minecraft.network.NetHandlerPlayServer.func_147340_a(NetHandlerPlayServer.java:1075) ~[pa.class:?]
	at net.minecraft.network.play.client.CPacketUseEntity.func_148833_a(SourceFile:69) ~[li.class:?]
	at net.minecraft.network.play.client.CPacketUseEntity.func_148833_a(SourceFile:13) ~[li.class:?]
	at net.minecraft.network.PacketThreadUtil$1.run(SourceFile:13) ~[hv$1.class:?]
	at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) ~[?:1.8.0_251]
	at java.util.concurrent.FutureTask.run(Unknown Source) ~[?:1.8.0_251]
	at net.minecraft.util.Util.func_181617_a(SourceFile:46) ~[h.class:?]
	... 5 more

see https://github.com/NightKosh/Sophisticated-wolves/pull/90


⚠ API - Lens has degraded performance

In 199ebb9, API - Lens ($LENS_API_URL) experienced degraded performance:

HTTP code: 503
Response time: 701 ms

Resolved: API - Lens performance has improved in a566d30 after 8 minutes.


Run CI on all branches

Only running them against auto-libc unfortunately means that PRs don't run CI.

@bors: r+ 81ba7f05a846c84cce9c685084d2eb1c8a02e5c3

:hourglass: Testing commit 81ba7f0 with merge 61ae486...

:sunny: Test successful - status-appveyor, travis


mkcloud: do not use $reposerver for image downloads

as it is mixing use cases
and directory layout might be different elsewhere.
Also, by using URLs, we allow for HTTP on custom port numbers

So I tested this change and it seems to work fine in our environment. I ran into some problems during my testing (see #1968, #1969), but they seem unrelated to me.
So a +1 from me to merge this :)


Fix #318 deploying ResNet to ONNX

#318 Add a check for pooling width=0 and height=0 to use globalAveragePool during onnx conversion

Did you run DLPy unit tests? Does the change product any diff?

Closing because this pull request is replaced by #356 .