text:
Consider changing the way of Action class usage

The current Action class has that big problem that it requires user-provided id forcing a user to use magic numbers or declare constants. Both are bad. Magic numbers are bad for obvious reason and named constants are bad because user has to declare a constant and use almost the same name for Action variable anyway. Also both are not scalable.
So for the version 1.0 please consider the changing of Action in the way that it will not require user-provided id.
Also would be much better if user could connect Action to the delegate instead of using of action listener with switch-case.

Good idea. But it's hard to propose good solution.

Maybe using signals? With variant-like argument which replaces the current *Param properties.
This should allow to separate action from the passed data. I.e. arguments should not be stored (or at least should not persist) in Action object.
As for default action ids the new entity can be created - ActionInfo which will contain such information as translatable text, system-dependent shortcut and icon (resource id?). Then add Action constructor specially for default action ids and/or for ActionInfo(and add function like getActionInfoForDefaultId).
The idea is to distinguish between actions and related data.

authors: FreeSlave buggins

repo: buggins/dlangui


text:
how to start without docker?

i have this error when opening the page
Warning: Unknown: Failed to open stream: No such file or directory in Unknown on line 0
Fatal error: Failed opening required '/Volumes/MacData/work/buggregator/server.php' (include_path='.:/usr/local/Cellar/php/8.0.12/share/php/pear') in Unknown on line 0

hello!
./rr serve

Got it working. But the port use is 8000.
I have to set ray port to 8000 to make it work

Got it working. But the port use is 8000. I have to set ray port to 8000 to make it work

You can change port in the config file .rr.yaml

Got it working. But the port use is 8000. I have to set ray port to 8000 to make it work

You can change port in the config file .rr.yaml

Do i change the port for web or add server for ray with port 23517?

Got it working. But the port use is 8000. I have to set ray port to 8000 to make it work

You can change port in the config file .rr.yaml

Do i change the port for web or add server for ray with port 23517?

You can change default port for ray via config file ray.php in your app https://spatie.be/docs/ray/v1/configuration/framework-agnostic-php

Thank you for fast response. I think need to add this to documentation for easy use

source: gharchive/issue

authors: anditsung butschster

repo: buggregator/app

license: MIT

license_type: permissive

license_source: github-api


text:
Bugsnag must be removed for mobile footer dropdowns to work when Shopify Chat is installed on Pipeline theme

Describe the bug
Hey team, Tobin from Theme Support here. I was instructed by developers working with the Shopify Inbox app team to post this issue here.
Footer dropdowns for the third party theme Pipeline by Groupthought no longer work when the Shopify Chat widget is present. Removing Bugsnag as a dependency on the Shopify Inbox app seems to resolve the issue. We have received two escalated tickets with this exact issue now. I have a ticket on hold with the merchant from Store #1 (linked below) and the Groupthought developers since it's been a bit of a back and forth about whether it's the app or the theme causing the issue.
Specifically, this line of code in Bugsnag is the cause of the issue.
Theme Support has a Third Party Theme Issue Repo - here is the issue posted there as well.
Store #1 where the issue is active.
Store #2 where they have removed footer dropdowns but when they are implemented the issue occurs.
Steps to reproduce

Travel to this merchant's live theme.
Attempt to open the footer menu drawers.
Remove BugSnag and this now functions correctly

(Issue can also be seen on this staging store.)
Environment

Bugsnag version: @bugsnag/js": "^7.22.3"
Browser version (e.g. chrome, safari): All browsers
Device (e.g. iphonex): Mobile devices only - can be replicated on desktop viewing mobile view.

Example code snippet
https://github.com/bugsnag/bugsnag-js/blob/8a70db4747e4ea40e1e9ce128c8b4582d93641f7/packages/plugin-inline-script-content/inline-script-content.js#L125

Hi Bugsnag team,
I'm a Shopify engineer who looked into this issue. I'm here to provide more technical context. Our app (Shopify Inbox) is a script that loads on a merchant's website. Our Inbox app also has Bugsnag as a dependency. We noticed that on certain websites, Bugsnag throws an error TypeError: 'arguments', 'callee', and 'caller' cannot be accessed in this context..., which causes bugs on websites running our script (like the footer dropdowns not opening on this site on iOS browsers). When we removed Bugsnag as a dependency, these bugs disappear. We definitely want to keep using Bugsnag though so we're hoping your team can provide the fix. Thanks!

Any update or information on this as of yet? We are getting several reports of this now - all accounts utilizing the Pipeline theme by Groupthought.

Hi :wave:
I have raised this with our engineers. we are investigating this further and I will keep you updated once we have more information to share.

Hi everyone,
After some brief investigation, it appears that both our inline script content plugin and the Shopify chat widget monkey patch the addEventListener methods of many window objects, and I believe that some context with either this or arguments is being lost through the multiple layers of patching. This could also be caused by modern browsers using strict mode - but we will need to spend more time investigating to ensure we take the correct approach to resolve this.
In this meantime, you can disable the inline script checking with the trackInlineScripts configuration option, which will prevent the monkey patch from being applied.
Hope this helps!

@gingerbenw and @clr182 turning [trackInlineScripts](https://docs.bugsnag.com/platforms/javascript/configuration-options/#trackinlinescripts) seemed to have worked for us, thank you!!

Thank you!

authors: JustTobinShopify clr182 gingerbenw laurieoulikesfood

repo: bugsnag/bugsnag-js

license: mit

license_source: bigquery


text:
restify: consider providing original request in beforeSend

This is also in close connection with  #420
For instance, I would like to use the original request to tag along req.user which contains my user details - something that the restify plugin does not do automatically.
The current approach makes the plugin pretty inflexible and the only way I can modify getRequestAndMetaDataFromReq is to fork.

My current solution is to add another middleware after the bugsnag requestHandler to attach the user to the req.bugsnag.

Thanks for the feedback. Your solution sounds reasonable but we'll look at this and see if there's a nicer api we can provide.

authors: bengourley karthikiyengar


text:
希望增加导出功能

希望增加导出功能

已经在待办中了，后面空下来就会做

authors: baseSky build-admin

repo: build-admin/buildadmin


text:
Clarifying BSP Specification: Servers should send build/publishDiagnostics with empty array to clear former diagnostics?

Describe the use-case for this feature
In the LSP specification, LSP servers are required to send textDocument/publishDiagnostics with an empty array of diagnostics to clear any previously published diagnostics.

If the computed set is empty, the server must push an empty array to clear former diagnostics.
https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_publishDiagnostics

However, the BSP specification does not provide clear guidance on how to clear previously published diagnostics, which has led to some confusion:

A BSP client (scalameta/metals) expects to receive build/publishDiagnostics with an empty diagnostics array (and reset = true).
Some BSP servers, such as sbt and bloop, do send build/publishDiagnostics with an empty array of diagnostics when the computed set is empty.
Yet, other BSP servers, like bazel-bsp and mill-bsp, do not follow this practice.

What do you propose
So, I propose there is a need to clarify how BSP clients should clear former diagnostics.
Should servers send build/publishDiagnostics with empty diagnostics, or should clients clear former diagnostics upon receiving a build/taskFinish with both errors and warnings set to 0?
I've checked to make sure there isn't already a way to support this in the current protocol

[X] I've checked the existing protocol and there isn't a way to do this currently

Maintainer approval (This is for the maintainers)

[x] Jetbrains
[x] Metals
[ ] Scala Center

Yes, the behavior of sbt and bloop was our informal agreement back then. I think we should follow the LSP practice in how it works, and be explicit about expected behavior.

authors: jastice tanishiking


text:
feat(rust): adding rotate-key to ockam_command cli

This commit adds the rotate-key command to the CLI. It can be used via ockam identity rotate-key --node n1 --label OCKAM_RK or the label argument can be omitted to use the default label of "OCKAM_RK", e.g. ockam identity rotate-key --node n1.
In response to issue: https://github.com/build-trust/ockam/issues/3685
This is a replacement for https://github.com/build-trust/ockam/pull/3841

Current Behavior
ockam identity rotate-key did not exists.
Proposed Changes
create cli command ockam identity rotate-key
Checks

[x] All commits in this Pull Request are signed and Verified by Github.
[x] All commits in this Pull Request follow the Ockam commit message convention.
[x] I accept the Ockam Community Code of Conduct.
[x] I have accepted the Ockam Contributor License Agreement by adding my Git/Github details in a row at the end of the CONTRIBUTORS.csv file in a separate pull request to the build-trust/ockam-contributors repository. The easiest way to do this is to edit the CONTRIBUTORS.csv file in the github web UI and create a PR, this will mark the commit as verified.

Hi @noyez! Do you need any help for completing this PR?

I think i need to pull in some code from master to get the tests passing. My dev machine is on the fritz and so i've been trying to get to get it to boot again.

Your work is much appreciated! Is there anything we can do to support you in completing this task?

@SanjoDeundiak what is the impact of the identity v2 work for this PR? Just a minor change to use a new API for identities?

source: gharchive/pull-request

authors: davide-baldo etorreborre noyez

repo: build-trust/ockam


text:
comments for AbortNode behaviour

fixes #6615. (Doesn't actually fix any thing)
Note: CI Tests do not need be run on this.

@SanjoDeundiak

@adiSuper94 yes, any objections?

I can clean up the comments a bit if you'd like.
Especially the numbers, I added the numbers just so that you get the order to read those comments. I am not sure they make sense in the larger code base though.

@SanjoDeundiak Made some edits, which might more value to future reader.

@adiSuper94 would you mind squashing the commits into one?

@adiSuper94 could you please check why your commit is unsigned?


text:
Listhubs Improvements

[ ] Implement form validation for controls
[ ] Link To Homepage at end of form input
[ ] Clear form state of user session

Minor issues to fix on v1 iteration:
-Allow freeform + additional amenities
https://www.figma.com/file/lSLF4RzNimKet5YrupZBht/dApp?node-id=290%3A2257
-Make first set of 3 rules default.  (If we want, we can have the person making the reservation check all three of the default rules before reserving)
-Availability section to just copy format from Calendly (see product_mvp channel)
-Minor spelling fixes:
"Air Conditioning"
"Equipped"

@angelo-build  do you think we need a name or title property on the hub model? I believe its a human friendly way of identifying hubs example "Beautiful 3 bedroom on the beach", a further description can be added in the description field to elaborate

Yes, We should allow them to give a title to the hub, great call.  For example the Idaho hub will be called "The Den" most likely so that should show up as the title of the hub

authors: angelo-build rollymaduk

repo: buildcities/product-mvp


text:
Get the storedProcedure or create it when it doesn't exist

This ensures we have the stored procedure within our cosmosDb

Oops... I wanted to publish this as a draft until I could verify it works, but here it is.

repo: builders-club/onlythemes


text:
Finish last a11y issues and add Travis CI execution

Describe the bug
There are 3 a11y issues remaining that need to be fixed related to the following :

text-input: Form elements must have labels.
ostentatious-copy: Elements that have scrollable content should be accessible by keyboard.
article: Aside (<aside>) must not be contained in another landmark.

In addition, to close the A11Y (for now), it is required to add the test to Travis CI.
To Reproduce
Steps to reproduce the behavior:

Go to /gravity-ui-nunjucks.
Run npm run test:a11y.
See the violation's list.

:tada: This issue has been resolved in version 3.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

authors: Elohina buildit-dev

repo: buildit/gravity-ui-web


text:
Containers on windows don't seem to be running commands

Heya, I'm trying to setup a pipeline to run inside windows containers, and am getting some unexpected results. As far as I can tell, the commands aren't ran at all.
I'm running the build agent on a Windows Server version 1803 Datacenter Core for Containers image on Google Container Engine, on which I installed Git for Windows, NSSM and the build agent, as per https://buildkite.com/docs/agent/v3/windows.
My pipeline.yml looks like this
steps:
  - label: windows-steps
    command: "echo hello"
    plugins:
      - docker#v2.0.0:
          image: "microsoft/dotnet:latest"
    agents:
      windows: true

And the output log looks like this:
Running plugin github.com/buildkite-plugins/docker-buildkite-plugin#v2.0.0 command hook
Running CMD.EXE /c 'echo hello' in microsoft/dotnet:latest | 2s
  | Microsoft Windows [Version 10.0.17134.345]
  | (c) 2018 Microsoft Corporation. All rights reserved.
  |
  | C:\workdir>> cd C:\buildkite-agent\builds\gce-buildkite-agent-windows-1-1\angular\testsetup\c\buildkite-agent\builds\gce-buildkite-agent-windows-1-1\angular\testsetup

I thought the command might be running but the output not shown, so I tried something that should error out (command: "not-a-binary"). The build still passed, same message, no error anywhere.

Heya 👋🏻Sorry you are running into issues, we've just started adding stronger support for Windows containers in the most recent version, so it's possible there are some bugs. I'll see if I can reproduce this!

The docker plugin uses git bash on windows, which uses msys2. msys2 will convert POSIX paths to Win32 paths: http://www.mingw.org/wiki/Posix_path_conversion
Thus /c becomes C:\.
This can be wholly disabled with the MSYS2_ARG_CONV_EXCL="*" variable.
PR submitted in https://github.com/buildkite-plugins/docker-buildkite-plugin/pull/82.
Below is the full investigation and how I got to this conclusion. It took a while.

I actually tried debugging it around a bit. In my buildkite agent folder I found the plugin folder and turned on the debug flag in hooks/command to debug_mode='on'.
This let me see the command that's being run:
Running CMD.EXE /c 'not-a-binary' in microsoft/dotnet:latest | 2s
-- | --
  | $ docker run -i --rm --volume C:\buildkite-agent\builds\RED-X1C6-1\angular\testsetup:C:\workdir --workdir C:\workdir microsoft/dotnet:latest CMD.EXE /c not-a-binary
  | Microsoft Windows [Version 10.0.17134.345]
  | (c) 2018 Microsoft Corporation. All rights reserved.
  |
  | C:\workdir>> cd C:\buildkite-agent\builds\RED-X1C6-1\angular\testsetup\c\buildkite-agent\builds\RED-X1C6-1\angular\testsetup

So I tried to run that command locally in docker with windows containers, and got the same result. Which is nice enough because it seems to mean that it's a usage issue.
kamik@RED-X1C6 MINGW64 /c/buildkite-agent/plugins/github-com-buildkite-plugins-docker-buildkite-plugin-v2-0-0 ((v2.0.0))
$ docker run -i --rm --volume "C:\buildkite-agent\builds\RED-X1C6-1\angular\testsetup:C:\workdir" --workdir "C:\workdir" microsoft/dotnet:latest CMD.EXE /c not-a-binary
Microsoft Windows [Version 10.0.17134.345]
(c) 2018 Microsoft Corporation. All rights reserved.

C:\workdir>

For the sake of debugging I removed the volume mount and workdir, so I'm testing with just docker run -i --rm microsoft/dotnet:latest CMD.EXE /c not-a-binary.
I don't quite get why -i is used, but it's used in both linux and windows so I assume it's there because it works. Indeed running a similar command on linux containers works as expected:
$ docker run -i --rm circleci/node:10.9.0 bash "-e" "-c" dir
bin   dev  home  lib64  mnt  proc  run   srv  tmp  var
boot  etc  lib   media  opt  root  sbin  sys  usr

$ docker run -i --rm circleci/node:10.9.0 bash "-e" "-c" not-a-binary
bash: not-a-binary: command not found

If I try the same thing with a windows container, it just hangs at the prompt and I have to ctrl+c to exit:
$ docker run -i --rm microsoft/dotnet:latest CMD.EXE /c dir
Microsoft Windows [Version 10.0.17134.345]
(c) 2018 Microsoft Corporation. All rights reserved.

C:\>
# ctrl+c

$ docker run -i --rm microsoft/dotnet:latest CMD.EXE /c not-a-binary
Microsoft Windows [Version 10.0.17134.345]
(c) 2018 Microsoft Corporation. All rights reserved.

C:\>
# ctrl+c

However, if I try it directly in my windows machine, without docker, these commands do what's expected:
C:\>cmd.exe /c dir
 Volume in drive C is RED-15
 Volume Serial Number is B633-9AD8

 Directory of C:\

13/11/2018  09:10    <DIR>          buildkite-agent
10/05/2018  09:20    <DIR>          cygwin64
29/04/2018  16:11    <DIR>          DRIVERS
13/06/2018  10:35    <DIR>          Intel
03/09/2018  12:29    <DIR>          msys64
11/04/2018  23:38    <DIR>          PerfLogs
13/11/2018  09:12    <DIR>          Program Files
31/10/2018  13:26    <DIR>          Program Files (x86)
24/09/2018  13:29    <DIR>          Python27
29/03/2018  16:03    <DIR>          Temp
01/05/2018  14:55    <DIR>          Users
01/11/2018  10:54    <DIR>          Windows
               0 File(s)              0 bytes
              12 Dir(s)  65,283,862,528 bytes free

C:\>cmd.exe /c not-a-binary
'not-a-binary' is not recognized as an internal or external command,
operable program or batch file.

I don't know why running it in docker behaves differently. There seems to be a similar issue in stack overflow though: https://stackoverflow.com/questions/42829450/docker-windows-containers-cmd-command-not-running
I tried to go back to the absolute basics and found https://docs.microsoft.com/en-us/virtualization/windowscontainers/quick-start/quick-start-windows-10, where they list a couple of very basic commands that should work in poweshell, which I can verify:
$ docker run -i microsoft/nanoserver powershell -Command dir

    Directory: C:\

Mode                LastWriteTime         Length Name
----                -------------         ------ ----
d-----       11/13/2018  10:39 AM                Program Files
d-----        7/16/2016   1:09 PM                Program Files (x86)
d-r---        10/6/2018   9:32 PM                Users
d-----       11/13/2018  10:39 AM                Windows
-a----       11/20/2016  11:32 AM           1894 License.txt

$ docker run -i microsoft/nanoserver powershell -Command not-a-binary
not-a-binary : The term 'not-a-binary' is not recognized as the name of a
cmdlet, function, script file, or operable program. Check the spelling of the
name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ not-a-binary
+ ~~~~~~~~~~~~
    + CategoryInfo          : ObjectNotFound: (not-a-binary:String) [], Comman
   dNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException

The equivalent using cmd doesn't really seem to work:
$ docker run -i microsoft/nanoserver cmd /c dir
Microsoft Windows [Version 10.0.14393]
(c) 2016 Microsoft Corporation. All rights reserved.

C:\>
# ctrl+c
$ docker run -i microsoft/nanoserver cmd /c not-a-binary
Microsoft Windows [Version 10.0.14393]
(c) 2016 Microsoft Corporation. All rights reserved.

C:\>
# ctrl+c

So maybe it's a problem with running cmd directly.
According to https://hub.docker.com/r/microsoft/nanoserver/, support requests should be filed in https://social.msdn.microsoft.com/Forums/en-US/home?forum=windowscontainers so I was about to file one there.
But then I noticed I was running all my repro docker commands without --rm. So I went to see how many zillion containers I had accumulated:
$ docker ps -a
CONTAINER ID        IMAGE                  COMMAND                  CREATED              STATUS                      PORTS               NAMES
479b833b60ed        microsoft/nanoserver   "powershell.exe -Com…"   44 seconds ago       Exited (0) 32 seconds ago                       peaceful_lalande
b5ce797ebbc1        microsoft/nanoserver   "powershell.exe -Com…"   About a minute ago   Exited (1) 49 seconds ago                       romantic_newton
3440a593d7cb        microsoft/nanoserver   "cmd.exe C:/ dir"        2 minutes ago        Exited (0) 2 minutes ago                        laughing_banach
42eeda283b78        microsoft/nanoserver   "cmd.exe C:/ not-a-b…"   3 minutes ago        Exited (0) 2 minutes ago                        epic_mcnulty
1adfe7861db8        microsoft/nanoserver   "cmd C:/ not-a-binary"   6 minutes ago        Exited (0) 5 minutes ago                        nifty_jones
c623e37de748        microsoft/nanoserver   "cmd C:/ not-a-binary"   12 minutes ago       Exited (0) 12 minutes ago                       tender_joliot
a1e060366654        microsoft/nanoserver   "cmd C:/ not-a-binary"   13 minutes ago       Exited (0) 13 minutes ago                       infallible_swartz
2801423e2336        microsoft/nanoserver   "cmd C:/ dir"            13 minutes ago       Exited (0) 13 minutes ago                       peaceful_mahavira
1b8797e5c12b        microsoft/nanoserver   "cmd C:/ dir"            14 minutes ago       Exited (0) 14 minutes ago                       upbeat_boyd
bfdb78abf8e3        microsoft/nanoserver   "powershell -Command…"   15 minutes ago       Exited (1) 14 minutes ago                       amazing_murdock
a06eeb3877f6        microsoft/nanoserver   "powershell -Command…"   16 minutes ago       Exited (0) 16 minutes ago                       sharp_poincare
ce213765011a        microsoft/nanoserver   "-i powershell -Comm…"   16 minutes ago       Created                                         ecstatic_bhaskara
1107be221eb8        microsoft/nanoserver   "powershell -Command…"   17 minutes ago       Exited (0) 16 minutes ago                       vigilant_bardeen
5b041d37d52a        microsoft/nanoserver   "powerhsell -Command…"   17 minutes ago       Created                                         clever_proskuriakova
70028610bcd5        microsoft/nanoserver   "cmd C:/ dir"            19 minutes ago       Exited (0) 18 minutes ago                       friendly_ride
1a2172c1dbf4        microsoft/nanoserver   "cmd C:/ dir"            19 minutes ago       Exited (0) 19 minutes ago                       condescending_neumann
5ffef025c550        microsoft/nanoserver   "cmd dir"                19 minutes ago       Exited (0) 19 minutes ago                       affectionate_swartz
8b167a6f2cc2        microsoft/nanoserver   "cmd"                    19 minutes ago       Exited (0) 19 minutes ago                       hardcore_easley

...and noticed the very curious "cmd C:/ dir"  command.
I'm familiar with the problem from the main repo that I work on: https://github.com/angular/angular-cli/issues/5606.
The buildkite docker plugin uses gitbash to run commands, and when gitbash sees /something it will convert the path. So /c becomes C:/. Details can be found in http://www.mingw.org/wiki/Posix_path_conversion.
I was doing all my testing inside gitbash, so I went to try in plan cmd on my machine and it does work:
C:\> docker run --rm microsoft/nanoserver cmd.exe /c dir
 Volume in drive C has no label.
 Volume Serial Number is 8E9A-67D4

 Directory of C:\

11/20/2016  11:32 AM             1,894 License.txt
07/16/2016  12:20 PM    <DIR>          Program Files
07/16/2016  12:09 PM    <DIR>          Program Files (x86)
10/06/2018  08:32 PM    <DIR>          Users
11/13/2018  10:58 AM    <DIR>          Windows
               1 File(s)          1,894 bytes
               4 Dir(s)  21,205,905,408 bytes free

So drawing inspiration from the solutions in https://github.com/angular/angular-cli/issues/5606, there are a couple of possible approaches.
Using //c instead (docker run --rm microsoft/nanoserver cmd.exe //c dir) works but what about if the user commands also use /something?
Using MSYS2_ARG_CONV_EXCL seems a better approach, and is detailed in https://github.com/Alexpux/MSYS2-packages/issues/84. It seems to support * as a catch all, and since I don't think we want any paths being converted at all, that seems ideal.
Indeed this works:
$ MSYS2_ARG_CONV_EXCL="*" docker run --rm microsoft/nanoserver cmd.exe /c dir
 Volume in drive C has no label.
 Volume Serial Number is 8E9A-67D4

 Directory of C:\

11/20/2016  11:32 AM             1,894 License.txt
07/16/2016  12:20 PM    <DIR>          Program Files
07/16/2016  12:09 PM    <DIR>          Program Files (x86)
10/06/2018  08:32 PM    <DIR>          Users
11/13/2018  11:14 AM    <DIR>          Windows
               1 File(s)          1,894 bytes
               4 Dir(s)  21,215,952,896 bytes free

Indeed this makes it work:

Running CMD.EXE /c 'not-a-binary' in microsoft/dotnet:latest | 3s
-- | --
  | $ docker run -i --rm --volume C:\buildkite-agent\builds\RED-X1C6-1\angular\testsetup:C:\workdir --workdir C:\workdir microsoft/dotnet:latest CMD.EXE /c not-a-binary
  | 'not-a-binary' is not recognized as an internal or external command,
  | operable program or batch file.

Will submit a PR.

It's worth mentioning that even with https://github.com/buildkite-plugins/docker-buildkite-plugin/pull/82, multiple commands don't seem to run properly.
Using the config:
steps:
  - label: windows-steps
    command:
      - "dir"
      - "not-a-binary"
    plugins:
      - docker#v2.0.0:
          image: "microsoft/dotnet:latest"
    agents:
      windows: true

The build logs this:

Running CMD.EXE /c 'dir | 3s
-- | --
  | not-a-binary' in microsoft/dotnet:latest
  | $ docker run -i --rm --volume C:\buildkite-agent\builds\RED-X1C6-1\angular\testsetup:C:\workdir --workdir C:\workdir microsoft/dotnet:latest CMD.EXE /c dir
  | not-a-binary
  | Volume in drive C has no label.
  | Volume Serial Number is 125C-63E0
  |
  | Directory of C:\workdir
  |
  | 11/13/2018  09:11 AM    <DIR>          .
  | 11/13/2018  09:11 AM    <DIR>          ..
  | 11/13/2018  09:11 AM               837 .bazelrc
  | 11/13/2018  11:58 AM    <DIR>          .buildkite
  | 11/13/2018  09:11 AM    <DIR>          .circleci
  | 11/13/2018  09:11 AM                73 .clang-format
  | 11/13/2018  09:11 AM                28 .gitignore
  | 11/13/2018  09:11 AM               324 BUILD.bazel
  | 11/13/2018  09:11 AM    <DIR>          e2e
  | 11/13/2018  09:11 AM            22,160 graph.png
  | 11/13/2018  09:11 AM             1,096 LICENSE
  | 11/13/2018  09:11 AM             1,621 package.json
  | 11/13/2018  09:11 AM             1,147 postinstall.tsconfig.json
  | 11/13/2018  09:11 AM             4,007 README.md
  | 11/13/2018  09:11 AM                41 renovate.json
  | 11/13/2018  09:11 AM    <DIR>          src
  | 11/13/2018  09:11 AM             3,425 WORKSPACE
  | 11/13/2018  09:11 AM           177,598 yarn.lock
  | 12 File(s)        212,357 bytes
  | 6 Dir(s)  62,776,291,328 bytes free
  | > cd C:\buildkite-agent\builds\RED-X1C6-1\angular\testsetup\c\buildkite-agent\builds\RED-X1C6-1\angular\testsetup
  | # MSYS2_ARG_CONV_EXCL changed

The dir runs, but the not-a-binary (which should fail) doesn't seem to run.

@lox heya 👋
Have you had time to look at https://github.com/buildkite-plugins/docker-buildkite-plugin/pull/82? I just added a fix for multiple commands on windows too.
I'm a bit worried about the command syntax being a bit brittle like... Have you considered starting a container, then running each command individually inside it? The container would have to be removed when running the last command though.

Just trying to get my windows environment working again today! 😓

Awesome, thank you!
Have you thought about the "running commands individually" idea? To be honest I can't think of a scenario offhand where the current setup would break. Probably something with newlines? It's hard to follow the logs though, when all pipeline commands are ran in a single line.
Under this setup what would happen with docker is:
docker start org/container:latest
# retrieve the containerid somehow
docker run containerid cmd.exe /C command 1
docker run containerid cmd.exe /C command 2
docker run containerid cmd.exe /C command 3
docker container rm containerid

Same on linux, just with bash instead of cmd.
I don't think changing this is very important right now but might be relevant if the current one lines breaks with some commands.

We tend to think of command parameters as shell scripts. It's pretty intrinsic in that contract that they are executed within the same shell context I think. If you created a different container for each it would break things like:
cd dir/
./run_script.sh
chmod +x my_file
``

It would be theoretically possible to use `docker exec` to run commands within a container, but you'd still lose shell context. Given your change with `&&` between commands, would there be an upsides to the proposed container-per-command approach?

In that setup they are actually executed in the same container.
The container keeps running in the background and is only stopped on container stop containerid.
Here's a demo, with the actual commands. The commands I listed before did not work.
D:\work\angular>docker run -d -it microsoft/nanoserver:1803
3ab21937d628bcf3e4dc4bd41d4dff7a72501e2f55e8771d1c7e75009baaed5c

D:\work\angular>docker container ls
CONTAINER ID        IMAGE                                  COMMAND                    CREATED             STATUS              PORTS               NAMES
3ab21937d628        microsoft/nanoserver:1803              "c:\\windows\\system32…"   14 seconds ago      Up 10 seconds                           keen_stallman
b8d257b2bee2        filipesilva/node-bazel-windows:0.0.2   "cmd /c 'cmd /C C:\\\\…"   20 hours ago        Up 20 hours                             hopeful_ganguly

D:\work\angular>docker exec 3ab21937d628 cmd /c echo hello
hello

D:\work\angular>docker exec 3ab21937d628 cmd /c mkdir persistentDir

D:\work\angular>docker exec 3ab21937d628 cmd /c dir
 Volume in drive C has no label.
 Volume Serial Number is 125C-63E0

 Directory of C:\

04/11/2018  11:53 PM             1,894 License.txt
11/23/2018  04:58 PM    <DIR>          persistentDir
11/23/2018  04:54 PM    <DIR>          Users
11/23/2018  04:54 PM    <DIR>          Windows
               1 File(s)          1,894 bytes
               3 Dir(s)  21,243,764,736 bytes free

D:\work\angular>docker stop 3ab21937d628
3ab21937d628

D:\work\angular>docker container ls
CONTAINER ID        IMAGE                                  COMMAND                    CREATED             STATUS              PORTS               NAMES
b8d257b2bee2        filipesilva/node-bazel-windows:0.0.2   "cmd /c 'cmd /C C:\\\\…"   20 hours ago        Up 20 hours                             hopeful_ganguly

In the example above I made a directory in one docker exec command and it was still there on the other.

Ah right, yes you are correct. I missed the lack of --rm!
You'd still miss out on the actual CMD.EXE shell context though.

Ah jeez, I missed your comment about exec and the shell context! Yes that would be lost...
At the moment I don't have a real upside besides the readable logs.
If I find a limitation with the current approach I'll look at this proposal again.

Sounds good, thanks so much for the PR! Let us know if you run into any other issues!

Btw, the other approach that we used historically was to generate a batch script that would execute things with the semantics you'd expect.
https://github.com/buildkite/agent/blob/5bdad78c5e7c75ca4487197a3f84537445d0bccf/bootstrap/hook.go#L97-L108
We still use that in the agent, it's just awkward to use with docker as you've got to get the generated script into the container.

authors: filipesilva lox


text:
bootstrap.sh should check out submodules by default

basically
buildbox-run "git checkout -qf \"$BUILDBOX_COMMIT\""
buildbox-run "git submodule update --init"

@ahawkins are you doing a git submodule update --init in your bootstrap.sh file?

I've added it to our bootstrap.sh for the upcoming 1.0 release of the agents: https://github.com/buildkite/agent/blob/master/templates/bootstrap.sh#L107

If you'd like similar behaviour now, just copy those 3 lines into your current bootstrap.sh
Thanks everyone for your help!! :dancers:

Sorry to comment on a closed issue, but would it be possible to disable the git submodule calls with a buildkite configuration setting or an environment variable?
This would be useful for minimal agents without perl installed (git submodules require perl).
Tasks on an agent without perl don't break, but they still display error messages like this:
/usr/libexec/git-core/git-submodule: line 1: /usr/bin/perl: not found

Currently I'm disabling git submodule calls with the following command, but that's rather brittle:
sed -i 's/\(git submodule\)/true \1/g' /buildkite/bootstrap.sh

@blueimp can you give the bootstrap from #168 a go? I've added a BUILDKITE_DISABLE_GIT_SUBMODULES environment variable for disabling the git submodule checkout commands.

Thanks, I've added my comment to #168

authors: MSch blueimp keithpitt toolmantim

repo: buildkite/agent


text:
Add submodule remotes to known_hosts

Add submodule remotes to known_hosts as part of the checkout process.
Fix for #503

More comments added @keithpitt!


text:
Add settings conveniences for Markdown

This PR is a bit speculative. Feel free to reject some or all of this!
The Markdown files in this repo are *.md.erb. In normal operation, neither GitHub nor VSCode recognize these as Markdown. This PR sets configuration to override ~both~ one of them. That is to say, this PR:

Supplies a VSCode workspace settings file with files.associations set for the Markdown files.
~Adds a .gitattributes file with github-linguist directives to do a similar thing to GitHub.~

~The latter change is hard to demonstrate and verify ahead of time. Right now, we don't get GitHub's rich diffs and the like for Markdown files. This is supposed to fix that, but it looks kinda… off on my branch, but perhaps that's because rendering is a very low priority background job. If it remains busted a few hours after merging, then we'll have to revert it. (And, though it should go without saying, if you don't like the rich previews then we shouldn't do it.)~

Not something to be deployed on a Friday :D

The rich preview is still busted. Shall we remove that?
I can't see any downsides to the vscode thing though. Does it load automatically?

I can't see any downsides to the vscode thing though. Does it load automatically?

That's right. The only problem this might pose is if someone already has a settings file (or wants to extend it and finds Git's tracking a nuisance). There are ways of dealing with that (e.g., a command to generate the settings file, only if it doesn't exist). But odds are… we ain't gonna need it.
I rolled back the attributes change. No rich diffs for now.

authors: ddbeck karensawrey plaindocs

repo: buildkite/docs


text:
Linux installed without my consent

Thanks for the debloater, but now I have Linux listed in File Explorer.

When trying to open Properties to see details on it, I get an error "The properties for this item are not available".

I did not consent to this.  So...  a debloater added bloat to my PC?
How do I remove the whatever iteration of Linux installed from running BloatyNosy?  It is not listed in partitions.  It is not listed in hardware devices.  It is not listed in installed programs.  It is not listed in Features.  There doesn't seem to be a simple way to remove what I didn't ask for.
(yes...  I created an account JUST to complain about this...)

You've enabled "Microsoft Windows Subsystem for Linux" feature in BloatyNosy. Many find it useful, which is why it has made its way into BloatyNosy. You can easily disable it by checking the box next to "Feature Recommendation" and then restoring the default settings (button with downward arrow next to the analysis button).

That...  worked?
I think it worked.  But I had restored defaults...  so I rebloated Windows?
Anyhow...  the Linux drive/folder/subsystem//icon/whatever is gone.  Luckily, this PC isn't important enough to bother further.
I recommend streamlining the GUI so it's simple to follow.  Having a feature listed at the bottom of a list (accessible via a small-print link-type sentence at the bottom of an oversized window with too much blank space) and describing the feature as to making a user unsure if I should check or uncheck the box to activate or deactivate the feature makes it confusing.
This is one of the reasons I regularly have trouble with open-source software and the like.  I enjoy them, but I have to filter through lots of badly interfaced choices until I find a good one.
Thanks, though!!!

@Belim, why is WSL considered part of debloating, and why can't it be toggled off so it doesn't have to be manually turned off after 'fix'-ing?

authors: Belim TempAccountToComplain realies

repo: builtbybel/BloatyNosy


text:
🛑 VODA-SA is down

In 9a5cc58, VODA-SA ($SECRET_SITE2) was down:

HTTP code: 403
Response time: 1114 ms

Resolved: VODA-SA is back up in 4396b42.

repo: buluma/uptime


text:
🛑 TowerCO is down

In dacddbb, TowerCO ($TOWERCO) was down:

HTTP code: 0
Response time: 0 ms

Resolved: TowerCO is back up in 6b04bcd after 1 hour, 14 minutes.


text:
Running bundle pack can cause "undefined method source_uri"

Here's the backtrace:
$ bundle pack
Unfortunately, a fatal error has occurred. Please see the Bundler troubleshooting documentation at http://bit.ly/bundler-issues. Thanks!
/Users/andre/src/bundler/bundler/lib/bundler/source/rubygems.rb:332:in `fetch_gem': undefined method `source_uri' for nil:NilClass (NoMethodError)
        from /Users/andre/src/bundler/bundler/lib/bundler/source/rubygems.rb:162:in `cached_built_in_gem'
        from /Users/andre/src/bundler/bundler/lib/bundler/source/rubygems.rb:148:in `cache'
        from /Users/andre/src/bundler/bundler/lib/bundler/runtime.rb:114:in `block in cache'
        from /Users/andre/src/bundler/bundler/lib/bundler/runtime.rb:112:in `cache'
        from /Users/andre/src/bundler/bundler/lib/bundler/cli/install.rb:79:in `run'
        from /Users/andre/src/bundler/bundler/lib/bundler/cli/package.rb:23:in `install'
        from /Users/andre/src/bundler/bundler/lib/bundler/cli/package.rb:13:in `run'
        from /Users/andre/src/bundler/bundler/lib/bundler/cli.rb:238:in `package'
        from /Users/andre/src/bundler/bundler/lib/bundler/vendor/thor/command.rb:27:in `run'
        from /Users/andre/src/bundler/bundler/lib/bundler/vendor/thor/invocation.rb:121:in `invoke_command'
        from /Users/andre/src/bundler/bundler/lib/bundler/vendor/thor.rb:363:in `dispatch'
        from /Users/andre/src/bundler/bundler/lib/bundler/vendor/thor/base.rb:440:in `start'
        from /Users/andre/src/bundler/bundler/lib/bundler/cli.rb:9:in `start'
        from /Users/andre/src/bundler/bundler/bin/bundle:20:in `block in <main>'
        from /Users/andre/src/bundler/bundler/lib/bundler/friendly_errors.rb:5:in `with_friendly_errors'
        from /Users/andre/src/bundler/bundler/bin/bundle:18:in `<main>'

I've gisted the output from bundle env here: https://gist.github.com/indirect/c6a472dad35636f58eb4

I was also receiving this error - in my case the context appears to be related to gemfury. I can't submit bundle env, since it has credentials in it.
Fetching gem metadata from https://gem.fury.io/emcien/...
Fetching additional metadata from https://gem.fury.io/emcien/..
Unfortunately, a fatal error has occurred. Please see the Bundler troubleshooting documentation at http://bit.ly/bundler-issues. Thanks!

The exception was raising out of cached_built_in_gem - remote_specs.search(spec) is returning an empty list.
Updating bundler from 1.7.12 -> 1.8.2 completely fixed the problem for me.

Thanks for letting us know, @nevinera!
I'll close this issue, then. If anyone else still gets this under 1.8.x+, please comment here with details (you can replace any private details in bundler env output with dummy credentials).

hi, i met the same problem:
☁  baozheng [master]  bundle package --all
Using rake 10.4.2
Using i18n 0.7.0
Using json 1.8.2
Using minitest 5.5.1
Using thread_safe 0.3.4
Using tzinfo 1.2.2
Using activesupport 4.2.0
Using builder 3.2.2
Using erubis 2.7.0
Using mini_portile 0.6.2
Using nokogiri 1.6.5
Using rails-deprecated_sanitizer 1.0.3
Using rails-dom-testing 1.0.5
Using loofah 2.0.1
Using rails-html-sanitizer 1.0.1
Using actionview 4.2.0
Using rack 1.6.0
Using rack-test 0.6.3
Using actionpack 4.2.0
Using globalid 0.3.0
Using activejob 4.2.0
Using mime-types 1.25.1
Using mail 2.6.3
Using actionmailer 4.2.0
Using activemodel 4.2.0
Using arel 6.0.0
Using activerecord 4.2.0
Using acts-as-taggable-on 3.4.3
Using addressable 2.3.6
Using angularjs-rails-resource 1.1.1
Using execjs 2.2.2
Using autoprefixer-rails 5.0.0
Using awesome_nested_set 3.0.2
Using awesome_print 1.6.1
Using descendants_tracker 0.0.4
Using ice_nine 0.11.1
Using axiom-types 0.1.1
Using bcrypt 3.1.9
Using coderay 1.1.0
Using better_errors 2.1.1
Using thor 0.19.1
Using railties 4.2.0
Using momentjs-rails 2.9.0
Using bootstrap3-datetimepicker-rails 3.1.3
Using bootstrap_flash_messages 1.0.0
Using browser 0.8.0
Using cancancan 1.10.1
Using colorize 0.7.5
Using net-ssh 2.9.2
Using net-scp 1.2.1
Using sshkit 1.6.1
Using capistrano 3.1.0
Using capistrano-bundler 1.1.3
Using capistrano-rails 1.1.2
Using capistrano-rvm 0.1.2 from git://github.com/capistrano/rvm.git (at master)
Using hitimes 1.2.2
Using timers 4.0.1
Using celluloid 0.16.0
Using chronic 0.10.2
Using climate_control 0.0.3
Using cocaine 0.5.5
Using coercible 1.0.0
Using coffee-script-source 1.8.0
Using coffee-script 2.3.0
Using coffee-rails 4.1.0
Using commonjs 0.2.7
Using daemons 1.1.9
Using delayed_job 4.0.6
Using delayed_job_active_record 4.0.3
Using orm_adapter 0.5.0
Using responders 2.0.2
Using warden 1.2.3
Using devise 3.4.1
Using devise-async 0.9.0
Using diff-lcs 1.2.5
Using diffy 3.0.7
Using doorkeeper 1.4.0
Using eventmachine 1.0.4
Using http_parser.rb 0.6.0
Using em-websocket 0.5.1
Using equalizer 0.0.9
Using faker 1.4.3
Using ffi 1.9.6
Using formatador 0.2.5
Using hashie 3.4.0
Using multi_json 1.10.1
Using multi_xml 0.5.5
Using rack-accept 0.4.5
Using rack-mount 0.8.3
Using virtus 1.0.4
Using grape 0.10.1
Using grape-doorkeeper 0.0.2
Using rabl 0.11.6
Using tilt 1.4.1
Using grape-rabl 0.3.0
Using rb-fsevent 0.9.4
Using rb-inotify 0.9.5
Using listen 2.8.5
Using lumberjack 1.0.9
Using nenv 0.2.0
Using shellany 0.0.1
Using notiffany 0.0.3
Using method_source 0.8.2
Using slop 3.6.0
Using pry 0.10.1
Using guard 2.11.1
Using guard-compat 1.2.1
Using guard-coffeescript 2.0.1
Using less 2.6.0
Using guard-less 2.0.0
Using guard-livereload 2.4.0
Using sass 3.4.9
Using guard-sass 1.6.0
Using hike 1.2.3
Using hirb 0.7.2
Using hpricot 0.8.6
Using html2slim 0.1.0
Using jbuilder 2.2.6
Using jquery-fileupload-rails 0.4.2
Using jquery-rails 4.0.3
Using launchy 2.4.3
Using less-rails 2.6.0
Using letter_opener 1.3.0
Using libv8 3.16.14.7
Using mysql2 0.3.17
Using nprogress-rails 0.1.6.5
Using oj 2.11.4
Using omniauth 1.2.2
Using paperclip 4.2.1
Using paranoia 2.0.4
Using polyamorous 1.1.0
Using pry-nav 0.2.4
Using pry-rails 0.3.2
Using pry-remote 0.1.8
Using quiet_assets 1.1.0
Using rack-utf8_sanitizer 1.2.4
Using bundler 1.8.5
Using sprockets 2.12.3
Using sprockets-rails 2.2.2
Using rails 4.2.0
Using rails-i18n 4.0.3
Using rails_config 0.4.2
Using rdoc 4.2.0
Using ref 1.0.5
Using uber 0.0.13
Using representable 2.1.4
Using roar 1.0.0
Using test_xml 0.1.7
Using roar-rails 1.0.1
Using rspec-support 3.0.4
Using rspec-core 3.0.4
Using rspec-expectations 3.0.4
Using rspec-mocks 3.0.4
Using rspec-rails 3.0.2
Using sass-rails 5.0.1
Using sdoc 0.4.1
Using select2-rails 3.5.9.1
Using simple_form 3.1.0
Using temple 0.7.5
Using slim 3.0.1
Using slim-rails 3.0.1
Using spring 1.2.0
Using squeel 1.2.2 from git://github.com/danielrhodes/squeel.git (at master)
Using therubyracer 0.12.1
Using thin 1.6.3
Using twitter-bootstrap-rails 3.1.1 from https://github.com/seyhunak/twitter-bootstrap-rails.git (at bootstrap3)
Using uglifier 2.7.0
Using whenever 0.9.4
Using zeroclipboard-rails 0.1.0
Updating files in vendor/cache
Fetching gem metadata from https://rails-assets.org/..
Fetching version metadata from https://rails-assets.org/.
――― ERROR REPORT TEMPLATE ―――――――――――――――――――――――――――――――――――――――――――――――――――――――
- What did you do?
- What did you expect to happen?
- What happened instead?

Error details

    NoMethodError: undefined method `source_uri' for nil:NilClass
    /Users/zuozuo/.rvm/gems/ruby-2.2.0@baozheng/gems/bundler-1.8.5/lib/bundler/source/rubygems.rb:359:in `fetch_gem'
    /Users/zuozuo/.rvm/gems/ruby-2.2.0@baozheng/gems/bundler-1.8.5/lib/bundler/source/rubygems.rb:168:in `cached_built_in_gem'
    /Users/zuozuo/.rvm/gems/ruby-2.2.0@baozheng/gems/bundler-1.8.5/lib/bundler/source/rubygems.rb:151:in `cache'
    /Users/zuozuo/.rvm/gems/ruby-2.2.0@baozheng/gems/bundler-1.8.5/lib/bundler/runtime.rb:116:in `block in cache'
    /Users/zuozuo/.rvm/gems/ruby-2.2.0@baozheng/gems/bundler-1.8.5/lib/bundler/runtime.rb:113:in `cache'
    /Users/zuozuo/.rvm/gems/ruby-2.2.0@baozheng/gems/bundler-1.8.5/lib/bundler/cli/install.rb:81:in `run'
    /Users/zuozuo/.rvm/gems/ruby-2.2.0@baozheng/gems/bundler-1.8.5/lib/bundler/cli/package.rb:32:in `install'
    /Users/zuozuo/.rvm/gems/ruby-2.2.0@baozheng/gems/bundler-1.8.5/lib/bundler/cli/package.rb:16:in `run'
    /Users/zuozuo/.rvm/gems/ruby-2.2.0@baozheng/gems/bundler-1.8.5/lib/bundler/cli.rb:258:in `package'
    /Users/zuozuo/.rvm/gems/ruby-2.2.0@baozheng/gems/bundler-1.8.5/lib/bundler/vendor/thor/command.rb:27:in `run'
    /Users/zuozuo/.rvm/gems/ruby-2.2.0@baozheng/gems/bundler-1.8.5/lib/bundler/vendor/thor/invocation.rb:121:in `invoke_command'
    /Users/zuozuo/.rvm/gems/ruby-2.2.0@baozheng/gems/bundler-1.8.5/lib/bundler/vendor/thor.rb:363:in `dispatch'
    /Users/zuozuo/.rvm/gems/ruby-2.2.0@baozheng/gems/bundler-1.8.5/lib/bundler/vendor/thor/base.rb:440:in `start'
    /Users/zuozuo/.rvm/gems/ruby-2.2.0@baozheng/gems/bundler-1.8.5/lib/bundler/cli.rb:10:in `start'
    /Users/zuozuo/.rvm/gems/ruby-2.2.0@baozheng/gems/bundler-1.8.5/bin/bundle:20:in `block in <top (required)>'
    /Users/zuozuo/.rvm/gems/ruby-2.2.0@baozheng/gems/bundler-1.8.5/lib/bundler/friendly_errors.rb:6:in `with_friendly_errors'
    /Users/zuozuo/.rvm/gems/ruby-2.2.0@baozheng/gems/bundler-1.8.5/bin/bundle:18:in `<top (required)>'
    /Users/zuozuo/.rvm/gems/ruby-2.2.0@baozheng/bin/bundle:23:in `load'
    /Users/zuozuo/.rvm/gems/ruby-2.2.0@baozheng/bin/bundle:23:in `<main>'
    /Users/zuozuo/.rvm/gems/ruby-2.2.0@baozheng/bin/ruby_executable_hooks:15:in `eval'
    /Users/zuozuo/.rvm/gems/ruby-2.2.0@baozheng/bin/ruby_executable_hooks:15:in `<main>'

Environment

    Bundler   1.8.5
    Rubygems  2.4.5
    Ruby      2.2.0p0 (2014-12-25 revision 49005) [x86_64-darwin14]
    GEM_HOME  /Users/zuozuo/.rvm/gems/ruby-2.2.0@baozheng
    GEM_PATH  /Users/zuozuo/.rvm/gems/ruby-2.2.0@baozheng:/Users/zuozuo/.rvm/gems/ruby-2.2.0@global
    RVM       1.26.10 (latest)
    Git       1.9.3 (Apple Git-50)
    rubygems-bundler (1.4.4)

Bundler settings

    cache_all
      Set for your local app (/Users/zuozuo/baozheng/.bundle/config): true
――― TEMPLATE END ――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――

Unfortunately, an unexpected error occurred, and Bundler cannot continue.

First, try this link to see if there are any existing issue reports for this error:
https://github.com/bundler/bundler/search?q=undefined+method+%60source_uri%27+for+nil%3ANilClass&type=Issues

If there aren't any reports for this error yet, please create copy and paste the report template above into a new issue. Don't forget to anonymize any private data! The new issue form is located at:
https://github.com/bundler/bundler/issues/new

Thanks, @iambaozheng!

Oddly, I saw this after adding sdoc to my Gemfile:
group :doc do
  # bundle exec rake doc:rails generates the API under doc/api.
  gem 'sdoc', require: false
end

Removing it resolved the problem. I then added it again, but without the group block and it worked just fine. I then added in the group block and it is still working. I have no idea why, but it seems to be resolved.
Just in case, here is my current bundle env, even though it's working:
Environment

    Bundler   1.8.5
    Rubygems  2.4.6
    Ruby      2.2.0p0 (2014-12-25 revision 49005) [x86_64-darwin14]
    GEM_HOME  /Users/ah/.rvm/gems/ruby-2.2.0@synchronicity
    GEM_PATH  /Users/ah/.rvm/gems/ruby-2.2.0@synchronicity:/Users/ah/.rvm/gems/ruby-2.2.0@global
    RVM       1.26.10 (latest)
    Git       2.3.1
    rubygems-bundler (1.4.4)

Bundler settings

    jobs
      Set for the current user (/Users/ah/.bundle/config): "4"

Gemfile

    source 'https://rubygems.org'

    # Rails and its supporting gems
    gem 'rails', '4.1.9'

    # Private gems (#mdtech represent!)
    source 'http://gems.moneydesktop.com' do
      gem 'active_remote-pagination'
      gem 'atlas'
      gem 'babou'
      gem 'buttress'
      gem 'lockout'
      gem 'md-default_categories'
      gem 'minimus'
    end

    # Public gems
    gem 'active_attr'
    gem 'active_remote'
    gem 'active_remote-cached'
    gem 'httpclient'
    gem 'redis-rails'
    gem 'progress_bar'
    gem 'protected_attributes'
    gem 'rabl'
    gem 'safe_yaml'
    gem 'sidekiq'
    gem 'strong_routes'
    gem 'will_paginate'
    gem 'zendesk_api'

    # JRuby-specific gems
    platforms :jruby do
      gem 'activerecord-jdbcpostgresql-adapter'
      gem 'json'
    end

    # MRI-specific gems
    platforms :ruby do
      gem 'pg'
      gem 'oj'
    end

    # Run it with Puma
    gem 'puma'

    # Deploy it with Trebuchet
    gem 'trebuchet', group: [:development]

    # So we have it when we need it
    gem 'pry', group: [:development, :test, :sandbox, :qa]

    # Test it with RSpec
    gem 'rspec-rails', group: [:development, :test]

    group :development do
      gem 'md-yard'
      gem 'rubocop', require: false
    end

    group :test do
      gem 'factory_girl_rails'
      gem 'nyan-cat-formatter'
      gem 'rspec-its'
      gem 'rspec-pride'
      gem 'rspec-rabl'
      gem 'shoulda'
      gem 'simplecov', require: false
      gem 'timecop'
    end

    group :doc do
      # bundle exec rake doc:rails generates the API under doc/api.
      gem 'sdoc', require: false
    end

Gemfile.lock

    GEM
      remote: https://rubygems.org/
      remote: http://gems.moneydesktop.com/
      specs:
        action_subscriber (1.0.4)
          activesupport (>= 3.2)
          bunny (>= 1.5.0)
          lifeguard
          middleware
        actionmailer (4.1.9)
          actionpack (= 4.1.9)
          actionview (= 4.1.9)
          mail (~> 2.5, >= 2.5.4)
        actionpack (4.1.9)
          actionview (= 4.1.9)
          activesupport (= 4.1.9)
          rack (~> 1.5.2)
          rack-test (~> 0.6.2)
        actionview (4.1.9)
          activesupport (= 4.1.9)
          builder (~> 3.1)
          erubis (~> 2.7.0)
        active_attr (0.8.5)
          activemodel (>= 3.0.2, < 5.0)
          activesupport (>= 3.0.2, < 5.0)
        active_remote (2.1.1)
          active_attr (>= 0.8)
          activesupport (>= 3.2)
          protobuf (>= 3.0)
        active_remote-cached (0.0.9)
          active_remote
          activesupport
        active_remote-pagination (2.0.0)
          active_remote (>= 2.1.0)
          concurrent-ruby
          will_paginate
        activemodel (4.1.9)
          activesupport (= 4.1.9)
          builder (~> 3.1)
        activerecord (4.1.9)
          activemodel (= 4.1.9)
          activesupport (= 4.1.9)
          arel (~> 5.0.0)
        activerecord-jdbc-adapter (1.3.15)
          activerecord (>= 2.2)
        activerecord-jdbcpostgresql-adapter (1.3.15)
          activerecord-jdbc-adapter (~> 1.3.15)
          jdbc-postgres (>= 9.1)
        activesupport (4.1.9)
          i18n (~> 0.6, >= 0.6.9)
          json (~> 1.7, >= 1.7.7)
          minitest (~> 5.1)
          thread_safe (~> 0.1)
          tzinfo (~> 1.1)
        algorithms (0.6.1)
        amq-protocol (1.9.2)
        arel (5.0.1.20140414130214)
        ast (2.0.0)
        astrolabe (1.3.0)
          parser (>= 2.2.0.pre.3, < 3.0)
        atlas (3.6.10)
          activesupport (>= 3.2)
          ffi-rzmq (>= 2.0)
          guid (>= 0.1.1)
          protobuf (>= 3.0)
        babou (1.0.3)
          action_subscriber (>= 1.0.2)
          activesupport (>= 3.2)
          thor (> 0.17)
        builder (3.2.2)
        bunny (1.7.0)
          amq-protocol (>= 1.9.2)
        buttress (2.15.2)
          activesupport (>= 3.2)
          atlas (>= 1.7.7)
          bunny (>= 1.5.0)
          heredity (>= 0.1.1)
          honeybadger (>= 1.11.0, < 2.0.0)
          ignorable (>= 0.2.0)
          lumberjack
          lumberjack_syslog_device
          progress_bar (>= 1.0.0)
          safe_yaml
          statsd-ruby
          sucker_punch (>= 1.0)
          thor (> 0.17)
        buttress (2.15.2-java)
          activesupport (>= 3.2)
          atlas (>= 1.7.7)
          heredity (>= 0.1.1)
          honeybadger (>= 1.11.0, < 2.0.0)
          ignorable (>= 0.2.0)
          lumberjack
          lumberjack_syslog_device
          march_hare (>= 2.7.0)
          progress_bar (>= 1.0.0)
          safe_yaml
          statsd-ruby
          sucker_punch (>= 1.0)
          thor (> 0.17)
        capistrano (2.15.5)
          highline
          net-scp (>= 1.0.0)
          net-sftp (>= 2.0.0)
          net-ssh (>= 2.0.14)
          net-ssh-gateway (>= 1.1.0)
        capistrano-deploytags (0.9.2)
          capistrano
          capistrano-ext
        capistrano-ext (1.2.1)
          capistrano (>= 1.0.0)
        capistrano_colors (0.5.5)
        celluloid (0.16.0)
          timers (~> 4.0.0)
        coderay (1.1.0)
        colored (1.2)
        concurrent-ruby (0.8.0)
          ref (~> 1.0, >= 1.0.5)
        connection_pool (2.1.2)
        diff-lcs (1.2.5)
        docile (1.1.5)
        erubis (2.7.0)
        factory_girl (4.5.0)
          activesupport (>= 3.0.0)
        factory_girl_rails (4.5.0)
          factory_girl (~> 4.5.0)
          railties (>= 3.0.0)
        faraday (0.9.1)
          multipart-post (>= 1.2, < 3)
        ffi (1.9.8)
        ffi (1.9.8-java)
        ffi-rzmq (2.0.4)
          ffi-rzmq-core (>= 1.0.1)
        ffi-rzmq-core (1.0.3)
          ffi (~> 1.9)
        firebolt (0.12.0)
          json
          rufus-scheduler (~> 3.0)
          sucker_punch (>= 1.0)
        guid (0.1.1)
        hashie (3.4.0)
        heredity (0.1.1)
        highline (1.6.21)
        hike (1.2.3)
        hitimes (1.2.2)
        hitimes (1.2.2-java)
        honeybadger (1.16.7)
          json
        httpclient (2.6.0.1)
        i18n (0.7.0)
        ignorable (0.2.0)
          activerecord (>= 3)
        inflection (1.0.0)
        jdbc-postgres (9.4.1200)
        json (1.8.2)
        json (1.8.2-java)
        lifeguard (0.0.8)
        lockout (2.5.2)
          actionpack
          active_remote
          activesupport
          atlas (> 1.0.0)
          buttress
          urlcrypt
          warden
        lumberjack (1.0.9)
        lumberjack_syslog_device (1.0.0)
          lumberjack (~> 1.0)
        mail (2.6.3)
          mime-types (>= 1.16, < 3)
        march_hare (2.8.0-java)
        md-default_categories (0.2.3)
          active_remote
          algorithms
          atlas
        md-yard (0.0.1)
          yard
        method_source (0.8.2)
        middleware (0.1.0)
        mime-types (2.4.3)
        minimus (0.3.2)
          activesupport
          atlas
          firebolt
          rack
        minitest (5.5.1)
        multi_json (1.11.0)
        multipart-post (2.0.0)
        net-scp (1.2.1)
          net-ssh (>= 2.6.5)
        net-sftp (2.1.2)
          net-ssh (>= 2.6.5)
        net-ssh (2.9.2)
        net-ssh-gateway (1.2.0)
          net-ssh (>= 2.6.5)
        nyan-cat-formatter (0.11)
          rspec (>= 2.99, >= 2.14.2, < 4)
        oj (2.12.1)
        options (2.3.2)
        parser (2.2.0.3)
          ast (>= 1.1, < 3.0)
        pg (0.18.1)
        powerpack (0.1.0)
        progress_bar (1.0.3)
          highline (~> 1.6.1)
          options (~> 2.3.0)
        protected_attributes (1.0.9)
          activemodel (>= 4.0.1, < 5.0)
        protobuf (3.4.4)
          activesupport (>= 3.2)
          middleware
          thor
          thread_safe
        pry (0.10.1)
          coderay (~> 1.1.0)
          method_source (~> 0.8.1)
          slop (~> 3.4)
        pry (0.10.1-java)
          coderay (~> 1.1.0)
          method_source (~> 0.8.1)
          slop (~> 3.4)
          spoon (~> 0.0)
        puma (2.11.1)
          rack (>= 1.1, < 2.0)
        puma (2.11.1-java)
          rack (>= 1.1, < 2.0)
        rabl (0.11.6)
          activesupport (>= 2.3.14)
        rack (1.5.2)
        rack-test (0.6.3)
          rack (>= 1.0)
        rails (4.1.9)
          actionmailer (= 4.1.9)
          actionpack (= 4.1.9)
          actionview (= 4.1.9)
          activemodel (= 4.1.9)
          activerecord (= 4.1.9)
          activesupport (= 4.1.9)
          bundler (>= 1.3.0, < 2.0)
          railties (= 4.1.9)
          sprockets-rails (~> 2.0)
        railties (4.1.9)
          actionpack (= 4.1.9)
          activesupport (= 4.1.9)
          rake (>= 0.8.7)
          thor (>= 0.18.1, < 2.0)
        rainbow (2.0.0)
        rake (10.4.2)
        rdoc (4.2.0)
        redis (3.2.1)
        redis-actionpack (4.0.0)
          actionpack (~> 4)
          redis-rack (~> 1.5.0)
          redis-store (~> 1.1.0)
        redis-activesupport (4.0.0)
          activesupport (~> 4)
          redis-store (~> 1.1.0)
        redis-namespace (1.5.1)
          redis (~> 3.0, >= 3.0.4)
        redis-rack (1.5.0)
          rack (~> 1.5)
          redis-store (~> 1.1.0)
        redis-rails (4.0.0)
          redis-actionpack (~> 4)
          redis-activesupport (~> 4)
          redis-store (~> 1.1.0)
        redis-store (1.1.4)
          redis (>= 2.2)
        ref (1.0.5)
        rspec (3.2.0)
          rspec-core (~> 3.2.0)
          rspec-expectations (~> 3.2.0)
          rspec-mocks (~> 3.2.0)
        rspec-core (3.2.2)
          rspec-support (~> 3.2.0)
        rspec-expectations (3.2.0)
          diff-lcs (>= 1.2.0, < 2.0)
          rspec-support (~> 3.2.0)
        rspec-its (1.2.0)
          rspec-core (>= 3.0.0)
          rspec-expectations (>= 3.0.0)
        rspec-mocks (3.2.1)
          diff-lcs (>= 1.2.0, < 2.0)
          rspec-support (~> 3.2.0)
        rspec-pride (3.1.0)
          rspec (~> 3.0)
        rspec-rabl (1.0.0)
          rabl (~> 0.9)
          rspec (~> 3.0)
        rspec-rails (3.2.1)
          actionpack (>= 3.0, < 4.3)
          activesupport (>= 3.0, < 4.3)
          railties (>= 3.0, < 4.3)
          rspec-core (~> 3.2.0)
          rspec-expectations (~> 3.2.0)
          rspec-mocks (~> 3.2.0)
          rspec-support (~> 3.2.0)
        rspec-support (3.2.2)
        rubocop (0.29.1)
          astrolabe (~> 1.3)
          parser (>= 2.2.0.1, < 3.0)
          powerpack (~> 0.1)
          rainbow (>= 1.99.1, < 3.0)
          ruby-progressbar (~> 1.4)
        ruby-progressbar (1.7.1)
        rufus-scheduler (3.0.9)
          tzinfo
        rvm-capistrano (1.5.6)
          capistrano (~> 2.15.4)
        safe_yaml (1.0.4)
        sdoc (0.4.1)
          json (~> 1.7, >= 1.7.7)
          rdoc (~> 4.0)
        shoulda (3.5.0)
          shoulda-context (~> 1.0, >= 1.0.1)
          shoulda-matchers (>= 1.4.1, < 3.0)
        shoulda-context (1.2.1)
        shoulda-matchers (2.8.0)
          activesupport (>= 3.0.0)
        sidekiq (3.3.2)
          celluloid (>= 0.16.0)
          connection_pool (>= 2.1.1)
          json
          redis (>= 3.0.6)
          redis-namespace (>= 1.3.1)
        simplecov (0.9.2)
          docile (~> 1.1.0)
          multi_json (~> 1.0)
          simplecov-html (~> 0.9.0)
        simplecov-html (0.9.0)
        slop (3.6.0)
        spoon (0.0.4)
          ffi
        sprockets (2.12.3)
          hike (~> 1.2)
          multi_json (~> 1.0)
          rack (~> 1.0)
          tilt (~> 1.1, != 1.3.0)
        sprockets-rails (2.2.4)
          actionpack (>= 3.0)
          activesupport (>= 3.0)
          sprockets (>= 2.8, < 4.0)
        statsd-ruby (1.2.1)
        steps (1.1.3)
          colored (>= 1.2)
          highline (>= 1.6)
        strong_routes (1.0.1)
          rack
        sucker_punch (1.4.0)
          celluloid (~> 0.16.0)
        thor (0.19.1)
        thread_safe (0.3.5)
        thread_safe (0.3.5-java)
        tilt (1.4.1)
        timecop (0.7.3)
        timers (4.0.1)
          hitimes
        trebuchet (4.3.1)
          activesupport (> 3.2)
          buttress (> 2.0)
          capistrano (~> 2)
          capistrano-deploytags (~> 0.9.2)
          capistrano_colors (> 0.5)
          httpclient
          rvm-capistrano (> 1.5)
          safe_yaml (> 1.0)
          steps (> 1.1)
          thor (> 0.17)
        tzinfo (1.2.2)
          thread_safe (~> 0.1)
        urlcrypt (0.1.1)
        warden (1.2.3)
          rack (>= 1.0)
        will_paginate (3.0.7)
        yard (0.8.7.6)
        zendesk_api (1.6.0)
          faraday (~> 0.9)
          hashie (>= 1.2, < 4.0)
          inflection
          mime-types
          multi_json
          multipart-post (~> 2.0)

    PLATFORMS
      java
      ruby

    DEPENDENCIES
      active_attr
      active_remote
      active_remote-cached
      active_remote-pagination!
      activerecord-jdbcpostgresql-adapter
      atlas!
      babou!
      buttress!
      factory_girl_rails
      httpclient
      json
      lockout!
      md-default_categories!
      md-yard
      minimus!
      nyan-cat-formatter
      oj
      pg
      progress_bar
      protected_attributes
      pry
      puma
      rabl
      rails (= 4.1.9)
      redis-rails
      rspec-its
      rspec-pride
      rspec-rabl
      rspec-rails
      rubocop
      safe_yaml
      sdoc
      shoulda
      sidekiq
      simplecov
      strong_routes
      timecop
      trebuchet
      will_paginate
      zendesk_api

@TimMoore @liveh2o
The problem has been solved by removing the block
source 'https://rails-assets.org' do
  gem 'rails-assets-angular'
end

And it behaved the same with @liveh2o's, when i remove this , it worked, and after that i add the rails-assets block back to my Gemfile and i still worked.

@TimMoore @liveh2o
The problem has been solved by removing the block
source 'https://rails-assets.org' do
  gem 'rails-assets-angular'
end

And it behaved the same with @liveh2o's, when i remove this , it worked, and after that i add the rails-assets block back to my Gemfile and i still worked.

sdoc was the issue for me. I am using source blocks like @iambaozheng mentions, but those don't seem to have caused any issues
Here is my bundle env
$ bundle env
Environment

    Bundler   1.9.2
    Rubygems  2.4.5
    Ruby      2.2.0p0 (2014-12-25 revision 49005) [x86_64-darwin14]
    GEM_HOME  /Users/michael.ries/.rvm/gems/ruby-2.2.0@bob
    GEM_PATH  /Users/michael.ries/.rvm/gems/ruby-2.2.0@bob:/Users/michael.ries/.rvm/gems/ruby-2.2.0@global
    RVM       1.26.10 (latest)
    Git       2.2.1
    rubygems-bundler (1.4.4)

Bundler settings

    gem.coc
      Set for the current user (/Users/michael.ries/.bundle/config): "false"
    gem.mit
      Set for the current user (/Users/michael.ries/.bundle/config): "true"
    gem.test
      Set for the current user (/Users/michael.ries/.bundle/config): "rspec"
    cache_all
      Set for your local app (/Users/michael.ries/deploys/bob/.bundle/config): "true"

Gemfile

    source 'https://rubygems.org'

    # Bundle edge Rails instead: gem 'rails', github: 'rails/rails'
    gem 'rails', '4.1.9'

    # Internal Gems
    source 'http://gems.moneydesktop.com' do
      gem 'buttress'
      gem 'josephus', '>= 0.3.0'
      gem 'trebuchet', require: false, group: [:development]
    end

    # Public Gems
    gem 'aws-sdk'
    gem 'jbuilder', '~> 2.0'
    gem 'jquery-rails'
    gem 'plist'
    gem 'puma'
    gem 'sass-rails', '~> 4.0.3'
    gem 'sidekiq'
    gem 'sidekiq-cron'
    gem 'sinatra' , '>= 1.3.0', :require => nil # Per https://github.com/mperham/sidekiq/wiki/Monitoring#rails-3-and-4
    gem 'turbolinks'
    gem 'uglifier', '>= 1.3.0'

    group :development, :test do
      gem 'brakeman', require: false
      gem 'pry'
    end

    group :test do
      gem 'rspec-rails', '>= 3.2.0'
      gem 'simplecov', '~> 0.7.1', :require => false
    end

    # MRI-specific gems
    platform :ruby do
      gem 'spring', :group => [:test, :development]
      gem 'therubyracer'
    end

    # JRuby-specific gems
    platform :jruby do
      gem 'jruby-openssl'
      gem 'therubyrhino', :group => :assetss
    end

Gemfile.lock

    GEM
      remote: https://rubygems.org/
      remote: http://gems.moneydesktop.com/
      specs:
        actionmailer (4.1.9)
          actionpack (= 4.1.9)
          actionview (= 4.1.9)
          mail (~> 2.5, >= 2.5.4)
        actionpack (4.1.9)
          actionview (= 4.1.9)
          activesupport (= 4.1.9)
          rack (~> 1.5.2)
          rack-test (~> 0.6.2)
        actionview (4.1.9)
          activesupport (= 4.1.9)
          builder (~> 3.1)
          erubis (~> 2.7.0)
        active_attr (0.8.5)
          activemodel (>= 3.0.2, < 5.0)
          activesupport (>= 3.0.2, < 5.0)
        active_remote (2.1.1)
          active_attr (>= 0.8)
          activesupport (>= 3.2)
          protobuf (>= 3.0)
        activemodel (4.1.9)
          activesupport (= 4.1.9)
          builder (~> 3.1)
        activerecord (4.1.9)
          activemodel (= 4.1.9)
          activesupport (= 4.1.9)
          arel (~> 5.0.0)
        activesupport (4.1.9)
          i18n (~> 0.6, >= 0.6.9)
          json (~> 1.7, >= 1.7.7)
          minitest (~> 5.1)
          thread_safe (~> 0.1)
          tzinfo (~> 1.1)
        amq-protocol (1.9.2)
        arel (5.0.1.20140414130214)
        atlas (3.8.1)
          activesupport (>= 3.2)
          ffi-rzmq (>= 2.0)
          guid (>= 0.1.1)
          protobuf (>= 3.0)
        aws-sdk (2.0.36)
          aws-sdk-resources (= 2.0.36)
        aws-sdk-core (2.0.36)
          builder (~> 3.0)
          jmespath (~> 1.0)
          multi_json (~> 1.0)
        aws-sdk-resources (2.0.36)
          aws-sdk-core (= 2.0.36)
        brakeman (3.0.2)
          erubis (~> 2.6)
          fastercsv (~> 1.5)
          haml (>= 3.0, < 5.0)
          highline (~> 1.6.20)
          multi_json (~> 1.2)
          ruby2ruby (~> 2.1.1)
          ruby_parser (~> 3.6.2)
          sass (~> 3.0)
          terminal-table (~> 1.4)
        builder (3.2.2)
        bunny (1.7.0)
          amq-protocol (>= 1.9.2)
        buttress (2.15.3)
          activesupport (>= 3.2)
          atlas (>= 1.7.7)
          bunny (>= 1.5.0)
          heredity (>= 0.1.1)
          honeybadger (>= 1.11.0, < 2.0.0)
          ignorable (>= 0.2.0)
          lumberjack
          lumberjack_syslog_device
          progress_bar (>= 1.0.0)
          safe_yaml
          statsd-ruby
          sucker_punch (>= 1.0)
          thor (> 0.17)
        capistrano (2.15.5)
          highline
          net-scp (>= 1.0.0)
          net-sftp (>= 2.0.0)
          net-ssh (>= 2.0.14)
          net-ssh-gateway (>= 1.1.0)
        capistrano-deploytags (0.9.2)
          capistrano
          capistrano-ext
        capistrano-ext (1.2.1)
          capistrano (>= 1.0.0)
        capistrano_colors (0.5.5)
        celluloid (0.16.0)
          timers (~> 4.0.0)
        coderay (1.1.0)
        coffee-rails (4.1.0)
          coffee-script (>= 2.2.0)
          railties (>= 4.0.0, < 5.0)
        coffee-script (2.4.1)
          coffee-script-source
          execjs
        coffee-script-source (1.9.1)
        colored (1.2)
        connection_pool (2.1.3)
        couchrest (1.2.0)
          mime-types (~> 1.15)
          multi_json (~> 1.0)
          rest-client (~> 1.6.1)
        couchrest_model (2.0.3)
          activemodel (>= 4.0, >= 3.0)
          couchrest (>= 1.2)
          mime-types (>= 1.16)
          tzinfo (>= 0.3.22)
        diff-lcs (1.2.5)
        erubis (2.7.0)
        execjs (2.5.0)
        fastercsv (1.5.5)
        felix (1.0.3)
          active_remote (>= 2.1.1)
          activesupport (>= 4.1, < 4.2)
          atlas (>= 3.7.3)
          plist (>= 3.0)
          thor (~> 0.18.1)
          xml-simple (>= 1.1.4)
        ffi (1.9.8)
        ffi-rzmq (2.0.4)
          ffi-rzmq-core (>= 1.0.1)
        ffi-rzmq-core (1.0.3)
          ffi (~> 1.9)
        guid (0.1.1)
        haml (4.0.6)
          tilt
        heredity (0.1.1)
        highline (1.6.21)
        hike (1.2.3)
        hitimes (1.2.2)
        honeybadger (1.16.7)
          json
        httpclient (2.6.0.1)
        i18n (0.7.0)
        ignorable (0.2.0)
          activerecord (>= 3)
        jbuilder (2.2.12)
          activesupport (>= 3.0.0, < 5)
          multi_json (~> 1.2)
        jmespath (1.0.2)
          multi_json (~> 1.0)
        josephus (0.4.0)
          couchrest_model (~> 2.0)
          felix (>= 0.5.3)
          sidekiq
          sidekiq-cron
          thor (~> 0.18.1)
        jquery-rails (3.1.2)
          railties (>= 3.0, < 5.0)
          thor (>= 0.14, < 2.0)
        json (1.8.2)
        libv8 (3.16.14.7)
        lumberjack (1.0.9)
        lumberjack_syslog_device (1.0.0)
          lumberjack (~> 1.0)
        mail (2.6.3)
          mime-types (>= 1.16, < 3)
        method_source (0.8.2)
        middleware (0.1.0)
        mime-types (1.25.1)
        minitest (5.5.1)
        multi_json (1.11.0)
        net-scp (1.2.1)
          net-ssh (>= 2.6.5)
        net-sftp (2.1.2)
          net-ssh (>= 2.6.5)
        net-ssh (2.9.2)
        net-ssh-gateway (1.2.0)
          net-ssh (>= 2.6.5)
        options (2.3.2)
        plist (3.1.0)
        progress_bar (1.0.3)
          highline (~> 1.6.1)
          options (~> 2.3.0)
        protobuf (3.4.4)
          activesupport (>= 3.2)
          middleware
          thor
          thread_safe
        pry (0.10.1)
          coderay (~> 1.1.0)
          method_source (~> 0.8.1)
          slop (~> 3.4)
        puma (2.11.1)
          rack (>= 1.1, < 2.0)
        rack (1.5.2)
        rack-protection (1.5.3)
          rack
        rack-test (0.6.3)
          rack (>= 1.0)
        rails (4.1.9)
          actionmailer (= 4.1.9)
          actionpack (= 4.1.9)
          actionview (= 4.1.9)
          activemodel (= 4.1.9)
          activerecord (= 4.1.9)
          activesupport (= 4.1.9)
          bundler (>= 1.3.0, < 2.0)
          railties (= 4.1.9)
          sprockets-rails (~> 2.0)
        railties (4.1.9)
          actionpack (= 4.1.9)
          activesupport (= 4.1.9)
          rake (>= 0.8.7)
          thor (>= 0.18.1, < 2.0)
        rake (10.4.2)
        rdoc (4.2.0)
        redis (3.2.1)
        redis-namespace (1.5.2)
          redis (~> 3.0, >= 3.0.4)
        ref (1.0.5)
        rest-client (1.6.8)
          mime-types (~> 1.16)
          rdoc (>= 2.4.2)
        rspec-core (3.2.3)
          rspec-support (~> 3.2.0)
        rspec-expectations (3.2.1)
          diff-lcs (>= 1.2.0, < 2.0)
          rspec-support (~> 3.2.0)
        rspec-mocks (3.2.1)
          diff-lcs (>= 1.2.0, < 2.0)
          rspec-support (~> 3.2.0)
        rspec-rails (3.2.1)
          actionpack (>= 3.0, < 4.3)
          activesupport (>= 3.0, < 4.3)
          railties (>= 3.0, < 4.3)
          rspec-core (~> 3.2.0)
          rspec-expectations (~> 3.2.0)
          rspec-mocks (~> 3.2.0)
          rspec-support (~> 3.2.0)
        rspec-support (3.2.2)
        ruby2ruby (2.1.3)
          ruby_parser (~> 3.1)
          sexp_processor (~> 4.0)
        ruby_parser (3.6.5)
          sexp_processor (~> 4.1)
        rufus-scheduler (3.0.9)
          tzinfo
        rvm-capistrano (1.5.6)
          capistrano (~> 2.15.4)
        safe_yaml (1.0.4)
        sass (3.2.19)
        sass-rails (4.0.4)
          railties (>= 4.0.0, < 5.0)
          sass (~> 3.2.2)
          sprockets (~> 2.8, < 2.12)
          sprockets-rails (~> 2.0)
        sexp_processor (4.5.0)
        sidekiq (3.3.3)
          celluloid (>= 0.16.0)
          connection_pool (>= 2.1.1)
          json
          redis (>= 3.0.6)
          redis-namespace (>= 1.3.1)
        sidekiq-cron (0.2.0)
          rufus-scheduler (>= 2.0.24)
          sidekiq (>= 2.17.3)
          tilt (< 2.0.0)
        simplecov (0.7.1)
          multi_json (~> 1.0)
          simplecov-html (~> 0.7.1)
        simplecov-html (0.7.1)
        sinatra (1.4.6)
          rack (~> 1.4)
          rack-protection (~> 1.4)
          tilt (>= 1.3, < 3)
        slop (3.6.0)
        spring (1.3.4)
        sprockets (2.11.3)
          hike (~> 1.2)
          multi_json (~> 1.0)
          rack (~> 1.0)
          tilt (~> 1.1, != 1.3.0)
        sprockets-rails (2.2.4)
          actionpack (>= 3.0)
          activesupport (>= 3.0)
          sprockets (>= 2.8, < 4.0)
        statsd-ruby (1.2.1)
        steps (1.1.3)
          colored (>= 1.2)
          highline (>= 1.6)
        sucker_punch (1.4.0)
          celluloid (~> 0.16.0)
        terminal-table (1.4.5)
        therubyracer (0.12.2)
          libv8 (~> 3.16.14.0)
          ref
        thor (0.18.1)
        thread_safe (0.3.5)
        tilt (1.4.1)
        timers (4.0.1)
          hitimes
        trebuchet (4.3.2)
          activesupport (> 3.2)
          buttress (> 2.0)
          capistrano (~> 2)
          capistrano-deploytags (~> 0.9.2)
          capistrano_colors (> 0.5)
          httpclient
          rvm-capistrano (> 1.5)
          safe_yaml (> 1.0)
          steps (> 1.1)
          thor (> 0.17)
        turbolinks (2.5.3)
          coffee-rails
        tzinfo (1.2.2)
          thread_safe (~> 0.1)
        uglifier (2.7.1)
          execjs (>= 0.3.0)
          json (>= 1.8.0)
        xml-simple (1.1.5)

    PLATFORMS
      ruby

    DEPENDENCIES
      aws-sdk
      brakeman
      buttress!
      jbuilder (~> 2.0)
      josephus (>= 0.3.0)!
      jquery-rails
      jruby-openssl
      plist
      pry
      puma
      rails (= 4.1.9)
      rspec-rails (>= 3.2.0)
      sass-rails (~> 4.0.3)
      sidekiq
      sidekiq-cron
      simplecov (~> 0.7.1)
      sinatra (>= 1.3.0)
      spring
      therubyracer
      therubyrhino
      trebuchet!
      turbolinks
      uglifier (>= 1.3.0)

+1 here. didn't find the reason it happens. Also using bundler pack.

+1 here. Mine's happening with bundle install
thomashowe:greenbot$ bundle env
Environment
Bundler   1.9.7
Rubygems  2.4.6
Ruby      2.2.0p0 (2014-12-25 revision 49005) [x86_64-darwin14]
GEM_HOME  /Users/thomashowe/.rvm/gems/ruby-2.2.0@kisst
GEM_PATH  /Users/thomashowe/.rvm/gems/ruby-2.2.0@kisst:/Users/thomashowe/.rvm/gems/ruby-2.2.0@global
RVM       1.26.11 (latest)
Git       2.3.2 (Apple Git-55)
rubygems-bundler (1.4.4)

Bundler settings
path
  Set for your local app (/Users/thomashowe/Documents/src/greenbot/.bundle/config): "vendor/cache"
disable_shared_gems
  Set for your local app (/Users/thomashowe/Documents/src/greenbot/.bundle/config): "1"
clean
  Set for your local app (/Users/thomashowe/Documents/src/greenbot/.bundle/config): "true"

Gemfile
source 'https://rubygems.org'

gem 'airbrake'
gem 'awesome_print'
gem 'bigdecimal'
gem 'builder'
gem 'bundler'
gem 'bundler-unload'
gem 'coderay'
gem 'eventmachine'
gem 'executable-hooks'
gem 'gem-wrappers'
gem 'gmail'
gem 'gmail_xoauth'
gem 'highline', ">=1.7.1"
gem 'io-console'
gem 'json'
gem 'mail'
gem 'method_source'
gem 'mime-types'
gem 'minitest'
gem 'multi_json'
gem 'nexmo'
gem 'oauth'
gem 'power_assert'
gem 'pry'
gem 'psych'
gem 'rake'
gem 'rdoc'
gem 'redis'
gem 'redis-semaphore'
gem 'rubygems-bundler'
gem 'rvm'
gem 'slop'
gem 'test-unit'
gem 'uuidtools'
gem 'parse-ruby-client'

Gemfile.lock
GEM
  remote: https://rubygems.org/
  specs:
    airbrake (4.2.1)
      builder
      multi_json
    awesome_print (1.6.1)
    bigdecimal (1.2.7)
    builder (3.2.2)
    bundler-unload (1.0.2)
    coderay (1.1.0)
    eventmachine (1.0.7)
    executable-hooks (1.3.2)
    faraday (0.9.1)
      multipart-post (>= 1.2, < 3)
    faraday_middleware (0.9.1)
      faraday (>= 0.7.4, < 0.10)
    gem-wrappers (1.2.7)
    gmail (0.5.0)
      gmail_xoauth (>= 0.3.0)
      mail (>= 2.2.1)
    gmail_xoauth (0.4.1)
      oauth (>= 0.3.6)
    highline (1.7.2)
    io-console (0.4.3)
    json (1.8.3)
    mail (2.6.3)
      mime-types (>= 1.16, < 3)
    method_source (0.8.2)
    mime-types (2.6.1)
    minitest (5.7.0)
    multi_json (1.11.0)
    multipart-post (2.0.0)
    nexmo (3.0.0)
    oauth (0.4.7)
    parse-ruby-client (0.3.0)
      faraday
      faraday_middleware
    power_assert (0.2.3)
    pry (0.10.1)
      coderay (~> 1.1.0)
      method_source (~> 0.8.1)
      slop (~> 3.4)
    psych (2.0.13)
    rake (10.4.2)
    rdoc (4.2.0)
    redis (3.2.1)
    redis-semaphore (0.2.4)
      redis
    rubygems-bundler (1.4.4)
      bundler-unload (>= 1.0.2)
      executable-hooks (>= 1.3.2)
    rvm (1.11.3.9)
    slop (3.6.0)
    test-unit (3.1.2)
      power_assert
    uuidtools (2.1.5)

PLATFORMS
  ruby

DEPENDENCIES
  airbrake
  awesome_print
  bigdecimal
  builder
  bundler
  bundler-unload
  coderay
  eventmachine
  executable-hooks
  gem-wrappers
  gmail
  gmail_xoauth
  highline (>= 1.7.1)
  io-console
  json
  mail
  method_source
  mime-types
  minitest
  multi_json
  nexmo
  oauth
  parse-ruby-client
  power_assert
  pry
  psych
  rake
  rdoc
  redis
  redis-semaphore
  rubygems-bundler
  rvm
  slop
  test-unit
  uuidtools

I have reproed this under ruby 2.1.6p336 with about any version of bundler from 1.8.9 and later (1.9-latest and 1.10-latest).
I don't know if it is present in earlier versions.
My minimal repro steps are
mkdir /tmp/bundler_repro

# I am using rbenv, plz adjust to your setup
echo "2.1.6" > /tmp/bundler_repro/.ruby-version

# This gem version matches exactly the version number of io-console
# in the ruby 2.1.6 builtin gemset.
# Probably explains the presence of 'cached_built_in_gem' in the callstack.
echo "gem 'io-console', '= 0.4.3', :require => false" > /tmp/bundler_repro/Gemfile

# boom
cd /tmp/bundler_repro && bundle package

============== #<Gem::Specification name=io-console version=0.4.3>
--- ERROR REPORT TEMPLATE -------------------------------------------------------
- What did you do?

  I ran the command `/home/sweethome/.rbenv/versions/2.1.6/bin/bundle package`

- What did you expect to happen?

  I expected Bundler to...

- What happened instead?

  Instead, what actually happened was...

Error details

    NoMethodError: undefined method `source_uri' for nil:NilClass
      /home/sweethome/.rbenv/versions/2.1.6/lib/ruby/gems/2.1.0/gems/bundler-1.9.10/lib/bundler/source/rubygems.rb:368:in `fetch_gem'
      /home/sweethome/.rbenv/versions/2.1.6/lib/ruby/gems/2.1.0/gems/bundler-1.9.10/lib/bundler/source/rubygems.rb:171:in `cached_built_in_gem'
      /home/sweethome/.rbenv/versions/2.1.6/lib/ruby/gems/2.1.0/gems/bundler-1.9.10/lib/bundler/source/rubygems.rb:153:in `cache'
      /home/sweethome/.rbenv/versions/2.1.6/lib/ruby/gems/2.1.0/gems/bundler-1.9.10/lib/bundler/runtime.rb:113:in `block in cache'
      /home/sweethome/.rbenv/versions/2.1.6/lib/ruby/gems/2.1.0/gems/bundler-1.9.10/lib/bundler/runtime.rb:110:in `cache'
      /home/sweethome/.rbenv/versions/2.1.6/lib/ruby/gems/2.1.0/gems/bundler-1.9.10/lib/bundler/cli/package.rb:20:in `run'
      /home/sweethome/.rbenv/versions/2.1.6/lib/ruby/gems/2.1.0/gems/bundler-1.9.10/lib/bundler/cli.rb:256:in `package'
      /home/sweethome/.rbenv/versions/2.1.6/lib/ruby/gems/2.1.0/gems/bundler-1.9.10/lib/bundler/vendor/thor/lib/thor/command.rb:27:in `run'
      /home/sweethome/.rbenv/versions/2.1.6/lib/ruby/gems/2.1.0/gems/bundler-1.9.10/lib/bundler/vendor/thor/lib/thor/invocation.rb:126:in `invoke_command'
      /home/sweethome/.rbenv/versions/2.1.6/lib/ruby/gems/2.1.0/gems/bundler-1.9.10/lib/bundler/vendor/thor/lib/thor.rb:359:in `dispatch'
      /home/sweethome/.rbenv/versions/2.1.6/lib/ruby/gems/2.1.0/gems/bundler-1.9.10/lib/bundler/vendor/thor/lib/thor/base.rb:440:in `start'
      /home/sweethome/.rbenv/versions/2.1.6/lib/ruby/gems/2.1.0/gems/bundler-1.9.10/lib/bundler/cli.rb:10:in `start'
      /home/sweethome/.rbenv/versions/2.1.6/lib/ruby/gems/2.1.0/gems/bundler-1.9.10/bin/bundle:20:in `block in <top (required)>'
      /home/sweethome/.rbenv/versions/2.1.6/lib/ruby/gems/2.1.0/gems/bundler-1.9.10/lib/bundler/friendly_errors.rb:7:in `with_friendly_errors'
      /home/sweethome/.rbenv/versions/2.1.6/lib/ruby/gems/2.1.0/gems/bundler-1.9.10/bin/bundle:18:in `<top (required)>'
      /home/sweethome/.rbenv/versions/2.1.6/bin/bundle:23:in `load'
      /home/sweethome/.rbenv/versions/2.1.6/bin/bundle:23:in `<main>'

Environment

    Bundler   1.9.10
    Rubygems  2.2.3
    Ruby      2.1.6p336 (2015-04-13 revision 50298) [x86_64-linux]
    GEM_HOME  /home/sweethome/.rbenv/versions/2.1.6/lib/ruby/gems/2.1.0
    GEM_PATH  /home/sweethome/.rbenv/versions/2.1.6/lib/ruby/gems/2.1.0:/home/sweethome/.gem/ruby/2.1.0
    Git       2.4.5

Bundler settings

    build.pg
      Set for the current user (/home/sweethome/.bundle/config): "--with-pg-config=/usr/lib/postgresql/9.4/bin/pg_config"
    build.nokogiri
      Set for the current user (/home/sweethome/.bundle/config): "--use-system-libraries"
--- TEMPLATE END ----------------------------------------------------------------

Unfortunately, an unexpected error occurred, and Bundler cannot continue.

First, try this link to see if there are any existing issue reports for this error:
https://github.com/bundler/bundler/search?q=undefined+method+%60source_uri%27+for+nil%3ANilClass&type=Issues

If there aren't any reports for this error yet, please create copy and paste the report template above into a new issue. Don't forget to anonymize any private data! The new issue form is located at:
https://github.com/bundler/bundler/issues/new

I have a hypothesis of what the problem is:
This failure occurs when a gem is included in the Gemfile that is already built into ruby. I was trying to work around gems that are no longer included in ruby 2.2 but bundling in ruby 2.1.6. For me it was test-unit. Does that sound right?

Yup, it does. That was exactly the case for io-console

For now, a workaround is to add "source 'https://rubygems.org'" to your Gemfile.
On Wed, Jul 29, 2015 at 4:21 AM, François Jacques
notifications@github.com wrote:

Yup, it does. That was exactly the case for io-console
Reply to this email directly or view it on GitHub:
https://github.com/bundler/bundler/issues/3158#issuecomment-125922748

the workaround does not work for me

Fixed by https://github.com/bundler/bundler/pull/3896.

Awesome!

authors: TimMoore agis- francoisjacques herisanu howethomas iambaozheng indirect liveh2o lukaso mmmries nevinera spjsschl wst07261144

repo: bundler/bundler


text:
error when creating new rails projects, "Permission denied"

Here is the error report template:
Error details
Errno::EACCES: Permission denied @ rb_sysopen - /Users/username/.bundle/cache/compact_index/rubygems.org.443.29b0360b937aa4d161703e6160654e47/versions
  /Users/username/.rbenv/versions/2.1.2/lib/ruby/gems/2.1.0/gems/bundler-1.12.0.rc/lib/bundler/vendor/compact_index_client/lib/compact_index_client/updater.rb:32:in `initialize'
  /Users/username/.rbenv/versions/2.1.2/lib/ruby/gems/2.1.0/gems/bundler-1.12.0.rc/lib/bundler/vendor/compact_index_client/lib/compact_index_client/updater.rb:32:in `open'
  /Users/username/.rbenv/versions/2.1.2/lib/ruby/gems/2.1.0/gems/bundler-1.12.0.rc/lib/bundler/vendor/compact_index_client/lib/compact_index_client/updater.rb:32:in `open'
  /Users/username/.rbenv/versions/2.1.2/lib/ruby/gems/2.1.0/gems/bundler-1.12.0.rc/lib/bundler/vendor/compact_index_client/lib/compact_index_client/updater.rb:32:in `update'
  /Users/username/.rbenv/versions/2.1.2/lib/ruby/gems/2.1.0/gems/bundler-1.12.0.rc/lib/bundler/vendor/compact_index_client/lib/compact_index_client.rb:63:in `update'
  /Users/username/.rbenv/versions/2.1.2/lib/ruby/gems/2.1.0/gems/bundler-1.12.0.rc/lib/bundler/vendor/compact_index_client/lib/compact_index_client.rb:54:in `update_and_parse_checksums!'
  /Users/username/.rbenv/versions/2.1.2/lib/ruby/gems/2.1.0/gems/bundler-1.12.0.rc/lib/bundler/fetcher/compact_index.rb:63:in `available?'
  /Users/username/.rbenv/versions/2.1.2/lib/ruby/gems/2.1.0/gems/bundler-1.12.0.rc/lib/bundler/fetcher/compact_index.rb:15:in `call'
  /Users/username/.rbenv/versions/2.1.2/lib/ruby/gems/2.1.0/gems/bundler-1.12.0.rc/lib/bundler/fetcher/compact_index.rb:15:in `block in compact_index_request'
  /Users/username/.rbenv/versions/2.1.2/lib/ruby/gems/2.1.0/gems/bundler-1.12.0.rc/lib/bundler/fetcher.rb:154:in `use_api'
  /Users/username/.rbenv/versions/2.1.2/lib/ruby/gems/2.1.0/gems/bundler-1.12.0.rc/lib/bundler/source/rubygems.rb:331:in `block in api_fetchers'
  /Users/username/.rbenv/versions/2.1.2/lib/ruby/gems/2.1.0/gems/bundler-1.12.0.rc/lib/bundler/source/rubygems.rb:331:in `select'
  /Users/username/.rbenv/versions/2.1.2/lib/ruby/gems/2.1.0/gems/bundler-1.12.0.rc/lib/bundler/source/rubygems.rb:331:in `api_fetchers'
  /Users/username/.rbenv/versions/2.1.2/lib/ruby/gems/2.1.0/gems/bundler-1.12.0.rc/lib/bundler/source/rubygems.rb:336:in `block in remote_specs'
  /Users/username/.rbenv/versions/2.1.2/lib/ruby/gems/2.1.0/gems/bundler-1.12.0.rc/lib/bundler/index.rb:10:in `build'
  /Users/username/.rbenv/versions/2.1.2/lib/ruby/gems/2.1.0/gems/bundler-1.12.0.rc/lib/bundler/source/rubygems.rb:335:in `remote_specs'
  /Users/username/.rbenv/versions/2.1.2/lib/ruby/gems/2.1.0/gems/bundler-1.12.0.rc/lib/bundler/source/rubygems.rb:82:in `specs'
  /Users/username/.rbenv/versions/2.1.2/lib/ruby/gems/2.1.0/gems/bundler-1.12.0.rc/lib/bundler/definition.rb:211:in `block (2 levels) in index'
  /Users/username/.rbenv/versions/2.1.2/lib/ruby/gems/2.1.0/gems/bundler-1.12.0.rc/lib/bundler/definition.rb:209:in `each'
  /Users/username/.rbenv/versions/2.1.2/lib/ruby/gems/2.1.0/gems/bundler-1.12.0.rc/lib/bundler/definition.rb:209:in `block in index'
  /Users/username/.rbenv/versions/2.1.2/lib/ruby/gems/2.1.0/gems/bundler-1.12.0.rc/lib/bundler/index.rb:10:in `build'
  /Users/username/.rbenv/versions/2.1.2/lib/ruby/gems/2.1.0/gems/bundler-1.12.0.rc/lib/bundler/definition.rb:206:in `index'
  /Users/username/.rbenv/versions/2.1.2/lib/ruby/gems/2.1.0/gems/bundler-1.12.0.rc/lib/bundler/definition.rb:200:in `resolve'
  /Users/username/.rbenv/versions/2.1.2/lib/ruby/gems/2.1.0/gems/bundler-1.12.0.rc/lib/bundler/definition.rb:140:in `specs'
  /Users/username/.rbenv/versions/2.1.2/lib/ruby/gems/2.1.0/gems/bundler-1.12.0.rc/lib/bundler/definition.rb:129:in `resolve_remotely!'
  /Users/username/.rbenv/versions/2.1.2/lib/ruby/gems/2.1.0/gems/bundler-1.12.0.rc/lib/bundler/installer.rb:195:in `resolve_if_need'
  /Users/username/.rbenv/versions/2.1.2/lib/ruby/gems/2.1.0/gems/bundler-1.12.0.rc/lib/bundler/installer.rb:70:in `run'
  /Users/username/.rbenv/versions/2.1.2/lib/ruby/gems/2.1.0/gems/bundler-1.12.0.rc/lib/bundler/installer.rb:22:in `install'
  /usr/local/Cellar/rbenv/1.0.0/rbenv.d/exec/gem-rehash/rubygems_plugin.rb:27:in `install'
  /Users/username/.rbenv/versions/2.1.2/lib/ruby/gems/2.1.0/gems/bundler-1.12.0.rc/lib/bundler/cli/install.rb:102:in `run'
  /Users/username/.rbenv/versions/2.1.2/lib/ruby/gems/2.1.0/gems/bundler-1.12.0.rc/lib/bundler/cli.rb:175:in `install'
  /Users/username/.rbenv/versions/2.1.2/lib/ruby/gems/2.1.0/gems/bundler-1.12.0.rc/lib/bundler/vendor/thor/lib/thor/command.rb:27:in `run'
  /Users/username/.rbenv/versions/2.1.2/lib/ruby/gems/2.1.0/gems/bundler-1.12.0.rc/lib/bundler/vendor/thor/lib/thor/invocation.rb:126:in `invoke_command'
  /Users/username/.rbenv/versions/2.1.2/lib/ruby/gems/2.1.0/gems/bundler-1.12.0.rc/lib/bundler/vendor/thor/lib/thor.rb:359:in `dispatch'
  /Users/username/.rbenv/versions/2.1.2/lib/ruby/gems/2.1.0/gems/bundler-1.12.0.rc/lib/bundler/vendor/thor/lib/thor/base.rb:440:in `start'
  /Users/username/.rbenv/versions/2.1.2/lib/ruby/gems/2.1.0/gems/bundler-1.12.0.rc/lib/bundler/cli.rb:11:in `start'
  /Users/username/.rbenv/versions/2.1.2/lib/ruby/gems/2.1.0/gems/bundler-1.12.0.rc/exe/bundle:27:in `block in <main>'
  /Users/username/.rbenv/versions/2.1.2/lib/ruby/gems/2.1.0/gems/bundler-1.12.0.rc/lib/bundler/friendly_errors.rb:98:in `with_friendly_errors'
  /Users/username/.rbenv/versions/2.1.2/lib/ruby/gems/2.1.0/gems/bundler-1.12.0.rc/exe/bundle:19:in `<main>'

Environment
Bundler   1.12.0.rc
Rubygems  2.6.3
Ruby      2.1.2p95 (2014-05-08 revision 45877) [x86_64-darwin15.0]
GEM_HOME  /Users/username/.rbenv/versions/2.1.2/lib/ruby/gems/2.1.0
GEM_PATH  /Users/username/.rbenv/versions/2.1.2/lib/ruby/gems/2.1.0:/Users/username/.gem/ruby/2.1.0
Git       2.8.1
  Bundler settings

orig_path
Set via BUNDLE_ORIG_PATH: "/Users/username/.rbenv/versions/2.1.2/bin:/usr/local/Cellar/rbenv/1.0.0/libexec:/Users/username/.rbenv/shims:/Users/username/.rbenv/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Users/username/.rvm/bin"

Do you have the correct file permissions on the file or directories listed in: /Users/username/.bundle/cache/compact_index/rubygems.org.443.29b0360b937aa4d161703e6160654e47/versions ?

I think I figured it out. I think bundler was installed to the root
directory. Uninstalling and reinstalling fixed the issue. Thanks for the
great reply time
On Saturday, April 9, 2016, James Wen notifications@github.com wrote:

Do you have the correct file permissions on the file or directories listed
in:
/Users/username/.bundle/cache/compact_index/rubygems.org.443.29b0360b937aa4d161703e6160654e47/versions
?
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/bundler/bundler/issues/4429#issuecomment-207794715


text:
🛑 doubledouble is down

In e1e2b46, doubledouble (https://doubledouble.top/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: doubledouble is back up in afa0c8c after 19 minutes.


text:
Incident report queue has times listed as GMT, not correct time zone

As I was cleaning up the incident report queue, I noticed that the incident reports were filed with the wrong timestamp (ie. its currently Friday 11am and there were reports filed Friday at 1620 as in the future).

Sounds like I made a hash of it.  Thank you for the clean-up, and my
apologies.  I'd also like to apologize for hogging the 3rd stations when
you were trying to get in a quick log.  I should have turned it over to
you, Pronto!
Fortress
On Fri, Sep 1, 2017 at 11:58 AM, rangerlibrarian notifications@github.com
wrote:

As I was cleaning up the incident report queue, I noticed that the
incident reports were filed with the wrong timestamp (ie. its currently
Friday 11am and there were reports filed Friday at 1620 as in the future).
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/burningmantech/ranger-ims-mac/issues/75, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AP76NvsVvr3Rz-xzSRoa5Ly-j7jvE09_ks5seFPZgaJpZM4PKhFE
.

The time zone setting on the client machine effects how it is displayed.
If you don't think that's the cause, I'll need specific examples for where to look for problems.

authors: rangerfortress rangerlibrarian wsanchez

repo: burningmantech/ranger-ims-mac


text:
Bundle-SymbolicName header missing error when installing on AEM

I'm implementing a feature in a project on AEM with AWS and the AWS libraries require the JMESPath library to be deployed to the container. The container requires that they bundle-SymbolicName been added to the header before it is deployable

I'm unsure as to what this means. From googling the terms I gather it has something to do with OSGi. The quickest way for this to happen is if you could submit a pull request with the necessary changes.

authors: gffny iconara

repo: burtcorp/jmespath-java


text:
🛑 LiveSeeYou-redirect is down

In b105351, LiveSeeYou-redirect (http://www.liveseeyou.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: LiveSeeYou-redirect is back up in 4c457e9.

repo: butteryoon/liveseeyou


text:
Look into reupload lag with listen mode on the 64Drive

When reuploading a ROM in listen mode, it can get stuck on 100% for much longer than usual on the 64Drive.

Fixed in the incoming commit.

license: WTFPL


text:
Replicating BioBERT Results - Mortality Prediction

hello,
we are trying to run the mortality prediction scripts on BioBERT model, however, we are encountering errors wrt the tokenizer.

We also tried adding AutoTokenizer from hugging face in the tokenization.py file of FARM, but the error remained the same. Can you suggest us how can we go about using BioBERT here?
Thank you!

Hello,
thanks for reaching out!
From the error message it is unfortunately hard to tell where the error comes from. Can you give a bit more detail about which BioBERT (base or large) you are using and which parameters you pass to the training?

repo: bvanaken/clinical-outcome-prediction


text:
Rendering problem with 40k+ rows

React-virtualized version: 8.8.1
Rows are disappearing when you scroll with 40 000 and more rows. It happens also in your demo: https://bvaughn.github.io/react-virtualized/#/components/Grid. It affects
I will try to revert to previous versions to identify where it happened.
Edit: version 8.7.1 seems to be ok.

Interesting. Thank you for reporting this!
I am able to scrollbar-scroll through a couple hundred thousand rows, but wheel-scrolling does indeed break as you mention.
So this worked in 8.7.1 but broken in 8.8.0 huh... that would mean it's probably related to the cached inline style objects.

If you have any time to dig into it before I do- I would appreciate the hand.

FYI @vysinsky: This issue has been fixed with the recent 8.9.0 release.
Just verified that the demo page works with 500,000 rows.
cc @cheton RE bvaughn/react-virtualized/issues/524

Awesome. Thank you @bvaughn!

Thank you!

authors: bvaughn cheton vysinsky

repo: bvaughn/react-virtualized


text:
🛑 Whitestone Landmark is down

In 6e4a4f6, Whitestone Landmark (https://cloud.tymly.in/status/1095) was down:

HTTP code: 521
Response time: 232 ms

Resolved: Whitestone Landmark is back up in 3a83afa.

repo: bvenkysubbu/tymlymonitor


text:
🛑 Desai Grandeur 1 is down

In efec62a, Desai Grandeur 1 (https://cloud.tymly.in/status/1133) was down:

HTTP code: 521
Response time: 20213 ms

Resolved: Desai Grandeur 1 is back up in 346fcf0.


text:
🛑 PSR Aster 3 E Block is down

In d15807f, PSR Aster 3 E Block (https://cloud.tymly.in/status/1064) was down:

HTTP code: 521
Response time: 234 ms

Resolved: PSR Aster 3 E Block is back up in b657f2d.


text:
🛑 Nitesh Flushing Meadows Block A is down

In 2ed20fa, Nitesh Flushing Meadows Block A (https://cloud.tymly.in/status/1053) was down:

HTTP code: 521
Response time: 20235 ms

Resolved: Nitesh Flushing Meadows Block A is back up in 9d4aacd.


text:
🛑 Sowparnika Swastika 1 is down

In f745a69, Sowparnika Swastika 1 (https://cloud.tymly.in/status/1101) was down:

HTTP code: 521
Response time: 14112 ms

Resolved: Sowparnika Swastika 1 is back up in 0769ffe.


text:
🛑 Trifecta Esplanade D Block is down

In f77ea33, Trifecta Esplanade D Block (https://cloud.tymly.in/status/1156) was down:

HTTP code: 521
Response time: 20228 ms

Resolved: Trifecta Esplanade D Block is back up in 6de8dbe.


text:
🛑 SMD Altezz Block A is down

In e8ef12b, SMD Altezz Block A (https://cloud.tymly.in/status/1175) was down:

HTTP code: 521
Response time: 913 ms

Resolved: SMD Altezz Block A is back up in 22cda52.


text:
🛑 VBHC Serene Town A Block is down

In 22592eb, VBHC Serene Town A Block (https://cloud.tymly.in/status/1129) was down:

HTTP code: 521
Response time: 20231 ms

Resolved: VBHC Serene Town A Block is back up in 7313724.


text:
🛑 VBHC Serene Town B Block is down

In b6204bb, VBHC Serene Town B Block (https://cloud.tymly.in/status/1130) was down:

HTTP code: 521
Response time: 243 ms

Resolved: VBHC Serene Town B Block is back up in ec21422.


text:
🛑 Sowparnika Swastika 2 is down

In 304ed92, Sowparnika Swastika 2 (https://cloud.tymly.in/status/1099) was down:

HTTP code: 521
Response time: 22012 ms

Resolved: Sowparnika Swastika 2 is back up in 967634d.


text:
🛑 Trifecta Esplanade N Block is down

In fde9491, Trifecta Esplanade N Block (https://cloud.tymly.in/status/1165) was down:

HTTP code: 521
Response time: 238 ms

Resolved: Trifecta Esplanade N Block is back up in 4373e0a.


text:
🛑 PSR Aster 1 is down

In eea14d1, PSR Aster 1 (https://cloud.tymly.in/status/1059) was down:

HTTP code: 521
Response time: 20227 ms

Resolved: PSR Aster 1 is back up in 33fc33f.


text:
🛑 Dasta Concerto Basement is down

In 4d03fbd, Dasta Concerto Basement (https://cloud.tymly.in/status/1138) was down:

HTTP code: 521
Response time: 20261 ms

Resolved: Dasta Concerto Basement is back up in bc1cae2.


text:
🛑 Mahaveer Varna A4 is down

In 48ac197, Mahaveer Varna A4 (https://cloud.tymly.in/status/1084) was down:

HTTP code: 521
Response time: 20226 ms

Resolved: Mahaveer Varna A4 is back up in cbb72ef.


text:
🛑 Greenville Whitefield is down

In 9b90456, Greenville Whitefield (https://cloud.tymly.in/status/1020) was down:

HTTP code: 521
Response time: 20232 ms

Resolved: Greenville Whitefield is back up in 2b498bc.


text:
🛑 Sunshine Silicon Citi is down

In 5dbf68f, Sunshine Silicon Citi (https://cloud.tymly.in/status/1021) was down:

HTTP code: 521
Response time: 1592 ms

Resolved: Sunshine Silicon Citi is back up in 280aeba.


text:
🛑 Trifecta Esplanade N Block is down

In 80608ea, Trifecta Esplanade N Block (https://cloud.tymly.in/status/1165) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Trifecta Esplanade N Block is back up in 38a6a85.


text:
🛑 SMR Vinay Cascade B Block is down

In 5c4b907, SMR Vinay Cascade B Block (https://cloud.tymly.in/status/1093) was down:

HTTP code: 521
Response time: 20222 ms

Resolved: SMR Vinay Cascade B Block is back up in 989b195.


text:
🛑 SMR Vinay Cascade B Block is down

In eed6e97, SMR Vinay Cascade B Block (https://cloud.tymly.in/status/1093) was down:

HTTP code: 521
Response time: 20221 ms

Resolved: SMR Vinay Cascade B Block is back up in 7f1b30b.


text:
🛑 VBHC Serene Town B Block is down

In 1907ef4, VBHC Serene Town B Block (https://cloud.tymly.in/status/1130) was down:

HTTP code: 521
Response time: 233 ms

Resolved: VBHC Serene Town B Block is back up in 7661daa.