[plasmashell] [Bug 487720] Taskbar and desktop not reading correct mouse position

[Shane Whitmire]

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

--- Comment #7 from Shane Whitmire  ---
This fixes it without having to restart everything:
plasmashell --replace &

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

[plasmashell] [Bug 487720] Taskbar and desktop not reading correct mouse position

[Shane Whitmire]

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

--- Comment #6 from Shane Whitmire  ---
(In reply to Shane Whitmire from comment #5)
> Also experimented with unplugging and replugging my KVM switch on the linux
> computer. It has no affect

I wish you could edit comments. What I mean is I currently have the bug
occuring right now, and when I unplug the USB from my linux computer and back
into it, I still have the same issue of it not registering my mouse. Not even
plugging my mouse directly into the desktop will fix the bug. only restarting
KDE.

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

[plasmashell] [Bug 487720] Taskbar and desktop not reading correct mouse position

[Shane Whitmire]

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

--- Comment #5 from Shane Whitmire  ---
Also experimented with unplugging and replugging my KVM switch on the linux
computer. It has no affect

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

[plasmashell] [Bug 487720] Taskbar and desktop not reading correct mouse position

[Shane Whitmire]

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

--- Comment #4 from Shane Whitmire  ---
So I now have more reliable reproduction steps. Sometimes when I switch my
mouse / keyboard input from one computer to another computer via KVM switch, it
will cause the desktop and task bar to no longer use mouse input

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

[PDB Announce] Production Deployment 2.58.0

[Shane Wadleigh]

2.58.0 was successfully released to production, changes can be viewed at [0].

If anyone encounters any problems, please contact supp...@peeringdb.com

Cheers

[0] https://docs.peeringdb.com/release_notes/
___
Pdb-announce mailing list
Pdb-announce@lists.peeringdb.com
https://lists.peeringdb.com/cgi-bin/mailman/listinfo/pdb-announce

[plasmashell] [Bug 487720] Taskbar and desktop not reading correct mouse position

[Shane Whitmire]

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

--- Comment #3 from Shane Whitmire  ---
Alright some new information. It doesn't seem like it has much to do with
suspending. It looks like it has to do with the KVM switch. Whenever I plug in
my kvm to another computer, it will automatically move all my inputs to the new
computer. Then when I come back to my machine running KDE, it bugs out.

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

[DISCUSS] Apache Daffodil VS Code Extension 1.4.0 Release

[Shane Dell]

Hello all,

The Apache Daffodil VS Code Extension development team believes we are
ready to create a release candidate for 1.4.0 of the Apache Daffodil VS
Code Extension. The list of issues for the VS Code extension can be found
here https://github.com/apache/daffodil-vscode/issues. Closed issues for
1.4.0 can be found at
https://github.com/apache/daffodil-vscode/milestone/5?closed=1. Are there
any problems, complaints or concerns?

This discussion thread will be opened for at least 72 hours before moving
forward. This will be Friday June 7th at 10:30 AM.

Thank you,

Shane Dell

[plasmashell] [Bug 487720] Taskbar and desktop not reading correct mouse position

[Shane Whitmire]

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

--- Comment #2 from Shane Whitmire  ---
something else i would like to add. I have a KVM switch and do oftenly use it.

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

[gatortalk] Fwd: Jaden Rashada Sues Napier (and others)

[Shane Ford]

Title: Jaden Rashada Sues Napier (and others)
FYI.  I ordered my copy. Last year’s magazine was awesome. Sent from Shane’s iPhoneGo Gators! Begin forwarded message:From: Read & Reaction Date: May 29, 2024 at 5:29:36 AM CDTTo: Shane Subject: Jaden Rashada Sues Napier (and others)Reply-To: Read & Reaction 












Implications of the story that won't go away
















  	
			






































  	
			




















  	
			






Can I ask you to do us a favor?

You've trusted us to give us your contact information, presumably because you like the Florida Gators content we provide. Could you please forward this email to 5 of your Gators friends to help us get the word out about our preseason magazine?

We offer Read & Reaction for free because we don't like paywalls. But the only way we're able to do that is if the magazine sells well enough to make it worth it. We know you and your friends will learn cool info about the Gators so please let them know this is out!

Order Now! The Read & Reaction Gators 2024 Preview Magazine

I've tried to avoid writing about Jaden Rashada again, but given the statement that Billy Napier made yesterday and Hal Lewis representing Marcus Castro-Walker, it isn't something that can be ignored. Thus, I've written about what I believe the implications are of the story that just won't go away, but we all hope does soon.

	Jaden Rashada sues Napier (and others)

Thank you so much for your support and for sending this to your friends and colleagues. You're a big part of what we do, and we appreciate you getting the word out that what we're writing has value to you and to Gator Nation!

Go Gators!
- Will & Nick






















	












Thanks so much for reading!

You can reach us at w...@readandreaction.com.
 















	












Thanks so much for reading!

You can reach us at w...

[kwin] [Bug 487720] Taskbar and desktop not reading correct mouse position

[Shane Whitmire]

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

--- Comment #1 from Shane Whitmire  ---
I should also add that I do not know where the KDE log files I need to send
ya'll are. If you let me know the file paths (best to give multiple), then I
can send you a log file

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

[kwin] [Bug 487720] New: Taskbar and desktop not reading correct mouse position

[Shane Whitmire]

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

Bug ID: 487720
   Summary: Taskbar and desktop not reading correct mouse position
Classification: Plasma
   Product: kwin
   Version: 6.0.5
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: input
  Assignee: kwin-bugs-n...@kde.org
  Reporter: dogunbou...@gmail.com
  Target Milestone: ---

The desktop and taskbar do not read the correct mouse position value preventing
me from clicking on any elements on the taskbar after waking from a sleep.

Relevant video demonstrating issue.
https://www.youtube.com/watch?v=UIzN5ZZr1xk

STEPS TO REPRODUCE
Unknown

OBSERVED RESULT
Taskbar and desktop not using correct mouse position

EXPECTED RESULT
Taskbar and desktop to use the correct mouse position

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 6.0.5
KDE Frameworks Version: 6.2.0
Qt Version: 6.7.1
Kernel Version: 6.9.2-arch1-1 (64-bit)
Graphics Platform: X11
Processors: 20 × 12th Gen Intel® Core™ i7-12700K
Memory: 62.5 GiB of RAM
Graphics Processor: Mesa Intel® Arc
Manufacturer: ASUS

ADDITIONAL INFORMATION

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

[jira] [Commented] (WHIMSY-415) /agenda/new fails to mark some reports due when calendar outdated

[Shane Curcuru (Jira)]

[ 
https://issues.apache.org/jira/browse/WHIMSY-415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17849364#comment-17849364
 ] 

Shane Curcuru commented on WHIMSY-415:
--

No - unless you happen to have an "ah-ha, it might be this!" moment, it's not 
worth working on now.  Partly a reminder to myself to be extra careful creating 
next month's agenda, and checking that reminders are only going to needed PMCs.

Thanks!

> /agenda/new fails to mark some reports due when calendar outdated
> -
>
> Key: WHIMSY-415
> URL: https://issues.apache.org/jira/browse/WHIMSY-415
> Project: Whimsy
>  Issue Type: Bug
>  Components: BoardAgenda
>Reporter: Shane Curcuru
>Priority: Minor
>
> On Wednesday 22 May I hit whimsy.a.o/board/agenda/new to create a new agenda, 
> but got several errors on the original screen, since the 
> committers/board/calendar.txt file didn't have any further dates ready.  
> Whimsy did guess at the correct third wednesday of the month, but I didn't 
> check the rest of the details.
> I closed the whimsy window without pushing Post.  Then I updated calendar.txt 
> and waited a day.
> Coming back Thursday to /board/agenda/new, I pressed Post, and it sent out 
> the normal reminders (and sent me a report).
> *BUG*
> Reminders went out to Aries and Struts, even though they had submitted 
> reports in May.  Struts in particular had missed April, so the PMC chair was 
> really confused when they thought we hadn't accepted the May report (which we 
> did).
> Not sure if this is reproduceable, may have been due to calendar.txt not 
> having future dates, or may be because I used /agenda/new, but didn't Post, 
> then came back later and did it all over again.



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

[jira] [Created] (WHIMSY-415) /agenda/new fails to mark some reports due when calendar outdated

[Shane Curcuru (Jira)]

Shane Curcuru created WHIMSY-415:


 Summary: /agenda/new fails to mark some reports due when calendar 
outdated
 Key: WHIMSY-415
 URL: https://issues.apache.org/jira/browse/WHIMSY-415
 Project: Whimsy
  Issue Type: Bug
  Components: BoardAgenda
Reporter: Shane Curcuru


On Wednesday 22 May I hit whimsy.a.o/board/agenda/new to create a new agenda, 
but got several errors on the original screen, since the 
committers/board/calendar.txt file didn't have any further dates ready.  Whimsy 
did guess at the correct third wednesday of the month, but I didn't check the 
rest of the details.

I closed the whimsy window without pushing Post.  Then I updated calendar.txt 
and waited a day.

Coming back Thursday to /board/agenda/new, I pressed Post, and it sent out the 
normal reminders (and sent me a report).

*BUG*

Reminders went out to Aries and Struts, even though they had submitted reports 
in May.  Struts in particular had missed April, so the PMC chair was really 
confused when they thought we hadn't accepted the May report (which we did).

Not sure if this is reproduceable, may have been due to calendar.txt not having 
future dates, or may be because I used /agenda/new, but didn't Post, then came 
back later and did it all over again.



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

[jira] [Assigned] (NIFI-13289) Add tooltip to NewCanvas item

[Shane O'Neill (Jira)]

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

Shane O'Neill reassigned NIFI-13289:


Assignee: Shane O'Neill

> Add tooltip to NewCanvas item
> -
>
> Key: NIFI-13289
> URL: https://issues.apache.org/jira/browse/NIFI-13289
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Core UI
>Reporter: Matt Gilman
>Assignee: Shane O'Neill
>Priority: Major
> Attachments: Screenshot 2024-05-23 at 2.36.55 PM.png
>
>
> Old NiFi UI had tooltips for the new canvas items in the top bar. These are 
> currently missing in the new UI.



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

Re: [C/C Europe 25] [DISCUSS] Where to hold the conference

[Shane Curcuru]

Claude Warren wrote on 5/18/24 10:24 AM:

I will not be chairing the next conference.  So I am looking for someone to
stand up and volunteer.  If there is no volunteer, there will not be a
conference.


People who are passionate about C/C Europe 2025 should participate in 
this other thread, which is the most important decision to make:


https://lists.apache.org/thread/n4t1sgsqlp54tv5mwc3m4j8ds48gog2z

...snip...

On Fri, May 17, 2024 at 8:45 AM Rich Bowen  wrote:


...snip...

Yes, I am being cynical here. It’s because I have endured 20 years of
these meetings, and half of them devolved into shouting matches (no, I’m
not exaggerating. Ask Shane for his stories!) and the rest were just a
waste of time.


If there is a which-city BOF, let me know!  I'll be in the back, 
cheering you on.  Don't mind the brown bag I'm drinking from.



I would encourage you, rather than having a “share our opinions” meeting,
to delegate specific tasks, figure out a timeline for reporting and
completion of those tasks, and then go get a beer.

...snip...

My suggestion: make a wiki page or text file somewhere to base C/C EU 25 
planning from [1] so you can collect information.


Then ask for volunteers who have experience with specific cities to list 
themselves, and include brief notes about *how* they can help as a local 
contact: do they know specific venues, have they run events locally, can 
they work as local marketing help, etc.


That will help any future conference, once the organizing team starts 
doing venue selection (which is primarily costing/contracts/travel).


--
- Shane
  Long-ago ex-conference planner
  The Apache Software Foundation

[1] Perhaps here?
  https://cwiki.apache.org/confluence/display/COMDEV/ApacheCon




-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

[PATCH 3/3] drm/amdgpu: Update the impelmentation of AMDGPU_PTE_MTYPE_VG10

[Shane Xiao]

This patch changes the implementation of AMDGPU_PTE_MTYPE_VG10,
clear the bits before setting the new one.

Suggested-by: Alex Deucher 
Signed-off-by: longlyao 
Signed-off-by: Shane Xiao 
---
 drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.c |  3 +--
 drivers/gpu/drm/amd/amdgpu/amdgpu_vm.h  |  7 --
 drivers/gpu/drm/amd/amdgpu/gmc_v9_0.c   | 32 -
 3 files changed, 21 insertions(+), 21 deletions(-)

diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.c 
b/drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.c
index 0364a7bb5893..f09f33d1beec 100644
--- a/drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.c
+++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.c
@@ -844,8 +844,7 @@ static void amdgpu_ttm_gart_bind_gfx9_mqd(struct 
amdgpu_device *adev,
int num_xcc = max(1U, adev->gfx.num_xcc_per_xcp);
uint64_t page_idx, pages_per_xcc;
int i;
-   uint64_t ctrl_flags = (flags & ~AMDGPU_PTE_MTYPE_VG10_MASK) |
-   AMDGPU_PTE_MTYPE_VG10(AMDGPU_MTYPE_NC);
+   uint64_t ctrl_flags = AMDGPU_PTE_MTYPE_VG10(flags, AMDGPU_MTYPE_NC);
 
pages_per_xcc = total_pages;
do_div(pages_per_xcc, num_xcc);
diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.h 
b/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.h
index 0c4a01fad851..9990794e275e 100644
--- a/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.h
+++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.h
@@ -94,8 +94,11 @@ struct amdgpu_mem_stats;
 #define AMDGPU_VM_NORETRY_FLAGS_TF (AMDGPU_PTE_VALID | AMDGPU_PTE_SYSTEM | \
   AMDGPU_PTE_PRT)
 /* For GFX9 */
-#define AMDGPU_PTE_MTYPE_VG10(a)   ((uint64_t)(a) << 57)
-#define AMDGPU_PTE_MTYPE_VG10_MASK AMDGPU_PTE_MTYPE_VG10(3ULL)
+#define AMDGPU_PTE_MTYPE_VG10_SHIFT(mtype) ((uint64_t)(mtype) << 57)
+#define AMDGPU_PTE_MTYPE_VG10_MASK AMDGPU_PTE_MTYPE_VG10_SHIFT(3ULL)
+#define AMDGPU_PTE_MTYPE_VG10(flags, mtype)\
+   ((flags) & ((~AMDGPU_PTE_MTYPE_VG10_MASK)) |\
+ AMDGPU_PTE_MTYPE_VG10_SHIFT(mtype))
 
 #define AMDGPU_MTYPE_NC 0
 #define AMDGPU_MTYPE_CC 2
diff --git a/drivers/gpu/drm/amd/amdgpu/gmc_v9_0.c 
b/drivers/gpu/drm/amd/amdgpu/gmc_v9_0.c
index 094c08cb98e7..6809ab532c40 100644
--- a/drivers/gpu/drm/amd/amdgpu/gmc_v9_0.c
+++ b/drivers/gpu/drm/amd/amdgpu/gmc_v9_0.c
@@ -1075,19 +1075,19 @@ static uint64_t gmc_v9_0_map_mtype(struct amdgpu_device 
*adev, uint32_t flags)
 {
switch (flags) {
case AMDGPU_VM_MTYPE_DEFAULT:
-   return AMDGPU_PTE_MTYPE_VG10(MTYPE_NC);
+   return AMDGPU_PTE_MTYPE_VG10(0ULL, MTYPE_NC);
case AMDGPU_VM_MTYPE_NC:
-   return AMDGPU_PTE_MTYPE_VG10(MTYPE_NC);
+   return AMDGPU_PTE_MTYPE_VG10(0ULL, MTYPE_NC);
case AMDGPU_VM_MTYPE_WC:
-   return AMDGPU_PTE_MTYPE_VG10(MTYPE_WC);
+   return AMDGPU_PTE_MTYPE_VG10(0ULL, MTYPE_WC);
case AMDGPU_VM_MTYPE_RW:
-   return AMDGPU_PTE_MTYPE_VG10(MTYPE_RW);
+   return AMDGPU_PTE_MTYPE_VG10(0ULL, MTYPE_RW);
case AMDGPU_VM_MTYPE_CC:
-   return AMDGPU_PTE_MTYPE_VG10(MTYPE_CC);
+   return AMDGPU_PTE_MTYPE_VG10(0ULL, MTYPE_CC);
case AMDGPU_VM_MTYPE_UC:
-   return AMDGPU_PTE_MTYPE_VG10(MTYPE_UC);
+   return AMDGPU_PTE_MTYPE_VG10(0ULL, MTYPE_UC);
default:
-   return AMDGPU_PTE_MTYPE_VG10(MTYPE_NC);
+   return AMDGPU_PTE_MTYPE_VG10(0ULL, MTYPE_NC);
}
 }
 
@@ -1228,8 +1228,8 @@ static void gmc_v9_0_get_coherence_flags(struct 
amdgpu_device *adev,
}
 
if (mtype != MTYPE_NC)
-   *flags = (*flags & ~AMDGPU_PTE_MTYPE_VG10_MASK) |
-AMDGPU_PTE_MTYPE_VG10(mtype);
+   *flags = AMDGPU_PTE_MTYPE_VG10(*flags, mtype);
+
*flags |= snoop ? AMDGPU_PTE_SNOOPED : 0;
 }
 
@@ -1281,9 +1281,9 @@ static void gmc_v9_0_override_vm_pte_flags(struct 
amdgpu_device *adev,
 * and can also be overridden.
 */
if ((*flags & AMDGPU_PTE_MTYPE_VG10_MASK) !=
-   AMDGPU_PTE_MTYPE_VG10(MTYPE_NC) &&
+   AMDGPU_PTE_MTYPE_VG10(0ULL, MTYPE_NC) &&
(*flags & AMDGPU_PTE_MTYPE_VG10_MASK) !=
-   AMDGPU_PTE_MTYPE_VG10(MTYPE_UC)) {
+   AMDGPU_PTE_MTYPE_VG10(0ULL, MTYPE_UC)) {
dev_dbg_ratelimited(adev->dev, "MTYPE is not NC or UC\n");
return;
}
@@ -1312,7 +1312,7 @@ static void gmc_v9_0_override_vm_pte_flags(struct 
amdgpu_device *adev,
if (nid == local_node) {
uint64_t old_flags = *flags;
if ((*flags & AMDGPU_PTE_MTYPE_VG10_MASK) ==
-   AMDGPU_PTE_MTYPE_VG10(MTYPE_NC)) {
+   AMDGPU_PTE_MTYPE_VG10(0ULL, MTYPE_NC)) {
unsigned int mtype_local = MTYPE_RW;
 
if (amdgpu_mtype_local == 1)
@@ -1320,12 +1320,10 @@ st

[PATCH 2/3] drm/amdgpu: Update the impelmentation of AMDGPU_PTE_MTYPE_NV10

[Shane Xiao]

This patch changes the implementation of AMDGPU_PTE_MTYPE_NV10,
clear the bits before setting the new one.

Suggested-by: Alex Deucher 
Signed-off-by: longlyao 
Signed-off-by: Shane Xiao 
---
 drivers/gpu/drm/amd/amdgpu/amdgpu_vm.h |  7 +--
 drivers/gpu/drm/amd/amdgpu/gmc_v10_0.c | 17 -
 drivers/gpu/drm/amd/amdgpu/gmc_v11_0.c | 17 -
 3 files changed, 21 insertions(+), 20 deletions(-)

diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.h 
b/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.h
index b5f81e7e6356..0c4a01fad851 100644
--- a/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.h
+++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.h
@@ -108,8 +108,11 @@ struct amdgpu_mem_stats;
 | AMDGPU_PTE_MTYPE_VG10(AMDGPU_MTYPE_CC))
 
 /* gfx10 */
-#define AMDGPU_PTE_MTYPE_NV10(a)   ((uint64_t)(a) << 48)
-#define AMDGPU_PTE_MTYPE_NV10_MASK AMDGPU_PTE_MTYPE_NV10(7ULL)
+#define AMDGPU_PTE_MTYPE_NV10_SHIFT(mtype) ((uint64_t)(mtype) << 48)
+#define AMDGPU_PTE_MTYPE_NV10_MASK AMDGPU_PTE_MTYPE_NV10_SHIFT(7ULL)
+#define AMDGPU_PTE_MTYPE_NV10(flags, mtype)\
+   ((flags) & ((~AMDGPU_PTE_MTYPE_NV10_MASK)) |\
+ AMDGPU_PTE_MTYPE_NV10_SHIFT(mtype))
 
 /* gfx12 */
 #define AMDGPU_PTE_PRT_GFX12   (1ULL << 56)
diff --git a/drivers/gpu/drm/amd/amdgpu/gmc_v10_0.c 
b/drivers/gpu/drm/amd/amdgpu/gmc_v10_0.c
index d933e19e0cf5..f0ceab3ce5bf 100644
--- a/drivers/gpu/drm/amd/amdgpu/gmc_v10_0.c
+++ b/drivers/gpu/drm/amd/amdgpu/gmc_v10_0.c
@@ -473,17 +473,17 @@ static uint64_t gmc_v10_0_map_mtype(struct amdgpu_device 
*adev, uint32_t flags)
 {
switch (flags) {
case AMDGPU_VM_MTYPE_DEFAULT:
-   return AMDGPU_PTE_MTYPE_NV10(MTYPE_NC);
+   return AMDGPU_PTE_MTYPE_NV10(0ULL, MTYPE_NC);
case AMDGPU_VM_MTYPE_NC:
-   return AMDGPU_PTE_MTYPE_NV10(MTYPE_NC);
+   return AMDGPU_PTE_MTYPE_NV10(0ULL, MTYPE_NC);
case AMDGPU_VM_MTYPE_WC:
-   return AMDGPU_PTE_MTYPE_NV10(MTYPE_WC);
+   return AMDGPU_PTE_MTYPE_NV10(0ULL, MTYPE_WC);
case AMDGPU_VM_MTYPE_CC:
-   return AMDGPU_PTE_MTYPE_NV10(MTYPE_CC);
+   return AMDGPU_PTE_MTYPE_NV10(0ULL, MTYPE_CC);
case AMDGPU_VM_MTYPE_UC:
-   return AMDGPU_PTE_MTYPE_NV10(MTYPE_UC);
+   return AMDGPU_PTE_MTYPE_NV10(0ULL, MTYPE_UC);
default:
-   return AMDGPU_PTE_MTYPE_NV10(MTYPE_NC);
+   return AMDGPU_PTE_MTYPE_NV10(0ULL, MTYPE_NC);
}
 }
 
@@ -536,8 +536,7 @@ static void gmc_v10_0_get_vm_pte(struct amdgpu_device *adev,
if (bo && bo->flags & (AMDGPU_GEM_CREATE_COHERENT |
   AMDGPU_GEM_CREATE_EXT_COHERENT |
   AMDGPU_GEM_CREATE_UNCACHED))
-   *flags = (*flags & ~AMDGPU_PTE_MTYPE_NV10_MASK) |
-AMDGPU_PTE_MTYPE_NV10(MTYPE_UC);
+   *flags = AMDGPU_PTE_MTYPE_NV10(*flags, MTYPE_UC);
 }
 
 static unsigned int gmc_v10_0_get_vbios_fb_size(struct amdgpu_device *adev)
@@ -763,7 +762,7 @@ static int gmc_v10_0_gart_init(struct amdgpu_device *adev)
return r;
 
adev->gart.table_size = adev->gart.num_gpu_pages * 8;
-   adev->gart.gart_pte_flags = AMDGPU_PTE_MTYPE_NV10(MTYPE_UC) |
+   adev->gart.gart_pte_flags = AMDGPU_PTE_MTYPE_NV10(0ULL, MTYPE_UC) |
 AMDGPU_PTE_EXECUTABLE;
 
return amdgpu_gart_table_vram_alloc(adev);
diff --git a/drivers/gpu/drm/amd/amdgpu/gmc_v11_0.c 
b/drivers/gpu/drm/amd/amdgpu/gmc_v11_0.c
index 527dc917e049..cad883783834 100644
--- a/drivers/gpu/drm/amd/amdgpu/gmc_v11_0.c
+++ b/drivers/gpu/drm/amd/amdgpu/gmc_v11_0.c
@@ -438,17 +438,17 @@ static uint64_t gmc_v11_0_map_mtype(struct amdgpu_device 
*adev, uint32_t flags)
 {
switch (flags) {
case AMDGPU_VM_MTYPE_DEFAULT:
-   return AMDGPU_PTE_MTYPE_NV10(MTYPE_NC);
+   return AMDGPU_PTE_MTYPE_NV10(0ULL, MTYPE_NC);
case AMDGPU_VM_MTYPE_NC:
-   return AMDGPU_PTE_MTYPE_NV10(MTYPE_NC);
+   return AMDGPU_PTE_MTYPE_NV10(0ULL, MTYPE_NC);
case AMDGPU_VM_MTYPE_WC:
-   return AMDGPU_PTE_MTYPE_NV10(MTYPE_WC);
+   return AMDGPU_PTE_MTYPE_NV10(0ULL, MTYPE_WC);
case AMDGPU_VM_MTYPE_CC:
-   return AMDGPU_PTE_MTYPE_NV10(MTYPE_CC);
+   return AMDGPU_PTE_MTYPE_NV10(0ULL, MTYPE_CC);
case AMDGPU_VM_MTYPE_UC:
-   return AMDGPU_PTE_MTYPE_NV10(MTYPE_UC);
+   return AMDGPU_PTE_MTYPE_NV10(0ULL, MTYPE_UC);
default:
-   return AMDGPU_PTE_MTYPE_NV10(MTYPE_NC);
+   return AMDGPU_PTE_MTYPE_NV10(0ULL, MTYPE_NC);
}
 }
 
@@ -501,8 +501,7 @@ static void gmc_v11_0_get_vm_pte(struct amdgpu_device *adev,
if (bo && bo->flags & (AMDGPU_GEM_CREATE_COHE

[PATCH 1/3] drm/amdgpu: Update the impelmentation of AMDGPU_PTE_MTYPE_GFX12

[Shane Xiao]

This patch changes the implementation of AMDGPU_PTE_MTYPE_GFX12,
clear the bits before setting the new one.
This fixed the potential issue that GFX12 setting memory to NC.

v2: Clear mtype field before setting the new one (Alex)
v3: Fix typo (Felix)

Suggested-by: Alex Deucher 
Signed-off-by: longlyao 
Signed-off-by: Shane Xiao 
---
 drivers/gpu/drm/amd/amdgpu/amdgpu_vm.h |  7 +--
 drivers/gpu/drm/amd/amdgpu/gmc_v12_0.c | 19 +--
 2 files changed, 14 insertions(+), 12 deletions(-)

diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.h 
b/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.h
index 312a408b80d3..b5f81e7e6356 100644
--- a/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.h
+++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.h
@@ -116,8 +116,11 @@ struct amdgpu_mem_stats;
 #define AMDGPU_PTE_PRT_FLAG(adev)  \
((amdgpu_ip_version((adev), GC_HWIP, 0) >= IP_VERSION(12, 0, 0)) ? 
AMDGPU_PTE_PRT_GFX12 : AMDGPU_PTE_PRT)
 
-#define AMDGPU_PTE_MTYPE_GFX12(a)  ((uint64_t)(a) << 54)
-#define AMDGPU_PTE_MTYPE_GFX12_MASKAMDGPU_PTE_MTYPE_GFX12(3ULL)
+#define AMDGPU_PTE_MTYPE_GFX12_SHIFT(mtype)((uint64_t)(mtype) << 54)
+#define AMDGPU_PTE_MTYPE_GFX12_MASKAMDGPU_PTE_MTYPE_GFX12_SHIFT(3ULL)
+#define AMDGPU_PTE_MTYPE_GFX12(flags, mtype)   \
+   ((flags) & ((~AMDGPU_PTE_MTYPE_GFX12_MASK)) |   \
+ AMDGPU_PTE_MTYPE_GFX12_SHIFT(mtype))
 
 #define AMDGPU_PTE_IS_PTE  (1ULL << 63)
 
diff --git a/drivers/gpu/drm/amd/amdgpu/gmc_v12_0.c 
b/drivers/gpu/drm/amd/amdgpu/gmc_v12_0.c
index e2c6ec3cc4f3..c723d36deac0 100644
--- a/drivers/gpu/drm/amd/amdgpu/gmc_v12_0.c
+++ b/drivers/gpu/drm/amd/amdgpu/gmc_v12_0.c
@@ -461,17 +461,17 @@ static uint64_t gmc_v12_0_map_mtype(struct amdgpu_device 
*adev, uint32_t flags)
 {
switch (flags) {
case AMDGPU_VM_MTYPE_DEFAULT:
-   return AMDGPU_PTE_MTYPE_GFX12(MTYPE_NC);
+   return AMDGPU_PTE_MTYPE_GFX12(0ULL,MTYPE_NC);
case AMDGPU_VM_MTYPE_NC:
-   return AMDGPU_PTE_MTYPE_GFX12(MTYPE_NC);
+   return AMDGPU_PTE_MTYPE_GFX12(0ULL,MTYPE_NC);
case AMDGPU_VM_MTYPE_WC:
-   return AMDGPU_PTE_MTYPE_GFX12(MTYPE_WC);
+   return AMDGPU_PTE_MTYPE_GFX12(0ULL,MTYPE_WC);
case AMDGPU_VM_MTYPE_CC:
-   return AMDGPU_PTE_MTYPE_GFX12(MTYPE_CC);
+   return AMDGPU_PTE_MTYPE_GFX12(0ULL,MTYPE_CC);
case AMDGPU_VM_MTYPE_UC:
-   return AMDGPU_PTE_MTYPE_GFX12(MTYPE_UC);
+   return AMDGPU_PTE_MTYPE_GFX12(0ULL,MTYPE_UC);
default:
-   return AMDGPU_PTE_MTYPE_GFX12(MTYPE_NC);
+   return AMDGPU_PTE_MTYPE_GFX12(0ULL,MTYPE_NC);
}
 }
 
@@ -524,8 +524,7 @@ static void gmc_v12_0_get_vm_pte(struct amdgpu_device *adev,
 
if (bo->flags & (AMDGPU_GEM_CREATE_COHERENT |
   AMDGPU_GEM_CREATE_UNCACHED))
-   *flags = (*flags & ~AMDGPU_PTE_MTYPE_GFX12_MASK) |
-AMDGPU_PTE_MTYPE_GFX12(MTYPE_UC);
+   *flags = AMDGPU_PTE_MTYPE_GFX12(*flags, MTYPE_UC);
 
bo_adev = amdgpu_ttm_adev(bo->tbo.bdev);
coherent = bo->flags & AMDGPU_GEM_CREATE_COHERENT;
@@ -534,7 +533,7 @@ static void gmc_v12_0_get_vm_pte(struct amdgpu_device *adev,
 
/* WA for HW bug */
if (is_system || ((bo_adev != adev) && coherent))
-   *flags |= AMDGPU_PTE_MTYPE_GFX12(MTYPE_NC);
+   *flags = AMDGPU_PTE_MTYPE_GFX12(*flags, MTYPE_NC);
 
 }
 
@@ -707,7 +706,7 @@ static int gmc_v12_0_gart_init(struct amdgpu_device *adev)
return r;
 
adev->gart.table_size = adev->gart.num_gpu_pages * 8;
-   adev->gart.gart_pte_flags = AMDGPU_PTE_MTYPE_GFX12(MTYPE_UC) |
+   adev->gart.gart_pte_flags = AMDGPU_PTE_MTYPE_GFX12(0ULL, MTYPE_UC) |
AMDGPU_PTE_EXECUTABLE |
AMDGPU_PTE_IS_PTE;
 
-- 
2.25.1

RE: [PATCH] drm/amdgpu: Update the impelmentation of AMDGPU_PTE_MTYPE_GFX12

[Xiao, Shane]

[AMD Official Use Only - AMD Internal Distribution Only]

Hi Alex,

I have changed the macro AMDGPU_PTE_MTYPE_GFX12 to clear mtype bit before 
setting.
Add one parameter for this macro, and some related code needs to be changed.

I'm not sure whether that's the ideal way to do it, but if it is, I'll 
implement it for all other generations.
If this is not ideal way, could you please give me some other advice?

Best Regards,
Shane


> -Original Message-
> From: Xiao, Shane 
> Sent: Monday, May 20, 2024 5:14 PM
> To: amd-gfx@lists.freedesktop.org; alexdeuc...@gmail.com; Kuehling, Felix
> ; Somasekharan, Sreekant
> 
> Cc: Liu, Aaron ; Xiao, Shane ;
> Yao, Longlong 
> Subject: [PATCH] drm/amdgpu: Update the impelmentation of
> AMDGPU_PTE_MTYPE_GFX12
>
> This patch changes the implementation of AMDGPU_PTE_MTYPE_GFX12,
> clear the bits before setting the new one.
> This fixed the potential issue that GFX12 setting memory to NC.
>
> v2: Clear mtype field before setting the new one (Alex)
>
> Signed-off-by: longlyao 
> Signed-off-by: Shane Xiao 
> ---
>  drivers/gpu/drm/amd/amdgpu/amdgpu_vm.h |  7 +--
> drivers/gpu/drm/amd/amdgpu/gmc_v12_0.c | 23 +++
>  2 files changed, 16 insertions(+), 14 deletions(-)
>
> diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.h
> b/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.h
> index bc71b44387b2..99b246e82ed6 100644
> --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.h
> +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.h
> @@ -116,8 +116,11 @@ struct amdgpu_mem_stats;
>  #define AMDGPU_PTE_PRT_FLAG(adev)\
>   ((amdgpu_ip_version((adev), GC_HWIP, 0) >= IP_VERSION(12, 0, 0)) ?
> AMDGPU_PTE_PRT_GFX12 : AMDGPU_PTE_PRT)
>
> -#define AMDGPU_PTE_MTYPE_GFX12(a)((uint64_t)(a) << 54)
> -#define AMDGPU_PTE_MTYPE_GFX12_MASK
>   AMDGPU_PTE_MTYPE_GFX12(3ULL)
> +#define AMDGPU_PTE_MTYPE_GFX12_SHIFT(mtype)  ((uint64_t)(mytype)
> << 54)
> +#define AMDGPU_PTE_MTYPE_GFX12_MASK
>   AMDGPU_PTE_MTYPE_GFX12_SHIFT(3ULL)
> +#define AMDGPU_PTE_MTYPE_GFX12(flags, mtype) \
> + ((flags) & ((~AMDGPU_PTE_MTYPE_GFX12_MASK)) |   \
> +   AMDGPU_PTE_MTYPE_GFX12_SHIFT(mtype))
>
>  #define AMDGPU_PTE_IS_PTE(1ULL << 63)
>
> diff --git a/drivers/gpu/drm/amd/amdgpu/gmc_v12_0.c
> b/drivers/gpu/drm/amd/amdgpu/gmc_v12_0.c
> index e2c6ec3cc4f3..f2d331d0181f 100644
> --- a/drivers/gpu/drm/amd/amdgpu/gmc_v12_0.c
> +++ b/drivers/gpu/drm/amd/amdgpu/gmc_v12_0.c
> @@ -461,17 +461,17 @@ static uint64_t gmc_v12_0_map_mtype(struct
> amdgpu_device *adev, uint32_t flags)  {
>   switch (flags) {
>   case AMDGPU_VM_MTYPE_DEFAULT:
> - return AMDGPU_PTE_MTYPE_GFX12(MTYPE_NC);
> + return AMDGPU_PTE_MTYPE_GFX12(0ULL,MTYPE_NC);
>   case AMDGPU_VM_MTYPE_NC:
> - return AMDGPU_PTE_MTYPE_GFX12(MTYPE_NC);
> + return AMDGPU_PTE_MTYPE_GFX12(0ULL,MTYPE_NC);
>   case AMDGPU_VM_MTYPE_WC:
> - return AMDGPU_PTE_MTYPE_GFX12(MTYPE_WC);
> + return AMDGPU_PTE_MTYPE_GFX12(0ULL,MTYPE_WC);
>   case AMDGPU_VM_MTYPE_CC:
> - return AMDGPU_PTE_MTYPE_GFX12(MTYPE_CC);
> + return AMDGPU_PTE_MTYPE_GFX12(0ULL,MTYPE_CC);
>   case AMDGPU_VM_MTYPE_UC:
> - return AMDGPU_PTE_MTYPE_GFX12(MTYPE_UC);
> + return AMDGPU_PTE_MTYPE_GFX12(0ULL,MTYPE_UC);
>   default:
> - return AMDGPU_PTE_MTYPE_GFX12(MTYPE_NC);
> + return AMDGPU_PTE_MTYPE_GFX12(0ULL,MTYPE_NC);
>   }
>  }
>
> @@ -509,8 +509,8 @@ static void gmc_v12_0_get_vm_pte(struct
> amdgpu_device *adev,
>   *flags &= ~AMDGPU_PTE_EXECUTABLE;
>   *flags |= mapping->flags & AMDGPU_PTE_EXECUTABLE;
>
> - *flags &= ~AMDGPU_PTE_MTYPE_GFX12_MASK;
> - *flags |= (mapping->flags & AMDGPU_PTE_MTYPE_GFX12_MASK);
> + *flags = AMDGPU_PTE_MTYPE_GFX12(*flags, (mapping->flags &
>   \
> +  AMDGPU_PTE_MTYPE_GFX12_MASK) >>
> AMDGPU_PTE_MTYPE_GFX12_SHIFT);

This is not correct. I will correct this change in next version.

>
>   if (mapping->flags & AMDGPU_PTE_PRT_GFX12) {
>   *flags |= AMDGPU_PTE_PRT_GFX12;
> @@ -524,8 +524,7 @@ static void gmc_v12_0_get_vm_pte(struct
> amdgpu_device *adev,
>
>   if (bo->flags & (AMDGPU_GEM_CREATE_COHERENT |
>  AMDGPU_GEM_CREATE_UNCACHED))
> - *flags = (*flags & ~AMDGPU_PTE_MTYPE_GFX12_MASK) |
> -  AMDGPU_PTE_MTYPE_GFX12(MTYPE_UC);
> + *flags = AMDGPU_PTE_MTYPE_GFX12(*flags, MTYPE_UC);
>
>   bo_adev = amdgpu_ttm_adev(bo->tbo.bdev);
>   coherent = bo->flags & AMDGPU

[PATCH] drm/amdgpu: Update the impelmentation of AMDGPU_PTE_MTYPE_GFX12

[Shane Xiao]

This patch changes the implementation of AMDGPU_PTE_MTYPE_GFX12,
clear the bits before setting the new one.
This fixed the potential issue that GFX12 setting memory to NC.

v2: Clear mtype field before setting the new one (Alex)

Signed-off-by: longlyao 
Signed-off-by: Shane Xiao 
---
 drivers/gpu/drm/amd/amdgpu/amdgpu_vm.h |  7 +--
 drivers/gpu/drm/amd/amdgpu/gmc_v12_0.c | 23 +++
 2 files changed, 16 insertions(+), 14 deletions(-)

diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.h 
b/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.h
index bc71b44387b2..99b246e82ed6 100644
--- a/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.h
+++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.h
@@ -116,8 +116,11 @@ struct amdgpu_mem_stats;
 #define AMDGPU_PTE_PRT_FLAG(adev)  \
((amdgpu_ip_version((adev), GC_HWIP, 0) >= IP_VERSION(12, 0, 0)) ? 
AMDGPU_PTE_PRT_GFX12 : AMDGPU_PTE_PRT)
 
-#define AMDGPU_PTE_MTYPE_GFX12(a)  ((uint64_t)(a) << 54)
-#define AMDGPU_PTE_MTYPE_GFX12_MASKAMDGPU_PTE_MTYPE_GFX12(3ULL)
+#define AMDGPU_PTE_MTYPE_GFX12_SHIFT(mtype)((uint64_t)(mytype) << 54)
+#define AMDGPU_PTE_MTYPE_GFX12_MASKAMDGPU_PTE_MTYPE_GFX12_SHIFT(3ULL)
+#define AMDGPU_PTE_MTYPE_GFX12(flags, mtype)   \
+   ((flags) & ((~AMDGPU_PTE_MTYPE_GFX12_MASK)) |   \
+ AMDGPU_PTE_MTYPE_GFX12_SHIFT(mtype))
 
 #define AMDGPU_PTE_IS_PTE  (1ULL << 63)
 
diff --git a/drivers/gpu/drm/amd/amdgpu/gmc_v12_0.c 
b/drivers/gpu/drm/amd/amdgpu/gmc_v12_0.c
index e2c6ec3cc4f3..f2d331d0181f 100644
--- a/drivers/gpu/drm/amd/amdgpu/gmc_v12_0.c
+++ b/drivers/gpu/drm/amd/amdgpu/gmc_v12_0.c
@@ -461,17 +461,17 @@ static uint64_t gmc_v12_0_map_mtype(struct amdgpu_device 
*adev, uint32_t flags)
 {
switch (flags) {
case AMDGPU_VM_MTYPE_DEFAULT:
-   return AMDGPU_PTE_MTYPE_GFX12(MTYPE_NC);
+   return AMDGPU_PTE_MTYPE_GFX12(0ULL,MTYPE_NC);
case AMDGPU_VM_MTYPE_NC:
-   return AMDGPU_PTE_MTYPE_GFX12(MTYPE_NC);
+   return AMDGPU_PTE_MTYPE_GFX12(0ULL,MTYPE_NC);
case AMDGPU_VM_MTYPE_WC:
-   return AMDGPU_PTE_MTYPE_GFX12(MTYPE_WC);
+   return AMDGPU_PTE_MTYPE_GFX12(0ULL,MTYPE_WC);
case AMDGPU_VM_MTYPE_CC:
-   return AMDGPU_PTE_MTYPE_GFX12(MTYPE_CC);
+   return AMDGPU_PTE_MTYPE_GFX12(0ULL,MTYPE_CC);
case AMDGPU_VM_MTYPE_UC:
-   return AMDGPU_PTE_MTYPE_GFX12(MTYPE_UC);
+   return AMDGPU_PTE_MTYPE_GFX12(0ULL,MTYPE_UC);
default:
-   return AMDGPU_PTE_MTYPE_GFX12(MTYPE_NC);
+   return AMDGPU_PTE_MTYPE_GFX12(0ULL,MTYPE_NC);
}
 }
 
@@ -509,8 +509,8 @@ static void gmc_v12_0_get_vm_pte(struct amdgpu_device *adev,
*flags &= ~AMDGPU_PTE_EXECUTABLE;
*flags |= mapping->flags & AMDGPU_PTE_EXECUTABLE;
 
-   *flags &= ~AMDGPU_PTE_MTYPE_GFX12_MASK;
-   *flags |= (mapping->flags & AMDGPU_PTE_MTYPE_GFX12_MASK);
+   *flags = AMDGPU_PTE_MTYPE_GFX12(*flags, (mapping->flags &   \
+AMDGPU_PTE_MTYPE_GFX12_MASK) >> 
AMDGPU_PTE_MTYPE_GFX12_SHIFT);
 
if (mapping->flags & AMDGPU_PTE_PRT_GFX12) {
*flags |= AMDGPU_PTE_PRT_GFX12;
@@ -524,8 +524,7 @@ static void gmc_v12_0_get_vm_pte(struct amdgpu_device *adev,
 
if (bo->flags & (AMDGPU_GEM_CREATE_COHERENT |
   AMDGPU_GEM_CREATE_UNCACHED))
-   *flags = (*flags & ~AMDGPU_PTE_MTYPE_GFX12_MASK) |
-AMDGPU_PTE_MTYPE_GFX12(MTYPE_UC);
+   *flags = AMDGPU_PTE_MTYPE_GFX12(*flags, MTYPE_UC);
 
bo_adev = amdgpu_ttm_adev(bo->tbo.bdev);
coherent = bo->flags & AMDGPU_GEM_CREATE_COHERENT;
@@ -534,7 +533,7 @@ static void gmc_v12_0_get_vm_pte(struct amdgpu_device *adev,
 
/* WA for HW bug */
if (is_system || ((bo_adev != adev) && coherent))
-   *flags |= AMDGPU_PTE_MTYPE_GFX12(MTYPE_NC);
+   *flags = AMDGPU_PTE_MTYPE_GFX12(*flags, MTYPE_NC);
 
 }
 
@@ -707,7 +706,7 @@ static int gmc_v12_0_gart_init(struct amdgpu_device *adev)
return r;
 
adev->gart.table_size = adev->gart.num_gpu_pages * 8;
-   adev->gart.gart_pte_flags = AMDGPU_PTE_MTYPE_GFX12(MTYPE_UC) |
+   adev->gart.gart_pte_flags = AMDGPU_PTE_MTYPE_GFX12(0ULL, MTYPE_UC) |
AMDGPU_PTE_EXECUTABLE |
AMDGPU_PTE_IS_PTE;
 
-- 
2.25.1

RE: [PATCH] drm/amdkfd: Correct the GFX12 memory type setting

[Xiao, Shane]

[AMD Official Use Only - AMD Internal Distribution Only]

> -Original Message-
> From: Xiao, Shane
> Sent: Monday, May 20, 2024 4:21 PM
> To: Alex Deucher 
> Cc: amd-gfx@lists.freedesktop.org; Kuehling, Felix
> ; Somasekharan, Sreekant
> ; Liu, Aaron ;
> Yao, Longlong 
> Subject: RE: [PATCH] drm/amdkfd: Correct the GFX12 memory type setting
>
>
>
> > -Original Message-
> > From: Alex Deucher 
> > Sent: Friday, May 17, 2024 11:52 PM
> > To: Xiao, Shane 
> > Cc: amd-gfx@lists.freedesktop.org; Kuehling, Felix
> > ; Somasekharan, Sreekant
> > ; Liu, Aaron ;
> Yao,
> > Longlong 
> > Subject: Re: [PATCH] drm/amdkfd: Correct the GFX12 memory type setting
> >
> > On Fri, May 17, 2024 at 3:07 AM Shane Xiao 
> wrote:
> > >
> > > This patch fixes the GFX12 memory type to NC. Since the Memory type
> > > can be overwritten by the previous operations, the GFX12 MTYPE bits
> > > need to be clear before setting to NC.
> > >
> > > Signed-off-by: longlyao 
> > > Signed-off-by: Shane Xiao 
> > > ---
> > >  drivers/gpu/drm/amd/amdgpu/gmc_v12_0.c | 3 ++-
> > >  1 file changed, 2 insertions(+), 1 deletion(-)
> > >
> > > diff --git a/drivers/gpu/drm/amd/amdgpu/gmc_v12_0.c
> > > b/drivers/gpu/drm/amd/amdgpu/gmc_v12_0.c
> > > index e2c6ec3cc4f3..6246d1dc0d30 100644
> > > --- a/drivers/gpu/drm/amd/amdgpu/gmc_v12_0.c
> > > +++ b/drivers/gpu/drm/amd/amdgpu/gmc_v12_0.c
> > > @@ -534,7 +534,8 @@ static void gmc_v12_0_get_vm_pte(struct
> > > amdgpu_device *adev,
> > >
> > > /* WA for HW bug */
> > > if (is_system || ((bo_adev != adev) && coherent))
> > > -   *flags |= AMDGPU_PTE_MTYPE_GFX12(MTYPE_NC);
> > > +   *flags |= (*flags & ~AMDGPU_PTE_MTYPE_GFX12_MASK) |
> > > +   AMDGPU_PTE_MTYPE_GFX12(MTYPE_NC);
> >
> > Maybe we should make the AMDGPU_PTE_MTYPE_GFX12() macro clear the
> > current field before setting the new one?  That would align with the
> > similar register field macros.
>
> The AMDGPU_PTE_MTYPE_GFX12() macro is used mtype as input,  if we align
> with Register field setting, we need use uint64 flags as input.
>
> If we do like below:
>
> -#define AMDGPU_PTE_MTYPE_GFX12(a)   ((uint64_t)(a) << 54)
> -#define AMDGPU_PTE_MTYPE_GFX12_MASK
> AMDGPU_PTE_MTYPE_GFX12(3ULL)
> +#define AMDGPU_PTE_MTYPE_GFX12_SHIFT(mtype) ((uint64_t)(mytype)
> << 54)
> +#define AMDGPU_PTE_MTYPE_GFX12_MASK
> AMDGPU_PTE_MTYPE_GFX12_SHIFT(3ULL)
> +#define AMDGPU_PTE_MTYPE_GFX12(flags)   \
> +((flags) & ((~AMDGPU_PTE_MTYPE_GFX12_MASK)) | (flags))

Just igore my comment before. We need both flags and MTYPE as input.

I will send V2 version for this.

>
> We need to change the memory type setting from
> AMDGPU_PTE_MTYPE_GFX12(MTYPE_NC) to
> AMDGPU_PTE_MTYPE_GFX12(AMDGPU_PTE_MTYPE_GFX12_SHIFT(MTYPE_
> NC)).
> This makes the code look more complicated.
>
>
> Another way is to add one more macro AMDGPU_UPDATE/SET_PTE
> _MTYPE_GFX12.
> #define AMDGPU_ UPDATE_PTE_MTYPE_GFX12(flags) \
>   ((flags) & ((~AMDGPU_PTE_MTYPE_GFX12_MASK)) | (flags))
>
> Which of the above two methods do you think is more suitable?
> If neither of these methods are suitable, do you have any other suggestions?




>
>
> Best Regards,
> Shane
>
> >
> > Alex
> >
> > >
> > >  }
> > >
> > > --
> > > 2.25.1
> > >

RE: [PATCH] drm/amdkfd: Correct the GFX12 memory type setting

[Xiao, Shane]

[AMD Official Use Only - AMD Internal Distribution Only]

> -Original Message-
> From: Alex Deucher 
> Sent: Friday, May 17, 2024 11:52 PM
> To: Xiao, Shane 
> Cc: amd-gfx@lists.freedesktop.org; Kuehling, Felix
> ; Somasekharan, Sreekant
> ; Liu, Aaron ;
> Yao, Longlong 
> Subject: Re: [PATCH] drm/amdkfd: Correct the GFX12 memory type setting
>
> On Fri, May 17, 2024 at 3:07 AM Shane Xiao  wrote:
> >
> > This patch fixes the GFX12 memory type to NC. Since the Memory type
> > can be overwritten by the previous operations, the GFX12 MTYPE bits
> > need to be clear before setting to NC.
> >
> > Signed-off-by: longlyao 
> > Signed-off-by: Shane Xiao 
> > ---
> >  drivers/gpu/drm/amd/amdgpu/gmc_v12_0.c | 3 ++-
> >  1 file changed, 2 insertions(+), 1 deletion(-)
> >
> > diff --git a/drivers/gpu/drm/amd/amdgpu/gmc_v12_0.c
> > b/drivers/gpu/drm/amd/amdgpu/gmc_v12_0.c
> > index e2c6ec3cc4f3..6246d1dc0d30 100644
> > --- a/drivers/gpu/drm/amd/amdgpu/gmc_v12_0.c
> > +++ b/drivers/gpu/drm/amd/amdgpu/gmc_v12_0.c
> > @@ -534,7 +534,8 @@ static void gmc_v12_0_get_vm_pte(struct
> > amdgpu_device *adev,
> >
> > /* WA for HW bug */
> > if (is_system || ((bo_adev != adev) && coherent))
> > -   *flags |= AMDGPU_PTE_MTYPE_GFX12(MTYPE_NC);
> > +   *flags |= (*flags & ~AMDGPU_PTE_MTYPE_GFX12_MASK) |
> > +   AMDGPU_PTE_MTYPE_GFX12(MTYPE_NC);
>
> Maybe we should make the AMDGPU_PTE_MTYPE_GFX12() macro clear the
> current field before setting the new one?  That would align with the similar
> register field macros.

The AMDGPU_PTE_MTYPE_GFX12() macro is used mtype as input,  if we align with
Register field setting, we need use uint64 flags as input.

If we do like below:

-#define AMDGPU_PTE_MTYPE_GFX12(a)   ((uint64_t)(a) << 54)
-#define AMDGPU_PTE_MTYPE_GFX12_MASK AMDGPU_PTE_MTYPE_GFX12(3ULL)
+#define AMDGPU_PTE_MTYPE_GFX12_SHIFT(mtype) ((uint64_t)(mytype) << 54)
+#define AMDGPU_PTE_MTYPE_GFX12_MASK AMDGPU_PTE_MTYPE_GFX12_SHIFT(3ULL)
+#define AMDGPU_PTE_MTYPE_GFX12(flags)   \
+((flags) & ((~AMDGPU_PTE_MTYPE_GFX12_MASK)) | (flags))

We need to change the memory type setting from AMDGPU_PTE_MTYPE_GFX12(MTYPE_NC) 
to
AMDGPU_PTE_MTYPE_GFX12(AMDGPU_PTE_MTYPE_GFX12_SHIFT(MTYPE_NC)).
This makes the code look more complicated.


Another way is to add one more macro AMDGPU_UPDATE/SET_PTE _MTYPE_GFX12.
#define AMDGPU_ UPDATE_PTE_MTYPE_GFX12(flags)   \
    ((flags) & ((~AMDGPU_PTE_MTYPE_GFX12_MASK)) | (flags))

Which of the above two methods do you think is more suitable?
If neither of these methods are suitable, do you have any other suggestions?


Best Regards,
Shane

>
> Alex
>
> >
> >  }
> >
> > --
> > 2.25.1
> >

[dns-wg] Fwd: [ripe-list] DNS Resolver Recommendations Published (ripe-823)

[Shane Kerr]

Dear RIPE DNS working group,

Here is a belated notice that the DNS Resolver Recommendations document 
was published a couple of weeks ago. Apologies for not mentioning it sooner!


Cheers,

--
Shane
--- Begin Message ---
Dear colleagues,

I am happy to inform you that the RIPE DNS Resolver Best Common Practice 
Task Force [1] finished its work and published a set of recommendations 
and best current practices for operators of DNS resolvers - now 
available as RIPE Document 823:

https://www.ripe.net/publications/docs/ripe-823/

I would like to take this opportunity to thank all task force members 
for their contributions to this document and especially Shane Kerr who 
chaired the group and ensured that progress was made and that all 
feedback was heard and considered by the task force.

Kind regards,
Mirjam Kühne
RIPE Chair

[1] The RIPE DNS Resolver Best Common Practice Task Force
https://www.ripe.net/community/tf/dns-resolver-best-common-practice-task-force/ 



-- 

To unsubscribe from this mailing list, get a password reminder, or change your 
subscription options, please visit: 
https://lists.ripe.net/mailman/listinfo/ripe-list
--- End Message ---


OpenPGP_0x3732979CF967B306.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature
-- 

To unsubscribe from this mailing list, get a password reminder, or change your 
subscription options, please visit: 
https://lists.ripe.net/mailman/listinfo/dns-wg

[PATCH] drm/amdkfd: Correct the GFX12 memory type setting

[Shane Xiao]

This patch fixes the GFX12 memory type to NC. Since
the Memory type can be overwritten by the previous
operations, the GFX12 MTYPE bits need to be clear
before setting to NC.

Signed-off-by: longlyao 
Signed-off-by: Shane Xiao 
---
 drivers/gpu/drm/amd/amdgpu/gmc_v12_0.c | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/drivers/gpu/drm/amd/amdgpu/gmc_v12_0.c 
b/drivers/gpu/drm/amd/amdgpu/gmc_v12_0.c
index e2c6ec3cc4f3..6246d1dc0d30 100644
--- a/drivers/gpu/drm/amd/amdgpu/gmc_v12_0.c
+++ b/drivers/gpu/drm/amd/amdgpu/gmc_v12_0.c
@@ -534,7 +534,8 @@ static void gmc_v12_0_get_vm_pte(struct amdgpu_device *adev,
 
/* WA for HW bug */
if (is_system || ((bo_adev != adev) && coherent))
-   *flags |= AMDGPU_PTE_MTYPE_GFX12(MTYPE_NC);
+   *flags |= (*flags & ~AMDGPU_PTE_MTYPE_GFX12_MASK) |
+   AMDGPU_PTE_MTYPE_GFX12(MTYPE_NC);
 
 }
 
-- 
2.25.1

[jira] [Created] (NIFI-13248) Add Flow Analysis report menu

[Shane Ardell (Jira)]

Shane Ardell created NIFI-13248:
---

 Summary: Add Flow Analysis report menu
 Key: NIFI-13248
 URL: https://issues.apache.org/jira/browse/NIFI-13248
 Project: Apache NiFi
  Issue Type: Sub-task
  Components: Core UI
Reporter: Shane Ardell
Assignee: Shane Ardell


In keeping feature parity with the new ui, we should recreate the work done 
here: https://github.com/apache/nifi/pull/8273



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

Re: [FFmpeg-user] A53 Captions Garbled If Frame Duplication Occurs

[Shane Warren]

Devin,

Thanks for the tips, I tried using the fps filter (and omitting -v) but this 
stream I'm testing on still gets garbled captions using either method. I have 
tried hardware encoding (h264_nvenc) and software encoding (libx264) both 
produce garbled captions using the fps filter.

If I use an old ffmpeg from before that checkin (which I noted earlier), both 
the fps filter and -v produce valid captions on output. Anything past that 
checkin will not produce valid captions for this file.

Here is my software encoding command line:

ffmpeg -y -threads 2 -nostats  -loglevel verbose  -probesize 5M -filter_threads 
4  -fflags +genpts -fflags discardcorrupt  -i "/tmp/sample-low-framerate.ts"  
-map "0:v:0" -map "0:a:0"  -af "aresample=async=1,volume=1.00" -c:a:0 aac 
-threads 2 -ac:a:0 2 -ar:a:0 48000 -b:a:0 192k  -flush_packets 0 -vf 
"fps=fps=29.97"  -c:v libx264 -b:v 5500k -minrate:v 5500k -maxrate:v 5500k 
-bufsize:v 11000k -a53cc 1  -profile:v high -level:v 4.2 -bf:v 0 -g:v 15  -f 
mpegts  /tmp/subtitle-encode-test.ts

I made a short 30 second capture of the transport stream that causes this issue:

https://drive.google.com/file/d/1IJwqxG92LH4fDyoZp3qhBL50PErKxIYN/view?usp=drive_link

Here is the transcoded output where the captions are messed up:

https://drive.google.com/file/d/1cbpK5NVBHY73OI9rtbO9rvjeIWV_y0tI/view?usp=drive_link

Hopefully someone can identify what I'm doing wrong, I'm leaning towards a bug 
that has existing for a while though.

-Original Message-
From: ffmpeg-user  On Behalf Of Devin 
Heitmueller
Sent: Tuesday, May 7, 2024 10:21 AM
To: FFmpeg user questions 
Subject: Re: [FFmpeg-user] A53 Captions Garbled If Frame Duplication Occurs

This email originated from outside Innovative Systems. Do not click links or 
open attachments unless you recognize the sender and know the content is safe.


Hi Shane,

On Fri, May 3, 2024 at 5:48 PM Shane Warren  wrote:
>
> I ingest some multicast video that has a53 captions embedded in h264 video, 
> the video claims to have a framerate of 29.97 but it must not quite be that 
> because ffmpeg duplicates frames when transcoding this stream. The output 
> stream has a53 captions, but they appear to be somewhat garbled, like some 
> letters are duplicated, sometimes.
>
> I decided to git bisect since I knew this worked in a much older ffmpeg 
> binary I had. I finally found the commit that broke this:
>
> a11ab647304307d0340fd052e04cf638b6bef309 : fftools/ffmpeg: share the
> code encoding a single frame between video and audio
>
> Call do_video_stats() for every video packet produced by the encoder,
> rather than for every frame sent to the encoder.
>
> --
> --
>
> The key part that was missed in this commit was calling this directly after 
> avcodec_send_frame:
>
> // Make sure Closed Captions will not be duplicated
> av_frame_remove_side_data(in_picture, AV_FRAME_DATA_A53_CC);
>
> I fixed this in that commit, and captions worked again. I tried to fix it the 
> same way in a the current ffmpeg source by changing:
>
> ffmpeg_enc.c encode_frame:
>
> ret = avcodec_send_frame(enc, frame);
> if (ret < 0 && !(ret == AVERROR_EOF && !frame)) {
> av_log(ost, AV_LOG_ERROR, "Error submitting %s frame to the 
> encoder\n",
>type_desc);
> return ret;
> }
>
> +if (frame != NULL)
> +{
> +   av_frame_remove_side_data(frame, AV_FRAME_DATA_A53_CC);
> +}
>
> But that didn't fix the problem, I suspect this is needed when a frame is 
> duplicated, but I can't figure out the place to put that.
>
> Anyone have any ideas what I need to change to get captions working in the 
> current ffmpeg source?
> ___
> ffmpeg-user mailing list
> ffmpeg-user@ffmpeg.org
> https://ffmp/
> eg.org%2Fmailman%2Flistinfo%2Fffmpeg-user=05%7C02%7Cshanew%40inno
> vsys.com%7C4b7d6324d2b141517be908dc6ea95eff%7C7a48ce45ee974a95ac183390
> 878a179b%7C0%7C0%7C638506920940580581%7CUnknown%7CTWFpbGZsb3d8eyJWIjoi
> MC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7
> C=9664azc5fc%2BwKMnBGFjJVNFk9gM0Tx0u2mwLwho%2FZX0%3D=0
>
> To unsubscribe, visit link above, or email
> ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".

This was discussed last May in the following thread:

https://ffmpeg.org/pipermail/ffmpeg-devel/2023-June/310534.html

The easiest thing for you to do is use the "fps" filter (i.e. -vf
fps=6/1001) rather than using "-r".  That makes use of the ccfifo framework 
to ensure that the data is properly preserved.  The hack to do it with "-r" 
actually doesn't work correctly in a number

[FFmpeg-user] A53 Captions Garbled If Frame Duplication Occurs

[Shane Warren]

I ingest some multicast video that has a53 captions embedded in h264 video, the 
video claims to have a framerate of 29.97 but it must not quite be that because 
ffmpeg duplicates frames when transcoding this stream. The output stream has 
a53 captions, but they appear to be somewhat garbled, like some letters are 
duplicated, sometimes.

I decided to git bisect since I knew this worked in a much older ffmpeg binary 
I had. I finally found the commit that broke this:

a11ab647304307d0340fd052e04cf638b6bef309 : fftools/ffmpeg: share the code 
encoding a single frame between video and audio

Call do_video_stats() for every video packet produced by the encoder,
rather than for every frame sent to the encoder.



The key part that was missed in this commit was calling this directly after 
avcodec_send_frame:

// Make sure Closed Captions will not be duplicated
av_frame_remove_side_data(in_picture, AV_FRAME_DATA_A53_CC);

I fixed this in that commit, and captions worked again. I tried to fix it the 
same way in a the current ffmpeg source by changing:

ffmpeg_enc.c encode_frame:

ret = avcodec_send_frame(enc, frame);
if (ret < 0 && !(ret == AVERROR_EOF && !frame)) {
av_log(ost, AV_LOG_ERROR, "Error submitting %s frame to the encoder\n",
   type_desc);
return ret;
}

+if (frame != NULL)
+{
+   av_frame_remove_side_data(frame, AV_FRAME_DATA_A53_CC);
+}

But that didn't fix the problem, I suspect this is needed when a frame is 
duplicated, but I can't figure out the place to put that.

Anyone have any ideas what I need to change to get captions working in the 
current ffmpeg source?
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".

[jira] [Created] (NIFI-13125) UI - Add view for comparing different versions of registered flows

[Shane Ardell (Jira)]

Shane Ardell created NIFI-13125:
---

 Summary: UI - Add view for comparing different versions of 
registered flows
 Key: NIFI-13125
 URL: https://issues.apache.org/jira/browse/NIFI-13125
 Project: Apache NiFi
  Issue Type: New Feature
  Components: Core UI
Reporter: Shane Ardell
Assignee: Shane Ardell


NIFI-13030 adds a new endpoint for comparing different versions of registered 
flows. A new view should be added to the UI for users to compare different 
versions. This should list out all the differences returned from the backend 
and allow a user to choose between different versions.

+Notes:+
 - Selecting the same version for both sides of the comparison will display a 
message indicating no differences between the two versions.



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

Re: License for text content

[Shane Curcuru]

(Moving general@incubator and dev@community to BCC since this is really 
a legal question about ASF licensing)


tison wrote on 5/1/24 11:25 PM:

Hi,

IIUC, the Apache License 2.0 is mainly to license code and related stuff 
that constructs the final software.


However, projects may also create text content like documents. Is it 
appropriate to use Apache License 2.0 for them (since quite a few terms 
may not be applicable)? Or what licenses shall we use?


The ASF uses the Apache-2.0 license for our projects' own content that 
is put into any releases, immaterial of type of content:


https://apache.org/legal/src-headers.html#faq-docs

Using a single license reduces complexity, and makes it simpler for 
users to understand the issues around re-using ASF products.


--
- Shane
  Member
  The Apache Software Foundation


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: License for text content

[Shane Curcuru]

(Moving general@incubator and dev@community to BCC since this is really 
a legal question about ASF licensing)


tison wrote on 5/1/24 11:25 PM:

Hi,

IIUC, the Apache License 2.0 is mainly to license code and related stuff 
that constructs the final software.


However, projects may also create text content like documents. Is it 
appropriate to use Apache License 2.0 for them (since quite a few terms 
may not be applicable)? Or what licenses shall we use?


The ASF uses the Apache-2.0 license for our projects' own content that 
is put into any releases, immaterial of type of content:


https://apache.org/legal/src-headers.html#faq-docs

Using a single license reduces complexity, and makes it simpler for 
users to understand the issues around re-using ASF products.


--
- Shane
  Member
  The Apache Software Foundation


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

[Bug 2063883] Re: Resuming from suspend, desktop crashes

[Shane Ross]

After some research appears this bug/crash is related to display-port +
Dell usb-c docking station.

Closing this as not related to Ubuntu directly.

** Changed in: ubuntu
   Status: New => Invalid

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

Title:
  Resuming from suspend, desktop crashes

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


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

[Bug 2063883] [NEW] Resuming from suspend, desktop crashes

[Shane Ross]

Public bug reported:

1) lsb_release -rd:
No LSB modules are available.
Description:Ubuntu 24.04 LTS
Release:24.04

2) /proc/version_signature:
Ubuntu 6.8.0-31.31-generic 6.8.1

uname -a:
Linux slat 6.8.0-31-generic #31-Ubuntu SMP PREEMPT_DYNAMIC Sat Apr 20 00:40:06 
UTC 2024 x86_64 x86_64 x86_64 GNU/Linux


3) After resuming from power suspend, expect to see existing desktop session 
and apps prior to suspend

4) Waking from power suspend, desktop crashes and user asked to login
again, on doing so previous session is gone.

dmesg:
[114249.273903] PM: suspend entry (s2idle)
[114249.274164] Filesystems sync: 0.000 seconds
[114249.278175] Freezing user space processes
[114249.280510] Freezing user space processes completed (elapsed 0.002 seconds)
[114249.280514] OOM killer disabled.
[114249.280515] Freezing remaining freezable tasks
[114249.282384] Freezing remaining freezable tasks completed (elapsed 0.001 
seconds)
[114249.282388] printk: Suspending console(s) (use no_console_suspend to debug)
[114249.768169] ACPI: EC: interrupt blocked
[161079.897587] ACPI: EC: interrupt unblocked
[161080.113134] i915 :00:02.0: [drm] GT0: GuC firmware i915/adlp_guc_70.bin 
version 70.20.0
[161080.113148] i915 :00:02.0: [drm] GT0: HuC firmware i915/tgl_huc.bin 
version 7.9.3
[161080.128217] iwlwifi :00:14.3: WRT: Invalid buffer destination
[161080.131053] i915 :00:02.0: [drm] GT0: HuC: authenticated for all 
workloads
[161080.131522] i915 :00:02.0: [drm] GT0: GUC: submission enabled
[161080.131527] i915 :00:02.0: [drm] GT0: GUC: SLPC enabled
[161080.131999] i915 :00:02.0: [drm] GT0: GUC: RC enabled
[161080.165738] nvme nvme0: 12/0/0 default/read/poll queues
[161080.286655] iwlwifi :00:14.3: WFPM_UMAC_PD_NOTIFICATION: 0x20
[161080.286665] iwlwifi :00:14.3: WFPM_LMAC2_PD_NOTIFICATION: 0x1f
[161080.286672] iwlwifi :00:14.3: WFPM_AUTH_KEY_0: 0x90
[161080.286680] iwlwifi :00:14.3: CNVI_SCU_SEQ_DATA_DW9: 0x0
[161080.287989] iwlwifi :00:14.3: RFIm is deactivated, reason = 4
[161082.464183] OOM killer enabled.
[161082.464187] Restarting tasks ... 
[161082.464287] usb 2-1.3: USB disconnect, device number 3
[161082.464353] usb 2-1: USB disconnect, device number 2
[161082.464363] usb 3-1: USB disconnect, device number 4
[161082.464373] usb 3-1.2: USB disconnect, device number 5
[161082.467680] int3472-discrete INT3472:06: cannot find GPIO chip INTC100B:00, 
deferring
[161082.468418] done.
[161082.468434] random: crng reseeded on system resumption
[161082.473105] mei_hdcp :00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: 
bound :00:02.0 (ops i915_hdcp_ops [i915])
[161082.474816] mei_pxp :00:16.0-fbf6fcf1-96cf-4e2e-a6a6-1bab8cbe36b1: 
bound :00:02.0 (ops i915_pxp_tee_component_ops [i915])
[161082.477809] audit: type=1107 audit(1714160826.354:487): pid=2127 uid=100 
auid=4294967295 ses=4294967295 subj=unconfined msg='apparmor="DENIED" 
operation="dbus_signal"  bus="system" path="/org/freedesktop/login1" 
interface="org.freedesktop.DBus.Properties" member="PropertiesChanged" 
name=":1.14" mask="receive" pid=6423 label="snap.firefox.firefox" peer_pid=2179 
peer_label="unconfined"
 exe="/usr/bin/dbus-daemon" sauid=100 hostname=? addr=? 
terminal=?'
[161082.483496] r8152-cfgselector 2-1.4: USB disconnect, device number 4
[161082.582018] int3472-discrete INT3472:06: cannot find GPIO chip INTC100B:00, 
deferring
[161082.586494] usb 3-1.3: USB disconnect, device number 6
[161082.586507] usb 3-1.3.1: USB disconnect, device number 8
[161082.688309] PM: suspend exit
[161082.771183] audit: type=1400 audit(1714160826.647:488): apparmor="DENIED" 
operation="open" class="file" profile="snap.firmware-updater.firmware-notifier" 
name="/proc/sys/vm/max_map_count" pid=36059 comm="firmware-notifi" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
[161082.853369] usb 3-1.3.2: USB disconnect, device number 9
[161082.906754] usb 3-1.3.5: USB disconnect, device number 10
[161082.943707] usb 3-1.5: USB disconnect, device number 7
[161083.157114] audit: type=1107 audit(1714160827.033:489): pid=2127 uid=100 
auid=4294967295 ses=4294967295 subj=unconfined msg='apparmor="DENIED" 
operation="dbus_signal"  bus="system" path="/org/freedesktop/login1" 
interface="org.freedesktop.DBus.Properties" member="PropertiesChanged" 
name=":1.14" mask="receive" pid=6423 label="snap.firefox.firefox" peer_pid=2179 
peer_label="unconfined"
 exe="/usr/bin/dbus-daemon" sauid=100 hostname=? addr=? 
terminal=?'
[161083.181074] [UFW BLOCK] IN=wlp0s20f3 OUT= MAC= SRC=10.0.60.11 
DST=239.255.255.250 LEN=635 TOS=0x00 PREC=0x00 TTL=1 ID=34871 DF PROTO=UDP 
SPT=37939 DPT=3702 LEN=615 
[161083.181320] [UFW BLOCK] IN=wlp0s20f3 OUT= MAC= 
SRC=fe80::::2e25:f35d:68f5:5ead 
DST=ff02:::::::000c LEN=655 TC=0 HOPLIMIT=1 
FLOWLBL=371897 PROTO=UDP SPT=57938 DPT=3702 LEN=615 
[161083.181455] [UFW BLOCK] IN=virbr0 OUT= MAC= SRC=192.168.122.1 

[marxmail] Political Economy Reading Group - NEW READING STARTS May 5th

[Shane Hopkinson]

Just a heads up that on May 5th Marx's Political Economy Reading group will
start reading the 'Results of the immediate process of production". We are
a group with members around the globe. This is a good opportunity to join
us at the start of a new reading on Sunday May 5th: Sydney 11PM/London
2PM/New York 9AM for 2 hours.
We try to cover about 10-15 pages a week. Please ask to join the Facebook
group <https://www.facebook.com/groups/243705580211832> and/or we can sign
you up to our gmail list
<https://groups.google.com/g/marxs_political_economy_reading_group>.
Comradely
Shane H
Convenor.


--


-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#30085): https://groups.io/g/marxmail/message/30085
Mute This Topic: https://groups.io/mt/105744499/21656
-=-=-
POSTING RULES & NOTES
#1 YOU MUST clip all extraneous text when replying to a message.
#2 This mail-list, like most, is publicly & permanently archived.
#3 Subscribe and post under an alias if #2 is a concern.
#4 Do not exceed five posts a day.
-=-=-
Group Owner: marxmail+ow...@groups.io
Unsubscribe: https://groups.io/g/marxmail/leave/8674936/21656/1316126222/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[jira] [Commented] (WHIMSY-414) Roll call tool to simplify PMC roll calls

[Shane Curcuru (Jira)]

[ 
https://issues.apache.org/jira/browse/WHIMSY-414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17840520#comment-17840520
 ] 

Shane Curcuru commented on WHIMSY-414:
--

Agreed: each PMC's roll calls should only be accessible by that PMC by default 
(and all Members as well per usual policy).  This is data the board needs quick 
and simple access to, because the board is evaluating project health; but it's 
not something we otherwise should be providing access to.

Any potential workflow should also store:
 * Director leading the roll call
 * date started / date expected to be finished (commits are fine after that 
date, but having a report on what was done before the X days deadline is useful)
 * (bonus) paragraph of what the Director writes as to why the board is asking 
for a roll call, so we can store at least some hand-written explanation of why 
this was done at that time.

> Roll call tool to simplify PMC roll calls
> -
>
> Key: WHIMSY-414
> URL: https://issues.apache.org/jira/browse/WHIMSY-414
> Project: Whimsy
>  Issue Type: New Feature
>  Components: Roster
>Reporter: Craig L Russell
>Priority: Major
>
> During review of project board reports, directors encounter projects that 
> seem to be in decline. In order to determine whether the PMC is healthy 
> enough for proper oversight, the board requests a roll call and assigns an 
> action item to a director.
> To start the roll call, a director goes to the Whimsy roster page for the 
> PMC, and clicks "send roll call".  Director writes out an explanation of any 
> specific board concerns, which is then sent out along with a boilerplate 
> explanation of the roll call process, along with a "reply by this date to 
> roll call here" link.
> PMC members click the link (which auth's them), fill out short form, and 
> click submit.  The board really needs to know the "how engaged are you" 
> detail, and we could also have an extra comments field where PMC members 
> might add extra data.
> Every submission results in a commit (by Whimsy) into a private repository 
> (visible to Members and Officers) as well as an email to board@ and 
> private@. The repository should be easy to search by name by 
> logged-in users, e.g.
> [https://svn.apache.org/repos/private/pmc//|https://svn.apache.org/repos/private/pmc/]roll-call/2024-04-01/.json.
>   
> The above directory will be created at the time the roll call request is 
> being executed. The private/pmc// directory might need to be created 
> by Whimsy if no roll call or other reason has been seen for this PMC. 
>  
> PMC members should be allowed to save their responses in a specific roll call 
> request directory
> PMC members should be allowed to review/read responses from their peers in 
> any of their svn project roll call directories 
> Members and Officers should be allowed to review/read responses from any of 
> the repositories
> Other access should be disallowed
> It's easy to track responses by Apache ID, and by date of response, as well 
> as have a simple read-only dashboard showing the outcome of each roll call, 
> assuming the right privileges.
> PMC members could also see each others' responses in email.
> Working example (you will be auth'd by your Apache ID):
> [https://whimsy.apache.org/officers/surveys?survey=test-rollcall.json]
> In this POC, commits go to foundation/officers/surveys.



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

Re: [DISCUSS] UI Contributions

[Shane Ardell]

I also agree with this stance for an initial period of transition time, but
this obviously has a huge impact on contributions. Without any kind of end
date, I worry this is going to be policy indefinitely. Because of this, I
tend to agree with what Rob said in the previous email. Maybe once 2.0 is
released, that's the end of this transition period where UI features must
be implemented twice (unless desired or needed for backward compatibility,
as Rob pointed out).

On Wed, Apr 24, 2024 at 8:17 AM Robert Fellows 
wrote:

> The new UI has progressed quite well and I agree with this stance. However,
> with 2.0 getting close, one could argue that new UI features should
> definitely land in the new UI but only really need to land in the original
> UI if desired or to support backward compatibility.
>
> --Rob
>
> On Tue, Apr 23, 2024 at 7:55 PM Scott Aslan  wrote:
>
> > Thanks for sending this out Matt! I agree that at this point any new
> > features to the frontend should be implemented in both the new and the
> > existing UI. Updating the contributions guidelines seems appropriate as
> > well.
> >
> > -Scott
> >
> > On Tue, Apr 23, 2024 at 4:07 PM Matt Gilman  wrote:
> >
> > > Team,
> > >
> > > Substantial progress has been made on modernizing the NiFi UI under [1]
> > and
> > > [2]. As detailed in the JIRAs, this effort has been largely motivated
> by
> > > moving away from deprecated and unsupported dependencies. As we begin
> the
> > > process to transition to the new UI, we are at a point where any UI
> > > contributions should target both the new UI and the existing UI. We've
> > > updated the PR template detailing this and the README for the new UI
> [3]
> > to
> > > help introduce folks making UI contributions to the layout of the
> > > repository. It discusses the steps needed to build NiFi with the new UI
> > > included and how to access it.
> > >
> > > Happy to discuss any questions folks may have.
> > >
> > > Matt
> > >
> > > [1] https://issues.apache.org/jira/browse/NIFI-11481
> > > [2] https://issues.apache.org/jira/browse/NIFI-12400
> > > [3] https://github.com/apache/nifi/pull/8693
> > >
> >
>
>
> --
> ---
> Rob Fellows
>

[PDB Announce] Production Deployment 2.57.0

[Shane Wadleigh]

2.57.0 was successfully released to production, changes can be viewed at [0].

If anyone encounters any problems, please contact supp...@peeringdb.com

Cheers

[0] https://docs.peeringdb.com/release_notes/
___
Pdb-announce mailing list
Pdb-announce@lists.peeringdb.com
https://lists.peeringdb.com/cgi-bin/mailman/listinfo/pdb-announce

Re: Commit: patch 9.1.0342: tests: test_taglist fails when 'helplang' contains non-english

[shane qian]

ok, whatever, it's not my problem or it was not an issue I made it, so you can 
choose the way whatever you like.

if there suggestion:
1, my workaround perhaps was better, whatever there were tags-ru, and/or 
tags-de, etc, it should be no err or no block from that test.
2, to real solution, I may suggest review that check-in code in makefile for 
tags-ru again, it had made some issues.

that's all.

--
shane.xb.qian

-- 
-- 
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/OS3P286MB0913B4D1C2C3DC98DCB242A9EB0F2%40OS3P286MB0913.JPNP286.PROD.OUTLOOK.COM.

Re: Commit: patch 9.1.0342: tests: test_taglist fails when 'helplang' contains non-english

[shane qian]

the ticket description is the description, not the ticket title, please check 
that. I am not near my PC, otherwise I should would be glad to spell out to you.

--
shane.xb.qian

-- 
-- 
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/OS3P286MB09134F4D6037893A625EAA75EB0F2%40OS3P286MB0913.JPNP286.PROD.OUTLOOK.COM.

Re: Commit: patch 9.1.0342: tests: test_taglist fails when 'helplang' contains non-english

[shane qian]

the `clear` problem is in the ticket description: a comment link, which was 
someone described or complained in another ticket.
seems you did not check that carefully, the problem is there not only 1 tag 
file.

--
shane.xb.qian

-- 
-- 
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/OS3P286MB0913B6B957FE9EF92ABA49B0EB0F2%40OS3P286MB0913.JPNP286.PROD.OUTLOOK.COM.

[marxmail] Loren Goldner ¡Presente!

[Shane Hopkinson]

I have just learned of the death of comrade Loren Goldner on April 12, aged
76. While we had intermittent email exchanges over the years he was a big
influence on me in the mid-2000's as I was rethinking my commitment to
the pretty conventional Trotskyist politics of my student days.
He was a multilingual Intellectual and activist in the left-communist
tradition. He was conservant in philosophy and economics. He wrote his PhD
on Herman Melville (subtitled 'between Charlemagne and the ante mosaic
cosmic man') and was part of producing the journal 'Race Traitor' and more
recently 'Insurgent Notes.' He promoted the relevance of both Guy DeBord
and Amadeo Bordiga. Lest that give the impression he was something of an
academic - he toured the world studying working class movements, lecturing
on Marx's critique of political economy, the 2nd International radicals -
Lenin, Luxemburg and Trotsky. Over the decade he's dedicated his time to
 serious study (including travelling in East Asia) of the Chinese working
class, who he felt, in many ways, held the future of the world in their
hands.

There is an online archive of his writing at his website: Break their
haughty power 

--


-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#29945): https://groups.io/g/marxmail/message/29945
Mute This Topic: https://groups.io/mt/105570771/21656
-=-=-
POSTING RULES & NOTES
#1 YOU MUST clip all extraneous text when replying to a message.
#2 This mail-list, like most, is publicly & permanently archived.
#3 Subscribe and post under an alias if #2 is a concern.
#4 Do not exceed five posts a day.
-=-=-
Group Owner: marxmail+ow...@groups.io
Unsubscribe: https://groups.io/g/marxmail/leave/8674936/21656/1316126222/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [atlas] Reverse traceroute

[Shane Kerr]

Hank,

On 16/04/2024 19.44, Hank Nussbacher wrote:

https://pulse.internetsociety.org/blog/reverse-traceroutes-help-troubleshoot-improve-visibility-of-internets-health

"Measure at least one reverse path from 39,544 Autonomous System (AS) 
destinations, which host 92.6% of Internet users. As a comparison, RIPE 
Atlas vantage points can measure from 4,344 AS destinations, 
representing 67.1% of the Internet user base."


This particular metric feels highly-contrived... as if to highlight one 
specific property that their system excels at. Number of ASN doesn't 
mean that much really... a single vantage point at Comcast would account 
for 30 million customers and probably twice that many users, but not 
actually tell you much about the network for the vast majority of those 
users.


It seems like the effort is targeted at operators and not end users, 
with the selling point is to provide a win-win situation, where 
operators gain useful metrics and the researchers learn about the 
network. This would encourage operators to run their code, and the 
researchers could more easily coax them to run their tool, getting these 
impressive numbers. (I haven't read the paper of course, because 
apparently the ACM is not open access and honestly I don't feel like 
spending $15 for access.)


My understanding is that RIPE Atlas is mostly targeted at end users, not 
operators, so probably a bit harder to get probes placed, as it has no 
direct benefit for operators... and in fact could reveal details about 
their network and the quality of their service that they would not care 
to share. This is not *completely* true, as there are the RIPE Atlas 
Anchors, which I think are intended to run as infrastructure nodes, but 
mostly.



Has anyone tried this and indeed found better visibility via their system?


I have not. It looks less flexible than Atlas, but also nice and simple!

Thanks for pointing it out.

Cheers,

--
Shane



OpenPGP_0x3732979CF967B306.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature
-- 
ripe-atlas mailing list
ripe-atlas@ripe.net
https://lists.ripe.net/mailman/listinfo/ripe-atlas

[dev] ASF Board Report for Libcloud - Repeated Reminder for April 2024

[Shane Curcuru]

Dear Libcloud community,

In the Apache governance model, the ASF board delegates responsibility for
managing projects to PMCs. This allows projects to govern themselves, in terms
of their own development goals, guidelines, and volunteer spirit, within the
scope of our purpose as an open source foundation. The state allows us to
supply an umbrella of corporate protection to our projects and volunteers, but
only to the extent that we retain active and effective oversight of each
project's operation on behalf of the public's interest.

To enable the board to provide oversight across the foundation, each PMC is
tasked with providing the board a quarterly report on the health of their
project. This allows us to hear your heartbeat, to see the project through
your eyes, and to inform the public through our meeting minutes.

The board has noticed that the reports for Libcloud have been missed
for a number of months. This makes us sad because we have lost that ability
to communicate with you, to see what may be preventing your good health,
and to ensure that we are providing the services that you need to continue
as an Apache project.

The reports to the board are normally written by the PMC chair but all PMC
members have an individual responsibility to ensure that a report is
submitted. If the PMC chair is not available then any PMC member can submit
the report. If you need help with this process, please reach out to
bo...@apache.org

Please ensure that a report for Libcloud is submitted to the board
for the next meeting on Wed, 17 Apr 2024 at 21:00 UTC.

If the PMC chair is not going to be available for an extended period of time,
it may make sense to rotate the PMC chair. Rotating the PMC chair does not
mean the current chair has failed. People's situations and interests change;
rotation is good as it allows more people to become familiar with that role.
Again, if assistance is required with this process, please feel free to
reach out to bo...@apache.org

As projects mature, they will naturally reach a point where activity reduces
to a level that the project is no longer sustainable. At Apache, projects
reach this stage when there are no longer 3 active PMC members providing
oversight. Projects that reach this stage are placed in our Attic, where
they continue to be accessible to the public but are not portrayed as having
an active community for maintenance.

http://attic.apache.org/

If Libcloud has reached this point, please reach out to the Attic project
to arrange transfer. On the other hand, if your project is mostly dormant but
still has at least three active PMC members, it can remain in that state for
as long as needed. If your project is in such a state, please mention that in
your report and verify the PMC's state at regular intervals.

Finally, if you have any questions, please feel free to reach out to
bo...@apache.org.

Thanks,
The ASF Board

Re: [ncc-services-wg] Enhancing the Security of RIPE NCC Access

[Shane Kerr]

Filipe,

On 10/04/2024 15.08, Felipe Victolla Silveira wrote:


Over the past few months, the RIPE NCC has been working on enhancing the 
security of RIPE NCC Access. In a new article on RIPE Labs, I explain 
the recent enhancements we've implemented and provide an overview of 
forthcoming developments you can anticipate from us:


https://labs.ripe.net/author/felipe_victolla_silveira/enhancing-the-security-of-ripe-ncc-access-recent-and-upcoming-changes/ 


Thanks for this! I appreciate this sort of "under the hood" look at RIPE 
NCC infrastructure.


I was very happy that the RIPE NCC decided to use an open source 
implementation rather than a proprietary service for IAM!


I was less thrilled that it is deployed on AWS. This means that 
everything that the RIPE NCC oversees that requires authentication - 
including things like voting for certain RIPE roles such as the RIPE PC 
I think - depends on Amazon. That feels wrong for a lot of reasons, but 
here we are.


Cheers,

--
Shane


OpenPGP_0x3732979CF967B306.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature
-- 

To unsubscribe from this mailing list, get a password reminder, or change your 
subscription options, please visit: 
https://lists.ripe.net/mailman/listinfo/ncc-services-wg

[jira] [Resolved] (NIFI-12999) UI - local build fails because of updated nifi-registry dependency

[Shane Ardell (Jira)]

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

Shane Ardell resolved NIFI-12999.
-
Resolution: Not A Problem

There's a configuration property for npm called {{{}engine-strict{}}}. When set 
to true, version mismatches will cause a failure. This was the cause of the 
issue on my machine.

> UI - local build fails because of updated nifi-registry dependency
> --
>
> Key: NIFI-12999
> URL: https://issues.apache.org/jira/browse/NIFI-12999
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: NiFi Registry
>Reporter: Shane Ardell
>Assignee: Shane Ardell
>Priority: Major
> Attachments: revert-1.png, revert-2.png
>
>  Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> When attempting to build a local version of NiFi on my machine, the build 
> fails when attempting to install npm dependencies for nifi-registry. See 
> attached screenshots for more details.



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

[jira] [Created] (NIFI-12999) UI - local build fails because of updated nifi-registry dependency

[Shane Ardell (Jira)]

Shane Ardell created NIFI-12999:
---

 Summary: UI - local build fails because of updated nifi-registry 
dependency
 Key: NIFI-12999
 URL: https://issues.apache.org/jira/browse/NIFI-12999
 Project: Apache NiFi
  Issue Type: Bug
  Components: NiFi Registry
Reporter: Shane Ardell
Assignee: Shane Ardell
 Attachments: revert-1.png, revert-2.png

When attempting to build a local version of NiFi on my machine, the build fails 
when attempting to install npm dependencies for nifi-registry. See attached 
screenshots for more details.



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

Trademarks and incubation (was: [DISCUSS] Graduate Apache AGE Incubating as a Top Level Project)

[Shane Curcuru]

Question: where did the incubation process fail in this case?  How can 
we prevent something like this from happening again?


On 2021/12/20 22:50:13 Eya Badal Abdisho wrote:

Hello Justin,

Thank you for your feedback. Please find more information following:


...snip...> - There are some minor trademark issues on the Bitnine site 
e.g [2] → All

will be fixed in a day.


One issue today is that both the Bitnine site advertises several 
software products with names that start with "AGE...", including a 
graph-based tool.  The other issue is that AgeDB is a company using 
similar names and branding as Apache Age.


These issues clearly weren't fixed, nor do they appear to really have 
been seriously addressed in the past two years.


  https://bitnine.net/
  https://agedb.io/

...snip...

- I notice one person who replied to this thread had a agedb.io email
address - what is it relationship with the project?

Agedb is a US startup (incorporated in California May this year) and is
affiliated with Bitnine Global, who contributed the original AGE source
codes to the Apache Software Foundation. The purpose of Agedb is not yet
clearly defined but it is expected to be to provide graph database
solutions and related services.


I definitely appreciate our Incubator mentors, who do an incredible job 
in their volunteer time.  Helping build communities is hard work, and is 
to be celebrated.


How can we improve documentation, education, or training so that the 
below sentence would leap out at any mentor as a "You can't do that!"


"purpose of Agedb is ... provide graph database solutions and related 
services"


Given we were trying to incubate Apache AGE as a graph database, the 
above sentence is literally describing trademark infringement!  How can 
we make it easier to ensure podlings and their donating organizations 
actually take trademark transfer seriously?


--
- Shane
  Member
  The Apache Software Foundation

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Getting a project back on track

[Shane Curcuru]

Rich Bowen wrote on 3/29/24 9:35 AM:

This week, I’ve been approached by someone concerned about one of our projects, 
and looking for a “how to get back on track” document, with concrete, 
actionable steps that a project can take when it is struggling to find 
contributors. This seems like a great doc that we should write. What comes to 
mind is:

* Clearly tell the dev@ and user@ list that the project is at risk if they 
don’t step up
* Publish a list of open issues to the Dev list
* Contact companies that you know rely on your outputs, and tell them that the 
project is at risk
* Clearly document the path/requirements for getting committer. Consider 
lowering your wall a little
* What else?


* Roadmap - consider publishing a roadmap of what 
features/ideas/improvements to build/docs/etc the project wants to 
implement.  Give contributors a sense of new things that they could help 
build, and a sense the project is still going someplace.


* Double-check your "how to contribute / build / test / submit PR" 
documentation is super clear and easy to follow.  Long-time committers 
on a project often forget all the institutional knowledge they just 
"know", so ensuring the "getting started" document actually works for 
newcomers is always worth looking at.



Another question that I have is where to put this doc. I’m thinking it goes in 
https://github.com/apache/comdev-site/tree/main/source/pmc somewhere, but I’m 
not sure that to name it.


Yes - primarily advice to PMCs (or active committers).  There are two 
potential primary audiences:


- PMCs that can't find new committers, and ask for help.

- PMCs who might want to regularly self-review how they're working, to 
see if they can improve things for new contributors.


It's kinda "How to encourage new contributors to turn into committers"?

--
- Shane
  Member
  The Apache Software Foundation


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

Re: "Maintainer" as an alias of PMC Member?

[Shane Curcuru]

Just to close out (as noted elsethread, no changes expected here)

tison wrote on 3/23/24 4:47 AM:
...snip...

Since people tend to use a short ref and "committer" gives a one-word
identifier first image, I'm trying to propose officially alias "PMC Member"
as "Maintainer" so that our wording is aligned.


I like the idea of improving docs, but a Maintainer is not the same as a 
PMC member.  The definition varies a lot in the industry; in particular, 
I always get the feel that "Maintainers" have a much more individual 
mindset; while PMCs have a community mindset.


Some references for what people think Maintainers do:

  https://fosssustainability.com/aspects/maintainer#references

--
- Shane
  Member
  The Apache Software Foundation


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

Assistance with surveys write error

[Shane Curcuru]

If anyone can spot my error when submitting to officers/surveys, I'd 
love help understanding how this is not working, even though the form 
submission code seems to be exactly the same structure as coi and 
mentor-update are (which work).


Checkout works fine, but I can't write to the file:

#/srv/svn/officers_surveys/boardf2f2024-data.json>

  /x1/srv/whimsy/www/officers/surveys.cgi:129:in `write'
...

Separately, someday I'll get help to figure out why using GitHub desktop 
to submit PRs and merge them often litters the commit stream with an 
extra "Merge branch 'apache:master' into master" commit (with nothing in 
it).


Thanks!

--
- Shane
  Member
  The Apache Software Foundation

Re: New project invitations

[Shane Curcuru]

Craig Russell wrote on 3/21/24 12:20 AM:
...snip...

We really can do better, but we have to have better documentation.


Some folks have started working on improving the actual emails or links 
we use for onboarding at various steps of the process.  So if we're 
updating this step, folks might want to look at some of the other steps 
too, which are listed here:


https://cwiki.apache.org/confluence/display/COMDEV/Proposal%3A+Improving+Onboarding+Experiences

A separate question for committer invitation process is: each PMC/PPMC 
is responsible for some of the steps themselves.  How can we make 
simple/easy enough tools so that the experience for a new committer on 
any project or podling is at least similar?  It's pretty clear some 
projects have different ways of doing the welcoming process, some 
better, some not as good.



--
- Shane
  Member
  The Apache Software Foundation


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [db-wg] Complying with Mail Provider Requirements When Sending Mail from Whois

[Shane Kerr via db-wg]

Denis,

On 21/03/2024 04.03, denis walker via db-wg wrote:

-we have no documented business requirements for either the RIPE
Database or a public registry


This is simply not true.

https://www.ripe.net/publications/docs/ripe-767/

All because you disagree with the published requirements does not mean 
that they do not exist.



A Task Force was set up, I thought, to document the business
requirements for the RIPE Database and public registry. All they did
was look backwards and write a document on the history of the
database...many of us already knew that.


Similarly, it is simply not true that RIPE 767 only looks backwards. We 
have specific recommendations based on this which were outlined at RIPE 83.


It *IS* true that we did not recommend designing a complete new database 
model and writing software to implement it.


Designing new models or building a new implementation are not contrary 
to the requirements as documented by the task force, but they are not 
necessary for them either.



So finally the bottom line:
It really is time to start this conversation about the future of the
RIPE Database and the public registry.


If you actually want something different, then I think you have at least 
two ways forward:


1. Propose specific changes to the current RIPE Database and iterate 
towards perfection.


2. Propose a new model, and outline a way to migrate from the current 
system towards that.


Unfortunately many of the items listed in your e-mail are not 
actionable, so not appropriate for path #1. For example:


> -the current java based software was first written about 12 years ago

Some of the items listed in your e-mail are too broad and unspecified, 
so also not appropriate for path #1. For example:


> -it has privacy issues

This might be true, although in several cases you seem to disagree with 
the lawyers who have given advice about privacy issues in the database, 
and so your specific proposals are unnecessary according to experts. I 
am sure the community would welcome privacy improvements for any actual 
problems though.


Luckily there *ARE* things on the list that could be converted to 
specific proposals in line with path #1:


> -there is no simple way for data users to even query their own data, 
never mind manage it


I don't necessarily agree, since you can do an inverse query to find all 
of the objects that you maintain, but I guess you have something else in 
mind. Great! Propose it. A short document focused on this one specific 
issue would be much easier for people to get their heads around and 
could result in genuine improvement.


You seem to be more interested in path #2, but also unwilling to start 
the work on your own. I suppose that makes sense, since it is a lot of 
work that probably requires a broader skill-set than any one person has. 
But since nobody else seems to think it worth their personal investment 
of time, then I think that is your best bet. If you come up with some 
solid principles and approaches, that may attract more interest than 
repeatedly scolding your fellow community members.


Good luck!

Cheers,

--
Shane


OpenPGP_0x3732979CF967B306.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature
-- 

To unsubscribe from this mailing list, get a password reminder, or change your 
subscription options, please visit: 
https://lists.ripe.net/mailman/listinfo/db-wg

[PDB Announce] Production Deployment 2.56.0

[Shane Wadleigh]

2.56.0 was successfully released to production, changes can be viewed at [0].

If anyone encounters any problems, please contact supp...@peeringdb.com

Cheers

[0] https://docs.peeringdb.com/release_notes/
___
Pdb-announce mailing list
Pdb-announce@lists.peeringdb.com
https://lists.peeringdb.com/cgi-bin/mailman/listinfo/pdb-announce

[opensource-wg] Ukrainian open source app for citizen's digital documents & government services

[Shane Kerr]

Comrades in open source,

This popped up on my radar today:

https://opensource.diia.gov.ua/en.html

It seems like a good initiative, and in general I think that governments 
have a duty to make source code available whenever possible.


I checked the GitHub:

https://github.com/diia-open-source/

And it looks like all of the code is under the EUPL, which is a nice 
copyleft license.


However if you look at the main page there is a section titled Open 
Source Usage License, which takes you here:


https://opensource.diia.gov.ua/documents/Public_licence.DOCX

This license includes things like:

2.6. This License applies to the territory of all states of the world 
(except for the territories of states recognized by the Verkhovna Rada 
of Ukraine as aggressor states, states subject to sanctions in 
accordance with the Law of Ukraine "On Sanctions", states that are 
members of customs and military unions with such states).


And also:

1.3.5. the Licensee – any person (except for persons of states 
recognized by the Verkhovna Rada of Ukraine as aggressor states, states 
subject to sanctions in accordance with the Law of Ukraine “On 
Sanctions”, states that are members of customs and military unions with 
such states) who voluntarily uses the Diia mobile application software 
under a public license;


Such provisions would likely prevent the license from being considered 
free (as in freedom) by folks like the OSI.


Honestly I'm not really sure where this second license is meant to 
apply, since the source code currently is under the EUPL which has no 
such restrictions.


Anyway, I thought it was interesting!

Cheers,

--
Shane


OpenPGP_0x3732979CF967B306.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature
___
opensource-wg mailing list
opensource-wg@ripe.net
https://lists.ripe.net/mailman/listinfo/opensource-wg

To unsubscribe from this mailing list, get a password reminder, or change your 
subscription options, please visit: 
https://lists.ripe.net/mailman/listinfo/opensource-wg

[Desktop-packages] [Bug 2044973] Re: ubuntu-drivers install the wrong version of Nvidia driver on some machines

[Shane Williams]

Finally had a chance to update today, and ubuntu-drivers-common
1:0.9.0~0.20.04.8 does appear to fix the issue for us.

01:00.0 VGA compatible controller: NVIDIA Corporation TU117GL [T1000
8GB] (rev a1) (prog-if 00 [VGA controller])

shanew@prius:~$ ubuntu-drivers devices
== /sys/devices/pci:00/:00:01.0/:01:00.0 ==
modalias : pci:v10DEd1FF0sv1028sd1612bc03sc00i00
vendor   : NVIDIA Corporation
driver   : nvidia-driver-535-open - distro non-free
driver   : nvidia-driver-535-server - distro non-free
driver   : nvidia-driver-535-server-open - distro non-free
driver   : nvidia-driver-535 - distro non-free recommended
driver   : nvidia-driver-525-server - distro non-free
driver   : nvidia-driver-525-open - distro non-free
driver   : nvidia-driver-470 - distro non-free
driver   : nvidia-driver-470-server - distro non-free
driver   : nvidia-driver-525 - distro non-free
driver   : xserver-xorg-video-nouveau - distro free builtin

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

Title:
  ubuntu-drivers install the wrong version of Nvidia driver on some
  machines

Status in ubuntu-drivers-common package in Ubuntu:
  Confirmed

Bug description:
  During the SRU testing, I found some of machines installed the wrong
  version of Nvidia driver.

  They shouldn't install nvidia-driver-535-server-open on a desktop.

  Please have a look, thanks.

  If you want to have more information, please let me know.

  
  + _run sudo ubuntu-drivers devices
  + ssh -t -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null 
ubuntu@10.102.154.51 sudo ubuntu-drivers devices

  == /sys/devices/pci:00/:00:01.0/:01:00.0 ==
  modalias : pci:v10DEd1FB8sv1028sd0906bc03sc02i00
  vendor   : NVIDIA Corporation
  model: TU117GLM [Quadro T2000 Mobile / Max-Q]
  driver   : nvidia-driver-535-server - distro non-free
  driver   : nvidia-driver-535 - distro non-free
  driver   : nvidia-driver-418-server - distro non-free
  driver   : nvidia-driver-525 - distro non-free
  driver   : nvidia-driver-535-open - distro non-free
  driver   : nvidia-driver-470 - distro non-free
  driver   : nvidia-driver-450-server - distro non-free
  driver   : nvidia-driver-535-server-open - distro non-free recommended
  driver   : nvidia-driver-470-server - distro non-free
  driver   : nvidia-driver-525-open - distro non-free
  driver   : nvidia-driver-525-server - distro non-free
  driver   : xserver-xorg-video-nouveau - distro free builtin

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


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

[Bug 2044973] Re: ubuntu-drivers install the wrong version of Nvidia driver on some machines

[Shane Williams]

Finally had a chance to update today, and ubuntu-drivers-common
1:0.9.0~0.20.04.8 does appear to fix the issue for us.

01:00.0 VGA compatible controller: NVIDIA Corporation TU117GL [T1000
8GB] (rev a1) (prog-if 00 [VGA controller])

shanew@prius:~$ ubuntu-drivers devices
== /sys/devices/pci:00/:00:01.0/:01:00.0 ==
modalias : pci:v10DEd1FF0sv1028sd1612bc03sc00i00
vendor   : NVIDIA Corporation
driver   : nvidia-driver-535-open - distro non-free
driver   : nvidia-driver-535-server - distro non-free
driver   : nvidia-driver-535-server-open - distro non-free
driver   : nvidia-driver-535 - distro non-free recommended
driver   : nvidia-driver-525-server - distro non-free
driver   : nvidia-driver-525-open - distro non-free
driver   : nvidia-driver-470 - distro non-free
driver   : nvidia-driver-470-server - distro non-free
driver   : nvidia-driver-525 - distro non-free
driver   : xserver-xorg-video-nouveau - distro free builtin

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

Title:
  ubuntu-drivers install the wrong version of Nvidia driver on some
  machines

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


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

[Bug 1574107] Re: busybox-initramfs: modinfo reports "can't open '/${VERSION}/': No such file or directory"

[Shane Thompson]

I am also affected. Additionally I can not get any stderr output from
modprobe, whether I use -v or not.

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

Title:
  busybox-initramfs: modinfo reports "can't open '/${VERSION}/': No such
  file or directory"

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


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

[Touch-packages] [Bug 1574107] Re: busybox-initramfs: modinfo reports "can't open '/${VERSION}/': No such file or directory"

[Shane Thompson]

I am also affected. Additionally I can not get any stderr output from
modprobe, whether I use -v or not.

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

Title:
  busybox-initramfs: modinfo reports "can't open '/${VERSION}/': No such
  file or directory"

Status in busybox package in Ubuntu:
  Confirmed

Bug description:
  Working on 16.04 and trying to solve some unrelated issues due to a
  complex initrd set-up I discovered that the included "modinfo" tool
  doesn't work, whether given just a module name or an absolute path to
  the .ko file.

  In this case it always reports, e.g:

  (initramfs) pwd
  /lib/modules/4.4.0-21-generic/kernel/drivers/md

  (initramfs) modinfo dm-crypt
  modinfo: can't open '/4.4.0-21-generic/': No such file or directory

  (initramfs) modinfo 
/lib/modules/4.4.0-21-generic/kernel/drivers/md/dm-crypt.ko
  modinfo: can't open '/4.4.0-21-generic/': No such file or directory

  There seems there may be a related issue with modprobe too, as I've
  found it doesn't always insert a module when instructed to - also
  using either just name, or absolute path. In the specific case here I
  was working with a LUKS/dm-crypt rootfs, where the initrd.img had been
  generated using "MODULES=dep" and hadn't included dm-crypt.ko.

  I connected a USB storage device with an identical root file-system
  (same kernel version, etc.) at /mnt/USB/ and was trying to use:

  (initramfs) modprobe -v -d /mnt/USB dm-crypt 
  modprobe: FATAL: Module dm-crypt not found in directory 
/mnt/USB/lib/modules/4.4.0-21-generic

  I'm *assuming* this is because despite setting the alternate root
  directory with "-d" it is still looking at the "modules.dep" in
  /lib/modules/4.4.0-21-generic rather than prefixing the "-d" alternate
  root.

  Using a chroot the module(s) can be loaded and the block device
  unlocked:

  (initramfs) chroot /mnt/USB
  (initramfs) modprobe dm-crypt
  (initramfs) modprobe aesni-intel
  (initramfs) modprobe xts
  (initramfs) exit
  (initramfs) grep dm_crypt /proc/modules
  dm_crypt 28672 0 - Live 0xc02fa000

  (initramfs) LD_LIBRARY_PATH=/mnt/USB/lib/x86_64-gnu-linux
  /mnt/USB/sbin/cryptsetup open /dev/sda4 LUKS_VG02 --type luks

  (initramfs) blkid /dev/mapper/LUKS_VG02
  /dev/mapper/LUKS_VG02: UUID="..." TYPE="LVM2_member"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1574107/+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

[Frameworks] FFFXI Call for Submissions

[Shane Eason]

All…

FFFXI is officially open for submissions. The regular deadline is set for April 
8th with the exhibition scheduled for April 27th at the MetroLab 
 in downtown Fort 
Lauderdale, FL. 

Submit films thru the FILMFREEWAY  
portal. Subscribers to the list can use code FFFXIFrame to waive the $5 entry 
fee. Please review the rules and terms prior to submitting. 

Feel free to pass this info to others that might be interested in submitting.   

Cheers,

SCE

Flamingo Film Festival: A Showcase of International Student Film and Video
FilmFreeway  | Web 
 | Facebook 
 | Twitter 
 | Instagram 
 | TikTok 
 | Vimeo 
 | YouTube 



-- 
Frameworks mailing list
Frameworks@film-gallery.org
https://mail.film-gallery.org/mailman/listinfo/frameworks_film-gallery.org

[PDB Announce] Production Deployment 2.55.0

[Shane Wadleigh]

2.55.0 was successfully released to production, changes can be viewed at [0].

If anyone encounters any problems, please contact supp...@peeringdb.com

Cheers

[0] https://docs.peeringdb.com/release_notes/
___
Pdb-announce mailing list
Pdb-announce@lists.peeringdb.com
https://lists.peeringdb.com/cgi-bin/mailman/listinfo/pdb-announce

Re: Update Website Template (WAS: Help to get the Wayang project website in shape)

[Shane Curcuru]

tison wrote on 2/4/24 10:16 AM:

Hi,

I finally find some time to prepare a demo for the new website template [1].


This is awesome; I love providing more default "just use this" templates 
in various themes like this.


One question: why doesn't this also link (At least in the docs for each 
readme maybe?) to the Infra-supported pelican template?  We should at 
least point to that, since infra supports it and it provides a 
python-managed template, in case people like that better than Jekyll/ruby.


  https://infra.apache.org/asf-pelican-gettingstarted.html

--
- Shane
  Member
  The Apache Software Foundation


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

Re: [WG: Welcome] Proposal, a Welcome Working Group - onboarding too?

[Shane Curcuru]

Rich Bowen wrote on 2/7/24 11:53 AM:

Proposed: A formal working group around how we welcome new folks in a 
consistent and helpful manner.

We get people on this list (and on every dev@ and user@ list at the foundation) 
asking how to get engaged. We almost always give them unhelpful answers, and 
send them off to go figure it out on their own.

The Welcome WG would write documentation, and process, around welcoming these 
new folks, and shepherding them towards engagement. This would include, but not 
be limited to:

...snip...
Question: should the wg-welcome group include reviewing all onboarding 
materials too, or does that deserve it's own group at some point?  They 
are closely related, but onboarding is a larger topic.


"Welcoming" is about creating easy to re-use content to help answer 
simple questions all around, and guiding newcomers - or existing 
contributors who answer questions! - to the right kind of path, and in a 
friendly and consistent way.


"Onboarding" I see as reviewing and updating the actual emails, 
boilerplate, and links that we send to anyone who is being welcomed to a 
new role at the ASF - committer (on any project, or on an additional 
project), PMC member, officer, Member, etc.


I've already listed the majority of actual sources our tooling actually 
mails or includes links to people in various places:



https://cwiki.apache.org/confluence/display/COMDEV/Proposal%3A+Improving+Onboarding+Experiences

We need a focused group to start reviewing these, and updating them to 
be consistent, friendly, and useful for newcomers.


--
- Shane
  Member
  The Apache Software Foundation


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

Re: Best way to have a FreeBSD VM for automated testing?

[Shane Ambler]

On 25/2/24 07:05, Jo Durchholz wrote:
> On 24.02.24 20:19, Paul Vixie wrote:
>> <> bandwagon anyway.>>
>>
>> Not new. Been in production for years now.
> 
> I admit I was going by assumptions, based on the fact I had never heard
> about it before, despite having been in the CI/CD treadmill for a few
> years.
> 
>> https://github.com/firecracker-microvm/firecracker
> 
> Hm.
> V 1.0.0 came out in Jan/Feb 2022, so in that sense, it's somewhat new.
> 
> Might have been in production use in pre-1.0.0 versions, of course.
> I tend to assume software exists starting with 1.0.0, pre-1.0 versions
> tend to be very experimental and/or require handholding by the engineers
> that are building it.
> Of course, for a shop like AWS, that's not always the most accurate
> assumption :-)

Took me a while, but I have let go of waiting for 1.0 releases. If it
works - use it, if it breaks - help make it better, otherwise you just
re-invent the wheel to get what you want.

How long was openssl in wide use before 1.0 ?

There is always something to fix and something to add. Tagging a release
or build as v1.0 is only a decision, it isn't a certainty of stability.

I have about 20% of installed pkgs with a version starting with 0

-- 
FreeBSD - the place to B...Software Developing

Shane Ambler

Re: Best way to have a FreeBSD VM for automated testing?

[Shane Ambler]

On 24/2/24 05:47, Jo Durchholz wrote:
> Hi all,
> 
> I'm in repeatable build land, working in Linux and developing a FreeBSD
> appliance.
> 
> For tests, I need to run a FreeBSD VM, put some Python code and test
> data into it, run the script, and get the test results back.
> 
> Repeatability means: Everything done with the VM needs to be scriptable
> (using a GUI for exploring is okay but things have to translate).
> Which in turn means that every setup step for a FreeBSD image comes with
> a pretty high coding and maintenance cost.
> 
> So my question is:
> What's the FreeBSD image that has the least number of steps to get the
> base system up and running? I suppose it's the VM-IMAGES section, but is
> this correct?
> 
> Follow-up question:
> The startup time needs to be as fast as possible. Sub-second would be
> great ("don't disrupt the developer's thought stream").
> I see the boot process from a vanilla VM-IMAGES image takes multiple
> seconds; can this be sped up to just a few seconds, or do I need to run
> the setup and create a VM snapshot at which the VM starts for each test
> run?

Firecracker - firecracker-microvm.github.io

It may add another level of setup but it provides sub-second boot times
- and can run FreeBSD

https://www.daemonology.net/blog/2022-10-18-FreeBSD-Firecracker.html

Not sure if there are any pre-built images with the firecracker kernel,
so may not meet your requirements.


-- 
FreeBSD - the place to B...Software Developing

Shane Ambler

Re: Anyone know this ornament?

[Shane Brandes]

Could also be a batterie, or an arpeggio that one runs over all the pitches
in between but only maintains the notated ones. Decidedly weird notion
though.

Shane Brandes

On Mon, Feb 19, 2024 at 1:33 PM Francesco Intrieri <
francesco.intrieri...@gmail.com> wrote:

> Dear Auke,
> Could it be a kind of « Arpègement simple » as Rameau describes in his *Pièces
> de clavecin*?
> Best,
> Franceesco
>
> Le 19 févr. 2024 à 19:28, Engraver  a écrit :
>
>
> This is a screenshot of the entire page.
>
>
>
> Op 19-2-2024 om 19:25 schreef Stefan Thomas:
>
> Dear Auke,
> I don't know this ornament either but maybe it could be useful to see a
> few bars more of this music.
> Best,
> Stefan
>
>>
>> Hallo,
>
> I'm transcribing the organ music of Josef Ferdinand Norbert Seger. The prelude
> I'm currently working on, shows an ornamentation I am not familiar with.
> See screenshot. I think it is probably meant as arpeggio, but I'm not
> sure. Does anyone know for sure what it is?
>
> Regards, Auke
>
>
> 
>
>
>

Re: additional credential needed in S3 connection

[Shane Ardell]

Hi Glenda,

Looking at the documentation, an approach you could take is to create an
AWSCredentialsProviderControllerService[1] as your AWS Credentials Provider
Service property value in the PutS3Object processor configuration
properties. You can assign a value to the access key and secret key
properties of the controller service. I have not done this myself, so
hopefully others can chime in to verify if this is the correct approach or
not. Hope that helps.

Best,
Shane

[1]
https://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi/nifi-aws-nar/1.23.0/org.apache.nifi.processors.aws.credentials.provider.service.AWSCredentialsProviderControllerService/index.html

On Tue, Feb 13, 2024 at 3:59 PM Glenda Ramos  wrote:

> Hi,
>
>
>
> We are currently testing Apache NiFi 1.23.0 specifically the "PutS3Object"
> processor to automatically transfer data from remote site to an "internal"
> S3 bucket. The standard AWSCLI commands work and able to connect the bucket
> because we are able to pass in additional credentials like the
> AWS_CA_BUNDLE environment variable. That being said, we need AWS_CA_BUNDLE
> property added in order to connect successfully to our S3 bucket using
> Apache NiFi's "PutS3Object". I have tried passing this as a Parameter and
> made it available to the flow but it's not being used by the "PutS3Object"
> processor to connect. Is there a way we can add an additional property for
> the AWS credentials/config file? It looks like it's only looking for
> "accessKey" and "secretKey".
>
>
>
> Any help would be greatly appreciated.
>
>
>
> Respectfully,
>
> Glenda Ramos
>
> Application Engineer
>

Re: OpenBSD vm troubles

[Shane Ambler]

On 11/2/24 17:28, Odhiambo Washington wrote:
> I am not sure what it is that I am doing wrong, but I am unable to install
> OpenBSD.
> 
> Here is how I am invoking the installer:
> ```
> bhyve -A -D -H -P -S -u -w -c 8 -m 4G \
> -s 0,hostbridge \
> -s 3,ahci-hd,/usr/local/bhyve-vms/.iso/miniroot74.img \
> -s 4,virtio-blk,/usr/local/bhyve-vms/OpenBSD/openbsd74.img \
> -s 5,virtio-net,tap1 \
> -s 8,hda,play=/dev/dsp,rec=/dev/dsp \
> -s 20,virtio-rnd \
> -s 29,fbuf,tcp=0.0.0.0:5901,w=1680,h=1050,wait \
> -s 30,xhci,tablet \
> -s 31,lpc -l com1,stdio \
> -l bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd \
> openbsd74
> ```
> 
> I end up with:
> ```
> probing: pc0 com0 com1 mem[640K 3049M 128K 16M 3M 1024M]
> disk: hd0 hd1*
>>> OpenBSD/amd64 BOOTX64 3.65
> boot>
> cannot open hd0a:/etc/random.seed: No such file or directory
> booting hd0a:/bsd: 17163596read text
>  failed(0). will try /bsd
> boot>
> cannot open hd0a:/etc/random.seed: No such file or directory
> booting hd0a:/bsd: 17163596read text
>  failed(0). will try /bsd
> Turning timeout off.
> boot>
> ```
> Not sure what I need to do for the installer to run.

You are at the boot prompt, so the openbsd kernel hasn't started.

Try entering hd1d/bsd.rd

The openbsd faq may help
https://www.openbsd.org/faq/faq4.html

Instead of using miniroot, I would try using the install74.iso


-- 
FreeBSD - the place to B...Software Developing

Shane Ambler

[Rpm-maint] [rpm-software-management/rpm] Is it possible for an RPM package to have no version? (Discussion #2896)

[Shane Bishop]

### Context
Feel free to skip this context, and go straight to my question.

My team has written some software that uses librpm to retrieve the version and 
release for every RPM package installed on a system (we use `RPMTAG_VERSION` 
and `RPMTAG_RELEASE` respectively to retrieve this data). The software 
component on the host sends an event containing this data to a backend service 
that performs downstream processing on this data in order to meet the 
requirements of the larger application.

We have observed from our backend service's logs that there is a package that 
has an empty version string, and an empty release string. Specifically, this it 
the package information in the event our backend service flagged:
* Package name: "appdynamics-machine-agent"
* Epoch: "0"
* Version: ""
* Release: ""
* `SOURCERPM` value: "appdynamics-machine-agent---src.rpm"
* Vendor: "AppDynamics Inc"

The client-side software that generates the events has been distributed and is 
now running in production. We do not have access to the hosts, as the client 
runs on customer computers. Therefore, we are not free to SSH onto the host and 
run `rpm -qa --queryformat` to confirm the data in the event matches the data 
reported by `rpm` on the host itself.

### Some investigation that I have performed
I downloaded what I believe to be an RPM installer for the latest version of 
this package, and installed the package. I noticed that the data reported on 
the package by `rpm` is different than the data in the event I describe above:
```
$ rpm -qa --queryformat 
'%{NAME},%{EPOCH},%{VERSION},%{RELEASE},%{SOURCERPM},%{VENDOR}\n' | grep -i 
appdynamics
appdynamics-machine-agent,0,24.1.0.3984,1,appdynamics-machine-agent-24.1.0.3984-1-src.rpm,AppDynamics
 Inc
```
I believe the reason why the data is different is because I installed using a 
newer version of the RPM installer than our customer used when they installed 
the package on their system. I could not find anywhere on the AppDynamics 
website that I could download any older versions of the RPM installer.

I also tried building an RPM installer from a `.spec` file that omits the 
`Version` property, but I got the error `Version field must be present in 
package`. Perhaps this is just because omitting the `Version` is no longer 
legal in my version of `rpmbuild`, which is version 4.11.3.

### Question
Was it ever possible, at any point in the history of RPM, for a RPM package to 
be created without a version or a release?

-- 
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/discussions/2896
You are receiving this because you are subscribed to this thread.

Message ID: ___
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint

[Kernel-packages] [Bug 2051342] Re: Enable lowlatency settings in the generic kernel

[Shane Turner]

I haven’t spotted any tests that show a workload with a significant
improvement shown here, on discourse, or Phoronix. Am I incorrect?
Please keep in mind that I’m not suggesting that this initiative not
move forward as there appears to be plenty of evidence being built up
suggesting that there is no significant regressions.

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

Title:
  Enable lowlatency settings in the generic kernel

Status in linux package in Ubuntu:
  New
Status in linux source package in Noble:
  New

Bug description:
  [Impact]

  Ubuntu provides the "lowlatency" kernel: a kernel optimized for
  applications that have special "low latency" requirements.

  Currently, this kernel does not include any specific UBUNTU SAUCE
  patches to improve the extra "low latency" requirements, but the only
  difference is a small subset of .config options.

  Almost all these options are now configurable either at boot-time or
  even at run-time, with the only exception of CONFIG_HZ (250 in the
  generic kernel vs 1000 in the lowlatency kernel).

  Maintaining a separate kernel for a single config option seems a bit
  overkill and it is a significant cost of engineering hours, build
  time, regression testing time and resources. Not to mention the risk
  of the low-latency kernel falling behind and not being perfectly in
  sync with the latest generic kernel.

  Enabling the low-latency settings in the generic kernel has been
  evaluated before, but it has been never finalized due to the potential
  risk of performance regressions in CPU-intensive applications
  (increasing HZ from 250 to 1000 may introduce more kernel jitter in
  number crunching workloads). The outcome of the original proposal
  resulted in a re-classification of the lowlatency kernel as a desktop-
  oriented kernel, enabling additional low latency features (LP:
  #2023007).

  As we are approaching the release of the new Ubuntu 24.04 we may want
  to re-consider merging the low-latency settings in the generic kernel
  again.

  Following a detailed analysis of the specific low-latency features:

  - CONFIG_NO_HZ_FULL=y: enable access to "Full tickless mode" (shutdown
  clock tick when possible across all the enabled CPUs if they are
  either idle or running 1 task - reduce kernel jitter of running tasks
  due to the periodic clock tick, must be enabled at boot time passing
  `nohz_full=`); this can actually help CPU-intensive
  workloads and it could provide much more benefits than the CONFIG_HZ
  difference (since it can potentially shutdown any kernel jitter on
  specific CPUs), this one should really be enabled anyway, considering
  that it is configurable at boot time

   - CONFIG_RCU_NOCB_CPU=y: move RCU callbacks from softirq context to
  kthread context (reduce time spent in softirqs with preemption
  disabled to improve the overall system responsiveness, at the cost of
  introducing a potential performance penalty, because RCU callbacks are
  not processed by kernel threads); this should be enabled as well,
  since it is configurable at boot time (via the rcu_nocbs=
  parameter)

   - CONFIG_RCU_LAZY=y: batch RCU callbacks and then flush them after a
  timed delay instead of executing them immediately (c'an provide 5~10%
  power-savings for idle or lightly-loaded systems, this is extremely
  useful for laptops / portable devices -
  
https://lore.kernel.org/lkml/20221016162305.2489629-3-j...@joelfernandes.org/);
  this has the potential to introduce significant performance
  regressions, but in the Noble kernel we already have a SAUCE patch
  that allows to enable/disable this option at boot time (see LP:
  #2045492), and by default it will be disabled
  (CONFIG_RCU_LAZY_DEFAULT_OFF=y)

   - CONFIG_HZ=1000 last but not least, the only option that is *only*
  tunable at compile time. As already mentioned there is a potential
  risk of regressions for CPU-intensive applications, but they can be
  mitigated (and maybe they could even outperformed) with NO_HZ_FULL. On
  the other hand, HZ=1000 can improve system responsiveness, that means
  most of the desktop and server applications will benefit from this
  (the largest part of the server workloads is I/O bound, more than CPU-
  bound, so they can benefit from having a kernel that can react faster
  at switching tasks), not to mention the benefit for the typical end
  users applications (gaming, live conferencing, multimedia, etc.).

  With all of that in place we can provide a kernel that has the
  flexibility to be more responsive, more performant and more power
  efficient (therefore more "generic"), simply by tuning run-time and
  boot-time options.

  Moreover, once these changes are applied we will be able to deprecate
  the lowlatency kernel, saving engineering time and also reducing power
  consumption (required to build the kernel and do all the 

[blind-gamers] clarification on earlier message: do not reply directly to me or the group moderator address.

[Shane Popplestone]

Hi all,
I’ve already received a few messages from people who replied to my 
earlier message regarding email verification. Unfortunately, this will

do nothing. You need to reply to the verification message you may have
received from groups.io directly. These messages would have gone out in
the last couple weeks. If you have already responded to that
verification email, you don’t need to do anything.
If you never received a verification email, you should also be fine. As
I understand, not everyone is being asked to verify.  The email
verification process is being performed by groups.io, which is the
organization that runs the infrastructure behind the list.

--
This email has been checked for viruses by Avast antivirus software.
www.avast.com


-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#127105): https://groups.io/g/blind-gamers/message/127105
Mute This Topic: https://groups.io/mt/103985998/21656
Group Owner: blind-gamers+ow...@groups.io
Unsubscribe: 
https://groups.io/g/blind-gamers/leave/607459/21656/1071380848/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[blind-gamers] ***important*** groups.io reverification, please act immediately.

[Shane Popplestone]

Note: This is important and please take the needed action to remain a
part of any groups.io lists if you receive this communication from
Groups.IO. This is completely beyond our control.
Many of you might have received communication from Groups.IO about
needing to verify your account. Here is what their frequently asked
question page says:
Some members have been sent an email with the subject Action Required:
Confirm Your Groups.io Membership to Continue Receiving Group Emails. It
asks the member to either respond to the email or log into their account
to confirm their membership. Most such accounts are ones that haven't
posted in a long time. It's important that all know that this email is
legit. It's not a phish.
Any user who got the email and does not complete the
confirmation/reverification by January 28, 2024, will be suspended from
Groups.io. A few follow-on emails will be sent to non-responding members
between now and January 28, 2024.
Members who received the reverification email have through Sunday,
January 28, 2024, to either reply to the email or log into their
Groups.io account.
If you reply to the email, you do not need to enter anything in the
reply. You will be sent an acknowledgement email.
If you log into your account, you will see a green banner saying you've
successfully reverified. You do not need to do anything else. If you
don't have a password or don't remember your password, use the Forgot
your password, or don't have one yet? link to have an email sent to you
with a link that will log you in automatically. Once you log in, you
will be reverified.
We will send additional reverification reminders until January 28, 2024.
For members that are removed after this process, the removals will be
logged in the group's Activity Log.
Sample Email:
Subject: Action Required: Confirm Your Groups.io Membership to Continue
Receiving Group Emails
Hello,
Your account associated with EMAIL ADDRESS has been a member of one or
more Groups.io email groups since DATE. As part of our commitment to
maintain a valuable and spam-free experience, we're updating our
subscription records. To ensure you still wish to receive emails from
your subscribed groups, we kindly ask for your confirmation.
You have two simple options to confirm your subscription:
1. Without adding any text, just send a reply to this email. This will
be seen by the software at groups.io as a wish to stay in your groups.
2. Or you can log into your Groups.io account and your active login will
count as confirmation.
If we don't hear from you, we will send a reminder email every 4 days to
ensure you have every opportunity to remain subscribed.
Without confirmation by Sun Jan 28, 2024, we will take it as an
indication that you prefer not to continue your subscriptions.
Consequently, your email will be removed from the groups you are a
member of.
email address, you need to reply to it. It's not phishing or spam. If
you
receive that message from groups.io and you don't reply to it, you won't
be
getting any more messages from any groups.io mailing list. the cutoff
day is Sunday, so if you got that message, reply to it ASAP.


--
This email has been checked for viruses by Avast antivirus software.
www.avast.com


-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#127103): https://groups.io/g/blind-gamers/message/127103
Mute This Topic: https://groups.io/mt/103984436/21656
Group Owner: blind-gamers+ow...@groups.io
Unsubscribe: 
https://groups.io/g/blind-gamers/leave/607459/21656/1071380848/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: Subpackage explanations

[Shane Ambler]

On 24/1/24 19:58, Luca Pizzamiglio wrote:
> Hi porters!
> 
> At the beginning of January, we merged the support to subpackages in the
> framework.

Sounds like some good work in the right direction.

> *Use cases we want to tackle*
> The first use case we want to get rid of is master/slave ports when slave
> ports could be built with the master port.

I don't see any mention of flavors. If I merge a slave port that builds
the python bindings into the master port, can I still build multiple
flavors for the subpackage?

Any possibility that build steps can be defined to be repeated for each
desired flavor?

do-build-flavor:
make --DPYVERS=${PY_FLAVOR}

do-build-PY38:
make --DUSE_FUTURES=yes


> *Use cases we don't want to tackle (yet)*
> Subpackages enable the adoption of micro-subpackages, a typical pattern for
> Linux distributions that split a package in smaller ones: one with docs
> (-doc), one with static libraries and headers (-dev), one with manpages
> (-man), one with examples (-examples), and so on.

To me that sounds like the easy first use case. Turn the
doc/test/example options into subpackages.


-- 
FreeBSD - the place to B...Software Developing

Shane Ambler

[PDB Announce] Production Deployment 2.54.0

[Shane Wadleigh]

2.54.0 was successfully released to production, changes can be viewed at [0].

If anyone encounters any problems, please contact supp...@peeringdb.com

Cheers

[0] https://docs.peeringdb.com/release_notes/
___
Pdb-announce mailing list
Pdb-announce@lists.peeringdb.com
https://lists.peeringdb.com/cgi-bin/mailman/listinfo/pdb-announce

[jira] [Updated] (NIFI-12400) Remaining items to migrate UI to currently supported/active framework

[Shane Ardell (Jira)]

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

Shane Ardell updated NIFI-12400:

Description: 
The purpose of this Jira is to track all remaining items following the initial 
commit [1] for NIFI-11481. The description will be kept up to date with 
remaining features, tasks, and improvements. As each items is worked, a new sub 
task Jira will be created and referenced in this description.
 * Support Parameters in Properties with Allowable Values (NIFI-12401)
 * Summary (NIFI-12437)
 ** Remaining work not addressed in initial Jira:
 *** input ports (NIFI-12504)
 *** output ports (NIFI-12504)
 *** remote process groups (NIFI-12504)
 *** process groups (NIFI-12504)
 *** connections (NIFI-12504)
 *** System Diagnostics (NIFI-12505)
 *** support for cluster-specific ui elements (NIFI-12537)
 *** Add pagination (NIFI-12552)
 * Counters (NIFI-12415)
 * Bulletin Board (NIFI-12560)
 * Provenance (NIFI-12445)
 ** Event Listing (NIFI-12445)
 ** Search (NIFI-12445)
 ** Event Dialog (NIFI-12445)
 ** Lineage (NIFI-12485)
 ** Replay from context menu (NIFI-12445)

 * Configure Reporting Task (NIFI-12563)
 * Flow Analysis Rules (NIFI-12588)
 * Registry Clients (NIFI-12486)
 * Import from Registry
 * Parameter Providers (NIFI-12622)
 * Cluster
 * Flow Configuration History
 * Node Status History (NIFI-12553)
 * Status history for components from canvas context menu (NIFI-12553)
 * Users (NIFI-12543)
 * Policies (NIFI-12548)
 * Help
 * About
 * Show Upstream/Downstream
 * Align
 * List Queue (NIFI-12589)
 * Empty [all] Queue (NIFI-12604)
 * View Content (NIFI-12589 and NIFI-12445)
 * View State (NIFI-12611)
 * Change Version
 * PG Version
 ** Start
 ** Commit
 ** Force Commit
 ** Show changes
 ** Revert changes
 ** Change Flow version
 ** Stop

 * Configure PG (NIFI-12417)
 * Process Group Services (NIFI-12425)
 ** Listing (NIFI-12425)
 ** Create (NIFI-12425)
 ** Configure (NIFI-12425)
 ** Delete (NIFI-12425)
 ** Enable (NIFI-12529)
 ** Disable (NIFI-12529)
 ** Improve layout and breadcrumbs
 * Configure Processor
 ** Service Link (NIFI-12425)
 ** Create inline Service (NIFI-12425)
 ** Parameter Link (NIFI-12502)
 ** Convert to Parameter (NIFI-12502)
 ** Fix issue with Property Editor width (NIFI-12547)
 ** Stop and Configure
 ** Open Custom UI
 ** Property History
 ** Unable to re-add any removed Property
 * Property Verification
 * More Details (Processor, Controller Service, Reporting Task)

 * Download Flow
 * Create RPG
 * Configure RPG
 * RPG Remote Ports
 * RPG Go To
 * Color
 * Move to Front
 * Copy/Paste
 * Add/Update Info Icons in dialogs throughout the application
 * Better theme support (NIFI-12655)
 * Run unit tests are part of standard build
 * Update all API calls to consider disconnect node confirmation
 * Update API calls to use uiOnly flag
 * Routing error handling
 * Introduce header in new pages to unify with canvas and offer better 
navigation. (NIFI-12597)
 * Prompt user to save Parameter Context when Edit form is dirty
 * Start/Stop processors, process groups, ... (NIFI-12568)
 * Dialog vertical resizing on smaller screens do not allow users to access all 
fields (NIFI-12603)
 * Flow Analysis report menu

[1] [https://github.com/apache/nifi/pull/8053]

  was:
The purpose of this Jira is to track all remaining items following the initial 
commit [1] for NIFI-11481. The description will be kept up to date with 
remaining features, tasks, and improvements. As each items is worked, a new sub 
task Jira will be created and referenced in this description.
 * Support Parameters in Properties with Allowable Values (NIFI-12401)
 * Summary (NIFI-12437)
 ** Remaining work not addressed in initial Jira:
 *** input ports (NIFI-12504)
 *** output ports (NIFI-12504)
 *** remote process groups (NIFI-12504)
 *** process groups (NIFI-12504)
 *** connections (NIFI-12504)
 *** System Diagnostics (NIFI-12505)
 *** support for cluster-specific ui elements (NIFI-12537)
 *** Add pagination (NIFI-12552)
 * Counters (NIFI-12415)
 * Bulletin Board (NIFI-12560)
 * Provenance (NIFI-12445)
 ** Event Listing (NIFI-12445)
 ** Search (NIFI-12445)
 ** Event Dialog (NIFI-12445)
 ** Lineage (NIFI-12485)
 ** Replay from context menu (NIFI-12445)

 * Configure Reporting Task (NIFI-12563)
 * Flow Analysis Rules (NIFI-12588)
 * Registry Clients (NIFI-12486)
 * Import from Registry
 * Parameter Providers (NIFI-12622)
 * Cluster
 * Flow Configuration History
 * Node Status History (NIFI-12553)
 * Status history for components from canvas context menu (NIFI-12553)
 * Users (NIFI-12543)
 * Policies (NIFI-12548)
 * Help
 * About
 * Show Upstream/Downstream
 * Align
 * List Queue (NIFI-12589)
 * Empty [all] Queue (NIFI-12604)
 * View Content (NIFI-12589 and NIFI-12445)
 * View State (NIFI-12611)
 * Change Version
 * PG Version
 ** Start
 ** Commit
 ** Force Commit
 ** Show changes
 ** Revert changes
 ** Change Flow version

[jira] [Updated] (NIFI-12661) Flow Analysis report menu

[Shane Ardell (Jira)]

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

Shane Ardell updated NIFI-12661:

Summary: Flow Analysis report menu  (was: Flow Analysis report UI menu)

> Flow Analysis report menu
> -
>
> Key: NIFI-12661
> URL: https://issues.apache.org/jira/browse/NIFI-12661
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Core UI
>Reporter: Shane Ardell
>Assignee: Shane Ardell
>Priority: Major
>
> Implement the work from [https://github.com/apache/nifi/pull/8273] in the new 
> UI. Link to original ticket here: 
> https://issues.apache.org/jira/browse/NIFI-11520 



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

[jira] [Created] (NIFI-12661) Flow Analysis report UI menu

[Shane Ardell (Jira)]

Shane Ardell created NIFI-12661:
---

 Summary: Flow Analysis report UI menu
 Key: NIFI-12661
 URL: https://issues.apache.org/jira/browse/NIFI-12661
 Project: Apache NiFi
  Issue Type: Sub-task
  Components: Core UI
Reporter: Shane Ardell
Assignee: Shane Ardell


Implement the work from [https://github.com/apache/nifi/pull/8273] in the new 
UI. Link to original ticket here: 
https://issues.apache.org/jira/browse/NIFI-11520 



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

[jira] [Updated] (NIFI-12400) Remaining items to migrate UI to currently supported/active framework

[Shane Ardell (Jira)]

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

Shane Ardell updated NIFI-12400:

Description: 
The purpose of this Jira is to track all remaining items following the initial 
commit [1] for NIFI-11481. The description will be kept up to date with 
remaining features, tasks, and improvements. As each items is worked, a new sub 
task Jira will be created and referenced in this description.
 * Support Parameters in Properties with Allowable Values (NIFI-12401)
 * Summary (NIFI-12437)
 ** Remaining work not addressed in initial Jira:
 *** input ports (NIFI-12504)
 *** output ports (NIFI-12504)
 *** remote process groups (NIFI-12504)
 *** process groups (NIFI-12504)
 *** connections (NIFI-12504)
 *** System Diagnostics (NIFI-12505)
 *** support for cluster-specific ui elements (NIFI-12537)
 *** Add pagination (NIFI-12552)
 * Counters (NIFI-12415)
 * Bulletin Board (NIFI-12560)
 * Provenance (NIFI-12445)
 ** Event Listing (NIFI-12445)
 ** Search (NIFI-12445)
 ** Event Dialog (NIFI-12445)
 ** Lineage (NIFI-12485)
 ** Replay from context menu (NIFI-12445)

 * Configure Reporting Task (NIFI-12563)
 * Flow Analysis Rules (NIFI-12588)
 * Registry Clients (NIFI-12486)
 * Import from Registry
 * Parameter Providers (NIFI-12622)
 * Cluster
 * Flow Configuration History
 * Node Status History (NIFI-12553)
 * Status history for components from canvas context menu (NIFI-12553)
 * Users (NIFI-12543)
 * Policies (NIFI-12548)
 * Help
 * About
 * Show Upstream/Downstream
 * Align
 * List Queue (NIFI-12589)
 * Empty [all] Queue (NIFI-12604)
 * View Content (NIFI-12589 and NIFI-12445)
 * View State (NIFI-12611)
 * Change Version
 * PG Version
 ** Start
 ** Commit
 ** Force Commit
 ** Show changes
 ** Revert changes
 ** Change Flow version
 ** Stop

 * Configure PG (NIFI-12417)
 * Process Group Services (NIFI-12425)
 ** Listing (NIFI-12425)
 ** Create (NIFI-12425)
 ** Configure (NIFI-12425)
 ** Delete (NIFI-12425)
 ** Enable (NIFI-12529)
 ** Disable (NIFI-12529)
 ** Improve layout and breadcrumbs
 * Configure Processor
 ** Service Link (NIFI-12425)
 ** Create inline Service (NIFI-12425)
 ** Parameter Link (NIFI-12502)
 ** Convert to Parameter (NIFI-12502)
 ** Fix issue with Property Editor width (NIFI-12547)
 ** Stop and Configure
 ** Open Custom UI
 ** Property History
 ** Unable to re-add any removed Property
 * Property Verification
 * More Details (Processor, Controller Service, Reporting Task)

 * Download Flow
 * Create RPG
 * Configure RPG
 * RPG Remote Ports
 * RPG Go To
 * Color
 * Move to Front
 * Copy/Paste
 * Add/Update Info Icons in dialogs throughout the application
 * Better theme support (NIFI-12655)
 * Run unit tests are part of standard build
 * Update all API calls to consider disconnect node confirmation
 * Update API calls to use uiOnly flag
 * Routing error handling
 * Introduce header in new pages to unify with canvas and offer better 
navigation. (NIFI-12597)
 * Prompt user to save Parameter Context when Edit form is dirty
 * Start/Stop processors, process groups, ... (NIFI-12568)
 * Dialog vertical resizing on smaller screens do not allow users to access all 
fields (NIFI-12603)
 * Flow Analysis report UI menu

[1] [https://github.com/apache/nifi/pull/8053]

  was:
The purpose of this Jira is to track all remaining items following the initial 
commit [1] for NIFI-11481. The description will be kept up to date with 
remaining features, tasks, and improvements. As each items is worked, a new sub 
task Jira will be created and referenced in this description.
 * Support Parameters in Properties with Allowable Values (NIFI-12401)
 * Summary (NIFI-12437)
 ** Remaining work not addressed in initial Jira:
 *** input ports (NIFI-12504)
 *** output ports (NIFI-12504)
 *** remote process groups (NIFI-12504)
 *** process groups (NIFI-12504)
 *** connections (NIFI-12504)
 *** System Diagnostics (NIFI-12505)
 *** support for cluster-specific ui elements (NIFI-12537)
 *** Add pagination (NIFI-12552)
 * Counters (NIFI-12415)
 * Bulletin Board (NIFI-12560)
 * Provenance (NIFI-12445)
 ** Event Listing (NIFI-12445)
 ** Search (NIFI-12445)
 ** Event Dialog (NIFI-12445)
 ** Lineage (NIFI-12485)
 ** Replay from context menu (NIFI-12445)

 * Configure Reporting Task (NIFI-12563)
 * Flow Analysis Rules (NIFI-12588)
 * Registry Clients (NIFI-12486)
 * Import from Registry
 * Parameter Providers (NIFI-12622)
 * Cluster
 * Flow Configuration History
 * Node Status History (NIFI-12553)
 * Status history for components from canvas context menu (NIFI-12553)
 * Users (NIFI-12543)
 * Policies (NIFI-12548)
 * Help
 * About
 * Show Upstream/Downstream
 * Align
 * List Queue (NIFI-12589)
 * Empty [all] Queue (NIFI-12604)
 * View Content (NIFI-12589 and NIFI-12445)
 * View State (NIFI-12611)
 * Change Version
 * PG Version
 ** Start
 ** Commit
 ** Force Commit
 ** Show changes
 ** Revert changes
 ** Change Flow version

Re: optional variations

[Shane Brandes]

Whose faircopy and why the indecision?

-Shane

On Wed, Jan 17, 2024, 4:23 PM mog...@kayju.com  wrote:

> Hi,
>
> The handwritten manuscript I am typesetting wants the performer to play
>4 OR
>4 OR
>4OR
>4
> at the performer's discretion.  Does anyone know a standard notation for
> such flexibility - three ossia staves seems overkill.
>
> Regards,
> Mogens
>
>
>

[Desktop-packages] [Bug 2044973] Re: ubuntu-drivers install the wrong version of Nvidia driver on some machines

[Shane Williams]

We discovered the same issue with T1000 cards in a bunch of Dell
Precision 3660s.  We believe the correct choice should be "nvidia-
driver-535", but it recommends "nvidia-driver-535-server-open" instead,
which prevents gdm and X from starting.  dmesg provides the following
error:

[  231.608701] NVRM objClInitPcieChipset: *** Chipset Setup Function Error!
[  233.147366] NVRM: Open nvidia.ko is only ready for use on Data Center GPUs.
[  233.147368] NVRM: To force use of Open nvidia.ko on other GPUs, see the
[  233.147369] NVRM: 'OpenRmEnableUnsupportedGpus' kernel module parameter 
described
[  233.147369] NVRM: in the README.
[  233.426588] NVRM: GPU :01:00.0: RmInitAdapter failed! (0x62:0x0:1904)
[  233.426882] NVRM: GPU :01:00.0: rm_init_adapter failed, device minor 
number 0
[  235.365019] NVRM: GPU :01:00.0: RmInitAdapter failed! (0x62:0x0:1904)
[  235.365336] NVRM: GPU :01:00.0: rm_init_adapter failed, device minor 
number 0
[  237.455019] NVRM: GPU :01:00.0: RmInitAdapter failed! (0x62:0x0:1904)
[  237.455443] NVRM: GPU :01:00.0: rm_init_adapter failed, device minor 
number 0
[  239.430998] NVRM: GPU :01:00.0: RmInitAdapter failed! (0x62:0x0:1904)
[  239.431436] NVRM: GPU :01:00.0: rm_init_adapter failed, device minor 
number 0
[  241.403724] NVRM: GPU :01:00.0: RmInitAdapter failed! (0x62:0x0:1904)
[  241.404223] NVRM: GPU :01:00.0: rm_init_adapter failed, device minor 
number 0
[  243.384996] NVRM: GPU :01:00.0: RmInitAdapter failed! (0x62:0x0:1904)
[  243.385389] NVRM: GPU :01:00.0: rm_init_adapter failed, device minor 
number 0


Here is the output of lspci and ubuntu-drivers devices:

shanew@prius:~$ sudo lspci -s 01:00.0 
01:00.0 VGA compatible controller: NVIDIA Corporation TU117GL [T1000 8GB] (rev 
a1)

shanew@prius:~$ sudo ubuntu-drivers devices
== /sys/devices/pci:00/:00:01.0/:01:00.0 ==
modalias : pci:v10DEd1FF0sv1028sd1612bc03sc00i00
vendor   : NVIDIA Corporation
driver   : nvidia-driver-525-server - distro non-free
driver   : nvidia-driver-525 - distro non-free
driver   : nvidia-driver-535-open - distro non-free
driver   : nvidia-driver-535-server - distro non-free
driver   : nvidia-driver-525-open - distro non-free
driver   : nvidia-driver-535-server-open - distro non-free recommended
driver   : nvidia-driver-470-server - distro non-free
driver   : nvidia-driver-470 - distro non-free
driver   : nvidia-driver-535 - distro non-free
driver   : xserver-xorg-video-nouveau - distro free builtin

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

Title:
  ubuntu-drivers install the wrong version of Nvidia driver on some
  machines

Status in ubuntu-drivers-common package in Ubuntu:
  Confirmed

Bug description:
  During the SRU testing, I found some of machines installed the wrong
  version of Nvidia driver.

  They shouldn't install nvidia-driver-535-server-open on a desktop.

  Please have a look, thanks.

  If you want to have more information, please let me know.

  
  + _run sudo ubuntu-drivers devices
  + ssh -t -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null 
ubuntu@10.102.154.51 sudo ubuntu-drivers devices

  == /sys/devices/pci:00/:00:01.0/:01:00.0 ==
  modalias : pci:v10DEd1FB8sv1028sd0906bc03sc02i00
  vendor   : NVIDIA Corporation
  model: TU117GLM [Quadro T2000 Mobile / Max-Q]
  driver   : nvidia-driver-535-server - distro non-free
  driver   : nvidia-driver-535 - distro non-free
  driver   : nvidia-driver-418-server - distro non-free
  driver   : nvidia-driver-525 - distro non-free
  driver   : nvidia-driver-535-open - distro non-free
  driver   : nvidia-driver-470 - distro non-free
  driver   : nvidia-driver-450-server - distro non-free
  driver   : nvidia-driver-535-server-open - distro non-free recommended
  driver   : nvidia-driver-470-server - distro non-free
  driver   : nvidia-driver-525-open - distro non-free
  driver   : nvidia-driver-525-server - distro non-free
  driver   : xserver-xorg-video-nouveau - distro free builtin

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


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

[jira] [Commented] (GRIFFIN-377) mention borrowed code in Griffin NOTICE

[Shane Curcuru (Jira)]

[ 
https://issues.apache.org/jira/browse/GRIFFIN-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17807198#comment-17807198
 ] 

Shane Curcuru commented on GRIFFIN-377:
---

The ASF's guide for what should be in NOTICE files is over here.  Questions 
about exactly how to update NOTICE files should go to legal-discuss@

https://infra.apache.org/licensing-howto.html#mod-notice

> mention borrowed code in Griffin NOTICE
> ---
>
> Key: GRIFFIN-377
> URL: https://issues.apache.org/jira/browse/GRIFFIN-377
> Project: Griffin
>  Issue Type: Task
>Reporter: PJ Fanning
>Priority: Major
>
> Griffin's ThreadUtils class looks like it is derived from Apache Spark's.
> https://github.com/apache/griffin/blob/9f3197cb2869f5d15a2d3b965650e22ce254f3aa/measure/src/main/scala/org/apache/griffin/measure/utils/ThreadUtils.scala#L28
> https://github.com/apache/spark/blob/ae9106370a9f3002979077662149ba9122d86cef/core/src/main/scala/org/apache/spark/util/ThreadUtils.scala#L32
> I think the Griffin file should mention this and that you should update your 
> NOTICE file to say that you have Apache Spark derived code.
> It might be a good idea to update the copyright years in your NOTICE too.
> https://github.com/apache/griffin/blob/master/NOTICE



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

[jira] [Updated] (NIFI-12608) Processor Bundle Maven Archetype broken build

[Shane O'Neill (Jira)]

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

Shane O'Neill updated NIFI-12608:
-
Description: 
I am seeing...
{noformat}
mvn archetype:generate -DarchetypeGroupId=org.apache.nifi 
-DarchetypeArtifactId=nifi-processor-bundle-archetype{noformat}
fail to produce a buildable project for the 
{{{}nifi-processor-bundle-archetype{}}}. The error is:
{code:java}
java.lang.ClassNotFoundException: 
org.apache.nifi.processor.util.StandardValidators
at java.net.URLClassLoader.findClass (URLClassLoader.java:445)
at java.lang.ClassLoader.loadClass (ClassLoader.java:593)
at java.lang.ClassLoader.loadClass (ClassLoader.java:526)
at org.example.processors.example.MyProcessor. (MyProcessor.java:53)
at jdk.internal.misc.Unsafe.ensureClassInitialized0 (Native Method)
at jdk.internal.misc.Unsafe.ensureClassInitialized (Unsafe.java:1160)
at jdk.internal.reflect.MethodHandleAccessorFactory.ensureClassInitialized 
(MethodHandleAccessorFactory.java:300)
at jdk.internal.reflect.MethodHandleAccessorFactory.newConstructorAccessor 
(MethodHandleAccessorFactory.java:103)
at jdk.internal.reflect.ReflectionFactory.newConstructorAccessor 
(ReflectionFactory.java:200)
at java.lang.reflect.Constructor.acquireConstructorAccessor 
(Constructor.java:549)
at java.lang.reflect.Constructor.newInstanceWithCaller (Constructor.java:499)
at java.lang.reflect.Constructor.newInstance (Constructor.java:486) {code}
Adding {{nifi-standard-services-api-nar}} to the NAR packaging module fixes it.

To recreate the issue, generate a project and run mvn package.
{code:java}
mvn archetype:generate \
-DarchetypeGroupId=org.apache.nifi \
-DarchetypeArtifactId=nifi-processor-bundle-archetype \
-DnifiVersion=2.0.0-M1 \
-DartifactBaseName=example \
-DgroupId=org.example \
-DartifactId=myproject \
-Dversion=0.0.1 \
-Dpackage=org.example.processors.example {code}
{code:java}
cd myproject
mvn package {code}

  was:
I am seeing the {{mvn archetype:generate}} CLI fail to produce a buildable 
project for the {{{}nifi-processor-bundle-archetype{}}}. The error is:
{code:java}
java.lang.ClassNotFoundException: 
org.apache.nifi.processor.util.StandardValidators
at java.net.URLClassLoader.findClass (URLClassLoader.java:445)
at java.lang.ClassLoader.loadClass (ClassLoader.java:593)
at java.lang.ClassLoader.loadClass (ClassLoader.java:526)
at org.example.processors.example.MyProcessor. (MyProcessor.java:53)
at jdk.internal.misc.Unsafe.ensureClassInitialized0 (Native Method)
at jdk.internal.misc.Unsafe.ensureClassInitialized (Unsafe.java:1160)
at jdk.internal.reflect.MethodHandleAccessorFactory.ensureClassInitialized 
(MethodHandleAccessorFactory.java:300)
at jdk.internal.reflect.MethodHandleAccessorFactory.newConstructorAccessor 
(MethodHandleAccessorFactory.java:103)
at jdk.internal.reflect.ReflectionFactory.newConstructorAccessor 
(ReflectionFactory.java:200)
at java.lang.reflect.Constructor.acquireConstructorAccessor 
(Constructor.java:549)
at java.lang.reflect.Constructor.newInstanceWithCaller (Constructor.java:499)
at java.lang.reflect.Constructor.newInstance (Constructor.java:486) {code}
Adding {{nifi-standard-services-api-nar}} to the NAR packaging module fixes it.

To recreate the issue, generate a project and run mvn package.
{code:java}
mvn archetype:generate \
-DarchetypeGroupId=org.apache.nifi \
-DarchetypeArtifactId=nifi-processor-bundle-archetype \
-DnifiVersion=2.0.0-M1 \
-DartifactBaseName=example \
-DgroupId=org.example \
-DartifactId=myproject \
-Dversion=0.0.1 \
-Dpackage=org.example.processors.example {code}
{code:java}
cd myproject
mvn package {code}


> Processor Bundle Maven Archetype broken build
> -
>
> Key: NIFI-12608
> URL: https://issues.apache.org/jira/browse/NIFI-12608
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Tools and Build
>Affects Versions: 2.0.0-M1
>Reporter: Shane O'Neill
>Priority: Major
>
> I am seeing...
> {noformat}
> mvn archetype:generate -DarchetypeGroupId=org.apache.nifi 
> -DarchetypeArtifactId=nifi-processor-bundle-archetype{noformat}
> fail to produce a buildable project for the 
> {{{}nifi-processor-bundle-archetype{}}}. The error is:
> {code:java}
> java.lang.ClassNotFoundException: 
> org.apache.nifi.processor.util.StandardValidators
> at java.net.URLClassLoader.findClass (URLClassLoader.java:445)
> at java.lang.ClassLoader.loadClass (ClassLoader.java:593)
> at java.lang.ClassLoader.loadClass (ClassLoader.java:526)
> at org.example.processors.example.MyProcessor. (MyProcessor.java:53)
> at jdk.internal.misc.Unsafe.ensureClassInitialized0 (Native Method)
> at jdk.internal.misc.Unsafe.ensureClassInitialized (Unsafe.java:1160)
> at jdk.internal.reflect.MethodH

[jira] [Updated] (NIFI-12608) Processor Bundle Maven Archetype broken build

[Shane O'Neill (Jira)]

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

Shane O'Neill updated NIFI-12608:
-
Description: 
I am seeing the {{mvn archetype:generate}} CLI fail to produce a buildable 
project for the {{{}nifi-processor-bundle-archetype{}}}. The error is:

 
{code:java}
java.lang.ClassNotFoundException: 
org.apache.nifi.processor.util.StandardValidators
at java.net.URLClassLoader.findClass (URLClassLoader.java:445)
at java.lang.ClassLoader.loadClass (ClassLoader.java:593)
at java.lang.ClassLoader.loadClass (ClassLoader.java:526)
at org.example.processors.example.MyProcessor. (MyProcessor.java:53)
at jdk.internal.misc.Unsafe.ensureClassInitialized0 (Native Method)
at jdk.internal.misc.Unsafe.ensureClassInitialized (Unsafe.java:1160)
at jdk.internal.reflect.MethodHandleAccessorFactory.ensureClassInitialized 
(MethodHandleAccessorFactory.java:300)
at jdk.internal.reflect.MethodHandleAccessorFactory.newConstructorAccessor 
(MethodHandleAccessorFactory.java:103)
at jdk.internal.reflect.ReflectionFactory.newConstructorAccessor 
(ReflectionFactory.java:200)
at java.lang.reflect.Constructor.acquireConstructorAccessor 
(Constructor.java:549)
at java.lang.reflect.Constructor.newInstanceWithCaller (Constructor.java:499)
at java.lang.reflect.Constructor.newInstance (Constructor.java:486) {code}
Adding {{nifi-standard-services-api-nar}} to the NAR packaging module fixes it.

To recreate the issue, generate a project and run mvn package.
{code:java}
mvn archetype:generate \
-DarchetypeGroupId=org.apache.nifi \
-DarchetypeArtifactId=nifi-processor-bundle-archetype \
-DnifiVersion=2.0.0-M1 \
-DartifactBaseName=example \
-DgroupId=org.example \
-DartifactId=myproject \
-Dversion=0.0.1 \
-Dpackage=org.example.processors.example {code}
{code:java}
cd myproject
mvn package {code}

  was:
I am seeing the {{mvn archetype:generate}} CLI fail to produce a buildable 
project for the {{{}nifi-processor-bundle-archetype{}}}. The error is:

 
Caused by: java.lang.ClassNotFoundException: 
org.apache.nifi.processor.util.StandardValidators
at java.net.URLClassLoader.findClass (URLClassLoader.java:445)
at java.lang.ClassLoader.loadClass (ClassLoader.java:593)
at java.lang.ClassLoader.loadClass (ClassLoader.java:526)
at org.example.processors.example.MyProcessor. (MyProcessor.java:53)
at jdk.internal.misc.Unsafe.ensureClassInitialized0 (Native Method)
at jdk.internal.misc.Unsafe.ensureClassInitialized (Unsafe.java:1160)
at jdk.internal.reflect.MethodHandleAccessorFactory.ensureClassInitialized 
(MethodHandleAccessorFactory.java:300)
at jdk.internal.reflect.MethodHandleAccessorFactory.newConstructorAccessor 
(MethodHandleAccessorFactory.java:103)
at jdk.internal.reflect.ReflectionFactory.newConstructorAccessor 
(ReflectionFactory.java:200)
at java.lang.reflect.Constructor.acquireConstructorAccessor 
(Constructor.java:549)
at java.lang.reflect.Constructor.newInstanceWithCaller 
(Constructor.java:499)
at java.lang.reflect.Constructor.newInstance (Constructor.java:486){{}}
Adding {{nifi-standard-services-api-nar}} to the NAR packaging module fixes it.

To recreate the issue, generate a project and run mvn package.

{{}}
mvn archetype:generate \
-DarchetypeGroupId=org.apache.nifi \
-DarchetypeArtifactId=nifi-processor-bundle-archetype \
-DnifiVersion=2.0.0-M1 \
-DartifactBaseName=example \
-DgroupId=org.example \
-DartifactId=myproject \
-Dversion=0.0.1 \
-Dpackage=org.example.processors.example
 
cd myproject
mvn package


> Processor Bundle Maven Archetype broken build
> -
>
> Key: NIFI-12608
> URL: https://issues.apache.org/jira/browse/NIFI-12608
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Tools and Build
>Affects Versions: 2.0.0-M1
>Reporter: Shane O'Neill
>Priority: Major
>
> I am seeing the {{mvn archetype:generate}} CLI fail to produce a buildable 
> project for the {{{}nifi-processor-bundle-archetype{}}}. The error is:
>  
> {code:java}
> java.lang.ClassNotFoundException: 
> org.apache.nifi.processor.util.StandardValidators
> at java.net.URLClassLoader.findClass (URLClassLoader.java:445)
> at java.lang.ClassLoader.loadClass (ClassLoader.java:593)
> at java.lang.ClassLoader.loadClass (ClassLoader.java:526)
> at org.example.processors.example.MyProcessor. (MyProcessor.java:53)
> at jdk.internal.misc.Unsafe.ensureClassInitialized0 (Native Method)
> at jdk.internal.misc.Unsafe.ensureClassInitialized (Unsafe.java:1160)
> at jdk.internal.reflect.MethodHandleAccessorFactory.ensureClassInitialized 
> (MethodHandleAccessorFactory.java:300)
> at jdk.internal.reflect.MethodHand

[jira] [Updated] (NIFI-12608) Processor Bundle Maven Archetype broken build

[Shane O'Neill (Jira)]

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

Shane O'Neill updated NIFI-12608:
-
Description: 
I am seeing the {{mvn archetype:generate}} CLI fail to produce a buildable 
project for the {{{}nifi-processor-bundle-archetype{}}}. The error is:
{code:java}
java.lang.ClassNotFoundException: 
org.apache.nifi.processor.util.StandardValidators
at java.net.URLClassLoader.findClass (URLClassLoader.java:445)
at java.lang.ClassLoader.loadClass (ClassLoader.java:593)
at java.lang.ClassLoader.loadClass (ClassLoader.java:526)
at org.example.processors.example.MyProcessor. (MyProcessor.java:53)
at jdk.internal.misc.Unsafe.ensureClassInitialized0 (Native Method)
at jdk.internal.misc.Unsafe.ensureClassInitialized (Unsafe.java:1160)
at jdk.internal.reflect.MethodHandleAccessorFactory.ensureClassInitialized 
(MethodHandleAccessorFactory.java:300)
at jdk.internal.reflect.MethodHandleAccessorFactory.newConstructorAccessor 
(MethodHandleAccessorFactory.java:103)
at jdk.internal.reflect.ReflectionFactory.newConstructorAccessor 
(ReflectionFactory.java:200)
at java.lang.reflect.Constructor.acquireConstructorAccessor 
(Constructor.java:549)
at java.lang.reflect.Constructor.newInstanceWithCaller (Constructor.java:499)
at java.lang.reflect.Constructor.newInstance (Constructor.java:486) {code}
Adding {{nifi-standard-services-api-nar}} to the NAR packaging module fixes it.

To recreate the issue, generate a project and run mvn package.
{code:java}
mvn archetype:generate \
-DarchetypeGroupId=org.apache.nifi \
-DarchetypeArtifactId=nifi-processor-bundle-archetype \
-DnifiVersion=2.0.0-M1 \
-DartifactBaseName=example \
-DgroupId=org.example \
-DartifactId=myproject \
-Dversion=0.0.1 \
-Dpackage=org.example.processors.example {code}
{code:java}
cd myproject
mvn package {code}

  was:
I am seeing the {{mvn archetype:generate}} CLI fail to produce a buildable 
project for the {{{}nifi-processor-bundle-archetype{}}}. The error is:

 
{code:java}
java.lang.ClassNotFoundException: 
org.apache.nifi.processor.util.StandardValidators
at java.net.URLClassLoader.findClass (URLClassLoader.java:445)
at java.lang.ClassLoader.loadClass (ClassLoader.java:593)
at java.lang.ClassLoader.loadClass (ClassLoader.java:526)
at org.example.processors.example.MyProcessor. (MyProcessor.java:53)
at jdk.internal.misc.Unsafe.ensureClassInitialized0 (Native Method)
at jdk.internal.misc.Unsafe.ensureClassInitialized (Unsafe.java:1160)
at jdk.internal.reflect.MethodHandleAccessorFactory.ensureClassInitialized 
(MethodHandleAccessorFactory.java:300)
at jdk.internal.reflect.MethodHandleAccessorFactory.newConstructorAccessor 
(MethodHandleAccessorFactory.java:103)
at jdk.internal.reflect.ReflectionFactory.newConstructorAccessor 
(ReflectionFactory.java:200)
at java.lang.reflect.Constructor.acquireConstructorAccessor 
(Constructor.java:549)
at java.lang.reflect.Constructor.newInstanceWithCaller (Constructor.java:499)
at java.lang.reflect.Constructor.newInstance (Constructor.java:486) {code}
Adding {{nifi-standard-services-api-nar}} to the NAR packaging module fixes it.

To recreate the issue, generate a project and run mvn package.
{code:java}
mvn archetype:generate \
-DarchetypeGroupId=org.apache.nifi \
-DarchetypeArtifactId=nifi-processor-bundle-archetype \
-DnifiVersion=2.0.0-M1 \
-DartifactBaseName=example \
-DgroupId=org.example \
-DartifactId=myproject \
-Dversion=0.0.1 \
-Dpackage=org.example.processors.example {code}
{code:java}
cd myproject
mvn package {code}


> Processor Bundle Maven Archetype broken build
> -
>
> Key: NIFI-12608
> URL: https://issues.apache.org/jira/browse/NIFI-12608
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Tools and Build
>Affects Versions: 2.0.0-M1
>Reporter: Shane O'Neill
>Priority: Major
>
> I am seeing the {{mvn archetype:generate}} CLI fail to produce a buildable 
> project for the {{{}nifi-processor-bundle-archetype{}}}. The error is:
> {code:java}
> java.lang.ClassNotFoundException: 
> org.apache.nifi.processor.util.StandardValidators
> at java.net.URLClassLoader.findClass (URLClassLoader.java:445)
> at java.lang.ClassLoader.loadClass (ClassLoader.java:593)
> at java.lang.ClassLoader.loadClass (ClassLoader.java:526)
> at org.example.processors.example.MyProcessor. (MyProcessor.java:53)
> at jdk.internal.misc.Unsafe.ensureClassInitialized0 (Native Method)
> at jdk.internal.misc.Unsafe.ensureClassInitialized (Unsafe.java:1160)
> at jdk.internal.reflect.MethodHandleAccessorFactory.ensureClassInitialized 
> (MethodHandleAccessorFactory.java:300)
> at jdk.internal.reflect.MethodHandleAccessorFactory.newConstructorAccessor 
> (MethodHandleAccessorFactory.java:103)
> at jdk.inte

[jira] [Created] (NIFI-12608) Processor Bundle Maven Archetype broken build

[Shane O'Neill (Jira)]

Shane O'Neill created NIFI-12608:


 Summary: Processor Bundle Maven Archetype broken build
 Key: NIFI-12608
 URL: https://issues.apache.org/jira/browse/NIFI-12608
 Project: Apache NiFi
  Issue Type: Bug
  Components: Tools and Build
Affects Versions: 2.0.0-M1
Reporter: Shane O'Neill


I am seeing the {{mvn archetype:generate}} CLI fail to produce a buildable 
project for the {{{}nifi-processor-bundle-archetype{}}}. The error is:

 
Caused by: java.lang.ClassNotFoundException: 
org.apache.nifi.processor.util.StandardValidators
at java.net.URLClassLoader.findClass (URLClassLoader.java:445)
at java.lang.ClassLoader.loadClass (ClassLoader.java:593)
at java.lang.ClassLoader.loadClass (ClassLoader.java:526)
at org.example.processors.example.MyProcessor. (MyProcessor.java:53)
at jdk.internal.misc.Unsafe.ensureClassInitialized0 (Native Method)
at jdk.internal.misc.Unsafe.ensureClassInitialized (Unsafe.java:1160)
at jdk.internal.reflect.MethodHandleAccessorFactory.ensureClassInitialized 
(MethodHandleAccessorFactory.java:300)
at jdk.internal.reflect.MethodHandleAccessorFactory.newConstructorAccessor 
(MethodHandleAccessorFactory.java:103)
at jdk.internal.reflect.ReflectionFactory.newConstructorAccessor 
(ReflectionFactory.java:200)
at java.lang.reflect.Constructor.acquireConstructorAccessor 
(Constructor.java:549)
at java.lang.reflect.Constructor.newInstanceWithCaller 
(Constructor.java:499)
at java.lang.reflect.Constructor.newInstance (Constructor.java:486){{}}
Adding {{nifi-standard-services-api-nar}} to the NAR packaging module fixes it.

To recreate the issue, generate a project and run mvn package.

{{}}
mvn archetype:generate \
-DarchetypeGroupId=org.apache.nifi \
-DarchetypeArtifactId=nifi-processor-bundle-archetype \
-DnifiVersion=2.0.0-M1 \
-DartifactBaseName=example \
-DgroupId=org.example \
-DartifactId=myproject \
-Dversion=0.0.1 \
-Dpackage=org.example.processors.example
 
cd myproject
mvn package



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

[NOTICE] Apache Bahir moving to the Apache Attic shortly

[Shane Curcuru]

Apache Bahir will be moving to the Apache Attic after this month's board 
meeting.  Since the ASF doesn't have sufficient volunteers on the PMC 
who can reliably provide security support for the project, we need to 
let users know there won't be fixes coming.


Sometime in the next few weeks all Apache Bahir resources will be turned 
read-only.  This means that the ASF project here won't have any 
development or email traffic; however the website, email archives, and 
of course complete code history will be preserved for the long term. 
For more about what the Apache Attic does:


  https://attic.apache.org/

Thanks to everyone who's contributed to the Apache Bahir project for the 
past 7 years!!


Shane Curcuru wrote on 12/17/23 8:55 PM:

Dear Bahir community:

Given the lack of activity in the Apache Bahir project for a number of 
months, it's likely that the board will be voting to move the project 
into the Apache Attic soon.  That will mean all project resources will 
become read-only, but archived and still available.


Dear João Boto and Bahir PMC:

The board report for Bahir has not yet been submitted for this month's 
board meeting. If anyone on the PMC can still submit a report, that'd be 
great, although we realize the project has been dormant for some time. 
While you're always welcome to try to find three PMC members who can 
provide oversight of serious issues, it sounds like the time for the 
Attic is here, as you noted in a thread this past summer.


   https://www.apache.org/foundation/board/reporting#how

Thanks,

Shane Curcuru, Director

(on behalf of the ASF Board)


--
- Shane
  Director
  The Apache Software Foundation

[NOTICE] Apache Bahir moving to the Apache Attic shortly

[Shane Curcuru]

Apache Bahir will be moving to the Apache Attic after this month's board 
meeting.  Since the ASF doesn't have sufficient volunteers on the PMC 
who can reliably provide security support for the project, we need to 
let users know there won't be fixes coming.


Sometime in the next few weeks all Apache Bahir resources will be turned 
read-only.  This means that the ASF project here won't have any 
development or email traffic; however the website, email archives, and 
of course complete code history will be preserved for the long term. 
For more about what the Apache Attic does:


  https://attic.apache.org/

Thanks to everyone who's contributed to the Apache Bahir project for the 
past 7 years!!


Shane Curcuru wrote on 12/17/23 8:55 PM:

Dear Bahir community:

Given the lack of activity in the Apache Bahir project for a number of 
months, it's likely that the board will be voting to move the project 
into the Apache Attic soon.  That will mean all project resources will 
become read-only, but archived and still available.


Dear João Boto and Bahir PMC:

The board report for Bahir has not yet been submitted for this month's 
board meeting. If anyone on the PMC can still submit a report, that'd be 
great, although we realize the project has been dormant for some time. 
While you're always welcome to try to find three PMC members who can 
provide oversight of serious issues, it sounds like the time for the 
Attic is here, as you noted in a thread this past summer.


   https://www.apache.org/foundation/board/reporting#how

Thanks,

Shane Curcuru, Director

(on behalf of the ASF Board)


--
- Shane
  Director
  The Apache Software Foundation

Re: Apache Daffodil VSCode Extension Issue Input

[Shane Dell]

Thank you for this Mike. I do have some questions as to what the program, data 
and root
should be set for this schema. I posted the question here 
https://github.com/apache/daffodil-vscode/issues/653 if you can take a look 
when you have a change.

On 2024/01/02 20:17:28 Mike Beckerle wrote:
> Please see PR: https://github.com/DFDLSchemas/envelope-payload/pull/1
> 
> 
> On Tue, Jan 2, 2024 at 12:32 PM Mike Beckerle  wrote:
> 
> > I'm creating an envelope-payload example schema under DFDLSchemas on
> > github.
> >
> >
> > On Wed, Dec 27, 2023 at 1:49 PM Shane Dell  wrote:
> >
> >> Hello,
> >>
> >> I am reaching out to the dev community to ask for some help/input on an
> >> issue that is in the Apache Daffodil VSCode Extension GitHub repository.
> >> The specific issue I am referring to,
> >> https://github.com/apache/daffodil-vscode/issues/653, was reported by
> >> Mike
> >> Beckerle and we are looking for some help/input on a schema we can use to
> >> test what Mike is describing so that we are able to update the extensions
> >> debugger in the appropriate way. Any information would be greatly
> >> appreciated either through this email thread or by posting a comment to
> >> the
> >> linked GitHub Issue.
> >>
> >> Thank you,
> >>
> >> Shane Dell
> >>
> >
> 

Re: [FFmpeg-user] Intel QSV and xstack_qsv: Error while filtering: Internal bug, should not have happened

[Shane Warren]

It must be in the latest ffmpeg because I took all the hwupload and hwdownload 
out of my command and everything still works.

One question I have is:

Why is hwdownload not needed before the pad filter and hwupload needed after 
the pad filter. Before trying out intel's hw transcoding I used nvidia's cards 
and as far as I remember one always had to hwdownload when doing cpu filters 
and hwupload when going back to gpu filters or gpu encoding.

Anyway, thanks for the help, updated command survives resolution changes.


From: ffmpeg-user  on behalf of Dennis Mungai 

Sent: Thursday, December 28, 2023 1:23 AM
To: FFmpeg user questions 
Cc: artem.ga...@gmail.com ; Wang, Fei W 

Subject: Re: [FFmpeg-user] Intel QSV and xstack_qsv: Error while filtering: 
Internal bug, should not have happened


On Thu, 28 Dec 2023, 05:15 Xiang, Haihao, <
haihao.xiang-at-intel@ffmpeg.org> wrote:

>
> > I have created a bug and linked a sample video that changes resolutions
> on the
> > fly:
> >
> > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftrac.ffmpeg.org%2Fticket%2F10762=05%7C02%7Cshanew%40innovsys.com%7C16af3691f50e441b105e08dc0775eba2%7C7a48ce45ee974a95ac183390878a179b%7C0%7C0%7C638393450253894506%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=oxcuG2TePe4NNYrzXnCJkJsw5X5BDIJP6nIUzUvfSaM%3D=0<https://trac.ffmpeg.org/ticket/10762>
> >
> > Get back to me if you need anything else I can help with.
> > 
> > From: ffmpeg-user  on behalf of Dennis
> Mungai
> > 
> > Sent: Wednesday, December 27, 2023 11:38 AM
> > To: FFmpeg user questions 
> > Cc: Haihao ;
> > artem.ga...@gmail.com ;
> > fei.w.w...@intel.com 
> > Subject: Re: [FFmpeg-user] Intel QSV and xstack_qsv: Error while
> filtering:
> > Internal bug, should not have happened
> >
> > [You don't often get email from dmng...@gmail.com. Learn why this is
> important
> > at https://aka.ms/LearnAboutSenderIdentification ]
> >
> > This email originated from outside Innovative Systems. Do not click
> links or
> > open attachments unless you recognize the sender and know the content is
> safe.
> >
> >
> > On Wed, 27 Dec 2023 at 18:40, Shane Warren  wrote:
> >
> > >
> > > I'm testing out an Intel Flex 140 card and I am attempting to
> transcode 4
> > > inputs to 1 output using the xstack_qsv filter.  My command takes in 4
> udp
> > > multicast ts files (h264 encoded) and outputs one h264_qsv encoded udp
> > > transport stream. My command looks like so:
> > >
> > > /tmp/ffmpeg_g  -nostats -loglevel verbose -init_hw_device
> > > qsv=card1:/dev/dri/card1 -hwaccel_device card1 -filter_hw_device card1
>
> Please use a render node instead, and you should use the key of
> child_device if
> you want to use a non-default render node:
>
> qsv=card1,child_device=/dev/dri/renderD129 -hwaccel_device card1 -
> filter_hw_device card1
>
>
> > > -fflags discardcorrupt  -fflags +genpts -fflags discardcorrupt  \
> > > -hwaccel qsv -hwaccel_output_format qsv -thread_queue_size 4096
> > > -async_depth 1 -i "udp://@
> > >
> 225.105.0.1:10102?fifo_size=214688_size=851968=80
> > > _nonfatal=1"
> > > \
> > > -hwaccel qsv -hwaccel_output_format qsv -thread_queue_size 4096
> > > -async_depth 1 -i "udp://@
> > >
> 225.105.0.14:10102?fifo_size=214688_size=851968=80
> > > n_nonfatal=1"
> > > \
> > > -hwaccel qsv -hwaccel_output_format qsv -thread_queue_size 4096
> > > -async_depth 1 -i "udp://@
> > >
> 225.105.0.5:10102?fifo_size=214688_size=851968=80
> > > _nonfatal=1"
> > > \
> > > -hwaccel qsv -hwaccel_output_format qsv -thread_queue_size 4096
> > > -async_depth 1 -i "udp://@
> > >
> 225.105.0.4:10102?fifo_size=214688_size=851968=80
> > > _nonfatal=1"
> > > \
> > > -noautoscale -filter_complex "\
> > > [0:v]vpp_qsv=deinterlace=2:w=720:h=480:framerate=3/1001[v1]; \
> > > [1:v]vpp_qsv=deinterlace=2:w=720:h=480:framerate=3/1001[v2]; \
> > > [2:v]vpp_qsv=deinterlace=2:w=720:h=480:framerate=3/1001[v3]; \
> > > [3:v]vpp_qsv=deinterlace=2:w=720:h=480:framerate=3/1001[v4]; \
> > > [v1][v2][v3][v4]
> xstack_qsv=inputs=4:layout=0_0|0_h0|w0_0|w0_h0[mosiac]; \
> > > [mosiac]vpp_qsv=w=1920:h=1080,hwdownload,format=nv12,pad=1920:1080:(ow-
> > > iw)/2:(oh-ih)/2,hwupload=extra_hw_frames=64,format=qsv[v]"
>
> -c:v h264_qsv encoder

Re: [FFmpeg-user] Intel QSV and xstack_qsv: Error while filtering: Internal bug, should not have happened

[Shane Warren]

I have created a bug and linked a sample video that changes resolutions on the 
fly:

https://trac.ffmpeg.org/ticket/10762

Get back to me if you need anything else I can help with.

From: ffmpeg-user  on behalf of Dennis Mungai 

Sent: Wednesday, December 27, 2023 11:38 AM
To: FFmpeg user questions 
Cc: Haihao ; artem.ga...@gmail.com 
; fei.w.w...@intel.com 
Subject: Re: [FFmpeg-user] Intel QSV and xstack_qsv: Error while filtering: 
Internal bug, should not have happened

[You don't often get email from dmng...@gmail.com. Learn why this is important 
at https://aka.ms/LearnAboutSenderIdentification ]

This email originated from outside Innovative Systems. Do not click links or 
open attachments unless you recognize the sender and know the content is safe.


On Wed, 27 Dec 2023 at 18:40, Shane Warren  wrote:

>
> I'm testing out an Intel Flex 140 card and I am attempting to transcode 4
> inputs to 1 output using the xstack_qsv filter.  My command takes in 4 udp
> multicast ts files (h264 encoded) and outputs one h264_qsv encoded udp
> transport stream. My command looks like so:
>
> /tmp/ffmpeg_g  -nostats -loglevel verbose -init_hw_device
> qsv=card1:/dev/dri/card1 -hwaccel_device card1 -filter_hw_device card1
> -fflags discardcorrupt  -fflags +genpts -fflags discardcorrupt  \
> -hwaccel qsv -hwaccel_output_format qsv -thread_queue_size 4096
> -async_depth 1 -i "udp://@
> 225.105.0.1:10102?fifo_size=214688_size=851968=80_nonfatal=1"
> \
> -hwaccel qsv -hwaccel_output_format qsv -thread_queue_size 4096
> -async_depth 1 -i "udp://@
> 225.105.0.14:10102?fifo_size=214688_size=851968=80_nonfatal=1"
> \
> -hwaccel qsv -hwaccel_output_format qsv -thread_queue_size 4096
> -async_depth 1 -i "udp://@
> 225.105.0.5:10102?fifo_size=214688_size=851968=80_nonfatal=1"
> \
> -hwaccel qsv -hwaccel_output_format qsv -thread_queue_size 4096
> -async_depth 1 -i "udp://@
> 225.105.0.4:10102?fifo_size=214688_size=851968=80_nonfatal=1"
> \
> -noautoscale -filter_complex "\
> [0:v]vpp_qsv=deinterlace=2:w=720:h=480:framerate=3/1001[v1]; \
> [1:v]vpp_qsv=deinterlace=2:w=720:h=480:framerate=3/1001[v2]; \
> [2:v]vpp_qsv=deinterlace=2:w=720:h=480:framerate=3/1001[v3]; \
> [3:v]vpp_qsv=deinterlace=2:w=720:h=480:framerate=3/1001[v4]; \
> [v1][v2][v3][v4] xstack_qsv=inputs=4:layout=0_0|0_h0|w0_0|w0_h0[mosiac]; \
> [mosiac]vpp_qsv=w=1920:h=1080,hwdownload,format=nv12,pad=1920:1080:(ow-iw)/2:(oh-ih)/2,hwupload=extra_hw_frames=64,format=qsv[v]"
> \
> -map "[v]" -map 0:a:0 -map 1:a:0 -map 2:a:0 -map 3:a:0 \
> -c:v h264_qsv -noautoscale -async_depth 1 -scenario livestreaming -r:v
> 3/1001 -b:v 6000k -minrate:v 6000k -maxrate:v 6000k -bufsize:v 12000k
> -threads 1 -profile:v high -bf:v 0 -g:v 15 \
> -filter:a "aresample=async=1" -c:a aac -ac:a 2 -ar:a 48000 -b:a 192k
> -fps_mode auto \
> -f mpegts -muxrate 7450599 -pes_payload_size 1528 "udp://@
> 229.100.100.44:10102?pkt_size=1316_size=9=7450599_bits=10528
> "
>
> The issue is eventually stream 1 changes resolution from 1280x720
> (progressive) to 1920x1080 (interlaced). The stream dies with the following
> logs coming out:
>
> [h264_qsv @ 0x55a240e68000] Error submitting the frame for encoding.
> [vost#0:0/h264_qsv @ 0x55a240e30780] Error submitting video frame to the
> encoder
> Error while filtering: Internal bug, should not have happened
>
> I can transcode the single stream that changes resolution on its own and
> it can survive a resolution change using this command:
>
> /tmp/ffmpeg_g  -nostats -loglevel verbose -init_hw_device
> qsv=card1:/dev/dri/card1 -hwaccel_device card1 -filter_hw_device card1
> -fflags discardcorrupt  -fflags +genpts -fflags discardcorrupt  -hwaccel
> qsv -hwaccel_output_format qsv -async_depth 1 -i "udp://@
> 225.105.0.1:10102?fifo_size=214688_size=851968=80_nonfatal=1"
> -vf "vpp_qsv=deinterlace=2:w=1920:h=1080:framerate=3/1001" -map "0:v"
> -map 0:a:0 -c:v h264_qsv -noautoscale  -async_depth 1 -scenario
> livestreaming -r:v 3/1001 -b:v 5000k -minrate:v 5000k -maxrate:v 5000k
> -bufsize:v 1k -a53cc 1 -forced_idr 1 -threads 1 -profile:v high -bf:v 0
> -g:v 15 -filter:a "aresample=async=1" -c:a aac -ac:a 2 -ar:a 48000 -b:a
> 192k -fps_mode auto -f mpegts -muxrate 6450599 -pes_payload_size 1528
> "udp://@
> 229.100.100.44:10102?pkt_size=1316_size=9=6450599_bits=10528
> "
>
> When that stream changes resolution I see these come out in the log, and
> the stream carries on without dying:
>
> [h264_qsv @ 0x561bc472f8c0] Video parameter change
> [AVHWDeviceContext @ 0x7f313000d1c0] VAAPI driver: Intel iHD driver for
> Intel(R

Apache Daffodil VSCode Extension Issue Input

[Shane Dell]

Hello,

I am reaching out to the dev community to ask for some help/input on an
issue that is in the Apache Daffodil VSCode Extension GitHub repository.
The specific issue I am referring to,
https://github.com/apache/daffodil-vscode/issues/653, was reported by Mike
Beckerle and we are looking for some help/input on a schema we can use to
test what Mike is describing so that we are able to update the extensions
debugger in the appropriate way. Any information would be greatly
appreciated either through this email thread or by posting a comment to the
linked GitHub Issue.

Thank you,

Shane Dell

[FFmpeg-user] Intel QSV and xstack_qsv: Error while filtering: Internal bug, should not have happened

[Shane Warren]

I'm testing out an Intel Flex 140 card and I am attempting to transcode 4 
inputs to 1 output using the xstack_qsv filter.  My command takes in 4 udp 
multicast ts files (h264 encoded) and outputs one h264_qsv encoded udp 
transport stream. My command looks like so:

/tmp/ffmpeg_g  -nostats -loglevel verbose -init_hw_device 
qsv=card1:/dev/dri/card1 -hwaccel_device card1 -filter_hw_device card1 -fflags 
discardcorrupt  -fflags +genpts -fflags discardcorrupt  \
-hwaccel qsv -hwaccel_output_format qsv -thread_queue_size 4096 -async_depth 1 
-i 
"udp://@225.105.0.1:10102?fifo_size=214688_size=851968=80_nonfatal=1"
 \
-hwaccel qsv -hwaccel_output_format qsv -thread_queue_size 4096 -async_depth 1 
-i 
"udp://@225.105.0.14:10102?fifo_size=214688_size=851968=80_nonfatal=1"
 \
-hwaccel qsv -hwaccel_output_format qsv -thread_queue_size 4096 -async_depth 1 
-i 
"udp://@225.105.0.5:10102?fifo_size=214688_size=851968=80_nonfatal=1"
 \
-hwaccel qsv -hwaccel_output_format qsv -thread_queue_size 4096 -async_depth 1 
-i 
"udp://@225.105.0.4:10102?fifo_size=214688_size=851968=80_nonfatal=1"
 \
-noautoscale -filter_complex "\
[0:v]vpp_qsv=deinterlace=2:w=720:h=480:framerate=3/1001[v1]; \
[1:v]vpp_qsv=deinterlace=2:w=720:h=480:framerate=3/1001[v2]; \
[2:v]vpp_qsv=deinterlace=2:w=720:h=480:framerate=3/1001[v3]; \
[3:v]vpp_qsv=deinterlace=2:w=720:h=480:framerate=3/1001[v4]; \
[v1][v2][v3][v4] xstack_qsv=inputs=4:layout=0_0|0_h0|w0_0|w0_h0[mosiac]; \
[mosiac]vpp_qsv=w=1920:h=1080,hwdownload,format=nv12,pad=1920:1080:(ow-iw)/2:(oh-ih)/2,hwupload=extra_hw_frames=64,format=qsv[v]"
  \
-map "[v]" -map 0:a:0 -map 1:a:0 -map 2:a:0 -map 3:a:0 \
-c:v h264_qsv -noautoscale -async_depth 1 -scenario livestreaming -r:v 
3/1001 -b:v 6000k -minrate:v 6000k -maxrate:v 6000k -bufsize:v 12000k 
-threads 1 -profile:v high -bf:v 0 -g:v 15 \
-filter:a "aresample=async=1" -c:a aac -ac:a 2 -ar:a 48000 -b:a 192k -fps_mode 
auto \
-f mpegts -muxrate 7450599 -pes_payload_size 1528 
"udp://@229.100.100.44:10102?pkt_size=1316_size=9=7450599_bits=10528"

The issue is eventually stream 1 changes resolution from 1280x720 (progressive) 
to 1920x1080 (interlaced). The stream dies with the following logs coming out:

[h264_qsv @ 0x55a240e68000] Error submitting the frame for encoding.
[vost#0:0/h264_qsv @ 0x55a240e30780] Error submitting video frame to the encoder
Error while filtering: Internal bug, should not have happened

I can transcode the single stream that changes resolution on its own and it can 
survive a resolution change using this command:

/tmp/ffmpeg_g  -nostats -loglevel verbose -init_hw_device 
qsv=card1:/dev/dri/card1 -hwaccel_device card1 -filter_hw_device card1 -fflags 
discardcorrupt  -fflags +genpts -fflags discardcorrupt  -hwaccel qsv 
-hwaccel_output_format qsv -async_depth 1 -i 
"udp://@225.105.0.1:10102?fifo_size=214688_size=851968=80_nonfatal=1"
 -vf "vpp_qsv=deinterlace=2:w=1920:h=1080:framerate=3/1001" -map "0:v" -map 
0:a:0 -c:v h264_qsv -noautoscale  -async_depth 1 -scenario livestreaming -r:v 
3/1001 -b:v 5000k -minrate:v 5000k -maxrate:v 5000k -bufsize:v 1k 
-a53cc 1 -forced_idr 1 -threads 1 -profile:v high -bf:v 0 -g:v 15 -filter:a 
"aresample=async=1" -c:a aac -ac:a 2 -ar:a 48000 -b:a 192k -fps_mode auto -f 
mpegts -muxrate 6450599 -pes_payload_size 1528 
"udp://@229.100.100.44:10102?pkt_size=1316_size=9=6450599_bits=10528"

When that stream changes resolution I see these come out in the log, and the 
stream carries on without dying:

[h264_qsv @ 0x561bc472f8c0] Video parameter change
[AVHWDeviceContext @ 0x7f313000d1c0] VAAPI driver: Intel iHD driver for 
Intel(R) Gen Graphics - 23.2.4 ().
[AVHWDeviceContext @ 0x7f313000d1c0] Driver not found in known nonstandard 
list, using standard behaviour.
[h264_qsv @ 0x561bc472f8c0] Decoder: output is video memory surface

My quesiton is why does the stream die when using xstack_qsv but works fine on 
its own.


___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".

Re: [gatortalk] Let's play Pick 'em

[Shane Ford]

Merry Christmas and Happy Holidays to all my Gators out there for sure!  YES!  I so wish that we could go back to the Spirrier years!  Fun times!!! Sent from Shane’s iPhoneGo Gators! On Dec 23, 2023, at 11:12 AM, 'Scott Lucas' via GatorTalk  wrote:
It has been quite the ride... but can we go back to the Spurrier years?  LOLMerry Christmas, Happy Holidays, and Happy New Year to you all!Scott





On Saturday, December 23, 2023 at 08:55:25 AM EST,   wrote:



I predict the Gators will be undefeated this bowl season.Merry Christmas to all my GatorNet friends.  I still would love to have a reunion someday!  It is hard to believe we have kept this going for all these years.  Jerry  Sent from my iPhoneOn Dec 23, 2023, at 6:03 AM, John Bowers  wrote:Happy Holidays, Gators. Hey, the basketball team is playing well at leastTime for a Bowl Extravaganza Pick 'Em.https://pickem.g8r.comGood luck and here's to a happier 2024, Gator football-wise.John and Oz



-- 
-- 
GATORS: ONE VOICE ON SATURDAY - NO VOICE ON SUNDAY!
1996 National Football Champions   |  2006 National Basketball Champions 2006 National Football Champions   |   2007 National Basketball Champions 2008 National Football Champions   |   Three Heisman Trophy winners: Steve Spurrier (1966), Danny Wuerffel (1996), Tim Tebow (2007)
--- 
You received this message because you are subscribed to the Google Groups "GatorTalk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to gatortalk+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/gatortalk/e2c1ad54bb875abd843c08cd0af7aa093f9f7832%40webmail.


-- 
-- 
GATORS: ONE VOICE ON SATURDAY - NO VOICE ON SUNDAY!
1996 National Football Champions   |  2006 National Basketball Champions 2006 National Football Champions   |   2007 National Basketball Champions 2008 National Football Champions   |   Three Heisman Trophy winners: Steve Spurrier (1966), Danny Wuerffel (1996), Tim Tebow (2007)
--- 
You received this message because you are subscribed to the Google Groups "GatorTalk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to gatortalk+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/gatortalk/27FE3473-1D11-4B74-AB1E-A79AC73EC839%40gmail.com.






-- 
-- 
GATORS: ONE VOICE ON SATURDAY - NO VOICE ON SUNDAY!
1996 National Football Champions   |  2006 National Basketball Champions 2006 National Football Champions   |   2007 National Basketball Champions 2008 National Football Champions   |   Three Heisman Trophy winners: Steve Spurrier (1966), Danny Wuerffel (1996), Tim Tebow (2007)
--- 
You received this message because you are subscribed to the Google Groups "GatorTalk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to gatortalk+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/gatortalk/1994747225.4778471.1703351520523%40mail.yahoo.com.




-- 
-- 
GATORS: ONE VOICE ON SATURDAY - NO VOICE ON SUNDAY!
1996 National Football Champions   |  2006 National Basketball Champions 2006 National Football Champions   |   2007 National Basketball Champions 2008 National Football Champions   |   Three Heisman Trophy winners: Steve Spurrier (1966), Danny Wuerffel (1996), Tim Tebow (2007)
--- 
You received this message because you are subscribed to the Google Groups "GatorTalk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to gatortalk+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/gatortalk/C15CB21B-4524-4A9A-B558-4DFF2B1912DA%40gmail.com.

owner notification close the topic: Re[2]: [blind-gamers] REQUEST FOR SIGNING THE PETITION REINSTATE FOREVER THE BASIC HTML VIEWER FOR VISUALLY IMPAIRED USERS

[Shane Popplestone]

This topic is not meant for this list, and it's closed, as of right now.

Further messages will be met with immediate moderation.
-- Original Message --

From "Mongwen" 

To blind-gamers@groups.io
Date 12/21/2023 7:59:45 AM
Subject Re: [blind-gamers] REQUEST FOR SIGNING THE PETITION REINSTATE
FOREVER THE BASIC HTML VIEWER FOR VISUALLY IMPAIRED USERS


I signed it. I don't use the web interface at all unless I am looking
for something in the spam folder, but I think simple views should
always be available no matter how accessible google thinks its intended
change is. Someone refusing to sign because they personally like the
new gmail isn't really getting to the point of the issue. I like
options and I don't like when options are taken away. The new gmail
would still be an option you can use if you like, and he isn't
suggesting any different. Sites have become more and more complicated
in their coding and so-called features, and there always needs to be a
simple option for those less computer savvy or who simply like things
straightforward. What seems accessible to one may be problematic for
another. Just my two cents.



On 12/21/2023 7:25 AM, Oriol Gómez wrote:

No thanks, I quite like the new GMail.

El jue, 21 dic 2023 a las 13:24, FARHAD ALI BHATTI (<
farhad.dangerous...@gmail.com>) escribió:

https://chng.it/BPmvGGw8wm









--
This email has been checked for viruses by Avast antivirus software.
www.avast.com


-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#126907): https://groups.io/g/blind-gamers/message/126907
Mute This Topic: https://groups.io/mt/103301899/21656
Group Owner: blind-gamers+ow...@groups.io
Unsubscribe: 
https://groups.io/g/blind-gamers/leave/607459/21656/1071380848/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Missing Bahir Board Report - likely move to Apache Attic by next month

[Shane Curcuru]

Dear Bahir community:

Given the lack of activity in the Apache Bahir project for a number of 
months, it's likely that the board will be voting to move the project 
into the Apache Attic soon.  That will mean all project resources will 
become read-only, but archived and still available.


Dear João Boto and Bahir PMC:

The board report for Bahir has not yet been submitted for this month's 
board meeting. If anyone on the PMC can still submit a report, that'd be 
great, although we realize the project has been dormant for some time. 
While you're always welcome to try to find three PMC members who can 
provide oversight of serious issues, it sounds like the time for the 
Attic is here, as you noted in a thread this past summer.


  https://www.apache.org/foundation/board/reporting#how

Thanks,

Shane Curcuru, Director

(on behalf of the ASF Board)

Re: Legal help to (Apache) NuttX RTOS: adding licenseed driver

[Shane Curcuru]

Gregory Nutt wrote on 12/10/23 5:22 PM:


On 12/10/2023 4:05 PM, Shane Curcuru wrote:


I think we have to be careful with the word "contribution".  The ASF 
cannot accept any contribution that is licensed and copyrighted by 
some other entity.  To "contribute" the code is to donate the code to 
the ASF without retaining any claims to it. Then the code belongs to 
the ASF and can be re-licensed as Apache 2.0 with the ASF copyright.


Er, no, that's not how the ASF treats "contributions".  In general, 
when someone contributes their copyrighted work to an Apache project, 
they keep the copyright, and merely license enough rights to the ASF 
such that the ASF (through our projects) can then re-ship that 
contribution at any point in the future as part of a larger work, 
under terms like the Apache-2.0 license.

...[snip]...


That use of the word "contribution" is causing me a little cognitive 
dissonance, but I will adapt.  Synonyms for "contribution" include 
donation, gift, present, grant, etc., most which are not interchangeable 
with "contribution" in this context.


"Contribution" is a specific term defined in the Apache-2.0 license, so 
when we're using it in reference to someone committing code (or other 
things) to an ASF repository, we're using the specific definition there.


  https://www.apache.org/licenses/LICENSE-2.0#definitions

How does the copyright holder "license enough rights to the ASF"?  I 
suppose that is via the license that they chose for the work, rather 
than through any specific interaction with the ASF?


If the copyright holder is a committer on any ASF project, then they've 
already signed the ICLA, which lays out in detail what they agree to 
whenever they're checking in code to any ASF repository.


  https://www.apache.org/licenses/contributor-agreements.html

So if you're looking for general information, the first step is to read 
the license and ICLA in detail, and then ask questions relating to 
specific parts therein.


But it feels like we've lost sight of the actual question for the 
project, which is something about "is it OK to accept *this* bit of code 
in our repository" - or something like that.


If the project is looking for an answer about legal questions, it always 
helps to be *very* specific about what you want to do, as in "Is it OK 
if so-and-so checks in this file ->, which is under this license -> to 
our project in this directory?" or the like.


In general, in terms of code with multiple licenses, one question the 
ASF likes to ask is that the copyright owner of the code is explicitly 
saying it's available under a permissive license, or is otherwise 
helping to commit the code at the ASF.  That's not strictly a legal 
question, more a policy one: the ASF prefers contributions into our 
project repositories that are *willingly* given (and are licensed 
appropriately).


I hope that helps more than confuses things!

--
- Shane
  Member
  The Apache Software Foundation

Re: Legal help to (Apache) NuttX RTOS: adding licenseed driver

[Shane Curcuru]

Gregory Nutt wrote on 12/10/23 9:54 AM:

On 12/10/2023 7:15 AM, Alan C. Assis wrote:

I understand your point. And in fact I think the issue is not your
contribution itself, but the future contribution from developers of RTEMS
and Linux that are using GPL.


I think we have to be careful with the word "contribution".  The ASF 
cannot accept any contribution that is licensed and copyrighted by some 
other entity.  To "contribute" the code is to donate the code to the ASF 
without retaining any claims to it. Then the code belongs to the ASF and 
can be re-licensed as Apache 2.0 with the ASF copyright.


Er, no, that's not how the ASF treats "contributions".  In general, when 
someone contributes their copyrighted work to an Apache project, they 
keep the copyright, and merely license enough rights to the ASF such 
that the ASF (through our projects) can then re-ship that contribution 
at any point in the future as part of a larger work, under terms like 
the Apache-2.0 license.


Any contributions still "belong" copyright-wise to the original author, 
who can continue to do whatever else they want with their code, 
including submitting to other projects, possibly under other licenses.


The legal framework for contributions is twofold, so folks interested in 
details really need to read both of these:


- Apache-2.0 license, section 5. Submission of Contributions
  https://www.apache.org/licenses/LICENSE-2.0#contributions

- Individual Contributor License Agreement
  https://www.apache.org/licenses/contributor-agreements.html#clas

The point is that the ASF only takes enough licensed rights so that we 
can safely ship code in our projects, *and* so that users of Apache 
projects only have to comply with the Apache-2.0 license overall.


--
- Shane
  Member
  The Apache Software Foundation

[PDB Announce] Production Deployment 2.53.0

[Shane Wadleigh]

2.53.0 was successfully released to production, changes can be viewed at [0].

If anyone encounters any problems, please contact supp...@peeringdb.com

Cheers

[0] https://docs.peeringdb.com/release_notes/
___
Pdb-announce mailing list
Pdb-announce@lists.peeringdb.com
https://lists.peeringdb.com/cgi-bin/mailman/listinfo/pdb-announce

[Frameworks] Tenure-Track Assistant Professor in Digital Media Production (FAU) >>> DEADLINE EXTENDED

[Shane Eason]

FYI…

The deadline for applications for the Tenure-Track Assistant Professor in 
Digital Media Production at Florida Atlantic University has been extended to 
December 11, 2023.

https://fau.wd1.myworkdayjobs.com/en-US/FAU/job/Assistant-Professor_REQ17083 
 

Cheers,

SCE-- 
Frameworks mailing list
Frameworks@film-gallery.org
https://mail.film-gallery.org/mailman/listinfo/frameworks_film-gallery.org

[jira] [Commented] (SPARK-37571) decouple amplab jenkins from spark website, builds and tests

[Shane Knapp (Jira)]

[ 
https://issues.apache.org/jira/browse/SPARK-37571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17793420#comment-17793420
 ] 

Shane Knapp commented on SPARK-37571:
-

a blast from the past!  XD

sounds good to me...  there are still some vestiges of amplab and jenkins in 
some bits of the repo but nothing really to write home about:

[https://github.com/search?q=repo%3Aapache%2Fspark+amplab=code]

[https://github.com/search?q=repo%3Aapache%2Fspark+jenkins=code]

the 'jenkins' entries *mostly* look to be setting bits for tests' setup and my 
quick perusal didn't raise any flags.  it might be a decent idea to audit this 
stuff at some point and pull it out.  :shrug:

> decouple amplab jenkins from spark website, builds and tests
> 
>
> Key: SPARK-37571
> URL: https://issues.apache.org/jira/browse/SPARK-37571
> Project: Spark
>  Issue Type: Improvement
>  Components: Build
>Affects Versions: 3.3.0
>Reporter: Shane Knapp
>Assignee: Shane Knapp
>Priority: Major
> Attachments: audit.txt, spark-repo-to-be-audited.txt
>
>
> we will be turning off jenkins on dec 23rd, and we need to decouple the build 
> infra from jenkins, as well as remove any amplab jenkins-specific docs on the 
> website, scripts and infra setup.
> i'll be creating > 1 PRs for this.



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

-
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org

Re: Resizing EBS with ZFS on AWS

[Shane Ambler]

On 2/12/23 11:26, Shane Ambler wrote:
> Hi,
> 
> I recently started an EC2 with the 14.0 ZFS AMI
> 
> After filling the drive, I expanded it, recovered the gpart partition
> and expanded the partition and zpool size and kept going.
> 
> Then I saw that I would need more space, so I have expanded the EBS vol
> again, while the EC2 was shutdown. This time the EC2 will not boot.
> 
> Using the EC2 console I get to...
> 
> Trying to mount root from zfs:zroot/ROOT/default []...
> Mounting from zfs:zroot/ROOT/default failed with error 2: unknown file
> system.
> GEOM: nda0: the secondary GPT header is not in the last LBA.
> 
> 
> What can I do at mountroot> to recover gpart? or boot from here?
> 

OK so it seems the expanding disk was a red herring, I had altered
loader.conf to break boot.

I came up with steps to attach the unbootable EBS to another instance,
import the pool, fix loader.conf, then re-attached to the original
instance and got it to boot.

Might need to document these cloud recovery steps somewhere.

-- 
FreeBSD - the place to B...Scaring Daemons

Shane Ambler

Resizing EBS with ZFS on AWS

[Shane Ambler]

Hi,

I recently started an EC2 with the 14.0 ZFS AMI

After filling the drive, I expanded it, recovered the gpart partition
and expanded the partition and zpool size and kept going.

Then I saw that I would need more space, so I have expanded the EBS vol
again, while the EC2 was shutdown. This time the EC2 will not boot.

Using the EC2 console I get to...


nvme0: SET_FEATURES (09) sqid:0 cid:15 nsid:0 cdw10:000b cdw11:031f
nvme0: INVALID_FIELD (00/02) crd:0 m:1 dnr:0 p:1 sqid:0 cid:15 cdw0:0
nda0 at nvme0 bus 0 scbus0 target 0 lun 1
nda0: 
nda0: Serial Number vol0f445f0597836b567
nda0: nvme version 1.4
nda0: 153600MB (314572800 512 byte sectors)
Trying to mount root from zfs:zroot/ROOT/default []...
Mounting from zfs:zroot/ROOT/default failed with error 2: unknown file
system.
GEOM: nda0: the secondary GPT header is not in the last LBA.


What can I do at mountroot> to recover gpart? or boot from here?

-- 
FreeBSD - the place to B...Serving Data

Shane Ambler