Of course, it could appear in the server logs (or be detailed on a file dumped on the filesystem) - but it seems PHP have just decided to move to Github, and may not actually care about this, so it may not see the light of day.
782 karma · joined February 4, 2016
Of course, it could appear in the server logs (or be detailed on a file dumped on the filesystem) - but it seems PHP have just decided to move to Github, and may not actually care about this, so it may not see the light of day.
That's even more evident for simple stuff that doesn't need debugging on the logic, but benefits from the Lambda features in terms of scaling etc.
Not mentioned is that your unit tests should be getting you most of the way...
GPT-3. Which I think is reasonable - not a lot of work to read it through and replace it with "on Zoom, or next time you're in the bay area".
Good point on the calendar though.
Daniel is clearly smart, but he's not thinking big enough. This is practically inter-galactic.
SE says it better than me: https://security.stackexchange.com/questions/213401/is-curl-...
Particularly the first link, which outlines how to return different things depending on whether it's being piped into bash or not: https://www.idontplaydarts.com/2016/04/detecting-curl-pipe-b...
https://app.amplication.com/ckjuaxw2518112510s6qfb0xi8q shows {"statusCode":500,"message":"Internal server error"} for code download, and has been waiting for a sandbox environment for a while.
But I'll be back to try it again in a few days :)
You have to use the cog icon on the FROM to add more bits to the FROM.
Unless you can provide a straight username/password option I'll have to pass.
I guess you don't want to handle them, which makes sense, but there are plenty of other services that can handle it for you.
Louder please - this is applicable far beyond cryptocurrency.
And of course some organisations do both - public cloud for new stuff which can be secure from day 1, and internal platforms for the keys to the kingdom or legacy stuff.
403 ERROR The request could not be satisfied. Bad request. We can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner. If you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.
Generated by cloudfront (CloudFront) Request ID: CYfM2liDaLwK2Mu8q7vnSE5rn89Fg8HmUSY6jIrL_5iTxe2dU1ADyw==
The only interesting things in it are whether you set firmwide/regional minimums/maximums, and how far you allow the ranking to move your numbers from everyone getting the same increase - eg, does the top ranked employee get 5% more than the median employee, or 50% more?
This has been bugging me for at least 10 years, and also extends to IM. If it's IM, I ask one at a time.
If it's email, I either have to ask one at a time, form the two questions into one, or turn it into a sandwich - question 1, question 2, rephrase question 1.
What I really want to do is grab them by the shoulders and shake them, shouting "You saw the second question - yes?!?!"
However someone is trying to make robotic process automation the Next Big Thing - which I think is hysterically funny.
He might not have directly interacted with it - doesn't mean he didn't see it? Shared by a friend?
Or are their analytics so detailed that they can guarantee he never saw it?
> The way the team engineered this is by queuing up the process while the two servers are still negotiating their TLS handshake.
That's pretty cool. I'm trying to see a downside, given that presumably it won't spin up a function for traffic from IPs it knows are abusive.