tmm1

I have a sample.mpg mpegts file with a video keyframe starting at 65738.512389

$ ffprobe -hide_banner -loglevel fatal sample.mpg -select_streams v -print_format json -show_packets -read_intervals "%+#1"
{
    "packets": [
        {
            "codec_type": "video",
            "stream_index": 0,
            "pts": 5916466115,

tmm1

diff --git a/libavfilter/aarch64/Makefile b/libavfilter/aarch64/Makefile
new file mode 100644
index 0000000..5d6f6d3
--- /dev/null
+++ b/libavfilter/aarch64/Makefile
@@ -0,0 +1,3 @@
+OBJS-$(CONFIG_YADIF_FILTER)      += aarch64/vf_yadif_init.o
+
+NEON-OBJS-$(CONFIG_YADIF_FILTER) += aarch64/vf_yadif.o
diff --git a/libavfilter/aarch64/vf_yadif_init.c b/libavfilter/aarch64/vf_yadif_init.c

tmm1

require 'rubygems'
require 'eventmachine'
require 'socket'

module RPCServer
  include EM::P::ObjectProtocol
  def post_init
    @obj = Hash.new
  end
  def receive_object method

tmm1

# Poor Man's Fiber (API compatible Thread based Fiber implementation for Ruby 1.8)
# (c) 2008 Aman Gupta (tmm1)

unless defined? Fiber
  require 'thread'

  class FiberError < StandardError; end

  class Fiber
    def initialize

tmm1

>  - In ruby 1.8.x, what is the functional difference between rb_thread_schedule and rb_thread_select?

rb_thread_schedule() is the guts of the thread scheduler, it traverses
over the linked list of threads (several times) to find the next one
to switch into. The function is long (250 lines) and messy, and covers
all the combinations of thread status (RUNNABLE, TO_KILL, STOPPED,
KILLED) and wait state (FD, SELECT, TIME, JOIN, PID).

If there are no threads doing i/o or waiting on a timeout,
rb_thread_schedule() picks another thread from the list (considering

tmm1

require 'rubygems'

# diff --git a/lib/rubygems/version.rb b/lib/rubygems/version.rb
# index 50d8204..4962ce1 100644
# --- a/lib/rubygems/version.rb
# +++ b/lib/rubygems/version.rb
# @@ -295,12 +295,16 @@ class Gem::Version
#      rhsize = other.segments.size
#      limit  = (lhsize > rhsize ? lhsize : rhsize) - 1
#  

tmm1

Ruby 2.1.0 in Production: known bugs and patches

Last week, we upgraded the github.com rails app to ruby 2.1.0 in production.
While testing the new build for rollout, we ran into a number of bugs. Most of
these have been fixed on trunk already, but I've documented them below to help
anyone else who might be testing ruby 2.1 in production.

@naruse I think we should backport these patches to the ruby_2_1 branch and
release 2.1.1 sooner rather than later, as some of the bugs are quite critical.
I'm happy to offer any assistance I can to expedite this process.

tmm1

tmm1

require 'rubygems'
require 'eventmachine'
require 'em-http' # gem install em-http-request
require 'yajl'    # gem install yajl-ruby

class String
  def bold
    "\033[1m#{self}\033[0m"
  end
end

tmm1

require 'rubygems'
require 'eventmachine'

module ChatClient
  def self.list
    @list ||= []
  end

  def post_init
    @name = "anonymous_#{rand(99999)}"