Feature: custom runtimes to define function #1602

MarlonJD · 2024-06-03T16:17:01Z

Problem

Changes

~~I changed runtime parameter to string from int. It was only nodejs version. Now it can be:~~

It's default NODEJS_18_X same as old functions, people only need to specify runtime: "NODEJS_16_X" if they want another version, it's giving lint error, so it's easy to inform people if it's changed. If it's empty, it's still creating nodejs version, I also add required to entry parameter when it's go or python runtimes.

Edit: I modified defineFunction to props and callback function can be parameters at the same time:

defineFunction({
  name: "my-regular-function",
})

// a go function
defineFunction((scope) => {
  return new GoFunction(scope, "GoFunction", {
    entry: "app/cmd/api",
  })
})

can be usable like proposal in RFC, go function will be usable out of box, python function will be require docker, so python function cannot be used on CI/CD, it can be deploy with custom pipeline on local.

ie: disabling auto deploy, npm ci && export CI=1 && npx ampx pipeline-deploy --branch BRANCH_NAME --app-id AMPLIFY_APP_ID will do the trick for python.

Checklist

If this PR includes a functional change to the runtime behavior of the code, I have added or updated automated test coverage for this change.
If this PR requires a change to the Project Architecture README, I have included that update in this PR.
If this PR requires a docs update, I have linked to that docs PR above.
If this PR modifies E2E tests, makes changes to resource provisioning, or makes SDK calls, I have run the PR checks with the run-e2e label set.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

changeset-bot · 2024-06-03T16:17:05Z

🦋 Changeset detected

Latest commit: aa6762e

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 2 packages

Name	Type
@aws-amplify/backend-function	Minor
@aws-amplify/backend	Minor

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

edwardfoyle

Hi @MarlonJD thanks for taking the time to open this. We will likely not merge this in its current form. There are a few reasons for this:

We cannot depend on CDK alpha packages in our stable release line. The approach outlined in the RFC you commented on moves the alpha CDK dependency to the customer's project so they are explicitly aware they are using alpha functionality.
Changing the runtime parameter from a number union to a string union is a breaking API change which we cannot do without a major version bump of our libraries
E2E tests that exercise building and calling python and go functions need to be added
The dependency on docker to build the functions needs more consideration of the implications (eg for backend deployments on Amplify hosting and getting started locally)

If you are interested, you can work with @josefaidt to define an interface that is appropriate here and then we can have further discussion on the CDK and docker dependencies.

MarlonJD · 2024-06-03T18:23:31Z

Hi @edwardfoyle.
1-) I understand what you mean, okay, I'll try to change this
2-) What about adding new parameter without modifying runtime?
3-) e2e tests will be added
4-) python docker build is necessary on python build, if it's not possible ı can remove python in pr

josefaidt · 2024-06-03T20:23:01Z

Hey @MarlonJD 👋 thanks for taking the time to file this! To add to @edwardfoyle 's note we'd like to avoid taking a dependency on Docker and the alpha distributions of L2 constructs for Go and Python. While those two runtimes are top of mind, the escape hatch is desirable to offer the capability of using defineFunction with any runtime, with an opt-out of TypeScript-based features like typed environment variables and automatic secrets resolution. Would you be interested in pivoting this PR to match the proposal? Happy to discuss any findings/thoughts you have along the way in the RFC!

MarlonJD · 2024-06-03T20:27:36Z

Hello @josefaidt. I'm trying to change my PR, I'm trying to create defineFunctionWithAnyLanguage in @aws-amplify/backend. Now I'm struggling about creating callback function for Construct/scope and use this function, any help in here? I can create directly with Stack parameter like this:

const lambdaStack = Stack.of(backend.sayHelloHandler.resources.lambda.stack);

const goFunctionStack = new NestedStack(lambdaStack, "say-hello-go-lambda");

