everything is part of a lar system right now that begins to open up into the realm of soul and what do we mean by Soul

But you're able to remove (usually inherited) fields by: class ChildForm < ParentForm remove_field :field_from_parent end

Lightweight file watcher weighing about 300 LOC. No runtime dependencies and no platform specific code. Works everywhere.

Features

slab, slab->objects, slab->inuse, slab->freelist, folio_flags(folio, 0)

ALLOC_FASTPATH, /* Allocation from cpu slab */ 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 ALLOC_SLOWPATH, /* Allocation by getting a new cpu slab */ FREE_FASTPATH, /* Free to cpu slab */ FREE_SLOWPATH, /* Freeing not to cpu slab */ FREE_FROZEN, /* Freeing to frozen slab */ FREE_ADD_PARTIAL, /* Freeing moves slab to partial list */ FREE_REMOVE_PARTIAL, /* Freeing removes last object */ ALLOC_FROM_PARTIAL, /* Cpu slab acquired from node partial list */ ALLOC_SLAB, /* Cpu slab acquired from page allocator */ ALLOC_REFILL, /* Refill cpu slab from slab freelist */ ALLOC_NODE_MISMATCH, /* Switching cpu slab */ FREE_SLAB, /* Slab freed to the page allocator */ CPUSLAB_FLUSH, /* Abandoning of the cpu slab */ DEACTIVATE_FULL, /* Cpu slab was full when deactivated */ DEACTIVATE_EMPTY, /* Cpu slab was empty when deactivated */ DEACTIVATE_TO_HEAD, /* Cpu slab was moved to the head of partials */ DEACTIVATE_TO_TAIL, /* Cpu slab was moved to the tail of partials */ DEACTIVATE_REMOTE_FREES,/* Slab contained remotely freed objects */ DEACTIVATE_BYPASS, /* Implicit deactivation */ ORDER_FALLBACK, /* Number of times fallback was necessary */ CMPXCHG_DOUBLE_CPU_FAIL,/* Failures of this_cpu_cmpxchg_double */ CMPXCHG_DOUBLE_FAIL, /* Failures of slab freelist update */ CPU_PARTIAL_ALLOC, /* Used cpu partial on alloc */ CPU_PARTIAL_FREE, /* Refill cpu partial on free */ CPU_PARTIAL_NODE, /* Refill cpu partial from node partial */ CPU_PARTIAL_DRAIN, /* Drain cpu partial to node partial */ NR_SLUB_STAT_ITEMS

You can also see underlying transactions for each income and spending area. 

You can split transactions among multiple tags or categories and exclude them from reports and the Spending Plan.

Nested categories. If I click into a spending group on Simplifi, I can see the breakdown of all categories within that group. Somehow I cannot do this on Monarch. I can only view by group or category as a whole. There's no nesting.

Monarch uses AI to clean your transactions, and gets smarter over time. If you want more control, you can use transaction rules to predictably update merchant names, categories, tags, notes, and more to keep everything organized.

ask about that transaction.

t is the cause, it is the cause, my soul.Let me not name it to you, you chaste stars,It is the cause.

thy rose

This sorrow’s heavenly,

By abstracting code away from "Files" and "Lines" we can offer more nuanced views like "Repeated Code Blocks" that could be refactored.

Figshare supports version control of all publicly available data. Any privately stored data can also be altered or deleted as you wish.

The act of minting an LSID indicates that you intend to try to make it permanent or at least never re-use it for another resource.

Governance

Persistence

Trust

Available Handle-based PID schemes

Scalability

Collectively the IDF and its RA members assume the long-term responsibility to maintain and sustain the DOI PID scheme for everyone.

Which identifiers are FAIR enough?

Compact identifiers are a longstanding informal convention in bioinformatics. To be used as globally unique, persistent, web-resolvable identifiers, they require a commonly agreed namespace registry with maintenance rules and clear governance; a set of redirection rules for converting namespace prefixes, provider codes and local identifiers to resolution URLs; and deployed production-quality resolvers with long-term sustainability.

Wittenburg, P., Hellström, M., Zwölf, C.-M., Abroshan, H., Asmi, A., Di Bernardo, G., Couvreur, D., Gaizer, T., Holub, P., Hooft, R., Häggström, I., Kohler, M., Koureas, D., Kuchinke, W., Milanesi, L., Padfield, J., Rosato, A., Staiger, C., van Uytvanck, D., & Weigel, T. (2017). Persistent identifiers: Consolidated assertions. Status of November, 2017. Zenodo. https://doi.org/10.5281/zenodo.1116189

