Based on the following article, select the correct option for the given question.
    Respond ONLY with the letter of the correct option (A, B, C, or D) and nothing else.
    Article: Welcome to Day 4 of our deep dive series covering five of the recent Qubic grant winners. Today we explore QubicMetrics, a user-friendly dashboard that provides essential metrics, enhancing the function of Qubic Explorer and providing in-depth insights into the Qubic network.

QubicMetrics will have the ability to track all Qubic repositories on GitHub and compile global analytics. Metrics such as commit statistics, contributor activity, and overall repository performance will be tracked and aggregated. It will provide accurate insights about the Qubic network by integrating with Qubic’s RPC servers, providing real-time data, and using the GitHub REST API to exclude merge commits and empty commits.

Meet the Developer
Tomas Pozo (Discord: tomaspozo_) is the developer of QubicMetrics. He has expertise in creating user-centric interfaces, and specialises in building web applications. He is proficient in JavaScript, TypeScript, Python, as well as React, Node.js, NestJS, Express, Django frameworks. As a continual learner, Tomas is always exploring new technologies in the tech industry. His technical contributions can be viewed on his GitHub page.

QubicMetrics Features and Benefits
Empowering Users: Users will have access to critical data about the Qubic network, which will promote engagement, help stakeholders make informed decisions, and ultimately contribute to the growth of the Qubic ecosystem.

Global Analytics: QubicMetrics will provide an overview of development activities through tracking all Qubic repositories on GitHub, as well as aggregating and displaying key metrics.

Real-Time Data Integration: The dashboard will integrate directly with Qubic’s RPC servers to fetch real-time data.

User-Friendly Interface: Users will be able to easily filter and explore data, compare historical trends, and gain insights into the network’s performance and development activities.

Ecosystem Growth: The dashboard will add value to and promote growth of the Qubic ecosystem by providing a foundational layer for other decentralised applications (dApps), wallets, and services.

Technical Architecture
React JavaScript library was chosen for its development efficiency, quick responsiveness, and ability to provide an optimal user experience.

Vite Single-Page Application (SPA) was chosen for its numerous benefits, including rapid development environment, fast load times, optimal user experience, reduced server load, easy development and maintenance, offline capabilities, and enhanced performance.

Tremor.so, an open-source charting library, was chosen for its functional and visually appealing charts, as well as components for building dashboards.

NestJS was chosen to develop a backend. It was chosen for its versatility and structured workflow, allowing rapid development of APIs and easy implementation of different protocols for both data exchange (e.g., REST, Graphql, etc.) and security. The backend will extract daily statistical data to populate a Postgres database. Current and historical data will be viewable within the dashboard.

Current Development Stages
The frontend has been developed. This includes key components such as data displays, filters and wallet connectivity. Development of the backend is underway. It will include integrating APIs to fetch data, and infrastructure for data processing and storage. The application will undergo rigorous testing prior to release. The project is tentatively scheduled for completion in October, 2024.

User Experience
QubicMetrics will align with the Qubic Explorer dashboard, enhancing the user experience, and maintaining the look and feel of the existing application. With a strong focus on historical data, users will be able to create charts for each of the main Qubic metrics. They will also be able to filter data by time periods to explore past trends.

Developer Grants Available
Congratulations to the developer of QubicMetrics! Do you have a project idea that could support the growth of the Qubic network? Qubic is actively seeking developers to help us grow our ecosystem. Read more about the Qubic Grants Program and apply for a grant.

Please note: This is the first batch of grants of many to come. The Qubic Grants Program is not currently accepting applications. There will be an announcement when the next grant period opens.

What features of QubicMetrics are you most excited to see implemented? Join the conversation on Discord and Telegram and share your thoughts.

Disclaimer 

QubicMetrics is a community-driven initiative and operates independently of Qubic Core and the Steering Committee (SteCo). It reflects the efforts and ideas of the community.

    Question: monitor = {'tes': 366, "Left': 327, "tous": 678, "selges": 309}
rare file math — ‘carss dene
File "C:\hostedtoalcache\windows\Python\3.9.13\x64\1ib\asyncio\praactor_events.py", 1
self.close()
File "C:\hostedtoalcache\windows\Python\3.9.13\x64\1ib\asyncio\praactor_events.py", 1
self._loop.call_soon(self._call_connection_lost, None)
File "C:\hostedtoalcache\windows\Python\3.9.13\x64\1ib\asyncio\base_events.py", line
self._check_closed()
File "C:\hostedtoalcache\windows\Python\3.9.13\x64\1ib\asyncio\base_events.py", Line |
raise RuntimeErrar('Event loop is closed}
untimeError: Event loop is closed
Ss C: \Users\runneradmin\Desktop> & C:/hastedtoolcache/windows/Pythen/3.9.13/x64/python..