You can try searching for your commits on all branches:
git log --all --author=
On Tue, Dec 22, 2015 at 10:59 AM, Perumal, Nithin
wrote:
> I've looked at my fork, but due to the sheer number of branches - I'm not
> sure which branch my code was committed too.
>
>
>
This is huge for us!
Thank you Thomas and big kudos to everyone in the Apex community, and our
mentors, Chris, Alan, Hitesh, Justin, Taylor, and Ted!!
David
On Mon, Apr 25, 2016 at 9:41 AM, Thomas Weise
wrote:
> Dear Community,
>
> Apex graduation was approved by the ASF board last week and the
Hi Ananth,
Can you do an "unzip -t" on your apa file and paste the output here?
Make sure the jar containing the application classes should be in the app
directory inside the apa.
Can I know why the apex-app-archetype is not used in your apa project?
David
On Thu, Apr 28, 2016 at 2:53 PM, Anant
class
>
> com.threatmetrix.dataplatform.storage.apps.cassandra.eventdetails.CassandraEventDetailsStreamingApp
> An alias for the application
>
>
> dt.operator.*.attr.MEMORY_MB
> 512
>
>
>
>
> dt.application.CED.operator.eventDetailsFormatter.attr.PARTITIONER
; icon next to it. All I see is the top level packaged
> name in the web console but nothing beneath it for me to trigger a launch.
>
> Regards,
> Ananth
>
> On Fri, Apr 29, 2016 at 8:27 AM, David Yan wrote:
>
>> Hi Ananth,
>>
>> The MANIFEST.MF file is im
;> working fine when uploading it but the moment I add in my code and
>>>> dependencies it goes back the issue I am seeing :
>>>>
>>>>
>>>> My app package looks like app.zip ( I removed all of the
>>>> application.class for brevity
Hi Ananth,
This error indicates that dtGateway has trouble accessing the app master.
Can you check the app master log for application_1462007878015_0037?
David
On Mon, May 2, 2016 at 4:27 AM, Ananth Gundabattula wrote:
> Hello All,
>
> I am trying to launch my app on Apex/DT 3.3 version runnin
Hi Sai:
Can you monitor the dtgateway.log file and send us the possible stack trace
that is causing the error?
David
On Mon, May 2, 2016 at 5:28 PM, Amol Kekre wrote:
>
> Sai,
> I am redirecting this thread to users@apex. Do subscribe to users@ email.
> See http://apex.apache.org/community.html
; first few hours. I believe the error started occuring in the first few
> minutes of launching the app itself as described in the mail above.
>
>
>
> Regards,
> Ananth
>
>
>
> On Tue, May 3, 2016 at 1:53 AM, David Yan wrote:
>
>> Hi Ananth,
>>
>> T
questHandler.headerComplete(HttpConnection.java:928)
>> at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:549)
>> at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)
>> at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
>> at
>>
jetty.Server.handle(Server.java:326)
>> at
>> org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542)
>> at
>> org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:928)
>> at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:549)
>> at org.mortbay.jetty.Ht
Hi all,
With the imminent release of Apex Core 3.4.0, I'd like to bring up some
backward compatibility issues between Apex 3.3.x and 3.4.x:
- Because we needed to fix an important security issue of a 3rd party
library that we use, Apex apps that use WebSockeInputOperator and
WebSocketOutputOperat
12 matches
Mail list logo
