Addition of patch 1.29 handle-related natives.

Includes wrappers for unit, item and effect native methods.
Changelog for each commit lists particular methods that have been accounted for.

Looks like the blizzard.j/ common.j are not yet updated on the serves thus native method references cannot be resolved.

@crojewsk Cool, nice stuff.
And yes, I am currently working on 1.29 support for the compiler under this branch https://github.com/wurstscript/WurstScript/tree/1.29
However I'm not sure yet how we should handle backwards compatability.
Probably the natives will just be void when on older patches or something.

In typical environment one must have backwards compatibility in mind, however, here in war3, once patch hits live each user is basically obligated to update his/her client before enjoying the game.
Of course you can still stick to golden principles and add compatibility to older versions. In such case, "do nothing" or return "default(T)" for void and return type functions respectively should suffice.

I don't think that users are obligated. Quite the opposite actually.
There are big communities in asia and russia that are still using patch 1.24 and 1.26.
And I doubt that all will ever move to latest patches.

Okay, the build still fails because your calls are missing the Blz prefix.

Idk for 1.24, but as far as I know in Russia pretty much everybody uses 1.26a. Though I believe as soon as there will be hacked version, our community will slowly transit on the new patch - mainly due to the awesome 24 players feature.

well it would be a branch, not a fork, but yes. Though I don't like having two branches to maintain, so it might be better to just ignore and warn with lower game versions.
The stdlib shouldn't require the new natives in any existing systems as I see it.
@crojewsk will you fix this?!

Adding new player native:
native BlzDecPlayerTechResearched takes player whichPlayer, integer techid, integer levels returns nothing

Nice 🍉
Now you just need to give your first star to the https://github.com/wurstscript/WurstScript repo 😄


Feature-Request: Make kill method of process configurable

I'm trying to stream my canon eos 600d feed with this config:
streams:
  canon: exec:gphoto2 --capture-movie --stdout

This works exactly one time. But the process is killed immediately (calling os.Process.Kill) by go2rtc after closing the stream without giving gphoto2 enough time for a proper cleanup.
gphoto2 is waiting for the SIGINT signal, therefore my request is to make that configurable.

https://github.com/AlexxIT/go2rtc/releases/tag/v1.9.0


Redundant validation on chart name

Hello,
I'm setting up a workflow with the following components:

Private Dockerhub OCI repository where my Helm Charts are stored
EKS Cluster
Below Kustomizations stored in a Private Github repo
Flux deploying my Kustomizations to my EKS Cluster

I've setup the following HelmRepository:
apiVersion: source.toolkit.fluxcd.io/v1beta2
kind: HelmRepository
metadata:
  name: my-dockerhub-oci
  namespace: flux-system
spec:
  type: "oci"
  interval: 1m
  url: oci://registry-1.docker.io/my-org
  secretRef:
    name: dockerhub-credentials

and the following HelmRelease:
apiVersion: helm.toolkit.fluxcd.io/v2beta2
kind: HelmRelease
metadata:
  name: my-application
  namespace: flux-system
spec:
  interval: 1m
  chart:
    spec:
      chart: internal.my-chart
      version: "2024.3.0"
      sourceRef:
        kind: HelmRepository
        name: my-dockerhub-oci
        namespace: flux-system
      interval: 1m
  values:
    key: value

The issue I'm running into is that the internal.my-chart format isn't supported, specifically the . and I'm receiving the following error on my HelmRelease object:
HelmChart ''flux-system/flux-system-my-application'' is not ready: invalid chart reference: invalid chart name ''internal.my-chart'': a valid name must be lower case letters and numbers and MAY be separated with dashes (-)

And when I remove the internal. it works without any issues (but obviously targeting the wrong chart).
Now the reason that I'm submitting this issues is that my chart has already been uploaded to our Dockerhub OCI repo and helm pull works, making the validation that's going on here redundant; if there were an error with the name the OCI repo would've already errored before it even gets pushed in.
I was wondering what the reason for this drift from typical helm functionality and if there really isn't, if it's possible to remove the redundant validation.
Seems like this regex just needs to be altered: https://github.com/fluxcd/source-controller/blob/eff5a0784c7c9c8139f851020445b9c8a0828fc8/internal/helm/chart/builder.go#L86
I'm happy to make those contributions myself 😃

Hey @darkowlzz, just kinda curious, how I can consume this change or when will it be available?

Hey thanks for making the change @darkowlzz, just kinda curious now, how do I consume this change or when will it be available?


New screenshots, mention RainViewer, typo fix.

New screenshots to show rain section in Current forecast, new preferences and weather map transparency. Added mention of RainViewer to readme and android description. Fixed typo in preference text.

@0-5-0 btw i might be wrong but i feel like i have to thank you too for the review on the play store ?

Haha, I did add one this afternoon :)

@0-5-0 thank you ! felt like it was you ;)
dont know if you are French by if one day you go by Grenoble in France ping me and I ll happily buy you a beer!

Hehe, french canadian, a bit far but I'll reach out if I'm ever heading that way :)


HTML Snippet using event bus - documentation update

This epic should be provided as production deployment section. Both current and future deployment options should be described.

With this issue production deployment diagrams will be provided.

Documentation should be done in #58


Possible feature: new client method to register model that is already in memory

Right now, the register_model Garden client method and the garden-ai model register command that wraps it assumes that you have a serialized model on disc. Working with Eliu's notebook, I found myself wanting to use his existing code to load his models into memory and then invoke the Garden client on those. But as it stands I have to figure out how to serialize them first.
This feature could also be useful for publishers to incorporate Garden into training workflows. (Adding some step at the end of their workflow to push the model they've just trained to Garden without needing to write it to disc first.)
Assumptions:

Acceptance Criteria
Given..., when..., then...

I have a quick draft of this in a branch that I'm gonna try and touch up early next week


Allow to see whether commits are merge commits

For better understanding of what was pushed to a repository by other people, differentiating regular commits from merge commits could really help.

Added parent commits SHA information into email for push event.
Closed with d3f3584604bbcd81e29ececad5c5061d4c055aa6.


Quering with PRQL website

Link to suggestion
https://github.com/eitsupi/querying-with-prql
Targeted section
Real life examples/Websites formats
Describe your suggestion
I believe there are currently no examples using Docusaurus in the official Quarto website gallery.
This website is an example of using Docusaurus and uses some notable features as follows:

Combination of Jupyter and knitr engines
PRQL, SQL, R, Python multi-language with knitr engine
Trick to include md file generated by Quarto with Docusaurus mdx functionality and Quart's rendering order setting (by project.render in _quarto.yml)

Checklist

[X] checked if your suggestion is not already listed in Awesome Quarto list.
[X] checked if it can fit in an existed section or suggest a new section and explain why your item does not fit into one and what would be the interest of your new section.
[X] checked when it's a repository if it's maintained (archived repository will be rejected).

Thanks!


AMBARI-24116 Web Client Pulls Back Too Much Information in Upgrade Wizard

How was this patch tested?
21798 passing (29s)
48 pending

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/2731/
Test PASSed.


Focused reader mode or collapsible left menu

A focused reading mode would be nice to have.  Perhaps just the option to collapse the TOC menu on the left hand side?  Preferably be able to switch to the mobile reader view where the text spans the page and the menu at left collapses by choice at any resolution?
Currently I only see text on just less than half of the window and have large amounts of whitespace on either side. If I make the window smaller to accommodate the 'fixed' column width, the column gets thinner to accommodate the menu bar until finally it auto collapses at some point.
It would be preferable to just have the option to resize at will since monitor resolutions and prefered text sizes vary so greatly.

May not be applicable now that we've moved to a new site/framework.


Fixed \yii\db\BaseActiveRecord::findOne return type

Method one() used inside this method never return anything like null.

in theme:

https://github.com/yiisoft/yii2/blob/master/framework/db/QueryInterface.php#L37
https://github.com/yiisoft/yii2/blob/master/framework/db/Command.php#L360
only look gii and how it work) ?

https://github.com/yiisoft/yii2-gii/blob/master/generators/crud/default/controller.php#L167


Ensure cyclic aliases are serialized with a scope reference

Currently, because JSON for a cyclic type references only its alias like $a, if two scopes had differing definitions for the same cyclic alias, caching could break.
Really this should use the id that is precomputed when parsing a node, but I want to ensure that is done in a way that doesn't arbitrarily introduce unnecessary barriers to serialization.
Maybe scopes should should have a globally unique id, then an alias could be ${scodeId}$${alias} or similar.

Added a test for this issue in scope.test.ts that should be fixed as part of this PR.
Search for https://github.com/arktypeio/arktype/issues/930


update proxy of master to use-back-addr-3

What problem does this PR solve?
Issue Number: ref #4982
Problem Summary:
update proxy to use-back-addr-3
Proxy PR:
Including:\nSubmodule contrib/tiflash-proxy 023c4e7261..36541e1923:

