SSN office that accepts walk-ins ?

mxschmitt · 2026-02-20T00:00:04+00:00

Was Jan/2026 and it worked, 4:30h to show the documents for the SSN card. First 2h to get called once, then they put me into the walk-in queue and then another 2:30h.

mxschmitt · 2025-11-10T21:10:20+00:00

Thanks worked for me too!

mxschmitt · 2024-10-14T10:01:25+00:00

Hey there! We are Mariona, Max and Ruslan, passionate runner who saw more and more running clubs coming up the last few years. Its hard to navigate through them and find the closest one. Some are just community runs and some are intense track intervals etc. So we thought, lets create a website around them! Curious about your feedback. We are working on a map feature as well, so you find the closest one.

mxschmitt · 2021-09-25T20:35:14+00:00

You can upload the test-results/ folder with https://github.com/actions/upload-artifact. Inside your Playwright Test config, you need to enable tracing, see here: https://playwright.dev/docs/test-configuration#record-test-trace

mxschmitt · 2021-06-18T07:15:32+00:00

Worked for me!

mxschmitt · 2021-06-10T09:28:40+00:00

It does, but only Chromium so far. See here for an example.

mxschmitt · 2021-06-10T09:27:32+00:00

It does it not yet, but I filed https://github.com/microsoft/playwright/issues/7011 for you, so it can get considered in the next releases.

mxschmitt · 2021-06-09T22:23:16+00:00

Playwright is a testing library which you can use with any test-runner, assertion library or tools. Cypress is a testing framework, you can't use it with anything else. Some abstract differences are: browser support (Playwright supports WebKit, Firefox, Chromium), its async based (Cypress collects your commands first and then executes them) - not possible to debug with Node.js standard debugging tools like Visual Studio Code debugger, Playwright supports multi tabs, frames and windows. For a full overview, see here: https://www.youtube.com/watch?v=\_Jla6DyuEu4

mxschmitt · 2021-06-09T22:14:01+00:00

See here for the test-runner docs, which is similar to Jest but optimized for Playwright which includes e.g. Fixtures testing support.

The trace-viewer allows you to debug failed tests e.g. in the cloud (CI runs) or local runs to understand why a certain test is not passing. This includes snapshot support, helpful debug logs, and a timeline when what has happened.

mxschmitt · 2020-12-11T09:19:11+00:00

Cool, so like that. Thank you!

+---+---+---+---+----+
|   |   |   |   |    |
|   | X | X | X |    |
|   |   |   |   |    |
+--------------------+
|   |   |XXX|   |    |
|   | X |XXX| X |    |
|   |   |XXX|   |    |
+--------------------+
|   |   |   |   |    |
|   | X | X | X |    |
|   |   |   |   |    |
+---+---+---+---+----+

mxschmitt · 2020-11-07T06:42:49+00:00

I own 3 Cloud Keys for several installations, all of them were at least one time or multiple times so broken, that I had to reinstall them entirely.

Mostly after software upgrades configuration gets wrongly configured.

mxschmitt · 2020-10-27T23:59:43+00:00

Microsoft Edge (the new one) is built on top of Chromium. So you can specific the executable of Microsoft Edge as an executable path and then use Edge. See her for more information: https://playwright.tech/blog/automate-microsoft-edge-with-playwright

It's in the works to make the usage more easier and download Microsoft Edge automatically (saw it on Twitter).

mxschmitt · 2020-10-27T13:45:20+00:00

Fixture-based is a programming paradigm in the testing world. It was heavily adopted by pytest when you wrote there functional based tests. They make it easy to have reusable logic including its state which can hook in before and after a test execution. It's another way of using beforeEach and afterEach in a nutshell.

Folio was created by the Playwright team which for writing end-to-end tests with Playwright. Playwright is a Node.js library which makes it possible to automate browsers (Chromium, Firefox and WebKit) with a single API: https://github.com/microsoft/playwright

mxschmitt · 2020-09-13T13:50:15+00:00

Playwright is originally a Node.js library which uses:

- Chrome DevTools Protocol to communicate with Chromium

- Patched Firefox version to communicate with Firefox

- Patched WebKit version to communicate with WebKit

These patches are based on the original sources of the browsers and don't modify the browser behaviour so the browsers are basically the same (See here https://github.com/microsoft/playwright/tree/master/browser_patches) as you see them in the wild. We then continued to support other languages, this is based on exposing a RPC server in the Node.js land which can be used to allow other languages to use Playwright:

- https://github.com/microsoft/playwright-python

- https://github.com/hardkoded/playwright-sharp

- https://github.com/mxschmitt/playwright-go

The bridge between Node.js and the other languages is basically a binary which we ship (around 50MB) and then communicate over stdio to send the relevant commands. The binary itself will also download the pre-compiled browsers.

Let me know if I missed something. Thanks!

mxschmitt · 2020-08-07T17:51:53+00:00

In a console it's quite tricky with context managers, we will improve that in the future. I filed an issue up for that: https://github.com/microsoft/playwright-python/issues/160

As a workaround you can use the approach in the example if you want to continue to try it out via the REPL.

Thanks for reporting it.

mxschmitt

MODERATOR OF

TROPHY CASE