PutBucketLifecycleConfiguration writing fails with MalformedXML #1944

rabarar · 2022-06-06T12:18:23Z

rabarar
Jun 6, 2022

Describe the bug

when attempting to Put a lifecycle configuration onto a bucket, it fails with:

Got an error creating the policy:
operation error S3: PutBucketLifecycleConfiguration, https response error StatusCode: 400, RequestID: M2506HYABH1AT7BK, HostID: ttF1JGprIhRDwOkz8e22C4EQR3CoUFvWyFau4z6fckhzzOH9aIGB25HtqZH7cxPy1DOTqD5lzlc=, api error MalformedXML: The XML you provided was not well-formed or did not validate against our published schema

The input looks as follows:

  input := &s3.PutBucketLifecycleConfigurationInput{
        Bucket: bucket,
        LifecycleConfiguration: &types.BucketLifecycleConfiguration{
            Rules: []types.LifecycleRule{
                {       
                    Status: types.ExpirationStatusEnabled,
                    AbortIncompleteMultipartUpload: &types.AbortIncompleteMultipartUpload{
                        DaysAfterInitiation: 1,
                    },  
                    Expiration: &types.LifecycleExpiration{
                        ExpiredObjectDeleteMarker: true,
                        Days:                      0,
                        Date:                      nil,
                    },
                    NoncurrentVersionExpiration:  nil,
                    NoncurrentVersionTransitions: []types.NoncurrentVersionTransition{},
                    ID:                           &lifecyleID,
                    Prefix:                       nil,
                    Transitions:                  []types.Transition{},
                },
            },
        }, 
    }

Expected Behavior

Expect it to write the lifecycle configuration with the instantiated input values

Current Behavior

failure with:

Got an error creating the policy:
operation error S3: PutBucketLifecycleConfiguration, https response error StatusCode: 400, RequestID: M2506HYABH1AT7BK, HostID: ttF1JGprIhRDwOkz8e22C4EQR3CoUFvWyFau4z6fckhzzOH9aIGB25HtqZH7cxPy1DOTqD5lzlc=, api error MalformedXML: The XML you provided was not well-formed or did not validate against our published schema

Reproduction Steps

Use this input:

   input := &s3.PutBucketLifecycleConfigurationInput{
        Bucket: bucket,
        LifecycleConfiguration: &types.BucketLifecycleConfiguration{
            Rules: []types.LifecycleRule{
                {   
                    Status: types.ExpirationStatusEnabled,
                    AbortIncompleteMultipartUpload: &types.AbortIncompleteMultipartUpload{
                        DaysAfterInitiation: 1,
                    },  
                    Expiration: &types.LifecycleExpiration{
                        ExpiredObjectDeleteMarker: true,
                        Days:                      0,  
                        Date:                      nil,
                    },  
                    NoncurrentVersionExpiration:  nil,
                    NoncurrentVersionTransitions: []types.NoncurrentVersionTransition{},
                    ID:                           &lifecyleID,
                    Prefix:                       nil,
                    Transitions:                  []types.Transition{},
                },  
            },  
        },  
    }

Possible Solution

No response

Additional Information/Context

No response

AWS Go SDK V2 Module Versions Used

"github.com/aws/aws-sdk-go-v2/config"
"github.com/aws/aws-sdk-go-v2/service/s3"
"github.com/aws/aws-sdk-go-v2/service/s3/types"

Compiler and Version used

go version go1.18.3 darwin/arm64

Operating System and version

Mac OSX 12.4

Answered by RanVaknin

Dec 1, 2022

@rabarar ,

After taking a deeper look into this here is what I have found.

The SDK serializes Golang strcuts into XML. When you send a request without that field in the request you're essentially leaving it out of the XML.
When the service reads the XML body sent by the GO SDK Client and sees that your LifeCycleRule doesn't have a <Filter> tag, it looks for <Prefix> type and if both are missing it throws this exception.

This is all handled on the service-side, and is documented.

To show that its not a GO SDK bug I've tested it on JS SDK V3 with the following code:

❌ Incorrect:

import { S3Client, PutBucketLifecycleConfigurationCommand } from '@aws-sdk/client-s3';

const client = new S3Client(

View full answer

skmcgrail · 2022-06-08T16:44:11Z

skmcgrail
Jun 8, 2022

Could you follow the instructions in the Developer Guide to enable client logging with the aws.LogRequestWithBody option enabled? That would help us understand the serialized XML that is being sent to the service for your particular request. Thanks!

0 replies

rabarar · 2022-06-08T20:51:41Z

rabarar
Jun 8, 2022
Author

Here’s the serialized XML on the request body: <LifecycleConfiguration xmlns="http://s3.amazonaws.com/doc/2006-03-01/"><Rule><AbortIncompleteMultipartUpload><DaysAfterInitiation>1</DaysAfterInitiation></AbortIncompleteMultipartUpload><Expiration><ExpiredObjectDeleteMarker>true</ExpiredObjectDeleteMarker></Expiration><ID>cleanup853211</ID><Status>Enabled</Status></Rule></LifecycleConfiguration>

…

On Jun 8, 2022, at 12:44 PM, Sean McGrail ***@***.***> wrote: Could you follow the instructions in the Developer Guide <https://aws.github.io/aws-sdk-go-v2/docs/configuring-sdk/logging/> to enable client logging with the aws.LogRequestWithBody option enabled? That would help us understand the serialized XML that is being sent to the service for your particular request. Thanks! — Reply to this email directly, view it on GitHub <#1722 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABB2J6HWUPSKYUINIBMK2VTVODEWNANCNFSM5X7GOUEQ>. You are receiving this because you authored the thread.

0 replies

skmcgrail · 2022-06-09T15:50:34Z

skmcgrail
Jun 9, 2022

Thank you for the logging information @rabarar ,

I was also able to reproduce this on my end as well in both the V2 and V1 Go SDKs, and the AWS CLI. Will follow-up this investigation with the service team.

0 replies

skmcgrail · 2022-06-09T16:52:40Z

skmcgrail
Jun 9, 2022

I've root caused this down to the service expecting the filter API member to be serialized to the request regardless if sent or not. If you provide an empty filter at the CLI it will work correctly, same with the V1 SDK (provide a pointer to a structure).

Works

<LifecycleConfiguration xmlns="http://s3.amazonaws.com/doc/2006-03-01/">
    <Rule>
        <AbortIncompleteMultipartUpload>
            <DaysAfterInitiation>1</DaysAfterInitiation>
        </AbortIncompleteMultipartUpload>
        <Expiration>
            <ExpiredObjectDeleteMarker>true</ExpiredObjectDeleteMarker>
        </Expiration>
        <Filter />
        <ID>abortMulti</ID>
        <Status>Enabled</Status>
    </Rule>
</LifecycleConfiguration>

Doesn't Work

<LifecycleConfiguration xmlns="http://s3.amazonaws.com/doc/2006-03-01/">
    <Rule>
        <AbortIncompleteMultipartUpload>
            <DaysAfterInitiation>1</DaysAfterInitiation>
        </AbortIncompleteMultipartUpload>
        <Expiration>
            <ExpiredObjectDeleteMarker>true</ExpiredObjectDeleteMarker>
        </Expiration>
        <ID>abortMulti</ID>
        <Status>Enabled</Status>
    </Rule>
</LifecycleConfiguration>

Unfortunately the Go V2 SDK uses a union type, so you can't quite set this in exactly the same way.

0 replies

rabarar · 2022-06-09T17:44:55Z

rabarar
Jun 9, 2022
Author

as an aside, attempting to reference the Filter type LifecycleRuleAndOperator in types fails to resolve and is inconsistent with the go-docs.

…

On Jun 9, 2022, at 12:52 PM, Sean McGrail ***@***.***> wrote: I've root caused this down to the service expecting the filter API member to be serialized to the request regardless if sent or not. Works <LifecycleConfiguration xmlns="http://s3.amazonaws.com/doc/2006-03-01/"> <Rule> <AbortIncompleteMultipartUpload> <DaysAfterInitiation>1</DaysAfterInitiation> </AbortIncompleteMultipartUpload> <Expiration> <ExpiredObjectDeleteMarker>true</ExpiredObjectDeleteMarker> </Expiration> <Filter /> <ID>abortMulti</ID> <Status>Enabled</Status> </Rule> </LifecycleConfiguration> Doesn't Work <LifecycleConfiguration xmlns="http://s3.amazonaws.com/doc/2006-03-01/"> <Rule> <AbortIncompleteMultipartUpload> <DaysAfterInitiation>1</DaysAfterInitiation> </AbortIncompleteMultipartUpload> <Expiration> <ExpiredObjectDeleteMarker>true</ExpiredObjectDeleteMarker> </Expiration> <ID>abortMulti</ID> <Status>Enabled</Status> </Rule> </LifecycleConfiguration> — Reply to this email directly, view it on GitHub <#1722 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABB2J6EXR3D2CN2TO6HCKZLVOIOOPANCNFSM5X7GOUEQ>. You are receiving this because you were mentioned.

0 replies

skmcgrail · 2022-06-09T18:00:14Z

skmcgrail
Jun 9, 2022

This code snippet does appear to work, though the serialization is different. It would provide a temporary work around at least:

_, err = client.PutBucketLifecycleConfiguration(context.TODO(), &s3.PutBucketLifecycleConfigurationInput{
		Bucket: aws.String("mcgrails-test-data"),
		LifecycleConfiguration: &types.BucketLifecycleConfiguration{
			Rules: []types.LifecycleRule{
				{
					Status: types.ExpirationStatusEnabled,
					AbortIncompleteMultipartUpload: &types.AbortIncompleteMultipartUpload{
						DaysAfterInitiation: 1,
					},
					Expiration: &types.LifecycleExpiration{
						ExpiredObjectDeleteMarker: true,
					},
					Filter: &types.LifecycleRuleFilterMemberPrefix{Value: ""},
					ID:     aws.String("abortMulti"),
				},
			},
		},
	})

This serializes as:

<LifecycleConfiguration xmlns="http://s3.amazonaws.com/doc/2006-03-01/">
<Rule>
    <AbortIncompleteMultipartUpload>
        <DaysAfterInitiation>1</DaysAfterInitiation>
    </AbortIncompleteMultipartUpload>
    <Expiration>
        <ExpiredObjectDeleteMarker>true</ExpiredObjectDeleteMarker>
    </Expiration>
    <Filter>
        <Prefix></Prefix>
    </Filter>
    <ID>abortMulti</ID>
    <Status>Enabled</Status>
</Rule>
</LifecycleConfiguration>

0 replies

skmcgrail · 2022-06-09T20:01:23Z

skmcgrail
Jun 9, 2022

This seems to be broken in the S3 Control model as well, for different, currently unknown, reasons...

client := s3control.NewFromConfig(cfg)
_, err = client.PutBucketLifecycleConfiguration(context.TODO(), &s3control.PutBucketLifecycleConfigurationInput{
	AccountId: aws.String("accountId"),
	Bucket:    aws.String("mcgrails-test-data"),
	LifecycleConfiguration: &types.LifecycleConfiguration{
		Rules: []types.LifecycleRule{
			{
				Status: types.ExpirationStatusEnabled,
				Filter: &types.LifecycleRuleFilter{},
				AbortIncompleteMultipartUpload: &types.AbortIncompleteMultipartUpload{
					DaysAfterInitiation: 1,
				},
				Expiration: &types.LifecycleExpiration{
					ExpiredObjectDeleteMarker: true,
				},
				ID: aws.String("abortMulti"),
			},
		},
	},
})

Returns

<?xml version="1.0" encoding="UTF-8"?>
<ErrorResponse>
    <Error>
        <Code>InvalidURI</Code>
        <Message>Couldn't parse the specified URI.</Message>
        <URI>bucket/mcgrails-test-data/lifecycleconfiguration</URI>
    </Error>
    <RequestId>Z2AGJDNK1QRRVC4V</RequestId>
    <HostId>3pXY5FhtMiP+Bq0w6wEU786mNkWl4ROwekWZ9JOusTZ5UlKkZZictU0+FkpbZlVwY2oa43KmzdQ=</HostId>
</ErrorResponse>

Seeing the same behavior with the Go V1 SDK and CLI.

0 replies

rabarar · 2022-06-13T12:38:39Z

rabarar
Jun 13, 2022
Author

Is there a timeline for a fix? Feel free to send me a t-shirt for finding this one ;)

