twilio / twilio/twilio-ruby

Local Jump Error Listing Recordings

Open
#663 3 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

status: work in progress type: bug
Dominant language
Ruby
Stars
1.4k
Forks
472
Avg merge
1d 3h
Merged PRs (30d)
5

Description

Issue Summary

Upgrading from 5.56.0 to 6.1.0 has introduced a bug for us in the following code.

Downgrading back to 5.56.0 resolves the issue.

Steps to Reproduce
  1. Run the below code snippet on 6.1.0, local jump error exists.
  2. Rollback to 5.56.0, error does not occur.
Code Snippet
        client = Twilio::REST::Client.new(api_key_sid, api_key_secret, account_sid)
        recordings = client.video.v1.recordings.list(grouping_sid: ['SOME_ROOM_ID'],
                                                    limit: 20)
Exception/Log
LocalJumpError: no block given (yield)
from /Users/jamesyorston/.rbenv/versions/2.7.6/lib/ruby/gems/2.7.0/gems/twilio-ruby-6.0.1/lib/twilio-ruby/framework/serialize.rb:77:in `block in serialize_list'
Technical details:
  • twilio-ruby version: 6.1.0
  • ruby version: 2.7.6

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with twilio-ruby/framework/serialize.rb at line 77 and reproduce the LocalJumpError using the recordings.list call in the issue on Ruby 2.7.6. Compare behavior between twilio-ruby 5.56.0 and 6.1.0, then verify that listing recordings with grouping_sid and a limit completes without requiring a missing block.

Written by the indexing model from the issue text.

Assessment

Tech stack
ruby
Domain
api
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.