I recommend using the term “parallel” when the simultaneous execution is assured or expected, and to use the term “concurrent” when it is uncertain or irrelevant if simultaneous execution will be employed.

multiple sub-tasks of a task

Concurrency is about dealing with lots of things at once. Parallelism is about doing lots of things at once.

A system is said to be concurrent if it can support two or more actions in progress at the same time. A system is said to be parallel if it can support two or more actions executing simultaneously.

Parallelism means that an application splits its tasks up into smaller subtasks which can be processed in parallel, for instance on multiple CPUs at the exact same time.

Concurrency means executing multiple tasks at the same time but not necessarily simultaneously.

Concurrency means that an application is making progress on more than one task at the same time (concurrently)

Mermaid allows even non-programmers to easily create detailed and diagrams through the Mermaid Live Editor.

Diagramming and documentation costs precious developer time and gets outdated quickly. But not having diagrams or docs ruins productivity and hurts organizational learning. Mermaid addresses this problem by enabling users to create easily modifiable diagrams, it can also be made part of production scripts (and other pieces of code).

a hyponym is in a type-of relationship with its hypernym

hyponym denoting a subtype

hypernym or hyperonym (sometimes called umbrella term or blanket term[1][2][3][4]) denoting a supertype

In other words, the semantic field of the hyponym is included within that of the hypernym.

Formalize your Pull Request etiquette.

Danger runs after your CI, automating your team's conventions surrounding code review.

You can use Danger to codify your team's norms, leaving humans to think about harder problems.

try to provide duplicate overlapping examples.

set up

We definitely want to have a way to monitor this "queue" as a follow-up with a Prometheus counter. This counter could be used to create alerts in case the queue grows significantly, for example: the scheduled (every 1 minute) worker cannot keep up with the deletions.

A review from the Technical Writing team before you merge is recommended. Reviews can happen after you merge.

Each commit should meet the following criteria: Have a well-written commit message. Has all tests passing when used on its own (e.g. when using git checkout SHA). Can be reverted on its own without also requiring the revert of commit that came before it. Is small enough that it can be reviewed in isolation in under 30 minutes or so.

then I saw your code, now I'm a believer 🎶

Even if the browser ignores the closing slash in void tags, it's good practice to close it because: 1. in frameworks like react js if these are not close, it creates an error 2. if you want your document to be readable by an XML parser then must close all elements

I wrote my own OAuth 2 implementation in the end, it actually wasn't that hard once you understand the spec.

We want to use the Doorkeeper gem to implement an OAuth provider in our app. However, we use 2 factor auth in the login process, so we need a way to modify the password grant to accept email, password and a 2fa token (and respond with an appropriate error if the 2fa token is required and missing).

Reuses OmniAuth strategy implementation, such as facebook or google

I'm building a Rails API with a separate web frontend app as "just another API client" (various smartphone apps to follow as well). In the previous "monolithic" version of the service, where all the server side was rolled into one Rails app

is there a more official way to deal hook in OmniAuth so we can authenticate with Facebook, Twitter, or Google?

Diversity, Equity & Inclusion Diversity enables the innovation and creativity needed to move the world forward. We are committed to creating an inclusive culture that is welcoming, respectful and provides equal opportunities for all.

2) The kanji are organized in chapters with wide themes (respectively: world, food, animals, people, body, spirit, power, learn, tools, places, journey). These chapters are in turn divided up into mini-themes dealing with each chapter (for example, different animals and ideas associated with them). This helped me a lot in mentally organizing kanji and their meanings.

Water your lawn deeply about once a week, or when the grass looks slightly wilted, providing about an inch (2.5 cm.) of water each time. Avoid frequent, shallow irrigation which results in weak roots that can’t tolerate summer heat. Don’t water if the lawn doesn’t need it.

Roots growing along the surface of the soil is equivalent to an exposed nerve: they are not protected from the environment.

Water deeply but only when the grass shows signs of stress; deep, infrequent irrigation creates strong, drought-tolerant roots. Never water every day; watering too frequently encourages shallow, weak roots and unhealthy grass. For a healthy lawn and sturdy roots, wait as long as possible before waterin

