Recaptcha error if I register a naccount.

Hello everyone, I have a problem now. I'm from China. So when I register an account, it shows, "Recaptcha error." So how can I do now? Godness
I just want to upload a package=(
Are there somebody can help me with this?

I just want to upload my package

Just, can you cancel it or use another method? I think its not friendly to chinese.

@di can you repair it?

Hi @s0rmayz, sorry you're having trouble here. We've tried a few workarounds on our end for this over the years (#13350, #3174), but looks like this has stopped working again.
If you can provide us with your email address and desired username, we can set up an account for you.

@di RRRRRRRRRRRReally?


Globally set git credential.helper to store in google colab

Fix warning message as discussed in https://github.com/huggingface/huggingface_hub/issues/1043 (https://github.com/huggingface/huggingface_hub/issues/1043#issuecomment-1247010710)
Now if huggingface_hub detects that it runs in a google colab, git config --global credential.helper store is ran by default without warning message to ask the user to do it.
Here is a Google Colab to test it.
(cc @apolinario)

Lots of commit to tests in the notebook but works fine now :grin:

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


Added Modu support

Description
In December 2024, Cyteon created the Modu programming language, that aims to be readable and fast, even tho it's interpreted. I like the project, so i decided to add support for it in GitHub's linguist. The project is improving every day, it's criminally underrated!
Checklist:

[x] I am adding a new language.

[x] The extension of the new language is used in hundreds of repositories on GitHub.com.

Search results for each extension:

https://github.com/search?type=code&q=NOT+is%3Afork+path%3A*.modu

[x] I have included a real-world usage sample for all extensions added in this PR:

Sample source(s):

samples/Modu/helloworld.modu (shows a simple function declaration and hello world)
samples/Modu/math.modu (showcases if statements and library imports

Sample license(s):

[x] I have included a syntax highlighting grammar
[x] I have added a color

Hex value: #F5AAAA
Rationale: The color was picked on Modu's logo, available in https://cyteon.tech/modu

[x] I have updated the heuristics to distinguish my language from others using the same extension.

modu is awesome, must add

In December 2024

There is absolutely no chance this will meet our usage requirements in 29 days of existence… I'm not even going to check. We do not add support for very new or hobby languages.
As such, I'm closing this PR. Feel free to open a new PR when the language meets our usage requirements, and be sure to follow the instructions in the CONTRIBUTING.md file when you do.

:(

Tbh I agree with @lildude. It's too early to add support for this language right now.


Problem when download fasttext embedding

It seems like the link to download fasttext embedding is invalid. I download it from embedding from fasttext website. But I found that the result can't be reproduced with this embedding. Can you update the link to download embedding?

Downloading the fasttext embeddings from: https://dl.fbaipublicfiles.com/fasttext/vectors-wiki/wiki.en.zip seems to work for me


[New VigyBag]- Contact Us and faq Page updated

Fixes Issue
Fix Issue:#1517
Closes:#1517

Changes proposed

Screenshots

Note to reviewers

Summary by CodeRabbit

New Features

Introduced a FAQ section where users can view and expand frequently asked questions.

Style

Adjusted the styling in the Contact Form to enhance layout consistency.

Chores

Updated and adjusted versions of ESLint and related plugins for improved code quality management.

You can merge now

kindly check the file changes then decrease the level


Application Logo

- The Project needs a Logo:-
> A clear and concise logo for the project, would love the *Red-Black* theme to be integrated which designing the logo.
- Time-Constraints:-
> Expected to receive the final draft of the design by 10th Jan 2022.

Please make sure to create a branch, check the results there and then push the changes into the main branch.

okay


Please make the app startup fully minimized in the icon tray

As the title said, it would be nice if the app startup fully minimized in the icon tray. It is a small change but would help a lot.

#169


led.PlotBarGraph - compiler error

Hi Peli, Program below does not compile. Pretty sure that it should. Error is "Compiler Error: c is undefined" and the line bins[n]++ appears in yellow. Thanks! Judith
// Declare bins
let bin: number[]
// Generate numbers, counting in bins
let run = 200
let limit = 5

led.plotBarGraph(0, 0)
for (let i = 0; i < run; i++) {
    let n = Math.random(limit)
    bin[n]++
}

// Show plot
for (let c = 0; c < limit; c++) {
    led.plotBarGraph(c, bin[c] / 40)
}

@abchatra array issue?

Not sure that the visualization you are trying to get will work. Plotbargraph renders the entire screen without pause. You could use pixel brightness to show a 2D histogram

Thanks!!
From: Peli de Halleux<EMAIL_ADDRESS>Sent: Tuesday, February 7, 2017 12:05 PM
To: Microsoft/pxt<EMAIL_ADDRESS>Cc: redjbishop<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [Microsoft/pxt] led.PlotBarGraph - compiler error (#1314)
Not sure that the visualization you are trying to get will work. Plotbargraph renders the entire screen without pause. You could use pixel brightness to show a 2D histogram
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/Microsoft/pxt/issues/1314#issuecomment-278123713, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AK3vaJqwe3Xq5qQX9D-ExAIj6TKCdyTHks5raM6IgaJpZM4L58OO.

There is a bug in the above code. You need to create the array, something like below. It is just defining a variable and not assigning anything.
let bin: number[] = [];

Hi Abhijith – Thanks a lot. I realize now you had told me about how to declare arrays in JavaScript before. Would it be possible to have a better error message?
Judith
From: Abhijith Chatra<EMAIL_ADDRESS>Sent: Tuesday, February 7, 2017 1:55 PM
To: Microsoft/pxt<EMAIL_ADDRESS>Cc: redjbishop<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [Microsoft/pxt] led.PlotBarGraph - compiler error (#1314)
There is a bug in the above code. You need to create the array, something like below. It is just defining a variable and not assigning anything.
let bin: number[] = [];
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/Microsoft/pxt/issues/1314#issuecomment-278153417, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AK3vaFQh06aEMPN0uAzlGbj7jsPI-NZ9ks5raOgvgaJpZM4L58OO.

@redjbishop Yes agree, error message we should improve. I will look into this.

Keeping it open to track error message

We are tracking the error message improvement by collecting data. Closing issue.


Initialize fields of UStructs.

Fixes #846

Thanks for the pull request @kring!

:heavy_check_mark: Signed CLA found.

Reviewers, don't forget to make sure that:

[ ] Cesium for Unreal Samples works.


headers into web platform?

// I need to add headers into web platform, and this option only this into:
 WebSocketOptions.vm

 // Not:
  WebSocketOptions.js

@AndreyDAraya, you can't send headers to the browser's web socket.
https://developer.mozilla.org/en-US/docs/Web/API/WebSocket


Poster upload link 404

@tyrasd https://2024.stateofthemap.org/calls/posters/ is broken.
in fact the 2022 page has simply covered over the 2024 page.
I recommend:

Not having strings like xKeT6JRap embedded into this webpage. Instead just  have ../posters/upload and keep the rest of the details under the hood.
Have an email sent: "Thank you for your poster, abc.pdf, 334 Kb." Else the user cannot be sure OSM really did get the poster, as staff doesn't look at the SOTM mailbox every day.

Wait. Somebody simply has copied the 2022 page into
https://2024.stateofthemap.org/calls/posters/
So someone needs to find the 2024 page and put it back.

Thx, fixed.

Thanks. Also I wish the staff would send a hand typed email to each submitter, saying that they indeed received their file. Else next thing you know the Deadline will have already passed, and some people thought staff received their files, but that is/was not the case.


Incorrect warning 41017 on groupshared variables

I wasn't able to create a simple reproducer case, but I shared privately with @csyonghe an example that is generating a warning on uninitialized groupshared memory and giving this warning in slang v2024.13:
cmaa2.fxc(609): warning 41017: use of uninitialized global variable 'g_groupShared2x2FracEdgesH'
    float4 valH = g_groupShared2x2FracEdgesH [ addr ] ; e00 . y = valH . x ; e10 . y = valH . y ; e01 . y = valH . z ; e11 . y = valH . w ;
           ^~~~
cmaa2.fxc(610): warning 41017: use of uninitialized global variable 'g_groupShared2x2FracEdgesV'
    float4 valV = g_groupShared2x2FracEdgesV [ addr ] ; e00 . x = valV . x ; e10 . x = valV . y ; e01 . x = valV . z ; e11 . x = valV . w ;

Filing this bug so we have an issue tracking it.

@danginsburg I believe you should be able to just disable this warning for your use case. 41017 only applies to global variables, and there is a spearate warning for uninitialized local variables or out parameters. This means that disabling 41017 will still allow you get receive warnings on more common uninitialized var errors.

I am going to close this issue since separating warnings for global and local variable is the what we've agreed to be the most useful solution right now.


cob_substitute: 0.6.6-0 in 'indigo/distribution.yaml' [bloom]

Increasing version of package(s) in repository cob_substitute to 0.6.6-0:

upstream repository: https://github.com/ipa320/cob_substitute.git
release repository: https://github.com/ipa320/cob_substitute-release.git
distro file: indigo/distribution.yaml
bloom version: 0.5.26
previous version for package: 0.6.5-0

cob_docker_control
* added fake_docking executable
  removed unused docker_control
* manually fix changelog
* Contributors: fmw-ss, ipa-fxm

cob_reflector_referencing
* manually fix changelog
* Contributors: ipa-fxm

cob_safety_controller
* manually fix changelog
* Contributors: ipa-fxm

cob_substitute
* remove obsolete packages due to unsupported robots
* manually fix changelog
* Contributors: ipa-fxm

@ipa-flg-pb Just to make sure: This PR is removing some packages that are needed by other packages (e.g. cob_lbr is used by cob_bringup). Are you planning on rereleasing these downstream packages with a reduced set of dependencies?

It looks like the removed packages have been removed a while ago from the source repo: https://github.com/ipa320/cob_substitute/commit/d1e2fc5f862c4fdf3200e01830c9e5662925e38d


separete lane connections for track/road vehicles.

fixes #354

hotkeys and icons from #1479
trolleybuses use same connections as cars.
used Road/Track sub managers to store lane connections.
all other data structures need to use separate arrays to store road/track connections.
lane connection manager does not allow making unsupported lane connection of the wrong lane/vehicle type. this helps with backward compatibility too. but it does allow making backward connections when not allowed for the sake of backward compatibility on train stations. this should change in #1213.

TMPE.zip
pictures are in the comments.
Tests:

[x] car only test: always in car mode. holding alt/shift does not change mode
[x] track only test: always in track mode. holding alt.shift does not change mode
[x] other node test: regardless of whether or not current node is car-only or track-only none-selected nodes show all car+track connections. if alt is held then they only show track connections.
[x] tram road test: holding alt make tram roads select-able. otherwise only car lanes are select-able.
[x] mixed lane mode: normally you see circle and can make car connection. holding alt shows triangle and can make track connection. holding shift can make both connections.
[x] bidirectional lane: node marker is diamond and you can make forward/backward connection. lane curves have arrows on them indicating their direction.
[x] acute+mixed test: hold shift to select mixed lanes. acute targets should show circle, and clicking them should only make car lane connection
[x] acute only mixed lane test: connect a road with mixed tram lane to an intersection with no other tram rods. expected: no
target lane connection is highlighted. shift clicking will put in car mode.
[x] source to target test: make sure you can only make lane connection in the right direction.
[x] hintbox text: go through different state and check if hintbox is OK. make sure ALT/SHIFT modifiers are only there when selecting car+tram node.
[x] big roundabout test: make sure roundabout connector makes stay in lane is applied on entry and inside of the roundabout when there is a node too close to the roundabout and when there are nodes inside roundabout. related #705
[x] mixed lane arrow test: connect trams only on a mixed lane and make sure you can still modify lane arrows. make sure that you can't modify lane arrows if you connect cars only.
[x] separate turning lane: in above scenario make sure separate turning lanes is blocked iff there is a car connection.

mixed connections tests: connect car and track differently on a mixed car+tram lane and:

[x] mixed lane routing test: verify the are routed differently.
[x] refresh test: exit and reenter tool, select the node and make sure you can see all connections.
[x] lane arrow test: lane arrows are influenced only by car connection.
[x] mixed lane persistency test: make sure they connections persist when save/load game
[x] mixed lane record test: make sure connections can be copied by move it.

backward compatibility test:

[x] save game backward compatibility test: connect mixed lanes in old TMPE and saved it. make sure they get both car/track connection when loaded with this version.
[x] lane record backward compatibility test: connect mixed lanes in old TMPE and export it. make sure they get both car/track connection when imported with this version.

TODO:

[X] on mixed lanes do not allow trams to make acute lane connections.
[x] hints

Suggestion: Concise tooltips when mouse hovers over one of the shapes to help user understand what the shape represents.

Looks nice
Make sure that the textures you draw have enough resolution to not be more blurry than the lane sausages and the small circles, so that it looks nice together. Currently on screenshots the triangles are more blurry and standing out.

Currently on screenshots the triangles are more blurry and standing out.

To me it looks like the triangles are fine, but the black border around them is thinner than the black border around the circles, so it's maybe just the black border that's looking blurry?

Currently on screenshots the triangles are more blurry and standing out.

Both triangle and the diamond use the same texture: 256x256 white (the quad gives it shape). So I don't think its a resolution issue. I don't notice any blur. maybe that is just how the overlay shader works?

but the black border around them is thinner than the black border around the circles

You are right. I expand them.

@kvakvs @krzychu124 @aubergine10
I was wondering maybe I can draw squares for uni-directional tracks and diamonds for bi-directional tracks.
triangles are not easy to work with:

they are small (half the size of a square)
they don't cover the lane end and lane curve very well (unless if I shift them but that make the code looks hackish.
their shadow needs re-centering (triangles are asymmetrical.

Enlarged triangle outline

I think you do not need special shape for single/bidirectional lane ends, one shape is fine.  A shape shows the traffic source, so shape on both ends of a junction means traffic comes from both directions.
Since you're using a PNG file it should make no difference in your code, whatever shape you draw in photoshop, even a 🍆 will work just fine, so triangles will work too. But the black outline is still very blurry.

@kvakvs Since you're using a PNG file it should make no difference in your code, whatever shape you draw in photoshop, even a 🍆 will work just fine, so triangles will work too. But the black outline is still very blurry.

1- Centering stuff does matter.
2- I am using square. because triangle will look ugly:
https://media.discordapp.net/attachments/968969871884951572/969000601235111936/unknown.png

I ditched triangle and am using square now. Triangle looks a bit ugly and is hard to write the code.

Looks good!

about backward compatibility at train stations:
In TMPE stable one lane connection like bellow is enough to make trains stay in lane.

The same is true with TMPE in this PR:

This makes backward compatibility easy. There is no need to keep connections that from target to source when loading legacy game.
Removing connections in the wrong direction also solves this issue that happens when you remove lane connections that was made using legacy TMPE:

Sync with master :)


Getting Started doc typo

Fix typo in getting started example code
query ... .result should be query ... .results

Good catch! ;)

thanks


create trivy db at top level instead of subdirectory "db"

Currently trivy db being generated inside "db" directory.
func Dir(cacheDir string) string {
	return filepath.Join(cacheDir, "db")
}

Can we create a db at cacheDir level instead of "db"

@shimish2 thanks for your interest in trivy!
I think that no. what is your use case? why is it needed?

I am trying to integrate trivy for my oci repository server and in our oci repository storage every directory is oci layout, so when I try to integrate trivy, fanal cache is created under db directory which is not an oci layout. That's why I was looking for option if we can create db at top level.

Just to be clear, the ask is whether the location of the db is configurable?
For our application, the db path and name collides with other artifacts.
Happy to post a PR if this is reasonable.
Also related to: https://github.com/aquasecurity/fanal/issues/422


Writing & Reading String data to/from keychain

Hi,
We're currently in the process of migrating to Swift. Our existing keychain management library SAMKeychain (SSKeychain) is writing & saving String data to keychain. I'd like to ask how do we go about making Locksmith compatible with SSKeychain in this sense? (we're trying to avoid writing data migration code)
SSKeychain
- (NSString *)password {
	if ([self.passwordData length]) {
		return [[NSString alloc] initWithData:self.passwordData encoding:NSUTF8StringEncoding];
	}
	return nil;
}

Locksmith
public extension CreateableSecureStorable where Self : InternetPasswordSecureStorable {
    var asCreateableSecureStoragePropertyDictionary: [String: Any] {
        var old = internetPasswordBaseStoragePropertyDictionary
        old[String(kSecValueData)] = NSKeyedArchiver.archivedData(withRootObject: data)
        return old
    }
}

Is there away to override the above variable to return different dictionary where the value is NSData of a string instead of the data dictionary?

Basically what I want is to override this variable to return a different dictionary where the value is NSData of a String instead of a NSData of dictionary data
public extension CreateableSecureStorable where Self : GenericPasswordSecureStorable {
    var asCreateableSecureStoragePropertyDictionary: [String: Any] {
        var old = genericPasswordBaseStoragePropertyDictionary
        old[String(kSecValueData)] = NSKeyedArchiver.archivedData(withRootObject: data)
        return old
    }
}

This is the solution if someone wants to achieve the same result. readFromSecureStore() returns a SecureStorableResultType where you can read the resultDictionary to retrieve the data from the key String(kSecValueData). Then you can convert the data to String as you wish


Poor performance?

I'm very excited about ArrowJS, but I've just came across benchmark, where ArrowJS is one of the slowest.
On the other hand, your performance demo clearly shows ArrowJS is much faster than Vue.
I'm kind of confused...

Yeah great question. Few things to mention here. First, there are a lot of performance enhancements coming down the pipe that should make most of this a moot point.
Second, js benchmarks is valid, but only partially so. All the results are super juiced — what I mean by that is most of the code written is optimized in a way that realistically people dont write their application code. The vue benchmark, for example, uses memo keys and shallow refs to give the absolute fastest performance possible. This isn’t wrong, because it has to "compete" with a ton of libraries doing the same thing, but in the end, the code isnt really how people write their JS.
The version of arrow benchmarked doesnt even have memokeys (it will in the future just to help with the benchmark tests), so they way it is written is pretty much how you would write code in your own app. There are certainly some operations which arrow is slower at than other libraries. In general fine grained mutations, which is what our demo shows, is quite fast.
In the real world, all of these frameworks are "fast enough" — and the only real bottlenecks you should see are initial paint speeds (which arrow is generally quite good at) and a huge number of dom elements (which any fine grained reactive system is quite good at, including arrow).
Again, when I get some time to refocus my efforts back on arrow I plan roll out a number of significant performance improvements. In the meantime if you are interested in a more performant version you can checkout arrow-refactor-1 and arrow-refactor-2.
Good luck out there ❤


feat: Add 'argo set' command

WIP: Not expected to compile as is now

Needs master sync AND tests fixing.

What other terms could we use?

argo tag? argo label?

Available for testing in v2.10.0-rc1.


fix(ui): improve single stat computation

The method we used to compute a single stat / gauge value previously had a few issues:

If the latest value was part of a numeric column but was null/NaN/not defined, the single stat computation would fail and a user would see an error message "Could not display single stat because your values are non-numeric"
If there were multiple latest values, an arbitrary selection would be made

This commit updates the single stat computation to find the latest defined numeric values.
If multiple latest valid numeric values are found, we will either:

Display an error message if using the compuation within a single stat visualization
Display nothing if using the computation within a within a line + single stat visualization (i.e. display the line vis only)

The behavior is similar if no latest numeric value is found.
This commit also updates the single stat computation to use the @influxdata/vis Table format as an intermediate/parsed representation of a Flux CSV response. This unlocks the possibility for performance gains in our CSV parsing. See #13852.
Closes #13824

Looks like this breaks a few of the single stats on the system dashboard template. Looking into it...


Clarity 0.9 wizard doesn't emit clrWizardPageOnLoad on wizard step navigation

We recently upgraded our project to use Angular 4 and Clarity 0.9, but the animations were broken and on investigating further the new wizard doesn't emit clrWizardPageOnLoad on wizard step navigation and hence wizard step animations were not getting triggered.
NOTE: I have imported BrowserAnimationsModule and animations at other places are working fine except for the wizard.

Hi @vediga
Thanks for bringing this to our attention.
Could you tell us which wizard you are using (the old one or new one) and provide a plunkr replicating the issue?
https://plnkr.co/uNwwZe
Thanks!

I don't know if it was before. But this is working as of 0.9.2 in the new wizard.
https://plnkr.co/edit/naLCt9XNAvu2UqFvZjLq?p=preview

Yes it was broken in Clarity 0.9.0 but works in 0.9.2


NDepend - Add Stride code base analysis

Update analysis and find out how this could be better integrated to our Stride Docs..
https://stride-doc-staging.azurewebsites.net/latest/en/contributors/NDependOut/NDependReport.html#Main

Closing as done! A new link available https://doc.stride3d.net/4.2/en/contributors/engine/static-analysis.html


feat: add support for compressing request bodies

A flag can now be passed to the BaseService that will enable gzip compression on the request body data. This flag is passed down to the RequestWrapper class where the compression code lives. Note that no code needs to be changed in the BaseService - the options passed into its constructor will be carried through to the RequestWrapper. In the generated code, I am planning on attaching the flag to the options passed into the BaseService constructor.
If there is a problem during compression, the code moves alone with the request, just uncompressed. If this is not the behavior we want, I can change it.

All feedback should now be addressed

:tada: This PR is included in version 2.7.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Add AWS CLI version 2 (2.0.26)

Motivation for this change
"AWS CLI v2 supports configuring and using credentials through AWS SSO using the new aws configure sso command."
https://aws.amazon.com/blogs/developer/aws-cli-v2-is-now-generally-available/
Since AWS CLI version 1 will be supported for a while, it may make sense to keep this a separate derivation.
https://github.com/NixOS/nixpkgs/issues/80956
Things done

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

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

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

LGTM; can you fixup git history per https://github.com/NixOS/nixpkgs/blob/master/.github/CONTRIBUTING.md ?

LGTM; can you fixup git history per https://github.com/NixOS/nixpkgs/blob/master/.github/CONTRIBUTING.md ?

@bhipple Fixed :wrench:

Result of nixpkgs-review pr 91655 1

1 package built:
- awscli2


IP2366

Is the Library works on IP2366?

This library was tested only on IP2368. I think they should be compatible, but it's better to check it out. Could you provide a register card for IP2366, please?

I have the datasheet translated.  It has some register information in there...   A bit misfoRmaTTed.
ip2366.pdf (1).pdf
Using a Pi, I'm able to scan the I2C bus and get the address back, but not much more than that..

@Eddiiie, thanks for the register map for IP2366.
It looks like IP2366 has the following changes relative to IP2368:

🚩
action
addr
register description
comment

⚠
modified
0x00
SYS_CTL0 (charge enable register)
do not have En_Vbus_Sinkctrl flag

❌
deleted
0x01
SYS_CTL1 (series number setting, battery type, current setting mode)

⚠
modified
0x02
SYS_CTL2 (Vset full charge voltage setting)
do not have Enable Flag; lowest voltage now is 2.5V

⚠
modified
0x03
SYS_CTL3 (Iset charging power or current setting)
do not have Enable Flag

❌
deleted
0x04
SYS_CTL4 (battery capacity setting)

❌
deleted
0x06
SYS_CTL6 (current battery power)

⚠
modified
0x07
SYS_CTL7 (trickle charging current, threshold, and charging timeout settings)
moved to 0x06 adress; now hane only current settings, which takes whole byte

⚠
modified
0x09
SYS_CTL9 (standby enable and low voltage setting)
En_BATlow_Set flag replaced by Standby (Enter standby mode immediately when not charging)

⚠
modified
0x0A
SYS_CTL10 (battery low voltage setting)
lowest voltage now is 2.5V

⚠
modified
0x0C
SYS_CTL12 (output maximum power selection register)
different poder selection map: 30, 45, 60, 65, 100, 140 W

✅
added
0x0D
SELECT_PDO (select charging PDO gear)
set preferable charging voltage

✅
added
0x2C
TypeC_CTL18 (PDO plus 10mA current enable, needs to be configured together with the current setting register)
???

❌
deleted
0x30
SOC_CAP_DATA (battery level data register)

❌
deleted
0x35
MOS_STATE (input MOS status indication register)

✅
added
0x35
RECEIVED_PDO (receive PDO gear)
actual charging voltage provided from charger

❌
deleted
0x54
IVbus_Sink_IADC_DAT0 (input current register)

❌
deleted
0x55
IVbus_Sink_IADC_DAT1 (input current register)

❌
deleted
0x56
IVbus_Src_IADC_DAT_Src_IADC_DAT0 (output current register)

❌
deleted
0x57
IVbus_Src_IADC_DAT1 (output current register)

✅
added
0x69
TIMENODE1 (the first bit of the timestamp register) (the timestamp symbol is an ASCII character)

✅
added
0x6A
TIMENODE2 (the second bit of the timestamp register)

✅
added
0x6B
TIMENODE3 (the third bit of the timestamp register)

✅
added
0x6C
TIMENODE4 (the fourth bit of the timestamp register)

✅
added
0x6D
TIMENODE5 (the fifth bit of the timestamp register)

❌
deleted
0x76
Vsys_POW_DAT2 (Vsys terminal power register Vsys_POW_ADC23:16])

❌
deleted
0x7A
VGPIO1_Iset_DAT0 (VGPIO1_Iset_ADC voltage register)

❌
deleted
0x7B
VGPIO1_Iset_DAT1 (VGPIO1_Iset_ADC voltage register)

❌
deleted
0x7C
VGPIO2_Vset_DAT0 (VGPIO2_Vset_ADC voltage register)

❌
deleted
0x7D
VGPIO2_Vset_DAT1 (VGPIO2_Vset_ADC voltage register)

❌
deleted
0x7E
VGPIO3_FCAP_DAT0 (VGPIO3_FCAP_ADC voltage register)

❌
deleted
0x7F
VGPIO3_FCAP_DAT1 (VGPIO3_FCAP_ADC voltage register)

❌
deleted
0x80
VGPIO4_BATNUM_DAT0 (VGPIO4_BATNUM_ADC voltage register)

❌
deleted
0x81
VGPIO4_BATNUM_DAT1 (VGPIO4_BATNUM_ADC voltage register)

you can compare it yourself based on these documents:
IP2368 I2C regs V1.63 EN.pdf
IP2366 I2C regs V1.13 EN.pdf
So, most functions are still compatible unless they use modified or deleted registers.
For example,
    void enableBatteryTypeSetting(bool enable);
    void setBatteryType(BatteryType type);
    void enableCurrentOrPowerSettingMode(bool enable);
    void setCurrentOrPowerSettingMode(CurrentSettingMode mode);

most likely they will not give any result, because they attempts to write 0x01(SYS_CTL1) register.

Do you know if you can get I2C access to the same LED pins on the IP2366 like you do on these same Ip2368 demo boards?
I have a few of the same purple demo boards for the IP2366 with the LED indicators but thought I needed a special IP2366 chip to be able to communicate with it via I2C. Would be great to know if we could communicate via I2C with any of the IP2366 chips like your doing on the IP2368 chips.

https://github.com/D-314/IP2366-Arduino-Library/tree/main
someone pls test and reply if it works

@RWBRWB, try this solder points. Yiu have to remove resistors first.

It does not work.
using proper 3v pull ups on the I2C lines you get no response on a I2C bus scan.
If you don't use pullups you can get some false readings where it looks like it's responding but it won't consistently unless its a I2C chip version. The techs told me the same when I asked last year.
Sure would be nice if the chip could do both but I guess it can't so they sell different versions.

@RWBRWB, try to play with the INT pin (connect it to GND or VCC). Also try to turn off the chip completely (disconnect the charger, battery and 3v3 power supply), and then connect only the charger and the i2c bus (with INT connected to GND or VCC).
And what do you mean by "false readings"? Is there a device response at 0x75?

I'll add the I2C version of the chip and see if it works without any changes.
The LED version will not provide I2C, that's been verified by multiple people selling the chips for Injonic.

@RWBRWB, try to play with the INT pin (connect it to GND or VCC). Also try to turn off the chip completely (disconnect the charger, battery and 3v3 power supply), and then connect only the charger and the i2c bus (with INT connected to GND or VCC). Also you have to slow down i2c bus to 100kHz for normal device operation.
And what do you mean by "false readings"? Is there a device response at 0x75?

Have you tried this board yet?

I don't have this board, but I wrote a library because there were a lot of requests for this chip. So can you perform the tests under different conditions, please? I have published this library under the name "IP2366" in the Arduino library manager.
Preferable tests
🟡 Yellow 	🟢 Green 	⚪ White 	⏛ Pull-Ups 	💡 Power
⚡VCC 	⏱ SCL 	📟 SDA 	Ω to VCC 	🔌 Cahrger
⏚ GND 	⏱ SCL 	📟 SDA 	Ω to VCC 	🔌 Cahrger
⚡VCC 	📟 SDA 	⏱ SCL 	Ω to VCC 	🔌 Cahrger
⏚ GND 	📟 SDA 	⏱ SCL 	Ω to VCC 	🔌 Cahrger
⚡VCC 	⏱ SCL 	📟 SDA 	❌ removed 	🔌 Cahrger
⏚ GND 	⏱ SCL 	📟 SDA 	❌ removed 	🔌 Cahrger
⚡VCC 	📟 SDA 	⏱ SCL 	❌ removed 	🔌 Cahrger
⏚ GND 	📟 SDA 	⏱ SCL 	❌ removed 	🔌 Cahrger
⚡VCC 	⏱ SCL 	📟 SDA 	Ω to VCC 	↪I2C, then charger
⏚ GND 	⏱ SCL 	📟 SDA 	Ω to VCC 	↪I2C, then charger
⚡VCC 	📟 SDA 	⏱ SCL 	Ω to VCC 	↪I2C, then charger
⏚ GND 	📟 SDA 	⏱ SCL 	Ω to VCC 	↪I2C, then charger
⚡VCC 	⏱ SCL 	📟 SDA 	❌ removed 	↪I2C, then charger
⏚ GND 	⏱ SCL 	📟 SDA 	❌ removed 	↪I2C, then charger
⚡VCC 	📟 SDA 	⏱ SCL 	❌ removed 	↪I2C, then charger
⏚ GND 	📟 SDA 	⏱ SCL 	❌ removed 	↪I2C, then charger

I swapped for the I2C version of the IP2366 chip and it works while the INT pin is floating after taking off the resistors.
I tested your library and it works, the library needs cleaned up for this chip but that shouldn't be too much work as it looks like you have alot of it done already.
Are you in the USA? I can send you a few of these I2C chips if you can get the library fixed up as I need it but have my hands full with multiple other things.

So yea it works

I added the IP2366 Chip and it works as expected.
Library gave me a good starting point also so thanks for that.

@RWBRWB, that's good!
Can you please provide detailed instructions with the actions that you have done? Or at least detailed photos with soldering points (I'm still not sure about the location of the SCL and SDA pins).
I also see you have pull-ups. What happens if you remove them?

Here is a picture showing which is SCL & SDA.

3v Pull-ups are required for reliable I2C communication so even if you get it to work without pull-ups it's not recommended if you don't want random incorrect data at times.
I have the INT pin attached to 3.3v so it never sleeps for testing and that works.
After all that is wired up I just run your libraries ExtendedDataRead.ino and it works. I did adjust the getVsysPower function so the output is formatted properly and adjusted at tad for more accurate readings based on what is actually being consumed by the attached device.

I haven't dug into the library to start exploring the other functions in it but look forward to. I wrote a library for the IP5839 chip in the past from scratch so nice to have a working library to start off with on the IP2366. If you do any more updates to this chip keep me updated as I will do the same if I add anything.
I have 150 of these IP2366 - I2C chips I ordered from China and I could send you 5 for testing if have any boards to use them with. I see the IP2366 better than the Ip2368.

@RWBRWB, that's good! Can you please provide detailed instructions with the actions that you have done? Or at least detailed photos with soldering points (I'm still not sure about the location of the SCL and SDA pins). I also see you have pull-ups. What happens if you remove them?

@RWBRWB, 🥺👉👈

@RWBRWB, 🥺👉👈

Sorry bro, just been caught up running the biz which is leaving almost zero time for playing and testing unfortunately.
I will report back soon as I get your library more, this weekend maybe.
I did start laying out a custom PCB with 4 of the IP2366's on it. 2 for USB C and 2 for USB A ports for a battery pack I'm building.

I did start laying out a custom PCB with 4 of the IP2366's on it. 2 for USB C and 2 for USB A ports for a battery pack I'm building.

I've also thought about this because I have a board that doesn't support I2C.
What kind of microcontroller are you having in mind for this?
Excited to hear about it...

if you hit the button to wake up the Ip2366 before plugging in your device does it work correctly then?
It does the same to me when plugging in a Samsung Phone, if it's not woken up before plugging the phone in then it provides 5v vs 9v but if you wake up the chip or pull the INT pin to 3.3-5v to keep it from going back to sleep then it will supply the phone with the 9v quick charge voltage.
Make sure you remove the I2C resistors also on the purple board.
Mine work just fine after simply swapping chips. Make sure you got the correct I2C chips, hard to tell just by looking at them or the model numbers since they are just manufacturing data.

Hi, I have some of the 2366 purple boards. I bought the 2366 chip with I2C, but the board no longer works by default after the swap. When I plug in a PD charger, it only grabs 5V, and the normal voltage is 20V. Does the IP2366 need some initial programming over i2c to work as a power bank? I can only see the machine-translated datasheet, but I did not find it. I checked the swap was correct. Replaced again by the original 2366, the board works as expected, it is something with the new IC.


angular cli  hmr not reload component

I use angular cli v 1.3rc0 and follow "stories hmr" from their wiki, it works well for a lot of component but there are some components that  after file change, cli rebuild correctly and page is refresh (without reload whole browser like when press F5) this behavior is works perfectly BUT new edition aren't applied, always old one is there and when  I pres F5 the edited text appear correctly.
Any idea?

I'm having the same issue. Sometimes I need to refresh or recompile the build in order to see changes in the view.

can you reproduce the issue in a repo so I can see what's going on

Please apologize Difficult to me i have relativly big project. 70module 60lazyload module. Mabye you @moshejs can give us better input, example ?!?
Thanks to investigate
Cc @gdi2290

I don't know how to reproduce the issue, but here's the behavior:
dev changes HTML
HMR does it's thing
view "flickers"
DOM doesn't update.

I believe I've traced this issue. @angular/cli > ~1.3.0 uses webpack ~3.4.1. I think the issue is that the generated modules are slightly different, so the code that attempts to reload the template doesn't work.
Downgrading to<EMAIL_ADDRESS>and ensuring that webpack ALSO downgrades to 2.x seems to revert this issue.

And that will explain my first breaking change. Thank you for your work

Also see #70


[24] Fix thunk leak in Histogram

Fixes #24

Added strictness annotations to HistogramSample
Switch to Data.Map.Strict as well to avoid thunk leaks within the Map
Do the same in Summary (unimplemented, but this way we won't make the same mistake again)

You can see the thunks disappear in the second ghci session in this gist: https://gist.github.com/ramirez7/591582438c34f6eac9c0b11ca95d086f

Awesome, thank you so much @ramirez7


[Bug]: assert len(self._async_stopped) == 0

Your current environment

The output of `python collect_env.py`
# For security purposes, please feel free to check the contents of collect_env.py before running it.
python collect_env.py
--2024-09-27 03:02:25--  https://raw.githubusercontent.com/vllm-project/vllm/main/collect_env.py
Resolving raw.githubusercontent.com (raw.githubusercontent.com)... <IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>, ...
Connecting to raw.githubusercontent.com (raw.githubusercontent.com)|<IP_ADDRESS>|:443... connected.
Unable to establish SSL connection.
python: can't open file '/home/corvo/collect_env.py': [Errno 2] No such file or directory
corvo@llmpfs-mistral-large-vllmd-0-0:~$ cd /models/
corvo@llmpfs-mistral-large-vllmd-0-0:/models$ python collect_env.py
Collecting environment information...
PyTorch version: 2.4.0+cu121
Is debug build: False
CUDA used to build PyTorch: 12.1
ROCM used to build PyTorch: N/A

OS: Ubuntu 22.04.4 LTS (x86_64)
GCC version: (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
Clang version: Could not collect
CMake version: version 3.29.2
Libc version: glibc-2.35

Python version: 3.10.12 (main, Nov 20 2023, 15:14:05) [GCC 11.4.0] (64-bit runtime)
Python platform: Linux-5.10.223-212.873.amzn2.x86_64-x86_64-with-glibc2.35
Is CUDA available: True
CUDA runtime version: 12.4.131
CUDA_MODULE_LOADING set to: LAZY
GPU models and configuration:
GPU 0: NVIDIA H100 80GB HBM3
GPU 1: NVIDIA H100 80GB HBM3
GPU 2: NVIDIA H100 80GB HBM3
GPU 3: NVIDIA H100 80GB HBM3

Nvidia driver version: 550.90.07
cuDNN version: Probably one of the following:
/usr/lib/x86_64-linux-gnu/libcudnn.so.9.1.0
/usr/lib/x86_64-linux-gnu/libcudnn_adv.so.9.1.0
/usr/lib/x86_64-linux-gnu/libcudnn_cnn.so.9.1.0
/usr/lib/x86_64-linux-gnu/libcudnn_engines_precompiled.so.9.1.0
/usr/lib/x86_64-linux-gnu/libcudnn_engines_runtime_compiled.so.9.1.0
/usr/lib/x86_64-linux-gnu/libcudnn_graph.so.9.1.0
/usr/lib/x86_64-linux-gnu/libcudnn_heuristic.so.9.1.0
/usr/lib/x86_64-linux-gnu/libcudnn_ops.so.9.1.0
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: True

CPU:
Architecture:                         x86_64
CPU op-mode(s):                       32-bit, 64-bit
Address sizes:                        48 bits physical, 48 bits virtual
Byte Order:                           Little Endian
CPU(s):                               192
On-line CPU(s) list:                  0-191
Vendor ID:                            AuthenticAMD
Model name:                           AMD EPYC 7R13 Processor
CPU family:                           25
Model:                                1
Thread(s) per core:                   2
Core(s) per socket:                   48
Socket(s):                            2
Stepping:                             1
BogoMIPS:                             5299.99
Flags:                                fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc cpuid extd_apicid aperfmperf tsc_known_freq pni pclmulqdq monitor ssse3 fma cx16 pcid sse4_1 sse4_2 x2apic movbe popcnt aes xsave avx f16c rdrand hypervisor lahf_lm cmp_legacy cr8_legacy abm sse4a misalignsse 3dnowprefetch topoext perfctr_core invpcid_single ssbd ibrs ibpb stibp vmmcall fsgsbase bmi1 avx2 smep bmi2 invpcid rdseed adx smap clflushopt clwb sha_ni xsaveopt xsavec xgetbv1 clzero xsaveerptr rdpru wbnoinvd arat npt nrip_save vaes vpclmulqdq rdpid
Hypervisor vendor:                    KVM
Virtualization type:                  full
L1d cache:                            3 MiB (96 instances)
L1i cache:                            3 MiB (96 instances)
L2 cache:                             48 MiB (96 instances)
L3 cache:                             384 MiB (12 instances)
NUMA node(s):                         2
NUMA node0 CPU(s):                    0-47,96-143
NUMA node1 CPU(s):                    48-95,144-191
Vulnerability Gather data sampling:   Not affected
Vulnerability Itlb multihit:          Not affected
Vulnerability L1tf:                   Not affected
Vulnerability Mds:                    Not affected
Vulnerability Meltdown:               Not affected
Vulnerability Mmio stale data:        Not affected
Vulnerability Reg file data sampling: Not affected
Vulnerability Retbleed:               Not affected
Vulnerability Spec rstack overflow:   Mitigation; safe RET, no microcode
Vulnerability Spec store bypass:      Mitigation; Speculative Store Bypass disabled via prctl and seccomp
Vulnerability Spectre v1:             Mitigation; usercopy/swapgs barriers and __user pointer sanitization
Vulnerability Spectre v2:             Mitigation; Retpolines, IBPB conditional, IBRS_FW, STIBP always-on, RSB filling, PBRSB-eIBRS Not affected
Vulnerability Srbds:                  Not affected
Vulnerability Tsx async abort:        Not affected

Versions of relevant libraries:
[pip3] numpy==1.26.4
[pip3] nvidia-nccl-cu12==2.20.5
[pip3] onnx==1.16.0
[pip3] optree==0.11.0
[pip3] pytorch-quantization==2.1.2
[pip3] pytorch-triton==3.0.0+989adb9a2
[pip3] pyzmq==26.0.3
[pip3] torch==2.4.0
[pip3] torch-tensorrt==2.4.0a0
[pip3] torchvision==0.19.0
[pip3] transformers==4.44.2
[pip3] triton==3.0.0
[conda] Could not collect
ROCM Version: Could not collect
Neuron SDK Version: N/A
vLLM Version: 0.6.1.post2@156403f983a2922fc2d5dc9da54be2cd474211e0
vLLM Build Flags:
CUDA Archs: 5.2 6.0 6.1 7.0 7.2 7.5 8.0 8.6 8.7 9.0+PTX; ROCm: Disabled; Neuron: Disabled
GPU Topology:
GPU0	GPU1	GPU2	GPU3	CPU Affinity	NUMA Affinity	GPU NUMA ID
GPU0	 X 	NV18	NV18	NV18	48-95,144-191	1		N/A
GPU1	NV18	 X 	NV18	NV18	48-95,144-191	1		N/A
GPU2	NV18	NV18	 X 	NV18	48-95,144-191	1		N/A
GPU3	NV18	NV18	NV18	 X 	48-95,144-191	1		N/A

Legend:

  X    = Self
  SYS  = Connection traversing PCIe as well as the SMP interconnect between NUMA nodes (e.g., QPI/UPI)
  NODE = Connection traversing PCIe as well as the interconnect between PCIe Host Bridges within a NUMA node
  PHB  = Connection traversing PCIe as well as a PCIe Host Bridge (typically the CPU)
  PXB  = Connection traversing multiple PCIe bridges (without traversing the PCIe Host Bridge)
  PIX  = Connection traversing at most a single PCIe bridge
  NV#  = Connection traversing a bonded set of # NVLinks

Model Input Dumps
No response
🐛 Describe the bug
We are wrapping around vllm's AsyncLLMEngine, code can be simplified as below.
engine = AsyncLLMEngine.from_engine_args(self.engine_args)

and then use engine to handle request
def request_handler():
  engine.generate(
              inputs=prompt,
              sampling_params=sampling_params,
              request_id=request_id,
              lora_request=lora_request,
              priority=priority,
          )

The error is
INFO 09-27 03:03:51 llm_engine.py:223] Initializing an LLM engine (v0.6.1.post2) with config: model='/models/mistral-large2', speculative_config=None, tokenizer='/models/mistral-large2', skip_tokenizer_init=False, tokenizer_mode=auto, revision=None, override_neuron_config=None, rope_scaling=None, rope_theta=None, tokenizer_revision=None, trust_remote_code=True, dtype=torch.bfloat16, max_seq_len=131072, download_dir=None, load_format=LoadFormat.AUTO, tensor_parallel_size=4, pipeline_parallel_size=1, disable_custom_all_reduce=False, quantization=fp8, enforce_eager=False, kv_cache_dtype=auto, quantization_param_path=None, device_config=cuda, decoding_config=DecodingConfig(guided_decoding_backend='outlines'), observability_config=ObservabilityConfig(otlp_traces_endpoint=None, collect_model_forward_time=False, collect_model_execute_time=False), seed=0, served_model_name=/models/mistral-large2, use_v2_block_manager=False, num_scheduler_steps=1, enable_prefix_caching=False, use_async_output_proc=True)
WARNING 09-27 03:03:51 multiproc_gpu_executor.py:56] Reducing Torch parallelism from 96 threads to 1 to avoid unnecessary CPU contention. Set OMP_NUM_THREADS in the external environment to tune this value as needed.
INFO 09-27 03:03:51 custom_cache_manager.py:17] Setting Triton cache manager to: vllm.triton_utils.custom_cache_manager:CustomCacheManager
(VllmWorkerProcess pid=180) INFO 09-27 03:03:51 selector.py:116] Using XFormers backend.
(VllmWorkerProcess pid=215) INFO 09-27 03:03:51 selector.py:116] Using XFormers backend.
INFO 09-27 03:03:51 selector.py:116] Using XFormers backend.
(VllmWorkerProcess pid=250) INFO 09-27 03:03:51 selector.py:116] Using XFormers backend.
(VllmWorkerProcess pid=180) /home/corvo/.local/lib/python3.10/site-packages/xformers/ops/fmha/flash.py:211: FutureWarning: `torch.library.impl_abstract` was renamed to `torch.library.register_fake`. Please use that instead; we will remove `torch.library.impl_abstract` in a future version of PyTorch.
(VllmWorkerProcess pid=180)   @torch.library.impl_abstract("xformers_flash::flash_fwd")
(VllmWorkerProcess pid=215) /home/corvo/.local/lib/python3.10/site-packages/xformers/ops/fmha/flash.py:211: FutureWarning: `torch.library.impl_abstract` was renamed to `torch.library.register_fake`. Please use that instead; we will remove `torch.library.impl_abstract` in a future version of PyTorch.
(VllmWorkerProcess pid=215)   @torch.library.impl_abstract("xformers_flash::flash_fwd")
/home/corvo/.local/lib/python3.10/site-packages/xformers/ops/fmha/flash.py:211: FutureWarning: `torch.library.impl_abstract` was renamed to `torch.library.register_fake`. Please use that instead; we will remove `torch.library.impl_abstract` in a future version of PyTorch.
  @torch.library.impl_abstract("xformers_flash::flash_fwd")
