How to inference with my own model?

After trained the model with my dataset. I got the checkpoints folder as shown below, but I don't know what to do next to be able to inference. Can you help me?

@TheK2NumberOne you can use the notebook (https://colab.research.google.com/drive/1LY5Ds6qyr_Drpp9WSdt-ZEMvvrFICdEx#scrollTo=VucO3HSMoJkz) or modify the generate_bloom.py, for instance.
Good luck

Hi @linhduongtuan. I read the notebook and the generate_bloom.py, but I don't see how to load checkpoint after training.
@TheK2NumberOne  Do you have any updates? Thank you for reply.


Keep indeterminate RefreshProgressIndicator spinning until end of time

Fixes https://github.com/flutter/flutter/issues/17923.

/cc @HansMuller

lol

await tester.pump(const Duration(days: 9999))
NICE

This is causing failures when trying to roll it into Google:
══╡ EXCEPTION CAUGHT BY FLUTTER TEST FRAMEWORK ╞════════════════════════════════════════════════════
The following assertion was thrown running a test:
pumpAndSettle timed out

When the exception was thrown, this was the stack:
#0      WidgetTester.pumpAndSettle.<anonymous closure> (package:flutter_test/src/widget_tester.dart:291:11)
<asynchronous suspension>
#3      TestAsyncUtils.guard (package:flutter_test/src/test_async_utils.dart:69:44)
#4      WidgetTester.pumpAndSettle (package:flutter_test/src/widget_tester.dart:287:27)
...

Is this the fault of the test, or should this be rolled back?

Paste more of the stack?

At a guess, it's the fault of the test. It probably starts a refresh and doesn't end it.

It's customer:mulligan code - ping me for the link to the next stack frame (it's in the test)

I'll take a look at this tomorrow.


Add ubuntu workflow

Added workflow to test creation of the image and it's functionality. Will need alignment with #1 on the command to ensure building on ubuntu. Unfortunately github actions doesn't allow building on other than windows/macos/ubuntu.
Actions visible at https://github.com/Sue-unix-experts/docker-drawio-mkdocs/actions

LGTM


chore(main): release 1.1.41

:robot: I have created a release beep boop
1.1.41 (2023-07-31)
Features

next.config.js: add logging configuration based on AIRBROKE_LOG_LEVEL environment variable to enable verbose logging if set to 'verbose' (264015c)
route.ts: update default OpenAI engine model from 'gpt-4' to 'gpt-3.5-turbo' if nothing is set (07d4f9f)

Bug Fixes

deps: update dependency @headlessui/react to v1.7.16 (#160) (44d7fa7)
deps: update dependency ai to v2.1.27 (#161) (3521094)
deps: update dependency ai to v2.1.28 (9879eea)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/icoretech/airbroke/releases/tag/v1.1.41 :sunflower:


Add initial Splunk check.

What's this PR do?
Adds a Splunk check that emits lots of master-shaped metrics about a Splunk cluster!
Motivation
We need to measure, monitor and understand various KPIs from Splunk.
Notes
See README!
This could probably to the splunk mainline repo, but starting here or easy deployment on our end.
r? @krstripe

Ok @krstripe, this is ready for another look. Adding a note to your earlier check question.

lgtm


Basic values in Serbian language

...  in Cyrillic alphabet

Please start the first PR for a language by contributing the homeassistant_HassTurnOn and homeassistant_HassTurnOff files together with the errors in common.


Planning the rails app

Shall we build an ecommerce app that looks like this? https://codepen.io/rohan10/pen/kEqno

I have created a contentstack but have no idea if I have structured it correctly. Need your review and input

This is what my stacks look like:

Is this correct?

Below is the structure -
Product
Name/Title (text, singleline)
Description (text, multiline)
Featured Images (file, image, multiple)
Price (number)
Offer Price (number)
Categories (reference, category, multiple)
Sizes (reference, size, multiple)
Brands (reference, brand)
In Stock? (boolean)
Related Products (reference, self, multiple)
Size
Name/Title (text, singleline)
Description (text, multiline)
Brand
Title (text, singleline)
Logo (file, image)
Description (text, multiline)
Category
Title (text, singleline)
Image (file, image)
Description (text, multiline)


firefox is not needed for ocropy to be installed

Installing firefox pulls in a lot of dependencies that are not needed in a headless setup.

Thank you!


Unreadable text in the adventure guide

Hey
I came across another bug that I'd like to point out. When opening the adventure guide, the text on one of the panes becomes thick and is unreadable. I've disabled every other addon to make sure nothing is causing trouble.

Keep up the good work!

Fixed :)
Update still pending on wowinterface, but live on my website http://gempui.danielps1.de


link popover position.

I'm submitting a bug/fix

[ ] Regression (a behavior that used to work and stopped working in a new release)
[x] Bug report
[ ] Enhancement
[ ] Feature request
[ ] Documentation issue or request

Description
When you use a dialog box with ngx-editor inside and you open this dialog box while you have scrolled far down the site and you try to make a link. Then the link popover does not show.
Way to fix this is change
.ngxePopover.popover {
        position: fixed;
}

Version Information
ngx-editor: 3.3.0
angular: 5.0.2 and 6.0.5

### Browser

- [x] Chrome - 66.0.3359.181
- [ ] Mozilla Firefox - x.x.x
- [ ] Opera - x.x.x
- [ ] Microsoft Edge - x.x.x

Finally, fixed in v5-alpha.9.


Support request timeouts in the UrlReader

For some applications, it would be helpful to be able to timeout a readUrl(...) request. We sometimes use a circuit breaker in combination with a timeout from cockatiel to wrap calls in our custom plugins. However, when we timeout, the call is still in progress and might also finish after we went ahead with other tasks. We could also handle this by discarding a response after it has finished, but that isn't a really good solution.
For fetch calls, the following should work:
const timeoutMs = 5000;

const controller = new AbortController();
setTimeout(() => controller.abort(), timeoutMs);

fetch('https://example.com', { signal: controller.signal });

It might be good to provide a helper function that creates the signal.

Possible Implementation

Add a { timeout?: number } property to ReadUrlOptions and SearchOptions.
Add the (optional) timeout logic to all UrlProcessors that either use fetch or which library support timeouts.

Still relevant!

Gave this a shot ^

I preferred to send in the actual signal instead, since that's the API that should be the most familiar, and is directly usable by the implementation. It also plays well with a possible future context, which wants to merge different timeouts/deadlines etc.


[$500] Web - Split Scan - Console error shows up when clicking Split on empty split action menu

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: v1.4.11-1
Reproducible in staging?: y
Reproducible in production?: n
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
Action Performed:

Go to staging.new.expensify.com.
Go to workspace chat > + > Split bill > Scan.
Create a split scan request.
Click on the spit preview.
Click Split.

Expected Result:
No console error shows up.
Actual Result:
Console error shows up.
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence
https://github.com/Expensify/App/assets/93399543/c4dba984-a2bc-4358-aca2-8419fd815f0b
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~014fa32ba034ba77de
Upwork Job ID:<PHONE_NUMBER>724713472
Last Price Increase: 2023-12-11

Most likely related to the refactor https://github.com/Expensify/App/pull/28618

Proposal
Please re-state the problem that we are trying to solve in this issue.
Err occur when clicking on empty split action menu
What is the root cause of that problem?
we are not safely accessting the trasnactionID:
https://github.com/Expensify/App/blob/243f932043089c625b0f6be4dea43925177b96c2/src/libs/actions/IOU.js#L1690
What changes do you think we should make in order to solve the problem?
use lodash get
_get(updatedTransaction,"trasnactionID")

@abzokhattab that solution is not enough as there are other properties required which cause console error

@mountiny Please remove Help wanted label here

We should show error on the form if the Amount and merchant have not been updated

I think disabling the button will be more correct

ah yeah, whatever our Forms.md dictate

Sorry, we should show error according to Forms.md

Thank you @bernhardoj, that looks like a correct fix. Would you mind putting that into proposal form?

Thanks, that looks great. Assigning to you now.

@shubham1206agra friendly reminder on the checklist so that we can pay this out tomorrow.

BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

[x]  [@shubham1206agra] The PR that introduced the bug has been identified. Link to the PR: https://github.com/Expensify/App/pull/28618
[x]  [@shubham1206agra] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment: https://github.com/Expensify/App/pull/28618/files#r1432819995
[x]  [@shubham1206agra] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion: Not required
[x]  [@shubham1206agra] Determine if we should create a regression test for this bug. No as we have already caught this in deploy testing
[x]  [@shubham1206agra] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.
[ ]  [@puneetlath] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:

Done

All paid. Thanks everyone!


client/executeCommand

See: https://github.com/microsoft/language-server-protocol/issues/1117

If this ultimately also leads to standardizing commands like "run auto-complete" and "commit completion" in a client-neutral way then I'm okay with this.

If this ultimately also leads to standardizing commands like "run auto-complete" and "commit completion" in a client-neutral way then I'm okay with this.

I don't get the use-case here, the client is supposed to orchestrate that directly with LSP operations, why would command be useful for that?
If we can identify some generally useful server side commands that we're ready to spec, then it's better to just specify them as proper LSP operation, with proper parameters definition and so on than leaving it in a pot-pourri of command ids without finer specification.

I don't get the use-case here, the client is supposed to orchestrate that directly with LSP operations, why would command be useful for that?

There are servers that put "command": "editor.action.triggerSuggest" in some of their completion items. This means "show the auto-complete widget". But it's not standardized.

If we can identify some generally useful server side commands that we're ready to spec, then it's better to just specify them as proper LSP operation, with proper parameters definition and so on than leaving it in a pot-pourri of command ids without finer specification.

For sure :)

@kdvolder thanks for the PR. Besides updating the specification we need a reference implementation somewhere as well. This can be VS Code, Eclipse or any other client. Is someone willing to do that as well?

This can be VS Code, Eclipse or any other client. Is someone willing to do that as well?

I was planning on doing it yes, just need to find the time :-)

@kdvolder great.

I appreciate the work being done here and aim to ship something.
Do you mind describing some concrete use cases this is aiming to solve?
I ran into at least two use cases myself where I had the need to execute client-side commands:

open completion prompt
show references

In both cases these are commands that would benefit from being linked directly from their relevant methods - i.e. CompletionItem.command or CodeLens.command.
Executing a separate standalone method would require either extra roundtrip where the server implements some kind of a proxy server-side command for any client-side command, or somehow entirely bypass the existing workflow.
Are there some other use cases this is meant to address?

I agree with @rwols here that for server to not know what commands are available on the client it makes it practically impossible to provide a decent UX in cases I outlined above. Imagine that server implements code lens to show reference counts, user clicks to "5 references", linking to editor.action.showReferences and the client passes it back to the server because it doesn't implement it. The server can't do anything about it so the click ends up as no-op in the UI. That doesn't seem ideal? It would seem better if the server could just suppress the code lens entirely and avoid showing the link in the first place.

