puma--puma/test/config/control_no_token.rb

activate_control_app 'unix:///tmp/pumactl.sock', { no_token: true }

app do |env|
  [200, {}, ["embedded app"]]
end
Fixes the bug that wouldn't allow no_token be set to true (#1803) * Fix crash when no_token is set * Use a more meaningful name instead of an empty string * Adds a test to ensure `{ no_token: true }` works * Adds an explanation for the usage of a String Just to justify the use of a String instead of a Symbol. * Removes thread that would start the server This removes the part of the test that would start the server. The reason why the thread was being created originally in the PR was to ensure that the server was booting even with `{ no_token: true }`. I believe we don't need to test the full server boot but just ensure that we won't pass a Symbol to OptionParser. In particular the test ensures that the token will be set to `'none'` when `no_token: true`. There're already other tests testing that the server boots. 2019-05-28 09:37:34 -04:00			`activate_control_app 'unix:///tmp/pumactl.sock', { no_token: true }`

			`app do \|env\|`
			`[200, {}, ["embedded app"]]`
			`end`