You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by GitBox <gi...@apache.org> on 2021/11/12 21:02:43 UTC
[GitHub] [airflow] karakanb opened a new issue #19566: Breeze - The CSS and JS files are not built
karakanb opened a new issue #19566:
URL: https://github.com/apache/airflow/issues/19566
### Describe the issue with documentation
I followed the documentation about running Breeze to develop locally. I have set up the database properly, and all the containers are properly starting with Breeze. I am on a Macbook Pro 13-inch, 2020. This machine has 16GB RAM, and I have allocated 6GB RAM and 3CPUs to the Docker VM. I am using Docker for all my development work, so I am familiar with it.
The final view I get is here:
<img width="1440" alt="image" src="https://user-images.githubusercontent.com/16530606/141528323-2b6327b1-af38-400f-8980-9bc94fa2222b.png">
The `yarn` step on the top right takes ~630 seconds on my machine, I guess a lot of it comes from the fact that the Docker networking is pretty bad on macOS due to the VM.
Anyway, when I go to `localhost:28080`, I am getting a lot of 404s with CSS and JS files.
<img width="1440" alt="image" src="https://user-images.githubusercontent.com/16530606/141528396-5036f017-1281-4be4-aade-acc82d0627ab.png">
Obviously, this breaks the UI. While going through the logs, I notice that there's a notice there:
```
WARNING: It seems that the generated assets files do not match the content of the sources
```
Okay, cool. I stop the Breeze environment, run the command `./airflow/www/compile_assets.sh` and I have my assets generated quite quickly for me, nice. I start Breeze again. The logs don't complain about the assets not matching.
There's a weird problem now:
- The yarn command takes a long time, and that's fine.
- While waiting for that to finish, refreshing the page makes everything look fine.
- Although some icons are not loading, and the multi-select tags like the ones in the role create UI are not working, and there are still 404s in the network tab.
- I wait until the yarn command finishes.
- The UI is back to being completely broken.
I presume there's something wrong with the yarn command that breaks the assets.
One of the files that seems to be missing is a file called `ab.js`. I am searching my airflow folder for that to find a file with that name using `find . -name 'ab.js'`, but nothing matches.
On the top left corner, I try to recompile the assets, this time inside the container, using the command `./airflow/www/compile_assets.sh`. This command takes ~80 seconds, and finishes. Now when I refresh the UI, it is partially back again:
<img width="1440" alt="image" src="https://user-images.githubusercontent.com/16530606/141531523-650fdd17-742b-4ba0-891a-369304f37145.png">
At this point, I have no clue about what to fix or how to fix.
### How to solve the problem
- I think the documentation has wrong levels of titles that makes it confusing to know what steps are alternatives to each other, and what are "must do" steps.
- Docker Compose and pyenv are stated as alternatives to each other in "Note to Starters" section of the Contributers Quick Start guide, but then the prerequisites section for Ubuntu tells them in order as if both are required.
- It might be the case that pyenv is still required for Docker-based setup, and that's also fine, but it is not clear if I have to do that, so I skipped that because I assumed everything regarding Airflow and its dependencies would be covered by Docker containers instead of having a local environment.
- Similarly, the same document is instructing to install `jq` without any usage of it. I agree that jq is an amazing tool and a must-have for many people, but if it is not relevant for this setup, why have it?
- It might be the case that the installation script or Breeze requires it for some reason, but it'd be good to see this mentioned.
- Also, if Breeze depends on it, why does it not check if it exists, just like it checks for Docker versions?
- The quick start guide has pretty similar steps for VS Code and PyCharm separately, which makes the document confusing.
- I love the fact that there are specific instructions for both of the IDEs in the document, but are they really relevant for setting up the environment?
- I think the primary focus of the document should be to get a contributor having their first local change and being able to see it over localhost.
- Once this is achieved, the suggestions and instructions for each IDE could focus on improving the developer ergonomics.
- As simple as it is, as a new contributor, I should be able to run Breeze, pick up `vim` or `nano` or whatever editor I want, edit an HTML file or a Python file somewhere, and immediately see the result of this in my browser over localhost.
- After this, I'd obviously love to see what debugging opportunities does VS Code or PyCharm offer, but not before I have stuff running.
- Also, the same confusion about Docker vs pyenv continues under these sections as well.
- For example, why does the section on VS Code have a subsection titled as "Installing airflow in the local virtual environment airflow-env with breeze."?
- At this point, I have my containers running, and all the commands on the container have completed successfully, but there are still some assets missing in my setup.
- Did I need to run something else?
### Anything else
Maintaining a project sometimes makes it harder to notice what are the things the new joiners might be going through, therefore I wanted to share my findings as a first-time contributor so that maybe we can identify areas for improvement. Once I have my environment working locally, I would love to contribute to the documentation with my findings. I appreciate all the docs there so far, and I acknowledge that the fact that I couldn't get this to work is probably because I missed some step somewhere or made a mistake down the line, but I'd also like to make it as foolproof as possible so that someone like me could still make it work and hopefully contribute to Airflow.
### Are you willing to submit PR?
- [X] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] potiuk commented on issue #19566: Breeze - The CSS and JS files are not built
Posted by GitBox <gi...@apache.org>.
potiuk commented on issue #19566:
URL: https://github.com/apache/airflow/issues/19566#issuecomment-971425628
This is likely setting of your browser, not the asset compilation
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] potiuk commented on issue #19566: Breeze - The CSS and JS files are not built
Posted by GitBox <gi...@apache.org>.
potiuk commented on issue #19566:
URL: https://github.com/apache/airflow/issues/19566#issuecomment-971418386
Well that page looks pretty complete. What's wrong with it?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] socar-grab commented on issue #19566: Breeze - The CSS and JS files are not built
Posted by GitBox <gi...@apache.org>.
socar-grab commented on issue #19566:
URL: https://github.com/apache/airflow/issues/19566#issuecomment-971411339
I have a same problem after pulling @potiuk 's merged commit.
I tried `./airflow/www/compile_assets.sh` in root directory and `./breeze start-airflow `
but I could show uncompleted page like below
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] potiuk commented on issue #19566: Breeze - The CSS and JS files are not built
Posted by GitBox <gi...@apache.org>.
potiuk commented on issue #19566:
URL: https://github.com/apache/airflow/issues/19566#issuecomment-971421994
> I believe you need to run compile_assets.sh in the container, not outside.
BTW. Both should work the same if you have the same node/yarn installed in host
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] potiuk edited a comment on issue #19566: Breeze - The CSS and JS files are not built
Posted by GitBox <gi...@apache.org>.
potiuk edited a comment on issue #19566:
URL: https://github.com/apache/airflow/issues/19566#issuecomment-968130873
Autem let's treat it as 'umbrella issue' and simply mention 'Relafed to: #issue_number' in PRs
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] potiuk commented on issue #19566: Breeze - The CSS and JS files are not built
Posted by GitBox <gi...@apache.org>.
potiuk commented on issue #19566:
URL: https://github.com/apache/airflow/issues/19566#issuecomment-971433660
But that has nothing to do with asset compilation
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] potiuk commented on issue #19566: Breeze - The CSS and JS files are not built
Posted by GitBox <gi...@apache.org>.
potiuk commented on issue #19566:
URL: https://github.com/apache/airflow/issues/19566#issuecomment-970582152
@karakanb @nshetty15 I reproduced the "static assets" case on a completely fresh install. The problem is that when you start it first without building the assets, the `webserver` in start-airflow will start before the assets are ready and will not re-read them again. I will fix it shortly but in order to fix the assets, you need to simply enter `breeze` once without the `start-airflow` and run the asset generation.
Then it should work.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] potiuk removed a comment on issue #19566: Breeze - The CSS and JS files are not built
Posted by GitBox <gi...@apache.org>.
potiuk removed a comment on issue #19566:
URL: https://github.com/apache/airflow/issues/19566#issuecomment-968105332
One more thing I missed:
> Also, if Breeze depends on it, why does it not check if it exists, just like it checks for Docker versions?
Excellent Idea! PR please!
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] potiuk commented on issue #19566: Breeze - The CSS and JS files are not built
Posted by GitBox <gi...@apache.org>.
potiuk commented on issue #19566:
URL: https://github.com/apache/airflow/issues/19566#issuecomment-971584198
It REALLY helps if issues are separated rather than one huge thread with big number of those - in the issue here you have many, many things raised and when someone mentions that the problem is solved, it might mean that only 1 of the 20 things mentioned in the thread is solved.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] karakanb commented on issue #19566: Breeze - The CSS and JS files are not built
Posted by GitBox <gi...@apache.org>.
karakanb commented on issue #19566:
URL: https://github.com/apache/airflow/issues/19566#issuecomment-971585746
Understood, makes total sense. I have created the issue here: https://github.com/apache/airflow/issues/19647
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] kaxil commented on issue #19566: Breeze - The CSS and JS files are not built
Posted by GitBox <gi...@apache.org>.
kaxil commented on issue #19566:
URL: https://github.com/apache/airflow/issues/19566#issuecomment-967732200
I think this error / delay is common among Mac users.
If this happens, I have generally run `./airflow/www/compile_assets.sh` from the repo root. See if that works for you.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] karakanb edited a comment on issue #19566: Breeze - The CSS and JS files are not built
Posted by GitBox <gi...@apache.org>.
karakanb edited a comment on issue #19566:
URL: https://github.com/apache/airflow/issues/19566#issuecomment-971422523
I think the box in the middle is supposed to be the JS-powered search bar, and when the JS doesn't load it looks like that plain HTML box.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] uranusjr commented on issue #19566: Breeze - The CSS and JS files are not built
Posted by GitBox <gi...@apache.org>.
uranusjr commented on issue #19566:
URL: https://github.com/apache/airflow/issues/19566#issuecomment-971416343
> I tried `./airflow/www/compile_assets.sh` in root directory and `./breeze start-airflow `
I believe you need to run `compile_assets.sh` in the container, not outside.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] karakanb commented on issue #19566: Breeze - The CSS and JS files are not built
Posted by GitBox <gi...@apache.org>.
karakanb commented on issue #19566:
URL: https://github.com/apache/airflow/issues/19566#issuecomment-971422523
I think the box in the middle is supposed to be the JS-powered search bar, and when the JS doesn't load it looks like that plan HTML box.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] potiuk commented on issue #19566: Breeze - The CSS and JS files are not built
Posted by GitBox <gi...@apache.org>.
potiuk commented on issue #19566:
URL: https://github.com/apache/airflow/issues/19566#issuecomment-971427541
Cleaning the cache, trying different browser, entering incognito mode should help you to debug it.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] karakanb commented on issue #19566: Breeze - The CSS and JS files are not built
Posted by GitBox <gi...@apache.org>.
karakanb commented on issue #19566:
URL: https://github.com/apache/airflow/issues/19566#issuecomment-968123807
Hi @potiuk, thanks a lot for getting back to me, I really appreciate the detailed response. Once I figure out how to fix some of the issues on my own local and make sure I have a functioning environment I'd love to contribute back in the form of documentation. I will keep all your suggestions in mind and will have small PRs, which should be easier to review and align on hopefully.
About the specific issues in my environment, I will try to go through everything from scratch later and see if it helps. If it doesn't, I'll try to share my findings here. Therefore, if that's okay, I'd like to keep this issue open, or at least be able to still use it to find a solution to this that can maybe be turned into a PR, what do you think?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] potiuk commented on issue #19566: Breeze - The CSS and JS files are not built
Posted by GitBox <gi...@apache.org>.
potiuk commented on issue #19566:
URL: https://github.com/apache/airflow/issues/19566#issuecomment-968105330
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] potiuk commented on issue #19566: Breeze - The CSS and JS files are not built
Posted by GitBox <gi...@apache.org>.
potiuk commented on issue #19566:
URL: https://github.com/apache/airflow/issues/19566#issuecomment-970615858
Fix to the "asset race condition" added in https://github.com/apache/airflow/issues/19566
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] potiuk commented on issue #19566: Breeze - The CSS and JS files are not built
Posted by GitBox <gi...@apache.org>.
potiuk commented on issue #19566:
URL: https://github.com/apache/airflow/issues/19566#issuecomment-968130873
Autem let's treat it as 'umbrella issue' and simply mention 'Relafed to: #pr_number'
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] boring-cyborg[bot] commented on issue #19566: Breeze - The CSS and JS files are not built
Posted by GitBox <gi...@apache.org>.
boring-cyborg[bot] commented on issue #19566:
URL: https://github.com/apache/airflow/issues/19566#issuecomment-967549963
Thanks for opening your first issue here! Be sure to follow the issue template!
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] potiuk commented on issue #19566: Breeze - The CSS and JS files are not built
Posted by GitBox <gi...@apache.org>.
potiuk commented on issue #19566:
URL: https://github.com/apache/airflow/issues/19566#issuecomment-970590648
And with the next restarts there is a race condition - if the `yarn dev` build is not fast enough, webserver will start while the dist folder is still empty. I think runing yarn dev by default was a mistake.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] karakanb commented on issue #19566: Breeze - The CSS and JS files are not built
Posted by GitBox <gi...@apache.org>.
karakanb commented on issue #19566:
URL: https://github.com/apache/airflow/issues/19566#issuecomment-971478124
I have pulled the latest version last night but that doesn't seem to fix the issue, neither by local pyenv nor by Docker.
I cannot copy separate logs from tmux, iTerm doesn't seem to allow that, but I can show the logs from the boot process of the breeze env:
```
Good version of docker 20.10.8.
f321cbfd33eeb8db8effc8f9bc4c3d5317758927da26abeb4c08b14fad09ff6b
f321cbfd33eeb8db8effc8f9bc4c3d5317758927da26abeb4c08b14fad09ff6b
No need to pull the image. Yours and remote cache hashes are the same!
The CI image for Python python:3.8-slim-buster image likely needs to be rebuild
The files were modified since last build: setup.py setup.cfg Dockerfile.ci .dockerignore scripts/docker/compile_www_assets.sh scripts/docker/common.sh scripts/docker/install_additional_dependencies.sh scripts/docker/install_airflow.sh scripts/docker/install_airflow_dependencies_from_branch_tip.sh scripts/docker/install_from_docker_context_files.sh scripts/docker/install_mysql.sh airflow/www/package.json airflow/www/yarn.lock airflow/www/webpack.config.js airflow/ui/package.json airflow/ui/yarn.lock
WARNING!!!!:Make sure that you rebased to latest upstream before rebuilding or the rebuild might take a lot of time!
Please confirm pull and rebuild image CI-python3.8 (or wait 4 seconds to skip it). Are you sure? [y/N/q]
The answer is 'no'. Skipping pull and rebuild image CI-python3.8.
@&&&&&&@
@&&&&&&&&&&&@
&&&&&&&&&&&&&&&&
&&&&&&&&&&
&&&&&&&
&&&&&&&
@@@@@@@@@@@@@@@@ &&&&&&
@&&&&&&&&&&&&&&&&&&&&&&&&&&
&&&&&&&&&&&&&&&&&&&&&&&&&&&&
&&&&&&&&&&&&
&&&&&&&&&
&&&&&&&&&&&&
@@&&&&&&&&&&&&&&&@
@&&&&&&&&&&&&&&&&&&&&&&&&&&&& &&&&&&
&&&&&&&&&&&&&&&&&&&&&&&&&&&& &&&&&&
&&&&&&&&&&&&&&&&&&&&&&&& &&&&&&
&&&&&&
&&&&&&&
@&&&&&&&&
@&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&
&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&
&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&
@&&&@ && @&&&&&&&&&&& &&&&&&&&&&&& && &&&&&&&&&& &&& &&& &&&
&&& &&& && @&& &&& && && &&& &&&@ &&& &&&&& &&&
&&& &&& && @&&&&&&&&&&&& &&&&&&&&&&& && && &&& &&& &&& &&@ &&&
&&&&&&&&&&& && @&&&&&&&&& && && &&@ &&& &&@&& &&@&&
&&& &&& && @&& &&&@ && &&&&&&&&&&& &&&&&&&&&&&& &&&& &&&&
&&&&&&&&&&&& &&&&&&&&&&&& &&&&&&&&&&&@ &&&&&&&&&&&& &&&&&&&&&&& &&&&&&&&&&&
&&& &&& && &&& && &&& &&&& &&
&&&&&&&&&&&&@ &&&&&&&&&&&& &&&&&&&&&&& &&&&&&&&&&& &&&& &&&&&&&&&&
&&& && && &&&& && &&& &&&& &&
&&&&&&&&&&&&& && &&&&@ &&&&&&&&&&&@ &&&&&&&&&&&& @&&&&&&&&&&& &&&&&&&&&&&
Use CI image.
Branch name: main
Docker image: ghcr.io/apache/airflow/main/ci/python3.8:latest
Airflow source version: 2.3.0.dev0
Python version: 3.8
Backend: mysql 5.7
####################################################################################################
Airflow Breeze CHEATSHEET
####################################################################################################
Adding breeze to your path:
When you exit the environment, you can add sources of Airflow to the path - you can
run breeze or the scripts above from any directory by calling 'breeze' commands directly
export PATH=${PATH}:"/Users/burakkarakan/Code/anything-else/airflow"
####################################################################################################
Port forwarding:
Ports are forwarded to the running docker containers for webserver and database
* 12322 -> forwarded to Airflow ssh server -> airflow:22
* 28080 -> forwarded to Airflow webserver -> airflow:8080
* 25555 -> forwarded to Flower dashboard -> airflow:5555
* 25433 -> forwarded to Postgres database -> postgres:5432
* 23306 -> forwarded to MySQL database -> mysql:3306
* 21433 -> forwarded to MSSQL database -> mssql:1443
* 26379 -> forwarded to Redis broker -> redis:6379
Here are links to those services that you can use on host:
* ssh connection for remote debugging: ssh -p 12322 airflow@127.0.0.1 pw: airflow
* Webserver: http://127.0.0.1:28080
* Flower: http://127.0.0.1:25555
* Postgres: jdbc:postgresql://127.0.0.1:25433/airflow?user=postgres&password=airflow
* Mysql: jdbc:mysql://127.0.0.1:23306/airflow?user=root
* Redis: redis://127.0.0.1:26379/0
####################################################################################################
You can setup autocomplete by running 'breeze setup-autocomplete'
####################################################################################################
You can toggle ascii/cheatsheet by running:
* breeze toggle-suppress-cheatsheet
* breeze toggle-suppress-asciiart
####################################################################################################
Checking resources.
* Memory available 5.9G. OK.
* CPUs available 3. OK.
WARNING!!!: Not enough Disk space available for Docker.
At least 40 GBs recommended. You have 28G
WARNING!!!: You have not enough resources to run Airflow (see above)!
Please follow the instructions to increase amount of resources available:
Please check https://github.com/apache/airflow/blob/main/BREEZE.rst#resources-required for details
Good version of docker-compose: 1.29.2
WARNING: The ENABLE_TEST_COVERAGE variable is not set. Defaulting to a blank string.
Creating network "docker-compose_default" with the default driver
Creating volume "docker-compose_sqlite-db-volume" with default driver
Creating volume "docker-compose_postgres-db-volume" with default driver
Creating volume "docker-compose_mysql-db-volume" with default driver
Creating volume "docker-compose_mssql-db-volume" with default driver
Creating docker-compose_mysql_1 ... done
Creating docker-compose_airflow_run ... done
Airflow home: /root/airflow
Airflow sources: /opt/airflow
Airflow core SQL connection: mysql://root@mysql/airflow?charset=utf8mb4
Using already installed airflow version
No need for www assets recompilation.
===============================================================================================
Checking integrations and backends
===============================================================================================
MySQL: OK.
-----------------------------------------------------------------------------------------------
-----------------------------------------------------------------------------------------------
Starting Airflow
Your dags for webserver and scheduler are read from /files/dags directory
which is mounted from your <AIRFLOW_SOURCES>/files/dags folder
You can add /files/airflow-breeze-config directory and place variables.env
In it to make breeze source the variables automatically for you
You can add /files/airflow-breeze-config directory and place .tmux.conf
in it to make breeze use your local .tmux.conf for tmux
```
The logs say `No need for www assets recompilation.` which signals that the assets are already up-to-date. However, when I visit the page, the files are not there:
<img width="687" alt="image" src="https://user-images.githubusercontent.com/16530606/142189803-92dc5e9f-c940-4272-98a1-e5845344b62d.png">
- When I search the whole directory with `find . -name 'ab_filters.js'`, there's no file, which means the issue is not with the browser cache.
- Just in case there was another race condition, I ran the following command again to see if it'd generate the file for some reason: `./breeze initialize-local-virtualenv --python 3.8` but the result of the `find . -name 'ab_filters.js' ` is still empty.
- Then I ran `./airflow/www/compile_assets.sh` but that didn't make a difference as well, `find` is still empty.
Here's the output from the `compile_assets.sh`:
```
❯ ./airflow/www/compile_assets.sh
yarn install v1.22.17
[1/4] 🔍 Resolving packages...
success Already up-to-date.
✨ Done in 0.56s.
yarn run v1.22.17
$ NODE_ENV=production webpack --colors --progress
23% building 26/39 modules 13 active ...www/node_modules/babel-loader/lib/index.js??ref--5!/Users/burakkarakan/Code/anything-else/airflow/airflow/www/static/js/datetime_utils.jspostcss-modules-values: postcss.plugin was deprecated. Migration guide:
https://evilmartians.com/chronicles/postcss-8-plugin-migration
postcss-modules-local-by-default: postcss.plugin was deprecated. Migration guide:
https://evilmartians.com/chronicles/postcss-8-plugin-migration
modules-extract-imports: postcss.plugin was deprecated. Migration guide:
https://evilmartians.com/chronicles/postcss-8-plugin-migration
postcss-modules-scope: postcss.plugin was deprecated. Migration guide:
https://evilmartians.com/chronicles/postcss-8-plugin-migration
postcss-import-parser: postcss.plugin was deprecated. Migration guide:
https://evilmartians.com/chronicles/postcss-8-plugin-migration
postcss-icss-parser: postcss.plugin was deprecated. Migration guide:
https://evilmartians.com/chronicles/postcss-8-plugin-migration
postcss-url-parser: postcss.plugin was deprecated. Migration guide:
https://evilmartians.com/chronicles/postcss-8-plugin-migration
Hash: c303806b9efab4bf5dec
Version: webpack 4.44.2
Time: 4583ms
Built at: 11/17/2021 11:13:58 AM
Asset Size Chunks Chunk Names
../../../../licenses/LICENSES-ui.txt 52.8 KiB [emitted]
airflowDefaultTheme.9ef6a9e2f0de25c0b346.css 102 KiB 0 [emitted] [immutable] airflowDefaultTheme
airflowDefaultTheme.9ef6a9e2f0de25c0b346.js 4.15 KiB 0 [emitted] [immutable] airflowDefaultTheme
bootstrap-datetimepicker.min.css 7.54 KiB [emitted]
bootstrap-datetimepicker.min.js 37.1 KiB [emitted]
bootstrap3-typeahead.min.js 10 KiB [emitted]
calendar.5260e8f126017610ad73.css 1.06 KiB 1 [emitted] [immutable] calendar
calendar.5260e8f126017610ad73.js 15.4 KiB 1 [emitted] [immutable] calendar
codemirror.css 5.79 KiB [emitted]
codemirror.js 389 KiB [emitted] [big]
coffeescript-lint.js 1.43 KiB [emitted]
connectionForm.be3bf4692736d58cfdb0.js 12.8 KiB 2 [emitted] [immutable] connectionForm
css-lint.js 1.28 KiB [emitted]
d3-shape.min.js 29.1 KiB [emitted]
d3-tip.js 8.99 KiB [emitted]
d3.min.js 148 KiB [emitted]
dag.c0b8852bb690f83bb55e.js 20.4 KiB 3 [emitted] [immutable] dag
dagCode.98dce599559f03115f1f.js 6.48 KiB 4 [emitted] [immutable] dagCode
dagDependencies.c2cdb377b2d3b7be7d1b.js 10.4 KiB 5 [emitted] [immutable] dagDependencies
dagre-d3.core.min.js 27.5 KiB [emitted]
dagre-d3.core.min.js.map 26.3 KiB [emitted]
dagre-d3.min.js 708 KiB [emitted] [big]
dagre-d3.min.js.map 653 KiB [emitted] [big]
dags.0ca53db014891875da7d.css 2.59 KiB 6, 3, 18 [emitted] [immutable] dags
dags.0ca53db014891875da7d.js 45.9 KiB 6, 3, 18 [emitted] [immutable] dags
dataTables.bootstrap.min.css 4.13 KiB [emitted]
dataTables.bootstrap.min.js 1.93 KiB [emitted]
durationChart.ca520df04ff71dd5fab9.js 5.11 KiB 7 [emitted] [immutable] durationChart
flash.ab8296a74435427f9b53.css 1.36 KiB 8 [emitted] [immutable] flash
flash.ab8296a74435427f9b53.js 4.12 KiB 8 [emitted] [immutable] flash
gantt.d7989000350b53dc0855.css 1.1 KiB 9, 3, 18 [emitted] [immutable] gantt
gantt.d7989000350b53dc0855.js 42 KiB 9, 3, 18 [emitted] [immutable] gantt
graph.eaba1e30424750441353.css 2.37 KiB 10, 3, 18 [emitted] [immutable] graph
graph.eaba1e30424750441353.js 55.5 KiB 10, 3, 18 [emitted] [immutable] graph
html-lint.js 1.94 KiB [emitted]
ie.fc8f40153cdecb7eb0b3.js 16.4 KiB 11 [emitted] [immutable] ie
javascript-lint.js 2.11 KiB [emitted]
javascript.js 37.9 KiB [emitted]
jquery.dataTables.min.js 81.6 KiB [emitted]
jshint.js 1.22 MiB [emitted] [big]
json-lint.js 1.3 KiB [emitted]
lint.css 2.55 KiB [emitted]
lint.js 8.91 KiB [emitted]
loadingDots.e4fbfc09969e91db1f49.css 1.21 KiB 12 [emitted] [immutable] loadingDots
loadingDots.e4fbfc09969e91db1f49.js 4.13 KiB 12 [emitted] [immutable] loadingDots
main.216f001f0b6da7966a9f.css 6.85 KiB 13 [emitted] [immutable] main
main.216f001f0b6da7966a9f.js 16.4 KiB 13 [emitted] [immutable] main
manifest.json 3.31 KiB [emitted]
materialIcons.e368f72fd0a7e9a40455.css 109 KiB 14 [emitted] [immutable] materialIcons
materialIcons.e368f72fd0a7e9a40455.js 4.13 KiB 14 [emitted] [immutable] materialIcons
moment.f2be510679d38b9c54e9.js 377 KiB 15 [emitted] [immutable] [big] moment
nv.d3.min.css 8.13 KiB [emitted]
nv.d3.min.css.map 3.59 KiB [emitted]
nv.d3.min.js 247 KiB [emitted] [big]
nv.d3.min.js.map 1.86 MiB [emitted] [big]
oss-licenses.json 66.3 KiB [emitted]
redoc.standalone.js 970 KiB [emitted] [big]
redoc.standalone.js.LICENSE.txt 2.75 KiB [emitted]
redoc.standalone.js.map 3.23 MiB [emitted] [big]
switch.3e30e60646cdea5e4216.css 2.04 KiB 16 [emitted] [immutable] switch
switch.3e30e60646cdea5e4216.js 4.12 KiB 16 [emitted] [immutable] switch
task.8082a6cd3c389845ca0c.js 5.33 KiB 17 [emitted] [immutable] task
taskInstances.d758e4920a32ca069541.js 33.1 KiB 18, 3 [emitted] [immutable] taskInstances
tiLog.fc2c3580403a943ccddb.js 23.8 KiB 19 [emitted] [immutable] tiLog
tree.57c43dd706cbd3d74ef9.css 1.31 KiB 20, 3 [emitted] [immutable] tree
tree.57c43dd706cbd3d74ef9.js 1.48 MiB 20, 3 [emitted] [immutable] [big] tree
trigger.57a3ebbaee0f22bd5022.js 5.03 KiB 21 [emitted] [immutable] trigger
variableEdit.45c5312f076fbe019680.js 4.97 KiB 22 [emitted] [immutable] variableEdit
yaml-lint.js 1.23 KiB [emitted]
Entrypoint airflowDefaultTheme = airflowDefaultTheme.9ef6a9e2f0de25c0b346.css airflowDefaultTheme.9ef6a9e2f0de25c0b346.js
Entrypoint connectionForm = connectionForm.be3bf4692736d58cfdb0.js
Entrypoint dag = dag.c0b8852bb690f83bb55e.js
Entrypoint dagCode = dagCode.98dce599559f03115f1f.js
Entrypoint dagDependencies = dagDependencies.c2cdb377b2d3b7be7d1b.js
Entrypoint dags = dags.0ca53db014891875da7d.css dags.0ca53db014891875da7d.js
Entrypoint flash = flash.ab8296a74435427f9b53.css flash.ab8296a74435427f9b53.js
Entrypoint gantt = gantt.d7989000350b53dc0855.css gantt.d7989000350b53dc0855.js
Entrypoint graph = graph.eaba1e30424750441353.css graph.eaba1e30424750441353.js
Entrypoint ie = ie.fc8f40153cdecb7eb0b3.js
Entrypoint loadingDots = loadingDots.e4fbfc09969e91db1f49.css loadingDots.e4fbfc09969e91db1f49.js
Entrypoint main = main.216f001f0b6da7966a9f.css main.216f001f0b6da7966a9f.js
Entrypoint materialIcons = materialIcons.e368f72fd0a7e9a40455.css materialIcons.e368f72fd0a7e9a40455.js
Entrypoint moment [big] = moment.f2be510679d38b9c54e9.js
Entrypoint switch = switch.3e30e60646cdea5e4216.css switch.3e30e60646cdea5e4216.js
Entrypoint task = task.8082a6cd3c389845ca0c.js
Entrypoint taskInstances = taskInstances.d758e4920a32ca069541.js
Entrypoint tiLog = tiLog.fc2c3580403a943ccddb.js
Entrypoint tree [big] = tree.57c43dd706cbd3d74ef9.css tree.57c43dd706cbd3d74ef9.js
Entrypoint calendar = calendar.5260e8f126017610ad73.css calendar.5260e8f126017610ad73.js
Entrypoint durationChart = durationChart.ca520df04ff71dd5fab9.js
Entrypoint trigger = trigger.57a3ebbaee0f22bd5022.js
Entrypoint variableEdit = variableEdit.45c5312f076fbe019680.js
[8] ./static/js/dag.js 8.77 KiB {3} {6} {9} {10} {18} {20} [built]
[16] ./static/js/task_instances.js 4.54 KiB {6} {9} {10} {18} [built]
[69] ./static/css/bootstrap-theme.css 50 bytes {0} [built]
[70] ./static/js/connection_form.js 7.35 KiB {2} [built]
[71] ./static/js/dag_code.js 1.09 KiB {4} [built]
[72] ./static/js/dag_dependencies.js 6.39 KiB {5} [built]
[73] multi ./static/css/dags.css ./static/js/dags.js 40 bytes {6} [built]
[76] ./static/css/flash.css 50 bytes {8} [built]
[77] multi ./static/css/gantt.css ./static/js/gantt.js 40 bytes {9} [built]
[80] multi ./static/css/graph.css ./static/js/graph.js 40 bytes {10} [built]
[83] ./static/js/ie.js 887 bytes {11} [built]
[85] ./static/css/loading-dots.css 50 bytes {12} [built]
[86] multi ./static/css/main.css ./static/js/main.js 40 bytes {13} [built]
[88] ./static/css/material-icons.css 50 bytes {14} [built]
[93] ./static/css/switch.css 50 bytes {16} [built]
+ 425 hidden modules
WARNING in configuration
The 'mode' option has not been set, webpack will fallback to 'production' for this value. Set 'mode' option to 'development' or 'production' to enable defaults for each environment.
You can also set it to 'none' to disable any default behavior. Learn more: https://webpack.js.org/configuration/mode/
WARNING in asset size limit: The following asset(s) exceed the recommended size limit (244 KiB).
This can impact web performance.
Assets:
moment.f2be510679d38b9c54e9.js (377 KiB)
tree.57c43dd706cbd3d74ef9.js (1.48 MiB)
nv.d3.min.js (247 KiB)
nv.d3.min.js.map (1.86 MiB)
dagre-d3.min.js (708 KiB)
dagre-d3.min.js.map (653 KiB)
redoc.standalone.js (970 KiB)
redoc.standalone.js.map (3.23 MiB)
codemirror.js (389 KiB)
jshint.js (1.22 MiB)
WARNING in entrypoint size limit: The following entrypoint(s) combined asset size exceeds the recommended limit (244 KiB). This can impact web performance.
Entrypoints:
moment (377 KiB)
moment.f2be510679d38b9c54e9.js
tree (1.48 MiB)
tree.57c43dd706cbd3d74ef9.css
tree.57c43dd706cbd3d74ef9.js
WARNING in webpack performance recommendations:
You can limit the size of your bundles by using import() or require.ensure to lazy load some parts of your application.
For more info visit https://webpack.js.org/guides/code-splitting/
Child mini-css-extract-plugin node_modules/css-loader/dist/cjs.js!static/css/bootstrap-theme.css:
Entrypoint mini-css-extract-plugin = *
[0] ./node_modules/css-loader/dist/cjs.js!./static/css/bootstrap-theme.css 130 KiB {0} [built]
+ 1 hidden module
Child mini-css-extract-plugin node_modules/css-loader/dist/cjs.js!static/css/calendar.css:
Entrypoint mini-css-extract-plugin = *
[0] ./node_modules/css-loader/dist/cjs.js!./static/css/calendar.css 1.47 KiB {0} [built]
+ 1 hidden module
Child mini-css-extract-plugin node_modules/css-loader/dist/cjs.js!static/css/dags.css:
Entrypoint mini-css-extract-plugin = *
[0] ./node_modules/css-loader/dist/cjs.js!./static/css/dags.css 3.31 KiB {0} [built]
+ 1 hidden module
Child mini-css-extract-plugin node_modules/css-loader/dist/cjs.js!static/css/flash.css:
Entrypoint mini-css-extract-plugin = *
[0] ./node_modules/css-loader/dist/cjs.js!./static/css/flash.css 2.25 KiB {0} [built]
+ 1 hidden module
Child mini-css-extract-plugin node_modules/css-loader/dist/cjs.js!static/css/gantt.css:
Entrypoint mini-css-extract-plugin = *
[0] ./node_modules/css-loader/dist/cjs.js!./static/css/gantt.css 1.58 KiB {0} [built]
+ 1 hidden module
Child mini-css-extract-plugin node_modules/css-loader/dist/cjs.js!static/css/graph.css:
Entrypoint mini-css-extract-plugin = *
[0] ./node_modules/css-loader/dist/cjs.js!./static/css/graph.css 3.16 KiB {0} [built]
+ 1 hidden module
Child mini-css-extract-plugin node_modules/css-loader/dist/cjs.js!static/css/loading-dots.css:
Entrypoint mini-css-extract-plugin = *
[0] ./node_modules/css-loader/dist/cjs.js!./static/css/loading-dots.css 1.64 KiB {0} [built]
+ 1 hidden module
Child mini-css-extract-plugin node_modules/css-loader/dist/cjs.js!static/css/main.css:
Entrypoint mini-css-extract-plugin = *
[0] ./node_modules/css-loader/dist/cjs.js!./static/css/main.css 10.7 KiB {0} [built]
[3] ./static/sort_both.png 307 bytes {0} [built]
[4] ./static/sort_desc.png 251 bytes {0} [built]
[5] ./static/sort_asc.png 255 bytes {0} [built]
+ 2 hidden modules
Child mini-css-extract-plugin node_modules/css-loader/dist/cjs.js!static/css/material-icons.css:
Entrypoint mini-css-extract-plugin = *
[0] ./node_modules/css-loader/dist/cjs.js!./static/css/material-icons.css 110 KiB {0} [built]
+ 1 hidden module
Child mini-css-extract-plugin node_modules/css-loader/dist/cjs.js!static/css/switch.css:
Entrypoint mini-css-extract-plugin = *
[0] ./node_modules/css-loader/dist/cjs.js!./static/css/switch.css 2.69 KiB {0} [built]
+ 1 hidden module
Child mini-css-extract-plugin node_modules/css-loader/dist/cjs.js!static/css/tree.css:
Entrypoint mini-css-extract-plugin = *
[0] ./node_modules/css-loader/dist/cjs.js!./static/css/tree.css 1.8 KiB {0} [built]
+ 1 hidden module
✨ Done in 7.53s.
```
I am back to where I have started currently, does anyone have any recommendations about what might be missing?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] potiuk commented on issue #19566: Breeze - The CSS and JS files are not built
Posted by GitBox <gi...@apache.org>.
potiuk commented on issue #19566:
URL: https://github.com/apache/airflow/issues/19566#issuecomment-968104545
Hello @karakanb - thanks for that very detailed description. There are probably about 10 issues specified in this one entry, so it's next to impossible to do any reasonable action with it. However let me try and have a proposal:
Airflow has >1800 contributors and many areas (the guides including) are created by many of them. We continuously improve it and actually the best way to contribution works is to turn experience of first time contributors into correcting the docs, removing silent assumptions that more experienced people have.
You seem to know well already how to improve the documentation for first time contributors, and since you are one, you probably have - correctly assessed what is confusing for you, so this is a great chance that you can correct it best by submitting PRs fixing some of those issues. We do not require (and even discourage) people from creating issues for such (non-core, mostly documentation changes).
You are completely free to start PRs directly proposing fixes to some of those changes you mentioned (but please, one "area" to fix in one PR - the more you split the easier it will be to review, get comments from others and approvals from committers to merge them.
Answering some of your questions:
* First of all you can see the recording from the first-time-contributors workshop we run in Mexico OCSS conference earlier this year https://youtu.be/kvccZizzfTk - it migh give you some more context on why we need more than one env (local + breeze) and might help to make your PRs better.
* one thing you have to remember is that not everyone is like you. There are people who have no Docker experience whatsoever and their programming is done mostly in the IDEs. The path you proposed is good for someone who knows vi or nano and is comfortable with using them, but MANY people (especially those who use Windows as their primary development platform) just use IDEs to do EVERYTHING. I would not dismiss such people - they are those who needs most help actually to get familiar with our environment. But maybe indeed a good idea (PR please?) to mention both possibilities in the docs and structure it in the way that people who have this experience will do it this way and people with IDE-only approach will do it differently. You have to always remember that you do not know who the reader is and you should assume that 90% of people reading it will have different background, experience, skills than you and you need to produce something that is good for all those people.
* yeah you need both - local virtualenv and dockerized Breeze environment in various circumstances. Breeze gives you "consistent" environment that is the same for everyone and avoids "works for me" kind of problems, where local virtualenv integrates better with IDEs and is generally much faster on MacOS, WSL2 environments (which VAST majority of our users use). You already saw that with yarn, but there are other cases where local virtualenv is better. A lot of details about it described in the main "CONTRIBUTING.rst" https://github.com/apache/airflow/blob/main/CONTRIBUTING.rst#development-environments - where comparision between the two is explained. What is likely a good candidate for PR (another one!) is to find a way to explain it in "quick quide" in the way that is not overwhelming and without the assumptions others have.
The `jq` is needed for some parts of breeze. I am not sure if it makes sense more than "it's needed". It is needed to run "kind/kubernetes" tests which are also run using breeze scripts and to test production images. I am not sure if the new user is even able to assess if they will need it or not initially, so better to just say "you need it" . But if you will have a proposal how to put in the way that will not add more confusion, I am all ears and happy to get (another) PR with that.
Eventually, what i really would love is a series of PRs proposing fixes to those problems you raised. All the community is very open and greatful for new contributors to improve our docs and developer experience and you seem to be the best kind of person to do it:
* you already know what annoys you
* you seem to know how to fix some of that
* you do not have all the assumptions more Airflow-dev-experienced people have
* this something that we keep on repeating on our workshops - improving the contributions docs is one of the BEST contributions you can do as first-time contributor. It is. You can pay back for the software you get for free AND help others like you!
So you seem ideal person to do it ! I hope I armed you with enough knowledge above - and even the recording from the workshops, so that you can get the missing context and propose it in the way that will be best for people like you.
Now -finaly (since I went through the ~10 issues you raised additionally in this one comment). Regarding assets generation: You just need to do it once (following the warning you correctly followed) - what @kaxil mentioned is true - but this is not MacOS only. You NEED to generate the assets once because they are not automatically generated at first entry (I wanted to do it but that would slow-down the experience of people who do not care about webui and running - quite many of them) . However when you run `start-airflow` command it **SHOULD** be exceuting automatically, so the warning should not be there. Unless there is an error in som of the "entrypoint" scripts, it is rather likely something specific to your environment. I wonder if you could prepare a gist with detailed dump of the logs you see when you run `start-airflow' - from each of the tmux terminals. That will make it possible to take a look of what you are experiencing and maybe we will be able to find out what's th
e reason and fix /improve it.
Once you compile the assets once in your sources, they should remain there.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] potiuk commented on issue #19566: Breeze - The CSS and JS files are not built
Posted by GitBox <gi...@apache.org>.
potiuk commented on issue #19566:
URL: https://github.com/apache/airflow/issues/19566#issuecomment-971581879
@karakanb - as mentioned above -> this is NIOT the problem with asset compliation/breeze. The race for asset compilation was there and it is solved now..
I believe this is a problem introduced recently in the `main` branch with wrong path to js files or similar.
Can you please open a separate issue for that ?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] karakanb commented on issue #19566: Breeze - The CSS and JS files are not built
Posted by GitBox <gi...@apache.org>.
karakanb commented on issue #19566:
URL: https://github.com/apache/airflow/issues/19566#issuecomment-967755882
I already ran it, both from within the container and outside of it, although nothing changed.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] nshetty15 commented on issue #19566: Breeze - The CSS and JS files are not built
Posted by GitBox <gi...@apache.org>.
nshetty15 commented on issue #19566:
URL: https://github.com/apache/airflow/issues/19566#issuecomment-970554959
@karakanb I'm seeing similar issues. Did you manage to fix this?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] potiuk commented on issue #19566: Breeze - The CSS and JS files are not built
Posted by GitBox <gi...@apache.org>.
potiuk commented on issue #19566:
URL: https://github.com/apache/airflow/issues/19566#issuecomment-971433408
Ah no - this is the same for me. Can you please open a separate issue for that ? Seems indeed latest main version have the search bar broken
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] karakanb commented on issue #19566: Breeze - The CSS and JS files are not built
Posted by GitBox <gi...@apache.org>.
karakanb commented on issue #19566:
URL: https://github.com/apache/airflow/issues/19566#issuecomment-971482689
I think the aim for me now is to have the file somewhere locally, without thinking about the webserver or the race conditions that might further complicate the problem. I am open to any tips.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org