Unable to test for SublimeText 3

[kaste]

It looks like that we can't test against Sublime Text 3.

For example, just re-running the test from master gives https://github.com/kaste/UnitTesting/pull/1/checks?check_run_id=2684397425

[randy3k]

Um, it used to work a few days ago. Let me take a look later.

[randy3k]

I haven’t checked, but I have a feeling that it is due to a pop up prompting ST3 users to upgrade to ST4.

[randy3k]

Confirmed.

[randy3k]

The setting

"update_check": false

does work but it requires us to specify a license that is not very feasible in CI.

[kaste]

Hm, appveyor still passes though timbrel/GitSavvy#1476

[kaste]

Can't we just send ESC to the dialog window?

[kaste]

Or we block the Sublime ip addr. That should be doable on linux

[randy3k]

Hm, appveyor still passes though timbrel/GitSavvy#1476

AFAIK, the popup on macOS and Linux is blocking the UI, perhaps the popup is not blocking on windows.

[kaste]

Ah, the popup is not blocking on Windows. You can just alt+tab to the editor window.

[randy3k]

Can't we just send ESC to the dialog window?

Or we block the Sublime ip addr. That should be doable on linux

Blocking Sublime IP sounds a better approach. Sending ESC is difficult to be delivered consistently and cross platformly.

[randy3k]

The following does work for macos

sudo route -n add -host 45.55.41.223 127.0.0.1

however its linux variate doesn't work because route seemingly doesn't work in docker containers without additional privilege.

[randy3k]

New-NetFirewallRule -DisplayName "Block sublimetext.com IP address" -Direction Outbound –LocalPort Any -Protocol TCP -Action Block -RemoteAddress 45.55.41.223

works on windows.

[randy3k]

Ironically, I still cannot find a way to block ip on docker without "--privileged".

[randy3k]

I found a solution for Linux, but it requires passing --cap-add=NET_ADMIN to docker.
https://github.com/SublimeText/UnitTesting/blob/blockip/.github/workflows/build.yml#L16-L17