If the application credentials check out, the authorization server returns an access token to the application. Now the application is authorized to use its own account.

Checkout

I just learned today that extend apparently doesn't override class methods that are already defined, even though the extend happens later:

I don’t like that when I read the Basecamp news and had a visceral reaction, my first thought was, “Will my commit access be revoked if I share what’s on my mind?” It’s incredibly unclear what mechanisms exist to remove commit access from someone against their will, and also unclear what recourse those people can take to get it re-instated.

It can be exhausting to backchannel and “find buy-in” for every little thing.

The funny thing is that I didn’t even realize that’s what I was doing. I loved a system driven by programmers because it “made sense to me” about getting changes in.

I loved that if I “did the work”, then I got the benefits.

I loved that if I “did the work”, then I got the benefits. If there’s something in Rails I didn’t like, I felt empowered to change it.

The older you are, the harder it is to get hired; despite laws and expectations to the contrary, unconscious, and even conscious, age discrimination does exist. When you have more experience, you will often be interviewed by people who in the normal course of circumstances would be reporting to you.

Indeed, judging from the accounts of the many employees who have now gone on record about this issue, the “debates” that have been happening at Basecamp are precisely the kinds of conversations that happen when you have a diverse workforce. Different issues affect different people differently, and being able to speak freely about those differences is the hallmark of a healthy culture. But by framing these discussions as “acrimonious debates” rather than “challenging conversations,” Hansson has positioned himself not as a peacemaker, but as a tyrant hell-bent on taking his toys and going home; shutting down discussions rather than holding space for growth and discovery.

If Hansson and Fried had been able to tolerate the dissenting opinions of their own employees, they might have been in for a difficult few weeks or months, but the long-term benefit of cultivating an atmosphere of trust would have been invaluable. Instead, they decided to make their tantrum international news. In doing so, they have all but dismantled the positive reputation they spent more than a decade carefully crafting.

You are not currently logged in. This can be for a number of reasons: The system is temporarily unavailable You haven't logged into the system yet The Username or Password provided is not valid You may not have the required access level You didn't do anything for 30 minutes

Epics, issues, requirements, and others all have similar but just subtle enough differences in common interactions that the user needs to hold a complicated mental model of how they each behave.

Issues are not extensible enough to support all of the emerging jobs they need to facilitate.

Issues are starting to become cluttered as we add more capabilities to them, and they are not perfect

Using labels to show issue types is cumbersome and makes reporting views more complex.

This leads to duplicated effort and ultimately small differences between common interactions.

New functionality is typically implemented with first class objects that import behavior from issues via shared concerns.

There is not a coherent interaction model across different types of issues because we use labels for this.

Here are some problems with current issues usage and why we are looking into work items:

WI model will be built on top of the existing Issue model and we’ll gradually migrate Issue model code to the WI model.

To avoid confusion and ensure communication is efficient, we will use the following terms exclusively when discussing work items.

Example of misuse

View tasks in issues, in the Child items section.

The task is not deleted, but the two are no longer connected. It’s not possible to connect them again.

cognitively adjacent

Process the log file to determine the spread of data: cat /tmp/sslparams.log | cut -d ' ' -f 2,2 | sort | uniq -c | sort -rn | perl -ane 'printf "%30s %s\n", $F[1], "="x$F[0];'

Replace 'log' with 'clock'; do you think it should be "clockin" because you aren't "clocking" anything? Plus, if 'login' was a verb, you'd not be logging in, but logining. Eww. Or, you'd have just logined instead of logged in.

I feel very happy about them indeed because they take me to the destinations they promise (they're all nouns). Login doesn't take me to my login, which makes me sad. It does take me to a place where I can log in, however.

oh I'm fine with defective verbs. I'm not fine with inconsistency, though. Make it "Signup and login", and make it that on every SE page everywhere ever, and you can countin me.

this has nothing to do with verbification, or "verbing."

This is not an attempt to arrest the evolution of the language, but to correct mistakes.

"you can verb any noun". :) Though, comparing "ssh into a workstation" to "login to host.com", where "log in" exists, it's a bit like saying "entrance the building" when "enter the building" already works