(VllmWorkerProcess pid=250) /home/corvo/.local/lib/python3.10/site-packages/xformers/ops/fmha/flash.py:211: FutureWarning: `torch.library.impl_abstract` was renamed to `torch.library.register_fake`. Please use that instead; we will remove `torch.library.impl_abstract` in a future version of PyTorch.
(VllmWorkerProcess pid=250)   @torch.library.impl_abstract("xformers_flash::flash_fwd")
(VllmWorkerProcess pid=180) /home/corvo/.local/lib/python3.10/site-packages/xformers/ops/fmha/flash.py:344: FutureWarning: `torch.library.impl_abstract` was renamed to `torch.library.register_fake`. Please use that instead; we will remove `torch.library.impl_abstract` in a future version of PyTorch.
(VllmWorkerProcess pid=180)   @torch.library.impl_abstract("xformers_flash::flash_bwd")
(VllmWorkerProcess pid=215) /home/corvo/.local/lib/python3.10/site-packages/xformers/ops/fmha/flash.py:344: FutureWarning: `torch.library.impl_abstract` was renamed to `torch.library.register_fake`. Please use that instead; we will remove `torch.library.impl_abstract` in a future version of PyTorch.
(VllmWorkerProcess pid=215)   @torch.library.impl_abstract("xformers_flash::flash_bwd")
(VllmWorkerProcess pid=250) /home/corvo/.local/lib/python3.10/site-packages/xformers/ops/fmha/flash.py:344: FutureWarning: `torch.library.impl_abstract` was renamed to `torch.library.register_fake`. Please use that instead; we will remove `torch.library.impl_abstract` in a future version of PyTorch.
(VllmWorkerProcess pid=250)   @torch.library.impl_abstract("xformers_flash::flash_bwd")
/home/corvo/.local/lib/python3.10/site-packages/xformers/ops/fmha/flash.py:344: FutureWarning: `torch.library.impl_abstract` was renamed to `torch.library.register_fake`. Please use that instead; we will remove `torch.library.impl_abstract` in a future version of PyTorch.
  @torch.library.impl_abstract("xformers_flash::flash_bwd")
(VllmWorkerProcess pid=250) INFO 09-27 03:03:54 multiproc_worker_utils.py:215] Worker ready; awaiting tasks
(VllmWorkerProcess pid=180) INFO 09-27 03:03:54 multiproc_worker_utils.py:215] Worker ready; awaiting tasks
(VllmWorkerProcess pid=215) INFO 09-27 03:03:54 multiproc_worker_utils.py:215] Worker ready; awaiting tasks
(VllmWorkerProcess pid=215) INFO 09-27 03:03:54 utils.py:981] Found nccl from library libnccl.so.2
(VllmWorkerProcess pid=180) INFO 09-27 03:03:54 utils.py:981] Found nccl from library libnccl.so.2
INFO 09-27 03:03:54 utils.py:981] Found nccl from library libnccl.so.2
(VllmWorkerProcess pid=215) (VllmWorkerProcess pid=180) INFO 09-27 03:03:54 pynccl.py:63] vLLM is using nccl==2.20.5
INFO 09-27 03:03:54 pynccl.py:63] vLLM is using nccl==2.20.5
INFO 09-27 03:03:54 pynccl.py:63] vLLM is using nccl==2.20.5
(VllmWorkerProcess pid=250) INFO 09-27 03:03:54 utils.py:981] Found nccl from library libnccl.so.2
(VllmWorkerProcess pid=250) INFO 09-27 03:03:54 pynccl.py:63] vLLM is using nccl==2.20.5
(VllmWorkerProcess pid=215) INFO 09-27 03:03:56 custom_all_reduce_utils.py:242] reading GPU P2P access cache from /home/corvo/.cache/vllm/gpu_p2p_access_cache_for_0,1,2,3.json
(VllmWorkerProcess pid=250) INFO 09-27 03:03:56 custom_all_reduce_utils.py:242] reading GPU P2P access cache from /home/corvo/.cache/vllm/gpu_p2p_access_cache_for_0,1,2,3.json
INFO 09-27 03:03:56 custom_all_reduce_utils.py:242] reading GPU P2P access cache from /home/corvo/.cache/vllm/gpu_p2p_access_cache_for_0,1,2,3.json
(VllmWorkerProcess pid=180) INFO 09-27 03:03:56 custom_all_reduce_utils.py:242] reading GPU P2P access cache from /home/corvo/.cache/vllm/gpu_p2p_access_cache_for_0,1,2,3.json
INFO 09-27 03:03:56 shm_broadcast.py:235] vLLM message queue communication handle: Handle(connect_ip='<IP_ADDRESS>', local_reader_ranks=[1, 2, 3], buffer=<vllm.distributed.device_communicators.shm_broadcast.ShmRingBuffer object at 0x7fc7022a4760>, local_subscribe_port=49977, remote_subscribe_port=None)
INFO 09-27 03:03:56 model_runner.py:999] Starting to load model /models/mistral-large2...
(VllmWorkerProcess pid=180) INFO 09-27 03:03:56 model_runner.py:999] Starting to load model /models/mistral-large2...
(VllmWorkerProcess pid=215) INFO 09-27 03:03:56 model_runner.py:999] Starting to load model /models/mistral-large2...
(VllmWorkerProcess pid=250) INFO 09-27 03:03:56 model_runner.py:999] Starting to load model /models/mistral-large2...
(VllmWorkerProcess pid=215) WARNING 09-27 03:03:56 fp8.py:47] Detected fp8 checkpoint. Please note that the format is experimental and subject to change.
(VllmWorkerProcess pid=180) WARNING 09-27 03:03:56 fp8.py:47] Detected fp8 checkpoint. Please note that the format is experimental and subject to change.
(VllmWorkerProcess pid=250) WARNING 09-27 03:03:56 fp8.py:47] Detected fp8 checkpoint. Please note that the format is experimental and subject to change.
WARNING 09-27 03:03:56 fp8.py:47] Detected fp8 checkpoint. Please note that the format is experimental and subject to change.
(VllmWorkerProcess pid=215) INFO 09-27 03:03:56 selector.py:116] Using XFormers backend.
(VllmWorkerProcess pid=180) INFO 09-27 03:03:56 selector.py:116] Using XFormers backend.
INFO 09-27 03:03:56 selector.py:116] Using XFormers backend.
(VllmWorkerProcess pid=250) INFO 09-27 03:03:56 selector.py:116] Using XFormers backend.
Loading safetensors checkpoint shards:   0% Completed | 0/26 [00:00<?, ?it/s]
Loading safetensors checkpoint shards:   4% Completed | 1/26 [00:00<00:03,  8.01it/s]
Loading safetensors checkpoint shards:   8% Completed | 2/26 [00:00<00:06,  3.56it/s]
Loading safetensors checkpoint shards:  12% Completed | 3/26 [00:00<00:08,  2.86it/s]
Loading safetensors checkpoint shards:  15% Completed | 4/26 [00:01<00:07,  2.77it/s]
Loading safetensors checkpoint shards:  19% Completed | 5/26 [00:01<00:07,  2.71it/s]
Loading safetensors checkpoint shards:  23% Completed | 6/26 [00:02<00:07,  2.60it/s]
Loading safetensors checkpoint shards:  27% Completed | 7/26 [00:02<00:07,  2.53it/s]
Loading safetensors checkpoint shards:  31% Completed | 8/26 [00:02<00:07,  2.44it/s]
Loading safetensors checkpoint shards:  35% Completed | 9/26 [00:03<00:07,  2.33it/s]
Loading safetensors checkpoint shards:  38% Completed | 10/26 [00:03<00:07,  2.26it/s]
Loading safetensors checkpoint shards:  42% Completed | 11/26 [00:04<00:06,  2.24it/s]
Loading safetensors checkpoint shards:  46% Completed | 12/26 [00:04<00:06,  2.12it/s]
Loading safetensors checkpoint shards:  50% Completed | 13/26 [00:05<00:06,  2.02it/s]
Loading safetensors checkpoint shards:  54% Completed | 14/26 [00:06<00:06,  1.91it/s]
Loading safetensors checkpoint shards:  58% Completed | 15/26 [00:06<00:06,  1.82it/s]
Loading safetensors checkpoint shards:  62% Completed | 16/26 [00:07<00:05,  1.77it/s]
Loading safetensors checkpoint shards:  65% Completed | 17/26 [00:07<00:05,  1.79it/s]
Loading safetensors checkpoint shards:  69% Completed | 18/26 [00:08<00:04,  1.79it/s]
Loading safetensors checkpoint shards:  73% Completed | 19/26 [00:08<00:03,  1.79it/s]
Loading safetensors checkpoint shards:  77% Completed | 20/26 [00:09<00:03,  1.77it/s]
Loading safetensors checkpoint shards:  81% Completed | 21/26 [00:10<00:02,  1.77it/s]
Loading safetensors checkpoint shards:  85% Completed | 22/26 [00:10<00:02,  1.78it/s]
Loading safetensors checkpoint shards:  88% Completed | 23/26 [00:11<00:01,  1.83it/s]
Loading safetensors checkpoint shards:  92% Completed | 24/26 [00:11<00:01,  1.85it/s]
Loading safetensors checkpoint shards:  96% Completed | 25/26 [00:12<00:00,  1.83it/s]
Loading safetensors checkpoint shards: 100% Completed | 26/26 [00:12<00:00,  1.84it/s]
Loading safetensors checkpoint shards: 100% Completed | 26/26 [00:12<00:00,  2.04it/s]
(VllmWorkerProcess pid=215) INFO 09-27 03:04:09 model_runner.py:1010] Loading model weights took 28.7698 GB
(VllmWorkerProcess pid=180) INFO 09-27 03:04:10 model_runner.py:1010] Loading model weights took 28.7698 GB
(VllmWorkerProcess pid=250) INFO 09-27 03:04:10 model_runner.py:1010] Loading model weights took 28.7698 GB
INFO 09-27 03:04:10 model_runner.py:1010] Loading model weights took 28.7698 GB
INFO 09-27 03:04:12 distributed_gpu_executor.py:57] # GPU blocks: 32028, # CPU blocks: 2978
INFO 09-27 03:04:14 model_runner.py:1444] Capturing the model for CUDA graphs. This may lead to unexpected consequences if the model is not static. To run the model in eager mode, set 'enforce_eager=True' or use '--enforce-eager' in the CLI.
INFO 09-27 03:04:14 model_runner.py:1448] CUDA graphs can take additional 1~3 GiB memory per GPU. If you are running out of memory, consider decreasing `gpu_memory_utilization` or enforcing eager mode. You can also reduce the `max_num_seqs` as needed to decrease memory usage.
(VllmWorkerProcess pid=250) INFO 09-27 03:04:14 model_runner.py:1444] Capturing the model for CUDA graphs. This may lead to unexpected consequences if the model is not static. To run the model in eager mode, set 'enforce_eager=True' or use '--enforce-eager' in the CLI.
(VllmWorkerProcess pid=250) INFO 09-27 03:04:14 model_runner.py:1448] CUDA graphs can take additional 1~3 GiB memory per GPU. If you are running out of memory, consider decreasing `gpu_memory_utilization` or enforcing eager mode. You can also reduce the `max_num_seqs` as needed to decrease memory usage.
(VllmWorkerProcess pid=180) INFO 09-27 03:04:14 model_runner.py:1444] Capturing the model for CUDA graphs. This may lead to unexpected consequences if the model is not static. To run the model in eager mode, set 'enforce_eager=True' or use '--enforce-eager' in the CLI.
(VllmWorkerProcess pid=180) INFO 09-27 03:04:14 model_runner.py:1448] CUDA graphs can take additional 1~3 GiB memory per GPU. If you are running out of memory, consider decreasing `gpu_memory_utilization` or enforcing eager mode. You can also reduce the `max_num_seqs` as needed to decrease memory usage.
(VllmWorkerProcess pid=215) INFO 09-27 03:04:14 model_runner.py:1444] Capturing the model for CUDA graphs. This may lead to unexpected consequences if the model is not static. To run the model in eager mode, set 'enforce_eager=True' or use '--enforce-eager' in the CLI.
(VllmWorkerProcess pid=215) INFO 09-27 03:04:14 model_runner.py:1448] CUDA graphs can take additional 1~3 GiB memory per GPU. If you are running out of memory, consider decreasing `gpu_memory_utilization` or enforcing eager mode. You can also reduce the `max_num_seqs` as needed to decrease memory usage.
(VllmWorkerProcess pid=180) INFO 09-27 03:04:35 custom_all_reduce.py:240] Registering 6195 cuda graph addresses
(VllmWorkerProcess pid=250) INFO 09-27 03:04:35 custom_all_reduce.py:240] Registering 6195 cuda graph addresses
(VllmWorkerProcess pid=215) INFO 09-27 03:04:35 custom_all_reduce.py:240] Registering 6195 cuda graph addresses
INFO 09-27 03:04:35 custom_all_reduce.py:240] Registering 6195 cuda graph addresses
(VllmWorkerProcess pid=180) INFO 09-27 03:04:35 model_runner.py:1564] Graph capturing finished in 21 secs.
INFO 09-27 03:04:35 model_runner.py:1564] Graph capturing finished in 21 secs.
(VllmWorkerProcess pid=250) INFO 09-27 03:04:35 model_runner.py:1564] Graph capturing finished in 21 secs.
(VllmWorkerProcess pid=215) INFO 09-27 03:04:35 model_runner.py:1564] Graph capturing finished in 21 secs.
INFO 09-27 03:04:35 engine.py:125] Took 44.80 seconds to start vllm engine for model mistral-large2
INFO 09-27 03:04:57 metrics.py:352] Avg prompt throughput: 0.1 tokens/s, Avg generation throughput: 0.0 tokens/s, Running: 0 reqs, Swapped: 0 reqs, Pending: 0 reqs, GPU KV cache usage: 0.0%, CPU KV cache usage: 0.0%.
INFO 09-27 03:05:27 metrics.py:352] Avg prompt throughput: 0.1 tokens/s, Avg generation throughput: 0.0 tokens/s, Running: 0 reqs, Swapped: 0 reqs, Pending: 0 reqs, GPU KV cache usage: 0.0%, CPU KV cache usage: 0.0%.
INFO 09-27 03:05:43 metrics.py:352] Avg prompt throughput: 3.2 tokens/s, Avg generation throughput: 0.1 tokens/s, Running: 2 reqs, Swapped: 0 reqs, Pending: 2 reqs, GPU KV cache usage: 46.5%, CPU KV cache usage: 0.0%.
ERROR 09-27 03:05:43 async_llm_engine.py:58] Engine background task failed
ERROR 09-27 03:05:43 async_llm_engine.py:58] Traceback (most recent call last):
ERROR 09-27 03:05:43 async_llm_engine.py:58]   File "/home/corvo/vllm-project/vllm/engine/async_llm_engine.py", line 48, in _log_task_completion
ERROR 09-27 03:05:43 async_llm_engine.py:58]     return_value = task.result()
ERROR 09-27 03:05:43 async_llm_engine.py:58]   File "/home/corvo/vllm-project/vllm/engine/async_llm_engine.py", line 772, in run_engine_loop
ERROR 09-27 03:05:43 async_llm_engine.py:58]     result = task.result()
ERROR 09-27 03:05:43 async_llm_engine.py:58]   File "/home/corvo/vllm-project/vllm/engine/async_llm_engine.py", line 712, in engine_step
ERROR 09-27 03:05:43 async_llm_engine.py:58]     request_outputs = await self.engine.step_async(virtual_engine)
ERROR 09-27 03:05:43 async_llm_engine.py:58]   File "/home/corvo/vllm-project/vllm/engine/async_llm_engine.py", line 296, in step_async
ERROR 09-27 03:05:43 async_llm_engine.py:58]     ) = self.scheduler[virtual_engine].schedule()
ERROR 09-27 03:05:43 async_llm_engine.py:58]   File "/home/corvo/vllm-project/vllm/core/scheduler.py", line 1115, in schedule
ERROR 09-27 03:05:43 async_llm_engine.py:58]     scheduler_outputs = self._schedule()
ERROR 09-27 03:05:43 async_llm_engine.py:58]   File "/home/corvo/vllm-project/vllm/core/scheduler.py", line 1078, in _schedule
ERROR 09-27 03:05:43 async_llm_engine.py:58]     return self._schedule_chunked_prefill()
ERROR 09-27 03:05:43 async_llm_engine.py:58]   File "/home/corvo/vllm-project/vllm/core/scheduler.py", line 1015, in _schedule_chunked_prefill
ERROR 09-27 03:05:43 async_llm_engine.py:58]     running_scheduled = self._schedule_running(budget,
ERROR 09-27 03:05:43 async_llm_engine.py:58]   File "/home/corvo/vllm-project/vllm/core/scheduler.py", line 542, in _schedule_running
ERROR 09-27 03:05:43 async_llm_engine.py:58]     assert len(self._async_stopped) == 0
ERROR 09-27 03:05:43 async_llm_engine.py:58] AssertionError

Before submitting a new issue...

[X] Make sure you already searched for relevant issues, and asked the chatbot living at the bottom right corner of the documentation page, which can answer lots of frequently asked questions.

i have more clues of how to reproduce now, let me add details later.

@alexm-neuralmagic

same issue here

save issue

I had a similar issue with Mixtral 8x22B. It might be caused by chunked prefill, as I managed to solve the issue by using enable_chunked_prefill=False.

has anyone solved this?


lib/rbreadline: Replace DL with Fiddle.

This removes usage of the now-deprecated DL in favour of Fiddle. Fixes
deprecation warnings when running under Ruby 2.0 and newer.

Ｉ tried this change. LGTM.
This is good to remove warning DL is deprecated, please use Fiddle


RHOAIENG-1119: Update result names that assume "internal" image

This PR stacks upon #215, #217, and #218. It will be held until those are merged, but it can still be reviewed, by just reviewing the new commit(s). This PR is an cleanup change to keep the result names meaningful.
JIRA: https://issues.redhat.com/browse/RHOAIENG-1119
Description

The following result name changes are included in this change; because
the image is not necessarily internal any longer, and/or the
properties are not specific to the candidate image:

internal-registry-url -> candidate-image-tag-reference
internal-image-url -> image-digest-reference
internal-image-size -> image-size-bytes
internal-image-created-at -> image-creation-time

