[ceph-users] Re: PGs stuck deep-scrubbing for weeks - 16.2.9

[Wesley Dillingham]

Yes these seems consistent with what we are experiencing. We have
definitely toggled the noscrub flags in various scenarios in the recent
past. Thanks for tracking down and fixing.

Respectfully,

*Wes Dillingham*
w...@wesdillingham.com
LinkedIn <http://www.linkedin.com/in/wesleydillingham>


On Fri, Jul 15, 2022 at 10:16 PM David Orman  wrote:

> Apologies, backport link should be:
> https://github.com/ceph/ceph/pull/46845
>
> On Fri, Jul 15, 2022 at 9:14 PM David Orman  wrote:
>
>> I think you may have hit the same bug we encountered. Cory submitted a
>> fix, see if it fits what you've encountered:
>>
>> https://github.com/ceph/ceph/pull/46727 (backport to Pacific here:
>> https://github.com/ceph/ceph/pull/46877 )
>> https://tracker.ceph.com/issues/54172
>>
>> On Fri, Jul 15, 2022 at 8:52 AM Wesley Dillingham 
>> wrote:
>>
>>> We have two clusters one 14.2.22 -> 16.2.7 -> 16.2.9
>>>
>>> Another 16.2.7 -> 16.2.9
>>>
>>> Both with a multi disk (spinner block / ssd block.db) and both CephFS
>>> around 600 OSDs each with combo of rep-3 and 8+3 EC data pools. Examples
>>> of
>>> stuck scrubbing PGs from all of the pools.
>>>
>>> They have generally been behind on scrubbing which we attributed to
>>> simply
>>> being large disks (10TB) with a heavy write load and the OSDs just having
>>> trouble keeping up. On closer inspection it appears we have many PGs that
>>> have been lodged in a deep scrubbing state on one cluster for 2 weeks and
>>> another for 7 weeks. Wondering if others have been experiencing anything
>>> similar. The only example of PGs being stuck scrubbing I have seen in the
>>> past has been related to snaptrim PG state but we arent doing anything
>>> with
>>> snapshots in these new clusters.
>>>
>>> Granted my cluster has been warning me with "pgs not deep-scrubbed in
>>> time"
>>> and its on me for not looking more closely into why. Perhaps a separate
>>> warning of "PG Stuck Scrubbing for greater than 24 hours" or similar
>>> might
>>> be helpful to an operator.
>>>
>>> In any case I was able to get scrubs proceeding again by restarting the
>>> primary OSD daemon in the PGs which were stuck. Will monitor closely for
>>> additional stuck scrubs.
>>>
>>>
>>> Respectfully,
>>>
>>> *Wes Dillingham*
>>> w...@wesdillingham.com
>>> LinkedIn <http://www.linkedin.com/in/wesleydillingham>
>>> ___
>>> ceph-users mailing list -- ceph-users@ceph.io
>>> To unsubscribe send an email to ceph-users-le...@ceph.io
>>>
>>
___
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to ceph-users-le...@ceph.io

Re: [RBW] Southwest Michigan Rivendell Ride ✅

[Wesley]

I love all of this, and must admit being confused by Ben's custom being 
called a single-speed.
-W
On Sunday, July 17, 2022 at 7:01:30 AM UTC-7 Max S wrote:

> [image: Leah saddlesack.jpeg][image: Platypus downtube.jpeg]
>
> On Sunday, July 17, 2022 at 10:00:57 AM UTC-4 Max S wrote:
>
>> [image: Rainbows and unicorns.jpeg][image: The bike life.jpeg][image: 
>> Rivvy Rally SW MI Jul 2022.jpeg][image: VO Adjustable Double 
>> Kickstand.jpeg]
>>
>> On Sunday, July 17, 2022 at 10:00:27 AM UTC-4 Max S wrote:
>>
>>> Great fun, that was! 
>>>
>>> A few more photodetails and a plug for Josh's bike biz – get in touch if 
>>> you want your nice steel bike electrified properly and nicely. 
>>>
>>> - Max "those last 3 miles were definitely uphill!" in A2 
>>>
>>> [image: Josh Planetary Gear.jpeg][image: Copenhagenize.jpeg][image: Get 
>>> some light in here.jpeg][image: The Rivendell Pirate.jpeg]
>>>
>>>

-- 
You received this message because you are subscribed to the Google Groups "RBW 
Owners Bunch" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rbw-owners-bunch+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/rbw-owners-bunch/d565459e-7878-47f8-b97e-cf7678faac4fn%40googlegroups.com.

[ceph-users] PGs stuck deep-scrubbing for weeks - 16.2.9

[Wesley Dillingham]

We have two clusters one 14.2.22 -> 16.2.7 -> 16.2.9

Another 16.2.7 -> 16.2.9

Both with a multi disk (spinner block / ssd block.db) and both CephFS
around 600 OSDs each with combo of rep-3 and 8+3 EC data pools. Examples of
stuck scrubbing PGs from all of the pools.

They have generally been behind on scrubbing which we attributed to simply
being large disks (10TB) with a heavy write load and the OSDs just having
trouble keeping up. On closer inspection it appears we have many PGs that
have been lodged in a deep scrubbing state on one cluster for 2 weeks and
another for 7 weeks. Wondering if others have been experiencing anything
similar. The only example of PGs being stuck scrubbing I have seen in the
past has been related to snaptrim PG state but we arent doing anything with
snapshots in these new clusters.

Granted my cluster has been warning me with "pgs not deep-scrubbed in time"
and its on me for not looking more closely into why. Perhaps a separate
warning of "PG Stuck Scrubbing for greater than 24 hours" or similar might
be helpful to an operator.

In any case I was able to get scrubs proceeding again by restarting the
primary OSD daemon in the PGs which were stuck. Will monitor closely for
additional stuck scrubs.


Respectfully,

*Wes Dillingham*
w...@wesdillingham.com
LinkedIn 
___
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to ceph-users-le...@ceph.io

Re: [RBW] Wald basket rusting. Equivalent in stainless steel? Or how to prevent rust?

[Wesley]

Yes, zinc inhibits rusting - it is sacrificial, so the zinc is meant to 
oxidize before the iron but it eventually runs out. Zinc coating is also 
pretty weakly attached to the underlying steel (kind of like paint). For 
serious marine and industrial applications, the steel would be hot-dip 
galvanized (dipped into a bath of molten zinc).
-W
On Tuesday, July 12, 2022 at 7:04:30 AM UTC-7 J J wrote:

> Good morning all. Appreciate your responses, Philip, Richard, and Brian. 
>
> I suppose I'm ignorant about how zinc plating on steel works — is it 
> supposed to be a great rust inhibitor? I attached a photo of the basket in 
> question. I was installing fenders on my Hunq and got a good look at the 
> underside of the basket and saw that it was basically covered in rust. So I 
> took it off, and noticed that the rusted points that contacted the Nitto 
> Campee rack caused pitting on the rack. I have ridden in wet conditions 
> occasionally, but nothing drastic. I wonder how common this extent of 
> rusting is? The rust on mine took buseage right up to the cliff and then 
> over the edge!
> On Tuesday, July 12, 2022 at 9:27:10 AM UTC-4 brok...@gmail.com wrote:
>
>> I purchased a Nitto rack from Analog back in 2020, and it has the 
>> Cerakote finish on it. It looks great of course, but I was surprised at how 
>> fast the coating wore off in certain spots where my bag rested on the top 
>> of the rack. I wonder if the material of a bag placed inside a Wald basket 
>> with Cerakote would abrade the basket finish in the same manner with normal 
>> riding? I think Cerakote is a thinner coating than say, powdercoat, but I 
>> had assumed it would be a bit more durable.
>>
>> On Tuesday, July 12, 2022 at 8:18:27 AM UTC-4 rmro...@gmail.com wrote:
>>
>>> Analog Cycles has some that are cerakoted. It’s tougher than powder. I 
>>> have a 137 from them & is great. Though as we speak it appears they only 
>>> have 137 half & full baskets. Worth a call though. Or finding a local 
>>> cerakote applicator.
>>>
>>> https://analogcycles.com/collections/basksets
>>>
>>> Sent from my iPhone
>>>
>>> On Jul 11, 2022, at 4:09 PM, J J  wrote:
>>>
>>> Has anyone come across a good stainless steel basket around the same 
>>> size as the 139? I'm not concerned about weight. I love the Wald, but the 
>>> rusting has gotten too much. 
>>>
>>>
>>> Or has anyone successfully treated a new Wald with a clear coat of some 
>>> sort to mitigate rusting? If so, what did you use?
>>>
>>> Thanks very much.
>>>
>>> -- 
>>>
>>> You received this message because you are subscribed to the Google 
>>> Groups "RBW Owners Bunch" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to rbw-owners-bun...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/rbw-owners-bunch/564b504e-ce12-4f07-9b6c-2dfd64e7b80cn%40googlegroups.com
>>>  
>>> 
>>> .
>>>
>>>

-- 
You received this message because you are subscribed to the Google Groups "RBW 
Owners Bunch" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rbw-owners-bunch+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/rbw-owners-bunch/5eed1205-e682-419d-a2d7-ab741750a5dbn%40googlegroups.com.

[RBW] Re: BB spindle length question

[Wesley]

You can adjust the alignment of your bottom bracket by using spacers on the 
drive 
side: https://www.universalcycles.com/search.php?q=bottom+bracket+spacer

On Monday, July 11, 2022 at 2:15:03 PM UTC-7 George Schick wrote:

> David - yeah, that's why I attached that chart.  For some reason the 107 
> and 110 have the same chain line (CL), but the 110 has a bit longer 
> non-drive side length (JL).  Not sure what the application would be for the 
> difference between those two.  The chain line (CL) doesn't jump another 
> 3-4mm or so until the 113.  As a buddy of mine used to always say years 
> ago, "why's it have to be so complicated?"  Beats me.  I happen to be in 
> the possession of a discontinued Park CLG-2  chain line gauge and whenever 
> I have to change BB's I attach one end of that to the middle cog (or either 
> side of middle for even numbered cassettes or freewheel clusters), see 
> where the middle of the seat tube (as measured with a caliper) divided by 
> half, plus the distance to where the midst of a two chainrings or middle of 
> a three chainring crank would be and order accordingly.
>
> On Monday, July 11, 2022 at 2:33:01 PM UTC-5 cycli...@gmail.com wrote:
>
>> FWIW, when the BB on my Hillborne needed replacement, I swapped out the 
>> Tange 107mm BB with a Shimano UN300 107mm BB and the inner chainring made 
>> contact with the chainstay.  I though, no problem, I'll install a 110mm.  
>> However, the additional 3mm spindle length was all on the non-drive side.  
>> I had to go with a 113mm.  Something to be aware of.  I had assumed that 
>> when going to a longer spindle, the extra length would be added to each end 
>> of the spindle equally.
>>
>>
>> BB-UN300  
>>   
>> *68x113*
>>   
>> Spindle Length 
>> 114mm 
>> Body Width 
>> 62.9mm 
>> Drive Side Taper Length 
>> 19.7mm 
>> Left side Taper Length 
>> 31.4mm 
>>   
>>  
>>
>> *68x110 * 
>>   
>> Spindle Length 
>> 111.5mm 
>> Body Width 
>> 63.0mm 
>> Drive Side Taper Length 
>> 17.1mm 
>> Left side Taper Length 
>> 31.4mm 
>>
>>
>>   
>> *68x107*  
>>   
>> Spindle Length 
>> 108.1mm 
>> Body Width 
>> 63.0mm 
>> Drive Side Taper Length 
>> 17.1mm 
>> Left side Taper Length 
>> 28.0mm 
>>
>> On Monday, July 11, 2022 at 5:42:56 AM UTC-7 lconley wrote:
>>
>>> Unfortunately, the arithmetic does not always add up. 
>>>
>>> 22.5 + 20.5 + 68 = 111, not 110. This means that the Q is 4mm less with 
>>> the 107, not 3; this makes sense as the JL difference (22.5 - 18.4) is also 
>>> 4mm.
>>>
>>> Laing
>>>
>>> On Sunday, July 10, 2022 at 8:14:58 PM UTC-4 John Hawrylak wrote:
>>>
 I agree with Bill & George.  The chart George provided, shows a 107 
 gives the same front chain line and C/S clearances as a 110 since the JR 
 dimension is the same for the 107 and the 110.   The 107 gives a 3mm lower 
 Q.I believe George's chart is for IRD BBs.

 John Hawrylak
 Woodstown NJ

 On Saturday, July 9, 2022 at 5:12:43 PM UTC-4 George Schick wrote:

> Agree with Bill.  I took a look at my Ram with a two-chainring crank 
> and that's what it has.  But attached is a chart that you might find 
> handy 
> in making the decision.
>
> George
>
> [image: image.jpeg]
>
> On Saturday, July 9, 2022 at 1:45:30 PM UTC-5 Bill Lindsay wrote:
>
>> I would expect a 107 would be the best choice.  I'm pretty sure I had 
>> a 107 on both of my recently parted out Silver-cranked bikes.  My 
>> Atlantis 
>> had a 38/24, and my wife's Yves Gomez had a triple.  
>>
>> I just built up a Quickbeam with a 38/35 on the big and middle ring 
>> positions and I'm running a 103mm BB.  
>>
>> On Saturday, July 9, 2022 at 10:46:55 AM UTC-7 Forrest wrote:
>>
>>> If I want to put an RBW Silver double crank (42/28) on a Rambouillet 
>>> (with an Ultegra front derailer), do I need a 110 spindle bottom 
>>> bracket? 
>>> Thanks.
>>>
>>>

-- 
You received this message because you are subscribed to the Google Groups "RBW 
Owners Bunch" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rbw-owners-bunch+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/rbw-owners-bunch/ff13f4ac-13d9-47d2-98f7-e1c4c7d70af7n%40googlegroups.com.

Re: [RBW] Susie's Limits

[Wesley]

My understanding is that Clem has been built heavily to take a lot of 
abuse. Have fun, and let us know how it rides with a touring load!
-W
On Tuesday, July 5, 2022 at 3:56:31 PM UTC-7 rmro...@gmail.com wrote:

> I have been thinking about this a lot lately in preparation for the trip I 
> am currently on with my Clem. I have about 30lbs. of gear including the 
> racks & 3 water bottles. Pretty evenly distributed f/r but perhaps biased 
> towards the front. Bike handles good. Hope it’s ok.
> [image: image0.jpeg]
>
> Sent from my iPhone
>
> On Jul 5, 2022, at 6:15 PM, Wesley  wrote:
>
> All else being equal (especially tubing size - which, maybe it's not the 
> same across sizes?), the larger size will be less strong than the smaller 
> sizes, while generally having a heavier rider. I am very curious what the 
> rider did to break his bike and I am also very happy to read that he has 
> apparently shrugged it off and seems to derive some satisfaction from the 
> repair.
>
>
>
> On Tuesday, July 5, 2022 at 3:12:42 PM UTC-7 Wesley wrote:
>
>> Well, they do offer the same bike in a version that will support a 
>> heavier rider. But I agree that people who fit the largest sizes are going 
>> to be flirting with Susie's weight limit even before adding gear. For 
>> instance I've got a 93cm PBH and weigh 190+, so I wouldn't be able to put 
>> much on a Susie and keep within the limits.
>> -W
>>
>> On Tuesday, July 5, 2022 at 2:59:28 PM UTC-7 campyo...@me.com wrote:
>>
>>> I find the weight limits very interesting. Rivendell has always marketed 
>>> their bikes as the “anti-racer” or “not light” alternative to wispy 
>>> aluminum and carbon bikes. Selling a bike with a weight limit most of us 
>>> would exceed seems strange. A max of 160 pounds implies to me a bike unlike 
>>> what I would expect from a company that urges us to take their products, 
>>> load a bunch of stuff on them, and ride on unpaved trails to an overnight 
>>> campout. After all, if I put 10 pounds of stuff on the bike, I can only 
>>> weight 150 pounds myself?
>>>
>>> Am I missing something?
>>>
>>> --Eric “Heavier than 160 Pounds” Norris
>>> campyo...@me.com
>>> Insta: @CampyOnlyGuy
>>> YouTube: YouTube.com/CampyOnlyGuy 
>>>
>>> On Jul 5, 2022, at 2:48 PM, Ryan Frahm  wrote:
>>>
>>> I did tell them that I ride semi aggressive and would be bikepacking, I 
>>> just don’t do any big jumps. They still told me Susie at my weight. So I’d 
>>> imagine there was some other factors for that break. But I guess I’d be 
>>> crazy loaded if I got over it 200 total with me and my camp gear. 
>>>
>>> I can say that it rides smoother than anything I’ve ever ridden, I 
>>> wonder if the Gus truly has that same ride. I only have 60 or so miles on 
>>> it and it has been mostly bike path. We’ll see how it goes when I get a 
>>> chance to take it on some real trails!
>>>
>>> On Tuesday, July 5, 2022 at 2:18:10 PM UTC-7 brendonoid wrote:
>>>
>>>> Originally it was 160 pounds, one of the main reasons I didn't jump on 
>>>> the first batch. Over six foot that was a very low weight limit and it 
>>>> made 
>>>> me nervous. Somewhat Ironically, photos of this exact bike made me think, 
>>>> actually I'd be fine.
>>>>
>>>> I rode down the stairs to the underpass on the weekend, I wont do that 
>>>> again. Surprise surprise, Grant knows his bikes best.
>>>>
>>>>
>>> -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "RBW Owners Bunch" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to rbw-owners-bun...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/rbw-owners-bunch/69fbd616-06f2-4179-adf1-a46cf0c81174n%40googlegroups.com
>>>  
>>> <https://groups.google.com/d/msgid/rbw-owners-bunch/69fbd616-06f2-4179-adf1-a46cf0c81174n%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>>
>>>
>>> -- 
> You received this message because you are subscribed to the Google Groups 
> "RBW Owners Bunch" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to rbw-owners-bun...@googlegroups.com.
>
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/rbw-owners-bunch/83544226-52a4-46fd-9e8e-8bf30b9eec6dn%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/rbw-owners-bunch/83544226-52a4-46fd-9e8e-8bf30b9eec6dn%40googlegroups.com?utm_medium=email_source=footer>
> .
>
>

-- 
You received this message because you are subscribed to the Google Groups "RBW 
Owners Bunch" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rbw-owners-bunch+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/rbw-owners-bunch/ce272588-1e04-486e-a1c8-2a94558a9716n%40googlegroups.com.

Re: [RBW] Susie's Limits

[Wesley]

All else being equal (especially tubing size - which, maybe it's not the 
same across sizes?), the larger size will be less strong than the smaller 
sizes, while generally having a heavier rider. I am very curious what the 
rider did to break his bike and I am also very happy to read that he has 
apparently shrugged it off and seems to derive some satisfaction from the 
repair.

On Tuesday, July 5, 2022 at 3:12:42 PM UTC-7 Wesley wrote:

> Well, they do offer the same bike in a version that will support a heavier 
> rider. But I agree that people who fit the largest sizes are going to be 
> flirting with Susie's weight limit even before adding gear. For instance 
> I've got a 93cm PBH and weigh 190+, so I wouldn't be able to put much on a 
> Susie and keep within the limits.
> -W
>
> On Tuesday, July 5, 2022 at 2:59:28 PM UTC-7 campyo...@me.com wrote:
>
>> I find the weight limits very interesting. Rivendell has always marketed 
>> their bikes as the “anti-racer” or “not light” alternative to wispy 
>> aluminum and carbon bikes. Selling a bike with a weight limit most of us 
>> would exceed seems strange. A max of 160 pounds implies to me a bike unlike 
>> what I would expect from a company that urges us to take their products, 
>> load a bunch of stuff on them, and ride on unpaved trails to an overnight 
>> campout. After all, if I put 10 pounds of stuff on the bike, I can only 
>> weight 150 pounds myself?
>>
>> Am I missing something?
>>
>> --Eric “Heavier than 160 Pounds” Norris
>> campyo...@me.com
>> Insta: @CampyOnlyGuy
>> YouTube: YouTube.com/CampyOnlyGuy 
>>
>> On Jul 5, 2022, at 2:48 PM, Ryan Frahm  wrote:
>>
>> I did tell them that I ride semi aggressive and would be bikepacking, I 
>> just don’t do any big jumps. They still told me Susie at my weight. So I’d 
>> imagine there was some other factors for that break. But I guess I’d be 
>> crazy loaded if I got over it 200 total with me and my camp gear. 
>>
>> I can say that it rides smoother than anything I’ve ever ridden, I wonder 
>> if the Gus truly has that same ride. I only have 60 or so miles on it and 
>> it has been mostly bike path. We’ll see how it goes when I get a chance to 
>> take it on some real trails!
>>
>> On Tuesday, July 5, 2022 at 2:18:10 PM UTC-7 brendonoid wrote:
>>
>>> Originally it was 160 pounds, one of the main reasons I didn't jump on 
>>> the first batch. Over six foot that was a very low weight limit and it made 
>>> me nervous. Somewhat Ironically, photos of this exact bike made me think, 
>>> actually I'd be fine.
>>>
>>> I rode down the stairs to the underpass on the weekend, I wont do that 
>>> again. Surprise surprise, Grant knows his bikes best.
>>>
>>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "RBW Owners Bunch" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to rbw-owners-bun...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/rbw-owners-bunch/69fbd616-06f2-4179-adf1-a46cf0c81174n%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/rbw-owners-bunch/69fbd616-06f2-4179-adf1-a46cf0c81174n%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>>
>>

-- 
You received this message because you are subscribed to the Google Groups "RBW 
Owners Bunch" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rbw-owners-bunch+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/rbw-owners-bunch/83544226-52a4-46fd-9e8e-8bf30b9eec6dn%40googlegroups.com.

Re: [RBW] Susie's Limits

[Wesley]

Well, they do offer the same bike in a version that will support a heavier 
rider. But I agree that people who fit the largest sizes are going to be 
flirting with Susie's weight limit even before adding gear. For instance 
I've got a 93cm PBH and weigh 190+, so I wouldn't be able to put much on a 
Susie and keep within the limits.
-W

On Tuesday, July 5, 2022 at 2:59:28 PM UTC-7 campyo...@me.com wrote:

> I find the weight limits very interesting. Rivendell has always marketed 
> their bikes as the “anti-racer” or “not light” alternative to wispy 
> aluminum and carbon bikes. Selling a bike with a weight limit most of us 
> would exceed seems strange. A max of 160 pounds implies to me a bike unlike 
> what I would expect from a company that urges us to take their products, 
> load a bunch of stuff on them, and ride on unpaved trails to an overnight 
> campout. After all, if I put 10 pounds of stuff on the bike, I can only 
> weight 150 pounds myself?
>
> Am I missing something?
>
> --Eric “Heavier than 160 Pounds” Norris
> campyo...@me.com
> Insta: @CampyOnlyGuy
> YouTube: YouTube.com/CampyOnlyGuy 
>
> On Jul 5, 2022, at 2:48 PM, Ryan Frahm  wrote:
>
> I did tell them that I ride semi aggressive and would be bikepacking, I 
> just don’t do any big jumps. They still told me Susie at my weight. So I’d 
> imagine there was some other factors for that break. But I guess I’d be 
> crazy loaded if I got over it 200 total with me and my camp gear. 
>
> I can say that it rides smoother than anything I’ve ever ridden, I wonder 
> if the Gus truly has that same ride. I only have 60 or so miles on it and 
> it has been mostly bike path. We’ll see how it goes when I get a chance to 
> take it on some real trails!
>
> On Tuesday, July 5, 2022 at 2:18:10 PM UTC-7 brendonoid wrote:
>
>> Originally it was 160 pounds, one of the main reasons I didn't jump on 
>> the first batch. Over six foot that was a very low weight limit and it made 
>> me nervous. Somewhat Ironically, photos of this exact bike made me think, 
>> actually I'd be fine.
>>
>> I rode down the stairs to the underpass on the weekend, I wont do that 
>> again. Surprise surprise, Grant knows his bikes best.
>>
>>
> -- 
> You received this message because you are subscribed to the Google Groups 
> "RBW Owners Bunch" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to rbw-owners-bun...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/rbw-owners-bunch/69fbd616-06f2-4179-adf1-a46cf0c81174n%40googlegroups.com
>  
> 
> .
>
>
>

-- 
You received this message because you are subscribed to the Google Groups "RBW 
Owners Bunch" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rbw-owners-bunch+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/rbw-owners-bunch/12c3cde1-da87-491b-9850-3c13bdc63f59n%40googlegroups.com.

[RBW] Re: Susie's Limits

[Wesley]

Huh, I wonder what happened! Reddit jumbles the comments based on upvotes, 
so it's pretty tough to find information. Do you know how he broke the 
downtube? It seems weird to me (not a frame maker, designer, nor engineer) 
that it broke in the middle rather than near one end.

On Tuesday, July 5, 2022 at 10:21:27 AM UTC-7 Paul Clifton wrote:

> This trip gallery was posted to the bikepacking forum on Reddit: 
> https://www.reddit.com/r/bikepacking/comments/vpan76/plenty_of_good_times_a_broken_frame_rowdy/
>
> I don't know the riders or anything, but the gallery shows what I think 
> are 3 Susie/Gus bikes and one other bike I don't recognize. There's an 
> orange Susie hauling about a gallon of water, a full front basket, and a 
> massive saddle bag. It's frame cracked.
>
> I'm usually one to scoff at load limits, but I guess at some point, 
> they're to be taken seriously. I'm glad these guys were able to get the 
> frame fixed and finish their trip. It looks like a really good time!
>
> But still, I thought y'all would be interested to see what it takes to 
> break a Susie. As a chronic over packer and heavy person, I'm even more 
> glad I picked the Gus!
>
> Paul in AR
>

-- 
You received this message because you are subscribed to the Google Groups "RBW 
Owners Bunch" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rbw-owners-bunch+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/rbw-owners-bunch/c178b96a-2f0b-4aac-8b4e-3dc24f4f4c11n%40googlegroups.com.

[RBW] Re: Craigslist (and others) Bikes For Sale: 3

[Wesley]

That Heron is gorgeous.
-W

On Saturday, July 2, 2022 at 10:07:21 AM UTC-7 eric...@gmail.com wrote:

> Heron
> 61cm
> $2,000
> Santa Montica, CA
>
> https://www.pinkbike.com/buysell/3366921/
>
> [image: p6pb22809883.jpg]
>
> On Friday, June 24, 2022 at 2:21:49 PM UTC-4 Matthew Williams wrote:
>
>> Atlantis
>> 56cm
>> 1800
>> Seattle, WA
>>
>> https://seattle.craigslist.org/see/bik/d/seattle-rivendell-atlantis/7500600207.html
>>
>>

-- 
You received this message because you are subscribed to the Google Groups "RBW 
Owners Bunch" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rbw-owners-bunch+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/rbw-owners-bunch/4c2d3442-7e08-4bcf-bed5-2732e789044fn%40googlegroups.com.

Re: [cayugabirds-l] bird guide for Europe

[Wesley M. Hochachka]

I'll second Kevin's recommendation of that field guide, which Princeton 
University Press publishes in the U.S.  I'm not suggesting buying from here, 
but here's the cover picture and other information: 
https://www.amazon.com/Birds-Europe-Second-Princeton-Guides/dp/0691143927.  As 
far as I know, it's still the best field guide for European birds...at least 
until the 3rd edition comes out later this year.  For birds of Poland the 
updates will be essentially irrelevant, and the 2nd edition should be widely 
marked down to clear stock.

   Also definitely download the Western Palearctic "bird pack" for Merlin, if 
for no other reason than to have recordings of vocalizations available.  Note 
that the Song ID feature will cover most, but not all Polish species (Sound ID 
coverage is better west of the former Iron Curtain).

   I'm afraid that I don't know any Polish birding guides.

Wesley




From: bounce-126651864-3494...@list.cornell.edu 
 on behalf of Kevin J. McGowan 

Sent: Thursday, June 30, 2022 17:56
To: Carol Cedarholm 
Cc: CAYUGABIRDS-L 
Subject: RE: [cayugabirds-l] bird guide for Europe


You don’t need internet or cell service to use Merlin. You download the “pack” 
you need before you go, and it works totally offline.



As to books, I like Mullarney et al., but I don’t know if there is anything 
newer and better.



Kevin





From: Carol Cedarholm 
Sent: Thursday, June 30, 2022 5:18 PM
To: Kevin J. McGowan 
Cc: CAYUGABIRDS-L 
Subject: Re: [cayugabirds-l] bird guide for Europe



Thanks so much, Kevin.  Can you recommend a book, though?  I wonder about 
internet access in more remote parts of Poland.





On Thu, Jun 30, 2022 at 4:37 PM Kevin J. McGowan 
mailto:k...@cornell.edu>> wrote:

The Cornell Lab’s Merlin app covers Europe, and it can tell you what birds are 
most likely to be encountered in Poland in September. It’s really handy when 
traveling in a foreign country where you don’t know what is common and what 
isn’t. We used it constantly on a trip to Spain a couple of years ago.