Login is a noun, the same as breakup (suffer a breakup), backup (keep backups safe), spinoff (a Star Wars spinoff), makeup, letdown,

Sure, you can try to solve that problem by using a one-word alternative for any multi-word phrase, but that's not always possible. Instead of relying on luck, being at the mercy of copy writers, and artificially limited to only allowing one-word items, IMHO you would be better off finding a general design solution that works even for multi-word phrases. Adjusting the letter-spacing and margin between items in your list isn't that hard

Given that so much of the web environment isn't being written by writers who care, I'm increasingly seeing 'login' used as a verb.

Don’t make claims unless you can cite documentation, formalized guidelines, and coding examples to back those claims up. People need to know why they are being asked to make a change, and another developer’s personal preference isn’t a good enough argument.

OAuth, or Open Authorization is a protocol for users to authorize websites to access their information without handing over a password.

Mint as of late has made it harder for scrapers to scrape it.

However, captcha should not be happening this often.

It would completely change how I view mint.com. It would become a powerful mechanism for opening up my own access to my own financial data which is currently being locked away by my banks, credit card companies and other providers. All I get is a crappy UI from those places. Mint's UI is much better, but an API would completely change the game.

Expenses don’t get posted to your accounts instantly.

I would like something to log and tag my spending instantly.

Following. I haven’t found anything in years. I’m planning on building my own scraper for my bank this winter if I can’t find anything by then

My main issue with mint was having to correct transactions multiple times. Do it one day, do it again the next, then it finally sticks.

This question is locked and replying has been disabled.

I also wanted to include the link format in case others had trouble locating the exact settings screen; hopefully this link format works for others.1) https://admin.google.com/ [YOUR DOMAIN HERE] /AdminHome?fral=1#MobileSettings:section=setup&flyout=setup (replace [YOUR DOMAIN HERE] with your own, no spaces)

        4a. There will be a blue link there that says 'Set up Google Management   -Click ItStep 5. (your header will now say Mobile Management) Scroll down until you see the word 'Custom' it should have a blue dot next to itStep 6. You should see the word 'Android' and it should say 'Basic' to the right of it. There's a drop down box/arrow there, click it and select 'Unmanaged' and that will clear up the lock screen issues.

Isn't there some tech support at Google to cancel the requirement to enter a pinfor a screen unlock?  I've been having to do this dozens of times a day for monthsand it is driving me crazy!

How do I turn off the requirement to have a lock screen?Today, I'm suddenly unable to use any Google related apps on my phone, because I am now REQUIRED to set up a lock screen on my phone. I get that you want to be super-secure for businesses using enterprise devices. I am not a business. I'm some guy who just happens to have a domain name. My only "employee" is me. I have a two email addresses: My real first name, and the shorter version that most people call me. I do NOT want a lock screen on my phone. I don't want to be forced to give myself permission to use apps on my phone. Why am I now required to add all this bull$%^? Nobody is hacking my interwebs. Give me a f#$%^& break! I don't need a lock screen. I've been using this account for everything (gmail, youtube, etc) for over five years now. I'm not interested in deleting it and going back to my gmail.com account. I'm also not interested in being forced to click multiple times just to use my phone. Let me disable it.So, how do I turn this garbage off?

URI::HTTPS.build(host: AUTH0_CONFIG['auth0_domain'], path: '/v2/logout', query: to_query(request_params)).to_s

def to_query(hash) hash.map { |k, v| "#{k}=#{CGI.escape(v)}" unless v.nil? }.reject(&:nil?).join('&') end

Dependencies: 0

Out of scope

Reducing nested structures is tiresome. Have you tried immer?

set( produce((state) => { state.lush.forest.contains = null }) ),

Don't disregard it because it's cute.

A related technique is git submodules, but they come with annoying caveats (for example people who clone your repository won't clone the submodules unless they call git clone --recursive),

git-subtrac (from the author of the earlier git-subtree) seems to solve some of the problems with git submodules.

# Do this the first time: $ git remote add -f -t master --no-tags gitgit https://github.com/git/git.git $ git subtree add --squash --prefix=third_party/git gitgit/master # In future, you can merge in additional changes as follows: $ git subtree pull --squash --prefix=third_party/git gitgit/master # And you can push changes back upstream as follows: $ git subtree push --prefix=third_party/git gitgit/master # Or possibly (not sure what the difference is): $ git subtree push --squash --prefix=third_party/git gitgit/master

I intend to keep it around and maybe fix up minor things here and there if needed, but don't really have any plans for new features at this point. I think it's great to give people the option to choose the Go port if the advanced features is what they're after.

You're set up!

tar -C /usr/local -xzf go1.19.linux-amd64.tar.gz

Why another tool?: At the moment of writting there exists no proper platform-independent GUI dialog tool which is bomb-proof in it's output and exit code behavior

the braking change documention

nodemon will automatically know how to run the script even though out of the box support for processing scripts

doesn't know if .env is a hidden file with no extension or a *.env without a filename.

depended on about 3 million projects

The vendor prefix (vnd.) indicates that it is custom for this vendor.

The +json indicates that it can be parsed as JSON, but the media type should define further semantics on top of JSON.

then two different listeners/renderers switching magically between each other based on the header being present or not, without the end user being informed or clear about this

Thus my docs recommendation of public function beforeFilter(Event $event) // do not render out the now inconsistent one for is(json) if (!$this->request->is('jsonapi')) { throw new NotFoundException('Invalid access, use application/vnd.api+json for Content-Type and Accept.'); } } to specifically only whitelist the desired jsonapi for the general use case.

A default baked app has all those included. Thats why I am saying this - it is by default an issue we should and need to address :)

If you're using JavaScript for writing to a HTML Attribute, look at the .setAttribute and [attribute] methods which will automatically HTML Attribute Encode. Those are Safe Sinks as long as the attribute name is hardcoded and innocuous, like id or class.

If you're using JavaScript for writing to HTML, look at the .textContent attribute as it is a Safe Sink and will automatically HTML Entity Encode.

In a clickjacking attack, the attacker creates a malicious website in which it loads the authorization server URL in a transparent iframe above the attacker’s web page. The attacker’s web page is stacked below the iframe, and has some innocuous-looking buttons or links, placed very carefully to be directly under the authorization server’s confirmation button. When the user clicks the misleading visible button, they are actually clicking the invisible button on the authorization page, thereby granting access to the attacker’s application. This allows the attacker to trick the user into granting access without their knowledge.

it's also one of the smartest games I've ever played and I can't recommend it enough if you enjoy system-driven narrative, which it handles exquisitely.

The Quiet Sleep has 'cult classic' written all over it. It uses strategy, management, and tower defence mechanics to take you inside someone's head in a way that I don't think has ever been done before. It's really a bold experiment, and you'll be glad you played it.

Well I would like to express my huge concern regarding the withdrawal of support for the SMB 1.0 network protocol in Windows 11, and future versions of the Microsoft OS, as there are many, many users who need to make use of this communication protocol, especially users households, since there are hundreds of thousands of products that use the embedded Linux operating system on devices that still use the SMB 1.0 protocol, and many devices, such as media players and NAS, that have been discontinued and companies no longer update their firmware.

With Windows 10 version 1511, support for SMBv1 and thus NetBIOS device discovery was disabled by default. Depending on the actual edition, later versions of Windows starting from version 1709 ("Fall Creators Update") do not allow the installation of the SMBv1 client anymore. This causes hosts running Samba not to be listed in the Explorer's "Network (Neighborhood)" views.

Since NetBIOS discovery is not supported by Windows anymore, wsdd makes hosts to appear in Windows again using the Web Service Discovery method.

Windows 10 if configured the way Microsoft wants you to configure it by default will never be able to "discover" your Ubuntu samba shares.

