2480 Commits (d32d632f71e7b100d9c5d2b17547cbe99248c6c3)

Author	SHA1	Message	Date
ulferts	2063c4d3b8	bump deckar01-task_list	5 years ago
ulferts	5d5e246572	bump activerecord-import	5 years ago
ulferts	b432210d78	bump stackprof	5 years ago
ulferts	b1ace56730	bump newrelic_rpm	5 years ago
ulferts	5ce8b2e404	bump rinku	5 years ago
ulferts	5dae443f89	bump ruby-prof	5 years ago
ulferts	9706571104	bump net-ldap	5 years ago
ulferts	1c1cad2abe	bump commonmarker	5 years ago
ulferts	9640b96682	bump aws-sdk-s3	5 years ago
ulferts	168a4e0c90	bump aws-sdk-core	5 years ago
ulferts	9f7d8ee31a	bump database_cleaner	5 years ago
ulferts	3a9a376c95	bump rspec-rails	5 years ago
ulferts	a1dad09029	bump will_paginate	5 years ago
ulferts	5e763fea15	bump oj	5 years ago
ulferts	0ca2e1e483	bump zeitwerk	5 years ago
Oliver Günther	d9e5dc1d9d	Bump parallel_tests	5 years ago
Oliver Günther	6fc13ee3f7	Bump danger	5 years ago
Oliver Günther	a46e2e00ab	Bump parallel_tests	5 years ago
Oliver Günther	9676ef413d	Bump danger	5 years ago
ulferts	69b2db5e1a	bump multi_json	5 years ago
ulferts	a0d29cce50	bump rack-protection	5 years ago
ulferts	47015633ea	bump rack-attack	5 years ago
ulferts	ba316383a7	bump autoprefixer-rails	5 years ago
ulferts	39c836dd77	bump oj	5 years ago
ulferts	c7dc369f1c	bump gon and by that rack	5 years ago
ulferts	de6da87d36	bump html-pipeline	5 years ago
ulferts	37fcf0d83a	bump i18n-js	5 years ago
ulferts	47aef3a89c	bump bootsnap	5 years ago
ulferts	c0a7b085a5	bump puma	5 years ago
ulferts	a84dbcd42d	bump nokogiri	5 years ago
ulferts	a8c946bc8a	bump rubocop	5 years ago
ulferts	c355738159	bump oj	5 years ago
ulferts	58d3e6b2ff	bump pg	5 years ago
ulferts	3f86af1883	use actuall released friendly_id again	5 years ago
ulferts	34ac8c9621	employ advisory lock for journal creation on attachment uploading	5 years ago
Oliver Günther	1dc04fe7e0	Bump nokogiri	5 years ago
ulferts	61026b9069	bump doorkeeper	5 years ago
Oliver Günther	d93fee38a4	Fix lookups and namespacing	5 years ago
ulferts	c795909b8b	bump webdrivers	5 years ago
Markus Kahl	2e07e3cb0b	updated Gemfile.lock after openid_connect providers update	5 years ago
Oliver Günther	fdc34b424f	Bump okcomputer to fix rack issue ... [ci skip]	5 years ago
Markus Kahl	59d297d62f	updated Gemfile.lock	5 years ago
ulferts	6b7d85f16a	bump spreadsheet gem	5 years ago
ulferts	8a8de14621	print formatted description and comments in pdf export ... This implementation is a best effort one, relying heavily on the prawn_markup gem and wrapping borders around it where necessary to keep the design.	5 years ago
ulferts	f935c5cfc6	bump secure_headers to close CVE-2020-5217	5 years ago
ulferts	eed6f81286	bump rails and grape	5 years ago
ulferts	49d939615e	Reactivate event base file checkers ... This reverts commit f920cc73a0. We originally removed event base file checking to cope with problems on os x that would lead to having a multitude of fsevent_watch processes (one for every directory) and those processes would sometimes, e. g. when the system was sent to standby turn zombie. If not killed dutifully by the developer, the system would become unresponsive as the maximum number of processes as dictated by the os would be reached. Not even killing processes would be possible any more as kill requires forking. Now the listen gem was released as version 3.2.1 which changed to only needing one process to watch all directories. As event based dirty checking promises to be more performant than checking all the files, and the reload time in dev mode would exceed tens of seconds if kept running for a longer period of time, I took another stab at integrating the listen gem again: The good: * The file checking seems to work. Altering the code is reflected by the application. * Only two fsevent_watch processes are created (one for the code files and one for the locales.) * The fsevent_watch processes where exited as desired when the rails process was existed. I did not yet test it for an extended amount of time but this also seems to hold true when the system was suspended in the meantime. The bad: * Subjectively, reloading did not seem to be faster. However, I did not leave the server running over an extended period of changes. So the event based detection might shine in the long run. The ugly: * When running multitreaded, the server seems to be running into deadlocks. I assume, that there is a shared, but mutexed, resource multiple threads attempt to access at the same time. It does not happen on every page but one of the roadmap pages on my development env causes the problem consistently. The problem can be circumvented by disabling multi treading: `RAILS_MIN_THREADS=1 RAILS_MAX_THREADS=1 bundle exec rails s` The same problem does not occur when running the server with multiple worker processes: `OPENPROJECT_WEB_WORKERS=4 RAILS_MIN_THREADS=1 RAILS_MAX_THREADS=1 bundle exec rails s`	5 years ago
ulferts	df70b46a3d	bump rack to fix CVE-2019-16782	5 years ago
ulferts	7169297d43	bump excon to fix CVE-2019-16779	5 years ago
ulferts	7ccdfcc389	bump puma to fix CVE-2019-16770	5 years ago