Best,



Kevin McGowan



From: 
bounce-126651362-3493...@list.cornell.edu<mailto:bounce-126651362-3493...@list.cornell.edu>
 
mailto:bounce-126651362-3493...@list.cornell.edu>>
 On Behalf Of Carol Cedarholm
Sent: Thursday, June 30, 2022 4:03 PM
To: CAYUGABIRDS-L 
mailto:cayugabird...@list.cornell.edu>>
Subject: [cayugabirds-l] bird guide for Europe



Hello,

I am going to Poland in September and plan to do some birding.  Can anyone 
recommend a bird guide book and app for Europe? Also, can anyone recommend 
areas to bird and individuals they know who could guide us once there?

Thanks,

Carol Cedarhollm

--

Cayugabirds-L List Info:

Welcome and Basics<http://www.northeastbirding.com/CayugabirdsWELCOME>

Rules and Information<http://www.northeastbirding.com/CayugabirdsRULES>

Subscribe, Configuration and 
Leave<http://www.northeastbirding.com/CayugabirdsSubscribeConfigurationLeave.htm>

Archives:

The Mail 
Archive<http://www.mail-archive.com/cayugabirds-l@cornell.edu/maillist.html>

Surfbirds<http://www.surfbirds.com/birdingmail/Group/Cayugabirds>

BirdingOnThe.Net<http://birdingonthe.net/mailinglists/CAYU.html>

Please submit your observations to eBird<http://ebird.org/content/ebird/>!

--

--
Cayugabirds-L List Info:
Welcome and Basics<http://www.northeastbirding.com/CayugabirdsWELCOME>
Rules and Information<http://www.northeastbirding.com/CayugabirdsRULES>
Subscribe, Configuration and 
Leave<http://www.northeastbirding.com/CayugabirdsSubscribeConfigurationLeave.htm>
Archives:
The Mail 
Archive<http://www.mail-archive.com/cayugabirds-l@cornell.edu/maillist.html>
Surfbirds<http://www.surfbirds.com/birdingmail/Group/Cayugabirds>
BirdingOnThe.Net<http://birdingonthe.net/mailinglists/CAYU.html>
Please submit your observations to eBird<http://ebird.org/content/ebird/>!
--

--

Cayugabirds-L List Info:
http://www.NortheastBirding.com/CayugabirdsWELCOME
http://www.NortheastBirding.com/CayugabirdsRULES
http://www.NortheastBirding.com/CayugabirdsSubscribeConfigurationLeave.htm

ARCHIVES:
1) http://www.mail-archive.com/cayugabirds-l@cornell.edu/maillist.html
2) http://www.surfbirds.com/birdingmail/Group/Cayugabirds
3) http://birdingonthe.net/mailinglists/CAYU.html

Please submit your observations to eBird:
http://ebird.org/content/ebird/

--

[RBW] Re: Rain! What do you ride?

[Wesley]

I've owned (I think) four copies of the Marmot Precip jacket over the 
years. It's an excellent minimalist and inexpensive rain shell - just a 
single layer of GoreTex with a hood and zip-up armpit vents.

On Monday, June 27, 2022 at 12:29:34 PM UTC-7 Wesley wrote:

> I have extensive experience with this even though I no longer live in a 
> rainy place.
>
> You can ride any bike. Fenders make all the difference if you'd like to 
> look presentable when you get where you're going. I would wear sandals 
> because they dry out, or heavy rubber boots when I feel like having warm 
> feet. Add a light rain shell to keep my upper body dry. Head, glasses, 
> pants: let them get wet. They'll dry off soon enough.
> -W
>
> On Monday, June 27, 2022 at 11:54:18 AM UTC-7 Patrick Moore wrote:
>
>> My interest may sound odd from someone riding in the desert, but 
>> precisely because rain is so relatively rare here (9" citywide average 
>> between 14" foothills and 5" Westside) that when it arrives, it's 
>> interesting.
>>
>> We've had the earliest and rainiest start to our SW Monsoon season in 
>> years if not decades, considerably reducing the fire danger so great just a 
>> couple of weeks ago (when there was a bush fire just 1 mile south of me; 
>> and I live along the bosque). We must have had as much as 2" of rain in the 
>> last 2 weeks, with more forecast.
>>
>> I wanted to ride in the rain to church yesterday morning, but was tired 
>> and late, and the rain kept off despite lowering clouds on morning's ride, 
>> although I carefully rode the Matthews 1:1 with new 4 1/2" front fender 
>> flap and carried my cape and so'wester.
>>
>> On the way out and back I passed a group of young mothers along the 
>> bosque bike trail shepherding a large group of very small children having 
>> the time of their lives riding little bikes in the mud and playing in a big 
>> mud puddle. Funny, you don't see small children playing in the puddles 
>> nowadays, but I remember having great fun, age about the same as these 
>> children playing in the flooded, muddy field across the street from my 
>> house; rather like Christopher Robin in the WtP story.
>>
>> But I'm curious, what do all y'all in rainy places wear and ride on in 
>> rainy weather? I find it fun to imagine the ideal rain bike: fixed gear (no 
>> damned ss freewheel to complicate things), full oil-bath chaincase, full 
>> fenders, with front extending 1/4 of the way around the forward curve of 
>> the tire, and flap skimming the tarmac, with skirts covering the spokes on 
>> the trailing 1/4 of the front wheel and forward 1/4 of the rear wheel; 
>> clips 'n' straps with toe covers; dyno lighting mounted sufficiently low to 
>> clear front and rear raincape overhang; have I missed anything?
>>
>> Oh, and while I've found that rain capes keep you perfectly dry from neck 
>> to knee even in SW downpours with howling winds -- I commuted extensively 
>> years ago across town with various rain capes, waxed cotton, various grades 
>> of plastic --  (and so'westers keep one dry from neck to crown) my lower 
>> legs and feet get wet. I guess this is where Splats come in handy?
>>
>> -- 
>>
>> ---
>> Patrick Moore
>> Alburquerque, Nuevo Mexico, Etats Unis d'Amerique, Orbis Terrarum
>>
>>

-- 
You received this message because you are subscribed to the Google Groups "RBW 
Owners Bunch" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rbw-owners-bunch+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/rbw-owners-bunch/e7147641-b713-4c6d-a262-f8e3160d0564n%40googlegroups.com.

[RBW] Re: Rain! What do you ride?

[Wesley]

I have extensive experience with this even though I no longer live in a 
rainy place.

You can ride any bike. Fenders make all the difference if you'd like to 
look presentable when you get where you're going. I would wear sandals 
because they dry out, or heavy rubber boots when I feel like having warm 
feet. Add a light rain shell to keep my upper body dry. Head, glasses, 
pants: let them get wet. They'll dry off soon enough.
-W

On Monday, June 27, 2022 at 11:54:18 AM UTC-7 Patrick Moore wrote:

> My interest may sound odd from someone riding in the desert, but precisely 
> because rain is so relatively rare here (9" citywide average between 14" 
> foothills and 5" Westside) that when it arrives, it's interesting.
>
> We've had the earliest and rainiest start to our SW Monsoon season in 
> years if not decades, considerably reducing the fire danger so great just a 
> couple of weeks ago (when there was a bush fire just 1 mile south of me; 
> and I live along the bosque). We must have had as much as 2" of rain in the 
> last 2 weeks, with more forecast.
>
> I wanted to ride in the rain to church yesterday morning, but was tired 
> and late, and the rain kept off despite lowering clouds on morning's ride, 
> although I carefully rode the Matthews 1:1 with new 4 1/2" front fender 
> flap and carried my cape and so'wester.
>
> On the way out and back I passed a group of young mothers along the bosque 
> bike trail shepherding a large group of very small children having the time 
> of their lives riding little bikes in the mud and playing in a big mud 
> puddle. Funny, you don't see small children playing in the puddles 
> nowadays, but I remember having great fun, age about the same as these 
> children playing in the flooded, muddy field across the street from my 
> house; rather like Christopher Robin in the WtP story.
>
> But I'm curious, what do all y'all in rainy places wear and ride on in 
> rainy weather? I find it fun to imagine the ideal rain bike: fixed gear (no 
> damned ss freewheel to complicate things), full oil-bath chaincase, full 
> fenders, with front extending 1/4 of the way around the forward curve of 
> the tire, and flap skimming the tarmac, with skirts covering the spokes on 
> the trailing 1/4 of the front wheel and forward 1/4 of the rear wheel; 
> clips 'n' straps with toe covers; dyno lighting mounted sufficiently low to 
> clear front and rear raincape overhang; have I missed anything?
>
> Oh, and while I've found that rain capes keep you perfectly dry from neck 
> to knee even in SW downpours with howling winds -- I commuted extensively 
> years ago across town with various rain capes, waxed cotton, various grades 
> of plastic --  (and so'westers keep one dry from neck to crown) my lower 
> legs and feet get wet. I guess this is where Splats come in handy?
>
> -- 
>
> ---
> Patrick Moore
> Alburquerque, Nuevo Mexico, Etats Unis d'Amerique, Orbis Terrarum
>
>

-- 
You received this message because you are subscribed to the Google Groups "RBW 
Owners Bunch" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rbw-owners-bunch+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/rbw-owners-bunch/41ddf993-8ead-43cb-830d-e1f1e7da58a2n%40googlegroups.com.

[RBW] Re: Garage sale Charlie Gallops

[Wesley]

God, that purple is incredible though.

On Friday, June 24, 2022 at 4:52:32 PM UTC-7 Wesley wrote:

> LMAO those went fast. The large Gus and large Susie are still on offer, 
> though.d

-- 
You received this message because you are subscribed to the Google Groups "RBW 
Owners Bunch" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rbw-owners-bunch+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/rbw-owners-bunch/c7e31438-36f7-40c1-8164-b397a1567703n%40googlegroups.com.

[RBW] Garage sale Charlie Gallops

[Wesley]

LMAO those went fast. The large Gus and large Susie are still on offer, 
though.d

-- 
You received this message because you are subscribed to the Google Groups "RBW 
Owners Bunch" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rbw-owners-bunch+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/rbw-owners-bunch/a6ab84b3-300a-4f13-9f0d-7e8c4270fc58n%40googlegroups.com.

Re: [RBW] Re: FS: 52cm Clem-L, 2016 $1500

[Wesley]

Hi Annie,
I just read your blog post about selling the Clem. You mentioned problems 
getting it into an Amtrak rack... is the bike just too long to fit on 
Amtrak, even if weight were not a problem? I am looking at a Clem but have 
worried about exactly that issue.
-Wes

On Friday, June 24, 2022 at 2:40:22 PM UTC-7 cycli...@gmail.com wrote:

> Wishing you success in finding a local buyer.  I've enjoyed your blog for 
> years.
>
> David
>
> On Friday, June 24, 2022 at 2:34:25 PM UTC-7 rmro...@gmail.com wrote:
>
>> If you find a buyer that requires shipping just take it to Analog to box 
>> / ship. They do it every day & it will be worth it to the buyer to know it 
>> is done right. 
>>
>> Sent from my iPhone
>>
>> On Jun 24, 2022, at 12:13 PM, anniebikes  wrote:
>>
>> I need to find a New England buyer. After reading all the shipping woes 
>> (chipped paint), no way am I planning on shipping this baby!
>>
>>
>>
>> On Thursday, June 23, 2022 at 9:23:54 PM UTC-4 Doug H. wrote:
>>
>>> Beautiful bike and so well equipped. I think this is a DEAL! 
>>> Doug
>>>
>>> On Thursday, June 23, 2022 at 10:56:04 AM UTC-4 anniebikes wrote:
>>>
 For sale is my Rivendell Clem step through. It's been well taken care 
 of with low mileage - less than 1000 miles. I have upgraded it to lighten 
 it, but it no longer fits my image of the perfect touring bike.

 For pick up only in Vermont.

 Stock parts include drivetrain with wide low double gearing: 24, 38 
 chainrings with 34-16 cassette, 650B wheels, Nitto stem, thumb shifters.

 Upgrades include Soma Oxford handle bar, Selle Royal ergonomic grips, 
 SKS fenders, rear rack, Sunlite front rack, and Panaracer Pasela PT 1.75 
 tires.

 Minor scratches, always stored indoors.

 Craigslist ad with lots of photos:

 https://vermont.craigslist.org/bik/d/colchester-rivendell-clem/7499137801.html

 anniebi...@gmail.com[image: PXL_20220618_152327404.jpg]

>>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "RBW Owners Bunch" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to rbw-owners-bun...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/rbw-owners-bunch/ab25fecf-1185-4a7d-90a3-5a897ead3287n%40googlegroups.com
>>  
>> 
>> .
>>
>>

-- 
You received this message because you are subscribed to the Google Groups "RBW 
Owners Bunch" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rbw-owners-bunch+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/rbw-owners-bunch/d61eba06-9869-4537-8334-7568eed0bcecn%40googlegroups.com.

[RBW] Re: FS: '84 Trek 720 (19"), Billie Bars

[Wesley]

Thanks, Collin - I agree that the levee reconstruction is necessary, if 
annoying.
I've heard of the West Sac gravel to Bike Dog rides - just for curiosity's 
sake, how does the group approach the short stretch of road between the 
port entrance and Bike Dog (if finishing the ride from the West)?
-W

On Thursday, June 23, 2022 at 8:41:56 AM UTC-7 Collin A wrote:

> Hey Wesley,
>
> I moved February 2020, so I'm right there with you! The riding is 
> definitely not as diverse as some other locales, but here is what I've 
> found so far that are doable from downtown-ish-area that stick to car-less 
> roads/paths:
>
>- Really fun (sometimes gray-area legal) single track along the ART 
>all the way up to Folsom. Unfortunately, a lot of the construction going 
> on 
>has eliminated that for the time being...
>- There is a fun gravel loop that a group of us do on Thursdays along 
>the West Sacramento Levees. We meet at Velo Veritas at 5:30 on Thursdays 
> if 
>you want to join, its a chill group and we end at Bikedog afterwards :)
>- There is the CHP loop that runs along the levees in West Sac as well 
>that loops around the CHP training facility
>- Rides out to Davis along the causeway (not the most pleasant, I 
>know) and then doing a bunch of the levee roads that surround the town
>- A fun out-and-back ride up to the Fremont weir (My normal route is 
>closed due to construction for now, its accessible, but requires a lot 
> more 
>pavement on the river highway, which is dangerous)
>- A bunch of other road rides that are a little sketchy when you do 
>them by yourself (IMO)
>- And obviously a short drive up to Auburn or Folsom for some great 
>singletrack and more rugged gravel roads with elevation!
>
> I realize that a couple of the routes are closed due to construction, but 
> its a good thing. Sacramento is the highest flood-risk city in the nation 
> and a lot of these projects are occurring to improve the safety of the 
> levees that protect the city and nearby areas. Its just a bummer they are 
> all going on at once!
>
> Collin, when the levee breaks, in Sacramento
> On Thursday, June 23, 2022 at 7:56:57 AM UTC-7 Wesley wrote:
>
>> Collin, any suggestions of good rides in Sac and environs? I arrived in 
>> 2020 and haven't found much to love aside from the American River trail 
>> (which is excellent).
>> -W
>> On Wednesday, June 22, 2022 at 9:26:17 PM UTC-7 Collin A wrote:
>>
>>> 720 is gonzo, thanks folks!
>>>
>>> Collin in Sacratomato
>>>
>>> On Wednesday, June 22, 2022 at 10:27:03 AM UTC-7 Collin A wrote:
>>>
>>>> The 720 is pending...
>>>>
>>>> Collin in Sactown
>>>>
>>>> On Monday, June 20, 2022 at 5:52:37 PM UTC-7 Collin A wrote:
>>>>
>>>>> Well, the Billie Bars are spoken for...
>>>>>
>>>>> The long-stayed Trek is still up for grabs! A rivendell-like ride for 
>>>>> a fraction of the price of a Rivendell...
>>>>>
>>>>> Collin, who is already thinking about new projects, in Sacramento
>>>>>
>>>>> On Monday, June 20, 2022 at 4:24:41 PM UTC-7 Collin A wrote:
>>>>>
>>>>>> Howdy Bunch,
>>>>>>
>>>>>> I've got a few things lingering in the bike closet that need to go! 
>>>>>>
>>>>>> Photos here:
>>>>>> https://photos.app.goo.gl/fq8pdK8MorGTXYNN7
>>>>>>
>>>>>> *1984 Trek 720, size 19"* - Comes with frame, fork, FSA duron 
>>>>>> headset and kalloy 27.2 seatpost. I bought this a couple months ago from 
>>>>>> IBOB, so its a bit of a catch-and-release + some extras. I built this up 
>>>>>> for my wife to use as a loaner bike over the summer...needless to say 
>>>>>> she 
>>>>>> liked it, but now she is back in SLC with her Rivendell and I no longer 
>>>>>> have a need for it. Fits 700x35 with fenders on skinny rims with 
>>>>>> older-style cantilever brakes - Hoping for *$500 + shipping*. I'll 
>>>>>> need to hunt down a bike box.
>>>>>>
>>>>>> *Billie Bars* - They are in generally good condition...however, this 
>>>>>> is from the first batch where the clamp diameter is just ever so 
>>>>>> slightly 
>>>>>> less than 22.2, which means some brakes/shifters/etc. won't work well 
>>>>>> without a thin layer of electrical tape to add some extra diameter. 
>>>>>> However, some lower-end components will fit fine for whatever reason - 
>>>>>> Hoping for *$70+shipping.*
>>>>>>
>>>>>> I'm going through some other bits and bobs and will likely update the 
>>>>>> photo album, so if you see something that is of interest just let me 
>>>>>> know!
>>>>>>
>>>>>> Cheers,
>>>>>> Collin in Sactown
>>>>>>
>>>>>

-- 
You received this message because you are subscribed to the Google Groups "RBW 
Owners Bunch" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rbw-owners-bunch+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/rbw-owners-bunch/54064666-f81e-41e1-91fe-3055da1de7can%40googlegroups.com.

[RBW] Re: FS: '84 Trek 720 (19"), Billie Bars

[Wesley]

Collin, any suggestions of good rides in Sac and environs? I arrived in 
2020 and haven't found much to love aside from the American River trail 
(which is excellent).
-W
On Wednesday, June 22, 2022 at 9:26:17 PM UTC-7 Collin A wrote:

> 720 is gonzo, thanks folks!
>
> Collin in Sacratomato
>
> On Wednesday, June 22, 2022 at 10:27:03 AM UTC-7 Collin A wrote:
>
>> The 720 is pending...
>>
>> Collin in Sactown
>>
>> On Monday, June 20, 2022 at 5:52:37 PM UTC-7 Collin A wrote:
>>
>>> Well, the Billie Bars are spoken for...
>>>
>>> The long-stayed Trek is still up for grabs! A rivendell-like ride for a 
>>> fraction of the price of a Rivendell...
>>>
>>> Collin, who is already thinking about new projects, in Sacramento
>>>
>>> On Monday, June 20, 2022 at 4:24:41 PM UTC-7 Collin A wrote:
>>>
 Howdy Bunch,

 I've got a few things lingering in the bike closet that need to go! 

 Photos here:
 https://photos.app.goo.gl/fq8pdK8MorGTXYNN7

 *1984 Trek 720, size 19"* - Comes with frame, fork, FSA duron headset 
 and kalloy 27.2 seatpost. I bought this a couple months ago from IBOB, so 
 its a bit of a catch-and-release + some extras. I built this up for my 
 wife 
 to use as a loaner bike over the summer...needless to say she liked it, 
 but 
 now she is back in SLC with her Rivendell and I no longer have a need for 
 it. Fits 700x35 with fenders on skinny rims with older-style cantilever 
 brakes - Hoping for *$500 + shipping*. I'll need to hunt down a bike 
 box.

 *Billie Bars* - They are in generally good condition...however, this 
 is from the first batch where the clamp diameter is just ever so slightly 
 less than 22.2, which means some brakes/shifters/etc. won't work well 
 without a thin layer of electrical tape to add some extra diameter. 
 However, some lower-end components will fit fine for whatever reason - 
 Hoping for *$70+shipping.*

 I'm going through some other bits and bobs and will likely update the 
 photo album, so if you see something that is of interest just let me know!

 Cheers,
 Collin in Sactown

>>>

-- 
You received this message because you are subscribed to the Google Groups "RBW 
Owners Bunch" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rbw-owners-bunch+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/rbw-owners-bunch/88072797-ce6a-4367-aee7-906527f5eeedn%40googlegroups.com.

[RBW] Re: Clem L Paint Crisis

[Wesley]

Ah, that's a tough break Kiley. I'd seek out the best match you can find in 
Sally Hansen nail polish. Here's a quote from Grant's latest Blahg so you 
know it's got official approval:

"We (well, I) use nail polish. Joe Bell, world's best bike painter, once 
told me he thought nail polish was super as touch-up paint, even tougher 
than his own paint. It comes in tons of colors and costs $4 to $8 per vial, 
and if you don't like your work, you can always use, you guessed it, nail 
polish remover. Pedals are fun, but it's kind of a shame that you cover up 
your work when you're riding. Do stems, seat posts, handlebars, hubs, inner 
perimeters of rims, spokes, derailers (I did a sloppy job on my most-used 
derailer, and ... I like it)." 

On Wednesday, June 22, 2022 at 7:19:01 AM UTC-7 Kiley Demond wrote:

> As some of you know, I have been looking for an early-model 59cm Clem L, 
> preferably orange with blue the runner-up. I preferred frame-only because I 
> knew that I would probably replace 80% of the components. For some reason, 
> I took the wheels too. The frame was pristine but in shipping, the wheels 
> were lashed to the frame with a tie-wrap, the hub protector popped off, and 
> the hub proceeded to gouge the frame for several days in transit.
>
> I bought this for myself for my 64th birthday and I am bitterly 
> disappointed. I can return the frame and start my search over, or I can 
> propose remediation. What will it take to fix this? I can live with a 
> little bit of marking but it obviously needs to be repaired to seal the 
> frame and reduce the cosmetic sting. I can contact Riv about touch-up 
> paint, but the frame is from 2016, so
>
> Thank you in advance for your thoughts.
>
> -Kiley
>
> [image: IMG_3218D.jpeg][image: IMG_3222D.jpeg][image: IMG_3216D.jpeg]
>

-- 
You received this message because you are subscribed to the Google Groups "RBW 
Owners Bunch" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rbw-owners-bunch+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/rbw-owners-bunch/296e412c-f9cf-4dcf-9d77-ef1f7f2d4cabn%40googlegroups.com.

Re: [RBW] Hillibikes are so close!

[Wesley]

Volvo 240 has got to be the Rivendell of cars.

On Friday, June 17, 2022 at 4:57:45 AM UTC-7 brendonoid wrote:

> It has been a crazy week but I managed to get a start on the build this 
> afternoon. The fillet brazing and paint on this bike is truly amazing in 
> person.
> I am so glad that I'd missed out on the larges and been forced to go with 
> the XL, turns out it is the perfect size for me.
> Sorry for the poor photo courtesy of my fluoro tube lit garage.
> [image: DSC_0126.JPG]
>
>

-- 
You received this message because you are subscribed to the Google Groups "RBW 
Owners Bunch" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rbw-owners-bunch+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/rbw-owners-bunch/dd900fef-9d92-4347-9419-59a223e5ae6bn%40googlegroups.com.

Re: [RBW] 26” to 650c on Rambouillet

[Wesley]

Yes, I should have been more clear - the bars just caught my eye, and your 
setup is new to me. It looks nice! I was surprised to read that you've 
found it difficult to get 26" road tires, since that wheel size is so 
universal. But I checked it out and you're right that all of the 26" road 
tires are for commuters. I'll file that under "good to know"!

On Wednesday, June 15, 2022 at 11:59:35 AM UTC-7 Fullylugged wrote:

> Patrick:
> I took the original comment on the bar as a positive. The angled inverted 
> mustache bars are nice for a senior citizen back. The Walnut studio grip 
> has held up well.  As to other observation of “so many things wrong,” that 
> seems to violate the list rules of etiquette. I’ll leave it to the 
> moderator to opine there. The bike has about 17k miles on it and most have 
> been really nice ones.
>
> My point was just to share that the wheel size works if you need it. 
>  While 26” tires are around in the 28 - 32 size this bike was made for, 
> road wheels (other than custom builds) are getting scarcer in that size. 
>  Brake bridge location was at times an issue on this model. I’m not 
> extolling it as the next big thing.
>
> Ymmv
>
> Sent from my iPad
>
> On Jun 15, 2022, at 1:29 PM, Patrick Moore  wrote:
>
> 
>
> Alas, the selection of tires available for the 650C size was miniscule in 
> 2015, and may be less than miniscule now, and those available were mostly 
> 23 mm models, tho' I think Terry made a rather heavy 28 mm model. Tho' the 
> selection of good road-capable 559 tires is small, it's a heckofalot bigger 
> than that for 571.
>
> There's only about 1/4" radial difference between 559 and 571 sizes: my 
> 650C wheels with 23 mm Pro Races measured about 24.5" in diameter, my 559 
> wheels with 23 mm Turbos measured 24" in diameter. Past tense for both.
>
> Patrick Moore, who still has a small stash of Sun ME14A 650C rims waiting 
> for the time when BQ introduces its full line of 571 tires, from 26 mm to 
> 60 mm in smooth and knobby models.
>
> And, yes, that bar. So, so many things wrong. (But if the rider found it 
> the best solution to needs, and this is not merely a desperate attempt to 
> make an unrideable bike rideble, more power to him/her.)
>
>
>
> On Wed, Jun 15, 2022 at 8:07 AM Fullylugged  wrote:
>
>> In the course of work on another bike, a set of 650c (571mm) wheels 
>> became surplus. Just to see, I tried them on my 52cm Rambouillet. The 50 
>> and 52 Ram sizes are built for 26” (559mm) wheels. And yes they fit just 
>> fine.  Plenty of room to adjust the brake pads on the stock Tiagra Calipers 
>> Riv shipped on the bikes.  In case you need wheels and 26” road selection 
>> is too limited, you can look at this size too.
>>
>> Still Fullylugged…..
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "RBW Owners Bunch" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to rbw-owners-bun...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/rbw-owners-bunch/481385b3-0f06-441e-837d-5991e9c1f4abn%40googlegroups.com
>>  
>> 
>> .
>>
>
>
> -- 
>
> ---
> Patrick Moore
> Alburquerque, Nuevo Mexico, Etats Unis d'Amerique, Orbis Terrarum
>
> -- 
>
> You received this message because you are subscribed to a topic in the 
> Google Groups "RBW Owners Bunch" group.
> To unsubscribe from this topic, visit 
> https://groups.google.com/d/topic/rbw-owners-bunch/YBnySKw4_Bk/unsubscribe
> .
> To unsubscribe from this group and all its topics, send an email to 
> rbw-owners-bun...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/rbw-owners-bunch/CALuTfgvzmExVY0QjNqHTkDavPMg_9qqFu7VMDxpu%2BpKvYVMz%3DQ%40mail.gmail.com
>  
> 
> .
>
>

-- 
You received this message because you are subscribed to the Google Groups "RBW 
Owners Bunch" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rbw-owners-bunch+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/rbw-owners-bunch/192a8e32-6b6a-4f98-8702-d3eb8b219caan%40googlegroups.com.

Pure Storage reaching out about possibly contributing an article

[Wesley Anderson]

Hello,

My name is Wesley, and I'm reaching out to www.debian.org on behalf of Pure
Storage. Our mission at Pure Storage is to redefine the online storage
experience and empower businesses by simplifying how people consume and
interact with data.

While looking for websites that offer educational content in our field, I
saw your site and thought it was worth asking if you were open to outside
article contributions? We'd love to create an article for you!

Ultimately, we aim to help other businesses navigate the complexities of
the cloud, online data storage, and AI and would love to provide a piece to
you for that purpose.

Please let me know if there are any guidelines, and I'm happy to set up a
quick call if need be.

Talk soon,
Wesley

--
WESLEY ANDERSON // Marketing Outreach*, Global SEO | *Pure Storage, Inc.
|  wander...@purestorage.com
[image: beacon]

[ceph-users] Re: Changes to Crush Weight Causing Degraded PGs instead of Remapped

[Wesley Dillingham]

I have found that I can only reproduce it on clusters built initially on
pacific. My cluster which went nautilus to pacific does not reproduce the
issue. My working theory is it is related to rocksdb sharding:

https://docs.ceph.com/en/quincy/rados/configuration/bluestore-config-ref/#rocksdb-shardingOSDs
deployed in Pacific or later use RocksDB sharding by default. If Ceph is
upgraded to Pacific from a previous version, sharding is off.
To enable sharding and apply the Pacific defaults, stop an OSD and run

ceph-bluestore-tool \
  --path  \
  --sharding="m(3) p(3,0-12) O(3,0-13)=block_cache={type=binned_lru} L P" \
  reshard


Respectfully,

*Wes Dillingham*
w...@wesdillingham.com
LinkedIn <http://www.linkedin.com/in/wesleydillingham>


On Tue, Jun 14, 2022 at 11:31 AM Wesley Dillingham 
wrote:

> I have made https://tracker.ceph.com/issues/56046 regarding the issue I
> am observing.
>
> Respectfully,
>
> *Wes Dillingham*
> w...@wesdillingham.com
> LinkedIn <http://www.linkedin.com/in/wesleydillingham>
>
>
> On Tue, Jun 14, 2022 at 5:32 AM Eugen Block  wrote:
>
>> I found the thread I was referring to [1]. The report was very similar
>> to yours, apparently the balancer seems to cause the "degraded"
>> messages, but the thread was not concluded. Maybe a tracker ticket
>> should be created if it doesn't already exist, I didn't find a ticket
>> related to that in a quick search.
>>
>> [1]
>>
>> https://lists.ceph.io/hyperkitty/list/ceph-users@ceph.io/thread/H4L5VNQJKIDXXNY2TINEGUGOYLUTT5UL/
>>
>> Zitat von Wesley Dillingham :
>>
>> > Thanks for the reply. I believe regarding "0" vs "0.0" its the same
>> > difference. I will note its not just changing crush weights which
>> induces
>> > this situation. Introducing upmaps manually or via the balancer also
>> causes
>> > the PGs to be degraded instead of the expected remapped PG state.
>> >
>> > Respectfully,
>> >
>> > *Wes Dillingham*
>> > w...@wesdillingham.com
>> > LinkedIn <http://www.linkedin.com/in/wesleydillingham>
>> >
>> >
>> > On Mon, Jun 13, 2022 at 9:27 PM Szabo, Istvan (Agoda) <
>> > istvan.sz...@agoda.com> wrote:
>> >
>> >> Isn’t it the correct syntax like this?
>> >>
>> >> ceph osd crush reweight osd.1 0.0 ?
>> >>
>> >> Istvan Szabo
>> >> Senior Infrastructure Engineer
>> >> ---
>> >> Agoda Services Co., Ltd.
>> >> e: istvan.sz...@agoda.com
>> >> ---
>> >>
>> >> On 2022. Jun 14., at 0:38, Wesley Dillingham 
>> >> wrote:
>> >>
>> >> ceph osd crush reweight osd.1 0
>> >>
>> >>
>> >> --
>> >> This message is confidential and is for the sole use of the intended
>> >> recipient(s). It may also be privileged or otherwise protected by
>> copyright
>> >> or other legal rules. If you have received it by mistake please let us
>> know
>> >> by reply email and delete it from your system. It is prohibited to copy
>> >> this message or disclose its content to anyone. Any confidentiality or
>> >> privilege is not waived or lost by any mistaken delivery or
>> unauthorized
>> >> disclosure of the message. All messages sent to and from Agoda may be
>> >> monitored to ensure compliance with company policies, to protect the
>> >> company's interests and to remove potential malware. Electronic
>> messages
>> >> may be intercepted, amended, lost or deleted, or contain viruses.
>> >>
>> > ___
>> > ceph-users mailing list -- ceph-users@ceph.io
>> > To unsubscribe send an email to ceph-users-le...@ceph.io
>>
>>
>>
>> ___
>> ceph-users mailing list -- ceph-users@ceph.io
>> To unsubscribe send an email to ceph-users-le...@ceph.io
>>
>
___
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to ceph-users-le...@ceph.io

[RBW] Re: 26” to 650c on Rambouillet

[Wesley]

Those handlebars, tho.

On Wednesday, June 15, 2022 at 7:06:51 AM UTC-7 Fullylugged wrote:

> In the course of work on another bike, a set of 650c (571mm) wheels became 
> surplus. Just to see, I tried them on my 52cm Rambouillet. The 50 and 52 
> Ram sizes are built for 26” (559mm) wheels. And yes they fit just fine. 
>  Plenty of room to adjust the brake pads on the stock Tiagra Calipers Riv 
> shipped on the bikes.  In case you need wheels and 26” road selection is 
> too limited, you can look at this size too.
>
> Still Fullylugged…..
>
>

-- 
You received this message because you are subscribed to the Google Groups "RBW 
Owners Bunch" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rbw-owners-bunch+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/rbw-owners-bunch/b4851244-4142-4137-b2e0-2442543b6e01n%40googlegroups.com.

[Mailman-Users] Removing the option to delete a list on the Postorious interface

[Wong, Wesley]

Hi, I have a question on the Postorious web interface in Mailman 3. I have 
found that a list owner can delete a list through the Postorious interface if 
they have the role of owner to the list. I wanted to have it either disabled or 
removed but I am not sure where to look to make changes to it.  I would rather 
remove it from the interface totally so it would be done from the command line. 
Any help would be greatly appreciated.

wesley
--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
https://mail.python.org/archives/list/mailman-users@python.org/

[ceph-users] Re: Changes to Crush Weight Causing Degraded PGs instead of Remapped

[Wesley Dillingham]

I have made https://tracker.ceph.com/issues/56046 regarding the issue I am
observing.

Respectfully,

*Wes Dillingham*
w...@wesdillingham.com
LinkedIn <http://www.linkedin.com/in/wesleydillingham>


On Tue, Jun 14, 2022 at 5:32 AM Eugen Block  wrote:

> I found the thread I was referring to [1]. The report was very similar
> to yours, apparently the balancer seems to cause the "degraded"
> messages, but the thread was not concluded. Maybe a tracker ticket
> should be created if it doesn't already exist, I didn't find a ticket
> related to that in a quick search.
>
> [1]
>
> https://lists.ceph.io/hyperkitty/list/ceph-users@ceph.io/thread/H4L5VNQJKIDXXNY2TINEGUGOYLUTT5UL/
>
> Zitat von Wesley Dillingham :
>
> > Thanks for the reply. I believe regarding "0" vs "0.0" its the same
> > difference. I will note its not just changing crush weights which induces
> > this situation. Introducing upmaps manually or via the balancer also
> causes
> > the PGs to be degraded instead of the expected remapped PG state.
> >
> > Respectfully,
> >
> > *Wes Dillingham*
> > w...@wesdillingham.com
> > LinkedIn <http://www.linkedin.com/in/wesleydillingham>
> >
> >
> > On Mon, Jun 13, 2022 at 9:27 PM Szabo, Istvan (Agoda) <
> > istvan.sz...@agoda.com> wrote:
> >
> >> Isn’t it the correct syntax like this?
> >>
> >> ceph osd crush reweight osd.1 0.0 ?
> >>
> >> Istvan Szabo
> >> Senior Infrastructure Engineer
> >> ---
> >> Agoda Services Co., Ltd.
> >> e: istvan.sz...@agoda.com
> >> ---
> >>
> >> On 2022. Jun 14., at 0:38, Wesley Dillingham 
> >> wrote:
> >>
> >> ceph osd crush reweight osd.1 0
> >>
> >>
> >> --
> >> This message is confidential and is for the sole use of the intended
> >> recipient(s). It may also be privileged or otherwise protected by
> copyright
> >> or other legal rules. If you have received it by mistake please let us
> know
> >> by reply email and delete it from your system. It is prohibited to copy
> >> this message or disclose its content to anyone. Any confidentiality or
> >> privilege is not waived or lost by any mistaken delivery or unauthorized
> >> disclosure of the message. All messages sent to and from Agoda may be
> >> monitored to ensure compliance with company policies, to protect the
> >> company's interests and to remove potential malware. Electronic messages
> >> may be intercepted, amended, lost or deleted, or contain viruses.
> >>
> > ___
> > ceph-users mailing list -- ceph-users@ceph.io
> > To unsubscribe send an email to ceph-users-le...@ceph.io
>
>
>
> ___
> ceph-users mailing list -- ceph-users@ceph.io
> To unsubscribe send an email to ceph-users-le...@ceph.io
>
___
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to ceph-users-le...@ceph.io

[ceph-users] Re: Changes to Crush Weight Causing Degraded PGs instead of Remapped

[Wesley Dillingham]

Thanks for the reply. I believe regarding "0" vs "0.0" its the same
difference. I will note its not just changing crush weights which induces
this situation. Introducing upmaps manually or via the balancer also causes
the PGs to be degraded instead of the expected remapped PG state.

Respectfully,

*Wes Dillingham*
w...@wesdillingham.com
LinkedIn <http://www.linkedin.com/in/wesleydillingham>


On Mon, Jun 13, 2022 at 9:27 PM Szabo, Istvan (Agoda) <
istvan.sz...@agoda.com> wrote:

> Isn’t it the correct syntax like this?
>
> ceph osd crush reweight osd.1 0.0 ?
>
> Istvan Szabo
> Senior Infrastructure Engineer
> ---
> Agoda Services Co., Ltd.
> e: istvan.sz...@agoda.com
> ---
>
> On 2022. Jun 14., at 0:38, Wesley Dillingham 
> wrote:
>
> ceph osd crush reweight osd.1 0
>
>
> --
> This message is confidential and is for the sole use of the intended
> recipient(s). It may also be privileged or otherwise protected by copyright
> or other legal rules. If you have received it by mistake please let us know
> by reply email and delete it from your system. It is prohibited to copy
> this message or disclose its content to anyone. Any confidentiality or
> privilege is not waived or lost by any mistaken delivery or unauthorized
> disclosure of the message. All messages sent to and from Agoda may be
> monitored to ensure compliance with company policies, to protect the
> company's interests and to remove potential malware. Electronic messages
> may be intercepted, amended, lost or deleted, or contain viruses.
>
___
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to ceph-users-le...@ceph.io

[ceph-users] Changes to Crush Weight Causing Degraded PGs instead of Remapped

[Wesley Dillingham]

I have a brand new Cluster 16.2.9 running bluestore with 0 client activity.
I am modifying some crush weights to move PGs off of a host for testing
purposes but the result is that the PGs go into a degraded+remapped state
instead of simply a remapped state. This is a strange result to me as in
previous releases (nautilus) this would cause only Remapped PGs. Are there
any known issues around this? Are others running Pacific seeing similar
behavior? Thanks.

"ceph osd crush reweight osd.1 0"

^ Causes degraded PGs which then go into recovery. Expect only remapped PGs

Respectfully,

*Wes Dillingham*
w...@wesdillingham.com
LinkedIn 
___
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to ceph-users-le...@ceph.io

[RBW] Re: Clem Smith Jr. L 59 cm Wheel Sizes

[Wesley]

Hey Jacob,
700c and 29er are the same thing - just called differently between the road 
and mountain bike worlds.
-W

On Wednesday, June 8, 2022 at 3:01:54 PM UTC-7 Jacob Lopez wrote:

> Hi, All.
>
> I did a quick search but didn't find a thread, so let me know if you know 
> of one re this topic and I can remove this re Clem L's 59cm with 29ers:
>
> I noticed on the Riv site that 59cm Clem's can take 700c rims and "29er 
> Tires".  Does that mean that it can take 29in rims, or...?   I may be 
> looking to size up on my 52cm Clem L to a 59cm and I'm super curious to how 
> 29's perform on this size.  Any experience with that (if, of course I'm 
> reading the specs right and the bike can take 29in wheels)?  Does this 
> introduce toe-overlap?
>
> Jacob
> San Diego, CA
>

-- 
You received this message because you are subscribed to the Google Groups "RBW 
Owners Bunch" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rbw-owners-bunch+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/rbw-owners-bunch/a9094ef4-081f-48b5-aa97-3d3dda5f52b5n%40googlegroups.com.

Re: [RBW] Re: #PlatyPosing: Post your pics here! (Riv Mixtes welcome, too.)

[Wesley]

Wow, the Mermaid color looks great in your photos, Christian (especially 
the first).
-W

On Tuesday, June 7, 2022 at 3:37:59 PM UTC-7 bei...@gmail.com wrote:

> Apologies, photos included here!
> [image: image0.jpeg][image: image10.jpeg]
>
> On Tuesday, June 7, 2022 at 4:34:30 PM UTC-6 Christian B-H wrote:
>
>> I could hardly be more excited to finally, after probably 3 or 4 years, 
>> be an official Riv *owner* not simply *reader*. In November/December I 
>> had *really *wanted a Gus. I missed it, and bought a Surly Karate Monkey 
>> in it's place. The chainstays are short, but it wheelies well and is fun to 
>> ride with jones bars. In March and April, I really wanted an Atlantis. I 
>> was too slow to decide to buy Bill Lindsey's, and hadn't convinced my wife 
>> in time to reserve one of the new batchBut, in the end, with some help 
>> from everyone here and especially Clark Fitzgerald's great report on his 
>> 1yr with Atlantis then switch to the Platy, Leah Petersenn "sold" another 
>> one. I convinced myself the Atlantis would've overlapped with my existing 
>> bikes too much anyways...
>>
>> Serendipitously,  after reaching out for Riv Riders on the Front Range in 
>> Colorado, Lance from Littleton offered to let me ride, *and *sell me his 
>> 60cm Mermaid Platy. We had a great ride this past Sunday before I brought 
>> it home to push all my neighbors to take a spin on it too, and since then I 
>> have ridden it at least for 1 minute of every hour I think (jumping out of 
>> my work-from-home-station to the garage to take a spin!). 
>>
>> I *love *the all-black aesthetics a la Crust build with black Antelope 
>> Hill extralights or Rylands from his June 2 post. I will update one day 
>> with new, bigger tires, and also racks, followed by changing out the cranks 
>> for gearing that will let me tackle group rides a little easier, inspired 
>> of course by Leah, just to shake things up a little bit! In the meantime, I 
>> am over the moon (or at least mountains) with my first ever Riv!
>>
>> Just Ride (Mixtes), 
>>
>> Christian in Boulder, CO
>>
>>
>>

-- 
You received this message because you are subscribed to the Google Groups "RBW 
Owners Bunch" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rbw-owners-bunch+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/rbw-owners-bunch/0a145ef1-096a-4eeb-8fbb-6efb9c300c20n%40googlegroups.com.

[RBW] Re: Current favorite tires in 60mm

[Wesley]

For many years I had Schwalbe Big Apples on my 29er single speed urban 
all-purpose bike. Now that bike is sadly departed and I have an old 26er 
MTB all-purpose bike with Schwalbe Fat Franks. Both of them are great tires 
for my purpose. The only downside is that they're heavy. I had the 29er in 
Wisconsin and the Big Apples were too slippery in snow, so I'd swap them 
for some big knobbies from WTB in winter.

On Friday, June 3, 2022 at 10:17:21 PM UTC-7 Ray Varella wrote:

> I’ve been riding the Schwalbe G one in 60mm x 650B on my Clem
> In an attempt to decode the various iterations of Schwalbe tires, the 
> Evolution casing are the lightest casing followed by the “performance” 
> line. 
>
> I would love to find these tires or the all road version in 70mm but only 
> the performance casing seems to be available. 
>
> I’ve ridden a number of Compass/Rene Herse tires as well as Gran Bois and 
> these G ones suit my usage just great. 
> Until either companies produce a 55mm or greater in smooth tread, I don’t 
> think there is a better fat smooth tread tire out there. 
>
> Does anyone have a favorite 55mm or larger multi purpose tire?
>
> Ray
>

-- 
You received this message because you are subscribed to the Google Groups "RBW 
Owners Bunch" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rbw-owners-bunch+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/rbw-owners-bunch/f44a9be8-d8b8-45ae-97f1-f25d711b3603n%40googlegroups.com.

[Bug 1977654] [NEW] installation failed

[Devin Wesley Harper]

Public bug reported:

Installation failed at 1st attempt in Try Ubuntu mode.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: ubiquity 22.04.15
ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
Uname: Linux 5.15.0-25-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.470
Date: Sat Jun  4 12:45:57 2022
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ubiquity (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug jammy ubiquity-22.04.15 ubuntu

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1977654

Title:
  installation failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1977654/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[ceph-users] Re: Slow delete speed through the s3 API

[Wesley Dillingham]

Is it just your deletes which are slow or writes and read as well?

On Thu, Jun 2, 2022, 4:09 PM J-P Methot  wrote:

> I'm following up on this as we upgraded to Pacific 16.2.9 and deletes
> are still incredibly slow. The pool rgw is using is a fairly small
> erasure coding pool set at 8 + 3. Is there anyone who's having the same
> issue?
>
> On 5/16/22 15:23, J-P Methot wrote:
> > Hi,
> >
> > First of all, a quick google search shows me that questions about the
> > s3 API slow object deletion speed have been asked before and are well
> > documented. My issue is slightly different, because I am getting
> > abysmal speeds of 11 objects/second on a full SSD ceph running Octopus
> > with about a hundred OSDs. This is much lower than the Redhat reported
> > limit of 1000 objects/second.
> >
> > I've seen elsewhere that it was a Rocksdb limitation and that it would
> > be fixed in Pacific, but the Pacific release logs do not show me
> > anything that suggest that. Furthermore, I have limited control over
> > the s3client deleting the files as it's a 3rd-party open source
> > automatic backup program.
> >
> > Could updating to Pacific fix this issue? Is there any configuration
> > change I could do to speed up object deletion?
> >
> --
> Jean-Philippe Méthot
> Senior Openstack system administrator
> Administrateur système Openstack sénior
> PlanetHoster inc.
>
> ___
> ceph-users mailing list -- ceph-users@ceph.io
> To unsubscribe send an email to ceph-users-le...@ceph.io
>
___
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to ceph-users-le...@ceph.io

[RBW] Re: Stubby Front Derailleur with a triple crank?

[Wesley]

The product photos show it on a triple, but I have no first-hand experience 
with it.
-W

On Wednesday, June 1, 2022 at 12:19:54 PM UTC-7 Rod Holland wrote:

> I'm wondering if the Stubby Skeleton Key front derailleur offered by Riv 
> will work with triple cranks and shifters? 3x9, hopefully. 3x10? If it will 
> work with a triple, any guidelines for success-prone configurations?
>
> This isn't directly addressed in the product copy on the Riv site, except 
> "This will work with all Silver cranks."
>
> rod
>

-- 
You received this message because you are subscribed to the Google Groups "RBW 
Owners Bunch" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rbw-owners-bunch+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/rbw-owners-bunch/107cf6f7-ddcf-4988-91c3-adbd38f054dfn%40googlegroups.com.

Re: [RBW] Re: Clem Smith Jr Update

[Wesley]

Use blue Loctite.

On Tuesday, May 31, 2022 at 9:30:54 AM UTC-7 J J wrote:

> Thanks for the recommendations, all. Which loc tite variety do you suggest 
> for the shifters?
>
> @Mackenzy, I’ve experienced the same slippage with a NOS Rapid Rise RD and 
> a modern, new high normal RD. In both cases it was with the same new 
> shifter cables, liners, and housing, and new chainrings, cassette, and 
> chain. I’m looking forward to trying loc tite. 
>
> On Tuesday, May 31, 2022 at 11:58:55 AM UTC-4 Doug H. wrote:
>
>> This is good info. I don’t mind needing to use loc-tite because the 
>> shifter is smooth and looks good. But, maybe Riv should make this a 
>> recommendation or pre install it on the bolt. I’ll try it and report back. 
>> Doug
>>
>> Sent from my iPhone
>>
>> On May 31, 2022, at 11:24 AM, Mackenzy Albright  
>> wrote:
>>
>> I installed a suntour barcon on my clem build with an ALTUS rear dr. Not 
>> sure if it's a stronger modern spring but find it's slipping more than 
>> normal. I previously had it paired with an older generation XTR reverse 
>> rapid rise which worked fine. But I think the reverse rapid rise has less 
>> return tension. 
>>
>>
>>
>> On Tuesday, May 31, 2022 at 9:06:24 AM UTC-6 Kainalu V. -Brooklyn NY 
>> wrote:
>>
>>> Doug, you're likely already aware that there's different levels of 
>>> loc-tite, but just make sure you use the less permanent option on those 
>>> shifters of yours.
>>> Happy shifting!
>>> -Kai
>>>
>>> On Tuesday, May 31, 2022 at 9:38:46 AM UTC-4 Doug H. wrote:
>>>
 I was just looking at shifters on the Rivendell website and found this 
 blurb in the description of the wing bolts that can replace the d-ring 
 bolt 
 that comes with the Silver2 shifter... "*Put some loc-tite on them and 
 you'll likely never have to mess with them. If your shifter loses a little 
 tension, turn it at the next stop or even while you're riding, if you're 
 careful."  *So, I think I will try a little loc-tite on the bolt to 
 see if that helps with slippage.
 Doug 


 On Tuesday, May 31, 2022 at 9:08:03 AM UTC-4 rmro...@gmail.com wrote:

> Man, I grew up with friction shifters & have been yearning for the 
> Silver shifters to replace my Microshift units that came on the bike. But 
> these things work flawlessly & I’d forgotten about “slippage”. I think I 
> shall resist the nostalgic trip down memory lane and save $170.00!
>
> Sent from my iPhone
>
> On May 30, 2022, at 8:50 PM, J J  wrote:
>
> 
>
> Hi Doug, thanks for the nice write up. CeeCee looks great!
>
> About the Silver2 shifters: I’ve had the same problem of gears 
> slipping. I find that I have to tighten the D ring screw so much to 
> prevent 
> slipping that it makes it hard to move the shift levers. I haven’t 
> thought 
> of using thread lock. I’ve just kind of accepted the slipping as reality 
> for these shifters. It seems like I constantly have to fiddle with them. 
>
> I’d love to hear suggestions from anyone else who might be reading 
> this. I prefer friction shifting. But the slipping with these brand new 
> Silver2s has me considering index shifting for the first time. Grant says 
> these are the best shifters in the world. If these are the best….surely 
> they should not slip?? 
>
> On Monday, May 30, 2022 at 4:14:29 PM UTC-4 Doug H. wrote:
>
>> I now have several hundred miles on my Clem Smith Jr so wanted to 
>> share some thoughts. I feel like I'm cruising around when I ride so I 
>> call 
>> it my Clem Cruiser, or CeeCee for short. I've never named a bike but 
>> CeeCee 
>> may work. Is it fast or slow? Those aren't the right questions to 
>> ponder. 
>> Am I faster or slower on the Clem as compared to other bikes I've 
>> ridden? 
>> It doesn't feel like it and I don't care! I'm amazed at how it tracks up 
>> hills with ease. I sit upright and enjoy the scenery which gives me a 
>> greater degree of feeling safe as well.  I'm really happy with how the 
>> Clem 
>> rides on asphalt, dirt or gravel.
>>
>> I recently had Rich build a dynamo wheel for me as I had never used 
>> dynamo but wanted to give it a shot. I'm hooked. I don't feel any drag 
>> from 
>> the hub and not having to worry about recharging lights frees my mind 
>> for 
>> other thoughts. The wheel is a Velocity Cliffhanger 32 spokes with a 
>> Kasai 
>> hub. My rear wheel is still the stock Alex 36 spoke with an unbranded 
>> hub. 
>> The mismatched wheels are kinda cool and Clem-like I think. 
>>
>> My pedals are One Up aluminum platform pedals that are large and 
>> grippy. They are perfect for the Clem and my big ole feet. I rode today 
>> wearing my Merrell sandals and the pedals gave plenty of support and 
>> grip. 
>> Speaking of grip, I 

[casper] CASPERFPGA and the Great Merge

[Wesley New]

Good day all.

There are many forks of CASPERFPGA floating around the community and we are
embarking on an effort to merge them into the main repository, to create
one branch to rule them all.

If you have branches that you think should be included in this merge please
let me know and Ill add them to the list.

Thanks for all the continued development and collaboration.

Regards

Wesley New
SARAO

-- 
You received this message because you are subscribed to the Google Groups 
"casper@lists.berkeley.edu" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to casper+unsubscr...@lists.berkeley.edu.
To view this discussion on the web visit 
https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CAE2vkmXCF0ghORuMfU8JG%3DQC5rWBT4XhYomrbsEBUKeP6e9euw%40mail.gmail.com.

Re: [RBW] Re: Club Rides On A Racing Platypus

[Wesley]

In my opinion, take the Clem. Just because it is the more beautiful bike 
(again, IMO.) However, you may consider taking a tire or the entire rear 
wheel off of either one, and swapping it onto the racing Platy for a little 
while.
-W

On Monday, May 30, 2022 at 3:02:02 PM UTC-7 Bicycle Belle Ding Ding! wrote:

> 
> This thread has been so fun for me to write, but I keep thinking, what 
> really else is there to say? We have covered the bases by now; we wondered 
> if a Raspberry Platypus could become a Racing Platypus, considered the 
> controversy, battled insecurities, confronted our (my) own preconceived 
> ideas, learned some new things from the racers. It’s been an adventure for 
> me, and thank you! But today, wouldn’t you know, I’ve got another bit of 
> conversation for your consideration.
>
> Last week I realized my rear tire was dripping sealant. A myriad of tiny 
> pin-prick holes that I have never noticed revealed themselves as my Racing 
> Platypus hung, inert on the wall. The only reason I caught it was that my 
> poor Shopping Platypus below it was catching the dripping sealant. Below: 
> left, front tire, with its tread still decent. Right, the rear tire, wet 
> and holey and with very worn tread.
>
> [image: image0.jpeg]
>
> Turns out, the tire is toast. The rubber is thin enough that it is not 
> holding the sealant, and it is leaking through in minuscule holes and 
> tears. I never thought it would be worn out already - I’d never have 
> checked. I can’t tell you how many miles it took to make this happen 
> because I don’t track miles per bike - I just have a running total of 
> ridden miles. And between 2021-present, that number is…well, never mind, 
> because the calculator app crashed and I’m not totaling them up again. BUT, 
> the tires are only a year and a few month old! I got 5 years out of the 
> Betty Foy tires before I sat next to it one day and noticed this:
> [image: image2.jpeg]
>
> The bike shop had nothing as wide or even close as the 44 mm tires on the 
> Racing Platypus, and the Ultradynamico tires I ultimately settled on 
> haven’t yet shipped. I hope they’re good! I got the gray 42 mm Cava Race. 
>
> But what am I going to take to club rides this week? I can’t see taking 
> the Racing Platypus without new tires. The other contenders: A 2019 
> Rivendell Clem L and the 2020 Shopping Platypus. Both are heavy. Neither is 
> set up for speed. Good grief, look at these two:
>
> [image: image0.jpeg]
>
> [image: image3.jpeg]
>
> You are thinking, just strip the Shopping Plat and ride that. Ah, but the 
> lights are attached to the racks, so those stay and they are HEAVY. That 
> Platypus is the heaviest of my trio! I can strip bags, but how much does 
> that really help? The gearing is different on it; it is a 1x and the 
> gearing is not as “right” as my Racing Plat. I don’t have technical terms 
> for this - I can only say that the Rivendell drive train always gives me 
> the “right” gear - the Shopping Plat often feels too hard or too easy. I 
> don’t want to be fiddling around with that while chasing club riders. But 
> that isn’t even the deal-killer for me…
>
> It’s that basket. 
>
> Listen, I have weathered the silent prejudice as I wheeled the Racing 
> Platypus to the huddle. The Saddlesack and Billie Bars always invoke 
> judgment in this scenario, but a BASKET. I don’t think I can do it.
>
> That leaves the Clem. A bike that Grant, while extolling its virtues and 
> its versatility, said, “Just don’t take it on your club rides or anything.” 
> The Clem, with its ultra-high and proud Bosco Bars and its step-through, 
> beefy frame. I shudder to think of what they will think. I don’t even know 
> how fast I can ride it. I think maybe fast because it was my only bike 
> during 2020 and I rode it hard. But, it is unproven at club rides and I’ve 
> got hesitation.
>
> I don’t know which bike to take for certain, but you are free to send your 
> advice and/or regards.
> Leah
>
> On May 27, 2022, at 10:56 AM, Joe T  wrote:
>
> 
>
>
> Another great story by Leah! From Vegas to Michigan life. Beautiful 
> Michigan, enjoy!
> On Thursday, April 7, 2022 at 10:25:24 AM UTC-5 Bicycle Belle Ding Ding! 
> wrote:
>
>> Kevin,
>>
>> Their slow group was slow. I was glad to be in the faster class on the 
>> women’s ride. I kept pace, rode in 2nd and 3rd position, and it wasn’t 
>> effortless. I don’t think I will fall victim to the Lycra; I’m perfectly 
>> happy with the workout wear I find at Target - highly recommend their All 
>> In Motion brand, for anyone looking. 
>>
>> As far as fitness, don’t give up. You can still be fit on a clunker!
>>
>> I want to preserve my abilities and keep preventable disease at bay, so I 
>> take fitness pretty seriously. Group rides will really challenge me and 
>> probably increase my abilities. With my heavier bike and non-aero gear, I 
>> am probably gleaning better results than the rest of the group. I also lift 
>> weights, run and do 

[RBW] Re: My '99 Franklin Custom

[Wesley]

Re: "old time bikes" - I was recently struck by how recently bicycles of 
any kind first existed, when I learned that Jonathan the tortoise lives on 
Saint Helena in the South Atlantic and was at least 40 years old when the 
penny-farthing bicycle was 
invented! https://en.wikipedia.org/wiki/Jonathan_(tortoise)

On Friday, May 27, 2022 at 3:33:42 PM UTC-7 Garth wrote:

> Yes Craig and Rich !  "Old time bikes!"  laughing heartily !    I 
> use the term "time" rather loosely here as I figure a working bike and 
> parts at-hand and all are timeless. Their backstory, as interesting as it 
> may or may not be, has no bearing on the present use and working of it, you 
> know ? I mean ... here it is, let's ride and play bike  ! 
>
> I do love freewheels Rich !  Love love love ! Love the feel, the sound, 
> the look, the simple function, everything about them. I still have all my 
> Suntours I ever rode and have 3 more new Sachs 13-32 7-speeds on hand. They 
> sound great !  Besides 2 sets of Phil FW hubs I have 2 sets of Specialized 
> FW hubs too. While those are 126mm I could apply them to 135mm spacing by 
> using a solid axle. I did that on my Stumpie so I could use a slightly 
> larger/wider freewheel.
>
> I saw a video the other day about Sean Kelley reuniting with his 
> bonded/lugged/made-to-measure aluminum and carbon fiber Vitus racing bikes 
> from the 80's. He and the host were marveling over the "manual" nature of 
> the shifting, and the lovely sound of the freewheel. "How did you ride such 
> a bike Sean ?" "It's what we had and it was the best at that time" replied 
> Sean. 
>
> I haven't seen a Condor a long time Craig ! Isn't it amazing how an "old 
> time bike" can be so all-around useful for so may conditions ? They were 
> all-around before anyone even applied the phrase to a bicycle. What's great 
> is always great, forever and ever ! 
>
> My Franklin here was called a Bradley model and yes it Rich, it was the 
> "basic" custom option. I didn't know there was any other options at the 
> time though, nor would I know what to opt for even if I could. I mainly 
> wanted a bike with 18" chainstays and much longer TT, reach and 
> front-center than any production model. I got that, but wasn't aware that 
> to use fenders on that model I'd have to use 28mm tires. I was using 30 or 
> 32's I think. I had the width, but not the height. No regrets though, as 
> honestly I like seeing the tires bare from above and hear the changes in 
> sounds of the tires from various road surfaces. I've ridden it in the rain 
> more than my fendered Bomba and while the fenders do keep some junk off the 
> frame and headset, I can't say I've ever experienced anything adverse not 
> having them. Growing up in Minnesota nobody had fenders, at least in my 
> small city. In the Twin Cities people may have. I tried some fenders on my 
> '83 Stumpjumper with some smaller knobbies in '89 for commuting but the 
> fenders fit and rode poorly, Zefal I think. I took them off, for ever and 
> ever !
>
> Speaking of which that's where I got the uncommon Shimano "Sport LX" rear 
> derailleur from, my Stumpie. The Mountech it came with was 
> "Mission-Impossible-like" self-exploding. so this is what the shop had 
> at hand. It works just fine, shifts a 32 with ease ! I had an XC Pro on 
> there originally but in attempting to quell a squeaking "sealed" pulley it 
> didn't go back together right and is draggy despite many fiddles, the 
> pulley that is. Frankly those "sealed" pulleys are for the birds ! The 
> Suntour Power Thumb Shifters were also taken from the Stumpie. I have a NOS 
> pair on hand also that I bought from Kraynick's in Pittsburgh for a song. 
> Same with an extra set of the NOS Suntour XC Pro cantis, they were in a 
> parts bin all loose so I assembled them right there and he was happy to 
> sell them ! That's where the Suntour Power rings are from too, all 
> chainrings were $10. He had a bunch of Suntour freewheels but none in sizes 
> I wanted, they were all $20 I think. I haven't been there in a decade ... I 
> wonder what's still in there ?  Upstairs was a treasure trove of 
> various odd parts. Sift through at your own pace, bring a flashlight and 
> some gloves ! I love all that "old" bike stuff ! Not old, fresh as a daisy !
>
> Talk about a practicable bike shop !  He even had a diy repair shop in the 
> back with any tool you'd need. The whole bike shop was help yourself, roam 
> freely. If you needed help, Jerry could point you in the right direction. 
> It's a cyclists Wonderland really.
>
>  
>  
>

-- 
You received this message because you are subscribed to the Google Groups "RBW 
Owners Bunch" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rbw-owners-bunch+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/rbw-owners-bunch/7b0d095c-7b01-4ed2-a71d-4ad532897a39n%40googlegroups.com.

Re: [RBW] Hillibikes are so close!

[Wesley]

Yes, the seat post. Still, I wonder: how did they do it?

On Thursday, May 26, 2022 at 9:58:57 PM UTC-7 Erik wrote:

> Just the seat post, not the seat tube.  
>
> On Wednesday, May 25, 2022 at 10:45:50 AM UTC-7 Wesley wrote:
>
>> This is the first I'm hearing that you can have tubes knurled on the 
>> aftermarket... how did they do it?
>>
>> On Tuesday, May 24, 2022 at 8:16:15 AM UTC-7 Erik wrote:
>>
>>> Knurling the seat post at the collar and about three inches down the 
>>> insertion into the seat tube.  Worked like a charm.  I've had this done on 
>>> a bike before when I was having a problem with slipping.  
>>>
>>> On Tuesday, May 24, 2022 at 5:31:59 AM UTC-7 Eric Daume wrote:
>>>
>>>> What was the fix for the slipping seat post?
>>>>
>>>>
>>>>>

-- 
You received this message because you are subscribed to the Google Groups "RBW 
Owners Bunch" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rbw-owners-bunch+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/rbw-owners-bunch/b21fe07f-4927-4d6d-921e-2b868283ebd5n%40googlegroups.com.

[ceph-users] Re: Cluster healthy, but 16.2.7 osd daemon upgrade says its unsafe to stop them?

[Wesley Dillingham]

pool 13 'mathfs_metadata' replicated size 2 min_size 2 crush_rule 0
object_hash rjenkins pg_num 32 pgp_num 32 autoscale_mode on last_change

The problem is you have size=2 and min_size=2 on this pool. I would
increase the size of this pool to 3 (but i would also do that to all of
your pools which are size=2) the ok-to-stop command is failing because you
would drop below min_size by stopping any osd service this pg and those pgs
would then be inactive.

Respectfully,

*Wes Dillingham*
w...@wesdillingham.com
LinkedIn <http://www.linkedin.com/in/wesleydillingham>


On Thu, May 26, 2022 at 2:22 PM Sarunas Burdulis 
wrote:

> On 5/26/22 14:09, Wesley Dillingham wrote:
> > What does "ceph osd pool ls detail" say?
>
> $ ceph osd pool ls detail
> pool 0 'rbd' replicated size 2 min_size 1 crush_rule 0 object_hash
> rjenkins pg_num 64 pgp_num 64 autoscale_mode on last_change 44740 flags
> hashpspool,selfmanaged_snaps stripe_width 0 application rbd
> pool 1 '.rgw.root' replicated size 2 min_size 1 crush_rule 0 object_hash
> rjenkins pg_num 32 pgp_num 32 autoscale_mode on last_change 44740 lfor
> 0/0/31483 owner 18446744073709551615 flags hashpspool stripe_width 0
> application rgw
> pool 2 'default.rgw.control' replicated size 2 min_size 1 crush_rule 0
> object_hash rjenkins pg_num 32 pgp_num 32 autoscale_mode on last_change
> 44740 lfor 0/0/31469 owner 18446744073709551615 flags hashpspool
> stripe_width 0 application rgw
> pool 3 'default.rgw.data.root' replicated size 2 min_size 1 crush_rule 0
> object_hash rjenkins pg_num 32 pgp_num 32 autoscale_mode on last_change
> 44740 lfor 0/0/31471 owner 18446744073709551615 flags hashpspool
> stripe_width 0 application rgw
> pool 4 'default.rgw.gc' replicated size 2 min_size 1 crush_rule 0
> object_hash rjenkins pg_num 32 pgp_num 32 autoscale_mode on last_change
> 44740 lfor 0/0/31471 owner 18446744073709551615 flags hashpspool
> stripe_width 0 application rgw
> pool 5 'default.rgw.log' replicated size 2 min_size 1 crush_rule 0
> object_hash rjenkins pg_num 32 pgp_num 32 autoscale_mode on last_change
> 44740 lfor 0/0/31387 owner 18446744073709551615 flags hashpspool
> stripe_width 0 application rgw
> pool 6 'default.rgw.users.uid' replicated size 2 min_size 1 crush_rule 0
> object_hash rjenkins pg_num 32 pgp_num 32 autoscale_mode on last_change
> 44740 lfor 0/0/31387 flags hashpspool stripe_width 0 application rgw
> pool 12 'mathfs_data' replicated size 2 min_size 1 crush_rule 0
> object_hash rjenkins pg_num 32 pgp_num 32 autoscale_mode on last_change
> 44740 lfor 0/31370/31368 flags hashpspool stripe_width 0 application cephfs
> pool 13 'mathfs_metadata' replicated size 2 min_size 2 crush_rule 0
> object_hash rjenkins pg_num 32 pgp_num 32 autoscale_mode on last_change
> 44740 lfor 0/27164/27162 flags hashpspool stripe_width 0 application cephfs
> pool 15 'default.rgw.lc' replicated size 2 min_size 1 crush_rule 0
> object_hash rjenkins pg_num 32 pgp_num 32 autoscale_mode on last_change
> 44740 lfor 0/0/31374 flags hashpspool stripe_width 0 application rgw
> pool 21 'libvirt' replicated size 3 min_size 1 crush_rule 0 object_hash
> rjenkins pg_num 32 pgp_num 32 autoscale_mode on last_change 56244 lfor
> 0/33144/33142 flags hashpspool,selfmanaged_snaps stripe_width 0
> application rbd
> pool 36 'monthly_archive_metadata' replicated size 2 min_size 1
> crush_rule 0 object_hash rjenkins pg_num 32 pgp_num 32 autoscale_mode on
> last_change 45338 lfor 0/27845/27843 flags hashpspool stripe_width 0
> application cephfs
> pool 37 'monthly_archive_data' replicated size 2 min_size 1 crush_rule 0
> object_hash rjenkins pg_num 32 pgp_num 32 autoscale_mode on last_change
> 45334 lfor 0/44535/44533 flags hashpspool stripe_width 0 application cephfs
> pool 38 'device_health_metrics' replicated size 2 min_size 1 crush_rule
> 0 object_hash rjenkins pg_num 1 pgp_num 1 autoscale_mode on last_change
> 56507 flags hashpspool stripe_width 0 pg_num_min 1 application
> mgr_devicehealth
> pool 41 'lensfun_metadata' replicated size 2 min_size 1 crush_rule 0
> object_hash rjenkins pg_num 32 pgp_num 32 autoscale_mode on last_change
> 54066 flags hashpspool stripe_width 0 pg_autoscale_bias 4 pg_num_min 16
> recovery_priority 5 application cephfs
> pool 42 'lensfun_data' replicated size 2 min_size 1 crush_rule 0
> object_hash rjenkins pg_num 32 pgp_num 32 autoscale_mode on last_change
> 54066 flags hashpspool stripe_width 0 application cephfs
>
>
> ___
> ceph-users mailing list -- ceph-users@ceph.io
> To unsubscribe send an email to ceph-users-le...@ceph.io
>
___
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to ceph-users-le...@ceph.io

[ceph-users] Re: Cluster healthy, but 16.2.7 osd daemon upgrade says its unsafe to stop them?

[Wesley Dillingham]

What does "ceph osd pool ls detail" say?

Respectfully,

*Wes Dillingham*
w...@wesdillingham.com
LinkedIn 


On Thu, May 26, 2022 at 11:24 AM Sarunas Burdulis <
saru...@math.dartmouth.edu> wrote:

> Running
>
> `ceph osd ok-to-stop 0`
>
> shows:
>
> {"ok_to_stop":false,"osds":[1],
> "num_ok_pgs":25,"num_not_ok_pgs":2,
> "bad_become_inactive":["13.a","13.11"],
>
> "ok_become_degraded":["0.4","0.b","0.11","0.1a","0.1e","0.3c","2.5","2.10","3.19","3.1a","4.7","4.19","4.1e","6.10","12.1","12.6","15.9","21.17","21.18","36.8","36.13","41.7","41.1b","42.6","42.1a"]}
> Error EBUSY: unsafe to stop osd(s) at this time (2 PGs are or would
> become offline)
>
> What are “bad_become_inactive” PGs?
> What can be done to make OSD into “ok-to-stop” (or override it)?
>
> `ceph -s` still reports HEALT_OK and all PGs active+clean.
>
> Upgrade to 16.2.8 still complains about non-stoppable OSDs and won't
> proceed.
>
> --
> Sarunas Burdulis
> Dartmouth Mathematics
> math.dartmouth.edu/~sarunas
>
> · https://useplaintext.email ·
> ___
> ceph-users mailing list -- ceph-users@ceph.io
> To unsubscribe send an email to ceph-users-le...@ceph.io
>
___
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to ceph-users-le...@ceph.io

[ceph-users] Re: Drained OSDs are still ACTIVE_PRIMARY - casuing high IO latency on clients

[Wesley Dillingham]

This sounds similar to an inquiry I submitted a couple years ago [1]
whereby I discovered that the choose_acting function does not consider
primary affinity when choosing the primary osd. I had made the assumption
it would when developing my procedure for replacing failing disks. After
that discovery I change my process to stop the OSD daemon failing (degraded
pgs) to ensure its not participating in PG anymore. Not sure if any of the
relevant code regarding this has changed since that initial submit but what
you describe here seems similar.

 [1] https://tracker.ceph.com/issues/44400

Respectfully,

*Wes Dillingham*
w...@wesdillingham.com
LinkedIn 


On Fri, May 20, 2022 at 7:53 AM Denis Polom  wrote:

> Hi
>
> I observed high latencies and mount points hanging since Octopus release
> and it's still observed on Pacific latest while draining OSD.
>
> Cluster setup:
>
> Ceph Pacific 16.2.7
>
> Cephfs with EC data pool
>
> EC profile setup:
>
> crush-device-class=
> crush-failure-domain=host
> crush-root=default
> jerasure-per-chunk-alignment=false
> k=10
> m=2
> plugin=jerasure
> technique=reed_sol_van
> w=8
>
> Description:
>
> If we have broken drive, we are removing it from Ceph cluster by
> draining it first. That means changing its crush weight to 0
>
> ceph osd crush reweight osd.1 0
>
> Normally on Nautilus it didn't affected clients. But after upgrade to
> Octopus (and since Octopus till current Pacific release) I can observe
> very high IO latencies on clients while OSD being drained (10sec and
> higher).
>
> By debugging I found out that drained OSD is still listed as
> ACTIVE_PRIMARY and that happens only on EC pools and only since Octopus.
> I tested it back on Nautilus, to be sure, where behavior is correct and
> drained OSD is not listed under UP and ACTIVE OSDs for PGs.
>
> Even if setting up primary-affinity for given OSD to 0 this doesn't have
> any effect on EC pool.
>
> Bellow are my debugs:
>
> Buggy behavior on Octopus and Pacific:
>
> Before draining osd.70:
>
> PG_STAT  OBJECTS  MISSING_ON_PRIMARY  DEGRADED  MISPLACED UNFOUND
> BYTES   OMAP_BYTES*  OMAP_KEYS*  LOG   DISK_LOG
> STATE  STATE_STAMP VERSION
> REPORTED   UP UP_PRIMARY  ACTING
> ACTING_PRIMARY LAST_SCRUB SCRUB_STAMP LAST_DEEP_SCRUB
> DEEP_SCRUB_STAMP SNAPTRIMQ_LEN
> 16.1fff 2269   0 0  0 0
> 89552977270   0  2449 2449
> active+clean 2022-05-19T08:41:55.241734+020019403690'275685
> 19407588:19607199[70,206,216,375,307,57]  70
> [70,206,216,375,307,57]  7019384365'275621
> 2022-05-19T08:41:55.241493+020019384365'275621
> 2022-05-19T08:41:55.241493+0200  0
> dumped pgs
>
>
> after setting osd.70 crush weight to 0 (osd.70 is still acting primary):
>
>   UP UP_PRIMARY ACTING
> ACTING_PRIMARY  LAST_SCRUB SCRUB_STAMP
> LAST_DEEP_SCRUB DEEP_SCRUB_STAMP SNAPTRIMQ_LEN
> 16.1fff 2269   0 0   2269 0
> 89552977270   0  2449  2449
> active+remapped+backfill_wait  2022-05-20T08:51:54.249071+0200
> 19403690'275685  19407668:19607289 [71,206,216,375,307,57]  71
> [70,206,216,375,307,57]  7019384365'275621
> 2022-05-19T08:41:55.241493+020019384365'275621
> 2022-05-19T08:41:55.241493+0200  0
> dumped pgs
>
>
> Correct behavior on Nautilus:
>
> Before draining osd.10:
>
> PG_STAT OBJECTS MISSING_ON_PRIMARY DEGRADED MISPLACED UNFOUND BYTES
> OMAP_BYTES* OMAP_KEYS* LOG DISK_LOG STATE STATE_STAMP
> VERSION REPORTED UP UP_PRIMARY ACTING ACTING_PRIMARY
> LAST_SCRUB SCRUB_STAMP LAST_DEEP_SCRUB DEEP_SCRUB_STAMP
> SNAPTRIMQ_LEN
> 2.4e  2  00 0   0
> 8388608   0  0   22 active+clean 2022-05-20
> 02:13:47.43210461'275:40   [10,0,7] 10   [10,0,7]
> 100'0 2022-05-20 01:44:36.217286 0'0 2022-05-20
> 01:44:36.217286 0
>
> after setting osd.10 crush weight to 0 (behavior is correct, osd.10 is
> not listed, not used):
>
>
> root@nautilus1:~# ceph pg dump pgs | head -2
> PG_STAT OBJECTS MISSING_ON_PRIMARY DEGRADED MISPLACED UNFOUND BYTES
> OMAP_BYTES* OMAP_KEYS* LOG DISK_LOG STATE
> STATE_STAMPVERSION REPORTED UP UP_PRIMARY
> ACTING ACTING_PRIMARY LAST_SCRUB SCRUB_STAMP
> LAST_DEEP_SCRUB DEEP_SCRUB_STAMP   SNAPTRIMQ_LEN
> 2.4e 14  00 0   0
> 58720256   0  0  18   18 active+clean 2022-05-20
> 02:18:59.414812   75'1880:43 [22,0,7] 22
> [22,0,7] 220'0 2022-05-20
> 01:44:36.217286 0'0 2022-05-20 01:44:36.217286 0
>
>
> Now question is if is it some implemented feature?
>
> Or is it a bug?
>
> Thank you!
>
> ___

[ceph-users] Re: Trouble getting cephadm to deploy iSCSI gateway

[Wesley Dillingham]

Well I dont use either the dashboard or the cephadm/containerized
deployment but do use ceph-iscsi. The fact that your two gateways are not
"up" might indicate that they havent been added to the target IQN yet. Once
you can get into gwcli and create an iqn and associate your gateways with
it, I guess they will report as "up"

On the filesystem ceph-iscsi uses /etc/ceph/iscsi-gateway.cfg to store
things lik the api password / trusted_ip_list etc. Maybe check this in the
container and see if it is being configured correctly.

Are you running gwcli on the server where the iscsi gateway is running? It
wants to connect to the rbd-target-api on port 5000 via localhost.

The error you reported "Unable to access the configuration object" also
sounds like a cephx inability to access the configuration rados object at
rbd/gateway.conf By default it would want to use the admin keyring unless
otherwise specified in the .cfg with the gateway_keyring option.

Hope that helps in some way.

Respectfully,

*Wes Dillingham*
w...@wesdillingham.com
LinkedIn 


On Tue, May 17, 2022 at 1:45 PM Erik Andersen  wrote:

> I am attempting to set up a 3 node Ceph cluster using Ubuntu server
> 22.04LTS, and the Cehpadm deployment tool.
>
> 3 times I've succeeded in setting up ceph itself, getting the cluster
> healthy, and OSDs all set up. The nodes (all monitors) are at
> 192.168.122.3, 192.168.122.4, and 192.168.122.5. All nodes have a second
> "backend" network on separate interface in the 10.0.0.3-10.0.0.5 range.
>
> I then create a RBD pool called "rbd".
>
> All is healthy with the cluster per the dashboard up to this point.
>
> I then try to set up iSCSI gateways on 192.168.122.3 and 192.168.122.5,
> following these directions:
> https://docs.ceph.com/en/pacific/cephadm/services/iscsi/
>
> That means doing `cephadm shell`, getting the `iscsi.yaml` file into the
> docker container (with echo since there seems to be no text editors
> available) and then running their recommended deployment command of `ceph
> orch apply -i iscsi.yaml`. The yaml file has in it:
>
>  service_type: iscsi
>  service_id: iscsi
>  placement:
>hosts:
>  - ceph1
>  - ceph3
>  spec:
>pool: rbd  # RADOS pool where ceph-iscsi config data is stored.
>trusted_ip_list:
> "192.168.122.3,192.168.122.5,10.0.0.3,10.0.0.5,192.168.122.4,10.0.0.4"
>
> I then get in the dashboard status page there there are 2 iSCSI gateways
> configured, but down.
> https://i.stack.imgur.com/wr619.png
>
> In services, it shows that the services are running:
>
> https://i.stack.imgur.com/PwSik.png
>
>
>   On the iSCSI gateways page it shows this:
>
> (Ceph dashboard iSCSI gateway page showing both gateways down)
> https://i.stack.imgur.com/Se2Mv.png
>
>
> Looking on one of the node's containers, it does look like cephadm
> started/deployed containers for this (apologies in advance for the horrible
> email formatting of a console table - look at the first two):
>
>  root@ceph1:~# docker ps
>  CONTAINER ID   IMAGE COMMAND
> CREATED STATUS PORTS NAMES
>  cefaf78b98ee   quay.ceph.io/ceph-ci/ceph
>  "/usr/bin/rbd-target…"   About an hour ago   Up About an hour
>  ceph-9f724dc4-d2de-11ec-b7be-8f11f39bf88a-iscsi-iscsi-ceph1-alnale
>  b405b321bd6a   quay.ceph.io/ceph-ci/ceph
>  "/usr/bin/tcmu-runner"   About an hour ago   Up About an hour
>  ceph-9f724dc4-d2de-11ec-b7be-8f11f39bf88a-iscsi-iscsi-ceph1-alnale-tcmu
>  a05af7ac9609   quay.io/prometheus/prometheus:v2.33.4
>  "/bin/prometheus --c…"   About an hour ago   Up About an hour
>  ceph-9f724dc4-d2de-11ec-b7be-8f11f39bf88a-prometheus-ceph1
>  4699606a7878   quay.io/prometheus/alertmanager:v0.23.0
>  "/bin/alertmanager -…"   About an hour ago   Up About an hour
>  ceph-9f724dc4-d2de-11ec-b7be-8f11f39bf88a-alertmanager-ceph1
>  103abafd0c19   quay.ceph.io/ceph-ci/ceph
>  "/usr/bin/ceph-osd -…"   About an hour ago   Up About an hour
>  ceph-9f724dc4-d2de-11ec-b7be-8f11f39bf88a-osd-2
>  adcad13a1dcb   quay.ceph.io/ceph-ci/ceph
>  "/usr/bin/ceph-osd -…"   About an hour ago   Up About an hour
>  ceph-9f724dc4-d2de-11ec-b7be-8f11f39bf88a-osd-0
>  9626b0794794   quay.io/ceph/ceph-grafana:8.3.5   "/bin/sh -c
> 'grafana…"   About an hour ago   Up About an hour
>  ceph-9f724dc4-d2de-11ec-b7be-8f11f39bf88a-grafana-ceph1
>  9a717edbf83f   quay.io/prometheus/node-exporter:v1.3.1
>  "/bin/node_exporter …"   About an hour ago   Up About an hour
>  ceph-9f724dc4-d2de-11ec-b7be-8f11f39bf88a-node-exporter-ceph1
>  c1c52d37baf1   quay.ceph.io/ceph-ci/ceph
>  "/usr/bin/ceph-crash…"   About an hour ago   Up About an hour
>  ceph-9f724dc4-d2de-11ec-b7be-8f11f39bf88a-crash-ceph1
>  f6b2c9fef7e9   quay.ceph.io/ceph-ci/ceph:master
> "/usr/bin/ceph-mgr -…"   About an hour ago   Up About an hour
>  

[ceph-users] Re: Migration Nautilus to Pacifi : Very high latencies (EC profile)

[Wesley Dillingham]

What was the largest cluster that you upgraded that didn't exhibit the new
issue in 16.2.8 ? Thanks.

Respectfully,

*Wes Dillingham*
w...@wesdillingham.com
LinkedIn 


On Tue, May 17, 2022 at 10:24 AM David Orman  wrote:

> We had an issue with our original fix in 45963 which was resolved in
> https://github.com/ceph/ceph/pull/46096. It includes the fix as well as
> handling for upgraded clusters. This is in the 16.2.8 release. I'm not sure
> if it will resolve your problem (or help mitigate it) but it would be worth
> trying.
>
> Head's up on 16.2.8 though, see the release thread, we ran into an issue
> with it on our larger clusters: https://tracker.ceph.com/issues/55687
>
> On Tue, May 17, 2022 at 3:44 AM BEAUDICHON Hubert (Acoss) <
> hubert.beaudic...@acoss.fr> wrote:
>
> > Hi Josh,
> >
> > I'm working with Stéphane and I'm the "ceph admin" (big words ^^) in our
> > team.
> > So, yes, as part of the upgrade we've done the offline repair to split
> the
> > omap by pool.
> > The quick fix is, as far as I know, still disable on the default
> > properties.
> >
> > On the I/O and CPU load, between Nautilus and Pacific, we haven't seen a
> > really big change, just an increase in disk latency and in the end, the
> > "ceph read operation" metric drop from 20K to 5K or less.
> >
> > But yes, a lot of slow IOPs were emerging as time passed.
> >
> > At this time, we have completely out one of our data node, and recreate
> > from scratch 5 of 8 OSD deamons (DB on SSD, data on spinning drive).
> > The result seems very good at this moment (we're seeing better metrics
> > than under Nautilus).
> >
> > Since recreation, I have change 3 parameters :
> > bdev_async_discard => osd : true
> > bdev_enable_discard => osd : true
> > bdev_aio_max_queue_depth => osd: 8192
> >
> > The first two have been extremely helpful for our SSD Pool, even with
> > enterprise grade SSD, the "trim" seems to have rejuvenate our pool.
> > The last one was set in response of messages in the newly create OSD :
> > "bdev(0x55588e220400 ) aio_submit retries XX"
> > After changing it and restarting the OSD process, messages were gone, and
> > it seems to have a beneficial effect on our data node.
> >
> > I've seen that the 16.2.8 was out yesterday, but I'm a little confused
> on :
> > [Revert] bluestore: set upper and lower bounds on rocksdb omap iterators
> > (pr#46092, Neha Ojha)
> > bluestore: set upper and lower bounds on rocksdb omap iterators
> (pr#45963,
> > Cory Snyder)
> >
> > (theses two lines seems related to https://tracker.ceph.com/issues/55324
> ).
> >
> > One step forward, one step backward ?
> >
> > Hubert Beaudichon
> >
> >
> > -Message d'origine-
> > De : Josh Baergen 
> > Envoyé : lundi 16 mai 2022 16:56
> > À : stéphane chalansonnet 
> > Cc : ceph-users@ceph.io
> > Objet : [ceph-users] Re: Migration Nautilus to Pacifi : Very high
> > latencies (EC profile)
> >
> > Hi Stéphane,
> >
> > On Sat, May 14, 2022 at 4:27 AM stéphane chalansonnet <
> schal...@gmail.com>
> > wrote:
> > > After a successful update from Nautilus to Pacific on Centos8.5, we
> > > observed some high latencies on our cluster.
> >
> > As a part of this upgrade, did you also migrate the OSDs to sharded
> > rocksdb column families? This would have been done by setting bluestore's
> > "quick fix on mount" setting to true or by issuing a "ceph-bluestore-tool
> > repair" offline, perhaps in response to a BLUESTORE_NO_PER_POOL_OMAP
> > warning post-upgrade.
> >
> > I ask because I'm wondering if you're hitting
> > https://tracker.ceph.com/issues/55324, for which there is a fix coming
> in
> > 16.2.8. If you inspect the nodes and disks involved in your EC pool, are
> > you seeing high read or write I/O? High CPU usage?
> >
> > Josh
> > ___
> > ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an
> > email to ceph-users-le...@ceph.io
> > ___
> > ceph-users mailing list -- ceph-users@ceph.io
> > To unsubscribe send an email to ceph-users-le...@ceph.io
> >
> ___
> ceph-users mailing list -- ceph-users@ceph.io
> To unsubscribe send an email to ceph-users-le...@ceph.io
>
___
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to ceph-users-le...@ceph.io

[ceph-users] Re: Migration Nautilus to Pacifi : Very high latencies (EC profile)

[Wesley Dillingham]

In our case it appears that file deletes have a very high impact on osd
operations. Not a significant delete either ~20T on a 1PB utilized
filesystem (large files as well).

We are trying to tune down cephfs delayed deletes via:
"mds_max_purge_ops": "512",
"mds_max_purge_ops_per_pg": "0.10",

with some success but still experimenting with how we can reduce the
throughput impact from osd slow ops.

Respectfully,

*Wes Dillingham*
w...@wesdillingham.com
LinkedIn <http://www.linkedin.com/in/wesleydillingham>


On Mon, May 16, 2022 at 9:49 AM Wesley Dillingham 
wrote:

> We have a newly-built pacific (16.2.7) cluster running 8+3 EC jerasure
> ~250 OSDS across 21 hosts which has significantly lower than expected IOPS.
> Only doing about 30 IOPS per spinning disk (with appropriately sized SSD
> bluestore db) around ~100 PGs per OSD. Have around 100 CephFS (ceph fuse
> 16.2.7) clients using the cluster. Cluster regularly reports slow ops from
> the OSDs but the vast majority, 90% plus of the OSDs, are only <50% IOPS
> utilized. Plenty of cpu/ram/network left on all cluster nodes. We have
> looked for hardware (disk/bond/network/mce) issues across the cluster with
> no findings / checked send-qs and received-q's across the cluster to try
> and narrow in on an individual failing component but nothing found there.
> Slow ops are also spread equally across the servers in the cluster. Does
> your cluster report any health warnings (slow ops etc) alongside your
> reduced performance?
>
> Respectfully,
>
> *Wes Dillingham*
> w...@wesdillingham.com
> LinkedIn <http://www.linkedin.com/in/wesleydillingham>
>
>
> On Mon, May 16, 2022 at 2:00 AM Martin Verges 
> wrote:
>
>> Hello,
>>
>> depending on your workload, drives and OSD allocation size, using the 3+2
>> can be way slower than the 4+2. Maybe give it a small benchmark and try if
>> you see a huge difference. We had some benchmarks with such and they
>> showed
>> quite ugly results in some tests. Best way to deploy EC in our findings is
>> in power of 2, like 2+x, 4+x, 8+x, 16+x. Especially when you deploy OSDs
>> before the Ceph allocation change patch, you might end up consuming way
>> more space if you don't use power of 2. With the 4k allocation size at
>> least this has been greatly improved for newer deployed OSDs.
>>
>> --
>> Martin Verges
>> Managing director
>>
>> Mobile: +49 174 9335695  | Chat: https://t.me/MartinVerges
>>
>> croit GmbH, Freseniusstr. 31h, 81247 Munich
>> CEO: Martin Verges - VAT-ID: DE310638492
>> Com. register: Amtsgericht Munich HRB 231263
>> Web: https://croit.io | YouTube: https://goo.gl/PGE1Bx
>>
>>
>> On Sun, 15 May 2022 at 20:30, stéphane chalansonnet 
>> wrote:
>>
>> > Hi,
>> >
>> > Thank you for your answer.
>> > this is not a good news if you also notice a performance decrease on
>> your
>> > side
>> > No, as far as we know, you cannot downgrade to Octopus.
>> > Going forward seems to be the only way, so Quincy .
>> > We have a a qualification cluster so we can try on it (but full virtual
>> > configuration)
>> >
>> >
>> > We are using 4+2 and 3+2 profile
>> > Are you also on the same profile on your Cluster ?
>> > Maybe replicated profile are not be impacted ?
>> >
>> > Actually, we are trying to recreate one by one the OSD.
>> > some parameters can be only set by this way .
>> > The first storage Node is almost rebuild, we will see if the latencies
>> on
>> > it are below the others ...
>> >
>> > Wait and see .
>> >
>> > Le dim. 15 mai 2022 à 10:16, Martin Verges  a
>> > écrit :
>> >
>> >> Hello,
>> >>
>> >> what exact EC level do you use?
>> >>
>> >> I can confirm, that our internal data shows a performance drop when
>> using
>> >> pacific. So far Octopus is faster and better than pacific but I doubt
>> you
>> >> can roll back to it. We haven't rerun our benchmarks on Quincy yet, but
>> >> according to some presentation it should be faster than pacific. Maybe
>> try
>> >> to jump away from the pacific release into the unknown!
>> >>
>> >> --
>> >> Martin Verges
>> >> Managing director
>> >>
>> >> Mobile: +49 174 9335695  | Chat: https://t.me/MartinVerges
>> >>
>> >> croit GmbH, Freseniusstr. 31h, 81247 Munich
>> >> CEO: Martin Verges - VAT-ID: DE310638492

[ceph-users] Re: Migration Nautilus to Pacifi : Very high latencies (EC profile)

[Wesley Dillingham]

We have a newly-built pacific (16.2.7) cluster running 8+3 EC jerasure ~250
OSDS across 21 hosts which has significantly lower than expected IOPS. Only
doing about 30 IOPS per spinning disk (with appropriately sized SSD
bluestore db) around ~100 PGs per OSD. Have around 100 CephFS (ceph fuse
16.2.7) clients using the cluster. Cluster regularly reports slow ops from
the OSDs but the vast majority, 90% plus of the OSDs, are only <50% IOPS
utilized. Plenty of cpu/ram/network left on all cluster nodes. We have
looked for hardware (disk/bond/network/mce) issues across the cluster with
no findings / checked send-qs and received-q's across the cluster to try
and narrow in on an individual failing component but nothing found there.
Slow ops are also spread equally across the servers in the cluster. Does
your cluster report any health warnings (slow ops etc) alongside your
reduced performance?

Respectfully,

*Wes Dillingham*
w...@wesdillingham.com
LinkedIn 


On Mon, May 16, 2022 at 2:00 AM Martin Verges 
wrote:

> Hello,
>
> depending on your workload, drives and OSD allocation size, using the 3+2
> can be way slower than the 4+2. Maybe give it a small benchmark and try if
> you see a huge difference. We had some benchmarks with such and they showed
> quite ugly results in some tests. Best way to deploy EC in our findings is
> in power of 2, like 2+x, 4+x, 8+x, 16+x. Especially when you deploy OSDs
> before the Ceph allocation change patch, you might end up consuming way
> more space if you don't use power of 2. With the 4k allocation size at
> least this has been greatly improved for newer deployed OSDs.
>
> --
> Martin Verges
> Managing director
>
> Mobile: +49 174 9335695  | Chat: https://t.me/MartinVerges
>
> croit GmbH, Freseniusstr. 31h, 81247 Munich
> CEO: Martin Verges - VAT-ID: DE310638492
> Com. register: Amtsgericht Munich HRB 231263
> Web: https://croit.io | YouTube: https://goo.gl/PGE1Bx
>
>
> On Sun, 15 May 2022 at 20:30, stéphane chalansonnet 
> wrote:
>
> > Hi,
> >
> > Thank you for your answer.
> > this is not a good news if you also notice a performance decrease on your
> > side
> > No, as far as we know, you cannot downgrade to Octopus.
> > Going forward seems to be the only way, so Quincy .
> > We have a a qualification cluster so we can try on it (but full virtual
> > configuration)
> >
> >
> > We are using 4+2 and 3+2 profile
> > Are you also on the same profile on your Cluster ?
> > Maybe replicated profile are not be impacted ?
> >
> > Actually, we are trying to recreate one by one the OSD.
> > some parameters can be only set by this way .
> > The first storage Node is almost rebuild, we will see if the latencies on
> > it are below the others ...
> >
> > Wait and see .
> >
> > Le dim. 15 mai 2022 à 10:16, Martin Verges  a
> > écrit :
> >
> >> Hello,
> >>
> >> what exact EC level do you use?
> >>
> >> I can confirm, that our internal data shows a performance drop when
> using
> >> pacific. So far Octopus is faster and better than pacific but I doubt
> you
> >> can roll back to it. We haven't rerun our benchmarks on Quincy yet, but
> >> according to some presentation it should be faster than pacific. Maybe
> try
> >> to jump away from the pacific release into the unknown!
> >>
> >> --
> >> Martin Verges
> >> Managing director
> >>
> >> Mobile: +49 174 9335695  | Chat: https://t.me/MartinVerges
> >>
> >> croit GmbH, Freseniusstr. 31h, 81247 Munich
> >> CEO: Martin Verges - VAT-ID: DE310638492
> >> Com. register: Amtsgericht Munich HRB 231263
> >> Web: https://croit.io | YouTube: https://goo.gl/PGE1Bx
> >>
> >>
> >> On Sat, 14 May 2022 at 12:27, stéphane chalansonnet  >
> >> wrote:
> >>
> >>> Hello,
> >>>
> >>> After a successful update from Nautilus to Pacific on Centos8.5, we
> >>> observed some high latencies on our cluster.
> >>>
> >>> We did not find very much thing on community related to latencies post
> >>> migration
> >>>
> >>> Our setup is
> >>> 6x storage Node (256GRAM, 2SSD OSD + 5*6To SATA HDD)
> >>> Erasure coding profile
> >>> We have two EC pool :
> >>> -> Pool1 : Full HDD SAS Drive 6To
> >>> -> Pool2 : Full SSD Drive
> >>>
> >>> Object S3 and RBD block workload
> >>>
> >>> Our performances in nautilus, before the upgrade , are acceptable.
> >>> However , the next day , performance dropped by 3 or 4
> >>> Benchmark showed 15KIOPS on flash drive , before upgrade we had
> >>> almost 80KIOPS
> >>> Also, HDD pool is almost down (too much lantencies
> >>>
> >>> We suspected , maybe, an impact on erasure Coding configuration on
> >>> Pacific
> >>> Anyone observed the same behaviour ? any tuning ?
> >>>
> >>> Thank you for your help.
> >>>
> >>> ceph osd tree
> >>> ID   CLASS  WEIGHT TYPE NAME STATUS  REWEIGHT
> >>> PRI-AFF
> >>>  -1 347.61304  root default
> >>>  -3  56.71570  host cnp31tcephosd01
> >>>   0hdd5.63399  osd.0 up   1.0
> >>> 1.0
> >>>   1

Re: [cayugabirds-l] Red headed woodpecker

[Wesley M. Hochachka]

The only Blue Jay-like bird that I saw outside of the Lab of O yesterday, which 
was flashing a lot of white, was a Northern Mockingbird.

Wesley



From: bounce-126547525-3494...@list.cornell.edu 
 on behalf of Suan Hsi Yong 

Sent: Wednesday, May 11, 2022 19:27
To: CAYUGABIRDS-L 
Subject: Re: [cayugabirds-l] Red headed woodpecker

Yesterday while volunteering with 5th graders at the Lab of O, I saw a
bluejay-like bird but with all-white secondaries against an otherwise
dark wing. I didn't have binoculars on me and was soon distracted by
other stuff. But on further reflection, Red-headed Woodpecker is the
only bird I can think of with that wing pattern. (That and gadwall,
which this was not :-). I don't suppose anyone at the lab has seen
one.

Suan


On Wed, May 11, 2022 at 4:40 PM Regi Teasley  wrote:
>
> Just saw a Red-headed woodpecker at the suet.
> West Hill in the city.  Hard to believe.
> Regi
> 201 cliff Park Rd
>
> 
> “There is a brief and rapidly closing window to secure a liveable future on 
> the planet.” Hans-Otto Partner, co-chair, 2022 IPCC working group
>

--

Cayugabirds-L List Info:
http://www.NortheastBirding.com/CayugabirdsWELCOME
http://www.NortheastBirding.com/CayugabirdsRULES
http://www.NortheastBirding.com/CayugabirdsSubscribeConfigurationLeave.htm

ARCHIVES:
1) http://www.mail-archive.com/cayugabirds-l@cornell.edu/maillist.html
2) http://www.surfbirds.com/birdingmail/Group/Cayugabirds
3) http://birdingonthe.net/mailinglists/CAYU.html

Please submit your observations to eBird:
http://ebird.org/content/ebird/

--


--

Cayugabirds-L List Info:
http://www.NortheastBirding.com/CayugabirdsWELCOME
http://www.NortheastBirding.com/CayugabirdsRULES
http://www.NortheastBirding.com/CayugabirdsSubscribeConfigurationLeave.htm

ARCHIVES:
1) http://www.mail-archive.com/cayugabirds-l@cornell.edu/maillist.html
2) http://www.surfbirds.com/birdingmail/Group/Cayugabirds
3) http://birdingonthe.net/mailinglists/CAYU.html

Please submit your observations to eBird:
http://ebird.org/content/ebird/

--

[ceph-users] Re: Erasure-coded PG stuck in the failed_repair state

[Wesley Dillingham]

In my experience:

"No scrub information available for pg 11.2b5
error 2: (2) No such file or directory"

is the output you get from the command when the up or acting osd set has
changed since the last deep-scrub. Have you tried to run a deep scrub (ceph
pg deep-scrub 11.2b5) on the pg and then try "rados list-inconsistent-obj
11.2b5" again. I do recognize that part of the pg repair also performs a
deep-scrub but perhaps the deep-scrub alone will help with your attempt to
run rados list-inconsistent-obj.

Respectfully,

*Wes Dillingham*
w...@wesdillingham.com
LinkedIn 


On Tue, May 10, 2022 at 8:52 AM Robert Appleyard - STFC UKRI <
rob.appley...@stfc.ac.uk> wrote:

> Hi,
>
> We've got an outstanding issue with one of our Ceph clusters here at RAL.
> The cluster is 'Echo', our 40PB cluster. We found an object from an 8+3EC
> RGW pool in the failed_repair state. We aren't sure how the object got into
> this state, but it doesn't appear to be a case of correlated drive failure
> (the rest of the PG is fine). However, the detail of how we got into this
> state isn't our focus, it's how to get the PG back to a clean state.
>
> The object (for our purposes, named OBJNAME) in question is from a RadosGW
> data pool. It presented initially as a PG in the failed_repair state.
> Repeated attempts to get the PG to repair failed. At this point we
> contacted the user who owns the data, and determined that the data in
> question was also stored elsewhere and so we could safely delete the
> object. We did that using radosgw-admin object rm OBJNAME, and confirmed
> that the object is gone with various approaches (radosgw-admin object stat,
> rados ls --pgid PGID | grep OBJNAME).
>
> So far, so good. Except, even after the object was deleted and in spite of
> many instructions to repair, the placement group is still in the state
> active+clean+inconsistent+failed_repair, and the cluster won't go to
> HEALTH_OK. Here's what the log from one of these repair attempts looks like
> (from the log on the primary OSD).
>
> 2022-05-08 16:23:43.898 7f79d3872700  0 log_channel(cluster) log [DBG] :
> 11.2b5 repair starts
> 2022-05-08 16:51:38.807 7f79d3872700 -1 log_channel(cluster) log [ERR] :
> 11.2b5 shard 1899(8) soid 11:ad45a433:::OBJNAME:head : candidate had an ec
> size mismatch
> 2022-05-08 16:51:38.807 7f79d3872700 -1 log_channel(cluster) log [ERR] :
> 11.2b5 shard 1911(7) soid 11:ad45a433:::OBJNAME:head : candidate had an ec
> size mismatch
> 2022-05-08 16:51:38.807 7f79d3872700 -1 log_channel(cluster) log [ERR] :
> 11.2b5 shard 2842(10) soid 11:ad45a433:::OBJNAME:head : candidate had an ec
> size mismatch
> 2022-05-08 16:51:38.807 7f79d3872700 -1 log_channel(cluster) log [ERR] :
> 11.2b5 shard 3256(6) soid 11:ad45a433:::OBJNAME:head : candidate had an ec
> size mismatch
> 2022-05-08 16:51:38.807 7f79d3872700 -1 log_channel(cluster) log [ERR] :
> 11.2b5 shard 3399(5) soid 11:ad45a433:::OBJNAME:head : candidate had an ec
> size mismatch
> 2022-05-08 16:51:38.807 7f79d3872700 -1 log_channel(cluster) log [ERR] :
> 11.2b5 shard 3770(9) soid 11:ad45a433:::OBJNAME:head : candidate had an ec
> size mismatch
> 2022-05-08 16:51:38.807 7f79d3872700 -1 log_channel(cluster) log [ERR] :
> 11.2b5 shard 5206(3) soid 11:ad45a433:::OBJNAME:head : candidate had an ec
> size mismatch
> 2022-05-08 16:51:38.807 7f79d3872700 -1 log_channel(cluster) log [ERR] :
> 11.2b5 shard 6047(4) soid 11:ad45a433:::OBJNAME:head : candidate had an ec
> size mismatch
> 2022-05-08 16:51:38.807 7f79d3872700 -1 log_channel(cluster) log [ERR] :
> 11.2b5 soid 11:ad45a433:::OBJNAME:head : failed to pick suitable object info
> 2022-05-08 19:03:12.690 7f79d3872700 -1 log_channel(cluster) log [ERR] :
> 11.2b5 repair 11 errors, 0 fixed
>
> Looking for inconsistent objects in the PG doesn't report anything odd
> about this object (right now we get this rather odd output, but aren't sure
> that this isn't a red herring).
>
> [root@ceph-adm1 ~]# rados list-inconsistent-obj 11.2b5
> No scrub information available for pg 11.2b5
> error 2: (2) No such file or directory
>
> We don't get this output from this command on any other PG that we've
> tried.
>
> So what next? To reiterate, this isn't about data recovery, it's about
> getting the cluster back to a healthy state. I should also note that this
> issue doesn't seem to be impacting the cluster beyond making that PG show
> as being in a bad state.
>
> Rob Appleyard
>
>
> This email and any attachments are intended solely for the use of the
> named recipients. If you are not the intended recipient you must not use,
> disclose, copy or distribute this email or any of its attachments and
> should notify the sender immediately and delete this email from your
> system. UK Research and Innovation (UKRI) has taken every reasonable
> precaution to minimise risk of this email or any attachments containing
> viruses or malware but the recipient should carry out its own virus and
> malware 

[weewx-user] Garni Arcus 2055 and weewx

[Wesley Verbraecken]

Hello,

I have a Garni Arcus 2055 pws that is reporting to weathercloud and weather 
underground.
The station can also be configured for a personal weather server (URL, 
stationID and key can be provided)and I was trying to do this with weewx. 
I'm rather new to this and at the moment I'm unable to.

I have installed weewx in a test environment but I'm not sure how I need to 
configure it to accept updates over the network. I can't find a lot of 
information on weewx in combination with the arcus 2055 pws if it is even 
possible.

Anyone an tips on how to do this?
I tried using the interceptor driver listed in the wiki and sniff the 
network for wu updates, but at the moment without succes.

Thanks,
Wesley

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/5790a031-778e-47b0-9121-7fb68d3523a0n%40googlegroups.com.

[ceph-users] Aggressive Bluestore Compression Mode for client data only?

[Wesley Dillingham]

I would like to use bluestore compression (probably zstd level 3) to
compress my clients data unless the incompressible hint is set (aggressive
mode) but I do no want to expose myself to the bug experienced in this Cern
talk (Ceph bug of the year) https://www.youtube.com/watch?v=_4HUR00oCGo
where the osd maps are compressed, even though I realize the bug is fixed
in lz4 (and i'm probably not going to use lz4).

So my question is if the compression mode is aggressive but is set on a per
pool basis (compression_mode vs bluestore_compression_mode) is ceph only
attempting to compress the client data and not "bluestore/cluster internal
data" like osd maps etc. Thanks.


Respectfully,

*Wes Dillingham*
w...@wesdillingham.com
LinkedIn 
___
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to ceph-users-le...@ceph.io

[ceph-users] Re: Is it normal Ceph reports "Degraded data redundancy" in normal use?

[Wesley Dillingham]

If you mark an osd "out" but not down / you dont stop the daemon do the PGs
go remapped or do they go degraded then as well?

Respectfully,

*Wes Dillingham*
w...@wesdillingham.com
LinkedIn 


On Thu, Apr 14, 2022 at 5:15 AM Kai Stian Olstad 
wrote:

> On 29.03.2022 14:56, Sandor Zeestraten wrote:
> > I was wondering if you ever found out anything more about this issue.
>
> Unfortunately no, so I turned it off.
>
>
> > I am running into similar degradation issues while running rados bench
> > on a
> > new 16.2.6 cluster.
> > In our case it's with a replicated pool, but the degradation problems
> > also
> > go away when we turn off the balancer.
>
> So this goes a long way of confirming there are something wrong with the
> balancer since we now see it on two different installation.
>
>
> --
> Kai Stian Olstad
> ___
> ceph-users mailing list -- ceph-users@ceph.io
> To unsubscribe send an email to ceph-users-le...@ceph.io
>
___
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to ceph-users-le...@ceph.io

Bug#1009242: zfs-dkms: PPC get_user workaround breaks boot on ZFS root

[Nathaniel Wesley Filardo]

Package: zfs-dkms
Version: 2.1.2-1~bpo11+1
Severity: critical
Tags: patch
Justification: breaks the whole system
X-Debbugs-Cc: nwfila...@gmail.com

Dear Maintainer,

Presently (and since 16 Nov 2021), the Debian ZFS repo has been carrying Colin
Ian King's
https://salsa.debian.org/zfsonlinux-team/zfs/-/blob/master/debian/patches/4900-ppc-get-user-workaround.patch
to work around a build failure on PPC machines whose kernels post-date
7613f5a66becfd0e43a0f34de8518695888f5458 ("powerpc/64s/kuap: Use
mmu_has_feature()").  5.13 is the first release to contain that patch
(amusingly, someone noticed pretty quickly: https://lwn.net/Articles/856312/).

Unfortunately, while this does fix the compilation error, in a rather
heavy-handed way, it results in the system hanging at boot, well before reaching
the multi-user target.  The EFAULT returned to userspace simply triggers a
retry, and so we spin.  As I am on a Debian kernel after 5.13, I am unable to
upgrade my ZFS pacakges and keep a working system without rolling back to an
older kernel, which I cannot readily do, due to another bug in pre-5.15 PPC
kernel packages: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990279 .

I reached out to the original author of mmu_feature_keys, and he has agreed to
change the EXPORT_SYMBOL status of this symbol.  His one-line patch to do so,
https://patchwork.ozlabs.org/project/linuxppc-dev/patch/20220329085709.4132729-1-haoke...@gmail.com/
has yet to be picked up by
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/ , but, I
think, could be safely included in Debian's kernel patch set until it does.

Can I ask that the ZFS and linux package maintainers coordinate picking up Kevin
Hao's patch into the kernel package and dropping Colin Ian King's workaround
from the ZFS package?

I do not know if I should also raise a bug against the linux package; please
advise.

-- System Information:
Debian Release: 11.3
  APT prefers stable-updates
  APT policy: (991, 'stable-updates'), (990, 'stable'), (500, 
'unstable-debug'), (500, 'stable-security'), (500, 'stable-debug'), (500, 
'proposed-updates-debug'), (300, 'unstable')
Architecture: ppc64el (ppc64le)

Kernel: Linux 5.15.0-0.bpo.2-powerpc64le (SMP w/176 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages zfs-dkms depends on:
ii  debconf [debconf-2.0]  1.5.77
ii  dkms   2.8.4-3
ii  file   1:5.39-3
ii  libc6-dev [libc-dev]   2.31-13+deb11u3
ii  libpython3-stdlib  3.9.2-3
ii  lsb-release11.1.0
ii  perl   5.32.1-4+deb11u2
ii  python3-distutils  3.9.2-1

Versions of packages zfs-dkms recommends:
ii  linux-libc-dev  5.16.12-1~bpo11+1
ii  zfs-zed 2.1.2-1~bpo11+1
ii  zfsutils-linux  2.1.2-1~bpo11+1

Versions of packages zfs-dkms suggests:
ii  debhelper  13.3.4

-- debconf information:
  zfs-dkms/stop-build-for-unknown-kernel: true
* zfs-dkms/note-incompatible-licenses:
  zfs-dkms/stop-build-for-32bit-kernel: true

Bug#1009242: zfs-dkms: PPC get_user workaround breaks boot on ZFS root

[Nathaniel Wesley Filardo]

Package: zfs-dkms
Version: 2.1.2-1~bpo11+1
Severity: critical
Tags: patch
Justification: breaks the whole system
X-Debbugs-Cc: nwfila...@gmail.com

Dear Maintainer,

Presently (and since 16 Nov 2021), the Debian ZFS repo has been carrying Colin
Ian King's
https://salsa.debian.org/zfsonlinux-team/zfs/-/blob/master/debian/patches/4900-ppc-get-user-workaround.patch
to work around a build failure on PPC machines whose kernels post-date
7613f5a66becfd0e43a0f34de8518695888f5458 ("powerpc/64s/kuap: Use
mmu_has_feature()").  5.13 is the first release to contain that patch
(amusingly, someone noticed pretty quickly: https://lwn.net/Articles/856312/).

Unfortunately, while this does fix the compilation error, in a rather
heavy-handed way, it results in the system hanging at boot, well before reaching
the multi-user target.  The EFAULT returned to userspace simply triggers a
retry, and so we spin.  As I am on a Debian kernel after 5.13, I am unable to
upgrade my ZFS pacakges and keep a working system without rolling back to an
older kernel, which I cannot readily do, due to another bug in pre-5.15 PPC
kernel packages: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990279 .

I reached out to the original author of mmu_feature_keys, and he has agreed to
change the EXPORT_SYMBOL status of this symbol.  His one-line patch to do so,
https://patchwork.ozlabs.org/project/linuxppc-dev/patch/20220329085709.4132729-1-haoke...@gmail.com/
has yet to be picked up by
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/ , but, I
think, could be safely included in Debian's kernel patch set until it does.

Can I ask that the ZFS and linux package maintainers coordinate picking up Kevin
Hao's patch into the kernel package and dropping Colin Ian King's workaround
from the ZFS package?

I do not know if I should also raise a bug against the linux package; please
advise.

-- System Information:
Debian Release: 11.3
  APT prefers stable-updates
  APT policy: (991, 'stable-updates'), (990, 'stable'), (500, 
'unstable-debug'), (500, 'stable-security'), (500, 'stable-debug'), (500, 
'proposed-updates-debug'), (300, 'unstable')
Architecture: ppc64el (ppc64le)

Kernel: Linux 5.15.0-0.bpo.2-powerpc64le (SMP w/176 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages zfs-dkms depends on:
ii  debconf [debconf-2.0]  1.5.77
ii  dkms   2.8.4-3
ii  file   1:5.39-3
ii  libc6-dev [libc-dev]   2.31-13+deb11u3
ii  libpython3-stdlib  3.9.2-3
ii  lsb-release11.1.0
ii  perl   5.32.1-4+deb11u2
ii  python3-distutils  3.9.2-1

Versions of packages zfs-dkms recommends:
ii  linux-libc-dev  5.16.12-1~bpo11+1
ii  zfs-zed 2.1.2-1~bpo11+1
ii  zfsutils-linux  2.1.2-1~bpo11+1

Versions of packages zfs-dkms suggests:
ii  debhelper  13.3.4

-- debconf information:
  zfs-dkms/stop-build-for-unknown-kernel: true
* zfs-dkms/note-incompatible-licenses:
  zfs-dkms/stop-build-for-32bit-kernel: true

Re: [RE-wrenches] Water Pumping 24/7

[Wesley Kennedy via RE-wrenches]

Hi Darryl,
I’d love to see that math on that.you mind sharing? 

-Wes
303-653-3073


> On Mar 27, 2022, at 1:27 PM, Darryl Thayer via RE-wrenches 
>  wrote:
> 
> 
> Hello, Sorry to be so late but I have been overloaded.  Just a note on 
> physics of lifting water.  The calculation indicates if you pump 1 gallon per 
> minute up 300 feet it required a water hp of 5 HP  
> Use this base number and good pumps are about 70% efficient.  If the flow 
> rate is not 1 GPM adjust the HP accordingly.  For example, if you want to 
> pump 10 GPM it requires 50 HP  or if you want to pump 10 Gallons / day it 
> requires (50HP/ 24h 60min )requiring 0,035 HP..   
> Again I apologize for delay.   
> 
>> On Wed, Mar 16, 2022 at 1:33 AM William Miller  
>> wrote:
>> Hilton:
>> 
>> A valid point.  However in this region wells often do not recharge as well
>> as we might like.  In these cases, to meet gallons per day you have to pump
>> long and slow--more hours per day than the sun will be up.  That means of
>> course generator or battery storage.
>> 
>> The economics have shifted from when I started installing direct-DC water
>> pumping.  The money that is being spent today to provide commercial ag water
>> is beyond what I would have comprehended back then.  This means new
>> technology--and questions need to be asked, including considering battery
>> storage.
>> 
>> Thanks for your reply.
>> 
>> William
>> 
>> Miller Solar
>> 17395 Oak Road, Atascadero, CA 93422
>> 805-438-5600
>> www.millersolar.com
>> CA Lic. 773985
>> 
>> 
>> 
>> -Original Message-
>> From: RE-wrenches [mailto:re-wrenches-boun...@lists.re-wrenches.org] On
>> Behalf Of Hilton Dier
>> Sent: Tuesday, March 15, 2022 6:56 PM
>> To: RE-wrenches@lists.re-wrenches.org
>> Subject: [RE-wrenches] Water Pumping 24/7
>> 
>> Here’s a lateral take on this. A 500 gallon poly water tank is far cheaper
>> than the batteries needed to fill it.
>> 
>> Years ago I rigged up a seasonal pump system for a man who had two ponds on
>> his property. The lower one was well fed by a spring but the upper one 
>> wasn’t.
>> I used a 200 watt DC piston pump and a couple of modules with a linear
>> current booster. A couple of breakers but no batteries. It just chugged away
>> quietly all (moderately sunny) day, filling the upper pond.
>> 
>> Using a positive displacement pump is key for minimizing power requirements.
>> At 300 feet that’s about 125 psi, which is not out of line for a piston
>> pump. Fill a big poly tank and pressurize it with a small DC diaphragm pump
>> if necessary.
>> 
>> Simple, efficient, cheap.
>> 
>> Hilton Dier III
>> Renewable Energy Design
>> Missisquoi River Hydro LLC
>> ___
>> List sponsored by Redwood Alliance
>> 
>> Pay optional member dues here: http://re-wrenches.org
>> 
>> List Address: RE-wrenches@lists.re-wrenches.org
>> 
>> Change listserver email address & settings:
>> http://lists.re-wrenches.org/options.cgi/re-wrenches-re-wrenches.org
>> 
>> There are two list archives for searching. When one doesn't work, try the
>> other:
>> https://www.mail-archive.com/re-wrenches@lists.re-wrenches.org/
>> http://lists.re-wrenches.org/pipermail/re-wrenches-re-wrenches.org
>> 
>> List rules & etiquette:
>> http://www.re-wrenches.org/etiquette.htm
>> 
>> Check out or update participant bios:
>> http://www.members.re-wrenches.org
>> ___
>> List sponsored by Redwood Alliance
>> 
>> Pay optional member dues here: http://re-wrenches.org
>> 
>> List Address: RE-wrenches@lists.re-wrenches.org
>> 
>> Change listserver email address & settings:
>> http://lists.re-wrenches.org/options.cgi/re-wrenches-re-wrenches.org
>> 
>> There are two list archives for searching. When one doesn't work, try the 
>> other:
>> https://www.mail-archive.com/re-wrenches@lists.re-wrenches.org/
>> http://lists.re-wrenches.org/pipermail/re-wrenches-re-wrenches.org
>> 
>> List rules & etiquette:
>> http://www.re-wrenches.org/etiquette.htm
>> 
>> Check out or update participant bios:
>> http://www.members.re-wrenches.org
>> 
> ___
> List sponsored by Redwood Alliance
> 
> Pay optional member dues here: http://re-wrenches.org
> 
> List Address: RE-wrenches@lists.re-wrenches.org
> 
> Change listserver email address & settings:
> http://lists.re-wrenches.org/options.cgi/re-wrenches-re-wrenches.org
> 
> There are two list archives for searching. When one doesn't work, try the 
> other:
> https://www.mail-archive.com/re-wrenches@lists.re-wrenches.org/
> http://lists.re-wrenches.org/pipermail/re-wrenches-re-wrenches.org
> 
> List rules & etiquette:
> http://www.re-wrenches.org/etiquette.htm
> 
> Check out or update participant bios:
> http://www.members.re-wrenches.org
> 
___
List sponsored by Redwood Alliance

Pay optional member dues here: http://re-wrenches.org

List Address: RE-wrenches@lists.re-wrenches.org

[google-appengine] Curious about Cloud Functions or Cloud Run?

[wesley chun]

I know we have lots of App Engine users here (duh), but if you were curious
about our other pair of serverless products (Cloud Functions
<http://cloud.google.com/functions> and Cloud Run <http://cloud.run/>), I'm
giving a real short (~20-min) high-level serverless
<http://cloud.google.com/serverless> overview at GDG Cloud Indy this Fri 9a
PDT/12n EDT/4p GMT. Online & free; register at Meetup
<http://meetup.com/GDGCloudIndy/events/284431016>; more info on LinkedIn
<http://linkedin.com/feed/update/urn:li:share:6908565837956145152> or the event
website <https://gdg.community.dev/e/m8azyv>.

Cheers,
--Wesley
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
"A computer never does what you want... only what you tell it."
wesley chun :: @wescpy <http://twitter.com/wescpy> :: Software
Architect & Engineer
Developer Advocate at Google
<https://cloud.google.com/developers/advocates/wesley-chun/> by day; at
night: Core Python <http://amzn.com/dp/0132269937>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CAB6eaA4KTrvkWMLgEpeywFR-roP1a_VWFXT8miDS3fvN%3DLxiPg%40mail.gmail.com.

Bug#959469:

[Wesley Redondo]

I would like to stop receiving these emails

Bug#959469:

[Wesley Redondo]

I would like to stop receiving these emails

Bug#959469: openssl 1.1.1n-0+deb10u1 flagged for acceptance

[Wesley Redondo]

How do I stop these emails

On Mon, Mar 21, 2022, 3:27 PM Adam D. Barratt 
wrote:

> On Sun, 2022-03-20 at 22:00 +0100, Paul Gevers wrote:
> > Dear Sebastian, Kurt,
> >
> > On 19-03-2022 12:33, Adam D Barratt wrote:
> > > Upload details
> > > ==
> > >
> > > Package: openssl
> > > Version: 1.1.1n-0+deb10u1
> > >
> > > Explanation: new upstream release
> >
> > We're seeing a regression in buster in the autopkgtest of gnutls28
> > with
> > the new version of openssl on all tested architectures. Can you
> > please
> > have a look and advise? (bullseye doesn't seem to have the test
> > anymore,
> > hence it doesn't fail).
>
> Thanks to both Kurt and Sebastian for quickly identifying the issue
> here, and to Adrian Bunk for the libnet-ssleay-perl fix.
>
> There's been some continued discussion today as to whether we feel
> comfortable releasing the update with the 10.12 point release when we
> have only been finding such issues during the week leading up to the
> point release.
>
> I fully appreciate that the large delays in getting to this point were
> mostly on our part, and that postponing the release until 10.13 would
> likely be frustrating, but the worry is that we don't have a good view
> of the changes that might be user-affecting in order to be comfortable
> with potential behaviour changes landing in oldstable - for example,
> the libnet-ssleay-perl issue appears to be related to 1024-bit keys no
> longer being accepted by default; while in general this is obviously a
> desirable behaviour, it is nonetheless a change in the behaviour
> compared to the current package in buster.
>
> The situation is also slightly complicated by the fact the debian-
> installer uses OpenSSL internally, so we are also under internal time
> pressure to reach a conclusion, in order to be able to proceed with the
> installer build for the point release, rather than being able to leave
> the decision until the end of the week.
>
> Thank you for bearing with us.
>
> Regards,
>
> Adam
>
>

Bug#959469: openssl 1.1.1n-0+deb10u1 flagged for acceptance

[Wesley Redondo]

How do I stop these emails

On Mon, Mar 21, 2022, 3:27 PM Adam D. Barratt 
wrote:

> On Sun, 2022-03-20 at 22:00 +0100, Paul Gevers wrote:
> > Dear Sebastian, Kurt,
> >
> > On 19-03-2022 12:33, Adam D Barratt wrote:
> > > Upload details
> > > ==
> > >
> > > Package: openssl
> > > Version: 1.1.1n-0+deb10u1
> > >
> > > Explanation: new upstream release
> >
> > We're seeing a regression in buster in the autopkgtest of gnutls28
> > with
> > the new version of openssl on all tested architectures. Can you
> > please
> > have a look and advise? (bullseye doesn't seem to have the test
> > anymore,
> > hence it doesn't fail).
>
> Thanks to both Kurt and Sebastian for quickly identifying the issue
> here, and to Adrian Bunk for the libnet-ssleay-perl fix.
>
> There's been some continued discussion today as to whether we feel
> comfortable releasing the update with the 10.12 point release when we
> have only been finding such issues during the week leading up to the
> point release.
>
> I fully appreciate that the large delays in getting to this point were
> mostly on our part, and that postponing the release until 10.13 would
> likely be frustrating, but the worry is that we don't have a good view
> of the changes that might be user-affecting in order to be comfortable
> with potential behaviour changes landing in oldstable - for example,
> the libnet-ssleay-perl issue appears to be related to 1024-bit keys no
> longer being accepted by default; while in general this is obviously a
> desirable behaviour, it is nonetheless a change in the behaviour
> compared to the current package in buster.
>
> The situation is also slightly complicated by the fact the debian-
> installer uses OpenSSL internally, so we are also under internal time
> pressure to reach a conclusion, in order to be able to proceed with the
> installer build for the point release, rather than being able to leave
> the decision until the end of the week.
>
> Thank you for bearing with us.
>
> Regards,
>
> Adam
>
>

Re: [google-appengine] Entities Not Visible in Developer Console

[wesley chun]

Sounds good Dave... glad you were able to access your Entities again. In
general, console.*developers*.google.com is just a shortcut to the API
manager, and that's the only time that link should be used. For everything
else, you should be using console.*cloud*.google.com.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
"A computer never does what you want... only what you tell it."
wesley chun :: @wescpy <http://twitter.com/wescpy> :: Software
Architect & Engineer
Developer Advocate at Google
<https://cloud.google.com/developers/advocates/wesley-chun/> by day; at
night: Core Python <http://amzn.com/dp/0132269937>



On Tue, Mar 1, 2022 at 5:45 AM 'Dave Howes' via Google App Engine <
google-appengine@googlegroups.com> wrote:

> Thanks for this response - it turned out that I was using the wrong URL -
> I was going to https://console.developer.google.com/datastore
> <https://console.cloud.google.com/datastore> ( and have been for years )
> - changing to https://console.cloud.google.com/datastore fixed things
>
> Dave
>
> On Sunday, 27 February 2022 at 23:02:42 UTC Wesley C (Google) wrote:
>
>> There have been no changes AFAIK (as far as I know). Going to
>> https://console.cloud.google.com/datastore brings up all my DS entities
>> as expected.
>>
>> However, people sometimes run into problems if they have >1 Google login,
>> say accounts for work, personal, school, etc. Click on your avatar in the
>> upper-right corner to ensure you're logged into the correct account, or
>> select the right one from there if you're not.
>>
>>
>> On Sun, Feb 27, 2022 at 10:03 AM 'Dave Howes' via Google App Engine <
>> google-a...@googlegroups.com> wrote:
>>
>>> I have an application that has been running on App Engine Standard
>>> edition for a number of years. Today, when I went to the Datastore page of
>>> the developers console, I can't see any Entity kinds, and get the following
>>> message :
>>>
>>> "Request had invalid authentication credentials. Expected OAuth 2 access
>>> token, login cookie or other valid authentication credential. See
>>> https://developers.google.com/identity/sign-in/web/devconsole-project.;
>>>
>>> When I go to that page, it seems to be asking me to integrate Google
>>> SignIn with my application, which doesn't seem relevant.
>>>
>>> Has something changed regarding authentication that I have missed?
>>>
>>> Dave
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CAB6eaA4hyh_PC59x81fJsX4c%2BcnhnthrWda%3DYjB3aEOh9yw5sw%40mail.gmail.com.

Re: [google-appengine] Entities Not Visible in Developer Console

[wesley chun]

There have been no changes AFAIK (as far as I know). Going to
https://console.cloud.google.com/datastore brings up all my DS entities as
expected.

However, people sometimes run into problems if they have >1 Google login,
say accounts for work, personal, school, etc. Click on your avatar in the
upper-right corner to ensure you're logged into the correct account, or
select the right one from there if you're not.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
"A computer never does what you want... only what you tell it."
wesley chun :: @wescpy <http://twitter.com/wescpy> :: Software
Architect & Engineer
Developer Advocate at Google
<https://cloud.google.com/developers/advocates/wesley-chun/> by day; at
night: Core Python <http://amzn.com/dp/0132269937>



On Sun, Feb 27, 2022 at 10:03 AM 'Dave Howes' via Google App Engine <
google-appengine@googlegroups.com> wrote:

> I have an application that has been running on App Engine Standard edition
> for a number of years. Today, when I went to the Datastore page of the
> developers console, I can't see any Entity kinds, and get the following
> message :
>
> "Request had invalid authentication credentials. Expected OAuth 2 access
> token, login cookie or other valid authentication credential. See
> https://developers.google.com/identity/sign-in/web/devconsole-project.;
>
> When I go to that page, it seems to be asking me to integrate Google
> SignIn with my application, which doesn't seem relevant.
>
> Has something changed regarding authentication that I have missed?
>
> Dave
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-appengine+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-appengine/33388dfa-ae44-4f4c-9952-928d82fde5d7n%40googlegroups.com
> <https://groups.google.com/d/msgid/google-appengine/33388dfa-ae44-4f4c-9952-928d82fde5d7n%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CAB6eaA4cSr0gb1no-z%3DCFrgXRjdy6MWb8m9oeCsAyNx6VLVHRg%40mail.gmail.com.

Re: [casper] Different Software Versions

[Wesley New]

Hi Kaj,

There is generally a requirements.txt in the root of the mlib_devel which
should list any python dependencies and appropriate versions. I am not sure
how well this is kept uptodate though.

Regards

Wes



On Mon, Feb 21, 2022 at 1:24 PM Kaj Wiik  wrote:

> Hi Adam,
>
> I am sorry but I missed your reply too.
>
> The reason for us to experiment with different versions was to get RFSoC
> (specifically ZCU111) stuff working (by following the documentation in
> https://github.com/casper-astro/tutorials_devel/blob/master/docs/tutorials/rfsoc/tut_getting_started.md
> ). If I understand correctly, the original toolflow in the casper repo does
> not (yet) support RFSoC's?
>
> We will now try to get the Ubuntu 20.04 based versions working, thanks
> Mitch, because Ubuntu 20.04 will be supported longer (perhaps until my
> retirement ;-)). I still have the 18.04 container so I could try out your
> repo too.
>
> I think one of the main problems is that after one group gets everything
> working, there will be Python package upgrades that later installers get
> (without intention) and suddenly the toolflow is not working anymore. I
> think it would be very useful if the versions of all Python packages of a
> working setup would be listed in the documentation.
>
> Many thanks to all who support and develop the Casper toolchain, it
> certainly is not an easy task!
>
> Best regards,
> Kaj
>
> On 2/21/22 12:22, Adam Isaacson wrote:
> > Hi Casperites,
> >
> > I hope you are well. I have been reading the mail list and there are
> lots of queries about which version of Ubuntu, Python, Matlab and Simulink.
> >
> > We have documented this quite well on our Casper website, but I have
> noticed that some people try it on Windows, different versions and expect
> it to work first time around.
> >
> > My honest opinion is that the odds of this working would be slight. My
> advice is to rather stick to the mentioned versions, as those have been
> tested. You are welcome to try new versions, but my feeling is that it
> mostly won't work. My advice is to stick to the software versions.
> >
> > SARAO and CASPER spend a lot of time testing with specific versions. We
> then move onto other projects and move onto newer software versions. This
> is more efficient in my opinion. If there is a major bug then we upgrade.
> >
> > Kind regards,
> >
> > Adam
> >
> > --
> > You received this message because you are subscribed to the Google
> Groups "casper@lists.berkeley.edu" group.
> > To unsubscribe from this group and stop receiving emails from it, send
> an email to casper+unsubscr...@lists.berkeley.edu  casper+unsubscr...@lists.berkeley.edu>.
> > To view this discussion on the web visit
> https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CADTJ%3DnEv0CTDQsW4bpaTXk-6ZB%3D5nsPnb_7%2B5%2BO1Bk8ECwXBxQ%40mail.gmail.com
> <
> https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CADTJ%3DnEv0CTDQsW4bpaTXk-6ZB%3D5nsPnb_7%2B5%2BO1Bk8ECwXBxQ%40mail.gmail.com?utm_medium=email_source=footer
> >.
>
> --
> You received this message because you are subscribed to the Google Groups "
> casper@lists.berkeley.edu" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to casper+unsubscr...@lists.berkeley.edu.
> To view this discussion on the web visit
> https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/29234ed5-7d35-7d5b-2d62-c59198839b56%40utu.fi
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"casper@lists.berkeley.edu" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to casper+unsubscr...@lists.berkeley.edu.
To view this discussion on the web visit 
https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CAE2vkmW%3DEXV%3D5g0ygWUZk_%3D40yJUzXVL84zy3_n62X6kcUUvyg%40mail.gmail.com.

[ovirt-users] Re: oVirt alternatives

[Wesley Stewart]

Thanks, I'll check them out.

On Mon, Feb 7, 2022, 3:56 AM Sandro Bonazzola  wrote:

>
>
> Il giorno dom 6 feb 2022 alle ore 14:06 Wesley Stewart <
> wstewa...@gmail.com> ha scritto:
>
>> Has anyone tried the open shift upstream old?  Looks like they support
>> virtualization now.  Which I'm guessing is the upstream for openshift
>> virtualization?
>>
>> https://docs.okd.io/latest/virt/about-virt.html
>>
>
> I gave a presentation about it 2 days ago at FOSDEM:
> https://fosdem.org/2022/schedule/event/vai_intro_okd/
> but looks like recordings are not yet available at
> https://video.fosdem.org/2022/
> Slides are here:
> https://fosdem.org/2022/schedule/event/vai_intro_okd/attachments/slides/4843/export/events/attachments/vai_intro_okd/slides/4843/OKD_Virtualization_Community.pdf
>
>
>
>
>>
>>
>>
>> On Sat, Feb 5, 2022, 10:34 PM Alex McWhirter  wrote:
>>
>>> Oh i have spent years looking.
>>>
>>> ProxMox is probably the closest option, but has no multi-clustering
>>> support. The clusters are more or less isolated from each other, and
>>> would need another layer if you needed the ability to migrate between
>>> them.
>>>
>>> XCP-ng, cool. No spice support. No UI for managing clustered storage
>>> that is open source.
>>>
>>> Harvester, probably the closest / newest contender. Needs a lot more
>>> attention / work.
>>>
>>> OpenNebula, more like a DIY AWS than anything else, but was functional
>>> last i played with it.
>>>
>>>
>>>
>>> Has anyone actually played with OpenShift virtualization (replaces RHV)?
>>> Wonder if OKD supports it with a similar model?
>>>
>>> On 2022-02-05 07:40, Thomas Hoberg wrote:
>>> > There is unfortunately no formal announcement on the fate of oVirt,
>>> > but with RHGS and RHV having a known end-of-life, oVirt may well shut
>>> > down in Q2.
>>> >
>>> > So it's time to hunt for an alternative for those of us to came to
>>> > oVirt because they had already rejected vSAN or Nutanix.
>>> >
>>> > Let's post what we find here in this thread.
>>> > ___
>>> > Users mailing list -- users@ovirt.org
>>> > To unsubscribe send an email to users-le...@ovirt.org
>>> > Privacy Statement: https://www.ovirt.org/privacy-policy.html
>>> > oVirt Code of Conduct:
>>> > https://www.ovirt.org/community/about/community-guidelines/
>>> > List Archives:
>>> >
>>> https://lists.ovirt.org/archives/list/users@ovirt.org/message/R4YFNNCTW5VVVRKSV2OORQ2UWZ2MTUDD/
>>> ___
>>> Users mailing list -- users@ovirt.org
>>> To unsubscribe send an email to users-le...@ovirt.org
>>> Privacy Statement: https://www.ovirt.org/privacy-policy.html
>>> oVirt Code of Conduct:
>>> https://www.ovirt.org/community/about/community-guidelines/
>>> List Archives:
>>> https://lists.ovirt.org/archives/list/users@ovirt.org/message/EYPC6QXF55UCQPMQL5LDU6XMAF2CZOEG/
>>>
>> ___
>> Users mailing list -- users@ovirt.org
>> To unsubscribe send an email to users-le...@ovirt.org
>> Privacy Statement: https://www.ovirt.org/privacy-policy.html
>> oVirt Code of Conduct:
>> https://www.ovirt.org/community/about/community-guidelines/
>> List Archives:
>> https://lists.ovirt.org/archives/list/users@ovirt.org/message/Z6JTGNYABYPZHHZ3F5Y75KF3KYDWV5OC/
>>
>
>
> --
>
> Sandro Bonazzola
>
> MANAGER, SOFTWARE ENGINEERING, EMEA R RHV
>
> Red Hat EMEA <https://www.redhat.com/>
>
> sbona...@redhat.com
> <https://www.redhat.com/>
>
> *Red Hat respects your work life balance. Therefore there is no need to
> answer this email out of your office hours.*
>
>
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/KAJFH5BOH6PZ3JMZI7UE2VSLQPMROTFQ/

[ovirt-users] Re: oVirt alternatives

[Wesley Stewart]

Good insight.

I use containers a lot, but the virtualization sections are surely
separate?  I might have to try out a node and see how it goes.

On Sun, Feb 6, 2022, 12:25 PM Strahil Nikolov  wrote:

> I've setup a test cluster with Kadalu (which is actually conternerized
> GlusterFS) for storage.
>
> To be honest, it is far more complex. I remember my first day with oVirt
> -> the UI doesn't need any explanation, while working with OKD requires at
> least some knowledge in the terminology of the k8s World.
>
> Best Regards,
> Strahil Nikolov
>
> On Sun, Feb 6, 2022 at 16:46, Wesley Stewart
>  wrote:
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/GD3MQT6L6G5XO3JRVRKBUTUSCMWJ4HUO/
>
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/RZHTSOE636IIRPWRVO7WKNWP4QLPU4AG/

[ovirt-users] Re: oVirt alternatives

[Wesley Stewart]

Sorry autocorrect on a cellphone.

Has anyone tried the openshift upstream okd?*

On Sun, Feb 6, 2022, 8:04 AM Wesley Stewart  wrote:

> Has anyone tried the open shift upstream old?  Looks like they support
> virtualization now.  Which I'm guessing is the upstream for openshift
> virtualization?
>
> https://docs.okd.io/latest/virt/about-virt.html
>
>
>
> On Sat, Feb 5, 2022, 10:34 PM Alex McWhirter  wrote:
>
>> Oh i have spent years looking.
>>
>> ProxMox is probably the closest option, but has no multi-clustering
>> support. The clusters are more or less isolated from each other, and
>> would need another layer if you needed the ability to migrate between
>> them.
>>
>> XCP-ng, cool. No spice support. No UI for managing clustered storage
>> that is open source.
>>
>> Harvester, probably the closest / newest contender. Needs a lot more
>> attention / work.
>>
>> OpenNebula, more like a DIY AWS than anything else, but was functional
>> last i played with it.
>>
>>
>>
>> Has anyone actually played with OpenShift virtualization (replaces RHV)?
>> Wonder if OKD supports it with a similar model?
>>
>> On 2022-02-05 07:40, Thomas Hoberg wrote:
>> > There is unfortunately no formal announcement on the fate of oVirt,
>> > but with RHGS and RHV having a known end-of-life, oVirt may well shut
>> > down in Q2.
>> >
>> > So it's time to hunt for an alternative for those of us to came to
>> > oVirt because they had already rejected vSAN or Nutanix.
>> >
>> > Let's post what we find here in this thread.
>> > ___
>> > Users mailing list -- users@ovirt.org
>> > To unsubscribe send an email to users-le...@ovirt.org
>> > Privacy Statement: https://www.ovirt.org/privacy-policy.html
>> > oVirt Code of Conduct:
>> > https://www.ovirt.org/community/about/community-guidelines/
>> > List Archives:
>> >
>> https://lists.ovirt.org/archives/list/users@ovirt.org/message/R4YFNNCTW5VVVRKSV2OORQ2UWZ2MTUDD/
>> ___
>> Users mailing list -- users@ovirt.org
>> To unsubscribe send an email to users-le...@ovirt.org
>> Privacy Statement: https://www.ovirt.org/privacy-policy.html
>> oVirt Code of Conduct:
>> https://www.ovirt.org/community/about/community-guidelines/
>> List Archives:
>> https://lists.ovirt.org/archives/list/users@ovirt.org/message/EYPC6QXF55UCQPMQL5LDU6XMAF2CZOEG/
>>
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/GD3MQT6L6G5XO3JRVRKBUTUSCMWJ4HUO/

[ovirt-users] Re: oVirt alternatives

[Wesley Stewart]

Has anyone tried the open shift upstream old?  Looks like they support
virtualization now.  Which I'm guessing is the upstream for openshift
virtualization?

https://docs.okd.io/latest/virt/about-virt.html



On Sat, Feb 5, 2022, 10:34 PM Alex McWhirter  wrote:

> Oh i have spent years looking.
>
> ProxMox is probably the closest option, but has no multi-clustering
> support. The clusters are more or less isolated from each other, and
> would need another layer if you needed the ability to migrate between
> them.
>
> XCP-ng, cool. No spice support. No UI for managing clustered storage
> that is open source.
>
> Harvester, probably the closest / newest contender. Needs a lot more
> attention / work.
>
> OpenNebula, more like a DIY AWS than anything else, but was functional
> last i played with it.
>
>
>
> Has anyone actually played with OpenShift virtualization (replaces RHV)?
> Wonder if OKD supports it with a similar model?
>
> On 2022-02-05 07:40, Thomas Hoberg wrote:
> > There is unfortunately no formal announcement on the fate of oVirt,
> > but with RHGS and RHV having a known end-of-life, oVirt may well shut
> > down in Q2.
> >
> > So it's time to hunt for an alternative for those of us to came to
> > oVirt because they had already rejected vSAN or Nutanix.
> >
> > Let's post what we find here in this thread.
> > ___
> > Users mailing list -- users@ovirt.org
> > To unsubscribe send an email to users-le...@ovirt.org
> > Privacy Statement: https://www.ovirt.org/privacy-policy.html
> > oVirt Code of Conduct:
> > https://www.ovirt.org/community/about/community-guidelines/
> > List Archives:
> >
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/R4YFNNCTW5VVVRKSV2OORQ2UWZ2MTUDD/
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/EYPC6QXF55UCQPMQL5LDU6XMAF2CZOEG/
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/Z6JTGNYABYPZHHZ3F5Y75KF3KYDWV5OC/

[Gimp-user] Animations plugins.

[Wesley Colvin via gimp-user-list]

I know you had some available before (I found about g’mic), are those still 
available to download?

Sent from Mail for Windows

___
gimp-user-list mailing list
List address:gimp-user-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list
List archives:   https://mail.gnome.org/archives/gimp-user-list

[Mpi-forum] Looking for MPI Forum Secretary Backup

[Wesley Bland via mpi-forum]

Hi all,

As I mentioned on virtual meeting call today, I’ll be changing jobs soon, and 
while I hope to continue participating in the MPI Forum in my current role as 
secretary, it seems like a good idea to start training someone as a backup for 
my role in the same way Jeff Squyres did with me years ago. Whether I end up 
stepping back from my current role before the next officer election or not, I 
intend to continue to serve as the secretary for at least 2022 to help train 
whomever might be interested in learning more about it.

To that end, Martin and I are soliciting folks who might be interested in 
learning more about the MPI Forum Secretary role and potentially taking over in 
the future to let us know (you can do that off-list), and we’d be happy to talk 
to people that would like to hear more about what that job entails.

As a logistical note, if you’re not already using w...@wesbland.com 
 to contact me via email (which I’ve been using on 
the mailing list for a few years now), you should switch over to that address 
at this point as my Intel email address will disappear in the near future.

Thanks,
Wes___
mpi-forum mailing list
mpi-forum@lists.mpi-forum.org
https://lists.mpi-forum.org/mailman/listinfo/mpi-forum

Re: [casper] Skarab programming error "Skarab has not come back after programming"

[Wesley New]

Hi June,

Over what ethernet interface are you connecting to the SKARAB? 1GbE or
40GbE. IIRC the boot firmware comes with both a 1gbe and 1 of the 40gbe
interfaces built in. The designs you mention would only have the 1 or more
40gbe ethernet interfaces included. You would see the symptoms you are
describing if you initially connect via 1gbe and then it is not included in
the uploaded design.

Hope this helps.

Regards

Wes



On Mon, Jan 10, 2022 at 11:35 PM June Tantiparimongkol 
wrote:

> Hi! Casperities,
>
> I'm writing to you guys for question on Skarab upload and programming
> error. Now, we're trying to program some fpg file into the platform but it
> fails. The error shows "*ERROR 192.168.3.2 transport_skarab.py:755 -
> Skarab has not come back after programming.*"
> So, I have try on generate new fpg files with tutorial design without
> editing (in https://github.com/casper-astro/tutorials_devel.git ) and
> upload and program. After, when we upload and programm new fpg file from
> tut_intro, tut_40gbe, tut_hmc, it shows the same errors too (as shown in
> figure). On the other hand, it has no problem when we worked on tutorial by
> using the example fpg files which are provided within tutorial_devel
> folder. Also, it has no problem with new-generate fpg file from
> skarab_adc_test and tut_spec which we have to generate due to mezzanine
> site configuration.
>
> But there're some condition for our work that we have to generate new fpg
> file with our computer which has Ubuntu 20 OS due to our Ubuntu 18 OS has
> not enough resource to run on execution flow.
>
> So, I wonder that what is the problems. Could anyone suggest us about this
> please.
>
> Thanks and sincerely,
> -- June
> National Astronomical Research Institute of Thailand (NARIT)
> [image: Skarab has not come back after programming.png]
>
> --
> You received this message because you are subscribed to the Google Groups "
> casper@lists.berkeley.edu" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to casper+unsubscr...@lists.berkeley.edu.
> To view this discussion on the web visit
> https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CABKTCqFRWfX9ujJmfyXYF_h%3D_izsQB9MXM6yUxifByasV2Kv9g%40mail.gmail.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"casper@lists.berkeley.edu" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to casper+unsubscr...@lists.berkeley.edu.
To view this discussion on the web visit 
https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CAE2vkmWHYEK0fnA35LOnBsvKJzXixB4_cgNB%3DYUgJckUwcmwRg%40mail.gmail.com.

Re: [google-appengine] Updates from the Google App Engine team (Fall 2021)

[wesley chun]

Reviving this for a bit: @Joshua: are you able to try out Python 3.8 (or
3.9) vs. 3.7 on App Engine? Several performance enhancements went into 3.8
<https://docs.python.org/3/whatsnew/3.8.html#demos-and-tools>, and I'm
curious whether that helps with what you've been experiencing. Also any
updates from your side?

Cheers,
--Wesley
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
"A computer never does what you want... only what you tell it."
wesley chun :: @wescpy <http://twitter.com/wescpy> :: Software
Architect & Engineer
Developer Advocate at Google
<https://cloud.google.com/developers/advocates/wesley-chun/> by day; at
night: Core Python <http://amzn.com/dp/0132269937>



On Sat, Nov 6, 2021 at 7:12 AM Joshua Smith 
wrote:

> I'll put it on my to-do list to make a mock application that just does
> this hammer-on-startup thing. That seems pretty easy. (And it'll be
> interesting to see if a trivial mock app takes 5s to start up, or if
> there's some import I'm doing that's weighing things down.)
>
> -Joshua
>
> On Nov 5, 2021, at 6:39 PM, Jason Collins 
> wrote:
>
> Yes, it is the same scheduler (this is all on GAE Standard, right?) Of
> course, that scheduler has lots of knobs.
>
> If you can build a repro, can you work with support? If anything, the
> concurrency of GAE Python 3 should be better than GAE Python 2.
>
> On Fri, Nov 5, 2021 at 3:36 PM Joshua Smith 
> wrote:
>
>> I don't have threadsafe in my 3.7 app's app.yaml. Just runtime and
>> instance class. (I do have it in my 2.7 app, of course.)
>>
>> I'll try playing with max concurrent threads, but if I bump it from 10
>> (the default) to 16, that really just changes it from 6 request to start an
>> instance, to 9. Hard to see how that would make any difference.
>>
>> As I said, the 2.7 only starts one more instance when I hammer it, and it
>> doesn't end up giving it any work. That's very different behavior from the
>> 3.7 app which starts a bunch of instances and spreads the work to all of
>> them (resulting in all the requests taking at least 5 seconds to fulfill,
>> since the instance takes 5s to start up). This is clearly visible in the
>> logs I included in the first message.
>>
>> You're positive the scheduler is the same?
>>
>> -Joshua
>>
>> On Nov 5, 2021, at 5:08 PM, Jason Collins 
>> wrote:
>>
>> The scheduler is the same.
>>
>> This might have to do with `threadsafe` in app.yaml, which is complicated
>> and confusing. I'd suggest removing `threadsafe` if it's present, then try
>> setting the max_concurrent_requests to something higher (like 2x your
>> number of workers):
>> https://cloud.google.com/appengine/docs/standard/python/config/appref#max_concurrent_requests
>>
>>
>> On Fri, Nov 5, 2021 at 1:48 PM Joshua Smith 
>> wrote:
>>
>>> I figured out from the logs (since it prints a message for each worker
>>> it starts) that 3.7 is starting 8 workers by default. So adding the
>>> entrypoint with defaults has no effect.
>>>
>>> However, I did some experiments and I think I can characterize the
>>> difference between 2.7 and 3.7 when it comes to scaling.
>>>
>>> When first landing on my app's page it shows a list of thumbnails. These
>>> come from the datastore, with each thumbnail making a HTTP request (GET
>>> /image?which=1, GET /image?which=2, etc.). If we:
>>>
>>> 1. Query for all of these at once so the server gets hammered with
>>> simultaneous requests:
>>> - 2.7 starts one extra instance, and while that's happening the images
>>> are all served by the instance that already existed; the new instance never
>>> actually serves any of those image requests.
>>> - 3.7 starts a lot of instances; it dumps a bunch of requests to each of
>>> them (one per worker thread, I presume), all of which are going to take 5
>>> seconds because that's how long it takes each instance to start.
>>>
>>> The net result is the user of the 2.7 app sees all the images load right
>>> away, while the 3.7 app gets them over the course of 15 seconds or so, and
>>> sometimes there are timeout errors.
>>>
>>> 2. Query for these with a delay that's long enough to avoid overlapping
>>> requests:
>>> - Neither starts extra instances.
>>>
>>> The user sees all the images load pretty quick, but not quite as quick
>>> as 2.7 with the first approach.
>>>
>>> My conclusion is that the change is that the old scheduler wouldn't use
>>> an instance until it was 

Re: [google-appengine] Re: When will GAE Python 2.7 be shutdown

[wesley chun]

Hi again,

   1. *dev_appserver*: I replied in my other email that the tool currently
   is available for Python 3 but still requires some components from 2.7 to
   function properly and suggested you can file an external bug to make it
   fully functional in 3.x.
   2. *bundled services*: Google has made available as many of the bundled
   services as possible, but unfortunately there's currently no plan on making
   search available in the next generation runtimes. It is currently
   recommended to migrate to Elastic Search using a Compute Engine VM
   
<https://cloudplatform.googleblog.com/2015/01/Deploy-Elasticsearch-on-Google-Compute-Engine.html>
as
   recommended here
   
<https://cloud.google.com/appengine/docs/standard/python/migrate-to-python3/migrating-services#search>.
   The goal is not "to move people away from App Engine," but to make
   developers' apps more portable, so they can take their apps elsewhere if
   App Engine isn't the right fit for their needs (removing the notion of
   "vendor lock-in") by encouraging developers to migrate away from those
   legacy bundled services. They are strickly a migration tool to ease
   upgrading to Python 3 and will not receive any new features... all of the
   innovation is going into any standalone Cloud equivalent services.
   3. *2.x support*: As Alejandro alluded to, there are no current plans to
   shutdown the Python 2 runtime, even with the sunset of Python 2
   <http://python.org/doc/sunset-python-2/>, older Java, PHP 5, and Go
   versions older than 1.11, by their respective communities. Google Cloud has
   assured users by expressing continued long-term support of these legacy
   runtimes
   <https://cloud.google.com/appengine/docs/standard/long-term-support>,
   including maintaining the Python 2 runtime
   <https://cloud.google.com/python/docs/python2-sunset>. So while there is
   no requirement for users to migrate to Python 3 at this time, developers
   like you are expressing interest in updating their applications to the
   latest language releases.

Best regards,
--Wesley
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
"A computer never does what you want... only what you tell it."
wesley chun :: @wescpy <http://twitter.com/wescpy> :: Software
Architect & Engineer
Developer Advocate at Google
<https://cloud.google.com/developers/advocates/wesley-chun/> by day; at
night: Core Python <http://amzn.com/dp/0132269937>



On Fri, Jan 7, 2022 at 11:38 PM Sajal Gupta  wrote:

> Thanks Alejandro.
>
> *dev_appserver*: The challenge seems to be that it needs python 2
> installation for it to support python 3.x. So, looks like dev_appserver is
> still not "native" to python 3.x.And possibly due to this, I am not able to
> run dev_appserver in debugger mode for python 3.x applications.  That is
> what I meant about dev_appserver not being available fully for python 3.x.
>
> *Bundled services: *Yes, I looks like now memcache and task queue is
> being made available for python 3.x and these seem to be in beta as of now.
> However, from what I understand, *search * is not available as yet unless
> there is a concrete plan to make it available for 3.x. The current
> suggestion for search seems to be host our own on Kubernetes, which defeats
> the whole purpose of someone using Google App Engine - which hides all the
> infra from the developers.
>
> So, unless, the unstated intent of Google team is to move people away from
> App Engine eventually, current, proposed migration path is not helping.
>
> *Notice of termination of python 2.x*: Thank you. This helps.
>
> Regards
>
> Sajal
> On Friday, January 7, 2022 at 9:24:48 PM UTC+5:30 Alejandro L wrote:
>
>> Hello,
>>
>> Thank you for your message.
>>
>> As you mention, Python has ended support for versions 2.x, and we do
>> encourage our users to use a 3.x version. However, I would like to answer
>> all your questions, point by point:
>>
>> 0 - Dev_appserver does indeed have support for Python 3, which you can
>> find here
>> <https://cloud.google.com/appengine/docs/standard/python3/tools/using-local-server>
>> [1].
>>
>> 1 - GAE still supports many 2.x bundled services in the Python 3 runtime,
>> including memcache and task queue. You can find more information about this
>> in this paragraph
>> <https://cloud.google.com/appengine/docs/standard/python/migrate-to-python3#services>
>> [2] from the migrate to Python 3 page, and in this link
>> <https://cloud.google.com/appengine/docs/standard/python3/services/access>
>> [3]. However, currently, the recommendation is to consider migrating to 
>> unbundled
>> Google Cloud products
>> <https://cloud.google.com/app

Re: [google-appengine] Debugger in Python 3

[wesley chun]

Hi, there are several issues at play here:

1. *missing pdb section in the 3.x docs*: this section may be missing
possibly because it doesn't work in Python 3 or hasn't been tested or
validated. The best thing to do here is to go to the Python 3 page you
linked to, scroll down to the bottom, and click the blue "Send feedback"
button, then specify the Python 2 page PDB section link like you did in
your email and ask why this section is missing from *this* (Python 3) page.

2. *dev_appserver.py running on Python 3 still requires the presence of a
2.7 interpreter*: Look specifically at the blue sidebar on this page:
https://cloud.google.com/appengine/docs/standard/python3/tools/using-local-server#running_the_local_development_server
which tells you how to specify the location of your Python 3 interpreter.
While there is an internal bug created against removing final 2.x
dependencies (for a purely 3.x version), I don't see an equivalent external
bug for an App Engine dev_appserver issue
<https://issuetracker.google.com/issues?q=status:open%20dev_appserver> yet,
so if you want there to be a public record tracking this work, please file
a new bug in that same component
<https://issuetracker.google.com/issues/new?component=187227=1162615>
.

Depending on how you feel, you can take either (or both) of the above
actions.

Best regards,
--Wesley

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
"A computer never does what you want... only what you tell it."
wesley chun :: @wescpy <http://twitter.com/wescpy> :: Software
Architect & Engineer
Developer Advocate at Google
<https://cloud.google.com/developers/advocates/wesley-chun/> by day; at
night: Core Python <http://amzn.com/dp/0132269937>



On Sat, Jan 8, 2022 at 1:17 AM Sajal Gupta  wrote:

> Hello,
>
> I am trying to use debugger in python 3 in localhost - using
> dev_appserver. While I find documentation for python debugger usage in
> python 2.7 documentation, there is no similar section for python 3.
>
> See the url below for python 2:
> https://cloud.google.com/appengine/docs/standard/python/tools/using-local-server#debugging_with_pdb
>
> But corresponding section for python 3 is missing:
> https://cloud.google.com/appengine/docs/standard/python3/tools/using-local-server
>
> IDE's own debugger doesn't seem to work - I am using pycharm. Trying to
> use it gives the following error:
> ===
> /usr/bin/python2.7 "/Applications/PyCharm
> CE.app/Contents/plugins/python-ce/helpers/pydev/pydevd.py" --multiproc
> --qt-support=auto --client 127.0.0.1 --port 57002 --file
> /Users/sajal/google-cloud-sdk/bin/dev_appserver.py
> --runtime_python_path=/usr/bin/python3 --support_datastore_emulator=yes
> Connected to pydev debugger (build 213.6461.77)
>
> *ERROR: (dev_appserver) python2: command not found*
> Process finished with exit code 1
> 
>
> Could you please advise.
>
> Thank you.
>
> Sajal
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-appengine+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-appengine/17f597c9-ce21-4a28-a6d7-bf8e26b5d935n%40googlegroups.com
> <https://groups.google.com/d/msgid/google-appengine/17f597c9-ce21-4a28-a6d7-bf8e26b5d935n%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CAB6eaA53uPMNzgTLBFxN7f%3DRtQcB8yU4UCztjxhHd2EqyMNFzQ%40mail.gmail.com.

Re: Last day for FOSDEM submission

[Wesley Peng via perl6-users]

Replacing Bash scripts with Raku? That’s an interesting thing. Can Linux be 
shipped with Raku by default?




hello people,

I just discovered this this morning:

https://www.reddit.com/r/rakulang/comments/rrcp4c/steal_these_ideas_for_raku_fosdem_talks/

I don't remember if there was a previous annoucement in this list but
it's still possible to jump in.

I just submitted one on "Replacing Bash scripts with Raku"

* features and way of doing things i love from zsh
* the raku way [1]
* getting started with raku ecosystem (raku.land, zef, Ddt, fez, rakudoc, 
prove6, ...)

gather/take=while read, Seq vs Pipes, ...) and ideas of modules

1: the raku way are things like

*sh        │ raku
───┼─
|          │ Seq.map
xargs -P  │ .race
while read │ gather/take

At some point it could become an Intro section on the Raku documentation
site.

If a native/fluent english speaker want to take over it: i'll be more
than happy to co-author the talk as well (i really feel like i'm a disaster as
speaker).

Regards
marc

Re: Last day for FOSDEM submission

[Wesley Peng via perl6-users]

Replacing Bash scripts with Raku? That’s an interesting thing. Can Linux be 
shipped with Raku by default?




hello people,

I just discovered this this morning:

https://www.reddit.com/r/rakulang/comments/rrcp4c/steal_these_ideas_for_raku_fosdem_talks/

I don't remember if there was a previous annoucement in this list but
it's still possible to jump in.

I just submitted one on "Replacing Bash scripts with Raku"

* features and way of doing things i love from zsh
* the raku way [1]
* getting started with raku ecosystem (raku.land, zef, Ddt, fez, rakudoc, 
prove6, ...)

gather/take=while read, Seq vs Pipes, ...) and ideas of modules

1: the raku way are things like

*sh        │ raku
───┼─
|          │ Seq.map
xargs -P  │ .race
while read │ gather/take

At some point it could become an Intro section on the Raku documentation
site.

If a native/fluent english speaker want to take over it: i'll be more
than happy to co-author the talk as well (i really feel like i'm a disaster as
speaker).

Regards
marc

Can't visualize image using network path

[henk wesley]

I can't view images using a network path, but when I use a local path, it 
works fine. Also, whenever I put the backslash's (\\10.0.0.18\images), when 
validating it automatically switches to forward slash's 
(//10.0.0.18/images).
Can someone help?
Thanks in advance.
[image: IM.IMAGE.TYPE.png]

-- 
-- 
IMPORTANT: T24/Globus posts are no longer accepted on this forum.

To post, send email to jBASE@googlegroups.com
To unsubscribe, send email to jbase-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/jBASE?hl=en

--- 
You received this message because you are subscribed to the Google Groups 
"jBASE" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jbase+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jbase/f63e3e28-e17c-4986-aaf5-61ddf7bd0d14n%40googlegroups.com.

Bug#1002555: lua-argparse: New upstream and upstream version?

[Nathaniel Wesley Filardo]

Package: lua-argparse
Version: 0.6.0-1.1
Severity: normal
X-Debbugs-Cc: nwfila...@gmail.com

Dear Maintainer,

It looks like LuaRocks has taken over, or at least extended, development of the
argparse module at https://github.com/luarocks/argparse .  They have a newer
version (0.7.1) released that has some nice additional features (e.g.
parser:choices()); would you consider packaging that version for Debian?

Thank you,
--nwf;

-- System Information:
Debian Release: 11.1
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 
'stable-security'), (500, 'stable-debug'), (500, 'proposed-updates-debug'), 
(500, 'stable'), (300, 'unstable')
Architecture: ppc64el (ppc64le)

Kernel: Linux 5.10.0-0.bpo.5-powerpc64le (SMP w/176 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

-- no debconf information

[java code coverage] Re: Jacoco report-aggregate analyzing bundle

[Wesley Wexell]

Just wanted to say thank you to Landmast0rz.  Nothing else online helped, 
but this solved our problem.   We didn't need the failOnWarning setting, 
but we did need to remove the test
Specifically, the integration test module had the app module as a test 
dependency.  Once I removed that scope the aggregation started working.   
Still really confused about WHY that worked, but it worked.

Our project structure
app-parent
|- app
|- app-test
|- app-deployer



On Wednesday, March 10, 2021 at 12:23:09 PM UTC-6 Landmast0rz wrote:

> The team I work with worked it out in the end. For those finding this 
> message from a web search, we ended up solving our problem by removing a 
> test on a module and putting false on 
> maven-dependency-plugin  param.
>
> On Tuesday, March 9, 2021 at 10:02:11 a.m. UTC-5 Landmast0rz wrote:
>
>> I should also mention the index.html file shows 0 coverage but the 
>> session page shows my exec files and (it seems like) all my classes so I'm 
>> really stumped
>>
>> On Tuesday, March 9, 2021 at 9:50:20 a.m. UTC-5 Landmast0rz wrote:
>>
>>> Hello Jacoco group! currently trying to implement Jacoco on multiple 
>>> projects at my work place and I've been stuck on this isssue. I've 
>>> downloaded an example of report-aggregate from the web and during it's 
>>> report-aggregate stage it will: load execution data file xyz and then 
>>> analyse bundle abc. My problem is that on my work project it will never 
>>> starts the analyse bundle stage. Any idea what could cause it to skip that 
>>> part? Many thanks!
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"JaCoCo and EclEmma Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jacoco+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jacoco/d1734efe-a7aa-4743-a445-1d262bf5d218n%40googlegroups.com.

[jira] [Commented] (NIFI-9505) Upgrade Log4j 2 to 2.17.0

[Wesley Philip (Jira)]

[ 
https://issues.apache.org/jira/browse/NIFI-9505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17464163#comment-17464163
 ] 

Wesley Philip commented on NIFI-9505:
-

It sounds like you're saying NiFi is not affected by 
[CVE-2021-45105|https://www.cve.org/CVERecord?id=CVE-2021-45105], but just to 
avoid false positives being reported in Security Scans, Log4j is being upgraded 
to 2.17.0.  Is my understanding correct?

> Upgrade Log4j 2 to 2.17.0
> -
>
> Key: NIFI-9505
> URL: https://issues.apache.org/jira/browse/NIFI-9505
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: David Handermann
>Assignee: David Handermann
>Priority: Minor
> Fix For: 1.16.0, 1.15.2
>
>
> Log4j 2 version 2.17.0 addresses a potential vulnerability in non-standard 
> logging configurations using Thread Context Map lookup capabilities, 
> described in [CVE-2021-45105|https://www.cve.org/CVERecord?id=CVE-2021-45105].
> Although NiFi does not use Log4j 2 for runtime logging, upgrading to version 
> 2.17.0 avoids potential references to older versions in external components.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Commented] (NIFI-9474) Upgrade Log4j 2 to 2.15.0

[Wesley Philip (Jira)]

[ 
https://issues.apache.org/jira/browse/NIFI-9474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17464156#comment-17464156
 ] 

Wesley Philip commented on NIFI-9474:
-

Is Nifi 1.15.1 affected by  CVE-2021-45105?

> Upgrade Log4j 2 to 2.15.0
> -
>
> Key: NIFI-9474
> URL: https://issues.apache.org/jira/browse/NIFI-9474
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Pierre Villard
>Assignee: Bryan Bende
>Priority: Major
>  Labels: security
> Fix For: 1.16.0, 1.15.1
>
>  Time Spent: 1.5h
>  Remaining Estimate: 0h
>
> Following NIFI-9283, upgrade Log4j to 2.15.0 wherever possible.
> This is in light of the recent announcement for 
> https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44228
> We do not believe we use log4j 2 in any way that exposes the vulnerability 
> but we'll update beyond the version anyway.  We still need to fix the 
> following so I reopened the JIRA
> ./nifi-nar-bundles/nifi-atlas-bundle/nifi-atlas-nar/target/classes/META-INF/bundled-dependencies/log4j-api-2.13.3.jar
> ./nifi-nar-bundles/nifi-atlas-bundle/nifi-atlas-nar/target/classes/META-INF/bundled-dependencies/log4j-core-2.13.3.jar
> ./nifi-registry/nifi-registry-core/nifi-registry-web-api/target/nifi-registry-web-api-1.16.0-SNAPSHOT/WEB-INF/lib/log4j-to-slf4j-2.14.1.jar
> ./nifi-registry/nifi-registry-core/nifi-registry-web-api/target/nifi-registry-web-api-1.16.0-SNAPSHOT/WEB-INF/lib/log4j-api-2.14.1.jar
> ./nifi-registry/nifi-registry-toolkit/nifi-registry-toolkit-assembly/target/nifi-registry-toolkit-1.16.0-SNAPSHOT-bin/nifi-registry-toolkit-1.16.0-SNAPSHOT/lib/log4j-to-slf4j-2.14.1.jar
> ./nifi-registry/nifi-registry-toolkit/nifi-registry-toolkit-assembly/target/nifi-registry-toolkit-1.16.0-SNAPSHOT-bin/nifi-registry-toolkit-1.16.0-SNAPSHOT/lib/log4j-api-2.14.1.jar



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Bug#995467: Salvaging status

[Wesley W. Terpstra]

Can I pass the baton of mlton package ownership off to someone?

I've been intending to some day come back to working on this, but the
reality is, I probably never will.
I'd be happy to answer questions about how to get things to work, if that
is helpful.

You need someone who either is currently or wants to become a debian
developer (and go through that whole process).

On Mon, Dec 20, 2021 at 11:39 AM Henry Cejtin 
wrote:

> I built the pdf guide a while ago, and I noticed a few problems that I
> managed to work around.
>
> One point is that you need to have lots of other packages installed, and
> if you don't, it doesn't say anything clear.
>
> I installed all of the following to make it work:
>
> asciidoc
> texlive-full
> docbook
> source-highlight
> context-nonfree
> context-doc-nonfree
> docbook-dsssl-doc
> docbook-defguide
> python-apt-doc
> vim-doc
> w3m
> lynx
> links
> vim-scripts
> epubcheck
> sgmls-doc
>
> (This was a while ago, under Debian Stretch.)
>
> A second point is that under Buster and Bullseye, the convert program
> (from ImageMagick) won't accept pdf's.  The reason has to do with an old
> Ghostscript but and security concerns.
>
> This problem of convert losing this capability also causes the Debian
> package pdfsandwich to no longer work.  It is all a real problem.  Note,
> that there are many other ways to do what needs to be done.  To put
> images into a pdf you can use the Debian package img2pdf.  To go the
> other way, you can use pdfimages or pdftocairo (in poppler-utils).
>
> Somehow it seems that this should be fixed in the imagemagick package
> since there must be other programs that depend on it.
>
> I agree with the comments from people about it probably not being a good
> idea to just edit /etc/ImageMagick-6/policy.xml to let Ghostscript do
> stuff.  That definitely makes me too nervous to do.
>
> On Sun, Dec 19, 2021 at 9:33 PM Ryan Kavanagh  wrote:
> >
> > Another status update for those following at home:
> >
> > The mlton package (upstream release 20210117) now bootstraps and builds!
> >
> > For some reason I can't get the guide to compile (pdflatex spits out a
> > bunch of errors and then dies, and the tool that calls pdflatex suggests
> > the docbook input is invalid), so I might just temporarily disable
> > building/installing it. I figure having an installable mlton package
> > sans PDF guide is better than having no mlton package whatsoever in the
> > meantime.
> >
> > I have considerably more time to work on this now that the semester is
> > over, so I'm hoping to get it uploaded in the next week or so.
> >
> > Best,
> > Ryan
> >
> > --
> > |)|/  Ryan Kavanagh  | 4E46 9519 ED67 7734 268F
> > |\|\  https://rak.ac | BD95 8F7B F8FC 4A11 C97A
>

[jira] [Commented] (NIFI-9474) Upgrade Log4j 2 to 2.15.0

[Wesley Philip (Jira)]

[ 
https://issues.apache.org/jira/browse/NIFI-9474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17460902#comment-17460902
 ] 

Wesley Philip commented on NIFI-9474:
-

OK, thanks [~joewitt] 

> Upgrade Log4j 2 to 2.15.0
> -
>
> Key: NIFI-9474
> URL: https://issues.apache.org/jira/browse/NIFI-9474
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Pierre Villard
>Assignee: Bryan Bende
>Priority: Major
>  Labels: security
> Fix For: 1.16.0, 1.15.1
>
>  Time Spent: 1.5h
>  Remaining Estimate: 0h
>
> Following NIFI-9283, upgrade Log4j to 2.15.0 wherever possible.
> This is in light of the recent announcement for 
> https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44228
> We do not believe we use log4j 2 in any way that exposes the vulnerability 
> but we'll update beyond the version anyway.  We still need to fix the 
> following so I reopened the JIRA
> ./nifi-nar-bundles/nifi-atlas-bundle/nifi-atlas-nar/target/classes/META-INF/bundled-dependencies/log4j-api-2.13.3.jar
> ./nifi-nar-bundles/nifi-atlas-bundle/nifi-atlas-nar/target/classes/META-INF/bundled-dependencies/log4j-core-2.13.3.jar
> ./nifi-registry/nifi-registry-core/nifi-registry-web-api/target/nifi-registry-web-api-1.16.0-SNAPSHOT/WEB-INF/lib/log4j-to-slf4j-2.14.1.jar
> ./nifi-registry/nifi-registry-core/nifi-registry-web-api/target/nifi-registry-web-api-1.16.0-SNAPSHOT/WEB-INF/lib/log4j-api-2.14.1.jar
> ./nifi-registry/nifi-registry-toolkit/nifi-registry-toolkit-assembly/target/nifi-registry-toolkit-1.16.0-SNAPSHOT-bin/nifi-registry-toolkit-1.16.0-SNAPSHOT/lib/log4j-to-slf4j-2.14.1.jar
> ./nifi-registry/nifi-registry-toolkit/nifi-registry-toolkit-assembly/target/nifi-registry-toolkit-1.16.0-SNAPSHOT-bin/nifi-registry-toolkit-1.16.0-SNAPSHOT/lib/log4j-api-2.14.1.jar



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Commented] (NIFI-9474) Upgrade Log4j 2 to 2.15.0

[Wesley Philip (Jira)]

[ 
https://issues.apache.org/jira/browse/NIFI-9474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17460888#comment-17460888
 ] 

Wesley Philip commented on NIFI-9474:
-

Thanks [~pvillard] .  I understand that NiFi 1.15.1 removes all references.  My 
question is whether we think NiFi 1.13.2 really has an exploitable issue with 
the older Log4j v2 libraries, or are the Log4 v2 libraries being upgraded / 
removed out of abundance of caution?

> Upgrade Log4j 2 to 2.15.0
> -
>
> Key: NIFI-9474
> URL: https://issues.apache.org/jira/browse/NIFI-9474
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Pierre Villard
>Assignee: Bryan Bende
>Priority: Major
>  Labels: security
> Fix For: 1.16.0, 1.15.1
>
>  Time Spent: 1.5h
>  Remaining Estimate: 0h
>
> Following NIFI-9283, upgrade Log4j to 2.15.0 wherever possible.
> This is in light of the recent announcement for 
> https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44228
> We do not believe we use log4j 2 in any way that exposes the vulnerability 
> but we'll update beyond the version anyway.  We still need to fix the 
> following so I reopened the JIRA
> ./nifi-nar-bundles/nifi-atlas-bundle/nifi-atlas-nar/target/classes/META-INF/bundled-dependencies/log4j-api-2.13.3.jar
> ./nifi-nar-bundles/nifi-atlas-bundle/nifi-atlas-nar/target/classes/META-INF/bundled-dependencies/log4j-core-2.13.3.jar
> ./nifi-registry/nifi-registry-core/nifi-registry-web-api/target/nifi-registry-web-api-1.16.0-SNAPSHOT/WEB-INF/lib/log4j-to-slf4j-2.14.1.jar
> ./nifi-registry/nifi-registry-core/nifi-registry-web-api/target/nifi-registry-web-api-1.16.0-SNAPSHOT/WEB-INF/lib/log4j-api-2.14.1.jar
> ./nifi-registry/nifi-registry-toolkit/nifi-registry-toolkit-assembly/target/nifi-registry-toolkit-1.16.0-SNAPSHOT-bin/nifi-registry-toolkit-1.16.0-SNAPSHOT/lib/log4j-to-slf4j-2.14.1.jar
> ./nifi-registry/nifi-registry-toolkit/nifi-registry-toolkit-assembly/target/nifi-registry-toolkit-1.16.0-SNAPSHOT-bin/nifi-registry-toolkit-1.16.0-SNAPSHOT/lib/log4j-api-2.14.1.jar



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Commented] (NIFI-9474) Upgrade Log4j 2 to 2.15.0

[Wesley Philip (Jira)]

[ 
https://issues.apache.org/jira/browse/NIFI-9474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17460824#comment-17460824
 ] 

Wesley Philip commented on NIFI-9474:
-

Regarding this statement in the description:

> We do not believe we use log4j 2 in any way that exposes the vulnerability 
> but we'll update beyond the version anyway. 
> We still need to fix the following so I reopened the Jira

I didn't see the following log4 2 core libraries mentioned, so just wondering 
if they were considered in the above statement? (We noticed them in NiFi 
1.13.2).


 
|/opt/nifi/nifi-current/work/nar/extensions/nifi-elasticsearch-client-service-nar-1.13.2.nar-unpacked/NAR-INF/bundled-dependencies/log4j-core-2.11.1.jar|
|/opt/nifi/nifi-current/work/nar/extensions/nifi-elasticsearch-restapi-nar-1.13.2.nar-unpacked/NAR-INF/bundled-dependencies/log4j-core-2.13.3.jar|

> Upgrade Log4j 2 to 2.15.0
> -
>
> Key: NIFI-9474
> URL: https://issues.apache.org/jira/browse/NIFI-9474
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Pierre Villard
>Assignee: Bryan Bende
>Priority: Major
>  Labels: security
> Fix For: 1.16.0, 1.15.1
>
>  Time Spent: 1.5h
>  Remaining Estimate: 0h
>
> Following NIFI-9283, upgrade Log4j to 2.15.0 wherever possible.
> This is in light of the recent announcement for 
> https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44228
> We do not believe we use log4j 2 in any way that exposes the vulnerability 
> but we'll update beyond the version anyway.  We still need to fix the 
> following so I reopened the JIRA
> ./nifi-nar-bundles/nifi-atlas-bundle/nifi-atlas-nar/target/classes/META-INF/bundled-dependencies/log4j-api-2.13.3.jar
> ./nifi-nar-bundles/nifi-atlas-bundle/nifi-atlas-nar/target/classes/META-INF/bundled-dependencies/log4j-core-2.13.3.jar
> ./nifi-registry/nifi-registry-core/nifi-registry-web-api/target/nifi-registry-web-api-1.16.0-SNAPSHOT/WEB-INF/lib/log4j-to-slf4j-2.14.1.jar
> ./nifi-registry/nifi-registry-core/nifi-registry-web-api/target/nifi-registry-web-api-1.16.0-SNAPSHOT/WEB-INF/lib/log4j-api-2.14.1.jar
> ./nifi-registry/nifi-registry-toolkit/nifi-registry-toolkit-assembly/target/nifi-registry-toolkit-1.16.0-SNAPSHOT-bin/nifi-registry-toolkit-1.16.0-SNAPSHOT/lib/log4j-to-slf4j-2.14.1.jar
> ./nifi-registry/nifi-registry-toolkit/nifi-registry-toolkit-assembly/target/nifi-registry-toolkit-1.16.0-SNAPSHOT-bin/nifi-registry-toolkit-1.16.0-SNAPSHOT/lib/log4j-api-2.14.1.jar



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Commented] (NIFI-9474) Upgrade Log4j 2 to 2.15.0

[Wesley Philip (Jira)]

[ 
https://issues.apache.org/jira/browse/NIFI-9474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17460164#comment-17460164
 ] 

Wesley Philip commented on NIFI-9474:
-

Just wondering when this fix will be released publicly, in a new version of 
Nifi?

> Upgrade Log4j 2 to 2.15.0
> -
>
> Key: NIFI-9474
> URL: https://issues.apache.org/jira/browse/NIFI-9474
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Pierre Villard
>Assignee: Bryan Bende
>Priority: Major
>  Labels: security
> Fix For: 1.16.0, 1.15.1
>
>  Time Spent: 1.5h
>  Remaining Estimate: 0h
>
> Following NIFI-9283, upgrade Log4j to 2.15.0 wherever possible.
> This is in light of the recent announcement for 
> https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44228
> We do not believe we use log4j 2 in any way that exposes the vulnerability 
> but we'll update beyond the version anyway.  We still need to fix the 
> following so I reopened the JIRA
> ./nifi-nar-bundles/nifi-atlas-bundle/nifi-atlas-nar/target/classes/META-INF/bundled-dependencies/log4j-api-2.13.3.jar
> ./nifi-nar-bundles/nifi-atlas-bundle/nifi-atlas-nar/target/classes/META-INF/bundled-dependencies/log4j-core-2.13.3.jar
> ./nifi-registry/nifi-registry-core/nifi-registry-web-api/target/nifi-registry-web-api-1.16.0-SNAPSHOT/WEB-INF/lib/log4j-to-slf4j-2.14.1.jar
> ./nifi-registry/nifi-registry-core/nifi-registry-web-api/target/nifi-registry-web-api-1.16.0-SNAPSHOT/WEB-INF/lib/log4j-api-2.14.1.jar
> ./nifi-registry/nifi-registry-toolkit/nifi-registry-toolkit-assembly/target/nifi-registry-toolkit-1.16.0-SNAPSHOT-bin/nifi-registry-toolkit-1.16.0-SNAPSHOT/lib/log4j-to-slf4j-2.14.1.jar
> ./nifi-registry/nifi-registry-toolkit/nifi-registry-toolkit-assembly/target/nifi-registry-toolkit-1.16.0-SNAPSHOT-bin/nifi-registry-toolkit-1.16.0-SNAPSHOT/lib/log4j-api-2.14.1.jar



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[ceph-users] Re: Experience reducing size 3 to 2 on production cluster?

[Wesley Dillingham]

I would avoid doing this. Size 2 is not where you want to be. Maybe you can
give more details about your cluster size and shape and what you are trying
to accomplish and another solution could be proposed. The contents of "ceph
osd tree " and "ceph df" would help.

Respectfully,

*Wes Dillingham*
w...@wesdillingham.com
LinkedIn 


On Fri, Dec 10, 2021 at 12:05 PM Marco Pizzolo 
wrote:

> Hello,
>
> As part of a migration process where we will be swinging Ceph hosts from
> one cluster to another we need to reduce the size from 3 to 2 in order to
> shrink the footprint sufficiently to allow safe removal of an OSD/Mon node.
>
> The cluster has about 500M objects as per dashboard, and is about 1.5PB in
> size comprised solely of small files served through CephFS to Samba.
>
> Has anyone encountered a similar situation?  What (if any) problems did you
> face?
>
> Ceph 14.2.22 bare metal deployment on Centos.
>
> Thanks in advance.
>
> Marco
> ___
> ceph-users mailing list -- ceph-users@ceph.io
> To unsubscribe send an email to ceph-users-le...@ceph.io
>
___
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to ceph-users-le...@ceph.io

Re: Retrieving Correct Click Data for Non-Search Campaigns (YouTube Video Ads)

[Wesley]

Please read my question, it's not about the definition of interactions, 
it's about why I'm getting results that indicate I got many clicks when in 
reality I only got 1 click from that location on that day.

Thanks.

On Thursday, December 9, 2021 at 7:27:02 PM UTC+1 adsapi wrote:

> Hi there,
>
> Here's a product support  
> page that explains what interactions are for Youtube 
> .
>
> Regards,
>
> [image: Google Logo] 
> Aryeh Baker 
> Google Ads API Team 
>   
>
> ref:_00D1U1174p._5004Q2SdGq9:ref
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog:
https://googleadsdeveloper.blogspot.com/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

You received this message because you are subscribed to the Google
Groups "AdWords API and Google Ads API Forum" group.
To post to this group, send email to adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"AdWords API and Google Ads API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to adwords-api+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/8ac728ce-e11d-49f0-8c95-277749b4cc91n%40googlegroups.com.

[kstars] [Bug 446605] Data updates errors out on asteroids update

[Wesley Handrow]

https://bugs.kde.org/show_bug.cgi?id=446605

--- Comment #4 from Wesley Handrow  ---
Fixed! Thanks for your help.


On Tue, Dec 7, 2021 at 2:49 PM Jasem Mutlaq 
wrote:

> https://bugs.kde.org/show_bug.cgi?id=446605
>
> --- Comment #3 from Jasem Mutlaq  ---
> For Windows, please use nightly beta as this was fixed there:
> https://binary-factory.kde.org/job/KStars_Nightly_win64/
>
> --
> You are receiving this mail because:
> You reported the bug.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kstars] [Bug 446605] Data updates errors out on asteroids update

[Wesley Handrow]

https://bugs.kde.org/show_bug.cgi?id=446605

--- Comment #2 from Wesley Handrow  ---
I have, nothing comes up when searching for Comet Leonard.

On Tue, Dec 7, 2021 at 3:31 AM Jasem Mutlaq 
wrote:

> https://bugs.kde.org/show_bug.cgi?id=446605
>
> Jasem Mutlaq  changed:
>
>What|Removed |Added
>
> 
>  Status|REPORTED|RESOLVED
>  Resolution|--- |FIXED
>
> --- Comment #1 from Jasem Mutlaq  ---
> This was fixed in 3.5.6, please try this version.
>
> --
> You are receiving this mail because:
> You reported the bug.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kstars] [Bug 446605] New: Data updates errors out on asteroids update

[Wesley Handrow]

https://bugs.kde.org/show_bug.cgi?id=446605

Bug ID: 446605
   Summary: Data updates errors out on asteroids update
   Product: kstars
   Version: 3.5.5
  Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: mutla...@ikarustech.com
  Reporter: w...@mudlakepottery.com
  Target Milestone: ---

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug
symbols.
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***Data update fails for asteroids.


STEPS TO REPRODUCE
1. 
2. 
3. 

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

-- 
You are receiving this mail because:
You are watching all bug changes.

[Mpi-forum] December 2021 Meeting Voting Block

[Wesley Bland via mpi-forum]

Hi all,

I just wanted to update folks so it’s clear when we’ll have our voting block 
this meeting. We did not use the voting block today, but we do plan to use 
tomorrow’s time slot (11:00am - 11:15am US Central 
) as our one and only voting 
block for this meeting. That means that if you missed the meeting today, you 
still have time to attend tomorrow before that time and be eligible to vote. My 
capture of those who were present today is on the attendance page 
, Please double check 
that I have your attendance correct there.

We will vote on two items tomorrow:

* Errata - •#449 - Fix wrong term "Cartesian process group" in section 8.5.6
* No-no - •#525 - Add new error class MPI_ERR_ERRHANDLER

Item #511 was withdrawn from this meeting. Full details can be found on the 
agenda page: https://www.mpi-forum.org/meetings/2021/12/agenda 
 

Thanks,
Wes___
mpi-forum mailing list
mpi-forum@lists.mpi-forum.org
https://lists.mpi-forum.org/mailman/listinfo/mpi-forum

Re: [Mpi-forum] December MPI Forum Meeting Registration Posted / Call For Topics

[Wesley Bland via mpi-forum]

Hi all,

As a reminder, we’re about a week away from the December 2021 meeting and a 
number of you have still not registered. Please do so at this link:

https://forms.gle/FYUSaHSqaL1uwEEv8 <https://forms.gle/FYUSaHSqaL1uwEEv8>

Thanks,
Wes

> On Nov 11, 2021, at 10:54 AM, Wesley Bland  wrote:
> 
> Hi all,
> 
> The registration page for the December 2021 meeting from December 6 - 9, 2021 
> is now posted. Please register here:
> 
> https://forms.gle/FYUSaHSqaL1uwEEv8 <https://forms.gle/FYUSaHSqaL1uwEEv8>
> 
> If you have topics for votes, plenaries, readings, etc., please announce them 
> to this mailing list ASAP. The deadline for those announcements is November 
> 22nd, which is the week of Thanksgiving in the US so many folks may be on 
> vacation that week.
> 
> Thanks,
> Wes

___
mpi-forum mailing list
mpi-forum@lists.mpi-forum.org
https://lists.mpi-forum.org/mailman/listinfo/mpi-forum

Re: investment offer

[Wesley Adams]

Dear Friend,

Good day to you ,thank you for your time and I hope you and your 
family are staying safe. My name is Wesley Adams, I represent 
Belair Investment LP UK as the company secretary. We are 
Corporate Financing company that generally engage in Project 
Financing. In the cause of our research for companies / 
individuals applying for project funding, we came across your 
contact details. At present, We have funds available to finance 
projects in a deposit account with HSBC UK.

Kindly reply with your Proposal (Project plan/Executive Summary)

Best regards

Wesley Adams
Company Secretary
Belair Investment Lp.

___
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

[Bug 1951994] [NEW] Custom CAs for install source

[Wesley Render]

Public bug reported:


We would like to be able to fully install Ubuntu over https.  Using our own 
certificate authority to secure the apt repo over https.  So for example in our 
Autoinstall user-data file we would have something like: 

apt:
primary:
- arches: [default]
  uri: https://repo.internal/
  ca-cert: |
 Our CA certificate goes here... 

Talking to dbungert in the IRC they mentioned it is not supported yet,
but to create a ticket as it might be something that could be added.

** Affects: subiquity (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1951994

Title:
  Custom CAs for install source

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1951994/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[ceph-users] Re: erasure coded pool PG stuck inconsistent on ceph Pacific 15.2.13

[Wesley Dillingham]

You may also be able to use an upmap (or the upmap balancer) to help make
room for you on the osd which is too full.

Respectfully,

*Wes Dillingham*
w...@wesdillingham.com
LinkedIn <http://www.linkedin.com/in/wesleydillingham>


On Fri, Nov 19, 2021 at 1:14 PM Wesley Dillingham 
wrote:

> Okay, now I see your attachment, the pg is in state:
>
> "state":
> "active+undersized+degraded+remapped+inconsistent+backfill_toofull",
>
> The reason it cant scrub or repair is that its degraded and further it
> seems that the cluster doesnt have the space to make that recovery happen
> "backfill_toofull" state. This may clear on its own as other pgs recover
> and this pg is ultimately able to recover. Other options are to remove data
> or add capacity. How full is your cluster? Is your cluster currently
> backfilling actively.
>
> Respectfully,
>
> *Wes Dillingham*
> w...@wesdillingham.com
> LinkedIn <http://www.linkedin.com/in/wesleydillingham>
>
>
> On Fri, Nov 19, 2021 at 10:57 AM J-P Methot 
> wrote:
>
>> We have stopped deepscrubbing a while ago. However, forcing a deepscrub
>> by doing "ceph pg deep-scrub 6.180" doesn't do anything. The deepscrub
>> doesn't run at all. Could the deepscrubbing process be stuck elsewhere?
>> On 11/18/21 3:29 PM, Wesley Dillingham wrote:
>>
>> That response is typically indicative of a pg whose OSD sets has changed
>> since it was last scrubbed (typically from a disk failing).
>>
>> Are you sure its actually getting scrubbed when you issue the scrub? For
>> example you can issue: "ceph pg  query"  and look for
>> "last_deep_scrub_stamp" which will tell you when it was last deep
>> scrubbed.
>>
>> Further, in sufficiently recent versions of Ceph (introduced in
>> 14.2.something iirc) setting the flag "nodeep-scrub" will cause all in
>> flight deep-scrubs to stop immediately. You may have a scheduling issue
>> where you deep-scrub or repairs arent getting scheduled.
>>
>> Set the nodeep-scrub flag: "ceph osd set nodeep-scrub" and wait for all
>> current deep-scrubs to complete then try and manually re-issue the deep
>> scrub "ceph pg deep-scrub " at this point your scrub should start
>> near immediately and "rados
>> list-inconsistent-obj 6.180 --format=json-pretty" should return with
>> something of value.
>>
>> Respectfully,
>>
>> *Wes Dillingham*
>> w...@wesdillingham.com
>> LinkedIn <http://www.linkedin.com/in/wesleydillingham>
>>
>>
>> On Thu, Nov 18, 2021 at 2:38 PM J-P Methot 
>> wrote:
>>
>>> Hi,
>>>
>>> We currently have a PG stuck in an inconsistent state on an erasure
>>> coded pool. The pool's K and M values are 33 and 3.  The command rados
>>> list-inconsistent-obj 6.180 --format=json-pretty results in the
>>> following error:
>>>
>>> No scrub information available for pg 6.180 error 2: (2) No such file or
>>> directory
>>>
>>> Forcing a deep scrub of the pg does not fix this. Doing a ceph pg repair
>>> 6.180 doesn't seem to do anything. Is there a known bug explaining this
>>> behavior? I am attaching informations regarding the PG in question.
>>>
>>> --
>>> Jean-Philippe Méthot
>>> Senior Openstack system administrator
>>> Administrateur système Openstack sénior
>>> PlanetHoster inc.
>>>
>>> ___
>>> ceph-users mailing list -- ceph-users@ceph.io
>>> To unsubscribe send an email to ceph-users-le...@ceph.io
>>>
>> --
>> Jean-Philippe Méthot
>> Senior Openstack system administrator
>> Administrateur système Openstack sénior
>> PlanetHoster inc.
>>
>>
___
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to ceph-users-le...@ceph.io

[ceph-users] Re: erasure coded pool PG stuck inconsistent on ceph Pacific 15.2.13

[Wesley Dillingham]

Okay, now I see your attachment, the pg is in state:

"state":
"active+undersized+degraded+remapped+inconsistent+backfill_toofull",

The reason it cant scrub or repair is that its degraded and further it
seems that the cluster doesnt have the space to make that recovery happen
"backfill_toofull" state. This may clear on its own as other pgs recover
and this pg is ultimately able to recover. Other options are to remove data
or add capacity. How full is your cluster? Is your cluster currently
backfilling actively.

Respectfully,

*Wes Dillingham*
w...@wesdillingham.com
LinkedIn <http://www.linkedin.com/in/wesleydillingham>


On Fri, Nov 19, 2021 at 10:57 AM J-P Methot 
wrote:

> We have stopped deepscrubbing a while ago. However, forcing a deepscrub by
> doing "ceph pg deep-scrub 6.180" doesn't do anything. The deepscrub doesn't
> run at all. Could the deepscrubbing process be stuck elsewhere?
> On 11/18/21 3:29 PM, Wesley Dillingham wrote:
>
> That response is typically indicative of a pg whose OSD sets has changed
> since it was last scrubbed (typically from a disk failing).
>
> Are you sure its actually getting scrubbed when you issue the scrub? For
> example you can issue: "ceph pg  query"  and look for
> "last_deep_scrub_stamp" which will tell you when it was last deep
> scrubbed.
>
> Further, in sufficiently recent versions of Ceph (introduced in
> 14.2.something iirc) setting the flag "nodeep-scrub" will cause all in
> flight deep-scrubs to stop immediately. You may have a scheduling issue
> where you deep-scrub or repairs arent getting scheduled.
>
> Set the nodeep-scrub flag: "ceph osd set nodeep-scrub" and wait for all
> current deep-scrubs to complete then try and manually re-issue the deep
> scrub "ceph pg deep-scrub " at this point your scrub should start
> near immediately and "rados
> list-inconsistent-obj 6.180 --format=json-pretty" should return with
> something of value.
>
> Respectfully,
>
> *Wes Dillingham*
> w...@wesdillingham.com
> LinkedIn <http://www.linkedin.com/in/wesleydillingham>
>
>
> On Thu, Nov 18, 2021 at 2:38 PM J-P Methot 
> wrote:
>
>> Hi,
>>
>> We currently have a PG stuck in an inconsistent state on an erasure
>> coded pool. The pool's K and M values are 33 and 3.  The command rados
>> list-inconsistent-obj 6.180 --format=json-pretty results in the
>> following error:
>>
>> No scrub information available for pg 6.180 error 2: (2) No such file or
>> directory
>>
>> Forcing a deep scrub of the pg does not fix this. Doing a ceph pg repair
>> 6.180 doesn't seem to do anything. Is there a known bug explaining this
>> behavior? I am attaching informations regarding the PG in question.
>>
>> --
>> Jean-Philippe Méthot
>> Senior Openstack system administrator
>> Administrateur système Openstack sénior
>> PlanetHoster inc.
>>
>> ___
>> ceph-users mailing list -- ceph-users@ceph.io
>> To unsubscribe send an email to ceph-users-le...@ceph.io
>>
> --
> Jean-Philippe Méthot
> Senior Openstack system administrator
> Administrateur système Openstack sénior
> PlanetHoster inc.
>
>
___
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to ceph-users-le...@ceph.io

[ceph-users] Re: erasure coded pool PG stuck inconsistent on ceph Pacific 15.2.13

[Wesley Dillingham]

That response is typically indicative of a pg whose OSD sets has changed
since it was last scrubbed (typically from a disk failing).

Are you sure its actually getting scrubbed when you issue the scrub? For
example you can issue: "ceph pg  query"  and look for
"last_deep_scrub_stamp" which will tell you when it was last deep scrubbed.

Further, in sufficiently recent versions of Ceph (introduced in
14.2.something iirc) setting the flag "nodeep-scrub" will cause all in
flight deep-scrubs to stop immediately. You may have a scheduling issue
where you deep-scrub or repairs arent getting scheduled.

Set the nodeep-scrub flag: "ceph osd set nodeep-scrub" and wait for all
current deep-scrubs to complete then try and manually re-issue the deep
scrub "ceph pg deep-scrub " at this point your scrub should start
near immediately and "rados
list-inconsistent-obj 6.180 --format=json-pretty" should return with
something of value.

Respectfully,

*Wes Dillingham*
w...@wesdillingham.com
LinkedIn 


On Thu, Nov 18, 2021 at 2:38 PM J-P Methot 
wrote:

> Hi,
>
> We currently have a PG stuck in an inconsistent state on an erasure
> coded pool. The pool's K and M values are 33 and 3.  The command rados
> list-inconsistent-obj 6.180 --format=json-pretty results in the
> following error:
>
> No scrub information available for pg 6.180 error 2: (2) No such file or
> directory
>
> Forcing a deep scrub of the pg does not fix this. Doing a ceph pg repair
> 6.180 doesn't seem to do anything. Is there a known bug explaining this
> behavior? I am attaching informations regarding the PG in question.
>
> --
> Jean-Philippe Méthot
> Senior Openstack system administrator
> Administrateur système Openstack sénior
> PlanetHoster inc.
>
> ___
> ceph-users mailing list -- ceph-users@ceph.io
> To unsubscribe send an email to ceph-users-le...@ceph.io
>
___
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to ceph-users-le...@ceph.io

[issue45824] CSV module document does not include how to append files

[Wesley Altham]

Wesley Altham  added the comment:

I now see other things on it but I think the doc should have it as well

--

___
Python tracker 
<https://bugs.python.org/issue45824>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue45824] CSV module document does not include how to append files

[Wesley Altham]

New submission from Wesley Altham :

easy- The CSV module does not include how to append a file which is using 'a' 
and not 'w' or 'r'. There might be more to appending but it is not documented 
for me to know, I saw a stackoverflow post about it when I looked and I tried 
it and worked. I hope whoever knows the CSV module could document append at all.

--
messages: 406438
nosy: wesrl
priority: normal
severity: normal
status: open
title: CSV module document does not include how to append files
type: enhancement
versions: Python 3.10

___
Python tracker 
<https://bugs.python.org/issue45824>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

Upload Click Conversions using Manager account

[Wesley van Opdorp]

Hello,

I'm having some trouble trying to upload click conversions using the api.

The error I'm receiving is:
*This customer does not have an import conversion action that matches the 
conversion action provided*

Let me provide me some context as how we've come to receive this error.

Our account structure:

   - Manager
  - Sub Manager
 - Account 1
 - Account 2
  
Some notes:

   - We use the *Manager* accounts id as *customerId.*
   - The import from clicks conversion action is configured under the 
   *Manager.*
   - For testing purposes we've generated a *gclid* from a campaign that 
   does not use cross account actions.

*Authentication and client setup*
The $loginCustomerId corresponds with the Manager id formatted to int.
---
$oAuth2Credential = (new 
\Google\Ads\GoogleAds\Lib\OAuth2TokenBuilder())->from($configuration)->build();
$googleAdsClient = (new GoogleAdsClientBuilder())
  ->withOAuth2Credential($oAuth2Credential)
  ->withDeveloperToken($developerToken)
  ->withLoginCustomerId($loginCustomerId)
  ->build()
;

*Retrieving the action through the api*
Because of the error I made an attempt to fetch the action through the api 
to make sure that we're using the correct customerId and actionId.
---


*$action = 
$googleAdsClient->getConversionActionServiceClient()->getConversionAction(ResourceNames::forConversionAction($loginCustomerId,
 
$actionId));echo $action->getOwnerCustomer(); // Same as 
$loginCustomerIdecho $action->getId(); // Same as $actionId*

*Uploading click conversion*
The following snippet attempts to upload the conversion. The 
$loginCustomerId and $actionId haven't changed from the snippets above.

*---*







*$clickConversion = new ClickConversion([ 'gclid' => 'Generated gclid 
from Account 1', 'conversion_action' => 
ResourceNames::forConversionAction($loginCustomerId, $actionId), 
'conversion_value' => 0.01, 'conversion_date_time' => (new 
\DateTime())->format('Y-m-d H:i:sP'), 'currency_code' => 'EUR',]);*

*$uploadClient = 
$googleAdsClient->getConversionUploadServiceClient();$response = 
$uploadClient->uploadClickConversions($loginCustomerId, [$clickConversion], 
true);*

The documentation 

 
has a lot of criteria that must be in place for this in order to work and 
I've been trying to make sense of them all. I'm just going to duplicate 
them here, and write down my comments.

   - The ConversionActionType is UPLOAD_CLICKS 
   

   .
  - $action->getType() returns 7 === UPLOAD_CLICKS.
   - The status 
   

 of 
   the ConversionAction is ENABLED.
  - It's enabled in the UI dashboard.
   - The ConversionAction exists in the effective conversion account of the 
   click's Google Ads account.
  - This one has me doubting - the click comes from a account that does 
  not have cross-account conversions enabled, but is still using it's own 
  conversion goals pulled from Google Analytics.
   - At the *time of the click*, conversion tracking was enabled in the 
effective 
   conversion account 
   

 of 
   the click's Google Ads account.
  - I'm not sure what this means - help?
   - Starting with v8 of the Google Ads API, the customer_id of the 
   UploadClickConversionsRequest 
   

 must 
   be the customer ID of the owner_customer of each click conversion's 
   conversion_action 
   

   .
  - The action's owner is the same as our $loginCustomerId.
   
I'm having the idea that the account from which the click originated needs 
to have cross account tracking configured for this to work properly? Could 
someone please confirm this that this is a problem?

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog:
https://googleadsdeveloper.blogspot.com/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

You received this message because you are subscribed to the Google
Groups "AdWords API and Google Ads API Forum" group.
To post to this group, send email to adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"AdWords API and Google Ads API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 

Bug#964934: cookiecutter: Upgrade to version 1.7.x

[Wesley Schwengle]

Hello Vincent,

On 7/13/20 1:08 AM, Vincent Bernat wrote:

  ❦ 12 juillet 2020 16:14 -04, Wesley Schwengle:


In December 2019 version 1.7.0 was released and in April 2020 1.7.1 and
1.7.2 were released. It adds a very useful feature:

   https://cookiecutter.readthedocs.io/en/1.7.2/advanced/directories.html

I would like to make use of this. Could you bump the version the debian
unstable branch?


I am missing a recent enough version of python3-recommonmark due to bug
#955180.


It seems that bug has been resolved. Could you perhaps see if the 
version bump is now possible?


Many thanks!
Wesley

--
Wesley Schwengle
E: wes...@schwengle.net