"Loading "shopify.js" tasks...ERROR" after updating to 1.0.1 from 1.0.0

After updating to the latest version, I receive this error when running a watch tasks with<EMAIL_ADDRESS>Loading "shopify.js" tasks...ERROR
Rolling back to 1.0.0 fixed this issue.
"devDependencies": {     "glob": "~3.2.3",     "growl": "^1.7.0",     "grunt": "^1.0.1",     "grunt-contrib-jshint": "^1.1.0",     "grunt-contrib-nodeunit": "^1.0.0",     "grunt-contrib-uglify": "^3.0.1",     "grunt-contrib-watch": "^1.0.0",     "grunt-shopify": "^1.0.0"   }

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Try 1.0.2. There was a syntax error that sneaked in.


Added transitionAction functionality

Implemented a prop to allow an optional action to be add when transitioning. Will add the class transition-<prop-value> to both children currently being transitioned.
Continuation of functionality discussed in #39

Thanks for this! I leave a comment. 😄 I think this is mergeable as soon as the comment is addressed.
Note to self:

Update document.
Built to lib.

Thanks!

Document updated: https://github.com/trungdq88/react-router-page-transition/blob/master/README.md


Add a Hello-World in any programming Language you like :computer:

Add your Hello-World in the language folder :file_folder: in the main branch.
if language folder doesn't exist you can make folder :file_folder: and add your program in it.
You can find new languages in this Programming Language List.

@dlx996 I would like to work on this


Fix il2cpp stripping issues

This PR does two things:

It injects a link.xml in order to tell unitylinker not to strip a couple of types
It refactors the API quite heavily in order to get rid of all usages of anonymous types

2 was done both in order to be able to make as narrow as possible entries for link.xml and because it makes the code-only api (without graphql source files) less awkward to use.
Fixes #15

Tested that both requests with variables and response deserialization now works on windows il2cpp and webgl


new project - next date finder created

new project - next date finder created

Hey @santhosh-pmk ,
similar kind of project exist here -> displayCalendar
try to update this file and add new features to this project

Hey @santhosh-pmk , similar kind of project exist here -> displayCalendar
try to update this file and add new features to this project

I cant see requested changes, you can close this pr and open new one after making the changes in that file


Design Review - style(App): Fixes having the unnecessary whitespace below the FooterCfGov

Relies on https://github.com/cfpb/design-system-react/pull/333 being merged into DSR first and carried over
closes https://github.com/cfpb/sbl-frontend/issues/365
Changes

style(App): Fixes having the unnecessary whitespace below the FooterCfGov

How to test this PR

Go to any page where FooterCfGov is used (basically all)
Use mobile view and swipe up at the scroll end OR zoom out (CMD + - multiple times)
See how the footer's grey part still extends to the bottom

Screenshots BEFORE the fix

Screenshot - Fix A (View zoomed out) - Maximizing the whitespace in main content

Screenshot - Fix B (View zoomed out) - Maximizing the footer

@shindigira
I prefer Fix B - extending the gray background - Maximizing the footer.


Support PHP 8.0

php8.0 has some change
https://www.php.net/manual/zh/migration80.incompatible.php

 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 accidentally deleted the removed other reviewer. I'm learning how to use the functions of GitHub and GIT.I'm sorry!


Add State Docs

Much Punk

This PR marks off another item from this issue and adds the README for documentation for the src/State bit of code.

Coverage remained the same at 100.0% when pulling 10ff4c9c267a10c6db36d8a3514e596d35bab88b on state-docs into c110fff19727b1fa65e72c5e17eda410d1086e40 on master.

Coverage remained the same at 100.0% when pulling 70ac927e06df2f6fdb373670e90a7c039556410d on state-docs into 5cc93fefbb1c239506c8808d756e0011c42ef32f on master.

Coverage remained the same at 100.0% when pulling d452d74ab0eb67968652ae47653cec7dc54d9cac on state-docs into 5cc93fefbb1c239506c8808d756e0011c42ef32f on master.


False positives for curl-auth rule if variables are quoted

Describe the bug
The new rule curl-auth-user is supposed to find leaks of basic auth credentials used with curl by determining if the curl command was called with the -u or --user flag, where the value contains a leaked secret (i.e. the credentials of an account).
However, the rule also matches if the flag is used in a script with variables. This is not a leak, as the environment variables are retrieved through other means and never committed to source code or any artifacts.
To Reproduce
Create a file test.sh (example AQL call to Artifactory):
curl -sSf -u ${USER}:${PASSWORD} \
    -H "content-type: text/plain" \
    -X POST 'https://xxx.com/artifactory/api/search/aql' \
    -d @query.aql \
    > output.json

Run gitleaks and inspect the finding.

...
Finding:     curl -sSf -u REDACTED
Secret:      REDACTED
RuleID:      curl-auth-user
Entropy:     4.169890
...

If the quotes around the value passed using -u are removed, the false positive disappears. This means the rule must be fixed to not simply match if quotes are given.
Expected behavior
Variables do not match the rule, even if they are quoted, as they are a valid way to pass the credentials without leaks.
One wants to quote variables to prevent word-splitting and globbing.
Screenshots
If applicable, add screenshots to help explain your problem.
Basic Info (please complete the following information):

OS: MacOs
Gitleaks Version: v8.21.1

Additional context
You can also verify the behavior with regex101:
https://regex101.com/r/LcccLw/1
cc @zricethezav

Thanks for the detailed report, @very-doge-wow. This seems to be an issue with one of the allowlist patterns, causing it to not match ${...}.
https://github.com/gitleaks/gitleaks/blob/d03d6c401b51633afc8e9d2b37cf3700927de595/config/gitleaks.toml#L286
This change in #1586 should fix that, once merged.


headsort added

add headsort with my code

Oke i can , later i will change
On Sun, Oct 11, 2020, 23:46 Larissa Lages<EMAIL_ADDRESS>wrote:

@larissalages requested changes on this pull request.
Can you rename the code for heap_sort, add inside the folder
data_structures/python and add the .python extension on the name of the
file?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/larissalages/code_problems/pull/130#pullrequestreview-506196871,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKL3NSYF3KP7BY7RYRL6CT3SKHONNANCNFSM4SIGZNTA
.

permission denied
Pada tanggal Sen, 12 Okt 2020 pukul 01.03 Yodi FM<EMAIL_ADDRESS>menulis:

Oke i can , later i will change
On Sun, Oct 11, 2020, 23:46 Larissa Lages<EMAIL_ADDRESS>wrote:

@larissalages requested changes on this pull request.
Can you rename the code for heap_sort, add inside the folder
data_structures/python and add the .python extension on the name of the
file?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/larissalages/code_problems/pull/130#pullrequestreview-506196871,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKL3NSYF3KP7BY7RYRL6CT3SKHONNANCNFSM4SIGZNTA
.


Using extensions in WinDbg Preview is not documented

It would be nice if somewhere on the WinDbg Preview page, the default extension search path was documented. Apparently it's %LOCALAPPDATA%\Dbg\EngineExtensions

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

ID: c1e093f9-7df0-17ab-71ae-8af9003ee041
Version Independent ID: 55ed6fd3-a7a6-f7d5-2a8e-fbf6cc6e2c7b
Content: Debugging Using WinDbg Preview - Windows drivers
Content Source: windows-driver-docs-pr/debugger/debugging-using-windbg-preview.md
Product: windows-hardware
Technology: windows-devices
GitHub Login: @DOMARS
Microsoft Alias: domars

@cbiesinger - As it turns out, the ability to auto load extensions is something that is being requested in this WinDbg issue - "Add a way to autoload extensions"
https://github.com/microsoftfeedback/WinDbg-Feedback/issues/32
That feature will need to be added to the product. When that is available, I will document it.
Thanks for using the debugger and providing input on this feature.
@aluhrs13 - FYI

@DOMARS I'm confused. I'm not requesting a new feature. I'm not asking for auto-loading extensions.
All I was asking for is documenting the existing feature that WinDbg will search for extensions in  %LOCALAPPDATA%\Dbg\EngineExtensions, so if you put a DLL there you can then do "!load foo" without specifying a full path.

@cbiesinger - That path may work, but my understanding is that not a supported feature at this point.

Oh, ok. Thanks for clarifying that.


pull request?

Link to related issue (if applicable)
Summary of proposed changes
Checklist

[ ] Use develop as the base branch
[ ] Exclude the gulp build (/dist changes) from the PR
[x] Test on supported browsers

thx

I have no idea what this is for. What it solves etc.


Logging and bug fix for rent position file clearing

Extends and fixed bugs in #103
Added logging in #105
Fixed the google client file query in #106
Summary:
Delete old RentPosition backup files to free up storage space going forwards.
The google client needs to query file createdDate explicitly, so the UseCase can use that to filter by it and fulfill these requirements:

Keep RentPosition Backup files created in the last 7 calendar days
Keep RentPosition Backup files created on the last working days of financial years
Delete other RentPosition Backup files

Key commit: https://github.com/LBHackney-IT/housing-finance-interim-api/pull/107/commits/cd8b99174a2e6459f25fc51d71024de6530d9f3d

Closed due to untested changes


Adjust TW polygon to include Matsu and Wuqiu islands [#127]

This modifies a small number of vertices in both the TW and CN polygons. The vertices should be co-incident between polygons (no gaps). I manually edited them down to 4-5 decimal places.

In summary, the partial geometry before was these two nodes:
[120.49232,25.22863],[118.56434,24.49266]
Which has been replaced by the sequence:
[120.5128,26.536],[120.0693,26.3959],[119.78816,26.2348],[119.98511,25.37624],[119.42295,25.0886],[118.6333,24.46259]

Thanks so much for the detailed pull request @bdon 🙌
Glad you are finding this project useful!


LV522 / Chances Claim

About the PR

Ports LV522, Also known as Chances Claim. Currently missing areas, but is in a completed state so will most likely be available with this pr.
Why / Balance

Map Parity also new map whooooo hehehe yeahhhh xipppeeee
Technical details

None
Media

Requirements

[ X ] I have read and am following the Pull Request and Changelog Guidelines.
[ X ] I have added media to this PR or it does not require an ingame showcase.

Breaking changes

None
Changelog

:cl: noctyrnal

add: Added Chances Claim, Also known as LV522, expect it be available soon!

test fail irrelevant to pr again


Enable retrieval of Gitlab labels

Gitlab issue labels are disabled for the moment, with this PR labels are retrieved from the repo.

reopening rebased soon


Model resolution

Here's an initial pass at writing down the resolution order for values in the graph, so that we go from a simplified graph to a full-qualified one (we should consider the inverse operation separately).

Values that are specified in the defaults section of the JSON document are propagated downwards through the document tree and set in a preorder traversal.
To resolve times and population sizes within demes, we start at the roots and visit demes in preorder (so, all ancestors will be fully qualified when we visit a particular deme). Within a deme, the times of each epoch are determined uniquely by the information supplied and the time information of parent demes. Population sizes are uniquely determined by the information within a deme.
Migrations are then resolved.

How does this sound?

If a deme has only one epoch, it's permissible to specify the start/end time and initial/final size directly on the deme. So epochs might not exist until the demes are resolved. This means that the defaults will need to be pushed down to the demes level, and then as/after the deme's epochs are constructed, the deme default can be pushed into the epoch level. Not sure if this detail matters for what you're writing though.

If a deme has only one epoch, it's permissible to specify the start/end time and initial/final size directly on the deme.

Is there a previous discussion on times as properties of demes vs always requiring the existence of at least one epoch?

Possibly not since we first started discussing the yaml format in the old msprime issue.

I'll open an issue - it's not totally obvious it's worth the complexity.

Oh, #133. Feel free to reopen there.

Closing this as the semantics have been decided.


refactor: Async recursive handler

This allows following the regular pattern of canHandle/handle with handlers that are recursive.
It fixes the Waterfall. I think I can simplify the Sequence one as well if this is ok.

@matthieubosquet What problem are we solving here—do you have an example of what is broken with the waterfall and what needs fixing?
In general, I would suggest to always create an issue first to describe the problem, and then have a PR that is a solution.

@matthieubosquet What problem are we solving here—do you have an example of what is broken with the waterfall and what needs fixing?
In general, I would suggest to always create an issue first to describe the problem, and then have a PR that is a solution.

In the WaterfallHandler, the canHandle and handle function aren't really usable as is.
Because the handle function does perform the canHandle check and the canHandle function can't return the handler that can Handle the input.
Therefore they're just duplicating/misleading code here to conform to the interface, which seems wrong.
I like the handleSafe => canHandle + handle pattern.
I don't think we should have to deviate from it here.

In the WaterfallHandler, the canHandle and handle function aren't really usable as is.
Because the handle function does perform the canHandle check and the canHandle function can't return the handler that can Handle the input.
Therefore they're just duplicating/misleading code here to conform to the interface, which seems wrong.
I like the handleSafe => canHandle + handle pattern.
I don't think we should have to deviate from it here.

In the WaterfallHandler, the canHandle and handle functions aren't really usable as is.

They are though. They work and conform to the contract.

Therefore they're just duplicating/misleading code here to conform to the interface, which seems wrong.

So is the issue that there is a performance overhead?
That's why we have handleSafe.

I like the handleSafe => canHandle + handle pattern.

Me too 🙂 We're not breaking it.

I don't think we should have to deviate from it here.

We're not deviating.

canHandle: should you be the one handling it?
handle: well, do it then!
handleSafe: the above 2 combined in one call

This PR would make all handlers deviate for one specific performance optimization, for which a solution already exists.

In the WaterfallHandler, the canHandle and handle functions aren't really usable as is.

They are though. They work and conform to the contract.

Therefore they're just duplicating/misleading code here to conform to the interface, which seems wrong.

So is the issue that there is a performance overhead?
That's why we have handleSafe.

I like the handleSafe => canHandle + handle pattern.

Me too 🙂 We're not breaking it.

I don't think we should have to deviate from it here.

We're not deviating.

canHandle: should you be the one handling it?
handle: well, do it then!
handleSafe: the above 2 combined in one call

This PR would make all handlers deviate for one specific performance optimization, for which a solution already exists.

I think you're right Ruben.
Thanks for the explanation! :)

I think you're right Ruben.
Thanks for the explanation! :)


Skip stats folder on update

In ISPConfig there is always a stats folder. Because this folder does not belong to Shopware, Shopware is blocking Updates everytime, so you have to change this line manually in the Core file.
It would be good to merge this pull request to skip this folder in future updates.

Thanks @kayyyy
We decided to close this PR because of time constraints and limited overall benefit to the product. If this change is still important to you, please create a new issue on https://issues.shopware.com so people can up-vote this feature.


Fixed detecting invalid root names in scene creation dialog, issue #66158

I made solution to issue #66158.
I removed _is_valid_identifier_bit function and changed its occurrences to is_ascii_identifier_char.

The correct solution is to replace the function used in scene_create_dialog.cpp, not changing how function works.

@DorianSzlachcic are you still work on this? If not, I'll take this issue and make a PR for this.

You can take it. I couldn't find better solution to this


plugins/gimp: Support for decoding animations

(edited by @mo271)

Test file:

Russian Propaganda.jxlzip -Z store Russian\ Propaganda.jxl.zip Russian\ Propaganda.jxl

Russian Propaganda.jxl.zip

Follows up to work done by @xiota and others.

Thanks a lot for the contribution, @ctrlcctrlv!
I tested plugin with an animation from our conformace repo animation_icos4d/input.jxl
Seems to work like a charm.
In order to comply with github-acceptable-use-policies,
I’ll edit your comments to replace the screenshot and link by a screenshot of and link to the icosahedron image.
Looking forward to a pull request for encoding animation, like you propose in #1864, if you come around doing that.

I fixed the failing authors check and linting https://github.com/libjxl/libjxl/actions/runs/3392132321/jobs/5643700386, taking the name from the commit.

I apologize for the offensive image originally used. It was an art project, and I wasn't aware there was an existing animation I could use as a test.

Besides handling review comments, 21adf35 handles blend modes equivalently to how it is done in the GIF loading plugin. Therefore, it is possible to export directly as GIF now.

Thanks for being so careful @alistair7. It was working for me with my test files because they all had the same denominator/numerator. My original commit (f150585) didn't quite fix it, it only fixed it for your files and not mine, so I based b81ff91 on tools/jxlinfo.c, as that program understands both.

That's Wikipedia.jxl:
Wikipedia.jxl.7z.001.zip
Wikipedia.jxl.7z.002.zip

No problem. Nice work!

78d0a94 omits frames of zero duration, which shouldn't cause issues, but did indeed cause flickering in GIMP's animation playback function.
There are no more blank frames in Wikipedia.jxl.

78d0a94 omits frames of zero duration, which shouldn't cause issues, but did indeed cause flickering in GIMP's animation playback function.

Should it really do that? Those frames could conceivably play a part in rendering due to blending.

@sboukortt Yes it should. If the display time is 0, then that means no display. How could it not?

I think it's a cjxl bug that those frames even get added, by the way. I can remove my workaround, but unless the spec itself clarifies this issue I think my reading is logical, and will result in a less buggy plugin for users as cjxl is the most common encoder.

@sboukortt Yes it should. If the display time is 0, then that means no display. How could it not?

What @sboukortt presumably means by "Those frames could conceivably play a part in rendering due to blending" is that you could have a frame of duration 0, that is a new background and then the next frame is some image that has alpha on top of that which comes with a non-zero duration. You never want to see a frame that is just the new background, but put something on it immediately. For this or in slightly more involved blending situations it is useful to allow frames of duration 0, no?

@mo271 I know what they mean, but cjxl doesn't do this. It (seemingly randomly) adds transparent layers of duration 0. I think that this should be accepted, if it matters to someone they should investigate why cjxl does this and get it to stop, then the two commits 78d0a94 and 2193f94 can be reverted.

78d0a94 omits frames of zero duration, which shouldn't cause issues, but did indeed cause flickering in GIMP's animation playback function.

Should it really do that? Those frames could conceivably play a part in rendering due to blending.

Maybe c28e3588a95d8a4f1282e613d26dd8b7ebc70248 will make you happier. It's more hacky, and looks terrible, lol, but on the off chance someone creates an image without cjxl that requires this strange combining edge case, I am now doing the combine in GIMP via gimp_image_merge_down(image,layer) instead of just dismissing the layer.

I noticed that there was JxlDecoderSetCoalescing, and I think when you set this to JXL_TRUE or not call it at all, (since then the default value is true), then the problem with the 0-duration frames will go away.
In fact I checked just that in this branch:
https://github.com/libjxl/libjxl/compare/main...mo271:libjxl:coalescing_gimp
with the wikipedia image, and I get 248 frames just as expected.
So I suggest to do it that way. What do you think?

https://libjxl.readthedocs.io/en/latest/api_decoder.html#_CPPv423JxlDecoderSetCoalescingP10JxlDecoder8JXL_BOOL

Sorry @mo271 but I feel like I need the coalescing. It makes the output much more useful to actually edit, especially for my original example, Russian Propaganda.jxl.

Sorry @mo271 but I feel like I need the coalescing. It makes the output much more useful to actually edit, especially for my original example, Russian Propaganda.jxl.

When you say "I need the coalescing" do you mean "I need set coalescing to be true" or "I need set coalescing to be false"?
I checked and it seems that the two frames in that image work exactly as intended with the coalescing set to be true, which is what is done in https://github.com/libjxl/libjxl/compare/main...mo271:libjxl:coalescing_gimp.
In what way does it make the output more useful to actually edit? (I'm not sure I'm understanding this correctly...)

Sounds like they're saying that they want the separate layers to remain separate so they can be treated as layers in GIMP.

Sounds like they're saying that they want the separate layers to remain separate so they can be treated as layers in GIMP.

Even with coalescing set to true, each frame in the animation will be separate layers in GIMP. Not sure what is going on with the empty frames of duration zero when we turn off coalescing, perhaps GIMP can't handle properly frames of different dimensions.
Will open a bug for further understand of what is going on.

Even with coalescing set to true, each frame in the animation will be separate layers in GIMP.

Yes, but with the entire background. Not as easy to edit at all.

Another complication with having coalescing disabled is that a frame's blend_source doesn't necessarily refer to the previous frame. That's probably not a concept that Gimp's combine/replace tags can deal with, so the exported results won't look right in those cases.  I'm not sure whether cjxl will ever produce a file like that from a converted GIF/APNG, but they certainly exist.  Silly example attached: face_skip_frame.jxl.zip
I don't know the best approach to dealing with this (if at all).  I guess at worst, you could consider throwing an error if we find a frame where blend_info.source != previous_save_as_reference, where previous_save_as_reference is stored from the previous frame's layer_info.save_as_reference ...in a similar way to how it currently rejects the more exotic blend modes.
Or would it make any sense for the plugin to try decoding without coalescing, but on finding any non-trivial blending, reset the decoder and try again with coalescing enabled?  Maybe that's overcomplicating it...

I think this points to a gap in our current API, since there are currently only two options:

Coalescing (default): gives only the blended frames, so you lose the crop region and transparency (i.e. only returns full-canvas sized frames with nonzero duration)
No coalescing: gives all frames as they are, without blending, including zero-duration frames (i.e. layers) that are kRegularFrames (the kReferenceOnly and kLfFrames ones are never returned because they are intended strictly to be used only as coding tools, not as semantically meaningful objects by themselves).

What would be useful here is an option to merge the zero-duration frames but not to blend the nonzero-duration frames, i.e. return only nonzero-duration frames but still have them as they are before blending and making them canvas-sized.
The question is if this can even be done in general, since jxl's frame blending model is not simply a linear stack where every next frame is "on top" of the one before, but frame blending can take other "source frames" than the usual one that is the current canvas state. This model is strictly richer than what can be expressed in GIF/APNG and in Gimp layers, so in the general case there is no way to map a jxl frame sequence to that.
For the specific case of transcoded GIF/APNG/AWebP though, there should be a way to map the jxl frame sequence to a suitable Gimp layer stack. I suspect the dummy empty frames cjxl generates are just a way to circumvent the lack of dispose modes in jxl, or something like that.

Not related to this, but another coalescing mode that would be good to have for animation display, is one where the returned frames are blended but only the crop box containing modified pixels gets returned (so it only returns kReplace frames like the default coalescing, but not necessarily canvas-sized ones). This has obvious advantages in terms of buffer sizes and would allow e.g. browsers to have a higher likelihood of being able to keep the entire animation in memory.
So I think we basically need one boolean setting to indicate whether zero-duration frames should be blended or not, and another boolean setting to indicate whether cropped frames should be returned or canvas-sized ones. We currently only have an option where it is (true,false)  (the default coalescing==true) and another where it is (false,true)  (this is what coalescing==false does).
And then we need to find a way for dealing with exotic blend source choices; probably this is something most applications will not want to deal with so it's probably best if by default anything that is not a simple "stack of layers" gets converted in something that is (we can always do the blending and turn anything into a kReplace frame that overwrites the whole canvas), and only when some new option is set, you can get the original thing which may be quite exotic.
Also it would be good to have a way to tell the decoder not to return 'exotic' blend modes (i.e. not kReplace and not kBlend), since in many cases (like Gimp) the application will already know about replace and blend but not about the other blend modes.

