When we have our git rev-parse examine our Git repository to view our origin/HEAD, what we see is whatever we have stored in this origin/HEAD. That need not match what is in their HEAD at this time. It might match! It might not.

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

instead of inlining the images, the image URL’s (and captions) are read from a .yaml file. The URL of the yaml file is passed as an argument when loading the page. The .yaml file as well as the images should be publicly served.

Oh I see whats happening, we actually have specs for this but they're not correct

It really only takes one head scratching issue to suck up all the time it saves you over a year, and in my experience these head scratchers happen much more often than once a year. So in that sense it's not worth it, and the first time I run into an issue with it, I disable it completely.

5.7 Prioritize by weighing the value of additional information against the cost of not deciding.

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:

Now all I had learned on my travelsFell into a new kind of placeEven maths and hard sciencesNo longer at oddsWith Art or HumanityBut serving to showA side of the storyInsufficient to stand on its own

Now I'm puzzled by the apparently biggest obstacle to implementation of this feature: possible misuse. I love ruby community, but sometimes saving the dummies' asses goes a bit too far.

build a browser that comes pre-installed with node.js

Embryonal rhabdomyosarcoma (ERMS) of the uterus has recently been shown to frequently harbor DICER1 mutations.

The DICER1 syndrome is an autosomal dominant tumor‐predisposi-tion disorder associated with pleuropulmonary blastoma, a rare pediatric lung cancer

ransack is a very dirty solution that completely integrates the Searching, Sorting, and Views as requirements of eachother

I believe this is partly due to a militant position on free software. Some advocates believe so strongly that users should be able to recompile their software that they force them to do so. They break libraries seemingly on purpose just to say, “Recompile! Oh you can’t? That’ll teach you to use binary software!” Of course users don’t want to recompile their software, but what users actually want is usually lost on GNOME developers.

They claim that they deduplicate runtimes. I question how much can really be shared between different branches when everything is recompiled. How much has /usr changed between releases of Ubuntu? I would guess just about all of it.

not all modern implementations have implemented this specification correctly (e.g., Safari)

Note that this is a breaking API change in the libraries (more information in the README.md). It does not affect the backwards compatibility of the protocol itself.

Hence an email address/mailbox/addr-spec is "local-part@domain"; "local-part" is composed of one or more of 'word' and periods; "word" can be an "atom" which can include anything except "specials", control characters or blank/space; and specials (the *only* printable ASCII characters [other than space, if you call space "printable"] *excluded* from being a valid "local-part") are: ()<>@,;:\".[] Therefore by the official standard for email on the internet, the plus sign is as much a legal character in the local-part of an email address as "a" or "_" or "-" or most any other symbol you see on the main part of a standard keyboard.

"+" is a completely valid character in an email address; as defined by the internet messaging standard published in 1982(!) RFC 822 (page 8 & 9)... Any website claiming anything else is wrong by definition, plus they are prohibiting me and many fellow anti-spam activists from tracking where inbound spam comes from:

I used Publii for my blog, but it was very constraining in terms of its styling

Even though not all code smells indicate real problems (think fluent interfaces)

As the only way to find outif something is worth reading is by reading it (even just bits of it), itmakes sense to use the time spent in the best possible way. Weconstantly encounter interesting ideas along the way and only afraction of them are useful for the particular paper we started readingit for. Why let them go to waste? Make a note and add it to your slip-box. It improves it. Every idea adds to what can become a criticalmass that turns a mere collection of ideas into an idea-generator.

That's like the example i wrote, and i think it's very ugly. It's annoying when frameworks are very elegant in demos and presentations but then that elegance disappear when you have to write real world code.

Seems easy, right? How about the below code, what will it print? new Promise((_, reject) => reject(new Error('woops'))). catch(error => { console.log('caught', err.message); }); It'll print out an unhandled rejection warning. Notice that err is not defined!

We cannot make the above statement reactive because we touch tmpCopyAsTemplates.

 "$; foo = bar.a" means that you expect foo to always be whatever bar.a is is not true

Raising an Independent Child

In Markdown, we literally built a Tower of Babel.

This post is like a year old... Does not matter ,

Yep, we experimented with this, but what we found is that you loose most of Svelte's niceness like slots, and instead you'll pass around deeply nested objects.

This is actively being worked on - for those interested you can follow the progress in https://github.com/snapcore/snapd/pull/10836

Seeing how this has been treated for 4.5 years makes this seem like a pretty dysfunctional project. Please have mercy on your poor users and fix this.

After 5 years there's still no fix. This is so annoying. I'm now getting rid of all snap packages and installing deb variants instead. Finally I'll purge snap and if these weird decisions keep on going I'll also move to another distro. Common Canonical. Seriously?

However, unless my feeble brain is feeble, this looks like a valid use case and I might not be alone.

Regarding the first example, we have to put aside the fact that we (from inspection) can see the runtime behavior of this code by executing it in our heads.

fresh (i.e. provably do not have properties we don't know about)

that is not ideal, since for example 'Cookie' is a forbidden header name, so I have to start worrying about env in load, which is kind of contra to its design.

Arguments for “it depends.”

I find Alt + right-click + drag to be the most convenient way to do this.

Maybe there’s a technical term that I’m not aware of for this type of centered line-splitting heading.

The classic SPA example is a to-do list. But, you know what? I don't like to-do lists. They make me think about all the things I have to do, many of which I don't want to do.So why don't we make a To-Don't List app? That way we can list all the things we're not going to do. Ever.

From my point of view, this approach will help you to write cleaner code. Also, it will help to maintain the project. For instance, moving a file from the current directory to another will cause fewer problems, because every file uses an absolute path instead of a relative one. Last but not least, it helps you during development.

Let's not get over-excited. Actually, we're only part-way there; you can compile this code with the TypeScript compiler.... But is that enough?I bundle my TypeScript with ts-loader and webpack. If I try and use my new exciting import statement above with my build system then disappointment is in my future. webpack will be all like "import whuuuuuuuut?"You see, webpack doesn't know what we told the TypeScript compiler in the tsconfig.json.

I am not going to do Webpack support. I’ve been pretty lenient in the past and answered most Webpack support questions, but it takes a lot of my time that I could have spent on more important things. I will instead refer users to the Webpack support channels.

⚠ Node Sass does not work with Yarn PnP feature and doesn't support @use rule.

The Rails server will also compile your assets if the dev server is not running, but this is much slower vs running separate processes and not recommended.

Webpacker used to configure Webpack indirectly, which lead to a complicated secondary configuration process. This was done in order to provide default configurations for the most popular frameworks, but ended up creating more complexity than it cured. So now Webpacker delegates all configuration directly to Webpack's default configuration setup.

An extensible plugin architecture allows for customizing your workflow or even making Yarn a package manager for non-JavaScript projects.

But it is always important to remember that those are not language concepts. Those are community concepts that only exist in our heads and in the names of some library methods.

Note: when I wrote above that "there is no such thing as X", what I meant was that "there is no such thing as X in the Ruby language". That does not mean that those concepts don't exist in the Ruby community.

The question is similar but its in a Rails context. The solutions would answer my question, but I'm almost certain that he could probably leverage Arel to solve his problem. The question I posted was designed purely as a Ruby question so that it was easier to search for. You might want to suggest an edit of the title of his question because it didn't show up when I searched for a solution to my problem.

Yes, unfortunately the other question has a misleading and completely irrelevant Rails context and might be harder to find for some people. IMHO, it's still a perfect content duplicate, although not a topic one. Answers are also equal. Anyways, still a good question of yours.

It seems to me (N.b. what do I know about this? Nothing!) that the best solution would be to tweak the 'Change Password' process so that it also updates the 'Passwords and Keys'>Passwords>Login folder's properties.

Good catch, @Hokascha. The project claims support for cross-domain iframes, but reading the docs reveals that it does still require server access to the embedded domain.

Always use the word ‘Africa’ or ‘Darkness’ or ‘Safari’ in your title.

historicalknowledge is foundational to beingable to understand ourselves as humans.

In every case, Psychol-ogy as a modern scientific discipline producesknowledge that changes the individuals, soci-eties, and cultures in which it is embedded, andthese changes then feed back into psychologicaltheory and practice.

I'd like to think this issue isn't quite a duplicate

That should work as expected and not be too verbose (or at least it doesn't repeat string literals anywhere)

If this was true, a paper should have been cited. Like all the other people did for their letters

“We need to find ways to meet our customers’ needs and ambitions of reducing emissions to remain relevant for them.

3. The no-keyword-arguments syntax (**nil) is introduced You can use **nil in a method definition to explicitly mark the method accepts no keyword arguments. Calling such methods with keyword arguments will result in an ArgumentError. (This is actually a new feature, not an incompatibility)

apart from [Websockets], which is unnecessarily complex for non-browser applications

Please note that the strategy: :build option must be passed to an explicit call to association, and cannot be used with implicit associations:

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.

(The null result should not be confused with a SQL NULL; see the examples.)

All safe methods are also idempotent, but not all idempotent methods are safe. For example, PUT and DELETE are both idempotent but unsafe.

Dependencies are hoisted, meaning they get installed in the root node_modules folder. This is done for performance reasons: if a dependency is shared by multiple packages, it gets saved only once in the root.

Do not use aria-orientation attribute for standard list (i.e., role="list"), use component's vertical property to set the orientation to vertical.

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

This kind of error handling does express error state (either via HTTP 500 or by the top-level "errors" key), but it doesn’t take advantage of GraphQL’s type system and can only express one error at a time.

Unfortunately, even though this bug/request was opened in 2016, this feature is still not implemented in ruby-install.

Cuprite is a pure Ruby driver (read as no Selenium/WebDriver/ChromeDriver dependency) for Capybara.

Ferrum connects to the browser by CDP protocol and there's no Selenium/WebDriver/ChromeDriver dependency.

It’s easy to create bugs because the environment is a somewhat degenerate settings database.

Note: Instead of storing a user’s ID in the session cookie you could store a JWT, but I’m not sure what that buys you. However, you may be using specific JWT claims that make this worthwhile.

For me the diagrams make it easier to talk about what the tests do without getting bogged down by how they do it.

When mocking is deemed profitable:

I don't think it is too clever. I think it solves the problem idiomatically. I.e., it uses reduce, which is exactly correct. Programmers should be encouraged to understand what is correct, why it is correct, and then propagate. For a trivial operation like average, true, one doesn't need to be "clever". But by understanding what "reduce" is for a trivial case, one can then start applying it to much more complex problems. upvote.

@7alhashmi: Yes, e.g. the 100 comes from the feature_values table

The field/element/path extraction operators return NULL, rather than failing, if the JSON input does not have the right structure to match the request; for example if no such key or array element exists.

Users who have installed it decided to trust me, and I'm not comfortable transferring that trust to someone else on their behalf. However, if you'd like to fork it, feel free.

Preserving history; we often find ourselves using the git blame tool to discover why a certain change was made.

Preserving commit hashes; we use commit hashes in binary names and our issue tracker; ideally, these references remain intact.

even if system scripts do not use this (I wonder why)

Note that not all of the colors in SMUI read from CSS variables, so some parts will still use the colors defined in the original Sass compile.

I am unable to change the name and URL of my Kickstarter account.

In the earlier example, I used “no-reply@” because this is, unfortunately, a common practice used by many email marketers. As a brand utilizing email, you should never expect a personal experience like email to ever be one-sided.

There's nothing to stop you from doing initializer code in a file that lives in app/models. for example class MyClass def self.run_me_when_the_class_is_loaded end end MyClass.run_me_when_the_class_is_loaded MyClass.run_me... will run when the class is loaded .... which is what we want, right? Not sure if its the Rails way.... but its extremely straightforward, and does not depend on the shifting winds of Rails.

These example are for Rails applications, but there is no dependency on Rails for using this gem. Most of the examples are applicable to any Ruby application.

I don't believe the sprockets and sprockets-rails maintainers (actually it's up to the Rails maintainers, see rails/rails#28430) currently consider it broken. (I am not a committer/maintainer on any of those projects). So there is no point in "waiting for someone else to fix" it; that is not going to happen (unless you can change their minds). You just need to figure out the right way to use sprockets 4 with rails as it is.

Actually, I've decided to stop using labels for a while. A "bug" label gives the impression that someone else is going to fix the problem. We don't have enough volunteers for that (new contributors welcome!). I try to help people working on issues, though. I've spent many hours on this one.

The other papers found no correlations between clinical symptom improvement and changes in connectivity (Abbott et al., 2013; Li et al., 2013; Posner et al., 201

If anything it thwarts separation of concerns to a degree.

According to Google (not that they are the end all of browser knowledge)

Historical negationism,[1][2] also called denialism, is falsification[3][4] or distortion of the historical record. It should not be conflated with historical revisionism, a broader term that extends to newly evidenced, fairly reasoned academic reinterpretations of history.

@H2CO3 Why did you remove your answer? It was the only one explaining what was happening. Or was it incorrect?

(Ideally the run-time library would treat a pipe in the same way as a console, but it seems that most don't.)

We also know there are known unknowns; that is to say we know there are some things we do not know.

Comedian Henny Youngman was famous for one-liners delivered in a deadpan manner. Much of his humor was both wry and dry.

Dry humor is a delivery technique. As such, it shouldn't be confused with specific types of humor or with sarcasm. Sarcasm is delivered without humor because it's generally not funny but intended to mock or convey contempt. Dry humor pertains to something funny.

Of course you must not use plain-text passwords and place them directly into scripts. You even must not use telnet protocol at all. And avoid ftp, too. I needn’t say why you should use ssh, instead, need I? And you also must not plug your fingers into 220 voltage AC-output. Telnet was chosen for examples as less harmless alternative, because it’s getting rare in real life, but it can show all basic functions of expect-like tools, even abilities to send passwords. BUT, you can use “Expect and Co” to do other things, I just show the direction.

I don't know if I am allowed to link here

This is hard because Apple does not want you to and a failed installation might render the ipad useless.

We also know people need a good sized group and time to see the impact and value of a platform like Stack Overflow for Teams. Our previous 30 day free trial of our Basic tier wasn’t long enough. Now, Stack Overflow for Teams has a free tier for up to 50 users, forever.