I just found a use case for this feature. I assume it would be useful for updating some UI elements when the server deems it necessary.
The client may pull certain details (such as language/dependency versions or constraints, or some sort of hierarchy) about the codebase via custom command, but these details may get outdated as the user works on the codebase. It would therefore be useful for the server to notify the client when such details change.
I suppose that is the reason why these refresh commands exist anyway

workspace/codeLens/refresh
workspace/semanticTokens/refresh


Support language-specific literals, expressions and statements

TESTed currently only supports language-agnostic expressions and statements to achieve the goal of programming-language agnostic test cases.
However, TESTed-DSL might also be used as a common format for specifying test suites, even for programming exercises that only target a single programming language or a limited list of programming languages. We could also support those use cases.
For exercises that target a single programming language, we could add a top-level setting programming_language: '<language>' to set a specific programming language. Its default value (e.g. 'abstract') is the current behavior: all expected return values (return), expressions (expression) and statements (statement) are interpreted as expressed in the abstract programming language of TESTed-DSL and translated on-the-fly into the programming language of the submission (or oracle). However, if the programming-language attribute is for example set to javascript, the test suite becomes JavaScript-specific, and all return values, expressions and statements are interpreted as expressed in JavaScript. This would obviate the need to translate the values, expression and statements in another language, and allow using language-specific syntax/constructs that are not supported in the abstract programming language of TESTed (e.g. anonymous functions).
For exercises that target a limited list of programming languages, we might provide language-specific representations for all target language at all places where the language-agnostic representation is not supported. Something like
- cases:
  # language-specific
  - expression:
      'python': "sort_words(['SPAM', 'eggs', 'bacon'], lambda word: word.upper())"
      'javascript': 'sortWords(["SPAM", "eggs", "bacon"], word => word.toUpperCase())'
  # language-agnostic
  - return: ['bacon', 'eggs', 'SPAM']

This would allow mixing language-specific and language-agnostic values, expressions and statements in a single test suite. If there's a need, wherever language-specific representations are used, we could also add an 'abstract' representation that is used for all cases where no language-specific representation is given.

Another use case I'm thinking of is the following. If a teacher specifies test suite for a single programming language, the entry-level is lower as the teacher can use a familiar programming language instead of the abstract programming language of TESTed-DSL.
If later it turns out that the exercise could be used across programming language, TESTed could have an option to automatically translate the language-specific test suite into a language-agnostic test suite. TESTed now only needs a way to transform expressions/statement expressed in its abstract programming language into a language-specific format. Its language modules do not support the reverse transformation. However, if that reverse transformation would be supported as well (for some commonly used languages), this use case could be achieved. During the process, the conversion to the abstract language could then check if all language-specific expressions/statements can be converted, and report where non-supported constructs have been used.

While thinking about implementing this, one potential pitfall with this approach is that it will require more thought to use when calling code from the submission.
Currently, in most languages, the code of the submission is not imported into the main namespace; instead it resides under a "submission" namespace (for example, in Python we do import submission). With the abstract syntax, this is not an issue, since we know what the function calls are, so we prefix them with the namespace of the submission.
However, when using language-specific literals, these are a "black box" to TESTed: we would need to just insert them into the generated code verbatim. In the example above, you would need to write submission.sort_words(). This is annoying, but not a big issue.
The same issue also occurs for return values: since some languages have "void" return types, we cannot wrap the expression with our function to capture the return value. For example, captureValue(someExpression) will not compile in Java if somExpression is a function call with return type void.
In the abstract syntax, we know if an expression is a function call, so we can work around it. However, in with language-specific literals, we won't know this, so this will potentially result in compilation errors. For this case, there is no easy way of fixing this.
So either we need to provide a way to provide this metadata somehow (e.g. it is a function call from the submission), or document these caveats somewhere. I think for now the second option is probably best, as it is less work, and I don't currently see a nice way to do the first.


dq: 20240101 -> 20241027

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/janmojzis/dq/releases.
meta.description for dq is: Recursive DNS/DNSCurve server and comandline tool
meta.homepage for dq is: https://github.com/janmojzis/dq
meta.changelog for dq is: https://github.com/janmojzis/dq/releases/tag/20241027
Updates performed

Version update

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 20241027 in filename of file in /nix/store/zdsllb5ydy1pwq3mwb3zhxpn0vd6phw8-dq-20241027

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

dq

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/zdsllb5ydy1pwq3mwb3zhxpn0vd6phw8-dq-20241027 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A dq https://github.com/r-ryantm/nixpkgs/archive/09db8040605c11ad67b80429e5efac8f21b6b3f2.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/09db8040605c11ad67b80429e5efac8f21b6b3f2#dq

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/zdsllb5ydy1pwq3mwb3zhxpn0vd6phw8-dq-20241027
ls -la /nix/store/zdsllb5ydy1pwq3mwb3zhxpn0vd6phw8-dq-20241027/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review

x86_64-linux

:white_check_mark: 1 package built:

dq

Maintainer pings
cc @sikmir for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

Add a :+1: reaction to pull requests you find important.

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 351792

x86_64-darwin

:white_check_mark: 1 package built:

dq


Enum type

I wonder if it is possible to create enum types with Kysely? I have not found anything in docs

