User card overflows outside of window

February 15, 2015, 5:17 pm

I've tracked down the change that causes the issue, not sure why it was changed here:

github.com

tweak positioning when it has no room to right

by SamSaffron on 05:25AM - 06 Nov 14

changed 1 files with 2 additions and 2 deletions.

I tested it on my install, reverting the above change, using the overage variable like it was before, causes the user card to display properly.

My question for @sam is why change it?

PR for fix:

github.com

FIX: Use overage to keep usercard from going off browser

by chapel on 01:16AM - 16 Feb 15

1 commits changed 1 files with 1 additions and 1 deletions.

Posts: 12

Participants: 4

Read full topic

↧

Ruby 2.2: first look

February 15, 2015, 5:49 pm

≫ Next: Replace Google OpenID 2.0 with OpenID Connect

≪ Previous: User card overflows outside of window

@elberet wrote:

So in a bout of update frenzy I've accidently upgraded my system Ruby to 2.2 and decided to use this as an excuse to test Discourse with ruby 2.2.0p0 r49005.

Right off the bat, I have to make two changes to even get Discourse running:

~~change Gemfile.lock to use version 1.8.2 of the json gem. Version 1.8.1 was moved into Ruby's stdlib, the native extension for the 1.8.1 gem won't compile against the Ruby 2.2 C API.~~ (Actually, this change made it into master only hours ago. )

set UNICORN_ENABLE_OOBGC=0 in the environment to disable out-of-band gargabe collection in unicorn in production. According to this, Ruby 2.2's incremental GC makes oob GC largely unnecessary.

Apart from this, things seem to be stable at first glance, but I'm definitely going to have a close look at my error logs and performance counters over the next few days.

All in the name of not admitting a mistake and just downgrading back to Ruby 2.1...

Posts: 1

Participants: 1

Read full topic

↧

Replace Google OpenID 2.0 with OpenID Connect

February 15, 2015, 9:35 pm

≫ Next: Does Discourse require 2GB to work "Lag Free"?

≪ Previous: Ruby 2.2: first look

@nahtnam wrote:

It looks like OpenID 2.0 will be replaced by OpenID Connect on April 20 for Google authentication.

More info here: https://support.google.com/accounts/answer/6135882

Posts: 6

Participants: 5

Read full topic

↧

Does Discourse require 2GB to work "Lag Free"?

February 15, 2015, 9:41 pm

≫ Next: Returning uncatchable promises

≪ Previous: Replace Google OpenID 2.0 with OpenID Connect

@nahtnam wrote:

In my opinion, we should be working on improving the performance of Discourse rather than working on adding more features. I find it ridiculous that for Discourse to work lag free we have to use a 2gb server, whereas using something like SMF barely requires 512mb. Just my two cents.

Posts: 6

Participants: 5

Read full topic

↧

Returning uncatchable promises

February 15, 2015, 10:07 pm

≫ Next: Moderators / Administrators can't change realname or other custom fields?

≪ Previous: Does Discourse require 2GB to work "Lag Free"?

@sam wrote:

Internally we follow a pattern similar to this quite extensively in our models:
 toggleBookmark() {
    const self = this, firstPost = this.get("postStream.posts")[0];
    var path = self.get('bookmarked') ? '/remove_bookmarks' : '/bookmark';

    this.toggleProperty('bookmarked');
    if (this.get("postStream.firstPostPresent")) { firstPost.toggleProperty("bookmarked"); }

    return Discourse.ajax('/t/' + this.get('id') + path, {
      type: 'PUT',
    }).catch(function(error) {
      self.toggleProperty('bookmarked');
      if (self.get("postStream.firstPostPresent")) { firstPost.toggleProperty('bookmarked'); }

      let showGenericError = true;
      if (error && error.responseText) {
        try {
          bootbox.alert($.parseJSON(error.responseText).errors);
          showGenericError = false;
        } catch(e){}
      }

      if(showGenericError){
        bootbox.alert(I18n.t('generic_error'));
      }
    });
  },
This raises a few red flags on my side which I would like to have a plan to address

Uncatchable promises

Consumers calling
post.toggleBookmark().catch(function(){
   // rollback UI
});
Are in for a rude surprise when they discover the catch code never fires.

UI is being triggered from models

The model has a dependecy on bootbox, which seems odd, view logic is creeping in to models.

How should we address these issues?

cc @eviltrout @zogstrip

On the "uncatchable promise thing"

Should we be throwing from inside the "catch" so stuff leaks out?

It just feels like we are setting us up with a models that do not allow the UI to respond to failure cleanly at the point of failure.

Posts: 5

Participants: 4

Read full topic

↧

Moderators / Administrators can't change realname or other custom fields?

February 16, 2015, 2:02 am

≫ Next: Back is not always taking me to the correct page

≪ Previous: Returning uncatchable promises

@tonninseteli wrote:

While messing around with each other's titles and realnames, I noticed that I cannot change all of my own data with admin user. Then I noticed the same applies when changing info for other users too.

While I myself have no problem with, say, oneliners and offensive stuff in these fields that my users use them for, I'd imagine some admins might want to give them a little touch up.

I am also uncertain if it's possible to forbid/allow users to change these fields themselves.

Any thoughts on this?

Posts: 4

Participants: 2

Read full topic

↧

Back is not always taking me to the correct page

February 16, 2015, 4:24 am

≫ Next: Upgrading cannot allocate memory

≪ Previous: Moderators / Administrators can't change realname or other custom fields?

@cpradio wrote:

Okay, I don't think this is just me any more. I've been having this odd experience on mobile and on a desktop for a few days now here at Meta.

Whenever I use the back button on my mobile (Android using Chrome) or if I use the u shortcut on a desktop, I'm occasionally taken to the wrong page (think 2 pages in my history instead of 1 page back in my history).

I don't have easily reproducible steps other than, use it for a while and see what happens, but here is my typical workflow that causes it (after you use it for a while)

Navigate to Latest

Click on a topic

Read topic, press u

You should be back to latest

Click on the same topic you just read

Press u

You should be back to latest (but you might not be)

Click on a different topic

Perform steps 3-8 again until issue occurs.

Posts: 8

Participants: 6

Read full topic

↧

Upgrading cannot allocate memory

February 16, 2015, 5:21 am

≫ Next: Upload to S3 error

≪ Previous: Back is not always taking me to the correct page

@downey wrote:

Continuing the discussion from Memory is running out and Discourse stops working:
sam:
So I am very cautiously optimistic here. I applied the fix to our code:
github.com
FIX: upgrade event machine
1.0.5 and 1.0.6 contain confirmed memory leaks
by SamSaffron on 08:06PM - 15 Feb 15

changed 1 files with 1 additions and 1 deletions.
We are now deploying this to all our customers, then I will be watching memory for the next 24 hours.

If all looks good we will push a new beta tomorrow. If not, well, I will continue hunting this down.

EDIT a few hours later, this is looking like the real deal across our entire infrastructure.
I just ran our mostly-daily update this morning, and received the following error above the black status window:

Sorry, there was an error upgrading Discourse. Please check the logs below.
Gem::Ext::BuildError: ERROR: Failed to build gem native extension.

/usr/local/bin/ruby -r ./siteconf20150216-7453-5i1l39.rb extconf.rb
Cannot allocate memory - /usr/local/bin/ruby -r ./siteconf20150216-7453-5i1l39.rb extconf.rb  2>&1

Gem files will remain installed in /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/eventmachine-1.0.7 for inspection.
Results logged to /var/www/discourse/vendor/bundle/ruby/2.0.0/extensions/x86_64-linux/2.0.0-static/eventmachine-1.0.7/gem_make.out
An error occurred while installing eventmachine (1.0.7), and Bundler cannot
continue.
Make sure that `gem install eventmachine -v '1.0.7'` succeeds before bundling.
Should I try to restart Discourse to free up memory or is there a bigger issue here?
             total       used       free     shared    buffers     cached
Mem:          2.0G       1.8G       184M        54M        15M       168M
-/+ buffers/cache:       1.6G       369M
Swap:         1.0G       925M        98M

Posts: 4

Participants: 2

Read full topic

↧

Upload to S3 error

February 16, 2015, 10:55 am

≫ Next: Edit window not docked in my browser

≪ Previous: Upgrading cannot allocate memory

@NomNuggetNom wrote:

We have our instance configured to upload backups to S3, but it's running into errors when trying to do that. Here is the important part of the log (ask me for the whole thing):

[2015-02-16 18:24:58 +0000] Making sure archive does not already exist...
[2015-02-16 18:24:58 +0000] Creating empty archive...
[2015-02-16 18:24:58 +0000] Archiving metadata...
[2015-02-16 18:24:58 +0000] Archiving data dump...
[2015-02-16 18:25:41 +0000] Archiving uploads...
[2015-02-16 18:28:03 +0000] Gzipping archive...
[2015-02-16 18:44:41 +0000] Executing the after_create_hook for the backup
[2015-02-16 18:44:47 +0000] EXCEPTION: Broken pipe (Errno::EPIPE)
[2015-02-16 18:44:47 +0000] /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/excon-0.42.1/lib/excon/socket.rb:109:in `write_nonblock'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/excon-0.42.1/lib/excon/socket.rb:109:in `write'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/excon-0.42.1/lib/excon/connection.rb:151:in `request_call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/excon-0.42.1/lib/excon/middlewares/mock.rb:47:in `request_call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/excon-0.42.1/lib/excon/middlewares/instrumentor.rb:22:in `request_call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/excon-0.42.1/lib/excon/middlewares/base.rb:15:in `request_call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/excon-0.42.1/lib/excon/middlewares/base.rb:15:in `request_call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/excon-0.42.1/lib/excon/middlewares/base.rb:15:in `request_call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/excon-0.42.1/lib/excon/connection.rb:232:in `request'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/excon-0.42.1/lib/excon/middlewares/idempotent.rb:26:in `error_call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/excon-0.42.1/lib/excon/middlewares/base.rb:10:in `error_call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/excon-0.42.1/lib/excon/middlewares/base.rb:10:in `error_call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/excon-0.42.1/lib/excon/connection.rb:255:in `rescue in request'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/excon-0.42.1/lib/excon/connection.rb:203:in `request'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/excon-0.42.1/lib/excon/middlewares/idempotent.rb:26:in `error_call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/excon-0.42.1/lib/excon/middlewares/base.rb:10:in `error_call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/excon-0.42.1/lib/excon/middlewares/base.rb:10:in `error_call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/excon-0.42.1/lib/excon/connection.rb:255:in `rescue in request'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/excon-0.42.1/lib/excon/connection.rb:203:in `request'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/excon-0.42.1/lib/excon/middlewares/idempotent.rb:26:in `error_call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/excon-0.42.1/lib/excon/middlewares/base.rb:10:in `error_call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/excon-0.42.1/lib/excon/middlewares/base.rb:10:in `error_call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/excon-0.42.1/lib/excon/connection.rb:255:in `rescue in request'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/excon-0.42.1/lib/excon/connection.rb:203:in `request'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/fog-core-1.27.2/lib/fog/core/connection.rb:63:in `request'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/fog-xml-0.1.1/lib/fog/xml/connection.rb:9:in `request'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/fog-1.26.0/lib/fog/aws/storage.rb:542:in `_request'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/fog-1.26.0/lib/fog/aws/storage.rb:537:in `request'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/fog-1.26.0/lib/fog/aws/requests/storage/put_object.rb:31:in `put_object'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/fog-1.26.0/lib/fog/aws/models/storage/file.rb:208:in `save'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/fog-core-1.27.2/lib/fog/core/collection.rb:50:in `create'
/var/www/discourse/lib/s3_helper.rb:26:in `upload'
/var/www/discourse/app/models/backup.rb:57:in `block in upload_to_s3'
/var/www/discourse/app/models/backup.rb:56:in `open'
/var/www/discourse/app/models/backup.rb:56:in `upload_to_s3'
/var/www/discourse/app/models/backup.rb:36:in `after_create_hook'
/var/www/discourse/lib/backup_restore/backuper.rb:267:in `after_create_hook'
/var/www/discourse/lib/backup_restore/backuper.rb:48:in `run'
/var/www/discourse/lib/backup_restore/backup_restore.rb:161:in `block in start!'
/var/www/discourse/lib/backup_restore/backup_restore.rb:158:in `fork'
/var/www/discourse/lib/backup_restore/backup_restore.rb:158:in `start!'
/var/www/discourse/lib/backup_restore/backup_restore.rb:13:in `backup!'
/var/www/discourse/app/controllers/admin/backups_controller.rb:30:in `create'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.8/lib/action_controller/metal/implicit_render.rb:4:in `send_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.8/lib/abstract_controller/base.rb:189:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.8/lib/action_controller/metal/rendering.rb:10:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.8/lib/abstract_controller/callbacks.rb:20:in `block in process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.8/lib/active_support/callbacks.rb:113:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.8/lib/active_support/callbacks.rb:113:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.8/lib/active_support/callbacks.rb:166:in `block in halting'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.8/lib/active_support/callbacks.rb:166:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.8/lib/active_support/callbacks.rb:166:in `block in halting'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.8/lib/active_support/callbacks.rb:166:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.8/lib/active_support/callbacks.rb:166:in `block in halting'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.8/lib/active_support/callbacks.rb:149:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.8/lib/active_support/callbacks.rb:149:in `block in halting_and_conditional'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.8/lib/active_support/callbacks.rb:166:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.8/lib/active_support/callbacks.rb:166:in `block in halting'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.8/lib/active_support/callbacks.rb:166:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.8/lib/active_support/callbacks.rb:166:in `block in halting'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.8/lib/active_support/callbacks.rb:166:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.8/lib/active_support/callbacks.rb:166:in `block in halting'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.8/lib/active_support/callbacks.rb:166:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.8/lib/active_support/callbacks.rb:166:in `block in halting'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.8/lib/active_support/callbacks.rb:166:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.8/lib/active_support/callbacks.rb:166:in `block in halting'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.8/lib/active_support/callbacks.rb:166:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.8/lib/active_support/callbacks.rb:166:in `block in halting'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.8/lib/active_support/callbacks.rb:166:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.8/lib/active_support/callbacks.rb:166:in `block in halting'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.8/lib/active_support/callbacks.rb:166:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.8/lib/active_support/callbacks.rb:166:in `block in halting'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.8/lib/active_support/callbacks.rb:229:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.8/lib/active_support/callbacks.rb:229:in `block in halting'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.8/lib/active_support/callbacks.rb:166:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.8/lib/active_support/callbacks.rb:166:in `block in halting'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.8/lib/active_support/callbacks.rb:86:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.8/lib/active_support/callbacks.rb:86:in `run_callbacks'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.8/lib/abstract_controller/callbacks.rb:19:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.8/lib/action_controller/metal/rescue.rb:29:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.8/lib/action_controller/metal/instrumentation.rb:31:in `block in process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.8/lib/active_support/notifications.rb:159:in `block in instrument'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.8/lib/active_support/notifications/instrumenter.rb:20:in `instrument'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.8/lib/active_support/notifications.rb:159:in `instrument'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.8/lib/action_controller/metal/instrumentation.rb:30:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.8/lib/action_controller/metal/params_wrapper.rb:250:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.8/lib/active_record/railties/controller_runtime.rb:18:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.8/lib/abstract_controller/base.rb:136:in `process'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionview-4.1.8/lib/action_view/rendering.rb:30:in `process'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-mini-profiler-0.9.2/lib/mini_profiler/profiling_methods.rb:79:in `block in profile_method'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.8/lib/action_controller/metal.rb:196:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.8/lib/action_controller/metal/rack_delegation.rb:13:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.8/lib/action_controller/metal.rb:232:in `block in action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.8/lib/action_dispatch/routing/route_set.rb:82:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.8/lib/action_dispatch/routing/route_set.rb:82:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.8/lib/action_dispatch/routing/route_set.rb:50:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.8/lib/action_dispatch/routing/mapper.rb:45:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.8/lib/action_dispatch/journey/router.rb:73:in `block in call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.8/lib/action_dispatch/journey/router.rb:59:in `each'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.8/lib/action_dispatch/journey/router.rb:59:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.8/lib/action_dispatch/routing/route_set.rb:678:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-protection-1.5.3/lib/rack/protection/frame_options.rb:31:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.2/lib/omniauth/strategy.rb:186:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.2/lib/omniauth/strategy.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.2/lib/omniauth/strategy.rb:186:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.2/lib/omniauth/strategy.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.2/lib/omniauth/strategy.rb:186:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.2/lib/omniauth/strategy.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.2/lib/omniauth/strategy.rb:186:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.2/lib/omniauth/strategy.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.2/lib/omniauth/strategy.rb:186:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.2/lib/omniauth/strategy.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.2/lib/omniauth/strategy.rb:186:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.2/lib/omniauth/strategy.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.2/lib/omniauth/builder.rb:59:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/conditionalget.rb:35:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/head.rb:11:in `call'
/var/www/discourse/lib/middleware/anonymous_cache.rb:123:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.8/lib/action_dispatch/middleware/params_parser.rb:27:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.8/lib/action_dispatch/middleware/flash.rb:254:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/message_bus-1.0.6/lib/message_bus/rack/middleware.rb:55:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/session/abstract/id.rb:225:in `context'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/session/abstract/id.rb:220:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.8/lib/action_dispatch/middleware/cookies.rb:560:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.8/lib/active_record/query_cache.rb:36:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.8/lib/active_record/connection_adapters/abstract/connection_pool.rb:621:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.8/lib/action_dispatch/middleware/callbacks.rb:29:in `block in call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.8/lib/active_support/callbacks.rb:82:in `run_callbacks'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.8/lib/action_dispatch/middleware/callbacks.rb:27:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.8/lib/action_dispatch/middleware/remote_ip.rb:76:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.8/lib/action_dispatch/middleware/debug_exceptions.rb:17:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.8/lib/action_dispatch/middleware/show_exceptions.rb:30:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/logster-0.1.6/lib/logster/middleware/reporter.rb:23:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.1.8/lib/rails/rack/logger.rb:38:in `call_app'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.1.8/lib/rails/rack/logger.rb:22:in `call'
/var/www/discourse/config/initializers/quiet_logger.rb:10:in `call_with_quiet_assets'
/var/www/discourse/config/initializers/silence_logger.rb:26:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.8/lib/action_dispatch/middleware/request_id.rb:21:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/methodoverride.rb:21:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/runtime.rb:17:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/sendfile.rb:112:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-mini-profiler-0.9.2/lib/mini_profiler/profiler.rb:193:in `call'
/var/www/discourse/lib/middleware/request_tracker.rb:60:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.1.8/lib/rails/engine.rb:514:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.1.8/lib/rails/application.rb:144:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.1.8/lib/rails/railtie.rb:194:in `public_send'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.1.8/lib/rails/railtie.rb:194:in `method_missing'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/builder.rb:138:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/urlmap.rb:65:in `block in call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/urlmap.rb:50:in `each'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/urlmap.rb:50:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/unicorn-4.8.3/lib/unicorn/http_server.rb:576:in `process_client'
/var/www/discourse/lib/middleware/unicorn_oobgc.rb:95:in `process_client'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/unicorn-4.8.3/lib/unicorn/http_server.rb:670:in `worker_loop'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/unicorn-4.8.3/lib/unicorn/http_server.rb:525:in `spawn_missing_workers'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/unicorn-4.8.3/lib/unicorn/http_server.rb:140:in `start'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/unicorn-4.8.3/bin/unicorn:126:in `<top (required)>'
/var/www/discourse/vendor/bundle/ruby/2.0.0/bin/unicorn:23:in `load'
/var/www/discourse/vendor/bundle/ruby/2.0.0/bin/unicorn:23:in `<main>'
[2015-02-16 18:44:47 +0000] Notifying 'NomNuggetNom' of the end of the backup...