Archives. The Member shall use best efforts to contract with a third-party archive or other content host (an "Archive") (a list of which can be found here) for such Archive to preserve the Member's Content and, in the event that the Member ceases to host the Member's Content, to make such Content available for persistent linking.

Maintaining and Updating Metadata.

Commitment to data persistence

Maintaining and Updating Metadata.

ePIC PID service, and an organisation, that provides a PID service and is not an ePIC member, can ask for a certification, that it provides its PID service along the lines of the ePIC rules and policies.

ePIC has rules and policies, how to provide PID services and how to ensure the reliability, that is necessary for the persistency of access to digital objects via ePIC PIDs.

Registered production PIDs will not be deleted. They are used as a kind of tombstone even if the underlying data is not available anymore.

Scalability – in the data/metadata stored;

To resolve a Compact ARK (ie, an ARK beginning "ark:") it must initially be promoted to a Mapping ARK so that it becomes actionable. On the web, this means finding a suitable web Resolver Service to prepend to the compact form of the identifier in order to convert it to a URL (cf [CURIE]). (This is more or less true for any type of identifier not already in URL form.)

When content underlying a DOI is updated, we recommend updating the DOI metadata and, for major changes, assigning a new DOI. For minor content changes, the same DOI may be used with updated metadata. A new DOI is not required. For major content changes, we recommend assigning a new DOI and linking the new DOI to the previous DOI with related identifiers.

To enable easy usability for both humans and machines, a DOI should resolve to a landing page that contains information about the DOI being resolved. It is the responsibility of the entity creating the DOI to provide such a landing page. The following are best practices for creating well-formed DOI landing pages.

there may be infrequent cases where it is not desirable for the item described by a DOI to be available publicly, such as in the case of research retraction. In these cases, it is best practice to still provide a "tombstone page", which is a special type of landing page describing the item that has been removed.

certification: If certified, acronym for certification organization or standard (e.g., TRAC, TDR, DSA) and year of certification.

succession: The plan for dealing with sudden loss of provider viability, including set-aside funding and length of time that operations would be able to support continued operation while a successor provider is found to keep references intact.

mission: One sentence mission statement of the organization.

business model: For profit (FP) or not for profit (NP).

name: Full name of the provider organization. identifier: Unique identifier for the organization.

inflection: a change to the ending of an object’s id string in order to obtain a reference to content related to the originally referenced content.

landing: content intended mostly for human consumption, such as an object description and links to primary information (e.g., an image file or a spreadsheet), to alternate versions and formats, and to related information; from “landing page”, this is intended to support a browsing experience of an abstract overall view of the object.

plunging: content intended as primary object information, often required or directly usable by software; from “below the landing page”, this is intended to support an immersive object experience that bypasses any browsing step.

introversioned: a kind of intraversioned content for which the version identifier (within the object identifier) is opaque, e.g., “http://doi.org/10.2345/678”, which happens to be version 4.

intraversioned: a version identifier is part of the id string, e.g., “http://doi.org/10.2345/67.V4”.

extraversioned: a version identifier is separate from the id string, so that the actionable id does not lead to specific version without human intervention, e.g., “http://doi.org/10.2345/67”, Version 4.

Precisely when such assignment will be triggered depends on policy that will differ across objects, collections, and providers.

waxing: change that is limited to appending content in a way that does not in itself disrupt or displace previously recorded content. Examples of waxing objects include live sensor-based data feeds, citation databases, and serial publications.

subinfinite: due to succession arrangements, the object is expected to be available beyond the provider organization’s lifetime.

lifetime: the object is expected to be available as long as the provider exists.

indefinite: the provider has no particular commitment to the object.

finite: availability is expected to end on or around a given date (e.g., limited support for software versions not marked “long term stable”) or trigger event (e.g., single-use link).

finite: availability is expected to end on or around a given date (e.g., limited support for software versions not marked “long term stable”) or trigger event (e.g., single-use link). indefinite: the provider has no particular commitment to the object. lifetime: the object is expected to be available as long as the provider exists. subinfinite: due to succession arrangements, the object is expected to be available beyond the provider organization’s lifetime.

We define content variance to be a description of the ways in which provider policy or practice anticipates how an object’s content will change over time. Approaches to content variance differ depending on the object, version, service, and provider.

