02-21-2022, 10:33 AM
Hi Zoe,
For this particular error, we'll actually apply a "fix" soon so that we can specifically tell researchers what's wrong. In general, much of the work does fall upon us - we do continuously optimize our grammar system so that it recognizes more and more coding errors, but as you can imagine, it's a long battle.
If you do encounter such a generic error message again in the future, what I would do is to comment out sections of the code and see if the error goes away. Then gradually uncomment bits of code to see which part is the culprit. It might also be a good idea to preview incrementally, so that it's easier to notice *when* a bug is introduced.
Hope this helps!
For this particular error, we'll actually apply a "fix" soon so that we can specifically tell researchers what's wrong. In general, much of the work does fall upon us - we do continuously optimize our grammar system so that it recognizes more and more coding errors, but as you can imagine, it's a long battle.
If you do encounter such a generic error message again in the future, what I would do is to comment out sections of the code and see if the error goes away. Then gradually uncomment bits of code to see which part is the culprit. It might also be a good idea to preview incrementally, so that it's easier to notice *when* a bug is introduced.
Hope this helps!