we cannot create the so-called new without addressing the historical homes that have been created.

he analysis reveals that media coverage is dominated by five themes: military justice, institutional structure, culture, gender/gender integration, and change. Gender is a relatively minor focus throughout media coverage, with attention to court cases dominating the majority of the coverage.

Institutional gaslighting includes political strategies to resist critiques of the institution or discredit evidence that undermines the authority or carefully crafted image of the institution.

Military exceptionalism is shaped by ideals of "good militaries" and "good soldiers," which are constructed as necessarily white, masculine, exclusive, and reproduced through the regulation of sex and the exclusion of women and racialized groups.

the bodh SATA path is what is the structure and practice that allows the soul to become embodied

what is our offering to this fourth turning because this is the you know the fourth training is a planetary process so it's not you know it's not us but what is our offering so essentially um you know it is a an education in in the the where psychology and spirituality meet

The Indians are today where civilized man then was.

The regime's discourse was directed not only at domestic audiences but also at international ones, particularly in the West, where it sought to project its strength and legitimacy through civilizational language that focused on barbarizing the opposition.

discourse of racial militarism to justify its brutal crackdown on opposition groups, particularly those with Islamic affiliations.

ecular militarism also plays a role in othering and excluding those who seek a greater role for religion in political and public life.

reinforce a masculinist nationalism through militarism

Syria's militarist state has been shaped by its experience of colonization, and its militarism is directly connected to the country's anticolonialism

The ideal masculine identity was tied to militarism

Racial militarism played a significant role in shaping insider-outsider boundaries of national identity, with militarism performing an exclusionary function within the nation-state.

The construction of the "Other" was also racialized

militarism, which was used to facilitate the transition from one epoch of human development to the next.

militarism is not only shaped by colonialism but also perpetuates racial hierarchies and civilizational anxiety.

Want to really annoy an open-source maintainer? Then ignore any communication channels they have setup for support.

Rails' observers were partly inspired by aspect-oriented programming -- they're about cross-cutting concerns. If you're putting business logic in observers that is tightly coupled to the models they're observing, you're doing it wrong IMO.

Instance methods Instances of Models are documents. Documents have many of their own built-in instance methods. We may also define our own custom document instance methods. // define a schema const animalSchema = new Schema({ name: String, type: String }, { // Assign a function to the "methods" object of our animalSchema through schema options. // By following this approach, there is no need to create a separate TS type to define the type of the instance functions. methods: { findSimilarTypes(cb) { return mongoose.model('Animal').find({ type: this.type }, cb); } } }); // Or, assign a function to the "methods" object of our animalSchema animalSchema.methods.findSimilarTypes = function(cb) { return mongoose.model('Animal').find({ type: this.type }, cb); }; Now all of our animal instances have a findSimilarTypes method available to them. const Animal = mongoose.model('Animal', animalSchema); const dog = new Animal({ type: 'dog' }); dog.findSimilarTypes((err, dogs) => { console.log(dogs); // woof }); Overwriting a default mongoose document method may lead to unpredictable results. See this for more details. The example above uses the Schema.methods object directly to save an instance method. You can also use the Schema.method() helper as described here. Do not declare methods using ES6 arrow functions (=>). Arrow functions explicitly prevent binding this, so your method will not have access to the document and the above examples will not work.

You can see how the constant jumping between these two tools in the first scenario is super annoying, and also very risky as none of the changes you make in Figma are also automatically being updated in the same GitLab designs.

As a positive example of where this works well: Our VS Code GitLab Workflow extension allows users to not only see comments that were written inside the GitLab UI, but also allows these users to respond to these comments right from the IDE, the tool where they actually have to make these changes.

you don't start a feminist revolution by arguing with your dad. (Marjorie laughs) He might be the one who needs to change, but that doesn't mean that you start there. 00:22:55 You start by talking to each other. We need to come together. We need to have solidarity.

Let’s check out what the refinement approach looks like and why I consider it the best way to implement conversion wrappers.

were almost wholly conducted by women;

On July 19-20, 1848, 68 women and 32 men attended the First Women’s Rights Convention which was held in the upstate New York town of Seneca Falls

