similar to: [RFC] The Early Demise of Myriad (Thanks To Ruby Threads)

Assuming you have Person that has_many :messages, what will it happen if it has 10000 messages? Will rails attempt to initialize @person.messages with 10000 rows from database? If that is the case, is combining finder_sql and counter_sql the common practice to avoid this? Bogdan _______________________________________________ Rails mailing list

Some of my earlier questions may have hinted ever so slightly in the direction that I''m trying to implement "enumerations". By an enumeration here I mean a class that has a fixed number of immutable instances, which in turn have essentially only a name and a position. Requirements I''ve tried to meet are - Enumeration instances should only be loaded once from the

On Fri, May 4, 2018 at 6:29 PM Walter Lee <waltl at google.com> wrote: > Hi Kostya. Thanks for the quick feedback. I will work on addressing your > comments. > > In regard to initialization checks, I can eliminate most of them by > initializing the shadow memory very early, This will be a very good way to handle this. > but I still need to do something > in two

Hey, I work on fuchsia symbolizer stuff. I don't know if you guys already have an external symbolizer but I'm working on making one right now and I plan on making one backed by LLVM that can be run host-side or target-side. I'd like to contribute that back to llvm ideally. What do you guys have so far? I have a prototype in golang that just spins up an instance of llvm-symbolizer

Hi Jake. Thanks for the info. Where can I keep up to date on the symbolizer status? Our symbolizer is provided by the Myriad vendor and integrated into its host test environment. It doesn't do much: just look for PC string patterns and symbolize them using addr2line. Thanks, Walter On Fri, May 4, 2018 at 5:36 PM Jake Ehrlich <jakehehrlich at google.com> wrote: > Hey, > I

On RAM... You chose the 32-byte shadow granularity to reduce the RAM overhead, but I am afraid this will actually increase it due to extra alignment requirements, especially if an average allocation on your typical application is small. The pointers are 32-bit, right? Given how RAM-constrained your environment is, maybe you should consider something more like HWASAN instead of ASAN.

Hi Kostya. Thanks for the quick feedback. I will work on addressing your comments. In regard to initialization checks, I can eliminate most of them by initializing the shadow memory very early, but I still need to do something in two places, __asan_handle_no_return and GetFakeStackFast. Would it be ok to have guards for those two places only? Walter On Fri, May 4, 2018 at 6:10 PM Kostya

Hi Walter, I've done a first quick scan. Overall looks reasonable, but I'd like to try reducing the number of newly introduced platform-specific ifs. Vitaly, please also take a look (once my initial comments are addressed). One outstanding issue is your problem with initialization vs checking, which requires you to insert so many ifs. Is there any chance you can avoid this? If you

I have ported ASan in LLVM to Myriad RTEMS, and I would like to upstream the port. Below is the design doc. Feedback welcome. https://docs.google.com/document/d/1oxmk0xUojybDaQDAuTEVpHVMi5xQX74cJPyMJbaSaRM The port is expected to work with modified versions of RTEMS and newlib. I have a git repo with changes to those projects, that I can make available if there is interest. Here is the patch

I''m having trouble getting backgroundrb up and running in a production environment. Here''s my backgroundrb.yml: --- port: "22222" timer_sleep: 60 load_rails: true environment: production host: XXX.XX.XXX.50 database_yml: config/database.yml acl: deny: all allow: localhost 127.0.0.1 XXX.XX.XXX.51 order: deny,allow I start BackgroundRB from XXX.XX.XXX.50 with

As far as I can tell, sending an actual HTTP PUT request to a Camping app will never parse the params out of the request body - or am I going nuts? This code seems to say only POST''s will parse the request body: elsif @method == "post" and \ e.CONTENT_TYPE == "application/x-www-form-urlencoded" q.u(C.qsp(@in.read)) end I looked for an easy spot to stick

I''m back to getting stuff to run as a Windows service, and am running in to a problem. My service (a Daemon ruby class) installs and starts fine, but when I try to stop it, I get: C:\workspaces\default\tahoe>ruby script\service stop script/service:77:in `stop'': An exception occurred in the service when handling the control request. (Win32::ServiceError) from

Running this program: require ''win32/open3'' i, o, e, pid = Open3.popen3("c:/ruby/bin/ruby.exe -e\"sleep 10\"") i.close Gives this result: C:\_co\source\build\web\temp>ruby t.rb t.rb:5: [BUG] Segmentation fault ruby 1.8.2 (2004-06-29) [i386-mswin32] This application has requested the Runtime to terminate it in an unusual way. Please

I''ve run in to an issue that I''m not sure how to address. Basically, I''m building queries with occur_default Search::BooleanClause::Occur::MUST, and using the StandardAnalyzer which does stop filtering. The stop filtering is working beautifully on the indexing side. The problem is that when the query parser parses through a query with a stop word in it, say

On Fri, May 4, 2018 at 6:21 PM Kostya Serebryany <kcc at google.com> wrote: > On RAM... > You chose the 32-byte shadow granularity to reduce the RAM overhead, > but I am afraid this will actually increase it due to extra alignment requirements, > especially if an average allocation on your typical application is small. Good point. I will run our test suite with 8-byte shadow

On Mon, May 7, 2018 at 12:35 PM Walter Lee <waltl at google.com> wrote: > On Mon, May 7, 2018 at 2:05 PM Kostya Serebryany <kcc at google.com> wrote: > >> >> >>> and GetFakeStackFast. >> >> >> Not sure. Why don't just disable stack-use-after-return? >> > > Yeah originally I was going to do that, but: > I probably

Hi Folks, I believe I tracked down the problem with the leaked DB connections. The simple fix is to put: ActiveRecord::Base.threaded_connections = false In your environment.rb file right before environment.rb does any ActiveRecord use. For example, here''s mine: ActiveRecord::Base.threaded_connections = false ActiveRecord::Base.configurations =

On Mon, May 7, 2018 at 2:05 PM Kostya Serebryany <kcc at google.com> wrote: > > >> and GetFakeStackFast. > > > Not sure. Why don't just disable stack-use-after-return? > Yeah originally I was going to do that, but: 1. We had a stack use-after-return last month that people had to debug by hand. that would have been caught by ASan with stack-use-after-return. So

The build failed. See http://cruisecontrolrb.thoughtworks.com/builds/RubyOnRails/6553 for details. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-core@googlegroups.com To unsubscribe from this group, send email to

Hi All, Alright, this release is getting closer. It''s nearly complete except the docs on my site aren''t written yet. There is however a full README with RDoc documentation and several packages including a gem release. Please check out the latest release at: * Announcement: http://www.zedshaw.com/ * README and RDoc: