Public
- Public
- Network
- Groups
- Featured
- Popular
- People

import { Sha256 } from '@aws-crypto/sha256-browser'; /** * Returns a SHA256 hash hex string of the 'data' param * @param {string} data * @returns {Promise<string>} * @internal * @ignore */ export async function sha256Hash(data) { const hash = new Sha256(); hash.update(data); const hashedData = await hash.digest(); return window.Buffer.from(hashedData).toString('hex'); }

Download link

import { Sha256 } from '@aws-crypto/sha256-browser'; /** * Returns a SHA256 hash hex string of the 'data' param * @param {string} data * @returns {Promise<string>} * @internal * @ignore */ export async function sha256Hash(data) { const hash = new Sha256(); hash.update(data); const hashedData = await hash.digest(); return window.Buffer.from(hashedData).toString('hex'); }
https://cdn.masto.host/twippedsocial/media_attachments/files/113/278/729/194/036/098/original/834563d21b985e07.png

Notices where this attachment appears

Embed this notice
Jocelynephiliac :reclaimer: (twipped@twipped.social)'s status on Monday, 14-Oct-2024 20:31:52 JST Jocelynephiliac :reclaimer:

This is what happens when you let your devs use copilot.
This is supposed to be client-side browser code, but this code does not work in a browser.
It passed in the test suite, because Jest copies the entire NodeJS global namespace into `window`, but `window.Buffer` is not actually a thing.
This change also added over 150k of extra code to the bundle, just to hash an object in order to assert a value change.
#Code #Fail #Copilot #aiRageIntensifies

In conversation about a month ago from twipped.social permalink