Re: Ruby 3.1 Event Driven Concurrent using Ruby Fiber Scheduler support.

2021-12-20 Thread Billy Zheng
Oh, Cool, never saw that, it' seem like don't need database_cleaner-sequel gem anymore if do some config myself. 在2021年12月19日星期日 UTC+8 21:18:34 写道: > Hi, > > it looks like database_cleaner-sequel gem is used to run the test within > a transaction so that database updates are cleaned up after

Re: Ruby 3.1 Event Driven Concurrent using Ruby Fiber Scheduler support.

2021-12-19 Thread abhijit
Hi, it looks like database_cleaner-sequel gem is used to run the test within a transaction so that database updates are cleaned up after the test runs. You'll achieve the same results if you use the testing strategy as suggested by Jeremy in Sequel docs -

Re: Ruby 3.1 Event Driven Concurrent using Ruby Fiber Scheduler support.

2021-11-05 Thread Billy Zheng
It's fine, thanks for help, if there have any useful update, i will report here. 在2021年11月2日星期二 UTC+8 下午10:39:32 写道: > On Tue, Nov 2, 2021 at 12:30 AM Billy Zheng wrote: > >> Hi, after some research, this test failing issue caused by >> database_cleaner-sequel gem. >> >> config here. >>

Re: Ruby 3.1 Event Driven Concurrent using Ruby Fiber Scheduler support.

2021-11-02 Thread Jeremy Evans
On Tue, Nov 2, 2021 at 12:30 AM Billy Zheng wrote: > Hi, after some research, this test failing issue caused by > database_cleaner-sequel gem. > > config here. > https://github.com/zw963/marketbet_crawler/blob/4e3537a267d93c3fc109ccebc119d08571d58d43/test/test_helper.rb > > after change

Re: Ruby 3.1 Event Driven Concurrent using Ruby Fiber Scheduler support.

2021-11-02 Thread Billy Zheng
Hi, after some research, this test failing issue caused by database_cleaner-sequel gem. config here. https://github.com/zw963/marketbet_crawler/blob/4e3537a267d93c3fc109ccebc119d08571d58d43/test/test_helper.rb after change DatabaseCleaner[:sequel].strategy from :transaction into :truncate,

Re: Ruby 3.1 Event Driven Concurrent using Ruby Fiber Scheduler support.

2021-11-01 Thread Jeremy Evans
On Mon, Nov 1, 2021 at 3:18 AM Billy Zheng wrote: > > I get many test failing message when add `Sequel.extension > :fiber_concurrency` into sequel config file, but then comment it,it can't > be fixed automatically. > i have to `RACK_ENV=test rake db:drop db:create db:migrate` again, to > make

Re: Ruby 3.1 Event Driven Concurrent using Ruby Fiber Scheduler support.

2021-11-01 Thread Billy Zheng
I get many test failing message when add `Sequel.extension :fiber_concurrency` into sequel config file, but then comment it,it can't be fixed automatically. i have to `RACK_ENV=test rake db:drop db:create db:migrate` again, to make test pass again. ``` RACK_ENV=test DB connected:

Re: Ruby 3.1 Event Driven Concurrent using Ruby Fiber Scheduler support.

2021-10-27 Thread Billy Zheng
[image: photo_2021-10-28_01-52-51.jpg] I run bin/console (irb) on my production server, it return false, thanks 在2021年10月27日星期三 UTC+8 上午2:41:08 写道: > On Tue, Oct 26, 2021 at 10:56 AM Billy Zheng wrote: > >> >> Thanks, >> >> i added this plugins, and test it on production, it still works. >>

Re: Ruby 3.1 Event Driven Concurrent using Ruby Fiber Scheduler support.

2021-10-26 Thread Jeremy Evans
On Tue, Oct 26, 2021 at 10:56 AM Billy Zheng wrote: > > Thanks, > > i added this plugins, and test it on production, it still works. > > i use sequel_pg and pg gem on production, and change web server from puma > to falcon. > > so, can you please tell me if there exists some special log or

Re: Ruby 3.1 Event Driven Concurrent using Ruby Fiber Scheduler support.

2021-10-26 Thread Billy Zheng
Thanks, i added this plugins, and test it on production, it still works. i use sequel_pg and pg gem on production, and change web server from puma to falcon. so, can you please tell me if there exists some special log or somethings to prove current work on per-fiber request mode?

Re: Ruby 3.1 Event Driven Concurrent using Ruby Fiber Scheduler support.

2021-10-24 Thread Jeremy Evans
On Sat, Oct 23, 2021 at 9:24 AM Billy Zheng wrote: > Ruby 3.1 will make ruby fiber scheduler, which introduced in ruby 3.0, > the official non-block io and concurrency solution, more mature and > completely, but, as mention by Samuel Williams @ioquatix, who is the > author of async, in this