chore: fix coverage

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@4dcb634). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             master        #1   +/-   ##
==========================================
  Coverage          ?   100.00%
==========================================
  Files             ?         3
  Lines             ?        77
  Branches          ?        13
==========================================
  Hits              ?        77
  Misses            ?         0
  Partials          ?         0

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


Can pomsky provide a permutations operation?

Is your feature request related to a problem? Please describe.
It's cumbersome to list all permutation of anded patterns, this can be done as a sugar syntax in pomsky?
Describe the solution you'd like
In pomsky: 'fox' & 'dog'
In regex:.(?:fox.?dog|dog.?fox)
Describe alternatives you've considered
Not yet
Additional context
No

I wouldn't call this an 'and' operation. You can think of regular expressions as sets, and | creates the union of two sets. Logically, & would be the intersection of two sets, which is rarely useful.
I'm not sure if permutation deserves dedicated syntax, and if we decide to implement this, it won't use the & symbol. Available symbols are: ~@$%/-,<>

Sure, what ever you call it is okay, I mean the need for this is real, it's useful to search a line with all patterns match no matter the order, like I want a line with both keywords of 'fox' and 'dog' in. Otherwise, I have to filter out all lines with 'fox' matched, then filter again over the results with 'dog' matched.


Investigate FlatBuffers

FlatBuffers are the serialization format used by TensorFlowLite: https://google.github.io/flatbuffers/

Done: https://github.com/PaddlePaddle/Mobile/wiki/FlatBuffers-Survey

Refer to: https://github.com/PaddlePaddle/Mobile/wiki/FlatBuffers-Survey


Fix link on features page

I'm not quite sure if this link is pointing to what you want, but this makes it point there correctly.

Perfect,  thanks!  I'll merge that as soon as Github lets me!


Error: Some specified paths were not resolved, unable to cache dependencies

Description:
I have a Github action to deploy as Astro site to Github Pages. Recently, it has been failing with the following error.
Error: Some specified paths were not resolved, unable to cache dependencies.

I think it is coming due to the fact that setup-node is trying to locate the cache inside apps/docs folder but since it is a monorepo, it is located two levels up.
From the job run, I noticed this:
cache-dependency-path: ./apps/docs/yarn.lock

There is no yarn.lock inside apps/docs since this is a monorepo.
Action version:
v3
Platform:

[ ] Ubuntu
[x] macOS
[ ] Windows

Runner type:

[x] Hosted
[ ] Self-hosted

Tools version:

Node 16.19
Yarn 3.2.0
Repro steps:
See the Github job: https://github.com/codelitdev/courselit/actions/runs/4132972124/jobs/7142310620
Expected behavior:
It should not throw an error.
Actual behavior:
An error is thrown.

It happens to me the same. I am trying to deploy my site with GitHub pages using Astro and GitHub Actions. The Action failed in the same as you. What was the solution to this problem? Thanks

It happens to me the same. I am trying to deploy my site with GitHub pages using Astro and GitHub Actions. The Action failed in the same as you. What was the solution to this problem? Thanks

Hi @DakkuaDev, did you manage to get around this yet? Struggling with this too!

@Dan-Finan in my case the package-lock.json file was in .gitignore, so not part of the repository. The setup-node action was trying to access the package-lock.json file but it wasn't pushed to the repo.

@lemilonkh thanks man your solution worked for me. Remove package-lock.json file from .env guys


add some tags to be searchable

So I had a problem to find this library, that is not abandoned about Vulkan and Common Lisp, will be nice if you add some tags like "common-lisp" "vulkan" and "graphics" to be searchable on Github, is a very nice library that more people need to know and I only find it because of one Reddit post that you probably made, so yeah, will be very nice to add some tags.
If you search "cl vulkan" or "common lisp vulkan" your library not even show up.

Thanks for the tip.  I added some tags.


Update hello-minikube.md

Removed --port option from kubectl create deployment as its not supported
fixes #11445

/check-cla

/check-cla

We have got at least three PRs to solve this issue. What an active community!


Fixed alignment issues for portrait images

Fixes #742

Description

Fixed: alignment issues with portrait images

Checklist
- [ ] I have made corresponding changes to the documentation.
- [ ] I have updated the types definition of modified exports.

[x] I have verified the functionality in some of the neeto web-apps.
[x] I have added the necessary label (patch/minor/major - If package publish
is required).

Reviewers
@AbhayVAshokan _a

@AbhayVAshokan Changes will be made to the neetoKB's EUI once this issue is closed.


[Bug] Inability to show right-most X axis label on bar charts

Version
5.2.2
Link to Minimal Reproduction
https://echarts.apache.org/examples/en/editor.html?c=bar-y-category&code=PYBwLglsB2AEC8sDeAoWtJgDYFMBcya6GOAHmAQOQDqwATlgCawAKoArlgIaQyVEBfADREwwYFkggCqYhjoQA5opx0qXUhADOlEXI3a2EaGFUyicsAE8Q-WJS0ALLo2AB3fnIGC9sXCuhGGWEiRQUgwjlcADMKewBmAFJdC1gFRUc4ygBGZN90ACNgMDEAWyoklLkAYxgwLmMAGS4CnCwCMDp2HB8iUgBBTS1zSxs7SgA3LixuquIi9kCuOisAcS5pWABtAAYhWB2AOh3sgF1e9CtB7RHia1sqap4cRXorOfRGHi4CLcoAIToXAAXhAsLp7ABJQIwHBaCBcCGUACqAGV-kjoYwEUiAMKOYyI_Y0ehMSjndAhdBaVQQOG_VKyOSwaBcUrjABMJ2yHzuYyoBWWvM-31-2QAHFz4vsOfEACzigCcMsVO3l-2yOzlioA7HtYNl4tkdXK5fsAGzxHaynanfLEbitdqRZnUxzuDpdHD2uQgYDw3jQKjpTKeZneLz2plyVnsqhc7Ic4UYfn2QV0ZNfepixXxDkAVhl8vi4v2Rp2FY1HOy-cVZoN8uycuyFvFEp2OrtqVd6EdbVurqcHvk3R9xD9AagQfsIbAYa8qQjsHOAgA3EA
Steps to Reproduce

Create a bar chart.
Label position is set to right and and the right grid is set to '1%'
Grid and Series/Label options

Current Behavior
When the the x-axis label at the the very right is very long or has a big font size some part of it can become invisible, or cut in half.
Expected Behavior
The issue can be corrected by increasing or decreasing the grid percentage, but then, the labels on the right end of the bars can become invisible as well.  And it can cause a big gap on the right hand side.
What is expected: the x-axis label at the very right can be hidden without the loss of series labels.
Environment
- OS:Linux Ubuntu 22.04
- Browser:Chrome 96.0.4664.55
- Framework<EMAIL_ADDRESS>
Any additional comments?
No response

grid: {containLabel: true} fixes it all (no left,right,etc.)

grid: {containLabel: true} fixes it all (no grid.right)

In the above link i provided containLabel is set to true, but still, you can only see half of the rightmost x-axis label. The problem still presists.

You could play with grid.width in %, but still narrow screens will have the problem.
  grid: {
    left: 5,
    width:'93%',
    bottom: '3%',
    containLabel: true
  }

You could play with grid.width in %, but still narrow screens will have the problem.
  grid: {
    left: 5,
    width:'93%',
    bottom: '3%',
    containLabel: true
  }

yes, there are hard-coded solutions for the above problem (ie. grid.right, grid.containLabel etc.). What all these solutions have in common is to increase the rightmost gap, but as you said in narrow screens or when a bigger font size is used for the labels, these approaches does not always work effectively.
Can the Echarts crew develop a dynamic/reactive solution for these kinds of scenarios?

width:'93%',

@helgasoft Echarts has collusion preventing properties like xAxis.boundaryGap and position.hideOverlap. These options works regardless of screen size. Can we have a similar one for the rightmost x-axis label?
It is true that if we omit grid.right and set containLabel to true the problem is solved. But the rightmost gap is default and set to a very large value. As you said it can be modified with grid.width, but again it does not work for all screen sizes. The above mentioned properties (ie. boundaryGap, hideOverlap etc.) work for every screen size. Can we have a similar property for this specific scenario that created this bug report?


fix args and lint issues

looks like the linter didn't like my last PR. I don't tend to run with --all so I didn't notice.
Sorry about that, here are some fixes
valgrind doesn't take well to empty arguments on Linux as it turns out so I fixed that too (tested originally on a mac).

Thank you!
Once again there is an issue on the master-branch (seems like I'm doing something horribly wrong): the CI doesn't run for pull-requests, that do originate from a forked repository... That's why I merged the PR without running CI (as there were none, so GitHub didn't show the red x) and it failed only on the master branch.
In the meantime I've updated the master-branch, so that PRs from forks also trigger a CI run. Thefore I'd like to ask you kindly: could you rebase once more onto the current master?
Thanks again!

Thank you for the review; this branch is now based on upstream/master.

Thank you very much!


[zeromq]Fix missing system version for mingw builds

Describe the pull request

What does your PR fix?
Fixes missing system version that is required to compile the code. It is detected in the main CMakeLists.txt file and used later as a _WIN32_WINNT - macro get_WIN32_WINNT in CMakeLists.txt. System version is required to be 6.0 or higher for ZeroMQ to work correctly.

Which triplets are supported/not supported? Have you updated the CI baseline?
This will not affect any other triplets except mingw, CI baseline is not updated.

Does your PR follow the maintainer guide?
I bump the version of the port using YYYY-MM-DD-N format

Seems all test passed, does this PR ready for review?

SGTM


If possible, please make FastImage.preload() return Promise.

Hi Guys,
First of all, You are doing awesome work. Package was almost abandoned. Thanks for reviving it.
Secondly, I have a situation where I need to preload the image (5-6) before showing to the user. I have used ReactNative's Image component for caching bcs it's Image.preload returns promise and fast image  was not actively maintained. But now I'm using your forked repo.
Can you please make FastImage.preload() promise.
Thanks

@HarwinderSingh15 Can you explain more about your use-case or share some code if possible.

@deepanshushuklad11
👇Here is my use case
I need to preload all the images for the screen before navigating to it, similar to how Instagram does. I show a loading indicator until all the images are loaded, and then I display the screen. Previously, I achieved this using Image.preload provided by React Native, which returns a promise. Now that I'm using the FastImage package, the FastImage.preload() method does not return a promise.

@HarwinderSingh15 this seems very specific use case , ideally user should move on to next screen and preload can happen in background.

@deepanshushuklad11
I agree with you, but making it promise can help in both situation

@HarwinderSingh15 Fair point.
If you could make changes and raise a PR for the same i am happy to look.

@deepanshushuklad11 Sure. I'll create PR within some days. Thanks


Metadata-free conformance and additional columns

The standard says

A dataset can be CLDF conformant without providing a separate metadata description file. To do so, the dataset must follow the default specification for the appropriate module regarding

I had assumed I could add additional columns which just would not have well-defined semantics and only string as possible datatype. But when I tried to load
ID,Language_ID,Parameter_ID,Form,Segments,Comment,Source,Cognate_Set
0,abai1240,feature1,form,,,,0
1,afad1236,feature1,form,,,,1
2,ambu1247,feature1,form,,,,0

I can get the Cognate_Set column by using iterdict, but I cannot ask the Dataset object whether that column exists.

