Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
Jason Frey
@Fryguy
I assume they aren't exported / public
there is a process.h
Adam Grare
@agrare
not all header files have to be for exported/public methods
Jason Frey
@Fryguy
yeah
Adam Grare
@agrare
yeah, would have expected internal/hash.h
Jason Frey
@Fryguy
All I meant was I've seen other projects that only put their exported prototypes in .h, and keep the rest "private"
but seems Ruby does neither haha
Adam Grare
@agrare
yeah the issue is you'd have to declare those in every C file that you want to use those utility methods in
Jason Frey
@Fryguy
yeah
Adam Grare
@agrare
anyway, awesome to see a fix so quickly
Jason Frey
@Fryguy
oh wait I totally misread - rb_envtbl was in hash.c - I thought it was on process.c
wow - that's really weird
Adam Grare
@agrare
yeah
Jason Frey
@Fryguy
I just assumed they were the same file for some reason haha
Adam Grare
@agrare
....there is an internal/hash.h
which process.c already includes
who is this guy? haha
Jason Frey
@Fryguy
commented :)
he's a Ruby core committer
yeah I'm happy this got turned around so quickly
amazingly this hit me like 3 levels of ADHD away from where I'm supposed to be fixing stuff :joy:
I'm trying to fix that Gemfile.lock.release thing you found, but in order to do that I need to rebuild the Gemfile.lock, but locally I have my bundler-inject global files getting in the way, so I thought I'd fix bundler-inject to have a way to skip the global bundler.d, but when I was testing that I hit this segfault....whew
Jason Frey
@Fryguy
I mean I could have just done a mv ~/.bundler.d{,.bak}, but where's the fun in that
I'm on a roll this week - found a Crystal bug and a Ruby bug haha
Daniel Berger
@djberg96
"After looking at hash.c, I do not understand why it isn't actually a hash. The actual implementation is overwrought for what it does." - Me, commenting in 2007 -> http://rubyonwindows.blogspot.com/2007/06/making-use-of-rubys-env-object.html -
Jason Frey
@Fryguy
same thought crossed my mind
Joe Rafaniello
@jrafanie
stuff like this is what I couldn't remember yesterday... where env isn't a hash: ManageIQ/manageiq@d098bc0
Joe Rafaniello
@jrafanie
that's pretty awesome Jeremy already fixed it... he fixed the Tempfile finalizer getting interrupted by timeout exceptions bug I opened: https://bugs.ruby-lang.org/issues/13876
Daniel Berger
@djberg96
@Fryguy what was the crystal bug?
Jason Frey
@Fryguy
Oh I haven't had a chance to post it yet
Mainly cause I wanted to fix it myself before someone sniped it haha
Keenan Brock
@kbrock
lol. you saw into my nefarious plan
Joe Rafaniello
@jrafanie
haha
Kuldip-Nanda
@Kuldip-Nanda

Hi,
I do not see any of the manageiq processes coming when I run

# bundle exec rails evm:status
** override_gem("manageiq-providers-ibm_cloud", :path=>"/mnt/githubfork/manageiq/plugins/manageiq-providers-ibm_cloud") at /mnt/githubfork/manageiq/bundler.d/local_plugins.rb:7                                                             
** override_gem("manageiq-providers-ibm_cloud", :path=>"/mnt/githubfork/manageiq/plugins/manageiq-providers-ibm_cloud") at /mnt/githubfork/manageiq/bundler.d/local_plugins.rb:7                                                             
** ManageIQ master, codename: Najdorf
Checking EVM status...
 Region | Zone    | Server | Status  |   PID |  SPID | Workers | Version | Started    | Heartbeat  | MB Usage | Roles
--------|---------|--------|---------|-------|-------|---------|---------|------------|------------|----------|----------------------------------------------------------------------------------------------------------------------------------------------------------
      0 | default | EVM*   | started | 88993 | 89010 |       0 | master  | 2021-09-09 | 2021-09-10 |      366 | automate:database_operations:database_owner:ems_inventory:ems_operations:event:remote_console:reporting:scheduler:smartstate:user_interface:web_services

* marks a master appliance

