winget source update returns success (0) when it fails

Brief description of your issue
The CDN being (at least partially) broken (#2666) seems like an unhandled exception in winget-cli, as it returns success / %errorlevel 0, no?
Following running in CMD as admin should not return success IMO.
C:\Windows\system32>winget source reset --force && winget source update && echo %errorlevel%
Resetting all sources...Done
Updating all sources...
Updating source: msstore...
Done
Updating source: winget...
Cancelled
0

C:\Windows\system32>

Steps to reproduce
Change DNS to replicate CDN being down?
Expected behavior
If sources can't in fact be updated, it should return an error.
Actual behavior
Says updating sources failed, but exit code 0 = success.
Environment
Windows Package Manager v1.3.2691
Copyright (c) Microsoft Corporation. All rights reserved.

Windows: Windows.Desktop v10.0.19045.2130
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.18.2691.0

This code is assuming that update never fails, and that any "failure" must surely be the user cancelling the update.  Whoever wrote that is still using some sort of default user icon with blocky purple... you know what, doesn't matter who wrote it.
https://github.com/microsoft/winget-cli/blob/34e8cbd322260641a1e9623f37a63feda9c5d8e7/src/AppInstallerCLICore/Workflows/SourceFlow.cpp#L201-L204
We can at least return E_ABORT if we think it was cancelled.  The real fix would be to actually return the error out of the update attempt so that we can decide between cancellation and error states, even if we always return some generic error like SOURCE_UPDATE_FAILED.


Added support for toggling stats huds on mobile.

This commit adds a SetCore method called ShowStatsBasedOnInputString,
which calls the GuIService method of the same name. It also adds a new
client chat command called /togglestats, which works with the following:
/togglestats (Toggles the General stats hud)
/togglestats general (Toggles the General stats hud)
/togglestats rendering (Toggles the Rendering stats hud)
/togglestats network (Toggles the Network stats hud)
/togglestats physics (Toggles the Physics stats hud)
/togglestats summary (Toggles the Summary stats hud)
/togglestats custom (Toggles the Custom stats hud)
/togglestats conhealth (Toggles the Connection Health stats hud)

Hi there, thank you for your feedback. We're going to be closing this repository as we've chosen the Roblox Dev Forum as our venue for developer feedback. Please feel free to migrate your feedback to a DevForum post if you feel it is still relevant.


feat: update faq content

This PR add  faq page new content.

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


I keep getting "Failed to update" errors in Obsius 1.2.0

I'm not able to edit or delete any existing notes. The errors are
Failed to update note
Failed to remove note
Publishing works fine.

Still same issue

same issue, still.

Still same issue

Same issue

The same.

i want to know where is the note to be saved? is data safe?  how long can you keep this website?

Same issue

This issue should now be fixed in version 1.2.2
Sorry this has taken so long.


Association Rest API Endpoint to Get One Association Record

As developer I want an association details API endpoint such that when I send a GET request to the URL I can get full details of a single association data in JSON Format
This will be a replacement to the old endpoint https://www.ebi.ac.uk/gwas/rest/api/studies
{
   "associationId":14347,
   "riskFrequency":"NR",
   "pvalueDescription":"(progression)",
   "pvalueMantissa":7,
   "pvalueExponent":-8,
   "multiSnpHaplotype":false,
   "snpInteraction":false,
   "snpType":"novel",
   "standardError":null,
   "range":null,
   "description":null,
   "orPerCopyNum":null,
   "betaNum":null,
   "betaUnit":null,
   "betaDirection":null,
   "lastMappingDate":"2023-09-15T12:31:10.000+0000",
   "lastUpdateDate":"2023-09-15T12:31:10.000+0000",
   “efoTrait”: "Dupuytren Contracture",
   "pValue":7e-8,
   "_links":{
  	"self":{
     	"href":"{base_url}/v1/associations/14347"
  	},
  	"locus":{
     	"href":"{base_url}/v1/associations/14347/loci"
  	},
  	"search":{
     	"href":"{base_url}/v1/associations?fullPvalueSet"
  	}

Must Have Additional Payload Attributes - These are displayed on the catalog UI:

discovery_ancestry (country of recruitment): "4390 European (U.K.)"
Traits: ["mental or behavioural disorder", "attempted suicide"]
Platform [SNPs passing QC]: "Affymetrix [1922309] (imputed)"
Replication ancestry (country of recruitment): "1649 NR (NR), 2698 European (Germany)"
Full Summary Statistics: "NA"
Terms/Licence: "https://www.ebi.ac.uk/about/terms-of-use/"
backgroundEfoTraits: ["",""]

Management Rules

Rule 1: Endpoint - /v1/associations/{associationId}
Rule 2: HTTP Request Method - GET
Rule 3: Endpoint should accept association id
Rule 4: Endpoint should return full attributes of the association
Rule 5: Endpoint should be accessible to all

Acceptance Criteria

Given a correct association Id
When a user sends a GET request to the endpoint
A single corresponding association data is returned in JSON Format
Given a wrong association id
When a GET request is sent to the endpoint
Properly described Resource not found exception error should be returned as JSON payload

Additional details here

Local Code changes completed


Duplicate CVE and GHSA vulnerabilities being reported to Anchore reports for the same package

Is this a request for help?: Yes

Is this a BUG REPORT or a FEATURE REQUEST? (choose one): Bug Report
Version of Anchore Engine and Anchore CLI if applicable:
Currently on:
Engine DB Version: 0.0.14
Engine Code Version: 0.9.4

Was on:
Engine Code Version: 0.9.1
(Not sure on DB Version)

What happened:
We are seeing an issue where we are seeing duplicate CVE and GHSA reported for the same package and the same vulnerability. It wasn’t happening in 0.9.1 but since we upgraded to 0.9.4 it seems to be reporting both causing our builds to break as the dev teams originally only had the CVE suppressed. Was there a regression in one of the recent versions to cause this? Or is this a feature that was broken between those two versions?
Example: https://nvd.nist.gov/vuln/detail/CVE-2021-29425 and https://github.com/advisories/GHSA-gwrp-pvrq-jmwv
What did you expect to happen:
See above
Any relevant log output from /var/log/anchore:
N/A
What docker images are you using:
N/A - All images
How to reproduce the issue:
Scan any image with both a GHSA and CVE vulnerability
Anything else we need to know:

Thanks @ssthom we'll take a look. Is there a specific public image we can verify exactly what you're seeing against?
We've made changes in this area already for the 0.10.0 release expected soon, so this may already be addressed so we'll confirm status with the current dev builds as well as the release you're reporting it on.

To clarify, the db version would not have changed between 0.9.1 and 0.9.4.

@ssthom Is there an example image that you can provide us with to help us verify the cause of the issue you are seeing?


add initial run/store interface

Rendered

Closing this. Some of this will be addressed in https://github.com/concourse/concourse/pull/6387.

Closing this. Some of this will be addressed in https://github.com/concourse/concourse/pull/6387.


Store and display your current trust level

Message about what you can do to increase your trust level would also be nice

not implementing in web app.


[stable/falco] Update Rules to match Falco version 0.13.0 rules

What this PR does / why we need it:
This PR updates the ruies file to match the same rules that are shipped with Falco 0.13.0
Which issue this PR fixes
(optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged)

fixes #

Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md

/assign bencer

/lgtm
/approve


Refactored the way that choices.xslt breaks rows

Since it seems the xml has no way of knowing when it should be
breaking the rows of choices I have change the code to use knockout
to give the 'start-column' conditionally to the css attribute.
The condition creates a filter version of the shuffleAnswer array and
makes use that to check if the corresponding choice is one that should
have the 'start-column' css rule applied to it.
The code is not pretty, but it gets the job does in as elegant a ways
as I could manage.

Thanks, but I've just pushed a commit which uses the CSS grid layout to fix this.
For future reference, I'm not using arrow functions in Numbas yet, to maintain compatibility with IE 11.


Added example with hyphen in action ID

Also added link to guide on actions - don't know if you have a better way than providing a static URL... And maybe it should be moved to the class description?
(Added the example because I didn't know whether the action had to be specified as authorComment or author-comment)

Thank you.


Fineract-953 - Upgrade ical4j from ancient version 1.0.7 to current 3.0.18

FINERACT-953

@nnatarajan We have a classpath duplicate error.

Maybe try to exclude groovy-all in dependencies.gradle.

@nnatarajan if stuck/unclear on this, it's totally OK (for me) if you first look at another issue, and come back to this later after someone else had a chance to look at this problem more closely? As @xurror said it probably needs some exclusion, but it's not always very obvious which.. BTW one of is could perhaps write up a short paragraph for the README with some guidance about how to do these upgrades - anyone interested?

I ran the integration test, but this specific error did not come up. How do I duplicate this specific error on my end: classpath duplicate error?

It's a unit test (that I wrote..), not an integration test. You can even
easily run that test in your IDE, it should give you the same result?

Sounds good. Please let me know the best way to access the test.
On Tue, May 19, 2020 at 12:17 PM Michael Vorburger ⛑ <
<EMAIL_ADDRESS>wrote:

It's a unit test (that I wrote..), not an integration test. You can even
easily run that test in your IDE, it should give you the same result?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/apache/fineract/pull/907#issuecomment-630994086, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AE5G5XY2VU3LNF4CJGIGLQDRSLEL5ANCNFSM4NDW7TZA
.

Find the exact name of that failing test on the Travis CI build log, open
it in your IDE, run it.

Maybe try to exclude groovy-all in dependencies.gradle.

@xurror in this particular case, the problem was different - #911 should hopefully fix it.

There are actually 2 totally separate problems here - the  #911 business (solved), but also some weird incompatibility between this upgrade and the Spotbugs Gradle problem... :sob: @nnatarajan this isn't exactly the greatest "starter issue"... :smiling_imp:  Would anyone else reading this want to help with figuring out the Spotbugs Gradle problem here? /Cc @thesmallstar if you are interested by this sort of thing...

I wonder if that Spotbugs Gradle problem may just disappear with #913 ... worth a rebase, after that's in.

#913 and #911 have now been merged.

Also see PR https://github.com/apache/fineract/pull/910 which has just been merged for some help.

/rebase

/rebase

Ohhh..this actually works now? Where was it fixed? What was the problem? Just curious.

@nnatarajan ...This now looks more friendly and may be easier to fix? See Travis Log: https://travis-ci.org/github/apache/fineract/builds/689183927
Something about redundant Casting to "Class"

That new problem is just due to the meanwhile merged #908 and should, hopefully, be trivial to resolve... almost there with this one!!

@vorburger , is a more experienced dev taking this on? I will remove myself from the ticket if that is the case.

@nnatarajan no no no, you're almost there with this one, we'd love you to finish this off! I've fixed unrelated problems, and you now just need to rebase, fix the latest (new) problem re. the cast, and this should be good to merge very soon! Let's get it done today? Ask if unclear. Sorry for any confusion caused!

I removed the casting, but now an error is thrown:
Verification failed: SpotBugs execution thrown exception

Hm #913 was supposed to fix that. Did you git rebase it from latest develop? It passed here because if you type slash rebase then then the remote branch of the PR gets rebased by a bot, but if you locally fix something and force push, without having rebased locally also, then that remote rebase is overwritten and lost. Does that make sense? Try to locally rebase, ./gradlew build, and if PK, then force push again, it will probably turn green.

I had rebased before pushing up modifications and #913 in showing in the code. When I ran locally ./gradlew build -- showing same error.

Curious. You can either try to dig into it, or (totally fine me!) move on to another issue and let me or someone else have a closer look into this some other time.

I had rebased before pushing up modifications and #913 in showing in the code.

Ok, great.

Does it matter if I running on Java 11?

Fineract does not support Java 8 anymore, only Java 11.

When I ran locally ./gradlew build -- showing same error.

yeah, I just locally pulled this PR, and likewise, I could locally reproduce it as well. Looking into build/reports/spotbugs/main.html, we can see that SpotBugs actually picked up on a real subtle but important bug breaking functionality that we would have introduced had we merged this PR as it is currently - thank God for SpotBugs! @nnatarajan will you look into and fix that particular problem here to get this PR to be green.
FINERACT-989 will look into the more general issue (not directly related to this PR) of SpotBug reporting.

/rebase

While investigating FINERACT-989, I have learnt that @xurror just fixed this problem in FINERACT-986, and I expect the currently running rebased Travis will now show the error much more clearly.
@xurror I don't know if FINERACT-986 was a coincidence, but if it was related to you also investigating this, please do feel free to chime in and leave a comment on any PR next time you help like this - you're great!

@vorburger - This morning, I made additional changes to the file. It appears all checks have passed. In addition to yesterday's casting errors, similarly I found other type errors. I hope this is resolved.


feat: file specifiers can now use globs to match the file path

Now using ts-declaration-location for matching where types come from.

#404  👈
main

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

Join @RebeccaStevens and the rest of your teammates on  Graphite

Merge activity

Apr 14, 3:27 AM EDT: @RebeccaStevens merged this pull request with Graphite.


Don't resummarize data stores if only their reference state changed.

Currently, we resummarize data stores if it did not receive ops but their reference state changed, i.e., they went from referenced -> unreferenced or vise-versa.
From this https://github.com/microsoft/FluidFramework/issues/8963#issuecomment-1029528450 and the related conversation in that issue, a single op may result in the change in reference state of hundreds of data stores. We should not re-summarize all these data stores as its very expensive.
We do this today because of limitations of ODSP which requires the unreferenced flag to be part of a data store's summary data. If a data store did not change, we send a handle to its data in the previous summary and ODSP retrieves the data from the previous summary. If we were to add the unreferenced flag to the handle, ODSP cannot encode that info into the data retrieved from the previous summary (or some variation of this).

Tracked by AB#391


[e2e]: generic schedule main multi-uses slsa3

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/2794230610
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.generic.schedule.main.multi-uses.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.generic.schedule.main.multi-uses.slsa3.yml
Trigger: schedule
Branch: main
Date: Thu Aug  4 04:54:23 UTC 2022

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/2794230610
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.generic.schedule.main.multi-uses.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.generic.schedule.main.multi-uses.slsa3.yml
Trigger: schedule
Branch: main
Date: Thu Aug  4 04:54:30 UTC 2022

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/2801354382
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.generic.schedule.main.multi-uses.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.generic.schedule.main.multi-uses.slsa3.yml
Trigger: schedule
Branch: main
Date: Fri Aug  5 04:57:31 UTC 2022
Tests are passing now. Closing this issue.


Improve frame sampling

Bring an updated k-means frame sampling algorithm into the COLMAP pipeline, to reduce the chance of the frames being selected being too similar.

This is done.


feat: make use of the partial file tree fetching implemented in the b…

…ackend
fix https://github.com/OpenDevin/OpenDevin/issues/1136

This implementation does not work with the selection of changed files in the file tree. Selecting changed files would mean we'd have to load that part of the tree on demand which can get very messy considering file changes are populated through actions and state updates.

Decided against this since this complicates things a lot and the new file tree implementation solves most of the UX problems.


MINOR: return unmodifiableMap for PartitionStates.partitionStateMap

Discussion https://github.com/apache/kafka/pull/7576#issuecomment-549189987. Makes the map returned by partitionStateMap unmodifiable to prevent mutation.

cc @ijuma

retest this please


Fix #288 - NbtTranslator has bad logic or formatting

Closing because frivolous

@Mumfrey There is a serious logical uncertainty here.
Are you sure you would like to continue running the code in both the 1st if block and the else statement, leading to two setTag() calls? I find it hard to believe that adding the value twice is intended.
If indeed, the double call is done on purpose, then the code in the else block should be merged into the 1st if block.

It was fixed in https://github.com/SpongePowered/SpongeCommon/commit/9a772dae0091fa21872537367f02a256fb2de561

Also refer to the Contribution Guidelines, namely the part about "small changes under 20 lines".

@saladoc O.K., will remember to do that next time.


update to latest version of egpax

TODO: Please replace this header with a description of your pull request.
Installation sequence for tool-installers

[ ] Test using @galaxybot test this
[ ] Inspect CI output for expected changes
[ ] Deploy using @galaxybot deploy this if test install was successful
[ ] Merge this PR

@galaxybot deploy this


Adding more userfriendly commands to namelayer

Added depreciated, common Citadel 1.0 commands as well as common word, unused command aliases.

Can one of the admins verify this patch?  Type 'ok to test' to test.

I think /accept might be used by civmenu, might want to remove that part.

the civmenu accept is a first login context sensitive, although I guess they could have a group invite waiting on first join before accepting the EULA.

CivMenu uses /sign, this PR should be fine.

The ct prefix is for citadel.  Legacy to that degree isn't supported and could potential confuse users when searching for ct commands.  Also the nl prefix is important in organization and letting people know that certain commands are associated with namelayer.  As such I'm not going to accept this pull request.  You can try discuss further but for now closing.

I can see why you wanted to split up NameLayer and Citadel from an organizational viewpoint, but from a user's standpoint they're still basically the same thing.
If you want to get rid of the old ct commands that's fine but namelayer commands are still a complicated heap of mess that's already impossible to search through.

Add a /nl command to accept these aliases and proxy them over to the real command classes?
/nl accept
/nl create
...


Update CI script to run tests on both the back-end and the front-end

The front-end and the back-end will be implemented as a single app


NansException

A tensor with all NaNs was produced in VAE. This could be because there's not enough precision to represent the picture. Try adding --no-half-vae commandline argument to fix this. Use --disable-nan-check commandline argument to disable this check.
This happens on stable diffusion to me.
I tried to add the commands, but after process i just receive a black image/gif
what is wrong?

I started getting output when i switched the sampler to DDIM, give that a shot?

For me this occurred when I set overlap too high


MSID: 91705 Version: 2 DOI: 10.1101/2<IP_ADDRESS>0908

MSID: 91705
Version: 2
Preprint DOI: https://doi.org/10.1101/2<IP_ADDRESS>0908
Step 1. Awaiting reviews
Editorial to post reviews via hypothesis
Useful links:

DocMap: https://data-hub-api.elifesciences.org/enhanced-preprints/docmaps/v2/by-publisher/elife/get-by-manuscript-id?manuscript_id=91705
New model tracking: https://docs.google.com/spreadsheets/d/1_fHaoOy7hjyocptKtVJRijeNpUY4hBS7Ck_aVmx6ZJk/
Reviews on sciety: https://sciety.org/articles/activity/10.1101/2<IP_ADDRESS>0908

For trouble shooting (e.g. no Docmaps available):

DocMap issue addressing: https://miro.com/app/board/uXjVNCwK6EI=/
Explore DataHub DocMaps API: https://lookerstudio.google.com/reporting/4c2f0368-babb-4beb-b5b3-497e7e7b0f08/page/ejphD
Unmatched submissions and preprints: https://lookerstudio.google.com/u/0/reporting/9f86204f-3bf7-477c-9b18-5c5ef141bf69/page/p_gxi57ha93c
Unmatched manuscripts spreadsheet: https://docs.google.com/spreadsheets/d/15QcK8w-ssB7109RQEDtFpJPZ0J5HTGxoHa_2TtpMBbg/edit#gid=1336081641

Step 2. Preview reviewed preprint
Production QC content ahead of publication
Instructions:

QC preview: https://prod--epp.elifesciences.org/previews/91705v2
Update ticket with any problems (add blocked label)
When QC OK, add QC OK label to ticket and add publication date and time to https://docs.google.com/spreadsheets/d/1amAlKvdLcaDp5W8Z8g77NmkwbMF5n_u89ArSqPMO8jg
Move card to next column
(At end of the day post link in #enhanced-preprint and ask for PDF to be generated)

Useful links:

Preprint DOI :  https://doi.org/10.1101/2<IP_ADDRESS>0908
Confirm reviews returned by EPP: https://prod--epp.elifesciences.org/api/reviewed-preprints/91705/v2/reviews
To update the MECA path in the docmap: https://docs.google.com/spreadsheets/d/1mctCQuNFBjSn97Lihy7_vBO6z7-N-oqyLv4clyi6zHg

Step 3: Awaiting search reindex
This step adds the reviewed preprint to the homepage: https://elifesciences.org
The search reindex is triggered once an hour. We need the reviewed preprint to be indexed as the search application serves the journal homepage.
Useful links:

Jenkins pipeline to reindex search can be triggered sooner or monitored here: https://alfred.elifesciences.org/job/process/job/process-reindex-reviewed-preprints/

Step 4: Published! PDF requested
Waiting for PDF to be generated
Useful links:

PDF tracking: https://docs.google.com/spreadsheets/d/106_XeDjmuBae7gexOTNzg60lapeqjl2aRn9DzupGyS8/

Step 5: Introduce PDF to data folder and git repo
Upload PDF to relevent folder in git repo https://github.com/elifesciences/enhanced-preprints-data/
Step 6: Done!

[ ] Kettle is on!

warn: [mixed-citation-other-publication-flag] mixed-citation in reference (id=c25) has a publication-type='other'. Is that correct?
warn: [mixed-citation-other-publication-flag] mixed-citation in reference (id=c65) has a publication-type='other'. Is that correct?
warn: [mixed-citation-publication-type-flag] mixed-citation has publication-type="otherg211 cl:272 " which is not one of the known/supported types: journal; book; data; patent; software; preprint; web; report; confproc; thesis; other.
warn: [article-email-corresp-author-count-equivalence] The number of corresponding authors (1: Jonas A Nilsson) is not equal to the number of distinct email addresses (2<EMAIL_ADDRESS>jonas.a.nilsson@surgery.gu.se). Is this correct?
warn: [url-conformance-test] @xlink:href doesn't look like a URL - 'http://<IP_ADDRESS>:8080/'. Is this correct?


Remove MXNet from key visual as it is no longer supported by DALI

I don't know what's our approach here, but we could consider adding a solid (non-transparent) background to this image, so that it views better in dark-mode:

I don't know what's our approach here, but we could consider adding a solid (non-transparent) background to this image, so that it views better in dark-mode:

Fixed


how can i import css

when i copy the code of demo ,it results like the picture above

If you expand the resources panel on the left side, you can find all the imported resources.
There you will also find the css that is used.


partition x not found errors should be 503 not 500

There are cases where the storage engine returns an error such as:
Status: 500, body: {"code":"internal error","message":"query error: rpc error: code = Unknown desc = partition 35 not found"
Typically, these errors are transient, and a retry succeeds. Therefore, 503 is probably the more appropriate error code.

This needs very careful consideration.  If we just change the return code we risk breaking customers workflow.  I think it makes sense to absorb this in to the "Synchronous Writes" Epic and address it there.  If we're going to be making potentially breaking changes (from a user's POV) then we should try and batch them all up together.


Using $each with array that contains multiple classes

I'm trying to use the $each property in validations with an array that has multiple classes in it - see https://jsfiddle.net/oejb3px8/3 for an example.
I can't seem to find a way to check the current element before actually creating the validation keys. For example, if I have an array like [{ common: 'first', propertyOne: '' }, { common: 'second', propertyTwo: ''}], then I don't want the propertyOne validation to exist for the second element.
What I've managed to do so far:

Create the propertyOne validator anyway and use a custom validator to return true always if that class is not supposed to have that property. This is not ideal because the validation will still be present on that array element, and it can never be made $dirty.

$each: {
  propertyOne: {
    required: function(val, elem) {
      if (elem is a specific class) {
        return true;
      }
      return required(val); // use default vuelidate required function
    }
  }
}

This doesn't quite work because I can't access the element inside $each - I'm gonna write some pseudocode below to show what I would ideally like to happen:

function returnValidator(element) {
  if (element.constructor.type === A) {
    return { propertyOne: { required: required, minLength: minLength(4) } }
  } else if (element.constructor.type === B) {
    return { propertyTwo: { required: required, minLength: minLength(6) } }
  }
}

$each: {
  common: { required: required, minLength: minLength(8) },
  ...returnValidator(element),
}

Would love to hear your thoughts on this!

$each assumes a collection of consistent type. You can use an approach i described in https://github.com/monterail/vuelidate/issues/166#issuecomment-319924309 as a workaround.

Thank you! That worked.
I'll try add this to the documentation if it's possible - would there be a workaround for the $trackBy option if using this?

In case anyone has the same issue with needing to use $trackBy, I'm currently resolving it by mapping my array of different objects (all of which have a UID parameter) - [{ uid: x, propertyOne: p1 }, { uid: y, propertyTwo: p2 }] - to a computed object whose keys are the uid - { x: { uid: x, propertyOne: p1 }, y: { uid: y, propertyTwo: p2 } } - and creating a validation object against this new object.
https://jsfiddle.net/b5v4faqf/234/

Your $trackBy can be a function if necessary :) It is given the object in question and the thing it returns must be unique.
https://github.com/monterail/vuelidate/blob/3baf496ce15f1cdcd5c9a8bcd1e9ee85ef0d067b/src/index.js#L308-L310
https://github.com/monterail/vuelidate/blob/3baf496ce15f1cdcd5c9a8bcd1e9ee85ef0d067b/src/index.js#L14-L18


Build and publish Evothings Viewer 1.4

Related issues:

https://github.com/evothings/evothings-viewer/issues/19
https://github.com/evothings/evothings-viewer/issues/20
https://github.com/evothings/evothings-viewer/issues/21

New Viewer for Android is available for testing:
https://evothings.com/uploads/evothings-studio/viewer/EvothingsViewer_1.4_160501_2042.apk
New in this version:

Plugin for NFC: https://github.com/evothings/evothings-viewer/issues/19
Plugin for Device Orientation: https://github.com/evothings/evothings-viewer/issues/20
Updated iBeacon plugin for Android 6. https://github.com/evothings/cordova-plugin-ibeacon/releases/tag/3.4.1
Updated BLE plugin for Android 6: https://github.com/evothings/cordova-ble/releases/tag/1.3.0
BLE plugin updated on npm: https://www.npmjs.com/package/cordova-plugin-ble

Test results this far:

BLE scanning and Eddystone works fine on Android 5 and 6
iBeacon scanning (ranging) works slowly, there is a delay before beacons are picked up (up to 1 minute), occasionally beacons are lost

Internal test sheet: https://docs.google.com/spreadsheets/d/173sk0XskMo3mqIAYYtkJSp2K2C7qyA0HKtxGjTaVL9Q/edit

Tested iOS, found issues:

On iOS the onReset method is not called. This is a Cordova bug. We can probably work around it by patching the Cordova code.
The "location" background mode needs to be added manually (or to the iBeacon plugin) it is not present in the updated plugin code. Testing should be done, on previous iOS versions the app broke if location mode was not present.
Also test and make video for BLE background scanning.

Status update:

BLE plugin updated, version 1.3.1 ships with Viewer 1.4: https://github.com/evothings/cordova-ble/releases/tag/1.3.1
BLE plugin updated on npm: https://www.npmjs.com/package/cordova-plugin-ble
iBeacon plugin updated, version 3.4.2 ships with Viewer 1.4 : https://github.com/evothings/cordova-plugin-ibeacon/releases/tag/3.4.2

Remaining task before release:

Make example app and video for BLE background scanning (primarily for iOS).

Version 1.4.0 is now published on the app stores for iOS and Android.
Source code release on GitHub: https://github.com/evothings/evothings-viewer/releases/tag/1.4.0


Request new module: cp-sterling-oms

Related user story
Provide the issue number for the user story related to this request
Type of module
gitops
If requesting a terraform module, what is the target cloud platform?
N/A
What is the purpose of the module?
Please describe what this automation module will do
What is the category of the module?
cluster, iam, network, database, integration, dev-tool, sre, infrastructure, util

/displayName CP Sterling Order Management

/softwareProvider: ibm-cp


What's going on?

Can i ask to the developers why this repo is not updated since a long time?
It seems a very good  project.
Is there a better alternative around here?
Thanks.

Second this! It's been almost two years ago since the last commit 😶

I've been wondering/thinking about this myself lately.  http://dronegames.co/ hasn't even been updated since, like, 2014.  Are people not into small programmable drones anymore?  Have they moved on the the Bebop or other Parrot drones, or vehicles by other manufacturers?  Or maybe this library has just gotten to the point where it does enough of what people want it to do that more development isn't really necessary.
I personally am still interested in programming the AR.Drone, though I've spent more of my time lately on a clojure port of node-ar-drone.  If you have some ideas for improvements for node-ar-drone, I'd be willing to take a look at it or at least help you work on it.

I'm the original developer of this library. I can't speak for other contributors, but my interests have shifted. I'm now developing in Go instead of node.js, and my recent side-projects have been more about 3d printing and electronics.
Dronegames piggy backed on the NodeCopter idea, but threw our original core values out of the window. As far as I can tell it was abandoned after its creator turned the resulting attention in VC funding for his own drone startup. This experience has also led to some disillusion about writing open source software and organizing community events for me.
That being said, I'm going to mentor a young high school student for a 2 month drone / computer vision project this summer. So perhaps I'll end up making some changes to this library again.

Ehy felixge, thank you for your follow up, i appreciate.
It's a shame hearing such stories but the reality shows that open source is driving the world to a better place so... don't be discouraged :)
It's nice to see that someone after you is going to keep this project up!
Regards!

Closing this since I think the question has been adequately answered 😄


Update LOCALIZATION_CONTRIBUTORS

Pull request (PR) to merge my change (list of translators for French language)

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Can you please move this to here: https://github.com/Qiskit/qiskit-translations


Drop support for Mongoid < 7 in new versions

Would like to cleanup codebase and also implement a few features such as partial indexes which require modern Mongoid
Will cut a final mongoid-slug 6.0.x release before the drop and tag it as 6.x-stable in case there is anything critical needing backport.
@dblock

@dblock please review and merge #270 if you're ok with this.


Make required arguments required.

Change method signatures to make required arguments actually required (using a paramater), all accross the API 🐮.
It's not complete (there is a few FIXME still), I'm opening the PR to gather opinion on this ; I also think it should not be merged until docker 1.11 is released 🐵.
@stevvooe is this something that you had in mind ?
/cc @calavera @MHBauer @dongluochen
This is related to and fixes #137.
🐸
Signed-off-by: Vincent Demeester<EMAIL_ADDRESS>

@vdemeester This is exactly what I was talking about. This is a fantastic start!

I like it. Makes using the api more understandable at a glance.

go for it!

I also think it should not be merged until docker 1.11 is released

agreed

@stevvooe updated with reference handling. I'm not sure I got all right but :stuck_out_tongue_closed_eyes:

LGTM

@dmcgowan @aaronlehmann @stevvooe updated :angel:

LGTM
I think we should put a note there that we intend to fix the fact that digest is transmitted in tag. That was not the intention. We should probably have an issue somewhere to simply take a ref over the API.

@stevvooe You mean for https://github.com/docker/engine-api/pull/162/files#diff-dbeb877b7334f75bc4c9063000523d71R19 or on a more general scale ? (every part of the Image* api that has repository and tag ?)
Once this (and the docker/docker counter part) is merged, I'll create an issue about it and start to work this out in both repository :wink:

@vdemeester I mean on a more general scale, but I am not sure about the level of complexity. The client-side parsing introduces a lot of errors but the reduced complexity may make the API easier to use in the future.

/cc @calavera still LGTM ? :angel:

/cc @MHBauer @dongluochen @vieux @duglin for final reviews too :angel:

LGTM

LGTM. I have a small change quest on parameter names.


Angular 16 app can't upgrade to MSAL 3+

Core Library
MSAL.js (@azure/msal-browser)
Core Library Version
3
Wrapper Library
MSAL Angular (@azure/msal-angular)
Wrapper Library Version
3
Public or Confidential Client?
Public
Description
I am upgrading to Angular v16 and updated all msal/* dependencies as well:
"@azure/msal-angular": "^3.0.6",
"@azure/msal-browser": "^3.3.0",

Unfortunately I keep getting an error during npm i execution. I tried around five-six times and every time I am getting an error:

As you can see, npm can't resolve one of the dependencies. All other packages worked fine (I've just updated dozens of them).
At first I thought this is my local problem but npmjs.com also has problems displaying details about msal-common package.

Can anyone check if this package wasn't corrupted or deleted by mistake?
Error Message
No response
Msal Logs
No response
MSAL Configuration
{
  auth: {
    clientId: '...',
    authority: 'https://login.microsoftonline.com/blahblah.onmicrosoft.com/',
    redirectUri: '/',
  },
  cache: {
    claimsBasedCachingEnabled: true,
    cacheLocation: BrowserCacheLocation.LocalStorage,
    storeAuthStateInCookie: isIE,
  },
  system: {
    loggerOptions: {
      loggerCallback,
      logLevel: LogLevel.Verbose,
      piiLoggingEnabled: false,
    },
  },
}

Relevant Code Snippets
None

Reproduction Steps
Try to install the following packages:
"@azure/msal-angular": "^3.0.6",
"@azure/msal-browser": "^3.3.0",

Expected Behavior
Packages should be installed without an error
Identity Provider
Azure AD / MSA
Browsers Affected (Select all that apply)
Chrome
Regression
No response
Source
Internal (Microsoft)

NPM is currently experiencing an incident related to package installs (we've seen this with some of our dependencies today as well). Please track status here for resolution.


adds a self managed, react-app template

This commit renames the current React template to cra-react, and adds a new template that provides a self managed app without any workflow dependencies.
The logic behind this change is to provide the users with a managed workflow(CRA), as well as a self managed one for custom configurations(React, Webpack5 and Babel).
One dependency which would need to be changed after this is the CLI, where the URLS will have to be adjusted. I can send a PR for this on your CLI fork if okay @mrinalwahal.
TODO

[x] Add Nhost-auth

We specifically renamed it from cra-react to react, because the CLI fundamentally does nothing except parse the git tree for templates directory and clone the same directory based on the framework choice.
Simply using react follows the convention by nuxt and next.
Otherwise if users want to bypass the prompt on CLI they will have to choose nhost templates -c cra-react instead of nhost templates -c react.
We want to keep the latter since it follows the format with other frameworks. Example: nhost templates -c nuxt

Ah I see. The issue is we would like to support a CRA-less React template as well, since most apps need to be 'ejected' at one time anyway. What should we do if we decide to use both the pure React, as well as the CRA managed template?

If you need both pure react and a CRA managed template, then we have no other option than using both react and cra-react folders.
I'll let @nunopato take the call. And will make the required change on the CLI accordingly.

Maybe we could display a sub-menu on nhost templates -c react and let the user decide there instead? I personally think it will be good to support a CRA less template as well.

I don't think that's a good idea. CLIs have their own design philosophy. It's not good practice to make them unpredictable by adding recursive sub-options for a single option. Also, we'll need to handle those sub-options through flags as well, to allow users to bypass those prompts in cases where we don't have access to their host machines.
Using two different folders is a better idea, than this one.

Closing this MR - it will be implemented in future if requested by users.


Can't compile polars-lazy with nightly-2023-10-12

I ran into an issue when compiling:
error[E0432]: unresolved import `polars_plan::dsl::all_horizontal`
  --> /Users/billy/.cargo/registry/src/index.crates.io-6f17d22bba15001f/polars-lazy-0.34.2/src/frame/mod.rs:28:5
   |
28 | use polars_plan::dsl::all_horizontal;
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ no `all_horizontal` in `dsl`

For more information about this error, try `rustc --explain E0432`.
error: could not compile `polars-lazy` (lib) due to previous error
warning: build failed, waiting for other jobs to finish...

== Compilation error in file lib/explorer/polars_backend/native.ex ==
** (RuntimeError) Rust NIF compile error (rustc exit code 101)
    (rustler 0.29.1) lib/rustler/compiler.ex:37: Rustler.Compiler.compile_crate/2
    lib/explorer/polars_backend/native.ex:32: (module)

This seems like a very recent issue with Polars:

https://github.com/pola-rs/polars/issues/12050

I was able to workaround it locally by doing the following:

unset the toolchain override$ cd native/explorer
$ rustup override unset
info: override toolchain for 'path/to/explorer/native/explorer' removed

In rust-toolchain.toml, change

channel = "nightly-2023-10-12" to
channel = "nightly-2023-10-31"

Run mix compile --force from root

Which successfully compiles. Note that unsetting the override was crucial. Just changing rust-toolchain.toml wasn't enough.
Also now when I run rustup show I get:
Default host: x86_64-apple-darwin
rustup home:  /Users/billy/.rustup

installed toolchains
--------------------

...

active toolchain
----------------

nightly-x86_64-apple-darwin (overridden by 'path/to/explorer/rust-toolchain.toml')
rustc 1.75.0-nightly (9d83ac217 2023-10-31)

I'm not sure if this issue is just on my machine. But just in case it isn't I figured my workaround might be useful.

Oops I was wrong! I just retried nightly-2023-10-12 and it worked.
I think I tricked myself somewhere along the way during my many attempts to compile. Perhaps it's time to walk away from my computer :)


New logo/icon proposal

Good day sir. I am a graphic designer and i am interested in designing a logo for your good project. I will be doing it as a gift for free. I just need your permission first before I begin my design. Hoping for your positive feedback. Thanks

Hello!
We appreciate your help with logo )
You can send your concepts to my email denis @ cleverpumpkin.ru

I have design logo for this project. what do you think ? do you like it ? which one do you like ? If there is a change. please let me know.

how about the logo. I really hope for a positive response from you.


Some panic and other statements can be simplified

We can improve readability by replacing lines like
panic!(
  "expected a module ordinal for identifier '{}', but none was found.",
  module
)

with
panic!("expected a module ordinal for identifier '{module}', but none was found.")

This should improve the codebase's maintainability and developer productivity.

PR currently in-progress


[Applying for a workshop] Inconsistency of the 'Application' page with the design

Environment: Windows 10 Corporate LTSC 64-bit, Google Chrome v100.0.4896.127
Reproducible: always
Build found: Frontend: gcp-0.0.50, Backend: gcp-0.0.101
Preconditions

Follow the link https://oos.dmytrominochkin.cloud/#/
Log into system as a Parent (e.g<EMAIL_ADDRESS>'Password'="Teteruk1!").
Open any workshop's page by clicking the "Детальніше" button on the workshop card.
Click on the 'Подати заяву' button.
The 'Application' page is opened.
Choose the child from the "Виберіть дитину" drop-down list.

Steps to reproduce
Look at the 'Application' page.
Actual result

There is no indents after 'Дані про дитину' and 'Дані про батьків' fields.

There is no indent after the workshop name. The name of the school doesn't match the design.

The 'Телефон' field's data is not displayed according to the mock-up.

Expected result

There should be indents after 'Дані про дитину' and 'Дані про батьків' fields according to the mock-up.

There should be an indent after the workshop name. The name of the school has to match the design.

The 'Телефон' field's data should be displayed according to the mock-up.

User story and test case links
User story https://github.com/ita-social-projects/OoS-Backend/issues/131
Labels to be added
Bug, pri: very low, severity: trivial, UI

verified and closed!


OpenAPI IP address support

OpenAPI IP addresses should be supported as a format (in poem-openapi as a type).
OpenAPI does not make reference to them in the specification but they seem to be supported.
See https://github.com/swagger-api/swagger-ui/pull/5033 for support on this point.
I recommend adding type support for Ipv4Addr as it is an existing struct.

It's easy, do it like below, would you like to open a PR to help me with this? 🙂
https://github.com/poem-web/poem/blob/master/poem-openapi/src/types/external/uuid.rs


bug: time_t is the wrong size on i686-musl

Did you check docs and existing issues?

[X] I have read all the lazy.nvim docs
[X] I have updated the plugin to the latest version before submitting this issue
[X] I have searched the existing issues of lazy.nvim
[X] I have searched the existing issues of plugins related to this issue

Neovim version (nvim -v)
v0.11.0-dev-1201+g0e2f92ed79
Operating system/version
Alpine Linux v3.14
Describe the bug
(Note: this reproduces on a wide variety of Neovim commits, and on later versions of Alpine and on Gentoo with a musl profile.)
lazy.nvim segfaults on i686-musl systems. It seems that this can be fixed with the following patch:
diff --git a/lua/lazy/stats.lua b/lua/lazy/stats.lua
index 015a2be..5195a56 100644
--- a/lua/lazy/stats.lua
+++ b/lua/lazy/stats.lua
@@ -34,51 +34,51 @@ end
 function M.cputime()
   if M.C == nil then
     pcall(function()
       ffi.cdef([[
         typedef long time_t;
         typedef int clockid_t;
         typedef struct timespec {
           time_t   tv_sec;        /* seconds */
           long     tv_nsec;       /* nanoseconds */
         } nanotime;
         int clock_gettime(clockid_t clk_id, struct timespec *tp);
       ]])
       M.C = ffi.C
     end)
   end

   local function real()
     local pnano = assert(ffi.new("nanotime[?]", 1))
     local CLOCK_PROCESS_CPUTIME_ID = jit.os == "OSX" and 12 or 2
     ffi.C.clock_gettime(CLOCK_PROCESS_CPUTIME_ID, pnano)
     return tonumber(pnano[0].tv_sec) * 1e3 + tonumber(pnano[0].tv_nsec) / 1e6
   end

   local function fallback()
     return (vim.uv.hrtime() - require("lazy")._start) / 1e6
   end

-  local ok, ret = pcall(real)
-  if ok then
-    M.cputime = real
-    M._stats.real_cputime = true
-    return ret
-  else
+  -- local ok, ret = pcall(real)
+  -- if ok then
+    -- M.cputime = real
+    -- M._stats.real_cputime = true
+    -- return ret
+  -- else
     M.cputime = fallback
     return fallback()
-  end
+  -- end
 end

 function M.stats()
   M._stats.count = 0
   M._stats.loaded = 0
   for _, plugin in pairs(require("lazy.core.config").plugins) do
     M._stats.count = M._stats.count + 1
     if plugin._.loaded then
       M._stats.loaded = M._stats.loaded + 1
     end
   end
   return M._stats
 end

 return M

The typedef long time_t; is certainly incorrect here -- long is int32_t on i686, but time_t is int64_t.
(This is insufficient to fix the segfault, but it's at least an easy thing to fix.)
FWIW, an example stack trace on segfault is:
#0  0x56a8e8fe in lj_alloc_free (msp=0xf7e98008, ptr=<optimized out>) at lj_alloc.c:1400
#1  0x56abb727 in lj_mem_free (osize=<optimized out>, p=0xf7de6940, g=0xf7e981f8)
    at /code/.deps/build/src/luajit/src/lj_gc.h:122
#2  lj_cdata_free (g=0xf7e981f8, cd=<optimized out>) at lj_cdata.c:83
#3  0x56a97077 in gc_sweep (g=g@entry=0xf7e981f8, p=0xf7e92218, lim=9, lim@entry=40) at lj_gc.c:423
#4  0x56a97d6a in gc_onestep (L=0xf7e981c8) at lj_gc.c:683
#5  0x56a9840b in lj_gc_step (L=L@entry=0xf7e981c8) at lj_gc.c:732
#6  0x56a851d7 in lj_parse_keepstr (ls=ls@entry=0xffef0ca8, str=0xf7e9f2b1 "` changed `dir`:\n- from: `\"", len=26)
    at lj_parse.c:246
#7  0x56a820bd in lex_string (tv=<optimized out>, ls=0xffef0ca8) at lj_lex.c:285
#8  lex_scan (ls=ls@entry=0xffef0ca8, tv=tv@entry=0xffef0cb0) at lj_lex.c:368
#9  0x56a82a05 in lj_lex_next (ls=ls@entry=0xffef0ca8) at lj_lex.c:460
#10 0x56a85806 in expr_binop (ls=ls@entry=0xffef0ca8, v=v@entry=0xffef02a8, limit=limit@entry=4) at lj_parse.c:2118
#11 0x56a85d7f in expr_binop (ls=ls@entry=0xffef0ca8, v=v@entry=0xffef0360, limit=limit@entry=0) at lj_parse.c:2121
#12 0x56a88678 in expr (v=0xffef0360, ls=0xffef0ca8) at lj_parse.c:2132
#13 expr_list (v=0xffef0360, ls=0xffef0ca8) at lj_parse.c:1899
#14 parse_local (ls=0xffef0ca8) at lj_parse.c:2284
#15 parse_stmt (ls=0xffef0ca8) at lj_parse.c:2676
#16 parse_chunk (ls=ls@entry=0xffef0ca8) at lj_parse.c:2713
#17 0x56a87b57 in parse_block (ls=0xffef0ca8) at lj_parse.c:2429
#18 parse_then (ls=0xffef0ca8) at lj_parse.c:2619
#19 parse_if (line=99, ls=0xffef0ca8) at lj_parse.c:2629
#20 parse_stmt (ls=0xffef0ca8) at lj_parse.c:2655
#21 parse_chunk (ls=ls@entry=0xffef0ca8) at lj_parse.c:2713
#22 0x56a87b57 in parse_block (ls=0xffef0ca8) at lj_parse.c:2429
#23 parse_then (ls=0xffef0ca8) at lj_parse.c:2619
#24 parse_if (line=95, ls=0xffef0ca8) at lj_parse.c:2629
#25 parse_stmt (ls=0xffef0ca8) at lj_parse.c:2655
#26 parse_chunk (ls=ls@entry=0xffef0ca8) at lj_parse.c:2713
#27 0x56a853a3 in parse_body (ls=ls@entry=0xffef0ca8, e=e@entry=0xffef08e0, needself=<optimized out>,
    line=line@entry=71) at lj_parse.c:1876
#28 0x56a87713 in parse_func (line=71, ls=0xffef0ca8) at lj_parse.c:2309
#29 parse_stmt (ls=0xffef0ca8) at lj_parse.c:2672
#30 parse_chunk (ls=ls@entry=0xffef0ca8) at lj_parse.c:2713
#31 0x56a88aed in lj_parse (ls=ls@entry=0xffef0ca8) at lj_parse.c:2747
#32 0x56a88be4 in cpparser (L=0xf7e981c8, dummy=0x0, ud=0xffef0ca8) at lj_load.c:50
#33 0x56a9539c in lj_vm_cpcall ()
#34 0x56a88da7 in lua_loadx (L=L@entry=0xf7e981c8, reader=reader@entry=0x56a88c90 <reader_file>,
    data=data@entry=0xffef0d6c,
    chunkname=chunkname@entry=0xf7e28afc <EMAIL_ADDRESS>    mode=mode@entry=0x0) at lj_load.c:72
#35 0x56a88ef2 in luaL_loadfilex (L=L@entry=0xf7e981c8,
    filename=filename@entry=0xf7ddbf3c "/root/.local/share/nvim/lazy/lazy.nvim/lua/lazy/core/meta.lua",
    mode=mode@entry=0x0) at lj_load.c:117
#36 0x56ac6877 in lj_cf_loadfile (L=0xf7e981c8) at lib_base.c:386
#37 0x56a95078 in lj_BC_FUNCC ()
#38 0x56acbfc4 in lj_cf_package_require (L=0xf7e981c8) at lib_package.c:453
#39 0x56a95078 in lj_BC_FUNCC ()
#40 0x56acc0b9 in lj_cf_package_require (L=0xf7e981c8) at lib_package.c:464
#41 0x56a95078 in lj_BC_FUNCC ()
#42 0x56acc0b9 in lj_cf_package_require (L=0xf7e981c8) at lib_package.c:464
#43 0x56a95078 in lj_BC_FUNCC ()
#44 0x56a80af4 in lua_pcall (L=0xf7e981c8, nargs=0, nresults=0, errfunc=-2) at lj_api.c:1151
#45 0x5683d2d5 in nlua_pcall (lstate=0xf7e981c8, nargs=0, nresults=0) at ../src/nvim/lua/executor.c:174
#46 0x56841700 in nlua_exec_file (path=0xf7e0a3a0 "/root/.config/nvim/init.lua") at ../src/nvim/lua/executor.c:1860
#47 0x56935789 in do_source (fname=0xf7e11cb0 "/root/.config/nvim/init.lua", check_other=1, is_vimrc=1, ret_sid=0x0)
    at ../src/nvim/runtime.c:2224