[ ] Clarify in the CLDF specs whether additional columns are permitted in mdf conformance (I'll raise a separate issue there)
[ ] If they are permitted, sniff the table header to add them to the table spec
[ ] In any case, unify column existence between tableSpec and iterdicts
[ ] Fix cldf validate to enforce the specs

(Or convince me why the current state is as it should be – as has happened often enough – and a bit of documentation about it somewhere.)

The scenario you describe isn't a problem of "metadata-free conformance". Even with a description file, iterdicts may return dictionaries with more keys than listed in the tableSchema. So I guess there are two levels of support for additional columns:

Implicit: You'd have to inspect the first dictionary returned by iterdicts
Explicit: Whatever is listed as non-virtual column in the description

I wouldn't want to force-add all columns to the description, because this would require reading (parts of) the data file right away and because this would interfere with the expliciteness of the description. So, in terms of the ZEN of CLDF I'd say:

Whatever isn't listed in the description shouldn't be accessed by CLDF-aware software.
If the default descriptions for metadata-free conformance don't list what you want to access, create an explicit more inclusive description first, which can subsequently also serve as documentation for your code.

In that case, I think it's good enough to document this behaviour in the iterdicts docstring (which is completely missing at the moment: https://github.com/clld/clldutils/issues/60)


[Spotify Controls] ...

Extension
https://www.raycast.com/thomas/spotify-controls
Description

Error:
Could not load command

Steps To Reproduce

install extension
Try any of the commands, pause, next track, etc.
Nothing happens and get error

Current Behaviour
Command does nothing to Spotify and you get an error message in Raycast
Expected Behaviour
Should do command - play, pause, next track, etc

Restarting Spotify and Raycast, I was prompted with the Mac OS message to allow Raycast work with Spotify (can't quite remember the exact copy). All is well and working as intended. Thanks for this extension!


Added a word - curfew

Added a word "curfew" and its definition to the collection
The Pull Request resolves Issue #[Issue-Number]
Description:
A brief description about the addition or edits made.
Notes: Delete all the text including this!

The #[Issue-Number] should be replaced with the specific Issue being referenced.

Adding word curfew to the collection


Trying out osx within Travis

Overview
This PR tries out osx within Travis CI.

Pull Request Test Coverage Report for Build 77

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 58.0%

Totals

Change from base Build 75:
0.0%

Covered Lines:
232

Relevant Lines:
400

💛  - Coveralls


Can't provide credentials for install via CLI

Paket allows to specify an api key for the push command, also taking it from the nugetkey environment variable. The same functionality doesn't exist for other commands (e.g. install).
Currently the only way to authenticate with a private nuget server is to specify an apikey with the source declaration in the dependencies file. This results in private credentials working their way into source control which has obvious security problems.
Ideally I'd like to be able to specify a key on the command line. There's some complication with this as the key works per source item and potentially infinite sources can be pulled by any one file - perhaps a key per group or default to using the same key across all sources if only one is provided.

Is there a workaround for keeping credentials out of the paket.dependencies file?
Would this be a reasonable feature for a PR?

Have you seen the paket config add-credentials command? https://fsprojects.github.io/Paket/paket-config.html

see also https://fsprojects.github.io/Paket/nuget-dependencies.html#NuGet-feeds
source http://myserver/nuget/api/v2 username: "%PRIVATE_FEED_USER%" password: "%PRIVATE_FEED_PASS%"

allows to use env variables

awesome, thanks!


InfluxDB allows more than just UDP subscriptions

To my knowledge, InfluxDB subscriptions can be HTTP[s] or UDP. The section listed below just refers to the UDP subscriptions and makes no mention of HTTP[s]. I know the section I was looking at is just a getting started section, but it could possibly lead to some misunderstanding for the reader.
Additionally, the subscriptions link on the page links to the InfluxQL spec which isn't super helpful. subscriptions
URL for relevant page?
https://github.com/influxdata/docs.influxdata.com/blob/master/content/kapacitor/v1.0/introduction/getting_started.md#starting-kapacitor

Closing as a dup of newer #1620.


[2.1.0] Document integrating spatie/laravel-activitylog

I am trying to integrate the spatie/laravel-activitylog , however, it is not picking up and saving to the tenant.
Is there a way to get this working to save to the DB for system if not a tenant domain and to the tenant if for their domains.
Any help would be appreciated!

I was talking with @stancl about this earlier today. I haven't had a chance to test it yet, but we were considering keeping the default connection (in the activitylog config file) set to central or mysql or whatever your central connection is, and using the bootstrapping event to set that config key to $tenantManager->getTenant()->getConnectionName()

I wonder if that default connection parameter could fallback to the Laravel default connection instead of the other way around.
Pinging @gummibeer for input.

I have ended up finding a way to do it.
I discovered that the Activity model sets the connectionName and the tableName in the Model class in the construct is it is not already set.
I simply created the following class to work with the Activity Model
{
    public function __construct(array $attributes = [])
    {
        if (! isset($this->connection)) {
            logger(Domain::exists(request()->getHost()));
            if (Domain::exists(request()->getHost())) {
                logger('tenant');
                $this->setConnection('');
                logger(isset($this->connection));
            } else {
                logger('system');
                $this->setConnection(config('activitylog.database_connection'));
            }
        }

        if (! isset($this->table)) {
            $this->setTable(config('activitylog.table_name'));
        }

        parent::__construct($attributes);
    }
}

it is a little bit of a hack but if you can find a way to use the events to overwrite the connection for packages like this it would be worth doing.

I'd suggest keeping the DB in the activity log config central and using this in AppServiceProvider:
Tenancy::hook('bootstrapped', function ($tenantManager) {
    config(['activitylog.connection', $tenantManager->getTenant()->getDatabaseConnection()]);
});

And on the ended event you'd set it back to your central connection.
Hope that makes sense, I'm writing this on mobile.
@Gummibeer I was going to open an issue. I think activitylog should fallback to the default DB connection, because:

changing your default DB connection would be enough to change your app's DB
some apps, like the ones using this package, use dynamic connections. Falling back to default is really useful here. I can imagine some sharding logic working similarly.

During config loading we fall back to the default Laravel env. But I think you mean something like null in config and use database.default in the model construct? This would make sense and I don't see a point to don't do it. Would this solve your issue here? 🤔

Yeah, that's what I meant.
The connection is set each time the model is constructed.
https://github.com/spatie/laravel-activitylog/blob/808a3e5c119d31d1115ff7831efa866aa3fe9692/src/Models/Activity.php#L23
Since models aren't singletons, I think it would solve it.
I'll take a better look at this in the afternoon when I'm on my computer.

You can also set the connection to null and it should work. No need for hooks.

@stancl I tried your suggestion of using the booted hook however it did not work even after I corrected a slight issue with your code.
Setting the Activity Log Connection to null does work however.
Thanks for the suggestion.
If I get a moment I will create a pull request for documentation of Spatie Activity Log

@jny986 Glad to hear that. No need to make a PR, I will be writing a documentation page specifically about integrating Spatie packages.

https://github.com/spatie/laravel-activitylog/releases/tag/3.9.1

https://github.com/stancl/tenancy-docs/commit/99655ea7e03b3d40959418a30aff23703b720c8d

Hi @stancl , love this package. From what I read from the docs, it seems that we can only use 1 option rather than both? Say if I would like to log in the central, AND in the tenant scope, is that possible just by setting db_connection to null? Thank you

Bumping the previous question, @stancl, thanks!


Add volume machine variable

To be able to show the current volume on a slide.
-> add to service mode

maybe one variable per track? @qcapen

changed to machine variable


keytool fails to parse APK signatures if there is a signature mismatch in a APK

Very strange situation, BUT some APKs have invalid signatures of files in the APK, so keytool fails. Will try to determine the best way to handle this.

Working on a commit that changes the "signature" table and Signature() class to better address this. Adding schema change tag.

Should be fixed here: https://github.com/jakev/dtfmods-core/commit/7efdbcbeada2f880a7066f03b6d4ea2a5820b482


Automator: update go-control-plane in istio/istio@master

Generated by Automator - 2024-03-10T02:01:12+00:00

@istio-testing: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-telemetry-istiodremote_istio
6a93f9f16db3d15489771035ee89224eb49529d0
link
true
/test integ-telemetry-istiodremote

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test integ-telemetry-istiodremote

@istio-testing: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-pilot_istio
6a93f9f16db3d15489771035ee89224eb49529d0
link
unknown
/test integ-pilot

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test integ-pilot

@istio-testing: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-pilot_istio
6a93f9f16db3d15489771035ee89224eb49529d0
link
unknown
/test integ-pilot

integ-security-multicluster_istio
6a93f9f16db3d15489771035ee89224eb49529d0
link
unknown
/test integ-security-multicluster

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test integ-security-multicluster


Content block simple/segmented/media/cards Leadspace block unmatched left/right margin at medium breakpoint

Detailed description

Describe in detail the issue you're having.

Content block simple/segmented, content block - cards and Leadspace block do not match at the medium breakpoint

Is this a feature request (new component, new icon), a bug, or a general
issue?  Bug

Is this issue related to a specific component?
content block segmented
content block media
Leadspace block

####Additional Information

React Storybook Study Box note

Not happening anymore. Tested on canary


[firebase_dynamic_links] sometimes got error NSPOSIXErrorDomain Code=53 in ios

As in link, there is a case of nil at the completion of handleUniversalLink.
https://github.com/firebase/firebase-ios-sdk/issues/2303
Also, even if  sleep,  cause an error, so fixed it to tell
it to the dart side.
https://github.com/flutter/flutter/issues/27810

I don't think our current flutter drive based integration testing can regression test this change, so I'm ok with merging it as-is. We should get rid of the NSError categories to match other plugins, but that can happen in a subsequent PR.

@collinjackson @bparrishMines
It became all green. Could you merge?

Yea I can merge it for you. I added a version bump and a corresponding part to the android side.
Thanks for the contribution! I'll merge once it goes green again.


Feat/onepanelio.core 348.system.updates

What this PR does:
Code cleanup and update CreateWorkflowExecution to have a WorkflowTemplate as a parameter
Which issue(s) this PR fixes:
Fixes onepanelio/core#
Special notes for your reviewer:

Getting this error when selecting a Workspace template in Workspace creation form:
ERRO[0466] finished unary call with code Unknown         error="no nodePoolOptions in config" grpc.code=Unknown grpc.method=GetWorkspaceTemplate grpc.service=api.WorkspaceTemplateService grpc.start_time="2020-06-19T21:55:02-07:00" grpc.time_ms=243.939 span.kind=server system=grpc

@Vafilor let's discuss this PR whenever you're back on it, see my comments in this draft PR


date info is missing in the autocreated album

I appreciate very much the capability to automatically group pictures according date criteria. It allows not to systematically have to create manual albums to group photos and ease photos searching.
But, there are no indication about the date in the album name except the day of the week !
I think that "Monday Morning with X and Y in this place and that place" should be improved with at least the date of the first picture and duration (for instance). Intuitively, the use can deduce many things looking at album cover but not the capture date !

LibrePhotos/librephotos-frontend#135 is the easiest fix for this. Just display the date below album title.
The display is already a mess on mobile, so adding more text will make it even more messy.

Thanks! To ease things everywhere, replacing long title which takes place (often 3 or 4 lines) and is not really useful (at least for me) with date (or min/max) would be enough!!!

I think removing the date from the function https://github.com/LibrePhotos/librephotos/blob/d2e1a6f9983e940122f699a163066848e38c0592/api/models/album_auto.py#L28
here would be the next step :)

I insist but there is a problem with the place taken by the title on the screen! On my tablet or my phone (chrome android, but ios should be the same ;-) ) it is sometime so large that date and number of pictures is not visible!
According to me, only date and number of pictures should be displayed, additional information being displayed by an other way (mouseover for instance).


Support markdown report in Gradle plugin

For #4967

Why is it failing on Windows 11?

Windows is flaky. Don't worry about it.

Thanks for the PR!


