It's a fork of Memery gem. Original Memery uses prepend Module.new with memoized methods, not touching original ones. This approach has advantages, but also has problems, see discussion here: tycooon#1

Then again, at times the little steel“dog” with its escapement working backand forth in the ratchet which controlledthe movement of the paper frame wouldfail to do its work properly, and the car-riage would jump an inch or two, or per-haps half a line, stopping with a suddenjerk, which was calculated to make onenervous, to say the least.

And this is what I believe is happening with students and reading, at least in part. They have convinced themselves that they aren’t readers. They have convinced themselves that reading old books, especially difficult old books, is just too arduous, too boring, too pointless. They have convinced themselves that even if the books are good and soul-enriching, there are better things to be doing with their time.

Enable ActiveRecord unsigned integers to use 8 bytes instead of 4. This fixes the ActiveModel::RangeError problem where AR models with perfectly fine 8 bytes primary keys are taken for ActiveModel::Type::Integer with a default limit of 4 bytes.

I'm going to close this thread which will no longer be monitored. In case you want to report a new issue or you can’t make project to be internal, please do not hesitate to create a new Issue Tracker thread describing your situation.

Windows 10 currently (01.01.2020) doesn't support Unicode country flags, and displays two-letter country codes instead of emoji flag images.

Stop autoclosing of PRs While the idea of cleaning up the the PRs list by nudging reviewers with the stale message and closing PRs that didn't got a review in time cloud work for the maintainers, in practice it discourages contributors to submit contributions. Keeping PRs open and not providing feedback also doesn't help with contributors motivation, so while I'm disabling this feature of the bot we still need to come up with a process that will help us to keep the number of PRs in check, but celebrate the work contributors already did instead of ignoring it, or dismissing in the form of a "stale" alerts, and automatically closing PRs.

I don't understand why it should be so hard to keep issues open / reopen them. That's just going to cause people to open a duplicate issue/PR — or (if they notice in time) cause people to add extra "not stale" noise when the bot warns it's about to be closed. Wouldn't it be preferable to keep the discussion together in one place instead of spreading across duplicate issues? (Similarly, moving the meta conversation about an issue out to a completely separate system (Discord) seems like the wrong direction, because it wouldn't be visible to/discoverable by those arriving at the closed issue.) I get how it's useful to have stale issues not cluttering the list. But if interes/activity later picks up again, then "stale" is no longer accurate and its status should be automatically updated to reflect its newfound freshness... like it did back here:

Rails 7 supports Postgres enums natively (more info)

The fixed filing place needs no system. It is sufficient that we give every slip a number which is easily seen (in or case on the left of the first line) and that we never change this number and thus the fixed place of the slip. This decision about structure is that reduction of the complexity of possible arrangements, which makes possible the creation of high complexity in the card file and thus makes possible its ability to communicate in the first place.

Rails' inability to automatically route my link_to and form_for in STI subclasses to the superclass is a constant source of frustration to me. +1 for fixing this bug.

Closing this PR since it's been sitting here for over 2 years. Can reopen if need be.

Happy Third Birthday #24728!

Closing this because it's obviously not going to get fixed and it's cluttering my open issues

17.3. Fixed point

Can you re-open this until we fix it?

The typical clinical course of an epidural hematoma is an initial loss of consciousness, a lucid interval, and recurrent loss of consciousness with an ipsilateral fixed and dilated pupil. While decompression of subdural hematomas may be delayed, epidural hematomas require evacuation within 70 minutes.

Unlike similar tools that are scheduled to take backups at a fixed time of the day, Timeshift is designed to run once every hour and take snapshots only when a snapshot is due. This is more suitable for desktop users who keep their laptops and desktops switched on for few hours daily. Scheduling snapshots at a fixed time on such users will result in missed backups since the system may not be running when the snapshot is scheduled to run. By running once every hour and creating snapshots when due, Timeshift ensures that backups are not missed.

fixed-point

This model of microservices that register themselves to a global registry will have a lot of advantages when it comes to building one or multiple applications using a microservice architectural approach. Eureka on its own won't have that much of use, but as you'll see in the future blogposts, Eureka will be the key element to locate all of our microservices.