"We are excited to announce the new release of the Metabob VSCode extension,” said Shige Ihara, president and CEO, NEC X. Today, Metabob can perform AI-based reviews on Python code and is one of the fastest growing tools on GitHub. In fact, over the last two years Metabob has collected feedback from close to 1,000 developers to perfect the tool. This has allowed the tool to learn to detect complex problems spanning across code bases that require understanding of code logic and context. Metabob (and the VSCode extension) is trained on millions of bug fixes of both human- and AI-generated code. This way, Metabob’s AI can quickly find and explain errors in plain English and recommend solutions on how to fix them.” “The VSCode extension helps to make our tool available to even more developers. Software developers are valuable for their ability to produce code, and their productivity is reduced when fixing bugs,” said Massi Genta, CEO, Metabob. “With recent advancements in AI, we set out to solve this problem and free up time for developers. Also, rule-based systems only find pre-defined coding errors and, since they do not understand code logic and context, they tend to flag irrelevant issues that waste review time. Both approaches have drawbacks: manual review is time-consuming and rule-based systems work only on predefined rule sets to identify bugs. There is a growing use of AI systems for code generation, however, code is still mainly reviewed either manually or by using rule-based systems. It provides users with functional context-sensitive code recommendations to fix errors right in the integrated development environment (IDE) – and it is specifically trained to fix code generated by AI tools, such as GitHub Copilot and ChatGPT. This value is used ORed with one of the other LY_ERR value and can be simply masked.PALO ALTO, Calif., (GLOBE NEWSWIRE) - Metabob announced today a new artificial intelligence (AI)-powered virtual studio code (VSCode) extension for its debugging and refactoring tool that speeds software development code review by 60%. According to the specific use case, the caller should react appropriately.Įrror reported by a plugin - the highest bit in the first byte is set. The operation did not fail, but requires context recompilation before it can be completed. According to the specific use case, the caller is usually supposed to perform the operation again. The operation did not fail, but for some reason it was not possible to finish it completely. No error, not set by functions, included just to complete LY_ERR enumeration Libyang's error codes returned by the libyang functions. Structures and functions to allow error information processing. Get the last (thread, context-specific) validation error code. Get the last (thread-specific) error message. Get the last (thread, context-specific) path of the element where was an error. If the coresponding module defined a specific error message, it will be used instead the default one. Get the last (thread, context-specific) error message. Get the last (thread, context-specific) error code. Get the last (thread, context-specific) error-app-tag if there was a specific one defined in the module for the last error. Print the error structure as if just generated. Ly_err_print (const struct ly_ctx *ctx, struct ly_err_item *eitem) Get the latest (thread, context-specific) generated error structure. Get the first (thread, context-specific) generated error structure. Ly_err_clean (struct ly_ctx *ctx, struct ly_err_item *eitem)įree error structures from a context. Whenever ly_errno is set to LY_EVALID, the ly_vecode is also set to the appropriate LY_VECODE value.
0 Comments
Leave a Reply. |