Installing 'black'
$ "D:\\Git\\whdload_slave\\.venv\\Scripts\\pip.exe" install   --verbose    "black" -i https://pypi.python.org/simple --exists-action w
Config variable 'Py_DEBUG' is unset, Python ABI tag may be incorrect
Config variable 'WITH_PYMALLOC' is unset, Python ABI tag may be incorrect
Collecting black
  1 location(s) to search for versions of black:
  * https://pypi.python.org/simple/black/
  Getting page https://pypi.python.org/simple/black/
  Looking up "https://pypi.python.org/simple/black/" in the cache
  Current age based on date: 660
  Freshness lifetime from max-age: 600
  Freshness lifetime from request max-age: 600
  The cached response is "stale" with no etag, purging
  Starting new HTTPS connection (1): pypi.python.org
  https://pypi.python.org:443 "GET /simple/black/ HTTP/1.1" 200 899
  Updating cache with response from "https://pypi.python.org/simple/black/"
  Caching b/c date exists and max-age > 0
  Analyzing links from page https://pypi.python.org/simple/black/
    Found link https://pypi.python.org/packages/22/5a/ebe5881cbf07435ea1ad76119ee142f42fb7a333d562c202db015b959ae7/black-18.3a0-py3-none-any.whl#md5=7bf286e5faebfd76af1eeb50b2a4c007 (from https://pypi.python.org/simple/black/) (requires-python:>=3.6), version: 18.3a0
    Found link https://pypi.python.org/packages/83/a2/fae3ddb516a52a0f37e6e2ef3bd789b6d093d2c7015a41a41bff30f39897/black-18.3a0.tar.gz#md5=cfdf55cf7969d2cd18ae90fcf0d2356b (from https://pypi.python.org/simple/black/) (requires-python:>=3.6), version: 18.3a0
    Found link https://pypi.python.org/packages/61/b4/3a39dcf59342f53680c59a5e44c0b172ea5d6470a5aaba8ae3cdbfccc1e7/black-18.3a1-py3-none-any.whl#md5=c706fc2879b3f7dc8008f92134144996 (from https://pypi.python.org/simple/black/) (requires-python:>=3.6), version: 18.3a1
    Found link https://pypi.python.org/packages/1b/4d/ff18ef3018083196b85c843387dfa6a1faf376e8f662f74634bad84092d5/black-18.3a1.tar.gz#md5=c1ac46cd7a5cb7096d5dee97e7781c93 (from https://pypi.python.org/simple/black/) (requires-python:>=3.6), version: 18.3a1
    Found link https://pypi.python.org/packages/83/12/450fb640290d1499ae3922f95190b66b36918656c68376517a8477c6c4c9/black-18.3a2-py36-none-any.whl#md5=c7d1a628e0eff9dc3fcb1224c470d887 (from https://pypi.python.org/simple/black/) (requires-python:>=3.6), version: 18.3a2
    Found link https://pypi.python.org/packages/f7/2b/359a321cb63d3b4a9aecc0d0fb87dd20023ed1a6bd1a9ab44fb1db91580a/black-18.3a2.tar.gz#md5=1c73162ae40f9b193b4c557df336c87b (from https://pypi.python.org/simple/black/) (requires-python:>=3.6), version: 18.3a2
    Found link https://pypi.python.org/packages/3a/ae/3e4c6b429af58b100d3cbdd1b7c0ba0d3d8b74781761961b4ede32390810/black-18.3a3-py36-none-any.whl#md5=cc4c2a1e486497709bfca988a709099b (from https://pypi.python.org/simple/black/) (requires-python:>=3.6), version: 18.3a3
    Found link https://pypi.python.org/packages/0f/69/f60a77390ae2182e8370fe669632812915599163853e55d04dec3ebed605/black-18.3a3.tar.gz#md5=04d3abf0cae51b904e2e73adbd8bc995 (from https://pypi.python.org/simple/black/) (requires-python:>=3.6), version: 18.3a3
    Found link https://pypi.python.org/packages/5e/c7/a1acc4f8f6baecacefabcf79e2165255f5605c7e33108aa58f16f4e55760/black-18.3a4-py36-none-any.whl#md5=14fbfc046e1e4456dcd535f5e753bf91 (from https://pypi.python.org/simple/black/) (requires-python:>=3.6), version: 18.3a4
    Found link https://pypi.python.org/packages/f1/c2/a336bc9bf176d30d9824e587fbe6f921ee51d7ab5f67f28ad7c2ee52fc8c/black-18.3a4.tar.gz#md5=9bcd445e512ed976d71c0ad1d7f0f6b5 (from https://pypi.python.org/simple/black/) (requires-python:>=3.6), version: 18.3a4
  Using version 18.3a4 (newest of versions: 18.3a0, 18.3a1, 18.3a2, 18.3a3, 18.3a4)
  Looking up "https://pypi.python.org/packages/5e/c7/a1acc4f8f6baecacefabcf79e2165255f5605c7e33108aa58f16f4e55760/black-18.3a4-py36-none-any.whl" in the cache
  Current age based on date: 661
  Freshness lifetime from max-age: 31557600
  The response is "fresh", returning cached response
  31557600 > 661
  Using cached black-18.3a4-py36-none-any.whl
  Downloading from URL https://pypi.python.org/packages/5e/c7/a1acc4f8f6baecacefabcf79e2165255f5605c7e33108aa58f16f4e55760/black-18.3a4-py36-none-any.whl#md5=14fbfc046e1e4456dcd535f5e753bf91 (from https://pypi.python.org/simple/black/) (requires-python:>=3.6)
Collecting click (from black)
  1 location(s) to search for versions of click:
  * https://pypi.python.org/simple/click/
  Getting page https://pypi.python.org/simple/click/
  Looking up "https://pypi.python.org/simple/click/" in the cache
  Current age based on date: 661
  Freshness lifetime from max-age: 600
  Freshness lifetime from request max-age: 600
  The cached response is "stale" with no etag, purging
  https://pypi.python.org:443 "GET /simple/click/ HTTP/1.1" 200 4747
  Updating cache with response from "https://pypi.python.org/simple/click/"
  Caching b/c date exists and max-age > 0
  Analyzing links from page https://pypi.python.org/simple/click/
    Found link https://pypi.python.org/packages/82/e9/39bc04e46ac4dc16f60d3c95d2a8238f8a86a738ecab723755470e1486d1/click-0.1-py2.py3-none-any.whl#md5=0cc6bb5069cd4aded45df121da94b482 (from https://pypi.python.org/simple/click/), version: 0.1
    Found link https://pypi.python.org/packages/1a/65/bde2803d3f5d217fde361f7773d51d5c9b1332181f740bdd7adb2462607c/click-0.1.tar.gz#md5=9f1eb0ea0d713e61c0a1a805095092a3 (from https://pypi.python.org/simple/click/), version: 0.1
    Found link https://pypi.python.org/packages/ee/a5/97f43386352a0658f12842848c152479fce3162251c08339866da45e912e/click-0.2-py2.py3-none-any.whl#md5=a8107b8c2ef4c28c0cb13957688656ee (from https://pypi.python.org/simple/click/), version: 0.2
    Found link https://pypi.python.org/packages/bb/aa/c8b583d8d7cc5e21c8da30de6d8c605652836b4ef33b2b57c37f6a017c09/click-0.2.tar.gz#md5=5dfdd49507748b776db6c051191b367f (from https://pypi.python.org/simple/click/), version: 0.2
    Found link https://pypi.python.org/packages/dd/ce/ae6ede3636c212a9b33fbe93754e0caee570405d6af3b2b3c95988ce601b/click-0.3-py2.py3-none-any.whl#md5=5bcb7aee93c18342927bf1ff0f475462 (from https://pypi.python.org/simple/click/), version: 0.3
    Found link https://pypi.python.org/packages/35/19/29f7f3ff89929a0a5b938a2a63ecb0d02e6faa4e9a6d84bcedbcc638e212/click-0.3.tar.gz#md5=5d9563adb701eb6508dd03180b69d0a7 (from https://pypi.python.org/simple/click/), version: 0.3
    Found link https://pypi.python.org/packages/88/e8/04c8f87706b72b470214502461c6c53081d64e6b82c8a2b4ba303a4caa53/click-0.4-py2.py3-none-any.whl#md5=f987186fcd3ceb83405542aeada54709 (from https://pypi.python.org/simple/click/), version: 0.4
    Found link https://pypi.python.org/packages/1c/4d/98210295b2f14097de14db6be528af60ba9a3ef60b7e9efb207b08cdea1a/click-0.4.tar.gz#md5=f5d95b8bafd0cf2e1c8938fade7058d0 (from https://pypi.python.org/simple/click/), version: 0.4
    Found link https://pypi.python.org/packages/a3/01/a0f85fd64800f0f477f7d36ec7c3e87758e78d1e4b39a590b16a436a0ff9/click-0.5-py2.py3-none-any.whl#md5=383371917b60bc71e94124f4ee76a396 (from https://pypi.python.org/simple/click/), version: 0.5
    Found link https://pypi.python.org/packages/72/de/ab7b1f0952b411a61bb155d3dbf6271e4d39841cb7b124b75f82117157a4/click-0.5.tar.gz#md5=7717647596f0dbac3ea2abfbb14e9e8e (from https://pypi.python.org/simple/click/), version: 0.5
    Found link https://pypi.python.org/packages/e9/4c/ce5c6a47f240de954cbcba430a7a4afdc13e3b7482d5302048a4e6611281/click-0.5.1-py2.py3-none-any.whl#md5=5eec0adef35a10bab82f5bdeb318e4ca (from https://pypi.python.org/simple/click/), version: 0.5.1
    Found link https://pypi.python.org/packages/82/46/e17055162fd9baa4ec7a4064ec313091fea3e3dad4047bf63b46471998ac/click-0.5.1.tar.gz#md5=03aea68acd0402273d10846581c154ba (from https://pypi.python.org/simple/click/), version: 0.5.1
    Found link https://pypi.python.org/packages/36/f2/648fe6bdc708b71c81c2db677ba7ac640aac7798a1198cc953eeac1d0041/click-0.6-py2.py3-none-any.whl#md5=f66a36e97a157788ab40168d1c696593 (from https://pypi.python.org/simple/click/), version: 0.6
    Found link https://pypi.python.org/packages/3f/e3/18d6042b27cc41d4ca0ac9ce035d0d3d9cde2d6f0902d3f6f08d04aff596/click-0.6.tar.gz#md5=49268a0b714d88499b0ae74ea315b706 (from https://pypi.python.org/simple/click/), version: 0.6
    Found link https://pypi.python.org/packages/f1/67/1b1c2077a99b9e2b5c4127e733ca4a90f8c9f0da05e256911aea8b25a31a/click-0.7-py2.py3-none-any.whl#md5=4ed8c0b279f982048f0852088aca0389 (from https://pypi.python.org/simple/click/), version: 0.7
    Found link https://pypi.python.org/packages/b4/7b/d57f1bc99f0776d79cfc1969a9e1eaffefe0fab153c5bd5abd1445b4805f/click-0.7.tar.gz#md5=970c4f58099d8f0132e5c53ad26729a8 (from https://pypi.python.org/simple/click/), version: 0.7
    Found link https://pypi.python.org/packages/25/71/234cf198880e0afd2edc69cafb97bbc34f5da90a29efa59787319c5f6c2d/click-1.0-py2.py3-none-any.whl#md5=3914880d0f97a722248d42a7d16e6b88 (from https://pypi.python.org/simple/click/), version: 1.0
    Found link https://pypi.python.org/packages/69/f4/c8b37e427b1810069b84db6aba7cb5c6e569d64e762add3f77183a5c49b0/click-1.0.tar.gz#md5=1b373dba472fbb9328cfbddfde61da9e (from https://pypi.python.org/simple/click/), version: 1.0
    Found link https://pypi.python.org/packages/89/60/384e2ab6f408564c9b86cac3680d89ea1aa12dbf5e7e89009c37b3c75511/click-1.1-py2.py3-none-any.whl#md5=ac934d5f166064d4b22ef9814f31f8b8 (from https://pypi.python.org/simple/click/), version: 1.1
    Found link https://pypi.python.org/packages/0a/37/9c433ae49db7d89bdab56e33d712837f6bd9d76d697d0f532ba449998ad7/click-1.1.tar.gz#md5=cb5a9b715bfffe7a297d107829978f45 (from https://pypi.python.org/simple/click/), version: 1.1
    Found link https://pypi.python.org/packages/1a/31/d1dcb9d90345731eaef95ee28d21b549ad3f637076ba02a51ffd7c97cf36/click-2.0-py2.py3-none-any.whl#md5=73f58892ba05d0fbdb56fa7c2c822c4a (from https://pypi.python.org/simple/click/), version: 2.0
    Found link https://pypi.python.org/packages/f3/78/915ee51099f8244181e6a85628ad836c0b505ee2efc0323b3554055544e2/click-2.0.tar.gz#md5=259ebb6fcf28a72df2104db8f5a22962 (from https://pypi.python.org/simple/click/), version: 2.0
    Found link https://pypi.python.org/packages/a7/99/3a3fbb2cff270d1da99f7c78f54f75aa598c17af59f0eb77f4d2ff9a84fc/click-2.1-py2.py3-none-any.whl#md5=d1003edfac1fd82eb539b1b3ba01cb61 (from https://pypi.python.org/simple/click/), version: 2.1
    Found link https://pypi.python.org/packages/26/ef/9152572c7d926c587aa75c7d39030422a7d1cec883f02965797b48ec1352/click-2.1.tar.gz#md5=0ba97ba09af82c56e2d35f3412d0aa6e (from https://pypi.python.org/simple/click/), version: 2.1
    Found link https://pypi.python.org/packages/a3/36/d7fc5be7e81506c0687100f7cf0de443bf9467b2f4e47400f59e9c4a8bfd/click-2.2-py2.py3-none-any.whl#md5=70cd3b28d696c6e882b0818352352505 (from https://pypi.python.org/simple/click/), version: 2.2
    Found link https://pypi.python.org/packages/30/05/12c666a6c55e315d70897f80005a8fc09c17f1d4137dd25667d849e16088/click-2.2.tar.gz#md5=e07460aab221e1b7ceee0018122e04a9 (from https://pypi.python.org/simple/click/), version: 2.2
    Found link https://pypi.python.org/packages/00/39/e0cb46e47f283e56e24107ee36456788106e744be284c998fbe8c7a7096e/click-2.3-py2.py3-none-any.whl#md5=7898be3bf41c91d003dd9cced5a8b183 (from https://pypi.python.org/simple/click/), version: 2.3
    Found link https://pypi.python.org/packages/90/b3/85bdfbdf0191ab1e691ec0530a1d65c9f5354a1caf635abdc1eb1bc59ac4/click-2.3.tar.gz#md5=ce4852da9d4c33855e6f55e1fd06c1ac (from https://pypi.python.org/simple/click/), version: 2.3
    Found link https://pypi.python.org/packages/fd/07/4df913eac02a5eed807a18e237f8d12e130cdf80085eab5a7a0b2fdffb07/click-2.4-py2.py3-none-any.whl#md5=52fb03573ab024cca207bd421888b08a (from https://pypi.python.org/simple/click/), version: 2.4
    Found link https://pypi.python.org/packages/a9/19/87bff1b8e670e2763043bbc0125449ab9861bd20a40e348f7ba47539d8b2/click-2.4.tar.gz#md5=7affaac2973184810c018fab7cedca4f (from https://pypi.python.org/simple/click/), version: 2.4
    Found link https://pypi.python.org/packages/83/93/b0209d3e0fcc1918808dd2eb2eb26f5edbc2722695cc4b8a63d1a11faebe/click-2.5-py2.py3-none-any.whl#md5=c1af149f5e10491831311f0e32aa7001 (from https://pypi.python.org/simple/click/), version: 2.5
    Found link https://pypi.python.org/packages/6b/ca/8441cb224f040af2a71056b6de5d7bfdfe60c580931f6226587ef7617870/click-2.5.tar.gz#md5=a1bff2d2270745affd5bc60e66e50c23 (from https://pypi.python.org/simple/click/), version: 2.5
    Found link https://pypi.python.org/packages/d1/bc/9afb108a31cb0fd37e6774b23569197aee9974425d9c361a29e3eade9f32/click-2.6-py2.py3-none-any.whl#md5=75941e4e80563ca134fda5045b537c78 (from https://pypi.python.org/simple/click/), version: 2.6
    Found link https://pypi.python.org/packages/fc/92/403b0389319c017d9971570b6fc868e789fba31d96c53799ba726bae6a34/click-2.6.tar.gz#md5=bf5fbaecc1370934347b82ec707e3413 (from https://pypi.python.org/simple/click/), version: 2.6
    Found link https://pypi.python.org/packages/f6/66/65f7bcdcb6ace560cc5d6c4cdbb968bfc8d53f256ba206bf1884e547d786/click-3.0-py2.py3-none-any.whl#md5=13cead4d730cf0184e981bc2b5748248 (from https://pypi.python.org/simple/click/), version: 3.0
    Found link https://pypi.python.org/packages/8d/f7/e4a41b165fbe0a1c52db0cfc1e2f4452fcbdfa240c66fd0300a3acc858b9/click-3.0.tar.gz#md5=6919bcf8dcbe99197893464a97f640d5 (from https://pypi.python.org/simple/click/), version: 3.0
    Found link https://pypi.python.org/packages/a3/8a/7b995e58729456e0ce61cc1ec91b77835da0171e3dcc1283c09212bea2ed/click-3.1-py2.py3-none-any.whl#md5=008bac40c0e11f6be2226a5667b67095 (from https://pypi.python.org/simple/click/), version: 3.1
    Found link https://pypi.python.org/packages/03/7b/4e36fd53099764fa70b5e56f2e089bfd9f433fb8da873326b5d8ee8b1820/click-3.1.tar.gz#md5=6fc0aa839e01ac1d05c4a823c698b6b2 (from https://pypi.python.org/simple/click/), version: 3.1
    Found link https://pypi.python.org/packages/85/e4/a39441e8cd202d5ad4af4e8e97d4c49d59f5ef60368721fab29ec4247240/click-3.2-py2.py3-none-any.whl#md5=7d0bf0ca4e8ce6056e35cc8135d21abd (from https://pypi.python.org/simple/click/), version: 3.2
    Found link https://pypi.python.org/packages/ee/0b/4bb57fb1115590ab62faf8552f3aaa4b9caf18af7b272abc379a31604371/click-3.2.tar.gz#md5=f8a439029337ff39ed814ae5ce948318 (from https://pypi.python.org/simple/click/), version: 3.2
    Found link https://pypi.python.org/packages/b7/21/ce45306a697fc80ebe0b73ce04ecc08c54488b2dbe74babc068959683fd5/click-3.3-py2.py3-none-any.whl#md5=5ca07a6c8b1eaca8e529cdb50a8a8349 (from https://pypi.python.org/simple/click/), version: 3.3
    Found link https://pypi.python.org/packages/15/0f/9070074d2bdabf216f99b922a5c85ef1bfc304236086d3bf77c6b35eacfc/click-3.3.tar.gz#md5=40edaba4d216915a8326c5b2cb52781d (from https://pypi.python.org/simple/click/), version: 3.3
    Found link https://pypi.python.org/packages/0c/d5/9b5cc74d3ac814140c1a0b89534b7d148c5b399b12f69883335d9c5cc622/click-4.0-py2.py3-none-any.whl#md5=c25cb7af50132bbf00eaf3b439815874 (from https://pypi.python.org/simple/click/), version: 4.0
    Found link https://pypi.python.org/packages/7b/61/80731d6bbf0dd05fe2fe9bac02cd7c5e3306f5ee19a9e6b9102b5784cf8c/click-4.0.tar.gz#md5=79b475a1dbd566d8ce7daba5e6c1aaa7 (from https://pypi.python.org/simple/click/), version: 4.0
    Found link https://pypi.python.org/packages/6e/97/f25f4277d90efa3d34ced57137023ecb96e0c9aacf79b4f93efe6d94a2f8/click-4.1-py2.py3-none-any.whl#md5=4c0dca35693367bf63b4290281dfeb2c (from https://pypi.python.org/simple/click/), version: 4.1
    Found link https://pypi.python.org/packages/4c/eb/dc135683e4865bbcba60b09b158bf491756a1c36d0e2820002235bf72a8a/click-4.1.tar.gz#md5=6a3fa88c738f2f775ec6de126feb99a4 (from https://pypi.python.org/simple/click/), version: 4.1
    Found link https://pypi.python.org/packages/af/55/056901e9f504a7cda9e955592360ce2c516b2b92f3da9318ba074be5d280/click-5.0-py2.py3-none-any.whl#md5=ae5a1032fb7e08e73213a847321044c2 (from https://pypi.python.org/simple/click/), version: 5.0
    Found link https://pypi.python.org/packages/3e/4f/e66a06ab731ba91faa60142d4e465fde941104fe9b6d27d1b9548f03ec64/click-5.0.tar.gz#md5=7c91618e3b067319250770d6e1f0f5c7 (from https://pypi.python.org/simple/click/), version: 5.0
    Found link https://pypi.python.org/packages/8f/98/14966b6d772fd5fba1eb3bb34a62a7f736d609572493397cdc5715c14514/click-5.1-py2.py3-none-any.whl#md5=03c35