…

On Jun 9, 2022, at 4:01 PM, Sean McGrail ***@***.***> wrote: This seems to be broken in the S3 Control model as well, for different, currently unknown, reasons... client := s3control.New(sess) _, err := client.PutBucketLifecycleConfiguration(&s3control.PutBucketLifecycleConfigurationInput{ AccountId: aws.String("<account>"), Bucket: aws.String("mcgrails-test-data"), LifecycleConfiguration: &s3control.LifecycleConfiguration{ Rules: []*s3control.LifecycleRule{ { AbortIncompleteMultipartUpload: &s3control.AbortIncompleteMultipartUpload{ DaysAfterInitiation: aws.Int64(1), }, Expiration: &s3control.LifecycleExpiration{ ExpiredObjectDeleteMarker: aws.Bool(true), }, Filter: &s3control.LifecycleRuleFilter{}, ID: aws.String("abortMulti"), Status: aws.String("Enabled"), }, }, }, }) Returns <?xml version="1.0" encoding="UTF-8"?> <ErrorResponse> <Error> <Code>InvalidURI</Code> <Message>Couldn't parse the specified URI.</Message> <URI>bucket/mcgrails-test-data/lifecycleconfiguration</URI> </Error> <RequestId>Z2AGJDNK1QRRVC4V</RequestId> <HostId>3pXY5FhtMiP+Bq0w6wEU786mNkWl4ROwekWZ9JOusTZ5UlKkZZictU0+FkpbZlVwY2oa43KmzdQ=</HostId> </ErrorResponse> Seeing the same behavior with the Go V1 SDK and CLI. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.

0 replies

rabarar · 2022-10-11T06:56:07Z

rabarar
Oct 11, 2022
Author

Definitely works but has zero relationship to the docs … not sure where types.LifecycleRuleFilterMemberPrefix comes from …

…

On Jun 9, 2022, at 2:00 PM, Sean McGrail ***@***.***> wrote: This code snippet does appear to work, though the serialization is different. It would provide a temporary work around at least: _, err = client.PutBucketLifecycleConfiguration(context.TODO(), &s3.PutBucketLifecycleConfigurationInput{ Bucket: aws.String("mcgrails-test-data"), LifecycleConfiguration: &types.BucketLifecycleConfiguration{ Rules: []types.LifecycleRule{ { Status: types.ExpirationStatusEnabled, AbortIncompleteMultipartUpload: &types.AbortIncompleteMultipartUpload{ DaysAfterInitiation: 1, }, Expiration: &types.LifecycleExpiration{ ExpiredObjectDeleteMarker: true, }, Filter: &types.LifecycleRuleFilterMemberPrefix{Value: ""}, ID: aws.String("abortMulti"), }, }, }, }) This serializes as: <LifecycleConfiguration xmlns="http://s3.amazonaws.com/doc/2006-03-01/"> <Rule> <AbortIncompleteMultipartUpload> <DaysAfterInitiation>1</DaysAfterInitiation> </AbortIncompleteMultipartUpload> <Expiration> <ExpiredObjectDeleteMarker>true</ExpiredObjectDeleteMarker> </Expiration> <Filter> <Prefix></Prefix> </Filter> <ID>abortMulti</ID> <Status>Enabled</Status> </Rule> </LifecycleConfiguration> — Reply to this email directly, view it on GitHub <#1722 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABB2J6D2DV5GSC5ZFGIBCCTVOIWLRANCNFSM5X7GOUEQ>. You are receiving this because you were mentioned.

0 replies

RanVaknin · 2022-11-30T23:03:25Z

RanVaknin
Nov 30, 2022
Maintainer

Hi @rabarar ,

You have to specify the <Filter> tag unless you have a <Prefix> tag in your xml.

source:

Filter
The Filter is used to identify objects that a Lifecycle Rule applies to. A Filter must have exactly one of Prefix, Tag, or And specified. Filter is required if the LifecycleRule does not contain a Prefix element.
Type: LifecycleRuleFilter data type

I think this isn't a bug, just an API design choice from s3.

0 replies

rabarar · 2022-11-30T23:14:30Z

rabarar
Nov 30, 2022
Author

