Update the Updates and Versioning of SDK article

https://help.apify.com/en/articles/3184510-updates-and-versioning-of-apify-sdk
From Zuzka:
Not sure how often we update these but I just ran across an article where we state that Apify 1.0 is not released yet -

Article updated: https://app.intercom.com/a/apps/kod1r788/articles/articles/3184510/show?language=en


Add username to Discord notifications

Both desktop and mobile Discord notifications for incoming bridged Messenger messages show the bot name, but not the Facebook user who sent the original message. Is it possible for Miscord to display the user name in Discord notifications? Thanks!

I don't think this would be possible due to the way Discord shows embeds in notifications

Checked, works but it would need adding an username to the original message and editing it after sending to remove that username which can be pretty annoying.

Yeah, that would be a pain. Thanks for maintaining this project! It's been useful thus far.


Error occurred while installing dependencies on Windows if npm is actually npm.cmd

Describe the bug
I install npm using a package manager (fnm). fnm creates a script npm.cmd which can be executed on the command-line as npm.
Such .bat or .cmd files can only be executed if a shell is spawned: https://nodejs.org/api/child_process.html#spawning-bat-and-cmd-files-on-windows
To Reproduce
Steps to reproduce the behavior:

Clone the template repository.
Use fnm to install npm (or any other package manager on Windows which uses npm.cmd as the shim).
Use npx quartz update and notice that it fails with An error occurred above while installing dependencies.

Expected behavior
It should properly execute npm.
Screenshots and Source
Issue is right here: https://github.com/jackyzha0/quartz/blob/0d1f15d37cf3ceeb6465d7f102fc49bc33933450/quartz/cli/handlers.js#L459-L466
By printing out the actual error on Windows, it ends up being an ENOENT (unable to find the file).
  // - snip -

  console.log("Ensuring dependencies are up to date")
  const res = spawnSync("npm", ["i"], { stdio: "inherit" }) // <-- should specify 'shell: true' on win32.
  if (res.status === 0) {
    console.log(chalk.green("Done!"))
  } else {
    console.log(chalk.red("An error occurred above while installing dependencies."))
  }

  // - snip -

Desktop (please complete the following information):

Quartz Version: v4.4.0
node Version: v20.9.0
npm version: 10.1.0
fnm version: 1.37.2
OS: Windows 11

Additional context
I submitted #1504, which is a potential solution to this. But there are drawbacks. See the PR for more details.
If there's a convenient way of using something similar to which on Unix, Get-Command on PowerShell, or where in cmd then a less invasive solution would be to invoke two shell commands: one to ascertain the full path of npm, then another to spawn a shell if it ends in .bat or .cmd.

I'm confused; it seems like a user setup problem.
otherwise all of our windows users won't be able to use quartz if they can't run npm?
i feel like the only contract that quartz has is to use npm, and users need to make sure that npm is available on most platforms. But then I don't have opinion against your change in the PR.

otherwise all of our windows users won't be able to use quartz if they can't run npm?

I'm able to run quartz, just not quartz update. Actually, I'm specifically able to run quartz update, but it always has an error on the npm i step.

i feel like the only contract that quartz has is to use npm, and users need to make sure that npm is available on most platforms.

I do have npm installed. On Windows, .cmd files are executable in the shell. So npm.cmd is executable just as npm.

Just that everyone shell configuration are different, meaning running in shell in fact are prone to bugs, like this

I don't disagree. Though in this case, the bug arises without running in shell.


Insert control: Press ESC to cancel

Press ESC, to cancel the insertion of the control.
The cursor should be changed back and the mouse hook should be stopped.

A keyboard hook could be the right solution for this.


Add issue form

Codecov Report

Merging #68 (4558c03) into main (4bf7d6d) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##              main       #68   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            4         4
  Lines          167       160    -7
  Branches        26        26
=========================================
- Hits           167       160    -7

Impacted Files
Coverage Δ

src/django_version_checks/checks.py
100.00% <0.00%> (ø)

src/django_version_checks/compat.py
100.00% <0.00%> (ø)

Continue to review full report at Codecov.

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


Added option to add additional filelog operators.

This PR is to gives user the ability to add additional operators for the filelog receiver. With this feature user have the ability to add operator to parse JSON logs, for example. The current pre-canned operators does not include this feature.

@ckt114 please update your description or create an issue detailing the problem this PR solves

@ckt114 please update your description or create an issue detailing the problem this PR solves

Description updated, @TylerHelmuth.

@ckt114 our stance with the presets is that they should not include any complex configuration.  Instead of adding this to the preset I think that configuring filelogreceiver and the extra operators via .Values.config is a better approach.

@TylerHelmuth I agree with you however with Helm one cannot merge arrays. If I define something new below receviers.filelog.operators it'll overwrite all the preset that's included in the chart. That's why I put in this PR. Do you agree?

@ckt114 you are correct.  For your use case you should not use the preset and instead configure the filelogreceiver manually via .Values.Config and add any volumes you need via .Values.extraHostPathMounts.

@ckt114 Sorry for the confusion.
I propose that instead of adding this to the operator I propose that you use the .Values.Config section to configure a filelogreceiver manually, including in that configuration any operators that you need.  These operators might be the same operators that the preset provides and any extras.
In addition to configuring the filelogreceiver, you may need to configure extra host path mounts to facilitate the filelogreceiver working as expected.  Depending on your needs you may not need to.
The presets are not made to be configurable, they exists to quickly show value, but as use cases grow in complexity their value diminishes.  Once the use case has out grown the preset the solution is to configure the collector manually.

@TylerHelmuth I'm already doing what you suggested but I feel that it's not DRY. I'm copying the exact same thing that's in the chart into my config. However, I do see your point. If you feel that this is not necessary then you can deny this PR. Thanks.


Cleanup Verifier.sol and make error handling consistent

Pull request checklist
Please check if your PR fulfills the following requirements:

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

Pull request type

Please check the type of change your PR introduces:

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

What is the current behavior?
Currently when provided with an invalid proof, the verifier will either:

return false,
execute the invalid() opcode,
revert with one of a variety of error messages, like

verifier-gte-snark-scalar-field
pairing-add-failed,
etc..

This makes handling invalid proofs hard. Returning false is especially dangerous because it puts the burden on the caller.
What is the new behavior?
When provided with an invalid proof, the verifier will:

revert with InvalidProof()

In the unlikely event that the caller desires different behaviour, the caller can use a Solidity try/catch statement.
Does this introduce a breaking change?

[x] Yes
[ ] No

The revert error message for an invalid proof changes.
Other information

My next move would be to remove the return value from _isValidProof, but at that point the name should also change. I want to check in and get maintainers opinion first.

@kobigurk  Looks like you are partially right: field elements are verified, but scalars are not considered field elements.

@kobigurk Looks like you are partially right: field elements are verified, but scalars are not considered field elements.

Ah yes, exactly the distinction I was looking for. Super dangerous :)

Ok, so let's be conservative here and reject proofs where the input is not reduced. I'll add a commit.

Ok, so let's be conservative here and reject proofs where the input is not reduced. I'll add a commit.

Thanks! Btw, it's not only conservative, it's a direct attack vector - https://github.com/a16z/zkp-merkle-airdrop-contracts/pull/2

I made all the functions in Pairing  strict on the input. Note that before Pairing.negate(..) would accept an unreduced Y coordinate, so there was malleability in Proof.A.
I don't know if this removes all proof malleability for people other than the prover. (i.e. given a valid proof but not the private inputs, can I compute a different also valid proof)

@cedoor I suspected there was some template involved, despite the usual warning comment missing. Thanks for the link, I will submit a PR there too.
I think we can still merge it here, the only thing that changes with a new ceremony is the contents of the verifyingKey() function, so that should be easy to update. The only other thing that can possibly change (assuming same proof system) is the number of inputs, which is also trivially changed in verifyProof().

I made all the functions in Pairing strict on the input. Note that before Pairing.negate(..) would accept an unreduced Y coordinate, so there was malleability in Proof.A.
I don't know if this removes all proof malleability for people other than the prover. (i.e. given a valid proof but not the private inputs, can I compute a different also valid proof)

It removes "public input" malleability, which is the dangerous part. Proofs can still be modified, because Groth16 is randomizable.


dwm not installing on debian/ubuntu

the following happens when trying to install on debian/ubuntu. Doesn't happen on Arch or fedora. Although I can't get dwm to work on fedora either.

To get fedora server working with dwm, I had to install all these dependencies. sudo dnf groupinstall "Development Tools" "X Window System" &&
sudo dnf install xorg-x11-server-Xorg xinit xterm libev libev-devel imlib2 imlib2-devel
xcb-util-image xcb-util-image-devel xcb-util-renderutil xcb-util-renderutil-devel
xcb-util xcb-util-devel libconfig libconfig-devel libepoxy libepoxy-devel dbus-devel &&
wget https://raw.githubusercontent.com/troydhanson/uthash/master/src/uthash.h &&
sudo mv uthash.h /usr/local/include/

Will be solved with the merge of #282


Additional annotations

What this PR does:
Exposes cass-operator's new AdditionalAnnotations field in the CRD.
Which issue(s) this PR fixes:
Fixes #1094
Checklist

[ ] Changes manually tested
[ ] Automated Tests added/updated
[ ] Documentation added/updated
[ ] CHANGELOG.md updated (not required for documentation PRs)
[ ] CLA Signed:  DataStax CLA

This should be good to go... There is one failing test but I don't think it is related - probably a flake but I'm re-running.

Alex says:

We need to add something like this so that we deploy the right cass-operator with the new fields.
He wants an e2e test for the new field as well.

Looks like we can't progress this as we don't have a cass-operator image right now due to CI failures. I don't know how to fix those so will put this on hold pending a new image being built.

Manually tested one more time, but this looks good to go indeed.


become part of awesome

This list is very similar to https://github.com/sindresorhus/awesome. You should add this repo to the list so it gets more traction!

You're right and I think it's a good idea.
Soon I will solve all the PRs and I will analyze better. Thank you very much for the idea @hipstersmoothie ;)


After updating records from SQL on server - incremental sync becomes always full

