Check with Red Hat - re:using the Annex on saturday September 22

Currently, it is available on Sept 22

Do we have it booked then for 21-22?  I know there was a question about
having a security guard present.
If not booked. Let’s book it.
On Tue, Jun 5, 2018 at 3:56 PM Jason Hibbets<EMAIL_ADDRESS>wrote:

Currently, it is available on Sept 22
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/ncopenpass/NCOpenPass/issues/1046#issuecomment-394839699,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAOGtfPafV0XGeTFHDTcz-UHEk5QBIJSks5t5uJ9gaJpZM4UasBV
.

--
Chris Mathews

Not that I have any hot leads but would folks want to go with Red Hat then?
I dont mind at all. I'm just asking so I can stop putting out feelers for
alternatives. The annex sounds great and makes it easy to plan around.
Let me know, don't want to duplicate effort.
On Tue, Jun 5, 2018, 4:09 PM Chris Mathews<EMAIL_ADDRESS>wrote:

Do we have it booked then for 21-22? I know there was a question about
having a security guard present.
If not booked. Let’s book it.
On Tue, Jun 5, 2018 at 3:56 PM Jason Hibbets<EMAIL_ADDRESS>wrote:

Currently, it is available on Sept 22
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
<
https://github.com/ncopenpass/NCOpenPass/issues/1046#issuecomment-394839699
,
or mute the thread
<
https://github.com/notifications/unsubscribe-auth/AAOGtfPafV0XGeTFHDTcz-UHEk5QBIJSks5t5uJ9gaJpZM4UasBV
.

--
Chris Mathews
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ncopenpass/NCOpenPass/issues/1046#issuecomment-394843394,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AB3Ie9aLSjLgMvx-C8qtezQXNq_3GnXvks5t5uVigaJpZM4UasBV
.

We can wait until the monthly meeting to decide and put it to a vote. Does
that give you time to make sure we don't have other options?
I want to make sure we give Red Hat enough lead time.
Chris Mathews
On Tue, Jun 5, 2018 at 7:06 PM, Leo Suarez<EMAIL_ADDRESS>wrote:

Not that I have any hot leads but would folks want to go with Red Hat then?
I dont mind at all. I'm just asking so I can stop putting out feelers for
alternatives. The annex sounds great and makes it easy to plan around.
Let me know, don't want to duplicate effort.
On Tue, Jun 5, 2018, 4:09 PM Chris Mathews<EMAIL_ADDRESS>wrote:

Do we have it booked then for 21-22? I know there was a question about
having a security guard present.
If not booked. Let’s book it.
On Tue, Jun 5, 2018 at 3:56 PM Jason Hibbets<EMAIL_ADDRESS>wrote:

Currently, it is available on Sept 22
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
<
https://github.com/ncopenpass/NCOpenPass/issues/1046#
issuecomment-394839699
,
or mute the thread
<
https://github.com/notifications/unsubscribe-auth/AAOGtfPafV0XGeTFHDTcz-
UHEk5QBIJSks5t5uJ9gaJpZM4UasBV
.

--
Chris Mathews
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<https://github.com/ncopenpass/NCOpenPass/issues/
1046#issuecomment-394843394>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AB3Ie9aLSjLgMvx-
C8qtezQXNq_3GnXvks5t5uVigaJpZM4UasBV>
.

—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/ncopenpass/NCOpenPass/issues/1046#issuecomment-394888296,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAOGtVfzRaMSeGlmwxA__rUHaRK7r30Bks5t5w7ngaJpZM4UasBV
.

Makes sense. Yes, let me work a few leads before the next meeting. Like I
said, nothing is promising at this time. Thank you for pushing on this
actually! ;)
On Tue, Jun 5, 2018 at 7:45 PM, Chris Mathews<EMAIL_ADDRESS>wrote:

We can wait until the monthly meeting to decide and put it to a vote. Does
that give you time to make sure we don't have other options?
I want to make sure we give Red Hat enough lead time.
Chris Mathews
On Tue, Jun 5, 2018 at 7:06 PM, Leo Suarez<EMAIL_ADDRESS>wrote:

Not that I have any hot leads but would folks want to go with Red Hat
then?
I dont mind at all. I'm just asking so I can stop putting out feelers for
alternatives. The annex sounds great and makes it easy to plan around.
Let me know, don't want to duplicate effort.
On Tue, Jun 5, 2018, 4:09 PM Chris Mathews<EMAIL_ADDRESS>wrote:

Do we have it booked then for 21-22? I know there was a question about
having a security guard present.
If not booked. Let’s book it.
On Tue, Jun 5, 2018 at 3:56 PM Jason Hibbets<EMAIL_ADDRESS>

wrote:

Currently, it is available on Sept 22
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
<
https://github.com/ncopenpass/NCOpenPass/issues/1046#
issuecomment-394839699
,
or mute the thread
<
https://github.com/notifications/unsubscribe-
auth/AAOGtfPafV0XGeTFHDTcz-
UHEk5QBIJSks5t5uJ9gaJpZM4UasBV
.

--
Chris Mathews
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<https://github.com/ncopenpass/NCOpenPass/issues/
1046#issuecomment-394843394>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AB3Ie9aLSjLgMvx-
C8qtezQXNq_3GnXvks5t5uVigaJpZM4UasBV>
.

—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
<https://github.com/ncopenpass/NCOpenPass/issues/
1046#issuecomment-394888296>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAOGtVfzRaMSeGlmwxA__
rUHaRK7r30Bks5t5w7ngaJpZM4UasBV>
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/ncopenpass/NCOpenPass/issues/1046#issuecomment-394895256,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AB3Ie26wH8X3NInL8_9lC-dJrYSGyeHaks5t5xgTgaJpZM4UasBV
.

Just to throw another wrinkle into the mix.
If we don’t pick a downtown Raleigh location -or relatively downtown
location - for CivicCamp we may not “qualify” to be part of the Raleigh
M.A.I.N. event promotion.
On Tue, Jun 5, 2018 at 7:57 PM Leo Suarez<EMAIL_ADDRESS>wrote:

Makes sense. Yes, let me work a few leads before the next meeting. Like I
said, nothing is promising at this time. Thank you for pushing on this
actually! ;)
On Tue, Jun 5, 2018 at 7:45 PM, Chris Mathews<EMAIL_ADDRESS>wrote:

We can wait until the monthly meeting to decide and put it to a vote.
Does
that give you time to make sure we don't have other options?
I want to make sure we give Red Hat enough lead time.
Chris Mathews
On Tue, Jun 5, 2018 at 7:06 PM, Leo Suarez<EMAIL_ADDRESS>wrote:

Not that I have any hot leads but would folks want to go with Red Hat
then?
I dont mind at all. I'm just asking so I can stop putting out feelers
for
alternatives. The annex sounds great and makes it easy to plan around.
Let me know, don't want to duplicate effort.
On Tue, Jun 5, 2018, 4:09 PM Chris Mathews<EMAIL_ADDRESS>wrote:

Do we have it booked then for 21-22? I know there was a question
about
having a security guard present.
If not booked. Let’s book it.
On Tue, Jun 5, 2018 at 3:56 PM Jason Hibbets <
<EMAIL_ADDRESS>

wrote:

Currently, it is available on Sept 22
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
<
https://github.com/ncopenpass/NCOpenPass/issues/1046#
issuecomment-394839699
,
or mute the thread
<
https://github.com/notifications/unsubscribe-
auth/AAOGtfPafV0XGeTFHDTcz-
UHEk5QBIJSks5t5uJ9gaJpZM4UasBV
.

--
Chris Mathews
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<https://github.com/ncopenpass/NCOpenPass/issues/
1046#issuecomment-394843394>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AB3Ie9aLSjLgMvx-
C8qtezQXNq_3GnXvks5t5uVigaJpZM4UasBV>
.

—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
<https://github.com/ncopenpass/NCOpenPass/issues/
1046#issuecomment-394888296>,
or mute the thread
<
https://github.com/notifications/unsubscribe-auth/AAOGtVfzRaMSeGlmwxA__
rUHaRK7r30Bks5t5w7ngaJpZM4UasBV>
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<
https://github.com/ncopenpass/NCOpenPass/issues/1046#issuecomment-394895256
,
or mute the thread
<
https://github.com/notifications/unsubscribe-auth/AB3Ie26wH8X3NInL8_9lC-dJrYSGyeHaks5t5xgTgaJpZM4UasBV
.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ncopenpass/NCOpenPass/issues/1046#issuecomment-394897271,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AK4rpq46c01JHotggBvUYJr9GJYS5hWpks5t5xr8gaJpZM4UasBV
.

That's good to know. :)
On Wed, Jun 6, 2018 at 9:59 AM, Janel<EMAIL_ADDRESS>wrote:

Just to throw another wrinkle into the mix.
If we don’t pick a downtown Raleigh location -or relatively downtown
location - for CivicCamp we may not “qualify” to be part of the Raleigh
M.A.I.N. event promotion.
On Tue, Jun 5, 2018 at 7:57 PM Leo Suarez<EMAIL_ADDRESS>wrote:

Makes sense. Yes, let me work a few leads before the next meeting. Like I
said, nothing is promising at this time. Thank you for pushing on this
actually! ;)
On Tue, Jun 5, 2018 at 7:45 PM, Chris Mathews<EMAIL_ADDRESS>wrote:

We can wait until the monthly meeting to decide and put it to a vote.
Does
that give you time to make sure we don't have other options?
I want to make sure we give Red Hat enough lead time.
Chris Mathews
On Tue, Jun 5, 2018 at 7:06 PM, Leo Suarez<EMAIL_ADDRESS>wrote:

Not that I have any hot leads but would folks want to go with Red Hat
then?
I dont mind at all. I'm just asking so I can stop putting out feelers
for
alternatives. The annex sounds great and makes it easy to plan
around.
Let me know, don't want to duplicate effort.
On Tue, Jun 5, 2018, 4:09 PM Chris Mathews<EMAIL_ADDRESS>

wrote:

Do we have it booked then for 21-22? I know there was a question
about
having a security guard present.
If not booked. Let’s book it.
On Tue, Jun 5, 2018 at 3:56 PM Jason Hibbets <
<EMAIL_ADDRESS>

wrote:

Currently, it is available on Sept 22
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
<
https://github.com/ncopenpass/NCOpenPass/issues/1046#
issuecomment-394839699
,
or mute the thread
<
https://github.com/notifications/unsubscribe-
auth/AAOGtfPafV0XGeTFHDTcz-
UHEk5QBIJSks5t5uJ9gaJpZM4UasBV
.

--
Chris Mathews
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<https://github.com/ncopenpass/NCOpenPass/issues/
1046#issuecomment-394843394>,
or mute the thread
<https://github.com/notifications/unsubscribe-
auth/AB3Ie9aLSjLgMvx-
C8qtezQXNq_3GnXvks5t5uVigaJpZM4UasBV>
.

—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
<https://github.com/ncopenpass/NCOpenPass/issues/
1046#issuecomment-394888296>,
or mute the thread
<
https://github.com/notifications/unsubscribe-auth/AAOGtVfzRaMSeGlmwxA__
rUHaRK7r30Bks5t5w7ngaJpZM4UasBV>
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<
https://github.com/ncopenpass/NCOpenPass/issues/1046#
issuecomment-394895256
,
or mute the thread
<
https://github.com/notifications/unsubscribe-auth/AB3Ie26wH8X3NInL8_9lC-
dJrYSGyeHaks5t5xgTgaJpZM4UasBV
.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<https://github.com/ncopenpass/NCOpenPass/issues/
1046#issuecomment-394897271>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/
AK4rpq46c01JHotggBvUYJr9GJYS5hWpks5t5xr8gaJpZM4UasBV>
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/ncopenpass/NCOpenPass/issues/1046#issuecomment-395078686,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AB3IezWcMk8zw92YW2vBFwYQyr7OTr-3ks5t5-BRgaJpZM4UasBV
.

Note: I only checked for Saturday, do I need to check for the full event?

Yes, please.
On Wed, Jun 6, 2018 at 10:48 AM, Jason Hibbets<EMAIL_ADDRESS>wrote:

Note: I only checked for Saturday, do I need to check for the full event?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/ncopenpass/NCOpenPass/issues/1046#issuecomment-395095921,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AB3Ie7bscS5PPNPf02Ai0Lj7aeq3BNkUks5t5-vGgaJpZM4UasBV
.

Last call you had said Friday wouldn't be a problem, and that you needed to
see about Saturday because normally the desk isn't staffed on Saturday.
So yes, both days available and need someone to man the front desk on
Saturday.
Chris Mathews
On Wed, Jun 6, 2018 at 10:50 AM, Leo Suarez<EMAIL_ADDRESS>wrote:

Yes, please.
On Wed, Jun 6, 2018 at 10:48 AM, Jason Hibbets<EMAIL_ADDRESS>wrote:

Note: I only checked for Saturday, do I need to check for the full
event?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<https://github.com/ncopenpass/NCOpenPass/issues/
1046#issuecomment-395095921>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/
AB3Ie7bscS5PPNPf02Ai0Lj7aeq3BNkUks5t5-vGgaJpZM4UasBV>
.

—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/ncopenpass/NCOpenPass/issues/1046#issuecomment-395096553,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAOGtfCmKUjmGWjgWUvQRd6oZG37tEBNks5t5-wsgaJpZM4UasBV
.

Also, what does that mean exactly. Might we have to pay for it to be
staffed on a saturday?
Just want to cover all the bases here.
On Wed, Jun 6, 2018 at 11:04 AM, Chris Mathews<EMAIL_ADDRESS>wrote:

Last call you had said Friday wouldn't be a problem, and that you needed to
see about Saturday because normally the desk isn't staffed on Saturday.
So yes, both days available and need someone to man the front desk on
Saturday.
Chris Mathews
On Wed, Jun 6, 2018 at 10:50 AM, Leo Suarez<EMAIL_ADDRESS>wrote:

Yes, please.
On Wed, Jun 6, 2018 at 10:48 AM, Jason Hibbets<EMAIL_ADDRESS>wrote:

Note: I only checked for Saturday, do I need to check for the full
event?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<https://github.com/ncopenpass/NCOpenPass/issues/
1046#issuecomment-395095921>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/
AB3Ie7bscS5PPNPf02Ai0Lj7aeq3BNkUks5t5-vGgaJpZM4UasBV>
.

—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
<https://github.com/ncopenpass/NCOpenPass/issues/
1046#issuecomment-395096553>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/
AAOGtfCmKUjmGWjgWUvQRd6oZG37tEBNks5t5-wsgaJpZM4UasBV>
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/ncopenpass/NCOpenPass/issues/1046#issuecomment-395101754,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AB3Ie6Exll3c1KyMmYeHMtMeadgDCKOwks5t5-9rgaJpZM4UasBV
.

Red Hat Annex is available for these dates, we should probably find a
different spot for lightning talks (that's a long  day in a windowless room)

Good point. Can I just point out how ironic that a Red hat person is
concerned that we need more Windows. :)
If we do switch venue for the evening, two things:

We will likely lose people
Need something very turnkey. I don't want to move things from the Annex
to venue#2 just to move it back on Saturday if we can help it.

Chris Mathews
On Wed, Jun 6, 2018 at 10:26 PM, Jason Hibbets<EMAIL_ADDRESS>wrote:

Red Hat Annex is available for these dates, we should probably find a
different spot for lightning talks (that's a long day in a windowless room)
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/ncopenpass/NCOpenPass/issues/1046#issuecomment-395272490,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAOGtceTD4nxahevz1__ZwsMAd2rDmH7ks5t6I9zgaJpZM4UasBV
.

Omg. I was just thinking about using the marbles for the lightning talks on
Friday night.
On Fri, Jun 8, 2018, 3:26 PM Leo Suarez<EMAIL_ADDRESS>wrote:

Just an idea, I wonder if we could use the Artspace lobby to kick off Civic
Camp. Then, we encourage folks to walk the 300 feet (literally) over to Red
Hat annex where the lunch will be ready.
http://artspacenc.org/events/rent-facility/
We may need to piece a few things together there but they clearly have
rented out space before. Chris, Tracy, take a look. I think it's worth
considering if we want to break up the day within the Annex.
On Thu, Jun 7, 2018 at 3:08 PM, Chris Mathews<EMAIL_ADDRESS>wrote:

Good point. Can I just point out how ironic that a Red hat person is
concerned that we need more Windows. :)
If we do switch venue for the evening, two things:

We will likely lose people
Need something very turnkey. I don't want to move things from the
Annex
to venue#2 just to move it back on Saturday if we can help it.

Chris Mathews
On Wed, Jun 6, 2018 at 10:26 PM, Jason Hibbets<EMAIL_ADDRESS>wrote:

Red Hat Annex is available for these dates, we should probably find a
different spot for lightning talks (that's a long day in a windowless
room)
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
<https://github.com/ncopenpass/NCOpenPass/issues/
1046#issuecomment-395272490>,
or mute the thread
<
https://github.com/notifications/unsubscribe-auth/AAOGtceTD4nxahevz1__
ZwsMAd2rDmH7ks5t6I9zgaJpZM4UasBV>
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<
https://github.com/ncopenpass/NCOpenPass/issues/1046#issuecomment-395531816
,
or mute the thread
<
https://github.com/notifications/unsubscribe-auth/AB3Iew9xQEapXFfxmQ8-HeShrvZoOcrpks5t6Xo8gaJpZM4UasBV
.

—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/ncopenpass/NCOpenPass/issues/1046#issuecomment-395864443,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADgoV2rvYfdphU35gevAx8tejVXPCH79ks5t6s_dgaJpZM4UasBV
.

I think I have the rough agenda mixed up. I know we're doing 2 days now but
has anyone written down a rough agenda for civic camp, what we're thinking?
On Fri, Jun 8, 2018, 4:07 PM Jason Hibbets<EMAIL_ADDRESS>wrote:

Omg. I was just thinking about using the marbles for the lightning talks on
Friday night.
On Fri, Jun 8, 2018, 3:26 PM Leo Suarez<EMAIL_ADDRESS>wrote:

Just an idea, I wonder if we could use the Artspace lobby to kick off
Civic
Camp. Then, we encourage folks to walk the 300 feet (literally) over to
Red
Hat annex where the lunch will be ready.
http://artspacenc.org/events/rent-facility/
We may need to piece a few things together there but they clearly have
rented out space before. Chris, Tracy, take a look. I think it's worth
considering if we want to break up the day within the Annex.
On Thu, Jun 7, 2018 at 3:08 PM, Chris Mathews<EMAIL_ADDRESS>wrote:

Good point. Can I just point out how ironic that a Red hat person is
concerned that we need more Windows. :)
If we do switch venue for the evening, two things:

We will likely lose people
Need something very turnkey. I don't want to move things from the
Annex
to venue#2 just to move it back on Saturday if we can help it.

Chris Mathews
On Wed, Jun 6, 2018 at 10:26 PM, Jason Hibbets <
<EMAIL_ADDRESS>wrote:

Red Hat Annex is available for these dates, we should probably find a
different spot for lightning talks (that's a long day in a windowless
room)
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
<https://github.com/ncopenpass/NCOpenPass/issues/
1046#issuecomment-395272490>,
or mute the thread
<
https://github.com/notifications/unsubscribe-auth/AAOGtceTD4nxahevz1__
ZwsMAd2rDmH7ks5t6I9zgaJpZM4UasBV>
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<

https://github.com/ncopenpass/NCOpenPass/issues/1046#issuecomment-395531816

,
or mute the thread
<

https://github.com/notifications/unsubscribe-auth/AB3Iew9xQEapXFfxmQ8-HeShrvZoOcrpks5t6Xo8gaJpZM4UasBV

.

—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
<
https://github.com/ncopenpass/NCOpenPass/issues/1046#issuecomment-395864443
,
or mute the thread
<
https://github.com/notifications/unsubscribe-auth/ADgoV2rvYfdphU35gevAx8tejVXPCH79ks5t6s_dgaJpZM4UasBV
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/ncopenpass/NCOpenPass/issues/1046#issuecomment-395875600,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AB3Ie8ZpH08YlioIDx5YGDypkXNyekUeks5t6tlwgaJpZM4UasBV
.

This is how Chris described it recently in a partner discussion:
CivicCamp event in the past - a combination of unconference presentations,
lightning round tasks, social and then all day hackathon with presentations
at the end.
Not sure if that helps or not
On Fri, Jun 8, 2018 at 4:36 PM, Leo Suarez<EMAIL_ADDRESS>wrote:

I think I have the rough agenda mixed up. I know we're doing 2 days now but
has anyone written down a rough agenda for civic camp, what we're thinking?
On Fri, Jun 8, 2018, 4:07 PM Jason Hibbets<EMAIL_ADDRESS>wrote:

Omg. I was just thinking about using the marbles for the lightning talks
on
Friday night.
On Fri, Jun 8, 2018, 3:26 PM Leo Suarez<EMAIL_ADDRESS>wrote:

Just an idea, I wonder if we could use the Artspace lobby to kick off
Civic
Camp. Then, we encourage folks to walk the 300 feet (literally) over to
Red
Hat annex where the lunch will be ready.
http://artspacenc.org/events/rent-facility/
We may need to piece a few things together there but they clearly have
rented out space before. Chris, Tracy, take a look. I think it's worth
considering if we want to break up the day within the Annex.
On Thu, Jun 7, 2018 at 3:08 PM, Chris Mathews <
<EMAIL_ADDRESS>wrote:

Good point. Can I just point out how ironic that a Red hat person is
concerned that we need more Windows. :)
If we do switch venue for the evening, two things:

We will likely lose people
Need something very turnkey. I don't want to move things from the
Annex
to venue#2 just to move it back on Saturday if we can help it.

Chris Mathews
On Wed, Jun 6, 2018 at 10:26 PM, Jason Hibbets <
<EMAIL_ADDRESS>wrote:

Red Hat Annex is available for these dates, we should probably
find a
different spot for lightning talks (that's a long day in a
windowless
room)
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
<https://github.com/ncopenpass/NCOpenPass/issues/
1046#issuecomment-395272490>,
or mute the thread
<
https://github.com/notifications/unsubscribe-auth/AAOGtceTD4nxahevz1__
ZwsMAd2rDmH7ks5t6I9zgaJpZM4UasBV>
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<

https://github.com/ncopenpass/NCOpenPass/issues/1046#
issuecomment-395531816

,
or mute the thread
<

https://github.com/notifications/unsubscribe-auth/AB3Iew9xQEapXFfxmQ8-
HeShrvZoOcrpks5t6Xo8gaJpZM4UasBV

.

—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
<
https://github.com/ncopenpass/NCOpenPass/issues/1046#
issuecomment-395864443
,
or mute the thread
<
https://github.com/notifications/unsubscribe-auth/
ADgoV2rvYfdphU35gevAx8tejVXPCH79ks5t6s_dgaJpZM4UasBV
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<https://github.com/ncopenpass/NCOpenPass/issues/
1046#issuecomment-395875600>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/
AB3Ie8ZpH08YlioIDx5YGDypkXNyekUeks5t6tlwgaJpZM4UasBV>
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/ncopenpass/NCOpenPass/issues/1046#issuecomment-395883141,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AK4rpo3stfnGGOEpo3OBRi34eoI0lQkmks5t6uBpgaJpZM4UasBV
.