export const goFunction = defineFunctionWithAnyLanguage(
  new GoFunction(goFunctionStack, "GoFunction", {
    entry: "./amplify/functions/say-hello-go/",
    runtime: Runtime.PROVIDED_AL2023,
    environment: {
      GOARCH: "amd64",
    },
    bundling: {
      goBuildFlags: ["-tags lambda.norpc"],
    },
  });

But it's will depend to backend variable in backend.ts file. I think it's bad idea, defineFunction is using new Error().stack as callerStack in FunctionFactory. Should I use same new Error().stack as a scope of defineFunctionWithAnyLanguage ?

josefaidt · 2024-06-03T21:09:02Z

Hey @MarlonJD you can define a union on the defineFunction argument to either take the existing props type or a callback like (scope: Construct) => lambda.Function, but this scope will be passed at buildtime from the defineFunction factory.

the props here will need adjustments
https://github.com/aws-amplify/amplify-backend/blob/main/packages/backend-function/src/factory.ts#L41
https://github.com/aws-amplify/amplify-backend/blob/main/packages/backend-function/src/factory.ts#L101

and the scope would be passed to the AmplifyFunction construct
https://github.com/aws-amplify/amplify-backend/blob/main/packages/backend-function/src/factory.ts#L235

We wouldn't want to necessarily change the scope but change how "props" (in this case, the callback) is called with the existing scope to initialize within the Amplify context

MarlonJD · 2024-06-03T22:28:28Z

@josefaidt I changed PR to this:

 const lambda = defineFunction({
  entry: './test-assets/default-lambda/handler.ts',
  runtime: 16,
});

or

const lambda = defineFunction((scope) => {
  return new NodejsFunction(scope, 'customFunction', {
    entry:
      './packages/backend-function/src/test-assets/default-lambda/handler.ts',
  });
});

Golang function will be usable out of box, python function will be require docker, so python function cannot be used on CI/CD, it can be deploy with custom pipeline on local.

ie: disabling auto deploy, npm ci && export CI=1 && npx ampx pipeline-deploy --branch BRANCH_NAME --app-id AMPLIFY_APP_ID will do the trick for python.

What are you thinking about this changes? If it's okay, I'll try to write e2e tests, can you guide me again?

MarlonJD · 2024-06-09T22:18:22Z

I hope you can review this changes @edwardfoyle

edwardfoyle

This is heading in the right direction! Another thing we need to do is turn off generating the typed process.env file when using custom runtimes. We can probably do that by creating a new noop FunctionEnvironmentTypeGenerator if a callback is specified to defineFunction

We should also have an integration and/or e2e test that asserts permissions and environment variables are correctly attached to functions with custom runtimes.

.changeset/flat-chefs-refuse.md

packages/backend-function/src/factory.ts

MarlonJD · 2024-06-13T23:49:16Z

@edwardfoyle I did changes, if it's okay about code, can you help me how and where should write for integration and/or e2e tests?

MarlonJD · 2024-06-24T12:14:37Z

@edwardfoyle Hey there, I hope you can review new changes

edwardfoyle · 2024-07-03T23:59:57Z

Hi @MarlonJD, sorry for the delay here. While this PR is on the right track in terms of implementation, we are concerned about the implications when deploying using the Amplify hosting service. Specifically, CDK requires Docker to build some runtimes and currently Docker is not installed in the hosting build container. Docker also cannot be installed using a custom build script because it requires permissions that the execution environment doesn't have. This means that customers using custom runtimes would not be able to use Hosting deployments. We want to consider this feature holistically rather than only offer partial support across our product offering. As a result, we need to do some internal prerequisite work to ensure custom runtime deployments can work in Amplify hosting deployments.

MarlonJD · 2024-07-04T18:12:38Z

@josefaidt @edwardfoyle Hey there! I have good news about python functions. There is already a local paramater in BundlingOptions. It gives us to bundle without docker. I just found a way to bypass docker build without a modify packages, here is the usage:

import { defineFunction } from "@aws-amplify/backend";
import { DockerImage, Duration } from "aws-cdk-lib";
import { Code, Function, Runtime } from "aws-cdk-lib/aws-lambda";
import { execSync } from "child_process";
import * as path from "path";

const functionDir = path.join(__dirname);

export const sayHelloPythonFunctionHandler = defineFunction(
  (scope) =>
    new Function(scope, "say-hello-python-xderawfe", {
      handler: "index.handler",
      runtime: Runtime.PYTHON_3_9,
      timeout: Duration.seconds(20),
      code: Code.fromAsset(functionDir, {
        bundling: {
          image: DockerImage.fromRegistry("dummy"),
          local: {
            tryBundle(outputDir: string) {
              // if you want to use another python version, make default this ie: pyvenv global 3.12
              // if you dont have python3.9 installed, you can use pyenv to install it from Amplify Hosting build settings
              // from amplify.yaml, you can add this command to install python3.9 in the build settings
              // ie: pyenv install 3.12, pyenv global 3.12

              // Add pyenv command here, if you have more than one python version installed in your functions

              execSync(
                `python3 -m pip install -r ${path.join(functionDir, "requirements.txt")} -t ${path.join(outputDir)} --platform manylinux2014_x86_64 --only-binary=:all:`
              );
              execSync(`rsync -rLv ${functionDir}/* ${path.join(outputDir)}`);
              return true;
            },
          },
        },
      }),
    })
);

I just tried any it's works. I used pure Function, for this reason we can use any language supported from Lambda, f you can bundle it correctly without any package use.
We can add samples to docs how people can use functions.
Now Go and Python functions ready to use, I hope we can move on to the PR and tests.

MarlonJD · 2024-07-22T13:54:31Z

@edwardfoyle Any updates?

MarlonJD · 2024-08-09T23:09:14Z

PTAL

Srakai · 2024-08-11T18:24:23Z

Great work @MarlonJD! Hope this gets merged quickly as currently im trying to achieve same but in a really whacky way

MarlonJD · 2024-08-15T20:15:24Z

Hey @josefaidt, I commented how we can use python functions without docker build, but there is no local parameter in PythonFunction in @aws-cdk/aws-lambda-python-alpha, so I just showed example on Pure Function in aws-cdk-lib/aws-lambda to create python function with local parameter, it's enough to use python function.

What are you thinking about this solution to using python functions like this, should we add local parameter to @aws-cdk/aws-lambda-python-alpha or is it okay to use like this?

mrubelmann · 2024-09-03T03:19:02Z

Any updates on this PR? @edwardfoyle, has @MarlonJD addressed your request? It would be super, super helpful to get this merged!

guikcd · 2024-10-04T15:59:01Z

@josefaidt @edwardfoyle Hey there! I have good news about python functions. There is already a local paramater in BundlingOptions. It gives us to bundle without docker. I just found a way to bypass docker build without a modify packages, here is the usage:

import { defineFunction } from "@aws-amplify/backend";
import { DockerImage, Duration } from "aws-cdk-lib";
import { Code, Function, Runtime } from "aws-cdk-lib/aws-lambda";
import { execSync } from "child_process";
import * as path from "path";

const functionDir = path.join(__dirname);

export const sayHelloPythonFunctionHandler = defineFunction(
  (scope) =>
    new Function(scope, "say-hello-python-xderawfe", {
      handler: "index.handler",
      runtime: Runtime.PYTHON_3_9,
      timeout: Duration.seconds(20),
      code: Code.fromAsset(functionDir, {
        bundling: {
          image: DockerImage.fromRegistry("dummy"),
          local: {
            tryBundle(outputDir: string) {
              // if you want to use another python version, make default this ie: pyvenv global 3.12
              // if you dont have python3.9 installed, you can use pyenv to install it from Amplify Hosting build settings
              // from amplify.yaml, you can add this command to install python3.9 in the build settings
              // ie: pyenv install 3.12, pyenv global 3.12

              // Add pyenv command here, if you have more than one python version installed in your functions

              execSync(
                `python3 -m pip install -r ${path.join(functionDir, "requirements.txt")} -t ${path.join(outputDir)} --platform manylinux2014_x86_64 --only-binary=:all:`
              );
              execSync(`rsync -rLv ${functionDir}/* ${path.join(outputDir)}`);
              return true;
            },
          },
        },
      }),
    })
);

I just tried any it's works. I used pure Function, for this reason we can use any language supported from Lambda, f you can bundle it correctly without any package use. We can add samples to docs how people can use functions. Now Go and Python functions ready to use, I hope we can move on to the PR and tests.

I was able to build my python custom function with my requirements. The only problem I have now is that this seems to be never updated even if I alter this line. Seems that a missing force/cache somewhere. Only workaround I've found now: remove the .amplify directory to force the re-generation of the bundle.

MarlonJD · 2024-10-05T18:19:23Z

@guikcd oh it's a good review, let me check how nodejs changes triggers, maybe we can found fix about it

MarlonJD · 2024-10-14T14:03:08Z

@josefaidt Hey there, I was looking into tracking changes on lambda functions, but I couldn't found this yet, I found FilesChangesTracker class but it's for sandbox file changes, can you help me how can I found how lambda functions triggering bundling again when function have changes?

sobolk

@MarlonJD
I looked at latest diff and it looks good overall.

Couple of areas I left comments:

test project - I ran e2e tests here https://github.com/aws-amplify/amplify-backend/actions/runs/12552245657 - they failed, I left comments with changes to make them passing.
The error messages. For these please keep in mind that they need that docs PR to stabilize, so this might not be final iteration.

.changeset/long-berries-greet.md

packages/integration-tests/src/test-projects/advanced-auth-and-functions/amplify/function.ts

sobolk · 2024-12-30T22:39:41Z

packages/backend-function/src/provided_function_factory.ts

+        throw new AmplifyUserError(
+          'FunctionProviderError',
+          {
+            message: e instanceof Error ? e.message : JSON.stringify(e),
+            // TODO better resolution
+            resolution: 'Ensure that function provider is working.',
+          },
+          e instanceof Error ? e : undefined
+        );


Suggested change

throw new AmplifyUserError(

'FunctionProviderError',

{

message: e instanceof Error ? e.message : JSON.stringify(e),

// TODO better resolution

resolution: 'Ensure that function provider is working.',

},

e instanceof Error ? e : undefined

);

throw new AmplifyUserError(

'CustomFunctionProviderError',

{

message: e instanceof Error ? e.message : JSON.stringify(e),

resolution: "Ensure that callback passed to 'defineFunction' executes without error. See https://docs.amplify.aws/react/build-a-backend/functions/custom-functions for more details.",

},

e instanceof Error ? e : undefined

);

@josefaidt @Amplifiyer please take a look at proposed wording here.

what are a few examples of errors that would fall into this category? The wording seems fine but I'm concerned with whether it would be tough to debug

Anything that function passed to defineFunction can throw.

Including:

Bundling errors,

Invalid properties/validation errors

Mistakes in function itself.

The underlying error will be printed in the console.

We copy it's message

We include actual root cause as cause, it is reported in std streams (see https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Error/cause ).

The idea here is that the troubleshooting section can be expanded on the docs page without changing this code. I.e. information about root cause and the docs page should be enough to investigate.

Btw. technically docker errors could be handled this way as well, but for now in PR they get their own category as we expect it to be common problem.

When we are wrapping the error, we should provide a different error message than the one being wrapped, specially as it is being passed in the cause. This error message should describe what happened at the call site e.g. "Failed to instantiate the custom function provider", or something like that.

Ensure that callback passed to 'defineFunction' executes without error, are we conflating the concept of callback here?

sobolk · 2024-12-30T22:46:57Z

packages/backend-function/src/provided_function_factory.ts

+        throw new AmplifyUserError(
+          'FunctionBundlingDockerError',
+          {
+            message: e.message,
+            // TODO better resolution
+            resolution:
+              'Ensure that docker is present and works correctly. See https://some.link.about.docker.',


Suggested change

throw new AmplifyUserError(

'FunctionBundlingDockerError',

{

message: e.message,

// TODO better resolution

resolution:

'Ensure that docker is present and works correctly. See https://some.link.about.docker.',

throw new AmplifyUserError(

'CustomFunctionProviderDockerRequiredError',

{

message: e.message,

resolution:

'See https://docs.amplify.aws/react/build-a-backend/functions/custom-functions for more details about current limitations and troubleshooting steps.',

@josefaidt @Amplifiyer please take a look at proposed wording here. The goal here is to:

refrain from stating docker support in error message/resolution in case we find a way to support it (avoid hardcoding).

point to web page that we can edit out of bound with most recent information about the state of support. (providing support should not involve code change in this repo, therefore need for decoupling).

We have that callout at the top of this page that calls out limitations with docker, but perhaps this warrants more clarity at the top of that page -- prereqs, etc.

There's a note I left on the docs PR to (separately) create a troubleshooting dedicated to docker errors which we can use to add more color for support

Co-authored-by: Kamil Sobol <[email protected]>

MarlonJD · 2024-12-31T07:10:28Z

Hi @sobolk, I’ve implemented the changes based on your suggestions. Please let me know if there’s anything else that needs adjustment.

sobolk · 2024-12-31T14:57:04Z

Hi @sobolk, I’ve implemented the changes based on your suggestions. Please let me know if there’s anything else that needs adjustment.

Thank you. The change in test project needs imports, see https://github.com/aws-amplify/amplify-backend/actions/runs/12556641214/job/35018558350?pr=1602

MarlonJD · 2025-01-01T21:31:11Z

Hi @sobolk, I've added the missing imports to address the issue.

sobolk · 2025-01-02T16:15:34Z

Hi @sobolk, I've added the missing imports to address the issue.

Thanks. The e2e look good here https://github.com/aws-amplify/amplify-backend/actions/runs/12584741475 .

Could you please address lint check? npm run lint:fix should do it.

MarlonJD · 2025-01-03T00:22:59Z

Hi @sobolk,

I’ve resolved the linting errors and committed the changes. I ran npm run lint, and it now reports: All matched files use Prettier code style!

packages/backend-function/src/provided_function_factory.ts

Co-authored-by: Amplifiyer <[email protected]>

sobolk · 2025-01-07T19:14:53Z

@MarlonJD could you please merge latest main to your branch? it should fix remaining checks.

sobolk · 2025-01-07T19:15:36Z

And please npm run lint:fix one more time.

…eFunction

MarlonJD · 2025-01-07T20:44:07Z

Hi @sobolk, I'm getting this error after npm run lint:fix:

> eslint --max-warnings 0 . && tsx scripts/check_package_json.ts && prettier --check . packages/backend-function


/Users/marlonjd/Developer/mobile/amplify/amplify-backend/packages/platform-core/src/cdk/enum_converters.ts
  97:66  error  Invalid type "never" of template literal expression  @typescript-eslint/restrict-template-expressions

✖ 1 problem (1 error, 0 warnings)

sobolk · 2025-01-07T20:48:22Z

Hi @sobolk, I'm getting this error after npm run lint:fix:

> eslint --max-warnings 0 . && tsx scripts/check_package_json.ts && prettier --check . packages/backend-function


/Users/marlonjd/Developer/mobile/amplify/amplify-backend/packages/platform-core/src/cdk/enum_converters.ts
  97:66  error  Invalid type "never" of template literal expression  @typescript-eslint/restrict-template-expressions

✖ 1 problem (1 error, 0 warnings)

It's likely related to workspace being in inconsistent state after main merge.

You can try the following:

npm run clean && npm install && npm run build && npm run lint:fix

Or just run npx prettier --write . in the repository root.

MarlonJD · 2025-01-07T20:54:35Z

Hi @sobolk,

Thank you for pointing this out. I followed your recommendations, which resolved the inconsistency, and I’ve committed the necessary changes.

I also want to express my gratitude for your guidance and support—it’s much appreciated!

sobolk · 2025-01-07T21:06:23Z

Hi @sobolk,

Thank you for pointing this out. I followed your recommendations, which resolved the inconsistency, and I’ve committed the necessary changes.

I also want to express my gratitude for your guidance and support—it’s much appreciated!

Thank you for contributing this @MarlonJD .

sofferor · 2025-01-10T10:19:52Z

Happy to hear it's finally possible to define a python function!
I also saw you add documentation about it in:
https://docs.amplify.aws/nextjs/build-a-backend/functions/custom-functions/#python

Can you also please add documentation about how a Python function can interact with the Amplify Data?
For example how to create/update/read/delete a table in Amplify Data.

Thanks!

MarlonJD requested review from a team as code owners June 3, 2024 16:17

MarlonJD changed the title ~~Feature/custom runtimes to define function~~ Feature: custom runtimes to define function Jun 3, 2024

edwardfoyle suggested changes Jun 3, 2024

View reviewed changes

MarlonJD force-pushed the feature/custom-runtimes-to-defineFunction branch from 9a96a36 to bb5e0df Compare June 3, 2024 22:25

MarlonJD requested a review from edwardfoyle June 3, 2024 23:38

MarlonJD mentioned this pull request Jun 5, 2024

RFC: Use existing Lambda Layers with referenceFunctionLayer #1549

Closed

edwardfoyle reviewed Jun 12, 2024

View reviewed changes

MarlonJD requested a review from edwardfoyle June 13, 2024 23:54

This was referenced Aug 15, 2024

RFC: Enable Python, Go, and others with defineFunction #1543

Open

Using python for lambda functions #1823

Closed

chore(function): add new API.md

9f6f2e4

MarlonJD mentioned this pull request Dec 22, 2024

feature(function): add custom functions documentation for AWS Amplify-backend aws-amplify/docs#8176

Merged

12 tasks

ykethan mentioned this pull request Dec 30, 2024

python function is not accessible via the amplify v2 data/resource.ts file (or it is not clear how) aws-amplify/amplify-category-api#3099

Open

sobolk reviewed Dec 30, 2024

View reviewed changes

MarlonJD and others added 4 commits December 31, 2024 10:00

fix(function): fix e2ee tests for provided function

cefa084

Co-authored-by: Kamil Sobol <[email protected]>

chore: change changeset

53b475f

Co-authored-by: Kamil Sobol <[email protected]>

chore(function): add without docker error message

89b52d4

Co-authored-by: Kamil Sobol <[email protected]>

chore(function): add provided function error message

497da33

Co-authored-by: Kamil Sobol <[email protected]>

chore(function): add missing imports

70db088

chore(function): fix lint error

cbaa8bc

Amplifiyer reviewed Jan 7, 2025

View reviewed changes

packages/backend-function/src/provided_function_factory.ts Outdated Show resolved Hide resolved

packages/backend-function/src/provided_function_factory.ts Outdated Show resolved Hide resolved

MarlonJD and others added 2 commits January 7, 2025 21:27

Update packages/backend-function/src/provided_function_factory.ts

7a79923

Co-authored-by: Amplifiyer <[email protected]>

Update packages/backend-function/src/provided_function_factory.ts

10726dd

Co-authored-by: Amplifiyer <[email protected]>

Merge branch 'aws-amplify:main' into feature/custom-runtimes-to-defin…

d7cf435

…eFunction

chore(function): fix lint issue

aa6762e

sobolk approved these changes Jan 7, 2025

View reviewed changes

Amplifiyer approved these changes Jan 7, 2025

View reviewed changes

sobolk merged commit 3f521c3 into aws-amplify:main Jan 7, 2025
143 checks passed

Feature: custom runtimes to define function #1602

Feature: custom runtimes to define function #1602

Conversation

MarlonJD commented Jun 3, 2024 • edited Loading

Problem

Changes

Checklist

changeset-bot bot commented Jun 3, 2024 • edited Loading

🦋 Changeset detected

edwardfoyle left a comment • edited Loading

Choose a reason for hiding this comment

MarlonJD commented Jun 3, 2024 • edited Loading

josefaidt commented Jun 3, 2024

MarlonJD commented Jun 3, 2024 • edited Loading

josefaidt commented Jun 3, 2024

MarlonJD commented Jun 3, 2024 • edited Loading

MarlonJD commented Jun 9, 2024

edwardfoyle left a comment

Choose a reason for hiding this comment

MarlonJD commented Jun 13, 2024

MarlonJD commented Jun 24, 2024

edwardfoyle commented Jul 3, 2024

MarlonJD commented Jul 4, 2024 • edited Loading

MarlonJD commented Jul 22, 2024

MarlonJD commented Aug 9, 2024

Srakai commented Aug 11, 2024

MarlonJD commented Aug 15, 2024

mrubelmann commented Sep 3, 2024

guikcd commented Oct 4, 2024 • edited Loading

MarlonJD commented Oct 5, 2024

MarlonJD commented Oct 14, 2024

sobolk left a comment

Choose a reason for hiding this comment

sobolk Dec 30, 2024

Choose a reason for hiding this comment

josefaidt Jan 6, 2025

Choose a reason for hiding this comment

sobolk Jan 6, 2025

Choose a reason for hiding this comment

sobolk Jan 6, 2025

Choose a reason for hiding this comment

Amplifiyer Jan 6, 2025

Choose a reason for hiding this comment

sobolk Dec 30, 2024

Choose a reason for hiding this comment

josefaidt Jan 6, 2025

Choose a reason for hiding this comment

MarlonJD commented Dec 31, 2024

sobolk commented Dec 31, 2024

MarlonJD commented Jan 1, 2025

sobolk commented Jan 2, 2025

MarlonJD commented Jan 3, 2025

sobolk commented Jan 7, 2025

sobolk commented Jan 7, 2025 • edited Loading

MarlonJD commented Jan 7, 2025

sobolk commented Jan 7, 2025

MarlonJD commented Jan 7, 2025

sobolk commented Jan 7, 2025

sofferor commented Jan 10, 2025

MarlonJD commented Jun 3, 2024 •

edited

Loading

changeset-bot bot commented Jun 3, 2024 •

edited

Loading

edwardfoyle left a comment •

edited

Loading

MarlonJD commented Jun 3, 2024 •

edited

Loading

MarlonJD commented Jun 3, 2024 •

edited

Loading

MarlonJD commented Jun 3, 2024 •

edited

Loading

MarlonJD commented Jul 4, 2024 •

edited

Loading

guikcd commented Oct 4, 2024 •

edited

Loading

sobolk commented Jan 7, 2025 •

edited

Loading