#48 0x5684faad in do_user_initialization () at ../src/nvim/main.c:1995
#49 0x5684ffa5 in source_startup_scripts (parmp=0xffef1604) at ../src/nvim/main.c:2108
#50 0x5684c102 in main (argc=2, argv=0xffef1764) at ../src/nvim/main.c:463

How exactly we get to gc_sweep differs, but the trace always ends in those same frames #0-#3.
Steps To Reproduce

Be on an i686-musl platform. (The muslcc/i686:i686-linux-musl Docker container is sufficient.)

Use the following init.lua:
-- Bootstrap lazy.nvim
local lazypath = vim.fn.stdpath("data") .. "/lazy/lazy.nvim"
if not (vim.uv or vim.loop).fs_stat(lazypath) then
  local lazyrepo = "https://github.com/folke/lazy.nvim.git"
  local out = vim.fn.system({ "git", "clone", "--filter=blob:none", "--branch=stable", lazyrepo, lazypath })
  if vim.v.shell_error ~= 0 then
    vim.api.nvim_echo({
      { "Failed to clone lazy.nvim:\n", "ErrorMsg" },
      { out, "WarningMsg" },
      { "\nPress any key to exit..." },
    }, true, {})
    vim.fn.getchar()
    os.exit(1)
  end
end
vim.opt.rtp:prepend(lazypath)