We've triple checked our S3 credentials and everything seems right. Any ideas what's going on?

Posts: 1

Participants: 1

Read full topic

↧

Edit window not docked in my browser

February 16, 2015, 12:43 pm

≫ Next: 1.2 beta users – please upgrade to beta 9 immediately due to critical memory leak

≪ Previous: Upload to S3 error

@tobiaseigen wrote:

Weird new behavior exhibited on my forum - I have not been able to replicate it! Check out the animated gif below. Basically what happened is I started a reply, then when I scrollled down and back up again the edit window disappeared. It was not "docked" in my browser as it usually is. Not sure I'm using the right words to describe this problem, though found it disconcerting enough that I wanted to report it!

Posts: 3

Participants: 2

Read full topic

↧

1.2 beta users – please upgrade to beta 9 immediately due to critical memory leak

February 16, 2015, 1:16 pm

≫ Next: SSO Plugin for mobile

≪ Previous: Edit window not docked in my browser

@codinghorror wrote:

Starting on about Feb 2nd 2015, the time of transition between 1.2 beta 6 and beta 7, we've been struggling with a severe memory leak in Discourse.

It took us a while to nail it down -- almost two weeks, sorry about that -- but we finally did. It was EventMachine 1.0.5 and 1.0.6:

Observed with 1.0.6: as soon as the ruby process is started it'll leak 16KB chunks of memory pretty much every second. This happens without serving any Requests (load balancer in front was disabled).

