Using Task.Run in Google.Cloud.Spanner.Data causes remarkable delay

We are developing a server application using Google.Cloud.Spanner.Data with .NET Core 3.1.
The application server is built with ASP.NET Core MVC.
Remarkable delay in the part that uses Task.Run at Google.Cloud.Spanner.Data  has occurred when load testing sending a large number of requests.
At high load, it takes more than 10 seconds and the transaction times out.
Specifically, call Task.Run() in GetOrdinal() and in PopulateMetadata() calliing from GetFieldValue() via GetSpannerFieldType().
So, when I cloned google-cloud-dotnet and implemented the async method of GetOrdinal() and GetFieldValue(),
The noticeable delay mentioned above has been resolved.
How about implementing the Async version for the two methods GetOrdinal() and GetFieldValue() ?
Now that I've signed the Corporate CLA, I can refine my implementation and contribute.

We could implement extra methods for those, yes. They're not part of ADO.NET (which basically wasn't designed for asynchrony) which reduces the portability of the solution, unfortunately.
I do wonder where the delay is coming from - it sounds like your system probably has a huge number of tasks, and the thread-pool can't cope - my only concern is that this would be tackling one symptom, only to propagate the problem elsewhere.
Another option that might be more transparent is to populate the metadata more eagerly - at which point a lot of things might be simplified. I'll have to look into how feasible that would be.

Yes, Those async methods who I proposed is NOT a part of ADO.NET.
But, Calling GetOrdinal() and GetFieldValue() is unavoidable because I need to get the data by specifying the column by name.
ASP.NET Core Performance Best Practices recommends not to use Task.Run, so I want an idea that doesn't call Task.Run and is consistent with the ADO.NET interface.
How about implementing the async version of GetFieldValue<T>(string columnName) which does not inherited from DbDataReader.