So how to best proceed here?
With the current API, I see three options

set coalescing to true
set coalescing to false and not merge 0 duration frames
set coalescing to false and merge 0 duration frame

The problem for 2. and 3. is that there will be animated jxl files that blend source will not be the previous frame, which gimp cannot seemt to handle, like @alistair7 pointed out.
Might it be possible to make the user select an option during the opening of a file, if there are frames of duration 0?
I think right now the cleanest approach would be 1., because it seems to work in all cases, however I can see that it would be nicer if the structure of the layers would be preserved.
Really great that you implemented the decoding (and encoding!) of animated JXLs in the gimp plugin, @ctrlcctrlv, showing that the API with respect to coalescing can possibly be improved. The source of the problem comes from the fact that jxl is more with frames and layers than gimp...
Would the problem with solution 2. other than the problem with further-back-reference, be that flickering in GIMP's animation playback function? Perhaps one could get that resolved in GIMP somehow.

Zero-duration frames in Gimp will not only be an issue for its own playback, but it will be even worse if you then save it as GIF/APNG/WebP where typical players impose a minimum duration per frame because of legacy content that relies on that.

I think wrong assumptions about GIMP's blending modes are being made. GIMP has many blending modes. I just didn't implement this because the plugin as it existed before my patches was already so incomplete I viewed my patchset(s) as incremental improvements, but it seems that I'm being held to a higher standard than the original patches. In any event, GIMP has plenty of support.

But, the API issue remains, because GIMP is not the only editor out there. And, as @jonsneyers correctly notes, in other formats there's a minimum delay, so the Coalescing API needs fixed anyway.

I agree; I think having the ability to decode at least some (not too exotic) animations is clearly an improvement over the current state of the gimp plugin. Do you prefer to get the version in https://github.com/libjxl/libjxl/commit/c28e3588a95d8a4f1282e613d26dd8b7ebc70248 (with the hack to remove 0 duration frames in gimp, while setting coalescing to false) or the versio in
https://github.com/mo271/libjxl/tree/coalescing_gimp (setting coalescing to true) merged?
I have a slight preference for the 2nd, since it will likely work for more files (having the drawback of not getting the layers correct for some of them).
@ctrlcctrlv

Coalescing frames has the disadvantage that going gif -> jxl -> gif will potentially produce a way larger gif, when the original had many frames that update only a small area. Then again I think Gimp does have an "optimize for gif" thing that can trim the frames again.
So if we want to get something that works in all cases first and make it better later, then coalescing=true is the way to go for now, I think. But we should expand the api to get a way to avoid coalescing while not returning exotic blend sources/modes — i.e. have a way to select which blend modes you want to keep in output and which ones you want libjxl to convert to kReplace, and also have a way to get only "blend source for current frame is current canvas state". This would be useful in browsers/viewers (to save memory and repaint by avoiding all frames to be full canvas sized), where you would want to get only kReplace, and also for Gimp, where you want to get both kReplace and kBlend.
For animations, merging zero-duration frames makes sense, but for layered images, keeping them as seperate layers makes more sense. So I think this is an orthogonal thing that should be configurable. For this plugin, it would make sense to merge zero-duration frames iff it is an animation, and to keep them as separate layers if it is a layered still image. The case of animations with layered frames is not something Gimp can currently handle and it is not something that will exist in the wild since there are no existing formats that can do that, or authoring tools that produce them, so merging the layers within each frame is OK in this case.

I'm OK with coalescing=true for now. Users of the GIMP format already are well aware of its many shortcomings and know that they may have to use e.g. IM with -layers Optimize after a convert from an exotic format. GIMP's plugin for that may even provide such a function.

Many thanks again, @ctrlcctrlv!

My pleasure :o)


Ability to disable the focus trap

Summary:
It would be great if it was possible to disable the focus trap. This would be useful if ever needing to render the modal inline in a page.
I am building an app which lets one build a modal, and it would be useful to turn off the focus trap while in design mode.
To workaround this for now, I just layered a transparent div over the modal to make it non-interactive.

@chaddjohnson I think setting shouldFocusAfterRender={false} will disable the focus trap. If you want it to still gain focus initially after opening, something like onAfterOpen={() => this.contentRef.focus()} might work.

@JKillian Thank you. I wonder if there also is a way to disable the focus trap to enable interaction with the modal without trapping focus.

@chaddjohnson I believe that shouldFocusAfterRender={false} does disable the focus trap. But not 100% sure, just what glancing at the code looked like to me!

Having the same issue here! Would be really useful if we could! In order to make it flexible for other dialogs types!
I tried shouldFocusAfterRender={false} but doesn't stop the trapping to work. @JKillian

An overlay on top prevents focus from ever entering the dialogue via click events. Keyboard tabbing into the modal may still cause focus to be trapped...I haven’t tested that.

Unfortunately setting shouldFocusAfterRender={false} does not disable the focus trap.

I've created a PR to address this issue: https://github.com/reactjs/react-modal/pull/876

We have a guide modal in our app. It can be viewed while using the app, but if it receives focus it needs to be closed before the user can transfer focus back to the rest of the app using the tab button. This is a major accessibility concern for us. All the other functionality of react-modal suits the use case very well.

Please see discussion #881. It'd be nice to have some feedback on this.


New release?

Can a new release get tagged and published to Packagist?  I would like to use invokables, but can't until #9 is released.
Thanks!

Ping @Crell, can you take care of this?

@Jean85 / @Crell Would a 1.0.1 do or should we tag 1.1.0?

Since there's a new feature I would say 1.1

@Jean85 oki will tag 1.1 momentarily

Just tagged 1.1.0.


add SNOMED CT codes to conditions covered

SNOMED CT is used by other EHR systems
Actually, codes are included.

only other conditions do not support Snomed CT codes


fully release dax onboarding and dialogs

Task/Issue URL: https://app.asana.com/0/392891325557410/1162375367527169
Tech Design URL:
CC:
Description:

Removes old onboarding, tips and experiment.
Removes EasyTips library from the project.
Fixes text jumping in dax dialog
Improves clarity around new install logic and removes some redundant code
Remove some redundant code/storyboard stuff for onboarding

Steps to test this PR:

Test migrating from before any Dax Onboarding.  No dax dialogs or onboarding should be displayed after upgrading.
Clean install, ensure that dax onboarding is shown and dax dialogs still behave as before (but with the text jumping fix)
Check logo positioning works across devices

Orientation Testing:

[x] Portrait
[x] Landscape

Device Testing:

[x] iPhone SE (1st Gen)
[x] iPhone 8
[x] iPhone X
[x] iPad

OS Testing:

[x] iOS 10
[x] iOS 11
[x] iOS 12
[x] iOS 13

Theme Testing:

[x] Light theme
[x] Dark theme

Internal references:
Software Engineering Expectations
Technical Design Template

Thanks @bwaresiak !


"No such file or directory" message after executing the command

I downloaded the HCL file from the cloud and extracted the .zip using the command unzip -o dasharo_hcl_reports.zip &&. When attempting the next steps, I used the command find . -name "platform_name_prefix*.tar.gz" -print0 | xargs -0 -n1 bash -c './dts-hclmgr cpu "$0"', in this case for "PC_Engines_apu2". The command located the mentioned files; however, it ended with the message 'No such file or directory.' As a result, I couldn’t complete the final step, i.e., passing the information to the DTS HCL manager.
[sbieniek@3M11 Downloads]$ find . -name "PC_Engines_apu2*.tar.gz" -print0 | xargs -0 -n1 bash -c './dts-hclmgr cpu "$0"'