This is quite nasty; 16KB per second is almost a megabyte per minute, a gigabyte per day. The good news is that we've improved our internal monitoring significantly so in the future we'll be able to tell sooner when someone introduces a serious memory leak.

As of beta 9, we have upgraded to a newer version of EventMachine which fixed the memory leak bug.

This means anyone who was on 1.2 beta 6, 7 or 8 should upgrade to beta 9 immediately. If you do not, expect to run into out of memory errors regularly until you do.

Posts: 4

Participants: 3

Read full topic

↧

SSO Plugin for mobile

February 16, 2015, 1:16 pm

≫ Next: How can I block an IP address? are there wildcards?

≪ Previous: 1.2 beta users – please upgrade to beta 9 immediately due to critical memory leak

@Craig_Kahle wrote:

I have an interesting case where I need to handle SSO from a mobile app. I have SSO working fine (great docs, thanks) on the web side, but need to detect if the incoming SSO request if from the app or the web.

Im writing a plugin to add a new endpoint to handle mobile SSO that simply registers and returns the nonce, instead of redirecting you to an external URL. The code looks something like this:
class MobileController < ApplicationController
	require_dependency 'single_sign_on'

	respond_to :json

	def returnNonce
		@url = DiscourseSingleSignOn.generate_url()
		respond_with @url
	end