-- Make sure to setup `mapleader` and `maplocalleader` before
-- loading lazy.nvim so that mappings are correct.
-- This is also a good place to setup other settings (vim.opt)
vim.g.mapleader = " "
vim.g.maplocalleader = "\\"

-- Setup lazy.nvim
require("lazy").setup({
})

collectgarbage()

Open nvim ~/.config/nvim/init.lua (or another not-tiny file; if it doesn't repro, open another/larger file)

Get a segfault

Expected Behavior
Don't segfault
Repro
vim.env.LAZY_STDPATH = ".repro"
load(vim.fn.system("curl -s https://raw.githubusercontent.com/folke/lazy.nvim/main/bootstrap.lua"))()

require("lazy.minit").repro({
  spec = {
    -- add any other plugins here
  },
})

-- not always necessary
collectgarbage()

So your fix is to just disable the cpu time??

Not a fix, a "debugging patch" -- it seems that it's pointing at that block as being related to the problem. The time_t definition, I can at least verify as being ABI-incorrect, so it could be the cause of the memory corruption, but I think there's something else there too (since just changing it to long long is insufficient to fix the segfault.)

Problem still exists.


Sometimes the timer doesn't stop.

Sometimes the timer doesn't stop when finish the round (your score/best score state).

I have not observed the error since my most recent changes, but this issue has been sporadic.

I believe this is fixed and we can close this issue. We'll reopen it if I am wrong.


[Accessibility]A11y_AzureDataStudio_CSVSelectDestinationDatbse_ScreenReader:VoiceOver does not read the ordering for list items under “Database the external table will be created  in ” combo box  .

Check out Keros! - Identify accessibility bugs before check-in and make bug fixing faster and easier.
GitHubTags: #A11yMAS; #A11yTCS; #MAS1.3.1; #A11y_AzureDataStudio; #MacOs; #DesktopApp
Environment Details:
Application name: Azure Data Studio
Version: 1.8.0-insider (user setup)
Commit: 2ca39b5
Electron: 3.1.8
Node.js: 10.2.0
V8: 6.6.346.32
OS : MacOS Mojave 10.14.5
Additional Details:
Tools Name: VoiceOver
MAS References: MAS1.3.1
Steps to Reproduce:
1.Install the app Azure Data Studio.
2.Connect to database->navigate to the Data services folder->HDFS Folder-> navigate to CSV files folder->Right click on the files->Select option Create external table from CSV files.
3.Start VoiceOver.
4.Navigate to the “Database the external table will be created  in ” combo box .
5.Observe that screen reader is not read the ordering for list items under  “Database the external table will be created  in ” combo box.
Actual:
Navigate till “Database the external table will be created  in ” combo box ,screen reader is not read the ordering for list items under  “Database the external table will be created  in ” combo box.
Similar issue has been found under the below pages:
1.MapDataSrcObjects- Enable SQL server2019 preview->select table from the database->Create External Table screen should open->Next button->Create Database Master Key screen should open->click on next button->fill all the required details->click on next button.
Expected:
Screen Reader should read order for the list item for example for item "WizardTesting" screen reader should announce "WizardTesting 1 of 5 level 1" and similar for other items.
Similar issue is also observed for other Combo boxes.
Recommendation:
Please refer the following snippet link for fixes:
https://microsoft.sharepoint.com/teams/msenable/mas/pages/browse-fixes.aspx
User Impact:
Screen reader user is unable to understand order of checkboxes are present on the page.
MAS Reference:
MAS1.3.1-
https://microsoft.sharepoint.com/:w:/r/teams/msenable/_layouts/15/WopiFrame.aspx?sourcedoc={54f28d1f-a2d1-4dcd-84e1-5c9b87e8aba4}
Attachment for Reference:
5971_[Accessibility]A11y_AzureDataStudio_CSVSelectDestinationDatbse_ScreenReader.pptx
Does this issue occur when all extensions are disabled?: Yes

Possibly related to #5969

VoiceOver doesn't seem to read out ordering at all. I created a simple html file with a select box, and it didn't announce any ordering like "1 of 15", as would be heard with Narrator, just the labels of the dropdown items.


[youtube] extractor report Downloading m3u8 information for both proto https and m3u8.

DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE

[X] I understand that I will be blocked if I intentionally remove or skip any mandatory* field

Checklist

[X] I'm asking a question and not reporting a bug or requesting a feature
[X] I've looked through the README
[X] I've verified that I'm running yt-dlp version 2023.07.06 (update instructions) or later (specify commit)
[X] I've searched known issues and the bugtracker for similar questions including closed ones. DO NOT post duplicates
[X] I've read the guidelines for opening an issue

Please make sure the question is worded well enough to be understood
[info] Available formats for p9k-nb5w1OU:
ID  EXT   RESOLUTION FPS CH │   FILESIZE   TBR PROTO │ VCODEC          VBR ACODEC      ABR ASR MORE INFO
───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
sb2 mhtml 48x27        1    │                  mhtml │ images                                  storyboard
sb1 mhtml 80x45        1    │                  mhtml │ images                                  storyboard
sb0 mhtml 160x90       1    │                  mhtml │ images                                  storyboard
233 mp4   audio only        │                  m3u8  │ audio only          unknown             [en] Default
234 mp4   audio only        │                  m3u8  │ audio only          unknown             [en] Default
599 m4a   audio only      2 │  339.30KiB   31k https │ audio only          mp4a.40.5   31k 22k [en] ultralow, m4a_dash
600 webm  audio only      2 │  339.05KiB   31k https │ audio only          opus        31k 48k [en] ultralow, webm_dash
139 m4a   audio only      2 │  537.26KiB   49k https │ audio only          mp4a.40.5   49k 22k [en] low, m4a_dash
249 webm  audio only      2 │  500.90KiB   46k https │ audio only          opus        46k 48k [en] low, webm_dash
250 webm  audio only      2 │  656.76KiB   60k https │ audio only          opus        60k 48k [en] low, webm_dash
140 m4a   audio only      2 │    1.39MiB  130k https │ audio only          mp4a.40.2  130k 44k [en] medium, m4a_dash
251 webm  audio only      2 │    1.28MiB  120k https │ audio only          opus       120k 48k [en] medium, webm_dash
17  3gp   176x144      8  1 │  891.67KiB   81k https │ mp4v.20.3           mp4a.40.2       22k [en] 144p
597 mp4   256x144     15    │  352.15KiB   32k https │ avc1.4d400b     32k video only          144p, mp4_dash
602 mp4   256x144     15    │ ~966.60KiB   86k m3u8  │ vp<IP_ADDRESS>   86k video only
598 webm  256x144     15    │  278.52KiB   25k https │ vp9             25k video only          144p, webm_dash
394 mp4   256x144     30    │  787.63KiB   72k https │ av01.0.00M.08   72k video only          144p, mp4_dash
269 mp4   256x144     30    │ ~  1.82MiB  166k m3u8  │ avc1.4D400C    166k video only
160 mp4   256x144     30    │  803.11KiB   73k https │ avc1.4D400C     73k video only          144p, mp4_dash
603 mp4   256x144     30    │ ~  1.69MiB  154k m3u8  │ vp<IP_ADDRESS>  154k video only
278 webm  256x144     30    │  913.17KiB   83k https │ vp<IP_ADDRESS>   83k video only          144p, webm_dash
395 mp4   426x240     30    │    1.15MiB  108k https │ av01.0.00M.08  108k video only          240p, mp4_dash
229 mp4   426x240     30    │ ~  3.95MiB  360k m3u8  │ avc1.4D4015    360k video only
133 mp4   426x240     30    │    1.59MiB  148k https │ avc1.4D4015    148k video only          240p, mp4_dash
604 mp4   426x240     30    │ ~  3.17MiB  289k m3u8  │ vp<IP_ADDRESS>  289k video only
242 webm  426x240     30    │    1.77MiB  165k https │ vp<IP_ADDRESS>  165k video only          240p, webm_dash
396 mp4   640x360     30    │    2.54MiB  237k https │ av01.0.01M.08  237k video only          360p, mp4_dash
230 mp4   640x360     30    │ ~  7.77MiB  707k m3u8  │ avc1.4D401E    707k video only
134 mp4   640x360     30    │    2.99MiB  279k https │ avc1.4D401E    279k video only          360p, mp4_dash
18  mp4   640x360     30  2 │    6.79MiB  633k https │ avc1.42001E         mp4a.40.2       44k [en] 360p
605 mp4   640x360     30    │ ~  6.29MiB  573k m3u8  │ vp<IP_ADDRESS>  573k video only
243 webm  640x360     30    │    3.17MiB  296k https │ vp<IP_ADDRESS>  296k video only          360p, webm_dash
397 mp4   854x480     30    │    4.42MiB  412k https │ av01.0.04M.08  412k video only          480p, mp4_dash
231 mp4   854x480     30    │ ~ 11.02MiB 1003k m3u8  │ avc1.4D401F   1003k video only
135 mp4   854x480     30    │    4.26MiB  397k https │ avc1.4D401F    397k video only          480p, mp4_dash
606 mp4   854x480     30    │ ~ 10.06MiB  916k m3u8  │ vp<IP_ADDRESS>  916k video only
244 webm  854x480     30    │    4.86MiB  453k https │ vp<IP_ADDRESS>  453k video only          480p, webm_dash
22  mp4   1280x720    30  2 │ ≈ 18.07MiB 1645k https │ avc1.64001F         mp4a.40.2       44k [en] 720p
136 mp4   1280x720    30    │   16.25MiB 1516k https │ avc1.4d401f   1516k video only          720p, mp4_dash
247 webm  1280x720    30    │   10.28MiB  959k https │ vp9            959k video only          720p, webm_dash
398 mp4   1280x720    60    │   14.25MiB 1328k https │ av01.0.08M.08 1328k video only          720p60, mp4_dash
311 mp4   1280x720    60    │ ~ 20.12MiB 1831k m3u8  │ avc1.4D4020   1831k video only
298 mp4   1280x720    60    │    8.36MiB  779k https │ avc1.4D4020    779k video only          720p60, mp4_dash
612 mp4   1280x720    60    │ ~ 25.34MiB 2307k m3u8  │ vp<IP_ADDRESS> 2307k video only
302 webm  1280x720    60    │   12.76MiB 1190k https │ vp<IP_ADDRESS> 1190k video only          720p60, webm_dash
399 mp4   1920x1080   60    │   25.82MiB 2408k https │ av01.0.09M.08 2408k video only          1080p60, mp4_dash
312 mp4   1920x1080   60    │ ~ 70.29MiB 6398k m3u8  │ avc1.64002A   6398k video only
299 mp4   1920x1080   60    │   30.82MiB 2874k https │ avc1.64002A   2874k video only          1080p60, mp4_dash
617 mp4   1920x1080   60    │ ~ 52.07MiB 4740k m3u8  │ vp<IP_ADDRESS> 4740k video only
303 webm  1920x1080   60    │   27.90MiB 2602k https │ vp<IP_ADDRESS> 2602k video only          1080p60, webm_dash

Issue 1:
format 303 should display `downloading https information' (what I remember the older version before 20230306 did), but now the output is
[youtube] Extracting URL: https://www.youtube.com/watch?v=p9k-nb5w1OU
[youtube] p9k-nb5w1OU: Downloading webpage
[youtube] p9k-nb5w1OU: Downloading ios player API JSON
[youtube] p9k-nb5w1OU: Downloading android player API JSON
[youtube] p9k-nb5w1OU: Downloading m3u8 information # Watch this line
[info] p9k-nb5w1OU: Downloading 1 format(s): 303+251
[download] Destination: Overwatch 2： Fight the Invasion Trailer ｜ The Null Sector Threat [p9k-nb5w1OU].f303.webm
[download]  42.8% of   27.90MiB at    1.17MiB/s ETA 00:13
ERROR: Interrupted by user

format 617 should display Downloading m3u8 information and it's correct:
[youtube] Extracting URL: https://www.youtube.com/watch?v=p9k-nb5w1OU
[youtube] p9k-nb5w1OU: Downloading webpage
[youtube] p9k-nb5w1OU: Downloading ios player API JSON
[youtube] p9k-nb5w1OU: Downloading android player API JSON
[youtube] p9k-nb5w1OU: Downloading m3u8 information # Watch this line
[info] p9k-nb5w1OU: Downloading 1 format(s): 617+251
[hlsnative] Downloading m3u8 manifest
[hlsnative] Total fragments: 20
[download] Destination: Overwatch 2： Fight the Invasion Trailer ｜ The Null Sector Threat [p9k-nb5w1OU].f617.mp4
[download]  36.1% of ~  21.78MiB at  137.24KiB/s ETA 01:43 (frag 6/20)
ERROR: Interrupted by user

Issue 2:
617 mp4   1920x1080   60    │ ~ 52.07MiB from the [info] Available formats for p9k-nb5w1OU:
I know it's unable to predict precisely, but this usually report twice large as the real size and which is ~28MB the same as 303 in this case.
haven't read the code, but maybe this can be improved?
Issue 3:
the downloading of 617 is correctly fragmented as showed [download]  36.1% of ~  21.78MiB at  137.24KiB/s ETA 01:43 (frag 6/20) above.
However, the downloading of 303 seems to be also https fragmented with the 'range' http header, you can tell by watching the downloading speed increase from ~50KB to ~2MB then drop back to ~50KB repeat over and over again. this may be related to the old comment https://github.com/yt-dlp/yt-dlp/issues/6400#issuecomment-1477819819
Note: All bytes of the downloaded 617 and 303 are exactly the same except only a few bytes of the metadata of the container.
BTW, the overall speed of format 617 is about 500KB/S, while the speed of 303 can be up to 2MB/S,
So the 617 is slower than 303, and the 617 probably is throttled or normal just like the age-restricted urls discussed in old issues?
Also downloading speed of 303 can be higher (more than 2MB/S) as the older version before than now if issue 3 is solved.
Provide verbose output that clearly demonstrates the problem

[X] Run your yt-dlp command with -vU flag added (yt-dlp -vU <your command line>)
[ ] If using API, add 'verbose': True to YoutubeDL params instead
[X] Copy the WHOLE output (starting with [debug] Command-line config) and insert it below

Complete Verbose Output
[debug] Command-line config: ['https://www.youtube.com/watch?v=p9k-nb5w1OU', '-vU']
[debug] Encodings: locale cp936, fs utf-8, pref cp936, out utf-8, error utf-8, screen utf-8
[debug] yt-dlp version<EMAIL_ADDRESS>[b532a3481] (pip)
[debug] Python 3.11.2 (CPython AMD64 64bit) - Windows-10-10.0.17134-SP0 (OpenSSL 1.1.1s  1 Nov 2022)
[debug] exe versions: ffmpeg 5.1.2-full_build-www.gyan.dev (setts), ffprobe 5.1.2-full_build-www.gyan.dev, phantomjs 2.1.1
[debug] Optional libraries: Cryptodome-3.17, brotli-1.0.9, certifi-2022.12.07, mutagen-1.46.0, sqlite3-2.6.0, websockets-10.4
[debug] Proxy map: {}
[debug] Loaded 1855 extractors
[debug] Fetching release info: https://api.github.com/repos/yt-dlp/yt-dlp/releases/latest
Available version<EMAIL_ADDRESS>Current version<EMAIL_ADDRESS>yt-dlp is up to date<EMAIL_ADDRESS>[youtube] Extracting URL: https://www.youtube.com/watch?v=p9k-nb5w1OU
[youtube] p9k-nb5w1OU: Downloading webpage
[youtube] p9k-nb5w1OU: Downloading ios player API JSON
[youtube] p9k-nb5w1OU: Downloading android player API JSON
[debug] Loading youtube-nsig.f98908d1 from cache
[debug] [youtube] Decrypted nsig IiqSwdpTHsWzzNTSO => Y8rj0oOPM3Nkdg
[youtube] p9k-nb5w1OU: Downloading m3u8 information
[debug] Sort order given by extractor: quality, res, fps, hdr:12, source, vcodec:vp9.2, channels, acodec, lang, proto
[debug] Formats sorted by: hasvid, ie_pref, quality, res, fps, hdr:12(7), source, vcodec:vp9.2(10), channels, acodec, lang, proto, size, br, asr, vext, aext, hasaud, id
[debug] Default format spec: bestvideo*+bestaudio/best
[info] p9k-nb5w1OU: Downloading 1 format(s): 303+251
[debug] Invoking http downloader on "https://rr2---sn-a5meknd6.googlevideo.com/videoplayback?expire=1691525728&ei=AE7SZLm0EtO3sfIP0bmH8AM&ip=<IP_ADDRESS>&id=o-AK3DyrZ3q9yE77AkYpFTjB47WpaIqpgVkMvYHs0kXNiF&itag=303&source=youtube&requiressl=yes&mh=xc&mm=31%2C29&mn=sn-a5meknd6%2Csn-a5mlrnll&ms=au%2Crdu&mv=m&mvi=2&pl=23&initcwndbps=9870000&vprv=1&svpuc=1&mime=video%2Fwebm&gir=yes&clen=29255684&dur=89.956&lmt=1691260189052006&mt=1691503792&fvip=4&keepalive=yes&fexp=24007246%2C51000022&beids=24350018&c=IOS&txp=5535434&sparams=expire%2Cei%2Cip%2Cid%2Citag%2Csource%2Crequiressl%2Cvprv%2Csvpuc%2Cmime%2Cgir%2Cclen%2Cdur%2Clmt&sig=AOq0QJ8wRAIgZXlW0O6GR6o_DoA0mckYk1o66cR7gePUwa10xgx1WfICICJkq1YmbAeb3Emq2xjQ7YuB24o_JjiGefth5BMbuAB2&lsparams=mh%2Cmm%2Cmn%2Cms%2Cmv%2Cmvi%2Cpl%2Cinitcwndbps&lsig=AG3C_xAwRgIhALa9KNHE1BmiO2AIXzJAFsfezX6gVkG0XXObSxIyF-qiAiEArU7sXUvXhGTTnETS3gWMb5JmWyZKhFcz4x0UvOzDutI%3D"
[debug] File locking is not supported. Proceeding without locking
[download] Destination: Overwatch 2： Fight the Invasion Trailer ｜ The Null Sector Threat [p9k-nb5w1OU].f303.webm
[download] 100% of   27.90MiB in 00:00:13 at 2.09MiB/s
[debug] Invoking http downloader on "https://rr4---sn-a5mlrnll.googlevideo.com/videoplayback?expire=1691525729&ei=AU7SZNPHD-CKsfIP9O-i-AY&ip=<IP_ADDRESS>&id=o-AAos0j3XcJPg5o8OBFTlq09FkorL9eTcrzO0HIucF_2Z&itag=251&source=youtube&requiressl=yes&mh=xc&mm=31%2C29&mn=sn-a5mlrnll%2Csn-a5meknd6&ms=au%2Crdu&mv=m&mvi=4&pl=23&initcwndbps=9870000&spc=UWF9f91eW1Q4Q7-HkLrv54zFd8ukn_U&vprv=1&svpuc=1&mime=audio%2Fwebm&gir=yes&clen=1344506&dur=89.981&lmt=1691248528166359&mt=1691503792&fvip=2&keepalive=yes&fexp=24007246%2C24362686%2C24363392&beids=24350018&c=ANDROID&txp=5532434&sparams=expire%2Cei%2Cip%2Cid%2Citag%2Csource%2Crequiressl%2Cspc%2Cvprv%2Csvpuc%2Cmime%2Cgir%2Cclen%2Cdur%2Clmt&sig=AOq0QJ8wRAIgIrCPI71M9FCmJr51VsoEwHGhXN9eJOzt1KEAhhVcukYCIE5-CYrDUZyEoXLclY7Ddcp3lYLW5QJftPEscbYj68xr&lsparams=mh%2Cmm%2Cmn%2Cms%2Cmv%2Cmvi%2Cpl%2Cinitcwndbps&lsig=AG3C_xAwRAIgQqbIpqVHLz2C7Nd_DIfWhPYzV_oFHbeg6T4M00kpTGgCIEKLgMy96CYmoSds4GxKVBrPd8rYQJ617ktjE6tJOfp_"

ERROR: Interrupted by user

Issue 1:
format 303 should display `downloading https information'

Downloading m3u8 information is displayed because the formats are still being extracted. yt-dlp cannot know which formats are available without doing this. This is before any actual downloading begins

(what I remember the older version before 20230306 did), but now the output is

It never did this. However, the downloading m3u8 information message is new, since now iOS formats are extracted by default as of version 2023.06.22

Issue 2:
617 mp4   1920x1080   60    │ ~ 52.07MiB from the [info] Available formats for p9k-nb5w1OU:
I know it's unable to predict precisely, but this usually report twice large as the real size and which is ~28MB the same as 303 in this case.
haven't read the code, but maybe this can be improved?

It cannot, because the information provided by youtube is unreliable. Youtube reports the maximum bitrate instead of the average bitrate of HLS streams, and approximate filesize is calculated from bitrate * duration. See https://github.com/yt-dlp/yt-dlp/issues/7255#issuecomment-1581413750

Issue 3:

version 2023.03.04 converted youtube's https formats to a pseudo-dash format in order to circumvent a speed-throttling measure that Youtube had in place. That restriction no longer exists, so the behavior was reverted in version 2023.06.22. If you prefer the "dashy" formats that 2023.03.04 used instead of the direct https formats, you can pass --extractor-args "youtube:formats=dashy"

Downloading m3u8 information is displayed because the formats are still being extracted. yt-dlp cannot know which formats are available without doing this. This is before any actual downloading begins

right, I found that afterward.
But maybe 'downloading m3u8' is confusing, since the context is 'downloading web, ios, android', and looks not related 'm3u8'.

It cannot, because the information provided by youtube is unreliable. Youtube reports the maximum bitrate instead of the average bitrate of HLS streams, and approximate filesize is calculated from bitrate * duration. See https://github.com/yt-dlp/yt-dlp/issues/7255#issuecomment-1581413750

By checking a few other urls, it seems the predicted size is not close to the real size.
Since the fragments in m3u8 should be usually same size file, have anyone tested how 'single fragment size' * 'fragment count' accurate is?

version 2023.03.04 converted youtube's https formats to a pseudo-dash format in order to circumvent a speed-throttling measure that Youtube had in place. That restriction no longer exists, so the behavior was reverted in version 2023.06.22. If you prefer the "dashy" formats that 2023.03.04 used instead of the direct https formats, you can pass --extractor-args "youtube:formats=dashy"

no, didn't mean prefer the downloading the http via fragment way with 'range' http head after 20230304 version.
It means by observing the speed, it looks like still use that way to download http. but I checked the code and it looks like it does revert to the way of version before 20230304.
So it's that just want to ask if anyone can reproduce that issue 3 of the op.

I think Downloading m3u8information is descriptive enough. It doesn't say it's downloading video/audio/etc

right. but the m3u8 is from one of web/android/ios player, and no other source to get the m3u8 url right?

Youtube does not provide single fragment size. It provides (inaccurate) bitrate and duration, which are used to calculate approx filesize

we can use head of http to get the response size.

It still downloads in 10M chunks, because youtube throttles downloads of any chunk sizes larger than that. This behavior existed before version 2023.03.04

in https://github.com/yt-dlp/yt-dlp/issues/6400#issuecomment-1477819819 mentioned in op, the https://github.com/yt-dlp/yt-dlp/issues/6400#issuecomment-1455142084 and https://github.com/yt-dlp/yt-dlp/issues/6400#issuecomment-1455363960 said that it don't need to limit to 10M, and https://github.com/yt-dlp/yt-dlp/issues/6400#issuecomment-1477819819 said reverted.
if so (i.e. used url+&range=0-clen), how could it still have 10M limit? And I dont think it exists before version 20230304 because I remember no speed drop observed during downloading before.

the m3u8 is from one of web/android/ios player, and no other source to get the m3u8 url right?

Yes, but I still don't see the point. If you run the command with -vF you can already see which client the m3u8 formats are sourced from

we can use head of http to get the response size of one of the m3u8 fragments.

This would create more overhead and it would still be inaccurate, since fragment size can vary

in https://github.com/yt-dlp/yt-dlp/issues/6400#issuecomment-1477819819 mentioned in op, the https://github.com/yt-dlp/yt-dlp/issues/6400#issuecomment-1455142084 and https://github.com/yt-dlp/yt-dlp/issues/6400#issuecomment-1455363960 said that it don't need to limit to 10M, and https://github.com/yt-dlp/yt-dlp/issues/6400#issuecomment-1477819819 said reverted.
if so (i.e. used url+&range=0-clen), how could it still have 10M limit? And I dont think it exists before version 20230304 because I remember no speed drop observed during downloading before.

It has existed since 2018: https://github.com/yt-dlp/yt-dlp/commit/e4a60912b8345536387ae14d0d0611eb0b82c23a

Yes, but I still don't see the point. If you run the command with -vF you can already see which client the m3u8 formats are sourced from

It means that it can add details from [youtube] p9k-nb5w1OU: Downloading m3u8 information to [youtube] p9k-nb5w1OU: Downloading m3u8 information of web or android or ios player

This would create more overhead and it would still be inaccurate, since fragment size can vary

yes.
but the fragments are usually equal in size (this can be tested if this idea looks also cool to other users).
for -F, a head should have only few overhead, for downloading, it can automatically get the size of the first fragment.

It has existed since 2018: https://github.com/yt-dlp/yt-dlp/commit/e4a60912b8345536387ae14d0d0611eb0b82c23a

What I tallked above is this commit https://github.com/yt-dlp/yt-dlp/commit/5038f6d713303e0967d002216e7a88652401c22a of version 20230303.
But that 2018 commit you quoted is also true and that code seems to exist in the current version 20230706.
So are both commits resulting the same except just with different downloaders, one http.py and one dash.py?
Is there an easy way to verify range=0-clen for better speed?

Is there an easy way to verify range=0-clen for better speed?

It would get the download throttled for any stream at has a content-length larger than 10MiB, so it would actually make it significantly slower.

It would get the download throttled for any stream that has a content-length larger than 10MiB, so it would actually make it significantly slower.

ok, then issue 3 is solved.
I'm leaving this issue open for unsolved issue 1 and 2

It means that it can add details from [youtube] p9k-nb5w1OU: Downloading m3u8 information to [youtube] p9k-nb5w1OU: Downloading m3u8 information of web or android or ios player

I think Downloading m3u8information is descriptive enough.

agree with bashonly

for -F, a head should have only few overhead, for downloading, it can automatically get the size of the first fragment.

No, the overhead would be quite large, similar to --check-all-formats. There's already a feature request open to support this with a new switch

No, the overhead would be quite large, similar to --check-all-formats. There's already a feature request open to support this with the switch

For -F, the "predicted filesize" by peak bitrate*duration is 2 times larger than the actual filesize usually from my test. from experience, the avg bitrate should be 30%~60% of the peak depending on the source (raw bluray or screen record or webdl).
For the in downloading progress "predicted filesize", it can use the first fragment size of m3u8 * amount for better prediction I think. (at least, often better than peak bitrate * duration)


Update netty-codec-http, ... to 4.1.107.Final

About this PR
📦 Updates

io.netty:netty-codec-http
io.netty:netty-handler-proxy
io.netty:netty-transport-native-epoll
io.netty:netty-transport-native-kqueue

from 4.1.87.Final to 4.1.107.Final
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "io.netty" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "io.netty" }
}]

labels: library-update, commit-count:1

Superseded by #134.


Switch to R24 to avoid dialyzer regression

Why?
See https://github.com/erlang/otp/issues/6935.
Since we power-use dialyzer and plan to extend Uptight.Result.t() with a type parameter too (btw, there needs to be an issue for that), we need to stay on R24 for the time being.
What?

[x] Enumerate all the projects that use goo-lang.
[x] witchcraft-goo, type_class-goo, cognivore/type_nest, something else?..
[x] Merge this PR
[ ] For each of the enumerated projects, check that flake.nix uses the correct version of the expression

type_class done.

Are you trying to layer static typing on top of Elixir here? If so, I strongly recommend doing it yourself instead of relying on dialyzer.
The crux of it is that dialyzer is fundamentally incapable of handling "types" as most people understand them: they are nothing more than value spaces as far as dialyzer is concerned. For example, it cannot distinguish an empty list of atoms from an empty list of integers, because both are merely the value [] which is a subset of both "list of atoms" and "list of integers."
Similarly, with -type foo() :: integer() and -type bar() :: 0. you're free to pass any foo() where bar() is expected and vice versa, because the value spaces overlap and dialyzer doesn't have a clue which of the "types" you mean: the value 0 can be found in both!
Put differently, the value 0 has no type in the traditional sense. It happens to be present in the set integer(), but that does not mean it's an integer per se: it is nothing more than the value 0. We cannot tell it apart from the user id 0 or similar.
Opaques were an attempt to shoehorn classical types into that framework. They may appear to work for the most part, but they're broken in subtle ways that would take ages to explain. Needless to say I recommend avoiding them.