Looks like Artspace could be a good fit Friday evening.  Price is within
our budget and they seem accommodating and not too restrictive.
Thank you for your interest in Artspace for the event you are planning.
Operating out of its historic building in downtown Raleigh, Artspace is a
wonderful, unique facility, filled with interesting and colorful artwork.
We always receive a lot of positive feedback from our guests after an
event.
The evening of Friday, September 21, 2018 is available at Artspace, and we
would love to have you!
Most events are held in our beautiful 2nd floor Gallery Two, which has a
seated maximum capacity of approximately 100.  However, buffet-style
receptions with as many as 200+ circulating guests are popular at
Artspace.  This is accomplished by expanding the footprint of your event
into our hallway adjacent to the Gallery.  (There is no additional charge
for use of the hallway.) With the Gallery's double doors opening diagonally
into our wide hallway, this is a lovely setup that provides a natural flow
for your guests in a setting surrounded by our art studios. The hallway is
the perfect place for your food and/or beverage tables, and possibly
additional (standing) cocktail tables.
Tuesday through Saturday events at Artspace may begin no earlier than 6:00
p.m., with catering set up and event set up allowed in the afternoon.
Artspace provides 8 foot by 30 inch (banquet-sized) rectangular tables at
no extra charge.  We have chairs that you may find acceptable, or you may
choose to have nicer-looking chairs brought in.  We do not provide round
tables, linens, or any other items.  I can provide a list of suggested
vendors if you are in need of recommendations.
I'm available for appointments Mondays through Fridays from 10:00am -
4:00pm.  If you are interested in making an appointment, please send me 1st
choice and 2nd choice of a time that will work for you, and I'll confirm.
Please let me know if I can assist you further with your plans.
Chris Mathews
On Mon, Jun 18, 2018 at 11:26 AM, Jason Hibbets<EMAIL_ADDRESS>wrote:

The Annex is available for both days. We can discuss tonight if you want
me to complete the booking process. No problem on my side, I just need to
fill out a form.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/ncopenpass/NCOpenPass/issues/1046#issuecomment-398093843,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAOGtTnwWQ__ZnzJoe7kJ5WYWQPlGk-dks5t98a-gaJpZM4UasBV
.


Aurora-dx-nvidia No Longer Automatically Applying Updates After Reboot

Describe the bug
I have 2 systems (desktop and laptop) running aurora-dx-nvidia on different branches - latest and stable. I’ve noticed in the last few weeks ((around the 7th or so), the updates are downloading but they are not applying after reboot. I have to manually rollback to a previous version (the 0801 one) then do a rpm-ostree update in order for updates to apply on reboot. I had to do that with the laptop on stable last week and it just downloaded a new update for this week and will not apply it automatically. Here is the rpm-ostree status after rebooting when it did not apply:
What did you expect to happen?
❯ rpm-ostree status -v
State: idle
AutomaticUpdates: stage; rpm-ostreed-automatic.timer: no runs since boot
Deployments:
● ostree-image-signed:docker://ghcr.io/ublue-os/aurora-dx-nvidia:stable (index: 0)
Digest: sha256:3c79afa3f5dbb3f8db4e0a4b243b80db31b5b689b63e781094e31dc20000fb5e
Version: 40.20240813.0 (2024-08-13T06:35:52Z)
Commit: 48c1d27ab8d7b8cb967f1e4aa906abf1b2eb65adf672ee5825f69bfd6a251154
Staged: no
StateRoot: fedora
ostree-image-signed:docker://ghcr.io/ublue-os/aurora-dx-nvidia:stable (index: 1)
Digest: sha256:392c885695d7b8e4c89c42ee21e94c0f8f86647ffdb343dd2c99c21ae397432f
Version: 40.20240801.0 (2024-08-01T19:56:00Z)
Commit: 2ad3671f2be2b081e4048533e18c120682684f5b6a7e7145b64fe80bc0051dea
StateRoot: fedora
AvailableUpdate:
Timestamp: 2024-08-20T05:52:32Z
Commit: 6d82f58c00667266c94380faa7ff7f75ca2b134330dcb8d7246478a6f4d8f782
Upgraded: amd-gpu-firmware 20240709-1.fc40 → 20240811-2.fc40
amd-ucode-firmware 20240709-1.fc40 → 20240811-2.fc40
atheros-firmware 20240709-1.fc40 → 20240811-2.fc40
brcmfmac-firmware 20240709-1.fc40 → 20240811-2.fc40
breeze-icon-theme 6.5.0-1.fc40 → 6.5.0-2.fc40
btrfs-progs 6.9.2-1.fc40 → 6.10-1.fc40
buildah 1.36.0-1.fc40 → 1.37.0-1.fc40
cirrus-audio-firmware 20240709-1.fc40 → 20240811-2.fc40
cockpit-machines 316-1.fc40 → 317-1.fc40
cockpit-ostree 1:203-1.fc40 → 1:204-1.fc40
cockpit-podman 91-1.fc40 → 92-1.fc40
code 1.92.1-1723066391.el8 → 1.92.2-1723661076.el8
devpod v0.5.18-1.fc40 → v0.5.19-1.fc40
distribution-gpg-keys 1.104-1.fc40 → 1.105-1.fc40
docker-buildx-plugin 0.16.1-1.fc40 → 0.16.2-1.fc40
docker-ce 3:27.1.1-1.fc40 → 3:27.1.2-1.fc40
docker-ce-cli 1:27.1.1-1.fc40 → 1:27.1.2-1.fc40
docker-ce-rootless-extras 27.1.1-1.fc40 → 27.1.2-1.fc40
egl-gbm 2:1.1.1-5.20240412git649c079.fc40 → 2:1.1.2-1.fc40
egl-gbm 2:1.1.1-5.20240412git649c079.fc40 → 2:1.1.2-1.fc40
egl-wayland 1.1.15-1.fc40 → 1.1.15-2.20240814gitf30cb0e.fc40
egl-wayland 1.1.15-1.fc40 → 1.1.15-2.20240814gitf30cb0e.fc40
ethtool 2:6.9-1.fc40 → 2:6.10-1.fc40
fzf 0.54.1-1.fc40 → 0.54.3-1.fc40
gperftools-libs 2.14-3.fc40 → 2.14-4.fc40
ibus 1.5.30-5.fc40 → 1.5.30-6.fc40
ibus-gtk2 1.5.30-5.fc40 → 1.5.30-6.fc40
ibus-gtk3 1.5.30-5.fc40 → 1.5.30-6.fc40
ibus-gtk4 1.5.30-5.fc40 → 1.5.30-6.fc40
ibus-libs 1.5.30-5.fc40 → 1.5.30-6.fc40
ibus-panel 1.5.30-5.fc40 → 1.5.30-6.fc40
ibus-setup 1.5.30-5.fc40 → 1.5.30-6.fc40
intel-audio-firmware 20240709-1.fc40 → 20240811-2.fc40
intel-gpu-firmware 20240709-1.fc40 → 20240811-2.fc40
intel-media-driver 24.1.5-1.fc40 → 24.2.5-1.fc40
iwlegacy-firmware 20240709-1.fc40 → 20240811-2.fc40
iwlwifi-dvm-firmware 20240709-1.fc40 → 20240811-2.fc40
iwlwifi-mvm-firmware 20240709-1.fc40 → 20240811-2.fc40
kcli 99.0.0.git.202408112231.ec8c845-0.fc40 → 99.0.0.git.202408152041.5eeaa03-0.fc40
kde-settings 40.0-1.fc40 → 40.1-1.fc40
kde-settings-plasma 40.0-1.fc40 → 40.1-1.fc40
kde-settings-pulseaudio 40.0-1.fc40 → 40.1-1.fc40
kde-settings-sddm 40.0-1.fc40 → 40.1-1.fc40
kernel 6.9.7-200.fc40 → 6.9.11-200.fc40
kernel-core 6.9.7-200.fc40 → 6.9.11-200.fc40
kernel-modules 6.9.7-200.fc40 → 6.9.11-200.fc40
kernel-modules-core 6.9.7-200.fc40 → 6.9.11-200.fc40
kernel-modules-extra 6.9.7-200.fc40 → 6.9.11-200.fc40
kernel-tools 6.10.3-200.fc40 → 6.10.5-200.fc40
kernel-tools-libs 6.10.3-200.fc40 → 6.10.5-200.fc40
kf6-breeze-icons 6.5.0-1.fc40 → 6.5.0-2.fc40
libedit 3.1-51.20240517cvs.fc40 → 3.1-53.20240808cvs.fc40
libedit 3.1-51.20240517cvs.fc40 → 3.1-53.20240808cvs.fc40
libedit-devel 3.1-51.20240517cvs.fc40 → 3.1-53.20240808cvs.fc40
libertas-firmware 20240709-1.fc40 → 20240811-2.fc40
libimagequant 4.0.3-3.fc40 → 4.0.3-5.fc40
libldb 2.9.1-1.fc40 → 2.9.1-4.fc40
libnfsidmap 1:2.6.4-0.rc6.fc40 → 1:2.6.4-0.rc8.fc40
libppd 1:2.0.0-4.fc40 → 1:2.0.0-6.fc40
libsrtp 2.3.0-14.fc40 → 2.6.0-1.fc40
linux-firmware 20240709-1.fc40 → 20240811-2.fc40
linux-firmware-whence 20240709-1.fc40 → 20240811-2.fc40
mt7xxx-firmware 20240709-1.fc40 → 20240811-2.fc40
nfs-utils 1:2.6.4-0.rc6.fc40 → 1:2.6.4-0.rc8.fc40
nvidia-gpu-firmware 20240709-1.fc40 → 20240811-2.fc40
nxpwireless-firmware 20240709-1.fc40 → 20240811-2.fc40
openssl 1:3.2.1-2.fc40 → 1:3.2.2-3.fc40
openssl-libs 1:3.2.1-2.fc40 → 1:3.2.2-3.fc40
passt 0^20240726.g57a21d2-1.fc40 → 0^20240814.g61c0b0d-1.fc40
passt-selinux 0^20240726.g57a21d2-1.fc40 → 0^20240814.g61c0b0d-1.fc40
podman 5:5.1.2-1.fc40 → 5:5.2.0-1.fc40
podmansh 5:5.1.2-1.fc40 → 5:5.2.0-1.fc40
python3-boto3 1.34.153-1.fc40 → 1.34.162-1.fc40
python3-botocore 1.34.153-1.fc40 → 1.34.162-1.fc40
qt-settings 40.0-1.fc40 → 40.1-1.fc40
realtek-firmware 20240709-1.fc40 → 20240811-2.fc40
rpm-ostree 2024.6-1.fc40 → 2024.7-1.fc40
rpm-ostree-libs 2024.6-1.fc40 → 2024.7-1.fc40
skopeo 1:1.15.2-1.fc40 → 1:1.16.0-1.fc40
tailscale 1.70.0-1.fc40 → 1.72.0-1
tiwilink-firmware 20240709-1.fc40 → 20240811-2.fc40
vim-common 2:9.1.660-1.fc40 → 2:9.1.672-1.fc40
vim-data 2:9.1.660-1.fc40 → 2:9.1.672-1.fc40
vim-enhanced 2:9.1.660-1.fc40 → 2:9.1.672-1.fc40
vim-filesystem 2:9.1.660-1.fc40 → 2:9.1.672-1.fc40
vim-minimal 2:9.1.660-1.fc40 → 2:9.1.672-1.fc40
wpa_supplicant 1:2.11-2.fc40 → 1:2.11-3.fc40
xxd 2:9.1.660-1.fc40 → 2:9.1.672-1.fc40
Removed: displaylink-6.0.0-2.fc40.x86_64
gvisor-tap-vsock-6:0.7.4-1.fc40.x86_64
gvisor-tap-vsock-gvforwarder-6:0.7.4-1.fc40.x86_64
kmod-evdi-6.9.7-200.fc40.x86_64-1.14.5-2.20240726giteab561a.fc40.x86_64
kmod-kvmfr-6.9.7-200.fc40.x86_64-0.0.git.23.2de42028-1.fc40.x86_64
kmod-nvidia-6.9.7-200.fc40.x86_64-3:560.31.02-1.fc40.x86_64
kmod-openrazer-6.9.7-200.fc40.x86_64-100.0.0.git.530.886f986d-1.fc40.x86_64
kmod-v4l2loopback-6.9.7-200.fc40.x86_64-0.13.1-1.fc40.x86_64
kmod-wl-6.9.7-200.fc40.x86_64-<IP_ADDRESS>1-51.fc40.x86_64
kmod-xone-6.9.7-200.fc40.x86_64-0.0.git.115.fdbb71f1-1.fc40.x86_64
kmod-xpadneo-6.9.7-200.fc40.x86_64-0.9.6-2.20240423git73be2eb.fc40.x86_64
kmod-zfs-6.9.7-200.fc40.x86_64-2.2.5-1.fc40.x86_64
libevdi-1.14.5-2.20230726giteab561a.fc40.x86_64
Added: kmod-kvmfr-6.9.11-200.fc40.x86_64-0.0.git.23.2de42028-1.fc40.x86_64
kmod-nvidia-6.9.11-200.fc40.x86_64-3:560.31.02-1.fc40.x86_64
kmod-openrazer-6.9.11-200.fc40.x86_64-100.0.0.git.530.886f986d-1.fc40.x86_64
kmod-v4l2loopback-6.9.11-200.fc40.x86_64-0.13.1-1.fc40.x86_64
kmod-wl-6.9.11-200.fc40.x86_64-<IP_ADDRESS>1-51.fc40.x86_64
kmod-xone-6.9.11-200.fc40.x86_64-0.0.git.115.fdbb71f1-1.fc40.x86_64
kmod-xpadneo-6.9.11-200.fc40.x86_64-0.9.6-2.20240423git73be2eb.fc40.x86_64
kmod-zfs-6.9.11-200.fc40.x86_64-2.2.5-1.fc40.x86_64
~
❯
Output of rpm-ostree status
No response
Output of groups
No response
Extra information or context
No response

My automatic updates on Aurora stopped working as well, with the following error:
❯ rpm-ostree upgrade
note: automatic updates (stage) are enabled
Pulling manifest: ostree-image-signed:docker://ghcr.io/ublue-os/aurora-dx
error: Creating importer: Failed to invoke skopeo proxy method OpenImage: remote error: cryptographic signature verification failed: invalid signature when validating ASN.1 encoded signature

I think this is due to https://github.com/ublue-os/main/issues/599 and https://github.com/ublue-os/bluefin/pull/1483.
As a workaround I fixed it by accepting all signatures in /etc/containers/policy.json:
/etc/containers🔒
❯ diff policy.json.bak policy.json -C 2
*** policy.json.bak	2024-08-22 09:46:37.796002073 +0200
--- policy.json	2024-08-22 09:46:53.903880061 +0200
***************
*** 32,40 ****
              "ghcr.io/ublue-os": [
                  {
!                     "type": "sigstoreSigned",
!                     "keyPath": "/usr/etc/pki/containers/ublue-os.pub",
!                     "signedIdentity": {
!                         "type": "matchRepository"
!                     }
                  }
              ],
--- 32,36 ----
              "ghcr.io/ublue-os": [
                  {
!                     "type": "insecureAcceptAnything"
                  }
              ],

Sounds like a different issue from the one I'm having.  The issue I'm having is occurring on 2 independent systems installed separately and there's no errors when rpm-ostree update is run.

@lion7 your error is indeed the one that you linked. See the pinned issue to get the updated cosign public key instead of doing insecureAcceptAnything.
@Mortifier13 is this still occuring? It sounds like the deployment is failing; however, its confusing since you said an update works after a rollback. The only time I've had a similar issue was when I had specifically modified the root fs outside of an ostree update and then removed a package dependent on those changes.

@lion7 your error is indeed the one that you linked. See the pinned issue to get the updated cosign public key instead of doing insecureAcceptAnything.
@Mortifier13 is this still occuring? It sounds like the deployment is failing; however, its confusing since you said an update works after a rollback. The only time I've had a similar issue was when I had specifically modified the root fs outside of an ostree update and then removed a package dependent on those changes.

I think my issue is occurring due to a lack of free space on /root, it was almost full when I had a few pinned deployments so I removed some of them so I'm down to 3 total deployments in /boot/ostree/.  My /boot is 1GB and with only 3 now instead of 5 it's still using about 750 megs.  It worked on a manual update last night so I'm testing it over the next few days to see but there haven't been many daily updates rolling through the nvidia branch lately.  If it seems to work on updating I'd like to increase the size of my /boot partition since I like to always keep a few pinned deployments on the latest branch.


Support ASCII authentication

most of the behavior in main needs to be refactored into a session handler, but it seems to work ok


PSTH plot does not work

When I try to plot a psth diagram as in the Jeffress tutorial, I get the attached error.
psth = plotting.PSTH(spiketrain, binsize=5)
psth.show_plot(neuron_indices=[8, 9, 10])
plt.show()
Machine: Windows 64 bit, Python3
<class 'numpy.ndarray'>
Traceback (most recent call last):
File "jeffress_test1.py", line 41, in
psth.show_plot(neuron_indices=[8, 9, 10])
File \Python34\site-packages\neurons\plo
tting.py", line 72, in show_plot
axis.hist(times, bins, histtype='bar', stacked=True, fill=True, facecolor='g
reen', alpha=0.5, zorder=0)
File \site-packages\matplotlib\axes_axes.py", l
ine 5597, in hist
raise ValueError("x must have at least one data point")
ValueError: x must have at least one data point

Should be corrected in c177a51

Before closing the issue let's test this on a Windows machine before

Tested on a windows machine last week, looks good so far.


Release v0.1.2

This is a draft of changelog for the v0.1.2 release.
Here you can find all related translations changes: v0.1.1...master.

⚠ Do not merge this pull request manually ⚠
You should approve this pull request instead. After approving, I will automatically update it (release date needs to be adjusted), merge, and tag a new release. You can read more about the process on forum.

Show release notes preview
v0.1.2

General changes:

Updated Flarum core translations.

All changes: v0.1.1...v0.1.2.

Success! Now you can announce new release on forum:
## Version [`v0.1.2`](https://github.com/flarum-lang/korean/releases/tag/v0.1.2)

**General changes**:

* Updated Flarum core translations.

All changes: [v0.1.1...v0.1.2](https://github.com/flarum-lang/korean/compare/v0.1.1...v0.1.2).

In order to update run these commands:

```console
composer update flarum-lang/korean
php flarum cache:clear
```


Docs: Update landing page with new diagram and update link to repo

just realized we need to update diagram and links on the landing page (Enterprise-scale support for Azure Virtual Desktop - Cloud Adoption Framework | Microsoft Docs), especially the link under Custom deployment is pointing to RDS-Templates repository

PR #3406 posted

Thanks for the great work Xavier, closing this one

@danycontre , The PR is assigned to Wahid as reviewer but he is on long term vacation. Who else can we assign it to?


fix: Patch AnimatedStyle to avoid discarding the initial style info

Summary
This PR patches AnimatedStyle to avoid discarding the initial style information which destroys the output of web-style compilers and breaks rendering, as requested on https://github.com/facebook/react-native/issues/34425. This uses a slightly modified version of a patch used by react-native-web  https://github.com/necolas/react-native-web/commit/4c678d2912bddf30ad3d1f2c9a71f453d29427f0.
Changelog
[General] [Fixed] - Patch AnimatedStyle to avoid discarding the initial style info
Test Plan
Run yarn jest Animated and ensure CI is green

Please provide a unit tests that shows how this behaviour was broken before and how this change resolves it. This will help me understand the goal here and prevent us from breaking it in the future :)

@necolas would you mind helping me with this one? I know that the problem is described on https://github.com/necolas/react-native-web/issues/2387 but I'm not completely sure how to recreate that scenario on this repo

Please provide a unit tests that shows how this behaviour was broken before and how this change resolves it. This will help me understand the goal here and prevent us from breaking it in the future :)

The behavior is broken on web because using flattenStyle is fundamentally incompatible with any approach to compiling styles to CSS. https://github.com/necolas/react-native-web/issues/2387
A unit test for this change in RN would only show that Animated nodes are duplicated in a new style object appended to the input styles, and that the return from the Style node is an array instead of an object. There would be no functional difference on native.

Does this correctly handle scenarios like this?
style={[
   {backgroundColor: animatedValue},
   {backgroundColor: 'red'},
]}

The expected outcome would be that animatedValue is not used.

Yes, it does. The first thing we do is a flatten, and then extract any animated values that are left

@necolas FYI this should be good for another review round

Hi @cipolleschi, do you mind importing this PR? 😅


.hadolint.yaml only detected at root of first folder in workspace, not folder root of related Dockerfile

I have a .hadolint.yaml file at the same level as my Dockerfile which are in a subfolder in a secondary root of a multi-root (multi-folder) VSCode workspace.
I didn't have luck with it being detected at the same folder, nor at the folder root... then I tried at the folder root of the first folder in my workspace and voila, it works. That's odd.
Has this extension been updated since VSCode incorporated multi-root workspaces? And should the .hadolint.yaml work at the same level as the Dockerfile file? If not, I'd at least expect it to work at the folder root of the repo the Dockerfile is in.
Thoughts?

Hi @ darkvertex,
Thanks for bringing this up.
I have never used the multi root feature in VSCode, properly that’s why I didn’t notice it earlier.
The plugin does not add any special handing for the ‘.hadolint.yml’ file beside relying on the ‘hadolint’ program itself to look for the configuration file.
Any chance you can create a sample repo that can reproduce the issue?
Meanwhile, I’m busy with school this year, and don’t have much availability to work on this. Help wanted :)

I looked a bit at the code and I'm guessing that this line where you use spawn.sync() you do not seem to pass the current working directory, so hadolint probably doesn't know and I guess VSCode probably passes the first root in the workspace by default.
I know you use cross-spawn for compatibility reasons but it's supposedly the same as the original nodejs .spawn(), where you can apparently pass the working directory via the options object's cwd (current working directory) value.
If it helps you also, I found this example of a dummy language server with multi-root workspace awareness here:
https://github.com/microsoft/vscode-extension-samples/blob/master/lsp-multi-server-sample/server/src/server.ts#L17
JS is not my specialty (and TypeScript less so) or I'd try to fix this myself.
I don't have time this instant to prepare you a sample repo reproducing the bug, but I will try to do you one at a later time.

I think this should actually be fixed in the hadolint itself. It should use a mechanism for loading the configuration in the folders up, starting from the same folder which the Dockerfile is in.

I think this should actually be fixed in the hadolint itself. It should use a mechanism for loading the configuration in the folders up, starting from the same folder which the Dockerfile is in.

To me the bug is with this extension not passing (to hadolint) the current working directory of the root of the open Dockerfile in question, only passing the first folder path of the workspace (but the thing is, a workspace can have lots! and that's the issue.)

I'm still not sure about it, but you have a point. The implementation should be easy, though.

@darkvertex @felipecrs
Let's say we have the below project structure.
- root
  - .hadolint.yml
  - app01
    - Dockerfile
  - app02
    - Dockerfile

If we just get the path.dirname of the current file and use it as cwd for spwan, it is not going to work. In the example above, the hadolint configuration file is definitely located at one level above.
Instead, we should look into whether VSCode provides API to extract the current project root, specifically for a multi-root workapce environment. I would love someone to help looking into if this is possible.
I recently start using this feature a lot and realize a bunch of plugins are not optimized for multi-root workspace. The built-in Source Control included, it wasn't correctly reading the project specific .gitattributes file until last ugprade.

Close via b03df4899eb2274ec219a30747f2ae7a83590075


F5 Load Balancer Only Recognizes 2 of 5 Worker Nodes as Active in OKD Cluster

@vrutkovs kindly your support
After installing the OKD cluster with the following configuration:
OKD version is: 4.15 stable
fedora core os version : fedora-coreos-40.20240728.3.0-metal.x86_64.raw.xz
installation type is: any platform platform  in VM's in VMware
3 master nodes
5 worker nodes
2 load balancers (LB) in F5, handling:
Ports 6443 and 22623
Ports 443 and 80
All worker nodes are ready and functioning properly within the cluster. However, the F5 load balancer only recognizes 2 worker nodes as active, while the remaining 3 are marked as inactive.
When I attempt to telnet to port 443:
It works on the active nodes as seen by the F5.
It does not work on the inactive nodes, neither from the VMs' IPs nor from within the VMs themselves (the 443 port is not responding).
How can I resolve this issue to ensure that all worker nodes are active in F5 and capable of handling incoming application requests?
Originally posted by @ahmedalazazy in https://github.com/okd-project/okd/discussions/1903#discussioncomment-10969501

Hi,
The OKD Working Group is transitioning OKD to an SCOS base and can only provide minimal guidance on versions <= 4.15. Please see these documents...
https://okd.io/blog/2024/06/01/okd-future-statement
https://okd.io/blog/2024/07/30/okd-pre-release-testing
We will be providing documentation on upgrading clusters from 4.15 FCOS to 4.16 SCOS when a stable release is available.
Many thanks,
Jaime


Docs cleanup for "KEP-3329 Retriable and non-retriable Pod failures for Jobs"

Cleanup for: https://github.com/kubernetes/website/pull/35219
Tracking issue: Retriable and non-retriable Pod failures for Jobs

/assign @sftim

/sig node
/kind cleanup
/lgtm
/approve
Thanks


Add HashJoinSegment, a virtual segment for joins.

An initial step towards #8728. This patch adds enough functionality to implement a joining
cursor on top of a normal datasource. It does not include enough to actually do a query. For
that, future patches will need to wire this low-level functionality into the query language.
The main files in this patch:

HashJoinSegment: The virtual join Segment described in #8728.
HashJoinSegmentStorageAdapter: Storage adapter for that segment; "makeCursors" is the
interesting part.
HashJoinEngine: Contains JoinColumnSelectorFactory, JoinCursor, which together implement
the row-by-row logic of a join.
LookupJoinable: Allows joining onto lookups.
IndexedTableJoinable: A more flexible Joinable that can have multiple columns in general,
including multiple key columns. I expect this will be used for joining onto subquery results
in the future. It may even be used as a sort of super-lookup.

Some supporting elements:

Added a "withDimension" method to DimensionSpec so prefixed dimensions can be rewritten to
remove their prefixes.
Added "canIterate" and "iterable" to LookupExtractor, necessary for right and full joins
on lookups. It will also be useful for direct queries on lookups in the future.
Removed "getSegmentIdentifier" method from StorageAdapter. It was not being used.
Moved RowBasedColumnSelectorFactory out of the groupBy engine, reflecting the fact that it
has been used by other, non-groupBy things. Also, split out the RowAdapter interface, which
is now used by RowBasedIndexedTable as well.
Renamed VectorColumnStrategizer to VectorColumnProcessorFactory (see below).
Added a "ColumnProcessors" utility class and "ColumnProcessorFactory" interface that is
currently only used to make join condition matchers in IndexedTableJoinMatcher. It wasn't
strictly necessary, but I think it's designed better than ColumnSelectorStrategyFactory,
and could replace it in the future. It's similar in design to VectorColumnProcessorFactory.

Next steps:

Implement the rest of "data server behavior" from https://github.com/apache/druid/issues/8728 (this patch is number 3, the virtual join Segment).
Implement "broker behavior" from https://github.com/apache/druid/issues/8728.
Implement SQL planning.
Various performance optimizations: filter push-down, deferred lookupName during condition matching / row retrieval, vectorized joins.
Fix handling of right-joins; see comment in HashJoinEngine: "Warning! The way this engine handles 'righty' joins is flawed: it generates the 'remainder' rows per-segment, but this should really be done globally. This should be improved in the future."

This is super cool thank you for putting this together. I would love to see a README.md (or similar) going over the high level mechanics of the join to help understand its limitations. I see a few comments scattered among classes but don't quite see the high level data flow. Is it all captured in https://github.com/apache/druid/issues/8728 , or are there more nuances in this PR since it is a foundation PR?

This is super cool thank you for putting this together. I would love to see a README.md (or similar) going over the high level mechanics of the join to help understand its limitations. I see a few comments scattered among classes but don't quite see the high level data flow. Is it all captured in #8728 , or are there more nuances in this PR since it is a foundation PR?

@drcrallen --
#8728 is more of a program for starting to build join support than a description of mechanics. I agree that such a description of mechanics would be useful, although I haven't written it yet. I will start working on that and, maybe, it will outlive the proposal #8728 in usefulness.
What sorts of questions would you want this mechanical description / design doc to answer?

Reviewers: by the way, I've done two things in this patch that were suggested on the dev list and I found to be useful. Please let me know if you agree.

The new unit tests in this patch are named in the style of https://lists.apache.org/thread.html/381816301bda945b7bf19c05822d1d910282ceb2a96db86b3bfe72b8%40<dev.druid.apache.org>. For example see HashJoinSegmentStorageAdapterTest.
Used Optional a bit more, as suggested in https://lists.apache.org/thread.html/5bb9c985bf0918dfbd2d247aa960bbaf8982654d95c648dba8ef2d67%40<dev.druid.apache.org>. For example see HashJoinSegmentStorageAdapter#getClauseForColumn and Exprs.decomposeEquals. There are still a lot of @Nullable where needed to interact with existing interfaces. I didn't think going on a rampage changing them was a good idea.

I started a design document at https://gist.github.com/gianm/39548daef74f0373b3c87056e3db4627. @drcrallen let me know if this answers your questions.

Thank you @gianm I'll comment in the doc as opposed to cluttering here.

I've found it tough reviewing this PR. I think it could have been broken down into a few other PRs. For example:

The refactor of class/method name changes
The implementation of all the factories for the selectors
The Join logic
The IndexedTable implementation and its related pieces

If you're not going to add unit tests, I think we should have a coverage check to make sure that the inputs to the functional tests end up testing all branches of the code...

Sounds like a good idea to me. IMO it isn't worth unit testing every single class, and can even be counter-productive (adds to the amount of work it takes to refactor things later). So I like the idea of pairing functional tests with coverage checks.
That being said, some of the examples you pointed out would be good to add unit tests for, so I'll go through and add a few more. I probably won't have a chance to do this today, but I'll try to get to it soon.

@jnaous — I've pushed up a commit with all the changes I said I'd make in your review.

I haven't really looked through the tests yet, but I don't have any more comments on the main code

Tests LGTM, there are some real TC errors about unused methods

Tests LGTM, there are some real TC errors about unused methods

I'm looking into these.


Preety print multiline diff messages from puppetdb

This PR fixes unreadable diff (and other multiline) messages from puppetdb - it splits message by newline character and show in separate paragraph.

Coverage decreased (-0.4%) to 81.298% when pulling caff0b8514d5e05a11c20e668c4661b743746e1c on lkosz:preety_print_diff into 66d344b3c16944771f3d7fcb88f6f974d8ec4814 on voxpupuli:master.

Closing as #576 that fills the same purpose is merged. Please open a new PR if you feel that there is still something to be done about this, @lkosz .


是否考虑增加表格设置仅内边框

What problem does this feature solve?
是否考虑增加表格设置仅内边框
What does the proposed API look like?
表格设置仅内边框

仅内边框什么意思


SET_PARAMETER Keepalive fail with Bad Request 400

Which version are you using?
v0.17.17
Which operating system are you using?

[ ] Linux amd64 standard
[x] Linux amd64 Docker
[ ] Linux arm64 standard
[ ] Linux arm64 Docker
[ ] Linux arm7 standard
[ ] Linux arm7 Docker
[ ] Linux arm6 standard
[ ] Linux arm6 Docker
[ ] Windows amd64 standard
[ ] Windows amd64 Docker (WSL backend)
[ ] macOS amd64 standard
[ ] macOS amd64 Docker
[ ] Other (please describe)

Describe the issue
The client send RTSP keepalives and fails with the message:
RTSP keepalive (SET_PARAMETER) failed with code 400, Bad Request for URL rtsp://<IP_ADDRESS>:8554/cam1/stream

The debug logs of the server shows following:
DEB [RTSP] [conn <IP_ADDRESS>:64398] [s->c] RTSP/1.0 400 Bad Request
CSeq: 4
Server: gortsplib

INF [RTSP] [conn <IP_ADDRESS>:64398] closed (unhandled request: SET_PARAMETER rtsp://<IP_ADDRESS>:8554/cam1/stream)

After the fail the client closes the connection, because it thinks that the connection is closed. Is this a valid RTSP keepalive?
Thanks for any hints!

Looking at the specification:

10.5. Showing Liveness
The mechanisms for showing liveness of the client is, any RTSP request with a Session header, if RTP & RTCP is used an RTCP message, or through any other used media protocol capable of indicating liveness of the RTSP client. It is RECOMMENDED that a client does not wait to the last second of the timeout before trying to send a liveness message. The RTSP message may be lost or when using reliable protocols, such as TCP, the message may take some time to arrive safely at the receiver. To show liveness between RTSP request issued to accomplish other things, the following mechanisms can be used, in descending order of preference:

RTCP:
If RTP is used for media transport RTCP SHOULD be used. If RTCP is used to report transport statistics, it MUST also work as keep alive. The server can determine the client by network address and port together with the fact that the client is reporting on the servers SSRC(s). A downside of using RTCP is that it only gives statistical guarantees to reach the server. However, the probability of a false client timeout is so low that it can be ignored in most cases. For example, assume a session with 60 seconds timeout and enough bitrate assigned to RTCP messages to send a message from client to server on average every 5 seconds. That client has, for a network with 5 % packet loss, the probability to fail showing liveness sign in that session within the timeout interval of 2.4*E-16. Sessions with shorter timeouts, or much higher packet loss, or small RTCP bandwidths SHOULD also use any of the mechanisms below.
SET_PARAMETER:
When using SET_PARAMETER for keep alive, a body SHOULD NOT be included. This method is the RECOMMENDED RTSP method to use for a request intended only to perform keep-alive.
GET_PARAMETER:
When using GET_PARAMETER for keep alive, no body SHOULD be included.
OPTIONS:
This method is also usable, but it causes the server to perform more unnecessary processing and results in bigger responses than necessary for the task. The reason is that the server needs to determine the capabilities associated with the media resource to correctly populate the Public and Allow headers.

The timeout parameter MAY be included in a SETUP response, and MUST NOT be included in requests. The server uses it to indicate to the client how long the server is prepared to wait between RTSP commands or other signs of life before closing the session due to lack of activity (see Appendix B). The timeout is measured in seconds, with a default of 60 seconds. The length of the session timeout MUST NOT be changed in an established session.

Hello, it's enough to read the spec you posted above to understand your issue:

The mechanisms for showing liveness of the client is, any RTSP request with a Session header,

Your keepalives don't include any session header.

Thanks for the hint. Not an expert in RTSP stuff and not familar with your code base. Didn't see, that there is no session header.

A keep-alive is used to keep a session alive, since a client that is reading or publishing can connect and disconnect multiple times, but its stream from/to the server is kept opened. This is possible due to the fact that sessions and clients are two separate concepts.
A keep-alive without a session header can't be associated to a session, therefore it can't prevent a session from being deleted for inactivity. Even if we edit the code base to support keep-alives at the connection level, the session that the client is using will be deleted after some time.


Add export as image

Add Export as Image Feature
Description
I propose adding a feature that allows users to export code snippets as images directly from the application.
Benefits

Ease of Sharing: Users can easily share code snippets on social media, blogs, or documentation.
Consistent Formatting: Ensures visually appealing and well-formatted output without requiring external tools.
Improved User Experience: Adds value for developers who need quick and polished visuals of their code.

Reference Implementation
I have implemented a similar feature on my website, where users can customize and export code snippets as images.
Here’s the link to my website: Code Snapshot
Example Output Grid
Below are some example images exported using my tool:

My Website Preview

Contribution Offer
I am eager to contribute to the project by integrating this feature or assisting with its implementation if it aligns with the project's roadmap.

Hello, there. I liked your Code Snapshot project. I will leave this issue open. If it's heavily requested by the community to include this feature, we will integrate.

integrate it really helpful

I have added the feature but got failing checks. I could not find the problem

I believe snippet generation from code does not need to be added to this. Since the focus is on finding code snippets and there are already plenty of 'code snippet generators' out there, users can just simply copy the code to one of those sites which provide much more rich features, like @robindev2007 's own https://codesnapshot.robinweb.site/ or even www.ray.so.
A suggestion would be, if this feature is requested a lot, to add a link to one of the established websites so users can easily download if necessary. For example, www.ray.so, allows URL parameters, so the app could just pass the code as a base64 encoded string so the snippet will be readily available on click.
Test Link for QuickSnip JavaScript - Array Manipulation : https://www.ray.so/#code=Y29uc3QgcmVtb3ZlRHVwbGljYXRlcyA9IChhcnIpID0-IFsuLi5uZXcgU2V0KGFycildOwoKLy8gVXNhZ2U6CmNvbnN0IG51bWJlcnMgPSBbMSwgMiwgMiwgMywgNCwgNCwgNV07CmNvbnNvbGUubG9nKHJlbW92ZUR1cGxpY2F0ZXMobnVtYmVycykpOyAvLyBPdXRwdXQ6IFsxLCAyLCAzLCA0LCA1XQ&language=javascript&darkMode=true

@psychlone77 A good idea

I find the idea of @psychlone77 better, it keeps the code base small, and removes a lot of the responsability of maintaining such a feature from our shoulders.


Allow structured outputs via function calling

Describe the change
Allows strict: true to be passed to OpenAI within a function's definition, triggering OpenAI's new structured outputs setup to ensure the function's schema is strictly adhered to.
Provide OpenAI documentation link
https://openai.com/index/introducing-structured-outputs-in-the-api/
Describe your solution
Add Strict to the properties of FunctionDefinition. Only serialise it in the JSON if its value is true (to avoid wasting tokens).
Tests
Added a test.
Additional context
None

@sashabaranov the linting error on my first commit wasn't related to this PR. I've fixed it in the second commit since it was a trivial one.

@greysteil thank you for the PR! Could you please fix the merge conflict and add an integration test — it's pretty hard to follow all the OpenAI API updates these days

@sashabaranov done!


Delete "Provider" suffix out of provider names

Following the rule we applied at most places about name repetition, our providers are under the providers module but still contain Provider in their name: MbedCryptoProvider, TpmProvider and Pkcs11Provider. I think it might be fine to remove the Provider part 😃

Actually, I was looking at the code structure, it goes like this:
providers -> <type>_provider -> <Type>Provider (e.g. providers::tpm_provider::TpmProvider)
I think it'd make more sense if it was:
providers -> <type> -> Provider (so providers::tpm::Provider)

Actually, I was looking at the code structure, it goes like this:
providers -> <type>_provider -> <Type>Provider (e.g. providers::tpm_provider::TpmProvider)
I think it'd make more sense if it was:
providers -> <type> -> Provider (so providers::tpm::Provider)

Yes definitely!

I can't close this :sweat_smile:


add quilt support

Quilt is a new modding toolchain. Currently, when someone uses Quilt mclo.gs shows server software vanilla

Thanks for the suggestion.
I created a pull request for this in our library that detects those things: https://github.com/aternosorg/codex-minecraft/pull/23
After that has been merged, we can update it in mclogs

It's merged

Thanks!


Type duality: jest vs @types/jest

Actually nevermind.
I'll be damned. Jest already declares its own types. Is it game over?
Edit: I just checked how that works out. When you import jest, it resolves to jest's own types. However, Typescript still brings in types from @types/jest and that only works because types are defined in the global namespace in @types/jest.

Now that (majority of) jest packages export their own typescript types, is it possible to expose types that @types/jest is exposing, but from jest without @types/jest and by reusing types from other jest modules in this repo?
Ideally, this should be done in a non-breaking/backward-compatible way for @types/jest users otherwise it's going to be a huge mess for TS users.
For example, jest.fn()'s generic arguments should default to any instead of unknown, at least until jest v27. There are many such small incompatibilities between jest's own types and @types/jest.
Some of such incompatibilities can potentially be fixed by jest package by re-exporting types from other packages by making minor modifications on types, where necessary.
Remember that once jest declares its own types, TS won't recognize @types/jest anymore! So it's a dangerous decision.
But this duality must be eventually abolished.

The plan is for @types/jest to continue to exist, but only to add types to the global env. See https://github.com/DefinitelyTyped/DefinitelyTyped/pull/44365
If you think Jest's own types can be improved, please send a PR 🙂


vim renders all wrong

How it looks in terminus:

How it looks in other terminal emulators:

I'm on MacOS 10.11.6, Vim 8.0 with this color theme.

Just from looking at those corners and characters, are you sure you're not using the Powerline fonts in iTerm? If so, you need to choose the same font in Terminus.

Yep, quite sure. I'm using "Inconsolata for powerline" just as I do for other emulators. To my understanding, I believe UTF8 support is still required to get the more obscure looking characters to show up, even with the right font selected.

Weird - as I'm using Powerline myself. Could you please upload the complete vim configuration so that I can try to reproduce this?

https://github.com/acarl005/bash-osx/blob/master/.vimrc

Works for me... can you also try other fonts from the Powerline family?

I've added another potential fix in Alpha 19


Default handling on must statement validation

The ip-prefix field like:
set / interface ethernet-1/1 subinterface 0 ipv4 address <IP_ADDRESS>/31

contains the following must statement:
https://github.com/nokia/srlinux-yang-models/blob/v23.10.1/srlinux-yang-models/srl_nokia/models/interfaces/srl_nokia-if-ip.yang#L169-L171
          must "(../../unnumbered/admin-state != 'enable')" {
            error-message "Assignment of IPv4 addresses is prohibited when the subinterface is unnumbered";
          }

The unnumbered/admin-state has a default value of disable. Which we do not seem to load as part of the validation.
https://github.com/nokia/srlinux-yang-models/blob/v23.10.1/srlinux-yang-models/srl_nokia/models/interfaces/srl_nokia-if-ip.yang#L236
Therefore the below config results in the following error:
rpc error: code = Unknown desc = Assignment of IPv4 addresses is prohibited when the subinterface is unnumbered

[
    {
        "path": "/",
        "value": {
            "interface": [
                {
                    "name": "ethernet-1/1",
                    "subinterface": [
                        {
                            "index": 0,
                            "ipv4": {
                                "admin-state": "enable",
                                "address": [
                                    {
                                        "ip-prefix": "<IP_ADDRESS>/31"
                                    }
                                ]
                            }
                        }
                    ]
                }
            ]
        }
    }
]

Default loading was implemented as part of #171


click on the notification

Hello
When the vpn is connected, we click on the notification, it takes us to the program settings in the phone's own settings (it brings up the app's default page in the settings)

Hi , did you solve it


Provide a proper response when a nonexisting username is provided to recover the password

Description
When a user provided an unexisting username when try to recover the password a valid response is not provided to the user.
Tested Environment
IS 5.8.0 m6
Actual Results
The following message appeared in application side

Following error appear in the IS backend
[2018-11-27 14:28:27,677] ERROR {org.wso2.carbon.identity.recovery.endpoint.impl.RecoverPasswordApiServiceImpl} -  Unable to find an user with username: sashini in the system.

Expected Results
Should provide the proper response message as the user does not exist or some other appropriate message to indicate that the provided username is not valid.

Thank you for your contribution!
We are closing this issue since it has not been prioritized for a long time. Chances are that it has already been solved in more recent versions. If not, we will be re-evaluating this when it becomes a priority.


Add an example on how to mutate an item from a list

I have a list of users coming from my API. I'd like to update one user and optimistically update the UI.
Currently I'm doing this (by mimicking the example from the README):
const updateUser = (userId, data) => {
  mutate(users.map((users) => users.id === userId ? { ...user, ...data } : user), false)
  mutate(users => {
    const newUser = fetch(`/api/users/${userId}`, { method: 'PUT', body: JSON.stringify(data) })
    return users.map((users) => users.id === userId ? newUser : user)
  })
}

The first mutate is here to update the UI, then I trigger the call to update my database and I mutate with the result.
Is it the correct way to do it? It seems a bit redundant.

Yes currently what you are doing is correct. We have discussions in #157 on how to improve this specific case, feel free to join the discussion there!

hi - apologies for opening this.
i was wondering how to handle this if the example above used query strings to sort/filter the user list (e.g., /users?sort=desc&assignee=bob)?
if the filters change, we edit a user and return to the previous filters which contains the same user, wouldn't it be outdated?


Add ability to select a character for editing

In order to improve the user experience, it would help if you could select a card from the top in order to display a context menu for the character on the bottom of the screen. As of now, my thought is to have a larger token of them with a wheel of options such as editing name, editing health, duplicating, and deleting. Could add more in the future for things like status effects.

Implemented with 7adf761


Add pkgdown website

[ ] add README.md source file -- usage/installation instructions
[ ] add Getting Started source file (vignettes/xmap.Rmd)

split out {xmap} package to separate repo

Temporary manual deploy of xmap pkgdown on netlify until I split out {xmap} package (ideally with git history)

https://xmap-r-pkg.netlify.app/index.html

Closed by #71, with temporary hosting solution until I work out #75


Add JsonPath support

Is your feature request related to a problem? If yes, please describe the problem.
I suppose it would be great to add some resources for the JsonPath support . This new resource, mixed with the fetch will make it extremely easy to query and amend the JSON responses to fit it into resulting query schema
Describe the solution you'd like to see.
We could add a jsonPath resource so the user could query the data like:
let a = fetch(...)
a:jsonPath("$.store.book[*].author")

The inspiration for this feature request was Raws.com: https://rows.com/docs/modifying-json?category=advanced

I like the idea, because it has a concrete use case.

... and it's super easy to implement in fact :-)


Support async database backends

Hello, first of all I apologize if this is not the appropriate place to have this discussion, if not please direct me to the correct place.
This is a try to start discussing the ability yo have asynchronous backends (e.g. psycopg3) and thus being able to use the ORM asynchronously. This proposal is backwards compatible.
Use the django.db.backends.postgresql_async backend to try, do not use runserver, not all Query methods where migrated but these will work:

prefetch_related
acount
afirst
alast
async for

The approach was:

added foundations: BaseDatabaseWrapperAsync, CursorWrapperAsync, CursorDebugWrapperAsync - same interface but with async methods when needed;
migrated PostgresSQL backend to psycopg3 async interface;
migrate Query async methods to use the new async interface;
call async_to_sync on sync methods when using an async backend;
call sync_to_async on async methods when using a sync backend;

Does not investigated yet:

runserver shenanigans;
migrations;

Problems:

is created one database connection for each operation done on a sync view when using an async backend. That is expected since database connections are "bind" to threads+coroutines. To fix this we will need to find a way to "bind" the connections to a theard+request, that should also facilitate the implementation of connection pools (https://github.com/django/django/pull/16881);
for the same motives of previous point, the connections are not closed. On async views the workaround, which is not always feasible, is closing the connection at the end of the view;
?

Ty for your feedback.

@domingues Have you seen this? https://github.com/django/deps/blob/main/accepted/0009-async.rst#id13
It is a useful source to learn what the maintainers planned for async ORM.

@salomvary I've read the RFC. but maybe you know more? I can not see any working/implementation plan. What's the progress? How can I contribute? Do we have bunch of small tickets to make it finally work?


support https on elb

user can configure:

elb protocol
elb port
custom external domain name
the arn of ssl certificate to be set to elb

@everpeace Thanks for taking your time! LGTM


woopshop.com is accepting NAV

Hello,
woopshop.com is accepting NAV.
Regards
Acceptance Criteria
Add merchant to stores listing

[ ] Title
[ ] Short Description
[ ] Link
[ ] Logo

Is www.woopshop.com the correct url for your website? It seems to be broken

https://www.woopshop.com
use https instead of http

claimed by @roast-nav

Resolved by #210


Shuffling positions is halting the callback chain

Howdy, I've been having an issue where the callback chain is being halted around the update_positions callback. The issue goes away if I remove this line. The remaining callbacks fire just fine, but of course, the shuffle_positions_on_intermediate_items method doesn't execute.
Following that method, I tried various things to address the issue. I mostly tried to explicitly return true, but I wasn't able to get things work.
I'm running v0.8.2 and rails v<IP_ADDRESS>. I also ran the master version of this gem with no success. I'm happy to open a PR, but I'm struggling to see why exactly the shuffling method is halting the callback chain.

Hi @DavidVII, that certainly sounds strange. You'll hate me saying so, but it'd be helpful if you could try to reproduce this in a test in our test suite. Once we have a failing case seperate from your application, it'll be much easier to diagnose. I'd be surprised if you didn't discover the reason for the failure in that process anyway :)
Let me know how you get on.
The only way for a callback to halt the chain is for it to return false, so somehow that must be happening? In Rails 5 I think that's also changed to needing to specifically call some kind of halting method.

Hi @brendon, indeed this is a strange one. I did write tests, but they're within my application. I'll see if I can replicate within your test suite. If I do, I'll open up a PR and with any luck, it'll include a fix too.
It's a bit tricky cause the code in question doesn't appear to be returning false. However, whenever that line runs, the remaining callbacks do not fire. I'll keep hacking around.

Thanks @DavidVII, sounds good. :)

Hi @brendon, i've got an isolated test file here that replicates the issue.
The main idea here, is that my_callback should be triggered every time the position is updated. The callback simply adds one to the counter column. As you can see by running the file, the callback is only triggered once. All Status position columns get updated, but not all counter columns do.
Perhaps this has something to do with the update_all in this line of code?
Is this by design? Do we want to avoid callbacks here or should we always be firing those off? Perhaps there should be an option to allow users to choose?

Thanks for the test :) What would be even better would be if you brought it into our test suite proper then we can run it more easily on our end too. Create a PR with the failing test case.
I had one quick thought though. It's prone to create havoc if you kick off other database operations in after_ callbacks. In this case you're kicking off an update of a column which will in turn kick off the acts_as_list callbacks again. In your case perhaps the side effects aren't too bad, but sometimes you can end up in infinite loops etc...
If you're just testing the logic and in your real case you're not also updating the database in an after_ callback, then in your test case perhaps test that your callback method is called the expected number of times. This might help: http://stackoverflow.com/questions/10869417/how-to-assert-certain-method-is-called-with-ruby-minitest-framework
Let me know how you get on :)