end
Here is plugin.rb
require_dependency 'single_sign_on'

    after_initialize do
    	load File.expand_path("../controllers/mobile_controller.rb", __FILE__)

    	Discourse::Application.routes.prepend do
    		get 'session/sso/mobile' => 'mobile#returnNonce'
    	end
    end
currently it sends back all of the main landing page markup, and I'm looking to just return the nonce, and continue auth with 3rd party SSO host site, then return to Discourse / mobile app. I can add any additional details if necessary. Thanks a bunch.

-C

Posts: 1

Participants: 1

Read full topic

↧

How can I block an IP address? are there wildcards?

February 16, 2015, 1:21 pm

≫ Next: Share by email does not work

≪ Previous: SSO Plugin for mobile

@rodrigofarcas wrote:

I can't see an Admin option to block IP or a range of IPs, is there one?

Thanks!

Posts: 4

Participants: 3

Read full topic

↧

Share by email does not work

February 16, 2015, 3:18 pm

≫ Next: Closing / Opening poll should store revision in edit history of topic

≪ Previous: How can I block an IP address? are there wildcards?

@parenthere wrote:

I click the button share by email:
It open new tab and url looks like
mailto:?to=&subject=%5BHeartEmma%5D%20Convertible%20car%20seats%20-%20Britax%20Marathon%20vs.%20Chicco%20NextFit&body=http%3A%2F%2Fwww.heartemma.com%2Ft%2Fconvertible-car-seats-britax-marathon-vs-chicco-nextfit%2F107%3Fu%3Demmafu`
but nothing happen after that.

Pasted image1177x497 76.5 KB

Posts: 10

Participants: 5

Read full topic

↧

Closing / Opening poll should store revision in edit history of topic

February 16, 2015, 7:07 pm

≫ Next: Why there is huge difference in Pageviews tracking number on discourse admin dahboard and on google analytics

≪ Previous: Share by email does not work

@DeanMarkTaylor wrote:

Recently noticed that a poll topic was closed my Discourse instance that should have been open.

But there was no way to know why or who closed it.

Upon selecting "Open Poll" I noted the title changed but no revision ("edit") was added to the topic.

I would expect that every time the title changes, even if that change is to open or close a poll (via the poll buttons) that a revision is stored in the edit history so who made the change and when can be tracked.

Posts: 1

Participants: 1

Read full topic

↧

Why there is huge difference in Pageviews tracking number on discourse admin dahboard and on google analytics

February 16, 2015, 9:36 pm

≫ Next: Changing emoji size

≪ Previous: Closing / Opening poll should store revision in edit history of topic

@lovechopra1 wrote:

Hi,
I found there is huge difference in google analytics pageviews number and pageviews number on admin panel of discourse.
On discourse's dashboard it is showing 10,000 pageviews however on Google Analytics its only 100. Can anyone please let me know what could be the reason for such a huge difference in tracking of two systems?

I have configured Google Analytics script by putting up ga tracking code @ Admin -> Settings -> Basic Setup

Posts: 16

Participants: 7

Read full topic

↧

Changing emoji size

February 16, 2015, 11:14 pm

≫ Next: Rake assets:precompile fails with new install

≪ Previous: Why there is huge difference in Pageviews tracking number on discourse admin dahboard and on google analytics

@Juffin wrote:

I'd like to change emoji size depending on what emoji is used, for example i've added "ragefaces" to the smiles database and they are displayed very small. is there any way to assign specific sizes to specific emojis?

Posts: 4

Participants: 4

Read full topic

↧

Rake assets:precompile fails with new install

February 16, 2015, 11:58 pm

≫ Next: Why did you move to runit + Unicorn

≪ Previous: Changing emoji size

@ernsheong wrote:

Hi guys, bootstrapping my web container is failing at assets:precompile

I, [2015-02-17T07:47:21.196448 #24415]  INFO -- : Writing /var/www/discourse/public/assets/images/docker-manager-ea64623b074c8ec2b0303bae846e21e6.png
rake aborted!
Errno::EEXIST: File exists - /var/www/discourse/public/uploads
/var/www/discourse/lib/sass/discourse_stylesheets.rb:88:in `compile'
/var/www/discourse/lib/sass/discourse_stylesheets.rb:38:in `block in compile'
/var/www/discourse/lib/sass/discourse_stylesheets.rb:35:in `synchronize'
/var/www/discourse/lib/sass/discourse_stylesheets.rb:35:in `compile'
/var/www/discourse/lib/tasks/assets.rake:81:in `block (3 levels) in <top (required)>'
/var/www/discourse/lib/tasks/assets.rake:80:in `each'
/var/www/discourse/lib/tasks/assets.rake:80:in `block (2 levels) in <top (required)>'
/var/www/discourse/vendor/gems/rails_multisite/lib/rails_multisite/connection_management.rb:86:in `block in each_connection'
/var/www/discourse/vendor/gems/rails_multisite/lib/rails_multisite/connection_management.rb:84:in `each'
/var/www/discourse/vendor/gems/rails_multisite/lib/rails_multisite/connection_management.rb:84:in `each_connection'
/var/www/discourse/lib/tasks/assets.rake:75:in `block in <top (required)>'
/var/www/discourse/lib/tasks/assets.rake:134:in `block in <top (required)>'
Tasks: TOP => assets:precompile:css
(See full trace by running task with --trace)
I, [2015-02-17T07:47:23.768710 #40]  INFO -- : Purging temp files
Bundling assets
Compiling css for default



FAILED
--------------------
RuntimeError: cd /var/www/discourse && su discourse -c 'bundle exec rake assets:precompile' failed with return #<Process::Status: pid 24413 exit 1>
Location of failure: /pups/lib/pups/exec_command.rb:105:in `spawn'
exec failed with the params {"cd"=>"$home", "hook"=>"bundle_exec", "cmd"=>["su discourse -c 'bundle install --deployment --verbose --without test --without development'", "su discourse -c 'bundle exec rake db:migrate'", "su discourse -c 'bundle exec rake assets:precompile'"]}
8b6f21b5118d4519cbbda58656d4039697a8972dc11035126cc2b7cabdce8980
FAILED TO BOOTSTRAP

