Sometimes the progress bar stay shown

I'm using the following setup:
        <fr.castorflex.android.smoothprogressbar.SmoothProgressBar
            android:id="@+id/progress_bar"
            android:layout_width="match_parent"
            android:layout_height="wrap_content"
            android:layout_gravity="bottom"
            app:spb_colors="@array/progress_color_table"
            app:spb_mirror_mode="false"
            app:spb_progressiveStart_speed="1.5"
            app:spb_progressiveStop_speed="3.5"
            app:spb_reversed="false"
            app:spb_sections_count="5"
            app:spb_speed="2.0"
            app:spb_stroke_separator_length="2dp"
            app:spb_stroke_width="4dp" />

Programmatically i simply show and hide the bar like this:
        if (visible) {
            progress.progressiveStart();
        } else {
            progress.progressiveStop();
        }

But under some circumstances the bar stays visible on the right side with a few pixels. Would be good what i can adjust to fix that behaviour.
Thank you very much,
Daniel

It happens to me all the time. Did you find a solution @drindt ?

+1
I'm also looking for a solution on this bug.

you can reduce "spb_progressiveStop_speed" value to solve it. its by default 3.4, change it to 2.4 for example.

I think this happens because you guys call progressiveStop() multiple times before the bar is completely out of the screen. I tried several times with different configurations and could only recreate the issue when I did this.


moves composer into the PHP directory and requires protobuf

The composer.json should not be in the root when the repo is not registered with packagist. Because the subdirectory gets copied over, it makes sense to have the composer.json in there.
Additionally, because the autoload error is fixed with google/protobuf, we should now be requiring that library as a hard dependency in composer, and the users can install the protobuf C extension optionally for better performance.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

I can probably take care of this a bit later. The changes cannot be made directly to these files. These files are generated from the templates/ directory.

@stanley-cheung I just updated composer.json.template, just in case. But ok sounds good! The main thing is to not have two composer.json files in this repository, and to add the hard dependency on google/protobuf back in.

Sorry should have made it more clear. The order of operations should be:

Do all your changes in the templates directory. So if you want to remove the root composer.json file, you need to remove templates/composer.json.template. If you need to update src/php/composer.json, you need to make the change in templates/src/php/composer.json.template.

After making all the changes to the templates directory, run ./tools/buildgen/generate_projects.sh. That should re-generate all the relevant files. So after this, the root composer.json file should be gone. The src/php/composer.json file should reflect the changes you wanted to make.

Done, PTAL


Login validation

Added validation for login using the Zod library.
Disabled the default built-in validation of the form
Added a fixed width of the container, so when error message occurs the input fields doesn't stretch

Not sure why all the tests fails.. :D


Access time from clock in models

Access to time, eg. to publish stamped message types
Support for timers (wait x sec)

For now, the workaround is to make a small, additional SCXML Component. Therefore we lower the prio here to middle.
Ref. https://github.com/convince-project/AS2FM/blob/main/test/jani_generator/_test_data/uc2_assembly/Components/Clock.scxml


Job Request Page

Build a page that will help a user through generating a job request to be sent to a Providing user

Frontend page design
Frontend API calls to store job requests
Backend user framework:
Job request Database
Job request Model & Controller
Middleware between database and backend API system

It looks as though this was implemented, is this complete?

Not yet, still need to put the data together and build the API POST call for a job row


storage client no retry， retry is completely invalid.

The current storage client retry mechanism is completely wrong.
For example
1）a host's request contains 2 parts, a part succeeds, the other has leader change,
2）a host's request contains 3 parts, one part is successful, and the other two parts have leader change, and these two parts correspond to two leaders respectivelys.
In two way, how many times the request is retried is always an error. Retrying is completely invalid.
There are two solutions:

The storage client does not retry, modify the leader host of all the parts of the leader change, so the next time you re-execute sql, it will succeed
Storage client retry. When the errcode in the same request is leader change, it will retry, otherwise it will not retry. Need to reorganize the leader change requst in the same request of collectResponse and getResponse. Then it may be sent multiple times.

The current pr is not to retry for storage client，I prefer storage client not to retry
Please hold this pr first for chaos test
The retry of storage client  pr will also perform the chaos test.

Good catch. Maybe we could reorganize the request of  one host as map<PartID, Request> in this form it's easy to reform when retry request.

Good catch. Maybe we could reorganize the request of  one host as map<PartID, Request> in this form it's easy to reform when retry request.

map
shoud map<leaderHost, Request> Both ways are ok, I am testing

map
shoud map<leaderHost, Request> Both ways are ok, I am testing

map
shoud map<leaderHost, Request>
Both ways are ok, I am testing

I means map<Host, map<PartID, Request>>

map
shoud map<leaderHost, Request>
Both ways are ok, I am testing

I means map<Host, map<PartID, Request>>

map
shoud map<leaderHost, Request>
Both ways are ok, I am testing

I means map<Host, map<PartID, Request>>

Shouldn't be like this,
The request contains the parts contained in the request,  and the redundant part contained in the request   should be removed

map
shoud map<leaderHost, Request>
Both ways are ok, I am testing

I means map<Host, map<PartID, Request>>

Shouldn't be like this,
The request contains the parts contained in the request,  and the redundant part contained in the request   should be removed


Missing test file

In Get.cs the test X has a hardcoded reference to a test file not found among the included test files.
using (GribFile file = new GribFile(@"C:\Users\eric\Documents\Visual Studio 2013\Projects\AccessViolationTest\AccessViolationTest\data\CMC_reg_TCDC_SFC_0_ps10km_2016031100_P000.grib2"))

Fixed


Use appveyor.yaml for CI config

This allows us to use some more fancy configuration options for CI.
Creates two configurations, one for master and one for v1.1.x. Master no longer builds VS12, but v1.1.x will

We will have to merge this into v1.1.x too. AppVeyor recommends that you use a common appveyor.yml across all branches to avoid merge conflicts.

Also, after this change, the AppVeyor UI settings will no longer do anything..

:+1:
Regarding our earlier discussion... what happens in the event that we are locking down for a release and potentially submitting patches to a different branch? Do we need to add a new entry to the AppVeyor run every time?

@mousetraps Yes, but there are a few options in my understanding:

Before creating the new branch, update the appveyor.yaml to in the parent branch to reference the new branch as well.
Update the appveyor.yaml to use simple patterns for the branch name matching. That would allow us to build all v1.x.x branches for a given config.
Create a fallback, default entry in the appveyor.yaml that builds any branch not explicitly matched.

New branch creation process
If neither branch name glob matching or the fallback would work, and we instead want to make new branches fully opt-in, I believe that the steps to create a new branch would look somewhat like this (new branch is called v2.7.1 and branched off of master and using its config in this example):

In master, add a new entry for v2.7.1 to the only block in the master AppVeyor config.

We generally want to update master instead of editing the appveyor.yaml in the branch to avoid merge conflicts if v2.7.1 is merged back in.

Submit the appveyor.yaml change to master
Create branch v2.7.1

Now any changes pushed to v2.7.1 should get built using the updated config.


Missing babel-preset-es2015 dependency

After install it in React Native, I'm getting a error due to babel-preset-es2015 is not added as a dependency in my code.

js-base64 itself is standalone, has no dependency unless you use it with React Native in which case babel-preset-es2015 is required.  Just
npm install --save babel-preset-es2015

before
npm install --save js-base64

This is because .babelrc file is included in the npm package.
Please add .npmignore to exclude .babelrc from the published package.

@dankogai ^

Fixed as @craftzdog suggested in
https://github.com/dankogai/js-base64/commit/3e048fce9f749e6f9738d130e5ca20c4a2dd9d43 .
npm published as well.

Thank you for the quick fix, @dankogai!


Dialog not popping up...

Do you have a demo on how to get this to work with iOS 15? Good work. Thx

Hi @johng1492,
sorry for the delay in answering your issue. You are right that the dialog wasn't shown on iOS15.
I've adjusted the code so it is working now on iOS15 again. Before calling ATTrackingManager.RequestTrackingAuthorization we need to wait a little bit. This was achieve by adding a Task.Delay. Now the dialog is showing on iOS15.


YouTube Live Broadcast API: liveStreamingNotEnabled thrown when enabled.

Environment details

OS: macOS 10.15.5 & CentOS 7.8
PHP version: 7.4.5
Package name and version<EMAIL_ADDRESS>
Steps to reproduce

Follow any liveBroadcasts example in the following page: Use Cases and Code Snippets.

Code example
$client = new Google_Client();
$client->setApplicationName('API code samples');
$client->setScopes([
    'https://www.googleapis.com/auth/youtube.readonly',
]);

$client->setAuthConfig('YOUR_CLIENT_SECRET_FILE.json');
$client->setAccessType('offline');

// let's assume we have a token saved in the session for now.
$client->setAccessToken($_SESSION['accessToken']);

// Define service object for making API requests.
$service = new Google_Service_YouTube($client);

$queryParams = [
    'broadcastType' => 'all',
    'mine' => true
];

$response = $service->liveBroadcasts->listLiveBroadcasts('snippet,contentDetails,status', $queryParams);

Issue description
The problem arises on the last line of this example. A Google_Exception is thrown with the following identifier: liveStreamingNotEnabled. It comes along with this help link which takes you to your account features and status.
In my personal case, not only did I have Live Streaming enabled but I also had no strikes whatsoever and have been streaming for years on YouTube. So, I know for a fact that my account is indeed enabled for live streaming.
What did I do? I ditched the PHP client library for that single fetch and went on to try with cURL. Guess what. It worked. I am still using the PHP client library but only to authorize the app, get access tokens, and whatnot. But I have to use cURL whenever I need to fetch stuff from the authorized user's account.
More about this issue is detailed on this StackOverflow question that was asked on November 9, 2016 and never answered, even with a 100-point bounty, to this day (June 15, 2020).

Any chance you want to add the curl request you used that worked?

Yes, of course.
$endpoint = 'https://www.googleapis.com/youtube/v3/liveBroadcasts?part=snippet,contentDetails,status&broadcastType=all&mine=true&key=[YOUR_API_KEY]';
$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, $endpoint);
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, [
    'Accept: application/json',
    'Authorization: Bearer '.$_SESSION['access_token'] // make sure this exists
]);
$output = curl_exec($ch);
curl_close($ch);
$res = json_decode($output, true);
if(isset($res['error'])){
    throw new Google_Exception($res['error']['message']);
}

Hi @zeke0816 , thank you for the detailed bug report. Unfortunately, this issue tracker has limited visibility and scope - basically, it's just for reporting issues with the samples contained here and is only watched by the folks who work on these samples.
We are happy to help you move this bug to venues where it'll get the attention of the appropriate product teams.

StackOverflow's Google API PHP client and YouTube tags is most appropriate for design and general troubleshooting.
Google Youtube API's public issue tracker is most appropriate for bugs and unexpected behavior.

I'm going to close this issue because the folks who own this repo have no actionable way to resolve it directly, but please let us know if there's anything we can do to help!


Improve test targets in Makefile

enable running eunit and retest tests separately
add neccessary dependencies to each test target so that
one can just do 'make test' without recompiling changed files
manually
enable overwriting retest's log level
use retest's own Makefile instead of invoking rebar manually

I'm fine with this. @tuncer ?

Other than the unneeded debug build of retest, +1.

@kejv you may want to append your name in THANKS as part of this commit.

I would wait with adding my name to THANKS, since I am currently working on some bigger refactor as part of #357, and then you will see if it's worth thanking me or not :-)

+1, but please don't forget to squash the fixup first.

Ok. Ready to merge.


No Longer Maintained?

There are 12 open pull request from contributors dating back to 16 Oct 2018 (almost 6 months). Is this project no longer maintained by the author?

Hey @travis5491811, slowly but still maintained.


Error when keying Sprite's frame property

Godot version
bc2445d
System information
W10
Issue description
When you create animation for Sprite node, there's this frame property auto-increment, i.e. you press the Key button and it will insert the frame key and automatically increment the property, so you can just click it a couple of times and you have animation.
This is very minor issue, but this never checks the sprite's bounds. If you reach the final frame, you will get an error with every Key press that the frame is out of bounds.
The relevant code is in editor_inspector.cpp if anyone is up for a fix. The editor should just bounds check the next frame before incrementing.
Steps to reproduce

Add Sprite2D/3D
Add AnimationPlayer
Create animation
Insert keys for the frame property in sprite
Just keep doing it
Errors

Minimal reproduction project
No response

I believe what the fix we're looking for is here:
if (use_keying_next()) {
	if (property == "frame_coords" && (object->is_class("Sprite2D") || object->is_class("Sprite3D"))) {
		Vector2i new_coords = object->get(property);
		new_coords.x++;
		if (new_coords.x >= object->get("hframes").operator int64_t()) {
			new_coords.x = 0;
			new_coords.y++;
		}

		call_deferred(SNAME("emit_changed"), property, new_coords, "", false);
	} else {
		call_deferred(SNAME("emit_changed"), property, object->get(property).operator int64_t() + 1, "", false);
	}

	call_deferred(SNAME("update_property"));
}

Just adding bounds here for new_coords. Is it as simple as adding it to the general conditional (e.g. calling call_deferred(SNAME("emit_changed"), property, object->get(property).operator int64_t() + 1, "", false); when out of bounds) or do we want to handle it in a special way when we get out of bounds


Moving sentinel(8) resources to v1beta1 version

sentinel 8

[ ]  azurerm_sentinel_data_connector_dynamics_365
[ ]  azurerm_sentinel_data_connector_microsoft_threat_protection
[ ]  azurerm_sentinel_data_connector_office_365_project
[ ]  azurerm_sentinel_data_connector_office_atp
[ ]  azurerm_sentinel_data_connector_office_irm
[ ]  azurerm_sentinel_data_connector_office_power_bi
[ ]  azurerm_sentinel_alert_rule_nrt
[ ]  azurerm_sentinel_alert_rule_scheduled

message: 'apply failed: creating Data Connector: (Name "sdcoaex" / Workspace Name
  "sdcoaex" / Resource Group "sdcoaex"): securityinsight.DataConnectorsClient#CreateOrUpdate:
  Failure responding to request: StatusCode=401 -- Original Error: autorest/azure:
  Service returned an error. Status=401 Code="Unauthorized" Message="Access denied": '

Require 'Global Administrator' or 'Security Administrator' on the workspace's tenant.

azurerm_sentinel_alert_rule_scheduled same issue:
"Failed to run
the analytics rule query"


style:resync token styles to DS component theme

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[Question] Railway Generation

Hi,
is there are reason why railways are not generated with the roads? Would be cool if they were also generated. Thanks for developing this mod.

Yeah, I'm just not sure how to automatically place rails nicely. It's probably possible I just haven't gotten around to it.

Ah okay. Thanks for the response though


Fix many instances of CodeFactor style issue A single-line comment must not be followed by a blank line

PR Summary
Fixes this simple style issue, improves general code health.

PR Context

PR Checklist

[X] PR has a meaningful title

Use the present tense and imperative mood when describing your changes

[X] Summarized changes
[X] Change is not breaking
[X] Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
[X] This PR is ready to merge and is not Work in Progress.

If the PR is work in progress, please add the prefix WIP: or [ WIP ] to the beginning of the title (the WIP bot will keep its status check at Pending while the prefix is present) and remove the prefix when the PR is ready.

User-facing changes

[X] Not Applicable
OR
[ ] Documentation needed

[ ] Issue filed:

Testing - New and feature

[X] N/A or can only be tested interactively
OR
[X] Make sure you've added a new test if existing tests do not effectively test the code changed

[X] Add [feature] to your commit messages if the change is significant or affects feature tests

@RDIL Thank you for your contribution.

Glad to help :)


feat: combine ops and workers into one svc type

Changes

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#957  👈
#956
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @MasterPtato and the rest of your teammates on  Graphite


Include branch name other than main in the update attribution PR title

Description of changes:
The most recent PR created by eks-distro-pr-bot to update ATTRIBUTION.txt files on release-0.20 branch did not include the branch name in the PR title. We follow the convention to prepend "[BRANCH_NAME] " to the PR title for most of the other automated PRs created by the bot when the PR is being created for any release branch in order to quickly identify the base branch. This PR updates the create_attribution function to follow this convention. The -r argument is removed for the pr_title local variable to allow updating it else it would be a read-only variable and throw an error.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/cherry-pick release-0.20

/cherry-pick release-0.19

/approve


Test helpers for assering value, reading and configuration

Dodal developers have produced various useful ways to test ophyd-async devices such as verify(). Some of these should probably make it back into main and sit alongside other helper functions like set_sim_signal.
I think we need 3 helper functions:

assert_value(signal: SignalR[T], value: T)
assert_reading(readable: Readable, reading: Reading)
assert_configuration(readable: Readable, configuration: Configuration)

Acceptance Criteria

Functions in ophyd-async
Tests provided
Docs provided where appropriate
Issues raised in dodal to replace verefy() and any other old functions that can be superseded

@coretl

Possibly also want assert_emitted from #206


Update Globalnet Pod env with the host nodeName

Related to: https://github.com/submariner-io/submariner/issues/970
Signed-Off-by: Sridhar Gaddam<EMAIL_ADDRESS>

Holding until https://github.com/submariner-io/submariner-operator/pull/997 is merged...


Top 20 referrers

If we deploy to our own CloudFront distribution, we can easily see the top 20 referrers.
I'd like to see the same report that is available on CloudFront for the top 20 referrers.  It's fine for a period of time (eg last day, last 7 days).
Additional context
This is important to us for change management and product management purposes.

It would be pretty cool to see this and other analytics passed through from Cloudfront to the Amplify dashboard


Fixed build badge / Improved Gulp file

I noticed that the build was failing for your dev branch and was causing the master branch to look like it was failing in the readme. I've updated the build badge to only show the status of master to resolve this.
I've also modified the Gulp file so that errors are better reported in Travis to help make it easier to fix a broken build.

thanks


328 servicefactory getservice test

Added tests to exercise error conditions for ServiceFactory::GetService API

Codecov Report

Merging #343 into development will increase coverage by 0.01%.
The diff coverage is n/a.

@@              Coverage Diff               @@
##           development    #343      +/-   ##
==============================================
+ Coverage        89.28%   89.3%   +0.01%
==============================================
  Files               89      89
  Lines             6225    6225
==============================================
+ Hits              5558    5559       +1
+ Misses             667     666       -1

Impacted Files
Coverage Δ

...mework/include/cppmicroservices/ServiceInterface.h
96.29% <0%> (+1.85%)
:arrow_up:

Fixes #328


How to reload the lnd.conf configuration without restarting the daemon?

latest version, how to send eg a sighup to make lnd process reload its config.
restart is horrible considering open channels etc

is there a specific setting that you want to alter?

yes: minchansize, tor.active, rpclisten, etc etc. basically everything. please help

for min chan size you can use the ChannelAcceptor API to alter requirements without a restart
For Tor enabling and disabling and RPC a restart is currently required yes

Closing as a duplicate of https://github.com/lightningnetwork/lnd/issues/800


Freezed while Initialization

Created clean droplet on DigitalOcean (512MB ram). Tried to run via docker image. Server actually works, but when I provide url and click "Render", state changes on "Initializing..." and hangs.
In console I can see only requests to web-interface and nothing more. How to solve this issue?

Do you by chance use an ad blocker? See https://github.com/scrapinghub/splash/issues/163

Oh, god. Thank you. I'm using uBlock.


ADAL is depracticed, change documentation to MSAL

Please change documentation and examples to using MSAL library and not ADAL.

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

ID: 2fc6b567-0762-fb88-e9f6-11482e81a5b2
Version Independent ID: c64e977e-5adf-e31d-955b-1bafae3e9006
Content: Call the Microsoft Graph API using OAuth from your web part
Content Source: docs/spfx/web-parts/guidance/call-microsoft-graph-from-your-web-part.md
Product: sharepoint
GitHub Login: @spdevdocs
Microsoft Alias: spdevdocs

Thanks for your post, some SharePoint docs and examples are maintained by the community, so they will not be updated in real time. Welcome to submit any pull request for contribution.

If you want to access the graph / AAD protected end points, we've made it significantly easier.  Follow these two tutorials:
https://docs.microsoft.com/en-us/sharepoint/dev/spfx/use-aadhttpclient
https://docs.microsoft.com/en-us/sharepoint/dev/spfx/use-msgraph


Hybrid Feature Type Support

Now in Shifu only categorical and numerical features are supported. While considering such feature which is numerical:
1, 3, 0, A, V, C, A, 4, 2, ...
Consider such feature as Hybrid and compute binBoundary only in numerical part, binCategory in categorical part. Then it is good to do woe transform for NN/LR training.