Hi -The API doesn’t afford access to the xml - that is internal to the go api and therefore is a bug imho.Best,RobOn Nov 30, 2022, at 6:03 PM, Ran Vaknin ***@***.***> wrote: Hi @rabarar , You have to specify the <Filter> tag unless you have a <Prefix> tag in your xml. source: Filter The Filter is used to identify objects that a Lifecycle Rule applies to. A Filter must have exactly one of Prefix, Tag, or And specified. Filter is required if the LifecycleRule does not contain a Prefix element. Type: LifecycleRuleFilter data type I think this isn't a bug, just an API design choice from s3. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>

0 replies

RanVaknin · 2022-12-01T00:19:30Z

RanVaknin
Dec 1, 2022
Maintainer

@rabarar ,

After taking a deeper look into this here is what I have found.

The SDK serializes Golang strcuts into XML. When you send a request without that field in the request you're essentially leaving it out of the XML.
When the service reads the XML body sent by the GO SDK Client and sees that your LifeCycleRule doesn't have a <Filter> tag, it looks for <Prefix> type and if both are missing it throws this exception.

This is all handled on the service-side, and is documented.

To show that its not a GO SDK bug I've tested it on JS SDK V3 with the following code:

❌ Incorrect:

import { S3Client, PutBucketLifecycleConfigurationCommand } from '@aws-sdk/client-s3';

const client = new S3Client({ region: 'us-east-1' });

const command = new PutBucketLifecycleConfigurationCommand({
    Bucket: 'mybucket123',
    LifecycleConfiguration: {
        Rules: [
            {
                Status: 'Enabled',
                ID: 'abortMulti',
                Expiration: {ExpiredObjectDeleteMarker: true},
                AbortIncompleteMultipartUpload: {DaysAfterInitiation: 1},
                     // <- missing Filter
            }
        ]
    }
});

try {
    const data = await client.send(command);
    console.log(data)
} catch (error) {
    console.log(error);
}

❌ Incorrect:

const command = new PutBucketLifecycleConfigurationCommand({
    Bucket: 'mybucket123',
    LifecycleConfiguration: {
        Rules: [
            {
                Status: 'Enabled',
                ID: 'abortMulti',
                Expiration: {ExpiredObjectDeleteMarker: true},
                AbortIncompleteMultipartUpload: {DaysAfterInitiation: 1},
                Filter: {} // <- change is here
            }
        ]
    }
});

✅ Correct

const command = new PutBucketLifecycleConfigurationCommand({
    Bucket: 'mybucket123',
    LifecycleConfiguration: {
        Rules: [
            {
                Status: 'Enabled',
                ID: 'abortMulti',
                Expiration: {ExpiredObjectDeleteMarker: true},
                AbortIncompleteMultipartUpload: {DaysAfterInitiation: 1},
                Filter: {Prefix: {}} // <- change is here 
            }
        ]
    }
});

==========

Golang Example:

❌ Wont Compile:

		LifecycleConfiguration: &types.BucketLifecycleConfiguration{
			Rules: []types.LifecycleRule{
				{
					Status: types.ExpirationStatusEnabled,
					Filter: &types.LifecycleRuleFilter{}, // <- this is an interface not a concrete type. 
					AbortIncompleteMultipartUpload: &types.AbortIncompleteMultipartUpload{
						DaysAfterInitiation: 1,
					},
					Expiration: &types.LifecycleExpiration{
						ExpiredObjectDeleteMarker: true,
					},
					ID: aws.String("abortMulti"),
				},
			},
		},
	})

❌ Incorrect:

		LifecycleConfiguration: &types.BucketLifecycleConfiguration{
			Rules: []types.LifecycleRule{
				{
					Status: types.ExpirationStatusEnabled,
					            // <- missing Filter
					AbortIncompleteMultipartUpload: &types.AbortIncompleteMultipartUpload{
						DaysAfterInitiation: 1,
					},
					Expiration: &types.LifecycleExpiration{
						ExpiredObjectDeleteMarker: true,
					},
					ID: aws.String("abortMulti"),
				},
			},
		},

✅ Correct:

LifecycleConfiguration: &types.BucketLifecycleConfiguration{
			Rules: []types.LifecycleRule{
				{
					Status: types.ExpirationStatusEnabled,
					Filter: &types.LifecycleRuleFilterMemberPrefix{},
					AbortIncompleteMultipartUpload: &types.AbortIncompleteMultipartUpload{
						DaysAfterInitiation: 1,
					},
					Expiration: &types.LifecycleExpiration{
						ExpiredObjectDeleteMarker: true,
					},
					ID: aws.String("abortMulti"),
				},
			},
		},

Again quoting documentation:

Filter is required if the LifecycleRule does not contain a Prefix element.
A Filter must have exactly one of Prefix, Tag, or And specified.

The only thing I could argue is that the s3 exception is not detailed enough and requires you to dig through documentation to see what is missing in the XML that is being serialized.

Conclusion: Not a bug.

I will convert this into a discussion and keep it open so I may address more questions if you have them in the future.

Thanks again!
Ran 😄

0 replies

joel-costigliola · 2023-02-16T21:48:02Z

joel-costigliola
Feb 16, 2023

I'm having trouble with creating a rule in Go, I'd like to try the suggested approach but I believe the approach works for the aws-sdk-go-v2 API while I'm using the v1 API which does not provide types.LifecycleRuleFilterMemberPrefix.

The closest I got is:

	deleteMarkers := &s3.LifecycleRule{
		ID: aws.String("Delete expired object delete markers"),
		Expiration: &s3.LifecycleExpiration{
			Days:                      aws.Int64(1),
			ExpiredObjectDeleteMarker: aws.Bool(true),
		},
		Status: aws.String(s3.ExpirationStatusEnabled),
		Filter: &s3.LifecycleRuleFilter{},
	}

but that does not work, I'm using the aws-sdk-go v1.44.184 (again not aws-sdk-go-v2).

Is there a workaround for the v1 API?

2 replies

RanVaknin Feb 16, 2023
Maintainer

Hi @joel-costigliola ,

v1 does not have a types folder.
The parent struct is LifecycleRuleFilter that has a Prefix field on it.
so something like this:

	rulefilter := s3.LifecycleRuleFilter{
		Prefix: aws.String("foo"),
	}

For additional help with v1, please open an issue / create a discussion on the v1 repo.

Thanks,
Ran~

joel-costigliola Feb 17, 2023

Thanks for the reply, I already tried your suggestion with am empty string prefix but it did not work.
I have raised a support request to AWS but I can certainly create a github issue on the v1 repo depending on the support feedback I guess.

Anyway thanks for taking the time to reply

2023-12-01T20:01:29Z

github-actions[bot]
bot Dec 1, 2023

Hello! Reopening this discussion to make it searchable.

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

PutBucketLifecycleConfiguration writing fails with MalformedXML #1944

{{title}}

Replies: 14 comments 2 replies

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

Select a reply

PutBucketLifecycleConfiguration writing fails with MalformedXML #1944

Describe the bug

Expected Behavior

Current Behavior

Reproduction Steps

Possible Solution

Additional Information/Context

AWS Go SDK V2 Module Versions Used

Compiler and Version used

Operating System and version

❌ Incorrect:

Replies: 14 comments · 2 replies

rabarar Jun 8, 2022 Author

Works

Doesn't Work

rabarar Jun 9, 2022 Author

rabarar Jun 13, 2022 Author

rabarar Oct 11, 2022 Author

RanVaknin Nov 30, 2022 Maintainer

rabarar Nov 30, 2022 Author

RanVaknin Dec 1, 2022 Maintainer

❌ Incorrect:

❌ Incorrect:

✅ Correct

Golang Example:

❌ Wont Compile:

❌ Incorrect:

✅ Correct:

Conclusion: Not a bug.

RanVaknin Feb 16, 2023 Maintainer

github-actions[bot] bot Dec 1, 2023

Replies: 14 comments 2 replies

rabarar
Jun 8, 2022
Author

rabarar
Jun 9, 2022
Author

rabarar
Jun 13, 2022
Author

rabarar
Oct 11, 2022
Author

RanVaknin
Nov 30, 2022
Maintainer

rabarar
Nov 30, 2022
Author

RanVaknin
Dec 1, 2022
Maintainer

RanVaknin Feb 16, 2023
Maintainer

github-actions[bot]
bot Dec 1, 2023