./dasharo_hcl_reports/external/PC_Engines_apu2_Dasharo_(coreboot+UEFI)_v0.9.0_a3244343-69c7-59cf-924f-f3928bc2ccf6_2024_05_31_07_14_58_811048826.tar.gz: line 1: ./dts-hclmgr: No such file or directory
./dasharo_hcl_reports/external/PC_Engines_apu2_v<IP_ADDRESS>_bd5f035a-203a-562f-9c4a-07ca4a09383e_2024_07_26_04_04_53_241097366.tar.gz: line 1: ./dts-hclmgr: No such file or directory
./dasharo_hcl_reports/external/PC_Engines_apu2_v<IP_ADDRESS>_4b385548-3490-53b2-b75e-daa6305c994c_2024_07_05_13_59_46_089631932.tar.gz: line 1: ./dts-hclmgr: No such file or directory
./dasharo_hcl_reports/external/PC_Engines_apu2_v<IP_ADDRESS>_4b385548-3490-53b2-b75e-daa6305c994c_2024_07_05_14_07_13_601876389.tar.gz: line 1: ./dts-hclmgr: No such file or directory
./dasharo_hcl_reports/external/PC_Engines_apu2_v<IP_ADDRESS>_4b385548-3490-53b2-b75e-daa6305c994c_2024_07_05_14_13_05_466943277.tar.gz: line 1: ./dts-hclmgr: No such file or directory
./dasharo_hcl_reports/external/PC_Engines_apu2_v<IP_ADDRESS>_4b385548-3490-53b2-b75e-daa6305c994c_2024_07_05_14_24_07_890380206.tar.gz: line 1: ./dts-hclmgr: No such file or directory
./dasharo_hcl_reports/external/PC_Engines_apu2_v<IP_ADDRESS>_58150020-f709-5f8c-9a8d-eda03aec4edb_2024_04_04_19_13_09_682271888.tar.gz: line 1: ./dts-hclmgr: No such file or directory
./dasharo_hcl_reports/external/PC_Engines_apu2_v<IP_ADDRESS>_63a69ed7-3a38-5790-87e6-923f1cd037ef_2023_07_13_13_33_48_972377879.tar.gz: line 1: ./dts-hclmgr: No such file or directory
./dasharo_hcl_reports/external/PC_Engines_apu2_v<IP_ADDRESS>_d65f4a16-6d08-5d42-adcb-a94ee8a16d97_2024_08_17_15_28_27_137180151.tar.gz: line 1: ./dts-hclmgr: No such file or directory
./dasharo_hcl_reports/external/PC_Engines_apu2_v<IP_ADDRESS>_e5c5f72f-8b9a-5136-8c2b-3c0bae980c07_2024_06_25_22_48_07_418482607.tar.gz: line 1: ./dts-hclmgr: No such file or directory
./dasharo_hcl_reports/internal/OEM-3mdeb-log/PC_Engines_apu2_88a4f96_d948c829-ec79-5e90-a1f2-799ddacb68cc_2024_05_01_00_04_32_216130321.tar.gz: line 1: ./dts-hclmgr: No such file or directory
./dasharo_hcl_reports/internal/OEM-3mdeb-log/PC_Engines_apu2_Dasharo_(coreboot+UEFI)_v0.9.0_04145fd2-4497-549d-abd8-ab26c728a027_2024_07_07_13_24_52_401160786.tar.gz: line 1: ./dts-hclmgr: No such file or directory
./dasharo_hcl_reports/internal/OEM-3mdeb-log/PC_Engines_apu2_Dasharo_(coreboot+UEFI)_v0.9.0_d948c829-ec79-5e90-a1f2-799ddacb68cc_2024_05_01_00_02_53_224407433.tar.gz: line 1: ./dts-hclmgr: No such file or directory
./dasharo_hcl_reports/internal/OEM-3mdeb-log/PC_Engines_apu2_Dasharo_(coreboot+UEFI)_v0.9.0_e16b5ce9-ab50-5c50-ae40-0135abedc818_2024_07_08_23_16_05_766716464.tar.gz: line 1: ./dts-hclmgr: No such file or directory
./dasharo_hcl_reports/internal/OEM-3mdeb-log/PC_Engines_apu2_v<IP_ADDRESS>_e5c5f72f-8b9a-5136-8c2b-3c0bae980c07_2024_06_27_21_48_17_849061150.tar.gz: line 1: ./dts-hclmgr: No such file or directory
./dasharo_hcl_reports/internal/OEM-3mdeb-log/PC_Engines_apu2_v<IP_ADDRESS>_5f97bdcb-dad0-5f04-8fe7-968f3052ca14_2024_05_08_02_20_04_175007959.tar.gz: line 1: ./dts-hclmgr: No such file or directory
./dasharo_hcl_reports/internal/OEM-3mdeb-log/PC_Engines_apu2_v<IP_ADDRESS>_2724a742-3253-56ee-8f16-95c717b85918_2024_10_25_10_20_08_977402073.tar.gz: line 1: ./dts-hclmgr: No such file or directory
./dasharo_hcl_reports/internal/OEM-3mdeb-log/PC_Engines_apu2_v<IP_ADDRESS>_1ef22a07-0c89-5ac5-be4b-58f68862a62f_2024_10_22_12_27_48_766102992.tar.gz: line 1: ./dts-hclmgr: No such file or directory
./dasharo_hcl_reports/internal/OEM-3mdeb-log/PC_Engines_apu2_v<IP_ADDRESS>_04145fd2-4497-549d-abd8-ab26c728a027_2024_07_07_13_04_18_654034997.tar.gz: line 1: ./dts-hclmgr: No such file or directory
./dasharo_hcl_reports/internal/OEM-3mdeb-log/PC_Engines_apu2_v<IP_ADDRESS>_8b21762c-3f43-54de-888c-962b75e0f808_2024_03_29_07_27_42_075843188.tar.gz: line 1: ./dts-hclmgr: No such file or directory
./dasharo_hcl_reports/internal/OEM-3mdeb-log/PC_Engines_apu2_v<IP_ADDRESS>_8b21762c-3f43-54de-888c-962b75e0f808_2024_03_29_07_53_30_847004629.tar.gz: line 1: ./dts-hclmgr: No such file or directory
./dasharo_hcl_reports/internal/OEM-3mdeb-log/PC_Engines_apu2_v<IP_ADDRESS>_8b21762c-3f43-54de-888c-962b75e0f808_2024_03_29_08_42_10_432463540.tar.gz: line 1: ./dts-hclmgr: No such file or directory
./dasharo_hcl_reports/internal/OEM-3mdeb-log/PC_Engines_apu2_v<IP_ADDRESS>_8b21762c-3f43-54de-888c-962b75e0f808_2024_04_02_07_34_36_387177669.tar.gz: line 1: ./dts-hclmgr: No such file or directory
./dasharo_hcl_reports/internal/OEM-3mdeb-log/PC_Engines_apu2_v<IP_ADDRESS>_8b21762c-3f43-54de-888c-962b75e0f808_2024_04_03_09_02_17_024690299.tar.gz: line 1: ./dts-hclmgr: No such file or directory
./dasharo_hcl_reports/internal/OEM-3mdeb-log/PC_Engines_apu2_v<IP_ADDRESS>_e16b5ce9-ab50-5c50-ae40-0135abedc818_2024_07_08_23_08_34_602041007.tar.gz: line 1: ./dts-hclmgr: No such file or directory
./dasharo_hcl_reports/internal/OEM-3mdeb-log/PC_Engines_apu2_v<IP_ADDRESS>_e40cfa7e-6217-5559-b3b7-e11bed68db8a_2024_06_29_16_49_34_127916770.tar.gz: line 1: ./dts-hclmgr: No such file or directory
./dasharo_hcl_reports/internal/OEM-3mdeb-log/PC_Engines_apu2_v<IP_ADDRESS>_e40cfa7e-6217-5559-b3b7-e11bed68db8a_2024_07_27_17_18_01_562080969.tar.gz: line 1: ./dts-hclmgr: No such file or directory
./dasharo_hcl_reports/internal/OEM-3mdeb-log/PC_Engines_apu2_v<IP_ADDRESS>_e5c5f72f-8b9a-5136-8c2b-3c0bae980c07_2024_04_03_13_13_55_293092679.tar.gz: line 1: ./dts-hclmgr: No such file or directory
./dasharo_hcl_reports/internal/OEM-3mdeb-log/PC_Engines_apu2_v<IP_ADDRESS>_e5c5f72f-8b9a-5136-8c2b-3c0bae980c07_2024_04_15_11_53_08_415736362.tar.gz: line 1: ./dts-hclmgr: No such file or directory
./dasharo_hcl_reports/internal/OEM-3mdeb-log/PC_Engines_apu2_v<IP_ADDRESS>_e5c5f72f-8b9a-5136-8c2b-3c0bae980c07_2024_06_27_16_57_10_767586112.tar.gz: line 1: ./dts-hclmgr: No such file or directory
./dasharo_hcl_reports/internal/OEM-3mdeb-log/PC_Engines_apu2_v<IP_ADDRESS>_e5c5f72f-8b9a-5136-8c2b-3c0bae980c07_2024_06_27_20_29_25_683106189.tar.gz: line 1: ./dts-hclmgr: No such file or directory
./dasharo_hcl_reports/internal/OEM-3mdeb-log/PC_Engines_apu2_v<IP_ADDRESS>_e5c5f72f-8b9a-5136-8c2b-3c0bae980c07_2024_06_27_21_26_48_725269852.tar.gz: line 1: ./dts-hclmgr: No such file or directory
./dasharo_hcl_reports/internal/OEM-3mdeb-log/PC_Engines_apu2_v<IP_ADDRESS>_e5c5f72f-8b9a-5136-8c2b-3c0bae980c07_2024_08_20_10_24_47_964079386.tar.gz: line 1: ./dts-hclmgr: No such file or directory

@Stanislaw-bnk, you must be in the directory where dts-hclmgr is. Now you are in Downloads, it will not work.

I opened the terminal in the folder with the downloaded dts-hw-conf-gen repository, where the dts-hclmgr file is located. This time, however, I'm receiving the warning Directory bash already exists.
[sbieniek@3M11 dts-hw-conf-gen]$ find . -name "Micro-Star_International_Co.,_Ltd._MS-7D25*.tar.gz" -print0 | xargs -0 -n1 bash -c './dts-hclmgr cpu "$0"'
Warning: Directory bash already exists.

Please run' find. -name "Micro-Star_International_Co.,_Ltd._MS-7D25*.tar.gz" -print0` in that directory and see if it returns anything.
Please consider this:

unizip does extract archives with reports
find look for specific names in all reports that should be in the current directory; otherwise, nothing is found, and nothing will be processed
only then it makes sense to pass to the further parts of commands, which are separated by |

Please spend some time with ChatGPT. It will help you with the basics, and then we can improve documentation to make it usable for everyone.

I've run the find . -name "Micro-Star_International_Co.,_Ltd._MS-7D25*.tar.gz" -print0 command in the dasharo_hcl_reports folder, and it managed to found the records:
[sbieniek@3M11 dasharo_hcl_reports]$  find . -name "Micro-Star_International_Co.,_Ltd._MS-7D25*.tar.gz" -print0
./external/Micro-Star_International_Co.,_Ltd._MS-7D25_1.0.0_4c878a10-59f4-512b-a474-9505214e955b_2024_10_17_14_12_46_409632289.tar.gz./external/Micro-Star_International_Co.,_Ltd._MS-7D25_1.0.0_4c878a10-59f4-512b-a474-9505214e955b_2024_10_17_14_26_28_877455877.tar.gz./external/Micro-Star_International_Co.,_Ltd._MS-7D25_1.0.0_4c878a10-59f4-512b-a474-9505214e955b_2024_10_17_14_30_23_563072402.tar.gz./external/Micro-Star_International_Co.,_Ltd._MS-7D25_1.0.0_4c878a10-59f4-512b-
....
....
....

I've then run xargs -0 -n1 bash -c './dts-hclmgr cpu "$0"' but it seems that nothing is happening. Should it automatically update the list? I've also tried xargs -0 -n1 bash -c './dts-hw-conf-gen cpu "$0"' as this is the name of the repo. How should I procees from here?

@Stanislaw-bnk I have no idea why you are approaching the problem that way when I said it is the wrong approach. It is very important that those commands are connected with |; those commands can work only in chains.
If find . -name "Micro-Star_International_Co.,_Ltd._MS-7D25*.tar.gz" -print0 provide results so you should be able to run:
find . -name "Micro-Star_International_Co.,_Ltd._MS-7D25*.tar.gz" -print0 | xargs -0 -n1 bash -c './dts-hclmgr cpu "$0"'

I have to provide a wrapper for that.

I copied the dts-hclmgr file into the dasharo_hcl_reports folder, which is where I run the terminal commands. I managed to get the following result:
[sbieniek@3M11 dasharo_hcl_reports]$ find . -name "Micro-Star_International_Co.,_Ltd._MS-7D25*.tar.gz" -print0 | xargs -0 -n1 bash -c './dts-hclmgr cpu "$0"'

gzip: stdin: unexpected end of file
tar: Child returned status 1
tar: Error is not recoverable: exiting now
| 12th Gen Intel(R) Core(TM) i5-12600K | v1.0.0 | Dasharo HCL Report |
| 12th Gen Intel(R) Core(TM) i5-12600K | v1.0.0 | Dasharo HCL Report |
| 12th Gen Intel(R) Core(TM) i5-12600K | v1.0.0 | Dasharo HCL Report |
| 12th Gen Intel(R) Core(TM) i5-12600K | v1.0.0 | Dasharo HCL Report |
| 12th Gen Intel(R) Core(TM) i5-12600K | v1.0.0 | Dasharo HCL Report |
| 12th Gen Intel(R) Core(TM) i5-12600K | v1.0.0 | Dasharo HCL Report |
| 12th Gen Intel(R) Core(TM) i7-12700K | v1.0.0 | Dasharo HCL Report |
| 12th Gen Intel(R) Core(TM) i7-12700K | v1.0.0 | Dasharo HCL Report |
| 12th Gen Intel(R) Core(TM) i5-12400 | v1.0.0 | Dasharo HCL Report |
| 12th Gen Intel(R) Core(TM) i5-12600K | v1.1.0 | Dasharo HCL Report |
| 12th Gen Intel(R) Core(TM) i5-12600K | v1.1.0 | Dasharo HCL Report |
...
...
...

The command also extracted the specified files into the folder:

Does this look like the correct result? If so, what are the next steps?

