加入apisix slack 频道

2024-06-04 Thread jc du



[Standards] Re: XEP-0424/425 Feedback

2024-05-14 Thread JC Brand

Hi Philipp,

sorry for the late response. Please see my replies inline.

On 2024/04/16 21:31, Philipp Hörist wrote:

Hi,

Some feedback while trying to implement these XEPs

XEP-0424
1)
The schema mentions



But the XEP does not mention the attribute, what is the purpose?


Looks like it's not necessary. I'll remove it.



2)
> When replacing the original message with a tombstone, the original 
contents (i.e. the  and any related elements which might leak 
information about the original message) get replaced with a 
 element which MUST include an 'id' attribute referring to 
the original message


Why does the element MUST have an id attribute? its a element inside 
the  which already has the id, or in case of groupchat its 
inside a mam wrapper which has a stanza id, in all cases its perfectly 
clear that the retracted element belongs to the actual message 
wrapping it, maybe im missing something obvious here but i dont see a 
need for this id attribute at all.


The id on the  is not guaranteed to be globally unique and the 
XEP states that if the origin-id was specified, that should be used with 
the  id as fallback.
The idea behind it is to allow clients to identify the original message 
if it was cached and replace it with the tombstone.
One could argue that if you're doing a MAM query, you're doing it for 
messages you don't already have cached. I think that's true, but I'm not 
sure I want to remove the ability to find an already cached message from 
a tombstone.




Example 7

> For messages of type 'groupchat', the stanza's Unique and Stable 
Stanza IDs (XEP-0359) <https://xmpp.org/extensions/xep-0359.html> [4 
<https://xmpp.org/extensions/xep-0424.html#nt-idm41385450875712>] 
'origin ID' MUST NOT be used for retractions


Example mentions origin-id in groupchat context


    





XEP-0425
1)
> A Message Archive Management (XEP-0313) 
<https://xmpp.org/extensions/xep-0313.html> [6 
<https://xmpp.org/extensions/xep-0425.html#nt-idm34711750431632>] 
service MAY replace the contents of a message, that was retracted due 
to moderation, with a 'tombstone' similar to the one described in 
Mess//age Retraction (XEP-0424) 
<https://xmpp.org/extensions/xep-0424.html> [5 
<https://xmpp.org/extensions/xep-0425.html#nt-idm34711750445088>].


How similiar? The tombstone text does not mention seemingly important 
MUST rules from XEP 0424


For example

> Some clients may have been offline while the retraction was issued. 
The archiving service therefore MUST store the retraction message, 
regardless of whether the original message is deleted or replaced with 
a tombstone.


the above mentioned MUST rule about the id attribute in the 
 element, seems to be not important anymore in moderation, 
at least the id attribute is not found anymore in the tombstone.


Im not saying we need to copy text 1:1 between the XEPs, but should 
the XEP not go into more detail what exactly the differences are, and 
what exactly from 0424 applies?


I think the main issue is that the id isn't needed for MUCs, but it is 
needed for 1:1 chats, since 1:1 message IDs aren't guaranteed to be unique.


I'm not sure what the best solution is here. The text in 424 can be 
updated to state that the MUST is necessary only for 1:1 message, but 
not MUC messages.

What do you think?

Regards
JC
___
Standards mailing list -- standards@xmpp.org
To unsubscribe send an email to standards-le...@xmpp.org


[Members] Re: Extending the XSF Community Code of Conduct (XEP-0458)

2024-04-29 Thread JC Brand

Hi Jonas

On 2024/04/27 10:36, Jonas Schäfer wrote:

Hello JC,

On Samstag, 27. April 2024 09:33:42 CEST JC Brand wrote:

On 2024/04/26 15:35, Jonas Schäfer wrote:

On Freitag, 26. April 2024 13:01:12 CEST JC Brand wrote:

One can always come up with more categories of marginalized people, and
trying to enumerate all of them in a CoC is IMO impractical, while
mentioning only some of them can create the impression that some
categories of people are "more equal" than others.

They are though, or should be anyway. People from marginalized groups are
just that, marginalized. We as an organisation should do the extra effort
to support individuals from these groups in order to allow them to be
safe in our spaces, to live up to their potential and what they'd like to
achieve and contribute.

You're basically advocating for so-called positive discrimination (aka
affirmative action), which is a political position advocated for by
certain political groupings.
I'm on record from previous discussions in saying that I don't think a
supposedly neutral standards organization should be instrumentalized for
the furtherance of political programmes.

"supposedly" is the key word here.

Neutrality does not exist. Let me paint you a picture (pun intended). In
photography, an important parameter when baking a picture into something which
can be viewed on screen is the so-called White Balance. Most of the time, it
controls the shift between red and blue in a picture [^1]. White balance is
normally configured by using a piece of plastic which is known to be "neutral
grey" and asking the picture processor to calibrate on that. It will then
shift the tint of the picture so that the sensor values in the area of the
neutral grey card get converted to 50% gray in RGB.

The same thing happens in brains, by the way. The (maybe) white wall in your
room is by no means emitting "white" light in your direction: it is reflecting
whichever colour your room lighting currently has, which is very unlikely to
be what some standards committee has defined as neutral white.

Now, does anyone remember that dress picture from a couple years back, which
divided the internet on whether the dress was blue or golden? That was
basically a white balance issue: without a point of reference for the brain to
identify "gray" in the picture, people in different contexts will see
different colours (because the white balance in your brain gets thrown off).

It is the same with political neutrality. The XSF is not "neutral gray".
Neutral gray, like neutral white, is an artificial construct which does not
stably exist. The XSF is some different shade, but because of your context, it
*looks* neutral gray to you [^2].


You seem to interpret "neutral" to mean an objective and unbiased view 
(i.e. picture) of the world.


That's not what I mean when I use the word neutral here. Instead, I mean 
"not getting involved in".


The XSF is a technical standards organization, not an activist or 
political organization. So it should stay neutral by not getting 
involved in activism, political programmes and attempts at social 
engineering.

Seen in that light, the analogy regarding photography is largely irrelevant.


We accommodate military use (another highly "politically charged" topic) of
our products: see for example XEP-0365, which specifies the use of XMPP over
some NATO communication standard.

It's an open standard. If you wanted to exclude certain groups of people 
from using and extending it, it would no longer be an open standard.


There's nothing in our bylaws or in any XEP that says you need to 
support Nato or pay deference to it.


In any case, I would not be surprised if the Russian military was also 
using XMPP on the battlefield.



This looks like neutral gray only if you live in or are affiliated with NATO 
countries and are not opposed to NATO or
military in general.


I don't live in a Nato country and believe there's lots to criticize 
about it, but both those facts are irrelevant to the XSF's mission.



There are politically contentious topics surrounding what constitutes
marginalized identities and how one (and society) should go about
accommodating them.
We're running the risk if introducing these politically divisive topics
into the XSF, thereby politicizing the organization which will likely
introduce the same divisiveness, acrimony and bitterness that
characterizes political debates.

Oh, the division and bitterness is there. You currently just have the "luxury"
to not see it, because the people who are divided away and get bitter are not
joining and/or have left the XSF (yes, this is happening / has happened).

[I said "you", instead of "we", above, because I in fact do see the division
and bitterness. It takes place outside the XSF spaces for obvious reasons.]

You make an awful lot of assumptions about me Jonas.

I d

[Members] Re: Extending the XSF Community Code of Conduct (XEP-0458)

2024-04-27 Thread JC Brand

On 2024/04/26 15:35, Jonas Schäfer wrote:




One can always come up with more categories of marginalized people, and
trying to enumerate all of them in a CoC is IMO impractical, while
mentioning only some of them can create the impression that some
categories of people are "more equal" than others.

They are though, or should be anyway. People from marginalized groups are just
that, marginalized. We as an organisation should do the extra effort to
support individuals from these groups in order to allow them to be safe in our
spaces, to live up to their potential and what they'd like to achieve and
contribute.


You're basically advocating for so-called positive discrimination (aka 
affirmative action), which is a political position advocated for by 
certain political groupings.
I'm on record from previous discussions in saying that I don't think a 
supposedly neutral standards organization should be instrumentalized for 
the furtherance of political programmes.



At the end of the day, the tiniest minority is the individual, and
requiring that we treat each individual with respect and courtesy is
enough, without having to refer to specific (sometimes politically
charged) categories.

Could you clarify "sometimes politically charged"?
There are politically contentious topics surrounding what constitutes 
marginalized identities and how one (and society) should go about 
accommodating them.
We're running the risk if introducing these politically divisive topics 
into the XSF, thereby politicizing the organization which will likely 
introduce the same divisiveness, acrimony and bitterness that 
characterizes political debates. I don't think this benefits the 
organization or aids in the furtherance of standards development.


JC



[Members] Re: Extending the XSF Community Code of Conduct (XEP-0458)

2024-04-26 Thread JC Brand

Hi Jonas

On 2024/04/25 18:01, Jonas Schäfer wrote:

Hi everyone,

Going through the CoC again, I notice that it has a few gaps we should
probably address.

While the current wording explicitly prohibits racist language, there are a
lot of other *-isms which are unfortunately quite present in various spaces on
the XMPP network and which sometimes roll into XSF rooms.

I do not think that we want to be perceived as, for instance, an anti-LGBTQIA+
community, so we should extend the CoC to:

a) send the clear message to the world that we won't tolerate behaviour that,
and
b) give our moderators (that includes me in some places) the necessary holding
to enforce when necessary

Concretely, I propose that we add to 2.4 Be respectful, the following items on
the list of things to avoid:


- Use of racist, misogynistic, anti-trans, anti-gay, ableist slurs, or other
   derogatory pejoratives for oppressed identity groups against such groups.

- Blatantly racist, casteist, ableist, sexist, anti-trans, or otherwise
   offensive and bigoted discourse.


FWIW, I don't think coming up with ever more fine-grained categorization 
of what constitutes marginalized persons and putting that in the CoC is 
the right way to go.
One can always come up with more categories of marginalized people, and 
trying to enumerate all of them in a CoC is IMO impractical, while 
mentioning only some of them can create the impression that some 
categories of people are "more equal" than others.


At the end of the day, the tiniest minority is the individual, and 
requiring that we treat each individual with respect and courtesy is 
enough, without having to refer to specific (sometimes politically 
charged) categories.



In addition, before the list of things to avoid, I would like to add:


Respect others requests for space. That includes to disengage from a
discourse if your partner(s) indicate that they do not want to discuss a
topic any further. It is not easy to let someone be "wrong" on the internet,
but boundaries are there to be respected.


I'm +0 on this. Part of me thinks this is already handled by disallowing 
harassment.



To section 2.5 ("Be friendly and supportive"), I would like to add after the
first paragraph:


This includes being mindful of the abilities of others; nobody is born an
expert in anything and we all had to learn at some point. Be supportive of
newcomers and learners. Do not be patronizing or condescending.


I agree and support adding this paragraph.

JC


CD vendeurs debian

2024-04-22 Thread jc gucci
https://www.debian.org/CD/vendors/#fr
vendeur de support d'installation de debian
https://www.getlinux.f le lien fonctionne j'ai pas encore essayé la
commande (5,99$)
https://www.hypra.fr/ le lien ne fonctionne pas


[linux] Password management and file encryption

2024-04-20 Thread Nash JC - NCF via linux

Follow-up to some earlier discussion. Thanks to those who commented.

I'm developing some discussion documents about password management (including the survivorship / executor issue) with 
companion file encryption document. Free / Open source is a priority, though proprietary solutions are mentioned too. 
Drafts (comments and contributions welcome) at

https://github.com/nashjc/CryptPass

John Nash

To unsubscribe send a blank message to linux+unsubscr...@linux-ottawa.org
To get help send a blank message to linux+h...@linux-ottawa.org
To visit the archives: https://lists.linux-ottawa.org



magazine linux et obtention de debian stable 12 X86 gnome

2024-04-13 Thread jc gucci
je suis en wifi, en bande passante limité , j'ai donc pensé qu'il
etait possible d'obtenir le dvd via un magazine. dans quels magazines est
ou sera inclus le prochain debian sinon comment l'obtenir (envoi par ups,
poste , lug ?).
merci.


LTS bulleye ou bookworm

2024-04-06 Thread jc gucci
je ne comprends pas comment la 11 peut etre disponible alors qu'elle est
prevu pour le 15 aout et la 12 pour 2026.
Que dois-je choisir - en lts - ?
merci.


[linux] updated presentation with scripts

2024-04-05 Thread Nash JC - NCF via linux

I added whitespace fix to the scripts in the presentation on the Wiki.

Scott's suggestion to run a demo revealed that glitch, and it was worth
fixing.

JN

To unsubscribe send a blank message to linux+unsubscr...@linux-ottawa.org
To get help send a blank message to linux+h...@linux-ottawa.org
To visit the archives: https://lists.linux-ottawa.org



退订

2024-03-26 Thread chao jc
退订


[linux] password keepers

2024-03-21 Thread Nash JC - NCF via linux

For the past few months I've been looking into secure cloud storage, partly for
use with my writings (about 80GB) and partly for use for my own scripted
"password" manager. My password setup handles a lot of extra stuff like serial 
numbers,
document references and things that aren't passwords but just small text
blocks. Some of you have probably seen some queries I've put around about cloud
storage. Quite a bit of annoying detail there, and that has been written up
in draft form.

A particular need is to export the data to a text file that is regularly
put on a USB in a secure storage for institutional executors, with the
decryption keys kept separately.

Bitwarden looks like a possibility, if anyone has experience with it.
I'd also be interested in other perspectives.

I've been writing up my investigations, and will be happy to give a talk
on my findings, as I can't believe issues like these are peculiar to me.
So comments and suggestions are welcome, if possible with context, as I've
been finding small details seem to get in the way of convenient usage.

Best,

John Nash

To unsubscribe send a blank message to linux+unsubscr...@linux-ottawa.org
To get help send a blank message to linux+h...@linux-ottawa.org
To visit the archives: https://lists.linux-ottawa.org



IPV6+mac

2024-03-12 Thread jc gucci
option pour desactiver la generation de l'adresse ipv6 base sur l'adresse
mac : pour stretch + version superieur.
j'ai fait des recherche et je n'ai pas trouve pouvez-vous eclaircir le
sujet ?
(ordinateur individuel-portable) merci.


Re: [linux] Linux-Ottawa / NCF collaboration

2024-01-25 Thread Nash JC - NCF

As far as I am aware, there's no intent that Linux-Ottawa folk should have to 
pay
for joining a mailing list. There was a note in one earlier post (some months 
ago)
that NCF had some legacy setup that restricted some of their facilities to 
"members"
and that we might have to sort out details.

JN

On 2024-01-25 16:54, Katherine Mcmillan wrote:

I am in agreement with JF

Sincerely,
Katie

*From:* Jean-Francois Messier 
*Sent:* Thursday, January 25, 2024 4:50:33 PM
*To:* Ian! D. Allen 
*Cc:* Linux-Ottawa 
*Subject:* Re: [linux] Linux-Ottawa / NCF collaboration
*Attention : courriel externe | external email*
I would call this a MAJOR obstacle. If Freenet/NCF is hoping to get money from everyone joining this list on an annual 
basis, although OCLUG gave them thousands of dollars already, we should dissociate from Freenet/NCF. The decision to 
send the money to NCF was an honest mistake, but let's not keep our dependency on NCF. Who knows what else they will ask 
from the members in the future ?


On Thu, Jan 25, 2024 at 4:37 PM Ian! D. Allen mailto:idal...@idallen.ca>> wrote:

Re:

- Yes, I'd call it an obstacle
- I agree [...] Is not going to work.
- I agree.  While the money is not a problem for me it is sort of offensive.

The new person joining does not have to pay this fee.  Imagine this:

"Hello and welcome to OCLUG.  We have teamed up with the local Free-Net
to sponsor a mailing list account for you so that you may participate
in discussions around Linux and other Free-Libre Open Source Software
[FLOSS].  We hope that at some point you become a paid-up member of
OCLUG to help support this and other FLOSS projects.  Welcome aboard."

-- 
| Ian! D. Allen, BA-Psych, MMath-CompSci idal...@idallen.ca  Ottawa CANADA

| Home: www.idallen.com   Contact Improvisation 
Dance: www.contactimprov.ca

| Former college professor of Free/Libre GNU+Linux @ teaching.idallen.com 

| Improve democracy www.fairvote.ca  and defend digital 
freedom www.eff.org 

To unsubscribe send a blank message to linux+unsubscr...@linux-ottawa.org 

To get help send a blank message to linux+h...@linux-ottawa.org 

To visit the archives: https://lists.linux-ottawa.org 




--
Geek, c'est ma nature
Linux, c'est mon choix !


To unsubscribe send a blank message to linux+unsubscr...@linux-ottawa.org
To get help send a blank message to linux+h...@linux-ottawa.org
To visit the archives: https://lists.linux-ottawa.org



Re: Re: [linux] Strange Email Issues with this list - gmail spamming myself

2024-01-25 Thread Nash JC - NCF

Perhaps I should have said that unless someone volunteers, what we have
is what will be available, rather than commenting on the properties of
mlmmj.

Linux-Ottawa is purely volunteer supported.
As will all such groups, that's its strength and also weakness.

Does anyone have sufficient motivation to replace the maillist s/w?

JN


On 2024-01-25 14:54, Dianne Skoll wrote:

On Thu, 25 Jan 2024 14:30:07 -0500
Nash JC - NCF  wrote:


Like many things, what we have more or less works,


I don't agree with that assessment...


so there's not a lot of incentive to fix the edge cases.


Both of the large email providers (Google and Microsoft) are starting
to crack down and enforce SPF/DKIM/DMARC more vigorously.  I would guess
a large percentage of OCLUG subscribers are on one of those providers
and much OCLUG traffic is likely not being delivered to them reliably.



I just downloaded mlmmj source code and docs and a text search did not
get a hit on DKIM, so probably does not support it.


mlmmj is written in C and the last release was almost 7 years ago.
Both of those facts IMO are red flags. :)

Regards,

Dianne.


To unsubscribe send a blank message to linux+unsubscr...@linux-ottawa.org
To get help send a blank message to linux+h...@linux-ottawa.org
To visit the archives: https://lists.linux-ottawa.org



Re: [linux] Strange Email Issues with this list - gmail spamming myself

2024-01-25 Thread Nash JC - NCF

We've been using mlmmj. Scott has kept it running, but I'm pretty sure he's
happy if someone would set up something better. However, we've had
people say they were going to do that, then not carry through.

Like many things, what we have more or less works, so there's not a lot of
incentive to fix the edge cases. But I agree it can be annoying.

I just downloaded mlmmj source code and docs and a text search did not
get a hit on DKIM, so probably does not support it.

JN


On 2024-01-25 13:56, Dianne Skoll wrote:

On Thu, 25 Jan 2024 13:32:23 -0500
Alan McKay  wrote:


Here is a curious issue that I see on this list only - gmail flags my
own emails as potential spam.


This is a longstanding problem with the OCLUG list software.  If you use
DKIM, then this list breaks DKIM.  And gmail.com uses DKIM.

I've mentioned it in the past (actually nagged/complained about it) but
nothing has been done.  GNU mailman (version 2... I don't use 3) can
handle this properly, but apparently whatever software this list uses
(ezmlm maybe?) cannot. :(

It's frustrating as hell.

Regards,

Dianne.

To unsubscribe send a blank message to linux+unsubscr...@linux-ottawa.org
To get help send a blank message to linux+h...@linux-ottawa.org
To visit the archives: https://lists.linux-ottawa.org



To unsubscribe send a blank message to linux+unsubscr...@linux-ottawa.org
To get help send a blank message to linux+h...@linux-ottawa.org
To visit the archives: https://lists.linux-ottawa.org



Re: [linux] December Meeting: 2023-12-07 @ 19:00

2023-12-07 Thread Nash JC - NCF

Anyone going to take on moderator role (I think this is a change in 
meet.jit.si)?

JN

On 2023-12-03 15:38, Scott Murphy wrote:

Meeting Announcement

Linux-Ottawa December 2023 Meeting.

Date/Time:

Thursday December 7th at 7pm

Format:

1. Online over Jitsi https://meet.jit.si/oclug_2023-12-07

2. Check mailing list for in-person clusters being hosted by other members.

Program:

Topics

1. Script Night: If you have a useful script you want to share, or a problem 
script you want to rescue, bring it along.

Current offerings include

John Nash - scripts to move data to and from cloud storage.

Tug Williams - using bash to download and compress feeds for use over low 
bandwidth connections.

Anyone else! - anything anyone wants to bring up.



To unsubscribe send a blank message to linux+unsubscr...@linux-ottawa.org
To get help send a blank message to linux+h...@linux-ottawa.org
To visit the archives: https://lists.linux-ottawa.org



To unsubscribe send a blank message to linux+unsubscr...@linux-ottawa.org
To get help send a blank message to linux+h...@linux-ottawa.org
To visit the archives: https://lists.linux-ottawa.org



Re: The Python module "subvertpy" is not installed.

2023-11-01 Thread JC Anderson
Is there a better forum for discussing installation issues?

Thanks
Chris

On Monday, October 30, 2023 at 1:45:46 PM UTC-5 JC Anderson wrote:

> I must be installing it wrong.  Does the install process I did look ok?
>
> Thanks
> Chris
>
> On Thursday, October 26, 2023 at 1:29:39 PM UTC-5 JC Anderson wrote:
>
>> root@debian:/opt/bitnami# source 
>> /opt/bitnami/reviewboard/venv/bin/activate
>> (venv) root@debian:/opt/bitnami# python /opt/bitnami/pysvn_install.py
>> Looking up latest PySVN version...
>> Downloading PySVN 1.9.20...
>> Building PySVN...
>> Processing /tmp/tmpmqdhm70x.pysvn-install/pysvn-1.9.20
>>   Preparing metadata (setup.py) ... done
>> Building wheels for collected packages: pysvn
>>   Building wheel for pysvn (setup.py) ... done
>>   Created wheel for pysvn: 
>> filename=pysvn-1.9.20-cp38-cp38-linux_x86_64.whl size=736343 
>> sha256=6cc30b8cc648896617273a767a69a7286f5a18c75bb1a662072a1d3a5567e1d6
>>   Stored in directory: 
>> /root/.cache/pip/wheels/89/4a/32/870d0959e91d5f2c0b06836f41dc5fad01782ecf05ac85aa68
>> Successfully built pysvn
>> Installing collected packages: pysvn
>>   Attempting uninstall: pysvn
>> Found existing installation: pysvn 1.9.20
>> Uninstalling pysvn-1.9.20:
>>   Successfully uninstalled pysvn-1.9.20
>> Successfully installed pysvn-1.9.20
>>
>> [notice] A new release of pip is available: 23.2.1 -> 23.3.1
>> [notice] To update, run: pip install --upgrade pip
>>
>> PySVN is installed.
>> (venv) root@debian:/opt/bitnami# bash ctlscript.sh restart
>> restarting services...
>> (venv) root@debian:/opt/bitnami#
>>
>> On Wednesday, October 25, 2023 at 10:29:02 PM UTC-5 Christian Hammond 
>> wrote:
>>
>>> Hi Chris,
>>>
>>> That error is confusing and we've fixed it for Review Board 6 (by 
>>> removing Subvertpy support — that project is barely maintained anymore). 
>>> It's only mentioning Subvertpy because it was the last installed SVN 
>>> implementation it tried to scan for.
>>>
>>> If you're getting that error, then PySVN didn't actually install, or 
>>> install into the right Python environment. Can you show me how you tried 
>>> installing it in Bitnami?
>>>
>>> I'd have expected Bitnami to have had this installed by default.
>>>
>>> Christian
>>>
>>>
>>> On Tue, Oct 24, 2023 at 11:53 AM JC Anderson  wrote:
>>>
>>>> I'm new to the ReviewBoard community.
>>>> I'm trying to get the Bitnami Debian vm version (5.0.6) up and running 
>>>> for subversion.
>>>> I've installed pysvn using the RB install script and restarted the vm.
>>>> Trying to add a svn repo gives me this error: 
>>>>
>>>> *The Python module "subvertpy" is not installed. You may need to 
>>>> restart the server after installing it.*
>>>>
>>>> Any ideas on how to troubleshoot?
>>>>
>>>> Thanks
>>>> Chris
>>>>
>>>> -- 
>>>> Supercharge your Review Board with Power Pack: 
>>>> https://www.reviewboard.org/powerpack/
>>>> Want us to host Review Board for you? Check out RBCommons: 
>>>> https://rbcommons.com/
>>>> Happy user? Let us know! https://www.reviewboard.org/users/
>>>> --- 
>>>> You received this message because you are subscribed to the Google 
>>>> Groups "Review Board Community" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send 
>>>> an email to reviewboard...@googlegroups.com.
>>>> To view this discussion on the web visit 
>>>> https://groups.google.com/d/msgid/reviewboard/13c0d007-121a-4dda-8f52-87a97508f573n%40googlegroups.com
>>>>  
>>>> <https://groups.google.com/d/msgid/reviewboard/13c0d007-121a-4dda-8f52-87a97508f573n%40googlegroups.com?utm_medium=email_source=footer>
>>>> .
>>>>
>>>
>>>
>>> -- 
>>> Christian Hammond
>>> President/CEO of Beanbag <https://www.beanbaginc.com/>
>>> Makers of Review Board <https://www.reviewboard.org/>
>>>
>>

-- 
Supercharge your Review Board with Power Pack: 
https://www.reviewboard.org/powerpack/
Want us to host Review Board for you? Check out RBCommons: 
https://rbcommons.com/
Happy user? Let us know! https://www.reviewboard.org/users/
--- 
You received this message because you are subscribed to the Google Groups 
"Review Board Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/reviewboard/d490052a-d5c7-4c4a-8b65-897477991745n%40googlegroups.com.


Re: The Python module "subvertpy" is not installed.

2023-10-30 Thread JC Anderson
I must be installing it wrong.  Does the install process I did look ok?

Thanks
Chris

On Thursday, October 26, 2023 at 1:29:39 PM UTC-5 JC Anderson wrote:

> root@debian:/opt/bitnami# source /opt/bitnami/reviewboard/venv/bin/activate
> (venv) root@debian:/opt/bitnami# python /opt/bitnami/pysvn_install.py
> Looking up latest PySVN version...
> Downloading PySVN 1.9.20...
> Building PySVN...
> Processing /tmp/tmpmqdhm70x.pysvn-install/pysvn-1.9.20
>   Preparing metadata (setup.py) ... done
> Building wheels for collected packages: pysvn
>   Building wheel for pysvn (setup.py) ... done
>   Created wheel for pysvn: 
> filename=pysvn-1.9.20-cp38-cp38-linux_x86_64.whl size=736343 
> sha256=6cc30b8cc648896617273a767a69a7286f5a18c75bb1a662072a1d3a5567e1d6
>   Stored in directory: 
> /root/.cache/pip/wheels/89/4a/32/870d0959e91d5f2c0b06836f41dc5fad01782ecf05ac85aa68
> Successfully built pysvn
> Installing collected packages: pysvn
>   Attempting uninstall: pysvn
> Found existing installation: pysvn 1.9.20
> Uninstalling pysvn-1.9.20:
>   Successfully uninstalled pysvn-1.9.20
> Successfully installed pysvn-1.9.20
>
> [notice] A new release of pip is available: 23.2.1 -> 23.3.1
> [notice] To update, run: pip install --upgrade pip
>
> PySVN is installed.
> (venv) root@debian:/opt/bitnami# bash ctlscript.sh restart
> restarting services...
> (venv) root@debian:/opt/bitnami#
>
> On Wednesday, October 25, 2023 at 10:29:02 PM UTC-5 Christian Hammond 
> wrote:
>
>> Hi Chris,
>>
>> That error is confusing and we've fixed it for Review Board 6 (by 
>> removing Subvertpy support — that project is barely maintained anymore). 
>> It's only mentioning Subvertpy because it was the last installed SVN 
>> implementation it tried to scan for.
>>
>> If you're getting that error, then PySVN didn't actually install, or 
>> install into the right Python environment. Can you show me how you tried 
>> installing it in Bitnami?
>>
>> I'd have expected Bitnami to have had this installed by default.
>>
>> Christian
>>
>>
>> On Tue, Oct 24, 2023 at 11:53 AM JC Anderson  wrote:
>>
>>> I'm new to the ReviewBoard community.
>>> I'm trying to get the Bitnami Debian vm version (5.0.6) up and running 
>>> for subversion.
>>> I've installed pysvn using the RB install script and restarted the vm.
>>> Trying to add a svn repo gives me this error: 
>>>
>>> *The Python module "subvertpy" is not installed. You may need to restart 
>>> the server after installing it.*
>>>
>>> Any ideas on how to troubleshoot?
>>>
>>> Thanks
>>> Chris
>>>
>>> -- 
>>> Supercharge your Review Board with Power Pack: 
>>> https://www.reviewboard.org/powerpack/
>>> Want us to host Review Board for you? Check out RBCommons: 
>>> https://rbcommons.com/
>>> Happy user? Let us know! https://www.reviewboard.org/users/
>>> --- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "Review Board Community" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to reviewboard...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/reviewboard/13c0d007-121a-4dda-8f52-87a97508f573n%40googlegroups.com
>>>  
>>> <https://groups.google.com/d/msgid/reviewboard/13c0d007-121a-4dda-8f52-87a97508f573n%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>>
>>
>>
>> -- 
>> Christian Hammond
>> President/CEO of Beanbag <https://www.beanbaginc.com/>
>> Makers of Review Board <https://www.reviewboard.org/>
>>
>

-- 
Supercharge your Review Board with Power Pack: 
https://www.reviewboard.org/powerpack/
Want us to host Review Board for you? Check out RBCommons: 
https://rbcommons.com/
Happy user? Let us know! https://www.reviewboard.org/users/
--- 
You received this message because you are subscribed to the Google Groups 
"Review Board Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/reviewboard/d753acb1-b59b-4712-adec-304a3059db74n%40googlegroups.com.


Re: The Python module "subvertpy" is not installed.

2023-10-26 Thread JC Anderson
root@debian:/opt/bitnami# source /opt/bitnami/reviewboard/venv/bin/activate
(venv) root@debian:/opt/bitnami# python /opt/bitnami/pysvn_install.py
Looking up latest PySVN version...
Downloading PySVN 1.9.20...
Building PySVN...
Processing /tmp/tmpmqdhm70x.pysvn-install/pysvn-1.9.20
  Preparing metadata (setup.py) ... done
Building wheels for collected packages: pysvn
  Building wheel for pysvn (setup.py) ... done
  Created wheel for pysvn: filename=pysvn-1.9.20-cp38-cp38-linux_x86_64.whl 
size=736343 
sha256=6cc30b8cc648896617273a767a69a7286f5a18c75bb1a662072a1d3a5567e1d6
  Stored in directory: 
/root/.cache/pip/wheels/89/4a/32/870d0959e91d5f2c0b06836f41dc5fad01782ecf05ac85aa68
Successfully built pysvn
Installing collected packages: pysvn
  Attempting uninstall: pysvn
Found existing installation: pysvn 1.9.20
Uninstalling pysvn-1.9.20:
  Successfully uninstalled pysvn-1.9.20
Successfully installed pysvn-1.9.20

[notice] A new release of pip is available: 23.2.1 -> 23.3.1
[notice] To update, run: pip install --upgrade pip

PySVN is installed.
(venv) root@debian:/opt/bitnami# bash ctlscript.sh restart
restarting services...
(venv) root@debian:/opt/bitnami#

On Wednesday, October 25, 2023 at 10:29:02 PM UTC-5 Christian Hammond wrote:

> Hi Chris,
>
> That error is confusing and we've fixed it for Review Board 6 (by removing 
> Subvertpy support — that project is barely maintained anymore). It's only 
> mentioning Subvertpy because it was the last installed SVN implementation 
> it tried to scan for.
>
> If you're getting that error, then PySVN didn't actually install, or 
> install into the right Python environment. Can you show me how you tried 
> installing it in Bitnami?
>
> I'd have expected Bitnami to have had this installed by default.
>
> Christian
>
>
> On Tue, Oct 24, 2023 at 11:53 AM JC Anderson  wrote:
>
>> I'm new to the ReviewBoard community.
>> I'm trying to get the Bitnami Debian vm version (5.0.6) up and running 
>> for subversion.
>> I've installed pysvn using the RB install script and restarted the vm.
>> Trying to add a svn repo gives me this error: 
>>
>> *The Python module "subvertpy" is not installed. You may need to restart 
>> the server after installing it.*
>>
>> Any ideas on how to troubleshoot?
>>
>> Thanks
>> Chris
>>
>> -- 
>> Supercharge your Review Board with Power Pack: 
>> https://www.reviewboard.org/powerpack/
>> Want us to host Review Board for you? Check out RBCommons: 
>> https://rbcommons.com/
>> Happy user? Let us know! https://www.reviewboard.org/users/
>> --- 
>> You received this message because you are subscribed to the Google Groups 
>> "Review Board Community" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to reviewboard...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/reviewboard/13c0d007-121a-4dda-8f52-87a97508f573n%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/reviewboard/13c0d007-121a-4dda-8f52-87a97508f573n%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>
>
> -- 
> Christian Hammond
> President/CEO of Beanbag <https://www.beanbaginc.com/>
> Makers of Review Board <https://www.reviewboard.org/>
>

-- 
Supercharge your Review Board with Power Pack: 
https://www.reviewboard.org/powerpack/
Want us to host Review Board for you? Check out RBCommons: 
https://rbcommons.com/
Happy user? Let us know! https://www.reviewboard.org/users/
--- 
You received this message because you are subscribed to the Google Groups 
"Review Board Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/reviewboard/a0c07d30-6202-42b8-8e13-095d69e21ecan%40googlegroups.com.


The Python module "subvertpy" is not installed.

2023-10-24 Thread JC Anderson
I'm new to the ReviewBoard community.
I'm trying to get the Bitnami Debian vm version (5.0.6) up and running for 
subversion.
I've installed pysvn using the RB install script and restarted the vm.
Trying to add a svn repo gives me this error: 

*The Python module "subvertpy" is not installed. You may need to restart 
the server after installing it.*

Any ideas on how to troubleshoot?

Thanks
Chris

-- 
Supercharge your Review Board with Power Pack: 
https://www.reviewboard.org/powerpack/
Want us to host Review Board for you? Check out RBCommons: 
https://rbcommons.com/
Happy user? Let us know! https://www.reviewboard.org/users/
--- 
You received this message because you are subscribed to the Google Groups 
"Review Board Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/reviewboard/13c0d007-121a-4dda-8f52-87a97508f573n%40googlegroups.com.


LOAN SCHEME

2023-10-23 Thread jc

Greetings:

I am Mr. Faheem Badawi, working as a project facilitator for (Kafur 
Project Management Services) also, with numerous investors worldwide. As 
a means of widening our global portfolio we would like to know if you 
have any project(s) requiring funding. We also offer business, personal 
and home loans to finance new projects as well as expansion capital.


For more updates on the mode of operation send a reply.

Waiting for your prompt response.

Kind regards,
Faheem Badawi.
(Financial Advisory - KPMS)
___
devel mailing list
de...@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel


Info.plist for Java machines

2023-10-19 Thread jc@tlo
I'm looking for the Apple reference about which keys and values can be used in 
the Info.plist file of a bundled Java app.

Any idea where I can find that?

-- 
Jean-Christophe Helary @jchel...@emacs.ch
https://traductaire-libre.org
https://mac4translators.blogspot.com
https://sr.ht/~brandelune/omegat-as-a-book/

___
MacOSX-talk mailing list
MacOSX-talk@omnigroup.com
https://www.omnigroup.com/mailman/listinfo/macosx-talk


[Gvsig_usuarios] problemas con versión 2.3

2023-09-14 Thread JC Zt
Hola
Soy un antiguo usuario de GvSig que intenta retomar la práctica con el
programa. Me acabo de instalar la versión 2.3 y me da un par de problemas:
No funcionan las teclas de zoom (siempre acerca, independientemente de cual
toques) y no me aparece la ventana TOC.  Imagino que habré hecho algo mal
en la instalación.
Gracias
___
gvSIG_usuarios mailing list
gvSIG_usuarios@listserv.gva.es

Para ver histórico de mensajes, editar sus preferencias de usuario o darse de 
baja en esta lista, acuda a la siguiente dirección:

https://listserv.gva.es/mailman/listinfo/gvsig_usuarios


Re: Declined: SPDX Legal call @ Every 2 weeks from 7pm to 8pm on Thursday (CET) (James C. Roberts III)

2023-08-22 Thread JC Roberts III
PLEASE NOTE: this invitation is in error.  Apparently, our IT person was
upgrading/updating various apps.  As far as I understand, it appears that
my acceptance years back of the invitation to join the group was through
some software that was no longer compatible, which was actually blocking
invitations from appearing across devices.

I do not know who the organizer for these events is these days, but if you
know, then please send me the email address so I can stop this craziness
that I seemed to have started.

One again, I apologize.


GlobalCapital  |  *Innovate.**  Disrupt.*  *Repeat.*  |  James C. Roberts
 III

For downloadable documents go to globalcaplaw.com/resources

EU:  +39.366.431.1090  |  US:   +1 (415) 937-7987  |  Skype:
 globalcapjames  |  LinkedIn:   Global Capital

The contents of this email may be confidential or proprietary and
not intended for you.  If that is the case, first, we apologize for
the inconvenience caused by our error.  Second, please keep the
email’s content confidential and do not use it, then return the email
to the sender as soon as possible and delete your copy.  Please also
note that this email does not contain any explicit or implicit tax advice
for any jurisdiction.


On Tue, Aug 22, 2023 at 5:36 PM spdx-legal@lists.spdx.org (Google Calendar)
 wrote:

> SPDX Legal call
>
>
> spdx-legal@lists.spdx.org has declined this invitation.
>
> Join the call: https://www.uberconference.com/spdxteam
> 
> Optional dial in number: 857-216-2871
> PIN: 38633
> WhenEvery 2 weeks from 7pm to 8pm on Thursday (Central European Time -
> Zurich)
> Guests
> James C. Roberts III  - organizer
> James C. Roberts III 
> Jilayne Lovejoy 
> SPDX-legal 
> View all guest info
> 
>
> Invitation from Google Calendar 
>
> You are receiving this email because you are subscribed to calendar
> notifications. To stop receiving these emails, go to Calendar settings
> , select this calendar,
> and change "Other notifications".
>
> Forwarding this invitation could allow any recipient to send a response to
> the organizer, be added to the guest list, invite others regardless of
> their own invitation status, or modify your RSVP. Learn more
> 
>


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#3446): https://lists.spdx.org/g/Spdx-legal/message/3446
Mute This Topic: https://lists.spdx.org/mt/100900349/21656
Group Owner: spdx-legal+ow...@lists.spdx.org
Unsubscribe: https://lists.spdx.org/g/Spdx-legal/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-




Invitation: SPDX Legal call @ Every 2 weeks from 7pm to 8pm on Thursday (CET) (spdx-legal@lists.spdx.org)

2023-08-22 Thread JC Roberts III
BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:REQUEST
BEGIN:VTIMEZONE
TZID:America/Denver
X-LIC-LOCATION:America/Denver
BEGIN:DAYLIGHT
TZOFFSETFROM:-0700
TZOFFSETTO:-0600
TZNAME:MDT
DTSTART:19700308T02
RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=2SU
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:-0600
TZOFFSETTO:-0700
TZNAME:MST
DTSTART:19701101T02
RRULE:FREQ=YEARLY;BYMONTH=11;BYDAY=1SU
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
DTSTART;TZID=America/Denver:20160107T11
DTEND;TZID=America/Denver:20160107T12
EXDATE;TZID=America/Denver:20160331T11
EXDATE;TZID=America/Denver:20230209T11
EXDATE;TZID=America/Denver:20230223T11
RRULE:FREQ=WEEKLY;WKST=SU;INTERVAL=2;BYDAY=TH
DTSTAMP:20230822T153221Z
ORGANIZER;CN=James C. Roberts III:mailto:j...@globalcaplaw.com
UID:D5CEA1C3-B11B-4A02-BC56-664A456699BE
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;RSVP=TRUE
 ;CN=James C. Roberts III;X-NUM-GUESTS=0:mailto:j...@globalcaplaw.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=DECLINED;RSVP=TRUE
 ;CN=James C. Roberts III;X-NUM-GUESTS=0:mailto:jcr...@globalcaplaw.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;RSVP=TRUE
 ;CN=Jilayne Lovejoy;X-NUM-GUESTS=0:mailto:lovejoyl...@gmail.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;RSVP=TRUE
 ;CN=SPDX-legal;X-NUM-GUESTS=0:mailto:spdx-legal@lists.spdx.org
X-MICROSOFT-CDO-OWNERAPPTID:-39726701
CREATED:20230822T153215Z
DESCRIPTION:Join the call: https://www.uberconference.com/spdxteam\nOptiona
 l dial in number: 857-216-2871\nPIN: 38633
LAST-MODIFIED:20230822T153215Z
LOCATION:
SEQUENCE:0
STATUS:CONFIRMED
SUMMARY:SPDX Legal call
TRANSP:TRANSPARENT
BEGIN:VALARM
ACTION:NONE
TRIGGER;VALUE=DATE-TIME:19760401T005545Z
END:VALARM
END:VEVENT
END:VCALENDAR


invite.ics
Description: application/ics


Re: [sage-devel] Re: Question about cysignals installation

2023-08-16 Thread JC
Thanks for your replies! So is there a way to let cysignals use an older 
version of Cython?

On Wednesday, August 16, 2023 at 12:36:49 PM UTC-4 Dima Pasechnik wrote:

> this seems to be the CI  error, something with setuptools version
>
> 2023-08-04T14:47:05.9834230Z config.status: creating src/config.h
> 2023-08-04T14:47:06.0117040Z config.status: creating 
> src/cysignals/cysignals_config.h
> 2023-08-04T14:47:06.0928570Z python3 -m pip -v install --no-index 
> --ignore-installed --no-deps .
> 2023-08-04T14:47:06.5479190Z Using pip 23.2.1 from 
> /Users/runner/hostedtoolcache/Python/3.10.12/x64/lib/python3.10/site-packages/pip
>  
> (python 3.10)
> 2023-08-04T14:47:06.7102480Z Processing 
> /Users/runner/work/cysignals/cysignals
> 2023-08-04T14:47:06.7169520Z Running command pip subprocess to install 
> build dependencies
> 2023-08-04T14:47:06.7169990Z Installing build dependencies: started
> 2023-08-04T14:47:07.3324070Z ERROR: Could not find a version that 
> satisfies the requirement setuptools>=40.8.0 (from versions: none)
> 2023-08-04T14:47:07.3326280Z ERROR: No matching distribution found for 
> setuptools>=40.8.0
> 2023-08-04T14:47:07.4154720Z error: subprocess-exited-with-error
> 2023-08-04T14:47:07.4155590Z   
> 2023-08-04T14:47:07.4156570Z × pip subprocess to install build 
> dependencies did not run successfully.
> 2023-08-04T14:47:07.4157390Z │ exit code: 1
>
>
> On Wed, 16 Aug 2023, 16:20 'Martin R. Albrecht' via sage-devel, <
> sage-...@googlegroups.com> wrote:
>
>> FWIW this PR https://github.com/sagemath/cysignals/pull/174 does this 
>> porting, I think.
>>
>> CI complaints but I don’t understand the complaint.
>>
>> On Wed, Aug 16 2023, Dima Pasechnik wrote:
>> > I think your cython is too new (3.0.0).
>> >
>> > Cysignals has not been ported to it yet.
>> >
>> > On Wednesday, August 16, 2023 at 4:00:24 PM UTC+1 JC wrote:
>> >
>> >> Dear Sage developers,
>> >>
>> >> I'm trying to install the cysignals 1.11.2 package in Python 3.9.7 
>> using 
>> >> pip (on a computer with macOS system and Apple M2 chip) and have 
>> already 
>> >> installed the prerequisite packages Cython and Sphinx, but still 
>> failed 
>> >> with some Cython compiling errors (please see the error message 
>> attached). 
>> >> Do you know what the problem might be and how I can fix it?
>> >>
>> >> Thank you very much!
>> >>
>>
>>
>> -- 
>>
>> _pgp: https://keybase.io/martinralbrecht
>> _www: https://malb.io
>> _prn: he/him or they/them
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "sage-devel" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to sage-devel+...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/sage-devel/87jztvui7p.fsf%40googlemail.com
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/4545fa4a-35b1-4e5c-8e5b-fe14709889fan%40googlegroups.com.


[sage-devel] Question about cysignals installation

2023-08-16 Thread JC
Dear Sage developers,

I'm trying to install the cysignals 1.11.2 package in Python 3.9.7 using 
pip (on a computer with macOS system and Apple M2 chip) and have already 
installed the prerequisite packages Cython and Sphinx, but still failed 
with some Cython compiling errors (please see the error message attached). 
Do you know what the problem might be and how I can fix it?

Thank you very much!

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/a24a536d-02ef-42a2-acb0-ccdffbd88f69n%40googlegroups.com.


cysignals_output
Description: Binary data


[sage-support] Question about cysignals installation

2023-08-16 Thread JC
Dear Sage developers,

I'm trying to install the cysignals 1.11.2 package in Python 3.9.7 using 
pip (on a computer with macOS system and Apple M2 chip) and have already 
installed the prerequisite packages Cython and Sphinx, but still failed 
with some Cython compiling errors (please see the error message attached). 
Do you know what the problem might be and how I can fix it?

Thank you very much!

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/efb78184-51f5-4ac3-aeca-7601b9f84191n%40googlegroups.com.


cysignals_output
Description: Binary data


Re: [chrono] Terrain Mesh + Static Objects

2023-08-10 Thread 'JC Denton' via ProjectChrono
Hi Marcel,

Thanks again for your insight.

I know about the functor to run raycasts on my terrain, and I was planning 
to use that for my traditional terrain mesh. I can't call into Unreal's 
terrain data 
with that function since there is no thread safe method of doing so that I 
know of, however I can copy that mesh into the Chrono side so it can query 
it whenever it needs.

My concern lies more with the non terrain type meshes that are still 
drivable, but seperate meshes. I have long spline type pathways, rocks, 
rubble and other debris that can also be driven upon.

These separate meshes have simplified primitive and convex colliders.

I have begun the process of extracting all collision shapes from unreal and 
making static versions of them on the Chrono Bullet side, but not sure how 
nicely Chrono's tire models will interact when driving over those non 
terrain objects, or 
perhaps it ignores them entirely. I have to make a distinction between 
drivable mesh and a terrain type mesh. But I will for sure have to do some 
work in that height/normal query to determine what its driving over, and 
may need to trace against 
my static meshes also, which could start getting expensive without 
optimizations. 

Guess we will see what happens!

Will report back

On Thursday, August 10, 2023 at 1:40:55 AM UTC-7 marcel.o...@gmail.com 
wrote:

> Hello JC,
>
> On 07-Aug-23 17:47, 'JC Denton' via ProjectChrono wrote:
> > I have my simulation running in unreal, where I have a terrain mesh 
> > that I can export as a mesh or heightmap. But I also have numerous 
> > static meshes that the vehicle can  drive on also such as extended 
> > dirt pathways, large flat rocks etc.
> Understood.
> > I can't call from Chrono-> into Unreal to ray cast these objects in 
> > this case and let Unreal do the height queries, since there isn't a 
> > synchronous method of doing so.
> You are aware that there is an option to provide a way to provide a 
> "functor" object for doing such raycasts in your custom terrain to 
> calculate the height, normal and friction at any point? See 
>
> https://api.projectchrono.org/development/classchrono_1_1vehicle_1_1_ch_terrain.html#a8e3e66a8f15858149786fe234dda23bd
>  
> for the methods to register such functors. If you have terrain that 
> needs to be used differently (I'm not that familiar with the terrain 
> code in Unreal) then this is a hook you might be able to leverage. Or 
> did you try this and is something else blocking you from making this work?
> > How best to add these to the simulation? Should I treat them as static 
> > bullet colliders and add them that way, or should I be converting each 
> > of these pathways into a terrain patch of their own? Is there a 
> > realistic limit on how many terrain patches I can add?
> > The overall poly count of all my meshes is quite high so I would like 
> > to anticipate any performance issues ahead of time.
>
> In general I would say that if you just provide a huge mesh (or multiple 
> smaller ones) the speed of the default implementation is likely to 
> become an issue (it was in my case, which is why I ended up using the 
> functors I mentioned above).
>
> Hope this helps (a bit).
>
> Greetings, Marcel
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"ProjectChrono" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to projectchrono+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/projectchrono/7a4a6201-fb38-4330-a206-38e9d79bf8fbn%40googlegroups.com.


[chrono] Terrain Mesh + Static Objects

2023-08-07 Thread 'JC Denton' via ProjectChrono
Hello!

I have my simulation running in unreal, where I have a terrain mesh that I 
can export as a mesh or heightmap. But I also have numerous static meshes 
that the vehicle can  drive on also such as extended dirt pathways, large 
flat rocks etc.

I can't call from Chrono-> into Unreal to ray cast these objects in this 
case and let Unreal do the height queries, since there isn't a synchronous 
method of doing so. 

How best to add these to the simulation? Should I treat them as static 
bullet colliders and add them that way, or should I be converting each of 
these pathways into a terrain patch of their own? Is there a realistic 
limit on how many terrain patches I can add? 
The overall poly count of all my meshes is quite high so I would like to 
anticipate any performance issues ahead of time. 

Thanks!
-JC

-- 
You received this message because you are subscribed to the Google Groups 
"ProjectChrono" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to projectchrono+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/projectchrono/e6d7230e-69b3-434f-989b-1459662bd01dn%40googlegroups.com.


Re: [chrono] How to visualize tires, wheels etc?

2023-08-03 Thread 'JC Denton' via ProjectChrono
Hi Marcel,

I do not have a caching system yet, that would be a smart move! 
Currently the Unreal side is drawing these debug meshes once per game 
thread tick (when debugging is enabled), so its not like its once per 
chrono step. 
This debug drawing is purely for debug purpose and wouldn't be visible to 
the end user. Still though, its a good idea, might as well not waste time 
looping
over all the verts if the mesh hasn't actually moved. 


Thanks!
-JC
On Thursday, August 3, 2023 at 1:10:40 AM UTC-7 marcel.o...@gmail.com wrote:

