beanstalkd / beanstalkd/beaneater

Segmentation faults

Open
#73 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Ruby
Stars
201
Forks
45
PR merge metrics
No merged PRs in 30d

Description

Sometimes, it seems when the workers are very busy we get segmentation faults.

/data/server/vendor/bundle/ruby/2.4.0/gems/beaneater-1.0.0/lib/beaneater/tube/collection.rb:106:in `watched': undefined method `map' for # (NoMethodError)

Is the following returning a string instead of an array?
```ruby
last_watched = transmit('list-tubes-watched')[:body]
```

Contributor guide

No contributing guide indexed for this repository

Research direction

Start in beaneater/tube/collection.rb around the watched method at line 106, then inspect the transmit('list-tubes-watched') response and its :body value. Compare the returned type with the method's use of map and investigate the busy-worker condition; done means the reported NoMethodError and segmentation-fault symptoms no longer occur.

Written by the indexing model from the issue text.

Assessment

Tech stack
ruby
Domain
backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.