profile
viewpoint

vHanda/google-keep-exporter 81

Export google keep notes to markdown

afiestas/docker-chaos 1

Creates chaos in a docker composed application while executing tests

vHanda/awesome-flutter-1 0

An awesome list that curates the best Flutter libraries, tools, tutorials, articles and more.

vHanda/awesome-notetaking 0

A curated list of awesome techniques, videos, and any other resources on notetaking

vHanda/awesome-selfhosted 0

A list of Free Software network services and web applications which can be hosted locally. Selfhosting is the process of hosting and managing applications instead of renting from Software-as-a-Service providers

vHanda/azad 0

amazon order history reporter chrome extension

vHanda/baloofs 0

Baloo FUSE Module

vHanda/blogofile_blog 0

A Blogofile blog plugin

vHanda/crmux 0

Chrome developer tools remote protocol multiplexer.

issue commentknadh/listmonk

Language Support

Update: Have almost finished building the English language pack. Should be able to push to master next week.

Will setup a https://traduora.com instance to manage translations and contributions.

PCC17

comment created time in 17 hours

pull request commentsupabase/gotrue

Feat: added logic for enabling/disabling users by admin

nice work @icecream78 , we might change adminChangeUserActivity to be called adminSetUserStatus , but other than that it looks pretty good,

I will have to add the new schema to supabase infrastructure but should be fine, I think it's worth it

icecream78

comment created time in a day

push eventknadh/listmonk

Kailash Nadh

commit sha 62182ab9798375f3b876016ded4b8edb2a310c5c

Refactor get-lists query for speed

view details

Kailash Nadh

commit sha 7dace84108f1b0e9e56d01f8413f4e1d1230af54

Merge branch 'master' of github.com:knadh/listmonk

view details

push time in 2 days

push eventsupabase/gotrue

Faker

commit sha 3a098169cd420f6fa4511b434ec1dc86e88cd8e7

Feat: added logic for redirecting expired token errors to user's app

view details

Fa[K]eR?! Yuriy

commit sha a4297b1a52e209593dad43a47c567b2894dfee38

Removed forgotten debug statement

view details

Fa[K]eR?! Yuriy

commit sha 6fa8899745d3c019c0eb3ea860e1a4bda812bf5d

Fixed redirect url building

view details

Ant Wilson

commit sha 71c1fe611e615ee20ac9e129eb7309c26d5de0a2

Merge pull request #44 from icecream78/feature/magic-link-error-redirect Feat: added logic for redirecting expired token errors to user's app

view details

push time in 2 days

PR merged supabase/gotrue

Feat: added logic for redirecting expired token errors to user's app

Added logic for redirecting errors to user's app when recovery/magiclink expire according to issue #39

+32 -2

1 comment

1 changed file

icecream78

pr closed time in 2 days

issue commentknadh/listmonk

Error updating campaign: pq: there is no unique or exclusion constraint matching the ON CONFLICT specification

yup, totally strange, and Im not sure what/why/how (it) happened, but happy that it wasn't too difficult to fix.

thx for all the help, I did manage to learn a little about Postgres, so win win

sweetppro

comment created time in 3 days

issue commentknadh/listmonk

Error updating campaign: pq: there is no unique or exclusion constraint matching the ON CONFLICT specification

Genuinely surprised by this. There is no straight forward way in Postgres to drop all constraints in a schema even if you want to! ^_^

sweetppro

comment created time in 3 days

issue commentknadh/listmonk

Error updating campaign: pq: there is no unique or exclusion constraint matching the ON CONFLICT specification

whoa... theres are all the changes I needed to make:

CREATE INDEX idx_sub_lists_list_id ON subscriber_lists(list_id);
CREATE INDEX idx_sub_lists_status ON subscriber_lists(status);
CREATE INDEX idx_sub_lists_sub_id ON subscriber_lists(subscriber_id);


CREATE UNIQUE INDEX campaign_lists_campaign_id_list_id_idx ON campaign_lists(campaign_id, list_id);
CREATE INDEX idx_camp_lists_camp_id ON campaign_lists(campaign_id);
CREATE INDEX idx_camp_lists_list_id ON campaign_lists(list_id);


ALTER TABLE campaigns ADD CONSTRAINT campaigns_uuid_key UNIQUE (uuid);


ALTER TABLE links ADD CONSTRAINT links_url_key UNIQUE (url);
ALTER TABLE links ADD CONSTRAINT links_uuid_key UNIQUE (uuid);


ALTER TABLE media ADD CONSTRAINT media_uuid_key UNIQUE (uuid);


ALTER TABLE settings ADD CONSTRAINT settings_key_key UNIQUE (key);
CREATE INDEX idx_settings_key ON settings(key);


CREATE UNIQUE INDEX templates_is_default_idx ON templates(is_default) WHERE is_default = true;
sweetppro

comment created time in 3 days

issue closedknadh/listmonk

Error updating campaign: pq: there is no unique or exclusion constraint matching the ON CONFLICT specification

I get the following error when trying to save/send a new campaign: Error updating campaign: pq: there is no unique or exclusion constraint matching the ON CONFLICT specification

is this a database error? im running: listmonk v0.8.0-beta PostgreSQL 10.15

closed time in 3 days

sweetppro

issue commentknadh/listmonk

Error updating campaign: pq: there is no unique or exclusion constraint matching the ON CONFLICT specification

thx for that I've found some more missing indexes...

sweetppro

comment created time in 3 days

issue commentknadh/listmonk

Error updating campaign: pq: there is no unique or exclusion constraint matching the ON CONFLICT specification

You can copy-paste the complete DROP IF ... CREATE sequence for all constraints for all tables from schema.sql. That should fix it. Either way, here's a dump of the remaining tables.

                                           Table "public.campaigns"
       Column       |           Type           | Collation | Nullable |                Default                
--------------------+--------------------------+-----------+----------+---------------------------------------
 id                 | integer                  |           | not null | nextval('campaigns_id_seq'::regclass)
 uuid               | uuid                     |           | not null | 
 name               | text                     |           | not null | 
 subject            | text                     |           | not null | 
 from_email         | text                     |           | not null | 
 body               | text                     |           | not null | 
 content_type       | content_type             |           | not null | 'richtext'::content_type
 send_at            | timestamp with time zone |           |          | 
 status             | campaign_status          |           | not null | 'draft'::campaign_status
 tags               | character varying(100)[] |           |          | 
 type               | campaign_type            |           |          | 'regular'::campaign_type
 messenger          | text                     |           | not null | 
 template_id        | integer                  |           |          | 1
 to_send            | integer                  |           | not null | 0
 sent               | integer                  |           | not null | 0
 max_subscriber_id  | integer                  |           | not null | 0
 last_subscriber_id | integer                  |           | not null | 0
 started_at         | timestamp with time zone |           |          | 
 created_at         | timestamp with time zone |           |          | now()
 updated_at         | timestamp with time zone |           |          | now()
Indexes:
    "campaigns_pkey" PRIMARY KEY, btree (id)
    "campaigns_uuid_key" UNIQUE CONSTRAINT, btree (uuid)
Foreign-key constraints:
    "campaigns_template_id_fkey" FOREIGN KEY (template_id) REFERENCES templates(id) ON DELETE SET DEFAULT
Referenced by:
    TABLE "campaign_lists" CONSTRAINT "campaign_lists_campaign_id_fkey" FOREIGN KEY (campaign_id) REFERENCES campaigns(id) ON UPDATE CASCADE ON DELETE CASCADE
    TABLE "campaign_views" CONSTRAINT "campaign_views_campaign_id_fkey" FOREIGN KEY (campaign_id) REFERENCES campaigns(id) ON UPDATE CASCADE ON DELETE CASCADE
    TABLE "link_clicks" CONSTRAINT "link_clicks_campaign_id_fkey" FOREIGN KEY (campaign_id) REFERENCES campaigns(id) ON UPDATE CASCADE ON DELETE CASCADE




                                       Table "public.links"
   Column   |           Type           | Collation | Nullable |              Default              
