Update stable version in repo from 0.10.0 to 0.10.2

Think about update stable version to 0.10.2
Version: stable=0.10.0 (119 days old) => latest=0.10.2 (38 days old)
Installs: stable=735 (58.57%), latest=134 (10.68%), total=1255
Click to edit

ping

A kind reminder.
Is there any reason to delay an update of stable revision?
Feel free to drop a simple note if I should trigger an update.


Why there is only ad impression for banner ads? I need impression for interstitial :(

PR are welcome
https://stackoverflow.com/a/62788746/1255819

@hakanihat
Not sure I'm understanding this at all. I've been using this plugin with interstitial ads for over a year and impressions are definitely being recorded.


how to create the zip file

The page says "When you are developing on a local computer, it's easy to create a .zip file of the function app project folder on your development computer." but it will be helpful if you mention on how to do that or point to a document explaining on how to properly create the zip file.

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

ID: 4581be64-415a-804a-0a45-25b6976095c3
Version Independent ID: 0cae0e82-c263-e2cf-ea54-a783291f5746
Content: Zip push deployment for Azure Functions
Content Source: articles/azure-functions/deployment-zip-push.md
Service: azure-functions
GitHub Login: @ggailey777
Microsoft Alias: glenga

@hpourreza thanks for providing this feedback. I agree that this needs to be clarified. All of the tools that support local development and publishing for Azure Functions (Visual Studio Code, Visual Studio, and Core Tools) support .zip publishing.
You could also just create a .zip of the project folder, which is a step performed by most publishing pipelines.

#assign:ggailey777

Addressed this feedback in the related PR. #please-close


Discussion: Opportunities for cleaner IL generation

I have played around a bit with F# and decompilers, and in many cases F# generates complicated IL.
e.g.
this
let sample1() =
    use fs = File.Create("x.txt")
    fs.WriteByte(byte 1)

compiles to
.method public static
    void sample1 () cil managed
{
    // Method begins at RVA 0x2050
    // Code size 48 (0x30)
    .maxstack 4
    .locals init (
        [0] class [mscorlib]System.IO.FileStream fs,
        [1] class [FSharp.Core]Microsoft.FSharp.Core.Unit,
        [2] class [mscorlib]System.IDisposable
    )

    IL_0000: nop
    IL_0001: ldstr "x.txt"
    IL_0006: call class [mscorlib]System.IO.FileStream [mscorlib]System.IO.File::Create(string)
    IL_000b: stloc.0
    .try
    {
        IL_000c: ldloc.0
        IL_000d: ldc.i4.1
        IL_000e: callvirt instance void [mscorlib]System.IO.Stream::WriteByte(uint8)
        IL_0013: ldnull
        IL_0014: stloc.1
        IL_0015: leave.s IL_002d
    } // end .try
    finally
    {
        IL_0017: ldloc.0
        IL_0018: isinst [mscorlib]System.IDisposable
        IL_001d: stloc.2
        IL_001e: ldloc.2
        IL_001f: brfalse.s IL_002a

        IL_0021: ldloc.2
        IL_0022: callvirt instance void [mscorlib]System.IDisposable::Dispose()
        IL_0027: ldnull
        IL_0028: pop
        IL_0029: endfinally

        IL_002a: ldnull
        IL_002b: pop
        IL_002c: endfinally
    } // end handler

    IL_002d: ldloc.1
    IL_002e: pop
    IL_002f: ret
} // end of method Program::sample1

Edit:
Opportunities in this this simple program

[ ]  ldnull/pop pairs
[ ] typecheck for IDisposable
[ ] second endfinally in try-finally
[ ] ldloc/pop @IL_002d

All these would reduce the size of the method from 0x2f (47) to less than 32 instructions.
32 instructions is the magic upper limit for inlining.

Some ideas, speaking as an observer:
All of these could definitely be optimized away:
ldnull
pop

That's what RyuJIT does so it has no performance impact, still looks strange in the IL though.
I don't understand the purpose of:
isinst [mscorlib]System.IDisposable

Since it's a compilation error to have a "use" binding with something that's not IDisposable. Candidate for removal too?
It's also unfortunate that 2 endfinally instructions are generated (along with their useless ldnull pop preludes), one extra for the false branch of the null check on fs, instead of converging both branches on the same instruction.
See also https://github.com/Microsoft/visualfsharp/issues/635

Yeah, I guess it could be simplified to
.method public static
void sample1 () cil managed
{
// Method begins at RVA 0x2050
// Code size 48 (0x30)
.maxstack 4
.locals init (
[0] class [mscorlib]System.IO.FileStream fs
)
IL_0001: ldstr "x.txt"
IL_0006: call class [mscorlib]System.IO.FileStream [mscorlib]System.IO.File::Create(string)
IL_000b: stloc.0
.try
{
    IL_000c: ldloc.0
    IL_000d: ldc.i4.1
    IL_000e: callvirt instance void [mscorlib]System.IO.Stream::WriteByte(uint8)
    IL_0015: leave.s IL_002d
} // end .try
finally
{
    IL_0017: ldloc.0
    IL_001f: brfalse.s IL_002a
    IL_0017: ldloc.0
    IL_0022: callvirt instance void [mscorlib]System.IDisposable::Dispose()
    IL_002c: endfinally
} // end handler
IL_002f: ret

} // end of method Program::sample1
This wasn't meant to be exhaustive, there ary other cases where the IL is a bit 'longwinded'.

@0x53A @asik Yes, in short we would accept high quality, well-tested PRs to improve the IL generated if there's some evidence it improves perf.
That said, things like removing the extra "endfinally" is unlikely to improve perf in any mainline case we care about, and it's likely we would judge that the churn-risk associated with making the change may be too great.  For example, a bug was injected into F# 4.0 because we accepted an optimization PR that looked ok at code review but actually applied the optimization in invalid situations.  It's very expensive to hot-fix such bugs after they creep into shipping versions of F#.
If you do delve into this, I expect most changes would be in IlxGen.fs.  There is a fair bit of apparatus there already to simplify generated IL.
I'll close this because we don't track IL improvement suggestions individually via github issues unless matched by a PR. Though we certainly welcome PRs! :)
Best
don

Closing - see above comment

@dsyme  Ok thanks for the feedback.
I do think there would be some gain by clarified IL, but as you mentioned, that is more than offset by the risk.
If I find ( and am able to fix ) anything that affects performance in a noticeable way, I will send a pr.

Great!
I'm converting this thread to what can be a long-running discussion about IL cleanliness (or we could use #635)
The tradeoff is also with the complexity of the change.  Clean IL is definitely a virtue :)  If you find simple ways to remove ldnull/pop pairs, for example, that would be good:  Even if you isolate the paths in IlxGen.fs where the ldnull is being generated but not eliminated, that would be useful.
Also, ways to avoid the use of locals is very welcome since I believe some of the JIT optimizers use the number of locals in a target method as a decision about whether to inline or not. But locals in exception handling are less important - F# try/catch and try/finally have result values, unlike C#, so it's not to osurprising we use some extra locals for those.

@dsyme
How about removing some of the "unbox.any" instructions? These appear quite costly if you are using interfaces a bit (In production code, when I have been optimizing inner loops, I have manually coded around it.)
I would submit a PR for this, but there is a comment in the GenCoerce function that unbox.any is important in "stack merge points" (which I must confess my ignorance about).
Anyway, here is an example of performance issue:
let empty (a:seq<'a>) =
    not ((a.GetEnumerator ()).MoveNext ())

[<EntryPoint>]
let main _ =
    let r = ResizeArray ()

    let sw = System.Diagnostics.Stopwatch.StartNew ()
    let s : seq<_> = upcast r
    let mutable counter = 0
    for i = 0 to 10000000 do
        if empty s then
            counter <- counter + 1
    System.Console.WriteLine ("cast to seq: {0} ({1})", sw.ElapsedMilliseconds, counter)

    let sw = System.Diagnostics.Stopwatch.StartNew ()
    let mutable counter = 0
    for i = 0 to 10000000 do
        if empty r then
            counter <- counter + 1
    System.Console.WriteLine ("as ResizeArray: {0} ({1})", sw.ElapsedMilliseconds, counter)

    0

With output of
cast to seq: 263 (10000001)
as ResizeArray: 1421 (10000001)

If I modify the fsharp compiler to remove the unbox.any then I get
cast to seq: 210 (10000001)
as ResizeArray: 209 (10000001)

This modified compiler passes all the standard .\appveyor-build.cmd tests, so I'm not sure what cases the comment is referring to, so some guidance would be appreciated.

@manofstick that's a nice cleanup, with perf too, good work!.
Maybe it's better to open a pr to discuss and validate the changes? pr are free :smile: , just add ref to this issue in the pr, it's not more work than discuss there
@manofstick appveyor-build.cmd ( without args ) runs only the smoke tests, not the full suites. You can run appveyor-build.cmd all to run the full suites, or follow instruction in readme about tests. I'll update docs.
from @dsyme comment:

I'll close this because we don't track IL improvement suggestions individually via github issues unless matched by a PR. Though we certainly welcome PRs! :)

i think that's a good requirement because a single issue (like this one) can become noise with multiple parallel discussion. Also the pr can show the code diff, can be commented and the discussion is separated from others, you can add your per test inside a the commit. and it's easy to clone a pr ( 'hub checkout https://github.com/Microsoft/visualfsharp/pull/872` )

Closing old discussion, and the work to remove unbox.any was already merged


Resolve sync only after heads have been added

This is required for a tentative solution to https://github.com/orbitdb/orbit-db/issues/509:
https://github.com/orbitdb/orbit-db/pull/514
See this commit message for a more detailed explanation.

@chmanie Thank you for the clarification. Can you and @tyleryasaka work to get the event listeners cleaned up?

So basically just removing the event listeners before resolving the promise? @chmanie

Friendly ping on this thread @chmanie @oed

So basically just removing the event listeners before resolving the promise

Yeah, that should do.

@tyleryasaka Would you be able to remove those event listeners? If so then we can merge this and the commensurate PR in orbit-db


Ambient sounds are inaudible when connecting to a server through the launcher, but audible locally

Description

hell issue
client configs are identical, ambience cvars are identical, volume settings etc are all identical
locally sounds are still audible even in release vs debug, when connecting with a new client
showambient overlays are identical for local vs launcher
launcher connected servers have inaudible ambience regardless of map, playercount, ghost status, etc
Reproduction

set ambience volume and max sources to max
start a local server and client on box, aghost around and see that you can hear lots of stuff
join the same server through the launcher by direct connecting to localhost, aghost around and see that you cant hear jack shit
join a live server through the launcher as well and see that you cant hear jack shit

Screenshots

Additional context

genuinely think i was hallucinating or something


Dynamic Task configuration

Currently Turbinia runs with a mostly static configuration, and so we run the same set of Tasks and the same set of arguments for those Tasks.  We would like to be able to change the behavior of a given Turbinia run by passing this kind of data in as a recipe.  This would allow us to specify more targeted processing and analysis for various scenarios.   This issue is to track the "dynamic task configuration" part of this, and #26 will track the Recipe side.
Some notes:
For dynamic task configuration, tasks will define the configuration options that it can use at run time.  This is just a flat dict of options set in the Task object code.  Only the options found there can be configured dynamically by users.  The values set in config will be the defaults that are used by the Task when no overriding config is specified.
Additionally, these options can also be used to dynamically generate command line option flags so users can specify those when making Turbinia requests.

This is done and documentation can be found here: https://turbinia.readthedocs.io/en/latest/user/recipes.html


Improved: Size of Products in bestsellers section (#382-bestseller-products-size)

Removed the CSS properties which were forcing some section with class 'section' (Bestseller section and share your look section) on home page, to have padding on mobile view, which cause less space for them to occupy.
Also these properties were making these section shrink and not in align with other sections of home page.
Related Issues

#382
Closes #382
Short Description and Why It's Useful

As mentioned in the issue, size of bestseller carousel was smaller in comparison to other carousels.
On debugging, I found that .section class have padding on mobile devices, this class was added on #shareyourlook and #bestseller section, and causing them to shrink more in the mobile devices.
Due to which size of bestseller carousel was smaller in comparison to other carousels.
Screenshots of Visual Changes before/after (If There Are Any)

Before

After

IMPORTANT NOTICE - Remember to update CHANGELOG.md with description of your change
Contribution and Currently Important Rules Acceptance

[X] I read and followed contribution rules

.section {     padding-left: var(--spacer-xl);      padding-right: var(--spacer-xl);      @include for-desktop {          padding-left: 0;          padding-right: 0;      }   }
Some CSS was adding unnecessary padding on the 'bestseller' carousal and 'share your look' section
Removed the two properties, from above mentioned class, which will give proper space to these section, in my above PR.
Also this will align these two section with the width of all other sections of the home page.
Currently, theses section are smaller in width than other sections in the home page.
Thanks!!


Translate site default label.

Do the tests still pass? Y
Does the code comply with the style guide? Y
For Python changes: Have you added tests to cover the new/fixed behaviour? N
For front-end changes: Did you test on all of Wagtail’s supported browsers? N/A
For new features: Has the documentation been updated accordingly? N/A

Looks good to me - thanks @allcaps!


allow cyclic reactors as long as equilibrium is reached

This has been discussed before in #22 and #8
Hopefully this proposed solution is something you can accept.
I'll try to describe the (simplified) use case why we need this:

we have a (client side) atom that defines which graphs (aka data sets) are in memory. This is initialised with an initial set.
we also have queries on this client side data set (aka derivables) that define which data sets should be available on the client
when the query for data sets returns new results, we fetch these graphs/data sets from the server and add these to the atom from the first step (a cyclic reactor)
once we add more data sets to the atom the derivable and reactor might trigger again as more data sets are needed. After 1 or 2 iterations this reaches an equilibrium

There is nothing wrong with the workflow you describe. That is an asynchronous cycle because it involves going away and querying another system like the server in your example. However, even when the query can be done synchronously, for example if you have a local cache, DerivableJS requires that you insert an asynchronous step in there using setImmediate or equivalent. This should be easy to do in all cases.
It might seem like this is required because of implementation details, but in fact it is because synchronous cyclical reactions are dangerous. They allow inconsistency to creep in to the state graph, and I can't let that kind of thing slide, sorry. You've already read my other explanations of this so I won't go into more detail, and I'll have to decline this PR. Thanks for the contribution anyway. It is good to know that people are making use of the library :)


unrecognized Caffe layer type [Reshape]

When I use vitis-ai-caffe to compile my caffe model .
I got a err like:
"[VAI_C][Warning]Only 'SUM' type is supported for Eltwise,current layer is [stem_activation]"
"[VAI_C][Warning]Only 'SUM' type is supported for Eltwise,current layer is [block1a_activation]"
"[VAI_C][Error]unrecognized Caffe layer type [Reshape]"
"[VAI_C][Error]Parsing layer graph failed"
it looks like DPU does not support Reshape and Eltwise layer(except 'SUM'),but it difficults to change "Reshape" layer in my caffe model.
Is there some suggestions for me to avoid this error?
Thanks!

I also encountered the same error with the SSD model.

VITIS_AI Compilation - Xilinx Inc.

[VAI_C][Warning] Only 'channel' axis supported on DPU for Concat, current layer is [mbox_priorbox].
[VAI_C][Error] Unrecognized Caffe layer type [Reshape].
[VAI_C][Error] Parsing layer graph failed.

Hi GithubAbner,
I wonder if you have solved this issue. If not, I will submit this issue to the engineer in charge of it. If it has been resolved, please let me know and I will close this issue.
Note that if we do not receive any reply from you within 2 weeks, we will assume that this issue has been resolved and will close this issue. Thank you.

Hi @GithubAbner and @A1exy ,
Yes, Reshape layer is not supported by the VAI_C, you have to remove Reshape layer from the prototxt and use CPU to process this layer. Hope it useful for you.

Hi @GithubAbner
Since I haven't received your reply for a long time, I will close this issue. If you still have a problem, you can reopen it. Thank you very much.


Window gone transparent after splash screen

From phyo.arkarlwin on 2013-12-03T16:22:54Z
I found one problem with spyder revision 3332 on linux KDE, Whole window transparent! with about 50% transparency after splash screen is finished. Something to do with splash screen opacity effecting whole window i think. I will make a bug report.
Original issue: http://code.google.com/p/spyderlib/issues/detail?id=1664

From ccordoba12 on 2013-12-11T18:01:58Z
I'm preparing a pull request to fix the opacity problem.
Labels: Cat-SpyderGUI MS-v2.3

From phyo.arkarlwin on 2013-12-03T13:26:39Z
Here is how it looks like
Attachment: spyder_transparent.png

From phyo.arkarlwin on 2013-12-03T13:27:10Z
Also spyder window becomes always on top!

From ccordoba12 on 2014-01-02T09:42:01Z
Summary: WIndow gone transparent after splash screen   (was: WIndow gone transparent after splash screen rev #3332)

From ccordoba12 on 2014-01-02T09:39:11Z
This issue was updated by revision 0d1412fa0f88 .
Status: Fixed

From ccordoba12 on 2014-01-02T10:11:05Z
Summary: Window gone transparent after splash screen   (was: WIndow gone transparent after splash screen)


Revert removal of layer size fetch, conditional on size annotation unavailable

Issue #, if available:
fixes #536
Description of changes:
Partial revert of https://github.com/awslabs/soci-snapshotter/commit/86ddfcdb2c521586177bf3c33eed7e7dcb516f86
When setting up newHTTPFetcher, if the descriptor Size is missing (due to the layer size annotation not being available for the layer) then run the previously-removed function to get the size from the remote host.
Testing performed:
Needs new integration test. PR is Draft until then.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Yeah, I just tested and we need to update source.FromDefaultLabels so that it doesn't require source.TargetSizeLabel or source.targetImageLayersSizeLabel. If they're present, we should use them, but if not, we should just set it to 0 and this code will fetch from the remote.
I think we will want to try to get the size labels upstreamed, though, because it adds several round trips to the pull that don't really need to happen.
On the plus side, with this patch + the change listed above + the fix for https://github.com/awslabs/soci-snapshotter/issues/725, I was able to successfully rpull a SOCI-fied image with an unmodified nerdctl: sudo nerdctl pull --snapshotter stargz $IMAGE
I had to pretend it was a stargz snapshotter to get nerdctl to add the remote labels.


[Jewel][DateField] Add ability to disable range of dates

DateField should have available bead which allows user specify min and max range date. Screenshot example from Vuetify where you cannot click on dates above 13 Nov:

Hi Piotr, thanks for adding this.
I can support you on this in the styles/theme side to make it look as close to jewel theme as possible

Thanks! Maybe it will work nicely just out of the box. You can shed some light how is build in HTML cell which holds day in DateChooser. What will happen if I make it disable - does it go gray in a similar way how Button goes when you add Disable bead ?

DateChooser use Table (DateChooserTable) to build the dates. So echa Date is a TableCell. The disabled style is setup at "table level". Right now there's no isolated table cell disabled style. That will need to be done. You can set up a temporal basic style in the Jewel library and as you finish the implementation I can go over there and create the appropiate styling and move the required to Jewel Themes.

@carlosrovira Here is example which contains bead and current state of my implementation. It has Maven pom file, so you should be able to build it. I didn't test it too much - it does block some dates, so something has started to work.
I will have time to back to that at the end of January probably - if you beat me earlier it would be great.
DateChooserExample.zip

@carlosrovira I did look again into that and over the road I see that there is an issue with DateChooser. I was using newest nightly to build TourDeJewel.

Hi Piotr,
Thanks for let me know. Just fixed it. It was caused by a recent update done in ListView where we want to perform the scrollToIndex in all kind of actions but not when we click on items. I extract that so in TableView we don't want to have that functionality.

Hi Piotr,
I added the bead with some updates to Jewel and added as well styles to JewelTheme to allow display the disabled cells.
I think the bead is very close to finish. I see to points to fix:

Fix the enabled/disable for cells since right now is not taking the right ones.
Run the enable/disable code when click on datechooser navigation buttons
I'll continue checking and working on it soon

Hi Piotr, just complete the bead and seems to work ok. Also added an example in TDJ's DateComponentsPlayGround page.

Thank you @carlosrovira for help with that :)

@carlosrovira One of the reason why I have started working on that bead was that I wanted to use it in DateField, instead of DateChooser. DateField using DateChooser - in order to apply that bead to DateField I will extend DateFieldView, but do you think it should be easiest way of adding that beat to DateField ?

Hi @piotrzarzycki21, I think we should be able to do that kind of things without the need to extend DateFieldView. In this case, we can throw an event in that view that signals the popup is created and ready and then create another bead that simply operate listening to that event and adding the new DateChooser bead. So that way for the user the only need will be to add the new bead to the DateField.

@carlosrovira it is still seems to be complicated plus how user provides it’s minDate and maxDate? Event can be helpful. I think user should have an ability to add our Date range bead in mxml and view of date field should handle that.

User should use the new bead in the same way he does in DateChooser providing minDate and maxDate. The new event should be used to hook these values in the popup that we create each time

Hi @piotrzarzycki21 just created the bead. The system used is the same we use in Jewel ComboBox with the same events, take a look. I also added the corresponding example to TDJ.

Hi Piotr, I did more updates to this one:

Now the bead support to set just one of the restriction (min or max date) or both as before
I added code to remove selectionDate if selection was out of the range, but then commented out and left for an extension since I think maybe not all people would want to do this and seems something optional, so better left for other bead. (Note: if the remove selection code is needed to craft another bead I left the lines commented to use it there easily).
Instead, I updated styles so "selected disabled dates" are now colorized correctly.

I think I'm done for now with this extension.

Hi Piotr, I did more updates to this one:

Now the bead support to set just one of the restriction (min or max date) or both as before
I added code to remove selectionDate if selection was out of the range, but then commented out and left for an extension since I think maybe not all people would want to do this and seems something optional, so better left for other bead. (Note: if the remove selection code is needed to craft another bead I left the lines commented to use it there easily).
Instead, I updated styles so "selected disabled dates" are now colorized correctly.

I think I'm done for now with this extension.


Convert any CURIEs to IRIs at the edge of the app

Internally all identifiers should be  IRIs, so that we never have to worry about prefix mapping in app code, like when putting identifiers in SPARQL queries. Right now we have the KGSQueryRequestBody complex type; it models IDs just as strings. We could upgrade this to reference a CURIE type or possibly a CURIEorIRI type (if the spec allows IRI IDs), and reject the message if we can't map the prefixes.

Similarly we should only compact IRIs to CURIEs when rendering the response.

Completed by #97.


Allow multiple linked accounts

This issue is imported from pivotal
It\'ts possible to have multiple accounts linked to your eduID, eq when a user has multiple affiliations at different institutions. At the moment, only one link is shown in the UI.

We should design a UI for managing (viewing, adding, refreshing, ordering and deleting) multiple links.

https://www.pivotaltracker.com/story/show/181773210 (Peter Havekes - Jan 16, 2023)


💄 Clean up shading code

In particular:

Use newer language features where relevant
Replace public readonly fields with auto-properties
Fix some naming of public and protected functions to be capitalised. NB: this is a breaking change

Agreed that these classes need a lot more work, but I feel that goes into the territory of subjectivity and how the library should be structured on a wider level. If you want me to, I am happy to rebuild one of the classes from scratch and you can see whether you like it or not.


changing grammar so that it can parse expect exprs and assignments

Using Martin's make test csv that ranks the parsing errors in order of most-occurring to least-occurring, I found that:

expect(<int>) was unable to be parsed, with 1490 errors
sum = 1 was unable to be parsed, with 1424 errors

As a result, I'm attempting to expand the tree-sitter grammar to parse these.
Test Plan:
Run
npx tree-sitter generate
And
npx tree-sitter test

@colleend shouldn't you make the PR to the original repo?

btw this is the checklist we have on some tree-sitter repos: https://github.com/tree-sitter/tree-sitter-javascript/blob/master/.github/pull_request_template.md
These are the @maxbrunsfeld-approved criteria that make a PR easy to approve.

This is great. Do you have some idea on what %improvment we get with those changes?

I think it would be around a 1-2% improvement from what I calculated -- but haven't run the make-stat tests yet, so can't fully confirm 🤔

btw this is the checklist we have on some tree-sitter repos: https://github.com/tree-sitter/tree-sitter-javascript/blob/master/.github/pull_request_template.md
These are the @maxbrunsfeld-approved criteria that make a PR easy to approve.

Awesome, these are great! Yep, it seemed to me that there wasn't that much activity in the original repo, so I decided to just add the changes here 😅


New package: Dionysos v0.0.1

Registering package: Dionysos
Repository: https://github.com/dionysos-dev/Dionysos.jl
Created by: @adrienbanse
Version: v0.0.1
Commit: 9e9a3a0af48b581686fe95e7b36a778b7aad26a1
Git reference: v0.0.2

@blegat Which licence should I put?

[noblock] The MIT license is the one most commonly used for Julia project, and thus would make your library the most compatible with the rest of the ecosystem

@JuliaRegistrator register()

Close

Close in favor of https://github.com/JuliaRegistries/General/pull/101970


Fix increments

fixes #506
@tjb900
Depends on #511

Codecov Report

Merging #512 into master will increase coverage by 0.08%.
The diff coverage is 96.87%.

@@            Coverage Diff             @@
##           master     #512      +/-   ##
==========================================
+ Coverage   86.48%   86.56%   +0.08%
==========================================
  Files          73       73
  Lines        6297     6321      +24
  Branches     1286     1291       +5
==========================================
+ Hits         5446     5472      +26
+ Misses        674      672       -2
  Partials      177      177

Impacted Files
Coverage Δ

devito/symbolics/manipulation.py
91.79% <100%> (+1.35%)
:arrow_up:

devito/ir/clusters/graph.py
85.9% <92.3%> (+0.48%)
:arrow_up:

devito/types.py
89.63% <0%> (+0.9%)
:arrow_up:

Continue to review full report at Codecov.

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

@ggorman thanks
so Travis was green until this morning; then I rebased the branch on top of latest master and now again Travis is simply running out of time, taking ages to run ...
yes, a test has been added (originally produced by @tjb900 )


Python: use PyPI mirror

Recently PyPI changed their url scheme at https://pypi.python.org. After some complaints they mapped the older urls to the new ones again. This is however done on the upcoming PyPI 2.0 website, and not the current website.
In this PR the new website (https://pypi.io) is added as mirror. The new website works most of the time but can still fail occasionally and is not as reliable as the old one.
cc @domenkozar @wkennington

Travis seems to indicate it's a mass rebuild, I don't understand why. It's changing only fixed output drvs.

Seems like nox is comparing drv paths: https://github.com/madjar/nox/blob/master/nox/nixpkgs_repo.py#L80

Nice catch! Opened https://github.com/madjar/nox/pull/44

I really see no reason to merge this, we'll fix issues as they come or switch to another mirror.

Verified using pythonPackages.msgpack and bumped the version.

My only concern with this is we're now codifying that pypi is the old style pypi URLs. In fact, PyPI has changed their URLs and are only providing these old style redirects as a favor for packagers like us. Given the rest of @FRidh's goals, I think it would be wiser to rename the pypi mirror to pypi-v1 (or whatever) so then we have an easier time moving forward by calling the newer style URLs pypi-v2.

If we keep in mind that this is not an official API and agree that if it turns out to be unreliable and that we need a better solution by using say the API, then I think it is fine.
I will anyway work further on autogenerated urls and hashes using the API.

with the pypi-v1 you have a good point, at least, thinking about people that use it outside of buildPythonPackage.


United Kingdom - 2022 spring bank holiday

In 2022, as we will have the Platinum Jubilee in United Kingdom on the 2022-06-03, it changes the Spring Bank Holiday date to the 2022-06-02
I will try to submit a PR about this

Closing. Resolved in v2.5


Routing does not handle trailing slashes consistently

This may be merely something to add to the docs.
Using a simple application such as the following:
<?php

require_once __DIR__.'/../silex.phar';
use Symfony\Component\HttpFoundation\Response;

$app = new Silex\Application();

$app->get('/', function () use ($app) {
      return new Response('Home root');
});
$app->get('/hello', function () use ($app) {
      return new Response('No trailing slash');
});
$app->get('/hello/', function () use ($app) {
      return new Response('With trailing slash');
});

$app->run();

this is the observed behavior:

http://app/ -> caputured by 'Home' route
http://app/hello -> caputured by 'No trailing slash' route
http://app/hello/ -> caputured by 'With trailing slash' route

However expected behaviour would be that the last route is inaccessible:

http://app/ -> caputured by 'Home' route
http://app/hello -> caputured by 'No trailing slash' route
http://app/hello/ -> caputured by 'No trailing slash' route

If the last route is not defined, the result of requesting /hello/ is "Sorry, the page you are looking for could not be found." - but you'd expect it to match the routefor /hello.
This is testing on an arch linux machine running nginx - though that shouldn't really be much of a factor.

Url ending with / and not ending with slash may canonically not mean the exact same thing, regardless of how you put it.
However, I think that a route with a slash, acting as a fallback to a url without a slash but not the other way round, is indeed plain weird. I would personally opt for a silex-wide setting to disregard any trailing slashes, from the request uri or route.

Also, parameters are not inserted into the url when the defined bound route has no trailing slash defined
  // Route: $ctl->get('/feed/{duration}', array($this, 'feed'))
  $params = array('duration'=>8);
  $feedlink = $this->app['url_generator']->generate('calendarfeed', $params, true);
  // Gives: http://local.dev/calendar/feed

  // Route: (with trailing slash) $ctl->get('/feed/{duration}/', array($this, 'feed'))
  $params = array('duration'=>8);
  $feedlink = $this->app['url_generator']->generate('calendarfeed', $params, true);
  // Gives: http://local.dev/calendar/feed/8/

Here's an iteration on @jrschumacher meta-route above, which doesn't handle GET requests.
// Silex does not handle POST, PUT, and DELETE requests that are missing a trailing
// slash in the url. This meta-route appends the missing slash to such requests.
// See https://github.com/silexphp/Silex/issues/149 for why, tl;dr frameworks are opinionated.
//
// We override the default RedirectableUrlMatcher so that it doesn't respond with 301 to GET requests
// missing a trailing slash, so that like POST requests (and the rest), the internal.trailing_slash_redirect
// route will handle it.
$app['url_matcher'] = $app->share(function () use ($app) {
    return new UrlMatcher($app['routes'], $app['request_context']);
});

$app->match('/{resource}', function($resource) use ($app) {
    if ($app['logger']) {
        $app['logger']->debug(sprintf('Appending a trailing slash for the request to `/%s`.', $resource));
    }

    $request = Request::create(
        '/' . $resource . '/',
        $app['request']->getMethod(),
        array_merge($app['request']->query->all(), $app['request']->request->all()),
        $app['request']->cookies->all(),
        $app['request']->files->all(),
        $app['request']->server->all(),
        $app['request']->getContent()
    );

    // Make an internal request based off the one that would have 404'd.
    // http://silex.sensiolabs.org/doc/usage.html#forwards
    return $app->handle($request, HttpKernelInterface::SUB_REQUEST);
})->assert('resource', '.*(?<!\/)$')->bind('internal.trailing_slash_redirect');

So after looking through the code on this issue. The crux of the problem lies here: https://github.com/symfony/routing/blob/master/Route.php#L158
The path is always prefixed with a /. Normally this isn't an issue except for the case as discussed in this issue.
I did some debugging, and if you remove that line of code about the prepending slash, it all works. Because the Symfony route variables are marked private, you can't update them by extending the Route class. I think this is more of a Symfony issue than Silex.
A nice solution would be to have a route implementation that doesn't automatically prefix the path, and then when you define a route with a prefix, then defining the route as $app->get('', function(){}) will actually work now. And for all other routes defined, you should always include the /. But this will be left up to the user to do that.
$forum = $app['controllers_factory'];
$forum->get('', function () {
    return 'Forum home page';
});

// define "global" controllers
$app->get('/', function () use ($app) {
    dump($app['routes']->all());exit;
    return 'Main home page';
});
$app->get('/abc', function() {
    return 'abc';
});
$app->mount('/forum', $forum);

@ragboyjr you might be onto something here! Perhaps there's a way to have minimal impact in Symfony's routing and resolve this issue within Silex itself.
We could change the accessors in Symfony\Component\Routing\Route and from Silex\Route overwrite the setRoute method to not prefix routes with a slash.
Thoughts?

@alexkappa
Yes,

You'd need to make the variables protected in Symfony first.
Then I was thinking, in the Silex\Route, I was thinking we could add a flag for (is prefixed). If that flag is not set, then we just use the parent::setPath, if it is set, then we just set the path without the prefix.

So this change would only affect mounted routes in silex. This wouldn't be a BC break for Symfony. And then we'd need to update the documentation to reflect this specific change.

@alexkappa, the boys at Symfony don't like the idea of making Route class with protected vars. Updating the setPath to take flag might work, but I'm not sure on how we'd get that to filter back down into silex because it's BC incompatible change with regards to extending the route class.

I was thinking we could add a flag for (is prefixed). If that flag is not set, then we just use the parent::setPath, if it is set, then we just set the path without the prefix.

Yes something along those lines, but how will users pass that $isPrefixed argument? The Route::setPath() method is called from Silex\ControllerCollection.
I was thinking that perhaps we could supply a separate Route class which users can use instead of the original Silex\Route. Silex\Application is configurable, and the route_class and route_factory can be swapped for something else, so users can configure their $app with whatever routing they prefer. The downside however is that we'll introduce two very similar routing classes and people won't obviously see the difference.
Maybe configuring Silex\Route with options which it already supports and replace route_factory to set this option.

@alexkappa, not a bad idea at all. Here's a mock I did, and it actually works!
https://github.com/ragboyjr/Silex/commit/9eb3a45dffcdfe0339b12a6b66a898bebda645b1

Also, @alexkappa, implementing this could be done kind of two ways. We either make the user explicitly choose to allow empty routes, or we implicitly allow it by only making mounted routes empty.
For explicitly, we could easily provide a parameter in the RoutingServiceProvider like
$app['allow_empty_routes'] = true;

and that will use the appropriate Route class in the application.
For implicitly, we could setup any mounted controller collection to use EmptyPathRoute as the default route instead of the normal route. So on non-mounted paths, all routes defined are on the normal route. And on mounted routes, all routes defined use the EmptyPathRoutes.
Both options wouldn't be very difficult to do.

I personally found this way more elegant instead of making sub requests
$app = new Application();

$app->mount('/v1', new SomethingListProvider());
$app->mount('/v1/something', new SomethingRestProvider());

class SomethingListProvider implements ControllerProviderInterface
{
    public function connect(Application $app)
    {
        $app['something_list_controller'] = function () use ($app) {
            return new SomethingController($app);
        };

        $controller = $app['controllers_factory'];
        $controller->get('/something', 'something_list_controller:listAction')->bind(
            'something_list'
        );

        return $controller;
    }
}

class SomethingRestProvider implements ControllerProviderInterface
{
    public function connect(Application $app)
    {
        $app['something_rest_controller'] = function() use ($app) {
            return new SomethingController($app);
        };

        $controller = $app['controllers_factory'];
        $controller->get('/{id}', 'something_rest_controller:getAction')->bind(
            'something_get'
        );

        return $controller;
    }
}

Check this Symfony mini-doc, I hope it helps:
Redirect URLs with a Trailing Slash
Also in Symfony if you use your routes with trailing slashes, the non-trailing slashed routes will 301 redirected to tralining slashed routes.

see symfony/symfony#26284

It's nice to get some closure on this one =D


chore(settings): Also disable settings on mobile when Plex isn't conf…

…igured yet

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


[Blur & Focus] Support relinquishing focus from multiple views via co…

…ntainer - #113
This adds the ability to call this.refs.parentView.blur() and blur any active text fields inside the view. It will first try to blur the field (already supported) and if the field is not found as an "active" text field, it will transverse the view and resignFirstResponder for each of them.
I am currently using it in my app and works well.

@ide Made the changes you requested and tested them in my app and everything seems to work great, let me know if you think anything else is needed.

I like this :smile: :+1:

@brentvatne not sure what went wrong with the build?

@josebalius - if #113 works (assuming we can resolve the issue you mentioned in https://github.com/facebook/react-native/issues/113#issuecomment-168464059) is this still needed?

@spicyj would you mind taking a look at this pull request? It's been a while since the last commit was reviewed.

@josebalius Can you please indicate whether this PR is still needed? See the comment by Brent Vatne:

if #113 works (assuming we can resolve the issue you mentioned in #113 (comment)) is this still needed?

It's been a while since the last commit was reviewed and the labels show this pull request needs review. Based on the blame information for the files in this pull request we identified @nicklockwood as a potential reviewer. Could you take a look please or cc someone with more context?

I think this can probably be closed guys.

Thanks for looking @josebalius. I assume this was resolved in https://github.com/facebook/react-native/issues/113?

We are exposing TextInputState in #3308 which will allow you to do this too. I'm not sure it's worth exposing this one line function as it will increase API surface area ...


Data movement cost of MACs (in conv layer) with low data-reuse

Hi Gao,
Thanks for the nice tool. It helps us a lot in prototyping our ideas.
One thing that I'm not sure about is: whether this tool appropriately models the data movement cost of MACs with low data-reuse?  For example, MACs in depth-wise convolution have very low data reuse because of the fragmented memory-access. In this tool, cost of any convolution is decided based on the dimensions of convolution layer. Although the dimesnions in depth-wise convolution will be changed (because only one filter channel in filter convolve with a single input feature map),  changing dimesnion would be enough to model the data movement cost or do we need to model some extra relative cost?

If you treat the n-channel depth-wise conv layer as one layer, then the computation behavior is different from a normal conv layer. In depth-wise conv, each input channel only contributes to one output channel; in normal conv, each input channel contributes to all output channels. You will have to define a new layer class to model the depth-wise conv layer, and specify its mapping and partitioning behavior.


Document endian-dependent behavior, if any

@sunfish raised the point that we should specify how portable packed SIMD vector types behave with respect to the endianness of the architecture.
The order of the elements within a vector depends on the endianness of the machine. This could not only affect the results one gets from the indexed operations (extract,store,replace) and memory load and stores, but also the results of bit casts, for example, when bit-casting i8x16toi16x8thei8s might be ordered differently inside each i16` lanes on big endian machines, affecting the results.
The weird thing is that the portable vector type tests are running on PowerPC64 and PowerPC64el and all 3000 tests currently pass. These tests are pretty generic, so maybe we are unlucky and these tests are not hitting any endianness issues.
Or maybe LLVM handles this for us already somehow? We should add a couple of tests that we expect to break in either big-endian or little-endian and see what happens.
If LLVM handles this for us, we should investigate what exactly LLVM does and document that.

If LLVM does not handle this for us, there are many ways about how to proceed:

make endianness machine specific: this would make the vector types not
portable anymore, because asserts like those above would fail or pass dependin
on endianness.

renumber indices: if extract, store, and replace would take compile-time
indices, we could easily re-number them in big-endian machines to make the
asserts in the code above pass.

but IMO we should figure out if LLVM handles this for us first before spending time thinking about any hypothetical solutions. If someone has access to real big-endian hardware, it would be nice if that person could run stdsimd tests and report if whatever tests we come up with here pass or break.

IIUC, the following asserts might pass/fail depending on endianness:
let v = i32x4::new(0, 1, 2, 3);
assert_eq!(v.extract(0), 0); // OK in LE - ERROR in BE
assert_eq!(v.extract(3), 0); // ERROR in LE - OK in BE

let x = i8x16::new(0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15);
let t: i16x8 = x.into_bits(); // mem::transmute
let t_el = i16x8::new(256, 770, 1284, 1798, 2312, 2826, 3340, 3854);
assert_eq!(t, t_el); // OK LE; ERROR: BE

cc @hsivonen who is more familiar with these issues than I am

I'm not really familiar with this beyond:

Logic saying that lane-width-changing bitcasts should be expected to reveal endianness, which the above-mentioned Travis job shows to be the correct assumption.
clang's arm_neon.h has a bunch of #ifdefs that in the big-endian case reverse the vector before and after calling whatever built-in a given ARM-defined vendor intrinsic is implemented as in LLVM, so in the big-endian ARM case as far as the behavior of ARM-defined intrinsics goes, endianness leaks outside LLVM itself to the headers provided by clang.

It's quite possible that whatever behavior LLVM's ARM-specific built-ins exhibit in the big-endian mode is preferable in terms of portability between little-endian and big-endian ARM compared to how ARM itself had defined them. I don't know.
According to Wikipedia, ARM was little-endian before it had a big-endian option. It's really hard to find information of any actual uses of big-endian ARM. It seems that people doing embedded systems in Rust are far more concerned about support for non-ARM architectures than about enabling big-endian ARM. So testing the ARM vendor intrinsics in practice in the big-endian case to find out if they behave portably may prove hard. But if it's too hard to find a way to test them, maybe it's an indication that they don't need to be tested in that configuration. Also, the behavior of ARM intrinsics is moot to the extent this issue is about portable SIMD.

Thanks @hsivonen . FWIW there is a PR documenting endian-dependent behavior that has some more tests: #394 and the travis powerpc buildbots allow us to test this just fine, so that problem is solved I guess.
For the RFC, the only way to trigger this behavior is by using unsafe code (mem::transmute, slice::from_raw_parts, and friends), so I'd say that if endianness issues are only revealed through unsafe code, then at least initially that's "ok-ish".
An API for safe bit-casts should in my opinion provide endian-independent behavior by default. We could and should experiment with doing something like what ARM headers do in the stdsimd FromBits/IntoBits traits. These are currently safe, but they fail on big-endian, so this is a bug that must be fixed either way.

Has been documented in https://github.com/rust-lang-nursery/stdsimd/blob/master/crates/coresimd/tests/endian_tests.rs
Basically, transmuting between arrays of same element type and length as vectors works in an endian-independent way, but the behavior of transmuting to vectors of the same size but different numbers of lanes is endian dependent. Transmuting vectors to/from tuples of the same element type and number of elements happens to work but is undefined behavior, and transmuting to other tuples produces garbage since the elements of the tuple can be reordered and is therefore undefined behavior.


Env Var

Describe the feature
Description
Would be great if will be possible to export to ENV var an client's and publisher's IP to use it in accounting and /or  storage/transcoding purposes.

duplicate of #687


Bug Fix for Native Recycler Integration and upgrade support version to 9.0.6

Please format is according to Google Java Guideline. You can use the plugin. https://plugins.jetbrains.com/plugin/8527-google-java-format or the guideline https://github.com/google/styleguide/blob/gh-pages/intellij-java-google-style.xml. Without it, it's very hard to review as the PR will show a lot of changes due to formatting only.


cleanup: error message typos in sql.go

What this PR does / why we need it:
/kind cleanup
Special notes for your reviewer:
If applicable:

[ ] this PR contains documentation
[ ] this PR contains unit tests
[ ] this PR has been tested for backwards compatibility

@hickeyma thanks for your suggestion.
Done.


Add Polyphone.app 1.5.0

Follow up pull request to https://github.com/caskroom/homebrew-cask/issues/8592

Thank you for the contribution. It will be merged in a different pull request due to some simple recommended alterations. Your contribution is still included (and still credited to you), with the appropriate modifications, when applicable.


fix: Fix issue on template test create

Jira: PSGO-788
Changes:

creating a missing files/folder for command kbc template create test

This PR addresses a template issue. The problem was that the files (manifest.json, meta.json, description.md) were missing after running the command kbc template create test. That's why I added the logic to create these files.

@Matovidlo tests 9450b33


Can not search erlang sdk

my window10 pc running  wsl system
$ wsl -l -v
NAME      STATE           VERSION

Ubuntu    Running         2

my wsl system version info
root# cat /etc/os-release
PRETTY_NAME="Ubuntu 22.04.2 LTS"
NAME="Ubuntu"
VERSION_ID="22.04"
VERSION="22.04.2 LTS (Jammy Jellyfish)"
VERSION_CODENAME=jammy
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
UBUNTU_CODENAME=jammy

run vmr to search erlang, and it return this result
root@LAPTOP-IUKO3FRG:~# vmr
INFO    No versions found for current platform.

I don’t know if this is due to my WSL environment or a Vmr issue, because I installed Elixir or other language SDKs normally. Please take a look at this problem.

On my Alibaba Cloud server, I also can’t find Erlang in the Ubuntu 20.04 version.
root:~# cat /etc/os-release
NAME="Ubuntu"
VERSION="20.04.1 LTS (Focal Fossa)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 20.04.1 LTS"
VERSION_ID="20.04"
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
VERSION_CODENAME=focal
UBUNTU_CODENAME=focal

vmr does support native installations of erlang/elixir for windows, you do not need to use WSL.
BTW, it seems that there is sth. wrong with the version list of erlang, I'll work it later. Thanks for your feedback.

Already fixed.


Please support JUnit step property

Please support JUnit step property. That would be useful.

https://github.com/testmoapp/junitxml?tab=readme-ov-file#steps

Example:
<testcase name="testExample" classname="Tests">
  <properties>
    <property name="step[passed]" value="This is a test step that passed." />
    <property name="step[failure]" value="And this step had a failure." />
    <property name="step[skipped]" value="This step wasn't executed." />
    <property name="step[error]" value="And this step had an error." />
  </properties>
</testcase>

FYI: https://github.com/gotestyourself/gotestsum/issues/460

@ledmonster We added support for steps in version 0.2.19.


Fixed #26158 -- Rewrote cookie parsing based on rfc6265.

Do you think it merits a mention in the release notes just in case?

I added a release note.

I offered a few more cosmetic edits: https://github.com/collinanderson/django/pull/1. Otherwise, LGTM.

Ok, I merged in your changes.

merged in 93a135d111c2569d88d65a3f4ad9e6d9ad291452, thanks!

Sweet! Thanks!


Library with internal definition does not show up

I released a library recently with an internal definition file for AboutLibraries. But it won't show up...
This is the definition file: https://github.com/RubenGees/Introduction/blob/master/library/src/main/res/values/library_introduction_strings.xml
I start the AboutLibraries Activity like the following:
new LibsBuilder().withAboutIconShown(true).withAboutVersionShownName(true)
                    .withAnimations(true).withAboutAppName(getString(R.string.app_name))
.withActivityTitle(getString(R.string.activity_about_title)).withFields(R.string.class.getFields())
                    .withActivityStyle(Libs.ActivityStyle.LIGHT_DARK_TOOLBAR).start(getActivity());

Thank you for your help in advance!

@RubenGees as far as i can see it looks fine. also you do not need this library_introduction_classPath for an internal lib.
the lib is used in the project, and proguard isn't messing something up?

Ahh I found it. I created an internal file with your generator, but I needed an external one...

ah ok. haha. just saw that it looked at the fixed version of the definition file :D sure that i can't find an issue :P

Haha sorry for this pointless Issue... :D


Add Gas Fee Estimation

Adding the gas fee estimation API to the Sei documentation.
What is the purpose of the change?
Adding new content to Sei documentation to help developers get started quickly.
Describe the changes to the documentation
Added the new Sei gas fee estimation API developed by Blocknative. This will help developers setup their infrastructure quickly and efficiently.
Notes

Hey @cordt-sei ! Thanks for the comment. Chatting with the Sei team we are working with it might be best to get the API out there sooner so that when things change devs know exactly where to go versus having to wait and scramble.

Hey @laurencedelisle would you be able to add some more detailed docs for this? Just enough so that someone who is already experienced with it can get the basic info they need to set this up without going to an external page.

Superceeded by a new PR


YouTubeRebornPlus IPA's (All v4.2.6-v4.2.8)

19.08.2-4.2.6
Dropbox
Artifact
19.10.5-4.2.6
Dropbox
Artifact
19.10.7-4.2.6
Dropbox
Artifact
19.13.1-4.2.6
Dropbox
Artifact
19.14.2-4.2.6 (this version crashes on me when I play a video. Use the previous version if you experience crashes)
Dropbox
Artifact
19.19.7-4.2.7
Dropbox
Artifact
19.23.3-4.2.8 (most recent)
Dropbox
Artifact
Get it while it's hot.

b3c51f3 I just now updated the Submodules, the iSponsorBlock crash should be gone now

Re-running the workflow ... T-minus 7 minutes :)

When I use 19.14.2 to play a video, the app will exit, but Short will not

still crash
I don’t know if other people have the same situation

still crash
I don’t know if other people have the same situation

Are you using one of these devices? What iOS version?

I use an iPhone 13 mini. iOS 17.4.1
All the files work for me (although I haven't tested 19.14.2 yet).
I get the odd bug (community tab doesn't show anything, downloading videos sometimes doesn't work on certain versions, or the comments/video description displays a black screen when playing a YouTube generated music playlist). But the bugs are rare and I can live with it.
I've never experienced any crashing though.

still crash
I don’t know if other people have the same situation

Are you using one of these devices? What iOS version?
I use an iPhone 13 mini. iOS 17.4.1 All the files work for me (although I haven't tested 19.14.2 yet). I get the odd bug (community tab doesn't show anything, downloading videos sometimes doesn't work on certain versions, or the comments/video description displays a black screen when playing a YouTube generated music playlist). But the bugs are rare and I can live with it.
I've never experienced any crashing though.

iPhone 15 Pro
iOS 17.5 beta 1
ESign

iPhone 15 Pro iOS 17.5 beta 1 ESign

I don't want to say that the beta iOS is the issue, but I'd probably use the 17.4.1 version over it if you're experiencing crashing, Or maybe other versions of the YTreborn.  If they all crash, it's more than likely the beta iOS.
Again, I'm not a developer or a code contributor so I'm not speaking with any authority on the issue.  I'd start with eliminating some variables that would most likely be the root cause of the issue, though.

iPhone 15 Pro iOS 17.5 beta 1 ESign

I don't want to say that the beta iOS is the issue, but I'd probably use the 17.4.1 version over it if you're experiencing crashing, Or maybe other versions of the YTreborn. If they all crash, it's more than likely the beta iOS.
Again, I'm not a developer or a code contributor so I'm not speaking with any authority on the issue. I'd start with eliminating some variables that would most likely be the root cause of the issue, though.

19.13.1 work fine

@arichornlover whatever changes that were made to YTABconfig in the last 2 commits are causing my workflows to fail. :(

"Settings.x:1:9: fatal error: 'YouTubeHeader/GOOHUDManagerInternal.h' file not found"

19.19.7 is up, ladies & gents

But no actual v4.2.8 builds are really available (yet), right?

OoOoOo ... Nice

For us with TrollStore and not AltStore (for example 17.0), in the JSON that @arichornlover provided there's a link to IPA:
v4.2.8 IPA Download (yes, a tinyurl link)

recompiled with newest commits. :)


Error: deployments.apps "oracledb-19c-oracle-db" already exists

What happened?
I'm trying to reinstall a chart which got stuck because there is an issue inside the pod which makes it readiness probe stuck. Pod says running but it will not succeed. So, I uninstalled/deleted the chart and made changes to the chart to fix the issue and tried to install again.
helm install oracledb-19c oracle-db-1.0.0.tgz
Then it started failing saying
Error: INSTALLATION FAILED: deployments.apps "oracledb-19c-oracle-db" already exists

C:\Users\paju\Desktop\Oracle_db_helm>helm list
NAME            NAMESPACE       REVISION        UPDATED                                 STATUS  CHART           APP VERSION
oracledb19c     habs-namespace  1               2022-01-12 12:37:28.3759001 -0500 EST   failed  oracle-db-1.0.0

I tried kubectl get deployments.apps -A and there is no deployments.app 'oracledb-19c-oracle-db'

C:\Users\paju\Desktop\Oracle_db_helm>kubectl get deployments.apps -A
NAMESPACE NAME READY UP-TO-DATE AVAILABLE AGE
gatekeeper-system gatekeeper-audit 1/1 1 1 20d
gatekeeper-system gatekeeper-controller 2/2 2 2 20d
kube-system azure-policy 1/1 1 1 20d
kube-system azure-policy-webhook 1/1 1 1 20d
kube-system azuredefender-collector-misc 1/1 1 1 19d
kube-system coredns 2/2 2 2 21d
kube-system coredns-autoscaler 1/1 1 1 21d
kube-system metrics-server 1/1 1 1 21d
kube-system omsagent-rs 1/1 1 1 21d
kube-system tunnelfront 1/1 1 1 21d

I went and cleaned up every resources (deployments, services, pv, pvc, volumes, pods if they existed )
I confirmed by doing kubectl get all --all-namespaces and there is no resources related to this chart in the cluster at the time. I try again with the helm install and see the same error.
Then I tried with helm upgrade oracledb-19c oracle-db-1.0.0.tgz --install
Result :

Release "oracledb-19c" does not exist. Installing it now.
Error: deployments.apps "oracledb-19c-oracle-db" already exists

I tried with the --debug on and this is what I get

C:\Users\paju\Desktop\Oracle_db_helm>helm install oracle19c oracle-db-1.0.0.tgz --debug
install.go:178: [debug] Original chart version: ""
install.go:199: [debug] CHART PATH: C:\Users\paju\Desktop\Oracle_db_helm\oracle-db-1.0.0.tgz
client.go:128: [debug] creating 5 resource(s)
Error: INSTALLATION FAILED: deployments.apps "oracle19c-oracle-db" already exists
helm.go:88: [debug] deployments.apps "oracle19c-oracle-db" already exists
INSTALLATION FAILED
main.newInstallCmd.func2
helm.sh/helm/v3/cmd/helm/install.go:127
github.com/spf13/cobra.(*Command).execute
github.com/spf13/cobra@v1.2.1/command.go:856
github.com/spf13/cobra.(*Command).ExecuteC
github.com/spf13/cobra@v1.2.1/command.go:974
github.com/spf13/cobra.(*Command).Execute
github.com/spf13/cobra@v1.2.1/command.go:902
main.main
helm.sh/helm/v3/cmd/helm/helm.go:87
runtime.main
runtime/proc.go:225
runtime.goexit
runtime/asm_amd64.s:1371

I'm stuck at this!!!
What did you expect to happen instead?
I would like to see all the resources related to the chart get deleted from the K8 cluster when I do an uninstall and when I install/upgrade the chart , this error should not happen.
How can we reproduce the bug? (as minimally and precisely as possible)
helm version

version.BuildInfo{Version:"v3.7.1", GitCommit:"1d11fcb5d3f3bf00dbe6fe31b8412839a96b3dc4", GitTreeState:"clean", GoVersion:"go1.16.9"}

kubectl version

C:\Users\paju\Desktop\Oracle_db_helm>kubectl version
Client Version: version.Info{Major:"1", Minor:"22", GitVersion:"v1.22.0", GitCommit:"c2b5237ccd9c0f1d600d3072634ca66cefdf272f", GitTreeState:"clean", BuildDate:"2021-08-04T18:03:20Z", GoVersion:"go1.16.6", Compiler:"gc", Platform:"windows/amd64"}
Server Version: version.Info{Major:"1", Minor:"22", GitVersion:"v1.22.4", GitCommit:"b695d79d4f967c403a96986f1750a35eb75e75f1", GitTreeState:"clean", BuildDate:"2021-11-18T19:30:35Z", GoVersion:"go1.16.10", Compiler:"gc", Platform:"linux/amd64"}

Kubernetes Cluster:
Cloud Provider: Microsoft Azure
Anything else we need to know?
I already have the helm 3 , so I cannot use the --purge option with helm delete. Also, I don't have tiller in the K8s server because it is helm 3.

Even when the subsequent helm installs say status 'FAILED', the actual process is happening inside the , deployment object was created, pod got created. pvc is bound.

Is there any update on this issue? I am facing the same.

Were you able to find a fix for this? @JithuPaul24


SpringBoard Quit expectedly - Simulator Version 9.2 (SimulatorApp-643

Using the 9.2 Sim and matching Xcode 7.2 Build version 7C68
Springboard crashes when 'echo com.apple.mobilecal' | nc <IP_ADDRESS> 8000 is performed.

same here

I can confirm this issue.
The output of xcrun simctl spawn booted launchctl debug system/com.apple.SpringBoard --environment DYLD_INSERT_LIBRARIES=$PWD/SBShortcutMenuSimulator.dylib is Service configured for next launch..
Then when I execute xcrun simctl spawn booted launchctl stop com.apple.SpringBoard the simulator restarts.
And finally with echo 'com.apple.mobilecal' | nc <IP_ADDRESS> 8000 it crashes.
Here is the crash report, in case it helps.
Thanks!

same here

Confirmed for me as well. Running version Xcode 7.2.
Application Specific Information:
*** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[SBIconController _revealMenuForIconView:presentImmediately:]: unrecognized selector sent to instance 0x7fc8e3099800'
terminating with uncaught exception of type NSException
abort() called
CoreSimulator 201.3 - Device: iPhone 6s - Runtime: iOS 9.2 (13C75) - DeviceType: iPhone 6s

same here

Same.

The problem appears to be that the method that is called to present the Quick Actions menu has changed from - (void)_revealMenuForIconView:(id)arg1 presentImmediately:(_Bool)arg2; to -(void)_revealMenuForIconView:(id)iconView;. After changing the code in SBShortcutMenuListener.m I've still been unable to get the menu to appear - it highlights the app icon but doesn't present the menu.

Workaround:
You can install the iOS 9.1 Simulator through Xcode (Preferences -> Downloads).
Then using this simulator with Xcode 7.2 installed, it all works fine. Of course the issue still needs to be fixed...

Any progress here? My app is already set to run on iOS 9.2 so, the above workaround does not work for me and I would really appreciate an update.

The same issue for me. I using Xcode 7.2 and run iOS 9.1 Simulator

The SBIconControler header if it helps ...
@interface SBIconController : XXUnknownSuperclass <SBApplicationShortcutMenuDelegate, BBObserverDelegate, MCProfileConnectionObserver, SBApplicationRestrictionObserver, SBFolderControllerDelegate, SBSearchGestureObserver, SBIconViewDelegate, SBIconModelDelegate, SBIconViewMapDelegate, SBIconModelApplicationDataSource, SBReachabilityObserver> {
NSSet* _visibleTags;
NSSet* _hiddenTags;
SBIconModel* _iconModel;
BOOL _needsRelayout;
BOOL _sendITunesNotification;
BBObserver* _bbObserver;
NSMutableSet* _displayIDsWithBadgingEnabled;
SBRootFolderController* _rootFolderController;
SBFolder* _closingFolder;
SBFolder* _folderToOpenWhenScrollingEnds;
BOOL _rotating;
SBIcon* _launchingIcon;
SBIcon* _highlightedIcon;
SBLeafIcon* _iconToReveal;
SBIcon* _grabbedIcon;
SBIcon* _recipientIcon;
NSMutableArray* _droppedIconsAnimatingIntoPlace;
NSMutableArray* _droppedIconsInToOrOutOfFolder;
unsigned _numberOfDroppedIconsAnimatingIntoOrOutOfFolder;
SBIcon* _lastTouchedIcon;
BOOL _isEditing;
BOOL _animatingFolder;
BOOL _grabbedIconIsDraggedOutOfFolderView;
SBFolder* _grabbedIconSourceFolder;
BOOL _allowsUninstall;
float _iconAlpha;
float _oldScrollOffset;
UITouch* _lastTouch;
NSTimer* _folderSpringloadTimer;
BOOL _keyboardIsRotating;
BOOL _isAnimatingFolderCreation;
BOOL _isAnimatingForUnscatter;
BOOL _isAnimatingSignficantly;
unsigned _maxIconViewsInHierarchy;
SBIconColorSettings* _iconColorSettings;
BOOL _reachabilityModeActive;
SBApplicationShortcutMenu* _presentedShortcutMenu;
BOOL _skipCancelTouchesAfterShortcutMenuDismiss;
BOOL _showingSearch;
_UILegibilitySettings* _legibilitySettings;
NSIndexPath* _indexPathToResetTo;
BOOL _performedInitialLayout;
}
@property(readonly, copy) NSString* debugDescription;
@property(readonly, copy) NSString* description;
@property(readonly, assign) Class superclass;
@property(readonly, assign) unsigned hash;
@property(retain, nonatomic) SBApplicationShortcutMenu* presentedShortcutMenu;
@property(retain, nonatomic) _UILegibilitySettings* legibilitySettings;
+(id)sharedInstance;
-(void)applicationShortcutMenu:(id)menu launchApplicationWithIconView:(id)iconView;
-(void)applicationShortcutMenu:(id)menu startEditingForIconView:(id)iconView;
-(void)applicationShortcutMenuDidDismiss:(id)applicationShortcutMenu;
-(void)applicationShortcutMenuDidPresent:(id)applicationShortcutMenu;
-(void)applicationShortcutMenu:(id)menu activateShortcutItem:(id)item index:(int)index;
-(id)_aggregateLoggingAppKeyForShortcutMenu:(id)shortcutMenu;
-(void)_cleanupForDismissingShortcutMenu:(id)dismissingShortcutMenu;
-(void)_dismissShortcutMenuAnimated:(BOOL)animated completionHandler:(id)handler;
-(void)dismissShortcutMenuWithCompletionHandler:(id)completionHandler;
-(void)_revealMenuForIconView:(id)iconView;
-(void)_handleShortcutMenuPeek:(id)peek;
-(BOOL)_canRevealShortcutMenu;
-(void)handleReachabilityModeDeactivated;
-(void)handleReachabilityModeActivated;
-(BOOL)_shouldCancelFailedReachability;
-(BOOL)_shouldRespondToReachability;
-(void)_performReachabilityTransactionForActivate:(BOOL)activate immediately:(BOOL)immediately;
-(void)searchGesture:(id)gesture changedPercentComplete:(float)complete;
-(void)folderControllerDidReceiveCancelReachabilityAction:(id)folderController;
-(void)folderControllerDidEndScrolling:(id)folderController;
-(void)folderControllerShouldBeginEditing:(id)folderController;
-(void)folderControllerShouldClose:(id)folderController;
-(void)folderController:(id)controller draggedIconShouldDropFromListView:(id)draggedIcon;
-(BOOL)folderController:(id)controller draggedIconMightDropFromListView:(id)listView;
-(BOOL)folderController:(id)controller draggedIconDidMoveFromListView:(id)draggedIcon toListView:(id)listView;
-(BOOL)folderController:(id)controller draggedIconDidPauseAtLocation:(CGPoint)draggedIcon inListView:(id)listView;
-(Class)controllerClassForFolder:(id)folder;
-(Class)_controllerClassForFolderClass:(Class)folderClass;
-(id)_debugStringForIconOrder:(int)iconOrder;
-(void)applicationRestrictionController:(id)controller didUpdateVisibleTags:(id)tags hiddenTags:(id)tags3;
-(void)profileConnectionDidReceiveEffectiveSettingsChangedNotification:(id)profileConnection userInfo:(id)info;
-(id)firstPageLeafIdentifiers;
-(id)defaultIconState;
-(id)allApplications;
-(void)observer:(id)observer noteServerConnectionStateChanged:(BOOL)changed;
-(void)observer:(id)observer updateSectionInfo:(id)info;
-(void)_updateEnabledBadgesSetWithSections:(id)sections;
-(BOOL)_badgesAreEnabledForSectionInfo:(id)sectionInfo;
-(BOOL)iconViewDisplaysCloseBox:(id)box;
-(BOOL)iconViewDisplaysBadges:(id)badges;
-(BOOL)iconAllowsBadging:(id)badging;
-(void)iconCloseBoxTapped:(id)tapped;
-(BOOL)icon:(id)icon canReceiveGrabbedIcon:(id)icon2;
-(void)iconTapped:(id)tapped;
-(BOOL)iconShouldAllowTap:(id)icon;
-(void)icon:(id)icon touchMoved:(id)moved;
-(void)iconTouchBegan:(id)began;
-(void)icon:(id)icon touchEnded:(BOOL)ended;
-(void)iconHandleLongPress:(id)press;
-(void)viewMap:(id)map configureIconView:(id)view;
-(int)viewMap:(id)map locationForIcon:(id)icon;
-(unsigned)viewMap:(id)map numberOfViewsToPrepareOfClass:(Class)aClass;
-(id)viewMapShouldPrepareViewsOfClasses:(id)viewMap;
-(Class)iconViewClassForIcon:(id)icon location:(int)location;
-(id)windowForRecycledViewsInViewMap:(id)viewMap;
-(unsigned)viewMap:(id)map maxRecycledViewsOfClass:(Class)aClass;
-(void)didDeleteIconState:(id)state;
-(void)didSaveIconState:(id)state;
-(BOOL)canSaveIconState:(id)state;
-(BOOL)canAddDownloadingIconForApplication:(id)application;
-(BOOL)canAddWebClip:(id)clip;
-(BOOL)supportsDock;
-(unsigned)maxColCountForListInRootFolderWithInterfaceOrientation:(int)interfaceOrientation;
-(unsigned)maxRowCountForListInRootFolderWithInterfaceOrientation:(int)interfaceOrientation;
-(unsigned)maxIconCountForDock;
-(unsigned)maxIconCountForListInFolderClass:(Class)folderClass;
-(unsigned)maxListCountForFolders;
-(void)noteIconStateChangedExternally;
-(BOOL)importIconState:(id)state;
-(void)_selectIconModel:(BOOL)model;
-(void)_installedAppsDidChange:(id)_installedApps;
-(void)_iconModelDidLayout:(id)_iconModel;
-(void)_iconModelWillLayout:(id)_iconModel;
-(void)_iconModelDidReloadIcons:(id)_iconModel;
-(void)_iconModelWillReloadIcons:(id)_iconModel;
-(BOOL)relayout;
-(BOOL)_dismissRightEdgeSpotlight:(BOOL)spotlight;
-(BOOL)_presentRightEdgeSpotlight:(BOOL)spotlight;
-(void)_activateShortcutItem:(id)item fromApplication:(id)application;
-(BOOL)_dismissTopEdgeSpotlight:(BOOL)spotlight;
-(BOOL)_presentTopEdgeSpotlight:(BOOL)spotlight;
-(void)_searchViewControllerIsPresented:(BOOL)presented fromBreadcrumb:(BOOL)breadcrumb;
-(BOOL)dismissSpotlightIfNecessary;
-(BOOL)dismissSpotlightAnimated:(BOOL)animated;
-(BOOL)presentSpotlightFromEdge:(unsigned)edge fromBreadcrumb:(BOOL)breadcrumb animated:(BOOL)animated;
-(void)_lockScreenUIWillLock:(id)_lockScreenUI;
-(void)_noteUserIsInteractingWithIcons;
-(BOOL)isIconVisiblyRepresented:(id)represented;
-(BOOL)_iconListIndexIsValid:(int)valid;
-(void)layoutIconLists:(float)lists domino:(BOOL)domino forceRelayout:(BOOL)relayout;
-(void)compactIconsInIconListsInFolder:(id)folder moveNow:(BOOL)now limitToIconList:(id)iconList;
-(void)compactRootIconLists;
-(void)compactFolders:(id)folders;
-(void)animationDidStop:(id)animation finished:(BOOL)finished;
-(void)folderSpringloadTimerFired;
-(void)noteGrabbedIconLocationChangedWithTouch:(id)touch;
-(void)_resetFolderSpringloadTimer;
-(void)_cancelFolderSpringloadTimer;
-(id)recipientIcon;
-(void)setLastTouchedIcon:(id)icon;
-(id)lastTouchedIcon;
-(void)setRecipientIcon:(id)icon duration:(double)duration;
-(id)grabbedIcon;
-(void)_iconDropDidFinish:(id)_iconDrop;
-(void)setGrabbedIcon:(id)icon;
-(void)_dropIcon:(id)icon withInsertionPath:(id)insertionPath;
-(void)fixupBouncedIconsInFolder:(id)folder startingWithIndex:(int)index;
-(void)setLastTouch:(id)touch;
-(void)noteViewCovered;
-(void)restoreScrollingAndRotationAfterUngrab;
-(void)moveIconFromWindow:(id)window toIconList:(id)iconList;
-(void)_moveIconToContentView:(id)contentView;
-(void)_keyboardWillHide:(id)_keyboard;
-(void)_keyboardWillShow:(id)_keyboard;
-(BOOL)isEditing;
-(void)setIsEditing:(BOOL)editing;
-(void)iconWasTapped:(id)tapped;
-(void)clearHighlightedIcon;
-(void)_launchIcon:(id)icon;
-(void)removeAllIconAnimations;
-(BOOL)isAnimatingForUnscatter;
-(void)unscatterAnimated:(BOOL)animated afterDelay:(double)delay withCompletion:(id)completion;
-(void)scatterAnimated:(BOOL)animated withCompletion:(id)completion;
-(void)setIdleModeText:(id)text;
-(void)updateNumberOfRowsWithDuration:(double)duration;
-(void)uninstallIcon:(id)icon animate:(BOOL)animate;
-(void)uninstallIcon:(id)icon;
-(BOOL)canUninstallIcon:(id)icon;
-(BOOL)allowsUninstall;
-(void)uninstallIconAnimationCompletedForIcon:(id)icon;
-(void)removeIcon:(id)icon compactFolder:(BOOL)folder;
-(void)removeIcon:(id)icon andCompactFolder:(BOOL)folder folderRef:(id*)ref;
-(id)insertIcon:(id)icon intoListView:(id)view iconIndex:(int)index moveNow:(BOOL)now;
-(id)insertIcon:(id)icon intoListView:(id)view iconIndex:(int)index moveNow:(BOOL)now pop:(BOOL)pop;
-(id)insertIcon:(id)icon atIndexPath:(id)indexPath moveNow:(BOOL)now;
-(id)insertIcon:(id)icon atIndexPath:(id)indexPath moveNow:(BOOL)now pop:(BOOL)pop;
-(id)placeIcon:(id)icon atIndexPath:(id)indexPath moveNow:(BOOL)now layoutNow:(BOOL)now4 pop:(BOOL)pop;
-(void)scrollToIconToRevealAnimated:(BOOL)revealAnimated;
-(void)finishInstallingIconAnimated:(BOOL)animated;
-(void)setIconToReveal:(id)reveal revealingPrevious:(BOOL)previous;
-(id)iconToReveal;
-(void)replaceIconAtPath:(id)path withIcon:(id)icon saveState:(BOOL)state;
-(void)addNewIconToDesignatedLocation:(id)designatedLocation animate:(BOOL)animate scrollToList:(BOOL)list saveIconState:(BOOL)state;
-(void)addNewIconsToDesignatedLocations:(id)designatedLocations saveIconState:(BOOL)state;
-(void)viewWillTransitionToSize:(CGSize)view withTransitionCoordinator:(id)transitionCoordinator;
-(void)_didRotateFromInterfaceOrientation:(int)interfaceOrientation;
-(void)_willAnimateRotationToInterfaceOrientation:(int)interfaceOrientation duration:(double)duration;
-(void)_willRotateToInterfaceOrientation:(int)interfaceOrientation duration:(double)duration;
-(void)handleHomeButtonTap;
-(BOOL)scrollToIconListAtIndex:(int)index animate:(BOOL)animate;
-(void)scrollToIconListContainingIcon:(id)iconListContainingIcon animate:(BOOL)animate;
-(BOOL)_shouldLockItemsInStoreDemoMode;
-(BOOL)_iconCanBeGrabbed:(id)grabbed;
-(id)dropDestinationIconList;
-(int)dropDestinationIconListIndex;
-(id)currentFolderIconList;
-(id)dockListView;
-(id)currentRootIconList;
-(void)resetCurrentVisibleIconListImageVisibilityAndJitterState;
-(void)updateCurrentIconListIndexAndVisibility:(BOOL)visibility;
-(void)updateCurrentIconListIndexAndVisibility;
-(BOOL)isFolderScrolling;
-(BOOL)isScrolling;
-(void)showCarrierDebuggingAlertIfNeeded;
-(void)showInfoAlertIfNeeded:(BOOL)needed;
-(void)showDeveloperBuildExpirationAlertIfNecessaryFromLockscreen:(BOOL)lockscreen toLauncher:(BOOL)launcher;
-(void)_iconVisibilityChanged:(id)changed;
-(void)_resetRootIconLists;
-(id)folderNameForDisplayID:(id)displayID;
-(void)_prepareToResetRootIconLists;
-(id)folderIconListAtIndex:(unsigned)index;
-(id)rootIconListAtIndex:(int)index;
-(int)currentFolderIconListIndex;
-(int)currentIconListIndex;
-(id)_currentFolderController;
-(id)_openFolderController;
-(id)_rootFolderController;
-(id)rootFolder;
-(int)orientation;
-(int)_effectiveOrientation;
-(BOOL)shouldAutorotate;
-(unsigned)supportedInterfaceOrientations;
-(void)viewWillLayoutSubviews;
-(id)contentView;
-(void)loadView;
-(void)dealloc;
-(id)model;
-(id)init;
-(void)_runScrollFolderTest:(int)test;
-(void)_runFolderCloseTest;
-(void)_runFolderOpenTest;
-(unsigned)_folderRowsForFolder:(id)folder;
-(unsigned)_folderRowsForFolder:(id)folder inOrientation:(int)orientation;
-(CGRect)_contentViewRelativeFrameForIcon:(id)icon;
-(void)shiftFolderViewsForKeyboardAppearing:(BOOL)keyboardAppearing keyboardHeight:(float)height;
-(BOOL)allowsNestedFolders;
-(id)_proposedFolderNameForGrabbedIcon:(id)grabbedIcon recipientIcon:(id)icon;
-(void)_snapshotFadeDidStop:(id)_snapshotFade finished:(id)finished snapshot:(id)snapshot;
-(void)_addToFolderAnimation:(id)folderAnimation didFinish:(id)finish context:(id)context;
-(void)_compactRootListsAfterFolderCloseWithAnimation:(BOOL)animation;
-(void)_cleanupForClosingFolderAnimated:(BOOL)closingFolderAnimated;
-(void)_folderDidFinishOpenClose:(BOOL)_folder animated:(BOOL)animated;
-(void)_animateFolder:(id)folder open:(BOOL)open animated:(BOOL)animated withCompletion:(id)completion;
-(void)_folderControllerDidReceiveCancelReachabilityAction:(id)_folderController;
-(void)_disableReachabilityImmediately:(BOOL)immediately;
-(void)_presentNotificationCenterForReachability;
-(void)replaceFolderIcon:(id)icon byContainedIcon:(id)icon2 animated:(BOOL)animated;
-(void)addIcons:(id)icons intoFolderIcon:(id)icon animated:(BOOL)animated openFolderOnFinish:(BOOL)finish complete:(id)complete;
-(BOOL)isDroppingIcon:(id)icon;
-(BOOL)isDroppingIconsInOrOutOfFolder;
-(void)_moveDroppedIconsToLocation:(int)location;
-(void)_dropIconOutOfClosingFolder:(id)closingFolder withInsertionPath:(id)insertionPath;
-(void)_dropIconIntoOpenFolder:(id)folder withInsertionPath:(id)insertionPath;
-(id)createNewFolderFromRecipientIcon:(id)recipientIcon grabbedIcon:(id)icon;
-(void)_closeFolderController:(id)controller animated:(BOOL)animated withCompletion:(id)completion;
-(void)closeFolderAnimated:(BOOL)animated;
-(void)closeFolderAnimated:(BOOL)animated withCompletion:(id)completion;
-(void)openFolder:(id)folder animated:(BOOL)animated;
-(id)openFolder;
-(BOOL)hasOpenFolder;
-(BOOL)hasAnimatingFolder;
-(void)_setAnimatingFolderCreation:(BOOL)creation;
-(void)_setFolderToOpenAfterScrolling:(id)openAfterScrolling;
-(void)_setHasAnimatingFolder:(BOOL)folder;
-(void)_noteFolderAnimationStateDidChange;
-(id)iconListViewAtIndex:(unsigned)index inFolder:(id)folder createIfNecessary:(BOOL)necessary;
-(void)getListView:(id*)view folder:(id*)folder relativePath:(id*)path forIndexPath:(id)indexPath createIfNecessary:(BOOL)necessary;
@end

I hit the exact same issue as described above..

same problem

It works if you download iOS 9.1 for the Simulator (Hardware->Devices->Manage Device) then click the + at the bottom left to Add Simulator. Then change iOS to iOS 9.1 (might have to Download it)

thank you ! I willl download iOS 9.1 for the Simulator.

Hi, when run command line xcrun simctl spawn booted launchctl debug system/com.apple.SpringBoard --environment DYLD_INSERT_LIBRARIES=$PWD/SBShortcutMenuSimulator.dylib Service configured for next launch. , then the simulator restart, and when I run   echo 'com.apple.mobilecal' | nc <IP_ADDRESS> 8000, then the SpringBoard crash, can you tell me how to fix it?

Same  here.

I have updated this to work with iOS 9.3 in my fork of the code.

Get PoomSmart's PR into the project or your own copy to make it work across OSes

That's #18.


any support for ffcv

recently a team release "ffcv",
https://github.com/libffcv/ffcv
will you support this?

Thanks for your suggestion! It's not in our plan but we will consider it. And PR from the community is also welcome.


[FEATURE REQ] Azure.Data.Tables TokenCredential

Library or service name.
What library or service is this request related to? [e.g. Azure.Storage.Blobs]
Azure.Data.Tables
Is your feature request related to a problem? Please describe.
What feature would you like to get added? What problem is it solving?
Many of the libraries in here allow you to initialize the credential clients with an implementation of the class
TokenCredentials that allow you to authenticate with, for example, oauth which table storage supports.
https://docs.microsoft.com/en-us/rest/api/storageservices/authorize-with-azure-active-directory
For example, i'm using a ITokenAcquisition from Identity.Web that allows me to use a token from Azure AD to instantiate an Service Client for Queue, just like:
queueServiceClient = new QueueServiceClient(serviceUri, new TokenAcquisitionTokenCredential(tokenAcquisition));
This would allow me, in this case, make use of the logged in Oauth user and the user_impersonation scope for Azure Storage and make calls in behalf of the user, for an automatic lockdown of resources.
Let me know if you need me to go deeper.

Thank you for your feedback.  Tagging and routing to the team member best able to assist.

TokenCredential authorization is currently not supported by the service. If they do add it, we will implement it in the client SDK.

I see now that this section does not mention the .table domain.
Appreciate the fast response time @christothes.


CKAN crashes when I try to install any of the USI related mods to KSP

I am using CKAN v.1.22.3. and KSP v.<IP_ADDRESS>4. When I attempt to install any of the USI Tools dependent USI mods, CKAN crashes. Unfortunately, I did not record the error. It ultimately did install USI Tools, but then all of the dependent USI mods reported a conflict with USI Tools.

See #5544


chore: add meta tags for OG and Twitter

Description

Added meta title
Added meta tags for OG / Facebook
Added meta tags for Twitter

Related issue(s)
Resolves #149

@magicmatatjahu just checked that the open graph image is showing here: https://www.opengraph.xyz/url/https%3A%2F%2Fdeploy-preview-170--modest-rosalind-098b67.netlify.app%2F/
It works with relative path in the content, but if there is a better way to do this to output the whole url let me know. I tried using %PUBLIC_URL% in the meta but it wasn't returning anything

@mcturco No problem, there can be relative path. Thanks very much!

Before merge. Why do you wanna use absolute paths, for SEO reason? @mcturco

I believe it is better practice to have absolute paths in the meta tags... however, it seems to be passing the Open Graph tests.

@mcturco Thanks!


Discussion forum/community

Hi,
This is not an issue (sorry about that) but just wanted to mention that I am missing a active community/forum around 3Scale API Management so I created a Google Group and hope it will come alive :)
https://groups.google.com/forum/#!forum/3scale-api-management-by-red-hat
/ Joacim Järkeborn

Hi Joacim. Did you intend the group to cover all of 3scale API Management, or be focussed more on this project/area: the API Gateway? Just out of interest.

Hi Andrew
My thinking was to cover both, overall 3Scale API Management solution but also its individual components like API Gateway/apicast.
The reason is that I haven't found any good discussion forums for the solution/components involved.
If the forum gets very active it can be an idea to split it :)
FYI I have made two posts in the group ;-)
@andrewdavidmackenzie
Regards Joacim

Closing as there is nothing else to do in this issue.


Refactor plugin structure

This fixes #488
Update 1/10
Done:

the plugin interface brakes because of moving the cloudprovider.ObjectStore and cloudprovider.BlockStore to their own object* and volume* packages
moved ObjectStore, BlockStore and BackupStore interfaces each into a separate package to minimize the importable surface even further, for the cases where authors don't need to import all three.
moved code that was importing from pkg/backup, pkg/restore into an action package.
created a package named actioninterface (plugin/interface/actioninterface) that holds the interfaces for backup and restore item actions. Now items corresponding to backup and restore are named BackupItemAction and RestoreItemAction throughout the code. This might be an improvement for clarity as a side effect. The biggest win was removing those interfaces (everything under plugin/interface) from the packages where they were being implemented.

Signed-off-by: Carlisia<EMAIL_ADDRESS>

@carlisia I'm not sure how much of a pain this is for you, but I think it'd be easier to work through this if we break it up into some smaller chunks, with separate PRs for each.  I'd propose starting with a PR that just extracts the 4 pluggable interfaces & related types out of their current packages and into independent packages.  Is that doable?
I'm also going back and forth between where it makes sense to move these interfaces + types to.  One option, similar to what you have now, is to move them all under pkg/plugin, either in a single subpackage, or in individual subpackages. What I don't like about this is that within the velero code base, other packages that require an ObjectStore, for example, now have to reference pkg/plugin or some subpackage of it, but really they don't need to know/care about the fact that this interface is pluggable.
An alternative would be to create a couple new packages, along the lines of:
pkg/storage
    object_store.go
pkg/volume (already exists)
    block_store.go
pkg/itemactions
    backup_item_action.go
    restore_item_action.go
    resource_identifier.go
    resource_selector.go

Another alternative would be a hybrid of the two, where we actually separate out the interfaces that a plugin author implements from the interfaces that the velero code requires.  The former would go into a subpackage of pkg/plugin, and the latter would go into some structure like the above.  The interface definitions would probably start as exact copies of each other, but could diverge over time.  The only hard requirements are that the GRPCServer implementations can translate gRPC requests into calls to the implemented interfaces, and the GRCPClient implementations can translate required interface calls to gRPC requests.
Let's discuss some more on this issue before proceeding further down a specific path.  @nrb please weigh in as well when you're back online!

I don't mind redoing this from scratch.
My preference is to go with the option to separate out the interfaces that a plugin author implements from the interfaces that the velero code requires. This is the idea I had when I did the plugin directory vs the pluginmanagement directory.
If we go this route, I think I would prefer the first PR to be either extract all of the non author code into a separate package, OR extract all of the author code into its own package. And then refine it from there. And hopefully that wouldn't cause a cyclical issue. But I could do it any other way.
There are many interfaces in these packages, what are you referring to as the "4 pluggable interfaces"?

The 4 pluggable interfaces are:

pkg/backup.ItemAction
pkg/restore.ItemAction
pkg/cloudprovider.BlockStore
pkg/cloudprovider.ObjectStore

These are the ones that plugin authors can implement a plugin for.  The intent of the original issue, #488, was to not require a plugin author to import all of pkg/backup just to be able to implement a pkg/backup.ItemAction interface (for example).
Separately, there's plugin framework code that a plugin author needs to import in order to serve their plugin.  Today, that's all contained in pkg/plugin.  Specifically -- they need to use pkg/plugin/server.go and pkg/plugin/logger.go (e.g. https://github.com/heptio/velero-plugin-example/blob/master/velero-examples/main.go#L25).  As you point out, that package contains both framework code to be used by a plugin author, and internal code to be used only by velero, and ideally we can split that out as well.
I'd like to tackle these two issues in separate PRs, and I was proposing starting with the first since I think it's more straightforward, but if you want to start with the second, I'm open to it.

Ok I'm pretty sure we are saying the same thing for the most part.

I agree - I just want to tackle them separately.  Couple thoughts:

I'd be fine putting the 4 interfaces (backup_item_action.go, restore_item_action.go, object_store.go, block_store.go) in one package.  I think the import surface on the 4 combined interfaces is still quite small. But I'll defer to your judgment on this one.
I like splitting out pkg/plugin/framework.  I'm guessing that when we start splitting it out, more items will have to go in there, but we can work thru that when you get to that PR.  I did take a look at this and I think I have a sense of where the cut line is.
I think a flat pkg/pluginmanagement makes sense.  Some alternate name/nesting options -  pkg/pluginmgmt? pkg/plugin/clientmgmt? Food for thought.

As discussed, let's tackle moving the 4 interfaces into their own package(s) in one PR, and then splitting pkg/plugin out in a separate PR.  We can close this one and start fresh if you want.

One other thing - maybe we should just do this development in master now that we're past v0.11.  Fewer merge conflicts down the road. Thoughts?

I like pkg/plugin/clientmgmt, let's go with that.
+1 for doing it against master. I'll open a PR to merge the commit that is ahead on the plugins branch.

To be sure, for the code to pass CI I will have to start moving the code into the plugin/framework package because of dependencies.


Add possibility to create coverage reports

Looks like this https://florian-bischof.at/leaflet/coverage/html/

Considering we'll be moving away from Karma in the near future, I wonder if it's worth it to merge this in? Still a great enhancement, and I personally have no issue with landing this now.

Considering we'll be moving away from Karma in the near future, I wonder if it's worth it to merge this in?

I now, thanks. But I think it make sense to have this report. We should also add a coverage report with the new tool in the future.


Add ARM64 support

Add ARM64 support for images and binaries for those people who want to run on a more power-efficient platform.

Solved by #13


System decoupling and refactor.

This PR refactors the system services so that the runner is more optional. However, this means we have moved away from "the runner controlling the lifetime" to a purely shared_ptr model. It will make the UX of the API a lot nicer in the long run despite being a breaking change (its alpha after all, this stuff happens). Resolves #204 .

I want to do some brief testing first, however this looks pretty good imo.
2 questions:

Is there a chance of circular dependency now that we're purely on shared pointers? (I didn't see any explicitly in the PR but I'd like to know if you happen to have identified any)

For dtors, we'd want to move away from destructing explicitly and instead call a tearDown() method of some sort, correct?

Is there a chance of circular dependency now that we're purely on shared pointers? (I didn't see any explicitly in the PR but I'd like to know if you happen to have identified any)

No. All the systems were decoupled in terms of circular dependencies long ago. This change is purely a lifetime management change. 😄

For dtors, we'd want to move away from destructing explicitly and instead call a tearDown() method of some sort, correct?

IMHO, the best way is to have both i.e. have dtor call tearDown() in situations where its needed. This way if we don't call it ourselves and the service is discarded, it still cleans up after itself.


[MATERIALS BREAK] higher period clock

THIS CHANGE BREAKS MATERIALS.
This adds getUserTime() in shaders/materials, which returns the time
in second since Renderer::resetUserTime() was called.
Two values are provided, the time in second encoded as a float and
the difference between that and the double value, which together allows
to perform high precision time computation when needed.
This change allows longer running animations in materials. Using only
the float value, give millisecond resolution for more than 4h.

Why use a float4 and not float2?