Good First Issues

### Description: Add a function is_email(text: str) -> bool that returns True if the input is a valid email address, False otherwise. ### Tasks: - [ ] Implement is_email() in validators.py - [ ] Use regex for validation (re.match) - [ ] Add unit tests in tests/test_validators.py - [ ] Update documentation with usage example

Created: 8/16/2025

Page going over each programming language likely to be used for VIP. Description of common applications for each programming language, ease of writing, interpreted vs compiled, how optimized its code tends to be, etc. Also add link to coding standard page if that's been made

Created: 8/16/2025

### Description #### Description Implement a comprehensive user registration system with Firebase authentication and payment processing capabilities. NOTE: THE USER REGISTERATION PAGE IS NOT THE PROJECT-XANGOES FRONTEND, YOU CAN USE POSTMAN TO MIMIC THE FRONTEND CALLS #### Requirements **Backend Implementation:** - Create `POST /register` endpoint **User Table Schema:** ```sql users { email: varchar(255) NOT NULL UNIQUE, name: varchar(255), photo: text, gender: enum('male', 'female', 'other'), dob: timestamp, state: varchar(100), // lowercase city: varchar(100), // lowercase college: varchar(255), // References institute.id idCard: text, // Cloudinary photo URL mobile: varchar(20) NOT NULL UNIQUE, festID: text, // fest ID rollNumber: varchar(50), firebaseId: varchar(255) NOT NULL UNIQUE, hasPaid: boolean DEFAULT false, receipt: text, transactionID: varchar(255), hall: varchar(100), // lowercase createdAt: timestamp DEFAULT now(), updatedAt: timestamp DEFAULT now() } ``` **Transaction Flow:** 1. User signs up with Firebase Google Auth 2. Registration details sent to backend 3. **Payment Gateway Flow:** // SKIP THE PAYMENT GATEWAY INTEGRATION FOR NOW JUST CREATE A CALLBACK ENDPOINT FOR THE PAYMENT GATEWAY THAT SENDS THE TRANSACTION DETAILS TO THE DB - Initial registration with basic details - Payment gateway callback to `POST /complete-transaction?via=payment-gateway.` 4. **Manual Payment Flow:** `POST /complete-transaction?via=manual` - Payment screenshot uploaded directly - Transaction details stored in transaction table NOTE: IN BOTH CASES USER WOULD BE IDENTIFIED BY BACKEND USING THE FIREBASE ADMIN UID. THE USER ID TOKEN SHOULD BE SENT IN THE BEARER TOKEN IN AUTH HEADER **Acceptance Criteria:** - [ ] `/register` endpoint functional for registering basic details - [ ] `/complete-transaction` endpoint for both payment gateway and manual flow - [ ] Follow the codebase pattern ### Additional Information _No response_

Created: 8/16/2025

<img width="1296" height="705" alt="Image" src="https://github.com/user-attachments/assets/d4364a0a-af24-4d54-9fcd-e3088a51e0fe" /> When you don't have any codes, it shows two buttons to add codes. It would be better if there only was one. Prefferably, the one at the top is removed if there are no codes. Otherwise, it stays there.

Created: 8/16/2025 • 1 comments

Created: 8/16/2025

Description: Currently, the navbar and footer only show limited links (Product, Company, Resources, Legal). The About Us and Blog links are listed in the footer, but they don’t actually lead to dedicated pages. Proposed Improvements: Create dedicated pages: about page → Include mission, vision, team details. blog page → List latest updates, articles, and announcements. Update Navbar: Add "About Us" and "Blog" as main navigation items so users can access them quickly. Link Footer Items: Ensure the footer About Us and Blog entries point to these new pages instead of placeholders (#). Consistency: Keep navbar and footer styling consistent with the rest of the site (dark mode toggle, hover effects, spacing). Why: Improves navigation and accessibility. Highlights company identity (About Us) and keeps users engaged with fresh content (Blog). Ensures footer links are not dead ends.

Created: 8/16/2025 • 2 comments

Auto-generated by Monsterrr.

Created: 8/16/2025

Auto-generated by Monsterrr.

Created: 8/16/2025

Auto-generated by Monsterrr.

Created: 8/16/2025

Add LED support to longhorn lib for boards. There should be an init to make sure that the PWM and HTIM timers are all set up. There should be another function that accepts a delta time (in milliseconds) and updates the new RGB values.

Created: 8/16/2025

## 🏪 Restaurant Dashboard Feature ### 📝 Description Build a comprehensive restaurant dashboard for restaurant owners to manage their surplus food inventory, orders, and business analytics. This is a core feature that enables restaurants to participate in the Surplus Supper marketplace. ### 🎯 Goals - [ ] Restaurant registration and authentication system - [ ] Restaurant profile management (name, address, cuisine type, hours) - [ ] Inventory management (add/edit/delete surplus food items) - [ ] Order management and tracking system - [ ] Analytics dashboard (sales, popular items, waste reduction) - [ ] Real-time notifications for new orders - [ ] Responsive dashboard UI/UX ### 🛠️ Technical Requirements #### Backend (Go) - **Restaurant Service**: Business logic for restaurant operations - **API Endpoints**: - `POST /api/restaurant/register` - Restaurant registration - `POST /api/restaurant/login` - Restaurant authentication - `GET /api/restaurant/profile` - Get restaurant profile - `PUT /api/restaurant/profile` - Update restaurant profile - `GET /api/restaurant/inventory` - Get inventory items - `POST /api/restaurant/inventory` - Add inventory item - `PUT /api/restaurant/inventory/:id` - Update inventory item - `DELETE /api/restaurant/inventory/:id` - Delete inventory item - `GET /api/restaurant/orders` - Get restaurant orders - `PUT /api/restaurant/orders/:id/status` - Update order status #### Frontend (Next.js) - **Dashboard Layout**: Responsive sidebar navigation - **Authentication**: Restaurant login/register forms - **Inventory Management**: CRUD operations for food items - **Order Management**: View and manage incoming orders - **Analytics**: Charts and reports for business insights - **Profile Management**: Restaurant information editing #### Database Schema ```sql -- Restaurants table CREATE TABLE restaurants ( id SERIAL PRIMARY KEY, name VARCHAR(255) NOT NULL, email VARCHAR(255) UNIQUE NOT NULL, password_hash VARCHAR(255) NOT NULL, address TEXT, latitude DECIMAL(10, 8), longitude DECIMAL(11, 8), cuisine_type VARCHAR(100), phone VARCHAR(20), opening_hours JSONB, created_at TIMESTAMP DEFAULT CURRENT_TIMESTAMP, updated_at TIMESTAMP DEFAULT CURRENT_TIMESTAMP ); -- Inventory items table CREATE TABLE inventory_items ( id SERIAL PRIMARY KEY, restaurant_id INTEGER REFERENCES restaurants(id), name VARCHAR(255) NOT NULL, description TEXT, original_price DECIMAL(10, 2), surplus_price DECIMAL(10, 2), quantity INTEGER DEFAULT 1, category VARCHAR(100), expiry_date TIMESTAMP, image_url VARCHAR(500), is_available BOOLEAN DEFAULT true, created_at TIMESTAMP DEFAULT CURRENT_TIMESTAMP, updated_at TIMESTAMP DEFAULT CURRENT_TIMESTAMP ); ``` ### 📁 Files to Create/Modify #### Backend Files - `backend/restaurantService/restaurant_service.go` - Restaurant business logic - `backend/restaurantService/auth.go` - Restaurant authentication - `backend/api/restaurant/restaurant_handler.go` - Restaurant API handlers - `backend/api/restaurant/inventory_handler.go` - Inventory API handlers - `backend/api/restaurant/order_handler.go` - Order management handlers - `backend/middleware/restaurant_auth.go` - Restaurant authentication middleware - `backend/db/migrations/002_restaurant_schema.sql` - Database migrations #### Frontend Files - `frontend-next/src/components/restaurant/` - Restaurant dashboard components - `frontend-next/src/app/restaurant/` - Restaurant dashboard pages - `frontend-next/src/lib/restaurant.ts` - Restaurant API client - `frontend-next/src/types/restaurant.ts` - Restaurant type definitions ### 🎨 UI/UX Considerations - **Design System**: Follow existing glassmorphism design theme - **Responsive**: Mobile-first design for restaurant staff on mobile devices - **Accessibility**: WCAG 2.1 AA compliance - **Performance**: Fast loading times for inventory management - **User Experience**: Intuitive workflow for adding/managing inventory ### 📋 Acceptance Criteria - [ ] Restaurant owners can register and login to the system - [ ] Restaurant profile can be created and edited - [ ] Inventory items can be added, edited, and deleted - [ ] Orders are displayed in real-time with status updates - [ ] Dashboard shows key metrics (sales, inventory, orders) - [ ] Mobile-responsive design works on all devices - [ ] Proper error handling and validation throughout - [ ] Integration with existing authentication system ### 🏷️ Labels - `enhancement` - `restaurant-dashboard` - `good first issue` - `help wanted` - `backend` - `frontend` - `database` ### 📚 Additional Notes - Should integrate seamlessly with existing user authentication system - Follow existing code patterns and styling conventions - Include comprehensive error handling and input validation - Consider performance implications for real-time features - Implement proper security measures for restaurant data

Created: 8/16/2025

Hello @akathedeveloper, I would like to enhance the health log input form(Add entry) by adding the following improvements: - Dropdown for selecting health log type (e.g., Heart Rate, Blood Pressure, Sugar). - Dynamic unit selection based on the chosen health log type. - Input validation to prevent unrealistic values (e.g., BP should not be 10). Problem: Currently, users have to manually type the log type and unit, which is error-prone and can lead to invalid entries. Benefit: This will make data entry faster, more accurate, and user-friendly by reducing errors. This feature will improve data accuracy and user experience. Could you please assign this to me as part of GSSoC’25? I’d be happy to implement it. Thanks!

Created: 8/16/2025 • 1 comments

Seemingly at random, these special windows are lost to the void and fall behind other ones. Sometimes it works, sometimes it does not. This is a minor issue since these windows can also be selected with the 'safe' right-click as a workaround for now (furthermore they are also not so common in MacOS nowadays).

Created: 8/16/2025 • 1 comments

We have some legacy language at the end of the Operator setup process that is unnecessarily specific to Claude desktop. Hypergrid works with any MCP client. <img width="1160" height="478" alt="Image" src="https://github.com/user-attachments/assets/7dd30d6c-2175-46e9-8e52-d024f6236126" /> Fix: replace all instances of "Claude" or "Claude Desktop" with "your MCP client"

Created: 8/16/2025

1. Minimize app. 2. Focus another app. 3. Click on minimized app via Dock. 4. Experience an ugly flicker for 1 frame before the regular app opening animation occurs.

Created: 8/16/2025

Hello, Right now the left side menu is hidden and only shows if you hover near the logo, so most users won’t discover it. I want to add a small floating menu tab/icon on the left edge (arrow or hamburger + “Menu” label) to clearly open the side panel.

Created: 8/16/2025 • 2 comments

Someone submitted the contact form! **URL**: https://usaco.guide/problems/usaco-1227-photoshoot/solution **Module**: Solution: USACO Bronze 2022 US Open - Photoshoot **Topic**: Mistake **Message**: Hello, I would like to report what I think is a mistake in the solution. The provided solution fails for the following test case: H H H G G H H G H G I believe the correct solution is a minimum of 3 flips (with all of the G's arranged in even-numbered positions): After Flip 1: H G G H H H H G H G After Flip 2: G H G H H H H G H G After Flip 3: H G H G H H H G H G However, the suggested solution code outputs 2. I'm wondering if I'm overlooking some detail in the problem statement. Thank you.

Created: 8/16/2025

Hello @MIHIR2006, As attached in the image below the UI of the Signin/Signup page in light mode needs to be fixed. I would love to fix this issue. <img width="1919" height="872" alt="Image" src="https://github.com/user-attachments/assets/7feafaa5-0428-4448-85ef-c59bb16ae944" />

Created: 8/16/2025 • 2 comments

## Feature Request Add basic Text-to-Speech functionality to convert text into audio files. ### Proposed Method ```php Deepgram::speak()->textToSpeech(string $text, string $outputPath, array $options = []): bool ``` ### Use Case Convert text content into high-quality speech audio files for accessibility, content creation, and voice applications. ### Implementation Notes - Implement basic `src/Api/Speak.php` class - Save audio output to specified file path - Support voice selection and audio format options - Handle file writing with proper error checking - Default to reasonable voice and format settings ### API Documentation 📖 [Deepgram Text-to-Speech API](https://developers.deepgram.com/reference/text-to-speech-api) ### API Endpoint `POST https://api.deepgram.com/v1/speak` ### Basic Usage Example ```php // Convert text to speech and save as audio file $success = Deepgram::speak()->textToSpeech( 'Hello, this is a test message', '/path/to/output.mp3', ['voice' => 'aura-asteria-en'] ); ```

Created: 8/16/2025

## Feature Request Add support for text summarization to the Read API using Deepgram's summarization feature. ### Proposed Methods ```php // For text input Deepgram::read()->summarizeText(string $text, array $options = []): array // For URL input Deepgram::read()->summarizeUrl(string $url, array $options = []): array ``` ### Use Case Generate brief summaries of long text content for content analysis, document processing, and text intelligence applications. ### Implementation Notes - Uses Deepgram's `/v1/read` endpoint with `summarize=true` parameter ### API Documentation 📖 [Deepgram Text Summarization](https://developers.deepgram.com/docs/text-summarization) ### API Endpoint `POST https://api.deepgram.com/v1/read?summarize=true&language=en`

Created: 8/16/2025