@DavidVII, I'm closing this due to inactivity. Let me know if it's still a problem and we can reopen and investigate further. You'll also need to create a PR with a failing test case if you want us to look into it for you.


Update dev testing master

This is a test of release update and conflict resolution.

/hold

@simplytunde 👋 Feel free to /reopen if this is still a test in progress.
/close


Change path serialization format

Currently, path ref serializes to the following string:
"ref:32449fe9:/Users/rockjam/projects/mill/out/dev/assembly/dest/mill"

but sometimes it's useful to use a result of the task that returns path. For instance:
mill root.assembly | xargs -I {} cp {} ~/dist/out.jar
Is it okay if we change a path ref format to the following one, so we can use json tools to parse output?
{
  "path": "/Users/rockjam/projects/mill/out/dev/assembly/dest/mill",
  "quick": true,
  "sig": "32449fe9"
}

I think we should stick with the current syntax; I explicitly changed it to the current syntax from the proposed syntax a while ago.
While JSON parsing output is convenient, human readability is important too, and using the proposed syntax makes the output take 5x as many lines and commands like allSources or compileClasspath impossible to skim visually.

I understand the motivation. One more thing - current output format isn't convenient to copy-paste either. If it was a simple path, starting with /, I would double click the output string in terminal and paste right there, but in current the format I have to select some part of the path, or copy the whole thing and clean out all before /. It's a small thing, but useful(for me at least)

