Over time, the risk grows that the document is no longer accessible at the loca-tion given as reference. Web servers that follow the HTTP protocol then give the notorious reply: ‘404 not found’. This resembles the situation of a book in a – very large – li

Over time the risk grows that the document is no longer accessible at the loca- tion given as reference. Web servers that follow the HTTP protocol then give the notorious reply: ‘404 not found’. This resembles the situation of a book in a – very large – li

Over time, the risk grows that the document is no longer accessible at the loca- tion given as reference. Web servers that follow the HTTP protocol then give the notorious reply: ‘404 not found’. This resembles the situation of a book in a – very large – l

Some privacy related extensions may cause issues on x.com.

I agree with your request, but your ticket's title describes the solution you envisioned rather than the issue. I suggest the following title to represent the actual issue:

Closing as won't fix since there is not a strong enough use case to add support for this behavior since we have not seen any recent requests for this behavior.

Authors contact

Supporting Files

Supporting Files

Figure 3

The authors declare no conflicts of interest.

R packages

emporary beans were labor inensive. Their pods matured at different times and had to be picked by hand. If you waited too long, the pods would shatter, spilling the beans onto the ground.

Reinforced planetary care: localism on its own cannot resist globalized pressure, nor solve planetary and global thermo-dynamic issues.

Most people in America today (85–90%) agree on most issues and topics (85–90%). The so-called polarization is the result of a media landscape that amplifies the voices of the 10–15% that keep constantly talking about the 10–15% of topics on which people are not on the same page.

let's go and and create all this great software to deploy it and kind of equalize the the the disparity of wealth across the world and ends up being locked out for by stupid issues like latency and bandwidth

the music became a voice for the poor and dispossessed

If you have questions, problems or suggestions about plugins system — please, don't hesitate to create a new issue.

The complication comes from the fact that the execution model does not have any means for the execution of "give up ownership of the lock" to have any influence over which execution of "gain ownership of the lock" in some other timeline (thread) follows. Very often, only certain handoffs give valid results. Thus, the programmer must think of all possible combinations of one thread giving up a lock and another thread getting it next, and make sure their code only allows valid combinations.

This basic mismatch between the scale of the problem and the scale of possible solutions is a source of many of today’s failures of global governance. Nation-states and the global governance institutions they have formed simply aren’t fit for the task of managing things such as viruses, greenhouse gases and biodiversity, which aren’t bound by political borders, but only by the Earth system.

what if a band decides to take one of the udio generated songs and re-record it entirely will they own the full copy rate to that very new recording now if I 00:21:03 was udio the answer probably be like no you made that thing using our platform

Regression in 3.13: custom matcher hash argument improperly converted to keyword args, results in ArgumentError

ZenHub’s Issue dependencies not only help teams visualize relationships between pieces of work, but they save team members a lot of time that would otherwise be lost just hunting down information.

When relying on just a list of GitHub issues and comment references to other Issues, there’s a strong possibility that visibility into how these changes impact other tasks get lost or forgotten.

Tracking dependent relationships between Issues and whether something is blocking another piece of work is important with any project process because it creates a central hub where everyone can communicate what’s needed without relying solely on meetings or comments to uncover important connections.

Sub tasks are just issues with a parent issue. When displaying them, always display the ancestor crumb trail.

It's also common to want to compute the transitive closure of these relations, for instance, in listing all the issues that are, transitively, duped to the current one to hunt for information about how to reproduce them.

Marking an issue as as a subtask of another. Having task lists in a description is a great start, but it doesn't help (AFAIK) navigating from child back up the chain to parent. Creating umbrella issues is a very common way to track the top-level focus areas for a release.

The "meaning" will tell Gitlab how to interpret the relation. For example, a "parent/child" relation will have the meaning set to "one is a part of another", and then user may define a "subtask" and "subcomponent" relations to distinguish two situations, but Gitlab will understand because all three will have the same meaning and it can render a tree with three different kinds of edges.

Another example are issue boards. They represent elegant use of a good infrastructure ­— it is all just a smart use of labels. It would be very complex feature without the use of labels.

Issue relations are meant to be the basic infrastructure to build on (at least that is how I meant it when I posted the original feature request). Just like the labels are just a binary relation between a issue and a "label", the relations should be just a ternary relation between two issues and a "label". Then you can build issue task lists on top of the relations like you've built issue boards on top of the labels.

This would be transformational in the scope of what issues can be effectively used for!

subtasks would give insight into how long it will take!

Blockers would give better insight into when an issue can be started,

Our flow is: The reporter reports an issue, and we developers create sub tasks upon that issue... in Redmine, we also had a percentage graph that would reach 100% when all sub-tasks were completed, was a great way about checking 1 item without the need to drill down all subtasks.

We use GitLab to manage software on interconnected embedded systems. What often comes up is this: New functionality on one system changes the protocol in a slightly incompatible way. Software on other systems have to be updated to understand the new protocol, take advantage of the new functionality, and stop complaining about the unexpected data. For this I would create multiple issues: Issues for the new functionality that we need. (Project A) Issue for defining the protocol changes. (Project A) Issue for implementing the protocol changes on the module. (Project A) Issues in related software projects for implementing the changes required to understand the new protocol. (Project B, C, D...)

bugzilla has had the concept of one or more ticket(s) blocking another for quite some time. We used that for over ten years before switching to GitLab and it is a feature I miss. A dependency tree between issues enables planning and workflow. This is can be seen as related to issues boards in that blocked issues should not be able to move ahead until the blockers are at least implemented perhaps reviewed.

It would be useful filter to have, also it would be useful to sort issues using topological order on Board and other issue listings, so the unblocked issues would be first.

Simple relations: [Issue A]---(relation R)--->[Issue B], which is a ternary (A, B, R) relation in a database.

I see specific relations in a similar way as labels. If a "label" is a binary relation between a label and an issue, "relation" between issues would be ternary relation between two issues and a label (from different set than ordinary labels).

One of the reasons that some projects don't use Gitlab's issues and use an external tracking platform is the lack of issues relations. Without relations issues are just flat, no way to actually track progress of big features. No way to create a "meta" issue that depends on 4 other or create subtasks and so on. The same problem exists on Github too. It would surely make a difference if Gitlab offers a full features tracking issue, instead of just flat issues. Relations is a major first step towards that.

but from previous experiences like this, the feature set has to be robust at the start or I think adoption will suffer.

I disagree. What is expressed is an attempt to solve X by making something that should maybe be agnostic of time asynchronous. The problem is related to design: time taints code. You have a choice: either you make the surface area of async code grow and grow or you treat it as impure code and you lift pure synchronous logic in an async context. Without more information on the surrounding algorithm, we don't know if the design decision to make SymbolTable async was the best decision and we can't propose an alternative. This question was handled superficially and carelessly by the community.

Otherwise, M does not respond to works? (NoMethodError) because there was a context switch before the require triggered by autoload returned.

If it passed before I would think it was just lucky timings.

BTW to improve the reliability of that test I believe you would need a sleep (smaller, e.g. of 0.1) between the Thread.new and assert M.works?, otherwise it's likely the M.works? runs first and then the other thread will see the constant is autoloading and wait, and anyway that thread does not check what is defined on M. For the test to fail it needs to be the Thread.new running first and defining the constant but not yet the method, before the main thread keeps running and call the method.

Eager-merging since this is a bug on prod. Happy to rework this solution as needed if another approach is preferable.

health impacts of violent conflict, bioterrorism, pandemics, and endemic diseases disproportionately affecting certain regions are all linked to health and security

World Health Organization (WHO) and policymakers recognize the importance of health for international peace, stability, and human security.

"responsibility to protect" (R2P).R2P suggests that states have a responsibility to intervene and protect civilians in other states if they are unable or unwilling to do so themselves.Some feminist scholars argue that the language of protection can reinforce gendered and racialized narratives.

International Criminal Court

providers of human security, and that NGOs and international organizations

he United Nations Development Programme and the Commission on Human Security have played important roles in promoting and defining the concept of human security.

DOIs have a business model. LSIDs currently do not. Without a business model (read funding) we should stick to something that doesn’t have the implementation/adoption impediment of LSIDs and make the best of it (i.e. just have a usage policy for HTTP URIs).

Without some kind of persistence mechanism the only advantage of LSIDs is that they look like they are supposed to be persistent. Unfortunately, because many people are using UUIDs as their object identifiers LSIDs actually look like something you wouldn’t want to look at let alone expose to a user! CoL actually hide them because they look like this: urn:lsid:catalogueoflife.org:taxon:d755ba3e-29c1-102b-9a4a-00304854f820:ac2009

Breaking of links is mostly due to administrative changes at the referencedInternet node

Over time the risk grows that the document is no longer accessible at the loca-tion given as reference. Web servers that follow the HTTP protocol then givethe notorious reply: ‘404 not found’. This resembles the situation of a book in a– very large – library that is not on the shelf at the position indicated in the cata-logue. How is it to be found?