Hi! Very weird issue -
After I update lets say 1000 records on server with raw SQL - sync always downloads those 1000 records, no matter query is incremental:(  -
__config table has query id and deltaToken date so for example
"deltaToken|CptCode|CptCode_"	"2017-11-07T02:04:03.7040000+00:00"
and query is
...tables/CptCode?$filter=(updatedAt%20ge%20datetimeoffset'2017-11-07T01%3A59%3A38.1790000%2B00%3A00')&$orderby=updatedAt&$skip=0&$top=20000&__includeDeleted=true
It always downloads those records:( But when I update records with EF or (what's makes it even more strange !!) from table editor in SQL Management Studio - then sync becomes incremental again!!!!
But we create models with EF and code-first approach - so EF creates triggers for UpdatedAt - seems it shouldn't matter where update/insert comes from - anyway it ends up with trigger setting UpdatedAt.
Yet turns out - it somehow matters:((
It's client version 3.1.0, server 2.0.0 - we can't switch to latest due to DataSet legacy support - and we rely on moving data from legacy db to our staging with SQL - so that's why it's crucial to have incremental sync working while merging data to staging with raw SQL not EF (mainly for reuse of legacy SPs and performance)
Thanx in advance!!

Ok -
after mind-blowing debugging session - it's not a bug - it's a feature, at least sort of:)
filter of incremental sync has 'ge' - greater or equal - so if you do with SQL - trigger does it so fast to the point that value of UpdatedAt is equal for all the records!!  So it does what is supposed to - ge - brings all the records. I believe it's a bug though - condition should be 'greater' - so it won't be bringing same records all over again and again. For a big table and big batch - it can be significant overhead! I doubt Azure team was expecting that tables would be modified only with EF that does insert/update record by record.

@vhnatss Thanks for using Azure Mobile Apps. Please read the Readme section on this repo which talks about the future of Azure Mobile Apps. Since this is a feature request in the product, I'll close this issue for now as we are not adding new features, but feel free to ask us questions if you have any. Thanks!


Plugin does not work with Bazel 5

When trying to open a project with Bazel 5.1.0 installed, the plugin fails to generate a working JDT.LS configuration.  The log is attached.
client.log.2022-03-25.txt
I made sure to clean the java language server workspace before trying to open a java source file, and the issue still occurs.  Is this a quick fix or something more involved?

This might be fixed with https://github.com/salesforce/bazel-eclipse/commit/4569d6b617dedecd47473ab64a02116f03dff93f

@plaird FYI. I think we should publish the Language Server and the Bazel Eclipse plug-in always at the same time. Once it's released I can look into building a new version of the VS Code extension.

Just as a quick test I rebuilt the plugin from source and it looks like that took care of the issue, so it does seem like the commit you referenced fixed this.  Since the extension isn't in the VSCode marketplace yet anyway just using the version I built manually is completely fine for our team.

@guw we have this Issue to think about how connected the product releases are. I think they at least need independent version numbers (e.g. if I refactor the Eclipse Import UI in BEF, that is a minor x.X.x BEF release and a patch x.x.X BJLS release).

This works now


Update version of @shelf/gh-sdk package

Need to do it as v2.0.0 because a 14 version of the node might include breaking changes for somebody

Why not straight to 16?


Question: Scaling settings and maintain_initial_size

Quick clarification: All the scaling configurations are relevant when I set maintain_initial_size = true and when max_queue_size > initial_queue_size.  http://cfncluster.readthedocs.io/en/latest/configuration.html#scaling
Is that correct?
If not, if I set maintain_initial_size = true, when would "auto Scaling group to scale down to 0 members, so resources will not sit idle when they aren’t needed." happen?
Thanks
Santi

I'm pretty sure that if maintaining initial size is set to true, and our initial size is 0 then it would scale down to zero.  In fact I've seen that happen.
Keep in mind that if you have zero compute nodes, it will take awhile for one compute node to come online, which may cause the Queuing system or your application to throw an error.

The scaling settings are always observed when scaling
Depends on initial_queue_size, it will scale down to the initial queue size when maintain_initial_size = true. Note initial_queue_size defaults to 2.

@hellmersjl3ds That is correct. I have noticed my application throwing an error when the total number of compute nodes went to zero. Trying to figure out how to handle this case without keeping too many compute nodes up and running the entire time.

yes

I saw an error in my application when I set maintain_initial_size = false and initial_queue_size = 2. Total compute nodes available went to zero.

That's by design https://cfncluster.readthedocs.io/en/latest/autoscaling.html
What I'm more interested in is why this causes an error in your application?


compare CBBR datasests

background
We plan to make our CBBR data product public. During the 'Making CBBR data public' meeting on 7/8, we learned about the dataset published by OMB: Register of Community Board Budget Requests.
As a first step in determining the best way to make the CBBR data public DE will compare three datasets:
A. What Planning support delivers to Data Engineering to create CBBR
B. the final CBBR output created by DE
C. the dataset published by OMB
goals
Write a description of the three datasets, how they're related, and how they're different. CBBR's wiki may be a good place to put a final draft of these details.

cbbr_submissions, the dataset delivered to Data Engineering by Planning Support, has 31 columns, with each row identifying a budget request. This submission contains information on the source, contents, geographies, and status of the request. The sources of the requests include the names of the borough and the board; the contents of the requests include priorities, types, textual descriptions of the request and reasons, supported entities, project ID, and budget line references. The geographies of the requests include street names, addresses, locations (site names), etc. Locations, street names and addresses could take various formats and could overlap. The statuses of the requests include the name and code of the agencies responding to the request, the content and category of the response, and any additional comments.
CDNeeds_CBBRs_ALL_Archive, the output dataset by Data Engineering, has 24 columns, with each row identifying a budget request. It also contains information on the sources, contents, geographies, and statuses of the requests but has a few columns modified or removed compared with cbbr_submissions. For sources, it dropped the boro_and_board column, which is a concatenation of the borough codes and board codes. For the geographies, it kept the location column and dropped other geographic columns such as street_name, cross_street_1, cross_street_2,  facility_or_park_name, and address. For the status columns, agency_name was renamed to agency_acronym, and the agency_reponse_code column was dropped.
Register of Community Board Budget Requests published by the Mayor's Office of Management & Budget (OMB) on NYC Open Data, has 26 columns, with each row identifying a budget request. Compared with cbbr_submissions, the publication added a Publication column, which records the budget publication date. For sources, it dropped the original full borough names and kept the borough codes (renamed to borough); It kept the community board number (renamed to community_board) and dropped the cb_label; it also dropped the type column. For contents, it kept all the columns and renamed some of them. For statuses, it kept the response, response agency full name, and response agency acronym. It dropped the agency code, response code, response category, and category description. For geographies, it dropped facility_or_park_name and location; It includes multiple additional geographic columns, such as Block, Lot, Postcode, Latitude, longitude, Council District, BIN, BBL, Census Tract, and Neighborhood Tabulation Area (NTA).


Namerd's http interfaces should each support both streaming and polling

We should refactor our polling/stamping code so that we can have a principled way of doing streaming and polling on each API endpoint.

are we talking about polling for changes since a particular timestamp, or just polling for the current state of the world?

Similar to how the thrift interface works.  I'd imagine you can poll with a version to get an update when that version is out-of-date, or you can poll without a version to get the current state immediately.

Oh, the use case i had in mind was just simple non-streaming read -- not necessarily stamped polling (which sounds a bit more complex)


[FEAT]: Openrouter.ai intergration

What would you like to see?
Would be nice to have openrouter.ai intergrated. Should be similar to OpenAI or TogetherAI.

Docs: https://openrouter.ai/docs#quick-start


added a harry potter quote & added comma to fix json

#3

@haidarrifki your branch has merge conflicts pls resolve and pr again

@NikhilNamal17 here is my new PR #362 thank you.


Deye Hybrid sensors unavailable in 24.09.22

Hi @davidrapan , after update to 24.09.22 i have some sensors unavailable

Yes, that's not a bug. I refactored entity names which did not fit our (soon to be) standardized scheme. And some static values (like serial number) were transferred into attributes to Device State entity.

Awesome. Thanks

Little OT: hacs does not see updates to your integration. I have to download it manually everytime. Why?

Not sure about that but I somehow noticed that too after HACS 2.0 was release. Maybe it just takes longer before it checks if there is anything to update?
But it does notice the update when you click on the Update information under 3 dots menu.

Not sure about that but I somehow noticed that too after HACS 2.0 was released. Maybe it just takes longer before it checks if there is anything to update?
But it does notice the update when you click on the Update information under 3 dots menu.

when i press on the 3 dots nothing happens. i was stuck on version 24.09.08 after about 10 days i accidentally saw that version 24.09.18 was available. no update notification

And did you click there on Update information?

And did you click there on Update information?

Yes, nothing happened

Weird, it did works that way for me.


myks: 3.4.4 -> 4.1.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/mykso/myks/releases.
meta.description for myks is: A configuration framework for Kubernetes applications
meta.homepage for myks is: https://github.com/mykso/myks
meta.changelog for myks is: https://github.com/mykso/myks/blob/v4.1.1/CHANGELOG.md
Updates performed

Golang update

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 4.1.1 with grep in /nix/store/zraijq7879z4vs96q70947mll8mr8n72-myks-4.1.1
found 4.1.1 in filename of file in /nix/store/zraijq7879z4vs96q70947mll8mr8n72-myks-4.1.1

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

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

myks

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/zraijq7879z4vs96q70947mll8mr8n72-myks-4.1.1 \
  --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 myks https://github.com/r-ryantm/nixpkgs/archive/02c795956bff14a3d41dd78fe09994bd8ff320f8.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/02c795956bff14a3d41dd78fe09994bd8ff320f8#myks

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/zraijq7879z4vs96q70947mll8mr8n72-myks-4.1.1
ls -la /nix/store/zraijq7879z4vs96q70947mll8mr8n72-myks-4.1.1/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.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

1 package built:

myks

Maintainer pings
cc @kbudde for testing.

Result of nixpkgs-review pr 312677 run on x86_64-linux 1

1 package built:

myks


Cognito User Groups Necessary for Unity-Sips-Test deployment

As a necessary prerequisite to getting https://github.com/unity-sds/unity-project-management/issues/71 done, we want to make sure some Cognito user groups are in place to support the Unity-Test and Unity-Sips-Test accounts.
Acceptance Criteria:

[ ] A documented convention for how the user group strings are composed.
[ ] The necessary Cognito User Groups are deployed to Unity-Test.   @ramesh-maddegoda will probably have to consult with the SPS Team, and ADS Teams, at a minimum, to figure out what these groups should be.
[ ] Some basic documentation exists, in Gitbook, describing what the groups are

Cognito User Group Standards
https://github.com/unity-sds/unity-cs/wiki/Cognito-User-Group-Standards


XAML Whitespace Behavior

XamlX's whitespace behavior is far from what Microsoft's XAML does. In particular, it's currently impossible to define a control that behaves like WPF's TextBlock and LineBreak.
This PR aims to get XamlX to the right place. First, I created a test case that fully passes against WPF's XAML parser and ported this to XamlX, with the intent to then make modifications to make it pass with XamlX.
Microsoft's documentation on this topic: https://docs.microsoft.com/en-us/dotnet/desktop/xaml-services/white-space-processing
Fun observation: [TrimSurroundingWhitespace] doesn't actually do anything in my WPF tests. It seems hardcoded to <LineBreak/>.

@kekekeks This is a big bad breaking change, and in some cases it's quite hard to bake this into the current architecture.
Can you take a look at this?
The unit tests were tested against WPF as well. The primary difference is that I did not opt to replicate a WPF bug (since it only exists in their dynamic parser), and that WPF treats "object Prop {get;set;}" different from "string Prop {get;set;}" with regards to handling xml:space="preserve" (both object and string will maintain the whitespace in our case).

@kekekeks I removed the type-system changes (PropertyType junk). Instead, I now inspect the available setters directly in the whitespace normalization transformer

Awesome, will merge once the corresponding PR in Avalonia repo is merged.

Ah cool, we'll swap the submodule ref then. Thanks!

@kekekeks I found a bug in CecilHelpers.Equals that affected IXamlType.IsAssignableFrom
This broke the whitespace normalization in Avalonia because IDictionary<string, T> was suddenly assignable from string (and thus being detected as a scalar string property).
Fixed in f4cad31


main: signal related func better with context

change signature of func interrupt  and reload with context.

However, I don't see any tangible reasons for this change. It doesn't improve anything. And there are controversial opinions on using context for just sake of cancellation.

@kakkoyun
Under the cmd/thanos, other go files use context.WithCancel to perform the cancel semantic(the main file as well). The purpose of the PR is to keep same style of such semantic.
If you doesn't agree, I'm glad to close the PR.

Hey @00arthur00, I have checked the usages of context patterns under thanos/cmd, I could only find one which is used solely for cancellation. https://github.com/thanos-io/thanos/blob/601d4cf57a1e940208714b2c309f990834df958d/cmd/thanos/rule.go#L493-L519
All the others are passed along to the other APIs that requires context.Context.
Maybe we should fix that exceptional case, to be consistent.
So I'm closing this, for now, thank you for your contribution anyway!
Maybe you would want to fix that case 🤗

Hey @00arthur00, I have checked the usages of context patterns under thanos/cmd, I could only find one which is used solely for cancellation.
https://github.com/thanos-io/thanos/blob/601d4cf57a1e940208714b2c309f990834df958d/cmd/thanos/rule.go#L493-L519
All the others are passed along to the other APIs that requires context.Context.
Maybe we should fix that exceptional case, to be consistent.
So I'm closing this, for now, thank you for your contribution anyway!
Maybe you would want to fix that case

@kakkoyun Please see the comment.
The orignal one is close(ch), but bwplotka comment to use context.WithCancel.
Please see:
https://github.com/thanos-io/thanos/pull/1848#discussion_r384960502

Hah, that's true I proposed it. I think I can agree context is nice for
consistency here. But really not a big deal I don't have a strong opinion.
Any other thoughts? (:
On Mon, 30 Mar 2020 at 09:29, Arthur<EMAIL_ADDRESS>wrote:

Hey @00arthur00 https://github.com/00arthur00, I have checked the
usages of context patterns under thanos/cmd, I could only find one which
is used solely for cancellation.
https://github.com/thanos-io/thanos/blob/601d4cf57a1e940208714b2c309f990834df958d/cmd/thanos/rule.go#L493-L519
All the others are passed along to the other APIs that requires
context.Context.
Maybe we should fix that exceptional case, to be consistent.
So I'm closing this, for now, thank you for your contribution anyway!
Maybe you would want to fix that case
@kakkoyun https://github.com/kakkoyun Please see the comment.
The orignal one is close(ch), but bwplotka comment to use
context.WithCancel.
Please see:
#1848 (comment)
https://github.com/thanos-io/thanos/pull/1848#discussion_r384960502
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/thanos-io/thanos/pull/2306#issuecomment-605857786,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABVA3O5EH3RN4IW5P2ISZADRKBJ5VANCNFSM4LSKVIFQ
.

I also don't have strong opinions on it as well. I find channels simpler.
I'm happy to reopen the PR if you all think context is way to go for the project.

I also don't have strong opinions on it as well. I find channels simpler.
I'm happy to reopen the PR if you all think context is way to go for the project.

@kakkoyun
I agree with bwplotka. Though not a big deal. Please help to reopen. I think we'd better keep consistent.

There's no button for me to reopen the PR.

doesnt matter too much one way or the other. I like to use chans if the use-case is simple enough and allows for it, e.g. here. Context is nice for when we have to propagate and build more context that can be cancelled by a parent.

Let's keep it simple then.
Thanks @00arthur00 anyway for this! I think building context for propagation cases, sounds like a good rule.


Fix typo in parse error

Prior to this change, if you followed the error exactly, you would get a weird error message:
> alter retention policy "monitor" on _internal retention
ERR: error parsing query: found RETENTION, expected DURATION, RETENTION, SHARD, DEFAULT at line 1, char 47

LGTM 👍


Fixing authentication cr creation check

Purpose
Part Fix for: https://github.com/wso2/apk/issues/1021

Codecov Report
Patch coverage has no change and project coverage change: +45.87 :tada:

Comparison is base (c4599d1) 33.35% compared to head (93aff28) 79.22%.

:exclamation: Current head 93aff28 differs from pull request most recent head 65df176. Consider uploading reports for the commit 65df176 to get more accurate results

Additional details and impacted files
@@             Coverage Diff             @@
##             main    #1024       +/-   ##
===========================================
+ Coverage   33.35%   79.22%   +45.87%
===========================================
  Files         176       11      -165
  Lines       19643      592    -19051
  Branches     5936      257     -5679
===========================================
- Hits         6551      469     -6082
+ Misses      12972      123    -12849
+ Partials      120        0      -120

Flag
Coverage Δ

adapter
?

devportal-domain-service
?

idp-domain-service
79.22% <ø> (ø)

runtime-domain-service
?

Flags with carried forward coverage won't be shown. Click here to find out more.
see 165 files with indirect coverage changes
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Allows to format the date displayed on datepickers input

This allows to display a custom format after selecting a date on the DatePicker. It defaults for the current solution.
It's a first step in order to be able to localize the DatePicker, while I agree that taking a dependency on something such as Intl or moment maybe too much, we can provide some better options such as allowing to format the Dialog display date.

I like the approach, thanks! May you make Travis pass so we can merge?

Also add the fixes in the comments to auto-close the related issue

Do you mean #320 ? I don't think this fixes it, since what they are asking if for full localization. I can take this up but first I want to take a shot at improving the autocomplete.
Updated the PR and travis is passing.

You're right. Thanks for the PR! :)


A bunch of improvements

Click map title to refresh the map (resolves #60)
Polygons Legend Scale color squares now have the same opacity as the polygons (before it was always 0.7)
Map Title box looks like a proper Leaflet control (same white background + shadow + round corners)
Fixed margins, padding and colors in all controls so that they all look the same
Cleaned CSS a little

thanks @ilyankou


Parse Error from Ignored File

Tell us about your environment

ESLint Version: 4.19.1
Node Version: 8.9.2
npm Version: 6.1.0

What parser (default, Babel-ESLint, etc.) are you using?
babel-eslint
Please show your full configuration:

Configuration

  "eslintIgnore": ["modules/validate.js"],
  "eslintConfig": {
    "parser": "babel-eslint",
    "parserOptions": {
      "ecmaFeatures": {
        "jsx": true
      }
    },
    "plugins": [
      "babel",
      "meteor",
      "react"
    ],
    "extends": [
      "airbnb",
      "plugin:meteor/recommended",
      "plugin:react/recommended"
    ],
    "env": {
      "browser": true
    },
    "globals": {
      "expect": false
    },
    "rules": {
      "import/no-unresolved": 0,
      "import/no-extraneous-dependencies": 0,
      "import/extensions": 0,
      "jsx-a11y/anchor-is-valid": [
        "error",
        {
          "components": [
            "Link"
          ],
          "specialLink": [
            "to"
          ]
        }
      ],
      "max-len": 0,
      "no-alert": 0,
      "no-console": 0,
      "no-restricted-globals": 0,
      "no-return-assign": [
        "error",
        "except-parens"
      ],
      "no-underscore-dangle": [
        "error",
        {
          "allow": [
            "_id",
            "_ensureIndex",
            "_verifyEmailToken",
            "_resetPasswordToken",
            "_name"
          ]
        }
      ],
      "class-methods-use-this": 0,
      "react/jsx-filename-extension": 0,
      "react/forbid-prop-types": 0
    },
    "settings": {
      "import/resolver": "meteor"
    }
  }

What did you do? Please include the actual source code causing the issue, as well as the command that you used to run ESLint.

// validate.js, the root of the issue
import { Meteor } from 'meteor/meteor';

if (Meteor.isClient) {
  import $ from 'jquery';
  import 'jquery-validation';

  export default (form, options) => $(form).validate(options);
}

// any other file importing validate (may be a different path
import validate from '../validate';
// ...

eslint .

What did you expect to happen?
I have the validate.js file in eslintIgnore so it should ignore any errors from the validate.js file.
What actually happened? Please include the actual, raw output from ESLint.
On any file that imports validate.js, I get "parse errors in imported module."
/Users/merlin/code/clever-beagle/pup/ui/components/AdminUserProfile/AdminUserProfile.js
  12:22  error  Parse errors in imported module '../../../modules/validate': Line 4: 'import' and 'export' may only appear at the top level

Copied from eslint #10615

I’m not sure that this is a bug; presumably if you add the file to the import/ignore setting, it would be fine. Adding a file to eslintignore tells eslint not to run rules on it; however, this plugin has to parse imported things so that it can lint the file doing the importing.
Is the only reason you’re ignoring the file because of the nonstandard meteor syntax of non-top-level imports/exports? Does meteor not provide a babel transform or an eslint parser that can cover that file?

That’s in fact the most common - when you don’t want to lint a vendored file, because you didn’t write it, but you still want to ensure you’re importing something from it that exists.


Static dimensions

The static analysis should include deducing dimensions. Currently this will be visible in terms of errors when the dimensions are statically deduced to be incorrect, and symbol tooltips. Eventually there should be tooltips for any hovered token, and codegen, but these can come later.

Given the type constraints, it seems most straightforward to put type checking, dimensions, and rewriting in one single pass. Next steps to get this working:

Figure out dynamic mapping from abstract functions to instantiations
Include dimensions in instantiation signatures

After:

Eliminate redundant dynamic dimension checks
Figure out rewriting, including use of symbols
Redesign the document <=> code model connections

Against all odds this is actually working as intended. The core behaviour is there and it's question of polish (including crash fixes).

I'm inclined to say this is good enough. Before doing a whole ton of work here, it would be nice have parse node tooltips to easily check static results.


Elastalert spike rule not getting any hits

Hello,
I have a scenario to identify if any spike on incoming work items. There is a huge spike around 57000 for works arrived when compared to a max range of 27000 last 3 months.
I tried to use a spike rule with below settings:
`es_host: xxxxxxx
es_port: 9200
name: Event spike
type: spike
index: work-2021-02
threshold_cur: 1
#threshold_ref: 0
timeframe:
hours: 2
spike_height: 2
spike_type: "up"
filter:

query:
query_string:
query: "(METRIC_TYPE:WORK_ARRIVED) AND (not WORK_TYPE:Integration Error) AND (WORK_TYPE : TT-214)"
type:
value: "some_doc_type"
alert:
"email"
email:
xxxxxxxxxxxxxxxx.com `

If i test the rule with same timerange when the spike occurred, i don't get any hits. Kindly let me know if my configurations are fine?
Thanks..

Yelp/elastalert is no longer maintained. Please use jertel elastalert. Questions to the discussion below
https://github.com/jertel/elastalert/discussions


Increment Version

@JuliaRegistrator register()

Registration pull request created: JuliaRegistries/General/44442
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.1.4 -m "<description of version>" 288e6dc984f56400eb165f98e406e5b4bfb8cd0c
git push origin v0.1.4


Asking for The pretrain checkpoint

Hi, I am trying to run your code but cannot get the same result as in your paper. Actually it is far from the performance in your paper. Could you please upload the checkpoint? Thank you so much!

Hi, for the network reason, I failed to upload the checkpoints.
However, you can use other pretrained weights by standrad SGD  (i.e. pretrained without oblique manifold or RSGD).
Here is the checkpoint from TIM.


Create gobuffalo ARM Template

Originally, we thought we would build a command to generate an ARM template to drop into a buffalo project. However, after some experimentation, it seems that the ARM template language builds in enough dynamic-ism to have a single template parameterized to accommodate the options available from within a Buffalo app.
The template should be be able to:

Deploy a Web App for Containers, pointing at an arbitrary image.
Optionally allocate a Postgres database

Progress can be seen here: https://github.com/marstr/azure-quickstart-templates/tree/5b969c16c683fd7e3b2e4e4bd1cb866d44e9ff7b/gobuffalo

The bulk of the template is done. I just need to polish comments/formatting then submit a PR to the quickstart-templates repository.


[FR]: Publish to Bazel Central Registry (bzlmod)

What is the current behavior?
No response
Describe the feature
Make Cypress testing available to bzlmod users with nothing in WORKSPACE

👋  Any update here?

Hey, sorry we haven't had time to get this one to 1.0 yet. Contributions welcome (fiscal or PRs)

Hello,
I saw https://github.com/aspect-build/rules_cypress/pull/69 and https://github.com/aspect-build/rules_cypress/pull/71 have been merged.
does this mean we're close or already there?
what's missing and how can i help ? :)
cc @gregmagolan


[Feature Request] Ordering/Filtering roll results

On the game I run and maintain on our community, we make heavy use of /r repeat (xdy, z, brief) for many things, most importantly attack rolls (one 2d6 per shot or swing).
Because of how accuracy works in our game, features that would save us a lot of time would be ordering or filtering the results.
A normal, non-ordered roll currently looks like this:
User:
/r repeat (2d6, 10, brief)

Sidekick:
@User:  repeat (2d6, 10, brief) = 7, 9, 8, 6, 5, 10, 2, 6, 7, 9

A mock-up of what I'd like ordering to look like:
User:
/r repeat (2d6, 10, brief, ordered)

Sidekick:
@User:  repeat (2d6, 10, brief, ordered) = 2, 5, 6, 6, 7, 7, 8, 9, 9, 10

This would allow me (and players in general) to have a far better idea of how many hits they've made with their particular weapon or attack, especially if there's many shots involved (the rule of one shot = one 2d6 does mean that we throw a LOT of dice over a typical session...)
If possible at all, filtering out certain values would be even better, as it would allow us to leave out what we consider to be misses.
Perhaps this could work by expressing a range, e.g. 3:6, or by using < > <= >= =.
Mock-ups of what I'd like filtering to look like:
User:
/r repeat (2d6, 10, brief, filter 3:6)

Sidekick:
@User:  repeat (2d6, 10, brief, filter 3:6) = 2, 7, 7, 8, 9, 9, 10

User:
/r repeat (2d6, 10, brief, filter <=8)

Sidekick:
@User:  repeat (2d6, 10, brief, filter <=8) = 9, 9, 10

I realize that my suggestions may not be terribly efficient, but they would make our jobs a lot easier.

Yes.  I also want this feature.  I run the Whispering Vault game, who has very unique skill tallying system,  I need to know how many of each die was rolled, as the sum of a single number can be your greatest roll.
The example you provided would be a great addition.
User:
/r repeat (1d6, 10, brief, ordered)

Sidekick:
@User:  repeat (1d6, 10, brief, ordered) = 1, 1, 2, 3, 4, 4, 5, 5, 5, 6

In this example, the roll total ends up being 15 (the highest total of similar dice).  Ordering the dice can achieve this easiest.


[feature request] - Add parent commit IDs to build details under Settings

Is your feature request related to a problem? Please describe.
If people make the slightest changes to their builds, the commit ID will not show where they are in terms of syncing with Trio upstream. If we add parent commit refs to the build details displayed at the top of Settings view, we will probably be able to se recent merges with Trio main/dev/alpha as parent commits.
Describe the solution you'd like
Make minor adjustments to the current code for getting and displaying build details
Describe alternatives you've considered
List and describe any alternative solutions or features you've considered that could also address the problem. Explain why you believe the proposed solution is the best option.
Additional context
Include any other context, screenshots, or relevant information that might help in understanding the issue or the proposed solution. If applicable, describe any previous discussions or decisions that relate to this feature request.
Technical Details
If applicable, provide any technical details or considerations that might impact the implementation of this feature. This could include dependencies, potential risks, or required changes to existing functionalities.
User Impact
(Optional) Describe the impact of this issue on your use of the Trio app. Include any specific examples or data that demonstrate how widespread or severe the problem is.

I think @dnzxy said this could be useful when supporting users that make their own changes. If we improve the build/versioning info that is displayed in Trio in line with what @bjorkert made for Loop Follow, we might want to incorporate the parent commit info there?


C# generator compiler errors on enums when enum is a number

I used NSwag Studio to generate c# code for a swagger where there was an enumeration defined, and the values of the enumeration were numbers.
That causes a problem,  because a number is not a valid identifier in c#.
Here's an example of the generator output:
    public enum ClassCode1
    {
        0562 = 0,
        0532 = 1,
        7391 = 2,
        01139 = 3,
    }

The REST service expects values like "0562", but we can't use that as the name of a value for an enum.
I compared this to the output of https://github.com/swagger-api/swagger-codegen and I noticed that generator prefixes numeric identifiers with an underscore, so it would produce:
    public enum ClassCode1
    {
        _0562 = 0,
        _0532 = 1,
        _7391 = 2,
        _01139 = 3,
    }

Perhaps NSwag should do something similar?

Yes, good find :)

Thanks -- I realized just now that I left something out.  The other generator also generates EnumMember attributes on those enums so that they serialize correctly.  So, the class code looks like this:
(this time a full copy/paste, not free-handing it):
        [JsonConverter(typeof(StringEnumConverter))]
        public enum ClassCodeEnum {

            [EnumMember(Value = "0562")]
            _0562,

            [EnumMember(Value = "0532")]
            _0532
        }

I currently don't use the C# generator. This is why I didn't find all these edge cases yet... Will fix this in the next days...

Btw: Why are you using NSwag over swagger-codegen?

Do you use NSwag generated swagger or external?

Hi rsuter:  Answers to your questions:
I'm just getting started with Swagger, and we are a .net shop, We are consuming some REST services that have Swagger set up for them (not building any right now).  I'm not sure what they used to generate the swagger.
So, my first attempt at generating code was to use the "Generate Client Code" option from the swagger  online editor here: http://editor.swagger.io/#/.  When it didn't compile, I started looking around for alternatives and found NSwag.  I liked that there is was a C# API in addition to the command line and GUI options, so I tried it out.
I generated the NSwag-generated code with the NSwag GUI
Some more searching led me to swagger-codegen, so I pulled down the .jar file, and tried it.  Oddly, while the Web Site produced code that did not compile, the .jar produced code that will.  (the code is a little odd though -- c# is probably not the primary language used by the person who wrote the generator)
In all honesty, my own needs are pretty simple -- I want to generate really "dumb" DTO's.  For my purposes, I would actually rather just have string properties than "real" enums for the DTO's that I am going to use (perhaps with some constants for the known values.
I may just end up hand-coding the DTO's, but I had hoped to generate them because they are rather large.

fixed in v3.9


Support Windows. Help wanted 🙏🪟

At all steps, SeaGOAT is developed with the intention of guaranteeing Windows support. That being said, as I don't have a Windows device and I don't have expertise regarding Windows development workflows, I have not been able to verify that it works properly on Windows.
The main goal is to support WSL, but supporting Windows natively is also a goal if it's possible!
Help wanted!
Here is a rough checklist of the current status of Windows support:

[x]  Enable CI checks for Windows
[ ] Enable tests for WSL if it's possible and necessary with GitHub actions
[ ]  Make sure that all CI tests pass for Windows
[ ]  Manually test SeaGOAT on Windows
[ ]  Document installation steps on Windows
[ ]  Make sure that any required Windows-specific features are implemented
[ ]  Ensure it's easy to install on Windows using common tools
[ ] Currently, the main problem is that I have not been able to try and run SeaGOAT manually on Windows.

Also, I have discovered that some of the tests are failing on Windows. So, I created a CI file specifically for Windows that only checks some of the tests that are passing without issue:
https://github.com/kantord/SeaGOAT/blob/1edae8e4b9272906300046cf99bb5de8fd4256aa/.github/workflows/test-windows.yml#L56-L58
For comparison, the Linux tests look like this:
https://github.com/kantord/SeaGOAT/blob/1edae8e4b9272906300046cf99bb5de8fd4256aa/.github/workflows/test.yml#L56-L58

Reference in n

You are able to query the repo while it's being indexed, and the most useful files are being prioritized for indexing. For this reason the intended use case is to allow you to work normally on your computer while the repo is being indexed, which is why CPU utilization is not being maximized. However maybe it would make sense to allow the user to customize this behavior

Thanks for the tip, seems like a reasonable design choice.
When I try to query, I'm getting an error however. It seems to think that I don't have ripgrep installed though I've ensured that I do.
2023-09-20 10:51:49,040 Handling task: query
Exception in thread Thread-1 (_worker_function):
Traceback (most recent call last):
  File "C:\Python311\Lib\threading.py", line 1038, in _bootstrap_inner
    self.run()
  File "C:\Python311\Lib\threading.py", line 975, in run
    self._target(*self._args, **self._kwargs)
  File "C:\Users\Paul\.local\pipx\venvs\seagoat\Lib\site-packages\seagoat\queue\base_queue.py", line 79, in _worker_function
    self._handle_task(context, task)
  File "C:\Users\Paul\.local\pipx\venvs\seagoat\Lib\site-packages\seagoat\queue\base_queue.py", line 66, in _handle_task
    result = handler(context, *task.args, **kwargs)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\Users\Paul\.local\pipx\venvs\seagoat\Lib\site-packages\seagoat\queue\task_queue.py", line 78, in handle_query
    context["seagoat_engine"].fetch_sync(
  File "C:\Users\Paul\.local\pipx\venvs\seagoat\Lib\site-packages\seagoat\engine.py", line 163, in fetch_sync
    loop.run_until_complete(self.fetch(*args, **kwargs))
  File "C:\Users\Paul\.local\pipx\venvs\seagoat\Lib\site-packages\nest_asyncio.py", line 99, in run_until_complete
    return f.result()
           ^^^^^^^^^^
  File "C:\Python311\Lib\asyncio\futures.py", line 203, in result
    raise self._exception.with_traceback(self._exception_tb)
  File "C:\Python311\Lib\asyncio\tasks.py", line 269, in __step
    result = coro.throw(exc)
             ^^^^^^^^^^^^^^^
  File "C:\Users\Paul\.local\pipx\venvs\seagoat\Lib\site-packages\seagoat\engine.py", line 149, in fetch
    results = await asyncio.gather(*async_tasks)
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\Python311\Lib\asyncio\tasks.py", line 339, in __wakeup
    future.result()
  File "C:\Python311\Lib\concurrent\futures\thread.py", line 58, in run
    result = self.fn(*self.args, **self.kwargs)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\Users\Paul\.local\pipx\venvs\seagoat\Lib\site-packages\seagoat\sources\ripgrep.py", line 45, in fetch
    return _fetch(query_text, str(path), limit)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\Users\Paul\.local\pipx\venvs\seagoat\Lib\site-packages\seagoat\sources\ripgrep.py", line 16, in _fetch
    Ripgrepy(query_text, path)
  File "C:\Users\Paul\.local\pipx\venvs\seagoat\Lib\site-packages\ripgrepy\__init__.py", line 131, in __init__
    raise RipGrepNotFound("ripgrep not found")
ripgrepy.RipGrepNotFound: ripgrep not found

Output from pip list

Is there something I'm doing wrong?

Now that I've resolved the ripgrep issue 😅 , I'm getting another error
Exception in thread Thread-1 (_worker_function):
Traceback (most recent call last):
  File "C:\Python311\Lib\threading.py", line 1038, in _bootstrap_inner
    self.run()
  File "C:\Python311\Lib\threading.py", line 975, in run
    self._target(*self._args, **self._kwargs)
  File "C:\Users\Paul\.local\pipx\venvs\seagoat\Lib\site-packages\seagoat\queue\base_queue.py", line 79, in _worker_function
    self._handle_task(context, task)
  File "C:\Users\Paul\.local\pipx\venvs\seagoat\Lib\site-packages\seagoat\queue\base_queue.py", line 66, in _handle_task
    result = handler(context, *task.args, **kwargs)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\Users\Paul\.local\pipx\venvs\seagoat\Lib\site-packages\seagoat\queue\task_queue.py", line 83, in handle_query
    results = context["seagoat_engine"].get_results(kwargs["limit_clue"])
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\Users\Paul\.local\pipx\venvs\seagoat\Lib\site-packages\seagoat\engine.py", line 208, in get_results
    sorted(
  File "C:\Users\Paul\.local\pipx\venvs\seagoat\Lib\site-packages\seagoat\engine.py", line 212, in <lambda>
    + 0.3 * normalize_file_position(top_files[x.path])
                                    ~~~~~~~~~^^^^^^^^
KeyError: 'views\\include\\murisuiteviews\\qglmeshviewer.h'

Now that I've resolved the ripgrep issue 😅 , I'm getting another error

Out of curiosity, how did you resolve the ripgrep issue? I was thinking that if it wasn't detecting your ripgrep installation originally, it might be a bug in ripgrepy itself: https://github.com/securisec/ripgrepy maybe we could help them fix the problem or at least submit an issue there.
Also if you used a specific workaround we could mention that in the readme of SeaGOAT

@DeveloperPaul123 : it's because the file path in top_files is in linux format.
Temp fix : Replace top_files[x.path] by top_files[Path(x.path).as_posix()] in engine.py (C:\Users\XXXXXX.local\pipx\venvs\seagoat\Lib\site-packages\seagoat\engine.py)

ok, actually we have something similar here: https://github.com/kantord/SeaGOAT/blob/51ae32c845365e64226f49d031769c6b47673bb1/seagoat/utils/server.py#L21-L22
we can probably reuse that

Now that I've resolved the ripgrep issue 😅 , I'm getting another error

Out of curiosity, how did you resolve the ripgrep issue? I was thinking that if it wasn't detecting your ripgrep installation originally, it might be a bug in ripgrepy itself: https://github.com/securisec/ripgrepy maybe we could help them fix the problem or at least submit an issue there.
Also if you used a specific workaround we could mention that in the readme of SeaGOAT

I just installed ripgrep via chocolatey as I didn't have it installed previously. Maybe I missed something, but I didn't realize that ripgrep was another command line tool that I needed to install along with SeaGOAT. I had installed ripgrepy via pip, but didn't have ripgrep available. It seems that ripgrepy assumes you have ripgrep installed and that it is available on your path.

I have merged this, now with the latest version of SeaGOAT, the path-related error should not happen on Windows. If either of you can try it, please confirm if it works or not :pray:  https://github.com/kantord/SeaGOAT/pull/234

@kantord Thanks for the the fixes, things seem to be working correctly now!

@kantord Thanks for the the fixes, things seem to be working correctly now!

amazing! let me know if you encounter other problems. also please let me know about your use cases and whether or not you find that the results are useful for your use cases.

@kantord Thanks for the the fixes, things seem to be working correctly now!

amazing! let me know if you encounter other problems. also please let me know about your use cases and whether or not you find that the results are useful for your use cases.

Will do thanks!
As for my use case, I occasionally use it to find code in my projects. I may use it in the future to help me replace code blocks or explore legacy code bases.

Can't install latest version seagoat on windows with python 3.12 because have dependency conflicts, how to resolve it?
pip3.exe install -U seagoat
Collecting seagoat
  Using cached seagoat-0.36.2-py3-none-any.whl.metadata (9.7 kB)
Collecting appdirs<2.0.0,>=1.4.4 (from seagoat)
  Using cached appdirs-1.4.4-py2.py3-none-any.whl.metadata (9.0 kB)
Collecting blessed<2.0.0,>=1.20.0 (from seagoat)
  Using cached blessed-1.20.0-py2.py3-none-any.whl.metadata (13 kB)
Collecting chardet<6.0.0,>=5.2.0 (from seagoat)
  Using cached chardet-5.2.0-py3-none-any.whl.metadata (3.4 kB)
Collecting chromadb<0.5.0,>=0.4.0 (from seagoat)
  Using cached chromadb-0.4.24-py3-none-any.whl.metadata (7.3 kB)
Requirement already satisfied: click<9.0.0,>=8.1.3 in c:\users\slach\scoop\apps\python\current\lib\site-packages (from seagoat) (8.1.7)
Collecting deepmerge<2.0.0,>=1.1.0 (from seagoat)
  Using cached deepmerge-1.1.1-py3-none-any.whl.metadata (1.9 kB)
Collecting flask<4.0.0,>=3.0.0 (from seagoat)
  Using cached flask-3.1.0-py3-none-any.whl.metadata (2.7 kB)
Requirement already satisfied: gitpython<4.0.0,>=3.1.31 in c:\users\slach\scoop\apps\python\current\lib\site-packages (from seagoat) (3.1.43)
Collecting jsonschema<5.0.0,>=4.19.1 (from seagoat)
  Using cached jsonschema-4.23.0-py3-none-any.whl.metadata (7.9 kB)
Collecting nest-asyncio<2.0.0,>=1.5.6 (from seagoat)
  Using cached nest_asyncio-1.6.0-py3-none-any.whl.metadata (2.8 kB)
Collecting orjson<4.0.0,>=3.9.5 (from seagoat)
  Using cached orjson-3.10.12-cp313-none-win_amd64.whl.metadata (42 kB)
Collecting prompt-toolkit<4.0.0,>=3.0.38 (from seagoat)
  Using cached prompt_toolkit-3.0.48-py3-none-any.whl.metadata (6.4 kB)
Collecting psutil<6.0.0,>=5.9.5 (from seagoat)
  Using cached psutil-5.9.8-cp37-abi3-win_amd64.whl.metadata (22 kB)
Requirement already satisfied: pygments<3.0.0,>=2.15.1 in c:\users\slach\scoop\apps\python\current\lib\site-packages (from seagoat) (2.18.0)
Requirement already satisfied: pyyaml<7.0.0,>=6.0.1 in c:\users\slach\scoop\apps\python\current\lib\site-packages (from seagoat) (6.0.1)
Requirement already satisfied: requests<3.0.0,>=2.31.0 in c:\users\slach\scoop\apps\python\current\lib\site-packages (from seagoat) (2.32.3)
Collecting setuptools<69.0.0,>=68.0.0 (from seagoat)
  Using cached setuptools-68.2.2-py3-none-any.whl.metadata (6.3 kB)
Requirement already satisfied: tqdm<5.0.0,>=4.65.0 in c:\users\slach\scoop\apps\python\current\lib\site-packages (from seagoat) (4.66.4)
Collecting waitress<3.0.0,>=2.1.2 (from seagoat)
  Using cached waitress-2.1.2-py3-none-any.whl.metadata (7.0 kB)
Collecting wcwidth>=0.1.4 (from blessed<2.0.0,>=1.20.0->seagoat)
  Using cached wcwidth-0.2.13-py2.py3-none-any.whl.metadata (14 kB)
Requirement already satisfied: six>=1.9.0 in c:\users\slach\scoop\apps\python\current\lib\site-packages (from blessed<2.0.0,>=1.20.0->seagoat) (1.16.0)
Collecting jinxed>=1.1.0 (from blessed<2.0.0,>=1.20.0->seagoat)
  Using cached jinxed-1.3.0-py2.py3-none-any.whl.metadata (4.7 kB)
Collecting build>=1.0.3 (from chromadb<0.5.0,>=0.4.0->seagoat)
  Using cached build-1.2.2.post1-py3-none-any.whl.metadata (6.5 kB)
Requirement already satisfied: pydantic>=1.9 in c:\users\slach\scoop\apps\python\current\lib\site-packages (from chromadb<0.5.0,>=0.4.0->seagoat) (2.8.2)
Collecting chroma-hnswlib==0.7.3 (from chromadb<0.5.0,>=0.4.0->seagoat)
  Using cached chroma-hnswlib-0.7.3.tar.gz (31 kB)
  Installing build dependencies ... done
  Getting requirements to build wheel ... done
  Preparing metadata (pyproject.toml) ... done
Collecting fastapi>=0.95.2 (from chromadb<0.5.0,>=0.4.0->seagoat)
  Using cached fastapi-0.115.5-py3-none-any.whl.metadata (27 kB)
Collecting uvicorn>=0.18.3 (from uvicorn[standard]>=0.18.3->chromadb<0.5.0,>=0.4.0->seagoat)
  Using cached uvicorn-0.32.1-py3-none-any.whl.metadata (6.6 kB)
Requirement already satisfied: numpy>=1.22.5 in c:\users\slach\scoop\apps\python\current\lib\site-packages (from chromadb<0.5.0,>=0.4.0->seagoat) (2.1.3)
Collecting posthog>=2.4.0 (from chromadb<0.5.0,>=0.4.0->seagoat)
  Using cached posthog-3.7.2-py2.py3-none-any.whl.metadata (2.0 kB)
Requirement already satisfied: typing-extensions>=4.5.0 in c:\users\slach\scoop\apps\python\current\lib\site-packages (from chromadb<0.5.0,>=0.4.0->seagoat) (4.12.2)
INFO: pip is looking at multiple versions of chromadb to determine which version is compatible with other requirements. This could take a while.
Collecting chromadb<0.5.0,>=0.4.0 (from seagoat)
  Using cached chromadb-0.4.23-py3-none-any.whl.metadata (7.3 kB)
  Using cached chromadb-0.4.22-py3-none-any.whl.metadata (7.3 kB)
  Using cached chromadb-0.4.21-py3-none-any.whl.metadata (7.3 kB)
  Using cached chromadb-0.4.20-py3-none-any.whl.metadata (7.3 kB)
  Using cached chromadb-0.4.19-py3-none-any.whl.metadata (7.3 kB)
  Using cached chromadb-0.4.18-py3-none-any.whl.metadata (7.4 kB)
  Using cached chromadb-0.4.17-py3-none-any.whl.metadata (7.3 kB)
INFO: pip is still looking at multiple versions of chromadb to determine which version is compatible with other requirements. This could take a while.
  Using cached chromadb-0.4.16-py3-none-any.whl.metadata (7.3 kB)
  Using cached chromadb-0.4.15-py3-none-any.whl.metadata (7.2 kB)
  Using cached chromadb-0.4.14-py3-none-any.whl.metadata (7.0 kB)
  Using cached chromadb-0.4.13-py3-none-any.whl.metadata (7.0 kB)
  Using cached chromadb-0.4.12-py3-none-any.whl.metadata (7.0 kB)
Collecting pydantic<2.0,>=1.9 (from chromadb<0.5.0,>=0.4.0->seagoat)
  Using cached pydantic-1.10.19-py3-none-any.whl.metadata (152 kB)
Collecting fastapi<0.100.0,>=0.95.2 (from chromadb<0.5.0,>=0.4.0->seagoat)
  Using cached fastapi-0.99.1-py3-none-any.whl.metadata (23 kB)
INFO: This is taking longer than usual. You might need to provide the dependency resolver with stricter constraints to reduce runtime. See https://pip.pypa.io/warnings/backtracking for guidance. If you want to abort this run, press Ctrl + C.
Collecting chromadb<0.5.0,>=0.4.0 (from seagoat)
  Using cached chromadb-0.4.11-py3-none-any.whl.metadata (7.0 kB)
  Using cached chromadb-0.4.10-py3-none-any.whl.metadata (7.0 kB)
  Using cached chromadb-0.4.9-py3-none-any.whl.metadata (7.0 kB)
Collecting chroma-hnswlib==0.7.2 (from chromadb<0.5.0,>=0.4.0->seagoat)
  Using cached chroma-hnswlib-0.7.2.tar.gz (31 kB)
  Installing build dependencies ... done
  Getting requirements to build wheel ... done
  Preparing metadata (pyproject.toml) ... done
Collecting chromadb<0.5.0,>=0.4.0 (from seagoat)
  Using cached chromadb-0.4.8-py3-none-any.whl.metadata (6.9 kB)
  Using cached chromadb-0.4.7-py3-none-any.whl.metadata (6.9 kB)
  Using cached chromadb-0.4.6-py3-none-any.whl.metadata (6.8 kB)
  Using cached chromadb-0.4.5-py3-none-any.whl.metadata (6.8 kB)
  Using cached chromadb-0.4.4-py3-none-any.whl.metadata (6.8 kB)
  Using cached chromadb-0.4.3-py3-none-any.whl.metadata (6.9 kB)
Collecting pandas>=1.3 (from chromadb<0.5.0,>=0.4.0->seagoat)
  Using cached pandas-2.2.3-cp313-cp313-win_amd64.whl.metadata (19 kB)
Collecting chroma-hnswlib==0.7.1 (from chromadb<0.5.0,>=0.4.0->seagoat)
  Using cached chroma-hnswlib-0.7.1.tar.gz (30 kB)
  Installing build dependencies ... done
  Getting requirements to build wheel ... done
  Preparing metadata (pyproject.toml) ... done
Collecting chromadb<0.5.0,>=0.4.0 (from seagoat)
  Using cached chromadb-0.4.2-py3-none-any.whl.metadata (6.9 kB)
  Using cached chromadb-0.4.1-py3-none-any.whl.metadata (6.9 kB)
  Using cached chromadb-0.4.0-py3-none-any.whl.metadata (6.9 kB)
Collecting seagoat
  Using cached seagoat-0.36.1-py3-none-any.whl.metadata (9.7 kB)
  Using cached seagoat-0.35.9-py3-none-any.whl.metadata (9.7 kB)
  Using cached seagoat-0.35.8-py3-none-any.whl.metadata (9.7 kB)
  Using cached seagoat-0.35.7-py3-none-any.whl.metadata (9.7 kB)
  Using cached seagoat-0.35.6-py3-none-any.whl.metadata (9.7 kB)
  Using cached seagoat-0.35.5-py3-none-any.whl.metadata (9.7 kB)
Collecting flask<3.0.0,>=2.3.2 (from seagoat)
  Using cached flask-2.3.3-py3-none-any.whl.metadata (3.6 kB)
Collecting seagoat
  Using cached seagoat-0.35.4-py3-none-any.whl.metadata (9.7 kB)
  Using cached seagoat-0.35.3-py3-none-any.whl.metadata (9.7 kB)
  Using cached seagoat-0.35.2-py3-none-any.whl.metadata (9.7 kB)
  Using cached seagoat-0.35.1-py3-none-any.whl.metadata (9.7 kB)
  Using cached seagoat-0.35.0-py3-none-any.whl.metadata (9.7 kB)
  Using cached seagoat-0.34.0-py3-none-any.whl.metadata (9.5 kB)
Collecting ripgrepy<3.0.0,>=2.0.0 (from seagoat)
  Using cached ripgrepy-2.0.0.tar.gz (19 kB)
  Installing build dependencies ... done
  Getting requirements to build wheel ... done
  Preparing metadata (pyproject.toml) ... done
Collecting seagoat
  Using cached seagoat-0.33.0-py3-none-any.whl.metadata (8.7 kB)
  Using cached seagoat-0.32.2-py3-none-any.whl.metadata (8.2 kB)
  Using cached seagoat-0.32.1-py3-none-any.whl.metadata (8.2 kB)
  Using cached seagoat-0.32.0-py3-none-any.whl.metadata (8.2 kB)
  Using cached seagoat-0.31.0-py3-none-any.whl.metadata (8.2 kB)
  Using cached seagoat-0.30.2-py3-none-any.whl.metadata (8.0 kB)
  Using cached seagoat-0.30.1-py3-none-any.whl.metadata (8.0 kB)
  Using cached seagoat-0.30.0-py3-none-any.whl.metadata (8.0 kB)
  Using cached seagoat-0.29.3-py3-none-any.whl.metadata (7.7 kB)
  Using cached seagoat-0.29.2-py3-none-any.whl.metadata (7.7 kB)
  Using cached seagoat-0.29.1-py3-none-any.whl.metadata (7.7 kB)
  Using cached seagoat-0.29.0-py3-none-any.whl.metadata (7.0 kB)
  Using cached seagoat-0.28.0-py3-none-any.whl.metadata (7.0 kB)
  Using cached seagoat-0.27.2-py3-none-any.whl.metadata (6.3 kB)
  Using cached seagoat-0.27.1-py3-none-any.whl.metadata (6.3 kB)
  Using cached seagoat-0.27.0-py3-none-any.whl.metadata (6.3 kB)
  Using cached seagoat-0.26.0-py3-none-any.whl.metadata (6.3 kB)
  Using cached seagoat-0.25.1-py3-none-any.whl.metadata (6.3 kB)
  Using cached seagoat-0.25.0-py3-none-any.whl.metadata (6.3 kB)
  Using cached seagoat-0.24.0-py3-none-any.whl.metadata (6.3 kB)
  Using cached seagoat-0.23.6-py3-none-any.whl.metadata (6.3 kB)
  Using cached seagoat-0.23.5-py3-none-any.whl.metadata (6.3 kB)
  Using cached seagoat-0.23.4-py3-none-any.whl.metadata (6.3 kB)
  Using cached seagoat-0.23.3-py3-none-any.whl.metadata (6.3 kB)
  Using cached seagoat-0.23.2-py3-none-any.whl.metadata (6.3 kB)
  Using cached seagoat-0.23.1-py3-none-any.whl.metadata (6.3 kB)
  Using cached seagoat-0.23.0-py3-none-any.whl.metadata (6.3 kB)
  Using cached seagoat-0.22.1-py3-none-any.whl.metadata (6.0 kB)
  Using cached seagoat-0.22.0-py3-none-any.whl.metadata (6.0 kB)
  Using cached seagoat-0.21.0-py3-none-any.whl.metadata (6.0 kB)
  Using cached seagoat-0.20.2-py3-none-any.whl.metadata (6.0 kB)
  Using cached seagoat-0.20.1-py3-none-any.whl.metadata (6.0 kB)
  Using cached seagoat-0.20.0-py3-none-any.whl.metadata (3.7 kB)
  Using cached seagoat-0.19.5-py3-none-any.whl.metadata (3.7 kB)
  Using cached seagoat-0.19.4-py3-none-any.whl.metadata (3.7 kB)
  Using cached seagoat-0.19.3-py3-none-any.whl.metadata (3.7 kB)
  Using cached seagoat-0.19.2-py3-none-any.whl.metadata (3.7 kB)
  Using cached seagoat-0.19.1-py3-none-any.whl.metadata (3.6 kB)
  Using cached seagoat-0.19.0-py3-none-any.whl.metadata (3.6 kB)
  Using cached seagoat-0.18.0-py3-none-any.whl.metadata (3.2 kB)
  Using cached seagoat-0.17.2-py3-none-any.whl.metadata (3.2 kB)
  Using cached seagoat-0.17.1-py3-none-any.whl.metadata (3.2 kB)
  Using cached seagoat-0.17.0-py3-none-any.whl.metadata (3.2 kB)
  Using cached seagoat-0.16.2-py3-none-any.whl.metadata (3.2 kB)
  Using cached seagoat-0.16.1-py3-none-any.whl.metadata (3.2 kB)
  Using cached seagoat-0.16.0-py3-none-any.whl.metadata (3.1 kB)
  Using cached seagoat-0.15.2-py3-none-any.whl.metadata (3.1 kB)
  Using cached seagoat-0.15.1-py3-none-any.whl.metadata (3.1 kB)
  Using cached seagoat-0.15.0-py3-none-any.whl.metadata (3.1 kB)
  Using cached seagoat-0.14.0-py3-none-any.whl.metadata (3.1 kB)
  Using cached seagoat-0.13.0-py3-none-any.whl.metadata (3.1 kB)
  Using cached seagoat-0.12.5-py3-none-any.whl.metadata (3.1 kB)
  Using cached seagoat-0.12.4-py3-none-any.whl.metadata (3.1 kB)
  Using cached seagoat-0.12.3-py3-none-any.whl.metadata (3.1 kB)
  Using cached seagoat-0.12.2-py3-none-any.whl.metadata (3.1 kB)
  Using cached seagoat-0.12.1-py3-none-any.whl.metadata (3.1 kB)
  Using cached seagoat-0.12.0-py3-none-any.whl.metadata (3.1 kB)
  Using cached seagoat-0.11.0-py3-none-any.whl.metadata (3.1 kB)
  Using cached seagoat-0.10.6-py3-none-any.whl.metadata (3.1 kB)
  Using cached seagoat-0.10.5-py3-none-any.whl.metadata (3.1 kB)
  Using cached seagoat-0.10.4-py3-none-any.whl.metadata (3.1 kB)
  Using cached seagoat-0.10.3-py3-none-any.whl.metadata (3.1 kB)
  Using cached seagoat-0.10.2-py3-none-any.whl.metadata (3.1 kB)
  Using cached seagoat-0.10.1-py3-none-any.whl.metadata (3.1 kB)
  Using cached seagoat-0.10.0-py3-none-any.whl.metadata (3.1 kB)
  Using cached seagoat-0.9.3-py3-none-any.whl.metadata (2.9 kB)
  Using cached seagoat-0.9.2-py3-none-any.whl.metadata (2.9 kB)
  Using cached seagoat-0.9.1-py3-none-any.whl.metadata (2.9 kB)
  Using cached seagoat-0.9.0-py3-none-any.whl.metadata (2.9 kB)
  Using cached seagoat-0.8.9-py3-none-any.whl.metadata (2.9 kB)
  Using cached seagoat-0.8.8-py3-none-any.whl.metadata (2.9 kB)
  Using cached seagoat-0.8.0-py3-none-any.whl.metadata (2.9 kB)
  Using cached seagoat-0.7.3-py3-none-any.whl.metadata (2.9 kB)
  Using cached seagoat-0.7.2-py3-none-any.whl.metadata (2.9 kB)
Collecting chromadb<0.4.0,>=0.3.26 (from seagoat)
  Using cached chromadb-0.3.29-py3-none-any.whl.metadata (6.9 kB)
Collecting hnswlib>=0.7 (from chromadb<0.4.0,>=0.3.26->seagoat)
  Using cached hnswlib-0.8.0.tar.gz (36 kB)
  Installing build dependencies ... done
  Getting requirements to build wheel ... done
  Preparing metadata (pyproject.toml) ... done
Collecting clickhouse-connect>=0.5.7 (from chromadb<0.4.0,>=0.3.26->seagoat)
  Using cached clickhouse_connect-0.8.7-cp313-cp313-win_amd64.whl.metadata (3.2 kB)
Collecting duckdb>=0.7.1 (from chromadb<0.4.0,>=0.3.26->seagoat)
  Using cached duckdb-1.1.3-cp313-cp313-win_amd64.whl.metadata (781 bytes)
Collecting fastapi==0.85.1 (from chromadb<0.4.0,>=0.3.26->seagoat)
  Using cached fastapi-0.85.1-py3-none-any.whl.metadata (24 kB)
Collecting chromadb<0.4.0,>=0.3.26 (from seagoat)
  Using cached chromadb-0.3.27-py3-none-any.whl.metadata (6.8 kB)
Collecting pydantic==1.9 (from chromadb<0.4.0,>=0.3.26->seagoat)
  Using cached pydantic-1.9.0-py3-none-any.whl.metadata (121 kB)
Collecting chromadb<0.4.0,>=0.3.26 (from seagoat)
  Using cached chromadb-0.3.26-py3-none-any.whl.metadata (6.8 kB)
Collecting seagoat
  Using cached seagoat-0.7.1-py3-none-any.whl.metadata (2.9 kB)
  Using cached seagoat-0.7.0-py3-none-any.whl.metadata (2.9 kB)
  Using cached seagoat-0.6.1-py3-none-any.whl.metadata (2.9 kB)
  Using cached seagoat-0.6.0-py3-none-any.whl.metadata (2.9 kB)
  Using cached seagoat-0.5.6-py3-none-any.whl.metadata (2.0 kB)
  Using cached seagoat-0.5.5-py3-none-any.whl.metadata (2.0 kB)
  Using cached seagoat-0.5.4-py3-none-any.whl.metadata (2.0 kB)
  Using cached seagoat-0.2.1-py3-none-any.whl.metadata (2.0 kB)
  Using cached seagoat-0.2.0-py3-none-any.whl.metadata (1.6 kB)
  Using cached seagoat-0.1.2-py3-none-any.whl.metadata (1.6 kB)
  Using cached seagoat-0.1.1-py3-none-any.whl.metadata (1.6 kB)
  Using cached seagoat-0.1.0-py3-none-any.whl.metadata (1.6 kB)
ERROR: Cannot install seagoat because these package versions have conflicting dependencies.

The conflict is caused by:
    chromadb 0.3.29 depends on pulsar-client>=3.1.0
    chromadb 0.3.27 depends on pulsar-client>=3.1.0
    chromadb 0.3.26 depends on pulsar-client>=3.1.0

To fix this you could try to:
1. loosen the range of package versions you've specified
2. remove package versions to allow pip to attempt to solve the dependency conflict

ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflicts


OnError method not getting called when back button is pressed

OnError method not getting called when back button is pressed.
Using flutter_cashfree_pg_sdk: ^2.1.1+31
For flutter version greatr than 3.16, OnError method not getting called.
But i have test only for Flutter version - 3.16.3 & 3.16.8
https://github.com/cashfree/flutter-cashfree-pg-sdk/assets/147540729/b3b9adbc-470c-45e6-acd4-d1863f1cd497
Expected result
But when using below flutter version, works fine
Flutter version - 3.13.9
https://github.com/cashfree/flutter-cashfree-pg-sdk/assets/147540729/b35ff85b-0a00-4e55-af8f-382e69fb2404
Code
class PaymentWidget extends StatefulWidget {
  const PaymentWidget({super.key});

  @override
  State<PaymentWidget> createState() => _PaymentWidgetState();
}

class _PaymentWidgetState extends State<PaymentWidget> {
  String paymentStatus = 'PaymentStatus None';
  final String _orderId = '';
  final String _paymentSessionId = '';
  static const CFEnvironment _environment = CFEnvironment.SANDBOX;

  final CFPaymentGatewayService _cfPaymentGatewayService =
      CFPaymentGatewayService();
  @override
  Widget build(BuildContext context) {
    return Scaffold(
      body: Center(
        child: Column(
          mainAxisAlignment: MainAxisAlignment.center,
          crossAxisAlignment: CrossAxisAlignment.center,
          children: [
            Text(
              paymentStatus,
              style: TextStyle(
                fontSize: 20,
              ),
            ),
            SizedBox(
              height: 30,
            ),
            ElevatedButton(
              onPressed: onPressed,
              child: const Text(
                'Make Payment',
              ),
            ),
          ],
        ),
      ),
    );
  }

  Future<void> onPressed() async {
    _cfPaymentGatewayService.setCallback(_verifyPayment, _onError);
    await _makePayment();
  }

  Future<void> _verifyPayment(String orderId) async {
    setState(() {
      paymentStatus = 'Payment Success';
    });
  }

  Future<void> _onError(
    CFErrorResponse errorResponse,
    String orderId,
  ) async {
    setState(() {
      paymentStatus = 'Payment Error';
    });
  }

  Future _makePayment() async {
    CFSession session = CFSessionBuilder()
        .setEnvironment(_environment)
        .setOrderId(_orderId)
        .setPaymentSessionId(_paymentSessionId)
        .build();
    var cfWebCheckout =
        CFWebCheckoutPaymentBuilder().setSession(session).build();
    _cfPaymentGatewayService.doPayment(cfWebCheckout);
  }
}

@suhas-cashfree

This is working. Are you still facing any issue ?

yes, issue is still there.
One ore thing i forgot to include one piece of code.
Also add android:enableOnBackInvokedCallback="true" in manifest file.
https://docs.flutter.dev/release/breaking-changes/android-predictive-back#supporting-predictive-back

@dheerajverma009
Can you confirm whether you are running on Android 14 devices?

Yes I am
I was able to test this issue in android 13,and 14. In other versions it works fine.
According to me it is happening when predictive back gestures support is enabled in android. If not enabled it is working fine.

By-default predictive back gestures is available from Android 14.
In Android 13, if some enable thro developer option then only it will be enabled else on Android 13 normal back button flow will work.

@kishan-cashfree  ok, will look into it for android 13

@kishan-cashfree
so do you mean we do not have to add android:enableOnBackInvokedCallback="true" in manifest file for android 14 ?

@dheerajverma009
https://developer.android.com/guide/navigation/custom-back/predictive-back-gesture#opt-predictive
If you don't add, by-default it will be false which means it will continue to work as expected as in previous version.
when you add it in manifest  as true then this will be enable.

@kishan-cashfree
I got it. So as issue descried above, is it a bug or not??

@dheerajverma009
It's not a bug, rather, we will consider it a feature request.

ok, so do i have to raise another issue as feature request for above issue?
And can you also can give update till when this feature will be available.


fix(action): fix the github action parameters

/approve

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

Needs approval from an approver in each of these files:

OWNERS [vbehar]

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


Can't turn on Anvil server anymore

When Anvil server is off, when I click on, I am prompted for my password.
After I enter my password, server is still off..
Any ideas?

Check for updates of Oh my ZSH
If oh my zsh is asking for updates, it wont let pow start, reinstall o restart from anvil
True Story


Keyframe properties after first are ignored.

Only the first property defined in a keyframe are used.
const fadeInAndRotate = stylex.keyframes({
  '0%': { opacity: 0, rotate: '-90deg' },
  '60%': { opacity: 1, rotate: '20deg' },
  '100%': { opacity: 1, rotate: '-90deg' },
});

compiles to
{
  '0%': { opacity: 0 },
  '60%': { opacity: 1},
  '100%': { opacity: 1},
}

and
const test= stylex.keyframes({
  '0%': { backgroundColor: '#fff', width: 100, height: 0 },
  '50%': { translate: -100 },
  '100%': { opacity: 0.5, width: 150, height: 200 },
});

compiles to
{
  '0%': { backgroundColor: '#fff' },
  '50%': { translate: -100 },
  '100%': { opacity: 0.5 },
}

In the mean time I can use multiple keyFrame animations at  the same time.
Only the first property defined in a keyframe are used.
const fadeIn = stylex.keyframes({
  '0%': { opacity: 0 },
  '100%': { opacity: 1 },
});
const blackToWhite = stylex.keyframes({
  '0%': { backgroundColor: '#000' },
  '100%': { backgroundColor: '#fff' },
});

const animation = stylex.create({
  fadeIn: {
    animationName: `${fadeIn}, ${blackToWhite}`,
    animationDuration: '2s, 1s',
  },
});

However I'm not sure this is a problem with the swc-plugin as I don't know if styleX supports multiple properties in it's keyframes. All googled examples always only showed animations using a single property.

Hi @BjornHMS ,
Your provided  examples is a valid StyleX code, the problem is in the SWC plugin. Thanks for finding the bug.
The fix is in the PR and will be available in the next release

My pleasure @Dwlad90
Thank you for your continued support.


Error with replit user

Operating System: macOS 10.15.7
Shell: zsh 5.7.1 (x86_64-apple-darwin19.0)
Python: Python 3.9.1
dillonbarnes@Downstairs-iMac ~ % replit user DillonB07
Traceback (most recent call last):
  File "/Users/dillonbarnes/Library/Python/3.9/bin/replit", line 5, in <module>
    from repl_cli.main import app
  File "/Users/dillonbarnes/Library/Python/3.9/lib/python/site-packages/repl_cli/main.py", line 583, in <module>
    app()
  File "/Users/dillonbarnes/Library/Python/3.9/lib/python/site-packages/typer/main.py", line 214, in __call__
    return get_command(self)(*args, **kwargs)
  File "/Users/dillonbarnes/Library/Python/3.9/lib/python/site-packages/click/core.py", line 829, in __call__
    return self.main(*args, **kwargs)
  File "/Users/dillonbarnes/Library/Python/3.9/lib/python/site-packages/click/core.py", line 782, in main
    rv = self.invoke(ctx)
  File "/Users/dillonbarnes/Library/Python/3.9/lib/python/site-packages/click/core.py", line 1259, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/Users/dillonbarnes/Library/Python/3.9/lib/python/site-packages/click/core.py", line 1066, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/Users/dillonbarnes/Library/Python/3.9/lib/python/site-packages/click/core.py", line 610, in invoke
    return callback(*args, **kwargs)
  File "/Users/dillonbarnes/Library/Python/3.9/lib/python/site-packages/typer/main.py", line 497, in wrapper
    return callback(**use_params)  # type: ignore
  File "/Users/dillonbarnes/Library/Python/3.9/lib/python/site-packages/repl_cli/main.py", line 553, in user
    icon = r['icon']['url']
TypeError: 'NoneType' object is not subscriptable

Video: https://youtu.be/1apEKasLAzA
~This is still processing as I am writing this, so it may be awful video quality for about an hour after this is posted.~

The issue was that my avatar was from gravatar. Changing it worked fine!

Yep the issue is when there isn't a custom profile picture present.
I'm on break right now which is why I haven't fixed it yet as I'm focusing on any major issues, I'll fix it later when I have time.


ISPN-8438 Update to Apache Lucene 5.5.5

Needs backporting on all maintained branches: 8.1.x, 8.2.x, 9.1.x, master

Merged on all maintained branches: 8.1.x, 8.2.x, 9.1.x, master
https://issues.jboss.org/browse/ISPN-8438


Ft/s3 c 1115/gcp copy

Reference Docs:
Copy: https://cloud.google.com/storage/docs/json_api/v1/objects/copy
Update: https://cloud.google.com/storage/docs/json_api/v1/objects/update

@ironman-machine try

Hello @alexanderchan-scality
"try": Success: Try build successfully launched on 'http://ci.ironmann.io/gh/scality/Integration/19053' with the following env. args:
{
    "SCALITY_INTEGRATION_BRANCH": "ultron/master",
    "REPO_NAME": "S3",
    "DEFAULT_BRANCH": "master",
    "SCALITY_S3_BRANCH": "ft/S3C-1115/GCP-COPY"
}

:sunny: :+1: circleCI test succeeded!

@ironman-machine try

Hello @alexanderchan-scality
"try": Success: Try build successfully launched on 'http://ci.ironmann.io/gh/scality/Integration/19057' with the following env. args:
{
    "SCALITY_INTEGRATION_BRANCH": "ultron/master",
    "REPO_NAME": "S3",
    "DEFAULT_BRANCH": "master",
    "SCALITY_S3_BRANCH": "ft/S3C-1115/GCP-COPY"
}

:sunny: :+1: circleCI test succeeded!

PR has been updated. Reviewers, please be cautious.

PR has been updated. Reviewers, please be cautious.

CONFLICT (add/add): Merge conflict in package.json
CONFLICT (add/add): Merge conflict in lib/metadata/wrapper.js
CONFLICT (add/add): Merge conflict in docker-entrypoint.sh
CONFLICT (add/add): Merge conflict in config.json
CONFLICT (add/add): Merge conflict in README.md

PR has been updated. Reviewers, please be cautious.

PR has been updated. Reviewers, please be cautious.

CONFLICT (add/add): Merge conflict in lib/data/external/GcpClient.js

PR has been updated. Reviewers, please be cautious.

PR has been updated. Reviewers, please be cautious.

PR has been updated. Reviewers, please be cautious.

@ironman-machine
DEFAULT_BRANCH=rel/7.4
SCALITY_INTEGRATION_BRANCH=ultron/rel/7.4
SCALITY_S3_BRANCH=ft/S3C-1115/GCP-COPY
try

Hello @alexanderchan-scality
"DEFAULT_BRANCH=rel/7.4": Success
"SCALITY_INTEGRATION_BRANCH=ultron/rel/7.4": Success
"SCALITY_S3_BRANCH=ft/S3C-1115/GCP-COPY": Success
"try": Success: Try build successfully launched on 'http://ci.ironmann.io/gh/scality/Integration/19455' with the following env. args:
{
    "DEFAULT_BRANCH": "rel/7.4",
    "SCALITY_INTEGRATION_BRANCH": "ultron/rel/7.4",
    "REPO_NAME": "S3",
    "SCALITY_S3_BRANCH": "ft/S3C-1115/GCP-COPY"
}

:broken_heart: :umbrella: circleCI test failed.

@ironman-machine
DEFAULT_BRANCH=rel/7.4
SCALITY_INTEGRATION_BRANCH=ultron/rel/7.4
SCALITY_S3_BRANCH=ft/S3C-1115/GCP-COPY
try

Hello @alexanderchan-scality
"DEFAULT_BRANCH=rel/7.4": Success
"SCALITY_INTEGRATION_BRANCH=ultron/rel/7.4": Success
"SCALITY_S3_BRANCH=ft/S3C-1115/GCP-COPY": Success
"try": Success: Try build successfully launched on 'http://ci.ironmann.io/gh/scality/Integration/19456' with the following env. args:
{
    "DEFAULT_BRANCH": "rel/7.4",
    "SCALITY_INTEGRATION_BRANCH": "ultron/rel/7.4",
    "REPO_NAME": "S3",
    "SCALITY_S3_BRANCH": "ft/S3C-1115/GCP-COPY"
}

:sunny: :+1: circleCI test succeeded!


Unable to disable constraints on a table with composed primary key

Given the table
CREATE TABLE myTable
(
  id1 INTEGER NOT NULL,
  id2 INTEGER NOT NULL,
  CONSTRAINT myPk PRIMARY KEY (id1, id2),
);

When calling Databases.postgresql(conn).dropAll("myTable")
Then the error datability.DatabaseException: Error thrown executing sql 'ALTER TABLE myTable DROP CONSTRAINT myPk'. Message: ERROR: constraint "myPk" of relation "myTable" does not exist is returned
Analysis : seems that primarry keys are seen as constraint, and then Datability tries to drop constraint on them.

Fixed by bea98ecd1829df6f9da2069bb36c0e09a0d482e1


zoom prop

can you add prop for enable/disable zoom

@Rome00 Will work on it and release it by end of next week. Thanks :)

@Rome00 Test out the latest version i just published and let me know if that works for you. Thanks :)


Issues when joining with pre 5 on 1.11.2 server

What is the output link of /viaversion dump?
https://gist.github.com/anonymous/a2040bbe27f43d1670c7db78eb5c99e8
Are you using any additional software like BungeeCord? If so, what software and version? (Please list your plugins as well)
HexaCord 1.12 pre5
How does this error happen? login? Using an item?
On login
Is there an error in the console? Use pastebin.com. Is there a kick message?
https://pastebin.com/sUaZX2be
Does even happen without protcolsupport.
Same versions works on our lobby server.
Seems to be something at spawn. If I logout somewhere else it works, but if I go to spawn, it dcs me.
Our spawn:
http://prntscr.com/f9wtnr
Maybe you spot something, that could cause this.

ViaVersion Debug:
https://pastebin.com/PVxn2BW5


Metamask no longer injects web.

Describe the bug
When using the "open" method of the hook useConnectModal it is not possible to connect to Metamask.
The error displayed is as follows:

The application freezes for a few seconds. Then it shows the menu without the Metamask option.
SDK Version

Version 2.0.0-beta.1 & 2.0.0-beta.2
React APP

To Reproduce
const { open } = useConnectModal()
Steps to reproduce the behavior:

Call the function "open"
Click on button
See error

Expected behavior
With  the problem is solved.
I understand that the operation should be the same, except for the aesthetics of the button.
Desktop (please complete the following information):

OS: Windows
Browser Firefox and Chrome

@JSanchezFDZ do you have repo that can be used to re-produce this? I am not able to get that error. Nor are we using web3. Is it possible that there is more stuff down the line where you perhaps try to use web3.js / Web3Provider or something like that?

I'm having the same problem, both in old projects (after updating) and in projects created from scratch. The projects that were already working were in beta.1, but I had a problem with the disconnect hook (the same one mentioned in issue #631), I tried to update to see if it solved it (I even went back to the alpha later and continued with the hook problem useDisconnect with useEffect). After that the problem started, even going back to beta.1 the problem persists.
I started to create a new project in next and also one using vite, both with the same problem.
I created a repository using next:
Repo

Thank you for the repro, will be looking into this 👍

@SatherBosco @JSanchezFDZ I have identified the issue guys, fix will be up in beta.3. Sorry for the inconvenience. As a quick workaround until then you can use our pre-styled component to open / close the modal (it has extra logic that needs to be ported to the open hook)
import { Web3Button } from "@web3modal/react";

Actually, you can also use custom button this way
     <button onClick={() => open()}>CONNECT</button>

Issue is essentially that we treat button event object as custom config for standalone modal that was introduced in beta.2, thus not passing it will also work.

Released beta.3 this should fix your issue and allow to use <button onClick={open}>CONNECT</button> pattern again 👍


[AutoPR managementgroups/resource-manager] chore: jsonfmt managementgroups

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/6154

(message created by the CI based on PR content)
Installation instruction
Direct download
Your files can be directly downloaded here:

azure_mgmt_managementgroups-2018_03_01_preview-py2.py3-none-any.whl
azure-mgmt-managementgroups-2018-03-01-preview.zip

This PR has been merged into https://github.com/Azure/azure-sdk-for-python/pull/5673


Rancher Ec2 Host

I created Ec2 Host on Rancher by providing the Access Key and Secret key. I am able to see the Host is running on Rancher UI but I cannot see the instance on AWS console. Does it appear on AWS console or not?

You're probably looking at the wrong region...


add more metrics for Windows

And make Perfornamce Counter plugin easier to add more metrics.

Two new configuration elements (GeneratorClass and AverageIntervals) have been added, to make it more generic and user friendly, I suggest to use "Transformer" and "TransformerArg", so that it would look like this:
LogicalDiskFreeBytesGenerator                 - Transformer=MegaBytesToBytes
LogicalDiskUsedSpacePercentGenerator   - Transformer=RemainingPercentage
UsedMemoryPercentGenerator                 - Transformer=MemoryAvailableBytesToUsedPercentage
AveragesGenerator                                  - Transformer=Average TransformerArg="60,300,900"
PerformanceCounterCategoryInstancesGenerator  - Transformer=InstanceCount


Determine how to deal with type validation in card metadata

How do we want to deal with card data validation? Dataclasses are a great way to give type hints, but they don't do any validation. Is this a complex enough use case to use pydantic? I think it would make our lives easier, but I'm concerned the dependency won't be welcomed in huggingface_hub if this code gets integrated there down the line.
CC @adrinjalali

Right now, in my PR (#5 ) I'm using dataclasses. I could add a __post_init__ and do validation there potentially.

I would do a card.validate() kinda thing where we do the validation, and yeah we probably don't wanna use pydantic.

Closing this and moving the conversation to #2


chore: fix typos

chore: fix typos

Hi @omahs
Thank you for contributing to Blocto SDK!
Could you help to add the changset following the instruction here so that we can include it in the version changelog?
Thanks again!


PIP-XYZ: Support  latency quantile metric for  pulsar read and write

Motivation

Currently, pulsar does not have an quantile metric used to statistics read and write latency, which is essential for our future troubleshooting and performance comparison tests.
And we need network io metrics to determine the current network processing pressure, to prevent too many requests from hanging the broker.

Goal

Our goal is to statics the latency which begin at readHandler init and end at the messages are read from the cache or underlying storage(eg: bookkeeper / hdfs / ...).
Why we just statics the latency between readHandler init and messages are found:
1.1. Because when fetch request arrive the broker, It may be no new messages for Consumer, the broker will wait and periodically query whether there are new messages, so it may cause the read cache latency longer than the remote read.
1.2. We statics the read latency between the cache/bookeeper/hdfs..., it is enough for us to troubleshooting and performance comparison tests.

We just statics the idle network process number and its percnetile of the total number of io threads.

API Changes

Add OpStats get method to statics the write latency:

public OpStatsLogger getOpStat();

Add generate metrics method for netty thread pool usage

private static void generateNetworkIdleMetrics(PulsarService pulsar, SimpleTextOutputStream stream);

Implementation

Add OpStats get method to statics the write latency:

public OpStatsLogger getOpStat() {
        return PulsarService.statsProvider.getStatsLogger("").getOpStatsLogger("READ_ENTRY_LATENCY");
}

Add generate metrics method for netty thread pool usage:

private static void generateNetworkIdleMetrics(PulsarService pulsar, SimpleTextOutputStream stream) {
        // generate network idle percent metrics
        try {
            int busyExecutors = 0;
            EventLoopGroup workerGroup = pulsar.getBrokerService().executor();
            Iterator<EventExecutor> iterator = workerGroup.iterator();
            while (iterator.hasNext()) {
                SingleThreadEventExecutor next = (SingleThreadEventExecutor) iterator.next();
                if (next.pendingTasks() > 0) {
                    ++busyExecutors;
                }
            }
            int numIoThreads = pulsar.getConfiguration().getNumIOThreads();
            float ioWaitRatioMetric = (float) busyExecutors / (float) numIoThreads;
            // Metric: netIdlePercentile -> ioWaitRatioMetric
            writeNetIdlePercentileMetrics(stream, "brk_net_idle_percentile", (1 - ioWaitRatioMetric) * 100f,
                                          Collector.Type.GAUGE, clusterName, currentTimeMillis);

            // general network io queue metrics
            Iterator<EventExecutor> iterator1 = workerGroup.iterator();
            while (iterator1.hasNext()) {
                SingleThreadEventExecutor next = (SingleThreadEventExecutor) iterator1.next();
                int pendingTasks = next.pendingTasks();
                String name = "brk_pending_tasks_" + StringUtils.replace(next.threadProperties().name(),
                                                                         "-", "_");
                // Metric: thread-name -> pendingTasks
                writeNetIdlePercentileMetrics(stream, name, pendingTasks,
                                              Collector.Type.GAUGE, clusterName, currentTimeMillis);
            }
        } catch (Exception e) {
            log.error("generate network idle percent metrics failed, error: [()]", e);
        }
}

Change the "PIP-XYZ" to a determined number please.   To determine the appropriate PIP number XYZ, inspect the mailing list for the most recent PIP. Add 1 to that PIP's number to get your PIP's number. @3286360470

I think 198 is left for this proposal. @3286360470 please update the title.

I think 198 is left for this proposal. @3286360470 please update the title.

ok, I have updated [XYZ] to 202.

Prometheus is highly recommended


check whether hathitrust rsync update improves ocr

dev notes

[x] update test site so it is synchronized with production (mirror db, content, reindex in Solr)
[x] manually run rsync to update from hathitrust; run in verbose mode and pipe output to a text file so we have a record of what's changed
[x] share text file and compare staging/production to see what the rsync update gets us

depends on #498 — need to replicate so we can compare exactly

related: while we're investigating, let's see if there's useful metadata we can use to track when documents have been rescanned so we'll be alerted if an excerpt page range may change

I think we need to adjust the hathi_rsync manage command to rsync in chunks when we want to update everything and not just specific ids. We're currently using rsync logging, which will give us one file per chunk we rsync. Here's an example of the rsync log output we get by default (this is from running locally, syncing from staging to dev).
The format is a bit arcane; the f/d at the beginning indicates file or directory; the s and t after that for files indicate that size and/or time have changed. The leading c and the ++ are new files being created that I didn't have locally (I don't think that's a scenario we'd expect for PPA, since this is to update existing content).
ppa_hathi_rsync_20240305-164410.log
It's possible to customize the rsync output format (although I don't quite see how yet...); but the rsync log files should tell us if the content has changed and we might need to run other steps (like reindexing or checking excerpt ranges).

I don't have a systematic way to check this, but spot-checking randomly suggests that updating rsync definitely improves OCR (at least for 'normal' texts -- not those written in phonetic alphabet, for instance, as I would expect). A couple examples of improvements:
For hvd.32044011432754, the new OCR recognizes columns (whereas the old OCR runs across the page left to right).
For chi.55229744-p219, the new OCR correctly renders numbers, whereas the old OCR renders them alphabetically such as Iooo for 1000.
As we discussed, updating rsync has so many downsteam effects that it is essential anyway, & this just seems like an added benefit.