This is correct output:
| 12th Gen Intel(R) Core(TM) i5-12600K | v1.0.0 | Dasharo HCL Report |
| 12th Gen Intel(R) Core(TM) i5-12600K | v1.0.0 | Dasharo HCL Report |
| 12th Gen Intel(R) Core(TM) i5-12600K | v1.0.0 | Dasharo HCL Report |
| 12th Gen Intel(R) Core(TM) i5-12600K | v1.0.0 | Dasharo HCL Report |
| 12th Gen Intel(R) Core(TM) i5-12600K | v1.0.0 | Dasharo HCL Report |
| 12th Gen Intel(R) Core(TM) i5-12600K | v1.0.0 | Dasharo HCL Report |
| 12th Gen Intel(R) Core(TM) i7-12700K | v1.0.0 | Dasharo HCL Report |
| 12th Gen Intel(R) Core(TM) i7-12700K | v1.0.0 | Dasharo HCL Report |
| 12th Gen Intel(R) Core(TM) i5-12400 | v1.0.0 | Dasharo HCL Report |
| 12th Gen Intel(R) Core(TM) i5-12600K | v1.1.0 | Dasharo HCL Report |
| 12th Gen Intel(R) Core(TM) i5-12600K | v1.1.0 | Dasharo HCL Report |

Now the crucial question is what is not in: https://docs.dasharo.com/unified/msi/hcl/
And extend the list.


CP-25569: All properties (A, R, G, B) in GraphvizColor class gets color from a field

From unknown CodePlex user on Friday, 20 June 2014 17:26:02
Code from GraphvizColor.cs:
        public byte A { get { return this.a; } }
        public byte R { get { return this.a; } }
        public byte G { get { return this.a; } }
        public byte B { get { return this.a; } }

change it to:
        public byte A { get { return this.a; } }
        public byte R { get { return this.r; } }
        public byte G { get { return this.g; } }
        public byte B { get { return this.b; } }

Form unknown CodePlex user on Thursday, 04 February 2016 13:48:02
I just got hit by this one.  It's a no-brainer, any reason why it hasn't been fixed?  Is anyone actively maintaining this project?

Form unknown CodePlex user on Friday, 05 February 2016 02:21:54
Another issue with this: it seems that these colors are formatted as "#RRGGBBAA" in the generated .dot file, but from what I can tell, Graphviz doesn't understand the "AA" part, so it doesn't render the color.  I tweaked it to format the colors as "#RRGGBB" (as well as fixing the original bug described above) and it started working.


cannot set Job=0, ParentRef=null on Customer

I'm working through making sure customer/child references are respected in a sync, and the one thing I just can't seem to figure out is how to turn off "Job" mode on a customer once it has been set.
within the qbo website, it's possible, by simply unticking "Is sub-customer" on a Customer and saving the Customer, but how do I do it via API?
the "obvious" answer would be to set 'Job'=false and 'ParentRef'=null, but I get an fatal error message back if I try that: Can't convert Passed Parameter to IPPReferenceType
so what if I use 0 for the ParentRef? now I get this error message: "Error":{"@attributes":{"code":"6150","element":"Job"},"Message":"ParentRef Required Error","Detail":"ParentRef is either required or not if Job is true or false."} <-- while that looks like English, it doesn't actually contain any information...
if I try setting ParentRef to false, I get another fatal error: Can't convert Passed Parameter to IPPReferenceType
so how do I convert a sub-customer back into a top-level customer?

@kaeverens can you please create a support ticket here: https://help.developer.intuit.com/s/


Don't log duplicate ids for image classification

[x] I have added tests to tests to cover my changes.
[ ] I have updated docs/, if necessary.
[ ] I have updated the README.md, if necessary.

In the model logger check if id has been logged before.
If so skip logging it.

wasnt quite ready yet. have to double check all data structure operations in _filter_duplicate_ids :(


No seek method for tokio implementation

I am using tokio as the runtime and from the src I notice that there is no seek method for tokio implementation. I tried a few things like seeking on the underlying reader as below, but it just sets the cursor to the start of the last record
reader.get_mut().seek(SeekFrom::Start(0)).await;
reader.read_record(&mut record).await

Is there any workaround for this? My use case is to start reading the file from the beginning after teh end of file

Yes. seek method is some extra add-on when you use async-std. There is no such method because tokio based AsyncRead trait does not provide it. I have limited time for work on this project currently (only some time during weekends) but will try to more deeply investigate this subject in next couple weeks.
For now the only one workaround that came to my mind is to reopen the file.

@coding-yogi  - please check, if you find time, if PR #9 address your needs.
I have added method rewind which is probably what you need.

Merged PR implements requested functionality


Homepage on pypi points to example.com

At https://pypi.org/project/django-single-session/, the link to "Homepage" points to http://example.com

fixed, thanks!


angular.isDefined(undefined)

I wanted to try this module, but when I ran eslint with --fix option, it completely broke some code.
e.g. if ($scope.something.whatever == undefined) => if (angular.isDefined(undefined))
So it's not trustworthy :(

Thanks for reporting this issue! This repo is just a config file. The actual plugin is at https://github.com/Gillespie59/eslint-plugin-angular. Report this issue over there and I'm sure they can take a look at it.

I'm using eslint-plugin-angular with extends: "plugin:angular/johnpapa" without this issue.
It was only when I tried eslint-config-angular with extends: "angular" that I observed the problem.


PUT or POST with empty bodies gives me 415 Media type not supported

If I create an endpoint that uses either a PUT or a POST verb, and either the parameters are not needed (EmptyRequest) or the parameters are fully contained within the route ("foo/{Id}"), then shouldn't I be able to send the request with an empty body for the data (works just fine with GET verbs).
When I do that I always get back a 415 Media type not supported exception.
The only workaround I've found is to send "{}" as the body of the request.
But this is highly inconvenient. For example, let's say the endpoint is a web hook, that means you can't just configure your system to send a regular request, you have to have the system configured to send "{}" in with the body, which might not be very obvious to the user and they'll be left wondering why their webhook doesn't work.
Has anyone else run into this or am I doing something wrong? I didn't find anything in the docs about it. Thank you.

i believe the following should answer your question: https://github.com/FastEndpoints/FastEndpoints/issues/492#issuecomment-1740210893


Beefy newSignatureCommitment collateral and minsupport implementation

https://github.com/darwinia-network/darwinia-bridge-sol/blob/46fd52e1fc36206723e0b6bb3cebc72715b79192/contracts/bridge/contracts/binance/LightClientBridge.sol#L350

Fixed in #68


https://try.gogs.io down

如题！

Thanks for report!
I'm rebuilding my server and will come with a fresh installation of Gogs(all old data has been deleted)
Should be up today(Jan 28, EST) :smile:

Back online!


Install packages?

Do I need to install new package to run this application? Or just npm start
If yes, would be nice to include packages that need to be installed in the readme :)

Yes do install the packages.

I would like to contribute for the frontend. Do you have any design that I can implement directly?

The design I want to implement is something like this Link

Thanks, I'll have a look


style: outline hover removed and icons in extra features

In general, dropdown item icons have been added, the active class has been duplicated to cover both navBar and dropdown items; dropdown items use onclick to reset the URL state value. (By using Links instead of the standard a tags, the page only renders the component referring to the page that changed, so a state is needed to identify when this happens).

yay!

Great Job. I just ran the code tested it all out and it's perfect. Thank you so much. Now you should be listed as a collaborator on this repo. Don't forget to update your main branch before tackling something else if you are going to continue contributing.

Thanks! Already looking for another issue to work on.

Take a peek at issue More work needed for messaging page #85  I added some links in the comment on how to write it. I'm working on it right now but if you can figure it out or we can figure it out together, awsome.


On-chain events persistence

This PR adds the possibility to save all the on-chain events in an SQLite table. This is useful since it allows the validator to have an off-chain (i.e.: not needing Alchemy/Infura API).
Having this information unlocks many uses such as analytics, benchmarks, future features impact testing, detailed inspection of real usage, etc.
The feature is enabled by using a new configuration attribute PersistEvents, in the EventFeed section of the chains. The runtime cost of the feature is close to the lowest it can be, since we the validator, save this information with the same stream of EventFeed events that it channels to the EventProcessor.
Enabling this feature makes the DB grow since event information isn’t negligible. I’ve run locally a cold sync with event persistence enabled, and the resulting DB is 262MiB compared to ~50MiB without event persistence. This makes sense since event persistence has a linear growth impact compared to the rest of the state which isn’t necessarily linear (e.g., UPDATE or DELETE queries).
The generated information is stored in a table:
CREATE TABLE system_evm_events (
    chain_id INTEGER NOT NULL,
    event_json TEXT NOT NULL,
    event_type TEXT NOT NULL,
    address TEXT NOT NULL,
    topics TEXT NOT NULL,
    data BLOB NOT NULL,
    block_number INTEGER NOT NULL,
    tx_hash TEXT NOT NULL,
    tx_index INTEGER NOT NULL,
    block_hash TEXT NOT NULL,
    event_index INTEGER NOT NULL,

    PRIMARY KEY(chain_id, tx_hash, event_index)
);
CREATE INDEX system_evm_events_chain_id_tx_hash on system_evm_events(chain_id, tx_hash);

All the fields but the first three are the raw ones from types.Log Ethereum API. The top three columns are enhanced information, notably:

event_type contains a friendly name of the type (e.g: ContractRunSQL, ContractCreateTable, etc)
event_json contains a JSON of the event data (e.g: ~an unmarshaled version of the data column). This is very useful to inspect particular event data with the ->> notation in SQLite JSON support. (e.g: tableID, caller, statements, etc).

Note that the raw log information only has block_number as time dimension data, which might be annoying for analytics or general understanding. Getting the wall clock timestamp requires that we do an extra API call for the timestamp of the block.
Doing these extra API calls to get the wall clock timestamp has some additional costs:

More calls to the ETH node API, thus higher costs for Alchemy/Infura.
External API calls are slow, which can hurt sync times if done synchronously.

To solve this, there’s a new top configuration section:
"Analytics": {
        "FetchExtraBlockInfo": true
 },

If FetchExtraBlockInfo is true, a background daemon will start filling a separate table:
CREATE TABLE system_evm_blocks (
    chain_id INTEGER NOT NULL,
    block_number INTEGER NOT NULL,
    timestamp INTEGER NOT NULL,

    PRIMARY KEY(chain_id, block_number)
);

This allows doing a JOIN by chain_id, block_number to get the wall clock timestamp of the event.
This table is filled in the background/asynchronously, thus not impacting the validator sync times and making it an optional feature if the validator is fine with having some cost overhead.

Really nice read. Exciting stuff.

In addition, the database growth is something that concerned me a bit. It will be important to watch closely how the size of the system_evm_events table grows and how queries executed there are performing. SQLite's storage model is not optimized for analytics, so as the number of events grows I expect analytical queries to get quite slow especially because of the JOIN and possible JSON operation in the event_json field. I'm not sure how the analytical use cases will unfold yet, so not worth worrying too much. But something to have in mind.

For sure, I was already thinking of that. For a while we can make analytics directly in the validator database, so we avoid building a lot of infra unnecessarily.
But in reality, system_evm_events should be only the source of truth that the validator is building. Probably in the future, we need to do some live replication of this data outside of the validator VM, and:

Probably offload analytics load from the VM
After we have system_evm_events replicated elsewhere, we can have ETLs do whatever transformation is needed for analytics. We can use Postgres, or even an analytics kind of DB (or even a cloud service).
At some point, we can create some background process to "move" old history to a separate SQLite DB so we archive it and have some bound in the size of this table.

That's what is on my mind for the medium or long term. LMK if makes sense to you.

Makes sense to me. Pretty much what's on my mind as well.


Incorrect meta-package references

Issue in ./help/installation/composer.md
All the example "composer create-project" commands use incorrect meta-package names. Instead of magento/project-community-edition and magento/project-enterprise-edition, they should use magento/product-community-edition and magento/product-enterprise-edition instead (notice it should be "product" instead of "project")

Sorry. False alarm. "Project" is correct as the template project name, while "product" is the name of the meta package.