check character (CC): A check character is incorporated in the assigned identifier to guard against common transcription errors.

On the other hand, the universal numeric fingerprint (Altman & King 2007) is a PID that supports citation of numeric data in a way that is largely immune to the syntactic formatting and packaging of the data

By contrast, repositories such as figshare (figshare 2016) and Merritt (Abrams et al. 2011) tolerate changes to metadata under the PID assigned originally, but create a new “versioned” PID if the object title or a component file changes, and in the latter case, the original non-versioned PID always references the latest version

The DataONE federated data network (Michener et al. 2011) assigns a PID to immutable data objects and a “series identifier” that resolves to the latest version of an object (DataONE 2015).

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

Data Management: Provenance, Versioning, and ReliableIdentification

median lifespan of these web pages was 9.3 years

Content drift describes the case where the resource identified by its URI changes over time and hence, as time goes by, the request returns content that becomes less and less representative of what was originally referenced.

The Topic Concentration chart above lends the clearest picture into the implied rationale behind the bans. Namely, the bans are not and have not been about the physical removal of a book from a shelf. The bans instead are meant to: Virtue signal by people in positions of institutional power to voting-age parents interested in school choice, parental rights, and wedge social issues to the detriment of non-voting age students Reject and exclude topics that challenge a perceived status quo from the public discourse (e.g. non-heteronormativity, non-cis identity, non-traditional gender roles, and non-Judeo-Christian books are targeted)

I do not disagree, but I would also like to point out that it can confuse newbies, e. g. when they wonder whether they should use class_eval or instance_eval. Some concepts are not trivial to remember offhand.

Another surprise was the amount of notecards that are associated with one another. While some cards contain a short one-line joke, other jokes span several cards. These collections of cards had originally been paper-clipped together, but at some point in the life of the gag file the paper clips were removed. This removal was great in terms of preservation because paper clips tend to rust and cause damage to the surface to which they have been attached. But the removal also made it difficult to decipher which cards were originally associated with one another. I was able to use the bend marks on cards as well as rust marks from where a paper clip used to be to record which joke cards were most likely originally paper-clipped together. This association is important to note because some individual cards only hold a portion of a longer joke and therefore do not make sense independently.

This joke card has a comic clipped from a newspaper glued to it. During the digitization process, the index card was put in a clear Mylar sleeve to prevent the comic, with its brittle glue, from being damaged or separated from the card.

While most of the joke cards are simply index cards with a joke typed on, others are more complicated. Some cards have strips of paper glued to them with longer jokes on those papers. Some cards have entire letter-size sheets of paper containing long jokes stapled to the cards. Some cards have comic strips, cut from the newspaper, glued to the cards. Other cards are not even cards but are just pieces of printer paper with jokes scribbled on them. These irregular cards were not stable enough to be sent through the feed scanner and had to be scanned one-by-one using a flatbed scanner, which slowed my progress.

“scrape” headshots from theonline directories of nine residential houses so students could vote onwhich of two random photos was “hotter.”

Google’s algorithms

Weaponsof Math Destruction, or WMDs

Big Data

That, if nothing else, is a reason to worry.

Faith in Google is thus dangerous as the airplane and the automo-bile have proved dangerous in ways their pioneers did not anticipate inthe 1920s. These technologies of mobility and discovery are dangerousnot just because they physically endanger their users but because weuse them recklessly, use them too much, and design daily life aroundthem.

Big Data.

cornerstone of Lycos's technique was analysis of anchortext, or the descriptions of outbound links on a Web page, to get abetter idea of the meaning of the existing page.

The market was still too imma-ture-robust business models were years from fruition

basic problem of search

n deciding which ads to display, Google’s algorithms fac-tored in how often advertisements were clicked on as well as the amount bid by theadvertiser

chat rooms

Please do not use the issue tracker for personal support requests. Stack Overflow or GitHub Discussions is a better place for that where a wider community can help you!

Refinements themselves present a significant hurdle to adoption by virtue of their limitations and overall introduction of conceptual complexity. So it’s a tough sell to recommend this for anything outside of personal projects or places with incredibly strong esoteric Ruby knowledge (like, say, hidden away within Rails).

Or, did you ever see a dog with a marrowbone in his mouth,—the beast of all other, says Plato, lib. 2, de Republica, the most philosophical? If you have seen him, you might have remarked with what devotion and circumspectness he wards and watcheth it: with what care he keeps it: how fervently he holds it: how prudently he gobbets it: with what affection he breaks it: and with what diligence he sucks it. To what end all this? What moveth him to take all these pains? What are the hopes of his labour? What doth he expect to reap thereby? Nothing but a little marrow

Google Books .pdf document equivalence problem #7884

f you have a sensor kit from Hollandse Luchten, we urge you to disconnect the humidity meter. We recently found out that the humidity

personal (desktop)computers could be used to duplicate proprietary software programs. And concernsassociated with computer crime appeared during this phase because individuals couldnow use computing devices, including remote computer terminals, to break into anddisrupt the computer systems of large organizations.

included concerns aboutpersonal privacy, intellectual property, and computer crime. Privacy concerns, which hademerged during Phase 1 because of worries about the amount of personal informationthat could be collected by government agencies and stored in a centralized government-owned database, were exacerbated because electronic records containing personal andconfidential information could now also easily be exchanged between two or morecommercial databases in the private sector.

We examine ethical issues that cutacross the spectrum of devices and networked communication systems comprisingcybertechnology, from stand-alone computers to networked systems

These include concerns affecting privacy, confidentiality, anonym-ity, free speech, defamation, and so forth. For example, did Cutler violate the privacy andconfidentiality of her romantic partners through the remarks she made about them in heronline diary?

“Megan Meier is a slut” and “Megan Meier is fat”—began to appear on MySpace.Meier, who was reported to have suffered from low self-esteem and depression, became increas-ingly distressed by the online harassment (cyberbullying) being directed at her

I fail to understand how this is such a low priority. Code review is one of the most basic and critical portions of development lifecycle, and prior to discovery of this ticket I literally had to roll an entire other repository manager just to perform that correctly when I discovered entire directories of changes had been omitted from the Gitlab generated MR. We actually found that in order to get the change set fix to apply reliably, that it is required to add "?w=1" to the url even after updating the white space setting.

Hey, checking from a few months in the future here. Is there by chance an update on this issue?

Unfortunately, the conversation on both PRs died off (no hard feelings, people have other things going on in their lives).

e doubted most students knew they were signing up for long-term monitoring when they clicked to connect to the campus WiFi.

The systems, he added, are isolating for students who don’t own smartphones,

In Sasha’s case, Benz said, the university sent an adviser to knock on her door

It also generates a “risk score” for students based around factors such as how much time they spent in community centers or at the gym.

The tracking systems, they worry, will infantilize students in the very place where they’re expected to grow into adults, further training them to see surveillance as a normal part of living, whether they like it or not.

Dozens of schools now use such technology to monitor students’ academic performance, analyze their conduct or assess their mental health.

When Syracuse University freshmen walk into professor Jeff Rubin’s Introduction to Information Technologies class, seven small Bluetooth beacons hidden around the Grant Auditorium lecture hall connect with an app on their smartphones and boost their “attendance points.”

And algorithms designed to detect suspicious movement will inevitably flag disabled students and others who do not move in the way the platforms expect, he added.

Facial recognition systems – which some proctoring platforms use to confirm the identity of the test taker – are less accurate with dark-skinned people, 

bias in facial recognition but also because of the potential for data collection.

“There are so many systematic barriers preventing people like me from obtaining these degrees – and this is just another example of tha

access to financials, course schedules and grades, and outstanding fees via voice devices.

This hasn't yet been scheduled, but we're tracking it on our backlog as something we want to do this year. A few months ago, we arranged for additional capacity to address items like this that have waited for so long. Now that additional capacity is available, it's just a matter of scheduling based on relative priority. We're anxious to get this one done, and I hope to soon have a clearer date to post here.

Companies set upfarms of servers running Web applications, with a load balancing system to route eachnew request to the least busy server. Storage area networks provided ultra-high-speedconnections between servers and disk pools. The technological lines separating main-frames, minicomputers, and personal computers were starting to blur

The bigger point here is that Microsoft was never able to turn the Web into a pro-prietary system because it couldn’t match its domination of the browser side of theWeb with similar control over the servers that generated Web pages.

Although the estab-lished Internet Relay Chat system, for exchanging real-time messages in chat roomsproved popular, other consumer-oriented messaging systems sprang up

to situate thathistory firmly within the broader stories of the Internet and of computing

cornerstone of Lycos's technique was analysis of anchortext, or the descriptions of outbound links on a Web page, to get abetter idea of the meaning of the existing page.

in 1996, it was impossible to create a pure play insearch that was economically viable. The market was still too imma-ture-robust business models were years from fruition.

fu the Web took off, so did the basic problem of search.

irst Period The Loss of the Diamond (1848) The events related by Gabriel Betteredge, house-steward in the service of Julia, Lady Verinder.