Were you ever able to figure out the reason?

I am having the same issue.

On Thursday, June 13, 2013 4:24:21 AM UTC-4, Arif Nadeem wrote:
>
> These are the logs from production.log file
>
>
>    1. 
>    
>    Started GET 
>    "/api/v3/projects/:id/repository/tree?private_token=my_private_token&id=4" 
>    for at 2013-06-13 12:48:36 +0530
>    2. 
>    
>    3. 
>    
>    ActionController::RoutingError (No route matches [GET] 
>    "/api/v3/projects/:id/repository/tree"):
>    4. 
>    
>    
> vendor/bundle/ruby/1.9.1/gems/actionpack-3.2.13/lib/action_dispatch/middleware/debug_exceptions.rb:21:in
>  
>    `call'
>    5. 
>    
>    
> vendor/bundle/ruby/1.9.1/gems/actionpack-3.2.13/lib/action_dispatch/middleware/show_exceptions.rb:56:in
>  
>    `call'
>    6. 
>    
>    
> vendor/bundle/ruby/1.9.1/gems/railties-3.2.13/lib/rails/rack/logger.rb:32:in 
>    `call_app'
>    7. 
>    
>    
> vendor/bundle/ruby/1.9.1/gems/railties-3.2.13/lib/rails/rack/logger.rb:16:in 
>    `block in call'
>    8. 
>    
>    
> vendor/bundle/ruby/1.9.1/gems/activesupport-3.2.13/lib/active_support/tagged_logging.rb:22:in
>  
>    `tagged'
>    9. 
>    
>    
> vendor/bundle/ruby/1.9.1/gems/railties-3.2.13/lib/rails/rack/logger.rb:16:in 
>    `call'
>    10. 
>    
>    
> vendor/bundle/ruby/1.9.1/gems/actionpack-3.2.13/lib/action_dispatch/middleware/request_id.rb:22:in
>  
>    `call'
>    11. 
>    
>    vendor/bundle/ruby/1.9.1/gems/rack-1.4.5/lib/rack/methodoverride.rb:21:in 
>    `call'
>    12. 
>    
>    vendor/bundle/ruby/1.9.1/gems/rack-1.4.5/lib/rack/runtime.rb:17:in 
>    `call'
>    13. 
>    
>    vendor/bundle/ruby/1.9.1/gems/rack-1.4.5/lib/rack/lock.rb:15:in `call'
>    14. 
>    
>    
> vendor/bundle/ruby/1.9.1/gems/rack-cache-1.2/lib/rack/cache/context.rb:136:in 
>    `forward'
>    15. 
>    
>    
> vendor/bundle/ruby/1.9.1/gems/rack-cache-1.2/lib/rack/cache/context.rb:245:in 
>    `fetch'
>    16. 
>    
>    
> vendor/bundle/ruby/1.9.1/gems/rack-cache-1.2/lib/rack/cache/context.rb:185:in 
>    `lookup'
>    17. 
>    
>    
> vendor/bundle/ruby/1.9.1/gems/rack-cache-1.2/lib/rack/cache/context.rb:66:in 
>    `call!'
>    18. 
>    
>    
> vendor/bundle/ruby/1.9.1/gems/rack-cache-1.2/lib/rack/cache/context.rb:51:in 
>    `call'
>    19. 
>    
>    vendor/bundle/ruby/1.9.1/gems/railties-3.2.13/lib/rails/engine.rb:479:in 
>    `call'
>    20. 
>    
>    
> vendor/bundle/ruby/1.9.1/gems/railties-3.2.13/lib/rails/application.rb:223:in 
>    `call'
>    21. 
>    
>    
> vendor/bundle/ruby/1.9.1/gems/railties-3.2.13/lib/rails/railtie/configurable.rb:30:in
>  
>    `method_missing'
>    22. 
>    
>    vendor/bundle/ruby/1.9.1/gems/rack-1.4.5/lib/rack/builder.rb:134:in 
>    `call'
>    23. 
>    
>    vendor/bundle/ruby/1.9.1/gems/rack-1.4.5/lib/rack/urlmap.rb:64:in 
>    `block in call'
>    24. 
>    
>    vendor/bundle/ruby/1.9.1/gems/rack-1.4.5/lib/rack/urlmap.rb:49:in 
>    `each'
>    25. 
>    
>    vendor/bundle/ruby/1.9.1/gems/rack-1.4.5/lib/rack/urlmap.rb:49:in 
>    `call'
>    26. 
>    
>    vendor/bundle/ruby/1.9.1/gems/puma-2.0.1/lib/puma/configuration.rb:66:in 
>    `call'
>    27. 
>    
>    vendor/bundle/ruby/1.9.1/gems/puma-2.0.1/lib/puma/server.rb:364:in 
>    `handle_request'
>    28. 
>    
>    vendor/bundle/ruby/1.9.1/gems/puma-2.0.1/lib/puma/server.rb:243:in 
>    `process_client'
>    29. 
>    
>    vendor/bundle/ruby/1.9.1/gems/puma-2.0.1/lib/puma/server.rb:142:in 
>    `block in run'
>    30. 
>    
>    vendor/bundle/ruby/1.9.1/gems/puma-2.0.1/lib/puma/thread_pool.rb:92:in 
>    `call'
>    31. 
>    
>    vendor/bundle/ruby/1.9.1/gems/puma-2.0.1/lib/puma/thread_pool.rb:92:in 
>    `block in spawn_thread'
>    
>
> On Thursday, June 13, 2013 1:43:23 PM UTC+5:30, Arif Nadeem wrote:
>>
>> According to GitLabs API documentation to get a repository tree via 
>> restful api call I should do the following, this excerpt is from the 
>> documentation which can be found 
>> here<http://api.gitlab.org/repositories.html>, 
>> it says that
>>
>> List repository tree
>>
>> Get a list of repository files and directories in a project.
>>
>> GET /projects/:id/repository/tree Parameters:
>>
>> id (required) - The ID of a project
>>
>> path (optional) - The path inside repository. Used to get contend of 
>> subdirectories
>>
>> ref_name (optional)-The name of a repository branch or tag or if not 
>> given the default branch
>>
>> But when I do call to the above web service it returns
>>
>> 404 The page you were looking for doesn't exist.
>>
>> I call 
>> http://myserverurl/api/v3/projects/:id/repository/tree?private_token=myprivatetoken
>>  and 
>> I get 404, of-course I pass the id of the project here which is an integer 
>> like 4, 5, 6 etc.
>>
>> All the other API's work fine except for this one, is there something I 
>> am missing here?
>>
>>
>> I am able to call GET /projects/:id/repository/branches, the moment I 
>> append /tree to the url, it returns 404. Also the project tree is not 
>> empty. 
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"GitLab" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to gitlabhq+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to