Re: Testing embedded image

[Krist Wongsuphasawat]

🤔

Best regards,

Krist

--

Krist Wongsuphasawat
http://kristw.yellowpigz.com
On Jan 12, 2019, 02:28 +0700, Maxime Beauchemin , 
wrote:
>

Re: Apache Superset Design Sync (vote on next meet up)

[Jolly Paramjit]

Hi Eli,

 We are good !!!  Appreciate your help. 
Looking forward to e-meet & have fruitful conversations.

-- 
Thanks & Regards
Jolly
Handphone: +91-9971815749
 
[We Learn, Unlearn & Re-learn.]
 

On 12/01/19, 2:58 AM, "Eli Brumbaugh"  wrote:

Hi All,

I wanted to let the group know that we've updated the Apache Superset
design sync to 5-6 PM (PST) from the previous 2-3 PM (PST) timing that
would have been more difficult for those of us who are distributed.

Jolly & Rasmiranjan, I hope this new time is more reasonable. Thank you for
sharing your itinerary with us. I will add it to the agenda.

Best,
- Eli

On Mon, Jan 7, 2019 at 11:05 PM Jolly Paramjit 
wrote:

> Eli,
>   Thanks for your reply, I think we should attend the video conference
> whatever odd hours it may be.  We will join the call.
> As I want first discussion with full information & some basic demo to
> showcase.
>
> We will be presenting:
> 1. Our high level planning for superset overall feature enhancements.
> (in-case everyone is interested)
> 2. Design system - We are working in Guavus
> 3. How we are thinking to use same in superset but we need some guidance
> from stake holders.
>
> Looking forward for the upcoming meeting.
>
> --
> Thanks & Regards
> Jolly
> Handphone: +91-9971815749
>
> [We Learn, Unlearn & Re-learn.]
>
>
> On 08/01/19, 5:17 AM, "Eli Brumbaugh" 
> wrote:
>
> Hi Jolly, Rasmiranjan (and the community!)
>
> Thank you again for letting the community know about your time zone
> difference (13.5 hours ahead of those of us in the Bay Area) and how
> the
> time originally set for the design sync is difficult for you to 
attend.
>
> *Geographically distributed collaboration proposal:*
> Please let us know what you think about this solution.
>
>- In place of a video conference we collaborate via this email
> alias,
>shared (publicly accessible docs) and Sketch files.
>- The ASF how-it-works
> suggest the
>following:
>   - *"Communication is done via mailing lists. These identify
> "virtual
>   meeting rooms" where conversations happen asynchronously, which
> is a
>   general requirement for groups that are so geographically
> distributed to
>   cover all time zones (like it's normally the case for the
> various Apache
>   communities).*
>- With our global distribution working asynchronously via the dev@
> email
>and google docs seems like the best way to move forward while
> maximizing
>the transparency of our discussions.
>
> *Sharing your proposal: *
> Jolly and Rasmiranjan, would you be willing to share your Superset
> Design
> System and custom UI framework proposal via the dev@ email alias
> along with
> any related publically accessible docs for discussion and if you
> desire a
> vote?
>
> *Upcoming design sync:*
>
>1. The Thursday, January 31st video chat will still occur for all
> who
>can attend.
>   - *All discussion*, notes, open questions, to do's, etc will be
> documented
>   in this publicly
>   <
> 
https://docs.google.com/document/d/1OokXB2BNdYx8-M4IGYyaoVU3J74Pe0ZNJeqSHjyLAmA/edit?usp=sharing
> >
>   accessible google doc.
>   - *All decisions* will still be put to a vote in the dev@ email
> alias.
>2. This doc
><
> 
https://docs.google.com/document/d/1OokXB2BNdYx8-M4IGYyaoVU3J74Pe0ZNJeqSHjyLAmA/edit?usp=sharing
> >
>will be sent out to the dev@ email alias as a reminder for
> additional
>comments/discussion.
>   - Please be sure to comment and leave feedback!
>3. This doc
><
> 
https://docs.google.com/document/d/1OokXB2BNdYx8-M4IGYyaoVU3J74Pe0ZNJeqSHjyLAmA/edit?usp=sharing
> >
>will serve as a record of meeting notes that can be accessed easily
> by all.
>
> *If anyone has any thoughts or concerns please let the thread know!*
>
> Best,
> Eli
>
>
>
> On Fri, Jan 4, 2019 at 11:35 AM Jolly Paramjit <
> jolly.param...@guavus.com>
> wrote:
>
> > Hi Eli,
> >
> > We can use hangouts not an issue, officially we use zoom.
> >
> > --
> > Thanks & Regards
> > Jolly
> > Handphone: +91-9971815749
> >
> > [We Learn, Unlearn & Re-learn.]
> >
> >
> > On 05/01/19, 12:34 AM, "Eli Brumbaugh"  .INVALID>
> 

[jira] [Created] (SUPERSET-6) case sensitivity breaks charts

[James Davidheiser (JIRA)]

James Davidheiser created SUPERSET-6:


 Summary: case sensitivity breaks charts
 Key: SUPERSET-6
 URL: https://issues.apache.org/jira/browse/SUPERSET-6
 Project: Superset
  Issue Type: Bug
Reporter: James Davidheiser


We have an issue where, at some point, Superset is changing the case of some 
text, and this is causing Pandas to fail when trying to manipulate data to 
display a bar chart.  This is running in Redshift,

 

Steps to reproduce:
 * In SQL lab, run a query to join two tables and create a two-column view, 
with a label and numeric value
 * click the "explore" button to make a dataset from this.
 * select a bar chart visualization type
 * for metrics, choose MAX(column_name)
 * for series, chose the label column
 * run the query
 * click the menu to the top right, and view results.  The column headers will 
be label_column, and max(column_name)  _note:  max is now lowercase_

I am able to get the chart to render by manually modifying the SQL for the 
aggregation to be lowercase, or by creating a new metric in the datasource that 
is defined as max(column_name), already lowercase.

 

Error logs when this happens:

{{2019-01-11 23:48:53,894:DEBUG:root:[stats_logger] (incr) loaded_from_source}}
{{2019-01-11 23:48:53,894:INFO:root:Caching 2262 chars at key 
fa6d6a8327a9476c27477dcd624b1793}}
{{2019-01-11 23:48:53,894:DEBUG:root:[stats_logger] (incr) set_cache_key}}
{{2019-01-11 23:48:53,897:ERROR:root:'MAX(column_name)'}}
{{Traceback (most recent call last):}}
{{  File "/usr/local/lib/python3.6/site-packages/pandas/core/indexes/base.py", 
line 3064, in get_loc}}
{{    return self._engine.get_loc(key)}}
{{  File "pandas/_libs/index.pyx", line 140, in 
pandas._libs.index.IndexEngine.get_loc}}
{{  File "pandas/_libs/index.pyx", line 162, in 
pandas._libs.index.IndexEngine.get_loc}}
{{  File "pandas/_libs/hashtable_class_helper.pxi", line 1492, in 
pandas._libs.hashtable.PyObjectHashTable.get_item}}
{{  File "pandas/_libs/hashtable_class_helper.pxi", line 1500, in 
pandas._libs.hashtable.PyObjectHashTable.get_item}}
{{KeyError: 'MAX(column_name)'}}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Closed] (SUPERSET-6) case sensitivity breaks charts

