Spiderfy all clusters at a particular view

Hi we have a certain requirement where by we would like to have all the clusters spiderfy at a particular view, once it has cross the maxzoom set.
Basically once we reach the maxzoom level, if there are 5 clusters at at that particular view, all of them should spiderfy.
Currently the default behaviour is that, when one cluster is spiderfied,  the remaining clusters get unspiderfied. How can we change this to make all the clusters spiderfied.
Even if we are clicking on a clusters, we don't want the first cluster to un - spiderfy  before the second cluster spiderfies.

Yep, same question here.  Anyone?

Leaflet.MarkerCluster only supports having one cluster spiderfied at the moment, so this would need a bit of work to support.

I am ready to take a dig at it, tell me the approach how should i start
On Thu, Mar 16, 2017 at 6:06 AM, Dave Leaver<EMAIL_ADDRESS>wrote:

Leaflet.MarkerCluster only supports having one cluster spiderfied at the
moment, so this would need a bit of work to support.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Leaflet/Leaflet.markercluster/issues/744#issuecomment-286922970,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AXjZEtaFE4nrMv0u_RPqCT5zOezNPAQ0ks5rmIP7gaJpZM4LS4I6
.

+1

Throughout the code there are references to _spiderfied, it is a member variable on MarkerClusterGroup.
I'm not 100% sure the best way to make it nicer, maybe look at changing it to an array instead, and have an option to control whether we only have a single one open or keep multiple open?

Hey, has anyone so far found a solution to the problem?
Cheers

Any update on this?

We have the same requirement as well - would like to have a way to spiderfy all the marker clusters.
I saw many requests for this - seem it is a common requirement now.
@danzel Could you please re-evaluate it? Thanks.

My two cents here, spiderify everything at a given zoom level is equivalent to replace all cluster another representation: the spider. Maybe it could be addressed by making cluster rendering customization more easy. Right now it seems to be limited to an icon but maybe a more simple way to do it is to make the spider render functions available to be used in cluster custom rendering ?

Do we have an implementation for this? I also have a requirement to spiderfy all the clusters.
Could anyone point me at a workaround if the library doesn't support it yet

Hi Team, I am also looking for the same usecase. I need to spiderify the cluster on reaching the maxzoom level without clicking it(cluster should automatically spiderify) Is there any workaround for this?. Please suggest

The solution for me was
                      if (marker.__parent._group != null) {
                        const layer = marker.__parent._group._featureGroup._layers;
                        for(let i in marker.__parent._group._featureGroup._layers) {
                          if (layer[i]._childCount != null) {
                            layer[i].spiderfy();
                            break;
                          }
                        };
                      }

@akira-kun how does your solution work? Do I have to put it in the zoom event, check the zoom and then walk through all the markers?


Error reading mzml files created by ThermoRawFileParser Version 1.3.3

As already described here, the new version of ThermoRawFileParser creates a CVTerm in its mzml files
<cvParam cvRef="MS" accession="MS:1003145" name="ThermoRawFileParser" />

which is not recognized by Proteowizard and causes an error when reading the file, for example when converting to a different format.
In case you'd appreciate support in fixing this problem I'll be happy to contribute ;)

I also wonder if it would be good practice for msconvert not to halt if it encounters a term it does not recognize at minimum in the software/processing section, since by doing that, it is a disincentive for others to "do the right thing" and register a new tool in the CV and write out the fact that it was used in the production of an mzML (or potentially other format) file.

I updated the CV last week so this file should work now. I agree it would be ideal if pwiz worked with newer CVs than it was compiled with but that would be quite tricky to implement. Easier would be to just monitor the CV and do an automatic update PR anytime there's an update. I just haven't gotten around to doing that. I am in the process of switching from Travis to GitHub actions though for some unofficial pwiz builds, so maybe I'll figure it out then.

On further consideration, auto-updating pwiz when CVs change won't fix downstream tools that use pwiz, like mzR. Seems like runtime CV updating (when necessary) is the only way.


30% Review - Enabling to use ElasticSearch as indexing/query backend

@Sanne, @hferentschik, @DavideD et al. this is the request for early feedback on the ES backend. At this point I am interested in feedback on the overall approach and strategy, so please no nit-picking about formatting, JavaDoc and the like. And yes, there are CS violations ;)
Some thoughts on the approach:

This implements an IndexManager+ LuceneWorkVisitor on the indexing side, and HSQuery on the query side
Queries are supported in form of the ES query DSL (JSON notation and the more concise, yet less powerful "query string syntax")
It uses JEST as a client, so to avoid coupling with specific ES/Lucene versions; JEST is supposedly compatible with several versions of the ES REST API
At creation time of the index manager the ES index + type mapping is created, later at run time data to be indexed is posted, adhering to the schemas created upfront
The entity id is used as ES document id (not to be mixed up with the internal Lucene document id!)
Indexing is quite featureful: proper type mapping, field boosting, embeddables etc. Querying also with paging, sorting, scrolling, projection
I aimed at altering no SPI contracts incompatbly in HSEARCH; this works so far, but it requires some nasty hacks to make things fit

Open issues and next steps:

Refine currently implemented things (e.g. "index null as", make timeouts configurable etc.)
Cover more features as far as possible: faceting, filtering, multi-tenancy etc. Some are "just" work to be done, not sure about conceptual mismatches in other cases, that needs more investigation
Re-work current IM to use a BackendQueryProcessor so one e.g. can use the combo of JMS (e.g. via a persistent queue) + ES; Currently the IM sends requests straight to ES
Investigate more performant (bulk) indexing/scrolling via suitable APIs in ES
Index sharing
Allow to pass in queries via ES query builder (making it an optional dependency, so users can add them in the right version if the want to)

Longer term tasks are:

Rework HS SPIs to make things work out better for non-Lucene backends; E.g. I create temporary Document instances atm. as that's what field bridges operate on; A more abstract representation would be useful here to avoid this kind of hacks
Generalize HS query DSL so it's not bound to Lucene queries but can emit other (ES) query representations as well
... ?

Ok, let the battle begin, or "Hashime" as they say, but be nice everyone :)

The entity id is used as ES document id (not to be mixed up with the internal Lucene document id!)

You mean our "normal Id logic applies" right? I.e. I might need to override them with @DocumentId, and we don't want to depend on JPA.

An important one: the ElasticSearch "backend" and the helpers to run queries on it should not depend on packages such as

org.hibernate:hibernate-search-orm
org.hibernate:hibernate-search-orm / testing classifier
org.hibernate:hibernate-testing
JPA interfaces
etc...

We want to be able to use that w/o requiring an Hibernate ORM/OGM or JPA application.

You mean our "normal Id logic applies" right? I.e. I might need to
override them with @DocumentId, and we don't want to depend on JPA.

Yes, exactly.

An important one: the ElasticSearch "backend" and the helpers to run
queries on it should not depend on packages such as

Good point. It should be doable by shuffling around some parts.

I wanted to play more with it but don't want to install ES at your same IP address so had some fun myself too ;-)
https://github.com/gunnarmorling/hibernate-search/pull/1

An important one: the ElasticSearch "backend" and the helpers to run queries on it should not depend on packages such as

Thinking about it, having these as test dependencies should be no problem, right? Otherwise, testing will become a bit tedious.

Thinking about it, having these as test dependencies should be no problem, right? Otherwise, testing will become a bit tedious.

+1

Thinking about it, having these as test dependencies should be no problem, right? Otherwise, testing will become a bit tedious.

Sure not a problem to have it as a test dependency if you prefer that.

I've pushed some more commits to make null tokens, class-level bridges and some things more work.
Any thoughts?

@Sanne, @hferentschik, @DavideD, ANY feedback at all? I know we all are busy, but this PR is sitting here now for almost a week and I really would like to make sure we agree on the large picture of this. Thanks!

I'm sorry, you're right. Back on it again right now..

Hi @gunnarmorling , looks like ES2 was released now: https://www.elastic.co/blog/elasticsearch-2-0-0-released
You think you could update this and get the integration tests to download/start ES automatically?
I remember sending you an experimental PR to get that done but I think you couldn't use that approach because ES was still in flux.

Hey @Sanne, ys, saw it and am about to do the update. Also will update those integration tests.
But please let's move forward with this then, this PR is sitting here since August :/ I know I didn't push for it myself either, but it's depressing how long it takes us sometimes to integrate such useful additions.

@Sanne Rebased and updated to ES 2.0. The Maven build also starts/stops an ES node before/after test execution now. If you want to use a different ES host, configure it in hibernate.properties.

I started by running the tests, and it's failing JGroupsElasticSearchTest; I assume because it has a hard-coded IP address.
But looking at it, I'm confused on the purpose of the tests as it's mixing both JGroups and ES. What's the architecture you have in mind?

@Sanne, it relates to the split of means of transport (local/JGroups/JMS) and means of indexing (Lucene/ES) I also would like to address with #896 (we should discuss that at the Paris meeting btw.)
Mixing JGroups and ES indeed is not going to be super-helpful, it's more JMS + ES which I consider as a very useful variant to address situations where a remote ES is temporarily unavailable and the indexing tasks are automatically re-sent later on by means of a persistent JMS queue. I chose the JGroups + ES mix only for testing purposes as JGroups seemed simpler to set up than JMS.
So this particular test generally shows that the ES index manager can be used with other means of transport than local. #896 seeks to further simplify that, e.g. the ES index manager class would look simpler then, but as said we could discuss that during the meeting.
I hope this clarifies things a bit?

Thanks yes that helps. And sorry, I realize you had already explained that now but I didn't remember the idea when looking at the test.
I do think your JMS+ES idea is interesting, but we need to start breaking this all down in smaller pieces.
Could we rework the separation of transport vs IndexManager at a second time?
I'm asking you as I didn't figure out yet if this a necessary step for the core of the issue "get stuff indexed in ES". If you think it's necessary then I guess we need to discuss the architecture in detail now. I'd hope this could be treated as a separate thing.
I'd hope to get a bit more practical than discuss architecture: what about we start merging some of this?
For example the first commit: I see no reason to not open a JIRA right now "Avoiding dependency to Lucene's Query type  in TimeoutManagerImpl" and send a PR for that.
Incidentally, that's a small one but I'd ask you to make the toString evaluation of the Query a lazy evaluation. Now I do suspect that you're not looking forward for that kind of detailed feedback within this large PR :) So that's why I'd break down those little blockers and try to get rid of them in break-out issues: that's the goal of 5.6, to collect all changes already which are not API breaking..
If you could extract several of those and send them as PR, then rebase this, rinse and repeat I think we should be able to integrate most of it and so have a "natural selection" of what needs to be postponed for 6?
In the meantime, I think the next steps on the "mainline work" should be to focus on the testing utilities and integration test fixtures. For example that hardcoded IP address in the JGroups test?

but we need to start breaking this all down in smaller pieces.
Could we rework the separation of transport vs IndexManager at a second time?

Really that's the case already :) There is my other PR #896 for doing this separation.
In the PR at bay nothing really has changed in this regard (which is why I had to create an ES-specific backend queue processor, which would not have been necessary with that split already in place). I've only replaced some references to DirectoryBasedIndexManager with IndexManager at places which should be agnostic of the specific implementation (BackendQueueProcessor contract).

If you could extract several of those and send them as PR, then rebase this, rinse and repeat I think we should be able to integrate most of it and so have a "natural selection" of what needs to be postponed for 6?

Ok, I can try and extract some PRs for the preparatory commits at the beginning. But also note that the entire change is meant to be acceptable for 5.6, there should be no breakages really (with the only exception being - but I will double check - the change to BackendQueueProcessor which I'd deem acceptable given it should rarely, if at all, be implemented by clients). I did not change FieldBridge etc. for exactly that reason, that's the sort of changes which should go into 6.

For example that hardcoded IP address in the JGroups test?

Ah yes, that's an oversight. There is a property for this now used in the other tests, I just forgot to remove that fixed setting from the JGroups test.

@Sanne Force-pushed an update. ES is now started/stopped for the test in the JGroups module, too. The host is configured through hibernate.properties, no need to change it normally.

Rebased to latest master and force-pushed. I am continuing now with executing the "orm" module test suite and addressing its test failures (as far as they apply to ES being used as a backend) one by one.
I keep that separate from that PR though in order to not let it grow indefinite. Let me know in case you are ready for more :)

It now passes tests on my machine! Nice progress
But it still fails on jenkins.. could you have a look at these?
http://ci.hibernate.org/view/Pull Requests/job/hibernate-search-PR/1008/

Jenkins, retest this please.

It now passes tests on my machine!

Cool, glad to hear!

But it still fails on jenkins.. could you have a look at these?

Weird. Looking into it...

@Sanne: Force-pushed an update, the module's build passes on CI now, too. There is just this intermittent test failure ScheduledCommitPolicyTest which we really should fix or disable.

now checkstyle is complaining.
Yea, about that failure there's a JIRA open for 5.6.. I haven't looked at it yet but I feel it might be a race in the test.

BTW ScheduledCommitPolicyTest never fails me locally

Ok, now it's all green on CI.

this is the request for early feedback on the ES backend. At this point I am interested in feedback on the overall approach and strategy, so please no nit-picking about formatting, JavaDoc and the like. And yes, there are CS violations ;)

Do you think I could consider it for merging at this stage?

Pushed another commit for adding some to-do markers. IMO it's good to push with that; Not yet for releasing, I'll send another PR with many improvements based on the current one.

it's merged!


Microsoft.Authorization/policy* entities 2019-09-01

Compare to iteration 1 to see diffs from the previous api-version.
Latest improvements:
MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Contribution checklist:

[x] I have reviewed the documentation for the workflow.
[x] Validation tools were run on swagger spec(s) and have all been fixed in this PR.
[x] The OpenAPI Hub was used for checking validation status and next steps.

ARM API Review Checklist

[x] Service team MUST add the "WaitForARMFeedback" label if the management plane API changes fall into one of the below categories.
adding/removing APIs.
adding/removing properties.
adding/removing API-version.
adding a new service in Azure.

Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.

[ ] If you are blocked on ARM review and want to get the PR merged urgently, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
Please follow the link to find more details on API review process.

Automation for azure-sdk-for-python

Automation for azure-sdk-for-go

Can one of the admins verify this patch?

@MyronFanQiu This is ready to merge whenever you get a chance


Create Calendar Events

Create Events That Sync To The System Calendar App On All Platforms.

Completed In Release: v1.0
Commit: https://github.com/markydoodled/Remember.it/commit/cf5c316cbdd2baed594c46c9c9bf98401d2fb2b1


[MODFQMMGR-151] Support nested object queries

Jira MODFQMMGR-151
Purpose
Allow queries on nested object properties, e.g. querying for entity type Purchase Order Lines where a fund_distribution $contains a code of ASIAHIST.
This allows queries such as:
{"fund_distribution[*]->code": {"$contains": "AFRICAHIST"}}

Approach
This is done by abstracting methods which relied on EntityTypeColumn to use the new superclass Field introduced in https://github.com/folio-org/folio-query-tool-metadata/pull/42

Idk why Sonar is mad at these...


Rails ActionController::RoutingError Not Being Reported As Default

Describe the bug
Rails ActionController::RoutingError not being reported, others look normal as expected.
Environment

Bugsnag version: 6.25.2
Ruby version: 3.2.3
Bundle version: 2.4.19
Integration framework version:

Rails: 7.0.8

Example code snippet
Bugsnag.configuration.ignore_classes
# => #<Set: {SystemExit, SignalException}>

Error messages:
# Server Logs
# ActionController::RoutingError (No route matches [GET] "/storefront/ba_tracking.js-1234567.map"

