Feature/upgrade geth and go #161

i-norden · 2022-05-31T13:50:39Z

abdulrabbani00 commented

2022-05-31 13:50:39 +00:00

(Migrated from github.com)

No description provided.

nikugogoi (Migrated from github.com) reviewed 2022-05-31 13:50:39 +00:00

ashwinphatak (Migrated from github.com) reviewed 2022-05-31 13:50:39 +00:00

prathamesh0 (Migrated from github.com) reviewed 2022-05-31 13:50:39 +00:00

abdulrabbani00 commented

2022-05-31 16:05:11 +00:00

(Migrated from github.com)

@ashwinphatak , @nikugogoi - Any of you guys familiar with the following issue when running the unit test:

  Unexpected error:
      <*errors.errorString | 0xc0005b2040>: {
          s: "db connection failed: pq: no pg_hba.conf entry for host \"172.29.0.1\", user \"vdbm\", database \"vulcanize_testing\", SSL off",
      }
      db connection failed: pq: no pg_hba.conf entry for host "172.29.0.1", user "vdbm", database "vulcanize_testing", SSL off
  occurred

The unit test is failing without any code change. I tried to debug on the server but found no success. Please let me know if this error is familiar.

@ashwinphatak , @nikugogoi - Any of you guys familiar with the following issue when running the unit test: ``` Unexpected error: <*errors.errorString | 0xc0005b2040>: { s: "db connection failed: pq: no pg_hba.conf entry for host \"172.29.0.1\", user \"vdbm\", database \"vulcanize_testing\", SSL off", } db connection failed: pq: no pg_hba.conf entry for host "172.29.0.1", user "vdbm", database "vulcanize_testing", SSL off occurred ``` The unit test is failing without any code change. I tried to debug on the server but found no success. Please let me know if this error is familiar.

👀 1

abdulrabbani00 commented

2022-06-01 12:35:43 +00:00

(Migrated from github.com)

A few notes:

I remove GINKGO from the makefile. The reason is that the tests for this repo are written using ginkgo v1, and by default, golang will try to install ginkgo v2. When you run the tests, it will output some errors lie: -ginkgo-timeout flag provided but not handled.... This is an indication that you are using the wrong version. In the make file I hardcode ginkgo v1.
I update the unit_test script to use the path of the docker-compose.yml file. For some reason, I was having issues with the unit test without it.

A few notes: * I remove `GINKGO` from the makefile. The reason is that the tests for this repo are written using ginkgo v1, and by default, golang will try to install ginkgo v2. When you run the tests, it will output some errors lie: `-ginkgo-timeout flag provided but not handled...`. This is an indication that you are using the wrong version. In the make file I hardcode ginkgo v1. * I update the unit_test script to use the path of the `docker-compose.yml` file. For some reason, I was having issues with the unit test without it.

i-norden commented

2022-06-01 17:31:44 +00:00

@ashwinphatak , @nikugogoi - Any of you guys familiar with the following issue when running the unit test:
  Unexpected error:
      <*errors.errorString | 0xc0005b2040>: {
          s: "db connection failed: pq: no pg_hba.conf entry for host \"172.29.0.1\", user \"vdbm\", database \"vulcanize_testing\", SSL off",
      }
      db connection failed: pq: no pg_hba.conf entry for host "172.29.0.1", user "vdbm", database "vulcanize_testing", SSL off
  occurred
The unit test is failing without any code change. I tried to debug on the server but found no success. Please let me know if this error is familiar.

I think it means your server is not configured (in pg_hba.conf) to allow a connection from that host, with that user, to that database (with SSL certification turned off).

> @ashwinphatak , @nikugogoi - Any of you guys familiar with the following issue when running the unit test: > > ``` > Unexpected error: > <*errors.errorString | 0xc0005b2040>: { > s: "db connection failed: pq: no pg_hba.conf entry for host \"172.29.0.1\", user \"vdbm\", database \"vulcanize_testing\", SSL off", > } > db connection failed: pq: no pg_hba.conf entry for host "172.29.0.1", user "vdbm", database "vulcanize_testing", SSL off > occurred > ``` > > The unit test is failing without any code change. I tried to debug on the server but found no success. Please let me know if this error is familiar. I think it means your server is not configured (in pg_hba.conf) to allow a connection from that host, with that user, to that database (with SSL certification turned off).

i-norden approved these changes 2022-06-01 17:32:28 +00:00

i-norden left a comment

LGTM but I don't have the time to review all these workflow changes line by line right now.

abdulrabbani00 commented

2022-06-01 17:32:37 +00:00

(Migrated from github.com)

@ashwinphatak , @nikugogoi - Any of you guys familiar with the following issue when running the unit test:
  Unexpected error:
      <*errors.errorString | 0xc0005b2040>: {
          s: "db connection failed: pq: no pg_hba.conf entry for host \"172.29.0.1\", user \"vdbm\", database \"vulcanize_testing\", SSL off",
      }
      db connection failed: pq: no pg_hba.conf entry for host "172.29.0.1", user "vdbm", database "vulcanize_testing", SSL off
  occurred
The unit test is failing without any code change. I tried to debug on the server but found no success. Please let me know if this error is familiar.
I think it means your server is not configured (in pg_hba.conf) to allow a connection from that host, with that user, to that database (with SSL certification turned off).

Thanks Ians, I got around it and got the tests working :D

> > @ashwinphatak , @nikugogoi - Any of you guys familiar with the following issue when running the unit test: > > ``` > > Unexpected error: > > <*errors.errorString | 0xc0005b2040>: { > > s: "db connection failed: pq: no pg_hba.conf entry for host \"172.29.0.1\", user \"vdbm\", database \"vulcanize_testing\", SSL off", > > } > > db connection failed: pq: no pg_hba.conf entry for host "172.29.0.1", user "vdbm", database "vulcanize_testing", SSL off > > occurred > > ``` > > > > > > > > > > > > > > > > > > > > > > > > The unit test is failing without any code change. I tried to debug on the server but found no success. Please let me know if this error is familiar. > > I think it means your server is not configured (in pg_hba.conf) to allow a connection from that host, with that user, to that database (with SSL certification turned off). Thanks Ians, I got around it and got the tests working :D

Sign in to join this conversation.

No reviewers

prathamesh0

ashwinphatak

nikugogoi

No Milestone

No project

No Assignees

2 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: cerc-io/ipld-eth-server#161