Missing Qt5PrintSupport.dll in the latest nightly

Bug description
Latest nightly doesn't start after fresh install. Windows reports that Qt5PrintSupport.dll is missing.
Steps to reproduce

Delete installed Grabber (at least the files from its installation folder)
Install latest Grabber_nightly_x64.exe from https://github.com/Bionus/imgbrd-grabber/releases/nightly
Run Grabber

Expected behavior
Normal Grabber start.
Context
N/A
Screenshots

System information

OS: Windows 10
Grabber version: nightly https://github.com/Bionus/imgbrd-grabber/commit/98c5b37b48d0eb0524db28cd0019d94c4d6a8326

Additional context
Can't be reproduced in the stable 7.9.1.

Strange, I removed it recently because it should not have been necessary. windeployqt deems it unnecessary (hence its non-presence in ZIP releases), and nowhere in Grabber are there any printing being done.
I guess I'll add it back although it's very confusing.

@Bionus I'm not that experienced enough. But 7.9.1 version doesn't have Qt5PrintSupport.dll inside its installation folder after fresh install and it runs fine. While latest nightly https://github.com/Bionus/imgbrd-grabber/commit/98c5b37b48d0eb0524db28cd0019d94c4d6a8326 runs only with Qt5PrintSupport.dll (which I got from some older version). Mb nightly build just needs some requirements changes?
7.9.1:

Even stranger then, but great info 🕵♂
Because the build process is pretty much identical between both, differences are truly minor. I guess I'll have to investigate to see which of those minor changes could add a dependency on printing.

That file is missing from the latest portable release (7.11.0_x64)

Still missing in v7.11.1, Grabber_v7.11.1_x64.zip doesn't have it yet needs it to run.

I get the same problem on the last portable version for Windows.

Qt5PrintSupport missing in v7.11.2_x64.zip

Can also confirm nightly portable launches fine, unlike 7.11.2 portable. And I guess nightly is already using Qt6 instead.


web location DO NOT MERGE

manually copy guides
see https://github.com/ome/omeroweb-install/pull/51

Installed OMERO.web and tested the running of it using the curl command.
All went well.

Closing this PR and merging https://github.com/ome/omeroweb-install/pull/51

Looking forward to not needing these anymore :)


Display how long a student has been marked as missing

This PR adds a timer to display how long a ticket has been marked as missing. It's more or less identical to the code for displaying a claimed timer, but based on the markedAsMissingAt field of a Ticket.
This is something that would be really helpful for CS33 hours. We frequently have many missing students because of long queues, and it would be much easier to enforce our missing policy with a timer.

Thanks for the pull request!! What exactly is the CS33 missing policy?

If someone's been marked missing for 30 minutes, we delete them from a queue. It's currently hard to gauge that exactly, so as a rule of thumb we try to delete tickets after helping 2 people. The time to help someone varies a lot though, so it's not ideal.

Makes sense. Would this be better solved then by automatically deleting the ticket after 30 minutes?

I don't think so, because someone can be seen after the 30 minute mark if they talk to a TA before it. Usually, they'll be helped after the TA finishes who they're currently on, so it can be another 15 minutes between them coming in and them being seen.

Good point, I didn’t think about that. What if the TA who checks in with
them unmarks them as missing? This would also prevent them from being
deleted by other TAs.
On Thu, Nov 15, 2018 at 5:54 PM Ben Navetta<EMAIL_ADDRESS>wrote:

I don't think so, because someone can be seen after the 30 minute mark if
they talk to a TA before it. Usually, they'll be helped after the TA
finishes who they're currently on, so it can be another 15 minutes between
them coming in and them being seen.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/signmeup/signmeup/pull/249#issuecomment-439220121,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAbtCNEvvMDuSFz25CqMYY7G6y582vItks5uvfCngaJpZM4YaxJQ
.

Yeah, I think that would work, and then other TAs could claim the student as well. Would this need to be a per-course setting then?
Sorry for dropping the ball on this by the way!

Definitely not dropping the ball - this is a busy time for everyone :)
Yeah, a per-course setting would definitely be needed, ideally so the course could choose the time limit, maybe in a drop-down similar to the one used to pick queue end times. Let me know if you have any questions, I look forward to seeing this!

Talked to another 33 TA, and there's a problem with autodeleting - there are some cases where we'd like to make exceptions to the policy, which is hard to do if the ticket is deleted. For example, if a student is pulled away from hours for some serious, unavoidable reason and comes back later, we'd like for them to not forfeit their spot.

Awesome!!
Wouldn't that still be a problem if students are deleted manually? Either way, they're no longer in the queue.

Yeah, true. Is there a way to see deleted questions? A TA would remember manually deleting a ticket, but probably not one that was removed automatically

Not presently, but the data is there. Presumably wouldn't a TA remember marking the student missing? Also, if we're already trusting a student to self identify a "serious situation" would it be ok to trust them with this too? They certainly couldn't get away with faking it very often. How do you feel about leaving the auto-delete and fixing it if we see abuse? That was kind of my plan for allowing users to set their preferred name and I haven't seen any serious abuse so far.

Yeah, I think we could give that a try. TAs generally remember, but it does get a little harder when there are lots of people missing. You're right that students probably won't try to abuse this.

Awesome! I'm super excited for this. I took a full look at the code/experience and just have a few things:

In the course settings, could we change the "No window" option to something like "No deletion"? I'm worried that "No window" could be interpreted as "delete immediately".
In addition to the problem you mentioned about unmarking and remarking a student as missing, there's also the case of server restarts, in which case the ticket wouldn't be deleted at all. For scheduling queue deletion we use Steve Jobs. What do you think about using this to schedule a ticket deletion job? You could associate a job id with the ticket and then cancel the job when the ticket is unmarked as missing. Note that we currently have Steve Jobs 2.0.1 installed, and the latest version is 3.0. You're welcome to either use 2.0.1 or update our existing code (it seems like 2.0.1 and 3.0 are pretty similar but it's unclear to me if there are any incompatibilities).

Thanks!!


Add a 'Proof' interface for services

Add a Proof interface for services to formalise the API.
@yknl
Checklist

[ ] Code is commented where needed
[ ] Unit test coverage for new or modified code paths
[x] npm run test passes
[ ] Changelog is updated
[x] Tag 1 of @yknl or @zone117x for review

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

I've renamed the variable. Do you think https://github.com/blockstack/blockstack.js/blob/master/src/profiles/profileSchemas/personUtils.ts#L114 will need to be changed too?

@expenses This ( https://github.com/blockstack/blockstack.js/blob/master/src/profiles/profileSchemas/personUtils.ts#L114) doesn't need to be changed. It is just good for backwards compatibility!

@yknl Looks good to me...

@expenses Can you provide some documentation for how you intend this API to be used?


fixing small logo and favicon

using parent folder to point to images:
favicon: '../images/favicon.png'
logo: '../images/logo_small.svg'

Codecov Report

Merging #211 into master will decrease coverage by 0.19%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #211      +/-   ##
==========================================
- Coverage   79.89%   79.69%   -0.20%
==========================================
  Files         100      100
  Lines        1870     1852      -18
==========================================
- Hits         1494     1476      -18
  Misses        376      376

Flag
Coverage Δ

#unittests
79.69% <ø> (-0.20%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

mantisshrimp/core/bbox.py
64.70% <0.00%> (-4.79%)
:arrow_down:

mantisshrimp/metrics/metric.py
90.90% <0.00%> (-0.76%)
:arrow_down:

mantisshrimp/core/mask.py
84.29% <0.00%> (-0.63%)
:arrow_down:

mantisshrimp/parsers/splits.py
95.65% <0.00%> (-0.19%)
:arrow_down:

mantisshrimp/parsers/parser.py
95.00% <0.00%> (-0.13%)
:arrow_down:

mantisshrimp/models/rcnn/fastai/callbacks.py
100.00% <0.00%> (ø)

...antisshrimp/models/rcnn/lightning/model_adapter.py
100.00% <0.00%> (ø)

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 f894806...3148081. Read the comment docs.


Added basic request logging

@erkie :dart:

Nice! Can you set it so it's enabled by default? :D And then change the wording the readme to be disable.

@erkie done!


Chore: Readme cleanup

Fix badge links and format filter demo links.

hm. my ambition to save some energy by not running CI failed :E


Masthead overflow – keyboard should skip overflow buttons

Detailed description

Describe in detail the issue you're having.

When navigating through the masthead with the keyboard, the overflow buttons are not being skipped and are getting a focus state.
The functional specs state the overflow buttons should skip focus on keyboard:

Is this a feature request (new component, new icon), a bug, or a general
issue?

bug

Is this issue related to a specific component?

masthead

What did you expect to happen? What happened instead? What would you like to
see changed?

Should match functional spec

What browser are you working in?

Chrome
Version 85.0.4183.121 (Official Build) (64-bit)

What version of the IBM.com Library are you using?

Canary

What offering/product do you work on? Any pressing ship or release dates we
should be aware of?

October release
Steps to reproduce the issue

Open in Chrome
Use keyboard to navigate through masthead
Step three
etc.

Additional information

Screenshots or code
Notes

@oliviaflory I think I remember that Ram and @Praveen-sr opened a different approach where we would provide a different aria-label that tells what it is, but not hide it. We might need functional spec updates on this @photodow ?

This isn't just about the screen reader though—the mismatch between what's on the screen and the pagination and functionality will be confusing to users and this does feel like an error.

@jeffchew @wonilsuhibm @oliviaflory do we need to set up a short meeting to discuss this? I feel like we're talking about 3 different things, or at least coming at it from 3 different angles and it might be nice to align before we make any changes.

That sounds like a good idea @photodow

Roberta will schedule a meeting next week.

Update the functional specs to NOT hide the left / right arrow from screen readers, but include an aria label that provides a description of the button behavior.  This is to accommodate to avoid confusion for users with low vision.
@photodow This is no longer a dev bug, but requires an update to the functional specs.

After the discussion we had today (10/22) with the accessibility team, Ram would like to review the updates made in #4183 before determining if the overflow buttons should be hidden from screen readers.

@Praveen-sr Can you retest this to be sure the change works properly.  Thanks.

@oliviaflory @RobertaJHahn @ariellalgilmore We re tested this on React
For keyboard user working fine.
For screen reader users:
Mentioned buttons are reachable only in up/down arrow key navigation. These buttons are not reachable in tab/shift tab navigation hence this may be confusing for the screen reader user.
Since all the menus items are navigable even without accessing overflow buttons, these can be hidden from the screen reader to avoid any confusion. Hide [using aria-hidden] overflow buttons from the screen reader.
Note: this is applicable for both JAWS FF as well as Voiceover iPhone.

@Praveen-sr thank you and Ram for the quick feedback
Confirming your recommendation is to:  Hide [using aria-hidden] overflow buttons from the screen reader


Pass family

In order to be able to select the IP type when DNS querying, family needs to be proxied from the options passed.

@bitinn friendly ping :)

We use the module at FB, which uses IPv6-only networks. However, we still return sometimes A registries from our DNS.

Yup!

Can you update https://github.com/mjesun/node-fetch/blob/e943b2273837fe4398ffb9d3951665db3380e996/README.md#options as well?

I think you'll have to save the property to this.family in the constructor as well for this to work.
Also to preserve this options through redirects, you'll probably want to add it to the options for  following redirects, too.
Take a look at #473 too see what I mean.

Superseded by #474.


Make Google shared drive an optional plugin, like NextCloud, update Cloud Backup documentation

Important notices
Before you add a new report, we ask you kindly to acknowledge the following:

[x] I have read the contributing guidelines at https://github.com/opnsense/core/blob/master/CONTRIBUTING.md
[x] I am convinced that my issue is new after having checked both open and closed issues at https://github.com/opnsense/core/issues?q=is%3Aissue

Is your feature request related to a problem? Please describe.
When reviewing 23.7.9 release notes, I noticed this note :
"system: add support for Google Shared drives backup (contributed by Jeremy Huylebroeck)"
Looking at the Cloud Backup documentation I see detailed instructions for Google Drive and Nextcloud with the following problems :

There is no mention of NextCloud backup functionality requiring the **os-nextcloud-backup ** to be installed.
The documentation mixes both NextCloud and Google drive information, giving the impression both are installed by default when Nextcloud is not.

Google drive's inclusion as a core feature is also incoherent with several OPNsense mission statement elements such as being open source, transparent and friendly.
Describe the solution you like

It would be useful to mention **os-nextcloud-backup ** needs to be installed and add a mention to it in core features.
Google drive backup should not be enabled by default, it should be available as an optional plugin, like Nextcloud.
When either of them is available, their parameters should only be visible/expanded when enabled.
Documentation should also be separate for both backup options, and updated. Having encryption for the Nextcloud backup was missing from the included screenshot.

Describe alternatives you considered

After installing **os-nextcloud-backup ** Nextcloud backup became available.
I searched for a dedicated Google shared drive backup package to remove but there was none.

Additional context
I didn't check in detail what was missing or outdated.

If this a docs problem might be worth contributing there instead.
Cheers,
Franco

I'd like to step up and work in improving the documentation.
Am I correct in this specific case the document to update is at :
https://github.com/opnsense/docs/blob/master/source/manual/how-tos/cloud_backup.rst
?
If so I'd like to request permission to do so, or just confirmation I can make a pull request etc.
Thanks in advance for considering this request.

@MagicFab yep, feel free to open a PR. Thanks in advance!


Forty-First Community Call

The next call will be on Tue, Nov 15th, at 10 am CET (8 am UTC), Asia and Europe-friendly time.
Agenda:

Cosmoverse Colombia
Wasmd 0.30
Cosmos SDK update plans
Next round of Academy
AwesomWasm
Sylvia Framework

Open Q&A
Zoom link: https://us02web.zoom.us/j/85474395134?pwd=TkhmZ0ZBdFErSm5Ga0dXWVpVK2NWQT09

The video is online: https://vimeo.com/771081061
Thank you to everyone who attended and for your questions!


Wasmer instability

I noticed the Github Actions stuff failing sometimes with downloading Wasmer. I think that is just unmaintained now.
I'll send a PR that fixes it by switching to a better maintained one.

Thanks!
On Sat, Aug 26, 2023 at 6:35 PM guregu @.***> wrote:

I noticed the Github Actions stuff failing sometimes with downloading
Wasmer. I think that is just unmaintained now.
I'll send a PR that fixes it by switching to a better maintained one.
—
Reply to this email directly, view it on GitHub
https://github.com/trealla-prolog/trealla/issues/307, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFNKSESI2IDGECJB4FR2TRTXXGYNXANCNFSM6AAAAAA37MZNCQ
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


Additional FQDN dependencies for GPU clusters

For VNET integrated environments do we need to add additional FQDN in the Firewall controlling egress from the Azure Databricks environment if we are using GPU based clusters? I have a support ticket open which suggests that we need to whitelist developer.download.nvidia.com and nvidia.github.io but there is no mention of this requirement on this page!

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

ID: 97e9dc65-c8f6-240f-48eb-c2ad00e7ec6d
Version Independent ID: 9af96e1b-b9ae-ddba-4f15-d0f5fbda9d62
Content: GPU-enabled clusters - Azure Databricks
Content Source: databricks/clusters/gpu.md
Service: azure-databricks
GitHub Login: @mssaperla
Microsoft Alias: saperla

@pnarsi  Thanks for the feedback! I have assigned the issue to the content author to evaluate and update as appropriate.

#please-close


Dannys changes

This is just one absurd PR of all the random changes I've been making in the last 2 weeks to get the ansible deploy to work. Best reviewed commit-by-commit?
I've been using this for real deploys to india cloud, so this is more for just for an extra set of eyeballs, and to make a list of things worth revisiting later
@TylerSheffels @cewing

@TylerSheffels want to get this in today so I can start making smaller PRs again :)?


