If you give the programmer a long list of inputs and actions, and they fire up their own copy of the program and nothing goes wrong, then you haven't given them enough information.

Log to stdout. Shut down on TERM/INT. Reload config on HUP. Provide the necessary config file for your favorite init system to control your daemon.

here must be a self now I'm not talking about a minimal kind of self a pre-reflective kind of self I'm talking about a socio-cognitive construct like philosophers like Dennard 00:03:30 and others have suggested a construct which is of a cognitive type it may also be of a social kind as suggested by social scientists like for example Wolfgang Prince Ian hacking and 00:03:42 even some neuroscientists like Michael Graziano have proposed scientific approaches to the notion of self

without the need of external requirements and only rely on default installed tools

If you develop a pure frameworkless Ruby application or embed Ruby and don't need any of the listed integrations, you can depend on the airbrake-ruby gem and ignore this gem entirely.

Rack::Session was moved to a separate gem. Previously, Rack::Session was part of the rack gem. Not every application needs it, and it increases the security surface area of the rack, so it was decided to extract it into its own gem rack-session which can be updated independently.

Compose V2 has been re-written in Go, which improves integration with other Docker command-line features, and allows it to run natively on macOS on Apple silicon, Windows, and Linux, without dependencies such as Python.

So transcriptor aims to do less, and impose the bare minimum of cognitive load needed to convert a REPL interaction into a test. The entire API is four functions:

Doing everything PID 1 needs to do and nothing else. Things like reading environment files, changing users, process supervision are out of scope for Tini (there are other, better tools for those)

A little copy paste is better than a little dependency.

Data, matrix multiplications, repeated and scaled with non-linear switches. Maybe that simplifies things a lot, but even today, most architectures boil down to these principles. Even the most complex systems, ideas, and papers can be boiled down to just that:

Dependencies: 0

'm open to considering adding this to core but it's such a rare need (given that you're the first to ever ask for it, and I've never wanted or needed an around(:all) hook) I have a preference for keeping it in external gem if we can do so w/o hooking into rspec's internals

This is the theory of the extended mind, introduced more than two decades ago by the philosophers Andy Clark and David Chalmers. A 1998 article of theirs published in the journal Analysis began by posing a question that would seem to have an obvious answer: “Where does the mind stop and the rest of the world begin?” They went on to offer an unconventional response. The mind does not stop at the usual “boundaries of skin and skull,” they maintained. Rather, the mind extends into the world and augments the capacities of the biological brain with outside-the-brain resources.

HTTP REST seems like an "out of external dependency" way to go.

In order to move forwards with this issue I'll need an example app that reproduces the behavior (https://www.codetriage.com/example_app).

But I can describe a simple reproduction case to demonstrate the developer inconvenience (can provide a sample app if it's helpful).

An example app is an application that is designed to reproduce a bug or demonstrate an issue.

Before a bug can be fixed, it has to be understood and reproduced. For every issue, a maintainer gets, they have to decipher what was supposed to happen and then spend minutes or hours piecing together their reproduction. Usually, they can’t get it right, so they have to ask for clarification. This back-and-forth process takes lots of energy and wastes everyone’s time. Instead, it’s better to provide an example app from the beginning. At the end of the day, would you rather maintainers spend their time making example apps or fixing issues?

Also as an aside, your REPL is far, far too complicated. You've got a much better chance of us being able to see your issue and fix it if you boil it down to just the minimum required code in order to reproduce the issue.

I am all for providing good APIs to integrate systemd's concepts with other projects, but I'd try to keep things minimal there, and focus on as few sets of APIs as possible, but then keep the quality of them high.

This is linux. Ouput first, formatting second. systemctl --no-pager -l should be the default.

The following examples are minimal, clean starting points using compose file version 2. Again they are not intended as a definitive reference.

Omitted details change everything here. There won't be circular dependency because unused import is skipped. Consider providing stackoverflow.com/help/mcve .

With the new plugin based architectue, the library has really small core. Everything else is built around as a plugin.

Of all the compile-to-languages, the one that strikes me as having the least merit is JSX. It's basically a ton of added complexity for the sake of what boils down to syntax. There are no real gains in terms of language semantics in JSX.

Made the repro above more manageable: https://svelte.dev/repl/a55ba18ceca44c898f2b011a0978de85?version=3.6.6

If you can't understand where it's coming from in the stack traces, please post screenshots or create reproducing sandboxes and we'll try to help. Most of these are probably coming from a few libraries, so the most productive thing to do is to reduce these cases and then file issues with those libraries.

Blocking users from installing unsigned extensions without offering a cross-platform way to disable the feature brings minimal security benefits while concentrating power in the hands of the browser vendor. Not even Google is this heavy-handed, they allow installing local extensions in Chrome after users enable an option, although a warning is shown on browser restarts about the presence of external extensions, which can be dismissed.

When it comes to building HTTP APIs, other frameworks weigh you down with tons of dependencies and unnecessary abstractions. Falcon cuts to the chase with a clean design that embraces HTTP and the REST architectural style.

People that join GitLab all say they already practice this iteration. But this is the value that they have the hardest time adopting. People are trained that if you don't deliver a perfect or polished thing you get dinged for it. If you do just one piece of something you have to come back to it. Doing the whole thing seems more efficient, even though it isn't.

it is worth opening a merge request with the minimal viable change instead of opening an issue encouraging open feedback on the problem without proposing any specific change directly.

problem in my app is fixed. It was not related to devise . I removed 'rails-api' gem and it started working.

In minimal media, cell growth and division slow considerably, while protein overproduction from plasmids can continue

it requires less computing power, and hence the developed educational games can be executed on the computers of most elementary schools in Taiwan; third, we wanted to avoid situating elementary school students in a complex 3D interface, which may increase the difficulty for them to learn with the game.