Created
February 20, 2017 17:21
-
-
Save becker1701/74357fca5d383965d26d6fe0af20b7eb to your computer and use it in GitHub Desktop.
Pry console error when calling show-method on PG::Result object
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| [1] pry(main)> require 'pg' | |
| => true | |
| [2] pry(main)> db = PG.connect(dbname: 'lesson_4') | |
| => #<PG::Connection:0x007f9701eb2950> | |
| [3] pry(main)> results = db.exec('SELECT * FROM films;') | |
| => #<PG::Result:0x007f9705bdb908 status=PGRES_TUPLES_OK ntuples=10 nfields=6 cmd_tuples=10> | |
| [4] pry(main)> results.fields | |
| => ["title", "year", "genre", "duration", "director_id", "id"] | |
| [5] pry(main)> results.values | |
| => [["Die Hard", "1988", "action", "132", "1", "1"], | |
| ["Casablanca", "1942", "drama", "102", "2", "2"], | |
| ["The Conversation", "1974", "thriller", "113", "3", "3"], | |
| ["1984", "1956", "scifi", "90", "4", "4"], | |
| ["Tinker Tailor Soldier Spy", "2011", "espionage", "127", "5", "5"], | |
| ["The Birdcage", "1996", "comedy", "118", "6", "6"], | |
| ["The Godfather", "1972", "crime", "175", "3", "7"], | |
| ["12 Angry Men", "1957", "drama", "96", "7", "8"], | |
| ["Wayne's World", "1992", "comedy", "95", "8", "9"], | |
| ["Let the Right One In", "2008", "horror", "114", "4", "10"]] | |
| [6] pry(main)> show-method results.fields | |
| Scanning and caching *.c files... | |
| [error]: Unhandled exception in YARD::Handlers::C::MixinHandler: | |
| in `/Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/pg-0.19.0/ext/pg_coder.c`:364: | |
| 364: if( nsp==rb_mPG_BinaryEncoder || nsp==rb_mPG_BinaryDecoder ) | |
| [error]: NoMethodError: undefined method `root?' for nil:NilClass | |
| [error]: Stack trace: | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/base.rb:562:in `ensure_loaded!' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/mixin_handler.rb:10:in `block (2 levels) in <class:MixinHandler>' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/mixin_handler.rb:8:in `scan' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/mixin_handler.rb:8:in `block in <class:MixinHandler>' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/processor.rb:114:in `block (2 levels) in process' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/processor.rb:112:in `each' | |
| [error]: Unhandled exception in YARD::Handlers::C::ConstantHandler: | |
| in `/Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/pg-0.19.0/ext/pg_coder.c`:367: | |
| 367: rb_define_const( coder_klass, "CFUNC", cfunc_obj ); | |
| [error]: NoMethodError: undefined method `root?' for nil:NilClass | |
| [error]: Stack trace: | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/base.rb:562:in `ensure_loaded!' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/base.rb:430:in `register_ensure_loaded' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/base.rb:410:in `block in register' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/base.rb:408:in `each' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/base.rb:408:in `register' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/handler_methods.rb:112:in `handle_constants' | |
| [warn]: The proxy PG has not yet been recognized. | |
| If this class/method is part of your source tree, this will affect your documentation results. | |
| You can correct this issue by loading the source file for this object before `/Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/pg-0.19.0/ext/pg_type_map_by_mri_type.c' | |
| [warn]: The proxy TypeMapByMriType has not yet been recognized. | |
| If this class/method is part of your source tree, this will affect your documentation results. | |
| You can correct this issue by loading the source file for this object before `/Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/pg-0.19.0/ext/pg_type_map_by_mri_type.c' | |
| [warn]: The proxy PG has not yet been recognized. | |
| If this class/method is part of your source tree, this will affect your documentation results. | |
| You can correct this issue by loading the source file for this object before `/Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/pg-0.19.0/ext/pg_type_map_all_strings.c' | |
| [warn]: The proxy PG has not yet been recognized. | |
| If this class/method is part of your source tree, this will affect your documentation results. | |
| You can correct this issue by loading the source file for this object before `/Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/pg-0.19.0/ext/pg_type_map_by_column.c' | |
| [warn]: The proxy TypeMapByColumn has not yet been recognized. | |
| If this class/method is part of your source tree, this will affect your documentation results. | |
| You can correct this issue by loading the source file for this object before `/Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/pg-0.19.0/ext/pg_type_map_by_column.c' | |
| [warn]: The proxy PG has not yet been recognized. | |
| If this class/method is part of your source tree, this will affect your documentation results. | |
| You can correct this issue by loading the source file for this object before `/Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/pg-0.19.0/ext/pg_type_map_by_class.c' | |
| [warn]: The proxy TypeMapByClass has not yet been recognized. | |
| If this class/method is part of your source tree, this will affect your documentation results. | |
| You can correct this issue by loading the source file for this object before `/Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/pg-0.19.0/ext/pg_type_map_by_class.c' | |
| [warn]: The proxy PG has not yet been recognized. | |
| If this class/method is part of your source tree, this will affect your documentation results. | |
| You can correct this issue by loading the source file for this object before `/Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/pg-0.19.0/ext/pg_type_map_in_ruby.c' | |
| [warn]: The proxy TypeMapInRuby has not yet been recognized. | |
| If this class/method is part of your source tree, this will affect your documentation results. | |
| You can correct this issue by loading the source file for this object before `/Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/pg-0.19.0/ext/pg_type_map_in_ruby.c' | |
| [warn]: The proxy PG has not yet been recognized. | |
| If this class/method is part of your source tree, this will affect your documentation results. | |
| You can correct this issue by loading the source file for this object before `/Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/pg-0.19.0/ext/pg_type_map_by_oid.c' | |
| [warn]: The proxy TypeMapByOid has not yet been recognized. | |
| If this class/method is part of your source tree, this will affect your documentation results. | |
| You can correct this issue by loading the source file for this object before `/Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/pg-0.19.0/ext/pg_type_map_by_oid.c' | |
| [warn]: The proxy PG has not yet been recognized. | |
| If this class/method is part of your source tree, this will affect your documentation results. | |
| You can correct this issue by loading the source file for this object before `/Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/pg-0.19.0/ext/pg_binary_encoder.c' | |
| [warn]: The proxy PG has not yet been recognized. | |
| If this class/method is part of your source tree, this will affect your documentation results. | |
| You can correct this issue by loading the source file for this object before `/Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/pg-0.19.0/ext/pg_binary_decoder.c' | |
| [warn]: The proxy PG has not yet been recognized. | |
| If this class/method is part of your source tree, this will affect your documentation results. | |
| You can correct this issue by loading the source file for this object before `/Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/pg-0.19.0/ext/pg_text_encoder.c' | |
| [warn]: The proxy PG has not yet been recognized. | |
| If this class/method is part of your source tree, this will affect your documentation results. | |
| You can correct this issue by loading the source file for this object before `/Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/pg-0.19.0/ext/pg_text_decoder.c' | |
| [warn]: The proxy PG has not yet been recognized. | |
| If this class/method is part of your source tree, this will affect your documentation results. | |
| You can correct this issue by loading the source file for this object before `/Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/pg-0.19.0/ext/pg_copy_coder.c' | |
| [warn]: The proxy PG has not yet been recognized. | |
| If this class/method is part of your source tree, this will affect your documentation results. | |
| You can correct this issue by loading the source file for this object before `/Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/pg-0.19.0/ext/pg_copy_coder.c' | |
| [warn]: The proxy PG has not yet been recognized. | |
| If this class/method is part of your source tree, this will affect your documentation results. | |
| You can correct this issue by loading the source file for this object before `/Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/pg-0.19.0/ext/pg_copy_coder.c' | |
| [warn]: The proxy PG has not yet been recognized. | |
| If this class/method is part of your source tree, this will affect your documentation results. | |
| You can correct this issue by loading the source file for this object before `/Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/pg-0.19.0/ext/pg_connection.c' | |
| [warn]: The proxy PGconn has not yet been recognized. | |
| If this class/method is part of your source tree, this will affect your documentation results. | |
| You can correct this issue by loading the source file for this object before `/Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/pg-0.19.0/ext/pg_connection.c' | |
| [warn]: Load Order / Name Resolution Problem on PGconn: | |
| - | |
| Something is trying to call child on object PGconn before it has been recognized. | |
| This error usually means that you need to modify the order in which you parse files | |
| so that PGconn is parsed before methods or other objects attempt to access it. | |
| - | |
| YARD will recover from this error and continue to parse but you *may* have problems | |
| with your generated documentation. You should probably fix this. | |
| - | |
| [error]: Unhandled exception in YARD::Handlers::C::AliasHandler: | |
| in `/Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/pg-0.19.0/ext/pg_connection.c`:3954: | |
| 3954: rb_define_alias(rb_cPGconn, "close", "finish"); | |
| [error]: ProxyMethodError: Proxy cannot call method #child on object 'PGconn' | |
| [error]: Stack trace: | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/code_objects/proxy.rb:189:in `rescue in method_missing' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/code_objects/proxy.rb:186:in `method_missing' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/handler_methods.rb:90:in `handle_alias' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/alias_handler.rb:13:in `block (2 levels) in <class:AliasHandler>' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/alias_handler.rb:11:in `scan' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/alias_handler.rb:11:in `block in <class:AliasHandler>' | |
| [warn]: Load Order / Name Resolution Problem on PGconn: | |
| - | |
| Something is trying to call child on object PGconn before it has been recognized. | |
| This error usually means that you need to modify the order in which you parse files | |
| so that PGconn is parsed before methods or other objects attempt to access it. | |
| - | |
| YARD will recover from this error and continue to parse but you *may* have problems | |
| with your generated documentation. You should probably fix this. | |
| - | |
| [error]: Unhandled exception in YARD::Handlers::C::AliasHandler: | |
| in `/Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/pg-0.19.0/ext/pg_connection.c`:3984: | |
| 3984: rb_define_alias(rb_cPGconn, "query", "exec"); | |
| [error]: ProxyMethodError: Proxy cannot call method #child on object 'PGconn' | |
| [error]: Stack trace: | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/code_objects/proxy.rb:189:in `rescue in method_missing' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/code_objects/proxy.rb:186:in `method_missing' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/handler_methods.rb:90:in `handle_alias' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/alias_handler.rb:13:in `block (2 levels) in <class:AliasHandler>' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/alias_handler.rb:11:in `scan' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/alias_handler.rb:11:in `block in <class:AliasHandler>' | |
| [warn]: Load Order / Name Resolution Problem on PGconn: | |
| - | |
| Something is trying to call child on object PGconn before it has been recognized. | |
| This error usually means that you need to modify the order in which you parse files | |
| so that PGconn is parsed before methods or other objects attempt to access it. | |
| - | |
| YARD will recover from this error and continue to parse but you *may* have problems | |
| with your generated documentation. You should probably fix this. | |
| - | |
| [error]: Unhandled exception in YARD::Handlers::C::AliasHandler: | |
| in `/Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/pg-0.19.0/ext/pg_connection.c`:3992: | |
| 3992: rb_define_alias(rb_cPGconn, "escape", "escape_string"); | |
| [error]: ProxyMethodError: Proxy cannot call method #child on object 'PGconn' | |
| [error]: Stack trace: | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/code_objects/proxy.rb:189:in `rescue in method_missing' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/code_objects/proxy.rb:186:in `method_missing' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/handler_methods.rb:90:in `handle_alias' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/alias_handler.rb:13:in `block (2 levels) in <class:AliasHandler>' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/alias_handler.rb:11:in `scan' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/alias_handler.rb:11:in `block in <class:AliasHandler>' | |
| [warn]: Load Order / Name Resolution Problem on PGconn: | |
| - | |
| Something is trying to call child on object PGconn before it has been recognized. | |
| This error usually means that you need to modify the order in which you parse files | |
| so that PGconn is parsed before methods or other objects attempt to access it. | |
| - | |
| YARD will recover from this error and continue to parse but you *may* have problems | |
| with your generated documentation. You should probably fix this. | |
| - | |
| [error]: Unhandled exception in YARD::Handlers::C::AliasHandler: | |
| in `/Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/pg-0.19.0/ext/pg_connection.c`:4016: | |
| 4016: rb_define_alias(rb_cPGconn, "nonblocking?", "isnonblocking"); | |
| [error]: ProxyMethodError: Proxy cannot call method #child on object 'PGconn' | |
| [error]: Stack trace: | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/code_objects/proxy.rb:189:in `rescue in method_missing' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/code_objects/proxy.rb:186:in `method_missing' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/handler_methods.rb:90:in `handle_alias' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/alias_handler.rb:13:in `block (2 levels) in <class:AliasHandler>' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/alias_handler.rb:11:in `scan' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/alias_handler.rb:11:in `block in <class:AliasHandler>' | |
| [warn]: Load Order / Name Resolution Problem on PGconn: | |
| - | |
| Something is trying to call child on object PGconn before it has been recognized. | |
| This error usually means that you need to modify the order in which you parse files | |
| so that PGconn is parsed before methods or other objects attempt to access it. | |
| - | |
| YARD will recover from this error and continue to parse but you *may* have problems | |
| with your generated documentation. You should probably fix this. | |
| - | |
| [error]: Unhandled exception in YARD::Handlers::C::AliasHandler: | |
| in `/Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/pg-0.19.0/ext/pg_connection.c`:4042: | |
| 4042: rb_define_alias(rb_cPGconn, "client_encoding=", "set_client_encoding"); | |
| [error]: ProxyMethodError: Proxy cannot call method #child on object 'PGconn' | |
| [error]: Stack trace: | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/code_objects/proxy.rb:189:in `rescue in method_missing' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/code_objects/proxy.rb:186:in `method_missing' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/handler_methods.rb:90:in `handle_alias' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/alias_handler.rb:13:in `block (2 levels) in <class:AliasHandler>' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/alias_handler.rb:11:in `scan' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/alias_handler.rb:11:in `block in <class:AliasHandler>' | |
| [warn]: Load Order / Name Resolution Problem on PGconn: | |
| - | |
| Something is trying to call child on object PGconn before it has been recognized. | |
| This error usually means that you need to modify the order in which you parse files | |
| so that PGconn is parsed before methods or other objects attempt to access it. | |
| - | |
| YARD will recover from this error and continue to parse but you *may* have problems | |
| with your generated documentation. You should probably fix this. | |
| - | |
| [error]: Unhandled exception in YARD::Handlers::C::AliasHandler: | |
| in `/Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/pg-0.19.0/ext/pg_connection.c`:4046: | |
| 4046: rb_define_alias(rb_cPGconn, "notifies_wait", "wait_for_notify"); | |
| [error]: ProxyMethodError: Proxy cannot call method #child on object 'PGconn' | |
| [error]: Stack trace: | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/code_objects/proxy.rb:189:in `rescue in method_missing' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/code_objects/proxy.rb:186:in `method_missing' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/handler_methods.rb:90:in `handle_alias' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/alias_handler.rb:13:in `block (2 levels) in <class:AliasHandler>' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/alias_handler.rb:11:in `scan' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/alias_handler.rb:11:in `block in <class:AliasHandler>' | |
| [warn]: Load Order / Name Resolution Problem on PGconn: | |
| - | |
| Something is trying to call child on object PGconn before it has been recognized. | |
| This error usually means that you need to modify the order in which you parse files | |
| so that PGconn is parsed before methods or other objects attempt to access it. | |
| - | |
| YARD will recover from this error and continue to parse but you *may* have problems | |
| with your generated documentation. You should probably fix this. | |
| - | |
| [error]: Unhandled exception in YARD::Handlers::C::AliasHandler: | |
| in `/Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/pg-0.19.0/ext/pg_connection.c`:4049: | |
| 4049: rb_define_alias(rb_cPGconn, "async_query", "async_exec"); | |
| [error]: ProxyMethodError: Proxy cannot call method #child on object 'PGconn' | |
| [error]: Stack trace: | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/code_objects/proxy.rb:189:in `rescue in method_missing' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/code_objects/proxy.rb:186:in `method_missing' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/handler_methods.rb:90:in `handle_alias' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/alias_handler.rb:13:in `block (2 levels) in <class:AliasHandler>' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/alias_handler.rb:11:in `scan' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/alias_handler.rb:11:in `block in <class:AliasHandler>' | |
| [warn]: Load Order / Name Resolution Problem on PGconn: | |
| - | |
| Something is trying to call child on object PGconn before it has been recognized. | |
| This error usually means that you need to modify the order in which you parse files | |
| so that PGconn is parsed before methods or other objects attempt to access it. | |
| - | |
| YARD will recover from this error and continue to parse but you *may* have problems | |
| with your generated documentation. You should probably fix this. | |
| - | |
| [error]: Unhandled exception in YARD::Handlers::C::AliasHandler: | |
| in `/Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/pg-0.19.0/ext/pg_connection.c`:4060: | |
| 4060: rb_define_alias(rb_cPGconn, "locreat", "lo_creat"); | |
| [error]: ProxyMethodError: Proxy cannot call method #child on object 'PGconn' | |
| [error]: Stack trace: | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/code_objects/proxy.rb:189:in `rescue in method_missing' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/code_objects/proxy.rb:186:in `method_missing' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/handler_methods.rb:90:in `handle_alias' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/alias_handler.rb:13:in `block (2 levels) in <class:AliasHandler>' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/alias_handler.rb:11:in `scan' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/alias_handler.rb:11:in `block in <class:AliasHandler>' | |
| [warn]: Load Order / Name Resolution Problem on PGconn: | |
| - | |
| Something is trying to call child on object PGconn before it has been recognized. | |
| This error usually means that you need to modify the order in which you parse files | |
| so that PGconn is parsed before methods or other objects attempt to access it. | |
| - | |
| YARD will recover from this error and continue to parse but you *may* have problems | |
| with your generated documentation. You should probably fix this. | |
| - | |
| [error]: Unhandled exception in YARD::Handlers::C::AliasHandler: | |
| in `/Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/pg-0.19.0/ext/pg_connection.c`:4062: | |
| 4062: rb_define_alias(rb_cPGconn, "locreate", "lo_create"); | |
| [error]: ProxyMethodError: Proxy cannot call method #child on object 'PGconn' | |
| [error]: Stack trace: | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/code_objects/proxy.rb:189:in `rescue in method_missing' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/code_objects/proxy.rb:186:in `method_missing' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/handler_methods.rb:90:in `handle_alias' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/alias_handler.rb:13:in `block (2 levels) in <class:AliasHandler>' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/alias_handler.rb:11:in `scan' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/alias_handler.rb:11:in `block in <class:AliasHandler>' | |
| [warn]: Load Order / Name Resolution Problem on PGconn: | |
| - | |
| Something is trying to call child on object PGconn before it has been recognized. | |
| This error usually means that you need to modify the order in which you parse files | |
| so that PGconn is parsed before methods or other objects attempt to access it. | |
| - | |
| YARD will recover from this error and continue to parse but you *may* have problems | |
| with your generated documentation. You should probably fix this. | |
| - | |
| [error]: Unhandled exception in YARD::Handlers::C::AliasHandler: | |
| in `/Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/pg-0.19.0/ext/pg_connection.c`:4064: | |
| 4064: rb_define_alias(rb_cPGconn, "loimport", "lo_import"); | |
| [error]: ProxyMethodError: Proxy cannot call method #child on object 'PGconn' | |
| [error]: Stack trace: | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/code_objects/proxy.rb:189:in `rescue in method_missing' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/code_objects/proxy.rb:186:in `method_missing' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/handler_methods.rb:90:in `handle_alias' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/alias_handler.rb:13:in `block (2 levels) in <class:AliasHandler>' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/alias_handler.rb:11:in `scan' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/alias_handler.rb:11:in `block in <class:AliasHandler>' | |
| [warn]: Load Order / Name Resolution Problem on PGconn: | |
| - | |
| Something is trying to call child on object PGconn before it has been recognized. | |
| This error usually means that you need to modify the order in which you parse files | |
| so that PGconn is parsed before methods or other objects attempt to access it. | |
| - | |
| YARD will recover from this error and continue to parse but you *may* have problems | |
| with your generated documentation. You should probably fix this. | |
| - | |
| [error]: Unhandled exception in YARD::Handlers::C::AliasHandler: | |
| in `/Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/pg-0.19.0/ext/pg_connection.c`:4066: | |
| 4066: rb_define_alias(rb_cPGconn, "loexport", "lo_export"); | |
| [error]: ProxyMethodError: Proxy cannot call method #child on object 'PGconn' | |
| [error]: Stack trace: | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/code_objects/proxy.rb:189:in `rescue in method_missing' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/code_objects/proxy.rb:186:in `method_missing' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/handler_methods.rb:90:in `handle_alias' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/alias_handler.rb:13:in `block (2 levels) in <class:AliasHandler>' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/alias_handler.rb:11:in `scan' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/alias_handler.rb:11:in `block in <class:AliasHandler>' | |
| [warn]: Load Order / Name Resolution Problem on PGconn: | |
| - | |
| Something is trying to call child on object PGconn before it has been recognized. | |
| This error usually means that you need to modify the order in which you parse files | |
| so that PGconn is parsed before methods or other objects attempt to access it. | |
| - | |
| YARD will recover from this error and continue to parse but you *may* have problems | |
| with your generated documentation. You should probably fix this. | |
| - | |
| [error]: Unhandled exception in YARD::Handlers::C::AliasHandler: | |
| in `/Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/pg-0.19.0/ext/pg_connection.c`:4068: | |
| 4068: rb_define_alias(rb_cPGconn, "loopen", "lo_open"); | |
| [error]: ProxyMethodError: Proxy cannot call method #child on object 'PGconn' | |
| [error]: Stack trace: | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/code_objects/proxy.rb:189:in `rescue in method_missing' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/code_objects/proxy.rb:186:in `method_missing' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/handler_methods.rb:90:in `handle_alias' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/alias_handler.rb:13:in `block (2 levels) in <class:AliasHandler>' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/alias_handler.rb:11:in `scan' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/alias_handler.rb:11:in `block in <class:AliasHandler>' | |
| [warn]: Load Order / Name Resolution Problem on PGconn: | |
| - | |
| Something is trying to call child on object PGconn before it has been recognized. | |
| This error usually means that you need to modify the order in which you parse files | |
| so that PGconn is parsed before methods or other objects attempt to access it. | |
| - | |
| YARD will recover from this error and continue to parse but you *may* have problems | |
| with your generated documentation. You should probably fix this. | |
| - | |
| [error]: Unhandled exception in YARD::Handlers::C::AliasHandler: | |
| in `/Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/pg-0.19.0/ext/pg_connection.c`:4070: | |
| 4070: rb_define_alias(rb_cPGconn, "lowrite", "lo_write"); | |
| [error]: ProxyMethodError: Proxy cannot call method #child on object 'PGconn' | |
| [error]: Stack trace: | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/code_objects/proxy.rb:189:in `rescue in method_missing' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/code_objects/proxy.rb:186:in `method_missing' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/handler_methods.rb:90:in `handle_alias' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/alias_handler.rb:13:in `block (2 levels) in <class:AliasHandler>' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/alias_handler.rb:11:in `scan' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/alias_handler.rb:11:in `block in <class:AliasHandler>' | |
| [warn]: Load Order / Name Resolution Problem on PGconn: | |
| - | |
| Something is trying to call child on object PGconn before it has been recognized. | |
| This error usually means that you need to modify the order in which you parse files | |
| so that PGconn is parsed before methods or other objects attempt to access it. | |
| - | |
| YARD will recover from this error and continue to parse but you *may* have problems | |
| with your generated documentation. You should probably fix this. | |
| - | |
| [error]: Unhandled exception in YARD::Handlers::C::AliasHandler: | |
| in `/Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/pg-0.19.0/ext/pg_connection.c`:4072: | |
| 4072: rb_define_alias(rb_cPGconn, "loread", "lo_read"); | |
| [error]: ProxyMethodError: Proxy cannot call method #child on object 'PGconn' | |
| [error]: Stack trace: | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/code_objects/proxy.rb:189:in `rescue in method_missing' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/code_objects/proxy.rb:186:in `method_missing' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/handler_methods.rb:90:in `handle_alias' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/alias_handler.rb:13:in `block (2 levels) in <class:AliasHandler>' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/alias_handler.rb:11:in `scan' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/alias_handler.rb:11:in `block in <class:AliasHandler>' | |
| [warn]: Load Order / Name Resolution Problem on PGconn: | |
| - | |
| Something is trying to call child on object PGconn before it has been recognized. | |
| This error usually means that you need to modify the order in which you parse files | |
| so that PGconn is parsed before methods or other objects attempt to access it. | |
| - | |
| YARD will recover from this error and continue to parse but you *may* have problems | |
| with your generated documentation. You should probably fix this. | |
| - | |
| [error]: Unhandled exception in YARD::Handlers::C::AliasHandler: | |
| in `/Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/pg-0.19.0/ext/pg_connection.c`:4074: | |
| 4074: rb_define_alias(rb_cPGconn, "lolseek", "lo_lseek"); | |
| [error]: ProxyMethodError: Proxy cannot call method #child on object 'PGconn' | |
| [error]: Stack trace: | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/code_objects/proxy.rb:189:in `rescue in method_missing' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/code_objects/proxy.rb:186:in `method_missing' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/handler_methods.rb:90:in `handle_alias' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/alias_handler.rb:13:in `block (2 levels) in <class:AliasHandler>' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/alias_handler.rb:11:in `scan' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/alias_handler.rb:11:in `block in <class:AliasHandler>' | |
| [warn]: Load Order / Name Resolution Problem on PGconn: | |
| - | |
| Something is trying to call child on object PGconn before it has been recognized. | |
| This error usually means that you need to modify the order in which you parse files | |
| so that PGconn is parsed before methods or other objects attempt to access it. | |
| - | |
| YARD will recover from this error and continue to parse but you *may* have problems | |
| with your generated documentation. You should probably fix this. | |
| - | |
| [error]: Unhandled exception in YARD::Handlers::C::AliasHandler: | |
| in `/Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/pg-0.19.0/ext/pg_connection.c`:4075: | |
| 4075: rb_define_alias(rb_cPGconn, "lo_seek", "lo_lseek"); | |
| [error]: ProxyMethodError: Proxy cannot call method #child on object 'PGconn' | |
| [error]: Stack trace: | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/code_objects/proxy.rb:189:in `rescue in method_missing' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/code_objects/proxy.rb:186:in `method_missing' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/handler_methods.rb:90:in `handle_alias' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/alias_handler.rb:13:in `block (2 levels) in <class:AliasHandler>' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/alias_handler.rb:11:in `scan' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/alias_handler.rb:11:in `block in <class:AliasHandler>' | |
| [warn]: Load Order / Name Resolution Problem on PGconn: | |
| - | |
| Something is trying to call child on object PGconn before it has been recognized. | |
| This error usually means that you need to modify the order in which you parse files | |
| so that PGconn is parsed before methods or other objects attempt to access it. | |
| - | |
| YARD will recover from this error and continue to parse but you *may* have problems | |
| with your generated documentation. You should probably fix this. | |
| - | |
| [error]: Unhandled exception in YARD::Handlers::C::AliasHandler: | |
| in `/Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/pg-0.19.0/ext/pg_connection.c`:4076: | |
| 4076: rb_define_alias(rb_cPGconn, "loseek", "lo_lseek"); | |
| [error]: ProxyMethodError: Proxy cannot call method #child on object 'PGconn' | |
| [error]: Stack trace: | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/code_objects/proxy.rb:189:in `rescue in method_missing' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/code_objects/proxy.rb:186:in `method_missing' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/handler_methods.rb:90:in `handle_alias' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/alias_handler.rb:13:in `block (2 levels) in <class:AliasHandler>' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/alias_handler.rb:11:in `scan' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/alias_handler.rb:11:in `block in <class:AliasHandler>' | |
| [warn]: Load Order / Name Resolution Problem on PGconn: | |
| - | |
| Something is trying to call child on object PGconn before it has been recognized. | |
| This error usually means that you need to modify the order in which you parse files | |
| so that PGconn is parsed before methods or other objects attempt to access it. | |
| - | |
| YARD will recover from this error and continue to parse but you *may* have problems | |
| with your generated documentation. You should probably fix this. | |
| - | |
| [error]: Unhandled exception in YARD::Handlers::C::AliasHandler: | |
| in `/Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/pg-0.19.0/ext/pg_connection.c`:4078: | |
| 4078: rb_define_alias(rb_cPGconn, "lotell", "lo_tell"); | |
| [error]: ProxyMethodError: Proxy cannot call method #child on object 'PGconn' | |
| [error]: Stack trace: | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/code_objects/proxy.rb:189:in `rescue in method_missing' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/code_objects/proxy.rb:186:in `method_missing' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/handler_methods.rb:90:in `handle_alias' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/alias_handler.rb:13:in `block (2 levels) in <class:AliasHandler>' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/alias_handler.rb:11:in `scan' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/alias_handler.rb:11:in `block in <class:AliasHandler>' | |
| [warn]: Load Order / Name Resolution Problem on PGconn: | |
| - | |
| Something is trying to call child on object PGconn before it has been recognized. | |
| This error usually means that you need to modify the order in which you parse files | |
| so that PGconn is parsed before methods or other objects attempt to access it. | |
| - | |
| YARD will recover from this error and continue to parse but you *may* have problems | |
| with your generated documentation. You should probably fix this. | |
| - | |
| [error]: Unhandled exception in YARD::Handlers::C::AliasHandler: | |
| in `/Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/pg-0.19.0/ext/pg_connection.c`:4080: | |
| 4080: rb_define_alias(rb_cPGconn, "lotruncate", "lo_truncate"); | |
| [error]: ProxyMethodError: Proxy cannot call method #child on object 'PGconn' | |
| [error]: Stack trace: | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/code_objects/proxy.rb:189:in `rescue in method_missing' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/code_objects/proxy.rb:186:in `method_missing' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/handler_methods.rb:90:in `handle_alias' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/alias_handler.rb:13:in `block (2 levels) in <class:AliasHandler>' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/alias_handler.rb:11:in `scan' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/alias_handler.rb:11:in `block in <class:AliasHandler>' | |
| [warn]: Load Order / Name Resolution Problem on PGconn: | |
| - | |
| Something is trying to call child on object PGconn before it has been recognized. | |
| This error usually means that you need to modify the order in which you parse files | |
| so that PGconn is parsed before methods or other objects attempt to access it. | |
| - | |
| YARD will recover from this error and continue to parse but you *may* have problems | |
| with your generated documentation. You should probably fix this. | |
| - | |
| [error]: Unhandled exception in YARD::Handlers::C::AliasHandler: | |
| in `/Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/pg-0.19.0/ext/pg_connection.c`:4082: | |
| 4082: rb_define_alias(rb_cPGconn, "loclose", "lo_close"); | |
| [error]: ProxyMethodError: Proxy cannot call method #child on object 'PGconn' | |
| [error]: Stack trace: | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/code_objects/proxy.rb:189:in `rescue in method_missing' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/code_objects/proxy.rb:186:in `method_missing' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/handler_methods.rb:90:in `handle_alias' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/alias_handler.rb:13:in `block (2 levels) in <class:AliasHandler>' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/alias_handler.rb:11:in `scan' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/alias_handler.rb:11:in `block in <class:AliasHandler>' | |
| [warn]: Load Order / Name Resolution Problem on PGconn: | |
| - | |
| Something is trying to call child on object PGconn before it has been recognized. | |
| This error usually means that you need to modify the order in which you parse files | |
| so that PGconn is parsed before methods or other objects attempt to access it. | |
| - | |
| YARD will recover from this error and continue to parse but you *may* have problems | |
| with your generated documentation. You should probably fix this. | |
| - | |
| [error]: Unhandled exception in YARD::Handlers::C::AliasHandler: | |
| in `/Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/pg-0.19.0/ext/pg_connection.c`:4084: | |
| 4084: rb_define_alias(rb_cPGconn, "lounlink", "lo_unlink"); | |
| [error]: ProxyMethodError: Proxy cannot call method #child on object 'PGconn' | |
| [error]: Stack trace: | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/code_objects/proxy.rb:189:in `rescue in method_missing' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/code_objects/proxy.rb:186:in `method_missing' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/handler_methods.rb:90:in `handle_alias' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/alias_handler.rb:13:in `block (2 levels) in <class:AliasHandler>' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/alias_handler.rb:11:in `scan' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/alias_handler.rb:11:in `block in <class:AliasHandler>' | |
| [warn]: The proxy PG has not yet been recognized. | |
| If this class/method is part of your source tree, this will affect your documentation results. | |
| You can correct this issue by loading the source file for this object before `/Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/pg-0.19.0/ext/pg_type_map.c' | |
| [warn]: The proxy TypeMap has not yet been recognized. | |
| If this class/method is part of your source tree, this will affect your documentation results. | |
| You can correct this issue by loading the source file for this object before `/Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/pg-0.19.0/ext/pg_type_map.c' | |
| [warn]: The proxy PG has not yet been recognized. | |
| If this class/method is part of your source tree, this will affect your documentation results. | |
| You can correct this issue by loading the source file for this object before `/Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/pg-0.19.0/ext/pg_result.c' | |
| [warn]: The proxy PGresult has not yet been recognized. | |
| If this class/method is part of your source tree, this will affect your documentation results. | |
| You can correct this issue by loading the source file for this object before `/Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/pg-0.19.0/ext/pg_result.c' | |
| [warn]: The proxy PGresult has not yet been recognized. | |
| If this class/method is part of your source tree, this will affect your documentation results. | |
| You can correct this issue by loading the source file for this object before `/Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/pg-0.19.0/ext/pg_result.c' | |
| [warn]: Load Order / Name Resolution Problem on PGresult: | |
| - | |
| Something is trying to call child on object PGresult before it has been recognized. | |
| This error usually means that you need to modify the order in which you parse files | |
| so that PGresult is parsed before methods or other objects attempt to access it. | |
| - | |
| YARD will recover from this error and continue to parse but you *may* have problems | |
| with your generated documentation. You should probably fix this. | |
| - | |
| [error]: Unhandled exception in YARD::Handlers::C::AliasHandler: | |
| in `/Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/pg-0.19.0/ext/pg_result.c`:1222: | |
| 1222: rb_define_alias( rb_cPGresult, "result_error_message", "error_message"); | |
| [error]: ProxyMethodError: Proxy cannot call method #child on object 'PGresult' | |
| [error]: Stack trace: | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/code_objects/proxy.rb:189:in `rescue in method_missing' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/code_objects/proxy.rb:186:in `method_missing' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/handler_methods.rb:90:in `handle_alias' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/alias_handler.rb:13:in `block (2 levels) in <class:AliasHandler>' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/alias_handler.rb:11:in `scan' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/alias_handler.rb:11:in `block in <class:AliasHandler>' | |
| [warn]: Load Order / Name Resolution Problem on PGresult: | |
| - | |
| Something is trying to call child on object PGresult before it has been recognized. | |
| This error usually means that you need to modify the order in which you parse files | |
| so that PGresult is parsed before methods or other objects attempt to access it. | |
| - | |
| YARD will recover from this error and continue to parse but you *may* have problems | |
| with your generated documentation. You should probably fix this. | |
| - | |
| [error]: Unhandled exception in YARD::Handlers::C::AliasHandler: | |
| in `/Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/pg-0.19.0/ext/pg_result.c`:1224: | |
| 1224: rb_define_alias( rb_cPGresult, "result_error_field", "error_field" ); | |
| [error]: ProxyMethodError: Proxy cannot call method #child on object 'PGresult' | |
| [error]: Stack trace: | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/code_objects/proxy.rb:189:in `rescue in method_missing' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/code_objects/proxy.rb:186:in `method_missing' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/handler_methods.rb:90:in `handle_alias' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/alias_handler.rb:13:in `block (2 levels) in <class:AliasHandler>' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/alias_handler.rb:11:in `scan' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/alias_handler.rb:11:in `block in <class:AliasHandler>' | |
| [warn]: Load Order / Name Resolution Problem on PGresult: | |
| - | |
| Something is trying to call child on object PGresult before it has been recognized. | |
| This error usually means that you need to modify the order in which you parse files | |
| so that PGresult is parsed before methods or other objects attempt to access it. | |
| - | |
| YARD will recover from this error and continue to parse but you *may* have problems | |
| with your generated documentation. You should probably fix this. | |
| - | |
| [error]: Unhandled exception in YARD::Handlers::C::AliasHandler: | |
| in `/Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/pg-0.19.0/ext/pg_result.c`:1227: | |
| 1227: rb_define_alias (rb_cPGresult, "check_result", "check"); | |
| [error]: ProxyMethodError: Proxy cannot call method #child on object 'PGresult' | |
| [error]: Stack trace: | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/code_objects/proxy.rb:189:in `rescue in method_missing' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/code_objects/proxy.rb:186:in `method_missing' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/handler_methods.rb:90:in `handle_alias' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/alias_handler.rb:13:in `block (2 levels) in <class:AliasHandler>' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/alias_handler.rb:11:in `scan' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/alias_handler.rb:11:in `block in <class:AliasHandler>' | |
| [warn]: Load Order / Name Resolution Problem on PGresult: | |
| - | |
| Something is trying to call child on object PGresult before it has been recognized. | |
| This error usually means that you need to modify the order in which you parse files | |
| so that PGresult is parsed before methods or other objects attempt to access it. | |
| - | |
| YARD will recover from this error and continue to parse but you *may* have problems | |
| with your generated documentation. You should probably fix this. | |
| - | |
| [error]: Unhandled exception in YARD::Handlers::C::AliasHandler: | |
| in `/Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/pg-0.19.0/ext/pg_result.c`:1229: | |
| 1229: rb_define_alias(rb_cPGresult, "num_tuples", "ntuples"); | |
| [error]: ProxyMethodError: Proxy cannot call method #child on object 'PGresult' | |
| [error]: Stack trace: | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/code_objects/proxy.rb:189:in `rescue in method_missing' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/code_objects/proxy.rb:186:in `method_missing' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/handler_methods.rb:90:in `handle_alias' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/alias_handler.rb:13:in `block (2 levels) in <class:AliasHandler>' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/alias_handler.rb:11:in `scan' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/alias_handler.rb:11:in `block in <class:AliasHandler>' | |
| [warn]: Load Order / Name Resolution Problem on PGresult: | |
| - | |
| Something is trying to call child on object PGresult before it has been recognized. | |
| This error usually means that you need to modify the order in which you parse files | |
| so that PGresult is parsed before methods or other objects attempt to access it. | |
| - | |
| YARD will recover from this error and continue to parse but you *may* have problems | |
| with your generated documentation. You should probably fix this. | |
| - | |
| [error]: Unhandled exception in YARD::Handlers::C::AliasHandler: | |
| in `/Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/pg-0.19.0/ext/pg_result.c`:1231: | |
| 1231: rb_define_alias(rb_cPGresult, "num_fields", "nfields"); | |
| [error]: ProxyMethodError: Proxy cannot call method #child on object 'PGresult' | |
| [error]: Stack trace: | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/code_objects/proxy.rb:189:in `rescue in method_missing' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/code_objects/proxy.rb:186:in `method_missing' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/handler_methods.rb:90:in `handle_alias' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/alias_handler.rb:13:in `block (2 levels) in <class:AliasHandler>' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/alias_handler.rb:11:in `scan' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/alias_handler.rb:11:in `block in <class:AliasHandler>' | |
| [warn]: Load Order / Name Resolution Problem on PGresult: | |
| - | |
| Something is trying to call child on object PGresult before it has been recognized. | |
| This error usually means that you need to modify the order in which you parse files | |
| so that PGresult is parsed before methods or other objects attempt to access it. | |
| - | |
| YARD will recover from this error and continue to parse but you *may* have problems | |
| with your generated documentation. You should probably fix this. | |
| - | |
| [error]: Unhandled exception in YARD::Handlers::C::AliasHandler: | |
| in `/Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/pg-0.19.0/ext/pg_result.c`:1247: | |
| 1247: rb_define_alias(rb_cPGresult, "cmdtuples", "cmd_tuples"); | |
| [error]: ProxyMethodError: Proxy cannot call method #child on object 'PGresult' | |
| [error]: Stack trace: | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/code_objects/proxy.rb:189:in `rescue in method_missing' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/code_objects/proxy.rb:186:in `method_missing' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/handler_methods.rb:90:in `handle_alias' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/alias_handler.rb:13:in `block (2 levels) in <class:AliasHandler>' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/alias_handler.rb:11:in `scan' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/alias_handler.rb:11:in `block in <class:AliasHandler>' | |
| [warn]: The proxy PG has not yet been recognized. | |
| If this class/method is part of your source tree, this will affect your documentation results. | |
| You can correct this issue by loading the source file for this object before `/Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/pg-0.19.0/ext/pg_errors.c' | |
| [warn]: Load Order / Name Resolution Problem on PGerror: | |
| - | |
| Something is trying to call child on object PGerror before it has been recognized. | |
| This error usually means that you need to modify the order in which you parse files | |
| so that PGerror is parsed before methods or other objects attempt to access it. | |
| - | |
| YARD will recover from this error and continue to parse but you *may* have problems | |
| with your generated documentation. You should probably fix this. | |
| - | |
| [error]: Unhandled exception in YARD::Handlers::C::AliasHandler: | |
| in `/Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/pg-0.19.0/ext/pg_errors.c`:83: | |
| 83: rb_define_alias( rb_ePGerror, "error", "message" ); | |
| [error]: ProxyMethodError: Proxy cannot call method #child on object 'PGerror' | |
| [error]: Stack trace: | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/code_objects/proxy.rb:189:in `rescue in method_missing' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/code_objects/proxy.rb:186:in `method_missing' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/handler_methods.rb:90:in `handle_alias' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/alias_handler.rb:13:in `block (2 levels) in <class:AliasHandler>' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/alias_handler.rb:11:in `scan' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/alias_handler.rb:11:in `block in <class:AliasHandler>' | |
| [warn]: Load Order / Name Resolution Problem on PGerror: | |
| - | |
| Something is trying to call attributes on object PGerror before it has been recognized. | |
| This error usually means that you need to modify the order in which you parse files | |
| so that PGerror is parsed before methods or other objects attempt to access it. | |
| - | |
| YARD will recover from this error and continue to parse but you *may* have problems | |
| with your generated documentation. You should probably fix this. | |
| - | |
| [error]: Unhandled exception in YARD::Handlers::C::AttributeHandler: | |
| in `/Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/pg-0.19.0/ext/pg_errors.c`:84: | |
| 84: rb_define_attr( rb_ePGerror, "connection", 1, 0 ); | |
| [error]: ProxyMethodError: Proxy cannot call method #attributes on object 'PGerror' | |
| [error]: Stack trace: | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/code_objects/proxy.rb:189:in `rescue in method_missing' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/code_objects/proxy.rb:186:in `method_missing' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/handler_methods.rb:80:in `block in handle_attribute' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/handler_methods.rb:76:in `each' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/handler_methods.rb:76:in `handle_attribute' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/attribute_handler.rb:10:in `block (2 levels) in <class:AttributeHandler>' | |
| [warn]: Load Order / Name Resolution Problem on PGerror: | |
| - | |
| Something is trying to call attributes on object PGerror before it has been recognized. | |
| This error usually means that you need to modify the order in which you parse files | |
| so that PGerror is parsed before methods or other objects attempt to access it. | |
| - | |
| YARD will recover from this error and continue to parse but you *may* have problems | |
| with your generated documentation. You should probably fix this. | |
| - | |
| [error]: Unhandled exception in YARD::Handlers::C::AttributeHandler: | |
| in `/Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/pg-0.19.0/ext/pg_errors.c`:85: | |
| 85: rb_define_attr( rb_ePGerror, "result", 1, 0 ); | |
| [error]: ProxyMethodError: Proxy cannot call method #attributes on object 'PGerror' | |
| [error]: Stack trace: | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/code_objects/proxy.rb:189:in `rescue in method_missing' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/code_objects/proxy.rb:186:in `method_missing' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/handler_methods.rb:80:in `block in handle_attribute' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/handler_methods.rb:76:in `each' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/handler_methods.rb:76:in `handle_attribute' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/attribute_handler.rb:10:in `block (2 levels) in <class:AttributeHandler>' | |
| [warn]: The proxy PG has not yet been recognized. | |
| If this class/method is part of your source tree, this will affect your documentation results. | |
| You can correct this issue by loading the source file for this object before `/Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/pg-0.19.0/ext/pg_errors.c' | |
| [warn]: The proxy PG has not yet been recognized. | |
| If this class/method is part of your source tree, this will affect your documentation results. | |
| You can correct this issue by loading the source file for this object before `/Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/pg-0.19.0/ext/pg_errors.c' | |
| [warn]: The proxy PG has not yet been recognized. | |
| If this class/method is part of your source tree, this will affect your documentation results. | |
| You can correct this issue by loading the source file for this object before `/Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/pg-0.19.0/ext/pg_errors.c' | |
| [warn]: The proxy PG has not yet been recognized. | |
| If this class/method is part of your source tree, this will affect your documentation results. | |
| You can correct this issue by loading the source file for this object before `/Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/pg-0.19.0/ext/pg_errors.c' | |
| [warn]: The proxy PG has not yet been recognized. | |
| If this class/method is part of your source tree, this will affect your documentation results. | |
| You can correct this issue by loading the source file for this object before `/Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/pg-0.19.0/ext/pg_errors.c' | |
| [warn]: The proxy PG has not yet been recognized. | |
| If this class/method is part of your source tree, this will affect your documentation results. | |
| You can correct this issue by loading the source file for this object before `/Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/pg-0.19.0/ext/pg_errors.c' | |
| [warn]: The proxy PG has not yet been recognized. | |
| If this class/method is part of your source tree, this will affect your documentation results. | |
| You can correct this issue by loading the source file for this object before `/Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/pg-0.19.0/ext/pg_coder.c' | |
| [warn]: Load Order / Name Resolution Problem on PG_Coder: | |
| - | |
| Something is trying to call attributes on object PG_Coder before it has been recognized. | |
| This error usually means that you need to modify the order in which you parse files | |
| so that PG_Coder is parsed before methods or other objects attempt to access it. | |
| - | |
| YARD will recover from this error and continue to parse but you *may* have problems | |
| with your generated documentation. You should probably fix this. | |
| - | |
| [error]: Unhandled exception in YARD::Handlers::C::AttributeHandler: | |
| in `/Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/pg-0.19.0/ext/pg_coder.c`:465: | |
| 465: rb_define_attr( rb_cPG_Coder, "name", 1, 1 ); | |
| [error]: ProxyMethodError: Proxy cannot call method #attributes on object 'PG_Coder' | |
| [error]: Stack trace: | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/code_objects/proxy.rb:189:in `rescue in method_missing' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/code_objects/proxy.rb:186:in `method_missing' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/handler_methods.rb:80:in `block in handle_attribute' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/handler_methods.rb:76:in `each' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/handler_methods.rb:76:in `handle_attribute' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/attribute_handler.rb:10:in `block (2 levels) in <class:AttributeHandler>' | |
| [warn]: The proxy PG has not yet been recognized. | |
| If this class/method is part of your source tree, this will affect your documentation results. | |
| You can correct this issue by loading the source file for this object before `/Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/pg-0.19.0/ext/pg_coder.c' | |
| [warn]: The proxy PG has not yet been recognized. | |
| If this class/method is part of your source tree, this will affect your documentation results. | |
| You can correct this issue by loading the source file for this object before `/Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/pg-0.19.0/ext/pg_coder.c' | |
| [warn]: The proxy PG has not yet been recognized. | |
| If this class/method is part of your source tree, this will affect your documentation results. | |
| You can correct this issue by loading the source file for this object before `/Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/pg-0.19.0/ext/pg_coder.c' | |
| [warn]: The proxy PG has not yet been recognized. | |
| If this class/method is part of your source tree, this will affect your documentation results. | |
| You can correct this issue by loading the source file for this object before `/Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/pg-0.19.0/ext/pg_coder.c' | |
| [warn]: Load Order / Name Resolution Problem on PG_CompositeCoder: | |
| - | |
| Something is trying to call attributes on object PG_CompositeCoder before it has been recognized. | |
| This error usually means that you need to modify the order in which you parse files | |
| so that PG_CompositeCoder is parsed before methods or other objects attempt to access it. | |
| - | |
| YARD will recover from this error and continue to parse but you *may* have problems | |
| with your generated documentation. You should probably fix this. | |
| - | |
| [error]: Unhandled exception in YARD::Handlers::C::AttributeHandler: | |
| in `/Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/pg-0.19.0/ext/pg_coder.c`:486: | |
| 486: rb_define_attr( rb_cPG_CompositeCoder, "elements_type", 1, 0 ); | |
| [error]: ProxyMethodError: Proxy cannot call method #attributes on object 'PG_CompositeCoder' | |
| [error]: Stack trace: | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/code_objects/proxy.rb:189:in `rescue in method_missing' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/code_objects/proxy.rb:186:in `method_missing' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/handler_methods.rb:80:in `block in handle_attribute' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/handler_methods.rb:76:in `each' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/handler_methods.rb:76:in `handle_attribute' | |
| /Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/yard-0.9.8/lib/yard/handlers/c/attribute_handler.rb:10:in `block (2 levels) in <class:AttributeHandler>' | |
| [warn]: The proxy PG has not yet been recognized. | |
| If this class/method is part of your source tree, this will affect your documentation results. | |
| You can correct this issue by loading the source file for this object before `/Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/pg-0.19.0/ext/pg_coder.c' | |
| [warn]: The proxy PG has not yet been recognized. | |
| If this class/method is part of your source tree, this will affect your documentation results. | |
| You can correct this issue by loading the source file for this object before `/Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/pg-0.19.0/ext/pg_coder.c' | |
| [warn]: The proxy PG_Coder has not yet been recognized. | |
| If this class/method is part of your source tree, this will affect your documentation results. | |
| You can correct this issue by loading the source file for this object before `/Users/MX-2000/.rvm/gems/ruby-2.3.1/gems/pg-0.19.0/ext/pg_coder.c' | |
| Error: Cannot locate this method: fields. (source_location returns nil) | |
| [7] pry(main)> |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment