When I try to install this package:
go get github.com/jasonnfls/goanda
I get this error:
/usr/local/go/bin/src/github.com/jasonnfls/goanda/trade.go:47: cannot use responseObj (type UpdateTradeResponse) as type OrderResponse in return argument
What would be the best way to resolve this?
Anyone have a good solution to this?
The bug in the package appears to be a copy/paste error. In the file trade.go, change the return value on line 20 from OrderResponse to UpdateTradeResponse, then run go install github.com/jasonnfls/goanda.
The file will be in your $GOPATH/src/github.com/jasonnfls/goanda
I submitted a pull request with the fix to the repo owner.
There's a bug in the package. It contains invalid code.
The solution would be to use an older version that isn't broken (if there is one), fix the bug, or get someone else (perhaps the author) to fix the bug.
Related
Because xlsx tag v1.1.0 does not contain the latest features, I use the following command to update the xlsx package to master
# go get github.com/bingoohuang/xlsx#master
Username for 'https://github.com':
Why do I still need to login to download the github public code, this does not happen when I download packages from other go get
The strange thing is that I can execute it on windows, but the above login question occurs on centos7.
what caused this to happen? I really appreciate any help with this.
It looks like github.com/bingoohuang/xlsx#master depends on github.com/bingoohuang/go-yaml, which either does not exist or is private.
Because GitHub responds with a 404 error for private repositories, it is likely this missing repository is causing go get to issue a password prompt.
A go get for a library without missing dependencies (e.g., go get github.com/rs/zerolog#master) works without a problem.
I am having this issue on specific system only(Mac mini). how can I resolve this?
You just need to comment that block of code where you are having this error.
after that you are able to make a build successfully.
For some reason most of my pages are giving this error "Call to undefined method DateTime::getTimezone()". I'm kind of positive that the pages that have this error got a ->created_at->diffForHumans() function. I still have no idea whats causing this.. It has been working fine since forever.
I tried updating my packages but there was no luck there.. Searched around for the function itself or inside my controllers.. also no luck. Checked my time zone in config/app.php and it had the same time zone that I've always had which is Asia/Amman
Check this discussion please:
https://github.com/laravel/framework/issues/24886
As it say there:
This issue is closed as it is not an issue with Laravel; it was an
issue with the PHP docs at the time, which have since been updated. I
would suggest you review your own code and make sure it's not a
namespace problem (i.e. use new \DateTime instead of new DateTime) and
if you still can't figure it out, post a question on StackOverflow
with the minimum amount of code needed to reproduce the error.
Edit:
Since this was after a Composer update, I would guess that the problem
lies with one of the packages that were updated. The error message
should give you the exact line number producing the error, which
should help you determine what package is causing the error. Then file
a bug report (or pull request) against that package if possible.
I hope it helps.
I kept changing the php version and it eventually worked. It was 7.1.22 and I changed it to 7.2.* and it worked just fine...
I cant seem to find the error log of authorize.net api.
I have Laravel application which uses "authorizenet/authorizenet" package and the code where I try to create a customer profile, I get following error:
"Error getting valid response from API. Check log file for error details"
Can anyone tell me whereto find these logs? and what it's name?
I tried in /var/logs folder but i cant seem to find it.
if someone else has this issue, here is the solution.
The authorize.net has changed their endpoints from https://api.authorize.net to https://api2.authorize.net which is one of the possible reasons that you might get this error.
So if you are hardcoding these endpoints in your code then update it to the new one or if you are using library constant for it, same as me:
\net\authorize\api\constants\ANetEnvironment::SANDBOX
\net\authorize\api\constants\ANetEnvironment::PRODUCTION
Then simply update your library by running:
composer update authorizenet/authorizenet
This is how I resolved it and it seems to be the best way so far because it will update their library to take everything up to date if they have changes something else and you started experiencing this issue.
I hope it helps
I am new to parse and I am trying to figure out how to handle the version number.
I have been deploying some cloud code a bunch of times. So when I last deployed it gave me this message:
Uploading source files
Finished uploading files
New release is named v18 (using Parse JavaScript SDK v1.2.19)
So I thought I could go and hit:
https://api.parse.com/18/functions/someFunctionIWrote
So there I tried to use version 18 because of what I saw after deploying. That does not work and it returns a 404.
So, then I tried to hit:
https://api.parse.com/1/functions/someFunctionIWrote
this works and return the JSON I wanted.
So, what am I missing here?
I thought that every time I deploy the version would match. Do I need to specifically go in and change the current version somehow?
Can somebody help understand how to think about this correctly?
Thank you
If you ran a "parse deploy" it put v18 up there for you the URL stays the same.
The version in cloud can be verified in the terminal by typing: "parse releases"