How to quickly delete multiple jobs in kubernetes

katydidknot — Thu, 21 Jan 2021 19:11:04 +0000

Kube jobs running wild?

To delete successful jobs:

kubectl delete jobs --field-selector status.successful=1

To delete failed or long running jobs

kubectl delete jobs --field-selector status.successful=0

Get rid of them all!

Cancelling a stripe subscription on 'period end'

katydidknot — Sun, 17 Jan 2021 19:11:01 +0000

Stripe's documentation on cancelling a subscription at the end of a period isn't entirely up to date.

https://stripe.com/docs/billing/subscriptions/cancel

For cancelling at end of period, the docs say to do the following:

Stripe::Subscription.update(
  'sub_',
  {
    cancel_at_period_end: true,
  }
)

Easy enough, right?

WRONG.

When actually doing this we were getting the following error:

{
  "error": {
    "message": "The subscription is managed by the subscription schedule `sub_sched_`, and updating any cancelation behavior directly is not allowed. Please update the schedule instead.",
    "type": "invalid_request_error"
  }
}

After contacting stripe support, if you wish to cancel at the period end you need to do the following:

Update phases on subscription schedule object to pass only current phase.
Set end_behavior to 'cancel'

Stripe::SubscriptionSchedule.update(
  'sub_sched_',
  {end_behavior: 'cancel'},
)

Links:

https://stripe.com/docs/billing/subscriptions/subscription-schedules#updating

https://stripe.com/docs/api/subscription_schedules/update?lang=ruby

Echo Cancellation with Web Audio Api and Chromium

katydidknot — Tue, 17 Nov 2020 19:49:10 +0000

Background

Recently, I ran into a doozy of a bug in Chromium. My pair and I were working on an application that was taking advantage of audio processing using the WebAudio Api. Part of the processing in question was the ability to spatially interact with noise based on the user's position in the application. We were building this application on top of a conferencing api stream that already had it's own processing built in. This added more complexity to the problem, as we had to yank the media stream coming through that api to apply the spatial processing, and then feed it back to the user all tidied up and ready to blow their minds.

The Problem

However, then came Chromium… The spatial awesomeness was working, and pretty neat, but the minute you took your headphones off- BAM, a sound only fit to be heard at experimental electronic basement shows came wallowing through our speakers. An extensive google search revealed an open bug lurking in the issues log.

It seems Chromium does not apply echo cancellation to any remote streams- including WebAudio Api streams. To save others the trouble in working with the WebAudio Api in Chromium, we wanted to collect and share our findings from the community, and ultimately what worked for us.

Step 1:

Create your audio processing and apply it to your stream

const audioContext = new AudioContext()
const destinationNode = audioContext.createMediaStreamDestination();
audioContext.createMediaStreamSource(new MediaStream([audioStream.getAudioTracks()[0]]))
        .connect(createDistortion(audioContext))
        .connect(destinationNode);

Note: audioStream is our current media stream that we want to apply audio processing to.

Be careful, as there are two destination nodes as part of Web Audio API. One is the audioContext.destination, and the other is audioContext.createMediaStreamDestination(); ---> use this one.

Step 2:

Create your audio loopback stream

const loopbackStream = await createLoopbackConnection(destinationNode);

The function createLoopbackConnection is setting up a local webRTC loopback connection. Chromium then picks this up and applies echo cancellation. Voila! Here's a helpful gist in the Chromium issue log we found to see how to do this.

Note: One important hiccup that tripped us up in the creation of a local loopback connection, was trying to use addStream which is deprecated- use addTrack to circumvent this.

Step 3:

Feed the loopback stream into your audio element.

In our case we had an existing audio element that was backed by the conferencing api we were using. We did not have to create one, but rather feed the processed stream into the existing audio element.

const audioElement = document.getElementById(`audio-element`);
audioElement.srcObject = loopbackStream;

Step 4:

Rejoice in the fact that your ears no longer hear feedback!
You no longer need to use headphones after applying audio processing in Chromium!

Lessons learned:

Debugging audio feedback with a pair is really hard.
Debugging audio feedback without a pair is even harder.
Always check issues logs.
Take care of your ears!

DEV Community: katydidknot