Skip to content
This repository has been archived by the owner on Aug 16, 2019. It is now read-only.

POST results in ERROR: no method pointer(ASCIIString,) #7

Closed
mlimotte opened this issue Apr 15, 2014 · 10 comments
Closed

POST results in ERROR: no method pointer(ASCIIString,) #7

mlimotte opened this issue Apr 15, 2014 · 10 comments

Comments

@mlimotte
Copy link

This is reproducible in the repl (Julia 0.2.1):

$ exec '/Applications/Julia-0.2.1.app/Contents/Resources/julia/bin/julia'
_
_ _ ()_ | A fresh approach to technical computing
() | () () | Documentation: http://docs.julialang.org
_ _ | | __ _ | Type "help()" to list help topics
| | | | | | |/ ` | |
| | |
| | | | (
| | | Version 0.2.1 (2014-02-11 06:30 UTC)
/ |_'|||__'| | Official http://julialang.org/ release
|__/ | x86_64-apple-darwin12.5.0

julia> using HTTPClient.HTTPC
julia> result = HTTPC.post("http://localhost:9999/foo/bar","foo")
ERROR: no method pointer(ASCIIString,)
in _put_post at /Users/marc/.julia/v0.2/HTTPClient/src/HTTPC.jl:480
in put_post at /Users/marc/.julia/v0.2/HTTPClient/src/HTTPC.jl:454
in post at /Users/marc/.julia/v0.2/HTTPClient/src/HTTPC.jl:388

@amitmurthy
Copy link
Contributor

This was due to a 0.3 dependency. Have updated METADATA accordingly. You can try removing and adding HTTPClient again (after a Pkg.update() i.e.).

Closing the issue, Do reopen if the problem is not solved.

@mlimotte
Copy link
Author

Hmm, update fails like this:

_julia> _Pkg.update()

INFO: Updating METADATA...

INFO: Updating DataFrames...

INFO: Computing changes...

WARNING: julia is fixed at 0.2.1 conflicting with requirement for
HTTPClient: [0.3.0-,∞)

INFO: Removing Stats v0.1.0

On Wed, Apr 16, 2014 at 5:12 AM, Amit Murthy notifications@github.comwrote:

This was due to a 0.3 dependency. Have updated METADATA accordingly. You
can try removing and adding HTTPClient again (after a Pkg.update() i.e.).

Closing the issue, Do reopen if the problem is not solved.


Reply to this email directly or view it on GitHubhttps://github.com//issues/7#issuecomment-40578387
.

@amitmurthy
Copy link
Contributor

OK. That was just a warning. Now, can you do a Pkg.rm("HTTPClient") followed by Pkg.add("HTTPClient")

@mlimotte
Copy link
Author

Ok. I'm still seeing the same issue, though. Where is your change? In
github, it looks like the last commit on master is from March 25th:

https://github.com/amitmurthy/HTTPClient.jl/commits/master

On Thu, Apr 17, 2014 at 11:29 AM, Amit Murthy notifications@github.comwrote:

OK. That was just a warning. Now, can you do a Pkg.rm("HTTPClient")followed by
Pkg.add("HTTPClient")


Reply to this email directly or view it on GitHubhttps://github.com//issues/7#issuecomment-40727083
.

@amitmurthy
Copy link
Contributor

The change is in METADATA - JuliaLang/METADATA.jl@976fe64 where I specifically marked dependency of the latest HTTPCient on julia version 0.3

The latest HTTPClient that can work with julia 0.2 is the previous version, i.e., JuliaLang/METADATA.jl@f714311

@amitmurthy
Copy link
Contributor

So, once you tried re-installing HTTPClient, I expected the package manager to get the previous version of HTTPClient which is compatible with julia 0.2

@amitmurthy
Copy link
Contributor

What does Pkg.resolve() display?

@mlimotte
Copy link
Author

Interesting. I was able to get the 0.1.0 pkg installed, but I had to do
Pkg.rm("HTTPClient") twice. The first time, it removed it from "Required
packages", but as shown here, the "0.1.1" pkg was still listed under
"Additional packages".

julia> Pkg.status()
Required packages:

  • DataFrames 0.4.2
  • JSON 0.3.5
  • Stats 0.1.0
    Additional packages:
  • Blocks 0.0.2
  • DataArrays 0.0.2
  • GZip 0.2.12
  • HTTPClient 0.1.1 master
  • LibCURL 0.1.1
  • SortingAlgorithms 0.0.1
  • StatsBase 0.2.10

After doing the Pkg.rm statement again, and then add, I finally had 0.1.0.

marc

On Thu, Apr 17, 2014 at 12:04 PM, Amit Murthy notifications@github.comwrote:

What does Pkg.resolve() display?


Reply to this email directly or view it on GitHubhttps://github.com//issues/7#issuecomment-40731054
.

@amitmurthy
Copy link
Contributor

Cool! You should not be seeing those errors on a HTTP POST now.

@mlimotte
Copy link
Author

Yes. Confirmed that POST works now.

On Thu, Apr 17, 2014 at 12:19 PM, Amit Murthy notifications@github.comwrote:

Cool! You should not be seeing those errors on a HTTP POST now.


Reply to this email directly or view it on GitHubhttps://github.com//issues/7#issuecomment-40732809
.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants