date:20240523

Re: [I] Content not from webpack is served from 'D:\tech_release\superset-fork\superset\static\assets' directory [superset]

2024-05-23 Thread via GitHub



duniang818 commented on issue #28632:
URL: https://github.com/apache/superset/issues/28632#issuecomment-2128596667

   1. i have checked the config file both webpack.config.js, 
webpack.proxy-config.js and superest_config.py, there everything is ok, i don't 
find something is wrong.
   2. the assets exist in the dir 
D:\tech_release\superset-fork\superset\static\assets.
   3. the structure is :
   D:\tech_release\superset-fork 
   D:\tech_release\superset-fork\superset
   `PS  D:\tech_release\superset-fork\superset  superset run -p 8088`
   D:\tech_release\superset-fork\superset\superset_config.py
   D:\tech_release\superset-fork\superset\static\assets
   D:\tech_release\superset-fork\superset-frontend
   `PS  D:\tech_release\superset-fork\superset-frontend  npm install && npm run 
dev-server`
   D:\tech_release\superset-fork\superset-frontend\webpack.config.js
   D:\tech_release\superset-fork\superset-frontend\webpack.proxy-config.js
   D:\tech_release\superset-fork\superset-frontend\package.json
   
   4. everything is above, but don't work now.
   
   



-- 
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: notifications-unsubscr...@superset.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org
For additional commands, e-mail: notifications-h...@superset.apache.org

Re: [I] Content not from webpack is served from 'D:\tech_release\superset-fork\superset\static\assets' directory [superset]

2024-05-23 Thread via GitHub



duniang818 commented on issue #28632:
URL: https://github.com/apache/superset/issues/28632#issuecomment-2128595906

   1. i have checked the config file both webpack.config.js, 
webpack.proxy-config.js and superest_config.py, there everything is ok, i don't 
find something is wrong.
   2. the assets exist in the dir 
D:\tech_release\superset-fork\superset\static\assets.
   3. the structure is :
   D:\tech_release\superset-fork 
   D:\tech_release\superset-fork\superset
   `PS  D:\tech_release\superset-fork\superset  superset run -p 8088`
   D:\tech_release\superset-fork\superset\superset_config.py
   D:\tech_release\superset-fork\superset\static\assets
   D:\tech_release\superset-fork\superset-frontend
   `PS  D:\tech_release\superset-fork\superset-frontend  npm install && npm run 
dev-server`
   D:\tech_release\superset-fork\superset-frontend\webpack.config.js
   D:\tech_release\superset-fork\superset-frontend\webpack.proxy-config.js
   D:\tech_release\superset-fork\superset-frontend\package.json
   
   4. everything is above, but don't work now.
   
   



-- 
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: notifications-unsubscr...@superset.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org
For additional commands, e-mail: notifications-h...@superset.apache.org

Re: [I] Superset ALERT & REPORTS not working [superset]

2024-05-23 Thread via GitHub



dosubot[bot] commented on issue #28686:
URL: https://github.com/apache/superset/issues/28686#issuecomment-2128525374

   
   To address the issue with the ALERT & REPORTS feature in your Superset 
project, follow these steps:
   
   1. **Check the `"ALERT_REPORTS"` Feature Flag**: Ensure it's enabled in your 
`superset_config.py`:
   ```python
   FEATURE_FLAGS = {
   "ALERT_REPORTS": True
   }
   ```
   
   2. **Update Celery Beat Schedule**: Ensure you have a schedule for 
`reports.scheduler` in your Celery configuration:
   ```python
   from celery.schedules import crontab
   
   class CeleryConfig:
   beat_schedule = {
   "reports.scheduler": {
   "task": "reports.scheduler",
   "schedule": crontab(minute="*", hour="*"),
   },
   "reports.prune_log": {
   "task": "reports.prune_log",
   "schedule": crontab(minute=0, hour=0),
   },
   }
   CELERY_CONFIG = CeleryConfig
   ```
   
   3. **Ensure Browser Installation for Screenshots**: Confirm a headless 
browser is installed. For Chrome:
   ```python
   WEBDRIVER_TYPE = "chrome"
   WEBDRIVER_OPTION_ARGS = [
   "--force-device-scale-factor=2.0",
   "--high-dpi-support=2.0",
   "--headless",
   "--disable-gpu",
   "--disable-dev-shm-usage",
   "--no-sandbox",
   "--disable-setuid-sandbox",
   "--disable-extensions",
   ]
   ```
   
   4. **SMTP or Slack Configuration**: Ensure your SMTP settings or 
`SLACK_API_TOKEN` are correctly configured:
   - **Slack**:
   ```python
   SLACK_API_TOKEN = "xoxb-your-slack-token"
   ```
   - **Email**:
   ```python
   SMTP_HOST = "smtp.sendgrid.net"
   SMTP_PORT = 2525
   SMTP_USER = "your_user"
   SMTP_PASSWORD = "your_password"
   SMTP_MAIL_FROM = "nore...@youremail.com"
   ```
   
   5. **Review Celery Worker and Beat Logs**: Examine the logs of your Celery 
worker and beat for additional insights.
   
   6. **Fix the "Failed to assign to property 'Path'" Error**: Ensure that the 
properties being assigned are correctly defined and used. For example:
   ```tsx
   const updateAlertState = (name: string, value: any) => {
 setCurrentAlert(currentAlertData => ({
   ...currentAlertData,
   [name]: value,
 }));
   };
   
   const onPathChange = (event: React.ChangeEvent) => {
 const { value } = event.target;
 updateAlertState('path', value);
   };
   ```
   
   Ensure all configurations, especially those related to Celery, the headless 
browser, and notification settings, are correct. For more detailed guidance, 
refer to the [Superset 
documentation](https://github.com/apache/superset/blob/master/docs/docs/configuration/alerts-reports.mdx)
 
[[1]](https://github.com/apache/superset/issues/28381)[[2]](https://github.com/apache/superset/issues/12794)[[3]](https://github.com/apache/superset/blob/master/docs/docs/configuration/alerts-reports.mdx).
   
   
   
   
   
   
    Details
   
   
   **About Dosu**
   This response is meant to be useful and save you time. It is **not meant to 
be a precise solution**, but rather a starting point for your own research.
   
   Help me be more useful! Please leave a  if this is helpful and  if it is 
irrelevant.
   
   
   *To continue the conversation, mention @dosu.*
   


-- 
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: notifications-unsubscr...@superset.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org
For additional commands, e-mail: notifications-h...@superset.apache.org

[I] Superset ALERT & REPORTS not working [superset]

2024-05-23 Thread via GitHub

mujohiddin opened a new issue, #28686:
URL: https://github.com/apache/superset/issues/28686

### Bug description

Hello there. my project is last september version but i have problem with
ALERT & REPORTS how to fix it. I don't know how to fix it. help me

### How to reproduce the bug

### Screenshots/recordings

![photo_2024-05-24_09-58-21](https://github.com/apache/superset/assets/69301931/6cd10e9b-aa50-456b-925e-bedd88f328df)

Could this be the cause of the problem?

### Superset version

master / latest-dev

### Python version

3.9

### Node version

### Browser

Chrome

### Additional context

### Checklist

- [ ] I have searched Superset docs and Slack and didn't find a solution to
my problem.
- [ ] I have searched the GitHub issue tracker and didn't find a similar bug
report.
- [ ] I have checked Superset's logs for errors and if I found a relevant
Python stacktrace, I included it here as text in the "additional context"
section.

--
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.

1 2 >

1 - 100 of 180 matches

Mail list logo