security – Would there be any actual secure, server side way to lock away react routes?

So I don’t know what I am asking is even possible but is there any way, like you can do with static HTML and CSS websites to only let a person see the “/test” route for example if they are verified?

I know this is possible with react-router-dom but as a perfectionist, I want to do it server side with preferably express and my own middleware (using JWT and MongoDB) to check user identities ETC.

Thanks a lot!

canon – What’s the difference between holding a half-pressed shutter button and pressing the AE lock?

It’s mainly about using the camera as a tool in extreme situations where user experience and preference and circumstance mean that very fine differences in operation may make all the difference to achieving the desired shot. Use or non-use of AE lock may be appropriate for different users and differing situations.

The effect on exposure and focusing is identical as long as the camera is set to lock both of these on half pressure. With many DSLRs, having either or both or neither lock on shutter half press is an option. Similarly, the AE button can usually be set to affect focus and/or exposure and to lock or to toggle.

AE can usually be set to lock only on pressure or to toggle the controlled parameter(s) on/off alternately and focus and or exposure may be able to be controlled. This adds to theaspects needing to be considered.

I’ll use “shutter operated” for actual operation of the shutter mechanism below to avoid confusion of the term shutter-released and button-released.

The differences are minor but significant. To some extent it is a matter of preference and personal experience and both have their place. The differences probably only matter at all under extreme pressure at the outside edge of user and camera shooting ability.

The following modes are “denied to you” by using the AE lock feature:

  • With respect to multiple shots with the settings locked, this is also generally possible using shutter half-pressure but can take some getting used to. To do this the shutter is operated by full shutter button pressure, but the shutter-button pressure is then returned to half pressure rather than being released fully. This holds the locked settings and allows the next photo to be taken with the same focus and exposure settings. I find this immensely useful when you want a variable multi shot mode but slower than the auto repeat rate or at variable timing. This is to some extent an alternative to using tracking focus with the exposure locked and which is better is a matter of preference and circumstance.

  • If you like to work in “one armed wallpaper hanger mode” you may wish to set the shutter button to lock only one of the two functions, allowing the other to release after the shot when the shutter button is held and then using AE or some other option to reset and relock the second function. For example you could lock and hold focus with the shutter button but not exposure, allowing the latter to be altered and then locked with AE button or some other button. This requires the brain to coordinate several fingers with he shutter finger needing to be partial-travel controlled and would not be usual (but, you did ask 🙂 ).

    Why would you want to do that? One reason MAY be to allow tracking something that held focus position but was moving through a zone of variable lighting. This would be a rather extreme case and not usually preferred.

  • If you use AE lock it takes an extra finger operation to release it, which is one more factor (amongst many) setting the outside edge of what you can achieve in a given time in utterly extreme shooting situations.

Camera stability and ability to hold user-attention on the job at hand and to track a “target” (especially a fast moving one such as an animal or surfer or gymnast) is affected by using either AE lock or half pressure. Which way it is affected is again a matter of preference. I much prefer using shutter half pressure as it allows all control in the index finger without extra time or thought to access the AE button, to the extent that I never use AE lock, whereas others may value the lack of need to hold button tension in absolute extreme situations. (Time i a vanishingly small consideration once the preferred functionality becomes burned into the brain).

In a tripod situation of a fixed scene, or where a scene is not going to change for some seconds until a critical moment arrives (head turns, bird flaps, diver dives, …) and a shot will be taken, perhaps with a “cable release”, use of AE lock may be preferred to maintaining half pressure for an extend period. An alternative is to swap focus to manual mode and to accept the minimal penalty of exposure ‘calculation’ at exposure time, ot to use AE toggle, but this too is a preference.

Other similar and subtle considerations could be thought of.

How to remove first lock screen and only keep the second one on Huawei?

When I want to use my phone I press the power button then it asks me to swipe up to unlock, I do that and then it asks me to enter the graphic code as the security measure. This is annoying because I only want to enter the graphic code and skip the first screen that only asks me to swipe up. How? I tried every setting I could find and googled for hours. Basically it feels as I am unlocking the phone twice. I am using Huawei default desktop, no third party home screens or lockers are installed. My phone is y8p.

lock screens – Turn off “double-tap to unlock” on Samsung Galaxy S7

I have a Galaxy S7 SM-G930U and had the same issue. Both during incoming and outgoing phone calls my phone would display a padlock symbol and a message reading “Double tap to unlock.” This would overlay the call information screen behind. When the message was displayed, I was unable to hear a ring or voice on the call.

The workaround was to quickly double-tap and press speaker to allow the phone call to function.

I had recently installed a new head phone jack inside the phone and had also received a software update. Trying new phone apps did not solve the problem, so I suspected it was a hardware issue. I went through all of the steps necessary to remove the back cover, disassemble the phone and removed and reattached the battery connection. I had taken this step to replace the headphone jack. Somehow the battery connection must have been loose because reattaching the battery solved the ‘double-tap’ issue for me. Disassembling your phone is a process, be careful, or take your phone to a shop to check it.

Quick Settings enable/disable each setting/icon on lock screen

Your privacy

By clicking “Accept all cookies”, you agree Stack Exchange can store cookies on your device and disclose information in accordance with our Cookie Policy.

lock screens – After factory reset Google Backup asks for pattern, can’t restore

My Redmi Note 8 suddenly stopped accepting my correct pattern lock, so I was forced to reset. It turns out I had Google Backup enabled, which was a happy surprise. However, it asks me for the previous pattern lock of the phone, which it still won’t accept. This is incredibly frustrating.

Is there anything I can do to get access to the backup file or be able to use it? Will it get deleted if I don’t restore it right now, in the initial setup?

Thank you.

amazon web services – Lock in AWS Lambda functions to avoid concurrent run of some critical section of the code

We have an AWS Lambda function which calls 3rd party API. That 3rd party system has some concurrency issue so under some circumstances if we call that API from several instances of the lambda function, which are running at the same time, we end up duplicated objects created in 3rd party system. Vendor of that system is not promising to fix that issue quickly so for the moment we need to avoid concurrency of the section of the code which calls that API

Our Lambda function is triggered when file is dropped into S3 bucket, so when multiple files are dropped at the same time, each of these files is processed by a running an instance of this function in parallel.

For the performance reasons we would like to continue processing files concurrently, so we do not consider a solution using a queue (like SQS) to put the files in queue and then call lambda function for each of them sequentially.

What is the easiest way to write a kind of a


command to block that critical section of the code that calls 3rd party API from executing in parallel instances?

We think that we can probably implement that by updating a value in DynamoDB and checking if it is locked or not, but at the moment we don’t use DynamoDb , our solution contains S3 buckets and serverless components like AWS Step Functions, Lambda functions, Glue jobs, so introducing a database just for a single purpose of controlling locks sounds like an overkill

Any thoughts are welcome

security – Possible to have different passwords for device encryption and screen lock?

Your privacy

By clicking “Accept all cookies”, you agree Stack Exchange can store cookies on your device and disclose information in accordance with our Cookie Policy.

settings – I want to lock the safe search on my phone

Your privacy

By clicking “Accept all cookies”, you agree Stack Exchange can store cookies on your device and disclose information in accordance with our Cookie Policy.

node.js – error No lock file in this directory. Run yarn install to generate one. LERNA JENKINS

I am using Lerna ( for managing my monorepo with the following structure:


(The above structure is the minimal example I could give, actual project has many more sub repos but this is the only one that’s built on Jenkins.)

On my local machine with Yarn and NPM version as follows:

yarn: 1.22.10
node: v12.14.1

I run the following commands to build my APP1 from my root directory

cd ./packages/app/app1
yarn build

which generates dist folder in packages/app/app1.

But when I run the same set of commands on Jenkins I get the following error:

error No lockfile in this directory. Run yarn install to generate one.
error Command failed with exit code 1.

Since I’m using lerna, my lockfile is in root directory. Why am I getting this error? Why not on local machine?

Node and Yarn versions on Jenkins:

yarn: 1.9.10
node: v12.16.1