问题描述
当我使用 neo4j.rb 项目（由 rake neo4j:migrate 和 gem 'activegraph','~> 10.0.1' 组成）运行 gem 'neo4j-ruby-driver','~> 1.7.0' 时，出现以下错误：
/Users/sanjaysingh/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/neo4j-9.6.2/lib/neo4j/tasks/migration.rake:51: warning: already initialized constant SCHEMA_YAML_PATH
/Users/sanjaysingh/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/activegraph-10.0.2/lib/active_graph/tasks/migration.rake:49: warning: prevIoUs deFinition of SCHEMA_YAML_PATH was here
/Users/sanjaysingh/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/neo4j-9.6.2/lib/neo4j/tasks/migration.rake:52: warning: already initialized constant SCHEMA_YAML_COMMENT
/Users/sanjaysingh/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/activegraph-10.0.2/lib/active_graph/tasks/migration.rake:50: warning: prevIoUs deFinition of SCHEMA_YAML_COMMENT was here
** Invoke neo4j:migrate (first_time)
** Execute neo4j:migrate
** Invoke neo4j:migrate:all (first_time)
** Invoke neo4j:allow_migrations (first_time)
** Execute neo4j:allow_migrations
** Invoke environment (first_time)
** Execute environment
** Execute neo4j:migrate:all
** Invoke neo4j:schema:dump (first_time)
** Invoke environment
** Execute neo4j:schema:dump
rake aborted!
No session defined!
/Users/sanjaysingh/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/neo4j-9.6.2/lib/neo4j/active_base.rb:9:in `block in current_session'
<internal:kernel>:90:in `tap'
/Users/sanjaysingh/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/neo4j-9.6.2/lib/neo4j/active_base.rb:8:in `current_session'
/Users/sanjaysingh/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/neo4j-9.6.2/lib/neo4j/tasks/migration.rake:68:in `check_neo4j_version_3'
/Users/sanjaysingh/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/activegraph-10.0.2/lib/active_graph/tasks/migration.rake:75:in `block (3 levels) in <main>'
/Users/sanjaysingh/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/task.rb:281:in `block in execute'
/Users/sanjaysingh/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/task.rb:281:in `each'
/Users/sanjaysingh/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/task.rb:281:in `execute'
/Users/sanjaysingh/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/task.rb:219:in `block in invoke_with_call_chain'
/Users/sanjaysingh/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/task.rb:199:in `synchronize'
/Users/sanjaysingh/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/task.rb:199:in `invoke_with_call_chain'
/Users/sanjaysingh/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/task.rb:188:in `invoke'
/Users/sanjaysingh/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/activegraph-10.0.2/lib/active_graph/tasks/migration.rake:119:in `block (3 levels) in <main>'
/Users/sanjaysingh/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/task.rb:281:in `block in execute'
/Users/sanjaysingh/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/task.rb:281:in `each'
/Users/sanjaysingh/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/task.rb:281:in `execute'
/Users/sanjaysingh/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/task.rb:219:in `block in invoke_with_call_chain'
/Users/sanjaysingh/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/task.rb:199:in `synchronize'
/Users/sanjaysingh/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/task.rb:199:in `invoke_with_call_chain'
/Users/sanjaysingh/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/task.rb:188:in `invoke'
/Users/sanjaysingh/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/activegraph-10.0.2/lib/active_graph/tasks/migration.rake:44:in `block (2 levels) in <main>'
/Users/sanjaysingh/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/task.rb:281:in `block in execute'
/Users/sanjaysingh/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/task.rb:281:in `each'
/Users/sanjaysingh/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/task.rb:281:in `execute'
/Users/sanjaysingh/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/task.rb:219:in `block in invoke_with_call_chain'
/Users/sanjaysingh/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/task.rb:199:in `synchronize'
/Users/sanjaysingh/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/task.rb:199:in `invoke_with_call_chain'
/Users/sanjaysingh/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/task.rb:188:in `invoke'
/Users/sanjaysingh/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/application.rb:160:in `invoke_task'
/Users/sanjaysingh/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/application.rb:116:in `block (2 levels) in top_level'
/Users/sanjaysingh/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/application.rb:116:in `each'
/Users/sanjaysingh/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/application.rb:116:in `block in top_level'
/Users/sanjaysingh/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/application.rb:125:in `run_with_threads'
/Users/sanjaysingh/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/application.rb:110:in `top_level'
/Users/sanjaysingh/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/application.rb:83:in `block in run'
/Users/sanjaysingh/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/application.rb:186:in `standard_exception_handling'
/Users/sanjaysingh/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/application.rb:80:in `run'
/Users/sanjaysingh/.rbenv/versions/3.0.0/lib/ruby/gems/3.0.0/gems/rake-13.0.3/exe/rake:27:in `<top (required)>'
/Users/sanjaysingh/.rbenv/versions/3.0.0/bin/rake:23:in `load'
/Users/sanjaysingh/.rbenv/versions/3.0.0/bin/rake:23:in `<main>'
Tasks: TOP => neo4j:schema:dump
可能是因为我对已经运行的迁移文件进行了更改？我重新启动了系统，重新启动了 neo4j 服务器，但没有任何效果。有没有办法通过删除一些旧的迁移来从头开始重新生成架构文件？提前致谢。
解决方法
暂无找到可以解决该程序问题的有效方法，小编努力寻找整理中！
如果你已经找到好的解决方法，欢迎将解决方案带上本链接一起发送给小编。
小编邮箱:dio#foxmail.com (将#修改为@）