[James Davidheiser (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SUPERSET-6?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

James Davidheiser closed SUPERSET-6.

Resolution: Duplicate

> case sensitivity breaks charts
> --
>
> Key: SUPERSET-6
> URL: https://issues.apache.org/jira/browse/SUPERSET-6
> Project: Superset
>  Issue Type: Bug
>Reporter: James Davidheiser
>Priority: Major
>
> We have an issue where, at some point, Superset is changing the case of some 
> text, and this is causing Pandas to fail when trying to manipulate data to 
> display a bar chart.  This is running in Redshift,
>  
> Steps to reproduce:
>  * In SQL lab, run a query to join two tables and create a two-column view, 
> with a label and numeric value
>  * click the "explore" button to make a dataset from this.
>  * select a bar chart visualization type
>  * for metrics, choose MAX(column_name)
>  * for series, chose the label column
>  * run the query
>  * click the menu to the top right, and view results.  The column headers 
> will be label_column, and max(column_name)  _note:  max is now lowercase_
> I am able to get the chart to render by manually modifying the SQL for the 
> aggregation to be lowercase, or by creating a new metric in the datasource 
> that is defined as max(column_name), already lowercase.
>  
> Error logs when this happens:
> {{2019-01-11 23:48:53,894:DEBUG:root:[stats_logger] (incr) 
> loaded_from_source}}
> {{2019-01-11 23:48:53,894:INFO:root:Caching 2262 chars at key 
> fa6d6a8327a9476c27477dcd624b1793}}
> {{2019-01-11 23:48:53,894:DEBUG:root:[stats_logger] (incr) set_cache_key}}
> {{2019-01-11 23:48:53,897:ERROR:root:'MAX(column_name)'}}
> {{Traceback (most recent call last):}}
> {{  File 
> "/usr/local/lib/python3.6/site-packages/pandas/core/indexes/base.py", line 
> 3064, in get_loc}}
> {{    return self._engine.get_loc(key)}}
> {{  File "pandas/_libs/index.pyx", line 140, in 
> pandas._libs.index.IndexEngine.get_loc}}
> {{  File "pandas/_libs/index.pyx", line 162, in 
> pandas._libs.index.IndexEngine.get_loc}}
> {{  File "pandas/_libs/hashtable_class_helper.pxi", line 1492, in 
> pandas._libs.hashtable.PyObjectHashTable.get_item}}
> {{  File "pandas/_libs/hashtable_class_helper.pxi", line 1500, in 
> pandas._libs.hashtable.PyObjectHashTable.get_item}}
> {{KeyError: 'MAX(column_name)'}}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: commit rights for Vyl and Sylvia

[Sylvia Tomiyama]

Same here -- thanks again for your help!

On Fri, Jan 11, 2019 at 2:09 PM Vyl Chiang  wrote:

> Thanks for checking. I’m all set for now!
>
> Sent from my iPhone
>
> > On Jan 11, 2019, at 1:19 PM, Alan Gates  wrote:
> >
> > I think all this got taken care of over the holidays, so Vyl and Sylvia
> > should have their full commit rights now.  Let me know if you see any
> > issues.
> >
> > Alan.
>

Re: commit rights for Vyl and Sylvia

[Vyl Chiang]

Thanks for checking. I’m all set for now!

Sent from my iPhone

> On Jan 11, 2019, at 1:19 PM, Alan Gates  wrote:
> 
> I think all this got taken care of over the holidays, so Vyl and Sylvia
> should have their full commit rights now.  Let me know if you see any
> issues.
> 
> Alan.

Re: Apache Superset Design Sync (vote on next meet up)

[Eli Brumbaugh]

Hi All,

I wanted to let the group know that we've updated the Apache Superset
design sync to 5-6 PM (PST) from the previous 2-3 PM (PST) timing that
would have been more difficult for those of us who are distributed.

Jolly & Rasmiranjan, I hope this new time is more reasonable. Thank you for
sharing your itinerary with us. I will add it to the agenda.

Best,
- Eli

On Mon, Jan 7, 2019 at 11:05 PM Jolly Paramjit 
wrote:

> Eli,
>   Thanks for your reply, I think we should attend the video conference
> whatever odd hours it may be.  We will join the call.
> As I want first discussion with full information & some basic demo to
> showcase.
>
> We will be presenting:
> 1. Our high level planning for superset overall feature enhancements.
> (in-case everyone is interested)
> 2. Design system - We are working in Guavus
> 3. How we are thinking to use same in superset but we need some guidance
> from stake holders.
>
> Looking forward for the upcoming meeting.
>
> --
> Thanks & Regards
> Jolly
> Handphone: +91-9971815749
>
> [We Learn, Unlearn & Re-learn.]
>
>
> On 08/01/19, 5:17 AM, "Eli Brumbaugh" 
> wrote:
>
> Hi Jolly, Rasmiranjan (and the community!)
>
> Thank you again for letting the community know about your time zone
> difference (13.5 hours ahead of those of us in the Bay Area) and how
> the
> time originally set for the design sync is difficult for you to attend.
>
> *Geographically distributed collaboration proposal:*
> Please let us know what you think about this solution.
>
>- In place of a video conference we collaborate via this email
> alias,
>shared (publicly accessible docs) and Sketch files.
>- The ASF how-it-works
> suggest the
>following:
>   - *"Communication is done via mailing lists. These identify
> "virtual
>   meeting rooms" where conversations happen asynchronously, which
> is a
>   general requirement for groups that are so geographically
> distributed to
>   cover all time zones (like it's normally the case for the
> various Apache
>   communities).*
>- With our global distribution working asynchronously via the dev@
> email
>and google docs seems like the best way to move forward while
> maximizing
>the transparency of our discussions.
>
> *Sharing your proposal: *
> Jolly and Rasmiranjan, would you be willing to share your Superset
> Design
> System and custom UI framework proposal via the dev@ email alias
> along with
> any related publically accessible docs for discussion and if you
> desire a
> vote?
>
> *Upcoming design sync:*
>
>1. The Thursday, January 31st video chat will still occur for all
> who
>can attend.
>   - *All discussion*, notes, open questions, to do's, etc will be
> documented
>   in this publicly
>   <
> https://docs.google.com/document/d/1OokXB2BNdYx8-M4IGYyaoVU3J74Pe0ZNJeqSHjyLAmA/edit?usp=sharing
> >
>   accessible google doc.
>   - *All decisions* will still be put to a vote in the dev@ email
> alias.
>2. This doc
><
> https://docs.google.com/document/d/1OokXB2BNdYx8-M4IGYyaoVU3J74Pe0ZNJeqSHjyLAmA/edit?usp=sharing
> >
>will be sent out to the dev@ email alias as a reminder for
> additional
>comments/discussion.
>   - Please be sure to comment and leave feedback!
>3. This doc
><
> https://docs.google.com/document/d/1OokXB2BNdYx8-M4IGYyaoVU3J74Pe0ZNJeqSHjyLAmA/edit?usp=sharing
> >
>will serve as a record of meeting notes that can be accessed easily
> by all.
>
> *If anyone has any thoughts or concerns please let the thread know!*
>
> Best,
> Eli
>
>
>
> On Fri, Jan 4, 2019 at 11:35 AM Jolly Paramjit <
> jolly.param...@guavus.com>
> wrote:
>
> > Hi Eli,
> >
> > We can use hangouts not an issue, officially we use zoom.
> >
> > --
> > Thanks & Regards
> > Jolly
> > Handphone: +91-9971815749
> >
> > [We Learn, Unlearn & Re-learn.]
> >
> >
> > On 05/01/19, 12:34 AM, "Eli Brumbaugh"  .INVALID>
> > wrote:
> >
> > Hi Jolly,
> >
> > Thank you for letting me know about your location and custom
> design
> > system
> > / UI framework. I will work on finding a time that works for
> everyone.
> >
> > Quick question: Can you use Google Hangouts?
> >
> > Best,
> > Eli
> >
> > On Wed, Jan 2, 2019 at 5:15 PM Jolly Paramjit <
> > jolly.param...@guavus.com>
> > wrote:
> >
> > > Thanks Eli for setting up this meeting.
> > >
> > > We are based in india hence plz make sure timings are not very
> odd.
> > > Currently it seems 4 am which is very early.
> > > We are ok anytime between 9 am - 11 pm IST. Hopefully you can
> move
> > to any
> >   

commit rights for Vyl and Sylvia

[Alan Gates]

I think all this got taken care of over the holidays, so Vyl and Sylvia
should have their full commit rights now.  Let me know if you see any
issues.

Alan.

Test image as attachment

[Maxime Beauchemin]

Testing embedded image

[Maxime Beauchemin]

[image: Screen Shot 2019-01-09 at 5.26.51 PM.png]