------------+--------------------------+-----------+----------+-----------------------------------
 id         | integer                  |           | not null | nextval('links_id_seq'::regclass)
 uuid       | uuid                     |           | not null | 
 url        | text                     |           | not null | 
 created_at | timestamp with time zone |           |          | now()
Indexes:
    "links_pkey" PRIMARY KEY, btree (id)
    "links_url_key" UNIQUE CONSTRAINT, btree (url)
    "links_uuid_key" UNIQUE CONSTRAINT, btree (uuid)
Referenced by:
    TABLE "link_clicks" CONSTRAINT "link_clicks_link_id_fkey" FOREIGN KEY (link_id) REFERENCES links(id) ON UPDATE CASCADE ON DELETE CASCADE



                        Table "public.link_clicks"
    Column     |           Type           | Collation | Nullable | Default 
---------------+--------------------------+-----------+----------+---------
 campaign_id   | integer                  |           |          | 
 link_id       | integer                  |           | not null | 
 subscriber_id | integer                  |           |          | 
 created_at    | timestamp with time zone |           |          | now()
Indexes:
    "idx_clicks_camp_id" btree (campaign_id)
    "idx_clicks_link_id" btree (link_id)
    "idx_clicks_sub_id" btree (subscriber_id)
Foreign-key constraints:
    "link_clicks_campaign_id_fkey" FOREIGN KEY (campaign_id) REFERENCES campaigns(id) ON UPDATE CASCADE ON DELETE CASCADE
    "link_clicks_link_id_fkey" FOREIGN KEY (link_id) REFERENCES links(id) ON UPDATE CASCADE ON DELETE CASCADE
    "link_clicks_subscriber_id_fkey" FOREIGN KEY (subscriber_id) REFERENCES subscribers(id) ON UPDATE CASCADE ON DELETE SET NULL



                                       Table "public.media"
   Column   |           Type           | Collation | Nullable |              Default              
------------+--------------------------+-----------+----------+-----------------------------------
 id         | integer                  |           | not null | nextval('media_id_seq'::regclass)
 uuid       | uuid                     |           | not null | 
 provider   | text                     |           | not null | ''::text
 filename   | text                     |           | not null | 
 thumb      | text                     |           | not null | 
 created_at | timestamp with time zone |           |          | now()
Indexes:
    "media_pkey" PRIMARY KEY, btree (id)
    "media_uuid_key" UNIQUE CONSTRAINT, btree (uuid)



                          Table "public.settings"
   Column   |           Type           | Collation | Nullable |   Default   
------------+--------------------------+-----------+----------+-------------
 key        | text                     |           | not null | 
 value      | jsonb                    |           | not null | '{}'::jsonb
 updated_at | timestamp with time zone |           |          | now()
Indexes:
    "settings_key_key" UNIQUE CONSTRAINT, btree (key)
    "idx_settings_key" btree (key)


                                       Table "public.templates"
   Column   |           Type           | Collation | Nullable |                Default                
------------+--------------------------+-----------+----------+---------------------------------------
 id         | integer                  |           | not null | nextval('templates_id_seq'::regclass)
 name       | text                     |           | not null | 
 body       | text                     |           | not null | 
 is_default | boolean                  |           | not null | false
 created_at | timestamp with time zone |           |          | now()
 updated_at | timestamp with time zone |           |          | now()
Indexes:
    "templates_pkey" PRIMARY KEY, btree (id)
    "templates_is_default_idx" UNIQUE, btree (is_default) WHERE is_default = true
Referenced by:
    TABLE "campaigns" CONSTRAINT "campaigns_template_id_fkey" FOREIGN KEY (template_id) REFERENCES templates(id) ON DELETE SET DEFAULT


                       Table "public.campaign_views"
    Column     |           Type           | Collation | Nullable | Default 
---------------+--------------------------+-----------+----------+---------
 campaign_id   | integer                  |           | not null | 
 subscriber_id | integer                  |           |          | 
 created_at    | timestamp with time zone |           |          | now()