gaga's third question where are we going is what i want to address in these talks 00:05:26 it may seem unanswerable who can foretell the human course through time but i think we can answer it in broad strokes by answering the other two questions first 00:05:40 if we see clearly what we are and what we've done we can recognize human behaviors that persist through many times and cultures and knowing these can tell us what we 00:05:52 are likely to do and where we are likely to go from here

the artist managed to harness his grief to produce a vast painting more a mural in conception than a canvas in which like the victorian age itself he demanded 00:04:31 new answers to the riddle of existence he wrote the title boldly on the image three childlike questions simple yet profound where do we come from 00:04:46 what are we where are we going the work is a sprawling panorama of enigmatic figures amid scenery

The next two questions are where to play and how to win. These twochoices, which are tightly bound up with one another, form the very heart ofstrategy and are the two most critical questions in strategy formulation.

I have yet to see a Snapd or Flatpak build of Audacity that I'm happy with. Those builds are beyond our control as they are made by 3rd parties. I do find it mildly annoying that Flatpak direct users that have problems with their builds to us.

Many of the workers reported that first thing in themorning, or after any interruption in their thought(like a ‘phone call), they have the “where was 1?”problem in a complex and ill-defined space of ideas.The layout of physical materials on their desk givesthem powerful and immediate contextual cues torecover a complex set of threads without difilcultyand delay, “this is my whole context, these are mypersonal piles”

For Jerome Bruner, the place to begin is clear: “One starts somewhere—where the learner is.”

Where around hooks shine is when you want to run an example within a block. For instance, if your database library offers a transaction method that receives a block, you can use an around to cleanly open and close the transaction around the example.

And it’s easier to share a personal story when you’re composing it 280 characters at a time and publishing it as you go, without thinking about or knowing where the end may be. It’s at least easier than staring down a blank text editor with no limit and having to decide later how much of a 2,500 word rant is worth sharing, anyway.

Users think every Webpack tool/config problem is a problem with a specific package and opens an issue asking for support on the package instead of Webpack. In the past year alone, I’ve had to deal with hundreds of Webpack issues on my repos.

This works nicely wherever we show authors, but after we deploy to production, the folks from other parts of the world won’t get notified anymore about their songs. Mistakes like these are easy to make when using concerns.

Whether you agree or not, to me there's nothing in this world that is entirely apolitical - when there are people there is politics. You don't have to agree with my views, nor do I expect you to. Diversity and disagreement is what drives mankind forward.

Thanks, this was just what I was looking for! This is a perfect appropriate use of instance_eval. I do not understand the nay-sayers. If you already have your array in a variable, then sure, a.reduce(:+) / a.size.to_f is pretty reasonable. But if you want to "in line" find the mean of an array literal or an array that is returned from a function/expression — without duplicating the entire expression ([0,4,8].reduce(:+) / [0,4,8].length.to_f, for example, is abhorrent) or being required to assign to a local, then instance_eval option is a beautiful, elegant, idiomatic solution!!

A litmus test on whether an option belongs to adapter config or kit config, would be to ask whether the option becomes irrelevant when you switch the adapter to static.

So even if it works for you, you won't know where it breaks.

CSS seems like the right place to put visual information. On the other hand, few would argue that image "src" should not be specified as an attribute and the height/width seem as tied to the binary image data as the "src" is.

We are are continuing our commitment to creating our games that are free and widely accessible anyone that is curious by making our game files available under Creative Commons license BY–NC–SA 4.0. That means we will continue offering a full, free print-and-play kit for Pax Pamir, and later this campaign, John Company! Anyone can use, remix, and share the game, so long as they do not use it for commercial purposes. 

however, if this is relevant to just one spec, you don't necessarily need to include devise helpers to all your controllers specs, you can just explicitly include those helpers in that one controller describe block: require 'spec_helper' describe MyCoolController include Devise::TestHelpers it { } end

Wasn't sure if this belonged as an issue in Devise or Rails though.

This is a great application for using route constraints.

Application: 3-D Shape RegistrationAn important problem in model-based recognition is to find the transformation of a set of datapoints that yields the best match of these points against a shape model. The process is oftenreferred to asdata registration. The data points are typically measured on a real object by rangesensors, touch sensors, etc., and given in Cartesian coordinates. The quality of a match is oftendescribed as the total squared distance from the data pointsto the model. When multiple shapemodels are possible, the one that results in the least total distance is then recognized as the shapeof the object.Quaternions are very effective in solving the above least-squares-based registration problem.

It sounds like a gnome-open (or the equivalent library call) bug. Reassigning.

I'm kinda stuck at the moment, going around in circles. Everything is really heavily coupled. I would like to get to the point where no load is called from within processors, but i'm not sure if that's possible. Currently the API and the caching strategies are fighting me at every step of the way. I have a branch where i'm hacking through some refactoring, no light at the end of the tunnel yet though :(

it's super hard to test master because i have no idea which gems need to be updated. is there a guide on how to take a rails 4.2 project to master sprockets without everything mysteriously exploding? ill try to make a repro case but its hard to tell where to even start

Is there a PR to... something? sassc-rails? That would make the patch not necessary? (I don't know if there's any good way to monkey-patch that in, I think you have to fork? So some change seems required...) Should the defaults be different somehow? This is very difficult to figure out.

Is there a PR to... something? sassc-rails?

Please note that the I/O DSL is only providing the most-used requirements. Feel free to use the low-level taskWrap API to build your own variable mapping with different scoping techniques.

Knowing about the wiring mechanics in Trailblazer is one thing. However, the real fun starts with nesting activities. That’s when the ideas of encapsulation, interfaces and reducing dependencies really come into play.

Whether this is the life-cycle of a <user> entity or just a sign-up function, it has to be defined and coded somewhere.

Trailblazer extends the conventional MVC stack in Rails. Keep in mind that adding layers doesn't necessarily mean adding more code and complexity. The opposite is the case: Controller, view and model become lean endpoints for HTTP, rendering and persistence. Redundant code gets eliminated by putting very little application code into the right layer.

ActiveInteraction plays nicely with Rails. You can use interactions to handle your business logic instead of models or controllers.

Why is all this interaction code better? Two reasons: One, you can reuse the FindAccount interaction in other places, like your API controller or a Resque task. And two, if you want to change how accounts are found, you only have to change one place.

I'm sure there will be a few other people out there who eventually want something like this, since Interactions are actually a great fit for enforcing consistency in data structures when working with a schemaless NoSQL store, but obviously it's still a bit of a niche audience.

The non-determinism is why cache invalidation — and that other hard problem, naming things — are uniquely and intractably hard problems in computer science. Computers can perfectly solve deterministic problems. But they can’t predict when to invalidate a cache because, ultimately, we, the humans who design and build computational processes, can’t agree on when a cache needs to be invalidated.

Creating more legally binding licenses and contracts just perpetuates the problem of law – a.k.a. state force – intruding where it doesn’t belong.

This nav bar by Chris Coyier is a great example of something that makes more sense as a flexbox than grid.

Flexbox's strength is in its content-driven model. It doesn't need to know the content up-front. You can distribute items based on their content, allow boxes to wrap which is really handy for responsive design, you can even control the distribution of negative space separately to positive space.

Ubuntu also supports ‘snap’ packages which are more suited for third-party applications and tools which evolve at their own speed, independently of Ubuntu. If you want to install a high-profile app like Skype or a toolchain like the latest version of Golang, you probably want the snap because it will give you fresher versions and more control of the specific major versions you want to track.

Great, I can use vw to scale text so it doesn't look puny on a desktop! Perfect... Oh. Huh, now the text is too small to read when viewed on a phone. Okay, well I can just use "max(x,y)" to make sure it doesn't get shrunk beyond a minimum size. Perfect... Oh. Hmm. Looks like "max" isn't supported properly by Chrome. Okay, well guess I'll just use "px" again.

CSS Grid Layout excels at dividing a page into major regions or defining the relationship in terms of size, position, and layer, between parts of a control built from HTML primitives.

Making literal grids. Like X columns with Y gap between them homegrown framework stuff. grid-gap is wonderful, as gutters are the main pain point of grid systems.

It must be called during the component's initialisation (but doesn't need to live inside the component; it can be called from an external module).

Nodes A wave function node occurs at points where the wave function is zero and changes signs. The electron has zero probability of being located at a node.

The main reason to use these lower-level components is if you need to customize your form input in some way that isn't supported using TextField.

In my opinion, deleting a user is not a function executed by an item on itself but is a function done by the holder of the array. So in your case you would be better of moving the deleteUser up to App.

When you use a function like color(). it’s impossible to know exactly where it was defined. Which @import does it come from?

Prettier’s printWidth option does not work the same way. It is not the hard upper allowed line length limit. It is a way to say to Prettier roughly how long you’d like lines to be. Prettier will make both shorter and longer lines, but generally strive to meet the specified printWidth. Remember, computers are dumb. You need to explicitly tell them what to do, while humans can make their own (implicit) judgements, for example on when to break a line. In other words, don’t try to use printWidth as if it was ESLint’s max-len – they’re not the same. max-len just says what the maximum allowed line length is, but not what the generally preferred length is – which is what printWidth specifies.

I'm not sure what's the best solution, but it could be a good idea to print the full path only at the end of the line, since it takes a lot of space, or to move it to a separate line.

Yeah I see what you're saying. In my case, I had a group of classes that relied on each other but they were all part of one conceptual "module" so I made a new file that imports and exposes all of them. In that new file I put the imports in the right order and made sure no code accesses the classes except through the new interface.

it also allows for more divergence in how people write there code and where they put their logic, making different svelte codebases potentially even more different due to fewer constraints. This last point is actually something I really value, I read a lot of Svelte code by a lot of different people and broadly speaking things look the same and are in the same places.

Keep the local state isolated.Think about which state is local to a particular UI representation — and don’t hoist that state higher than necessary.

He says that he sees the combination of long form pieces and Q&A as a new level of support. “We used to have level one, which was sending a ticket to the help desk, and it was something we could easily resolve for you. Level two was a more complex problem that maybe required an engineer or specialist from a certain team to figure out. I look at this new system as a level zero.” Before sending us a ticket, folks can search Teams. If they find a question that solves the problem, great. If they need more details, they can follow links to in-depth articles or collections that bring together Q&A and article with the same tags.“

I took the same approach with _layout.svelte and not just for the svelte-apollo client. Except I put all of that setup into another module (setup.js) and imported from _layout. I just couldn't stomach having all that code actually in my _layout file. It's for layout, supposedly, but it's the only component that is a parent to the whole app.

I got this working by using _layout.svelte as the point to initialise and set the Client we can then use getClient in each route that uses this layout.

there is one major weakness to this approach and to scoped CSS: organization gets very hard – you end up with styles everywhere!

Keeping the CSS with the HTML for organization may have value however.

but adding logic to the <script> is unfortunate

require 'minitest/autorun' class BugTest < Minitest::Test

Technical and general support for those using our free options is “Community First”. Like many other free SaaS products, users are first directed to find support in community sources such as the following:

For general questions, use cases, or anything else that does not fit into one of the above cases, please post in the GitLab Forum or on a third-party help site.

If you're in a paid tier on GitLab.com or GitLab Self-managed, you're entitled to Support. Please open a support ticket after reviewing our Statement of Support

If you're a free user on GitLab.com and are having one of the following specific issues please file a support ticket after reviewing the Free Plan Users Section in our Statement of Support

Account Support If you haven't received your confirmation email, you can request to resend your confirmation instructions via our confirmation page.

We're closing the Support Forum issue tracker in favor of the Community Forum and support channels. We recognize that the Support Forum issue tracker has not received much attention in the last few months, and want to redirect our community members to locations that are regularly monitored by GitLab staff. As a result, this issue will be moved to the GitLab product issue tracker and triaged there.

Types of questions and where to ask: How do I? -- ask on Server Fault (tell them what tags to use -- your product tag at minimum) I got this error, why? -- ask on Server Fault I got this error and I'm sure it's a bug -- report it on your own site I have an idea/request -- report it on your own site Why do you? -- ask in your own community (support forum, etc) When will you? -- ask in your own community