Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

48 SqlException in last 24h, DonorAddresses cannot be NULL #711

Closed
tiagonmas opened this issue Nov 25, 2022 · 6 comments
Closed

48 SqlException in last 24h, DonorAddresses cannot be NULL #711

tiagonmas opened this issue Nov 25, 2022 · 6 comments
Assignees
@guerrerotook
Labels
prio:Very.High things that are the highest priority of all

Comments

@tiagonmas
Copy link
Collaborator

Describe the bug
"An error occurred while saving the entity changes. See the inner exception for details. Cannot insert the value NULL into column 'Address1', table 'alimentestaideia.core.dbo.DonorAddresses'; column does not allow nulls. INSERT fails. "

BancoAlimentar.AlimentaEstaIdeia.Repository.PaymentNotificationRepository.AddEmailNotification

As seen in AppInsights
@tiagonmas tiagonmas added the prio:Very.High things that are the highest priority of all label Nov 25, 2022
@guerrerotook
Copy link
Contributor

I already push some code to try to mitigate this.

@tiagonmas
Copy link
Collaborator Author

when /where did you push the code to ? I checked master and dev and last updates where from 2 days ago before this happened ?

@guerrerotook
Copy link
Contributor

My last try didn't work. I just this commit to try to solve the issue.

2c67faa

I don't know why still complaints that DonorAddress is null when I'm not inserting anything new in the database. Anyway this is an small change.

@tiagonmas
Copy link
Collaborator Author

Trying to push this into preprod, but pipeline is failing on Publish

guerrerotook added a commit that referenced this issue Nov 29, 2022
@guerrerotook
Trying to solve the issue #711 by adding existing references of the u…
02a7083 
…ser and the payment.
@guerrerotook
Copy link
Contributor

Changed the way we are getting those entities when creating the notification. Now instead of getting these values from the database I force to get a WebUser and BasePayment that already exits. Hope this helps solve this issue that still showing in Applicaiton Insights.

@tiagonmas
Copy link
Collaborator Author

I dont see any more issues in the last 24h. I think we can close this one. Closing ...

guerrerotook added a commit that referenced this issue Nov 30, 2022
@guerrerotook
Merge the latest changes from developer (#713)
c8151d9 
* Solved an InvalidCastException when using the TenantStaticFileProvider

* Trying to solve the issue #711 by adding existing references of the user and the payment.

* Fixed issue #688 where the sorting by date is not correct in the datatable.

* Added the viewport option trying to fix the tests.

* Set the ExpirationTime to a maximum of 15 years. #675
guerrerotook added a commit that referenced this issue Dec 2, 2022
@guerrerotook
Merge developer into master. (#714)
37b8539 
* Solved an InvalidCastException when using the TenantStaticFileProvider

* Trying to solve the issue #711 by adding existing references of the user and the payment.

* Fixed issue #688 where the sorting by date is not correct in the datatable.

* Added the viewport option trying to fix the tests.

* Set the ExpirationTime to a maximum of 15 years. #675

* Fix an small issue with the Google Authentication

* Hope to finally fix the Address1 us null on this method.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@guerrerotook guerrerotook

Labels
prio:Very.High things that are the highest priority of all
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@tiagonmas @guerrerotook