Not everyone has time to adhere to the specific coding styles for a project, so if you can't do a full blown pull-request, there is NOTHING wrong with opening a pull-request that only has the intention of showing the author how you solved the problem.

It is not helpful to use the term "terrorism" in a war when the White House only ever applies it to one side. Better to remind both Hamas and the Israeli government that humanitarian law makes it a war crime to target or indiscriminately fire on civilians.

Using --ours did what I was after, just discarding the incoming cherry picked file. @Juan you're totally right about those warning messages needing to say what they did't do, not just why they didn't do it. And a bit more explanation that the ambiguity from the conflict needs to be resolved (by using --ours, etc) would be super helpful to this error message.

Note though, that this only works when you're already using git for your dependency

This was originally disallowed because #5907 was opened asking for different behavior in this situation that we didn't want to allow, and so we decided to make it a compiler error rather than have confusing behavior in that situation.

I just spent a day dismantling a model, trying to find the cause of the silent rollback - taking out every association, every validation, every callback, whittling down all the code in the transaction, only to finally discover that it was return true that was the cause of it all. Or yes, an exception!

If you paste a message from somewhere else that spans multiple lines, you can quote that without having to manually prepend > to every line!

No option is perfect here, but a warning seems like a decent compromise unless there's a whole bunch of other plugins that break

Once zeitwerk mode is enabled and the configuration of eager load paths double-checked, please run: bin/rails zeitwerk:check

the last "All is good!" is what you are looking for.

To verify the application is running in zeitwerk mode, execute bin/rails runner 'p Rails.autoloaders.zeitwerk_enabled?'

Indeed, if MoneySerializer was reloadable, starting with Rails 7 such initializer would raise a NameError.

because it is in a central location and contributed to by many people, problems are found quickly, and fixes are for everyone—not just one specific template.

Caution: This is NOT the current local time in most locations in that time zone North America: Only some locations are currently on MST because most places in this time zone are currently on summer time / daylight saving time and are observing MDT.

If you forget to define x in the object you pass as the second argument, or if there's some similar bug or confusion, you won't get an error -- just unexpected results.

For every mile we don't drive, our air gets a little bit cleaner. There are many ways to drive less- walking, biking, taking transit, telecommuting, carpooling, and more. Driving less can also save you money and improve your emotional and physical health. Working from home has been gaining popularity and may offer other benefits such as improved productivity. 

We’ve enabled deprecation warnings by default when running specs. Making these warnings more visible to developers helps upgrading to newer Ruby versions.

wanted to surface to the user during SSR if the client-side call would likely fail due to cross-origin fetching, credentials, etc.

I would argue though that crashing is better than quietly providing unexpected behavior.

MJML has been designed with responsiveness in mind. The abstraction it offers guarantee you to always be up-to-date with the industry practices and responsive. Email clients update their specs and requirements regularly, but we geek about that stuff - we’ll stay on top of it so you can spend less time reading up on latest email client updates and more time designing beautiful email.

I`m getting "rsync warning: some files vanished before they could be transferred (code 24) at main.c(1518) [generator=3.0.9]" on one of my systems i`m backing up with rsync , but rsync doesn`t show WHICH files.

0 of 0 users found this helpful

27 of 31 users found this helpful274

The best place to let the developers know, and track those bugs is in the bug tracker. There are hundreds of forums online, all over the place in many languages. We can’t be expected to read all of them. Anyone with a launchpad ID (thus, anyone who has an account on this discourse instance) has the capability to file a bug. I’d strongly recommend doing so, for each specific issue. Taking just a few minutes to do that will help tremendously.

Questions act as mini "self-tests" for students.

The change would be useful to other people as-is.

Get told in big red letters when the dependency changed and you need to check that your fix is still valid.

You can determine which openssl.cnf is being used by adding a spurious XXX to the file and see if openssl chokes.

`Module ${a.id} may be unable to evaluate without ${b.id}, but is included first due to a cyclical dependency. Consider swapping the import statements in ${parent} to ensure correct ordering`

Svelte forces you do to do all kinds of things in a very specific way (as does every other framework/library), those constraints generally make for a better experience.

More in-depth examples definitely sound like a good idea. I've seen cookbooks quite a few times already and they are always helpful.

Since this issue seems to pop up periodically, it would be useful to turn this into a warning. It may not be elegant, but it prevents surprise blank screens due to a navigation error.

Jean Renoir

The node-resolve plugin doesn't like failing to resolve module IDs (because it usually indicates a bug, like you forgot to install the package in question), so it will throw an error rather than letting Rollup print a warning.

using modulesOnly behaves exactly as expected when it warns you that the listed npm libraries do not use the ES6 format and are in fact ignored. This option is meant as a way to determine if you still have commonjs libraries in your dependencies that require special treatment via rollup-plugin-commonjs. Your code will probably not work since the listed dependencies will be missing. You should remove modulesOnly and instead add rollup-plugin-commonjs.

You oftentimes see packages list react as a peer dependency. Since this prevents react from being installed into that package's node_modules, this is another way of preventing Rollup from bundling the module. This is also nice _if_ you want the application to install react from npm, because if an application forgets to install a peer dependency, npm will issue a warning.

When the message say function was called outside component initialization first will look at my code and last at my configuration.

i feel it should get a runtime warning / error, if it returns something besides function or undefined.

Ideally: Only let a parent control those specific CSS properties, and never let a child use them on the root element.

margin, flex, position, left, right, top, bottom, width, height, align-self, justify-self among other is CSS properties that should never be modified by the child itself. The parent should always have control of those properties, which is the whole reason I'm asking for this.

Actions aren't necessary, otherwise they would have been implemented from the start. But they do allow for easier code-reuse and better shared libraries without exploding/complicating the ecosystem.

This is a little confusing to describe. An example:

By adding constraints, we have managed to create a simple API and a performant output.

Instead, my purpose is to illustrate why an alternative approach — based on Single File Components with real CSS — is so damn delightful.

Designing with constraints. Using inline styles, every value is a magic number. With utilities, you're choosing styles from a predefined design system, which makes it much easier to build visually consistent UIs.

preventDefault — calls event.preventDefault() before running the handler. Useful for client-side form handling, for example. stopPropagation — calls event.stopPropagation(), preventing the event reaching the next element passive — improves scrolling performance on touch/wheel events (Svelte will add it automatically where it's safe to do so) capture — fires the handler during the capture phase instead of the bubbling phase (MDN docs) once — remove the handler after the first time it runs self — only trigger handler if event.target is the element itself

Just to make this clear, I'm on the side that adding strict rules doesn't necessarily improve a situation. Especially with something that is subjective like a commit message.

It's amazing what new can do for clarity. This is exactly what I meant, but couldn't figure out how to phrase at the time.

Unhelpful is the motivation writing app that tries to help instead of hurt.

People cannot see exhaustive documentation and code examples on their own file system. They would have to visit the repository (which also requires an internet connection).

I want to be very clear that I’m not talking about kids of marginalized identities or communities who have never for one second had the luxury to choose whether to fight or not

Press Command+Shift+Dot

Is each of the following examples an outcome or an impact? Choose the correct answer.

Something we often don’t have time for in practice is evaluating how things are going internally with our programs. How’s it going with all the documentation our agency asks us to complete? Is the space we’re using for our group sessions facilitating client engagement? Is the way we communicate with volunteers effective?

(Pro-tip: logic models are a heck of a lot easier to make in Excel than Word.)

Let’s think back to our example from the start of the chapter

The reality of the grant funding environment is that funders want to see that their money is not only being used wisely, but is having a material effect on the target population. This is a good thing, because we want to know our programs have a positive effect on clients and communities and not just keep running a program because it’s what we’ve always done. (Consider the ethical implications of continuing to run an ineffective program.) It also forces us as practitioners to plan grant-funded programs with an eye toward evaluation. It’s much easier to evaluate your program when you can gather data at the beginning of the program than when you have to work backwards at the middle or end of the program.

Realistically, as a practitioner, you’re far more likely to engage in program evaluation than you are in research.

There are two ways to think about what counterbalancing accomplishes. One is that it controls the order of conditions so that it is no longer a confounding variable. Instead of the attractive condition always being first and the unattractive condition always being second, the attractive condition comes first for some participants and second for others.

The three most common versions of the t-test are: one-sample t-test, independent samples t-test, and the paired samples t-test. The one sample t-test is used to test whether a sample mean could have come from a particular population. The independent samples t-test is used in between-subjects designs, to test whether the sample mean in one condition is different from the sample mean in another condition. The paired samples t-test is used in within-subjects designs, to test whether the sample mean in one condition is different from the sample mean in the other condition.

ecall that internal validity is the extent to which the design of a study supports the conclusion that changes in the independent variable caused any observed differences in the dependent variable.

is chapter, we look at how to present your research effectively.

cles For journal articles, the generic format for a reference is as follows: Author, A. A., Author, B. B., & Author, C. C. (year). Title of article. Title of Journal, xx(yy), pp–pp. doi:xx.xxxxxxxxxx

Imagine if chemistry could tell us only that there is some relationship between the temperature of a gas and its volume—as opposed to providing a precise equation to describe that relationship.

(Note that the term error here refers to random variability and does not imply that anyone has made a mistake. No one “commits a sampling error.”)

Learning Objectives

Consider, for example, an actual study on “personal space” conducted in a public men’s room (Middlemist, Knowles, and Matter 1976). The researchers secretly observed their participants to see whether it took them longer to begin urinating when there was another man (a confederate of the researchers) at a nearby urinal. While some critics found this to be an unjustified assault on human dignity (Koocher 1977), the researchers had carefully considered the ethical conflicts, resolved them as best they could, and concluded that the benefits of the research outweighed the risks (Middlemist, Knowles, and Matter 1977). For example, they had interviewed some preliminary participants and found that none of them was bothered by the fact that they had been observed

Know and Accept Your Ethical Responsibilities

Counterbalancing

but you found that this had no effect on the number of happy or sad childhood events they recalled. This could be because being in a happy or sad mood has no effect on memories for childhood events. But it could also be that the music was ineffective at putting participants in happy or sad moods. A manipulation check—in this case, a measure of participants’ moods—would help resolve this uncertainty