VSS   E_OUTOFMEMORY

After executing the following code loop to create and delete multiple times, after half an hour, creating vss  error = "E_OUTOFMEMORY"
you can see microsoft doc (https://learn.microsoft.com/en-us/windows/win32/api/vsbackup/nf-vsbackup-ivssbackupcomponents-initializeforbackup) about 'E_OUTOFMEMORY'
code:
package main

import ( "https://github.com/restic/restic/tree/master/internal/fs")

func main() {
	for {
		snap2(`G:\`)
	}
}

func snap2(volume string) {
       //system provider
       var provider = "b5946137-7b9f-4925-af80-51abd60b20d5"
	var vs, e = fs.NewVssSnapshot(provider, volume, 60*time.Second, func(string2 string, err error) {
		println("err=", string2, ",err=", err)
	})
	if e != nil {
		println(e.Error())
	}
	_ = vs.Delete()
}

Does that code leak VSS snapshot? What does vssadmin list shadows (https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/vssadmin-list-shadows) report?
Are you able to create new VSS snapshots after waiting for some time?
@DRON-666 Do you have an idea what might be going on here?

Does that code leak VSS snapshot? What does vssadmin list shadows (https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/vssadmin-list-shadows) report?
Are you able to create new VSS snapshots after waiting for some time?
@DRON-666 Do you have an idea what might be going on here?

I can observe in the Task Manager that the memory usage of VSSVC.exe is getting higher and higher.
However, using vssadmin to create a shadow and then delete it will not result in a significant memory usage
and. you can try my test script( this script Will not cause a significant increase in memory for VSSVC.exe)
@echo off
setlocal

:loop
    echo Creating shadow copy for volume G:...
    wmic /namespace:\\root\cimv2 path win32_shadowcopy call create Volume="G:\"
    if errorlevel 1 (
        echo Error creating shadow copy. Exiting...
        exit /b
    )

    echo Deleting all shadow copies...
    vssadmin delete shadows /all /quiet
    if errorlevel 1 (
        echo Error deleting shadow copies. Exiting...
        exit /b
    )

    echo Loop completed. Press Ctrl+C to exit.
    goto loop

endlocal

@MichaelEischer I think we are leaking all COM-objects passing through convertToVSSAsync and one for each timeout in callAsyncFunctionAndWait.
In other languages all this Add/Release stuff is automatic, but in go all is manual and unfortunately not testable.
I can't reproduce E_OUTOFMEMORY but after 3 hours of testing more than 3Gb leaked.

@fgma Why do we even need convertToVSSAsync? My understanding is that all callers are already pass IVSSAsync to it.

@zhuxiujia Please test this branch. I use this testing code instead of you.
In my tests, after ~3000 snapshots, memory consumption for VSSVC.exe was less than 10Mb, and for main.exe ~25Mb.

wmic /namespace:\\root\cimv2 path win32_shadowcopy call create Volume="G:\"

n my tests（wmic /namespace:\\root\cimv2 path win32_shadowcopy call create Volume="G:\"）, after ~3000 snapshots, memory consumption for VSSVC.exe was on 2MB-3MB(Floating up and down, and no longer growing)。
I can think your code is helpful, but it hasn't solved the problem。

@zhuxiujia Please test this branch. I use this testing code instead of yours.
In my tests, after ~3000 snapshots, memory consumption for VSSVC.exe was less than 10Mb, and for main.exe ~25Mb.

my tests（wmic /namespace:\\root\cimv2 path win32_shadowcopy call create Volume="G:\"）, after ~3000 snapshots, memory consumption for VSSVC.exe was on 2MB-3MB(Floating up and down, and no longer growing)。
I can think your code is helpful, but it hasn't solved the problem。

@DRON-666 Can you turn the VSS code fixes into a PR? You're definitely right about the leaked objects from the (redundant) QueryInterface calls. Those fixes are relevant even if there's still another problem hidden somewhere.

@MichaelEischer Do you plan to include it in 0.17 or there is no need to rush?

@DRON-666  The object leak has existed for quite a few releases by now, so I don't think there's a need to rush.


Sorting

This PR implements Numpy array sorting and Python list sorting using quicksort.
The timsort implementation is included as an addition to the test suite.
This implementation is between 1.5x and 2.5x slower than Numpy's, regardless of the array size. Part of it seems to be due to LLVM not optimizing away tests for negative indexes.

I think we should put a warning in the docs about the performance being lower than Numpy sort.

We don't really have a policy for doc warnings yet, but if we start warning about such differences I'm afraid the docs will have a lot of red in them. What do you think?
(actually I think it may be more important to document the possible O(n**2) worst case :-))

In this case, I think it a warning in the doc is warranted since we know our implementation is currently slower than Numpy's.  We are providing it as a convenience for use inside a larger function, and hopefully we can get LLVM to generate faster code in the future.
If a user's reasonable expectation is going to deviate from reality, we probably want a place to put those clarifying notes.  Either inline in the docs themselves, or on their own page of "limitations" that we can link to from various points in the docs.

This needs a remerge with master now.

Ok, I've merged and added the performance warnings.


:house: Home title style

:rocket: deployed to http://profiles-pr-28.dev.c2s.nhschoices.net

:rocket: deployed to http://profiles-pr-28.dev.c2s.nhschoices.net


🚀 RELEASE: 0.3.1

This PR sets up jupyterbook-latex==0.3.1 as a minor maintenance release for increase flexibility in version pins on dependencies

@chrisjsewell @AakashGfude I have gone ahead and merged this to help with the jupyter-book release.


MAINT: Only calc position values once per packet.

Instead of calculating the position values for each stat result, e.g.
gross_exposure, net_liquidity etc.; get the positions upfront and then
calculate the period and position stats in order, passing each value
explicitly to the ones that follow it in the dependency chain.
e.g. the gross_value depends on the long_value and the short_value,
which called the position_values property for calculating both the
long_value and the short_value.
Removing the repeated calls to position_values (and
position_exposures) removes the need for the caching the last sale
prices and position amounts in separate vectors, since it is inexpensive
enough to read those values off of the positions dictionary held in the
position tracker.
This patch gives a small gain to ~500 sized portfolios, but the main
intent is to clear the path to not storing last_sale_prices on the
position objects at all. Removing all of the caching layer in this class
makes that change easier to apply. Removing the extra calls to
position_values also made this class easier to step through/reason about
when splicing in the new last sale price access, as well.

@ssanderson this is the PR I mentioned to you earlier today.
@jbredeche you may be a good candidate for reviewing this, as well, since it is based on some work contained in the lazy-mainline branch.

Ran this on our internal performance harness, and the change had some slight wins, but not really outside of variance (though was seeing some >3-4% gains for universes that held positions for universes sized ~500). Having no perf regression would be the perf goal here, as the main impetus behind this patch is reducing the number of calculations for clarity and ease of changing how the data is sourced for the position values.


Reusing parser modifies previous results

Installed via PyPI
from cysimdjson import JSONParser
parser = JSONParser()
result = parser.parse(b'{"hello": "world"}')
print(result['hello'])  # "world"
new_result = parser.parse(b'{"hello": "universe"}')
print(result['hello'])  # "universe"

This only happens when reusing a previous parser instance. I'm not sure whether this is by design, but if it is, it should probably be explicitly documented to avoid confusion.
It also becomes especially iffy when mixing different types:
result = parser.parse(b'{"hello": "world"}')
print(type(result))  # JSONObject
print(list(result.keys()))  # ['hello']
new_result = parser.parse(b'[1,2,3]')
print(type(result))  # JSONObject
print(type(new_result))  # JSONArray
print(list(result.keys()))  # ['hello', 'hello', 'hello']

So if it is by design, it might be worthwhile to somehow invalidate the previous reference when a new document is parsed.

Thanks for reporting, we will look at that.

Ok, after some digging, this is actually correct behaviour - it is linked with the SIMDJSON requirement for the lifecycle of the document, see the remark at https://simdjson.org/api/0.9.1/classsimdjson_1_1dom_1_1parser.html#ab3e5bbb1974a1932aead90ad63883a23
I will try to provide some kind of indication of this as per your suggestion.

Note that the parser holds the allocated memory. By reusing the parser from document to document, we reuse the allocated memory. The net result is to avoid memory reallocation, an expensive process. On some systems, it is more expensive to allocate memory than to parse JSON !

You can see one approach to stopping this in pysimdjson, https://github.com/TkTech/pysimdjson/blob/master/simdjson/csimdjson.pyx#L437. It's likely not our final fix, since it's a bit buggy on pypy whose garbage collector might wait a long, long time to cleanup things pointing into the Parser's document even if it's been explicitly deleted. In @ROpdebee's example above, it would have raised a RuntimeError instead of a potential segfault.


feat: update to drawio-desktop 21.8.2

:tada: This PR is included in version 1.15.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Fixed for event user interface

Fixed for #44

Coverage decreased (-0.1%) to 24.25% when pulling 56d6e26bdcc7a238638fdfc7907d4cad88e4b094 on issue-44 into 5f23d48d165ef18d937d2fd7cc2fc89adbacf4db on develop.


GUI: display a message when not enough coins are available to fund a transaction

User cannot pass anymore the choose recipients step if the spend amount is superior or egal of the available amount
closed by #279


transport_failure_callback Bug

tl;dr: transport_failure_callback is not called on 4xx or 5xx errors and should have a failure reason

The idea behind transport_failure_callback is just fantastic. It means that there is no longer a single point of failure for reporting events to Sentry. Yet there is a bug with its implementation and I feel that it is missing a key feature.

Bug
According to the documentation, transport_failure_callback is called "If the transport fails to send an event to Sentry for any reason (either the Sentry server has returned a 4XX or 5XX response)." Yet it would appear that the callback is only called when Faraday#post raises an exception (or if ClientState#should_try? is false); thus failed_send and (more importantly) transport_failure_callback is not called when Sentry servers return with 4xx or 5xx status codes; the source code in question:
      begin
        transport.send_event(generate_auth_header, encoded_data,
                       :content_type => content_type)
        successful_send
      rescue => e
        failed_send(e, event)    # this is called _only_ if an error is raised by `Faraday#post`
        return
      end

I double-checked this hypothesis:

by writing an little script that uses Faraday when contacting a server that returns 200/400/500 codes; in all cases, Faraday returns a response without raising an exception

script: https://gist.github.com/aryeh-looker/515632a6da7661df908a4ddd77186402
example script run (would expect the word "raised error" instead of 400, 500 in the script's output): https://gist.github.com/aryeh-looker/277a196269e9cfc8755f8315f29f39e2

by using Sentry under debugger control with a DSN that contacts a server that always returns a 500 code; in that case, transport.send_event does not raise an exception

Key Feature
It would be ideal if transport_failure_callback were called with the raven event and the reason why the Sentry server was not reachable or contacted; for example: 400 status, server is completely unreachable, raven client is in a failure state, the secret key is missing from the DSN, etc.

It should be possible to have unit tests for this by using something like Webmock.

@aryeh-looker What adapter are you using for Faraday? The default is Net/HTTP.
I don't think Faraday is supposed to work the way you describe. I'm working on a test case.

Aha! The file linked is an optional middleware. I'll have this fixed in a jiffy.


Wildcard doesn't work at the beginning of -path

$ touch foo
$ find -path '*foo'
./foo
$ ./toybox find -path '*foo'
$

Looks like FNM_PATHNAME is being set?

commit fbedc9dd74aeb0331202f9e503316960e32fa879 fixed this.
@landley to close...


Track if a DiscoveredPackage is for the From-side, the To-side or both

I want to know if a DiscoveredPackage is for the From-side, the To-side or both.
A package could come from scanning manifests, or from matching and it may be deployed or not deployed. We need to track explicitly if a package is present on the To/From/both as this is then an important filter in the UI and for reporting SBOMs and attribution

The simplest solution is probably to add a tag field as it is implemented on the resource model.


Warnings from Felix due to lack of Apply for KDD

2017-05-02 14:56:27.985 [WARNING][138] k8s.go 335: Attempt to 'Apply' using kubernetes backend is not supported.
2017-05-02 14:56:27.985 [WARNING][138] felix.go 676: Failed to write status to datastore: operation Apply is not supported on StatusReport(hostname=gke-smc4-default-pool-d435533e-v9hb)

Felix defaults to generating process status reports, could we make KDD return a global setting to disable that or simply ignore StatusReport writes?

I've opened #411 which ignores status reports in the KDD.


Device is already configured

Hello,
I got an issue lately where my switches (p100) where no longer available. They were grayed out on home assistant but still working on the official tapo application.
So i thought about deleting the integrations before adding them again.
I deleted them one by one and tried adding a device again, but i get this message : Device is already configured
I wonder where are the config files where this is declared so i can delete them from the source.
I also wonder if the solution is not to remove the tapo integration completely and install it again ? How should i do that ?
Thanks for your help

I have the exact same issue. I have two p100 smart plugs and although they both work through the tapo app only one can be added to HA. When I try to add the second one a message "the device already exists" appears.
Any help would be appreciated
Thanks

"the device already exists" is issued when there is two devices with same MAC address, please check that you adding the right devices. Additionally, check the configuration.yml and be sure there is not the same device that are you trying to add with UI or viceversa.

My router correctly depicts that the two smart plugs (with different MAC addresses) have different IPs. My cinfiguration.yaml is empty . Where is the information of the added devices kept so I can check against which device the integration checks the one I am trying to add?

@psampatakos @ChoppyThing I know this has been a while but did you ever manage to resolve this? I have the same issue and I was just about to open another ticket when I noticed this one was names almost identically. I had an old plug previously monitoring Elec usage for my Fridge. I have since moved it to the lounge for the TV but in the meantime it hadn't been used for several months so I removed it from the Tapo Integration as it was constantly trying to poll it and it was never connected.
When I am trying to add the device now I get the "device already configured" message. I have tried giving it a different IP but as above it appears it uses its MAC address. There is nothing else added to my router with that MAC, there is also nothing manually configured with yaml as it was all done with the GUI.
I have looked through the custom components directory but there doesnt seem anything obvious to delete. I have reused plugs and gave them new names which has required adding them again to function properly but never had this error before.


User presence

Continuation from https://github.com/jonashagstedt/swampdragon/issues/70

There are many alternatives to doing this.
user manager could indeed become a class that is replaceable.
I will consider this.
You can also write your own notification backend:
https://github.com/jonashagstedt/swampdragon-notifications/tree/master/swampdragon_notifications/backends
if you need to do anything specific there.
If it was rewritten to be a class there would have to be yet another setting to decide which user manager class to use.
There is already logic for handling this based on testing so it wouldn't be a big leap of course.
A lot to consider.
I will look in to this more when I get some time (hoping to get 0.4.3 out the door soon-ish so people finally get DRF serializer support)

Looking forward to DRF serializers!
This is my solution for now.
Define my own user manager that is a copy of yours
https://github.com/bufke/chat-experiment/tree/master/chatroom/connection
Override the router because it uses your user manager and not mine
https://github.com/bufke/chat-experiment/blob/master/chatroom/routers.py#L55
Right now all this does is provide a hook to run print statements proving I can extend the user manager. But from here it should be possible to extend it and track user presence as I want. If I was lazy (I am) I could set a postgres field is_online and be done. A naive solution might not be bad until I have a reason to scale it.
I agree adding yet another setting isn't ideal. If I think of a cleaner solution I'll let you know. All these overrides are doable but not ideal as I'd have to manually merge upstream changes into them.
If I was scaling - would I need to ensure only one instance of swampdragon with periodic_callback is running?

I'll have a poke at this as soon as I am at a desk with a proper connection etc. (will be a few days).
The periodic_callback is the one that does the cleaning up of online users who are no longer online?
If that's the case then theoretically you only need one, but it's not an expensive operation as such.
I mean if you have tens of thousands of users online then it would probably need optimising but then the entire architecture should be reviewed, but for a few hundred I don't think it's noticeable


pubsub: migrate to v1

Fixes #699
It looks like the only change was enabling multiple ack IDs to be passed to subscriptions.modifyAckDeadline: https://cloud.google.com/pubsub/reference/rest/v1/projects.subscriptions/modifyAckDeadline

@tmatsuo did I miss anything in the migration from v1beta2 to v1?
// @dhermes

Thanks for the cc!

Yes, that's the only change. Good eye :)

Woo! Thanks for the review!


Implement more protocol messages

I've added more response parsings:

F message
N message
A message

More abstract device handling, add todict method with more readable output as dict.

Hi, thanks for your contribution! could you please fix the failing tests and add tests for the new code?
Cheers,
David


cssnext version

I've created a branch that uses cssnext syntax.  I noticed there was at one time a postcss version of Milligram, and I can see a good argument for avoiding Postcss specifically, since the Sass or Less versions could be processed by someones Postcss build process, but I like the idea of having a version written with cssnext syntax, since it's potentially future css.
In the build I only used one additional Postcss plugin, postcss-imports, just so the builds would be concatenated.
Here it is if you want to bring it into the mix.  I'd be happy to maintain it.

Hi @steven-klein
Sounds good. I appreciate your interest. I create the repository with what name?
milligram-cssnext
milligram-postcss
milligram-???

I went with milligram-cssnext since the other repositories were named for the syntax that is being used.

Hi @steven-klein check it https://github.com/milligram/milligram-cssnext
Let me know if there is anything else I can help. It will be a pleasure to participate in this project

@steven-klein Nice job!!
https://github.com/milligram/milligram-cssnext/pull/1


stereo mode persists even when VR mode is exited (in native WebVR on Chrome for Android)

reproduced in Chrome 65 on an Android Pixel 2 device:

ensure that the WebVR flag is Enabled from chrome://flags#enable-webvr
using Chrome on Android (current release: 65), navigate to the demo scene at https://mozilla.github.io/unity-webvr-export/ (or your localhost server)
click the VR-icon button to enter VR mode.
put your mobile phone in your Daydream headset viewer.
move your head around to view the scene in VR mode.
take the headset off.
press the × icon in the corner to close/exit Daydream's Google VR mode.
notice the screen is split in half, still in stereo mode (should be reverted to mono mode).
notice, even after subsequent clicks of the VR-icon button, it is impossible to revert to mono mode. (a page refresh obviously does, but nothing else appears to.)

Also happens with Oculus Go.

fixed with:
https://github.com/mozilla/unity-webvr-export/commit/d121593fe721a7d3ef52e51c1cc364ea54a172d2
Issue was that on mobile, the vrdisplaydeactivate events were not being fired.  In any case, the enter/exit VR logic has been changed up and it's now working properly: https://github.com/mozilla/unity-webvr-export/blob/master/Assets/WebGLTemplates/WebVR/webvr.js#L304-L314


1.28.16 doesn't work in Chrome

Current Chrome Browser (Version 44.0.2403.155 m) in Windows 8.
<!DOCTYPE html>
<html lang="en">
<head>
	<meta charset="utf-8" />
	<title></title>
    <script
        id='sap-ui-bootstrap'
        type='text/javascript'
        src='https://openui5.hana.ondemand.com/resources/sap-ui-core.js'>
    </script>
</head>
<body>
</body>
</html>

Produces error
Uncaught TypeError: Cannot read property 'length' of null [sap-ui-core.js:144]

on page load.
The same works in Firefox and IE.

Hi Blumi,
I found it also in online CDN https://openui5.hana.ondemand.com/1.28.15/resources/sap-ui-core.js
Maybe a problem with the online libs copy or with time lag access.
If you try with local downloaded resource version might work fine.
Regards,
Alberto Arce

That's a known issue and we are already working on it.
There was a fix or improvement in the area of the ThemeCheck (check whether the CSS for the current theme has been applied already) which unfortunately uncovered another (real) error in the theme check (also related to cross origin resource access).

Will be fixed via 53343145ff57c225f438ee49761c12a9aeacb4ad (master), f4c875df7f8b10ae7b4a3b970ad810ea09a7cb92 (rel-1.30) and 5cf9f91f7c6c900d99a55b29fea901618ee37448 (rel-1.28).


Fix a problem with new lumilist format

@mmascher, Marco, do you need a new tag with this patch?

@amaltaro, did we see any problem with this case. I assume it returns "string" format in some cases? I am asking whether we should create wmagent branch patch for this.

I think this has to do with how CRAB is constructing them that the lumi numbers are not guaranteed to be integers, probably because the lumi numbers are now dict keys.
What I find interesting is that this code works with the dict of events/lumi now too. I never envisioned that usage. :-)

Nope, I haven't spotted any issues with LumiList. Even if it didn't cause a real code execution problem, I would expect problems in the final outcome, but there where none as well.


offlineFallback feature request in workbox-build

Library Affected:
workbox-build
Browser & Platform:
all
Issue or Feature Request Description:
offlineFallback(); from workbox-recipes is a straightforward solution , for simplicity, which assumes offline.html located in root to cache in workbox-offline-fallback cache storage.
In workbox-build generateSW, offline.html needs to be precached first, and then we have to add these extra lines  precacheFallback: {fallbackURL: 'offline.html'} into runtimeCaching in generateSW mode.
Offline page only
offlineFallback: 'true' or 'false' (false as default value) would be as sophisticated option as skipWaiting, navigationPreload and clientsClaim, for instance.
Even though runtimeCaching and offlineFallback(); recipe are hand in hand just like runtimeCaching and navigationPreload, hope there is no any particular reason of why precache manifest is prefarable to offline fallback.

Hi there,
Workbox is moving to a new engineering team within Google. As part of this move, we're declaring a partial bug bankruptcy to allow the new team to start fresh. We realize this isn't optimal, but realistically, this is the only way we see it working. For transparency, here're the criteria we applied:

For PRs, we closed everything that doesn't target the current v7 branch.
For Issues, we closed everything that was created before 2024.

Thanks, and we hope for your understanding!
The Workbox team


feat(reactor): support for destroying SPDK threads

Reactors now remove and destroy exited SPDK threads. A check for long SPDK poll was added.
Signed-off-by: Dmitry Savitskiy<EMAIL_ADDRESS>

bors try

bors try

bors merge


Unable to sign up with Federation

I want to login for fb and g+ for userpool, i am able to so with cognito auth but i need to do it with congito identity provider. I have manage to do it in android webview i have access token and id token but was unable to pass it cognito user pool identity.
Need a sample like ios to integrated third party sign up like this. Please help
https://github.com/awslabs/aws-sdk-ios-samples/tree/master/CognitoAuth-Sample

Hi @developerboi ,
Are you trying to federate the userpool token with Cognito Identity service to get access to an identity id and aws credentials?
If so, the key that you would use in the logins may for Cognito Identity is:
String.format("cognito-idp.%s.amazonaws.com/%s", region.getName(), poolId);

Thanks @minbi, for replying. I am trying to this. It would be nice if you can help a bit.
https://stackoverflow.com/questions/51185577/authenticate-social-identity-federation-user-to-aws-userpool-android

Hi @minbi @kvasukib, thankyou for responding to my query.
I have to implement cognito in both android and ios. As i was going through the projects i find much difference in ios and android implementation.
In iOS, i can add IdentityProvider which takes me directly to identity login page for example facebook. If i set IdentityProvider as Facebook, it will take me directly to facebook authenticate and set session in sdk.
https://github.com/awslabs/aws-sdk-ios-samples/tree/master/CognitoAuth-Sample
But in android project i cannot set Identity directly, I cannot find any identity method exposed, I have to first navigate user to aws hosted UI (which i dont want) and after clicking facebook, it take me to facebook. It then authenticate my user.
https://github.com/awslabs/aws-sdk-android-samples/tree/master/AmazonCognitoAuthDemo

Why android and ios implementation are different? Why there is no identityProvider in Auth Builder android or am i missing anything here?

When i add both below mention libraries, my project is not compiling. It is showing Dex Error. implementation ('com.amazonaws:aws-android-sdk-cognitoauth:2.6.8@aar') { transitive = true} implementation 'com.amazonaws:aws-android-sdk-cognitoidentityprovider:2.6.8'

I am using both username and password registration flow and social sign up. username and password flow work seamless with cognitoidentityprovider. But for social sign up I need to authenticate/sign up my facebook user in aws and then update its user attributes.
Auth.getCurrentUser() does not have update user attributes methods. Thats why i needed to use cognitoidentityprovider library.
It would be very helpful if you can provide some assistance on this. I have been stuck on this for days.

We will investigate and see if we can provide parity between the two platforms. Thank you for bringing it to our attention.
I see that the stack include onSuccess callback and then a getSession. Is the getSession causing the error?

@minbi

Yes, getSession was causing the error. But i was able resolve it. I invalidate cache, clean and build the project, it worked fine then. I believe it was due the the different version of libraries i had included in project before.

implementation ('com.amazonaws:aws-android-sdk-cognitoauth:2.6.18@aar') { transitive = true} implementation 'com.amazonaws:aws-android-sdk-cognitoidentityprovider:2.6.24'

Why android and ios implementation are different? Why there is no identityProvider in Auth Builder android or am i missing anything here?

PR https://github.com/aws/aws-sdk-android/pull/495 addresses this issue. I will update this thread once the changes are released.

@kvasukib , is there an ETA for when a version with the fix will be available?

@developerboi, one workaround that I was able to implement was to setup a another app client under the same user pool. For this newly created app client, only select a single provider checkbox for "Enabled Identity Providers". This way, cognito will directly take you to the provider's login page. If you have multiple identity providers, you could set up a different app client for each provider but with only that identity provider enabled.

We have released version 2.6.28 of the SDK. Please see if it fixes this issue.


Get Network Summary Statistics

Run network_summary.sh when we have an available CPU partition

I assume we can close this, @dakota0064 ?


Task 489-492: mwsc Dataset

Reviews: https://github.com/swarooprm/CSE576HW/pull/7

Thanks!
@Maitreyapatel wondering if you can review this PR?

Yeah, sure I will review them.

Everything looks good to me. Just few minor suggestions for Task489:

Coreference definition is long so, can you first explain the task clearly and then further expand on coreference (like you did to another task files)? For example, you can keep following instruction before explaining coreference resolution. "Construct a question in such a way that (i) it is unambiguous, (ii) its answer is unique."
Also, you can remove "Sentence:" from each examples and instances as there is no other information apart from the simple text as input.

@NSVPC, can you address the comments above so that we can go ahead with merging.

Two suggestions; after addressing them, feel free to merge.


Bug (tracer): decorated class methods cannot access this

Bug description
All three existing utilities (Logger, Tracer, Metrics) provide method decorators that customers can use to decorate a Lambda class in AWS Lambda. Decorators are an experimental feature in TypeScript and at the time of writing the only way of using them is to use Classes.
Here's a generic example of how customers are expected to use the Powertools decorators:
import { Tracer } from '@aws-lambda-powertools/tracer';
import { LambdaInterface } from '@aws-lambda-powertools/commons';

const tracer = new Tracer({ serviceName: 'serverlessAirline' });

class Lambda implements LambdaInterface {
    // Decorate your handler class method
    @tracer.captureLambdaHandler()
    public async handler(_event: any, _context: any): Promise<void> {
        /* ... */
    }
}

export const handlerClass = new Lambda();
export const handler = handlerClass.handler;

Every time the function is invoked, the Lambda service will call the exported handler, which is now decorated. While the example above shows a decorator that belongs to Tracer, what discussed below affects also the other two utilities as they all use a similar implementation.
According to the TypeScript documentation, a method decorator has the following signature/type annotation:
type MethodDecorator = <T>(
  target: Object,
  propertyKey: string | symbol,
  descriptor: TypedPropertyDescriptor<T>
) => TypedPropertyDescriptor<T> | void;

The parameters are:

target: can be either the constructor function of the class for a static member, or the prototype of the class for an instance member (in most of the cases that interest this discussion & the usage that we recommend, the latter applies).
propertyKey: name of the property (e.g. handler in the example above)
descriptor: property descriptor for the member

Let us now take a simplified & stripped down version of the current implementation seen across Powertools:
class DecoratorUtilClass {
  public decorate() {
    return function (
      target: any,
      propertyKey: string,
      descriptor: PropertyDescriptor
    ) {
      const originalMethod = descriptor.value;

      descriptor.value = (...args: any[]) => {
        // Do something before
        const result = originalMethod.call(target, args);
        // Do something after

        return result;
      };

      return descriptor;
    };
  }
}

The above would be used as follows:
const myUtilClass = new DecoratorUtilClass();

class Lambda implements LambdaInterface {
    // Decorate your handler class method
    @ myUtilClass.decorate()
    public async handler(_event: any, _context: any): Promise<void> {
        /* ... */
    }
}

export const handlerClass = new Lambda();
export const handler = handlerClass.handler;

The interesting bits of the implementation above are:

We save a reference of the original method being decorated const originalMethod = descriptor.value; [1]
We then reassign a new value to the descriptor to a custom function that:

Performs some actions before decorated method
Calls the decorated method by passing back the target as first parameter, hence returning the initial this (aka the decorated Class) (more on this in the "Possible solution" section)
Performs some actions after the decorated method has returned

Returns the descriptor with a new value (thus decorating it)

The issue with this implementation is that the current implementation prevents customers from accessing all attributes from the decorated class. This is because the implementation is using an () => {} arrow function and the incorrect value of this is being passed back down.
Additionally, there's another caveat that was ignored until now which is that when exporting the handler at the end of the file:
export const handlerClass = new Lambda();
export const handler = handlerClass.handler;

Customers actually should bind() the class back to the handler so that when used and called later it will have access to the correct value of this.
export const handlerClass = new Lambda();
export const handler = handlerClass.handler.bind(handlerClass);

[1] This is mostly harmless but the line const originalMethod = descriptor.value; is potentially useless. The reason why I say this is that description.value evaluates to undefined all the time. This happens because we most probably misunderstood the order of evaluation of a decorator (see "Order of Evaluation" section of this page). That section of the code is always evaluated when the utility is instantiated for the first time. In the context of Lambda, this means during the execution environment's initialisation (aka during cold start).
Further readings

https://blog.10pines.com/2019/07/23/writing-object-oriented-typescript-code-for-aws-lambda/
https://saul-mirone.github.io/a-complete-guide-to-typescript-decorator/

Expected Behavior
Customers should potentially be able to decorate a Class method and then still be able to access both methods and attributes of the decorated class after the decoration has happened.
Current Behavior
Depending on the implementation & execution environment the behaviour varies (see possible solutions below).
Possible Solution
There are a few changes to the decorator implementation that essentially boil down to switching to a function() {} (instead of an () => {}  arrow fn) and then passing the correct value for this:
class DecoratorUtilClass {
  public decorate() {
    return function (
      target: any,
      propertyKey: string,
      descriptor: PropertyDescriptor
    ) {
      const originalMethod = descriptor.value;

      // We save this reference so we can call other methods on the DecoratorUtilClass
      const tracerRef = this;

      // We change the function to a regular function instead of an arrow fn
      descriptor.value = (function (this: Handler, ...args: any[]) {

        // We save the reference to the decorated fn/handler (in the actual implementation this is needed)
        const handlerRef: Handler = this;

        // Do something before

        // We pass the handlerRef when calling/applying
        const result = originalMethod.call(handlerRef, args);
        // Do something after

        return result;
      };

      return descriptor;
    };
  }
}

This work is being done in #1055
Steps to Reproduce
import { Tracer } from '@aws-lambda-powertools/tracer';
import { LambdaInterface } from '@aws-lambda-powertools/commons';

const tracer = new Tracer({ serviceName: 'serverlessAirline' });

class Lambda implements LambdaInterface {
    myAttribute: string = "someValue";

    @tracer.captureLambdaHandler()
    public async handler(_event: any, _context: any): Promise<void> {
        /* ... */
        console.log(this.otherMethod);
    }

    public async otherMethod () {
      return this.myAttribute;
    }
}

export const handlerClass = new Lambda();
export const handler = handlerClass.handler;

Environment

Powertools version used: v1.1.0
Packaging format (Layers, npm): all
AWS Lambda function runtime: all
Debugging logs: N/A

Related issues, RFCs
#1026

@dreamorosi Thanks for your help fixing this issue so far.

Released in v1.1.1


Avoid copying data when creating MLSPlaintextTBS

Make the field serialized_context_option a reference

This has been fixed in #293.

This has been fixed in #293.


Transaction failed：    WalletConnect Transaction Error: No matching key with tag: {tag}

When I sent a call to smart  contract, the transaction sometimes return failed with error:
WalletConnect Transaction Error: No matching key with tag: {tag}

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
sometimes occure, sometimes success
Expected behavior
the transaction success
Environment

OS: [Android]
Unity version [e.g. 2021.3.5f1]
Package name and version [e.g. WalletConnectUnity Modal v1.1.0]

Is this happening in Unity Editor or on a player like Android, iOS, Windows?
Android and Editor both
Wallets used for testing
Metamask
Additional context
Maybe because of the VPN?

Thank you, @Dejavu0709! I was able to reproduce the issue, and I will try to release a fix this week or next.

Thank you, @Dejavu0709! I was able to reproduce the issue, and I will try to release a fix this week or next.

thanks my hero, expecting for your fix.

Fixed in WalletConnectUnity Modal v1.1.2


[Fix] BoxMatcher fails when target has no ground truth data.

Description
When the input target is of shape [batch_size x 0 x 5] BoxMatcher throws exception in the following line:
https://github.com/WongKinYiu/YOLO/blob/8228669808a626fc5f9c233fdb35550b5e041fae/yolo/utils/bounding_box_utils.py#L221
The target_matrix here had the shape [batch_size, 0, 8400].
Closes #87.
Changes:

BoxMatcher.__call__() returns zeroed out "anchor matched target" Tensor of shape [batch x anchors x (class + 4)] and valid_mask.
Docstrings of BoxMatcher.__call__() updated.

Type of Change

[x] Bug fix (non-breaking change which fixes an issue)

Checklist:

[x] The code follows the Python style guide.
[x] Code and files are well organized.
[x] All tests pass.
[ ] New code is covered by tests.
[x] The pull request is directed to the corresponding topic branch.

Licensing:
By submitting this pull request, I confirm that:

[x] My contribution is made under the MIT License.
[x] I have not included any code from questionable or non-compliant sources (GPL, AGPL, ... etc).
[x] I understand that all contributions to this repository must comply with the MIT License, and I promise that my contributions do not violate this license.
[x] I have not used any code or content from sources that conflict with the MIT License or are otherwise legally questionable.

Future Considerations
The variable names can be made better. Names like grid_mask, valid_mask, target_matrix, unique_indices can be made more descriptive.
Docstrings can be improved. The practice of immediately appending the size information after the argument name, is maybe causing problems. When hovering over function names in IDE, the help texts appear broken.
Instead of target_matrix [batch x targets x anchors]: The suitability for each targets-anchors
please consider something like: target_matrix: Represents the suitability for each target-anchor pair. Tensor of size [batch x targets x anchors].

Is this project still being maintained by the original authors? I see you've been busy, @Abdul-Mukit.

This is solving the issue! Can we merge this?

Is this project still being maintained by the original authors? I see you've been busy, @Abdul-Mukit.

I’m still responsible for maintaining this repo. Apologies for being busy last month, but moving forward, this repo will be maintained more frequently.
Henry Tsui

Thank you, @Abdul-Mukit , for your contribution and @vlaminckaxel  for the review! I'm looking for a more graceful solution, for example, avoiding this in the dataloader or fixing it without an if condition. However, I will merge this PR now.
I strongly suggest pushing to the corresponding branch, which is the TRAIN branch.
Best regards,
Henry Tsui


feat: add utkuozdemir/pv-migrate

utkuozdemir/pv-migrate: CLI tool to easily migrate Kubernetes persistent volumes
$ aqua g -i utkuozdemir/pv-migrate

How to confirm if this package works well
Reviewers aren't necessarily familiar with this package, so please describe how to confirm if this package works well.
Please confirm if this package works well yourself as much as possible.
Command and output
$ pv-migrate --help
A command-line utility to migrate data from one Kubernetes PersistentVolumeClaim to another

Usage:
  pv-migrate [command]

Available Commands:
  completion  Generate completion script
  help        Help about any command
  migrate     Migrate data from one Kubernetes PersistentVolumeClaim to another

Flags:
  -h, --help                help for pv-migrate
      --log-format string   log format, must be one of: json, fancy (default "fancy")
      --log-level string    log level, must be one of: trace, debug, info, warn, error, fatal, panic (default "info")
  -v, --version             version for pv-migrate

Use "pv-migrate [command] --help" for more information about a command.

Reference

Usage

https://github.com/utkuozdemir/pv-migrate/blob/master/USAGE.md

Thank you always!

🤔
It is caused by different assets name and assets name in checksums.txt?
ERRO[0000] Checksum isn't found in a checksum file. Checksum file content:
46c38c1d528d81284f2e265c8f0a3f89d44a9c1f25942371e6904e8303f4c109  pv-migrate_v0.5.4_darwin_x86_64.tar.gz
a7e10a24d83462f5159d1bdce5ba10c441f0325d5f64dc4025b2c4011f8a01f6  pv-migrate_v0.5.4_windows_x86_64.zip
c658904cb89bb0421edf4d6fce9e0a900a44a95a75565ae096948550900412d5  pv-migrate_v0.5.4_linux_x86_64.tar.gz  aqua_version=2.8.0 checksum_file_format= env=linux/amd64 package_name=utkuozdemir/pv-migrate package_version=v0.5.4 program=aqua registry=standard
ERRO[0000] install the package                           aqua_version=2.8.0 asset_name=pv-migrate_0.5.4_linux_x86_64.tar.gz env=linux/amd64 error="no checksum is found" package_name=utkuozdemir/pv-migrate package_version=v0.5.4 program=aqua registry=standard

v0.5.4's checksums file contains v prefix.
$ cat checksums.txt
46c38c1d528d81284f2e265c8f0a3f89d44a9c1f25942371e6904e8303f4c109  pv-migrate_v0.5.4_darwin_x86_64.tar.gz
a7e10a24d83462f5159d1bdce5ba10c441f0325d5f64dc4025b2c4011f8a01f6  pv-migrate_v0.5.4_windows_x86_64.zip
c658904cb89bb0421edf4d6fce9e0a900a44a95a75565ae096948550900412d5  pv-migrate_v0.5.4_linux_x86_64.tar.gz

In that case, let's disable checksum verification in v0.5.4.

Thank you for your suggestion. I will fix it.

Thanks!

Released. https://github.com/aquaproj/aqua-registry/releases/tag/v4.9.0


Can't get stacktrace

Tried boost but b2 only builds noop on gcc 13.2.  Runs but outputs very little other than blanks, though debug panel shows a lot of detail in impl, a hidden variable.
Haven't tried  in C++23; that output didn't look much better.

I think I saw "Get-PSStack" somewhere.

Would close but I need to review if the output is showing up in Show-Error.

One thing is uncaught errors, especially syntax, don't give the line they occurred on, but rather the last line that called the code that contained the error.  I probably need to catch everything generically and then use Get-PSCallStack.

Works


Current master is completely busted

Tested with https://media.xiph.org/video/derf/y4m/coastguard_qcif.y4m
Second frame from the decoder:

Second frame reconstruction from the encoder:

Frame 289 from the decoder:

Frame 289 reconstruction from the encoder:

Disabling B-frames makes the green and purple streaks go away, but the color drift mismatch between encoder and decoder remains.

Should be fixed in latest master.


Enable all characters' idle animations when the character is in highly populated areas (e.g. Grand Exchange)

We have the GPU plugin that drastically improves the visual quality of the game. Following the same idea of improving visual fidelity, It would be amazing if it was possible to have RuneLite play all the original animations, even in highly congested areas.
It was clearly made for weaker machines to handle locations with a high number of players at the same time, but now machines are able to handle Runescape with huge draw distances and also anti-aliasing.
My proposed solution for this issue would be to provide a toggle for making sure the game client does not skip playing character animations. This would allow users with lower end machines to still play the game with the performance that they are used to.
In the following image, you can see characters with weapons not in their idle animation position, and also users high alching without the game rendering the yellow glow.

Duplicate of #8927

@melkypie This is not a duplicate of #8927. This suggestion is the exact opposite. I don't want my character to have the no animation state. I want all the other characters to not be in no animation state and instead do the idle animation.


[webui] Investigate removing Redux in favour of React contexts and hooks

I wondered about using your async reducer, but because I believe that since React 16.3 (and the arrival of Context API) redux is not necessary and is actually just overheads.
However, some store mechanism should be used since the entire app might need the config. If you want me to rewrite with a
context I'd be happy to. It'll take about 5 minutes and will be much neater. Just tell me what you prefer
Originally posted by @eylonronen in https://github.com/treeverse/lakeFS/pull/751#issuecomment-703215962

@nopcoder @ozkatz @johnnyaug do we want to try to drop Redux?

my 2 cents on this: I'd rather not support both hooks/context and redux going forward. If we decide to move from Redux to something else, by all means let's do it - but the definition of done should be a complete migration from one to the other.
If that's the case, I'm OK with it, even if it takes a while to complete - we'll need to add it to our roadmap as a low priority item to make that clear.

Also in favor to reduce complexity

Closed by #1766 - Moved to context and hooks


Known issues

In this issue are a list of known issues with the plugin which I will commit to fixing.

Inline Anthropic generation doesn't work


Random 404 errors in traffic routing

When there are lots of requests going to a Service Fabric cluster, some of them will fail to 404 error. This varies how often it happens, between about 1 to 30 minutes between errors. Then there will be a period of a few seconds where some requests fail to 404 errors. These errors happen often enough that the Service Fabric plugin cannot be used in heavy production use. These errors did not happen with Traefik 1.7.
Based on analyzing the Traefik and Service Fabric plugin logs, this is caused by the Service Fabric dynamic configuration sometimes being read by Traefik as completely empty on one Service Fabric node's Traefik, then returning to normal a few seconds later the next time Traefik reads the configuration. Based on discussions with Traefik support, this seems to be caused by specific timing when reading the Service Fabric configuration, so that the configuration file is either missing or empty just as it's being read.
It seems that this is likely caused by the configuration file handling but I don't know it could be fixed.
https://github.com/microsoft/service-fabric-traefik/blob/488ce82ce9151d86e6b39bd34381841345097bf8/src/serviceFabricDiscoveryService/pkg/discovery/discoveryservice.go#L96
err := os.WriteFile(disco.publishFilePath, data, 0644)
The Traefik logs will show something like:
...00:00:05Z" level=debug msg="Skipping unchanged configuration." providerName=file
...00:00:08Z" level=debug msg="Configuration received:
...00:00:10Z" level=debug msg="Configuration received:
...00:00:12Z" msg="Skipping unchanged configuration." providerName=file
Service Fabric plugin debug logs will show:
...00:00:03Z" level=debug msg="New snapshot arrived:
...00:00:08Z" level=debug msg="New snapshot arrived:
...00:00:13Z" level=debug msg="New snapshot arrived:
Most likely the Service Fabric plugin is writing new configuration at 00:00:08 at some exact timing when Traefik is reading the configuration file, and Traefik gets empty or missing file.
Service Fabric plugin is configured to write the configuration (PUBLISH_FILE_PATH) to "..\work\sf_discovered.yaml" and Traefik is configured to read the directory (which has also traefik_dynamic.toml with other settings):
[providers]
[providers.file]
directory = "../work"
watch = true
This is currently preventing us from taking Traefik 2.x into use with Service Fabric.

Hi @nokjuh, We're due to bring Traefik 2.x into production later this month. We haven't experienced the above issue during our performance testing, but I'm wondering how much "lots of requests" means for you? The above is making me even more nervous of upgrading.

Thanks for the quick response, @nokjuh. I 100% agree with your last statement; that's not something I would approve of internally.
In saying that, we fortunately already have retries built into our service calls (using Polly), and perhaps that's why we've yet to see it during our integration or performance tests. We'll have to review our logs to see if it's an issue that's been hidden from us until now.

Hi @nokjuh,
We've been carrying out further Performance Tests in a dedicated environment (Previous tests performed were local to our dev environment). Like you, we've encountered ongoing issues with services not being found. Traefik Support has been brilliant in helping me investigate the problem, but we're still looking for a solution. I've now recommended that we don't upgrade to V2 of Traefik until these issues with the integration are resolved.
I will note that our log files don't show the same issue as described above, i.e., empty configuration (we always appear to get a configuration; however, Traefik gives out that it can't always find a service, which leads me to believe that the configuration is not loading or there is a small window between the service configuration loading/reloading.
Best,
Stephen
@craftyhouse @dariopb Is this something you can assist with?

This should be fixed with pull requests #29 , #30 , and #31 . Each fixes a different case which can lead to Traefik reading a missing, empty, or practically empty configuration.

fixed with pull requests #29  , #30  , and #31


actions started

10 Actions/Commands
move
wait
item use
trade item
melee attack
magic (ranged) attack
talk (recruit)
heal (staff heal)
seize (win the game)
rescue/drop


srcPath does not always work correctly

The anonymous function that determines srcPath is subject to race conditions and does not always return the correct value.

I think a little more work could be done to figure out if it's safe to attempt to use srcPath as a last resort. Right now it just assumes it's OK to try, but really it could be require.js or the most recent asynchronously accessed file. It should be possible to detect those cases and then ignore the srcPath option. Another idea would be to require backupWorkerSource to be provided and remove the srcPath thing altogether. That would probably require moving to v3.0, since it would make it so IE can no longer access remote datasources inside web workers without extra configuration.

Plan on adding this polyfill for detecting the current source path. document.currentScript works in non-IE modern browsers.


[Studio] Adding French support for Tock Studio

[EN]It would be interesting to add French as a possible language on Tock Studio, which would help French trades in particular to use the interface much more easily (no need to be bilingual).
[FR]Il serait intéressant d'ajouter le français en tant que langue possible sur Tock Studio, ce qui aiderait les métiers français notamment à utiliser l'interface bien plus facilement (ne nécessitant pas d'être bilingue)

https://angular.io/guide/i18n

From my investigations, this is quite a big part.
For production, it means to generate a build for each language, and then, with a server like nginx for example, to serve the correct build.
For example :
https://demo.tock.ai/fr/nlp/inbox => build fr
https://demo.tock.ai/en/nlp/inbox => build en
Not impossible, but some stuff to do :D


Enable async processing for SDF on Spark runner #23852

Enables SparkRunner to process SDF functions which can generate large output ( such as ParquetIO ) without the need to fit outuup to memory.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

R: @je-ik
R: @aromanenko-dev
R: @mosche

Thanks @JozoVilcek, that's awesome. I won't get to this today, but I'll have a look early next week!

@je-ik , @mosche I hope I did address all suggested changes except unit tests for iterators ( in my todo list for later ). Validates runner did pass for me locally.

Thanks so much @JozoVilcek. I'm off tomorrow, but I'll have a look on Monday.

Run Java PreCommit

Run Spark ValidatesRunner

Hi @mosche , just a quick feedback, I appreciate all the comments and suggestion. Ido plan to address them all by beginning of next week. Apologies for delay due to some other priorities on my side.

Thanks, no worries @JozoVilcek :)

Run Java PreCommit

Run Portable_Python PreCommit

Run Spark ValidatesRunner

Run Spark ValidatesRunner

Run Portable_Python PreCommit

Run Spark ValidatesRunner

Thanks so much @JozoVilcek, merged 🎉


thriftbp: Add closed bad connections counter to client pools

The bug fixed in 6bfad2e highlights the fact that this is a part of the
code that has very limited external visibility, and when a bug happens
there it's very hard to debug (it took me almost 2 days to find it).
So adding a counter to provide external visibility, and if a similar bug
happens in the future, it would be more obvious that this counter
dropped while the actual failure rate remains the same.

:haircut: Dropped "bad" from the counter and renamed the field. Although most of the closed connections are indeed bad it's not necessarily 100% bad.

:haircut: Dropped "bad" from the counter and renamed the field. Although most of the closed connections are indeed bad it's not necessarily 100% bad.


⚠ Bofrost.de has degraded performance

In 184c18b, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 986 ms

Resolved: Bofrost.de performance has improved in a12d984 after 13 minutes.


Remove default exports (#261)

Implements #261

The Vue demo at https://github.com/Palindrom/palindrom.github.io/blob/ffc1db8411f0b6d33f12ac8d6ccf50129988da6b/public/lab/vue/src/App.vue#L9 is already compatible with this change, because it uses a named export.

I made few changes that I think make it very clear which named export to use. I think that the lack of default export does not require explanation.


definition request

Hi  Dr. Nazarov,
Forgive my unwiseness, I am still puzzled by some definitions, e.g.
in repOverlap() fucntion, https://immunarch.com/reference/repOverlap.html

step
Either an integer or a numeric vector.In the first case, the integer defines the step of incremental overlap.In the second case, the vector encodes all repertoire sampling depths.

When and where I use the arguement ".step" ?  Does it display the overlapped clones between the "step".
And also, the method = "inc+morisita" or "inc+public". what does "incremental overlap" or "incremental" mean generally?
Generally, the mixcr may give more than one best v hit for a sequence, for example, TRBV4-1,TRBV4-3. In geneUsage(), there is an argument ".ambig" which can determine the first one will be chosen for analysis, while in pubRep(), there is no identical argument to do the same work, so if I set ".col" = "aa+v", how will it work? choose the first v segment or the second one? even if they belong to the same family.

Thanks a lot!
Best,
Decen

Hi Decen!
1 & 2. Yes, so in short you apply repOverlap at the the very first N clonotypes, where N is incrementally grows by .step. If .step is 1000, then you will have overlaps of the most abundant 1000, 2000, 3000, 4000, etc. clonotypes

"aa+v" will work with full matches, so if a clonotype has "TRBV4-1, TRBV4-2", the full match of both segments is required to count this as an equal clonotype to a clonotype in another repertoire

Does it make sense, or would you like me to clarify something?

Hi Decen!
1 & 2. Yes, so in short you apply repOverlap at the the very first N clonotypes, where N is incrementally grows by .step. If .step is 1000, then you will have overlaps of the most abundant 1000, 2000, 3000, 4000, etc. clonotypes

"aa+v" will work with full matches, so if a clonotype has "TRBV4-1, TRBV4-2", the full match of both segments is required to count this as an equal clonotype to a clonotype in another repertoire

Does it make sense, or would you like me to clarify something?

Yes, thanks a lot. When it plots, it is a little bit weird, so I write a command to only choose the first segment, discarding the others. and in the manual of Mixcr, the author also mentioned sometimes more than one segment will be assigned, anyhow, the first one is the first place, and they are always in the same family.  I also really hope someday, immunarch can incorporate an function to output the fasta file, read by MEGA or MrBayes with designated variables (like case name/number, proportion, v gene name .etc.)
Cheers,
Decen

Closing this issue for now. More details on the next version of Immunarch are here: https://b-t.cr/t/immunarch-will-significantly-evolve-but-it-will-break-things-and-we-need-your-help/1123


RealSenseViewer crashes when Kinect v2 is connected

Required Info

Camera Model
hoping to get D435 soon

Firmware Version

Operating System & Version
Windows 10 v 1709

Kernel Version (Linux Only)

SDK Version
SDK 2.0 version 2.8.2

Reproduce by connecting a Kinect (v2) to a computer and start the RealSense Viewer. It crashes immediately.

I want to confirm this bug is still there in the 2.10.0 release.
I've also built win32 debug from sources (691dc69228b0cbc0fc1718c7ecb69ab3b9611587) and got an exception with the following stack:
 	KernelBase.dll!751f08c2()	Unknown	Non-user code. Cannot find or open the PDB file.
 	[Frames below may be incorrect and/or missing, no symbols loaded for KernelBase.dll]		Annotated Frame
 	[External Code]		Annotated Frame
	realsense2.dll!librealsense::platform::wmf_uvc_device::get_pu_range(rs2_option opt) Line 692	C++	Symbols loaded.
 	realsense2.dll!librealsense::platform::retry_controls_work_around::get_pu_range(rs2_option opt) Line 523	C++	Symbols loaded.
 	realsense2.dll!librealsense::platform::multi_pins_uvc_device::get_pu_range(rs2_option opt) Line 774	C++	Symbols loaded.
 	realsense2.dll!librealsense::uvc_pu_option::get_range::__l2::<lambda>(librealsense::platform::uvc_device & dev) Line 43	C++	Symbols loaded.
 	realsense2.dll!librealsense::uvc_sensor::invoke_powered<librealsense::platform::control_range <lambda>(librealsense::platform::uvc_device &) >(librealsense::uvc_pu_option::get_range::__l2::librealsense::platform::control_range <lambda>(librealsense::platform::uvc_device &) action) Line 198	C++	Symbols loaded.
 	realsense2.dll!librealsense::uvc_pu_option::get_range() Line 46	C++	Symbols loaded.
 	realsense2.dll!librealsense::uvc_sensor::try_register_pu(rs2_option id) Line 680	C++	Symbols loaded.
 	realsense2.dll!librealsense::platform_camera::platform_camera(const std::shared_ptr<librealsense::context> & ctx, const std::vector<librealsense::platform::uvc_device_info,std::allocator<librealsense::platform::uvc_device_info> > & uvc_infos, const librealsense::platform::backend_device_group & group, bool register_device_notifications) Line 271	C++	Symbols loaded.
 	[External Code]		Annotated Frame
 	realsense2.dll!librealsense::platform_camera_info::create(std::shared_ptr<librealsense::context> ctx, bool register_device_notifications) Line 293	C++	Symbols loaded.
 	realsense2.dll!librealsense::device_info::create_device(bool register_device_notifications) Line 51	C++	Symbols loaded.
 	realsense2.dll!rs2_create_device(const rs2_device_list * info_list, int index, rs2_error * * error) Line 316	C++	Symbols loaded.
 	[External Code]		Annotated Frame

The reason appears to be that wmf_uvc_device._video_proc field is NULL.

Hi @baSSiLL
Thank you for detailed call-stack and crash info. We will add some extra checks around this area of code, but we still only have just Kinect 1 at our lab.

Hi, @dorodnic
Let me know when this update is published to GitHub, I'll test whether it fixes the issue.

Hi @baSSiLL
Did you get a chance to try the new release (v2.10.2)?

Yes @dorodnic , I did - and it works! No more crashes while Kinect 2 is connected. Actually I tested on the next day after release, but forgot to get back to you with results.
Thanks for quick fix guys.

Thanks for the feedback.


composite widget ideas

Module with "composite" widgets, basically specific combinations of graphics that can be placed within a subplot

[ ] similar to pyqtgraph ImageView widget with histogram and vmin-vmax setting.

taken over by #31


npx sst tunnel immediately exits

When following along with the Drizzle example, I'm unable to use a tunnel to connect to the database cluster in the VPC. After successfully installing the tunnel, opening the tunnel via npx sst dev or npx sst tunnel opens the tunnel, which then immediately exits.
SST Version: 3.2.73
OS: MacOS 14.5 (23F79)
My Repro Steps

CD or Clone into the Drizzle Example, run npm install.
Configure AWS credentials.
Run sudo npx sst tunnel install.
Run npx sst dev.

After the VPC, Database, and Function get created, SST starts the Tunnel and Studio command, but the tunnel exits immediately with:
Tunnel

➜  Forwarding ranges
   <IP_ADDRESS>/22
   <IP_ADDRESS>/22
   <IP_ADDRESS>/22
   <IP_ADDRESS>/22

Waiting for connections...

✕  Make sure you have installed the tunnel with `sudo sst tunnel install`

[process exited]

When running npx sst tunnel --print-logs:
➜  aws-drizzle npx sst tunnel --print-logs
time=2024-11-01T10:53:11.389-04:00 level=INFO msg="checking for pulumi" path="/Users/taylor.steele/Library/Application Support/sst/bin/pulumi"
time=2024-11-01T10:53:11.529-04:00 level=INFO msg="checking for bun" path="/Users/taylor.steele/Library/Application Support/sst/bin/bun"
time=2024-11-01T10:53:11.540-04:00 level=INFO msg="initializing project" version=3.2.73
time=2024-11-01T10:53:11.540-04:00 level=INFO msg="esbuild building" out=/Users/taylor.steele/Sites/aws-drizzle/.sst/platform/sst.config.1730472791540.mjs
time=2024-11-01T10:53:11.542-04:00 level=INFO msg="esbuild built" outfile=/Users/taylor.steele/Sites/aws-drizzle/.sst/platform/sst.config.1730472791540.mjs
time=2024-11-01T10:53:11.542-04:00 level=INFO msg="evaluating config"
time=2024-11-01T10:53:11.578-04:00 level=INFO msg="config evaluated"
time=2024-11-01T10:53:11.581-04:00 level=INFO msg="checking platform"
time=2024-11-01T10:53:11.581-04:00 level=INFO msg="loading home"
time=2024-11-01T10:53:11.892-04:00 level=INFO msg="aws credentials found" region=us-east-1 profile=dev
time=2024-11-01T10:53:11.892-04:00 level=INFO msg="fetching bootstrap"
time=2024-11-01T10:53:12.081-04:00 level=INFO msg="found existing bootstrap" data="{\"version\":4,\"asset\":\"sst-asset-xkmstvnnxtdh\",\"assetEcrRegistryId\":\"340752840587\",\"assetEcrUrl\":\"340752840587.dkr.ecr.us-east-1.amazonaws.com/sst-asset\",\"state\":\"sst-state-xkmstvnnxtdh\"}"
time=2024-11-01T10:53:12.081-04:00 level=INFO msg="loaded config" app=aws-drizzle stage=taylorsteele
time=2024-11-01T10:53:12.082-04:00 level=INFO msg="INFO getting passphrase app=aws-drizzle stage=taylorsteele"
time=2024-11-01T10:53:12.262-04:00 level=INFO msg="INFO pulling state app=aws-drizzle stage=taylorsteele out=/Users/taylor.steele/Sites/aws-drizzle/.sst/.pulumi/stacks/aws-drizzle/taylorsteele.json"
time=2024-11-01T10:53:13.041-04:00 level=INFO msg="starting tunnel" cmd="[sudo -n -E /opt/sst/sst1 tunnel start --subnets <IP_ADDRESS>/22,<IP_ADDRESS>/22,<IP_ADDRESS>/22,<IP_ADDRESS>/22 --host <IP_ADDRESS> --user ec2-user --print-logs]"
Tunnel

➜  Forwarding ranges
   <IP_ADDRESS>/22
   <IP_ADDRESS>/22
   <IP_ADDRESS>/22
   <IP_ADDRESS>/22

Waiting for connections...

time=2024-11-01T10:53:13.058-04:00 level=INFO msg="killing process" pid=65541
time=2024-11-01T10:53:13.058-04:00 level=ERROR msg="exited with error" err=<nil>
time=2024-11-01T10:53:13.059-04:00 level=INFO msg="process killed with term" pid=65541
time=2024-11-01T10:53:13.059-04:00 level=INFO msg="untracked process" pid=65541
✕  Make sure you have installed the tunnel with `sudo sst tunnel install`

When running sudo npx sst tunnel the tunnel works, but at the cost of changing the permissions in the .sst folder and the workspace json file in Library/Application Support/sst/workspaces. This works at the cost of needing elevated permissions to use other SST commands in the project. It would be preferable if I didn't need to use sudo to run these commands.
Here's the sst.config.ts for reference as well:
/// <reference path="./.sst/platform/config.d.ts" />

export default $config({
  app(input) {
    return {
      name: 'aws-drizzle',
      removal: input?.stage === 'production' ? 'retain' : 'remove',
      home: 'aws',
      providers: {
        aws: {
          profile: 'dev',
        },
      },
    };
  },
  async run() {
    const vpc = new sst.aws.Vpc('MyVpc', { bastion: true, nat: 'ec2' });
    const rds = new sst.aws.Postgres('MyPostgres', { vpc, proxy: true });

    const api = new sst.aws.Function('MyApi', {
      vpc,
      url: true,
      link: [rds],
      handler: 'src/api.handler',
    });

    new sst.x.DevCommand('Studio', {
      link: [rds],
      dev: {
        command: 'npx drizzle-kit studio',
      },
    });

    return {
      api: api.url,
    };
  },
});

Discord Reference: https://discord.com/channels/983865673656705025/983865673656705028/1300501887216390186

Similar #3940

Which version of Mac is this?

I'm on Sonoma 14.5. I'll update the original post.

restarting the terminal had no effect
resetting the repository with git clean -f -d -x and reinstalling in depentecy had no effect
restarting the computer had an effect. The tunnel works
Mac 13.3.1 (a)
"sst": "3.3.30"

Same issue, after installing tunnel with sudo, now when I deploy it gives me 30+ errors that the resources already exists, I already did a refresh and same issue, now I can't deploy!!

@goto3 yours seems like a different issue. Can you try deleting your .sst dir and trying again? If it doesn't work, then open a new issue with your error details?

This is still an issue, only thing that fixes it for me is a restart of my entire computer.

@bodhihawken do you mean it works for a while and then once it breaks you need to restart?

Getting the same tunnel error with the following config:
/// <reference path="./.sst/platform/config.d.ts" />

export default $config({
  app(input) {
    return {
      name: "sst-zero",
      removal: input?.stage === "production" ? "retain" : "remove",
      protect: ["production"].includes(input?.stage),
      home: "aws",
    };
  },
  async run() {
    const vpc = new sst.aws.Vpc("Vpc", { nat: "ec2", bastion: true });

    const db = new sst.aws.Postgres("Database", {
      vpc,
      dev: {
        username: "postgres",
        password: "password",
        database: "local",
        host: "localhost",
        port: 5432,
      },
      transform: {
        parameterGroup: {
          parameters: [
            {
              name: "rds.logical_replication",
              value: "1",
              applyMethod: "pending-reboot",
            },
            {
              name: "rds.force_ssl",
              value: "0",
              applyMethod: "pending-reboot",
            },
            {
              name: "max_connections",
              value: "1000",
              applyMethod: "pending-reboot",
            },
          ],
        },
      },
    });
    const cluster = new sst.aws.Cluster("Cluster", { vpc });
    const connection = $interpolate`postgres://${db.username}:${db.password}@${db.host}:${db.port}`;
    cluster.addService("Zero", {
      image: "rocicorp/zero",
      dev: {
        command: "npx zero-cache",
      },
      loadBalancer: {
        ports: [{ listen: "80/http", forward: "4848/http" }],
      },
      environment: {
        ZERO_UPSTREAM_DB: $interpolate`${connection}/${db.database}`,
        ZERO_CVR_DB: $interpolate`${connection}/${db.database}_cvr`,
        ZERO_CHANGE_DB: $interpolate`${connection}/${db.database}_change`,
        ZERO_REPLICA_FILE: "zero.db",
        ZERO_NUM_SYNC_WORKERS: "1",
      },
    });

    return {
      connection: $interpolate`${connection}/${db.database}`,
    };
  },
});

@mattkinnersley was it working for you before?  What happens when you run the install command again?

This is the first time I've tried it out and it isn't working. Running sudo npx sst tunnel install works and says tunnel installed.

This was fixed with @thdxr's help. It was because my users name had a . in it which messed up something in the sst tunnel command. I believe a fix is coming.


Prototype: Ambassador Authentication Filter

First stage of GH-9

Prototype code to validate the external authentication mechanism and learn how to implement properly as well as learn Envoy toolchain.
Prototype Documentation
Plan for moving from Prototype to GA.

There's now a separate ticket for docs. We need to have CI pushing this image to Docker before we can close it though.

CI is pushing to Docker for ambassador-envoy and for ambassador-auth-service


[Ring Attention] Improve comments

📌 Checklist before creating the PR

[ ] I have created an issue for this PR for traceability
[ ] The title follows the standard format: [doc/gemini/tensor/...]: A concise description
[ ] I have added relevant tags if possible for us to better distinguish different PRs
[ ] I have installed pre-commit: pip install pre-commit && pre-commit install

🚨 Issue number

Link this PR to your issue with words like fixed to automatically close the linked issue upon merge
e.g. fixed #1234, closed #1234, resolved #1234

📝 What does this PR do?
Improve comments on comm overlap
💥 Checklist before requesting a review

[ ] I have linked my PR to an issue (instruction)
[ ] My issue clearly describes the problem/feature/proposal, with diagrams/charts/table/code if possible
[ ] I have performed a self-review of my code
[ ] I have added thorough tests.
[ ] I have added docstrings for all the functions/methods I implemented

⭐ Do you enjoy contributing to Colossal-AI?

[ ] 🌝 Yes, I do.
[ ] 🌚 No, I don't.

Tell us more if you don't enjoy contributing to Colossal-AI.

Thanks Liu zong


Provide a smarter fusion strategy

As described in #593, we need more rules to fuse more nodes when build fine-grained graph, it is a key step to enhance Mars optimizer, to start with, we can fuse diamond and inverted Y-shape in graph first.

hi, @hekaisheng , there are fusion strategy in two places: one is mars/fuse.pyx which is used to generate TensorFuseChunk. The other is to generate a specified fuse chunk such as TensorCpFuseChunk or TensorNeFuseChunk. I wonder which one should I add this smarter fusion strategy. I think it shoule be the fuse.pyx one. Is that true？

hi, @hekaisheng , there are fusion strategy in two places: one is mars/fuse.pyx which is used to generate TensorFuseChunk. The other is to generate a specified fuse chunk such as TensorCpFuseChunk or TensorNeFuseChunk. I wonder which one should I add this smarter fusion strategy. I think it shoule be the fuse.pyx one. Is that true？

Yes, the logic of fusing fine-grained graph is in fuse.pyx, the fusion strategy concerns about the structure of graph and need not to know which operand the node represents.

This issue is staled, replaced by #2435 .


git error outputted when destroying an app from non git directory

If you are in a non-git directory and destroy an app it will output:
fatal: Not a git repository (or any of the parent directories): .git

This should be avoided (or at least hidden).

Oh hey, what was the command line used?
Seems to also be coming running specs (see below), but I haven't seen that on heroku destroy: for some reason.
Below the spec output are two cases of create/destroy apps without git dirs.
rake spec without a git dir
~/github/steakknife/heroku  ᐅ rake spec
fatal: Not a git repository (or any parent up to mount parent /Volumes)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
fatal: Not a git repository (or any parent up to mount parent /Volumes)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
fatal: Not a git repository (or any parent up to mount parent /Volumes)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
fatal: Not a git repository (or any parent up to mount parent /Volumes)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
/Volumes/Users/barry/.rvm/rubies/ruby-1.9.3-p125/bin/ruby -S rspec ./spec/heroku/auth_spec.rb ./spec/heroku/client_spec.rb ./spec/heroku/command/addons_spec.rb ./spec/heroku/command/apps_spec.rb ./spec/heroku/command/auth_spec.rb ./spec/heroku/command/base_spec.rb ./spec/heroku/command/config_spec.rb ./spec/heroku/command/db_spec.rb ./spec/heroku/command/domains_spec.rb ./spec/heroku/command/drains_spec.rb ./spec/heroku/command/help_spec.rb ./spec/heroku/command/keys_spec.rb ./spec/heroku/command/logs_spec.rb ./spec/heroku/command/maintenance_spec.rb ./spec/heroku/command/pg_spec.rb ./spec/heroku/command/pgbackups_spec.rb ./spec/heroku/command/plugins_spec.rb ./spec/heroku/command/ps_spec.rb ./spec/heroku/command/releases_spec.rb ./spec/heroku/command/run_spec.rb ./spec/heroku/command/sharing_spec.rb ./spec/heroku/command/ssl_spec.rb ./spec/heroku/command/stack_spec.rb ./spec/heroku/command/version_spec.rb ./spec/heroku/command_spec.rb ./spec/heroku/helpers_spec.rb ./spec/heroku/heroku-postgresql_client_spec.rb ./spec/heroku/heroku-shared-postgresql_client_spec.rb ./spec/heroku/pg_resolver_spec.rb ./spec/heroku/pgbackupsclient_spec.rb ./spec/heroku/plugin_spec.rb
fatal: Not a git repository (or any parent up to mount parent /Volumes)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
fatal: Not a git repository (or any parent up to mount parent /Volumes)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
.................................F.........................................................................................................................................................................................................................................................................................................

Failures:

  1) Heroku::Client read_logs new style can read new style logs
     Failure/Error: @client.read_logs("myapp") do |logs|
     WebMock::NetConnectNotAllowedError:
       Real HTTP connections are disabled. Unregistered request: GET http://api.heroku.com:443/logplex_url with headers {'Accept'=>'*/*', 'User-Agent'=>'Ruby'}

       You can stub this request with the following snippet:

       stub_request(:get, "http://api.heroku.com:443/logplex_url").
         with(:headers => {'Accept'=>'*/*', 'User-Agent'=>'Ruby'}).
         to_return(:status => 200, :body => "", :headers => {})

       registered request stubs:

       stub_request(:get, "https://api.heroku.com/logplex_url")
       stub_request(:get, "https://api.heroku.com/apps/myapp/logs?logplex=true")

       ============================================================
     # ./lib/heroku/client.rb:414:in `block in read_logs'
     # ./lib/heroku/client.rb:413:in `read_logs'
     # ./spec/heroku/client_spec.rb:140:in `block (4 levels) in <top (required)>'

Finished in 4.74 seconds
331 examples, 1 failure

Failed examples:

rspec ./spec/heroku/client_spec.rb:139 # Heroku::Client read_logs new style can read new style logs

Randomized with seed 30734

Coverage report generated for RSpec to /Volumes/Users/barry/github/steakknife/heroku/coverage. 2267 / 3113 LOC (72.82%) covered.
rake aborted!
    WARNING: Potentially Destructive Action
 !     This command will affect the app: dasfadsf88888
 !    To proceed, type "dasfadsf88888" or re-run this command with --confirm dasfadsf88888

> dasfadsf88888
Destroying dasfadsf88888 (including all add-ons)... done
~/heroku  ᐅ

Create repo, create app, remove repo, destroy app
~/heroku  ᐅ mkdir blah7777
~/heroku  ᐅ cd blah7777
~/heroku/blah7777  ᐅ git init
Initialized empty Git repository in /Volumes/Users/barry/heroku/blah7777/.git/
~/heroku/blah7777 (master ✔) ᐅ heroku apps:create blah7777
Creating blah7777... done, stack is bamboo-mri-1.9.2
http://blah7777.heroku.com/ | git@heroku.com:blah7777.git
Git remote heroku added
~/heroku/blah7777 (master ✔) ᐅ rm -rf .git
~/heroku/blah7777  ᐅ heroku apps:destroy blah7777

 !    WARNING: Potentially Destructive Action
 !     This command will affect the app: blah7777
 !    To proceed, type "blah7777" or re-run this command with --confirm blah7777

> blah7777
Destroying blah7777 (including all add-ons)... done
~/heroku/blah7777  ᐅ


Improve python dependencies, license and readme

Add wheel and anytree to the Python requirements.
Added a note on possibly needing sudo for screen.
Added a note on possibly needing to install python requirements twice.
Added year and owner to licence.
Added instructions to program device in Vivado.

Thanks for the fixes @marnovandermaas


How to compute number with 256 bits?

How can I calculate the length of a 256-bit number?
I tried to change the parameter 't', but it seems that the maximum value I can set is 60.

I searched briefly among the closed issues. Maybe this SEAL manual would help you get to know better the scheme parameters.
Further on, there was a comment here explaining that "The HE security standard does not have parameters for degree 256. By default, it will be treated as insecure".
I was also wondering in this issue, how t can be set higher than what you mentioned.

Thanks for your answer.
Now I see, the SEAL lib constrains the individual primes can be up to 60 bits.

Hmm, as I didn't work with BFV scheme for a while. Does that mean you get a running execution or still you have problem?

Since SEAL has some constrains on the parameter setting, the problem still here. So, I need to figure out a workaround solution of my problem.

Could you describe the operation you seek to perform a bit more in detail? There might be some tricks with CRT decomposition that you might use


Update list of required visibilities for running Accumulo Store integration tests

SchemaHidingIT requires a "public" visibility

Merged into develop.


apiserver endpoint error en session.get_task_result_stream(task_id) with client

I'm doing something wrong but I can't figure it out. When I call from my fastapi to try to retrieve the streaming events, the apiserver output gives me a 404 Not found:
NFO:     <IP_ADDRESS>:57518 - "POST /sessions/create HTTP/1.1" 200 OK
INFO:llama_deploy.message_queues.base - Publishing message of type 'ag-rag-react-stream' with action 'ActionTypes.NEW_TASK' to topic 'llama_deploy.ag-rag-react-stream'
INFO:     <IP_ADDRESS>:55704 - "POST /publish/llama_deploy.ag-rag-react-stream HTTP/1.1" 200 OK
INFO:     <IP_ADDRESS>:57524 - "POST /sessions/5cfe06a0-375f-4387-a8fb-036e94957f85/tasks HTTP/1.1" 200 OK
INFO:     <IP_ADDRESS>:42934 - "POST /process_message HTTP/1.1" 200 OK
INFO:llama_deploy.message_queues.simple - Successfully published message 'ag-rag-react-stream' to consumer.
INFO:     <IP_ADDRESS>:57530 - "GET /sessions/5cfe06a0-375f-4387-a8fb-036e94957f85/tasks/821c981c-55bb-4240-9ada-7065bdd36613/result_stream HTTP/1.1" 404 Not Found
INFO:     <IP_ADDRESS>:60004 - "GET /sessions/5cfe06a0-375f-4387-a8fb-036e94957f85/state HTTP/1.1" 200 OK
example code (fastapi endpoint)
@workflow_router.post("/workflow/execute")
async def workflow_execute(request: Request):
(...)
client = llama_deploy.Client(api_server_url=apiserver_url,
                            control_plane_url=control_plane_url,
                            timeout=300
                            )
session = await client.core.sessions.create()
task_id = await session.run_nowait(service_name, **request_input)

async def stream_events():

    async for event in session.get_task_result_stream(task_id):
        if "progress" in event:
            data = {
                "choices": [
                    {
                        "delta": { "content": f"Chunk {event['progress']}" }
                    }
                ]
            }
            yield f"data: {json.dumps(data)}\n\n"
            logger.info(f"Progress: {event['progress']}")

return StreamingResponse(stream_events(), media_type="application/octet-stream")

=============
OUTPUT :
INFO:     <IP_ADDRESS>:57970 - "POST /workflow/execute HTTP/1.1" 200 OK
ERROR:    Exception in ASGI application
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/httpx/_transports/default.py", line 69, in map_httpcore_exceptions
yield
File "/usr/local/lib/python3.11/site-packages/httpx/_transports/default.py", line 373, in handle_async_request
resp = await self._pool.handle_async_request(req)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/httpcore/_async/connection_pool.py", line 216, in handle_async_request
raise exc from None
File "/usr/local/lib/python3.11/site-packages/httpcore/_async/connection_pool.py", line 196, in handle_async_request
response = await connection.handle_async_request(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/httpcore/_async/connection.py", line 101, in handle_async_request
return await self._connection.handle_async_request(request)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/httpcore/_async/http11.py", line 143, in handle_async_request
raise exc
File "/usr/local/lib/python3.11/site-packages/httpcore/_async/http11.py", line 113, in handle_async_request
) = await self._receive_response_headers(**kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/httpcore/_async/http11.py", line 186, in _receive_response_headers
event = await self._receive_event(timeout=timeout)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/httpcore/_async/http11.py", line 224, in _receive_event
data = await self._network_stream.read(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/httpcore/_backends/anyio.py", line 32, in read
with map_exceptions(exc_map):
File "/usr/local/lib/python3.11/contextlib.py", line 158, in exit
self.gen.throw(typ, value, traceback)
File "/usr/local/lib/python3.11/site-packages/httpcore/_exceptions.py", line 14, in map_exceptions
raise to_exc(exc) from exc
httpcore.ReadTimeout
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/uvicorn/protocols/http/httptools_impl.py", line 401, in run_asgi
result = await app(  # type: ignore[func-returns-value]
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/uvicorn/middleware/proxy_headers.py", line 60, in call
return await self.app(scope, receive, send)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/fastapi/applications.py", line 1054, in call
await super().call(scope, receive, send)
File "/usr/local/lib/python3.11/site-packages/starlette/applications.py", line 113, in call
await self.middleware_stack(scope, receive, send)
File "/usr/local/lib/python3.11/site-packages/starlette/middleware/errors.py", line 187, in call
raise exc
File "/usr/local/lib/python3.11/site-packages/starlette/middleware/errors.py", line 165, in call
await self.app(scope, receive, _send)
File "/usr/local/lib/python3.11/site-packages/starlette/middleware/exceptions.py", line 62, in call
await wrap_app_handling_exceptions(self.app, conn)(scope, receive, send)
File "/usr/local/lib/python3.11/site-packages/starlette/_exception_handler.py", line 62, in wrapped_app
raise exc
File "/usr/local/lib/python3.11/site-packages/starlette/_exception_handler.py", line 51, in wrapped_app
await app(scope, receive, sender)
File "/usr/local/lib/python3.11/site-packages/starlette/routing.py", line 715, in call
await self.middleware_stack(scope, receive, send)
File "/usr/local/lib/python3.11/site-packages/starlette/routing.py", line 735, in app
await route.handle(scope, receive, send)
File "/usr/local/lib/python3.11/site-packages/starlette/routing.py", line 288, in handle
await self.app(scope, receive, send)
File "/usr/local/lib/python3.11/site-packages/starlette/routing.py", line 76, in app
await wrap_app_handling_exceptions(app, request)(scope, receive, send)
File "/usr/local/lib/python3.11/site-packages/starlette/_exception_handler.py", line 62, in wrapped_app
raise exc
File "/usr/local/lib/python3.11/site-packages/starlette/_exception_handler.py", line 51, in wrapped_app
await app(scope, receive, sender)
File "/usr/local/lib/python3.11/site-packages/starlette/routing.py", line 74, in app
await response(scope, receive, send)
File "/usr/local/lib/python3.11/site-packages/starlette/responses.py", line 250, in call
async with anyio.create_task_group() as task_group:
File "/usr/local/lib/python3.11/site-packages/anyio/_backends/_asyncio.py", line 597, in aexit
raise exceptions[0]
File "/usr/local/lib/python3.11/site-packages/starlette/responses.py", line 253, in wrap
await func()
File "/usr/local/lib/python3.11/site-packages/starlette/responses.py", line 242, in stream_response
async for chunk in self.body_iterator:
File "/maarifa/maarifa-api/routes/workflow.py", line 436, in stream_events
async for event in session.get_task_result_stream(task_id):
File "/usr/local/lib/python3.11/site-packages/llama_deploy/client/models/core.py", line 128, in get_task_result_stream
async with client.stream("GET", url) as response:
File "/usr/local/lib/python3.11/contextlib.py", line 210, in aenter
return await anext(self.gen)
^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/httpx/_client.py", line 1617, in stream
response = await self.send(
^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/httpx/_client.py", line 1661, in send
response = await self._send_handling_auth(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/httpx/_client.py", line 1689, in _send_handling_auth
response = await self._send_handling_redirects(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/httpx/_client.py", line 1726, in _send_handling_redirects
response = await self._send_single_request(request)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/httpx/_client.py", line 1763, in _send_single_request
response = await transport.handle_async_request(request)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/httpx/_transports/default.py", line 372, in handle_async_request
with map_httpcore_exceptions():
File "/usr/local/lib/python3.11/contextlib.py", line 158, in exit
self.gen.throw(typ, value, traceback)
File "/usr/local/lib/python3.11/site-packages/httpx/_transports/default.py", line 86, in map_httpcore_exceptions
raise mapped_exc(message) from exc
httpx.ReadTimeout

@jdelacasa I think either

the stream was not created yet and the code to get the stream ran too soon? You might need to retry this or have a small delay
your workflow isn't streaming any events

If it is used constantly in the workflow
ctx.write_event_to_stream(ProgressEvent(msg="Step one is happening"))
and the final result is given to me correctly when it finishes its execution:
async def stream_events():

    async for event in session.get_task_result_stream(task_id):
        if event is not None:
            #if "progress" in event:
            data = {
                "choices": [
                    {
                        "delta": { "content": f"Chunk {event}" }
                    }
                ]
            }
            yield f"data: {json.dumps(data)}\n\n"
            logger.info(f"Progress: {event['progress']}")

    try:
        while True:
            final_result = await session.get_task_result(task_id)
            if final_result is not None:

                data = {
                    "choices": [
                        {
                            "delta": { "content": f"Final Result: {final_result.result}" }
                        }
                    ]
                }
                yield f"data: {json.dumps(data)}\n\n"
                # # Finalizamos el stream
                data = {
                    "choices": [
                        {
                            "finish_reason": "stop"
                        }
                    ]
                }
                yield f"data: {json.dumps(data)}\n\n"
                logger.info(f"Final Result: {final_result}")
                break
            await asyncio.sleep(0.3)

    except Exception as e:
        logger.error(f"Error in result: {e}")
        yield f"data: {json.dumps({'error': str(e)})}\n\n"

    finally:
        await client.core.sessions.delete(session.id)

return StreamingResponse(stream_events(), media_type="application/octet-stream")

It seems that if I add a sleep before each ctx.write_event_to_stream the reception of events in stream works:
    await asyncio.sleep(0.3)
    ctx.write_event_to_stream(ProgressEvent(msg="ok"))


Resuming a BADS run

Hi, I'm testing your package and it seems to be working amazingly for my use case :)
However, I have two questions regarding how BADS can be initialized:

If a previous BADS run has stopped for some reason, is there a way to continue it from that point?
More generally, if I have a known set of points of the function to optimize, is there some way I can feed them into BADS, maybe as initial points?

Thanks!

Thanks for the question - I answered it under our Discussions here: https://github.com/orgs/acerbilab/discussions/5
We keep the Issues section of individual repos for actual bugs and developer notes; we use the lab Discussions forum for Q&A since they often apply to multiple versions of our packages (for example this question applies to both the MATLAB and Python versions).


libc, console: declare __stdout_hook_install in libc-hooks.h

Declare __stdout_hook_install in libc-hooks.h and use it in the console drivers rather than redeclare it every time.

Nit - 2nd commit message should read "Should be console_out not consoleOut."

Thanks, fixed.


chore: update the navigation link for setting page

Description

disable start bot button when there are some errors
fix the diagnostic link error in sidebar
add link for setting page

Task Item
#minor
closes #4858

Screenshots

@lei9444 is this PR still WIP? should it moved back to draft?

@lei9444 is this PR still WIP? should it moved back to draft?

Hi @srinaath this PR is ready now


Finalize Delivery-related template interface

In RFC0013, two templates were proposed for deploying services and validated them post-deployment:

ClusterDeployTemplates are cluster-scoped resources that enable application operators to specify resource templates that deploy environments.
ClusterDeployTemplates take a single source artifact and return a single deployment artifact.
source -> deployment

ClusterDeliveryTemplates are cluster-scoped resources that enable application operators to specify resource templates that perform validations on a particular deployed environment.
ClusterDeliveryTemplates take a deployment artifact and any number of additional source artifacts. They return a single deployment artifact.
deployment, source[] -> deployment

Based on feedback from the community, I want to suggest that we simplify this interface by making these templates identical in inputs/outputs, by moving the source->deployment "cast" to the input of ClusterDeployTemplate. This also gives us the ability to inject additional K8s config (e.g., values.yaml files for Kapp, out-of-band resources) into ClusterDeployTemplate. Additionally, I also want to suggest that we rename these resources for clarity. The new descriptions would look like:

ClusterDeploymentTemplates are cluster-scoped resources that enable application operators to specify resource templates that deploy environments.
ClusterDeliveryTemplates take a deployment artifact and any number of additional source artifacts. They return a single deployment artifact.
deployment, source[] -> deployment

ClusterDeploymentValidationTemplates are cluster-scoped resources that enable application operators to specify resource templates that perform validations on a particular deployed environment.
ClusterDeliveryTemplates take a deployment artifact and any number of additional source artifacts. They return a single deployment artifact.
deployment, source[] -> deployment

An interesting outcome of this approach would be that it becomes possible to feed the output of a deployment into another deployment. This may or may not be useful. One use case might be deploying several environments that should remain synchronized.

source into source is actually fairly common. At unit-test step is one example.
I also think that there is a separate distinction for deployment into deployment. It's actually a source into deployment where the source gets cast into a deployment (which gives nice symmetry when its later downcast back to a source).

RFC 13 should be updated to match this spec if we accept this issue

An interesting outcome of this approach would be that it becomes possible to feed the output of a deployment into another deployment. This may or may not be useful. One use case might be deploying several environments that should remain synchronized.

I see usefulness in ClusterDeploymentTemplate consuming deployments from other ClusterDeploymentTemplates. Namely, consider a Delivery author who does not have access to create ClusterDeploymentTemplates. There exist two templates that alter a cluster in a manner necessary for their tests of the app to be deployed. The Delivery author can simply call the first deployment template and then call the second deployment template.
I do not think that ClusterDeploymentTemplate consuming deployments from other ClusterDeploymentTemplates gives us enough primitives to keep two environments synchronized. This is because ClusterDeploymentTemplate only takes a single deployment. While that deployment would be locked, every other value (e.g. the sources) would not be locked. So synchronization cannot be assured.

Possible solution, the sources taken by a deployment are also locked and also passed along. This is not very satisfying because there is no distinction between sources and deployments. Better to allow ClusterDeploymentTemplate to take (and pass on) multiple deployments. Even this is a bit messy, as we would then have to dissambiguate between the different deployments that were being referenced within the template field of the ClusterDeploymentTemplate or ClusterDeploymentValidationTemplates .

Closed by #322


Package is "broken" on npm

Your Environment

Prettier version: 3.0.0
node version [12.x.x, 14.x.x]: v20.9.0
package manager<EMAIL_ADDRESS><EMAIL_ADDRESS>IDE: VSCode

Describe the bug
Something is corrupted on https://www.npmjs.com/
To Reproduce
Visit https://www.npmjs.com/package/@trivago/prettier-plugin-sort-imports or try to npm install or npm ci this package (any version).
Expected behavior
Package works
Screenshots, code sample, etc

diagnostics id: 81e655d02e8a29fd_1e11
Configuration File (cat .prettierrc, prettier.config.js, .prettier.js)
N/A
Error log
$ yarn install
yarn install v1.22.19
[1/4] 🔍  Resolving packages...
[2/4] 🚚  Fetching packages...
error An unexpected error occurred<EMAIL_ADDRESS>Request failed \"500 Internal Server Error\"".
info If you think this is a bug, please open a bug report with the information provided in ".../yarn-error.log".
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.

Contribute to @trivago/prettier-plugin-sort-imports

[ ] I'm willing to fix this bug 🥇

It looks fixed now!


Regarding Issue #319

The Neon guard at the front desk still insist I have a bounty, but infact I have not

Details
If I reenable Skeevers .esm mod https://www.nexusmods.com/starfield/mods/5724 the problem is fixed instantly. Is this supposed to take some time to take effect (if I used another mod for it?)
Game Version
<IP_ADDRESS>
Language
English (EN)
New Game
Yes
Reproduction Steps
Disable .esm and remove plugin.txt entry for mod https://www.nexusmods.com/starfield/mods/5724
Head over to Neon either via fast travel, or direct flight and landing
Neon guard insists on bounty, if you ever had one in your playthrough, even if not currently outstanding.

They just missed forwarding the DialogueNeonConvo_SecurityCheckpoint (0032C7C3) changes from skeever's mod.