Weekly GitHub Report for Enola: September 22, 2025 - September 29, 2025 (12:03:24)

Weekly GitHub Report for Enola

Thank you for subscribing to our weekly newsletter! Each week, we deliver a comprehensive summary of your GitHub project's latest activity right to your inbox, including an overview of your project's issues, pull requests, contributors, and commit activity.

---

Table of Contents

• I. News
  • 1.1. Recent Version Releases
  • 1.2. Other Noteworthy Updates
• II. Issues
  • 2.1. Top 5 Active Issues
  • 2.2. Top 5 Stale Issues
  • 2.3. Open Issues
  • 2.4. Closed Issues
  • 2.5. Issue Discussion Insights

• III. Pull Requests
  • 3.1. Open Pull Requests
  • 3.2. Closed Pull Requests
  • 3.3. Pull Request Discussion Insights

• IV. Contributors
  • 4.1. Contributors

I. News

1.1 Recent Version Releases:

No recent version releases were found.

1.2 Version Information:

Please provide the version release information you would like me to analyze and summarize.

II. Issues

2.1 Top 5 Active Issues:

We consider active issues to be issues that that have been commented on most frequently within the last week. Bot comments are omitted.

1. search_google Tool cannot be used together with other local tools ("Tool use with function calling is unsupported"): This issue reports an error encountered when attempting to use the search_google tool together with other local tools in an agent configuration, resulting in a "Tool use with function calling is unsupported" client exception. The problem appears to be specific to the search_google tool due to its server-side nature and current limitations in the underlying ADK/GenAI SDK, which does not support combining this remote tool with other local tools in a single request.

   • The discussion confirmed that the issue only occurs with the search_google tool and not with other tools like clock or exec. Documentation was updated to clarify this limitation, and a related issue (#1785) was suggested as a potential workaround, while acknowledging that a full fix may require upstream changes beyond the Enola project.
   • Number of comments this week: 3

2. Explore use of Brave Search AI Grounding: This issue is about exploring how the Brave Search AI Grounding, as described in a Brave blog post, could be integrated and utilized within the Enola project. It follows up on a previous issue and seeks to investigate potential applications of this AI grounding technology to enhance Enola's capabilities.

   • The comments discuss the creation of a new repository for the WhatToCook-agent, which will leverage the brave_search tool to find meal ingredients and instructions. The conversation suggests moving further discussion to a dedicated discussion thread for more focused collaboration.
   • Number of comments this week: 2

3. generate-xml.sh failed: error executing TestRunner command: This issue describes a failure when running Java tests within IntelliJ using the Bazel plugin inside a Nix environment, resulting in an error executing the TestRunner command via the generate-xml.sh script. The user reports encountering this problem both manually and through the Gemini CLI, and suspects it may be related to a known Bazel issue.

   • The comments reveal that adding bash to the Nix configuration did not resolve the problem, and the user has engaged with a related Bazel issue for potential solutions. Another suggestion is to bypass Bazel by setting up an IntelliJ project with a non-Bazel classpath as an alternative approach.
   • Number of comments this week: 2

4. google-java-formatter pre-commit total size of the argument list and exported variables (7.6MB) exceeds the OS limit of 2MB.: This issue describes a failure in the google-java-formatter pre-commit hook caused by the total size of the argument list and exported variables exceeding the operating system's limit, which leads to an error when formatting many Java files at once. The user reports that while running the formatter locally works fine, the problem occurs in the CI environment due to too many file arguments, and they discuss potential workarounds such as disabling the full pre-commit run temporarily or using a file list to pass arguments to the formatter.

   • The comments reveal that the issue is blocking because it causes consistent failures in the CI pipeline when many Java files are added. The user clarifies a mistake in their example command, explores the impact of ignored directories on file selection, and considers solutions like using an argument file with @filename syntax supported by the formatter or bypassing pre-commit to run the formatter directly via Nix scripts.
   • Number of comments this week: 2

Since there were fewer than 5 open issues, all of the open issues have been listed above.

2.2 Top 5 Stale Issues:

We consider stale issues to be issues that has had no activity within the last 30 days. The team should work together to get these issues resolved and closed as soon as possible.

1. Run SpotBugs during build to flag code quality issues: This issue proposes integrating SpotBugs into the build process to automatically detect and flag code quality problems, enhancing the overall reliability and maintainability of the project. It references several resources related to SpotBugs and Bazel rules, indicating a focus on leveraging existing tools and community knowledge to implement this static analysis effectively.
2. Maven Model: This issue discusses the use of the pkg: URI scheme for identifying Maven packages, highlighting that while it is used in some contexts, it is not an official IANA standard and conflicts with other uses such as the uri-scheme package for Node.js. The author suggests creating an Enola-specific URL template for Maven artifacts and inquires whether there is an existing standard from the Security (CVE) community or SPDX that could be adopted or mapped to instead.
3. Java Model: This issue focuses on enhancing the Java model functionality by enabling the command ./enola -v get --load file:bazel-bin/java/dev/enola/cli/enola_deploy.jar enola:/ to list Java Class, Enum, and other type entities, with the ability to retrieve references for a selected item. Additionally, it suggests incorporating an integration test that utilizes a method for obtaining the full path of a JAR file from a class, which could support further features such as those proposed in issue #502.
4. .owl (and .owl.xml) extension should be recognised as application/owl+xml, and loaded: This issue addresses the problem that files with the .owl and .owl.xml extensions are not being recognized with the correct media type application/owl+xml, causing them to be loaded as application/octet-stream instead. As a result, when attempting to load these files, the system fails to identify any "Things" within them, indicating improper handling of the file format during the loading process.
5. .rdf (and .rdf.xml) should be loadable (as what?): This issue concerns the inability of the system to properly load files with the extensions .rdf and .rdf.xml, specifically when attempting to process them as RDF/XML media types. Despite the loader recognizing the file and its media type, it fails to find any "Things" within the loaded resource, indicating a problem with how these file formats are being interpreted or parsed.

2.3 Open Issues

This section lists, groups, and then summarizes issues that were created within the last week in the repository.

Issues Opened This Week: 5

Summarized Issues:

• Tool Integration Limitations: The search_google tool cannot be used simultaneously with other local tools in an agent configuration due to the ADK/GenAI SDK not supporting combining remote Google Search with other tools in a single request. This limitation results in a "Tool use with function calling is unsupported" error when attempted.
• issues/1784

• Search Technology Integration: The Brave Search AI Grounding technology is being considered for integration into the Enola project, building on previous related work. This exploration aims to utilize the technology as described in the Brave blog to enhance the project.
• issues/1786

• Build and Test Failures with Bazel and Nix: Running Java tests in IntelliJ using the Bazel plugin within a Nix environment fails due to the generate-xml.sh script not executing the TestRunner command, causing test exit with error 127. The issue appears related to a known Bazel problem tracked as issue #12579.
• issues/1789

• Pre-commit Hook Environment Limits: The google-java-formatter pre-commit hook fails in CI because the combined size of the argument list and environment variables (7.6MB) exceeds the OS limit of 2MB, although it works locally. This size limitation causes the formatter to error out during automated runs.
• issues/1799

• Build System Alternatives: There is discussion about supporting alternative build systems such as Maven or Gradle either alongside or instead of Bazel for the project. This consideration aims to explore more flexible or compatible build options.
• issues/1812

2.4 Closed Issues

This section lists, groups, and then summarizes issues that were closed within the last week in the repository. This section also links the associated pull requests if applicable.

Issues Closed This Week: 5

Summarized Issues:

• Test Failures and CI Issues: Several issues report test failures caused by different underlying problems, including excessive test output size and problematic class field initializers that interfere with Bazel's test runner. These failures complicate debugging and require specific workarounds or configuration changes to resolve.
• [issues/1780, issues/1790]

• Search Tool Development: There is an ongoing effort to develop a new built-in search_brave tool using the Brave Search API as an alternative to the existing search_google tool. This aims to improve compatibility with various LLMs and enhance the Enola project's search capabilities.
• [issues/1785]

• Update and Cache Management: Users face difficulties updating the Enola application via JBang due to the updated JAR being stored in the Maven repository cache instead of JBang's cache, preventing successful version upgrades despite attempts to force reinstall and clear caches.
• [issues/1802]

• Bazel Build Configuration: Configuring Bazel to use the local JDK provided by Nix exclusively for all Java compilation and execution tasks is necessary to avoid Bazel’s default remote JDK toolchain, ensuring consistent build environments.
• [issues/1806]

2.5 Issue Discussion Insights

This section will analyze the tone and sentiment of discussions within this project's open and closed issues that occurred within the past week. It aims to identify potentially heated exchanges and to maintain a constructive project environment.

Based on our analysis, there are no instances of toxic discussions in the project's open or closed issues from the past week.

---

III. Pull Requests

3.1 Open Pull Requests

This section provides a summary of pull requests that were opened in the repository over the past week. The top three pull requests with the highest number of commits are highlighted as 'key' pull requests. Other pull requests are grouped based on similar characteristics for easier analysis. Up to 25 pull requests are displayed in this section, while any remaining pull requests beyond this limit are omitted for brevity.

Pull Requests Opened This Week: 3

Key Open Pull Requests

1. WIP: feat: hermetic build for enola #1730 (buildBazelPackage): This pull request proposes a work-in-progress feature to implement a hermetic build system for the Enola project using Bazel, addressing issue #1730 and including local test verification and documentation updates.

• URL: pull/1792

• Merged: No

• Associated Commits: ad46b

2. WIP: feat: hermetic build for enola #1730 (custom-hermetic-build): This pull request introduces a feature for a hermetic build process in the Enola project, addressing issue #1730, and is currently a work in progress.

• URL: pull/1794

• Merged: No

• Associated Commits: 72ca6

3. WIP: feat: hermetic build for enola #1730 (dumb build): This pull request introduces a feature for a hermetic build process for the Enola project, addressing issue #1730, and is currently a work in progress.

• URL: pull/1795

• Merged: No

• Associated Commits: c5777

3.2 Closed Pull Requests

This section provides a summary of pull requests that were closed in the repository over the past week. The top three pull requests with the highest number of commits are highlighted as 'key' pull requests. Other pull requests are grouped based on similar characteristics for easier analysis. Up to 25 pull requests are displayed in this section, while any remaining pull requests beyond this limit are omitted for brevity.

Pull Requests Closed This Week: 26

Key Closed Pull Requests

1. Bump various dependencies: This pull request updates various project dependencies, including pre-commit hooks, web dependencies, and nixpkgs, while also making related fixes such as changing javadoc/classpath to javac/dependencies and adding a script to run 'nix flak update'.

• URL: pull/1814

• Merged: Yes

• Associated Commits: bf3de, 6bbad, 64b48, b43c2, 7dcad, c487a

2. fix: Defer MCP secret resolution until used (fixes #1734): This pull request fixes issue #1734 by deferring the resolution of MCP secrets until they are actually used, includes improvements such as skipping tools with unavailable secrets in the MCP list-tools command, resolves duplicate use of the 'origin' field in MCP configuration, and clarifies method signatures and error messages related to MCP loading.

• URL: pull/1796

• Merged: Yes

• Associated Commits: 016e7, d051a, fc6d2, 491bf, 889d5

3. feat: search_brave MCP Tool (fixes #1785): This pull request introduces the search_brave MCP Tool feature to the project, addressing issue #1785, along with documentation updates related to tool usage limitations and additions to the table of contents and agent listings.

• URL: pull/1787

• Merged: Yes

• Associated Commits: 8b929, 2d4a5, cd83d, 80885

Other Closed Pull Requests

• Build and CI improvements: Multiple pull requests focus on enhancing the build and continuous integration processes. These include caching the Python virtual environment to speed up builds, fixing Bazel JVM external rules warnings, updating Bazel build flags, and bumping Java build rules versions to maintain dependencies and fix related issues.
  [pull/1779, pull/1782, pull/1807, pull/1781]

• RAG feature development: Several pull requests introduce and improve the RAG feature, including the initial version 0.0.1, adding new directories for VS Code, integrating langchain4j-easy-rag dependency, and updating LangChain4j to a newer version. These changes lay the groundwork for RAG testing and dependency management.
  [pull/1810, pull/1809, pull/1808, pull/1816]

• Code and tool simplifications: Pull requests address code clarity and tool improvements by simplifying McpLoader and related tools, fixing OkHttpResource with lazy MediaType retrieval and memoization, and disabling pre-commit runs temporarily due to an unresolved issue. These changes improve maintainability and optimize resource handling.
  [pull/1783, pull/1793, pull/1798]

• Java and JDK configuration updates: Updates to Java toolchains and JDK configurations are covered, including switching remotejdk_21 to use the local JDK for compilation and runtime, and a chore update related to local Java toolchains that was not merged. These changes aim to streamline Java environment setup and address related issues.
  [pull/1804, pull/1803]

• Pre-commit and formatting enhancements: Enhancements include adding a pre-commit hook that applies google-java-format only to Java files in the java/* directory, updating language-formatters-pre-commit-hooks dependency, and temporarily disabling pre-commit runs due to an issue. These changes improve code formatting and pre-commit reliability.
  [pull/1800, pull/1801, pull/1793]

• New features and agent additions: New functionality is introduced such as a Weather agent with expanded short agent names to full URLs, and a cooking-agent tool addition. These pull requests expand the project's agent capabilities and tooling.
  [pull/1778, pull/1803]

• Build infrastructure and dependency management: A pull request introduces an MVP for a future build infrastructure without Bazel, generating a single large classpath without modular dependencies. Another replaces Coursier with Maveniverse Toolbox for dependency management. These changes explore alternative build and dependency strategies.
  [pull/1813, pull/1811]

• Bug fixes and regressions: Fixes include resolving a regression where BazelTestRunner exited with return value 1, fixing classpath.bash script overwrite risk, and implementing GitHub MCP server communication via HTTP instead of STDIO. These address stability and communication issues in the project.
  [pull/1791, pull/1817, pull/1797]

• Configuration and documentation updates: Updates include adding support for secret placeholder syntax in environment configs, enabling the --http-scheme option by default in documentation, and improving development and IDE setup docs with protolint from Nix. These changes enhance configuration flexibility and developer experience.
  [pull/1788, pull/1781, pull/1816]

3.3 Pull Request Discussion Insights

This section will analyze the tone and sentiment of discussions within this project's open and closed pull requests that occurred within the past week. It aims to identify potentially heated exchanges and to maintain a constructive project environment.

Based on our analysis, there are no instances of toxic discussions in the project's open or closed pull requests from the past week.

---

IV. Contributors

4.1 Contributors

Active Contributors:

We consider an active contributor in this project to be any contributor who has made at least 1 commit, opened at least 1 issue, created at least 1 pull request, or made more than 2 comments in the last month.

If there are more than 10 active contributors, the list is truncated to the top 10 based on contribution metrics for better clarity.

Contributor	Commits	Pull Requests	Issues	Comments
vorburger	135	36	31	64
dotdoom	7	3	1	0
joaothallis	3	2	1	1
edewit	4	1	1	1
temi-ro	3	0	1	2
cstamas	0	0	2	2
Copilot	3	0	0	0
enola-dev-steward	2	0	0	0