Bryan Tong (ea97ff94) at 16 Mar 06:04
Merge branch 'removeTravisCI' into 'master'
... and 2 more commits
For now, I am using the 2.5.6 connector.
TypeError: reject is not a function
at Connection.query (C:\Users\Nullivex\WebstormProjects\stretchfs\new\node_modules\mariadb\lib\connection.js:1338:14)
at PoolPromise._setConnectionUTC (C:\Users\Nullivex\WebstormProjects\stretchfs\new\node_modules\kado\lib\Database.js:74:14)
at PoolPromise.emit (node:events:513:28)
at Pool.emit (node:events:513:28)
at C:\Users\Nullivex\WebstormProjects\stretchfs\new\node_modules\mariadb\lib\pool.js:95:14
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
They are using promises and this implementation uses a callback. It would be best to detect the version and act accordingly.
When tracking notifications often the same page is loaded immediately after submit. However, when opening multiple pages at once and then submitting an action the notification for that action can appear on the wrong page.
This happens because the notifications are tracked on the session level rather than the connection level. Notifications need to be assigned a connection-id and then that connection-id needs to be checked when draining the notification queue.
Since these informational messages are desired, the end user only notices minor confusion with this bug and it is a low priority.
This means that a left join requires an actual value for each join record. (This defeats the purpose and was an oversight on original setup).
There needs to be a way to join based on the fieldName of another table as well as supporting multiple on statements. I was able to do this kind of reference using the following code, however it was caught by the error check that forces a value.
const otherQuery = Query.from(otherTable).on([['OtherThing, 'MyId']])
const myList = Query.from(someTable).select(someTable + '.*, otherTable.something').leftJoin(otherQuery)
The use of the array double makes sense here and should be allowed.
This causes tests against production applications to fail.
We need to go through and upgrade all Documentation so that all of the users coming to the website will have a better time and easier way of understanding and being able to do what you need with out having trouble understand the directions and things will look a lot better.
These three pages are the most popular pages on Kado right now so it would really help grow and optimize these three pages if we add more content as well as adding more description to each page so that it will help the user understand and make it easier for them to use and create what they need.
Here is the error I get in logs, it is generic and untraceable.
Request Error Error: aborted
at connResetException (node:internal/errors:705:14)
at abortIncoming (node:_http_server:642:17)
at socketOnClose (node:_http_server:636:3)
at Socket.emit (node:events:525:35)
at TCP.<anonymous> (node:net:301:12) {
code: 'ECONNRESET'
}
There needs to be a way to handle these errors by registering an error handler into the application setup.
Here is the error I get in logs, it is generic and untraceable.
Request Error Error: aborted
at connResetException (node:internal/errors:705:14)
at abortIncoming (node:_http_server:642:17)
at socketOnClose (node:_http_server:636:3)
at Socket.emit (node:events:525:35)
at TCP.<anonymous> (node:net:301:12) {
code: 'ECONNRESET'
}
There needs to be a way to handle these errors by registering an error handler into the application setup.
Fixes #123
NOTICE: Users must implement error handling methods or request errors will cause fatal errors.
Tony Butler (51329241) at 03 Nov 21:55
Merge branch 'removeRequestErrorHandlers' into 'master'
... and 1 more commit
Fixes #123
NOTICE: Users must implement error handling methods or request errors will cause fatal errors.
Fixes #123
NOTICE: Users must implement error handling methods or request errors will cause fatal errors.
Fixes #123
NOTICE: Users must implement error handling methods or request errors will cause fatal errors.
Here is the error I get in logs, it is generic and untraceable.
Request Error Error: aborted
at connResetException (node:internal/errors:705:14)
at abortIncoming (node:_http_server:642:17)
at socketOnClose (node:_http_server:636:3)
at Socket.emit (node:events:525:35)
at TCP.<anonymous> (node:net:301:12) {
code: 'ECONNRESET'
}
There needs to be a way to handle these errors by registering an error handler into the application setup.