front-end | semantic analysis for the Cypher Query Language | Parser library

Google recently sent me an email with the following:

One or more of your web applications uses the legacy Google Sign-In JavaScript library. Please migrate your project(s) to the new Google Identity Services SDK before March 31, 2023

The project in question uses the Google Drive API alongside the now legacy authentication client.

The table on the migration page (https://developers.google.com/identity/gsi/web/guides/migration) says:

I was currently using gapi on the front-end to perform authorization which is loaded from apis.google.com/js/api.js. According to the table I would need to replace it with the new library.

I've tried the following to authenticate and authorize in the same manner that I used to do with gapi:

I have a ratchet WebSocket server, whose entityManager is initialized from the backend. However, if some changes happen from one of the front-ends since the state of the entityManager of the WebSocket server is different from the backend, the new changes are not reflected in the data that is served by the WebSocket server.

For this purpose, I wrote some listeners on the backend that listen for changes in these entities in and then send a request to the server like so:

I am using Spring Security along with Spring Authorization Server and experimenting with creating an auth server.

I have a basic flow allowing me to login with the pre-built login page (from a baledung guide - this is the code I'm working off ). I'm assuming this login page form comes from formLogin() like so:

I am using fetch in a NodeJS application. Technically, I have a ReactJS front-end calling the NodeJS backend (as a proxy), and then the proxy calls out to backend services on a different domain.

However, from logging errors from consumers (I haven't been able to reproduce this issue myself) I see that a lot of these proxy calls (using fetch) throw an error that just says Network Request Failed, which is of no help. Some context:

• This only occurs on a subset of all total calls (lets say 5% of traffic)
• Users that encounter this error can often make the same call again some time later (next couple minutes/hours/days) and it will go through
• From Application Insights, I can see no correlation between browsers, locations, etc
• Calls often return fast, like < 100 ms
• All calls are HTTPS, non are HTTP
• We have a fetch polyfill from fetch-ponyfill that will take over if fetch is not available (Internet Explorer). I did test this package itself and the calls went through fine. I also mentioned that this error does occur on browsers that do support fetch, so I don't think this is the error.
• Fetch settings for all requests
  • Method is set per request, but I've seen it fail on different types (GET, POST, etc)
  • Mode is set to 'same-origin'. I thought this was odd, since we were sending a request from one domain to another, but I tried to set it differently and it didn't affect anything. Also, why would some requests work for some, but not for others?
  • Body is set per request, based on the data being sent.
  • Headers is usually just Accept and Content-Type, both set to JSON.

I have tried researching this topic before, but most posts I found referenced React native applications running on iOS, where you have to set some security permissions in the plist file to allow HTTP requests or something to do with transport security.

I have implement logging specific points for the data in Application Insights, and I can see that fetch() was called, but then() was never reached; it went straight to the .catch(). So it's not even reaching code that parses the request, because apparently no request came back (we then parse the JSON response and call other functions, but like I said, it doesn't even reach this point).

Which is also odd, since the request never comes back, but it fails (often) within 100 ms.

My suspicions:

1. Some consumers have some sort of add-on for there browser that is messing with the request. Although, I run with uBlock Origin and HTTPS Everywhere and I have not seen this error. I'm not sure what else could be modifying requests that would cause it to immediately fail.
2. The call goes through, which then reaches an Azure Application Gateway, which might fail for some reason (too many connected clients, not enough ports, etc) and returns a response that immediately fails the fetch call without running the .then() on the response.

For #2, I remember I had traced a network call that failed and returned Network Request Failed: Made it through the proxy -> made it through the Application Gateway -> hit the backend services -> backend services sent a response. I am currently requesting access to backend service logs in order to verify this on some more recent calls (last time I did this, I did it through a screenshare with a backend developer), and hopefully clear up the path back to the client (the ReactJS application). I do remember though that it made it to the backend services successfully.

So I'm honestly not sure what's going on here. Does anyone have any insight?

I have a react project which has two pages and each page has its own css file.

1- Page1.jsx -> Page1.css
2- Page2.jsx -> Page2.css

Each css file is only included in its corresponding jsx file. Both css files share similar class name (example: column, image-place, etc.)

The problem is Page1 is affected by Page2 CSS file.

I am not expert in front-end technologies. Any help will be appreciated.

I'm trying to query from a table where the teacherId is equal to the teacherId of the person that logs in but I can't pass that teacherId from the front-end to the back-end.

This is the back end

I have the initial state of tree diagram that I'm building, with collapse animation and custom node design but whatever I try to make the tree vertical instead of horizontal I mess something else (animation not working well, the lines are wrong and other problems).

I'm trying to visualize a merkle tree where a vertical display is more intuitive. unfortunately I dont have strong background in front-end or deep understanding of d3 lib.

Here is the code:

I need to export huge amount of rows to Excel. I am using Laravel-excel. I followed all the suggestions given in documentation for exporting large database.

I have created a RDS cluster with 2 instances using terraform. When I am upgrading the RDS from front-end, it modifies the cluster. But when I do the same using terraform, it destroys the instance.

We tried create_before_destroy, and it gives error.

We tried with ignore_changes=engine but that didn't make any changes.

Is there any way to prevent it?