Indexes:
    "idx_views_camp_id" btree (campaign_id)
    "idx_views_subscriber_id" btree (subscriber_id)
Foreign-key constraints:
    "campaign_views_campaign_id_fkey" FOREIGN KEY (campaign_id) REFERENCES campaigns(id) ON UPDATE CASCADE ON DELETE CASCADE
    "campaign_views_subscriber_id_fkey" FOREIGN KEY (subscriber_id) REFERENCES subscribers(id) ON UPDATE CASCADE ON DELETE SET NULL

sweetppro

comment created time in 3 days

issue commentknadh/listmonk

Error updating campaign: pq: there is no unique or exclusion constraint matching the ON CONFLICT specification

any chance you could post a complete overview of the schema of all the tables? So I can check nothing else is messed up

sweetppro

comment created time in 3 days

issue commentknadh/listmonk

Error updating campaign: pq: there is no unique or exclusion constraint matching the ON CONFLICT specification

yikes...

im not sure what happened, but this is probably all related to my update failure. thx for your help

sweetppro

comment created time in 3 days

issue commentknadh/listmonk

Error updating campaign: pq: there is no unique or exclusion constraint matching the ON CONFLICT specification

Two indexes are missing from the subscribers table. You'll have to recreate those.

The subscribers_pkey error on inserting a new subscriber might be because the autoincrement value of id is out of sequence and it's picking an ID that's already in the table. Not sure how that's happened either.

You can try resetting the sequence to with SELECT setval('subscribers_id_seq', 100000);

sweetppro

comment created time in 3 days

issue commentknadh/listmonk

Error updating campaign: pq: there is no unique or exclusion constraint matching the ON CONFLICT specification

listmonk=> \d subscribers
                                       Table "public.subscribers"
   Column   |           Type           | Collation | Nullable |                 Default                 
------------+--------------------------+-----------+----------+-----------------------------------------
 id         | integer                  |           | not null | nextval('subscribers_id_seq'::regclass)
 uuid       | uuid                     |           | not null | 
 email      | text                     |           | not null | 
 name       | text                     |           | not null | 
 attribs    | jsonb                    |           | not null | '{}'::jsonb
 status     | subscriber_status        |           | not null | 
 campaigns  | integer[]                |           |          | 
 created_at | timestamp with time zone |           |          | now()
 updated_at | timestamp with time zone |           |          | now()
Indexes:
    "subscribers_pkey" PRIMARY KEY, btree (id)
Referenced by:
    TABLE "campaign_views" CONSTRAINT "campaign_views_subscriber_id_fkey" FOREIGN KEY (subscriber_id) REFERENCES subscribers(id) ON UPDATE CASCADE ON DELETE SET NULL
    TABLE "link_clicks" CONSTRAINT "link_clicks_subscriber_id_fkey" FOREIGN KEY (subscriber_id) REFERENCES subscribers(id) ON UPDATE CASCADE ON DELETE SET NULL
    TABLE "subscriber_lists" CONSTRAINT "subscriber_lists_subscriber_id_fkey" FOREIGN KEY (subscriber_id) REFERENCES subscribers(id) ON UPDATE CASCADE ON DELETE CASCADE
sweetppro

comment created time in 3 days

issue commentknadh/listmonk

Error updating campaign: pq: there is no unique or exclusion constraint matching the ON CONFLICT specification

Can you share \d subscribers?

I also have this error when sending out my campaign:

Same issue with missing indexes. You can try recreating those for the rest of the tables. Surprising that all indexes have gone missing!

sweetppro

comment created time in 3 days

issue commentknadh/listmonk

Error updating campaign: pq: there is no unique or exclusion constraint matching the ON CONFLICT specification

I also have this error when send out my campaign:

2020/11/28 13:52:00 error registering tracking for link 'https://xxxxxx.com': pq: there is no unique or exclusion constraint matching the ON CONFLICT specification
sweetppro

comment created time in 3 days

issue commentknadh/listmonk

Error updating campaign: pq: there is no unique or exclusion constraint matching the ON CONFLICT specification

I ran the following updates:

CREATE INDEX idx_sub_lists_list_id ON subscriber_lists(list_id);
CREATE INDEX idx_sub_lists_status ON subscriber_lists(status);
CREATE INDEX idx_sub_lists_sub_id ON subscriber_lists(subscriber_id);


CREATE UNIQUE INDEX campaign_lists_campaign_id_list_id_idx ON campaign_lists(campaign_id, list_id);
CREATE INDEX idx_camp_lists_camp_id ON campaign_lists(campaign_id);
CREATE INDEX idx_camp_lists_list_id ON campaign_lists(list_id);

and I can now save my new campaign! however I am still having issues adding a new user via the form. I still get this error:

2020/11/28 13:38:06 error inserting subscriber: pq: duplicate key value violates unique constraint "subscribers_pkey"
sweetppro

comment created time in 3 days

issue commentknadh/listmonk

Error updating campaign: pq: there is no unique or exclusion constraint matching the ON CONFLICT specification

The constraints from what's expected in the default schema and what you have are different. The indexes are missing, which explains the Postgres errors. Something's gone wrong in the manual schema changes, it looks like.

You can try manually creating the indexes for subscriber_lists and campaign_lists by copy-pasting the statements from schema.sql.

It might be easier to do a) data only Postgres dump b) re-install listmonk and do a TRUNCATE subscribers, campaigns, lists, templates CASCADE to clear the default data c) restore the dump into the database.

sweetppro

comment created time in 3 days

pull request commentsupabase/gotrue

Feat: added logic for redirecting expired token errors to user's app

@awalias Do you have any other remarks?

icecream78

comment created time in 3 days

issue commentknadh/listmonk

Error updating campaign: pq: there is no unique or exclusion constraint matching the ON CONFLICT specification

listmonk=# \d subscriber_lists
                                   Table "public.subscriber_lists"
    Column     |           Type           | Collation | Nullable |              Default               
---------------+--------------------------+-----------+----------+------------------------------------
 subscriber_id | integer                  |           | not null | 
 list_id       | integer                  |           | not null | 
 status        | subscription_status      |           | not null | 'unconfirmed'::subscription_status
 created_at    | timestamp with time zone |           |          | now()
 updated_at    | timestamp with time zone |           |          | now()
Indexes:
    "subscriber_lists_pkey" PRIMARY KEY, btree (subscriber_id, list_id)
Foreign-key constraints:
    "subscriber_lists_list_id_fkey" FOREIGN KEY (list_id) REFERENCES lists(id) ON UPDATE CASCADE ON DELETE CASCADE
    "subscriber_lists_subscriber_id_fkey" FOREIGN KEY (subscriber_id) REFERENCES subscribers(id) ON UPDATE CASCADE ON DELETE CASCADE
listmonk=# \d campaign_lists;
              Table "public.campaign_lists"
   Column    |  Type   | Collation | Nullable | Default  
-------------+---------+-----------+----------+----------
 campaign_id | integer |           | not null | 
 list_id     | integer |           |          | 
 list_name   | text    |           | not null | ''::text
Foreign-key constraints:
    "campaign_lists_campaign_id_fkey" FOREIGN KEY (campaign_id) REFERENCES campaigns(id) ON UPDATE CASCADE ON DELETE CASCADE
    "campaign_lists_list_id_fkey" FOREIGN KEY (list_id) REFERENCES lists(id) ON UPDATE CASCADE ON DELETE SET NULL
sweetppro

comment created time in 3 days

issue commentknadh/listmonk

Error updating campaign: pq: there is no unique or exclusion constraint matching the ON CONFLICT specification

Looks like the constraints on subscriber_lists and campaign_lists table are broken. Looking at schema.sql and re-creating the same properties should fix it. You might have to delete, or NULL the values in the offending rows. Can you post the results of psql > \d subscriber_lists and \d campaign_lists schemas?

Here's how they should look like.

                                   Table "public.subscriber_lists"
    Column     |           Type           | Collation | Nullable |              Default               
---------------+--------------------------+-----------+----------+------------------------------------
 subscriber_id | integer                  |           | not null | 
 list_id       | integer                  |           | not null | 
 status        | subscription_status      |           | not null | 'unconfirmed'::subscription_status
 created_at    | timestamp with time zone |           |          | now()
 updated_at    | timestamp with time zone |           |          | now()
Indexes:
    "subscriber_lists_pkey" PRIMARY KEY, btree (subscriber_id, list_id)
    "idx_sub_lists_list_id" btree (list_id)
    "idx_sub_lists_status" btree (status)
    "idx_sub_lists_sub_id" btree (subscriber_id)
Foreign-key constraints:
    "subscriber_lists_list_id_fkey" FOREIGN KEY (list_id) REFERENCES lists(id) ON UPDATE CASCADE ON DELETE CASCADE
    "subscriber_lists_subscriber_id_fkey" FOREIGN KEY (subscriber_id) REFERENCES subscribers(id) ON UPDATE CASCADE ON DELETE CASCADE
listmonk=# \d campaign_lists;
              Table "public.campaign_lists"
   Column    |  Type   | Collation | Nullable | Default  
-------------+---------+-----------+----------+----------
 campaign_id | integer |           | not null | 
 list_id     | integer |           |          | 
 list_name   | text    |           | not null | ''::text
Indexes:
    "campaign_lists_campaign_id_list_id_idx" UNIQUE, btree (campaign_id, list_id)
    "idx_camp_lists_camp_id" btree (campaign_id)
    "idx_camp_lists_list_id" btree (list_id)
Foreign-key constraints:
    "campaign_lists_campaign_id_fkey" FOREIGN KEY (campaign_id) REFERENCES campaigns(id) ON UPDATE CASCADE ON DELETE CASCADE
    "campaign_lists_list_id_fkey" FOREIGN KEY (list_id) REFERENCES lists(id) ON UPDATE CASCADE ON DELETE SET NULL

sweetppro

comment created time in 3 days

PR opened supabase/gotrue

Feat: added logic for enabling/disabling users by admin

Add feature to enable/disable users by admin according issue #41 While start implementing the task I realized that it's more correct to separate this functionality from PUT /admin/users method. While doing task I've changed migrations's schema.sql file and I'm not sure is this correct=) but I needed migrations was added to

+100 -1

0 comment

10 changed files

pr created time in 3 days

issue commentknadh/listmonk

Error updating campaign: pq: there is no unique or exclusion constraint matching the ON CONFLICT specification

I see this:

2020/11/28 08:17:01 v0.8.0-beta (cde0b4b 2020-11-10T18:12:39Z)
2020/11/28 08:17:01 reading config: config.toml
2020/11/28 08:17:01 connecting to db: localhost:5432/listmonk
2020/11/28 08:17:02 loading static files from: static
2020/11/28 08:17:02 media upload provider: filesystem
2020/11/28 08:17:02 loaded email (SMTP) messenger: AKIAQX5KF2TS25XB65UI@email-smtp.us-east-1.amazonaws.com
2020/11/28 08:20:03 error updating campaign: pq: there is no unique or exclusion constraint matching the ON CONFLICT specification
2020/11/28 08:21:00 error updating campaign: pq: there is no unique or exclusion constraint matching the ON CONFLICT specification
2020/11/28 08:52:31 error inserting subscriber: pq: duplicate key value violates unique constraint "subscribers_pkey"
2020/11/28 08:52:40 error inserting subscriber: pq: duplicate key value violates unique constraint "subscribers_pkey"
2020/11/28 08:52:43 error inserting subscriber: pq: duplicate key value violates unique constraint "subscribers_pkey"
2020/11/28 09:19:16 error updating campaign: pq: there is no unique or exclusion constraint matching the ON CONFLICT specification
sweetppro

comment created time in 3 days

issue commentknadh/listmonk

Error updating campaign: pq: there is no unique or exclusion constraint matching the ON CONFLICT specification

hmm, maybe the schema changes broke something. Can you check the app logs? Terminal or UI -> Settings -> Logs.

sweetppro

comment created time in 3 days

issue commentknadh/listmonk

Error updating campaign: pq: there is no unique or exclusion constraint matching the ON CONFLICT specification

Im getting a 500 Internal Server Error when making this call PUT | https://xxxxxxx.com/api/campaigns/1' and also this:Uncaught (in promise) Error: Request failed with status code 500 chunk-vendors.f5340186.js:7:67152`

sweetppro

comment created time in 3 days

Pull request review commentknadh/listmonk

added dav provider

 type settings struct { 	PrivacyAllowWipe          bool     `json:"privacy.allow_wipe"` 	PrivacyExportable         []string `json:"privacy.exportable"` -	UploadProvider             string `json:"upload.provider"`-	UploadFilesystemUploadPath string `json:"upload.filesystem.upload_path"`-	UploadFilesystemUploadURI  string `json:"upload.filesystem.upload_uri"`-	UploadS3AwsAccessKeyID     string `json:"upload.s3.aws_access_key_id"`-	UploadS3AwsDefaultRegion   string `json:"upload.s3.aws_default_region"`-	UploadS3AwsSecretAccessKey string `json:"upload.s3.aws_secret_access_key,omitempty"`-	UploadS3Bucket             string `json:"upload.s3.bucket"`-	UploadS3BucketDomain       string `json:"upload.s3.bucket_domain"`-	UploadS3BucketPath         string `json:"upload.s3.bucket_path"`-	UploadS3BucketType         string `json:"upload.s3.bucket_type"`-	UploadS3Expiry             string `json:"upload.s3.expiry"`+	UploadProvider             string            `json:"upload.provider"`+	UploadFilesystemUploadPath string            `json:"upload.filesystem.upload_path"`+	UploadFilesystemUploadURI  string            `json:"upload.filesystem.upload_uri"`+	UploadS3AwsAccessKeyID     string            `json:"upload.s3.aws_access_key_id"`+	UploadS3AwsDefaultRegion   string            `json:"upload.s3.aws_default_region"`+	UploadS3AwsSecretAccessKey string            `json:"upload.s3.aws_secret_access_key,omitempty"`+	UploadS3Bucket             string            `json:"upload.s3.bucket"`+	UploadS3BucketDomain       string            `json:"upload.s3.bucket_domain"`+	UploadS3BucketPath         string            `json:"upload.s3.bucket_path"`+	UploadS3BucketType         string            `json:"upload.s3.bucket_type"`+	UploadS3Expiry             string            `json:"upload.s3.expiry"`+	UploadDavEndpoint          string            `json:"upload.webdav.endpoint"`+	UploadDavUsername          string            `koanf:"upload.webdav.username"`+	UploadDavPassword          string            `koanf:"upload.webdav.password"`+	UploadDavRootPath          string            `koanf:"upload.webdav.root_path"`+	UploadDavHeaders           map[string]string `koanf:"upload.webdav.headers"` 

Should we add

	if !dav.Connect(dav.Opts{
		Endpoint: set.UploadDavEndpoint,
		Username: set.UploadDavUsername,
		Password: set.UploadDavPassword,
		RootPath: set.UploadDavRootPath,
		Headers:  set.UploadDavHeaders,
	}) {
		return echo.NewHTTPError(http.StatusBadRequest,
			fmt.Sprintf("Error connecting to webdav provider: %v", err))
	}

in line number 187 as an additional validation for configurations

joicemjoseph

comment created time in 4 days

PR opened knadh/listmonk

added dav provider
+241 -90

0 comment

7 changed files

pr created time in 4 days

pull request commentsupabase/gotrue-js

feat: adds inviteUserByEmail for api users

:tada: This PR is included in version 1.8.0 :tada:

The release is available on:

Your semantic-release bot :package::rocket:

awalias

comment created time in 4 days

release supabase/gotrue-js

v1.8.0

released time in 4 days

more