ument what I was seeing well enough
before my VM froze and I decided to call it a night. After I finish
another task I could return to this debugging session.
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/554#comment:11>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
me.
I am curious why it works in your setup :)
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/554#comment:12>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
I grep'ed around the
!AccountManager codebase for interaction with `Session`, it did not look
like it could be involved. I wouldn't be surprised if that conclusion was
incorrect though.
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/554#comment:13>
ticket/554#comment:14>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
e and display a custom
message «Product %s not found».//
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/561>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
ase 6"] and we don't yet have a patch.
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/529#comment:5>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
61#comment:1>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
: multiproduct |Version:
Resolution:| Keywords:
---+---
Changes (by rjollos):
* component: dashboard => multiproduct
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/561#comment:2>
Apache Bloodhou
rt=8000 --basic-auth="lastvisit,/.../.htpasswd,bloodhound"
lastvisit
}}}
In both, the last_visit time is only updated on the first login. If I
manually set it to 0, another login does not change it.
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/554#comment:15>
Apache B
| Keywords:
--+-
Changes (by astaric):
* status: new => closed
* resolution: => fixed
Comment:
Implemented in r1493719.
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/559#comment:1>
Apache Bloodhound <https://is
nt:2>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
hound/ticket/561#comment:3>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
items related to products in index
page.
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/562>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
list.
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/563>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
t URL: <https://issues.apache.org/bloodhound/ticket/561#comment:4>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
:
--+
Changes (by olemis):
* status: new => closed
* resolution: => duplicate
* component: => dashboard
Comment:
Posted twice . Sorry . See #562
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/563#comment:1>
Apache Bl
: <https://issues.apache.org/bloodhound/ticket/561#comment:5>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
Ticket URL: <https://issues.apache.org/bloodhound/ticket/562#comment:1>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
:
Resolution:| Keywords: hooks
---+--
Changes (by olemis):
* owner: nobody => olemis
* status: new => accepted
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/541#comment:2>
Apache Bloodhound <https://is
-
Ticket URL: <https://issues.apache.org/bloodhound/ticket/541#comment:3>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
(see comment:3:ticket:541 )
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/561#comment:6>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
the links seem to direct to the default handler
for the product.
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/561#comment:7>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
ment:1>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
ttp://www.python.org/dev/peps/pep-0001/
- 2. PEP 9, Sample Plaintext PEP Template, Warsaw
- http://www.python.org/dev/peps/pep-0009
- 2. PEP 12, Sample reStructuredText ''PEP'' Template, Goodger, Warsaw
- http://www.python.org/dev/peps/pep-0012/
- 3. http://www.openconte
line]]
---8<--8<--8<--8<--8<--8<--8<--8<
--
Page URL: <https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0009>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
This i
7;''Content-Type''' || [wiki:PageTemplates/Proposals text/x-trac-wiki] ||
-|| '''Created''' || ||
-|| '''Post-History''' || ||
+|| '''Type''' || ||
+|| '''Content-Type''' || text/x-trac-wiki||
+|| '''Created''' || ||
+|| '''Post-History''' || ||
---8<--8<--8<--8<--8<--8<--8<--8<
--
Page URL: <https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0009>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
This is an automated message. Someone added your email address to be
notified of changes on 'Proposals/BEP-0009' page.
If it was not you, please report to .
Author''' || Pranay ||
|| '''Status''' || Draft ||
|| '''Type''' || ||
-|| '''Content-Type''' || text/x-trac-wiki||
+|| '''Content-Type''' ||text/x-trac-wiki||
||
jor => minor
Comment:
(In [1494718])
Fixes #558: Show a message on the Basic Settings admin panel when `pytz`
is not installed.
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/558#comment:2>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
custom bootstrap
handlers .
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/561#comment:8>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
e stated that the patch for that ticket is built on the patch
in #561, but you submitted the patch for this ticket before #541 and
comment:4 doesn't indicate that the patch in #541 is required.
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/561#comment:9>
.blood-hound.net/
http://dataviz.blood-hound.net/products/dataviz
http://dataviz.blood-hound.net/dashboard
it's work in progress though ;)
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/561#comment:10>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
ct misconfiguration (i.e. the subject of #541) the request
will be handled by the global environment directly . The few issues caused
by this will be fixed by the patch(es) submitted for #541 .
I'll provide an updated version for both patches asap .
--
Ticket URL: <https://issues.apac
eemed like
`process_request` could be refactored a bit to simplify the code.
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/561#comment:12>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
ot be reflected in
TitleIndex . After sending `HUP` signal to ''apache2'' server everything
works as expected .
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/539#comment:3>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
s not installed.
}}}
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/541#comment:4>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
icket:541 new patch] for #541 has been tested against
this one . Both issues are related .
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/561#comment:13>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
.]
Of course , if you share it I'll take a look ;)
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/561#comment:14>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
messed up. Widget elements
are not positioned correctly, there's overlapping, etc ...
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/565>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
sions, milestones and components
vary depending on request environment context. Corresponding widgets have
to be explicitly scoped to consistently reflect the state of target
product.
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/564>
Apache Bloodhound <https://issues.apache.
ponent: => dashboard
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/564#comment:1>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
and summarized values differ, product
widgets in global dashboard tend to be misaligned.
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/566>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
ut.png)]]
--
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/565#comment:1>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
L: <https://issues.apache.org/bloodhound/ticket/566#comment:1>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
t seems to be the same root cause.
--
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/552#comment:3>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
will be an
"empty" dashboard, regardless of whether they permission to access
`prod2`. Also, a user can see the list of all products by accessing
`/products/prod1/products/`.
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/561#comment:15>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
;PRODUCT_VIEW privileges are
required to perform this operation on Product None. You don't have the
required permissions.'' when accessing `/products` or
`/products/prod1/products`.
> Also, a user can see the list of all products by accessing
`/products/prod1/products/`.
P
`prod2`, and may be something we want to avoid.
* Really what we need are some functional tests here, so the code can be
properly refactored!
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/561#comment:17>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
:
- Request handling in product web module #541 and #561
... more will be added later
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/567>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
ugin? Does Trac properly
update `last_visit` if there hasn't been a login for > 24 hours?
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/554#comment:16>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
=> nobody
* milestone: => Release 7
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/567#comment:1>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
nd/ticket/541#comment:5>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
hanged the default
Product name.
All the tickets that cannot be viewed seem to have the new Product (I've
looked in the db with sqlite3). This seems like it might be related.
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/568>
Apache Bloodhound <https://issues.apa
cribe.
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/541#comment:6>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
is.
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/568#comment:1>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
ber of the ticket that was created, if necessary.
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/569>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
d behavior?
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/569#comment:1>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
redictably useful experience.
We should simply default to the current product in the relevant drop down
within the quick ticket dialogue.
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/569#comment:2>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The A
efault to the `default_product`? Or default to the product in
the current scope?
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/569#comment:3>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
rg/bloodhound/ticket/541#comment:7>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
#comment:4>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
actory misconfiguration. Patch
by Olemis.
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/513#comment:5>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
: <https://issues.apache.org/bloodhound/ticket/514#comment:8>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
leware for custom web bootstrap
handlers. Patch by Olemis.
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/514#comment:9>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
template is needed to replace `product_edit.html`.
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/570>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
k ticket form to be scoped considering active product
context, or at least default values set consistently.
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/569#comment:4>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
and you'll notice .
Anyway these changes deal with some inconsistencies dealing not solved by
the solution proposed for #561 .
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/541#comment:8>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
n-existent product?
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/541#comment:9>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
New user registration for user nokia6
--
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
: <https://issues.apache.org/bloodhound/ticket/571>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
to
manually update the last_visit time.
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/554#comment:17>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
hen I can
reproduce the issue by setting `[multiproduct] default_product_prefix` to
a non-existent product?
At least [comment:1 when I reported this ticket] that's what was happening
to me.
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/541#comment:10>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
permissions).
trac:TracFineGrainedPermissions should also be included in permission
check.
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/572>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
org/bloodhound/ticket/541#comment:11>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
I understand
correctly, QCT should default to the product in the current scope, but
still allow selection of other products. And when invoked in the global
scope, it should default to the default_product.
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/569#comment:5>
Apach
Deleted User for user nokia6
--
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
tps://issues.apache.org/bloodhound/ticket/571#comment:1>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
8<--8<--8<--8<----
--
Page URL: <https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0008>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
This is an automated message. Someone added your email address to be
notified of changes on 'Proposals/BEP-0008' page.
If it was not you, please report to .
lt;--8<--8<--8<--8<--8<--8<----
--
Page URL: <https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0009>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
This is an automated message. Someone added your email address to be
notified of changes on 'Proposals/BEP-0009' page.
If it was not you, please report to .
07&col=id&col=summary&col=status&col=priority&col=milestone",
title=BEP 7 ticket summary)]]
== Resources #resources
---8<--8<--8<--8<--8<--8<--8<--8<----
--
Page URL: <https://issues.apache.org/bloodhound/wik
way.
New description:
The issue is described in detail in trac:#11102, and affects Bloodhound in
the same way.
--
Comment:
Committed to Trac in [t 11827] and [t 11828].
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/446#comment:3>
Apache Bloodhound <https://issues.apa
may be added in that ticket. I'll wait for feedback today
before making these changes.
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/569#comment:6>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
:
+
Comment (by rjollos):
To fix the issue, make the following edit in trac.ini:
{{{#!ini
[ticket]
default_product = @
}}}
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/568#comment:2>
Apache Bloodhound <https://issues.apache.org/bloodho
elease 6
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/569#comment:7>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
cket/568#comment:3>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
-)
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/569#comment:8>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
ticket/556#comment:1>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
braces so that the tickets list will be actually rendered.>
+
+{{{
+[[Widget(TicketQuery, query="keywords=~bep-&col=id&col=summary&col=status&col=priority&col=milestone", title=BEP
ticket summary)]]
+}}}
== Resources #resources
---8<------8<------8&l
ol=status&col=priority&col=milestone", title=BEP
ticket summary)]]
---8<--8<--8<--8<--8<--8<--8<--8<
--
Page URL: <https://issues.apache.org/bloodhound/wiki/PageTemplates/Proposals>
Apache Bloodhound <https://issues.apache.o
.
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/573>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
| Milestone:
Component: plugins |Version:
Resolution:| Keywords: bep-0007
---+--
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/573#comment:1>
Apache Bloodhound <https://issues.apache.org/b
New user registration for user cst
--
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
t_ticket_prefix` is set to a
prefix that doesn't exist.
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/569#comment:9>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
functionality for reports:
Display historical changes for a specific ticket according to the given
ticket no/keywords
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/574>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
: | Keywords: qct
+---
Comment (by rjollos):
I had incorrectly specified the option in comment:2, but I've since edited
it to correct.
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/568#comment:4>
Apache Bloodhound <https://iss
ciated with the first product in the sorted list of products (which
will most likely be the product with prefix `@`).
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/568#comment:5>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
Ticket 1 does not exist.
The URL will be `/products/prod2/ticket/1`.
Navigate to `/products/prod1/ticket/1` to find the ticket, replacing `1`
with the number of the ticket that was created, if necessary.
--
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/569#comment:10>
A
: | Keywords: BEP-0008
+--
Changes (by huaxiang):
* keywords: => BEP-0008
* owner: => nobody
* component: => dashboard
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/574#comment:1>
Apache Bl
roperly populated, even when
`[multiproduct] default_product_prefix` is invalid.
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/569#comment:11>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
Resolution: | Keywords: AccountManager
--+
Changes (by rjollos):
* priority: critical => major
* milestone: Release 6 => Release 7
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/554#comment:18>
Apache Bloodhound <
601 - 700 of 1820 matches
Mail list logo
