API tools faq
paste
Advertisement
Guest User

Untitled

a guest
May 24th, 2017
72
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 60.88 KB | None | 0 0
raw download clone embed print report
  1. [7] pry(main)> show-method result.values
  2. Scanning and caching *.c files...
  3. [error]: Unhandled exception in YARD::Handlers::C::MixinHandler:
  4. in `C:/Ruby23/lib/ruby/gems/2.3.0/gems/pg-0.20.0-x86-mingw32/ext/pg_coder.c`:364:
  5.  
  6. 364: if( nsp==rb_mPG_BinaryEncoder || nsp==rb_mPG_BinaryDecoder )
  7.  
  8. [error]: NoMethodError: undefined method `root?' for nil:NilClass
  9. [error]: Stack trace:
  10. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/base.rb:562:in `ensure_loaded!'
  11. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/mixin_handler.rb:10:in `block (2 levels) in <class:MixinHandler>'
  12. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/mixin_handler.rb:8:in `scan'
  13. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/mixin_handler.rb:8:in `block in <class:MixinHandler>'
  14. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/processor.rb:114:in `block (2 levels) in process'
  15. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/processor.rb:112:in `each'
  16.  
  17. [error]: Unhandled exception in YARD::Handlers::C::ConstantHandler:
  18. in `C:/Ruby23/lib/ruby/gems/2.3.0/gems/pg-0.20.0-x86-mingw32/ext/pg_coder.c`:367:
  19.  
  20. 367: rb_define_const( coder_klass, "CFUNC", cfunc_obj );
  21.  
  22. [error]: NoMethodError: undefined method `root?' for nil:NilClass
  23. [error]: Stack trace:
  24. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/base.rb:562:in `ensure_loaded!'
  25. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/base.rb:430:in `register_ensure_loaded'
  26. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/base.rb:410:in `block in register'
  27. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/base.rb:408:in `each'
  28. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/base.rb:408:in `register'
  29. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/handler_methods.rb:112:in `handle_constants'
  30.  
  31. [warn]: The proxy PG has not yet been recognized.
  32. If this class/method is part of your source tree, this will affect your documentation results.
  33. You can correct this issue by loading the source file for this object before `C:/Ruby23/lib/ruby/gems/2.3.0/gems/pg-0.20.0-x86-mingw32/ext/pg_type_map_by_mri_type.c'
  34.  
  35. [warn]: The proxy TypeMapByMriType has not yet been recognized.
  36. If this class/method is part of your source tree, this will affect your documentation results.
  37. You can correct this issue by loading the source file for this object before `C:/Ruby23/lib/ruby/gems/2.3.0/gems/pg-0.20.0-x86-mingw32/ext/pg_type_map_by_mri_type.c'
  38.  
  39. [warn]: The proxy PG has not yet been recognized.
  40. If this class/method is part of your source tree, this will affect your documentation results.
  41. You can correct this issue by loading the source file for this object before `C:/Ruby23/lib/ruby/gems/2.3.0/gems/pg-0.20.0-x86-mingw32/ext/pg_type_map_all_strings.c'
  42.  
  43. [warn]: The proxy PG has not yet been recognized.
  44. If this class/method is part of your source tree, this will affect your documentation results.
  45. You can correct this issue by loading the source file for this object before `C:/Ruby23/lib/ruby/gems/2.3.0/gems/pg-0.20.0-x86-mingw32/ext/pg_type_map_by_column.c'
  46.  
  47. [warn]: The proxy TypeMapByColumn has not yet been recognized.
  48. If this class/method is part of your source tree, this will affect your documentation results.
  49. You can correct this issue by loading the source file for this object before `C:/Ruby23/lib/ruby/gems/2.3.0/gems/pg-0.20.0-x86-mingw32/ext/pg_type_map_by_column.c'
  50.  
  51. [warn]: The proxy PG has not yet been recognized.
  52. If this class/method is part of your source tree, this will affect your documentation results.
  53. You can correct this issue by loading the source file for this object before `C:/Ruby23/lib/ruby/gems/2.3.0/gems/pg-0.20.0-x86-mingw32/ext/pg_type_map_by_class.c'
  54.  
  55. [warn]: The proxy TypeMapByClass has not yet been recognized.
  56. If this class/method is part of your source tree, this will affect your documentation results.
  57. You can correct this issue by loading the source file for this object before `C:/Ruby23/lib/ruby/gems/2.3.0/gems/pg-0.20.0-x86-mingw32/ext/pg_type_map_by_class.c'
  58.  
  59. [warn]: The proxy PG has not yet been recognized.
  60. If this class/method is part of your source tree, this will affect your documentation results.
  61. You can correct this issue by loading the source file for this object before `C:/Ruby23/lib/ruby/gems/2.3.0/gems/pg-0.20.0-x86-mingw32/ext/pg_type_map_in_ruby.c'
  62.  
  63. [warn]: The proxy TypeMapInRuby has not yet been recognized.
  64. If this class/method is part of your source tree, this will affect your documentation results.
  65. You can correct this issue by loading the source file for this object before `C:/Ruby23/lib/ruby/gems/2.3.0/gems/pg-0.20.0-x86-mingw32/ext/pg_type_map_in_ruby.c'
  66.  
  67. [warn]: The proxy PG has not yet been recognized.
  68. If this class/method is part of your source tree, this will affect your documentation results.
  69. You can correct this issue by loading the source file for this object before `C:/Ruby23/lib/ruby/gems/2.3.0/gems/pg-0.20.0-x86-mingw32/ext/pg_type_map_by_oid.c'
  70.  
  71. [warn]: The proxy TypeMapByOid has not yet been recognized.
  72. If this class/method is part of your source tree, this will affect your documentation results.
  73. You can correct this issue by loading the source file for this object before `C:/Ruby23/lib/ruby/gems/2.3.0/gems/pg-0.20.0-x86-mingw32/ext/pg_type_map_by_oid.c'
  74.  
  75. [warn]: The proxy PG has not yet been recognized.
  76. If this class/method is part of your source tree, this will affect your documentation results.
  77. You can correct this issue by loading the source file for this object before `C:/Ruby23/lib/ruby/gems/2.3.0/gems/pg-0.20.0-x86-mingw32/ext/pg_binary_encoder.c'
  78.  
  79. [warn]: The proxy PG has not yet been recognized.
  80. If this class/method is part of your source tree, this will affect your documentation results.
  81. You can correct this issue by loading the source file for this object before `C:/Ruby23/lib/ruby/gems/2.3.0/gems/pg-0.20.0-x86-mingw32/ext/pg_binary_decoder.c'
  82.  
  83. [warn]: The proxy PG has not yet been recognized.
  84. If this class/method is part of your source tree, this will affect your documentation results.
  85. You can correct this issue by loading the source file for this object before `C:/Ruby23/lib/ruby/gems/2.3.0/gems/pg-0.20.0-x86-mingw32/ext/pg_text_encoder.c'
  86.  
  87. [warn]: The proxy PG has not yet been recognized.
  88. If this class/method is part of your source tree, this will affect your documentation results.
  89. You can correct this issue by loading the source file for this object before `C:/Ruby23/lib/ruby/gems/2.3.0/gems/pg-0.20.0-x86-mingw32/ext/pg_text_decoder.c'
  90.  
  91. [warn]: The proxy PG has not yet been recognized.
  92. If this class/method is part of your source tree, this will affect your documentation results.
  93. You can correct this issue by loading the source file for this object before `C:/Ruby23/lib/ruby/gems/2.3.0/gems/pg-0.20.0-x86-mingw32/ext/pg_copy_coder.c'
  94.  
  95. [warn]: The proxy PG has not yet been recognized.
  96. If this class/method is part of your source tree, this will affect your documentation results.
  97. You can correct this issue by loading the source file for this object before `C:/Ruby23/lib/ruby/gems/2.3.0/gems/pg-0.20.0-x86-mingw32/ext/pg_copy_coder.c'
  98.  
  99. [warn]: The proxy PG has not yet been recognized.
  100. If this class/method is part of your source tree, this will affect your documentation results.
  101. You can correct this issue by loading the source file for this object before `C:/Ruby23/lib/ruby/gems/2.3.0/gems/pg-0.20.0-x86-mingw32/ext/pg_copy_coder.c'
  102.  
  103. [warn]: The proxy PG has not yet been recognized.
  104. If this class/method is part of your source tree, this will affect your documentation results.
  105. You can correct this issue by loading the source file for this object before `C:/Ruby23/lib/ruby/gems/2.3.0/gems/pg-0.20.0-x86-mingw32/ext/pg_connection.c'
  106.  
  107. [warn]: The proxy PGconn has not yet been recognized.
  108. If this class/method is part of your source tree, this will affect your documentation results.
  109. You can correct this issue by loading the source file for this object before `C:/Ruby23/lib/ruby/gems/2.3.0/gems/pg-0.20.0-x86-mingw32/ext/pg_connection.c'
  110.  
  111. [warn]: Load Order / Name Resolution Problem on PGconn:
  112. -
  113. Something is trying to call child on object PGconn before it has been recognized.
  114. This error usually means that you need to modify the order in which you parse files
  115. so that PGconn is parsed before methods or other objects attempt to access it.
  116. -
  117. YARD will recover from this error and continue to parse but you *may* have problems
  118. with your generated documentation. You should probably fix this.
  119. -
  120.  
  121. [error]: Unhandled exception in YARD::Handlers::C::AliasHandler:
  122. in `C:/Ruby23/lib/ruby/gems/2.3.0/gems/pg-0.20.0-x86-mingw32/ext/pg_connection.c`:3954:
  123.  
  124. 3954: rb_define_alias(rb_cPGconn, "close", "finish");
  125.  
  126. [error]: ProxyMethodError: Proxy cannot call method #child on object 'PGconn'
  127. [error]: Stack trace:
  128. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/code_objects/proxy.rb:189:in `rescue in method_missing'
  129. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/code_objects/proxy.rb:186:in `method_missing'
  130. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/handler_methods.rb:90:in `handle_alias'
  131. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/alias_handler.rb:13:in `block (2 levels) in <class:AliasHandler>'
  132. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/alias_handler.rb:11:in `scan'
  133. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/alias_handler.rb:11:in `block in <class:AliasHandler>'
  134.  
  135. [warn]: Load Order / Name Resolution Problem on PGconn:
  136. -
  137. Something is trying to call child on object PGconn before it has been recognized.
  138. This error usually means that you need to modify the order in which you parse files
  139. so that PGconn is parsed before methods or other objects attempt to access it.
  140. -
  141. YARD will recover from this error and continue to parse but you *may* have problems
  142. with your generated documentation. You should probably fix this.
  143. -
  144.  
  145. [error]: Unhandled exception in YARD::Handlers::C::AliasHandler:
  146. in `C:/Ruby23/lib/ruby/gems/2.3.0/gems/pg-0.20.0-x86-mingw32/ext/pg_connection.c`:3984:
  147.  
  148. 3984: rb_define_alias(rb_cPGconn, "query", "exec");
  149.  
  150. [error]: ProxyMethodError: Proxy cannot call method #child on object 'PGconn'
  151. [error]: Stack trace:
  152. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/code_objects/proxy.rb:189:in `rescue in method_missing'
  153. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/code_objects/proxy.rb:186:in `method_missing'
  154. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/handler_methods.rb:90:in `handle_alias'
  155. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/alias_handler.rb:13:in `block (2 levels) in <class:AliasHandler>'
  156. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/alias_handler.rb:11:in `scan'
  157. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/alias_handler.rb:11:in `block in <class:AliasHandler>'
  158.  
  159. [warn]: Load Order / Name Resolution Problem on PGconn:
  160. -
  161. Something is trying to call child on object PGconn before it has been recognized.
  162. This error usually means that you need to modify the order in which you parse files
  163. so that PGconn is parsed before methods or other objects attempt to access it.
  164. -
  165. YARD will recover from this error and continue to parse but you *may* have problems
  166. with your generated documentation. You should probably fix this.
  167. -
  168.  
  169. [error]: Unhandled exception in YARD::Handlers::C::AliasHandler:
  170. in `C:/Ruby23/lib/ruby/gems/2.3.0/gems/pg-0.20.0-x86-mingw32/ext/pg_connection.c`:3992:
  171.  
  172. 3992: rb_define_alias(rb_cPGconn, "escape", "escape_string");
  173.  
  174. [error]: ProxyMethodError: Proxy cannot call method #child on object 'PGconn'
  175. [error]: Stack trace:
  176. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/code_objects/proxy.rb:189:in `rescue in method_missing'
  177. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/code_objects/proxy.rb:186:in `method_missing'
  178. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/handler_methods.rb:90:in `handle_alias'
  179. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/alias_handler.rb:13:in `block (2 levels) in <class:AliasHandler>'
  180. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/alias_handler.rb:11:in `scan'
  181. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/alias_handler.rb:11:in `block in <class:AliasHandler>'
  182.  
  183. [warn]: Load Order / Name Resolution Problem on PGconn:
  184. -
  185. Something is trying to call child on object PGconn before it has been recognized.
  186. This error usually means that you need to modify the order in which you parse files
  187. so that PGconn is parsed before methods or other objects attempt to access it.
  188. -
  189. YARD will recover from this error and continue to parse but you *may* have problems
  190. with your generated documentation. You should probably fix this.
  191. -
  192.  
  193. [error]: Unhandled exception in YARD::Handlers::C::AliasHandler:
  194. in `C:/Ruby23/lib/ruby/gems/2.3.0/gems/pg-0.20.0-x86-mingw32/ext/pg_connection.c`:4016:
  195.  
  196. 4016: rb_define_alias(rb_cPGconn, "nonblocking?", "isnonblocking");
  197.  
  198. [error]: ProxyMethodError: Proxy cannot call method #child on object 'PGconn'
  199. [error]: Stack trace:
  200. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/code_objects/proxy.rb:189:in `rescue in method_missing'
  201. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/code_objects/proxy.rb:186:in `method_missing'
  202. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/handler_methods.rb:90:in `handle_alias'
  203. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/alias_handler.rb:13:in `block (2 levels) in <class:AliasHandler>'
  204. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/alias_handler.rb:11:in `scan'
  205. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/alias_handler.rb:11:in `block in <class:AliasHandler>'
  206.  
  207. [warn]: Load Order / Name Resolution Problem on PGconn:
  208. -
  209. Something is trying to call child on object PGconn before it has been recognized.
  210. This error usually means that you need to modify the order in which you parse files
  211. so that PGconn is parsed before methods or other objects attempt to access it.
  212. -
  213. YARD will recover from this error and continue to parse but you *may* have problems
  214. with your generated documentation. You should probably fix this.
  215. -
  216.  
  217. [error]: Unhandled exception in YARD::Handlers::C::AliasHandler:
  218. in `C:/Ruby23/lib/ruby/gems/2.3.0/gems/pg-0.20.0-x86-mingw32/ext/pg_connection.c`:4042:
  219.  
  220. 4042: rb_define_alias(rb_cPGconn, "client_encoding=", "set_client_encoding");
  221.  
  222. [error]: ProxyMethodError: Proxy cannot call method #child on object 'PGconn'
  223. [error]: Stack trace:
  224. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/code_objects/proxy.rb:189:in `rescue in method_missing'
  225. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/code_objects/proxy.rb:186:in `method_missing'
  226. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/handler_methods.rb:90:in `handle_alias'
  227. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/alias_handler.rb:13:in `block (2 levels) in <class:AliasHandler>'
  228. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/alias_handler.rb:11:in `scan'
  229. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/alias_handler.rb:11:in `block in <class:AliasHandler>'
  230.  
  231. [warn]: Load Order / Name Resolution Problem on PGconn:
  232. -
  233. Something is trying to call child on object PGconn before it has been recognized.
  234. This error usually means that you need to modify the order in which you parse files
  235. so that PGconn is parsed before methods or other objects attempt to access it.
  236. -
  237. YARD will recover from this error and continue to parse but you *may* have problems
  238. with your generated documentation. You should probably fix this.
  239. -
  240.  
  241. [error]: Unhandled exception in YARD::Handlers::C::AliasHandler:
  242. in `C:/Ruby23/lib/ruby/gems/2.3.0/gems/pg-0.20.0-x86-mingw32/ext/pg_connection.c`:4046:
  243.  
  244. 4046: rb_define_alias(rb_cPGconn, "notifies_wait", "wait_for_notify");
  245.  
  246. [error]: ProxyMethodError: Proxy cannot call method #child on object 'PGconn'
  247. [error]: Stack trace:
  248. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/code_objects/proxy.rb:189:in `rescue in method_missing'
  249. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/code_objects/proxy.rb:186:in `method_missing'
  250. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/handler_methods.rb:90:in `handle_alias'
  251. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/alias_handler.rb:13:in `block (2 levels) in <class:AliasHandler>'
  252. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/alias_handler.rb:11:in `scan'
  253. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/alias_handler.rb:11:in `block in <class:AliasHandler>'
  254.  
  255. [warn]: Load Order / Name Resolution Problem on PGconn:
  256. -
  257. Something is trying to call child on object PGconn before it has been recognized.
  258. This error usually means that you need to modify the order in which you parse files
  259. so that PGconn is parsed before methods or other objects attempt to access it.
  260. -
  261. YARD will recover from this error and continue to parse but you *may* have problems
  262. with your generated documentation. You should probably fix this.
  263. -
  264.  
  265. [error]: Unhandled exception in YARD::Handlers::C::AliasHandler:
  266. in `C:/Ruby23/lib/ruby/gems/2.3.0/gems/pg-0.20.0-x86-mingw32/ext/pg_connection.c`:4049:
  267.  
  268. 4049: rb_define_alias(rb_cPGconn, "async_query", "async_exec");
  269.  
  270. [error]: ProxyMethodError: Proxy cannot call method #child on object 'PGconn'
  271. [error]: Stack trace:
  272. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/code_objects/proxy.rb:189:in `rescue in method_missing'
  273. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/code_objects/proxy.rb:186:in `method_missing'
  274. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/handler_methods.rb:90:in `handle_alias'
  275. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/alias_handler.rb:13:in `block (2 levels) in <class:AliasHandler>'
  276. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/alias_handler.rb:11:in `scan'
  277. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/alias_handler.rb:11:in `block in <class:AliasHandler>'
  278.  
  279. [warn]: Load Order / Name Resolution Problem on PGconn:
  280. -
  281. Something is trying to call child on object PGconn before it has been recognized.
  282. This error usually means that you need to modify the order in which you parse files
  283. so that PGconn is parsed before methods or other objects attempt to access it.
  284. -
  285. YARD will recover from this error and continue to parse but you *may* have problems
  286. with your generated documentation. You should probably fix this.
  287. -
  288.  
  289. [error]: Unhandled exception in YARD::Handlers::C::AliasHandler:
  290. in `C:/Ruby23/lib/ruby/gems/2.3.0/gems/pg-0.20.0-x86-mingw32/ext/pg_connection.c`:4060:
  291.  
  292. 4060: rb_define_alias(rb_cPGconn, "locreat", "lo_creat");
  293.  
  294. [error]: ProxyMethodError: Proxy cannot call method #child on object 'PGconn'
  295. [error]: Stack trace:
  296. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/code_objects/proxy.rb:189:in `rescue in method_missing'
  297. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/code_objects/proxy.rb:186:in `method_missing'
  298. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/handler_methods.rb:90:in `handle_alias'
  299. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/alias_handler.rb:13:in `block (2 levels) in <class:AliasHandler>'
  300. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/alias_handler.rb:11:in `scan'
  301. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/alias_handler.rb:11:in `block in <class:AliasHandler>'
  302.  
  303. [warn]: Load Order / Name Resolution Problem on PGconn:
  304. -
  305. Something is trying to call child on object PGconn before it has been recognized.
  306. This error usually means that you need to modify the order in which you parse files
  307. so that PGconn is parsed before methods or other objects attempt to access it.
  308. -
  309. YARD will recover from this error and continue to parse but you *may* have problems
  310. with your generated documentation. You should probably fix this.
  311. -
  312.  
  313. [error]: Unhandled exception in YARD::Handlers::C::AliasHandler:
  314. in `C:/Ruby23/lib/ruby/gems/2.3.0/gems/pg-0.20.0-x86-mingw32/ext/pg_connection.c`:4062:
  315.  
  316. 4062: rb_define_alias(rb_cPGconn, "locreate", "lo_create");
  317.  
  318. [error]: ProxyMethodError: Proxy cannot call method #child on object 'PGconn'
  319. [error]: Stack trace:
  320. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/code_objects/proxy.rb:189:in `rescue in method_missing'
  321. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/code_objects/proxy.rb:186:in `method_missing'
  322. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/handler_methods.rb:90:in `handle_alias'
  323. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/alias_handler.rb:13:in `block (2 levels) in <class:AliasHandler>'
  324. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/alias_handler.rb:11:in `scan'
  325. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/alias_handler.rb:11:in `block in <class:AliasHandler>'
  326.  
  327. [warn]: Load Order / Name Resolution Problem on PGconn:
  328. -
  329. Something is trying to call child on object PGconn before it has been recognized.
  330. This error usually means that you need to modify the order in which you parse files
  331. so that PGconn is parsed before methods or other objects attempt to access it.
  332. -
  333. YARD will recover from this error and continue to parse but you *may* have problems
  334. with your generated documentation. You should probably fix this.
  335. -
  336.  
  337. [error]: Unhandled exception in YARD::Handlers::C::AliasHandler:
  338. in `C:/Ruby23/lib/ruby/gems/2.3.0/gems/pg-0.20.0-x86-mingw32/ext/pg_connection.c`:4064:
  339.  
  340. 4064: rb_define_alias(rb_cPGconn, "loimport", "lo_import");
  341.  
  342. [error]: ProxyMethodError: Proxy cannot call method #child on object 'PGconn'
  343. [error]: Stack trace:
  344. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/code_objects/proxy.rb:189:in `rescue in method_missing'
  345. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/code_objects/proxy.rb:186:in `method_missing'
  346. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/handler_methods.rb:90:in `handle_alias'
  347. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/alias_handler.rb:13:in `block (2 levels) in <class:AliasHandler>'
  348. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/alias_handler.rb:11:in `scan'
  349. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/alias_handler.rb:11:in `block in <class:AliasHandler>'
  350.  
  351. [warn]: Load Order / Name Resolution Problem on PGconn:
  352. -
  353. Something is trying to call child on object PGconn before it has been recognized.
  354. This error usually means that you need to modify the order in which you parse files
  355. so that PGconn is parsed before methods or other objects attempt to access it.
  356. -
  357. YARD will recover from this error and continue to parse but you *may* have problems
  358. with your generated documentation. You should probably fix this.
  359. -
  360.  
  361. [error]: Unhandled exception in YARD::Handlers::C::AliasHandler:
  362. in `C:/Ruby23/lib/ruby/gems/2.3.0/gems/pg-0.20.0-x86-mingw32/ext/pg_connection.c`:4066:
  363.  
  364. 4066: rb_define_alias(rb_cPGconn, "loexport", "lo_export");
  365.  
  366. [error]: ProxyMethodError: Proxy cannot call method #child on object 'PGconn'
  367. [error]: Stack trace:
  368. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/code_objects/proxy.rb:189:in `rescue in method_missing'
  369. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/code_objects/proxy.rb:186:in `method_missing'
  370. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/handler_methods.rb:90:in `handle_alias'
  371. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/alias_handler.rb:13:in `block (2 levels) in <class:AliasHandler>'
  372. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/alias_handler.rb:11:in `scan'
  373. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/alias_handler.rb:11:in `block in <class:AliasHandler>'
  374.  
  375. [warn]: Load Order / Name Resolution Problem on PGconn:
  376. -
  377. Something is trying to call child on object PGconn before it has been recognized.
  378. This error usually means that you need to modify the order in which you parse files
  379. so that PGconn is parsed before methods or other objects attempt to access it.
  380. -
  381. YARD will recover from this error and continue to parse but you *may* have problems
  382. with your generated documentation. You should probably fix this.
  383. -
  384.  
  385. [error]: Unhandled exception in YARD::Handlers::C::AliasHandler:
  386. in `C:/Ruby23/lib/ruby/gems/2.3.0/gems/pg-0.20.0-x86-mingw32/ext/pg_connection.c`:4068:
  387.  
  388. 4068: rb_define_alias(rb_cPGconn, "loopen", "lo_open");
  389.  
  390. [error]: ProxyMethodError: Proxy cannot call method #child on object 'PGconn'
  391. [error]: Stack trace:
  392. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/code_objects/proxy.rb:189:in `rescue in method_missing'
  393. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/code_objects/proxy.rb:186:in `method_missing'
  394. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/handler_methods.rb:90:in `handle_alias'
  395. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/alias_handler.rb:13:in `block (2 levels) in <class:AliasHandler>'
  396. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/alias_handler.rb:11:in `scan'
  397. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/alias_handler.rb:11:in `block in <class:AliasHandler>'
  398.  
  399. [warn]: Load Order / Name Resolution Problem on PGconn:
  400. -
  401. Something is trying to call child on object PGconn before it has been recognized.
  402. This error usually means that you need to modify the order in which you parse files
  403. so that PGconn is parsed before methods or other objects attempt to access it.
  404. -
  405. YARD will recover from this error and continue to parse but you *may* have problems
  406. with your generated documentation. You should probably fix this.
  407. -
  408.  
  409. [error]: Unhandled exception in YARD::Handlers::C::AliasHandler:
  410. in `C:/Ruby23/lib/ruby/gems/2.3.0/gems/pg-0.20.0-x86-mingw32/ext/pg_connection.c`:4070:
  411.  
  412. 4070: rb_define_alias(rb_cPGconn, "lowrite", "lo_write");
  413.  
  414. [error]: ProxyMethodError: Proxy cannot call method #child on object 'PGconn'
  415. [error]: Stack trace:
  416. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/code_objects/proxy.rb:189:in `rescue in method_missing'
  417. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/code_objects/proxy.rb:186:in `method_missing'
  418. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/handler_methods.rb:90:in `handle_alias'
  419. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/alias_handler.rb:13:in `block (2 levels) in <class:AliasHandler>'
  420. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/alias_handler.rb:11:in `scan'
  421. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/alias_handler.rb:11:in `block in <class:AliasHandler>'
  422.  
  423. [warn]: Load Order / Name Resolution Problem on PGconn:
  424. -
  425. Something is trying to call child on object PGconn before it has been recognized.
  426. This error usually means that you need to modify the order in which you parse files
  427. so that PGconn is parsed before methods or other objects attempt to access it.
  428. -
  429. YARD will recover from this error and continue to parse but you *may* have problems
  430. with your generated documentation. You should probably fix this.
  431. -
  432.  
  433. [error]: Unhandled exception in YARD::Handlers::C::AliasHandler:
  434. in `C:/Ruby23/lib/ruby/gems/2.3.0/gems/pg-0.20.0-x86-mingw32/ext/pg_connection.c`:4072:
  435.  
  436. 4072: rb_define_alias(rb_cPGconn, "loread", "lo_read");
  437.  
  438. [error]: ProxyMethodError: Proxy cannot call method #child on object 'PGconn'
  439. [error]: Stack trace:
  440. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/code_objects/proxy.rb:189:in `rescue in method_missing'
  441. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/code_objects/proxy.rb:186:in `method_missing'
  442. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/handler_methods.rb:90:in `handle_alias'
  443. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/alias_handler.rb:13:in `block (2 levels) in <class:AliasHandler>'
  444. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/alias_handler.rb:11:in `scan'
  445. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/alias_handler.rb:11:in `block in <class:AliasHandler>'
  446.  
  447. [warn]: Load Order / Name Resolution Problem on PGconn:
  448. -
  449. Something is trying to call child on object PGconn before it has been recognized.
  450. This error usually means that you need to modify the order in which you parse files
  451. so that PGconn is parsed before methods or other objects attempt to access it.
  452. -
  453. YARD will recover from this error and continue to parse but you *may* have problems
  454. with your generated documentation. You should probably fix this.
  455. -
  456.  
  457. [error]: Unhandled exception in YARD::Handlers::C::AliasHandler:
  458. in `C:/Ruby23/lib/ruby/gems/2.3.0/gems/pg-0.20.0-x86-mingw32/ext/pg_connection.c`:4074:
  459.  
  460. 4074: rb_define_alias(rb_cPGconn, "lolseek", "lo_lseek");
  461.  
  462. [error]: ProxyMethodError: Proxy cannot call method #child on object 'PGconn'
  463. [error]: Stack trace:
  464. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/code_objects/proxy.rb:189:in `rescue in method_missing'
  465. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/code_objects/proxy.rb:186:in `method_missing'
  466. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/handler_methods.rb:90:in `handle_alias'
  467. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/alias_handler.rb:13:in `block (2 levels) in <class:AliasHandler>'
  468. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/alias_handler.rb:11:in `scan'
  469. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/alias_handler.rb:11:in `block in <class:AliasHandler>'
  470.  
  471. [warn]: Load Order / Name Resolution Problem on PGconn:
  472. -
  473. Something is trying to call child on object PGconn before it has been recognized.
  474. This error usually means that you need to modify the order in which you parse files
  475. so that PGconn is parsed before methods or other objects attempt to access it.
  476. -
  477. YARD will recover from this error and continue to parse but you *may* have problems
  478. with your generated documentation. You should probably fix this.
  479. -
  480.  
  481. [error]: Unhandled exception in YARD::Handlers::C::AliasHandler:
  482. in `C:/Ruby23/lib/ruby/gems/2.3.0/gems/pg-0.20.0-x86-mingw32/ext/pg_connection.c`:4075:
  483.  
  484. 4075: rb_define_alias(rb_cPGconn, "lo_seek", "lo_lseek");
  485.  
  486. [error]: ProxyMethodError: Proxy cannot call method #child on object 'PGconn'
  487. [error]: Stack trace:
  488. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/code_objects/proxy.rb:189:in `rescue in method_missing'
  489. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/code_objects/proxy.rb:186:in `method_missing'
  490. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/handler_methods.rb:90:in `handle_alias'
  491. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/alias_handler.rb:13:in `block (2 levels) in <class:AliasHandler>'
  492. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/alias_handler.rb:11:in `scan'
  493. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/alias_handler.rb:11:in `block in <class:AliasHandler>'
  494.  
  495. [warn]: Load Order / Name Resolution Problem on PGconn:
  496. -
  497. Something is trying to call child on object PGconn before it has been recognized.
  498. This error usually means that you need to modify the order in which you parse files
  499. so that PGconn is parsed before methods or other objects attempt to access it.
  500. -
  501. YARD will recover from this error and continue to parse but you *may* have problems
  502. with your generated documentation. You should probably fix this.
  503. -
  504.  
  505. [error]: Unhandled exception in YARD::Handlers::C::AliasHandler:
  506. in `C:/Ruby23/lib/ruby/gems/2.3.0/gems/pg-0.20.0-x86-mingw32/ext/pg_connection.c`:4076:
  507.  
  508. 4076: rb_define_alias(rb_cPGconn, "loseek", "lo_lseek");
  509.  
  510. [error]: ProxyMethodError: Proxy cannot call method #child on object 'PGconn'
  511. [error]: Stack trace:
  512. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/code_objects/proxy.rb:189:in `rescue in method_missing'
  513. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/code_objects/proxy.rb:186:in `method_missing'
  514. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/handler_methods.rb:90:in `handle_alias'
  515. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/alias_handler.rb:13:in `block (2 levels) in <class:AliasHandler>'
  516. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/alias_handler.rb:11:in `scan'
  517. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/alias_handler.rb:11:in `block in <class:AliasHandler>'
  518.  
  519. [warn]: Load Order / Name Resolution Problem on PGconn:
  520. -
  521. Something is trying to call child on object PGconn before it has been recognized.
  522. This error usually means that you need to modify the order in which you parse files
  523. so that PGconn is parsed before methods or other objects attempt to access it.
  524. -
  525. YARD will recover from this error and continue to parse but you *may* have problems
  526. with your generated documentation. You should probably fix this.
  527. -
  528.  
  529. [error]: Unhandled exception in YARD::Handlers::C::AliasHandler:
  530. in `C:/Ruby23/lib/ruby/gems/2.3.0/gems/pg-0.20.0-x86-mingw32/ext/pg_connection.c`:4078:
  531.  
  532. 4078: rb_define_alias(rb_cPGconn, "lotell", "lo_tell");
  533.  
  534. [error]: ProxyMethodError: Proxy cannot call method #child on object 'PGconn'
  535. [error]: Stack trace:
  536. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/code_objects/proxy.rb:189:in `rescue in method_missing'
  537. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/code_objects/proxy.rb:186:in `method_missing'
  538. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/handler_methods.rb:90:in `handle_alias'
  539. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/alias_handler.rb:13:in `block (2 levels) in <class:AliasHandler>'
  540. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/alias_handler.rb:11:in `scan'
  541. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/alias_handler.rb:11:in `block in <class:AliasHandler>'
  542.  
  543. [warn]: Load Order / Name Resolution Problem on PGconn:
  544. -
  545. Something is trying to call child on object PGconn before it has been recognized.
  546. This error usually means that you need to modify the order in which you parse files
  547. so that PGconn is parsed before methods or other objects attempt to access it.
  548. -
  549. YARD will recover from this error and continue to parse but you *may* have problems
  550. with your generated documentation. You should probably fix this.
  551. -
  552.  
  553. [error]: Unhandled exception in YARD::Handlers::C::AliasHandler:
  554. in `C:/Ruby23/lib/ruby/gems/2.3.0/gems/pg-0.20.0-x86-mingw32/ext/pg_connection.c`:4080:
  555.  
  556. 4080: rb_define_alias(rb_cPGconn, "lotruncate", "lo_truncate");
  557.  
  558. [error]: ProxyMethodError: Proxy cannot call method #child on object 'PGconn'
  559. [error]: Stack trace:
  560. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/code_objects/proxy.rb:189:in `rescue in method_missing'
  561. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/code_objects/proxy.rb:186:in `method_missing'
  562. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/handler_methods.rb:90:in `handle_alias'
  563. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/alias_handler.rb:13:in `block (2 levels) in <class:AliasHandler>'
  564. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/alias_handler.rb:11:in `scan'
  565. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/alias_handler.rb:11:in `block in <class:AliasHandler>'
  566.  
  567. [warn]: Load Order / Name Resolution Problem on PGconn:
  568. -
  569. Something is trying to call child on object PGconn before it has been recognized.
  570. This error usually means that you need to modify the order in which you parse files
  571. so that PGconn is parsed before methods or other objects attempt to access it.
  572. -
  573. YARD will recover from this error and continue to parse but you *may* have problems
  574. with your generated documentation. You should probably fix this.
  575. -
  576.  
  577. [error]: Unhandled exception in YARD::Handlers::C::AliasHandler:
  578. in `C:/Ruby23/lib/ruby/gems/2.3.0/gems/pg-0.20.0-x86-mingw32/ext/pg_connection.c`:4082:
  579.  
  580. 4082: rb_define_alias(rb_cPGconn, "loclose", "lo_close");
  581.  
  582. [error]: ProxyMethodError: Proxy cannot call method #child on object 'PGconn'
  583. [error]: Stack trace:
  584. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/code_objects/proxy.rb:189:in `rescue in method_missing'
  585. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/code_objects/proxy.rb:186:in `method_missing'
  586. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/handler_methods.rb:90:in `handle_alias'
  587. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/alias_handler.rb:13:in `block (2 levels) in <class:AliasHandler>'
  588. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/alias_handler.rb:11:in `scan'
  589. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/alias_handler.rb:11:in `block in <class:AliasHandler>'
  590.  
  591. [warn]: Load Order / Name Resolution Problem on PGconn:
  592. -
  593. Something is trying to call child on object PGconn before it has been recognized.
  594. This error usually means that you need to modify the order in which you parse files
  595. so that PGconn is parsed before methods or other objects attempt to access it.
  596. -
  597. YARD will recover from this error and continue to parse but you *may* have problems
  598. with your generated documentation. You should probably fix this.
  599. -
  600.  
  601. [error]: Unhandled exception in YARD::Handlers::C::AliasHandler:
  602. in `C:/Ruby23/lib/ruby/gems/2.3.0/gems/pg-0.20.0-x86-mingw32/ext/pg_connection.c`:4084:
  603.  
  604. 4084: rb_define_alias(rb_cPGconn, "lounlink", "lo_unlink");
  605.  
  606. [error]: ProxyMethodError: Proxy cannot call method #child on object 'PGconn'
  607. [error]: Stack trace:
  608. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/code_objects/proxy.rb:189:in `rescue in method_missing'
  609. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/code_objects/proxy.rb:186:in `method_missing'
  610. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/handler_methods.rb:90:in `handle_alias'
  611. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/alias_handler.rb:13:in `block (2 levels) in <class:AliasHandler>'
  612. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/alias_handler.rb:11:in `scan'
  613. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/alias_handler.rb:11:in `block in <class:AliasHandler>'
  614.  
  615. [warn]: The proxy PG has not yet been recognized.
  616. If this class/method is part of your source tree, this will affect your documentation results.
  617. You can correct this issue by loading the source file for this object before `C:/Ruby23/lib/ruby/gems/2.3.0/gems/pg-0.20.0-x86-mingw32/ext/pg_type_map.c'
  618.  
  619. [warn]: The proxy TypeMap has not yet been recognized.
  620. If this class/method is part of your source tree, this will affect your documentation results.
  621. You can correct this issue by loading the source file for this object before `C:/Ruby23/lib/ruby/gems/2.3.0/gems/pg-0.20.0-x86-mingw32/ext/pg_type_map.c'
  622.  
  623. [warn]: The proxy PG has not yet been recognized.
  624. If this class/method is part of your source tree, this will affect your documentation results.
  625. You can correct this issue by loading the source file for this object before `C:/Ruby23/lib/ruby/gems/2.3.0/gems/pg-0.20.0-x86-mingw32/ext/pg_result.c'
  626.  
  627. [warn]: The proxy PGresult has not yet been recognized.
  628. If this class/method is part of your source tree, this will affect your documentation results.
  629. You can correct this issue by loading the source file for this object before `C:/Ruby23/lib/ruby/gems/2.3.0/gems/pg-0.20.0-x86-mingw32/ext/pg_result.c'
  630.  
  631. [warn]: The proxy PGresult has not yet been recognized.
  632. If this class/method is part of your source tree, this will affect your documentation results.
  633. You can correct this issue by loading the source file for this object before `C:/Ruby23/lib/ruby/gems/2.3.0/gems/pg-0.20.0-x86-mingw32/ext/pg_result.c'
  634.  
  635. [warn]: Load Order / Name Resolution Problem on PGresult:
  636. -
  637. Something is trying to call child on object PGresult before it has been recognized.
  638. This error usually means that you need to modify the order in which you parse files
  639. so that PGresult is parsed before methods or other objects attempt to access it.
  640. -
  641. YARD will recover from this error and continue to parse but you *may* have problems
  642. with your generated documentation. You should probably fix this.
  643. -
  644.  
  645. [error]: Unhandled exception in YARD::Handlers::C::AliasHandler:
  646. in `C:/Ruby23/lib/ruby/gems/2.3.0/gems/pg-0.20.0-x86-mingw32/ext/pg_result.c`:1222:
  647.  
  648. 1222: rb_define_alias( rb_cPGresult, "result_error_message", "error_message");
  649.  
  650. [error]: ProxyMethodError: Proxy cannot call method #child on object 'PGresult'
  651. [error]: Stack trace:
  652. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/code_objects/proxy.rb:189:in `rescue in method_missing'
  653. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/code_objects/proxy.rb:186:in `method_missing'
  654. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/handler_methods.rb:90:in `handle_alias'
  655. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/alias_handler.rb:13:in `block (2 levels) in <class:AliasHandler>'
  656. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/alias_handler.rb:11:in `scan'
  657. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/alias_handler.rb:11:in `block in <class:AliasHandler>'
  658.  
  659. [warn]: Load Order / Name Resolution Problem on PGresult:
  660. -
  661. Something is trying to call child on object PGresult before it has been recognized.
  662. This error usually means that you need to modify the order in which you parse files
  663. so that PGresult is parsed before methods or other objects attempt to access it.
  664. -
  665. YARD will recover from this error and continue to parse but you *may* have problems
  666. with your generated documentation. You should probably fix this.
  667. -
  668.  
  669. [error]: Unhandled exception in YARD::Handlers::C::AliasHandler:
  670. in `C:/Ruby23/lib/ruby/gems/2.3.0/gems/pg-0.20.0-x86-mingw32/ext/pg_result.c`:1224:
  671.  
  672. 1224: rb_define_alias( rb_cPGresult, "result_error_field", "error_field" );
  673.  
  674. [error]: ProxyMethodError: Proxy cannot call method #child on object 'PGresult'
  675. [error]: Stack trace:
  676. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/code_objects/proxy.rb:189:in `rescue in method_missing'
  677. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/code_objects/proxy.rb:186:in `method_missing'
  678. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/handler_methods.rb:90:in `handle_alias'
  679. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/alias_handler.rb:13:in `block (2 levels) in <class:AliasHandler>'
  680. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/alias_handler.rb:11:in `scan'
  681. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/alias_handler.rb:11:in `block in <class:AliasHandler>'
  682.  
  683. [warn]: Load Order / Name Resolution Problem on PGresult:
  684. -
  685. Something is trying to call child on object PGresult before it has been recognized.
  686. This error usually means that you need to modify the order in which you parse files
  687. so that PGresult is parsed before methods or other objects attempt to access it.
  688. -
  689. YARD will recover from this error and continue to parse but you *may* have problems
  690. with your generated documentation. You should probably fix this.
  691. -
  692.  
  693. [error]: Unhandled exception in YARD::Handlers::C::AliasHandler:
  694. in `C:/Ruby23/lib/ruby/gems/2.3.0/gems/pg-0.20.0-x86-mingw32/ext/pg_result.c`:1227:
  695.  
  696. 1227: rb_define_alias (rb_cPGresult, "check_result", "check");
  697.  
  698. [error]: ProxyMethodError: Proxy cannot call method #child on object 'PGresult'
  699. [error]: Stack trace:
  700. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/code_objects/proxy.rb:189:in `rescue in method_missing'
  701. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/code_objects/proxy.rb:186:in `method_missing'
  702. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/handler_methods.rb:90:in `handle_alias'
  703. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/alias_handler.rb:13:in `block (2 levels) in <class:AliasHandler>'
  704. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/alias_handler.rb:11:in `scan'
  705. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/alias_handler.rb:11:in `block in <class:AliasHandler>'
  706.  
  707. [warn]: Load Order / Name Resolution Problem on PGresult:
  708. -
  709. Something is trying to call child on object PGresult before it has been recognized.
  710. This error usually means that you need to modify the order in which you parse files
  711. so that PGresult is parsed before methods or other objects attempt to access it.
  712. -
  713. YARD will recover from this error and continue to parse but you *may* have problems
  714. with your generated documentation. You should probably fix this.
  715. -
  716.  
  717. [error]: Unhandled exception in YARD::Handlers::C::AliasHandler:
  718. in `C:/Ruby23/lib/ruby/gems/2.3.0/gems/pg-0.20.0-x86-mingw32/ext/pg_result.c`:1229:
  719.  
  720. 1229: rb_define_alias(rb_cPGresult, "num_tuples", "ntuples");
  721.  
  722. [error]: ProxyMethodError: Proxy cannot call method #child on object 'PGresult'
  723. [error]: Stack trace:
  724. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/code_objects/proxy.rb:189:in `rescue in method_missing'
  725. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/code_objects/proxy.rb:186:in `method_missing'
  726. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/handler_methods.rb:90:in `handle_alias'
  727. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/alias_handler.rb:13:in `block (2 levels) in <class:AliasHandler>'
  728. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/alias_handler.rb:11:in `scan'
  729. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/alias_handler.rb:11:in `block in <class:AliasHandler>'
  730.  
  731. [warn]: Load Order / Name Resolution Problem on PGresult:
  732. -
  733. Something is trying to call child on object PGresult before it has been recognized.
  734. This error usually means that you need to modify the order in which you parse files
  735. so that PGresult is parsed before methods or other objects attempt to access it.
  736. -
  737. YARD will recover from this error and continue to parse but you *may* have problems
  738. with your generated documentation. You should probably fix this.
  739. -
  740.  
  741. [error]: Unhandled exception in YARD::Handlers::C::AliasHandler:
  742. in `C:/Ruby23/lib/ruby/gems/2.3.0/gems/pg-0.20.0-x86-mingw32/ext/pg_result.c`:1231:
  743.  
  744. 1231: rb_define_alias(rb_cPGresult, "num_fields", "nfields");
  745.  
  746. [error]: ProxyMethodError: Proxy cannot call method #child on object 'PGresult'
  747. [error]: Stack trace:
  748. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/code_objects/proxy.rb:189:in `rescue in method_missing'
  749. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/code_objects/proxy.rb:186:in `method_missing'
  750. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/handler_methods.rb:90:in `handle_alias'
  751. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/alias_handler.rb:13:in `block (2 levels) in <class:AliasHandler>'
  752. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/alias_handler.rb:11:in `scan'
  753. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/alias_handler.rb:11:in `block in <class:AliasHandler>'
  754.  
  755. [warn]: Load Order / Name Resolution Problem on PGresult:
  756. -
  757. Something is trying to call child on object PGresult before it has been recognized.
  758. This error usually means that you need to modify the order in which you parse files
  759. so that PGresult is parsed before methods or other objects attempt to access it.
  760. -
  761. YARD will recover from this error and continue to parse but you *may* have problems
  762. with your generated documentation. You should probably fix this.
  763. -
  764.  
  765. [error]: Unhandled exception in YARD::Handlers::C::AliasHandler:
  766. in `C:/Ruby23/lib/ruby/gems/2.3.0/gems/pg-0.20.0-x86-mingw32/ext/pg_result.c`:1247:
  767.  
  768. 1247: rb_define_alias(rb_cPGresult, "cmdtuples", "cmd_tuples");
  769.  
  770. [error]: ProxyMethodError: Proxy cannot call method #child on object 'PGresult'
  771. [error]: Stack trace:
  772. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/code_objects/proxy.rb:189:in `rescue in method_missing'
  773. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/code_objects/proxy.rb:186:in `method_missing'
  774. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/handler_methods.rb:90:in `handle_alias'
  775. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/alias_handler.rb:13:in `block (2 levels) in <class:AliasHandler>'
  776. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/alias_handler.rb:11:in `scan'
  777. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/alias_handler.rb:11:in `block in <class:AliasHandler>'
  778.  
  779. [warn]: The proxy PG has not yet been recognized.
  780. If this class/method is part of your source tree, this will affect your documentation results.
  781. You can correct this issue by loading the source file for this object before `C:/Ruby23/lib/ruby/gems/2.3.0/gems/pg-0.20.0-x86-mingw32/ext/pg_errors.c'
  782.  
  783. [warn]: Load Order / Name Resolution Problem on PGerror:
  784. -
  785. Something is trying to call child on object PGerror before it has been recognized.
  786. This error usually means that you need to modify the order in which you parse files
  787. so that PGerror is parsed before methods or other objects attempt to access it.
  788. -
  789. YARD will recover from this error and continue to parse but you *may* have problems
  790. with your generated documentation. You should probably fix this.
  791. -
  792.  
  793. [error]: Unhandled exception in YARD::Handlers::C::AliasHandler:
  794. in `C:/Ruby23/lib/ruby/gems/2.3.0/gems/pg-0.20.0-x86-mingw32/ext/pg_errors.c`:83:
  795.  
  796. 83: rb_define_alias( rb_ePGerror, "error", "message" );
  797.  
  798. [error]: ProxyMethodError: Proxy cannot call method #child on object 'PGerror'
  799. [error]: Stack trace:
  800. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/code_objects/proxy.rb:189:in `rescue in method_missing'
  801. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/code_objects/proxy.rb:186:in `method_missing'
  802. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/handler_methods.rb:90:in `handle_alias'
  803. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/alias_handler.rb:13:in `block (2 levels) in <class:AliasHandler>'
  804. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/alias_handler.rb:11:in `scan'
  805. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/alias_handler.rb:11:in `block in <class:AliasHandler>'
  806.  
  807. [warn]: Load Order / Name Resolution Problem on PGerror:
  808. -
  809. Something is trying to call attributes on object PGerror before it has been recognized.
  810. This error usually means that you need to modify the order in which you parse files
  811. so that PGerror is parsed before methods or other objects attempt to access it.
  812. -
  813. YARD will recover from this error and continue to parse but you *may* have problems
  814. with your generated documentation. You should probably fix this.
  815. -
  816.  
  817. [error]: Unhandled exception in YARD::Handlers::C::AttributeHandler:
  818. in `C:/Ruby23/lib/ruby/gems/2.3.0/gems/pg-0.20.0-x86-mingw32/ext/pg_errors.c`:84:
  819.  
  820. 84: rb_define_attr( rb_ePGerror, "connection", 1, 0 );
  821.  
  822. [error]: ProxyMethodError: Proxy cannot call method #attributes on object 'PGerror'
  823. [error]: Stack trace:
  824. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/code_objects/proxy.rb:189:in `rescue in method_missing'
  825. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/code_objects/proxy.rb:186:in `method_missing'
  826. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/handler_methods.rb:80:in `block in handle_attribute'
  827. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/handler_methods.rb:76:in `each'
  828. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/handler_methods.rb:76:in `handle_attribute'
  829. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/attribute_handler.rb:10:in `block (2 levels) in <class:AttributeHandler>'
  830.  
  831. [warn]: Load Order / Name Resolution Problem on PGerror:
  832. -
  833. Something is trying to call attributes on object PGerror before it has been recognized.
  834. This error usually means that you need to modify the order in which you parse files
  835. so that PGerror is parsed before methods or other objects attempt to access it.
  836. -
  837. YARD will recover from this error and continue to parse but you *may* have problems
  838. with your generated documentation. You should probably fix this.
  839. -
  840.  
  841. [error]: Unhandled exception in YARD::Handlers::C::AttributeHandler:
  842. in `C:/Ruby23/lib/ruby/gems/2.3.0/gems/pg-0.20.0-x86-mingw32/ext/pg_errors.c`:85:
  843.  
  844. 85: rb_define_attr( rb_ePGerror, "result", 1, 0 );
  845.  
  846. [error]: ProxyMethodError: Proxy cannot call method #attributes on object 'PGerror'
  847. [error]: Stack trace:
  848. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/code_objects/proxy.rb:189:in `rescue in method_missing'
  849. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/code_objects/proxy.rb:186:in `method_missing'
  850. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/handler_methods.rb:80:in `block in handle_attribute'
  851. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/handler_methods.rb:76:in `each'
  852. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/handler_methods.rb:76:in `handle_attribute'
  853. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/attribute_handler.rb:10:in `block (2 levels) in <class:AttributeHandler>'
  854.  
  855. [warn]: The proxy PG has not yet been recognized.
  856. If this class/method is part of your source tree, this will affect your documentation results.
  857. You can correct this issue by loading the source file for this object before `C:/Ruby23/lib/ruby/gems/2.3.0/gems/pg-0.20.0-x86-mingw32/ext/pg_errors.c'
  858.  
  859. [warn]: The proxy PG has not yet been recognized.
  860. If this class/method is part of your source tree, this will affect your documentation results.
  861. You can correct this issue by loading the source file for this object before `C:/Ruby23/lib/ruby/gems/2.3.0/gems/pg-0.20.0-x86-mingw32/ext/pg_errors.c'
  862.  
  863. [warn]: The proxy PG has not yet been recognized.
  864. If this class/method is part of your source tree, this will affect your documentation results.
  865. You can correct this issue by loading the source file for this object before `C:/Ruby23/lib/ruby/gems/2.3.0/gems/pg-0.20.0-x86-mingw32/ext/pg_errors.c'
  866.  
  867. [warn]: The proxy PG has not yet been recognized.
  868. If this class/method is part of your source tree, this will affect your documentation results.
  869. You can correct this issue by loading the source file for this object before `C:/Ruby23/lib/ruby/gems/2.3.0/gems/pg-0.20.0-x86-mingw32/ext/pg_errors.c'
  870.  
  871. [warn]: The proxy PG has not yet been recognized.
  872. If this class/method is part of your source tree, this will affect your documentation results.
  873. You can correct this issue by loading the source file for this object before `C:/Ruby23/lib/ruby/gems/2.3.0/gems/pg-0.20.0-x86-mingw32/ext/pg_errors.c'
  874.  
  875. [warn]: The proxy PG has not yet been recognized.
  876. If this class/method is part of your source tree, this will affect your documentation results.
  877. You can correct this issue by loading the source file for this object before `C:/Ruby23/lib/ruby/gems/2.3.0/gems/pg-0.20.0-x86-mingw32/ext/pg_errors.c'
  878.  
  879. [warn]: The proxy PG has not yet been recognized.
  880. If this class/method is part of your source tree, this will affect your documentation results.
  881. You can correct this issue by loading the source file for this object before `C:/Ruby23/lib/ruby/gems/2.3.0/gems/pg-0.20.0-x86-mingw32/ext/pg_coder.c'
  882.  
  883. [warn]: Load Order / Name Resolution Problem on PG_Coder:
  884. -
  885. Something is trying to call attributes on object PG_Coder before it has been recognized.
  886. This error usually means that you need to modify the order in which you parse files
  887. so that PG_Coder is parsed before methods or other objects attempt to access it.
  888. -
  889. YARD will recover from this error and continue to parse but you *may* have problems
  890. with your generated documentation. You should probably fix this.
  891. -
  892.  
  893. [error]: Unhandled exception in YARD::Handlers::C::AttributeHandler:
  894. in `C:/Ruby23/lib/ruby/gems/2.3.0/gems/pg-0.20.0-x86-mingw32/ext/pg_coder.c`:465:
  895.  
  896. 465: rb_define_attr( rb_cPG_Coder, "name", 1, 1 );
  897.  
  898. [error]: ProxyMethodError: Proxy cannot call method #attributes on object 'PG_Coder'
  899. [error]: Stack trace:
  900. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/code_objects/proxy.rb:189:in `rescue in method_missing'
  901. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/code_objects/proxy.rb:186:in `method_missing'
  902. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/handler_methods.rb:80:in `block in handle_attribute'
  903. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/handler_methods.rb:76:in `each'
  904. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/handler_methods.rb:76:in `handle_attribute'
  905. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/attribute_handler.rb:10:in `block (2 levels) in <class:AttributeHandler>'
  906.  
  907. [warn]: The proxy PG has not yet been recognized.
  908. If this class/method is part of your source tree, this will affect your documentation results.
  909. You can correct this issue by loading the source file for this object before `C:/Ruby23/lib/ruby/gems/2.3.0/gems/pg-0.20.0-x86-mingw32/ext/pg_coder.c'
  910.  
  911. [warn]: The proxy PG has not yet been recognized.
  912. If this class/method is part of your source tree, this will affect your documentation results.
  913. You can correct this issue by loading the source file for this object before `C:/Ruby23/lib/ruby/gems/2.3.0/gems/pg-0.20.0-x86-mingw32/ext/pg_coder.c'
  914.  
  915. [warn]: The proxy PG has not yet been recognized.
  916. If this class/method is part of your source tree, this will affect your documentation results.
  917. You can correct this issue by loading the source file for this object before `C:/Ruby23/lib/ruby/gems/2.3.0/gems/pg-0.20.0-x86-mingw32/ext/pg_coder.c'
  918.  
  919. [warn]: The proxy PG has not yet been recognized.
  920. If this class/method is part of your source tree, this will affect your documentation results.
  921. You can correct this issue by loading the source file for this object before `C:/Ruby23/lib/ruby/gems/2.3.0/gems/pg-0.20.0-x86-mingw32/ext/pg_coder.c'
  922.  
  923. [warn]: Load Order / Name Resolution Problem on PG_CompositeCoder:
  924. -
  925. Something is trying to call attributes on object PG_CompositeCoder before it has been recognized.
  926. This error usually means that you need to modify the order in which you parse files
  927. so that PG_CompositeCoder is parsed before methods or other objects attempt to access it.
  928. -
  929. YARD will recover from this error and continue to parse but you *may* have problems
  930. with your generated documentation. You should probably fix this.
  931. -
  932.  
  933. [error]: Unhandled exception in YARD::Handlers::C::AttributeHandler:
  934. in `C:/Ruby23/lib/ruby/gems/2.3.0/gems/pg-0.20.0-x86-mingw32/ext/pg_coder.c`:486:
  935.  
  936. 486: rb_define_attr( rb_cPG_CompositeCoder, "elements_type", 1, 0 );
  937.  
  938. [error]: ProxyMethodError: Proxy cannot call method #attributes on object 'PG_CompositeCoder'
  939. [error]: Stack trace:
  940. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/code_objects/proxy.rb:189:in `rescue in method_missing'
  941. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/code_objects/proxy.rb:186:in `method_missing'
  942. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/handler_methods.rb:80:in `block in handle_attribute'
  943. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/handler_methods.rb:76:in `each'
  944. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/handler_methods.rb:76:in `handle_attribute'
  945. C:/Ruby23/lib/ruby/gems/2.3.0/gems/yard-0.9.9/lib/yard/handlers/c/attribute_handler.rb:10:in `block (2 levels) in <class:AttributeHandler>'
  946.  
  947. [warn]: The proxy PG has not yet been recognized.
  948. If this class/method is part of your source tree, this will affect your documentation results.
  949. You can correct this issue by loading the source file for this object before `C:/Ruby23/lib/ruby/gems/2.3.0/gems/pg-0.20.0-x86-mingw32/ext/pg_coder.c'
  950.  
  951. [warn]: The proxy PG has not yet been recognized.
  952. If this class/method is part of your source tree, this will affect your documentation results.
  953. You can correct this issue by loading the source file for this object before `C:/Ruby23/lib/ruby/gems/2.3.0/gems/pg-0.20.0-x86-mingw32/ext/pg_coder.c'
  954.  
  955. [warn]: The proxy PG_Coder has not yet been recognized.
  956. If this class/method is part of your source tree, this will affect your documentation results.
  957. You can correct this issue by loading the source file for this object before `C:/Ruby23/lib/ruby/gems/2.3.0/gems/pg-0.20.0-x86-mingw32/ext/pg_coder.c'
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement
Public Pastes
Advertisement
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy.  OK, I Understand
Not a member of Pastebin yet?
Sign Up, it unlocks many cool features!