Hello. Latest build (commit 0adaa7c) brings it back after some years
It comes right after the discourse-presence plugin is integrated and enabled by default. Should I remove it from the list? I have renamed it so it looks like
I thought it failed because I changed the container configuration without running ./launcher rebuild app but then I ran it and:
I, [2017-09-07T12:41:47.226058 #14] INFO -- : > cd /var/www/discourse/plugins && git clone https://github.com/discourse/discourse-presence.git
fatal: destination path 'discourse-presence' already exists and is not an empty directory.
I, [2017-09-07T12:41:47.232919 #14] INFO -- :
FAILED
--------------------
Pups::ExecError: cd /var/www/discourse/plugins && git clone https://github.com/discourse/discourse-presence.git failed with return #<Process::Status: pid 159 exit 128>
Location of failure: /pups/lib/pups/exec_command.rb:108:in `spawn'
exec failed with the params {"cd"=>"$home/plugins", "cmd"=>["mkdir -p plugins", "git clone https://github.com/discourse/docker_manager.git", "git clone https://github.com/discourse/discourse-spoiler-alert.git", "git clone https://github.com/discourse/discourse-voting.git", "git clone https://github.com/discourse/discourse-solved.git", "git clone https://github.com/discourse/discourse-assign.git", "git clone https://github.com/discourse/discourse-presence.git", "git clone https://github.com/lidel/discourse-openstreetmap.git"]}
6cdaf8b12114762b0bc1f96f3f014e0ad5e356c24b49370812bd4513a147ce0f
** FAILED TO BOOTSTRAP ** please scroll up and look for earlier error messages, there may be more than one
On the server-side nothing’s wrong. The /logs/report_js_error contains only OK which gives a syntax error. See screenshot below.
Commits · discourse/discourse · GitHub still mentions the build failing… I’m going to wait until test-passed includes your fix to revert to that branch.
OK, thanks for your interest @david, but I guess it’s a different topic. I resolved the blank page issue by switching to the master branch that includes your reverts. Now, on the master branch, there’s still this Markdown issue that doesn’t seem to affect much of the site use.
Today I switched back to tests-passed from master and all is working again. I suspect the patch @david was mentioning in response #8 was causing the blank page. All izz well now.