100% small spike to 100% decrease

Hello. Thank you for this tool but with this afternoon's price, my prediction has been completely changed. I am the only one on the island, all prices are from my island, there has been no time traveling, and all prices are correct.
Thursday am:https://turnipprophet.io?prices=<IP_ADDRESS>.<IP_ADDRESS>.....
Thursday PM:https://turnipprophet.io?prices=<IP_ADDRESS>.<IP_ADDRESS>.55....

It appears as though your Monday AM value of 82 is the root cause of the issue here.
Some necessary context:
The sell price for any period is your Sunday buy price, known as basePrice multiplied by a given rate where the rate has a random chance element. The result of that is passed into an intceil() function which adds 0.9999 and then truncates the floating point down to a whole number.
With that out of the way, for a Decreasing pattern, the first period's rate is guaranteed to be between 0.85 - 0.9, based on this code extracted from the game.
rate = 0.9;
rate -= randfloat(0, 0.05);

Then, if we assume the worst possible random chance, we get the lowest rate of 0.85 and we multiply your base price against that value.
97 * 0.85 = 82.45

Finally, we pass the result into intceil() to get the final price value.
intceil(82.45)
82.45 + 0.99999 = 83.44999
(int) 83.44999 = 83

What this tells us is that for a buy price of 97, the lowest possible value for a Decreasing pattern is 83, making the 82 you received out of range, which means if the value is correct your pattern cannot be Decreasing.
There is only one other pattern that could possibly have as many consistent decreases before eventually spiking, and that is Small Spike, which has an opening range between 0.4 - 0.9, as seen in this code from the game:
rate = randfloat(0.9, 0.4);

However, for a Small Spike, the Thursday PM period is the last possible start of the spike, and when your value came in lower again, that made it impossible for Small Spike to be your pattern.
At this point, Turnip Prophet has determined there are no possible patterns for your values at all, and so it went over all the patterns again but this time with a fudge factor of 1, effectively increasing the possible ranges by 1 on the lower & upper bounds and as a result making your 82 on Monday AM appear as an acceptible value, even though by the game's math it is not possible.
Now, for why you ended up seeing a Decreasing pattern show up in the end - that's an unfortunate side effect of the fudge-factor that Turnip Prophet adds when it cannot find a valid pattern.
If you remove the Monday AM value of 82, the rest of your week results in a Decreasing prediction.
https://turnipprophet.io?prices=97..<IP_ADDRESS>.63.58.55
So this begs a few questions:

Are you confident the values were entered exactly correctly?
Is every value, included the buy price, from the same island?
Are you certain absolutely no time traveling was done this week?

Thank you for such a thorough explanation.

I have been keeping a written log this week in order to track and am 99.9% certain of my accuracy
All values are from the same island including the buy.
I do not time travel as a part of my play style and am the only one with access to my switch

Ok, thanks for the detail here.
Something I hadn't mentioned previously was why we have the fudge factor in the first place.
When it comes to math in computing, floating point (not whole numbers) math is one of the most troublesome areas. CPUs from different architecture (x86, or ARM for example) can have slightly different results. Furthermore, programming languages can also have differences in how they handle the same math.
Essentially it's impossible to guarantee the exact result at all times unless your environment is identical, which ours is not.
The game runs on an ARM based CPU and the game is written in C++, while this tool runs on (probably) an x86 CPU, and is written in JavaScript.
If you are absolutely certain of those details, it is definitely possible that the Monday 82 was a rounding difference between the game on a Switch and this app, but I have to be honest that's an extremely rare or unlikely chance.
In any case, if it is a rounding issue, then sadly there's not really much we can do about it.
We have talked about putting messages on the site that appear when the fudge factor is applied, to give people a better sense of the fact that the numbers could be off. At least in that case you would have known to not take the result as gospel.

