Issue 1:
Reproduction:

Create and open a file that contains any warnings or errors from deno, let's it be a.ts, for example.

Add the file to the exclude list in deno.json:

"lint": {
"files": {
"exclude": ["a.ts"]
}
}

Config re-applies but diagnostics from a.ts do not disappear.

If we edit deno.json before opening the file - it works as should.

Issue 2:
Description

The issue below happens in these scenarios:

Running the server.ts with --watch and modifying the server.ts file triggering a restart.

Running the same file twice in separate terminal windows

Both of these cases result in the exact same message.

I added reproduce steps below the stack trace

Error Log W/ RUST_BACKTRACE

============================================================
Deno has panicked. This is a bug in Deno. Please report this
at https://github.com/denoland/deno/issues/new.
If you can reliably reproduce this panic, include the
reproduction steps and re-run with the RUST_BACKTRACE=1 env
var set and include the backtrace in your report.

Platform: macos x86_64
Version: 1.25.0
Args: ["deno", "run", "-A", "--unstable", "--watch", "test-server.ts"]

thread 'main' panicked at 'called `Option::unwrap()` on a `None` value', ext/flash/lib.rs:1316:42
stack backtrace:
0: _rust_begin_unwind
1: core::panicking::panic_fmt
2: core::panicking::panic
3: <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll
4: <extern "C" fn(A0) .> R as v8::support::CFnFrom<F>>::mapping::c_fn
5: __ZN2v88internal12_GLOBAL__N_119HandleApiCallHelperILb0EEENS0_11MaybeHandleINS0_6ObjectEEEPNS0_7IsolateENS0_6HandleINS0_10HeapObjectEEENS8_INS0_20FunctionTemplateInfoEEENS8_IS4_EEPmi
6: __ZN2v88internal21Builtin_HandleApiCallEiPmPNS0_7IsolateE
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

Error Log original

============================================================
Deno has panicked. This is a bug in Deno. Please report this
at https://github.com/denoland/deno/issues/new.
If you can reliably reproduce this panic, include the
reproduction steps and re-run with the RUST_BACKTRACE=1 env
var set and include the backtrace in your report.

Platform: macos x86_64
Version: 1.25.0
Args: ["deno", "run", "-A", "--unstable", "--watch", "test-server.ts"]

thread 'main' panicked at 'called `Option::unwrap()` on a `None` value', ext/flash/lib.rs:1316:42
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Exact Repro Steps

Scenario 1: --watch

Create new project folder mkdir project-test-watch

Navigate to project folder cd project-test-watch

Create server.ts file

echo "
Deno.serve(
(request) => {
console.log('url', request.url);
const url = new URL(request.url);
console.log('url', url);
return new Response('hehe');
},
{ port: 4500 },
);
" > server.ts

Start server in watch mode RUST_BACKTRACE=1 deno run -A --unstable --watch server.ts

Modify the server.ts file echo "\n // update file :)" >> server.ts

EXPECTED:

Server Restarts fine

ACTUAL:

The error above shows

Scenario 2: Running file twice

Follow Scenario 1's steps 1-3;

Start server RUST_BACKTRACE=1 deno run -A --unstable server.ts --watch is not needed

Open up a another terminal window

Run the same deno script to start the server (Make sure the other one is still running) RUST_BACKTRACE=1 deno run -A --unstable server.ts

EXPECTED:

Some error akin to port already in use

ACTUAL

The Second tab from step 4 outputs the error above.