mohammadranjbarz

@mhmdksh See this part of code https://github.com/Giveth/impact-graph/blob/b67ed85e3345dee7d7b21ea5bc12796b773aa8c4/src/server/bootstrap.ts#L97-L110 It seems you just need to set DROP_DATABASE to false in configs when running on CI so it would not drop database (...

> So I think the only thing we should do to integrate this with the test step in the CI is this: > > ``` > - name: Run tests...

@jainkrati I checked our logs it seems we have almost good logs in all the `catch` statements and also inside of lots of functions we have informative logs, I don't...

Thanks @aminlatifi for your given information @jainkrati So we need this logging things for all backend projects, not only the `impact-graph` * Impact-graph * Notification-center * Authorization microservice * Balance...

@ae2079 You can clone these repositories and make sure we have logs in all the `catch` statements, till we decide what to do for fatal errors * https://github.com/Giveth/notification-center * https://github.com/Giveth/SiweAuthMicroservice...

@ae2079 I think these places are needed to throw alert ( I don't know how you should throw alert) - **When donation verification fails** you can search `syncDonationStatusWithBlockchainNetwork() error` to...

> > @ae2079 I think these places are needed to throw alert ( I don't know how you should throw alert) > > > > * **When donation verification fails**...

> I think that's a good idea... if we find out that they did actually go through ok and say "failed" because of the verification update, can you change that...

> @mohammadranjbarz is this issue still relevant? @divine-comedian I think we can close this

@MoeNick All READ APIs are already accessible for everyone, so we don't need to add scope/permission token for them unless you want some other READ web services