molting: Previously recorded content may be entirely overwritten at any time with content that preserves thematic continuity. For example, an organization’s homepage may be completely reworked while continuing to be its homepage, and a weather or financial service page may reflect dramatic changes in conditions several times a day.

rising: Previously recorded content may be improved at any time, for example, with better metadata (datasets), new features (software), or new insights (pre- and post-prints). This encompasses any change under “fixing”

fixing: Previously recorded content may be corrected at any time, in addition to any change under “keeping”

keeping: Previously recorded content will not change, but character, compression, and markup encodings may change during a format migration, and high-priority security concerns will be acted upon (e.g., software virus decontamination, security patching).

frozen: The bit stream representing previously recorded content will not change

id string: the sequence of characters that is the identifier string itself, possibly modified by adding a well-known prefix (often starting with http://) in order to turn it into a URL. identifier: an association between an id string and a thing; e.g., an identifier “breaks” when the association breaks, but to act on an identifier requires its id string. actionable identifier: an identifier whose id string may be acted upon by widely available software systems such as web browsers; e.g., URLs are actionable identifiers.

At a minimum it implies a prediction about an archive’s commitment and capacity to provide some specific kind of long-term functionality

persistence is purely a matter of service

We propose a novel approach relying on persistent, timestamped, adapted queries to versioned and timestamped data sources

If a published dataset is improved by amendments to thedata files of the dataset, a major version increment iscreated with a record of changes. In cases where it isnecessary to disable access to earlier versions, these can bedeaccessioned

Once a DOI is registered in the DOI System server, or repository, it will be stored there virtually forever.

These findings provide strong indicators that scholarly contentproviders reply to DOI requests differently, depending on the request method,the originating network environment, and institutional subscription levels

DOIs are a great solution for the problem of URIs that change over time, but this approach does depend on journal publishers, repositories, libraries, and other major hosting organization to be responsible for maintaining current link information within the DOI records that they have created

identifiers will continue to resolve indefinitely.

All PID Registration Agencies must have highly redundant storage and hosting infrastructure in order to ensure that services are globally available 24-7

Persistent

Machine-Readable

Globally Unique Names

In terms of evolution, animals adapt to their ecological conditions, but as humans, we have been able to control our ecological conditions.

Systems such as DOI can thus support resolution mechanisms that are likely to be able to maintain the resolution of identifiers regardless of changes in technology or to one particular system.

Supported Schemes

Stephen Davies, Javier Velez-Morales, & Roger King (2005), "Building the memex sixty years later: trends and directions in personal knowledge bases", Department of Computer Science, University of Colorado at Boulder. The Wikipedia article on personal knowledge bases (PKBs) is basically a summary of the technical report. The report defined personal knowledge base systems, described their benefits, reviewed relevant fields of research, and compared systems in terms of several aspects of their data models: structural framework, knowledge elements, schema, and the role of transclusion. This report is the most comprehensive publication I've read that compares PKB systems according to their key features.

Fashion is a non-verbal communication that can represent one’s political and religious beliefs, gender identity, occupation, and essence. Whether intentional or not, the way that you dress can send a message to others about how you view yourself and how you want to be seen.

Diet YAML is a light weight version of YAML that removes much of the complex aspects of the mainline YAML specification.

paranoia has some surprising behaviour (like overriding ActiveRecord's delete and destroy) and is not recommended for new projects. See discard's README for more details. Paranoia will continue to accept bug fixes and support new versions of Rails but isn't accepting new features.

yield is a bit of laguage level magic that only works in the context of a method.

Automated personalization, localization, recommendation, f iltering, classif ication, evaluation, aggregation, synthetization, or ad hoc generation of information are similarly pervasive practices that do not require explicit user input to select, sequence, arrange, or modulate some set of digital items

Search has become a dominant means to access and order the masses of digital and dataf ied bits and pieces that clutter the environments we inhabit.

Current ruby releases generate *.tar.gz, *.tar.bz2, *.tar.xz, and *.zip. But I think we can stop generating *.tar.bz2. I think *.tar.bz2 are less merit. For better size, *.tar.xz exist. For better compatibility, *.tar.gz and *.zip exist.

In other words, i18n allows applications to support and satisfy the needs of multiple locales, thus “enabling” l10n.

The person was transported to Doctor's West in critical condition.

HBCC is the most common form of nonparental child care for infants and toddlers

Moving forward I'd rather see {#await} being removed than adding more {#await}. But that's just from my experience and I'm sure there are use-cases for it.

Persisting across apps Your notifications can persist across multiple apps / page reloads, as long as they use this library. This is useful for a scenario where you show a notification and then redirect the browser to a different application, or trigger a full reload of the page. This is completely automatic and uses session storage.

With firefox 88 it won't work anymore, now navigator.webdriver is always true when maionette is enabled.

The release of Capybara 2.0.0 removed the wait_until method from the API. This seems to have frustrated a few people,

Update API usage of the view helpers by changing javascript_packs_with_chunks_tag and stylesheet_packs_with_chunks_tag to javascript_pack_tag and stylesheet_pack_tag. Ensure that your layouts and views will only have at most one call to javascript_pack_tag or stylesheet_pack_tag. You can now pass multiple bundles to these view helper methods.

The WebSocket Protocol is designed on the principle that there should be minimal framing (the only framing that exists is to make the protocol frame-based instead of stream-based and to support a distinction between Unicode text and binary frames). It is expected that metadata would be layered on top of WebSocket by the application Fette & Melnikov Standards Track [Page 9] RFC 6455 The WebSocket Protocol December 2011 layer, in the same way that metadata is layered on top of TCP by the application layer (e.g., HTTP). Conceptually, WebSocket is really just a layer on top of TCP that does the following: o adds a web origin-based security model for browsers o adds an addressing and protocol naming mechanism to support multiple services on one port and multiple host names on one IP address o layers a framing mechanism on top of TCP to get back to the IP packet mechanism that TCP is built on, but without length limits o includes an additional closing handshake in-band that is designed to work in the presence of proxies and other intermediaries Other than that, WebSocket adds nothing. Basically it is intended to be as close to just exposing raw TCP to script as possible given the constraints of the Web. It's also designed in such a way that its servers can share a port with HTTP servers, by having its handshake be a valid HTTP Upgrade request. One could conceptually use other protocols to establish client-server messaging, but the intent of WebSockets is to provide a relatively simple protocol that can coexist with HTTP and deployed HTTP infrastructure (such as proxies) and that is as close to TCP as is safe for use with such infrastructure given security considerations, with targeted additions to simplify usage and keep simple things simple (such as the addition of message semantics).

The emphasis was made on a raw CDP protocol because Chrome allows you to do so many things that are barely supported by WebDriver because it should have consistent design with other browsers.

The main (IMO) feature of MQTT – quality of service – doesn't make sense in our case: if a WebSocket server is down and doesn't receive broadcast messages (through HTTP/Redis/queue), it's likely not to handle client connections too.

While rails does have nice CSRF protection, in my instance it limited me.

if you just need a screenshot of a webpage, that’s built in:

When fetch runs on the server, the resulting response will be serialized and inlined into the rendered HTML. This allows the subsequent client-side load to access identical data immediately without an additional network request.

o help us meet this vision, the frontend should use GraphQL in preference to the REST API for new features.

Local development and testing has huge advantages, but sometimes one needs to test web applications against their real-world domain name. Editing /etc/hosts is a pain however, and error prone. Node Foreman can start up an HTTP forward proxy which your browser can route requests through. The forward proxy will intercept requests based on domain name, and route them to the local application.

Screen and Tmux are used to add a session context to a pseudoterminal, making for a much more robust and versatile solution. For example, each provides terminal persistence, allowing a user to disconnect from one computer and then connect later from another computer.

Apparently when you create a subclass, that subclass's singleton class has # its superclass's singleton class as an ancestor.

Now VS Code's generic debugger UI supports all data breakpoint access types defined in the Debug Adapter Protocol as context menu actions in the VARIABLES view: Break on Value Read: breakpoint will be hit every time a variable gets read. Break on Value Change: breakpoint will be hit every time a variable gets changed (this action was previously available). Break on Value Access: breakpoint will be hit every time a variable is read or changed.

_Underline_

Title: "goal the use case is trying to satisfy"[23]:101 Main Success Scenario: numbered list of steps[23]:101 Step: "a simple statement of the interaction between the actor and a system"[23]:101 Extensions: separately numbered lists, one per Extension[23]:101 Extension: "a condition that results in different interactions from .. the main success scenario". An extension from main step 3 is numbered 3a, etc.

Use the button to get a sharable link to the page with annotations.

and the --enable-gui=<gui> e.g. (--enable-gui=gnome for the Gnome Gui).

How to install VIM with all options/features? - VIM

If you want to compile youself you can pass the --with-features=huge to the configure script. Note, however, this does not enable the different language bindings because those are mostly optional and also the various GUIs need to enabled specifically, because you can have only one gui.

If you call ./configure --enable-gui=auto, the build process will automatically build against whichever GUI libraries are available. A cursory glance suggests that gtk2 will be prioritised over gnome2.

Software that is not currently being used gradually becomes unusable as the remainder of the application changes.

Infrequently used portions of code, such as document filters or interfaces designed to be used by other programs, may contain bugs that go unnoticed. With changes in user requirements and other external factors, this code may be executed later, thereby exposing the bugs and making the software appear less functional.

now that I realize how easy it is to just manually include this in my app: <%= javascript_include_tag 'xray', nonce: true if Rails.env.development? %> I regret even wasting my time getting it to automatically look for and add a nonce to the auto-injected xray.js script

Another solution is using the Safe Navigation Operator &. introduced in Ruby 2.3 which is a bit better because this is a language feature rather than an opinionated runtime environment pollution

ActiveInteraction provides detailed errors for easier introspection and testing of errors. Detailed errors improve on regular errors by adding a symbol that represents the type of error that has occurred.

support round-tripping (assigning the submitted params again)

Folding This is the one function whose name is confusing because many products use the term for what we called “collapsing” above. For this article, collapsing is the process of making whole headers and paragraphs invisible, tucking them up under a “parent.” Folding is a different kind of tucking under; it works on paragraphs and blocks to reduce them to a single line, hiding the rest. A simple case of folding might involve a long paragraph that is reduced to just the first line—plus some indication that it is folded; this shows that a paragraph is there and something about its content without showing the whole thing. Folding is most common in single-pane outline displays, and a common use is to fold everything so that every header and paragraph is reduced to a single line. This can show the overall structure of a huge document, including paragraph leaves in a single view. You can use folding and collapsing independently. At one time, folding was one of the basics of text editors, but it has faded somewhat. Now only about half of the full-featured editors employ folding. One of the most interesting of these is jEdit. It has a very strong implementation of folding, so strong in fact it subsumes outlining. Though intended as a full editor, it can easily be used as an outliner front end to TeX-based systems. jEdit is shown in the example screenshot in both modes. The view on the right shows an outline folded like MORE and NoteBook do it, where the folds correspond to the outline structure. But see on the left we have shifted to “explicit folding” mode where blocks are marked with triple brackets. Then these entire blocks can be folded independent of the outline. Alas, folding is one area where the Mac is weak, but NoteBook has an implementation that is handy. It is like MORE’s was, and is bound to the outline structure, meaning you can only fold headers, not arbitrary blocks. But it has a nice touch: just entering a folded header temporarily expands it.

If a reviver is specified, the value computed by parsing is transformed before being returned.

This decorators proposal deliberately omits these features, in order to keep the meaning of decorators "well-scoped" and intuitive, and to simplify implementations, both in transpilers and native engines.

However, this coalescing was very complicated, both in the specification and implementations, due to the dynamism of computed property names for accessors. Coalescing was a big source of overhead (e.g., in terms of code size) in polyfill implementations of "Stage 2" decorators.

Long ago, the standards deities gifted us <style scoped>, before removing it in favour of the arguably less-useful shadow DOM encapsulation mechanism.

👍 Can it notify user while field is being validated? 👍 Can it stop performing remaining validators if there is a validator that the field does not pass? 👍 Can it perform the validation only when the field value exceed a given number of characters? 👍 Can it postpone the validation for a given number of seconds from the moment user stops fill in the field?

The goal is to bring element creation down to this logic:

There is a killer feature of vDOM that Svelte has nothing to replace with. It is the ability to treat component hierarchy as an object.

It provides several capabilities that are difficult to achieve with React alone, while being compatible with the newest features of React.

A new option --proximate=N groups together lines of output that are within N lines of each other in the file. This is useful when looking for matches that are related to each other.

Also Svelte is so great because developer do not need to worry about class names conflict, except of passing (global) classes to component (sic!).

TBH It is a bit disheartening to see this issue closed when all proposed solutions do not sufficiently solve the issue at hand, I really like svelte but if this is how feature requests are handled I am probably not going to use it in the future.

Update: As best I can tell, <style scoped> has been removed from the specs and even browsers that were supporting it have pulled it. Even as I write this update (August 2017) scoped styles are arguably more popular and desirable than ever before.