add OwnedEntityPicker field in plugin/scaffolder

Hey, I just made a Pull Request!
Added a new field component in plugin/scaffolder
OwnedEntityPicker lists down all Entities owned by the logged-in user
spec:
  parameters:
      properties:
        EntityOwner:
          title: Your Entities
          type: string
          description: List of Entities owned by you
          ui:field: OwnedEntityPicker
          ui:options:
            allowedKinds:
              - System
            defaultKind: System

For testing the field use may use this template
https://github.com/backstage/backstage/issues/8391

Thanks for this! This is a great start!
Thinking that this is a little inefficient at the min, and I know that it's done this way in a a lot of other places too, with how we load all entities and then use the filter to check if we own it or not.
I'm wondering if we can have a go at trying doing this part from the hook https://github.com/backstage/backstage/blob/31f00e8015ef5eabbc586a5ef28e4e4871b61194/plugins/catalog-react/src/hooks/useEntityOwnership.ts#L145-L146 and building a Set of all the ownership refs, and then make one query getEntities and using the filter prop to specify ownedBy = ref1 OR ownedBy = ref2

So I worked it out because I couldn't find an example anywhere of doing this query.
But you want to grab the identityRefs and catalogRefs like before and pass them as the array to like below:
const catalogApi = useApi(catalogApiRef);
const response = useAsync(() =>
    catalogApi.getEntities({
      filter: {
        [`relations.${RELATION_OWNED_BY}`]: ['group:default/team-b', 'user:default/guest'],
      },
    }),
  );

Maybe it makes sense actually to make a hook in catalog-react that encapsulates all this and use the new hook instead of the hook that returns you a matching function. useOwnedEntities or something.

Yes, that can be a good addition as well.
I spend some time finding an API that could do the specific query to get owned entities, but couldn't find anything. Hence went with this approach

Yep - I tried looking for examples too, and it was a pain so had a little play to see if I could get it working. Thinking that we will probably want to use this approach more than the other to be honest where we can as it's really not performant for large catalogs to grab the entire catalog and filter in the client. Much better to do it serverside where we can cache the filtering etc too if needed to increase performance later down the line.

Would this restrict a user from inputing a entity name manually? Also, what happens when the user ownes 0 entities?

@benjdlambert the code snippets you shared were very helpful, created a useOwnedEntities file, have placed it in the same folder, for now, maybe later we can push it to @backstage/catalog-client
Now our component will fetch only the Entities owned by the user. Please review

but was wondering if this would restrict the current user from inputing a entity name manually
As this is only a front-end change, I don't think it will restrict or validate user's input, you might want to use custom FieldValidation for this.

We have a use case that came up around the Group entity where we were looking to have the user only pick a Group they are a member of
We can use this component and pass groups in allowedKinds

Also, what happens when the user ownes 0 entities?
No options will be visible to the user

Thanks @mufaddal7 this helps! It looks like there was a recent contribution to allow an option to disable arbitrary values within the EntityPicker - https://github.com/backstage/backstage/pull/8441 do you feel it makes sense to also include this option as well @benjdlambert ?

Let's leave that for a follow up PR - want to try and get this in for the release today :pray:

All checks cleared , feels good.
No problem,  next week it is 🎉 @benjdlambert


[Bug]: Session disconnects after 5 minutes

What happened?
I'm running LibreChat in a docker container, but after 5 minutes without writing in a chat, the session disconnects and I have to login again.
Steps to Reproduce

Log in
Interact with any chat provided (OpenAI, Together, Ollama)
Wait around 5 minutes without interacting
When I write something in the active chat, the login screen appears

What browsers are you seeing the problem on?
No response
Relevant log output
No response
Screenshots
No response
Code of Conduct

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

Please read through the following discussions:
https://github.com/danny-avila/LibreChat/discussions/572
https://github.com/danny-avila/LibreChat/discussions/3001


Add left side and right side view of vehicle

Can anyone suggest, how to add left side view and right side view of a vehicle?
Thank you.

It is not completely clear what you are trying to achieve.
We have some documentation how to display 2 logs.  This creates 2 viewports with different data sources but synchronized controls and camera.  https://avs.auto/#/streetscape.gl/advanced-topics/display-multiple-logs?section=synchronized-cameras
If you just want an additional 3d view from the same data, you should be able to create that using multiple LogViewers and updating the viewState.  I'm not 100% sure on this but if you can access the view state of you main window then you should be able to adjust the other viewstates with a fixed transform (ie left & right)

@sivakanth1989 Let me know if the above is useful or not.

@twojtasz Thank you for the reply.
My question is, right now we have 3 view modes: Perspective, top-down and Driver. Now I want to add Left view and Right view to see the vehicle from the left side and right side.
Could you please help me.

Hi @twojtasz and @srikanth-kuriyala,
Even I am looking for implementing same kind of requirement.  Mainly I am trying to achieve rear view,  can you please help me out in this?  Thank you!

@twojtasz Thank you for the reply.
My question is, right now we have 3 view modes: Perspective, top-down and Driver. Now I want to add Left view and Right view to see the vehicle from the left side and right side.
Could you please help me.

Hi, is it done yet?

Hello, nope.. still haven't done?
any suggestions?
On Sun, Jun 20, 2021 at 3:02 PM pai @.***> wrote:

@twojtasz https://github.com/twojtasz Thank you for the reply.
My question is, right now we have 3 view modes: Perspective, top-down and
Driver. Now I want to add Left view and Right view to see the vehicle from
the left side and right side.
Could you please help me.
Hi, is it done yet?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/uber/streetscape.gl/issues/346#issuecomment-864525909,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGHYNMI6FCXUYE6IQEW7PY3TTWYSLANCNFSM4HXYSMBQ
.

That's easy. you can set your car offset bearing as 90 or -90, you can get it.


Support for Rails 7

The gem appears to work fine with Rails 7.  Is there any reason for the restriction of less than rails 7?

The restriction was already lifted with pull request #105 . But it seems rubygems.org doesn't have the change yet. Probably the gem version needs to be lifted as well for rubygems to pick it up.

A new release would be appreciated.

Same here, a release would be appreciated @klaseskilson @tim-heighes-fishbrain 🙏

Maybe @dalen or @pastpatryk is able to help us? 🙏 🙏

I have release a new version. however, you will have to forgive me, but I have not 100 % verified myself that it is working properly. but I hope it is working for y'all.
full disclosure: we don't actively use administrate as of 2019 at Fishbrain.

@alexceder thank you so much! Judging from the diff, the changes shouldn't include much more than allowing Rails 7.0, so it should be fine 💪


Images for plastic products

Collect license-free images of products commonly made from ocean plastics to be displayed on mission screen.

Images for plastic products should be the same size and style as the toothbrush image. (Plain black line image tilted 45° to the left.)

Hello @DainialPadraig,
I am just a beginner to open source and was looking for some contributions when I found that you had opened some issues.
Don't know whether you still need those images but if needed then assign this to me. I will be glad to help and make some contributions to your repo.


Accommodate groups by appending assignees rather than replacing them

In the event of a group project, the Assignment Progress issue should assign to the entire team rather than just the latest author.

This has been shipped as of v0.5.0.


Website responsiveness

It's not entirely responsive between the width range 771 and 990
Check the warning message in console. There's a body tag in div
Increase the font size of 'Kranti' to make it significantly bigger than that of the nav contents, especially on bigger screen.
Make the logo a link that redirects to the home page.

To test please go to the link : https://codesandbox.io/s/github/amritsrivastava/Kranti/tree/amrit-patch-1

I would like to take this one up. Plz assign me this

Sure @devshiva619 Go ahead

Can u assign it to me?

I would like to work on this issue if @devshiva619 won't work. :sweat_smile:

@AvaniVerma Is this issue still open? I would like to work on it. I have a fairly simple solution for the responsiveness problem and I can address the other points too.

hey @ayush221b would you like to share your solution?

Yeah sure. Just replace <nav className="navbar navbar-default navbar-fixed-top"> with <nav className="navbar navbar-default navbar-static-top">
This should do the trick.

@adi44 Would you like to work on this issue ?

yes

@adi44 Please work on it and tell us how much time you'll need.


SAA-2122: Turn on toggle in pre-prod

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 84.19%. Comparing base (0fb4881) to head (7600a81).

Additional details and impacted files
@@            Coverage Diff            @@
##               main    #1112   +/-   ##
=========================================
  Coverage     84.19%   84.19%
  Complexity     3719     3719
=========================================
  Files           383      383
  Lines         12625    12625
  Branches       1087     1087
=========================================
  Hits          10629    10629
  Misses         1498     1498
  Partials        498      498

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


Wildcard (*) in excludedUrls is a catch all

Btw, kudos.
Describe the bug
I wanted {x,y,z}.foo.bar to be ignored, so I put *.foo.bar in excludedUrls. The result was Vimari not working anywhere. Btw, foo.bar seems to be enough for this purpose.
To Reproduce
Steps to reproduce the behavior:

Put something like *.facebook.com in excludedUrls.
Go to any page but *.facebook.com (example).
Nothing works.

Expected behavior
Key bindings to work.
Desktop (please complete the following information):

macOS version: 11.1
Safari version: 14.0.2
Vimari version: 2.1.0

Also, It'd be a good idea to make excludedUrls an array instead of CSV.

I have narrowed this down to here (L354): https://github.com/televator-apps/vimari/blob/768e7b93e8a36bb3882cdba043aa71f894f16864/Vimari Extension/js/injected.js#L352-L361; Then here (L374): https://github.com/televator-apps/vimari/blob/768e7b93e8a36bb3882cdba043aa71f894f16864/Vimari Extension/js/injected.js#L363-L380
What happens is: The js code tries to check whether it should activate in the first one. During this check, it tries to compile a regex from the provided strings in excludedUrls. But, something like *.foo.com is an invalid regex, and makes the code throw an exception, never reaching the activation, which is at L359-L360 (right?).
This can either be changed, so that *s are removed, etc.; Or, the documentation can be amended so that users are warned not to use * in their excludedUrls.
Either way (or any other), let me know what you think is the best approach for this, and I'll submit a PR.


not working on react unless you use class instead of className

Sorry, this was an error by me, it does work correctly


jupyter continuously asks me  to install ipykernel

Type: Bug
jupyter continuously asks me  to install ipykernel, and i can't make codes run in jupyter.
VS Code version: Code 1.81.1 (6c3e3dba23e8fadc360aed75ce363ba185c49794, 2023-08-09T22:18:39.991Z)
OS version: Linux x64 5.19.0-46-generic snap
Modes:

System Info

Item
Value

CPUs
AMD Ryzen Threadripper PRO 5955WX 16-Cores (32 x 1800)

GPU Status
2d_canvas: unavailable_softwarecanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: disabled_softwaremultiple_raster_threads: enabled_onopengl: disabled_offrasterization: disabled_softwareraw_draw: disabled_off_okvideo_decode: disabled_softwarevideo_encode: disabled_softwarevulkan: disabled_offwebgl: unavailable_softwarewebgl2: unavailable_softwarewebgpu: disabled_off

Load (avg)
1, 2, 2

Memory (System)
251.54GB (244.15GB free)

Process Argv
--no-sandbox --force-user-env --unity-launch --crash-reporter-id a55e6f6d-d2f7-4882-bb9a-acf96f1e320c

Screen Reader
no

VM
0%

DESKTOP_SESSION
ubuntu

XDG_CURRENT_DESKTOP
GNOME

XDG_SESSION_DESKTOP
ubuntu

XDG_SESSION_TYPE
x11

Extensions (7)

Extension
Author (truncated)
Version

python
ms-
2023.14.0

vscode-pylance
ms-
2023.8.40

jupyter
ms-
2023.7.1002162226

jupyter-keymap
ms-
1.1.2

jupyter-renderers
ms-
1.0.17

vscode-jupyter-cell-tags
ms-
0.1.8

vscode-jupyter-slideshow
ms-
0.1.5

A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
vserr242:30382549
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
vscoreces:30445986
vscod805cf:30301675
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593cf:30376535
pythonvs932:30410667
vsclangdc:30486549
c4g48928:30535728
dsvsc012cf:30540253
pynewext54:30695312
azure-dev_surveyone:30548225
vsccc:30803844
3biah626:30602489
f6dab269:30613381
a9j8j154:30646983
showlangstatbar:30737416
03d35959:30757346
pythonfmttext:30731395
fixshowwlkth:30771522
showindicator:30805244
pythongtdpath:30769146
i26e3531:30792625
gsofa:30804715
pythonnosmt12:30797651
pythonidxptcf:30805731
pythonnoceb:30805159
asynctok:30815620
dsvsc013:30795093
dsvsc014:30804076
diffeditorv2:30812749

/extJupyter

It looks like this is caused by the Jupyter extension. Please file the issue to the Jupyter extension repository. Make sure to check their issue reporting template and provide them relevant information such as the extension version you're using. See also our issue reporting guidelines for more information.
Happy Coding!

[heart]         Zhang, Ke reacted to your message:

From: VSCode Triage Bot @.>
Sent: Thursday, August 24, 2023 3:27:42 AM
To: microsoft/vscode @.>
Cc: Zhang, Ke @.>; Author @.>
Subject: Re: [microsoft/vscode] jupyter continuously asks me to install ipykernel (Issue #191159)
It looks like this is caused by the Jupyter extension. Please file the issue to the Jupyter extension repositoryhttps://urldefense.com/v3/__https://github.com/microsoft/vscode-jupyter__;!!GNU8KkXDZlD12Q!6mlGI0Q-JHx4FbcUBjs23yESQLXwDkNUbJxGoCveYTASyYq6z9HXibBuvYWtTKspIjSPImy3AScElDWgD4jAZXI$. Make sure to check their issue reporting template and provide them relevant information such as the extension version you're using. See also our issue reporting guidelineshttps://urldefense.com/v3/__https://aka.ms/vscodeissuereporting__;!!GNU8KkXDZlD12Q!6mlGI0Q-JHx4FbcUBjs23yESQLXwDkNUbJxGoCveYTASyYq6z9HXibBuvYWtTKspIjSPImy3AScElDWghtQc2wo$ for more information.
Happy Coding!
—
Reply to this email directly, view it on GitHubhttps://urldefense.com/v3/__https://github.com/microsoft/vscode/issues/191159*issuecomment-1690937443__;Iw!!GNU8KkXDZlD12Q!6mlGI0Q-JHx4FbcUBjs23yESQLXwDkNUbJxGoCveYTASyYq6z9HXibBuvYWtTKspIjSPImy3AScElDWgktFxxZk$, or unsubscribehttps://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/BAD6RIRGZ22R3LWPE24AMZTXW3C25ANCNFSM6AAAAAA34LG6S4__;!!GNU8KkXDZlD12Q!6mlGI0Q-JHx4FbcUBjs23yESQLXwDkNUbJxGoCveYTASyYq6z9HXibBuvYWtTKspIjSPImy3AScElDWgZ5c4pME$.
You are receiving this because you authored the thread.Message ID: @.***>


Role Required for Access

[Enter feedback here]
What is the minimum role within Azure AD or Intune (or both) is needed to access this portal? That's pretty vital information that's missing. Also does someone who has access to the Surface Management Portal see ALL Surfaces in the org, or only the ones their MEM scope group has been assigned?

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

ID: 572ed74d-7997-32b3-3ebd-d56a6cd71b88
Version Independent ID: 572ed74d-7997-32b3-3ebd-d56a6cd71b88
Content: Surface Management Portal - Surface
Content Source: surface/surface-management-portal.md
Product: w10
Technology: windows
GitHub Login: @CoveMiner
Microsoft Alias: greglin

Read All permission is all you needed to access SMP


test on Node.js version 8

Several tests fail on Node 8:
test failure due to stderr output
Transformation error for /home/myk/Projects/qbrt/bin/cli.js ; return original code

Transformation error for /home/myk/Projects/qbrt/bin/cli.js ; return original code

test failure due to stderr output
Invalid Version: https://registry.npmjs.org/istanbul-lib-instrument/-/istanbul-lib-instrument-1.7.3.tgz

test failure due to stderr output
Transformation error for /home/myk/Projects/qbrt/bin/cli.js ; return original code

Transformation error for /home/myk/Projects/qbrt/bin/cli.js ; return original code

test failure due to stderr output
Invalid Version: https://registry.npmjs.org/istanbul-lib-instrument/-/istanbul-lib-instrument-1.7.3.tgz

test/package-main-path.js ............................. 0/1
  not ok test/package-main-path.js
    timeout: 600000
    file: test/package-main-path.js
    command: /home/myk/.nvm/versions/node/v8.2.1/bin/node
    args:
      - test/package-main-path.js
    cwd: /home/myk/Projects/qbrt
    exitCode: 1

test failure due to stderr output
Transformation error for /home/myk/Projects/qbrt/bin/cli.js ; return original code

Transformation error for /home/myk/Projects/qbrt/bin/cli.js ; return original code

test failure due to stderr output
Invalid Version: https://registry.npmjs.org/istanbul-lib-instrument/-/istanbul-lib-instrument-1.7.3.tgz

test/package-path.js .................................. 0/1
  not ok test/package-path.js
    timeout: 600000
    file: test/package-path.js
    command: /home/myk/.nvm/versions/node/v8.2.1/bin/node
    args:
      - test/package-path.js
    cwd: /home/myk/Projects/qbrt
    exitCode: 1

Transformation error for /home/myk/Projects/qbrt/bin/cli.js ; return original code
Invalid Version: https://registry.npmjs.org/istanbul-lib-instrument/-/istanbul-lib-instrument-1.7.3.tgz
test/package-url.js ................................... 0/1
  not ok test/package-url.js
    timeout: 600000
    file: test/package-url.js
    command: /home/myk/.nvm/versions/node/v8.2.1/bin/node
    args:
      - test/package-url.js
    cwd: /home/myk/Projects/qbrt
    exitCode: 1

console.log: ["-foo","bar"]
JavaScript error: resource://gre/modules/osfile/osfile_async_front.jsm, line 410: Error: OS.File has been shut down. Rejecting post to remove
JavaScript error: resource://gre/modules/osfile/osfile_async_front.jsm, line 410: Error: OS.File has been shut down. Rejecting post to remove
test/run-command-line-args.js ..Transformation error for /home/myk/Projects/qbrt/bin/cli.js ; return original code
Invalid Version: https://registry.npmjs.org/istanbul-lib-instrument/-/istanbul-lib-instrument-1.7.3.tgz

They pass when I run them with the latest version of node-tap, however, so they'll presumably be fixed by #105. Unfortunately, tap has been broken on Windows for months, and I'm waiting for the fix to update it. Stuck.

Woot, we got unstuck by a tap update, so we now work with Node 8!


TODO : RangeSlider

A Neumorphic Slider with 2 thumbs : min & max

will be done on demand, if someone need this


Got "Namespace object has no attribute" when run spruned first time

Installed spruned on Raspberry Pi 3 Model B. OS is Raspbian Stretch Lite and python version is Python 3.5.3. Got to this part:

$ ~/src/spruned/venv/bin/spruned

Then I got this:
$ ~/src/spruned/venv/bin/spruned
Traceback (most recent call last):
File "/home/admin/src/spruned/venv/bin/spruned", line 11, in
load_entry_point('spruned==0.0.4b4', 'console_scripts', 'spruned')()
File "/home/admin/src/spruned/venv/lib/python3.5/site-packages/pkg_resources/init.py", line 561, in load_entry_point
return get_distribution(dist).load_entry_point(group, name)
File "/home/admin/src/spruned/venv/lib/python3.5/site-packages/pkg_resources/init.py", line 2631, in load_entry_point
return ep.load()
File "/home/admin/src/spruned/venv/lib/python3.5/site-packages/pkg_resources/init.py", line 2291, in load
return self.resolve()
File "/home/admin/src/spruned/venv/lib/python3.5/site-packages/pkg_resources/init.py", line 2297, in resolve
module = import(self.module_name, fromlist=['name'], level=0)
File "/home/admin/src/spruned/venv/lib/python3.5/site-packages/spruned-0.0.4b4-py3.5.egg/spruned/app.py", line 122, in
ctx.load_args(args)
File "/home/admin/src/spruned/venv/lib/python3.5/site-packages/spruned-0.0.4b4-py3.5.egg/spruned/application/context.py", line 151, in load_args
'cache_size': int(args.cache_size),
AttributeError: 'Namespace' object has no attribute 'cache_size'

Had the same issue, see #78, it should fix that problem

Thnks @afilini, fix merged.
Will release on pypy this w.e. along with other fixes.


integrated yard-junk into Cl

issue #399

@zverok please suggest changes to ignore yard script for ruby 2.0

please suggest changes to ignore yard script for ruby 2.0

Let's try to approach the problem from another side? To include yard-junk script only on ruby-2.4 (because it will produce the same errors on any version of Ruby)
And that's also true for Rubocop, BTW

Ah, and you should look at how it fails on Travis. It fails not on script running stage, but on gem installation. It could be easily avoided with if RUBY_VESION >= '2.1' in gemspec

The problem is that config in the travis build wasn't changed as expected for ruby 2.0, if that is solved, the build can be modified as required.

The problem is that config in the travis build wasn't changed as expected for ruby 2.0, if that is solved, the build can be modified as required.

It was. But before using the config, travis does bundle install. Which tries to install yard-junk, and fails (because gem specifies minimal Ruby version)

I have changed the build matrix as required.

@zverok is it okay to allow 2.0 build to fail for now to keep the number of builds intact?

Screw the Ruby 2.0 :)


arch/riscv: rearrange for standard use of extern "C"

Consistently place C++ use of extern "C" after all include directives,
within the negative branch of _ASMLANGUAGE if used.
Remove extern "C" support from files that don't declare objects or
functions.
Background from issue #17997:
Declarations that use C linkage should be placed within extern "C"
so the language linkage is correct when the header is included by
a C++ compiler.
Similarly #include directives should be outside the extern "C" to
ensure the language-specific default linkage is applied to any
declarations provided by the included header.
See: https://en.cppreference.com/w/cpp/language/language_linkage
Signed-off-by: Peter Bigot<EMAIL_ADDRESS>

Expect shippable to fail until #18198 is resolved.  That is not a regression due to the changes in this PR.


Cabal build issues when trying to run plutus locally

I hope this is the right place to post this.
I have been trying to run the Plutus Playground locally for a while with no success, and I was hoping to get help here. I will be more than happy to provide more details.
Thanks,

Hi, thanks for the interest. However, we're not really looking to help external people run our software at the moment. Maybe once this is released properly!


Global not always detecting

Hi, I have an issue where Global is not being triggered when one of the inside rooms is.
I don't have any exclusions in that room or on Global.
The element that is triggering the room does have a customisation setting it to 'door' class so that I can use the "Door" option on selected sensor types for the room.
I do have a similar config for another sensor on another room and that works AFAIK.
Any suggestion?
I have tried deleting both the room and global and allowing fresh config...no change.
Feature: As an aside...is there a way to see what sensor(s) triggered the detection?  Would be nice to see that in attributes for the room.

Hey @Bodge-IT , can you check if this was solved in the beta?

Hi @jseidl I have not seen a recurrence of this in my recent testing.


Zcash-compatible Bitcoin script impl

some helpful pointers from @prestwich:

Bitcoin script test vectors: https://github.com/bcoin-org/bcoin/blob/master/test/data/core-data/script-tests.json
Parser for those tests: https://github.com/bcoin-org/bcoin/blob/master/test/script-test.js#L28-L68
Rust implementation of Bitcoin script (CC0) https://github.com/rust-bitcoin/rust-bitcoin/blob/master/src/blockdata/script.rs

relevant discord discussion: https://discordapp.com/channels/676527656170160146/716086297210650634/729816649242378261

@yaahc mind reposting some context for those of us following who aren't on discord? :)

Not sure how well this will paste but here goes nothing

Yaah (she/her)Yesterday at 2:50 PM
this is the relevant issue right? https://github.com/ZcashFoundation/zebra/issues/180
GitHub
Zcash-compatible Bitcoin script impl · Issue #180 · ZcashFoundation...
durumcrustulumYesterday at 2:51 PM
correct yes
The current Script type is just a wrapper around a Vec with some Zcash(De)Serialize trait impls
https://github.com/ZcashFoundation/zebra/blob/8281b9040cd56b6ef40ddbbc36638c15e8fc2059/zebra-chain/src/types.rs#L99
GitHub
ZcashFoundation/zebra
An ongoing Rust implementation of a Zcash node. 🦓. Contribute to ZcashFoundation/zebra development by creating an account on GitHub.
str4dYesterday at 2:53 PM
Hoo boy, not envying you implementing this
durumcrustulumYesterday at 2:53 PM
we aren't, we're pulling in a dep
definitely uh, not trying to do that from scratch :sweat_smile:
str4dYesterday at 2:53 PM
Sentiment still applies
durumcrustulumYesterday at 2:53 PM
eeep
str4dYesterday at 2:55 PM
We don't have SegWit (or several other NOP changes) from upstream, and we stripped out FindAndDelete etc. before launch, so you likely can't just depend on a Bitcoin Rust dependency.
durumcrustulumYesterday at 2:55 PM
I think this is the one
https://github.com/rust-bitcoin/rust-bitcoin/
GitHub
rust-bitcoin/rust-bitcoin
Rust Bitcoin library. Contribute to rust-bitcoin/rust-bitcoin development by creating an account on GitHub.
hrmpph yeah
str4dYesterday at 2:56 PM
Using that as a starting point, and keeping close enough to pull in updates from them, makes sense. But I doubt that the delta can be easily applied as a purely functional wrapper
(I'd be happy to be wrong!)
Some things (like NOP changes) could be wrapped to hide the internal behaviour with an actual nop, but IDK enough about how that implementation is designed. The C++ impl certainly isn't amenable to that (it internally iterates over the script, and there's no modular "handle one opcode" point that is treated as an opaque handler within the script iteration, just a giant switch statement)
Yaah (she/her)Yesterday at 3:06 PM
This library must not be used for consensus code

wheeeeww

I think eeep is the only correct response ya
this is a really thorny issue as Zcash relies on an ancient fork of Script, and Script is full of terrible edge cases (like negative 0). If we use a Rust re-implementation we're more likely to cause consensus failures :thinking:

If we use a Rust re-implementation we're more likely to cause consensus failures 🤔

not if zcashd adopts the same rust impl :D

if moving to a new Script implementation entirely, it would be a good idea to patch up sighash a bit. ZIP-243 hasn't been updated for the recent BIP-143 value issues.
Here's a list of changes in BIP-341. Numbers 2 and 3 are useful for Zcash:
In summary, the semantics of the BIP143 sighash types remain unchanged, except the following:

1. The way and order of serialization is changed.
2. The signature message commits to the scriptPubKey of the spent output and if the SIGHASH_ANYONECANPAY flag is not set, the message commits to the scriptPubKeys of all outputs spent by the transaction.
3. If the SIGHASH_ANYONECANPAY flag is not set, the message commits to the amounts of all transaction inputs.
4. The signature message commits to all input nSequence if SIGHASH_NONE or SIGHASH_SINGLE are set (unless SIGHASH_ANYONECANPAY is set as well).
5. The signature message includes commitments to the taproot-specific data spend_type and annex (if present).

If we use a Rust re-implementation we're more likely to cause consensus failures 🤔

not if zcashd adopts the same rust impl :D

That would have to wait until at least the Canopy network upgrade, which is in November. We would need some kind of script implementation before then, to validate Sapling to Heartwood.

That would have to wait until at least the Canopy network upgrade, which is in November. We would need some kind of script implementation before then, to validate Sapling to Heartwood.

Good point. I think we will need to come up with two plans, one for short term and one for long term.
Short Term

fork rust-bitcoin and use it for validation

This is going to cause the same consensus issues that reimplementing it from scratch would
we're not even sure that rust-bitcoin includes a full implementation of the runtime for scripts

reimplement in rust only the subset of bitcoin script that is currently used in existing transactions, document the fragility
wrap libzcashconsensus via ffi, either with a bindgen or cxx

Long Term

do a full reimplementation of the script impl from libzcashconsensus in rust and switch both zcashd and zebrad to this impl as part of the Canopy upgrade
stick with the wrapped c++ dependency for libzcashconcensus
stick with the rust-bitcoin impl assuming

The best option seems to be 3 for short term and then 1 for long term, that gives us a fully valid and reliable script implementation at all times. If we run into issues with ffi and c++ or if we really don't want to have any c++ dependencies then I feel like the second best option would be 2 which then grows into 1. And for 2 we could even use bits and pieces of rust-bitcoin as a starting point, though it hardly matters at that point. I'm going to start with looking into FFI for now pending further feedback from other @ZcashFoundation/zebra-team members.

I think eeep is the only correct response ya

Voice of a generation, I ams

do a full reimplementation of the script impl from libzcashconsensus in rust and switch both zcashd and zebrad to this impl as part of the Canopy upgrade

How do we validate pre-Canopy blocks?
Zebra can set a mandatory checkpoint, but zcashd can't.

In general, it might help to look through the list of BIPs and ZIPs in #253 to find any script changes or restrictions.

How do we validate pre-Canopy blocks?
Zebra can set a mandatory checkpoint, but zcashd can't.

disclaimer: I'm not exactly an expert on the network upgrades or consensus, so this could easily be based on faulty assumptions.
I assume the zebra-script impl would be well tested against all pre canopy blocks. If we're worried about some of the last pre Canopy blocks failing to validate causing problems with the network update we could do a transition period where as part of the Canopy upgrade we include both script validators and continue to use the c++ script validator for all old blocks and use the rust validator for all new blocks, then we could go back and make sure all existing pre-canopy blocks successfully validate with zebra-script and once they do we could rip out the c++ script validator at our leasure.

Using dual libraries works, as long as the new validator accepts all the old blocks.
Here's how we would do that hard fork at Canopy activation:

use the old validator up to the Canopy height
use the new validator at and after the Canopy upgrade height

That way, we support chain reorganisations across the activation height.
If the old validator rejects some old blocks, then new zcashd nodes will reject those old blocks during the initial sync. There are workarounds, but they involve hard-coded exceptions for some blocks or block ranges.

@str4d went and setup a version of libzcashconsensus that is refactored to be more self contained which we should use for any zcash ffi based impls for this
https://github.com/str4d/zcash/tree/proofverifier-refactor
pull that branch from str4d's repo and then build just libzcashconsensus with this command:
CONFIGURE_FLAGS="--with-libs" ./zcutil/build.sh -j$(nproc)

You can disable more parts and build just libzcashconsensus.a:
CONFIGURE_FLAGS="--with-libs --without-daemon --without-utils --disable-tests --disable-bench" ./zcutil/build.sh -j$(nproc)

The static library ends up in src/.libs/libzcashconsensus.a. The relevant API is zcashconsensus_verify_script, which is declared in src/script/zcashconsensus.h (and would be redeclared in an extern "C" {} Rust block).

extremely relevant reference impl for when someone wrapped the upstream version of bitcoinconsensus as a rust library
https://github.com/rust-bitcoin/rust-bitcoinconsensus/blob/master/build.rs


Updating homepage language, fixing scroll bar on site nav

Spun up a tugboat env for this PR: https://pr46-9rvnwvgtaacxeiwwry81yfvffpvjqdzg.tugboat.qa/
That should be automatic from any new PR's going forward.


Added Cors and support for heroku

Okay, so in summary i want you to do this before getting this merged:

Restore the package-lock.json file.
Remove the src/index.js file.
Leave the host and port part just as it.


Linker error on macOS

Possible regression in compilers 1.0.4.
Compiling a simple C program fails at link time. Used to work in 1.0.3.
Here's the C code "test.c":
#include <stdio.h>

int main(void){
    printf("hello world");
}

clang test.c gives the following error:
ld: library not found for -lSystem
clang-9: error: linker command failed with exit code 1 (use -v to see invocation)

I checked I'm using clang from the compilers package:
$ which clang
path/to/conda_env/bin/clang

Possibly due to the bump of clang version (8 -> 9) ?

I've marked the latest builds as broken. Can you send a PR adding a test?

Btw, can you run dtrace on the command and post the output?

Fixed in https://github.com/conda-forge/cctools-and-ld64-feedstock/pull/12 . Can someone send a PR to my PR with a test using a newer SDK? You'll have to download a new SDK in the test and set CONDA_BUILD_SYSROOT to that.

Ping on this.


can't accept sending with cookie, like fetch/es6

I want insert credentials option from fetch/es6.
credentials: 'include'
fetch
fetch('/post?type=fetch', {
    credentials: 'include',
}

Can EasyAgent do it like this?
EasyAgent
  .post(...)
  .setHeaders({
    credentials: 'include'
  })

or
EasyAgent({credentials: 'include'})
  .post(URL)
  .setJson(...)

Reference: https://developers.google.com/web/updates/2015/03/introduction-to-fetch

@snghrym
Thank you for posting your issue :)
I updated EasyAgent to v0.0.4.
It can receive some new options. I think your issue is solved now. Look this:
EasyAgent.post('/some/api/', {
  crendetials: 'include',
})
   .setJson(/* ... */)
  .fetch()
...

Have fun to use! :)

thank you for your high speed response.


[SPARK-9241][SQL] Supporting multiple DISTINCT columns (2) - Rewriting Rule

The second PR for SPARK-9241, this adds support for multiple distinct columns to the new aggregation code path.
This PR solves the multiple DISTINCT column problem by rewriting these Aggregates into an Expand-Aggregate-Aggregate combination. See the JIRA ticket for some information on this. The advantages over the - competing - first PR are:

This can use the faster TungstenAggregate code path.
It is impossible to OOM due to an OpenHashSet allocating to much memory. However, this will multiply the number of input rows by the number of distinct clauses (plus one), and puts a lot more memory pressure on the aggregation code path itself.

The location of this Rule is a bit funny, and should probably change when the old aggregation path is changed.
cc @yhuai - Could you also tell me where to add tests for this?

Can one of the admins verify this patch?

ok to test

Merged build triggered.

Merged build started.

Test build #44915 has started for PR 9406 at commit 6139f47.

Test build #44915 has finished for PR 9406 at commit 6139f47.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):\n  * case class Expand(\n

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

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Test build #45019 has started for PR 9406 at commit 1e705fe.

Test build #45019 has finished for PR 9406 at commit 1e705fe.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):\n  * case class Expand(\n

Merged build finished. Test FAILed.

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

Merged build triggered.

Merged build started.

Test build #45207 has started for PR 9406 at commit 9be5b9d.

Test build #45207 has finished for PR 9406 at commit 9be5b9d.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):\n  * final class ShuffleSortDataFormat extends SortDataFormat<PackedRecordPointer, LongArray> \n  * final class UnsafeSortDataFormat extends SortDataFormat<RecordPointerAndKeyPrefix, LongArray> \n  * case class Expand(\n

Merged build finished. Test FAILed.

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

Hmmmm... this is a bit of a strange error.

Jenkins retest this please

Jenkins is not retesting... @marmbrus could you add me to the whitelist?

Merged build triggered.

Merged build started.

Test build #45219 has started for PR 9406 at commit d3bdb2b.

Test build #45219 has finished for PR 9406 at commit d3bdb2b.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):\n  * case class Expand(\n

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

Merged build finished. Test PASSed.

@hvanhovell I have started to use this PR as the foundation of removing our old aggregation code path.

Okay, I looked over this pretty quickly and it looks awesome.  We need some tests and we are super close to me cutting a preview release.  That said, I'd really like to include this in 1.6.  Here is my proposal:

Lets merge this as is.
Yin will start ripping out the old aggregation path. (with or without #9409).
Comments and TODOs can be addressed in a follow up.


SyntaxError

The web site is blank
SyntaxError: missing } after function body prose.min.js:16
Under:
Name: Firefox
Version: 31.0a1
User Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101 Firefox/31.0

Hello and thank you for this issue report. There have been several point releases in Prose since this issue was opened and there has not been much discussion here. I wanted to ask if you could please assist in confirming this is still an issue in the latest version of the product. If it is fixed, please close this issue :-)
Also, if possible could you please

Find out if this only affects certain browsers
Create a test case -- a list of steps we can perform to reproduce the problem
Enable web developer extensions and report the Javascript error message. And when in doubt, be over-descriptive of the bug and how you discovered it.

Since this project is looking for new maintainers (#743), it will be helpful if users can double check the old issues and delete ones that are fixed. This will be super helpful for the new team that works on moving this project forward.
I'm sorry this message is impersonal. And thanks for your help!

Dont worry @fulldecent .
I have a big pull request, maybe tonight I'll send the changes.
To use Prose as Chrome App, Mozilla WebMaker, Mozilla Add-ons, and Desktop App.


Question about generate speech

heya my lad,
I have run you Usage code for generate speech, but nothing output.
Could you please give a full example to accept a prompt and text, then generating the speech?
Or give some simple steps to attain this goal.

"if there is a wip flag next to the title of the repo, it isn't done yet", The model has not yet been trained, so no inference can be made at this stage.

i am just a programmer. i will like to contribute but don't have much knowlage, can you please tell us when can be expect this to start generating some speech. you project is awsome just thanks for open sourcing

I was able to train (unconditioned) on some of my data and it was able to produce speech ... but it only one word of speech no matter what. I'll be looking into conditional training soon.

Hi, have you tried something?Can you teach me something:
how to use the Usage?Does it need to create a new .py file? Or add a few lines from Usage to my existing encoder?


Mark java.util.Optional as well-known immutable container

The class WellKnownMutability contains an entry only for Guava's Optional in KNOWN_IMMUTABLE, but not for the JDK's Optional. This means that the ImmutableChecker will not allow marking classes as @Immutable with fields of type java.util.Optional.

In fact, there are also a few other classes I would suggest to add, e.g., BigInteger, and I expect maybe more might come up in the future. What is your desired way of proposing such additions? File a separate issue for each group of them, or collect them all in one ticket? Or do you prefer a pull request adding lines to WellKnownMutability?
Are proposals to add further Guava classes welcome (e.g., UnsignedInteger), or do you plan on adding Error-Prone's @Immutable to them directly?

Some applicable types configured in MutabilityDetector:

JDK
Guava

Any answer for my question in my previous comment on how to report such requests?
Currently I would like to see BigInteger, File, Path, URL, and URI` added.

I'd be happy to take a pull request for those.
We may start adding @Immutable to more guava classes, but using WellKnownMutability as a stop-gap is OK too.


Does 'debug' cache the DEBUG environment variable somewhere? Getting no output after changing namespace and DEBUG env var.

I am using 'debug' with TypeScript in an Electron project like so:
import debug from 'debug';
const log = debug('foo');

export default async function myFunction(name: string) {
  log('calling myFunction');
  ...
  log('successfully returning myFunction');
  return someVariable;
}

in my shell (zsh) I set the DEBUG env var like so export DEBUG=foo and then started running my application. Everything worked fine. Eventually, I changed the namespace from foo to bar and now no matter what I do, I cannot get any output. I tried resetting DEBUG, I restarted my shell and set the environment variable again with export DEBUG=bar, I tried using the [cross-env]{https://www.npmjs.com/package/cross-env} to set it like so:
"scripts": {
    "start": "tsc && cross-env DEBUG=bar NODE_ENV=development electron-forge start",
    ...
}

but nothing ever shows up.
I tried
import debug from 'debug';
const log = debug('bar');

console.log("DEBUG", process.env.DEBUG);

export default async function myFunction(name: string) {
  log('calling myFunction');
  ...
  log('successfully returning myFunction');
  return someVariable;
}

and the console.log output is indeed: DEBUG bar.
The only way I can get it to work now is by doing:
import debug from 'debug';
const log = debug('bar');
log.enabled = true;

The moment I change const log = debug('bar'); back to const log = debug('foo'); , I get output messages for the foo namespace no matter what's in the DEBUG env var.
Any idea what might be happening here?

Having a similar issue here, but just to help you, maybe try running set on its own to print a debug output of all environment variables set for your shell

No idea, this seems like an environment issue to be honest. DEBUG is checked once at the first import of debug and cached.

I've been bitten by this the other day too. Turns out, DEBUG is cached in LocalStorage, and in subsequent runs, LocalStorage will override the environment. You can do localStorage.debug = null in a dev console to reset it.

@algernon that's a detail of the browser version. I believe OP is using the node side of things.

Are/were you using regex in your code somewhere? possibly passing it into debug?
I think this issue was introduced with toNamespace() in 4.1.0
When I had DEBUG = *, I saw express was able to debug fine. I noticed that they're using debug 2.6.9, so I went through the versions and found that debug works as expected until 4.1.0. Seeing that toNamespace converts regex into a namespace and realizing I was potentially passing regex into debug, I remembered Javascript's regex is weird. commenting out my regex returned the output in 4.3.4.
However, at that point, the universe decided I was done, as uncommenting it did not reintroduce the issue and no matter what I do now I can't reproduce it again, I've rolled everything back to exactly as it was when I had the problem and it's just gone 🤷


fixed boost linking

Description of the Change
Added target links for libraries that could not find the boost include files. Tested with CMake version 3.11.1 and boost version 1.67.0_1

Benefits
All the packages find boost files.

Possible Drawbacks
None

Usage Example or Tests
mkdir build; cd build; cmake ..; make -j$(nproc)
cmake --build build --target test

@sjashwin thank you for you work!
However, we have some requirements:

Please make a little bit more detailed PR description (like here: https://github.com/hyperledger/iroha/pull/1297)
Please, sign-off your commit with DCO (https://github.com/apps/dco). It's Hyperledger's requirement. You can git reset --soft HEAD~ to ammend previous commit and after it recommit again with -s option. After it, you need to force push a commit, so we can see it here.

@laSinteZ I've made the required changes.

Oh @sjashwin I see that you've accidentally pushed code related to Segmentation fault on negative precision into this PR. Could you please remove unrelated to this PR commits, since we can't merge it otherwise? 😔


Ideas to improve the training accuracy

I am trying to fine-tune the model with UCF-101 dataset.
with the SGD optimizer and lr decay, I can get almost 91.79% accuracy after 6000 steps with BS: 32.
global_step = tf.Variable(0, trainable=False)
learning_rate = tf.compat.v1.train.exponential_decay(3, global_step, 100, 0.96)
optimizer = tf.compat.v1.train.GradientDescentOptimizer(learning_rate).minimize(loss, global_step=global_step)

From the paper, I see the accuracy could be 94.x%, any ideas to improve my accuracy?

How many frames are being used in training and testing ?
Joao
On Wed, Feb 12, 2020 at 2:45 PM Leslie-Fang<EMAIL_ADDRESS>wrote:

I am trying to fine-tune the model with UCF-101 dataset.
with the SGD optimizer and lr decay, I can get almost 91.79% accuracy
after 6000 steps with BS: 32.
global_step = tf.Variable(0, trainable=False)
learning_rate = tf.compat.v1.train.exponential_decay(3, global_step, 100, 0.96)
optimizer = tf.compat.v1.train.GradientDescentOptimizer(learning_rate).minimize(loss, global_step=global_step)
From the paper, I see the accuracy could be 94.x%, any ideas to improve my
accuracy?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/deepmind/kinetics-i3d/issues/93?email_source=notifications&email_token=ADXKU2X7VJIO5B3X5FBGE6TRCQDSNA5CNFSM4KT3DOC2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4IM6WIKA,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADXKU2QV7URPHTL7SC4A4ADRCQDSNANCNFSM4KT3DOCQ
.

@joaoluiscarreira  Thanks for looking into my issue.
Training: almost 9500 frame in one epoch.
Testing: almost 3700 frame.
BTW: I am using depth 64.

Let me clarify: what we did was to use 64 frames in training and 250 frames
in testing. If you're testing on only 64 frames for each video that would
have a negative impact.
Joao
On Wed, Feb 12, 2020 at 2:50 PM Leslie-Fang<EMAIL_ADDRESS>wrote:

@joaoluiscarreira https://github.com/joaoluiscarreira Thanks for
looking into my issue.
Training: almost 9500 frame in one epoch.
Testing: almost 3700 frame.
BTW: I am using depth 64.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/deepmind/kinetics-i3d/issues/93?email_source=notifications&email_token=ADXKU2QYY3IPL3ZFJ2WPWK3RCQECZA5CNFSM4KT3DOC2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOELRBHMQ#issuecomment-585241522,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADXKU2VMJL7D5ZHYW3WMNP3RCQECZANCNFSM4KT3DOCQ
.

我正在尝试使用 UCF-101 数据集微调模型。 使用 SGD 优化器和 lr 衰减，在 BS: 32 的 6000 步后，我可以获得几乎 91.79% 的准确率。
global_step = tf.Variable(0, trainable=False)
learning_rate = tf.compat.v1.train.exponential_decay(3, global_step, 100, 0.96)
optimizer = tf.compat.v1.train.GradientDescentOptimizer(learning_rate).minimize(loss, global_step=global_step)

从论文中，我看到准确率可能是 94.x%，有什么想法可以提高我的准确率吗？

Can I share the code？


unimplemented getTermDocument @ bundle.js:5 error on Hyper 2.0.2

Opening a new tab in the newest version of Hyper causes an error. The tab is open and the name is visualized correctly but the keymaps do not work.

I have a working v2 branch. And I made a (merged) PR to have possibility to specify : hyper-pane@next in Hyper config.

Thank you for your feedback 🙏

It works! Thanks a lot!

From v2.1.1 of Hyper, it is possible to specify @next in hyper config file.
I just published a v2.0.0-rc2 on this @next update channel.
Please update your plugins.
Thank you again for your feedback


Jenkins configuration project limit

Jenkins Plugin - Configuration of project limit pull request!
:heavy_check_mark: Checklist

[x] Edits readme files
[x] Add configuration of project count limit
[x] If not configured the default limit is 50

Hi @awanlin, short reminder for this PR :) Or is one of my doings still missing? Thank you!

Hi @PiCookie, it's in the queue but as I have other PRs to review it will take some time.

While you wait for the review can you take a look at the CI failures, please @PiCookie?

Hi @awanlin, fixed the CI failures in https://github.com/backstage/community-plugins/pull/796/commits/357b73d3f76f413ad10bc8084c9d5eaeedb6948a

@PiCookie I'm pretty sure this PR is causing some issues on the plugin:
Cannot read properties of undefined (reading 'filter')
The issue seems from these rows:

As you can see, we are "swapping" a jobTreeSpec (singular) with a limitedJobsTreeSpec (plural).
The result is that the plugin is applying a JSON filter "jobs=[action[*]...." which doesn't work, as the "jobs" field is not present for standalone project

Hi @Skiepp,
you are right, thank you for the explanation and fix!


Revert 254797428e705f0cab8dd8718243cf331823ee48

This commit reverts the changes made in the PR
https://github.com/CartoDB/cartodb/pull/5945
We've discovered that a combination of ogr2ogr2 options + cartodbfy
produces MULTIPOINT geometries at the end of the process, which affects
torque rendering, for CSV's containing single point geometries.
@rochoa

merging and deploying, as it is a hotfix

Thanks for taking care of this @rafatower !! :heart:


Vertical scrolling with touch pad in dialogue editor is jittery (may be related to Godot's text editor, may be Mac specific)

Describe the bug
When scrolling vertically in the dialogue editor with a touch pad, the editor doesn't scroll unless a certain scrolling speed is used. When the scrolling gesture is stopped, the editor stop scrolling abruptly as opposed to slowly coming to a halt. This makes navigating dialogue files a bit hard. Horizontal scrolling works just fine.
Affected version

Dialogue Manager version: 2.19.0
Godot version: 4.1.1 (stable, official)

To Reproduce
Steps to reproduce the behavior: as described above.
Expected behavior
As described above. This was happening in Godot's code editor too but seems to have been resolved since. There's an editor option (Text Editor > Behavior > Smooth Scrolling) that fixes the issue when turned on. There has been some discussion on Godot's repo regarding smooth scrolling, I can't point to a single issue as the discussion has been quite sparse, but turning that option on seems to do wonders.

I've added some code to grab the main code editor smooth scrolling setting and apply it to the dialogue editor. I hope that helps 👍

Just pasted that line in to test it out and it's smooth (…) sailings :) Thanks!


Can't generate bindings for all files in a folder

Hi,
I'm opening an issue here because the forums at http://forum.lubyk.org/ seem to be inaccessible.
I'm trying to make dub generate bindings for classes and functions found in all files starting in a folder. In my tests I have:

include

subdir

Test4.h: Contains the mc2::Test4 class

Test.h: Contains the mc::Test2 and the mc::Test3 classes, and the mc::doStuffWithTest function

My dub script is:
local lub = require 'lub'
local dub = require 'dub'

local inspector = dub.Inspector {
  INPUT    = {
    lub.path '|include/',
  },
  RECURSIVE = 'YES',
  GENERATE_HTML = 'YES',
  doc_dir = lub.path '|doc',
  keep_xml = true,
}

local binder = dub.LuaBinder()

binder:bind(inspector, {
  lib_name = '_',

  single_lib = 'miniclip',

  output_directory = lub.path '|src',

  header_base = lub.path '|include',

  luaopen    = 'cppbindings',
})

When I run the dub script only things in Test.h end up having Lua bindings. Examining doxygen's output, I can see that it's not catching the mc::Test4 class, which I believe is the reason why dub is not generating its binding.
dub's version is 2.2.4, and doxygen's is 1.8.11.
Am I doing something wrong?
Thanks in advance,
Andre

Never mind, there was something wrong in my Test4.h file. Now my issue is that it works with the .h extension but not with .hpp.


Align text on mobile and tablet

When using phones and tablets, the top section appears disorganized. I suggest either aligning it to the center or increasing the margins.

@olimpiuus I'm unsure what you mean by disorganized here. Can you provide a bit more context or instruction?

I am going to close this if I don't hear back in a week or so because I also am unsure what should be done...

can you please assign me this, I think I can work on this issue

@MandyMeindersma: Do you think this issue can be closed since we have not heard back from the owner?


My History appears in white and I do not know why.

My History appears blank as if I had no any funds in my  wallet. But I have transferred money from mi wallet of hitbtc. In the blockchain apears the transaction as you can see.
https://blockchain.info/address/1K5XHCn2apMDj9qRLbcUAYKyduMPmQ8Ck6

I apologize for my english.

The link shows a bitcoin transaction, not a bitcoin cash transaction


Opera don't work all foundation 5 js?

Opera/9.80 (X11; Linux x86_64) Presto/2.12.388 Version/12.16
example http://foundation.zurb.com/docs/components/orbit.html
(I removed an item from the top bar)

In the inspector(f12), such an error js - Uncaught exception: Error: Syntax error, unrecognized expression: [data-"DejaVu Serif"-abide]

Thanks @xa0c - that solved a problem I was having with a site not running under Opera using Foundation 5


Have a way to send events to custom module

Currently, you can handle mouse events by running a command, but it doesn't look like there is a way to send the mouse event to a continuously running module program, so that the module program can update the message in response to a mouse event. For example, I was thinking about how I might create a custom module  similar to the clock module but with #522.  It is possible to do this by using some other kind of IPC which is triggered by a command on mouse events to inform the module program, but it would be simpler to implement the module if the event was sent to the program over stdin.

I'll not implement something like that on the waybar side, you can write such scripts to handle your need.
For the clock module you can trigger a timezone change on click and the script will echo the new time based on the new timezone. :)

you can write such scripts to handle your nee
Yes, it is possible, but it's certainly not simple.

For the clock module you can trigger a timezone change on click
I don't want to change the system timezone on click, I just want to change the display in waybar.


Crshanks fix synthetics scripts

Allows Scripted Browser, Scripted API, Simple Browser and Ping monitors to be migrated.

Merging the fixes for monitor migrations. Thank you @crshanks


Fixes CAMEL-14893: fix 2.25.x branch

I reported to jira about error handling in grpc component and it was fixed.
https://issues.apache.org/jira/browse/CAMEL-14893
I am also using camel 2.25.x version in my project.
So I modified the source code in the 2.25.x branch for this issue.

Should this be on the camel-2.x branch also?

No only 2.25.x is active


Apply injectmocks usage/reduce system under test instantiation

Some of the classes are not applicable to reduce because they are abstract classes

Hey @NyorJa ! I've left you an invite to the see if we can get Sonar to execute that build process correctly.

Hi Benj,
I still encounter issues. I am not sure if this is a permissions issue
though I do have view access
On Tue, Oct 11, 2022 at 5:56 AM Benjamin La Madrid @.***>
wrote:

Hey @NyorJa https://github.com/NyorJa ! I've left you an invite to the
see if we can get Sonar to execute that build process correctly.
—
Reply to this email directly, view it on GitHub
https://github.com/trebol-ecommerce/spring-boot-backend/pull/130#issuecomment-1273852623,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AB6FLERKIF2QQDV4ASXJTOTWCSGIDANCNFSM6AAAAAARAWOALI
.
You are receiving this because you were mentioned.Message ID:
@.***>


futures==3.2.0

CRITICAL:pip.index:Could not find a version that satisfies the requirement futures==3.2.0 (from versions: 0.2.python3, 0.1, 0.2, 1.0, 2.0, 2.1, 2.1.1, 2.1.2, 2.1.3, 2.1.4, 2.1.5, 2.1.6, 2.2.0, 3.0.0, 3.0.1, 3.0.2, 3.0.3, 3.0.4, 3.0.5, 3.1.0, 3.1.1)

Quick guess:
From https://pypi.python.org/pypi/futures:

Requires Python: >=2.6, <3

You might somehow have a corrupted dependency cache that believes (due to previous resolver bug) that futures==3.2.0 is still a dependency under Py3. I'd clear that just in case before digging deeper.

can no longer reproduce

i lied

[[source]]

url = "https://pypi.python.org/simple"
verify_ssl = true
name = "pypi"

[packages]

futures = "*"

[dev-packages]

[requires]

python_version = "3.6"

leads to
{
    "_meta": {
        "hash": {
            "sha256": "defaf2233df08ddd288f75787d4a8904217ecf22fba389a152b64f50144c6ce6"
        },
        "pipfile-spec": 6,
        "requires": {
            "python_version": "3.6"
        },
        "sources": [
            {
                "name": "pypi",
                "url": "https://pypi.python.org/simple",
                "verify_ssl": true
            }
        ]
    },
    "default": {
        "futures": {
            "hashes": [
                "sha256:51ecb45f0add83c806c68e4b06106f90db260585b25ef2abfcda0bd95c0132fd",
                "sha256:c4884a65654a7c45435063e14ae85280eb1f111d94e542396717ba9828c4337f"
            ],
            "version": "==3.1.1"
        }
    },
    "develop": {}
}

This file:
[[source]]

url = "https://pypi.python.org/simple"
verify_ssl = true
name = "pypi"

[packages]

futures = {version = "==3.2", python_version = "<'3.0.0'"}

Leads to:
Locking [dev-packages] dependencies…
Locking [packages] dependencies…

CRITICAL:pip.index:Could not find a version that satisfies the requirement futures==3.2 (from versions: 0.2.python3, 0.1, 0.2, 1.0, 2.0, 2.1, 2.1.1, 2.1.2, 2.1.3, 2.1.4, 2.1.5, 2.1.6, 2.2.0, 3.0.0, 3.0.1, 3.0.2, 3.0.3, 3.0.4, 3.0.5, 3.1.0, 3.1.1)
Warning: Your dependencies could not be resolved. You likely have a mismatch in your sub-dependencies.
  You can use $ pipenv install --skip-lock to bypass this mechanism, then run $ pipenv graph to inspect the situation.
No matching distribution found for futures==3.2

Current workaround: lock with Python 2 environment.

fixed.

I am experiencing this issue again:
➜  foobar ls -al
total 0
drwxr-xr-x   2 Browning  wheel   64 Apr  1 18:55 .
drwxrwxrwt  14 root      wheel  448 Apr  1 18:55 ..
➜  foobar pipenv --version
pipenv, version 11.9.0
➜  foobar pipenv install background
Creating a virtualenv for this project…
Using /usr/local/Cellar/pipenv/11.9.0_1/libexec/bin/python3.6 (3.6.5) to create virtualenv…
⠋Already using interpreter /usr/local/Cellar/pipenv/11.9.0_1/libexec/bin/python3.6
Using real prefix '/usr/local/Cellar/python/3.6.5/Frameworks/Python.framework/Versions/3.6'
New python executable in /Users/Browning/.local/share/virtualenvs/foobar-XaAZ4vih/bin/python3.6
Also creating executable in /Users/Browning/.local/share/virtualenvs/foobar-XaAZ4vih/bin/python
Installing setuptools, pip, wheel...done.

Virtualenv location: /Users/Browning/.local/share/virtualenvs/foobar-XaAZ4vih
Creating a Pipfile for this project…
Installing background…
Collecting background
  Using cached background-0.1.1-py2.py3-none-any.whl
Collecting futures (from background)
Installing collected packages: futures, background
Successfully installed background-0.1.1 futures-3.1.1

Adding background to Pipfile's [packages]…
Pipfile.lock not found, creating…
Locking [dev-packages] dependencies…
Locking [packages] dependencies…
Updated Pipfile.lock (bab157)!
Installing dependencies from Pipfile.lock (bab157)…
An error occurred while installing futures==3.2.0! Will try again.
  🐍   ▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉ 2/2 — 00:00:00
Installing initially–failed dependencies…
Collecting futures==3.2.0 ▉▉▉▉▉▉▉▉▉▉▉ 0/1 — 00:00:00

  Could not find a version that satisfies the requirement futures==3.2.0 (from -r /var/folders/h1/2b6gts3x37zcnj5khyv8y5180000gn/T/pipenv-td3t4m4r-requirements/pipenv-iafh_u6d-requirement.txt (line 1)) (from versions: 0.2.python3, 0.1, 0.2, 1.0, 2.0, 2.1, 2.1.1, 2.1.2, 2.1.3, 2.1.4, 2.1.5, 2.1.6, 2.2.0, 3.0.0, 3.0.1, 3.0.2, 3.0.3, 3.0.4, 3.0.5, 3.1.0, 3.1.1)
No matching distribution found for futures==3.2.0 (from -r /var/folders/h1/2b6gts3x37zcnj5khyv8y5180000gn/T/pipenv-td3t4m4r-requirements/pipenv-iafh_u6d-requirement.txt (line 1))

Adding futures = "==3.1.1" to generated Pipfile seems to work around this issue.

@jacebrowning good question. Does pipenv lock —clear lock the same version?

I think i added some resolver fixes last week that aren’t released yet

@techalchemy Yes, $ pipenv lock --clear still locks 3.2.0.

@jacebrowning are you using the version from master or the release

@techalchemy I've been installing from Homebrew lately (which unfortunately makes it harder to test preview releases).

I don't seem to have a pipenv-resolver command on my machine. How do I get it?

Oh boy. It comes with pipenv these days. Is there not one in /usr/local/Cellar/pipenv/11.9.0? Or does wherever which pipenv points have a shim for the resolver tool? Idk how homebrew works

I found it with $ find /usr/local -name pipenv-resolver.
$ /usr/local/Cellar/pipenv/11.9.0/libexec/bin/pipenv-resolver --debug --verbose background

Using pip: -i https://pypi.python.org/simple

                          ROUND 1
Current constraints:
  background

Finding the best candidates:
DEBUG:notpip.index:1 location(s) to search for versions of background:
DEBUG:notpip.index:* https://pypi.python.org/simple/background/
DEBUG:notpip.index:Getting page https://pypi.python.org/simple/background/
DEBUG:pip9._vendor.cachecontrol.controller:Looking up "https://pypi.python.org/simple/background/" in the cache
DEBUG:pip9._vendor.cachecontrol.controller:Current age based on date: 8
DEBUG:pip9._vendor.cachecontrol.controller:Freshness lifetime from max-age: 600
DEBUG:pip9._vendor.cachecontrol.controller:Freshness lifetime from request max-age: 600
DEBUG:pip9._vendor.cachecontrol.controller:The response is "fresh", returning cached response
DEBUG:pip9._vendor.cachecontrol.controller:600 > 8
DEBUG:notpip.index:Analyzing links from page https://pypi.python.org/simple/background/
DEBUG:notpip.index:Found link https://pypi.python.org/packages/86/be/9de7386afe732d0e9a3972741b712a100bb706bc2fc7e0526f558739da93/background-0.1.0-py2.py3-none-any.whl#md5=c200d77f83b51637ee7bafaf9b6bad7c (from https://pypi.python.org/simple/background/), version: 0.1.0
DEBUG:notpip.index:Found link https://pypi.python.org/packages/39/4c/f2602b10b469a95caf2b601ab0bb5671adb77bfe21364816205e29f43d47/background-0.1.0.tar.gz#md5=a42c4edc5a83a0471919d655e3ee133a (from https://pypi.python.org/simple/background/), version: 0.1.0
DEBUG:notpip.index:Found link https://pypi.python.org/packages/d5/91/5bdb02c03859e835d2eacfa5b3f1d39a5d24cad2f3b30525e212ae3618b9/background-0.1.1-py2.py3-none-any.whl#md5=0bcb8095a8a8ab12c5e32b0676a6aa0a (from https://pypi.python.org/simple/background/), version: 0.1.1
DEBUG:notpip.index:Found link https://pypi.python.org/packages/70/aa/3f05d4b9af2ffceff988d54e68217d511ef629d61aac99094d526054c416/background-0.1.1.tar.gz#md5=a95ea2464137f49d134e70444ba496ad (from https://pypi.python.org/simple/background/), version: 0.1.1
  found candidate background==0.1.1 (constraint was <any>)

Finding secondary dependencies:
  background==0.1.1         requires futures

New dependencies found in this round:
  adding ['futures', '', '[]']
Removed dependencies in this round:
Unsafe dependencies in this round:
------------------------------------------------------------
Result of round 1: not stable

                          ROUND 2
Current constraints:
  background
  futures

Finding the best candidates:
  found candidate background==0.1.1 (constraint was <any>)
DEBUG:notpip.index:1 location(s) to search for versions of futures:
DEBUG:notpip.index:* https://pypi.python.org/simple/futures/
DEBUG:notpip.index:Getting page https://pypi.python.org/simple/futures/
DEBUG:pip9._vendor.cachecontrol.controller:Looking up "https://pypi.python.org/simple/futures/" in the cache
DEBUG:pip9._vendor.cachecontrol.controller:Current age based on date: 9
DEBUG:pip9._vendor.cachecontrol.controller:Freshness lifetime from max-age: 600
DEBUG:pip9._vendor.cachecontrol.controller:Freshness lifetime from request max-age: 600
DEBUG:pip9._vendor.cachecontrol.controller:The response is "fresh", returning cached response
DEBUG:pip9._vendor.cachecontrol.controller:600 > 9
DEBUG:notpip.index:Analyzing links from page https://pypi.python.org/simple/futures/
DEBUG:notpip.index:Found link https://pypi.python.org/packages/2e/65/81cb1de73f001863f90981f4f5a0cea8da08bf7a9ed2a1d812e8f53fe822/futures-0.1.tar.gz#md5=14c2e3af0f90479792555e20061a4532 (from https://pypi.python.org/simple/futures/), version: 0.1
DEBUG:notpip.index:Found link https://pypi.python.org/packages/09/9a/5cb5882312ae289aadab9dec2bd6557b25c45b79f3de5b400aafe547f3a5/futures-0.1.win32.exe#md5=3d4dbe19986aa9c654a2294cf6280c97 (from https://pypi.python.org/simple/futures/), version: 0.1.win32
DEBUG:notpip.index:Found link https://pypi.python.org/packages/08/80/a9e000de5b7372a514add2ef614a953be8bc3d13c8d6205455739d0fb189/futures-0.2.python3.tar.gz#md5=b6f1d454aa2ba3c870a3743c154b95d5 (from https://pypi.python.org/simple/futures/), version: 0.2.python3
DEBUG:notpip.index:Found link https://pypi.python.org/packages/b1/52/b6024136771fed73f22bb2aae612683ad3f0654af16bc2462d648917cff2/futures-0.2.python3.win32.exe#md5=242c2437e402a03034823abc91b79d3c (from https://pypi.python.org/simple/futures/), version: 0.2.python3.win32
DEBUG:notpip.index:Found link https://pypi.python.org/packages/58/da/820c674b07041df44a4bc6c062c0da3e68a5172bf0ad01312634ea39c4f4/futures-0.2.tar.gz#md5=1a913df7f2e50c2d445cbc959c70b01e (from https://pypi.python.org/simple/futures/), version: 0.2
DEBUG:notpip.index:Found link https://pypi.python.org/packages/a7/6a/a4386efd6fe91c85f97837c33eab5d3ec7ac29137f89930f15ad52865413/futures-0.2.win32.exe#md5=dc65adcd66ba6ecf0a89d8d6ec891de6 (from https://pypi.python.org/simple/futures/), version: 0.2.win32
DEBUG:notpip.index:Found link https://pypi.python.org/packages/18/ab/85f2f673ac828bc3d1c1ceb92c82382cdcbf890046c77cd74edaa63cb7d7/futures-1.0.tar.gz#md5=0171acd9e2486915ccbe3d0e2e92ec3f (from https://pypi.python.org/simple/futures/), version: 1.0
DEBUG:notpip.index:Found link https://pypi.python.org/packages/17/47/1382bf17e7faa123464057df0afc69cca9c7eb14e930734ce8b5bdbfad7e/futures-2.0.tar.gz#md5=bcc58e035661b9be325b6d278005c0f2 (from https://pypi.python.org/simple/futures/), version: 2.0
DEBUG:notpip.index:Found link https://pypi.python.org/packages/4b/19/93f2dd20a2e7eb72348c90b697ef7a0bd20168f973fc269f8986b8e49391/futures-2.1.tar.gz#md5=b1b9879b20e1ca45451124428ebd8157 (from https://pypi.python.org/simple/futures/), version: 2.1
DEBUG:notpip.index:Found link https://pypi.python.org/packages/10/0e/bde74dc8717243adba113ef415b4c4517c532ce18ca5c476f8f147b9f74e/futures-2.1.1.tar.gz#md5=158422d8727f148c439408a8b423f9bb (from https://pypi.python.org/simple/futures/), version: 2.1.1
DEBUG:notpip.index:Found link https://pypi.python.org/packages/36/0d/ff8097028893cc2ba0ad6c1a23f8aa5486728f2077f00989733978a4e289/futures-2.1.2.tar.gz#md5=a6fa247e3c5fe3d60d8e12f1b873cc88 (from https://pypi.python.org/simple/futures/), version: 2.1.2
DEBUG:notpip.index:Found link https://pypi.python.org/packages/1c/98/bc0938f1c7c46b14dae9b25fc7edd32a7c26ef78b16a8b90835971f2143b/futures-2.1.3.tar.gz#md5=3de68835c8035dff0495cbe7f5c75beb (from https://pypi.python.org/simple/futures/), version: 2.1.3
DEBUG:notpip.index:Found link https://pypi.python.org/packages/fd/6f/3ce6a5e9e0754a02ca3f0f6027c73bcc337dbd18517920eea2db0b369ae9/futures-2.1.4.tar.gz#md5=c6116d2d8c3c1a7c386ce196a2c98a4d (from https://pypi.python.org/simple/futures/), version: 2.1.4
DEBUG:notpip.index:Found link https://pypi.python.org/packages/32/e3/1de389e9e4372d106b1644b56cc0b94226a3ad637f96f45a8c3b55fc0709/futures-2.1.5-py2.py3-none-any.whl#md5=e6763f4016c0a6e31a0edc15072cc56e (from https://pypi.python.org/simple/futures/), version: 2.1.5
DEBUG:notpip.index:Found link https://pypi.python.org/packages/6d/e6/52fa0ac964982c773087d967feb628408b9c3d278d931761afd863c176ee/futures-2.1.5.tar.gz#md5=2fc924890ccd30a5fe676fa9bbcf0ab8 (from https://pypi.python.org/simple/futures/), version: 2.1.5
DEBUG:notpip.index:Found link https://pypi.python.org/packages/59/a0/cf4cd997e1750f0c2d91c6ea5abea218251c43c3581bcc2f118b00baf5cf/futures-2.1.6-py2.py3-none-any.whl#md5=9327a3b0bd315594d755180045947b03 (from https://pypi.python.org/simple/futures/), version: 2.1.6
DEBUG:notpip.index:Found link https://pypi.python.org/packages/38/25/85ec21efa813e4158dcea8bc676d1f81510af0ca3e2ba32ec47247d4857d/futures-2.1.6.tar.gz#md5=cfab9ac3cd55d6c7ddd0546a9f22f453 (from https://pypi.python.org/simple/futures/), version: 2.1.6
DEBUG:notpip.index:Found link https://pypi.python.org/packages/d7/1d/68874943aa37cf1c483fc61def813188473596043158faa6511c04a038b4/futures-2.2.0-py2.py3-none-any.whl#md5=12159c04b91abe5d26769f3ed4e01cc8 (from https://pypi.python.org/simple/futures/), version: 2.2.0
DEBUG:notpip.index:Found link https://pypi.python.org/packages/c0/12/927b89a24dcb336e5af18a8fbf581581c36e9620ae963a693a2522b2d340/futures-2.2.0.tar.gz#md5=310e446de8609ddb59d0886e35edb534 (from https://pypi.python.org/simple/futures/), version: 2.2.0
DEBUG:notpip.index:Found link https://pypi.python.org/packages/10/1c/182c9e959ca708ce611a7bf6b0ab6022d4a0e7edad79e5145c220431b028/futures-3.0.0-py2-none-any.whl#md5=d64edfffae0bbda1f28ceef944c1d7cc (from https://pypi.python.org/simple/futures/), version: 3.0.0
DEBUG:notpip.index:Found link https://pypi.python.org/packages/ea/c9/35287369718fc05059e7a9d0d73c53745fe981010b4185b3858e7d46eff1/futures-3.0.0.tar.gz#md5=ed8cd52e316ad1ec1ed3fd1f1f622961 (from https://pypi.python.org/simple/futures/), version: 3.0.0
DEBUG:notpip.index:Found link https://pypi.python.org/packages/5c/27/2f22e96c596b7cd83a3c1adceec4609eebd57ba3f8a061f993b4f84e592c/futures-3.0.1-py2-none-any.whl#md5=5abb7b2cdf2cc9f727b513c9bbaf415e (from https://pypi.python.org/simple/futures/), version: 3.0.1
DEBUG:notpip.index:Found link https://pypi.python.org/packages/b2/2c/6b6a57379e47031c6f52e625e0e2b8f6702a8d1f61b6e0daee391e82c187/futures-3.0.1.tar.gz#md5=c872d96e128fb79371409f68f8c17f74 (from https://pypi.python.org/simple/futures/), version: 3.0.1
DEBUG:notpip.index:Found link https://pypi.python.org/packages/87/77/e02574de90ec2944113447106e3be417af2d4b3dd21a9a050c04b007cd29/futures-3.0.2-py2-none-any.whl#md5=56b6b9c77a9488de90f4b81978753870 (from https://pypi.python.org/simple/futures/), version: 3.0.2
DEBUG:notpip.index:Found link https://pypi.python.org/packages/f8/e7/fc0fcbeb9193ba2d4de00b065e7fd5aecd0679e93ce95a07322b2b1434f4/futures-3.0.2.tar.gz#md5=42aaf1e4de48d6e871d77dc1f9d96d5a (from https://pypi.python.org/simple/futures/), version: 3.0.2
DEBUG:notpip.index:Found link https://pypi.python.org/packages/26/7d/a7e1130b63514cd7192f0ba0b53bdda7f96df88641ee0c97bfed8477f324/futures-3.0.3-py2-none-any.whl#md5=347b9df805d31b3edea63731ea79cb54 (from https://pypi.python.org/simple/futures/), version: 3.0.3
DEBUG:notpip.index:Found link https://pypi.python.org/packages/4c/dc/f9473006d4c9c52d4a4e977173fbcbfb1a8ef3a57e32e885edf994fd4a45/futures-3.0.3.tar.gz#md5=32171f72af7e80c266310794adc4db46 (from https://pypi.python.org/simple/futures/), version: 3.0.3
DEBUG:notpip.index:Found link https://pypi.python.org/packages/9b/3a/da5dd42fb24e577d7cbb13b6f3a1bd466b7f11ff67facd670583d6bb6931/futures-3.0.4-py2-none-any.whl#md5=0b6343283c10a6e3b9eb0453739ee84d (from https://pypi.python.org/simple/futures/), version: 3.0.4
DEBUG:notpip.index:Found link https://pypi.python.org/packages/8d/73/b5fff618482bc06c9711e7cdc0d5d7eb1904d35898f48f2d7f9696b08bef/futures-3.0.4.tar.gz#md5=27f0941502b3852ac78f3384e94f544e (from https://pypi.python.org/simple/futures/), version: 3.0.4
DEBUG:notpip.index:Found link https://pypi.python.org/packages/9c/3f/1d818ea03fb2956a2bdfa8f8a3b1319590f0f151a5584a8a3ae45085066c/futures-3.0.5-py2-none-any.whl#md5=968375970768ad7b7838cb07a0d60b44 (from https://pypi.python.org/simple/futures/), version: 3.0.5
DEBUG:notpip.index:Found link https://pypi.python.org/packages/55/db/97c1ca37edab586a1ae03d6892b6633d8eaa23b23ac40c7e5bbc55423c78/futures-3.0.5.tar.gz#md5=ced2c365e518242512d7a398b515ff95 (from https://pypi.python.org/simple/futures/), version: 3.0.5
DEBUG:notpip.index:Found link https://pypi.python.org/packages/d5/ea/a77d7379219f717333c7726bcaafa7839f11f475a3d3691ec9ed5b4add0e/futures-3.1.0-py2-none-any.whl#md5=a2e7fbede87d71aee50caaa44b8966b8 (from https://pypi.python.org/simple/futures/), version: 3.1.0
DEBUG:notpip.index:Found link https://pypi.python.org/packages/25/83/113da7c7832a4efa80ec7fd5d25b2ea431d9a847cd78f1fa98ddd99d591a/futures-3.1.0.tar.gz#md5=ab78b3ed854a38b82af19f3d617d29eb (from https://pypi.python.org/simple/futures/), version: 3.1.0
DEBUG:notpip.index:Found link https://pypi.python.org/packages/a6/1c/72a18c8c7502ee1b38a604a5c5243aa8c2a64f4bba4e6631b1b8972235dd/futures-3.1.1-py2-none-any.whl#md5=61a88f749eb3655042f95d198f783ef3 (from https://pypi.python.org/simple/futures/), version: 3.1.1
DEBUG:notpip.index:Found link https://pypi.python.org/packages/cc/26/b61e3a4eb50653e8a7339d84eeaa46d1e93b92951978873c220ae64d0733/futures-3.1.1.tar.gz#md5=77f261ab86cc78efa2c5fe7be27c3ec8 (from https://pypi.python.org/simple/futures/), version: 3.1.1
DEBUG:notpip.index:Found link https://pypi.python.org/packages/2d/99/b2c4e9d5a30f6471e410a146232b4118e697fa3ffc06d6a65efde84debd0/futures-3.2.0-py2-none-any.whl#md5=cfd62ab6c9852b04bb6048480fefaa75 (from https://pypi.python.org/simple/futures/) (requires-python:>=2.6, <3), version: 3.2.0
DEBUG:notpip.index:Found link https://pypi.python.org/packages/1f/9e/7b2ff7e965fc654592269f2906ade1c7d705f1bf25b7d469fa153f7d19eb/futures-3.2.0.tar.gz#md5=d1b299a06b96ccb59f70324716dc0016 (from https://pypi.python.org/simple/futures/) (requires-python:>=2.6, <3), version: 3.2.0
  found candidate futures==3.2.0 (constraint was <any>)

Finding secondary dependencies:
  background==0.1.1         requires futures
  futures==3.2.0            requires -
------------------------------------------------------------
Result of round 2: stable, done
DEBUG:notpip.index:1 location(s) to search for versions of background:
DEBUG:notpip.index:* https://pypi.python.org/simple/background/
DEBUG:notpip.index:Getting page https://pypi.python.org/simple/background/
DEBUG:pip9._vendor.cachecontrol.controller:Looking up "https://pypi.python.org/simple/background/" in the cache
DEBUG:pip9._vendor.cachecontrol.controller:Current age based on date: 9
DEBUG:pip9._vendor.cachecontrol.controller:Freshness lifetime from max-age: 600
DEBUG:pip9._vendor.cachecontrol.controller:Freshness lifetime from request max-age: 600
DEBUG:pip9._vendor.cachecontrol.controller:The response is "fresh", returning cached response
DEBUG:pip9._vendor.cachecontrol.controller:600 > 9
DEBUG:notpip.index:Analyzing links from page https://pypi.python.org/simple/background/
DEBUG:notpip.index:Found link https://pypi.python.org/packages/86/be/9de7386afe732d0e9a3972741b712a100bb706bc2fc7e0526f558739da93/background-0.1.0-py2.py3-none-any.whl#md5=c200d77f83b51637ee7bafaf9b6bad7c (from https://pypi.python.org/simple/background/), version: 0.1.0
DEBUG:notpip.index:Found link https://pypi.python.org/packages/39/4c/f2602b10b469a95caf2b601ab0bb5671adb77bfe21364816205e29f43d47/background-0.1.0.tar.gz#md5=a42c4edc5a83a0471919d655e3ee133a (from https://pypi.python.org/simple/background/), version: 0.1.0
DEBUG:notpip.index:Found link https://pypi.python.org/packages/d5/91/5bdb02c03859e835d2eacfa5b3f1d39a5d24cad2f3b30525e212ae3618b9/background-0.1.1-py2.py3-none-any.whl#md5=0bcb8095a8a8ab12c5e32b0676a6aa0a (from https://pypi.python.org/simple/background/), version: 0.1.1
DEBUG:notpip.index:Found link https://pypi.python.org/packages/70/aa/3f05d4b9af2ffceff988d54e68217d511ef629d61aac99094d526054c416/background-0.1.1.tar.gz#md5=a95ea2464137f49d134e70444ba496ad (from https://pypi.python.org/simple/background/), version: 0.1.1
DEBUG:pip9._vendor.cachecontrol.controller:Looking up "https://pypi.python.org/packages/70/aa/3f05d4b9af2ffceff988d54e68217d511ef629d61aac99094d526054c416/background-0.1.1.tar.gz" in the cache
DEBUG:pip9._vendor.cachecontrol.controller:Current age based on date: 6
DEBUG:pip9._vendor.cachecontrol.controller:Freshness lifetime from max-age: 31557600
DEBUG:pip9._vendor.cachecontrol.controller:The response is "fresh", returning cached response
DEBUG:pip9._vendor.cachecontrol.controller:31557600 > 6
DEBUG:pip9._vendor.cachecontrol.controller:Looking up "https://pypi.python.org/packages/d5/91/5bdb02c03859e835d2eacfa5b3f1d39a5d24cad2f3b30525e212ae3618b9/background-0.1.1-py2.py3-none-any.whl" in the cache
DEBUG:pip9._vendor.cachecontrol.controller:Current age based on date: 5895212
DEBUG:pip9._vendor.cachecontrol.controller:Freshness lifetime from max-age: 31557600
DEBUG:pip9._vendor.cachecontrol.controller:The response is "fresh", returning cached response
DEBUG:pip9._vendor.cachecontrol.controller:31557600 > 5895212
DEBUG:notpip.index:1 location(s) to search for versions of futures:
DEBUG:notpip.index:* https://pypi.python.org/simple/futures/
DEBUG:notpip.index:Getting page https://pypi.python.org/simple/futures/
DEBUG:pip9._vendor.cachecontrol.controller:Looking up "https://pypi.python.org/simple/futures/" in the cache
DEBUG:pip9._vendor.cachecontrol.controller:Current age based on date: 9
DEBUG:pip9._vendor.cachecontrol.controller:Freshness lifetime from max-age: 600
DEBUG:pip9._vendor.cachecontrol.controller:Freshness lifetime from request max-age: 600
DEBUG:pip9._vendor.cachecontrol.controller:The response is "fresh", returning cached response
DEBUG:pip9._vendor.cachecontrol.controller:600 > 9
DEBUG:notpip.index:Analyzing links from page https://pypi.python.org/simple/futures/
DEBUG:notpip.index:Found link https://pypi.python.org/packages/2e/65/81cb1de73f001863f90981f4f5a0cea8da08bf7a9ed2a1d812e8f53fe822/futures-0.1.tar.gz#md5=14c2e3af0f90479792555e20061a4532 (from https://pypi.python.org/simple/futures/), version: 0.1
DEBUG:notpip.index:Found link https://pypi.python.org/packages/09/9a/5cb5882312ae289aadab9dec2bd6557b25c45b79f3de5b400aafe547f3a5/futures-0.1.win32.exe#md5=3d4dbe19986aa9c654a2294cf6280c97 (from https://pypi.python.org/simple/futures/), version: 0.1.win32
DEBUG:notpip.index:Found link https://pypi.python.org/packages/08/80/a9e000de5b7372a514add2ef614a953be8bc3d13c8d6205455739d0fb189/futures-0.2.python3.tar.gz#md5=b6f1d454aa2ba3c870a3743c154b95d5 (from https://pypi.python.org/simple/futures/), version: 0.2.python3
DEBUG:notpip.index:Found link https://pypi.python.org/packages/b1/52/b6024136771fed73f22bb2aae612683ad3f0654af16bc2462d648917cff2/futures-0.2.python3.win32.exe#md5=242c2437e402a03034823abc91b79d3c (from https://pypi.python.org/simple/futures/), version: 0.2.python3.win32
DEBUG:notpip.index:Found link https://pypi.python.org/packages/58/da/820c674b07041df44a4bc6c062c0da3e68a5172bf0ad01312634ea39c4f4/futures-0.2.tar.gz#md5=1a913df7f2e50c2d445cbc959c70b01e (from https://pypi.python.org/simple/futures/), version: 0.2
DEBUG:notpip.index:Found link https://pypi.python.org/packages/a7/6a/a4386efd6fe91c85f97837c33eab5d3ec7ac29137f89930f15ad52865413/futures-0.2.win32.exe#md5=dc65adcd66ba6ecf0a89d8d6ec891de6 (from https://pypi.python.org/simple/futures/), version: 0.2.win32
DEBUG:notpip.index:Found link https://pypi.python.org/packages/18/ab/85f2f673ac828bc3d1c1ceb92c82382cdcbf890046c77cd74edaa63cb7d7/futures-1.0.tar.gz#md5=0171acd9e2486915ccbe3d0e2e92ec3f (from https://pypi.python.org/simple/futures/), version: 1.0
DEBUG:notpip.index:Found link https://pypi.python.org/packages/17/47/1382bf17e7faa123464057df0afc69cca9c7eb14e930734ce8b5bdbfad7e/futures-2.0.tar.gz#md5=bcc58e035661b9be325b6d278005c0f2 (from https://pypi.python.org/simple/futures/), version: 2.0
DEBUG:notpip.index:Found link https://pypi.python.org/packages/4b/19/93f2dd20a2e7eb72348c90b697ef7a0bd20168f973fc269f8986b8e49391/futures-2.1.tar.gz#md5=b1b9879b20e1ca45451124428ebd8157 (from https://pypi.python.org/simple/futures/), version: 2.1
DEBUG:notpip.index:Found link https://pypi.python.org/packages/10/0e/bde74dc8717243adba113ef415b4c4517c532ce18ca5c476f8f147b9f74e/futures-2.1.1.tar.gz#md5=158422d8727f148c439408a8b423f9bb (from https://pypi.python.org/simple/futures/), version: 2.1.1
DEBUG:notpip.index:Found link https://pypi.python.org/packages/36/0d/ff8097028893cc2ba0ad6c1a23f8aa5486728f2077f00989733978a4e289/futures-2.1.2.tar.gz#md5=a6fa247e3c5fe3d60d8e12f1b873cc88 (from https://pypi.python.org/simple/futures/), version: 2.1.2
DEBUG:notpip.index:Found link https://pypi.python.org/packages/1c/98/bc0938f1c7c46b14dae9b25fc7edd32a7c26ef78b16a8b90835971f2143b/futures-2.1.3.tar.gz#md5=3de68835c8035dff0495cbe7f5c75beb (from https://pypi.python.org/simple/futures/), version: 2.1.3
DEBUG:notpip.index:Found link https://pypi.python.org/packages/fd/6f/3ce6a5e9e0754a02ca3f0f6027c73bcc337dbd18517920eea2db0b369ae9/futures-2.1.4.tar.gz#md5=c6116d2d8c3c1a7c386ce196a2c98a4d (from https://pypi.python.org/simple/futures/), version: 2.1.4
DEBUG:notpip.index:Found link https://pypi.python.org/packages/32/e3/1de389e9e4372d106b1644b56cc0b94226a3ad637f96f45a8c3b55fc0709/futures-2.1.5-py2.py3-none-any.whl#md5=e6763f4016c0a6e31a0edc15072cc56e (from https://pypi.python.org/simple/futures/), version: 2.1.5
DEBUG:notpip.index:Found link https://pypi.python.org/packages/6d/e6/52fa0ac964982c773087d967feb628408b9c3d278d931761afd863c176ee/futures-2.1.5.tar.gz#md5=2fc924890ccd30a5fe676fa9bbcf0ab8 (from https://pypi.python.org/simple/futures/), version: 2.1.5
DEBUG:notpip.index:Found link https://pypi.python.org/packages/59/a0/cf4cd997e1750f0c2d91c6ea5abea218251c43c3581bcc2f118b00baf5cf/futures-2.1.6-py2.py3-none-any.whl#md5=9327a3b0bd315594d755180045947b03 (from https://pypi.python.org/simple/futures/), version: 2.1.6
DEBUG:notpip.index:Found link https://pypi.python.org/packages/38/25/85ec21efa813e4158dcea8bc676d1f81510af0ca3e2ba32ec47247d4857d/futures-2.1.6.tar.gz#md5=cfab9ac3cd55d6c7ddd0546a9f22f453 (from https://pypi.python.org/simple/futures/), version: 2.1.6
DEBUG:notpip.index:Found link https://pypi.python.org/packages/d7/1d/68874943aa37cf1c483fc61def813188473596043158faa6511c04a038b4/futures-2.2.0-py2.py3-none-any.whl#md5=12159c04b91abe5d26769f3ed4e01cc8 (from https://pypi.python.org/simple/futures/), version: 2.2.0
DEBUG:notpip.index:Found link https://pypi.python.org/packages/c0/12/927b89a24dcb336e5af18a8fbf581581c36e9620ae963a693a2522b2d340/futures-2.2.0.tar.gz#md5=310e446de8609ddb59d0886e35edb534 (from https://pypi.python.org/simple/futures/), version: 2.2.0
DEBUG:notpip.index:Found link https://pypi.python.org/packages/10/1c/182c9e959ca708ce611a7bf6b0ab6022d4a0e7edad79e5145c220431b028/futures-3.0.0-py2-none-any.whl#md5=d64edfffae0bbda1f28ceef944c1d7cc (from https://pypi.python.org/simple/futures/), version: 3.0.0
DEBUG:notpip.index:Found link https://pypi.python.org/packages/ea/c9/35287369718fc05059e7a9d0d73c53745fe981010b4185b3858e7d46eff1/futures-3.0.0.tar.gz#md5=ed8cd52e316ad1ec1ed3fd1f1f622961 (from https://pypi.python.org/simple/futures/), version: 3.0.0
DEBUG:notpip.index:Found link https://pypi.python.org/packages/5c/27/2f22e96c596b7cd83a3c1adceec4609eebd57ba3f8a061f993b4f84e592c/futures-3.0.1-py2-none-any.whl#md5=5abb7b2cdf2cc9f727b513c9bbaf415e (from https://pypi.python.org/simple/futures/), version: 3.0.1
DEBUG:notpip.index:Found link https://pypi.python.org/packages/b2/2c/6b6a57379e47031c6f52e625e0e2b8f6702a8d1f61b6e0daee391e82c187/futures-3.0.1.tar.gz#md5=c872d96e128fb79371409f68f8c17f74 (from https://pypi.python.org/simple/futures/), version: 3.0.1
DEBUG:notpip.index:Found link https://pypi.python.org/packages/87/77/e02574de90ec2944113447106e3be417af2d4b3dd21a9a050c04b007cd29/futures-3.0.2-py2-none-any.whl#md5=56b6b9c77a9488de90f4b81978753870 (from https://pypi.python.org/simple/futures/), version: 3.0.2
DEBUG:notpip.index:Found link https://pypi.python.org/packages/f8/e7/fc0fcbeb9193ba2d4de00b065e7fd5aecd0679e93ce95a07322b2b1434f4/futures-3.0.2.tar.gz#md5=42aaf1e4de48d6e871d77dc1f9d96d5a (from https://pypi.python.org/simple/futures/), version: 3.0.2
DEBUG:notpip.index:Found link https://pypi.python.org/packages/26/7d/a7e1130b63514cd7192f0ba0b53bdda7f96df88641ee0c97bfed8477f324/futures-3.0.3-py2-none-any.whl#md5=347b9df805d31b3edea63731ea79cb54 (from https://pypi.python.org/simple/futures/), version: 3.0.3
DEBUG:notpip.index:Found link https://pypi.python.org/packages/4c/dc/f9473006d4c9c52d4a4e977173fbcbfb1a8ef3a57e32e885edf994fd4a45/futures-3.0.3.tar.gz#md5=32171f72af7e80c266310794adc4db46 (from https://pypi.python.org/simple/futures/), version: 3.0.3
DEBUG:notpip.index:Found link https://pypi.python.org/packages/9b/3a/da5dd42fb24e577d7cbb13b6f3a1bd466b7f11ff67facd670583d6bb6931/futures-3.0.4-py2-none-any.whl#md5=0b6343283c10a6e3b9eb0453739ee84d (from https://pypi.python.org/simple/futures/), version: 3.0.4
DEBUG:notpip.index:Found link https://pypi.python.org/packages/8d/73/b5fff618482bc06c9711e7cdc0d5d7eb1904d35898f48f2d7f9696b08bef/futures-3.0.4.tar.gz#md5=27f0941502b3852ac78f3384e94f544e (from https://pypi.python.org/simple/futures/), version: 3.0.4
DEBUG:notpip.index:Found link https://pypi.python.org/packages/9c/3f/1d818ea03fb2956a2bdfa8f8a3b1319590f0f151a5584a8a3ae45085066c/futures-3.0.5-py2-none-any.whl#md5=968375970768ad7b7838cb07a0d60b44 (from https://pypi.python.org/simple/futures/), version: 3.0.5
DEBUG:notpip.index:Found link https://pypi.python.org/packages/55/db/97c1ca37edab586a1ae03d6892b6633d8eaa23b23ac40c7e5bbc55423c78/futures-3.0.5.tar.gz#md5=ced2c365e518242512d7a398b515ff95 (from https://pypi.python.org/simple/futures/), version: 3.0.5
DEBUG:notpip.index:Found link https://pypi.python.org/packages/d5/ea/a77d7379219f717333c7726bcaafa7839f11f475a3d3691ec9ed5b4add0e/futures-3.1.0-py2-none-any.whl#md5=a2e7fbede87d71aee50caaa44b8966b8 (from https://pypi.python.org/simple/futures/), version: 3.1.0
DEBUG:notpip.index:Found link https://pypi.python.org/packages/25/83/113da7c7832a4efa80ec7fd5d25b2ea431d9a847cd78f1fa98ddd99d591a/futures-3.1.0.tar.gz#md5=ab78b3ed854a38b82af19f3d617d29eb (from https://pypi.python.org/simple/futures/), version: 3.1.0
DEBUG:notpip.index:Found link https://pypi.python.org/packages/a6/1c/72a18c8c7502ee1b38a604a5c5243aa8c2a64f4bba4e6631b1b8972235dd/futures-3.1.1-py2-none-any.whl#md5=61a88f749eb3655042f95d198f783ef3 (from https://pypi.python.org/simple/futures/), version: 3.1.1
DEBUG:notpip.index:Found link https://pypi.python.org/packages/cc/26/b61e3a4eb50653e8a7339d84eeaa46d1e93b92951978873c220ae64d0733/futures-3.1.1.tar.gz#md5=77f261ab86cc78efa2c5fe7be27c3ec8 (from https://pypi.python.org/simple/futures/), version: 3.1.1
DEBUG:notpip.index:Found link https://pypi.python.org/packages/2d/99/b2c4e9d5a30f6471e410a146232b4118e697fa3ffc06d6a65efde84debd0/futures-3.2.0-py2-none-any.whl#md5=cfd62ab6c9852b04bb6048480fefaa75 (from https://pypi.python.org/simple/futures/) (requires-python:>=2.6, <3), version: 3.2.0
DEBUG:notpip.index:Found link https://pypi.python.org/packages/1f/9e/7b2ff7e965fc654592269f2906ade1c7d705f1bf25b7d469fa153f7d19eb/futures-3.2.0.tar.gz#md5=d1b299a06b96ccb59f70324716dc0016 (from https://pypi.python.org/simple/futures/) (requires-python:>=2.6, <3), version: 3.2.0
DEBUG:pip9._vendor.cachecontrol.controller:Looking up "https://pypi.python.org/packages/2d/99/b2c4e9d5a30f6471e410a146232b4118e697fa3ffc06d6a65efde84debd0/futures-3.2.0-py2-none-any.whl" in the cache
DEBUG:pip9._vendor.cachecontrol.controller:Current age based on date: 5012701
DEBUG:pip9._vendor.cachecontrol.controller:Freshness lifetime from max-age: 31557600
DEBUG:pip9._vendor.cachecontrol.controller:The response is "fresh", returning cached response
DEBUG:pip9._vendor.cachecontrol.controller:31557600 > 5012701
DEBUG:pip9._vendor.cachecontrol.controller:Looking up "https://pypi.python.org/packages/1f/9e/7b2ff7e965fc654592269f2906ade1c7d705f1bf25b7d469fa153f7d19eb/futures-3.2.0.tar.gz" in the cache
DEBUG:pip9._vendor.cachecontrol.controller:Current age based on date: 858057
DEBUG:pip9._vendor.cachecontrol.controller:Freshness lifetime from max-age: 31557600
DEBUG:pip9._vendor.cachecontrol.controller:The response is "fresh", returning cached response
DEBUG:pip9._vendor.cachecontrol.controller:31557600 > 858057
RESULTS:
[{"name": "background", "version": "0.1.1", "hashes": ["sha256:8f64df9b1f1d4f91603f16d25f79691fa87eff62244d631b8b69cf121396b725", "sha256:b2fb684c150aaf1c4716686e7bd0e81a5c13db1852e7af48c01b98a3486a84c6"]}, {"name": "futures", "version": "3.2.0", "hashes": ["sha256:ec0a6cb848cc212002b9828c3e34c675e0c9ff6741dc445cab6fdd4e1085d1f1", "sha256:9ec02aa7d674acb8618afb127e27fde7fc68994c0437ad759fa094a574adb265"]}]

@jacebrowning this is a resolver bug which hasn’t been fixed in a release yet -part of the resolver changes now include otherwise excluded files, it’s including .exe files here. Will try to get it released ASAP

An ugly workaround is to change the virtualenv to Python 2.7, then freeze your requirements file pipenv run pip freeze > requirements.txt and change the version number manually in there.

I am also getting this when I try to install a py3 virtualenv with pipenv, the only way to get around it seems to be to change the python version being required to py2.7 but this of course breaks because the syntax is py3. Is there a better workaround somewhere?

@LasseGravesen We’ve since removed dependency to futures altogether. You might want to consider purge your environment (i.e. uninstall everything until pip list shows nothing but pip and setuptools) and install a fresh copy of Pipenv.

This is still an issue. at least with brew installed pipenv
$ pipenv --version
pipenv, version 2018.05.18
$ which pipenv
/usr/local/bin/pipenv

Also pip3 install --user pipenv finds the same version, with the same issue.
Can you be more clear about "purge your environment" ?
Can we have a link to the "unfixed bug"? @techalchemy

Given you use --user but which finds Pipenv globally in /usr/local, I’d guess you have a mismatch in versions in PATH and sys.path. With --use pip should install the executable in ~/.local, so there is something going very wrong in your setup.

I'm running into this same issue when installing the azure package.
Installing the package using pip install works fine.
It seems that the following line is not interpeted correctly; (https://github.com/Azure/azure-cosmosdb-python/blob/master/requirements.txt)
futures;python_version<="2.7"

My environment:
λ python --version
Python 3.6.5

λ pip list
Package          Version
---------------- ---------
certifi          2018.4.16
pip              10.0.1
pipenv           2018.5.18
setuptools       39.2.0
virtualenv       16.0.0
virtualenv-clone 0.3.0

You can add this to your lock file before `"version": "3.2.0"
"markers": "python_version == '2.6' or python_version == '2.7'",

I am still seeing this issue with pipenv, version 2018.05.18

Grow does not install with the default python downloaded today (3.6.5) due to this same error.

I feel like this particular issue is probably addressed and I just can't tell, but I have an odd futures issue that seems to be related to the pipenv lock file (but only seems to be an issue on a redhat system, not my mac where I have things using homebrew):
https://gist.github.com/Drin/13784a703319d48dcca79ef7a36ce458
In the above gist, I have tried to have a simple layout with commands and outputs and errors grouped reasonably logically. For all of my environment/software information, see the gist.
The summary of the issue I'm seeing is:

When I don't have futures installed, things seem to work well.
When I pipenv install futures, pipenv grabs and installs the correct futures version (3.1.1) that seems to be available for Python 3.6 (specifically, 3.6.3 from the yum repos):

However, it seems that pipenv does not correctly update the Pipfile.lock file--although a lock file is seemingly created (I see a hash in the output), pipenv does not seem to actually swap it with the old Pipfile.lock file (see gist - "Futures Problem")

When I pipenv install pyarrow, it seems to have a different, related problem with futures, though I'm not sure what that is and I will document with their bug tracker.

Anyways, I'm not entirely sure where the source of this error is, and I don't have the time to dig in much more today. I am able to work around the issue by manually changing the Pipfile.lock file to have versions of the libraries I know work:

futures=3.1.1
pyarrow=0.9.0

but I thought it might be reasonable to mention this issue here, for someone to follow up at some point.
Thanks for any help anyone can provide! I will update here if I find any relevant info, including issues that are still open.

can get around this for now with pipenv install --skip-lock which is less than ideal.

I wanted to maintain the Pipe.lock file which is used in my docker orchestration because of this issue, It fails entire application to be stable.
Locking [dev-packages] dependencies…
Locking [packages] dependencies…
Warning: Your dependencies could not be resolved. You likely have a mismatch in your sub-dependencies.
  You can use $ pipenv install --skip-lock to bypass this mechanism, then run $ pipenv graph to inspect the situation.
Could not find a version that matches futures==3.1.1,==3.2.0
Tried: 0.2.python3, 0.1, 0.2, 1.0, 2.0, 2.1, 2.1.1, 2.1.2, 2.1.3, 2.1.4, 2.1.5, 2.1.5, 2.1.6, 2.1.6, 2.2.0, 2.2.0, 3.0.0, 3.0.0, 3.0.1, 3.0.1, 3.0.2, 3.0.2, 3.0.3, 3.0.3, 3.0.4, 3.0.4, 3.0.5, 3.0.5, 3.1.0, 3.1.0, 3.1.1, 3.1.1

I resolved the issue by upgrading the pip and pipenv.
$ sudo pip install --upgrade pip
$ sudo pip install --upgrade pipenv

Still a problem on OS X. What the heck?

getting this error on OS X as well, on a Python 3.6.6 virtual environment with pipenv install zappa
Adding zappa to Pipfile's [packages]...
Pipfile.lock not found, creating...
Locking [dev-packages] dependencies...
Locking [packages] dependencies...
Updated Pipfile.lock (38062f)!
Installing dependencies from Pipfile.lock (38062f)...
An error occurred while installing futures==3.2.0! Will try again.
  ��   ▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉ 33/33 — 00:00:09
Installing initially failed dependencies...
Collecting futures==3.2.0 ▉▉▉▉▉▉▉▉▉▉▉ 0/1 — 00:00:00

  Could not find a version that satisfies the requirement futures==3.2.0 (from -r /var/folders/sw/3hvw1zqj1ssfbslpcd66fwq53h18cy/T/pipenv-3l5pi3pj-requirements/pipenv-y15vbzja-requirement.txt (line 1)) (from versions: 0.2.python3, 0.1, 0.2, 1.0, 2.0, 2.1, 2.1.1, 2.1.2, 2.1.3, 2.1.4, 2.1.5, 2.1.6, 2.2.0, 3.0.0, 3.0.1, 3.0.2, 3.0.3, 3.0.4, 3.0.5, 3.1.0, 3.1.1)
No matching distribution found for futures==3.2.0 (from -r /var/folders/sw/3hvw1zqj1ssfbslpcd66fwq53h18cy/T/pipenv-3l5pi3pj-requirements/pipenv-y15vbzja-requirement.txt (line 1))
You are using pip version 10.0.1, however version 18.0 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.

I'm having the same problem with zappa as well.
After digging through pipenv 2018.7.1 I found that the issue is in how markers are handled.  The and condition in the case where 2 'python_version' conditions were defined wasn't being properly properly.
This is already resolved in the current master branch (just not released yet).
You can use this command to install pipenv from the repo:
sudo python3.6 -m pip install git+git://github.com/pypa/pipenv.git@541b87abd5baa1b6528ab5938fc275b6e982d7e0 --user
I've confirmed here that zappa 0.46.2 installs properly with this version.

I was facing the same issue and getting a bunch of errors related to futures and markers. Not sure how exactly, but I did below steps and was able to successfully create the virtualenv via pipenv:
pipenv --rm
pipenv lock --clear
pipenv shell
pipenv install

This link helped me arrive at the lock --clear step. Hopefully this helps others.


Preparing For Release 3.1.1-RC1

The commit message should say RC2. Also didn't we agree that the script changes will be committed as the CI user?

Merged with modified commit, please close this pull request.