1080 Commits (752743a349dbe013fe46c6a00778cd77d42ce1a8)

Author	SHA1	Message	Date
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
ulferts	c795909b8b	bump webdrivers	5 years ago
Oliver Günther	fdc34b424f	Bump okcomputer to fix rack issue ... [ci skip]	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
Henriette Dinger	bd7f4e4814	Update copyright notice	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	7ccdfcc389	bump puma to fix CVE-2019-16770	5 years ago
Oliver Günther	35d30e18af	Add xml writer	5 years ago
Oliver Günther	d3594766c8	JSON viewpoint mapper spec	5 years ago
Oliver Günther	d19262114e	Bump nokogiri to 1.10.5	5 years ago
Oliver Günther	f2bcf466d6	Bump rails to 6.0.1 and dependent gems	5 years ago
ulferts	4befc236f9	bump rspec gems	5 years ago
Oliver Günther	d01d33c631	Bump ruby and bundler	5 years ago
Oliver Günther	1e4b090076	Bump danger	5 years ago
ulferts	78a0aaa60a	bump puma	5 years ago
ulferts	c83ba63640	Revert revert unwanted in dev branch ... This reverts commit b05a8f7b54. The release/10 branch received a revert that was applied after changes from dev unwillingly where merged into it. But when merging release/10.0 back into dev, that revert was also applied to dev where the changes are indeed wanted. So we revert the revert for dev.	5 years ago
Oliver Günther	b05a8f7b54	Revert "[31080] Trigger wpEvent after custom action"	5 years ago
ulferts	ccaf1989d6	bump test-prof	5 years ago
ulferts	a3317eb748	bump capybara	5 years ago
ulferts	e7263fcedb	migrate to rails 6.0.0	5 years ago
ulferts	ce9522dca2	use awesome_nested_set 3.2.0	5 years ago
ulferts	4656715a85	bump rspec-rails to 4.0.0 beta2	5 years ago
Oliver Günther	569c70aa18	Replace deprecated chromedriver-helper with webdrivers ... We're using a fixed outdated version of chromedriver. Instead we should use the latest stable, as we do with the stable chrome version.	5 years ago
ulferts	d48342660b	bump browser	5 years ago
ulferts	ddc9e10602	bump sanitize	5 years ago
ulferts	159a1e56b3	remove unused codecov	5 years ago
ulferts	9c6c7d76b3	bump html-pipeline	5 years ago
ulferts	19e04691d0	bump secure_headers	5 years ago
Oliver Günther	cace1b1015	Test dangerfile in test and development environment	5 years ago
ulferts	53a24ab38a	bump aws-sdk-s3	5 years ago
ulferts	99af3511bd	bump aws-sdk-core	5 years ago
ulferts	4f9938aef6	bump parallel_tests	5 years ago
ulferts	51b50c6196	bump webmock	5 years ago
ulferts	f46d5a296b	bump activerecord-import	5 years ago
ulferts	fe0e062aeb	bump activerecord-nulldb-adapter	5 years ago
ulferts	20a9a1c70d	bump bootsnap	5 years ago
ulferts	e5157b3c0d	bump rack-attack	5 years ago
ulferts	20ac95e331	bump puma	5 years ago
ulferts	4f7dd55ae7	bump airbrake	5 years ago
ulferts	b7e7f6b947	bump addressable	5 years ago
ulferts	729c2b6a96	bump rubytree	5 years ago
ulferts	c1b42194fd	bump awesome_nested_set	5 years ago
ulferts	2fed1e9ca3	bump acts_as_tree	5 years ago
ulferts	953b21806f	bump pry-byebug	5 years ago
ulferts	3bb03e066f	bump dalli	5 years ago
ulferts	b95a3e6d24	bump bourbon	5 years ago