What about adding a blank after the colon?


Around 4 billion dropped entries on P2

Hello,
I'm getting the following...
[P2] Table 7 scan took 64.342 sec
[P2] Table 7 rewrite took 101.659 sec, dropped 0 entries (0 %)
[P2] Table 6 scan took 72.0408 sec
[P2] Table 6 rewrite took 197.033 sec, dropped 581589561 entries (13.5494 %)
[P2] Table 5 scan took 76.9387 sec
[P2] Table 5 rewrite took 187.423 sec, dropped 762356078 entries (17.7554 %)
[P2] Table 4 scan took 73.3449 sec
[P2] Table 4 rewrite took 186.928 sec, dropped 829225236 entries (19.3097 %)
[P2] Table 3 scan took 73.6602 sec
[P2] Table 3 rewrite took 193.011 sec, dropped 855274573 entries (19.9149 %)
[P2] Table 2 scan took 73.0457 sec
[P2] Table 2 rewrite took 185.298 sec, dropped 865753587 entries (20.1576 %)
Phase 2 took 1490.75 sec

What does it mean that these short to 4 billion entries dropped?

you mean in total? that's normal

I can totally confirm that's normal.  Though I don't know why.  It is normal, no matter how you slice it.

@madMAx43v3r I've seen Bram's video analyzing your plotter and stating that there are around %0.1 lost entries and that the generated plots aren't bit for bit identical to stock plotter.
Are these ones he was talking about?
How does they affect farming?
Fixing these on the milestone?

nope, those are normal dropped entries. it's 0.01% which are dropped in addition at most, your plot will the smaller too, in the end no difference

@madMAx43v3r but the progress output shows it's dropping up to %20 which is extremely confusing!
Can you please clarify from what you can see in my initial post.
Thanks.

@madMAx43v3r but the progress output shows it's dropping up to %20 which is extremely confusing!
Can you please clarify from what you can see in my initial post.
Thanks.

This is not the same thing as the 0.01% dropped entries in phase 1. This 20% or whatever is a normal result of Phase 2, which aims to remove unnecessary entries in the plot tables. From this excellent article:
"The purpose of the backpropagation step is to remove data that is not useful for finding proofs. During this phase, all entries which do not form part of the matching condition in the next table, are dropped."

Is the "0.01% drop" going to be fixed anyway? Despite being negligible in terms of plot quality, Bram himself talks about it as an undesirable effect of this plotter.

@madMAx43v3r Is the "0.01% drop" going to be fixed anyway? Despite being negligible in terms of plot quality, Bram himself talks about it as an undesirable effect of this plotter.

@madMAx43v3r Is the "0.01% drop" going to be fixed anyway? Despite being negligible in terms of plot quality, Bram himself talks about it as an undesirable effect of this plotter.

How is the drop even material to anything of concern?

@madMAx43v3r Is the "0.01% drop" going to be fixed anyway? Despite being negligible in terms of plot quality, Bram himself talks about it as an undesirable effect of this plotter.

No plans as of today, it'll slow phase 1 down and increase tmp 1 + 2 space needed by one byte per entry.

@madMAx43v3r Is the "0.01% drop" going to be fixed anyway? Despite being negligible in terms of plot quality, Bram himself talks about it as an undesirable effect of this plotter.

No plans as of today, it'll slow phase 1 down and increase tmp 1 + 2 space needed by one byte per entry.

Wow! Then make it optional if it relates to performance or required temp storage :/

Wow! Then make it optional if it relates to performance or required temp storage :/

That's the way to go, in my opinion.

I still fail to see how this issue is material to anything of concern. There are far more significant issues in this forum than this. Seriously, people are getting 23 minute plot times, smaller plots, and you're saying that something that, you have yet to demonstrate has any measurable impact on those things, is a problem?

it's a cosmetic / emotional issue, maybe when we add it to official chia repo, it's not possible to have a dynamic switch, has to be hardcoded either way

If that's so, I'd say we shouldn't compromise performance/storage utilization.

No plans as of today, it'll slow phase 1 down and increase tmp 1 + 2 space needed by one byte per entry.

Just out of curiosity, are there any estimates of what "slow phase 1 down" and "increase tmp 1 + 2 space" values might be?


powerstat: 0.02.18 -> 0.02.19

Motivation for this change
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[x] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

Changelog: https://kernel.ubuntu.com/git/cking/powerstat.git/tree/debian/changelog


Feat: Added Contact Us Page and Portion of Teams

Description:
This PR adds the Contact Us Page along with a portion of Teams Page in the benjamin directory(directory made to convert whole website to nexjs).
Changes Done:

Added Contact Us Page
Added Portion of Teams Page

Video:
https://github.com/mdazfar2/HelpOps-Hub/assets/72603662/ad163a05-8427-4696-9ece-b775de8a2a89
Additional Context:
N/A

@mdazfar2 kindly review


Fix changelog link in Rubygem listing

Not a bug or issue in the gem itself, but wanted to flag this for @lazaronixon.
On the gem's Rubygem page (https://rubygems.org/gems/authentication-zero), the Changelog leads to:
https://github.com/lazaronixon/authentication-zero/blob/main/CHANGELOG.md
The actual changelog is at:
https://github.com/lazaronixon/authentication-zero/blob/master/CHANGELOG.md

Thank you @geetfun, I've updated the master branch to main... 🙌


Circular dependency

General information

Library version: 5.2.0
Browser and OS: Safari 16.4 on macOS 13.3.1

Issue description
When doing a build for a project that uses<EMAIL_ADDRESS>I am seeing a circular dependency in the frames package...
Circular dependency: node_modules/framebus/dist/lib/package-payload.js -> node_modules/framebus/dist/lib/subscribe-replier.js -> node_modules/framebus/dist/framebus.js -> node_modules/framebus/dist/lib/package-payload.js

I'll take a look at this and ticket it up if it's something we can fix but I do recommend updating to a more recent version as well

When you say you were using braintree 3.15.0, did you mean braintree_node? Not braintree web?

Yes - braintree node (braintree@3.1.5). I'm also using<EMAIL_ADDRESS>These are the latest published correct?

Are you also using framebus directly? Are you using these via npm?

Solved. Released a fix for this in v5.2.1

