Clarify the names animation and forwardAnimation

Motion to rename the parameter names 'animation' and 'forwardAnimation' to

'incomingAnimation' and 'outgoingAnimation' or
'entranceAnimation' and 'exitAnimation' or
something that points out their analogous nature.

And rename the various underlaying field variables and properties.
cc @Hixie

The problem is that the animations are used like this:

Route A <--animation1--> Route B <--animation2--> Route C

...which means that animation1 can be both "incoming" or "entrance" (when going from A to B) and "outgoing" or "exit" (when going from B to A), as can animation2 (when going from B to C and C to B respectively).
Further complicating matters, the "animation" for B is the "forwardAnimation" for A, and the "forwardAnimation" for B is the "animation" for C.

(moving to M2 since if we don't change it in the coming week or so we probably can't change it ever)

I think renaming these parameters would make the API a little easier to understand.
I also think we could improve the doc for ModalRoute.buildTransitions() a little. Currently it begins with: Override this method to wrap the route in a number of transition widgets. It might be a little clearer to say that the method enables defining how the route transitions in and out.
If the example for the buildTransitions() method demo'd transitions that were linked to both the incoming and outgoing animations, that would help too.

@hixie I see that I was more confused than I thought. I still hope that we can clarify that docs/names somehow.

Yeah I totally agree that the current names suck. I tried for a while to come up with better names and failed. :-( I'm open to suggestions, but they have to be at least as accurate as today's dubious names. :-)

There's actually 2 independent instances of things that can be at where you drew the 'animation1' right? The 'forwardAnimation' for route A and the 'animation' for route B are 2 separate orthogonal things that are happening simultaneously right?
The situation you described is indeed confusing but mainly because you changed perspective right? I think the clearer way to visualize it is when going from C to B for instance, we're reversing the entranceAnimation of C and reversing the exitAnimation of B. But we're still calling them entranceAnimation and exitAnimation from the perspective of the advancing animation.

In other words, when taking the absolute numerical values of those animations into account, the words entrance/incoming/exit/outgoing can make a bit more sense. If we go from C to B, the fact that we're still running the 'entranceAnimation' of C is a bit easier to understand when we also think about the fact that that animation is running from 1.0 to 0.0.

IIRC, the animation for B and the forwardAnimation for A are driven by the same underlying AnimationController. (They might overlay different curves on that underlying animation.) They are fundamentally the "same" animation.

I don't really see why the animation from B to C is any more of an "exit" animation for B than the animation from A to B. Both animations are used when B "exits", it just depends if it exits "forward" or "backward". In fact strictly speaking, it doesn't exit at all when going from B to C; it's still there in the background and you can typically return to it by reversing the animation from B to C.

re https://github.com/flutter/flutter/issues/9132#issuecomment-290819486
I think that's ok though. Having the same instance of a thing under the hood being called 2 different things from 2 different perspectives is ok. Having that same input produce 2 different outputs is ok too.

I don't really see why the animation from B to C is any more of an "exit" animation for B than the animation from A to B.

You meant 'for B than the animation from B to A' right?
So from B to C, you're running B's exitAnimation from 0->1. That's easier to visualize.
From B to A, you're running B's entranceAnimation from 1->0. Thus, you're reversing B's entranceAnimation. Backing out of an entrance is easy to visualize too I think and describes what it's doing.

In fact that's why we just call the A->B animation "animation" from B's perspective, because it's usually the only one you deal with. It's very rare in practice to actually use "forwardAnimation".

What about using some name that denoted the you're-going-above-someone-else and the you're-going-below-someone-else nature of it? That doesn't change depending on the directionality of the perspective.

Say above/belowAnimation or covering/becomingCoveredAnimation?

Seems reasonable if we can find good words... It's hard though, e.g. is "aboveAnimation" the animation for when you are above someone, or when someone is coming above you?
There's a huge asymmetry in how much these are used. For example, we literally only use forwardAnimation once in our repo, and it's in a test. We use the other animation a lot more. This argues for the current asymmetry in the names, where the commonly used argument is just "animation" and the rarely used one has a longer name.

I think we shouldn't use how frequently we used this to implement material to inform assumptions on how our users would use it or to guide how easy to make each part of the API understandable.
All these terms from properties and parameters are coming from superclasses of self. It would be a leap to derive that 'above' is referring to a non-self entity being above.
Trying to think of transferable skeuomorphic terms from relatable industries. foreground/backgroundAnimations could work. It's kinda like we're shooting a movie.

I think we shouldn't use how frequently we used this to implement material to inform assumptions on how our users would use it or to guide how easy to make each part of the API understandable.

I think it's probably a reasonable proxy for how common the feature is in general (at least, it's the only real proxy we have today). We should definitely make common things shorter and easier and rarer things longer. (The short names are a scarce namespace, the common things should be short for convenience.)

It would be a leap to derive that 'above' is referring to a non-self entity being above.

I think it would be eminently reasonable to assume that the "aboveAnimation" is above the "belowAnimation", but if I understand what you're describing, it would be the other way around.

foreground/backgroundAnimations could work. It's kinda like we're shooting a movie.

I like the idea of using terms from film-making. I'm not sure about those specific terms... when you're going back from the "forward" animation, you're in the foreground, in that if the user taps the screen that's what gets tapped.

Word clouds:

primary, enter, exit, intro, outro
nextRoute, pause, resume, backgrounded, foregrounded

Name suggestions:

animation / nextRouteAnimation
entranceAnimation / suspendAnimation

API suggestion:
Should we have more methods instead of one all-sing, all-dance method?
Widget buildEntranceTransition(Animation<double> animation, Widget child);
Widget buildExitTransition(Animation<double> animation, Widget child);
Widget buildSuspendTransition(Animation <double> animation, Widget child);
Widget buildResumeTransition(Animation <double> animation, Widget child);

or
Widget buildTransition(Animation<double> animation, Widget child);
Widget buildSuspendResumeTransition(Animation <double> animation, Widget child);

Having all four won't work because you can reverse the animation mid-course, otherwise that would bevery attractive. Even having two is dubious because you can actually have both animations simultaneously going on and it's not clear which one you want to build inside the other. I can imagine wanting it both ways. That's why it's one builder today.
animation / nextRouteAnimation is what I was going for with animation / forwardAnimation. I'm fine with that one if y'all prefer it to forwardAnimation.
animation / suspendResumeAnimation could work, I guess, though it seems weird to have those names versus something like entranceExitAnimation / suspendResumeAnimation or previousRouteAnimation / nextRouteAnimation, both of which seem excessively verbose.

Having all four won't work because you can reverse the animation mid-course, otherwise that would very attractive.

The way we handle this for CurvedAnimation is that we only flip over to the reverse curve if you actually make it to the end of the forward curve.

(Obviously we could supply a default implementation of buildExitTransition that just called through to buildEntranceTransition with the animation reversed or whatever.)

People get really jumpy when the "out" animation isn't exactly the same as the "in" animation in reverse, that's what started this whole thing. I think we'd be better off not making that easier. :-)

Ah, ok.  I guess that makes sense.  I got too wrapped up in the filmmaking analogy.  :)

Could we remove forwardTransition? If it's "very rare in practice to use the forwardAnimation" and see https://github.com/flutter/flutter/issues/9132#issuecomment-290841280, could we live without it? I have to admit that I'm still confused about what it's for...

I'm using it for the cupertino page animation :S
Let's talk in person.

You need it for some effects.  For example, if you want to slide the old route over to the side a bit as the new route comes in.

So you use the "forwardAnimation" if you want to change how your route exits or leaves or disappears or vanishes when it's being replaced or dimsissed or removed or ... :-)
I suppose we need to beef up https://docs.flutter.io/flutter/widgets/ModalRoute/buildTransitions.html so that this use case can be understood.

Yes, we'll violently add more explanations to the dartdoc either way. It's only used when the route is being replaced by another route and and in reverse when it's un-replaced. The 'primary' animation is used when it was already the top of the stack and being dismissed.


Why EyeTracker doesn't work in hololens emulator even though I tick the 'GazeInput' checkbox under Capabilities in 'Package.appxmanifest'

Describe the Issue
The problem of using eye Tracker in HoloLens emulator.
Feature Area
I did the work step by step by following this link "https://microsoft.github.io/MixedRealityToolkit-Unity/Documentation/EyeTracking/EyeTracking_BasicSetup.html". But the HoloLens emulator didn't have the "Eye Tracker"checkbox. So what's the problem?

Did you read and follow this part?

You don't see a 'GazeInput' capability?
Check that your system meets the prerequisites for using MRTK (in particular the Windows SDK version).
You can also manually add the entry by opening the appxmanifest in an XML editor and adding the following:

  <Capabilities>
    <DeviceCapability Name="gazeInput" />
  </Capabilities>

Thanks for your reply.
I did this but it didn't work. When I run the MRTK "eyeTracking"example, I could see this in HoloLens Emulator.
[cid:930e98e2-3c2a-4f5d-a249-bcdfbeca59c3]
But when I run my own app, I couldn't see it. I truly did it as you say (setting the "Gazeinput"), But it didn't work.
So is there any other reason?
Thanks.

发件人: Alexander Seeck<EMAIL_ADDRESS>发送时间: 2019年9月18日 4:46
收件人: microsoft/MixedRealityToolkit-Unity<EMAIL_ADDRESS>抄送: cheeseEvil<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>主题: Re: [microsoft/MixedRealityToolkit-Unity] Why EyeTracker doesn't work in hololens emulator even though I tick the 'GazeInput' checkbox under Capabilities in 'Package.appxmanifest' (#5980)
Did you read and follow this part?
You don't see a 'GazeInput' capability?
Check that your system meets the prerequisites for using MRTKhttps://microsoft.github.io/MixedRealityToolkit-Unity/Documentation/GettingStartedWithTheMRTK.html#prerequisites (in particular the Windows SDK version).
You can also manually add the entry by opening the appxmanifest in an XML editor and adding the following:

―
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/MixedRealityToolkit-Unity/issues/5980?email_source=notifications&email_token=AHW4PJXDRDIAKCU7DKBEBYLQKIIK5A5CNFSM4IX2ESRKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD67ZBIA#issuecomment-532648096, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AHW4PJSMCKV4CRPFORNRQRLQKIIK5ANCNFSM4IX2ESRA.


[bugfix][distributed] fix multi-node bug for shared memory

fixes https://github.com/vllm-project/vllm/issues/6564

@youkaichao wouldn't the right thing to be to not attempt to use ShmRingBuffer at all for TP groups that span nodes?

@njhill even for a group that spans nodes, we use shm for the ranks inside the node, and zmq for ranks outside the node.
this is, actually, in preparation for the future, the alternative to ray dag implementation.


Add option to disable system tray icon

Closes #14443
Until I saw this issue, I hadn't realized I wasn't the only one that didn't like the icon.

Removing the tray icon would also silently break tray notifications, which is kind of not nice (there is no feedback about it).

Removing the tray icon would also silently break tray notifications, which is kind of not nice (there is no feedback about it).

I know. I added a warning for the config saying exactly that.

That seems fine. I would probably place the "Enable tray icon" above the "Enable tray notifications" option since people tend to read top -> bottom and the one is dependent the other.

I would probably place the "Enable tray icon" above the "Enable tray notifications" option since people tend to read top -> bottom and the one is dependent the other.

Done!


intro tutorial: Remove unique_id from Agent init

Remove unique_id from the Agent init in the introduction tutorial, since unique_id is now automatically assigned in Mesa 3.0 and Mesa-geo 0.9.
Update after the changes in https://github.com/projectmesa/mesa-geo/pull/248.

@tpike3 @wang-boyu I have a very specific question: The notebook had unique_id = "HOODNUM" defined in the class, and then unique_id=self.unique_id in the AgentCreator from_file() method. I think that meant that the HOODNUM column was assigned as the unique_id, right? How was that used and is it still needed? And isn't it also saved as an Agent attribute?
Please explain to how it's intended to work :)

I think that meant that the HOODNUM column was assigned as the unique_id, right?

That's right!

How was that used and is it still needed?

I don't think it's really used, but better confirm with @tpike3 for this tutorial.

For the Neighbourhood, I think I found an elegant solution of using the HOODNUM in the __repr__ method, so that it prints its HOODNUM from the data file.
    def __repr__(self):
        return f"Neighbourhood {self.HOODNUM}"

This was equivalent of the original behavior of assigning HOODNUM to unique_id and then printing unique_id.
I will give @tpike3 a chance to review and otherwise I will merge tonight.

Thanks!
Please don't merge my PRs though, I like to do that myself. An review and approve is really appreciated!


No issue!  Just a thank you.

Hello!
I wasn't sure how else to reach out to you, so I hope this is ok.  I just wanted to say I've been trying to accomplish something very similar to json-flat for the last couple of months, but I wasn't able to wrap my head around it.  I found your code day or two ago, and it's great!  Thank you very much for writing this and making it available.  It's amazing. 🥇
Regards,
Jeremy

To echo that - yes, this works very well and super useful.

To echo that - yes, this works very well and super useful.

Thank you very much for your feedback. It really helps.
My apologies for this very late reply. I had seen your messages earlier but lost then in the shuffle to reply.


Redirect to project page when user logs in

When a user first logs in (or successfully resets their password) , they are currently redirected to the homepage.
It would be nice if they were instead redirected to their projects page at http://localhost/manage/projects/
ping @di for feedback and labelling.  I assume we can tag this with 'good first issue'?

Agreed. 👍

https://github.com/pypa/warehouse/blob/64510f16148cefe77e7ae69809575c36e484e475/warehouse/accounts/views.py#L119
Just a matter of updating this line, correct?

Yes, and the corresponding tests.

@di @nlhkabu I'm interested in contributing to warehouse and would like to start with this good first issue.

Fixed in #2919.


Check for growth that is too fast.

resolves #38
Please refer to the issue for more information. The added content is a straight-forward test of growth.

Codecov Report

Merging #120 into develop will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           develop    #120   +/-   ##
=======================================
  Coverage     85.3%   85.3%
=======================================
  Files            9       9
  Lines          388     388
  Branches        83      83
=======================================
  Hits           331     331
  Misses          51      51
  Partials         6       6

Continue to review full report at Codecov.

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

Nice find on the references! Looks nice and clean.


Minimal doesn't compile (no dark and light

This is odd:
commit 428c48339bcc2dc7f0d04b0e571f937f25c600d8
has only the Custom.Shared.xaml file while the Minimal.csproj has all the three ones:
<Page Include="Styles\Custom.Dark.xaml">
    <Generator>MSBuild:Compile</Generator>
    <SubType>Designer</SubType>
</Page>
<Page Include="Styles\Custom.Light.xaml">
    <Generator>MSBuild:Compile</Generator>
    <SubType>Designer</SubType>
</Page>
<Page Include="Styles\Custom.Shared.xaml">
    <Generator>MSBuild:Compile</Generator>
    <SubType>Designer</SubType>
</Page>

Never mind I think is something that will be fixed ASAP, because the build fails so I don't want to clutter with a "dull" pull request.
I've raised this issue only to let you know, just in case someone else has problems on compiling this specific commit.

I think you caught me in the middle of some updates. Can you verify it works now?

Yes now is ok.

I have just updated Template10 to vers. 1.0.6 from NuGet Package Manager and I am experimenting the same errors on Styles ...

hi, you could see the differences of custom.xaml from a newly minimal created project using the latest template and the one you currently have or check the source code on GitHub.
It should be better to open a new issue instead of commenting on a closed one.

Thank you also for the suggestion on how to use Issues in GitHub.
It is a pity that there is not a specific forum for discussing Template10 issues/problems other than this section in GitHub that personally I do not find very friendly to use (compared with Community forum, Codeplex forum, StackOverflow ...). I wonder if there is some other place where people, trying to use Template10, can discuss and point out problems/questions ... Let me know if so :-)


Parse token as Authorization: Bearer

The syntax Authorization: <uuid> is not valid. The proper way to provide a token should be Authorization: Bearer <uuid>

Can you check that branch 161-parse-token-as-authorization-bearer works for you ?
If so, I'll open the PR and merge, thx

good!


Add two more buggy output tests to findMostCommonCharacter question.

One issue I ran into testing this: it would be great for the performance tests to allow for custom messages because "try making this linear" is not super-helpful for a beginner who hasn't learned O yet. I'd like to say something like: "It looks like your code is slow for large inputs. Are you going over the string multiple times? Using a dictionary might allow you to solve this problem with a single pass over the string." Or something like that.

Could we just remove the performance tests part of the schema? I think that would be fine, because that part of the code isn't really fleshed out yet in TIE anyway and might lead to false positives/negatives.

PTAL

Thanks!


Remove reference to deprecated allow-privileged flag for kubelet

The --allow-privileged flag does not exist for kubelet:
https://kubernetes.io/docs/reference/command-line-tools-reference/kubelet/
It was removed: https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.15.md#node
However I still don't understand why privileged pods are only required if a daemonset is used. How else can the plugin be deployed besides a daemonset, and how does it work when it is unprivileged?
This also fixes some minor language issues.

Or does it really mean that privileged mode is only required when health checks are run by the daemonset?

Thanks for the clean up @rptaylor, it is much appreciated.  I wrote this long time ago and I probably had the impression (likely incorrect) that privileged container for daemonset is somehow different from privileged container in a regular pod.
And yes, I meant to say privileged mode is needed with health check because of this:
https://github.com/ROCm/k8s-device-plugin/blob/master/cmd/k8s-device-plugin/main.go#L104
The device plugin (without health check) usually doesn't need to be privileged because it just does the allocation without accessing the hw itself.  I might need to rethink how I do health check.
I would be happy to merge this as is or if you want to further rephrase base on what I wrote here I would be happy to wait as well.  Please let me know.

@y2kenny Updated, ready to go.
Could you also have a look at https://github.com/ROCm/k8s-device-plugin/pull/29#issuecomment-2036001985 https://github.com/ROCm/k8s-device-plugin/issues/57  if you get a chance? Thanks!


Spaces for testing CI integration.

It seems that travis-ci check failed. Is there anything we need to do?

Seems like checkstyle was not done on one of the previous commits.  I will fix this.

It appears that travis-ci has been successfully triggered on this pull request. Thus we don't need to commit dummy pull request to verify that it is working.


May I know Azure workload identity works for aks virtual-node-aci-linux

Currently, we are using Azure AD Pod Identity for our aks clusters.
We are exploring Azure AD workload identity and able to install using the below links and see it works in nodes as per the given example.
https://azure.github.io/azure-workload-identity/docs/introduction.html
https://github.com/Azure/azure-workload-identity
As mentioned in the 7th point or end of this page, https://azure.github.io/azure-workload-identity/docs/quick-start.html
I have deployed the workload and am able to access the key vault secret via the azure token.
Then I have updated the yaml with nodeSelector & tolerations to install in the virtual-node-aci-linux. Upon deploy, the pod is running but not able to access the keyvault secret.
Deploy pod:
apiVersion: v1
kind: Pod
metadata:
  name: quick-start-vk
  namespace: ${SERVICE_ACCOUNT_NAMESPACE}
spec:
  serviceAccountName: ${SERVICE_ACCOUNT_NAME}
  containers:
    - image: ghcr.io/azure/azure-workload-identity/msal-go:latest
      name: oidc
      env:
      - name: KEYVAULT_NAME
        value: ${KEYVAULT_NAME}
      - name: SECRET_NAME
        value: ${KEYVAULT_SECRET_NAME}
  nodeSelector:
    kubernetes.io/role: agent
    beta.kubernetes.io/os: linux
    type: virtual-kubelet
  tolerations:
    - key: virtual-kubelet.io/provider
      operator: Exists
    - key: azure.com/aci
      effect: NoSchedule

Error when running kubectl logs podname:
E0215 15:21:21.216383       1 token_credential.go:43] 'failed to read the service account token from the filesystem' err='open /var/run/secrets/azure/tokens/azure-identity-token: no such file or directory'

We haven't tried running it in a virtual node but I can give it a try.
Meanwhile, could you confirmed that the pod has been mutated (i.e. `kubectl describe quick-start-vk -n ${SERVICE_ACCOUNT_NAMESPACE} and check for injected properties described in https://azure.github.io/azure-workload-identity/docs/installation/mutating-admission-webhook.html)

I think yes
kubectl describe pod quick-start-1 -n default
Name:         quick-start-1
Namespace:    default
Priority:     0
Node:         virtual-node-aci-linux/
Start Time:   Thu, 17 Feb 2022 07:57:25 -0500
Labels:       <none>
Annotations:  <none>
Status:       Running
IP:           zzz.zz.104.4
IPs:
  IP:  zzz.zz.104.4
Containers:
  oidc:
    Container ID:   aci://3ff8ade75zzzzzzzzzzzzzzzzzzzzzzaae59de1f016293
    Image:          ghcr.io/azure/azure-workload-identity/msal-go:latest
    Image ID:
    Port:           <none>
    Host Port:      <none>
    State:          Running
      Started:      Thu, 17 Feb 2022 07:57:25 -0500
    Ready:          True
    Restart Count:  283
    Environment:
      KEYVAULT_NAME:               azwi-kv-tmp-0e1c
      SECRET_NAME:                 tmp-azwi-secret
      AZURE_CLIENT_ID:             zzzzzzz-9zz9-4zze-zzzz-afazzzzzbd6
      AZURE_TENANT_ID:
      AZURE_FEDERATED_TOKEN_FILE:  /var/run/secrets/azure/tokens/azure-identity-token
      AZURE_AUTHORITY_HOST:        https://login.microsoftonline.com/
    Mounts:
      /var/run/secrets/azure/tokens from azure-identity-token (ro)
      /var/run/secrets/kubernetes.io/serviceaccount from workload-identity-sa-token-bmlsv (ro)
Conditions:
  Type           Status
  Ready          True
  Initialized    True
  PodScheduled   True
Volumes:
  workload-identity-sa-token-bmlsv:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  workload-identity-sa-token-bmlsv
    Optional:    false
  azure-identity-token:
    Type:                    Projected (a volume that contains injected data from multiple sources)
    TokenExpirationSeconds:  3600
QoS Class:                   BestEffort
Node-Selectors:              beta.kubernetes.io/os=linux
                             kubernetes.io/role=agent
                             type=virtual-kubelet
Tolerations:                 azure.com/aci:NoSchedule
                             node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
                             node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
                             virtual-kubelet.io/provider op=Exists
Events:                      <none>

This might be a bug in virtual-kubelet/azure-aci with service account token projected volumes. I see projected volume support was added as part of this PR. The check for service account projected volume assumes the token is stored in a Kubernetes secret: https://github.com/virtual-kubelet/azure-aci/blob/master/provider/aci.go#L1740-L1745 which isn't really the case. While default service account token is stored in a Kubernetes secret, the projected service account JWT token are not.
@feiskyer for azure-aci

Hi, @chewong did you get a chance to try in virtual node?
I am a bit confused with the above comment, the problem is with azure-aci, so it's already fixed and we can update the azure-aci with the latest or wait?
Please mention if I missed anything.

I am a bit confused with the above comment, the problem is with azure-aci, so it's already fixed and we can update the azure-aci with the latest or wait?

The bug still exists in azure-aci. The PR I linked above added support for projected service account token volumes, but the but the projected service account token volume is incorrect. I would recommend opening an issue here.

The bug is being tracked in azure-aci: https://github.com/virtual-kubelet/azure-aci/issues/189.
Closing this issue now. Please feel free to reopen if you've any questions.


[Release Radar Request] Uno Platform 5.2 Release

Open Source Project name
Uno Platform
What is your project?
Uno Platform is an open-source platform for building single codebase native mobile, web, desktop, and embedded apps quickly. It allows C# and WinUI XAML and/or C# code to run on all target platforms while allowing you control of every pixel.
Version
5.2
Date
April 22, 2024
Description of breaking changes
First and only true .NET Single Project for Nine Platform Targets across Mobile, Web, Desktop, and Embedded.
Introducing Uno.SDK Features for easy NuGet package management.
Multi-Window support.
Enhanced Skia renderers for improved performance.
GitHub Repo
https://github.com/unoplatform/uno
Website
https://platform.uno/
Link to changelog
https://aka.platform.uno/blog-5-2
Social media
https://x.com/UnoPlatform/status/1782496737271087537
Anything else to add?
This release adds new large features and a new project structure, but technically no breaking changes so it did not necessitate a major version bump.
We had 2400 commits included in this release compared to less than 1500 commits in a typical release.

As mentioned via Twitter DMs, thanks for submitting, and we're really excited to feature this project. The Release Radar features major version releases. Please submit again when you have version 6.0 and we'll feature you 😄


Location can get lost, when editing the job title

This might be a bug in the Geo Module

@TiSiE this was done, wasn't it?

Geo search seems completely broken - therefore, this cannot be tested.

Thanks. Now the location remains when editing again the same jobs.
However, the location does neither show up in the overview page (jobboard) nor does the geo-search take it into account (whatever location I search for, my new test job shows ups).

Sorry, that is a problem with the yawik/Solr module


A problem with typing --delay30 string by xdotool

Hi Marty!
I use bemoji -t with instant typing parameter to paste an emoji character into an active input. I've discovered that xdotool also typing a following string: --delay30:

So I decided to fix it, here is my PR: https://github.com/marty-oehme/bemoji/pull/2

Good catch, I knew there was something left behind when switching my code to enable wtype/ydotool.
I'll check out the PR later today and merge it accordingly!

Thank you!


Merge master to release-4.0 branch to pick bugifx #6692 to 4.0.0-beta.1

What have you changed?
This PR merges master to release-4.0 branch in order to pick bugfix #6692 to 4.0.0-beta.1
What is the type of the changes?

Misc (other changes)

How is the PR tested?

Unit test
Integration test

/run-all-tests


Bug: TPC-DS_query57 fails with Tried to unproject agg expr not found in provided Aggregate!. error (Postgres acceleration)

Describe the bug
Run TPC-DS_query57 below with Postgres acceleration
https://docs.snowflake.com/en/user-guide/sample-data-tpcds
with v1 as(
  select i_category, i_brand, cc_name, d_year, d_moy,
        sum(cs_sales_price) sum_sales,
        avg(sum(cs_sales_price)) over
          (partition by i_category, i_brand,
                     cc_name, d_year)
          avg_monthly_sales,
        rank() over
          (partition by i_category, i_brand,
                     cc_name
           order by d_year, d_moy) rn
  from item, catalog_sales, date_dim, call_center
  where cs_item_sk = i_item_sk and
       cs_sold_date_sk = d_date_sk and
       cc_call_center_sk= cs_call_center_sk and
       (
         d_year = 1999 or
         ( d_year = 1999-1 and d_moy =12) or
         ( d_year = 1999+1 and d_moy =1)
       )
  group by i_category, i_brand,
          cc_name , d_year, d_moy),
v2 as(
  select v1.i_category ,v1.d_year, v1.d_moy ,v1.avg_monthly_sales
        ,v1.sum_sales, v1_lag.sum_sales psum, v1_lead.sum_sales nsum
  from v1, v1 v1_lag, v1 v1_lead
  where v1.i_category = v1_lag.i_category and
       v1.i_category = v1_lead.i_category and
       v1.i_brand = v1_lag.i_brand and
       v1.i_brand = v1_lead.i_brand and
       v1.cc_name = v1_lag.cc_name and
       v1.cc_name = v1_lead.cc_name and
       v1.rn = v1_lag.rn + 1 and
       v1.rn = v1_lead.rn - 1)
select  *
from v2
where  d_year = 1999 and
        avg_monthly_sales > 0 and
        case when avg_monthly_sales > 0 then abs(sum_sales - avg_monthly_sales) / avg_monthly_sales else null end > 0.1
order by sum_sales - avg_monthly_sales, 3
limit 100;

Native query completes successfully, but Spice fails
Query Error Internal error: Tried to unproject agg expr not found in provided Aggregate!.
sql> .error
Status { code: InvalidArgument, message: "Internal error: Tried to unproject agg expr not found in provided Aggregate!.\nThis was likely caused by a bug in DataFusion's code and we would welcome that you file an bug report in our issue tracker", source: None }

Close as duplicate with https://github.com/spiceai/spiceai/issues/2650


Forward models

I will sort out how to resolve this later -- for now this is my first working(?) draft of the new forward models.

@julesfowler Is this for v0.3 or the next version?

@hover2pi I figured this was for the next version.

@bourque Can you review this?

Sorry to ignore @hover2pi's review, but wheels must be in motion!


Enable Tailscale's Funnel feature

Draft because can be merged only after #196 is merged/settled
Proposed Changes
As an addition to the inbound HTTPS proxy, this enables Tailscale's Funnel.
Similarly to the HTTPS proxy, this currently works only on port 443 and only for HA access. This can be later modified when Tailscale's WEB-UI will provide some configuration options.
Related Issues

Looks good to me, thanks. #new-feature
Rel.: #166

Not stale.

Anything we can do to get this merged?

How can the "🏷 Verify PR has a valid label" issue be resolved? Is that blocking this being merged in? @lmagyar

Only repo owners can add labels, review PRs, etc.

not stale

Okay come on, how can we resolve this label issue? Do one of the repo owners need to add the label? This is so close!

Until it is merged, you can use my fork of this repo (with the Funnel feature and other useful stuff) at: https://github.com/lmagyar/homeassistant-addon-tailscale


Update Path Example in GraphQL demo

The path example used to follow a route through dependencies in a container image, now it returns a path through the golang type node. Find a different example or update the text.

Let's add node filters to force it to go in the direction we want?

Yes, sounds good. We could run as is and then have a second example with a filter.


fix(select): required validation refactor

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Absence of Pan-STARRS data

There is a match with a Pan-STARRS object. However, click to "Closest Pan-STARRS object, apparent" does not show anything. Morever, below in "Pan-STARRS DR2 Stacked" table, click to the object leads to the "No records found".
Ex.: https://ztf.snad.space/dr8/view/821207100004043
Kostya's comments:
It happens in Pan-STARRS that the object exists but the observations do not. More precisely, there are only upper limits. However, in stack image the object can be seen, that's why he is given in the table "Pan-STARRS DR2 Stacked".

There are actually two issues

Light curve issue: we probably could deactivate check-box and change text to something like "Pan-STARRS (no detections)".
Table issue: we can always put a link to a stacked table instead of detections table


0 Flowpipe Handling

Gracefully handle flowstar calls that return 0 flow pipes, i.e. when the follow occurs

Computation not completed: 0 flowpipe(s) computed.
Please try smaller step sizes or larger Taylor model orders.

Currently this produces a parsing error that is hard to decipher.

As you do in https://github.com/agerlach/Flowstar.jl/issues/9 looks good to me


[FLINK-4559][kinesis-connector] Fix AWSUtil.getCredentialsProvider() to not return null

This mainly fixes the Kinesis producer to correctly set credentials on AWS's KinesisProducerConfiguration when using the AUTO option.
Previously the producer was setting credentials for KPL to null as returned from AWSUtil#getCredentialsProvider. Now the method returns a DefaultAWSCredentialsProviderChain instead.

Looks good to me.
Should we also create a ticket to make AUTO the default as this checks for credentials in multiple places?
http://docs.aws.amazon.com/java-sdk/latest/developer-guide/credentials.html

Thanks for the review @greghogan.
I think it makes sense to let AUTO be the default, as the usual use case for most AWS users is to auto-detect the credentials delivered to instances by AWS's metadata service. Changing this should not break user code either. Would you like to open the ticket for that?

Merging ...


Classes

Merge classes branch

Is this the move to gradle? That move was motivated by the other dashboard project right? It's an enabler?

Hang on this is the "classes" repo, what we merging here?! Shall we squash these as a single commit?

I deleted the old classes repo, forked it from the base xp-dojo repo, and this merges the classes branch (xp-dojo-classes:classes) into the master branch of classes (xp-dojo-classes:master)


Prefer local identifiers in auto-complete

I've noticed since (I think) the new ML-based auto-complete was added that IntelliJ will now suggest identifiers that are defined in libraries I have not even imported. That can be a delightful feature in some cases. But when I've typed the first couple of letters of a local variable declared on a previous line, it's really likely that that's the identifier I'm typing, and I didn't decide to turn my program into a web app:

In fact, I find myself so accustomed to auto-complete naturally suggesting my local variable that I often hit tab to accept the completion before realizing it picked the wrong thing. Then if I'm not careful to immediately undo it, I end up with a dangling import to an unused library that I need to remember to scroll up to and delete.
Is it possible for auto-complete to prefer in-scope identifiers over the ML results?
(In cases where I don't want to refer to a local identifier, or where there are multiple options, the ML has been a wonderful improvement.)

Sorry for the long delay in responding. I believe the issue you're seeing is that IntelliJ re-orders the list that the server sends using several heuristics. One of those heuristics is that exact matches should appear first in the list.
@jwren Is there any way to disable IntelliJ's re-sorting behavior?

Sorry for the long delay in responding. I believe the issue you're seeing is that IntelliJ re-orders the list that the server sends using several heuristics. One of those heuristics is that exact matches should appear first in the list.
@jwren Is there any way to disable IntelliJ's re-sorting behavior?


Update while module installed

Hey guys,
I have quick question: Is it ok, to update the module while it's installed in the goggles (not powerd up)?
Greets

It depends on your particular module but I would recommend taking it out. The RealAcc version tries to backpower the goggles through the 5V rail (without success!).

I'm using the Realacc module. Can the backpower damage the googles?

It could make the voltage regulator a little upset, but not sure about real damage. The main problem is that (assuming it's powered over USB) your power source might go overcurrent.
Still strongly advise just taking it out!

Ok. Thank you very much!


New crates-io release?

It'd be nice to get the crossbeam-channel upgrade live.

@a8m ping

@a8m ping

Thanks for the reminder @kornelski. A new version was released (v1.0.4).
Closing.

Thanks for the reminder @kornelski. A new version was released (v1.0.4).
Closing.


{Interactive} Configurations to support error assistance enable/disable

Related commands
Syntactically incorrect commands
Description
Supports configurations for error assistance targeting beginners making syntax error in flags, command structure, or preset parameter values. Early version that supports the aforementioned syntax errors but does not yet recognize error relating to custom parameter values such as a non-existent resource group. The feature provides an explanation of the user's errors and a remedied command suggestion after traditional error messages.
Two separate configuration enable the feature for interactive mode and the default CLI. It is enabled by default in interactive mode and disabled by default outside of interactive mode. These configurations can be set as follows:
az config set core.error_assistance=True/False
az config set interactive.assistance=True/False
The interactive configuration is dependent on the additions in this PR. See the relevant azure-cli PR here:
https://github.com/Azure/azure-cli/pull/27256
Example:
Incorrect Command:
"""
keyvault create --resource-group 't-interns2' --'testKeyvault' --location 'eastus'
"""
Output:
"""
Issue:
The --name flag is missing before the resource name.
Corrected Command:
az keyvault create --name testKeyvault --resource-group t-interns2 --location eastus
"""
Note: Api key and endpoint have been set as environment variables for security. Edits needs to be made to make it generalizable to all users.
Builds upon copilot for interactive linked below:
https://github.com/Azure/azure-cli-extensions/pull/6600/files

Interactive

This PR is superseded by a newer one https://github.com/Azure/azure-cli-extensions/pull/6966


change name to zzz

because it's more type safe

I don't get the joke.

It would make the language sound like a snooze

it's ambiguously ambiguous as we don't know if the z is derefencing itself or the other z
is zz z(z) or (z)z, or the double-z operator? perhaps a single z is better.
but i think the triple-z has the advantage that it's definitively ambiguous. there's no way we can resolve what it references, so it's a clearer ambiguity than the current name, and therefore should be preferred.

https://github.com/void-linux/void-runit/blob/master/zzz.8

Unfortunately now that it's all over the internet, changing the name isn't reasonably anyway.


Switch from TravisCI to something else, like CircleCI

TravisCI seem to have a 50% chance of producing a false negative when running the unit/integration tests. It has become a major annoyance having to click the «restart build» button every time the project build status is failing.

An alternative to CircleCI is SemaphoreCI. I should investigate.

https://circleci.com
https://semaphoreci.com

I've bumped the timeouts on some tests that target ssl operations. Seems to work for now.

I really should switch to some alternative to travis. The tests can fail on occasion when run locally, but for some reason it is almost a guarantee that they fail on travis, for what-ever reason.

In 0.8.2 we switched to semaphore! 🎉


new paper

https://www.ncbi.nlm.nih.gov/m/pubmed/27751941/?i=2&from=power jd
please comment on its relevance
@gkiar

looks awesome a quick scan through (got GREs tmr so I'll do a more thorough
read after); once we finish fMRI pipeline, might be cool to look into
finding a fMRI dataset that also collected physiological data during the
scan (I think HCP does this?), analyze, and map how signal fluctuates with
different physiological measures.
On Fri, Nov 25, 2016 at 12:33 PM, joshua vogelstein <
<EMAIL_ADDRESS>wrote:

Assigned #121 https://github.com/neurodata/ndmg/issues/121 to @ebridge2
https://github.com/ebridge2.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/neurodata/ndmg/issues/121#event-872325202, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AIeNWzy_U9ydEHzAFec4LbaFWatN-Zu4ks5rBxv7gaJpZM4K8oE4
.

--
Eric Bridgeford
ericwb.me

i think HCP does.  gary glover has as well.
but, we want to put in into the context of advancing neurobiology, not just addressing this technical question...

we incorporated this into ndmg-f


Multiple clients aren't working

Environment
nuxt: latest
nuxtjs/apollo: next
windows 11
Describe the bug
when using multiple clients, only the default or first client is detected, no other client's data is showing on frontend. I have tested different graphql endpoints to test that only one client is working at a time.

Expected behaviour
multiple clients like shown in the documentation and playground in this repository should work as expected with multiple graphql endpoints working.
Reproduction
No response
Additional context
No response
Logs
No response

#22


awscli: 1.11.30 -> 1.11.35

Motivation for this change
Fixes #21591
Things done

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

[ x] NixOS
[ ] macOS
[ ] Linux

[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Fits CONTRIBUTING.md.

@FRidh TravisCI is not designed to handle this particular pull request. What are we going to do now?

Just ignore Travis, its not reliable enough.

In the past (b2d9b48) I moved awscli to python-packages.nix because it is used as a library as well and therefore I removed the namePrefix. This was added back in 323eb0649929d1580ba1f8cc5812dba33f9e354b because when it is used as an application we typically do not include the prefix.

@grahamc I did what you asked for. Can you please merge it?


Add TS_HAS_QUICHE feature variable.

Some of the quic features may only work with the quiche implementation. Having this will make easy in particular for unit tests to opt out depending of the variable value.
Exmaple:
Test.SkipUnless(
   Condition.HasATSFeature('TS_HAS_QUICHE')
)

This also makes the variable available for all binaries.
/opt/ats/bin/traffic_layout info --features | grep QUICHE
#define TS_HAS_QUICHE 1

[approve ci autest]

HAVE_QUICHE_H is used at some places. We might want to consistently use TS_HAS_QUICHE if we add it.

HAVE_QUICHE_H is used at some places. We might want to consistently use TS_HAS_QUICHE if we add it.

you mean change all the HAVE_QUICHE_H usage and use TS_HAS_QUICHE instead?

you mean change all the HAVE_QUICHE_H usage and use TS_HAS_QUICHE instead?

Yes, I'm fine with either one but using the both may cause confusion.

[approve ci rocky]

convert to draft, I'm not happy with this, will re-open once I'm satisfied.


Feature Request: Enabling/Disabling package from appsettings/DI

Hi Jesper,
I'd like to suggest a feature request for the option to enable/disable preview. This option would be useful for projects that share a common code base and are not headless - boilerplates. This could be a great option for the package registration with the option to disable/enable through settings.
I was investigating a bit how this could be done, but as I saw that we are loading the configuration from appsettings and then we use it from the dashboard into a database. We would need somehow to change the endpoints behaviour and option to control. Or we could change the behaviour and only use appsettings (or doing the registration from DI) for the package enabling/disabling and when disabled then greying out the dashboard in backoffice until it is again enabled.
Please let me know what you think.
Cheers,
Adrian

Hi @aochmann Thank you for sharing your feature request :-)
Do you want the plugin to be able to disable the preview button for the entire Umbraco installation, meaning all sites in the Umbraco installation or only for specific sites in a Umbraco installation?
Yes you can configure the package from either appsettings.json or from the UI. If you have configuration in the appsettings.json file the UI will be disabled and not saved in the database. If you have no configuration in the appsettings.json file you can use the UI and the settings will be store in the database.

Hi @aochmann Thank you for sharing your feature request :-)
Do you want the plugin to be able to disable the preview button for the entire Umbraco installation, meaning all sites in the Umbraco installation or only for specific sites in a Umbraco installation?
Yes you can configure the package from either appsettings.json or from the UI. If you have configuration in the appsettings.json file the UI will be disabled and not saved in the database. If you have no configuration in the appsettings.json file you can use the UI and the settings will be store in the database.

Hi @jesperweber
sorry for the late answer.
Yes disabling the package fully from configuration. Something like that:
"HeadlessPreview": {
    "Enabled": false,
    "TemplateUrl": "https://mysite.com/api/preview?slug={slug}&secret=mySecret"
}

and inside registration we could have options:
umbracoBuilder.AddHeadlessPreview(); //here will check if enabled or not

What do you think about that?

It makes sense and it's defiantly doable, I will look into it :-)

Hi @aochmann,
A new version 2.2.0 has just been released with the option to disable the headless preview and more :-)
Take a look at it: https://github.com/jesperweber/Our.Umbraco.HeadlessPreview/releases/tag/2.2.0


Join support builder

Codecov Report

Merging #1002 into master will decrease coverage by 0.18%.
The diff coverage is 47.36%.

@@            Coverage Diff            @@
##           master   #1002      +/-   ##
=========================================
- Coverage   54.29%   54.1%   -0.19%
=========================================
  Files          41      41
  Lines        7548    7561      +13
=========================================
- Hits         4098    4091       -7
- Misses       2934    2946      +12
- Partials      516     524       +8

Impacted Files
Coverage Δ

statement.go
66.53% <47.36%> (-0.57%)
:arrow_down:

xorm.go
61.53% <0%> (-4.62%)
:arrow_down:

engine_table.go
78.26% <0%> (-2.9%)
:arrow_down:

engine.go
61.17% <0%> (-0.34%)
:arrow_down:

dialect_postgres.go
75.24% <0%> (-0.33%)
:arrow_down:

session_update.go
51.59% <0%> (-0.32%)
:arrow_down:

session_insert.go
60.15% <0%> (-0.26%)
:arrow_down:

Continue to review full report at Codecov.

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


fatal error: Argument 1 passed to Zend\Mvc\Router\Console\Catchall::__construct() must be of the type array

Make sure that defaults are set https://github.com/zendframework/zend-mvc/blob/master/src/Router/Console/Catchall.php#L88
return new static(isset($options['defaults']) ? $options['defaults'] : []);

I've created PR #93 for it


vSphere Cloud provider: Volume detach is not issued when VM is not present kubernetes#33061

vSphere Cloud provider: Volume detach is not issued when VM is not present kubernetes#33061

Fixed in #40118


Nick: Watch (?-i:endopeak5)(?#bit.ly)

Nick requests the watch of the watch_keyword (?-i:endopeak5)(?#bit.ly). See the MS search here and the Stack Exchange search in text, in URLs, and in code.

(?-i:endopeak5)(?#bit.ly) has been seen in 0 true positives, 0 false positives, and 0 NAAs.

Approved by Jeff Schaller in Charcoal HQ


Please NOT post private advertisement here

I create an unofficial wechat group for everyone to communicate with
My wechat: 282028340

I delete an unofficial wechat advertisement here.


MAC OS X, Certificates, everything...still getting Certificate Authentication Error

So, I’ve done everything in the below for VS Code on my mac:

I can get to the site, the certificate is secure/valid. I’ve pulled it down to my laptop and in the VS Code SAS Settings pointed directly to it. I’ve done the environment variable = 0 on my terminal….and I’m still getting the unable to verify the first certificate.

Thank you,
Matt

Some things to double check:

Regarding the step 1.4 above, please make sure to select the option with "certificate chain". There're a few options there that may look similar, but other options won't work.
Regarding the enviornment variable, please make sure it affects your VS Code process. For example a variable set in one terminal may not work for applications started from other processes. I'm not an expert to Mac OS.
Also worth trying to upgrade your VS Code version to latest if not already.
Click Help > Toggle Developer Tools from the top menu bar to see if any errors from the console.

No feedback heard. Closing.


Question about HystrixCommand

Hello!
Should we must create a new Command class like FortuneServiceCommand and add it to the dependency injection container in Startup class?
Is there any way to use circuit breaker with Attribute?
For example,
[HystrixCommand(FallbackMethod = "RunRandomFortuneFallbackAsync")]
public async Task<Fortune> RandomFortuneAsync()
{
    var client = GetClient();
    var result = await client.GetStringAsync(RANDOM_FORTUNE_URL);
    _logger.LogInformation("RandomFortuneAsync: {0}", result);

    return JsonConvert.DeserializeObject<Fortune>(result);
}

//fallback method
public async Task<Fortune> RunRandomFortuneFallbackAsync()
{
    _logger.LogInformation("RunFallback");
    return await Task.FromResult<Fortune>(new Fortune() { Id = 9999, Text = "You will have a happy day!" });
}

Maybe the above code is more convenient to use.

Hi @catcherwong,
That could be a neat way to do it, but we do not currently have support for HystrixCommand via Attribute.
Another way of working with outbound http requests would be with DelegatingHandlers in HttpClientFactory. We experimented with the idea a bit several weeks ago, but have not yet come to a resolution on an ideal path forward - you can look at these branches in the samples repo for ideas about where we are thinking about going https://github.com/SteeltoeOSS/Samples/tree/hystrix-HttpClientFactory and https://github.com/SteeltoeOSS/Samples/tree/hystrix-factory-dave-ideas

@TimHess
Thanks for your answer!  Those ideas are vary good! And I will have a try for this.

Any more questions feel free to reach out to us


Fixed split issue (not working for '|')

I fixed a couple of the errors. @kkunal1408 There is another class of errors having to do with trace_template.
You can reproduce by running:
pytest -vv --runnightly -k Sanitized_civiR_DLDO_TOP -- tests/integration


output from rpc_mapproject

With ASP2.2, rpc_mapproject seems to try to write xml files in an unwritable location, and spews warning messages:
Warning: GdalIO: Unable to save auxilary information in /vsisubfile/3989_961434577,WV01_11DEC131600110-P1BS_R1C1-10200100150C8F00.ntf.aux.xml. (code = 1)
[repeated ~ 10 times]
I've seen this problem on an RHEL6 linux box and on a mac running OSx 10.8

I re-opened this issue in the GDAL bug tracker. I can reproduce this only with gdal_translate.

This is something we can easily fix ourselves with a patch to GDAL. Should be a one-line change.
The reason this should be fix is because for large runs it can create hundreds of MB of log files.
This fix should be mentioned in NEWS, I think users will appreciate it.


Clarifying Questions

Clarifying Questions
1. #1 Please include the Bootloader and Partitions in the release as well. 📥
2. I'm also quite confused about the chip8.txt file. Could you please explain it in more detail? 📝
3. I'm also quite confused about the file for connecting to WiFi. For what purpose does the device need a connection to WiFi? Is it for adding or deleting files through LittleFS or SDCard? 📶💻

#1 Please include the Bootloader and Partitions in the release as well. 📥

done.

I'm also quite confused about the chip8.txt file. Could you please explain it in more detail? 📝

This is, in fact, no longer used. The README contained stale information. I have updated it.
Rather than using a separate file (chip8.txt), at some point I decided to invent a new file format *.ec8 which has some options prepended before the actual CHIP8 data. Ultimately, I would have loved to support John Earnest's *.gif files, but I shied away from the processing required to extract the game data on the ESP32.

I'm also quite confused about the file for connecting to WiFi. For what purpose does the device need a connection to WiFi? Is it for adding or deleting files through LittleFS or SDCard? 📶💻

This is very much work in (slow, I admit) progress. My goal for this project is to create a gadget which allows writing code as well as playing games. The on-device memory editor and disassembler is a first step. With the web server, the idea was to create a simple IDE as a web form which could be used from eg. a mobile device. However, the code for this is yet to be written. First experiments proved difficult: I had some problems fitting the code into the memory of the device.

Actually your project is very cool. I'm very grateful for your hard work

Actually your project is very cool. I'm very grateful for your hard work


Support for stack

Hello! Thanks for writing this package binding.
I have an issue using this package with stack (both from including the package name into package.yaml and/or direct git repository reference into stack.yaml) and I'm failing to build my project.
I could build the library in isolation and as a dependency with cabal just fine though.
OS: OpenSUSE 15.3 Leap
Stack version: Version 2.7.5, Git revision ba147e6f59b2da75b1beb98b1888cce97f7032b1 x86_64 hpack-0.34.4
C's libfuse3 was installed from the official package manager fuse3-devel (version: 3.6.1-3.3.8)
Build log of (stack build):
Trying to generate configure with autoreconf in /tmp/stack-d952671704453c33/libfuse3-<IP_ADDRESS>/
libfuse3> configure
libfuse3> [1 of 2] Compiling Main             ( /tmp/stack-d952671704453c33/libfuse3-<IP_ADDRESS>/Setup.hs, /tmp/stack-d952671704453c33/libfuse3-<IP_ADDRESS>/.stack-work/dist/x86_64-linux-tinfo6/Cabal-<IP_ADDRESS>/setup/Main.o )
libfuse3> [2 of 2] Compiling StackSetupShim   ( /home/modotte/.stack/setup-exe-src/setup-shim-mPHDZzAJ.hs, /tmp/stack-d952671704453c33/libfuse3-<IP_ADDRESS>/.stack-work/dist/x86_64-linux-tinfo6/Cabal-<IP_ADDRESS>/setup/StackSetupShim.o )
libfuse3> Linking /tmp/stack-d952671704453c33/libfuse3-<IP_ADDRESS>/.stack-work/dist/x86_64-linux-tinfo6/Cabal-<IP_ADDRESS>/setup/setup ...
libfuse3> Configuring libfuse3-<IP_ADDRESS>...
libfuse3> build
libfuse3> Preprocessing library for libfuse3-<IP_ADDRESS>..
libfuse3> compiling .stack-work/dist/x86_64-linux-tinfo6/Cabal-<IP_ADDRESS>/build/System/LibFuse3/Internal_hsc_make.c failed (exit code 1)
libfuse3> rsp file was: ".stack-work/dist/x86_64-linux-tinfo6/Cabal-<IP_ADDRESS>/build/System/LibFuse3/hsc2hscall22993-0.rsp"
libfuse3> command was: /usr/bin/gcc -c .stack-work/dist/x86_64-linux-tinfo6/Cabal-<IP_ADDRESS>/build/System/LibFuse3/Internal_hsc_make.c -o .stack-work/dist/x86_64-linux-tinfo6/Cabal-<IP_ADDRESS>/build/System/LibFuse3/Internal_hsc_make.o -fuse-ld=gold -D__GLASGOW_HASKELL__=900 -Dlinux_BUILD_OS=1 -Dx86_64_BUILD_ARCH=1 -Dlinux_HOST_OS=1 -Dx86_64_HOST_ARCH=1 -Iinclude -I/usr/include/fuse3 -I.stack-work/dist/x86_64-linux-tinfo6/Cabal-<IP_ADDRESS>/build/include -I/usr/include/fuse3 -I.stack-work/dist/x86_64-linux-tinfo6/Cabal-<IP_ADDRESS>/build/autogen -I.stack-work/dist/x86_64-linux-tinfo6/Cabal-<IP_ADDRESS>/build/global-autogen -include .stack-work/dist/x86_64-linux-tinfo6/Cabal-<IP_ADDRESS>/build/autogen/cabal_macros.h -I/home/modotte/.stack/programs/x86_64-linux/ghc-tinfo6-9.0.2/lib64/ghc-9.0.2/unix-<IP_ADDRESS>/include -I/home/modotte/.stack/programs/x86_64-linux/ghc-tinfo6-9.0.2/lib64/ghc-9.0.2/time-1.9.3/include -I/home/modotte/.stack/snapshots/x86_64-linux-tinfo6/f9ac3f602e4f7d9c0347503494e57a84725c58d20ba3eac85bd77d188e49f3a3/9.0.2/lib/x86_64-linux-ghc-9.0.2/primitive-<IP_ADDRESS>-EikPDi9CXNiB9f5MDJybeY/include -I/home/modotte/.stack/programs/x86_64-linux/ghc-tinfo6-9.0.2/lib64/ghc-9.0.2/bytestring-<IP_ADDRESS>/include -I/home/modotte/.stack/programs/x86_64-linux/ghc-tinfo6-9.0.2/lib64/ghc-9.0.2/base-<IP_ADDRESS>/include -I/home/modotte/.stack/programs/x86_64-linux/ghc-tinfo6-9.0.2/lib64/ghc-9.0.2/ghc-bignum-1.1/include -I/home/modotte/.stack/programs/x86_64-linux/ghc-tinfo6-9.0.2/lib64/ghc-9.0.2/include -I/home/modotte/.stack/programs/x86_64-linux/ghc-tinfo6-9.0.2/lib64/ghc-9.0.2/include/
libfuse3> error: In file included from /usr/include/fuse3/fuse.h:19:0,
libfuse3>                  from Internal.hsc:66:
libfuse3> /usr/include/fuse3/fuse_common.h:791:4: error: #error only API version 30 or greater is supported
libfuse3>  #  error only API version 30 or greater is supported
libfuse3>     ^~~~~
libfuse3> /tmp/stack-d952671704453c33/libfuse3-<IP_ADDRESS>/In file included from Internal.hsc:67:0:
libfuse3> /usr/include/fuse3/fuse_lowlevel.h:22:2: error: #error FUSE_USE_VERSION not defined
libfuse3>  #error FUSE_USE_VERSION not defined
libfuse3>   ^~~~~
libfuse3>
Progress 1/2

--  While building package libfuse3-<IP_ADDRESS> (scroll up to its section to see the error) using:
      /tmp/stack-d952671704453c33/libfuse3-<IP_ADDRESS>/.stack-work/dist/x86_64-linux-tinfo6/Cabal-<IP_ADDRESS>/setup/setup --builddir=.stack-work/dist/x86_64-linux-tinfo6/Cabal-<IP_ADDRESS> build --ghc-options " -fdiagnostics-color=always"
    Process exited with code: ExitFailure 1

Thanks.

Nice to meet you!
The error message tells you that a C macro FUSE_USE_VERSION is not defined. This packages makes use of Cabal's buildinfo file, which defines the macro.
Perhaps Stack is not generating a libfuse3.buildinfo file, or not compatible with it. I'm afraid I don't think I have time to fix this by myself because I don't use Stack at all.
Try looking for libfuse3.buildinfo. It looks like that your log doesn't contain the output of ./configure, so Stack might have not run it. If Stack does run ./configure, it must be generated somewhere:
find -name libfuse3.buildinfo

@matil019 Thanks for the pointers :slightly_smiling_face: . After viewing the linked doc, I noticed haskell-libfuse3's Setup.hs file content is not identical to the snippet from the documentation page.
If I understand correctly from that documentation, defaultMain is for Simple build-type and doesn't fit well for Configure or other custom build?
Good news is, I managed to build the library with both cabal and stack after replacing the main = defaultMain with main = defaultMainWithHooks autoconfUserHooks in Setup.hs file. I also could build the examples and use the package as a library from other projects just fine with both cabal and stack too.

@modotte The new version is published to Hackage as <IP_ADDRESS>! Please take a look.

Building from source and git url works brilliantly now, unfortunately, I still couldn't build the one from Hackage (yes, including <IP_ADDRESS>). :slightly_frowning_face:
I'll try to investigate the potential cause.


Why time.sleep(0.5) is needed after agent.run() in tabular_q_learning.py?

I have some questions about below line.
https://github.com/Microsoft/malmo/blob/672a68971f88f6cef39642825ebccc1c261977fd/Malmo/samples/Python_examples/tabular_q_learning.py#L410

What is this sleep for?
Where does "0.5" come from?
Can I remove it?

It's there to give the mod time to reset. When the mission ends, the mod first sends a MissionEnded message to the agent host, and then it does some housekeeping before returning to the dormant state, ready for the next mission.
During this housekeeping stage, attempts to start a new mission will be rejected, so we wait half a second.
A better solution might be to have the mod return a "try again later" message during this housekeeping stage, rather than the "busy" message it currently returns. Then the agent code (or perhaps our AgentHost code) could respond to that and wait. But for now, the time.sleep() is a simple solution.

Thanks for your reply.
Without that time.sleep(0.5), my script occurs segmentation fault error randomly.
I'm now trying to reproduce it with minimum codes. When I catch it, I will post it......

Am assuming this is no longer an issue, and closing. Please reopen if you manage to reproduce it. Cheers.


search window does not work when entered japanese character

When I type in Japanese, nothing is found in the search.
Can you support Japanese search or hide the search window?

Ok, I have to include the ability to customize the pagefind plugin (https://lume.land/plugins/pagefind/#the-binary-file)

I have released v0.10.0, and you can configure the pagefind plugin to support japanese characters:
use.blog({
  pagefind: {
    binary: {
      extended: true
    },
  }
})


feat: Expose different hooks dynamically to inject different database

This environment configuration setting hook allows administrators to alter different database connection parameters on the fly based on user information and hook strategy. This can be use for a variety of purposes:

rewire a subset of users to use different database user accounts，for example, integrating with ldap
pass user related information to the database for logging or QoS purposes
custom, per-database-engine, environment-specific impersonation

SUMMARY

Although there is already a DB_CONNECTION_MUTATOR hook available to inject database connection logic on the fly, if we do not modify the code in superset/models/core.py within the Database.get_sqla_engine method, this injection will affect all data source connections. Specifically, if different data sources require different injection logic, then we need to make different modifications to the code within superset/models/core.py to handle the different database types. Therefore, I have added a DB_CONNECTION_MODIFIER hook (clearly, DB_CONNECTION_MUTATOR would be a better name, but it is already in use, so I used a synonym instead), which allows for different data sources to implement different injection logic on the fly, as long as these database injection logic classes implement the run method of the ImpalaURLModifier class. This increases the flexibility of injecting database connection logic on the fly.
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

TESTING INSTRUCTIONS

For example, when each user connects to the postgres data source, their use the current username to connect to the database, and the password is new_password_ str plus the username.
Add a new class PostgresDBConnectModifier in file superset/utils/database_connect_modifier.py
class PostgresDBConnectModifier(BaseDBConnectModifier):
    # When connecting to a postgres data source,
    # replace the default connection username and password

    @classmethod
    def run(cls, sqlalchemy_url: URL, params: dict[str, Any], username: str, *args: Any,
            **kwargs: Any) -> (URL, dict[str, Any]):
        new_password = cls._get_new_password(username)
        sqlalchemy_url.username = username
        sqlalchemy_url.password = new_password
        return sqlalchemy_url, params

    @staticmethod
    def _get_new_password(username):
        # Implement password generation logic
        return 'new_password_' + username

superset/config.py中
DB_CONNECTION_MODIFIER_ENABLED = True
DB_CONNECTION_MODIFIER: dict[str, type[BaseDBConnectModifier]] = {
    "postgresql": PostgresDBConnectModifier,
}

The user logs in to the superset page and queries the postgres database table in sqllab; or the underlying data table triggered by the chart page is the postgres data source.
ADDITIONAL INFORMATION

[ ] Has associated issue:
[x] Required feature flags:
[ ] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

[ ] Migration is atomic, supports rollback & is backwards-compatible
[ ] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[x] Introduces new feature or API
[ ] Removes existing feature or API

Hello, I found that all the checks related to docker pull failed. Is there anything I need to do?

Are you able to start by fixing the failed tests in the details of the pre-commit check?

Are you able to start by fixing the failed tests in the details of the pre-commit check?

Yeah，I fix the pre-commit hook errros and pushed the submission again! thanks you for help! :)

@betodealmeida this seems kind of in your wheelhouse -- are you able to review, or can you think of another committer who would be well-suited?


Issue-24: make hashable slice of errors by Error() and type. Works bad but doesn't panic at least

…d for chain but at least if doesn't panic

@TheZeroSlave  It would be really nice, if you merged it, even though it's not a perfect solution. It causes panics where you're not expecting at all, not allowing to log, for instance, mongo-driver command errors properly.


update proxy of release-7.1 to raftstore-proxy

What problem does this PR solve?
Issue Number: ref #4982
Problem Summary:
update proxy to raftstore-proxy
Proxy PR:
Including:\nSubmodule contrib/tiflash-proxy 23dea9183f..27108ee96b:

Merge pull request #325 from CalvinNeo/v2/merge-7.1-1
Fix ci_check script (#324)
Support proxy tests of simple write (#323)
Merge pull request #322 from CalvinNeo/update-7.1/merge-base
Support read data from tablet snapshot (#321)

What is changed and how it works?
Check List
Tests

[ ] Unit test
[ ] Integration test
[ ] Manual test (add detailed scripts or steps below)
[ ] No code

Side effects

[ ] Performance regression: Consumes more CPU
[ ] Performance regression: Consumes more Memory
[ ] Breaking backward compatibility

Documentation

[ ] Affects user behaviors
[ ] Contains syntax changes
[ ] Contains variable changes
[ ] Contains experimental features
[ ] Changes MySQL compatibility

Release note

None

/run-all-tests

/run-all-tests

/run-all-tests

/run-integration-test

/merge

/merge

/run-all-tests


Exit without watcher

Get exit data for a deposit locally, with just the transactionhash
rootChain.getDepositExitData({ transactionHash })
issue 223
Small edge case I ran into was that there is a possibility that someone makes multiple deposits of the same amount/token and are included in the same ethereum block. There is no way to tell which DepositEvent belongs to the transaction in question in this case, since the only info we have to filter the events are the depositor/token/amount/blocknumber. So the method returns an array of possible utxoPos when this happens. The user would just have to start exits on all of these positions in that case

Re: the edge case
Ethereum events are stored as transaction logs, so there is a way to get only the DepositEvent related to the tx, without filtering all past events. You can get the tx logs from the tx receipt. Something like
  const receipt = await web3.eth.getTransactionReceipt(txHash)
  // blknum will be the 3rd topic in the first event
  // (the 1st topic is a hash of the event signature)
  const blknum = web3.utils.hexToNumber(receipt.logs[0].topics[2])

@kevsul that simplified it a lot thanks!


doc: net: Enhance IEEE 802.15.4 documentation

Add a simple overview chapter to IEEE 802.15.4 documentation.
Signed-off-by: Jukka Rissanen<EMAIL_ADDRESS>

This needs more TLC. We probably need a documentation how the APIs are used.

Codecov Report

Merging #13513 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master   #13513   +/-   ##
=======================================
  Coverage    52.5%    52.5%
=======================================
  Files         318      318
  Lines       46527    46527
  Branches    10755    10755
=======================================
  Hits        24429    24429
  Misses      17199    17199
  Partials     4899     4899

Continue to review full report at Codecov.

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

Updated according to comments.


1D noise?

iv'e search for 1D but only found 2 & 3D could you please expand the library to support 1D?

Last commit was 2017 just so you know

Yeah I'm probably not adding 1d noise. Feel free to fork! You can get 1d noise by using the 2d noise functions and setting y=1 or something.

@josephg
I've added pull request about it
https://github.com/josephg/noisejs/pull/34


remove kubernetes resources

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
According to step 3 of the docs:

Note: As of June 4, 2024, the Expel Security Benchmark Report is no longer supported.

If I understand correctly, this means creation of the kubernetes_cluster_role, kubernetes_cluster_role_binding, along with updating the aws-auth ConfigMap is outdated.
Describe the solution you'd like
A clear and concise description of what you want to happen.
Remove the Kubernetes resources along with aws-auth config in docs.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Leave `em :woman_shrugging: they don't hurt anything.
Additional context
Add any other context or screenshots about the feature request here.
I'm only weakly convinced this is true so feel free to close if I've missed the mark.

@hall Thanks for calling out this potential discrepancy, we have this in our backlog to verify and address.

Any update on this?


[Dropdown] Position fixed parent makes the container render too far away from the trigger

Bug report
Current Behavior
When inside a position: fixed parent, the container of the dropdown goes a little bit too much away from the trigger as seen on the screenshot.

Expected behavior
The container should be right below the trigger, since no offset property is set.
Your environment

Software
Name(s)
Version

Radix Package(s)
react-dropdown-menu
0.1.6

React
n/a
16.9.1

Browser
Google Chrome
101.0.4951.41 (Official Build) (64-bit)

Hi @RodolfoSarkisRocha, we are aware of the issue and are already tracking it here: #370, #781.
I will close this one as a duplicate.
✌

Oh, sorry about that and thanks for the awesome job!


Update word limit

Context
Increasing word limit for references.
Changes proposed in this pull request
Simple change in the form and the view
Guidance to review
Is there anywhere else we need to look for changes?
I have spoken to the Provendor team and we don't have any concerns about knock-on effects to the API. See https://ukgovernmentdfe.slack.com/archives/CN1MCQCHZ/p1605883511484200
Link to Trello card
https://trello.com/c/QYDlevJV/2523-dev-increase-word-limit-for-references-to-500wds

It would be nice to add a test to cover this change. Something similar to what we have in the further_information_form_spec.rb. But currently the reference_feedback_form doesn't have it's own test file and it looks like the validations are being carried out in reference_review_form_spec instead. I've spent some time trying to add a test but I can't make it stick.
If you think adding a test for this is worth it then I'd appreciate a bit of pairing to see what I'm missing here.


Update prisma-fmt tests to be automatically tracked

Currently, tests in prisma-fmt (code-actions and autocompletions) need to be manually added to a list of scenarios.
It would be nicer if these were automatically found rather than needing to be manually added.

Hi there,
As part of our effort to clean up our GitHub repo, we’re closing this issue to help focus on features and improvements that align with our focus areas and those of our community.
This issue was originally created for internal tracking purposes, but if you feel this is important to you, feel free to reopen the issue and get like-minded users to upvote as we will prioritize fixing issues based on community interest.
For more insight into our priorities and how we’re thinking about the future of Prisma, please see our blog post: https://www.prisma.io/blog/prisma-orm-manifesto.
Thank you for your understanding and support!


Importing ably_api_key results in key being null

When importing a basic setup like
terraform {
	required_providers {
		ably = {
		source = "github.com/ably/ably"
		}
	}
}

# You can provide your Ably Token & URL inline or use environment variables ABLY_ACCOUNT_TOKEN & ABLY_URL
provider "ably" {}

resource "ably_app" "app0" {
	name     = "app0"
	status   = "enabled"
	tls_only = true
}

resource "ably_api_key" "root" {
	app_id = ably_app.app0.id
	name   = "Root"
	capabilities = {
	  "[*]*" = ["*"]
	}
  }

And running terraform import ably_api_key.root "${APP_ID},${KEY_ID}" the resulting state is always null and can't be daisy chained into other resources.
┆Issue is synchronized with this Jira Task by Unito

I am still a bit skeptical about the solution.
The api clearly can retrieve the key, so can the ui. Forcing the user to specify the key is in my opinion making the process more complicated than it needs to be.
And for people like me who previously imported the resource we are stuck. Updating the provider won't help us.
Our only solution is to terraform state rm & terraform import again.
My proposed solution would have fixed everyone's resource with no extra action
On the other side if the fact that the api returns the key is a bug or something you don't want to continue then yes this is one solution. For example gitlab took another approach  and outright stated that the token is not present unless created.


Font size/weight doesn't work?

I've just started using Park-UI for a new project and I love it so far. Thanks for the effort you put into it.
However, I've encountered what seems to be a bug with the Typography component not honoring font sizes. Below is a screenshot from the documentation:

Am I missing anything here?

Seee #308


Concatenating high number of members requires too much memory?

When concatenating many members for a givensource_id I think I run into memory issues. For instance, when I query 30 members of EC-Earth3, for variables psl & sfcWind, for ssp245, the following won't finish on the small (5Gb RAM) and medium (16 Gb RAM) sized Pangeo Google Cloud Hub servers (but will for only 20 members, or for 30 members on the large (30Gb RAM server). Note this is before loading in the datasets.
The function that doesn't finish is the concat_members step below, regardless of splitting large chunks or not:
with dask.config.set(**{'array.slicing.split_large_chunks': True}): #join=outer pads NaNs which result in large chunks for timeseries that differ in length
    ddict_merged = combine_datasets(ddict,merge_variables_aligning_lonlat,match_attrs=['source_id', 'grid_label', 'experiment_id', 'table_id','variant_label'])
    ddict_concat = combine_datasets(ddict_merged,concat_members_aligning_lonlat,match_attrs=['source_id', 'grid_label', 'experiment_id', 'table_id'])

with these custom functions defined as:

def align_lonlat(ds_list):
    aligned_ds_list = []
    for ds in ds_list: #list of ds can't seem to be passed to xr.align instead
        a,b = xr.align(ds_list[0],ds,join='override',exclude=['time','member_id'])
        aligned_ds_list.append(b)
    return aligned_ds_list

def concat_members_aligning_lonlat(ds_list):
    aligned_ds_list = align_lonlat(ds_list) #override same-dimension lon/lat prior to concatenating (ensures lon/lats are not padded)
    return xr.concat(aligned_ds_list, dim='member_id', join='outer', coords='minimal',compat='override') #return xr.concat(ds_pick, dim='member_id')

def merge_variables_aligning_lonlat(ds_list):
    aligned_ds_list = align_lonlat(ds_list) #override same-dimension lon/lat prior to concatenating (ensures lon/lats are not padded)
    return xr.merge(aligned_ds_list, join='outer',compat='override')

I'm unclear why concatenating lazily opened datasets requires so much memory @jbusecke?
EDIT: we don't actually have to concatenate members before the subsetting has happened, and concatenating the subsetted data may cost less memory?

No longer an issue in the new workflow.


Minimal hand tracking distance is too short

I am impressed you guys got hand tracking in with v0.9.4, but I found that it's usefulness only goes out to about 4 to 5 feet before it loses confidence and resorts back to tracking just to the wrists. By comparison, the ol' Kinect v2 that I have can go out to nearly 10 feet before it can no longer detect the hands while still giving me whether its a fist, open, or "lasso".
I guess your models were only done at a desk and not an open space?

@JZharay You should still have joint values for the hand joint even if the confidence is set to NONE. There is a marked drop off in hand joint accuracy beyond 2m (from the camera) hence the no confidence value.

In Kinect v2 we had a hand state classifier for open / closed / lasso states separate to the body tracking algorithm. For Azure Kinect we have a new body tracking algorithm and we have not made a hand state classifier. This is something that could potentially be added in future if required, but another possibility is to do fully articulated hand tracking as in HoloLens 2. A state classifier can produce good results at longer distances but it only outputs one discrete label, whereas a pose tracker requires higher input resolution but can provide full 3D articulation.
I would like to understand the various scenarios for which users want hand tracking so we can move the technology in the right direction. What is your use case?
As @qm13 says, the hand joints are still tracked beyond 2m but we set the confidence to NONE to indicate that the accuracy of the joint positions is questionable.

@tobysharp-msft The hand state classifier was already (many times) required. Look here: https://feedback.azure.com/forums/920053-azure-kinect-dk/suggestions/38154784-hands-support-in-body-tracking It would provide means for interaction with virtual objects. The hand states could also be used to emulate taps, drags, drops, interactions with the UI, like button presses, etc. I thought you have already started it and even expected it in the next Body SDK update :(
Of course, fully articulated hand tracking would be always preferred, but even then such kinds of discrete states (like open, closed hands, finger pinches, presses, touches, etc.) will be again very valuable to the developers. The beauty of Kinect has always been that the user is the controller, without carrying any extra gears, like headsets, controllers, trackers. etc..

Here is a new feature request regarding hand states: https://feedback.azure.com/forums/920053-azure-kinect-dk/suggestions/38933653-classifier-for-hand-states
The original one: https://feedback.azure.com/forums/920053-azure-kinect-dk/suggestions/38154784-hands-support-in-body-tracking was closed half completed.

As someone who has built a direct manipulation music interface with the existing Kinect V2 classifier poses (see holofunk.com), I strongly prefer the classifier approach. Anyone doing prototyping or experimental work with the Kinect is very likely to lack the resources to develop their own classifier.  It is a significant effort.  The feature will be much more widely adopted if you can develop a classifier.  The basic Kinect poses are the obvious start, with the possible addition of one or two more (perhaps a thumb-and-finger "bang-bang" pointing variation, or a "Spock greeting" hand pose -- whatever is distinct enough to be classifiable).
Full finger data seems unlikely to be reliable enough to do much with, but maybe the new sensor would surprise me. But please, please develop a classifier -- MSFT has far more resource to make a good one than anyone external is likely to have for some time.

@RobJellinghaus That's very useful info, and points well made. Thank you. I hope to be able to come back with news on this in the near future.

You're welcome, I sincerely appreciate your receptiveness to the feedback.
FWIW one of the biggest issues with the Kinect V2 hand pose classifier is accuracy when the hand is at a low angle and/or in front of the torso.  I had to build my app to specifically work around the major loss of accuracy when the hand is in front of the torso; the classifier works well when hands are out to the side, but much less well in other poses.  If this is something that the new classifier's training data set can address (having lots of training poses with hands in front of torso from the camera's perspective), it would be a significant improvement even if only the Kinect V2 poses are detected.

It's close to 3 years and as far as I know there hasn't been any change in this direction? What's going on?

This issue was closed by the team over three years ago, so as far as the team is concerned, nothing is going on and no changes are planned.
Given that the Kinect for Windows device gave very unreliable hand tracking data, I don't in retrospect think the Azure Kinect could have done a much better job. I'm moving to non-hand-pose based approaches for my Azure Kinect app at this point.

Yeah we've had to finally scratch using a Kinect at all, sadly. It's quite sad because from the hardware point it seems more than possible. In 3D view it reliably distracts the thumb from the hand without any issues even multiple meters away...

Truly bummed the azure doesn't have any way of detecting hand state. It's unfortunate the Azure is missing this feature without any recommendation for migration/fallback implementation.


Add option for output dir

Add option for output dir.
Allowing output dir to be configured makes it easier to compare across multiple different endpoints.

Please change this to OutPath and allow specifying the entire output file path instead of just the dir.


Based on discussion in #24

Removed ConnectionPool and exposed the implementation specific details of HikariCP more fully in ManagedDatasource. Might later add a utility to serialize and deserialize the HikariConfig. Also attempts to fix some formatting in the Javadoc

It would probably be useful to turn ManagedDatasource into a decorator by implementing the DataSource interface (and maybe Closeable as well). All it would need to do is delegate all of the methods to the wrapped DataSource.

I'll look into it.

Actually, never mind. The unique functionality of ManagedDatasource is in the additional methods that are not part of the DataSource interface. Treating it as a decorator wouldn't be useful in any case.

@ProgrammerDan do we still want this?

No.


Fix fetching assets in Web Workers

Objective
This PR fixes #12125
Solution
The logic in this PR was borrowed from gloo-net and essentially probes the global Javascript context to see if we are in a window or a worker before calling fetch_with_str.

Not sure what the procedure/rules are here, but I would like to suggest that this be added to the 0.13.1 milestone.

unblocks your use case, not a breaking change, and it works 👍

@mockersf do I need to rebase this PR onto the release-0.13.1 branch?

no, once this PR has been approved by someone else, we'll merge it to main then cherry pick to the release branch

I noticed that the check "validation jobs / run-examples-on-wasm (pull_request)" was skipped, is there any reason for this? It seems like a relevant check for this PR.

run-examples-on-wasm does not run until this PR gets added to the merge queue. You can ignore it for now :)