fix(Schedulers): Throwing a falsy error in a scheduled function no longer results in strange error objects.

spec/schedulers/QueueScheduler-spec.ts

@@ -63,7 +63,7 @@ describe('Scheduler.queue', () => {
     const actions: Subscription[] = [];
     let action2Exec = false;
     let action3Exec = false;
-    let errorValue = undefined;
+    let errorValue: any = undefined;
     try {
       queue.schedule(() => {
         actions.push(

spec/util/UnsubscriptionError-spec.ts

@@ -16,10 +16,13 @@ describe('UnsubscriptionError', () => {
     try {
       subscription.unsubscribe();
     } catch (err) {
-      expect(err instanceof UnsubscriptionError).to.equal(true);
-      expect(err.errors).to.deep.equal([err1, err2]);
-      expect(err.name).to.equal('UnsubscriptionError');
-      expect(err.stack).to.be.a('string');
+      if (err instanceof UnsubscriptionError) {
+        expect(err.errors).to.deep.equal([err1, err2]);
+        expect(err.name).to.equal('UnsubscriptionError');
+        expect(err.stack).to.be.a('string');
+      } else {
+        throw new TypeError('Invalid error type');
+      }
     }
   });
 });

src/internal/scheduler/AsyncAction.ts

@@ -116,7 +116,10 @@ export class AsyncAction<T> extends Action<T> {
       this.work(state);
     } catch (e) {
       errored = true;
-      errorValue = (!!e && e) || new Error(e);
+      // HACK: Since code elsewhere is relying on the "truthiness" of the
+      // return here, we can't have it return "" or 0 or false.
+      // TODO: Clean this up when we refactor schedulers mid-version-8 or so.
+      errorValue = e ? e : new Error('Falsy action error');
     }
     if (errored) {
       this.unsubscribe();