Hi @berniechiu
Thanks for your patience here.
In Rails, we capture errors as they are raised through the Rack server. If a request raises an error, we capture and notify it.
After looking into this, it appears  ActionController::RoutingError is not actually being raised through Rack. It's instead responding with the error page and not raising an error, presumably to keep the application running as it hasn't entered a failure state (which 4xx errors traditionally aren't).
We have now added a task to our backlog to look into changing this, so that these errors are able to be automatically reported. I can't currently give an ETA on when this could be implemented, but if you explicitly raise a RoutingError in the meantime, it should be caught and notified.
We'll make sure to update this thread with any developments around automatic reporting for these errors.

Thanks a lot


Only Include Certain Keys

Is there a way to not have certain keys? This seems like a really dumb question, but I haven't been able to figure out a way...simply not including it in the keys category doesn't seem to work. Is there a way to do this, like, an only_explicit_includes variable? I took a look at #222, and it seems like people have been able to this.

Use the --show flag or show option in macchina.toml, it is documented in the man page.


Fix nuclei deduplication

Description
Many nuclei templates have several matchers, such as tech-detect
If there are several matchers, each is reported as a separate finding.
The current parser puts matcher under component_name yet the hash fields do not include component_name resulting in findings being closed as duplicates when they're not (such as multiple technologies for the mentioned template)
The deduplication done within the nuclei parser itself considers matcher as key already which was not aligned with hash fields, as those didn't consider component_name.
alternative
Another option could be appending matcher to title instead of changing the hash code fields. This would allow seeing the matcher in the findings list (that does not show components) but we would lose the ability to filter by component.

@fopina this PR says there are conflicts, but idk what they are though... Pretty strange

@Maffooch I received the notification yet it's still missing approvals and I was considering just waiting for all approvals before resolving them
Yet, as I came here to comment, I also resolved them 👍  (it was the settings shasum)


Don't flag errors in class "Success"

E.g. if the operation was cancelled, that's not an error.
Fixes https://github.com/grpc-ecosystem/grpc-opentracing/issues/44

I suppose it's there so that the server doesn't mark its span as an error if the problem originated from the client.

@bboreham - Looks like there's a test case that also needs to be updated for this https://circleci.com/gh/opentracing-contrib/go-grpc/2?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link.
Could you put in a follow up PR for it?

@rnburn note I created #2 to fix the test case


IE9/10/11 webFont: 9 second load for most fonts

Error (might not be related to this issue):
CSS3117: @font-face failed cross-origin request.  but eventually they are loaded anyway.
See the page at http://foshin.com .Currently Latin-Modern is selected, but it behaves and looks about the same with all fonts that "load slowly".

Thanks for reporting. I can reproduce the issue.
The CORS headers are fine btw. Perhaps this is another case of #950 .

OK, it looks like the problem is in your configuration, where you have
		"availableFonts": ["Asana-Math"],
		"preferredFont": "Asana-Math",

The availableFonts and preferredFont tell MathJax what local fonts to look for.  The Asana-Math font is a web font (a specially modified version of Asana for use with MathJax), and won't be available on anyone's local system, so there is no use in trying to check for it.  Apparently, IE is having trouble with the attempt, and it tries waiting for it to arrive, and times out after 10 seconds when it doesn't find it.  Then it loads the Latin-Modern font.
Changing these lines to
		"availableFonts": [],
		"preferredFont": null,

prevents MathJax from attempting to loco for local fonts at all, and so you get the Latin-Modern font directly.  The solves the problem for me.  It also solves the problem with the square roots from issue #1044, which I don't understand at all.  Apparently, the attempt to load the Asana font messing up wither MathJax or IE.  I will have to look into it further, but if you change the lines above, you won't need to apply the fix for the square roots.

http://setosa.io/ev/eigenvectors-and-eigenvalues/
I am getting CORS error on this page.

@louy2 I'm afraid I'm unable to reproduce any issues on FF48 / Win10 using your page (using saucelabs to test). You might want to provide more information (but please file a new issue since this one is IE specific).

@pkra
Thanks for response. Before opening I rechecked and found that CORS is caused by HTTPS Everywhere blocking HTTP requests. It doesn't affect usage.

@louy2 glad you could figure it out. That's unfortunately outside MathJax's control.


[Menu] Truncated nested menus in FireFox

Bug, feature request, or proposal:
Bug
What is the expected behavior?
The menus width to show the whole name like it does in Chrome and the menu to show all items (non-offscreen) when a long list is given.
What is the current behavior?
In Firefox the menu names are being truncated and in FF and Chrome the menu is off the screen when a long list is used.
What are the steps to reproduce?
https://stackblitz.com/edit/angular-material2-issue-c2wnl5
What is the use-case or motivation for changing an existing behavior?
I have a place in my app where there is multiple nested menus that all have (at times) a long list of items. When that is the case in FF the menu truncates the item names and in both FF and Chrome does not show the full menu.
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Angular 5.1.0, Material 5.0.0-rc.2, Ubuntu, Typescript 2.4.2

I tried this real quick with the latest Angular Material and the latest Firefox and it doesn't seem to be an issue any longer. Free free to open a new issue if a problem persists.


Update Debian 10 & Ubuntu 20.4 point releases

Debian 10 & Ubuntu 20.04 had new point releases last month. Updating documentation to reflect this.

Thank you for the support of the project. This is your first PR, welcome to our community. I have verified your changes on the website and everything is correct.


Add link to the WAFv2 service support issue

Issue #, if available: https://github.com/awslabs/aws-sdk-rust/issues/118
Description of changes: Adds link to the WAFv2 service support issue
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Thank you!


feat: implement issuer and certificaterequest api and controllers

This PR includes all the code needed for the external issuer.

Thanks for the review, I've pushed the changes. As for the missing tests, I'll open issues with some stuff that need to be done so others can get into this code.


ARM template deployment to Management group and RBAC role

Required Information
Entering this information will route you directly to the right team and expedite traction.
Question, Bug, or Feature?
Type: Bug
?
Enter Task Name: AzureResourceManagerTemplateDeploymentV3
Environment

Server - Azure Pipelines or TFS on-premises?

If using Azure Pipelines, provide the account name, team project name, build definition name/build number: Not sure to post this information publicly.

Agent - Hosted or Private:

If using private agent, provide the OS of the machine running the agent and the agent version: Windows (Windows Server 2019 Datacenter) running agent version 2.165.0.

Issue Description
I'm trying to publish a ARM template for management groups to a management group to assign policies (I have also tried an empty ARM template). The tasks fails with an AuthorizationFailed error. The applied roles to the service principal on the management group are:

Management Group Contributor
Resource Policy Contributor
User Access Administrator

According to this (https://docs.microsoft.com/en-us/azure/governance/management-groups/overview#management-group-access) these roles combined should result in the same permissions as the owner role for the management group. Preferable I would only want to use the "Resource Policy Contributor" role for the SPN of this task.
When assigning the SPN to the owner role of the management group, the task runs succesfully.
Error logs
2020-03-10T17:05:33.2048224Z ##[section]Starting: Deploy Management Group
2020-03-10T17:05:33.2264080Z ==============================================================================
2020-03-10T17:05:33.2264490Z Task         : ARM template deployment
2020-03-10T17:05:33.2264866Z Description  : Deploy an Azure Resource Manager (ARM) template to all the deployment scopes
2020-03-10T17:05:33.2265206Z Version      : 3.1.19
2020-03-10T17:05:33.2265461Z Author       : Microsoft Corporation
2020-03-10T17:05:33.2265886Z Help         : https://docs.microsoft.com/azure/devops/pipelines/tasks/deploy/azure-resource-group-deployment
2020-03-10T17:05:33.2266346Z ==============================================================================
2020-03-10T17:05:34.5784531Z ARM Service Conection deployment scope - ManagementGroup
2020-03-10T17:05:34.6230947Z Creating deployment parameters.
2020-03-10T17:05:34.6236615Z The detected encoding for file 'E:\Agent1\48\CompanyName-arm-templates\CompanyName.json' is 'utf-8'
2020-03-10T17:05:34.6241555Z The detected encoding for file 'E:\Agent1\48\CompanyName-arm-templates\CompanyName.parameters.json' is 'utf-8'
2020-03-10T17:05:34.8123104Z Starting template validation.
2020-03-10T17:05:34.8123609Z Deployment name is ManagementGroup-CompanyName
2020-03-10T17:05:34.9936602Z ##[warning]Validation errors were found in the Azure Resource Manager template. This can potentially cause template deployment to fail. Template validation failed. Error: "The client '00000000-0000-0000-0000-000000000000' with object id '00000000-0000-0000-0000-000000000000' does not have authorization to perform action 'Microsoft.Resources/deployments/validate/action' over scope '/providers/Microsoft.Management/managementGroups/CompanyName/providers/Microsoft.Resources/deployments/ManagementGroup-CompanyName' or the scope is invalid. If access was recently granted, please refresh your credentials.".. Please follow https://docs.microsoft.com/en-us/azure/azure-resource-manager/templates/template-syntax
2020-03-10T17:05:34.9939274Z Starting Deployment.
2020-03-10T17:05:34.9939565Z Deployment name is ManagementGroup-CompanyName
2020-03-10T17:05:35.0276516Z There were errors in your deployment. Error code: AuthorizationFailed.
2020-03-10T17:05:35.0279532Z ##[error]The client '00000000-0000-0000-0000-000000000000' with object id '00000000-0000-0000-0000-000000000000' does not have authorization to perform action 'Microsoft.Resources/deployments/write' over scope '/providers/Microsoft.Management/managementGroups/CompanyName/providers/Microsoft.Resources/deployments/ManagementGroup-CompanyName' or the scope is invalid. If access was recently granted, please refresh your credentials.
2020-03-10T17:05:35.0285050Z ##[error]Please make sure the Service Principal with name AzDo-MG-CompanyName-Contributor is assigned the right roles for the entity CompanyName. Follow the link for more details: https://docs.microsoft.com/en-us/azure/role-based-access-control/role-assignments-portal
2020-03-10T17:05:35.0288603Z ##[error]Task failed while creating or updating the template deployment.
2020-03-10T17:05:35.0378689Z ##[section]Finishing: Deploy Management Group

Fixed this problem by creating a custom role with the following permissions:

Microsoft.Resources/deployments/write
Microsoft.Resources/deployments/validate/action

I optionally added the permissions:

Microsoft.Resources/deployments/whatIf/action
Microsoft.Resources/deployments/cancel/action

Assigning this new role to the SPN together with the Resource Policy Contributor role, is enough to get the pipeline deployment working for management groups.

You are correct that these roles (Management Group Contributor, Resource Policy Contributor, User Access Administrator) combined should result in the same permissions as the owner role for the management group and it holds correct but when it comes to ARM template deployment you need a write permission on 'deployment' resource which is different then permissions on Management Group resource.

I'm doing pipeline deployments to subscriptions and management groups and this extra permission was not needed for subscriptions. Why is this for management groups different?

As per this doc https://docs.microsoft.com/en-us/azure/role-based-access-control/built-in-roles#management-group-contributor,  Management Group Contributor doesn't have Microsoft.Resources/deployments/* permission.
But contributor role https://docs.microsoft.com/en-us/azure/role-based-access-control/built-in-roles#contributor, it has * permission and few not-action permission. Thus you are able to run over subscriptions w/o giving Microsoft.Resources/deployments/* permission .


Fix sitemap URL

If the blog is installed in a subdirectory, /sitemap.xml will not include the subdirectory.

Thanks!


Add etherswap.org

They're attempting to phish/scam via slackbot reminder. Screenshot taken on slack mobile:
https://s11.postimg.org/t4sql3mur/Screenshot_2017-07-27-00-32-56-215_com.Slack.png

Site is a mirror of Ethereum.org at time of writing.
<!DOCTYPE html><html>
--
  | <!-- Mirrored from ethereum.org/ by HTTrack Website Copier/3.x [XR&CO'2014], Thu, 20 Jul 2017 11:16:00 GMT -->
  | <!-- Added by HTTrack --><meta http-equiv="content-type" content="text/html;charset=utf-8" /><!-- /Added by HTTrack -->

Thanks @nulldash !


Convert clinics.coffee to clinics.js

I rule and have completed some work on Case Manager that's ready for review!
Converted clinics.coffee to clinics.js
This pull request makes the following changes:

Convert the coffeescript to JS
Move the new JS into the packs directory and import it into the application pack
Add the document to the list of globals known by ESLint (fixes linting issues around things like $(document).ready

It relates to the following issue #s:

Fixes #1681

@colinxfleming: I fixed that dropdown and I pruned some code that looks like it wasn't used anymore.


Add route53 alias target support for records

This will allow to simply assign an ELB id to a type A record for example.

Duplicate of #814


bash: update patches

Motivation for this change
Apply latest fixes to Bash 5.1. Especially 009, fixing a bug in its malloc implementation.
I've merged against master because those are fixes, but feel free to argue that it should be against staging.
Things done

[X] Run pkgs/shells/bash/update-patch-set.sh bash 4.4 --> nothing new
[X] Run pkgs/shells/bash/update-patch-set.sh bash 5.1

Built on platform(s)

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

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

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

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

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

[X] Fits CONTRIBUTING.md.

test failure is as follow:
error: unable to download 'https://ftpmirror.gnu.org/bash/bash-5.1-patches/bash51-012': HTTP error 404
I can confirm I have the same error, ftpmirror around the world are probably just not updated yet? it finds up to 008 just fine.

I agree with merging to master, since we are cutting it close to the 21.11 release though, let me see what the release managers have to say about it.
I've just checked and I don't get the 404 anymore, perhaps force push the branch to retrigger the build ?

I can confirm I have the same error, ftpmirror around the world are probably just not updated yet? it finds up to 008 just fine.

I think that's the case, 012 seems to be resolved without any issue on my end now.
@GrahamcOfBorg eval

Surely not directly to master, as it rebuilds completely everything.  staging-next is conceivable at this moment (and gets to 21.11 automatically), but I think that's worth it only if the fix is very urgent... and I don't see that indicated.  Otherwise I'd expect staging and then a bit later backport to 21.11.

@vcunat, my motivation for 009 was to be able to use DynamicUser= in some NixOS services without workaround as this one for syncoid:
BindReadOnlyPaths = [ builtins.storeDir "/etc" "/run" "/bin/sh"
  # A custom LD_LIBRARY_PATH is needed to access in `getent passwd`
  # the systemd's entry about the DynamicUser=,
  # so that ssh won't fail with: "No user exists for uid $UID".
  #
  # Unfortunately, Bash 5.1 is incompatible with libnss_systemd.so:
  #<EMAIL_ADDRESS>  # Hence we cannot just directly put this custom LD_LIBRARY_PATH
  # in the service's environment as one would expect
  # but have to use a workaround: wrapping ssh.
  # This wrapping is done here as a mounted path because
  # because Nixpkgs' wrapping of syncoid enforces the use
  # of the ${pkgs.openssh}/bin/ssh path.
  # This problem does not arise on NixOS systems where stdenv.hostPlatform.libc == "musl",
  # because then Bash is built with --without-bash-malloc
  # This problem will be fixed once https://ftp.gnu.org/gnu/bash/bash-5.1-patches/bash51-009
  # has been applied to Bash.
  ("${pkgs.writeShellScript "ssh-with-support-for-DynamicUser" ''
    export LD_LIBRARY_PATH="${config.system.nssModules.path}"
    exec -a ${pkgs.openssh}/bin/ssh /bin/ssh "$@"
  ''}:${pkgs.openssh}/bin/ssh")

  "${pkgs.openssh}/bin/ssh:/bin/ssh"
];

So at least there is a workaround in this case, but knowing that this bug allows to "overwrite memory bounds checking" it sounds like it may be exploitable, though I don't have any proof of concept to back that up. Therefore I would prefer to have those patches included as soon as possible. To this end I'm rebasing against staging-next as you suggested.

Please rebase on staging. We really need the current staging-next cycle to be able to be merged by tomorrow or saturday. This will essentially be another 3-5 day push back on that window.

About merging this to master with the rebuild amount: this would only be possible if it would include a very high severity CV or bug that needs to be patched asap and is or likely is to be exploited in the wild with very high damage. For example if something gets a CVE of 10.0 we could justify it. This can of course be expanded and if there is a good argument Something can be always merged to master which I don't see here.

@jonringer, I've rebased on staging as you requested.

@ofborg eval

tests seem to have failed on a subtest of git 2.34
t2200-add-update.sh ................................ Dubious, test returned 1 (wstat 256, 0x100)
https://github.com/git/git/blob/master/t/t2200-add-update.sh
I can't really see anything in that test that seems bash specific. I'm going to try to do the eval again just to see if it is a flaky test.

@GrahamcOfBorg eval

re-evaluation doesn't trigger a full eval.
Should we still try to merge on staging and potentially disable the flaky test there ?

tests seem to have failed on a subtest of git 2.34 t2200-add-update.sh ................................ Dubious, test returned 1 (wstat 256, 0x100) https://github.com/git/git/blob/master/t/t2200-add-update.sh I can't really see anything in that test that seems bash specific. I'm going to try to do the eval again just to see if it is a flaky test.

I was able to get it passing locally with --cores 1

So are you ok to merge as is, or would you prefer we "enableParallelBuild = false;" ?

Succeeds for me with 32 cores.  I retried a couple times.  Jon's using some extreme machine, I suspect.

Ok then let's consider this test flaky and think about disabling it potentially if this is still a problem in staging-next.

Succeeds for me with 32 cores. I retried a couple times. Jon's using some extreme machine, I suspect.

128 cores IIRC


MM-28290 Always update team member unread counts when added to a channel

When fixing https://mattermost.atlassian.net/browse/MM-26730, I made it so that markChannelAsUnread isn't dispatched when you're first added to a channel because the ChannelMember object has already been updated with the correct unread counts by that point. Doing that broke the unread count on the TeamMember object though, so instead, we need to dispatch markChannelAsUnread, but we need to make sure it only updates the TeamMember in that case.
I did some renaming since I keep coming across this file when looking for utils/post_utils, so the important changes are in https://github.com/mattermost/mattermost-webapp/commit/3c8b13fae50c5bb27b03b2fde2d6ec031ae5d206 and in the redux PR.
Ticket Link
https://mattermost.atlassian.net/browse/MM-28290
Related Pull Requests
https://github.com/mattermost/mattermost-redux/pull/1240

The failing unit tests are caused by the changes I made to the previous fix. I'll update those shortly.

When this PR is cherry-picked onto the release branch, mattermost-redux should be set to 50813febcf5ff7bb60f71dcdf53e573aed3f9b55

Cherry pick is scheduled.

Error trying doing the automated Cherry picking. Please do this manually
+++ Updating remotes...
Fetching upstream
Failed to add the RSA host key for IP address '<IP_ADDRESS>' to the list of known hosts (/app/.ssh/known_hosts).
From github.com:mattermost/mattermost-webapp
 * [new branch]          MM-28151   -> upstream/MM-28151
   68126d8f3..e665a3f42  MM-28706-fix-autosuggest-ordering-again -> upstream/MM-28706-fix-autosuggest-ordering-again
   fcbadbde1..49e9c752a  MM-28839   -> upstream/MM-28839
   88511bfe6..fae9096c2  master     -> upstream/master
Fetching origin
Failed to add the RSA host key for IP address '<IP_ADDRESS>' to the list of known hosts (/app/.ssh/known_hosts).
+++ Updating remotes done...
+++ Creating local branch automated-cherry-pick-of-mattermost-webapp-#6500-upstream-release-5.28-1600874575
Switched to a new branch 'automated-cherry-pick-of-mattermost-webapp-#6500-upstream-release-5.28-1600874575'
Branch 'automated-cherry-pick-of-mattermost-webapp-#6500-upstream-release-5.28-1600874575' set up to track remote branch 'release-5.28' from 'upstream'.

+++ About to attempt cherry pick of PR #6500 with merge commit fae9096c2d5f709f73177cbc29e9801148cd28e8.

error: could not apply fae9096c2... MM-28290 Always update team member unread counts when added to a channel (#6500)
hint: after resolving the conflicts, mark the corrected paths
hint: with 'git add <paths>' or 'git rm <paths>'
hint: and commit the result with 'git commit'

+++ Conflicts detected:

UU package-lock.json
UU package.json
Aborting.

+++ Aborting in-progress git cherry-pick.

+++ Returning you to the master branch and cleaning up.


Add scope methods to Rails/FindEach cop

Makes the cop check for the following scopes: includes, joins, left_outer_joins, and unscoped.
I can add a changelog entry if this looks good.

@koic should be good now

Thank you!


Let URL getters accept a filter instead of query parameters

Since these functions are exposed, they are much more useful if they accept a filter, similar to the fetch methods.

Test failure flagged here is unrelated, and fixed in #52.


Ensure systemctl is up and running (handle WSL ubuntu)

This would cover all the windows ubuntu linuxes


Make library iOS 8 compatible

added to TODO projects

What's the status of iOS 8 support?

unfortunately, i do not think this will be done.
someone will have to make a pull request. this project alone has gotten very time intensive.

hey, is easy to do, but im just so very very busy right now.
install the library on your project, and then do a search in the library files for this text:
semanticContentAttribute

You should see it appearing 6 times in the library.
Just delete it. and you should be good.
If someone can create a pull request to add the @availailable 9.0 tags to the code, i will gladly accept it.

ios8 will now be supported again.


[FEAT REQ.] - Program Name Change

NASR2SCT was good at first but it does much more and is planned to do even more in the future. Now is the time for a name change prior to v1.0.

"Facility Buddy"
-Credit to Chris James

Or... "FE Buddy"


Review alternate initial offset provider for bootstrapping EventProcessor

In track 1 library, Event Processor Host (EPH) used an offset provider to bootstrap an application for the first time. When an EPH starts up and claims ownership of a partition, it needs to determine the position (sequence number/offset) to start processing events from. If a checkpoint is available, the EPH will start processing the events from the checkpointed sequence number. If it's not available (i.e the application has never used EPH before or the storage is new/migrated and all checkpoints are lost), then EPH will fallback to using user provided implementation of an offset provider that has the ability to return a sequence number to start processing from for a given partition id.
Given that the offset provider is used occasionally and increases the complexity of EPH interface and implementation, in Track 2 library, the offset provider can be deprecated and Event Processor (EPH equivalent in Track 2) can be simplified. If/when applications want to provide a custom checkpoint for new Event Processor, they can follow the steps below to achieve the purpose offset provider served in Track 1.
https://gist.github.com/srnagar/714b0064668b4d1d3520fcc52e5879c6

Addressed in latest design to use initialization handler to provide custom initial position.


single client with futures api

Changes api to a single client which returns Streams and Futures on subscribe and publish respectively.

I'll defer to @Xaeroxe's request for changes before approving, but otherwise LGTM...assuming you've got your C contract right. Want me to review that?
EDIT: And I hit "Approve" by accident. Heh.

The C contract is going to be the area where I will be weakest.  I'm happy for a review of that.

It looks like an audit of C code will take a while -- it looks like client code is responsible for the lifetimes of provided strings to most of the c-core API. Eep! Let's do this: I'll create a separate issue for this and we'll get to it...sometime.


Initialised Swift Package Manager with Alamofire dependency for inter…

Initialised Swift Package Manager with Alamofire dependency for internal dependency management

@akanksharma  A small conflict has crept in, check it out


Adding More than 4 Sub Accounts Doesn't Save

Description
When adding a fifth account to the Command Center, I am able to add/save it initially and rearrange the accounts.  However, after leaving CC and coming back, it has reverted to a prior save and I can only see the 4 accounts previously working.
Steps to Reproduce
Add new 5th account from configuration
Save the file
Close browser and return
Expected Behaviour
Five accounts to be available after returning.

If you open browser dev tools and look at the console logs, are there any errors? Either upon saving the 5th account or upon initial load/refresh?

On save:
Saving data in 1 60k chunks index.js:70 Error: GraphQL error: Service Exception: NerdStore.API.Error Server Error (307)     at new e (wanda--wanda-ec-ui--app-release-1358-prod.js:1)     at Object.next (wanda--wanda-ec-ui--app-release-1358-prod.js:1)     at g (wanda--wanda-ec-ui--app-release-1358-prod.js:1)     at b (wanda--wanda-ec-ui--app-release-1358-prod.js:1)     at t.value (wanda--wanda-ec-ui--app-release-1358-prod.js:1)     at wanda--wanda-ec-ui--app-release-1358-prod.js:1     at Set.forEach (<anonymous>)     at Object.next (wanda--wanda-ec-ui--app-release-1358-prod.js:1)     at g (wanda--wanda-ec-ui--app-release-1358-prod.js:1)     at b (wanda--wanda-ec-ui--app-release-1358-prod.js:1) index.js:81 Error: GraphQL error: Service Exception: NerdStore.API.Error Server Error (307)     at new e (wanda--wanda-ec-ui--app-release-1358-prod.js:1)     at Object.next (wanda--wanda-ec-ui--app-release-1358-prod.js:1)     at g (wanda--wanda-ec-ui--app-release-1358-prod.js:1)     at b (wanda--wanda-ec-ui--app-release-1358-prod.js:1)     at t.value (wanda--wanda-ec-ui--app-release-1358-prod.js:1)     at wanda--wanda-ec-ui--app-release-1358-prod.js:1     at Set.forEach (<anonymous>)     at Object.next (wanda--wanda-ec-ui--app-release-1358-prod.js:1)     at g (wanda--wanda-ec-ui--app-release-1358-prod.js:1)     at b (wanda--wanda-ec-ui--app-release-1358-prod.js:1)

When I return to the page after that, I get the following:
ad5c82d8-f070-4824-823d-5146bf468d55--nr1-command-center-nerdlet.js:1 Uncaught (in promise) TypeError: undefined is not iterable (cannot read property Symbol(Symbol.iterator))
at W (ad5c82d8-f070-4824-823d-5146bf468d55--nr1-command-center-nerdlet.js:1)
at I. (ad5c82d8-f070-4824-823d-5146bf468d55--nr1-command-center-nerdlet.js:1)
at d (runtime.js:45)
at Generator._invoke (runtime.js:274)
at Generator.forEach.e. [as next] (runtime.js:97)
at r (asyncToGenerator.js:3)
at o (asyncToGenerator.js:25)
at asyncToGenerator.js:32
at new Promise ()
at I. (asyncToGenerator.js:21)
And I have NO configuration

Thanks @tdavis13 ! The TypeError: undefined is expected. It looks like the culprit is the first error posted:
index.js:70 Error: GraphQL error: Service Exception: NerdStore.API.Error Server Error (307)
Can you also send me the User-Agent header your browser is sending? You should be able to find it by navigating to:
https://www.whatismybrowser.com/detect/what-is-my-user-agent

Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/84.0.4147.105 Safari/537.36 Edg/84.0.522.52

Thanks! I'm not able to replicate this on my own Edge 84 / Win10 machine, which makes me think there may be some unique browser security settings that may be causing the 307 redirect. To better troubleshoot this, can you shoot me an email at<EMAIL_ADDRESS>with a HAR file? I think inspecting the requests/responses of the GraphQL calls will provide more detail to fix this issue.
To generate a HAR file in Edge: https://support.zendesk.com/hc/en-us/articles/204410413-Generating-a-HAR-file-for-troubleshooting#Edge
Please make sure you add a few accounts via Configuration and click Save before exporting the HAR file.

It appears this may be related to a specific account.  I can't even add the account as a '4th' account at this point and have it truly save.

Is it possible to shoot over via email the account name and ID you are trying to add?


textbox element

[ ] has placeholder text of different color from normal text

this will be autosquashed the same way we do with window element (when that is done...)

[ ] has text
[ ] has ability to fire a changed event if you define that function, will be passed oldtext and newtext
[ ] box background, which is the text area
[ ] no outline, or extra outside styling, very minimal

See #1 for this being worked on


We need some error handling m8 xd

Tried to create a new user with the same username. I think that it will be better with some sort of error code or something so id does not crash the server xd.

The error in described in the screen you provided is telling you that there is already a user with the specified username.

Feature Request / TODO
Easier error handling for row operations
Eg: Creating users, posts, etc...
Suggested implementation: Middle man API between sequelize and routes.js

@HyScript7 how do i get list of all emails? so i can email to them?

select email from users;
Or just fetch all users and get the email property if you're like me and can't figure out where to run raw SQL.

Hell naw 😂😂😂

Well, this is all still broken. I can't really work on it right now, but here's how I'll attempt to fix this:
In the helper, whenever a row is created, we immediately attempt to fetch that row. If we fail, we clearly didn't create it.
I will also split the mail list into their own table. Users will have a nullable foreign key pointing to the mail table.


No License

This repository has no license. Am I allowed to relicense it to some FOSS license GPL/BSD (I don't really care) to fork it and base some other functionality on it?

I'm not super familiar with my options. I see MIT a lot so I'll probably go with that. Any concerns?

I think GPL and MIT/BSD are the most common ones. The main difference is that the GPL is viral in a sense that all derived works also need to be licensed under GPL, while MIT/BSD allows everybody to keep derived works proprietary.

Fixed.


Dynamically change sticky header

In my app I dynamically change two TextView with numbers in sticky header by clicking overflow menu (in screenshot). Then I insert a number with length more then 1, and TextView don't display the whole number. Is there another way to fix it? without setting new adapter and StickyLayoutManager, because this way refreshing the whole RecyclerView, and I don't need it :)
TextView has layout_width="wrap_content" parameter
(Sorry for bad language)

However, one of the simplest process to add sticky header :) great work!

So the TextView content is being cut off?

yes, it is

Sorry for the delay, this is still something I will look into but I've been pretty busy lately.

Could you please see if this is still an issue in 0.4.8?
Also, is the TextView of your header set to match_parent for width?

Make that 0.4.9. I was able to periodically reproduce what I think your issue is, but it's fixed now (I'm forcing a layout of the Sticky Header view when re-bound).


Update README.md

Add Inyector

Inyector - Dependency Injection Automation for

Add Inyector library (tool used for automation IOC for asp.net core engine)

Sorry, @davidrevoledo ,
This entry isn't going to make the list for the following reason(s):

Possibly too new
Possibly too small
No of response from the community suggested the previous statements were false

Don't let this setback cause you to lose heart, and we look forward to your next contribution.
Thanks, Pleb

I'm disagree with those statement

possibly too small is something irrelevant the idea of the tool is auto inyect dependencies not a framework for a lot of things.

It'd be good to at least put new frameworks to give them the possibility to be populars

But I respect your considerations :)
Kind Regards,


[feature] Request missing collection items from Jellyseerr

I would love to see a feature added where missing items from a collection can be passed as requests to Jellyseerr!
An intermediary feature request that would also be helpful would be to log missing collection items to a text file.

Have added some basic support for this now. Try adding this to your config:
jellyfin:
  ...
jellyseerr:
  server_url: https://jellyseerr.example.com
  api_key: AAaaAAAaAAA0AaAaAaaaa...
...
plugins:
  ....

Let me know if there are any problems.

Good afternoon. Tell me, the new jellyseerr feature will make requests from which user? If it is from the administrator, then this is bad, because the administrator may have the option to automatically accept the request.
But I would like to see and confirm before the script adds 10 or 100 movies to my collection.

Yes you're right it was authenticating as admin which auto-accepts all the requests. I've added the option to authenticate as any user now:
jellyseerr:
  server_url: https://jellyseerr.example.com
  email<EMAIL_ADDRESS>  password: mypassword
  user_type: local

Might be worth making a seperate local user just for this script so you can seperate the requests.


Change color of selected item

Hello
Is it possible to change the color of the highlighted current item in the left pane ?- the very light blue is quite difficult to see
thank you
Andrew

@barney2074 this possible only if you rebuild data manager and modify this color there.
It's here: https://github.com/heartexlabs/dm2/blob/0f704d7c7a8ab5182fe7cd957c07bf8425c802a3/src/components/Common/Table/Table.styl#L62


PR to fix #2.

This is already declared as a bin in js-yaml's package file, npm@3 kills the assumption that this file will be present in this location when installing yaml-front-matter and this therefore stops the project from being built if js-yaml has already been installed.

Thanks for the PR. I published a new version with the updated package file which has resolved issue #2.


Default flags when fetching all flags

Hi @dabeeeenster ,
We have just noticed that when we use getFeatureFlags(*) and identifyUserWithTraits(user, traits), we get the raw values directly from Flagsmith, so no default values are used (which are very important to us). This is specially problematic in the scenario where we use a proxy to secure the Flagsmith endpoints (Flagsmith -> BFF (just forwards flags as received) -> frontend).
Since this is something that everyone should do (have sane defaults), we would like to extend the SDK with the following logic:

Analog to setDefaultFlagPredicate and setDefaultFlagValueFunction, we would like to have a setDefaultFlags method.
setDefaultFlags would accept an array of strings (feature flag names).
If there is an error when fetching flags from the API, we then create default flags (if the string array was set) with the default values set above.
If there is no error, but the flag was not received from Flagsmith, we can insert it with default values. I thought you may have a stronger opinion on this point, so we can always add further configuration for this behaviour if required.

This is the behaviour we would like but you guys know best how your API is consumed. Any thoughts?
Cheers,
Olga

Hi.
Thanks - this sounds generally like a good idea, yes. We're just trying to consider what the best way of setting these defaults might be. Given that flags are now a combination of booleans and string values, what about something like:
FlagsmithClient flagsmithClient = FlagsmithClient.newBuilder()
                .setApiKey("YOUR_ENV_API_KEY")
                .build();

flagsmithClient.setDefaultFlagState("show_chat_widget", true, null);
flagsmithClient.setDefaultFlagState("checkout_button", true, "green");
...

Hi @dabeeeenster
We also considered that option to start with, but then decided that instead of passing static values true, null, we could pass lambda functions like we do for setDefaultFlagPredicate and setDefaultFlagValueFunction. This way the default values can be dynamics depending on whatever logic the developer has (which would still be static).
What do you think?

Hi @matthewelwell
Those methods are only called if you call hasFeatureFlag() (for example), but not if we call identifyUserWithTraits(). If we call identifyUserWithTraits() we get an empty list back.
This means, that if we manipulate the list that is returned without using the SDK methods we end up with unexpected fallbacks/defaults. Therefore, we would expect these methods to include the default already when called directly.
This is something that was brought to us by a new team that we just onboarded. We then analysed our code in production and we misused those methods too and have a bug in PROD that we are trying to now (luckily Flagsmith has always responded correctly in PROD so we haven't encountered this bug yet). But given that both teams have already had this bug, I would say the interface is misleading.
What do you think?

Ok, thanks for explaining @sw-tracker, I will have a look at the identifyUserWithTraits() method to understand further how this would best be solved.

PR merged


FEATURE: Add Process View

closes #51

Current coverage is 63.88% (diff: 74.19%)

Merging #67 into master will increase coverage by 0.89%

@@             master        #67   diff @@
==========================================
  Files             6          6
  Lines           716        778    +62
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits            451        497    +46
- Misses          188        200    +12
- Partials         77         81     +4

Powered by Codecov. Last update a3ae1f6...2e4115d


data manipulation / data error handling

version 3.X
Can we add a features for data manipulation/ error handling example: if data cell is null show (' ') empty

Hi @sahadat84
Version 3.X is deprecated. I'd advise that you switch to version 4.X. The migration should be very simple.
Apart from that, json2csv doesn't aim to do data processing, only to do the conversion. You can do the processing before calling json2csv.
Also, aren't empty fields already converted to ""? Have you checked the default option?
It would be easier to help you if you provide a data sample, the output that you are getting and the output that you would expect.

Closing since there was no response.
Please feel free to reopen if you think that it should be reopened.


"Usage" section seems useless to reader

In some documentation files we have "Usage" section, like this:
Defined as:

    multi method fmt(Pair:D:) returns Str:D {}

Usage:

    PAIR.fmt(FORMATSTRING)

Judging by grep, we have about 300 occurrences of such "examples". But, eh, is it really useful?
If we explain some method or subroutine, I think, anyone, who reads documentation, do know how to apply subroutines and call methods. For a method it's just value.method-name(maybe-some-args) - this formula doesn't change with every section, we just repeat useless stuff. We don't have any output example to be really useful for anyone in such sections, too. If we apply a function, it'll almost always(yes, perl 6 has many ways to call a subroutine, but that's not the case) be sub-name(value, some-other-args).
Is it me or this "Usage" sections are a bit redundant?
Secondly, because we have "fake" arguments there, like "PAIR" or "FORMATSTRING', it is impossible to check them with a compiler. I think, if we want to really show some usage, we need to rewrite all such strings as a proper examples, if we not, we need to remove such sections.

I'm more with having the actual signature (pretty much as in the declaration,) and then if necessary some example (or examples,) that show it being used with some example output.

IIRC @dha started adding those Usage sections but then someone raised concerns similar to yours and the work stopped.
They do seem redundant, though personally I'd be OK if those were replaced with actual usage; that is actual code example, rather than FORMATSTRING, say :foo<bar>.fmt: '%s: %s'

I was the one who raised that concern originally.
I believe they are intended to address the issue that to truly understand the signature presented in a perl 6 routine, you might have to understand a lot of extra syntax; The simplified approach is supposed to make it easier to understand.
My concern is that we already have to explain all the details of how signatures work; now we may also have to explain all the details about the USAGE blocks work.
I am fine with going all out with USAGES where needed, but I think we need to document the docs in that case.
If we end up just using function signatures, then we should have quick links/popups to "what this signature means" that are automatically generated.
The current situation with some USAGES and some not is confusing.

I believe that actual working examples will be more useful than just repeating of Type.method-name every time.
Signatures can really be strange for a novice(with all this :D:, slurps, etc), but actual example provides an ability to copy-paste code just from the docs and play with it a bit, to understand what is where.
Hence, my suggestion is to replace every Using occurrence with actual example with actual output. I can try to do this using my own time and knowledge, but if someone is willing to spend an evening or two to help me - I'll be really grateful.
If you're against of this replacement idea, please, write out your thoughts here. If you're okay with it, simple +1 will be enough.

The "confusing signatures" could be somewhat alleviated by a link of some sort to the signature documentation which IIRC is quite complete (or should be by now.)

It seems to me that:
multi method fmt(Pair:D:) returns Str:D {}
Has some real usability problems as docs, but it should be easily translated into something much more docish.
Some rules I'd propose:

method foo(Bar:D:) should become Bar instance method foo()
"multi" should be dropped unless required (e.g. we're showing multiple signatures for the same method/function
We should think about breaking out returns something:D as a separate line: returns defined something
Remove the trailing {}

So the example becomes:
instance method fmt()
returns defined Str
I'd suggest that's quite readable, but all of the transformations are pretty straightforward (heck, we could build it into Signature as something like .explain

I agree that we should have more useful examples. “Usage” section will indeed have less value if we provide enough useful examples.
That being said, I don't think that usage sections are “useless” when there are no examples. It is much easier to read than the actual signature (no matter how much you explain them, it is just harder to read). Compare yourself:
multi sub    split(  Str:D $delimiter, Str:D $input, $limit = Inf,
  :$skip-empty, :$v, :$k, :$kv, :$p) returns Positional

split( DELIMITER,  STRING [,LIMIT] [,:v] [,:k] [,:kv] [,:p] [,:skip-empty] )

I really don't like the idea of using things like instance method fmt(), because it's not Perl 6 syntax. If you read the docs, chances are you're already struggling with some Perl 6 concepts, and having to learn yet another syntax doesn't help much, especially when you find out that you can only use the syntax in the docs.

@AlexDaniel
They are easier to use mainly because they offer less info.
sub split($delimiter, $string, :$limit, :$v, :$k, :$kv, :$p, :$skip-empty) is much easier to read too.

@ajs let's see. Trailing {} is needed to compile all signatures. I've already seen(and fixed) places where signatures were wrong. If we are able to compile them - it's good. I don't like the idea of skipping this code pieces.
Separating of signature in two lines seems strange too. We have a few long methods, but we have much more short methods, they will look weird.
It's not the talk about an actual signatures, I suppose, they should be untouched. It's the documentation, not a language tutorial.

@pmurias I know, you are right. But people trying to learn Perl 6 want something readable to get started, and my point is that “usage” section is not as useless as this issue seems to suggests. It does offer less info, but sometimes that's what you want and need.
However, examples are even more useful, if done correctly. I don't mind “usage” sections go.

Hovering explanations could help people learn.

Don't add {} to sig code. Tag the block and make the test smart enough to add the {} for you

@coke it's a good idea, thanks.

My two cents:

Always show the signatures in proper Perl 6 notation.

Make sure that the free-form text + example snippets that follow it, are comprehensive enough to allow a newbie to learn all relevant information about the routine in question, without having to understand the signature.

@smls
1)It is already our base if we want to compile examples. The only one tricky point is that some signatures were changed in rakudo(is it from where they were taken? I somewhat doubt that). As example, see
https://docs.perl6.org/type/IO::Spec::Cygwin#method_abs2rel
and then
https://github.com/rakudo/rakudo/blob/8cbb1efd1d84fd57298e0e0813b64d8dd37140ba/src/core/IO/Spec/Cygwin.pm#L44
And yes, our IO::Spec are completely undocumented(but I believe they are similar to Perl equivalents).
If you mean that signatures should be correct, from the point of Perl 6, then we're working on it, since some of them contain typos/errors.
2)We cannot give some math proof of it, but I do efforts in this direction. Many eyes is a good problem detector too.

IIRC I autogenerated the IO::Spec docs about a year ago, so it is entirely possible that the actual methods have changed in the meantime.

@jonathanstowe then it's a time for a new issue for someone to investigate/write/test these pages.

With https://github.com/perl6/doc/commit/3029fc1075 last "Usage" sections were removed(you can still grep a few, but they are mostly needed).
We still need a decent example for .ACCEPTS method, but this issue can be closed.

As zoffixznet and coke pointed out, this was my work. When coke raised objections, I stopped, but when that happened, I asked if i should remove the usage statements and the response was, "no, don't do that yet" and that was where, AFAIK, it was left.
The discussions about it left me with the following feeling about this general area of documentation: Use the actual signatures, and have sufficient (fsvo) examples in the actual documentation, rather than usage statements. This, however, would, IMO, require very detailed documentation of signatures. jonathanstowe indicates that he thinks such documentation is currently complete, but, as I've been somewhat busy lately and out of the loop, I am not aware of that being the case. A quick look at docs.perl6.org does not have information on signatures jumping out at me, so I'm skeptical on that point.
In any case, if we can have an explicit, obvious, and complete Signatures documentation page, I see no reason why the usage statements can't be removed. And I'll be happy to be the one to do that if we have actual agreement on that point.

And now I see that I missed the comment indicating that they have, in fact, mostly been removed and this issue closed. Blah.
I was about to question Altai-man's comment that "you can still grep a few, but they are mostly needed" on the basis of why they'd be needed, but a quick grep shows that they all seem to be gone. shrug
I guess I'll shut up now.

@dha
with the latest commit, it looks like this now:
➜  doc-origin git:(master) ✗ grep -r "Usage:" doc/* | sort | nl
     1	doc/Language/5to6-nutshell.pod6:        Usage:
     2	doc/Language/functions.pod6:    Usage: {$*PROGRAM-NAME} [number]
     3	doc/Language/rb-nutshell.pod6:        opts.banner = 'Usage: example.rb --length=abc'
     4	doc/Language/rb-nutshell.pod6:        Usage:
     5	doc/Type/Any.pod6:Usage:
     6	doc/Type/Cancellation.pod6:Usage:
     7	doc/Type/IO/Path.pod6:Usage:
➜  doc-origin git:(master) ✗

First four matches are false positives, I wasn't able to come up with a good example for Any.ACCEPTS(if anybody willing to do it, it will be a good thing). Also, example of Cancellation method is missing for the same reason and the last one is a false positive.
About your words about the signatures - yes, I'm completely agree with you in the point that we need a good Signature page documentation. Personally, I don't think that we need signatures explanation in popups, but I'm not against it, so if someone wants to implement such a feature - don't be afraid to open a new issue or even pull request.


Fixes for the previously merged TryFrom

Turns out generating shim code via build.rs and relying on being correct without compiling/running any of it during testing is a bad idea. Code that does not get compiled won't fail tests either. Embarrassing.
Fixes:

I used #[cfg(feature = “try_from”)] instead #[cfg(feature = “try-from”)] causing my code to not even get generated. (#fdda4b1)
Had a wrong error type in one function that did not get caught. (#07319d7)
Had a wrong implementation in one function that did not get caught. (#e3d0328)

Changes:

Switched errors from core::num::TryFromIntError to cast::Error. (#35a3fbd)
Removed impls of TryFrom for usize/isize to mirror ‘stdlib’. (#67a17b1)
Refactored unit tests. Let’s actually run them this time, shall we? (#b134161)

As part of the unit test refactoring we are now also:

Testing From and TryFrom for every variant of cast::From, where applicable.
Splitting asserts into smaller test functions making it easier to see what's wrong.

We now have 418 tests for num-traits and 477 tests for cast::From/From/TryFrom.

Thanks @regexident
I think you may need to install the rustfmt-preview in the Travis builder for the buld script to work, though? Let's see what bors says.
bors r+

Could we try this one again, @japaric?


Removes overview.md from security

fixes #36591

Seems an irrelevant commit is included. You shall remove this commit: subscribe to kubeweelkly enchanced by running git rebase and commented out this commit.


Sprockets can't use a directory with a parentheses

When trying to start Middleman locally, it fails if the cloned source directory has a parentheses in its name, due to the sprockets gem.

Is this a problem with middleman, or a problem with Slate?

Hmm, I can't seem to reproduce the problem? Closing due to in activity, but feel free to reopen if you're still having problems!


DrunkenPython adhock solution for it #1

the problem was to solve int and str built-in functions.
Issue No.- #
Type issue number after hash(Py-Droid#178)

Checklist
[ y] Yes, this task assigned to me.
[ y] My code follows the style guidelines(Clean Code) of this project
[ y] I have performed a self-review of my own code
[ y] My Filename is in camelCase format
[ y] I have added Problem statement, Problem link in file.

Thanks for messaging but priority will give to issue-author(who created the issue)

No issue no. Unable to find


Examples for stm32f30x

As mentioned, we should have a couple of examples (one with and one without graphics perhaps?) using the stm32f30x. The examples at the moment use the stm32f103 chip commonly found on "Blue Pill" dev boards so shouldn't be too difficult to port.

I'm not too happy about platform specific examples in generic drivers. Not only will that drag in a lot of dependencies to mostly unstable crates which might change at any time but it'll also cause frustration when people try to use the driver but can't figure out how to get past the platform specifics.

For the record, neither am I. However, I do like the idea of having working examples with the driver because

It makes development much easier, and
People who are using the same hardware can get up to speed more quickly. I've seen device-specific stuff used in @japaric's crates, although I don't think he includes the dependencies for them which fixes one of the problems.

I'd like to explore the idea of Cargo workspaces. The driver can be in one crate (ssd1306) with examples and all their dependencies in the other (ssd1306-examples or something). I'm open to better suggestions, but I think that's a good way to go. Thoughts?

It sounds like a better idea. I really haven't looked into workspaces though.
I think japaric mostly uses large blocks of example code as in documentation which seems like a great idea but I haven't quite figured out how to work with code in docstrings efficiently.

although I don't think he includes the dependencies for them which fixes one of the problems.

For example specific dependencies I use dev-dependencies. These won't be compiled when the driver is compiled as a dependency, but they (dev-dependencies) are required to be published to publish the driver crate.

There's a growing corpus of examples in the community from HAL/project repositories, so I'm going to close this issue. It doesn't make much sense to have device-specific examples for a generic crate such as this, however I develop it on an STM32F103, so it makes life much easier for me. It should be pretty obvious which bits of the examples are ssd1306-specific, so gleaning usage out of them should still allow them to provide value.


indexId missing in AutocompleteRenderState type while being listed in the docs

🐛 Current behavior
The documentation for autocomplete shows the indices containing a property named indexId, but this isn't reflected in the AutocompleteRenderState type here. This means that we can't index on the indexId without writing some smelly typescript.
🔍 Steps to reproduce
Providing steps to repro this type mismatch seems a bit excessive. However, I'm happy to do it if the above description isn't sufficient.
Live reproduction
See comment above
💭 Expected behavior
I would expect the AutocompleteRenderState type in this file to contain the indexId like described in the docs.
Package version
instantsearch.js 4.64.3
Operating system
macOS 14.2.1
Browser
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

That's correct, thanks. I've just made a PR (https://github.com/algolia/instantsearch/pull/6050) to address this.

Wow that was fast. Thanks for moving so quickly on this 🙌


Name field in Speaker table should be unique - we have at least one duplicate

all other tables should also be checked to ensure that the relevant fields have unique constraints

(Ben Edmunds is the duplicate speaker)

Is a unique name columns the best way? What if you have three speakers named John Smith?


private app namespace dont need prefix

Coverage decreased (-0.03%) to 41.992% when pulling 05ceebadfcbf0d28a58135767106130f6088ec9f on lepdou:bugfix_0711 into 1b7a4aa036e19b36c7e12c0681dda58792230b3b on ctripcorp:master.

[Current coverage][cc-pull] is 39.59%
[][cc-pull]

No coverage report found for master at 1b7a4aa.

Powered by Codecov. Last updated by [1b7a4aa...05ceeba][cc-compare]
[cc-base-branch]: https://codecov.io/gh/ctripcorp/apollo/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/ctripcorp/apollo/compare/1b7a4aa036e19b36c7e12c0681dda58792230b3b...05ceebadfcbf0d28a58135767106130f6088ec9f?src=pr
[cc-pull]: https://codecov.io/gh/ctripcorp/apollo/pull/320?src=pr


Camera is reseted to default location when map is on tabbedpage

When I switch my application to third tab page camera position is reseted.
It is very interesting that switching to second page does not affect map camera position.
As you can see on this video: https://sendvid.com/mpfovxyl switching to third page affects map camera.
I think this relates to #7 but for sure I created this issue
Could you please confirm my idea?

Oh this is interesting.
Could you show me sample project for reproduce?

Hello,
i uploaded my solution to https://github.com/deextercz/iMHD/tree/xamarin.forms

Are you able to induce this issue?

I created bug in xamarin, because it is alsi in xamarin.forms.map
https://bugzilla.xamarin.com/show_bug.cgi?id=49057

Should be this fixed in xamarin.forms.maps or in this project?

I just investagated the problem and I think I got it.
[0:] Page No:1changed
12-26 22:17:40.334 W/FragmentManager( 5004): moveToState: Fragment state for FragmentContainer{ab1a12b8 #2 id=0x1 android:switcher:1:353799762} not updated inline; expected state 3 found 2
[0:] Page No:0changed
[0:] Page No:1changed
12-26 22:17:43.918 W/FragmentManager( 5004): moveToState: Fragment state for FragmentContainer{ab1a12b8 #2 id=0x1 android:switcher:1:353799762} not updated inline; expected state 3 found 2
[0:] Page No:2changed
12-26 22:17:46.750 I/Google Maps Android API( 5004): Google Play services package version: 10084070
12-26 22:17:46.750 W/f       ( 5004): Suppressed StrictMode policy violation: StrictModeDiskReadViolation
12-26 22:17:46.750 W/f       ( 5004): Suppressed StrictMode policy violation: StrictModeDiskWriteViolation
12-26 22:17:46.762 W/f       ( 5004): Suppressed StrictMode policy violation: StrictModeDiskReadViolation
12-26 22:17:46.762 D/dalvikvm( 5004): GC_CONCURRENT freed 1823K, 8% free 34916K/37796K, paused 1ms+2ms, total 9ms
12-26 22:17:46.766 W/f       ( 5004): Suppressed StrictMode policy violation: StrictModeDiskReadViolation
12-26 22:17:46.766 W/f       ( 5004): Suppressed StrictMode policy violation: StrictModeDiskWriteViolation
[0:] Page No:0changed
12-26 22:17:46.770 W/f       ( 5004): Suppressed StrictMode policy violation: StrictModeDiskReadViolation
12-26 22:17:46.818 D/GLHostConnection( 5004): Waiting for host to establish connection for PID 5004 (com.aulicon.imhd)
12-26 22:17:46.818 D/GLHostConnection( 5004): HostConnection::get() New Host Connection established 0xba57caa0, tid 5133
12-26 22:17:46.826 W/f       ( 5004): Suppressed StrictMode policy violation: StrictModeDiskReadViolation
12-26 22:17:46.826 W/f       ( 5004): Suppressed StrictMode policy violation: StrictModeDiskWriteViolation
12-26 22:17:46.870 D/dalvikvm( 5004): GC_CONCURRENT freed 1798K, 7% free 35166K/37796K, paused 0ms+1ms, total 21ms
12-26 22:17:46.870 D/dalvikvm( 5004): WAIT_FOR_CONCURRENT_GC blocked 20ms
12-26 22:17:46.874 D/dalvikvm( 5004): WAIT_FOR_CONCURRENT_GC blocked 6ms
12-26 22:17:46.918 D/dalvikvm( 5004): GC_FOR_ALLOC freed 1082K, 6% free 35760K/37796K, paused 6ms, total 6ms
12-26 22:17:46.922 I/dalvikvm-heap( 5004): Grow heap (frag case) to 38.985MB for 4194316-byte allocation
12-26 22:17:46.926 D/dalvikvm( 5004): GC_FOR_ALLOC freed 30K, 5% free 39826K/41896K, paused 7ms, total 7ms
12-26 22:17:46.934 D/dalvikvm( 5004): GC_CONCURRENT freed 142K, 5% free 39893K/41896K, paused 0ms+1ms, total 5ms
12-26 22:17:46.970 D/dalvikvm( 5004): GC_FOR_ALLOC freed 657K, 4% free 40541K/41896K, paused 11ms, total 11ms
12-26 22:17:47.038 D/dalvikvm( 5004): GC_FOR_ALLOC freed 6095K, 5% free 36034K/37796K, paused 5ms, total 5ms
12-26 22:17:47.082 D/dalvikvm( 5004): GC_FOR_ALLOC freed 723K, 6% free 36014K/38056K, paused 4ms, total 4ms
12-26 22:17:47.110 D/dalvikvm( 5004): GC_FOR_ALLOC freed 646K, 6% free 36017K/38056K, paused 5ms, total 5ms
12-26 22:17:47.142 D/dalvikvm( 5004): GC_FOR_ALLOC freed 519K, 6% free 36017K/38056K, paused 5ms, total 5ms
12-26 22:17:47.178 D/dalvikvm( 5004): GC_FOR_ALLOC freed 645K, 6% free 36020K/38056K, paused 5ms, total 5ms
12-26 22:17:47.226 D/dalvikvm( 5004): GC_FOR_ALLOC freed 647K, 6% free 36025K/38056K, paused 7ms, total 7ms
12-26 22:17:47.262 D/dalvikvm( 5004): GC_FOR_ALLOC freed 648K, 6% free 36029K/38056K, paused 4ms, total 4ms
12-26 22:17:47.306 D/dalvikvm( 5004): GC_FOR_ALLOC freed 645K, 6% free 36033K/38056K, paused 6ms, total 6ms
12-26 22:17:47.350 D/dalvikvm( 5004): GC_FOR_ALLOC freed 646K, 6% free 36037K/38056K, paused 5ms, total 5ms
On page 0 is MAP
so after click on Page0 there is executed garabage collector and it deletes all from memmory.
But it happens only when you click from page 2 to page 0 (if you have 3 tabs)
Could you help me with this?

@amay077 how about this solution?
    public MapSpan VisibleRegion
    {
        get { return _visibleRegion; }
        internal set
        {
            if (_visibleRegion == value)
                return;
            if (value == null)
                throw new ArgumentNullException(nameof(value));
            OnPropertyChanging();
            _visibleRegion = value;
            OnPropertyChanged();
            InitialCameraUpdate = CameraUpdateFactory.NewBounds(value.ToBounds(), 0); # fix for #101
        }
    }

I don´t know the reason of using OnPropertyChanging(); and OnPropertyChanged(); maybe it could be removed.

Hi @deextercz ,
You can write same code in app side.
public partial class BasicMapPage : ContentPage
{
    public BasicMapPage()
    {
        InitializeComponent();

        map.CameraChanged += (sender, e) =>
        {
            map.InitialCameraUpdate = CameraUpdateFactory.NewCameraPosition(e.Position);
        };
    }
}

OnPropertyChanging and OnPropertyChanged are needed because these are notifying VisibleRegion property before changing and after changed.

Hello @amay077 ,
I tried your solution with 1.8.0-beta5, but it freezes on my splash screen.
Mentioned my solution works.
Is there possibility to merge my changes and reopen PR #172 ?

Could you open a new issue first?


BSOD (MANUALLY_INITIATED_CRASH) on 1803 / ver. 17134

Hey,
I wanted to try out your debugging-framework, but sadly I always get a BSOD.
Here is an MEMORY.DMP out from my system:
The logfile from GuardMon says:
00:20:26.253	INF	#3	    4	 6244	System         	Log has been initialized. 00:20:26.271	INF	#0	    4	 6244	System         	Initializing VMX for the processor 0. 00:20:26.346	INF	#0	    4	 6244	System         	Initialized successfully. 00:20:26.347	INF	#1	    4	 6244	System         	Initializing VMX for the processor 1.
After that the BSOD with „MANUALLY_INITIATED_CRASH„  get hit.

Please pull the latest commits (both in GuardMon and submodule, HyperPlatform). This should be fixed now with commit 3adfd28

Please pull the latest commits (both in GuardMon and submodule, HyperPlatform). This should be fixed now with commit 3adfd28

Thanks, working as intended now!


Improvement for k8s.io/docs/tasks/run-application/configure-pdb/ - pods with long startup

Just wondering how to handle pods with long startup time?
The pods set with "initialDelaySeconds: 45" for startupProbe will show the status as (0/1) Running.
The old pod will be deleted once the new pod's status becomes (0/1) Running
But the new pod is still (0/1) and  not ready to handle traffic as the startup, readiness, liveness probes are yet to complete.
This will cause downtime!
It would be great to update the documentation to handle this scenario.

Page reported in issue (based on issue title): https://kubernetes.io/docs/tasks/run-application/configure-pdb
/language en

I was using kubectl delete pod for testing. Looks like we shall evict the pod instead of delete.
With evict pod, its working as expected. So it would be nice to add the right step to test in the doc 😄.

/sig node
/sig docs

/priority backlog
/triage accepted


Add instances for Data.Sequence

Make Data.Sequence.Seq an instance of Unfoldable and
of Unfolder.

Add a .gitignore file.

Add Other-extensions field to .cabal.

Fixes #2

That sounds likely, but I don't really understand Unfoldable yet.
On Oct 17, 2016 8:04 AM, "Sjoerd Visscher"<EMAIL_ADDRESS>wrote:

@sjoerdvisscher commented on this pull request.
In src/Data/Unfoldable.hs
https://github.com/sjoerdvisscher/unfoldable/pull/3#pullrequestreview-4458922
:

\ No newline at end of file

[ Reverse <$> getDualA (unfold (DualA fa)) ]

+instance Unfoldable S.Seq where

unfold fa = choose
[ pure empty
, (S.<|) <$> fa <*> unfold fa ]

Would it make sense to also add (S.|>) <$> unfold fa <*> fa?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/sjoerdvisscher/unfoldable/pull/3#pullrequestreview-4458922,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABzi_cyur-gDA2sukbRVcpbSLBnC6HZjks5q02QvgaJpZM4KYBdv
.

Oh, but we have to pick just one, right? Seq generally behaves like []
unless there's a good reason to behave otherwise.
On Oct 17, 2016 9:44 AM, "David Feuer"<EMAIL_ADDRESS>wrote:

That sounds likely, but I don't really understand Unfoldable yet.
On Oct 17, 2016 8:04 AM, "Sjoerd Visscher"<EMAIL_ADDRESS>wrote:

@sjoerdvisscher commented on this pull request.
In src/Data/Unfoldable.hs
https://github.com/sjoerdvisscher/unfoldable/pull/3#pullrequestreview-4458922
:

\ No newline at end of file

[ Reverse <$> getDualA (unfold (DualA fa)) ]

+instance Unfoldable S.Seq where

unfold fa = choose
[ pure empty
, (S.<|) <$> fa <*> unfold fa ]

Would it make sense to also add (S.|>) <$> unfold fa <*> fa?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/sjoerdvisscher/unfoldable/pull/3#pullrequestreview-4458922,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABzi_cyur-gDA2sukbRVcpbSLBnC6HZjks5q02QvgaJpZM4KYBdv
.

Hmm, I was thinking if you would generate arbitrary values for testing, you might want to add values on both sides. Usually there's one case for each constructor, but that doesn't apply in this case. So I guess picking one particular view like you did is the best option.
Another option is implementing Unfoldable for FingerTree, Digit and Node.
Do you have a particular use-case in mind?


Starr merge with config changes

several config changes in folder structure
added zip file script for non-windows
new app.zip to deploy to PC

This PR is about organizing out install artifacts and shortening our run.ps1 by consolidating logging


On the demo

On the demo after changing to any theme memory leak. D10.2.3

It's not a memory leak of the SVG components but only of the TTreeView of the demo.


Update UG

Codecov Report

Merging #195 (3db69a8) into master (71243ee) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #195   +/-   ##
=========================================
  Coverage     45.49%   45.49%
  Complexity      495      495
=========================================
  Files           129      129
  Lines          2473     2473
  Branches        292      292
=========================================
  Hits           1125     1125
  Misses         1259     1259
  Partials         89       89

Continue to review full report at Codecov.

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


'NoneType' object has no attribute 'tag'; causes files to be excluded from library

What version of Music Assistant has the issue?
2.2.2
What version of the Home Assistant Integration have you got installed?
N/A
Have you tried everything in the Troubleshooting FAQ and reviewed the Open and Closed Issues and Discussions to resolve this yourself?

[X] Yes

The problem
eyed3 returns None when reading some MP3 files. This is related to the fixed issue https://github.com/music-assistant/hass-music-assistant/issues/2656 but with a slightly different error message. We get this stacktrace when running in a development container:
2024-08-23 02:35:43.279 ERROR (MainThread) [music_assistant.filesystem_local] Error processing /path/to/some.mp3 - 'NoneType' object has no attribute 'tag'
Traceback (most recent call last):
  File "/workspaces/music-assistant-server/music_assistant/server/providers/filesystem_local/base.py", line 342, in sync_library
    track = await self._parse_track(item)
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/workspaces/music-assistant-server/music_assistant/server/providers/filesystem_local/base.py", line 761, in _parse_track
    tags = await parse_tags(input_file, file_item.file_size)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/workspaces/music-assistant-server/music_assistant/server/helpers/tags.py", line 453, in parse_tags
    if audiofile.tag is not None:
       ^^^^^^^^^^^^^
AttributeError: 'NoneType' object has no attribute 'tag'

How to reproduce
Not sure, but some of my badly tagged files seem to still anger eyed3 (incidentally, I think there are other MP3 tag parsers which might be more robust -- I've had good luck with tinytag in other projects). I haven't dug into why eyed3 rejects the files but it's hopefully moot as I have a workaround.
Music Providers
N/A
Player Providers
N/A
Full log output
No response
Additional information
PR with a workaround coming soon!
What version of Home Assistant Core are your running
2024.8.2
What type of installation are you running?
Home Assistant Container
On what type of hardware are you running?
Linux

Actually @MelHarbour was already looking into the tagging situation. He should review this.

Good tip about tinytag, I like the fact its pure python

We currently use ffmpeg/ffprobe as our primary tag reader but it has some issues with mp3 files where it simply doesnt read some of the tags, hence eyed3 is only used to fill in the blanks for mp3 files only. We are considering just switching to a different tag library completely, such as taglib or mutagen but the hard thing is that none of them are async friendly (so we still need to run in an executor) and full support for all tags and filetypes is also hard, that is why ffprobe was so great.
I guess we can swap it around. Use a more robust tag scanner for all common file formats and use ffprobe only for the obscure ones. I am definitely going to look into tinytag, maybe we can even make it async friendly

Thanks for the context! By the way, I just noticed that tinytag has a great library of weird MP3 (and other audio format) samples to test for robustness.
This one in particular is a great example of a file that's not supported by eyed3 but is parseable by tinytag. Happy to add it as a test case if that would be helpful.


Incompatible with Groove Coaster: Wai Wai Party

Doesn't seem to work with groove coaster.
No video or audio is streamed.

Took a look at the demo of the game, it has screenshots disabled in the nacp and this seems to prevent recording even with this patch. The youtube app has the same issue.
Currently i don't know how to fix it but will look into it.

Figured out how to patch that as well.  Download the new patches and it should work.
I only tested the demo and the youtube app but i assume it should work on the full game as well.


As a user, I would like to be able to display the current production speed.

Provide a general summary of the issue in the Title above
Expected Behavior
If the line is currently not producing I want to get back the production speed 0 and not the last one it produced at.
I also don't want the last production speed to fluctuate as much as the current minute is added up --> maybe the last 60 seconds should be considered for the last value.
Current Behavior

When I return the last value, it is the one that was last produced, regardless of how long ago that was. This also distorts the average production speed if the last values (standstill) are not included.

Is this still relevant @kruegeralex ?


Allow increase api request timeout

Hi in our project we are having timeout issue while fetch some blocks,
Error: timeout of 30000ms exceeded at createError (/usr/local/lib/node_modules/@subql/node-terra/node_modules/@terra-money/terra.js/node_modules/axios/lib/core/createError.js:16:15)

https://github.com/terra-money/terra.js/blob/9e5f553de3ff3e975eaaf91b1f06e45658b1a5e0/src/client/lcd/APIRequester.ts#L31
Is that possible to add an option allow us to manually increase the timeout? Thank you

30s of timeout is long enough i think. did you query to public lcd?

I also encountered the same problem, and they all appeared frequently

Hey! 👋🏻
If you are using the public LCD, maybe you should verify that you are not rate-limited.

@RomainLanz Thank you.

@jiqiang90 seems okay to close. feel free to reopen it if you want.


Integrate Zeit 'release' package

Setup for:

web-utils
canvas-image-draw
vitalizer

https://github.com/zeit/release

Using semantic-release instead


IMPORTANT DB UPDATE for Config Cleanup.

This is going to be a tricky update - we need to do this the folowing way:

Run this DB update.
Copy the settings into the backend under Status -> App Configuration.
Run the respective "git pull" commands.

Merged to stable.. Ready for push to QA


Addressnumber string

Accounts for address ranges that are not numeric. So far the following cases have been contemplated as per the TIGER/Line geocoding documentation

Address ranges can include numbers with alphabetic characters (i.e. G1-G99)
Some address systems use a hyphen to separate avenue numbers, private road
designators, and grid cell numbers from the structure numbers (i.e. 10-01)

Checking this out now.  Reading up on ScalaTest's Property-based Testing and Generator-driven Property Checks.

Review complete.  Overall looks good, though I think we should fix the Travis log spew issue before merging.

Travis is certainly much happier now.  However, there are still a considerable number or ERRORs being logged related to SearchUtilsSpec.
There's about 50 entries that look like:
[2015-08-26 18:20:22,642][ERROR][pool-7-thread-9-ScalaTest-running-SearchUtilsSpec] For input string: "C"
[2015-08-26 18:20:22,643][ERROR][pool-7-thread-9-ScalaTest-running-SearchUtilsSpec] For input string: "B"

...and nearly 100 that look like:
[2015-08-26 18:20:22,738][ERROR][pool-7-thread-9-ScalaTest-running-SearchUtilsSpec] For input string: ""

I don't quite understand what these mean.  It seems like an error logged from the internals of ScalaTest or ScalaCheck.  The tests themselves all pass, and this error does not seem related to our own error logging when unparsable strings are passed in.
@jmarin, thoughts?

Nevermind.  I must have been looking at a previous build or something.  I don't see the above-mentioned errors in the latest Travis build.  Merging...


Terraform 0.14 upgrade

what

Upgrade to support Terraform 0.14 and bring up to current Cloud Posse standard

why

Support Terraform 0.14

supersedes and closes #38
supersedes and closes #44
supersedes and closes #47

/test all

/test all

/test all

/test all

/test all


yorm: mark dataset->setRelatedCollection() as internal

https://github.com/FriendsOfREDAXO/rexstan/issues/407#issuecomment-1474784809
this method is not meant for public use outside of yform

Schade.

Wofür verwendest du es?


05/28/2018 02:11 : Create Pull Request for branch master -> prTesting1_2018052802

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

split/updateTestRef1.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


oidc auth provider does not support role mapping rules using custom keys

Roles can be mapped to oidc users based on claims.  While the rules allow setting arbitrary claims, the oidc implementation only allows a fixed set.  I would have used the Groups claim but Auth0 restricts setting that claim.  Digging into the code I found that backend_impl.go limits my choices to name, email, sub, groups, account_id and, as a boolean, is_org_admin.  And, while the ACS documentation notes that sub is mapped to userid, it makes no mention that account_id is mapped to orgid.  I was able to meet my need by creating an account_id claim and a rule matching value stored in orgid to a role, but that was not at all obvious.
The best case may be fully supporting custom claims within the oidc provider.  If not, then restricting rules to allowed claims would be helpful, and if not that, then please document the limitations.

The way the ACS OIDC provider works is that it takes claims token from the underlying IdP and adds them to ACS-issued token.
By default, only the aforementioned claims(name, email, sub, groups) are added. However, there is an ability to add custom claim mappings which will transform IdP token claim to an ACS-issued token claim. You can find documentation here: doc
There are two ways to add these claim mappings to auth provider:

By using auth provider API
Starting with 4.1, you could leverage declarative config functionality that will allow you to create auth resources via k8s ConfigMap/Secret.

At the moment you can't add claim mappings via auth provider UI, however, it is on our roadmap.

@ghoff, the upcoming 4.4.0 version will also have the UI for the mapping functionality.


use an arg file for scalac to deal with large targets

we don't want large targets for build speed and incrementalism, but for thrift it might happen (and we'd rather be slow than fail).

@jcoveney what do you think?

LGTM


Username tab completion inconsistency

Sometimes users who've recently spoken in a moderately large (but relatively slow) chat (~1000-1500 viewers) are not in the tab completion list accessed via @abc<tab>. I'm not quite sure why they're not being added in to the tab complete list, but it's happening pretty regularly. I would recommend a similar methodology to suggested in #14 and/or sorting user tab-complete by who most recently spoke.

Issue has something to do with case-sensitivity and hashing of the completion model, I've looked into it a bit but not committed to fixing it just yet