Adding black to Pipfile's [dev-packages]…
Pipfile.lock (625834) out of date, updating to (f10a67)…
Locking [dev-packages] dependencies…

Warning: Your dependencies could not be resolved. You likely have a mismatch in your sub-dependencies.
  You can use $ pipenv install --skip-lock to bypass this mechanism, then run $ pipenv graph to inspect the situation.
Could not find a version that matches black
Tried: 18.3a0, 18.3a0, 18.3a1, 18.3a1, 18.3a2, 18.3a2, 18.3a3, 18.3a3, 18.3a4, 18.3a4

When running pipenv graph after running pipenv install --skip-lock after the above as suggested this is all I get, I can't see any problem with the dependencies.
black==18.3a4
  - attrs [required: >=17.4.0, installed: 17.4.0]
  - click [required: Any, installed: 6.7]

Steps to replicate
Provide the steps to replicate (which usually at least includes the commands and the Pipfile).
pipenv install black --dev --verbose
Contents of Pipfile
[[source]]
url = "https://pypi.python.org/simple"
verify_ssl = true
name = "pypi"

[packages]

[dev-packages]
black = "*"

[requires]
python_version = "3.6"

Black is in alpha, you could try pipenv install --pre black which will also install prereleases.

--dev --pre black to get it in your dev section, but yeah.  It's a pre-release so you'll need to enable those with the --pre flag as @anowlcalledjosh mentioned

I get the same result using pre I'm afraid.
Installing black…
Installing 'black'
$ "D:\\Git\\black_test\\.venv\\Scripts\\pip.exe" install --pre  --verbose    "black" -i https://pypi.python.org/simple --exists-action w
Config variable 'Py_DEBUG' is unset, Python ABI tag may be incorrect
Config variable 'WITH_PYMALLOC' is unset, Python ABI tag may be incorrect
Collecting black
  1 location(s) to search for versions of black:
  * https://pypi.python.org/simple/black/
  Getting page https://pypi.python.org/simple/black/
  Looking up "https://pypi.python.org/simple/black/" in the cache
  Current age based on date: 123
  Freshness lifetime from max-age: 600
  Freshness lifetime from request max-age: 600
  The response is "fresh", returning cached response
  600 > 123
  Analyzing links from page https://pypi.python.org/simple/black/
    Found link https://pypi.python.org/packages/22/5a/ebe5881cbf07435ea1ad76119ee142f42fb7a333d562c202db015b959ae7/black-18.3a0-py3-none-any.whl#md5=7bf286e5faebfd76af1eeb50b2a4c007 (from https://pypi.python.org/simple/black/) (requires-python:>=3.6), version: 18.3a0
    Found link https://pypi.python.org/packages/83/a2/fae3ddb516a52a0f37e6e2ef3bd789b6d093d2c7015a41a41bff30f39897/black-18.3a0.tar.gz#md5=cfdf55cf7969d2cd18ae90fcf0d2356b (from https://pypi.python.org/simple/black/) (requires-python:>=3.6), version: 18.3a0
    Found link https://pypi.python.org/packages/61/b4/3a39dcf59342f53680c59a5e44c0b172ea5d6470a5aaba8ae3cdbfccc1e7/black-18.3a1-py3-none-any.whl#md5=c706fc2879b3f7dc8008f92134144996 (from https://pypi.python.org/simple/black/) (requires-python:>=3.6), version: 18.3a1
    Found link https://pypi.python.org/packages/1b/4d/ff18ef3018083196b85c843387dfa6a1faf376e8f662f74634bad84092d5/black-18.3a1.tar.gz#md5=c1ac46cd7a5cb7096d5dee97e7781c93 (from https://pypi.python.org/simple/black/) (requires-python:>=3.6), version: 18.3a1
    Found link https://pypi.python.org/packages/83/12/450fb640290d1499ae3922f95190b66b36918656c68376517a8477c6c4c9/black-18.3a2-py36-none-any.whl#md5=c7d1a628e0eff9dc3fcb1224c470d887 (from https://pypi.python.org/simple/black/) (requires-python:>=3.6), version: 18.3a2
    Found link https://pypi.python.org/packages/f7/2b/359a321cb63d3b4a9aecc0d0fb87dd20023ed1a6bd1a9ab44fb1db91580a/black-18.3a2.tar.gz#md5=1c73162ae40f9b193b4c557df336c87b (from https://pypi.python.org/simple/black/) (requires-python:>=3.6), version: 18.3a2
    Found link https://pypi.python.org/packages/3a/ae/3e4c6b429af58b100d3cbdd1b7c0ba0d3d8b74781761961b4ede32390810/black-18.3a3-py36-none-any.whl#md5=cc4c2a1e486497709bfca988a709099b (from https://pypi.python.org/simple/black/) (requires-python:>=3.6), version: 18.3a3
    Found link https://pypi.python.org/packages/0f/69/f60a77390ae2182e8370fe669632812915599163853e55d04dec3ebed605/black-18.3a3.tar.gz#md5=04d3abf0cae51b904e2e73adbd8bc995 (from https://pypi.python.org/simple/black/) (requires-python:>=3.6), version: 18.3a3
    Found link https://pypi.python.org/packages/5e/c7/a1acc4f8f6baecacefabcf79e2165255f5605c7e33108aa58f16f4e55760/black-18.3a4-py36-none-any.whl#md5=14fbfc046e1e4456dcd535f5e753bf91 (from https://pypi.python.org/simple/black/) (requires-python:>=3.6), version: 18.3a4
    Found link https://pypi.python.org/packages/f1/c2/a336bc9bf176d30d9824e587fbe6f921ee51d7ab5f67f28ad7c2ee52fc8c/black-18.3a4.tar.gz#md5=9bcd445e512ed976d71c0ad1d7f0f6b5 (from https://pypi.python.org/simple/black/) (requires-python:>=3.6), version: 18.3a4
  Using version 18.3a4 (newest of versions: 18.3a0, 18.3a1, 18.3a2, 18.3a3, 18.3a4)
  Looking up "https://pypi.python.org/packages/5e/c7/a1acc4f8f6baecacefabcf79e2165255f5605c7e33108aa58f16f4e55760/black-18.3a4-py36-none-any.whl" in the cache
  Current age based on date: 2145
  Freshness lifetime from max-age: 31557600
  The response is "fresh", returning cached response
  31557600 > 2145
  Using cached black-18.3a4-py36-none-any.whl
  Downloading from URL https://pypi.python.org/packages/5e/c7/a1acc4f8f6baecacefabcf79e2165255f5605c7e33108aa58f16f4e55760/black-18.3a4-py36-none-any.whl#md5=14fbfc046e1e4456dcd535f5e753bf91 (from https://pypi.python.org/simple/black/) (requires-python:>=3.6)