Memory/process instances issues

Hi,
It seems that there are two issues with the exiftool processes.
The first is that the processes aren't actually closed; when I go to Task Manager (using Win10) I see that all opened exiftool.exe processes are still open even though it looks like everything goes well in the code execution (the .then(() => ep.close()) is included).
The second issue is that some of these processes appear to not refer to a created copy of the original exiftool.exe. When I inspect the file location of the process in Task Manager, half of the processes appear to originate in C:\Users\paddotk\AppData\Local\Temp\par-546a6172646f\cache-exiftool-11.65.
Thanks for making this tool btw, I'm glad to finally have found one that works with mp4 files! 😄

I've been using this package recently and I've noticed this too, I also think that this is not maintained anymore so perhaps the best solution would be to fork this repo and edit from there.


not working with latest node (6.3.1)

i got it working by using 6.2.2.
thanks!

Here is working fine with node 6.8.0.


Felt math

Went through mathematical asserts / comparisons  and made a few updates. Also used OZ Uint2656 safemath for voting power aggregation

Should we be using assert_le_felt (i.e using treating the input as unsigned instead of signed numbers)?

resolved on discord

I think we can squash and merge then :)


⚠ PrivateHD has degraded performance

In 08cc12a, PrivateHD ($PHD) experienced degraded performance:

HTTP code: 200
Response time: 1767 ms

Resolved: PrivateHD performance has improved in ffc7295.


Collect compiler messages after refchecks

Following up on https://github.com/scalameta/scalameta/pull/749
The semanticdb does still not contain -deprecation warnings because they are emitted during refchecks.

I have a pending fix for this issue.


[multiple platform] Can't run image with other platform

Is your feature request related to a problem? Please describe.
Not sure if the feature is supported in orbstack or not. I need run a container with other platforms.
I have discovered a potential bug while trying to run Docker images docker run --platform
Although I was able to build images for different platforms with docker buildx --platform, attempting to run the images on other platforms resulted in an error. This may be a bug or a new feature we need support, and I would like to report it.
$ docker run --rm -ti --platform "linux/arm64" alpine sh
exec /bin/sh: exec format error

$ docker run --rm -ti --platform "linux/amd64" alpine sh
/ # exit

# interesting part is, if I run above command with other platform (not "linux/amd64") , the command remembered
# that  platform, and  always try to run image with that platform, seems a bug in it
$ docker run --rm -ti --platform "linux/arm64" alpine sh
Unable to find image 'alpine:latest' locally
latest: Pulling from library/alpine
Digest: sha256:124c7d2707904eea7431fffe91522a01e5a861a624ee31d03372cc1d138a3126
Status: Downloaded newer image for alpine:latest
exec /bin/sh: exec format error

$ docker run -ti --rm alpine sh
WARNING: The requested image's platform (linux/arm/v6) does not match the detected host platform (linux/amd64/v3) and no specific platform was requested
exec /bin/sh: exec format error

# So I have to run with platform amd64 to reset to my platform on macbook
$ docker run --rm -ti --platform "linux/amd64" alpine sh
Unable to find image 'alpine:latest' locally
latest: Pulling from library/alpine
Digest: sha256:124c7d2707904eea7431fffe91522a01e5a861a624ee31d03372cc1d138a3126
Status: Downloaded newer image for alpine:latest
/ # exit

$ docker run --rm -ti alpine sh
/ # exit

Describe the solution you'd like
Be above to run docker run --platform xxxx as well with docker buildx --platform xxxx

more tests:
Image Alpine supports below platform

I run tests with Colima , Here are the report that I can run or can't run
can run with docker run --platform xxx

linux/389
linux/amd64
linux/arm64/v8

can't run with docker run --platform xxx

linux/arm/v6
linux/arm/v7
linux/ppc64le
linux/s390x

Then I run test under orbstack

Support for emulating arm64 on x86 has been added for the next release. Until now, we've only supported emulating x86 on arm64.

Released in v0.8.0.

nice job.
let me test it

@kdrag0n
Seems I have upgraded to latest 0.8.0, but there is no command to show the version
$ orbctl --version
Error: unknown flag: --version

$ orbctl version
Error: unknown command "version" for "orbctl"
Run 'orbctl --help' for usage.

$ orb version
-bash: line 1: version: command not found

$ orb --version
Error: unknown flag --version

Released in v0.8.0.

Confirm, it works now with v0.8.0, thanks.
$ docker run --rm -ti --platform "linux/arm64" alpine sh

Unable to find image 'alpine:latest' locally
latest: Pulling from library/alpine
Digest: sha256:124c7d2707904eea7431fffe91522a01e5a861a624ee31d03372cc1d138a3126
Status: Downloaded newer image for alpine:latest
/ #

@kdrag0n
But the other bug isn't fixed
# this command is failed
$ docker run --rm -ti --platform "linux/arm/v6" alpine sh
Unable to find image 'alpine:latest' locally
latest: Pulling from library/alpine
Digest: sha256:124c7d2707904eea7431fffe91522a01e5a861a624ee31d03372cc1d138a3126
Status: Downloaded newer image for alpine:latest
exec /bin/sh: exec format error

# but why it impacts the next `docker run` command, which should work.
$ docker run --rm -ti alpine sh
WARNING: The requested image's platform (linux/arm/v6) does not match the detected host platform (linux/amd64/v3) and no specific platform was requested
exec /bin/sh: exec format error

That's standard Docker behavior. I don't know why, but it's not a bug.

That's standard Docker behavior. I don't know why, but it's not a bug.

So it is not orb bug, it is docker's bug?
Ok, let me check with docker moby team.

I believe it's intended behavior but couldn't find evidence for that.


PARQUET-965: Add support for FIXED_LEN_BYTE_ARRAY read and write support in parquet-arrow

The decimal support is left for further commits.
This may also helps ARROW-901

Also, cc @cpcloud if you are adding Decimal support.

Minor comments. The build is fine; hopefully we'll get the Appveyor stuff squared away soon

ping @wesm, minor changes had been made according to your comments.

Sorry for the delay. +1


Increase test coverage of Contract Class

Per #753 to increase overall test coverage and quality.
Missing test coverage of Contract class in package:contract of getBalance and multiCall methods.

I believe these methods do get covered in other tests, potentially outside of the contract package itself, however I don't think tests outside of this package should be the source of truth for functionality within the contract class. Just familiarising myself with the repository, would be happy to pick this up over the weekend :)


Add func method to SaveAt

See https://github.com/patrick-kidger/diffrax/issues/113

Added a (set of) test(s?) as a parameterization to the existing test

Nit aside, this LGTM!

Great. Looks like the checks are failing bc of some package manager but LMK if you need something from my PR too

Yup, looks like a broken upstream update. I'll take it from here.
Thank you for contributing!


Swagger UI-viewer handled over http

UI viewer is done through calling a http URL and gives this warning:
Mixed Content: The page at 'https://nightly2.apinf.io/api/pGZPrqpS4i3jduC2C' was loaded over HTTPS, but requested an insecure image 'http://online.swagger.io/validator?url=https://nightly2.apinf.io/gridfs/fs/id/88d7b90bb0547157b848752f'. This content should also be served over HTTPS.

@bajiat Should be fixed by update swagger-ui.js https://github.com/apinf/api-umbrella-dashboard/issues/1371#issuecomment-239176879


Add curves

This adds a support class for curves.

[x] parsing <curve> opcodes
[x] explicit and implicit indexing
[x] linear interpolation
[x] spline interpolation (not in sfz, can be introduced as extension)

Some test cases for curves (plot)

Builtin curve 6

run: ./build/tests/sfizz_plot_curve 6 curves.sfz > curves.dat
sfz: /*empty*/

Undefined curve 7, fallback to default

run: ./build/tests/sfizz_plot_curve 7 curves.sfz > curves.dat
sfz: /*empty*/

Custom curve 7 (not indexed)

run: ./build/tests/sfizz_plot_curve 7 curves.sfz > curves.dat
sfz: <curve> v0=1.0 v64=0.9 v127=0.0

Custom curve 7, omitted side points, fallback to 0.0 and 1.0 (not indexed)

run: ./build/tests/sfizz_plot_curve 7 curves.sfz > curves.dat
sfz: ` v64=0.9

Custom curve 8 (indexed)

run: ./build/tests/sfizz_plot_curve 8 curves.sfz > curves.dat
sfz: <curve> curve_index=8 v0=1.0 v64=0.9 v127=0.0

Spline curve 7 (extension)

delete relevant #if 0 in Curve.cpp
run: ./build/tests/sfizz_plot_curve 7 curves.sfz > curves.dat
sfz: <curve> sfizz:curve_interpolator=spline v64=0.75

Rebased on the new parser

What is the bug of lerpFill corrected in e58bf6f?

Any of the "Custom" test case (I missed your comment when writing them, saw it after :sweat:)
TEST_CASE("[Curve] Custom 2")
{
    auto curve = sfz::Curve::buildCurveFromHeader({
        { "v063", "1" }
    }, sfz::Curve::Interpolator::Linear);
    REQUIRE( curve.evalCC7(0) == 0.0f );
    REQUIRE( curve.evalCC7(127) == 1.0f );
    REQUIRE( curve.evalCC7(63) == 1.0f );
    REQUIRE( curve.evalCC7(2) == Approx(0.032).margin(1e-3) );
    REQUIRE( curve.evalCC7(70) == 1.0f );
}

At 63 the value obtained is 0.984. I took the opportunity to use the linearRamp SIMD thingy although it's not active on x86, but it should be a simple index issue so we can recover the original code if you prefer.
-------------------------------------------------------------------------------
[Curve] Custom 2
-------------------------------------------------------------------------------
/home/paul/source/sfizz-paulfd/tests/CurveT.cpp:119
...............................................................................

/home/paul/source/sfizz-paulfd/tests/CurveT.cpp:126: FAILED:
  REQUIRE( curve.evalCC7(63) == 1.0f )
with expansion:
  0.98437f == 1.0f

It overwrited the index 63? oh, my bad.
The current index iCurr should have been checked for fillStatus =1, and in this case, skip it.

on the else DBG(...) thing:
To fix this cleanly in all cases, the macro expansion should be wrapped into the form do { ... } while (0).
There is a discussion: https://stackoverflow.com/questions/257418/do-while-0-what-is-it-good-for

I'll let you revert it and correct it if you want. The loops that fills values are slightly tighter like this but all of this is not so critical :slightly_smiling_face: You can build it against the test suite it should cover most corner cases.

Other than this I'm OK to merge!

No it doesn't interpolate multi points correctly.
Check for instance <curve> v0=1.0 v64=0.9 v100=0.9 v127=0.0

Sorry it does work correctly... it's just me who took the wrong plotfile..

It's OK, your punition is another test case :+1:

Phew I thought I was punished to be forced to write it :smile:
It's good to merge.


Change image time to locale, add troubleshooting.md, add logo to othe…

This has a few different changes.  First of all the 'buildah images' command has been changed to show the machine local time rather than utc time for the Created Date column.   This addresses issue #537.
This PR also has the first rendition of a Buildah Troubleshooting guide listing common problems and their solutions.  Because I love our logo, I've also added it to several of our .md files.
Signed-off-by: TomSweeneyRedHat<EMAIL_ADDRESS>

bot, retest this please

LGTM
@rh-atomic-bot r+


Update the README

PR Summary
<!-- summarize your PR between here and the checklist --
Made the README better
## PR Checklist

- [X] [PR has a meaningful title](https://github.com/PowerShell/PowerShell/blob/master/.github/CONTRIBUTING.md#pull-request---submission)
    - Use the present tense and imperative mood when describing your changes
- [X] [Summarized changes](https://github.com/PowerShell/PowerShell/blob/master/.github/CONTRIBUTING.md#pull-request---submission)
- [X] [Change is not breaking](https://github.com/PowerShell/PowerShell/blob/master/.github/CONTRIBUTING.md#making-breaking-changes)
- [X] [Make sure all `.h`, `.cpp`, `.cs`, `.ps1` and `.psm1` files have the correct copyright header](https://github.com/PowerShell/PowerShell/blob/master/.github/CONTRIBUTING.md#pull-request---submission)
- [X] This PR is ready to merge and is not [Work in Progress](https://github.com/PowerShell/PowerShell/blob/master/.github/CONTRIBUTING.md#pull-request---work-in-progress).
    - If the PR is work in progress, please add the prefix `WIP:` to the beginning of the title and remove the prefix when the PR is ready.
- **User-facing changes**
    - [X] Nah
- **Testing - New and feature**
    - [X] Not Applicable or can only be tested interactively
    - **OR**
    - [ ] [Make sure you've added a new test if existing tests do not effectively test the code changed](https://github.com/PowerShell/PowerShell/blob/master/.github/CONTRIBUTING.md#before-submitting)
        - [X] [Add `[feature]` if the change is significant or affects feature tests](https://github.com/PowerShell/PowerShell/blob/master/docs/testing-guidelines/testing-guidelines.md#requesting-additional-tests-for-a-pr)

God apple phones don’t like powershell

@RDIL Please update the PR description - what is the change?


Upgrade sops to v3.7.1

..to suport AGE encryption.
#50

@lukasmrtvy Thanks! I merged #58 not realizing you've kindly submitted a PR for that before thus I'm closing this as resolved. But I appreciate your efforts!


feat: video download support

Standards checklist:

[x] The PR title is descriptive.
[x] The PR doesn't replicate another PR which is already open.
[ ] The PR has self-explained commits history.
[ ] The code is mine, or it's from somewhere with an Apache-2.0 compatible license.
[ ] The code is efficient, to the best of my ability, and does not waste computer resources.
[ ] The code is stable, and I have tested it myself, to the best of my abilities.
[ ] If the code introduces new classes, methods, I provide a valid use case for all of them.

Changes:

[...]

Other comments:
...

What is ready

Peertube link generation for video download
Working on any browser and Electron

TODO

[ ] Electron doesn't show any UI to inform about the download process
[ ] Check if Cordova works


wesnoth: 1.14.0 -> 1.14.1

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/wesnoth/versions.
These checks were done:

built on NixOS
ran ‘/nix/store/rzsmm117p5z6094z5k1ndc1v9pzms2gn-wesnoth-1.14.1/bin/wesnoth -h’ got 0 exit code
ran ‘/nix/store/rzsmm117p5z6094z5k1ndc1v9pzms2gn-wesnoth-1.14.1/bin/wesnoth --help’ got 0 exit code
ran ‘/nix/store/rzsmm117p5z6094z5k1ndc1v9pzms2gn-wesnoth-1.14.1/bin/wesnothd -h’ got 0 exit code
ran ‘/nix/store/rzsmm117p5z6094z5k1ndc1v9pzms2gn-wesnoth-1.14.1/bin/wesnothd --help’ got 0 exit code
ran ‘/nix/store/rzsmm117p5z6094z5k1ndc1v9pzms2gn-wesnoth-1.14.1/bin/wesnothd -V’ and found version 1.14.1
ran ‘/nix/store/rzsmm117p5z6094z5k1ndc1v9pzms2gn-wesnoth-1.14.1/bin/wesnothd --version’ and found version 1.14.1
found 1.14.1 with grep in /nix/store/rzsmm117p5z6094z5k1ndc1v9pzms2gn-wesnoth-1.14.1
directory tree listing: https://gist.github.com/8868591a076d925d789cd1cfb562344c

cc @abbradar for testing

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: wesnoth
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

Success on x86_64-linux (full log)
Attempted: wesnoth
Partial log (click to expand)
shrinking RPATHs of ELF executables and libraries in /nix/store/rzsmm117p5z6094z5k1ndc1v9pzms2gn-wesnoth-1.14.1
shrinking /nix/store/rzsmm117p5z6094z5k1ndc1v9pzms2gn-wesnoth-1.14.1/bin/wesnothd
shrinking /nix/store/rzsmm117p5z6094z5k1ndc1v9pzms2gn-wesnoth-1.14.1/bin/wesnoth
gzipping man pages under /nix/store/rzsmm117p5z6094z5k1ndc1v9pzms2gn-wesnoth-1.14.1/share/man/
strip is /nix/store/j75dgadrff2d1fyc4fczmcgqkid2imdx-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/rzsmm117p5z6094z5k1ndc1v9pzms2gn-wesnoth-1.14.1/bin
patching script interpreter paths in /nix/store/rzsmm117p5z6094z5k1ndc1v9pzms2gn-wesnoth-1.14.1
/nix/store/rzsmm117p5z6094z5k1ndc1v9pzms2gn-wesnoth-1.14.1/share/wesnoth/data/tools/unit_tree/update-wmlunits: interpreter directive changed from "/bin/bash" to "/nix/store/xn5gv3lpfy91yvfy9b0i7klfcxh9xskz-bash-4.4-p19/bin/bash"
checking for references to /build in /nix/store/rzsmm117p5z6094z5k1ndc1v9pzms2gn-wesnoth-1.14.1...
/nix/store/rzsmm117p5z6094z5k1ndc1v9pzms2gn-wesnoth-1.14.1

Failure on aarch64-linux (full log)
Attempted: wesnoth
Partial log (click to expand)
[ 98%] Building CXX object src/CMakeFiles/wesnothd.dir/server/server.cpp.o
[ 98%] Building CXX object src/CMakeFiles/wesnothd.dir/server/server_base.cpp.o
[ 98%] Building CXX object src/CMakeFiles/wesnothd.dir/server/user_handler.cpp.o
[ 98%] Building CXX object src/CMakeFiles/wesnothd.dir/server/simple_wml.cpp.o
[ 98%] Linking CXX static library libwesnoth-client.a
[ 98%] Built target wesnoth-client
Scanning dependencies of target wesnoth
[ 98%] Building CXX object src/CMakeFiles/wesnoth.dir/wesnoth.cpp.o
building of '/nix/store/agql4crz0b1p48x6p4k63r12z992hjy7-wesnoth-1.14.1.drv' timed out after 3600 seconds
error: build of '/nix/store/agql4crz0b1p48x6p4k63r12z992hjy7-wesnoth-1.14.1.drv' failed


Fix benchmark behavior

Results compared to prior to interior mutability:
Gnuplot not found, using plotters backend
Benchmarking bls_cache.aggregate_verify, 0% cache hits: Warming up for 3.0000 s
Warning: Unable to complete 100 samples in 5.0s. You may wish to increase target time to 51.1s, or reduce sample count to 10.
bls_cache.aggregate_verify, 0% cache hits
                        time:   [512.40 ms 516.72 ms 522.79 ms]
                        change: [-0.1042% +0.7965% +2.0013%] (p = 0.16 > 0.05)
                        No change in performance detected.
Found 9 outliers among 100 measurements (9.00%)
  5 (5.00%) high mild
  4 (4.00%) high severe

Benchmarking bls_cache.aggregate_verify, 10% cache hits: Warming up for 3.0000 s
Warning: Unable to complete 100 samples in 5.0s. You may wish to increase target time to 47.0s, or reduce sample count to 10.
bls_cache.aggregate_verify, 10% cache hits
                        time:   [464.36 ms 465.94 ms 467.72 ms]
                        change: [-8.6168% -8.2999% -7.9271%] (p = 0.00 < 0.05)
                        Performance has improved.
Found 11 outliers among 100 measurements (11.00%)
  2 (2.00%) high mild
  9 (9.00%) high severe

Benchmarking bls_cache.aggregate_verify, 20% cache hits: Warming up for 3.0000 s
Warning: Unable to complete 100 samples in 5.0s. You may wish to increase target time to 40.8s, or reduce sample count to 10.
bls_cache.aggregate_verify, 20% cache hits
                        time:   [407.63 ms 408.87 ms 410.40 ms]
                        change: [-19.863% -19.596% -19.288%] (p = 0.00 < 0.05)
                        Performance has improved.
Found 5 outliers among 100 measurements (5.00%)
  1 (1.00%) high mild
  4 (4.00%) high severe

Benchmarking bls_cache.aggregate_verify, 50% cache hits: Warming up for 3.0000 s
Warning: Unable to complete 100 samples in 5.0s. You may wish to increase target time to 25.6s, or reduce sample count to 10.
bls_cache.aggregate_verify, 50% cache hits
                        time:   [258.91 ms 259.95 ms 261.08 ms]
                        change: [-49.998% -49.686% -49.347%] (p = 0.00 < 0.05)
                        Performance has improved.
Found 5 outliers among 100 measurements (5.00%)
  5 (5.00%) high mild

bls_cache.aggregate_verify, 100% cache hits
                        time:   [2.1386 ms 2.1594 ms 2.1925 ms]
                        change: [+3.8251% +5.2293% +7.0844%] (p = 0.00 < 0.05)
                        Performance has regressed.
Found 1 outliers among 100 measurements (1.00%)
  1 (1.00%) high severe

Benchmarking bls_cache.aggregate_verify, no cache: Warming up for 3.0000 s
Warning: Unable to complete 100 samples in 5.0s. You may wish to increase target time to 26.6s, or reduce sample count to 10.
bls_cache.aggregate_verify, no cache
                        time:   [266.31 ms 267.23 ms 268.25 ms]
                        change: [-1.3208% -0.5508% +0.1486%] (p = 0.14 > 0.05)
                        No change in performance detected.
Found 4 outliers among 100 measurements (4.00%)
  2 (2.00%) high mild
  2 (2.00%) high severe

I think we're abandoning the target branch and picking the parts we want to keep into separate PRs. I don't believe this issue of the benchmark exists in main


disc: banning peer does not work

Describe the bug
If we get disconnected from a remote peer, we ban it, but the banning mechanism doesn't work. Example trace:
// We get disconnected due to too many peers

2022-12-20T19:04:06.617861Z ERROR start_pending_outbound_session{remote_addr=<IP_ADDRESS>:30303}: reth_eth_wire::p2pstream: Disconnected by peer during handshake: Too many peers
2022-12-20T19:04:06.618009Z  WARN net: Outgoing pending session failed remote_addr=<IP_ADDRESS>:30303 peer_id=0x0bc93319baa713e64285af358e423ea8379c707a813601d157242825d5d6840bc06a2712f16e2b923c3f45e664401a6f41a9d1db715debf6ca6f0bb6bdb78ae6 error=Some(Eth(P2PStreamError(HandshakeError(Disconnected(TooManyPeers)))))

// The peer is banned
2022-12-20T19:04:07.012543Z  WARN net: Outgoing pending session failed remote_addr=<IP_ADDRESS>:30303 peer_id=0x0bc93319baa713e64285af358e423ea8379c707a813601d157242825d5d6840bc06a2712f16e2b923c3f45e664401a6f41a9d1db715debf6ca6f0bb6bdb78ae6 error=Some(Ecies(IO(Os { code: 54, kind: ConnectionReset, message: "Connection reset by peer" })))
2022-12-20T19:04:07.012571Z DEBUG net: Banning discovery peer_id=0x0bc93319baa713e64285af358e423ea8379c707a813601d157242825d5d6840bc06a2712f16e2b923c3f45e664401a6f41a9d1db715debf6ca6f0bb6bdb78ae6 ip=<IP_ADDRESS>
2022-12-20T19:04:07.012602Z DEBUG discv4: removed node node_id=0x0bc93319baa713e64285af358e423ea8379c707a813601d157242825d5d6840bc06a2712f16e2b923c3f45e664401a6f41a9d1db715debf6ca6f0bb6bdb78ae6

// Again
2022-12-20T19:04:07.996832Z  WARN net: Outgoing pending session failed remote_addr=<IP_ADDRESS>:30303 peer_id=0x0bc93319baa713e64285af358e423ea8379c707a813601d157242825d5d6840bc06a2712f16e2b923c3f45e664401a6f41a9d1db715debf6ca6f0bb6bdb78ae6 error=Some(Ecies(UnreadableStream))
2022-12-20T19:04:07.996854Z DEBUG net: Banning discovery peer_id=0x0bc93319baa713e64285af358e423ea8379c707a813601d157242825d5d6840bc06a2712f16e2b923c3f45e664401a6f41a9d1db715debf6ca6f0bb6bdb78ae6 ip=<IP_ADDRESS>

Steps to reproduce
Run reth with RUST_LOG=debug
Node logs
// We get disconnected due to too many peers

2022-12-20T19:04:06.617861Z ERROR start_pending_outbound_session{remote_addr=<IP_ADDRESS>:30303}: reth_eth_wire::p2pstream: Disconnected by peer during handshake: Too many peers
2022-12-20T19:04:06.618009Z  WARN net: Outgoing pending session failed remote_addr=<IP_ADDRESS>:30303 peer_id=0x0bc93319baa713e64285af358e423ea8379c707a813601d157242825d5d6840bc06a2712f16e2b923c3f45e664401a6f41a9d1db715debf6ca6f0bb6bdb78ae6 error=Some(Eth(P2PStreamError(HandshakeError(Disconnected(TooManyPeers)))))

// The peer is banned
2022-12-20T19:04:07.012543Z  WARN net: Outgoing pending session failed remote_addr=<IP_ADDRESS>:30303 peer_id=0x0bc93319baa713e64285af358e423ea8379c707a813601d157242825d5d6840bc06a2712f16e2b923c3f45e664401a6f41a9d1db715debf6ca6f0bb6bdb78ae6 error=Some(Ecies(IO(Os { code: 54, kind: ConnectionReset, message: "Connection reset by peer" })))
2022-12-20T19:04:07.012571Z DEBUG net: Banning discovery peer_id=0x0bc93319baa713e64285af358e423ea8379c707a813601d157242825d5d6840bc06a2712f16e2b923c3f45e664401a6f41a9d1db715debf6ca6f0bb6bdb78ae6 ip=<IP_ADDRESS>
2022-12-20T19:04:07.012602Z DEBUG discv4: removed node node_id=0x0bc93319baa713e64285af358e423ea8379c707a813601d157242825d5d6840bc06a2712f16e2b923c3f45e664401a6f41a9d1db715debf6ca6f0bb6bdb78ae6

// Again
2022-12-20T19:04:07.996832Z  WARN net: Outgoing pending session failed remote_addr=<IP_ADDRESS>:30303 peer_id=0x0bc93319baa713e64285af358e423ea8379c707a813601d157242825d5d6840bc06a2712f16e2b923c3f45e664401a6f41a9d1db715debf6ca6f0bb6bdb78ae6 error=Some(Ecies(UnreadableStream))
2022-12-20T19:04:07.996854Z DEBUG net: Banning discovery peer_id=0x0bc93319baa713e64285af358e423ea8379c707a813601d157242825d5d6840bc06a2712f16e2b923c3f45e664401a6f41a9d1db715debf6ca6f0bb6bdb78ae6 ip=<IP_ADDRESS>

Platform(s)
Mac (Apple Silicon)
Code of Conduct

[X] I agree to follow the Code of Conduct

@mattsse ptal

what's the commit you're on @jonasbostoen ?

#2dc5b80ef0045186e1de4baa92b5f519a49477ea

ah okay, I see what's happening.
This is a non-fatal error but clearly it doesn't make sense to try to connect again when the peer is clearly busy, so we should put it in timeout for a while.

Yes, these things happen quite frequently and with a lot of peers at the same time, so a timeout would be more efficient


Update ACE editor to 1.35.2 - fixing the JSDoc bug

Fixing: #159

Big thank you to @mkslanc for fixing the bug and @InspiredGuy for approving and merging it.


CLI is not working properly

This is  a bug.
Prerequisites

[x] Are you running the latest version?
[x] Are you reporting to the correct repository?
[x] Did you check the documentation?
[x] Did you perform a cursory search?

Description
After set all options and generate the files, only the migration is done.
I'm using Enso version 2.13.7 (commit e68f80d07d43efe81fd06743cb42f159aa82769e), on Laradock, version of Sat Oct 27, commit 538b6aa0cd484c475c5c537a763e4e1fe330fcae.
Steps to Reproduce

php artisan enso:make:structure
set all options
generate files

Expected behavior
To have new files for Form, Model, etc.
Actual behavior
Only the migration is created

This means that you did not configure the files to be generated. By default only the structure migration is created.
(as instructed)

I'm sorry! it's true, it's a little embarrassing.... I've tested several times, and always I jumped that step.
Thanks!


type parsing failed: dateTime

element_string: type parsing has failed: ' .' / 'http://www.w3.org/2001/XMLSchema#dateTime'

Do you have an example input triple?

These errors are spit out without the underlying context, but I am using a Wikidata NT dump and these are some example triples that may be setting it off:
https://www.wikidata.org/wiki/Special:EntityData/Q31 http://schema.org/dateModified "2023-04-07T08:06:07Z"^^<http
://www.w3.org/2001/XMLSchema#dateTime> .
http://www.wikidata.org/entity/statement/Q31-e89a40c1-4d8e-cf38-95bd-3e383542ff7a http://www.wikidata.org/prop/qualifier/P585 "2010-01-01T00:00:00Z"^^http://www.w3.org/2001/XMLSchema#dateTime .

Also, http://www.wikidata.org/wiki/Special:EntityData/Q31 (http not https) creates the intended data structure, though it will work (badly) with https.

I don't actually know what statement is causing this error. It is possible the one I extracted is fine. The fundamental problem is that these errors are being spit out without disclosing the data causing them, so I can't give you reliable information.

I made the error output a bit more clear, and the whole thing a bit faster as well. Have a try please.

I am getting a lot of messages saying "Getting DB connection..." It appears to nonetheless be working since tables are being created, but this is flooding my output and making the interesting messages difficult to find.

Forgot a debug message, fixed now.

I switched all the println error output to eprintln for stderr. I now see what you mean with the errors. Will debug.

I pulled and built the latest version, and the database connection spam is thankfully gone, but as before, the parsing errors are presented without the original context.

Added better error messages, also fixed two parser errors (huge years in time values, and non-earth coordinates), please try again

I pulled the latest repo, rebuilt with cargo build, and then ran target/debug/wdqsbe --import ~/wikidata-20230417-all-BETA.nt. It is now quiet, but it has also been running for several days, and I am not sure it's making any progress at all; my database folder isn't getting any bigger.


NFC support

Closes #228

Really!? That easy?
I will see if I can find time in the next days to test this.
Thanks!!


bug Fail to download training-parallel-corpora-common-crawl

Description
When I tried to run the example about the EN-DE translation, I obtained this error
tensorflow.python.framework.errors_impl.UnimplementedError: File system scheme 'http' not implemented (file: 'http://www.statmt.org/wmt13/training-parallel-commoncrawl.tgz')

…

TensorFlow and tensor2tensor versions
TF 1.7 T2T 1.5.7

…

In case of bug report: Steps to reproduce the problem

…

In case of bug report: Error log

…

is this problem fixed? I encounter the same problem.


Document the release process in CONTRIBUTING.md

These steps were assembled from the comments in:

https://github.com/OctoLinker/browser-extension/pull/136
https://github.com/OctoLinker/browser-extension/pull/137
https://github.com/OctoLinker/browser-extension/pull/138

Looks good, just two minor comments. Thank you 👍

Needs a rebase. Do you know why we can't update the branch directly on Github like we do for others?

Oh, the Update branch button was enabled just now. Maybe there was some backend delay earlier?


The VM description is duplicate in annotations

Steps to reproduce:

Create a VM filling something in the description
After the VM is created, check on the VM detail page

The description is duplicate in annotations
Results:

[x] 1. The description is added as an annotation, nothing is populated in description

[x] 2. Edit description filling something in and save, another annotation is added

[x] 3. Erase the description content then save it, the annotation description is not deleted accordingly

Suggestion:
Though the description is saved as an annotation, it makes no sense to display it in annotations, because a description has been provided

The description is still only added to annotations, I suppose that the description should be only shown in the description but not in annotations.

@DoNotSayYes Please validate it again, thanks!

Is that necessary to display the description again in annotations? Maybe suppress it in annotations, just displaying in the description would be better? @DaiYuzeng

@DoNotSayYes Sorry, could you tell me how to reproduce it? In my environment , it isn't displayed in the annotation modal.

Or could you provide me the environment which can reproduce. Thanks!

annotations modal was removed from the details page of vm.

Label & Annotation tab has been removed


[#136783629] SSL between router ELB and HAProxy

What
Story: How do encrypt traffic between the elb and gorouter using haproxy
As part of DIT onboarding, we want to encrypt all communications. This PR enables SSL on HAProxy.
The following PR https://github.com/alphagov/paas-cf/pull/715 will change the backend port on the ELB to use this SSL port. It was separated in 2 PRs to create minimal downtime.
Depends on https://github.com/alphagov/paas-haproxy-release/pull/8
How to review

Deploy
Make sure all tests pass

Before merging

Merge https://github.com/alphagov/paas-haproxy-release/pull/8
Copy the output from the build-final-release job at https://concourse.build.ci.cloudpipeline.digital/teams/main/pipelines/paas-haproxy
Update commit [TEMP] Use haproxy release with SSL with the final release
Merge

Who can review
Not @keymon or me

It failed on availability tests. I think we need to change the way we deploy haproxy.
 - Duration: 1m5.599998702s, Requests: 657, Non 200 Requests: 311, Success Rate: 52.66%
 - Duration: 1m10.599998702s, Requests: 707, Non 200 Requests: 361, Success Rate: 48.94%
``

Ok, this deploys correctly now. I've updated the TMP commit with final haproxy release.

Merging.


stops working after awhile

Expected Behaviour

keep working until quit
Actual Behaviour

stops working after awhile
tray icon becomes unresponsive, have to quit from task manager
Reproduction steps

for me, it just happens
Frequency

everyday
Aurora Version:

v41
Previously an Issue?

Yes

2022-05-25 19.46.00.log

can you share your profile with me? Logs don't show anything sadly

I'm only using the default desktop profile

Happens to me as well, usually after the computer wakes up from sleep.

I've tried to solve this before and I couldn't. I hope someone with better experience can solve this one :(

Sorry I've not been able to check this issue. Usually how long does it run before Aurora closes?
Can you check the latest version, it had small improvements with window handles

can you try this fix?
https://github.com/Aurora-RGB/Aurora/issues/63#issuecomment-1200134725

Okay then can you show me event log from "Event Viewer" like the guy from that thread? Right after aurora closes
https://www.howtogeek.com/123646/htg-explains-what-the-windows-event-viewer-is-and-how-you-can-use-it/

can you try latest dev version?

This is an error that's source can't be found easily. I remember much earlier I made a workaround fix for someone else
open %appdata%/Aurora and edit Config.json and change "close_on_exception" value to false and you won't be bothered with the error again but Aurora might become unstable


Consistent use of else after return (pylint no-else-return)

While working on some pylint warnings in tensorflow/python/keras/backend.py I noticed that two different ways of "if else return" styles are used.

if condition: return 0
return 1
if condition: return 0
else: return 1

Is changing the behaiviour to one of the variants considered good practice?
I would like to clear things up (and improve the pylint score :D ).

Both behaviours appear in the PEP 8 style guide (look up "be consistent in return statements." on this page), so I do not believe there is a preferred one per se, at least not in this guide.
That being said, in my humble not-a-tensorflow-developer opinion, you should (in accordance with PEP-8 principles) use the alternative that feels best as to readability and comprehensibility based on context. Parsimony would ask to do as pylint suggests, getting rid of useless else statements, but there might be cases in which this statement actually improves the reader's comprehension of what is happening, in which case you should probably keep it. If you worry about pylint scores, you can always add a pylint command in comment on those specific cases.

Alright, thanks for clarifying!


Use different constructor that gradle still supports

Before this PR
Using an internal constructor of AbstractPolymorphicDomainObjectContainer that has disappeared in gradle nightly, as of https://github.com/gradle/gradle/pull/7876
After this PR
Use a different constructor from DefaultPolymorphicDomainObjectContainer that gradle seems to still support, because nebula.lint is using it and they're using nebula.lint as part of their CI pipeline.
Sadly, this is still quite brittle and need to verify if this works on any gradle 4.x.
Edit: verified this constructor has existed since like 2.3 (added in https://github.com/gradle/gradle/commit/18833dc8eefdf5f4fb862178cc1e118445f69d61), and definitely there in gradle 4.x:
https://github.com/gradle/gradle/blob/v4.0.0/subprojects/core/src/main/java/org/gradle/api/internal/DefaultPolymorphicDomainObjectContainer.java#L35-L37

@tkrullmann mind taking a look when you've got a chance?

Looks good, thanks!
It's unfortunate that even though polymorphic containers are part of the public API, there is still no public way to construct them.


Russian characters problem

Hello!
I am using version 0.21.3, but I also tried: 0.21.25 and 1.0-234-d1a2b53, it's not resolve a problem.
My code:
  def kafkaRoutes(): HttpRoutes[IO] = {
    HttpRoutes.of[IO] {
      case req@GET -> Root / Constants.SUBSCRIBE =>
        req.decode[String] {
          message => Ok(message)
        }
    }
  }

If i got message with Russian characters, after .decode i have question marks instead of symbols.
For example what i have in message

evtVersion=test,????=????,prevEvtID=test

I try use method decodeText EntityDecoder.decodeText(req).unsafeRunSync()
Add in code import scala.concurrent.ExecutionContext.Implicits.global
Or change headers like Content-Type: "text/plain ; charset=UTF-8" or Content-Type: "'application/json;charset=UTF-8'"
But nothing help.
What my mistake and how it can fix?
With Best Regards!

Is your body UTF-8 encoded?  This works for me:
import cats.effect._
import org.http4s._
import org.http4s.dsl.io._
import org.http4s.implicits._

object Anton extends IOApp {
  val routes = HttpRoutes.of[IO] {
    case req =>
      req.decode[String] {
        message => Ok(message)
      }
  }

  val req = Request[IO]().withEntity("Здравствуйте".getBytes("UTF-8"))

  def run(args: List[String]): IO[ExitCode] = {
    routes
      .orNotFound(req)
      .flatMap(resp => resp.as[String])
      .flatMap(IO.println)
      .as(ExitCode.Success)
  }
}

Output:
sbt:dsl> run
[info] compiling 1 Scala source to /Users/ross.baker/src/http4s/dsl/target/scala-2.12/classes ...
[info] done compiling
[info] running Anton
Здравствуйте
[success] Total time: 6 s, completed Sep 15, 2021 2:18:51 PM

Would it be possible to capture a binary dump of your message that's failing?


Add --enable-lv2 support?

Hi,
I want to do noise suppression with ffmpeg rnnoise model, like described in this post. Can you show me how to do that, or maybe included this in your script?
If I simply included --enable-lv2 in ffmpeg configure, it shows this error:

ERROR: lilv-0 not found using pkg-config

I couldn't get it working modifying the shell script in this repo.
So I installed  sudo apt install liblilv-dev and followed the official ffmpeg ubuntu compilation guild with the --enable-lv2 flag, it worked.

...What do I need to modify in the script, to ensure that ffmpeg will output 10-bit color files on a MacBook Pro? Or, is encoding 10-bit video on a MacBook Pro impossible?

Added with commit 3563a1cc5365409b51f497f71be6a0391c908c02.


Make initialstate.NET available as a NuGet package

Probably the simplest way to integrate third party libraries like this one into your project is to use the NuGet package manager (if a NuGet package is available).  initialstate.NET needs a NuGet package.

Hey @dwyban, I'd like to take this on if no one else is yet!

@dwyban I'll need to know a licence URL, project URL, icon URL, and some tags for the package otherwise they will be left blank

@dwyban I'll also need to know your organization's NuGet API key in order to publish this. If you do not feel comfortable doing this, I can provide everything you'll need and the documentation on how to get the package publish. It takes 5 minutes if that when you have the API key

Let me consult with our open source office and get back to you.

Hi @atrievel.  I'm still learning about how to go about creating a NuGet package for this project and after talking with our OpenSource office I think due to account security reasons we're going to have to handle this one internally.  Thank you for offering to help though.

No worries @dwyban! Here’s some helpful documentation to get you guys started. It’s not too complicated of a process. Best of luck 👍

Looks like I was able to get it published under my own account so this is working.
https://www.nuget.org/packages/InitialState.NET/
Will need to remove and get it published under Tek's account.


Added module for Split Payments extension

Added module for Split Payments extension. Module allows you to:

Get list of target wallets
Add target wallets
Delete all target wallets

P.S.
Also added test examples for pay lnurl and paylnaddress in test_userwallet.py (To-do in #142)

Thanks for your pull request. I'm asking a few to test it and will get back to you soon

@Mccalabrese, please review. thanks

Bump. @Mccalabrese

Split payments test ran successfully 👍

@jimasuen i have just been slow here; sorry about that. let me see if i can get this merged in today


TagBot trigger issue

This issue is used to trigger TagBot; feel free to unsubscribe.
If you haven't already, you should update your TagBot.yml to include issue comment triggers.
Please see this post on Discourse for instructions and more details.

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/24813

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/25002

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/115885

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/118005

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/119658

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/120482


Testing issue

gcc -dynamic  -o  atomics  obj/atomics-c.o -Wl,--as-needed -Wl,--rpath=/home/user/.config/trizen/sources/libxsmm/src/libxsmm-1.17/lib/ -L/home/user/.config/trizen/sources/libxsmm/src/libxsmm-1.17/lib/ -lxsmmnoblas -Wl,--no-as-needed -Wl,--rpath=/usr/lib/ -L/usr/lib/ -lblas -Wl,--rpath=/usr/lib/ -Wl,--gc-sections -Wl,-z,relro,-z,now -Wl,--rpath=/usr/lib/ -Wl,--gc-sections -Wl,-z,relro,-z,now -Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now -Wl,--as-needed -lm -lrt -ldl -Wl,--no-as-needed -fopenmp -Wl,--as-needed -lstdc++ -Wl,--no-as-needed -pthread
/usr/sbin/ld: obj/atomics-c.o: in function `main':
/home/user/.config/trizen/sources/libxsmm/src/libxsmm-1.17/tests/atomics.c:54: undefined reference to `pthread_yield'
collect2: error: ld returned 1 exit status
make[1]: *** [Makefile:115: atomics] Error 1
make[1]: *** Waiting for unfinished jobs....

OS: Arch Linux
gcc: 12.1.1

Confirmed. This is fixed in our master revision. I am currently considering v1.18 to bring back this and perhaps some other updates. The consideration depends on when we are ready for our mighty v2.0 release (which competes with this task). Note, this issue is due to the new GCC compiler and runtime libraries which were never tested with our v1.x release.

We rather release 2.0 by begin of 2023 rather than releasing v1.18.


Reverse Behavior

I used the example LED. However, the board LED lights up when I activate the LED in HomeKit and not the external one. I suspect that I need to change to gpio_write(led_gpio, on ? 1 : 0), but I don’t know how to with vagrant.

There are two ways to connect an LED: 1) pin, resistor, LED, ground; 2) power, resistor, LED, pin. In first case you need to set pin high to light up LED, in second - low. Usually pins can sink more current than they can source, so second option is used to get LED brighter.
Not sure I understand the problem with Vagrant.

Ok, maybe I missread the wuestion. If what you were saying is you want to blink with a different LED, you need to change led_gpio to pin number your other LED is connected to.

It's working.  My mistake was that I wired the LED like this:
Pin, resistor, led, ground.

Make sure you preserve polarity on LED, shorter leg goes to ground.


Always crash when the source folder fails to copy

Add meaningful message to help users debug it

Codecov Report

Merging #148 into master will decrease coverage by 0.01%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master     #148      +/-   ##
==========================================
- Coverage    52.2%   52.18%   -0.02%
==========================================
  Files          58       58
  Lines        4611     4612       +1
==========================================
  Hits         2407     2407
- Misses       1897     1898       +1
  Partials      307      307

Impacted Files
Coverage Δ

cli/cli_app.go
44.61% <0%> (-0.14%)
:arrow_down:

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 5fc5072...b75fe90. Read the comment docs.


Scripts to leverage OSM for baremetal provisioning

What this PR does / why we need it:
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

/approve

/lgtm


Datepicker: Range causes 'minimumNumber' error

Describe the bug
When passing a range to the datepicker component, the error "Pass the property of 'minimumNumber' with value in the RangeConfig, otherwise it won't work." is thrown and the component fails to update it's value when the user selects a date.
To Reproduce
Component
import { DateRange } from '@acpaas-ui/js-date-utils';

public clickedDate: Date = new Date();
public range: DateRange = [1, 6];

selectDate(event) {
    if (event.complete) {
        this.clickedDate = event.date;
    }
}

View
<aui-calendar
    [range]="range"
    [selectedDate]="clickedDate"
    (selectDate)="selectDate($event)">
</aui-calendar>

Screenshots

Expected behavior
No error should be thrown.
OS (please complete the following information):

OS: Windows 10
Browser Chrome
Version 77

This is an error caused by reactive-form-validators, because it thinks the range attribute is a request for validation and misinterprets it. It works fine when using <aui-date-picker> and <aui-calendar> and the range attribute without that framework. It is not a bug in acpaas ui.
You could try setting minimumNumber: -1 and maximumNumber:<PHONE_NUMBER> properties on the DateRange array to make it always pass the range validation, or to override the validation behavior somehow to disable the range validation (I'm not familiar with this validation framework).


Test RangeDict uniqueness cannot be broken by exhausting a Range in it

Start with a RangeStream with a _ranges RangeDict initialised as the full range, e.g. [0,11) for the example text file.
Read the entire Range with stream.read()

which will change the tell() of the active range to 11
which will change the ranges() RangeDict entry for the active range to an empty range

Test to determine that it is not possible to register a duplicate key for the initial, full, range [0,11), and clarify why this is undesirable

Currently it is permitted to reassign a range after it has been read, and this behaviour is documented by a test: see c7c4a6bbdcef3838b874d9972c77583038d62cf5


Add moon icons for night time

hello!
great plugin, I'm loving it so far!
One thing that keeps bothering me is when it's night but the icon keeps showing the sun. I think it's because it wants to tell us that "it's clear sky outside", but I'd like to add the proper icons for the night time. Can you tell me where should I start looking for? I'm pretty n00b with tmux plugins, but I think that I can accomplish something with enough trial and error :smile:
Thanks!

Hi @betoharres, thanks for your review :)
The plugin just obtains the data from https://wttr.in and shows it as it is. Unfortunately, here is no special post-processing.
But wttr.in has some customizations here, please take a look, maybe you'll find something useful.
Another thing, get_weather function returns the string representation from wttr.in API, so perhaps you could find an emoji symbol there and replace it with a correct night representation if it's night.


GithubRelease

Changes
NUKE: GithubRelease stage should not attempt to run during normal merges / PR validation #50

This is the totally wrong way to do this.


Suggestion: API guidance

I'm assuming we could create, update, delete Asset hierarchy/models etc using the Managed Objects API. Is that correct?
Is there any documentation for JSON schema other than reverse engineering it from the sample https://github.com/SoftwareAG/cumulocity-digital-twin-manager/blob/main/samples/sample-asset-models-for-vaccum-factory or exported models
We'd like all of our changes in Cumulocity to be scriptable.

Hi,
We are internally discussing to have built API's for assets/modes/properties. Once the API is available we would support any CRUD operation on these objects. Currently we can reverse engineer and use inventory API to create these objects. But once the API is available we would recommed to use the API instead of any custom implementation and usage of the domain data model.


Please add support for the Electriq CD12PW

Good day,
Is it possible to add support for this model, I have a feeling it's largely the same as existing models?
I found this: https://templates.blakadder.com/electriq_CD12PW.html

The information at that link is about the protocol between the ESP8266 and another microcontroller.  Although it is likely to be similar to the Tuya level protocol, it is quite common to have mapping of string values at Tuya protocol level to integers at the internal protocol level.  So some logs from attempting to configure the device would be useful.
You may also find if you configure it that it is a close enough match to one of the other ElectriQ CDPRO models to work with an existing configuration.

This looks similar enough to the CD25PRO that it should get detected as that and partially function.  There are some difference in the number and labelling of presets though that might limit the compatibility a bit.  But I'll need further details on the actual lpreset names observed in the logs to make a custom config that works fully for this device.

This is now in 0.11.3, if there are any issues with it, or you find additional info, please open a new issue.


July Rediesign: /join page

Following along with the Figma details for the /join page:

Added the words linking to the new /helpout page
Following the new style, removing bullet points and  text around all the roles

Moved to draft until the /helpout page is ready. The central change here is the link to the new /helpout page so we can't have that broken link there.


[BUG]

Office Tool Plus Version, e.g. <IP_ADDRESS>:

<IP_ADDRESS>

Operating System, e.g. Windows 10 20H2 or Windows 7 SP1:

版本：Windows 10 专业版
版本号：22H2

Error description (required):

部署的office版本与实际安装的版本不同。
例如，当选择部署office家庭和学生版2016时，实际安装的是office standard 2019
Reproduction steps (suggested):

Screenshot (suggested):

Additional information (optional):

A feature of the new Microsoft Office is to use old activation licenses if another product was previously installed.
The product type is checked in the registry.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\ClickToRun\Configuration
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\16.0\ClickToRunStore
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\ClickToRun\Inventory\Office\16.0
ProductReleaseIds

A feature of the new Microsoft Office is to use old activation licenses if another product was previously installed.
The product type is checked in the registry.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\ClickToRun\Configuration
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\16.0\ClickToRunStore
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\ClickToRun\Inventory\Office\16.0
ProductReleaseIds

There was another answers I think.


Inconsistency with Swift's standard naming conventions

I have the feeling that, in the spirit of Swift's standard library (and Foundation) it should be:
HTML
CSSSelector
HTTPPipeline
etc..

instead of
Html
CssSelector
HttpPipeline
etc..

examples from Stdlib/Foundation:
String.UTF8View
URLSession
etc...

Going to close this since it's a bit stale. We've preferred the unconventional naming since it's an easy rule to follow, but perhaps we should revisit the discussion sometime.


proposal: encoding/xml: add flag for stricter XML char parsing

Proposal Details
Background
As reported by @DemiMarie
The encoding/xml package does not properly validate that the characters within comments, processing instructions, or directives are properly within the CharData range as defined by the XML specification.
Proposal
Add a godebug flag, xmlvalidatechars=1, which enables more strict validation of characters within comments, processing instructions, and directives. It is my understanding that changing XML behavior can sometimes lead to unexpected behavior/breaking changes, but I have tested what would happen if this flag were enabled by default internally and ran into zero issues.

Related Issues and Documentation

proposal: encoding/xml: ignore invalid characters when Decoder.Strict is false #62217

(Emoji vote if this was helpful or unhelpful; more detailed feedback welcome in this discussion.)

I’d prefer if strict validation were on by default, at least eventually if not initially.  Would this be possible, or would it break the Go 1 stability guarantee?

Making encoding/xml do strict validation by default would be OK with the Go 1 compatibility guarantee.  Adding the GODEBUG would give people an easy way to back off.
That said: why would strict validation be a good default?  Who would that help in practice?

Making encoding/xml do strict validation by default would be OK with the Go 1 compatibility guarantee. Adding the GODEBUG would give people an easy way to back off.
That said: why would strict validation be a good default? Who would that help in practice?

XML with malformed characters is ill-formed, so the Principle of Least Astonishment suggests that it should be rejected.

XML with malformed characters is ill-formed, so the Principle of Least Astonishment suggests that it should be rejected.

If we were starting from scratch, I would certainly agree.  But we aren't.  Making this change will most likely break some existing working code, which in an ecosystem that stresses backward compatibility is astonishing in a different way.

XML with malformed characters is ill-formed, so the Principle of Least Astonishment suggests that it should be rejected.

If we were starting from scratch, I would certainly agree. But we aren't. Making this change will most likely break some existing working code, which in an ecosystem that stresses backward compatibility is astonishing in a different way.

Would it be better to create a new XML parsing entry point and mark the old entry points as deprecated?  There are a ton of problems in encoding/xml and absolutely strict well-formedness checking might break a lot of code.

I think that we should have a plan for encoding/xml/v2.  It's clear that there are many problems with encoding/xml.  But that is a big undertaking.
In the meantime, we need to decide about this proposal, which is not about v2.

I think that we should have a plan for encoding/xml/v2. It's clear that there are many problems with encoding/xml.

:+1:

But that is a big undertaking.

:100:

In the meantime, we need to decide about this proposal, which is not about v2.

Fair!
You have much more experience than I do when it comes to the Go ecosystem, so I think it would be better for you to make this decision.  Other options include adding an extra flag field or setter method.

This proposal has been added to the active column of the proposals project
and will now be reviewed at the weekly proposal review meetings.

Just to make sure I understand, the specific part of the XML specification you're talking about validating is the Char non-terminal as used in Comment, PI, and CData, right? This is what CL 601815 implements.

There are many ways in which encoding/xml is not as strict as it ought to be. Making it stricter in any way presents compatibility problems, and I don't think we want to introduce separate GODEBUGs for every way it could be stricter. At the same time, we're not going to tackle all of the ways it could be stricter at once (we probably don't even know all of the ways!), so it's not practical to just have a big switch for stricter parsing.
It's also not clear that a GODEBUG is the right way to control this. GODEBUG is very coarse-grained. We already have decoder configuration in the encoding/xml.Decoder type, so this would seem to be a natural place to put control over this. However, encoding/xml.Decoder already has a Strict field and, unfortunately, it already defaults to true! We're not going to add a Stricter field. :)
So here's a counter-proposal: we add a Lax field to Decoder (I'm open to better names) that's a bit-field of ways in which the parser should be non-strict. That way, the Strict field continues to default to true, but we tweak it to mean "be as strict as you can about parsing, except in the ways specified by the Lax field". For XML char parsing, we'd define a bit in the Lax bitfield, say LaxChars. For compatibility, this bit would be set by default in the Lax field. Any other ways we make the parser more strict in the future would get their own bits. If an XML consumer wants the strictest possible parsing, it can set Lax to 0. It a consumer wants to be strict, but knows there are some issues in the data it's parsing, it can set Lax to just the bits that make sense for what it's parsing. If a strictness check in the XML decoder fails, it can report a helpful error like "consider setting LaxChars". Finally, we could define one GODEBUG, say xmllax, that can take a list of the bitfield names, such as xmllax=chars,etc, to override the default value of the Lax field.

If Lax is 0, for compatibility sake, the Decoder must behave as it currently does. Because a new field with existing code will be defauting to 0.

The zero value of Decoder is already not usable. You have to call NewDecoder. So in this case we don't have the constraint that new fields need to default to 0.
But I definitely see your argument that Lax is sort of a double-negative.
What I'm trying to avoid is having Strict: true mean the fairly arbitrary set of ways in which encoding/xml happens to be strict as of 2024. Maybe at some level that's unavoidable.
One thing I like about Lax is that it's really easy to ask for "the strictest parsing this version of Go can do" by just setting Lax to 0. With a "Stricter" approach, I think we're need to define some other way to ask for the strictest thing; whether that's a const who's value can change in newer versions, or a function/method.
Orthogonally, this doesn't have to be a bit field. It could be a set of bool fields.


line-height is defined at html and body with differents values

Same as old https://github.com/twbs/bootstrap/issues/24964
The bootstrap-reboot.css defines:
html {
  /** ... */
  line-height: 1.15;
  /** ... */
}

/** ... */

body {
  /** ... */
  line-height: 1.5;
  /** ... */
}

And it seems non-sense. The original post, @mdo said that It's part of Reboot and there as part of a global browser reset, forked from Normalize. Leaving for now.
It is not part of normalize.css currently, but I do not know if before was, anyway, maybe is time to fix it?

This was fixed in #28698 and is coming in v5.

https://github.com/twbs/bootstrap/issues/30645#issue-606540381


extra_context via the command line?

@michaeljoseph's work on #260 & #274 introduced the extra_context parameter and at one point an --override option to set extra_context vars via the command line, it was suggested that perhaps --parameter would be better, but ultimately @audreyr decided against including either at the time (per https://github.com/audreyr/cookiecutter/pull/260#issuecomment-54107644 )
Any new thinking on this? I personally find it a bit jarring to be prompted for every single template var when I only really care about the repo/project name (for example). --no-input is part of the solution, but the other part is being able to set template vars from the command line.
For now I'll likely hook up a small wrapper script to call out to the cookiecutter module, so no huge deal -- mostly just trying to keep the conversation open.

I'd really like this - I have exactly the same use case: I just want to take a project name and then generate the class name, repo name etc. from that using the default behaviour.

The work is there in #400.

Closing this as resolved.


[Bug]: Class name must be a valid object or a string

What happened?
Error after installation on
resources/views/vendor/filament-email-2fa/email-sent.blade.php :4
Class name must be a valid object or a string
@lang('filament-email-2fa::filament-email-2fa.email_sent', ['email' => $this->getUser()->email])
How to reproduce the bug
install
submit login form
above error and all site is broken
PS. 2fa code saved in db
Package Version
1.0.2
PHP Version
8.2.19
Laravel Version
11.10.0
Which operating systems does with happen with?
macOS
Notes
No response

I fixed the bug...
please let the super admin login to finish configurations i didn't even had email setup I took the code from db :))
location /vendor/solution-forest/filament-email-2fa/src/Pages/TwoFactorAuth.php
    public function getUser()
    {
        $guard = $this->getCurrentGuard();
        //$model = config("auth.providers.{$guard}.model");

        $model = config('auth.providers.users.model');

        $user = $model::where('email', $this->email)->first();

        return $user;
    }


Make sources a global option

Sources need to be split into global section and these options would move to source settings
Originally posted by @Harjot1Singh in https://github.com/ShabadOS/desktop/issues/204#issuecomment-592205976

Marked as high since this could very well speed up the UI by not loading all translations at once.


cmake: backport gasnet detection

@gshipman @ipdemes , this should fix our gasnet mess!

I'll go ahead and merge this, as y'all are the only ones using the cmake branch.  @ipdemes, did you get a chance to see if the master branch's cmake build worked well enough for y'all to switch back to that?

As for the last week's repository, master branch didn't work for us. I am working on rewriting our legion mapper to be able to use master.


remove deprecation warning

deprecation warnings
lifespan instead of startup and shutdown event
handle some pylint warnings
isort again

TO MERGE IN WIP_187 FIRST


[#294] Link d.ts file in package.json

Change to d.ts so that Typescript / Node doesn't get confused by the d.mts extension.
Also, install @types/node as a devDependency. Without node typings, src/stores/utils/jwt.ts will not build because the type definition for global is missing.

Closing because https://github.com/pocketbase/js-sdk/issues/47#issuecomment-1273411424


Build IPFS subschema

Requirements, we need to know the ipfs gateway and cid.
Theoretically, cid is enough. However, in practice, cid cannot be resolved correctly without propoer ipfs gateway.

Finished. it's also on branch web2-ipfs. waiting for github endpoints.


Make this repo's relation to Boost clearer

It is not entirely clear from the README.md whether this repository is part of boost, an adaptation of a part of boost for stand-alone use, or something else. Please clarify... (not here - in README.md).

Is there a standalone version of this library?

@alandefreitas : I hope you're not asking me...

This is a boostorg subproject.


Add pytest to .travis.yml file

Right now the tests we are writing for the tests directory are not being run by Travis.

Fixed in b5feb42.


PHP 8.3 | Generic/UpperCaseConstantName: add support for typed constants

Description
This sniff is specifically targeted at constant names.
PHP 8.3 introduces typed constants. This means that the sniff now needs to jump over a potentially declared constant type to get at the constant name.
Fixed now.
Includes tests.
Suggested changelog entry

Generic.NamingConventions.UpperCaseConstantName : support for typed class constants

Related issues/external references
Related to #106
Fixes squizlabs/PHP_CodeSniffer#3927
Closes squizlabs/PHP_CodeSniffer#3936
Types of changes

[x] New feature (non-breaking change which adds functionality)

Have just tested this branch with the following code
class CompanyRegionsCommand extends Command
{
    private const int PAGE_SIZE = 40;
}

And I can confirm that the UpperCaseConstantNameSniff sniff no longer reports a false positive, thinking the "int" part is the constant name.
👍 Good work Juliette @jrfnl

Unless there are objections/someone leaves a comments on this PR, I will merge this tomorrow.

Rebased without changes. Merging once the build passes.


[README]: Allow media.githubusercontent.com Images in README.md

Related Problem
I have the following image in my README.md:

This uses the URL:

https://media.githubusercontent.com/media/RehanSaeed/Serilog.Enrichers.Span/main/Images/Banner.png

This shows like this on NuGet:

The Elevator Pitch
Please allow images from media.githubusercontent.com in README.md.
Additional Context and Details
No response

Workaround in the meantime<EMAIL_ADDRESS>

@augustoproiete,  we support list of github related domain below(https://docs.microsoft.com/en-us/nuget/nuget-org/package-readme-on-nuget-org#allowed-domains-for-images-and-badges):
camo.githubusercontent.com
github.com/.../workflows/.../badge.svg
raw.github.com
raw.githubusercontent.com
user-images.githubusercontent.com
The workaround is you could use domain above to render your images.
For the domain, media.githubusercontent.com, we have some security and privacy requirement if we want to add new domain to our allowlist, we will take time to evaluate this domain. We will keep up update once we have a result. Thanks for your patience.

@lyndaidaii Will leave it for @RehanSaeed to decide if he would like to pursue further. I merely suggested a workaround. ☺

I mean why not just auto accept all request as long these domains are already related to the ones we have.
for example we can confirm when you go to this domain it's part of github

I tried switching the image to use a direct github URL and that still didn't work.
https://github.com/RehanSaeed/Serilog.Enrichers.Span/blob/main/Images/Banner.png
Please add support for both.

In my project the image URL is https://raw.githubusercontent.com/Giorgi/DuckDB.NET/main/Logo.jpg but it is still not displayed on NuGet even though Allowed domains for images and badges contains raw.githubusercontent.com

@Giorgi  I was able to display the image URL you provided on NuGet.org. Please let me know if you have further question.


About getting the size in Bytes of the possible candidates

I'm having some issues to use one of those candidates of the Size Search Space when it comes to measure the size in bytes of a specific candidate.
I know to do it using the tensorflow lite kit, but I don't have any idea how to get the model to a torch.nn object and measure it.

Thanks for your interest in our NATS-Bench.
I have created an example for you, on how to measure the byte size of a candidate at here. Please let me know if you have other questions.

Thank you so much for your support. This example of yours, was exactly what I needed.


[Refactor] SCSS + contextMenu

Summary of changes

What did you change?

[x] refactor all CSS using SCSS
[x] IAction
[ ] IMenu
[ ] IContextMenu
[x] ContextMenuService

fix #163


Adds a warning when redhat yaml is enabled

As @AaronFriel discovered, Pulumi YAML and Red Hat YAML interfere with each other. Specifically Red Hat YAML prevents Pulumi YAML's completion from inserting correctly.
This PR adds a warning when both are enabled. The only solution I found was to disable Red Hat YAML. The warning has a dialog option to disable Red Hat YAML.
Looking at other packages, the closest analogy I found was for C++ (clangd & Microsoft C++). It provides a similar solution. I remember that rust presented a similar warning when rust-lsp and rust-analyzer conflicted.
Fixes #49

@iwahbe If we were to coordinate with the Red Hat YAML extension maintainers to have their extension disable or not trigger on Pulumi.yaml files, would that solve the issue without requiring users to disable an extension?

@iwahbe If we were to coordinate with the Red Hat YAML extension maintainers to have their extension disable or not trigger on Pulumi.yaml files, would that solve the issue without requiring users to disable an extension?

I'm not sure. I'm concerned that there is some global configuration that Red Hat YAML performs, since we see invalid behavior even when autocomplete is disabled for Red Hat YAML.


Implement Bucket-Elimination-based contractor

The core of the logic for BE contractor is already implemented by #64 and #89. This just wraps it up in a contractor interface.
Note that like many other contraction algorithms, this one is very sensitive to contraction order. For this reason, we let the caller decide it. There are some heuristics in the literature which we should implement. Once we have them one of the can be made default to simplify the API by not requiring the second argument.
Context: #50.

Squash and merge if you are ready.

Accidentally merged all commits to master. Sorry.
I disabled "Allow merge commits" in project settings to prevent this in future. You can now choose between squash or rebase (copying all commits is disabled).

That's ok, I did that before too. Thanks for flipping the disable switch!


allocate_sharded_buffer_on_device: RuntimeError: bad optional access

The following tt_lib code throws bad optional access:
        dram_memory_config = ttl.tensor.MemoryConfig(
            ttl.tensor.TensorMemoryLayout.HEIGHT_SHARDED,
            ttl.tensor.BufferType.DRAM,
            tensor.memory_config().shard_spec,
        )
        tensor = ttl.tensor.move(tensor, output_mem_config=dram_memory_config))

Trying to just move a sharded tensor from L1 to DRAM.
Culprit tt_eager/tensor/tensor_impl.cpp:
  DeviceBuffer allocate_sharded_buffer_on_device(uint32_t buffer_size_bytes, Device *device,
                                              const Shape& shape, DataType data_type, Layout layout,
                                              std::optional<ShardSpecBuffer> shard_params,
                                              const MemoryConfig& memory_config) {
      auto page_shape = shard_params.value().page_shape;

@tarafdarTT, this isn't blocking me!  I just ran into it trying some stuff

hey @nsmithtt thank you for posting the memory config. Could you also post the tensor shape and shard_spec.
With that information I'll be able to recreate the bug on my end.  Or if its easier you can point me to your branch and test that runs into this.

Any shard spec should do! Here's my repro tho:
tt::tt_metal::MemoryConfig(memory_layout=TensorMemoryLayout::HEIGHT_SHARDED,buffer_type=BufferType::L1,shard_spec=tt::tt_metal::ShardSpec(shard_grid={[(x=0,y=0) - (x=11,y=6)], [(x=0,y=7) - (x=3,y=7)]}, shard_shape={240, 32}, shard_orientation=ShardOrientation::ROW_MAJOR, halo=false))


Incompatible with react-router v4.4.0-beta.6

I was upgrading an older app and attempting to use connected-react-router, and encountered the following error being generated by react-router when attempting to wrap Links and Switches in this library's ConnectedRouter.
Error: Invariant failed: You should not use <Link> outside a <Router>

Repro example: https://codesandbox.io/s/ymk0787ox
I'm not familiar with how react-router previously allowed other Router implementations, but it seems that this future version no longer will. I'm also unsure whether this is an issue with connected-react-router or a regression/problem that should be fixed in react-router but I wanted to get your input. Thanks!

For additional context, I have to use that version of react-router because of issues with react-router Routes unable to properly handle React.lazy() components. The fix (https://github.com/ReactTraining/react-router/pull/6417) for that problem was merged but a new release hasn't been made yet.

Some additional info:

Using v4.3.1 works fine
I found a workaround by wrapping the ConnectedRouter in react-router's own BrowserRouter seems to have worked to silence the error, but of course, isn't ideal.

i am facing the same problem...

same problem +1
when i use jest test it happened

https://reacttraining.com/blog/react-router-v5/#why-the-major-version-bump


Add delegate take argument to root_register extrinsic and set_delegate_take extrinsic

Unit testing related to this change has been fixed, the remaining failing tests are fixed in main with the toggle POW registration update.


hardware

Besides NVIDIA DRIVE, what hardware you use to read and write the CAN bus? I would like to do such a setup: use a PC with Autoware, connect the PC to the car's OBD II port, then from the PC control the car via OBD II. (Would probably install an angle sensor on the steering wheel because OBD II does not output that.)
If someone has such a setup, could you tell me what hardware you use to connect the PC and the car's OBD II port? Thanks.

Hi,
We are using CANtoUSB Interface such as PCAN or Kvaser.
https://www.peak-system.com/PCAN-USB.199.0.html?L=1
https://www.kvaser.com/products-services/our-products/#/?descriptors=pc_int
But, Autoware can not control normal car with OBD2.
In general car, the CAN bus that can be connected by OBD 2 is limited by the CAN gateway.
If you connect Autoware to car by OBD2,  You can not do anything.
Also, most ECUs do not support control signal by outside even if you can access CAN in the car.


Adds support to print rendered charts on helm lint --debug

What this PR does / why we need it:
closes #8982 (hopefully)
This PR is to add support to render out the YAML from helm lint by using the --debug flag. It should support both valid and invalid YAML. This has similar behaviour to helm template --debug
If applicable:

[ ] this PR contains documentation
[x] this PR contains unit tests
[ ] this PR has been tested for backwards compatibility

Hey @bacongobbler, looks like a transient issue which seems unrelated as I'm not near that area of code. I've kicked off another ci build to run and this has passed if you could take another look? Thanks!


Improvement of News-letter Section of Footer

Is your feature request related to a problem? Please describe.
After succesfully submitting an email for our newsletter ,we can show an card/msg like
https://user-images.githubusercontent.com/56510414/112461090-9aab0c80-8d85-11eb-9ab1-6379c3a46b3f.mp4
Also, msg/card will be responsive on all screen-sizes!

Pls, assign me this issue
Have you read the Code of Conduct?
Yes

LGTM what do you say @Kajol-Kumari

LGTM what do you say @Kajol-Kumari

+1 @ShubhamSj07 please go ahead with this :)


Add Intel® QuickAssist Technology (Intel® QAT) support as contrib extensions

Title:
Add Intel® QuickAssist Technology (Intel® QAT) support as contrib extensions
Description:
Next generation Intel® QAT support with Intel® Xeon® Scalable processors will feature an Intel® QAT cryptography and compression acceleration engine. In order to use it, two new Envoy contrib extensions are proposed:

QATzip compression extension. This extension uses QATzip library (https://github.com/intel/QATzip) to implement accelerated HTTP compression. This can have a valid use case in scenarios such as service meshes, where the traffic within the mesh may be compressed without consuming CPU cycles.
QAT private key provider. This extension will use qatlib library (https://github.com/intel/qatlib) to accelerate RSA operations in handshakes. The extension will look a bit like the existing cryptomb private key provider. The use case is to move the expensive cryptographic operations away from the CPU to the accelerator device, leaving CPU cycles for other use.

Two new library dependencies would be added: QATzip library for compression and qatlib for accessing the hardware. Support for Intel® QAT is already present in the mainline Linux kernel and in Kubernetes device plugins (to expose the device files to containers). There are previous generations of Intel QAT® hardware devices, but they are not supported by these extensions.
Relevant links:
https://github.com/intel/intel-device-plugins-for-kubernetes/blob/main/cmd/qat_plugin/README.md
https://www.intel.com/content/www/us/en/architecture-and-technology/intel-quick-assist-technology-overview.html
https://www.intel.com/content/www/us/en/developer/topic-technology/open/quick-assist-technology/overview.html

@ipuustin QAT technology is highly effective in enhancing the performance of Envoy. Could you share a contrib extension of QATzip?

Hi, @sjtuzbk you can find out qatzip extension at https://github.com/intel/envoy/tree/release-1.19-intel/contrib/qat/compression/qatzip/compressor, you also can reach me on the envoy Slack for your usecase and question.

Hi, @sjtuzbk you can find out qatzip extension at https://github.com/intel/envoy/tree/release-1.19-intel/contrib/qat/compression/qatzip/compressor, you also can reach me on the envoy Slack for your usecase and question.

Thanks for your reply! I will try it.

Hi, @sjtuzbk May I get your email? It will be great we can have a talk about the usecase of qatzip. Or you can contact me, my email is<EMAIL_ADDRESS>glad to see we can get contact.


Summary table by variable with rows for waves

Change the summary tables so instead of having a separate table for each wave we have a separate table for each variable with
This may be super easy to do with groupby, ie  change make_summary_table so the group_by command also includes wave.
Then edit the rmarkdown report so it goes variable by variable reporting a table of stats and then the plots.

We could experiment with making the plots and the stats side by side but it may be too much of a faf.


chore: Fix warnings produced by shellcheck on bench.sh

Which issue does this PR close?

N/A
Rationale for this change

Many of the warnings produced by shellcheck are indications of bugs in the script that would break under certain circumstances.
What changes are included in this PR?

The following warnings was previously produced:
SC2006
SC2035
SC2045
SC2086
SC2140
SC2221 (SC2222)
Are these changes tested?
Manually running the script.

Are there any user-facing changes?
No.

I wonder if we want to add something here https://github.com/apache/datafusion/tree/main/dev (lint_scripts.sh) maybe? And maybe also a task in CI?

Agreed. If people agree that this is a change in the desired direction. Then it makes sense to address the same issues in other bash scripts in this repo and add a CI check as a follow up.

I wonder if we want to add something here https://github.com/apache/datafusion/tree/main/dev (lint_scripts.sh) maybe? And maybe also a task in CI?

Agreed. If people agree that this is a change in the desired direction. Then it makes sense to address the same issues in other bash scripts in this repo and add a CI check as a follow up.

This is a nice idea. Not sure about having another CI task though.