Awesome - thank you!


Staking dashboard/tool

Description
Staking dashboard to allow users to stake and choose the role they want to play within the protocol.
Motivation
Need of having a user friendly way for staking
Implementation details

[ ] Network selector: according to the selected network use the staking contract address for this network
[ ] Stake: input amount
[ ] Dashboard that shows staked and allocated amounts
[ ] Unstake: input amount. Only available if has unallocated staking.
[ ] Set role using kvStore (Job Launcher, Exchange Oracle, Recording Oracle, Reputation Oracle)
[ ] Show accrued rewards
[ ] Withdraw rewards
[ ] Slash

I like this

@portuu3
It might help https://miro.com/app/board/uXjVPG1mXJc=/?moveToWidget=3458764537804136449&cot=14

broken down into smaller tasks


Don't use two pages when one is sufficient

Why is the login process spread across two pages? This wastes everybody's time as you have to wait for the second page to load, and it's a deviation from the standard everybody else uses. Username and password belong in a single dialog.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: d23565fb-ccc9-42fc-6bde-f999d92fc762
Version Independent ID: 60c86bac-f951-8181-793b-34018f4a76ea
Content: Microsoft sigin-in experience updates
Content Source: articles/multi-factor-authentication/end-user/sign-in-experience-updates.md
Service: multi-factor-authentication
GitHub Login: @eross-msft
Microsoft Alias: lizross

@HdeJong0 Thanks for your feedback! We will investigate and update as appropriate.

@HdeJong0 Please post this as a feedback @ https://feedback.azure.com/forums/169401-azure-active-directory. This will allow the community to upvote and for the product team to include into their plans.
We also have the "Give Product Feedback" button in our documents now to take you directly to the appropriate feedback page.

From my understanding, the 2 pages login experience comes from a technical constraint related to federated authentication.
You can use different type of accounts: enterprise/school account or personal account.
Entering first your username/email, allows the system to redirect you to the proper authentication mechanism, hence explaining the 2 steps.

I've added this as feedback, thanks.
https://feedback.azure.com/forums/169401-azure-active-directory/suggestions/34465306-login-should-be-a-single-page-instead-of-two
H. de Jong

From: SaurabhSharma-MSFT<EMAIL_ADDRESS>Sent: Tuesday, June 5, 2018 9:22:56 PM
To: MicrosoftDocs/azure-docs
Cc: Harro de Jong; Mention
Subject: Re: [MicrosoftDocs/azure-docs] Don't use two pages when one is sufficient (#9734)
@HdeJong0https://github.com/HdeJong0 Please post this as a feedback @ https://feedback.azure.com/forums/169401-azure-active-directory. This will allow the community to upvote and for the product team to include into their plans.
We also have the "Give Product Feedback" button in our documents now to take you directly to the appropriate feedback page.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/azure-docs/issues/9734#issuecomment-394829719, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AVL9qjuMKFjvOnI4bQVhzK07Clqr6D8vks5t5tqQgaJpZM4Ua_09.

@HdeJong0 Thanks, we will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.


DeviceInfo.getCarrier() on ios devices does not work

Bug
The function of DeviceInfo.getCarrier() return "Carrier" instead of a name of sim's carrier in the IOS devices, however it works fine in Android devices
Environment info
React native info output:
  System:
      OS: macOS 10.14.5
      CPU: (4) x64 Intel(R) Core(TM) i5-7400 CPU @ 3.00GHz
      Memory: 162.75 MB / 16.00 GB
      Shell: 3.2.57 - /bin/bash
    Binaries:
      Node: 10.15.0 - /usr/local/bin/node
      Yarn: 1.9.4 - /usr/local/bin/yarn
      npm: 6.4.1 - /usr/local/bin/npm
    SDKs:
      iOS SDK:
        Platforms: iOS 13.2, DriverKit 19.0, macOS 10.15, tvOS 13.2, watchOS 6.1

   Xcode: 11.2/11B52 - /usr/bin/xcodebuild
    npmPackages:
      react: 16.6.3 => 16.6.3
      react-native: 0.57.8 => 0.57.8
    npmGlobalPackages:
      create-react-native-app: 1.0.0
      react-native-cli: 2.0.1
      react-native-git-upgrade: 0.2.7

Library version: 2.2.2
        let carr = await DeviceInfo.getCarrier();
        console.log('getCarrier carr : ', carr);
       //  getCarrier carr :  Carrier

Update to current and reproduce please, troubleshooting old versions has little value
Note: I don't think the behavior will change necessarily, but I still won't spend time on old versions


where are the index.html files located for daedalos

I need these files so i can port this html to uwp for my xbox one

Those files can be created by cloning the repo and running:

yarn to install the package dependencies
yarn build to build the project
yarn export to create the out folder with the html/js required

Another command instead of export can also be yarn deploy which runs some additional minification steps on the out folder.


Save those tokens!

I installed your bot today and noticed that when I tried to use /draw it said I can't have more than 100 characters.
I've been fine tuning my "compress this" prompt for a long time and it works surprisingly well. When I have long prompt or even sending long text to the gpt api, I will compress it using some form of the following:
GPTgz specializes in compressing text into lossless instructions. Compress the provided text into a single paragraph, ensuring that you (AI) can reconstruct it with 100% accuracy to the original intent. This compressed text is for internal use and does not need to be human-readable. Utilize any non-standard protocols, including language-mixing, abbreviations, slang, technical jargon, Unicode, Emoji, or any other unconventional methods, as long as the result is a lossless compression of the original text. The compressed text should maintain its integrity, particularly when pasted into a new or different context. To achieve this, include a contextual cue or introductory sentence that aids in accurate interpretation. Prioritize compression, losslessness, and utilization of non-standard protocols.

Here is the text:

(then, of course, include the text you want compressed)
For example:
GPTgz specializes in compressing text into lossless instructions. Compress the provided text into a single paragraph, ensuring that you (AI) can reconstruct it with 100% accuracy to the original intent. This compressed text is for internal use and does not need to be human-readable. Utilize any non-standard protocols, including language-mixing, abbreviations, slang, technical jargon, Unicode, Emoji, or any other unconventional methods, as long as the result is a lossless compression of the original text. The compressed text should maintain its integrity, particularly when pasted into a new or different context. To achieve this, include a contextual cue or introductory sentence that aids in accurate interpretation. Prioritize compression, losslessness, and utilization of non-standard protocols.

Here is the text:

Generate a detailed and atmospheric image of a Diablo Immortal character. The image should be square, featuring {USER}'s name prominently yet artistically, without extra text. Ensure that the {USER}'s name is the only text used in the image and that it is 100% legible.

Focus on a visual style that brings the character to life in a typical Diablo Immortal setting, such as dark Gothic landscapes or fiery dungeons. Strive for a high-quality, photographic look, resembling images from a Canon EOS 5D Mark IV. The character design and surroundings should embody the dark fantasy theme of the game, with intricate detailing. Use a color scheme that resonates with Diablo Immortal's aesthetic, ensuring the character's name enhances the image without dominating it.

To create a DALL-E prompt that generates the most realistic looking images, consider these key tips from the Tory Barber website:
1. Avoid "Photo Realistic" Keywords: Using terms like "Photo Realistic" is counterproductive, as DALL-E interprets them as a style of art, not as a descriptor of a photograph. Instead, use simpler descriptors like "Photo of a [subject]".
2. Consider DALL-E's Training: DALL-E was trained on image metadata, including camera settings like lens type, saturation levels, ISO, shutter speed, aperture, and focal length. Incorporating these details in your prompt can enhance realism.
3. Photographer Prompting Keywords: Mentioning a photographer's name can convey a lot of information about the desired style of the photo, as DALL-E associates certain photographers with specific styles and equipment. However, be cautious with this approach due to ethical considerations about using artists' names without their consent.
4. Style Prompting Keywords: Using specific photographic techniques or styles in your prompts, like "tilt shift", can add unique qualities to the image. Tilt shift, for example, adds a blur to the top and bottom of a photo, focusing on the middle to create a sense of movement.
Prompts should avoid "Photo Realistic" keywords, use specific camera metadata, and includes a style prompting keywords to generate a realistic and dynamic image.

Produces:
🗜GPTgz🧬TxtCmprs📜: 🎨DiabloImmortal👹char, 🖼sq. {USER}📛➕🎨, 🚫📝➡. 🌌Gothic/fiery🔥dungeon, 📸CanonEOS5DMkIV💡. 🖌dark🌒fantasy, 🎨scheme🎭. 🤖DALL-E👁🗝: 1⃣🚫"PhotoRealistic"🔍, 2⃣📷meta🎚(ISO,🔍,📸speed), 3⃣👨🎨name🚫🔇, 4⃣🎨style🔎(tilt shift👁🎢). 🎯Realistic🌌📸.
Typically, I will include further instructions or clarification as plain text. In the case of the above, I would paste the output, then add:
You will now ask the {USER} for their {USER} name, character class, and gender and then proceed to generate image based on their response.

Same way

I meant more so, I'm curious if using emoji degrades performance of DALL-E, do you have any insight into this?

I’ve noticed nothing like that. If anything, I would bet it’s faster.

It’s worth noting that it doesn’t always produce emojis. It’s just some internal communication language that only the AI understands.

I noticed today that I pasted the wrong compression, that was from a GPT app that I was messing with. For just the compression part you need to remove the "you are GPTgz" portion, otherwise, the compressed prompt won't use the right context. Update (this should be all you need to do before sending to the API).
Compress the provided text into a single paragraph, ensuring that you (AI) can reconstruct it with 100% accuracy to the original intent. This compressed text is for internal use and does not need to be human-readable. Utilize any non-standard protocols, including language-mixing, abbreviations, slang, technical jargon, Unicode, Emoji, or any other unconventional methods, as long as the result is a lossless compression of the original text. The compressed text should maintain its integrity, particularly when pasted into a new or different context. To achieve this, include a contextual cue or introductory sentence that aids in accurate interpretation. Prioritize compression, losslessness, and utilization of non-standard protocols.

Update to my update ;)
I was working on testing this better today and wrote a small script to put the output into langchain so that I could verify that the tokens were fewer. I updated my prompt to get it down (about 50% less in my test):
Condense the following text into a minimal, GPT-readable format, ensuring complete fidelity to the original meaning. Use any efficient encoding methods (e.g., shorthand, technical symbols, mixed language). The output should be robust against context shifts, ideally starting with a clarifying header. Aim for maximum compression with absolute losslessness.

What I didn't realize before was that the emoji use, while shorter to the human eye, was taking more tokens. So this prompt works a lot better.

@Kav-K, I was searching to see if anyone else had tried to do "compression" like mine and found a paper that Shapiro wrote. I ran a lot of tests and came to the conclusion that a mixed use might be beneficial.
Mine uses fewer tokens on shorter stuff (like prompts)
SPR is better at decompressing longer text (results in better similarity to the original)
I tried inputting a bedtime story I did for my daughter with about 36k characters. Mine compressed it better, but also lost more fidelity during decompression.
So maybe you can use a mix? e.g.: For prompts/summarizing smaller input like up to 3 paragraphs or so, use mine. For longer inputs, I'd try that SPR method.


[Not4Review] Fix cluster group e2e test flake

Codecov Report

Merging #3415 (34f2a60) into main (7dc81f0) will decrease coverage by 20.90%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##             main    #3415       +/-   ##
===========================================
- Coverage   63.32%   42.42%   -20.91%
===========================================
  Files         268      200       -68
  Lines       26871    24296     -2575
===========================================
- Hits        17017    10308     -6709
- Misses       7996    12922     +4926
+ Partials     1858     1066      -792

Flag
Coverage Δ

kind-e2e-tests
?

unit-tests
42.42% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.