Any idea what's wrong?

Posts: 2

Participants: 2

Read full topic

↧

Why did you move to runit + Unicorn

February 17, 2015, 1:37 am

≫ Next: Image uploading problems and other errors

≪ Previous: Rake assets:precompile fails with new install

@panduwana wrote:

It used to be bluepill + thin, right?
Why did you move?

Posts: 3

Participants: 3

Read full topic

↧

Image uploading problems and other errors

February 17, 2015, 1:45 am

≫ Next: Customize first welcome pm received

≪ Previous: Why did you move to runit + Unicorn

@vulkanino wrote:

Hello,

I'm running 1.2.0.beta8 but my users are reporting image uploading errors.

In the error logs I've found many Errno::ENOMEM:

Errno::ENOMEM (Cannot allocate memory - convert /var/www/discourse/public/uploads/default/1238/95e4476679bd4aa8.jpg[0] -background transparent -gravity center -thumbnail 240x240^ -extent 240x240 -inte
4 days ago
!!
Errno::ENOMEM (Cannot allocate memory - convert)
4 days ago
!!
Errno::ENOMEM (Cannot allocate memory - convert)
4 days ago
!!
Errno::ENOMEM (Cannot allocate memory - convert)
4 days ago
!!
Errno::ENOMEM (Cannot allocate memory - convert)
4 days ago
!!
Errno::ENOMEM (Cannot allocate memory - convert)
Can't verify CSRF token authenticity
4 days ago
!
Job exception: getaddrinfo: Name or service not known
3 days ago
!
Job exception: Wrapped SocketError: getaddrinfo: Name or service not known
...

What should I do?

Posts: 3

Participants: 2

Read full topic

↧

Uncatchable promises

UI is being triggered from models

Latest Images