[gcompris] [Bug 485856] Duplicate dataset names in Frieze activity

[Jazeix Johnny]

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

--- Comment #2 from Jazeix Johnny  ---
Thank you for noticing. I've added the pattern count as it is the difference
between these datasets.

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

[gcompris] [Bug 485856] Duplicate dataset names in Frieze activity

[Jazeix Johnny]

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

Jazeix Johnny  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|REPORTED|RESOLVED
  Latest Commit||https://invent.kde.org/educ
   ||ation/gcompris/-/commit/64e
   ||ac32117a049c867b7e6e61bd047
   ||e83d93022a

--- Comment #1 from Jazeix Johnny  ---
Git commit 64eac32117a049c867b7e6e61bd047e83d93022a by Johnny Jazeix.
Committed on 14/05/2024 at 17:12.
Pushed by jjazeix into branch 'master'.

frieze, update objectives to avoid duplicate ones.

M  +1-1src/activities/frieze/resource/11/Data.qml
M  +1-1src/activities/frieze/resource/7/Data.qml
M  +1-1src/activities/frieze/resource/8/Data.qml
M  +8-8src/activities/frieze/resource/9/Data.qml

https://invent.kde.org/education/gcompris/-/commit/64eac32117a049c867b7e6e61bd047e83d93022a

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

Bug#1056704: xfce4-pabel-profiles: Checking in on this bug

[Faulk Johnny]

Good morning, 
This bug has been her over 6 months now. Is there some sort of issue? I want to 
check in because this bug is a fairly straightforward fix, or so it seems. 
Seems well overdue that this be resloved and the package returned to testing...

Bug#1056704: xfce4-pabel-profiles: Checking in on this bug

[Faulk Johnny]

Good morning, 
This bug has been her over 6 months now. Is there some sort of issue? I want to 
check in because this bug is a fairly straightforward fix, or so it seems. 
Seems well overdue that this be resloved and the package returned to testing...

[education/gcompris/KDE/4.0] docs/docbook: docs, bump version to 4.1

[Johnny Jazeix]

Git commit b39e9cc03137dc5d6493ec2a8cfc4ed778df57b4 by Johnny Jazeix.
Committed on 11/05/2024 at 08:55.
Pushed by jjazeix into branch 'KDE/4.0'.

docs, bump version to 4.1

M  +2-2docs/docbook/index.docbook

https://invent.kde.org/education/gcompris/-/commit/b39e9cc03137dc5d6493ec2a8cfc4ed778df57b4

diff --git a/docs/docbook/index.docbook b/docs/docbook/index.docbook
index 1c90b0a5b5..cc5c992689 100644
--- a/docs/docbook/index.docbook
+++ b/docs/docbook/index.docbook
@@ -46,12 +46,12 @@
 Don't forget to include this last date.
 Please respect the format of the date (-MM-DD),it is used by scripts.
 -->
-2024-02-21
+2024-05-23
 
 
-4.0
+4.1
 
 
 

[education/gcompris] docs/docbook: docs, bump version to 4.1

[Johnny Jazeix]

Git commit f35bf970623fc84817a00f3fba030fb73e263cd5 by Johnny Jazeix.
Committed on 11/05/2024 at 08:08.
Pushed by jjazeix into branch 'master'.

docs, bump version to 4.1

M  +2-2docs/docbook/index.docbook

https://invent.kde.org/education/gcompris/-/commit/f35bf970623fc84817a00f3fba030fb73e263cd5

diff --git a/docs/docbook/index.docbook b/docs/docbook/index.docbook
index 05f068c519..f90dc5ba69 100644
--- a/docs/docbook/index.docbook
+++ b/docs/docbook/index.docbook
@@ -46,12 +46,12 @@
 Don't forget to include this last date.
 Please respect the format of the date (-MM-DD),it is used by scripts.
 -->
-2024-02-21
+2024-05-23
 
 
-4.0
+4.1
 
 
 

[RBW] Re: FS: Droptube Rivendell Custom 54cm

[Johnny Alien]

Main ways it differs (geometry aside because that is above my pay grade), 
this one has canti studs for V, mini-v, or canti brakes. This one is 135 
spaced in the rear I cant remember if the production gallop is 130 or 135. 
The Gallop top tube hits the seat stay a touch higher and uses a lug there 
vs the filet braze. This custom one appears to have downtube shifter bosses 
(nice). Probably slighty lighter tubes but who knows. Thats about all I 
could tell from the photos.

On Friday, May 10, 2024 at 9:57:47 AM UTC-4 Valerie Yates wrote:

> Joe - Thanks for the additional pictures and info.  It is a lovely and 
> interesting bike that sounds like a fun ride. I wonder how it compares to 
> the upcoming Gallop. I am curious but it is out of my price range at 
> present. 
> On Thursday, May 9, 2024 at 7:43:36 AM UTC-6 Joe Bernard wrote:
>
>> Hey, I found pics with the 7-spd stuff! 
>>
>> [image: Screenshot_20240509_064218.jpg]
>> [image: Screenshot_20240509_064229.jpg]
>> On Thursday, May 9, 2024 at 6:40:44 AM UTC-7 Joe Bernard wrote:
>>
>>> [image: Screenshot_20240509_063907.jpg][image: 
>>> Screenshot_20240509_063951.jpg]
>>>
>>> On Thursday, May 9, 2024 at 6:16:25 AM UTC-7 Joe Bernard wrote:
>>>
 Hi Valerie! I'm posting the geometry/tubing mockup Riv sent me which 
 hopefully will answer some questions, I still need to get a current photo 
 set put together this weekend. 

 The tubing is on the lighter side, I would say somewhere between Roadeo 
 and Roadini; I've never ridden a Sam so can't compare to that one. 

 It's long and feels it. At my weight (175 now, closer to 200 for most 
 of the time I've owned it) it has a slight suspension-like ride which is 
 amazingly comfortable. 

 Saddle height in pics is 69cm. I'll get more information and pics for 
 you soon. 

 [image: Screenshot_20221117_163140.jpg]

 On Thursday, May 9, 2024 at 6:05:35 AM UTC-7 Valerie Yates wrote:

> Hi Joe! I am as surprised as everyone  and also impressed how you are 
> constantly assessing what works for you and where you want to be. I would 
> love to see more pics, including the current drivetrain, the handlebar 
> stem 
> area, and the seatpost with height measurement without a bag on it. I 
> love 
> the idea of a fatter tired road-oriented drop tube bike. Is the tubing 
> like 
> Roadini or more like Sam (more stout)? Is the length like Roadini or is 
> it 
> one of the longer models? From the pic, it looks possibly similar in 
> shape 
> to the new Gallop but the tubing and length look more traditional (apart 
> from, the snazzy drop tube and high-viz handlebars). What does it feel 
> like 
> to ride compared to your other Rivs? At my lower weight than yours, I 
> wonder if this would be a good gravel/climbing bike (slot currently 
> filled 
> by a 53 Atlantis, old style). 
>
> On Thursday, May 9, 2024 at 6:02:44 AM UTC-6 Doug H. wrote:
>
>> If the Clem satisfies your needs I understand why you'd sell the 
>> custom. Life throws curve balls at times and forces us to make hard 
>> decisions. So, no second guessing here from me. Just be careful riding a 
>> motorcycle! I love two wheels but not at 60+ mph. :)
>> Doug
>>
>> On Thursday, May 9, 2024 at 6:56:53 AM UTC-4 Mathias Steiner wrote:
>>
>>> If you sell it, you'll kick yourself later, I'm sure. And we'll have 
>>> to listen to it ;)
>>>
>>> When you ride it, it's a custom.
>>> To anyone else, it's a well-made used bicycle.
>>>
>>> Save up for the motor bike, and watch for deals. 
>>> Unlike a motorcycle, your bicycle doesn't cost anything just sitting 
>>> there.
>>>
>>> cheers -mathias
>>>
>>>
>>> On Thursday, May 9, 2024 at 1:40:28 AM UTC-4 Joe Bernard wrote:
>>>
 Bill, 

 I'm not convinced the custom will sell at a price I can live with 
 so there's every possibility it shall remain with me. Selling the Clem 
 would be a possibility but there's not much money in it, I'm not sure 
 it 
 would be worth the trouble. Also I just really like the Clem, I love 
 the 
 color and its utilitarian non-precious vibe. The truth is if I had 
 known in 
 2018 what my riding preferences and mileage would be at 62-years-old I 
 would heve just kept the Clem.L I had then and been happy. Who knew?? 路

 Joe Bernard 

 On Wednesday, May 8, 2024 at 1:07:53 PM UTC-7 Bill Lindsay wrote:

> What are the chances you'll leave it out there, change your mind 
> and sell the Clem instead?  That's the outcome I'm rooting for.  A 
> Rivendell custom is Grant creating a one-of-a-kind bike just for you. 
>  A 
> Clem is fungible.  
>
> Bill Lindsay
> El 

Re: [RBW] Re: For Leah re my Gallop

[Johnny Alien]

I think the big thing is that the gallop was designed for sweptback bars 
and the roadini was not. In the world of Rivendell I am not sure what that 
equates to because most of their bikes can go either way and Grant has said 
that is true here too if you use a short stem. That statement tells me that 
the effective top tube on the gallop will be longer and most likely the 
wheelbase will be as well. If I can figure out how to measure those things 
well I can give it a shot on my prototype and assuming the end geometry is 
pretty similar to the production model we would get some info. Points for 
the gallop would be 1. Just different enough to get you a go fast bike that 
still turns some heads 2. Geometry providing a better fit for an 
alternative cockpit if you don't like the drops.

Downside to the gallop is that the lower top tube allows a larger size to 
fit better. I think its a good guess that Rivendell would steer people that 
way and you likely would be very comfy on a size similar to the larger 
Platy but I think doing that might make drops a bit harder to be 
comfortable on. It would likely need a very very short stem. I guess thats 
not a downside it just makes the sizing discussion a little more open on 
the gallop than the Roadini. But wiht the new 50cm platy you will be packed 
with all sorts of sizing and comfort information to rely on.

Otherwise weight and tubing specs are probably pretty similar between the 
two
On Friday, May 10, 2024 at 8:03:31 AM UTC-4 Bicycle Belle Ding Ding! wrote:

> Woah, that’s a pretty steep drop from Will’s saddle to bars for me! But 
> it’s pretty.
>
> I look forward to your photos, Valerie, and how I wish I lived in your 
> neighborhood so I could bring my saddle and try your bikes. 
>
> When it all boils down, it’s this:
> I’m looking to see what it’s like to ride a stripped-down roadish 
> Rivendell and see how that affects my performance on group rides. Rivendell 
> offers 2 (not counting the hard-to-obtain Roadeo) road bikes in their 
> lineup and I’m trying to differentiate between them and see which one is 
> better for me. I hope they can make that clear in their product description 
> when the time comes for them to launch the CHG. Meanwhile, we get to chat 
> and speculate and evaluate here and it is loads of fun! 
>
> Also, thank you again to everyone for sharing your wisdom with me. Keep it 
> coming!
> L
>
> On May 9, 2024, at 9:46 PM, P W  wrote:
>
> You know, as soon as I hit send, I thought: “It’s a Riv, I bet the tire 
> clearance is actually massive!”
>
>
> 
>
> For how a go-fast Riv roadie could and should look, what better source of 
> inspiration than Will’s:
>
> 
>
>
> See also:
>
>
> <441164476_1599207264208847_1445036392027071003_n.jpg>
>  
> Calling in Sick Magazine on Instagram: "#bikecheck #willkeating @rivbike" 
> 
> Watch and share reels with friends 
> 
> 
>
>
> P. W.
> ~
> (917) 514-2207
> ~
>
>
>
>
> On May 9, 2024, at 6:06 PM, Valerie Yates  wrote:
>
>  
> Also Philip - I have 700x50 tires on my Gallop, so it is not just for 
> skinny tires. But all the rest fits with my impression.  
>
> -- 
> 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/786e3bf1-cb18-479d-8084-edd2aba197c2n%40googlegroups.com
>  
> 
> .
>
> -- 
> 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/zj49RBeKKIM/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/4CC9D2BA-DC90-4CAF-A893-486D2085C41B%40gmail.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/7e527b56-a782-4658-afa3-e604b89e82b3n%40googlegroups.com.

[jira] [Commented] (KAFKA-16672) Fix flaky DedicatedMirrorIntegrationTest.testMultiNodeCluster

[Johnny Hsu (Jira)]

[ 
https://issues.apache.org/jira/browse/KAFKA-16672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17844986#comment-17844986
 ] 

Johnny Hsu commented on KAFKA-16672:


from DistributedHerder, the comment

> Similar to handling HTTP requests, config changes which are observed 
>asynchronously by polling the config log are batched for handling in the work 
>thread.

 

Thus, when there is a rebalance, the herder would throw an error 
`RebalanceNeededException` (in DistributedHerder, L2309). I think this should 
be an retryable exception since it's possible and we should wait for a while 
and try again.

[~chia7712] I am happy to fix this.

> Fix flaky DedicatedMirrorIntegrationTest.testMultiNodeCluster
> -
>
> Key: KAFKA-16672
> URL: https://issues.apache.org/jira/browse/KAFKA-16672
> Project: Kafka
>  Issue Type: Test
>Reporter: Chia-Ping Tsai
>Assignee: Chia-Ping Tsai
>Priority: Minor
>
> It is flaky on my jenkins, and sometimes it fails in Kafka CI[0]
> The error happens in virtue of race condition. `KafkaBasedLog` loads records 
> from topic via thread, so `RebalanceNeededException` will be thrown if we 
> check the task configs too soon. It seems to me `RebalanceNeededException` is 
> a temporary exception so we should treat it as a retryable exception in 
> waiting.
> In short, we should catch `RebalanceNeededException` in 
> `awaitTaskConfigurations` [1] 
> [0] 
> https://ge.apache.org/scans/tests?search.buildOutcome=failure=gradle=P28D=kafka=Asia%2FTaipei=org.apache.kafka.connect.mirror.integration.DedicatedMirrorIntegrationTest=testMultiNodeCluster()
> [1] 
> https://github.com/apache/kafka/blob/55a00be4e973f3f4c8869b6f70de1e285719e890/connect/mirror/src/test/java/org/apache/kafka/connect/mirror/integration/DedicatedMirrorIntegrationTest.java#L355



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Re: [libreoffice-users] Libreoffice Calc

[Johnny Rosenberg]

I guess it depends on your theme, but at least for me, the active cell is
the one that is surrounded by a fat blue frame. I'm not sure how it could
be any clearer than that. Also the column and row headers have a blue
background instead of grey.


Kind regards

Johnny Rosenberg

Den ons 8 maj 2024 kl 12:25 skrev Armando Galavotti <
armando.galavo...@yandex.com>:

> Hi,  where possible I would need your
> help. I have recently been using Libreoffice and in
> particular Calc. However, I have a small problem that I would like to
> solve. When the spreadsheet is clean, i.e. new, I can
> quickly locate which is the active cell where I am going to write but when
> the sheet is full of numbers I have a hard time figuring out which cell is
> active, i.e. which cell is ready to receive my
> writing. I would like to find a way that I can make
> the frame thicker that emasculates the active
> cell. Can you help me with
> this? Thank you very much and see you
> soon. style="color:black;font-family:'century gothic' ,
> sans-serif;font-size:16px;line-height:normal">--  style="font-size:16px;line-height:normal"> style="color:black;font-family:'century gothic' ,
> sans-serif">  style="font-size:16px;line-height:normal"> style="color:black;font-family:'century gothic' , sans-serif">Armando
> Galavotti style="background-color:rgb( 255 , 255 , 255 );color:rgb( 255 , 106 , 0
> );font-family:'lucida
> grande';font-size:10.7px;font-style:normal;font-weight:400;line-height:normal;text-align:justify;text-decoration-color:initial;text-decoration-style:initial;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px">
>   style="background-color:rgb( 255 , 255 , 255 );color:rgb( 255 , 106 , 0
> );font-family:'lucida
> grande';font-size:10.7px;font-style:normal;font-weight:400;line-height:normal;text-align:justify;text-decoration-color:initial;text-decoration-style:initial;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"> style="color:black;font-family:'century gothic' ,
> sans-serif;font-size:16px;line-height:normal">3 Via Piave, Modena (ITA)
> 41121 style="color:black;font-family:'century gothic' ,
> sans-serif;font-size:16px;line-height:normal">Tel. +39 (351) 551 01
> 86 style="color:black;font-family:'century gothic' ,
> sans-serif;font-size:16px;line-height:normal"> style="color:rgb( 17 , 85 , 204 )">
> armando.galavo...@yandex.com style="background-color:rgb( 255 , 255 , 255 );color:rgb( 255 , 106 , 0
> );font-family:'lucida
> grande';font-size:10.7px;font-style:normal;font-weight:400;line-height:normal;text-align:justify;text-decoration-color:initial;text-decoration-style:initial;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"> />RISERVATEZZA DELLE
> INFORMAZIONI />Questo messaggio di posta
> elettronica contiene informazioni di carattere confidenziale rivolte
> esclusivamente al destinatario sopra indicato. E' vietato l'uso, la
> diffusione, distribuzione o riproduzione da parte di ogni altra persona.
> Nel caso aveste ricevuto questo messaggio di posta elettronica per errore,
> siete pregati di segnalarlo immediatamente al mittente e distruggere quanto
> ricevuto (compresi i file allegati) senza farne copia. Qualsivoglia
> utilizzo non autorizzato del contenuto di questo messaggio costituisce
> violazione dell'obbligo di non prendere cognizione della corrispondenza tra
> altri soggetti, salvo più grave illecito, ed espone il responsabile alle
> relative conseguenze.This e-mail is confidential and may also
> contain privileged information. If you are not the intended recipient you
> are not authorized to read, print, save, process or disclose this message.
> If you have received this message by mistake, please inform the sender
> immediately and delete this e-mail, its attachments and any copies. Any
> use, distribution, reproduction or disclosure by any person other than the
> intended recipient is strictly prohibited and the person responsible may
> incur penalties. Thank you! 
> --
> To unsubscribe e-mail to: users+unsubscr...@global.libreoffice.org
> Problems?
> https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
> Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
> List archive: https://listarchives.libreoffice.org/global/users/
> Privacy Policy: https://www.documentfoundation.org/privacy
>

-- 
To unsubscribe e-mail to: users+unsubscr...@global.libreoffice.org
Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
List archive: https://listarchives.libreoffice.org/global/users/
Privacy Policy: https://www.documentfoundation.org/privacy

[CentOS-announce] CESA-2024:1935 Low CentOS 7 thunderbird Security Update

[Johnny Hughes]

CentOS Errata and Security Advisory 2024:1935 Low

Upstream details at : https://access.redhat.com/errata/RHSA-2024:1935

The following updated files have been uploaded and are currently 
syncing to the mirrors: ( sha256sum Filename ) 

x86_64:
3edc5c8d5cf1dd51b987f3178aa2e996847bacf9b48d9d5f96f0831a21c48b97  
thunderbird-115.10.0-2.el7.centos.x86_64.rpm

Source:
e520e8a450ea7f14a689a5c91dd88e028ac3be1196ad17456c4cb0475da642da  
thunderbird-115.10.0-2.el7.centos.src.rpm



-- 
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@libera.chat
Twitter: @JohnnyCentOS

___
announce mailing list -- announce@lists.centos.org
To unsubscribe send an email to announce-le...@lists.centos.org

[CentOS-announce] CESA-2024:1910 Important CentOS 7 firefox Security Update

[Johnny Hughes]

CentOS Errata and Security Advisory 2024:1910 Important

Upstream details at : https://access.redhat.com/errata/RHSA-2024:1910

The following updated files have been uploaded and are currently 
syncing to the mirrors: ( sha256sum Filename ) 

x86_64:
469ca6e8993db68735d7333e493a80dd4dde10f37d4c15b290e072922a543da8  
firefox-115.10.0-1.el7.centos.i686.rpm
daff96fd89f92832ea99fda83cf1b76e717202ee8aa4dbe27e75350ce028065f  
firefox-115.10.0-1.el7.centos.x86_64.rpm

Source:
b272bc5c50b3107bf2130f9ae259fdc7a05e20a8c73a8967c9724219c6267173  
firefox-115.10.0-1.el7.centos.src.rpm



-- 
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@libera.chat
Twitter: @JohnnyCentOS

___
announce mailing list -- announce@lists.centos.org
To unsubscribe send an email to announce-le...@lists.centos.org

[CentOS-announce] CEBA-2024:1759 CentOS 7 firefox BugFix Update

[Johnny Hughes]

CentOS Errata and Bugfix Advisory 2024:1759 

Upstream details at : https://access.redhat.com/errata/RHBA-2024:1759

The following updated files have been uploaded and are currently 
syncing to the mirrors: ( sha256sum Filename ) 

x86_64:
06de00e45a444bd8381c6526ee4a204b80511ebbca8c8b0b52bfd9d9bacec74c  
firefox-115.9.1-2.el7.centos.i686.rpm
74e98e4966e80435f954bb2859be485730a97c3e547acc848d76d50f49af0329  
firefox-115.9.1-2.el7.centos.x86_64.rpm

Source:
e556ba9ce8535f9e8992a4255356beaf9ff24096c76a7f43495a40c3783553d3  
firefox-115.9.1-2.el7.centos.src.rpm



-- 
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@libera.chat
Twitter: @JohnnyCentOS

___
announce mailing list -- announce@lists.centos.org
To unsubscribe send an email to announce-le...@lists.centos.org

[CentOS-announce] CESA-2024:2004 Important CentOS 7 kernel Security Update

[Johnny Hughes]

CentOS Errata and Security Advisory 2024:2004 Important

Upstream details at : https://access.redhat.com/errata/RHSA-2024:2004

The following updated files have been uploaded and are currently 
syncing to the mirrors: ( sha256sum Filename ) 

x86_64:
580edd83e305e9b58fb0cceca959a21a8c59ccd3bc075f075211019108f73863  
bpftool-3.10.0-1160.118.1.el7.x86_64.rpm
8db5b248a66cb5ad1ed9c3264fe68eb2d2de4e9b3a5c7cc07f61bde703d26938  
kernel-3.10.0-1160.118.1.el7.x86_64.rpm
085f001bc61a93bf23c68f240bd7b5c24aa41e4a9b6c5539dfe676b451ec102a  
kernel-abi-whitelists-3.10.0-1160.118.1.el7.noarch.rpm
211028daa1af91e1fc841cb5b76e2f4edf63f510630571253c89635fccd41209  
kernel-debug-3.10.0-1160.118.1.el7.x86_64.rpm
aed30d0de3bf0d71c9c9be43e3e4b5e8d6832a7e755e8cfd843a6bd7f735d310  
kernel-debug-devel-3.10.0-1160.118.1.el7.x86_64.rpm
c20dbccc7c4cc73173c89b3632eb2dbf33e22faaaf1b317279ecad8e2b1fe49b  
kernel-devel-3.10.0-1160.118.1.el7.x86_64.rpm
16a9d3e7ce759abfcc7721bbe369b46acd4b3c511910e0ac4f61445d857f52d8  
kernel-doc-3.10.0-1160.118.1.el7.noarch.rpm
bbfb59fb0bbbee9e6941d7531aa54e1719671ed000cfb77426d6cc19506cebe1  
kernel-headers-3.10.0-1160.118.1.el7.x86_64.rpm
b6ef3e291bb25a5525d4b85ac8b4bad708a7f474d0baeb5ed6d75da8f0ff9c5e  
kernel-tools-3.10.0-1160.118.1.el7.x86_64.rpm
c560870127d4c5652e42c74ffbb3cf96a864ca994702fffd84bfe5a6b5275464  
kernel-tools-libs-3.10.0-1160.118.1.el7.x86_64.rpm
07bd35c3abbf6026fb0e99d204b230ccbed3b91ccbed6d0675f5dc885931ea62  
kernel-tools-libs-devel-3.10.0-1160.118.1.el7.x86_64.rpm
a48132ab5f5f42b2a741922bb5933c0f84e9994688313798505382288ac76453  
perf-3.10.0-1160.118.1.el7.x86_64.rpm
643e8a5dafaf596ced8be2e0be3e3edb692c0c81871c46db2a2541ee4de4aca2  
python-perf-3.10.0-1160.118.1.el7.x86_64.rpm

Source:
5841347df43921557d9488aad1584d7fa0ccfa354dccea91ad187b452f78f30b  
kernel-3.10.0-1160.118.1.el7.src.rpm



-- 
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@libera.chat
Twitter: @JohnnyCentOS

___
announce mailing list -- announce@lists.centos.org
To unsubscribe send an email to announce-le...@lists.centos.org

[CentOS-announce] CESA-2024:2002 Moderate CentOS 7 grub2 Security Update

[Johnny Hughes]

CentOS Errata and Security Advisory 2024:2002 Moderate

Upstream details at : https://access.redhat.com/errata/RHSA-2024:2002

The following updated files have been uploaded and are currently 
syncing to the mirrors: ( sha256sum Filename ) 

x86_64:
425b1c0988b4a82a7edad5a994ae16e7775d36d9efe1e2cfab48f0893276a38c  
grub2-2.02-0.87.0.2.el7.centos.14.x86_64.rpm
ba3679dbdaf62ecae1a485bd198e4127a1c7605fffa6492fb32ed97c97eff892  
grub2-common-2.02-0.87.0.2.el7.centos.14.noarch.rpm
31e074062d36f692f0ee2ec64a68e0193b540bf85cc09b3fd7a6f3384ab55806  
grub2-efi-ia32-2.02-0.87.0.2.el7.centos.14.x86_64.rpm
c30d6ca286d3a7294da3e5596cf791d5c1314667173d02f21d751e689e05d52b  
grub2-efi-ia32-cdboot-2.02-0.87.0.2.el7.centos.14.x86_64.rpm
fa40075494cdb791de80bb9dd16a60c61c5e4200559523fc4cb22ded671eda5a  
grub2-efi-ia32-modules-2.02-0.87.0.2.el7.centos.14.noarch.rpm
6629074551d9fb3315ab487254009bfbf5ff68dc9d1c73b4aa5c866e5448129c  
grub2-efi-x64-2.02-0.87.0.2.el7.centos.14.x86_64.rpm
bcebc5d5ae20b6fbf0a5f35a2831414d8ad7aa1ea1720883560416fbd5db15b7  
grub2-efi-x64-cdboot-2.02-0.87.0.2.el7.centos.14.x86_64.rpm
61afac8f37a4ea3ff4615ff2c44e669f884f9d092a45699fc0fd2dcac09465d8  
grub2-efi-x64-modules-2.02-0.87.0.2.el7.centos.14.noarch.rpm
70d313100de0a9a28bad9868e3267b01f56634e7b633d7519f3153020d8c77b7  
grub2-i386-modules-2.02-0.87.0.2.el7.centos.14.noarch.rpm
e319773b66bb4f0227b1608807845710d392639797e4f0e6714024b71cb7b1f7  
grub2-pc-2.02-0.87.0.2.el7.centos.14.x86_64.rpm
2445bee7e1332244f8b40961bfe9f59880197fd2e4ea9800c0b288239d229acb  
grub2-pc-modules-2.02-0.87.0.2.el7.centos.14.noarch.rpm
7ed3fc20ba01570a826ffa2af023ade0d8581765238cc534b73fe6e9508c4beb  
grub2-tools-2.02-0.87.0.2.el7.centos.14.x86_64.rpm
4c61a98e630cf29009706ab099ff7870c3593c7eb39e9d0edb5e059359012e52  
grub2-tools-extra-2.02-0.87.0.2.el7.centos.14.x86_64.rpm
c67c4c4063b74aae72efd079229bf2ca2167a39844fe319e3e726d3df81c4767  
grub2-tools-minimal-2.02-0.87.0.2.el7.centos.14.x86_64.rpm

Source:
0465f1475edbb9f51763cbc79c51263fa408f6478cee30db712ba438154613ae  
grub2-2.02-0.87.0.2.el7.centos.14.src.rpm



-- 
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@libera.chat
Twitter: @JohnnyCentOS

___
announce mailing list -- announce@lists.centos.org
To unsubscribe send an email to announce-le...@lists.centos.org

[CentOS-announce] CESA-2024:2080 Important CentOS 7 tigervnc Security Update

[Johnny Hughes]

CentOS Errata and Security Advisory 2024:2080 Important

Upstream details at : https://access.redhat.com/errata/RHSA-2024:2080

The following updated files have been uploaded and are currently 
syncing to the mirrors: ( sha256sum Filename ) 

x86_64:
0e15a4084dc2ccf63f0b0ad4073f81fdd2a5a9137184d9fd3f72e558dadcb56e  
tigervnc-1.8.0-33.el7_9.x86_64.rpm
1b79cf7e51fdd270ad47abaf4877bf5ef54856e2842af27bf476d4129bf130cb  
tigervnc-icons-1.8.0-33.el7_9.noarch.rpm
e33353c1f5c8cd09778ece298733e91964fae61ddc04af20b7b6eec95035236c  
tigervnc-license-1.8.0-33.el7_9.noarch.rpm
6ca8c118a949900b7ee2de435dfa29344feecf178d19d4852cfd3f958da2ac14  
tigervnc-server-1.8.0-33.el7_9.x86_64.rpm
2ad5877d7f45633aac8fe2c12d2a6f3490fa224374fff1161e930b4f55896467  
tigervnc-server-applet-1.8.0-33.el7_9.noarch.rpm
37ac533da616e343432c0f1378f9e585ef3a6d8ad632bf56c45e59e7cbb1076a  
tigervnc-server-minimal-1.8.0-33.el7_9.x86_64.rpm
7fd90181b9a3e062d087509d186c4ef8394aec39ce24e0670b0a4c7b21d8c381  
tigervnc-server-module-1.8.0-33.el7_9.x86_64.rpm

Source:
bcb1ef5e5c28f48632f22c952634a1133be57d47a2d375afc42a86c8b74abeeb  
tigervnc-1.8.0-33.el7_9.src.rpm



-- 
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@libera.chat
Twitter: @JohnnyCentOS

___
announce mailing list -- announce@lists.centos.org
To unsubscribe send an email to announce-le...@lists.centos.org

[CentOS-announce] CESA-2024:1787 Important CentOS 7 squid Security Update

[Johnny Hughes]

CentOS Errata and Security Advisory 2024:1787 Important

Upstream details at : https://access.redhat.com/errata/RHSA-2024:1787

The following updated files have been uploaded and are currently 
syncing to the mirrors: ( sha256sum Filename ) 

x86_64:
f5ee3ffceb6d3dc9e61ef0f7f67a18dcd1934d4331e74fa1ae157538a284020d  
squid-3.5.20-17.el7_9.10.x86_64.rpm
d5b8118e51ac12c714bac62344ad5e2f4caebfee78da0c525e284f1a1334bd7d  
squid-migration-script-3.5.20-17.el7_9.10.x86_64.rpm
8c9ca7fef03b651b6cf4439fc8f4e9406e901baac07b1d86a9d94eedeb2b84cc  
squid-sysvinit-3.5.20-17.el7_9.10.x86_64.rpm

Source:
c52644f3b90f7565d6a694361e0206070a8f463656b0da648ef7e1f9d514df02  
squid-3.5.20-17.el7_9.10.src.rpm



-- 
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@libera.chat
Twitter: @JohnnyCentOS

___
announce mailing list -- announce@lists.centos.org
To unsubscribe send an email to announce-le...@lists.centos.org

[CentOS-announce] CESA-2024:1785 Important CentOS 7 xorg-x11-server Security Update

[Johnny Hughes]

CentOS Errata and Security Advisory 2024:1785 Important

Upstream details at : https://access.redhat.com/errata/RHSA-2024:1785

The following updated files have been uploaded and are currently 
syncing to the mirrors: ( sha256sum Filename ) 

x86_64:
d048e9282e3eab42d5adfd632ef5cd029524100f32b305395da9da9a0371c460  
xorg-x11-server-common-1.20.4-29.el7_9.x86_64.rpm
b0a8eeea28a48870600033e3ed255b73b22ef84935f83e1d18f3bf72359b66d3  
xorg-x11-server-devel-1.20.4-29.el7_9.i686.rpm
cfb8fb181e4fcc069e88e40ad4838b6d53339b522603c2c188f4b7719a7547d1  
xorg-x11-server-devel-1.20.4-29.el7_9.x86_64.rpm
a4e3cfe2ec39289ce4330038a8f3fa801449727c3b6173cf5ceabec99f36bf59  
xorg-x11-server-source-1.20.4-29.el7_9.noarch.rpm
8e736c3e7e6197e2f51879707a4e058e188e3e707c7a986b9cfb7846c920b11b  
xorg-x11-server-Xdmx-1.20.4-29.el7_9.x86_64.rpm
b7a51c89deecc8235479935646047575b00838c8e74a15aa90fd3f04dbf38d1f  
xorg-x11-server-Xephyr-1.20.4-29.el7_9.x86_64.rpm
f80cd4881b32dd129ece7202403ba656b6cabbaebccce97cfcacaf448e2d221f  
xorg-x11-server-Xnest-1.20.4-29.el7_9.x86_64.rpm
a513143acbf28366be9f3830ac06cb3468fbca694206826e572edafd38461ed0  
xorg-x11-server-Xorg-1.20.4-29.el7_9.x86_64.rpm
dd05b77f960a6b0aed0f034b93449043a31100aec1f59ed4819b5d1ad663b83d  
xorg-x11-server-Xvfb-1.20.4-29.el7_9.x86_64.rpm
cf83179c708ff22b53ddfb306e537749dfa4ac8e8f7f820be6740d1988c8ffc8  
xorg-x11-server-Xwayland-1.20.4-29.el7_9.x86_64.rpm

Source:
d90825158475951624597cd04ab8a4aeaff353bb6d121fafcfcb5f81691c85ce  
xorg-x11-server-1.20.4-29.el7_9.src.rpm



-- 
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@libera.chat
Twitter: @JohnnyCentOS

___
announce mailing list -- announce@lists.centos.org
To unsubscribe send an email to announce-le...@lists.centos.org

[jira] [Commented] (KAFKA-16684) FetchResponse#responseData could return incorrect data

[Johnny Hsu (Jira)]

[ 
https://issues.apache.org/jira/browse/KAFKA-16684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17844496#comment-17844496
 ] 

Johnny Hsu commented on KAFKA-16684:


hi [~chia7712] 
May i know if you are working on this? if not I am happy to help :) 

> FetchResponse#responseData could return incorrect data
> --
>
> Key: KAFKA-16684
> URL: https://issues.apache.org/jira/browse/KAFKA-16684
> Project: Kafka
>  Issue Type: Bug
>Reporter: Chia-Ping Tsai
>Assignee: Chia-Ping Tsai
>Priority: Minor
>
> [https://github.com/apache/kafka/commit/2b8aff58b575c199ee8372e5689420c9d77357a5]
>  make it accept input to return "partial" data. The content of output is 
> based on the input but we cache the output ... It will return same output 
> even though we pass different input. That is a potential bug.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Re: [RBW] Re: FS: 58cm Appaloosa Double Top Tube Disc Brake

[Johnny Burrell]

If you sold it parted out, I'd love to have the Mark's front rack.

On Thursday, May 2, 2024 at 9:18:19 AM UTC-7 eric swain wrote:

> Sold. 
>
> On Monday, April 22, 2024 at 10:59:51 AM UTC-7 eric swain wrote:
>
>> Bump. 
>>
>> I'd also part it out. Frame/fork/headset/seat post/front rack/stem $1000. 
>>
>> On Monday, April 8, 2024 at 4:38:40 PM UTC-7 Patrick Moore wrote:
>>
>>> Nice. I find disc-brake retro-equipped Rivendells rather interesting; I 
>>> know another person retrofitted them to a very nice Atlantis.
>>>
>>> Who else has done this, and why?
>>>
>>> Me, I like discs for dirt riding tho' they don't add anything for my 
>>> pavement riding.
>>>
>>> On Mon, Apr 8, 2024 at 4:56 PM eric swain  wrote:
>>>
 And here is a full list of parts.

 Frame & fork: 58cm Joe Appaloosa with double top tubes AND disc brake 
 tabs added by Walt Works.
 Headset: Tange Levin CDS
 Stem:  Crust/Nitto, 31.8mm, 75mm, silver 
 Handlebars: Tumbleweed Persuader, steel, cut to 760mm 
 Grips: DMR Deathgrip
 Brake levers: Shimano BL-M600
 Brakes: Paul Klampers, long pull, Paul brake adapters. Avid Clean Sweep 
 G2 160mm Rotors
 Shifters: Shimano XT SL-M750
 Rear Derailleur: Shimano Deore RD-M591
 Front Derailleur: Shimano Deore XT Triple
 Cassette: Sram PG-950 9 speed, 11-34
 Chain: Sram PC-951
 Cranks: Shimano Deore FC-MT60, 175mm, 110/74 bcd, Shimano chain rings 
 46t/30t(46 mounted in the middle position, 30 in the small ring position)
 Bottom Bracket: Shimano UN55 68 x 118mm
 Pedals: No pedals, I'm keeping the Speedplay platforms currently 
 installed. 
 Hubs: Profile Racing Elite 6 bolt disc, 32h, black, QR, HG 11 speed 
 road freehub body, Shimano XT skewers. I'll also include the end caps and 
 hardware to convert hubs to bolt on.
 Rims: Sun Ringle Rhyno Lites, 32h, black with machined sidewalls
 Spokes/nipples, DT Swiss Competition, black, DT Swiss silver brass 
 nipples
 Tires: Schwalbe Marathon 700 x 50, regular inner tubes
 Seat Post: Thomson Elite, silver. I'll include the Nitto post as well.
 Saddle: Brooks Cambium C17
 Front rack: Nitto Mark's Rack, silver with Wald 137 Basket
 Fenders: Planet Bike Cascadia 29 x 65mm, Black

 On Monday, April 8, 2024 at 3:55:05 PM UTC-7 eric swain wrote:

> Hey folks,
>
> Some of you may remember I tried selling my Appaloosa back in 2020. 
> Well at that time I decided to keep it, change a few parts, and have 
> really 
> enjoyed it since then. Fun bike to ride, great set up for commuting, 
> running errands, dawdling around the neighborhood, and general bicycle 
> shenanigans. Fast forward to present times: my quiver has grown to a 
> ridiculous amount of bikes, my personal riding focus has shifted, I have 
> a 
> new bike on the way, and I may be moving soon. I do not have room for 
> every 
> bike and with a potential move I need scale back on large items, like 
> bikes. So this one is back up for sale! 
>
> I am asking $2000 as pictured(minus pedals). Including the Outershell 
> Wald 137 basket bag, Makeshifter Snackhole stem bag, Zefal frame pump, 
> Paul 
> Gino light mount, and King cages. Bike is located in Portland OR. Test 
> rides are welcome. Boxing and shipping is no problem. Here is a link to 
> more pics and the geo.
>
>
> https://drive.google.com/drive/folders/119mQzJCLMtSAMxge007HSiDUI9lv76W4?usp=sharing
>
> Thanks,
> Eric
>
> -- 
 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/ad91a613-8390-46df-b513-ce0e7305be34n%40googlegroups.com
  
 
 .

>>>
>>>
>>> -- 
>>>
>>> Patrick Moore
>>> Alburquerque, Nuevo Mexico, Etats Unis d'Amerique, Orbis Terrarum
>>>
>>> ---
>>>
>>> Executive resumes, LinkedIn profiles, bios, letters, and other writing 
>>> services
>>>
>>>
>>> ---
>>>
>>> *When thou didst not, savage, k**now thine own meaning,*
>>>
>>> *But wouldst gabble like a** thing most brutish,*
>>>
>>> *I endowed thy purposes w**ith words that made them known.*
>>>
>>

-- 
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] Re: WTB: Hunqapillar 54 / 56 cm

[Johnny Burrell]

Good luck Max. I was on the same quest when an amazing person from this 
group, Matthew Williams, saw one and let me know about it. I posted here 
every ~6 months letting folks know I was still looking and it took a few 
years to find one in my size, but it did happen eventually. It's a cool 
bike, for sure.

On Tuesday, May 7, 2024 at 5:44:41 AM UTC-7 Max S wrote:

> Test-rode one over a decade ago at BBB, shoulda bought it then. Maybe 
> someone's ready to pass theirs on to another good home?.. (Ideally just a 
> frameset)
>
> - Max "coulda shoulda woulda try againa" in A2
>

-- 
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/5a86afdc-1401-402e-8339-f0853ced0ab8n%40googlegroups.com.

[RBW] Re: New Sam Hillborne sizing advice

[Johnny Alien]

I find Rivendells sizing based on PBH to oversimplify getting a good bike 
fit. They are very smart but they also have their preferences and I think 
most of the time their suggestions lean on that preference more than it 
should. The smaller size will be way easier to fit with drops if you really 
think that will be something you want to do. I agree that you "could" make 
a larger one work too but IMO its easier to get a sweptback setup to work 
on a smaller frame than it is to get a dropdown setup to work on a frame 
thats a touch big. If it were me and I rode a 57 and was comfortable on it 
with sweptback bars then I would go for that one. BUT the best situation is 
to find a 60 and give it a ride.

On Monday, May 6, 2024 at 7:56:00 AM UTC-4 Tim Bantham wrote:

> My recommendation is to go with the 60 Sam.  You said you want to ride 
> with swept back bars and use it for mostly commuting and general riding. 
> Based on your described use case I'd say go with the 60 all day long. If 
> someday you want to ride the Sam with drops you could still do so with a 
> short stem. 
>
> My PBH is 93.5. I ride a 62 Sam and a 58 MIT Homer. The only reason I 
> sized down was because my focus for the Homer was going to be a drop bar 
> road bike for sporty riding. The 61.5 Homer would have been too much reach 
> for my situation. 
>
>
>
> On Monday, May 6, 2024 at 2:06:45 AM UTC-4 David B wrote:
>
>> Hey all, first time posting here. I'm planning on grabbing a Sam 
>> Hillborne frameset when they go on sale this month. It'll be my first 
>> Rivendell. I decided on the Hillborne as a replacement for my 56cm Cross 
>> Check, which has never been comfortable for me. The short headtube puts the 
>> bars too far below my saddle.
>>
>> I have a pair of Billie bars I'd like to put on the Hillborne for daily 
>> commuting, grocery getting, and some light off road riding. I'd also like 
>> to have the option to use drop bars at some point down the line.
>>
>> I went to the Rivendell shop a few weeks ago to test ride a few bikes and 
>> get sized. I'm 6' with a 92 PBH (long legs, short torso), and based on the 
>> Sam geo chart, my PBH puts me firmly in the size 60 Sam range. They didn't 
>> have a 60 Hillborne around, so I instead rode a 57 Sam and a couple of 61.5 
>> Homers with different cockpit setups. 
>>
>>- The 57 Sam was set up with wide, swept back bars (Ron's Ortho bars) 
>>and was comfortable. We did have to raise the seatpost up pretty high to 
>>get the saddle in a good position.
>>- The first 61.5 Homer was set up with Billie bars and was also 
>>comfortable. The saddle was pretty close to the top tube, however - there 
>>was maybe a little less than a fistful of seatpost showing.
>>- The second 61.5 Homer with drops made me feel a little stretched 
>>out. The saddle was raised up higher than ideal for my height, but the 
>> bike 
>>belonged to a staff member who wasn't around that day, and so we didn't 
>>adjust the saddle position. Part of me thinks it might have worked with a 
>>lower saddle, shorter stem, and higher bars, but I'm not totally sure.
>>
>> I left feeling like a 60 Sam would work for me, but I'm now second 
>> guessing whether it makes more sense to go down to the 57 for a shorter top 
>> tube length. However, the size 57 Sam has a suggested PBH range of 86-89, 
>> which is 3cm lower than my PBH of 92. 
>>
>> Could anyone share if you've had a similar experience being in-between 
>> sizes for a Sam Hillborne, and how the size you chose worked out? Or better 
>> yet, is there anyone near Berkeley who has a 57cm or 60cm Hillborne you'd 
>> let me test ride to nail down my size? I'd be happy to buy you a beer or 
>> some other beverage as a thank you!
>>
>> David
>> Berkeley, 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/71cee5ce-ea96-4fa3-b237-b355e17330ben%40googlegroups.com.

[RBW] Re: Lugged Roadini and Charlie H Gallup

[Johnny Alien]

I'm curious about the whole lugged Roadini thing now. The Susie I 
understand because its a cost/time of manufacture thing but in the case of 
the Roadini it basically is just upping the cost. Unless the feeling is 
that a lugged model will just sell better regardless of a higher price.

On Sunday, May 5, 2024 at 3:35:27 PM UTC-4 Tim Bantham wrote:

> I saw the mention of the lugged Roadini. I am 99% certain I will order one 
> once they become available. 
>
> On Sunday, May 5, 2024 at 3:17:24 PM UTC-4 Joe Bernard wrote:
>
>> "Your friend would be *more* thrilled if this bike was coming in July or 
>> something. Like, during riding season!"
>>
>> I concede that this would be better!
>>
>> On Sunday, May 5, 2024 at 10:12:37 AM UTC-7 Bicycle Belle Ding Ding! 
>> wrote:
>>
>>> Your friend would be *more* thrilled if this bike was coming in July or 
>>> something. Like, during riding season!
>>>
>>> On Sunday, May 5, 2024 at 12:22:45 PM UTC-4 Joe Bernard wrote:
>>>
 Doug, 

 My understanding (which may be wrong, my memory for stuff I read a 
 while ago seems to have left me as I recently approached my 62nd birthday) 
 is the CHG will also be lugged and probably not cheap. It will be 
 longer-stayed than the Roadini. It's coming September! I know at least one 
 friend of ours who will be thrilled with this news. 

 Joe Bernard 

 On Sunday, May 5, 2024 at 9:04:26 AM UTC-7 Doug H. wrote:

> Grant's most recent Blahg mentioned the frame schedule and the 
> upcoming *Lugged *Roadini. It seems the Charlie H Gallup may replace 
> the Roadini as the partially lugged more affordable road bike. I 
> appreciate 
> the cream colored head tubes and full lugs but I also really like my 
> solid 
> Mermaid Roadini so I don't feel like I'm missing out. 
>
> Will the Charlie H Gallup be longer than the Roadini? If so, I do 
> think it might work better for me but we shall see. For those waiting for 
> the CHG, Grant lists them as coming in September.
>
> Doug
>


-- 
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/3f5dfb99-e191-4bff-98b2-ec6e3cf64dc1n%40googlegroups.com.

[RBW] Re: Lugged Roadini and Charlie H Gallup

[Johnny Alien]

You are not. I just peeked again and thats 100% what it says.

On Sunday, May 5, 2024 at 12:33:35 PM UTC-4 Doug H. wrote:

> I hope I'm not spreading misinformation but in Grant's latest Blahg he 
> mentions a Lugged Roadini in October. Does that mean fully lugged? It think 
> so but not 100% sure. This Blahg is loaded with good stuff too if you 
> haven't seen it check it out.
> Doug
>
> On Sunday, May 5, 2024 at 12:29:25 PM UTC-4 Johnny Alien wrote:
>
>> Waitlugged Roadini?? I thought you just messed up and meant Susie. 
>> There is a lugged Roadini coming? Has that been discussed before?
>>
>>

-- 
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/3ee610a5-5c04-42b5-b8a1-3ea0a1584487n%40googlegroups.com.

[RBW] Re: Lugged Roadini and Charlie H Gallup

[Johnny Alien]

Waitlugged Roadini?? I thought you just messed up and meant Susie. 
There is a lugged Roadini coming? Has that been discussed before?

-- 
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/17fcc908-e33d-4b50-9d58-4b2ad7ddafacn%40googlegroups.com.

[RBW] Re: Lugged Roadini and Charlie H Gallup

[Johnny Alien]

Man I wish I could edit posts here. My typing is terrible and my review 
skills are poor.

On Sunday, May 5, 2024 at 12:26:24 PM UTC-4 Johnny Alien wrote:

> I think the Gallop is going to be fully lugged correct? The geometry is 
> probably pretty close through the iterations but visually its very 
> different than how it started. Its been quite some time since they offered 
> a fully lugged road frame I standard production. I prefer the swoop and 
> canti posts BUT it looks really nice and I still appreciate the angled top 
> tube. They say its designed for sweptback but can handle drops. I think 
> they should just lean in hard one way or the other. I have mine set up with 
> sweptback because I feel like thats where it was supposed to go. But also 
> interesting is that means there is no road focused drop by bike in the 
> standard lineup. At least not designed to be so. I think that the Gallop 
> and Roadini could co-exist with the Roadini being more affordable and 100% 
> road focused with drops. I don't think thats what is happening though, I 
> think the Roadini is goin away for now.
>
>
> On Sunday, May 5, 2024 at 12:06:38 PM UTC-4 captaincon...@gmail.com wrote:
>
>> Throw some Canti posts on the Roadini while they are brazing, and I'm a 
>> buyer.
>>
>> On Sunday, May 5, 2024 at 11:04:26 AM UTC-5 Doug H. wrote:
>>
>>> Grant's most recent Blahg mentioned the frame schedule and the upcoming 
>>> *Lugged 
>>> *Roadini. It seems the Charlie H Gallup may replace the Roadini as the 
>>> partially lugged more affordable road bike. I appreciate the cream colored 
>>> head tubes and full lugs but I also really like my solid Mermaid Roadini so 
>>> I don't feel like I'm missing out. 
>>>
>>> Will the Charlie H Gallup be longer than the Roadini? If so, I do think 
>>> it might work better for me but we shall see. For those waiting for the 
>>> CHG, Grant lists them as coming in September.
>>>
>>> Doug
>>>
>>

-- 
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/247600d4-6456-4c7d-95f7-3ff89506a58fn%40googlegroups.com.

[RBW] Re: Lugged Roadini and Charlie H Gallup

[Johnny Alien]

I think the Gallop is going to be fully lugged correct? The geometry is 
probably pretty close through the iterations but visually its very 
different than how it started. Its been quite some time since they offered 
a fully lugged road frame I standard production. I prefer the swoop and 
canti posts BUT it looks really nice and I still appreciate the angled top 
tube. They say its designed for sweptback but can handle drops. I think 
they should just lean in hard one way or the other. I have mine set up with 
sweptback because I feel like thats where it was supposed to go. But also 
interesting is that means there is no road focused drop by bike in the 
standard lineup. At least not designed to be so. I think that the Gallop 
and Roadini could co-exist with the Roadini being more affordable and 100% 
road focused with drops. I don't think thats what is happening though, I 
think the Roadini is goin away for now.


On Sunday, May 5, 2024 at 12:06:38 PM UTC-4 captaincon...@gmail.com wrote:

> Throw some Canti posts on the Roadini while they are brazing, and I'm a 
> buyer.
>
> On Sunday, May 5, 2024 at 11:04:26 AM UTC-5 Doug H. wrote:
>
>> Grant's most recent Blahg mentioned the frame schedule and the upcoming 
>> *Lugged 
>> *Roadini. It seems the Charlie H Gallup may replace the Roadini as the 
>> partially lugged more affordable road bike. I appreciate the cream colored 
>> head tubes and full lugs but I also really like my solid Mermaid Roadini so 
>> I don't feel like I'm missing out. 
>>
>> Will the Charlie H Gallup be longer than the Roadini? If so, I do think 
>> it might work better for me but we shall see. For those waiting for the 
>> CHG, Grant lists them as coming in September.
>>
>> Doug
>>
>

-- 
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/58b0b146-3886-4cad-9987-36730d898f16n%40googlegroups.com.

[jira] [Commented] (KAFKA-16668) Enable to set tags by `ClusterTest`

[Johnny Hsu (Jira)]

[ 
https://issues.apache.org/jira/browse/KAFKA-16668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17843482#comment-17843482
 ] 

Johnny Hsu commented on KAFKA-16668:


hi [~chia7712] 
may I know if you are working on this? if not I am willing to help, thanks!

> Enable to set tags by `ClusterTest` 
> 
>
> Key: KAFKA-16668
> URL: https://issues.apache.org/jira/browse/KAFKA-16668
> Project: Kafka
>  Issue Type: Improvement
>Reporter: Chia-Ping Tsai
>Assignee: Chia-Ping Tsai
>Priority: Minor
>
> Currently, the display name can be customized by only `name` 
> (https://github.com/apache/kafka/blob/trunk/core/src/test/java/kafka/test/annotation/ClusterTest.java#L42).
>  However, the "key" is hard-code to "name=xxx". Also, it is impossible to set 
> more "tags" for display name. 
> https://github.com/apache/kafka/pull/15766 is a example that we want to add 
> "xxx=bbb" to display name.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Comment Edited] (KAFKA-14579) Move DumpLogSegments to tools

[Johnny Hsu (Jira)]

[ 
https://issues.apache.org/jira/browse/KAFKA-14579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17843421#comment-17843421
 ] 

Johnny Hsu edited comment on KAFKA-14579 at 5/4/24 10:36 AM:
-

currently only DumpLogSegments is using Decoder, if it's removed then Decoder 
should be safe to be deprecated since no one will be using that anymore.
I am willing to work on the KIP for this


was (Author: JIRAUSER304478):
currently only DumpLogSegments is using Decoder, if it's removed then Decoder 
should be safe to be deprecated since no one will be using that anymore.
I am willing to work on the KIP for this :) 

> Move DumpLogSegments to tools
> -
>
> Key: KAFKA-14579
> URL: https://issues.apache.org/jira/browse/KAFKA-14579
> Project: Kafka
>  Issue Type: Sub-task
>Reporter: Mickael Maison
>Assignee: Alexandre Dupriez
>Priority: Major
>




--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Comment Edited] (KAFKA-14579) Move DumpLogSegments to tools

[Johnny Hsu (Jira)]

[ 
https://issues.apache.org/jira/browse/KAFKA-14579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17843421#comment-17843421
 ] 

Johnny Hsu edited comment on KAFKA-14579 at 5/4/24 10:36 AM:
-

currently only DumpLogSegments is using Decoder, if it's removed then Decoder 
should be safe to be deprecated since no one will be using that anymore.
I am willing to work on the KIP for this :) 


was (Author: JIRAUSER304478):
currently only DumpLogSegments is using Decoder, if it's removed then Decoder 
should be safe to be deprecated since no one will be using that anymore 

> Move DumpLogSegments to tools
> -
>
> Key: KAFKA-14579
> URL: https://issues.apache.org/jira/browse/KAFKA-14579
> Project: Kafka
>  Issue Type: Sub-task
>Reporter: Mickael Maison
>Assignee: Alexandre Dupriez
>Priority: Major
>




--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Commented] (KAFKA-14579) Move DumpLogSegments to tools

[Johnny Hsu (Jira)]

[ 
https://issues.apache.org/jira/browse/KAFKA-14579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17843421#comment-17843421
 ] 

Johnny Hsu commented on KAFKA-14579:


currently only DumpLogSegments is using Decoder, if it's removed then Decoder 
should be safe to be deprecated since no one will be using that anymore 

> Move DumpLogSegments to tools
> -
>
> Key: KAFKA-14579
> URL: https://issues.apache.org/jira/browse/KAFKA-14579
> Project: Kafka
>  Issue Type: Sub-task
>Reporter: Mickael Maison
>Assignee: Alexandre Dupriez
>Priority: Major
>




--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Comment Edited] (KAFKA-16174) Flaky test: testDescribeQuorumStatusSuccessful – org.apache.kafka.tools.MetadataQuorumCommandTest

[Johnny Hsu (Jira)]

[ 
https://issues.apache.org/jira/browse/KAFKA-16174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17843403#comment-17843403
 ] 

Johnny Hsu edited comment on KAFKA-16174 at 5/4/24 8:21 AM:


the exception is from 
[https://github.com/apache/kafka/blob/9b8aac22ec7ce927a2ceb2bfe7afd57419ee946c/core/src/main/scala/kafka/server/BrokerServer.scala#L474]

when the cluster starts, 
[https://github.com/apache/kafka/blob/9b8aac22ec7ce927a2ceb2bfe7afd57419ee946c/core/src/test/java/kafka/testkit/KafkaClusterTestKit.java#L426]
 tries to init broker, but it failed to get the response from controller 


was (Author: JIRAUSER304478):
the exception is from 
[https://github.com/apache/kafka/blob/9b8aac22ec7ce927a2ceb2bfe7afd57419ee946c/core/src/main/scala/kafka/server/BrokerServer.scala#L474]

when the cluster starts, 
[https://github.com/apache/kafka/blob/9b8aac22ec7ce927a2ceb2bfe7afd57419ee946c/core/src/test/java/kafka/testkit/KafkaClusterTestKit.java#L426]
 tries to init broker, but it failed. 

> Flaky test: testDescribeQuorumStatusSuccessful – 
> org.apache.kafka.tools.MetadataQuorumCommandTest
> -
>
> Key: KAFKA-16174
> URL: https://issues.apache.org/jira/browse/KAFKA-16174
> Project: Kafka
>  Issue Type: Test
>Reporter: Apoorv Mittal
>Assignee: Johnny Hsu
>Priority: Major
>  Labels: flaky-test
>
> [https://ci-builds.apache.org/blue/organizations/jenkins/Kafka%2Fkafka-pr/detail/PR-15190/3/tests/]
>  
> {code:java}
> Errorjava.util.concurrent.ExecutionException: java.lang.RuntimeException: 
> Received a fatal error while waiting for the controller to acknowledge that 
> we are caught upStacktracejava.util.concurrent.ExecutionException: 
> java.lang.RuntimeException: Received a fatal error while waiting for the 
> controller to acknowledge that we are caught up at 
> java.base/java.util.concurrent.FutureTask.report(FutureTask.java:122)
> at java.base/java.util.concurrent.FutureTask.get(FutureTask.java:191)   at 
> kafka.testkit.KafkaClusterTestKit.startup(KafkaClusterTestKit.java:421)  
> at 
> kafka.test.junit.RaftClusterInvocationContext.lambda$getAdditionalExtensions$5(RaftClusterInvocationContext.java:116)
> at 
> org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.lambda$invokeBeforeTestExecutionCallbacks$5(TestMethodTestDescriptor.java:192)
>   at 
> org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.lambda$invokeBeforeMethodsOrCallbacksUntilExceptionOccurs$6(TestMethodTestDescriptor.java:203)
>   at 
> org.junit.platform.engine.support.hierarchical.ThrowableCollector.execute(ThrowableCollector.java:73)
> at 
> org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.invokeBeforeMethodsOrCallbacksUntilExceptionOccurs(TestMethodTestDescriptor.java:203)
>at 
> org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.invokeBeforeTestExecutionCallbacks(TestMethodTestDescriptor.java:191)
>at 
> org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.execute(TestMethodTestDescriptor.java:137)
>   at 
> org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.execute(TestMethodTestDescriptor.java:69)
>at 
> org.junit.platform.engine.support.hierarchical.NodeTestTask.lambda$executeRecursively$6(NodeTestTask.java:151)
>at 
> org.junit.platform.engine.support.hierarchical.ThrowableCollector.execute(ThrowableCollector.java:73)
> at 
> org.junit.platform.engine.support.hierarchical.NodeTestTask.lambda$executeRecursively$8(NodeTestTask.java:141)
>at 
> org.junit.platform.engine.support.hierarchical.Node.around(Node.java:137)
> at 
> org.junit.platform.engine.support.hierarchical.NodeTestTask.lambda$executeRecursively$9(NodeTestTask.java:139)
>at 
> org.junit.platform.engine.support.hierarchical.ThrowableCollector.execute(ThrowableCollector.java:73)
> at 
> org.junit.platform.engine.support.hierarchical.NodeTestTask.executeRecursively(NodeTestTask.java:138)
> at 
> org.junit.platform.engine.support.hierarchical.NodeTestTask.execute(NodeTestTask.java:95)
> at 
> org.junit.platform.engine.support.hierarchical.SameThreadHierarchicalTestExecutorService.submit(SameThreadHierarchicalTestExecutorService.java:35)
>at 
> org.junit.platform.engine.support.hierarchical.NodeTestTask$DefaultDynamicTestExecutor.execute(NodeTestTask.java:226)
> at 
> org.junit.platform.engine.support.hierarchical.NodeTestTask$DefaultDynamicTestExecutor.execute(NodeTestTask.java:204)
>  {code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Commented] (KAFKA-16174) Flaky test: testDescribeQuorumStatusSuccessful – org.apache.kafka.tools.MetadataQuorumCommandTest

[Johnny Hsu (Jira)]

[ 
https://issues.apache.org/jira/browse/KAFKA-16174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17843403#comment-17843403
 ] 

Johnny Hsu commented on KAFKA-16174:


the exception is from 
[https://github.com/apache/kafka/blob/9b8aac22ec7ce927a2ceb2bfe7afd57419ee946c/core/src/main/scala/kafka/server/BrokerServer.scala#L474]

when the cluster starts, 
[https://github.com/apache/kafka/blob/9b8aac22ec7ce927a2ceb2bfe7afd57419ee946c/core/src/test/java/kafka/testkit/KafkaClusterTestKit.java#L426]
 tries to init broker, but it failed. 

> Flaky test: testDescribeQuorumStatusSuccessful – 
> org.apache.kafka.tools.MetadataQuorumCommandTest
> -
>
> Key: KAFKA-16174
> URL: https://issues.apache.org/jira/browse/KAFKA-16174
> Project: Kafka
>  Issue Type: Test
>Reporter: Apoorv Mittal
>Assignee: Johnny Hsu
>Priority: Major
>  Labels: flaky-test
>
> [https://ci-builds.apache.org/blue/organizations/jenkins/Kafka%2Fkafka-pr/detail/PR-15190/3/tests/]
>  
> {code:java}
> Errorjava.util.concurrent.ExecutionException: java.lang.RuntimeException: 
> Received a fatal error while waiting for the controller to acknowledge that 
> we are caught upStacktracejava.util.concurrent.ExecutionException: 
> java.lang.RuntimeException: Received a fatal error while waiting for the 
> controller to acknowledge that we are caught up at 
> java.base/java.util.concurrent.FutureTask.report(FutureTask.java:122)
> at java.base/java.util.concurrent.FutureTask.get(FutureTask.java:191)   at 
> kafka.testkit.KafkaClusterTestKit.startup(KafkaClusterTestKit.java:421)  
> at 
> kafka.test.junit.RaftClusterInvocationContext.lambda$getAdditionalExtensions$5(RaftClusterInvocationContext.java:116)
> at 
> org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.lambda$invokeBeforeTestExecutionCallbacks$5(TestMethodTestDescriptor.java:192)
>   at 
> org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.lambda$invokeBeforeMethodsOrCallbacksUntilExceptionOccurs$6(TestMethodTestDescriptor.java:203)
>   at 
> org.junit.platform.engine.support.hierarchical.ThrowableCollector.execute(ThrowableCollector.java:73)
> at 
> org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.invokeBeforeMethodsOrCallbacksUntilExceptionOccurs(TestMethodTestDescriptor.java:203)
>at 
> org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.invokeBeforeTestExecutionCallbacks(TestMethodTestDescriptor.java:191)
>at 
> org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.execute(TestMethodTestDescriptor.java:137)
>   at 
> org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.execute(TestMethodTestDescriptor.java:69)
>at 
> org.junit.platform.engine.support.hierarchical.NodeTestTask.lambda$executeRecursively$6(NodeTestTask.java:151)
>at 
> org.junit.platform.engine.support.hierarchical.ThrowableCollector.execute(ThrowableCollector.java:73)
> at 
> org.junit.platform.engine.support.hierarchical.NodeTestTask.lambda$executeRecursively$8(NodeTestTask.java:141)
>at 
> org.junit.platform.engine.support.hierarchical.Node.around(Node.java:137)
> at 
> org.junit.platform.engine.support.hierarchical.NodeTestTask.lambda$executeRecursively$9(NodeTestTask.java:139)
>at 
> org.junit.platform.engine.support.hierarchical.ThrowableCollector.execute(ThrowableCollector.java:73)
> at 
> org.junit.platform.engine.support.hierarchical.NodeTestTask.executeRecursively(NodeTestTask.java:138)
> at 
> org.junit.platform.engine.support.hierarchical.NodeTestTask.execute(NodeTestTask.java:95)
> at 
> org.junit.platform.engine.support.hierarchical.SameThreadHierarchicalTestExecutorService.submit(SameThreadHierarchicalTestExecutorService.java:35)
>at 
> org.junit.platform.engine.support.hierarchical.NodeTestTask$DefaultDynamicTestExecutor.execute(NodeTestTask.java:226)
> at 
> org.junit.platform.engine.support.hierarchical.NodeTestTask$DefaultDynamicTestExecutor.execute(NodeTestTask.java:204)
>  {code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Assigned] (KAFKA-16174) Flaky test: testDescribeQuorumStatusSuccessful – org.apache.kafka.tools.MetadataQuorumCommandTest

[Johnny Hsu (Jira)]

 [ 
https://issues.apache.org/jira/browse/KAFKA-16174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Johnny Hsu reassigned KAFKA-16174:
--

Assignee: Johnny Hsu

> Flaky test: testDescribeQuorumStatusSuccessful – 
> org.apache.kafka.tools.MetadataQuorumCommandTest
> -
>
> Key: KAFKA-16174
> URL: https://issues.apache.org/jira/browse/KAFKA-16174
> Project: Kafka
>  Issue Type: Test
>Reporter: Apoorv Mittal
>Assignee: Johnny Hsu
>Priority: Major
>  Labels: flaky-test
>
> [https://ci-builds.apache.org/blue/organizations/jenkins/Kafka%2Fkafka-pr/detail/PR-15190/3/tests/]
>  
> {code:java}
> Errorjava.util.concurrent.ExecutionException: java.lang.RuntimeException: 
> Received a fatal error while waiting for the controller to acknowledge that 
> we are caught upStacktracejava.util.concurrent.ExecutionException: 
> java.lang.RuntimeException: Received a fatal error while waiting for the 
> controller to acknowledge that we are caught up at 
> java.base/java.util.concurrent.FutureTask.report(FutureTask.java:122)
> at java.base/java.util.concurrent.FutureTask.get(FutureTask.java:191)   at 
> kafka.testkit.KafkaClusterTestKit.startup(KafkaClusterTestKit.java:421)  
> at 
> kafka.test.junit.RaftClusterInvocationContext.lambda$getAdditionalExtensions$5(RaftClusterInvocationContext.java:116)
> at 
> org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.lambda$invokeBeforeTestExecutionCallbacks$5(TestMethodTestDescriptor.java:192)
>   at 
> org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.lambda$invokeBeforeMethodsOrCallbacksUntilExceptionOccurs$6(TestMethodTestDescriptor.java:203)
>   at 
> org.junit.platform.engine.support.hierarchical.ThrowableCollector.execute(ThrowableCollector.java:73)
> at 
> org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.invokeBeforeMethodsOrCallbacksUntilExceptionOccurs(TestMethodTestDescriptor.java:203)
>at 
> org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.invokeBeforeTestExecutionCallbacks(TestMethodTestDescriptor.java:191)
>at 
> org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.execute(TestMethodTestDescriptor.java:137)
>   at 
> org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.execute(TestMethodTestDescriptor.java:69)
>at 
> org.junit.platform.engine.support.hierarchical.NodeTestTask.lambda$executeRecursively$6(NodeTestTask.java:151)
>at 
> org.junit.platform.engine.support.hierarchical.ThrowableCollector.execute(ThrowableCollector.java:73)
> at 
> org.junit.platform.engine.support.hierarchical.NodeTestTask.lambda$executeRecursively$8(NodeTestTask.java:141)
>at 
> org.junit.platform.engine.support.hierarchical.Node.around(Node.java:137)
> at 
> org.junit.platform.engine.support.hierarchical.NodeTestTask.lambda$executeRecursively$9(NodeTestTask.java:139)
>at 
> org.junit.platform.engine.support.hierarchical.ThrowableCollector.execute(ThrowableCollector.java:73)
> at 
> org.junit.platform.engine.support.hierarchical.NodeTestTask.executeRecursively(NodeTestTask.java:138)
> at 
> org.junit.platform.engine.support.hierarchical.NodeTestTask.execute(NodeTestTask.java:95)
> at 
> org.junit.platform.engine.support.hierarchical.SameThreadHierarchicalTestExecutorService.submit(SameThreadHierarchicalTestExecutorService.java:35)
>at 
> org.junit.platform.engine.support.hierarchical.NodeTestTask$DefaultDynamicTestExecutor.execute(NodeTestTask.java:226)
> at 
> org.junit.platform.engine.support.hierarchical.NodeTestTask$DefaultDynamicTestExecutor.execute(NodeTestTask.java:204)
>  {code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Commented] (KAFKA-16174) Flaky test: testDescribeQuorumStatusSuccessful – org.apache.kafka.tools.MetadataQuorumCommandTest

[Johnny Hsu (Jira)]

[ 
https://issues.apache.org/jira/browse/KAFKA-16174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17843155#comment-17843155
 ] 

Johnny Hsu commented on KAFKA-16174:


[~apoorvmittal10] may I know if you are working on this ticket? if not I am 
willing to help :) 

> Flaky test: testDescribeQuorumStatusSuccessful – 
> org.apache.kafka.tools.MetadataQuorumCommandTest
> -
>
> Key: KAFKA-16174
> URL: https://issues.apache.org/jira/browse/KAFKA-16174
> Project: Kafka
>  Issue Type: Test
>Reporter: Apoorv Mittal
>Priority: Major
>  Labels: flaky-test
>
> [https://ci-builds.apache.org/blue/organizations/jenkins/Kafka%2Fkafka-pr/detail/PR-15190/3/tests/]
>  
> {code:java}
> Errorjava.util.concurrent.ExecutionException: java.lang.RuntimeException: 
> Received a fatal error while waiting for the controller to acknowledge that 
> we are caught upStacktracejava.util.concurrent.ExecutionException: 
> java.lang.RuntimeException: Received a fatal error while waiting for the 
> controller to acknowledge that we are caught up at 
> java.base/java.util.concurrent.FutureTask.report(FutureTask.java:122)
> at java.base/java.util.concurrent.FutureTask.get(FutureTask.java:191)   at 
> kafka.testkit.KafkaClusterTestKit.startup(KafkaClusterTestKit.java:421)  
> at 
> kafka.test.junit.RaftClusterInvocationContext.lambda$getAdditionalExtensions$5(RaftClusterInvocationContext.java:116)
> at 
> org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.lambda$invokeBeforeTestExecutionCallbacks$5(TestMethodTestDescriptor.java:192)
>   at 
> org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.lambda$invokeBeforeMethodsOrCallbacksUntilExceptionOccurs$6(TestMethodTestDescriptor.java:203)
>   at 
> org.junit.platform.engine.support.hierarchical.ThrowableCollector.execute(ThrowableCollector.java:73)
> at 
> org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.invokeBeforeMethodsOrCallbacksUntilExceptionOccurs(TestMethodTestDescriptor.java:203)
>at 
> org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.invokeBeforeTestExecutionCallbacks(TestMethodTestDescriptor.java:191)
>at 
> org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.execute(TestMethodTestDescriptor.java:137)
>   at 
> org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.execute(TestMethodTestDescriptor.java:69)
>at 
> org.junit.platform.engine.support.hierarchical.NodeTestTask.lambda$executeRecursively$6(NodeTestTask.java:151)
>at 
> org.junit.platform.engine.support.hierarchical.ThrowableCollector.execute(ThrowableCollector.java:73)
> at 
> org.junit.platform.engine.support.hierarchical.NodeTestTask.lambda$executeRecursively$8(NodeTestTask.java:141)
>at 
> org.junit.platform.engine.support.hierarchical.Node.around(Node.java:137)
> at 
> org.junit.platform.engine.support.hierarchical.NodeTestTask.lambda$executeRecursively$9(NodeTestTask.java:139)
>at 
> org.junit.platform.engine.support.hierarchical.ThrowableCollector.execute(ThrowableCollector.java:73)
> at 
> org.junit.platform.engine.support.hierarchical.NodeTestTask.executeRecursively(NodeTestTask.java:138)
> at 
> org.junit.platform.engine.support.hierarchical.NodeTestTask.execute(NodeTestTask.java:95)
> at 
> org.junit.platform.engine.support.hierarchical.SameThreadHierarchicalTestExecutorService.submit(SameThreadHierarchicalTestExecutorService.java:35)
>at 
> org.junit.platform.engine.support.hierarchical.NodeTestTask$DefaultDynamicTestExecutor.execute(NodeTestTask.java:226)
> at 
> org.junit.platform.engine.support.hierarchical.NodeTestTask$DefaultDynamicTestExecutor.execute(NodeTestTask.java:204)
>  {code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[GSoC] Introduction to the KDE projects and contributors!

[Johnny Jazeix]

Hi,

The KDE contributions for this year GSoC are finally known since yesterday!
Carl wrote a nice blog post summing up what will the contributors work on
during the next months: https://mentorship.kde.org/blog/2024-05-gsoc-2024/

For mentors, please ensure you are in the kde-soc-mentor mailing list (
https://mail.kde.org/mailman/listinfo/kde-soc-mentor) and both you and your
contributors are in the kde-soc mailing list (
https://mail.kde.org/mailman/listinfo/kde-soc) where all the communication
will take place for now.

Let's have some fun this summer and welcome warmfully the new contributors!

Cheers,

Johnny for the admin team

[jira] [Commented] (KAFKA-16027) Refactor MetadataTest#testUpdatePartitionLeadership

[Johnny Hsu (Jira)]

[ 
https://issues.apache.org/jira/browse/KAFKA-16027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17842946#comment-17842946
 ] 

Johnny Hsu commented on KAFKA-16027:


[~alexanderaghili] thanks for replying!
got you, then I will close my draft and let's discuss on your PR :)

> Refactor MetadataTest#testUpdatePartitionLeadership
> ---
>
> Key: KAFKA-16027
> URL: https://issues.apache.org/jira/browse/KAFKA-16027
> Project: Kafka
>  Issue Type: Improvement
>Reporter: Philip Nee
>Assignee: Alexander Aghili
>Priority: Minor
>  Labels: newbie
>
> MetadataTest#testUpdatePartitionLeadership is extremely long.  I think it is 
> pretty close to the 160 line method limit - I tried to modfity it but it 
> would hit the limit when i tried to break things into separated lines.
> The test also contains two tests, so it is best to split it into two separate 
> tests.
> We should also move this to ConsumerMetadata.java



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[RBW] Re: Drops vs albatross. Easy to swap or do I need two bikes?

[Johnny Alien]

Let me suggest that you get yourself some albastache bars. I think you 
would feel comfortable in all of your scenarios with those handlebars. They 
are the secret weapon in Rivendell's offerings.

On Wednesday, May 1, 2024 at 8:14:04 AM UTC-4 erik.s...@gmail.com wrote:

>
> Answering on the practical side (easily swapping handlebars) rather than 
> the “should I own two bikes” side of things, Russ from Path Less Pedaled 
> did a video a while back on optimizing 1 bike for easy cockpit swaps. 
> Basically using a little Jagwire cable splitting doodad so the cables and 
> housing can mostly stay in place when swapping bars. It makes more sense if 
> your bike has full-length housing, but there may still be some nuggets in 
> there that are helpful.
>
> https://youtu.be/qj0qOyw_Es8?si=wKDJKxwHhdtKdBg0
>
> Could be a good in-between option while you’re building up your second 
> bike ;)
>
> Erik, Philly
> On Wednesday, May 1, 2024 at 2:23:08 AM UTC-4 Michael wrote:
>
>> Looking for a single bike for casual rides on bike 
>> paths/paved/gravel/dirt roads with the occasional 100 mile ride thrown in. 
>> Will suggest the Sam Hillborne, which I'm leaning towards. I assumed I 
>> would build it with drops for the long rides but I recently fell in love 
>> with albatross bars for upright lazy bike path rides. 
>> Is there a way to quickly/easily swap handlebars or are two bikes 
>> inevitable? 
>> Would a Sam with drops and an appaloosa or atlantis w/ albatross be a 
>> good combo or is that too much overlap? 
>>
>>

-- 
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/919317fc-6edc-4f19-81a1-f8f60184bf03n%40googlegroups.com.

[jira] [Commented] (KAFKA-16027) Refactor MetadataTest#testUpdatePartitionLeadership

[Johnny Hsu (Jira)]

[ 
https://issues.apache.org/jira/browse/KAFKA-16027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17842537#comment-17842537
 ] 

Johnny Hsu commented on KAFKA-16027:


hey [~alexanderaghili] may I know if we have any updates on this?
I am happy to help if you are busy with something else :) 

> Refactor MetadataTest#testUpdatePartitionLeadership
> ---
>
> Key: KAFKA-16027
> URL: https://issues.apache.org/jira/browse/KAFKA-16027
> Project: Kafka
>  Issue Type: Improvement
>Reporter: Philip Nee
>Assignee: Alexander Aghili
>Priority: Minor
>  Labels: newbie
>
> MetadataTest#testUpdatePartitionLeadership is extremely long.  I think it is 
> pretty close to the 160 line method limit - I tried to modfity it but it 
> would hit the limit when i tried to break things into separated lines.
> The test also contains two tests, so it is best to split it into two separate 
> tests.
> We should also move this to ConsumerMetadata.java



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Commented] (KAFKA-16553) log controller configs when startup

[Johnny Hsu (Jira)]

[ 
https://issues.apache.org/jira/browse/KAFKA-16553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17842011#comment-17842011
 ] 

Johnny Hsu commented on KAFKA-16553:


hey [~chia7712] , I would like to address this first with the current approach, 
and refactor this part after the changes in 13105, so that we can get this 
controller log first. wdyt?

> log controller configs when startup
> ---
>
> Key: KAFKA-16553
> URL: https://issues.apache.org/jira/browse/KAFKA-16553
> Project: Kafka
>  Issue Type: Improvement
>Reporter: Chia-Ping Tsai
>Assignee: Chia-Ping Tsai
>Priority: Minor
>
> We can't observe the controller configs from the log file. We can copy the 
> solution used by broker 
> (https://github.com/apache/kafka/blob/trunk/core/src/main/scala/kafka/server/BrokerServer.scala#L492).
> Or this issue should be blocked by 
> https://issues.apache.org/jira/browse/KAFKA-13105 to wait for more graceful 
> solution.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[RBW] Re: Bridgestone ride - 1st in a decade

[Johnny Alien]

That's a 92 right? Grant has said that he considers that to be the peak of 
the RB bikes. I have not ridden one so have no comment on that BUT I will 
say that the color scheme is the peak of RB bikes for me. Yellow and 
white??? Chef's kiss.

On Monday, April 29, 2024 at 8:33:47 AM UTC-4 Art wrote:

> It's been over 10 years since I did a ride on my Bridgestone RB-1. 
> Yesterday afternoon was quite lovely in northern NJ so I decided to take a 
> quick spin. It felt good to be back on the bike and although it was a 
> relatively short ride, it was fun and invigorating.
> I expect more ride in the near future.
> .Art
>
> [image: RB-1 _240429 IMG_2281.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/8c87bbea-07be-432f-8122-83697acc7231n%40googlegroups.com.

[jira] [Commented] (KAFKA-15897) Flaky Test: testWrongIncarnationId() – kafka.server.ControllerRegistrationManagerTest

[Johnny Hsu (Jira)]

[ 
https://issues.apache.org/jira/browse/KAFKA-15897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17841998#comment-17841998
 ] 

Johnny Hsu commented on KAFKA-15897:


previously I thought that the poll should be fine, since the 
`rpcStats(manager)` always returns the current status of the manager, which 
means that no matter whether there are race conditions or not, if the 
prepareResponseFrom was executed before the second poll, it should not fail. 
However, actually there is another event queue thread which append the request. 
Thus, if there are race conditions between the first and second poll, this 
could lead to the second poll failing, because the request could be taken away 
by the first poll.

Thanks [~chia7712] for the through discussion, I am willing to fix this :)

> Flaky Test: testWrongIncarnationId() – 
> kafka.server.ControllerRegistrationManagerTest
> -
>
> Key: KAFKA-15897
> URL: https://issues.apache.org/jira/browse/KAFKA-15897
> Project: Kafka
>  Issue Type: Test
>Reporter: Apoorv Mittal
>Assignee: Chia-Ping Tsai
>Priority: Major
>  Labels: flaky-test
>
> Build run: 
> https://ci-builds.apache.org/blue/organizations/jenkins/Kafka%2Fkafka-pr/detail/PR-14699/21/tests/
>  
> {code:java}
> org.opentest4j.AssertionFailedError: expected: <(false,1,0)> but was: 
> <(true,0,0)>Stacktraceorg.opentest4j.AssertionFailedError: expected: 
> <(false,1,0)> but was: <(true,0,0)>at 
> app//org.junit.jupiter.api.AssertionFailureBuilder.build(AssertionFailureBuilder.java:151)
>at 
> app//org.junit.jupiter.api.AssertionFailureBuilder.buildAndThrow(AssertionFailureBuilder.java:132)
>at 
> app//org.junit.jupiter.api.AssertEquals.failNotEqual(AssertEquals.java:197)  
> at 
> app//org.junit.jupiter.api.AssertEquals.assertEquals(AssertEquals.java:182)  
> at 
> app//org.junit.jupiter.api.AssertEquals.assertEquals(AssertEquals.java:177)  
> at app//org.junit.jupiter.api.Assertions.assertEquals(Assertions.java:1141)   
>   at 
> app//kafka.server.ControllerRegistrationManagerTest.$anonfun$testWrongIncarnationId$3(ControllerRegistrationManagerTest.scala:228)
>at 
> app//org.apache.kafka.test.TestUtils.retryOnExceptionWithTimeout(TestUtils.java:379)
>  at 
> app//kafka.server.ControllerRegistrationManagerTest.testWrongIncarnationId(ControllerRegistrationManagerTest.scala:226)
>   at 
> java.base@17.0.7/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native 
> Method)at 
> java.base@17.0.7/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
>   at 
> java.base@17.0.7/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.base@17.0.7/java.lang.reflect.Method.invoke(Method.java:568)
> at 
> app//org.junit.platform.commons.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:728)
>   at 
> app//org.junit.jupiter.engine.execution.MethodInvocation.proceed(MethodInvocation.java:60)
>at 
> app//org.junit.jupiter.engine.execution.InvocationInterceptorChain$ValidatingInvocation.proceed(InvocationInterceptorChain.java:131)
>  at 
> app//org.junit.jupiter.engine.extension.SameThreadTimeoutInvocation.proceed(SameThreadTimeoutInvocation.java:45)
>  at 
> app//org.junit.jupiter.engine.extension.TimeoutExtension.intercept(TimeoutExtension.java:156)
> at 
> app//org.junit.jupiter.engine.extension.TimeoutExtension.interceptTestableMethod(TimeoutExtension.java:147)
>   at 
> app//org.junit.jupiter.engine.extension.TimeoutExtension.interceptTestMethod(TimeoutExtension.java:86)
>at 
> app//org.junit.jupiter.engine.execution.InterceptingExecutableInvoker$ReflectiveInterceptorCall.lambda$ofVoidMethod$0(InterceptingExecutableInvoker.java:103)
> at 
> app//org.junit.jupiter.engine.execution.InterceptingExecutableInvoker.lambda$invoke$0(InterceptingExecutableInvoker.java:93)
>  at 
> app//org.junit.jupiter.engine.execution.InvocationInterceptorChain$InterceptedInvocation.proceed(InvocationInterceptorChain.java:106)
> at 
> app//org.junit.jupiter.engine.execution.InvocationInterceptorChain.proceed(InvocationInterceptorChain.java:64)
>at 
> app//org.junit.jupiter.engine.execution.InvocationInterceptorChain.chainAndInvoke(InvocationInterceptorChain.java:45)
> at 
> app//org.junit.jupiter.engine.execution.InvocationInterceptorChain.invoke(InvocationInterceptorChain.java:37)
> at 
> app//org.junit.jup

Re: [RBW] Re: ISO // WTB // blue homer 54.5

[Johnny Alien]

That post says its still available as of 3 days ago but he also mentioned 
its most likely a 58 not a 54.5. The 54.5 is a 700C size.

On Sunday, April 28, 2024 at 2:03:12 AM UTC-4 Kim H. wrote:

> I tried. 
>
> Kim Hetzel. 
>
> On Sat, Apr 27, 2024, 10:59 PM Brenton Eastman  
> wrote:
>
>> That Facebook post is from Jan 2023 so I gotta assume that bike is gone. 
>> Also the head tube looks very tall for a 54. Does anyone know if there were 
>> 700c versions of AHH in 54.5?
>>
>> On Apr 27, 2024, at 9:04 PM, Kim H.  wrote:
>>
>> 
>> @Brenton -
>> If you go FACEBOOK Rivendell Bicycle BUY/SELL/TRADE, there is a blue 
>> Homer under the owner's name of 
>> *Payton Beargrr* 
>> 
>>  
>>
>> Very near mint condition A. Homer Hilsen, 54.5cm with 650b wheels. Unsure 
>> of year but it's likely 4 or less years old. Taiwanese made frame. I am not 
>> the original owner but this appears to be a Rivendell build. 
>> -Nitto handlebars, stem, and seat post
>> -Brooks saddle
>> -Paul racer brakes, Paul canti levers
>> -Paul thumbie mounts with Microshift shifters
>> -Riv Silver double crankset
>> -IRD front derailleur
>> -Shimano Alivio rear derailleur
>> -MKS Grip Monarch pedals
>> -mismatched Shimano hubs, no name rims
>> -Soma Cazadero 650 x 42b
>> -Sackville bag
>> The only imperfections are the two small paint chips on the top tube, 
>> noted in the pictures. 
>> $2500 + shipping. 
>> Let me know if you have any questions.
>>
>> Kim Hetzel.
>> On Saturday, April 27, 2024 at 8:12:21 PM UTC-7 brenton...@gmail.com 
>> wrote:
>>
>>> Looking for an AHH in Homer Blue. Not sure if older years came in sizes 
>>> other than 54.5 but that's about the size I want for my lady. Interested in 
>>> new or used, frame+fork or complete, or a semi-complete project. 
>>>
>>> Thanks!
>>>
>> -- 
>> 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/6dmIxSyf72o/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/b5976036-9ea9-4ce2-847c-ca2458c1e354n%40googlegroups.com
>>  
>> 
>> .
>>
>> -- 
>> 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/6dmIxSyf72o/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/D941A7E6-E21F-4558-9C07-E83C62D58779%40gmail.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/f9013215-de67-4548-8cca-f48b165d8521n%40googlegroups.com.

Re: [RBW] Re: WTB: Soba Handlebars

[Johnny Alien]

The Dream bar was the classic standard drop bar made for Rivendell by 
Nitto. If I remember correctly its what they offered prior to the Noodle. 
It was sold along with the Noodle bar for a bit before they just dropped it 
because the Noodle was the drop they would suggest over all others. 

On Saturday, April 27, 2024 at 7:32:41 AM UTC-4 captaincon...@gmail.com 
wrote:

> Bill,
>
> Thanks for the clarification.  My posts weren't meant to be adversarial, 
> just pedantic.  I came into Riv via EcoVelo ~2010, and I didn't own my 
> first Riv until 2013, so the "Soba" predates me, and I thought that y'all 
> were using it colloquially for "So Bar"--the marketing content from Sim 
> Works makes references to literal soba noodles.  I'm curious if the 
> contemporary "So Bar" is inspired by the "Soba".
>
>
> Fair winds,
>
> Captain Conway Bennett
> 239.877.4119 <(239)%20877-4119>
> On Sat, Apr 27, 2024, 12:48 AM Bill Lindsay  wrote:
>
>> The Simworks So Bar is a handlebar that resembles a Nitto Noodle but in a 
>> wide width that was made in the late 2010s and early 2020s
>>
>> The Nitto Soba Noodle is a completely different handlebar that was made 
>> by Nitto and offered by Rivendell in the mid to late 2000s 
>>
>> Do not conflate the two.  This thread and WTB is focused on the Nitto 
>> Soba Noodle -NOT- the Simworks So Bar. 
>>
>> BL in EC
>>
>>
>> On Friday, April 26, 2024 at 5:40:48 PM UTC-7 captaincon...@gmail.com 
>> wrote:
>>
>>> I think the So Bar came out in the fall of 2018.  Here's the intro from 
>>> Sim Works:
>>>
>>> https://sim-works.com/en/news/ramen-nope-i-take-so-bar
>>>
>>> They also appear to have a sleeve.  But I've never owned the So Bar, so 
>>> I don't know what the production model was like in practice.  I had a 50 cm 
>>> Rando Bar from Velo Orange that I really liked at the time the So Bar was 
>>> released, and that's why I didn't buy it, but I love 50 cm + drop bars.
>>>
>>> It seems as though there is plans for a new iteration of the So Bar.  
>>> Sim Works USA wrote, "These were a very popular bar that we've temporarily 
>>> discontinued while we make some changes to a new version."
>>>
>>> I'm a bit of a Noodle/drop bar connoisseur myself.  I currently in use 
>>> the Crust Nullabar on my Monstercross, Sim Works Wild Honey on my Lightning 
>>> Bolt, and Ritchey Corralitos on my Hunqapillar.  I wish the Fairweather All 
>>> Road 174 AA bar was offered in a wider size, but my criticism of the 54 cm 
>>> Noodle is that it lost the back sweep that enjoyed in the Noodle as it got 
>>> wider.
>>>
>>>
>>> Fair winds,
>>>
>>> Captain Conway Bennett
>>> 239.877.4119 <(239)%20877-4119>
>>>
>>> On Fri, Apr 26, 2024, 5:32 PM Conway Bennett  
>>> wrote:
>>>
 Where did y'all read these were a lightweight Nitto Noodle?  They are 
 listed at 380 grams which is inline with other Noodles.  My understanding 
 was they were 50 cm wide--two cm wider than the then widest 48 cm 
 offering.  Then, Riv went all 7 minute abs and released the 52 and 54 
 centimeter variants.  I recently had a conversation with someone at Riv 
 regarding the widest Noodles who said that Nitto is trying to deprecate 
 the 
 26.0 clamp diameter.  I personally have had 46 cm Noodles, the Fairweather 
 174AA short shallow Noodle in 46 cm, and this week I swapped the 54 cm 
 ones 
 off my Hunqapillar in favor of the new Ritchey Corralitos bar which may be 
 my favorite drop bar for a longish top tube bike.  I wanted to like the 
 Noodle, but they have too much drop for me.

 On Friday, April 26, 2024 at 5:09:51 PM UTC-5 Bill Lindsay wrote:

> I absolutely snatch them up whenever I see them, and I never sell 
> them.  Buy the good stuff when it's available, before you need it.  
> That's 
> my advice.  ;)
>
> BL in EC
>
> -- 
 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/UMraDupetro/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/31ce2374-192d-4669-ae08-ca657c7975d9n%40googlegroups.com
  
 
 .

>>> -- 
>> 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/UMraDupetro/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 
>> 

[RBW] Re: WTB: Soba Handlebars

[Johnny Alien]

When RIvendell sold them back in the day I think Grant said they were about 
60g lighter than a standard noodle bar. That is right in line with what you 
found, Bill.

On Friday, April 26, 2024 at 7:26:39 PM UTC-4 Bill Lindsay wrote:

> "Where did y'all read these were a lightweight Nitto Noodle?"  
>
> They were already out of production when I came in 2009.  If I type "Nitto 
> Soba Noodle" into the googler, I get hits to bike forums in 2007 discussing 
> them.   At that time they are talking about how the regular Noodle mod 177 
> is the heavier cheaper version, and the Soba Noodle is in Nittos 
> "ultralight" flavor.  
>
> There are 9 of them in my garage right now.  8 are on bikes, and 1 is 
> loose.  7 are Mod 177 Noodles, and 2 are the Soba Noodle.  The shape is 
> identical.  I guess you'd just have to take my word for it.  I'm kind of a 
> Noodle zealot.  Most of the 9 in my garage are 460mm and a couple are 
> 440mm.  
>
> The loose bar is the model 177 regular Noodle.  It has 460 stamped in the 
> end and it measures 460mm center to center.  The Soba Noodle that went on 
> my new Roadeo had 460 stamped in the end and it also measures 460mm center 
> to center.  The regular Noodle has a "sleeve" in the middle, with embossed 
> Nitto graphics into the metal of the sleeve.  The Soba Noodle has a bulge 
> in the middle, and the Nitto graphics are black ink or similar printing on 
> the metal.  My build notes indicate I weighed the Soba Noodle at 310g.  The 
> loose regular 460mm Noodle weighs 372g on the same gram scale just now.  
>
> Bill Lindsay
> El Cerrito, CA 
>
> On Friday, April 26, 2024 at 3:32:19 PM UTC-7 captaincon...@gmail.com 
> wrote:
>
>> Where did y'all read these were a lightweight Nitto Noodle?  They are 
>> listed at 380 grams which is inline with other Noodles.  My understanding 
>> was they were 50 cm wide--two cm wider than the then widest 48 cm 
>> offering.  Then, Riv went all 7 minute abs and released the 52 and 54 
>> centimeter variants.  I recently had a conversation with someone at Riv 
>> regarding the widest Noodles who said that Nitto is trying to deprecate the 
>> 26.0 clamp diameter.  I personally have had 46 cm Noodles, the Fairweather 
>> 174AA short shallow Noodle in 46 cm, and this week I swapped the 54 cm ones 
>> off my Hunqapillar in favor of the new Ritchey Corralitos bar which may be 
>> my favorite drop bar for a longish top tube bike.  I wanted to like the 
>> Noodle, but they have too much drop for me.
>>
>> On Friday, April 26, 2024 at 5:09:51 PM UTC-5 Bill Lindsay wrote:
>>
>>> I absolutely snatch them up whenever I see them, and I never sell them. 
>>>  Buy the good stuff when it's available, before you need it.  That's my 
>>> advice.  ;)
>>>
>>> BL in EC
>>>
>>>

-- 
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/c92b39dc-4da8-416c-bd9f-8dfe5d7c6f64n%40googlegroups.com.

[RBW] Re: WTB: Soba Handlebars

[Johnny Alien]

Look at Bill just strolling in and flexing about his super stash of these 
bars.  :)

It looks like I might have a line on one but I agree that they would knock 
these out quick if they did a small release of them.

On Friday, April 26, 2024 at 3:16:45 PM UTC-4 Bill Lindsay wrote:

> I've got three of them in my stable, and would buy several more.  I've 
> told Grant at least once that if he got Nitto to make 200 of them, and he 
> did a presale at $150, that I bet he could pre-sell them before any of them 
> actually get made.  That would be a nice $30,000 cash flow exercise.  I'm 
> sure there are barriers to doing such a thing that I don't know, but the 
> $140 MSRP on Rene Herse bars certainly suggests that $150 is a price point 
> that would make sense for all involved.  
>
> Bill Lindsay
> El Cerrito, CA
>
> On Thursday, April 25, 2024 at 10:00:31 AM UTC-7 Johnny Alien wrote:
>
>> Every once and awhile I decide I want to search for some Soba bars again. 
>> This is the lightweight version of the Noodle handlebars. Anyone have a 
>> spare one they want to unload? Not really concerned about width.
>
>

-- 
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/98a424df-7a57-4d5c-bd39-26b1d690e9c5n%40googlegroups.com.

[RBW] WTB: Soba Handlebars

[Johnny Alien]

Every once and awhile I decide I want to search for some Soba bars again. 
This is the lightweight version of the Noodle handlebars. Anyone have a 
spare one they want to unload? Not really concerned about width.

-- 
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/e40ac0e2-b0c5-4842-b6d5-0b3cded51846n%40googlegroups.com.

Re: [RBW] Rivendell Roadbike Curious

[Johnny Alien]

Yeah thats a big haul too. New wheels, cockpit, brake setup, gearing 
(potentially). New road focused bike is 100% the way to go. :)

PS: I would feel the same way about getting a bike that would then need a 
cockpit overhaul automatically like that. A good deal gets to be less of 
one when you have to throw down a bunch cash on top of it to get it the way 
you want

PPS: This has inspired me to get a road frame to replace the Roadini that I 
was unable to build up last year. Not a Rivendell but Riv adjacent.

PPPS: When you keep adding postscripts should you be adding extra P's the 
way I did it or you you at extra S's? It seems like Post, Post, makes more 
sense than Script, Script.if that is indeed what the S stands for. Its 
been years since I have been in school or actually wrote a real life letter.

On Thursday, April 25, 2024 at 1:17:29 AM UTC-4 Joe Bernard wrote:

> Putting myself in Leah's place to answer your question, if I had her 
> plethora of Platys I would choose a new/different bike for drop bars 
> because it would be more interesting. Popping drops on one of my Platys 
> with wide tires and a dynohub ain't gonna do the roadie thing for me. 
>
> Joe Bernard 
>
> On Wednesday, April 24, 2024 at 6:39:13 PM UTC-7 ttoshi wrote:
>
>> --What if I flip the question on its head and say could I do club riding 
>> with my Cheviot, and what would I gain from getting a road bike?
>>
>> I've not ridden a Platypus, but I would assume that it would be similar 
>> to a Cheviot.
>>
>> If I stripped down my Cheviot, then I am confident that I would be 
>> perfectly fine on club rides.  I have Albastache bars, and basically use 2 
>> positions.  My brake levers are on the curves up front and it is probably 
>> similar to my drop bars.  I have an upright position at the end of the bar 
>> where the bar end shifters are.  I think rides up to a century or 200k 
>> would be fine.  I think I might prefer a drop bar for longer rides because 
>> I have more hand positions that I use (I'm sure there are more usable 
>> positions on the Albastache, but I don't use them...).
>>
>> For my drop bars, I found this site to describe various hand positions: 
>> https://www.roadbikerider.com/dropped-bar-hand-positions/
>>
>> I probably use position 3 (curves of the flat front bar) for 45% of my 
>> riding.  30% in position 7 in the drops and the other 20% in position 9 
>> (end of drops) and 10% on the flats or in the hoods (2,5).
>>
>> I actually don't use the hoods too much because I set up my drop bars so 
>> that I am most comfortable in the drops and a bit stretched out when my 
>> hands are in the hoods.
>> --I would definitely recommend TRP levers if you want to brake from the 
>> drops because they are angled out to make it easy to grab when you are 
>> braking from the drops.
>>
>> Aside from more hand positions with a drop bar, there would be more 
>> responsive steering from the handlebar.  I think that if I had a bmx setup 
>> without brake or derailleur cables, then I would be able to spin my front 
>> wheel 360 degrees without falling on my Cheviot.  
>>
>> If I tried to spin my Roadeo front wheel 360 degrees, then I'm pretty 
>> sure I'd fall flat on my face as I angled the front wheel too far to the 
>> left or right.
>>
>> My Roadeo has the best handling via steering input.  This responsiveness 
>> to steering gives me better descending capabilities when going down curvy 
>> roads.  I wouldn't otherwise need the responsive steering if I didn't 
>> descend hilly/mountainous roads, and would be perfectly fine going slightly 
>> slower on my Cheviot.
>>
>> If I had a racing Platy/Cheviot: 1. Albastache bars to have the hand 
>> position with the brakes up front to tuck down in the wind. 2. Supple 
>> sidewall tires.  Yes there is a greater risk of sidewall damage, but if I 
>> store my bike indoors (I do) and do periodic inspection of my tires (I need 
>> to do this before big rides for sure), then I am comfortable with the risk 
>> benefit tradeoff. The improvement in ride quality and speed was tremendous 
>> for me. 38-42 mm is ideal for me (Hetre EL or Babyshoe pass EL or parimoto 
>> 38 mm are tires I have used and are wonderful).  I think Jan 
>> Heine/Compass/Rene Herse's research showed that 42 mm supple tires are no 
>> less efficient and can be more efficient than 28 mm road tires.
>>
>> I wouldn't worry about the weight of the bike unless I was just hanging 
>> on by a thread and needed to lose a pound or two to keep a margin of 
>> comfort, or unless I were actually racing (I don't) and seconds might 
>> really count. Besides, I know there is a certain amount of satisfaction 
>> when a racing Platy keeps up with the carbon fiber pack!
>>
>> Toshi in Oakland, 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 

Re: [RBW] Rivendell Roadbike Curious

[Johnny Alien]

The Romulus was essentially just the Rambouillet and I fit Kojaks on it. 
Those are stated to be 35 but I think they were actually more like 36. With 
that in mind it worked but I am not sure I would have been able to or 
wanted to go to 38's. It was probably possible though.

Interesting that in reviewing some of those pages Grant said that the AHH 
and Rambouillet are the same with the only exception being that the AHH 
takes larger tires. I'm not sure I ever knew that before. I thought the AHH 
was the same as the Saluki with only the 650B vs 700C tires being the 
difference at the beginning.

On Tuesday, April 23, 2024 at 4:26:17 PM UTC-4 George Schick wrote:

> Yep, according to that Riv chart, up to 38mm.  But I don't recommend going 
> there because they will increase your SOH.  And you don't really need any 
> tires of that size anyway if you have a road bike that you're going to be 
> riding on paved roads - 32mm or so would be good enough.
>
> On Tuesday, April 23, 2024 at 3:13:08 PM UTC-5 Bicycle Belle Ding Ding! 
> wrote:
>
>> …which would give me room for that larger tire!
>> Sent from my iPhone
>>
>> On Apr 23, 2024, at 4:09 PM, George Schick  wrote:
>>
>> Hmm... according to a geometry chart for the Romulus 
>> http://cyclofiend.com/rbw/romulus/romflyer/04.html a 55cm Rom should 
>> have a "typical  PBH" of between 79-80 and a 57cm for those with PBH's of 
>> 81-83.  So...disagreeing as I do with Grant about "going larger is better" 
>> on frame size, I'd say that this bike would be perfect.
>>
>>
>>
>> On Tuesday, April 23, 2024 at 2:55:13 PM UTC-5 pi...@gmail.com wrote:
>>
>>> The Romulus had a different geometry with a much misleading frame 
>>> sizing. Here's the geometry: 
>>> https://notfine.com/rivreader/Brochures/Rivendell%20Frames%20Romulus.pdf
>>>
>>> Looks like if you were 5' 10", that'll put you onto a 59cm Romulus. 
>>> Unusual compared to today's Roadini sizing, but the Romulus also has a 
>>> lower BB. I would buy it. If Leah doesn't want it let me know and I'd 
>>> consider it for my wife who still wants a Roadini.
>>>
>>> On Tue, Apr 23, 2024 at 12:52 PM Mathias Steiner  
>>> wrote:
>>>
 >> So I found a 55 cm Romulus for $1250. What do we think of THAT? 

 We think that you need to find a geometry chart for the Romulus.

 The older AHH and Roadeo charts show 80.9 and 80.6 cm standover 
 clearance, respectively, for the 55 cm size.
 That's awfully close to your stated PBH of 81 cm.

 cheers -mathias

 On Tuesday, April 23, 2024 at 3:46:47 PM UTC-4 George Schick wrote:

> Sounds great, right in and around your PBH and SOH.  'Course, that all 
> depends upon what kind of shape it's in, where it has to come from 
> (shipped 
> or local) therefore sight seen or unseen, etc. I'd say give it a shot - 
> there aren't many of those Romulus models around and they're almost 
> collectables.  Got a trustworthy LBS now that you can depend upon to give 
> it a good going over and therefore a professional evaluation?
>
> Best winds!
> On Tuesday, April 23, 2024 at 2:33:00 PM UTC-5 Bicycle Belle Ding 
> Ding! wrote:
>
>> So I found a 55 cm Romulus for $1250. What do we think of THAT?
>>
>> On Apr 23, 2024, at 3:02 PM, Jim Bronson  wrote:
>>
>> 
>>
>> Get an old one like a Rambouillet for true road-ability.  The early 
>> Rivs are the best if you are into club riding.  I love my Clem for being 
>> versatile but I have ridden over 20,000 Km of brevets on my 90s Riv Road 
>> Standard or custom, not sure which. I bought it used.  I have mine 650B 
>> converted, run 650Bx38 with the Tektro long, long reach brakes, 55-73 
>> reach, IIRC.  There's several others in the forum that have theirs done 
>> this way as well.
>>
>> Jim
>> Austin, TX burbs
>>
>> On Sat, Apr 20, 2024 at 2:33 PM Bicycle Belle Ding Ding! <
>> jonasa...@gmail.com> wrote:
>>
>>> I’m starting to wonder about a roadbike. But it has to be a 
>>> Rivendell roadbike because I’m loyal and all that. Anyway, I don’t know 
>>> that the Roadini really offers enough of a change for me. I have no 
>>> idea 
>>> what is going on with the Gallup. Then there’s the Roadeo - that one 
>>> looks 
>>> great but there’s a 2 year wait, unless I can find one used. Which 
>>> would be 
>>> ideal. 
>>>
>>> Who rides their Rivbike in club rides and what do you ride? Who has 
>>> a Roadeo that never gets ridden and wants to sell it? I don’t even know 
>>> what size I’d be but I’m an 81 PBH. Must I ride drop bars? I never have 
>>> before. I know nothing about any of this. Clearly.
>>>
>>> Note: I still like my raspberry Platypus for club riding but it does 
>>> take a toll on me in wind. I recently got a shorter-height, 
>>> longer-reach 
>>> stem which marginally helped, but our high spring winds are 

Re: [RBW] Rivendell Roadbike Curious

[Johnny Alien]

And congrats if you get it. That is a very solid road focused Riv at a 
really fair price.

On Tuesday, April 23, 2024 at 4:05:36 PM UTC-4 Johnny Alien wrote:

> That still falls into that "rivendell likes to size up" thing. I had a 54 
> Rambouillet and while I am 5'9" I have a lower PBH (around 80). The 54 was 
> the max I would be comfortable with. A 55 Romulus would likely work. Leah's 
> PBH is slightly larger so I think the 55 would be a great fit. Going to a 
> 59 sounds crazy to me.
>
> On Tuesday, April 23, 2024 at 3:55:13 PM UTC-4 pi...@gmail.com wrote:
>
>> The Romulus had a different geometry with a much misleading frame sizing. 
>> Here's the geometry: 
>> https://notfine.com/rivreader/Brochures/Rivendell%20Frames%20Romulus.pdf
>>
>> Looks like if you were 5' 10", that'll put you onto a 59cm Romulus. 
>> Unusual compared to today's Roadini sizing, but the Romulus also has a 
>> lower BB. I would buy it. If Leah doesn't want it let me know and I'd 
>> consider it for my wife who still wants a Roadini.
>>
>> On Tue, Apr 23, 2024 at 12:52 PM Mathias Steiner  
>> wrote:
>>
>>> >> So I found a 55 cm Romulus for $1250. What do we think of THAT? 
>>>
>>> We think that you need to find a geometry chart for the Romulus.
>>>
>>> The older AHH and Roadeo charts show 80.9 and 80.6 cm standover 
>>> clearance, respectively, for the 55 cm size.
>>> That's awfully close to your stated PBH of 81 cm.
>>>
>>> cheers -mathias
>>>
>>> On Tuesday, April 23, 2024 at 3:46:47 PM UTC-4 George Schick wrote:
>>>
>>>> Sounds great, right in and around your PBH and SOH.  'Course, that all 
>>>> depends upon what kind of shape it's in, where it has to come from 
>>>> (shipped 
>>>> or local) therefore sight seen or unseen, etc. I'd say give it a shot - 
>>>> there aren't many of those Romulus models around and they're almost 
>>>> collectables.  Got a trustworthy LBS now that you can depend upon to give 
>>>> it a good going over and therefore a professional evaluation?
>>>>
>>>> Best winds!
>>>> On Tuesday, April 23, 2024 at 2:33:00 PM UTC-5 Bicycle Belle Ding Ding! 
>>>> wrote:
>>>>
>>>>> So I found a 55 cm Romulus for $1250. What do we think of THAT?
>>>>>
>>>>> On Apr 23, 2024, at 3:02 PM, Jim Bronson  wrote:
>>>>>
>>>>> 
>>>>>
>>>>> Get an old one like a Rambouillet for true road-ability.  The early 
>>>>> Rivs are the best if you are into club riding.  I love my Clem for being 
>>>>> versatile but I have ridden over 20,000 Km of brevets on my 90s Riv Road 
>>>>> Standard or custom, not sure which. I bought it used.  I have mine 650B 
>>>>> converted, run 650Bx38 with the Tektro long, long reach brakes, 55-73 
>>>>> reach, IIRC.  There's several others in the forum that have theirs done 
>>>>> this way as well.
>>>>>
>>>>> Jim
>>>>> Austin, TX burbs
>>>>>
>>>>> On Sat, Apr 20, 2024 at 2:33 PM Bicycle Belle Ding Ding! <
>>>>> jonasa...@gmail.com> wrote:
>>>>>
>>>>>> I’m starting to wonder about a roadbike. But it has to be a Rivendell 
>>>>>> roadbike because I’m loyal and all that. Anyway, I don’t know that the 
>>>>>> Roadini really offers enough of a change for me. I have no idea what is 
>>>>>> going on with the Gallup. Then there’s the Roadeo - that one looks great 
>>>>>> but there’s a 2 year wait, unless I can find one used. Which would be 
>>>>>> ideal. 
>>>>>>
>>>>>> Who rides their Rivbike in club rides and what do you ride? Who has a 
>>>>>> Roadeo that never gets ridden and wants to sell it? I don’t even know 
>>>>>> what 
>>>>>> size I’d be but I’m an 81 PBH. Must I ride drop bars? I never have 
>>>>>> before. 
>>>>>> I know nothing about any of this. Clearly.
>>>>>>
>>>>>> Note: I still like my raspberry Platypus for club riding but it does 
>>>>>> take a toll on me in wind. I recently got a shorter-height, longer-reach 
>>>>>> stem which marginally helped, but our high spring winds are taking it 
>>>>>> out 
>>>>>> of me. I did a club ride yesterday with my women’s group and my heart 
>

Re: [RBW] Rivendell Roadbike Curious

[Johnny Alien]

That still falls into that "rivendell likes to size up" thing. I had a 54 
Rambouillet and while I am 5'9" I have a lower PBH (around 80). The 54 was 
the max I would be comfortable with. A 55 Romulus would likely work. Leah's 
PBH is slightly larger so I think the 55 would be a great fit. Going to a 
59 sounds crazy to me.

On Tuesday, April 23, 2024 at 3:55:13 PM UTC-4 pi...@gmail.com wrote:

> The Romulus had a different geometry with a much misleading frame sizing. 
> Here's the geometry: 
> https://notfine.com/rivreader/Brochures/Rivendell%20Frames%20Romulus.pdf
>
> Looks like if you were 5' 10", that'll put you onto a 59cm Romulus. 
> Unusual compared to today's Roadini sizing, but the Romulus also has a 
> lower BB. I would buy it. If Leah doesn't want it let me know and I'd 
> consider it for my wife who still wants a Roadini.
>
> On Tue, Apr 23, 2024 at 12:52 PM Mathias Steiner  
> wrote:
>
>> >> So I found a 55 cm Romulus for $1250. What do we think of THAT? 
>>
>> We think that you need to find a geometry chart for the Romulus.
>>
>> The older AHH and Roadeo charts show 80.9 and 80.6 cm standover 
>> clearance, respectively, for the 55 cm size.
>> That's awfully close to your stated PBH of 81 cm.
>>
>> cheers -mathias
>>
>> On Tuesday, April 23, 2024 at 3:46:47 PM UTC-4 George Schick wrote:
>>
>>> Sounds great, right in and around your PBH and SOH.  'Course, that all 
>>> depends upon what kind of shape it's in, where it has to come from (shipped 
>>> or local) therefore sight seen or unseen, etc. I'd say give it a shot - 
>>> there aren't many of those Romulus models around and they're almost 
>>> collectables.  Got a trustworthy LBS now that you can depend upon to give 
>>> it a good going over and therefore a professional evaluation?
>>>
>>> Best winds!
>>> On Tuesday, April 23, 2024 at 2:33:00 PM UTC-5 Bicycle Belle Ding Ding! 
>>> wrote:
>>>
 So I found a 55 cm Romulus for $1250. What do we think of THAT?

 On Apr 23, 2024, at 3:02 PM, Jim Bronson  wrote:

 

 Get an old one like a Rambouillet for true road-ability.  The early 
 Rivs are the best if you are into club riding.  I love my Clem for being 
 versatile but I have ridden over 20,000 Km of brevets on my 90s Riv Road 
 Standard or custom, not sure which. I bought it used.  I have mine 650B 
 converted, run 650Bx38 with the Tektro long, long reach brakes, 55-73 
 reach, IIRC.  There's several others in the forum that have theirs done 
 this way as well.

 Jim
 Austin, TX burbs

 On Sat, Apr 20, 2024 at 2:33 PM Bicycle Belle Ding Ding! <
 jonasa...@gmail.com> wrote:

> I’m starting to wonder about a roadbike. But it has to be a Rivendell 
> roadbike because I’m loyal and all that. Anyway, I don’t know that the 
> Roadini really offers enough of a change for me. I have no idea what is 
> going on with the Gallup. Then there’s the Roadeo - that one looks great 
> but there’s a 2 year wait, unless I can find one used. Which would be 
> ideal. 
>
> Who rides their Rivbike in club rides and what do you ride? Who has a 
> Roadeo that never gets ridden and wants to sell it? I don’t even know 
> what 
> size I’d be but I’m an 81 PBH. Must I ride drop bars? I never have 
> before. 
> I know nothing about any of this. Clearly.
>
> Note: I still like my raspberry Platypus for club riding but it does 
> take a toll on me in wind. I recently got a shorter-height, longer-reach 
> stem which marginally helped, but our high spring winds are taking it out 
> of me. I did a club ride yesterday with my women’s group and my heart 
> rate 
> was in the 170s the whole 26.3 miles. It was brutal. Everyone else agreed 
> it was a hard ride, but I felt like it was harder on me than them, and 
> I’m 
> the youngest and probably the most fit. 
>
> Leah
>
> -- 
> 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/fab5132f-e8ca-4a76-842d-9b994853e099n%40googlegroups.com
>  
> 
> .
>


 -- 
 --
 signature goes here

 -- 

 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/uXZ6OSH6T-s/unsubscribe
 .
 To unsubscribe from this group and all its topics, send an email to 

Re: [RBW] Rivendell Roadbike Curious

[Johnny Alien]

*- "Would they love it as a road bike? Or is it kind of all-purpose? 
Thanks!"*

Rivendell makes stuff to be pretty flexible so even the Roadeo "could" be 
built out to be kind of all-purpose but the geometry and intent of the 
Gallop is to be a road frame that replaces the Roadini. My prototype is 
pretty light and very lively. I assume the production ones will be as well 
because the geometry should be the same it just has a straight bar vs a 
swoop. I think while its not a step through the angled bar will allow it to 
be more flexible with fitting.

On Sunday, April 21, 2024 at 11:07:13 AM UTC-4 leva...@gmail.com wrote:

> Hi Leah!
>
> I think you would dig a Crust Canti-Lightning Bolt as a complementary 
> addition to your wonderful stable of Rivs - not only for the ride quality, 
> but you can get a cool Lilac (with pink graphics) or Light Sea Green frame 
> in your size now.  I own this bike, and it is light, quick, and fun to 
> ride, and can easily accommodate up to a 650B x 48 tire.  But wait there’s 
> more….in older Riv road bike style, the Canti-Bolts have flat top tubes, 
> threaded headsets, and a gorgeous curved fork.  This is a low-trail Rando 
> bike for sure - even the 650B wheels, etc.  This is a fun bike!  I’m a Riv 
> head for sure, but I really enjoy a long faster road ride on the Crust 
> every now and then.  
>
> Crustbikes.com
>
>
> Good luck in your search,
>
> Guy
> On Sunday, April 21, 2024 at 7:01:14 AM UTC-6 David Hays wrote:
>
>> Good morning Leah,
>> I’m not sure where I read it but apparently Grant had at one point been a 
>> fan of Mercians.
>> A few years after I bought and built up my 650B Homer I found a used 
>> Mercian KOM on Craigslist. I’ve since picked up another off the list and 
>> had one purpose built for me. Very comfortable and fast. Some thing to 
>> consider.
>>
>> Cheers,
>> David 
>>
>> On Apr 21, 2024, at 12:17 AM, Josiah Anderson  
>> wrote:
>>
>> Hi Leah,
>>
>> I'm also excited to hear about your journey towards a road bike; you 
>> probably don't know it but your writing on this list was one of my main 
>> influences towards ending up with a Riv. Drop bars and pavement are very 
>> familiar, comfortable territory for me, and – like others have said here – 
>> I still enjoy that type of riding at times.
>>
>> You're probably already familiar with him, but if not, I'd recommend 
>> checking out some of Jan Heine's work – Bicycle Quarterly, *The All-Road 
>> Bike Revolution,* his blog, etc. Bicycle Quarterly was my point of 
>> departure from "mainstream" bike culture, and I came around to appreciating 
>> Riv a bit later and now enjoy both approaches for different rides. Jan is 
>> much more focused on speed than Grant is, but in what feels to me like a 
>> healthy way. This is an old blog post that I think may be worth a read, as 
>> it's an articulation of the same sort of perspective you seem to be 
>> arriving at: https://www.renehersecycles.com/riding-fast-is-fun/. Jan 
>> also wrote somewhere (can't find it right now) about how he and Grant are 
>> good friends, and he wanted to make it clear he's not dissing Riv by 
>> promoting what he likes.
>>
>> I currently have two of what I'd call "really nice" bikes, a Gus 
>> Boots-Willsen and a Crust Lightning Bolt (alongside moderately nice bikes 
>> like a Bridgestone MB-3 and a dumpster-find Bianchi Volpe). The Gus is 
>> "full-Riv" – friction shifting, Carradice saddlebag, weird bar wrap, etc – 
>> and the Crust is full Bicycle Quarterly, with 42mm extralight tires, 
>> low-trail geometry, Gilles Berthoud handlebar bag, and all that. (Jan is 
>> not affiliated with Crust, but Crust designed the Lightning Bolt with his 
>> preferences in mind). The two bikes are a perfect combination for my 
>> current riding: there is enough crossover that both work great for 
>> doubletrack rides, and the Gus is ideal for riding singletrack while the 
>> Crust excels at long, fast road and gravel rides. Rivendell doesn't make 
>> randonneur bikes like my Crust, as it sounds to me like they don't like the 
>> lighter-gauge tubing and the handling optimized for drop bars and moderate 
>> front loads, but Grant has written (quoting from memory, so hopefully I'm 
>> pretty close here) that he's glad companies like Crust exist and do 
>> different stuff from Riv. I don't feel like riding my Crust is an insult to 
>> Rivendell, just an expression of the fact that my riding conditions are a 
>> bit different from theirs, though I totally get it if that's how it feels 
>> to you. 
>>
>> I've never ridden a Roadeo or Roadini, but I've ridden a LOT of road race 
>> and "sport-touring" bikes from the 1960s through 2000s, many of which (like 
>> early 80s Trek sport tourers, one of my main rides for a long time) have a 
>> lot of similarities to the Roadeo. I prefer my Crust for several reasons: 
>> it's designed for bigger tires, which when they're René Herse Extralights 
>> are just as fast as 23mm tubulars and far more 

[RBW] Re: Rivendell Roadbike Curious

[Johnny Alien]

Probably a bit of a wait for a Gallop but the slightly lower top tube could 
give it an edge over standard road frames. I have the swoopy prototype and 
if it rides the same people are going to love it.

On Saturday, April 20, 2024 at 7:23:36 PM UTC-4 bei...@gmail.com wrote:

> Leah I was psyched to see this post because you were the #1 influence on 
> me to get a Platypus (besides Lance who sold it to me! Thanks, Lance!). 
> Besides the Platy, which is for around town and gravel and kid-hauling, I 
> also ride my father-in-laws 1990-something Merlin road bike in occasional 
> club rides and races. I love the Platy for all the already mentioned 
> reasons in this Bunch, and love the snappy, fast, titanium Merlin, but 
> always wish the fork was a bit heavier (and not carbon) and that the 
> chainstays were a hair longer (and didn’t limit the rear tire to 25mm). 
>
> I almost jumped on a used Roadeo in my size a month or so ago and am 
> extremely Roadini curious. I wonder if you say the roadini “doesn’t offer 
> enough of a change” for you because you think it’s not different enough 
> from the Platy? I would think the Roadini is closer to the Roadeo or a 
> Rambouillet than the Gallop will be. From the August 2023 blahg, the Gallop 
> looks like a mix between a Platy and a Roadini. 
>
> when I see that Homer Jim shared in your size as a web special my first 
> thought was, “THAT’S IT!,” but I think you should give a ”real” “road bike” 
> a shot rather than a “country bike” like a Sam or a Homer, since your 
> Platy’s are in that category. 
>
> Thanks for your contributions Leah and have fun finding your next “Save me 
> from the wind on club rides!” Bike! 
>
> Christian
> Boulder, CO
>
> PS: Gallop pics in this blagh:
>
> https://www.rivbike.com/blogs/grant-petersens-blog/august?_pos=11&_sid=e1163b89a&_ss=r
>
>
>
>
> On Saturday, April 20, 2024 at 3:58:44 PM UTC-6 Jim M. wrote:
>
> I think the Roadeo is the raciest road bike Riv has made. I've seen one 
> 56cm that was built up to 18.5 lbs with pedals. But if you're looking 
> beyond the weight weenie category, there are lots of other options. 
> Rambouillet, Redwood, and Romulus come to mind. And if you're not fixed on 
> 700 wheels, you've got the Hilsen, Saluki, and Bleriot. I had a road 
> wheelset for my Legolas, which I used for club rides and randonneuring. I 
> wouldn't hesitate to put drop bars on my Bleriot and turn it into a 
> randonneur too. And how could I forget the Hillborne? Also very roadable. 
> There's a 51 dropbar Homer on the web special page 
> https://www.rivbike.com/products/51cm-homer-dark-gold-antonios-dropbar-pick 
> if that's your size.
>
> jim m
> walnut creek ca
>
> On Saturday, April 20, 2024 at 12:33:50 PM UTC-7 Bicycle Belle Ding Ding! 
> wrote:
>
> I’m starting to wonder about a roadbike. But it has to be a Rivendell 
> roadbike because I’m loyal and all that. Anyway, I don’t know that the 
> Roadini really offers enough of a change for me. I have no idea what is 
> going on with the Gallup. Then there’s the Roadeo - that one looks great 
> but there’s a 2 year wait, unless I can find one used. Which would be 
> ideal. 
>
> Who rides their Rivbike in club rides and what do you ride? Who has a 
> Roadeo that never gets ridden and wants to sell it? I don’t even know what 
> size I’d be but I’m an 81 PBH. Must I ride drop bars? I never have before. 
> I know nothing about any of this. Clearly.
>
> Note: I still like my raspberry Platypus for club riding but it does take 
> a toll on me in wind. I recently got a shorter-height, longer-reach stem 
> which marginally helped, but our high spring winds are taking it out of me. 
> I did a club ride yesterday with my women’s group and my heart rate was in 
> the 170s the whole 26.3 miles. It was brutal. Everyone else agreed it was a 
> hard ride, but I felt like it was harder on me than them, and I’m the 
> youngest and probably the most fit. 
>
> Leah
>
>

-- 
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/9e7853f7-c074-465a-a99d-cf7713b5914en%40googlegroups.com.

[RBW] Re: Rivendell Roadbike Curious

[Johnny Alien]

I doubt the Roadeo is a TON lighter than a Roadini. I think the weight 
details would be in the build more than anything else. As far as bars are 
concerned drops are fun on a road bike but not required. My recommendation 
for a non-drop road setup would be the Albastache bars which are IMO the 
best road bars out there.

On Saturday, April 20, 2024 at 5:12:07 PM UTC-4 George Schick wrote:

> Ryan - sorry.  I don't always see things as clearly with my aged 
> ready-for-cataract surgery eyeballs.  Nevertheless, it bears repeating.
>
>
> On Saturday, April 20, 2024 at 4:06:11 PM UTC-5 Ryan wrote:
>
>> 81 PBH was mentioned
>>
>> On Saturday, April 20, 2024 at 4:04:52 PM UTC-5 Ryan wrote:
>>
>>> There ya go Leah!...Put yourself in Bill's more-than-capable hands and 
>>> you won't go wrong!
>>>
>>> On Saturday, April 20, 2024 at 3:51:55 PM UTC-5 Bill Lindsay wrote:
>>>
 Leah

 My previous Roadeo was set up as a straight-ahead stripped down road 
 bike, and I would have used that anyplace anybody rides a road bike.  
 After 
 selling that, and while I was waiting for my new pink Roadeo, I used my 
 Black Mountain Road in that stripped down road bike slot, and that bike 
 was 
 the deal of the century, IMO.  The RoadeoRosa revealed itself to be more 
 than just a stripped down road bike: It has insisted to become my 700c 
 randonneuse.  

 Anyway, I did a very fast build on a Leo Roadini, last batch, and my 
 best-ever brevet time was on that bike.  So I think it's doable.  The 
 newer 
 batch with its long reach brakes feels less "roadie".  

 I can sympathize with the desire to run a Riv, but I'd also recommend 
 casting a wider net, because smaller frame sized used road bikes can be 
 had 
 at a really good price.  Maybe if you start trolling Michigan craigslist 
 and the next time I'm out in Wayne County for work I can come be your 
 personal shopper.  :)

 Anything that can be set up with drop bars can probably also be set up 
 with an albastache build, which may ease you in.  Also, having a 
 placeholder road bike could free you up to put a deposit on a Roadeo and 
 then you'll have both!  

 Do let me know if you want more advice

 Bill Lindsay
 El Cerrito, CA

 On Saturday, April 20, 2024 at 12:33:50 PM UTC-7 Bicycle Belle Ding 
 Ding! wrote:

> I’m starting to wonder about a roadbike. But it has to be a Rivendell 
> roadbike because I’m loyal and all that. Anyway, I don’t know that the 
> Roadini really offers enough of a change for me. I have no idea what is 
> going on with the Gallup. Then there’s the Roadeo - that one looks great 
> but there’s a 2 year wait, unless I can find one used. Which would be 
> ideal. 
>
> Who rides their Rivbike in club rides and what do you ride? Who has a 
> Roadeo that never gets ridden and wants to sell it? I don’t even know 
> what 
> size I’d be but I’m an 81 PBH. Must I ride drop bars? I never have 
> before. 
> I know nothing about any of this. Clearly.
>
> Note: I still like my raspberry Platypus for club riding but it does 
> take a toll on me in wind. I recently got a shorter-height, longer-reach 
> stem which marginally helped, but our high spring winds are taking it out 
> of me. I did a club ride yesterday with my women’s group and my heart 
> rate 
> was in the 170s the whole 26.3 miles. It was brutal. Everyone else agreed 
> it was a hard ride, but I felt like it was harder on me than them, and 
> I’m 
> the youngest and probably the most fit. 
>
> Leah
>


-- 
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/8463b8d2-f8fc-465c-9a84-8bd346fe1932n%40googlegroups.com.

[Documentation-packages] [Bug 2062655] [NEW] "Enable Animations" system a11y setting does not apply to CSS media query prefers-reduced-motion

[Johnny Gérard]

Public bug reported:

I am able to disable animations by switching off the system setting
"Enable Animations" in the Accessibility pane.

But it does not apply to the CSS media query prefers-reduced-motion.

The MDN page documents this media query and can be used to test the
feature.

https://developer.mozilla.org/en-US/docs/Web/CSS/@media/prefers-reduced-
motion

** Affects: ubuntu-docs (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of
Documentation Packages, which is subscribed to ubuntu-docs in Ubuntu.
https://bugs.launchpad.net/bugs/2062655

Title:
  "Enable Animations" system a11y setting does not apply to CSS media
  query prefers-reduced-motion

Status in ubuntu-docs package in Ubuntu:
  New

Bug description:
  I am able to disable animations by switching off the system setting
  "Enable Animations" in the Accessibility pane.

  But it does not apply to the CSS media query prefers-reduced-motion.

  The MDN page documents this media query and can be used to test the
  feature.

  https://developer.mozilla.org/en-US/docs/Web/CSS/@media/prefers-
  reduced-motion

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-docs/+bug/2062655/+subscriptions


-- 
Mailing list: https://launchpad.net/~documentation-packages
Post to : documentation-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~documentation-packages
More help   : https://help.launchpad.net/ListHelp

[Bug 2062655] [NEW] "Enable Animations" system a11y setting does not apply to CSS media query prefers-reduced-motion

[Johnny Gérard]

Public bug reported:

I am able to disable animations by switching off the system setting
"Enable Animations" in the Accessibility pane.

But it does not apply to the CSS media query prefers-reduced-motion.

The MDN page documents this media query and can be used to test the
feature.

https://developer.mozilla.org/en-US/docs/Web/CSS/@media/prefers-reduced-
motion

** Affects: ubuntu-docs (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/2062655

Title:
  "Enable Animations" system a11y setting does not apply to CSS media
  query prefers-reduced-motion

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-docs/+bug/2062655/+subscriptions


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

[RBW] Re: Sizing question for "in between" PBH measurement

[Johnny Alien]

That I can't say BUT if you go with the 54 might I suggest the Billie bars? 
They are similar to the Albatross but go back a bit further. Quite 
luxurious.

On Thursday, April 18, 2024 at 8:13:32 PM UTC-4 Robert Calton wrote:

> That does make sense. I wonder if a 130 stem with the Albatross bars on 
> the 51 would give enough knee clearance, because I definitely want to run 
> those bars. 
> On Thursday, April 18, 2024 at 8:08:44 PM UTC-4 Johnny Alien wrote:
>
>> I would never question Rivendell's knowledge on anything at all but like 
>> I said their method of sizing bikes for people does not work for me 
>> personally. If you are comfortable on the 55 Salsa the 54 SH will feel a 
>> lot bigger. The 51 will likely feel pretty close. But I don't want to 
>> discourage sizing up especially if you are diving into the sweptback 
>> movement the kids are into these days.
>>
>> On Thursday, April 18, 2024 at 8:02:45 PM UTC-4 Robert Calton wrote:
>>
>>> OP here, apologies for deleting the post amidst the thoughtful 
>>> conversation, I thought that I got the answer I needed and didn't want to 
>>> clutter up the board :p 
>>>
>>> Will at Riv suggested that I size up to the 54. 
>>>
>>> The context was: compared to my current bike, a drop-bar 55cm Salsa 
>>> Vaya's standover of 77.6cm and top tube of 55cm...
>>>
>>> 51 Sam standover: 78.6 (+1cm from Vaya)
>>> 51 Sam top tube: 56.5 (+1.5cm from Vaya) 
>>>
>>> 54 Sam standover: 82.0 (+4.4cm from Vaya) 
>>> 54 Sam top tube:  58 (+3cm from Vaya) 
>>>
>>> An 83.8 PBH was the highest measurement out of the 10 or so times I 
>>> measured. Most of the time it was 81.2 - 82.5 range. I'm 5'11 with a 30" 
>>> inseam. Riv says a 51 Sam is 79-83 and a 54 is 83-86. That nearly 2" 
>>> increase of standover height gives me pause, to be honest. But eh, seems 
>>> that the wisdom of the riding community suggests sizing up. 
>>> On Thursday, April 18, 2024 at 7:56:06 PM UTC-4 Drew Fitchette wrote:
>>>
>>>> Echoing Bill on here. I also look at stack and reach, and have nearly 
>>>> the same dimensions as the OP
>>>>
>>>> I had a 53 Atlantis from the last run as it was correct for my PBH as 
>>>> I’m between the 53 and 55, after deep dives on stack and reach(in 
>>>> particular) I realized what made the bike *feel* small to me. I 
>>>> should’ve sized up to a 55 instead, and similar to Bill have now scooped a 
>>>> 56 hillborne from another list member as it’s the biggest size non step 
>>>> over riv I can fit. 
>>>>
>>>> Roman told me that the 54 Sam would feel bigger as far as 
>>>> standover(mostly due to the 700c wheels) but the bike might feel similar 
>>>> to 
>>>> the Atlantis for stack and the reach is shorter. He actually suggested a 
>>>> 60cm Plat with my seat slammed since I’m 6 ft tall. And I know Grant rides 
>>>> a 59cm Clem with only a slightly taller PBH than I have. 
>>>>
>>>> All that to say, I think I’ll be sizing up henceforth as I like toscos 
>>>> or albatross bars usually and don’t mind the straddle heigh being close!
>>>>
>>>>
>>>>
>>>> On Thursday, April 18, 2024 at 6:42:10 PM UTC-4 Bill Lindsay wrote:
>>>>
>>>>> Johnny said: "the 51 SH I owned seemed as large or larger than the 
>>>>> 54cm Rambo"
>>>>>
>>>>> I agree with that.  A 51 Sam is "bigger" than a 54cm Rambouillet, IMO. 
>>>>>  My comment had to do with the OP's height at 5'11".  A 5'11" person 
>>>>> would 
>>>>> probably do best on a 60cm Ram.  At 5'10" I'd pick a 60cm if you gave me 
>>>>> any size I choose.  A 57 Hillborne would be a little bigger than a 60 
>>>>> Ram, 
>>>>> and a 54 Hilborne would be a little smaller.  The OP deleted their post 
>>>>> so 
>>>>> it's maybe a thread we should let die.  
>>>>>
>>>>> Here's a comment to those who are super confused by the numbers 
>>>>> associated with bike sizing:  it is super confusing.  Different people 
>>>>> have 
>>>>> different approaches to normalize bike fitting.  The method I use is 
>>>>> pretty 
>>>>> common, and pretty contemporary, and that is Stack and Reach.  I keep my 
>>>>> Stack and Reach numbers in my pocket and go from there.  The numb

[RBW] Re: Sizing question for "in between" PBH measurement

[Johnny Alien]

I would never question Rivendell's knowledge on anything at all but like I 
said their method of sizing bikes for people does not work for me 
personally. If you are comfortable on the 55 Salsa the 54 SH will feel a 
lot bigger. The 51 will likely feel pretty close. But I don't want to 
discourage sizing up especially if you are diving into the sweptback 
movement the kids are into these days.

On Thursday, April 18, 2024 at 8:02:45 PM UTC-4 Robert Calton wrote:

> OP here, apologies for deleting the post amidst the thoughtful 
> conversation, I thought that I got the answer I needed and didn't want to 
> clutter up the board :p 
>
> Will at Riv suggested that I size up to the 54. 
>
> The context was: compared to my current bike, a drop-bar 55cm Salsa Vaya's 
> standover of 77.6cm and top tube of 55cm...
>
> 51 Sam standover: 78.6 (+1cm from Vaya)
> 51 Sam top tube: 56.5 (+1.5cm from Vaya) 
>
> 54 Sam standover: 82.0 (+4.4cm from Vaya) 
> 54 Sam top tube:  58 (+3cm from Vaya) 
>
> An 83.8 PBH was the highest measurement out of the 10 or so times I 
> measured. Most of the time it was 81.2 - 82.5 range. I'm 5'11 with a 30" 
> inseam. Riv says a 51 Sam is 79-83 and a 54 is 83-86. That nearly 2" 
> increase of standover height gives me pause, to be honest. But eh, seems 
> that the wisdom of the riding community suggests sizing up. 
> On Thursday, April 18, 2024 at 7:56:06 PM UTC-4 Drew Fitchette wrote:
>
>> Echoing Bill on here. I also look at stack and reach, and have nearly the 
>> same dimensions as the OP
>>
>> I had a 53 Atlantis from the last run as it was correct for my PBH as I’m 
>> between the 53 and 55, after deep dives on stack and reach(in particular) I 
>> realized what made the bike *feel* small to me. I should’ve sized up to 
>> a 55 instead, and similar to Bill have now scooped a 56 hillborne from 
>> another list member as it’s the biggest size non step over riv I can fit. 
>>
>> Roman told me that the 54 Sam would feel bigger as far as 
>> standover(mostly due to the 700c wheels) but the bike might feel similar to 
>> the Atlantis for stack and the reach is shorter. He actually suggested a 
>> 60cm Plat with my seat slammed since I’m 6 ft tall. And I know Grant rides 
>> a 59cm Clem with only a slightly taller PBH than I have. 
>>
>> All that to say, I think I’ll be sizing up henceforth as I like toscos or 
>> albatross bars usually and don’t mind the straddle heigh being close!
>>
>>
>>
>> On Thursday, April 18, 2024 at 6:42:10 PM UTC-4 Bill Lindsay wrote:
>>
>>> Johnny said: "the 51 SH I owned seemed as large or larger than the 54cm 
>>> Rambo"
>>>
>>> I agree with that.  A 51 Sam is "bigger" than a 54cm Rambouillet, IMO. 
>>>  My comment had to do with the OP's height at 5'11".  A 5'11" person would 
>>> probably do best on a 60cm Ram.  At 5'10" I'd pick a 60cm if you gave me 
>>> any size I choose.  A 57 Hillborne would be a little bigger than a 60 Ram, 
>>> and a 54 Hilborne would be a little smaller.  The OP deleted their post so 
>>> it's maybe a thread we should let die.  
>>>
>>> Here's a comment to those who are super confused by the numbers 
>>> associated with bike sizing:  it is super confusing.  Different people have 
>>> different approaches to normalize bike fitting.  The method I use is pretty 
>>> common, and pretty contemporary, and that is Stack and Reach.  I keep my 
>>> Stack and Reach numbers in my pocket and go from there.  The numbers I use 
>>> are 600mm for Stack and 390mm for Reach for a roadish drop bar setup.  I 
>>> have a ton of bikes, and the names of their sizes range from 47 all the way 
>>> to 62, but are all where I want them to be in Stack and Reach.  Looking for 
>>> those numbers the 54 is right there in Stack for 5'10" me, but it's a 
>>> little short in the Reach department so I'd need to run a longer stem with 
>>> drop bars and forget about it for any kind of upright bar setup.  The extra 
>>> reach of the 57 would make an upright bar setup more straightforward, and I 
>>> could slam the stem because the stack is high.  If you have a bike that 
>>> "fits" I think it's a really good idea to figure out the Stack and Reach on 
>>> that bike and use it for comparison.  The OP on this thread said they have 
>>> a Salsa Vaya.  Looking over that geo-chart, I can say for certain I would 
>>> not ride a Salsa Vaya in any size.  None of them gets me in the 
>>> neighborhood of where I'd want to be in Stack and Reach.  I think that's 
>>

[RBW] Re: Sizing question for "in between" PBH measurement

[Johnny Alien]

With the way these bikes are designed the 51 SH I owned seemed as large or 
larger than the 54cm Rambo that I owned at the same time. For road riding I 
would not have wanted to go larger. But I also admit that I don't like 
having no standover clearance so thats part of it for me. One of the big 
reasons I like step-over/thru frames. But IMO Riv's already have fairly 
long reach and (obviousl) long wheelbases so moving up for a drop bar setup 
just seems way to stretches out. Honestly I prefer the 50cm Gallop I have 
for road stuff to the 51cm SH I had.

On Thursday, April 18, 2024 at 5:24:51 PM UTC-4 ian m wrote:

> It's pretty wild the differing opinions people have on upsizing or 
> downsizing based on cockpit choices. I'm with Bill on this, and I think Riv 
> tends to suggest smaller sizes than necessary, maybe because there's still 
> consumer pushback to running shorter stems? Everyone thinks they need a 
> 10cm for optimum handling or something. 
>
> But why would one aim for a 51 Hillborne to use drops and a 54 to use 
> sweptback bars? The reach difference is 6mm! That's less than the 
> difference between the stem you have and the next size up or down. 
>
> Maybe it's better from a consumer happiness standpoint to have customers 
> on a too small bike, as they'll feel more comfortable with the extra 
> standover clearance, and Riv has moved far more upright than even the 
> recent past. When in-between two sizes I'll always go for the largest I can 
> standover (on a roadish bike anyways)
> On Thursday, April 18, 2024 at 1:34:29 PM UTC-4 Bill Lindsay wrote:
>
>> OOPS! the OP deleted their post.  It's worth pointing out to people that 
>> this Google Group is basically an email activity.  You can delete a post, 
>> but it's deleted the same way an email is deleted.  It's out there.  
>>
>> BL in EC
>>
>> On Thursday, April 18, 2024 at 10:32:17 AM UTC-7 Bill Lindsay wrote:
>>
>>> I'm 5'10", shorter than the OP, and I think I'm between sizes on the 
>>> Hillbornebut not between 51 and 54.  I think I'm between 54 and 57 on 
>>> the Hillborne.  
>>>
>>> My Saddle Height is 75.5cm, so my PBH is probably in the 85-86 range.  I 
>>> own an older 56cm Hillborne which is perfect, used to run a 56cm Bombadil 
>>> which was perfect. 
>>>
>>> When I went to buy an original run Leo Roadini, the Riv guys leaned 
>>> towards a 54.  I was surprised because that felt like a significant 
>>> downsize.  I disagreed with them and got a 57 and it was terrific, albeit 
>>> with no standover clearance.  If I had to replace my 56 Hillborne with a 
>>> current Hillborne I'd almost definitely get a 57.  
>>>
>>> Does that make me ever more of a weird upsizer than the reputation Riv 
>>> has with people like Johnny?  I'm not sure.  The idea of a 5'11" human on a 
>>> 51cm Hillborne doesn't seem right to me.  
>>>
>>> Is your Salsa Vaya a perfect fit?  do you want to share a photo of your 
>>> setup?
>>>
>>> Bill Lindsay
>>> El Cerrito, CA
>>>
>>> On Thursday, April 18, 2024 at 9:38:33 AM UTC-7 brok...@gmail.com wrote:
>>>
>>>> I agree with Johnny. Think about how you mostly want this bike set up 
>>>> and size accordingly. You had mentioned wanting an Albatross bar setup, so 
>>>> if it were me, I would go with the 54cm and longer top tube that will play 
>>>> nicely with the swept-back bars and longer stem required for said bars. I 
>>>> also have a PBH that's between 83-84, even though I'm a little shorter 
>>>> than 
>>>> you. If I were buying a new Sam, I would purchase the 54cm size, and I 
>>>> would probably also run some sort of swept-back cockpit. I already have a 
>>>> drop bar Riv, and a fat-tired Riv, and those are the only two factors that 
>>>> would make me want to size down to a 51cm.
>>>>
>>>> Brian
>>>> Lex KY
>>>>
>>>> On Thursday, April 18, 2024 at 11:40:27 AM UTC-4 Johnny Alien wrote:
>>>>
>>>>> I am between sizes as well and my general rule is...if I want a more 
>>>>> traditional setup/fit (maybe with drop bars) I size down. If I want to go 
>>>>> laid back, more sweptback style I go up. With your PBH if you want drops 
>>>>> go 
>>>>> with the 51 otherwise the 54 might be best. If you want to size up but 
>>>>> the 
>>>>> standover gives you pause then consider a Platypus. I understand the 
>>>>> advice 
>>>>> to call Rivendell but (from

[RBW] Re: Sizing question for "in between" PBH measurement

[Johnny Alien]

I am between sizes as well and my general rule is...if I want a more 
traditional setup/fit (maybe with drop bars) I size down. If I want to go 
laid back, more sweptback style I go up. With your PBH if you want drops go 
with the 51 otherwise the 54 might be best. If you want to size up but the 
standover gives you pause then consider a Platypus. I understand the advice 
to call Rivendell but (from my experience) they are almost always going to 
push you into a go larger direction and that has not historically always 
worked for me.

On Thursday, April 18, 2024 at 11:20:35 AM UTC-4 DavidP wrote:

> Oooh, a new Sam - exciting!
>
> 1) Send Riv an email and get their recommendation, they're great with this 
> stuff.
>
> 2) I'm a similar height but have an 87cm PBH. With your torso length I'm 
> guessing you'll want more reach, the concern is the standover on the 54cm 
> Sam if you max out the tires. Either way you'll probably want a long stem 
> on that Albatross. My 58cm top tube Albatross bike has a 120mm stem. The 
> drop tube bikes (Susie, Platypus, Clem) are great for getting a longer fit 
> without worrying about standover; I'm on a 60cm Platypus and the reach is 
> luxurious.
>
> -Dave
>
> On Thursday, April 18, 2024 at 10:43:16 AM UTC-4 Robert Calton wrote:
>
>> Haven't had luck pinning down a used bike this last week, so I'm thinking 
>> I might try and buy a new Sam in May/June with the refresh and I don't know 
>> if the 51 or 54 frame size is the right choice. Compared to my current 
>> bike, a 55cm Salsa Vaya's standover of 77.6cm and top tube of 55cm...
>>
>> 51 Sam standover: 78.6 (+1cm from Vaya)
>> 51 Sam top tube: 56.5 (+1.5cm from Vaya) 
>>
>> 54 Sam standover: 82.0 (+4.4cm from Vaya) 
>> 54 Sam top tube:  58 (+3cm from Vaya) 
>>
>> An 83.8 PBH was the highest measurement out of the 10 or so times I 
>> measured. Most of the time it was 81.2 - 82.5 range. I'm 5'11 with a 30" 
>> inseam. Riv says a 51 Sam is 79-83 and a 54 is 83-86. 
>>
>> I would like to run Albatross bars and be comfy about it. 
>>
>> Which frame size should I choose? 
>>
>>
>>

-- 
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/d78fb308-6950-48e5-9a1f-d51f0ccd3af0n%40googlegroups.com.

[RBW] Re: FS: Sam Hillborne 51cm $200/obo

[Johnny Alien]

I believe that is blue not sage. Blue was available as a 51 frame.

On Tuesday, April 16, 2024 at 10:08:03 PM UTC-4 nca...@gmail.com wrote:

> Hi Doug, thanks again for some insight. It seems they didn't make a 51 in 
> the 2009 sage frame runs, it went from 48 to 52 and that measurement seems 
> too big to be a 48. Unless they had sage frames in the 2017 run of 51's, 
> that is, but I'm not sure when the color switch happened. 
>
> On Tuesday, April 16, 2024 at 9:32:56 PM UTC-4 Doug H. wrote:
>
>> I'm thinking that this is a size 51 maybe since Riv uses the seat tube 
>> measurement for the listed sizes.
>> Doug
>>
>> On Tuesday, April 16, 2024 at 8:23:55 PM UTC-4 nca...@gmail.com wrote:
>>
>>> Thank you for those measurements. I'm trying to determine if this is 
>>> indeed the 52cm frame, but alas this older geometry chart 
>>> 
>>>  doesn't 
>>> show those two measurements you gave. I hate to trouble you further, but 
>>> would it be possible to measure the top tube? That should determine 
>>> definitively which it is, as that chart does have that measurement.
>>>
>>> On Tuesday, April 16, 2024 at 8:02:29 PM UTC-4 johnb wrote:
>>>
 Measurement from center of BB to top of TT is 20". Center of BB to top 
 of Seat Tube is 20.25". Same for TT. I apologize for the confusion. I 
 bought the bike 3rd hand and never measured it. I just took the sellers 
 word and quite honestly I could have just misremembered it.  I am 5'6" 
  with a 28" inseam. I have Compass 650Bx48 tires on the bike and I barely 
 clear the TT..

 I forgot the Crank Brothers Stamp pedals.

 On Tuesday, April 16, 2024 at 11:50:22 AM UTC-4 nca...@gmail.com wrote:

> Thanks Doug for the insight! I'll give Riv a call tomorrow and ask 
> them about the PBH range for the 52, though I suspect that would be my 
> size 
> in this model given the other geometry :) 
>
> On Sunday, April 14, 2024 at 1:53:36 PM UTC-4 Doug H. wrote:
>
>> I see on Bike Insights that Rivendell made a size 52 in 2009. I don't 
>> know how accurate those numbers are on that website though. If the 
>> numbers 
>> are accurate, they show a 57 effective top tube and 650b wheels. That is 
>> a 
>> nice looking build with nice parts.
>> Doug
>>
>> On Sunday, April 14, 2024 at 2:39:03 AM UTC-4 nca...@gmail.com wrote:
>>
>>> Good evening John. I'm sorry to hear about your reasons for selling 
>>> and hope all is well, but I am very interested in this lovely 
>>> Hillborne. I 
>>> just wanted to double-check the size on it before I commit. The listing 
>>> says 53cm but I can't seem to find Rivendell's dimensions on a 53cm: on 
>>> their site they have 51cm or 54cm. Could you please confirm if it is 
>>> 54cm 
>>> or indeed 53cm? I have a PBH of 83.8, which puts me in a 54cm, but I'm 
>>> sure 
>>> a 53 would be fine too.  
>>>
>>> All the best,
>>> Robert 
>>>
>>> On Thursday, April 11, 2024 at 9:13:42 AM UTC-4 johnb wrote:
>>>
 Due to a progressive medical issue, my beloved Rivs have to go. 
 First up, a 53cm Sam Hillborne that includes:

- New Albion cranks 46/30
- Paul brake levers
- Tektro brakes
- Hand built (velocity/Velo Orange) wheels/Rene Herse 48 tires
- 9-speed cassette
- Acera derailleur 
- Cambium Special Edition C-17 with orange rivets
- Albatross handlebars 
- Paul thumbies 

 Will be professionally packed by bike shop. Next up, 51cm Atlantis

 Photos: https://share.icloud.com/photos/075HDkT5H9Rkyy65vqo4lel2w

>>>

-- 
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/c7fb215d-feb3-4ef4-8496-742ea311bea9n%40googlegroups.com.

[jira] [Assigned] (KAFKA-13105) Expose a method in KafkaConfig to write the configs to a logger

[Johnny Hsu (Jira)]

 [ 
https://issues.apache.org/jira/browse/KAFKA-13105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Johnny Hsu reassigned KAFKA-13105:
--

Assignee: Johnny Hsu

> Expose a method in KafkaConfig to write the configs to a logger
> ---
>
> Key: KAFKA-13105
> URL: https://issues.apache.org/jira/browse/KAFKA-13105
> Project: Kafka
>  Issue Type: Improvement
>Reporter: Colin McCabe
>    Assignee: Johnny Hsu
>Priority: Minor
>  Labels: 4.0-blocker
>
> We should expose a method in KafkaConfig to write the configs to a logger. 
> Currently there is no good way to write them out except creating a new 
> KafkaConfig object with doLog = true, which is unintuitive.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[RBW] Re: Rosco MMM build photos

[Johnny Alien]

Love it!!!

On Monday, April 15, 2024 at 8:59:50 PM UTC-4 Kainalu V. -Brooklyn NY wrote:

> Wowzers!  That is beautiful, but it’s no MMM…
> WMM or JMM (Will or Jumbo) maybe, but nowheres close to Medium 
> Happy shredding!
> -Kai
> On Monday, April 15, 2024 at 8:28:30 PM UTC-4 Stephen wrote:
>
>> Couple more:
>>
>> [image: IMG_6627.jpg]
>>
>> [image: IMG_6629.jpg]
>>
>> [image: IMG_6630.jpg]
>> On Monday, April 15, 2024 at 8:27:06 PM UTC-4 Stephen wrote:
>>
>>> Howdy,
>>>
>>> Wanted to share some pics of my (sorta) recently new to me rosco as I 
>>> settle in and keep personalizing it. 
>>>
>>> I bought this bike from list member Kai back in February I think. I 
>>> really wasn't trying to expand the stable at that moment, but the riv mixte 
>>> propaganda had been working on my subconscious and Kai was selling this 
>>> thing a 15 minute ride away, and well, in the end I couldn't help myself. 
>>>
>>> This past week or so I've been diving into a serious bicycle spring 
>>> cleaning strip down /regrease/relube/ wipe off all the winter city scuzz 
>>> /etc.. from my bikes and its been an opportunity to try some new things 
>>> with the rosco, and I'm really liking how its turning out. Just using what 
>>> I have around, and stealing some parts from my appaloosa.
>>>
>>> Couple of my favorite things about this build so far: Got the used 
>>> maxxis tires at the charlotte bike coop for $10 each to see how big o' 
>>> meats this frame can take. Getting a little close to those v brake cables.. 
>>> I'll probably drop back down to 2.25s for the day to day, but these big 
>>> ones are fun. And I've had this nos xtr FD sitting in a drawer for a couple 
>>> years because I bought it at a swap before I knew to think about the clamp 
>>> size and its a 34.9. This bike has a 31.8 tube, and I was able to shim the 
>>> derailer by cutting a plastic 35mm film canister. Very happy thats working. 
>>>
>>> Hope y'all enjoy taking a gander at the bike:
>>>
>>> Build notes:
>>> 60cm Tosco's
>>> old ass oury grips
>>> avid 1.9 Speed dial levers
>>> riv silver 2 thumbies 
>>> nitto 11cm talux
>>> stock fsa headset
>>> stock kalloy seatpost
>>> imperial brooks (gooch cutout)
>>> Avid 2.0 V brakes w/koolstops 
>>> Wheelset: Cliffhangers to SON28 and a Deore
>>> 2.4 tire in the back, 2.5 in the front
>>> Sugino/white industries triple crankset (22/36/44)
>>> mismatchy monarch pedals
>>> XTR M9sumthin FD
>>> XTR Rapid Rise RD
>>> XT 11-34 cassette
>>> one of those blingy gold kmc chains
>>>
>>> [image: IMG_6619.jpg]
>>>
>>> [image: IMG_6622.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/8f60c5b4-8782-43ec-9960-9bc3dd76c4b9n%40googlegroups.com.

[jira] [Commented] (KAFKA-13105) Expose a method in KafkaConfig to write the configs to a logger

[Johnny Hsu (Jira)]

[ 
https://issues.apache.org/jira/browse/KAFKA-13105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17837366#comment-17837366
 ] 

Johnny Hsu commented on KAFKA-13105:


hi [~cmccabe] I would like to work on this if no one is on it now :D

> Expose a method in KafkaConfig to write the configs to a logger
> ---
>
> Key: KAFKA-13105
> URL: https://issues.apache.org/jira/browse/KAFKA-13105
> Project: Kafka
>  Issue Type: Improvement
>Reporter: Colin McCabe
>Priority: Minor
>  Labels: 4.0-blocker
>
> We should expose a method in KafkaConfig to write the configs to a logger. 
> Currently there is no good way to write them out except creating a new 
> KafkaConfig object with doLog = true, which is unintuitive.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Re: [call to action] submit your ideas for OSPP 2024

[Johnny Jazeix]

Hi,

for info, KDE has registered to OSPP and Burgess will lead the
administration part for KDE.

Thanks to him and hoping there will be proposals from KDE!

Johnny

Le lun. 8 avr. 2024 à 23:40, Burgess Chang  a écrit :

> Hi,
>
> KDE has registered for the Open Source Promotion Plan (OSPP) program
> this year, which is a regional (China) program provides support for open
> source communities, yet another GSoC. We'd like to invite the community
> to submit ideas for OSPP 2024. Deadline to do is *Friday, April 26, 2024*.
>
> https://community.kde.org/OSPP/2024/Ideas
>
> All community members are welcome to submit ideas. If you have an idea,
> make sure that your project maintainer is aware of your intentions. If
> not, do not add the project there.
>
> This year, we are encouraging members to submit ideas for projects
> that would improve Chinese localization or support for the RISC-V
> platform. Here are some possible ideas:
>
> - Software that lacks Chinese localization support.
> - Add Chinese features and translations to KDE applications, such as
>   lunar calendar support, Chinese characters/word sorting, input method,
>   Chinese spell-checking, and so on.
> - Improve the availability and performance of KDE software on the RISC-V
>   platform.
>
> And your ideas are not limited only to coding tasks and you can include
> projects related to documentation, translation.
>
> For more information see https://community.kde.org/OSPP. We recommend
> you to read this page before submitting an idea, as there are some
> differences between OSPP and SoK/GSoC.
>
> Let's move forward in this program.
>
> Regards,
> Burgess Chang
> (on behalf of the KDE-OSPP team)
> --
> Burgess Chang
> Pronouns: He/Him/His
> OpenPGP: 7B740DB9F2AC6D3B226BC53078D74502D92E0218
>

[RBW] Re: Soliciting opinions: help me pick the right Rivendell

[Johnny Alien]

I like to think outside the box. Comfortable, nimble, useful..Platypus

On Friday, April 5, 2024 at 10:16:21 PM UTC-4 Luke Hendrickson wrote:

> [image: R0004896.jpeg]
> I suggest the Atlantis, though I am biased as I have one. I have it on 
> good authority that the last run of them was also the last with a double 
> TT. Moving forward, the Atlantis will have a single TT.
>
> I have racked my bike, unracked it, fendered it, have a BOB trailer for 
> it, commute 150 miles a week on it, climb up huge dirt passes, descend 
> roads faster than I should while in an aero tuck (a little hard given I 
> have a 62 and am 6’6”), and overall just really love it. So versatile, so 
> comfortable, and so pretty.
> On Friday, April 5, 2024 at 5:55:08 PM UTC-7 aeroperf wrote:
>
>> Get a Sam with a 3x9 drive.
>> Strong enough to do the riding you want, versatile enough for errands and 
>> light touring, and very comfortable.
>>
>>

-- 
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/141fccd5-d937-4f9d-9130-d403cd3b893fn%40googlegroups.com.

Re: [RBW] Building up a 45cm Clem for a 5'2 rider

[Johnny Alien]

That is the stem (FW33) I ultimately chose as well.

I agree the Albatross is a pretty decent bar for doing the forward position 
because it doesn't come back as far as the others but to do it properly you 
have to concede that that one of the positions won't be as ideal. I use the 
loscos and they work very well too. If you set it really far forward to 
account for the sweep back then the forward position is not great to be in 
for long. If you set it to be comfortable in the forward position the 
upright is sometimes not great. The losco and albatross counter that pretty 
well. I never understood the multi position angle that Riv takes but then 
tell you you need a really long stem to counter the sweep. That puts the 
forward position way out there. So yeah if you want to use both get one 
with less sweep and rise/ Thats been what has worked for me.

On Friday, April 5, 2024 at 11:19:05 AM UTC-4 Igor wrote:

> For what it's worth, I tried a Nitto FW33 stem (120mm, too long for her 
> imagine...) and it can be "slammed" in the head tube of this 45cm. I've got 
> all of the spacers on the headset and have not/will not cut the steerer of 
> the fork either. I need to measure the stem quill length.. 
> https://global.bluelug.com/nitto-fw30-power-stem-dull.html
>
> On Friday, April 5, 2024 at 10:46:13 AM UTC-4 rmro...@gmail.com wrote:
>
>> My experience on my Clem is quite the opposite of Garth’s. I do 
>> understand that my situation may be unique but it is what it is. 45 degree 
>> forward simply does not work for me. Bolt upright is the only way I can 
>> achieve a no numb hands position. Going into the wind I will assume a more 
>> forward leaning position but I cannot stay there very long. Numbness is 
>> almost immediately. I ride my Clem for hours with virtually no weight on my 
>> hands. And yes, my saddle is in the perfect vertical & horizontal position 
>> relative to the bottom bracket. I have ridden in this position, Bosco’s 
>> 2”-3” above saddle height, for 2 years & over 7,000 miles. No numb hands.
>> Sent from my iPhone
>>
>> On Apr 5, 2024, at 9:24 AM, Garth  wrote:
>>
>> An Albatoross is best for being in a forward, say 45d angle in a swept 
>> back style bar. If you use reverse Tektro brake levers, tape the bar up to 
>> and just around the top bend, then put thumbshiters there, that's about a 
>> "racey upright" as one can get using 45d body position as a base. All the 
>> other swept back bars, with regular MTB levers and grips at the ends, is 
>> just all wrong for what I'm referring to as the bars come back too far, 
>> requiring more weight on the arms and hands. When you lean forward, with 
>> proper forward seat placement in relation to the BB so you're using your 
>> legs and core to support yourself(not unlike riding a unicycle), having 
>> your arms extended forward exerts less pressure on the arms and hands. I 
>> think shallow, wide flared drop bars could also work if more hand positions 
>> are desired. 
>>
>>
>> On Friday, April 5, 2024 at 9:02:00 AM UTC-4 Johnny Alien wrote:
>>
>>> Note when choosing stem (as I see a Faceplater was suggested), the 
>>> smaller sizes have headtubes that don't go very deep. I face this on the 
>>> 50-52 sizes. Those SUPER tall stems that Rivendell sells will not go very 
>>> far in and thus you are forced to have a ton of stem exposed. Couple that 
>>> with a bar like the Bosco and you will be way way way up with no way to get 
>>> it lower. Pick up a stem that does not have the super long lengths. Go 
>>> short even if you have any uprise to it or are planning to use handlebars 
>>> that also have height. 
>>>
>>> The losco bars are my favorite bars and perfect for a racy upright mix. 
>>> Also they are the best looking bars that Riv sells (IMO)
>>>
>>> On Friday, April 5, 2024 at 8:48:53 AM UTC-4 Igor wrote:
>>>
>>>> This is a 2023 45cm Clem.
>>>>
>>>>  I'm looking at putting her in a somewhat middle between racy and 
>>>> upright. Bosco could work for that I imagine, with the shifters and levers 
>>>> further up and gives her options. 
>>>> Alternatively was thinking Losco could be good, too.  Might have her 
>>>> try the Vegan saddle as well.
>>>>
>>>> On Friday, April 5, 2024 at 5:06:06 AM UTC-4 John Johnson wrote:
>>>>
>>>>> Hi Igor,
>>>>>
>>>>> For a 5'2" rider (I'm not going to assume it's for a lady or for your 
>>>>> friend!), the 45cm Clem is perfect. Obviously there is no "objective" 
>&

Re: [RBW] Building up a 45cm Clem for a 5'2 rider

[Johnny Alien]

Note when choosing stem (as I see a Faceplater was suggested), the smaller 
sizes have headtubes that don't go very deep. I face this on the 50-52 
sizes. Those SUPER tall stems that Rivendell sells will not go very far in 
and thus you are forced to have a ton of stem exposed. Couple that with a 
bar like the Bosco and you will be way way way up with no way to get it 
lower. Pick up a stem that does not have the super long lengths. Go short 
even if you have any uprise to it or are planning to use handlebars that 
also have height. 

The losco bars are my favorite bars and perfect for a racy upright mix. 
Also they are the best looking bars that Riv sells (IMO)

On Friday, April 5, 2024 at 8:48:53 AM UTC-4 Igor wrote:

> This is a 2023 45cm Clem.
>
>  I'm looking at putting her in a somewhat middle between racy and upright. 
> Bosco could work for that I imagine, with the shifters and levers further 
> up and gives her options. 
> Alternatively was thinking Losco could be good, too.  Might have her try 
> the Vegan saddle as well.
>
> On Friday, April 5, 2024 at 5:06:06 AM UTC-4 John Johnson wrote:
>
>> Hi Igor,
>>
>> For a 5'2" rider (I'm not going to assume it's for a lady or for your 
>> friend!), the 45cm Clem is perfect. Obviously there is no "objective" right 
>> answer for which bars to use, and it's gonna depend on different factors (I 
>> know I'm not dropping any mind-blowing information, but just to lay the 
>> groundwork for my suggestions). 
>> I'd ask the following questions:
>>
>>- What year Clem is it? The older Clems had shorter top tubes (less 
>>reach) than the newer (2019 and post) models. 
>>- What is the intended use? Tooling around, commuting, touring, 
>>mountain biking? 
>>- How does the rider like to be positioned? Aggressive and racy? 
>>Upright and comfy? 
>>- What is the rider's morphology? Long torso, short legs? Long legs, 
>>short torso? Normal legs, normal torso?
>>- Are there aesthetic considerations? 
>>- Are there cost considerations?
>>
>> For me (an N of 1 - I am 5'8", longer torso with very short legs, for 
>> reference), I currently ride a Clem 45 L (longer reach 2019 model, but 
>> still with 26" wheels before the switch to 27.5") with a 70cm Nitto Tallux 
>> at the minimum insertion and 60cm Tosco bars and I couldn't be happier. My 
>> wife rides a Clem 45 L with Soma Oxford bars and I really like that set up 
>> too, but I find the Oxfords at 54cm (identical to Nitto Albatross) a tad 
>> bit narrow for my taste. I rode my pre-2019 Clem H with a Riv Bullmoose 
>> (67cm) and it was totally great - but I was running that bike single speed 
>> and as a dedicated mountain bike - I don't love the 30° sweep for longer 
>> rides (on longer rides, I want 45-60° sweep). I tried Boscos for a minute 
>> (I think it was the 54cm that came stock on my wife's Clem), but I felt 
>> almost cartoonishly upright and didn't feel connected enough with the bike. 
>>
>> For your rider, at 5'2", I'm guessing you have a newer (post 2019 geo 
>> changes) Clem and it's likely they'll want swept back bars of some sort. I 
>> think the Albatross (or Soma Oxford) are perfect for the Clem  - right 
>> rise, sweep, width, and good looking to boot. The Toscos, like I mentioned, 
>> are great, but I'd opt for the 55cm model probably in your rider's case. 
>> Re: the Boscos, I'm a bit taller than your rider, so maybe Boscos would do 
>> the trick in their case. Lastly, if they don't want a relaxed position, 
>> you've got a billion options of flat or riser bars with minimal sweep, but 
>> I won't bother with recs. 
>>
>>
>>
>> cheers,
>>
>> John (outside Fontainebleau)
>>
>>
>> On Friday, April 5, 2024 at 6:36:58 AM UTC+2 Kim H. wrote:
>>
>>> @Igor -
>>> I have a couple of Terry women's saddles that are lightly used to sell, 
>>> if you are interested for your lady friend.
>>>
>>> https://www.terrybicycles.com/Cite-X-Gel-Italia
>>>
>>> https://www.terrybicycles.com/Liberator-X
>>>
>>> Contact me off this group for more details and pictures.
>>>
>>> Kim Hetzel. 
>>>
>>> On Thursday, April 4, 2024 at 7:52:34 PM UTC-7 Richard Rose wrote:
>>>
 A lot of nice bars to choose from. That said, the Bosco is perfect. The 
 extra rise is great as it results in less stem exposed than with the 
 Tosco. 
 I suggest one of the three FacePlater stems makes life so much easier & 
 the 
 older tig welded one is currently on sale, I think. But, without the frame 
 & handlebar at hand it’s guesswork at best regarding stem length. I am 
 5’10”, ride a 52 Clem with Bosco & 135 FacePlater. I do not know how much 
 shorter the reach is on the 45, but I would guess a stem closer to 70-80? 
 Call Riv & ask them, they give excellent advice. Or, try to get your hands 
 n a few different (cheap) stems to try?
 Sent from my iPhone

 On Apr 4, 2024, at 9:28 PM, Igor  wrote:

 Any suggestions or ways to "know" what stem or 

[jira] [Commented] (KAFKA-16475) Create unit test for TopicImageNode

[Johnny Hsu (Jira)]

[ 
https://issues.apache.org/jira/browse/KAFKA-16475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17834261#comment-17834261
 ] 

Johnny Hsu commented on KAFKA-16475:


hi [~cmccabe] 
I am willing to work on this ticket, thanks! 

> Create unit test for TopicImageNode
> ---
>
> Key: KAFKA-16475
> URL: https://issues.apache.org/jira/browse/KAFKA-16475
> Project: Kafka
>  Issue Type: Improvement
>Reporter: Colin McCabe
>Priority: Major
>




--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Assigned] (KAFKA-16475) Create unit test for TopicImageNode

[Johnny Hsu (Jira)]

 [ 
https://issues.apache.org/jira/browse/KAFKA-16475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Johnny Hsu reassigned KAFKA-16475:
--

Assignee: Johnny Hsu

> Create unit test for TopicImageNode
> ---
>
> Key: KAFKA-16475
> URL: https://issues.apache.org/jira/browse/KAFKA-16475
> Project: Kafka
>  Issue Type: Improvement
>Reporter: Colin McCabe
>    Assignee: Johnny Hsu
>Priority: Major
>




--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[CentOS-announce] CEBA-2024:1540 CentOS 7 redhat-support-tool BugFix Update

[Johnny Hughes]

CentOS Errata and Bugfix Advisory 2024:1540 

Upstream details at : https://access.redhat.com/errata/RHBA-2024:1540

The following updated files have been uploaded and are currently 
syncing to the mirrors: ( sha256sum Filename ) 

x86_64:
096e36a0f28a54f5ad7c593b2efd58ee933bf7f9c314927179a6d0244e0a596a  
redhat-support-tool-0.14.0-1.el7_9.noarch.rpm

Source:
a470b95be4f9036778b3805dd90ad0bc8b196f7a847826345e04fb9da5e963dd  
redhat-support-tool-0.14.0-1.el7_9.src.rpm



-- 
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@libera.chat
Twitter: @JohnnyCentOS

___
CentOS-announce mailing list
CentOS-announce@centos.org
https://lists.centos.org/mailman/listinfo/centos-announce

[CentOS-announce] CEBA-2024:1540 CentOS 7 redhat-support-lib-python BugFix Update

[Johnny Hughes]

CentOS Errata and Bugfix Advisory 2024:1540 

Upstream details at : https://access.redhat.com/errata/RHBA-2024:1540

The following updated files have been uploaded and are currently 
syncing to the mirrors: ( sha256sum Filename ) 

x86_64:
623f1a82453fc1bd44617826a88974cd43fbbb30a2d72e47bd706b0deb895254  
redhat-support-lib-python-0.14.0-1.el7_9.noarch.rpm

Source:
4492c7df1e69f89395e1347815fd9bafe952d299b2b29541c850ad72a553939e  
redhat-support-lib-python-0.14.0-1.el7_9.src.rpm



-- 
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@libera.chat
Twitter: @JohnnyCentOS

___
CentOS-announce mailing list
CentOS-announce@centos.org
https://lists.centos.org/mailman/listinfo/centos-announce

[CentOS-announce] CESA-2024:1498 Moderate CentOS 7 thunderbird Security Update

[Johnny Hughes]

CentOS Errata and Security Advisory 2024:1498 Moderate

Upstream details at : https://access.redhat.com/errata/RHSA-2024:1498

The following updated files have been uploaded and are currently 
syncing to the mirrors: ( sha256sum Filename ) 

x86_64:
de56cf10dbbabd9a55f388bacf02eb1f5bb04b430bbad9a217d6dc57141aaeb5  
thunderbird-115.9.0-1.el7.centos.x86_64.rpm

Source:
2a36182ee2aeb5bbdb7c973d6d48bc6a4a929f8d3a3b0c8ffd8e35debc2ce22f  
thunderbird-115.9.0-1.el7.centos.src.rpm



-- 
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@libera.chat
Twitter: @JohnnyCentOS

___
CentOS-announce mailing list
CentOS-announce@centos.org
https://lists.centos.org/mailman/listinfo/centos-announce

[CentOS-announce] CESA-2024:1486 Critical CentOS 7 firefox Security Update

[Johnny Hughes]

CentOS Errata and Security Advisory 2024:1486 Critical

Upstream details at : https://access.redhat.com/errata/RHSA-2024:1486

The following updated files have been uploaded and are currently 
syncing to the mirrors: ( sha256sum Filename ) 

x86_64:
33dd225ef7b01c077e7d0977782fa69f3d8fd4cea6363f4cde213cc37694b3a2  
firefox-115.9.1-1.el7.centos.i686.rpm
2f160bf3a57455fd82821ea858e6ab2789596f1ae502a2b3968383670f17296f  
firefox-115.9.1-1.el7.centos.x86_64.rpm

Source:
3267298df86f1f220840ce663243282de3bd1cdbe0eabd1485f3f01ad1ae07ec  
firefox-115.9.1-1.el7.centos.src.rpm



-- 
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@libera.chat
Twitter: @JohnnyCentOS

___
CentOS-announce mailing list
CentOS-announce@centos.org
https://lists.centos.org/mailman/listinfo/centos-announce

[i18n] [Bug 484810] Mauvaise traduction de "Display luminosité" dans l'applet "Luminosité et couleur"

[Jazeix Johnny]

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

Jazeix Johnny  changed:

   What|Removed |Added

 CC||jaz...@gmail.com

--- Comment #2 from Jazeix Johnny  ---
Bonjour,

juste en rapide car je ne souhaite pas m'étendre sur le sujet (HS pour le bug),
Carl a développé un embryon d'outil en ligne et en a discuté sur la liste
https://mail.kde.org/pipermail/kde-i18n-doc/2024-March/002172.html.

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

[jira] [Assigned] (KAFKA-13906) Invalid replica state transition

[Johnny Hsu (Jira)]

 [ 
https://issues.apache.org/jira/browse/KAFKA-13906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Johnny Hsu reassigned KAFKA-13906:
--

Assignee: Johnny Hsu

> Invalid replica state transition
> 
>
> Key: KAFKA-13906
> URL: https://issues.apache.org/jira/browse/KAFKA-13906
> Project: Kafka
>  Issue Type: Bug
>  Components: controller, core, replication
>Affects Versions: 3.1.0, 3.0.0, 3.0.1, 3.2.0, 3.1.1, 3.3.0, 3.0.2, 3.1.2, 
> 3.2.1
>Reporter: Igor Soarez
>Assignee: Johnny Hsu
>Priority: Major
>  Labels: BUG, controller, replication, reproducible-bug
>
> The controller runs into an IllegalStateException when reacting to changes in 
> broker membership status if there are topics that are pending deletion.
>  
> How to reproduce:
>  # Setup cluster with 3 brokers
>  # Create a topic with a partition being led by each broker and produce some 
> data
>  # Kill one of the brokers that is not the controller, and keep that broker 
> down
>  # Delete the topic
>  # Restart the other broker that is not the controller
>  
> Logs and stacktrace:
> {{[2022-05-16 11:53:25,482] ERROR [Controller id=1 epoch=1] Controller 1 
> epoch 1 initiated state change of replica 3 for partition test-topic-2 from 
> ReplicaDeletionSuccessful to ReplicaDeletionIneligible failed 
> (state.change.logger)}}
> {{java.lang.IllegalStateException: Replica 
> [Topic=test-topic,Partition=2,Replica=3] should be in the 
> OfflineReplica,ReplicaDeletionStarted states before moving to 
> ReplicaDeletionIneligible state. Instead it is in ReplicaDeletionSuccessful 
> state}}
> {{        at 
> kafka.controller.ZkReplicaStateMachine.logInvalidTransition(ReplicaStateMachine.scala:442)}}
> {{        at 
> kafka.controller.ZkReplicaStateMachine.$anonfun$doHandleStateChanges$2(ReplicaStateMachine.scala:164)}}
> {{        at 
> kafka.controller.ZkReplicaStateMachine.$anonfun$doHandleStateChanges$2$adapted(ReplicaStateMachine.scala:164)}}
> {{        at scala.collection.immutable.List.foreach(List.scala:333)}}
> {{        at 
> kafka.controller.ZkReplicaStateMachine.doHandleStateChanges(ReplicaStateMachine.scala:164)}}
> {{        at 
> kafka.controller.ZkReplicaStateMachine.$anonfun$handleStateChanges$2(ReplicaStateMachine.scala:112)}}
> {{        at 
> kafka.controller.ZkReplicaStateMachine.$anonfun$handleStateChanges$2$adapted(ReplicaStateMachine.scala:111)}}
> {{        at 
> kafka.utils.Implicits$MapExtensionMethods$.$anonfun$forKeyValue$1(Implicits.scala:62)}}
> {{        at 
> scala.collection.immutable.HashMap.foreachEntry(HashMap.scala:1092)}}
> {{        at 
> kafka.controller.ZkReplicaStateMachine.handleStateChanges(ReplicaStateMachine.scala:111)}}
> {{        at 
> kafka.controller.TopicDeletionManager.failReplicaDeletion(TopicDeletionManager.scala:157)}}
> {{        at 
> kafka.controller.KafkaController.onReplicasBecomeOffline(KafkaController.scala:638)}}
> {{        at 
> kafka.controller.KafkaController.onBrokerFailure(KafkaController.scala:599)}}
> {{        at 
> kafka.controller.KafkaController.processBrokerChange(KafkaController.scala:1623)}}
> {{        at 
> kafka.controller.KafkaController.process(KafkaController.scala:2534)}}
> {{        at 
> kafka.controller.QueuedEvent.process(ControllerEventManager.scala:52)}}
> {{        at 
> kafka.controller.ControllerEventManager$ControllerEventThread.process$1(ControllerEventManager.scala:130)}}
> {{--}}
> {{[2022-05-16 11:53:40,726] ERROR [Controller id=1 epoch=1] Controller 1 
> epoch 1 initiated state change of replica 3 for partition test-topic-2 from 
> ReplicaDeletionSuccessful to OnlineReplica failed (state.change.logger)}}
> {{java.lang.IllegalStateException: Replica 
> [Topic=test-topic,Partition=2,Replica=3] should be in the 
> NewReplica,OnlineReplica,OfflineReplica,ReplicaDeletionIneligible states 
> before moving to OnlineReplica state. Instead it is in 
> ReplicaDeletionSuccessful state}}
> {{        at 
> kafka.controller.ZkReplicaStateMachine.logInvalidTransition(ReplicaStateMachine.scala:442)}}
> {{        at 
> kafka.controller.ZkReplicaStateMachine.$anonfun$doHandleStateChanges$2(ReplicaStateMachine.scala:164)}}
> {{        at 
> kafka.controller.ZkReplicaStateMachine.$anonfun$doHandleStateChanges$2$adapted(ReplicaStateMachine.scala:164)}}
> {{        at scala.collection.immutable.List.foreach(List.scala:333)}}
> {{        at 
> kafka.controller.ZkReplicaStateMachine.doHandleStateChanges(ReplicaStateMachine.scala:164)}}
> {{        at 
> kafka.controller.ZkReplicaStateMachine.$anonfun$handleState

[jira] [Commented] (KAFKA-13906) Invalid replica state transition

[Johnny Hsu (Jira)]

[ 
https://issues.apache.org/jira/browse/KAFKA-13906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17832368#comment-17832368
 ] 

Johnny Hsu commented on KAFKA-13906:


hey [~soarez] [~showuon] I would like to work on this, let me assign this to 
myself, thanks for reporting this

> Invalid replica state transition
> 
>
> Key: KAFKA-13906
> URL: https://issues.apache.org/jira/browse/KAFKA-13906
> Project: Kafka
>  Issue Type: Bug
>  Components: controller, core, replication
>Affects Versions: 3.1.0, 3.0.0, 3.0.1, 3.2.0, 3.1.1, 3.3.0, 3.0.2, 3.1.2, 
> 3.2.1
>Reporter: Igor Soarez
>Priority: Major
>  Labels: BUG, controller, replication, reproducible-bug
>
> The controller runs into an IllegalStateException when reacting to changes in 
> broker membership status if there are topics that are pending deletion.
>  
> How to reproduce:
>  # Setup cluster with 3 brokers
>  # Create a topic with a partition being led by each broker and produce some 
> data
>  # Kill one of the brokers that is not the controller, and keep that broker 
> down
>  # Delete the topic
>  # Restart the other broker that is not the controller
>  
> Logs and stacktrace:
> {{[2022-05-16 11:53:25,482] ERROR [Controller id=1 epoch=1] Controller 1 
> epoch 1 initiated state change of replica 3 for partition test-topic-2 from 
> ReplicaDeletionSuccessful to ReplicaDeletionIneligible failed 
> (state.change.logger)}}
> {{java.lang.IllegalStateException: Replica 
> [Topic=test-topic,Partition=2,Replica=3] should be in the 
> OfflineReplica,ReplicaDeletionStarted states before moving to 
> ReplicaDeletionIneligible state. Instead it is in ReplicaDeletionSuccessful 
> state}}
> {{        at 
> kafka.controller.ZkReplicaStateMachine.logInvalidTransition(ReplicaStateMachine.scala:442)}}
> {{        at 
> kafka.controller.ZkReplicaStateMachine.$anonfun$doHandleStateChanges$2(ReplicaStateMachine.scala:164)}}
> {{        at 
> kafka.controller.ZkReplicaStateMachine.$anonfun$doHandleStateChanges$2$adapted(ReplicaStateMachine.scala:164)}}
> {{        at scala.collection.immutable.List.foreach(List.scala:333)}}
> {{        at 
> kafka.controller.ZkReplicaStateMachine.doHandleStateChanges(ReplicaStateMachine.scala:164)}}
> {{        at 
> kafka.controller.ZkReplicaStateMachine.$anonfun$handleStateChanges$2(ReplicaStateMachine.scala:112)}}
> {{        at 
> kafka.controller.ZkReplicaStateMachine.$anonfun$handleStateChanges$2$adapted(ReplicaStateMachine.scala:111)}}
> {{        at 
> kafka.utils.Implicits$MapExtensionMethods$.$anonfun$forKeyValue$1(Implicits.scala:62)}}
> {{        at 
> scala.collection.immutable.HashMap.foreachEntry(HashMap.scala:1092)}}
> {{        at 
> kafka.controller.ZkReplicaStateMachine.handleStateChanges(ReplicaStateMachine.scala:111)}}
> {{        at 
> kafka.controller.TopicDeletionManager.failReplicaDeletion(TopicDeletionManager.scala:157)}}
> {{        at 
> kafka.controller.KafkaController.onReplicasBecomeOffline(KafkaController.scala:638)}}
> {{        at 
> kafka.controller.KafkaController.onBrokerFailure(KafkaController.scala:599)}}
> {{        at 
> kafka.controller.KafkaController.processBrokerChange(KafkaController.scala:1623)}}
> {{        at 
> kafka.controller.KafkaController.process(KafkaController.scala:2534)}}
> {{        at 
> kafka.controller.QueuedEvent.process(ControllerEventManager.scala:52)}}
> {{        at 
> kafka.controller.ControllerEventManager$ControllerEventThread.process$1(ControllerEventManager.scala:130)}}
> {{--}}
> {{[2022-05-16 11:53:40,726] ERROR [Controller id=1 epoch=1] Controller 1 
> epoch 1 initiated state change of replica 3 for partition test-topic-2 from 
> ReplicaDeletionSuccessful to OnlineReplica failed (state.change.logger)}}
> {{java.lang.IllegalStateException: Replica 
> [Topic=test-topic,Partition=2,Replica=3] should be in the 
> NewReplica,OnlineReplica,OfflineReplica,ReplicaDeletionIneligible states 
> before moving to OnlineReplica state. Instead it is in 
> ReplicaDeletionSuccessful state}}
> {{        at 
> kafka.controller.ZkReplicaStateMachine.logInvalidTransition(ReplicaStateMachine.scala:442)}}
> {{        at 
> kafka.controller.ZkReplicaStateMachine.$anonfun$doHandleStateChanges$2(ReplicaStateMachine.scala:164)}}
> {{        at 
> kafka.controller.ZkReplicaStateMachine.$anonfun$doHandleStateChanges$2$adapted(ReplicaStateMachine.scala:164)}}
> {{        at scala.collection.immutable.List.foreach(List.scala:333)}}
> {{        at 
> kafka.controller.ZkReplicaStateMachine.doHandleStateChanges(ReplicaStateMach

[jira] [Commented] (KAFKA-16310) ListOffsets doesn't report the offset with maxTimestamp anymore

[Johnny Hsu (Jira)]

[ 
https://issues.apache.org/jira/browse/KAFKA-16310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17832226#comment-17832226
 ] 

Johnny Hsu commented on KAFKA-16310:


thanks [~junrao] for pointing this out and sharing the solution, and thanks 
[~chia7712] [~showuon] for those discussions and revert it for 3.6. 

 
{quote}Since this is a rare operation, paying the decompression overhead is 
fine.

 

Adding a new field in the batch requires record format change, which is a much 
bigger effort. For now, the easiest thing is to add a method in Batch to find 
out offsetOfMaxTimestanp by iterating all records.

Regarding the optimization on the leader side by caching offsetOfMaxTimestanp, 
we could do it. However, my understanding is that listMaxTimestamp is rare and 
I am not sure if it's worth the additional complexity.
{quote}
have go through the comments and had a offline discussion with Chia-Ping, I got 
more context and also feel that we can transfer the workload to 
listMaxTimestamp when clients fetch this since it's rare. What do you think?  

> ListOffsets doesn't report the offset with maxTimestamp anymore
> ---
>
> Key: KAFKA-16310
> URL: https://issues.apache.org/jira/browse/KAFKA-16310
> Project: Kafka
>  Issue Type: Bug
>Affects Versions: 3.7.0
>Reporter: Emanuele Sabellico
>Assignee: Chia-Ping Tsai
>Priority: Blocker
> Fix For: 3.8.0
>
>
> Updated: This is confirmed a regression issue in v3.7.0. 
> The impact of this issue is that when there is a batch containing records 
> with timestamp not in order, the offset of the timestamp will be wrong.(ex: 
> the timestamp for t0 should be mapping to offset 10, but will get offset 12.. 
> etc). It'll cause the time index is putting the wrong offset, so the result 
> will be unexpected. 
> ===
> The last offset is reported instead.
> A test in librdkafka (0081/do_test_ListOffsets) is failing an it's checking 
> that the offset with the max timestamp is the middle one and not the last 
> one. The tests is passing with 3.6.0 and previous versions
> This is the test:
> [https://github.com/confluentinc/librdkafka/blob/a6d85bdbc1023b1a5477b8befe516242c3e182f6/tests/0081-admin.c#L4989]
>  
> there are three messages, with timestamps:
> {noformat}
> t0 + 100
> t0 + 400
> t0 + 250{noformat}
> and indices 0,1,2. 
> then a ListOffsets with RD_KAFKA_OFFSET_SPEC_MAX_TIMESTAMP is done.
> it should return offset 1 but in 3.7.0 and trunk is returning offset 2
> Even after 5 seconds from producing it's still returning 2 as the offset with 
> max timestamp.
> ProduceRequest and ListOffsets were sent to the same broker (2), the leader 
> didn't change.
> {code:java}
> %7|1709134230.019|SEND|0081_admin#producer-3| 
> [thrd:localhost:39951/bootstrap]: localhost:39951/2: Sent ProduceRequest (v7, 
> 206 bytes @ 0, CorrId 2) %7|1709134230.020|RECV|0081_admin#producer-3| 
> [thrd:localhost:39951/bootstrap]: localhost:39951/2: Received ProduceResponse 
> (v7, 95 bytes, CorrId 2, rtt 1.18ms) 
> %7|1709134230.020|MSGSET|0081_admin#producer-3| 
> [thrd:localhost:39951/bootstrap]: localhost:39951/2: 
> rdkafkatest_rnd22e8d8ec45b53f98_do_test_ListOffsets [0]: MessageSet with 3 
> message(s) (MsgId 0, BaseSeq -1) delivered {code}
> {code:java}
> %7|1709134235.021|SEND|0081_admin#producer-2| 
> [thrd:localhost:39951/bootstrap]: localhost:39951/2: Sent ListOffsetsRequest 
> (v7, 103 bytes @ 0, CorrId 7) %7|1709134235.022|RECV|0081_admin#producer-2| 
> [thrd:localhost:39951/bootstrap]: localhost:39951/2: Received 
> ListOffsetsResponse (v7, 88 bytes, CorrId 7, rtt 0.54ms){code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Commented] (KAFKA-16310) ListOffsets doesn't report the offset with maxTimestamp anymore

[Johnny Hsu (Jira)]

[ 
https://issues.apache.org/jira/browse/KAFKA-16310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17831464#comment-17831464
 ] 

Johnny Hsu commented on KAFKA-16310:


{quote}[~chia7712] thanks for the help!

This returns the offset and timestamp corresponding to the record with the 
highest timestamp on the partition. Noted that we should choose the offset of 
the earliest record if the timestamp of the records are the same.

This sounds good to me, thanks! 


{quote}

> ListOffsets doesn't report the offset with maxTimestamp anymore
> ---
>
> Key: KAFKA-16310
> URL: https://issues.apache.org/jira/browse/KAFKA-16310
> Project: Kafka
>  Issue Type: Bug
>Affects Versions: 3.7.0
>Reporter: Emanuele Sabellico
>Assignee: Chia-Ping Tsai
>Priority: Blocker
> Fix For: 3.6.2, 3.8.0, 3.7.1
>
>
> Updated: This is confirmed a regression issue in v3.7.0. 
> The impact of this issue is that when there is a batch containing records 
> with timestamp not in order, the offset of the timestamp will be wrong.(ex: 
> the timestamp for t0 should be mapping to offset 10, but will get offset 12.. 
> etc). It'll cause the time index is putting the wrong offset, so the result 
> will be unexpected. 
> ===
> The last offset is reported instead.
> A test in librdkafka (0081/do_test_ListOffsets) is failing an it's checking 
> that the offset with the max timestamp is the middle one and not the last 
> one. The tests is passing with 3.6.0 and previous versions
> This is the test:
> [https://github.com/confluentinc/librdkafka/blob/a6d85bdbc1023b1a5477b8befe516242c3e182f6/tests/0081-admin.c#L4989]
>  
> there are three messages, with timestamps:
> {noformat}
> t0 + 100
> t0 + 400
> t0 + 250{noformat}
> and indices 0,1,2. 
> then a ListOffsets with RD_KAFKA_OFFSET_SPEC_MAX_TIMESTAMP is done.
> it should return offset 1 but in 3.7.0 and trunk is returning offset 2
> Even after 5 seconds from producing it's still returning 2 as the offset with 
> max timestamp.
> ProduceRequest and ListOffsets were sent to the same broker (2), the leader 
> didn't change.
> {code:java}
> %7|1709134230.019|SEND|0081_admin#producer-3| 
> [thrd:localhost:39951/bootstrap]: localhost:39951/2: Sent ProduceRequest (v7, 
> 206 bytes @ 0, CorrId 2) %7|1709134230.020|RECV|0081_admin#producer-3| 
> [thrd:localhost:39951/bootstrap]: localhost:39951/2: Received ProduceResponse 
> (v7, 95 bytes, CorrId 2, rtt 1.18ms) 
> %7|1709134230.020|MSGSET|0081_admin#producer-3| 
> [thrd:localhost:39951/bootstrap]: localhost:39951/2: 
> rdkafkatest_rnd22e8d8ec45b53f98_do_test_ListOffsets [0]: MessageSet with 3 
> message(s) (MsgId 0, BaseSeq -1) delivered {code}
> {code:java}
> %7|1709134235.021|SEND|0081_admin#producer-2| 
> [thrd:localhost:39951/bootstrap]: localhost:39951/2: Sent ListOffsetsRequest 
> (v7, 103 bytes @ 0, CorrId 7) %7|1709134235.022|RECV|0081_admin#producer-2| 
> [thrd:localhost:39951/bootstrap]: localhost:39951/2: Received 
> ListOffsetsResponse (v7, 88 bytes, CorrId 7, rtt 0.54ms){code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Comment Edited] (KAFKA-16310) ListOffsets doesn't report the offset with maxTimestamp anymore

[Johnny Hsu (Jira)]

[ 
https://issues.apache.org/jira/browse/KAFKA-16310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17831464#comment-17831464
 ] 

Johnny Hsu edited comment on KAFKA-16310 at 3/27/24 5:01 PM:
-

{quote}[~chia7712] thanks for the help!

This returns the offset and timestamp corresponding to the record with the 
highest timestamp on the partition. Noted that we should choose the offset of 
the earliest record if the timestamp of the records are the same.

This sounds good to me, thanks! {quote}


was (Author: JIRAUSER304478):
{quote}[~chia7712] thanks for the help!

This returns the offset and timestamp corresponding to the record with the 
highest timestamp on the partition. Noted that we should choose the offset of 
the earliest record if the timestamp of the records are the same.

This sounds good to me, thanks! 


{quote}

> ListOffsets doesn't report the offset with maxTimestamp anymore
> ---
>
> Key: KAFKA-16310
> URL: https://issues.apache.org/jira/browse/KAFKA-16310
> Project: Kafka
>  Issue Type: Bug
>Affects Versions: 3.7.0
>Reporter: Emanuele Sabellico
>Assignee: Chia-Ping Tsai
>Priority: Blocker
> Fix For: 3.6.2, 3.8.0, 3.7.1
>
>
> Updated: This is confirmed a regression issue in v3.7.0. 
> The impact of this issue is that when there is a batch containing records 
> with timestamp not in order, the offset of the timestamp will be wrong.(ex: 
> the timestamp for t0 should be mapping to offset 10, but will get offset 12.. 
> etc). It'll cause the time index is putting the wrong offset, so the result 
> will be unexpected. 
> ===
> The last offset is reported instead.
> A test in librdkafka (0081/do_test_ListOffsets) is failing an it's checking 
> that the offset with the max timestamp is the middle one and not the last 
> one. The tests is passing with 3.6.0 and previous versions
> This is the test:
> [https://github.com/confluentinc/librdkafka/blob/a6d85bdbc1023b1a5477b8befe516242c3e182f6/tests/0081-admin.c#L4989]
>  
> there are three messages, with timestamps:
> {noformat}
> t0 + 100
> t0 + 400
> t0 + 250{noformat}
> and indices 0,1,2. 
> then a ListOffsets with RD_KAFKA_OFFSET_SPEC_MAX_TIMESTAMP is done.
> it should return offset 1 but in 3.7.0 and trunk is returning offset 2
> Even after 5 seconds from producing it's still returning 2 as the offset with 
> max timestamp.
> ProduceRequest and ListOffsets were sent to the same broker (2), the leader 
> didn't change.
> {code:java}
> %7|1709134230.019|SEND|0081_admin#producer-3| 
> [thrd:localhost:39951/bootstrap]: localhost:39951/2: Sent ProduceRequest (v7, 
> 206 bytes @ 0, CorrId 2) %7|1709134230.020|RECV|0081_admin#producer-3| 
> [thrd:localhost:39951/bootstrap]: localhost:39951/2: Received ProduceResponse 
> (v7, 95 bytes, CorrId 2, rtt 1.18ms) 
> %7|1709134230.020|MSGSET|0081_admin#producer-3| 
> [thrd:localhost:39951/bootstrap]: localhost:39951/2: 
> rdkafkatest_rnd22e8d8ec45b53f98_do_test_ListOffsets [0]: MessageSet with 3 
> message(s) (MsgId 0, BaseSeq -1) delivered {code}
> {code:java}
> %7|1709134235.021|SEND|0081_admin#producer-2| 
> [thrd:localhost:39951/bootstrap]: localhost:39951/2: Sent ListOffsetsRequest 
> (v7, 103 bytes @ 0, CorrId 7) %7|1709134235.022|RECV|0081_admin#producer-2| 
> [thrd:localhost:39951/bootstrap]: localhost:39951/2: Received 
> ListOffsetsResponse (v7, 88 bytes, CorrId 7, rtt 0.54ms){code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Commented] (KAFKA-16310) ListOffsets doesn't report the offset with maxTimestamp anymore

[Johnny Hsu (Jira)]

[ 
https://issues.apache.org/jira/browse/KAFKA-16310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17831460#comment-17831460
 ] 

Johnny Hsu commented on KAFKA-16310:


The update is in below section:

 

## When the TimestampType is LOG_APPEND_TIME

When the TimestampType is LOG_APPEND_TIME, the timestamp of the records are the 
same. In this case, we should choose the offset of the first record. [This 
path|https://github.com/apache/kafka/blob/6f38fe5e0a6e2fe85fec7cb9adc379061d35ce45/storage/src/main/java/org/apache/kafka/storage/internals/log/LogValidator.java#L294]
 in LogValidator was added to handle this case for non-compressed type, while 
[this 
path|https://github.com/apache/kafka/blob/6f38fe5e0a6e2fe85fec7cb9adc379061d35ce45/storage/src/main/java/org/apache/kafka/storage/internals/log/LogValidator.java#L421]
 in LogValidator was added to handle this case for compressed type.  

I don't have the Confluence account yet, [~chia7712] would you please help 
update the KIP in the wiki? I will send this update to the dev thread for 
visibility. Thanks! 

> ListOffsets doesn't report the offset with maxTimestamp anymore
> ---
>
> Key: KAFKA-16310
> URL: https://issues.apache.org/jira/browse/KAFKA-16310
> Project: Kafka
>  Issue Type: Bug
>Affects Versions: 3.7.0
>Reporter: Emanuele Sabellico
>Assignee: Chia-Ping Tsai
>Priority: Blocker
> Fix For: 3.6.2, 3.8.0, 3.7.1
>
>
> Updated: This is confirmed a regression issue in v3.7.0. 
> The impact of this issue is that when there is a batch containing records 
> with timestamp not in order, the offset of the timestamp will be wrong.(ex: 
> the timestamp for t0 should be mapping to offset 10, but will get offset 12.. 
> etc). It'll cause the time index is putting the wrong offset, so the result 
> will be unexpected. 
> ===
> The last offset is reported instead.
> A test in librdkafka (0081/do_test_ListOffsets) is failing an it's checking 
> that the offset with the max timestamp is the middle one and not the last 
> one. The tests is passing with 3.6.0 and previous versions
> This is the test:
> [https://github.com/confluentinc/librdkafka/blob/a6d85bdbc1023b1a5477b8befe516242c3e182f6/tests/0081-admin.c#L4989]
>  
> there are three messages, with timestamps:
> {noformat}
> t0 + 100
> t0 + 400
> t0 + 250{noformat}
> and indices 0,1,2. 
> then a ListOffsets with RD_KAFKA_OFFSET_SPEC_MAX_TIMESTAMP is done.
> it should return offset 1 but in 3.7.0 and trunk is returning offset 2
> Even after 5 seconds from producing it's still returning 2 as the offset with 
> max timestamp.
> ProduceRequest and ListOffsets were sent to the same broker (2), the leader 
> didn't change.
> {code:java}
> %7|1709134230.019|SEND|0081_admin#producer-3| 
> [thrd:localhost:39951/bootstrap]: localhost:39951/2: Sent ProduceRequest (v7, 
> 206 bytes @ 0, CorrId 2) %7|1709134230.020|RECV|0081_admin#producer-3| 
> [thrd:localhost:39951/bootstrap]: localhost:39951/2: Received ProduceResponse 
> (v7, 95 bytes, CorrId 2, rtt 1.18ms) 
> %7|1709134230.020|MSGSET|0081_admin#producer-3| 
> [thrd:localhost:39951/bootstrap]: localhost:39951/2: 
> rdkafkatest_rnd22e8d8ec45b53f98_do_test_ListOffsets [0]: MessageSet with 3 
> message(s) (MsgId 0, BaseSeq -1) delivered {code}
> {code:java}
> %7|1709134235.021|SEND|0081_admin#producer-2| 
> [thrd:localhost:39951/bootstrap]: localhost:39951/2: Sent ListOffsetsRequest 
> (v7, 103 bytes @ 0, CorrId 7) %7|1709134235.022|RECV|0081_admin#producer-2| 
> [thrd:localhost:39951/bootstrap]: localhost:39951/2: Received 
> ListOffsetsResponse (v7, 88 bytes, CorrId 7, rtt 0.54ms){code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Re: [RBW] Craigslist, etc 2024

[Johnny Alien]

Thats a solid deal but sadly for me looks like its a 51 which would be way 
too small.

On Saturday, March 23, 2024 at 4:44:07 PM UTC-4 jerry...@gmail.com wrote:

> *Not mine and no affiliation, just a shame for me it's not a 56 or 58cm.
> Rivendell Atlantis 2, serial #2 - $1,000 (Santa Cruz)
>
> https://sfbay.craigslist.org/scz/bik/d/santa-cruz-rivendell-atlantis-serial/7730132678.html
> [image: 00Q0Q_bDQSLzWSDsP_0CI0pN_1200x900.jpg]
>
> On Friday 22 March 2024 at 09:35:54 UTC-7 maxcr wrote:
>
>> PSA: beautiful green 58cm Rambouillet in the FB riv buy/sell group.
>>
>> No connections to the seller and they don't seem to know their asking 
>> price yet, but if you've been looking for one, this one looks great!
>>
>> [image: ram.jpg]
>>
>> On Friday, March 22, 2024 at 9:56:55 AM UTC-4 Elisabeth Sherwood wrote:
>>
>>> Btw, the Reston (VA) Homer is now down to $2,500.
>>>
>>>
>>> https://washingtondc.craigslist.org/nva/bik/d/reston-rivendell-homer-hilsen/7726857824.html
>>>
>>>
>>>
>>>
>>>
>>> On Thursday, March 21, 2024 at 7:40:06 PM UTC-4 eric...@gmail.com wrote:
>>>
 That Reston Homer is nicely appointed and a good deal for someone right 
 for a 47cm!

 On Thursday, March 21, 2024 at 9:43:22 AM UTC-4 Bill Lindsay wrote:

> Your patience continues to earn you money.  Now the price is down to 
> $6000.  Wait until September and you'll get paid to take it.  
>
> Bill Lindsay
> El Cerrito, CA
>
> On Friday, March 15, 2024 at 8:46:10 AM UTC-7 Joe Bernard wrote:
>
>> I love a bargain 
>>
>> On Friday, March 15, 2024 at 7:40:48 AM UTC-7 Bill Lindsay wrote:
>>
>>> It's on special offer now to those of us who are watching it.  Now 
>>> avaiable for the low low price of $6250.  
>>>
>>> Bill Lindsay
>>> El Cerrito, CA
>>>
>>> On Wednesday, March 13, 2024 at 9:59:37 AM UTC-7 LBleriot wrote:
>>>
 Yikes!  I would love to add a Heron Touring to go with my Road, but 
 this Ebay listing is kind of a silly way to solicit real offers.

 On Wednesday, March 13, 2024 at 12:26:30 PM UTC-4 Patrick Moore 
 wrote:

> Obviously the Chris King Headset Composite Index has gone through 
> the roof.
>
> On Tue, Mar 12, 2024 at 6:37 PM Josh C  
> wrote:
>
>> wow
>>
>> On Monday, March 11, 2024 at 3:33:10 PM UTC-4 Bill Lindsay wrote:
>>
>>> $7000  In a word, HA!  At least they are taking offers...  
>>>
>>> BL in EC
>>>
>>> On Monday, March 11, 2024 at 12:28:26 PM UTC-7 Michael Morrissey 
>>> wrote:
>>>
 Heron Touring 
 55cm
 $7000
 Walled Lake, Michigan
 Rare rare rare parts like Titanium Chris King headset, Nitto 
 racks, and full Campagnolo...

 https://www.ebay.com/itm/176156925449?itmmeta=01HRQFP37XW2ZW9W57MX91XV8H=item2903c55e09:g:1-QAAOSwlT9le1Vr=enc%3AAQAI4A7jbJYmJLb0qhGidg8sdvoie5vcUpIvYrS%2BSMvrLJLvPiSDvKpjMsaHlJTCd1soc%2BS7lyI3DhBCJIMPjYbsw%2Bz2jx3FF1A8HaYOsrSGCGDojnJMNqrJC9m0GJvRkaVV7ejS4wIjNmkGPkl5PLpOEQlbXY8ub8%2FhPJelndP333HN%2B5YXfIBsGZBcK%2BedK1MLmQWY7kHqX4c4AzxDVzG%2B1rJVrllsTotNUBw2pKEhm%2BQDzzEV4sTfCquOQ0jScQhSElZQaXk3KjAGccNhRMGhT54kCgPjyFiebEPpJtvqbTfN%7Ctkp%3ABk9SR4C02O_FYw

 On Sunday, March 3, 2024 at 5:36:38 PM UTC-5 Matthew Williams 
 wrote:

> Roadini
> 57cm
> 2000
> Emeryville, CA
>
>
> https://sfbay.craigslist.org/eby/bik/d/emeryville-rivendell-leo-roadini/7720529232.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-bun...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/rbw-owners-bunch/74990461-7391-474d-8678-55c5cf2c2ef6n%40googlegroups.com
>>  
>> 
>> .
>>
>
>
> -- 
>
> Patrick Moore
> Alburquerque, Nuevo Mexico, Etats Unis d'Amerique, Orbis Terrarum
>
> ---
>
> Executive resumes, LinkedIn profiles, bios, letters, and other 
> writing services
>
>
> ---
>
> *When thou didst not, savage, k**now thine own meaning,*

[jira] [Updated] (KAFKA-16419) Abstract validateMessagesAndAssignOffsetsCompressed of LogValidator to simply the process

[Johnny Hsu (Jira)]

 [ 
https://issues.apache.org/jira/browse/KAFKA-16419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Johnny Hsu updated KAFKA-16419:
---
Description: 
Currently in the 
[LogValidator.validateMessagesAndAssignOffsetsCompressed|https://github.com/apache/kafka/blob/51c9b0d0ad408754b1c5883a9c7fcc63a5f57eb8/storage/src/main/java/org/apache/kafka/storage/internals/log/LogValidator.java#L315],
 there are lots of if-else checks based on the `magic` and `CompressionType`, 
which makes the code complicated and increase the difficulties of maintaining. 

The flow of the validation can be separated into 5 steps:
 # IBP validation
 ## whether the compression type is valid for this IBP
 # In-place assignment enablement check
 ## based on the magic value and compression type, decide whether we can do 
in-place assignment
 # batch level validation
 ## based on the batch origin (client, controller, etc) and magic version
 # record level validation
 ## based on whether we can do in-place assignment, choose different iterator 
 ## based on the magic and compression type, do different validation
 # return validated results
 ## based on whether we can do in-place assignment, build the records or assign 
it

This whole flow can be extracted into an interface, and the 
LogValidator.validateMessagesAndAssignOffsetsCompressed can init an 
implementation based on the passed-in records.

The implementation class will have the following fields:
 # magic value
 # source compression type
 # target compression type
 # origin
 # records
 # timestamp type

  was:
Currently in the 
[LogValidator.validateMessagesAndAssignOffsetsCompressed|http://example.com](https://github.com/apache/kafka/blob/51c9b0d0ad408754b1c5883a9c7fcc63a5f57eb8/storage/src/main/java/org/apache/kafka/storage/internals/log/LogValidator.java#L315),
 there are lots of if-else checks based on the `magic` and `CompressionType`, 
which makes the code complicated and increase the difficulties of maintaining. 

The flow of the validation can be separated into 5 steps:
 # IBP validation
 ## whether the compression type is valid for this IBP
 # In-place assignment enablement check
 ## based on the magic value and compression type, decide whether we can do 
in-place assignment
 # batch level validation
 ## based on the batch origin (client, controller, etc) and magic version
 # record level validation
 ## based on whether we can do in-place assignment, choose different iterator 
 ## based on the magic and compression type, do different validation
 # return validated results
 ## based on whether we can do in-place assignment, build the records or assign 
it

This whole flow can be extracted into an interface, and the 
LogValidator.validateMessagesAndAssignOffsetsCompressed can init an 
implementation based on the passed-in records.

The implementation class will have the following fields:
 # magic value
 # source compression type
 # target compression type
 # origin
 # records
 # timestamp type


> Abstract validateMessagesAndAssignOffsetsCompressed of LogValidator to simply 
> the process
> -
>
> Key: KAFKA-16419
> URL: https://issues.apache.org/jira/browse/KAFKA-16419
> Project: Kafka
>  Issue Type: Improvement
>    Reporter: Johnny Hsu
>Assignee: Johnny Hsu
>Priority: Major
>
> Currently in the 
> [LogValidator.validateMessagesAndAssignOffsetsCompressed|https://github.com/apache/kafka/blob/51c9b0d0ad408754b1c5883a9c7fcc63a5f57eb8/storage/src/main/java/org/apache/kafka/storage/internals/log/LogValidator.java#L315],
>  there are lots of if-else checks based on the `magic` and `CompressionType`, 
> which makes the code complicated and increase the difficulties of 
> maintaining. 
> The flow of the validation can be separated into 5 steps:
>  # IBP validation
>  ## whether the compression type is valid for this IBP
>  # In-place assignment enablement check
>  ## based on the magic value and compression type, decide whether we can do 
> in-place assignment
>  # batch level validation
>  ## based on the batch origin (client, controller, etc) and magic version
>  # record level validation
>  ## based on whether we can do in-place assignment, choose different iterator 
>  ## based on the magic and compression type, do different validation
>  # return validated results
>  ## based on whether we can do in-place assignment, build the records or 
> assign it
> This whole flow can be extracted into an interface, and the 
> LogValidator.validateMessagesAndAssignOffsetsCompressed can init an 
> implementation based on the passed-in records.
> The implementation class will have the following fields:
>  # magic value
>  # source compression type
>  # 

[jira] [Updated] (KAFKA-16419) Abstract validateMessagesAndAssignOffsetsCompressed of LogValidator to simply the process

[Johnny Hsu (Jira)]

 [ 
https://issues.apache.org/jira/browse/KAFKA-16419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Johnny Hsu updated KAFKA-16419:
---
Description: 
Currently in the 
[LogValidator.validateMessagesAndAssignOffsetsCompressed|http://example.com](https://github.com/apache/kafka/blob/51c9b0d0ad408754b1c5883a9c7fcc63a5f57eb8/storage/src/main/java/org/apache/kafka/storage/internals/log/LogValidator.java#L315),
 there are lots of if-else checks based on the `magic` and `CompressionType`, 
which makes the code complicated and increase the difficulties of maintaining. 

The flow of the validation can be separated into 5 steps:
 # IBP validation
 ## whether the compression type is valid for this IBP
 # In-place assignment enablement check
 ## based on the magic value and compression type, decide whether we can do 
in-place assignment
 # batch level validation
 ## based on the batch origin (client, controller, etc) and magic version
 # record level validation
 ## based on whether we can do in-place assignment, choose different iterator 
 ## based on the magic and compression type, do different validation
 # return validated results
 ## based on whether we can do in-place assignment, build the records or assign 
it

This whole flow can be extracted into an interface, and the 
LogValidator.validateMessagesAndAssignOffsetsCompressed can init an 
implementation based on the passed-in records.

The implementation class will have the following fields:
 # magic value
 # source compression type
 # target compression type
 # origin
 # records
 # timestamp type

  was:
Currently in the LogValidator.validateMessagesAndAssignOffsetsCompressed, there 
are lots of if-else checks based on the `magic` and `CompressionType`, which 
makes the code complicated and increase the difficulties of maintaining. 

The flow of the validation can be separated into 5 steps:
 # IBP validation
 ## whether the compression type is valid for this IBP
 # In-place assignment enablement check
 ## based on the magic value and compression type, decide whether we can do 
in-place assignment
 # batch level validation
 ## based on the batch origin (client, controller, etc) and magic version
 # record level validation
 ## based on whether we can do in-place assignment, choose different iterator 
 ## based on the magic and compression type, do different validation
 # return validated results
 ## based on whether we can do in-place assignment, build the records or assign 
it

This whole flow can be extracted into an interface, and the 
LogValidator.validateMessagesAndAssignOffsetsCompressed can init an 
implementation based on the passed-in records.

The implementation class will have the following fields:
 # magic value
 # source compression type
 # target compression type
 # origin
 # records
 # timestamp type


> Abstract validateMessagesAndAssignOffsetsCompressed of LogValidator to simply 
> the process
> -
>
> Key: KAFKA-16419
> URL: https://issues.apache.org/jira/browse/KAFKA-16419
> Project: Kafka
>  Issue Type: Improvement
>    Reporter: Johnny Hsu
>Assignee: Johnny Hsu
>Priority: Major
>
> Currently in the 
> [LogValidator.validateMessagesAndAssignOffsetsCompressed|http://example.com](https://github.com/apache/kafka/blob/51c9b0d0ad408754b1c5883a9c7fcc63a5f57eb8/storage/src/main/java/org/apache/kafka/storage/internals/log/LogValidator.java#L315),
>  there are lots of if-else checks based on the `magic` and `CompressionType`, 
> which makes the code complicated and increase the difficulties of 
> maintaining. 
> The flow of the validation can be separated into 5 steps:
>  # IBP validation
>  ## whether the compression type is valid for this IBP
>  # In-place assignment enablement check
>  ## based on the magic value and compression type, decide whether we can do 
> in-place assignment
>  # batch level validation
>  ## based on the batch origin (client, controller, etc) and magic version
>  # record level validation
>  ## based on whether we can do in-place assignment, choose different iterator 
>  ## based on the magic and compression type, do different validation
>  # return validated results
>  ## based on whether we can do in-place assignment, build the records or 
> assign it
> This whole flow can be extracted into an interface, and the 
> LogValidator.validateMessagesAndAssignOffsetsCompressed can init an 
> implementation based on the passed-in records.
> The implementation class will have the following fields:
>  # magic value
>  # source compression type
>  # target compression type
>  # origin
>  # records
>  # timestamp type



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (KAFKA-16419) Abstract validateMessagesAndAssignOffsetsCompressed of LogValidator to simply the process

[Johnny Hsu (Jira)]

 [ 
https://issues.apache.org/jira/browse/KAFKA-16419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Johnny Hsu updated KAFKA-16419:
---
Description: 
Currently in the LogValidator.validateMessagesAndAssignOffsetsCompressed, there 
are lots of if-else checks based on the `magic` and `CompressionType`, which 
makes the code complicated and increase the difficulties of maintaining. 

The flow of the validation can be separated into 5 steps:
 # IBP validation
 ## whether the compression type is valid for this IBP
 # In-place assignment enablement check
 ## based on the magic value and compression type, decide whether we can do 
in-place assignment
 # batch level validation
 ## based on the batch origin (client, controller, etc) and magic version
 # record level validation
 ## based on whether we can do in-place assignment, choose different iterator 
 ## based on the magic and compression type, do different validation
 # return validated results
 ## based on whether we can do in-place assignment, build the records or assign 
it

This whole flow can be extracted into an interface, and the 
LogValidator.validateMessagesAndAssignOffsetsCompressed can init an 
implementation based on the passed-in records.

The implementation class will have the following fields:
 # magic value
 # source compression type
 # target compression type
 # origin
 # records
 # timestamp type

  was:
Currently in the LogValidator.validateMessagesAndAssignOffsetsCompressed, there 
are lots of if-else checks based on the `magic` and `CompressionType`, which 
makes the code complicated and increase the difficulties of maintaining. 

The flow of the validation can be separated into x steps:
 # IBP validation
 ## whether the compression type is valid for this IBP
 # In-place assignment enablement check
 ## based on the magic value and compression type, decide whether we can do 
in-place assignment
 # batch level validation
 ## based on the batch origin (client, controller, etc) and magic version
 # record level validation
 ## based on whether we can do in-place assignment, choose different iterator 
 ## based on the magic and compression type, do different validation
 # return validated results
 ## based on whether we can do in-place assignment, build the records or assign 
it

This whole flow can be extracted into an interface, and the 
LogValidator.validateMessagesAndAssignOffsetsCompressed can init an 
implementation based on the passed-in records.

The implementation class will have the following fields:
 # magic value
 # source compression type
 # target compression type
 # origin
 # records
 # timestamp type


> Abstract validateMessagesAndAssignOffsetsCompressed of LogValidator to simply 
> the process
> -
>
> Key: KAFKA-16419
> URL: https://issues.apache.org/jira/browse/KAFKA-16419
> Project: Kafka
>  Issue Type: Improvement
>    Reporter: Johnny Hsu
>Assignee: Johnny Hsu
>Priority: Major
>
> Currently in the LogValidator.validateMessagesAndAssignOffsetsCompressed, 
> there are lots of if-else checks based on the `magic` and `CompressionType`, 
> which makes the code complicated and increase the difficulties of 
> maintaining. 
> The flow of the validation can be separated into 5 steps:
>  # IBP validation
>  ## whether the compression type is valid for this IBP
>  # In-place assignment enablement check
>  ## based on the magic value and compression type, decide whether we can do 
> in-place assignment
>  # batch level validation
>  ## based on the batch origin (client, controller, etc) and magic version
>  # record level validation
>  ## based on whether we can do in-place assignment, choose different iterator 
>  ## based on the magic and compression type, do different validation
>  # return validated results
>  ## based on whether we can do in-place assignment, build the records or 
> assign it
> This whole flow can be extracted into an interface, and the 
> LogValidator.validateMessagesAndAssignOffsetsCompressed can init an 
> implementation based on the passed-in records.
> The implementation class will have the following fields:
>  # magic value
>  # source compression type
>  # target compression type
>  # origin
>  # records
>  # timestamp type



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[CentOS-announce] CESA-2024:1249 Important CentOS 7 kernel Security Update

[Johnny Hughes]

CentOS Errata and Security Advisory 2024:1249 Important

Upstream details at : https://access.redhat.com/errata/RHSA-2024:1249

The following updated files have been uploaded and are currently 
syncing to the mirrors: ( sha256sum Filename ) 

x86_64:
ebf604edce00a3a3778207eeaac06a3de226dbf62bfb987ed00584aa8d736ea1  
bpftool-3.10.0-1160.114.2.el7.x86_64.rpm
4ea83e958a87df368396a4445d79a7047566af99a681051e97005b0c5b61aa05  
kernel-3.10.0-1160.114.2.el7.src.rpm
d4e1ed8394af297a574fede15b7e0b3dcc28d263998175257f45e728f22fca91  
kernel-3.10.0-1160.114.2.el7.x86_64.rpm
18d2703d9432cd3d8353acf0fb1f852fe4c15301b3d49fffac3f0194c6a4aaa0  
kernel-abi-whitelists-3.10.0-1160.114.2.el7.noarch.rpm
fe01de01f7bcb863a54f276394f9ab097a0d29db56661a42eb33d27e4bef27f8  
kernel-debug-3.10.0-1160.114.2.el7.x86_64.rpm
cfde4230671763bf6a464de9ec8c191195c9ae864571afd92bc7bea8dfcbb11e  
kernel-debug-devel-3.10.0-1160.114.2.el7.x86_64.rpm
74dfc146e5e4ab219dba838033e3a2a983e2ad796cee5a175fda1b6c17653193  
kernel-devel-3.10.0-1160.114.2.el7.x86_64.rpm
b5a460913216927a863650ccef6d332b05a92836c9647e73a369720e9156fe84  
kernel-doc-3.10.0-1160.114.2.el7.noarch.rpm
4aeb221b696dbe4b67c7b108b689cf26df6c7baa673fd4a529bd4df444eaf4fc  
kernel-headers-3.10.0-1160.114.2.el7.x86_64.rpm
2ba740802cbbc7ff23957b8b2a38c06b773a113b40708d05815b6081f7eecb19  
kernel-tools-3.10.0-1160.114.2.el7.x86_64.rpm
d4ce276deccf36c3cdff38a52ff6f73bd2c271d8df45463c61cc66cdd8dd7e18  
kernel-tools-libs-3.10.0-1160.114.2.el7.x86_64.rpm
bee03f8565ac02484c05292876b9c0976e9334dad12bbf643dd9f59526e9eb6d  
kernel-tools-libs-devel-3.10.0-1160.114.2.el7.x86_64.rpm
0af8a6a9e3b24968bed3be9b8de12ef658fbbfc2164edfd7186a7cced585e5ec  
perf-3.10.0-1160.114.2.el7.x86_64.rpm
850766245b53884b841d001909aa89898b167cf79a244d26c44c42dd775019c3  
python-perf-3.10.0-1160.114.2.el7.x86_64.rpm




-- 
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@libera.chat
Twitter: @JohnnyCentOS

___
CentOS-announce mailing list
CentOS-announce@centos.org
https://lists.centos.org/mailman/listinfo/centos-announce

[jira] [Created] (KAFKA-16419) Abstract validateMessagesAndAssignOffsetsCompressed of LogValidator to simply the process

[Johnny Hsu (Jira)]

Johnny Hsu created KAFKA-16419:
--

 Summary: Abstract validateMessagesAndAssignOffsetsCompressed of 
LogValidator to simply the process
 Key: KAFKA-16419
 URL: https://issues.apache.org/jira/browse/KAFKA-16419
 Project: Kafka
  Issue Type: Improvement
Reporter: Johnny Hsu
Assignee: Johnny Hsu


Currently in the LogValidator.validateMessagesAndAssignOffsetsCompressed, there 
are lots of if-else checks based on the `magic` and `CompressionType`, which 
makes the code complicated and increase the difficulties of maintaining. 

The flow of the validation can be separated into x steps:
 # IBP validation
 ## whether the compression type is valid for this IBP
 # In-place assignment enablement check
 ## based on the magic value and compression type, decide whether we can do 
in-place assignment
 # batch level validation
 ## based on the batch origin (client, controller, etc) and magic version
 # record level validation
 ## based on whether we can do in-place assignment, choose different iterator 
 ## based on the magic and compression type, do different validation
 # return validated results
 ## based on whether we can do in-place assignment, build the records or assign 
it

This whole flow can be extracted into an interface, and the 
LogValidator.validateMessagesAndAssignOffsetsCompressed can init an 
implementation based on the passed-in records.

The implementation class will have the following fields:
 # magic value
 # source compression type
 # target compression type
 # origin
 # records
 # timestamp type



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (KAFKA-16419) Abstract validateMessagesAndAssignOffsetsCompressed of LogValidator to simply the process

[Johnny Hsu (Jira)]

Johnny Hsu created KAFKA-16419:
--

 Summary: Abstract validateMessagesAndAssignOffsetsCompressed of 
LogValidator to simply the process
 Key: KAFKA-16419
 URL: https://issues.apache.org/jira/browse/KAFKA-16419
 Project: Kafka
  Issue Type: Improvement
Reporter: Johnny Hsu
Assignee: Johnny Hsu


Currently in the LogValidator.validateMessagesAndAssignOffsetsCompressed, there 
are lots of if-else checks based on the `magic` and `CompressionType`, which 
makes the code complicated and increase the difficulties of maintaining. 

The flow of the validation can be separated into x steps:
 # IBP validation
 ## whether the compression type is valid for this IBP
 # In-place assignment enablement check
 ## based on the magic value and compression type, decide whether we can do 
in-place assignment
 # batch level validation
 ## based on the batch origin (client, controller, etc) and magic version
 # record level validation
 ## based on whether we can do in-place assignment, choose different iterator 
 ## based on the magic and compression type, do different validation
 # return validated results
 ## based on whether we can do in-place assignment, build the records or assign 
it

This whole flow can be extracted into an interface, and the 
LogValidator.validateMessagesAndAssignOffsetsCompressed can init an 
implementation based on the passed-in records.

The implementation class will have the following fields:
 # magic value
 # source compression type
 # target compression type
 # origin
 # records
 # timestamp type



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[CentOS-announce] CEBA-2024:1276 CentOS 7 resource-agents BugFix Update

[Johnny Hughes]

CentOS Errata and Bugfix Advisory 2024:1276 

Upstream details at : https://access.redhat.com/errata/RHBA-2024:1276

The following updated files have been uploaded and are currently 
syncing to the mirrors: ( sha256sum Filename ) 

x86_64:
619d5b89b88c559b235692c6c00c5d06cedd0d274f0132dc0732b25bc91bb93e  
resource-agents-4.1.1-61.el7_9.20.src.rpm
1f633f20c7b2aa6eafb4ac8894d9cd73727c40432189eee52f62aee11daf62e9  
resource-agents-4.1.1-61.el7_9.20.x86_64.rpm
6d0aee209b29a68899270b50fbdb5657444b46017f3f4b39ff4652e77f30292c  
resource-agents-aliyun-4.1.1-61.el7_9.20.x86_64.rpm
639a97b21ae7b51141fd76f2777d2f3ea1bd758549e53130764657fafe2daf7a  
resource-agents-gcp-4.1.1-61.el7_9.20.x86_64.rpm




-- 
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@libera.chat
Twitter: @JohnnyCentOS

___
CentOS-announce mailing list
CentOS-announce@centos.org
https://lists.centos.org/mailman/listinfo/centos-announce

[CentOS-announce] CEBA-2024:1275 CentOS 7 lm_sensors BugFix Update

[Johnny Hughes]

CentOS Errata and Bugfix Advisory 2024:1275 

Upstream details at : https://access.redhat.com/errata/RHBA-2024:1275

The following updated files have been uploaded and are currently 
syncing to the mirrors: ( sha256sum Filename ) 

x86_64:
88e82b5a11526a65b2ac8dcbe253868992a00064db1db424255bd509feb452cb  
lm_sensors-3.4.0-8.20160601gitf9185e5.el7_9.1.src.rpm
be4cfd2a6f6ccca83e063fb2eccc0c3e16716ba370638be5de4deda72c80848a  
lm_sensors-3.4.0-8.20160601gitf9185e5.el7_9.1.x86_64.rpm
95d76c0c65f9a62fc846a490f4d2b19a993d7bfe3b29c8f5435e619d31f10fe5  
lm_sensors-devel-3.4.0-8.20160601gitf9185e5.el7_9.1.i686.rpm
552d8f1a349abd352ed882be0cfbe9423589f98f6621627e58afa84d6c83599d  
lm_sensors-devel-3.4.0-8.20160601gitf9185e5.el7_9.1.x86_64.rpm
189cab5bc603286773946e73c42d38c539c7a0de2d36fdb6fa6aba0763c86a44  
lm_sensors-libs-3.4.0-8.20160601gitf9185e5.el7_9.1.i686.rpm
0af4fa113704a011a3594459a6619542c384a68bce85aa250f90448e347431fe  
lm_sensors-libs-3.4.0-8.20160601gitf9185e5.el7_9.1.x86_64.rpm
60f10f4641f2dac4d689ad5b1ee25cc224768eadce58b7f0d64c3eecf32b94ff  
lm_sensors-sensord-3.4.0-8.20160601gitf9185e5.el7_9.1.x86_64.rpm




-- 
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@libera.chat
Twitter: @JohnnyCentOS

___
CentOS-announce mailing list
CentOS-announce@centos.org
https://lists.centos.org/mailman/listinfo/centos-announce

[CentOS-announce] CEBA-2024:1277 CentOS 7 libX11 BugFix Update

[Johnny Hughes]

CentOS Errata and Bugfix Advisory 2024:1277 

Upstream details at : https://access.redhat.com/errata/RHBA-2024:1277

The following updated files have been uploaded and are currently 
syncing to the mirrors: ( sha256sum Filename ) 

x86_64:
3e22c1e91e6c946f60aaa437911042d67c7e9de92d77cf458a51d5660658186c  
libX11-1.6.7-5.el7_9.i686.rpm
f79bf580272858f3f9343a97221fc561755bb908456a1beb77582f9310486ae1  
libX11-1.6.7-5.el7_9.src.rpm
1f4f286b0441b2c508c416f72ee52c1b323a1ba12aae4579f986c007ecde653f  
libX11-1.6.7-5.el7_9.x86_64.rpm
70bbd71ba6462d9f6702322739a79ddf57ab8a23f41a3ae1e2c47feacb60d0d1  
libX11-common-1.6.7-5.el7_9.noarch.rpm
1ef57080cad8889aa2a957bb771d161af38b61bf4aec83a7fcd19e2dfe510079  
libX11-devel-1.6.7-5.el7_9.i686.rpm
374f721b5f41a11a081cd23537162130ab654a02ece3e8c55f3840ecd8f839a0  
libX11-devel-1.6.7-5.el7_9.x86_64.rpm




-- 
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@libera.chat
Twitter: @JohnnyCentOS

___
CentOS-announce mailing list
CentOS-announce@centos.org
https://lists.centos.org/mailman/listinfo/centos-announce

[jira] [Commented] (KAFKA-16318) Add javadoc to KafkaMetric

[Johnny Hsu (Jira)]

[ 
https://issues.apache.org/jira/browse/KAFKA-16318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17830539#comment-17830539
 ] 

Johnny Hsu commented on KAFKA-16318:


the PR is merged, close this ticket

> Add javadoc to KafkaMetric
> --
>
> Key: KAFKA-16318
> URL: https://issues.apache.org/jira/browse/KAFKA-16318
> Project: Kafka
>  Issue Type: Bug
>  Components: docs
>Reporter: Mickael Maison
>Assignee: Johnny Hsu
>Priority: Major
> Fix For: 3.8.0
>
>
> KafkaMetric is part of the public API but it's missing javadoc describing the 
> class and several of its methods.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[RBW] Re: I have questions

[Johnny Alien]

I actually forgot all about that. I had read a large and very nerdy article 
on this recently. The reason why this hasn't taken off is because its not 
really practical or efficient to charge a phone with the dynamo. Most 
phones have software that throttle low level charges like what you would 
get from a dynamo. I have been becoming a big fan of battery lights as 
well. They have so many lighting options and stay charged for a really long 
time. And battery packs are really easy to keep with you if you go longer. 
Easier than all of the wires and drag that a dynamo brings. BUT there is 
something to be said to always 100% having a light read to go if you need 
it.

On Friday, March 22, 2024 at 7:55:19 PM UTC-4 Max S wrote:

> Let me be a bit of a contrarian on the lighting situation. Is a dyno hub + 
> phone charger worth the hassle?.. I am not sure. 
>
> A dyno hub puts out a nominal 3 Watts. If you ride it for an hour, that's 
> 3 watt-hours worth of electricity. Let's say it gets split between the 
> light and your phone. If you ride continuously for 10 hours, that's about 
> 30 watt-hours. Let's say half is used to power the light, half to power the 
> phone... 
>
> An iPhone 15 Pro has a 3,274 mA-hour / 12.70 watt-hr battery. So, half the 
> energy from the dynamo will charge the phone about once. 
>
> How large of a battery would hold that much electricity? Thanks to modern 
> lithium ion polymer technology, a small power-bank like this one 
> 
>  (about 
> the thickness of the iPhone but fits in the palm of your hand) can recharge 
> that phone ~1.5 times (implying it's got ~19 watt-hours of useful 
> capacity). A slightly larger one 
> 
>  
> (say about the size of the phone in a sturdy case) holds twice as much 
> energy, and even incorporates a charging plug. It's easy to chuck into a 
> bag, charge your phone off of it, use it as a wall plug in a hotel / on the 
> train, etc.  You don't even need to muck around with wiring on the bike or 
> a dyno hub at all. If you forego a dyno-powered light altogether, a battery 
> powered headlight will have 6+ hrs of its own battery life, and can be 
> charged off the portable battery. 
>
> In case you don't want to muck around with wires and connectors and all 
> that. But if someone's gonna do it all for you and anodize it nice colors, 
> then by all means! :-) 
>
> - Max "trying to unplug and plug it back in again" in A2
>
> On Friday, March 22, 2024 at 6:36:58 PM UTC-4 cz...@sonic.net wrote:
>
>> Hi Leah -
>>
>> I have been riding 40mm tires on my custom and 44mm tires on my Quickbeam 
>> and have noticed no difference in performance - only in comfort. I would 
>> imagine 48mm tires would be no worse in performance and slightly more 
>> comfortable.
>>
>> Regarding the light and charging your phone - I have an Edelux II on my 
>> Hubbuhubbuhz. Given that my wife cannot be without her phone, we have a 
>> Sinewave Revolution wired directly to the Edelux II. This may eliminate the 
>> potential of wiring a taillight to the Edelux II - but we use rechargeable 
>> taillights; that's not a problem for us.
>>
>> Hope this helps.
>>
>> Regards,
>>
>> Corwin
>> On Tuesday, March 19, 2024 at 6:10:14 PM UTC-7 Bicycle Belle Ding Ding! 
>> wrote:
>>
>>> I have had some of the same questions tumbling about in my brain as I 
>>> wait for the last of the parts for my Gravel & Travel Platy. I just got 
>>> back from a warm and delightful weekend of cycling in Philadelphia. I, a 
>>> newly minted Michigander, was happy to return to the shire, and for that, I 
>>> was welcomed with Second Winter. 
>>>
>>> Michigan is over here, doing me dirty. 
>>>
>>> I’m prevailing upon you to humor me and answer my questions, because a 
>>> lot 

[jira] [Commented] (KAFKA-16341) Fix un-compressed records

[Johnny Hsu (Jira)]

[ 
https://issues.apache.org/jira/browse/KAFKA-16341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17829517#comment-17829517
 ] 

Johnny Hsu commented on KAFKA-16341:


on it now, thanks for the reminder 

> Fix un-compressed records
> -
>
> Key: KAFKA-16341
> URL: https://issues.apache.org/jira/browse/KAFKA-16341
> Project: Kafka
>  Issue Type: Sub-task
>Reporter: Luke Chen
>    Assignee: Johnny Hsu
>Priority: Major
> Fix For: 3.8.0, 3.7.1
>
>




--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[RBW] Re: I have questions

[Johnny Alien]

Depends on the tires too. An overbuilt robust 42 will feel slower than a 
fairly supple 48. So if you are comparing a 48 to a 42 rene Herse tire it 
might feel a bit slower. I like GK and I think they roll pretty smooth. I 
can't remember if they have different "toughness" levels. I think you will 
be happy with them. I would personally for sure use those tires for that 
application.
On Tuesday, March 19, 2024 at 9:58:14 PM UTC-4 Jay wrote:

> Those are really nice looking wheels and I, and I'm sure everyone, looks 
> forward to seeing the final build.
>
> I was going to comment briefly about tires, though I've only got a handful 
> of years on large volume tires on the road (before I was strictly a roadie, 
> with 25mm's).  I don't feel a big difference going from 25 to 30, I do feel 
> a difference going up to a 43 (GKSS).  What's interesting is I don't feel a 
> huge difference going from 43 to 55.  In the last few weeks alone I've had 
> a chance to ride all the bikes and wheels/tires I have, and this was my 
> observation about tires as I was thinking about this during and after the 
> rides.  "Can 48 mm tires do a 15-17 mph road ride pace?"  If you can do 
> this on a 42, comfortably, I think you can do so on a 48 (maybe play with 
> the pressure a bit, to get what works best for speed/comfort balance).  I 
> used the 43's on a ride with my speedy friend a month ago and I kept up, 
> felt pretty comfortable (particularly on descents), but I had to work 
> harder...so I would also recommend a good fuelling strategy for your 2-day 
> event.  Good luck!
>
> Weather :-( I'm just outside Toronto and we're getting second (first?) 
> winter here since Saturday.  I know how you feel.  And the forecast doesn't 
> look great for next 1-2 weeks.  I'm getting out on the 55 tires more, 
> pumping them based on conditions and appreciating I have them and these 
> wider tire bikes, or I would be stuck on the trainer with a road bike 
> (yuck).
>
> On Tuesday, March 19, 2024 at 9:10:14 PM UTC-4 Bicycle Belle Ding Ding! 
> wrote:
>
>> I have had some of the same questions tumbling about in my brain as I 
>> wait for the last of the parts for my Gravel & Travel Platy. I just got 
>> back from a warm and delightful weekend of cycling in Philadelphia. I, a 
>> newly minted Michigander, was happy to return to the shire, and for that, I 
>> was welcomed with Second Winter. 
>>
>> Michigan is over here, doing me dirty. 
>>
>> I’m prevailing upon you to humor me and answer my questions, because a 
>> lot of you are having spring and flowers and sunshine, so this is the least 
>> you could do!
>>
>> I got the 50 cm Platy to take on trips. Will fit in the van better, will 
>> fit on Amtrak, be easier to shove in elevators, that sort of thing. But the 
>> tires I have on hand are 48 mm Gravel Kings. They are almost new. I’m 
>> considering taking a train to a ride this summer, but that means no Racing 
>> Platypus, only the purple one can fit. Can 48 mm tires do a 15-17 mph road 
>> ride pace? I have 42 on all my other bikes. Would 48s be slow? The ride is 
>> a 2 day event, 100 miles total. I’d like to keep the tires if I could, 
>> because they’re new and they are fat enough to also double as gravel tires, 
>> should I decide to do a gravel ride again. But I do more road rides than 
>> anything else, and if those 48s will cripple me, I’ll go back to 42s. 
>> What’s the consensus?
>>
>> Basket straps. I have the Nitto Basket Rack and even though I’ve disliked 
>> it in the past, I figure it’s pretty and I already own it and I might need 
>> a front rack for travel. But do I really have to put the ugly strap from 
>> bar to basket? Is the Nitto Basket Rack safer than the Mark’s Rack? I know 
>> Sergio was thrown when his Mark’s Rack loosened and hit the front tire and 
>> he’s missing significant chunks of front teeth! What is everyone doing 
>> about their front racks?
>>
>> Lights. I have an Edelux light. It’s not the right color for this build, 
>> but it’s perfectly good. But sometimes I think, “wouldn’t it be nice to 
>> have a light that would charge your phone?” The Sinewave Beacon 2 will do 
>> just that, but it sounds like it’s not a great road light. What are people 
>> using to charge phones on long rides away from home?
>>
>> I ordered my wheels today. This, because J at the Velocity booth in 
>> Philly talked me into them when he heard about the theme of my build. 
>> Here’s a sneak peek.
>>
>> And thanks for helping me out here! It’s good to hear people’s 
>> experiences and points of view!
>> Leah
>>
>>
>>

-- 
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/e5988a1b-3c4f-4a10-9bce-7b32d128a5f2n%40googlegroups.com.

[RBW] Re: FS: Box Two Mini-V Brakes & Tektro Levers

[Johnny Alien]

Sold

On Tuesday, March 19, 2024 at 1:23:54 PM UTC-4 Johnny Alien wrote:

> On hold pending payment. Thanks!
>
> On Tuesday, March 19, 2024 at 12:55:22 PM UTC-4 Johnny Alien wrote:
>
>> I got these Box Two mini V brakes to use on my Protogallop vs full V. I 
>> was just interested in how they worked and they worked great. I switched up 
>> to Mini Motos. Just because I wanted Paul parts. What makes the Box Two 
>> nice is 1. The look pretty nice 2. They are lightweight 3. They offer the 
>> most tire clearance on a mini-V next to the Paul brakes. I was able to get 
>> Ultrdynamico Cavas under it with just enough spare room. Anyway I went for 
>> the blink so I will pass these along at a good price to someone that wants 
>> to give mini-V brakes a shot. These are black and the brake pads are in 
>> great usable condition. I am going to include some Tektro 314 brake levers. 
>> They are cool because they allow for both short and long pull setup. Black 
>> with silver arms. They look like every Tektro brake lever out there. They 
>> work great but there is some wear on the black parts. Not a lot but enough 
>> that I am just going to throw them in for free (since mini-V's require 
>> short pull and most upright levers are longI think). $30 shipped gets 
>> all of it.
>>
>> https://www.modernbike.com/product-2126289808
>>
>

-- 
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/5d6aa0b3-4b5e-4017-b71a-d62ad068603bn%40googlegroups.com.

[RBW] Re: FS: Box Two Mini-V Brakes & Tektro Levers

[Johnny Alien]

On hold pending payment. Thanks!

On Tuesday, March 19, 2024 at 12:55:22 PM UTC-4 Johnny Alien wrote:

> I got these Box Two mini V brakes to use on my Protogallop vs full V. I 
> was just interested in how they worked and they worked great. I switched up 
> to Mini Motos. Just because I wanted Paul parts. What makes the Box Two 
> nice is 1. The look pretty nice 2. They are lightweight 3. They offer the 
> most tire clearance on a mini-V next to the Paul brakes. I was able to get 
> Ultrdynamico Cavas under it with just enough spare room. Anyway I went for 
> the blink so I will pass these along at a good price to someone that wants 
> to give mini-V brakes a shot. These are black and the brake pads are in 
> great usable condition. I am going to include some Tektro 314 brake levers. 
> They are cool because they allow for both short and long pull setup. Black 
> with silver arms. They look like every Tektro brake lever out there. They 
> work great but there is some wear on the black parts. Not a lot but enough 
> that I am just going to throw them in for free (since mini-V's require 
> short pull and most upright levers are longI think). $30 shipped gets 
> all of it.
>
> https://www.modernbike.com/product-2126289808
>

-- 
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/b98f5d6a-50ed-45c0-969a-59a94316feb3n%40googlegroups.com.

[RBW] FS: Box Two Mini-V Brakes & Tektro Levers

[Johnny Alien]

I got these Box Two mini V brakes to use on my Protogallop vs full V. I was 
just interested in how they worked and they worked great. I switched up to 
Mini Motos. Just because I wanted Paul parts. What makes the Box Two nice 
is 1. The look pretty nice 2. They are lightweight 3. They offer the most 
tire clearance on a mini-V next to the Paul brakes. I was able to get 
Ultrdynamico Cavas under it with just enough spare room. Anyway I went for 
the blink so I will pass these along at a good price to someone that wants 
to give mini-V brakes a shot. These are black and the brake pads are in 
great usable condition. I am going to include some Tektro 314 brake levers. 
They are cool because they allow for both short and long pull setup. Black 
with silver arms. They look like every Tektro brake lever out there. They 
work great but there is some wear on the black parts. Not a lot but enough 
that I am just going to throw them in for free (since mini-V's require 
short pull and most upright levers are longI think). $30 shipped gets 
all of it.

https://www.modernbike.com/product-2126289808

-- 
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/85417576-cd3f-4365-9540-4e6f65422391n%40googlegroups.com.

Re: [RBW] Re: Rapid rise derailleur suggestion

[Johnny Alien]

I have to think that most of the market for these is from the Rivendell fan 
base. I don't hear any other bike group talking about them at all. Because 
of that I kind of think IF Riv ends up bringing their new one to market the 
used scene will come WAY down. Just a theory. I really hope that I can test 
the theory (because they successfully release it)

On Tuesday, March 19, 2024 at 12:14:10 PM UTC-4 chintan...@gmail.com wrote:

> Thank you all for the replies :) Now that I know of the RR, every time I 
> am on an uphill and I have to push the gear to climb higher on the cassette 
> I feel some justification for having a "low-normal" derailleur. 
>
> Thanks also for clarifying that any of these will work well.
>
> The RR will also hypothetically make life a little easier in introducing a 
> friend to front and rear shifting- why does the same action push the bike 
> to a higher gear in the front and lower gear in the rear (I forget too..)
>
> On Tue, 19 Mar 2024 at 20:58, Miles Payton  wrote:
>
>> I got a used XTR M951 long cage derailleur for a song on ebay a few 
>> months ago. Maybe there's not much demand? The seller gave me a half off 
>> offer so I couldn't refuse. Anyway it works great and it appears they're 
>> usually $50-80 depending on the condition. Not bad for what was once a 
>> top-of-the-line derailleur. I'd just avoid the NOS stuff because that's 
>> where you start spending $200 or more. 
>> I've been plenty happy with mine. It's paired to Gevenalle 10 speed 
>> shifters on my Atlantis. I can't speak to replacement parts but it wouldn't 
>> be expensive to replace, and my old M900 hasn't needed more than a rebuild 
>> in 20 years. They're pretty well-made.
>>
>> On Monday, March 18, 2024 at 12:01:39 PM UTC-5 chintan jadwani wrote:
>>
>>> I'm looking to try a RR derailleur and want something under 50-60 
>>> ideally.
>>>
>>> Which ones would you recommend? Were there are early RR derailleurs that 
>>> one should stay from or budget ones that are a good value? Were there 
>>> differences in pulley sizes - so would be better to get one where 
>>> replacements are available?
>>>
>>> I'm currently seeing an LX m580, xt M760, an xtr m951 and xtr m952 
>>> around that range on ebay in different used conditions...and then the 
>>> prices rise very quickly! 
>>>
>>> Thanks a lot for guiding :)
>>> Chintan
>>>
>> -- 
>> 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/W7fPfdsBFqw/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/a54c1daa-9eed-4c93-a14b-291f86853932n%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/9084c968-a957-4f2f-bb00-43344136f22cn%40googlegroups.com.

[jira] [Commented] (KAFKA-16323) Failing test: fix testRemoteFetchExpiresPerSecMetric

[Johnny Hsu (Jira)]

[ 
https://issues.apache.org/jira/browse/KAFKA-16323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17828304#comment-17828304
 ] 

Johnny Hsu commented on KAFKA-16323:


I have added logs to observe and tried to verify some potential causes:
 # check whether it really enters the delayed remote fetch
 # check whether it really enters the onExpire() section
 # check whether it succeeds in marking the metrics

All verified and works as expected. 

 

Thanks to [~showuon], I also tried to add @BeforeAll to the tear down function, 
which remove all metrics before the test. However it still failed. 

Need some more tries to find the root causes...

> Failing test: fix testRemoteFetchExpiresPerSecMetric 
> -
>
> Key: KAFKA-16323
> URL: https://issues.apache.org/jira/browse/KAFKA-16323
> Project: Kafka
>  Issue Type: Bug
>  Components: core
>    Reporter: Johnny Hsu
>Assignee: Johnny Hsu
>Priority: Major
>  Labels: test-failure
>
> Refer to 
> [https://ci-builds.apache.org/job/Kafka/job/kafka/job/trunk/2685/testReport/junit/kafka.server/ReplicaManagerTest/Build___JDK_21_and_Scala_2_13___testRemoteFetchExpiresPerSecMetric__/]
> This test is failing, and this ticket aims to address this 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)