to see the changes the commands make. Among the commands, I'd like to use useradd, userdel, usermod, groupadd, groupmod, & groupdel. And, as I'm guessing you are understanding, these are just the ones I've read about today. If I can get away without modifying any files directly, I'd rather be able to do that because it means I'll have a strong grasp of the commands, and I'd be able to learn the editing of smb.conf (& the other files) by seeing how it/they change as I use the commands.

I'm trying to learn enough about Samba that I'm able to do complete administration from the command line. That's a big task, I know, like learning DOS when all I know is French (I know far more DOS than French, but that's the idea).

I have definitely looked at some of the Samba.org instructions. The problem is mine - I'm either too busy dealing with the kids in the morning, or too tired in the evenings, to be able to - within my realm of patience - find what I need, implement it, test it, and confirm that it works or try something else. Finding it, and recognizing that I've found it, is usually the hard part. That's why a book does me worlds of good - I can read it during the work day when I'm taking a few minutes break, and it's uninterrupted concentration time.

sudo usermod -aG sambashare $USER

Extensions from Ruby are noted in the following list.

Component is not maintained anymore.

The custom title bar has been a success on Windows, but the customer response on Linux suggests otherwise. Based on feedback, we have decided to make this setting opt-in on Linux and leave the native title bar as the default. The custom title bar provides many benefits including great theming support and better accessibility through keyboard navigation and screen readers. Unfortunately, these benefits do not translate as well to the Linux platform. Linux has a variety of desktop environments and window managers that can make the VS Code theming look foreign to users.

convert to URL query parameters with the qs library

If you insist on having the user id in the version table, you can do this: ActiveRecord::Base.transaction do @user.save! @user.versions.last.update_attributes!(:whodunnit => @user.id) end

Wouldn't it be easier to do a squash merge instead? git merge --squash [branch] Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand Brack Carmony Brack Carmony Brack Carmony Follow Joined Jan 3, 2022 • Jan 3 Dropdown menu Copy link Hide Report abuse It would, if the assumption that every commit in the chain is what you want, this lets you keep the power of the rebase available if you want to cherry-pick commits or any of the other crazy features it seems to let you use.

NOTE: Setting both is not necessarily needed, but some programs may not use the more-correct VISUAL. See VISUAL vs. EDITOR.

Would be more of a neutral rating for me but seeing that I have only two options (or no review at all), I'll go with the upvote for encouragement as they do appear to be putting some effort into the game.

This is actually the most correct answer, because it explains why people (like me) are suddenly seeing this warning after nearly a decade of using git. However,it would be useful if some guidance were given on the options offered. for example, pointing out that setting pull.ff to "only" doesn't prevent you doing a "pull --rebase" to override it.

I appreciate the time and effort you put into your answer, but frankly this is still completely incomprehensible to me.

one should not upgrade a production environment without extensive testing. I prefer to not upgrade prod at all. Instead, I create a new instance with latest everything, host my apps there, test everything out, and then make it production.

Beyond memory leaks, it's also really useful to be able to re-run a test many times to help with tracking down intermittence failure and race conditions.

I don't understand the hesitation here to accept a really useful addition to rspec. Maintenance burden. Forseen internal changes required to do it. Unforseen internal changes required to do it. Formatter changes to handle new output status for a spec that passed and failed It's simply not a previously design use case of RSpec. It will be hacky to implement.

We already have a very wide configuration API. The further we expand it the more unwieldy it becomes for users. At this point we generally require new features to be implemented first as extension gems, and then to see support, before considering including them in core.

I created a gem called rspec_n that installs an executable that will do this. It will re-run the test suite N times by default. You can make it stop as soon as it hits a failing iteration via the -s cli option. It will display other stats about the iterations as well.

You can pass any options to puma via the server setting Capybara.server = :puma, { queue_requests: true }

This very much appears to be a bug or design flaw in puma - The fact that a persistent connection ties up a thread on the chance a request might come over that connection seems like not great behavior. This would really only be an issue when puma is run with no workers (which wouldn't be done in production) but it still seems a little nuts.