Collecting click (from black)
  1 location(s) to search for versions of click:
  * https://pypi.python.org/simple/click/
  Getting page https://pypi.python.org/simple/click/
  Looking up "https://pypi.python.org/simple/click/" in the cache
  Current age based on date: 123
  Freshness lifetime from max-age: 600
  Freshness lifetime from request max-age: 600
  The response is "fresh", returning cached response
  600 > 123
  Analyzing links from page https://pypi.python.org/simple/click/
    Found link https://pypi.python.org/packages/82/e9/39bc04e46ac4dc16f60d3c95d2a8238f8a86a738ecab723755470e1486d1/click-0.1-py2.py3-none-any.whl#md5=0cc6bb5069cd4aded45df121da94b482 (from https://pypi.python.org/simple/click/), version: 0.1
    Found link https://pypi.python.org/packages/1a/65/bde2803d3f5d217fde361f7773d51d5c9b1332181f740bdd7adb2462607c/click-0.1.tar.gz#md5=9f1eb0ea0d713e61c0a1a805095092a3 (from https://pypi.python.org/simple/click/), version: 0.1
    Found link https://pypi.python.org/packages/ee/a5/97f43386352a0658f12842848c152479fce3162251c08339866da45e912e/click-0.2-py2.py3-none-any.whl#md5=a8107b8c2ef4c28c0cb13957688656ee (from https://pypi.python.org/simple/click/), version: 0.2
    Found link https://pypi.python.org/packages/bb/aa/c8b583d8d7cc5e21c8da30de6d8c605652836b4ef33b2b57c37f6a017c09/click-0.2.tar.gz#md5=5dfdd49507748b776db6c051191b367f (from https://pypi.python.org/simple/click/), version: 0.2
    Found link https://pypi.python.org/packages/dd/ce/ae6ede3636c212a9b33fbe93754e0caee570405d6af3b2b3c95988ce601b/click-0.3-py2.py3-none-any.whl#md5=5bcb7aee93c18342927bf1ff0f475462 (from https://pypi.python.org/simple/click/), version: 0.3
    Found link https://pypi.python.org/packages/35/19/29f7f3ff89929a0a5b938a2a63ecb0d02e6faa4e9a6d84bcedbcc638e212/click-0.3.tar.gz#md5=5d9563adb701eb6508dd03180b69d0a7 (from https://pypi.python.org/simple/click/), version: 0.3
    Found link https://pypi.python.org/packages/88/e8/04c8f87706b72b470214502461c6c53081d64e6b82c8a2b4ba303a4caa53/click-0.4-py2.py3-none-any.whl#md5=f987186fcd3ceb83405542aeada54709 (from https://pypi.python.org/simple/click/), version: 0.4
    Found link https://pypi.python.org/packages/1c/4d/98210295b2f14097de14db6be528af60ba9a3ef60b7e9efb207b08cdea1a/click-0.4.tar.gz#md5=f5d95b8bafd0cf2e1c8938fade7058d0 (from https://pypi.python.org/simple/click/), version: 0.4
    Found link https://pypi.python.org/packages/a3/01/a0f85fd64800f0f477f7d36ec7c3e87758e78d1e4b39a590b16a436a0ff9/click-0.5-py2.py3-none-any.whl#md5=383371917b60bc71e94124f4ee76a396 (from https://pypi.python.org/simple/click/), version: 0.5
    Found link https://pypi.python.org/packages/72/de/ab7b1f0952b411a61bb155d3dbf6271e4d39841cb7b124b75f82117157a4/click-0.5.tar.gz#md5=7717647596f0dbac3ea2abfbb14e9e8e (from https://pypi.python.org/simple/click/), version: 0.5
    Found link https://pypi.python.org/packages/e9/4c/ce5c6a47f240de954cbcba430a7a4afdc13e3b7482d5302048a4e6611281/click-0.5.1-py2.py3-none-any.whl#md5=5eec0adef35a10bab82f5bdeb318e4ca (from https://pypi.python.org/simple/click/), version: 0.5.1
    Found link https://pypi.python.org/packages/82/46/e17055162fd9baa4ec7a4064ec313091fea3e3dad4047bf63b46471998ac/click-0.5.1.tar.gz#md5=03aea68acd0402273d10846581c154ba (from https://pypi.python.org/simple/click/), version: 0.5.1
    Found link https://pypi.python.org/packages/36/f2/648fe6bdc708b71c81c2db677ba7ac640aac7798a1198cc953eeac1d0041/click-0.6-py2.py3-none-any.whl#md5=f66a36e97a157788ab40168d1c696593 (from https://pypi.python.org/simple/click/), version: 0.6
    Found link https://pypi.python.org/packages/3f/e3/18d6042b27cc41d4ca0ac9ce035d0d3d9cde2d6f0902d3f6f08d04aff596/click-0.6.tar.gz#md5=49268a0b714d88499b0ae74ea315b706 (from https://pypi.python.org/simple/click/), version: 0.6
    Found link https://pypi.python.org/packages/f1/67/1b1c2077a99b9e2b5c4127e733ca4a90f8c9f0da05e256911aea8b25a31a/click-0.7-py2.py3-none-any.whl#md5=4ed8c0b279f982048f0852088aca0389 (from https://pypi.python.org/simple/click/), version: 0.7
    Found link https://pypi.python.org/packages/b4/7b/d57f1bc99f0776d79cfc1969a9e1eaffefe0fab153c5bd5abd1445b4805f/click-0.7.tar.gz#md5=970c4f58099d8f0132e5c53ad26729a8 (from https://pypi.python.org/simple/click/), version: 0.7
    Found link https://pypi.python.org/packages/25/71/234cf198880e0afd2edc69cafb97bbc34f5da90a29efa59787319c5f6c2d/click-1.0-py2.py3-none-any.whl#md5=3914880d0f97a722248d42a7d16e6b88 (from https://pypi.python.org/simple/click/), version: 1.0
    Found link https://pypi.python.org/packages/69/f4/c8b37e427b1810069b84db6aba7cb5c6e569d64e762add3f77183a5c49b0/click-1.0.tar.gz#md5=1b373dba472fbb9328cfbddfde61da9e (from https://pypi.python.org/simple/click/), version: 1.0
    Found link https://pypi.python.org/packages/89/60/384e2ab6f408564c9b86cac3680d89ea1aa12dbf5e7e89009c37b3c75511/click-1.1-py2.py3-none-any.whl#md5=ac934d5f166064d4b22ef9814f31f8b8 (from https://pypi.python.org/simple/click/), version: 1.1
    Found link https://pypi.python.org/packages/0a/37/9c433ae49db7d89bdab56e33d712837f6bd9d76d697d0f532ba449998ad7/click-1.1.tar.gz#md5=cb5a9b715bfffe7a297d107829978f45 (from https://pypi.python.org/simple/click/), version: 1.1
    Found link https://pypi.python.org/packages/1a/31/d1dcb9d90345731eaef95ee28d21b549ad3f637076ba02a51ffd7c97cf36/click-2.0-py2.py3-none-any.whl#md5=73f58892ba05d0fbdb56fa7c2c822c4a (from https://pypi.python.org/simple/click/), version: 2.0
    Found link https://pypi.python.org/packages/f3/78/915ee51099f8244181e6a85628ad836c0b505ee2efc0323b3554055544e2/click-2.0.tar.gz#md5=259ebb6fcf28a72df2104db8f5a22962 (from https://pypi.python.org/simple/click/), version: 2.0
    Found link https://pypi.python.org/packages/a7/99/3a3fbb2cff270d1da99f7c78f54f75aa598c17af59f0eb77f4d2ff9a84fc/click-2.1-py2.py3-none-any.whl#md5=d1003edfac1fd82eb539b1b3ba01cb61 (from https://pypi.python.org/simple/click/), version: 2.1
    Found link https://pypi.python.org/packages/26/ef/9152572c7d926c587aa75c7d39030422a7d1cec883f02965797b48ec1352/click-2.1.tar.gz#md5=0ba97ba09af82c56e2d35f3412d0aa6e (from https://pypi.python.org/simple/click/), version: 2.1
    Found link https://pypi.python.org/packages/a3/36/d7fc5be7e81506c0687100f7cf0de443bf9467b2f4e47400f59e9c4a8bfd/click-2.2-py2.py3-none-any.whl#md5=70cd3b28d696c6e882b0818352352505 (from https://pypi.python.org/simple/click/), version: 2.2
    Found link https://pypi.python.org/packages/30/05/12c666a6c55e315d70897f80005a8fc09c17f1d4137dd25667d849e16088/click-2.2.tar.gz#md5=e07460aab221e1b7ceee0018122e04a9 (from https://pypi.python.org/simple/click/), version: 2.2
    Found link https://pypi.python.org/packages/00/39/e0cb46e47f283e56e24107ee36456788106e744be284c998fbe8c7a7096e/click-2.3-py2.py3-none-any.whl#md5=7898be3bf41c91d003dd9cced5a8b183 (from https://pypi.python.org/simple/click/), version: 2.3
    Found link https://pypi.python.org/packages/90/b3/85bdfbdf0191ab1e691ec0530a1d65c9f5354a1caf635abdc1eb1bc59ac4/click-2.3.tar.gz#md5=ce4852da9d4c33855e6f55e1fd06c1ac (from https://pypi.python.org/simple/click/), version: 2.3
    Found link https://pypi.python.org/packages/fd/07/4df913eac02a5eed807a18e237f8d12e130cdf80085eab5a7a0b2fdffb07/click-2.4-py2.py3-none-any.whl#md5=52fb03573ab024cca207bd421888b08a (from https://pypi.python.org/simple/click/), version: 2.4
    Found link https://pypi.python.org/packages/a9/19/87bff1b8e670e2763043bbc0125449ab9861bd20a40e348f7ba47539d8b2/click-2.4.tar.gz#md5=7affaac2973184810c018fab7cedca4f (from https://pypi.python.org/simple/click/), version: 2.4
    Found link https://pypi.python.org/packages/83/93/b0209d3e0fcc1918808dd2eb2eb26f5edbc2722695cc4b8a63d1a11faebe/click-2.5-py2.py3-none-any.whl#md5=c1af149f5e10491831311f0e32aa7001 (from https://pypi.python.org/simple/click/), version: 2.5
    Found link https://pypi.python.org/packages/6b/ca/8441cb224f040af2a71056b6de5d7bfdfe60c580931f6226587ef7617870/click-2.5.tar.gz#md5=a1bff2d2270745affd5bc60e66e50c23 (from https://pypi.python.org/simple/click/), version: 2.5
    Found link https://pypi.python.org/packages/d1/bc/9afb108a31cb0fd37e6774b23569197aee9974425d9c361a29e3eade9f32/click-2.6-py2.py3-none-any.whl#md5=75941e4e80563ca134fda5045b537c78 (from https://pypi.python.org/simple/click/), version: 2.6
    Found link https://pypi.python.org/packages/fc/92/403b0389319c017d9971570b6fc868e789fba31d96c53799ba726bae6a34/click-2.6.tar.gz#md5=bf5fbaecc1370934347b82ec707e3413 (from https://pypi.python.org/simple/click/), version: 2.6
    Found link https://pypi.python.org/packages/f6/66/65f7bcdcb6ace560cc5d6c4cdbb968bfc8d53f256ba206bf1884e547d786/click-3.0-py2.py3-none-any.whl#md5=13cead4d730cf0184e981bc2b5748248 (from https://pypi.python.org/simple/click/), version: 3.0
    Found link https://pypi.python.org/packages/8d/f7/e4a41b165fbe0a1c52db0cfc1e2f4452fcbdfa240c66fd0300a3acc858b9/click-3.0.tar.gz#md5=6919bcf8dcbe99197893464a97f640d5 (from https://pypi.python.org/simple/click/), version: 3.0
    Found link https://pypi.python.org/packages/a3/8a/7b995e58729456e0ce61cc1ec91b77835da0171e3dcc1283c09212bea2ed/click-3.1-py2.py3-none-any.whl#md5=008bac40c0e11f6be2226a5667b67095 (from https://pypi.python.org/simple/click/), version: 3.1
    Found link https://pypi.python.org/packages/03/7b/4e36fd53099764fa70b5e56f2e089bfd9f433fb8da873326b5d8ee8b1820/click-3.1.tar.gz#md5=6fc0aa839e01ac1d05c4a823c698b6b2 (from https://pypi.python.org/simple/click/), version: 3.1
    Found link https://pypi.python.org/packages/85/e4/a39441e8cd202d5ad4af4e8e97d4c49d59f5ef60368721fab29ec4247240/click-3.2-py2.py3-none-any.whl#md5=7d0bf0ca4e8ce6056e35cc8135d21abd (from https://pypi.python.org/simple/click/), version: 3.2
    Found link https://pypi.python.org/packages/ee/0b/4bb57fb1115590ab62faf8552f3aaa4b9caf18af7b272abc379a31604371/click-3.2.tar.gz#md5=f8a439029337ff39ed814ae5ce948318 (from https://pypi.python.org/simple/click/), version: 3.2
    Found link https://pypi.python.org/packages/b7/21/ce45306a697fc80ebe0b73ce04ecc08c54488b2dbe74babc068959683fd5/click-3.3-py2.py3-none-any.whl#md5=5ca07a6c8b1eaca8e529cdb50a8a8349 (from https://pypi.python.org/simple/click/), version: 3.3
    Found link https://pypi.python.org/packages/15/0f/9070074d2bdabf216f99b922a5c85ef1bfc304236086d3bf77c6b35eacfc/click-3.3.tar.gz#md5=40edaba4d216915a8326c5b2cb52781d (from https://pypi.python.org/simple/click/), version: 3.3
    Found link https://pypi.python.org/packages/0c/d5/9b5cc74d3ac814140c1a0b89534b7d148c5b399b12f69883335d9c5cc622/click-4.0-py2.py3-none-any.whl#md5=c25cb7af50132bbf00eaf3b439815874 (from https://pypi.python.org/simple/click/), version: 4.0
    Found link https://pypi.python.org/packages/7b/61/80731d6bbf0dd05fe2fe9bac02cd7c5e3306f5ee19a9e6b9102b5784cf8c/click-4.0.tar.gz#md5=79b475a1dbd566d8ce7daba5e6c1aaa7 (from https://pypi.python.org/simple/click/), version: 4.0
    Found link https://pypi.python.org/packages/6e/97/f25f4277d90efa3d34ced57137023ecb96e0c9aacf79b4f93efe6d94a2f8/click-4.1-py2.py3-none-any.whl#md5=4c0dca35693367bf63b4290281dfeb2c (from https://pypi.python.org/simple/click/), version: 4.1
    Found link https://pypi.python.org/packages/4c/eb/dc135683e4865bbcba60b09b158bf491756a1c36d0e2820002235bf72a8a/click-4.1.tar.gz#md5=6a3fa88c738f2f775ec6de126feb99a4 (from https://pypi.python.org/simple/click/), version: 4.1
    Found link https://pypi.python.org/packages/af/55/056901e9f504a7cda9e955592360ce2c516b2b92f3da9318ba074be5d280/click-5.0-py2.py3-none-any.whl#md5=ae5a1032fb7e08e73213a847321044c2 (from https://pypi.python.org/simple/click/), version: 5.0
    Found link https://pypi.python.org/packages/3e/4f/e66a06ab731ba91faa60142d4e465fde941104fe9b6d27d1b9548f03ec64/click-5.0.tar.gz#md5=7c91618e3b067319250770d6e1f0f5c7 (from https://pypi.python.org/simple/click/), version: 5.0
    Found link https://pypi.python.org/packages/8f/98/14966b6d772fd5fba1eb3bb34a62a7f736d609572493397cdc5715c14514/click-5.1-py2.py3-none-any.whl#md5=03c35b9dc7332c55f2c202d57fba8394 (from https://pypi.python.org/simple/click/), version: 5.1
    Found link https://pypi.python.org/packages/b7/34/a496632c4fb6c1ee76efedf77bb8d28b29363d839953d95095b12defe791/click-5.1.tar.gz#md5=9c5323008cccfe232a8b161fc8196d41 (from https://pypi.python.org/simple/click/), version: 5.1
    Found link https://pypi.python.org/packages/af/3b/96f97aea83acce065079e31fc7befe9bb188e9
