tartelet UI does not work

What happened?
I'm trying to setup on Mac Mini M2 (14.5 (23F79)) using latest tartelet (0.9.0) and tart (2.11.0). I also tried to downgrade tartelet to (0.8.3). But UI does not let me edit virtual machine, it also does not reflect that pem file for GitHub app is configure, although I see it adds it to keychain. Tart was able to create a VM though I used tart create with default settings and latest image.
What is the known configuration which may work. I see in https://github.com/shapehq/tartelet/issues/76 mentioned to use 14.3.1 on host?
What are the steps to reproduce?
See above.
What is the expected behavior?
UI reflect what is happening, let's editing the VM.

@simonbs 👋 if you can guide here what is better to use, I'm trying to downgrade the machine right now.

Exported logs are empty, is there some debug mode?

I believe it is because PEM key is not set up. I see it a first menu item, but then when I try to set up I'm getting the following error
11:18:27.554 INFO: Failed storing RSA private key with tag github.credentials.privateKey. Received status code: -25308

I already tried to quite the app, remove all attributes from the app with xattr -d (it seems it was put in the quarantine by Safari), and then clean up the keychain for anything related to tartelet. But then I still get this error.

Apparently it is this error: https://developer.apple.com/documentation/security/errsecinteractionnotallowed


NTR: subdistal appendages

A reviewer of the cilia GO ontology manuscript has requested an additional component term as part of the eukaryotic cilium. @paolaroncaglia, @JohnvanDam, and I need to work on this promptly to meet October 30 deadline to submit revisions.

2: similarly, the eukaryotic cilium is also only missing one component: subdistal appendages.
There are several proteins localizing there are described e.g. in  10.1242/bio.20122337 and
https://doi.org/10.1016/j.devcel.2016.10.006.

link for 10.1242/bio.20122337: http://bio.biologists.org/content/1/10/965
Sonnen KF, Schermelleh L, Leonhardt H, Nigg EA. 3D-structured illumination
microscopy provides novel insight into architecture of human centrosomes. Biol
Open. 2012 Oct 15;1(10):965-76. PMID: 23213374

https://doi.org/10.1016/j.devcel.2016.10.006. =
Mazo G, Soplop N, Wang WJ, Uryu K, Tsou MB. Spatial Control of Primary
Ciliogenesis by Subdistal Appendages Alters Sensation-Associated Properties of
Cilia. Dev Cell. 2016 Nov 21;39(4):424-437. PMID: 27818179

which is also referred to in this interesting commentary:
Galati DF, Mitchell BJ, Pearson CG. Subdistal Appendages Stabilize the Ups and
Downs of Ciliary Life. Dev Cell. 2016 Nov 21;39(4):387-389. PMID: 27875681.

Copying from an email from @JohnvanDam for internal reference:
"I have to check if the sub distal appendages should maybe be a synonym to an already existing term. I'll check that this wednesday, when I get back at work."

Quick notes:
From the first paper (http://bio.biologists.org/content/1/10/965):
“Of the two centrioles, the older one (frequently referred to as the mother) carries distinctive distal and subdistal appendages (Paintrand et al., 1992), which confer important functional asymmetry (Bornens, 2012; Nigg and Stearns, 2011).”
So at a first glance it sounds like we may want to create ‘subdistal appendage’ as part_of GO:0005814 ‘centriole’. (At present, ‘centriole’ has no children.) However, ‘appendage’ is ambiguous (see ‘GO:0035107 ‘appendage morphogenesis’) and I’d rather use it as a synonym. Or call it explicitly ‘centriole subdistal appendage’ - we have previously allowed this type of specification in GO where necessary to disambiguate (see some dinoflagellate terms). Also, the reviewer asks for ‘subdistal appendages’, but we may need to think about ‘distal’ too if appropriate - as a term or synonym.
The second paper (http://www.sciencedirect.com/science/article/pii/S1534580716307195) suggests we should add sDAP as a synonym:
“…centriole subdistal appendages (sDAP)…”.
We should also annotate the relevant human proteins, see section on “Appendage proteins” in http://bio.biologists.org/content/1/10/965. Proteins are also described in the second paper.

The term 'ciliary transition fiber' already has several 'distal appendage' synonyms. The question I would ask is whether the subdistal appendages are also transition fibers, in which case, we might need to have separate terms for both distal and subdistal appendages, each of which could be a type of transition fiber. I agree that terms called 'distal appendage' or 'subdistal appendage' would need to be explicitly called 'centriole ...'
[Term]
id: GO:0097539
name: ciliary transition fiber
namespace: cellular_component
def: "A nine-bladed, propeller-like protein complex that links the distal end of the basal body and the cilium to the plasma membrane. Functions in protein sorting and gating (i.e. active and passive transport of proteins in and out of the cilium)." [GOC:cilia, GOC:kmv, GOC:krc, PMID:22653444, PMID:24231678, PMID:5064817, PMID:5335827]
comment: In mammals, ciliary transition fibers comprise at least five components (Ccdc41/Cep83, Cep89/Cep123, Sclt1, Fbf1, and Cep164) (PMID:24469809).
synonym: "centriolar distal appendage" RELATED [PMID:24469809]
synonym: "cilial transition fiber" EXACT []
synonym: "cilial transition fibre" EXACT []
synonym: "ciliary transition fibre" EXACT []
synonym: "cilium transition fiber" EXACT []
synonym: "cilium transition fibre" EXACT []
synonym: "distal appendage of basal body" RELATED [GOC:krc]
synonym: "distal appendage of centriole" RELATED [GOC:krc]
synonym: "distal appendage of mother centriole" RELATED [GOC:krc]
synonym: "transition fiber" BROAD []
synonym: "transition fibre" BROAD []
is_a: GO:0043234 ! protein complex
is_a: GO:0044441 ! ciliary part
created_by: paola
creation_date: 2013-12-03T16:46:37Z

This paper:
Garcia-Gonzalo FR, Reiter JF. Open Sesame: How Transition Fibers and the
Transition Zone Control Ciliary Composition. Cold Spring Harb Perspect Biol. 2017
Feb 1;9(2). Review. PubMed PMID:27770015
confirms our existing equivalence of distal appendages' with 'transition fibers'

Basal bodies start their lives as mother centrioles, distinguished from daughter centrioles by the distal appendages through which they dock to the vesicles that are eventually remodeled into the ciliary membrane (Sorokin 1962; Lu et al. 2015). When associated with the ciliary membrane or its precursors, centriolar distal appendages are referred to as transition fibers (TFs) or alar sheets.

and does not suggest that subdistal appendages should also be considered as 'transition fibers'

from Mazo G et al. 2016 (PMID: 27818179):

DAP and sDAP are distinct structures composed of different core components:

DAP: CEP83, CEP89, SCLT1, CEP164, and FBF1
sDAP: ODF2, CNTRL, and NIN

from Galati et al. 2016 (PMID: 27875681)

Centrioles acquire subdistal appendages (sDAPs) during primary cilium formation.

From what I've looked at, I do not think that any of our existing terms represent distal appendages and agree with the reviewer that we need a new term for these.
Since they form during ciliogenesis, they could be is_a 'ciliary part'.

Interesting how I seem to have missed sDAPs completely... I agree that DAP and sDAP appear to be two different structures. To me it seems like DAP is the same as transition fibers though, but from Karen's previous post I guess literature is conflicting on this. Figure 3 in https://www.ncbi.nlm.nih.gov/pmc/articles/PMC4113101/ has some nice detailed EM photographs showing the difference between DAP and sDAP. Comparing the protein annotations for transition fiber to the list above it seems that some of the protein annotations need to be reassigned after the sDAP term is created.
In addition, distal appendage seems to be used more often than transitional fiber, when searching pubmed. We might consider making distal appendage the canonical name if we agree that DAP and transitional fibers constitute the same structure.

Sorry if it was confusing that I was just wondering if sDAPs are also transition fibers. However, some reading I did yesterday (Garcia-Gonzalo et al. 2017, PMID:27770015) confirms that DAP is the same as transition fiber (and sDAP is not), so I am in agreement with you there.
I have also been wondering if we should change the name from "transition fiber" to "distal appendage". If PubMed is indicating that "distal appendage" is more commonly used, then I agree it might be good to make it the primary term name and convert "transition fiber" to a synonym.
I also agree with Paola's suggestion to add DAP and sDAP as synonyms.

Hi @krchristie and @JohnvanDam,
Thank you both for your feedback on this. You have both read a lot more than I have on those cellular components, so I’ll refer to your judgment. My only comment would be that when we created the cilia terms, ‘transition fiber’ sounded like well-accepted nomenclature to me, so I might be a bit reluctant about swapping it for a synonym, but as I said I’m not the major expert here. Perhaps, if there are still any grey areas we’d like validation on, we could ask for a third opinion? Who could be a friendly expert you’ve already been in touch with, and who’d be available to provide feedback promptly? So we can go ahead with adding/editing terms and annotations. Thanks!

I guess renaming transition fibers would not be important as it is captured via synonym anyway, and as you say the current name is well accepted in literature. As for experts to contact, I am now browsing through pubmed for names that may be considered expert on centrioles and distal appendages: JF Reiter (UCSF) comes up regularly in the context of both centrioles and basal bodies. Although I did not have previous contact before, he seems a nice enough fellow. I would not know who in my Syscilia network would be specifically knowledgeable about sub-distal vs distal appendages, but we could maybe ask Colin Johnson (Leeds University) if he knows, or at least knows someone. Shall I send him an email?

Thanks @JohnvanDam,
I wouldn't mind you asking Drs. Reiter or Johnson, unless @krchristie has any objection.

Transition fiber is well accepted nomenclature, but distal appendages are also well accepted nomenclature. The biggest issue I've had in annotating these seems to be that many papers use one name or the other without mentioning the other name, but as long as we have both names attached to the same term, curators and users will be able to find it. GO often goes with the most commonly used name as the primary name.
I've met Jeremy Reiter at a cilia meeting, though haven't had any further contact with him subsequently. Rereading the quote from a review from his lab that I included earlier in this thread also makes me wonder if there is a subtle distinction between distal appendages and transition fibers based on the fact that this quote specifies the "centriolar distal appendages are referred to as transition fibers" "When associated with the ciliary membrane or its precursors". This might suggest a need for terms for both "centriolar distal appendages" and "transition fibers" separately from each other. I would be quite cautious about this course as it seems it would be very difficult to annotate these accurately.
I don't object to contacting people for their input, though we should be aware that adding non-GOC people to the conversation often makes it take longer to get to resolution. But if John wants to shepherd that conversation, I don't object.

While trying to come up with a proposal for the new "centriolar subdistal appendage" term, I've seen some additional comments that also suggest that at least sometimes there is a distinction in the use of "distal appendage" to "transition fiber" that corresponds to a maturation of the structure from the DAPs forming on the mother centriole to becoming transition fibers when they form the connections of a fully assembled cilium, e.g. this one from this paper cited by the existing "transition fiber" term:
Wei Q et al. Transition fibre protein FBF1 is required for the ciliary entry of assembled
intraflagellar transport complexes. Nat Commun. 2013;4:2750. PMID: 24231678.

transition fibres (TFs; transformed from the distal appendages of the mother centriole)

However, from an annotator's perspective, I don't think it will be useful, or even possible, to make a meaningful distinction between a "distal appendage" and a "transition fiber" since I think many papers still refer to these structures as distal appendages even when looking at fully assembled cilia. I'd be fine with just leaving this term as is, though I don't object if John wants to contact researchers.

We also can proceed with adding the requested term for centriolar subdistal appendages without resolving the issue regarding the name of the term for "centriolar distal appendages" or "transition fibers", so here is a proposal for a new term:
name: centriolar subdistal appendage
definition: A structure containing ODF2, CNTRL, NIN, CCDC120c and CCDC68 which forms on the mother centriole, adjacent and proximal to a centriolar distal appendage, during cilium formation.
def dbxrefs: Mazo G et al. 2016 (PMID: 27818179); GOC:cilia, PMID:28422092
synonym: sDAP (RELATED)
and the same parentage as the current "transition fiber" term, e.g.:
subclass_of: cilium part
subclass_of: protein complex
I'm hesitant to try to say too much about what the complex does as these two papers cited seem to be among the among the first to try to characterize what the subdistal appendages do, so it may be premature to try to say much.

The biggest issue regarding these terms is that they are called different depending on the situation. Which is fair, but I think essentially these are the same structures. I think the quote about TF's being "transformed from the distal appendages of the mother centriole" is a way for the authors to deal with the two nomenclatures, as so far as I can tell the only known difference is whether it attaches to the plasma membrane or not. I would keep transition fiber and distal appendage as synonyms, and maybe add a comment that it could be possible that the composition of this structure might change depending on the state of the centriole/basal body.
I will not contact Colin of JF Reiter at this point, to avoid going of track with what we need to do at this point. Maybe we can revisit once it becomes relevant for annotation when more conclusive research emerges about possible differences between distal appendages and transition fibers.
The proposed term definition by Karen for subdistal appendage looks good to me.

@krchristie @JohnvanDam
I agree that if the literature is in its ‘early days’ wrt sub distal appendages, we may not want to say too much. Karen’s latest proposal above would be good with me, except for a minor point in the definition, i.e. addressing the need to try and make the definition as species-generic as possible. So perhaps
“A protein complex which assembles on the mother centriole during cilium formation, adjacent and proximal to a centriolar distal appendage. In human [it is human, right?], it contains ODF2, CNTRL, NIN, CCDC120c and CCDC68.”
I would also add PMID:23213374 among def dbxrefs (“3D-structured illumination microscopy provides novel insight into architecture of human centrosomes”), as that was suggested by reviewer 1.
As for expanding the definition comment to ‘ciliary transition fiber’ along the lines of “the composition of this structure might change depending on the state of the centriole/basal body”, I do not disagree and will leave it to you two, if you’d like, to choose the most appropriate wording.
Lastly, who should annotate those proteins? @krchristie, can you do that or should we ask UniProt?
Thanks!

Thanks for the suggestion on the definition @paolaroncaglia. I will definitely include that it is human. I don't know why I didn't include that. I normally do... I'll add the term today so it is available in Protein2GO as soon as possible.
I think it might be simplest if I just annotate them myself. It's only two papers.

I've added the new term for 'centriolar subdistal appendage' as I proposed with Paola's suggestions incorporated, and also with some synonyms following the pattern of the existing synonyms for the 'ciliary transition fiber' term, viewable here:
https://github.com/geneontology/go-ontology/pull/14339/files
Since I forgot to close this automatically, I think I'll just leave it open to remind me to do the annotations when the term is available in P2GO.

@krchristie Thanks for adding the term - and the annotations later on!

Hi @krchristie,
Is the new term 'centriolar subdistal appendage' now available in P2GO? If so, and compatibly with your other commitments, could you please add a comment on this ticket when the annotations are ready, so we can add their details in the re-submission letter. Many thanks!

@krchristie
P.S. and indicate the expected release date of those human annotations, thanks.

It doesn't look like the new GO term has made it into P2GO yet. I had tried yesterday, and just checked again now.
Regarding the expected release date, I have no idea. Maybe it would be easier for you,  @paolaroncaglia, to find out from your EBI colleagues when the next planned release date is.

@paolaroncaglia - I have made a number of annotations for proteins that are part of the subdistal appendages from two papers. I've downloaded the annotations as GPAD files directly from P2GO, so I'll email you those.
I think that complete annotation of PMID:23213374 would require a one or two more terms, highlighted in this quote from this paper:
Together, our studies identified redundant functions of sDAP and the proximal end factor C-Nap1 in centrosome cohesion, cilia-to-Golgi association, and ciliary pit maintenance, critical for the spatial control of ciliogenesis. I'll put this new stuff in a different ticket...
These two papers might also suggest a need for more granular terms for the centriole. Currently both "mother centriole" and "daughter centriole" are both synonyms for centriole, but there are things that localize differentially to one or the other. Then these papers also make a point about localization to the proximal end of the centriole, but then we get into a proliferation of combinations of proximal vs distal with mother vs daughter... so I think I'll just leave that be.

@krchristie
Thanks for making and sending those annotations! I'll include them in the response letter.


embedding mat-optgroup elements using *ngFor causes app to crash/freeze

Reproduction
https://stackblitz.com/edit/angular-xwukxn?file=src%2Fapp%2Fapp.component.html
Steps to reproduce:

Embedding mat-optgroup elements using *ngFor over a hard-coded array works OK.

<mat-select>
  <mat-optgroup *ngFor="let g of [{name: 'group 1'}, {name: 'group 2'}]" [label]="g.name">
    <mat-option>None</mat-option>
  </mat-optgroup>
</mat-select>

However, trying to pass an array returned by an object getter to the *ngFor results in the app freezing.

class MyClass {
    get values() { return [{name: 'group 1'}, {name: 'group 2'}]; }
}

class MyComponent {
    instance = new MyClass();
}

<mat-select>
  <mat-optgroup *ngFor="let g of instance.values" [label]="g.name">
    <mat-option>None</mat-option>
  </mat-optgroup>
</mat-select>

Expected Behavior
The mat-select should be displayed correctly.
Actual Behavior
The app freezes.
Environment

Angular: 8.2.0
CDK/Material: 8.1.2
Browser(s): Google Chrome
Operating System (e.g. Windows, macOS, Ubuntu):

When you put the array in a getter like that you end up returning a new array every time Angular runs change detection. This means that as far as Angular is concerned the data always keeps changing which means that the UI has to be re-rendered.

Ouch. Of course, that makes sense. I was shocked by the sudden freezes and the solution was actually quite simple 😅
Thank you!


lua: set mainProgram

set meta.mainProgram for lua

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] 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/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

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

[ ] Fits CONTRIBUTING.md.

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

Should I update packages and docs using ${lua}/bin/lua to ${lib.getExe lua}?

I dont think it's necessary. I find ${lua}/bin/lua clearer/less magical than ${lib.getExe lua} for instance (and I dont know of many instances of such). It could make a difference when you use luajit instead of lua but even then we have a symlink lua -> luajit.
I am just waiting for eval before merge

the failure looks unrelated (though annoying)

@teto I just realized luajit is also missing mainProgram, welp I guess that will be my next PR

I guess it should be luajit then


RHEL ChefDK 0.7.0 asking for FQDN, or flags when bootstrapping new node

On CentOS 6.7, using ChefDK 0.7.0, I am attempting to bootstrap a node into our Enterprise Chef server using the command
knife bootstrap servername.internal.net

Then I am prompted for
ERROR: You must pass a node name with -N when bootstrapping with user credentials

Then I use the -N, or --ssh-user option and I am still greeted with:
ERROR: Must pass an FQDN or ip to bootstrap

Then when I supply the IP, I get the same error. Supplying the --verbose option only provides:
INFO: Using configuration from /vagrant/.chef/knife.rb

I was able to bootstrap a node using the RubyGem chef and MRI 2.2.3.

I was able to do this recently on a dev build between 0.8 and 0.9. Maybe just the way the options work is confusing? e.g., you have to do knife bootstrap servername.internal.net -N servername.internal.net or something? In any case this would be an upstream issue in the Chef project, if you are still experiencing problems, could you open an issue over there?

i worked on this issue on version 12 of the Chef Server for a while and after reviewing various articles on the web I did not find a solution so I wanted to share my solution that works for me.
The problem I had
knife bootstrap clientname -x myuserID --sudo
ERROR: You must pass a node name with -N when bootstrapping with user credentials
then using the -N option with the FQDN or IP did not resolve the issue as below
knife bootstrap -N clientname -x myuserID -- sudo
or
knife bootstrap -N <IP_ADDRESS> -x myuserID --sudo
gave this annoying error
ERROR: Must pass an FQDN or ip to bootstrap
The SOLUTION
knife bootstrap -N clientname.mydomain.com -x userID@clientname --sudo
This worked without any errors and was able bootstrap the client.
FYI - as part of my troubleshooting process I also deleted the chef-validator and validation_key from knife.rb as suggested by some web sites.
The lines below were delete from the knife.rb and the chef-validator.pem was deleted as well ( you may want to keep a backup copy the knife.rb and the chef-validaor.pem files in a backup folder outside the chef-repo )
validation_client_name   'chef-validator'
validation_key           '/home/myuserID/chef-repo/chef-validator.pem'


[Improve][Connector-V2] Refactor local file sink connector code structure

Purpose of this pull request
According to pr #2555 , this pr has optimized the local file sink connector on top of it

Check list

[x] Code changed are covered with tests, or it does not need tests for reason:
[ ] If any new Jar binary package adding in your PR, please add License Notice according
New License Guide
[ ] If necessary, please update the documentation to describe the new feature. https://github.com/apache/incubator-seatunnel/tree/dev/docs

@CalvinKirs @EricJoy2048 PTAL.

@CalvinKirs @EricJoy2048 PTAL.


example bottom_navigation_multiple_beamers not keeping state when changing tabs

Hello, I tried to use this example, but I couldn't get it to work. I tried using both 0.11.2 and 1.0.0-pre.1.0. It seems that the state is not being saved.
Intended:
https://raw.githubusercontent.com/slovnicki/beamer_examples/master/bottom_navigation_multiple_beamers/example-bottom-navigation-multiple-beamers.gif
Actual:

The repo I am working on is here, in case you want to check my setup

Hi @getBoolean
Thanks for the feedback!
Yeah, this example was always kind of a work in progress and forgotten about most of the times during updates.
I'll see if I can fix it today.

This is a more fundamental problem that I thought. I'll try to resolve it this week.

Quick update: I detected a major flaw - a cause of this behavior and a reason this example can never work as expected with current beamer.
It's the NavigationNotifier. Sibling Beamers are listening to eachother 🤦
So this will automatically be solved by https://github.com/slovnicki/beamer/issues/181, two birds with one stone.

That's great to hear, thanks for the update.

Also, would that be related to why when I change the theme with a provider (specifically hooks_riverpod), it goes back to the home page? repo
If it's not related, I can make another issue.

@getBoolean I believe this is a separate issue. Feel free to make a new issue and I will check your repo in the evening

this should be fixed now. See example


home-assistant: 2021.4.6 -> 2021.5.0

Motivation for this change
https://www.home-assistant.io/blog/2021/05/05/release-20215/
Things done

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

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

[x] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

         Outdated dependencies
┏━━━━━━━━━━━━━━━┳━━━━━━━━━━━━┳━━━━━━━━┓
┃ Package       ┃ Current    ┃ Wanted ┃
┡━━━━━━━━━━━━━━━╇━━━━━━━━━━━━╇━━━━━━━━┩
│ denonavr      │ 0.9.10     │ 0.10.5 │
│ pydroid-ipcam │ 2021-04-16 │ 0.8    │
│ pyotgw        │ 2021-03-25 │ 1.1b1  │
│ roombapy      │ 1.6.2-1    │ 1.6.3  │
│ sqlalchemy    │ 1.3.23     │ 1.4.11 │
│ surepy        │ 0.5.0      │ 0.6.0  │
└───────────────┴────────────┴────────┘

I think we are on top of all of these in other PRs, that I will tackle right after this one.

Result of nixpkgs-review pr 121865 at 3e3d9b7a run on x86_64-linux 1

1 package failed to build:

home-assistant

2 packages built successfully:

python38Packages.zwave-js-server-python
python39Packages.zwave-js-server-python

Note that build failures may predate this PR, and could be nondeterministic or hardware dependent.
Please exercise your independent judgement.


Feature/instance profile support

Get credential from EC2 instance profile.

I aporogize for committing after PullRequest again and again.
I take the current Region from InstanceProfile.
All spec tests are passed in my local environment, but Travis is failing.

Hi @ueki-kazuki ! Thank you for Great commit !!
I know this fail. So you don't mind !
LGTM!

Released as v1.12.0.


Display an error page when cannot connect to a page;

Follow ups:

Style page nicer
Add certificate failures to this (they're handled differently, more complex, but this provides foundation)

I tried making this a content page, but got too hairy being a separate page without modifying the webview history -- as a static display, this'll just appear over the webview if an error is found.

Coverage decreased (-0.3%) to 43.067% when pulling 4e2dc4b50180f0a0dc7a99d204d8695e676508b3 on jsantell:error-page into 41cfad7e5d83c21290b3b551a1711bdf389dcb1f on mozilla:master.

Coverage decreased (-0.2%) to 43.13% when pulling ba257ed433598ca36367fd166017a868b4032189 on jsantell:error-page into 8d3b62e887429c1ea93510c5a808d8de50571c85 on mozilla:master.


"zones" configuration is case sensitive

If an user configure the zones in WEB-INF/configuration.properties using uppercase (for example, COM instead of com), the web server throws the following exception:
SEVERE [localhost-startStop-1] mx.nic.rdap.sql.model.zoneModel.validateConfiguratedZones Configured zone not found in database: COM
Wouldn't be more user-friendly if this kind of validation were case insensitive? As far as I know, TLD aren't case sensitive, so It could be possible that an user configures his zones according to this rule.

Verified. The zones configuration is changed to lowercase and then validated, so the user can configure using only uppercase.


Extend scala.math.Equiv

Nope. It's made useless by https://github.com/scala/scala/blob/v2.11.8/src/library/scala/math/Equiv.scala#L42


Adding a breakpoint to a method should update the method on the stack

Basically, it should behave like the method is saved and revert the stack at the good place

Thanks Andrei!


Manuals incorrectly reported as roff

https://github.com/tony/tmuxp/search?l=groff
Add .txt extension to fix that.

@yegortimoschenko would you like to make a pull request for it?


Cannot find dGPU when install ollama on Windows

When "pip install ipex-llm[cpp]", then "init-ollama.bat", it runs on CPU:
" ... msg="inference compute" id=0 library=cpu compute="" driver=0.0 name="" total="31.6 GiB" ... "
But when "pip install ipex-llm[xpu]", it can run on my A770 dGPU.
When install them both "pip install ipex-llm[cpp,xpu]", i got this error:
ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts.
bigdl-core-cpp 2.5.0b20240616 requires torch==2.2.0, but you have torch 2.1.0a0+cxx11.abi which is incompatible.

Hi @YunLiu1,

msg="inference compute" id=0 library=cpu is a confusing and useless runtime log, and it does not mean that ollama is running on CPU. To ensure that it's running on the dGPU, you may follow the steps below:

Check the output from the ollama server. When running successfully on the dGPU, ollama will produce output similar to the sample output.
Check the memory usage of your dGPU during running model inference.

To run ipex-llm ollama on your dGPU, you only need to install ipex-llm[cpp]. For more details, please see our ollama document.

To run ipex-llm ollama on your dGPU, you only need to install ipex-llm[cpp]

Is there documentation that explains these options? What does installing ipex-llm[xpu] do that ipex-llm[cpp] doesn't?  Why do all the examples in the quickstart folder seem to all use different options and versions none of them seem to be compatible?

Is there documentation that explains these options? What does installing ipex-llm[xpu] do that ipex-llm[cpp] doesn't? Why do all the examples in the quickstart folder seem to all use different options and versions none of them seem to be compatible?

Hi @samamiller, you may see our official document for more details.

To run ipex-llm ollama on your dGPU, you only need to install ipex-llm[cpp]

Is there documentation that explains these options? What does installing ipex-llm[xpu] do that ipex-llm[cpp] doesn't? Why do all the examples in the quickstart folder seem to all use different options and versions none of them seem to be compatible?

@samamiller It depends on your use cases (e.g., llama.cpp vs. pytorch vs. llm); see https://github.com/intel-analytics/ipex-llm#use


Select related extensions

Added possibility to select related extensions in models.MenuItem.children(). Requires new setting TREEMENUS_EXTENSION_RELATED_NAME set to the name of the relation.
This will reduce the number of SQL queries needed when using menu extensions.
Docs are updated accordingly.

That sounds good, although instead of catching an AttributeError it'd be nicer to test for the existence of that setting. Could you also add some tests, probably using assertNumQueries (https://docs.djangoproject.com/en/dev/topics/testing/#django.test.TestCase.assertNumQueries). Thanks!


Add switches and transformers as supported components

Add support for switches and transformers to PowerPlots, PowerModelsDataFrames, and PowerModelsGraph
Add keywords to specify size, color, data visualization etc.

switch_size, switch_color, switch_data, switch_data_type
transformer_size, transformer_color, transformer_data, transformer_data_type

Codecov Report
Base: 93.94% // Head: 91.37% // Decreases project coverage by -2.56% :warning:

Coverage data is based on head (0cdd8a1) compared to base (a9003ea).
Patch coverage: 72.41% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #113      +/-   ##
==========================================
- Coverage   93.94%   91.37%   -2.57%
==========================================
  Files          14       14
  Lines         809      870      +61
==========================================
+ Hits          760      795      +35
- Misses         49       75      +26

Impacted Files
Coverage Δ

src/core/options.jl
100.00% <ø> (ø)

src/plots/plot.jl
86.63% <68.42%> (-9.70%)
:arrow_down:

src/core/data.jl
100.00% <100.00%> (ø)

src/core/types.jl
100.00% <100.00%> (ø)

src/layouts/SFDP_fixed_layout.jl
90.41% <0.00%> (-1.37%)
:arrow_down:

src/core/export.jl
100.00% <0.00%> (ø)

src/core/utils.jl
94.87% <0.00%> (+0.27%)
:arrow_up:

src/core/configuration.jl
100.00% <0.00%> (+11.11%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


TODO: Create Build file

Since we're not doing a dot.net project, we won't need to make a make file. Instead the build will be automated with Gradle. We'll have to come up with a Gradle script that runs in the terminal, and spits out a .apk file as the Android executable.


Cannot highlight the searches when comparing Aquitanian vs. Aquitanian or when Square is on the left slot

The highlighting of the neumes by contour does not work if the file uploaded to the left is in square notation and the one in the right is Aquitanian. Or when both are in Aquitanian notation.

You can try with these two Aquitanian:

05_dicit-dominus_pem84540_aquit_AQUIT
06_dicit-dominus_pem84623_aquit_AQUIT

They render correctly, but only the Aquitanian on the left gets highlighted:

Or with a square on the left and an Aquitanian on the right:

07_dicit-dominus_pem84873_square_SQUARE
06_dicit-dominus_pem84623_aquit_AQUIT

They render correctly, but nothing gets highlighted:

I fixed this in commit 28ab3c4 by adding a detection function in src/utils.js called get_annotation_type(MEI_content). Essentially, it gets the @staffDef from the chant and check its lines attribute. If there are more than 1 line, it's Square annotation, otherwise, it's Aquitanian.
// [...]
const staffDef = htmldoc.querySelector('staffDef');
const lines = staffDef.attributes.getNamedItem('lines').nodeValue;
if (lines > 1) {
  return "square";
}
else {
  return "aquitanian";
}


Add support for embedded objects

This adds a second optional parameter when creating a Message to add an embedded object.
#7 Embedded Objects
https://discordapp.com/developers/docs/resources/channel#embed-object

Thanks!

Thanks, fixed in v1.0.2.


Segfault when exiting after unit blocked error

I observed this twice, first with 2 ceph-osd units blocked, second with one ceph-mon unit blocked:
$ cou upgrade --auto-approve

...

Running cloud upgrade...
Verify that all OpenStack applications are in idle state ✖
2024-07-02 02:29:41 [ERROR] Unit in blocked: ceph-mon/2
2024-07-02 02:29:41 [ERROR] See the known issues at https://canonical-charmed-openstack-upgrader.readthedocs-hosted.com/en/stable/reference/known-issues/
Segmentation fault (core dumped)

Also observed when ceph-osd/2 was in error:
$ cou upgrade data-plane --auto-approve --force
...
Running cloud upgrade...
Verify that all OpenStack applications are in idle state ✖
2024-07-11 04:29:50 [ERROR] Unit in error: ceph-osd/2
2024-07-11 04:29:50 [ERROR] See the known issues at https://canonical-charmed-openstack-upgrader.readthedocs-hosted.com/en/stable/reference/known-issues/
Segmentation fault (core dumped)

I tried to get a traceback, hopefully this helps:
$ PYTHONFAULTHANDLER=1 cou upgrade data-plane --force --auto-approve
...
Running cloud upgrade...
Verify that all OpenStack applications are in idle state ✖
2024-07-11 04:38:48 [ERROR] Unit in error: ceph-osd/2
2024-07-11 04:38:48 [ERROR] See the known issues at https://canonical-charmed-openstack-upgrader.readthedocs-hosted.com/en/stable/reference/known-issues/
Fatal Python error: Segmentation fault

Current thread 0x00007f8b0237c000 (most recent call first):
  Garbage-collecting
  File "/usr/lib/python3.10/asyncio/queues.py", line 164 in get
Segmentation fault (core dumped)

Maybe something like an async thread was still executing when sys.exit was called?  Maybe a bug in python itself?
python3.10/now 3.10.12-1~22.04.3 is the version that apt reports is installed.  Ubuntu jammy.


feat(Actions): modify prototype to get scene props

I modified the prototype of Actions[key] in order to have access to the scene props. This is very useful in this auth scenario where you'd simple add a propType like <Scene key="someSceneKey" forbidden={true} /> and have access just with Actions.someSceneKey.forbidden, etc
I don't know if prototypes are the best way to go but it was the only one to avoid breaking changes..

@enapupe looks quite complex and it doesn't return changed props (with Actions.refresh), so we would receive complaints for it at the future for sure. Could you just re-use existing Actions.get(SCENE_KEY) (sorry, it is not documented yet, but it should return actual state of Scene with key==SCENE_KEY?

Yeah, I could definitely use Actions.get(), but i couldn't find anything like this. Could you link the source? Thanks for your attention.

Just try it :) It is set from Router like all other actions.

ExceptionsManager.js:55 _reactNativeRouterFlux.Actions.get is not a function
There is no get() in the Actions.js file.. Could you be more specific?

ExceptionsManager.js:55 _reactNativeRouterFlux.Actions.get is not a function
There is no get() in the Actions.js file.. Could you be more specific?
edit:
I see there is something in Router.js:95 but I can't call it from Actions

Never mind, I was running outdated code while looking to master branch..

So, the function is there but it isn't finding my scene..  I don't see any reasons to not, also, the used function (findElement) has a lot more logic than a simple find. What is the role of ActionConst.REFRESH in this?

Strange, it worked well for (i'm using it to open/close drawer)

IDK why. My navigationState root scene has only ONE children (the first registered scene) but the scenes property has all the scenes there..

@aksonov I was debugging that case where get does not return my scenes and realized the get only finds scenes in the current navigation stack, so it is definitely not a solution. I need a function to get props for ANY registered scene.


SRS Stage example is incorrect

Describe the error
The example in the How it works section of WaniKani's SRS Stages is incorrect
Describe the correction
Currently the copy is the following:

Correct (+1 level, so it’s now at SRS level 2)
Correct (+1 level, SRS level 3)
Correct (+1 level, SRS level 4)
Incorrect once before getting it correct (-2 levels, SRS level 2)
Correct (+1 level, SRS level 3)
Correct (+1 level, SRS level 4)
Correct (+1 level, SRS level 5 GURU)

Corrected it should be

Correct (+1 level, so it’s now at SRS level 2)
Correct (+1 level, SRS level 3)
Correct (+1 level, SRS level 4)
Incorrect once before getting it correct (-1 levels, SRS level 3)
Correct (+1 level, SRS level 4)
Correct (+1 level, SRS level 5 GURU)

Additional context
There is a penalty factor of 2 applied for SRS stages at 5 and higher. Anything below is a factor of 1. I double-checked this by looking at the code just to make sure :)

I would like to make a suggestion to perhaps describe the penalty factor and provide two examples illustrating both halves.


fix(key): support very long buffered input

Fixes #502.
First two commits from #568 and #569.
Split away from #511 as discussed in https://github.com/charmbracelet/bubbletea/pull/511#issuecomment-1287061948
cc @muesli

@muesli this is ready again.


Need to implement waiting room before entering into the main room ac

Need to implement waiting room before entering into the main room in twilio

Hi @rohith231 - thanks for the feature request!
Unfortunately, we don't have plans to add this feature to this app. However, if you could provide me with some more detailed information about the feature you have in mind, I might be able to point you in the right direction.
In the meantime, it may be worthwhile to check out this related tutorial: https://www.twilio.com/blog/telemedicine-waiting-room-video

Hi, Need to Implement Design UI Twilio Video React app waiting Room Consultation for the exisiting code
After the user Joins the room There will be waiting room only enter when the doctors admits its same like Google meet admin permssion.
Need to implement waiting screen rather than click to join the video

Objective:
The objective is to allow patient wait in a waiting room in case the previous consultation is in progress. This will allow provider to valid if the right patient is in the waiting room and can admit them accordingly
Description:
Patients joining the link while another consultation is in progress will wait in the waiting room.
While the patient is waiting, patient will be able to
a.        View the provider  information
b.       Test their audio/video link
c.       Chat will provider incase they need assistance to join the call
d.      A countdown of when the consultation will start
e.       Add a 3rd party
Patient will be able to join the consultation only after the provider admits him


Stop workers of deleted algorithms

When an algorithm is deleted, stopProcessing should be sent to all running workers of that algorithm

@yehiyam
Solved?


Kick off analyze gene coverage from CoverageSettings dialog

Need a way to kick off 'analyze gene coverage' from new Coverage Settings dialog.  (Used to be accomplished by 'Analyze all' button).

I think we can hold off on this until after release 4.0.  Are you okay with that @mvelinder @AlistairNWard ?  If the cutoffs are set in the 'Insufficient Coverage' popup, it seems like the genes are getting refreshed properly to show exons that don't meet the coverage min, mean, and median. .

Just so I'm clear, this means I click Assess Coverage from the menu bar?
If I go into this and change the settings, then click Apply, the hover over an exon will show the new values, but the exons themselves aren't flagged, and the count of genes that have exons failing coverage (e.g. in the left panel, and in the menu bar in the Assess Coverage button) does not update. It seems like we would have to have these update, otherwise someone applying more stringent coverage rules would not realise that some exons now fail unless they go through every gene and hover over the exon.
If I'm understanding the issue correctly, I would say the updating has to work for this to available. But we could just make it so the user can't edit the values for now, rather than fixing

Damn it.  Is this broken?

I'm not super clear what the issue is here. Sounds like we're talking about two different things?

@mvelinder I was just guessing. I have no idea what CoverageSettings is referring to, and this was my best guess!

Sorry.  Will is working on this issue.  Basically, if you click on the 'Assess Coverage' in the nav bar and change the cutoffs and press 'Apply', the app is supposed to automatically review the coverage in the exons to see if any should be highlighted as 'insufficient coverage'.  This appears to have some quirks right now, so the functionality isn't quite there.


Missing OfflineDefinitionUpdateVerifySig documentation

The new OfflineDefinitionUpdateVerifySig setting is not listen on 'Set preferences for MDE for Linux' page: https://learn.microsoft.com/en-us/microsoft-365/security/defender-endpoint/linux-preferences?view=o365-worldwide

@Dansimp Please help us in resolving this issue. Thanks

To make it easier for you to submit feedback on articles on learn.microsoft.com, we're transitioning our feedback system from GitHub Issues to a new experience.
As part of the transition, this GitHub Issue will be moved to a private repository. We're moving Issues to another repository so we can continue working on Issues that were open at the time of the transition. When this Issue is moved, you'll no longer be able to access it.
If you want to provide additional information before this Issue is moved, please update this Issue before December 15th, 2023.
With the new experience, you no longer need to sign in to GitHub to enter and submit your feedback. Instead, you can choose directly on each article's page whether the article was helpful. Then you can then choose one or more reasons for your feedback and optionally provide additional context before you select Submit.
Here's what the new experience looks like.
Note: The new experience is being rolled out across learn.microsoft.com in phases. If you don't see the new experience on an article, please check back later.
First, select whether the article was helpful:

Then, choose at least one reason for your feedback and optionally provide additional details about your feedback:

Article was helpful
Article was unhelpful

Finally, select Submit and you're done!


Update template/demo with filtering, paging and sorting features.

Where at least everything is happening on the client side. It would be nicer of course if filtering, paging and sorting are server side.

Thanks for the suggestion.
 We’ve designed the existing ones to be what we think is the preferred balance.
For features like paging/sorting/filtering, it would be preferable for there either to be an external tutorial, or a grid component that already has that built in.


[Backport 2.x] Bump org.apache.zookeeper:zookeeper from 3.9.0 to 3.9.1 in /test/fixtures/hdfs-fixture

Manual backport of https://github.com/opensearch-project/OpenSearch/pull/10506 to 2.x line.

❌ Gradle check result for f52ebc4: null
Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

https://github.com/opensearch-project/OpenSearch/issues/8932


Remove "Enter your name" field from registration

Country offices should decide what to ask for in the registration survey, including whether to ask for a name or not.

"Change your profile" button should allow to re-do the registration survey in the future.
For now, remove the "Change your profile" button.


Standardize usage of sync.WaitGroup

Description of Changes

Removes unnecessary indirection when embedded on a struct
Standardizes naming to the ecosystem standard wg

Please check that the PR fulfills these requirements

[x] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been added / updated (for bug fixes / features)
[x] Add a changelog entry (for non-trivial bug fixes / features)
[x] CI passes

Log Files
Logs / Second
CPU Avg (%)
CPU Avg Δ (%)
Memory Avg (MB)
Memory Avg Δ (MB)

1
1000
1.7759001
+0.10345876
126.322464
-2.7075806

1
5000
5.879401
-0.10343361
135.13686
-0.83013916

1
10000
11.914196
-0.4138193
143.4173
+1.5014801

1
50000
57.1394
-2.6385994
175.0528
-1.4869385

1
100000
112.873024
-1.7120895
226.98087
-5.9439697

10
100
2.103484
-0.120690584
130.50323
-2.272766

10
500
6.827753
+0.3449049
134.8913
-2.4506989

10
1000
13.258868
-0.36254406
145.72252
+3.0802765

10
5000
62.52146
-1.1080513
180.64102
-5.083252

10
10000
134.88258
+6.3479614
236.77142
+3.0789337


Verifier side not working

I am getting 'Error generating proof'.

Very less information from my side..


Pass PodEnvironmentConfigMap to results

Fixes #476 issue.

Coverage remained the same at 23.705% when pulling 4a090044657a7e20968758800785b20c2d5ab95f on kupson:fix-pod-env-cm into ed6acc117804e7edea9fe2346d4bff5487227078 on zalando-incubator:master.

Yes, I can confirm the issue, and after a short testing I don't see any drawbacks of proposed change.


ORC-327. Fix java unit test cases to pass when -Duser.timezone is set.

It moves the SimpleDateFormat constructor, which stores the timezone, into the place where the timezone is controlled.
It also sets the testOldTimestamp to explicitly use America/Los_Angeles.
Finally, it uses string dates instead of longs in TestFileDump.testDataDump.

+1


Fix owner link for "rocker-compose"

Hey @veggiemonk
just fixing a broken link for rocker-compose.
Cheers!

Ahhh, okay. So the tool is requiring the link to be broken or removed. That's funny! Should we remove the first link ?

Both links for rocker and rocker-compose should be By [@grammarly](grammarly) and we need to add
[grammarly]: https://github.com/grammarly

at the end of README.md

Hey @agebhar1,
can you have a look if it's correct now?
Cheers,
Peter

Looks good @spekulatius :+1: - thank you

Cool, thanks for checking!


Hadoop segment index file rename

Description
Segment index file zips are now renamed from the index task, rather than in the hadoop reduce job. When index file renaming
occurs in the hadoop reduce job, it was found that at times, the final index file would get deleted because of a race condition
between between job retries.
Manually tested this using the hadoop ingest tutorial: https://druid.apache.org/docs/latest/tutorials/tutorial-batch-hadoop.html
This PR has:

[x] been self-reviewed.

[ ] using the concurrency checklist (Remove this item if the PR doesn't have any relation to concurrency.)

[x] added documentation for new or modified features or behaviors.
[x] added Javadocs for most classes and all non-trivial methods. Linked related entities via Javadoc links.
[ ] added or updated version, license, or notice information in licenses.yaml
[x] added comments explaining the "why" and the intent of the code wherever would not be obvious for an unfamiliar reader.
[x] added unit tests or modified existing tests to cover new code paths, ensuring the threshold for code coverage is met.
[ ] added integration tests.
[x] been tested in a test Druid cluster.

I ran both the indexing-hadoop and indexing-service module unit tests with both java8 and java11 locally, and ran ITHadoopIndexTest locally with both java8 and java11.

Some additional color- this was done to fix a race condition that was suspected to be something with s3 deep storage (using Hadoop's s3n adapter) that goes like:

Reducer A launches
Reducer A successfully uploads a segment to temp location
Reducer A starts renaming the temp segment to the final location (this is really a delete of the final location if it exists, then a copy of the temp to the final, and finally deletion of the temp)
Reducer A takes too long, triggering a replica Reducer B to be launched speculatively
While Reducer A is still copying the temp to the final, Reducer B finishes ingesting and uploads its temp file.
While Reducer A is still copying the temp to the final, Reducer B issues a delete for the final file being written by A, because  is "renaming" its temp file
Reducer A finishes its rename
Deletion issued by Reducer B in step 6 takes effect and deletes the final segment
Reducer A completes, because it finished the rename
Reducer A finishes, so it's the "winning" speculative execution replica, and Reducer B gets terminated before it can finish moving its temp file to the final location, leaving just its temp file (is this how Hadoop speculative execution works?)

The intent was to fix a problem where sometimes, instead of index.zip being present in the final location, it's index.zip.1 or something like that. We do believe this fixed the problem, although the cost is that all the renames got moved to the launcher index_hadoop job rather than being spread throughout the various reducers. It would potentially slow down jobs that create large numbers of segments using large numbers of reducers.


Provision command

Adds a chef provision command to ChefDK. I created this because, when I was working on a Policyfile "walkthrough" blog post, I had no good way to provision production-y machines (which I needed to properly demonstrate how cookbook "versioning" works in Policyfiles). I mostly like how Chef Provisioning works but I wanted some command line integration for convenience.
For now, I'm considering this an experimental feature. It covers my use cases but I'm only scratching the surface of what you can do with Chef Provisioning, so it's possible that some design decision I made will not produce a good user experience for many cases, therefore I want to explicitly reserve the right to make radically breaking changes for a little while. Once this is shipped I'll solicit feedback and we'll see how it goes. When everything seems stable, I'll take off the warning and add a complementary cookbook generator.
@chef/client-core

Also, now that ChefDK depends directly on Chef Provisioning, maybe we should remove Chef Provisioning from the omnibus package and just manage the version via ChefDK's gemspec?

:heart:

Now that we have both POLICYFILE_README and PROVISION_README, I think we should just create a README or DOCS folder and move these into that

@tyler-ball I'm cool with that, on the other hand both of these are supposed to be temporary until we have real docs on docs.chef.io.

:cake:

:+1:


Trying to run Legacy Code But not working

Is there an existing issue for this?

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

Steps to reproduce

Install a previous version of flutter by downloading a old version like 2.10.5
run flutter doctor
run flutter run

Actual results
Launching lib/main.dart on Chrome in debug mode...
../local/flutter/.pub-cache/hosted/pub.dartlang.org/another_flushbar-1.12.30/lib/flushbar.dart:350:31: Error: Method 'addPostFrameCallback' cannot be called on 'SchedulerBinding?' because it is potentially null.

'SchedulerBinding' is from 'package:flutter/src/scheduler/binding.dart' ('../local/flutter/packages/flutter/lib/src/scheduler/binding.dart').
Try calling using ?. instead.
SchedulerBinding.instance.addPostFrameCallback(
^^^^^^^^^^^^^^^^^^^^
Waiting for connection from debug service on Chrome...             25.2s
Failed to compile application.

Logs
Long message but ended with:
[        ]     |       "name": "vector_math",
[        ]     |       "rootUri": "file:///home/archit/local/flutter/.pub-cache/hosted/pub.dartlang.org/vector_math-2.1.1",
[        ]     |       "packageUri": "lib/",
[        ]     |       "languageVersion": "2.14"
[        ]     |     },
[        ]     |     {
[        ]     |       "name": "foo",
[        ]     |       "rootUri": "../",
[        ]     |       "packageUri": "lib/",
[   +1 ms]     |       "languageVersion": "2.16"
[        ]     |     }
[        ]     |   ],
[        ]     |   "generated": "2023-05-19T13:45:22.268951Z",
[        ]     |   "generator": "pub",
[        ]     |   "generatorVersion": "2.16.2"
[        ]     | }
[   +1 ms] MSG : Changed 25 dependencies!
[  +43 ms] Running "flutter pub get" in foo... (completed in 3.5s)
[ +125 ms] Generating /home/archit/foo/foo/android/app/src/main/java/io/flutter/plugins/GeneratedPluginRegistrant.java
[   +5 ms] Wrote 96 files.
[        ]
All done!
[   +1 ms] In order to run your application, type:
         $ cd foo
         $ flutter run

       Your application code is in foo/lib/main.dart.

[   +1 ms] "flutter create" took 3,995ms.
[ +256 ms] ensureAnalyticsSent: 253ms
[   +3 ms] Running shutdown hooks
[   +1 ms] Shutdown hooks complete
[   +6 ms] exiting with code 0
Flutter Doctor output
[✓] Flutter (Channel stable, 2.10.5, on Ubuntu 22.04.2 LTS 5.19.0-41-generic, locale en_IN)
• Flutter version 2.10.5 at /home/archit/local/flutter
• Upstream repository https://github.com/flutter/flutter.git
• Framework revision 5464c5bac7 (1 year, 1 month ago), 2022-04-18 09:55:37 -0700
• Engine revision 57d3bac3dd
• Dart version 2.16.2
• DevTools version 2.9.2
[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.2)
• Android SDK at /home/archit/Android/Sdk
• Platform android-33-ext5, build-tools 33.0.2
• Java binary at: /snap/android-studio/125/android-studio/jre/bin/java
• Java version OpenJDK Runtime Environment (build 11.0.13+0-b1751.21-8125866)
• All Android licenses accepted.
[✓] Chrome - develop for the web
• Chrome at google-chrome
[✓] Android Studio (version 2021.3)
• Android Studio at /snap/android-studio/125/android-studio
• Flutter plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/9212-flutter
• Dart plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/6351-dart
• Java version OpenJDK Runtime Environment (build 11.0.13+0-b1751.21-8125866)
[✓] VS Code
• VS Code at /snap/code/current
• Flutter extension version 3.64.0
[✓] Connected device (1 available)
• Chrome (web) • chrome • web-javascript • Google Chrome 113.0.5672.126
[✓] HTTP Host Availability
• All required HTTP hosts are available
• No issues found!

I used github actions too giving similar results: https://github.com/architsangal/Portfolio/actions/runs/5024837491/jobs/9011019006

Hi @architsangal
The fix is suggested clearly in the error message:

Try calling using ?. instead.

For eg:
SchedulerBinding.instance?.addPostFrameCallback

Moreover, since the error comes from 3rd party package (another_flushbar), you should report issue there. I also see an existing issue related to this (https://github.com/cmdrootaccess/another-flushbar/issues/81).
And please also check Migrating to null safety for more information.
Closing since the error is showing as expected. Your question is best suited for support channels like StackOverflow, so please ask the same there for solutions if any.


WebSocket upgrade failed: Unspecified connection error (200). USP state: 2. Received audio size: 0 bytes.

The result returned each time is ResultReason.Canceled

more detail msg:
WebSocket upgrade failed: Unspecified connection error (200). USP state: 2. Received audio size: 0 bytes.

It seems that Microsoft has deliberately done some changes to prevent 3rd party tools(such as aspeak) using their trial service.

I guess this two cookies are the main reason that prevents aspeak from functioning, but I will double check it later.
If this is the case. The fix won't be easy because we need to reimplement most of azure-cognitiveservices-speech and remove it from requirements.txt.

Or we can use our own API

I decided to end this mouse & cat game and thus drop support for the trial service. I do not have enough time to fight against Microsoft. I'm just an undergraduate with tons of course works to do and lots of deadlines to catch. (And I have another PR to work on: jobisoft/CategoryManager#86)
However, I'm willing to accept PRs that re-enable the token-free trial service.
You need an azure subscription to continue to use the next major version of aspeak.
A free azure subscription(credit card needed) provides you 5 audio hours free per month, which is enough for daily usage. You can also choose a nearby region to lower latency, which is not possible in the trial service.
Unfortunately,  azure didn't accept my prepaid card, which means I do not have a subscription for testing purpose.

Although  have some regrets, I still appreciate what you have done before. I'm also trying to use Python selenium to solve this problem temporarily.
Good luck.

Can anyone else fix up the code?

Can anyone else fix up the code?

This won't be an easy fix.
I have already fixed the voice listing function(aspeak -L): https://github.com/kxxt/aspeak/commit/127a7a42a2785796e68102cf3e0cb3ed71de25ab
To fix other things, you need to attach header Origin: https://azure.microsoft.com to the websocket connection. But that is controlled by Microsoft propriety native code.

https://azure.microsoft.com/zh-cn/products/cognitive-services/speech-translation/
This address can obtain the token as before

Fixed in v3.1.0.


[Bug] (Minor) Variable DUMP_ADDITIONAL_RADIO_LIST not mentioned in Docker file and documentation

Available in release 2022-12-07.2


New Dataset: Cape Town - South Africa

https://web1.capetown.gov.za/web1/OpenDataPortal/DatasetDetail?DatasetName=Street addresses

Is there any comparison to https://github.com/openaddresses/openaddresses/blob/master/sources/za/wc/cape_town.json ?

Ah! Already exists.


feat!: rename label to desc for mapping descriptions

This aligns the mapping API closer with the core keymap.set lua API in Neovim
This is a continuation on #1186

Sorry for disturb you all, but when this PR is merged, is there any other way we can set the desc attribute of a single key?

Sorry for disturb you all, but when this PR is merged, is there any other way we can set the desc attribute of a single key?

please explain the purpose of what you want to do, why do you need another way

Hi @coffebar, Thank you for your response. In my workflow I often rely on which-key to do the key prompting for me, and the which-key plugin in turn relies on the desc property of key (specified by the opts parameter of vim.keymap.set)
Prior to this pr merge, I would have configured the above workflow in this way
require('neo-tree').setup({
    window = {
      mapping_options = {
          silent = true,
          noremap = true,
          nowait = true,
      },
      mappings = {
          ['a'] = { command = 'noop', desc = 'which_key_ignore' },
          ['fi'] = { command = 'foo', desc = 'Show file details.' },
      },
    }
})

But after this pr merge, the desc attribute that was previously set won't work, because it will be filtered out here
https://github.com/nvim-neo-tree/neo-tree.nvim/blob/dcef81d96e0678b01cca5445cffb9a3ae0e9ce4f/lua/neo-tree/ui/renderer.lua#L827
This caused me to rework the previous init.lua framework to accommodate the change.

That should be considered a bug on my part. Sorry! That should not be getting filtered out 😓

I opeened #1206 to resolve this. It also does a step further and makes sure desc is set when using functions based on string.


feature request - add option to memory and disk caches to cache responses based on response headers

When using fetch in the browser only responses returning an appropriate cache-control header are cached. This is useful when dealing with uncachable responses or responses that expire at a different (or unpredictable) rate.
By adding this option we spare entries from being vacuumed unlike using a interval-based approach since the cache-control header states how long the response can be cached and we know exactly which responses are stale and which are still fresh.

Hello, have you considered make-fetch-happen? It might be better for you since it supports caching based on headers.

Closing: make-fetch-happen is likely a better choice if you need caching based on response header semantics. This module is intended to cache everything.


ModuleNotFoundError after pip upgrade to 0.72.1

Home Assistant release with the issue:
0.72.1
Last working Home Assistant release (if known):
0.71.0
Operating environment (Hass.io/Docker/Windows/etc.):
Python 3.6.4 virtualenv in Ubuntu 16.04.4 x86-64
Component/platform:
Frontend
Description of problem:
ModuleNotFoundError after running pip install -U homeassistant to upgrade in place from 0.71.0 to 0.72.1.  HASS was not running during the pip upgrade.
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
config:
  frontend:
    javascript_version: es5

Traceback (if applicable):
2018-07-06 10:58:07 ERROR (MainThread) [homeassistant.setup] Error during setup of component frontend
Traceback (most recent call last):
  File "/home/buh/homeassistant/lib/python3.6/site-packages/homeassistant/setup.py", line 143, in _async_setup_component
    hass, processed_config)
  File "/home/buh/homeassistant/lib/python3.6/site-packages/homeassistant/components/frontend/__init__.py", line 235, in async_setup
    import hass_frontend_es5
ModuleNotFoundError: No module named 'hass_frontend_es5'

Additional information:
Reverting to 0.71.0 allows HASS to run again, e.g. pip install -U homeassistant==0.71.0
The Frontend did appear to work, but with a card that said that there was an error with the frontend, and also with logbook.

Closing.  Whatever it was in 0.72.1 seems resolved in 0.73.1.


Add ulimit to docker build

Signed-off-by: Lei Jitang<EMAIL_ADDRESS>I think ulimit should also be added to docker build.
With this we can do more resource constraint to docker build
and protect the host.

update as @cpuguy83 's suggestion

This looks good, the one thing I'm not sure about is passing in these params via base64 encoded header.
Any thoughts on this?

Other parameters for the build endpoint are sent as query-params, I think? Are there clients (that we know of) that put a max-length restriction on the query-string?

I found that PR #9176 also passing params via base64 encoded header. For the passing params via base64 encoded header, WDYT? @jfrazelle  @LK4D4  @estesp

update use get param to passing these params. thanks all. ping @cpuguy83  @vieux  @thaJeztah

Just needs some tests.. can probably append to the resource constraint on build test.

Needs docs in the command line reference as well, and a description of the --ulimit flag below the "options" section in the man-page (but we're not in "docs-review" yet)

thanks I'll add  these tomorrow

ping @cpuguy83  @jfrazelle test is added
@thaJeztah  the docs is updated

One nit, but LGTM.

Except for of course the windows build is not working, but I think that's unrelated.

@cpuguy83 PR was updated and builds retriggered, PTAL

ping @cpuguy83

Still LGTM

rebased due to conflict

ping @vieux PTAL

@coolljt0725 Tests failed; got a panic;
DockerSuite.TestBuildResourceConstraintsAreUsed             0.98

----------------------------------------------------------------------
PANIC: docker_cli_build_test.go:5275: DockerSuite.TestBuildResourceConstraintsAreUsed

... Panic: runtime error: index out of range (PC=0x43D7E5)

/usr/local/go/src/runtime/panic.go:387
  in gopanic
/usr/local/go/src/runtime/panic.go:12
  in panicindex
docker_cli_build_test.go:5316
  in DockerSuite.TestBuildResourceConstraintsAreUsed
/usr/local/go/src/reflect/value.go:296
  in Value.Call
/go/src/github.com/docker/docker/vendor/src/github.com/go-check/check/check.go:763
  in func.003
/go/src/github.com/docker/docker/vendor/src/github.com/go-check/check/check.go:657
  in func.001
/usr/local/go/src/runtime/asm_amd64.s:2232
  in goexit

@thaJeztah  test failed fixed

ping ....

@coolljt0725 Sorry for this, but need another rebase :/

ping @LK4D4  @cpuguy83  rebased

Collective review with @jfrazelle @crosbymichael @calavera
@coolljt0725 Any reason why you can't just set this on the daemon? Does it have to be a per-build setting?

I'm not sure if this PR was abandoned. I'm tentatively closing it, but please ping us here (or even better on IRC) if you need it reopened!

Sorry, I just miss the notes. sorry for the late response. I think why we need this is we always get some untrusted Dockerfile, so we should use a more strict limit than the global set on daemon. ping @icecrime

ping @cpuguy83  @icecrime  @LK4D4  rebased base on the latest master

Build failed (not related);
/go/src/github.com/docker/docker/hack/make.sh: line 278: local: can only be used in a function
@tiborvass I think you mentioned this issue on IRC?

@thaJeztah yes i'm not sure why that happens, I restarted the builds let's see how it goes.

Yet again sorry @coolljt0725, this needs another rebase :/

LGTM. Let's merge it as soon as we have a rebased branch.

Still needs documentation as well, I think the docs (https://github.com/docker/docker/pull/12850#issuecomment-101562869) got lost during a rebase somewhere.

@calavera @LK4D4  @thaJeztah  @abronan  rebased

Rebased, I think the experimental Jenkins failed is unrelated.

Thanks @coolljt0725 ; I've moved to docs review
Seems like to finish up docs there was a request to add the description of ulimit options to the docs; @thaJeztah can add more info on what is needed.

Thanks for the ping, @estesp, I see the flags are mentioned again in the docs.
I wonder if we should add a link to the docker run docs for this option so that we don't have to repeat all information that's already present there.

I agree, a link in build.md to run.md#setting-ulimits-in-a-container, and to **docker-run(1)** in docker-build.1.md would be very useful.
I'd also love a sentence in build.md telling the reader why they'd like to use it for builds, but that might be harder.

updated the docs

Thanks @coolljt0725. Apart from fixing the links, this LGTM :+1:

update the docs as @thaJeztah 's suggestion

Docs LGTM. Thanks @coolljt0725 !
ping @fredlf @jamtur01 @moxiegirl @SvenDowideit

@coolljt0725 sorry needs a rebase

rebased

LGTM with @jamtur01's comment resolved

thanks @SvenDowideit  update the docs

LGTM; looks like all doc updates have LGTM + prior LGTM--going to merge


Overload of operator for percentages

See https://github.com/printfn/fend/pull/165#issue-1337725749 by @Techcable:

Proposal to overload of
I propose overloading the of operator specifically to handle this case with percentages. We would have 5% of 100 == 5, while multiplication would give 500%. This would clear up any ambiguity (although I would probably file a separate issue/PR).
It should not cause issues with any other operations, since it would only activate when a percentage is on the left-side of the of operator (similar to how string concat is special-cased in many languages).

What is the current purpose of the of operator?

I did an experiment of adding objects (key-value pairs) to fend at one point, and used the “of” operator to access members. For example, “earth” is defined as an object with a bunch of properties, including “mass” and “volume”. You can type “mass of earth” or “volume of earth” to get that property value.
This idea was never fully fleshed out though - there’s no way to create custom objects currently, and the “of” operator doesn’t have any other meaning.

I did an experiment of adding objects (key-value pairs) to fend at one point, and used the “of” operator to access members. For example, “earth” is defined as an object with a bunch of properties, including “mass” and “volume”. You can type “mass of earth” or “volume of earth” to get that property value.
This idea was never fully fleshed out though - there’s no way to create custom objects currently, and the “of” operator doesn’t have any other meaning.

That’s a cool idea, it very unfortunate it was never actually implemented

This has been implemented in #244 and will be included in the next release.


Should update the gateway information

Kindly update the Create flows in the right environment content as:
Gateway installation is now enabled for also non-default environments.
https://docs.microsoft.com/en-us/power-platform-release-plan/2019wave2/power-automate/support-gateways-all-environments

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

ID: 66ddd5e3-db39-4f50-4be4-71ae16dd19d2
Version Independent ID: 61cafb41-19d2-24cc-a17f-85a36b22b4fa
Content: Learn about Power Automate environments - Power Automate
Content Source: articles/environments-overview-maker.md
Service: flow
GitHub Login: @sunaysv
Microsoft Alias: sunayv

@DavidPaf  Thanks for reporting this issue. This is fixed, and will be available later today.


367 experiment registry

Fixes #367
Looks up the experiment plan from a "registry" which can later be made more dynamic
To test:

Consider if this is a good way to approach this?
Run tests

@callumforrester and @abbiemery this will basically be replaced by blueapi soon, is there any way we should change this to make that move easier?

@DominicOram Probably not, current thinking for blueapi is to have a module full of plans and build the registry automagically from that.


[Feature Request] add a timeout property to the tooltip

Existing Component
Yes
Component Name
el-tooltip
Description
It would be nice to be able to hide a tooltip after a timeout.

Sorry, we have no plan to support this.


drivers: sensor: stm32_temp

STM32 internal temperature sensor driver.
This sensor can be used to measure the temperature of the CPU
and its surroundings.
Related issue: https://github.com/zephyrproject-rtos/zephyr/issues/34538
Signed-off-by: Eug Krashtan<EMAIL_ADDRESS>

I'd like to make a change in sensor.h after merging https://github.com/zephyrproject-rtos/zephyr/pull/34679
Please review it first.

@MaureenHelm Thank you. I did all the requested changes.

^^ @StefJar

@StefJar Thank you for comment. Just checked with STM32F412RE.
Bit TSVREFE sets ok, adc_stm32_set_common_path(dev) was resolved to
__STATIC_INLINE void LL_ADC_SetCommonPathInternalCh(ADC_Common_TypeDef *ADCxy_COMMON, uint32_t PathInternal)
{
  MODIFY_REG(ADCxy_COMMON->CCR, ADC_CCR_TSVREFE | ADC_CCR_VBATE, PathInternal);
}

in file stm32f4xx_ll_adc.h and debugger shows CCR=0x00800000 (i.e.  ADC_CCR_TSVREFE set)
So this part of the code has no problem in STM32F4
Values from ADC also changed as expexted when heating, but STM32F4 has another formula to calculate the temperature.
Will change stm32_temp_channel_get accordingly.

@erwango @StefJar Probably have the sense to move AVGSLOPE and V25 values to Kconfig section? And unify formula for all chips? Will investigate this ASAP

@erwango One small question - is it possible to use something like "platform_allow" in sample.yaml, but select the whole STM32 family instead of a board name like nucleo_xxx?
Or how to restrict buildkite in a proper way?

is it possible to use something like "platform_allow" in sample.yaml, but select the whole STM32 family instead of a board name like nucleo_xxx?
Or how to restrict buildkite in a proper way?

You can use 'filter' field, for instance:
tests:
  sample.drivers.flash.shell:
    tags: flash shell
    filter: CONFIG_FLASH_HAS_DRIVER_ENABLED

You can also base the filter on dts, which could be even more fine-grained:
    filter: dt_compat_enabled("st,stm32-window-watchdog")

You can also use operators: not, and, or, ...

@erwango Thank you. I've tried the second variant without success, but finally, I understand where is my problem. Hope It's the final push (fingers crossed)

@FRASTM Yes, right now it runs here on devboard since yesterday.

@FRASTM  I have question about STM32G4 HAL. In this HAL there is no definition for ADC_CHANNEL_TEMPSENSOR, common for all other HALs. Is it possible to add
#define ADC_CHANNEL_TEMPSENSOR ADC_CHANNEL_TEMPSENSOR_ADC1

to file stm32cube\stm32g4xx\drivers\include\stm32g4xx_hal_adc.h ?

@ABOSTM Yes, fixed with ARRAY_SIZE() instead of sizeof(), as this table contains uint16 values.


Update Read Properties from File to Read Parameters from File

Describe the bug
The name of a Task is incorrectly referencing Properties which are now deprecated
Expected behavior
Task uses the Parameters terminology

Hi @amhudson ready for a loader update.

https://github.com/boomerang-io/flow.loader/pull/21


CPKAFKA-465 : Exactly once transactional producer -- initial implementation

The basic flow works: find coordinator, get pid, add partitions to transaction, commit/abort.
Still to add:

'sendOffsets' implementation.
error handling.
failure test cases.

Opened against the wrong branch.


Error building project with google maps plugin

Hi,
I successfully built a sample app with a previous version of your plugin, however with the new version of the plugin i get build errors as shown below. I see now you have removed the dependancy on the old nativescript-plugin-google-play-services plugin.
A problem occurred configuring root project 'games'.

Could not resolve all dependencies for configuration ':_nativescript-google-maps-sdkDebugCompile'.
Could not find any matches for com.google.android.gms:play-services-maps:+ as no versions of com.google.android.gms:play-services-maps are available.
Searched in the following locations:
https://jcenter.bintray.com/com/google/android/gms/play-services-maps/maven-metadata.xml
https://jcenter.bintray.com/com/google/android/gms/play-services-maps/
file:/Users/osx/Development/nativescript/gmaps/platforms/android/libs/aar/
file:/Volumes/UserData/usr/local/opt/android-sdk/extras/android/m2repository/com/google/android/gms/play-services-maps/maven-metadata.xml
file:/Volumes/UserData/usr/local/opt/android-sdk/extras/android/m2repository/com/google/android/gms/play-services-maps/
Required by:
:gmaps:unspecified

I do have google play installed at the following location:
/Volumes/UserData/usr/local/opt/android-sdk/extras/google/google_play_services/libproject/google-play-services_lib/libs/
I am new to android and gradle builds. I thought that since you had the dependency in your include.grade file that the gradle build would take care of including the google map dependency.
I know previous to the gradle integration that you had to use a library add to add the google play jar file. Am i missing something here?
dependencies {
compile 'com.google.android.gms:play-services-maps:+’
}
Also did you have any plans on adding the my location option to your plugin?
Many thanks for a great plugin.
Peter

Looks like gradle can't find the play-services-maps Android library, which needs to be installed on your machine.  Verify that you have the latest Google Play Services installed https://developer.android.com/sdk/installing/adding-packages.html

For my location, you should be able to do something like this, although I haven't tested it:
function onMapReady(args) {
    var mapView = args.object;
    var gMap = mapView.gMap;

    console.log("Setting a marker...");

    if(mapView.android) {
        gMap.setMyLocationEnabled(true);
    }

    if (mapView.ios) {
        gMap.myLocationEnabled(true);
    }
}

I had google play installed and after i added the google repository my project built successfully.
Also the my location button appeared on android after adding your code suggestion. I did have to add an extra permission to the android manifest:

Although everything builds ok and I can see the location button, there is no map shown.
Do you have any suggestions on why this might be?
I'm pretty sure the API key is correct as I have used it before.
It's difficult to debug since 1.5.1 no longer outputs the android logcat as default.

It now works perfectly.
Many thanks for your help with this.
My last issue as to do with incorrect credentials to the API.

Great - glad to hear it's working now.  Enjoy!


Adding peak filtering by multiple of non zero median

Adds a peak filtering option where user specifies a multiple of the non-zero median to set the peak filtering threshold. See issue #19

Looks like a nice addition, thanks Adam.


Update version to 1.2.72-0 on staging

Update version to 1.2.72-0

Hey! I see that you made changes to our Form component. Make sure to update the docs in FORMS.md accordingly. Cheers!


Fixed typo

Coverage remained the same at 97.531% when pulling 864541a2a79ecdf15b3f1d49d674d7b852d3c857 on julienetie:patch-1 into 947ecf92b67d25bb693a0f625fa8e90c099887d5 on Matt-Esch:master.


feat: support retrying failed requests

📰 Summary of changes

What is the new functionality added in this PR?

This PR adds support for retrying failed network requests. In short, the following is not possible:

Specifying a RetryBehavior "globally" for any request made by the SturdyHttp instance
Specifying a RetryBehavior "locally" for a single request, which takes precedence over the RetryBehavior of the SturdyHttp instance
Relying on the default retry logic provided by defaultRetryClause
Specifying custom retry logic

Notable: This implementation does not rely on Interceptors to handle the actual retry logic as I personally have found retry logic via Interceptors to be problematic in the past. This could be changed if we find the implementation as written to not be satisfactory.
🧪 Testing done

What testing was added to cover the functionality added in this PR

Unit tests added and passing

Codecov Report
Attention: Patch coverage is 58.82353% with 56 lines in your changes are missing coverage. Please review.

Project coverage is 31.46%. Comparing base (141820e) to head (1301489).

Files
Patch %
Lines

lib/src/network_response.freezed.dart
20.00%
36 Missing :warning:

lib/src/sturdy_http_event_listener.freezed.dart
20.00%
12 Missing :warning:

lib/src/network_request.freezed.dart
33.33%
4 Missing :warning:

lib/src/retry_behavior.dart
83.33%
2 Missing :warning:

lib/src/sturdy_http.dart
96.55%
2 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main       #8      +/-   ##
==========================================
+ Coverage   29.25%   31.46%   +2.21%
==========================================
  Files           9       10       +1
  Lines         670      696      +26
==========================================
+ Hits          196      219      +23
- Misses        474      477       +3

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

/no-platform


PL-122: Multipage vertical scroll

Done:
- zoom
- sliding window
- page counting
- switching pages with buttons and keyboard shortcuts
- text rendering
- clean code
- text selection misalignment
TODO:
- navbar does not stay on top (should it be done in this task)?

BUGS:
- two page layout distorted and stretched
It's ready for reviews. I still expect that bugs will be found. It was a large commit, please test it and show the bugs you found.

When you zoom out 2 or more times this happens when you scroll past the last page:

And if you scroll even further:

When you zoom out 2 or more times this happens when you scroll past the last page:  And if you scroll even further:

Fixed by removing the text layers when resizing the pages. Problems was caused by text layers that remained when changing sizes.

You really did a great job here, nice clean code and it works like a charm now. Only problem I have is with registerEvents method in PdfReaderComponent like I wrote in the comments, except that it's +1 from me.

+1 from me


🐛 [firebase_storage] 'FirebaseStorage/FIRStorageTypedefs.h' file not found

Bug report
Describe the bug
With the latest version firebase_storage 10.3.0 iOS build fails with this error: 'FirebaseStorage/FIRStorageTypedefs.h' file not found.
Steps to reproduce
Steps to reproduce the behavior:

pub upgrade to get the latest dependecies
After that firebase_storage is not working on any platform. Before the upgrade it worked fine.
I tested it in two projects. Both throw the same error.

Console output
Lexical or Preprocessor Issue (Xcode): 'FirebaseStorage/FIRStorageTypedefs.h' file not found
/Users/tom/development/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_storage-10.3.0/ios/Classes/FLTFirebaseStoragePlugin.m:6:8

Flutter doctor
Run flutter doctor and paste the output below:
Click To Expand
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.0.3, on macOS 12.4 21F79 darwin-arm, locale de-DE)
[✓] Android toolchain - develop for Android devices (Android SDK version 32.0.0-rc1)
[✓] Xcode - develop for iOS and macOS (Xcode 13.4.1)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2021.2)
[✓] VS Code (version 1.68.1)
[✓] Connected device (5 available)
[✓] HTTP Host Availability

• No issues found!

Flutter dependencies
Run flutter pub deps -- --style=compact and paste the output below:
Click To Expand
- firebase_auth_platform_interface 6.3.0 [firebase_core flutter meta plugin_platform_interface]
- firebase_auth_web 3.3.18 [firebase_auth_platform_interface firebase_core firebase_core_web flutter flutter_web_plugins http_parser intl js meta]
- firebase_core_platform_interface 4.4.1 [collection flutter meta plugin_platform_interface]
- firebase_core_web 1.6.5 [firebase_core_platform_interface flutter flutter_web_plugins js meta]
- firebase_crashlytics_platform_interface 3.2.9 [collection firebase_core flutter meta plugin_platform_interface]
- firebase_storage_platform_interface 4.1.9 [collection firebase_core flutter meta plugin_platform_interface]
- firebase_storage_web 3.2.18 [async firebase_core firebase_core_web firebase_storage_platform_interface flutter flutter_web_plugins http js meta]

@BugsOverBugs
Can you try same as https://github.com/firebase/flutterfire/issues/9012#issuecomment-1172248683 ?

I'm facing the same error... any idea?
I noticed that also on firebase_storage 10.2.18 the same problem occurs.

@BugsOverBugs Can you try same as #9012 (comment) ?

I am using know v10.3.1 and 9.2.0 but know this error is thrown when running pod install:
[!] The following Swift pods cannot yet be integrated as static libraries:

The Swift pod `FirebaseCoreInternal` depends upon `GoogleUtilities`, which does not define modules. To opt into those targets generating module maps (which is necessary to import them from Swift when building as static libraries), you may set `use_modular_headers!` globally in your Podfile, or specify `:modular_headers => true` for particular dependencies.

The Swift pod `FirebaseStorage` depends upon `FirebaseStorageInternal`, `FirebaseAppCheckInterop`, `FirebaseAuthInterop`, `FirebaseCore`, and `FirebaseCoreExtension`, which do not define modules. To opt into those targets generating module maps (which is necessary to import them from Swift when building as static libraries), you may set `use_modular_headers!` globally in your Podfile, or specify `:modular_headers => true` for particular dependencies.

i' facing the same problem when i tried to install that firebase_storage.. anyone has a solution?

To fix this I check my podfile and update the Firebase SDK version to lasted $FirebaseSDKVersion = '9.2.0'


⚠ Bofrost.fr has degraded performance

In 04c6f9d, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 955 ms

Resolved: Bofrost.fr performance has improved in 24f3b50 after 6 minutes.


Starlight sidebar badges outlined style issue

Describe the Bug
Note: the issue has initially been reported in https://github.com/withastro/starlight/issues/1764

Navigate to https://events-3bg.pages.dev/jotter/history-of-changes/ and notice the sidebar entry for this page containing a badge with an outlined style as expected for the current page:

Navigate with a full navigation to https://events-3bg.pages.dev/jotter/ and notice the sidebar entry for the previous page ("Recent changes") with a colored badge as expected as it's not the current page:

Navigate to the "Recent changes" page using the sidebar link and notice that the sidebar badge is not updated to an outlined style as expected for the current page:

What's the expected result?
The sidebar badges should be updated to an outlined style when the page is the current one (and vice versa when it's no longer the current one).
Link to Minimal Reproducible Example
https://events-3bg.pages.dev/jotter/history-of-changes/
Participation

[ ] I am willing to submit a pull request for this issue.

Hi @HiDeoo, really great that you have posted the detailed issue! A reference to the Starlight issue would have sufficed, but of course it's much easier for me to understand this way. Thank you very much for that, I really appreciate it.

Lots of options, see https://github.com/withastro/starlight/issues/1764. Looks like this issue will be closed by https://github.com/withastro/starlight/issues/1530 😄

Closed after https://github.com/withastro/starlight/pull/1530 was merged


setCurrent page method and isLooped prop

Your component is very nice! Thank You!
Could you provide this with method setPage: actually I do it with
this.сarousel._setCurrentPage(cardNum);
this.сarousel._placeCritical(cardNum);
Also it would be nice to have isLooped prop :)

@Yuriy1988 can you share how you did that? my attempt failed :(

Here I have my carousel
<Carousel
ref={ref => (this.сarousel = ref)}

and when I need - I just call this.сarousel._animateToPage(pageNum');
Actually I changed a little the source of сarousel, and if method above will not work for you - let me now, i can share working example;

@Yuriy1988 thanks for the reply! that helped me figure out how to have a reference to the carousel throughout the component
I put this.carousel._placeCritical(); in componentWillUpdate and it seems to have solved my problem
I'd be curious to see your changes though - do you have a diff?

@kevindavis
Sorry, for late response, but i had a lot of work
here is diff
https://gist.github.com/Yuriy1988/b52c060540443c21e7fbbe4f92626a91
Actually, i don't remember what for i changed it :)

thanks!

It's not yet in the docs, but we renamed _animateToPage() to animateToPage().
Feel free to call the method to slide the carousel programatically (it will do the animation as well).
We do also happily accept PRs for other functionality!

As regards the isLooped prop, see my comment to #101.

As regards the isLooped prop, see my comment to #101.


Upgrade Gafi application from level 2 to level 3

Project Abstract

Please provide a brief description of your project here summarising key points (1-2 paragraphs).
If your application is a follow-up to a previous grant, please mention which one in the first line of the abstract and include a link to previous pull requests if applicable.

For which grant level are you applying?

[ ] Level 1:  Up to $10,000, 2 approvals
[ ] Level 2:  Up to $50,000, 3 approvals
[x] Level 3:  Unlimited, 5 approvals (for > $100k Web3 Foundation Council approval)

Application Checklist

[x] The application template has been copied, renamed ( project_name.md) and updated.
[x] A BTC or Ethereum (DAI/USDT) address for the payment of the milestones is provided inside the application.
[x] I have read and acknowledged the terms and conditions.
[x] The software delivered for this grant will be released under an open-source license specified in the application.
[x] The initial PR contains only one commit (squash and force-push if needed).
[x] The grant will only be announced once the first milestone has been accepted.

How Did You Hear About our grants program?

[ ] Social Media
[ ] Hackathon
[ ] Personal Recommendation
[x] Substrate Builders Program
[ ] Investor/VC
[ ] Online Search
[ ] Other: _______

Hi, after months of building, Substrate gives us more clarity on the possible features that we did not add to the Gafi grant application in the first place. We would like to add pallet sponsored pool, pallet cache, and pallet game creator to the delivery of milestones 2 and 3 (milestone 1 we have passed).

player spam join<->leave pools

Can you expand on this? People spam transactions? Why would they do that? Sounds like a problem with the economics.

Every 30 minutes, players in the pool get a specific number of tickets to use for a discount on the transaction fee. When they run out of tickets they would rejoin to refresh the tickets, but the pallet cache will prevent that by giving the remaining tickets to that player when they rejoin.

Thank you for being so supportive, after receiving the grant from milestone 1 we have the momentum. Until now, Gafi is just at the beginning of the long development process, therefore we believe Substrate will give us more ideas and solutions to achieving Level 3.


Determine how exit fees on strategies should be handled

Our initial strategy may be a yVault with a 0.5% exit fee that is charged under some (not all) scenarios. This could result in users seeing a decrease in their OUSD balance which is not ideal. Some ideas:

We keep a reserve buffer to handle withdrawals so we most likely never have to withdraw from the yVault. e.g. 10% assets held liquid, 90% in yVault.
We have a combination of strategies, that allow us to liquidate without fees. E.g. 20% Compound, 80% yVault. All withdrawals come out of the Compound strategy.
Detect if the yVault will charge an exit fee and only allow the withdrawal if it won't (yuck).

Do we still need to keep this open or can we close this and just use #312 to discuss this area of the product?

Do we still need to keep this open or can we close this and just use #312 to discuss this area of the product?

Let's discuss this when we are implementing a specific strategy that needs this.

Let's discuss this when we are implementing a specific strategy that needs this.


Is there a new release coming?

I'm using 0.7.1 since that's what's in crates.io, but I'm running into some unwrapping Error crashes under some circumstances when Python nodes are publishing to me.  Starting to debug that I noticed how old 0.7.1 is.  Is there a new release coming at some point?  If so, will the new release have working docs on docs.rs?
Is there something specific blocking a new version?

I'd say it's inertia.
I'll bump a release right now. Since it's in the 0.x stage, it doesn't matter how many unrelated changes are bundled together.


FarCry 5 cars dont steer ... its only me ?

The game runs excellent , the only problem is that i can drive cars , i can't steer and i changed controls.
Software information
FarCry 5
System information

GPU: NVIDIA 980
Driver: 396.24
Wine version: wine-3.9 (Staging)
DXVK version: 0.53

DXVK doesn't handle input, so this is not my bug.

Sorry , i will ask somewhere. Thanks
By the way , excellent job doing this man !!!


[UI and UX Enhancement] Contact Details Card Addition | Revamp Contact Us Page | FAQs Section Removal (As Already Present on Home Page)

I want to do the following:-

Contact Details Card Addition
Revamp Contact Us Page
FAQs Section Removal (As Already Present on Home Page).

@manikumarreddyu sir, this issue should not be of level 3
make this level 2
but make this issue #827 of level 3, beacuse it has more work this one.

i would like to contribute @manikumarreddyu


Duplicate environments() declaration

Currently breaking tests on master

@gbelorgey Can you solve merge conflicts?

Well there is now a commit on master that fixes the issue, so no point anymore.


Failure to get address of DAC_PAL_InitializeDLL on custom centos build

Hi !
We know that the current port of Clrmd to linux is WIP and highly unstable but we are encountering scenarios where lldb + sosplugin are not enough to get to the bottom of our issues.
We tried playing with clrmd in its current state and we noticed that with our custom build of dotnet (v2.1.4 + a few cherry-picked commits) we fail to load the address of "DAC_PAL_InitializeDLL " in DacLibrary https://github.com/Microsoft/clrmd/blob/master/src/Microsoft.Diagnostics.Runtime/DacLibrary.cs#L74
We solved it locally by loading PAL_InitializeDLL instead. Would you have any pointers as to why this is happening ?
Thanks !
cc @kevingosse who came up with the idea to try to remove the DAC prefix

Hmm interesting, @mikem8361 for an FYI.
I don't have a CENTOS VM to test this with right now.  Maybe the code should look like this?
        IntPtr initAddr = DataTarget.PlatformFunctions.GetProcAddress(dacLibrary, "DAC_PAL_InitializeDLL");
        if (initAddr == IntPtr.Zero)
            initAddr = DataTarget.PlatformFunctions.GetProcAddress(dacLibrary, "PAL_InitializeDLL");

        if (initAddr != IntPtr.Zero)
        {
            IntPtr dllMain = DataTarget.PlatformFunctions.GetProcAddress(dacLibrary, "DllMain");
            DllMain main = (DllMain)Marshal.GetDelegateForFunctionPointer(dllMain, typeof(DllMain));
            int result = main(dacLibrary, 1, IntPtr.Zero);
        }

I'm hesitant to make this change without understanding why the DAC_ prefix is missing there.  I'll try to take a look at it this week if I can.

FYI we are using a dotnet runtime we built ourselves with https://github.com/dotnet/source-build. We are actually wondering if the DAC prefix is controlled by a flag during the build .

It's definitely possible that this is controlled by a build flag.  Unfortunately the person I would ask to help me track it down is out on vacation for a couple weeks.  Even still, we want ClrMD to work on these custom builds, even when you change the build flags to not do this...
Can you confirm the code snippet above does the right thing on your custom build?

Yes the snippet above is working :+1:

The DAC prefix was added recently to solve some problems when libmscoredac.so and libcoreclr.so are loaded into the same process. They both contain PAL.

See here for details: https://github.com/dotnet/coreclr/pull/18904

Ahh thank you @janvorli, so it sounds like I should use the non-DAC_ prefixed version in older builds.  Or are you saying these older builds just won't work when you load the dac into a .Net Core process?

@crntn I've pushed https://github.com/Microsoft/clrmd/commit/9d848aec96daf6abd6117286b8c86a144cc4afd6 which has that code snippet applied, for now.  I need to do some digging here later to see if everything works as intended, but for now this should be okay as a workaround.

@leculver I have to dig out an old discussion thread to refresh my memory on the issues. But IIRC, the issue was happening on Alpine Linux only (or I should say on any Linux with MUSL standard C library).

It's probably this one: https://github.com/dotnet/coreclr/pull/18873

Yes, it is the same one as I've mentioned, but this one actually got in. The other one was targeting release 2.1, but didn't get ported there if I recall it correctly.

Great thank you @janvorli!


Add cardinality aggregation.

It's already tracked in Quickwit but not in tantivy.
This is the same aggregation as the one defined in elasticsearch

I gave a quick look, unfortunately no time to implem but here are a few pointers for someone else, or future me :D
Spoilers ??????

The code should be pretty similar to the percentiles aggregation (see implem PR #1984)
PercentilesCollector -> CardinalityCollector which would hold a hyperloglog implementing add, merge and count.
hashing -> values need to be hashed in order to map them to a uniform distribution. It's possible the hll implem hashes => need to make sure the hash is computent just once
missing values -> it may be faster to simply check if we've seen a missing value and add +1 to the count rather than blindly adding the same value's hash to the hll each time we encounter one.