@jhogberg thank you so much for your comment, it's highly appreciated.
I've learned about dialyzer back some ten years ago and I do remember

The big idea behind how it works (I've re-read the PDF the other day too!).
Most of its gotchas.

I use opaques if and only if I can manually test that all the use-cases of an opaque.
In general, I want to say that I don't rely on dialyzer in the same way I would rely on an actual type system.
When I say "power-use", I mean that sometimes we use opaques to get an indication of a library API misuse and we use parametric types.
When I say

extend Uptight.Result.t() with a type parameter too

I mean that we currently have a rather silly situation, when we use a result data structure, which can and should be parametric, but isn't. I'm pretty sure that, based on the stuff here, I should be able to get this to work.

BTW, I'm not sure if you have seen purerl, @jhogberg.
But in case you haven't, check it out. If we wanted to contribute to type system on top of BEAM, we would've put our money there.

Alright, glad to hear you're on top of it. :-)


ReSummarization Tab Error

Are You on the Latest version?
You did a git pull and are running the latest version/build?
Y/ Docker version CPU only
Please describe the bug
When running resummarization on content, I encounter an error within the Results:
"Error during database update: Error updating content: Error creating document version: database is locked"
Is the bug reproducible reliably?
Yes
Steps to to reproduce the issue
Steps to reproduce the behavior:

Go to 'Re-summarize tab search for an item'
Click on 'Re-Summarize'
See error after contect processes

What was the expected behavior?
Content to be summarized
Screenshots
If applicable, please add screenshots to help explain your problem.

Desktop (please complete the following information):

OS: Fedora 40
Browser :Firefox
Date you performed the last git pull: Sept 144

Any Additional context
Please add any other context about the problem here. Thank you!

Solved.


Final AA S3 link - COUNTRY=zimbabwe

Description

Updated the S3 link to a stable one
Fixed typo for MountDarwin -> Mount Darwin in the boundary files. (@wadhwamatic can you make sure the next boundary exports do not override this fix?)

How to test the feature:

[ ]
[ ]

Checklist - did you ...

Test your changes with

[ ] REACT_APP_COUNTRY=rbd yarn start
[ ] REACT_APP_COUNTRY=cambodia yarn start
[ ] REACT_APP_COUNTRY=mozambique yarn start
[ ] Add / update necessary tests?
[ ] Add / update outdated documentation?

Screenshot/video of feature:

Fixed typo for MountDarwin -> Mount Darwin in the boundary files. (@wadhwamatic can you make sure the next boundary exports do not override this fix?)

@ericboucher - will do


[Part 3] Increase Microsoft.Bot.Schema.Teams code coverage

Fixes #5639

Description
Part 3 of 8.
Write unit tests to bring Microsoft.Bot.Schema.Teams to 100% code coverage 🎊🥳🎉

Original Microsoft.Bot.Schema.Teams Coverage: 6.23%

Coverage Raised to with this Chunk: 16.54%

Pull Request Test Coverage Report for Build 250662

0 of 0   changed or added relevant lines in 0 files are covered.
9 unchanged lines in 5 files lost coverage.
Overall coverage decreased (-0.04%) to 78.853%

Files with Coverage Reduction
New Missed Lines
%

/libraries/Microsoft.Bot.Builder/DelegatingTurnContext.cs
1
88.24%

/libraries/Microsoft.Bot.Builder.Dialogs.Adaptive/Recognizers/EntityRecognizers/TextEntityRecognizer.cs
1
85.71%

/libraries/Microsoft.Bot.Builder.Dialogs/Prompts/DatetimePrompt.cs
1
77.5%

/libraries/Microsoft.Bot.Builder/Adapters/TestFlow.cs
2
78.32%

/libraries/Microsoft.Bot.Builder.Dialogs/Memory/DialogStateManager.cs
4
78.76%

Totals

Change from base Build 250626:
-0.04%

Covered Lines:
18155

Relevant Lines:
23024

💛  - Coveralls


Evaluate composability opportunities

Review the top 10 components for composaibility.

Reference the Aitable metrics from Oct or just look at telemetry
Determine if any of the top components need to be more composable

Collaborate with devs for recommendations on composability

Consider:

level of composability
level of effort to make it more composable
how much the component is used
these will help inform us the priority of each component

Create issues based on findings

Telemetry as of 11/14/24

-Tearsheet-
-Create Tearsheet-
Notifications (double check, individual notifications or panel?)
Side panel
Coachmark
Interstitial
API Key modal
Export
Options tile
Tag set


jenkins: 2.89.4 -> 2.107.3

Motivation for this change
Update to latest LTS release.
Things done

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

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

[x] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

NOTE: This also contains several critical security fixes. See https://jenkins.io/changelog-stable/

@GrahamcOfBorg build jenkins

Success on x86_64-linux (full log)
Attempted: jenkins
Partial log (click to expand)
  /nix/store/g0ykbvfbqfvyw12bskvc5kwimq732846-jenkins-2.107.3.drv
building '/nix/store/02pfiaf9si48cxzsvmj6lrh6800akp6n-jenkins.war.drv'...

trying http://mirrors.jenkins.io/war-stable/2.107.3/jenkins.war
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   252  100   252    0     0    878      0 --:--:-- --:--:-- --:--:--   878
100 71.1M  100 71.1M    0     0  5514k      0  0:00:13  0:00:13 --:--:-- 6432k
building '/nix/store/g0ykbvfbqfvyw12bskvc5kwimq732846-jenkins-2.107.3.drv'...
/nix/store/71qvcipicadk2rkrh1i2252h77lq08km-jenkins-2.107.3

Success on x86_64-darwin (full log)
Attempted: jenkins
Partial log (click to expand)
  /nix/store/9kl5g909qb7fbaj0xnpzwr9rckmcl2hl-jenkins-2.107.3.drv
building '/nix/store/99ypwkql560wlpvkg6zz7grl4kg20kax-jenkins.war.drv'...

trying http://mirrors.jenkins.io/war-stable/2.107.3/jenkins.war
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   252  100   252    0     0   1292      0 --:--:-- --:--:-- --:--:--  1292
100 71.1M  100 71.1M    0     0  12.9M      0  0:00:05  0:00:05 --:--:-- 14.0M
building '/nix/store/9kl5g909qb7fbaj0xnpzwr9rckmcl2hl-jenkins-2.107.3.drv'...
/nix/store/lpn7msk0b8bd67s6zf5j7i6l4dq5kw0a-jenkins-2.107.3

Success on aarch64-linux (full log)
Attempted: jenkins
Partial log (click to expand)
  /nix/store/7li6dipfaz6srj0r4wp3xlnkr3cj7c6b-jenkins-2.107.3.drv
building '/nix/store/xs7bsfapr18k3wpbzk3alfzacdyp6b4h-jenkins.war.drv'...

trying http://mirrors.jenkins.io/war-stable/2.107.3/jenkins.war
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   252  100   252    0     0     95      0  0:00:02  0:00:02 --:--:--    95
100 71.1M  100 71.1M    0     0  9700k      0  0:00:07  0:00:07 --:--:-- 13.9M
building '/nix/store/7li6dipfaz6srj0r4wp3xlnkr3cj7c6b-jenkins-2.107.3.drv'...
/nix/store/bqm7xwp0vndlv4rns5kszh31md5my5ik-jenkins-2.107.3

@grahamcofborg test jenkins

No attempt on aarch64-linux (full log)
The following builds were skipped because they don't evaluate on aarch64-linux: tests.jenkins
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnfree = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnfree = true; }
to ~/.config/nixpkgs/config.nix.


Differences between CPU and GPU implementations

Hey,
Thanks for providing this great implementation of the UKF. I notice that there are some significant differences between the CPU and GPU implementations. The two main ones that I noticed are that in the CPU implementation, the sigma points are only generated once as opposed to the generation at each iteration for the measurement of sigma points in the GPU node.  The second is the missing Process noise covariance Q in the CPU implementation.
Just trying to understand the differences between the two implementations.

Hi,
Sorry for the late response, I was developing the CPU to build the framework it is not an exact copy of the GPU version. The idea why I added the CPU version was for others to do some development and testing before implementing their own GPU versions. Think of it as more of an sandbox to play around with.
If I do get time to work on this, I will match both the CPU and GPU implementations.
Regards


Diff Preview Against Current File

Is it possible to show the diff against the current file rather than smaller diffs against the previous state?
If I'm looking back at a file that has many changes, I'd like to be able to see all of the changes between the previous state and the current state to better understand what I'd be undoing. I understand that might have greater costs to performance given a large undo history so maybe this could be a mapping to telescope that opens vimdiff against the changeset to preview all changes in full.

I like the idea!
What telescope-undo does is basically calling undo on the real buffer and calculating a diff between each u call in between. When done, it restores to a given change ID that sits on top of the list, i.e. the current state. This means the performance will only be different by the additional diffs themselves.
However, each entry has the sequence number of the undo state attached, so calculating the "total diff" on-demand would be a single undo to that state (as <cr> does), calculate the diff, and switch the preview.
How would you envision the UX for that? The current "change diff" as a default, and a binding to switch the preview over to a "total diff"? I don't think it's possible to have two previews 😅 But I'm also not quite sold on this being a feature of the main telescope-undo telescope... maybe you're right and this should indeed be another telescope (offered by this plugin), but that would limit the ability to go back to the original view 🤔
What are your thoughts on this? I think a config switch for what to show ("change diff", "total diff", both??) is definitely doable, but I guess there's a way to integrate this nicely. I don't like that the "total diff mode" makes the yank addition/deletion completely useless 😅 Am I guessing correctly that your need for this is mostly for undoing changes, not yanking them out of a previous state?

Oh, and the obligatory: If you're motivated to work on this I'm happy to help you out and answer any questions, but I'll get to doing it myself in time I assume 🦥

I got around to implementing this, feel free to test it out and let me know your thoughts. It's available on branch feat/compare_to_current (here, comes with some docs in the README).
I played around with it for a bit and to be honest can't make much sense of it. Yanking is next to useless, and restoring states feels somehow not very intuitive... Not sure if the diff should be the other way around? Anyhow, let me know and test this, if you (or anyone) sees value in it I'll put it to main 👍🏻
Using require("telescope").extensions.undo.undo({compare_to_current=true}) to invoke for testing is the most convenient, probably ;)

Thanks for the work on this feature! But, I think you're right, it's a bit difficult to understand the diff being presented. It doesn't seem to be aggregating the changes from each undo point to reconstruct the old version of the file for comparison. It looks like it's showing the diff between each undo point against the current file, which gets pretty hard to decipher the further back in history I go.
I based this functionality from the timeline view used in VSCode. The way it seems to work is by saving the entire buffer after each change such that when you view the diff you're actually viewing the diff between the old and new version of the file, rather than a single change in history.
Since this plugin calculates diffs based on the undo history, this might be an out-of-scope feature. I would still find it very useful to have this type of view. Is it possible to reconstruct the previous version of a from the undo points that have come before it?
I think another approach would be to save your own versions of the file, but then it wouldn't really be leveraging the Undo History at that point.
I can annotate some screen captures to better explain if you think that might help.

Well that's the weird part, it seems to work for the full diff for a test file, but the diff on a "real" history looks to weird to be the aggregation of it. If you can provide a small normal mode string (i.e. ifoo<esc>obar<esc>obaz<esc> works alright) which creates a bad diff you'd boost my efforts quite considerably, as I'm really unclear on what's happening...
Regarding undo states in vim, each state has a clear parent, and vim can restore to any state. I.e. you can use the the number from telescope-undo to run :undo 42 to restore the buffer to after that state (post diff). You'll also be able to go to the latest state this way.
The way I implemented this first version is grabbing the buffer on execute and substituting that for the "child".

I use this to look at the difference between the unsaved buffer and the previous saved one.
local filetype = vim.api.nvim_buf_get_option(0, "filetype")
  vim.cmd("tab split | diffthis")
  vim.cmd("aboveleft vnew | r # | normal! 1Gdd")
  vim.cmd("diffthis")
  vim.cmd("setlocal bt=nofile bh=wipe nobl noswf ro ft=" .. filetype)
  vim.cmd("wincmd l")

Maybe it is about somehow comparing the different write event in the buffer that could help at a high level.

This might have been looking so very weird because of #50. I'll look into it once I'm confident to put the fix for that onto main 👍🏻

I've rebased the above mentioned branch with the proof of concept onto that recent fix, and now it looks like it's working 🎉 I'm still not sure whether it's very useful though, can you guys try it out and let me know whether that's what you'd expect?


=kill kraken, but no king goldemar or Malygos

So I noticed as we're all sitting in bso doing the patreon kill command. =kill 500 kraken works, ofc no working emojis lol np.
But when I try to do =kill 500 king goldemar I get the response "I don't have that monster!"
I've also tried =kill 500 king, =kill 500 goldemar.  Nothing.
Is it possible king goldemar was forgotten when you added kraken to kill simulations? Lol
& Malygos is still a new addition but I'd like to request that be added also. Thanks 😊

You can close this

JerMous3 kindly let me know
Thanks


Add MIT License

@handav Is there anything in this repo that might be incompatible with MIT License in terms of the data work you are producing? I am assuming the various python scripts that are adapted from other tensorflow examples can be MIT.


Intalling error on Ubuntu 20.04.2 TLS

I'm seeing issues when installing through:
sudo remnux install
Distributor ID: Ubuntu
Description: Ubuntu 20.04.2 LTS
Release: 20.04
Codename: focal
saltstack.log

Looks like an issue installing ViperMonkey. We'll look into it. The other tools installed successfully, though.

Fixed by @digitalsleuth in https://github.com/REMnux/salt-states/pull/183


feat(footer): add version number

There were the following issues with your Pull Request

Commit: 1a1c51272cef9e7c39e6dde54f2c7f8599933296
Your commit message does not contain a body

Guidelines are available at https://github.com/fabric8io/fabric8-ui

This message was auto-generated by https://gitcop.com

DO NOT MERGE YET