Well, you can create anything with raw SQL using the sql template tag. You can run raw sql in migrations. On the typescript side enums work just fine. Just create an enum and use if for a field.
No enum support has been added to the schema builder because all database engines have different implementation for enums. Also people mean different things when they talk about enums. On postgres there's a way to create new enum types and use those as columns. AFAIK no other engine has something like that. Even knex simply creates a check constraint for enums by default, even on postgres.
Kysely doesn't have an abstraction layer on top of SQL. Therefore there's never going to be a .addColumn('foo', 'text', col => col.enum(['a', 'b', 'c']) kind of methods.
There are already methods for creating check constraints, but you still need to write the check code using raw sql.
What kind of support would you like see in kysely? And what do YOU mean by enum types?

@roitman-g Any thoughts?

Did you go mute?

For postgres you can do:
await db.schema     .createType("status")     .asEnum(["failed", "success"])     .execute();
and then reference the status type:
.addColumn("status", "status")

When I do this, it throws a ts error saying that is not assignable to DataTypeExpression

@vladstavarache fixed your example with sql template tag usage in .addColumn.
@bhgames check the example again.

the example above worked for me! I'm using postgres
thanks @vladstavarache

@vladstavarache fixed your example with sql template tag usage in .addColumn.
@bhgames check the example again.

@igalklebanov ,  For me the following solution worked, when I want to use different name(UserStatus) for type.
await db.schema
    .createType("UserStatus")
    .asEnum(["failed", "success"])
    .execute();

and then reference the UserStatus type:
.addColumn("status", sql`"UserStatus"`)

@anoopsimelabs @vladshcherbin  how would you do migrations if you need to change the type? It doesn't seem like db.schema has any way to change the type. Is it better to just do raw SQL for this?


Create a proper timing class for tracking deltas

The current uses are messy, unreadable, and not quite accurate. They get the job done but should be revisited and share code.

These can be found under // TODO: Very quick and dirty stable timing in ECSContext and WindowContext.


Support sidecar manifests (Was: Question about "manif_file")

Hello,
I can't find any reference to the "manif_file" string anywhere in the Cryptomatte sources; it is present only in the specification .rtf file. Is this option supported, or deprecated? Originally I intended to implement it, but I removed the implementation after I realized it's not really used anywhere.
Best regards,
Vlado

We added this to the standard with the intention of supporting it, but haven't gotten around to putting it into our Arnold implementation. Now that we have other renderer implementations we'll prioritize getting this working in our Nuke Implementation as soon as possible.

Ok, thanks. I will hold the output implementation in V-Ray until it is supported and I can test it.
Best regards,
Vlado

I pushed up a dev branch, called sidecar_manifest, with basic sidecar manifest support, and example image with a sidecar manifest. It also has minor corrections to the specification regarding this - should have a sidecar path like "../manifest.json" and not "./manifest.json"  as was stated in there previously.

@cedricduriau I think it'd be a good idea to enable this in the fusion plugin too. In Nuke it was pretty easy as the metadata contained the file path, and after that it's simple to get the relative file path.

Hi Jonah
So if I get this right, there is a var being populated by the shader in the EXR metadata holding a cached manifest? If so, this could mean some serious improvements and how does this react on multi frame based manifests? More id sublevels?
Cheers
Cedric

That's right, yeah. Instead of writing the manifest to the EXR header, the renderer implementation can instead write the manifest to a sidecar file, which is a json file. Potentially this could be a single file for a whole sequence, which is an improvement. It could even be a single file for a whole project, the decoder doesn't really care, it's just a path to a file.
The path to it can be absolute ("c:/path/to/manifest.json") or relative to the EXR file ("../manifest.1001.json"). I think relative paths will be far more useful.
With regex-based cryptomattes, you need to either freeze the selection or consult the manifest on each frame, so having a single shared manifest for an image sequence would be good to avoid constantly rebuilding it. However I wouldn't count on having renderers spitting out shared manifests like this soon, since having a combined manifest for a whole image sequence could potentially go beyond renderer implementation and involve render farm software as well.

Alright, thanks for the info. I know already that Lua has no direct relative path resolving so I'll have to do the resolving myself. Shared manifests would be amazing, but I see your point.
I'll keep you posted.
Cheers
Cedric

We've proposed a change to the sidecar manifests schema to simply and narrow it down to (what we consider to be) the only useful case, and update spec and the implementation in the sidecar_manifests branch. I hope this doesn't cause any issues. I've updated the implementation, the spec, and the examples.

The change is in, sidecar manifests will now be supported by the Nuke plugin (and hopefully soon for the Fusion plugin, but we can create a separate issue for that), and the specification has been updated to reflect the changes. .

Hi Erwan,
No, we didn't get to implementing it. I tried to find out if we should
write one sidecar per EXR, or somehow combine the data from several/all
frames but I didn't get any feedback.
Even if we did this, wouldn't the speed be exactly the same, no matter if
Nuke itself was reading the metadata or the Cryptomatte plugin?
Best regards,
Vlado
On Tue, Apr 16, 2024, 17:30 Erwan Leroy @.***> wrote:

@vkoylazov https://github.com/vkoylazov did you ever get to
implementing sidecar manifests in Vray? Cryptomatte metadata in EXRs is
killing our read performance on the EXRs with some very complex scenes, but
can't find an option to sidecar the manifest in Vray Maya.
—
Reply to this email directly, view it on GitHub
https://github.com/Psyop/Cryptomatte/issues/14#issuecomment-2060115095,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAMAWWU4Y4JCSXEMD4YOYK3Y5W7CRAVCNFSM4DNUPA7KU5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TEMBWGAYTCNJQHE2Q
.
You are receiving this because you were mentioned.Message ID:
@.***>

Hi Vlado thanks for the quick reply.
I need to contact Foundry as well, it seems like Nuke constantly accesses
either the metadata or the EXR headers and in our case the cryptomatte data
is magnitudes larger than all the other metadata combined. Somehow it
accesses these even when not using the data at all, whereas with the
sidecars it only accesses these when needed.
In the past (it's been a few years at another company) Renderman was only
able to output one sidecar per frame, and as part of an abandoned tweak I
was working on (#79) I had written a tool to iterate through all the
manifests and combine them into a single one, so if VRay offered that
option that would be amazing, though I suppose there are some choices to be
made (do you put the whole scene in the manifest? Only the visible objects?
If only the visible ones, what about those that go in and out of frame but
you're not rendering all the frames at once?).
I personally quite like the idea of having the whole scene in the manifest
as it can help with Sequence level work as well, to easily make a template
that will select the same objects in every shot no matter what is visible,
but that could increase the size of the manifest.
On Tue, Apr 16, 2024, 20:11 vkoylazov @.***> wrote:

Hi Erwan,
No, we didn't get to implementing it. I tried to find out if we should
write one sidecar per EXR, or somehow combine the data from several/all
frames but I didn't get any feedback.
Even if we did this, wouldn't the speed be exactly the same, no matter if
Nuke itself was reading the metadata or the Cryptomatte plugin?
Best regards,
Vlado
On Tue, Apr 16, 2024, 17:30 Erwan Leroy @.***> wrote:

@vkoylazov https://github.com/vkoylazov did you ever get to
implementing sidecar manifests in Vray? Cryptomatte metadata in EXRs is
killing our read performance on the EXRs with some very complex scenes,
but
can't find an option to sidecar the manifest in Vray Maya.
—
Reply to this email directly, view it on GitHub
https://github.com/Psyop/Cryptomatte/issues/14#issuecomment-2060115095,

or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/AAMAWWU4Y4JCSXEMD4YOYK3Y5W7CRAVCNFSM4DNUPA7KU5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TEMBWGAYTCNJQHE2Q>

.
You are receiving this because you were mentioned.Message ID:
@.***>

—
Reply to this email directly, view it on GitHub
https://github.com/Psyop/Cryptomatte/issues/14#issuecomment-2060266726,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAJAV5BK6VD2F7VJQCUPXG3Y5XR67AVCNFSM4DNUPA7KU5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TEMBWGAZDMNRXGI3A
.
You are receiving this because you commented.Message ID:
@.***>

I have done more tests today, including extracting the metadata to a sidecar using OIIO, and the performance difference is night and day. I've sent a recording to Foundry to show them the issue, it's something with Nuke itself. They already have a bug in their tracker: https://support.foundry.com/hc/en-us/articles/210142389-ID-228821-Reading-in-EXRs-with-a-lot-of-metadata-causes-very-slow-performance-when-changing-frames-in-Nuke
Seeing as this bug has been filed years ago, I have little hope that it will be solved anytime soon. @vkoylazov do you think sidecars is something that you guys could look into? Thanks a lot.

Yes, for sure we can look into it; it's not that complicated to implement
it per file. Do you have recommendation on how the sidecar file should be
named? The same name as the .exr but with .json extension?
Best regards,
Vlado
On Wed, Apr 17, 2024, 16:52 Erwan Leroy @.***> wrote:

I have done more tests today, including extracting the metadata to a
sidecar using OIIO, and the performance difference is night and day. I've
sent a recording to Foundry to show them the issue, it's something with
Nuke itself. They already have a bug in their tracker:
https://support.foundry.com/hc/en-us/articles/210142389-ID-228821-Reading-in-EXRs-with-a-lot-of-metadata-causes-very-slow-performance-when-changing-frames-in-Nuke
Seeing as this bug has been filed years ago, I have little hope that it
will be solved anytime soon. @vkoylazov https://github.com/vkoylazov do
you think sidecars is something that you guys could look into? Thanks a lot.
—
Reply to this email directly, view it on GitHub
https://github.com/Psyop/Cryptomatte/issues/14#issuecomment-2062722664,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAMAWWVNA4PA4PEEW4C2QELY54DMRAVCNFSM4DNUPA7KU5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TEMBWGI3TEMRWGY2A
.
You are receiving this because you were mentioned.Message ID:
@.***>

I haven't put too much thought into it, but that sounds like a reasonable default. I imagine some users would want to be able to define their own path/filename.
Thanks!


OverloadedStrings for Ledger.TokenName (onchain)

Describe the feature you'd like
I think it would nice to be able to use OverloadedStrings for Ledger.TokenName in onchain code. I've checked in the source of Ledger.TokenName that fromString doesn't have INLINABLE pragma (maybe the error comes from this).
On the other hand, I see that the mechanism works properly in offchain code.
As an example, the code below fails when template Haskell tries to convert it to Plutus core.
{-# LANGUAGE OverloadedStrings   #-}

{-# INLINABLE mkPolicy #-}
mkPolicy :: TokenName -> () -> ScriptContext -> Bool
mkPolicy tn () _ =
    let expected = "foo" :: TokenName
    in  traceIfFalse "fromString for TokenName doesn't work in onchain code" $ tn == expected

It's something really minor but it would save time for beginners trying to understand why OverloadedStrings for TokenName doesn't work in onchain code.
Many thanks and congratulations on Plutus.
Describe alternatives you've considered
As I mentioned in the feature box, it's something really minor.
I can get the same functionality doing:
{-# LANGUAGE OverloadedStrings   #-}

{-# INLINABLE mkPolicy #-}
mkPolicy :: TokenName -> () -> ScriptContext -> Bool
mkPolicy tn () _ =
    let expected = TokenName "foo"  -- here OverloadedStrings for BuiltinString works properly.
    in  traceIfFalse "fromString for TokenName doesn't work in onchain code" $ tn == expected

Same thing happens for  PubKeyHash.

Thanks for the suggestion!
Unfortunately, due to the technical reasons plutus plugin doesn't support OverloadedStrings with newtypes.
Maybe, to make it less confusing, it's worth to remove IsString instances for the on-chain newtypes.


Multiple Different Styles for Query Parameters

Is it possible to have multiple different styles for query parameters under the same path/operation? This mostly relates to explode. For example, would something like this make sense:
/users?id=3|id=4|id=5&q=1

Hi @dekryptic ,
Are you talking about passing the array values in the query parameter?
Thanks,
Mohammed

As far as I understand that specification seems to only say that a query begins with a '?' and ends where the URI ends or at a '#' while the OAI spec is more specific.
I basically want to know whether in tooling for the OpenAPI specification, should we allow for mixing of delimiters or enforce constraints when exploding parameters? e.g. mixing pipeDelimited and spaceDelimited.
I don't think this is practically possible, so maybe this should be mentioned this in the docs?

@dekryptic I don't believe the original example you presented is actually possible.  The PipeDelimiter and SpaceDelimiter styles only refer to the separator between values, not the delimiter (prefix) between key=value pairs.  Therefore, if you have id with style PipeDelimiter and q with style Form you would get,
/users?id=3|4|5&q=1
The Pipe and Space just replace the comma that would be used with style=form.

What about what's mentioned in the Swagger Docs? i.e.

pipeDelimited
true
n/a
n/a
/users?id=3|id=4|id=5
n/a

Can you provide an example of mixing explode = true with different styles?

I hadn't seen those docs. In my opinion those examples are wrong.  One of the goals of the changes that were made with OAS 3.0 was to try and make the parameter serialization align as closely as possible with RFC6570 without breaking backward compatibility.  The Style concept encapsulates two different things from 6570, the separator and the prefix.  Characters like the dot, semi-colon and slash are prefixes and commas are separators in 6570.  The explode operator (which is concept taken directly from 6570) causes the prefix and key= to be repeated for each value.  It isn't related to the separator.  So, when you mix styles with different prefixes, the serialization is fairly straightforward.
Consider the template:
{/segments*}{;coords*}{?params*}
where
segments = ["foo","bar"]
coords = {"x": 2 ,"y": 3]
params = {"sort": "up", "view": "minimal" }
you would get:
/foo/bar;x=2;y=3?sort=up&view=minimal
Now only a subset of 6570 is support currently in OAS, so you can't actual represent the above template yet.  However, the serialization rules should attempt to follow 6570 where possible.
For Pipe and Space delimiting, it should play the same role a comma plays in 6570. i.e. it should separate values when they are not exploded. I see no value in introducing more capability that is incompatible with 6570.  Ideally, I would like tooling folks to be able to use existing off the shelf 6570 libraries.  I see no reason for us to have to reinvent URL construction code.

Thank you for the detailed explanation.
Is the example for {"in": "path", "style": "label", "explode": false, "schema": {"type": "array"}} incorrect?
Instead of .blue.black.brown, I'm getting .blue,black,brown using two different URI Template libraries. Here is an example.

@dekryptic Now that is a mistake in the spec example.  You only get .blue.black.brown with explode = true.  I will create a PR to fix the spec.
I find this dictionary useful for remembering the behavior of the different operators.

Should the spaceDelimited example be color=blue%20black%20brown and the pipeDelimited example color=blue|black|brown, similar to form?

Also, under the "Style Values" table, should the types for simple be primitive, array, object and the types for spaceDelimited and pipeDelimited be array, object? You have examples for these styles and types in the next section.

How do you expect tooling to implement deserialization for explode? Do we enforce a constraint that only one exploded query parameter can exist to avoid any conflicts?

@dekryptic

Yes.  Instead of color=blue,black,brown the comma separator is a space or pipe.
For simple, primitive is the same as an array of one.  For object the behavior is undefined.  I think the behaviour should be the same for pipeDelimited and spaceDelmited.

Can you explain what you mean by the behavior for object is undefined with the simple style? I'm confused by the examples:

style
explode
...
object

simple
false
...
R,100,G,200,B,150

simple
true
...
R=100,G=200,B=150

I get that in most cases it shouldn't be an issue. But what if I have this code:

var uriTemplates = require("uri-templates")
let template = new uriTemplates("/{?person*,place*}")
template.fill({person: {name: 'John'}, place: {name: 'The Eiffel Tower'}})

that produces this output:
"/?name=John&name=The%20Eiffel%20Tower"

How would this be deserialized?

@dekryptic
2.  I said undefined, but I sort of lied.  OAS doesn't explicitly define what to do with objects that are not exploded, but 6570 does and that is what the example shows. See https://tools.ietf.org/html/rfc6570#section-3.2.2   I'm not really sure we want to specify that behavior because it really isn't very useful.

Welcome to the challenge of 6570.  It works pretty well for serialization.    It wasn't intended to work for deserialization.  We are at the mercy of URL designers to create URLs that don't suck.

As far as I can tell this conversation was resolved - I know the bug in the spec example was fixed in a PR.  I'm going to close this, but if I mentioned something anyone should feel free to comment and I can re-open it (or just feel free to file a new issue with a clear request for a spec change, which may be more likely to get looked at).


remove mysql-oracle dependency jar from release package lib

What's changed?

remove mysql-oracle dependency jar from release package lib
if user want to use it, please download it yourself and put it in the lib directory for use.
mysql-connector-java ojdbc8 orai18n
Checklist

[x]  I hereby agree to the terms of the HertzBeat CLA
[ ]  I have read the Contributing Guide
[ ]  I have written the necessary doc or comment.
[ ]  I have added the necessary unit tests and all cases have passed.

Add or update API

[ ] I have added the necessary e2e tests and all cases have passed.

groupId mysql is obsolete and no longer maintained, it is better to use com.mysql.mysql-connector-j

OK，we can replace it later.


Adding jinja2 extension

Adds support for using the render_bundle function inside Jinja2.

@destos Wonderful. Thanks for the PR. Can we move the section in docs to the bottom of the page inside a section called extras? I would like the main docs to stay to the point for 90% of the people.

@destos Also, can we also reduce the configuration example to the relevant part please? Something like this,
TEMPLATES = [
    {
        "BACKEND": "django_jinja.backend.Jinja2",
        "OPTIONS": {
            "extensions": [
                "webpack_loader.contrib.jinja2ext.WebpackExtension",
            ],
        }
    }
]

and then may be link to django-jinja docs for configuration specific to setting up Jinja2 with django? Also, let mention this is for django1.8 and above.

@owais Made the changes, also fixed an issue I found in the template tag.

@destos Thanks a lot! This is ready. One small change. I've implemented the staticfiles integration elsewhere. Thanks for the pointer. Can you please revert your changes in webpack_loader/templatetags/webpack_loader.py? Thanks!

@owais reverted the change in that file. Did you fix the issue with endswith being misstyped as endwith on the css elif check?

@destos, thanks. I didn't fix the typo yet. I'll do that and then merge. Ive also added basic test cases. I'll add test cases for jinja myself for this one though.

@destos I've merged your PR into master. Here https://github.com/owais/django-webpack-loader/commit/834b56367071ac97f4895f3bdb37df7c03c2ae4c
I like to follow a rebase workflow instead of merge workflow and it seems github PRs don't like that and can't figure out that the branch was merged. I think this happens because commit ids change while rebasing and squashing commits.
I'll write some docs on how to submit squashed commits so PRs can show as merged in future.
Thanks!

@destos Since I don't use jinja ever, I think it'll be very hard for me to maintain it. Would it be possible for you to create a support package called django-webpack-loader-jinja or submit a patch to django-jinja? I see they already carry patches for django-pipeline and other packages.

The reason I'm proposing this is that I'm not sure if I can provide 100% stable jinja support. It is better to let users do it themselves or install an extra package than provide broken built in support.

@owais, I don't see the API on Jinja's side changing that much so I would be opposed to splitting it off. I feel to support alternative template engines it's up to the original package to attempt to add support. But it of course it not required if a maintainer doesn't wish to support more than the default.
At the moment the tests you've implemented for django_jinja should fail if there are any changes on the jinja side.

@destos You are right, test cases should be enough for now. I think we can carry jinja2 support until it gets out of hand.
My concern was that I'm not the best person to maintain Jinja2 support as I don't use it on a daily basis and I had to drop Python3.2 from test matrix because jinja2 doesn't work there which made the whole library drop support for 3.2. 3.2 is not a huge deal but this is an indication of what might happen in future because of jinja dependency. Anyway, thanks a lot for the patch.


Cannot save behavior (Inconsistent paths!)

I just started using WebUI.
I created a project by running the following
ros2 run flexbe_widget create_repo foobar

After colcon build; source install/setup.bash, I launched WebUI by running the following
ros2 launch flexbe_webui flexbe_full.launch.py

Next I loaded the Example Behavior and confirmed  it to work.
However, when I change the arrangement in the Statemachine Editor and click "Save Behavior" in Runtiem Control, I get an error as shown in the image.

It is said that the behavior Python file path and the manifest XML file path are inconsistent, so I checked them and found the paths are as follows.

/home/masutani/test_ws/install/foobar_flexbe_behaviors/local/lib/python3.10/dist-packages/foobar_flexbe_behaviors/example_behavior _sm.py
/home/masutani/test_ws/install/foobar_flexbe_behaviors/lib/foobar_flexbe_behaviors/manifest/example_behavior.xml

There must be a problem with the path checking.

I presume you are using Humble as it uses the "local/lib" path.  Iron and Jazzy don't have that, and I've been testing in Iron lately so missed that when I added the validate_path_consistency method to tools.py in the flexbe_webui folder.
Just have that function return True, or add 'local' to the possible checks.
I think that we may want to change https://github.com/FlexBE/flexbe_webui/blob/beta/flexbe_webui/tools.py#L43
to be
            if ndx > 2 and (python_path_elements[ndx - 1] == 'lib' or manifest_path_elements[ndx - 1] == 'share' or  python_path_elements[ndx] == 'local'):
to work with Humble.
I would appreciate if you'd be willing to make the change and test.
On a related note, the create_repo and copy_behavior scripts are out of date for  Iron and Jazzy as it still includes the local path.
We are still actively developing this flexbe_webui for the next few weeks, so I don't want to create separate branches for Humble, Iron, and Jazzy until we are ready for the "official" release.

Thanks for your reply.
Yes, I am using Humble. I rewrote tools.py as you wrote, and now the error no longer occurs.
Since I will still continue to use Humble for some years, I would be very happy if you support Humble as well.

@MrKeith99 We have stored the manifests in a different folder from the python scripts.
So I believe the use in manifest folders is consistent without change.  It will create a different folder, but does so consistently.
While one fix to the path consistency issue might be to move the manifest packages, I suggest not doing that.


Save img in memory as buffer data

Is there a way to save the image as a buffer in a variable and not in disk?

This would be great!
I've been looking for a node-js library that is able to retrieve the colors of a region of the screen; this one already has the cross-platform screenshotting part down, just needs to have a communication channel between the calling NodeJS code and the C++ code to return the data.


Isolated synchronous deinit

Implementation of the Isolated asynchronous deinit
~Still pending:~

~I suspect that logic for adding attributes for inferred isolation is not correct, would like some input from the Core team about this.~
~Still need to integrate with distributed actors, waiting for https://github.com/apple/swift/pull/60050 to be merged.~
~Didn't copy changes to BackDeployConcurrency yet. I expect that I'll have to make changes based on review comments, and want to apply all changes to BackDeployConcurrency in one go. I would appreciate some advice for maintaining the two in sync.~
~Investigate fast path for self-isolated default actor's deinit~

Didn't copy changes to BackDeployConcurrency yet. I expect that I'll have to make changes based on review comments, and want to apply all changes to BackDeployConcurrency in one go. I would appreciate some advice for maintaining the two in sync.

BackDeployConcurrency is actually supposed to be frozen in time, and not updated with new features. For back-deployment of this feature, we'll have to bring up another statically-linked back-deployment library that would be linked into all problems that build with a deployment target that predates this work. @etcwilde is starting to bring up such a library to back-deploy other concurrency-related fixes. Once that's in place, this PR can build on that work.

BackDeployConcurrency is actually supposed to be frozen in time, and not updated with new features. For back-deployment of this feature, we'll have to bring up another statically-linked back-deployment library that would be linked into all problems that build with a deployment target that predates this work. @etcwilde is starting to bring up such a library to back-deploy other concurrency-related fixes. Once that's in place, this PR can build on that work.

I would really appreciate a document about how to work with BackDeployConcurrency. Could not find anything in the repo.

AFAICS the distributed adjustment looks good 👍
We only resignID as before in the local branch, and the remote does only destroy fields properly, looks good to me.

@swift-ci please test

@swift-ci please test

@swift-ci please test

@swift-ci please test

I asked on the review thread, but maybe it'll get more visibility here. Any chance we can get a toolchain to test?

@swift-ci please build toolchain

@swift-ci please build toolchain

@swift-ci please build toolchain macOS

@swift-ci please build toolchain

@swift-ci please build toolchain macOS

I think that swiftThreading error should be gone now. I saw it late last week in an unrelated pull request, and it's gone now. However, the conflict will prevent us from getting clean builds on this PR.

Rebased and updated implementation:

Removed all code changes related to TL, but updated and preserved unit-tests.
Preserved flags parameter, as an extension point for the future. No strong opinion about this, I don't mind removing it.
Removed changes for async deinit to separate branch (can be recovered later).
Removed changes to python tests (out of scope, see also https://github.com/swiftlang/swift/pull/61510).
Allowed @preconcurrency attribute on deist
Fixed a bug in slow path of the isolated deinit, by removing pair of swift_retain()/swift_release()arounddefaultActorDrain()`.
Always use Legacy_NoCheckIsolated_NonCrashing when checking for current executor, even in Swift 6.

Branch is ready to run CI and resume code review process.

@swift-ci please build toolchain

@swift-ci please test

@swift-ci please build toolchain

@swift-ci please test

@swift-ci please build toolchain

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test


[5.3] $timestamps = false, and create() method adds timestamps to insert query

Does public $timestamps = false; really work? I have a factory defined (well basic user factory that ships with L5.3) and when I set public $timestamps = false; and run factory in question $a = factory(App\User::class)->create() I get back
=> App\User {#776
     email<EMAIL_ADDRESS>     updated_at: "2016-09-02 19:32:10",
     created_at: "2016-09-02 19:32:10",
     id: 3,
   }

Same scenario except when I don't have created_at and updated_at fields in table I get error
Factory
$factory->define(App\Article::class, function (Faker\Generator $faker) {
    return [
        'title' => $faker->title,
        'body' => $faker->text(),
    ];
});

$ art tinker
>>> factory(App\Article::class)->create()

error
Illuminate\Database\QueryException with message 'SQLSTATE[42S22]: Column not found: 1054 Unknown column 'updated_at' in 'field list' (SQL: insert into `articles` (`title`, `body`, `updated_at`, `created_at`) values (Mr., Dolore vel in qui eligendi sunt maxime consectetur. Esse vero porro facilis et. Nobis laudantium aut maiores explicabo soluta est. Vitae velit officia aliquam tempora et tempore minima veritatis., 2016-09-02 19:27:45, 2016-09-02 19:27:45))'

Am I missing something?

I've made some tests on fresh 5.3 ($timestamps = false) and
>>> App\User::create(['name'=>'Joe Doe'<EMAIL_ADDRESS>'password'=>'secret']) also adds timestamps to insert query

art tinker wasted 2 hours... if I do any change I have to restart tinker :(


additional allowed spelling

there are currently 78 spelling errors reported by CI: https://circleci.com/gh/SAPDocuments/Tutorials/444
this should bring the number of reported spelling issues down to 10

Following need to be surrounded by backticks, backtick blocks or in a URL:
8.x
_ABC
_ACCOUNTS
_AMOUNT
_CALCULATE
_CONTROL
_INPUT
_LEGEND
_LEGEND
_OF
_PAL
_RESULT
_SHARE
_TBL
sap-hana-express
www.intel.com
www.vmware.com
Also - SQL is capitalized


Run clean and install in workspace in parallel

LGTM :+1:

Great :p Thx !!!

Are we sure this won't cause weird bugs ?

My bad, @sgaestel just explained me what I did not see, clean and install are ran in // :smile:


Summoned players should be permanently combat-tagged.

Would actually make summoning something viable.

Can you explain further the motivation here? What would this prevent or enable?

Right now, summoning is not a viable tactic when people are pearled because if it is a high profile pearl, they will know just to instantly log out.
With permanent combat tag on summoned players, this restricts their ability to log out since they'll always be hanging around for 30 seconds after.

This relates to the bug where if someone logged out after summing, they could log back in and respawn overworld?
That's a bug ...
Or perhaps I'm misunderstanding. Ideal state is: logging out simply, logs them out. Doesn't free, doesn't cause randomspawn, doesn't change pearl state.

When someone is summoned, they can log out, when they log back in they'll still be overworld however they will be taking damage for being so far away from their pearl (most likely). In that timeframe, they can have friends go to where the summoned player logged off, pearl them and have them freed.
As far as I understand you cannot return a offline player to the end therefore there is no way to currently prevent this.

Ok, that's a bug. Mind opening a new top-level with that as a bug listing?
If they log out and back in, they should return to where they logged out at, or if that location is unavailable or they've been returned, they should respawn in the end.

Oh, actually, this is already an issue: #131
I'll close this and link to it in 131 for reference.


Support redub -{q|v} {build|test|...}

Currently
redub build|test -v

works whereas
redub -v build|test

fails as, for instance,
redub -v test
Parsing ~/Work/gmp-d/dub.sdl at ~/Work/gmp-d with : -c
Added project gmp-d to memory cache.
Dependencies resolved - 6 ms "debug" using /usr/bin/dmd v2.110.0-beta.1 [linux-x86_64] - no parallel
Project gmp-d Dirty Files: ["~/Work/gmp-d/src"]
Built: gmp-d [unittest] - 82ms

	/usr/bin/dmd '-color=on' -op -vcolumns '-checkaction=context' '-preview=dip1000' '-Xcc=-fuse-ld=lld' -debug -g '-version=gmp_test' '-version=Have_gmp_d' -I~/Work/gmp-d/src ~/Work/gmp-d/src/gmp/traits.d ~/Work/gmp-d/src/gmp/z.d ~/Work/gmp-d/src/gmp/f.d ~/Work/gmp-d/src/gmp/package.d ~/Work/gmp-d/src/gmp/q.d -lib '-of=/home/per/.dub/.redub/0617393430CB1BF5/0617393430CB1BF5/libgmp-d.a'

Finished gmp-d - 82ms - To force a rebuild of up-to-date targets, run again with --force
Error Program exited with code 1

.
Both cases are supported by dub.
The same change should happen for
redub -q test
and maybe other flags.

This one works for me, when I fixed that issue, I solved in a generic way
PS C:\Users\Marcelo\Documents\D\redub\package_manager> redub -v build
Parsing C:\Users\Marcelo\Documents\D\redub\package_manager\dub.json at C:\Users\Marcelo\Documents\D\redub\package_manager with : -c
Added project package_manager to memory cache.
Parsing C:\Users\Marcelo\Documents\D\redub\hipjson\dub.json at C:\Users\Marcelo\Documents\D\redub\hipjson with : -c
Parsing C:\Users\Marcelo\Documents\D\redub\semver\dub.json at C:\Users\Marcelo\Documents\D\redub\semver with : -c
Dependencies resolved - 15 ms "debug" using C:\D\dmd2\windows\bin64\dmd.exe v2.110.0-beta.1 [win64-x86_64] - full parallel
Up-to-Date: package_manager; hipjson; semver;
Up-to-Date: package_manager, skipping linking
Finished package_manager - 3ms - To force a rebuild of up-to-date targets, run again with --force

This one works for me, when I fixed that issue, I solved in a generic way
PS C:\Users\Marcelo\Documents\D\redub\package_manager> redub -v build
Parsing C:\Users\Marcelo\Documents\D\redub\package_manager\dub.json at C:\Users\Marcelo\Documents\D\redub\package_manager with : -c
Added project package_manager to memory cache.
Parsing C:\Users\Marcelo\Documents\D\redub\hipjson\dub.json at C:\Users\Marcelo\Documents\D\redub\hipjson with : -c
Parsing C:\Users\Marcelo\Documents\D\redub\semver\dub.json at C:\Users\Marcelo\Documents\D\redub\semver with : -c
Dependencies resolved - 15 ms "debug" using C:\D\dmd2\windows\bin64\dmd.exe v2.110.0-beta.1 [win64-x86_64] - full parallel
Up-to-Date: package_manager; hipjson; semver;
Up-to-Date: package_manager, skipping linking
Finished package_manager - 3ms - To force a rebuild of up-to-date targets, run again with --force

I don't follow.
Are you saying you won't fix this?

I've said that is working:
Parsing ~/Work/gmp-d/dub.sdl at ~/Work/gmp-d with : -c
Added project gmp-d to memory cache.
Project gmp-d Dirty Files: ["~/Work/gmp-d/src"]

Those output are verbose from your code shared here, even the build command is supposed to show only in verbose mode. I don't understand what is the issue you're having

I'm saying that for instance for gmp-d,
redub test -q
3 modules passed unittests

whereas
redub -q test
Error Program exited with code 1

I have detected only a problem in the SDL -> JSON parser, which I'll fix, I'll release it under a new version. Feel free to try it


Rails Sprockets Integration (Vendor assets getting linted)

Hi,
First of all thank you for your work.
I would like to ask what you approach is to avoid having the vendor js's (jquery/jquery-ujs etc) thrown into the eslinter?
My approach was a really hacky way like this:
my manifest application.js
//= require eslint-fix
//= require jquery
/*eslint-enable */
// ... other eslintable requires

the eslint-fix is a file that only has the /eslint-disable/.
why i did this?
because even if i added /eslint-disable/ before the jquery require, due to sprockets overriding this order, jquery would still get rendered in the bundled application first, so i added a new file that forcefully gets rendered first with that tag disabling everything until i re-enable it.
This might not be a common use case for other persons, nevertheless i would like to know what would be a less hacky approach to this.

Hi @miguelm. I just wanted to check in and say that we haven't forgotten about this, and to thank you for sharing your experience. We're thinking about ways to improve this. We'll use your issue to keep track of it. Thanks!

Hi @justinforce no problem.
Keep on the good work

So I just tried out this gem, and I and was bit by this issue as well.  A better way to configure vendor assets around sprockets would be much appreciated...


Some functions require numpy > 1.19.0

Describe the bug
The comparison between two raster, using the overload __eq__ does not work with numpy < 1.19.
To Reproduce
Use numpy < 1.19, then
import geoutils.georaster as gr
from geoutils import datasets
r = gr.Raster(datasets.get_path("landsat_B4"))
r == r

raises the error:

TypeError: _array_equal_dispatcher() got an unexpected keyword argument 'equal_nan'

Expected behavior
This should not raise an error.
To avoid this, either find an alternative to 'equal_nan' or specify the numpy version needed in the requirements.
System (please complete the following information):
numpy version '1.18.1'

Nice that you found out! I'm sure there's a way around it. Worst case, we can just go back to np.nansum(np.abs(r - r2)) < *dtype_min*

Actually, it seems it's just possible to compare with zero:
>>> np.float32(0.11111111111) - np.float32(0.111111111111111111111111111111)
0.0

So it should be as simple as np.nansum(np.abs(r - r2)) == 0.0. I wonder what happens with masks though...


Too Agressive Add {...} to arrow function

Thanks for the bug report!
I'm trying to understand what the bug is here. Add to arrow function should be availalbe, as it seems to be a legit code action, and it does not seem to be suggested.
Are you looking for a better activation range? Or is it about the action showing up as a quick-fix?

That makes total sense. I'm thinking about having 2 levels of activation:

quick fix on the function head and the arrow and the space after, i.e., on () =>  here.
code action (refactoring menu, convert menu) on the function it is now
Would this option work for you?

I've tweaked the activation ranges for 'add/remove {}' in v1.120.2. Thanks for the feedback!


[material-ui][Paper] Need paperChannel along with defaultChannel when using extendTheme()

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Summary 💡
Currently, we are getting default, paper, and defaultChannel variables while using the extendTheme (experimental_extendTheme). It would be great if the paperChannel variable is provided.
Examples 🌈
No response
Motivation 🔦
I have multiple <div>s where I want to add background color same as the paper variable along with some opacities. This is possible only if I get the paperChannel variable.

Note
I have white color for the light colorScheme but I have updated the paper color for the dark colorScheme.

Currently, I have achieved this by manually adding the paperChannel variable into the theme like the following into a types.ts file:
declare module '@mui/material/styles' {
  interface PalettePaperChannel {
    paperChannel: string
  }
  interface TypeBackground extends PalettePaperChannel {}

  // Palette
  interface Palette {
    background: {
      default: string
      paper: string
      defaultChannel: string
      paperChannel: string
    }
  }
  interface PaletteOptions {
    background?: {
      default?: string
      paper?: string
      defaultChannel?: string
      paperChannel?: string
    }
  }
}

It would be great if the paperChannel variable would be provided in the theme.
If it is not possible to provide the paperChannel variable in the theme, please guide me if I have correctly added the variable. If there is any simpler method, please let me know.

Hey @neelbrahmakshatriya, thanks for the report 😊
The way you're adding the paperChannel token to the theme is correct. I'll add the "waiting for upvotes" label so people can vote for this initiative.

@neelbrahmakshatriya In the future (maybe ~1-2 yrs), we will replace *channel tokens with color-mix() to produce translucent color.

Hi @siriwatknp,
Any update on this till color-mix() is implemented in the future?


LspInfo: disable transparency for terminal emulator compatibility

For the non-iTerm apple term user(s) out there

@csmoe

@csmoe

@mjlbach thanks, it's fixed 👍

@mjlbach thanks, it's fixed 👍

This is what I get for trying to make things pretty :cry:

This is what I get for trying to make things pretty :cry:


Fixing functions and adding trademark caption

Checklist
Before creating the Pull-Request, I...

[x] Ran devtools::document() and Install and Restart.
[x] Ran devtools::check() (GHA will do this but doesn't hurt to check yourself).
[ ] (If applicable) Checked changes made to website with pkgdown::build_site().
[x] Wrote commit message(s) throughout the time spent working on this branch with clear details of changes made.
[x] Updated package version with usethis::use_version() (choosing one of "major", "minor", "patch", "dev" options) and wrote down changes made in NEWS.md
[ ] (If applicable) Created new tests for new functions or changes made to existing functions (Check codecov).

After all of the Github Actions Checks have finished, I...

[ ] Checked lintr issues by going to the latest commit or the Checks tab.
[ ] Used Squash & Merge option.
[ ] Wrote in detail of all the changes made in the various commits on this branch.
[ ] Added a keyword like closes #56, fixes #123 at the end of the message.
[ ] Merged the Pull-Request.
[ ] Deleted the branch.

Works on #111 and #110

I checked plot_sonar() and I think it is okay, performs okay and as such, will not be touched in this fix.


Doing backToPreviousPage using Router Outlet inside a TabView cause an error

Make sure to check the existing issues in this repository
This is similar to this issue https://github.com/NativeScript/nativescript-angular/issues/941.
iOS throws this error:  ERROR TypeError: undefined is not an object (evaluating 'states.pop')
Android throws this error: ERROR TypeError: Cannot read property 'pop' of undefined

If there is no issue for your problem, tell us about it
Please, ensure your title is less than 63 characters long and starts with a capital
letter.
Which platform(s) does your issue occur on?
Both Android and iOS.
iOS: 11.4
Android: 8.1.0
Please, provide the following version numbers that your issue occurs with:

CLI: (run tns --version to fetch it)
4.1.2
Cross-platform modules: (check the 'version' attribute in the
~4.1.0
node_modules/tns-core-modules/package.json file in your project)
Runtime(s): (look for the "tns-android" and "tns-ios" properties in the package.json file of your project)
tns-ios: 4.1.1
tns-android: 4.1.3
Plugin(s): (look for the version numbers in the package.json file of your
project and paste your dependencies and devDependencies here)
"@angular/animations": "~6.0.0",
"@angular/common": "~6.0.0",
"@angular/compiler": "~6.0.0",
"@angular/core": "~6.0.0",
"@angular/forms": "~6.0.0",
"@angular/http": "~6.0.0",
"@angular/platform-browser": "~6.0.0",
"@angular/platform-browser-dynamic": "~6.0.0",
"@angular/router": "~6.0.0",
"nativescript-angular": "~6.0.0",
"nativescript-theme-core": "~1.0.4",
"reflect-metadata": "~0.1.8",
"rxjs": "~6.1.0",
"tns-core-modules": "~4.1.0",
"zone.js": "^0.8.26"

Please, tell us how to recreate the issue in as much detail as possible.
Describe the steps to reproduce it.
1.) Go to TabView page.
2.) On Tab 1, click on 'Go to another page'.
3.) Once you're on 'Another Page', click on 'Go Back to Tab View Child'.
4.) You'll see an error and the navigation doesn't work anymore.
Is there any code involved?

provide a code example to recreate the problem
(EVEN BETTER) consider using the playground to provide an application where the problem is reproducible. If this is not possible, provide a .zip with application or refer to a repository with application where the problem is reproducible.

A demo project is here: https://github.com/18clans/blank_master/tree/tab-view-router-outlet

Hi @18clans,
This issue seems to be related to a missing functionality. You can follow the issue here.


Failed to compile from source neither on arm64 or x86

Hi,
I am trying to compile the goofys on Graviton2, as there are no arm64 package available.
However when I follow the steps to build from source, following error messages shown up
github.com/kahing/goofys/api
api/api.go:124:56: cannot use common.FusePanicLogger{...} (type common.FusePanicLogger) as type fuseutil.FileSystem in argument to fuseutil.NewFileSystemServer:
common.FusePanicLogger does not implement fuseutil.FileSystem (missing BatchForget method)
Then I try to use x86 instance, but failed as well, with same error message
I also have tried different go version including 1.17, 1.18, 1.19 but no lucky
Please help to verify this
Thanks,
Vincent

Hi, this PR https://github.com/kahing/goofys/pull/733 should fix the compiling issue.
At least it works on x86, would you be able to try it on arm64 as well?
thanks

It works! Both x86 and arm64.
Thanks a lot

sorry, I forget to change the file api/common/panic_logger.go.
After changed, I compiled successful!
Thanks!


Filtering with .where method: no matches without ActiveRecord

I am really excited about the progress of JSON API spec and the JSON API Resources Gem.
In my experiments with the gem, I found the following to be incompatible with Mongoid, the ActiveRecord replacement for integrating with MongoDB.
def apply_filter(records, filter, value)
  records.where(filter => value)
end

The value passed to this method is always an array. In ActiveRecord, passing an array value to the where method builds an IN SQL query. The challenge with something like Mongoid is that values can be stored as arrays. Thus, Contact.where(:github => ['realityendshere']) seems to search for contact records where the github property is exactly equal to the array ['realityendshere'] and does not return the expected results.
It's easy to override this method in my app's resources:
def self.apply_filter(records, filter, value)
  records.in(filter => value)
end

Hopefully, this helps anyone else trying to understand how jsonapi-resources gem works with ActiveRecord alternatives.

@realityendshere I also tried a document store db, the ORM is NoBrainer http://nobrainer.io/docs/introduction/
RethinkDB which is based on ActiveModel not ActiveRecord - I had an error at https://github.com/cerebris/jsonapi-resources/blob/master/lib/jsonapi/resource.rb#L337
Class#includes is expected (ActiveRecord defines the includes method), but NoBrainer::Document does not (I believe it extends ActiveModel).
http://guides.rubyonrails.org/active_record_querying.html
[326, 335] in /Users/me/.rvm/gems/ruby-2.1.1/gems/jsonapi-resources-0.2.0/lib/jsonapi/resource.rb
   326:             end
   327:           else
   328:             records = apply_filter(records, filter, value)
   329:           end
   330:         end
=> 331:         records.includes(required_includes)
   332:       end

I'm curious if JSON API Resources will only be compatible when using ActiveRecord

Updates on this?


Cleanup per formatting guidelines

General cleanup of free-programming-books.md

Of note: Amongst the dead links removed was the only one under the Silverlight heading. I have left the heading in place, but if desired, it can be removed until there is content to place under it. Please let me know.

Thanks a lot for all this awesome work! The formatting looks good and the dead links cleanup is great.
I'll spend some time over the next few days commenting this PR with alternative links for some resources which happened to move. After this, and if you don't have time to add the new links back into this PR, I'll do it myself and merge it. Thanks again!

All links updated thus far. Updating PR.

Many thanks. One last nitpick (A-Z) and I'll merge this!

@vhf Ready to go.

Great, thank you!


Add ability to group cursor operations

First of all, sorry for the wall of text. I'm trying to cover the argumentation, why this is needed and how this can open for more powerful patterns, so we can have a discussion around it. A lot of times there is a need to group operations on cursors, much like withMutations, but not with passed values but the actual cursors. Like so:
var data = Immutable.fromJS({'a': 1});
var c1 = Cursor.from(data, ['a'], onChange);
var c2 = c1.groupedOperations(cursor => cursor.set(2));

In contrast to
var data = Immutable.fromJS({'a': 1});
var c1 = Cursor.from(data, ['a'], onChange);
var c2 = c1.withMutations(cursor => cursor.set(2)); // Would fail
// This would also fail as c1 points to a scalar
c2 = c1.withMutations(value => 2); // Would fail

// Would instead have to go "one level up" to point to a immutable structure:
c1 = Cursor.from(data, onChange);
c2 = c1.withMutations(value => value.set('a', 2)); // Would work

By having groupedOperations (or with another name?) you could have seperate operations/functions and group/compose them to one, and behave as if it was one with only one triggered onChange.
Problem is, if you have the following:
var square = cursor => cursor.update(input => input * input);
var timesTwo = cursor => cursor.update(input => input * 2);

you could do:
var c2 = square(c1);

and that would work as expected. You could also do:
var c2 = square(timesTwo(c1));

but that would trigger onChange twice, which is in many cases less than optimal. How ever, with groupedOperations, you can pass in composed functions and only trigger one update:
var c2 = c1.groupedOperations(compose(square, timesTwo));

As mentioned, you could do something seemingly similar with withMutations, but as withMutations pass on the cursors underlaying data and not the cursor it self, this would be "semantically different", and our functions would have to be different with composed and non-composed editions (one handling cursors, and one handling the values the cursors are pointing at).
Alternative to groupedOperations name can be bulk or grouped.

Thanks for your exploration and explanation, but I'm still a little bit confused.
Why could you not just slightly change your example to:
var square = input => input * input;
var timesTwo = input => input * 2;

var c2 = c1.update(square);

var c2 = c1.update(square(timesTwo(c1));
var c2 = c1.update(compose(square, timesTwo));

This gives you shorter and more versatile definitions for "square" and "timesTwo" -> it operates on the value of the cursor rather than the cursor itself, then you can use the pre-existing "update" function to group operations.
Is there a more real-world use case that you're trying to use that leads to this being necessary?

I get the confusion, and what you propose is kind of a viable alternative. But the problem with this is that you have to invoke the update function through cursor updates, and that would potentially allow cursor.updates to "leak through your system". I think it's a question of principal/separation here.
Let's say I have a React component:
var Comp = React.createClass({
  render: function () {
     // Partially apply action to get cursor as input (or any other props.
     // Component doesn't care about what type of input it is.
     let onClick = partial(compose(clickAction, logAction), this.props.data);
     return <button onClick={click}>Click me</button>
  }
});

// Some other place/file, a collection of functions that just
// manipulate state cursors point at. Separate from the
// Component, and holds the "whole truth" of state
// manipulation.
function clickAction (cursor) {
  return cursor.update(....)
}

function logAction () { /* ... */ }

Alternativly, my component would have to be implemented as
var Comp = React.createClass({
  render: function () {
     // Component has to care about whether it's a cursor or not
     let onClick = partial(this.props.data.update, compose(clickAction, logAction));
     return <button onClick={click}>Click me</button>
  }
});

// and clickAction

function clickAction (someSortOfInput) {
  return someSortOfOutput;
}
function logAction () { /* ... */ }

Both examples will work, and having more generic/versatile functions as the latter example is smart in many cases, but I'd argue that sometimes you'd want to have the entire truth of your state update in these sort of actions, and have them specific to state-update.
Summarised, I think this
var newCursor = manipulate(oldCursor);

is in many cases (in regards to component "actions") better separated with more clear intent for the manipulate function, rather than
var newCursor = oldCursor.update(manipulate);

Another potential drawback of the second example is multiple inputs. So if a "action" (state update function) requires multiple data as arguments (depends on some sort of data in a immutable tree), you'd have to have the cursors as input anyways, as a mere cursor.update wouldn't do.
With something like groupedOperations you could potentially group operations across cursors as well, by finding the common parent cursor, updating that by manipulating the parent cursor inside the groupedOperations body. If that made any sense.

Hmm, I'm still a bit confused - I don't see where "groupedUpdates" fits into your examples.
Because of the nature of cursor updates, an "onclick" does need to know about cursors, since calling cursor.update and ignoring the result implies the top-level mutation and side-effects that we use cursors for.
To me, the 2nd example you illustrate there looks like a cleaner implementation. The component on-click is explicit about calling the cursor's side-effecting update method while the library functions are more generic since they operate on values rather than operating on cursors.

To give more isolated feedback, if I were doing a code review and came across code that looked like:
function clickAction (cursor) {
  return cursor.update(someSortOfInput => someSortOfOutput)
}
function logAction (cursor) {
  return cursor.update(someSortOfInput => someSortOfOutput)
}

With the intention of being reusable or compostable, then I would recommend isolating the cursor.update calls outside of these functions. It's the inner function within cursor.update which is reusable and composable.

Regardless, I think we may be able to solve this using update without you needing to change how your methods work today.
When calling cursor.update(value => ...), value will be the unwrapped collection. At this point you can call whatever you want on it, including update without triggering a change event on the cursor's root.
let onClick = partial(this.props.data.update, clickAction);
let onLog = partial(this.props.data.update, logAction);
let onClickAndLog = partial(this.props.data.update, compose(clickAction, logAction));

function clickAction (cursor) {
  return cursor.update(someSortOfInput => someSortOfOutput)
}
function logAction (cursor) {
  return cursor.update(someSortOfInput => someSortOfOutput)
}

This will still work as expected, each event handler will only result in one change event, since the values passed to clickAction and logAction are regular immutable collections in all three cases

I realise that it's hard to understand my point, and I'm having a hard time formulating why I think this is a very nice to have, but bear with me. Also, this discussion has kind of derailed to be about "actions" and whether or not they should have cursors or data as input, but I think that's kind of the integral part of if groupedOperations is needed or not. I think, if it's sensible to have actions which takes cursors as input, this feature is needed.

Hmm, I'm sorry but I'm still a bit confused - I don't see where "groupedUpdates" fits into your examples.

Thinking of it, it's not really groupedUpdates or groupedOperations, but it's essentially just an update where you're passed the cursor you want to update instead of the underlying immutable object (or scalar value).

Because of the nature of cursor updates, an "onclick" does need to know about cursors, since calling cursor.update and ignoring the result (all React event handlers) implies the top-level mutation and side-effects that we use cursors for.

It wouldn't ignore the result, but return the resulting cursor(s). Actions should be pure, or at least abstract side-effects to lifted functions (returning accessors to async data/promises/observables or what ever).

To me, the 2nd example you illustrate there looks like a cleaner implementation. The component on-click is explicit about calling the cursor's side-effecting update method while the library functions are more generic since they operate on values rather than operating on cursors.

My examples are fairly contrived and the distinction between the two isn't too clear, but in more real-world examples the actions would probably be larger and probably some use set, remove, push etc, and/or a combination thereof. I think having the ability to pass in the cursors it self (or the immutable objects for that sake) as arguments is more flexible in the sense that you can more dictate the signature of your actions, instead of immutable.js cursors doing it. You can design your internal API with more flexibility and "intent". You could work around that with partial applications and binding of your actions to pass inn additional data, but I'd say that would be semantically weird and the API would be way harder to use/not clean.

With the intention of being reusable or compostable, then I would recommend isolating the cursor.update calls outside of these functions. It's the inner someSortOfInput => someSortOfOutput functions within cursor.update which are reusable and composable

In the current examples, I'd agree with you. But I didn't necessarily intend to make them reusable across immutable structures, native structures and scalar values in a sense. But reusable across components getting passed cursors as props, if that makes sense. What I tried to argue, was that it held a more complete picture what is happening/shows better intent.

Regardless, I think we may be able to solve this using update without you needing to change how your methods work today.

Yeah, you're right, and that's what I've done previously, and recommended others to do. However, this doesn't work if cursors point to scalar values. If I have a cursor that points to an integer, I'd get passed an integer as argument to the update functions. This is part of the "problem". By having a update function that is passed a cursor, you can compose without having to know if the cursor points to a scalar or not.
I get your scepticism and would be vary of feature creep myself, but I think the ability of passing cursors to your actions can allow you to have a better internal API. Therefor a method like this could help to make actions much more composable.

I agree with Mikael! The uniformity of cursors is much preferable to have to deal with either immutables or scalars.

Thanks for sending in this pull request. This has been stalled for a while so I think it is time to just close this pull request. It might be that this feature is useful, but it seems like we would need a more concise case for it to make it core-library-worthy.


Prevent NPE if classifier of dependency is null

If the classifier of a project dependency is not defined it is null (maven 3.3.3).
This fix prevents a NPE during the verification of the mojo.

If the classifier of a project dependency is not defined it is null (maven 3.3.3).

I wonder if the classifier can ever be an empty string as you check?
Similarly, is the trimming really useful?
Otherwise Objects.equals(a.getClassifier(), classifier) would do the job.

I implemented it just to be save.
If you think Objects.equals is enough, i can change it.

I think I'd prefer Objects.equals() though it's not a huge deal.

All replaced.


Tabs not aligned vertically

I'm not sure why, but I get a bottom padding inside bottom bar. Tabs are not centered vertically:

The selected tab is meant to be higher than all the others, this is part of the material design guidelines.

I know... I'm not talking about the selected tab, I'm talking about the bottom padding inside the bottom bar.

I'd love to see this get fixed too..  👼

The tabs are centered properly in the newest versions starting from 2.0.

Not if you remove the text on the tabs, the icons stay near the top and the place of the text is still taken up

You can do this ugly line: bottomBar.findViewById(R.id.bb_bottom_bar_item_container).setPadding(0, 0, 0, -40);
until you find that the icons are now centered


I suddenly started to get this error while Hot reloding my flutter app, and its not everytime im getting it sometimes it just works fine, like every 1 in 3 times it throws this error.

Unhandled exception:
FileSystemException: writeFrom failed, path = '' (OS Error: The pipe is being closed.
, errno = 232)
#0      _RandomAccessFile.writeFromSync (dart:io/file_impl.dart:858:7)
#1      _StdConsumer.addStream. (dart:io/stdio.dart:309:15)
#2      _RootZone.runUnaryGuarded (dart:async/zone.dart:1593:10)
#3      _BufferingStreamSubscription._sendData (dart:async/stream_impl.dart:339:11)
#4      _BufferingStreamSubscription._add (dart:async/stream_impl.dart:271:7)
#5      _SyncStreamControllerDispatch._sendData (dart:async/stream_controller.dart:774:19)
#6      _StreamController._add (dart:async/stream_controller.dart:648:7)
#7      _StreamController.add (dart:async/stream_controller.dart:596:5)
#8      _StreamSinkImpl.add (dart:io/io_sink.dart:136:17)
#9      _IOSinkImpl.write (dart:io/io_sink.dart:269:5)
#10     _IOSinkImpl.writeln (dart:io/io_sink.dart:289:5)
#11     _StdSink.writeln (dart:io/stdio.dart:342:11)
#12     FrontendCompiler.recompileDelta (package:frontend_server/frontend_server.dart:840:19)
#13     listenAndCompile. (package:frontend_server/frontend_server.dart:1284:20)
#14     _RootZone.runUnaryGuarded (dart:async/zone.dart:1593:10)
#15     _BufferingStreamSubscription._sendData (dart:async/stream_impl.dart:339:11)
#16     _BufferingStreamSubscription._add (dart:async/stream_impl.dart:271:7)
#17     _SinkTransformerStreamSubscription._add (dart:async/stream_transformers.dart:63:11)
#18     _EventSinkWrapper.add (dart:async/stream_transformers.dart:13:11)
#19     _StringAdapterSink.add (dart:convert/string_conversion.dart:238:11)
#20     _LineSplitterSink._addLines (dart:convert/line_splitter.dart:153:13)
#21     _LineSplitterSink.addSlice (dart:convert/line_splitter.dart:128:5)
#22     StringConversionSinkMixin.add (dart:convert/string_conversion.dart:163:5)
#23     _SinkTransformerStreamSubscription._handleData (dart:async/stream_transformers.dart:111:24)
#24     _RootZone.runUnaryGuarded (dart:async/zone.dart:1593:10)
#25     _BufferingStreamSubscription._sendData (dart:async/stream_impl.dart:339:11)
#26     _BufferingStreamSubscription._add (dart:async/stream_impl.dart:271:7)
#27     _SinkTransformerStreamSubscription._add (dart:async/stream_transformers.dart:63:11)
#28     _EventSinkWrapper.add (dart:async/stream_transformers.dart:13:11)
#29     _StringAdapterSink.add (dart:convert/string_conversion.dart:238:11)
#30     _StringAdapterSink.addSlice (dart:convert/string_conversion.dart:243:7)
#31     _Utf8ConversionSink.addSlice (dart:convert/string_conversion.dart:317:20)
#32     _Utf8ConversionSink.add (dart:convert/string_conversion.dart:310:5)
#33     _ConverterStreamEventSink.add (dart:convert/chunked_conversion.dart:72:18)
#34     _SinkTransformerStreamSubscription._handleData (dart:async/stream_transformers.dart:111:24)
#35     _RootZone.runUnaryGuarded (dart:async/zone.dart:1593:10)
#36     _BufferingStreamSubscription._sendData (dart:async/stream_impl.dart:339:11)
#37     _BufferingStreamSubscription._add (dart:async/stream_impl.dart:271:7)
#38     _SyncStreamControllerDispatch._sendData (dart:async/stream_controller.dart:774:19)
#39     _StreamController._add (dart:async/stream_controller.dart:648:7)
#40     _StreamController.add (dart:async/stream_controller.dart:596:5)
#41     _Socket._onData (dart:io-patch/socket_patch.dart:2355:41)
#42     _RootZone.runUnaryGuarded (dart:async/zone.dart:1593:10)
#43     _BufferingStreamSubscription._sendData (dart:async/stream_impl.dart:339:11)
#44     _BufferingStreamSubscription._add (dart:async/stream_impl.dart:271:7)
#45     _SyncStreamControllerDispatch._sendData (dart:async/stream_controller.dart:774:19)
#46     _StreamController._add (dart:async/stream_controller.dart:648:7)
#47     _StreamController.add (dart:async/stream_controller.dart:596:5)
#48     new _RawSocket. (dart:io-patch/socket_patch.dart:1877:33)
#49     _NativeSocket.issueReadEvent.issue (dart:io-patch/socket_patch.dart:1334:14)
#50     _microtaskLoop (dart:async/schedule_microtask.dart:40:21)
#51     _startMicrotaskLoop (dart:async/schedule_microtask.dart:49:5)
#52     _runPendingImmediateCallback (dart:isolate-patch/isolate_patch.dart:123:13)
#53     _RawReceivePort._handleMessage (dart:isolate-patch/isolate_patch.dart:193:5)
the Dart compiler exited unexpectedly.
This is very hard to reproduce as its occurrence seems pretty random, Or please can anyone suggest which area to look for..

We would need considerably more information about this to be able to figure what is going wrong. Do you have any other error messages showing up?
/cc @brianquinlan for any ideas on how we could maybe print more informations about this
/cc @aam just fyi

Just found these logs in verbose mode.
[+2167 ms] flutter: WebsocketChannel was unable to establish connection
[   +1 ms] flutter: =========== stream onError: SYNC STREAM ERROR
[   +2 ms] flutter: ========CHANNEL RETRY
[  +86 ms] flutter: CONNECTIVITY BAR REBUILD
[+6314 ms] Service protocol connection closed.
[   +1 ms] Lost connection to device.
[   +1 ms] DevFS: Deleting filesystem on the device (file:///C:/Users/Aditya/AppData/Local/Temp/oomsapp8873134/oomsapp/)
[ +253 ms] Ignored error while cleaning up DevFS: TimeoutException after 0:00:00.250000: Future not completed
[   +4 ms] "flutter run" took 120,953ms.
[ +254 ms] ensureAnalyticsSent: 248ms
[   +2 ms] Running 1 shutdown hook
[  +22 ms] Shutdown hooks complete
[   +1 ms] exiting with code 0
seems like it has something to do with Socket connction. im digging more into it

Just discovered more errors in verbose mode.
...
[   +1 ms] InitializeBuildStatus:
[        ]   Creating "printing_plugin.dir\Debug\printing_plugin.tlog\unsuccessfulbuild" because "AlwaysCreate" was specified.
[        ] CustomBuild:
[        ]   All outputs are up-to-date.
[  +12 ms] ClCompile:
[        ]   All outputs are up-to-date.
[  +15 ms] Link:
[        ]   All outputs are up-to-date.
[        ]   printing_plugin.vcxproj -> C:\src\allprojects\fip\flutterProject\oomsapp\build\windows\plugins\printing\Debug\printing_plugin.dll
[  +10 ms] FinalizeBuildStatus:
[        ]   Deleting file "printing_plugin.dir\Debug\printing_plugin.tlog\unsuccessfulbuild".
[   +1 ms]   Touching "printing_plugin.dir\Debug\printing_plugin.tlog\printing_plugin.lastbuildstate".
[        ] Done Building Project "C:\src\allprojects\fip\flutterProject\oomsapp\build\windows\plugins\printing\printing_plugin.vcxproj"
(default targets).
[  +13 ms] InitializeBuildStatus:
[        ]   Creating "oomsapp.dir\Debug\oomsapp.tlog\unsuccessfulbuild" because "AlwaysCreate" was specified.
[   +5 ms] CustomBuild:
[        ]   All outputs are up-to-date.
[  +43 ms] ClCompile:
[        ]   C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.32.31326\bin\HostX64\x64\CL.exe /c
/IC:\src\allprojects\fip\flutterProject\oomsapp\windows
/IC:\src\allprojects\fip\flutterProject\oomsapp\windows\flutter\ephemeral
/IC:\src\allprojects\fip\flutterProject\oomsapp\windows\flutter\ephemeral\cpp_client_wrapper\include
/IC:\src\allprojects\fip\flutterProject\oomsapp\windows\flutter\ephemeral.plugin_symlinks\connectivity_plus\windows\include
/IC:\src\allprojects\fip\flutterProject\oomsapp\windows\flutter\ephemeral.plugin_symlinks\flutter_secure_storage_windows\windows\include
/IC:\src\allprojects\fip\flutterProject\oomsapp\windows\flutter\ephemeral.plugin_symlinks\printing\windows\include /Zi /nologo /W4 /WX
/diagnostics:column /Od /Ob0 /D _UNICODE /D UNICODE /D WIN32 /D _WINDOWS /D _HAS_EXCEPTIONS=0 /D _DEBUG /D "FLUTTER_VERSION="1.0.0+1"" /D FLUTTER_VERSION_MAJOR=1 /D
FLUTTER_VERSION_MINOR=0 /D FLUTTER_VERSION_PATCH=0 /D FLUTTER_VERSION_BUILD=1 /D NOMINMAX /D UNICODE /D _UNICODE /D "CMAKE_INTDIR="Debug"" /Gm- /EHsc /RTC1 /MDd /GS
/fp:precise /Zc:wchar_t /Zc:forScope /Zc:inline /GR /std:c++17 /Fo"oomsapp.dir\Debug\" /Fd"oomsapp.dir\Debug\vc143.pdb" /external:W4 /Gd /TP /wd4100 /errorReport:queue
C:\src\allprojects\fip\flutterProject\oomsapp\windows\flutter\generated_plugin_registrant.cc
C:\src\allprojects\fip\flutterProject\oomsapp\windows\runner\flutter_window.cpp
[ +455 ms]   generated_plugin_registrant.cc
[ +440 ms]   flutter_window.cpp
[ +797 ms]   Generating Code...
[ +164 ms] ResourceCompile:
[   +1 ms]   All outputs are up-to-date.
[  +21 ms] Link:
[   +1 ms]   C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.32.31326\bin\HostX64\x64\link.exe /ERRORREPORT:QUEUE
/OUT:"C:\src\allprojects\fip\flutterProject\oomsapp\build\windows\runner\Debug\oomsapp.exe" /INCREMENTAL /ILK:"oomsapp.dir\Debug\oomsapp.ilk"
/NOLOGO ..\flutter\Debug\flutter_wrapper_app.lib ..\plugins\connectivity_plus\Debug\connectivity_plus_plugin.lib
..\plugins\flutter_secure_storage_windows\Debug\flutter_secure_storage_windows_plugin.lib ..\plugins\printing\Debug\printing_plugin.lib
C:\src\allprojects\fip\flutterProject\oomsapp\windows\flutter\ephemeral\flutter_windows.dll.lib kernel32.lib user32.lib gdi32.lib winspool.lib
shell32.lib ole32.lib oleaut32.lib uuid.lib comdlg32.lib advapi32.lib /MANIFEST /MANIFESTUAC:"level='asInvoker' uiAccess='false'" /manifest:embed
/manifestinput:C:\src\allprojects\fip\flutterProject\oomsapp\windows\runner\runner.exe.manifest /DEBUG
/PDB:"C:/src/allprojects/fip/flutterProject/oomsapp/build/windows/runner/Debug/oomsapp.pdb" /SUBSYSTEM:WINDOWS /TLBID:1 /DYNAMICBASE /NXCOMPAT
/IMPLIB:"C:/src/allprojects/fip/flutterProject/oomsapp/build/windows/runner/Debug/oomsapp.lib" /MACHINE:X64  /machine:x64
oomsapp.dir\Debug\Runner.res
[   +2 ms]   oomsapp.dir\Debug\flutter_window.obj
[        ]   oomsapp.dir\Debug\main.obj
[        ]   oomsapp.dir\Debug\utils.obj
[   +1 ms]   oomsapp.dir\Debug\win32_window.obj
[        ]   oomsapp.dir\Debug\generated_plugin_registrant.obj
[ +435 ms] LINK : fatal error LNK1168: cannot open C:\src\allprojects\fip\flutterProject\oomsapp\build\windows\runner\Debug\oomsapp.exe for
writing [C:\src\allprojects\fip\flutterProject\oomsapp\build\windows\runner\oomsapp.vcxproj]
[  +14 ms] Done Building Project "C:\src\allprojects\fip\flutterProject\oomsapp\build\windows\runner\oomsapp.vcxproj" (default targets) --
FAILED.
[   +2 ms] Done Building Project "C:\src\allprojects\fip\flutterProject\oomsapp\build\windows\ALL_BUILD.vcxproj" (default targets) -- FAILED.
[        ] Done Building Project "C:\src\allprojects\fip\flutterProject\oomsapp\build\windows\INSTALL.vcxproj" (default targets) -- FAILED.
[   +2 ms] Build FAILED.
[   +8 ms] "C:\src\allprojects\fip\flutterProject\oomsapp\build\windows\INSTALL.vcxproj" (default target) (1) ->
[        ] "C:\src\allprojects\fip\flutterProject\oomsapp\build\windows\ALL_BUILD.vcxproj" (default target) (3) ->
[        ] "C:\src\allprojects\fip\flutterProject\oomsapp\build\windows\runner\oomsapp.vcxproj" (default target) (9) ->
[        ] (Link target) ->
[        ]   LINK : fatal error LNK1168: cannot open C:\src\allprojects\fip\flutterProject\oomsapp\build\windows\runner\Debug\oomsapp.exe for
writing [C:\src\allprojects\fip\flutterProject\oomsapp\build\windows\runner\oomsapp.vcxproj]
[   +1 ms]     0 Warning(s)
[        ]     1 Error(s)
[        ] Time Elapsed 00:00:20.94
[  +47 ms] Building Windows application... (completed in 26.6s)
[   +2 ms] Exception: Build process failed.
[   +2 ms] "flutter run" took 29,482ms.
[   +7 ms]
#0      throwToolExit (package:flutter_tools/src/base/common.dart:10:3)
#1      RunCommand.runCommand (package:flutter_tools/src/commands/run.dart:722:9)

#2      FlutterCommand.run. (package:flutter_tools/src/runner/flutter_command.dart:1257:27)

#3      AppContext.run. (package:flutter_tools/src/base/context.dart:150:19)

#4      CommandRunner.runCommand (package:args/command_runner.dart:209:13)

#5      FlutterCommandRunner.runCommand. (package:flutter_tools/src/runner/flutter_command_runner.dart:283:9)

#6      AppContext.run. (package:flutter_tools/src/base/context.dart:150:19)

#7      FlutterCommandRunner.runCommand (package:flutter_tools/src/runner/flutter_command_runner.dart:229:5)

#8      run.. (package:flutter_tools/runner.dart:64:9)

#9      AppContext.run. (package:flutter_tools/src/base/context.dart:150:19)

#10     main (package:flutter_tools/executable.dart:91:3)

[ +252 ms] ensureAnalyticsSent: 248ms
[        ] Running 1 shutdown hook
[   +4 ms] Shutdown hooks complete
[        ] exiting with code 1

Seems like you are running into a build error here[ ] (Link target) ->
[ ] LINK : fatal error LNK1168: cannot open C:\src\allprojects\fip\flutterProject\oomsapp\build\windows\runner\Debug\oomsapp.exe for
writing [C:\src\allprojects\fip\flutterProject\oomsapp\build\windows\runner\oomsapp.vcxproj]
[ +1 ms] 0 Warning(s)
[ ] 1 Error(s)

hot reload does not rebuild the app but looks like you are rebuilding the app while it is running ?
Not sure if this is a Dart issue.