Now, our img element will render at whatever size it wants, as long as it’s narrower than its containing element. But if it happens to be wider than its container, then the max-width: 100% directive forces the image’s width to match the width of its container.

me. We recommend using cloud-based TOTP apps such as: 1Password

When setting up SAML SSO in your organization, you can test your implementation without affecting your organization members by leaving Require SAML SSO authentication for all members of the organization name organization unchecked.

I know about the interpolation brackets method, but what if the selector is deeper in the three, for example three of four layers deep? I only want its parent selector to be duplicated, not the whole selector tree.

In Rails, this is known as nested layouts, and it is a bit awkward to use. The standard Rails practice for nested layouts is complicated and involves these considerations:

Either way, I’m a fan of leaving the math in the authored code.

which I hope would extend to iframes.

When a web page is viewed on a screen with a large physical size (assuming a maximised browser window), the author might wish to include some less relevant parts surrounding the critical part of the image. When the same web page is viewed on a screen with a small physical size, the author might wish to show only the critical part of the image.

We tend to put images into flexible container elements, and the image inside is set to width: 100%;

There are ways to create aspect-ratio sized boxes in HTML/CSS today. None of the options are particularly elegant because they rely on the “hack” of setting a zero height and pushing the boxes height with padding. Wouldn’t it be nicer to have a platform feature to help us here?

t's annoying there's no native event for this yet (popstate did not work for me)

A type lockup is a typographic design where the words and characters are styled and arranged very specifically.

Danke! Danke! Danke! ich suche seit Tagen nach einer Lösung und das hier ist es!

you can use -ic option to close the window directly: $ wmctrl -ic 0x02e00085

Assumes you're using screen 0 (if you didn't know that displays could have more than one screen, ignore this).

# Allows you to just run "pry" inside a Rails app directory and get # everything loaded as rails c does. Inside a Bundler directory does # what bundle console does.

The other one is xvkbd which sends keyboard events from a lower subsystem. You can pipe keystrokes into it on STDIN. Combined with xsel, you get something like this: $ xsel | xvkbd -xsendevent -file -

The last note is that when binding commands to keyboard shortcuts it is often necessary to only have one command, not two commands connected with a pipe like we use above. You can accomplish this by invoking your piped command as a command string argumetn to a new shell like this:

X clipboard The X window system has its own clipboard. It is also known as a cutbuffer. Any text or content you mark by highlighting with the mouse cursor is automatically copied to this clipboard. This is known as the PRIMARY selection or X Window selection or just selection in X jargon. When you middle-click the mouse cursor at the destination location, this copied content is pasted there.

xdotool key --clearmodifiers ctrl+shift+v

In 13.10, Shift+Insert pastes from the selection buffer (the thing that selecting text writes to). In Libre Office, Chrome, and Firefox, Shift+Insert pastes from the clipboard. I would thus like to configure gnome-terminal to do the same.

"xclip -i /dev/null" b:2``

xdotool search --onlyvisible . behave %@ focus exec xclip -i /dev/null

The while(true) is not a problem because the loop contains sleep 0.5 which relinquishes half a second of CPU time in each of the loop's iterations. Because of that (and the lightweightness of the xsel command invocation which comprises the other part of the loop), the CPU resources taken up by the loop will be exceedingly tiny even on the slowest of Ubuntu machines.

While this isn't a solution, hopefully this explanation will make it clear WHY. In Ubuntu there are two clipboards at work. One, which everyone is familiar with, the freedesktop.org clipboard (captures Ctrl+C command) The second is a clipboard manager that has been at play since before Ubuntu even existed - X11. The X Server (X11) manages three other clipboards: Primary Selection, Secondary Selection, and Clipboard. When you select text with your pointer it gets copied to a buffer in the XServer, the Primary Selection, and awaits pasting by means of the Mouse 3 button. The other two were designed to be used by other applications in a means to share a common clipboard between applications. In this case the freedesktop.org clipboard manager in Ubuntu already does this for us.

I realize this isn't an ideal solution - but seems to be the truth to the issue. The only relevant solution I could muster is actually a hack, create a script that executes an infinite while loop that just replaces the Primary Selection with a null value.

Not what you asked, but as this question is linked to from a few places I hope someone finds this answer useful.

Its core theme - segregation. It's done in such an ingenious and innocent way - colour.

particularly affecting users of Typekit, a web typography product from Adobe Systems.[1] Within 2 months, Adobe had changed the way in which their fonts were included into third-party websites in order to avoid the undesired rendering behaviour.

Add a rule to /lib/udev/rules.d/69-libmtp.rules just after LABEL="libmtp_usb_rules": ATTR{idVendor}=="0bb4", ATTR{idProduct}=="0f91", RUN+="/bin/sh -c 'env >> /home/username/udev-phone-mtp_%E{SEQNUM}.log'"

usb-devices

lsusb -t

Element is a realtime strategy space game for people who don't have time to play realtime strategy space games.

I believe your description of the proper mixture (add 24 oz to a gallon of water) is misleading. I have used Ortho Ground Clear concentrate for years with outstanding results; the way I mix it, I include the 20% of concentrate with the 80% of water and this has never failed me. Your recommended mixture is too thin/weak to work properly.

$: bodyStyle = ` <style> body { background-color: ${backgroundColor.hex} } </style> `;

const aYearFromNow = new Date(); aYearFromNow.setFullYear(aYearFromNow.getFullYear() + 1); console.log(aYearFromNow);

Don’t make the mistake of conflating Rails secrets with Rails credentials (like I did several times before learning better!).

I found this counterintuitive because usually I try to make all my passwords, etc. different for each environment I have. I thought I would need to create a different master key for my production environment. No, I need to not create a different master key.

This has cropped up in particular when trying to create a copy of a store object when the store changes (which is a common use case with forms where you don't want to mutate the global store until the form is saved).

if ls -1qA ./somedir/ | grep -q .

The above is a POSIX-compatible test - and should be very fast

This gem is just one concern with one scope. If you want to customize it later you can simply copy the code directly into your project.

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

Creates a model for every table.

Adds custom validation methods for CHECK constraints.

Your app is specific to Postgres and proud of it. You use the mature declarative data validation that only a real database can provide.

Generates ActiveRecord models to fit a pre-existing Postgres database.

Purge the repository: sudo apt install ppa-purge sudo ppa-purge system76/pop This will remove all conflicts/depends/packages/changes done by the PPA.

sudo dpkg -i --force-overwrite /var/cache/apt/archives/pop-gnome-initial-setup_3.36.1~1612193315~20.04~4367c76_amd64.deb

Reopening this as it does seem we have broken compatibility with the oldest GPUs. Even if NVIDIA no longer support them, if they used to work it should still work.

NVIDIA periodically drops older cards off of its support matrix for NVENC/NVDEC, even if they do have the required hardware. This makes it appear, at first glance to current information sources, that Kepler GPUs do not support NVENC, so we responded as such.

level 1Fatal_Taco · 2 days ago · edited 2 days agoArch Linux, and likely most distros, are defined by these few things and are not limited to:The Linux Kernel, what type of config and modules it's been compiled with.The pre-packaged programs it comes with by default.The init.The package manager.The repositories it references.The slightly differing Linux Filesystem Hierarchy.The types of computers it runs on.

Just like any other distribution, Arch Linux is just a collection of utilities strapped together running Linux kernel under the hood.

Their dismissive attitude of, it's not an OBS bug is off-putting, how do they know? I was told I am not using their support version of Linux so they closed off my bug and told me to go on the forum.

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.

Today, on my machine, the KCalc Snap takes a full seven seconds to start up. Not just the first time after boot; every time, without fail. Seven seconds to start a calculator.

Snap is the slowest of all, largely because it stores all its data in squashfs images. Snap mounts all registered snaps at startup instead of just extracting the metadata they need beforehand, possibly in an effort to mitigate this slowness. They’re just moving part of the slow startup time to the boot time of your computer. All sorts of snap crap now shows up in mount and fdisk -l. The more snaps you have installed, the slower your computer will start, even if you don’t use them.

Software has gotten so much slower and more bloated that operating systems no longer run acceptably on spinning rust.

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.

Flatpak says this is so that apps can share runtimes. But the whole point of their runtime system is to let apps use different runtimes.

Yeah, Ubuntu also seems to be getting as resource intensive as Windows

I've been saying that Ubuntu is resource hungry for years.

I used to maintain a small patch set of issues that affected me and were fixed on the GNOME bugzilla but ignored by main devs. This is was a motivating factor in my switch to to Unity years ago. Sad to hear this situation hasn't improved.

I don't want to agree with you, but I tried to make a few polishing contributions to GNOME games and they got ignored after the first developer response (they told me what to fix, I fixed it). They've been stagnant for over 3 years now.

Submitting changes and having them accepted by GNOME is an exercise in futility if you aren't a GNOME dev.

Flatpak is built on top of a technology called OSTree, which is influenced by and very similar to the Git version control system. Like Git, OSTree allows versioned data to be tracked and to be distributed between different repositories. However, where Git is designed to track source files, OSTree is designed to track binary files and other large data.

Storing applications in a local OSTree repository has other advantages. For example, it allows files that are stored on disk to be deduplicated, so the same file that belongs to multiple applications (or runtimes) is only stored once.

Internally, Flatpak therefore works in a similar way to Git, and many Flatpak concepts are analogous to Git concepts. Like Git, Flatpak uses repositories to store data, and it tracks the differences between versions.

The underlying architecture might be summarized as “git for operating system binaries”.

GitLab self-monitoring gives administrators of self-hosted GitLab instances the tools to monitor the health of their instances. This feature is deprecated in GitLab 14.9, and is scheduled for removal in 15.0.

The reason for the new name is that the "dist-upgrade" name was itself extremely confusing for many users: while it was named that because it was something you needed when upgrading between distribution releases, it sounded too much as though it was only for use in that circumstance, whereas in fact it's much more broadly applicable.

his serves as a good example of apt-gets stability. In apt, the name was changed to be more user friendly, while in apt-get the name remains unchanged so as not to break compatibility with old scripts.

Use apt as a first choice, but if you're scripting use apt-get. Apt-get has more stable output (meaning that the output format is left alone as much as possible so as not to break scripts which parse that output automatically). Apt-get also has some low-level commands not available in apt.

Yes they are the same command. This part of apt's cmdline/apt.cc source file proves it:

Note: triggering events by JS will never make CSS :hover work

Just let it expand inside an array declaration's right side: list=(../smth*/) # grab the list echo "${#list[@]}" # print array length echo "${list[@]}" # print array elements for file in "${list[@]}"; do echo "$file"; done # loop over the array

The short answer is that you want an array: dirs=(/content/{dev01,dev01})

Capybara can get us part of the way there. It allows us to work with an API rather than manipulating the HTML directly, but what it provides isn't an application specific API. It gives us low-level API methods like find, fill_in, and click_button, but it doesn't provide us with high-level methods to do things like "sign in to the app" or "click the Dashboard item in the navigation bar".

A page object is a data structure that provides an interface to your web application for the purposes of test automation. For example, it could represent a single HTML page, or perhaps even a fragment of HTML on a page.

A page object wraps an HTML page, or fragment, with an application-specific API, allowing you to manipulate page elements without digging around in the HTML.

Data integrity is a good thing. Constraining the values allowed by your application at the database-level, rather than at the application-level, is a more robust way of ensuring your data stays sane.

t.datetime :seen_at, default: { expr: 'NOW()' }

Define table structure (columns and indexes) inside your ActiveRecord models like you can do in migrations. Also similar to DataMapper inline schema syntax.

This is particularly useful in cases where you want to separate your data migrations from your schema migrations or where you have multiple steps in your migration process that must have other steps invoked throughout.

support for ActiveRecord migrations in non-Rails applications.

It's more opinionated than active_record_migrations and standalone-migrations, and therefore simpler to configure.

In 1994, The Unix-Haters Handbook was published containing a long list of missives about the software—everything from overly-cryptic command names that were optimized for Teletype machines, to irreversible file deletion, to unintuitive programs with far too many options. Over twenty years later, an overwhelming majority of these complaints are still valid even across the dozens of modern derivatives. Unix had become so widely used that changing its behavior would have challenging implications. For better

Pragma::Migration is an experiment at implementing Stripe-style API versioning.

# Optionally, you can write a description for the migration, which you can use for # documentation and changelogs. describe 'The _id suffix has been removed from the author property in the Articles API.'

apply_to '/api/v1/articles/:id'

When we insert data into the comments table, we need it to route to be inserted into a partition instead of the actual table. For that, we can create a trigger: add_partition_trigger :comments, :comments_by_year, [ { if: 'NEW.year = 2016', insert: :comments_2016 }, { elsif: 'NEW.year = 2017', insert: :comments_2017 }, { else: "RAISE EXECEPTION 'comments_by_year recieived an unexpected value: %', NEW.year;" } ]

There are a couple of reasons why you may want to do this.

systematize

If you want to organize said migrations in their purpose you'll probably have a folder for the struture ones and another for the data ones.

Why does this even exist ? So you can seperate the data and structure migrations in different folders

db/migrate/core/user/

We are looking for sustainable sponsorship. If your company is relying on rom-rb or simply want to see rom-rb evolve faster to meet your requirements, please consider backing the project

The problems with ORMs are numerous, and the above issues only begin to scratch the surface

Object hierarchies are very different from relational hierarchies. Relational hierarchies focus on data and its relationships, whereas objects manage not only data, but also their identity and the behavior centered around that data.

Ruby Object Mapper (rom-rb) is a fast ruby persistence library with the goal of providing powerful object mapping capabilities without limiting the full power of the underlying datastore.

The call signature for setting up enums in migrations has changed.

Lately I've been much happier working with ROM, so it's just as well that Rails is obsoleting this gem.

Rails 7 supports Postgres enums natively (more info)

If you need to ensure migrations run in a certain order with regular db:migrate, set up Outrigger.ordered. It can be a hash or a proc that takes a tag; either way it needs to return a sortable value: Outrigger.ordered = { predeploy: -1, postdeploy: 1 } This will run predeploys, untagged migrations (implicitly 0), and then postdeploy migrations.

class PreDeployMigration < ActiveRecord::Migration tag :predeploy end

This is especially useful for zero downtime deploys to Production environments.

The code will work without exception but it doesn’t set correct association, because the defined classes are under namespace AddStatusToUser. This is what happens in reality: role = AddStatusToUser::Role.create!(name: 'admin') AddStatusToUser::User.create!(nick: '@ka8725', role: role)

If the gem purpose is still not clear please check out this blog post.

this gem promotes writing tests for data migrations providing a way allows to write code that migrates data in separate methods.

having the code migrates data separately covered by proper tests eliminates those pesky situations with outdated migrations or corrupted data.

If the users table is large, running this migration on a live Postgres 9 database will likely cause downtime. Safe PG Migrations hooks into Active Record so that the following gets executed instead: class AddAdminToUsers < ActiveRecord::Migration[5.2] # Do not wrap the migration in a transaction so that locks are held for a shorter time. disable_ddl_transaction! def change # Lower Postgres' lock timeout to avoid statement queueing. Acts like a seatbelt. execute "SET lock_timeout TO '5s'" # The lock_timeout duration is customizable. # Add the column without the default value and the not-null constraint. add_column :users, :admin, :boolean # Set the column's default value. change_column_default :users, :admin, false # Backfill the column in batches. User.in_batches.update_all(admin: false) # Add the not-null constraint. Beforehand, set a short statement timeout so that # Postgres does not spend too much time performing the full table scan to verify # the column contains no nulls. execute "SET statement_timeout TO '5s'" change_column_null :users, :admin, false end end

There are three keys to backfilling safely: batching, throttling, and running it outside a transaction. Use the Rails console or a separate migration with disable_ddl_transaction!.

Active Record creates a transaction around each migration, and backfilling in the same transaction that alters a table keeps the table locked for the duration of the backfill. class AddSomeColumnToUsers < ActiveRecord::Migration[7.0] def change add_column :users, :some_column, :text User.update_all some_column: "default_value" end end

Can you check out whether the polkit permission is even queried by adding a rule /etc/polkit-1/rules.d/10-udisks.rules. polkit.addRule(function(action, subject) { var prefix = "org.freedesktop.udisks"; if (action.id.slice(0, prefix.length) == prefix) polkit.log(action.id); });

echo "TEMP /dev/sdb2 /home/key" >> /etc/crypttab

One of the DEBUG lines near the end of the udiskie output should contain a hint as to why the device was rejected by udiskie.

Let's investigate:

udiskie-mount -v /dev/sdb2 gdbus call --system --dest org.freedesktop.UDisks2 --object-path /org/freedesktop/UDisks2/block_devices/sdb2 --method org.freedesktop.DBus.Properties.GetAll org.freedesktop.UDisks2.Block

No need to construct strings that then need to be deconstructed later.

And events are just data so can process, enrich, filter, aggregate, visualise the data with your own tools.

Because it is cheap to log events, you can freely log plenty.

Event logs are useful, but not as important as process flow (therefore preferable to drop events rather than crashing the process)

I believe we need the break free of these anachronistic designs and use event loggers, not message loggers

In any significant project I worked in the last 15 years, logging text messages resulted in a large amount of strings which was hard to make sense of, thus mostly ignored.

µ/log's idea is to replace the "3 Pillars of Observability" with a more fundamental concept: "the event"

Event-based data is easy to index, search, augment, aggregate and visualise therefore can easily replace traditional logs, metrics and traces.

// Native const datePattern = /^(\d{2})-(\d{2})-(\d{4})$/; const [, month, day, year] = datePattern.exec('12-25-1995'); new Date(`${month}, ${day} ${year}`);

Modern JavaScript environments will also implement the by ECMA-402 specification, which provides the Intl object

Using Date.parse, or new Date(<string>) has been problematic and implemented inconsistently in the past. The current specification defines parsing a variation of ISO 8601 strings, where date-only forms (like "2020-09-14") are parsed as UTC, instead of local time as they would be by ISO 8601.

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

You Probably Don't Need Moment.js Anymore You don't (may not) need Moment.js

The Moment team has discussed these issues at length. We recognize that many existing projects may continue to use Moment, but we would like to discourage Moment from being used in new projects going forward. Instead, we would like to recommend alternatives that are excellent choices for use in modern applications today.

The chip was developed as a result of the 1983 video game crash in North America, partially caused by an oversaturated market of console games due to lack of publishing control. Nintendo president Hiroshi Yamauchi said in 1986, "Atari collapsed because they gave too much freedom to third-party developers and the market was swamped with rubbish games."[6] By requiring the presence of the 10NES in a game cartridge, Nintendo prevented third-party developers from producing games without Nintendo's approval, and provided the company with licensing fees

There's an open suggestion at microsoft/TypeScript#13347 to introduce a compiler flag or some other mechanism to more strictly enforce readonly, but it's been around for a long time and it's not clear whether or not this will ever happen.

The cleanest is to give up on readonly properties and instead use some kind of mapping that turns an object into something you really can only read from, via something like getter functions.