How Has This Been Tested?

Example PipelineRuns execute successfully

Merge criteria:

[x] The commits are squashed in a cohesive manner and have meaningful messages.
[x] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[x] The developer has manually tested the changes and verified that the changes work

/hold until #215, #217, and #218 are reviewed and merged.

Looks good to me too.

/unhold


Revoke-token issue

When trying to revoke have an error (working via PostMan) :
{
"error": "invalid_request",
"error_description": "URL query parameters are not allowed"
}

Hi all.
My team and I are constantly using this framework and it seems it has died out there. I contacted the owner by email asking if he would add some of us as maintainers so we could continue to improve it. However we didn't get a response.
I am publishing the project under my profile and we are going to continue to invest time in it.
So I would like to gently ask you to contribute to this project on: https://github.com/wagnerdelima/drf-social-oauth2.
Thank you for understanding.


chore: add changelog for v0.1 and v0.2

This PR adds a changelog in preparation for the release of v0.2.

We can wait to merge this until the docs PR #152 is done and everything else is ready to go.

Thanks for the review @tohrnii, I've made some of the updates and addressed your other points


cmake: kconfig: pass EXTRA_DTC_FLAGS to kconfig for EDT init

Pass EXTRA_DTC_FLAGS to kconfig so the EDT object we have in
kconfigfunctions can use that to set warn_reg_unit_address_mismatch
properly.
Signed-off-by: Kumar Gala<EMAIL_ADDRESS>

CI failure is related to qemu, not going to re-run.


[Bug]: Japanese date format is not parsed correctly

Debug log ID
WQJ98YTK-apse
What happened?
Since I use Japanese language in Google Chrome, Zotero Connector sets the "date" value of some items like "7月 1, 2009".
https://dl.acm.org/doi/10.1145/1538788.1538814 is an example and I submitted the debug output for it.
When I export this item using better bibtex, it sets BibTeX's "year" value as "7月 1, 2009", which should have been "2009".
A similar issue for Chinese was reported in https://github.com/retorquere/zotero-better-bibtex/issues/621 and it seems to have been fixed (so "七月 1, 2009" will be correctly parsed into "2009"), but still Japanese "7月 1, 2009" does not work.
Also refer to twitter reply from Emiliano Heyns(@retorquere): https://twitter.com/retorquere/status/1635403804010237952 and https://twitter.com/retorquere/status/1635404438386130945
Workaround
Use following postscript:
if (tex.has.year) {
tex.add({name: 'year', replace: true, value: tex.has.year.value.replace(/.* /, '')})
}

This is essentialy same as one provided in the previous issue but updated to conform to the current version.
Also note that you may have to enable debug output logging and modify postscript to make your script work: https://github.com/retorquere/zotero-better-bibtex/issues/2447

Build 4011 should fix that. If you could confirm, I can roll that into a new release.

I confirmed the build 4011 fixed this. thank you.


Please make the project exposes multiple YAML files to GraphQL nodes.

What would you like to be added:

Parameterize typeName of gatsby-transformer-yaml plugin or make it flexible that we can expose new YAML to new GraphQL node.
Why is this needed:

Since we set  typeName to static value SidebarItems, we cannot expose new YAML file to a new GraphQL node.
Is your enhancement request related to a problem? Please describe.

