Increase rack timeout in development to fix assets locally

[zachmargolis]

Why: Low timeouts consistently trigger a segfault in
sassc, it happens even more often in Ruby 3 than it did
before

[jmhooper]

I think you want a string here. Also, we can probably make is something more reasonable, like 10 minutes

[zachmargolis]

it's valid YAML! and our config parser just calls Integer() on it anyways

require 'yaml'
YAML.load <<-STR
rack_timeout_service_timeout_seconds: 9_999_999_999
STR
=> {"rack_timeout_service_timeout_seconds"=>9999999999}

identity-idp/lib/identity_config.rb

Lines 18 to 20 in 0f018a5

	integer: proc do |value|
	Integer(value)
	end,

[jmhooper]

Ah sweet. There used to be something that yelled at you when you put non string values in here. Maybe that went away with Figaro.

[mitchellhenke]

Yeah, it was a Figaro-ism because it also had to be able to write the value to the system environment variable

[solipet]

do we need to add this to test as well?

[zachmargolis]

I figure the problem happened most often in development? But yeah I guess it wouldn't hurt to add to test... will follow up

[zachmargolis]

#5766