Fix ETCD certificates path for calico service.

The path was change at some point and didn't notice it. Fixed.

Current coverage is 56.90% (diff: 100%)

Merging #39 into master will not change coverage

@@             master        #39   diff @@
==========================================
  Files             4          4
  Lines           949        949
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
  Hits            540        540
  Misses          329        329
  Partials         80         80

Powered by Codecov. Last update 6255751...999ae5a


Prevent spurious warnings  on attempting access to child axis of text() or attributes

From Sebastian Rahtz
I am reading iso_schematron_skeleton_for_saxon.xsl, with lots of DPC good bits.
My problem is that when we have rules which match text() or attributes, we get
fake warnings like:
     [xslt] /Users/rahtz/TEI/Sourceforge/trunk/P5/Exemplars/tei_jtei.xsl:1605: Warning! The child axis starting at an attribute node will never select anything

from a generated “apply-template select=‘*’”
My crude fix is below, if you’re interested. I can’t really tell whether this code is maintained somewhere formal?
--- ../Utilities/iso_schematron_skeleton_for_saxon.xsl  (revision 13161)
+++ ../Utilities/iso_schematron_skeleton_for_saxon.xsl  (working copy)
@@ -1638,11 +1638,20 @@
<xsl:with-param name="subject" select="@subject" />
</xsl:call-template>

                  <xsl:apply-templates/>

                  <!-- DPC introduce context-xpath and select-contexts variables -->

                  <xsl:if test="not($select-contexts)">

                    <axsl:apply-templates select="{$context-xpath}" mode="M{count(../preceding-sibling::*)}"/>

                    <xsl:apply-templates/>

                    <!-- DPC introduce context-xpath and select-contexts variables -->

                    <xsl:if test="not($select-contexts)">

                      <xsl:choose>

                      <xsl:when

                          test="starts-with(@context,'text(')"/>

                      <xsl:when

                          test="starts-with(@context,'@')"/>

                      <xsl:otherwise>

                        <axsl:apply-templates

                            select="{$context-xpath}"

                        mode="M{count(../preceding-sibling::*)}"/>

                      </xsl:otherwise>

                      </xsl:choose>
                  </xsl:if>
          </axsl:template>

A note Rick made perhaps relating to this:
At end of handling PATTERN  has
xsl:commentHousekeeping: SAXON warns if attempting to find the attribute of an attribute</xsl:comment>
          <axsl:when test="not(@*)">

but   @* will not test if current node is attribute (or /).
So this should be   (self::*)  because an element is the only thing that can recurse.

N.b. I have complained in the past to Saxonica that they generate spurious warning messages. It is maddening. But SAXON is a great product.


Fetch public IP without aws-lib.

AWS provides metadata about each EC2 instance at
http://<IP_ADDRESS>/latest/meta-data.  By making use of this metadata,
licode no longer requires AWS credentials.

Thanks for the submission! We're closing old PRs, we've set up a new mechanism to test each PR, and most of these ones have conflicts with master. Feel free to open an issue or submit a new PR again!
Sorry for the inconvenience.


Make TestAsyncOperationResultLog more robust

This PR improves the robustness of some tests. Essentially, they were asserting that a set of logs contained some desired output but if extra output was added... Like I did inadvertently in this PR that we merged and reverted.
Luckily we caught this accidentally before it made it to prod and this is the only instance of this pattern I could find.

/azp run ci

/azp run e2e


[dv,top_level] Fix chip_sw_power_idle_load

Disables alert_handler outgoing alert pings, since they cause the ping response to be confused for an outgoing alert. This workaround can be removed when #23644 is fixed.
Fixes #23570

Re. CI failures: The test failure is unrelated, and the countermeasure failure for englishbreakfast is unrelated, and there is a pending fix for it in https://github.com/lowRISC/opentitan/pull/23650. Merging this.


aj-417 enable automatic container scanning

For AJ-417:
This pull request enables the container scanning API to automatically scan containers for import service.

There are no checks in this repo. Is it on purpose?


Replaced all occurrences of "export_all" with explicit export lists.

Compilation fails when compiling Yaws with the latest Erlang/OTP
master branch (Version 20) with the following error message:
compile: warnings being treated as errors
<file>.erl:<line number>: export_all flag enabled - all functions
will be exported

The above problem can be fixed with this patch.

This is quite boring to explicitly export functions in the testsuite modules. Because it is harder to write tests this way. Instead, we can just inhibit the warning for the whole testsuite. Could you confirm that the following patch do the trick ?
diff --git a/testsuite/Makefile.am b/testsuite/Makefile.am
index b89a3bf..7b484f5 100644
--- a/testsuite/Makefile.am
+++ b/testsuite/Makefile.am
@@ -17,7 +17,7 @@ EBIN_FILES=$(MODULES:%.erl=$(EBIN_DIR)/%.beam)

 LOG_DIR=@builddir@/logs

-ERLC_FLAGS = $(ERLC_GENERIC_FLAGS) -DSHOW_LOG
+ERLC_FLAGS = $(ERLC_GENERIC_FLAGS) -DSHOW_LOG +nowarn_export_all

 include<EMAIL_ADDRESS>

Sure, I'm on it.

These two files also need to be adjusted:
www/code/myappmod.erl
www/shoppingcart/shopcart.erl

Shall we use the +nowarn_export_all flag or an explicit export list?

Good catch. There is also some modules in mail and wiki applications. But for all these ones, I think, an explicit export of all public functions is the best choice. I'll try to push the fix very soon. Many thanks.

Cheers!


[Pipeline] Integrate with self-signed-certificate GitLab

Hello,
I'm testing rancher 2.1 with gitlab . I have set an application on gitlab.
Now I try to configure the pipeline on rancher I put the application id , the secret , I'm using a private  gitlab the problem con from the certificat I'm using a self signed certificat.
I have this error "Post https://gitlab.mlkain.org/oauth/token: x509: certificate signed by unknown authority" and nothing happen after that .
How can I fixed this .

To support integration with Gitlab instances that use self-signed certificates.

The certificate needs to be validated by rancher server, which can be done following the instruction
Git client in user clusters need to validate the certificate. The Clone stage is not customizable at the moment so there's some todo work.
It would be nice if we can have options to skip ssl verify, install custom ca certificate for cloning, etc.

Do you have a work around ? or for the moment there is nothing to do for skip the ssl for git

@modogo2000 Sorry, there's no workaround at the moment, for testing you may try to connect gitlab using HTTP.

Another circumstance is that there could be a legacy jenkins which is used to build jar, tar, etc,. To smoothly migrate to kubernetes, using rancher pipeline to build docker image and auto deploy could be an awesome choice, but now first stage of pipeline is fixed with Clone, which limits the usage.
It's impossible to tell project manager disposing their current CI and doing all the stuff on rancher~

I can get past the first issue by launching rancher-server with bind mounted certs in /etc/rancher/ssl putting a cert.pem and key.pem and a cacerts.pem
But when I go to authenticate the gitlab server sends back (after a popup that I click authorize on the gitlab server)  400 Bad Request Response.  400 No required SSL certificate was sent.  Meaning the gitlab server is expecting to be sent a client cert to HTTPS.   Can the Gitlab outgoing send client certs?

@gitlawr - Is there a timeline for when there will be customization options to add a ca-cert, private/public key combination to the cloning config?

I also strongly hope that clone stage can use ssh instead of user name and token.
I'm using a private gitlab server, and admin only allow git clone via ssh.
See issue 16504

Same here, but for GitHub Enterprise.

@loganhz  @gitlawr I merged the rancher/rancher PR but I had some questions on the "support additional ca certs" PR


Add export to file feature

Hi Tantan, just wanna say i love your idea. I've been wanting to dip my hand into rust for a while now and after watching your vid i thought this is a good chance for me to do so. I'm still new to rust so i hope i implemented the feature correctly.
Preview:

Steps:

In Command mode press colon : to enter CommandInput mode,
In CommandInput mode press W then enter the path,
Press enter to save the image.

I'm using image crate to encode the image.
ggez does provide encoding feature but only png format is currently supported so i choose image crate instead since it's support more formats.
I've only tested it on linux (Pop_OS 20.04) so i don't know if it'll work on windows or mac.
And also sorry, i butchered your code.

Bug: Entering an invalid output filename; e.g. no filename suffix ("outfile"), filename only suffix (".png"), yields a 0-byte output file.
Bug: InputVisualizer "Save Image:" prefix doesn't clear when the filename prompt is exited without entry.
Comment: Errors seem to be printed to stdout.
Huh: Exporting a file with a .jpeg or .jpg suffix appears to actually work. Verified with file headers: .png (89 50 4E 47) and jpg/jpeg (FF D8 FF E0).
NBD/nitpick: Some of your commits overwrite each other.

For the filename bug, i'll add validation for it.
Prefix bug, will fix it.
Printing the error to stdout was intentional to help with debug/test, should i remove it?
I've tested it with .png .jpg/.jpeg .gif and .bmp, here's the list of formats according to image crate.
I'll try to make cleaner commits.

@rainqubit: how's it coming? I'm a test engineer by trade, and have swung along the Git-ropes with some strict developers. So, maybe I don't need to slam the ruler so hard on the desk (so to speak). @TanTanDev is the ultimate yea-er or nay-er.

Ah sorry, i haven't been able to get around and make the changes due to irl circumstances, i'll push the changes as soon as i can and it's ok if you're strict with me since i like to learn the best practices :)

Sorry for taking such a long time to check this out, I've been working on many different projects, but got inspiration to finally check this pull request out.
As you saw I changed the input to go into CommandInput to 'C' from 'Colon' because it doesn't work on windows.
Thanks a bunch guys!

Sorry for taking such a long time to check this out, I've been working on many different projects, but got inspiration to finally check this pull request out.
As you saw I changed the input to go into CommandInput to 'C' from 'Colon' because it doesn't work on windows.
Thanks a bunch guys!


METRON-2309 Add a Kafka "metadata.broker.list" for each log writer filter.

Hi,
in examples 4-5 in readme.md file it seems like you can set a different kafka broker list for each different bro filter, as in:
local http_filter: Log::Filter = [
$name = "kafka-http",
$writer = Log::WRITER_KAFKAWRITER,
$config = table(
["metadata.broker.list"] = "localhost:9092"
),
$path = "http"
];
However, looking at the code here, this is the case only for the topic_name. I fixed this.
Mauro

Just a quick follow-up. I run the tests on the master branch (without the changes iin this PR) and got errors:
vi zkg.test_command.stderr
kafka.l2s-l2e-no-overlap ... ok
kafka.l2s-set-l2e-set ... ok
kafka.l2s-set-l2e-unset ... ok
kafka.l2s-unset-l2e-set ... ok
kafka.l2s-unset-l2e-unset ... ok
kafka.resolved-topic-config ... ok
kafka.resolved-topic-default ... ok
kafka.resolved-topic-override-and-config ... failed
% 'bro -r ../../../tests/pcaps/exercise-traffic.pcap ../../../scripts/Apache/Kafka/ /home/aramis/.zkg/testing/metron-bro-plugin-kafka/clones/metron-bro-plugin-kafka/tests/.tmp/kafka.resolved-topic-override-and-config/resolved-topic-override-and-config.bro > output' failed unexpectedly (exit code 139)
% cat .stderr
1258531693.825212 conn/Log::WRITER_KAFKAWRITER: Debug is turned off.
1258531693.825212 kafka_xxx/Log::WRITER_KAFKAWRITER: Debug is turned off.
Segmentation fault (core dumped)
kafka.resolved-topic-override-only ... failed
% 'bro -r ../../../tests/pcaps/exercise-traffic.pcap ../../../scripts/Apache/Kafka/ /home/aramis/.zkg/testing/metron-bro-plugin-kafka/clones/metron-bro-plugin-kafka/tests/.tmp/kafka.resolved-topic-override-only/resolved-topic-override-only.bro > output' failed unexpectedly (exit code 139)
% cat .stderr
1258531680.237254 kafka_xxx/Log::WRITER_KAFKAWRITER: Debug is turned off.
Segmentation fault (core dumped)
kafka.send-all-active-logs-l2e-set ... ok
kafka.send-all-active-logs-l2e-unset ... ok
kafka.send-all-active-logs-l2s-set-l2e-set ... ok
kafka.send-all-active-logs-l2s-set-l2e-unset ... ok
kafka.show-plugin ... ok
2 of 14 tests failed
Not sure what is going on here. Maybe there is something wrong in my setup, but I have been running an older version of this plugin without any problem for quite a while...

I @mauropalumbo75 thanks for the contribution!  I haven't had a chance to take a look at it, but to answer your testing question I would recommend you run docker/run_end_to_end.sh to identify if there are any issues.

Hi @mauropalumbo75 thanks again for the contribution.  Can you rebase this on master and see if the e2e tests pass?  It should include the btests within Docker to take your local environment out of the equation.
After the rebase you should be able to cd Docker/; ./run_end_to_end.sh and let it churn for a while to see if it works.  It won't test multiple brokers, but that's something we are working towards with the move to docker-compose for e2e tests.

@mauropalumbo75 the issue you were seeing was fixed as of 587e9da and I just confirmed that everything is now passing on this branch.
I would love to get this in - can you please add some tests for the new logic?

Also please align the title of the PR exactly with your JIRA

As much as I would love to get this in, I have to mark it as abandoned.  I'll be closing this soon if there's no response


Add BROKEN_DELIMINATOR issue

See https://github.com/Sp2000/colplus-backend/issues/609#issuecomment-572730183

CSV rows with less columns are skipped, so there is no verbatim record to attach an issue to.
The logs contain all skipped lines for imports.
To get a better handle on these usually very bad frameshift problems we could:

A) attach an issue to the previous and/or next record as they are usually effected too
B) keep the number of skipped & broken CSV records in the import statistics, plus maybe some 10 or so example line numbers where the problem is found. The frontend could integrate these with the other issue but make them not clickable (there is not verbatim record to show)

I think those approaches make sense, especially A since it would show up in the GSD issue matrix, making it easier to keep an eye out for broken delimination catalogue-wide.