get create project - by default kotlin/swift

would be nice to be able to select project language kotlin or java for android and swift or objc for IOS, like flutter do  "flutter create -a java -i swift"
workaround:
1-run "flutter create -i swift -a java --org com.example project_name"
2-run "get init"

It will be implementing soon.


chore: release 0.14.0

:robot: I have created a release *beep* *boop*
0.14.0 (2024-04-24)
Features

add html rewrite (#494) (2d3fa09)
add user agent allowlist option (#492) (1986127)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/ethersphere/gateway-proxy/releases/tag/v0.14.0 :sunflower:


Made spot_options in instance_market_options optional

what
Made spot_options in instance_market_options optional.
why
On the AWS Web console there is an option to tick a box that provides guidance on how to create a Launch Template, there works with an EC2 Auto scaling group.
Expanding the "Advanced details" ticking "Request spot instance" you will see most of the options are marked as "Don't include in launch template (recommended)"
Expiry date and Interruption behaviour are not applicable. Having all spot_options as required in this template makes it impossible to enable spot instances in an EC2 Auto Scaling group.
On a related note, but not requiring any change to the module.
The variable instance_initiated_shutdown_behavior should be set to null as it's also not allowed in the Launch Template when used for an EC2 Auto Scaling group
references
https://docs.aws.amazon.com/autoscaling/ec2/userguide/create-launch-template.html

/terratest

@skjensen Thanks for your contribution.
LGTM


--dry-run should print out unsigned transactions

For both ord wallet send and ord wallet inscribe

Ok, I'll do it like that for #808

It might be tricky, I don't know if transactions implement Serialize. If they don't, we probably want to punt on it for now.

I'm actually not sure if this is useful. Closing for now.


rss-datasource not able to load two different feeds

When using the link found on this page it loaded what it thought to be the feed but only showed the feed generator as a feed item (I think it's best if you try that out yourself to see what I mean)
When using the other link it just threw me a NetworkError.

I was able to resolve the first issue on my own by selecting "items" and not "channel" when creating the table, the second error remains though.

@Jocomol, thank you for opening the issue.
I got Origin https://demo.volkovlabs.io is not allowed by Access-Control-Allow-Origin. from my demo server when accessing https://www.golem.de/sonstiges/rss.html. Probably it works only for your region.
When I am trying to connect to https://threatpost.com/feed I got Request header field x-grafana-nocache is not allowed by Access-Control-Allow-Headers., which is Grafana's internal header and I am not sure how to disable it yet. Do you see the same error?

Could you please try this one, it's the google G Suite status feed.

@bygmakavi I don't see the link? Is it Google Workspace? https://www.google.com/appsstatus/dashboard/en/feed.atom

yes it is :)

@bygmakavi You should be able to see Google Workspace Atom feed using the latest version: https://github.com/VolkovLabs/volkovlabs-rss-datasource/releases/tag/v1.3.1
Please let me know if there is anything else.

Thank you kind sir

I was able to get it to work with the vanilla RSS Feed by enabling the CORS-Proxy. Maybe the issue here is the same.

I was able to get it to work with the vanilla RSS Feed by enabling the CORS-Proxy. Maybe the issue here is the same.

Vanilla plugin dosent support ATOM feeds :(

@Jocomol CORS-Proxy was not stable for me. It's great that it's working for you.


Push 0.51.0 release to rubygems.org

Hi,
Right now, at rubygems.org, latest version is 0.50.0. But tag v0.51.0 and release 0.51 in download section exists.

I pushed it a couple of hours ago.
On 19 October 2017 at 00:18, Igor Zubkov<EMAIL_ADDRESS>wrote:

Hi,
Right now, at rubygems.org, latest version is 0.50.0. But tag v0.51.0 and
release 0.51 in download section exists.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/bbatsov/rubocop/issues/4879, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAGVyjbKMLGtDeSGqubSaFcnPmSdv9iQks5stmsbgaJpZM4P-XyR
.


Update image ghcr.io/zoriya/kyoo_front to a3a1c31

This PR contains the following updates:

Package
Update
Change

ghcr.io/zoriya/kyoo_front
digest
6da2573 -> a3a1c31

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

Edited/Blocked Notification
Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.
You can manually request rebase by checking the rebase/retry box above.
⚠ Warning: custom changes will be lost.


Tear free display.

Is it possible to generate smooth animation on the display ? As far as I can see ST7789 Vsync pin is not connected. Are there any alternative methods?

Increase the SPI rate, when the clock rate reaches 32M (135x240x16x60), it can reach 60HZ.
Actually image processing and register setting take some time.

That won't fix tearing, it will just provide (potentially) more FPS, but I want to avoid having images cut in half because I'm updating the ram while a retrace is being done. This is usually usually handled by waiting for vsync signal before writing to vram , in order to avoid memory being overwritten while being read (thus, causing tearing).

.

In which scene are you using the screen tearing. Most of the ST7789's screen modules do not have access to the Vsync pin.


How to set up a Python Web Socket with aiohttp

Proposed title of article
How to set up a Python Web Socket with aiohttp
Proposed article introduction
A socket consists of two major endpoints. One end sends data, and the other end receives data. Take an example of what you can do over the internet. In this case, different nodes/computers are connected to establish a connection that will allow you to send or receive data. A node can be a server or a client. A client sends a request, and the server will send back a response. These connections between the server and client are achieved through sockets. A socket acts as the communication endpoint.
This guide will discuss the socket concept in detail and build client-server socket architecture using the aiohttp.
Key takeaways

What are sockets
The client-server architecture
An introduction to aiohttp
Build a client with aiohttp
Build a server with aiohttp
Send data between the client and the server

Could you please expand upon how your content will differ from what is already available through the documentation? We lean towards content that offers an original viewpoint/approach around programming-centric topics.

@LinusMuema, I believe this doc shows the very basics of a client WebSocket, just like any doc shows a hello world based on a certain technology. An creating an extensive socket that has a client and a server and exchanges data between the two.


CLI issue similar to #1057, but on OS X with rvm

Issue similar to #1057, but on OS X (10.10.5) with rvm.
/Users/me/.heroku/client/lib/heroku/auth.rb:7:in `require': cannot load such file -- netrc (LoadError)
	from /Users/me/.heroku/client/lib/heroku/auth.rb:7:in `<top (required)>'
	from /Users/me/.heroku/client/lib/heroku/client.rb:3:in `require'
	from /Users/me/.heroku/client/lib/heroku/client.rb:3:in `<top (required)>'
	from /Users/me/.rvm/gems/ruby-2.1.2@global/gems/heroku-2.11.1/lib/heroku.rb:6:in `require'
	from /Users/me/.rvm/gems/ruby-2.1.2@global/gems/heroku-2.11.1/lib/heroku.rb:6:in `<top (required)>'
	from /Users/me/.rvm/gems/ruby-2.1.2@global/gems/heroku-2.11.1/bin/heroku:6:in `require'
	from /Users/me/.rvm/gems/ruby-2.1.2@global/gems/heroku-2.11.1/bin/heroku:6:in `<top (required)>'
	from /Users/me/.rvm/rubies/ruby-2.1.2/bin/heroku:23:in `load'
	from /Users/me/.rvm/rubies/ruby-2.1.2/bin/heroku:23:in `<main>'
	from /Users/me/.rvm/gems/ruby-2.1.2/bin/ruby_executable_hooks:15:in `eval'
	from /Users/me/.rvm/gems/ruby-2.1.2/bin/ruby_executable_hooks:15:in `<main>'

Attempted remedy in ruby-2.1.2 was to add netrc to global gemset:
$ ls /Users/me/.rvm/gems/ruby-2.1.2@global/gems
bundler-1.6.2		foreman-0.25.0		launchy-0.4.0		rack-1.3.5		rdoc-4.1.0		rvm-<IP_ADDRESS>
bundler-unload-1.0.2	gem-wrappers-1.2.4	mime-types-1.16		rack-test-0.6.1		rest-client-1.6.7	term-ansicolor-1.0.7
configuration-1.2.0	gem-wrappers-1.2.7	minitest-2.7.0		rake-0.8.7		rubygems-bundler-1.4.4	test-unit-<IP_ADDRESS>
executable-hooks-1.3.2	heroku-2.11.1		netrc-0.11.0		rake-10.1.0		rubyzip-0.9.4		thor-0.14.6

I acknowledge this may be more an rvm than heroku issue.

...sorry, think this is too arcane to pursue and likely the result of the involvement of the "heroku" gem in my Gemfile.


Wallet name and amount on Home

Only the amount should move not the title on clicking ******
https://github.com/bithyve/bitcoin-keeper/assets/107177634/47fcb495-4b7b-46e3-bf4b-0713c815718d

Fixed.

Bottom tile is moving it should not if the Wallet balance is clicked .....a minor one

Completed


fix: Add migration for db to add project_id as a public key constaint

What does this PR do and why?
Provide a description of what this PR does. Link to any relevant GitHub issues, Notion tasks or Discord discussions.
Screenshots or screen recordings
If applicable, provide screenshots or screen recordings to demonstrate the changes.
Acceptance checklist

[ ] I have evaluated the Approval Guidelines for this PR.
[ ] (if relevant) I have tested this PR in all supported browsers.
[ ] (if relevant) I have tested this PR in dark mode and light mode (if applicable).

Current dependencies on/for this PR:

main

PR #3341   👈

This comment was auto-generated by Graphite.


MobilePlatform-Messages API Cleanup

ITS-Pro time category: https://its-pro.ucsd.edu/browse/MA-60
This is complete when:

[x] MobilePlatform-Messages API in Prod and QA are in sync
[x] Have apps subscribe to v1.0.0 in QA
[ ] MobilePlatform-Messages API v2.0.0 in QA is deleted or deployed to Prod

A few applications to unsubscribe from MobilePlatform-Messages API v2.0.0 - @g9singh / @i8wu when time permits.
g1singh	DefaultApplication
icwu	MobileReminders
icwu	MobileReminders2

Unsubbed MobileReminders


#90 document api

not finish, but needed because of big refactoring

Coverage remained the same at 19.77% when pulling dfe86ec7bbb3a1b342229d68a6f22b367b23e56d on #90-document-api into bdaf1bd946dc01df368222f47d897e9f31052bbc on master.

Coverage remained the same at 19.77% when pulling 0a871cc46ba9a8d69eb1fa37ffd6fb87fcd15f53 on #90-document-api into bdaf1bd946dc01df368222f47d897e9f31052bbc on master.

Coverage remained the same at 19.77% when pulling 93417959fd95036d6ea4c00db049f444c214cbca on #90-document-api into bdaf1bd946dc01df368222f47d897e9f31052bbc on master.

Coverage remained the same at 19.77% when pulling 603e7103ca10d7c73717b2cf54932ca843640adb on #90-document-api into bdaf1bd946dc01df368222f47d897e9f31052bbc on master.


Have Cicero Address verification not get called for partial addresses

hub thread: https://powerofus.force.com/0D58000002EKNu5

**lurch: add

Tracking W-008328

we should decide whether each verification service needs these smarts (because only they know what is incomplete to them), or maybe we just change ADDR_Validator.verifyAddressRecords() to ignore any empty or partial addresses.  for example, if the user has a default value on contact for Primary Address Type, then even contacts with no addresses will still get an address object (to save the address type), which then causes the validation, which fails for Cicero.

Salesforce has determined that this issue will not be explored further.


Strong name sign the NUnit2 assemblies

All other AutoFixture assemblies that I have used are strong name signed, but the NUnit2 ones are not.  This makes the assemblies unusable as-is in scenarios where the product/test assemblies are themselves strong name signed.
To support using the NUnit2 assemblies in these scenarios I would like to request strong naming them along with the others.

I don't know the reason that the NUnit2 assemblies aren't signed; could it be that we forgot?
IIRC, at least one AutoFixture assembly is unsigned: AutoFixture.AutoFoq. The reason for that is that Foq itself isn't signed.
It may be the case that there's a similar reason AutoFixture.NUnit2 isn't signed, but I find it more probable that we forgot to do it.

Resolved in AutoFixture.NUnit2 3.32.2 (f3b3dc8b3f6a4df53e77f8872735da3c085808c5).


Port winapi_util from winapi to windows-sys.

This ports winapi_util from using winapi internally to using windows-sys
internally.
The port is mostly straightforward, except that windows-sys declares
constants like FOREGROUND_BLUE with type u32, which is inconvenient
because they are passed to an API that uses u16, but the workaround
is simple and I've filed an issue in windows-sys.
Background: Some projects I'm working on which use winapi_util are
switching to windows-sys because it covers some APIs we need that
winapi lacks and winapi is not responsive on a PR to add them. I don't
know if others are interested in making this change; if not, feel free to
close this.

@retep998 What do you make of the move to windows-sys from winapi? Do you think that's what I should be doing?
@sunfishcode Assuming I do agree with this move, it's going to be logistically challenging given my constrained time. Namely:

This is maybe a big enough change that it might be worth doing a major bump, even though I don't believe there are any technically breaking changes. It just feels bad to swap out such a fundamental dependency in a minor version upgrade.
If I make the switch for this crate, then I'll probably insist on making the switch in every crate I maintain that depends on winapi. The last thing I want is, for example, ripgrep building both winapi and windows-sys. So that means termcolor and walkdir, for example, which are themselves both quite popular. Which means I do not want to go through with this change until I fully understand the trade offs involved here.

Otherwise though, I personally have no particular affinity towards winapi or windows-sys. But that is most likely a result of ignorance rather than any sort of informed opinion.

It appears this change isn't compatible with winapi_util's minimum supported Rust version of 1.34. Empirically, it needs Rust 1.48, which would be another reason to do a major bump.
Looking at ripgrep's Cargo.lock, I see winapi dependencies in two other places:

atty; there is already a PR to port this to windows-sys is here: https://github.com/softprops/atty/pull/54
walkdir: I've now opened a PR to port this to windows-sys: https://github.com/BurntSushi/walkdir/pull/162

I have to look into this and, honestly, it isn't a priority for me. The main issue I have with windows-sys is churn. And I don't know what its compile times look like. I don't want to depend on something that is going to be publishing breaking changes every few months. IMO, it needs to settle down first.
An alternative is inlining the bindings themselves into this crate. I think I'd be more amenable to that.

For the compile times it looks like a win. Cross-compiling winapi-util on my old Linux machine with cargo build --release --offline --target x86_64-pc-windows-gnu gives ~2.5s on master while this PR only takes ~1.4s.
I can't deny that there's some version churn, but I don't think it's that much of a problem. Most of the time it's just a version number bump because the API surface is so large and you're unlikely to use the part that changed.
And windows-sys 0.48 was current for ~8 months, which isn't that short IMO.
parking_lot went the inlined bindings route, but that caused linker and target support issues which had to be fixed by depending on windows-targets instead (https://github.com/Amanieu/parking_lot/pull/378). At that point nothing really was gained in regards to version churn.
(Apparently winapi already misses some import libs which would cause issues with some targets.)
PS: Thanks for the updating the PR so quickly, @sunfishcode.

https://kennykerr.ca/rust-getting-started/standalone-code-generation.html

For the compile times it looks like a win. Cross-compiling winapi-util on my old Linux machine with cargo build --release --offline --target x86_64-pc-windows-gnu gives ~2.5s on master while this PR only takes ~1.4s.

Awesome! Thanks for testing that.

but I don't think it's that much of a problem.

I hear you. But to be clear here, this is a decision for me to make, since I'm the maintainer and the one who will be experiencing the churn. I move pretty slowly, and needing to do semver incompatible updates every few months is too much for me.
If their cadence is every 8 months, that is... perhaps okay. Do they have a release policy written down anywhere?

parking_lot went the inlined bindings route, but that caused linker and target support issues which had to be fixed by depending on windows-targets instead (Amanieu/parking_lot#378). At that point nothing really was gained in regards to version churn.

I was unaware of this issue. That's unfortunate. Indeed, it looks like that doesn't avoid version churn.
The next thing on my list here would be to look at what windows-targets is actually doing, and whether version churn is an intrinsic property of the Windows support required for this crate (I doubt it), and whether we can do something cheaper.

I hear you. But to be clear here, this is a decision for me to make, since I'm the maintainer and the one who will be experiencing the churn.

Obviously and it wasn't my intention to imply otherwise. Apologies if it came across that way.

If their cadence is every 8 months, that is... perhaps okay. Do they have a release policy written down anywhere?

Apparently they switched from a 3-6 months cadence to on-demand releases in Nov 2022 (https://github.com/microsoft/windows-rs/issues/2156#issuecomment-1313876870 and https://github.com/microsoft/windows-rs/issues/2156#issuecomment-1323816991). Might at times be more volatile than every 8 months then.

The next thing on my list here would be to look at what windows-targets is actually doing, and whether version churn is an intrinsic property of the Windows support required for this crate (I doubt it), and whether we can do something cheaper.

winapi contains a bunch of binaries (import libraries) for different platforms that all get downloaded if you use the crate. On the other hand  windows-targets serves as a kind of meta-crate for instead only picking the right libs for your target. Alternatively it can use the new raw-dylib rustc feature to avoid the binaries altogether but only if the user sets an environment variable. This will hopefully become the default (and maybe only) way once the windows-sys MSRV is high enough.
I'll admit you can't beat winapi for stability. It is now only getting security patches so it's very unlikely to ever have a breaking change. On the flip side though it doesn't get new functions, bug fixes or support for new targets.

It is now only getting security patches

While it's not declared as such, from the looks of it, winapi is unmaintained.  So I'm not sure it's even getting security patches.
It's because of that that I acknowledge that winapi is not the long term solution here. And, windows-sys is maintained by the Microsoft folks, which is nice.
I've been thinking about this more, and I'm leaning towards just merging this PR and seeing what the churn feels like.

It is now only getting security patches

While it's not declared as such, from the looks of it, winapi is unmaintained.  So I'm not sure it's even getting security patches.

If a security patch is ever needed, you can always just poke me on discord. But yeah, windows-rs killed any interest I had in continuing to work on winapi, so barring something serious I have no intention of updating winapi further.

We've hit issues while porting our project to the new arm64ec-pc-windows-msvc target . winapi doesn't support (and won't be supporting) it, but gets included anyway through the walkdir dependency, effectively breaking our build. windows-sys on the other hand supports that target since 0.56.

This PR is on crates.io in winapi-util 0.1.7.


[CLOSED] Add how to add a new document format to readme

 Issue by tommyp
Monday 27 October 2014 at 11:06 GMT
Originally opened as https://github.com/alphagov/specialist-publisher/pull/292

This commit adds a step by step guide for adding a new document format along with how to to test that document format.

tommyp included the following code: https://github.com/alphagov/specialist-publisher/pull/292/commits

 Comment by kalleth
Monday 27 October 2014 at 11:22 GMT

:+1:


Cleanup

Q
A

Is bugfix?
❌

New feature?
❌

Breaks BC?
✔

Tests pass?
-

Fixed issues
-

 Clean up yii-authclient

This is just cleaning. Let's refactor individual PRs.

👍


Guidance Conflict - Application Gateway Deployments

There appears to be a conflict in advice regarding deployment of application gateways. This needs to be clarified or the older update removed so that it's not confusing for customers
Conflicting Recommendation 1 = Application Gateways should be used in perimeter networks (the hub): Perimeter networks - Cloud Adoption Framework | Microsoft Learn - from the GitHub repo, looks like this has been here since 2019 so it's the older one.
Conflicting Recommendation 2 = "Treat the Application Gateway as an application component and deploy it in a spoke virtual network not as a shared resource in the hub": Plan for application delivery - Cloud Adoption Framework | Microsoft Learn
In my experience, there are cases for both and for various reasons. However, at present it's not called out why you would pick one over the other, so without additional context this is conflicting and confusing for customers.

Thank you for your feedback. We have created internal ticket 196675 to track and investigate this issue.

#please-close

What was the resolution for this?
Kind regards,
Alex Rose (he/him)
Senior Cloud Solutions Architect Engineer (Azure Core)
Customer Success Unit
<EMAIL_ADDRESS>Follow me on Linkedinhttps://www.linkedin.com/in/alexander-rose-networks-and-cloud/
@.***
@.***
Microsoft Azurehttps://azure.microsoft.com/en-us/overview/what-is-azure/
@.https://twitter.com/microsoft @. https://www.facebook.com/Microsoft @.*** https://www.linkedin.com/company/microsoft @.*** https://www.youtube.com/user/Microsoft @.*** https://www.yammer.com/
This and subsequent emails on the same topic are for discussion and information purposes only. Only those matters set out in a fully executed agreement are legally binding. This email may contain confidential information and should not be shared with any third party without the prior written agreement of Microsoft. If you are not the intended recipient, take no action and contact the sender immediately.
Microsoft Limited (company number 01624297) is a company registered in England and Wales whose registered office is at Microsoft Campus, Thames Valley Park, Reading RG6 1WG.
From: Jason Bouska @.>
Sent: Friday, May 31, 2024 8:24 PM
To: MicrosoftDocs/cloud-adoption-framework @.>
Cc: Alex Rose @.>; Author @.>
Subject: Re: [MicrosoftDocs/cloud-adoption-framework] Guidance Conflict - Application Gateway Deployments (Issue #1280)
Thank you for your feedback. We have created internal ticket 196675 to track and investigate this issue.

Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/cloud-adoption-framework/issues/1280#issuecomment-2142857711, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BERXMTME774BUHXSK4S2DC3ZFDE4HAVCNFSM6AAAAABANB35XSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNBSHA2TONZRGE.
You are receiving this because you authored the thread.Message ID<EMAIL_ADDRESS>

Hey @MohawkAlexMS , The issue you opened is in our backlog and has not been addressed yet.  We are transitioning to another feedback system and retiring GitHub Issues.


API discussion

Previous / next should wrap around both playlist ends, shouldn't they? This is the behavior of ExoPlayer but not on the web.

The bidirectional behavior of ExoPlayer is implemented in other apps (e.g. Spotify or Apple Music) and makes sense. A dedicated task will be created for the web.


Add new feature : upload file to walrus by multiple workers

Mainly changed:

Add config params workers with Config
Add clap params workers with GeneralArgs
upload and publish use multiple workers as configuration.

Example usage:
site-builder --workers 10 --config ./client_config.yaml update --epochs 200 ./site

Thank you for the contribution @v1xingyue ! We will review your PR shortly.

Ya.  But  I'm not sure what happened.
Sometimes error will happend like this :
RPC call failed: ErrorObject { code: ServerError(-32002), message: "Failed to sign transaction by a quorum of validators because one or more of its objects is reserved for another transaction. Retried transaction 272PdQfqLqJSZAT42nLjePRji5CXF967AnBPpJCrdpFW (succeeded) because it was able to gather the necessary votes. Other transactions locking these objects:\n- 272PdQfqLqJSZAT42nLjePRji5CXF967AnBPpJCrdpFW (stake 75.92)

I don't know why this happened and what should I do?

Thank you for the contribution @v1xingyue ! We will review your PR shortly.

Ya. But I'm not sure what happened. Sometimes error will happend like this :
RPC call failed: ErrorObject { code: ServerError(-32002), message: "Failed to sign transaction by a quorum of validators because one or more of its objects is reserved for another transaction. Retried transaction 272PdQfqLqJSZAT42nLjePRji5CXF967AnBPpJCrdpFW (succeeded) because it was able to gather the necessary votes. Other transactions locking these objects:\n- 272PdQfqLqJSZAT42nLjePRji5CXF967AnBPpJCrdpFW (stake 75.92)

I don't know why this happened and what should I do?

Hey @v1xingyue , many thanks for the contribution. Unfortunately parallel uploads are quite tricky. The problem is that the walrus clients all use the same wallet, and therefore it may happen that they try to use the same gas coin or storage object at the same time, creating a race condition that is not allowed on chain (it would be basically double spending!)
I'm working on the walrus core side to improve this functionality on the walrus client side. However, until that is ready, I think there is no good way to implement parallel uploads.
Please reopen the pull request if I misunderstoon anything! And thanks again for working with walrus sites.

Thank you for the contribution @v1xingyue ! We will review your PR shortly.

Ya. But I'm not sure what happened. Sometimes error will happend like this :
RPC call failed: ErrorObject { code: ServerError(-32002), message: "Failed to sign transaction by a quorum of validators because one or more of its objects is reserved for another transaction. Retried transaction 272PdQfqLqJSZAT42nLjePRji5CXF967AnBPpJCrdpFW (succeeded) because it was able to gather the necessary votes. Other transactions locking these objects:\n- 272PdQfqLqJSZAT42nLjePRji5CXF967AnBPpJCrdpFW (stake 75.92)

I don't know why this happened and what should I do?

Hey @v1xingyue , many thanks for the contribution. Unfortunately parallel uploads are quite tricky. The problem is that the walrus clients all use the same wallet, and therefore it may happen that they try to use the same gas coin or storage object at the same time, creating a race condition that is not allowed on chain (it would be basically double spending!)
I'm working on the walrus core side to improve this functionality on the walrus client side. However, until that is ready, I think there is no good way to implement parallel uploads.
Please reopen the pull request if I misunderstoon anything! And thanks again for working with walrus sites.

Seems, I got the problem.
What if I split coin first, and each transaction use the diffrent coin as the split usage.
Then that will be fine.


Reuse Assertions across different tests

It would be nice if we could re use the same assertions that are common across different test cases (it). Assume there are 10 assertions a1 to a10 for it1. For it2 there is the same assertions a1 to a10 plus a11. Today, we need to repeat a1 to a10 twice.

Sounds good if we can have something like
assertionTemplate:
  - name: myAsserts
    template: |
      equal:
        path: some.path.{{ .prop }}
        value: {{ .val }}
     ...

and use it like
...
- assertions:
    withTemplate:
      name: myAsserts
      args:
        prop: ...
        val: ...

so the logic can be easily reuse.

Oh and you can alway use yaml template within the same file:
- it: test1
  asserts: &myAssert
    - ...
- it: test2
  asserts: *myAssert

Close due to archiving repository.
Sorry for not presenting so long. I've been working on another project and don't have time to for helm-unittest.
Please consider other working forks like quintush/helm-unittest.

Can we re-open this @quintush, I haven't seen this feature implemented yet, and it seems that you're actively maintaining and is a collaborator for this repo.


Flow errors when Array is assigned to an Array field when x subclass of y

Here is the code to reproduce this issue:
class VirtualElement {
  type = "Element"
  children: Array<VirtualElement>
}

class ElementNode extends VirtualElement {
  constructor(children:Array<ElementNode>) {
    super()
    this.children = children
  }
}

Which produces following errors
3:   children: Array<VirtualElement>
                     ^ VirtualElement. This type is incompatible with
7:   constructor(children:Array<ElementNode>) {
                                ^ ElementNode

Maybe I'm missing something, but I would expect this to type while it isn't.

Oddly enough following code type checks
class VirtualElement {
  type = "Element"
  children: Array<VirtualElement>
}

class ElementNode extends VirtualElement {
  constructor(children:Array<ElementNode>) {
    super()
    this.children = [...children]
  }
}

But then performance overhead of this is unacceptable :(

I also tried going with types vs classes, but I run into same issue:
type VirtualElement = {
  type: "Element",
  children: Array<VirtualElement>
}

class ElementNode {
  type = "Element"
  children: Array<VirtualElement>
  constructor(children:Array<ElementNode>) {
    this.children = children
  }
}

Also worth mentioning that problem only occurs when Array is involved for example following code works fine:
interface VirtualElement {
  type: "Element",
  parent: VirtualElement
}

class ElementNode {
  type = "Element"
  parent: VirtualElement
  constructor(parent:ElementNode) {
    this.parent = parent
  }
}

This is correct, it's the classic invariance example:
const dogs: Array<Dog> = getArrayOfDogs();
const animals: Array<Animal> = dogs; // this shouldn't type check, because...
animals.push(new Cat()); // oh no, my dogs array has a cat in it!

I guess what I really wanted was along these lines instead:
class VirtualElement <Child:VirtualElement<*>> {
  type = "Element"
  children: Array<Child>
}

class ElementNode extends VirtualElement<ElementNode> {
  children: Array<ElementNode>
  constructor(children:Array<ElementNode>) {
    super()
    this.children = children
  }
}

Here's a simpler test case
class Base {
  id: string;
}

class Test extends Base {
  id: string;
}

const getFirst = (t: Array<Base>): Base => {
  return t[0];
};

const b = new Test();

// This works
getFirst([ b ]);
// This works
const bArray1 = [ b ];
getFirst(bArray1);
// This does not work
const bArray2: Array<Test> = [ b ];
getFirst(bArray2);

output
11: const getFirst = (t: Array<Base>): Base => {
                               ^ Base. This type is incompatible with
23: const bArray2: Array<Test> = [ b ];
                         ^ Test

Closing, not a bug

@vkurchatkin I think maybe morphing this bug into providing better error message would be better than just closing. Once you consider mutation as pointed out by @erikdesjardins behavior starts to make sense, but often times people (at least on my team) tend to not consider that, partially due to algebraic data types being mostly available in languages that are free of this problem due to immutability. I would highly recommend include that in error message.


Add csv-to-task converter in scratch

Added csv-to-task converter

@simonholgate Since I sneaked in the PEP8 stuff this is now failing, it's only polite that I'll fix it ;)


Add particle coarsening

based on #473

@LasNikas This has been superseeded right?

superseded in #652 (see #643 )


question

Is VirConv-S.yaml right?5 epochs? I train it. But 5 performance is not good. I hope you can answer, thank you!

What's your performance, can you provide more details?
Seems that you did not use the pre-trained VirConv-T to initialize the VirConv-S.
Please check the readme to train the VirConv-S correctly.

ok， I really forget to train T first， sorry.

Do I need to repeat T every time so that I can train S? I use 7 3090s to train T once, but the first time S is 90.3AP, and the second time is 88.8.

The performance is much depended on your initial VirConv-T model.
Please do not choose the best VirConv-T to initialize the VirConv-S, as the VirConv-T may be overfitted to labeled data.
Choosing a VirConv-T checkpoint with high learning rate is better.
For example, if you trained the VirConv-T 60 epochs, you could choose the checkpoint from 40 epoch for initializing.
Besides, the performance also has some gap between different devices (based on my past experiment). But at least, I can obtain 90.5+AP.
Alternatively, the training epoch can be further tunned (such as 10 epoch, sometimes give me better results).


Migrate from nunit to xunit

As part of the move to the new csproj/MSBuild project format I decided to migrate existing tests from nunit to xunit.
Some changes:

xunit requires minimum .NET Framework version of 4.5.2 as target

change is only required for test projects; does not affect main project.

Migration completed as part of 2520cff2dacafe803322b6d760b21609e1253137 and 6ac870f8465f3810a726f57439f242425890ee1c.
There still seems to be an issue with the Test Runner in VS 2017. For some reason some tests fail with various different reasons. This needs to be looked into.
The AppVeyor build was adapted as well (986fcb1f9e3d564101cf560ff76e33adebb1db8b) to be able to run the xunit tests. Tests are still run for all target frameworks (net452 & netcore1.0).
As noted before the test projects had to be updated to target net452 instead of net451 due to xunit framework requirements.

The issue with tests failing when using VS is still persistent in the final release of VS 2017.
The following issues target this issue:

[ ] https://github.com/Microsoft/vstest/issues/391
[ ] https://github.com/xunit/xunit/issues/1132

According to the latest comment on https://github.com/Microsoft/vstest/issues/391 It seems that adding
<AutoGenerateBindingRedirects>true</AutoGenerateBindingRedirects> <GenerateBindingRedirectsOutputType>true</GenerateBindingRedirectsOutputType>
does the trick.


liblept172 cannot be loaded on different PC

So far, I had no problem using this library for c# application using NuGet package.
But recently, I found it is not working on a laptop.
The error are like these :

Tesseract Information: 0 : Current platform: x86
Tesseract Information: 0 : Checking custom search location './' for 'liblept172.dll' on platform x86.
Tesseract Information: 0 : Trying to load native library "./x86\liblept172.dll"...
Tesseract Error: 0 : Failed to load native library "./x86\liblept172.dll".
Check windows event log.
Tesseract Information: 0 : Checking executing application domain location 'C:\Users\xx\Desktop\Release' for 'liblept172.dll' on platform x86.
Tesseract Information: 0 : Trying to load native library "C:\Users\xx\Desktop\Release\x86\liblept172.dll"...
Tesseract Error: 0 : Failed to load native library "C:\Users\xx\Desktop\Release\x86\liblept172.dll".
Check windows event log.

I already write the custom path using TesseractEnviornment.CustomSearchPath = @"./";
It will works on some PC.
But not in my laptop.
I already has the dll on Release folder both in x86 or x64, since I used "Copy Always" option.
I wonder why it is still failing ?

Hmmm, just read this...
Common reasons for failure are:
The Visual Studio 2015 x86 & x64 Runtime is not installed, as detailed on the main readme page these can be found here.
I will check if this is the solution


add Kubernetes Container name to tags

What does this PR do?
This PR adds a tag to docker_daemon and kubernetes metrics pod_container_name that takes the name of the Kubernetes Container resource corresponding to the container in question. This is kinda subtle (I'd love some feedback on naming / good ways to document something like this) - the name of a Container resource https://kubernetes.io/docs/api-reference/v1.6/#container-v1-core, not the actual Docker name of the container (which is already covered in container_name)
Motivation
Because some stats are reported on a per-container basis, being able to easily select data using the same names that are in a Pod manifest is useful.
Testing Guidelines
Notably, I haven't been able to get the docker_daemon check's tests working locally (on either OSX or Linux), so I'm hoping that the CI system tells me if I missed anything 😄
This PR has a corresponding change to dd-agent's kubeutil.py to have the CONTAINER_NAME_LABEL constant - submitting that separately.

I'm just realizing that there's no way the tests will pass here b/c they require the change in https://github.com/DataDog/dd-agent/pull/3405 to not fail - any tips for how to get travis & appveyor to do such a build?

@sophaskins Can we catch up after the holiday weekend to discuss?

Absolutely!

I'm a little confused by this test failure - does anyone have advice?

Fixed, thanks @sophaskins !