Point Remix config schema to GitHub (#11757)
remix · 2026-08-28
Build Better Websites. Create modern, resilient user experiences with web fundamentals. - Point Remix config schema to GitHub (#11757) · rem
Build Better Websites. Create modern, resilient user experiences with web fundamentals. - Point Remix config schema to GitHub (#11757) · rem
Co-authored-by: Matt Brophy <matt@brophy.org>
Windows carried a second, much weaker scheduler: a single Win32 mutex as the GVL, vm->clock for preemption, its own VM barrier over vm-&g
Build Better Websites. Create modern, resilient user experiences with web fundamentals. - Include Remix version in release PR title (#11753)
Build Better Websites. Create modern, resilient user experiences with web fundamentals. - Prepare Remix 3.0.0-rc.1 (#11752) · remix-run/remi
Build Better Websites. Create modern, resilient user experiences with web fundamentals. - Add conventional render() middleware for Remix UI
Co-authored-by: Matt Brophy <matt@brophy.org>
Fix compatibility with json 3.0
Ruby on Rails. Contribute to rails/rails development by creating an account on GitHub.
Currently dates are allocated in a 40B slot plus a 32B (simple) or 48B (complex) external struct. Once embedded they entirely fit into a 80
`escape` is not valid for `JSON.parse`, activesupport has its own special handling for `as_json` stuff `ActiveRecord::Coders::JSON` is nodo
Every branch of offset_to_sec range-checks the resulting number of seconds except one path through the Rational branch: when the day fractio
https://github.com/ruby/date/commit/569565d8c0
Reject week numbers outside -53..-1 and 1..53 before conversion so integer overflow cannot make invalid input appear valid. Fixes https://g
Pass the input encoding through `date__strptime` so non-ASCII trailing data is treated as a parse failure instead of raising an encoding err
It needs keywords arguments now. I guess the method signature should really be `def decode(...)` and just pass stuff along but theres a tes
We keep a singleton of iseq wrappers (RubyVM::InstructionSequence). However, this is rarely used and causes 8 bytes to be wasted on all iseq
https://bugs.ruby-lang.org/issues/21629 https://github.com/ruby/date/commit/214024627a
Set timeout-minutes for ci.yml jobs
…safe Prefixed partial names ractor safe
This was previously flagged by ubsan because the AR_HINT_BASE_MASK constant is implicitly typed as long: hash.c:664:43: runtime error: sign
Each ractor gets its own event reporter, so it can be safely accessed within non main ractors.
Store ActionView::AbstractRenderer::ObjectRendering::PREFIXED_PARTIAL_NAMES cache in ractor local storage.
The Ruby Programming Language. Contribute to ruby/ruby development by creating an account on GitHub.
概要 半年前に以下の記事を書きました。 https://zenn.dev/avaintelligence/articles/debt-free-ai-coding-practices 基本的に前回の流れとそこまで変わってないですが一部で新しいスキルを導入したり、新しいツールを導入
The Ruby Programming Language. Contribute to ruby/ruby development by creating an account on GitHub.
coroutine_thread_terminated() leaves the Ractor's living set before handing the scheduler slot over, then keeps using th for the rest of
※この記事は、estie プログラミングコンテスト2026 懇親会の LT で紹介した内容をブログ記事として再構成したものです。 はじめに 昨今、AIのコーディング能力は飛躍的に向上し、業務におけるコーディングの大半をAIが担うようになってきました。また、プログラミングコンテ
ローカルLLMがとても盛り上がっていますね！ 特に30Bクラスのモデルが立て続けにリリースされており、とても性能が高い結果が報告されています。中には有料APIに匹敵する性能を持つモデルもでてきており、Qwen3.8-27Bはその中の一つです。 という訳で、今回はQwen3.8-2
test_global_variables called nonexistent assert_not_include?, raising NoMethodError when the suite runs with RUBY_BOX=1. Co-Authored-By: Cl
Keep complete dependency rules in upstream gems while storing only source mappings in the Ruby repository.
Keep generated rules even when manual rules cover them so source mappings can round-trip between default gems and ruby/ruby.
The option has been readable from gemrc since it was added, but the RDoc list of valid gemrc options never gained a row for it. https://git
…eans Alternation binds looser than the anchors, so `/\Atrue|false\Z/` reads as `(\Atrue)|(false\Z)` and quietly turned every gemrc string
They sit after `private`, which does not apply to constants, so both are public API today. Nothing outside the file reads them, and the sett
The two sides of one setting now disagree on `off`, so the list has to say why it stays wider here. Nothing on the way in turns `off` into a
`credential_store` was the only Bundler setting that read `off` as disabled, while every other setting goes through `Settings#to_bool`, whos