Well yes, it's nice not to use Task.Run if you can avoid it, but the fundamental problem is that Spanner communication is asynchronous and ADO.NET is synchronous. (And we need to use Task.Run() rather than blocking on the task as the same code could be used from WPF etc.) Unfortunately checklists like those "best practices" don't often take account the reality of synchronous code :(
I'll look at it when I get more time, ideally changing it to populate the metadata more eagerly (as I suspect its needed everywhere anyway). It won't be this week though I'm afraid.

Fixed now - there's a new GetOrdinalAsync method to call if you want to use that before calling Read or ReadAsync - but after you've moved to the first row, it shouldn't call Task.Run anyway.

(We're planning on doing a 3.1.0 release later this week, so the change will be in that.)

Thanks a lot !
However, it seems that this change does not concern about GetFieldValue(int ordinal), I think.
// GetFieldValue(int ordinal) calls GetSpannerFieldType(int i) which calls PopulateMetadata().

That should be fine though - because PopulateMetadata does nothing if the metadata already exists, which it already will if you've called Read or ReadAsync... and if you haven't called Read or ReadAsync, then GetFieldValue will fail anyway.

We've tested brand-new libraries v3.1.0 with our server codes, and this issue was solved.
Thank you very much!


Feature: Proportional Resize

I added a feature that scales the iframe proportionally. It uses an aspect ratio derived from the width/height props.
I added three new props: resize, resizeDelay, and fitParent.
resize enables proportional resizing. I set the default to false since it would change the behavior for existing users.
resizeDelay makes sure the player isn't updated every event.
fitParent makes the resize logic use the parent element's width for sizing. Without it, CSS properties are necessary.
watch.resize is necessary to toggle off the eventHandler and also restore the player's initial state. This way the component always responds to props actively, instead of requiring it to be remounted.
Also updated the docs to reflect these changes. Added a props section.
Testing was not working at all in the repo. Didn't want to solve two problems. If you like this PR, I can add tests later once it is sorted out.

@tarikhamilton  great work, thank you for your contribution.


fix(scan): correctly resolve virtual modules

Description
Reverts https://github.com/vitejs/vite/pull/5659 (cc  @benmccann)
Reason was that resolving virtual modules with resolve() skips the virtual module loading, so essentially we never scanned the files in <script> tags of Svelte (and Vue's respective).
Additional context

What is the purpose of this pull request?

[x] Bug fix
[ ] New Feature
[ ] Documentation update
[ ] Other

Before submitting the PR, please make sure you do the following

[x] Read the Contributing Guidelines.
[ x Read the Pull Request Guidelines and follow the Commit Convention.
[x] Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
[x] Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
[ ] Ideally, include relevant tests that fail without this PR but pass with it.

Yeah' I've tested this locally on vite-plugin-svelte's kit-node test app. I have not run all tests though. (It doesn't seem to like my local environment). But I'm pretty confident that the code we had before wasn't working as expected.

To be safe, I can try to get my setup working tomorrow and run the tests again. We may still have time during beta.

Hmm. When I run the tests it looks like we go from 3 tests failing before this PR to 73 tests failing after this PR. A lot of the failing tests are in the kit-node test app, so I'm surprised that app worked for you and doesn't seem to be for me

There's currently two kinds of tests in vite-plugin-svelte, for dev and build. I think this would fix dev mode tests, and the failed tests you see now could potentially be from the build mode tests? I have another PR (incoming) to address that as kit-node build + preview doesn't work currently due to dedupeRequire.

I was (finally) able to get tests running locally. Yeah looks like there's still some things not caught, putting this as draft for now.

I made the real fix now, and it was because in esbuild, we had to resolve the virtual module to an actual file path for its file imports to be resolved, which was causing the initial html:virtual-module:... bug in the first place. I refactored the code a bit and it's working locally for me now. All tests passing for dev mode.


UE review comments_1

Mockup can be read from:
https://wiki.eng.vmware.com/wiki/images/4/4d/Miscellaneous.pdf
Page 3


Added AEG PX7 Purifier

Thank you! I'm not able to verify that it work, so I'll merge it and wait for feedback.

Works for me :)

I'm really trying to get this to work but I'm not succeeding. My AX7 is showing up in the AEG and Electrolux app on my phone. I can manage it from there so all good.
I have installed the integration from HACS, restarted HA, added it through the normal integration screen and used the same credentials there as I use in the apps on my phone.
It keeps saying I have no entities/devices and that setup has failed and it will try again (and fail).
Did I miss a step?

I'm really trying to get this to work but I'm not succeeding. My AX7 is showing up in the AEG and Electrolux app on my phone. I can manage it from there so all good.
I have installed the integration from HACS, restarted HA, added it through the normal integration screen and used the same credentials there as I use in the apps on my phone.
It keeps saying I have no entities/devices and that setup has failed and it will try again (and fail).
Did I miss a step?

I deleted the integration in HACS, then adjusted and reloaded it first. With this it worked.
Do you have the latest version?
Just tried it with another AEG (have 3), also went without problems.

Hey @MickLesk , thanks for responding.  So here's what I just did:

deleted integration in HA
deleted integration from HACS.
full shutdown and restart of the system
installed it again from HACS (made sure it was version 1.0.7)
restarted HA
added the integration in HA
waited
added my credentials (my email in the username field) and (password in the password field)
error when trying to setup the integration, will try later it keeps saying.

some more info:
Logger: homeassistant.config_entries
Source: config_entries.py:432
First occurred: 21:54:54 (1 occurrences)
Last logged: 21:54:54
Config entry<EMAIL_ADDRESS>for wellbeing integration not ready yet; Retrying in background

Should we add the AX5 and AX9 models too?

Should we add the AX5 and AX9 models too?

I can do this tomorrow, you can Test this, because i dont have AX5 / AX9 😅

@STemplar ive added AX5 & AX9


Issues with Leaflet 1.3.4 and MarkerCluster 1.4.1

When using this plugin with Issues with Leaflet 1.3.4 and MarkerCluster 1.4.1, when using .addLayer or .addLayer, .removeLayer or .removeLayer, get the following error here and there:

Any chance of getting a compatibility update?

Hi,
The repo example looks to work fine with the versions you mention:
https://plnkr.co/edit/kwjn5B8bR9imbTXXYEJV?p=preview
Should you still need help on your project, please provide a live reproduction example of your issue (e.g. by forking the above Plunker), and consider posting a question on Stack Overflow to reach a wider audience.

Closing due to lack of input.


Bump up implicit-hie-cradle lower bound

To ensure we get the desired version

The build is failing due to https://github.com/actions/setup-haskell/issues/44, we'll have to wait to the fix

The build is failing due to actions/setup-haskell#44, we'll have to wait to the fix

Many thanks for digging this out!


Spekt8 - Visualization tool to perhaps include in Polaris

A visualization tool and possible candidate for including in Polaris:
https://github.com/spekt8/spekt8

Nice. Perhaps we can create a chart for use in Polaris and then PR the chart to the spekt8 repo


add zowe chatops to zowe.org front page

Signed-off-by: MarkAckert<EMAIL_ADDRESS>

cc: @Phoebecdy91.  This is Mark's PR for the changes to zowe.org.

@MarkAckert.     Phoebe and I were working this morning and she had a newer graphic built on yours but with a nice zoomed in area,  so we added that into the branch and also I switched chatops to chat at the same time.  @nannanli was also going to do some work on the site to swop some of the graphic->description for the projects in html to be left->right, right->left reading down the page for visual aesthetics, and also break apart the list of components at the top to separate the four core ones apart from the incubator ones.   She is a reviewer as well on this now.  Thank you !

resolves zowe/zowe-chat#4

Thanks for the updates Joe, I'll wait for nannanli's review

@nannanli ,  yes we should create our own channel once we get more momentum.  I'll bring this up at our next Zowe chat scrum call


smoothstate.js works perfectly, but CSS animations are not triggered

Hello!
I'm using smoothstate in my portfolio website – it works just fine, except for the fact that CSS animations are not triggered when a new page fragment is loaded, which is weird since I just copied over code from the demo. Tested in Safari, FF and Chrome, but to no avail.
I don't think this is a known/common issue. I'm using v0.5.2 of smoothstate.js, if that helps. Please let me know if posting my code will help figure out what's wrong.
Thank you!

any link to your site plz?
Before copy code and direct apply, we suggest you to really go through and have an overview understand on how it works bcz smoothstate is slightly an advanced plugin, required better understand how it actually works.
CSS3 animate; prefix such as -webkit, -moz, may required and the class overlaying is important as well.
You may check out my example > http://jonathlee.com

@Jonathlee I went through it and understood how it works. I used code from the demo because it fit my use case perfectly. When that didn't work, I went ahead and set it up myself, bit by bit. That didn't work either.
I checked for the usual suspects like vendor prefixes and such, but no dice. I'll post a link shortly.
Thanks!

@Jonathlee This is it – http://achalv.com/work/new/work.html

Replace your css from your line 253 with the below to try
/*
 * CSS Animations
 * Don't forget to add vendor prefixes!
 */

/* --------------- */

.m-scene.is-exiting > .content > .scene-element {
  -webkit-animation-direction: alternate-reverse;
  animation-direction: alternate-reverse; }

.m-scene .scene_element--fadein{
  animation: fadeIn linear 1s;
  animation-iteration-count: 1;
  transform-origin: 50% 50%;
  animation-fill-mode:forwards; /*when the spec is finished*/
  -webkit-animation: fadeIn linear 1s;
  -webkit-animation-iteration-count: 1;
  -webkit-transform-origin: 50% 50%;
  -webkit-animation-fill-mode:forwards; /*Chrome 16+, Safari 4+*/
  -moz-animation: fadeIn linear 1s;
  -moz-animation-iteration-count: 1;
  -moz-transform-origin: 50% 50%;
  -moz-animation-fill-mode:forwards; /*FF 5+*/
  -o-animation: fadeIn linear 1s;
  -o-animation-iteration-count: 1;
  -o-transform-origin: 50% 50%;
  -o-animation-fill-mode:forwards; /*Not implemented yet*/
  -ms-animation: fadeIn linear 1s;
  -ms-animation-iteration-count: 1;
  -ms-transform-origin: 50% 50%;
  -ms-animation-fill-mode:forwards; /*IE 10+*/
}

@keyframes fadeIn{
  0% {
    opacity:0;
    transform:  scaleX(1.50) scaleY(1.50) ;
  }
  100% {
    opacity:1.00;
    transform:  scaleX(1.00) scaleY(1.00) ;
  }
}

@-moz-keyframes fadeIn{
  0% {
    opacity:0;
    -moz-transform:  scaleX(1.50) scaleY(1.50) ;
  }
  100% {
    opacity:1.00;
    -moz-transform:  scaleX(1.00) scaleY(1.00) ;
  }
}

@-webkit-keyframes fadeIn {
  0% {
    opacity:0;
    -webkit-transform:  scaleX(1.50) scaleY(1.50) ;
  }
  100% {
    opacity:1.00;
    -webkit-transform:  scaleX(1.00) scaleY(1.00) ;
  }
}

@-o-keyframes fadeIn {
  0% {
    opacity:0;
    -o-transform:  scaleX(1.50) scaleY(1.50) ;
  }
  100% {
    opacity:1.00;
    -o-transform:  scaleX(1.00) scaleY(1.00) ;
  }
}

@-ms-keyframes fadeIn {
  0% {
    opacity:0;
    -ms-transform:  scaleX(1.50) scaleY(1.50) ;
  }
  100% {
    opacity:1.00;
    -ms-transform:  scaleX(1.00) scaleY(1.00) ;
  }
}

@Jonathlee Thanks, I did that and it works. But it flashes once before replacing the content, and then fades in again. Do you know what might be causing this?
Maybe it's adding classes prematurely?

It was creating a fadeIn animation, try changing the animation duration to 0 (in source.js)
onStart: {
          duration: 0,

Managed to fix it.
Thanks for your help, @Jonathlee!


Opening attachments (PDF) in Icedove doesn't work

I thing it is because it tries to launch the sandboxed evince, and this logs into the journal:
Feb 15 11:36:18 subgraph oz-daemon[765]: 2016/02/15 11:36:18 [icedove] (stderr) Cannot run a sandbox from inside a running sandbox!

A workaround is using /usr/bin-oz/evince from within icedove.

Migrated as #56


Update 02_Technical_Starter_code.ipynb

Hi,
I have been following the code in the book and have had to make amendments to run it. In this chapter, I have had to import matplotlib as plt in preference to np.histogram and add plt.show() to get the code to run.  I'm  a bit confused about using the object 'subplots' on p21 of the book as it is an object of class matplotlab and not np.histogram (?)

Hi @DavidAKZ .  Thanks for the question.  What comment in the book are you referencing?  I use matpotlib very widely throughout the book, so if I said otherwise ... the text needs to be fixed.  --Thanks, Mark

@mfenner1 . Thanks for your reply. I discovered  it was me that made the mistake. Basically confusing 'matplotlib as plt' with 'numpy as np'.
I would like to add one comment about generating the  Figure shown on p22.  For both methods of calculation, I had to add the following code to get the Figure to generate.
import matplotlib.pyplot as plt
 plt.show()

Are you able to say in the following line what the meaning of '[0]' is
few_counts = np.histogram(few_rolls, bins=np.arange(0.5, 7.5))[0]

Regards, David

@DavidAKZ
No worries!  The worst thing about code is that it does exactly (and only!) what we say.  For your questions:
(1) With plt.show(), that usually happens when you are running python from an interactive command line (or something like an IDE ... for example Spyder ...) and you have to force matplotlib to display stuff onscreen.  With current (recently updated jupyter notebooks), figures will display by default.  If you have an older notebook version, you may need to do %matplotlib inline. If you do that (in a jupyter notebook), you should see the figures displayed immediately below the cell with code that defines them.
(2)  np.histogram returns a few results.  We only need the first.  So, we select it with [0].  You can see the full details with either help(np.histogram) or here:  https://numpy.org/doc/stable/reference/generated/numpy.histogram.html
Best,
Mark

Thanks very much.


$ is not defined

Just noticed this error on https://ibma.github.io/Va11yS/WCAG_ARIA/ARIA18_example1.html:
Uncaught ReferenceError: $ is not defined at ARIA18_example1.html:11

Thanks for reporting this!  It looks like we were using http instead of https linking out to jQuery.  I found it in a couple of the other ARIA examples as well.  Changed them to https and also went ahead and switched to Google's CDN.

Glad it was an easy fix. 👍


Can't Pull Data for PTGI

Expected Behavior

We can gather data for all the securities in the Data Explorer.
Actual Behavior

The Data Explorer shows we have data for PTGI, but we can't pull any of it with a History request in a backtest or in a notebook. Additionally, the data isn't passed to OnData in a backtest.
Related thread
Potential Solution

N/A
Reproducing the Problem

This project includes a backtest and notebook that demonstrates the issue.
System Information

Checklist

[x] I have completely filled out this template
[x] I have confirmed that this issue exists on the current master branch
[x] I have confirmed that this is not a duplicate issue by searching issues

[x] I have provided detailed steps to reproduce the issue

Data in place but no PTGI map file - why isn't the data picked up?
Why aren't we generating the PTGI map file?

If its a mapping, not a delisting (i.e. PTGI is active as another ticker now) - then the algo is wrong and it should be called with today's ticker.


add update datastore script

@nevin-manoj1 Looks fine. I'll add approval and merge on GA day. Thanks


SSL_connect returned=1 errno=0 state=SSLv2/v3 read server hello A: unknown protocol (OpenSSL::SSL::SSLError)

I get this error when trying to install Heroku CLI behind proxy:
SSL_connect returned=1 errno=0 state=SSLv2/v3 read server hello A: unknown proto
col (OpenSSL::SSL::SSLError)
C:/RailsInstaller/Ruby2.2.0/lib/ruby/gems/2.2.0/gems/excon-0.51.0/lib/excon/ssl_
socket.rb:120:in connect_nonblock' C:/RailsInstaller/Ruby2.2.0/lib/ruby/gems/2.2.0/gems/excon-0.51.0/lib/excon/ssl_ socket.rb:120:in initialize'
C:/RailsInstaller/Ruby2.2.0/lib/ruby/gems/2.2.0/gems/excon-0.51.0/lib/excon/conn
ection.rb:404:in new' C:/RailsInstaller/Ruby2.2.0/lib/ruby/gems/2.2.0/gems/excon-0.51.0/lib/excon/conn ection.rb:404:in socket'
C:/RailsInstaller/Ruby2.2.0/lib/ruby/gems/2.2.0/gems/excon-0.51.0/lib/excon/conn
ection.rb:106:in request_call' C:/RailsInstaller/Ruby2.2.0/lib/ruby/gems/2.2.0/gems/excon-0.51.0/lib/excon/midd lewares/mock.rb:47:in request_call'
C:/RailsInstaller/Ruby2.2.0/lib/ruby/gems/2.2.0/gems/excon-0.51.0/lib/excon/midd
lewares/instrumentor.rb:25:in request_call' C:/RailsInstaller/Ruby2.2.0/lib/ruby/gems/2.2.0/gems/excon-0.51.0/lib/excon/midd lewares/base.rb:15:in request_call'
C:/RailsInstaller/Ruby2.2.0/lib/ruby/gems/2.2.0/gems/excon-0.51.0/lib/excon/midd
lewares/base.rb:15:in request_call' C:/RailsInstaller/Ruby2.2.0/lib/ruby/gems/2.2.0/gems/excon-0.51.0/lib/excon/midd lewares/base.rb:15:in request_call'
C:/RailsInstaller/Ruby2.2.0/lib/ruby/gems/2.2.0/gems/excon-0.51.0/lib/excon/conn
ection.rb:250:in request' C:/RailsInstaller/Ruby2.2.0/lib/ruby/gems/2.2.0/gems/excon-0.51.0/lib/excon.rb:2 38:in get'
C:/RailsInstaller/Ruby2.2.0/lib/ruby/gems/2.2.0/gems/heroku-3.43.5/lib/heroku/js
plugin.rb:246:in manifest' C:/RailsInstaller/Ruby2.2.0/lib/ruby/gems/2.2.0/gems/heroku-3.43.5/lib/heroku/js plugin.rb:259:in url'
C:/RailsInstaller/Ruby2.2.0/lib/ruby/gems/2.2.0/gems/heroku-3.43.5/lib/heroku/js
plugin.rb:149:in block (2 levels) in setup' C:/RailsInstaller/Ruby2.2.0/lib/ruby/gems/2.2.0/gems/heroku-3.43.5/lib/heroku/js plugin.rb:137:in open'
C:/RailsInstaller/Ruby2.2.0/lib/ruby/gems/2.2.0/gems/heroku-3.43.5/lib/heroku/js
plugin.rb:137:in block in setup' C:/RailsInstaller/Ruby2.2.0/lib/ruby/2.2.0/tmpdir.rb:88:in mktmpdir'
C:/RailsInstaller/Ruby2.2.0/lib/ruby/gems/2.2.0/gems/heroku-3.43.5/lib/heroku/js
plugin.rb:135:in setup' C:/RailsInstaller/Ruby2.2.0/lib/ruby/gems/2.2.0/gems/heroku-3.43.5/lib/heroku/cl i.rb:27:in start'
C:/RailsInstaller/Ruby2.2.0/lib/ruby/gems/2.2.0/gems/heroku-3.43.5/bin/heroku:24
:in <top (required)>' C:/RailsInstaller/Ruby2.2.0/bin/heroku:23:in load'
C:/RailsInstaller/Ruby2.2.0/bin/heroku:23:in `'
!    Heroku client internal error.
!    Search for help at: https://help.heroku.com
!    Or report a bug at: https://github.com/heroku/heroku/issues/new
Error:       SSL_connect returned=1 errno=0 state=SSLv2/v3 read server hello

A: unknown protocol (OpenSSL::SSL::SSLError) (Excon::Error::Socket)
Command:     heroku login
HTTP Proxy:  http://<IP_ADDRESS>:8080
HTTPS Proxy: http://<IP_ADDRESS>:8080
Version:     heroku-gem/3.43.5 (i386-mingw32) ruby/2.2.4

I have the same problem:
heroku-cli: Installing CLI...
Error: SSL_connect returned=1 errno=0 state=SSLv2/v3 read server hello A: unknown protocol (OpenSSL::SSL::SSLError)
/usr/local/heroku/vendor/gems/excon-0.51.0/lib/excon/ssl_socket.rb:120:in connect_nonblock' /usr/local/heroku/vendor/gems/excon-0.51.0/lib/excon/ssl_socket.rb:120:in initialize'
/usr/local/heroku/vendor/gems/excon-0.51.0/lib/excon/connection.rb:404:in new' /usr/local/heroku/vendor/gems/excon-0.51.0/lib/excon/connection.rb:404:in socket'
/usr/local/heroku/vendor/gems/excon-0.51.0/lib/excon/connection.rb:106:in request_call' /usr/local/heroku/vendor/gems/excon-0.51.0/lib/excon/middlewares/mock.rb:47:in request_call'
/usr/local/heroku/vendor/gems/excon-0.51.0/lib/excon/middlewares/instrumentor.rb:25:in request_call' /usr/local/heroku/vendor/gems/excon-0.51.0/lib/excon/middlewares/base.rb:15:in request_call'
/usr/local/heroku/vendor/gems/excon-0.51.0/lib/excon/middlewares/base.rb:15:in request_call' /usr/local/heroku/vendor/gems/excon-0.51.0/lib/excon/middlewares/base.rb:15:in request_call'
/usr/local/heroku/vendor/gems/excon-0.51.0/lib/excon/connection.rb:250:in request' /usr/local/heroku/vendor/gems/excon-0.51.0/lib/excon.rb:238:in get'
/usr/local/heroku/lib/heroku/jsplugin.rb:255:in manifest' /usr/local/heroku/lib/heroku/jsplugin.rb:268:in url'
/usr/local/heroku/lib/heroku/jsplugin.rb:158:in block (2 levels) in setup' /usr/local/heroku/lib/heroku/jsplugin.rb:146:in open'
/usr/local/heroku/lib/heroku/jsplugin.rb:146:in block in setup' /home/eguinosa/.rvm/rubies/ruby-2.2.5/lib/ruby/2.2.0/tmpdir.rb:88:in mktmpdir'
/usr/local/heroku/lib/heroku/jsplugin.rb:144:in setup' /usr/local/heroku/lib/heroku/cli.rb:27:in start'
/usr/local/heroku/bin/heroku:25:in `'
retrying...
Error: SSL_connect returned=1 errno=0 state=SSLv2/v3 read server hello A: unknown protocol (OpenSSL::SSL::SSLError)
/usr/local/heroku/vendor/gems/excon-0.51.0/lib/excon/ssl_socket.rb:120:in connect_nonblock' /usr/local/heroku/vendor/gems/excon-0.51.0/lib/excon/ssl_socket.rb:120:in initialize'
/usr/local/heroku/vendor/gems/excon-0.51.0/lib/excon/connection.rb:404:in new' /usr/local/heroku/vendor/gems/excon-0.51.0/lib/excon/connection.rb:404:in socket'
/usr/local/heroku/vendor/gems/excon-0.51.0/lib/excon/connection.rb:106:in request_call' /usr/local/heroku/vendor/gems/excon-0.51.0/lib/excon/middlewares/mock.rb:47:in request_call'
/usr/local/heroku/vendor/gems/excon-0.51.0/lib/excon/middlewares/instrumentor.rb:25:in request_call' /usr/local/heroku/vendor/gems/excon-0.51.0/lib/excon/middlewares/base.rb:15:in request_call'
/usr/local/heroku/vendor/gems/excon-0.51.0/lib/excon/middlewares/base.rb:15:in request_call' /usr/local/heroku/vendor/gems/excon-0.51.0/lib/excon/middlewares/base.rb:15:in request_call'
/usr/local/heroku/vendor/gems/excon-0.51.0/lib/excon/connection.rb:250:in request' /usr/local/heroku/vendor/gems/excon-0.51.0/lib/excon.rb:238:in get'
/usr/local/heroku/lib/heroku/jsplugin.rb:255:in manifest' /usr/local/heroku/lib/heroku/jsplugin.rb:268:in url'
/usr/local/heroku/lib/heroku/jsplugin.rb:158:in block (2 levels) in setup' /usr/local/heroku/lib/heroku/jsplugin.rb:146:in open'
/usr/local/heroku/lib/heroku/jsplugin.rb:146:in block in setup' /home/eguinosa/.rvm/rubies/ruby-2.2.5/lib/ruby/2.2.0/tmpdir.rb:88:in mktmpdir'
/usr/local/heroku/lib/heroku/jsplugin.rb:144:in setup' /usr/local/heroku/lib/heroku/cli.rb:27:in start'
/usr/local/heroku/bin/heroku:25:in `'
retrying...
Error: SSL_connect returned=1 errno=0 state=SSLv2/v3 read server hello A: unknown protocol (OpenSSL::SSL::SSLError)
/usr/local/heroku/vendor/gems/excon-0.51.0/lib/excon/ssl_socket.rb:120:in connect_nonblock' /usr/local/heroku/vendor/gems/excon-0.51.0/lib/excon/ssl_socket.rb:120:in initialize'
/usr/local/heroku/vendor/gems/excon-0.51.0/lib/excon/connection.rb:404:in new' /usr/local/heroku/vendor/gems/excon-0.51.0/lib/excon/connection.rb:404:in socket'
/usr/local/heroku/vendor/gems/excon-0.51.0/lib/excon/connection.rb:106:in request_call' /usr/local/heroku/vendor/gems/excon-0.51.0/lib/excon/middlewares/mock.rb:47:in request_call'
/usr/local/heroku/vendor/gems/excon-0.51.0/lib/excon/middlewares/instrumentor.rb:25:in request_call' /usr/local/heroku/vendor/gems/excon-0.51.0/lib/excon/middlewares/base.rb:15:in request_call'
/usr/local/heroku/vendor/gems/excon-0.51.0/lib/excon/middlewares/base.rb:15:in request_call' /usr/local/heroku/vendor/gems/excon-0.51.0/lib/excon/middlewares/base.rb:15:in request_call'
/usr/local/heroku/vendor/gems/excon-0.51.0/lib/excon/connection.rb:250:in request' /usr/local/heroku/vendor/gems/excon-0.51.0/lib/excon.rb:238:in get'
/usr/local/heroku/lib/heroku/jsplugin.rb:255:in manifest' /usr/local/heroku/lib/heroku/jsplugin.rb:268:in url'
/usr/local/heroku/lib/heroku/jsplugin.rb:158:in block (2 levels) in setup' /usr/local/heroku/lib/heroku/jsplugin.rb:146:in open'
/usr/local/heroku/lib/heroku/jsplugin.rb:146:in block in setup' /home/eguinosa/.rvm/rubies/ruby-2.2.5/lib/ruby/2.2.0/tmpdir.rb:88:in mktmpdir'
/usr/local/heroku/lib/heroku/jsplugin.rb:144:in setup' /usr/local/heroku/lib/heroku/cli.rb:27:in start'
/usr/local/heroku/bin/heroku:25:in `'
retrying...
Error: SSL_connect returned=1 errno=0 state=SSLv2/v3 read server hello A: unknown protocol (OpenSSL::SSL::SSLError)
/usr/local/heroku/vendor/gems/excon-0.51.0/lib/excon/ssl_socket.rb:120:in connect_nonblock' /usr/local/heroku/vendor/gems/excon-0.51.0/lib/excon/ssl_socket.rb:120:in initialize'
/usr/local/heroku/vendor/gems/excon-0.51.0/lib/excon/connection.rb:404:in new' /usr/local/heroku/vendor/gems/excon-0.51.0/lib/excon/connection.rb:404:in socket'
/usr/local/heroku/vendor/gems/excon-0.51.0/lib/excon/connection.rb:106:in request_call' /usr/local/heroku/vendor/gems/excon-0.51.0/lib/excon/middlewares/mock.rb:47:in request_call'
/usr/local/heroku/vendor/gems/excon-0.51.0/lib/excon/middlewares/instrumentor.rb:25:in request_call' /usr/local/heroku/vendor/gems/excon-0.51.0/lib/excon/middlewares/base.rb:15:in request_call'
/usr/local/heroku/vendor/gems/excon-0.51.0/lib/excon/middlewares/base.rb:15:in request_call' /usr/local/heroku/vendor/gems/excon-0.51.0/lib/excon/middlewares/base.rb:15:in request_call'
/usr/local/heroku/vendor/gems/excon-0.51.0/lib/excon/connection.rb:250:in request' /usr/local/heroku/vendor/gems/excon-0.51.0/lib/excon.rb:238:in get'
/usr/local/heroku/lib/heroku/jsplugin.rb:255:in manifest' /usr/local/heroku/lib/heroku/jsplugin.rb:268:in url'
/usr/local/heroku/lib/heroku/jsplugin.rb:158:in block (2 levels) in setup' /usr/local/heroku/lib/heroku/jsplugin.rb:146:in open'
/usr/local/heroku/lib/heroku/jsplugin.rb:146:in block in setup' /home/eguinosa/.rvm/rubies/ruby-2.2.5/lib/ruby/2.2.0/tmpdir.rb:88:in mktmpdir'
/usr/local/heroku/lib/heroku/jsplugin.rb:144:in setup' /usr/local/heroku/lib/heroku/cli.rb:27:in start'
/usr/local/heroku/bin/heroku:25:in `'
retrying...
Error: SSL_connect returned=1 errno=0 state=SSLv2/v3 read server hello A: unknown protocol (OpenSSL::SSL::SSLError)
/usr/local/heroku/vendor/gems/excon-0.51.0/lib/excon/ssl_socket.rb:120:in connect_nonblock' /usr/local/heroku/vendor/gems/excon-0.51.0/lib/excon/ssl_socket.rb:120:in initialize'
/usr/local/heroku/vendor/gems/excon-0.51.0/lib/excon/connection.rb:404:in new' /usr/local/heroku/vendor/gems/excon-0.51.0/lib/excon/connection.rb:404:in socket'
/usr/local/heroku/vendor/gems/excon-0.51.0/lib/excon/connection.rb:106:in request_call' /usr/local/heroku/vendor/gems/excon-0.51.0/lib/excon/middlewares/mock.rb:47:in request_call'
/usr/local/heroku/vendor/gems/excon-0.51.0/lib/excon/middlewares/instrumentor.rb:25:in request_call' /usr/local/heroku/vendor/gems/excon-0.51.0/lib/excon/middlewares/base.rb:15:in request_call'
/usr/local/heroku/vendor/gems/excon-0.51.0/lib/excon/middlewares/base.rb:15:in request_call' /usr/local/heroku/vendor/gems/excon-0.51.0/lib/excon/middlewares/base.rb:15:in request_call'
/usr/local/heroku/vendor/gems/excon-0.51.0/lib/excon/connection.rb:250:in request' /usr/local/heroku/vendor/gems/excon-0.51.0/lib/excon.rb:238:in get'
/usr/local/heroku/lib/heroku/jsplugin.rb:255:in manifest' /usr/local/heroku/lib/heroku/jsplugin.rb:268:in url'
/usr/local/heroku/lib/heroku/jsplugin.rb:158:in block (2 levels) in setup' /usr/local/heroku/lib/heroku/jsplugin.rb:146:in open'
/usr/local/heroku/lib/heroku/jsplugin.rb:146:in block in setup' /home/eguinosa/.rvm/rubies/ruby-2.2.5/lib/ruby/2.2.0/tmpdir.rb:88:in mktmpdir'
/usr/local/heroku/lib/heroku/jsplugin.rb:144:in setup' /usr/local/heroku/lib/heroku/cli.rb:27:in start'
/usr/local/heroku/bin/heroku:25:in `'
retrying...
SSL_connect returned=1 errno=0 state=SSLv2/v3 read server hello A: unknown protocol (OpenSSL::SSL::SSLError)
/usr/local/heroku/vendor/gems/excon-0.51.0/lib/excon/ssl_socket.rb:120:in connect_nonblock' /usr/local/heroku/vendor/gems/excon-0.51.0/lib/excon/ssl_socket.rb:120:in initialize'
/usr/local/heroku/vendor/gems/excon-0.51.0/lib/excon/connection.rb:404:in new' /usr/local/heroku/vendor/gems/excon-0.51.0/lib/excon/connection.rb:404:in socket'
/usr/local/heroku/vendor/gems/excon-0.51.0/lib/excon/connection.rb:106:in request_call' /usr/local/heroku/vendor/gems/excon-0.51.0/lib/excon/middlewares/mock.rb:47:in request_call'
/usr/local/heroku/vendor/gems/excon-0.51.0/lib/excon/middlewares/instrumentor.rb:25:in request_call' /usr/local/heroku/vendor/gems/excon-0.51.0/lib/excon/middlewares/base.rb:15:in request_call'
/usr/local/heroku/vendor/gems/excon-0.51.0/lib/excon/middlewares/base.rb:15:in request_call' /usr/local/heroku/vendor/gems/excon-0.51.0/lib/excon/middlewares/base.rb:15:in request_call'
/usr/local/heroku/vendor/gems/excon-0.51.0/lib/excon/connection.rb:250:in request' /usr/local/heroku/vendor/gems/excon-0.51.0/lib/excon.rb:238:in get'
/usr/local/heroku/lib/heroku/jsplugin.rb:255:in manifest' /usr/local/heroku/lib/heroku/jsplugin.rb:268:in url'
/usr/local/heroku/lib/heroku/jsplugin.rb:158:in block (2 levels) in setup' /usr/local/heroku/lib/heroku/jsplugin.rb:146:in open'
/usr/local/heroku/lib/heroku/jsplugin.rb:146:in block in setup' /home/eguinosa/.rvm/rubies/ruby-2.2.5/lib/ruby/2.2.0/tmpdir.rb:88:in mktmpdir'
/usr/local/heroku/lib/heroku/jsplugin.rb:144:in setup' /usr/local/heroku/lib/heroku/cli.rb:27:in start'
/usr/local/heroku/bin/heroku:25:in `'
!    Heroku client internal error.
!    Search for help at: https://help.heroku.com
!    Or report a bug at: https://github.com/heroku/heroku/issues/new
Error:       SSL_connect returned=1 errno=0 state=SSLv2/v3 read server hello A: unknown protocol (OpenSSL::SSL::SSLError) (Excon::Error::Socket)
Command:     heroku --version
HTTP Proxy:  http://user:password@proxy:port
HTTPS Proxy: http://user:password@proxy:port
Version:     heroku-toolbelt/3.43.12 (x86_64-linux) ruby/2.2.5

More information in /home/eguinosa/.heroku/error.log

Somebody knows how to solve this?????????

@eguinosa What exact version of linux are you running?  I can try and set up a VM to try and recreate.  Also any information you can give me about your network proxy would be useful, I have only tested with squid presently, and I can better match your environment that will help with debugging.
Also, it appears that you might be a ruby developer, would you feel comfortable just running the following as it may be an [issue with the upstream library] (https://github.com/excon/excon/issues/478) and I would have something simpler to submit as a bug report.  (you may have to gem install excon first)
require 'excon'

Excon.get("https://cli-assets.heroku.com/branches/stable/gz/manifest.json", expects: [200])

Hi,
Yes, I'm using Ubuntu 16.04 and I'm also a Ruby developer that's the reason
so I use heroku.
The congirutation is for my school http proxy.
I hope my information can help.
On Thu, Sep 22, 2016 at 5:19 PM, Ransom Briggs<EMAIL_ADDRESS>wrote:

@eguinosa https://github.com/eguinosa What exact version of linux are
you running? I can try and set up a VM to try and recreate. Also any
information you can give me about your network proxy would be useful, I
have only tested with squid presently, and I can better match your
environment that will help with debugging.
Also, it appears that you might be a ruby developer, would you feel
comfortable just running the following as it may be an issue with the
upstream library https://github.com/excon/excon/issues/478 and I would
have something simpler to submit as a bug report. (you may have to gem
install excon first)
require 'excon'
Excon.get("https://cli-assets.heroku.com/branches/stable/gz/manifest.json", expects: [200])
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/heroku/heroku/issues/1979#issuecomment-248901093, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AQX1uo1nV_F_KbXnvv2B5m3VbHx4Zjl3ks5qsoBrgaJpZM4JMYrw
.

@eguinosa Could you run this bit of Ruby code and paste the output?  I want to try and isolate what is causing the bug and it would help me remove a bunch of layers.   (you may have to gem install excon first)
require 'excon'
Excon.get("https://cli-assets.heroku.com/branches/stable/gz/manifest.json", expects: [200])

Here is the output:
eguinosa Documents $ cat code.rb
require 'excon'
Excon.get("https://cli-assets.heroku.com/branches/stable/gz/manifest.json",
expects: [200])
eguinosa Documents $ ruby code.rb
/home/eguinosa/.rvm/rubies/ruby-2.3.1/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in
require': cannot load such file -- excon (LoadError) from /home/eguinosa/.rvm/rubies/ruby-2.3.1/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in require'
from code.rb:1:in `'
eguinosa Documents $
On Fri, Sep 23, 2016 at 7:36 PM, Ransom Briggs<EMAIL_ADDRESS>wrote:

@eguinosa https://github.com/eguinosa Could you run this bit of Ruby
code and paste the output? I want to try and isolate what is causing the
bug and it would help me remove a bunch of layers. (you may have to gem
install excon first)
require 'excon'
Excon.get("https://cli-assets.heroku.com/branches/stable/gz/manifest.json", expects: [200])
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/heroku/heroku/issues/1979#issuecomment-249225922, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AQX1ujHOEXHVaW47OX4j-v78_8g0iS0tks5qs_IKgaJpZM4JMYrw
.

@eguinosa that error comes from excon not being installed, you need to run gem install excon first before ruby code.rb