Adding black to Pipfile's [dev-packages]…
Pipfile.lock not found, creating…
Locking [dev-packages] dependencies…
Using pip: -i https://pypi.python.org/simple

                          ROUND 1
Current constraints:
  black

Finding the best candidates:
Using pip: -i https://pypi.python.org/simple

                          ROUND 1
Current constraints:
  black

Finding the best candidates:

Warning: Your dependencies could not be resolved. You likely have a mismatch in your sub-dependencies.
  You can use $ pipenv install --skip-lock to bypass this mechanism, then run $ pipenv graph to inspect the situation.
Could not find a version that matches black
Tried: 18.3a0, 18.3a0, 18.3a1, 18.3a1, 18.3a2, 18.3a2, 18.3a3, 18.3a3, 18.3a4, 18.3a4
Warning: Your dependencies could not be resolved. You likely have a mismatch in your sub-dependencies.
  You can use $ pipenv install --skip-lock to bypass this mechanism, then run $ pipenv graph to inspect the situation.
Could not find a version that matches black
Tried: 18.3a0, 18.3a0, 18.3a1, 18.3a1, 18.3a2, 18.3a2, 18.3a3, 18.3a3, 18.3a4, 18.3a4

Try pipenv lock --pre and make sure you dont have black in both sections of your pipfile

pipenv lock --pre appears to have done the job, thanks.


Add doc style check in precommit

doc style check, via vale, can fail in github, but isn't incorporated in the precommit via the dedicated config file. Is it possible to add it? Can we do this in all repos as appropriate?

Hi @seanpearsonuk I discussed this issue with @mkundu1 and we found that vale is not officially supported by pre-commit yet.
Here is the list of hooks supported by pre-commit. - https://pre-commit.com/hooks.html
We have also found some other ways related to vale on following links -
Installation -
https://vale.sh/docs/vale-cli/installation/
Configuration -
https://vale.sh/generator/
Quick start -
https://vale.sh/docs/vale-cli/structure/#quick-start

Thanks, @hpohekar, @mkundu1. I will close this now.


how to execute flushall/flushdb on codis

you need to execute flushall for every redis directly

i execute flushall on each Master ,done!
Thanks


Allow update by path

Provide an update by path or return a mutable borrow.

Yes. I believe that mutable borrowing can be a usefull thing.

 jsonpath#11

hi @besok.  Love using your library, very nice addition to serde_json.  Any updates on supporting mutable references?

Thank you.
I hope to start working on that issue next week at long last.

that would be fantastic.  Spasibo

After playing around for a bit, I could not find a way to provide an ability to modify the results for the query.
Tbh, even the understanding of the contract is a bit vague.
For instance, we have a list of references at the end where we can have duplicates and making them mutable with refs (&mut) will not really work and bringing smart pointers(custom or RefCell) with internal mutability will expense the runtime. Besides, conceptually, the query ceases to be a search query and turns into a query and transform which goes beyond the initial js path.
I would love to hear the thoughts in general regarding that :).
In a meantime, I suggest the following:
I introduced 2 methods for JsonLike structure:

reference
reference_mut
That can take the direct path (root, field, index) and return the reference to that path of the structure.
The path can be found by using js-path :).  Readme section

#[test]
fn update_by_path_test() -> Result<(), JsonPathParserError> {
    let mut json = json!([
            {"verb": "RUN","distance":[1]},
            {"verb": "TEST"},
            {"verb": "DO NOT RUN"}
        ]);

    let path: Box<JsonPath> =<EMAIL_ADDRESS>== 'RUN')]")?);
    let elem = path
        .find_as_path(&json)
        .get(0)
        .cloned()
        .ok_or(JsonPathParserError::InvalidJsonPath("".to_string()))?;

    if let Some(v) = json
        .reference_mut(elem)?
        .and_then(|v| v.as_object_mut())
        .and_then(|v| v.get_mut("distance"))
        .and_then(|v| v.as_array_mut())
    {
        v.push(json!(2))
    }

    assert_eq!(
        json,
        json!([
                {"verb": "RUN","distance":[1,2]},
                {"verb": "TEST"},
                {"verb": "DO NOT RUN"}
            ])
    );

    Ok(())
}


Browser Use

I would love to know how to make this work for browser / frontend

Hi again! Don't know if you still need this, but I've put the browser JavaScript files in the dist/ folder. Check it out.


warnings during build

Building Scryer Prolog with:
$ cargo build --release

Recently shows warnings:
warning: struct `OrderedOpDirKey` is never constructed
warning: method `unify_big_num` is never used
warning: ambiguous wide pointer comparison, the comparison includes metadata which may not be expected
warning: ambiguous wide pointer comparison, the comparison includes metadata which may not be expected

Anything to worry about?

It seems that the Rust compiler got better at detecting these things. But they were already there, so I won't worry too much


[Activation] Minimal viable rewind data refactor

This is a refactor of coin views to ensure rewind data can be aggregated per block as per #1810
Unit tests will be fixed in a separate PR to make this PR smaller
The approach is as follows:

Construct rewind data list in cache and keep creating rewind data per block.
Once cache is flushed we pass this list to DBreezeCoinView to be persisted.
When rewind is requested, check cache first and if it is available in cache, rewind it from there. Otherwise, attempt to rewind from the DBreezeCoinView.

@dangershony @noescape00 Could you guys please check the logic here, this needs as many eyes as possible

I'll have a look at this tomorrow.

Updated all as per feedback. Need more eyes on it.

great work guys!


Membership agreements on docusign

Add similar locking as used for receipts to ensure email is only sent once

Add feature toggle so we can disable this if someone complains


Add Bitcoin Knots as an additonal app (to replace core)

As requested some people want to see Bitcoin Knots on the RaspiBlitz:
https://x.com/ChrisMartl/status/1820527897028989031
https://x.com/LukeDashjr/status/1820565013725372860
The "dont ask, just do it" way would be to fork RaspiBlitz (KnotsBlitz would be my recommended name) and keep it in sync with RaspiBlitz while only taking care of always replacing Bitcoin Core with Knots in the Bitcoin install scripts:
https://github.com/raspiblitz/raspiblitz/blob/dev/home.admin/config.scripts/bitcoin.install.sh
https://github.com/raspiblitz/raspiblitz/blob/dev/home.admin/config.scripts/bitcoin.update.sh
The more advanced integration would be to add "Bitcoin Knots" as an additional app that will deactivate Bitcoin Core and install/activate Knots as a in-place replacement.
In both solutions make sure that all Ports & CLI stays the same with Knots as it with Core.
This issue is tagged with help wanted because at the moment there is not much capacity within main raspiblitz team to take the lead on this feature request - but if someone like to contribute we are happy to give directions and assist.

Taking care of this one 👍
https://github.com/Retropex/knotsblitz

@Retropex We like to support forks of RaspiBlitz .. if there is anything that makes it easier for you to maintain/keepInSync the KnotsBlitz - let us know

@rootzoll may I ask you if local build worked fine lately, it's probably a misconfiguration on my side but I don't know what to do to fix this:
# Build the image
# Running: packer build  -var branch=knots -var pack=fatpack -var github_user=Retropex build.arm64-rpi.pkr.hcl
???????: Failed to load source type

  on build.arm64-rpi.pkr.hcl line 8:
  (source code not available)

Unknown address type: 0

arm.raspiblitz-arm64-rpi: output will be in this color.

==> Wait completed after 120 microseconds

==> Builds finished but no artifacts were created.
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x28 pc=0xbc1188]

goroutine 114 [running]:
github.com/hashicorp/packer/packer.(*CoreBuild).Run(0xc0006e5560, {0x44371e0, 0xc0000b5380}, {0x443c960?, 0xc000546810})
	github.com/hashicorp/packer/packer/build.go:225 +0x5e8
github.com/hashicorp/packer/command.(*BuildCommand).RunContext.func1()
	github.com/hashicorp/packer/command/build.go:255 +0x1da
created by github.com/hashicorp/packer/command.(*BuildCommand).RunContext
	github.com/hashicorp/packer/command/build.go:246 +0xac5

!!!!!!!!!!!!!!!!!!!!!!!!!!! PACKER CRASH !!!!!!!!!!!!!!!!!!!!!!!!!!!!

Packer crashed! This is always indicative of a bug within Packer.
A crash log has been placed at "crash.log" relative to your current
working directory. It would be immensely helpful if you could please
report the crash with Packer[1] so that we can fix this.

[1]: https://github.com/hashicorp/packer/issues

!!!!!!!!!!!!!!!!!!!!!!!!!!! PACKER CRASH !!!!!!!!!!!!!!!!!!!!!!!!!!!!
make: *** [Makefile:108 : arm64-rpi-fatpack-image] Erreur 1

@openoms can you comment on the packer build?
@Retropex I would recommend building manual for testing & releases - see FAQ here: https://docs.raspiblitz.org/docs/faq/dev#what-is-the-process-of-creating-a-new-raspberrypi-sd-card-image-release-manually

@Retropex see the changes here to fix the local (non-docker) packer run: https://github.com/raspiblitz/raspiblitz/pull/4696/files


Generalized runtime backpressure

This is a first draft of generalized runtime backpressure. A final version would require a changes to TCPConnection and anything else that can become "overloaded" and would need to exert backpressure based on external conditions (such as a slow receiver).

@SeanTAllen Would you consider also adding some variation of https://gist.github.com/slfritchie/0dab74fd729b7ecdd2a11c32c1f984cb?

@slfritchie i think that's reasonable.
do you think coarse grained tracking on the number of times an actor is overloaded or muted would be interesting? (also overloading cleared and unmuted)

@SeanTAllen tl;dr: yes.
DTrace (and presumably SystemTap) permit easy dynamic probes at entry & exit to any function.  This code is structured almost enough dynamic function entry probes could tell you most of what you'd like to know. Overload & not overload have dedicated functions.  But mute & unmute do not.  Muting status changes are buried far inside of ponyint_sched_mute() and ponyint_sched_unmute_senders().
The code could be restructured to give dedicated small functions for the actual mute state changes; then dynamic function entry probes are easy.  However, there's infrastructure value in defining static probes for important events in the system.  These new events are the kinds of thing that affect scheduling, and visibility into scheduling is Good.

Ive found a couple problems with this implementation.

program termination doesnt take into account that there might be muted actors (unscheduled) which will become scheduled again, which can lead to early program termination. the fewer actors running, the more like that is to occur. Really we need to know if there are any muted actors before termination. because if there are, we should keep trying to steal actors rather than exiting that scheduler thread.

the incrementing and decrementing of mute value for an actor isnt thread safe. more than 1 scheduler could try to decrement the mute value at a time. which could result in a data race and FUN. we’d probably want a CAS operation for that OR… what would also solve the issue 1. we need an actor like the cycle detector that handles all muting and unmuting. and can know if there are any “live” muted actors around (in which case a scheduler shouldn’t exit)

@SeanTAllen The first problem can be solved by two small modifications to the workstealing and quiescence detection algorithm.

A scheduler shouldn't send SCHED_BLOCK if the size of its mutemap isn't 0.
When a scheduler is looping in steal and reschedules a previously muted actor as a result of receiving SCHED_UNMUTE_ACTOR, it should resume its normal execution.

Could you detail the circumstances in which the second problem can occur? It seems to me that a given actor can only be in one mutemap at a time.

@Praetonus excellent ideas. and now that I am a little less tired, I realize you are correct about an actor only being able to be in a single mutemap at a time. I need to add comments to that effect.

At the next sync, I'd like to discuss what sort of documentation this might need. Inclusion in the tutorial? On the website? Just notes in the code?

@SeanTAllen Here's the diff containing the changes needed to remove the message chain iteration in ponyint_maybe_mute: https://gist.github.com/Praetonus/e6f9d24d1f88e4d1fbfd97dbdc340fef

@Praetonus patch applied. looking good.

@Praetonus everything we talked about is in place. Sylvan helped me track down a bug.
I have to add the ability for actors to manual indicate they can't make progress so that is included in the backpressure system and perf testing. but this is getting close.
right now "can't make progress" would be a TCPConnection that is unable to send (backpressure for example).

@slfritchie I added the telemetry info. Can you have a look to make sure I did it correctly?

Things I need to do:

[ ] add docs for the Backpressure package
[ ] performance testing using Wallaroo

Please give this another review. It's ready for more feedback.
Question, how, if at all should we document this somewhat advanced feature beyond the package level docs in Backpressure?

I just updated ProcessMonitor to use backpressure mechanism to prevent unbounded pending queue growth. This is a breaking API change to the constructor as a ApplyReleaseBackpressureAuth token is now required.

Ok with the updates to TCPConnection documentation and with the addition of backpressure to ProcessMonitor, it appears to me that any of the "runaway memory growth" actors in the standard library have some sort of backpressure coverage.

There's a problem with work stealing and block messages. At the time a scheduler enters into steal() it might have a muted actor. This will cause it to not send a block message. When that actor is unmuted, it might be stolen by another scheduler, leaving the existing scheduler blocked but looping in steal, without ever being able to exit and without ever having sent a block message.

I added the telemetry info. Can you have a look to make sure I did it correctly?

The change to examples/dtrace/telemetry.d looks fine, @SeanTAllen.

We did performance testing with Wallaroo.
Using our standard testing app under a normal load of 3 million messages a 2nd, we saw no change in latencies. Awesome!

We did performance testing with Wallaroo.
Using our standard testing app under a normal load of 3 million messages a 2nd, we saw no change in latencies. Awesome!

I want to add DTrace probes for when an actor is muted and unmuted. However, there's nothing "magical" about that.  Really there are already probes for that, an actor is UNSCHEDULED when muted and SCHEDULED when unmuted. That would appear to be the correct probes to add for those.
And, then, probes for...

actor is overloaded
actor no longer overload
actor under pressure
actor no longer under pressure

which should be the last addition to this before merging.
@slfritchie @sylvanc @Praetonus @jemc
Do those seem like reasonable plans for probes?

@SeanTAllen The probes added in commit 3b75716 are mostly reasonable.  If I were to qubble, it would be that the new probes are related pairs, but the naming convention of the pairs isn't the same.  One uses 'condition' and 'condition-change' while the other uses 'changeA-condition' and 'condition-changeB'. To find names of probes, DTrace users frequently do queries based on glob-style wildcard matches, e.g., dtrace -ln 'pony$target:::condition*'.  A consistent naming convention makes it easier to craft helpful glob patterns.
A quick fix: the change the names of the new pressure probes to be 'actor-pressure' and 'actor-pressure-released'.   A bigger change: change the probes to be simply 'condition' and also add an argument of 0=condition off or 1=condition on.

I'm ready for this be squashed and merged if everyone wants to sign off.
@slfritchie I'm going to leave DTrace as is now. I think it would be better to come back and revisit all the DTrace probes and make sure there is a consistent scheme for how to do things (then make those changes and document). If you feel like taking that on, let me know.

@jemc @Praetonus @mfelsche @sylvanc i added comments and did some clean up. please have a look. where should there be additional explanation, comments etc.

Latest perf testing round looks good. On the cleanup and blog post etc.

I'm planning on squashing and merging this today. Here's the planned commit comment. Anything else that should be included? If no, I'll get this merged down then start working on a blog post that would announce the feature.

This commit has backpressure to Pony runtime scheduling.
Prior to this commit, it was possible to create Pony programs that would be able to cause runaway memory growth due to a producer/consumer imbalance in message sending. There are a variety of actor topologies that could cause the problem.
Because Pony actor queues are unbounded, runaway memory growth is possible. This commit contains a program that demonstrates this. examples/overload has a large number of actors sending to a single actor. Under the original scheduler algo, each of these actors would receive a fairly equivalent number of chances to process messages. For each time an actor is given access to the scheduler, it is allowed to process up to batch size number of messages. The default for batch size is 100. The overload example many many actors sending to a single actor where it can't keep up with the send.
This commit adjusts the Pony scheduler to apply backpressure. The basic idea is:
1- Pony message queues are unbounded
2- Memory can grow without end if an actor isn't able to keep up with the incoming messages
3- We need a way to detect if an actor is overloaded and if it is, apply backpressure
With this commit, we apply backpressure according to the following rules:
1- If an actor processes batch size application messages then it is overloaded. It wasn't able to drain its message queue during a scheduler run.
2- Sending to an overloaded actor will result in the sender being "muted"
3- Muting means that an actor won't be scheduled for a period of time allowing overloaded actors to catch up
Particular details on this
1- Sending to an overloaded or muted actor will result in the sender being muted unless the sender is overloaded.
2- Muted actors will remain unscheduled until any actors that they sent to that were muted/overloaded are no longer muted/overloaded
With this commit, the basics of backpressure are in place. Still to come:
backpressure isn't currently applied from the cycle detector so its queue can still grow in an unbounded fashion. More work/thought needs to go into addressing that problem.
Its possible that due to implementation bugs that this commit results in deadlocks for some actor topologies. I found a number of implementation issues that had to be fixed after my first pass. The basic algo though should be fine.
There are a number of additional work items that could be added on to the basic scheme. Some might turn out to be actual improvements, some might turn out to not make sense.
1- Allow for notification of senders when they send to a muted/overloaded actor. This would allow application level decisions on possible load shedding or other means to address the underlying imbalance.
2- Allow an actor to know that it has become overloaded so it can take application level
3- Allow actors to have different batch sizes that might result in better performance for some actor topologies
This work was performance tested at Wallaroo Labs and was found under heavy loads to have no noticeable impact on performance.

Excellent! :+1:
One small typo I noticed in the first line: I think "has" should be "adds".


I can't discovery service in kubernets with loadbanlace?

when I use the reactiveFeign request the service ,the discovery doesn't build full ,the reactiveFeign just build mapping url,the service ip(ip:port) doesn,t build in the full url. how can i do that can let it work in kubernets environment?
the dependencies

the reactiveFeign code

the main application

If you use @EnableDiscoveryClient annotation so you rely on discovery service. You should omit url parameter in @ReactiveFeignClient. Actual url will be resolved by service name from name parameter

thanks for ur answer. i have removed the url parameter ,but it likes cann't work discovery any service and threw a exception like this:

You need to configure ribbon correctly


Create wheels.js

Don't merge yet obviously, Idk you guys' economy functions so replace mine with them, to find them just search in ctrl + f Economy and Db nothingelse is reliant on my economy in there

Don't merge yet obviously, Idk you guys' economy functions so replace mine with them
dude, that's your job lol
Also, if you need to correct something, amend/squash your commits(s)

Aight, I guess this should be fine, but you still need to do two things:

Indent your code with tabs and not spaces
Squash your commits into one

In the future, syntax check your code using http://esprima.org/demo/validate.html
Or even better, test every update of yours :P

doing just /animal makes the help command show up twice

Merged in be7cbd532aed28afc27408cd4efaa1d8dd7d01bb


Re-rendering a component within an SVG fails to apply some attributes

... due to the isSvgMode flag never getting set.

/cc @billneff79


[update] update the Kubernetes version of the GKE templates

Since the new stable version of Rancher is 2.8.2, you can update the K8s version of GKE by following the Support Matrix.
Ref. ->
Rancher version: https://github.com/rancher/rancher?tab=readme-ov-file#latest-release
Rancher Support Matrix: https://www.suse.com/suse-rancher/support-matrix/all-supported-versions/rancher-v2-8-2/
GKE (K8s) version: https://cloud.google.com/kubernetes-engine/docs/release-notes
cc @dnoland1

Done with #138


[SPARK-35478][PYTHON] Enable disallow_untyped_defs mypy check for pyspark.pandas.window.

What changes were proposed in this pull request?

Adds more type annotations in the file python/pyspark/pandas/window.py and fixes the mypy check failures.
Why are the changes needed?

We should enable more disallow_untyped_defs mypy checks.
Does this PR introduce any user-facing change?

Yes.
This PR adds more type annotations in pandas APIs on the Spark module, which can impact interaction with development tools for users.
How was this patch tested?

The mypy check with a new configuration and existing tests should pass.

Could you update mypy.ini as well?

Can one of the admins verify this patch?

ok to test

Test build #139718 has started for PR 32886 at commit 5b3ab15.

Can one of the admins verify this patch?

Test build #139718 has finished for PR 32886 at commit 5b3ab15.

This patch fails Python style tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/139718/

Kubernetes integration test unable to build dist.
exiting with code: 1
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/44233/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/44233/

Can one of the admins verify this patch?

Test build #139729 has started for PR 32886 at commit 5d73782.

Test build #139729 has finished for PR 32886 at commit 5d73782.

This patch fails Python style tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/139729/

Test build #139730 has started for PR 32886 at commit 78b8de4.

Test build #139730 has finished for PR 32886 at commit 78b8de4.

This patch fails Python style tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/139730/

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/44255/

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/44254/

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/44255/

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/44254/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/44254/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/44255/

Can one of the admins verify this patch?

@ueshin Thanks for the review. I've updated the PR.

ok to test

Test build #139981 has started for PR 32886 at commit be0df23.

Test build #139981 has finished for PR 32886 at commit be0df23.

This patch fails Python style tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/139981/

@ueshin Thanks for the review.
And sorry to update so late. I was in the army a couple days ago.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/44508/

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/44508/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/44508/

Thanks! merging to master.

Sorry, I missed the Jenkins' linter failure before merging. I submitted a PR to fix it #32965.

Sorry, I didn't notice Jenkin's linter failure. I'll pay attention next time


"done" should fail when called multiple times

I did some online searching and didn't find any discussion, so let me know if this is as expected. Happy to do a PR if this should be correct behavior
🐛 Bug Report
Calling done() multiple times in one test should be a failure, but it succeeds
To Reproduce
it('should fail when done called second time', done => {
  done();
  done();
});

Expected behavior
Test fails with "done" called multiple times or some such message
Link to repl or repo (highly encouraged)
Above code snippet showcases issue. Looks like following test could be added to e2e failures:
test('done();done()', done => {
  done();
  done();
});

Run npx envinfo --preset jest
Paste the results here:
  System:
    OS: macOS High Sierra 10.13.6
    CPU: x64 Intel(R) Core(TM) i5-5287U CPU @ 2.90GHz
  Binaries:
    Node: 10.3.0 - /usr/local/bin/node
    Yarn: 1.5.1 - /usr/local/bin/yarn
    npm: 6.1.0 - /usr/local/bin/npm

I agree this should fail. Wanna send a PR for it? 😀

Hey, I'd like to take this up. Don't have enough context as it is though. From what I understand, this will have to be updated in both circus and jasmine(Env.js?). Could you give me a place to start?

Circus: https://github.com/facebook/jest/blob/e2dac2ba04bd0655d7f81a02907375429746c05a/packages/jest-circus/src/utils.js#L180-L196
Jasmine: https://github.com/facebook/jest/blob/e2dac2ba04bd0655d7f81a02907375429746c05a/packages/jest-jasmine2/src/jasmine/Env.js#L549-L561
I'm personally fine fixing this just in Circus, but if both are easy, go for it 🙂

The code for circus looks like something I can work with. The one for jasmine don't I don't quite grok. I don't see where the callback is provided. Basically what I plan on doing is to wrap done in a higher order function which increments a variable for done being called more than once. If it's called more than once then we mark the test as a fail.

Hello, me and another student are trying to fix this issue for a course in college. However, it's our first time working with jest so we are not so sure which files to run to reproduce this issue... Can you please replicate it in repl.it?

Hey @jmcsilva98, really happy to hear that!
Here's a repl.it, if you run this then the test passes but the OP requests that we fail it. The message could be something like "Expected done to be called once but it was called multiple times"
Here is a good place to start looking to add the feature. Note that this is the jest-circus runner so you should follow these instructions to run
Finally, here are some instructions on how to setup jest locally as well. If you have any issues or troubles, feel free to reach out to me on twitter or the reactiflux discord and I'd be happy to help!

May I give this a shot?

That would be great, thanks!


[Tests] Add tests for SchedulerImpl

Also moves the mock task.Service to a shared location for testing.

Codecov Report

Merging #6 into master will increase coverage by 1.68%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master       #6      +/-   ##
==========================================
+ Coverage   77.38%   79.06%   +1.68%
==========================================
  Files          18       18
  Lines        1110     1137      +27
==========================================
+ Hits          859      899      +40
+ Misses        192      178      -14
- Partials       59       60       +1

Impacted Files
Coverage Δ

internal/domain/task/recurring/manager.go
76.84% <ø> (ø)
:arrow_up:

internal/infra/cron/task/recurring/scheduler.go
79.71% <0%> (ø)

internal/domain/task/recurring/mock_service.go

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 df2a385...8aa4f77. Read the comment docs.


Update components.md

Description

Updated the Creating your own section of the documentation on customizing bootstrap components.
Motivation & Context

The intent is to make it clearer to the reader that:

Callouts are custom components created by the bootstrap team for use in documentation;
Callouts aren't part of and are not provided by core bootstrap

Type of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[x] Refactoring (non-breaking change)
[ ] Breaking change (fix or feature that would change existing functionality)

Checklist

[x] I have read the contributing guidelines
[x] My code follows the code style of the project (using npm run lint)
[x] My change introduces changes to the documentation
[x] I have updated the documentation accordingly
[ ] I have added tests to cover my changes
[ ] All new and existing tests passed

Live previews

https://github.com/github-user-en/bootstrap/blob/main/site/content/docs/5.3/customize/components.md#creating-your-own

Related issues

Hey, thanks for your contribution.
I think it doesn't bring much to the documentation and it doesn't seem to be ask by much people neither.
The actual is rather clear since we don't present callouts, it's only an example if people want to dig more into the our code principles.


Unbounded subresource range

Fixes #3200
I've only updated the GL and Vulkan backends, since those are the only ones I have access to.
PR checklist:

[X] make succeeds (on *nix)
[X] make reftests succeeds
[X] tested examples with the following backends: GL, Vulkan

Alright, I've spent quite a bit of time converting this (pushing to this PR), and I have opinions now.
First and foremost, it turns out that Vulkan does require the exact layer count for SubresourceLayers. That means, only SubresourceRanges has this semantic of "remaining" stuff, and it's only used in a couple of places (notably, image creation and barriers).
Secondly, wgpu doesn't care about this, since it has to know and validate all the ranges anyway.
And direct users of the API unlikely care either. So this is more or less a "nice to have" thing rather than necessity.
As a result, I'm thinking of just redoing this from the ground up, again, in a separate PR.
Sorry for dragging you @GabrielMajeri into this, your help is still hugely appreciated!
This issue though I'll have to take care myself, since it requires building on all platforms.

It wasn't wasted time, since we learned about how we should redesign this API in the future 🙂


for some reason it won't let me activate the plugin

any idea if i did something wrong?

Are you using the correct Godot version? For godot-voip 3.0 Godot 3.2.4 is required because it uses a new feature which is only available in that version.

If you were using 3.2.3 since 3.2.4 is still unstable and if it works fine thank you and excuse the inconvenience

If you want to use Godot 3.2.3 you can still use godot-voip version 2.0


Tensor interpolate nearest mode

did this before in onnx heh

Can you remove the logic from onnx and reuse the new stuff in Tensor?

I rewrote the resize op.
The implementation before was just horribly hacked. I don't even know how tests passed looking back...
The resize op does not directly call Tensor.interpolate because the _apply_coordinate_function has a bunch of transformations that is different from the modes for Tensor.interpolate. (Tensor.interpolate assumes a specific mode in apply_coordinate_function)
I just copied the impl of Tensor.interpolate over to onnx resize.
for test/external/external_test_image_resize.py I wrote some random tests for fun cuz I was curious how bad the actual discrepancies were
currently our nearest and nearest-exact modes perfectly match torch.interpolate.
torch.interpolate's nearest-exact does not exactly match PIL's NEAREST. (around 1% to 5% of mismatched elements)
torch.interpolate's nearest does not match PIL's NEAREST at all. (over 50% mismatched elements)
I'm not too sure what to think of this. Should we try to match PIL's NEAREST exactly?

ok #6209 had an effect on linear interpolation
I'm prettttyyy sure it's cuz of this line
before: data0[alu0] = ((float)(acc0)+((float)((val2+(-acc0)))*val1));
now: data0[alu0] = ((float)(acc0)+((float)((val2+(acc0*((unsigned char)(-1)))))*val1));
this is cuz the acc0 is neg-ed, and that (unsigned char)(-1) wraps around to 255 so now it becomes val2 + (acc0 * 255) instead of val2 - acc0
gonna see if there's a principled way of fixing this.


Question: Flyout within/over ContentDialog

If you create a ContentDialog that contains controls which are capable of displaying Flyouts, there is this weird behavior where the Flyout is affected by the ContentDialog. Where the two items overlap, the Flyout becomes shaded. (In the image below, the HotPink area and the default Flyout background become shaded.) This same behavior can be witnessed with Popups. Is there a way to make this not happen, or is this a bug? I tried fiddling with the background colors for the default ContentDialog template and it didn't seem to have an effect.

(I know one of the devs thinks this is a use case per this comment on another issue: https://github.com/microsoft/microsoft-ui-xaml/issues/2461#issuecomment-629865558   It just doesn't seem to be working properly out of the box.)
Targeting 1903. Easily reproducible in a blank UWP project by newing up a ContentDialog and then triggering the display of a Flyout/Popup inside of it.

This seems to be an issue that is reproducible in Windows 10 release 1909 but not Windows 10 release 2004 (H1). I guess the fix is to require users to update...

Re-opening this question because upgrading to Windows 10 release 2004 fixed it for some people but not others. This misbehavior seems to be tied to display/visual ease of access settings for some users, but they don't seem to have an effect on my computer.

@codendone or @gegao This looks like a shadows bug, do either of you have an idea what might be happening?

The only potential user difference should be if shadows are fully disabled for the user.  The only known issue here was fixed in 2004.
@DmitriyKomin for any additional thoughts.


Create docs page on Highly Available mode

Right now the only refernce to HA mode is https://docs.dapr.io/getting-started/install-dapr-kubernetes/#install-in-highly-available-mode
There should be a dedicated page to describe the feature, how it works, and how to enable it on difference platforms.

@yaron2 @msfussell is HA mode just for Kubernetes?

Yes, HA mode is only for K8s.

@msfussell

This command creates three replicas of each control plane pod for an HA deployment (with the exception of the Placement pod) in the dapr-system namespace.

Is there anything else that HA mode does that should be documented?
And what is our recommendation? Should all production deployments have HA mode enabled? What's a scenario where you don't want it enabled?
And more for my benefit, why isn't HA mode always enabled on Kubernetes? What's the tradeoff that's being made?