- What are conditions under which data loss may occur?
Tracing framworks have the following components:
- A client library that is used directly in the application code for instrumenation
- A sidecar application that buffers data from the client library and passes it along
- A dedicated aggregation and reporting server that accumulates and processes data from sidecar applications
- General questions about his background and experience
- Two-way chit-chat about microservices best practices and trade-offs
- Coding problem:
- Using any programming language (even pseudocode), write a function that takes in a string and outputs the first non-repeating character
First, I don't know the answer to this yet, so I can't tell you. What I can do is show you how I'd find the answer.
I'll be using line numbers, which will change when you merge master
back into your branch.
The commit I'm working off of is the current git HEAD of your PR.
I can't find any reason for this in the code. But based on its movement from staging to production at roughly our deploy cycle cadence, I advise checking to see if there is any environment/config changes that are responsible.
At some point, staging and production each started encountering the same error:
- URL: http://apidocs.parsable.com
- username: admin
- password: wearable-195
- apidocs link: http://apidocs.parsable.com/job_template.html#Fn_JobTemplateService_acquireLock
- HTTP method: POST
This gist is to verify the safety and effectiveness of the script for backfilling document checksums. The script can be found on this mothership PR.
This "script" is meant to fill in checksums for any documents table row that should have a checksum, but doesn't. Documents "should have" a checksum if pending == false. But not all do.
We're introducing a new UI that will be feature-flagged. In order to determine that the new UI doesn't depart from the old UI in the wrong ways (e.g. not showing documents, or leaving off steps) we need to compare the new and old UIs when presenting the same jobs We'll select the three most-used recurring jobs from the six most active customers for this purpose.
In environment E, we have two teams, T1 and T2. T1 has the new-UI feature flag on, but T2 doesn't.
See PA-14782
-
Accept Shea's invitation to the Pow team
shea-team
-
Use 'Advanced' options to ignore the SSL certificate problems, so you can access the website
-
Ensure you can log in to the web view with a password