You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It happens as standalone function, or a method of a component. In every case where debugger statement is at the end of a method definition or a block. It generally doesn't happen if something directly follows the debugger statement.
It generates this error:
ERROR COMPILING IMBA RangeError: Maximum call stack size exceeded
The text was updated successfully, but these errors were encountered:
class A
def startMonitoring
return unless env.PG_PUBLICATION_NAME
const sql = postgres uri,
publications: env.PG_PUBLICATION_NAME
fetch_types: no
try
const { unsubscribe } = await sql.subscribe '*' do(row, { command, relation, key, old })
console.log 'event 1', row
debugger
And it's extremely hard to detect. As the bundler just ignores the file if it's imported. So you see errors like this in the console
> app/server/session.imba:9:8: warning: Import "sql" will always be undefined because the file "app/server/db.imba" has no exports
9 │ import {sql} from './db'/*$path$*/;
Imba Version: 2.0.0-alpha.199
Details
Here are some minimal examples:
It happens as standalone function, or a method of a component. In every case where
debuggerstatement is at the end of a method definition or a block. It generally doesn't happen if something directly follows thedebuggerstatement.It generates this error:
The text was updated successfully, but these errors were encountered: