[GitHub] incubator-usergrid pull request: Fixes to get Core, Services and R...
GitHub user snoopdave opened a pull request: https://github.com/apache/incubator-usergrid/pull/48 Fixes to get Core, Services and REST tests working consistently with Core Persistence. You can merge this pull request into a Git repository by running: $ git pull https://github.com/snoopdave/incubator-usergrid two-dot-o Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-usergrid/pull/48.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #48 commit 2fe3c13bda216723f6e9920c5cf6e53683100862 Author: Dave Johnson dmjohn...@apigee.com Date: 2014-08-09T22:26:36Z More progress on getting test to pass with Core Persistence, also allow forked C* and ES for Core and Services modules. commit 6d666f0aad2bc78ff54f3b4166402ee7974575bf Author: Dave Johnson dmjohn...@apigee.com Date: 2014-08-11T22:48:22Z More progress on getting REST tests passing with Core Persistence, now down to 12 tests not passing. commit 30d00089777923778fa3c25e8d566771331662aa Author: Dave Johnson dmjohn...@apigee.com Date: 2014-08-12T20:37:06Z More progress on getting REST tests passing with Core Persistence, plus some config necessary to get better logging out of Jersey. commit 3ceee949d0dd4daed7e541077f9c96d135b81bd4 Author: Dave Johnson dmjohn...@apigee.com Date: 2014-08-13T12:51:55Z Removing outdated perftest projects for now. commit 053b027143e8b2587a4d865d6d2c800e5dcaaa26 Author: Dave Johnson dmjohn...@apigee.com Date: 2014-08-13T15:51:50Z More progress on getting REST tests going in the two-dot-o branch, marked some tests as @Ignore and opened JIRA issues to fix them later. commit ab8ea15d35845b86e90d313249238dd795830cd0 Author: Dave Johnson dmjohn...@apigee.com Date: 2014-08-13T21:03:17Z Fix for problem in unique values implementation in Core Persistence, and tests to verify new fix. commit 4d38aab280222879f7dd1ae5a059c6e03d2bbde0 Author: Dave Johnson dmjohn...@apigee.com Date: 2014-08-13T21:03:52Z Merge branch 'two-dot-o' of https://git-wip-us.apache.org/repos/asf/incubator-usergrid into two-dot-o commit be93261fb53620163ae70318a5f8c329c5d2a830 Author: Dave Johnson dmjohn...@apigee.com Date: 2014-08-13T21:10:48Z Merge branch 'master' into two-dot-o. Also making log configs consistent. Conflicts: .gitignore portal/dist/usergrid-portal/index-debug.html portal/dist/usergrid-portal/index-template.html portal/dist/usergrid-portal/index.html portal/dist/usergrid-portal/js/libs/usergrid-libs.min.js portal/dist/usergrid-portal/js/libs/usergrid.sdk.js portal/dist/usergrid-portal/js/usergrid-dev.min.js portal/dist/usergrid-portal/js/usergrid.min.js commit 91699d34e17e60d8cd0c4ecc1e0ef003d27f24fa Author: Dave Johnson dmjohn...@apigee.com Date: 2014-08-14T02:04:06Z Couple more Core Persistence test fixes. commit 6a9bb7434e5a00667eddee0eb2a39d15c1de2809 Author: Dave Johnson dmjohn...@apigee.com Date: 2014-08-14T02:09:46Z Ignore failing test until it is fixed via associated JIRA issue. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
Using Jira as a mechanism for Tracking Usergrid Progress
Hi Folks, I thought I would put this one out there as we build up to the 1.0 release. Is there any motivation for us to use Jira as an issue tracker? I know that there is some material going on to Jira but I also see a lot not going on there. One aspect of Jira which I find extremely useful is the ability to generate release reports which we can then distribute with the release announcement. An example can be found here http://s.apache.org/1.9-release Which I recenly included within the CHANGES.txt for Apache Nutch release candidate https://dist.apache.org/repos/dist/dev/nutch/1.9/CHANGES.txt -- *Lewis*
[jira] [Created] (USERGRID-215) Possible bug in usergrid-lib.min.js TypeError: c in null
Lewis John McGibbney created USERGRID-215: - Summary: Possible bug in usergrid-lib.min.js TypeError: c in null Key: USERGRID-215 URL: https://issues.apache.org/jira/browse/USERGRID-215 Project: Usergrid Issue Type: Bug Components: Portal Affects Versions: 1.0 Environment: Macosx v 10.9.4 Firefox 31.0 Usergrid (master) Reporter: Lewis John McGibbney Fix For: 1.1 Using UG (master) when I turn on firebug in firefox and log in to the UG portal, I see the following console error usergrid-lib.min.js (line 27, col 92) ...==thisc.$$nextSibling))for(;c!==this!(d=c.$$nextSibling);)c=c.$parent}while(... First things first, can anyone else reproduce this? I have no idea about why this is as I have not looked into the JavaScript yet. -- This message was sent by Atlassian JIRA (v6.2#6252)
[GitHub] incubator-usergrid pull request: AWSCluster and test fixes.
GitHub user snoopdave opened a pull request: https://github.com/apache/incubator-usergrid/pull/49 AWSCluster and test fixes. This PR contains two fixes: 1) AWSCluster now sets Tomcat threads and memory based on AWS instance type 2) Cassandra and Hystrix connection/thread settings to allow Core and Services tests to run consistently. You can merge this pull request into a Git repository by running: $ git pull https://github.com/snoopdave/incubator-usergrid two-dot-o Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-usergrid/pull/49.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #49 commit 630e6210d8de071bf6dd2e0c9108df97cd8c31af Author: Dave Johnson dmjohn...@apigee.com Date: 2014-08-14T21:53:18Z Set Tomcat threads and memory based on AWS instance type. commit 5878b4060fca47fc9068e8a5cd5285f9fb9f7941 Author: Dave Johnson dmjohn...@apigee.com Date: 2014-08-14T21:54:07Z Property settings to allow Core and Services tests to run (and succeed) consistently, REST still needs some work. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] incubator-usergrid pull request: AWSCluster and test fixes.
Github user asfgit closed the pull request at: https://github.com/apache/incubator-usergrid/pull/49 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
Re: Using Jira as a mechanism for Tracking Usergrid Progress
+1 for using JIRA. People like to hate it, but it does the job. - Dave On Thu, Aug 14, 2014 at 12:55 PM, Lewis John Mcgibbney lewis.mcgibb...@gmail.com wrote: Hi Folks, I thought I would put this one out there as we build up to the 1.0 release. Is there any motivation for us to use Jira as an issue tracker? I know that there is some material going on to Jira but I also see a lot not going on there. One aspect of Jira which I find extremely useful is the ability to generate release reports which we can then distribute with the release announcement. An example can be found here http://s.apache.org/1.9-release Which I recenly included within the CHANGES.txt for Apache Nutch release candidate https://dist.apache.org/repos/dist/dev/nutch/1.9/CHANGES.txt -- *Lewis*
Re: Using Jira as a mechanism for Tracking Usergrid Progress
+1 agreed. On Thursday, August 14, 2014, Dave snoopd...@gmail.com wrote: +1 for using JIRA. People like to hate it, but it does the job. - Dave On Thu, Aug 14, 2014 at 12:55 PM, Lewis John Mcgibbney lewis.mcgibb...@gmail.com javascript:; wrote: Hi Folks, I thought I would put this one out there as we build up to the 1.0 release. Is there any motivation for us to use Jira as an issue tracker? I know that there is some material going on to Jira but I also see a lot not going on there. One aspect of Jira which I find extremely useful is the ability to generate release reports which we can then distribute with the release announcement. An example can be found here http://s.apache.org/1.9-release Which I recenly included within the CHANGES.txt for Apache Nutch release candidate https://dist.apache.org/repos/dist/dev/nutch/1.9/CHANGES.txt -- *Lewis* -- https://pages.apigee.com/i-love-apis-2014.html?utm_source=sigutm_medium=email
Re: push messaging
Hi I've come up with the design on how I'm adding push messaging so If any one how intrested is using this or having it added to main repo please comment on design any idea are welcome . 1- push message notifiers will be attached to groups and each application will get a default notifier that will message all devices for the application (no need to create two notifier just to message iOS or android). 2- will add a push messaging service to the services module. 3 - will add a messaging endpoint to the REST module. (for registering device for push and for trigger , etc) 4 - will add some tests to test service and rest code. 5 - will add to android and iOS sdks so device can handle push and register for push. Im also starting with HTTP access to Android push messaging if I have time or at a latter time I'll add CCS (XMPP) . One thing Ive not decided on is if we should add a Model File to the Core module any input on that would be helpful . Please fell free to look at my fork on bitbucket as the we work on this Im hoping this won't take more then a week Ive put two other guys on it with my self. all are welcome to comment, help ,etc Will use com.notnoop.apns and google.gcm.server August 14 2014 2:01 PM, jas...@apps4u.com.au wrote: that Ok Ive started mine yesterday and engaged 2 programmers yesterday to start so I know I'll be done within a week . So I'll leave to other to decide wether they take my pull request. I don't know your timeline is but with out push this is really not something that can be called turnkey as its the most requested feature of and mobile BaaS. Also I don't really like having two different notifiers for one application one for iOS and one for Android . It would be easy to integrate this with AWS message service as it has the same feature as APIGee push messaging. Which I thought was just AWS SNS. August 14 2014 1:01 AM, Todd Nine todd.n...@gmail.com wrote: Hey Jason, We've already build this at Apigee. We're in the process of contributing it back, but I'm not sure on the timeline of this. It's stable and been in production use for some time. Below is the documentation and the API overview. http://apigee.com/docs/app-services/content/push-notifications-overview We've found our api works well and it's easy for our users to understand and get set up. Internally, we're using our scheduler to perform large batch delivery, and the master/worker distribution semantics to increase the delivery throughput. For the push clients, we're using these libraries iOs https://github.com/relayrides/pushy/tree/master Android https://developer.android.com/google/gcm/client.html Let me know if you have any more question. Later, Todd On Wed, Aug 13, 2014 at 12:11 AM, Matthias Wessendorf mat...@apache.org wrote: On Wed, Aug 13, 2014 at 7:57 AM, jas...@apps4u.com.au wrote: I was thinking that I would use these two packages as Ive got existing code using these two libraries and Ive got client side code that would not take long to add the the ios and Android SDK's that was I get auth for free from the sdk's usergrid and the queue server can be a option either iron.io or beanstalk . com.google.android.gcm.server http://notnoop.github.com/java-apns yep - we, internally, use the same bits August 13 2014 3:44 PM, jas...@apps4u.com.au wrote: Im get one of my team members to download your code and have a look weather this would could be integrated into usergrid. August 13 2014 3:36 PM, Matthias Wessendorf mat...@apache.org wrote: Hello Jason, perhaps you can integrate our UnifiedPush Server (e.g. running on a different box, or on Openshift). It supports the concept of Application: http://staging.aerogear.org/docs/unifiedpush/ups_userguide/admin-ui/#_sending_a_push_notification You can even narrow down to specific platforms (we call them Variants), e.g. just ping all Android (or iOS) users of the Application -Matthias On Wed, Aug 13, 2014 at 7:30 AM, jas...@apps4u.com.au wrote: HI I'm wanting to add push messaging to usergrid I would like to submit a pull request once its done but I wanted to get some input form the dev team on my Idea as I would like to submit a pull request , The Idea I had for push messaging is a bit different to how ApiGee has implemented it I want to have notifiers but in context to a Application so instead of having notifiers for each type of device I want to have notifier for applications . Also the current code I have user queues to queue up the messages using either iron,io or beanstalk . Please let me know if this is not something that would be accepted as a pull request and if any body has any input please respond, I should have a pull request ready within a week. -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf
[jira] [Created] (USERGRID-216) GET an non-exists entity by ID or Name throws 401 if no authorisation is required
Strong Liu created USERGRID-216:
---
Summary: GET an non-exists entity by ID or Name throws 401 if no
authorisation is required
Key: USERGRID-216
URL: https://issues.apache.org/jira/browse/USERGRID-216
Project: Usergrid
Issue Type: Story
Reporter: Strong Liu
for example
get /sandbox/users/non-exist-username throws 401 error code
this is because below code
{code}
@Provider
public class ServiceResourceNotFoundExceptionMapper extends
AbstractExceptionMapperServiceResourceNotFoundException {
@Override
public Response toResponse( ServiceResourceNotFoundException e ) {
if ( SubjectUtils.getSubjectUserId() == null ) {
return toResponse( UNAUTHORIZED, e );
}
else {
return toResponse( NOT_FOUND, e );
}
}
}
{code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