I would like to add new data stored in YAML and expose it as GraphQL node that I can query later.
However, adding gatsby-transformer-yaml plugin section in my custom gatsby-config doesn't help.
This is because it cannot override the existing  typeName: 'SidebarItems' and all new YML files will be merged to this type.
This also causes  an issue when trying to [query allSidebarItems in gast-by-node.js].(https://github.com/jpedroschmitz/rocketdocs/blob/main/%40rocketseat/gatsby-theme-docs-core/gatsby-node.js#L75)
Additional context
This screenshot took from my personal project that I added multiple YAML files and exposed them to GraphQL nodes.
I only use default type name of gatsby-transformer-yaml

Could you open a PR for it?
We can add a new option for this.

@jpedroschmitz That's okay. Thank you.

@jpedroschmitz PR's opened #124
Thanks.

A new version that supports this feature was released!
Thanks a lot for your work on this @aaronamm ❤


Wrapping DatePicker in a styled-component prevents typing of dates

A convenient way to apply custom styling with react-datepicker is to wrap the <DatePicker /> component using the popular styled-components library. For example:
const Wrapper = styled.div`
  .react-datepicker {
    box-shadow: 3px 2px 11px rgb(0 0 0 / 30%);
  }
  .react-datepicker__input-container input {
    width: ${props.width || "auto"};
  }
`;

return (
  <Wrapper>
    <DatePicker
      onChange={date => setSelectedDate(date)}
      selected={selectedDate}
    />
  </Wrapper>
);

The Issue
Wrapping <DatePicker /> as above causes any typed entry of text that can be interpreted as a date to immediately select that date and de-focus the field — exactly as if the date had been clicked from the calendar popup. For example, typing 3 into the field will immediately populate the date 03/01/2021, instead of allowing the user to continue typing the rest of a date interactively. Typing a non-date value like - will allow the user to continue typing until a valid date is recognized. If you type ---3, you're fine until the 3, at which point the number ---3 is interpreted as the date 03/01/2021.
Wrapping <DatePicker /> in a plain <div> does not cause this problem.
Wrapping <DatePicker /> in a <Wrapper /> does cause this problem, even if the wrapper contains no styles at all.
Minimal Repro Case
...

import DatePicker from "react-datepicker";
import styled from "styled-components";

const [selectedDate, setSelectedDate] = useState(null);

const Wrapper = styled.div`
`;

return (
  <Wrapper>
    <DatePicker
      onChange={date => setSelectedDate(date)}
      selected={selectedDate}
    />
  </Wrapper>
);

The expected behavior here would be that the user is allowed to begin typing text like 4/1/2024, and the cursor would remain in the field and allow that date to continue to be typed.
The observed behavior is that the instant the 4 is typed, the field is populated and defocused. Swapping out <Wrapper> for a plain <div> allows the correct behavior again.
In all other ways, the styled wrapper approach works fine.

Bump. Still a problem.

I think this is down to how you have defined your Wrapper. Styled components should be defined outside otherwise any change to state will cause them to be recreated. The typed input is changing state which recreates your Wrapper and unmounts its children.
import DatePicker from "react-datepicker";
import styled from "styled-components";

const Wrapper = styled.div``; // Moved outside of Calendar component

const Calendar = () => {
  const [selectedDate, setSelectedDate] = useState(null);

  return (
    <Wrapper>
      <DatePicker
        onChange={date => setSelectedDate(date)}
        selected={selectedDate}
      />
    </Wrapper>
  );
};

https://styled-components.com/docs/basics#define-styled-components-outside-of-the-render-method

You can wrap directly the DatePicker component like :
const Wrapper = styled(DatePicker)`
    border-radius: 4px;
    border: 1px solid ${colors('grey')};
`

and use the Wrapper component instead DatePicker like
<Wrapper
    selected={startDate}
    onChange={(date) => setStartDate(date)}
/>

same for me, @redler except that in my case I've already defined outside the styled components and, unfortunately, solution provided by @alimtunc doesn't work for me: no style rule is applied...

same for me, @redler except that in my case I've already defined outside the styled components and, unfortunately, solution provided by @alimtunc doesn't work for me: no style rule is applied...

Iff all you wan to do is style the calendar element, use the calendarContainer prop:
// Styled component
export const CalendarContainer = styled.div`
    width: 400px;
`;

// Component
export const DatePicker = () => {
    const [startDate, setStartDate] = useState(new Date());

    return (
        <ReactDatePicker
            calendarContainer={Styled.CalendarContainer}
            selected={startDate}
            onChange={(date) => setStartDate(date)}
        />
    );
};


Invalid conversion allowed in gsl::span constructor

The constructor for gsl::span from any container seems to be a bit too permissive when it comes to Base and Derived types. (nb: the same remark applies to Microsoft's version of GSL)
struct B { int _b; B(int b) : _b{b} { } };
struct D : B { int _d; D(int b,int d) : B{b}, _d{d} { } };
std::vector<D> v1={{1,10},{2,20},{3,30}};
gsl::span<B> s1(v1);
for(const auto &i: s1) { std::cerr << i._b << ' '; } std::cerr << '\n';
// obtained: 1 10 2 20 3 30 (i.e. kind of reinterpret_cast with an incorrect size!)
// expected: compilation failure since D[] is not convertible to B[]
//           (although D* is convertible to B*)

I would suggest a constructor similar to this one.
  template<typename Container,
           typename PointerType = decltype(std::declval<Container>().data()),
           typename ValueType = decltype(*std::declval<PointerType>()),
           typename SizeType = decltype(std::declval<Container>().size()),
           typename = std::enable_if_t<
                        std::is_convertible<PointerType,pointer>::value&&
                        std::is_same<std::decay_t<ValueType>,
                                     std::decay_t<value_type>>::value&&
                        std::is_convertible<SizeType,size_type>::value>>
  gsl_api gsl_constexpr14
  span(Container &c) noexcept
  : begin_{c.data()}
  , end_{c.data()+c.size()}
  { }

By the way (another topic): shouldn't  GSL_UNENFORCED_ON_CONTRACT_VIOLATION be automatically defined when NDEBUG is?
Thank you for your great work (and readable code!).
Hope that helps.

Thanks!
To answer your question right away:

By the way (another topic): shouldn't GSL_UNENFORCED_ON_CONTRACT_VIOLATION be automatically defined when NDEBUG is?

Boundary checking at runtime at default is by intent, see this comment.

M-GSL issue #384.

Closing this as the constructor for containers is constrained as in proposal p0122, see release 0.31.0.


How to write models programmatically

I am wondering how to use the macro to scale models up programmatically.
What I have in mind is a model with multiple regions where most of the equations are the same for each region and could be recycled.
In dynare this can be done with the dynare macro which allows for loops in building a mod file.
I am sure it is possible to modify the expression in between @model and also @parameters but I tried using basic Meta.parse and could not get it to work.
Any pointer would be appreciated.
Thank you.

This could work if we use vectors to represent the different regions.
Something even more flexible (but I am not sure about practicality is to allow the macro to define new variables.
For example in dynare I would have the following code
  @#for i in reg_idx
    [name='Demand for labor - region @{i}']
    L@{i} = 0
    @#for j in reg_idx
            +om@{i}_@{j}*L@{i}_@{j}
    @#endfor
    ;
   [name='Demand for capital - region @{i}']
    K@{i} = 0
    @#for j in reg_idx
            +om@{i}_@{j}*K@{i}_@{j}
    @#endfor
    ;
  @#endfor

Which after running the dynaremacro command evaluates as (reg_idx = (1,2) here):
    [name='Demand for labor - region 1']
    L1 = 0
            +om1_1*L1_1
            +om1_2*L1_2
    ;
   [name='Demand for capital - region 1']
    K1 = 0
            +om1_1*K1_1
            +om1_2*K1_2
    ;
    [name='Demand for labor - region 2']
    L2 = 0
            +om2_1*L2_1
            +om2_2*L2_2
    ;
   [name='Demand for capital - region 2']
    K2 = 0
            +om2_1*K2_1
            +om2_2*K2_2
;

A work around would to generate a new model text file directly in julia which includes @model  begin on top.
But this could be a useful addition.

I would want to try to solve it within the @model block. let me try to come up with an intuitive syntax for your example. here is a proposal:
@model multi_country_model begin
    for c1 in [1,2]
        L(c1)[0] = for c2 in [1,2] + om(c1)(c2) * L(c1)(c2)[0] end

        K(c1)[0] = for c2 in [1,2] + om(c1)(c2) * K(c1)(c2)[0] end
    end
end

and then in the background (after it's implemented) he would translate this to:
L(1)[0] = om(1)(1) * L(1)(1)[0] + om(1)(2) * L(1)(2)[0]
K(1)[0] = om(1)(1) * K(1)(1)[0] + om(1)(2) * K(1)(2)[0]
L(2)[0] = om(2)(1) * L(2)(1)[0] + om(2)(2) * L(2)(2)[0]
K(2)[0] = om(2)(1) * K(2)(1)[0] + om(2)(2) * K(2)(2)[0]

I see that for full flexibility there is no way around for loops here. would that cover all possible use cases?
also I am not sure about what braces to use. ( is visually nice but can be confused with function calls. { makes it visually hard to read and [ makes it hard to distinguish variable timing from country/sector/... indices. any views on syntax?

Thanks for pushing this and offering a solution.
I am not quite sure about the syntax.
I am personally in flavor of {} braces. Even if they do look clunky they differentiate strongly from function call () or array index [].
Regarding your proposal.
L(idx) (or L{idx}) would translate into L(1).
I am wondering what would the variable name be down the road? Say in the irf or simulation DataFrame.
I don't think it could be L(1)?
So maybe it should translate from L(idx) to L1 ?
But I will leave it up to you as you are running the code. If the function exists, I would be already very happy.

hi Erik,
I finally took some time to implement programmatic model writing. I have a working version on the multi_country branch. Here is an example of how to use it:

@model RBC_multi_country begin
    for co in [:H, :F]
        Y{co}[0] = ((LAMBDA{co}[0] * K{co}[-4]^theta{co} * N{co}[0]^(1-theta{co}))^(-nu{co}) + sigma{co} * Z{co}[-1]^(-nu{co}))^(-1/nu{co})

        K{co}[0] = (1-delta{co})*K{co}[-1] + S{co}[0]

        X{co}[0] = for lag in (-4+1):0 phi{co} * S{co}[lag] end

        A{co}[0] = (1-eta{co}) * A{co}[-1] + N{co}[0]

        L{co}[0] = 1 - alpha{co} * N{co}[0] - (1-alpha{co})*eta{co} * A{co}[-1]

        U{co}[0] = (C{co}[0]^mu{co}*L{co}[0]^(1-mu{co}))^gamma{co}

        psi{co} * mu{co} / C{co}[0]*U{co}[0] = LGM[0]

        psi{co} * (1-mu{co}) / L{co}[0] * U{co}[0] * (-alpha{co}) = - LGM[0] * (1-theta{co}) / N{co}[0] * (LAMBDA{co}[0] * K{co}[-4]^theta{co}*N{co}[0]^(1-theta{co}))^(-nu{co})*Y{co}[0]^(1+nu{co})

        for lag in 0:(4-1)
            beta{co}^lag * LGM[lag]*phi{co}
        end +
        for lag in 1:4
            -beta{co}^lag * LGM[lag] * phi{co} * (1-delta{co})
        end = beta{co}^4 * LGM[+4] * theta{co} / K{co}[0] * (LAMBDA{co}[+4] * K{co}[0]^theta{co} * N{co}[+4]^(1-theta{co})) ^ (-nu{co})* Y{co}[+4]^(1+nu{co})

        LGM[0] = beta{co} * LGM[+1] * (1+sigma{co} * Z{co}[0]^(-nu{co}-1)*Y{co}[+1]^(1+nu{co}))

        NX{co}[0] = (Y{co}[0] - (C{co}[0] + X{co}[0] + Z{co}[0] - Z{co}[-1]))/Y{co}[0]
    end

    (LAMBDA{:H}[0]-1) = rho{:H}{:H}*(LAMBDA{:H}[-1]-1) + rho{:H}{:F}*(LAMBDA{:F}[-1]-1) + E{:H}[x]

    (LAMBDA{:F}[0]-1) = rho{:F}{:F}*(LAMBDA{:F}[-1]-1) + rho{:F}{:H}*(LAMBDA{:H}[-1]-1) + E{:F}[x]

    for co in [:H,:F] C{co}[0] + X{co}[0] + Z{co}[0] - Z{co}[-1] end = for co in [:H,:F] Y{co}[0] end
end

@parameters RBC_multi_country begin
    K[ss] = K_ss | beta
    K_ss = 10
    mu      =    0.34
    gamma   =    -1.0
    alpha   =    1
    eta     =    0.5
    theta   =    0.36
    nu      =    3
    sigma   =    0.01
    delta   =    0.025
    phi     =    1/4
    psi     =    0.5

    rho{:H}{:H} = 0.906
    rho{:F}{:F} = rho{:H}{:H}
    rho{:H}{:F} = 0.088
    rho{:F}{:H} = rho{:H}{:F}
end

any feedback is very welcome.
I am ironing out some last issues and documentation and will merge it into the next release.

Thanks a lot. I will update my code and test this.

I'll release a new version with this feature this week so you don't have to install from GitHub...

Hi Thore,
Is it possible to declare arrays within the model block? For example, instead of for co in [H, F], Countries = [H,F] and for Countries.
For now, such arrays could not be declared outside the model block, as the elements are not separately defined. When I try declaring them within the model block, I get an error.
Cheers,
Roshen

Hi roshen,
It's a limitation of julia macros that variables inside the macro don't have access to attached values.
I looked into what you are trying to do some time ago but didn't find a user friendly way of implementing it. I left it there but maybe there is a less user-friendly way: you could try write a function that writes the @model macro for you, fills it with the entries of Countries, and evaluates it.

Thanks so much for the prompt response, Thorek! I've tried the method you suggested for some other languages (e.g., for converting a Dynare mod file for gEcon). I was expecting an internal fix within Julia. Since there doesn't seem to be any, I'll try and let you know if I succeed.


remove get_schema method from Neo4jGraph class

Description: Remove get_schema method from Neo4jGraph. A property should not be named get_schema, and We can just use self.schema to get access the schema.
Tag maintainer: @baskaryan (I am sorry but the relevant maintainer are not showed in default pull request message)

tend to agree, any thoughts @tomasonjo?

LGTM

Actually, can we just port the removal of the property to https://github.com/langchain-ai/langchain/pull/10577 and I'll test memgraph tomorrow myself, so we can get it merged in.
the string schema won't be used anymore in cypher chain anyway, but we'll leave it just in case.

@DayuanJiang I've ported your PR to https://github.com/langchain-ai/langchain/pull/10577 as it contains to changes to graph schema and I have also updated the example notebooks

@tomasonjo  Thank you, I will close this PR.


Added support for Async Generators in TableClient.submit_transaction method

Fixes #21083

@annatisch You may commit directly to the branch. Thanks!


№189

I found another bug. But I don't want to waste my time describing it. Because You ignored 188 requests. That's the lamest repository and a product that I have ever seen. I hope that at least this will Wake your senses. And no need to repeat a high-level api flash!  Inherit from DisplayObject string.
And it's the least I can tell You, after weeks of wasted time. For the first time in several years I can say that the time spent in vain. I wish You to live until that time when Your product will be better than flash.

wow a flash troll. did I suddenly wake up to 2007?

I'm sorry you feel that way @acopalipsis, I try to spend what time I can on the product but I do have a full time job, life, and other side projects as well. Sometimes it is hard to put the time necessary to make this library great.
I assure you I read every bug that comes in, hopefully you will find the time to put in a proper bug.
Good Luck,
-Chad


[AutoPR datafactory/resource-manager] Update IntegrationRuntime: add new optional property for public ip feature

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

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


harbor_project_membership_user always drifts between apply runs due to changed username

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
resource "harbor_project" "purpose" {
  name                   = "my-project"
  public                 = "true"
  vulnerability_scanning = "true"
  deployment_security    = "critical"
  enable_content_trust   = "false"
  force_destroy          = false
}

resource "harbor_project_member_user" "admins" {
  for_each      = toset(["vendrell"])
  project_id    = harbor_project.purpose.id
  user_name   = each.value
  role          = "projectadmin"
}

When running terraform plan I consistently get a replace action on the membership resources, due to the username being something different than I state in the resource block:
  # module.harbor.harbor_project_member_user.admins["vendrell"] must be replaced
-/+ resource "harbor_project_member_user" "admins" {
      ~ id         = "/projects/1304/members/957" -> (known after apply)
      + member_id  = (known after apply)
      ~ user_name  = "Vendrell" -> "vendrell" # forces replacement
        # (2 unchanged attributes hidden)
    }

If I run apply and plan again, this is the output:
  # module.harbor.harbor_project_member_user.admins["vendrell"] must be replaced
-/+ resource "harbor_project_member_user" "admins" {
      ~ id         = "/projects/1304/members/957" -> (known after apply)
      + member_id  = (known after apply)
      ~ user_name  = "vendrell" -> "Vendrell" # forces replacement
        # (2 unchanged attributes hidden)
    }

The interesting bit is that it seemingly does not matter whether or not I try to normalize the value of username using lower(), upper() or title() - the username is always different and forces the resource to be replaced.
Expected behavior
There should be no changes required, as the user and membership did not change.
Additional context
We primarily use LDAP groups to manage group memberships - I opted to not use a group in this instance, because I need to assign the same collection of people to several projects as admins, but cannot do so as there is no group resource to share between configurations.
Provider version is 3.7.1, terraform version is v1.0.9.

Hi,
I don't have the issue with latest provider
I close the issue feel free to re-open it if needed


Show documentation on custom rules

I have noticed the new support for Show documentation for  pops up as a suggested correction. However, when using custom rules this uses this github repo and results in a 404 (e.g. https://github.com/PowerShell/PSScriptAnalyzer/blob/development/RuleDocumentation/Measure-PascalCase.md). Is it possible to use a custom url for this feature? This would allow us to direct the documentation at our own internal spaces.

We would need to either abuse an existing property in DiagnosticRecord or create a new property (which would require a new version of PSSA), I think the latter is the better option unless there is an unused property. After this we would also need a PR each in PowerShellEditorServices and powershell-vscode...
Feel free to submit a PR for that

It would be great to have this customization. I have been looking for customizing this url to custom one.

Perfect! Looking forward on this

If someone can brief me about the changes we expect, I can give it a try. At least the main script that needs a change.

Sorry, I'll pick this up today

Cc @rkeithhill

So I have a working solution for this, however, it might not be everyone unfortunately. As @bergmeister mentioned, in order to make this change, it involves making changes to PSES and VSCode, which in turn would probably then call for an extension to the diagnostic records here to include a custom URL, in an ideal world this is how I would it.
However, in the interest of time I opted for the solution below, maybe this will be of some use to someone else.

We (myself and my colleagues) use an internal wiki space for documentation
I have specifically named all of our internal rules to match our naming schema Verb-PrefixNoun
I have updated the CodeAction.js found in "$env:USERPROFILE.vscode\extensions\ms-vscode.powershell-2019.5.0\out\src\features\CodeActions.js"
The update is for the function showRuleDocumentation

The function already makes use if (ruleId.startsWith("PS")) -> I simply extended this logic to something similar where if the ruleId matches our Prefix we update pssaDocBaseURL to point our internal wiki (I removed it from being a Const).

Now, VSCode goes to this GitHub for all PSScriptAnalyzer rules and our Wiki for internal rules!
I know this is a little, hacky but fairly simple to implement at build time for us (we use chocolatey). Hope this helps anyone that might be interested.

Nice!

This 'working solution' is a really bad hack and I strongly recommend against using it. The ms-vscode.powershell has been a bit quiet in the last months with releases bug generally expect a release every other month. Every release will break your 'solution' because the extension will be auto-updated in the background without you noticing and replace the code with new code and the path will change as well (and so will code).
All you would've needed for a proper solution is adding a new optional property to DiagnosticRecord and making a small change in the extension to pick up this new property or just adding a setting in the extension itself...

Someone make the change to DiagnosticRecord and I'd be happy to plumb this change through PSES and the extension.

@bergmeister If this is similar to https://github.com/PowerShell/PSScriptAnalyzer/pull/1144 ? Then I can submit a PR

Yes, you'd add a property to DiagnosticRecord and then translate that property similar to how it was done in that referenced PR.

Its a year since this has been commented. Has anyone started this, seems a quick thing.

Hi, is someone working on this issue. I have also the same scenario, where I need to customize the documentation link.

@Shruti-MS No, but you could follow the above guidance and we'd be happy to accept a PR


Make seed optional

@mali-git what happens if you don't set the seed to 2? It's okay if it's a random one, right?

Codecov Report

Merging #28 into master will increase coverage by 0.68%.
The diff coverage is 77.77%.

@@            Coverage Diff             @@
##           master      #28      +/-   ##
==========================================
+ Coverage   31.33%   32.02%   +0.68%
==========================================
  Files          23       24       +1
  Lines        1436     1452      +16
==========================================
+ Hits          450      465      +15
- Misses        986      987       +1

Impacted Files
Coverage Δ

src/pykeen/run.py
22.72% <ø> (ø)
:arrow_up:

...c/pykeen/kg_embeddings_model/unstructured_model.py
26.66% <100%> (+1.24%)
:arrow_up:

src/pykeen/kg_embeddings_model/__init__.py
100% <100%> (ø)
:arrow_up:

src/pykeen/kg_embeddings_model/trans_r.py
18.75% <100%> (+1.02%)
:arrow_up:

src/pykeen/utilities/pipeline.py
24.5% <100%> (+0.74%)
:arrow_up:

src/pykeen/kg_embeddings_model/conv_e.py
14.73% <100%> (+0.9%)
:arrow_up:

src/pykeen/kg_embeddings_model/trans_d.py
16.86% <100%> (+1.01%)
:arrow_up:

...pykeen/kg_embeddings_model/structured_embedding.py
20.23% <100%> (+0.96%)
:arrow_up:

src/pykeen/hyper_parameter_optimizer/__init__.py
100% <100%> (ø)

src/pykeen/kg_embeddings_model/rescal.py
21.66% <100%> (+1.32%)
:arrow_up:

... and 7 more

Continue to review full report at Codecov.

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

Wait so when you merged the master branch, it basically squashed the changes I made...

I included the random seed configuration in the configuration layer, it will be saved in the config.json


improve stream response for http

Codecov Report
Patch coverage: 100.00% and project coverage change: +0.06 :tada:

Comparison is base (6a4e39e) 78.58% compared to head (71f001d) 78.64%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@            Coverage Diff             @@
##           master    #2564      +/-   ##
==========================================
+ Coverage   78.58%   78.64%   +0.06%
==========================================
  Files         630      627       -3
  Lines       51393    51056     -337
==========================================
- Hits        40388    40155     -233
+ Misses       9016     8930      -86
+ Partials     1989     1971      -18

Flag
Coverage Δ

go-1.15-amd64
78.64% <100.00%> (?)

go-1.17-386
?

go-1.17-amd64
?

go-1.18-386
?

go-1.18-amd64
?

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

Impacted Files
Coverage Δ

net/ghttp/ghttp_response_writer.go
100.00% <100.00%> (ø)

... and 7 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.


feat: add timeadd as an alias for dateadd

sqlglot~=21.2.0 does not support timeadd for Snowflake, this transform simply tries to convert it to DateAdd.
sqlglot v23.1.0 adds timeadd/addtime with https://github.com/tobymao/sqlglot/pull/3180/files but upgrade would require changes on other transforms like to_timestamp and ones with json extraction.

Ah it's probably best to do the upgrade of sqlglot. I try to keep it on the latest but have fallen behind.

Ah it's probably best to do the upgrade of sqlglot. I try to keep it on the latest but have fallen behind.

Might be better, on my fork I've bumped it to v22.4.0 for following changes;
https://github.com/tobymao/sqlglot/commit/c51b64fa6a437698fd8b347d98ffaf9fb543d2d5
https://github.com/tobymao/sqlglot/commit/ddab9dff663985d9473ce4b2dbe4fe266ae1bdf7
https://github.com/tobymao/sqlglot/commit/c333017fe49c0645cdaa3a75d0a7cc6a5b46dddc
I can close this PR and work on the upgrade. sqlglot is evolving in a fast pace, do you have a preferred version or the latest is ok?

That would be great, thankyou! The latest and greatest version 🙂


Catch all exceptions for get_archive and remove_container

*OSBS-7560
Signed-off-by: Robert Cerven<EMAIL_ADDRESS>Maintainers will complete the following section:

[x] Commit messages are descriptive enough
[x] "Signed-off-by:" line is present in each commit
[x] Code coverage from testing does not decrease and new code is covered
[x] JSON/YAML configuration changes are updated in the relevant schema
[x] Changes to metadata also update the documentation for the metadata
[x] Pull request includes link to an osbs-docs PR for user documentation updates

rn updated: Catch all exceptions for get_archive and remove_container


Allow overriding of existing JS dependencies like prism

Doctave comes prepackaged with a version of prism that has a subset of languages for highlighting in code blocks. If we want to change the version of prism used, all we'd have to do is edit the prism.js file. (FWIW, I was interested in YAML and BASH highlighting). I'd expect if I:

Add the custom prism.js file I wanted in docs/_include/assets
Running doctave serve should reflect the change
Running doctave build --release should reflect the change: the file should be copied to site/assets/prism.js

But neither of the above occurs.
This may be as simple as allowing any file in docs/_include/assets to be copied over at the latest possible step.
i.e., switching these two lines:
https://github.com/Doctave/doctave/blob/4531be88b1d11eb68ffc6532f54cf2cbf63f4a53/src/site_generator.rs#L51-L52

Thanks for reporting this. I'm a bit torn about this.
It doesn't sound unreasonable to be able to override the prism version, but it does feel like it's reaching a bit into the implementation details of Doctave. I'd really like to just have all language syntaxes available already so this is not a problem. The issue with that is the bundle size - each new language adds between ~0.5kb and ~6kb to the bundle, which has to be served on every request (modulo caching etc).
You can play around with the bundle here: https://prismjs.com/download.html
The currently supported languages are:
c, clike, clojure, cpp, csharp, css, diff, docker, elixir, elm, erb, erlang,
go, graphql, haskell, java, javascript, jsx, julia, lua, markup, markup-templating,
objectivec, perl, php, r, ruby, rust, sql, swift, toml

I guess there are a few options here:

Just add the 2 languages into the included bundle (adds ~6kb)

Does not handle the general case.
What about the next language that gets asked about?

Do what you suggest and allow overriding the library

I feel this goes a bit against the ethos of "batteries included" and is reaching into the implementation details of Doctave

Figure out a way where we could only include the languages that are actually used on the page (?)

This would be the most powerful solution but also the most complicated

Perhaps there's a fourth option?

Did a bit of reading and Prism does support an autoloading feature that lazily loads language definitions as needed: https://prismjs.com/plugins/autoloader/
This could be worth looking into.

I'm going to close this issue in favor of #24. I don't think Doctave should allow overriding the JS dependencies, but language support should be expanded.


Reduce excludes clutter.

mvn dependency:tree -Dverbose gives different results than mvn dependency:tree though extra jars are not included in either case.
http://maven.apache.org/plugins/maven-dependency-plugin/tree-mojo.html
For verbose option its mentioned: Whether to include omitted nodes in the serialized dependency tree. Notice this feature actually uses Maven 2 algorithm and may give wrong results when used with Maven 3.


[MRESOLVER-130] Move GlobalSyncContextFactory to a separate module

@elharo Please check documentation for typos and consistency.

@elharo Regarding comments to TrackingFileManager. I have intentionally not touched the class as a whole because I have copied it from maven-resolver-impl. I needed to remove the synchronization only because I consider it to be wrong for several reasons. A JIRA issue will follow. So let's also keep this class as-is (out of scope).


in _deposit, do not assume that the call to transfer does transfer exactly the right amount of tokens

instead, check the difference in balance

same with all other places where pool.balance is updated, like withdraw

What's the reason for that?

the reason is that we might have lpTokens that tax transactinons - i.e. tokens that when calling transfer(amount) do no necessarily transfer exactly amount of tokens


package.json: Update Handlebars (security update)

<EMAIL_ADDRESS>includes the vulnerable package<EMAIL_ADDRESS>Updating to latest<EMAIL_ADDRESS>

Thanks a lot for heads up, this change was included with a few other updates in v2.0.0

Great, thanks!