I had the same situation this week.
This was the situation before this afternoon: https://turnipprophet.io/?prices=<IP_ADDRESS>.<IP_ADDRESS>.....
A 100% small spike
And this was the situation after this afternoon: https://turnipprophet.io/?prices=<IP_ADDRESS>.<IP_ADDRESS>.63....
A 100% decrease, same as OP.
I have not time-traveled this week, have only bought on my island, am sure of the prices, and nobody visited my island (if that's relevant).


How to download Focal-DINO weights ? Model zoo links throw error

I tried downloading some pretrained weights from the model zoo of the focal-DINO repo, but the link throws an error ("Public access is not permitted on this storage account."). I saw that the same issue has been discussed for FocalNet's model zoo, and the answer was to look on huggingface. However I can't find anything on huggingface for the DINO version of FocalNet. Where can I find that ?

Please find the ckpts here: https://huggingface.co/microsoft/focalnet-large-fl4-dino-o365/resolve/main/focalnet_large_fl4_pretrained_on_o365.pth and https://huggingface.co/microsoft/focalnet-large-fl4-dino-o365-cocoft/resolve/main/focalnet_large_fl4_o365_finetuned_on_coco.pth

Thank you very much !


Check all model & guess fitting functions

Check that in all model & guess functions, that they behave for all inputs e.g must check all for flat data as this is most likely to cause problems (div by 0 errors).

For the guess functions, if they really can't guess a sensible value for a parameter (e.g. guessing the centre of a gaussian with amplitude zero) then make them fall back to very simple guesses - e.g. always guess centre of gaussian is in middle of x range, guess a height of 1, etc... This is still "better than nothing" as a guess for the optimizer.


Character not importing?

Im unable to import Clerics or Paladins into my game (Druids are fine), I have the cookie-thing enabled and other stuff and the error reads out like this

Please provide a character link and:

What browser are you using?
What version of ddb-importer are you using?

I've forwarded these to the discord server but I'll provide them here as
well
https://www.dndbeyond.com/profile/Maliki_lagiban/characters/49128422
(Cleric)
https://www.dndbeyond.com/profile/Theloserlord2365/characters/49053647
(Paladin)
Google Chrome (Molten Hosting)
Foundry 0.79
DDB Importer 0.6.31
On Sun, Apr 25, 2021 at 10:49 AM Jack Holloway @.***>
wrote:

Please provide a character link and:

What browser are you using?
What version of ddb-importer are you using?

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/MrPrimate/ddb-importer/issues/126#issuecomment-826362210,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AT2MPVABIF5SMHSHJ5GWZXLTKRI3RANCNFSM43Q2AF7Q
.

Resolved by MrPrimate


Bug in right shift bitwise operator?

For ex, 100 >> 32 should return 0, but it returns 1.

We decided to solve it this way:

We add unsafe_shl and unsafe_shr as Int methods that do what the current >> and << do (thus the "unsafe" in their names.
We add >> and << with the rules seen in the commit above: use the opposite operation on negative numbers, return zero if shifting by an amount larger than the number of bits in the type, else invoke the unsafe variants.

The >> and << methods are usually used with constants, and in those cases LLVM is pretty smart and will optimize that out. When the argument is not known at compile-time there's an 1.5x slowdown, but we prefer this slowdown to undefined behaviour.
Because primitives will be replaced with regular methods, it will take a couple of releases for this to be available.

Yes, this makes sense, it is better to avoid unsafe behaviour (if someone really wants to go for it, the unsafe version of the shift operators is provided anyhow according to the above).


Fix selectPeers js/react switching tabs

selectPeerCount and selectPeers have the same id so that tabs were not working

merged, thanks @rodumani !


BucketLifecycleConfigurationV2 has no nonCurrent version action configuration

Describe what happened
When creating an aws.s3.BucketLifecycleConfigurationV2 resource, one would expect to control what happens to objects once they expire. The only "rule type" that is allowed is an expiration rule.  If you go into your bucket lifecycle rule in the AWS console and check the box that says "Permanently delete noncurrent versions of objects", a new noncurrent version action is created in the console. When running a pulumi preview after checking the "Permanently delete noncurrent versions of objects" box, the stack shows a diff in the rules configuration.

Sample program
const bucketName = "superdupermegatestbucketforpulumi"
const bucketLifeCycle = new aws.s3.BucketLifecycleConfigurationV2(`${name}-bucket-lifecycle`, {
                        bucket: bucketName,
                        rules: [{
                            id: "DeleteObjects",
                            status: "Enabled",
                            filter: {
                                prefix: "",
                            },
                            expiration: {
                                days: 3,
                                expiredObjectDeleteMarker: true,
                            },

                        }],
                    });

Log output
 aws:s3:BucketLifecycleConfigurationV2 [redacted]-bucket-lifecycle update [diff: ~rules]
Affected Resource(s)
aws.s3.BucketLifecycleConfigurationV2
Output of pulumi about
Plugins
KIND      NAME        VERSION
resource  aws         6.57.0
resource  awsx        2.16.1
resource  cloudflare  5.42.0
resource  docker      4.5.7
resource  docker      3.6.1
resource  eks         2.8.1
resource  kubernetes  4.18.3
language  nodejs      unknown

Host
OS       debian
Version  bookworm/sid
Arch     x86_64

This project is written in nodejs: executable='/home/dj/.nvm/versions/node/v21.7.2/bin/node' version='v21.7.2'

[redacted stack resources]

Found no pending operations associated with development

Backend
Name           pop-os
URL            file://~
User           dj
Organizations
Token type     personal

Dependencies:
NAME                VERSION
@pulumi/awsx        2.16.1
@pulumi/kubernetes  4.18.3
typescript          4.9.5
@pulumi/pulumi      3.137.0
@types/node         18.19.63
npm-upgrade         3.1.0
prettier            3.3.3
zod                 3.23.8
@pulumi/aws         6.57.0
@pulumi/cloudflare  5.42.0
@pulumi/eks         2.8.1

Additional context
I would want to be able to configure what happens to objects once they expire with Pulumi. It seems this might just be a missing type in the typescript package? Essentially, the end goal is after x number of days, expire the objects in the bucket, then after those x days, delete all expired objects.
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

Hey @davidfries, BucketLifecycleConfigurationV2  has two nonCurrent related actions available.

noncurrentVersionExpiration: Can be used to delete non-current object versions
noncurrentVersionTransitions: Can be used to move non-current objects to other storage classes

This example shows both of them at play.
You should be able to use the noncurrentVersionExpiration option for your usecase.

Hey @flostadler that did the trick! I guess the of noncurrentVersionTransitions was a little confusing in-regards to whether it deletes or does something else. I'll go ahead and mark this closed, thanks for your time and help!


🐞 - tui-multi-select\tui-data-list-wrapper with updadeOn=blur does not correct work

Which @taiga-ui/* package(s) are the source of the bug?
kit
Please provide a link to a minimal reproduction of the bug
No response
Description
Hi, everyone!
There are some code:
component
const form= this.fb.group({
    employeeValue: [employees as EmployeeDto[], { updateOn: 'blur' }],
});

template
<tui-multi-select
  formControlName="employeeValue"
  [stringify]="getEmployeeLabel"
  [tuiTextfieldLabelOutside]="true"
  [tuiTextfieldCleaner]="true"
  [identityMatcher]="matcher"
>
  Сотрудники
  <tui-data-list-wrapper
	  *tuiDataList
	  tuiMultiSelectGroup
	  [items]="employessItems$ | async"
	  [itemContent]="searchStringify | tuiStringifyContent"
	  [emptyContent]="'Сотрудники не выбраны'"
  >
  </tui-data-list-wrapper>
</tui-multi-select>

Checkboxes stop correct working in list when use { updateOn: 'blur' } .

Angular version
13.2.2
Taiga UI version
2.34.0
Which browsers have you used?

[X] Chrome
[ ] Firefox
[ ] Safari
[ ] Edge

Which operating systems have you used?

[ ] macOS
[X] Windows
[ ] Linux
[ ] iOS
[ ] Android

Our internal implementation relies on valueChanges of the control so it does not get updated until blur. We need to come up with something else 🤔

#3479


Fix link to how to create a client to update HAPI

See context here: https://vmware.slack.com/archives/C6P0RC8UQ/p1627235186443000

Thanks @robertjsullivan! Merging now.


Approve, publish, and send out press release

Draft is here: http://citycampnc.org/?p=2935&preview=true

@ChrisTheDBA Can you give me more information so I can tweet about this?

@jhibbets I am not able to see the draft

@natalienoel1 this was published today http://citycampnc.org/2017/09/25/seventh-annual-citycamp-nc-civic-technology-unconference/


dependabot?

what do people think of adding a dependabot hook to the napari repo?  https://github.com/marketplace/dependabot-preview/
I don't think we would necessarily use it to actually merge the PRs (actually bumping our dependency requirements), but it would immediately trigger a CI test every-time something gets released (and problematic updates would immediately fail in a PR test).

How would you use it? We don't really have a dependency update policy...?

it would just be to catch things like the numpy 1.18 update breaking tests and numcodecs breaking tests, so we could either fix the problems (as we did in the case of numpy) or pin the requirements.txt (in the case of numcodecs).  Given the high level of activity of napari PRs, we're likely to stumble upon these things pretty quickly anyway, so it's not a big deal... but it also doesn't come with much overhead or effort, this would just open up a new PR each time a dependency was released, we would make sure the tests pass, and then close the PR (or update accordingly if it didn't).  just a passing thought...

I like this idea. It seems useful to explicitly test and catch these things and work on fixes rather than just wait for them to be detected organically, which can be confusing when also working on new features in PRs too.
What does @kne42 think?

On one hand, it would immediately point out different bugs/incompatibilities and make it easier to separate dependency bugs from bugs introduced in PRs. On the other hand, it might flood us with unnecessary PRs...
I think because it makes it easier to isolate dependency-related bugs, I'm overall in favour of it.

that's a good point... that could be kinda annoying.  I wonder if it might be better to create a fork that has dependabot active instead... something that won't clutter up the main repo PRs.  It might even be possible to get alerts on failed tests.  Will look into it

trying it out here: https://github.com/tlambert-forks/napari-dependabot/pulls
feel free to watch that repo if you want to see how the PRs work.  we'll see how useful/interesting it is.

I'm curious about the philosophy of dependabot - am I correct that it makes PRs for us to be always >= the latest release. Is that desirable? Another philosophy might be to be >= the oldest release we are still compatible with. Thoughts @jni?

that was my immediate question as well after playing with it for a bit.  As you might have noticed, I ended up "cheating" to make it work by actually pinning all of our requirements to a specific version, so that when a new one comes out it will appear out of date and open a PR.  It might be aiming more for the crowd that generally pins requirements precisely, and needs to know about security and other updates (e.g. often in web development).  While it may be possible to still get it to open a PR every time a dependency updates without changing our requirements.txt (or perhaps other similar services do that), I still don't think it's worth adding to all the tooling we've already got going on here.  With the frequency that our tests are run (and the fact that that fork there will also be running dependabot anyway), it's unlikely to add much.  So I'm now 👎on the idea.

I'm curious about the philosophy of dependabot - am I correct that it makes PRs for us to be always == the latest release. Is that desirable?

also: no that's not desirable. the intention was never to merge the dependabot PRs... just to be immediately notified of a failing test (or close the PR otherwise).

ah ok, yeah I'm probably 👎for now, but curious what others think. Definitely good to be aware of though (I wasn't before this)


Populate publications with findrefs.Reference

Done in https://github.com/laminlabs/cellxgene-lamin/pull/108


multiple-graph

I would like to use gcn in case of multiple edges. How i can include different adjacency matrix?
Thank you

If you have multiple edge types, you can use:
https://github.com/tkipf/relational-gcn
On Thu, Apr 25, 2019 at 4:14 PM Mónica Aguilar Herrero <
<EMAIL_ADDRESS>wrote:

I would like to use gcn in case of multiple edges. How i can include
different adjacency matrix?
Thank you
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/tkipf/keras-gcn/issues/47, or mute the thread
https://github.com/notifications/unsubscribe-auth/ABYBYYAH35YIAYYSGXTMLV3PSG4EDANCNFSM4HINR23Q
.

Thanks for the quick reply!


Ability to return paragraphs from a note with a particular tag in them

I like to mark paragraphs of various types with a hashtag (for example, #try for an experiment, #idea for an idea I want to follow up on, #insight for insights worth returning to in a spaced repetition model, and so forth). There may be multiple instances within a particular note. I'd like to create a table of every such paragraph, organized by the note that it is in or as a flat list.
I have found two ways to do this in the current model, both a bit clunky:

Make the paragraph a task. Then I used DataviewJS to pick out all the tasks that have the hashtag string in them:

dv.table(["Link", "Experiment"],
myTasks.filter(t => t.text.includes("#try"))
.filter(t => !t.completed)
.map(t => [t.section, t.text]));
This is fine for things that are tasks (like #try), but the others aren't tasks and it's ugly in the original note.

Add an extra prefix to the paragraph, so it can be picked out by a table query. For example, prefix the paragraph with "Core:: " and then run this query:

TABLE Core AS "Core Idea", file.mday.month + "-" + file.mday.day + "-" + file.mday.year AS "Updated"
FROM #core
WHERE !contains(file.path,"Template") and !contains(file.path,"Daily Pages")
This works, but is also clunky.
So, the request:
Could you add an ability to query for paragraphs containing a particular hashtag, at the scope of the paragraph and not at the scope of the whole note? It would be great if you could do it with a table query, to leverage all the power you've created for that, but JS would also work. And of course, if I'm missing something, open to other ideas!
Thanks for a really powerful plugin - it's been a game-changer in finding new ways to leverage Obsidian, for me.

This functionality is incoming soon - all tag, metadata, and link references will include the paragraph that they came from.

+1, I am trying to use DataView to annotate list items and paragraphs in my Daily Notes .e.g.,
- [meeting:: [[Person Name]]], spoke about ordering more books, left it with them
Then have an "index" on that person's own page that will show the text from each line of all notes that have that field in them. Much more useful in that case that a list of pages.
Very excited to see this is an upcoming feature. Nice work!

+1 - a vital feature

This functionality is incoming soon - all tag, metadata, and link references will include the paragraph that they came from.

Just curious - has there been any update on this? I've scanned the changelogs and haven't seen anything obvious in them that might match this?

It hasn't appeared yet - I have pieces scattered about but have been focusing on some live preview improvements first and finally stabilizing Dataview Beta.

+1, I am trying to use DataView to annotate list items and paragraphs in my Daily Notes .e.g.,
- [meeting:: [[Person Name]]], spoke about ordering more books, left it with them
Then have an "index" on that person's own page that will show the text from each line of all Daily Notes that have that field in them. Much more useful in that case that a list of pages.
Very excited to see this is an upcoming feature. Nice work!

Im trying to achieve exactly this, would be interesting to see if the official solution comes out soon!


Require Explicitly initialize Email regex mask operator

I do not intend to mask emails in my logs, only using MaskProperties, but this enricher masks emails by default. I also don't have an option to opt-out of this operator either.
// Configures Serilog: sinks and enrichers go here
let initializeLogging (configuration: IConfigurationRoot) =
    Log.Logger <-
        LoggerConfiguration()
            // read from Serilog section of json config files
            .ReadFrom
            .Configuration(
                configuration
            )
            .Enrich
            // FIX: this constructor automatically adds Email regex matching everywhere
            .WithSensitiveDataMasking(
                // these properties will always be masked if they are present.
                // the field names are case insensitive
                Action<SensitiveDataEnricherOptions>(fun opts -> opts.MaskProperties.AddRange([ "Secrets"; "Password" ]))
            )
            .Destructure.FSharpTypes()
            .CreateLogger()

as an aside, maybe we can also add NeverMaskProperties to exclude properties from regex operators that may match it

You can configure the enricher to only mask a specific property and ignore the rest like so:
new LoggerConfiguration()
    .Enrich
    .WithSensitiveDataMasking(
        options =>
        {
            options.MaskingOperators.Clear();
            options.MaskProperties.AddRange([ "Secrets"; "Password" ]);
        });

That will remove all the default masking operators and always mask the Secrets and Password properties.
I don’t have a computer handy here to test so while I think this works it might not 😉

as an aside, maybe we can also add NeverMaskProperties to exclude properties from regex operators that may match it

Good suggestion 👍
I’ll include this in the next release

I've decided to not change the behavior of the configuration just yet as that would break usage if you already have implemented the package in your app. Suddenly the masking would not be active anymore and that's a surprise I don't want to spring on users.
In the meantime, if you don't want the default masking operators (or basically, good practice anyway)  you should indicate the list of masking operators that are relevant to your application like so:
new LoggerConfiguration()
    .Enrich
    .WithSensitiveDataMasking(
        options =>
        {
            options.MaskingOperators = new List<IMaskingOperator>
            {
                new EmailAddressMaskingOperator(),
                new IbanMaskingOperator()
                // etc etc
            };
        });

I've updated the README to reflect this.
In the meantime I've also added a ExcludeProperties option which you can use to exclude properties from masking even if their values would match a masking operator.


python3Packages.sendgrid: 6.9.6 -> 6.9.7

Description of changes
https://github.com/sendgrid/sendgrid-python/releases/tag/6.9.7

Things done

Built on platform(s)

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

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

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

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

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

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 163621 run on x86_64-linux 1

2 packages built:

python310Packages.sendgrid
python39Packages.sendgrid


txn: finish transaction

Based on

https://github.com/tikv/agatedb/pull/67
https://github.com/dgraph-io/badger/blob/45bca18f24ef5cc04701a1e17448ddfce9372da0/txn.go
https://github.com/dgraph-io/badger/blob/45bca18f24ef5cc04701a1e17448ddfce9372da0/txn_test.go

Signed-off-by: GanZiheng<EMAIL_ADDRESS>

A quite weird problem on leak sanitizer test.
As shown in https://github.com/tikv/agatedb/runs/6933910360?check_suite_focus=true, segmentation violation occurred while tests were running. And if we test it locally, we could additionally get error information as below.

Currently I have no idea about why this error occurs. It is not reproduced stably. I have tried a lot to find which modification introduces this error, and I found it may have relationship with the compaction. If we set option to run compaction more frequently, we then be more easier to get this error.
And another point that attracts me is premature terminator entry in the picture above. I guess some codes make a memory corruption when running.


Support for latest versions of Django (4+), Graphene (3+), Graphene Django (3+) ?

I am working on a project where I have the latest versions of all of the above packages. As soon as I installed graphene-django-filter, pip started uninstalling and downgrading my packages since graphene-django-filter has a hard upper limit on its dependencies.
I just wanted to know if there is any particular reason for this and if there are any compatibility issues already noted because of which this has been kept?
If not, can we bump up the dependency versions?

I think this repository has not been maintained for more than an year. I forked one and updated the pacakge dependencies.

Maybe if the maintainers want some support, I am happy to help.

Hi guys!
Now our team is a little dispersed and there is no strength to support. However, if you really need the functionality of this library, we can implement it.
@thomas-arun I sent an invitation for you to take part in this project

Thank you @Luferov, I shall put in few PRs with potential fixes.

Thank you @Luferov, I shall put in few PRs with potential fixes.

Thank you so mush for you job!

#73
@Luferov I have put in a pull request for bumping the package versions. Can you take a look and merge?
Do you need me to create a release too?

@Luferov Thank you for approving the PR, there were few other fixes I needed to do for the GitHub actions. They are all fixed now and the CI action has completed successfully.
Will you be able to create a new release to PyPi? I am not sure what steps are followed to do that.
Thanks in advance

I fixed the commit message part. Didn't know python semantic releaser was being used.
I've successfully released v0.6.5
Closing this ticket


Task list inside table cells

Originally requested in https://github.com/github/markup/issues/364
Task lists inside of table cells could be really interesting. I don't know exactly what the syntax would look like…
[x] | First Header  | Second Header
--- | ------------- | -------------
[ ] | Content Cell  | Content Cell
[ ] | Content Cell  | Content Cell

Hello Githubbers @bkeepers and @mtodd !
I apologize if my posting this comment is considered 'dead post resurrection' but as I currently have a use-case for this I searched and came across github/markup#364 which led me here.

Please don't judge me until the end. Conveying thoughts/feels/ideas in text is... limited.

I consider myself, like so many others amongst us, to be a prolific Gist user. Lately I've been finding more and more things that Gists just... do. And do them well.
Some very quick background: I listen to a lot of music podcasts while I'm working (predominantly electronic) and I frequently hear tracks that have me very "imustownthisomg". But in the spirit of taming my addiction to purchasing music on iTunes (which is serious. really serious.) I have kept a number of text files strewn about Dropbox collecting track information in hopes of having the wherewithal to force myself to wait to buy them.

Remember, you promised not to judge yet. The point is incoming.

These lists have ranged from overtly, almost uselessly simple text files:
Gabriel D'Or & Bordoy - Real Diamond [Bla Bla]
...

To overly-complex YAML files:
Podcasts:
  - Name: Phobiq Podcast 024 with Gabriel D'or & Bordoy
    Link: https://soundcloud.com/d2techno/phobiq-podcast-024-with
    Tracks:
      - Name: Gabriel D'Or & Bordoy - Real Diamond [Bla Bla]
        Link: https://itunes.apple.com/us/album/real-diamond/id829830612?i=829830635

Not only is managing these lists tedious and error-prone, but it's even more tedious to find a standard way to mark tracks as purchased once I actually do fork over my $1.29.
    Tracks:
      - Name: Gabriel D'Or & Bordoy - Real Diamond [Bla Bla]
        Link: https://itunes.apple.com/us/album/real-diamond/id829830612?i=829830635
        Purchased: true

Most importantly, the only thing keeping the list in my life is Dropbox, and if you have as much data in yours as I do in mine then you'll know what I mean when I say "where the hell did I put that file?...".
The Point, Finally
It would be amazing, amazing I tell you, if I could keep track of these in a gist. Now, that being said, I just created one earlier (https://gist.github.com/rex/20435e1783c585ebfa1b) which was awesome. "Finally", I said to myself, "Finally I have arrived at Providence! Badass text formatting and a badass checkbox that I can use to mark things as purchased in one click!". Well, that's when I tried to format it the way I really wanted to and came up empty.
See, it would be so, so amazing if I could turn this:

[ ] Zack Roth - Sleep Talking [Andy Bianchini Remix] Jaytech Music 085

Into this:

$?
Artist
Track
Remixed By
Label
Source

[ ]   |  Zack Roth  |  Sleep Talking  | Andy Bianchini  |  Nueva Records  |  Jaytech Music 085

The Point: Episode 2 - The Conclusion
Now, I know what you're thinking. "Pierce, that's just about the biggest first world problem I've ever heard.  It's absurd for me to even actually give it a second thought. It's a 100% aesthetic difference that only saves me a few seconds (likely less) and makes precisely zero tangible, calculable difference in my life.
But you know what? This is 'Murrca! Where would we be without the endless pursuit of shaving a few seconds here and there? Internal combustion engine ring any bells?!

I'm sitting on top of a bomb covered in shrapnel and creating a never-ending rabbit hole of petroleum dependency, war, environmental devastation, and consumerism but HOT DAMN AM I GOIN FAST!!!
-- One Great 'Murrcan

You see those colors? Those colors don't run! Making things go fast is the 'Murrcan Way™. I'm pretty sure that's in the Bible [citation needed].
The Bottom Line
This is 'Murrca. So the following logic applies:

If we don't 'Murrca, then the terrorists win.
If we don't make things go fast, then we didn't 'Murrca.
If we don't make formatting checkboxes in Gists fast, then we didn't make things go fast.

Thus, it follows logically that if we don't make formatting checkboxes in Gists fast then the terrorists win. And I for one am not going to stand by and let the terrorists win!
This means the only way for America to win is for you guys to let me help make formatting checkboxes in Gists exist. Give me a place to start hacking away and I'll go there with my Bald Eagle and emerge from the rubble victorious and unscathed.
Let's do this doggone thing.

Side note: I am sure there are more than a few great use cases for this functionality to exist, very likely better than mine. Heck, it wouldn't be hard to translate that type of functionality into something that would give parts of Basecamp a run for its money. But you know what, if 'Murrca isn't a good enough reason to make this happen then, well, the terrorists have already won.

:+1: for this feature. I just ran into this and was very disappointed.

Hi @rex, thanks for sharing your use case. And @jasonkeene for your support.
There's no contest that this would be a useful addition, I would love to have it. However, the problem isn't convincing me that it's a good idea: the problem is that it's a challenging feature to implement and isn't my top priority.
Anybody should feel free to contribute a Pull Request implementing this feature, I'll work with whomever to get it right. That said, I won't be tackling this problem any time soon.
Again, I agree this is a worthy feature addition, :+1:s won't convince me further (or help me prioritize it higher). A PR is the only contribution that will help make progress on this.
I'm debating closing (and locking) this issue to set expectations clearly but will leave it open for a bit longer (I haven't decided if it warrants closing/locking yet).

@mtodd Thanks for the honest reply. And for what it's worth, I at least somewhat apologize for the ridiculous first comment. There may have been a beer involved and it turns out that beer and GH issues are not great friends.
It makes complete sense to me why this isn't a very high priority. I wish it were different, but it's the way it is. Check boxes work fantastically in their current context/use case. I suppose I was hoping a picture of Ricky Bobby would sway your judgment.
All kidding aside, I would truly enjoy taking on the challenge of implementing this feature and submitting the PR, but I'm honestly not entirely sure how I would test it before submitting the PR. It seems most likely that the testing infrastructure for these task lists lies (correctly) behind the GitHub infrastructure wall. Is there a way that you can point me that would allow me to test the work before submitting? Specifically, to ensure that task list items marked as checked persist properly after page refresh?
I know you GitHubbers are busy people, I obviously don't expect your undivided attention. Any information you can give me regarding how best to test my changes would be appreciated, though!
Thanks again.

:+1:

I'd love to see this functionality as well.
Totally understand that you all have priorities just like everyone else, but I thought I'd add my vote.
Thanks for doing everything you do.
:+1:

:+1: Tried to use checkboxes in a table today :(

:+1:

:thumbsup:

I'm going to lock this issue to prevent further :+1:s. Agreed that this would be useful and the next step would be for someone to submit a PR to implement this functionality. Alternatively, a similar but distinct library could provide the behavior for tables (task_table?).
In any case, I won't be starting on this project and would encourage anybody interested in :+1:ing this issue to instead dig in and put together a PR which I will be happy to review and pull in if it makes sense to.


[Bug]: Mushroom Chip Card using light/dark mode color

Current Behavior
The HA theme mode (light or Dark) is overwriting the mushroom chip icon color. Setting the color on the chip via UI has no affect and chips that support automatic color like lights do not change.
Inspecting the icon shows that there are two color styles being applied. The actual correct color is one of them, but it seems to be trumped by the mode color 'rgb(225,225,225)' or 'rgb(33,33,33)'

Expected Behavior
Icon for the mushroom chip should be colored depending on the entity type and state.
Steps To Reproduce
This is happening on all dashboards, even if I create a new one. I've tried two different browsers, cleared cache and cookies, changed themes, removed the themes configuration from my configuration.yaml, manually tried to set icon color via UI or template chip, reinstalled mushroom icons via HACS, and restarted HA instance.
Environment
- OS: HA OS
- Browsers tested on: Chrome, FireFox, HA Companion app
- Hassio:2022.7.3

Anything else?
No response

Could not reproduce. Please send your YAML config for your chips.

I created a new dashboard to test. Here is the entire dashboard code with a few chip icons for testing.
`views:

title: Home
cards:

type: custom:mushroom-chips-card
chips:

type: template
content: |2-
{% if states.light | selectattr('state', 'eq', 'on')
| map(attribute='entity_id') | map('area_name')
| select('string')
| list | count  == 0 %}
{0}
{%else %}
{{states.light | selectattr('state', 'eq', 'on')
| map(attribute='entity_id') | map('area_name')
| select('string')
| list | count}}
{%- endif %}
icon: mdi:lightbulb
icon_color: |
{% if
(states.light | selectattr('state', 'eq', 'on')
| map(attribute='entity_id') | map('area_name')
| select('string')
| list | count) >= 1 -%}
red
{%- else -%}
blue
{%- endif %}
hold_action:
action: call-service
service: light.turn_off
service_data: {}
target:
area_id:
- 2_bedroom
- back_entrance
- dining_room
- front_entrance
- garage
- 1_bedroom
- kitchen
- living_room
- bedroom
- office
type: entity
entity: sensor.average_indoor_temperature
use_entity_picture: false
icon: mdi:home-thermometer
icon_color: purple
type: alarm-control-panel
entity: alarm_control_panel.home_alarm
type: entity
entity: lock.front_door_lock
name: Door
tap_action:
action: more-info
type: light
entity: light.office_ambient
use_light_color: true
type: entity
entity: sensor.panel_temperature
icon_color: red
alignment: center
`

Odd. Have you tried a ctrl+shift+r on default theme yet?
Works for me with
type: custom:mushroom-chips-card
chips:
  - type: entity
    entity: sensor.family_room_temperature
    icon_color: red

Same thing. I just swapped over to a different PC and tried as well with no luck.
Changed to the default theme using Auto mode (Firefox Browser using a dark theme) and created that same card you added but used my own sensor entity and had the same results.
The only thing I've seen that is able to change the colors is changing the mode from light mode to dark mode.
Dark mode: results in
<ha-icon style="--color: rgb(var(--rgb-red)); color: rgb(225, 225, 225);" class=" active "></ha-icon>
Light mode: results in
<ha-icon style="--color: rgb(var(--rgb-red)); color: rgb(33, 33, 33);" class=" active "></ha-icon>
And all of the chip cards have that "color: rgb(33, 33, 33);" or "color: rgb(225, 225, 225)" regardless if im manually setting the color via UI, a jinja template, or if its defaulting based on the cards logic.

Maybe you have a theme or a card that override the color ?

How could I check this? I've tried changing the theme from the drop down list and all of them have the same effect. I've also tried removed the theme folder from the configuration.yaml and restarted my instance with the no luck.
The real weird thing is that I've only been able to see this issue on the mushroom-chip card.

Which custom cards are installed with HACS? Can you list them?

I've figured it out and and I'm sorry for the time wasted!
It seems like there was an issue with my card-mod installation. I started the process of removing cards and re-installing them. I dont know what exactly changed but I removed my card-mod card (which broke a lot of things...) and then when I re-installed it, I had color!!!
I currently have the latest version of card-mod that is available through HACS 3.1.5. There is a chance I had an older version even though HACS hadn't told me I had an update, but I didnt check the version number so I am not sure if that was the case.
Thank you for working with me through this.


2.0.0 react universally doesn't work anymore

Hi,
I use React Universally and have been using styled-components 2.0.0-x for a while now. After upgrading to 2.0.0-16 or 2.0.0-17, my page doesn't load anymore. It just hangs. There is no visible error. Up to and including 2.0.0-15, it works fine.
I use react-async-component and server side loading. Not sure what to look for.

Are you able to submit more material, so we can try to figure out what's going on? Optimally a repository to reproduce maybe? Can you also post how you're using SSR with Styled Components, since the SSR API has changed?

I've never used styled components for SSR in a special way. Where can I read about the SSR changes, so I can verify if that is the problem?

Hmm, so I made the changes and I'm getting errors:
const sheet = new ServerStyleSheet();

const app = (
<AsyncComponentProvider asyncContext={asyncComponentsContext}>
	<StyleSheetManager
		sheet={sheet}
	>
		<App />
	</StyleSheetManager>
</AsyncComponentProvider>
);

asyncBootstrapper(app).then(() => {
const appString = renderToString(app);

// Generate the html response.
const html = renderToStaticMarkup(
  <ServerHTML
	  reactAppString={appString}
	  nonce={nonce}
	  helmet={Helmet.rewind()}
	  css={sheet.getStyleElement()}
	  asyncComponentsState={asyncComponentsContext.getState()}
  />,
);

The error
Warning: Failed prop type: Invalid prop `sheet` of type `ServerStyleSheet` supplied to `StyleSheetManager`, expected instance of `StyleSheet`.
	in StyleSheetManager (at index.js:59)
Error walking your react tree
TypeError: styleSheet.getName is not a function
	at ComponentStyle.generateAndInjectStyles (/project/node_modules/styled-components/lib/models/ComponentStyle.js:53:37)
	at StyledComponent.generateAndInjectStyles (/project/node_modules/styled-components/lib/models/StyledComponent.js:117:38)
at /project/node_modules/styled-components/lib/models/StyledComponent.js:141:43
	at subscribe (/project/node_modules/styled-components/lib/utils/create-broadcast.js:31:7)
	at StyledComponent.componentWillMount (/project/node_modules/styled-components/lib/models/StyledComponent.js:132:28)

The documentation is incorrect right now, you'll need to supply sheet.instance to that prop. But you should also be able to just use the method, described in the docs, in this case.

Hmm, well using sheet.instance resolved the error. Unfortunately, we're back to "it hangs without visible error".
Tried multiple things, such as using jsx around AsyncComponentProvider and using the sheet.collectStyles method
asyncBootstrapper is based on react-async-component
Any suggestions?

I'll set up a react universally repo
On Wed, May 3, 2017, 17:08 Phil Plückthun<EMAIL_ADDRESS>wrote:

The documentation is incorrect right now, you'll need to supply
sheet.instance to that prop. But you should also be able to just use the
method, described in the docs, in this case.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/styled-components/styled-components/issues/762#issuecomment-299020634,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAXfv1HhvgP5otyEKPS1VrMd7GCiYr-Gks5r2N6tgaJpZM4NO1uU
.

--
Kind regards,
Marc
M.Schipperheyn

my app breaks changing from "2.0.0-15", to "2.0.0-16",
Because of TypeError: _StyleSheet2.default.getCSS is not a function
I am using nextjs.

@pungggi I recommend referencing the new docs. https://sc-next-docs.philpl.com/docs/advanced#server-side-rendering Although, they are apparently not 100% complete and correct yet.

@philpl  Ok, created a repo for you.
https://github.com/mschipperheyn/react-universally
There are 2 branches:
https://github.com/mschipperheyn/react-universally/tree/styled-components-762 - a hanging implementation with v2.0.0-17
https://github.com/mschipperheyn/react-universally/tree/styled-components-v2-15 - a working implementation with v2.0.0-15
In both cases, just npm install and npm run develop to get the website up.

Sorry for unscoping this from v2 after rescoping it. I'd guess it's an issue with the AsyncComponentProvider + Styled Components, but I haven't looked into it.
I'm pretty sure it's just about getting the setup right and not a weird edge case. I'll still try to look into it, but I think I won't be able to solve this before the v2 release. Sorry again

Yeah, just tried it with 2.0.0 and it is indeed not working. Updated the repo.

I'm also having issues. I'm not using this boilerplate but I am using react-async-component and async bootstrapper. Possibly related?

@mschipperheyn Possibly related to https://github.com/styled-components/styled-components/issues/883 ?

@mschipperheyn Looks like our babel-plugin with the ssr option fixes it for @scf4. How about your repo? :)

Nope, added the babel-plugin on this test repo I prepared and added the ssr: true. Still a "hanging" load. I updated the repo

@mschipperheyn Any luck getting these two libraries to play well together?
@philpl Any updates/thoughts?

Hi I was directed here from https://github.com/ctrlplusb/react-universally/issues/297
Here is a gist of a project I just started that seems to have styled-components working for me:
https://gist.github.com/designspin/c11095334ae1f105d1f93123232d37fd

@designspin are you using async components? Because I have a very similar setup that is still not working which is inline with docs. I think async components are the reason it's not working.

@mschipperheyn is it any form of async components or a specific library? Are you seeing it with, say, react-loadable?

If I get time this week, i'll try adding the changes detailed in my Gist to a fresh install of react-universally and see what the outcome is then. I am using the async components, although I only have one route at present outputting to main chunk, i'll let you know what happens when I add a few more later on. Thanks.

I set up a react universally lib for testing. The info is above. But perhaps good to start fresh. I have it specifically with react-async-component https://github.com/ctrlplusb/react-async-component. I am working on a test that involves the import promise async loading

It seems someone has a clear path of solving this issue. Once you switch to the react element output for the SSR'd CSS code this problem goes away. I'm not sure why, but I'm sure it can't be related to our html string output or anything similar.
To be honest, apart from what @mschipperheyn posted at some point, I haven't seen a clear description of this bug either. So I'm going to go ahead and close this for now


Add FIPS mode builders

Add new fips optional bool in builder list.
On any platform, handle fips: true by passing run-builder a -fipsmode flag that sets GOFIPS=true before running tests.
On Windows, also enable system-wide FIPS using the registry package.
Change the test run names from the job ID mess:
linux_default_default_amd64_test_default_False to the human-readable name, instead:
linux-amd64 test

linux-amd64 test [opensslcrypto] FIPS
windows-amd64 test [cngcrypto] FIPS

This actually fills a gap in our Linux/OpenSSL tests since the boring branch merge. The boring branch used an image that sets GOFIPS=true:
https://github.com/microsoft/go/blob/ae8300fc957c60070df9846e4571085df9db128b/eng/pipeline/jobs/run-job.yml#L29-L30
And this isn't the case in microsoft/main:
https://github.com/microsoft/go/blob/39476b4a06b19a3b241c3c3e7a036632254aec66/eng/pipeline/jobs/run-job.yml#L38-L39
We need to run both in FIPS and not in FIPS in microsoft/main, so we need flexibility, and I think putting it in run-builder is a reasonable place, rather than picking different base images in the yml.

TODO: Test to make sure that setting the registry entry like this actually has the effects it should, in practice.

CNG PR has been merged. Would be good to rebase and run test again.


increase mysql max_connections to 1k

Would it make sense to make this configurable? I'm just thinking that this affects file descriptor usage as well, so there might be deployments where we want a lower value.

I'm on the fence. I don't think it hurts us much to have a higher water mark. Given it wasn't a tuneable before, I'm okay with just a bump of the hard set number.

retest

retest


Consider changing environment specification to Python 3.9

We know that napari doesn't always work well on Big Sur on Python <3.9, so that should probably be our preferred environment.

eek ok - is that easy?

done!


Fix replication Javascript test

The test was flaky for a variety of reasons:

waitForSeq only waited for 3 seconds and on failure it never explitly
indicated an error and just waited for the comparison below to fail. So made
it wait for 30 seconds and also throw an exception right away if it fails.

Last waitForSeq was used after task was canceled. So it just wasted time
waiting until timeout as the task was null. So created a function to
wait for task to be null.

waitForSeq spun in a tight do/while loop querying _active_tasks. In some test
environment with minimal CPU resources that's not the greatest thing to do.
So made it wait for 0.5 seconds between retries.

waitForSeq waited for replication task's through_seq value to match source
update sequence from source db info. Those don't necessarily match. Instead
made waitForSeq use the changes feed last sequence since that's what the
replication task uses to update through_seq.

Tested on a CPU and disk resource constrained VM
CPU resources slowed down to 9% and disk throughput limit set at 100KB/sec
VBoxManage bandwidthctl ${VM} set Limit --limit 100KB
Seems to pass when before it failed:
 test/javascript/run replication.js
test/javascript/tests/replication.js   pass
=======================================================
JavaScript tests complete.
  Failed: 0.  Skipped or passed: 1.

+1

Sadly we have a new failure scenario now. I'm going to reopen #634.


I am building an app that would act as a remote for presentations. I would like to use the volume buttons to trigger some sort of event. Can I capture hardware button clicks in flutter?

I am building an app that would act as a remote for presentations. I would like to use the volume buttons to trigger some sort of event. Can I capture hardware button clicks in flutter?

Well, this is exactly what this package offers. Didn't you read the readme?


Cannot Read Type of Contravariant Property

Given a class like:
class Lambda<-Input, +Output> {
  -input: Input;
  +output: Output;
}

I would expect to be able to use the $PropertyType utility to read the type of the input property on a Lambda. However, flow does not seem to allow this with [arrow ]functions, giving the error:
Cannot instantiate `$PropertyType` because property `input` is not readable.

See the Flow Error here for a more concrete example of this. Is this a bug or is there some other principle being violated here? The function isn't reading from this "write-only" property of the instance, so I wouldn't expect flow to error.

This is expected.


Possible edge case

I'm not sure what I'd expect velin to do here but just pointing out that it doesn't currently recognize the returns as a section in this docstring, instead treating it as another parameter. I suppose there is a fundamental ambiguity here unfortunately, so it may not be fixable, but perhaps should be flagged?
def f(blarg):
    """
    Parameters
    ----------
    blarg : bool
        some description
    returns
    -------
    init_val, control
    """
    pass

gives this output:
(mpl-inter) ian@fermented-beans:~/Documents/jupyter/mpl-interactions$ velin v_test.py
~/mambaforge/envs/mpl-inter/lib/python3.9/site-packages/velin/ref.py:513 in  | v_test.py:f
~/mambaforge/envs/mpl-inter/lib/python3.9/site-packages/velin/ref.py:514 in  |   missing: set()
~/mambaforge/envs/mpl-inter/lib/python3.9/site-packages/velin/ref.py:515 in  |   extra: {'-------', 'returns', 'init_val', 'control'}
~/mambaforge/envs/mpl-inter/lib/python3.9/site-packages/velin/ref.py:513 in  | v_test.py:f
~/mambaforge/envs/mpl-inter/lib/python3.9/site-packages/velin/ref.py:514 in  |   missing: set()
~/mambaforge/envs/mpl-inter/lib/python3.9/site-packages/velin/ref.py:515 in  |   extra: {'-------', 'returns', 'init_val', 'control'}

This is an issue in numpydoc parsing. you actually do need a blank line  before Returns


Use GitHub actions to build release?

see: https://github.com/features/actions

It's not viable per se, I tried it and its not as flexible as using a full CI


I run yourcode on SPTLS3D dataset,the miou is very low

maybe there is something wrong,can you give me some advice

I think this might be an overfit, do you have any suggestions


fix $apply already in progress bug

refer to https://github.com/mobxjs/mobx-angularjs/issues/17

Codecov Report

Merging #18 into master will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff          @@
##           master    #18   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files           1      1
  Lines          10     10
  Branches        2      2
=====================================
  Hits           10     10

Impacted Files
Coverage Δ

src/index.ts
100% <100%> (ø)
: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 1391bde...00143ef. Read the comment docs.


update deps

I can do nothing about it until I find a Windows device.

Maybe we can upgrade one by one. This is also the easiest way to upgrade deps.

I found that the reason for CI failure is prettier.
Maybe we can skip this step in Windows CI.

I skipped the format check on windows...

We should run npm run release to update dist/index.js

BTW. The command npm run release is ambiguous. it makes people confuse.

Could we merge this first? I will continue to make some changes tomorrow.


Wintertodt Breaking Brazier Color

When doing Wintertodt, I sometimes have trouble seeing the snow above the braziers when they're about to break because it is white-on-white.
I think a good improvement to the Wintertodt plugin would be to highlight the snow entities or the tiles in red when the player should move, and since it only adds extra contrast for an existing notification, I don't think it would be something Jagex would oppose.

As much as Wintertodt is considered a skilling activity by most of the community, this is still technically a boss, and such a feature would run afoul of the following lines of Jagex's statement:

Indicates the time where a boss mechanic may start or end
Adds additional visual or audio indicators of a boss mechanic


Additions to the subform documentation

#550
Configuration options for subform table.

@HauklandJ take a look at the latest and see if you're happy with the changes.


demo video link gives 404 error

link appears to have a double-quote at the end that shouldn't be there.

Tahnks.


Use a Trait with the Message class

removed unused code
Ref #7

Coverage decreased (-5.3%) to 74.282% when pulling<PHONE_NUMBER>2deb54cb1e97267b912d062ec3dcca on feature-7 into 37ef2faf9b521146f3a5fb53f6d64b7d65bf11e9 on master.

Coverage decreased (-5.3%) to 74.282% when pulling<PHONE_NUMBER>2deb54cb1e97267b912d062ec3dcca on feature-7 into 37ef2faf9b521146f3a5fb53f6d64b7d65bf11e9 on master.

Coverage decreased (-2.1%) to 77.403% when pulling<PHONE_NUMBER>ff8a82fa741781bb93b3a9564708a1 on feature-7 into 37ef2faf9b521146f3a5fb53f6d64b7d65bf11e9 on master.

Coverage decreased (-1.3%) to 78.25% when pulling d1b636d0d9c82eb6d5ce17f40255b732a8f0f753 on feature-7 into 37ef2faf9b521146f3a5fb53f6d64b7d65bf11e9 on master.

Coverage decreased (-1.3%) to 78.25% when pulling 48188c8da2c682b78473286cdad2edf8e71125b4 on feature-7 into 37ef2faf9b521146f3a5fb53f6d64b7d65bf11e9 on master.

Coverage increased (+9.3%) to 88.834% when pulling d3e20e0cca895c23896a6f6ae9c3d9d66c6d950e on feature-7 into 37ef2faf9b521146f3a5fb53f6d64b7d65bf11e9 on master.


Feat: Lynk RPC Preparation

Description
Please include a summary of the change and which issue has been fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Fixes #59
Type of change
Please update the title of this PR to reflect the type of change. (Delete the ones that aren't required).

[x] New feature (non-breaking change which adds functionality) [title: 'feat:']
[x] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[x] This change requires a documentation update

Testing
Please make sure that existing test cases pass (with go test ./... -race and go test -bench=. ./... -race),
and if required please add new test cases and list them below:
All test cases pertaining to Frisbee connections have been updated, and test cases in the pkg/Packet module have been created.
Benchmarking
Frisbee tries to adhere to strict performance requirements, so please make sure to run go test -bench=. ./... and paste the results below:
Benchmarking Results:
goos: darwin
goarch: arm64
pkg: github.com/loopholelabs/frisbee
BenchmarkAsyncThroughputPipe/32_Bytes-10                      80          14109945 ns/op         226.79 MB/s      821757 B/op     100265 allocs/op
BenchmarkAsyncThroughputPipe/512_Bytes-10                     69          17710251 ns/op        2890.98 MB/s      827182 B/op     100405 allocs/op
BenchmarkAsyncThroughputPipe/1024_Bytes-10                    51          22858920 ns/op        4479.65 MB/s      840082 B/op     100553 allocs/op
BenchmarkAsyncThroughputPipe/2048_Bytes-10                    40          28997430 ns/op        7062.69 MB/s      832183 B/op     100349 allocs/op
BenchmarkAsyncThroughputPipe/4096_Bytes-10                    25          45807188 ns/op        8941.83 MB/s      841764 B/op     100720 allocs/op
BenchmarkAsyncThroughputPipe/1mb-10                            1<PHONE_NUMBER> ns/op        99750.52 MB/s   94265008 B/op     137301 allocs/op
BenchmarkAsyncThroughputNetwork/32_Bytes-10                   87          15612723 ns/op         204.96 MB/s      817222 B/op     100037 allocs/op
BenchmarkAsyncThroughputNetwork/512_Bytes-10                  45          28804448 ns/op        1777.50 MB/s      809793 B/op     100036 allocs/op
BenchmarkAsyncThroughputNetwork/1024_Bytes-10                 39          34522701 ns/op        2966.16 MB/s      813449 B/op     100034 allocs/op
BenchmarkAsyncThroughputNetwork/2048_Bytes-10                 24          43996290 ns/op        4654.94 MB/s      832169 B/op     100055 allocs/op
BenchmarkAsyncThroughputNetwork/4096_Bytes-10                 21          53019544 ns/op        7725.45 MB/s      858459 B/op     100062 allocs/op
BenchmarkAsyncThroughputNetwork/1mb-10                         1<PHONE_NUMBER> ns/op        100092.33 MB/s  203903720 B/op    101339 allocs/op
BenchmarkClientThroughput/test-10                             46          24865066 ns/op        2059.11 MB/s      819905 B/op     100058 allocs/op
BenchmarkClientThroughputResponse/test-10                     67          18377911 ns/op        1825.77 MB/s      541525 B/op      65571 allocs/op
BenchmarkThroughput/test-10                                   57          23081383 ns/op        1453.72 MB/s      552083 B/op      65684 allocs/op
BenchmarkThroughputWithResponse/test-10                       60          21519821 ns/op        1559.21 MB/s      536695 B/op      65540 allocs/op
BenchmarkSyncThroughputPipe/32_Bytes-10                        7         160555149 ns/op          19.93 MB/s     1600572 B/op     200006 allocs/op
BenchmarkSyncThroughputPipe/512_Bytes-10                       7         162084292 ns/op         315.89 MB/s     1601539 B/op     200013 allocs/op
BenchmarkSyncThroughputPipe/1024_Bytes-10                      7         159316607 ns/op         642.75 MB/s     1601034 B/op     200006 allocs/op
BenchmarkSyncThroughputPipe/2048_Bytes-10                      7         159968351 ns/op        1280.25 MB/s     1600414 B/op     200002 allocs/op
BenchmarkSyncThroughputPipe/4096_Bytes-10                      6         167863618 ns/op        2440.08 MB/s     1602921 B/op     200005 allocs/op
BenchmarkSyncThroughputPipe/1mb-10                             1<PHONE_NUMBER> ns/op        44193.78 MB/s   13313592 B/op     200061 allocs/op
BenchmarkSyncThroughputNetwork/32_Bytes-10                     3         503513931 ns/op           6.36 MB/s     1600394 B/op     200008 allocs/op
BenchmarkSyncThroughputNetwork/512_Bytes-10                    2         655643562 ns/op          78.09 MB/s     1601064 B/op     200010 allocs/op
BenchmarkSyncThroughputNetwork/1024_Bytes-10                   3         410320500 ns/op         249.56 MB/s     1600992 B/op     200006 allocs/op
BenchmarkSyncThroughputNetwork/2048_Bytes-10                   2         612692208 ns/op         334.26 MB/s     1604176 B/op     200011 allocs/op
BenchmarkSyncThroughputNetwork/4096_Bytes-10                   2         731523416 ns/op         559.93 MB/s     1615160 B/op     200021 allocs/op
BenchmarkSyncThroughputNetwork/1mb-10                          1<PHONE_NUMBER>8 ns/op       10035.67 MB/s   19195488 B/op     200114 allocs/op
PASS
ok      github.com/loopholelabs/frisbee 60.274s
goos: darwin
goarch: arm64
pkg: github.com/loopholelabs/frisbee/internal/protocol
BenchmarkEncodeHandler-10               170914500                6.935 ns/op
BenchmarkDecodeHandler-10               186285698                6.383 ns/op
BenchmarkEncodeDecodeHandler-10         78061472                15.09 ns/op
BenchmarkEncode-10                      180105733                6.554 ns/op
BenchmarkDecode-10                      249070460                4.946 ns/op
BenchmarkEncodeDecode-10                92686458                13.05 ns/op
PASS
ok      github.com/loopholelabs/frisbee/internal/protocol       9.840s
PASS
ok      github.com/loopholelabs/frisbee/internal/ringbuffer     0.103s
PASS
ok      github.com/loopholelabs/frisbee/pkg/packet      0.081s

Linting
Please make sure you've run the following and fixed any issues that arise:

[x] trunk check has been run

Final Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] Any dependent changes have been merged and published in downstream modules
[x] I have checked my code and corrected any misspellings

Theeere we go, had to get rid of all the flaky tests that were timing out because of the ridiculous amount of data being pushed through

Okay, all the minor bug fixes are done, all future work will be done in the "rpc-async" branch, this PR is 100% ready for review


bump tsp version to 0.56.0

to sync up emitter changes in https://github.com/Azure/autorest.csharp/pull/4719

closed in favor of https://github.com/microsoft/typespec/pull/3386


pod 'RNAdvertisingId', :path => '../node_modules/react-native-advertising-id/'

react-native version latest 0.60.5 version I got this issue

+1

Which version of the library are you using?


[FEATURE] Request to Implement Hover Effects and Animations on Cards in Event and Shop Pages

Description
I would like to propose the addition of hover effects and animations on all cards displayed on the event and shop pages. By incorporating these dynamic visual elements, we can make the user experience more engaging and visually appealing. When users hover over the cards, they will be greeted with interactive animations that capture their attention and provide a delightful browsing experience.
I am excited to contribute to this feature implementation and kindly request permission to proceed with adding hover effects and animations to the cards. Thank you.
I am eager to contribute to this issue and would appreciate being assigned this task under GSSOC'23.
Screenshots
No response
🥦 Browser
Google Chrome
Checklist ✅

[X] I checked and didn't find similar issue
[X] I have read the Contributing Guidelines
[X] I am willing to work on this issue (blank for no)

Someone else also raised the same kind of issue 4 days ago #714  - please always check for duplicates before you proceed to make an issue.
Anyways I will temporarily lock this, as I am waiting for them to reply, if they don't in the next few days we can proceed. Thanks.

Hi @AkanshaMundel , you can start to work on this - as #714 was closed because of inactivity. Make sure to raise a PR once done.
Good PR makes a Good Developer !
We at Milan work hard to maintain the structure, and use conventional Pull request titles and commits.
Please make sure that you have read our documentation on Commiting guidelines and Pull request guidelines.
Without a proper template for the PR, not following the guidelines and spam might get the pull request closed, or banned.


[Terraform]create compute instance

Create OCI components using Terraform.

Compute instance

Script has no problem.
Merge
(But, It cannot create instance resource because out of capacity issue =>  #3  )


Implement proper key syntax for weak sets

TODO
This should be allowed:
many[X].weak.ref[...]

This must be prohibited, it makes no sense:
many[X].weak.add[...]

Not relevant.
RN I've implemented this and it's okay:
  many[WeakSetTest]
      .weak[WeakSetGood]
      .weak[WeakSetBad]


GoogleNet aux is None in pytorch test

When running
TVM_FFI=ctypes python -m pytest -v /home/liuwenjian/incubator-tvm/tests/python/frontend/pytorch/test_forward.py -k "test_googlenet"
error will occur at
https://github.com/apache/incubator-tvm/blob/90bde33e60a3ae0d18a767eba9a2092eab204788/tests/python/frontend/pytorch/test_forward.py#L179
the error message is
"
assert(isinstance(orig, torch.nn.Module))
E       AssertionError
anaconda3/lib/python3.7/site-packages/torch/jit/init.py:2195: AssertionError
"
This is because when getting googlenet pretrained model, the aux module is always None. Therefore the assert will fail
torch.version='1.6.0+cu101'
tvm.version='0.7.dev1'

PyTorch 1.6 is not supported yet, a PR welcome.

I'll try this one, thanks!


Any wsl command is met with access denied after installing ubuntu 24

Windows Version
Microsoft Windows [version 10.0.22631.3527]
WSL Version
'Access denied' | ubutnu 24.04 LTS or Ubuntu 20.04.6 LTS
Are you using WSL 1 or WSL 2?

[X] WSL 2
[ ] WSL 1

Kernel Version
Access denied
Distro Version
Ubuntu 24.04 LTS
Other Software
Wsl Ubuntu 20.04.6 LTS
Windows Terminal Version : 1.19.11213.0
Powershell 7.4.2
I had wsl2 with ubuntu 20 for a while, no issue there. I wanted to switch to the latest LTS and added ubuntu 24 through the store. Using Terminal it worked fine. I did not want to unregister the previous ubuntu version until I was sure I would still have everything working fine. Booting my computer this morning, every wsl command is met with 'access denied'.
Edit: Running as admin does no difference.
Repro Steps
Install Ubuntu 24 through the store, reboot the computer.

Open a terminal and run > wsl

Try to read wsl installed distros: > wsl -l

Expected Behavior

Wsl default distro is launched.
Powershell returns the list of installed linux distributions

Actual Behavior

PS C:\Users\jsandrin> wsl
Accès refusé.

PS C:\Users\jsandrin> wsl -l
Accès refusé.

Diagnostic Logs
WslLogs-2024-05-06_10-09-13.zip

Similar issues seems to all have been closed without author answers.
Launching Ubuntu from the store does not work either.
I just found out that I can run the wsl program but not the 'ubuntu' one.
Inside wsl I could check my version:
jsandr@SST-JSA:~$ uname -a
Linux SST-JSA <IP_ADDRESS>-microsoft-standard-WSL2 #1 SMP Fri Mar 29 23:14:13 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

As shown in this screenshot I was able to run wsl but not ubuntu

Thank you @jsandr.
Looking at the logs, this looks like the MSIX installation might be broken, but I wonder if you can call wsl.exe directly.
Does calling: C:\Program Files\WSL\wsl.exe work ?

Hi @OneBlue, yes wsl.exe does work.

Hi @OneBlue, yes wsl.exe does work.

Ok then this is indeed an MSIX issue.
Does re-installing the latest package solve the issue ?

Hi,
Re-installing throws this:

As any wsl commands are refused I could not un-register Ubuntu 24, so I went to 'add or remove apps' and uninstalled both Ubuntu 20 and 24. Removed all startup calls to wsl or terminal. Rebooted then tried install via the .msi
After it failed I went to the store, installed Ubuntu 24 again (it worked ?!). Now I'm back with an Ubuntu 24 app but still unable to launch it directly.
Only noticeable difference is that now when trying to launch a wsl command via powershell this is the answer I have:

Hi, I just found out that my home is not at ~ but is at ü

Anyone else with a better idea than re-installing in loops until it starts working again ?

No, but I'm also having massive issues with ubuntu 24. After about 10 minutes, systemd entirely locks up (took forever just to get that much information) and it seems the last windows update did it in. Super frustrating.

Hi @OneBlue, yes wsl.exe does work.

Ok then this is indeed an MSIX issue.
Does re-installing the latest package solve the issue ?

I'm having similar issues. Any wsl command is met with "Access is denied". If I run it from the Program Files it does seem fine but applying updates doesn't seem to resolve.

I've tried completely uninstalling and disabling the feature but no luck there either.
One strange thing I found is that if I go into the "Windows Subsystem for Linux" system component and then reset the component. The first command will run with WSL but after that it immediately goes back to "Access is denied" on subsequent commands. I'm using a relatively fresh Windows 11 install.

Example where I "reset" and then run two commands:

Hi, I installed windows updates KB5035942 and KB5037853 which enabled Ubuntu again.

> wsl -l
Distributions du Sous-système Windows pour Linux :
Ubuntu-24.04 (par défaut)
Ubuntu-20.04

Now I'm missing the GUI, apps like meld or gitg starts a process but remains hanging without launching a new window.

I wonder if this is related to a systemd bug that causes nearly the entire WSL instance to completely hang after running for about 10/15 minutes. IIRC, ubuntu 24 starts systemd by default (check in /etc/wsl.conf). I set it to false and things seem to be working much better.

Windows Version
Microsoft Windows [version 10.0.22631.3527]
WSL Version
'Access denied' | ubutnu 24.04 LTS or Ubuntu 20.04.6 LTS
Are you using WSL 1 or WSL 2?

[x]  WSL 2
[ ]  WSL 1

Kernel Version
Access denied
Distro Version
Ubuntu 24.04 LTS
Other Software
Wsl Ubuntu 20.04.6 LTS Windows Terminal Version : 1.19.11213.0 Powershell 7.4.2
I had wsl2 with ubuntu 20 for a while, no issue there. I wanted to switch to the latest LTS and added ubuntu 24 through the store. Using Terminal it worked fine. I did not want to unregister the previous ubuntu version until I was sure I would still have everything working fine. Booting my computer this morning, every wsl command is met with 'access denied'.
Edit: Running as admin does no difference.
Repro Steps
Install Ubuntu 24 through the store, reboot the computer.

Open a terminal and run > wsl
Try to read wsl installed distros: > wsl -l

Expected Behavior

Wsl default distro is launched.
Powershell returns the list of installed linux distributions

Actual Behavior
PS C:\Users\jsandrin> wsl
Accès refusé.

PS C:\Users\jsandrin> wsl -l
Accès refusé.

Diagnostic Logs
WslLogs-2024-05-06_10-09-13.zip

I migrated all of my WSL distros from the C: drive to a high capacity external drive about 2 years ago and since I did that, I have not had the same problems I was having with WSL. All my distros function pretty well now. There are some minor bugs using nano that are annoying but that's about all I've had issues with since. I have not seen a WSL related accessdenied error since then. I migrated them to reclaim some disk space on C:, but in the process it seems to have fixed the accessdenied errors I had been getting from time to time, so that was a nice bonus.


SoundCloud does not emit new api credentials

Might want to remove SoundCloud from the list of music apis given that at the moment no new apps can be registered.
see: https://github.com/soundcloud/api#can-i-request-an-api-key-for-a-new-app

Thanks for pointing it out @egm0121
Would you like to make a PR regarding the same?


Elevation???

Unable to add elevation or shadow to bottom tab bar, I don't want to add stroke.
Is there anyway to add shadow to its top side on android.

Hi @Jamal-ReachFirst ,
I’m working on it.

Hi @Jamal-ReachFirst , I’m working on it.

I am using react-native-drop-shadow to apply shadow.
Make some changes in react-native-curved-bottom-bar:
import DropShadow from "react-native-drop-shadow";

<DropShadow
    style={{
      shadowColor: "#DDDDDD",
      shadowOffset: {
        width: 0,
        height: 0,
      },
      shadowOpacity: 1,
      shadowRadius: 5,
    }}
  >
      <SVG width={maxWidth} height={height + (type === 'DOWN' ? 0 : 30)}>
        <PATH
          fill={bgColor}
          stroke="#DDDDDD"
          strokeWidth={strokeWidth}
          {...{ d }}
        />
      </SVG>
  </DropShadow>

Thanks.

Hi @Jamal-ReachFirst , I’m working on it.

I am using react-native-drop-shadow to apply shadow.
Make some changes in react-native-curved-bottom-bar:
import DropShadow from "react-native-drop-shadow";

<DropShadow
    style={{
      shadowColor: "#DDDDDD",
      shadowOffset: {
        width: 0,
        height: 0,
      },
      shadowOpacity: 1,
      shadowRadius: 5,
    }}
  >
      <SVG width={maxWidth} height={height + (type === 'DOWN' ? 0 : 30)}>
        <PATH
          fill={bgColor}
          stroke="#DDDDDD"
          strokeWidth={strokeWidth}
          {...{ d }}
        />
      </SVG>
  </DropShadow>

Thanks.

Thank you very helpful.

hi All, Top shadow do not working on Android. I'm find solutions.

hi All, Top shadow do not working on Android. I'm find solutions.

What is the solution, when are you going to push it to this package?

hi All, Top shadow do not working on Android. I'm find solutions.

can I know what is the solution ?

react-native-drop-shadow

react-native-drop-shadow use this

did you have example code for reference ?

did you have example code for reference ?

As shown here
import DropShadow from "react-native-drop-shadow";

<DropShadow
    style={{
      shadowColor: "#DDDDDD",
      shadowOffset: {
        width: 0,
        height: 0,
      },
      shadowOpacity: 1,
      shadowRadius: 5,
    }}
  >
      // child component
  </DropShadow>

hi All,
This issue is resolved. Please install version 3.1.0 Later re-build app.
add shadow (9fb40da)

hi All, This issue is resolved. Please install version 3.1.0 Later re-build app. add shadow (9fb40da)

@hoaphantn7604 Thanks for your efforts and hard work, the shadow is working now but I am unable to change the shadow properties (no method/prop provided to override the existing shadow style).
I am manually changing the shadow style inside react-native-curved-bottom-bar/src/CurvedBottomBar/Components/BottomBarView/styles.ts
shadow: {
    shadowColor: '#DDDDDD',
    shadowOffset: {
      width: 0,
      height: 0,
    },
    shadowOpacity: 1,
    shadowRadius: 5,
  },

Can you please provide a method/prop to override this style??

hi All, This issue is resolved. Please install version 3.1.0 Later re-build app. add shadow (9fb40da)

@hoaphantn7604 Thanks for your efforts and hard work, the shadow is working now but I am unable to change the shadow properties (no method/prop provided to override the existing shadow style).
I am manually changing the shadow style inside react-native-curved-bottom-bar/src/CurvedBottomBar/Components/BottomBarView/styles.ts
shadow: {
    shadowColor: '#DDDDDD',
    shadowOffset: {
      width: 0,
      height: 0,
    },
    shadowOpacity: 1,
    shadowRadius: 5,
  },

Can you please provide a method/prop to override this style??

This issue is resolved. Install new version. You can use shadowStyle props.

It's not working in Android. It's not showing any shadow


Different version in master, compared to that on the hardware

Version 0.9.11 is in master at the moment, but version 0.9.12 shipped on the devices in batch 2 of the Tindie run.
Was there much changed between those versions? (It might be worth using Github tags to keep track of the versions as you create them)
@DustinWatts can you push the 0.9.12 code to github so we can see if anything important needs to be included in things like #51 or #52 please?

Hi @danielhunt Nothing has changed since 0.9.11, when I made the binary that I used to flash the ESP32 TouchDown, I accidentally set the version number to 0.9.12 but that should be version 0.9.11.
The only thing different is that USECAPTOUCH and speakerPin are defined.
Hope this explains the difference in version numbers. Feel free to reopen if not.


master reboot test is failing

This seemed to slip into the master branch during when the tests were temporarily broken over some of the self-hosted-flannel changes. If I reboot a master node, the api-server doesn't come back up. @aaronlevy is already on it and suspects what the problem is.

There are a few different issues at play here - but the core issue seems to be that the checkpointer is relying on determining local state from the kubelet /pods api - but that api may not reflect accurate local state.
Unfortunately that kubelet api endpoint will just report state from the last time it was able to successfully contact an api-server. Essentially a cache of the last state reported to api.
We didn't have this same issue with the old checkpointer - because it would determine "api is running" by reaching out to an api -- but that isn't reliable in multi-master, or for generic checkpointing.
This is a rather disappointing discovery -- as it seems there is no way to easily determine the local pod state if an api-server is not available.
Some options moving forward:

Go back to hard-coded expectations (e.g. curl localhost:8080)
Extract liveness probes from pod specs and try to use those if available
Add some kind of "last seen" annotation to checkpoint parent pods, where we expect to see an update within a particular time window.
Longer term option: make use of CRI interface and inspect state ourselves

/cc @yifan-gu @dghubble

Just to be sure, does this affect 0.3.2 only or 0.3.1 too?

On Jan 6, 2017, at 18:18, Aaron Levy<EMAIL_ADDRESS>wrote:
There are a few different issues at play here - but the core issue seems to be that the checkpointer is relying on determining local state from the kubelet /pods api - but that api may not reflect accurate local state.
Unfortunately that kubelet api endpoint will just report state from the last time it was able to successfully contact an api-server. Essentially a cache of the last state reported to api.
We didn't have this same issue with the old checkpointer - because it would determine "api is running" by reaching out to an api -- but that isn't reliable in multi-master, or for generic checkpointing.
This is a rather disappointing discovery -- as it seems there is no way to easily determine the local pod state if an api-server is not available.
Some options moving forward:
Go back to hard-coded expectations (e.g. curl localhost:8080)
Extract liveness probes from pod specs and try to use those if available
Add some kind of "last seen" annotation to checkpoint parent pods, where we expect to see an update within a particular time window.
Longer term option: make use of CRI interface and inspect state ourselves
/cc @yifan-gu @dghubble
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

I am not too familiar with the checkpointer itself and the contraints that surround it but I believe that relying on liveness probes could be a decent solution. It is simple, users are familiar with the concept and they would expect the checkpointer to rely on them. It is also user customizable in a way. Additionally, the project also vendors Kubernetes so the functions that achieve that could be re-used directly.
The downside is that if we do not want to add the requirement of defining probes, this is only part of the solution.

The other part of this issue is that api-server behavior has changed in v1.5:
In earlier versions, the api-server would continually re-try to bind to particular addresses (:443 & :8080). If they were already in use, it would just try again in 15 seconds.
The behavior in v1.5 is that the api-server will exit immediately if it is not able to listen on those addresses (and would rely on external mechanisms of systemd/kubelet/etc to restart it again).
In terms of the checkpointer - we need a reliable way to determine "real api-server is running, or it is trying to be run". The "trying to be run" is important, because we need to remove an active checkpoint in this situation, so the real server can actually start (and bind on 443/8080).
Even if we check the liveness probe, we don't know "what" we are checking (someone happens to be listening on 8080). It could be an active checkpoint, or it could be the active parent. All we get to determine is that one of them happens to be running - but we can't make super reliable / actionable decisions based on just that information (I think it will work to add the liveness check - just not in a particularly clean way).
For example, the issue I was seeing was:

After reboot the kubelet starts (no local pod state)
Checkpointer sees that it has an inactive checkpoint for api-server, and should start it
Checkpointed-apiserver starts, and now kubelet can ask api what pods should be running
Kubelet starts the real apiserver pod, but it immediately fails because it cannot bind to 8080/443
Even though the api-server pod immediately failed, it was in fact "started" by the kubelet - so the last reported state to the api was: apiserver podState=running.
Checkpointer inspects the local kubelet-api, and sees apiserver podState=running - even though that is no longer true.
We are now in a state where kubelet-api thinks api-pod is running - but this could be stale information.
the issue: The desired state is that the checkpointed copy is deactivated (happens), and that the real apiserver pod takes over (does not happen). What I'm seeing is that the kubelet is not trying to restart the real api-server pod (it had failed to bind prior) - even though it could successfully start now. But then the checkpointer only sees that /pods api reports (stale) state of apiserver podState=running - so it makes no changes (it thinks everything is a-ok).

One other option which comes to mind after typing this: ensuring that the local docker state (of failed pods) exists for a longer window (--minimum-image-ttl-duration).
I think this might help because I believe the kubelet determines what pods it needs to restart by inspecting information serialized into the docker containers (otherwise a reboot of a kubelet would mean all local state is lost until api-server is available). So my hunch is that we have an issue where the api-server pod is being garbage collected in the window before kubelet knows to restart it. But if we leave this sitting around longer -- we could have a better recovery window.

Both the old and new checkpointers are affected by the API server change in 1.5
The --minimum-image-ttl-duration doesn't seem to help
The old checkpointer is slightly better because the race can potentially be won but the odds are low and it takes forever to get the right timing

Will experiment waiting for a file lock on the API server start.

For posterity:
There is only minimal state which is actually stored with the docker containers: https://github.com/kubernetes/kubernetes/blob/master/pkg/kubelet/dockertools/labels.go#L70
So it's not actually possible to recover local state from this info alone (this is mapped to the internal kubelet pod state).
Another option @Quentin-M and I came up with is to have the api-server use file locks to coordinate between the parent / checkpoint. This way we don't end up in failure loops when both are running, but only one can successfully listen on host address.

Should be closed by: https://github.com/kubernetes-incubator/bootkube/pull/264


Minor changes on logo (more regular, smooth lines, png and svg favicon)

Minor changes on logo (more regular, smooth lines, png and svg favicon), size change to 24x24 for future usage in simple icons
.vs/* added in .gitignore

I like the changes, thank you for making those edits to the SVG.
I'd prefer not to change the favicon though, if you don't mind. I can go ahead and merge this into the repo, which should also clear up the PR over at simple-icons. Thank you for your inclusion of this project into simple-icons btw, happy to see it featured over there :)


VM Scale set issue

This is autogenerated. Please review and update as needed.
Describe the bug
Command Name
az vmss create
Errors:
Azure Error: InvalidTemplateDeployment
Message: The template deployment 'vmss_deploy_hxmDzLnbc9mp3uxmdeaL91MFUrdvyEC7' is not valid according to the validation procedure. The tracking id is 'b05fb8d5-f1e8-4dd7-be6a-550dfc7cdd49'. See inner errors for details.
Exception Details:
	Error Code: QuotaExceeded
	Message: The operation couldn't be completed as it results in exceeding quota limit of Core. Maximum allowed: 4, Current in use: 4, Additional requested: 1. Read more about quota limits at https://aka.ms/AzurePerVMQuotaLimits. Submit a request for Quota increase using the link https://aka.ms/ProdportalCRP/?#create/Microsoft.Support/Parameters/%7B%22subId%22:%2224b14b93-0bf2-4340-9c3e-16f1a7848e0f%22,%22pesId%22:%2206bfd9d3-516b-d5c6-5802-169c800dec89%22,%22supportTopicId%22:%22e12e3d1d-7fa0-af33-c6d0-3c50df9658a3%22%7D.

To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

Put any pre-requisite steps here...
az vmss create --resource-group {} --name {} --image {} --upgrade-policy-mode {} --instance-count {} --admin-username {} --generate-ssh-keys

Expected Behavior
Environment Summary
Linux-4.15.0-1063-azure-x86_64-with-debian-stretch-sid
Python 3.6.5
Shell: bash

azure-cli 2.0.76

Additional Context

@qwordy please take a look.

The error message said it exceeded the quota. Have you try increasing quota using the given link?

Hi,
No i did not increase the quote, I was trying to create a scale set with 4
machine and it started giving me the error.
Question:
Can we have more 3 vm machine in the scale set with Trail license in azure?
Regards,
Aasif Faheem Ansari
Principal Consultant - AST Pvt Ltd.
India : +91-98 60 442310
Blog: http://siebel-ansari.blogspot.com http://ansarifa.blogspot.com/
On Thu, 21 Nov 2019 at 11:38, Feiyue Yu<EMAIL_ADDRESS>wrote:

The error message said it exceeded the quota. Have you try increasing
quota using the given link?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Azure/azure-cli/issues/11327?email_source=notifications&email_token=AHZ6D3HWU2C7LYU42GZ3OYDQUYQULA5CNFSM4JPRKIV2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEEZCTBY#issuecomment-556935559,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHZ6D3AT5KYC4YRBVXCQPLLQUYQULANCNFSM4JPRKIVQ
.

@shpa-microsoft, Hi Shalaka, Can we have more 3 virtual machines in the scale set with Trail license in azure?

HI, So this quota is not per VMSS. It is per subscription. Do we have anything outside of this VMSS in this subscription? If we already have another VMSS. or VM then this can happen. In that case you can try deleting existing VM and then redo this operation OR increase quota limits

Adding @Jun Wang<EMAIL_ADDRESS>to help with Trail license.
From: Feiyue Yu<EMAIL_ADDRESS>Sent: Monday, November 25, 2019 6:52 PM
To: Azure/azure-cli<EMAIL_ADDRESS>Cc: Shalaka Patel<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [Azure/azure-cli] VM Scale set issue (#11327)
@shpa-microsofthttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fshpa-microsoft&data=02|01|Shalaka.Patel%40microsoft.com|86b4aece9bad4904488b08d7721ba023|72f988bf86f141af91ab2d7cd011db47|1|0|637103335285418232&sdata=gCyB3tGLfOh9%2FE3X71UQhWX9koKfZYN%2BMvd1XtiFNFs%3D&reserved=0, Hi Shalaka, Can we have more 3 virtual machines in the scale set with Trail license in azure?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAzure%2Fazure-cli%2Fissues%2F11327%3Femail_source%3Dnotifications%26email_token%3DAMYPRUNLQJ6M7WX5XU5BY53QVSFNNA5CNFSM4JPRKIV2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFEQYGI%23issuecomment-558435353&data=02|01|Shalaka.Patel%40microsoft.com|86b4aece9bad4904488b08d7721ba023|72f988bf86f141af91ab2d7cd011db47|1|0|637103335285418232&sdata=VBIIm4tMK4Or4bjou2JSZpNT1Jy2WivwHKPBdYUjrpg%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAMYPRUMGD3QVSITNTVKC6A3QVSFNNANCNFSM4JPRKIVQ&data=02|01|Shalaka.Patel%40microsoft.com|86b4aece9bad4904488b08d7721ba023|72f988bf86f141af91ab2d7cd011db47|1|0|637103335285428185&sdata=GzCMQz9vFMK7k2uTh%2B9oK%2BQuvTDjXLlqTFP5wn7N9kw%3D&reserved=0.

Free trail allows for 4 vCPU per region.

Hello Team,
Thank you very much for the response and help here.
Regards,
Aasif Faheem Ansari
Principal Consultant - AST Pvt Ltd.
India : +91-98 60 442310
Blog: http://siebel-ansari.blogspot.com http://ansarifa.blogspot.com/
On Thu, 28 Nov 2019 at 03:55, wangjun-jwa<EMAIL_ADDRESS>wrote:

Free trail allows for 4 vCPU per region.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Azure/azure-cli/issues/11327?email_source=notifications&email_token=AHZ6D3APVUVAFZ4HDXWVZY3QV3XV5A5CNFSM4JPRKIV2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFK44MQ#issuecomment-559271474,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHZ6D3C57FR7S2TB2ANE2JLQV3XV5ANCNFSM4JPRKIVQ
.

move to S163.

hi @aasif2310 we'll close the issue for now, free trial allows for 4 vCPU per region, which could resolve the quota limit error, pls give it a try and reopen or create new issue if you met any other issue. thanks.


(PUP-8487) Remove MethodHelper

The functions in MethodHelper provided a generic way to supply optional arguments to a constructor and send them to setters. In practice this obscures the signature of the constructor and makes it very difficult to figure out what arguments are being passed around. It also generated a lot of garbage in constructing the names of setter methods.

jenkins please test this

CLA signed by all contributors.

blocked on having master depend on ruby 2.3 again

jenkins please test this

jenkins please test this

jenkins please test this

jenkins please test this

This needs to be rebased before the PR testing will work.

jenkins please test this

Those failures seem more like real failures.

jenkins please test this

The finalized_on_cycle.rb failure is unrelated to this PR (it's due to PUP-6344 which is fixed in the 5.5.1_release branch, but hasn't been merged back to 5.5.x and up to master)

jenkins please test this

jenkins please test this

jenkins please test this

(rebased to fix an unrelated failure yet again)


Make startAggressiveTracking public

otherwise get an error message that it not a valid plugin method

I'm actually probably going to get rid of this functionality. Is there a good reason to keep this?


Could change issures's hyperlink based on local IP?

Gitea version (or commit ref):
Git version: 1.14.2
Operating system: Cent OS
Database (use [x]):

[ ] PostgreSQL
[ ] MySQL
[ ] MSSQL
[x] SQLite

Description
There are questions about links:
In the Issures menu: The hyperlink of issures is based on domain name IP (from App.conf),Could It changed by local IP（or url IP）?
Like 192.168.../.../issures/6 ?
Screenshots
photos:

Gitea currently does not have multi-domain support, closing as duplicate of #8697

In Gitea version 1.14.2 , the issures items's hypelink's  domain is different whith url 's  domain.
But in Gitea version 1.12 ,the issures items's hypelink's  domain is same whith url 's  domain.
So can keep the issures items's hypelink's  domain  same with url's  domain ?
As you see, the issures items's author's hypelink's domain is same with url's domain.


Function calls are not supported in decorators

I am using Angular 6, but when I try to compile it I get the following error:
ERROR in Error during template compile of 'AppModule'   Function calls are not supported in decorators but 'InjectionToken' was called in 'SocketIoModule'     'SocketIoModule' references 'SOCKET_CONFIG_TOKEN'       'SOCKET_CONFIG_TOKEN' calls 'InjectionToken' at ngx-socket-io\src\socket-io.module.ts(10,40).

I used the ngx-socket-io package, not this one.


Linux, please

So.  This works well in WINE, almost (Manjaro and OpenSUSE Tumbleweed.)  While I would love to have a native application, it does work.
It complains that it can't find LifePlay.exe.  This makes sense if it's to be limited to Windows, but LifePlay.exe is not distributed in the linux LifePlay binary releases.
LifePlay.sh exists in the binary release-root directory.  I do not recall whether this has the executable bit set by default.  I believe it does.
LifePlay.sh calls /LifePlay/Binaries/Linux/LifePlay-Linux-Shipping, which is the executable binary.
Would you modify to check for an existing linux binary?
Bonus points for enabling me to set in a config the location of my binary, and my LP update scripts, or just pick from a (pref: my OS/GUI-native) filepicker.

Sorry for delay, this is on my to-do-list, I promise!

Nudge.
And. No worries. It's really just an annoyance.


Add intensityCandela API to LightManager

This adds a new intensityCandela builder method and setIntensityCandela API method for updating a punctual light's intensity in candela, as opposed to lumens or watts.

Well that's not helpful here. Our existing APIs take lumens but the shaders work in candelas. For glTF we want a way to directly set the candelas intensity. That or a lumensFromCandela() function but it does require passing the type of light. I still don't understand why glTF went with candelas…

A lumensFromCandela function would require passing the type of light, and in the case of spot lights, the cone angles. But then we're back to the case where we're doing two conversions just to cancel each other out.


missing ops

[x] eval
[x] stdin
[x] close

(Should be noted they ain't done, even if they are partially/almost implemented)

[ ] ls-session
[X] describe
[X] interrupt
[x] load-file

Source:
https://github.com/clojure/tools.nrepl/blob/master/doc/ops.md

cc63ee3e5313182236af927b390bdc1510d19a1f implements ls-session as the only remaining op.


users response not OK - limit_required

This tool is great - it works really well, except on one Slack group:
gh slack read https://example.slack.com/archives/C1M5388TF/p1688463409836309
Error: users response not OK: {"ok":false,"error":"limit_required"}

There are ~30k users on this Slack, so perhaps this is the issue

If the collection is too large you may experience limit_required

👋 Apologies for the slow reply, my notifications were going to a defunct email address. This should be fairly simple to address by adding paging to the users call https://github.com/rneatherway/gh-slack/blob/211b567ee13226729ae0162620989cff8a0ec528/internal/slackclient/client.go#L358
You could use this function as an example: https://github.com/rneatherway/gh-slack/blob/211b567ee13226729ae0162620989cff8a0ec528/internal/slackclient/client.go#L316
I'd be happy to review such a PR, or may get to it myself at some point!

This should be fixed by https://github.com/rneatherway/gh-slack/pull/61. Would you like to give it a test @rmoff?

Great! If you checkout the PR and then run
go run ./cmd/gh-slack/ read https://example.slack.com/archives/C1M5388TF/p1688463409836309

that should be equivalent to the command that you pasted above.

Works perfectly. thanks!

Released!


Map class_8012

This is one of the three mystery constant classes.
I diffed the pre4-pre5 and noticed that a new field was added here. I checked the usage of the newly added field_44941 in the code diff, and it was used in RealmsInviteScreen as a gray color.
I then converted each field to hexadecimal unsigned int - and tada! It was all something that were meaningful as colors; white, black, and red.

I'm a bit late, but shouldn't it be in the client package? If it's used in screens

@YanisBft Client package is reserved for actually client-only class; this is not.


update observables

Some operations for VectorObservable like var are corrected
BinningObservable is deprecated

Instead, use obs = SimpleObservable() and binned = binning(obs)
binning returns new SimpleObservable with binned
binning takes one option, binsize::Int or numbins::Int.

binsize is the size of each bin
numbins is the number of bins
If omitted, binsize = floor(Int, sqrt(count(obs))) is used

param in runMC(param::Parameter) takes new optional keys, Binning size and Number of Bins

Operations for the mixture of Jackknife and JackknifeVector are added

I close it until the test passes


Improve keyboard and screen reader compatibility

A number of the buttons, check boxes, and edit fields are not accessible to screen readers. For instance, the checkbox that is supposed to enable Markdown in the editor does not have a label attached to it, so the screen reader says, only, check box.
Menus do not gain focus upon opening them with the keyboard, as well.
Steps to reproduce.

Download and run NVDA, the free and open source screen reader.
Launch the Demo CMS.
Navigate via keyboard only. No mouse.

CMS version.
The demo version says 2.0.4.

Closing in favour of https://github.com/netlify/netlify-cms/issues/1333.
You can list any specific issue in the existing issue