z
Use addr's ip if status_addr's is is empty (#334)

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

/approve

/run-all-tests

/merge

/hold

/run-integration-test

/run-build-release comment=true

/run-integration-test

/run-build-release comment=true

/run-build-release comment=true

/run-integration-test

/run-integration-test

/run-integration-test

/run-integration-test

/rebuild

/run-integration-test

/merge

/run-unit-test

/run-all-tests

/run-unit-test

/unhold


Template repository for a connector

Feature description
We should create a template repository for creating a connector. Think about guiding the user towards creating tests, prepare a docker compose that spins up 3rd party resources, prepare a makefile that runs tests and spins the docker containers up/down, if possible include github actions for running a linter and tests.

Done! https://github.com/ConduitIO/conduit-connector-template


AutoFocus timing out in Android

Is there an existing issue for this?

[X] I have searched the existing issues
[X] I have read the guide to filing a bug

Steps to reproduce
I found an issue with the auto focus in the later versions of the camera_android package.
It appears to affect versions of camera_android 0.10.8+4 and higher.
When taking a photo when the resolution preset is higher than medium the auto focus will time out.
This was reproducible on two different Android devices as well.
Expected results
Autofocus should not time out.
Actual results
Autofocus does time out.
Code sample
Code sample
This can be reproduced in the example app.
```dart
      kIsWeb ? ResolutionPreset.max : ResolutionPreset.max,
```

Screenshots or Video

Screenshots / Video demonstration
[Upload media here]

Logs
Logs
I/Camera  ( 5000): runPictureAutoFocus
I/Camera  ( 5000): lockAutoFocus
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: null | aeState: null
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 1 | aeState: 1
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 1 | aeState: 1
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 1 | aeState: 1
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 1 | aeState: 1
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_WAITING_FOCUS | afState: 2 | aeState: 2
W/CameraCaptureCallback( 5000): Focus timeout, moving on with capture
I/Camera  ( 5000): captureStillPicture
D/Camera  ( 5000): Updating builder with feature: ExposureLockFeature
D/Camera  ( 5000): Updating builder with feature: ExposurePointFeature
D/Camera  ( 5000): Updating builder with feature: ZoomLevelFeature
D/Camera  ( 5000): Updating builder with feature: AutoFocusFeature
D/Camera  ( 5000): Updating builder with feature: NoiseReductionFeature
I/Camera  ( 5000): updateNoiseReduction | currentSetting: fast
D/Camera  ( 5000): Updating builder with feature: FocusPointFeature
D/Camera  ( 5000): Updating builder with feature: ResolutionFeature
D/Camera  ( 5000): Updating builder with feature: SensorOrientationFeature
D/Camera  ( 5000): Updating builder with feature: FlashFeature
D/Camera  ( 5000): Updating builder with feature: ExposureOffsetFeature
D/Camera  ( 5000): Updating builder with feature: FpsRangeFeature
I/Camera  ( 5000): sending capture request
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_CAPTURING | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_CAPTURING | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_CAPTURING | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_CAPTURING | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_CAPTURING | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_CAPTURING | afState: null | aeState: null
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_CAPTURING | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_CAPTURING | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_CAPTURING | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_CAPTURING | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_CAPTURING | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_CAPTURING | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_CAPTURING | afState: 2 | aeState: 2
D/CameraCaptureCallback( 5000): CameraCaptureCallback | state: STATE_CAPTURING | afState: 2 | aeState: 2
I/Camera  ( 5000): onImageAvailable
W/gralloc4( 5000): Could not find component description for FourCC value 0
I/DMABUFHEAPS( 5000): Using : Legacy ion heaps
I/gralloc4( 5000): No mtk_sapu_data_shm_region heap, ion name , flags 0, legacy_ion_heap_mask 0x0, legacy_ion_heap_flags 0x0
I/gralloc4( 5000): No mtk_sapu_engine_shm_region heap, ion name , flags 0, legacy_ion_heap_mask 0x0, legacy_ion_heap_flags 0x0
I/Camera  ( 5000): unlockAutoFocus
I/Camera  ( 5000): refreshPreviewCaptureSession

Flutter Doctor output
Doctor output
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.13.4, on macOS 13.5.2 22G91 darwin-arm64, locale en-AU)
[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
[✓] Xcode - develop for iOS and macOS (Xcode 14.2)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2022.3)
[✓] VS Code (version 1.82.2)
[✓] Connected device (3 available)
[✓] Network resources

Hi @MarcoSavaglia. Thanks for filing this. I can't seem to reproduce this. Can you help with the device information you are reproducing this on please?

Absolutely, the two devices I had that could replicate was a Motorola Fusion Edge 20 and a Samsung Galaxy S23 Ultra.

Cross-posting from #84957.
Will someone check this and this, please?


Update README

Description
Update the README file with

new screenshots
detailed description of what the environment is capable of
what packages and tools are used
link to the neovim config repository

Done in https://github.com/tomijaroli/dotfiles/commit/13cf969bf748d7e9e436b7d10ec67f06bd3502d8


Add pull request template

🤔 Not Existing Feature Request?

[X] Yes, I'm sure, this is a new requested feature!

🤔 Not an Idea or Suggestion?

[X] Yes, I'm sure, this is not idea or suggestion!

📋 Request Details
Add pull request template.
Lots of template are already available, you can use any one.
📜 Code of Conduct

[X] I agree to follow this project's Code of Conduct.

Do you have example of it @theritikchoure ?

@warengonzaga , below I have mentioned a link for pull request templates.
https://github.com/axolo-co/pull_request_template
You can use any, I personally use Example - 6

@warengonzaga , below I have mentioned a link for pull request templates.
https://github.com/axolo-co/pull_request_template
You can use any, I personally use Example - 6

Interesting, I'll take a look.


x/website: doc/install: add download instructions into numbered steps

What is the URL of the page with the issue?
https://go.dev/doc/install#
What is your user agent?
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36
Screenshot

What did you do?
It's not an error but felt like a little inconsistent for someone if they are coming for the first time to download and install Golang.
If you are coming from the go.dev homepage, and you press the Download button, then it's landing you to the https://go.dev/dl/ which seems fine. Then, if you go to the installation instructions from that page, that also seems fine (Refer to the first Screenshot)
But, if you are coming from the https://go.dev/doc/ or directly hitting the link https://go.dev/doc/install# from the search engine page, then these instructions going to look a little confusing.
As, it's assuming we have already downloaded the Go binary release, as the first instruction starts with that.(Refer to the second Screenshot)
What did you expect to see?
My suggestion is that we modify the first line on the [https://go.dev/dl/] (https://go.dev/dl/) page to obtain the binary release suitable for your system, and then follow the installation instructions.
And for the users who are coming from the https://go.dev/doc/ or directly hitting the link https://go.dev/doc/install# from the search engine page, we can add the first instruction in the Go Installation as-

Download the suitable binary release from the above button.(If you have already downloaded it, kindly move ahead with the following instructions)

Rest steps could remain the same.
It was the first time that I missed the very first thing, which was a download, as my focus went straight to the Go Installation. Although, I am doing installing binaries and programming for years, but I just felt it a little inconsistent from the perspective of a new user. As, I landed to https://go.dev/doc/install from an open-source contributing page. Particularly, the steps for installing on Linux.

Hi @seankhliao,
Thank you for correcting the title and tag, as it is my first issue. If this seems like a valid inconsistency with the instructions, I would love to contribute to this issue.
Regards.

Hi,
Is this the right place https://github.com/golang/website/tree/master/_content/doc/install to edit the doc/install page to add the required number step?
Do I have to edit the source.html file only?

Hi @seankhliao I have opened a PR https://github.com/golang/website/pull/229 for the numbered step instructions to eliminate the inconsistency.

Thanks for highlighting this but we're currently redesigning the download and install flow internally.

Hi @jamalc, So should I close the PR and this issue?


Lower accuracy when reproducing the experiments

Hello, thank you for the work you have done. In my attempt to replicate the experiments reported in the LassoNet paper, I found that the results I am getting are totally different. The performance at 50 selected features is significantly lower than the one reported in the paper (<60% vs 88% for the ISOLET dataset). I have repeated the experiment on 20 or 30 runs and tried all the possible hidden_dim. I was wondering if there I am missing something or if there is a default parameter which significantly affects the performance and needs to be changed.
I will detail the steps I have done:

I downloaded the datasets from Google drive provided on the github repo.
I created a fresh virtual environment using venv with python 3.9.2 and only installed lassonet.
For loading the data, I also used the loaders in data_utils.py in the experiments folder of the repo.
Instead of tuning the hidden_dim (as the paper indicates), I experimented with all the possible options [d//3, 2d//3, d, 4d//3]
I used the following script for running the experiments (for one hidden_dim at a time):

import matplotlib.pyplot as plt
from sklearn.metrics import accuracy_score
from sklearn.model_selection import train_test_split
from lassonet import LassoNetClassifier
from lassonet.interfaces import LassoNetClassifierCV
from lassonet.plot import plot_path
from lassonet.utils import eval_on_path
from data_utils import load_mice, load_coil, load_activity, load_isolet
import torch
import pickle

(X_train, y_train), (X_test, y_test) = load_isolet()
X_train_valid_fixed = X_train
y_train_valid_fixed = y_train

seed = None
device = 'cuda'

data_dim = X_train.shape[1]
hidden_dim = (data_dim//3,)

score_list_of_lists = []
n_selected_list_of_lists = []
lambda_list_of_lists = []

for i in range(30):
    X_train, X_val, y_train, y_val = train_test_split(X_train_valid_fixed, y_train_valid_fixed, test_size=0.125, random_state=seed)
    model = LassoNetClassifier(M=10, hidden_dims=hidden_dim, verbose=1, torch_seed=seed, random_state=seed, device=device)
    path = model.path(X_train, y_train, X_val=X_val, y_val=y_val)

    score = eval_on_path(model, path, X_test, y_test, score_function=None)
    n_selected = [save.selected.sum().item() for save in path]
    lambda_ = [save.lambda_ for save in path]

    score_list_of_lists.append(score)
    n_selected_list_of_lists.append(n_selected)
    lambda_list_of_lists.append(lambda_)

And the following to plot
plt.figure(figsize=(30, 10))
for sublist_A, sublist_B in zip(score_list_of_lists, n_selected_list_of_lists):
    plt.plot(sublist_B, sublist_A)
    plt.xlabel('Features Selected')
    plt.ylabel('Accuracy')
    plt.title('Accuracy vs Features Selected for hidden_dim=(data_dim//3,) on ISOLET dataset --- GPU version for 30 runs')

plt.savefig('isolet_1.png')

Surprisingly,  I got the following plots:

To rule out possible GPU issues, I ran the first experiment on the CPU for fewer runs (as it was taking longer)

Similarly, I repeated the first experiment on COIL dataset

I was surprised of the plots given the steps I have followed. However, I realized that similar plots were reported by a paper that studies LassoNet (especially for the case of 50 features).
I suspect the behavior should be consistent, and I'm still wondering what I might have missed. Could you kindly provide insight or assistance to help resolve these discrepancies? Thank you in advance!

Many thanks for sharing these results.
Indeed, the current version of LassoNet went through substantial upgrades and default parameters have likely changed over time to accomodate more use cases and improve overall performance.
Perhaps another thing to keep in mind is that we did not use the network that was learned during training, but retrained the reconstruction network from scratch to address the bias due to L1 regularization (cf. Section 4.4 of the paper).

Many thanks for your immediate responses!
May I ask how is it possible (code wise) to retrain the network from scratch, "restricting the input features to the subset of interest and zeroing out all others"?
Also to be confident of my tests, are there other parameters which you think have been changed and might have a huge impact? I apologize for bombarding you with questions, but I am seeking a fair comparison of the models :D !

I'm replying from my phone but basically you just have to select the first feature mask on the path that has less than 50 positive entries.
Then you select those features with X[:, mask] and you train a model with lambda = 0 (you can probably use the standard API, eg provide lambda_seq=[0]).
You can modify the number of epochs to improve the results.
I think that you could try modifying the learning rates too as a last resort.

Thanks for the tips, it finally worked out and I get similar results! Really appreciate your help

Great!!! Do you mind sharing exactly what was needed (just changing the parameters or retraining without penalty)? Could you contribute by adding your code to the experiments/ folder? That would be great!

It was retraining without penalty, without changing the parameters.
Sure thing! While I managed to reproduce the results in table 1, I couldn't do so for the plots without retraining the model  from scratch for each set of selected features, which doesn't align with the functionality of LassoNet as mentioned in appendix A. Thus I refrained from doing it. However, I'll be happy to write the code if you can clarify the approach for achieving it.

@ilemhadri can you help here? I don't remember what we did there.

@HadiHammoud44 in case it's not clear from Appendix A, the there about the cost remaining the same refers to the cost of selecting features and not to the cost of training the network.
Each of the results in Appendix A did follow the same procedure of retraining the network from scratch on the subset of features that LassoNet selected.

Oh okk clear! Then the code is already done for that, will add it soon. Thanks again for your prompt assistance.


General: Split and Menu Buttons - Options shouldn't be selected (highlighted)

I think this one should be resolved in oceanfornt.

It looks fine.


oauth: Nango migrator: skip alreayd migrated

Description
Skip alreaydy migrated connections
Risk
N/A
Deploy Plan

deploy connectors

PMRR


GitHub lab is woefully out of date

The GitHub lab https://github.com/Microsoft/azuredevopslabs/tree/master/labs/vstsextend/github/ is extremely out of date; I think it should be updated or retired.
The README still says things like:
The primary difference between the two is that VSTS is focused on closed source projects and GitHub is focused more on open source projects. GitHub offers both private and public repositories. However, it doesn't have an integrated build server.

That's completely inaccurate as of 2021.

@larryclaman - Thanks for your feedback.  What is your opinion?  Should this be deprecated or fixed?  If you believe the answer is "fixed" then I ask for a second opinion...  Would you prefer that we spend time updating our Contributions page and clearly state that we accept contributions... and if so, would you be interested in issuing a PR to update this content?

HI @larryclaman ,
https://github.com/Microsoft/azuredevopslabs/tree/master/labs/vstsextend/github/
This lab is already deprecated and is not displayed on our home page https://azuredevopslabs.com
We have new set of labs
https://azuredevopslabs.com/labs/vstsextend/github-azurepipelines/
https://azuredevopslabs.com/labs/vstsextend/github-azureboards/
We will add a deprecate note in the https://github.com/Microsoft/azuredevopslabs/tree/master/labs/vstsextend/github/
Thanks

@sriramdasbalaji , thanks for the note.  Glad to hear that this lab is no longer featured on the azuredevopslab.com home page, but you should be aware that it is one of the labs still available on the Azure DevOps Demo Generator site https://azuredevopsdemogenerator.azurewebsites.net/, which is how I came across it in the first place.


added roles for invite modal

Your checklist for this pull request
🚨Please review the guidelines for contributing to this repository.

[ ✔] Make sure you are requesting to pull a topic/feature/bugfix branch (right side). Don't request your master!
[ ✔] Make sure you are making a pull request against the dev branch. Also you should start your branch off dev branch.
[ ] Check you have added tests that prove your fix is effective or that your feature works.
[✔ ] Check your code additions will fail neither code linting checks nor unit test.
[ ] Check you added any notable changes to the CHANGELOG.md file.

Description
added role field for invite modal  for issue#263

Codecov Report

Merging #265 into dev will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##                dev     #265   +/-   ##
=========================================
  Coverage     79.06%   79.06%
  Complexity      223      223
=========================================
  Files            81       81
  Lines           731      731
=========================================
  Hits            578      578
  Misses          153      153

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 a4d3e15...2783a4d. Read the comment docs.


Add electron support

Without explicitly writing https in the href of the <link> element injected into index.html electron will interpret it as a file:// URL. Adding https enables use with Electron and does not break normal use with ember serve.

Hi @fostertheweb, thanks for the PR 👍


For users, we need to allow them to check out and edit their personal info.

Goal:
Make it so that the users can customize their personal information more.
Key Requirements:

[ ] Add the feature to allow users to change their username and their email (remember to confirm uniqueness with the DB)
[ ] Add the feature to allow users to upload images to display.

Put on hold to focus on more vital parts of the program


Eng 9458 basic functional testing

Description
This PR adds a foundation for functional/end to end testing.
Why is this needed
Code confidence and quality need to be improved. This PR tries to address those.
Fixes: #
How Has This Been Tested?
See test/README.md.  add resources to file: test/resources.yaml then run make test-functional
How are existing users impacted? What migration steps/scripts do we need?

Checklist:
I have:

[X] updated the documentation and/or roadmap (if required)
[X] added unit or e2e tests
[ ] provided instructions on how to upgrade

@mikemrm @jgavinray @mmlb  just a friendly ping :)

Looks good, I think the intermediate drafts of test setup should all be squashed.

@mmlb mind having another look now that the commits are cleaned (hopefully) up?


Advanced functionality not defined

🚨 Looks like you arrived from the internal review site
🚨 Do not enter Microsoft confidential information here
In the article, Advanced functionality is mentioned, requiring additional licensing however we don't see an explanation on what this means, what makes an alert policy contain advanced functionality.

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 9f2879ba-e58e-cd47-f488-10d153c31418
Version Independent ID: 391a2c05-d63d-e84e-7c7d-80c3b3518419
Content: Microsoft 365 alert policies - Microsoft Purview (compliance)
Content Source: microsoft-365/compliance/alert-policies.md
Service: o365-seccomp
GitHub Login: @robmazz
Microsoft Alias: robmazz

@tiburd kindly point internal MS contributors to the ADO form link and close the issue. Thanks

@asdcristi
Hi, Cristian-Alexandru,
Thanks for the feedback.
As a Microsoft submitter, I'll send you an internal email with the link to the content request form so you can submit this request there. Submitting internally is easier for the compliance content team and the PG team to review, confirm, and approve.
Thanks!
cc: @yogkumgit


KCFinder

Hi, I faced this error ... i don't know why its hapen...
kcfinder attention unknown error

any idea?

No. How to generate this error?

I think the problem in my server production ... access privilages, i test in windows it's work, i will close this issue. Thanks for your fast reply brother.


chromium: 119.0.6045.123

@apprehensions Thanks! Any reason why this is a draft PR?

because i haven't built it yet, but ioraff has so i think it works


Updating breakpoint from debug adapter does not work if another session is focused

When implementing Debug Adapter Protocol, I sometimes issue breakpoints event where breakpoints change the verified status from false to true. If that happens while another debugging session is current (focused), the update is ignored.
I think the problem is in this line. Here idFromAdapter depends on currently focused debugging session, which may or may not be the one receiving the event.
Steps to reproduce:

Use this modified version of vscode-mock-debug.
Run the mock debug extension on testWorkspace folder included in the branch above.
Set breakpoint in the session2.md file on the line with "lazy".
Launch "Bug" configuration.
Two scenarios

If you select "Session2" during first 5 seconds, breakpoint on the "lazy" line will be verified after 5 seconds (Session2 will emit "breakpoint changed" DAP event).
If you don't select "Session2" during first 5 seconds (e.g. do nothing, Session1 will be focused by default), the breakpoint will not be verified, and switching between sessions afterwards does not help.

@dgozman your analysis is correct. That line is the issue and should look at the id from the recieving session, not from the focussed session.
This is not a regression, thus I plan to fix this next milestone.
Also I am open to a PR which fixes this since you already nicely found the root cause.
Proposed fix: idFromAdapter should be a real method and not a getter. This method needs to be passed in a sessionId so it is not dependent on the focused session.


[BUG] Hypercube broken pipe error with PHP deprecation error on PHP 8.1+ISLE

What steps does it take to reproduce the issue?
Create a site with the ISLE Site Template, which runs on PHP 8.1.
With Islandora Text Extraction enabled, verify that a media derivative context is configured with a reaction that carries out a text extraction action.
This is configured in the starter site by default.
Create a Repository Item node of type Paged Content, then add one or more members with model Page.
Add media to those pages of type File and upload a TIFF with embedded text.

When does this issue occur?

Which page does it occur on?

What happens?

No Extracted Text media is created.
The Hypercube logs show the following errors:

isle-site-template-hypercube-dev-1  | <IP_ADDRESS> - - [25/Sep/2023:20:23:09 +0000] "GET / HTTP/1.1" 500 84265 "-" "Apache-HttpClient/4.5.13 (Java/17.0.8)" "-"
isle-site-template-hypercube-dev-1  | [2023-09-25 20:23:10] request.INFO: Matched route "hypercube_convert". {"route":"hypercube_convert","route_parameters":{"_route":"hypercube_convert","_controller":"App\\Islandora\\Hypercube\\Controller\\HypercubeController::ocr"},"request_uri":"http://hypercube:8000/","method":"GET"} []
isle-site-template-hypercube-dev-1  | [2023-09-25 20:23:10] security.INFO: Guard authentication successful! {"token":"[object] (Symfony\\Component\\Security\\Guard\\Token\\PostAuthenticationGuardToken: PostAuthenticationGuardToken(user=\"admin\", authenticated=true, roles=\"authenticated, fedoraadmin\"))","authenticator":"Islandora\\Crayfish\\Commons\\Syn\\JwtAuthenticator"} []
isle-site-template-hypercube-dev-1  | [2023-09-25 20:23:10] php.INFO: Deprecated: fopen(): Passing null to parameter #3 ($use_include_path) of type bool is deprecated {"exception":"[object] (ErrorException(code: 0): Deprecated: fopen(): Passing null to parameter #3 ($use_include_path) of type bool is deprecated at /var/www/crayfish/Hypercube/vendor/guzzlehttp/psr7/src/StreamWrapper.php:45)"} []
isle-site-template-hypercube-dev-1  | [2023-09-25 20:23:10] request.CRITICAL: Uncaught PHP Exception ErrorException: "Notice: fwrite(): Write of 1024 bytes failed with errno=32 Broken pipe" at /var/www/crayfish/Hypercube/vendor/islandora/crayfish-commons/CmdExecuteService.php line 82 {"exception":"[object] (ErrorException(code: 0): Notice: fwrite(): Write of 1024 bytes failed with errno=32 Broken pipe at /var/www/crayfish/Hypercube/vendor/islandora/crayfish-commons/CmdExecuteService.php:82)"} []
isle-site-template-hypercube-dev-1  | <IP_ADDRESS> - - [25/Sep/2023:20:23:10 +0000] "GET / HTTP/1.1" 500 84265 "-" "Apache-HttpClient/4.5.13 (Java/17.0.8)" "-"
   ^[^[

To whom does it occur (anonymous visitor, editor, administrator)?

Editor,, Administrator

What did you expect to happen?

Text extractions are successfully executed.
Which version of Islandora are you using?
ISLE Site Template run via automatic setup script on ~ Sept 21, 2023.
Crayfish container version:
"Image": "sha256:399ac4c2df9f71f0609b0a115b34072e964bbbda2f947a4a442c52bddbc71da2",
"ResolvConfPath": "/var/lib/docker/containers/6dfe5dd791d1d89d14e32fbc2722a253f2381b9779708051a490dc7de21b1c29/resolv.con
Any related open or closed issues to this bug report?
Screenshots:

This seems to be a php 8.1 issue or perhaps something else with the docker build in isle-buildkit 2.x...
Editing docker-compose to use hypercube:1.0.10 resolves the issue for me for the time being.

This may be completed in 2.0.4 - needs testing/verification.


Use ImmutableWorkerInfo instead of ZKWorker

This PR is follow up changes for  #2249 and #2585
#2249 uses Worker instead of ZkWorker whenever possible for task tiering.
This PR changes the behavior to expose ImmutableWorkerInfo from WorkerTaskRunner instead of Worker. ImmutableWorkerInfo has more details like list of running tasks and availability groups.
These extra details exposed are required for #2086 (implementing pending task based resource management strategy)

@gianm @drcrallen: Since its mostly related to your changes, please have a look at it.

@nishantmonu51 looks good other than some minor comments

@drcrallen @gianm handed review comments, please check again.

:+1: after travis

Tests run: 5, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 34.79 sec <<< FAILURE! - in io.druid.indexing.worker.WorkerTaskMonitorTest
testRestartCleansOldStatus(io.druid.indexing.worker.WorkerTaskMonitorTest)  Time elapsed: 31.087 sec  <<< ERROR!
java.lang.Exception: test timed out after 30000 milliseconds
at sun.misc.Unsafe.park(Native Method)
at java.util.concurrent.locks.LockSupport.park(LockSupport.java:186)
at java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:834)
at java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:994)
at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1303)
at java.util.concurrent.CountDownLatch.await(CountDownLatch.java:236)
at io.druid.indexing.worker.WorkerTaskMonitor.stop(WorkerTaskMonitor.java:260)
at io.druid.indexing.worker.WorkerTaskMonitorTest.testRestartCleansOldStatus(WorkerTaskMonitorTest.java:331)
testRestartCleansOldStatus(io.druid.indexing.worker.WorkerTaskMonitorTest)  Time elapsed: 31.087 sec  <<< ERROR!
java.lang.IllegalStateException: not started
at com.google.common.base.Preconditions.checkState(Preconditions.java:176)
at io.druid.indexing.worker.WorkerTaskMonitor.stop(WorkerTaskMonitor.java:250)
at io.druid.indexing.worker.WorkerTaskMonitorTest.tearDown(WorkerTaskMonitorTest.java:205)
Running io.druid.indexing.worker.http.WorkerResourceTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.809 sec - in io.druid.indexing.worker.http.WorkerResourceTest
Running io.druid.indexing.worker.TaskAnnouncementTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.013 sec - in io.druid.indexing.worker.TaskAnnouncementTest
Running io.druid.indexing.appenderator.ActionBasedUsedSegmentCheckerTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 sec - in io.druid.indexing.appenderator.ActionBasedUsedSegmentCheckerTest
Running io.druid.server.initialization.IndexerZkConfigTest
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.874 sec - in io.druid.server.initialization.IndexerZkConfigTest
Results :
Tests in error:
io.druid.indexing.worker.WorkerTaskMonitorTest.testRestartCleansOldStatus(io.druid.indexing.worker.WorkerTaskMonitorTest)
Run 1: WorkerTaskMonitorTest.testRestartCleansOldStatus:331 »  test timed out after 3...
Run 2: WorkerTaskMonitorTest.tearDown:205 » IllegalState not started

:+1: (after travis) minor question about javadoc at author's discretion.


[Feature request]: Exclude pattern option

Description
First of all, I'm not really sure if this concerns to nvim-lspconfig or neovim directly, sorry if it does not concerns to you!.
I have configured bashls but it starts running on every .env file that I open, I was looking into the docs but I didn't find a way to do it. it would be nice to have an option to omit some file patterns to trigger the lsp.

check your bashls filetype config and it just sh filetype in default. so check your config first

@glepnir It has everything as default, so the file type is set to sh but it recognize .env files as sh

emm because neovim detect the env extension for  shebang. i think you can edit this behavoir by using something like
vim.filetype.add({
  extension = {
    env = 'test',
  },
})


Ansible doesn't run on second play

When running the master-iso.sh when it gets to the ansible portion it will fail if you run it twice.   This is only an issue when you sign packages and they either partially download or all download and get signed. Once these conditions are met and you want to run the script again for any reason it will crash out in download packages task.
https://github.com/rocknsm/rock-createiso/blob/9144b22e1b911a1b679621f2ff128de7ffa03642/ansible/roles/common/tasks/main.yml#L11-L18
The out put from ansible is below.
TASK [common : download packages] **********************************************************************************************************************************************************************************************************************************************
task path: /home/admin/rock-createiso/ansible/roles/common/tasks/main.yml:11
<<IP_ADDRESS>> ESTABLISH LOCAL CONNECTION FOR USER: root
<<IP_ADDRESS>> EXEC /bin/sh -c 'echo ~root && sleep 0'
<<IP_ADDRESS>> EXEC /bin/sh -c '( umask 77 && mkdir -p "` echo /root/.ansible/tmp/ansible-tmp-1554392843.21-207182491353216 `" && echo ansible-tmp-1554392843.21-207182491353216="` echo /root/.ansible/tmp/ansible-tmp-1554392843.21-207182491353216 `" ) && sleep 0'
Using module file /home/admin/rock-createiso/ansible/roles/common/library/repobuilder.py
<<IP_ADDRESS>> PUT /root/.ansible/tmp/ansible-local-36132nxq0YE/tmpNU27M_ TO /root/.ansible/tmp/ansible-tmp-1554392843.21-207182491353216/AnsiballZ_repobuilder.py
<<IP_ADDRESS>> EXEC /bin/sh -c 'chmod u+x /root/.ansible/tmp/ansible-tmp-1554392843.21-207182491353216/ /root/.ansible/tmp/ansible-tmp-1554392843.21-207182491353216/AnsiballZ_repobuilder.py && sleep 0'
<<IP_ADDRESS>> EXEC /bin/sh -c '/usr/bin/python2 /root/.ansible/tmp/ansible-tmp-1554392843.21-207182491353216/AnsiballZ_repobuilder.py && sleep 0'
<<IP_ADDRESS>> EXEC /bin/sh -c 'rm -f -r /root/.ansible/tmp/ansible-tmp-1554392843.21-207182491353216/ > /dev/null 2>&1 && sleep 0'
The full traceback is:
Traceback (most recent call last):
  File "/root/.ansible/tmp/ansible-tmp-1554392843.21-207182491353216/AnsiballZ_repobuilder.py", line 113, in <module>
    _ansiballz_main()
  File "/root/.ansible/tmp/ansible-tmp-1554392843.21-207182491353216/AnsiballZ_repobuilder.py", line 105, in _ansiballz_main
    invoke_module(zipped_mod, temp_path, ANSIBALLZ_PARAMS)
  File "/root/.ansible/tmp/ansible-tmp-1554392843.21-207182491353216/AnsiballZ_repobuilder.py", line 48, in invoke_module
    imp.load_module('__main__', mod, module, MOD_DESC)
  File "/tmp/ansible_repobuilder_payload_idX4fO/__main__.py", line 417, in <module>
  File "/tmp/ansible_repobuilder_payload_idX4fO/__main__.py", line 405, in main
  File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1075, in getPackage
    **kwargs
  File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1042, in _getFile
    raise e
yum.Errors.NoMoreMirrorsRepoError: failure: Packages/GConf2-3.2.6-8.el7.x86_64.rpm from base: [Errno 256] No more mirrors to try.
http://mirror.centos.org/centos/7/os/x86_64/Packages/GConf2-3.2.6-8.el7.x86_64.rpm: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable

fatal: [localhost]: FAILED! => {
    "changed": false,
    "module_stderr": "Traceback (most recent call last):\n  File \"/root/.ansible/tmp/ansible-tmp-1554392843.21-207182491353216/AnsiballZ_repobuilder.py\", line 113, in <module>\n    _ansiballz_main()\n  File \"/root/.ansible/tmp/ansible-tmp-1554392843.21-207182491353216/AnsiballZ_repobuilder.py\", line 105, in _ansiballz_main\n    invoke_module(zipped_mod, temp_path, ANSIBALLZ_PARAMS)\n  File \"/root/.ansible/tmp/ansible-tmp-1554392843.21-207182491353216/AnsiballZ_repobuilder.py\", line 48, in invoke_module\n    imp.load_module('__main__', mod, module, MOD_DESC)\n  File \"/tmp/ansible_repobuilder_payload_idX4fO/__main__.py\", line 417, in <module>\n  File \"/tmp/ansible_repobuilder_payload_idX4fO/__main__.py\", line 405, in main\n  File \"/usr/lib/python2.7/site-packages/yum/yumRepo.py\", line 1075, in getPackage\n    **kwargs\n  File \"/usr/lib/python2.7/site-packages/yum/yumRepo.py\", line 1042, in _getFile\n    raise e\nyum.Errors.NoMoreMirrorsRepoError: failure: Packages/GConf2-3.2.6-8.el7.x86_64.rpm from base: [Errno 256] No more mirrors to try.\nhttp://mirror.centos.org/centos/7/os/x86_64/Packages/GConf2-3.2.6-8.el7.x86_64.rpm: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable\n",
    "module_stdout": "",
    "msg": "MODULE FAILURE\nSee stdout/stderr for the exact error",
    "rc": 1
}
	to retry, use: --limit @/home/admin/rock-createiso/ansible/offline-snapshot.retry

PLAY RECAP *********************************************************************************************************************************************************************************************************************************************************************
localhost                  : ok=3    changed=0    unreachable=0    failed=1

It is possible to work around this locally by simply deleting the packages previously signed and downloaded. This works but is not desired as it requires redownloading all the things..
Steps to reproduce.

Run the master-iso script with a gpg key

./master-iso.sh -s ${INPUT_ISO} -o output.iso -g '${KEY_NAME}' -p '${KEY_PASSWORD}' -i ${KEY_PATH}

Repeat step 1 after completion

I think the API that repobuilder uses can generate a list of URLs rather than actually do the downloads. If so, we can take the filename of the URL and compare it with files on disk. To do it correctly, we need to either know the size of the upstream RPM via the API, and/or we need to check the integrity of the RPM on disk, which the file format has built in.

So I am not a 100% sure but pretty sure that is what I am attempting to do already. This should just a list of all the packages that user requested.
https://github.com/rocknsm/rock-createiso/blob/f71c3e86d02bc52c69418917f64f8f1ccb3bee5e/ansible/roles/common/library/repobuilder.py#L336-L345
This finds all the dependancies for the requested packages from the user.
https://github.com/rocknsm/rock-createiso/blob/f71c3e86d02bc52c69418917f64f8f1ccb3bee5e/ansible/roles/common/library/repobuilder.py#L362-L374
This then downloads all the things that are in the tree that is created.
https://github.com/rocknsm/rock-createiso/blob/f71c3e86d02bc52c69418917f64f8f1ccb3bee5e/ansible/roles/common/library/repobuilder.py#L387-L412
Specifically this should be checking the currently downloaded package on the system and then skip it.
https://github.com/rocknsm/rock-createiso/blob/f71c3e86d02bc52c69418917f64f8f1ccb3bee5e/ansible/roles/common/library/repobuilder.py#L393-L395
I think the error is beyond the skip and possibly on the YUM side of the house. This works perfectly fine if you don't sign the packages with a custom key. As soon as you sign the packages however it breaks. I dunno if yum is doing something different internally when checking because the packages locally are now signed differently than the ones it is seeing upstream?

Closing as repobuilder wont be used. Replacing with the built in dnf module. Will open a new issue the signing fails using dnf module.


not verify

hi I already submit but I did mistake is there option to change the video

https://app.proofofhumanity.id/profile/0x6cb4890d712c91020df2e62fb7bb869ce6ca3e8a
Not a human


open-cluster-management addon framework

Define the standard procedure
Define the interface for addon framework library

/close


Not Viewable in Internet Explorer

body tag remains empty when viewing with internet explorer

Commits were rolled back due to issues with the Babel changes.  I am currently looking into implementing a Travis-CI build process to provide ES5 support.  This may also allow for rendering other secondary document types.

Should be fixed with TRAVIS-CI build process. Will close after testing.


Add a new Tag model

What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Does this PR introduce a user-facing change?:

NONE

/hold

/rebase

We decided to use Labels instead of Tags.
Furthermore, we made sure to define Labels declaratively in the configuration file, so we don't need to complete them; we don't need to store them for ACLs either, so we don't need a Label model.
/close


Make updater not require admin permissions

(It's annoying having to deal with UAC on each debug start, and I'm sure users are also not happy with it)

Well, as I assigned updater.exe to always run as Administrator, UAC doesn't pop up anymore. Just a trick till you get this :)


handle context cancellation

We're passing around contexts and I believe we said we'd exit early on context cancellation (there's some code scattered here and there for that), but it's not full threaded through the codebase yet

Has this been addressed with some of the the recent context work already?

ah, this one was an older issue about handle stuff like ctrl-C gracefully. Usually the pattern is to catch the signal and then cancel the context for the operation. Since we haven't really been focused on that area of things recently we can close this issue


PERCENTAGE PRICE OSCILLATOR (PPO) - DOCUMENTATION (DESCRIPTIONS OF EXISTING RULES/INDICATORS)

What Is the Percentage Price Oscillator (PPO)?
The percentage price oscillator (PPO) is a technical momentum indicator that shows the relationship between two moving averages in percentage terms. The moving averages are a 26-period and 12-period exponential moving average (EMA).
The PPO is used to compare asset performance and volatility, spot divergence that could lead to price reversals, generate trade signals, and help confirm trend direction.

How to Calculate the Percentage Price Oscillator (PPO)

Calculate the 12-period EMA of the asset's price.
Calculate the 26-period EMA of the asset's price.
Apply these to the PPO formula to get the current PPO value.
Once there are at least nine PPO values, generate the signal line by calculating the nine-period EMA of the PPO.
To generate a histogram reading, take the PPO value and subtract the current signal line value. The histogram is an optional visual representation of the distance between these two lines.

Bullish Reversal: when PPO is above zero
Bearish Reversal: when PPO is below zero

The theory suggests that asset price will have a trend shift when the PPO cross above zero levels and vice versa. So:
if PPO > 0
then allocation = max_allocation(long position)
if PPO < 0
then allocation = -max_allocation(short position)
else: allocation = 0

What Is the Percentage Price Oscillator (PPO)?
The percentage price oscillator (PPO) is a momentum indicator that measures the difference between two moving averages as a percentage of the larger moving average. The moving averages are a 26-period and 12-period exponential moving average (EMA).  The Percentage Price Oscillator is shown with a signal line, a histogram and a centerline. Signals are generated with signal line crossovers, centerline crossovers, and divergences.  A bullish reversal of an asset is identify when the PPO cross above zero line.  And a bearish reversal when the PPO cross below the zero line.
@fhashim Definition free of copyright issues. Thank you


Wrong license output

In the three10x benchmark, it produced a license file
dist/static/js/async/213.bf016bb8.js.LICENSE.txt
with the content
// !\ DECLARE ALIAS AFTER assign prototype !

// !\ DECLARE ALIAS AFTER assign prototype !

Oops wrong bundler.


document need for manageSpawn in SpawnOnce

Description
Document that most of the functions in XMonad.Util.SpawnOnce rely on XMonad.Actions.SpawnOn.manageSpawn. Also, reexport that function for convenience. Closes #663.
Checklist

[x] I've read CONTRIBUTING.md

[x] I've considered how to best test these changes (property, unit,
manually, ...) and concluded: documentation change

[n/a] I updated the CHANGES.md file

Uh, hold on, editor used tabs…


Legacy Bug - Middle click scrolling not working on pinned columns

I'm submitting a ...  (check one with "x")
[x] bug report => search github for a similar issue or PR before submitting
[ ] feature request
[ ] support request => Please do not submit support request here, instead see https://github.com/ceolter/ag-grid/blob/master/CONTRIBUTING.md#question

Current behavior
This is a bug that happened since forever, but sometimes was seemed to be fixed. Currently, V8, not fixed.
When pinning a column (left) and then trying to use middle mouse click to scroll down on the pinned column - can't (The container with scrolling is on the right)
When pinning right and then trying to use middle mouse click to scroll down on the main table, you can't.
Double pinning - scroll down available only on the right.
Expected behavior
Be able to scroll down on all sections of the viewport
A fix direction
As far as I understand, the scroll-able view is always on the right, for it to always appear like the scrollbar isn't moving, and is scrolling the entire table. (and right one syncs to everything)
The simplest solution in my opinion, would be to have scrollbars on all views, styled to be hidden, and sync all of them. Although, this is a very naive solution, and you probably know better
What is the motivation / use case for changing the behavior?
Super annoying to fail to scroll
Please tell us about your environment:
https://www.ag-grid.com/example.php

ag-Grid version: 8.0.0

Browser:
"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36"

ta, will raise jira at medium priority. i can't remember off the top of my head why i choose not to have hidden scrolls on the other rows.

tracked by AG-238


Logic Analyzer should report channels it was unable to render

At this point, if a channel is requested, but not found in the log, the renderer just renders a blank channel.
I want it to ignore that channel and report back to the user it was unable to render said channel.

I've changed the functionality of the ScreenRenderer class to ignore missing channels, tests show it rendering an image 3 channels tall even when 4 are requested.
I've added a report_failed_signals method. It's a bit more passive than having the class actively throw an error of some kind, but it should work just fine. For the time being though it is a facade.
I'll be implementing the actual logic here shortly.

I've added a way to extrapolate all signals not used from the requested_signals list and return them as failed_signals.
It's a hack, but it works. I'm closing this issue. I'll address the mess when I clean up the code for #3.


Feature/Update to use pedantic 1.11

Updates to use pedantic version 1.11.0 over 1.8.0. This will result in more analyzer warnings that will need to be fixed, but is worth considering as the package supports dart 2.12+.

to this been completed, it will be good to proceed and resolve all the dart analyzer issues at least all the ones set as error we can work warnings for later.
version update only I think it is not enough. let me know if you need help with this.

@defuncart do you know if there is a log somewhere with the differences between those pedantic versions?

@matthew-carroll There is some info on the change log, about 20 or so new rules added since 1.8.

@Arkangel12 Running flutter analyze on main reveals the following errors and warnings

So actually this PR doesn't introduce any new errors, just new warnings (about 260 more).
Most of the errors stems from example/integration_test as in example/pubspec.yaml integration_test is commented out. I pushed a simple fix for the uri error as it is unclear if example should have integration_tests or not.
Feel free to close this PR if it is not applicable at this time.

I'm gonna merge this in before I restructure the repo. We can deal with the warnings later.


ES6 import support

Any plans to implement es6 style imports?

Looking into it. The syntax is very different.
It might be relatively straightforward to do this syntax:
//--myFunc.js--
export default function() {
   return 'foo';
};

// --main.js--
import * as myFunc from "../path/to/myFunc.js";
console.log(myFunc()); // logs 'foo'

But the import statement syntax below doesn't give me any information to work with when determining the file to use for the import statement until you have already typed out the module:
//--myModule.js--
export function getFoo() {
   return 'foo';
};

// --main.js--
import { getFoo } from "../path/to/myModule.js";
console.log(getFoo()); // logs 'foo'

Not sure if Jetbrains provides a way currently with their javascript library to quickly look through the exports of all the files in a project. If it does, then it might be possible to add support for it. So that's what I am investigating at the moment.

+1

I have a branch up with basic support simple imports: https://github.com/jballant/CommonJSAutoComplete/tree/feature-es6-import.
You can download and manually install the zip file if you would like to try it out.
At this point, the autocomplete will work for importing a complete module like this:
// ./lib/MyClass.js
export default class MyClass {
    // class
}

// ./main.js
import MyClass from './ilb/MyClass';
// " from './lib/MyClass' will autocomplete once you've typed "import MyClass"

It only works with the default export at this point. I'm investigating other syntaxes.

Basic ES6 import support is in the current version, so I will close this issue for now.


Orphanet mapping for July release (the correct PR)

Spreadsheet is here: https://docs.google.com/spreadsheets/d/1Xq2g3Kn4eWyUUmRvNvXZU1bytmepMWc_DSPM71UdIFc/edit#gid=0

I am bypassing the branch protection because Nicole has already approved PR #7819, and this one is the same (without the parentage error).


Switch to useId for more consistent SSR

Looks like using React's useId is a more consistent solution for this library. It is isomorphic and covers all SSR and hydration edge cases.

I agree that the built-in useId is a better option going forward. I will migrate to it and publish a major version when I will have more free time in the upcoming months.
In the meantime, you can use a provider (see SSR example) to generate correct IDs during SSR.

Thanks, PRs are welcome

@laleksiunas Hi, I have created a PR to allow the use of a custom id generator hook, can you help review it?


Empty results

I used the git codespace to test the samples and none of the images are generating the markup. The output file is empty with errors.

Sorry, but I can't see the errors in the above image.

hi, to work with jpg files, you'll need ExifTool and an OpenAI API key so markitdown can extract text and convert it

I don't understand why they aren't using an open-source OCR tool or an open-source model as it's an open-source project.

Feel free to create an issue or PR? You can always supply a custom client from OSS model eg Ollama.


Remove old "course" theme.

We currently have two course themes, "course" and "course-v2". This causes some confusion, especially in regards to bug fixes.
Many of the bugs in "course-v2", e.g., #982, were inherited from "course". So when we fix the bug, do we fix it in both or just v2? And if we fix it in both, should reviewers test the change in both? Should we verify the commit on rc in both? (Probably not).  This is especially confusing for new contributors.
Acceptance Criteria

[ ] confirm that no courses on prod/rc are using the theme
[ ] remove old "course" theme and associated CI actions
[ ] remove old course config from ocw-hugo-projects

@gumaerc Am I missing anything in the above to-do list?
@pdpinch @gumaerc are we actually ok removing the old theme? I think we should. It has caused confusion in some PRs. (e.g., #984 )

I think we are good to remove the original course theme at this point. We should preserve a copy of it somewhere in version control in case we ever need to refer to it in the future for historical reasons, but there shouldn't be anything actively using it anymore.


Release 0.4.0

Hi! I was happy to find this crate and wanted to use it in my project. Are there any 'blockers' for releasing the 0.4.0 version of this crate? I need some of the functionality that has been added since 0.3.2

Hi @lulf - short answer is our 10 month old baby 🤣. It hasn’t been a top priority for any work, so it fell down the list. I can spend some time this afternoon to come back up to speed and get at least the work that’s already been done published as a new version. I expect I’m behind the current draft standard by at least a bit again. Thanks for reporting issues as you find them.

Thanks for the poke on this @lulf! I dug up some previously uncommitted WIP which was blocked on a change to the CPE crate that shipped in September. I incorporated that, your contribution, and a couple other maintenance upgrades in a v0.4.0 release which is live on crates.io. I suspect we're now a bit behind the current editor draft of the spec, which I might have some time to investigate this weekend. I also opened a couple other issues to track improvements that have been on my mind.

Thank you!


"impact search" should return the result sorted

Also allow a list of ALL available libs. This seems currently to work with impact search "" but is not intuitive.

This needs to be revisited with the Go version.
One thing to consider, when talking about searching.  When crawling, I just store all the libraries I crawl.  I do not store them by name (alone).  The point here is that there may be forks and I'd like to store all possible versions and then disambiguate which specific fork using some kind of URI as the true unique identifier.
Now, I haven't implemented this yet.  But if impacts install and search (and probably others) because of the need to handle the case where there are multiple versions of a library with the same name.  I'm not sure yet how to actually render that for end users.  But it is something we need to think about.

One other comment...I propose sorting these by stars (with perhaps some kind of tweak to bump up official MA libraries).

Was closed by a commit, but shouldn't have been.

My plan is to provide a --all flag for search.  Normally, the default is "false" (i.e., don't display all possible results).  In that case, the search will only be done over the set of libraries that would be installed (i.e., the first with that name in the list unless explicitly called out by a choice settings in the users impactrc file).
In the case where the --all flag is set, the search results will show all libraries.  In the case where multiple libraries with the same name match, the one that would be installed will be shown as the "main" result and then all other matches will be shown as "also" matches.  The "also" matches will be sorted by rating (and the rating of the "main" result will indicate rating as well).
Sorting by rating only would be misleading because the user might assume that if they do an install, the highest rated one is the one that would get installed (since it would appear first in the list).  Showing them by order is also not good because a highly rated library might appear last.  So this is the best compromise I could think of where the selected library appears first and the remaining ones are sorted by rating.


Display Contributors Profile in ReadMe

Go for it @Safnaj!!

https://github.com/avincodes/Web-dev-Snippets/pull/41


Document that annotation values can only be strings

This is a Feature Request
Currently only key validity is specified. There is no mention on https://kubernetes.io/docs/concepts/overview/working-with-objects/annotations/ that e.g. numeric, boolean, list or other types for annotation values are not permitted.

/triage accepted
/sig architecture

/remove-lifecycle stale
/assign


gbrs_emissions_all_tissues.avecs.npz output file question

Hi Jackson Lab,
I was looking at the output of the the gbrs_emissions_all_tissues.avecs.npz file and I wanted to make sure I was understanding this correctly? Correct me on this if I am wrong because I am new to emission probability but in this file, is it basically the header or name is
the gene and for each gene there is an array of numbers and each one represents the  probability  for the  haplotype or mouse strain associated with that gene? Also, are there several arrays for one specific gene because it is showing all of the possible combinations and predictions based on the Hidden Markov model?

@lawtyunc your questions fall outside the scope of issues we support in this repository. Your statements seem correct, but I suggest contacting the GBRS developers for confirmation and any further questions related to GBRS.


bead develop silently overwrites existing local directory?

having an existing bead x
$ bead develop x
$ bead develop x

works he second time without error/warning

Fixed in 24a1d70ddd27d11fc59846d2babac26c6808d504


Remove unused trait and case class

The trait WorkerState and case class WorkerData are no longer used
anywhere. Keeping them in the code base makes no sense.

Description

Related issue and scope

[ ] I opened an issue to propose and discuss this change (#????)

My changes affect the following components

[ ] API
[ ] Controller
[ ] Message Bus (e.g., Kafka)
[ ] Loadbalancer
[ ] Invoker
[ ] Intrinsic actions (e.g., sequences, conductors)
[ ] Data stores (e.g., CouchDB)
[ ] Tests
[ ] Deployment
[ ] CLI
[ ] General tooling
[ ] Documentation

Types of changes

[x] Bug fix (generally a non-breaking change which closes an issue).
[ ] Enhancement or new feature (adds new functionality).
[ ] Breaking change (a bug fix or enhancement which changes existing behavior).

Checklist:

[x] I signed an Apache CLA.
[x] I reviewed the style guides and followed the recommendations (Travis CI will check :).
[ ] I added tests to cover my changes.
[ ] My changes require further changes to the documentation.
[ ] I updated the documentation where necessary.

Thanks @georgianfire.

I think this would be great to include in the 1.0.0 release.
Shall we merge this?

👍


There might be mistakes in the perimeter network diagram

There might be mistakes in the routing tables associated with Perimeter PerimeterNat and Perimeter-Tgw route tables.
The diagram is located here.
https://github.com/aws-samples/landing-zone-accelerator-on-aws-for-cccs-medium/blob/main/architecture-doc/images/network/high-level-network-Perimeter.drawio.png
The network firewall is located at perimeter subnet. And the design principal is to direct all traffic to network firewall first.
So:
For Perimeter route table,
<IP_ADDRESS>/0 -> nat gateway
Supernet -> Tgw
For PerimeterNat route table, this subnet  contains the NAT gateway
<IP_ADDRESS>/0 -> igw
Supernet -> Network firewall
For Perimeter-Tgw route table
<IP_ADDRESS>/0 -> network firewall
The PerimeterNat should be our public subnet.

Hi sdzhangtao,
Thanks for creating this issue. I will review this with the team.

Hi sdzhangtao,
The current diagram aligns with the changes introduced in version 1.9.2-b with the addition of the IGW-Ingress-Routes route table.
The routes described above are those in place prior to this change. Detailed instructions to make the changes can be found here

Hi Ryan,
Thanks for your reply. I see it now and I like it a lot better with this change.
Our current version is 1.10.x. So I think it's better to apply the 1.9.2-b changes.


Add --watchAll=false to coverage docs

Is your proposal related to a problem?
Yes, when I follow the instructions on https://create-react-app.dev/docs/running-tests/#coverage-reporting to run coverage reporting, I get an empty report. Others have reported this in #6888 #7838 #9322 #9876.
Describe the solution you'd like
Until this changes, I propose updating https://github.com/facebook/create-react-app/blame/master/docusaurus/docs/running-tests.md#L179 to prescribe npm test -- --coverage --watchAll=false
Describe alternatives you've considered
Ideally this behavior would be changed by the Jest team, but https://github.com/facebook/jest/issues/7331 doesn't seem to have much activity. Maybe there's another issue that's tracking it.

I've opened a PR for this, please let me know if this feature request is inappropriate and I'll close it.

This should be default honestly, very confusing why it defaults to watch in the first place.

Just for your information, in my environment, I reproduced the same problem but it outputs the full coverage reports when I manually pass --watchAll with --coverage.
🙅♂ react-scripts test --coverage
🙆♂ react-scripts test --coverage --watchAll


[forwardport] Support Istio Gateway as first class resource in Rancher UI

[forwardport] https://github.com/rancher/rancher/issues/20892

Currently blocked by reopen of #23370

rancher/rancher:master-head 1304c55a2
ui: vmaster-dev

Gateway navigation tab is shown
All Istio navigation tabs are shown
Imported gateways appear in UI w/ correct values
Created gateways are functional
Gateway inputs match resulting CRD


[RFC]: refactor blas/ext/base/dcusum to follow current project conventions

Description
This RFC proposes refactoring @stdlib/blas/ext/base/dcusum to follow current project conventions.
These conventions are outlined in more detail in https://github.com/stdlib-js/stdlib/issues/788. Namely, we want to migrate from C++ add-on interfaces to C add-on interfaces and then make various style and simplification changes.
Some example commits which perform most, if not all, of the requested changes include https://github.com/stdlib-js/stdlib/commit/d66d80cfcbab1da95cb5ae8cfae4a1fc4c5129d1 (saxpy),  https://github.com/stdlib-js/stdlib/commit/3c82fe7b6c0f9fd6ef02c86d6e2024d708ac8c14 (cswap), and https://github.com/stdlib-js/stdlib/commit/5b15c9675be434c0e11b1ec1e1f78d7b089abbcd (dasum).
Related Issues
Related issues #788, #1152.
Questions
No.
Other
No.
Checklist

[X] I have read and understood the Code of Conduct.
[X] Searched for existing issues and pull requests.
[X] The issue name begins with RFC:.

@Planeshifter, started working on this issue.


How to fill unavailable data with last available data

For example, suppose volume data for AAPL on 2020-03-03 is missing. It looks like the current handlers will generate volume related features as 0, which worsen the model. Would it be possible to define a handler, to fill missing data with the data from the previous day?

You can use this operator.
https://github.com/microsoft/qlib/blob/main/examples/highfreq/highfreq_ops.py#L54
PS: please remember to register it before using it.


[golangci-lint] Remove deprecated setting from staticcheck config

What does this PR do?

Remove a useless line from the golangci-lint config.
Motivation

I found it weird to have a go: 1.17 in that config file.
I looked quickly and it seems to be a deprecated setting. Removing it still works.
Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

Reviewer's Checklist

[ ] If known, an appropriate milestone has been selected; otherwise the Triage milestone is set.
[ ] Use the major_change label if your change either has a major impact on the code base, is impacting multiple teams or is changing important well-established internals of the Agent. This label will be use during QA to make sure each team pay extra attention to the changed behavior. For any customer facing change use a releasenote.
[ ] A release note has been added or the changelog/no-changelog label has been applied.
[ ] Changed code has automated tests for its functionality.
[ ] Adequate QA/testing plan information is provided if the qa/skip-qa label is not applied.
[ ] At least one team/.. label has been applied, indicating the team(s) that should QA this change.
[ ] If applicable, docs team has been notified or an issue has been opened on the documentation repo.
[ ] If applicable, the need-change/operator and need-change/helm labels have been applied.
[ ] If applicable, the k8s/<min-version> label, indicating the lowest Kubernetes version compatible with this feature.
[ ] If applicable, the config template has been updated.

/merge

Sad merge queue :cry:


Leverage new RN JS Navigation

Facebook is working on a revamp of the JS Navigator and the preview is available here: https://github.com/ericvicenti/navigation-rfc
@ohanhi I believe this would solve the major blocker with the current implementation of the Navigator.

Oh wow. I will have to look into this. Thank you very much, @tlvenn!

Well I am glad I could be of help and thank you and @staltz for this awesome project !

Update: this is actually moving along nicely. NavigationExperimental is now in RN master branch, and there's some improvements to it already in progress: https://github.com/facebook/react-native/pull/5912

We tried updating react native to the current master in order to leverage the new navigation in https://github.com/elm-native-ui/elm-native-ui/compare/master...mk:navigation-experimental but it seems changes to the require polyfill are currently breaking Elm.
We had to move the F2 etc functions of the generated elm.js up a level to get it to work, see https://github.com/elm-native-ui/elm-native-ui/commit/16db2a046e4a1529177b3aa3c1d54c0acc326d45

@mk Interestingly, the anonymous function has always been there and it works under RN 0.14. But now that I am trying to upgrade to 0.21.0-rc, I am facing the same issue as you did: Can't find variable: F2. So strange.

@ohanhi Yeah, I was really surprised by that as well. But what do you mean with "has always been there"? As far as I saw, the anonymous function in the processed version of elm.js gets wrapped one more time additionally after upgrading RN.
Sorry for just providing screenshots here, but I found these in my scrap notes when I was digging into the issue.
Before upgrading RN:

After upgrading RN:

This is from compiled js which gets served from the react packager.

@kommen Where did you get that twice-wrapped file from? I can't see double (function() { rows in the compiled elm.js or in DevTools.

The undefined functions issue was circumvented in https://github.com/elm-native-ui/elm-native-ui/pull/14

With #44 and #49, I'd say this is now done!


Handle flat and nested dependency tree

This change is meant to address that scenario when you have conflicting versions of dependencies. In that case npm 3 would still install it nested while also have it in the top level node_module. My change tries to resolve the deep dependency (nested one) and then does a fallback to flat.

@matthewdavidson made it recursive not to miss any potential sub-package


ConsumerSeekAware broken with upgrade from 1.1.5 to 1.1.6

Having a listener which implements ConsumerSeekAware annotated with @KafkaListener works fine in 1.1.5 but not in 1.1.6:
@Component
public class EntityChangedEventConsumer implements ConsumerSeekAware {
@KafkaListener(topics = "${kafka.consumer.topic}")
    public void onMessage(ConsumerRecord<String, EntityChangedEvent> data) { ... }
}
   @Override
    public void registerSeekCallback(ConsumerSeekCallback callback) {
    }

    @Override
    public void onPartitionsAssigned(Map<TopicPartition, Long> assignments, ConsumerSeekCallback callback) {
      ...
    }

    @Override
    public void onIdleContainer(Map<TopicPartition, Long> assignments, ConsumerSeekCallback callback) {
...
    }

None of the ConsumerSeekAware-EntryPoints are called in 1.1.6.
Since #324 ConsumerSeekAware implementations are detected on this.genericListener
But this.genericListener is always assigned to listener:
line 354 KafkaMessageListenerContainer -> this.genericListener = listener;
The case of having a GenericAcknowledgingMessageListener is lost:
line 331 -> this.theListener = listener == null ? ackListener : listener;

Fixed via https://github.com/spring-projects/spring-kafka/commit/b02ecd6fb52dd5b50c78a3aa6f4ac97d264bc7b7

Hi, using version 1.2.2.RELEASE here and the methods are still not invoked.
Using a ConcurrentKafkaListenerContainerFactory and a listener with KafkaListener annotation and implementing ConsumerSeekAware like described in this issue.
Like @tbinias has described, when arriving at below condition in KafkaMessageListenerContainer in createRebalanceListener method, genericListener is null.
if (ListenerConsumer.this.genericListener instanceof ConsumerSeekAware) { 	seekPartitions(partitions, false); }
Also, I added the idle interval config like @garyrussell said in this stack overflow thread: https://stackoverflow.com/questions/46321483/spring-kafka-consumer-seek-aware-methods-not-invoked/46325685?newreg=5487961b397b4c7387b56694c6798884
I am using auto commit and I have auto offset reset set to "latest" if that changes anything.
something I am missing?
Thank you very much for your help!

Well, the fix is there already after release 1.2.2: https://github.com/spring-projects/spring-kafka/commits/1.2.x .
We may release 1.2.3 if that is a strong requirement.

My mistake, sorry; my local 1.2.x branch was out of date; I somehow reasoned it wasn't an issue on that branch.
@artembilan Please go ahead and release 1.2.3 tomorrow, while I am in transit; thanks.

Spring Kafka 1.2.3 has been released.
You can obtain it from the https://repo.spring.io/release/org/springframework/kafka/spring-kafka/1.2.3.RELEASE/
Will be in the Maven Central in a couple hours.


Support multiple translations

Describe the solution you'd like
It would be nice if we could support multiple languages based on the users language. The default language should always be English.
Created the issue to discuss this topic.
Additional context

I think ngx-translate will be the package to use?

For people looking through the issues. The initial implementation will be Dutch, English as you can see in PR #305.
Would you the support for a another language, please let us know!


Fix development VM provision scripts

Fixes https://github.com/cilium/cilium/issues/6081

This change is

test-me-please

Coverage increased (+0.1%) to 43.485% when pulling d10b3ccaa445ea254d1f04c755bf140399477f5a on pr/fix-dev-vm-bugs into 01010a9013063f1efb68e94136260be31237dcf3 on master.

test-me-please