Define a new column type which is Hybrid compared with Categorical and Numerical

Add a new config file for user to define hybrid feature which is hidden by default
User can define types like a,b,c or  <= 0 as expression

For Hybrid feature: Do stats for both numerical stats to compute numerical boundaries and categorical stats to compute categories; Then such stats results will be set in both binBoundary and binCategory; ‘binPosRate,‘binCountWoe’ … will be combined by both. And Missing value is in last element if have.

Norm for both WOE and ZScale
a)	WOE is easy, numerical and categorical value can both be set to woe values
b)	ZScale is OK, numerical values is on ZScore, categorical features can be set to binPosRate; at this part, as not meaningless for such norm, maybe better to limited for only woe transform

Training & Eval
a)	NN/LR Training is OK as it is based on norm output
b)	Tree Training has some issues as in the before only numerical and categorical features can be used to split a node. As a hybrid feature, at first version, we can still treat it as numerical; then in the future, I am thinking to compute info gain on both numerical bins and categorical bins, then get split on both types. More computation will be excepted.

PMML Support: http://dmg.org/pmml/v4-1/Functions.html#xsdElement_Apply
After evaluating on PMML, DefinedFuntion and Apply can help us  to define such transform. I just implemented binary format NN model like GBT, in my tests of these days, I found the flexibility of binary format to define any transform and better SLA. In production, NN SLA is bad and 95% execution time is >= 25ms. While in may testing it is good as CAM GBT(1000 trees), which is 3ms in Horton eval jobs.

Such issue is better to be split for detailed development.

Done in develop branch


Add option to show 0 predicted hit

It would be nice if there is a way to add a 0 hitsplat drop.
I tried to add it myself but it looks like the hitsplats are added on xp gain so I don't know how you would check for a 0 hitsplat.

Yea that is precisely the problem. There is no way to know so it is not possible to add currently.

No you don't hit every tick. If you did and you still need this feature then you might as well use visual metronome


Login from Connect Bank Account link makes it overlap LHN content.

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Login from link: https://staging.new.expensify.com/bank-account/new
Notice after logging in, the LHN content is overlapped by Connect Bank Account screen.

Expected Result:
Connect Bank Account should be fully visible
Actual Result:
LHN content is overlapped by Connect Bank Account screen.
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android / native
[ ] Android / Chrome
[ ] iOS / native
[x] iOS / Safari
[ ] MacOS / Chrome / Safari
[ ] MacOS / Desktop

Version Number: 1.3.7-2
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://user-images.githubusercontent.com/43996225/234969738-0a9971b8-fec7-478d-b098-be3b32e579f9.MP4
https://user-images.githubusercontent.com/43996225/234969792-15d74532-73cc-4801-9408-eebd2e5f1660.MP4
Expensify/Expensify Issue URL:
Issue reported by: @hungvu193
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1682584165878629
View all open jobs on GitHub

Triggered auto assignment to @laurenreidexpensify (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

Bug0 Triage Checklist (Main S/O)

[ ] This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
[ ] This bug is not a duplicate report (check E/App issues and #expensify-bugs)

If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead

[ ] This bug is reproducible using the reproduction steps in the OP. S/O

If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
If the reproduction steps aren't clear and you determine the correct steps, please update the OP.

[ ] This issue is filled out as thoroughly and clearly as possible

Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.

[ ] I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync

Note to self: I need to repro this later

I just tested this on iOS Safari on a device and cannot reproduce. Am closing.


cardinal components crast at the start

Mod Name
Cardinal Components
Mod Homepage
https://www.curseforge.com/minecraft/mc-mods/cardinal-components
Describe the bug
crash at start
Steps to reproduce

have ffapi, connector, cardinal components
start
see

Logs
https://pastebin.com/VTddsJWL
Additional context
No response

Fixed in c4e4c1721695e2bbb3d8757b87e85c052be4a3ba


Update get-started.md

Added WSUS to the reference link

Docs Build status updates of commit 8330c73:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docset/docs-conceptual/windows/get-started.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


propagate updates

State of the world.
(1) people don’t know that they need to propagate their projects
(2) people don’t know how to propagate projects
So, we need to do the following:
(1) put a warning in neurodataviz so people know their data isn’t propogated
(a) point them to the documentation about propagation (@alexbaden)
(b) tell them to use UI to propagate project (@alexbaden)
(c) document propagate (@kunallillaney)
(2) get UI button that calls propagate service to work (@randburns)
The UI gives status as to the propagation state 0, 1, running
Eventually we need:
(3) progress bar (estimated based on the current z-index being processed @alexbaden)
(4) propagation to be restartable. (what’s up here @kunallillaney)
@randalburns @alexbaden @kunallillaney

@jovo - By UI you mean some version of the web console?  Last we talked about this, there were some data security questions we punted on and also some new documentation needed to make it clear when a user should/should not propagate.  Running through the webconsole instead of an exposed restful interface will help.
It would be cool if we supported bidirectional on-the-fly propagation, even if it's potentially very slow. For computer vision applications (e.g., cell detection, synapses, ...we often will write an intermediate output that would be cool to visualize, but may have additional data to write and so don't propagate.  If this isn't clear, maybe talk about on Monday?

@jovo - By UI you mean some version of the web console?  Last we talked about this, there were some data security questions we punted on and also some new documentation needed to make it clear when a user should/should not propagate.  Running through the webconsole instead of an exposed restful interface will help.
It would be cool if we supported bidirectional on-the-fly propagation, even if it's potentially very slow. For computer vision applications (e.g., cell detection, synapses, ...we often will write an intermediate output that would be cool to visualize, but may have additional data to write and so don't propagate.  If this isn't clear, maybe talk about on Monday?

@willgray i copied and pasted randal's comment here.

@willgray i copied and pasted randal's comment here.

@willgray - I believe OCP already does dynamic up sampling / downsampling
for annotation channels that are NOT propagated.
On Fri, Jan 1, 2016 at 15:09 joshua vogelstein<EMAIL_ADDRESS>wrote:

@willgray https://github.com/willgray i copied and pasted randal's
comment here.
—
Reply to this email directly or view it on GitHub
https://github.com/openconnectome/open-connectome/issues/187#issuecomment-168348858
.

@willgray - I believe OCP already does dynamic up sampling / downsampling
for annotation channels that are NOT propagated.
On Fri, Jan 1, 2016 at 15:09 joshua vogelstein<EMAIL_ADDRESS>wrote:

@willgray https://github.com/willgray i copied and pasted randal's
comment here.
—
Reply to this email directly or view it on GitHub
https://github.com/openconnectome/open-connectome/issues/187#issuecomment-168348858
.

@jovo @randalburns @alexbaden Documentation for propagate exists here http://docs.neurodata.io/open-connectome/api/propagate_api.html.
Propagation is also restartable. The way it restarts is to wipe out everything apart from the base resolution and start over again. Caveat: Very rarely propagation breaks down in the under propagation state, say the celery process crashed because the database became unreachable, at this stage we require manual intervention to restart it.
@willgray We did talk about this. With the new branch you cannot propagate a project if it is marked readonly(this is true from the REST'ful interface and should be done so from the GUI as well to avoid confusion). To make a project solid you propagate it and mark it readonly. The only way you can mark a project "not readonly" is from the Console. This ensure that you own the project before you can mark it "not readonly" and only then can you call propagate on it. Let me know if this is unclear and we can discuss it more.

Propagate status check added to the latest ndv beta: http://brainviz1.cs.jhu.edu/ndv/kharris15apical/em,annos/


ASYNC: Fixes for nested job creation

In such a scenario, calling ASYNC_start_job() in a job again to create
a new job will cause the program to crash. This scenario is common in
coroutines, such as a web server, a coroutine listener, and a new client,
a new coroutine service, after accept() is created.
The current design of ASYNC does not support this scenario. Each coroutine
eventually falls back to the dispatcher. There are multiple coroutines,
and there is only one context for saving the coroutine exit, which is the
dispatcher. At this time, the context will be Being covered, this also
determines that only one coroutine can be running at the same time. And it
is dispatched by the dispatcher, which limits the application scenario
of ASYNC to a certain extent. In the traditional sense of coroutines,
dispatching is done by the users themselves, and there is no need for a
so-called dispatching center, dispatcher.
This patch solves this problem. For each coroutine, a context called back
is used for exit or ASYNC_job_pause(), so the dispatcher is not needed.
This patch does not change the ASYNC API.
Signed-off-by: Tianjia Zhang<EMAIL_ADDRESS>

The origin PR is: https://github.com/openssl/openssl/pull/11421

Tengine 的 ssl_async 功能使用了ASYN，这个改动有否在Tengine中进行过验证？
参见： http://tengine.taobao.org/document/ngx_http_ssl_asynchronous_mode.html

Tengine 的 ssl_async 功能使用了ASYNC，这个改动有否在Tengine中进行过验证？
参见： http://tengine.taobao.org/document/ngx_http_ssl_asynchronous_mode.html

@uudiin ，有么？

Tengine 的 ssl_async 功能使用了ASYNC，这个改动有否在Tengine中进行过验证？
参见： http://tengine.taobao.org/document/ngx_http_ssl_asynchronous_mode.html

@uudiin ，有么？

@zhsnew 没有测试过Tengine，确实不知道Tengine用到了这个特性

@uudiin
1、async.c，下面这个代码有问题，会导致  currjob 自引用：
        if (ctx->currjob->status == ASYNC_JOB_PAUSED) {
            (*job)->prevjob = ctx->currjob;

2、因为 currjob 自引用，再加上下面最后一行代码，使程序进入错误状态，最终导致崩溃(基于Tengine已验证）：
        if (ctx->currjob->status == ASYNC_JOB_STOPPING) {
            *ret = ctx->currjob->ret;
            ctx->currjob->waitctx = NULL;
            async_release_job(ctx->currjob);
            ctx->currjob = ctx->currjob->prevjob;

3、修改方法如下，可以解决崩溃问题(已验证）
        if (ctx->currjob->status == ASYNC_JOB_PAUSED) {
            if (*job != ctx->currjob)
                (*job)->prevjob = ctx->currjob;

@zhsnew 非常感谢，我马上更新一下


Added OSX to travisci

See #6

Installing xtensor-io from conda and linking with the target xtensor-io in the CMake should fix the issues, thus this PR.


Add magic_html to benchmarks

Authors have stated that magic_html outperforms similar libraries including trafilatura. I'm not sure how relevant their benchmark is. It would be great if you included this library in your evaluation tables.

Hi @dantetemplar, thanks for the link, the package is interesting indeed.
They evaluate the packages on 200-300 webpages and forums in Chinese, this is a pretty specific use case and things would look different on a larger, more international benchmark, but it would be good to add magic_html all the same.

I had to tweak the evaluation script in the magic_html repository because it doesn't work as is. In the end magic_html is not better than other alternatives, the PR above will be merged soon.


Fix #479: Raise IndexError during Register.getitem

Update Register.__getitem__ to conform to the Python convention and
raise a subclass of IndexError for identifying the end of the sequence
when using it in a for loop. The exception raised is also a subclass
of QISKitError, for consistency with our current exception policy.
Fixes #479 (and hopefully sets a very small next stone for expanding our usage of exceptions).
@chriseclectic thanks for spotting this! Can you provide an example where that iteration over a Register is used? While looking at it, it seems a bit odd that it returns (self, int) tuples and I'm wondering if we could make it more usable - I basically went for the least intrusive modification in order to fix the bug, but would like to explore cleaner options (such as making it a fully fledged iterable if it makes sense).

Description

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[ ] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

while on the topic of registers it might be good to add a friendlier print name for them. For example in QuantumRegister something like:

Sounds good - just added it at f662d2a, as indeed in this case we can come up with an "information-rich and unambiguous" string that can be used for recreating the Registers, nice addition!

I agree it would be nice to make registers proper iterables and have a better way of referencing qubits than a tuple, but I think a lot of the code base uses the tuple representation so it might take a little bit of work.

Fair enough - maybe we can look at it in the future if needed!


feat: lib1 as general kotlin project, with Android example project

Closes #2 (again)
Now, we have a kotlin library, which is included in an example Android project.
Please try it out to see if it works out of the box :)

@a-miscellaneous Maybe, you could take a look at this, too? :)


add public & private prop tests.

This is the code that checks that the resolver does not output a public & private conflict. We still do not have the gen of public dependencies do to https://github.com/rust-lang/cargo/pull/6653/commits/9b8b12c1f85082e623a4dc8c7b248d7b757efcde, because backtracking is to inefficient, but this checks that we are getting a correct answer.
This was supposed to be in #6653, but was lost in the edits of history.
Reconstructed from https://github.com/Eh2406/cargo/commit/5522aba5e8875d9c9e14eb66b5469ad481cba7a1

r? @ehuss
(rust_highfive has picked a reviewer for you, use r? to override)

@bors: r+

:pushpin: Commit a02f6a12f8b178c88723eff815f52e8cd53f4399 has been approved by alexcrichton

:hourglass: Testing commit a02f6a12f8b178c88723eff815f52e8cd53f4399 with merge d1b55add24beacb7bb7184eb6bdcdb572c72e904...

:sunny: Test successful - checks-travis, status-appveyor
Approved by: alexcrichton
Pushing d1b55add24beacb7bb7184eb6bdcdb572c72e904 to master...


make_standalone_toolchain.py script is no longer needed for interfacing with arbitrary build systems.

As of NDK r19, the toolchains installed by default with the NDK may be used in-place. The make_standalone_toolchain.py script is no longer needed for interfacing with arbitrary build systems.

https://developer.android.com/ndk/guides/other_build_systems

Thanks, android-example doesn't use/require make_standalone_toolchain.py anymore and documentation describes usage of clang based toolchain:
https://dushistov.github.io/rust_swig/java-android-example.html


Fix #665 - make all plugins apply to matching files instead of just the first matching plugin

That's a breaking change, I don't think we can do that.

The existing behavior is relatively unexpected (and limiting), so it would be nice to eventually change it.
Are there any other planned breaking changes that this could be grouped with for a later version?

Yes with FuseBox 3 we will redesign the entire API these change could come, however I need to investigate it. This PR might break some people's builds, let's keep it open for now

See new pull request #677


YJDH-618 | Remove duplicated getLastCookieValue imports from main branch

Description :sparkles:
Remove duplicated getLastCookieValue imports from main branch
Issues :bug:
Testing :alembic:
Screenshots :camera_flash:
Additional notes :spiral_notepad:

Codecov Report

Merging #1273 (8b860c6) into main (60982b8) will decrease coverage by 0.23%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main    #1273      +/-   ##
==========================================
- Coverage   64.14%   63.90%   -0.24%
==========================================
  Files         758       80     -678
  Lines       20544     1366   -19178
  Branches     2316      225    -2091
==========================================
- Hits        13177      873   -12304
+ Misses       7024      434    -6590
+ Partials      343       59     -284

Impacted Files
Coverage Δ

frontend/benefit/applicant/jest.config.js

...enefit/applicant/src/context/DeMinimisProvider.tsx

backend/shared/shared/audit_log/viewsets.py

.../tet/shared/src/components/container/Container.tsx

backend/benefit/calculator/tests/conftest.py

...youth/src/__tests__/utils/backend/backend-nocks.ts

frontend/benefit/handler/src/utils/common.ts

...on/steps/step2/accordions/EmploymentAccordions.tsx

frontend/tet/youth/src/pages/postings/show.tsx

...benefit/applicant/src/components/header/Header.tsx

... and 668 more

Continue to review full report at Codecov.

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


ns-3: 3.35 -> 3.37

Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

So this is a work in progress for packaging ns-3 3.37, which changed of build system from waf to a cmake based one, but with an helper python script for the cmake configuration. I will probably need some help regarding this packaging.

This doesn't seem to build the actualy ns3 binary, but just seems to build

ls /nix/store/...-ns-3-35/bin]

ns3.35-bench-packets-debug    ns3.35-print-introspected-doxygen-debug  ns3.35-tap-creator-debug
ns3.35-bench-simulator-debug  ns3.35-raw-sock-creator-debug            ns3.35-tap-device-creator-debug

Ns-3 is a library to do network simulation, not a binary. Arguably, the most important thing is stuff in /lib/, not even stuff in /bin/ (but it's still important to check whether the simulator works as expected).

Must of got confused with this,  https://www.nsnam.org/docs/release/3.37/tutorial/html/quick-start.html#brief-summary
which mentioned ./ns3
But i think this package is something different.

sry this got forgotten ('cos of draft status maybe). Closing in favor of more uptodate https://github.com/NixOS/nixpkgs/pull/242131/


exp/services/recoverysigner: add support for any type of JWT keys

What
Add support for any type of JWT keys, such as ECDSA, RSA, etc.
Why
The recoverysigner currently assumes that a JWT key is a ECDSA key, but not everyone who might wish to run this will be using an ECDSA key. The key in use will be defined by the SEP-10 server that they're using the recoverysigner with. If the SEP-10 server is using an RSA key the recoverysigner will be incompatible.

The config option for the JWT public key is currently an ASN.1 DER and base64 encode public key which was easy to code using built-in Go stdlib functions, but doesn't make it easy to specify different types of keys since that data isn't stored in the encoded bytes.
It could be changed to be a JSON Web Key (JWK) value, per RFC7517 which defines a JSON object that can be used to define any JWT key.
Supporting a JSON Web Key Set, also included in the RFC, would support a group of keys being valid which would help smooth over key rotation/migration.


Try run coverage tests early

matrix include adds jobs to the end of the jobs list, and doing that for the coverage run means the longest run starts last.. This PR starts it earlier by having PHPUNIT=true and PHPUNIT=true COVERAGE=true in the default matrix, but exclude one depending on what we want to do with that version.


Update free-programming-books.md

Added category for embedded programming with three starting resources.
One for learning how to program on the STM32 Discovery board(a very popular choice for embedded programming using C)
One that explains the basics of a microcontroller with reference to the Atmel 8-bit board and STMicroelectronics' 32-bit board
And the third gives the theoretical introduction to control and embedded systems

I think "Embedded Systems" is a better category name.

Done!


disable incremental build

Title
disable incremental build
Summary
Disable incremental build to workaround an incremental build bug.
Suggested Reviewers
@mairaw @wh-alice

no longer needed.


Use hardware acceleration on the container

Allow the usage of hardware acceleration for complex tests and simulation

Could you provide any reference for what you call "graphic boards"?

Could you provide any reference for what you call "graphic boards"?

"Graphic board" is not the correct naming, my mistake, is graphic cards, like nvidia.

@ivan1993br, are you working on this? I think we need this to run rviz2

Actually, I was not, did you fix it?


[Proposal]:  Deprecate on_startup and on_shutdown in favor of lifespan

Issue guidelines

[X] I've read the Issue Guidelines and wholeheartedly agree.

Issue Checklist

[X] I have searched open or closed issues and found nothing related to my idea.
[X] I have read the Documentation and it doesn't mention anything about my idea.
[X] To my best knowledge, my idea wouldn't break something for other users.

Describe your Idea
Currently, Starlette supports on_startup and on_shutdown hooks for running startup and shutdown tasks. However, these hooks have certain limitations and are not as robust as the lifespan approach, which uses async context managers.
Use Cases
The lifespan approach provides a more structured and reliable way to handle startup and shutdown tasks, and it is recommended by the ASGI specification (https://asgi.readthedocs.io/en/latest/specs/lifespan.html). This proposal aligns with the ASGI specification and promotes best practices for handling startup and shutdown tasks in Starlette applications in our APIs such as WebGear and WebGear_RTC which uses it.
Any other Relevant Information?
Related Issues:

https://github.com/encode/starlette/discussions/2067
https://github.com/encode/starlette/pull/2065

Successfully fixed in commit https://github.com/abhiTronix/vidgear/commit/20dec0accda1ca9a850d91bcec194184176f1b70


proposal: testing: support automatic multiple package coverage

Currently it's very hard to support coverage for the tested package and all the dependencies of that package.
In order to do this today, one would need to do something like this:
go test -coverpkg `go list -f {{.Deps}} | sed 's/\[//g' | sed 's/]//g' | sed 's/ /,/g'`,tested/package/name tested/package/name

The problem is that this would also list the standard library dependencies, which is not really useful and it's hard to write as well (see the fact that one needs to append the name of the tested package to actually get the coverage for it). The above command also doesn't work on Windows.
The other option would be to use:
go test -coverpkg PACKAGE_DIR/... tested/package/name

This however will not show dependencies from GOPATH.
As such, I'm proposing adding a magical keyword named deps (like all) to solve this problem. The way it should work would be:
go test -coverpkg deps tested/package/name

This comes up pretty often, see: https://youtrack.jetbrains.com/issue/GO-1541 for the number of voters / watchers or duplicate issues. It is true that the IDE could generate the list of packages but the users that do not use such a tool wouldn't be able to benefit from it.
Please note this is different from #6909.

I made a tool for that and #6909: https://github.com/AlekSi/gocovermerge.

I reopened #10271 because we are in a position to make -coverpkg=all mean "all dependencies".
Closing this issue since it is now a duplicate of #10271.


Key binds screen has things configured wrong

happened on the build from commit 6cc0d16117f523f6948519045a4c79bc15bcf5fa , Windows x64

What I pressed was function 1 through 4 = A S D F, but this thing put every one of those keys one off, and there is a "skip" thing with no string

fixed


feat: add autocomplete for project name arguments, fixes #4880

The Issue
Lots of the go commands take a project name as an argument, but don't provide autocompletion for those arguments.
How This PR Solves The Issue
Adds autocompletion for commands that take a project name as an argument.

If only one argument is allowed, it doesn't give completion for more.
If multiple arguments are allowed, it gives completion for all of them.
For start and stop specifically, if only gives names of the relevant (inactive and active respectively) projects - for all other commands, all names are given.

NOTE This makes the --select flag for ddev start and ddev stop redundant. I've marked the flag as hidden and deprecated for both of those commands - it can be removed in some future release.
I've also removed the docs about that flag - but if you want me to add it back with a note that they're deprecated, I can happily do that.
Manual Testing Instructions
Type ddev start <tab> and see the autocompletion results.

Try this with any command that takes a project name as an argument
Check that commands that only accept one argument only perform completion for one argument
Check that commands that accept multiple arguments perform completion for as many arguments as you like
Check that ddev start only gives completion for currently inactive projects
Check that ddev stop only gives completion for currently active projects
Check that a project name isn't repeated if it's already included as an argument

Automated Testing Overview

I've added tests that work based on the TestSites array - though since these tests won't run with less than 2 test sites, the tests are skipped if there's not enough tests.
Related Issue Link(s)

https://github.com/ddev/ddev/issues/4880

Release/Deployment Notes

This is fully backwards compatible and shouldn't affect anything else.

Whitespace changes and imports moving around were done automatically by my IDE

I've marked the --select flag for ddev start and ddev stop as hidden and deprecated.
I've also made a start on tests (which will currently fail) - I need to see if there's a tidy way to either:

a) only create a few specific sites so I can rely on specific site names
b) write the tests in a way that generically uses names of whatever test sites happen to be spun up

I ran out of time to do that tonight. Any pointers would be welcome.
Marking as draft for now until I get them sorted.

a) only create a few specific sites so I can rely on specific site names

My opinion: the only requirement is that the number of sites should be sufficient to test all possible cases.

I've added tests now. They work using the existing TestSites array because I ran into weird problems when I tried to define my own. The only caveat there is that the tests will be skipped if there's less than 2 tests in the array (which if I'm not mistaken will only happen if someone is testing locally and uses the GOTEST_SHORT env variable).
I also removed the docs about the deprecated/hidden --select flag but if you want to keep that doc around I can bring it back with a note about it being deprecated. Makes more sense to me to just not mention it in the docs though.
I've also updated the PR description.

You are completely amazing @GuySartorelli . I won't have time to adequately grok this for at least a few days, but so appreciative! This will be a much-loved feature.

Rebased, reviewing.
@GuySartorelli please see if you can convince your IDE to use standard gofmt formatting, which is what's generally required. As you point out, it makes a mess and is hard to review when things get changed that aren't relevant to the PR. Happy to chat with you about this, I know the timezones are hard. But it would be cool if you could experiment a bit to see if you can calm it down a bit. What IDE are you using? How do you have it set up? We can discuss in another issue if that's the easiest.
Thanks so much for your incredible contributions. You know we're looking forward to more. I'm going to learn a lot from you.

please see if you can convince your IDE to use standard gofmt formatting, which is what's generally required.

If you can point me to something that explains what that specifically means, I'll be happy to

Github discussion is great. Some vscode plugins use rather exotic and opinionated golang setup, whereas we're trying mostly to just use what gofmt says to do, so gofmt -w -s is what's expected everywhere. Your IDE should be able to do that. That said, I didn't really see all that much to worry about in this PR.

This is working wonderfully for me in testing just now.


Fix infinite spinner on OldDot transition

Details
This PR fixes two related race conditions:
LoginWithShortLivedTokenPage race condition explanation

Page loads, beta/session props are not present yet.
Calls Session.signInWithShortLivedToken
Before call to API.createLogin or betas load, LogInWithShortLivedTokenPage immediately runs this.setState({hasRun: true});
In componentDidUpdate, this.state.hasRun is true, and then we are stuck in LogInWithShortLivedTokenPage / infinite spinner forever.

LoginWithShortLivedTokenPage race condition fix
Get rid of hasRun state just navigate to exitTo once betas are loaded and we are logged into the correct account.
AuthScreens race condition explanation

We send an API request to create the policy
We send API requests to fetch existing policies.
First API request returns and policy is added to Onyx.
Second API request(s) return, but at the time when the API was collecting the list of policies to send in the response, the new policy hadn't been created yet. So it's missing from this response and we remove it from Onyx.

AuthScreens race condition fix
Don't load policies until after we've finished with the transition and workspace/new pages. That way, the new workspace won't be overwritten.
Fixed Issues
$ https://github.com/Expensify/App/issues/5518
Tests

Add a setTimeout of 1000 around these lines. This consistently reproduced the AuthScreens race condition before these changes.
Make sure Web-E is up-to-date, run grunt, and then run ngrok
In a mobile browser, visit your ngrok url. This should open OldDot on dev.
Sign in with a new account.
Click Set up my company for free.
Verify that you are taken into NewDot, a new workspace is created, and you are shown the workspace settings page. You should not get stuck on an infinite spinner.

QA Steps

In a mobile browser, visit https://staging.expensify.com/
Sign in with a new account under a domain in the freeCard beta, such as chivito.pw
Click on Set up my company for free
Verify that:

You are taken into New Expensify
A new workspace is created
You are shown the workspace settings page
You do not get stuck on an infinite spinner.

Repeat steps 1-4 20 times to verify that the race condition is eradicated (sorry 😓)

Tested On

[ ] Web
[x] Mobile Web
[ ] Desktop
[ ] iOS
[ ] Android

Screenshots

Web

Mobile Web
https://user-images.githubusercontent.com/47436092/135006383-fd228198-4b59-49d0-b1de-4269dba090d9.mov
Desktop

iOS

Android

Just double-checking @roryabraham so that I'm not holding anything up, is this PR ready to be reviewed again or are we waiting for https://github.com/Expensify/App/pull/5614/files to get merged?

Sorry for the lackluster communication here @nickmurray47 – discussion is ongoing in the linked issue

Closing this out in preference of https://github.com/Expensify/App/pull/5706


Updates list of exposed metrics

Closes #1458
Not entirely sure if this is correct.

Thanks a lot for your contribution! :medal_sports:
It is a great start but I think it would be even better if we would make it a table in the following format:
| metric                                | description                             |
|---------------------------------------|-----------------------------------------|
| `flux_cache_request_duration_seconds` | Duration of cache requests, in seconds. |

This way a user not only has a description of what is exposed but also knows how it is exposed.


No summary of hints/errors/warnings in "problems view"

I'd love to see a summary of how many hints/errors/warnings I have. Right now, it's a flat list and can scroll out of view. I don't know if I have any errors or warnings, because all I see is a list of hints.

I'd love to see something like: 24 hints, 2 warnings, 0 errors. This way, I don't get stressed from the list of hints that I see.

Somehow I have hidden my problem view and can't get it back. How can I show it again? Or is this a bug?

The settings to hide and show it are in the linter plugin. You can see them in the Settings page, in the packages section.

Closing this as I think it's largely a dup of #112.


#15 adding set days function

Fix: #15

Really appreciate your work and quick response, Thanks @guyluz11. I will review this today itself.


Add Client Certificates tutorial.

Updated!

Ok, only one failure left, which I don't care about, since it is in the server section, which needs to be rewritten. Merging.


feat: add model api type interfaces

For the declaration of the Model interface. Would it make sense to somehow make use of the existing JSON schema?

I tried to use this package to generate types based on the JSON schema, and the result does seem more complete. However, it reveals certain keys that require the any type so linting for those had to be disabled.

Very nice! I think most places that are now annotated with any can safely be set to string | object. Or whatever the syntax is there.


fix(besu): deployContractSolBytecodeNoKeychainV1 requires keychainId

In the DeployContractSolidityBytecodeNoKeychainV1Request of
packages/cactus-plugin-ledger-connector-besu/src/main/json/openapi.tpl.json
there are parameters that are required despite the entire point of this
operation is to not need them (e.g. keychainId and contract JSON object).
Fixes #3586
Signed-off-by: Peter Somogyvari<EMAIL_ADDRESS>Pull Request Requirements

[x] Rebased onto upstream/main branch and squashed into single commit to help maintainers review it more efficient and to avoid spaghetti git commit graphs that obfuscate which commit did exactly what change, when and, why.
[x] Have git sign off at the end of commit message to avoid being marked red. You can add -s flag when using git commit command. You may refer to this link for more information.
[x] Follow the Commit Linting specification. You may refer to this link for more information.

Character Limit

[x] Pull Request Title and Commit Subject must not exceed 72 characters (including spaces and special characters).
[x] Commit Message per line must not exceed 80 characters (including spaces and special characters).

A Must Read for Beginners
For rebasing and squashing, here's a must read guide for beginners.

I investigated why the DAST scan is failing but could not reproduce the problem locally. I'm going to assume that it's an issue with the environment setup logic of the CI job and not an issue with the endpoints. Based on that I'll disable the DAST scan for now until we can figure out what's wrong with it.


Inconsistency in when questions actions appear

Description
The "Move up" "Move down" "Duplicate" "Delete" "More" menu appears on some but not all questions
Steps to reproduce

Go to GC Forms
Add a bunch of different form elements including dynamic fields
Scroll down and see how some elements "not selected" have the menu appear
See inconsistencies across different blocks

Details

Browser: Edge
Operating system: Windows
Environment: Staging
Language: French
Viewport: Tablet

Expected behaviour
Consistent behaviour across questions, menu appearing when question is in focus?
Screenshots or videos

Pre-known issue that will be addressed when we remove the menu here (#3729)


Validate gives error on valid syntax

@synesthesiam Showed a better way to handle set of min/max brightness in https://github.com/home-assistant/intents/pull/487#discussion_r1071547128. The essence of the problem is that the syntax, as below, uses a colon.
 "set <name> brightness to [the] {brightness_min_max:brightness}"
This works as intended when testing directly with intentfest but the validation catches the colon from the syntax and does not allow the sentence.
I guess the reg-exp here needs to be updated. Probably let it allow the specific sequence of "{" ? ":" ? "}", would be good to not allow punctuations everywhere. But i do not speak regexp and does not know how to go any further.  https://github.com/home-assistant/intents/blob/8dcb1775910d1351308ca63dd8c53ce24852450b/script/intentfest/validate.py#L114-L117.

Fixed in https://github.com/home-assistant/intents/pull/673


Not able to initialize MultiNode config DB when dockvols directory is not present

Not able to initialize MultiNode config DB when dockvols directory is not present
vDVS driver version
[root@sc-rdops-vm17-dhcp-15-182:~] esxcli storage guestvol status
=== Service:
Version: 0.17.c2aef31-0.0.1
Status: Running
Pid: 97781
Port: 1019
LogConfigFile: /etc/vmware/vmdkops/log_config.json
LogFile: /var/log/vmware/vmdk_ops.log
LogLevel: INFO
=== Authorization Config DB:
DB_LocalPath: N/A
DB_Mode: NotConfigured (no local DB, no symlink to shared DB)
DB_SharedLocation: N/A

steps to reproduce:

Make sure you have clean environment (fresh setup is recommended OR remove dockvol/authdb etc)
install vDVS driver (VIB)
invoke esxcli storage guestvol status to make sure vmdkops service is running fine
invoke esxcli storage guestvol config init --datastore=<sharedDS_name>

Observe the following error cause.
Expected behavior: MultiNode config db should be created without any problem.
root@sc-rdops-vm17-dhcp-15-182:~] esxcli storage guestvol config init --datastore="sharedVmfs-0"
Got no data from process: LANG=en_US.UTF-8 /usr/lib/vmware/vmdkops/bin/vmdkops_admin.py --output-format=xml config init  --datastore='sharedVmfs-0'

[root@sc-rdops-vm17-dhcp-15-182:~] /usr/lib/vmware/vmdkops/bin/vmdkops_admin.py --output-format=xml config init  --datastore='sharedVmfs-0'
Traceback (most recent call last):
  File "/usr/lib/vmware/vmdkops/Python/auth_data.py", line 640, in __connect
    self.conn = sqlite3.connect(self.db_path)
sqlite3.OperationalError: unable to open database file

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/lib/vmware/vmdkops/bin/vmdkops_admin.py", line 1478, in <module>
    main()
  File "/usr/lib/vmware/vmdkops/bin/vmdkops_admin.py", line 72, in main
    if args.func(args) != None:
  File "/usr/lib/vmware/vmdkops/bin/vmdkops_admin.py", line 1325, in config_init
    err = auth.new_db()
  File "/usr/lib/vmware/vmdkops/Python/auth_data.py", line 761, in new_db
    self.__connect()
  File "/usr/lib/vmware/vmdkops/Python/auth_data.py", line 643, in __connect
    raise DbConnectionError(self.db_path)
auth_data.DbConnectionError: DB connection error at /vmfs/volumes/sharedVmfs-0/dockvols/vmdkops_config.db

This is related with Cross ESX multi tenancy so not adding mustfix keyword.
Workaround is to create dockvols directory at /vmfs/volumes/<sharedDS_Name>/ helps to avoid reported issue.
@tusharnt @govint : what do you think? If you think we should address by kubecon release then mustfix kw should be added.

No, this needs to be addressed post the upcoming release and possibly rethink the use of a DB itself.


reSnap: init at 2.5.2

Description of changes

Things done

Built on platform(s)

[X] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/4426

Cool, I've made all the changes, but I rebased the wrong things and am fixing a git issue now. This should be ready to merge soon

I think it's all fixed and ready! Thanks again for all the great feedback!

Hey @SuperSandro2000, good call about wrapping with mkDerivation, I've made the change. If I'm reading right you want to remove explicit phases -- why is this? And how does the current state look? Thanks!

@SuperSandro2000 not to be annoying, but have you had a chance to look this over again?

Hey @404Wolf, I think you're doing great so far, but I believe the package can still be improved further:

We don't need two mkDerivation since we can put everything in one
We don't need writeShellApplication anymore as we can just copy the script to the output
Use finalAttrs instead of rec (see https://github.com/NixOS/nixpkgs/issues/315337).
Whenever we override a phase like installPhase, we should always add the pre- and post- hooks.
Contrary to my first suggestion, it's discouraged to set phases according to the stdenv docs since it's easy to forget those that run important things.

As such, here is what I think the derivation should look like:
package.nix
{
  lib,
  stdenvNoCC,
  fetchFromGitHub,
  ffmpeg,
  feh,
  imagemagick_light,
  lz4,
}:
stdenvNoCC.mkDerivation (finalAttrs: {
  pname = "resnap";
  version = "2.5.2";

  src = fetchFromGitHub {
    owner = "cloudsftp";
    repo = "reSnap";
    rev = "v${finalAttrs.version}";
    hash = "sha256-thVyf1gTDPLQVtZKoWL7SGiWI++ICWqmF/Ar57I3WP8=";
  };

  buildInputs = [
    ffmpeg
    feh
    imagemagick_light
    lz4
  ];

  installPhase = ''
    runHook preInstall

    install -D ./reSnap.sh $out/bin/reSnap

    runHook postInstall
  '';

  postFixup = ''
    substituteInPlace $out/bin/reSnap \
      --replace-fail "\$0" "reSnap"
  '';

  meta = {
    description = "Take screnshots of your reMarkable tablet over SSH";
    homepage = "https://github.com/cloudsftp/reSnap";
    license = with lib.licenses; [ mit ];
    maintainers = with lib.maintainers; [ _404wolf ];
    mainProgram = "reSnap";
  };
})

Let me know what you think and if you have any questions regarding this, don't hesitate to ask.

Hey @404Wolf, I think you're doing great so far, but I believe the package can still be improved further:
* We don't need two `mkDerivation` since we can put everything in one

* We don't need `writeShellApplication` anymore as we can just copy the script to the output

* Use `finalAttrs` instead of `rec` (see [Documentation: guide for using `let in` vs `rec` vs `finalAttrs` #315337](https://github.com/NixOS/nixpkgs/issues/315337)).

* Whenever we override a phase like `installPhase`, we should always add the `pre-` and `post-` hooks.

* Contrary to my first suggestion, it's discouraged to set `phases` according to the [stdenv docs](https://github.com/NixOS/nixpkgs/blob/420d0cc6f27b2b7f117be67aa721dd7154ffb003/doc/stdenv/stdenv.chapter.md#phases-var-stdenv-phases) since it's easy to forget those that run important things.

As such, here is what I think the derivation should look like:
package.nix
Let me know what you think and if you have any questions regarding this, don't hesitate to ask.

Thanks, I've changed it to be that, that makes a ton of sense. I didn't realize that buildInputs also propagate to runtime.

Hey @404Wolf, I think you're doing great so far, but I believe the package can still be improved further:
* We don't need two `mkDerivation` since we can put everything in one

* We don't need `writeShellApplication` anymore as we can just copy the script to the output

* Use `finalAttrs` instead of `rec` (see [Documentation: guide for using `let in` vs `rec` vs `finalAttrs` #315337](https://github.com/NixOS/nixpkgs/issues/315337)).

* Whenever we override a phase like `installPhase`, we should always add the `pre-` and `post-` hooks.

* Contrary to my first suggestion, it's discouraged to set `phases` according to the [stdenv docs](https://github.com/NixOS/nixpkgs/blob/420d0cc6f27b2b7f117be67aa721dd7154ffb003/doc/stdenv/stdenv.chapter.md#phases-var-stdenv-phases) since it's easy to forget those that run important things.

As such, here is what I think the derivation should look like:
package.nix
Let me know what you think and if you have any questions regarding this, don't hesitate to ask.

I could be wrong, but I don't think that buildInputs are available at runtime; it didn't seem to work. I cleaned it up a bit by only using one mkDerivation though, and just manually append to the PATH instead of writeShellApplication, and by reusing the name. Let me know what you think. Thanks for looking it over :)

I believe runtimeInputs will work in this case, but if that doesn't, we can wrap the executable with the PATH:
  nativeBuildInputs = [ makeWrapper ];

  runtimeInputs = [
    ffmpeg
    feh
    imagemagick_light
    lz4
  ];

  postFixup = ''
    substituteInPlace $out/bin/reSnap \
      --replace-fail "\$0" "reSnap"

    wrapProgram $out/bin/reSnap \
      --set PATH "${lib.makeBinPath finalAttrs.runtimeInputs}"
  '';

Hey @SuperSandro2000, any chance you could look this over at some point? I think it's ready to merge. Thanks!

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/4607


Fix Identity Azure CLI Cred process exectuion

Fixes #9058

Please add a timeout to waiting on the process exit.

added 10 seconds timeout


Deprecation Notice: Python 3.8 Wheel Support to End in future releases

Python 3.8 has reached its end-of-life as outlined in the Status of Python version. Starting with FlashInfer v0.2.3 (in the future), we will no longer provide official wheel support for Python 3.8. Users are encouraged to upgrade to a newer Python version to continue receiving updates and support.

pytorch 2.5 already dropped python 3.8 support, so does vllm.
however, i still recommend to build the wheel with python 3.8+ abi , since that does not hurt anything. you only need to release one wheel for all the python versions, right?


[Stats] Add support for infinite range with delta stream positions

Addresses #3 to allow clients to conveniently fetch stats for unbounded intervals

LGTM, thanks for the supporting the unbounded delta stream positions!


[Bug]: Every time a full-text search is performed, the index must be recreated; otherwise, an empty result will be obtained

Is there an existing issue for the same bug?

[X] I have checked the existing issues.

Version or Commit ID
v0.3.0-dev6
Other environment information
操作系统：ubuntu 22

Actual behavior and How to reproduce it
The first time search.py is executed, it can search for content normally; executing it again will return an empty result.
import_from_mysql.py
`
import infinity
from db import get_db_connection2
connection = get_db_connection2()
cursor = connection.cursor()
infinity_instance = infinity.connect("/var/infinity")
db_instance = infinity_instance.get_database("default_db")
db_instance.drop_table("zl_team", infinity.common.ConflictType.Ignore)
table_instance = db_instance.create_table("zl_team", {
"id": {"type": "integer"},
"name": {"type": "varchar"},
"photo": {"type": "varchar"},
"position": {"type": "varchar"},
"location": {"type": "varchar"},
"phone": {"type": "varchar"},
"email": {"type": "varchar"},
"business_field": {"type": "varchar"},
"industry_field": {"type": "varchar"},
"introduction": {"type": "varchar"},
"key_achievements": {"type": "varchar"},
"honors": {"type": "varchar"},
"qualifications": {"type": "varchar"},
"education_background": {"type": "varchar"},
"work_experience": {"type": "varchar"},
"working_languages": {"type": "varchar"},
"social_positions": {"type": "varchar"},
"publications": {"type": "varchar"}
})
读取 zl_team 表中的数据
cursor.execute("SELECT * FROM zl_team")
rows = cursor.fetchall()
for row in rows:
json_data = {
"id": row[0] if row[0] is not None else "",
"name": row[1] if row[1] is not None else "",
"photo": row[2] if row[2] is not None else "",
"position": row[3] if row[3] is not None else "",
"location": row[4] if row[4] is not None else "",
"phone": row[5] if row[5] is not None else "",
"email": row[6] if row[6] is not None else "",
"business_field": row[7] if row[7] is not None else "",
"industry_field": row[8] if row[8] is not None else "",
"introduction": row[9] if row[9] is not None else "",
"key_achievements": row[10] if row[10] is not None else "",
"honors": row[11] if row[11] is not None else "",
"qualifications": row[12] if row[12] is not None else "",
"education_background": row[13] if row[13] is not None else "",
"work_experience": row[14] if row[14] is not None else "",
"working_languages": row[15] if row[15] is not None else "",
"social_positions": row[16] if row[16] is not None else "",
"publications": row[17] if row[17] is not None else ""
}
table_instance.insert([json_data])
# print("插入数据成功")
# print(json_data)
res = table_instance.create_index(
"introduction_index",
infinity.index.IndexInfo("introduction", infinity.index.IndexType.FullText, {"ANALYZER": "chinese"}))
infinity_instance.disconnect()
`
search.py
`import infinity
from db import get_db_connection2
connection = get_db_connection2()
cursor = connection.cursor()
infinity_instance = infinity.connect("/var/infinity")
db_instance = infinity_instance.get_database("default_db")
table_instance = db_instance.get_table("zl_team")
questions = [
r"送达与取证",
r"商法",
]
for question in questions:
qb_result = table_instance.output(["id", "name","location","introduction", "_score"]).match_text("introduction", question, 10).to_pl()
print(f"question: {question}")
print(qb_result)
res = table_instance.output(["id", "name", "introduction"]).to_pl()
print(res)
res = table_instance.show_index("introduction_index")
print(res)
infinity_instance.disconnect()`
Expected behavior
No response
Additional information
No response

Can you post your scripts as attachment?

Here are three Files
import_from_mysql2.py
Creating tables, importing data, creating indexes.
t2.py
Full-text search.
shell.txt
Execution process in the shell.
[
infinity.zip
](url)

I cannot reproduce this issue on Ubuntu 24.04. Here's my screenshot

Here's my procedure:

Install conda
Create Python 3.10 env and enter this env
pip install infinity-sdk==0.3.0-dev6
Create dir /var/infinity and ensure current user owns it
Checkout Chinese dictionary under /var/infinity/resources
Run modified import_from_mysql2.py once to create table, import data and create index.
Run modified t2.py multiple times to search and show result. Ensure it succeed each time.

Here's my modified scripts:
infinity.zip

In your screenshot
Pay attention to the red parts; the search results are different between the two searches.

I don't understand what you mean.
I found when I split the fulltext_search_zh.py file from the example directory into two files:
One for creating the table and index
Another for querying
I encountered the same issue where the second search returns no data.
infinity.zip

I think I've found the root cause. The infinity embedded sdk connect() shall ensure MemIndexRecover actually done.
The fix will be available with next beta release, 0.3.0-dev7

ok,thanks for your reply


[MM-14698] Add CSRF Header in File Upload and Profile Image Set Operations

Summary
This PR manually sets the X-CSRF-Token header for operations that do not rely on Client4 for non-get HTTP requests to avoid missing token warning.
Ticket Link
https://mattermost.atlassian.net/projects/MM/issues/MM-14698
Device Information
This PR was tested on: Android 9 Emulator

Spoke with @DSchalla offline, there is no need to add the header in the share extensions as the Share Extensions do not send the cookie with the request.


Changing font family doesn't invalidate AutoFittedText.metrics

Needs a small refactor, to make the canvas context font property dependent on font family.

This should be fixed by work done for #13


Single file inferencing issue

While running single file inferencing with the command inside docker:
python sfi.py --audio-file /workspace/w2v_inference/record.wav --ft-model /workspace/w2v_inference/hindi_large.pt --w2l-decoder kenlm --lexicon /workspace/w2v_inference/hindi/lexicon.lst --kenlm-model /workspace/w2v_inference/hindi/lm.binary
I get an error:
Traceback (most recent call last):
  File "sfi.py", line 260, in load_model_and_update
    mdl, cfg, task = fairseq.checkpoint_utils.load_model_ensemble_and_task([mdl_path])
  File "/home/fairseq/fairseq/checkpoint_utils.py", line 432, in load_model_ensemble_and_task
    task = tasks.setup_task(cfg.task)
  File "/home/fairseq/fairseq/tasks/__init__.py", line 39, in setup_task
    cfg = merge_with_parent(dc(), cfg)
  File "/home/fairseq/fairseq/dataclass/utils.py", line 490, in merge_with_parent
    merged_cfg = OmegaConf.merge(dc, cfg)
  File "/opt/conda/lib/python3.8/site-packages/omegaconf/omegaconf.py", line 321, in merge
    target.merge_with(*others[1:])
  File "/opt/conda/lib/python3.8/site-packages/omegaconf/basecontainer.py", line 331, in merge_with
    self._format_and_raise(key=None, value=None, cause=e)
  File "/opt/conda/lib/python3.8/site-packages/omegaconf/base.py", line 95, in _format_and_raise
    format_and_raise(
  File "/opt/conda/lib/python3.8/site-packages/omegaconf/_utils.py", line 629, in format_and_raise
    _raise(ex, cause)
  File "/opt/conda/lib/python3.8/site-packages/omegaconf/_utils.py", line 610, in _raise
    raise ex  # set end OC_CAUSE=1 for full backtrace
  File "/opt/conda/lib/python3.8/site-packages/omegaconf/basecontainer.py", line 329, in merge_with
    self._merge_with(*others)
  File "/opt/conda/lib/python3.8/site-packages/omegaconf/basecontainer.py", line 347, in _merge_with
    BaseContainer._map_merge(self, other)
  File "/opt/conda/lib/python3.8/site-packages/omegaconf/basecontainer.py", line 314, in _map_merge
    dest[key] = src._get_node(key)
  File "/opt/conda/lib/python3.8/site-packages/omegaconf/dictconfig.py", line 258, in __setitem__
    self._format_and_raise(
  File "/opt/conda/lib/python3.8/site-packages/omegaconf/base.py", line 95, in _format_and_raise
    format_and_raise(
  File "/opt/conda/lib/python3.8/site-packages/omegaconf/_utils.py", line 629, in format_and_raise
    _raise(ex, cause)
  File "/opt/conda/lib/python3.8/site-packages/omegaconf/_utils.py", line 610, in _raise
    raise ex  # set end OC_CAUSE=1 for full backtrace
omegaconf.errors.ConfigKeyError: Key 'sampling_alpha' not in 'AudioFinetuningConfig'
	full_key: sampling_alpha
	reference_type=Optional[AudioFinetuningConfig]
	object_type=AudioFinetuningConfig

The problem seems to stem from the sfi.py file at load_model_and_update, the main loop never breaks, and the exception keeps on happening.
I'm using the finetuned model

Hi The same issue has been fixed here please find the link
https://github.com/AI4Bharat/IndicWav2Vec/issues/5


FutureWarning: jax.tree_* is deprecated

Following #406 many jax.tree operations have been deprecated and moved to jax.tree_* -> jax.tree_util.tree_*. in the latest release resulting in many future warnings.
It would be nice to get a hk spot release that fixes these warnings.

Hi @njwfish , I'll cut a release next week to address this. Thanks for the heads up.

I just published https://github.com/deepmind/dm-haiku/releases/tag/v0.0.8 which should get rid of the deprecation warnings 😄


Too many concurrent edits to the project configuration - error

We are trying to use the tube prometheus helm chart for unmanaged workloads https://github.com/GoogleCloudPlatform/prometheus-engine/issues/298 and running into this error.
ts=2022-08-23T20:16:48.417Z caller=export.go:796 level=error component=gcm_exporter msg="send batch" size=200 err="rpc error: code = Aborted desc = Errors during metric descriptor creation: {(metric: prometheus.googleapis.com/net_conntrack_dialer_conn_attempted_total/counter, error: Too many concurrent edits to the project configuration. Please try again.), (metric: prometheus.googleapis.com/net_conntrack_dialer_conn_closed_total/counter, error: Too many concurrent edits to the project configuration. Please try again.), (metric: prometheus.googleapis.com/net_conntrack_dialer_conn_established_total/counter, error: Too many concurrent edits to the project configuration. Please try again.), (metric: prometheus.googleapis.com/net_conntrack_dialer_conn_failed_total/counter, error: Too many concurrent edits to the project configuration. Please try again.), (metric: prometheus.googleapis.com/prometheus_engine_query_duration_seconds_sum/summary:counter, error: Too many concurrent edits to the project configuration. Please try again.), (metric: prometheus.googleapis.com/prometheus_http_request_duration_seconds/histogram, error: Too many concurrent edits to the project configuration. Please try again.), (metric: prometheus.googleapis.com/prometheus_http_requests_total/counter, error: Too many concurrent edits to the project configuration. Please try again.), (metric: prometheus.googleapis.com/prometheus_http_response_size_bytes/histogram, error: Too many concurrent edits to the project configuration. Please try again.), (metric: prometheus.googleapis.com/prometheus_rule_evaluation_failures_total/counter, error: Too many concurrent edits to the project configuration. Please try again.), (metric: prometheus.googleapis.com/prometheus_rule_evaluations_total/counter, error: Too many concurrent edits to the project configuration. Please try again.), (metric: prometheus.googleapis.com/prometheus_rule_group_iterations_missed_total/counter, error: Too many concurrent edits to the project configuration. Please try again.), (metric: prometheus.googleapis.com/prometheus_rule_group_iterations_total/counter, error: Too many concurrent edits to the project configuration. Please try again.), (metric: prometheus.googleapis.com/prometheus_sd_consul_rpc_duration_seconds_sum/summary:counter, error: Too many concurrent edits to the project configuration. Please try again.), (metric: prometheus.googleapis.com/prometheus_sd_kubernetes_events_total/counter, error: Too many concurrent edits to the project configuration. Please try again.), (metric: prometheus.googleapis.com/prometheus_sd_kubernetes_http_request_duration_seconds_count/summary, error: Too many concurrent edits to the project configuration. Please try again.), (metric: prometheus.googleapis.com/prometheus_target_interval_length_seconds/summary, error: Too many concurrent edits to the project configuration. Please try again.), (metric: prometheus.googleapis.com/prometheus_target_scrape_pool_sync_total/counter, error: Too many concurrent edits to the project configuration. Please try again.), (metric: prometheus.googleapis.com/prometheus_target_sync_failed_total/counter, error: Too many concurrent edits to the project configuration. Please try again.), (metric: prometheus.googleapis.com/prometheus_target_sync_length_seconds_count/summary, error: Too many concurrent edits to the project configuration. Please try again.), (metric: prometheus.googleapis.com/prometheus_target_sync_length_seconds_sum/summary:counter, error: Too many concurrent edits to the project configuration. Please try again.)}."
ts=2022-08-23T20:16:48.891Z caller=export.go:796 level=error component=gcm_exporter msg="send batch" size=74 err="rpc error: code = Aborted desc = Errors during metric descriptor creation: {(metric: prometheus.googleapis.com/net_conntrack_dialer_conn_attempted_total/counter, error: Too many concurrent edits to the project configuration. Please try again.), (metric: prometheus.googleapis.com/net_conntrack_dialer_conn_established_total/counter, error: Too many concurrent edits to the project configuration. Please try again.), (metric: prometheus.googleapis.com/net_conntrack_dialer_conn_failed_total/counter, error: Too many concurrent edits to the project configuration. Please try again.), (metric: prometheus.googleapis.com/prometheus_engine_query_duration_seconds_count/summary, error: Too many concurrent edits to the project configuration. Please try again.), (metric: prometheus.googleapis.com/prometheus_rule_evaluation_failures_total/counter, error: Too many concurrent edits to the project configuration. Please try again.), (metric: prometheus.googleapis.com/prometheus_rule_evaluations_total/counter, error: Too many concurrent edits to the project configuration. Please try again.), (metric: prometheus.googleapis.com/prometheus_rule_group_iterations_missed_total/counter, error: Too many concurrent edits to the project configuration. Please try again.), (metric: prometheus.googleapis.com/prometheus_sd_kubernetes_events_total/counter, error: Too many concurrent edits to the project configuration. Please try again.), (metric: prometheus.googleapis.com/prometheus_sd_kubernetes_http_request_duration_seconds_sum/summary:counter, error: Too many concurrent edits to the project configuration. Please try again.), (metric: prometheus.googleapis.com/prometheus_target_interval_length_seconds/summary, error: Too many concurrent edits to the project configuration. Please try again.), (metric: prometheus.googleapis.com/prometheus_target_scrape_pool_sync_total/counter, error: Too many concurrent edits to the project configuration. Please try again.), (metric: prometheus.googleapis.com/prometheus_target_sync_length_seconds_count/summary, error: Too many concurrent edits to the project configuration. Please try again.), (metric: prometheus.googleapis.com/prometheus_target_sync_length_seconds_sum/summary:counter, error: Too many concurrent edits to the project configuration. Please try again.)}."
ts=2022-08-23T20:17:03.003Z caller=export.go:796 level=error component=gcm_exporter msg="send batch" size=200 err="rpc error: code = Aborted desc = Errors during metric descriptor creation: {(metric: prometheus.googleapis.com/apiserver_selfrequest_total/counter, error: Too many concurrent edits to the project configuration. Please try again.)}."
ts=2022-08-23T20:17:04.589Z caller=export.go:796 level=error component=gcm_exporter msg="send batch" size=200 err="rpc error: code = Aborted desc = Errors during metric descriptor creation: {(metric: prometheus.googleapis.com/apiserver_response_sizes/histogram, error: Too many concurrent edits to the project configuration. Please try again.), (metric: prometheus.googleapis.com/apiserver_selfrequest_total/counter, error: Too many concurrent edits to the project configuration. Please try again.)}."
ts=2022-08-23T20:17:04.591Z caller=export.go:796 level=error component=gcm_exporter msg="send batch" size=200 err="rpc error: code = Aborted desc = Errors during metric descriptor creation: {(metric: prometheus.googleapis.com/apiserver_response_sizes/histogram, error: Too many concurrent edits to the project configuration. Please try again.), (metric: prometheus.googleapis.com/apiserver_selfrequest_total/counter, error: Too many concurrent edits to the project configuration. Please try again.)}."
ts=2022-08-23T20:17:44.701Z caller=export.go:796 level=error component=gcm_exporter msg="send batch" size=200 err="rpc error: code = Aborted desc = Errors during metric descriptor creation: {(metric: prometheus.googleapis.com/kube_pod_container_status_waiting_reason/gauge, error: Too many concurrent edits to the project configuration. Please try again.)}."

The change in the helm chart for tube-prometheus is
prometheus:
    Container ID:  containerd://15b76a0edbe5f31e1a4177c7130973e5de1469523f1481b1976462a5c6fc4212
    Image:         gke.gcr.io/prometheus-engine/prometheus:v2.35.0-gmp.2-gke.0
    Image ID:      gke.gcr.io/prometheus-engine/prometheus@sha256:02449f32a9fa8ab02c529eb34aa5c13f49d5b6c56f5d3cf23ff7ca23af6eb7d2
    ```

    How do we handle this?

See https://cloud.google.com/stackdriver/docs/managed-prometheus/troubleshooting#concurrent-edits
tl;dr: these are transient errors caused by creating a ton of new metrics at once, which we rate limit to protect our system. They should resolve naturally within 30 minutes.

@lyanco Is this something we need to worry about?
ts=2022-08-29T16:47:07.500Z caller=export.go:796 level=error component=gcm_exporter msg="send batch" size=200 err="rpc error: code = Internal desc = Internal error encountered. Please retry after a few seconds. If internal errors persist, contact support at https://cloud.google.com/support/docs."
ts=2022-08-29T16:47:07.540Z caller=export.go:796 level=error component=gcm_exporter msg="send batch" size=200 err="rpc error: code = Internal desc = Internal error encountered. Please retry after a few seconds. If internal errors persist, contact support at https://cloud.google.com/support/docs."
ts=2022-08-29T16:47:07.580Z caller=export.go:796 level=error component=gcm_exporter msg="send batch" size=179 err="rpc error: code = Internal desc = Internal error encountered. Please retry after a few seconds. If internal errors persist, contact support at https://cloud.google.com/support/docs."
ts=2022-08-29T16:47:08.284Z caller=export.go:796 level=error component=gcm_exporter msg="send batch" size=200 err="rpc error: code = Internal desc = Internal error encountered. Please retry after a few seconds. If internal errors persist, contact support at https://cloud.google.com/support/docs."
ts=2022-08-29T16:47:08.363Z caller=export.go:796 level=error component=gcm_exporter msg="send batch" size=86 err="rpc error: code = Internal desc = Internal error encountered. Please retry after a few seconds. If internal errors persist, contact support at https://cloud.google.com/support/docs."
ts=2022-08-29T16:47:08.652Z caller=export.go:796 level=error component=gcm_exporter msg="send batch" size=200 err="rpc error: code = Internal desc = Internal error encountered. Please retry after a few seconds. If internal errors persist, contact support at https://cloud.google.com/support/docs."
ts=2022-08-29T16:47:09.366Z caller=export.go:796 level=error component=gcm_exporter msg="send batch" size=111 err="rpc error: code = Internal desc = Internal error encountered. Please retry after a few seconds. If internal errors persist, contact support at https://cloud.google.com/support/docs."

Is this still happening? Or was it transient.


(NEW__VIRAL) baltasar engonga videos telegram channel balthazar video telegram link baltasar en #111

21 seconds ago
L𝚎aked Video Balthazar Baltasar Ebang Engonga Original Video Viral Video L𝚎aked on X Twitter Telegram
Balthazar Baltasar Ebang Engonga Dark Video Female Balthazar Baltasar Ebang Engonga Dark Video Link Viral On Social Media X TikTok Trending Now
Balthazar Baltasar Ebang Engonga Original Video video took the internet by storm and amazed viewers on various social media platforms. Balthazar Baltasar Ebang Engonga , a young and talented digital creator, recently became famous thanks to this interesting video.
L𝚎aked Video Balthazar Baltasar Ebang Engonga Original Video Viral Video L𝚎aked on X Twitter
Balthazar Baltasar Ebang Engonga Original Video video oficial twitter
L𝚎aked Video Balthazar Baltasar Ebang Engonga Original Video Viral Video L𝚎aked on X Twitter.

gfhtr


post date display error

Please update Hugo to the latest version. This should be fixed.

If this issue does not get fixed after updating Hugo version, feel free to reopen.


docs: adding readme for testing suite

Description
I have worked on creating the complete testing suite of Website using Cypress , it shall be helpful for both the contributors and maintainers to know how the tests are run and the folder structure so that if any new tests have to be added to the website or existing tests are to be changed it becomes easy for them to navigate and run the tests locally .
Related issue(s)
fixes #2084

cc : @akshatnema @derberg @alequetzalli 🚀

@alequetzalli Ping Pong for the review 😅

@AnimeshKumar923 @akshatnema I can't review this because the creator of the PR has not addressed all feedback; once they finish addressing all feedback, this PR can move to next stage.

@alequetzalli
I'll take a look at this PR now. The author has become inactive in the org, so I will be making changes on behalf of her.
Do review the PR fully, so that I could make the changes at the once.

Still relevant '

/update

closing this as we don't require this fix now