> Great to hear, JC!
>
> Transformation of coordinate systems is something we all have to live with 
> when converting from 3D modeling tools and physics engines to game engines.
>
> One question I have, when you transfer "low level mesh data" from Chrono 
> to Unreal, do you also have a method of caching that so you can send it to 
> the GPU once (and not every frame)?
>
> In any case, it's nice to hear your project is coming along nicely, good 
> luck with it!
>
> Greetings, Marcel
>
>
> On 03-Aug-23 7:06, 'JC Denton' via ProjectChrono wrote:
>
> Thanks Marcel!
>
> I do indeed have my physics thread separate from my render thread. I have 
> a queued callback system to send render debug info from 
> my chrono dll to the unreal side in a thread safe manner. 
>
> I rolled my own debug helper class to manually loop through the vertices 
> from ChCylinder and ChTriangleMeshes and 
> push those into vert structures that Unreal can read. Seems to be 
> rendering the meshes in unreal okay, just gotta work out some transform 
> conversions now
> and expand it to other chrono shape types.
>
> I just pulled the vert data directly from the m_trimesh_shape which exists 
> inside ChWheel already.
> So now I have my Unreal visual meshes driven from the Chrono physics 
> output + the chrono collision debug shapes rendering overlayed on top for 
> comparison which is exactly
> what I was looking for. 
>
> Thanks!
>
> -JC
>
> On Wednesday, August 2, 2023 at 12:11:41 AM UTC-7 marcel.o...@gmail.com 
> wrote:
>
>> Hello JC, 
>>
>> Responses in-line below. 
>>
>> On 02-Aug-23 5:27, 'JC Denton' via ProjectChrono wrote: 
>> > I do indeed visualize my wheels and chassis no problem in Unreal 
>> > engine, however my visual mesh in Unreal is not the same as the 
>> > collision meshes in Chrono. I would like to draw the scene as Chrono 
>> > sees it, 
>> > to ensure it aligns 1:1 with what Unreal sees. 
>>
>> Understood, and this of course is a generic "issue". Collision meshes 
>> are always simplified meshes to keep a decent performance and the visual 
>> mesh (regardless of Unreal, Irrlicht or VSG rendering it) will be 
>> different. I typically use a mental model where I distinguish three 
>> worlds: 
>>
>> 1. The visual one, that is normally rendered. 
>>
>> 2. The collision world, that has all kinds of collidable (simple) shapes 
>> bumping into each other (car bodies bumping into terrain or other cars). 
>>
>> 3. The tire world, that typically uses its own type of collision system 
>> (although that depends a bit on the type of tire, I mostly use 
>> semi-empirical ones for my use case. 
>>
>> > Hoping there is a way (ideally without modifying Chrono engine code) 
>> > to visualize the contact points, tire, wheel etc. 
>>
>> I've gone through a similar process and with the help of this community 
>> and a few small patches I have mostly managed to get to the data I want 
>> to visualize without having to change the engine. I did end up doing a 
>> lot of the drawing "myself". There is a lot of information available at 
>> the end of every physics "step" so the biggest deal then becomes how to 
>> pass all that data to (in your case) Unreal. Part of that design is also 
>> about potentially decoupling the physics thread from your rendering (at 
>> least in my case I quickly concluded that with physics running at 1000 
>> fps my graphics card was never going to keep up). 
>>
>> > I notice inside ChWheel::AddVisualizationAssets() we have some logic 
>> > to setup triangle meshes: 
>> > 
>> > void ChWheel::AddVisualizationAssets(VisualizationType vis) 
>> > { 
>> > if (vis == VisualizationType::MESH && !m_vis_mesh_file.empty()) { 
>> > ChQuaternion<> rot = (m_side == VehicleSide::LEFT) ? 
>> > Q_from_AngZ(0) : Q_from_AngZ(CH_C_PI); 
>> > auto trimesh = 
>> > 
>> geometry::ChTriangleMeshConnected::CreateFromWavefrontFile(vehicle::GetDa

Re: [chrono] How to visualize tires, wheels etc?

2023-08-02 Thread 'JC Denton' via ProjectChrono
Thanks Marcel!

I do indeed have my physics thread separate from my render thread. I have a 
queued callback system to send render debug info from 
my chrono dll to the unreal side in a thread safe manner. 

I rolled my own debug helper class to manually loop through the vertices 
from ChCylinder and ChTriangleMeshes and 
push those into vert structures that Unreal can read. Seems to be rendering 
the meshes in unreal okay, just gotta work out some transform conversions 
now
and expand it to other chrono shape types.

I just pulled the vert data directly from the m_trimesh_shape which exists 
inside ChWheel already.
So now I have my Unreal visual meshes driven from the Chrono physics output 
+ the chrono collision debug shapes rendering overlayed on top for 
comparison which is exactly
what I was looking for. 

Thanks!

-JC

On Wednesday, August 2, 2023 at 12:11:41 AM UTC-7 marcel.o...@gmail.com 
wrote:

> Hello JC,
>
> Responses in-line below.
>
> On 02-Aug-23 5:27, 'JC Denton' via ProjectChrono wrote:
> > I do indeed visualize my wheels and chassis no problem in Unreal 
> > engine, however my visual mesh in Unreal is not the same as the 
> > collision meshes in Chrono. I would like to draw the scene as Chrono 
> > sees it,
> > to ensure it aligns 1:1 with what Unreal sees.
>
> Understood, and this of course is a generic "issue". Collision meshes 
> are always simplified meshes to keep a decent performance and the visual 
> mesh (regardless of Unreal, Irrlicht or VSG rendering it) will be 
> different. I typically use a mental model where I distinguish three worlds:
>
> 1. The visual one, that is normally rendered.
>
> 2. The collision world, that has all kinds of collidable (simple) shapes 
> bumping into each other (car bodies bumping into terrain or other cars).
>
> 3. The tire world, that typically uses its own type of collision system 
> (although that depends a bit on the type of tire, I mostly use 
> semi-empirical ones for my use case.
>
> > Hoping there is a way (ideally without modifying Chrono engine code) 
> > to visualize the contact points, tire, wheel etc.
>
> I've gone through a similar process and with the help of this community 
> and a few small patches I have mostly managed to get to the data I want 
> to visualize without having to change the engine. I did end up doing a 
> lot of the drawing "myself". There is a lot of information available at 
> the end of every physics "step" so the biggest deal then becomes how to 
> pass all that data to (in your case) Unreal. Part of that design is also 
> about potentially decoupling the physics thread from your rendering (at 
> least in my case I quickly concluded that with physics running at 1000 
> fps my graphics card was never going to keep up).
>
> > I notice inside ChWheel::AddVisualizationAssets() we have some logic 
> > to setup triangle meshes:
> >
> > void ChWheel::AddVisualizationAssets(VisualizationType vis)
> > {
> > if (vis == VisualizationType::MESH && !m_vis_mesh_file.empty()) {
> > ChQuaternion<> rot = (m_side == VehicleSide::LEFT) ? 
> > Q_from_AngZ(0) : Q_from_AngZ(CH_C_PI);
> > auto trimesh = 
> > 
> geometry::ChTriangleMeshConnected::CreateFromWavefrontFile(vehicle::GetDataFile(m_vis_mesh_file),
> >   true, true);
> > m_trimesh_shape = 
> > chrono_types::make_shared();
> > m_trimesh_shape->SetMesh(trimesh);
> > m_trimesh_shape->SetName(filesystem::path(m_vis_mesh_file).stem());
> > m_trimesh_shape->SetMutable(false);
> > m_spindle->AddVisualShape(m_trimesh_shape, 
> > ChFrame<>(ChVector<>(0, m_offset, 0), ChMatrix33<>(rot)));
> > return;
> > }
> > }
> >
> > Is there an easy general way to draw arbitrary chrono shapes such as 
> > ChTriangleMeshConnected or ChCylinderShape? Or do I need to roll my 
> > own function to iterate over each chrono shape's verts and then render 
> > them on my Unreal side?
>
> I don't think there is. For "primitive" shapes I ended up implementing 
> them myself based on the provided parameters and I mostly use those to 
> visualize how the vehicle physics respond. For "mesh" shapes I ended up 
> completely ignoring what is defined in Chrono and loading my own 3D 
> model, using a bit of glue code to make the right parts of that model 
> show up in the places calculated by Chrono (position and orientation). 
> You could also take the defined OBJ meshes and load those in Unreal I 
> guess. OBJ is nice because it's a simple format to generate and parse. 
> That said, I ended up wanting to have the whole 

Re: [chrono] How to visualize tires, wheels etc?

2023-08-01 Thread 'JC Denton' via ProjectChrono
Thanks Marcel!

I do indeed visualize my wheels and chassis no problem in Unreal engine, 
however my visual mesh in Unreal is not the same as the collision meshes in 
Chrono. I would like to draw the scene as Chrono sees it,
to ensure it aligns 1:1 with what Unreal sees. 

Hoping there is a way (ideally without modifying Chrono engine code) to 
visualize the contact points, tire, wheel etc. 

I notice inside ChWheel::AddVisualizationAssets() we have some logic to 
setup triangle meshes:

void ChWheel::AddVisualizationAssets(VisualizationType vis) 
{
if (vis == VisualizationType::MESH && !m_vis_mesh_file.empty()) {
ChQuaternion<> rot = (m_side == VehicleSide::LEFT) ? Q_from_AngZ(0) 
: Q_from_AngZ(CH_C_PI);
auto trimesh = 
geometry::ChTriangleMeshConnected::CreateFromWavefrontFile(vehicle::GetDataFile(m_vis_mesh_file),

  true, true);
m_trimesh_shape = chrono_types::make_shared();
m_trimesh_shape->SetMesh(trimesh);
m_trimesh_shape->SetName(filesystem::path(m_vis_mesh_file).stem());
m_trimesh_shape->SetMutable(false);
m_spindle->AddVisualShape(m_trimesh_shape, ChFrame<>(ChVector<>(0, 
m_offset, 0), ChMatrix33<>(rot)));
return;
}
}

Is there an easy general way to draw arbitrary chrono shapes such as 
ChTriangleMeshConnected or ChCylinderShape? Or do I need to roll my own 
function to iterate over each chrono shape's verts and then render them on 
my Unreal side? 

Thanks!

On Tuesday, August 1, 2023 at 12:18:45 AM UTC-7 marcel.o...@gmail.com wrote:

> Hello JC,
>
> On 01-Aug-23 5:10, 'JC Denton' via ProjectChrono wrote:
> > I'm using my own engine, and I have a callback system setup to draw 
> > like so:
> >
> > m_system->GetCollisionSystem()->Visualize(ChCollisionSystem::VIS_Shapes 
> > | ChCollisionSystem::VIS_Aabb);
> >
> > This works fine for my chassis.
> I learned something new, you are registering a callback to draw a 
> visualization of the collision shapes and using those callbacks to 
> render something in your engine. That's nice. As far as I'm aware, a 
> similar hook does not exist for rendering visualizations in general...
> > But for my wheels and tires it doesn't.
> >
> > My wheel set's its visual mesh file via:
> >
> >   m_vis_mesh_file = "Meshes/Collision/LeftWheel.obj";
> >
> > and my tire's visualize mesh via:
> >
> > void 
> > RangeRoverSport_TMeasyTire::AddVisualizationAssets(VisualizationType vis)
> > {
> > if (vis == VisualizationType::MESH)
> > {
> > m_trimesh_shape = AddVisualizationMesh(m_meshFile_left, 
> > m_meshFile_right);
> > }
> > else
> > {
> > ChTMeasyTire::AddVisualizationAssets(vis);
> > }
> > }
> >
> > but perhaps this is only meant for visualizing with irrlicht and 
> > doesn't support drawing out to my own engine?
>
> I'm pretty sure that assumption is correct. Irrlicht and Vulkan Scene 
> Graph (VSG) both basically iterate over the whole system and will grab 
> those assets and render them. The good news is, you can do something 
> similar yourself. I have done something similar to render terrain and 
> vehicles for my own simulator.
>
> Greetings, Marcel
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"ProjectChrono" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to projectchrono+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/projectchrono/4904cf25-506b-4840-a5e6-abacddc1f1ean%40googlegroups.com.


[chrono] How to visualize tires, wheels etc?

2023-07-31 Thread 'JC Denton' via ProjectChrono
I'm using my own engine, and I have a callback system setup to draw like so:

m_system->GetCollisionSystem()->Visualize(ChCollisionSystem::VIS_Shapes | 
ChCollisionSystem::VIS_Aabb);

This works fine for my chassis. 

But for my wheels and tires it doesn't. 

My wheel set's its visual mesh file via:

  m_vis_mesh_file = "Meshes/Collision/LeftWheel.obj";

and my tire's visualize mesh via:

void RangeRoverSport_TMeasyTire::AddVisualizationAssets(VisualizationType 
vis) 
{
if (vis == VisualizationType::MESH) 
{  
m_trimesh_shape = AddVisualizationMesh(m_meshFile_left, 
m_meshFile_right);
}
else 
{
ChTMeasyTire::AddVisualizationAssets(vis);
}
}

but perhaps this is only meant for visualizing with irrlicht and doesn't 
support drawing out to my own engine?

Thanks!
-JC


-- 
You received this message because you are subscribed to the Google Groups 
"ProjectChrono" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to projectchrono+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/projectchrono/a3a0f0fe-479e-4575-9f9d-3ee84fbf21a9n%40googlegroups.com.


[kwin] [Bug 438883] Re-implement Desktop Cube effect with modern effects API

2023-07-25 Thread JC Casiano
https://bugs.kde.org/show_bug.cgi?id=438883

--- Comment #73 from JC Casiano  ---
Agreed, this and the burning-windows feature are great distiguishing
effects, and should be re-integrated since they are working again.

> https://bugs.kde.org/show_bug.cgi?id=438883
>
> --- Comment #72 from Dalix  ---
> (In reply to JC Casiano from comment #71)
>> There is a package available in AUR (there are actually 2, but this one
>> is
>> for Plasma5):  https://aur.archlinux.org/packages/kwin-effects-cube
>>
>> I easily built and installed it, and have been using it for many weeks
>> now.
>> I'm very appreciative of "zjuyk" for giving us something to work with.
>> This
>> version gives the basic zoom out and screen flipping, as well as
>> allowing
>> for the 3-D rotation/view.  I think the only thing it didn't like about
>> my
>> setup was the second touchscreen monitor, but otherwise it seems to do
>> what
>> the Cube used to do.
>>
>> It did fail after one upgrade, but after recompiling and reinstalling
>> it, I
>> got it to work again.
>
> This is good to know but I am still really hoping for it to be properly
> re-integrated into Plasma!
>
> --
> You are receiving this mail because:
> You are on the CC list for the bug.
> You voted for the bug.

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

[kwin] [Bug 438883] Re-implement Desktop Cube effect with modern effects API

2023-07-17 Thread JC Casiano
https://bugs.kde.org/show_bug.cgi?id=438883

--- Comment #71 from JC Casiano  ---
There is a package available in AUR (there are actually 2, but this one is for
Plasma5):  https://aur.archlinux.org/packages/kwin-effects-cube

I easily built and installed it, and have been using it for many weeks now. 
I'm very appreciative of "zjuyk" for giving us something to work with.  This
version gives the basic zoom out and screen flipping, as well as allowing for
the 3-D rotation/view.  I think the only thing it didn't like about my setup
was the second touchscreen monitor, but otherwise it seems to do what the Cube
used to do.  

It did fail after one upgrade, but after recompiling and reinstalling it, I got
it to work again.

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

Bug#1037560: lxpanel: Icons of the launchbar plugin are not properly displayed

2023-06-14 Thread JC
Package: lxpanel
Version: 0.10.1-2+rpt19
Severity: minor

Dear Maintainer,

I have a pi400 and upgraded it to debian 12. I configured a new panel
since the one I had was clumsy, with the classical : menu then
launcher then taskbar then several system icons

The icons of the launcher are too large compared to the button size so
they are cut at the top and not well centered

I suspect a margin/padding problem (I do not know gtk, just judging
from my CSS, SwiftUI and swing knowledge), I do not know if it is
linked to the raspberry pi. I deleted all files from the original
installation in /etc/xdg/lxpanel and only have the default files. I
also deleted previous .config/lxpanel to have it created by
configuration dialog.

-- System Information:
Debian Release: 12.0
  APT prefers stable-security
  APT policy: (500, 'stable-security'), (500, 'stable')
Architecture: arm64 (aarch64)
Foreign Architectures: armhf

Kernel: Linux 6.1.21-v8+ (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_CRAP
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to fr_FR.UTF-8), LANGUAGE=fr_FR.UTF-8
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages lxpanel depends on:
ii  libasound2   1.2.8-1+b1
ii  libc62.36-9
ii  libcairo21.16.0-7
ii  libcurl3-gnutls  7.88.1-10
ii  libfm-gtk4   1.3.2-1+rpt3
ii  libfm-modules1.3.2-1+rpt3
ii  libfm4   1.3.2-1+rpt3
ii  libgdk-pixbuf-2.0-0  2.42.10+dfsg-1+b1
ii  libglib2.0-0 2.74.6-2
ii  libgtk-3-0   3.24.37-2
ii  libiw30  30~pre9-14
ii  libkeybinder-3.0-0   0.3.2-1.1
ii  libmenu-cache3   1.1.0-1.1
ii  libpango-1.0-0   1.50.12+ds-1
ii  libwnck-3-0  43.0-3
ii  libx11-6 2:1.8.4-2
ii  libxml2  2.9.14+dfsg-1.2
ii  lxmenu-data  0.1.5-2.1
ii  lxpanel-data 0.10.1-2+rpt19

Versions of packages lxpanel recommends:
pn  libnotify-bin 
ii  lxterminal [x-terminal-emulator]  0.4.0-2
pn  notification-daemon   
pn  pavucontrol | gnome-alsamixer 
ii  xkb-data  2.35.1-1

Versions of packages lxpanel suggests:
ii  chromium-browser [www-browser]  113.0.5672.95-rpt1
ii  dillo [www-browser] 3.0.5-7+rpt1
ii  firefox-esr [www-browser]   102.12.0esr-1~deb12u1
ii  lynx [www-browser]  2.9.0dev.12-1
pn  menu

-- Configuration Files:
/etc/xdg/lxpanel/default/config [Errno 2] Aucun fichier ou dossier de ce type: 
'/etc/xdg/lxpanel/default/config'
/etc/xdg/lxpanel/default/panels/panel [Errno 2] Aucun fichier ou dossier de ce 
type: '/etc/xdg/lxpanel/default/panels/panel'
/etc/xdg/lxpanel/two_panels/config [Errno 2] Aucun fichier ou dossier de ce 
type: '/etc/xdg/lxpanel/two_panels/config'
/etc/xdg/lxpanel/two_panels/panels/bottom [Errno 2] Aucun fichier ou dossier de 
ce type: '/etc/xdg/lxpanel/two_panels/panels/bottom'
/etc/xdg/lxpanel/two_panels/panels/top [Errno 2] Aucun fichier ou dossier de ce 
type: '/etc/xdg/lxpanel/two_panels/panels/top'

-- no debconf information



Re: [chrono] Does Chrono Vehicle have the concept of a handbrake/ emergency brake?

2023-06-01 Thread 'JC Denton' via ProjectChrono
Excellent! thanks for your help

-JC

On Monday, May 29, 2023 at 11:04:09 AM UTC-7 Radu Serban wrote:

> Looking back in the code, I realized I had already implemented a parking 
> brake (exactly along the lines I mentioned below). I just pushed a minor 
> change so that the parking brake (i.e., locking of the spindle DOF) happens 
> only for non-steerable axles. 
>
>  
>
> The function to engage/release the parking brake is 
> ChWheeledVehicle::ApplyParkingBrake() which takes a bool argument.
>
>  
>
> --Radu
>
>  
>
> *From:* 'Radu Serban' via ProjectChrono  
> *Sent:* Monday, May 29, 2023 8:20 AM
> *To:* ProjectChrono 
> *Subject:* RE: [chrono] Does Chrono Vehicle have the concept of a 
> handbrake/ emergency brake?
>
>  
>
> Well, that is true for the “standard” 4-wheel, front-steering 
> configuration. Granted, the most common topology. For Chrono::Vehicle, 
> where one can model all sorts of configurations, implementing an 
> emergency/parking brake would also require user input for which axles that 
> would be applied.  I’ll consider adding that.
>
>  
>
> For now, you want to implement this outside the Chrono::Vehicle library 
> (i.e., in user code). Look at the implementation of ChBrakeSimple 
> <https://github.com/projectchrono/chrono/blob/main/src/chrono_vehicle/wheeled_vehicle/brake/ChBrakeSimple.cpp>
>  
> which uses this locking of the spindle joints to overcome a limitation of 
> this simplistic brake model (no braking torque applied when the wheel has 
> zero relative angular velocity). You can get the appropriate revolute joint 
> from the ChSuspension object and then can call the Lock(true) function on 
> that joint.
>
>  
>
> By the way, if you are using a ChBrakeSimple in your model, I suggest you 
> change that to a ChBrakeShafts which does not require the hack I mentioned 
> above.
>
>  
>
> --Radu
>
>  
>
> *From:* 'JC Denton' via ProjectChrono  
> *Sent:* Monday, May 29, 2023 3:31 AM
> *To:* ProjectChrono 
> *Subject:* Re: [chrono] Does Chrono Vehicle have the concept of a 
> handbrake/ emergency brake?
>
>  
>
> Thanks for the info!
> Is there an easy way to lock the spindles on/off?
>
> As you know the brake is applied to all wheels, but on most cars the 
> handbrake is only applied to the rear wheels. So just wondering if there 
> was already something implemented for a handbrake. Alternatively I can 
> figure out how to lock the rotation of the rear spindles 
>
> On Friday, May 26, 2023 at 12:51:25 AM UTC-7 Radu Serban wrote:
>
> There is no model of an emergency brake in Chrono::Vehicle. A simple way 
> of adding that would be by providing a function that would lock the wheel 
> spindles (i.e., remove their rotation degrees of freedom).
>
>  
>
> What scenario are you trying to model? In other words, why isn’t it enough 
> to just apply maximum brake input (+1)?
>
>  
>
> --Radu
>
>  
>
> *From:* 'JC Denton' via ProjectChrono  
> *Sent:* Friday, May 26, 2023 5:51 AM
> *To:* ProjectChrono 
> *Subject:* [chrono] Does Chrono Vehicle have the concept of a handbrake/ 
> emergency brake?
>
>  
>
> And if so, where to find it, or is there another approach you suggest to 
> apply it?
>
> Thanks!
>
> -- 
> You received this message because you are subscribed to the Google Groups 
> "ProjectChrono" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to projectchron...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/projectchrono/a69c4b93-61a5-47d9-8f0b-10b476c2529fn%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/projectchrono/a69c4b93-61a5-47d9-8f0b-10b476c2529fn%40googlegroups.com?utm_medium=email_source=footer>
> .
>
> -- 
> You received this message because you are subscribed to the Google Groups 
> "ProjectChrono" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to projectchron...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/projectchrono/f02cd447-1c5b-4f89-88b4-fd99ef6f56a7n%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/projectchrono/f02cd447-1c5b-4f89-88b4-fd99ef6f56a7n%40googlegroups.com?utm_medium=email_source=footer>
> .
>
> -- 
> You received this message because you are subscribed to the Google Groups 
> "ProjectChrono" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to projectchron...@googlegroups.com.
>
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/proj

Re: [chrono] Does Chrono Vehicle have the concept of a handbrake/ emergency brake?

2023-05-28 Thread 'JC Denton' via ProjectChrono
Thanks for the info!
Is there an easy way to lock the spindles on/off?

As you know the brake is applied to all wheels, but on most cars the 
handbrake is only applied to the rear wheels. So just wondering if there 
was already something implemented for a handbrake. Alternatively I can 
figure out how to lock the rotation of the rear spindles 

On Friday, May 26, 2023 at 12:51:25 AM UTC-7 Radu Serban wrote:

> There is no model of an emergency brake in Chrono::Vehicle. A simple way 
> of adding that would be by providing a function that would lock the wheel 
> spindles (i.e., remove their rotation degrees of freedom).
>
>  
>
> What scenario are you trying to model? In other words, why isn’t it enough 
> to just apply maximum brake input (+1)?
>
>  
>
> --Radu
>
>  
>
> *From:* 'JC Denton' via ProjectChrono  
> *Sent:* Friday, May 26, 2023 5:51 AM
> *To:* ProjectChrono 
> *Subject:* [chrono] Does Chrono Vehicle have the concept of a handbrake/ 
> emergency brake?
>
>  
>
> And if so, where to find it, or is there another approach you suggest to 
> apply it?
>
> Thanks!
>
> -- 
> You received this message because you are subscribed to the Google Groups 
> "ProjectChrono" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to projectchron...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/projectchrono/a69c4b93-61a5-47d9-8f0b-10b476c2529fn%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/projectchrono/a69c4b93-61a5-47d9-8f0b-10b476c2529fn%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"ProjectChrono" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to projectchrono+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/projectchrono/f02cd447-1c5b-4f89-88b4-fd99ef6f56a7n%40googlegroups.com.


[chrono] Does Chrono Vehicle have the concept of a handbrake/ emergency brake?

2023-05-25 Thread 'JC Denton' via ProjectChrono
And if so, where to find it, or is there another approach you suggest to 
apply it?

Thanks!

-- 
You received this message because you are subscribed to the Google Groups 
"ProjectChrono" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to projectchrono+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/projectchrono/a69c4b93-61a5-47d9-8f0b-10b476c2529fn%40googlegroups.com.


[webkit-changes] [WebKit/WebKit] 2ecaa0: crashes in removeInvalidElement...

2023-05-24 Thread JC Alvarado
  Branch: refs/heads/main
  Home:   https://github.com/WebKit/WebKit
  Commit: 2ecaa0ec8a3a99ad250305824746deffb2217acb
  
https://github.com/WebKit/WebKit/commit/2ecaa0ec8a3a99ad250305824746deffb2217acb
  Author: Alexey Shvayka 
  Date:   2023-05-24 (Wed, 24 May 2023)

  Changed paths:
A LayoutTests/fast/forms/input-type-radio-form-gc-crash-expected.txt
A LayoutTests/fast/forms/input-type-radio-form-gc-crash.html
M Source/WebCore/html/FormAssociatedCustomElement.cpp
M Source/WebCore/html/FormAssociatedCustomElement.h
M Source/WebCore/html/ValidatedFormListedElement.cpp
M Source/WebCore/html/ValidatedFormListedElement.h

  Log Message:
  ---
   crashes in 
removeInvalidElementToAncestorFromInsertionPoint() during GC
https://bugs.webkit.org/show_bug.cgi?id=253860


Reviewed by Ryosuke Niwa.

When a  gets destroyed, it calls into formWillBeDestroyed() callback of 

which, when removing radio buttons themselves, calls into updateValidity() and 
then into
removeInvalidElementToAncestorFromInsertionPoint() with partially-deleted 
ContainerNode as an
argument, causing a crash.

This change guards removeInvalidElementToAncestorFromInsertionPoint() and its 
counterpart
from being called during form destruction.

* LayoutTests/fast/forms/input-type-radio-form-gc-crash-expected.txt: Added.
* LayoutTests/fast/forms/input-type-radio-form-gc-crash.html: Added.
* Source/WebCore/html/FormAssociatedCustomElement.cpp:
(WebCore::FormAssociatedCustomElement::didChangeForm):
(WebCore::FormAssociatedCustomElement::formWillBeDestroyed): Deleted.
* Source/WebCore/html/FormAssociatedCustomElement.h:
* Source/WebCore/html/ValidatedFormListedElement.cpp:
(WebCore::ValidatedFormListedElement::updateValidity):
(WebCore::ValidatedFormListedElement::formWillBeDestroyed):
* Source/WebCore/html/ValidatedFormListedElement.h:
(WebCore::ValidatedFormListedElement::belongsToFormThatIsBeingDestroyed const):

Originally-landed-as: 259548.534@safari-7615-branch (f5dc82736e2c). 
rdar://105086386
Canonical link: https://commits.webkit.org/264496@main


  Commit: 23ef02b6528e0113ebb5a13bb0b18eef750b7a7c
  
https://github.com/WebKit/WebKit/commit/23ef02b6528e0113ebb5a13bb0b18eef750b7a7c
  Author: JC Alvarado 
  Date:   2023-05-24 (Wed, 24 May 2023)

  Changed paths:
A LayoutTests/fast/editing/insert-text-hit-testing-crash-expected.txt
A LayoutTests/fast/editing/insert-text-hit-testing-crash.html
M Source/WebCore/dom/Document.cpp
M Source/WebCore/rendering/HitTestRequest.h

  Log Message:
  ---
  Update layout of child frames before hit testing a document if necessary
https://bugs.webkit.org/show_bug.cgi?id=253615
rdar://107375598

Reviewed by Alan Baradlay.

If hit testing can recurse into a child frame, we should make sure that
layout and style are updated for all children before proceeding with
hit testing.

* LayoutTests/fast/editing/insert-text-hit-testing-crash-expected.txt: Added.
* LayoutTests/fast/editing/insert-text-hit-testing-crash.html: Added.
* Source/WebCore/dom/Document.cpp:
(WebCore::Document::hitTest):

Originally-landed-as: 259548.535@safari-7615-branch (3bc53a0a2ccf). 
rdar://107375598
Canonical link: https://commits.webkit.org/264497@main


Compare: https://github.com/WebKit/WebKit/compare/2f019929ef93...23ef02b6528e
___
webkit-changes mailing list
webkit-changes@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-changes


[webkit-changes] [WebKit/WebKit] 439b3f: Ignore snap offsets with an identifier of zero

2023-05-22 Thread JC Alvarado
  Branch: refs/heads/main
  Home:   https://github.com/WebKit/WebKit
  Commit: 439b3f7091afcdcb29c02821fd8ead3b24d90d60
  
https://github.com/WebKit/WebKit/commit/439b3f7091afcdcb29c02821fd8ead3b24d90d60
  Author: JC Alvarado 
  Date:   2023-05-22 (Mon, 22 May 2023)

  Changed paths:
A LayoutTests/fast/scrolling/scroll-snap-crash-expected.txt
A LayoutTests/fast/scrolling/scroll-snap-crash.html
M Source/WebCore/platform/ScrollSnapAnimatorState.cpp

  Log Message:
  ---
  Ignore snap offsets with an identifier of zero
https://bugs.webkit.org/show_bug.cgi?id=254383
rdar://107130316

Reviewed by Simon Fraser.

When updating snap offsets, if there is no element for a RenderBox,
then a snap offset with an identifier of 0 is created. This can lead
to issues when we add that offset identifier to a HashSet so we should
ignore them in ScrollSnapAnimatorState::currentlySnappedBoxes().

* LayoutTests/fast/animation/scroll-snap-crash-expected.txt: Added.
* LayoutTests/fast/animation/scroll-snap-crash.html: Added.
* Source/WebCore/platform/ScrollSnapAnimatorState.cpp:
(WebCore::ScrollSnapAnimatorState::currentlySnappedBoxes const):

Originally-landed-as: 259548.525@safari-7615-branch (3d4fc69bfad2). 
rdar://107130316
Canonical link: https://commits.webkit.org/264359@main


___
webkit-changes mailing list
webkit-changes@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-changes


[webkit-changes] [WebKit/WebKit] e4c271: Increase max scrollbar update passes

2023-05-22 Thread JC Alvarado
  Branch: refs/heads/main
  Home:   https://github.com/WebKit/WebKit
  Commit: e4c271f0d9f8b4f3b7ea38335366734a81433920
  
https://github.com/WebKit/WebKit/commit/e4c271f0d9f8b4f3b7ea38335366734a81433920
  Author: JC Alvarado 
  Date:   2023-05-22 (Mon, 22 May 2023)

  Changed paths:
A LayoutTests/fast/editing/frame-selection-in-child-view-crash-expected.txt
A LayoutTests/fast/editing/frame-selection-in-child-view-crash.html
M Source/WebCore/platform/ScrollView.cpp
M Tools/TestWebKitAPI/Tests/WebKitCocoa/CSSViewportUnits.mm

  Log Message:
  ---
  Increase max scrollbar update passes
rdar://104064235

Reviewed by Simon Fraser.

Scrollbars are not fully updated in a single layout which
can lead to an additional layout in the scriptDisallowedScope
in FrameView::scrollRectToVisibleInChildView.

* LayoutTests/fast/editing/frame-selection-in-child-view-crash-expected.txt: 
Added.
* LayoutTests/fast/editing/frame-selection-in-child-view-crash.html: Added.
* Source/WebCore/platform/ScrollView.cpp:
(WebCore::ScrollView::updateScrollbars):

* Tools/TestWebKitAPI/Tests/WebKitCocoa/CSSViewportUnits.mm:
(TEST):
Add scrollbarSize to width in WritingMode tests because we should
expect vertical overflow in these cases. This test would pass prior
to this patch despite the displayed WebView having both a vertical
and horizontal scroll bar.

Originally-landed-as: 259548.465@safari-7615-branch (cf0b3436ba58). 
rdar://104064235
Canonical link: https://commits.webkit.org/264353@main


___
webkit-changes mailing list
webkit-changes@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-changes


[Touch-packages] [Bug 2018327] [NEW] package initramfs-tools 0.140ubuntu13.1 failed to install/upgrade: el subproceso instalado paquete initramfs-tools script post-installation devolvió el código de s

2023-05-02 Thread JC
Public bug reported:

I receive error msg

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: initramfs-tools 0.140ubuntu13.1
ProcVersionSignature: Ubuntu 5.19.0-40.41~22.04.1-generic 5.19.17
Uname: Linux 5.19.0-40-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu82.4
AptOrdering:
 openssl:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Tue May  2 20:34:26 2023
ErrorMessage: el subproceso instalado paquete initramfs-tools script 
post-installation devolvió el código de salida de error 1
InstallationDate: Installed on 2020-05-25 (1071 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
PackageArchitecture: all
Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.21.1ubuntu2.1
 apt  2.4.9
SourcePackage: initramfs-tools
Title: package initramfs-tools 0.140ubuntu13.1 failed to install/upgrade: el 
subproceso instalado paquete initramfs-tools script post-installation devolvió 
el código de salida de error 1
UpgradeStatus: Upgraded to jammy on 2022-08-24 (251 days ago)

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package jammy

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/2018327

Title:
  package initramfs-tools 0.140ubuntu13.1 failed to install/upgrade: el
  subproceso instalado paquete initramfs-tools script post-installation
  devolvió el código de salida de error 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  I receive error msg

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: initramfs-tools 0.140ubuntu13.1
  ProcVersionSignature: Ubuntu 5.19.0-40.41~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-40-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82.4
  AptOrdering:
   openssl:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Tue May  2 20:34:26 2023
  ErrorMessage: el subproceso instalado paquete initramfs-tools script 
post-installation devolvió el código de salida de error 1
  InstallationDate: Installed on 2020-05-25 (1071 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.4.9
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.140ubuntu13.1 failed to install/upgrade: el 
subproceso instalado paquete initramfs-tools script post-installation devolvió 
el código de salida de error 1
  UpgradeStatus: Upgraded to jammy on 2022-08-24 (251 days ago)

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


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


[webkit-changes] [WebKit/WebKit] 25d4c6: Do not update hasOutlineAutoAncestor when moving o...

2023-04-28 Thread JC Alvarado
  Branch: refs/heads/main
  Home:   https://github.com/WebKit/WebKit
  Commit: 25d4c6c5948d715b1d1b51ba086c274d1d61
  
https://github.com/WebKit/WebKit/commit/25d4c6c5948d715b1d1b51ba086c274d1d61
  Author: JC Alvarado 
  Date:   2023-04-28 (Fri, 28 Apr 2023)

  Changed paths:
M Source/WebCore/rendering/RenderObject.cpp
M Source/WebCore/rendering/updating/RenderTreeBuilder.cpp

  Log Message:
  ---
  Do not update hasOutlineAutoAncestor when moving out a spanner's renderer
https://bugs.webkit.org/show_bug.cgi?id=255956
rdar://107953410

Reviewed by Alan Baradlay.

When we move out a spanner's renderer, we might set the renderer as having
a hasOutlineAutoAncestor value of true and leave the spanner placeholder
with a hasOutlineAutoAncestor value of false. This is because when we move
out the spanner's renderer we set hasOutlineAutoAncestor based on its new
parent. However we want to maintain a value consistent with spanner's 
placholder.

* Source/WebCore/rendering/RenderObject.cpp:
(WebCore::RenderObject::propagateRepaintToParentWithOutlineAutoIfNeeded const):
We want to check if the originalRenderer needs a repaint, not the placeholder.

* Source/WebCore/rendering/updating/RenderTreeBuilder.cpp:
(WebCore::RenderTreeBuilder::attachToRenderElementInternal):

Canonical link: https://commits.webkit.org/263501@main


___
webkit-changes mailing list
webkit-changes@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-changes


[webkit-changes] [WebKit/WebKit] 5f072a: Use smart pointers for captured variables stored i...

2023-04-27 Thread JC Alvarado
  Branch: refs/heads/main
  Home:   https://github.com/WebKit/WebKit
  Commit: 5f072a4987568b69edfdbf81de2c9f4b0431d125
  
https://github.com/WebKit/WebKit/commit/5f072a4987568b69edfdbf81de2c9f4b0431d125
  Author: JC Alvarado 
  Date:   2023-04-27 (Thu, 27 Apr 2023)

  Changed paths:
M Source/WebKit/GPUProcess/GPUProcess.cpp
M Source/WebKit/NetworkProcess/NetworkProcess.cpp

  Log Message:
  ---
  Use smart pointers for captured variables stored in memory pressure handler
https://bugs.webkit.org/show_bug.cgi?id=255992
rdar://problem/108561984

Reviewed by Ryosuke Niwa.

Adopt smart pointers for captured variables in GPUProcess::initializeGPUProcess 
and
NetworkProcess::initializeNetworkProcess.

* Source/WebKit/NetworkProcess/NetworkProcess.cpp:
(WebKit::NetworkProcess::initializeNetworkProcess):

Canonical link: https://commits.webkit.org/263466@main


___
webkit-changes mailing list
webkit-changes@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-changes


[PestList] Re: Crushed dreams of a world free of MWD*s

2023-04-26 Thread JC Reardon
Hi Joel,

The two closest traps were adhesive board multi-pheromone Cloth Moth Traps from 
MothPrevention out of the UK.  Been using them for several years and always 
caught something.  Date on the packaging is 06/25, set them out March 18, and 
yes, they are still very, very sticky.

One is now in close(r) quarters with patient zero in the isolation bathtub, and 
I put out fresh ones in the storage area.   No takers yet.

We might have another brand in one of the other storage areas but I don't dare 
check until I have a change of clothes.

-JC


From: pestlist@googlegroups.com<mailto:pestlist@googlegroups.com> 
mailto:pestlist@googlegroups.com>> on behalf of 
Voron, Joel mailto:jvo...@cwf.org>>
Sent: Wednesday, April 26, 2023 1:26:43 PM
To: pestlist@googlegroups.com<mailto:pestlist@googlegroups.com> 
mailto:pestlist@googlegroups.com>>
Subject: [PestList] Re: Crushed dreams of a world free of MWD*s

Question #1 what type of traps?

Joel Voron   Colonial Williamsburg Foundation
  Conservation Dept.
 Integrated Pest Management Specialist
  Office 757-220-7080
Cell 757-634-1175
  E-Mail jvo...@cwf.org<mailto:jvo...@cwf.org>


From: pestlist@googlegroups.com<mailto:pestlist@googlegroups.com> 
mailto:pestlist@googlegroups.com>> on behalf of JC 
Reardon mailto:j...@saintonge.org>>
Sent: Wednesday, April 26, 2023 1:00 PM
To: pestlist@googlegroups.com<mailto:pestlist@googlegroups.com>
Subject: [PestList] Crushed dreams of a world free of MWD*s

[CAUTION: This message originated from outside the Foundation. Do not click 
links, open attachments or take action unless you know the contents are safe]
It seemed too good to be true.  It's warming up, the humidity is way up: moth 
prime time here in New England. Yet not a sign of moths in the most valuable 
wool storage area in the building, clean traps high and low.  Our isolation 
efforts must finally be paying off!

I was actually excited, could I for once focus on actual repairs instead of 
mitigation? A quarterly airing-out without caution tape and quarantine zones?

But wait, what's this suspicious lint drifting to the floor?  That's odd... 
hang on...




S, how's everyone else's day going?  Mine is going... actually, it's not 
going at all, mine has just screeched to a halt.

Put bluntly, I'm not a happy camper in more ways than one.  Not sure if I want 
to scream, tear my hair out, burn the place down, or hide in the janitor's 
closet with a bucket on my head.

I suspect I've just learned a valuable lesson -don't trust the traps - the hard 
way, and I'm hoping the damage is limited to my crushed spirit and already 
overburdened workload, and that the collateral damage to textiles is limited in 
extent.

But now that my faith in the universe of IPM as I know it has been shattered, 
I've got questions:

Question 1: What went wrong here?  What could be the reason behind multiple 
empty traps adjacent to obviously active infestations? Fresh, opened just over 
a month ago, placed both high and low, minimal light, practically zero air 
flow, and one was literally a handspan away from the red item pictured.

Question 2: What would you have done/do to avoid it happening again?  Where do 
you draw the line when it comes to "trust but verify" and indicator traps?  How 
often does this sort of thing happen?

Question 3: How long has it been going on?  At what point should we have caught 
this / was it just the traps that missed it? What size does a population have 
to reach before traps will reliably indicate?  What's the worst case (for us) 
scenario/time-frame for reaching that point, under ideal (for them) conditions?

Apologies for the slew of questions; while I'd like to claim it's out of a 
pursuit of understanding and a dedication to conservation, I will admit the 
length of this email is directly related to just how much I don't want to go 
deal with this.  (Again.)

Your time and any knowledge or wisdom you care to share will be greatly 
appreciated!

Best Regards,

JC Reardon


*MWDs = Moths of Wool Destruction.








--
You received this message because you are subscribed to the Google Groups 
"MuseumPests" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
pestlist+unsubscr...@googlegroups.com<mailto:pestlist+unsubscr...@googlegroups.com<mailto:pestlist+unsubscr...@googlegroups.com%3cmailto:pestlist+unsubscr...@googlegroups.com>>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/pestlist/MN2PR16MB278319B77F57A4424ED83F02C5659%40MN2PR16MB2783.namprd16.prod.outlook.com<https://groups.google.com/d/msgid/pestlist/MN2PR16MB278319B77F57A4424ED83F02C5659%40MN2PR16MB2783.namprd16.prod.outlook.com?utm_medium=email_source=footer><https://groups.google.com/d/msgid/pestlist/MN2PR16MB278319B77F57A4

[webkit-changes] [WebKit/WebKit] 0a6033: Check if ShadowRoot nodes are cloneable when extra...

2023-04-13 Thread JC Alvarado
  Branch: refs/heads/main
  Home:   https://github.com/WebKit/WebKit
  Commit: 0a60334817acffa3be8fcf8d9e170fac7c331669
  
https://github.com/WebKit/WebKit/commit/0a60334817acffa3be8fcf8d9e170fac7c331669
  Author: JC Alvarado 
  Date:   2023-04-13 (Thu, 13 Apr 2023)

  Changed paths:
M Source/WebCore/dom/Range.cpp

  Log Message:
  ---
  Check if ShadowRoot nodes are cloneable when extracting a range
https://bugs.webkit.org/show_bug.cgi?id=254842
rdar://106276289

Reviewed by Ryosuke Niwa.

When extracting or cloning a range, we might call cloneNode on a ShadowRoot
that is not cloneable resulting in a release assertion crash. We should skip
nodes that are not cloneable in processAncestorsAndTheirSiblings.

* Source/WebCore/dom/Range.cpp:
(WebCore::processAncestorsAndTheirSiblings):

Canonical link: https://commits.webkit.org/262933@main


___
webkit-changes mailing list
webkit-changes@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-changes


[webkit-changes] [WebKit/WebKit] c27c56: Wrap captured variable with WeakPtr in GPUProcess:...

2023-03-30 Thread JC Alvarado
  Branch: refs/heads/main
  Home:   https://github.com/WebKit/WebKit
  Commit: c27c56bff56cb60c7e717975cfe3b8cf1eec31c0
  
https://github.com/WebKit/WebKit/commit/c27c56bff56cb60c7e717975cfe3b8cf1eec31c0
  Author: JC Alvarado 
  Date:   2023-03-30 (Thu, 30 Mar 2023)

  Changed paths:
M Source/WebKit/GPUProcess/GPUProcess.cpp

  Log Message:
  ---
  Wrap captured variable with WeakPtr in GPUProcess::initializeGPUProcess
https://bugs.webkit.org/show_bug.cgi?id=254316
rdar://107117855

Reviewed by Ryosuke Niwa and Youenn Fablet.

We are storing a lambda with a captured variable. We should use a
smart pointer here so we can check if this is alive before accessing it.

* Source/WebKit/GPUProcess/GPUProcess.cpp:
(WebKit::GPUProcess::initializeGPUProcess):

Canonical link: https://commits.webkit.org/262314@main


___
webkit-changes mailing list
webkit-changes@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-changes


[webkit-changes] [WebKit/WebKit] 15d4f3: Use Ref for m_node in ComposedTreeAncestorIterator

2023-03-29 Thread JC Alvarado
  Branch: refs/heads/main
  Home:   https://github.com/WebKit/WebKit
  Commit: 15d4f3483d44b391652df7d59e5eba54e9316063
  
https://github.com/WebKit/WebKit/commit/15d4f3483d44b391652df7d59e5eba54e9316063
  Author: JC Alvarado 
  Date:   2023-03-29 (Wed, 29 Mar 2023)

  Changed paths:
M Source/WebCore/dom/ComposedTreeAncestorIterator.h

  Log Message:
  ---
  Use Ref for m_node in ComposedTreeAncestorIterator
https://bugs.webkit.org/show_bug.cgi?id=254274
rdar://107061402

Reviewed by Chris Dumez.

* Source/WebCore/dom/ComposedTreeAncestorIterator.h:
(WebCore::ComposedTreeAncestorAdapter::ComposedTreeAncestorAdapter):
(WebCore::ComposedTreeAncestorAdapter::begin):

Canonical link: https://commits.webkit.org/262298@main


___
webkit-changes mailing list
webkit-changes@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-changes


[webkit-changes] [WebKit/WebKit] 1bb6a5: Cherry-pick 259548.8@safari-7615-branch (5a0f792b0...

2023-03-28 Thread JC Alvarado
  Branch: refs/heads/main
  Home:   https://github.com/WebKit/WebKit
  Commit: 1bb6a599c3aef0843ff171cb156f008ae1c634a0
  
https://github.com/WebKit/WebKit/commit/1bb6a599c3aef0843ff171cb156f008ae1c634a0
  Author: JC Alvarado 
  Date:   2023-03-28 (Tue, 28 Mar 2023)

  Changed paths:
A LayoutTests/fast/backgrounds/background-color-lch-crash-expected.txt
A LayoutTests/fast/backgrounds/background-color-lch-crash.html
M Source/WebCore/platform/graphics/ColorBlending.cpp

  Log Message:
  ---
  Cherry-pick 259548.8@safari-7615-branch (5a0f792b008f). rdar://10795

Check color opacity after lossy conversion when blending
https://bugs.webkit.org/show_bug.cgi?id=251158
rdar://104553839

Reviewed by Dean Jackson.

We check opacity to determine if we should forgo blending,
however after performing a lossy conversion we can end
up with alpha values that result in a division by zero.
Add an additional check after conversion to prevent this
case.

* LayoutTests/fast/backgrounds/background-color-lch-crash-expected.txt: 
Added.
* LayoutTests/fast/backgrounds/background-color-lch-crash.html: Added.
* Source/WebCore/platform/graphics/ColorBlending.cpp:
(WebCore::blendSourceOver):

Canonical link: https://commits.webkit.org/259548.8@safari-7615-branch

Canonical link: https://commits.webkit.org/262245@main


___
webkit-changes mailing list
webkit-changes@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-changes


[webkit-changes] [WebKit/WebKit] 1b354f: Use CheckedRef for m_documentLoader in Application...

2023-03-20 Thread JC Alvarado
  Branch: refs/heads/main
  Home:   https://github.com/WebKit/WebKit
  Commit: 1b354fa4ac8a76b80ec9678da8d00c67adca663a
  
https://github.com/WebKit/WebKit/commit/1b354fa4ac8a76b80ec9678da8d00c67adca663a
  Author: JC Alvarado 
  Date:   2023-03-20 (Mon, 20 Mar 2023)

  Changed paths:
M Source/WebCore/loader/DocumentLoader.h
M Source/WebCore/loader/appcache/ApplicationCacheHost.cpp
M Source/WebCore/loader/appcache/ApplicationCacheHost.h

  Log Message:
  ---
  Use CheckedRef for m_documentLoader in ApplicationCacheHost
https://bugs.webkit.org/show_bug.cgi?id=254086
rdar://106870953

Reviewed by Ryosuke Niwa.

DocumentLoader is RefCountable so we should use a smart pointer for
ApplicationCacheHost's m_documentLoader member variable.

* Source/WebCore/loader/DocumentLoader.h:
* Source/WebCore/loader/appcache/ApplicationCacheHost.cpp:
(WebCore::ApplicationCacheHost::ApplicationCacheHost):
(WebCore::ApplicationCacheHost::selectCacheWithoutManifest):
(WebCore::ApplicationCacheHost::selectCacheWithManifest):
(WebCore::ApplicationCacheHost::canLoadMainResource):
(WebCore::ApplicationCacheHost::maybeLoadMainResource):
(WebCore::ApplicationCacheHost::maybeLoadFallbackForMainResponse):
(WebCore::ApplicationCacheHost::maybeLoadFallbackForMainError):
(WebCore::ApplicationCacheHost::maybeLoadResource):
(WebCore::ApplicationCacheHost::maybeLoadFallbackForError):
(WebCore::ApplicationCacheHost::maybeLoadSynchronously):
(WebCore::ApplicationCacheHost::notifyDOMApplicationCache):
(WebCore::ApplicationCacheHost::shouldLoadResourceFromApplicationCache):
(WebCore::ApplicationCacheHost::scheduleLoadFallbackResourceFromApplicationCache):
(WebCore::ApplicationCacheHost::update):
(WebCore::ApplicationCacheHost::swapCache):
(WebCore::ApplicationCacheHost::abort):
(WebCore::ApplicationCacheHost::isApplicationCacheEnabled):
(WebCore::ApplicationCacheHost::isApplicationCacheBlockedForRequest):
* Source/WebCore/loader/appcache/ApplicationCacheHost.h:

Canonical link: https://commits.webkit.org/261896@main


___
webkit-changes mailing list
webkit-changes@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-changes


[chrono] Suspension disconnected from chassis?

2023-03-12 Thread 'JC Denton' via ProjectChrono
I'm having an issue where my vehicles suspension and spindle don't appear 
connected to the rest of the vehicle.

When visualizing the components at runtime, I gather the vehicle's wheels, 
body, suspension and spindle locations and set them according to their 
values. 

I'm getting the body position via:
Vehicle->GetPos();

the wheel positions via:
Vehicle->GetWheel(0, RIGHT)->GetState().pos
Vehicle->GetWheel(0, LEFT)->GetState().pos
Vehicle->GetWheel(1, RIGHT)->GetState().pos
Vehicle->GetWheel(1, LEFT)->GetState().pos 

The suspension locations via:
Vehicle->GetAxle(0)->m_suspension->GetRelPosition() +  Vehicle->GetPos(); 
Vehicle->GetAxle(1)->m_suspension->GetRelPosition() +  Vehicle->GetPos(); 

and the spindle locations via:
Vehicle->GetAxle(0)->m_suspension->GetSpindlePos(VehicleSide::RIGHT);
Vehicle->GetAxle(0)->m_suspension->GetSpindlePos(VehicleSide::LEFT);
Vehicle->GetAxle(1)->m_suspension->GetSpindlePos(VehicleSide::RIGHT);
Vehicle->GetAxle(1)->m_suspension->GetSpindlePos(VehicleSide::LEFT);

As you can see in this video, the chassis and wheel positions are 
reasonable, but the suspensions and spindles (marked with white text) are 
not in the correct position, and they move further and further to the rear 
of the vehicle the longer the simulation continues.

https://youtu.be/Rzg26OFCrW4

The relative position of the suspension continues to increase relative to 
the chassis as the simulation continues.

Any potential things that could cause this? I assumed the suspension was 
fixed to the chassis, and the spindles were fixes to the suspension (+- the 
suspension limits). Also assumed the wheels would be attached to the 
spindle, so it seems odd that they don't seem to be connected. 

In addition, the vehicle continually moves backwards, despite the wheels 
not turning. 

-- 
You received this message because you are subscribed to the Google Groups 
"ProjectChrono" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to projectchrono+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/projectchrono/850895cb-b1f3-40a8-b376-37bfa1ef77dan%40googlegroups.com.


[webkit-changes] [WebKit/WebKit] 682fa4: Check pixel buffer before dereferencing

2023-03-10 Thread JC Alvarado
  Branch: refs/heads/main
  Home:   https://github.com/WebKit/WebKit
  Commit: 682fa4507d4d42682ffc76a8a9703c30dbd91e1d
  
https://github.com/WebKit/WebKit/commit/682fa4507d4d42682ffc76a8a9703c30dbd91e1d
  Author: JC Alvarado 
  Date:   2023-03-10 (Fri, 10 Mar 2023)

  Changed paths:
A LayoutTests/fast/html/canvas-integer-overflow-expected.txt
A LayoutTests/fast/html/canvas-integer-overflow.html
M Source/WebCore/html/canvas/CanvasRenderingContext2DBase.cpp

  Log Message:
  ---
  Check pixel buffer before dereferencing
https://bugs.webkit.org/show_bug.cgi?id=253686
rdar://106492794

Reviewed by Aditya Keerthi.

When calculating the area of a rect, there can be an integer overflow
that results in getPixelBuffer returning a nullptr. In this case, we
should return early from postProcessPixelBuffer.

* LayoutTests/fast/html/canvas-integer-overflow-expected.txt: Added.
* LayoutTests/fast/html/canvas-integer-overflow.html: Added.
* Source/WebCore/html/canvas/CanvasRenderingContext2DBase.cpp:
(WebCore::CanvasRenderingContext2DBase::postProcessPixelBuffer const):

Canonical link: https://commits.webkit.org/261532@main


___
webkit-changes mailing list
webkit-changes@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-changes


Re: [Standards] Moderation (XEP-0425) by anonymous moderator/admin

2023-03-02 Thread JC Brand


On 27.02.23 18:20, Nicolas Cedilnik wrote:

Hi all,

XEP-0425 is explicit about the "by" attribute of  being 
mandatory:


> The  element MUST have a 'by' attribute specifying the 
JID of the moderating entity.


> 

Following up on a jdev@ discussion, I believe there are legitimate use 
cases where this requirement should be alleviated:


- preventing offenders to come at moderators directly

- moderation with external (eg, CLI) tools

- service-wide moderation, where a MUC service admin might want to 
remove all messages with a certain attachment, eg disturbing awful 
pictures, URLs, from a certain author, etc.


- gateways to services where there the moderator is not known

Would a PR in this direction be acceptable?



Hi Nicolas

I've relaxed the requirement from MUST to SHOULD.

The change is in this PR: https://github.com/xsf/xeps/pull/1271

All the best
JC

___
Standards mailing list
Info: https://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: standards-unsubscr...@xmpp.org
___


Re: [Standards] XEP-0424: Message Retraction - Remove Fastening

2023-02-20 Thread JC Brand


On 20.02.23 10:32, Florian Schmaus wrote:

On 13/02/2023 16.57, Daniel Gultsch wrote:

I’m currently looking at implementing 'Message Retraction' and I think
it should get rid of Fastening.

I mentioned it during Summit and while it wasn’t discussed much
further my comment also didn’t get much protest: I think Fastening is
dead.

A general purpose approach doesn’t seem to work for MAM.

Luckily I think removing it from Retraction is fairly simple.

We can just stick the ID into the retract element and send something




Since origin-id is spoofable, one should not use it when referencing 
other stanzas. Instead always use the 'id' *and* 'by' value of 
xep359's  element.


So the example above should become something like


  


While one could argue that the 'by' attribute could potentially be 
omitted and made implicit, e.g., it has the value of the MUC service 
that hosts the MUC in which a message got retracted, I believe this 
could lead far too easily to insecure implementations that only 
compare the id value, making the technically unspoofable xep359 
stanza-id spoofable again [1]. Therefore I would strongly consider 
making it mandatory and explicit.



Fair enough. I searched in the XEPs repo to see if some other XEP uses 
 and no-one does, even though there are other XEPs 
that do similar things, like XEP-0444 reactions.


___
Standards mailing list
Info: https://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: standards-unsubscr...@xmpp.org
___


Re: [Standards] LAST CALL: XEP-0425 (Message Moderation)

2023-02-19 Thread JC Brand

Hi All

Thanks to everyone who responded with feedback on the XEP-0425 Last 
Call, especially Marvin for the well founded criticism and helpful 
suggestions.


I've made a PR which I believe addresses the main criticisms and 
suggestions.

https://github.com/xsf/xeps/pull/1271

To recap:

1. Remove the dependency on XEP-0422 Message Fastening (and thereby use 
direct child of IQ)
2. Rename to 'Moderated Message Retraction' and focus only on the 
retraction use-case

3. Ensure compatibility with clients that only implement XEP-0424
4. Clarify the purpose of the reason element

Also, my apologies for taking so long to respond.

All the best
JC


On 07.12.21 19:45, Marvin W wrote:

Hi,

Answering the standard questions first.


1. Is this specification needed to fill gaps in the XMPP protocol
stack or to clarify an existing protocol?

Yes.


2. Does the specification solve the problem stated in the introduction
and requirements?

No.

The introduction explains different moderator actions:
- "retracting them [groupchat messages] from the groupchat history"
- "correct a message on another user's behalf"
- "flag a message as inappropriate without requiring that it be retracted"

The XEP only defines means for retracting messages. While the syntax
suggests that other moderator actions might be added (by putting
something else in  than ), the semantics
described only make sense for retraction.


3. Do you plan to implement this specification in your code? If not,
why not?

Not really. The current specification has too many issues to be
considered sensible to implement in production IMO.


4. Do you have any security concerns related to this specification?

No.


5. Is the specification accurate and clearly written?

No.
There is absolutely no normative description of the syntax being used.
The examples show a  element inside / which
is not described anywhere outside the examples (and also does not appear
in the XML schema)


- The XEP in its current form is not a generic message moderation XEP as
suggested in its name, abstract and introduction.
- The XEP depends on XEP-0424 (Message retraction) while not being
compatible at all or taking any of its semantics. The only thing taken
from XEP-0424 is the syntax element  which is used in a
different way as described in XEP-0424.
- The XEP uses  element from XEP-0422 in an IQ. However
XEP-0422 only describes means and rules for using  inside
messages. According to RFC-6121 §6, `the specific semantics needed to
complete particular use cases are defined in all instances by the
extended namespace that qualifies the direct child element of an IQ
stanza of type "get" or "set"`. However, the semantics of the IQ shown
in example 4 of XEP-0425 are defined by the second level child of the IQ
stanza (the  inside the ).

Suggestions for changes:
- Focus on solely providing the feature of moderated message retraction
in all parts of the specification.
- Use own direct child for IQ to MUC service instead of .
- Clarify (optional) usage of  (this was already discussed
on-list IIRC).
- Choose syntax of message sent to participants and tombstones such that
clients that only implement XEP-0424 will understand the message
retraction (maybe losing information that retraction was performed by a
moderator). For example by placing the  inside the 
instead of the other way round. Alternatively consider moderated
retraction and self retraction completely independent features that
don't share any syntax elements.

IMO, this XEP needs further work before being ready to move to Stable.

Marvin
___
Standards mailing list
Info: https://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: standards-unsubscr...@xmpp.org
___

___
Standards mailing list
Info: https://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: standards-unsubscr...@xmpp.org
___


Re: [Standards] XEP-0424: Message Retraction - Remove Fastening

2023-02-19 Thread JC Brand

Hi Daniel

Thanks for bringing this up again. This was also the feedback when the 
XEP was reviewed by council about 2 (!) years ago.


As one of the XEP authors, I've gone ahead and made a PR with the change.
https://github.com/xsf/xeps/pull/1270

The next XEP, 0425 'Message Moderation' is related and similar and also 
relies on fastenings. I'll look into remove them there as well.


Regards
JC

On 13.02.23 16:57, Daniel Gultsch wrote:

Hi,

I’m currently looking at implementing 'Message Retraction' and I think
it should get rid of Fastening.

I mentioned it during Summit and while it wasn’t discussed much
further my comment also didn’t get much protest: I think Fastening is
dead.

A general purpose approach doesn’t seem to work for MAM.

Luckily I think removing it from Retraction is fairly simple.

We can just stick the ID into the retract element and send something



All the business rules and much of the wording can remain intact for now.

(I think long term we might want to adopt the ID rules from Replies;
but that can be a different discussion)

If people are happy with that suggestion (to get rid of Fastening) I
think I can very easily make a PR.

cheers
Daniel
___
Standards mailing list
Info: https://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: standards-unsubscr...@xmpp.org
___

___
Standards mailing list
Info: https://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: standards-unsubscr...@xmpp.org
___


Re: [OpenSIPS-Users] trunking connection expires?

2023-02-15 Thread JC Lee

-Original Message-
From: "JC Lee"
To: ;
Cc:
Sent: 2023-02-10 (금) 15:03:42 (GMT+09:00)
Subject: [OpenSIPS-Users] trunking connection expires?

I am using opensips 3.2.10 with trunking service.
First the opensips service starts, it goes well with first 120 second.
And after that, the call is not connected and there is no incoming logs.
'opensips-cli -x mi reg_list' command shows that the same status as when it 
goes well.

I got some logs from trunking service, they sent invite and ack message 
normally but opensips received nothing.

What is the problem?

--
I found some log that seems to be related while uac_registrant

opensips[42303]: DBG:uac_registrant:reg_tm_cback: tm [0x7fd5c68f27b0] 
notification cb for  [200] reply at [1674579393]
opensips[42303]: DBG:uac_registrant:reg_print_record: checking 
uac=[0x7fd5c673d3c8] state=[2][AUTHENTICATING_STATE] expires=[-970240579] 
last_register_sent=[1674579393] registration_timeout=[0] 
auth_user[0x7fd5c673d5dd][11]->[070**] 
auth_password=[0x7fd5c673d5e8][7]->[R2nbWZ5] sock=[0x7fd5c8372140] 
clustering=[/0] enabled=[yes]
opensips[42303]: DBG:uac_registrant:reg_print_record: 
RURI=[0x7fd5c673d5cb][18]->[sip:211.233.***]
opensips[42303]: DBG:uac_registrant:reg_print_record:   
To=[0x7fd5c673d5a8][35]->[sip:070***@211.233.***:5060]
opensips[42303]: DBG:uac_registrant:reg_print_record: 
From=[0x7fd5c673d5a8][35]->[sip:070***@211.233.***:5060] 
tag=[0x7fd5c673d5a3][5]->[3df50]
opensips[42303]: DBG:uac_registrant:reg_print_record:  
Call-Id=[0x7fd5c673d588][27]->[56895a842ce5f806ae37f29dc43]
opensips[42303]: DBG:uac_registrant:reg_print_record:  
Contact=[0x7fd5c673d5ef][30]->[sip:070***@211.233.***] [(nil)][0]->[]
opensips[42303]: DBG:core:parse_headers: flags=
opensips[42303]: DBG:core:parse_params: Parsing params for:[expires=120]

with opensips 3.2, the value of last line is 120 and the trunk connection seems 
to be expired about 120 seconds,
and opensips 2.2, the value of 3600 and it seems to last an hour.

I edited tcp_connection_lifetime and uac_registrant timer inverval and 
registrar default expires, but the log is not changed.

what is the expires value from?



___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


[OpenSIPS-Users] trunking connection expires?

2023-02-09 Thread JC Lee
I am using opensips 3.2.10 with trunking service.
First the opensips service starts, it goes well with first 120 second.
And after that, the call is not connected and there is no incoming logs.
'opensips-cli -x mi reg_list' command shows that the same status as when it 
goes well.

I got some logs from trunking service, they sent invite and ack message 
normally but opensips received nothing.

What is the problem?
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


Re: What Pentax gear is on your shopping (or wish) list?

2023-01-17 Thread JC OConnell
since I already have nearly a complete set of "K" primes
my recent acqusition of of thr K1 was the final nail in the cofffin
asfar as my pentax collection goes.
jco
-Original Message-
From: Pentax-Discuss Mail List 
Sent: Jan 15, 2023 12:14 PM
To: Pentax-Discuss Mail List 
Subject: Re: What Pentax gear is on your shopping (or wish) list?

Im actually content with my gear. I really like my K-5 and have no 
desire to buy a newer body.

I do wish that my 17-70 was weatherproof, or that my wifes 18-85 was 
wider at the short end. Oh, and that my 80-320 was sharper.

Rick

> On Jan 15, 2023, at 10:19 AM, Steve Cottrell wrote:
>
> Which one ? ;-)
>
>
> On 15 Jan 2023, at 04:43, Larry Colen wrote:
>
> The 85/1.4 is also kind of on my wish list, but the pricing is such that it 
> barely qualifies as an idle fantasy.
> --
> %(real_name)s Pentax-Discuss Mail List
> To unsubscribe send an email to pdml-le...@pdml.net
> to UNSUBSCRIBE from the PDML, please visit the link directly above and follow 
> the directions.
--
%(real_name)s Pentax-Discuss Mail List
To unsubscribe send an email to pdml-le...@pdml.net
to UNSUBSCRIBE from the PDML, please visit the link directly above and follow 
the directions.

--
%(real_name)s Pentax-Discuss Mail List
To unsubscribe send an email to pdml-le...@pdml.net
to UNSUBSCRIBE from the PDML, please visit the link directly above and follow 
the directions.


[chrono] Re: How to configure the articulated vehicle JSON file ? Including coordinates, units and other issues.

2022-12-29 Thread 'JC Denton' via ProjectChrono
 There are some example obj files for vehicles in the chrono project such 
as the truck_chassis.obj or sedan_chassis_col.obj
If you open these up to compare to your obj file you should be able to 
apply the same scale and orientation when you export. You can also change 
the world up direction using ChWorldFrame::SetYUP for Y up, or 
ChWorldFrame::Set() to set the coordinate system to whatever you need. 


On Tuesday, December 27, 2022 at 7:47:02 PM UTC-8 james...@gmail.com wrote:

> Dear all,
>
> First of all at this time to disturb you, I am sorry !
> Happy New Year to you and the Chrono team !
>
>
> I tried to import my own vehicle parameters by modifying the official JSON 
> file ( articulated _ chassis ), but I encountered some problems : 
> ( 1 ) When I import my own frame OBJ file, because my frame is the actual 
> size, I need to reset the coordinates and related parameters, I do not know 
> how to start, even do not know what the unit is. I hope to provide some 
> explanations or comments. This really makes me a headache.
>
> The powerful function of Chrono cannot be separated from the efforts of 
> everyone in the team, and I am very interested in Chrono.
>
> Thank you !
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"ProjectChrono" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to projectchrono+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/projectchrono/b6bdfbb8-026f-4a1d-a6a5-8afabba2f6a6n%40googlegroups.com.


[chrono] Can't seem to get any collisions

2022-12-28 Thread 'JC Denton' via ProjectChrono
I have made a project based closely on the HMMWV using largely the same 
parameters. But when simulating, the vehicle's chassis falls through the 
floor, and the wheels remain in place. I tried PAC02 tire and Rigid Mesh 
tire, as well as Rigid tire without mesh, along with a Rigid Terrain but 
nothing seems to collide. Setting the steering input also doesn't seem to 
change the orientation of the wheels. Making gravity 0 or positive also has 
no effect, chassis still falls through floor.

Inside ChPac02Tire, it indicates each tire is in contact with the surface, 
m_data.in_contact = true. The chassis uses a box Primitive for collision, 
and it appears to be setup and created the physics colliders for it. Using 
NSC System with default settings. The positions all appear correct, with 
the vehicle and its wheels originating slightly above the terrain. I 
initialize my systems in the following order:
Vehicle -> 
Chassis->Steering->Axles->Driveline->Powertrain->Wheels->Tires->RigidTerrain->Driver

I update using 
VehicleDriver->Synchronize(Time);
Landscape->Synchronize(Time);
PhysVehicle->Synchronize(Time,  DriverInputs, *Landscape->GetTerrain());   
 

VehicleDriver->Advance(PhysicsTimeStep);
Landscape->Advance(PhysicsTimeStep);
PhysVehicle->Advance(PhysicsTimeStep);

Clearly something is very amiss, and feels like my systems are not 
communicating with each other although inspecting their components doesn't 
reveal anything out of the ordinary. I'm out of ideas at this point. Is 
there something I might be missing? Or maybe steps I can take to dig 
deeper? 

Thanks for your time

-- 
You received this message because you are subscribed to the Google Groups 
"ProjectChrono" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to projectchrono+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/projectchrono/c5e3a0b3-2cdb-4bbc-9ec5-4b180a90b62cn%40googlegroups.com.


Re: [chrono] How to setup initial wheel rotation?

2022-12-27 Thread 'JC Denton' via ProjectChrono
Great thank you, this was what I was starting to figure, but thank you for 
confirming!

On Monday, December 26, 2022 at 11:57:28 PM UTC-8 Radu Serban wrote:

> This is by design. All wheel reference frames have their Y axis pointing 
> to the left of the vehicle. See 
> https://api.projectchrono.org/vehicle_overview.html#vehicle_ISO_frame for 
> more details on the ISO frame convention used throughout in Chrono::Vehicle.
>
>  
>
> There is no such thing as a “wrong” orientation (it’s all a matter of 
> convention). You just need to take into account the vehicle side a wheel is 
> mounted on when you use (however/wherever you do that) the rotation 
> quaternion in the WheelState struct you get from ChWheel::GetState().
>
>  
>
> --Radu
>
>  
>
> *From:* 'JC Denton' via ProjectChrono  
> *Sent:* Tuesday, 27 December 2022 02:26
> *To:* ProjectChrono 
> *Subject:* [chrono] How to setup initial wheel rotation?
>
>  
>
> I assume  we can get the current wheel orientation using 
> ChWheel::GetState().rot,
>
> which seems to work for the left side of my vehicle, but the right side 
> has the same orientation as the left side. 
>
> I setup the wheels according to their corresponding sides:
>
>  m_axles[0]->m_wheels[0] = 
> chrono_types::make_shared("Wheel_FL", true);
> m_axles[0]->m_wheels[1] = 
> chrono_types::make_shared("Wheel_FR", false);
> m_axles[1]->m_wheels[0] = 
> chrono_types::make_shared("Wheel_RL", true);
> m_axles[1]->m_wheels[1] = 
> chrono_types::make_shared("Wheel_RR", false);
>
>
> and when I query GetState() the positions and rotations are correct except 
> for the Rotations on the Right side. Where can I setup the initial 
> rotation? I figured setting the VehicleSide::RIGHT should do the trick?
>
>  
>
> -- 
> You received this message because you are subscribed to the Google Groups 
> "ProjectChrono" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to projectchron...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/projectchrono/56d16b90-f22c-4ecf-b9f4-4b01f8b98ac9n%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/projectchrono/56d16b90-f22c-4ecf-b9f4-4b01f8b98ac9n%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"ProjectChrono" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to projectchrono+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/projectchrono/3257cfc9-5131-4a73-8c0e-2df0b3a0d7f4n%40googlegroups.com.


[chrono] How to setup initial wheel rotation?

2022-12-26 Thread 'JC Denton' via ProjectChrono
I assume  we can get the current wheel orientation using 
ChWheel::GetState().rot,
which seems to work for the left side of my vehicle, but the right side has 
the same orientation as the left side. 
I setup the wheels according to their corresponding sides:

 m_axles[0]->m_wheels[0] = 
chrono_types::make_shared("Wheel_FL", true);
m_axles[0]->m_wheels[1] = 
chrono_types::make_shared("Wheel_FR", false);
m_axles[1]->m_wheels[0] = 
chrono_types::make_shared("Wheel_RL", true);
m_axles[1]->m_wheels[1] = 
chrono_types::make_shared("Wheel_RR", false);

and when I query GetState() the positions and rotations are correct except 
for the Rotations on the Right side. Where can I setup the initial 
rotation? I figured setting the VehicleSide::RIGHT should do the trick?

-- 
You received this message because you are subscribed to the Google Groups 
"ProjectChrono" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to projectchrono+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/projectchrono/56d16b90-f22c-4ecf-b9f4-4b01f8b98ac9n%40googlegroups.com.


Topband: Small Loop does not receive weak signal on 160m BOUVET RX SPOILER

2022-12-23 Thread JC


Hi topband lovers

 

Some friends contact me with deep concerns about the next Bouvet DX expedition 
receiver antenna called SALAD

 

 <http://www.lz1aq.signacor.com/docs/active-wideband-directional-antenna.php> 
Salad antenna

 

I understand the concerns, Bouvet on 160m is a lifetime opportunity for most 
top-banders!

 

When Doug NX4D, me N4IS and Dr Dallas started to try to understand the 
limitation of the new Waller Flag, the first big question was;

 

How small a loop antenna can be to receive weak signal on 160, or MW? 

 

Dr. Dallas Lankford III (SK), measured the internal noise of a small loop. 
15x15 FT on his quiet QTH, and wrote a paper with the derivation necessary to 
calculate the thermal noise of a small loop. The study most important point was:

 

The sensitivity of small loop antennas can be limited by internally generated 
thermal noise which is a characteristic of the loop itself. Even amplifying the 
loop output with the lowest noise figure preamp available may not improve the 
loop sensitivity if manmade noise drops low enough

 

The noise on Bouvet island will be very low, < -120 dBm at 500Hz,  and for sure 
the internal thermal noise of the prosed RX antenna will limit the reception of 
weak signals on 160m, it may work on 80 and above, but for 160 m, it will be a 
set up for failure.

 

Why not a single, trustable beverage antenna over the ice or snow?? Or a proved 
K9AY or a DHDL??

 

Below is the almost good transcript of the original pdf Flag Theory, for the 
long answer.

 

 

73’s

JC

N4IS

 

Flag Theory
Dallas Lankford, 1/31/09, rev. 9/9/09 


The derivation which follows is a variation of Belrose's classical derivation 
for ferrite rod loop antennas,
“Ferromagnetic Loop Aerials,” Wireless Engineer, February 1955, 41– 46.


Some people who have not actually compared the signal output of a flag antenna 
to other small antennas have expressed their opinions to me that the signal 
output of a flag antenna has great attenuation compared to those other small 
antennas, such as loops and passive verticals. Their opinions are wrong. One 
should never express opinions which are based, say, on computer simulations 
alone, without actual measurements. The development below is based on physics 
(including Maxwell's equations), mathematics, and measurements.


Measurements have confirmed that the flag signal to noise formula derived below 
is approximately correct despite EZNEC simulations to the contrary. For 
example, EZNEC simulation of a 15' square loop at 1 MHz predicts its gain is 
about +4 dbi, while on the other hand EZNEC simulation of a 15' square flag at 
1 MHz predicts its gain is about –46 dBi. But if you construct such a loop and 
such a flag and observe the signal strengths produced by them for daytime 
groundwave MW signals, you will find that the maximum loop and flag signal 
outputs are about equal. Although somewhat more difficult to judge, the 
nighttime sky wave MW signals are also about equal.


Also, the signal to noise ratio formula below for flag arrays has been verified 
by manmade noise measurements in the 160 meter band using a smaller flag array 
than the MW flag array discussed below. Several years ago a similar signal to 
noise ratio formula for small un-tuned (broadband) loop antennas was verified 
at the low end of the NDB band.


The signal voltage es in volts for a one turn loop of area A in meters and a 
signal of wavelength λ for a given radio wave is

 

es = [2πA Es /λ] COS(θ) 

 

where Es is the signal strength in volts per meter and θ is the angle between 
the plane of the loop and the radio wave. It is well known that if an 
omnidirectional antenna, say a short whip, is attached to one of the output 
terminals of the loop and the phase difference between the loop and vertical 
and the amplitude of the whip are adjusted to produce a cardioid patten, then 
this occurs for a phase difference of 90 degrees and a whip amplitude equal to 
the amplitude of the loop, and the signal voltage in this case is 

 

es = [2πA Es /λ] [1 + COS(θ)] 

.
Notice that the maximum signal voltage of the cardioid antenna is twice the 
maximum signal voltage of the loop (or vertical) alone. 

A flag antenna is a one turn loop antenna with a resistance of several hundred 
ohms inserted at some point into the one turn. With a rectangular turn, with 
the resistor appropriately placed and adjusted for the appropriate value, the 
flag antenna will generate a cardioid pattern. The exact mechanism by which 
this occurs is not given here. Nevertheless, based on measurements, the flag  
antenna signal voltage is approximately the same as the cardioid pattern given 
above. The difference between an actual flag and the cardioid pattern above is 
that an actual flag pattern is not a perfect cardioid for some cardioid 
geometries and resistors. 

 

In general a flag pattern will be 

es = [2πA Es /λ] [1 + kCOS(θ)] 

 

where k is a constant less than or e

[kwin] [Bug 460594] Plasma freeze happening since 5.26.0 update

2022-12-14 Thread JC
https://bugs.kde.org/show_bug.cgi?id=460594

--- Comment #37 from JC  ---
I updated my system to kde-frameworks v5.101.0 and kde-plasma (including kwin)
v5.26.4. After 4 days, my system seems to be operating normally again.

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

[Discuss] Suggestions for a new server machine

2022-12-09 Thread jc
Oops; I forgot to edit the subject of my question ;-)
Maybe this one will work better.

| Hi, folks.  My home linux server has been  acting  up,  and
| after  14  years,  it may not be long for this world.  So I
| thought  I'd  ask  y'all  what  you  might  suggest  as   a
| replacement.
...


--
--
   _'
   O
 <:#/>  John Chambers
   +   
  /#\  
  |.|.

___
Discuss mailing list
Discuss@lists.blu.org
http://lists.blu.org/mailman/listinfo/discuss


Re: [Discuss] rsync issue

2022-12-09 Thread jc
Hi, folks.  My home linux server has been  acting  up,  and
after  14  years,  it may not be long for this world.  So I
thought  I'd  ask  y'all  what  you  might  suggest  as   a
replacement.

I got the current one from the PCs For Everyone people, who
aren't  in  business  any  more.  Their "farewell" web site
suggests people go to thinkmake.com.   But  you  may  think
otherwise.  Buying locally has its benefits, though I don't
think I ever actually needed them for anything after taking
the old one home.

Shelley has been getting into IoT lately, so it'd  be  good
to  find  one that's good at talking via wifi to a flock of
little gadgets.  I've mostly stuck with web-site stuff, and
keeping a good wired connection has been useful at times.

But let me know your thoughts ...



--
--
   _'
   O
 <:#/>  John Chambers
   +   
  /#\  
  |.|.

___
Discuss mailing list
Discuss@lists.blu.org
http://lists.blu.org/mailman/listinfo/discuss


[chrono] Change world coordinate up direction?

2022-11-25 Thread 'JC Denton' via ProjectChrono
Wondering if its easy to change the world up direction to Y up? And if so, 
where would this be done?

If its going to be more trouble than its worth, I'll just stick with Z up 
and rotate my outputs when I visualize it. 

Thanks!

-- 
You received this message because you are subscribed to the Google Groups 
"ProjectChrono" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to projectchrono+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/projectchrono/ffba57cd-5fa5-4af6-aea1-449061275236n%40googlegroups.com.


[kwin] [Bug 460594] Plasma freeze happening since 5.26.0 update

2022-11-22 Thread JC
https://bugs.kde.org/show_bug.cgi?id=460594

--- Comment #34 from JC  ---
(In reply to jcfisher from comment #33)
> Could this possibly be related or the same issue as
> https://bugs.kde.org/show_bug.cgi?id=457847? The symptoms seem similar if
> not identical.

Not sure, they mention having black rectangles. In my case I can see the
content of all the windows, in fact I see all windows from all desktops, but no
black rectangles.

I've been trying to isolate the cause but so far no luck. Sometimes it happens
when I get a notification, other times it happens when I switch windows with
alt+tab and once it happened just by using the open file dialog (which shows a
pop-up with the possible file names).

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

[kwin] [Bug 460594] Plasma freeze happening since 5.26.0 update

2022-11-19 Thread JC
https://bugs.kde.org/show_bug.cgi?id=460594

--- Comment #32 from JC  ---
(In reply to JC from comment #31)
> My experience is similar to what Ricardo reported but my setup is slightly
> different. This started happening around the upgrade to KWin 2.26.0:

I meant KDE Plasma 5.26.0

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

[kwin] [Bug 460594] Plasma freeze happening since 5.26.0 update

2022-11-19 Thread JC
https://bugs.kde.org/show_bug.cgi?id=460594

--- Comment #31 from JC  ---
(In reply to Ricardo J. Barberis from comment #28)

My experience is similar to what Ricardo reported but my setup is slightly
different. This started happening around the upgrade to KWin 2.26.0:

Operating System: Gentoo Linux 2.9
KDE Plasma Version: 5.26.3
KDE Frameworks Version: 5.100.0
Qt Version: 5.15.5
Kernel Version: 5.19.8-gentoo (64-bit)
Graphics Platform: X11
Processors: 12 × Intel® Core™ i7-8086K CPU @ 4.00GHz
Memory: 31.2 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 630

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

[kwin] [Bug 460594] Plasma freeze happening since 5.26.0 update

2022-11-19 Thread JC
https://bugs.kde.org/show_bug.cgi?id=460594

JC  changed:

   What|Removed |Added

 CC||mg05182-...@yahoo.ca

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

Topband: FW: Band conditions

2022-11-16 Thread JC
One common misunderstanding is that propagation on low bands is bad when
high bands are good. When solar activity is high, the solar flux increase
and allows F2 reflection on the high bands , 15.12 and 10m. The MUF is way
up. However for 1.8 or 3.5 MHz the MUF is always good, and the reflection is
on lower layers F / E, at night F1 and E become almost one layer.

So.. 160m is open every night, it does not depend on the MUF. What change is
the large number of Es clouds the create duct, most common on solar maximum.
Also long path is more friendly when the path cross the magnetic equator.
Spot light is very defined during solar maximum.

That makes propagation on 160m, very interesting with long ducts and spot
light. If both station does not call CQ they never going to figure it out.
Signals can be very strong on both side of the path.

Larry web page K9LA has a fantastic book from NM7M's book titled "The Big
Gun's Guide to Low-Band Propagation" is in the 160m link.

The propagation on solar maximum is just different from solar minimum.

73's
JC
N4IS

_
Searchable Archives: http://www.contesting.com/_topband - Topband Reflector


Re: [jdev] Announcing the release of python-omemo, with support for the new SCE-based OMEMO

2022-11-13 Thread JC Brand
Congratulations Tim! And thanks for contributing to the diversity of libraries 
in our little ecosystem.


On November 11, 2022 3:49:17 PM GMT+01:00, Tim Henkes  wrote:
>After years of development I am stoked to announce the release of
>python-omemo - An open Python implementation of the OMEMO Multi-End
>Message and Object Encryption protocol!
>
>
>python-omemo [1] is an OMEMO implementation written from scratch with
>support for both the currently widespread eu.siacs.conversations.axolotl
>version of OMEMO [2] and the newest, SCE-based version under the
>urn:xmpp:omemo:2 namespace [3].
>
>
>Notably, python-omemo is an implementation of the OMEMO _protocol_ and
>not just the cryptographic primitives, which means that many of the
>small protocol flow details of the OMEMO specification are handled by
>python-omemo as well.
>
>
>Key properties of the library:
>
>- Seamless support for both versions of the OMEMO specification at the
>same time. The library transparently handles compatibility between the
>two versions, i.e. identity keys, device ids and trust are shared
>appropriately. The protocol version to encrypt a message with can either
>be selected explicitly, or given as a priority, to e.g. use the new
>OMEMO if available, and fall back to the old OMEMO if not.
>
>- Handles bundle and device list, making sure the published data is
>always in sync with the local data.
>
>- Handles small protocol flow details, like sending automated empty
>messages in response to a key exchange or to prevent staleness.
>
>- Provides an easy way to integrate any sort of trust system - be it
>simple manual trust, BTBV, TOFU or something more complex.
>
>- Thin and straight-forward public API - OMEMO doesn't have to be
>complicated :)
>
>- Optionally reads/verifies and builds ElementTree XML structures for
>you, so that you can keep your codebase even thinner.
>
>- Clean, modern, fully-typed Python 3 with thorough API documentation.
>
>- Very easy to get started with - provide a simple key-value storage,
>implement some methods to upload/download bundles and device lists from
>PEP, and you're pretty much set!
>
>
>This library aims to enable client developers to equip their clients
>with OMEMO support without understanding all of the nasty cryptography
>or protocol flow details. Please give it a look, send me feedback and
>consider it for your Python-based client :)
>
>
>[1]: https://github.com/Syndace/python-omemo
>
>[2]: https://xmpp.org/extensions/attic/xep-0384-0.3.0.html
>
>[3]: https://xmpp.org/extensions/xep-0384.html
>
>
>___
>JDev mailing list
>Info: https://mail.jabber.org/mailman/listinfo/jdev
>Unsubscribe: jdev-unsubscr...@jabber.org
>___
___
JDev mailing list
Info: https://mail.jabber.org/mailman/listinfo/jdev
Unsubscribe: jdev-unsubscr...@jabber.org
___


Re: [edk2-devel] 回复: [PATCH v3 1/1] MdePkg/BaseLib: Fix out-of-bounds reads in SafeString

2022-11-07 Thread JC
Hi Pedro, this is just a test email

Thanks,
JC


-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#96032): https://edk2.groups.io/g/devel/message/96032
Mute This Topic: https://groups.io/mt/94861914/21656
Group Owner: devel+ow...@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-




Re: [edk2-devel] 回复: [PATCH v3 1/1] MdePkg/BaseLib: Fix out-of-bounds reads in SafeString

2022-11-07 Thread JC
test mail

On Mon, Nov 7, 2022 at 9:14 AM Pedro Falcato 
wrote:

> Thanks!
>
> On Mon, 7 Nov 2022, 01:32 gaoliming via groups.io,  byosoft.com...@groups.io> wrote:
>
>> Create https://github.com/tianocore/edk2/pull/3604 to merge this patch.
>>
>>
>>
>> Thanks
>>
>> Liming
>>
>> *发件人:* devel@edk2.groups.io  *代表 *Pedro Falcato
>> *发送时间:* 2022年11月5日 8:25
>> *收件人:* devel@edk2.groups.io; gaolim...@byosoft.com.cn
>> *抄送:* Vitaly Cheptsov ; Marvin Häuser <
>> mhaeu...@posteo.de>; Michael D Kinney ;
>> Zhiguang Liu ; Jiewen Yao 
>> *主题:* Re: [edk2-devel] 回复: [PATCH v3 1/1] MdePkg/BaseLib: Fix
>> out-of-bounds reads in SafeString
>>
>>
>>
>> Hi Liming,
>>
>>
>>
>> Thank you for the review. Can we please push this in time for the stable
>> tag?
>>
>>
>>
>> Thanks,
>>
>> Pedro
>>
>>
>>
>> On Fri, Nov 4, 2022 at 1:22 AM gaoliming via groups.io > byosoft.com...@groups.io> wrote:
>>
>> Reviewed-by: Liming Gao 
>>
>> > -邮件原件-
>> > 发件人: Pedro Falcato 
>> > 发送时间: 2022年11月3日 9:12
>> > 收件人: devel@edk2.groups.io
>> > 抄送: Pedro Falcato ; Vitaly Cheptsov
>> > ; Marvin Häuser ;
>> > Michael D Kinney ; Liming Gao
>> > ; Zhiguang Liu ;
>> Jiewen
>> > Yao 
>> > 主题: [PATCH v3 1/1] MdePkg/BaseLib: Fix out-of-bounds reads in
>> SafeString
>> >
>> > There was a OOB access in *StrHexTo* functions, when passed strings like
>> > "XDEADBEEF".
>> >
>> > OpenCore folks established an ASAN-equipped project to fuzz Ext4Dxe,
>> > which was able to catch these (mostly harmless) issues.
>> >
>> > Cc: Vitaly Cheptsov 
>> > Cc: Marvin Häuser 
>> > Cc: Michael D Kinney 
>> > Cc: Liming Gao 
>> > Cc: Zhiguang Liu 
>> > Signed-off-by: Pedro Falcato 
>> > Acked-by: Michael D Kinney 
>> > Reviewed-by: Jiewen Yao 
>> > ---
>> >  MdePkg/Library/BaseLib/SafeString.c | 25 +
>> >  1 file changed, 21 insertions(+), 4 deletions(-)
>> >
>> > diff --git a/MdePkg/Library/BaseLib/SafeString.c
>> > b/MdePkg/Library/BaseLib/SafeString.c
>> > index f338a32a3a41..b75b33381732 100644
>> > --- a/MdePkg/Library/BaseLib/SafeString.c
>> > +++ b/MdePkg/Library/BaseLib/SafeString.c
>> > @@ -863,6 +863,9 @@ StrHexToUintnS (
>> >OUT   UINTN   *Data
>> >)
>> >  {
>> > +  BOOLEAN  FoundLeadingZero;
>> > +
>> > +  FoundLeadingZero = FALSE;
>> >ASSERT (((UINTN)String & BIT0) == 0);
>> >
>> >//
>> > @@ -892,12 +895,14 @@ StrHexToUintnS (
>> >//
>> >// Ignore leading Zeros after the spaces
>> >//
>> > +
>> > +  FoundLeadingZero = *String == L'0';
>> >while (*String == L'0') {
>> >  String++;
>> >}
>> >
>> >if (CharToUpper (*String) == L'X') {
>> > -if (*(String - 1) != L'0') {
>> > +if (!FoundLeadingZero) {
>> >*Data = 0;
>> >return RETURN_SUCCESS;
>> >  }
>> > @@ -992,6 +997,9 @@ StrHexToUint64S (
>> >OUT   UINT64  *Data
>> >)
>> >  {
>> > +  BOOLEAN  FoundLeadingZero;
>> > +
>> > +  FoundLeadingZero = FALSE;
>> >ASSERT (((UINTN)String & BIT0) == 0);
>> >
>> >//
>> > @@ -1021,12 +1029,13 @@ StrHexToUint64S (
>> >//
>> >// Ignore leading Zeros after the spaces
>> >//
>> > +  FoundLeadingZero = *String == L'0';
>> >while (*String == L'0') {
>> >  String++;
>> >}
>> >
>> >if (CharToUpper (*String) == L'X') {
>> > -if (*(String - 1) != L'0') {
>> > +if (!FoundLeadingZero) {
>> >*Data = 0;
>> >return RETURN_SUCCESS;
>> >  }
>> > @@ -2393,6 +2402,9 @@ AsciiStrHexToUintnS (
>> >OUT   UINTN  *Data
>> >)
>> >  {
>> > +  BOOLEAN  FoundLeadingZero;
>> > +
>> > +  FoundLeadingZero = FALSE;
>> >//
>> >// 1. Neither String nor Data shall be a null pointer.
>> >//
>> > @@ -2420,12 +2432,13 @@ AsciiStrHexToUintnS (
>> >//
>> >// Ignore leading Zeros after the spaces
>> >//
>> > +  FoundLeadingZero = *String == '0';
>> >while (*String == '0') {
>> >  String++;
>> >}
>> >
>> >if (AsciiCharToUpper (*String) == 'X') {
>> > -if (*(String - 1) != '0') {
>> > +if (!FoundLeadingZero) {
>> >*Data = 0;
>> >return RETURN_SUCCESS;
>> >  }
>> > @@ -2517,6 +2530,9 @@ AsciiStrHexToUint64S (
>> >OUT   UINT64  *Data
>> >)
>> >  {
>> > +  BOOLEAN  FoundLeadingZero;
>> > +
>> > +  FoundLeadingZero = FALSE;
>> >//
>> >// 1. Neither String nor Data shall be a null pointer.
>> >//
>> > @@ -2544,12 +2560,13 @@ AsciiStrHexToUint64S (
>> >//
>> >// Ignore leading Zeros after the spaces
>> >//
>> > +  FoundLeadingZero = *String == '0';
>> >while (*String == '0') {
>> >  String++;
>> >}
>> >
>> >if (AsciiCharToUpper (*String) == 'X') {
>> > -if (*(String - 1) != '0') {
>> > +if (!FoundLeadingZero) {
>> >*Data = 0;
>> >return RETURN_SUCCESS;
>> >  }
>> > --
>> > 2.38.1
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> --
>>
>> Pedro Falcato
>>
>> 
>
>


-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#96031): 

[kwin] [Bug 438883] Re-implement Desktop Cube effect with modern effects API

2022-09-01 Thread JC Casiano
https://bugs.kde.org/show_bug.cgi?id=438883

JC Casiano  changed:

   What|Removed |Added

 CC||j...@seanet.com

--- Comment #47 from JC Casiano  ---
Please bring back the Cube, the Fade and Slide effects don't even compare.  It
was odd hearing my friend even mention it and express his disappointment the
other day.  I was surprised he even noticed my Linux effects, and he thought it
was one of the coolest effects that he couldn't get on Windows.

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

Tokina AT-X SP 60-120mm F2.8 manual focus Super-Portrait lens

2022-08-17 Thread JC OConnell
Just got ahold of my second copy of subject lens
(yes, its so good, I wanted a spare). They are
hard to find in a PENTAX PK mount. Recently one showed
up on ebay BIN for 200 pounds in LN condition
so I grabbed it. When I bought my first one twenty years
ago, I found the zoom range ideal for people shots
of all types on film. Seems even better with the digital
K-1

heres a simple sample nature photo showing the incredible resolution
for a zoom https://www.jchriso.com/temp/tree.jpg ( resized for web )
this is the same photo but shows a 100% mag crop
of the center of the image https://www.jchriso.com/temp/treecrop.jpg



--
%(real_name)s Pentax-Discuss Mail List
To unsubscribe send an email to pdml-le...@pdml.net
to UNSUBSCRIBE from the PDML, please visit the link directly above and follow 
the directions.


[time-nuts] Re: GPS failed

2022-07-11 Thread JC via time-nuts
Google 'GPS testing notices'


On Mon, Jul 11, 2022 at 1:15 PM jeanmichel.friedt--- via time-nuts <
time-nuts@lists.febo.com> wrote:

> for what it's worth ... the UK gov. is nice enough to warn about GPS
> jamming
> exercises
> https://www.ofcom.org.uk/spectrum/information/gps-jamming-exercises
> not sure about the US of A announcements on such activities. At least in
> France
> I have never seen such warnings.
>
> Best, JM
>
> --
> JM Friedt, FEMTO-ST Time & Frequency, 26 rue de l'Epitaphe, 25000
> Besancon, France
>
> July 11, 2022 7:42 PM, "Bob kb8tq via time-nuts" 
> wrote:
>
> > Hi
> >
> > Are all the receivers the same type / model? If so what are they?
> Various
> > receivers made over the last 20 years have some “issues” that can pop
> up.
> >
> > Is the antenna gain properly matched to the needs of the receiver? Some
> > are designed for a “target gain” of 20 db, others 30, some 50. Match a
> > 20 db receiver with a 50 db antenna …. you have issues.
> >
> > Are all the hilltops in common view of each other? Somebody jamming their
> > ankle bracelet could be the simple answer if they are ….
> >
> > Just what overloads this or that receiver often is a bit obscure. Most
> are pretty
> > good at taking out CW tones. It often takes something a bit more complex
> > to drive them insane. This makes testing a bit exciting.
> >
> > Lots of strange and weird possibilities.
> >
> > Bob
> >
> >> On Jul 10, 2022, at 3:19 PM, skipp Isaham via time-nuts <
> time-nuts@lists.febo.com> wrote:
> >>
> >> Hello to the Group,
> >>
> >> I'd like to get some opinions and war stories regarding GPS reliability
> at
> >> high RF level and elevation locations.
> >>
> >> Background: Three different hill-top GPS receivers, all different
> types, using
> >> different antennas mounted on an outside fixiture, plain view of the
> open sky,
> >> all stopped working.
> >>
> >> Test antennas were brought in and placed on a fixture well away from the
> >> original antennas, the recevers went back in to capture and lock.
> >>
> >> From what I understand, the original antennas are what I would call
> straight
> >> preamp with no pre-selection / filtering.
> >>
> >> The ordered and now inbound replacements are said to contain a SAW
> filter
> >> system. It is the intent of the client to just place these "improved
> antennas" in
> >> to service and get on with life.
> >>
> >> I would suspect a GPS antenna (and receiver) could be subject to RF
> overload
> >> or blocking, however, we're assuming nothing major has changed at the
> site, nor
> >> any nearby location. One might think there are more GPS receivers being
> pushed
> >> out of reliable operation by the world around them, I'm just not
> hearing those stories
> >> from a lot of people using them (GPS receivers).
> >>
> >> Any new install GPS receiver antenna ordered will/should contain some
> pre-selection
> >> to potentially avoid a problem, even some years down the road? Seems
> like that's
> >> where things are going... no more off the shelf, wide band, (hot)
> preamplified GPS antennas
> >> in busy locations?
> >>
> >> Thank you in advance for any related comments and/or opions ...
> >>
> >> cheers,
> >>
> >> skipp
> >>
> >> skipp025 at jah who dot calm
> >> ___
> >> time-nuts mailing list -- time-nuts@lists.febo.com
> >> To unsubscribe send an email to time-nuts-le...@lists.febo.com
> >
> > ___
> > time-nuts mailing list -- time-nuts@lists.febo.com
> > To unsubscribe send an email to time-nuts-le...@lists.febo.com
> ___
> time-nuts mailing list -- time-nuts@lists.febo.com
> To unsubscribe send an email to time-nuts-le...@lists.febo.com
___
time-nuts mailing list -- time-nuts@lists.febo.com
To unsubscribe send an email to time-nuts-le...@lists.febo.com

Re: sample photos. - smc pentax A 100mm F2.8 MACRO at middle distances w/K-1

2022-06-17 Thread JC OConnell
didnt Pentax super multicoat all air glass surfaces starting back in the
early 70's. including rear elements?
jco
-Original Message-
From: Pentax-Discuss Mail List 
Sent: Jun 17, 2022 11:37 AM
To: 
Subject: Re: sample photos. - smc pentax A 100mm F2.8 MACRO at middle distances 
w/K-1
 
On 6/16/2022 10:17 PM, Alan C wrote:
> The problem is related to lack of Multi-coating on the rear element > which 
> was absent on pre-digital lenses. More commonly this gives rise > to ghosting 
> (back-and-forth reflections) when these old lenses are > used on digital 
> camera because the sensors are much more reflective > than film. The 
> difference between the Sigma 170-500 APO & the later DG > version is 
> indicative.
>
I suspect that is a possibility, I suspect the "multicoated" lenses of the day 
may not have been as multicoated on the rear element. I use quite a few legacy 
glass and the A100/2.8 macro is the only one I've noticed hot spots on, which 
is why I thought it might be related to the FREE design and the flat rear 
element.
 
Anyway, according to John, the problem doesn't exist, so it's all good.
 
bill
--
%(real_name)s Pentax-Discuss Mail List
To unsubscribe send an email to pdml-le...@pdml.net
to UNSUBSCRIBE from the PDML, please visit the link directly above and follow 
the directions.

 
--
%(real_name)s Pentax-Discuss Mail List
To unsubscribe send an email to pdml-le...@pdml.net
to UNSUBSCRIBE from the PDML, please visit the link directly above and follow 
the directions.

Re: sample photos. - smc pentax A 100mm F2.8 MACRO at middle distances w/K-1

2022-06-17 Thread JC OConnell
I didnt state the problem didnt exist. I stated I hadnt seen the problem YET.
-Original Message-
From: Pentax-Discuss Mail List 
Sent: Jun 17, 2022 11:37 AM
To: 
Subject: Re: sample photos. - smc pentax A 100mm F2.8 MACRO at middle distances 
w/K-1
 
On 6/16/2022 10:17 PM, Alan C wrote:
> The problem is related to lack of Multi-coating on the rear element > which 
> was absent on pre-digital lenses. More commonly this gives rise > to ghosting 
> (back-and-forth reflections) when these old lenses are > used on digital 
> camera because the sensors are much more reflective > than film. The 
> difference between the Sigma 170-500 APO & the later DG > version is 
> indicative.
>
I suspect that is a possibility, I suspect the "multicoated" lenses of the day 
may not have been as multicoated on the rear element. I use quite a few legacy 
glass and the A100/2.8 macro is the only one I've noticed hot spots on, which 
is why I thought it might be related to the FREE design and the flat rear 
element.
 
Anyway, according to John, the problem doesn't exist, so it's all good.
 
bill
--
%(real_name)s Pentax-Discuss Mail List
To unsubscribe send an email to pdml-le...@pdml.net
to UNSUBSCRIBE from the PDML, please visit the link directly above and follow 
the directions.

 
--
%(real_name)s Pentax-Discuss Mail List
To unsubscribe send an email to pdml-le...@pdml.net
to UNSUBSCRIBE from the PDML, please visit the link directly above and follow 
the directions.

Re: sample photos. - smc pentax A 100mm F2.8 MACRO at middle distances w/K-1

2022-06-16 Thread JC OConnell
the lens is not "quite prone" to hot spots w/ K-1.; I havent seen any yet. 
Maybe under certain rare conditions. Secondly an AF lens is not as good
or better than a MF lens, its just different. 
jco

-Original Message-
From: Pentax-Discuss Mail List 
Sent: Jun 16, 2022 10:29 AM
To: 
Subject: Re: sample photos. - smc pentax A 100mm F2.8 MACRO at middle distances 
w/K-1
 
On 6/15/2022 4:56 PM, JC OConnell wrote:
> https://jchriso.com/temp/smc100.htm
> > This is a great all around lens.
> The A100/2.8 was a great lens, but it is quite prone to reflections off the 
> sensor giving hot spots on the image. I suspect it is related to the FREE 
> design and the absolutely flat rear element.
It's too bad because it was such a good lens on film.
I ended up retiring my copy of it in favour of the DFA100/2.8 Macro, which is 
easily as good a lens and shows none of the reflection problems. I'd sell it 
but my conscience won't let me sell a known defect such as this.
 
--
%(real_name)s Pentax-Discuss Mail List
To unsubscribe send an email to pdml-le...@pdml.net
to UNSUBSCRIBE from the PDML, please visit the link directly above and follow 
the directions.

 
--
%(real_name)s Pentax-Discuss Mail List
To unsubscribe send an email to pdml-le...@pdml.net
to UNSUBSCRIBE from the PDML, please visit the link directly above and follow 
the directions.

Re: sample photos. - smc pentax A 100mm F2.8 MACRO at middle distances w/K-1

2022-06-16 Thread JC OConnell
there was a stray leaf in the image i used the smudge tool to cover it up 
rather crudely-
-Original Message-
From: Pentax-Discuss Mail List 
Sent: Jun 16, 2022 2:25 AM
To: Pentax-Discuss Mail List 
Subject: Re: sample photos. - smc pentax A 100mm F2.8 MACRO at middle distances 
w/K-1
 
What are the things that look like water smears on a print, on the 
chalk-on-the-ground picture?
 
> On 15 June 2022 at 23:56 JC OConnell wrote:
>
>
> https://jchriso.com/temp/smc100.htm
>  
> This is a great all around lens.
--
%(real_name)s Pentax-Discuss Mail List
To unsubscribe send an email to pdml-le...@pdml.net
to UNSUBSCRIBE from the PDML, please visit the link directly above and follow 
the directions.

 
--
%(real_name)s Pentax-Discuss Mail List
To unsubscribe send an email to pdml-le...@pdml.net
to UNSUBSCRIBE from the PDML, please visit the link directly above and follow 
the directions.

Re: sample photos. - smc pentax A 100mm F2.8 MACRO at middle distances w/K-1

2022-06-16 Thread JC OConnell
for APSC BODIES I usually prefer the A50/2.8 Macro
jco
-Original Message-
From: Pentax-Discuss Mail List 
Sent: Jun 16, 2022 1:08 AM
To: 
Subject: Re: sample photos. - smc pentax A 100mm F2.8 MACRO at middle distances 
w/K-1
 
Agree. I still have my FA 100/2.8 which has the same formula but I find it a 
trifle on the long side with an APS-C sensor.
 
Alan C
 
On 16-Jun-22 04:49 AM, JC OConnell wrote:
> for portraits I use a k  85/1.8 or my outstanding Tokina ATX 60-120/2.8 zoom
> > Message-
> From: Pentax-Discuss Mail List
> Sent: Jun 15, 2022 9:50 PM
> To:
> Subject: Re: sample photos. - smc pentax A 100mm F2.8 MACRO at middle 
> distances w/K-1
> > Back in film days it was my favorite portrait lens.
> > I still used it for such with the APS-C Pentax digitals and only recently 
> > switched over to the SMC Pentax-D FA 100mm F2.8 Macro WR (ran across a 
> > price so good on-line that I couldn't refuse) ... but I still have the A 
> > 100mm F2.8 MACRO for backup.
> > On 6/15/2022 6:56 PM, JC OConnell wrote:
>> https://jchriso.com/temp/smc100.htm
>>> This is a great all around lens.
>>> jco
>> --
>> %(real_name)s Pentax-Discuss Mail List
>> To unsubscribe send an email to pdml-le...@pdml.net
>> to UNSUBSCRIBE from the PDML, please visit the link directly above and 
>> follow the directions.
> > --
> Vivere in aeternum aut mori conatur
> > --
> This email has been checked for viruses by AVG.
> https://www.avg.com
> --
> %(real_name)s Pentax-Discuss Mail List
> To unsubscribe send an email to pdml-le...@pdml.net
> to UNSUBSCRIBE from the PDML, please visit the link directly above and follow 
> the directions.
>
> > --
> %(real_name)s Pentax-Discuss Mail List
> To unsubscribe send an email to pdml-le...@pdml.net
> to UNSUBSCRIBE from the PDML, please visit the link directly above and follow 
> the directions.
--
%(real_name)s Pentax-Discuss Mail List
To unsubscribe send an email to pdml-le...@pdml.net
to UNSUBSCRIBE from the PDML, please visit the link directly above and follow 
the directions.

 
--
%(real_name)s Pentax-Discuss Mail List
To unsubscribe send an email to pdml-le...@pdml.net
to UNSUBSCRIBE from the PDML, please visit the link directly above and follow 
the directions.

Re: sample photos. - smc pentax A 100mm F2.8 MACRO at middle distances w/K-1

2022-06-15 Thread JC OConnell
for portraits I use a k  85/1.8 or my outstanding Tokina ATX 60-120/2.8 zoom
 
Message-
From: Pentax-Discuss Mail List 
Sent: Jun 15, 2022 9:50 PM
To: 
Subject: Re: sample photos. - smc pentax A 100mm F2.8 MACRO at middle distances 
w/K-1
 
Back in film days it was my favorite portrait lens.
 
I still used it for such with the APS-C Pentax digitals and only recently 
switched over to the SMC Pentax-D FA 100mm F2.8 Macro WR (ran across a price so 
good on-line that I couldn't refuse) ... but I still have the A 100mm F2.8 
MACRO for backup.
 
On 6/15/2022 6:56 PM, JC OConnell wrote:
> https://jchriso.com/temp/smc100.htm
> > This is a great all around lens.
> > jco
> --
> %(real_name)s Pentax-Discuss Mail List
> To unsubscribe send an email to pdml-le...@pdml.net
> to UNSUBSCRIBE from the PDML, please visit the link directly above and follow 
> the directions.
 
--
Vivere in aeternum aut mori conatur
 
--
This email has been checked for viruses by AVG.
https://www.avg.com
--
%(real_name)s Pentax-Discuss Mail List
To unsubscribe send an email to pdml-le...@pdml.net
to UNSUBSCRIBE from the PDML, please visit the link directly above and follow 
the directions.

 
--
%(real_name)s Pentax-Discuss Mail List
To unsubscribe send an email to pdml-le...@pdml.net
to UNSUBSCRIBE from the PDML, please visit the link directly above and follow 
the directions.

sample photos. - smc pentax A 100mm F2.8 MACRO at middle distances w/K-1

2022-06-15 Thread JC OConnell
https://jchriso.com/temp/smc100.htm
 
This is a great all around lens.
 
jco
--
%(real_name)s Pentax-Discuss Mail List
To unsubscribe send an email to pdml-le...@pdml.net
to UNSUBSCRIBE from the PDML, please visit the link directly above and follow 
the directions.

Re: [Standards] [XEP-0424] (Message Retraction) How to handle "removing fastening"?

2022-06-11 Thread JC Brand
Yes I think it should just be ignored, but I guess this is another example of 
how fastenings were created with a different usecase in mind and aren't 
necessary or relevant to retractions.

I'll try to update the XEP soon to remove them.



On June 10, 2022 5:00:18 PM GMT+02:00, Goffi  wrote:
>Hi,
>
>I'm implemeting XEP-0424 (Message Retraction) and I'm wondering how I'm 
>supposed to act when I receive a fastening removal (as in 
>https://xmpp.org/extensions/xep-0422.html#remove) on a retracted message?
>Am I supposed to restore the message (meaning that I would somehow archive 
>it), or to ignore the removal request?
>I guess the latter would make more sense (it's simpler to send a new identical 
>message than to keep an archive of supposedly removed message), but it would 
>make sense to indicate that in business rules.
>Also should I notice the sender/receiver when a removal is rejected?
>
>As a side note, the XEP is still flagged as "last call" but the call has been 
>vetoed, thus the XEP should be updated accordingly.
>
>Thanks
>Goffi
>
>
>___
>Standards mailing list
>Info: https://mail.jabber.org/mailman/listinfo/standards
>Unsubscribe: standards-unsubscr...@xmpp.org
>___
___
Standards mailing list
Info: https://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: standards-unsubscr...@xmpp.org
___


[krita] [Bug 454750] Fresh Fedora install, Krita doesn't load project

2022-06-02 Thread JC
https://bugs.kde.org/show_bug.cgi?id=454750

JC  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |WORKSFORME

--- Comment #3 from JC  ---
(In reply to Halla Rempt from comment #2)
> I'm pretty sure that's a wayland and/or nvidia driver problem... Please try
> the appimage and see whether that works, or whether a plain X11 session
> works.

Damn you're right. I tried the appimage first and Krita was throwing "not
responding". I then uninstalled the nvidia drivers and krita loads projetcs
properly. 

I had the 510.68.02 drivers but now my PC runs like garbage lmao, I'll try
other nvidia drivers see if one works with Krita.

Thanks kind stranger!

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

[krita] [Bug 454750] Fresh Fedora install, Krita doesn't load project

2022-06-02 Thread JC
https://bugs.kde.org/show_bug.cgi?id=454750

--- Comment #1 from JC  ---
Here are the logs inside Krita (right after recording the video) : 

Krita

 Version: 5.0.0
 Languages: en_CA, en
 Hidpi: true

Qt

  Version (compiled): 5.15.2
  Version (loaded): 5.15.3

OS Information

  Build ABI: x86_64-little_endian-lp64
  Build CPU: x86_64
  CPU: x86_64
  Kernel Type: linux
  Kernel Version: 5.17.11-300.fc36.x86_64
  Pretty Productname: Fedora Linux 36 (Workstation Edition)
  Product Type: fedora
  Product Version: 36
  Desktop: GNOME

OpenGL Info

  Vendor:  "NVIDIA Corporation" 
  Renderer:  "NVIDIA GeForce GTX 1080 Ti/PCIe/SSE2" 
  Version:  "4.6.0 NVIDIA 510.68.02" 
  Shading language:  "4.60 NVIDIA" 
  Requested format:  QSurfaceFormat(version 3.0, options
QFlags(DeprecatedFunctions), depthBufferSize 24,
redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8,
stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer,
swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile 
QSurfaceFormat::CompatibilityProfile) 
  Current format:  QSurfaceFormat(version 4.6, options
QFlags(DeprecatedFunctions), depthBufferSize 0,
redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8,
stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer,
swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile 
QSurfaceFormat::CompatibilityProfile) 
 Version: 4.6
 Supports deprecated functions true 
 is OpenGL ES: false 
  supportsBufferMapping: true 
  supportsBufferInvalidation: true 
  Extensions: 
 "GL_EXT_draw_range_elements" 
 "GL_EXT_blend_minmax" 
 "GL_ARB_texture_mirrored_repeat" 
 "GL_NV_viewport_array2" 
 "GL_ARB_draw_buffers_blend" 
 "GL_ARB_tessellation_shader" 
 "GL_EXT_memory_object_fd" 
 "GL_ATI_texture_float" 
 "GL_NV_occlusion_query" 
 "GL_ARB_depth_clamp" 
 "GL_ARB_multitexture" 
 "GL_ARB_blend_func_extended" 
 "GL_ARB_texture_buffer_range" 
 "GL_ARB_texture_compression_rgtc" 
 "GL_ARB_texture_cube_map" 
 "GL_EXT_texture_shared_exponent" 
 "GL_EXT_sparse_texture2" 
 "GL_ARB_seamless_cubemap_per_texture" 
 "GL_ARB_sparse_texture" 
 "GL_ARB_vertex_array_bgra" 
 "GL_EXT_texture_compression_rgtc" 
 "GL_EXT_blend_color" 
 "GL_ARB_shader_clock" 
 "GL_NV_explicit_multisample" 
 "GL_NV_fragment_program2" 
 "GL_NV_framebuffer_multisample_coverage" 
 "GL_ARB_texture_float" 
 "GL_NV_texture_rectangle_compressed" 
 "GL_NV_fragment_shader_interlock" 
 "GL_KHR_robustness" 
 "GL_NV_fog_distance" 
 "GL_ARB_transform_feedback2" 
 "GL_KHR_no_error" 
 "GL_EXT_framebuffer_sRGB" 
 "GL_EXT_texture_env_add" 
 "GL_NV_conservative_raster_dilate" 
 "GL_ARB_shader_bit_encoding" 
 "GL_NV_timeline_semaphore" 
 "GL_ARB_sampler_objects" 
 "GL_ARB_texture_query_levels" 
 "GL_ARB_sample_shading" 
 "GL_NV_query_resource_tag" 
 "GL_EXT_geometry_shader4" 
 "GL_NV_blend_minmax_factor" 
 "GL_EXT_direct_state_access" 
 "GL_ARB_instanced_arrays" 
 "GL_ARB_multi_draw_indirect" 
 "GL_NV_register_combiners2" 
 "GL_ARB_ES2_compatibility" 
 "GL_ARB_point_parameters" 
 "GL_ARB_spirv_extensions" 
 "GL_ARB_imaging" 
 "GL_EXT_texture_integer" 
 "GL_EXT_texture_lod_bias" 
 "GL_NV_fragment_coverage_to_color" 
 "GL_NV_conservative_raster_pre_snap_triangles" 
 "GL_NV_vertex_program1_1" 
 "GL_ARB_sparse_texture_clamp" 
 "GL_NV_multisample_coverage" 
 "GL_EXT_import_sync_object" 
 "GL_NV_framebuffer_mixed_samples" 
 "GL_NV_shader_subgroup_partitioned" 
 "GL_ARB_texture_storage" 
 "GL_ARB_stencil_texturing" 
 "GL_EXT_texture_filter_anisotropic" 
 "GL_NV_texture_shader" 
 "GL_ARB_multisample" 
 "GL_SGIX_depth_texture" 
 "GL_EXT_separate_shader_objects" 
 "GL_NV_shader_atomic_counters" 
 "GL_ARB_multi_bind" 
 "GL_NV_shader_atomic_int64" 
 "GL_ARB_polygon_offset_clamp" 
 "GL_NV_texture_multisample" 
 "GL_EXT_multiview_timer_query" 
 "GL_ARB_draw_indirect" 
 "GL_NV_te

[krita] [Bug 454750] Fresh Fedora install, Krita doesn't load project

2022-06-02 Thread JC
https://bugs.kde.org/show_bug.cgi?id=454750

JC  changed:

   What|Removed |Added

  Component|* Unknown   |General

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

[krita] [Bug 454750] New: Fresh Fedora install, Krita doesn't load project

2022-06-02 Thread JC
https://bugs.kde.org/show_bug.cgi?id=454750

Bug ID: 454750
   Summary: Fresh Fedora install, Krita doesn't load project
   Product: krita
   Version: 5.0.0
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: critical
  Priority: NOR
 Component: * Unknown
  Assignee: krita-bugs-n...@kde.org
  Reporter: coltwest...@gmail.com
  Target Milestone: ---

Created attachment 149404
  --> https://bugs.kde.org/attachment.cgi?id=149404=edit
Krita Window after creating / opening a project

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


STEPS TO REPRODUCE
1. Open Krita
2. Start new project
3. Bam, problem ^

OBSERVED RESULT
The window where the Canvas should be is frozen, but the rest of the
application is clickable and select-able.

EXPECTED RESULT
Krita should open and show the Canvas

SOFTWARE/OS VERSIONS
Fedora 36 Workstation;
Gnome 42.1;
Wayland;

ADDITIONAL INFORMATION
Here is a video of the bug : https://streamable.com/98vo5q

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

[Kernel-packages] [Bug 1973482] Re: kernel 4.15.0.177 break everything on Dell XPS 15 9570

2022-05-17 Thread JC AGUILAR
Hello,
Same issue with a Dell Latitude 5580. Device detection like disks fail 
randomly. Built-in keyboard, touchpad and Wifi don't work.

Previous kernel build is fine.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1973482

Title:
  kernel 4.15.0.177 break everything on Dell XPS 15 9570

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  There are many issues including:

  - wireless card DISBLED / UNCLAIMED
  - no sound output device listed
  - strange electrical noise in the speakers when the cpu is under load
  - mounting /boot/efi hangs for 1m30
  - various services not starting (snap, etc)

  Rolling back to 4.15.0.176 fixes all the issues.

  Can you let me know which logs I could provide to help?

  Thank you

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-177-generic 4.15.0-177.186
  ProcVersionSignature: Ubuntu 4.15.0-177.186-generic 4.15.18
  Uname: Linux 4.15.0-177-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.27
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 16 00:39:58 2022
  InstallationDate: Installed on 2018-12-15 (1247 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  IwConfig:
   virbr0no wireless extensions.
   
   lono wireless extensions.
   
   virbr0-nic  no wireless extensions.
  MachineType: Dell Inc. XPS 15 9570
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-177-generic 
root=UUID=d62d426c-0675-4dca-a5e1-6c8b79ed8056 ro acpi_rev_override=1 
nouveau.modeset=0 pcie_aspm=force drm.vblankoffdelay=1 scsi_mod.use_blk_mq=1 
nouveau.runpm=0 mem_sleep_default=deep noibrs noibpb nopti nospectre_v2 
nospectre_v1 l1tf=off nospec_store_bypass_disable no_stf_barrier mds=off 
mitigations=off clocksource=hpet
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-177-generic N/A
   linux-backports-modules-4.15.0-177-generic  N/A
   linux-firmware  1.173.20
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/07/2021
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.20.0
  dmi.board.name: 0D0T05
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.20.0:bd06/07/2021:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9570
  dmi.sys.vendor: Dell Inc.

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


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


[Bug 1973482] Re: kernel 4.15.0.177 break everything on Dell XPS 15 9570

2022-05-17 Thread JC AGUILAR
Hello,
Same issue with a Dell Latitude 5580. Device detection like disks fail 
randomly. Built-in keyboard, touchpad and Wifi don't work.

Previous kernel build is fine.

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

Title:
  kernel 4.15.0.177 break everything on Dell XPS 15 9570

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


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

Price deflation of Pentax Manual Focus Lenses

2022-05-15 Thread JC OConnell
Seems like vintage NM high quality Pentax MF Prime lenses are defying
inflation price wise on ebay. I just ordered:
SMC Pentax A * 200mm F2.8 $399
SMC Pentax A 100mm F2.8 Macro $349
SMC Pentax 28mm F3.5 shift $449
All three of these sold for considerably less than
the going rate just a few years ago.
jco
--
%(real_name)s Pentax-Discuss Mail List
To unsubscribe send an email to pdml-le...@pdml.net
to UNSUBSCRIBE from the PDML, please visit the link directly above and follow 
the directions.


[Bug 1944468] Re: Electron applications all crash upon launch

2022-05-08 Thread JC
I'm on 22.04 jammy (clean install) and code42 (Crashplan SMB 8.8.4, just
installed) is crashing on start with
"6272:0508/105039.170247:FATAL:gpu_data_manager_impl_private.cc(445)]
GPU process isn't usable. Goodbye.".

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

Title:
  Electron applications all crash upon launch

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


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

[visualization-api] Re: A little lost - trying to see my timeline coding's results

2022-04-23 Thread JC
Thank you!
Working :-)

On Saturday, 23 April 2022 at 02:25:25 UTC+1 Ray Thomas wrote:

> You shouldn't be using Word or any other word processor to write HTML 
> files as most do not produce clean code. Copy and paste what you've got 
> into something like Notepad and save that as an HTML file.
>
> The other thing  is that it sounds like you are running the file locally 
> -  that is a file hosted on your computer and then run in a browser. What 
> you are running into is probably something called CORS - Cross-Origin 
> Resource Sharing. That's a set of rules in browsers designed to protect 
> your computer from malicious attacks. Google Charts code run locally will 
> trigger the protection because the browser knows it's running a local file 
> but then it's trying to download files from another domain, even if it is 
> Google's.
>
> Most browsers have a developer mode. Press F12 and you will probably see 
> the messages saying exactly why the chart is not displaying.
>
> Try uploading the file to a web server. Failing that you can test it by 
> pasting the code into something like CodePen or JSFiddle. You can even go 
> any of the W3Shools tutorials, remove their code and copy and paste your 
> own, then click Run to test it.
>
> CodePen, JSFiddle and the like are more flexible but this is supposed to 
> be a CSS tutorial in W3Schools but it's running the example from 
> https://developers.google.com/chart/interactive/docs/quick_start
>
> [image: w3schools-charts-api.jpg]
>
> On Friday, April 22, 2022 at 7:33:28 PM UTC-4 JC wrote:
>
>> Apologies if I am asking a very basic question, but this is my first time 
>> using Google Charts. I have coded everything for my timeline as instructed 
>> in the guide.
>>
>> However my challenge is that I cannot get it to show me the chart - if I 
>> save it as an html from word, then open it using a browser it just shows me 
>> my coding.
>>
>> So how do I look at my chart?
>>
>> Thanks for any help!
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google Visualization API" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-visualization-api+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-visualization-api/2a5e1a7c-50cf-4b6f-91c9-242f5e4dd8c2n%40googlegroups.com.


[visualization-api] A little lost - trying to see my timeline coding's results

2022-04-22 Thread JC
Apologies if I am asking a very basic question, but this is my first time 
using Google Charts. I have coded everything for my timeline as instructed 
in the guide.

However my challenge is that I cannot get it to show me the chart - if I 
save it as an html from word, then open it using a browser it just shows me 
my coding.

So how do I look at my chart?

Thanks for any help!

-- 
You received this message because you are subscribed to the Google Groups 
"Google Visualization API" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-visualization-api+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-visualization-api/3980c0d0-5047-4cc1-9fc4-ac4b030b23acn%40googlegroups.com.


  1   2   3   4   5   6   7   8   9   10   >