Hi Deepak,
Great! at least the mystery is out. Thank you for the clarification.
Can we trigger a manual sync ourselves or is this something affecting all
projects and thus only available to infra? I will follow up on that JIRA
meanwhile.
On Jan 8, 2018 9:38 AM, "Deepak Dixit"
There are some issue at infra level in pussub service that sync svn with
github. Due to this svn to github auto synching not working.
Infra team is looking into it.Here is the issue for pubsub sync
https://issues.apache.org/jira/browse/INFRA-15806
Admin team did manual sync and now its updated
Oops here is correct link
https://issues.apache.org/jira/servicedesk/agent/INFRA/issue/INFRA-15686
http://markmail.org/message/2vy3tprutqe5hqti
http://markmail.org/message/ange7ygquw7vc22v
Thanks & Regards
--
Deepak Dixit
www.hotwaxsystems.com
www.hotwax.co
On Mon, Jan 8, 2018 at 11:42 AM,
Its already reported
https://f.apache.org/jira/servicedesk/agent/INFRA/issue/INFRA-15686
Thanks & Regards
--
Deepak Dixit
www.hotwaxsystems.com
www.hotwax.co
On Mon, Jan 8, 2018 at 4:08 AM, Jacques Le Roux <
jacques.le.r...@les7arts.com> wrote:
> AFAIK, we don't have a Jira about that.
>
> For
I'm in favor of the status quo. It's useful to have them available out of
the box to be able to pick the one you need and proceed without having to
look elsewhere. The same goes for the fieldtype definitions.
Regards
Scott
On 8/01/2018 6:26 AM, "Pierre Smits" wrote:
We
Le 07/01/2018 à 21:08, Taher Alkhateeb a écrit :
Sorry, I'm not sure what you mean by a transient error?
A test error which happens only once. The same code (no commits between) is
used few minutes later and it works.
If you want to know more about possible such issues please ask infra.
I
AFAIK, we don't have a Jira about that.
For Infra issues, we are requested to pass by
https://issues.apache.org/jira/servicedesk/customer/portal/1/create/3 or for
quick things Hipchat room.
Maybe though for such a long term request (documentation) the infra ML can be
used (but I think Jira
I'm not against strictly against removing exampleext (maybe merging some part in example ). But then what it not clearly tries to explain (misc.
extension mechanisms) should be clearly documented!
For commonext I need to look at it again but at 1st glance it seems redundant indeed and could be
I'm not familiar with commonext or exampleext, but the purpose of the
entity-ext component was to allow the entity engine to exist without the
service engine. That's why all the entity-related logic that relies on the
service engine is implemented there (EECAs, EntitySync, DCC). The
alternative
I think all -ext components (entityext, commonext, exampleext) are
redundant and do not add value. Any patches to fix this issue and
merge these components would be great.
On Sun, Jan 7, 2018 at 9:38 PM, Pierre Smits wrote:
> Hi all,
>
> The ExampleExt components
If anyone has information to share that would be great, or at least as
Michael pointed out if you know any documentation anywhere that can
help us identify how mirroring is done so we can resolve the issue
ourselves in the future then we can resolve this more quickly.
Perhaps we should start a
Sorry, I'm not sure what you mean by a transient error? How did you
determine that it is a transient error, and did you identify what is
causing it? Why are we having more of these errors than in the past?
On Sun, Jan 7, 2018 at 8:41 PM, Jacques Le Roux
wrote:
> Le
Hi all,
The ExampleExt components provides functionality to extend widgets across
components. In this solution, the ExampleExt component has form widgets
extending similar widgets in the Example component.
This kind of functionality (both within one component and across, and with
more variants)
Similarly to the OFBiz project, INFRA is for the greater part staffed with
volunteers (but I may have outdated insights). More often than not, and due
to the inability to enforce volunteers (with commitments beyond the
project) to take action on something they do not desire) this leads to a
Le 07/01/2018 à 18:41, Jacques Le Roux a écrit :
A request is of the form
"force build ofbizTrunkFrameworkPlugins"
you put the text you want to appear after this expression, something like
"forces manual build after Buildbot weird 85 errors on labels :-o"
Forgot to say that with our last config
Le 07/01/2018 à 15:44, Taher Alkhateeb a écrit :
I am suspecting this is still a broken build system rather than a
genuine error. Can you confirm?
It's not a "broken build system" but was a transient error as you can see there
https://ci.apache.org/builders/ofbizTrunkFrameworkPlugins
If tests
We could consider having example configurations (entityengine.xml files)
for applicable database solutions in the documentation (in confluence).
Removing unused code snippets is always worth the effort put forward.
Best regards,
Pierre Smits
V.P. Apache Trafodion
On Sun, Jan 7, 2018 at 5:36
Le 07/01/2018 à 11:43, Jacques Le Roux a écrit :
My answer to your question is: we should keep them of course, except if a
better way would be proposed, I see none for now...
I must have said: I see none PROVIDED for now...
We could consider a modular solution which would include split parts
So far I simply got to the Infra HipChat room and asked there.
Very successful most of the time, but not documented apart some messages I sent to this ML and bookmarks I kept on them for myself, like "[FYI] Let's
encrypt certificate renewal failed"
Note that with infra things are moving fast
Hi Jacopo,
a little late but thank you for putting together the new release and thanks to
all who contributed!
Best regards,
Michael
Am 03.01.18 um 18:12 schrieb Jacopo Cappellato:
The Apache OFBiz community is pleased to announce the new release "Apache
OFBiz 16.11.04".
Apache OFBiz® is
BTW, do we have documentation somewhere which explains who is
responsible for these services, how they work, where to lokk what's
wrong and who to inform if there are issues?
To me this is not clear for some of the services (like publishing the
website, fisheye, GitHub sync, ...) , but I
It seems that is not the only service lagging in providing correct results.
The same applies to fisheye. See
https://fisheye.apache.org/browse/ofbiz/ofbiz-framework/trunk
Best regards,
Pierre Smits
V.P. Apache Trafodion
On Sun, Jan 7, 2018 at 3:47 PM, Taher Alkhateeb
Hey folks, it seems we still have this delay in our git account. Any
idea how to resolve this and why does it keep happening?
I am suspecting this is still a broken build system rather than a
genuine error. Can you confirm? If tests are running okay locally then
we still have a faulty build logic.
On Sun, Jan 7, 2018 at 5:20 PM, wrote:
> The Buildbot has detected a new failure on builder
Hi everyone,
Only did a quick look at the 2 patches.
I think the improvement is incomplete and effectively removed the datasource
configurations like MSSQL, MySQL, Oracle etc. Developers (like me) using these
databases will require additional work to find and apply the missing
configurations.
Michael,
We crossed on wire. I put a comment just after yours in the Jira it's not an
answer to your questions but my thoughts at large.
My answer to your question is: we should keep them of course, except if a
better way would be proposed, I see none for now...
Jacques
Le 07/01/2018 à
Hi everyone,
please have a look at the issue mentioned below and express your
opionion if we should remove the different schema configurations from
the main entityengine.xml or if we should keep them.
Thanks,
Michael
Am 07.01.18 um 11:23 schrieb Pierre Smits (JIRA):
[
27 matches
Mail list logo