Commit History
-
clean up code
63db11a -
fix
7771b05 -
fix code formatting
74052d0 -
update UI for main page
04c818a -
update landing page style
d669273
-
update default
4c3311e -
update
3c247ba -
fix
e6104d9 -
update fix
aa0bba7 -
update
a4a6500 -
optimizations
990c944 -
fix
3e5404a -
update to use grok 4.1 fast
0b126be
-
update landing to show login
27c7a45 -
add landing page
4b29926 -
update ui changes
0423b7b -
fix requirements txt generation
4ceee61 -
more fixes
3bbc203 -
transformers js deploy fix
5d7cc0b -
update
35169fd -
fix
d1b315f -
update
68ff582 -
fix
6de7d1a -
fix transformers js deploy
27ceb47 -
fix login
a0e6952 -
update
89d579c -
new update
d017d01 -
fix
dcd2ebe -
update
106a0d6 -
update
31713bf -
update
4134e29 -
fix deploy
47565e8 -
fix
da59e40
-
update
fe566fd -
update import and deploy
c66426d -
update to 20k
0c30765 -
update import project
53813c1 -
fix import project
ddf45da -
update
25c838a -
add import feature
3eb00a5 -
update gemini to poe
d4d57c4 -
update
d1efd8a -
update gemini
0498411 -
updates
2948440 -
fix gemini 3
fab9ff4 -
add gemini 3
28c44e9 -
Fix transformers.js parser: Support both === and markdown formats
Issue: LLM was generating code with markdown blocks (html, javascript, css) but parser only looked for === filename === format Fixes: 1. Updated TRANSFORMERS_JS_SYSTEM_PROMPT to specify === format explicitly - Added clear examples showing === index.html ===, === index.js ===, === style.css === - Explicitly stated NOT to use markdown code blocks 2. Enhanced parse_transformers_js_output() with fallback logic: - Primary: Parse === filename === sections - Fallback: Parse markdown code blocks (html, javascript, css) - Last resort: Try single HTML file extraction - Removes placeholder comments from extracted content This ensures backward compatibility with already-generated code while guiding future generations to use the correct format.f5a9d8a -
Fix transformers.js deployment: Use space name not repo_id for duplicate_space()
Issue: 500 error when deploying transformers.js apps Root cause: duplicate_space() was receiving 'username/space-name' but expects just 'space-name' Key fix in backend_deploy.py: - Changed: duplicate_space(to_id=repo_id, ...) - To: duplicate_space(to_id=space_name, ...) The huggingface_hub duplicate_space() function automatically prepends the username from the token, so it expects just the space name, not the full repo_id format. Additional improvements: 1. Better error handling and logging for transformers.js parsing 2. Added detailed print statements to track duplication process 3. Match original deploy.py validation logic exactly: - Use dict access (files['index.html']) instead of .get() - Check all three files with 'or' conditions 4. Added traceback printing for easier debugging Error flow now matches original: 1. Parse transformers.js output → extract 3 files 2. Validate all 3 files exist (KeyError if missing) 3. Write files to temp directory 4. Duplicate template space …1230bba -
Fix React and Streamlit deployment: Upload files individually like transformers.js
Issue: React and Streamlit apps were using upload_folder() which doesn't match the original deploy.py behavior, potentially causing issues with multi-file apps. Root cause analysis from original deploy.py: - Transformers.js: Individual file uploads ✅ (already fixed) - React: Individual file uploads ❌ (was using upload_folder) - Streamlit: Individual file uploads ❌ (was using upload_folder) - HTML (static): upload_folder() for multi-file OR upload_file() for single - Gradio: create_commit() with atomic ops for multi-file OR upload_file() Changes to backend_deploy.py: 1. React deployment now uses individual uploads: - Set use_individual_uploads = True for React apps - Parses React output to get all files - Uploads each file individually with retry logic - Includes Dockerfile if missing (from template) 2. Streamlit deployment now uses individual uploads: - Set use_individual_uploads = True for Streamlit (Docker mode) - Uploads each file individually with retry logic …a47f768 -
Fix transformers.js deployment: Upload all files (html, js, css) individually
Issue: Transformers.js apps were not deploying correctly - CSS and JavaScript files were missing from the deployed space. Root cause: backend_deploy.py was using upload_folder() for all file types, but transformers.js requires individual file uploads like the original deploy.py. Changes to backend_deploy.py: 1. Added validation for transformers.js files: - Check all three files exist (index.html, index.js, style.css) - Return error if any file is missing 2. Template space duplication (NEW): - Use duplicate_space() from static-templates/transformers.js template - Matches original deploy.py behavior - Falls back to create_repo() if duplication fails 3. Individual file upload for transformers.js: - Added use_individual_uploads flag - Upload each file separately using api.upload_file() - NOT using upload_folder() for transformers.js 4. Retry logic with error handling: - 3 attempts per file - 2-second delay between retries - Proper permission error det…1e9598c