I will add an issue PREVIOUS_LINE_SKIPPED to the following record.
We could also mark all records that have more columns then the first row.


Refactor code not to use div_num as part of creating DOM IDs on the fly.

Do not use nor reference div_num when rendering flash_msg partial view

@GregP : looking at these PRs I see you are changing only one side. Only the flash rendering.
That would mean that the flash messages either did not work until then or would not work after this PR.
To have this properly fixed, you need to make sure that the original flash div (before any flash message is displayed) has the proper ID.
Can you point me to the related flash div in each of the PRs so that I can review that this is correct?

Here's a nice explanation (page 232)
https://books.google.cz/books?id=DmUlcuWkajAC&pg=PA233&lpg=PA233&dq=replace+replace_html+tutorial+ruby&source=bl&ots=gMbJGyRlBe&sig=1yQrl2gfgjkKP8QNJAPZBY9e1CE&hl=cs&sa=X&ved=0ahUKEwiy8cyb6oHPAhWHXBoKHShSByY4ChDoAQgqMAI#v=onepage&q=replace replace_html tutorial ruby&f=false

@martinpovolny Not changing anything in code save for getting rid of div_num when rendering the flash_msg partial. So, instead of trying to force DOM ID to use this div_num as part of a dynamic div name generation we'll just use what's already in the flash_msg HTML code for div name. flash_msg partial will now default to "", Line 2 in code, and once all references to div_num are eliminated we can get rid of div_num in the flash_msg partial itself.
As is, flash_msg partial does have a proper div id flash_msg_div.

@GregP : So now the flash message does not display and after this PR it does?
Either that or vice versa so which is the case?


Add method to replicate https://cogeotiff.github.io/rio-tiler/advanced/feature/

Reading a file for a specific feature seems a bit more natural than using a bbox for some users
We have a way of doing this using cutline
from rio_tiler.io import COGReader
from rio_tiler.utils import create_cutline
from rasterio.features import bounds as featureBounds

feat =     {
    "type": "Feature",
    "properties": {},
    "geometry": {
    "type": "Polygon",
    "coordinates": [
        [
        [-52.6025390625, 73.86761239709705],
        [-52.6025390625, 73.59679245247814],
        [-51.591796875, 73.60299628304274],
        [-51.591796875, 73.90420357134279],
        [-52.4267578125, 74.0437225981325],
        [-52.6025390625, 73.86761239709705]
        ]
    ]
    }
}

# Get BBOX of the polygon
bbox = featureBounds(feat)

# Use COGReader to open and read the dataset
with COGReader("my_tif.tif") as cog:
    # Create WTT Cutline
    cutline = create_cutline(cog.dataset, feat, geometry_crs="epsg:4326")

    # Read part of the data (bbox) and use the cutline to mask the data
    data, mask = cog.part(bbox, vrt_options={'cutline': cutline})

but it will be nicer if we could directly pass the feature to a method (or to the part() method)
from rio_tiler.io import COGReader

feat =     {
    "type": "Feature",
    "properties": {},
    "geometry": {
    "type": "Polygon",
    "coordinates": [
        [
        [-52.6025390625, 73.86761239709705],
        [-52.6025390625, 73.59679245247814],
        [-51.591796875, 73.60299628304274],
        [-51.591796875, 73.90420357134279],
        [-52.4267578125, 74.0437225981325],
        [-52.6025390625, 73.86761239709705]
        ]
    ]
    }
}

with COGReader("my_tif.tif") as cog:
    data, mask = cog.part(None, feature=feat)

I feel like it might be better to define a separate method for this, instead of overloading part. Maybe cog.feature or something

@kylebarron I agree, at first I didn't like feature... but we do have tile() so having a feature method that returns data for features make sense ;-)

Well I'm not sure I like feature either, because it doesn't return a feature, it returns data corresponding to feature input

well tile doesn't return a tile ... it retunrs a data for a tile index input 🤷♂

Yeah I guess you're right


update references to st2web and st2flow

Updates some references to st2web and st2flow in the README

thanks @nmaludy
I get this:


Support for diagnostic

I saw a PR for cordova-diagnostic-plugin integration, but i don't see it in the docs, how can i use it?

Any word on this? Apparently someone already committed this on Jan 15 2016 but it was never merged.

Still waiting for the  OP (or anyone else that wants to) to actually base it off of dev-next and issue a PR against dev-next. https://github.com/driftyco/ng-cordova/pull/993

Too bad this isn't added yet?

@datnordstrom You can always take the time to make the changes in an up-to-date fork of dev-next and submit a PR. That'll help it get accepted faster.


Issues in globalEdgeMotion

If the code is not modified, globalEdgeMotion only supports the shape of input frames (M, N).
In function canny(frame), line 31 of skvideo/utils/edge.py
M, N = frame.shape
In function globalEdgeMotion(frame1, frame2, r=6, method='hamming'), line 64-72 of skvideo/motion/gme.py, e.g.,
E_1=canny(frame1)

Ah, I see. The input to that function should be standardized. There is a function that does this, called vshape, which should be used.

@beyondmetis So as you said, the following codes should be added before line 64 in gme.py
frame1 = vshape(frame1)
frame2 = vshape(frame2)
if frame1.shape[3] == 3:
    frame1 = rgb2gray(frame1)
if frame2.shape[3] == 3:
    frame2 = rgb2gray(frame2)
frame1 = frame1[0, ..., 0]
frame2 = frame2[0, ..., 0]

@beyondmetis I suggest using mae instead of using mad as the name of mean absolute error (MAE). This is to avoid mixing up mean absolute deviation and most apparent distortion, which use the same abbreviation "MAD" and they are both FR measures.

If you look at the unit test for msssim, you can see that we pad the reference and distorted videos with zeros before computing the measure. The test dataset is intended to be small for only testing purposes.
I left a couple comments on the pull request regarding the rgb2gray and MAD suggestions.
Thank you for your contributions and interest in improving this package!


Chinese translation is completed.

You can add it any time.
Thank you for making a great browser.

Thank you for your cooperation!
Sorry, some translations in Google Play store was not enough. So I added it to zanata.

Thank you again!


♻ (navigation) cmdk, mobile, navigation

Attempt to bubble up one Navigation Data Element that can be used across the board for:

Command Menu (cmdk)
Mobile Menu (Sheet)
Navigation Menu (Desktop)

Commits:

[x] 🚧 (cmdk) prep for menu refactor
[x] ♻ (cmdk) menu prep for full site refactor
[x] 🔥 MenuKBar
[x] ♻  (cmdk) Dynamic Sub Items 🔥 SubItem, Settings
[x] 🚨  (cmdk) fix unused vars and remove unused files
[x] ♻  (menu) 🚚 move files around
[x]  ♻  URL_TYPE

This pull request has been deployed to Vercel.

Latest commit:
d3c7ab8

✅ Preview:
https://jeromefitzgerald-nx4nt2wze-jerome5.vercel.app

🔍 Inspect:
https://vercel.com/jerome/jeromefitzgerald/HU7PqEjxDVGAUDrhCJsoaunwJUm5

View Workflow Logs

This pull request has been deployed to Vercel.

Latest commit:
5cab3a5

✅ Preview:
https://jeromefitzgerald-q1w40rr3z-jerome5.vercel.app

🔍 Inspect:
https://vercel.com/jerome/jeromefitzgerald/ARafWFJeGRjNkyLQ6XXBFJ7hFGza

View Workflow Logs


[FIX] sha256 witness issue (#1081)

This PR fix issue #1081.
It is caused by  copy assigning cells from phase2 col into phase1 col. In the first pass such phase 1 cells would not be assigned and lead to a complain of 'Syntheis' from halo2.

lgtm.  (since limechain may test develop i wil merge it now)


:bug: Retain host parameter after successful install

AppBridge 2.0 (now required for successful submission) requires the host parameter, after redirect it is not available on the URL any longer. Include it here to make it easily available.
I'm not using the supplied views, mine are custom, and I need the host parameter to be more readily available when I instantiate appbridge.  This works fine.

Static analysis appears to be failing for a reason that isn't related to the code change; Want a hand with that?

Memory error, no worries, thanks!


Added Bugify integration

Hi,
This pull request adds support for Bugify, an issues manager self hosted. It requires to define the custom domain on settings.
You can test the integration with bugify demo https://bugify.com/demo

Hey @jbfournot , we decided to clear up old PRs to make way for some big refactoring that is upcoming. If you wish to continue work on this PR please feel free to reopen or add an issue for adding Bugify support!


ablation/occlusion vs dCAM

Hi, thank you for your paper! I read your paper, and I was wondering if you had any thoughts as to why dCAM was not compared with a gradCAM channel ablation/occlusion approach (setting one or a combination of input channels to zero)? Channel ablation seems like such a simple idea to extend gradCAM for multivariate time-series. So I'm wondering if there is a reason that dCAM results were not compared with a gradCAM feature ablation approach? A recent paper tried ablation for gradCAM, but they did not compare with dCAM.
Thanks for your feedback!

Hi, Thank you for your interest in our research. Thanks also for the pointer; comparing dCAM with the radCAM channel ablation/occlusion approach is definitely relevant. While I was working on dCAM, I remember trying ablation techniques, but I did not get any promising results. Nevertheless, it is worth trying again and comparing dCAM with the recent paper you mentioned. I will let you know about the progress here!


Support for a search bar

It would be cool if the table of contents had a search bar so we could quickly filter headings. Something like this:

I'm currently playing with this. Works great except for two issues that might be irritating:

The search bar doesn't remember its filter on subsequent openings
It always scrolls to the top on subsequent openings

This is just how GitHub's own filters work. We'll probably keep it that way for now and go from there.


Skip CI on sparc64-unknown-linux-gnu for now

cc #2502
r? @ghost

@bors r+ p=1

:pushpin: Commit 6248bf60c3c605d519bf888ab1369269e67e2aa4 has been approved by JohnTitor

:hourglass: Testing commit 6248bf60c3c605d519bf888ab1369269e67e2aa4 with merge daea21338b0121292f7b2d05f5261fd9f2c4ccc1...

:sunny: Test successful - checks-actions, checks-cirrus-freebsd-11, checks-cirrus-freebsd-12, checks-cirrus-freebsd-13
Approved by: JohnTitor
Pushing daea21338b0121292f7b2d05f5261fd9f2c4ccc1 to master...


Test restart with large messages

WHAT is this pull request doing?
Asserting it takes less than 1 second and uses less than 1MB of RAM to restart the server with ten 128MB messages.
HOW can this pull request be tested?
crystal spec spec/server_spec.cr:1120

Cirrius CI is slow, requires 2.1s, locally it takes 7ms.


[improve][client]When namespace is deleted, the client is constantly reconnecting

Motivation
If the namespace is deleted, the cmd-lookup will still keep retrying, because the error code sent to the client is MetadataError, and the client will retry when it gets MetadataError. No matter how many times it tries again, it will not succeed.
https://github.com/apache/pulsar/blob/6cc30c93a05bb16b7ef62ffebc15ceb5e6efb502/pulsar-broker/src/main/java/org/apache/pulsar/broker/lookup/TopicLookupBase.java#L250-L257
Modifications
If the namespace is deleted

the cmd-lookup will get the error code TopicNotFound
the rest request will get the response code 404
improve response message for API topics and API namespaces
TODO I will write a test later

Documentation

[ ] doc
[ ] doc-required
[x] doc-not-needed
[ ] doc-complete

Matching PR in forked repository
PR in forked repository:

https://github.com/poorbarcode/pulsar/pull/30

rebase master

Codecov Report

Merging #18194 (9fd0426) into master (6c65ca0) will increase coverage by 4.09%.
The diff coverage is 41.70%.

@@             Coverage Diff              @@
##             master   #18194      +/-   ##
============================================
+ Coverage     34.91%   39.01%   +4.09%
- Complexity     5707     8301    +2594
============================================
  Files           607      683      +76
  Lines         53396    67284   +13888
  Branches       5712     7220    +1508
============================================
+ Hits          18644    26248    +7604
- Misses        32119    38033    +5914
- Partials       2633     3003     +370

Flag
Coverage Δ

unittests
39.01% <41.70%> (+4.09%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...org/apache/bookkeeper/mledger/LedgerOffloader.java
0.00% <ø> (ø)

...che/bookkeeper/mledger/LedgerOffloaderFactory.java
0.00% <ø> (ø)

...pache/bookkeeper/mledger/LedgerOffloaderStats.java
0.00% <ø> (ø)

...ookkeeper/mledger/LedgerOffloaderStatsDisable.java
0.00% <ø> (ø)

...a/org/apache/bookkeeper/mledger/ManagedCursor.java
85.71% <ø> (ø)

...che/bookkeeper/mledger/ManagedLedgerException.java
41.17% <ø> (ø)

...bookkeeper/mledger/ManagedLedgerFactoryConfig.java
86.66% <ø> (ø)

...g/apache/bookkeeper/mledger/ManagedLedgerInfo.java
22.22% <ø> (ø)

...he/bookkeeper/mledger/OffloadedLedgerMetadata.java
0.00% <ø> (ø)

...ava/org/apache/bookkeeper/mledger/ScanOutcome.java
0.00% <ø> (ø)

... and 724 more

/pulsarbot rerun-failure-checks


Android Build Fails when using AVPro plugin

Hello I am getting this error when trying to build APk that is using VideoKit

When I remove VideoKit it builds with no errors.
It happens when I import the AVPro plugin.
Here is a test project.
https://drive.google.com/file/d/1HxO0c3zUfv5a439E_dg0cRH5HmsGhJ-h/view?usp=sharing

One of our users was able to find a solution to this: here you go.


Bump to PyGMT v0.1.1 and enable Windows builds

Checklist

[x] Used a fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

@conda-forge-admin, please rerender

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@weiji14 All green for PyGMT v0.1.1.


[WIP] Add a Tooltip widget

This PR implements #460 as described in the issue. I have added a very simple example (definitely needs to be improved) to showcase the widget. I'm not sure about the widget name, since this acts as kind of a Container too. Or maybe the API could be done in a different way? I'd like to hear ideas about this.
Stuff to do:

[ ] Improve the example
[ ] Make the tooltip change position if it overflows a window edge to keep it visible

I would love for this to have an overlay_mode enum that allows me to place it relative to the anchor element rather than flying with the cursor. This would mimic the data-placement directive for Bootstrap tooltip.
enum OverlayMode {
    WithCursor, // current behavior
    Top,
    Right,
    Bottom,
    Left,
}

I would love for this to have an overlay_mode enum that allows me to place it relative to the anchor element rather than flying with the cursor. This would mimic the data-placement directive for Bootstrap tooltip.
enum OverlayMode {
    WithCursor, // current behavior
    Top,
    Right,
    Bottom,
    Left,
}

Edit: Great job so far! The example program works for me.

Yep, that sounds like a good idea! I'll try implementing that when I have time.

I would love for this to have an overlay_mode enum that allows me to place it relative to the anchor element rather than flying with the cursor. This would mimic the data-placement directive for Bootstrap tooltip.
enum OverlayMode {
    WithCursor, // current behavior
    Top,
    Right,
    Bottom,
    Left,
}

Edit: Great job so far! The example program works for me.

Yep, that sounds like a good idea! I'll try implementing that when I have time.

https://streamable.com/3rsu4r video showcasing this! @clarkmoody

https://streamable.com/3rsu4r video showcasing this! @clarkmoody

Oh yeah!


env.example missing

I've been grepping up and down the directory , even rolling back a few versions of the git repo and for the life of me I cant seem to find the env.example file. I cant currently determine what the .env variables are or what should go in them, and it doesn't seem to be documented anywhere?
Is there somewhere I can go to find an example or some sort of documentation? (The only documentation I found told me to copy env.example!)

See #1295

https://cookiecutter-django.readthedocs.io/en/latest/developing-locally-docker.html#configuring-the-environment
In short, there has been a major refactoring of this repo. There is no more env.example.

Ah ok. It would be good if one could be restored, for some reason the docs where not showing up on my google search.

@shayneoneill

It would be good if one could be restored


Add a parameter to handle extended user profile fields on facebook

A new parameter tock_messenger_extended_profile_fields was added to handle the fields that will be requested frm facebook concerning the user profile.
By default the parameter is set to false and the fields first_name, last_name, profile_pic are requested from facebook
If special authorizations were set, the paramete rcan be set to true to get locale, timezone, gender fields
More info in: https://developers.facebook.com/docs/messenger-platform/identity/user-profile/#fields


_ide_fix.php shouldn't be in version control

Or at the very least, in branch laravel-5 it should have been generated for Laravel 5, not for Laravel 4. PhpStorm lights up with errors.

Yeah, that's totally right. Thanks for your input!
Cheers


Improve CI speed

The speed of the CI (mostly the development tests) has a noticeable overhead because three separate tox environments are used for the Python unittests, Jupyter notebook tests, and doctests.
This PR introduces a new tox environment which combines all of these tests into one target, removing the three-fold tox environment setup overhead.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>9
Details

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 100.0%

Totals

Change from base Build<PHONE_NUMBER>9:
0.0%

Covered Lines:
297

Relevant Lines:
297

💛  - Coveralls


Text() vs. InnerText vs. jQuery difference

I'm trying to get inner text of a node, however .InnerText property seems to misbehave:
> CQ.Create("<hai>foo & bar   baz
qux</hai>").["hai"].[0].InnerText;;
"foo & bar   bazqux"

Compare to jQuery:
> $("<hai>foo & bar   baz
qux</hai>")[0].innerText
"foo & bar   baz\nqux"

At the same time Text() seems to work closer to jQuery:
> CQ.Create("<hai>foo & bar   baz
qux</hai>").["hai"].Text();;
"foo & bar   bazqux"

Do you have a suggestion on how can I want to achieve behaviour similar to jQuery?

Write
CsQuery.Config.OutputFormatter = OutputFormatters.HtmlEncodingNone;
before any CQ use.

@alexander1986 thanks, that makes output of .InnerText similar to .Text(). Although I wish I could get the exact behavior of jQuery.


Feature request: Be able to close log viewer with Esc key

Rancher versions:
rancher/server: 1.6.14
rancher/agent: rancher/agent:v1.2.9
Infrastructure Stack versions:
healthcheck: rancher/healthcheck:v0.3.3
ipsec: rancher/net:holder
network-services: rancher/network-manager:v0.7.19
scheduler: rancher/scheduler:v0.8.3
kubernetes (if applicable): Not applicable
Docker version: (docker version,docker info preferred)
17.12.1-ce
Operating system and kernel: (cat /etc/os-release, uname -r preferred)
Ubuntu 16.04
Type/provider of hosts: (VirtualBox/Bare-metal/AWS/GCE/DO)
Bare-metal, hosted on AWS.
Setup details: (single node rancher vs. HA rancher, internal DB vs. external DB)
Single node rancher w/ external DB.
Environment Template: (Cattle/Kubernetes/Swarm/Mesos)
Cattle.
Steps to Reproduce:
Open the log viewer for a container.
Results:
The log view opens. But, you must press the Close button with the mouse to close it. It feels like it untuitively "should" work to press Esc to close the log viewer. What do you think? If you point me at the right file in the web UI, I might be able to submit a PR.
Thanks for a great tool! 👍 👍 👍

I can see this working for most of the popups we use (logs/shell/kubectl/kubeconfig). Just not sure if this can be implemented cleanly. The UI code lives in https://github.com/rancher/ui, branch 1.6-dev for 1.6

Logs yes, shell no (you need the escape key)

Agree @vincent99, but the shell can already be closed by Ctrl-D so that's easy. 😉

@deniseschannon Will this go into 2.0 only, not 1.6?

@perlun yes, currently only in 2.0.

Version - 2.0 master 4/17
Verified fixed


[gp-2316] floating ui and rough tooltip mvp

https://cambly.atlassian.net/browse/GP-2316

I had to do some significant refactors. Let me clean this up some more, add working storybook configs and fix the tests/linting. I might do arrow placement in a separate PR. Trying to center the arrow based on the anchor element has proved to be difficult
I'll address relevant comments.

Closing this one and just gonna merge in this one instead:
https://github.com/Cambly/syntax/pull/138
(it's built off of this branch)


Separate object creation from non-trivial operations.

Constructors really shouldn't do anything more than trivial setting of state.  However, we have quite a few classes with non-trivial constructors.  (For example, of those with @injectable applied, there are at least 96.  See #10454.)  This adds complexity that makes it harder to understand what is happening when the extension is starting up, much less carefully controlling and adapting activation.
To address this, we should do the following:

move all non-trivial initialization out of constructors
split up object init into several distinct phases

The phases would be something like this:

creation

provided with dependencies (which it must treat as un-initialized) and POTS values
stores them for use in later phases
sets up and stores trivial immutable state
(minimally) sets up and stores trivial initial mutable state
more complex init at the phase should be done instead in a factory function

simple-init

relies only on stored dependencies and initial state
stored dependencies are treated as simply-initialized (forced?)
idempotent (for mutable state, short-circuit)
only trivial work
sets up and stores all remaining trivial initial mutable state
not async

complex-init

relies only on state (incl. stored dependencies)
stored dependencies are treated as fully initialized (forced?)
does non-trivial work to finish setting up state
interaction with external resources (e.g. IO, telemetry)
async operations
if it relies on having some callback or event handler set then either this should block until that happens or it should make a call on a dependency (e.g. a wrapper func) to force it to happen
at this point it is ready to be used

start any background operations

relies only on state (incl. stored dependencies)
stored dependencies are treated as fully initialized (forced?)
includes starting "daemon" processes

registration

relies only on state (incl. stored dependencies)
registers callbacks and event handlers
at this point we should expect it be fully used

A hard separation between these phases makes it much easier to understand what is going on and to divide up extension activation along horizontal layers.  Note that the phases easily map onto methods.  An interface (for discussion purposes only) could look like one of the following:
interface Initializable {
    // 1
    constructor(...);
    // 2
    initializeSimple();
    // 3
    initialize(): Promise<void>;
    // 4
    start(): Promise<void>;
    // 5
    register();
}

interface Initializable {
    // 1 & 2 (if we are a little more permissive about what's done in the constructor)
    constructor(...);
    // 3
    initialize(): Promise<void>;
    // 4
    start(): Promise<void>;
    // 5
    register();
}

interface Initializable {
    // 1
    constructor(...);
    // 2
    initialize();
    // 3, 4, & 5
    activate(): Promise<void>;
}

(Note that the problem has been addressed for some classes, though with various different solutions.  So this is also the right time to apply a consistent approach to how we tackle the problem.)
Of particular interest are classes with any of the following characteristics:

with @injectable applied:

has mutable state
registers a callback or event handler

all:

constructor with non-empty body, noting trivial vs. non-trivial

non-trivial:  performs work and/or interacts with external resources
setting up simple state is trivial

has one of the following methods: initialize(), register*(), activate(), start()

Relative to those classes, we should consolidate on a simple initialization "interface" that we can use consistently during extension activation.  It should also make it easy to identify the level of complexity of a class's initialization.

In terms of concrete steps, the following should be done for all classes in the code base, with an initial preference toward those with @injectable applied:

identify every class that need attention and add a TODO to each referencing this issue
eliminate any existing initialize() and register*() methods

move all trivial init code to the constructor (phases 1 & 2)

trivial init of immutable object state
trivial init of mutable object state
nothing async
treat provided args (dependencies) as though they have not been initialized yet

move all other code to an activate() method (phases 3, 4, & 5)

consistent signature: public async activate(): Promise<void>
non-trivial work (including complex init of mutable object state)
interaction with external resources (e.g. IO, telemetry)
any async operations
registering a callback or event handler

update activateLegacy() (in src/client/extensionActivation.ts) to call the various activate() methods in the right locations

It may make sense to be a bit more granular about it:

...
move any callback or event handler registration into a register() method (phase 5)

consistent signature: public register(): void
assumes that the object is fully initialized
assumes that any necessary background operations have been started

move any starting of background operations to a start() method (phase 4)

consistent signature: public async start(): Promise<void>

eliminate any activate() method

move any init code to an initialize() method (phase 3)

consistent signature: public async initialize(): Promise<void>

move any activation-time telemetry code activateLegacy() (in src/client/extensionActivation.ts)
any other code (there shouldn't be any) should be moved to registered callback handlers

move to the constructor any trivial init of object state in initialize() (phases 1 & 2)
update activateLegacy() (in src/client/extensionActivation.ts) to call the various initialize(), start(), and register() methods in the right locations

Splitting phases 1 & 2 could happen as well, but that isn't as important.

There is also the question of how to make sure we do not regress.  It may make sense to add a test that verifies that all constructor bodies are empty.  That should be doable without much parsing complexity.  It would require that all classes be updated to move everything out of the constructor body and into an initialize() method.  However, this might not be practical (e.g. super() calls).  It could make sense to look for a marker comment at the beginning of a non-empty constructor indicating that it has been manually vetted.

We'll try this out with the upcoming "env discovery" work.

We did this: https://github.com/microsoft/vscode-python/issues/10542#issuecomment-598411420, closing.


Doxygen access from extern

We are using cereal as our serialization library together with our libraries and would like to be able to have our doxygen documentation link to that of cereal.
To do that, a tagfile is needed, and finer control over the output directory is useful.

Merged to develop!


Statewide header page references Support page. Convert to Contact us link

Updated this link on statewide header, page feedback, and site navigation, including updating the copy to match. Closing this issue as done.


Feature/stats carousel

Description
Changed the stats bar to a carousel, changed the copy in the stats section (very open to changing/feedback!), and adjusted the styling of the Stats section and some corresponding changes to the Map styling
Type of change
Please delete options that are not relevant.

[X ] New feature (non-breaking change which adds functionality)

Change Status

[X] Complete, but not tested (may need new tests)
[X] Incomplete/work-in-progress, PR is for discussion/feedback

Checklist

[X] My code follows the style guidelines of this project
[X] I have performed a self-review of my own code
[TBD] My code has been reviewed by at least one peer
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[X] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[X] There are no merge conflicts

Sorry, accidentally pushed the PR template update to this branch. I won't bother reverting it because it doesn't affect anything else, but let me know if you'd prefer that I do.


Some Commands Tests use not existing device names

Some command's tests use not existing device names - Random-Boolean-Device. (example, example2, example3 ), or is not set correctly - > incompatibility between setting DeviceName , but expecting {{getDeviceByName}}

Replace with device names with existing one. Be sure that the tests do not fails with 404, when not really expecting.

@cherrycl
Closing this issue, because it figured out that the virtual-device service is supposed to be up when running the tests -> and thus the devices exit in the database.
Closing the issue, because of not correct environment used during the testing


Generalize the figure= keyword argument to all kind of plot

Should solve #86

Hi @Sigmun, thanks for contributing. I will try to have a detailled look at the MR as soon as possible, I am quite busy now.
I already tried to implement this feature, but struggled how the API should be designed. There are a few critical issues that have to be settled:

Should we check the plotting type (line, bar, ...) and only allow certain combinations that make sense
How should we handle the case when the first plot has a different numerical range as the second (x/y range, ticks, etc)
Errorhandling in the code or indirect via Bokeh API

What do you think about that?
Best Patrik

Thanks for working on this! I just wanted to note that this is the default behavior of matplotlib backend, and has been very productive for me.  We don't have to copy exactly, but maybe we can reference what matplotlib is doing in some aspects.
Regarding 1 & 2 : One option I think it makes is respecting the first plot.
fig = s1.plot(kind='line', show_figure=False)  #first
s2.plot(kind="bar", figure=fig)                #second

The first line is responsible for "creating" a figure, and second line is "using" an already created plot so I think such behavior is intuitive API wise as well.

this looks like a very good change to me.   without it the higher level API that pandas-bokeh offers removes a significant number of use cases.  As well as working with matplotlib and plotly that offer this capability have also worked with geopandas explore()which provides similar type API to folium.  effectively building up a figure from a sequence of layers

@rraymondgh: As already mentioned I wanted this feature for nearly 1,5 years, but couldn't find the time to implement it. The problems are outlined above and the current code status is a bit messy, so in order to implement the feature, I would have to refactor the code quite a lot.

Gents, I'm sorry, still having issues figuring out how to plot 2 lines of different style in HTML.
Let's say here's an example. df would have different columns. I want to display one of it as normal line, but some others as discrete arrows (to show my signals) or circles or whatever, to mark the main line with some entries/exists. Also how can I make solid vertical line for xticks? They're kind of very pale. Thanks!
	with open("osc_multimodel_forecast_plot.html" , "w") as f: 		html = df.plot_bokeh(kind='line', title="BB S&P",  xticks=xticks,  vertical_xlabel=True,figsize=(2000, 1000), show_figure=True,return_html=True, xlabel='date', ylabel='Price', hovertool=True, zooming=True,panning=True, legend='top_right') 		f.write(html+"\n") 	f.close()

Gents, I'm sorry, still having issues figuring out how to plot 2 lines of different style in HTML.
Let's say here's an example. df would have different columns. I want to display one of it as normal line, but some others as discrete arrows (to show my signals) or circles or whatever, to mark the main line with some entries/exists. Also how can I make solid vertical line for xticks? They're kind of very pale. Thanks!
with open("osc_multimodel_forecast_plot.html" , "w") as f: html = df.plot_bokeh(kind='line', title="BB S&P", xticks=xticks, vertical_xlabel=True,figsize=(2000, 1000), show_figure=True,return_html=True, xlabel='date', ylabel='Price', hovertool=True, zooming=True,panning=True, legend='top_right') f.write(html+"\n") f.close()

Hi @algomaschine, I don't see the link with this PR. you need to open an issue for your problem.


Can't resolve dependencies

Issue description
pipenv can't resolve dependencies.
I have Pipfile
[packages]
librosa = "<0.6"
scipy = ">=0.18.1"
pydub = "*"
audioread = "==2.1.6"
numpy = "<1.15.0"

[dev-packages]

[requires]
python_version = "3.6"

pipenv lock failed
$ pipenv lock
Locking [dev-packages] dependencies…
Locking [packages] dependencies…
Building requirements...
Resolving dependencies...
✘ Locking Failed!
[ResolutionFailure]:   File "/usr/local/lib/python3.6/site-packages/pipenv/resolver.py", line 785, in _main
[ResolutionFailure]:       resolve_packages(pre, clear, verbose, system, write, requirements_dir, packages)
[ResolutionFailure]:   File "/usr/local/lib/python3.6/site-packages/pipenv/resolver.py", line 753, in resolve_packages
[ResolutionFailure]:       requirements_dir=requirements_dir,
[ResolutionFailure]:   File "/usr/local/lib/python3.6/site-packages/pipenv/resolver.py", line 736, in resolve
[ResolutionFailure]:       req_dir=requirements_dir
[ResolutionFailure]:   File "/usr/local/lib/python3.6/site-packages/pipenv/utils.py", line 1386, in resolve_deps
[ResolutionFailure]:       req_dir=req_dir,
[ResolutionFailure]:   File "/usr/local/lib/python3.6/site-packages/pipenv/utils.py", line 1093, in actually_resolve_deps
[ResolutionFailure]:       resolver.resolve()
[ResolutionFailure]:   File "/usr/local/lib/python3.6/site-packages/pipenv/utils.py", line 818, in resolve
[ResolutionFailure]:       raise ResolutionFailure(message=str(e))
[pipenv.exceptions.ResolutionFailure]: Warning: Your dependencies could not be resolved. You likely have a mismatch in your sub-dependencies.
  First try clearing your dependency cache with $ pipenv lock --clear, then try the original command again.
 Alternatively, you can use $ pipenv install --skip-lock to bypass this mechanism, then run $ pipenv graph to inspect the situation.
  Hint: try $ pipenv lock --pre if it is a pre-release dependency.
ERROR: Could not find a version that matches numpy<1.15.0,>=1.10,>=1.13.3,>=1.15,>=1.8.0 (from -r /tmp/pipenv39v4hwjkrequirements/pipenv-sf1frvwr-constraints.txt (line 3))
Tried: 1.3.0, 1.4.1, 1.5.0, 1.5.1, 1.6.0, 1.6.0, 1.6.1, 1.6.1, 1.6.2, 1.6.2, 1.7.0, 1.7.0, 1.7.1, 1.7.1, 1.7.2, 1.7.2, 1.8.0, 1.8.0, 1.8.1, 1.8.1, 1.8.2, 1.8.2, 1.9.0, 1.9.0, 1.9.1, 1.9.1, 1.9.2, 1.9.2, 1.9.3, 1.9.3, 1.10.0.post2, 1.10.0.post2, 1.10.1, 1.10.1, 1.10.2, 1.10.2, 1.10.4, 1.10.4, 1.11.0, 1.11.0, 1.11.1, 1.11.1, 1.11.2, 1.11.2, 1.11.3, 1.11.3, 1.12.0, 1.12.0, 1.12.1, 1.12.1, 1.13.0, 1.13.0, 1.13.1, 1.13.1, 1.13.3, 1.13.3, 1.14.0, 1.14.0, 1.14.1, 1.14.1, 1.14.2, 1.14.2, 1.14.3, 1.14.3, 1.14.4, 1.14.4, 1.14.5, 1.14.5, 1.14.6, 1.14.6, 1.15.0, 1.15.0, 1.15.1, 1.15.1, 1.15.2, 1.15.2, 1.15.3, 1.15.3, 1.15.4, 1.15.4, 1.16.0, 1.16.0, 1.16.1, 1.16.1, 1.16.2, 1.16.2, 1.16.3, 1.16.3, 1.16.4, 1.16.4, 1.16.5, 1.16.5, 1.16.6, 1.16.6, 1.17.0, 1.17.0, 1.17.1, 1.17.1, 1.17.2, 1.17.2, 1.17.3, 1.17.3, 1.17.4, 1.17.4, 1.17.5, 1.17.5, 1.18.0, 1.18.0, 1.18.1, 1.18.1, 1.18.2, 1.18.2, 1.18.3, 1.18.3, 1.18.4, 1.18.4
Skipped pre-versions: 1.11.0b3, 1.11.0b3, 1.11.0rc1, 1.11.0rc1, 1.11.0rc2, 1.11.0rc2, 1.11.1rc1, 1.11.1rc1, 1.11.2rc1, 1.11.2rc1, 1.12.0b1, 1.12.0b1, 1.12.0rc1, 1.12.0rc2, 1.12.0rc2, 1.12.1rc1, 1.12.1rc1, 1.13.0rc1, 1.13.0rc1, 1.13.0rc2, 1.13.0rc2, 1.14.0rc1, 1.14.0rc1, 1.15.0rc1, 1.15.0rc1, 1.15.0rc2, 1.15.0rc2, 1.16.0rc1, 1.16.0rc1, 1.16.0rc2, 1.16.0rc2, 1.17.0rc1, 1.17.0rc1, 1.17.0rc2, 1.17.0rc2, 1.18.0rc1, 1.18.0rc1, 1.19.0rc1, 1.19.0rc1, 1.19.0rc1, 1.19.0rc2, 1.19.0rc2, 1.19.0rc2
There are incompatible versions in the resolved dependencies:
  numpy<1.15.0 (from -r /tmp/pipenv39v4hwjkrequirements/pipenv-sf1frvwr-constraints.txt (line 3))
  numpy>=1.10 (from resampy==0.2.2->librosa==0.5.1->-r /tmp/pipenv39v4hwjkrequirements/pipenv-sf1frvwr-constraints.txt (line 5))
  numpy>=1.13.3 (from scikit-learn==0.23.1->librosa==0.5.1->-r /tmp/pipenv39v4hwjkrequirements/pipenv-sf1frvwr-constraints.txt (line 5))
  numpy>=1.13.3 (from scipy==1.4.1->-r /tmp/pipenv39v4hwjkrequirements/pipenv-sf1frvwr-constraints.txt (line 4))
  numpy>=1.15 (from numba==0.49.1->resampy==0.2.2->librosa==0.5.1->-r /tmp/pipenv39v4hwjkrequirements/pipenv-sf1frvwr-constraints.txt (line 5))
  numpy>=1.8.0 (from librosa==0.5.1->-r /tmp/pipenv39v4hwjkrequirements/pipenv-sf1frvwr-constraints.txt (line 5))

Expected result
pipenv would resolve to this
ordereddict==1.1; python_version < "2.7"
enum34==1.1.10; python_version < "3.4"
funcsigs==1.0.2; python_version < "3.3"
llvmlite==0.32.1
setuptools==47.1.1
singledispatch==<IP_ADDRESS>; python_version < "3.4"
numba==0.47.0
threadpoolctl==2.1.0
decorator==4.4.2
joblib==0.15.1
resampy==0.2.2
scikit-learn==0.23.1
six==1.15.0
audioread==2.1.6
librosa==0.5.1
numpy==1.14.6
pydub==0.24.0
scipy==1.4.1

poetry and dephell resolve this perfectly/
Actual result
 pipenv lock --verbose
Locking [dev-packages] dependencies…
Locking [packages] dependencies…
Building requirements...
Resolving dependencies...
⠹ Locking...
                          ROUND 1
✘ Locking Failed!
Current constraints:
  audioread==2.1.6 (from -r /tmp/pipenvxzu9oeb4requirements/pipenv-v9bklki1-constraints.txt (line 4))
  librosa<0.6 (from -r /tmp/pipenvxzu9oeb4requirements/pipenv-v9bklki1-constraints.txt (line 5))
  numpy<1.15.0 (from -r /tmp/pipenvxzu9oeb4requirements/pipenv-v9bklki1-constraints.txt (line 6))
  pydub (from -r /tmp/pipenvxzu9oeb4requirements/pipenv-v9bklki1-constraints.txt (line 2))
  scipy>=0.18.1 (from -r /tmp/pipenvxzu9oeb4requirements/pipenv-v9bklki1-constraints.txt (line 3))

Finding the best candidates:
  found candidate audioread==2.1.6 (constraint was ==2.1.6)
  found candidate librosa==0.5.1 (constraint was <0.6)
  found candidate numpy==1.14.6 (constraint was <1.15.0)
  found candidate pydub==0.24.0 (constraint was <any>)
  found candidate scipy==1.4.1 (constraint was >=0.18.1)

Finding secondary dependencies:
  scipy==1.4.1              requires numpy>=1.13.3
  librosa==0.5.1            requires audioread>=2.0.0, decorator>=3.0.0, joblib>=0.7.0, numpy>=1.8.0, resampy>=0.1.2, scikit-learn>=0.14.0, scipy>=0.13.0, six>=1.3
  pydub==0.24.0             requires -
  numpy==1.14.6             requires -
  audioread==2.1.6          requires -

New dependencies found in this round:
  adding ['audioread', '>=2.0.0', '[]']
  adding ['decorator', '>=3.0.0', '[]']
  adding ['joblib', '>=0.7.0', '[]']
  adding ['numpy', '>=1.13.3,>=1.8.0', '[]']
  adding ['resampy', '>=0.1.2', '[]']
  adding ['scikit-learn', '>=0.14.0', '[]']
  adding ['scipy', '>=0.13.0', '[]']
  adding ['six', '>=1.3', '[]']
Removed dependencies in this round:
------------------------------------------------------------
Result of round 1: not stable

                          ROUND 2
Current constraints:
  audioread==2.1.6,>=2.0.0 (from -r /tmp/pipenvxzu9oeb4requirements/pipenv-v9bklki1-constraints.txt (line 4))
  decorator>=3.0.0 (from librosa==0.5.1->-r /tmp/pipenvxzu9oeb4requirements/pipenv-v9bklki1-constraints.txt (line 5))
  joblib>=0.7.0 (from librosa==0.5.1->-r /tmp/pipenvxzu9oeb4requirements/pipenv-v9bklki1-constraints.txt (line 5))
  librosa<0.6 (from -r /tmp/pipenvxzu9oeb4requirements/pipenv-v9bklki1-constraints.txt (line 5))
  numpy<1.15.0,>=1.13.3,>=1.8.0 (from -r /tmp/pipenvxzu9oeb4requirements/pipenv-v9bklki1-constraints.txt (line 6))
  pydub (from -r /tmp/pipenvxzu9oeb4requirements/pipenv-v9bklki1-constraints.txt (line 2))
  resampy>=0.1.2 (from librosa==0.5.1->-r /tmp/pipenvxzu9oeb4requirements/pipenv-v9bklki1-constraints.txt (line 5))
  scikit-learn>=0.14.0 (from librosa==0.5.1->-r /tmp/pipenvxzu9oeb4requirements/pipenv-v9bklki1-constraints.txt (line 5))
  scipy>=0.13.0,>=0.18.1 (from -r /tmp/pipenvxzu9oeb4requirements/pipenv-v9bklki1-constraints.txt (line 3))
  six>=1.3 (from librosa==0.5.1->-r /tmp/pipenvxzu9oeb4requirements/pipenv-v9bklki1-constraints.txt (line 5))

Finding the best candidates:
  found candidate audioread==2.1.6 (constraint was >=2.0.0,==2.1.6)
  found candidate decorator==4.4.2 (constraint was >=3.0.0)
  found candidate joblib==0.15.1 (constraint was >=0.7.0)
  found candidate librosa==0.5.1 (constraint was <0.6)
  found candidate numpy==1.14.6 (constraint was >=1.13.3,<1.15.0,>=1.8.0)
  found candidate pydub==0.24.0 (constraint was <any>)
  found candidate resampy==0.2.2 (constraint was >=0.1.2)
  found candidate scikit-learn==0.23.1 (constraint was >=0.14.0)
  found candidate scipy==1.4.1 (constraint was >=0.13.0,>=0.18.1)
  found candidate six==1.15.0 (constraint was >=1.3)

Finding secondary dependencies:
  scipy==1.4.1              requires numpy>=1.13.3
  resampy==0.2.2            requires numba>=0.32, numpy>=1.10, scipy>=0.13, six>=1.3
  scikit-learn==0.23.1      requires joblib>=0.11, numpy>=1.13.3, scipy>=0.19.1, threadpoolctl>=2.0.0
  librosa==0.5.1            requires audioread>=2.0.0, decorator>=3.0.0, joblib>=0.7.0, numpy>=1.8.0, resampy>=0.1.2, scikit-learn>=0.14.0, scipy>=0.13.0, six>=1.3
  pydub==0.24.0             requires -
  decorator==4.4.2          requires -
  numpy==1.14.6             requires -
  six==1.15.0               requires -
  joblib==0.15.1            requires -
  audioread==2.1.6          requires -

New dependencies found in this round:
  adding ['joblib', '>=0.11,>=0.7.0', '[]']
  adding ['numba', '>=0.32', '[]']
  adding ['numpy', '>=1.10,>=1.13.3,>=1.8.0', '[]']
  adding ['scipy', '>=0.13,>=0.13.0,>=0.19.1', '[]']
  adding ['threadpoolctl', '>=2.0.0', '[]']
Removed dependencies in this round:
  removing ['joblib', '>=0.7.0', '[]']
  removing ['numpy', '>=1.13.3,>=1.8.0', '[]']
  removing ['scipy', '>=0.13.0', '[]']
------------------------------------------------------------
Result of round 2: not stable

                          ROUND 3
Current constraints:
  audioread==2.1.6,>=2.0.0 (from -r /tmp/pipenvxzu9oeb4requirements/pipenv-v9bklki1-constraints.txt (line 4))
  decorator>=3.0.0 (from librosa==0.5.1->-r /tmp/pipenvxzu9oeb4requirements/pipenv-v9bklki1-constraints.txt (line 5))
  joblib>=0.11,>=0.7.0 (from librosa==0.5.1->-r /tmp/pipenvxzu9oeb4requirements/pipenv-v9bklki1-constraints.txt (line 5))
  librosa<0.6 (from -r /tmp/pipenvxzu9oeb4requirements/pipenv-v9bklki1-constraints.txt (line 5))
  numba>=0.32 (from resampy==0.2.2->librosa==0.5.1->-r /tmp/pipenvxzu9oeb4requirements/pipenv-v9bklki1-constraints.txt (line 5))
  numpy<1.15.0,>=1.10,>=1.13.3,>=1.8.0 (from -r /tmp/pipenvxzu9oeb4requirements/pipenv-v9bklki1-constraints.txt (line 6))
  pydub (from -r /tmp/pipenvxzu9oeb4requirements/pipenv-v9bklki1-constraints.txt (line 2))
  resampy>=0.1.2 (from librosa==0.5.1->-r /tmp/pipenvxzu9oeb4requirements/pipenv-v9bklki1-constraints.txt (line 5))
  scikit-learn>=0.14.0 (from librosa==0.5.1->-r /tmp/pipenvxzu9oeb4requirements/pipenv-v9bklki1-constraints.txt (line 5))
  scipy>=0.13,>=0.13.0,>=0.18.1,>=0.19.1 (from -r /tmp/pipenvxzu9oeb4requirements/pipenv-v9bklki1-constraints.txt (line 3))
  six>=1.3 (from librosa==0.5.1->-r /tmp/pipenvxzu9oeb4requirements/pipenv-v9bklki1-constraints.txt (line 5))
  threadpoolctl>=2.0.0 (from scikit-learn==0.23.1->librosa==0.5.1->-r /tmp/pipenvxzu9oeb4requirements/pipenv-v9bklki1-constraints.txt (line 5))

Finding the best candidates:
  found candidate audioread==2.1.6 (constraint was >=2.0.0,==2.1.6)
  found candidate decorator==4.4.2 (constraint was >=3.0.0)
  found candidate joblib==0.15.1 (constraint was >=0.11,>=0.7.0)
  found candidate librosa==0.5.1 (constraint was <0.6)
  found candidate numba==0.49.1 (constraint was >=0.32)
  found candidate numpy==1.14.6 (constraint was >=1.10,>=1.13.3,<1.15.0,>=1.8.0)
  found candidate pydub==0.24.0 (constraint was <any>)
  found candidate resampy==0.2.2 (constraint was >=0.1.2)
  found candidate scikit-learn==0.23.1 (constraint was >=0.14.0)
  found candidate scipy==1.4.1 (constraint was >=0.13,>=0.13.0,>=0.18.1,>=0.19.1)
  found candidate six==1.15.0 (constraint was >=1.3)
  found candidate threadpoolctl==2.1.0 (constraint was >=2.0.0)

Finding secondary dependencies:
  resampy==0.2.2            requires numba>=0.32, numpy>=1.10, scipy>=0.13, six>=1.3
  decorator==4.4.2          requires -
  six==1.15.0               requires -
  pydub==0.24.0             requires -
  librosa==0.5.1            requires audioread>=2.0.0, decorator>=3.0.0, joblib>=0.7.0, numpy>=1.8.0, resampy>=0.1.2, scikit-learn>=0.14.0, scipy>=0.13.0, six>=1.3
  scipy==1.4.1              requires numpy>=1.13.3
  joblib==0.15.1            requires -
  scikit-learn==0.23.1      requires joblib>=0.11, numpy>=1.13.3, scipy>=0.19.1, threadpoolctl>=2.0.0
  audioread==2.1.6          requires -
  threadpoolctl==2.1.0      requires -
  numpy==1.14.6             requires -
  numba==0.49.1             requires llvmlite<=0.33.0.dev0,>=0.31.0.dev0, numpy>=1.15, setuptools

New dependencies found in this round:
  adding ['llvmlite', '<=0.33.0.dev0,>=0.31.0.dev0', '[]']
  adding ['numpy', '>=1.10,>=1.13.3,>=1.15,>=1.8.0', '[]']
  adding ['setuptools', '', '[]']
Removed dependencies in this round:
  removing ['numpy', '>=1.10,>=1.13.3,>=1.8.0', '[]']
------------------------------------------------------------
Result of round 3: not stable

                          ROUND 4
Current constraints:
  audioread==2.1.6,>=2.0.0 (from -r /tmp/pipenvxzu9oeb4requirements/pipenv-v9bklki1-constraints.txt (line 4))
  decorator>=3.0.0 (from librosa==0.5.1->-r /tmp/pipenvxzu9oeb4requirements/pipenv-v9bklki1-constraints.txt (line 5))
  joblib>=0.11,>=0.7.0 (from librosa==0.5.1->-r /tmp/pipenvxzu9oeb4requirements/pipenv-v9bklki1-constraints.txt (line 5))
  librosa<0.6 (from -r /tmp/pipenvxzu9oeb4requirements/pipenv-v9bklki1-constraints.txt (line 5))
  llvmlite<=0.33.0.dev0,>=0.31.0.dev0 (from numba==0.49.1->resampy==0.2.2->librosa==0.5.1->-r /tmp/pipenvxzu9oeb4requirements/pipenv-v9bklki1-constraints.txt (line 5))
  numba>=0.32 (from resampy==0.2.2->librosa==0.5.1->-r /tmp/pipenvxzu9oeb4requirements/pipenv-v9bklki1-constraints.txt (line 5))
  numpy<1.15.0,>=1.10,>=1.13.3,>=1.15,>=1.8.0 (from -r /tmp/pipenvxzu9oeb4requirements/pipenv-v9bklki1-constraints.txt (line 6))
  pydub (from -r /tmp/pipenvxzu9oeb4requirements/pipenv-v9bklki1-constraints.txt (line 2))
  resampy>=0.1.2 (from librosa==0.5.1->-r /tmp/pipenvxzu9oeb4requirements/pipenv-v9bklki1-constraints.txt (line 5))
  scikit-learn>=0.14.0 (from librosa==0.5.1->-r /tmp/pipenvxzu9oeb4requirements/pipenv-v9bklki1-constraints.txt (line 5))
  scipy>=0.13,>=0.13.0,>=0.18.1,>=0.19.1 (from -r /tmp/pipenvxzu9oeb4requirements/pipenv-v9bklki1-constraints.txt (line 3))
  setuptools (from numba==0.49.1->resampy==0.2.2->librosa==0.5.1->-r /tmp/pipenvxzu9oeb4requirements/pipenv-v9bklki1-constraints.txt (line 5))
  six>=1.3 (from librosa==0.5.1->-r /tmp/pipenvxzu9oeb4requirements/pipenv-v9bklki1-constraints.txt (line 5))
  threadpoolctl>=2.0.0 (from scikit-learn==0.23.1->librosa==0.5.1->-r /tmp/pipenvxzu9oeb4requirements/pipenv-v9bklki1-constraints.txt (line 5))

Finding the best candidates:
  found candidate audioread==2.1.6 (constraint was >=2.0.0,==2.1.6)
  found candidate decorator==4.4.2 (constraint was >=3.0.0)
  found candidate joblib==0.15.1 (constraint was >=0.11,>=0.7.0)
  found candidate librosa==0.5.1 (constraint was <0.6)
  found candidate llvmlite==0.32.1 (constraint was >=0.31.0.dev0,<=0.33.0.dev0)
  found candidate numba==0.49.1 (constraint was >=0.32)
Traceback (most recent call last):
  File "/usr/local/lib/python3.6/site-packages/pipenv/utils.py", line 808, in resolve
    results = self.resolver.resolve(max_rounds=environments.PIPENV_MAX_ROUNDS)
  File "/usr/local/lib/python3.6/site-packages/pipenv/patched/piptools/resolver.py", line 180, in resolve
    has_changed, best_matches = self._resolve_one_round()
  File "/usr/local/lib/python3.6/site-packages/pipenv/patched/piptools/resolver.py", line 260, in _resolve_one_round
    best_matches = {self.get_best_match(ireq) for ireq in constraints}
  File "/usr/local/lib/python3.6/site-packages/pipenv/patched/piptools/resolver.py", line 260, in <setcomp>
    best_matches = {self.get_best_match(ireq) for ireq in constraints}
  File "/usr/local/lib/python3.6/site-packages/pipenv/patched/piptools/resolver.py", line 320, in get_best_match
    ireq, prereleases=self.prereleases
  File "/usr/local/lib/python3.6/site-packages/pipenv/patched/piptools/repositories/pypi.py", line 202, in find_best_match
    raise NoCandidateFound(ireq, all_candidates, self.finder)
pipenv.patched.piptools.exceptions.NoCandidateFound: Could not find a version that matches numpy<1.15.0,>=1.10,>=1.13.3,>=1.15,>=1.8.0 (from -r /tmp/pipenvxzu9oeb4requirements/pipenv-v9bklki1-constraints.txt (line 6))
Tried: 1.3.0, 1.4.1, 1.5.0, 1.5.1, 1.6.0, 1.6.0, 1.6.1, 1.6.1, 1.6.2, 1.6.2, 1.7.0, 1.7.0, 1.7.1, 1.7.1, 1.7.2, 1.7.2, 1.8.0, 1.8.0, 1.8.1, 1.8.1, 1.8.2, 1.8.2, 1.9.0, 1.9.0, 1.9.1, 1.9.1, 1.9.2, 1.9.2, 1.9.3, 1.9.3, 1.10.0.post2, 1.10.0.post2, 1.10.1, 1.10.1, 1.10.2, 1.10.2, 1.10.4, 1.10.4, 1.11.0, 1.11.0, 1.11.1, 1.11.1, 1.11.2, 1.11.2, 1.11.3, 1.11.3, 1.12.0, 1.12.0, 1.12.1, 1.12.1, 1.13.0, 1.13.0, 1.13.1, 1.13.1, 1.13.3, 1.13.3, 1.14.0, 1.14.0, 1.14.1, 1.14.1, 1.14.2, 1.14.2, 1.14.3, 1.14.3, 1.14.4, 1.14.4, 1.14.5, 1.14.5, 1.14.6, 1.14.6, 1.15.0, 1.15.0, 1.15.1, 1.15.1, 1.15.2, 1.15.2, 1.15.3, 1.15.3, 1.15.4, 1.15.4, 1.16.0, 1.16.0, 1.16.1, 1.16.1, 1.16.2, 1.16.2, 1.16.3, 1.16.3, 1.16.4, 1.16.4, 1.16.5, 1.16.5, 1.16.6, 1.16.6, 1.17.0, 1.17.0, 1.17.1, 1.17.1, 1.17.2, 1.17.2, 1.17.3, 1.17.3, 1.17.4, 1.17.4, 1.17.5, 1.17.5, 1.18.0, 1.18.0, 1.18.1, 1.18.1, 1.18.2, 1.18.2, 1.18.3, 1.18.3, 1.18.4, 1.18.4
Skipped pre-versions: 1.11.0b3, 1.11.0b3, 1.11.0rc1, 1.11.0rc1, 1.11.0rc2, 1.11.0rc2, 1.11.1rc1, 1.11.1rc1, 1.11.2rc1, 1.11.2rc1, 1.12.0b1, 1.12.0b1, 1.12.0rc1, 1.12.0rc2, 1.12.0rc2, 1.12.1rc1, 1.12.1rc1, 1.13.0rc1, 1.13.0rc1, 1.13.0rc2, 1.13.0rc2, 1.14.0rc1, 1.14.0rc1, 1.15.0rc1, 1.15.0rc1, 1.15.0rc2, 1.15.0rc2, 1.16.0rc1, 1.16.0rc1, 1.16.0rc2, 1.16.0rc2, 1.17.0rc1, 1.17.0rc1, 1.17.0rc2, 1.17.0rc2, 1.18.0rc1, 1.18.0rc1, 1.19.0rc1, 1.19.0rc1, 1.19.0rc1, 1.19.0rc2, 1.19.0rc2, 1.19.0rc2
There are incompatible versions in the resolved dependencies:
  numpy<1.15.0 (from -r /tmp/pipenvxzu9oeb4requirements/pipenv-v9bklki1-constraints.txt (line 6))
  numpy>=1.10 (from resampy==0.2.2->librosa==0.5.1->-r /tmp/pipenvxzu9oeb4requirements/pipenv-v9bklki1-constraints.txt (line 5))
  numpy>=1.13.3 (from scikit-learn==0.23.1->librosa==0.5.1->-r /tmp/pipenvxzu9oeb4requirements/pipenv-v9bklki1-constraints.txt (line 5))
  numpy>=1.13.3 (from scipy==1.4.1->-r /tmp/pipenvxzu9oeb4requirements/pipenv-v9bklki1-constraints.txt (line 3))
  numpy>=1.15 (from numba==0.49.1->resampy==0.2.2->librosa==0.5.1->-r /tmp/pipenvxzu9oeb4requirements/pipenv-v9bklki1-constraints.txt (line 5))
  numpy>=1.8.0 (from librosa==0.5.1->-r /tmp/pipenvxzu9oeb4requirements/pipenv-v9bklki1-constraints.txt (line 5))

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/local/lib/python3.6/site-packages/pipenv/resolver.py", line 807, in <module>
    main()
  File "/usr/local/lib/python3.6/site-packages/pipenv/resolver.py", line 803, in main
    parsed.requirements_dir, parsed.packages, parse_only=parsed.parse_only)
  File "/usr/local/lib/python3.6/site-packages/pipenv/resolver.py", line 785, in _main
    resolve_packages(pre, clear, verbose, system, write, requirements_dir, packages)
  File "/usr/local/lib/python3.6/site-packages/pipenv/resolver.py", line 753, in resolve_packages
    requirements_dir=requirements_dir,
  File "/usr/local/lib/python3.6/site-packages/pipenv/resolver.py", line 736, in resolve
    req_dir=requirements_dir
  File "/usr/local/lib/python3.6/site-packages/pipenv/utils.py", line 1386, in resolve_deps
    req_dir=req_dir,
  File "/usr/local/lib/python3.6/site-packages/pipenv/utils.py", line 1093, in actually_resolve_deps
    resolver.resolve()
  File "/usr/local/lib/python3.6/site-packages/pipenv/utils.py", line 818, in resolve
    raise ResolutionFailure(message=str(e))
pipenv.exceptions.ResolutionFailure: ERROR: Could not find a version that matches numpy<1.15.0,>=1.10,>=1.13.3,>=1.15,>=1.8.0 (from -r /tmp/pipenvxzu9oeb4requirements/pipenv-v9bklki1-constraints.txt (line 6))
Tried: 1.3.0, 1.4.1, 1.5.0, 1.5.1, 1.6.0, 1.6.0, 1.6.1, 1.6.1, 1.6.2, 1.6.2, 1.7.0, 1.7.0, 1.7.1, 1.7.1, 1.7.2, 1.7.2, 1.8.0, 1.8.0, 1.8.1, 1.8.1, 1.8.2, 1.8.2, 1.9.0, 1.9.0, 1.9.1, 1.9.1, 1.9.2, 1.9.2, 1.9.3, 1.9.3, 1.10.0.post2, 1.10.0.post2, 1.10.1, 1.10.1, 1.10.2, 1.10.2, 1.10.4, 1.10.4, 1.11.0, 1.11.0, 1.11.1, 1.11.1, 1.11.2, 1.11.2, 1.11.3, 1.11.3, 1.12.0, 1.12.0, 1.12.1, 1.12.1, 1.13.0, 1.13.0, 1.13.1, 1.13.1, 1.13.3, 1.13.3, 1.14.0, 1.14.0, 1.14.1, 1.14.1, 1.14.2, 1.14.2, 1.14.3, 1.14.3, 1.14.4, 1.14.4, 1.14.5, 1.14.5, 1.14.6, 1.14.6, 1.15.0, 1.15.0, 1.15.1, 1.15.1, 1.15.2, 1.15.2, 1.15.3, 1.15.3, 1.15.4, 1.15.4, 1.16.0, 1.16.0, 1.16.1, 1.16.1, 1.16.2, 1.16.2, 1.16.3, 1.16.3, 1.16.4, 1.16.4, 1.16.5, 1.16.5, 1.16.6, 1.16.6, 1.17.0, 1.17.0, 1.17.1, 1.17.1, 1.17.2, 1.17.2, 1.17.3, 1.17.3, 1.17.4, 1.17.4, 1.17.5, 1.17.5, 1.18.0, 1.18.0, 1.18.1, 1.18.1, 1.18.2, 1.18.2, 1.18.3, 1.18.3, 1.18.4, 1.18.4
Skipped pre-versions: 1.11.0b3, 1.11.0b3, 1.11.0rc1, 1.11.0rc1, 1.11.0rc2, 1.11.0rc2, 1.11.1rc1, 1.11.1rc1, 1.11.2rc1, 1.11.2rc1, 1.12.0b1, 1.12.0b1, 1.12.0rc1, 1.12.0rc2, 1.12.0rc2, 1.12.1rc1, 1.12.1rc1, 1.13.0rc1, 1.13.0rc1, 1.13.0rc2, 1.13.0rc2, 1.14.0rc1, 1.14.0rc1, 1.15.0rc1, 1.15.0rc1, 1.15.0rc2, 1.15.0rc2, 1.16.0rc1, 1.16.0rc1, 1.16.0rc2, 1.16.0rc2, 1.17.0rc1, 1.17.0rc1, 1.17.0rc2, 1.17.0rc2, 1.18.0rc1, 1.18.0rc1, 1.19.0rc1, 1.19.0rc1, 1.19.0rc1, 1.19.0rc2, 1.19.0rc2, 1.19.0rc2
There are incompatible versions in the resolved dependencies:
  numpy<1.15.0 (from -r /tmp/pipenvxzu9oeb4requirements/pipenv-v9bklki1-constraints.txt (line 6))
  numpy>=1.10 (from resampy==0.2.2->librosa==0.5.1->-r /tmp/pipenvxzu9oeb4requirements/pipenv-v9bklki1-constraints.txt (line 5))
  numpy>=1.13.3 (from scikit-learn==0.23.1->librosa==0.5.1->-r /tmp/pipenvxzu9oeb4requirements/pipenv-v9bklki1-constraints.txt (line 5))
  numpy>=1.13.3 (from scipy==1.4.1->-r /tmp/pipenvxzu9oeb4requirements/pipenv-v9bklki1-constraints.txt (line 3))
  numpy>=1.15 (from numba==0.49.1->resampy==0.2.2->librosa==0.5.1->-r /tmp/pipenvxzu9oeb4requirements/pipenv-v9bklki1-constraints.txt (line 5))
  numpy>=1.8.0 (from librosa==0.5.1->-r /tmp/pipenvxzu9oeb4requirements/pipenv-v9bklki1-constraints.txt (line 5))
ROUND 1
Current constraints:
  audioread==2.1.6 (from -r /tmp/pipenvxzu9oeb4requirements/pipenv-v9bklki1-constraints.txt (line 4))
  librosa<0.6 (from -r /tmp/pipenvxzu9oeb4requirements/pipenv-v9bklki1-constraints.txt (line 5))
  numpy<1.15.0 (from -r /tmp/pipenvxzu9oeb4requirements/pipenv-v9bklki1-constraints.txt (line 6))
  pydub (from -r /tmp/pipenvxzu9oeb4requirements/pipenv-v9bklki1-constraints.txt (line 2))
  scipy>=0.18.1 (from -r /tmp/pipenvxzu9oeb4requirements/pipenv-v9bklki1-constraints.txt (line 3))

Finding the best candidates:
  found candidate audioread==2.1.6 (constraint was ==2.1.6)
  found candidate librosa==0.5.1 (constraint was <0.6)
  found candidate numpy==1.14.6 (constraint was <1.15.0)
  found candidate pydub==0.24.0 (constraint was <any>)
  found candidate scipy==1.4.1 (constraint was >=0.18.1)

Finding secondary dependencies:
  scipy==1.4.1              requires numpy>=1.13.3
  librosa==0.5.1            requires audioread>=2.0.0, decorator>=3.0.0, joblib>=0.7.0, numpy>=1.8.0, resampy>=0.1.2, scikit-learn>=0.14.0, scipy>=0.13.0, six>=1.3
  pydub==0.24.0             requires -
  numpy==1.14.6             requires -
  audioread==2.1.6          requires -

New dependencies found in this round:
  adding ['audioread', '>=2.0.0', '[]']
  adding ['decorator', '>=3.0.0', '[]']
  adding ['joblib', '>=0.7.0', '[]']
  adding ['numpy', '>=1.13.3,>=1.8.0', '[]']
  adding ['resampy', '>=0.1.2', '[]']
  adding ['scikit-learn', '>=0.14.0', '[]']
  adding ['scipy', '>=0.13.0', '[]']
  adding ['six', '>=1.3', '[]']
Removed dependencies in this round:
------------------------------------------------------------
Result of round 1: not stable

                          ROUND 2
Current constraints:
  audioread==2.1.6,>=2.0.0 (from -r /tmp/pipenvxzu9oeb4requirements/pipenv-v9bklki1-constraints.txt (line 4))
  decorator>=3.0.0 (from librosa==0.5.1->-r /tmp/pipenvxzu9oeb4requirements/pipenv-v9bklki1-constraints.txt (line 5))
  joblib>=0.7.0 (from librosa==0.5.1->-r /tmp/pipenvxzu9oeb4requirements/pipenv-v9bklki1-constraints.txt (line 5))
  librosa<0.6 (from -r /tmp/pipenvxzu9oeb4requirements/pipenv-v9bklki1-constraints.txt (line 5))
  numpy<1.15.0,>=1.13.3,>=1.8.0 (from -r /tmp/pipenvxzu9oeb4requirements/pipenv-v9bklki1-constraints.txt (line 6))
  pydub (from -r /tmp/pipenvxzu9oeb4requirements/pipenv-v9bklki1-constraints.txt (line 2))
  resampy>=0.1.2 (from librosa==0.5.1->-r /tmp/pipenvxzu9oeb4requirements/pipenv-v9bklki1-constraints.txt (line 5))
  scikit-learn>=0.14.0 (from librosa==0.5.1->-r /tmp/pipenvxzu9oeb4requirements/pipenv-v9bklki1-constraints.txt (line 5))
  scipy>=0.13.0,>=0.18.1 (from -r /tmp/pipenvxzu9oeb4requirements/pipenv-v9bklki1-constraints.txt (line 3))
  six>=1.3 (from librosa==0.5.1->-r /tmp/pipenvxzu9oeb4requirements/pipenv-v9bklki1-constraints.txt (line 5))

Finding the best candidates:
  found candidate audioread==2.1.6 (constraint was >=2.0.0,==2.1.6)
  found candidate decorator==4.4.2 (constraint was >=3.0.0)
  found candidate joblib==0.15.1 (constraint was >=0.7.0)
  found candidate librosa==0.5.1 (constraint was <0.6)
  found candidate numpy==1.14.6 (constraint was >=1.13.3,<1.15.0,>=1.8.0)
  found candidate pydub==0.24.0 (constraint was <any>)
  found candidate resampy==0.2.2 (constraint was >=0.1.2)
  found candidate scikit-learn==0.23.1 (constraint was >=0.14.0)
  found candidate scipy==1.4.1 (constraint was >=0.13.0,>=0.18.1)
  found candidate six==1.15.0 (constraint was >=1.3)

Finding secondary dependencies:
  scipy==1.4.1              requires numpy>=1.13.3
  resampy==0.2.2            requires numba>=0.32, numpy>=1.10, scipy>=0.13, six>=1.3
  scikit-learn==0.23.1      requires joblib>=0.11, numpy>=1.13.3, scipy>=0.19.1, threadpoolctl>=2.0.0
  librosa==0.5.1            requires audioread>=2.0.0, decorator>=3.0.0, joblib>=0.7.0, numpy>=1.8.0, resampy>=0.1.2, scikit-learn>=0.14.0, scipy>=0.13.0, six>=1.3
  pydub==0.24.0             requires -
  decorator==4.4.2          requires -
  numpy==1.14.6             requires -
  six==1.15.0               requires -
  joblib==0.15.1            requires -
  audioread==2.1.6          requires -

New dependencies found in this round:
  adding ['joblib', '>=0.11,>=0.7.0', '[]']
  adding ['numba', '>=0.32', '[]']
  adding ['numpy', '>=1.10,>=1.13.3,>=1.8.0', '[]']
  adding ['scipy', '>=0.13,>=0.13.0,>=0.19.1', '[]']
  adding ['threadpoolctl', '>=2.0.0', '[]']
Removed dependencies in this round:
  removing ['joblib', '>=0.7.0', '[]']
  removing ['numpy', '>=1.13.3,>=1.8.0', '[]']
  removing ['scipy', '>=0.13.0', '[]']
------------------------------------------------------------
Result of round 2: not stable

                          ROUND 3
Current constraints:
  audioread==2.1.6,>=2.0.0 (from -r /tmp/pipenvxzu9oeb4requirements/pipenv-v9bklki1-constraints.txt (line 4))
  decorator>=3.0.0 (from librosa==0.5.1->-r /tmp/pipenvxzu9oeb4requirements/pipenv-v9bklki1-constraints.txt (line 5))
  joblib>=0.11,>=0.7.0 (from librosa==0.5.1->-r /tmp/pipenvxzu9oeb4requirements/pipenv-v9bklki1-constraints.txt (line 5))
  librosa<0.6 (from -r /tmp/pipenvxzu9oeb4requirements/pipenv-v9bklki1-constraints.txt (line 5))
  numba>=0.32 (from resampy==0.2.2->librosa==0.5.1->-r /tmp/pipenvxzu9oeb4requirements/pipenv-v9bklki1-constraints.txt (line 5))
  numpy<1.15.0,>=1.10,>=1.13.3,>=1.8.0 (from -r /tmp/pipenvxzu9oeb4requirements/pipenv-v9bklki1-constraints.txt (line 6))
  pydub (from -r /tmp/pipenvxzu9oeb4requirements/pipenv-v9bklki1-constraints.txt (line 2))
  resampy>=0.1.2 (from librosa==0.5.1->-r /tmp/pipenvxzu9oeb4requirements/pipenv-v9bklki1-constraints.txt (line 5))
  scikit-learn>=0.14.0 (from librosa==0.5.1->-r /tmp/pipenvxzu9oeb4requirements/pipenv-v9bklki1-constraints.txt (line 5))
  scipy>=0.13,>=0.13.0,>=0.18.1,>=0.19.1 (from -r /tmp/pipenvxzu9oeb4requirements/pipenv-v9bklki1-constraints.txt (line 3))
  six>=1.3 (from librosa==0.5.1->-r /tmp/pipenvxzu9oeb4requirements/pipenv-v9bklki1-constraints.txt (line 5))
  threadpoolctl>=2.0.0 (from scikit-learn==0.23.1->librosa==0.5.1->-r /tmp/pipenvxzu9oeb4requirements/pipenv-v9bklki1-constraints.txt (line 5))

Finding the best candidates:
  found candidate audioread==2.1.6 (constraint was >=2.0.0,==2.1.6)
  found candidate decorator==4.4.2 (constraint was >=3.0.0)
  found candidate joblib==0.15.1 (constraint was >=0.11,>=0.7.0)
  found candidate librosa==0.5.1 (constraint was <0.6)
  found candidate numba==0.49.1 (constraint was >=0.32)
  found candidate numpy==1.14.6 (constraint was >=1.10,>=1.13.3,<1.15.0,>=1.8.0)
  found candidate pydub==0.24.0 (constraint was <any>)
  found candidate resampy==0.2.2 (constraint was >=0.1.2)
  found candidate scikit-learn==0.23.1 (constraint was >=0.14.0)
  found candidate scipy==1.4.1 (constraint was >=0.13,>=0.13.0,>=0.18.1,>=0.19.1)
  found candidate six==1.15.0 (constraint was >=1.3)
  found candidate threadpoolctl==2.1.0 (constraint was >=2.0.0)

Finding secondary dependencies:
  resampy==0.2.2            requires numba>=0.32, numpy>=1.10, scipy>=0.13, six>=1.3
  decorator==4.4.2          requires -
  six==1.15.0               requires -
  pydub==0.24.0             requires -
  librosa==0.5.1            requires audioread>=2.0.0, decorator>=3.0.0, joblib>=0.7.0, numpy>=1.8.0, resampy>=0.1.2, scikit-learn>=0.14.0, scipy>=0.13.0, six>=1.3
  scipy==1.4.1              requires numpy>=1.13.3
  joblib==0.15.1            requires -
  scikit-learn==0.23.1      requires joblib>=0.11, numpy>=1.13.3, scipy>=0.19.1, threadpoolctl>=2.0.0
  audioread==2.1.6          requires -
  threadpoolctl==2.1.0      requires -
  numpy==1.14.6             requires -
  numba==0.49.1             requires llvmlite<=0.33.0.dev0,>=0.31.0.dev0, numpy>=1.15, setuptools

New dependencies found in this round:
  adding ['llvmlite', '<=0.33.0.dev0,>=0.31.0.dev0', '[]']
  adding ['numpy', '>=1.10,>=1.13.3,>=1.15,>=1.8.0', '[]']
  adding ['setuptools', '', '[]']
Removed dependencies in this round:
  removing ['numpy', '>=1.10,>=1.13.3,>=1.8.0', '[]']
------------------------------------------------------------
Result of round 3: not stable

                          ROUND 4
Current constraints:
  audioread==2.1.6,>=2.0.0 (from -r /tmp/pipenvxzu9oeb4requirements/pipenv-v9bklki1-constraints.txt (line 4))
  decorator>=3.0.0 (from librosa==0.5.1->-r /tmp/pipenvxzu9oeb4requirements/pipenv-v9bklki1-constraints.txt (line 5))
  joblib>=0.11,>=0.7.0 (from librosa==0.5.1->-r /tmp/pipenvxzu9oeb4requirements/pipenv-v9bklki1-constraints.txt (line 5))
  librosa<0.6 (from -r /tmp/pipenvxzu9oeb4requirements/pipenv-v9bklki1-constraints.txt (line 5))
  llvmlite<=0.33.0.dev0,>=0.31.0.dev0 (from numba==0.49.1->resampy==0.2.2->librosa==0.5.1->-r /tmp/pipenvxzu9oeb4requirements/pipenv-v9bklki1-constraints.txt (line 5))
  numba>=0.32 (from resampy==0.2.2->librosa==0.5.1->-r /tmp/pipenvxzu9oeb4requirements/pipenv-v9bklki1-constraints.txt (line 5))
  numpy<1.15.0,>=1.10,>=1.13.3,>=1.15,>=1.8.0 (from -r /tmp/pipenvxzu9oeb4requirements/pipenv-v9bklki1-constraints.txt (line 6))
  pydub (from -r /tmp/pipenvxzu9oeb4requirements/pipenv-v9bklki1-constraints.txt (line 2))
  resampy>=0.1.2 (from librosa==0.5.1->-r /tmp/pipenvxzu9oeb4requirements/pipenv-v9bklki1-constraints.txt (line 5))
  scikit-learn>=0.14.0 (from librosa==0.5.1->-r /tmp/pipenvxzu9oeb4requirements/pipenv-v9bklki1-constraints.txt (line 5))
  scipy>=0.13,>=0.13.0,>=0.18.1,>=0.19.1 (from -r /tmp/pipenvxzu9oeb4requirements/pipenv-v9bklki1-constraints.txt (line 3))
  setuptools (from numba==0.49.1->resampy==0.2.2->librosa==0.5.1->-r /tmp/pipenvxzu9oeb4requirements/pipenv-v9bklki1-constraints.txt (line 5))
  six>=1.3 (from librosa==0.5.1->-r /tmp/pipenvxzu9oeb4requirements/pipenv-v9bklki1-constraints.txt (line 5))
  threadpoolctl>=2.0.0 (from scikit-learn==0.23.1->librosa==0.5.1->-r /tmp/pipenvxzu9oeb4requirements/pipenv-v9bklki1-constraints.txt (line 5))

Finding the best candidates:
  found candidate audioread==2.1.6 (constraint was >=2.0.0,==2.1.6)
  found candidate decorator==4.4.2 (constraint was >=3.0.0)
  found candidate joblib==0.15.1 (constraint was >=0.11,>=0.7.0)
  found candidate librosa==0.5.1 (constraint was <0.6)
  found candidate llvmlite==0.32.1 (constraint was >=0.31.0.dev0,<=0.33.0.dev0)
  found candidate numba==0.49.1 (constraint was >=0.32)
Traceback (most recent call last):
  File "/usr/local/lib/python3.6/site-packages/pipenv/utils.py", line 808, in resolve
    results = self.resolver.resolve(max_rounds=environments.PIPENV_MAX_ROUNDS)
  File "/usr/local/lib/python3.6/site-packages/pipenv/patched/piptools/resolver.py", line 180, in resolve
    has_changed, best_matches = self._resolve_one_round()
  File "/usr/local/lib/python3.6/site-packages/pipenv/patched/piptools/resolver.py", line 260, in _resolve_one_round
    best_matches = {self.get_best_match(ireq) for ireq in constraints}
  File "/usr/local/lib/python3.6/site-packages/pipenv/patched/piptools/resolver.py", line 260, in <setcomp>
    best_matches = {self.get_best_match(ireq) for ireq in constraints}
  File "/usr/local/lib/python3.6/site-packages/pipenv/patched/piptools/resolver.py", line 320, in get_best_match
    ireq, prereleases=self.prereleases
  File "/usr/local/lib/python3.6/site-packages/pipenv/patched/piptools/repositories/pypi.py", line 202, in find_best_match
    raise NoCandidateFound(ireq, all_candidates, self.finder)
pipenv.patched.piptools.exceptions.NoCandidateFound: Could not find a version that matches numpy<1.15.0,>=1.10,>=1.13.3,>=1.15,>=1.8.0 (from -r /tmp/pipenvxzu9oeb4requirements/pipenv-v9bklki1-constraints.txt (line 6))
Tried: 1.3.0, 1.4.1, 1.5.0, 1.5.1, 1.6.0, 1.6.0, 1.6.1, 1.6.1, 1.6.2, 1.6.2, 1.7.0, 1.7.0, 1.7.1, 1.7.1, 1.7.2, 1.7.2, 1.8.0, 1.8.0, 1.8.1, 1.8.1, 1.8.2, 1.8.2, 1.9.0, 1.9.0, 1.9.1, 1.9.1, 1.9.2, 1.9.2, 1.9.3, 1.9.3, 1.10.0.post2, 1.10.0.post2, 1.10.1, 1.10.1, 1.10.2, 1.10.2, 1.10.4, 1.10.4, 1.11.0, 1.11.0, 1.11.1, 1.11.1, 1.11.2, 1.11.2, 1.11.3, 1.11.3, 1.12.0, 1.12.0, 1.12.1, 1.12.1, 1.13.0, 1.13.0, 1.13.1, 1.13.1, 1.13.3, 1.13.3, 1.14.0, 1.14.0, 1.14.1, 1.14.1, 1.14.2, 1.14.2, 1.14.3, 1.14.3, 1.14.4, 1.14.4, 1.14.5, 1.14.5, 1.14.6, 1.14.6, 1.15.0, 1.15.0, 1.15.1, 1.15.1, 1.15.2, 1.15.2, 1.15.3, 1.15.3, 1.15.4, 1.15.4, 1.16.0, 1.16.0, 1.16.1, 1.16.1, 1.16.2, 1.16.2, 1.16.3, 1.16.3, 1.16.4, 1.16.4, 1.16.5, 1.16.5, 1.16.6, 1.16.6, 1.17.0, 1.17.0, 1.17.1, 1.17.1, 1.17.2, 1.17.2, 1.17.3, 1.17.3, 1.17.4, 1.17.4, 1.17.5, 1.17.5, 1.18.0, 1.18.0, 1.18.1, 1.18.1, 1.18.2, 1.18.2, 1.18.3, 1.18.3, 1.18.4, 1.18.4
Skipped pre-versions: 1.11.0b3, 1.11.0b3, 1.11.0rc1, 1.11.0rc1, 1.11.0rc2, 1.11.0rc2, 1.11.1rc1, 1.11.1rc1, 1.11.2rc1, 1.11.2rc1, 1.12.0b1, 1.12.0b1, 1.12.0rc1, 1.12.0rc2, 1.12.0rc2, 1.12.1rc1, 1.12.1rc1, 1.13.0rc1, 1.13.0rc1, 1.13.0rc2, 1.13.0rc2, 1.14.0rc1, 1.14.0rc1, 1.15.0rc1, 1.15.0rc1, 1.15.0rc2, 1.15.0rc2, 1.16.0rc1, 1.16.0rc1, 1.16.0rc2, 1.16.0rc2, 1.17.0rc1, 1.17.0rc1, 1.17.0rc2, 1.17.0rc2, 1.18.0rc1, 1.18.0rc1, 1.19.0rc1, 1.19.0rc1, 1.19.0rc1, 1.19.0rc2, 1.19.0rc2, 1.19.0rc2
There are incompatible versions in the resolved dependencies:
  numpy<1.15.0 (from -r /tmp/pipenvxzu9oeb4requirements/pipenv-v9bklki1-constraints.txt (line 6))
  numpy>=1.10 (from resampy==0.2.2->librosa==0.5.1->-r /tmp/pipenvxzu9oeb4requirements/pipenv-v9bklki1-constraints.txt (line 5))
  numpy>=1.13.3 (from scikit-learn==0.23.1->librosa==0.5.1->-r /tmp/pipenvxzu9oeb4requirements/pipenv-v9bklki1-constraints.txt (line 5))
  numpy>=1.13.3 (from scipy==1.4.1->-r /tmp/pipenvxzu9oeb4requirements/pipenv-v9bklki1-constraints.txt (line 3))
  numpy>=1.15 (from numba==0.49.1->resampy==0.2.2->librosa==0.5.1->-r /tmp/pipenvxzu9oeb4requirements/pipenv-v9bklki1-constraints.txt (line 5))
  numpy>=1.8.0 (from librosa==0.5.1->-r /tmp/pipenvxzu9oeb4requirements/pipenv-v9bklki1-constraints.txt (line 5))

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/local/lib/python3.6/site-packages/pipenv/resolver.py", line 807, in <module>
    main()
  File "/usr/local/lib/python3.6/site-packages/pipenv/resolver.py", line 803, in main
    parsed.requirements_dir, parsed.packages, parse_only=parsed.parse_only)
  File "/usr/local/lib/python3.6/site-packages/pipenv/resolver.py", line 785, in _main
    resolve_packages(pre, clear, verbose, system, write, requirements_dir, packages)
  File "/usr/local/lib/python3.6/site-packages/pipenv/resolver.py", line 753, in resolve_packages
    requirements_dir=requirements_dir,
  File "/usr/local/lib/python3.6/site-packages/pipenv/resolver.py", line 736, in resolve
    req_dir=requirements_dir
  File "/usr/local/lib/python3.6/site-packages/pipenv/utils.py", line 1386, in resolve_deps
    req_dir=req_dir,
  File "/usr/local/lib/python3.6/site-packages/pipenv/utils.py", line 1093, in actually_resolve_deps
    resolver.resolve()
  File "/usr/local/lib/python3.6/site-packages/pipenv/utils.py", line 818, in resolve
    raise ResolutionFailure(message=str(e))
pipenv.exceptions.ResolutionFailure: ERROR: Could not find a version that matches numpy<1.15.0,>=1.10,>=1.13.3,>=1.15,>=1.8.0 (from -r /tmp/pipenvxzu9oeb4requirements/pipenv-v9bklki1-constraints.txt (line 6))
Tried: 1.3.0, 1.4.1, 1.5.0, 1.5.1, 1.6.0, 1.6.0, 1.6.1, 1.6.1, 1.6.2, 1.6.2, 1.7.0, 1.7.0, 1.7.1, 1.7.1, 1.7.2, 1.7.2, 1.8.0, 1.8.0, 1.8.1, 1.8.1, 1.8.2, 1.8.2, 1.9.0, 1.9.0, 1.9.1, 1.9.1, 1.9.2, 1.9.2, 1.9.3, 1.9.3, 1.10.0.post2, 1.10.0.post2, 1.10.1, 1.10.1, 1.10.2, 1.10.2, 1.10.4, 1.10.4, 1.11.0, 1.11.0, 1.11.1, 1.11.1, 1.11.2, 1.11.2, 1.11.3, 1.11.3, 1.12.0, 1.12.0, 1.12.1, 1.12.1, 1.13.0, 1.13.0, 1.13.1, 1.13.1, 1.13.3, 1.13.3, 1.14.0, 1.14.0, 1.14.1, 1.14.1, 1.14.2, 1.14.2, 1.14.3, 1.14.3, 1.14.4, 1.14.4, 1.14.5, 1.14.5, 1.14.6, 1.14.6, 1.15.0, 1.15.0, 1.15.1, 1.15.1, 1.15.2, 1.15.2, 1.15.3, 1.15.3, 1.15.4, 1.15.4, 1.16.0, 1.16.0, 1.16.1, 1.16.1, 1.16.2, 1.16.2, 1.16.3, 1.16.3, 1.16.4, 1.16.4, 1.16.5, 1.16.5, 1.16.6, 1.16.6, 1.17.0, 1.17.0, 1.17.1, 1.17.1, 1.17.2, 1.17.2, 1.17.3, 1.17.3, 1.17.4, 1.17.4, 1.17.5, 1.17.5, 1.18.0, 1.18.0, 1.18.1, 1.18.1, 1.18.2, 1.18.2, 1.18.3, 1.18.3, 1.18.4, 1.18.4
Skipped pre-versions: 1.11.0b3, 1.11.0b3, 1.11.0rc1, 1.11.0rc1, 1.11.0rc2, 1.11.0rc2, 1.11.1rc1, 1.11.1rc1, 1.11.2rc1, 1.11.2rc1, 1.12.0b1, 1.12.0b1, 1.12.0rc1, 1.12.0rc2, 1.12.0rc2, 1.12.1rc1, 1.12.1rc1, 1.13.0rc1, 1.13.0rc1, 1.13.0rc2, 1.13.0rc2, 1.14.0rc1, 1.14.0rc1, 1.15.0rc1, 1.15.0rc1, 1.15.0rc2, 1.15.0rc2, 1.16.0rc1, 1.16.0rc1, 1.16.0rc2, 1.16.0rc2, 1.17.0rc1, 1.17.0rc1, 1.17.0rc2, 1.17.0rc2, 1.18.0rc1, 1.18.0rc1, 1.19.0rc1, 1.19.0rc1, 1.19.0rc1, 1.19.0rc2, 1.19.0rc2, 1.19.0rc2
There are incompatible versions in the resolved dependencies:
  numpy<1.15.0 (from -r /tmp/pipenvxzu9oeb4requirements/pipenv-v9bklki1-constraints.txt (line 6))
  numpy>=1.10 (from resampy==0.2.2->librosa==0.5.1->-r /tmp/pipenvxzu9oeb4requirements/pipenv-v9bklki1-constraints.txt (line 5))
  numpy>=1.13.3 (from scikit-learn==0.23.1->librosa==0.5.1->-r /tmp/pipenvxzu9oeb4requirements/pipenv-v9bklki1-constraints.txt (line 5))
  numpy>=1.13.3 (from scipy==1.4.1->-r /tmp/pipenvxzu9oeb4requirements/pipenv-v9bklki1-constraints.txt (line 3))
  numpy>=1.15 (from numba==0.49.1->resampy==0.2.2->librosa==0.5.1->-r /tmp/pipenvxzu9oeb4requirements/pipenv-v9bklki1-constraints.txt (line 5))
  numpy>=1.8.0 (from librosa==0.5.1->-r /tmp/pipenvxzu9oeb4requirements/pipenv-v9bklki1-constraints.txt (line 5))
[a.ilyushenkov@ilyushenkov-mbp pipenv_bug]$

<details><summary>$ pipenv --support</summary>

Pipenv version: `'2020.6.2'`

Pipenv location: `'/usr/local/lib/python3.6/site-packages/pipenv'`

Python location: `'/usr/bin/python3'`

Python installations found:

  - `3.6.8`: `/usr/bin/python3.6`
  - `3.6.8`: `/usr/bin/python3`
  - `3.6.8`: `/usr/bin/python3.6m`
  - `3.6.8`: `/bin/python3.6`
  - `3.6.8`: `/bin/python3`
  - `3.6.8`: `/bin/python3.6m`
  - `3.6.8`: `/home/a.ilyushenkov/.local/share/dephell/venvs/dephell/bin/python3.6`
  - `3.6.8`: `/home/a.ilyushenkov/.local/share/dephell/venvs/dephell/bin/python3`
  - `2.7.5`: `/usr/bin/python2`
  - `2.7.5`: `/usr/bin/python2.7`
  - `2.7.5`: `/bin/python2`
  - `2.7.5`: `/bin/python2.7`

PEP 508 Information:

{'implementation_name': 'cpython',
'implementation_version': '3.6.8',
'os_name': 'posix',
'platform_machine': 'x86_64',
'platform_python_implementation': 'CPython',
'platform_release': '4.19.76-linuxkit',
'platform_system': 'Linux',
'platform_version': '#1 SMP Tue May 26 11:42:35 UTC 2020',
'python_full_version': '3.6.8',
'python_version': '3.6',
'sys_platform': 'linux'}

System environment variables:

  - `HOSTNAME`
  - `TERM`
  - `OLDPWD`
  - `LC_ALL`
  - `LS_COLORS`
  - `PATH`
  - `PWD`
  - `LANG`
  - `HISTCONTROL`
  - `SHLVL`
  - `HOME`
  - `PIP_DISABLE_PIP_VERSION_CHECK`
  - `LESSOPEN`
  - `_`
  - `PYTHONDONTWRITEBYTECODE`
  - `PIP_SHIMS_BASE_MODULE`
  - `PIP_PYTHON_PATH`
  - `PYTHONFINDER_IGNORE_UNSUPPORTED`

Pipenv–specific environment variables:

Debug–specific environment variables:

  - `PATH`: `/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/home/a.ilyushenkov/.local/share/dephell/venvs/dephell/bin`
  - `LANG`: `en_US.UTF-8`
  - `PWD`: `/home/a.ilyushenkov/workspace/pipenv_bug`

---------------------------

Contents of `Pipfile` ('/home/a.ilyushenkov/workspace/pipenv_bug/Pipfile'):

```toml
[packages]
librosa = "<0.6"
scipy = ">=0.18.1"
pydub = "*"
audioread = "==2.1.6"
numpy = "<1.15.0"

[dev-packages]

[requires]
python_version = "3.6"

```

Pipenv reuses the ability of pip-tools for resolving dependencies. The resolver itself can't fall back to older versions of numba to see if any of the candidates depends on a compatible version of numpy.
To workaround this situation, you should pin numba==0.47.0 in the Pipfile.

Hi,
I encauntered a similar issue. For me pinning is not a solution, as not needing to pin was a reason to move to pipenv.
For me #4777 solves this issue. Maybe you want to have a look.
Best regards,
Franz


KeyError: "TopDown: 'LiteHRNet is not in the models registry'"

遇到了一个这样的问题：KeyError: "TopDown: 'LiteHRNet is not in the models registry'"
不知道是什么原因造成的。感谢大家帮忙解答！

Has this problem been solved?


null is not an object (evaluating 'RNGestureHandlerModule.State')

……
It's happen to me.
And I deal it.
If you have same issue and you use cocopod.
You need run  'pod install' after run 'react-native link'.
My env is:
"react": "16.6.3",
"react-native": "0.58.4",
"react-native-gesture-handler": "^1.0.15",
"react-navigation": "^3.2.1",

mine still not working

mine still not working

me too


Remove tracking of RequestCancelKey to CancellationToken

We want to implement cancellation on top of Swift concurrency’s cancellation, which will most likely need a completely different paradigm.

@swift-ci Please test

Closing this because I’ve included it in the https://github.com/apple/sourcekit-lsp/tree/ahoppen/asyncification branch, in which I’m collecting all the asyncification changes, which will then be merged into main in one go.


Fail to fetch the robots.txt file stops the crawler

If for some reason fetching the robots.txt throws and exception the crawler stops. Setting ignoreRobots has no effect because fetching the file happens before checking if we want to ignore it or not.
Maybe we can catch any exception when trying to fetch the robots.txt file and then check if we want to honor it and it is not null?
What do you think @freekmurze?

I will close this issue and move it to the spatie/crawler repository


PostgresSQLEnum arrays error

I have this enum
enum Permission: String, PostgreSQLEnum, PostgreSQLMigration {
    ...
    case asset_create = "asset:create"
    case asset_delete = "asset:delete"
    case asset_read = "asset:read"
    case asset_update = "asset:update"
    ...
}

this Entity:
final class Role: PostgreSQLUUIDModel, Migration, Content {
    static var entity = "roles"

    var id: UUID?
    var name: String
    var permissions: [Permission]

    init(name: String, permissions: [Permission]) {
        self.name = name
        self.permissions = permissions
    }
}

this migration:
struct RoleDemo: Migration {
    typealias Database = PostgreSQLDatabase

    static func prepare(on connection: PostgreSQLConnection) -> Future<Void> {
        let role = Role(
            name: "Demo",
            permissions: [.asset_create, .item_create]
        )

        return role.save(on: connection).transform(to: ())
    }

    static func revert(on connection: PostgreSQLConnection) -> Future<Void> {
        return .done(on: connection)
    }
}

And finally... This error:
Thread 1: Fatal error: Error raised at top level: ⚠ PostgreSQL Error: column "permissions" is of type permission[] but expression is of type text[]
- id: PostgreSQLError.server.error.transformAssignedExpr

These suggestions could address the issue:
- You will need to rewrite or cast the expression.

Have you added Permission as a migration in your configure.swift, prior to its use within the Role migration?
var migrations = MigrationConfig()
migrations.add(migration: Permission.self, database: .psql)
migrations.add(model: Role.self, database: .psql)
// ...
services.register(migrations)```

@gperdomor Did you find a workaround for this issue?

@docterd no :(

Any workaround or maybe is there already solution for it?

@Janoz94 to clarify my idea for a workaround, you could store the enum values as [String], and then have a mutable computed property on the model that converts to / from [MyEnum]. No solution has been found yet, but I'll make sure it gets fixed by the next major release at the latest.

I have this exact same issue. Happy to see it’s got a healthy discussion. I’d love to either see this feature work as intended or have a best practices documentation so other devs don’t step on the same landmine.

This is fixed in Fluent 4. The workarounds mentioned here are the best option for Fluent 3.


Upgrade storybook & organize components into hierarchies

Hi team,
Here's a PR - you can see what it looks like here:
https://sumup.github.io/circuit-ui/
A few changes I'm suggesting:

Upgrade storybook to 3.4
Add storysource plugin (replace info? Or does anyone know if we can customize the component info reports on)
Organized the components into groups: Layout, Components, Forms, Grid, Typography, Icons.
Similar components, I placed in the hiearchy under the main component (see Calendar and CreditCardDetails)

PENDING:
For some reason, storysource doesn't like the CreditCardDetails story. Any ideas of something funny you're doing there @felixjung?

Edit, the build error is:
  3:1  error  '@storybook/react' should be listed in the project's dependencies, not devDependencies       import/no-extraneous-dependencies
  4:1  error  '@storybook/addon-info' should be listed in the project's dependencies, not devDependencies  import/no-extraneous-dependencies

What's the situtation here? Should I really move them, or is this mis-reporting by this linting condition or these libraries are mis-reporting where they belong in the package.json?

Would it be possible to rearrange the Storybook addons to show the knobs first (so they're selected by default)?

@connor-baer Good question. I will check if the order can be changed by altering the order they're registered in, or something like that.

@elanoism Duh! Makes sense. I need to figure out how to fix that story before merging anyways.

@connor-baer @mlent for the addons order all you have to do is change the import order in addons.js


Setup papermill integration tests

Have tox setup and install papermill
Use integration test notebooks executed by papermill runner as test coverage
Test Coverage: %requirements_load
Test Coverage: %pex_load
Test Coverage: %pants_load (and %pants_repo)

after rethinking this, it won't be possible to use papermill in the CI path to exercise example notebooks due to the explicit !pip install step (which pulls from pypi vs the repo) - abandoning.


fix: QnA Maker EndpointKey is null Issue

Description
This PR is to fix this Issue
Root Cause
This Issue is because the botproject(runtime) read qna.endpointkey from disk before. After we omitted it, we need to send this from composer server to botproject(runtime).
Task Item
closes #1538
Type of change
Please delete options that are not relevant.

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Code refactor (non-breaking change which improve code quality, clean up, add tests, etc)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Doc update (document update)

Checklist

[ ] I have added tests that prove my fix is effective or that my feature works
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have functionally tested my change

Screenshots
During the QnaMaker trace, it won't show "Object not set to instance of an object" anymore.

The design here is odd. What happens when there are multiple QnA kb's in play? This looks to hardcode the qna key on the settings object.

The design here is odd. What happens when there are multiple QnA kb's in play? This looks to hardcode the qna key on the settings object.

Yes, Thanks for the reminding. I don't have an accurate concept of multiple QnA kb's before. I treat it as a fixed property as luis key. According to @luhan2017 and @hibrenda 's description, I try some corner cases and find it has nothing to do with the property name( no mater it's qna.knowledgebaseid /qna.endpointkey/… or not). So those key-value pairs are more like self-defined property, user who want to use QnA just need to make sure the property in settings is the same as in form.
So, I think it's hard to find a pattern to omit those sensitive properties(such like endpointkey) saving to disk. The best solution for this Issue is simply treated it as self-defined value and not omit it.
FYI. It's a case that works.

@cwhitten  Sorry, I mis-deleted my branch caused this PR closed. I send a new one here