Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Tests fail when SES is used

See original GitHub issue

If https://github.com/ljharb/object.assign/blob/main/test/ses-compat.js#L15 is changed to require('.'), so it runs the tests:

Boolean.prototype.valueOf.call(require('.')(true)) fails (altho Boolean.prototype.valueOf.call(Object.assign(true)) still succeeds).

cc @kumavis

We need to figure out if this is a bug in the entry point, or a bug in SES.

Issue Analytics

State:
Created 3 years ago
Comments:29 (17 by maintainers)

Top GitHub Comments

1reaction

erightscommented, Sep 22, 2020

Scratch that. The getter itself should work independent of this binding. Only the setter cares about the this binding.

0reactions

ljharbcommented, Sep 22, 2020

There are no spec-provided setters I’m aware of besides Object.prototype.__proto__, and I have no use case for using that intrinsic (i have a setPrototypeOf helper for that).

Top Results From Across the Web

Rspec tests failing when using amazon ses mail sending

The problem is that you're setting config.action_mailer.perform_deliveries = false , so no deliveries are being made and therefore ...

Amazon SES SMTP issues - Amazon Simple Email Service

Problems connecting to the Amazon SES SMTP endpoint are most commonly related to the following issues: Incorrect credentials – The credentials that you...

Tracking opens, clicks, failures and complaints for AWS SES

How to track Amazon SES mail events at scale using event publishing and configuration sets.

Email test failed. -mail address is not verified. - WordPress.org

You need to verify both sender and recipient email addresses from AWS SES Dashboard. Looks like you are using Sandbox mode in Amazon...

Integration tests - LocalStack Docs

Make sure your tests always clean up AWS resources, even if your test fails! Prefer existing factory fixtures (like sqs_create_queue ). Introduce try/finally ......