mattn / mattn/mruby-require

Issues with mruby 3.2.0

Open
#55 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C
Stars
42
Forks
24
PR merge metrics
No merged PRs in 30d

Description

Hi,

I've found an issue with mruby 3.2.0.

Given these two files:

entry.rb

$:.unshift '.'

require 'zip'

and zip.rb

a = [1,2,3]
b = [:a, :b, :c]

p a.zip(b)

I am getting the error:

trace (most recent call last):
        [10] (unknown):0
        [9] (unknown):0:in require
        [8] /home/sean/Syncthing/code/c++/taylor/zip.rb:4
        [7] /home/sean/Syncthing/code/c++/taylor/zip.rb:4:in zip
        [6] /home/sean/Syncthing/code/c++/taylor/zip.rb:4:in each
        [5] /home/sean/Syncthing/code/c++/taylor/zip.rb:4:in zip
        [4] /home/sean/Syncthing/code/c++/taylor/zip.rb:4:in each
        [3] /home/sean/Syncthing/code/c++/taylor/zip.rb:4:in zip
        [2] /home/sean/Syncthing/code/c++/taylor/zip.rb:4:in next
        [1] /home/sean/Syncthing/code/c++/taylor/zip.rb:4:in next_values
/home/sean/Syncthing/code/c++/taylor/zip.rb:4:in resume: can't cross C function boundary (FiberError)

It works as expected with mruby 3.1.0

Please let me know if you require any more information

Contributor guide

No contributing guide indexed for this repository

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

Reproduce the report using entry.rb and zip.rb with mruby 3.2.0, then compare the same case on mruby 3.1.0. Investigate the require and FiberError path exposed by Array#zip and determine what needs to change so the example works again on 3.2.0; done means the reported program runs without the boundary error.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.