CPlus: Watch (buy|purchase) account

CPlus requests the watch of the watch_keyword (buy|purchase) account. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

(buy|purchase) account has been seen in 6 true positives, 0 false positives, and 0 NAAs.

Rejected by Cow in Charcoal HQ. Reason: 'Please try to optimize it better, check the comment from Makyen'


Extend minimum watch interval

Soooo... due to the scaled timeout increase, the minimum polling period of 5 seconds is repeated a number of times. This means that when running high job counts the server is hammered into oblivion straight away, and struggles to recover.
A previous change altered the max polling interval, but the result has been that the Cromwell API still dies immediately, then the watch jobs poll for status updates and receive API errors. The polling interval between errors can be increased quite a lot, but the server can take hours to return to normal function, so this has just resulted in multiple error results, spaced really far apart.
Allowing both minimum and maximum polling intervals to be set permits the jobs running to have fine grained control over frequency (for high numbers of long running jobs, not checking until ~10mins+ after submission could be rational, and would really spread the load)

Maybe we should add some randomness to spread out the requests to avoid 140 at almost exactly 10 minutes?

I've been doing a randint() range for each of the SG IDs to create some manual jitter. This first SG stage is really the only place where there would be multiple jobs polling at once, the rest are either once total, or once per sub-cohort


Example for above-ground biomass / tree cover assessment?

Has anyone has assessed the spatial autocorrelation error of Clay vs standard models in downstream prediction/fine tuning tasks?
Here's an example assessment vs Bayesian models: https://www.mdpi.com/1660-4601/18/13/6856
I'm considering generating embeddings at the patch level and using these to classify tree cover based on this tutorial:
https://clay-foundation.github.io/model/tutorial_digital_earth_pacific_patch_level.html
The tree dataset is here: https://tree-map.nycgovparks.org/
If there is a more appropriate starting point, let me know!
Use case context if it's helpful:
I've been working on health equity metrics at the neighborhood level, and think Clay could be a good fit for applying this framework: https://treesasinfrastructure.com/
To this data: https://jaanli.github.io/new-york-real-estate/
Linked to these demographics that have spatial components: https://jaanli.github.io/american-community-survey/new-york-area/income-by-race
Where every Census Bureau-defined "microdata area" is linked to health outcomes computed from claims datasets such as: https://onefact.github.io/synthetic-healthcare-data/
The hardest part here will be error analysis for looking at spatial autocorrelation of this deep model compared to conventional models like logistic regression. Moran plots are helpful debugging tools (https://connordonegan.github.io/geostan/articles/spatial-me-models.html).
(Before using downstream fine-tuning predictions for resource allocation and public health use cases, need to carefully benchmark against the byzantine Census Bureau methods/spatial lag methods/etc)

Thanks for creating this Issue @jaanli !
This sounds very interesting and please do keep us in the loop of progress.
I'd say pass on patch-level embeddings. As I explain on #223 I think them are fundamentally skewed by the context in ways that make them less valuable in most cases than chip-level embeddings.
The good news, if you wait a couple of weeks, is that Clay v1 can create embeddings at any chip size. Keep en eye for the v1 release.

I am a bit late to comment on this @jaanli . We did not assess spatial auto-correlation in any of the use cases. We did not get that deep into the downstream applications. The issue does resonate with me though, I have used spatial econometrics  in my PhD thesis.
We recently released the v1 version of the model, which works well with Sentinel-2 (10m resolution) and also NAIP data (sub-meter resolution, available for all of the US). The new version can also handle smaller input chips (with less pixels) so the patch level analysis is no longer necessary (it has strong limitations anyway as @brunosan pointed out).
Have a look at the following tutorial on how to use the new version of the model. Happy to help if you hit any roadblocks.
https://clay-foundation.github.io/model/clay-v1-wall-to-wall.html


Log is empty on iOS

GetCurrentContent returns empty string on iOS 10.
Hard to say if this is that method that is wrong, perhaps nothing is written to the file...
Log File name seems to be ok.
Of course the same code running on Android and UWP projects is ok. Only the iOS one is showing this problem.
But using the nuget package it's hard to tell more.
Do you have an idea ?

Hello,
will have a look at that, worked on my iOS emulators and devices in the past. Maybe it's something ios version dependent.
regards
Jiri

Hello,
Any news on this issue ?
I also have this problem on iOS 11 with GetAllLogsContent and GetLogContent(filename) methods. Log File Name is OK but it seems that nothing is written when calling Info(message) for example.
regard,


How to add a new cold-ammonia model?

I want to add the cold-ammonia model. The implementation of the model is simply
    dT0 = 41.18 # Energy difference between (2,2) and (1,1) in K
    trot = tkin * (1 + (tkin/dT0)*np.log(1 + 0.6*np.exp(-15.7/tkin)))**-1
    return ammonia(xarr, trot=trot, **kwargs)

I guess a new function AmmoniaRunner_cold() should be created, which looks almost the same as AmmoniaRunner_cold(). Anything else?

Hi Jaime, I've added the Swift approximation as an option in a keyword argument as AmmoniaRunner(..., cold=True). This will convert a prior sampling kinetic temperatures and convert them to rotation temperatures. The rotation temperature is only used locally, so the posterior samples will all be in kinetic as drawn from the prior.
I'm finishing up a major refactor and update, so at the exact time of this writing I still need to test that the cube fitting framework still works, but I should get to that in the next couple days. If you'd like to come back and take a look at using it, I'm just finishing up some testing and validation steps while I write-up the paper. I'd be happy to chat about it over video too, since I'm still working on documentation.


Allow mod save button from inboxes

Related to #589 and its fix d1ad5ddcf8f427ecb5c2d625a975c19076a713e5 - It appears inboxes and such were known to be excluded from this; is this by design or can I add it back in those places? I'm thinking rather than using the .moderator body class we can filter the save buttons by whether or not their thing's data-subreddit is a mod sub.
Something like this for these lines:
function addButtons () {
    var $usertextButtons = $('.commentarea>.usertext .usertext-buttons');
    $usertextButtons = $usertextButtons.filter(function () {
        return TBUtils.mySubs.indexOf($(this).closest('.thing').attr('data-subreddit')) > -1
    })

    // Add buttons to DOM...
}
TBUtils.getModSubs(addButtons)

// Click listeners...

Uh... I think they are excluded since in the inbox you can't distinguish right away. Also with how weird inboxes are on reddit there might have been some issues.

Also testing something really quick. pls ignore.

I mean, the distinguish button is still there after you comment, so unless the mutationobserver is doing something I don't understand (which is likely) it should be fine.

Feel free to poke around, but this is probably one of those areas where in a few months we have to redo the entire thing anyway.

If it lets me do what I think it will, this will be easy. If not I'll give up.  The inbox clones the reply field when you hit the "reply" button, so we can't actually make it different for each item easily. So this was intentional.


API Sample

Will there be a sample of implementing a MultiTenant API?
Specifically an example of a MultiTenant scenario where there's a tenant database for tenant lookup and a database per tenant?

Hi @CMTietgen
I'm working on more samples-- I hadn't thought of an API sample, but that is a good idea. Also I'm working on specific functionality for a database multitenant store (#26) so there will definitely will have a sample for that, hopefully soon.

@CMTietgen Hi just wanted to let you know that I added a new sample project to the Dev branch -- it shows how to implement IMultiTenantStore to look up the tenant from a SQLite database. It could easily be adapted for any other database.
I still plan to include a formal store that integrates with EFCore in the future.

Awesome, thanks. Can't wait for the EFCore sample.


PlaceOnGrid Constraint

This PR introduces a new constraint that can be used for primitives and/or subcircuits:
class PlaceOnGrid(SoftConstraint):
    direction: Literal['H', 'V']
    pitch: int
    ored_terms: List[OffsetsScalings] = Field(default_factory=lambda: [OffsetsScalings()])

A primitive generator can specify this constraint under metadata as in align/pdk/finfet/resistor.py. When present, this metadata is written to .json.
Please see the test below for a sample usage:
cd tests/pdk/finfet
pytest -v test_placement_grid.py
more run_ckt_place_on_grid/3_pnr/inputs/TFR_PRIM_L_1E06_W_1E06.json

@stevenmburns , @parijatm , fyi.

An alternative way to do this would be to append PlaceOnGrid's from primitive generator to the constraint set of the subcircuit that it is part of. We can modify the constraint definition to include a concrete_name as follows:
class PlaceOnGrid(SoftConstraint):
    concrete_name: str
    direction: Literal['H', 'V']
    pitch: int
    ored_terms: List[OffsetsScalings] = Field(default_factory=lambda: [OffsetsScalings()])

This constraint would then propagate to PnR just like other constraints. @stevenmburns , @parijatm , any thoughts?

@854768750 , please let me know if you have questions or need more info to get started on this.

@854768750 , please let me know if you have questions or need more info to get started on this.

No question. I am working on this.

@854768750 , to make faster progress, we can reduce the scope of this problem to horizontal placement grid. Please let me know.

Is TFR_PRIM_L_1E06_W_1E06.json a hard coded name? I will use this hard coded name temporarily.

@854768750
Is TFR_PRIM_L_1E06_W_1E06.json a hard coded name? I will use this hard coded name temporarily.
TFR_PRIM_L_1E06_W_1E06 is a primitive just like any other primitive in ALIGN. There should not be any name hard coding.
Does TFR_PRIM_L_1E06_W_1E06.json apply to all hierarchies?
Yes. As this is a primitive, this constraint shall be respected wherever it is instantiated.
Do I need to read TFR_PRIM_L_1E06_W_1E06.json directly? Is it passed through subcircuit.pnr.const.json?
Yes. It is preferred to keep constraint with the primitive.json.

@854768750 , thank you for doing this. I revised the test to get rid of scaling issue. This PR is ready for review.


Handle token stream in Parser

This is very far from being ready for review but @Vexu I wanted to get your feedback on the general approach before going any further, since it will be a fairly large change.
The basic idea is that a significant source of memory usage currently is that we completely preprocess the file before parsing it. With large files that means we have a lot of tokens laying around even though most don't need to be saved. For example zig2.c results in a pp.tokens.capacity of 23,031,552 after preprocessing (552,757,248 bytes in ReleaseFast, not counting expansion locations).
But, in general the only tokens we need to save are those used in decl and decl_ref tree nodes. Things like keywords, semicolons & other punctuation, literals, etc aren't needed after they're parsed. So the general idea is to have the parser pull in tokens from the preprocessor as needed, instead of doing it all up front. This is handled by having a stack of tokenizers in the preprocessor (#include pushes a new tokenizer onto the stack; finishing the file pops the tokenizer). Macros are fully expanded into an arraylist, so we don't need to store additional state in the preprocessor. Parser backtracking is handled by having "checkpoints" that prevent the preprocessor's token array from being cleared if any checkpoints are active.

The basic idea is that a significant source of memory usage currently is that we completely preprocess the file before parsing it. With large files that means we have a lot of tokens laying around even though most don't need to be saved. For example zig2.c results in a pp.tokens.capacity of 23,031,552 after preprocessing (552,757,248 bytes in ReleaseFast, not counting expansion locations).

I'm guessing you did some analysis on the memory usage, do you have any more detailed stats on it like what % of the memory usage is just tokens?
Either way this change looks to make the parser code a bit more readable with helper functions and values being used instead of fields and indexes. But that is only assuming that this results in an equivalent or faster runtime. Since the main target of Aro is modern systems using more memory for improved performance is acceptable as long as we can stay under a reasonable amount like 1GB for even the largest inputs so any performance regressions should be well justified by significant memory usage improvements.

But, in general the only tokens we need to save are those used in decl and decl_ref tree nodes.

Note that I plan to add (at least optionally) source locations to all nodes for use in translate-c and debug info generation in codegen.

I agree it's only worth doing if performance is equal to or faster than status quo - just wanted to make sure you didn't see any obvious red flags. The total RSS size of the zig2.c parse for me with ReleaseFast is 1.4 gigs. It has 7,477,094 identifier tokens, so if those are indeed the only ones that need to be saved then I think we'd save about 370 megs, plus expansion locations that take an additional 40 megs. So if all goes according to plan that would get us down near the 1GB mark.
I think preserving node source locations will be compatible with this change - would that just be another field in Node?

It looks like it would improve readability since it removes the data-oriented "abstraction" so no objections on that front.
This is compatible with the node source location thing, I was just noting that it'll increase the amount of nodes that need to be saved.

I'm going to cancel this; it ended up being really invasive and given the uncertain outcome I'm not sure I want to pursue it. I'm working on a new idea for storing fewer expansion location pointers that's much more straightforward. I have a proof of concept working for that, just need to clean it up and take some measurements.


Command center should be centered when menu is visible

Testing #150396

When using the command center on the web or windows, after a certain breakpoint the command center becomes off-centered and doesn't look great. I also notice that as you make the window smaller, the menu overflows into the ellipsis:

Suggestion
My suggestion would be to keep the command center centered (heh) and make the menu go into an ellipsis:

@misolori would you consider the logo taking the role of the hamburger button when menu is hidden? I believe this suggestion becomes more relevant with the title bar height change (https://github.com/microsoft/vscode/pull/150272), since it makes room for a bigger logo.

@safasofuoglu I don't think so, in the past we experimented with making the logo that menu and it wasn't a clear enough distinction, so we opted to introduce the compact menu option that has a menu button.

Yeah, the command center very much copies what we were doing for the static title already.. I do like the idea of the burger menu and also the idea of the ellipsis. Question is if this is a command center special case or if it should also be done for the static title?

With the static title, it made most sense to me to prioritize space for the menu since it required interaction and we were migrating from an experience where the menu was fully visible always. With both the command center and menu, I would go straight to hamburger menu as it feels like the right compromise and is much less error-prone.
After having years on the custom menu, I could be convinced that the static title could follow suit, but I suspect there would be push back.

I'd like to nominate slack title bar for spaciousness and collapsed hamburger menu.

I'd like to nominate slack title bar for spaciousness and collapsed hamburger menu.

By this way isn't it better to remove vscode icon on left?

Can we please have the "Full Menu Bar + Command Center" on 2K screens or above in maximized mode and collapse the menu bar to a hamburger only after a breakpoint?
I remember the above being the case during the experimental phase.

@manojbaishya this request was made in a separate issue and is the direction we take in the latest insiders builds

This has been addressed with a separate change motivated by performance.


Member List not working

I am using i3wm, relying heavily on the alt key.  So far as I can tell I have not assigned alt+b to anything, so there should not be any conflicts with other programs.  When I use it to try and get the member list, nothing happens.  I have tried it in several different places, including chat, server list, etc.  So far, I have gotten nothing from alt+b.

Try again with the new version on pip


JSON-powered UI for TaxBrain

The current TaxBrain interface (www.ospc.org/taxbrain) uses the standard Django Model/Form abstraction to present an interface to the user. Each parameter lives on a Django Model, and we use the built-in abstraction of a ModelForm to present the form to the user and then receive the user's input to create an instance of a Model. This is a fairly heavyweight approach, in the sense that as additional parameters are added to Tax-Calculator (or are removed from Tax-Calculator), we have to modify the Model class in TaxBrain, which involves a database migration. It further involves editing the Python file specifying the model, and the HTML temples for rendering the form.
This issue is for the discussion of a replacement of this interface. The idea would be that the entire UI could be specified in some text format (preferably JSON) and then rendered in Javascript directly from this text specification. The rendering would happen dynamically, so that a UI change would simply involve changing the text specification (which would likely live in Tax-Calculator, or perhaps some other package).
This idea seems feasible, but I haven't found a large number of libraries that do this. One option that seems to capture the requirements is Angular Formly
I'm wondering if either @zrisher or @brendancol could take a read through the documentation of Angular Formly (linked above) and give their opinion on whether you think this library would work for TaxBrain. Thanks!
cc @MattHJensen

@talumbau @MattHJensen

I would love to abstract away taxcalc usage details from the server-side code of this repo. I think it will simplify a ton of stuff and make this easier to maintain.
I'm a huge fan of Angular and think it's an excellent candidate for this type of problem.
Angular-formly looks like it has a big community, is well maintained, and aims to make specifying forms with arbitrary configuration straight forward.
I wouldn't be able to devote much time to this until Feb at the earliest. Happy to help out with architectural questions, but otherwise that may limit the usefulness of my support for this idea.

@talumbau @MattHJensen Been doing some research in javascript front end frameworks. The current best overall options seem to be Angular 2 (/4 soon) and Vue. I actually discovered Vue just going through the most popular repos on Github, but the comparison with other frameworks was a nice sell on it.
IMHO, Angular is the way to go if you're building an app that communicates with many different processes maintained by different people. That's where variable typing really shines, and I think their choice of TypeScript was heavily motivated by that core requirement.
Vue attracted me with its simplicity and speed, and I haven't been disappointed when developing with it so far. I think it would be an excellent candidate for this problem, and if it's only being used for the taxbrain page we wouldn't need its standard dependencies vue-router and vuex.
I'm available to work on this, whatever tool we decide to use, in mid Feb.

Closed via #822


Added delete command

Added delete command. Can be used to remove aircraft from the scope.
Syntax: [Select aircraft] delete
Synonyms: del, rem

I'm curious what is the intended use case for this?  It is certainly not very realistic :wink:

It's present in all the major simulators (NexSim, Adacel, UFA, etc), and I can attest there are times I've wanted it... @tedrek it's definitely not realistic, but it's important from the training perspective, as it allows you to focus on a particular task (say box pattern vectoring), and if you mess up, you have the option to kill a plane or two and continue with the drill. Useful for developing skills, and personally i would rather have the option to use or not use it based on whatever purposes I'm playing the game that day.

@erikquinn, thanks for the insight.  I'll merge once my comment on the diff is resolved.

I'll fix it when I have a chance. What do you think would be the best/most efficient way to give the option of deleting an aircraft when they are not in the center airspace?

@JHG0, the best solution is probably to wait for #601 to be merged and then implement it as a system level command which will delete regardless of being in the airspace.

Closed - new pull request will be made after merge with #601.


Issue in Quick links

Description
In Quick links, "About us" and "Projects" pages aren't opening. I want to work on this issue and fix it.
Thankyou!!
Screenshots

Additional information
No response
Do you want to work on this issue?

[X] I want to work on this issue.

fix all the broken links! THanks


feat: Liquidate command

Description
Adds CLI command for MsgLiquidate

Author Checklist
All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.
I have...

[ ] included the correct type prefix in the PR title
[ ] added appropriate labels to the PR
[ ] added ! to the type prefix if API or client breaking change
[ ] targeted the correct branch (see PR Targeting)
[ ] provided a link to the relevant issue or specification
[ ] added a changelog entry to CHANGELOG.md
[ ] included comments for documenting Go code
[ ] updated the relevant documentation or specification
[ ] reviewed "Files changed" and left comments if necessary
[ ] confirmed all CI checks have passed

Reviewers Checklist
All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.
I have...

[ ] confirmed the correct type prefix in the PR title
[ ] confirmed ! in the type prefix if API or client breaking change
[ ] confirmed all author checklist items have been addressed
[ ] reviewed state machine logic
[ ] reviewed API design and naming
[ ] reviewed documentation is accurate
[ ] reviewed tests and test coverage
[ ] manually tested (if applicable)

Codecov Report

Merging #317 (06c214c) into main (8818590) will decrease coverage by 0.11%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##             main     #317      +/-   ##
==========================================
- Coverage   32.41%   32.30%   -0.12%
==========================================
  Files          73       73
  Lines        9152     9185      +33
==========================================
  Hits         2967     2967
- Misses       5892     5925      +33
  Partials      293      293

Impacted Files
Coverage Δ

x/leverage/client/cli/tx.go
0.00% <0.00%> (ø)


Enemy artillery is being added to support module

The array which gets a list of vehicles to add just takes a list of classnames. This means if an opfor arty spawns, and it is in the arty support module list, players can call opfor artillery.

fixed in 1b49ee2ae2f712b064fcbc94ba23756a85272dd1
However, captured opfor artillery can no longer be used for support.


Changes color of settings/info popups from red to blue on settings page.

from:

to:

:+1:

:+1:


Inconsistent naming of the specs-go module

$ git grep 'specs-go"'
cmd/cdi/cmd/cdi-api.go: oci "github.com/opencontainers/runtime-spec/specs-go"
cmd/cdi/cmd/inject.go:  oci "github.com/opencontainers/runtime-spec/specs-go"
pkg/cdi/cache.go:       oci "github.com/opencontainers/runtime-spec/specs-go"
pkg/cdi/cache.go:       cdi "tags.cncf.io/container-device-interface/specs-go"
pkg/cdi/cache_test.go:  oci "github.com/opencontainers/runtime-spec/specs-go"
pkg/cdi/cache_test.go:  cdi "tags.cncf.io/container-device-interface/specs-go"
pkg/cdi/container-edits.go:     oci "github.com/opencontainers/runtime-spec/specs-go"
pkg/cdi/container-edits.go:     "tags.cncf.io/container-device-interface/specs-go"
pkg/cdi/container-edits_test.go:        oci "github.com/opencontainers/runtime-spec/specs-go"
pkg/cdi/container-edits_test.go:        cdi "tags.cncf.io/container-device-interface/specs-go"
pkg/cdi/default-cache.go:       oci "github.com/opencontainers/runtime-spec/specs-go"
pkg/cdi/default-cache_test.go:  oci "github.com/opencontainers/runtime-spec/specs-go"
pkg/cdi/device.go:      oci "github.com/opencontainers/runtime-spec/specs-go"
pkg/cdi/device.go:      cdi "tags.cncf.io/container-device-interface/specs-go"
pkg/cdi/device_test.go: cdi "tags.cncf.io/container-device-interface/specs-go"
pkg/cdi/doc.go://           oci "github.com/opencontainers/runtime-spec/specs-go"
pkg/cdi/doc.go://           oci "github.com/opencontainers/runtime-spec/specs-go"
pkg/cdi/doc.go://       "tags.cncf.io/container-device-interface/specs-go"
pkg/cdi/doc.go://       "tags.cncf.io/container-device-interface/specs-go"
pkg/cdi/oci.go: spec "github.com/opencontainers/runtime-spec/specs-go"
pkg/cdi/registry.go:    oci "github.com/opencontainers/runtime-spec/specs-go"
pkg/cdi/registry.go:    cdi "tags.cncf.io/container-device-interface/specs-go"
pkg/cdi/registry_test.go:       oci "github.com/opencontainers/runtime-spec/specs-go"
pkg/cdi/regressions_test.go:    oci "github.com/opencontainers/runtime-spec/specs-go"
pkg/cdi/spec.go:        oci "github.com/opencontainers/runtime-spec/specs-go"
pkg/cdi/spec.go:        cdi "tags.cncf.io/container-device-interface/specs-go"
pkg/cdi/spec_test.go:   cdi "tags.cncf.io/container-device-interface/specs-go"
pkg/cdi/validate/schema.go:     raw "tags.cncf.io/container-device-interface/specs-go"

I'd propose to replace all of that with unnamed import "tags.cncf.io/container-device-interface/specs-go"

/assign @klihub @elezar

Isn't that consistent naming ? I mean everywhere within pkg/cdi, we call specs-go cdi, so the spec reference reads cdi.Spec, not specs.Spec. Similarly we call opencontainers/runtime-spec/spec-go oci, so we have then oci.Spec in the code.
Anyway you need to import one of them with a renamed alias, since you can't call both of them in the same module specs. So then probably you would have specs.Spec instead of cdi.Spec and maybe oci.Spec or ocispec.Spec for the oci Spec. Personally I consider both of these less readable than the current implementation choice.

Ah ok. In pkg/container-edits.go we're inconsistent. If the current and above described reasoning is acceptable, then at least that should be changed to be consistent with the rest within pkg/cdi. And then I'd change raw to cdi in pkg/cdi/validate/schema.go as well.

Ah ok. In pkg/container-edits.go we're inconsistent... And then I'd change raw to cdi in pkg/cdi/validate/schema.go as well.

Filed #228 to fix those.

This seems to be closed by #228
/close


{} and getAll

Hey,
it would be much easier to handle programatically generated find objects if a {} would result in a getAll. At the moment this seems to be the case if you pass null to find only.
I wanted to fix the code myself but was not sure if that would break anything.
Regards,
Kim

No problem, I believe the change I just committed should perform as described.  If not you can submit pull request or describe further.
Thanks,
Dave

Alright, thanks! :)


Create Pages “about-1”

Automatically generated by Netlify CMS

👷 Deploy Preview for yff111 processing.

Name
Link

🔨 Latest commit
9ea71f709591fd1d99c20f0ce2799d5fc4d49131

🔍 Latest deploy log
https://app.netlify.com/sites/yff111/deploys/63627db688e95f00095fd2f7


App freezes when imageURL fails caused by infinite loop

Xcode 13
iOS 14+
When my model retrieves its image URL, the following code is called:
if let imageURL = model.profilePhotoURL, !imageURL.absoluteString.isEmpty {
                            AnimatedImage(url: imageURL).onFailure(perform: { error in
                                print("we got an error")
                            })

Turns out my imageURL was a little misinformed, so loading the image fails.
The issue is that the app freezes on failure. And when I print "we got an error" I can see that we are stuck in an infinite loop, as it gets called over and over. This is causing the app to freeze.
Is there a resolution?

Please attach the stack trace when your App freeze. Or any demo ?

We also see this behaviour. This is a very scary bug.

I'm experiencing this too. The app freezes and its memory usages grows forever:

This issue seems to happen when loading unreachable URLs in your library. For example, this SwiftUI code causes the issue:
@ViewBuilder var profileImage: some View {
	AnimatedImage(url: URL(string: "https://avatars.blue.ravetel.com/test.jpeg")!)
		.resizable()
		.aspectRatio(contentMode: .fill)
		.frame(maxWidth: 200, maxHeight: 200, alignment: .center)
		.clipShape(Circle())
}

SDWebImage is a really great help for my app. My team and I really appreciate your work.
That said, this is a very serious issue: apps should not freeze when their network requests fail.
An urgent fix would be very much appreciated.

Hi. This SDWebImageSwiftUI seems lag of long-time maintainess. Any contributor can help with ?
To fix this, I guess we should replace all the usage of @State which binding a Class, to use the @StateObject.
Which bump the min deployment target to iOS 14+

I recently not focus on mobile iOS UI-related development and works on Swift compiler stack related stuff. So maybe I can not manitain too many SDWebImage related project as previous. :(

I retested in SDWebImageSwiftUI version 2.2.1 and the issue appears to be fixed.


Graphical Issues with Discord Icon

I found couple issues with discord icon:

cant set bgColor to transparent (only displays as white)
discord icon masking is off and shows a circle when colors are changed

To reproduce:
Note: using twitter icon to show desired result
 <SocialIcon network='twitter' bgColor='transparent' fgColor='white'/>
 <SocialIcon network='discord' fgColor='white' bgColor='black'/>
 <SocialIcon network='discord' fgColor='white' bgColor='transparent'/>

Output in order:

I also experience this issue.

Probably have to remake the discord icon. I consider doing this tmrw

i also ran in to this when using the transparent as bgColor, fgColor works fine.

identical issue here.  Is this being looked into? thanks

hi @advra, this has been addressed in v6 of react-social-icons
CC @bonbonio @mortslhawmit @jefezebos

@couetilc great work! Thanks!


num peerps does not match max_ips

Hey @nicholaschiasson, firstly thanks for the module here.
I'm looking through the code, trying to understand the reason for this block of code below:
https://github.com/nicholaschiasson/ngx_upstream_jdomain/blob/bcf71ff90fd6acc200e3219340401b91f9b08a97/src/ngx_http_upstream_jdomain_module.c#L157-L160
What's the reason that peer pointers & max_ips have to be the same? What I'm seeing is that if an upstream server has 2 separate ports such as below:
upstream test {
  jdomain backend_1 port=1000 max_ips=2;
  jdomain backend_1 port=2000 max_ips=2;
}

Starting up nginx will trigger the num peerps does not match max_ips error message.
Changing the upstream to max_ips=1 doesn't work either, e.g.
upstream test {
  jdomain backend_1 port=1000 max_ips=1;
  jdomain backend_1 port=2000 max_ips=1;
}

will also yield the same num peerps does not match max_ips error message.
Trying to understand if this is an intended design constraint or unintended behavior. I'm happy to contribute & help out if you'd like.

Hi @zxlin,
I quickly looked into this. I have become somewhat unfamiliar with the code after a long break from this project, so I don't remember deeply the purpose for this check. There may have been more context when I wrote it. I should have written a comment or something. I suspect it was intended to just check that there were the correct number of array elements (max_ips) allocated for a given instance of the jdomain directive, otherwise assume something weird must have happened with the memory management... something unexpected in the upstream block such as an incompatible assortment of directives.
As it happens, in this case the check is actually useful in that it has revealed to us a nice bug! 😄
It appears that the case of multiple jdomain directives with the same domain but different ports is unsupported. The for loop just before this check is looking for peers for which the server name matches the instance data's server name. This should work except that in the ngx_http_upstream_jdomain function I simply assigned the server name the value of the jdomain domain argument without the port. So basically that loop will find more peers for backend_1:1000 than expected since it's only checking that the name is backend_1 and not backend_1:1000. It will increment j up to the sum of max_ips where the domain is backend_1 and then result in writing out of bounds of peerp.
To fix this, the server name simply needs to have the port (to string) concatenated. I think that should be sufficient. And for this one I think to be safe, we'll need to allocate a new string buffer for the name with a size equal to the domain length plus the port string plus 1 for :. If you'd like to help out and submit a PR, that would be super awesome! Otherwise I can try to get around to the fix soon.
Thanks for reporting this!

@nicholaschiasson I think the patch works in that it can start up fine now, but I don't think it's sending any traffic to another port of the same host. I'm testing with 2 hosts, 2 ports to each host as the upstream, only the first defined port of a host in the upstream block is receiving traffic.
e.g.
  upstream test {
    ip_hash;
    jdomain test-1 port=8080 interval=60s max_ips=2;
    jdomain test-1 port=8081 interval=60s max_ips=2;
    jdomain test-2 port=8080 interval=60s max_ips=2;
    jdomain test-2 port=8081 interval=60s max_ips=2;
  }

only test-1:8080 and test-2:8080 are receiving traffic

Hi @zxlin, could this be related to your use of ip_hash? Is this a small scale test you're conducting and is it possible due to the hashing function, we're never hitting the 8081 peers? If you're testing with a sufficient number of client IPs where that shouldn't be the case, then it's possible the module has a compatibility issue with ip_hash.

I don't think it's ip_hash, I'm testing with 100 different client IPs.
I also tested changing the domain name to include a . at the end of one of the domain names, e.g. test-1 and test-1. are both valid ways to represent the same domain name. In this test, clients are spread fairly evenly across the 4 upstreams. So it's unlikely that it's an issue with ip_hash. Config example below:
  upstream test {
    ip_hash;
    jdomain test-1 port=8080 interval=60s max_ips=2;
    jdomain test-1. port=8081 interval=60s max_ips=2;
    jdomain test-2 port=8080 interval=60s max_ips=2;
    jdomain test-2. port=8081 interval=60s max_ips=2;
  }


Blog feeds render nicely by default (XSLT stylesheet)

Have you read the Contributing Guidelines on issues?

[X] I have read the Contributing Guidelines on issues.

Motivation
It is possible to style how an XML file is rendered by browsers thanks to XML XSLT stylesheets:
https://darekkay.com/blog/rss-styling/

<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet href="/rss.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom"
      xmlns:media="http://search.yahoo.com/mrss/">
  ...
</feed>

I think it could be useful to have a beautiful XML output by default for XML-based feeds.
We could also add an icon in the blog sidebar to link to that feed, helping users know that a feed is available.

(this could become later a "blog sidebar item type", related to https://github.com/facebook/docusaurus/issues/7227)

Also, it can be the occasion to do some additional cleanup in the RSS feed item content:

Are the className attributes set by the Docusaurus theme really needed to be in the feed item content? I doubt it leads to any significant styling difference from RSS readers considering they don't have the stylesheet.
Self-service

[ ] I'd be willing to do some initial work on this proposal myself.

@slorber can I take this issue? Is there any prerequisite knowledge to taking this issue?

You can submit a PR if you think you are able to work on it. It's up to you to figure out if you have the required skills.

@slorber Give me a week to investigate on this and then get back to you

@slorber what actually you want in this issue. can you please specify. I am new to opensource by knowing more about this issue i will be able to contribute to this issue

@KirtiKamal we already have a PR for this issue that I should review soon: https://github.com/facebook/docusaurus/pull/9252
If you don't understand what the issue is about, then try to find another to contribute to. We unfortunately don't have time to help you figure it out 😅

I'd like to see an entire docusaurus site available as xml - xslt-fo could be a nice way to finally generate some good looking pdf content.


External API

What is the best way to use this with an external api eg stripe or twilio?

I assume I can do something like this and be fine:
import { Schema } from '@effect/schema'
import { pipe } from 'effect'
import { Api, Client } from 'effect-http'

const OauthTokenQuery = Schema.struct({
  grant_type: Schema.string,
  code: Schema.string,
  client_id: Schema.string,
  client_secret: Schema.string,
  redirect_uri: Schema.string,
})

const OauthTokenResponse = Schema.struct({
  access_token: Schema.string,
  token_type: Schema.literal('bearer'),
  expires_in: Schema.number,
  refresh_token: Schema.string,
  created_at: Schema.number,
  scope: Schema.array(Schema.string),
})

const pcoOauthApi = Api.apiGroup('oauth').pipe(
  Api.post('oauthToken', '/oauth/token', {
    response: OauthTokenResponse,
    request: { query: OauthTokenQuery },
  }),
)

const pcoApi = pipe(Api.api(), Api.addGroup(pcoOauthApi))

export const planningCenterClient = Client.make(pcoApi, {
  baseUrl: 'https://api.planningcenteronline.com',
})

Hey, yes. This looks exactly like it's intended to be used.

Thanks @sukovanej. I am trying to figure out how to deal with http errors.
Api.post('oauthToken', '/oauth/token', {
  response: [
    {
      status: 200,
      content: OAuthTokenResponse,
    },
    {
      status: 401,
      // content: Schema.any,
      // message: Schema.jsonSchema(
      //   Schema.struct({
      //     error: Schema.string,
      //     error_description: Schema.string,
      //   }),
      // ),
      // error: {
      //   error: Schema.string,
      //   error_description: Schema.string,
      // },
    },
  ],
  request: { query: OAuthTokenQuery },
})

Trying stuff that looks like this. I am wanting to have the error states defined out and just thrown so I can match through them and figure out what to do.

Currently, I'm not tracking errors in the Api spec. You'll need to match on the ClientError. I'm planning to add it because it'd be benefitial to document it in to OpenApi but unfortunately it's currently not in place.

Ya that would be lit. ClientError works for now. Can deal with it.


Updated tearsheet.py

Added block=False to plt.show() in order to enable automated calls from command line without having to wait for user to close the file.

Coverage remained the same at 57.143% when pulling 1bbea34ab5969ed2095c397b6a0fd473a155e754 on mindlessbrain:patch-1 into 5f8d23accaa9bf49d2106c5928979d2b24ea9520 on mhallsmoore:master.


Add Amethyst: Nostr client to apps using UnifiedPush

https://github.com/vitorpamplona/amethyst

Thanks :)

e9072e6eccfdb5b3fbe4ead96fc6f2aa0bc7afed


Map: show simple dot as marker on path

Suggestion to use simple marker instead of sailboat which clutters the image
Before:

After:

Technically, It is suppose to be a sailboat or a motorboat icon, could more options. Agreed there is too many point display, for long logs. I was thinking to display one out of two.

But it does not make sense to have multiple boats shown on the same track, it is kind of misleading. Also you want indicators where you can get the popup with more data.
I would add sailboat/powerboat in timelapse on current position. Also, we could add different sailboat sail setup for apparent wind angle: close-hauled, beam reach, broad reach, run
https://www.kavas.com/media/wysiwyg/sail_chC1.jpg
When you select particular point on the track, we could overlay the sailboat with sail setup. I think that would be cool.
I think we should/could get all the data for the track points:

course over ground
speed over ground
apparent wind angle and speed
true wind direction
true wind speed

Sorry i am confused, it should display either a sailboat or a motorboat not both as it does not make sense.
Currently, the following data is present in the geojson. More can be add.
      "properties": {
        "time": "",
        "notes": "",
        "latitude": ,
        "longitude": ,
        "speedoverground": ,
        "windspeedapparent": ,
        "courseovergroundtrue":
      }

I agree, displaying sailboat or powerboat on track does not make sense if sailing/motoring. As I already said, I would display only one boat at a time on the map - only on current location (like in timelapse), but not on each track point. I would use then different color for sailing (let say green) than motoring (let say blue) for the track between points.
Regarding geojson: it would be great if we could add these two fields:

true wind direction (TWD)
true wind speed (TWS)

That way, we could:

show sailboat on the current position with sail configuration:

no sails - motoring
close-hauled (when abs(TWD - COG) is 0 to 50 degrees)
close reach (when abs(TWD - COG) is  50-80
beam reach (when abs(TWD - COG) is  80-110
broad reach (when TWD - COG is 110-150
run - sails on oposite sides (when abs(TWD - COG) is 150-180
https://asa.com/wordpress/wp-content/uploads/2019/02/News-2019-02-11-Points-of-Sail-961x1024.jpg

show wind arrow and direction in corner/legend of the map

maybe best shown with wind barbs
or just direction triangle + windspeed in kts
https://michigan-weather-center.org/wp-content/uploads/2019/02/windbarbs.jpg

I like the concept of the dot on map instead of a sailboat or motorboat. However it should be an option in the preference.
Let discuss on how we can improve. In the meantime will close this as it conflict the latest change on the map


ISPN-13350 Use capacity-factor instead of capacity

https://issues.redhat.com/browse/ISPN-13350

I think you have to drink beers continuously until this PR is merged, @tristantarrant!

I started while coding it :)


Tuning

Hello,
In the "mainstream" moses, tuning is not presented as "optional". On the contrary, it's pretty clear that the default weights will not work properly.
I am not clear why you say it's an "optional" step in the tuto.
Also, is the devset automatically heldout at corpus preparation ? (ie I don't have to specify a devset path at tuning time ?)
Grazie mille.

Hi @vince62s
In MMT tuning is reported as optional because the default weights assigned to a newly created engine (as the last step of the "mmt create" command) are not uniform as in moses: they come from past experience on other systems.
So they are considered in some way as "reasonable" to begin...
Clearly a tuning step on domain data is expected to improve the system, sometimes a lot.
Concerning the second question, yes, default of "mmt create" is to separate two small portions on the training set as dev and test sets, so the user can issue "mmt tune" and "mmt evaluate" without any additional info.
This default behaviour can be inhibited with the option --no-split in "mmt create": in this case the full training set is used to create the engine, but the user has to provide the dev or test set with the --path option when invocating "mmt tune" or "mmt evaluate".


Could you please ask the author to upload or provide the code to generate those four JSON files in the assets folder?

Could you please ask the author to upload or provide the code to generate those four JSON files in the assets folder?

That code is here:
https://github.com/dcharatan/pixelsplat/blob/main/src/scripts/generate_evaluation_index.py


ERROR: No such service: varnish

Info:

Docker version ($ docker --version): Docker version 17.03.1-ce, build c6d412e
Laradock commit ($ git rev-parse HEAD): ac895209f0cf9f4591f0780a715ec4ada84ed2d7
System info (Mac, PC, Linux): Mac
System info disto/version:

Issue: ERROR: No such service: varnish
What seems to be going wrong?
I'm trying to setup Varnish. When I tried 'docker-compose up varnish
Expected behavior: Hoping I can setup varnish with 'docker-compose up varnish'

Hi @moiroca varnish service name is proxy or proxy2, you can search docker-compose.yml.

@bestlong Oh, I was just looking at their documentation. Thanks for this one.


Creating permissions through Tower CLI

We'd love to be able to create permissions through Tower CLI. Our playbooks to bootstrap Tower are a mix of CLI calls and API calls. Creating permissions (and other objects) is fine through the API (really liking the browseable documentation) but there are far more steps to do something idempotent in true Ansible style (lookup the permission, POST if not there, PUT if there etc vs just a tower-cli --force-if-exists).
Thanks!

"me too"

Which version of tower-cli will this be available in?
I have 2.3.1 from pip and I don't see permissions as an option

We're currently working on some not insignificant permissions changes in Tower itself...  this feature will surface in tower-cli after that.


Julia Nightly custom interpreter

@aviatesk there's some issue right now where on Julia Nightly, the interpreter seems not to be successfully applying (erring in the custom rules). The other 1.7, 1.8, 1.9 versions are fine. Did the api for inlining or something change?

The main change I'm aware of around inlining is https://github.com/JuliaLang/julia/pull/49404 but I confirmed Enzyme.jl test suite fails on https://github.com/JuliaLang/julia/commit/b27c87eb1d04f0bd001f32ffd134437007170984 (the previous commit) the same as on the latest master.


Support rendering project description from Markdown

As detailed here please update setup.py to support rendering the project description from Markdown.

I recently did this with the following commit: https://github.com/mschwager/fierce/commit/23af95f39316f2b4e810972d35ff5c84cc13703c, works like a charm. Should be easy enough to translate to this project :)

This now included.
See 59cfa99b99d87bf2cb2e9176c6dfcacafb532023 (the comma bug was later fixed).
This issue can be closed.


[Mutant Year Zero] No option to push rolls

@nodos-7 The option to push rolls is missing.

Help wanted

Closing this ticket. Advanced roller can be used for this and I added additional buttons for pushing single options in #5151  .


Lo-Fi:s

/Users/fredrikfalkman/Desktop/Screen Shot 2016-11-28 at 13.32.58.png
Shopping basket

Shopping cart

Order Confirmation

Are these all the lo-fis you need? What does the index page look like? The one with meatballs? What about the restaurant information?

This is an attempt at an mvp. The index is also the menu/add to basket page.
Would you like us to sketch out a more complete implementation?

Not unless you feel you need one. I was just asking questions to help tease
out any missing information. If what you have drawn is enough to build an
index page, then there's no problem.
Amber Wilkie
www.amberwilkie.com
07<IP_ADDRESS> | Instagram http://www.instagram.com/amberwphoto
On Tue, Nov 29, 2016 at 3:35 PM, Fredrik Falkman<EMAIL_ADDRESS>wrote:

This is an attempt at an mvp. The index is also the menu/add to basket
page.
Would you like us to sketch out a more complete implementation?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/CraftAcademy/slow_food_sinatra_nov/issues/9#issuecomment-263585960,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ATNVdG3hBUhOM2xzBMtqtmmMeTxsy-hqks5rDDgbgaJpZM4K9prV
.


odroid-c4-hardkernel.conf: Do not pin gcc versions

8.3 is gone and we are able to use gcc 10 to build this device rootfs
Signed-off-by: Khem Raj<EMAIL_ADDRESS>

Thanks.
I am a bit behind

Thanks.
I am a bit behind


Large Log File problems in Safari

I'm finding that large log files causes the RPi Cam Control web page to hang in Safari when trying to view files.
I would also like to request a change to the interface to allow us to DOWNLOAD or DELETE the log files without actually having to preview the contents in the web page.

Thanks for the update v6.2.14


Generate autocompletion for fish shell

Which issue(s) this PR fixes:

Fixes #
What type of PR is this?
/kind feature
Special notes for your reviewer:
Does this PR introduce a user-facing change? Then add your Release Note here:

Generate autocmpletion for fish shell

Documentation:

NONE

This has been implemented in #3471
/close


Images in Overview section are small and inaccurate

The overview sections shows two images - the ribbon and a floating ribbon menu. The first, ribbon, image is small and blurry.
The text above the images states "The following image shows two command interfaces (a CommandBar and a floating contextual CommandBarFlyout) that share many of the same commands." But that's not accurate. The controls called out are Xaml controls while the screenshots appear to be of Win32 controls. Neither CommandBar nor CommandBarFlyout look like what is shown in the screenshots.

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

ID: a9331458-c8a4-8936-6b4a-a58a8685cbe7
Version Independent ID: c8be4bc6-bb46-244d-402b-8cba837e65d7
Content: Commanding in Universal Windows Platform (UWP) apps - Windows UWP applications
Content Source: windows-apps-src/design/controls-and-patterns/commanding.md
Product: uwp
Technology: design
GitHub Login: @Karl-Bridge-Microsoft
Microsoft Alias: jimwalk

Thanks @YuliKl. I've replaced them with images used in the menus.md and appbars.md topics.


When loading the graph, the following node types were not found

I just started to figure out comfyui and I don't know what to do with this error

you need to check the extension installation. it's not properly installed

I've also been struggling with this isse for 4+ hourrs and using portable version on ComfyUI instead of a StabilityMatrix one helped me.
I installed insightface locally via github and used a wheel mentioned in the YouTube video from the comment below.
https://github.com/cubiq/ComfyUI_InstantID/issues/9#issuecomment-1944124506
Let me know if it helps


how to set the background image of the floating action button please?

This is a "container" of cool ui made by other users.
You should contact the developer of that specific library


web: Migrate from Zod to Valibot

The main motivation here is to work around

colinhacks/zod#1884

But also Valibot has a slightly better design and is supposedly twice as fast.
This is slightly unfinished, but I found and filed a few blocking upstream issues:

fabian-hiller/valibot#982
fabian-hiller/valibot#983
fabian-hiller/valibot#984

Feel free to contact me here, on Discord or any other platform if you have any questions about Valibot. I just finished my master's degree and will be more active from now on.


Logging in on Chrome 55 when hosting in docker returns to login page

We have been using IdentityServer 4 for quite some time.
We are getting several reports from users that try to login but after pressing 'login' the credentials get removed and nothing happens.
I reproduced this issue by opening a chrome 55 (or earlier) browser and trying to login.
What we noticed it that the redirect to the redirect_uri is being ignored and a user will be send the login page instead.
Issue / Steps to reproduce the problem
Deploy a blank IdentityServer4 to a docker enviroment
Open Chrome 55
Try to login to the identity server, you will be redirected to the login page

Sounds like a samesite cookie to me.


Add support for Linux thread names.

This PR adds support for thread names on Linux.

Implement the Linux version of Process::EnumerateThreads method.
Thread names are read from the "/proc//Task//comm" files.
Moved and modified existing util functions from ProcessUtils.h to Utils.h.
This does not catch newly created thread's name, will be a subsequent change.


feat: tera-code polish

Description
Added some polish to the code editor but would like to get your input. I thought it should be similar to how one might expect a text editor to work (e.g. new text files don't automatically save + you can explicitly overwrite or save as a new file)

Added a highlight on hover over the title. Automatically saves when you change the name. @jwaese as per this thread, the Inplace component can't really be used to add arbitrary buttons like you suggested. I still think it is unlikely that user will accidentally edit this field (and it seems equally likely that any button or field on the page may be accidentally clicked) but happy to go with whatever best practices are.
Dropdown to select language with corresponding change in syntax highlighting. Language type changes automatically based on file extension and it's added automatically if you save without a file extension.
Save new button to save as new code asset with file naming modal.
Ignore the sidebar and tab headers not updating correctly - this is an unrelated issue that will be fixed as part of a refactor.

https://github.com/DARPA-ASKEM/Terarium/assets/16358728/105a475f-4a9d-4179-ad78-795767a8b1f2

This is looking really good!
I like your solution for the rename-a-file flow. It looks really intuitive. I wish it didn't resize when focused on, which then moves the other buttons around though.
I'd like to make a tweak to the toolbar, since it's bad practice to have more than one primary button in a group.
CURRENT

Can we try something more like this?
PROPOSED

What is the expected behaviour of Save as new? From the video it looks you are just renaming the code-fragment instead of creating new code-fragment? I was expecting that you would have two code-fragments showing up in the resource-sidebar but it looks like you just replaced the existing one.

What is the expected behaviour of Save as new? From the video it looks you are just renaming the code-fragment instead of creating new code-fragment? I was expecting that you would have two code-fragments showing up in the resource-sidebar but it looks like you just replaced the existing one.

It opens in a new tab. It should also show in the resource sidebar but that's an existing bug with the sidebar not refreshing properly.

Is this ready to be merged by now? are all questions been answered.

Is this ready to be merged by now? are all questions been answered.

Ready to merge for now, we can re-open discussions when we come back to this feature.


refactor(helm): rework email configuration to use ident

:id: Reference related issue.
https://gravitee.atlassian.net/browse/DEVOPS-180
:pencil2: A description of the changes proposed in the pull request

rework email configuration in helm values.yml in smtp.email
rework also the notifiers.email

Note: previously, some properties was different between helm values and
gravitee.yml file:

starttlsEnable to starttls.enable
sslTrust to ssl.trust
sslProtocols to ssl.protocols

And on another side, the notifiers email configuration in
gravitee.yml use these camelcase properties...
This refactoring take care to be backward compatible with old and new
configuration. (see unit test)

fix also the conversion from starttlsEnable to startTLSEnabled
remove unwanted properties from smtp when include to notifiers
flatten the .smtp.properties into api.notifiers.email directly

:memo: Test scenarios
see unittest

issue: Except if I missed something, your commit changes the behaviour. Previously, it was possible to initialize the notifier part using the smtp section to avoid settings duplications. Looks like it is not the case anymore or at least there is not test case to validate this point.

Nope, this is the test which ensure notifiers configuration is well merged with smtp part: https://github.com/gravitee-io/gravitee-access-management/pull/3184/files#diff-43ca7103cf4aef604c0a1982d4f40c84d5465229ecf0570ec0e33821b22bcb53R189
And the notifiers part can overwrite smtp part 😁


Necessary to use as part of TiDB?

Some people, myself included, are keener just to use a key-value store, and build other sorts of databases on top of it, rather than using SQL. Will this ever be possible?

Yes. You can just use TiKV as a distributed key-value database.

Hi @alexreg
Now we only have a go client, you can see how to use it here https://github.com/pingcap/tidb/blob/master/benchkv/main.go

Oh right. In that case, the line in the README about needing to build and run as part of TiDB is rather misleading, I think…

On 24 Oct 2016, at 15:31, Ivan.Yang<EMAIL_ADDRESS>wrote:
Yes. You can just use TiKV as a distributed key-value database.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/pingcap/tikv/issues/1212#issuecomment-255757266, or mute the thread https://github.com/notifications/unsubscribe-auth/AAEF3L5d9jqSaB69A5ifjVtMDihIr0omks5q3MFZgaJpZM4Ke3CY.

Hi @alexreg
You can't use TiKV alone, must with PD if you only want to use it as a distributed Key-Value store. Btw, the go client now belongs to TiDB and has not been separated from TiDB.
The TiDB project contains PD, TiKV, and TiDB, and in production, now we only support using them together, have not provided an independent KV outside. So I think the README is ok now.
It is not difficult to add clients for TiKV (The RPC protocol is easy and may be more easier if we support gRPC later), so you can use TiKV + PD as a distributed KV alone, no need to depend TiDB.
It is very appreciated that you can help us do this and if you have any problem, please tell us.

Thanks for the info, @siddontang. That's fair enough. PD seems essential, though I wonder if you will be removing the dependency on etc in time? It's interesting that TiKV is written in Rust, but TiBD/PD are in Go... do you plan to make everything all Rust or all Go in time?
I'll let you know how I get on, and if there any problems I run into (and solutions), I will post them.

Hi @alexreg

though I wonder if you will be removing the dependency on etc in time
What is "the dependency on etc"?  I don't know, sorry :-)

do you plan to make everything all Rust or all Go in time?
We have no plan and will not do it later too. Go and Rust have their own advantages and shortcomings.
We use Go for TiDB and PD because we want to develop them fast, and don't care the GC problem too much. But For TiKV, we must ensure that it has a very high performance and can't be effected by GC, so we use Rust.

Hi @siddontang. Sorry, typo – I meant etcd. In the PD README file, it states "PD supports distribution and fault-tolerance by embedding etcd."
Regarding the use of Go/Rust, I quite understand. Of course, it's nice to have all technology unified under one language, but perhaps a Rust port/equivalent of PD will pop up at some point. :-)

@alexreg It's ready to use TiKV as a distributed key-value database. We just provide the raw API which can be used if you don't need transaction and MVCC. And it's fast, demo is here: https://github.com/pingcap/tidb/blob/master/cmd/benchraw/main.go#L38
Currently we have a few very simple raw API: get/put/delete/
Happy hacking.


Add missing key property on NestFields

When rendering a NestField this message appeares on console:
Warning: Each child in a list should have a unique "key" prop.
      Check the render method of 'Nest'. See https://fb.me/react-warning-keys for more information.
          in Fragment (created by Nest)
          in Nest (created by NestField)
          in NestField (created by AutoField)
          in AutoField (created by AutoFields)
          in div (created by AutoFields)
          in AutoFields (created by FormRenderer)
          in form (created by Form)
          in Form (created by AutoValidatedQuickPatternflyForm)
          in AutoValidatedQuickPatternflyForm (created by FormRenderer)
          in FormRenderer (created by WrapperComponent)
          in WrapperComponent

Looks like the key prop is missing.

Thank you for logging issue. We will address that problem in 24 hours.

Actually I see key being supplied but it might be duplicate on the field names in your schemas causing issue:
https://github.com/aerogear/uniforms-patternfly/blob/master/src/NestField.tsx#L39
I'm not at the computer right now but we have test and sample app that I will check once back from PTO tommorow

With just quick glance I cannot replicate it. it could be that key value is override by passed props.
Tests for nest fields passing.
Also nest field will have proper key.
https://github.com/aerogear/uniforms-patternfly/blob/master/src/AutoFields.tsx#L27
My take is it can be schema having duplicates or there is multiple nested fields that somehow clash (and I do not see test for it.
any more info will be good

@wtrocki I forgot to paste an example! You can try to reproduce it with this schema (https://github.com/kiegroup/kogito-apps/blob/master/ui-packages/packages/task-console/server/MockData/forms/ConfirmTravel.js).
Hoe it helps!

Oh.. yes. This really helps. I will look into this tommorow

Repeated. Fixing

Hi
I have dropped schema into the sample app and it seems to be working for me.
I have updated it for the master repository.

Master has schema so it can be checked as well in the example app.

Is there branch where I can see the actual changes.
From package.json I see that there is couple libs outdated:
https://github.com/kiegroup/kogito-apps/blob/master/ui-packages/packages/task-console/package.json#L37-L39
Dependencies we work with (kinda forced by patternfly to use latest react)
https://github.com/aerogear/uniforms-patternfly/blob/master/examples/package.json#L13-L22


Extend JLedSequence with and ability to suspend it (On/Off).

Hi,
After looking into the library code, I think I have an idea how a sequence could be suspended. This might be a quick fix, or a dirty hack, not sure - I just know I need it.
Two new methods would be created: .Off() and .On():
.Off() would allocate a new private/protected array leds_saved_, and copy the sequence's leds_ into leds_saved_. Then it would call leds_[i].Off() to turn them off. Finally, might have to call Update() once the iteration though LEDs is done?
.On() would copy the leds_saved_ array back into leds_, and free leds_saved_. Might need to call Reset() once the copy is done, too?
Unfortunately, I don't have the savviness to do this myself as I'm not familiar with the library and my C++ skills aren't up to snafu either.

Working on it in #102


Request to add support for custom claim identifiers in AzureCP other than default

My company is trying to integrate Azure AD federated authentication in its SharePoint 2019 farm. Current we use custom user identifier in on-prem AD like "EmpID". The old ADFS server will be decommissioned soon and we will transition to Azure AD federated authentication.
We have this custom property synced with the AzureAD too and currently can federate authentication using Azure AD Enterprise app without AzureCP. We plan to use AzureCP fo resolve user for better experience. But resolving user using EmpID does not work and thus setting permission via same fails.
We also have restrictions getting Application permission GroupMember.Read.All and User.Read.All in our tenant. So, is there a way we can change the application to use Delegate permissions?
Summarizing the changes we look forward to are listed below. We can also contribute if needed to bring below enhancements.

Add support for non-standard user claim identifier like EmpID.
Add support to resolve user with their additional properties like EmpID.
Add support to use delegated permission for resolving user/groups(GroupMember.Read.All and User.Read.All)

@sujeetsharma thank you for sharing your feedback.
About 3.: Dlegated permission means that a user needs to sign-in whenever AzureCP needs an access token. Since AzureCP runs in many SharePoint processes, this is impossible by design
About 1. and 2.: It is a fair request and technically possible to implement, but challenging and risky because of the risk of breaking the AzureCP configuration when updating AzureCP.wsp solution in the SharePoint farm:
The problem is that current design uses a fixed enum type as a source of user attributes list, and that would need to be changed to a list of string (that can be modified later by SharePoint admins), and it will be difficult to do this change without risking problems when updating AzureCP.

Hi @Yvand, Thanks for the quick response.
About 3- We plan to use a functional account/password to logon and not end-users account. This could help solve this.
About 1 & 2 - Can we provide the option in AzureCP config page to select default user type or custom user identifier textbox(With default selected to the fixed enum type of user attributes)?
Even if the solution is updated in future, the existing implementations will continue to have the same settings. If the SP Admins want to customize they can by coming to the AzureCP config page.

@sujeetsharma
About 3. It is by design totally impossible to use delegated permissions, AzureCP can only use application-only permissions.
About 1 & 2, it is an original design mistake which I made to use an enum type for the user attributes. The good solution is to change it completely to use a list of string. Your idea might also work, but at the cost of even more complexity and hard to maintain/understand. I keep in mind this update but I cannot promise if I will actually do it, as again it is a risky change

Today I did some investigation on this issue as we are seeing the same requirement to add custom claims to AAD.
Initial test to confirm the complexity of the solution:

I started of with extending the enumeration with the various claims (e.g. EmployeeType). I did this to see, if there are any further hurdles to take.
Solution deployment went fine and no errors were visible from central admin.

Outcome so far:

The newly added values (e.g. EmployeeType)  are not visible in the dropdown
There is a blocking check within the code. The code checks, if the properties are available within the MSGraph User/Group object.
This check causes the newly added values not being present in the configuration

https://github.com/Yvand/AzureCP/blob/243ba6d94975dba9afe3d10e537a04e1f201b3d8/AzureCP/TEMPLATE/ADMIN/AzureCP/ClaimTypesConfig.ascx.cs#L309-L317
The new value 'EmployeeType' would map to user.onPremisesExtensionAttributes.extensionattribute10 within AAD.
MSGraph user objects do have the collection of extension attributes:
//
// Summary:
//     Gets or sets on premises extension attributes. Contains extensionAttributes 1-15
//     for the user. Note that the individual extension attributes are neither selectable
//     nor filterable. For an onPremisesSyncEnabled user, the source of authority for
//     this set of properties is the on-premises and is read-only and is read-only.
//     For a cloud-only user (where onPremisesSyncEnabled is false), these properties
//     may be set during creation or update. These extension attributes are also known
//     as Exchange custom attributes 1-15. Supports $filter (eq, NOT, ge, le, in).
[JsonProperty(NullValueHandling = NullValueHandling.Ignore, PropertyName = "onPremisesExtensionAttributes", Required = Required.Default)]
public OnPremisesExtensionAttributes OnPremisesExtensionAttributes { get; set; }

Now, the challenge is to extend the UI to have a choice field/Dropdown to select extensionAttribute1-15 and to name this mapping so that it can be stored.
@Yvand and @sujeetsharma Do you have any suggestions?

Just followed up on my yesterday's findings and was looking into an easy solution. The easy solution would add the 15 extension attributes to the enumeration AzureADObjectProperty.
https://github.com/Yvand/AzureCP/blob/243ba6d94975dba9afe3d10e537a04e1f201b3d8/AzureCP/AzureCPConfig.cs#L1143-L1184
Having these attributes available here will hit the same issue as above and as a quick workaround I would implement something like that in the check in  https://github.com/Yvand/AzureCP/blob/243ba6d94975dba9afe3d10e537a04e1f201b3d8/AzureCP/TEMPLATE/ADMIN/AzureCP/ClaimTypesConfig.ascx.cs#L309-L317
 // Ensure property exists for the current object type
                if (azureObject.Value.EntityType == DirectoryObjectType.User)
                {
                    if (AzureCP.GetPropertyValue(new User(), prop.ToString()) == null && !prop.ToString().StartsWith("extensionAttribute"))
                    {
                        continue;
                    }
                }

Right now I'm struggling with where else is this information used. The enumeration values do not match the real property on the Microsoft graph user object.
e.g. extensionAttribute15 would need to mapped to userboject.OnPremisesExtensionAttributes.extensionAttribute15
Any help would be highly appreciated.

@andikrueger I need to look at this in more detail before I can give you an answer, it is on my radar and I'll come back asap

I'll push my changes to this branch: https://github.com/andikrueger/AzureCP/tree/162-custom-claims
I found an easier option to add the extensionAttributes to the dropdowns and config pages. Now looking at the usage of these extensions within queries to MSGraph - if there are any.

Just some info what I added so far:

Option to select 15 extensionAttributes by exenting the enum for AzureADObjectProperty
New AD Connect Client ID field for tenants to allow the proper construction of the extensionAttributes within the tenant
New input field to set the AD Connect client ID Field
Replace logic for creating queries with the extension attributes

At the moment, the solution is untested for the query part. The other parts are tested within the UI.

@andikrueger thank you for your work.
Can you make sure to cherry picks those 3 commits from the dev branch?
Once you think there is something ready to test, feel free to open a PR to merge on dev branch and I'll test it on my side.

171 and 172 should already be part of my branc. I’ll do some rebasing as soon as I’m confident with the changes made.
I faced one issue while upgrading the solution. I had to remove the current current configuration - I don’t know if this was something within my environment or something to expect. The stsadm command did the trick in the end.

Just pushed an additional commit to my branch with a minor change. Right now, we struggle due to #164 to verify the solution.


PWA Install Button Not Visible on iOS Devices

Description
I am using the vite-pwa/nuxt module to enable PWA functionality in my Nuxt 3 application. The install button is not visible when the app is accessed on iOS devices (iPhone and iPad), despite working as expected on other platforms (such as desktop and Android).
The issue appears to be specific to iOS and the $pwa?.showInstallPrompt method, which does not trigger the installation prompt, nor does the button appear.
I’m new to this, so I would really appreciate any help or guidance on how to resolve this issue.
Steps to Reproduce:

Implement PWA functionality using vite-pwa/nuxt in a Nuxt 3 project.
Add a button that calls the PWA installation logic using $pwa?.showInstallPrompt.
Test the app on iOS devices (iPhone or iPad) and observe that the button is not visible.

Expected Behavior:
The PWA install button should be visible on iOS devices, and clicking it should either prompt the user to install the app or provide appropriate feedback.
Actual Behavior:
The install button is not visible on iOS devices. There is no way for the user to install the PWA from the app interface.
nuxt.config.ts
const sw = process.env.SW === 'true'

// https://nuxt.com/docs/api/configuration/nuxt-config
export default defineNuxtConfig({
  modules: [
    '@nuxt/ui',
    '@nuxthub/core',
    '@nuxt/icon',
    '@vueuse/nuxt',
    '@vite-pwa/nuxt',
  ],
  experimental: { payloadExtraction: true, appManifest: true },
  ui: { global: true },

  hub: { database: true, blob: true, kv: true, remote: true },

  pwa: {
    strategies: sw ? 'injectManifest' : 'generateSW',
    registerType: 'autoUpdate',
    client: { installPrompt: true },
    manifest: {
      name: 'Schmalify',
      short_name: 'Schmalify',
      description:
        'Schmalify is a second-hand marketplace designed for students in Schmalkalden, providing a dedicated platform to buy and sell items within the local student community. Schmalify aims to simplify the trading process and foster a more efficient way for students to connect and exchange goods.',
      background_color: '#111827',
      theme_color: '#111827',
      icons: [
        { src: 'icons/icon_64x64.png', sizes: '64x64', type: 'image/png' },
        { src: 'icons/icon_144x144.png', sizes: '144x144', type: 'image/png' },
        { src: 'icons/icon_192x192.png', sizes: '192x192', type: 'image/png' },
        { src: 'icons/icon_512x512.png', sizes: '512x512', type: 'image/png' },
      ],
    },
    workbox: { globPatterns: ['**/*.{js,css,html,png,svg,ico}'] },
    injectManifest: { globPatterns: ['**/*.{js,css,html,png,svg,ico}'] },
  },
  compatibilityDate: '2024-09-12',
})

Main page (index.vue)
<template>
<ClientOnly>
        <UButton
          v-if="$pwa?.showInstallPrompt && !$pwa?.offlineReady"
          label="Install Application"
          class="mt-4"
          size="sm"
          @click="installPwa"
        />
      </ClientOnly>
</template>

<script setup lang="ts">
const nuxtApp = useNuxtApp()
const installPwa = () => {
  const pwa = nuxtApp.$pwa
  if (pwa?.showInstallPrompt) {
    pwa.install()
  } else {
    throw createError({
      statusCode: 400,
      message: 'Something went wrong installing the application, please try again later or contact support.',
    })
  }
}
</script>

You can try on your device by going to this url here scroll to the bottom and see whether it works

This is a browser issue, we cannot do anything here.

This is a browser issue, we cannot do anything here.

The button appears on chrome on all the devices except IOS. Can you walk me through the issue if possible, why does it behave like this ?

There is no button at all, the browser supporting this feature will expose the event listener, the approach in nuxt pwa is about replacing the default browser behavior.
If the browser doesn't support the beforeinstallprompt event listener, there is nothing we can do from JavaScript: https://github.com/vite-pwa/nuxt/blob/main/src/runtime/plugins/pwa.client.ts#L92-L121


Change refresh time of Traccar component

Hi all,
how i can change the refresh time for the traccar component?
Thanks

Try scan_interval: <seconds>.
Please use the issue template to provide further information .


LightGBM Earth Mover's Distance

Thanks for designing such an awesome library. I was curious if you have plans to incorporate Earth Mover's Distance into LightGBM so we can optimize over distributions.

Could you specify more precisely what you have in mind? Even computing the EMD requires solving a linear program if I'm not mistaken.

@vruvora , what's situation/scenario do you want to use Wasserstein/EMD?  considering it's normally seen in deep learning scenario.

I want to train the LightGBM to output a distribution.

Closed in favor of being in #2302. We decided to keep all feature requests in one place.
Welcome to contribute this feature! Please re-open this issue (or post a comment if you are not a topic starter) if you are actively working on implementing this feature.


Custom sorting tabs in lists show filament colour in box

Custom sorting tabs in lists, also sort filament by name type, vendor, colour, show filament colour in box, posible hide some not need tabs. It helps for search in lots of spools! :)
It would be nice if the filament color was also displayed in the lists, as it is on the octoprint.

Colour tab, please make it little bit biger and wider :)
Thank you

Sorting/filtering is now available. I will create new issues for the remaining feature requests in this issue


Option to exclude archived repo's from code search results

Feature Description

I'm not quite sure if it should actually search through archived repo's though?

It's useful but could be improved to have option to exclude them from search results. Also would be cool for archived repo results to show after normal repo results (using priority weights)
Originally posted by @lafriks in https://github.com/go-gitea/gitea/issues/17817#issuecomment-979735851
Screenshots
No response

I think maybe we need to upgrade the indexer version to support that. Some repositories' properties maybe need to store into indexer.

Another question is how the UI should look. I think we should not clutter the interface too much, so I imagine a cogwheel icon with a popup menu of options on the right side of the search bar, possibly also including the existing option for fuzzy search in there.

Perhaps another approach could be to allow repositories to opt themselves out of the indexer?
This way, by default, everything would work as it does now. But repo owners could opt out of indexing, whether the repo is archived or not, which in turn would hide them from code search results.
The added benefit of this would be that even live repos could opt out of search, which I personally would find very useful too.


[Possible Solution] WhatsApp reporting outdated Chrome version

This is the same issue thats been raised many times here. Eg: https://github.com/nativefier/nativefier/issues/1112
Using latest release of nativefier, the above problem exists even if user agent is overridden.
The troubleshooting steps mentioned in README didnt help either.
This is because user agent used by service worker is still the original one. (Ref: https://github.com/GoogleChrome/workbox/issues/2314)
According to the link above, it makes sense to use the original user agent for service workers.
But for the scope of nativefier, things are different. We can have an app level user agent.
Seems like Electron does have some option for this.
See https://github.com/electron/electron/issues/16196
https://github.com/electron/electron/issues/16196#issuecomment-591674111

We do use this to an extent (if you do not provide a user agent and don't specify the user agent honest flag. However a quick experiment with doing this for all (even injected user agents) seems promising. I'll see if we can get a release to do this soon.


Use standard process to auto-detect whether biotype entry exists in GTF file

Bypass https://github.com/nextflow-io/nextflow/issues/2060 by using a standard process with awk  rather than a native Groovy process.
Tested my branch via Tower on AWS and the pipeline is now running as expected with -profile test.

Thanks muchly @ewels ! This is a fix for a fix which has already been added to the CHANGELOG.


$ref pointing to subdirectory generates classes in wrong packages

When $ref includes a schema from different directory, referred class is generated in the package containing referring schema, e.g.:
schema/bar/a.json
{
  "$schema" : "http://json-schema.org/draft-04/schema#",
  "type" : "object",
  "properties" : {
    "refA" : {
      "$ref": "../foo/b.json"
    }
  }
}

schema/foo/b.json
{
  "$schema" : "http://json-schema.org/draft-04/schema#",
  "type" : "object",
  "properties" : {
    "propA" : {
      "type" : "string"
    }
  }
}

Both classes are generated in bar package.
I assumed that:

sourceDirectory is the default package of generated classes
directory structure along with the schemas inside will be reflected in generated packages and classes

It's mainly caused by a this block of code in SchemaRule class:
        if (schemaNode.has("$ref")) {
            schema = ruleFactory.getSchemaStore().create(schema, schemaNode.get("$ref").asText());
            schemaNode = schema.getContent();

            if (schema.isGenerated()) {
                return schema.getJavaType();
            }

            return apply(nodeName, schemaNode, generatableType, schema); // <-- see description below
        }

When generatableType is a JPackage, it points to current package instead of package of referred schema.
I have a piece of code that fixes this issue:

generates classes in proper directories when $ref points to subdirectory (at any level)
handles $ref containing #
unit tests for common and edge cases, covering 100% of added/modified code
leaves other protocols (http, java, resource, file, etc.) intact

But the questions is: Is it an bug or an improvement?
If it's an improvement, we should discuss the compliance with the spec of your plugin and handling of other protocols if needed.
If it's a bug, here's the patch fix necessary changes and tests:
https://github.com/joelittlejohn/jsonschema2pojo/compare/master...badhabit85:patch-1

@badhabit85 this seems like a long standing bug that people have been using javaType to get around.  I took a quick look at your patch and it seems strange that you have actual protocol names in there.

According to the tests I've found here plugin can use the $ref value to include schema from many different sources (e.g.: classpath, web, etc.). The patch resolves the bug for relative paths only and doesn't impact the others as I didn't know how they should be treated - for instance: should the value of 'classpath:schema/foo/bar/A.json' be resolved to 'foo.bar' package or 'schema.foo.bar'?
The protocols' names you mentioned are in the exclusion list - they're not a part of the package resolution process for 2 purposes:

don't break the contract of handling other protocols (most important)
leave the plugin open for further improvements (e.g.: handle http, classpath, resource using protocol-specific approach)
'javaType' is a workaround, but I believe that we can't workaround forever, hence the fix.

+1

I've included "support" for ids (referenced in #481), which can solve the issue. Would you take a look on it?

It works like a charm. Thank you!

Any updates on this issue ?

I've just checked it using 0.4.27. Looks fine, thank you :)

The issues may have been solved for Maven plugin in  #481, but not for others. Classes are still generated in wrong packages if using Gradle.


Error in folder naming on PNG paste

Hallo,
I wish to convert every PNG without further renaming or movement with the following settings:

On PNG paste the following Error occurs:

and the Console shows:

Looks like a clash in the folder name?

Wrong repository, this repo is for nuke-orphans plugin

Sorry

...I use your plugin as well and find it extremely useful.
Thank you very much for your work!


realm with cocoapods 1.0.0

i'm use cocoapods 1.0.0, when use
pod update
there some errors:
Installing Realm (0.102.1)
[!] /bin/bash -c
set -e
sh build.sh cocoapods-setup
when update Realm, and cocoapods exit.

Could you please try to reset your installation (rm -rf Pods), pod cache clean Realm and run pod update --verbose? If the error still persists, you would get more helpful output.
As your profile indicates that you life in china, this might be very likely another instance of what we track by #2713. You will find there some further hints.


bug: dependency on resource provider registration in virtual network module

Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

Versions

Please paste the output of terraform version command from within the initialized directory:
Terraform v1.5.7
on darwin_arm64
+ provider registry.terraform.io/azure/azapi v1.11.0
+ provider registry.terraform.io/hashicorp/azurerm v3.85.0
+ provider registry.terraform.io/hashicorp/time v0.10.0

Please enter the module version that you are using:
3.4.2

Description
Steps to Reproduce
Use this configuration and run terraform init, plan, and apply.
module "lz_vending" {
  source  = "./module"
  for_each = local.landing_zone_data_map

  location = each.value.location

  # subscription variables
  subscription_alias_enabled = true
  subscription_billing_scope = "<OMITTED>"
  subscription_display_name  = each.value.name
  subscription_alias_name    = each.value.name
  subscription_workload      = each.value.workload
  subscription_register_resource_providers_enabled = true

  network_watcher_resource_group_enabled = false

  # management group association variables
  subscription_management_group_association_enabled = true
  subscription_management_group_id                  = each.value.management_group_id

  # virtual network variables
  virtual_network_enabled = true
  virtual_networks        = each.value.virtual_networks
}

The Terraform plan shows creating the provider registrations:
module.lz_vending["lz1.json"].module.resourceproviders["Microsoft.Network"].azapi_resource_action.resource_provider_registration will be created
  + resource "azapi_resource_action" "resource_provider_registration" {
      + action      = "providers/Microsoft.Network/register"
      + id          = (known after apply)
      + method      = "POST"
      + output      = (known after apply)
      + resource_id = "/subscriptions/<omitted>"
      + type        = "Microsoft.Resources/subscriptions@2021-04-01"
      + when        = "apply"
    }

However Terraform is trying to create the virtual network in the subscription before completing provider registrations which is resulting in this problem:
│ Error: creating/updating "Resource: (ResourceId \"/subscriptions/<omitted>/resourceGroups/1-tst-net-rg/providers/Microsoft.Network/virtualNetworks/1-tst-vnet\" / Api Version \"2021-08-01\")": PUT https://management.azure.com/subscriptions/<omitted>resourceGroups/1-tst-net-rg/providers/Microsoft.Network/virtualNetworks/1-tst-vnet
│ --------------------------------------------------------------------------------
│ RESPONSE 409: 409 Conflict
│ ERROR CODE: MissingSubscriptionRegistration
│ --------------------------------------------------------------------------------
│ {
│   "error": {
│     "code": "MissingSubscriptionRegistration",
│     "message": "The subscription is not registered to use namespace 'Microsoft.Network'. See https://aka.ms/rps-not-found for how to register subscriptions.",
│     "details": [
│       {
│         "code": "MissingSubscriptionRegistration",
│         "target": "Microsoft.Network",
│         "message": "The subscription is not registered to use namespace 'Microsoft.Network'. See https://aka.ms/rps-not-found for how to register subscriptions."
│       }
│     ]
│   }
│ }

Screenshots

Additional context

I went through the dependency tree and made changes which ensure provider registration happens before trying to deploy the virtual network:
Changes
main.virtualnetwork.tf:
module "virtualnetwork" {
  source           = "./modules/virtualnetwork"
  count            = var.virtual_network_enabled ? 1 : 0
  subscription_id  = local.subscription_id
  virtual_networks = var.virtual_networks
  location         = var.location

  depends_on = [
    module.resourcegroup_networkwatcherrg,
  +  module.resourceproviders,
  ]
}

main.resourceproviders.tf:
module "resourceproviders" {
  source            = "./modules/resourceprovider"
  for_each          = { for k, v in var.subscription_register_resource_providers_and_features : k => v if var.subscription_register_resource_providers_enabled }
  resource_provider = each.key
  features          = each.value
  subscription_id   = local.subscription_id

  depends_on = [
    module.subscription
  - module.virtualnetwork,
  - module.roleassignment,
  - module.usermanagedidentity
  - module.resourcegroup
  - module.roleassignment_umi
  ]
}

Why this doesn't fully solve the problem
My goal is to be able to deploy a subscription landing zone and the resources inside of that subscription in a single Terraform apply. az_api_action (used for provider registration) doesn't have a mechanism to wait until provider registration is complete, so still the module attempts to deploy the virtual network before the Microsoft.Network provider is fully registered. Provider registration is an async API call, and azapi_update_resource doesn't seem to be able to account for this.
There is an open issue on az_api for this scenario: https://github.com/Azure/terraform-provider-azapi/issues/366
Likely could do some workaround using a provisioner or api call to work around this, but it has me questioning the approach of deploying a subscription based landing zone including resources inside of the subscription in a single terraform apply.
Questions
Is it a recommended pattern to deploy an entire landing zone (subscription with resources) in a single terraform apply?
It doesn't seem possible (today) in using this module, and it also isn't possible with azurerm due to https://github.com/hashicorp/terraform-provider-azurerm/issues/17979#issuecomment-1457783514
What is a recommended pattern? Do most customers manually deploy a subscription and then use Terraform to manage the landing zone components within?

The azure sdk for go, which azapi uses, will register providers for resources that it is deploying at the time of deployment. This is why the RP registration is left until last. It's to register any providers that are required for use later.

Thanks for the quick response Matt! I knew I must have been missing something...
Might this issue indicate that the azure go sdk is not registering the Microsoft.Network as expected upon this landing zone module making the API request to deploy a virtual network?
 Error: creating/updating "Resource: (ResourceId \"/subscriptions/<omitted>/resourceGroups/1-tst-net-rg/providers/Microsoft.Network/virtualNetworks/1-tst-vnet\" / Api Version \"2021-08-01\")": PUT https://management.azure.com/subscriptions/<omitted>resourceGroups/1-tst-net-rg/providers/Microsoft.Network/virtualNetworks/1-tst-vnet
│ --------------------------------------------------------------------------------
│ RESPONSE 409: 409 Conflict
│ ERROR CODE: MissingSubscriptionRegistration
│ --------------------------------------------------------------------------------
│ {
│   "error": {
│     "code": "MissingSubscriptionRegistration",
│     "message": "The subscription is not registered to use namespace 'Microsoft.Network'. See https://aka.ms/rps-not-found for how to register subscriptions.",
│     "details": [
│       {
│         "code": "MissingSubscriptionRegistration",
│         "target": "Microsoft.Network",
│         "message": "The subscription is not registered to use namespace 'Microsoft.Network'. See https://aka.ms/rps-not-found for how to register subscriptions."
│       }
│     ]
│   }
│ }

You can see in this file the registration process. You should be able to see log messages for provider registration.
Can you set TF_LOG_PROVIDER=trace and retry the operation?

@rybal06 Please see this comment: https://github.com/Azure/terraform-azurerm-lz-vending/issues/314#issuecomment-1906465482
Have you disabled provider registration using an environment variable?

Apologies about the delay - you are exactly correct. The env to disable azurerm provider registration is in our pipeline template as default, and I had thought initially because this module uses az_api that env var was ignored. Sorry about the inconvenience and thanks for the response!
Ultimately, we went a different direction. We had to make a decision about whether to use this repo (which relies on az_api) or to build a complex CICD process to work around azure_rm not supporting deploying a subscription with resources inside of it in a single Terraform operation and not easily supporting managing resources in multiple subscriptions without using provider blocks and aliases.
Ultimately, we decided the challenges of az_api outweighed the challenges of a complex CICD process and we have a similar solution to this repo working using azure_rm instead. We have one state file per subscription to work around needing provider aliases, and use item level targeting to deploy the subscription independently of the resources within a stage prior to managing the rest of the resources.
I want to thank the team behind this repo! We learned new Terraform tricks and concepts; and the organization very much inspired our own design. It was incredibly valuable to see how things are designed in this repo, and how you overcame certain challenges we faced.

No worries glad you worked around the issue in the end!
There is a simple workaround though,
You can explicitly set provider registration in your config for just the azapi provider - it will then only register the ones it needs.
provider "azapi" {
  skip_provider_registration = false
}


Implement Structs

Related to #71

Codecov Report
Attention: 245 lines in your changes are missing coverage. Please review.

Comparison is base (68423e9) 68.75% compared to head (936a955) 60.71%.
Report is 1 commits behind head on main.

Files
Patch %
Lines

crates/concrete_codegen_mlir/src/scope_context.rs
27.27%
136 Missing :warning:

crates/concrete_codegen_mlir/src/codegen.rs
51.21%
100 Missing :warning:

crates/concrete_driver/src/lib.rs
0.00%
5 Missing :warning:

crates/concrete_ast/src/statements.rs
33.33%
2 Missing :warning:

crates/concrete_ast/src/types.rs
71.42%
2 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #85      +/-   ##
==========================================
- Coverage   68.75%   60.71%   -8.04%
==========================================
  Files          28       29       +1
  Lines        1309     1586     +277
==========================================
+ Hits          900      963      +63
- Misses        409      623     +214

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


$ionicLoading.hide() freezes all spinners

Short description of the problem:
In the android platform (have not tried other) when the $ionicLoading.hide is called it freezes all spinners animations in view
What behavior are you expecting?
I'm using a the $ionicLoading service the first time data is required and an ionRefresher to let user refresh the data when needed. The $ionicLoading works great but when the users pull to refresh the refresher's spinner animation is freezed.
Can check an example of this behavior on this Pen
What is causing this behavior? check the stop method on the $ionicRefresher controller. The sentence anim.stop = false;, the stop member of anim is used by all animations, so if its false you get not animations at all.
Which Ionic Version? 1.x
System information:
Cordova CLI: 6.0.0
Gulp version:  CLI version 3.9.1
Gulp local:   Local version 3.9.1
Ionic Version: 1.2.4
Ionic CLI Version: 1.7.14
Ionic App Lib Version: 0.7.0
OS: Windows 8.1
Node Version: v0.12.10

Hello all! Is this still an issue with the latest version of ionic? Thanks!

Hello all! As it seems it has been a while since there was any activity on this issue i will be closing it for now. Feel free to comment if you are still running into this issue. Thanks for using Ionic!

I'm having this problem, any solutions?

I know it sounds trivial but try uninstalling and reinstalling ionic its what i did and it worked

solved it updating from 1.2.4 to 1.3.1 thanks.


When a whatsapp group is muted, Franz still show the notification

I have some muted contacts/groups, but on Franz it keeps showing the notification that I have an unread message, even though the group is set to hide notifications.
Expected Behavior
It shouldn't show the notification as the group is configured to not show.
Current Behavior
It shows the notification that I have an unread message.
Possible Solution
Check if the group is configured to hide notifications.
Steps to Reproduce (for bugs)

Log in to whatsapp
Mute a group and configure it to hide notifications
Receive a message on that group
You'll see that the notifications are shown in Franz

Context
Well, I don't want to be bothered by these groups.
Your Environment

Franz Version used: 5.0.0-beta.10
Operating System and version: Windows 10 - Build 1511

Is this the same issue? https://github.com/meetfranz/recipe-whatsapp/issues/1

Yes, I didn't know if the thread was supposed to be opened here or there, apparently all threads are being opened here...

I'm not sure, but I don't think duplicated issues is ok. What do you think @adlk ?

Oh, ok, didn't know. I'm new here, just tell me which one to delete and I'll do so.

Thats actually pretty a tough question as I personally prefer having recipe issues directly at the recipe repo. Every issue that is not directly connected with the client creates a lot of distraction. At the same time I believe we are expecting a bit much from the average user to find the right repo and post it there.
In this case here, @ms-lemos please copy your issue to the whatsapp repo as it's a pretty good explanation. Thanks!