#

On investigation I see in evm.log

[----] I, [2021-09-14T15:02:33.326512 #7075:9178]  INFO -- evm: MIQ(EvmServer#check_migrations_up_to_date) database schema version 20210824231354 is up to date
[----] I, [2021-09-14T15:02:33.326784 #7075:9178]  INFO -- evm: MIQ(EvmServer#impersonate_server) Impersonating server - id: 1, guid: f8a33125-19cf-433d-8418-4811b04ecdcd
/mnt/githubfork/manageiq/app/models/miq_worker.rb:200:in `block in fetch_worker_settings_from_options_hash': Missing config section event_catcher_ibm_cloud_iks (RuntimeError)
        from /mnt/githubfork/manageiq/app/models/miq_worker.rb:198:in `each'
        from /mnt/githubfork/manageiq/app/models/miq_worker.rb:198:in `fetch_worker_settings_from_options_hash'
        from /mnt/githubfork/manageiq/lib/vmdb/settings/validator.rb:208:in `validate_worker_request_limit'
        from /mnt/githubfork/manageiq/lib/vmdb/settings/validator.rb:195:in `block in workers'
        from /mnt/githubfork/manageiq/lib/vmdb/settings/validator.rb:194:in `each'
        from /mnt/githubfork/manageiq/lib/vmdb/settings/validator.rb:194:in `workers'
        from /mnt/githubfork/manageiq/lib/vmdb/settings/validator.rb:22:in `block in validate'
        from /mnt/githubfork/manageiq/lib/vmdb/settings/validator.rb:17:in `each_key'
        from /mnt/githubfork/manageiq/lib/vmdb/settings/validator.rb:17:in `validate'
        from /mnt/githubfork/manageiq/lib/vmdb/settings/validator.rb:11:in `valid?'
        from /mnt/githubfork/manageiq/lib/vmdb/settings/activator.rb:11:in `activate'
        from /mnt/githubfork/manageiq/lib/vmdb/settings.rb:43:in `activate'
        from /mnt/githubfork/manageiq/lib/workers/evm_server.rb:96:in `start_server'
        from /mnt/githubfork/manageiq/lib/workers/evm_server.rb:43:in `block in start_servers'
        from /mnt/githubfork/manageiq/lib/workers/evm_server.rb:266:in `block in as_each_server'
        from /mnt/githubfork/manageiq/lib/workers/evm_server.rb:264:in `each'
        from /mnt/githubfork/manageiq/lib/workers/evm_server.rb:264:in `as_each_server'
        from /mnt/githubfork/manageiq/lib/workers/evm_server.rb:43:in `start_servers'
        from /mnt/githubfork/manageiq/lib/workers/evm_server.rb:28:in `start'
        from /mnt/githubfork/manageiq/lib/workers/evm_server.rb:82:in `start'
        from /mnt/githubfork/manageiq/lib/workers/bin/evm_server.rb:4:in `<main>'
[----] I, [2021-09-14T15:14:41.842410 #7228:9498]  INFO -- evm: MIQ(Vmdb::Loggers.apply_config) Log level for azure.log has been changed to [WARN]
Jason Frey
@Fryguy
@Kuldip-Nanda That was just fixed
pull in the latest code from the ibm_cloud plugin
Kuldip-Nanda
@Kuldip-Nanda
thanks Jason, let me see
vasilatos v
@vasgitlab_gitlab
Hi @Fryguy
its nice to meet you. I am going to develop the gitlab integration solution with manageIQ. could we have a discussion about this?
Jason Frey
@Fryguy
Sure - it might be easier in talk.manageiq.org though if we want to make sure we don't lose the converstaion
vasilatos v
@vasgitlab_gitlab
how can I connect to talk.manageiq.org?
Adam Grare
@agrare
@vasgitlab_gitlab you can create a topic in the Developers section: https://talk.manageiq.org/c/developers/5
vasilatos v
@vasgitlab_gitlab
okay thank you
I created a new topic regarding to how to create a plugin integrated with GitLab for DevOps purpose
@Fryguy , @agrare Hope you explain me how to do it for this purpose