Hey, I have a question about cameras.h5. Each camera seems to have 2 focal lengths (shape 2x1). All other entries seem to make sense to me (translation is a 3x1, rotation matrix is a 3x3x1, etc). Which is the right value or is there something I am missing?

As per this inline comment[1], there's a mismatch between the title/description and the actual test for systcl-17[2], martian logging.

The title says we're testing to ensure martian logging is disabled, but the actual test verifies that the logging is enabled. If I'm understanding correctly it's possible, even likely, that this is just a simple oversight in commit bb7c532f where the test

The methodology that was outline in the export.md is incredibly out-of-date. TensorFlow has official docker binaries now as well

What happened?

It's easy for people to write code like this with no failures:

} catch (InterruptedException e) {
  throw new RuntimeException(e);
}

Just rethrowing an exception like this is usually wrong because if the user is trying to abort, the calling thread will be unable to detect that an interruption happened and short-circuit.

What did you want to happen

Describe the bug
Protocol sftp is disabled by default. This enforces using scp. Described in README:

This role by default deactivates SFTP.

Expected behavior
Today I have read release notes of OpenSSH 8.0 when they say:

Picnic CSS uses a neat trick to avoid having to specify explicit colours for elements that change on hover (see also the docs). Basically, you use an inset box shadow with a partial transparency value.

This way, I could include natuive css as-is and just specify my ow

This test:

https://github.com/dev-sec/windows-baseline/blob/c093ac4531631236e09972d31f606c682e17ff54/controls/user_rights.rb#L41-L50

..currently allows for other users to be present. This is potentially necessary, if the server is a web server or SQL server, but is not secure by default, as any user can be arbitrarily added?

When this is used as a resource pack but the controls are not used it populates the output data with extra data. I think we should split this into a proper resource pack and then an example repo that depends on the resource pack and put the control tests in the example.

On the index page, we should show a label identifying whether each top-level heading is for a class, namespace, interface, etc.

As highlighted in #16, the inspec test (https://github.com/dev-sec/postgres-baseline/blob/master/controls/postgres_spec.rb#L69-L73) for:

describe service(postgres.service) do
   it { should be_installed }
   it { should be_running }
   it { should be_enabled }
end

do not work well across all operating systems. We need to investigate if this is caused by docker or by inspec.