git - BitBucket cannot push, "fatal: The remote end hung up unexpectedly" -


when trying push new bitbucket repository, keep getting error: 

counting objects: 28, done. delta compression using 4 threads. compressing objects: 100% (28/28), done. writing objects: 100% (28/28), 10.82 mib | 7.29 mib/s, done. total 28 (delta 1), reused 0 (delta 0) error: rpc failed; curl 56 ssl read: error:140943fc:ssl routines:ssl3_read_bytes:sslv3 alert bad record mac, errno 0 fatal: remote end hung unexpectedly fatal: remote end hung unexpectedly up-to-date

i same error in sourcetree well. tried messing config file increase buffer size shown below:

git config --global http.postbuffer 524288000

i don't want use ssh on windows 10 without server use ssh from. rather push command prompt. should note folders able push repository others not.

wondering do. noticed there post issue here, wanted state case have tried of these no avail. looking here. i'm pushing simple bootstrap website.

i don't want use ssh on windows 10 without server use ssh from

you still push through ssh though: git windows has openssh included in distro. maybe server not have right use ssh outbound transaction? know cannot use ssh on server in company.

check if issue persists, there recent incident report atlassian bitbucket affecting git via https.
"bad record mac" ssl error "message authentication code", , suggests upgrade of ssl library on server side (as part of incident resolution).
make sure use latest git widows 2.8.3.


-

Comments

Post a Comment

Popular posts from this blog

scala - 'wrong top statement declaration' when using slick in IntelliJ -

Image
i'm porting project scala 2.9 2.10, therefore have use slick instead of scalaquery. i'm using slick 2.1.0 since supports ms access. according this tutorial , upgrade guide changed robs object class , added val robs : why error message wrong top statement declaration , how rid of it? edit: i'm new scala... according this question seems can't put val outside of methods or classes, right? code above directly in packge. right approach slick then? should move code in class or trait? according this changed val robs = tablequery[robs] to object robs extends tablequery(new robs(_)) {} . no warnings or errors anymore. :)
Read more

c# - DevExpress.Wpf.Grid.InfiniteGridSizeException was unhandled -

Image
when using devexpress, see error: devexpress.wpf.grid.infinitegridsizeexception unhandled message="by default, infinite grid height not allowed since grid rows rendered , hence grid work slowly. fix issue, should place grid container give finite height grid, or should manually specify grid's height or maxheight. note can avoid exception setting gridcontrol.allowinfinitegridsize static property true, in case grid run slowly." the problem dxgrid has infinite height. to fix, set height non-infinite. snoop absolutely invaluable this: if "height" xaml element infinite (i.e. 0 or nan ), can set using one of following: option 1: height="{binding path=actualheight, relativesource={relativesource mode=findancestor, ancestortype=uielement}}" option 2: verticalalignment="stretch" option 3: height="auto" hint: use verticalalignment="stretch" if child of grid <rowdefinition height=
Read more

PySide and Qt Properties: Connecting signals from Python to QML -

i trying run simple pyside appliccation design made in qml. call function in qml python in separated thread. i have following qml view: import qt 4.7 rectangle { visible: true width: 100; height: 100 color: "lightgrey" text { id: datestr objectname: "datestr" x: 10 y: 10 text: "init text" font.pixelsize: 12 function updatedata(text) { datestr.text = qstr(text) console.log("you said: " + text) } } } here application: some imports.... #!/usr/bin/python import sys import time pyside import qtdeclarative, qtcore pyside.qtgui import qapplication pyside.qtdeclarative import qdeclarativeview the qthread worker.... #worker thread class worker(qtcore.qthread): updateprogress = qtcore.signal(int) def __init__(self, child): qtcore.qthread.__init__(self) self.child = child def run(self):
Read more