CB-11074: Ensure settings from config.xml are taken into consideration

#7 is also supposed to address this issue, but in my tests it didn't work.
This pull request presents a workaround that requires two WKWebView instances to be inited (only one is kept and used for the app though). This isn't supposed to be merged as is, it's more a proof of concept and designed to provide exposure to the workaround if others users need this fix urgently.

@shazron the logic presented in this PR would have been made more complicated via the updateWithInfo: method, which as far as I could see is unused, so I removed it for now. Other than that, what do you think about this as general direction?
As I commented in #7, the best approach for this would be to change CDVViewController.m to pass in the settings directly on init, or to rearrange the check logic there. That is a longer-term solution. In the meantime, maybe we can get by with the approach presented here.

I also commented on #7.
To solve this problem, instead of having to instantiate WKWebView twice here, I think we can safely move all initializing code from the initWithFrame, to pluginInitialize:
https://github.com/apache/cordova-plugin-wkwebview-engine/blob/33a75172a1450e8922788cd23382cc6ec33845c7/src/ios/CDVWKWebViewEngine.m#L50-L64 -- all we need to do is save the CGRect for the frame for later. At this point, with this approach, the WKWebView will have been instantiated for this return call: https://github.com/apache/cordova-ios/blob/e51eda0f3b1e68d210182c3bbd3d9022c1ffe8ec/CordovaLib/Classes/Public/CDVViewController.m#L426
As I mentioned in #7, we still need updateWithInfo.
The rest of your approach is sound.

@shazron in that case we'd have to remove the configuration code from updateWithInfo because we've already established that it doesn't do anything anyway. It'd be very frustrating for a new developer to see that code and wonder why it does nothing at all. As far as I can see it will never work, wkWebView.configuration is listed as read-only in Apple's docs. I'd also rename updateWithInfo to updateDelegates or similar unless it breaks something else.
If we just inited the WKWebView once in pluginInitialize, I'm pretty certain the CDVViewController.m would fail at the canLoadRequest: check and then proceed to replace the WKWebViewEngine with defaultWebViewEngineClass, as commented in #7:
if ( (...) || ![self.webViewEngine canLoadRequest:[NSURLRequest requestWithURL:self.appUrl]]) {
    self.webViewEngine = [[NSClassFromString(defaultWebViewEngineClass) alloc] initWithFrame:bounds];
}

Specifically this is due to the following code in CDVWKWebViewEngine: https://github.com/apache/cordova-plugin-wkwebview-engine/blob/33a75172a1450e8922788cd23382cc6ec33845c7/src/ios/CDVWKWebViewEngine.m#L136
_engineWebView would still be nil here (because pluginInitialize wouldn't have been called), which would as far as I understand (I'm Swift-first, ObjC when necessary) be coerced to NO, making the above check fail.
As far as I can see, the only clean solution to this would be to pass settings into the WebViewEngine's init method. That is probably also the most logical and explicit way about getting the settings from config.xml into the WebView.

I'm creating failing unit tests for this first, I think we have passed the point where we can argue about the implementation, but we need objective verification: https://issues.apache.org/jira/browse/CB-11496

I commented on #7, updateWithInfo needs to be changed to not allow updating the WKWebViewConfiguration, because you can't update it at runtime -- I objectively verified this in the updated unit tests.

Please see #13, and let's continue discussion there.

Please provide feedback on #13, I will be pulling that in soon.


DeepSpeech looks good, but KWS became weird (I guess it was added with previous labels in mind). It should be:

Source
W (input - time)
H (input)
C (channels)
N (batch size)
K  (number of filters)
R (filter height)
S (filter width)
pad_h
pad_w
Vertical Stride
Horizontal Stride

KWS
151
40
1
1
32
5
20
8
8
2
8

Wow, I take a look at the code and found that it messed up:
spreadsheets do not fit conv_problems.h
different implementations read parameters inconsistently
I propose to always specify horisontal spatial parameter first. That way table became more consistent and less error prone:
Source | W (input - time) | H (input) | C (channels) | N (batch size) | K
(number of filters) | S (filter width) | R (filter height) | pad_w | pad_h | Horizontal Stride | Vertical Stride
-- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | --
DeepSpeech | 700 | 161 | 1 | 1 | 32 | 20 | 5 | 0 | 0 | 2 | 2
DeepSpeech | 700 | 161 | 1 | 2 | 32 | 20 | 5 | 0 | 0 | 2 | 2
DeepSpeech | 700 | 161 | 1 | 4 | 32 | 20 | 5 | 0 | 0 | 2 | 2
DeepSpeech | 341 | 79 | 32 | 1 | 32 | 10 | 5 | 0 | 0 | 2 | 2
DeepSpeech | 341 | 79 | 32 | 2 | 32 | 10 | 5 | 0 | 0 | 2 | 2
DeepSpeech | 341 | 79 | 32 | 4 | 32 | 10 | 5 | 0 | 0 | 2 | 2
KWS | 151 | 40 | 1 | 1 | 32 | 20 | 5 | 8 | 8 | 8 | 2
Also the same sequence of parameters should be used for both spreadsheets and header files.

@Kirpich30000 , thanks for looking into this. I think the problem is limited to the ARM convolution code where R is used as the filter width. This doesn't impact any of the results since ARM convolutions only support square filters.
You're right about the KWS kernel. I'll update it in the spreadsheet.
Additionally, I agree regarding your proposed format. #53 updates the code but not the spreadsheets. I can do it as a part of this PR.

@sharannarang note that the KWS kernel in conv_problems.h also have bug with stride - wstride should be 8 and hstride is 2.

#53 updates the code but not the spreadsheets. I can do it as a part of this PR.

I'm totaly fine if you do all changes as a part of this PR.

Alright, all the code updates and changes to excel files are now part of this PR. The KWS kernel is also updated and results in a segmentation fault. So, I've left it commented out.
Thanks for looking into this @Kirpich30000 . Can you look over this briefly to make sure I've covered everything we discussed?

I've eyeballed some spreadsheets with results and spotted few more things:

P, Q params not always follow "width first" rule
For RaspberryPI formulas for P and Q are mixes w and h in same formula
Formulas for P and Q are not precise:

Result is not rounded which affects teraflops calculation
Cells are formated to show only integer part. Still resulted format will not always show correct value
Correct formula for symmetric padding is: outputDim = 1 + (inputDim - filterDim + 2 * pad) / stride, where result of division is rounded down.

@Kirpich30000 , I've updated the spreadsheets to reflect the correct formulas for output height and width calculations and the ordering issue as well.

Looks good to me


Missing scrollbars on Firefox for non supported websites

At least in Ubuntu, the Firefox version is missing scrollbars for non supported websites. In example, if you go to a random website like https://alphabetizer.org/, in Chrome you have a normal window with scrollbars as expected which you can use to move around inside the window:

On the other hand in Firefox the scrolbars do not show, leaving the user stuck without any chance of moving around and not even the cursor keys work:

pt
Resumo em português, estão a faltar as barras de deslocação no Firefox em sites sem players ou sem players suportados na extensão, ficamos agarrados à parte superior do ecrã e dali não dá para sair.
Parabéns pela excelente extensão que é super útil!
Abraço

Hi, @pemartins1. You're right. It seems that there's a bug in Firefox. :cry:
I'll report it to Bugzilla as soon as possible.

It seems it was fixed:


error when players die?

Well what error comes from C_Fire_Plug, i guess you need to contact them to get a fix.


Fix the multi-instance overlap in TRT backend

Please review only latest commit.
cb020088fafe6e250c5faa563be524ddcae0b773
The first commit is part of the PR #20.

Before

After

Four instances are properly being executed.

The change looks good, I think round-robin over the semaphore_list_ in line 1643 is okay, I don't think it is possible that the context will be completed out of order.

Exactly! The ops are enqueued to the same stream!


Documentation_ Design with React Magma button> "Not Found" error message is appearing upon launching

Describe the bug
"Not Found" error message is appearing upon launching the button "Design with React Magma".
To Reproduce
Steps to reproduce the behavior:

Go to https://react-magma.cengage.com/version/2.5.7/
Click on "Design with React Magma" button
Verify the message

Expected behavior
Appropriate page should appear when clicks on button "Design with React Magma"
Screenshots
https://screencast-o-matic.com/watch/c3nQQlVDNgt
Desktop :

OS: [Win 10]
Browser [Chrome]
Version [Chrome version: Version 98.0.4758.81 (Official Build) (64-bit)]

The issue is fixed.
See Screen-cast : https://www.screenpresso.com/=Tv8Kc
Hence, Closing the ticket.
Thanks!


Reg\Operation - Opt-ins with existing BORO IDs are not shown Opt-In application

Dependencies

Blocked by
Blocking

Description:
Some opt-in operations already received a BORO ID, so when they come back in registration 2 to register their operation, they should NOT be shown the opt-in application form since they already filled it out before. Thread from SME channel for context.
Acceptance Criteria:
Given that my operation is an Opt-in with a BORO ID
When I am registering this operation
Then I am not shown the opt-in application
Development Checklist:

[ ] In bciers/apps/registration/app/components/operations/OperationRegistrationPage.tsx, in the if statement that determines whether or not show the opt-in page, check for BORO id. BORO id should already be available in this component in as part of operationData as 'bc_obps_regulated_operation'
[ ] vitests
[ ] Checklist item
[ ] Meets the DOD

Definition of Ready (Note: If any of these points are not applicable, mark N/A)

[ ] User story is included
[ ] User role and type are identified
[ ] Acceptance criteria are included
[ ] Wireframes are included (if required)
[ ] Design / Solution is accepted by Product Owner
[ ] Dependencies are identified (technical, business, regulatory/policy)
[ ] Story has been estimated (under 13 pts)

·Definition of Done (Note: If any of these points are not applicable, mark N/A)

[ ] Acceptance criteria are tested by the CI pipeline
[ ] UI meets accessibility requirements
[ ] Configuration changes are documented, documentation and designs are updated
[ ] Passes code peer-review
[ ] Passes QA of Acceptance Criteria with verification in Dev and Test
[ ] Ticket is ready to be merged to main branch
[ ] Can be demoed in Sprint Review
[ ] Bugs or future work cards are identified and created
[ ] Reviewed and approved by Product Owner

Notes:

Refinement Notes:

@andrea-williams to add Dev checklist

@zoeyli-46  would I be correct in assuming that the "Opted in Operation" section of the Operation form in view mode (https://www.figma.com/design/LsDmLDCdnJqI8UahyqvOD8/BCIERS-Designs?node-id=18025-1179&m=dev&t=HNQ6XaR8QUjb2CZ2-1 ) should not appear in this case? What about for Edit mode of the form?

Based on this thread, because Opted-in operations from registration 1 submitted the application manually outside of BCIERS, their application data will not be showing up in BCIERS. Therefore there will not be an opted in operation section of the operation form for these operations.
For future consideration: would the business area want the operations to have the functionality to add their opt-in application data in the Operation Information form in edit mode? So, they wont see the form in Register Operation BUT when they go to edit their Operation Information form then they could see a blank opt-in form that they could fill in? is this confusing for the user because they don't understand why it would be empty? is this difficult to implement anyways?

controversial opinion: would it be acceptable to have previously opted-in operators fill out the opt-in form again (this time within BCIERS)? It's just a few yes/no questions, it shouldn't be a lot of time or effort for them to fill it out again.

Refinement Notes:

Potential discussion later during Reg. Collab (Nov. 5)

Just looping back on this and re-adding the backlog refinement tag. It was discussed at Reg Collab on Nov 5 and BA and DST came to the following decision:

for now we will plan to require already designated opt-ins to complete the opt-in form again (unless we have time to go back and fix it later).
It was agreed that we would add additional communications to explain how this works before we launch.

cc: @zoeyli-46 @andrea-williams


Fixed #26 : Updated the "auto-label" workflow

Fixed #26
Description
Update the auto-label issues to include gssoc-ext and hacktoberfest-accepted
note -to auto label the issues "level1"and level2" etc, github-bot has to be context aware which is not possible . However i have included code for level1 if there is any doc or readme.md mentioned in issue

Hey @Devanik21 Please add the correct labels to this


Don't wait three seconds between re-tries for failed networking

Decreases the time before attempting another reconnect, if they're failing then they're probably taking less than a second to show, plus who waits for 3 seconds for anything nowadays?

It'll need a rebase

rebased :+1:

Looks like a backlog on Circle.


Feature Request: Add the skia particles module

Would be nice to have access to this as well.

The only objection I have to this is that potentially it might inflate binary size too much. Can you run a comparison?


App touch broken after oauth

the oauth works fine, it returns the user but sometimes after the in app browser close the app stop responding to screen touch, i mean, it's imposible to touch any element again, then i must close the app and reopen it ...
my code is
private oauth: OauthCordova = new OauthCordova();

  private googleProvider: Google = new Google({
    clientId: 'xxxx',
    appScope: ['email']
  })

this.oauth.logInVia(this.googleProvider).then(success => {
      if(success['access_token']){
           goHome(success)
      }
    }, error => {
      console.log("ERROR: Google", error);
    });

Your system information:

Cordova CLI: 7.0.0
Ionic Framework Version: 2.1.0
Ionic CLI Version: 2.2.1
Ionic App Lib Version: 2.2.0
Ionic App Scripts Version: 1.1.3
ios-deploy version: Not installed
ios-sim version: 4.1.1
OS: macOS Sierra
Node Version: v6.9.2
Xcode version: Xcode 8.3.2 Build version 8E2002

This one is new to me.
Does this happen on Android, iOS, or both? Are you attempting to use Ionic Serve or anything similar, because that won't work correctly.
On a side note, be aware that Google is starting to block requests from the InAppBrowser in favor of their native SDKs. Even if it works for you now, it won't In the future.
Best,

It's happening on iOS 10, i'm using on device (iphone 6s), but I thinks I solved this problem, I remove the inappbrowser plugin version 1.7.0 and installed the inappbrowser 1.5.0 and the problem stops, but it was very strange because it only happens after a successfully oauth.


os init_state: add new state OSINIT_IDLELOOP

Summary
os init_state: add new state OSINIT_IDLELOOP
This is for distinguish we are in init idle or idle loop.
Use for assertion for sem_trywait & sem_wait
In the previous PR:
https://github.com/apache/incubator-nuttx/pull/5577
There is a check error:
DEBUGASSERT(OSINIT_IDLELOOP() && !sched_idletask());
should be:
DEBUGASSERT(!OSINIT_IDLELOOP() || !sched_idletask());
And the last PR regression caused by lack of testing.
This time do the fully test.
Impact
idle take sem
Testing
Test in maix-bit:kostest, VELA

@masayuki2009 could you try this one?

@GUIDINGLI
Hmm, stm32f4discovery:kostest (DEBUG build) failed with assertion.
I've never seen this assertion before.
user_main: semaphore test
sem_test: Initializing semaphore to 0
sem_test: Starting waiter thread 1
sem_test: Set thread 1 priority to 191
waiter_func: Thread 1 Started
sem_test: Starting waiter thread 2
waiter_func: Thread 1 initial semaphore value = 0
sem_test: Set thread 2 priority to 128
waiter_func: Thread 1 waiting on semaphore
waiter_func: Thread 2 Started
sem_test: Starting poster thread 3
waiter_func: Thread 2 initial semaphore value = -1
sem_test: Set thread 3 priority to 64
waiter_func: Thread 2 waiting on semaphore
poster_func: Thread 3 started
poster_func: Thread 3 semaphore value = -2
poster_func: Thread 3 posting semaphore
waiter_func: Thread 1 awakened
poster_func: Thread 3 new semaphore value = -1
waiter_func: Thread 1 new semaphore value = -1
pup_assert: Assertion failed at file:armv7-m/arm_svcall.c line: 429 task: pt-0x8022711
arm_registerdump: R0: 20000004 R1: 00000000 R2: 40004400  R3: 00000000
arm_registerdump: R4: 20000004 R5: 00000031 R6: 00000000  FP: 00000068
arm_registerdump: R8: 00000001 SB: 2000000a SL: 00000000 R11: 00000001
arm_registerdump: IP: 08003eb7 SP: 20012358 LR: 08005353  PC: 0800ad9a
arm_registerdump: xPSR: 61000000 PRIMASK: 00000000 CONTROL: 00000000
arm_registerdump: EXC_RETURN: fffffff9
arm_dump_stack: User Stack:
arm_dump_stack: sp:     200122b0
arm_dump_stack:   base: 20011cf8
arm_dump_stack:   size: 00000800
arm_stackdump: 200122a0: 20011cf8 00000800 200122b0 08004d11 00000000 00000000 0800ad9a 00000001
arm_stackdump: 200122c0: 2001230c 1ffffffc 200003e4 00000068 00000001 08003ec7 00000001 08000c31
arm_stackdump: 200122e0: 00000000 200003e4 0000000b 0800203b 00000000 080008ad 2001230c 00000031
arm_stackdump: 20012300: 00000000 08000845 200022d0 20012358 00000000 20000004 00000031 00000000
arm_stackdump: 20012320: 00000068 00000001 2000000a 00000000 00000001 fffffff9 20000004 00000000
arm_stackdump: 20012340: 40004400 00000000 08003eb7 08005353 0800ad9a 61000000 00000001 00000000
arm_stackdump: 20012360: 20000004 0000001f 20010bab 00000001 00000011 20000010 00000068 0800b11b
arm_stackdump: 20012380: 0800b07f 20010b9c 0000001f 0000001f 00000001 200124b8 00000000 200124b8
arm_stackdump: 200123a0: 000000ed 08007073 00000001 200020f8 0000001f 00000000 00000001 08007083
arm_stackdump: 200123c0: 00000000 08000c0b 00000000 00000001 0000001f 08025e6d 00000014 20010b9c
arm_stackdump: 200123e0: 20010b7c 08025e6d 80000000 0000000a 20010b7c 00000000 00000000 08026929
arm_stackdump: 20012400: 0000000a 0a010b7c 080260ed 2001247c 0000000a 08026113 0000000a 2001247c
arm_stackdump: 20012420: 0000001f 0802640f 0802a85f 00000001 20002090 00000000 00000032 00000000
arm_stackdump: 20012440: 00000000 fffffffd 00000000 20010b84 00000000 20010b7c 0802a83f 200124b4
arm_stackdump: 20012460: 20002090 00000000 00000000 00000000 00000000 08025ef7 00000000 080260ed
arm_stackdump: 20012480: 20010b10 080260cd 0000001e 20010b7c 0802a83f 08025835 20002080 08025c1d
arm_stackdump: 200124a0: 0802a83f 200124b4 00000002 08022751 0802a83f 00000002 00000000 20002368
arm_stackdump: 200124c0: 00000002 ffffffff 00000000 08025847 00000002 08008a6d 00000080 08008a6d
arm_showtasks:    PID    PRI     STACK   COMMAND
arm_dump_task:      0      0      1000   Idle Task
arm_dump_task:      2    100      2024   ostest_main
arm_dump_task:      3    100      1992   ostest
arm_dump_task:     29    128      2048   pt-0x8022711
arm_dump_task:     30     64      2048   pt-0x8022669

@masayuki2009
Can you share the detail cmds ?

Can you revert this patch, and have a try ?
commit e0fabbfdd6a55510eae265472fd992aba1c0b588
Author: chao.an<EMAIL_ADDRESS>Date:   Tue Feb 22 15:25:56 2022 +0800
arch/arm: replace SYS_syscall_return hardcode from syscall

Signed-off-by: chao.an<EMAIL_ADDRESS>
diff --git a/arch/arm/src/armv7-m/arm_svcall.c b/arch/arm/src/armv7-m/arm_svcall.c
index 6119ee6297..1330dc3a81 100644
--- a/arch/arm/src/armv7-m/arm_svcall.c
+++ b/arch/arm/src/armv7-m/arm_svcall.c
@@ -103,8 +103,9 @@ static void dispatch_syscall(void)
" ldr r2, [sp, #16]\n"         /* Restore (orig_SP - new_SP) value /
" add sp, sp, r2\n"            / Restore SP /
" mov r2, r0\n"                / R2=Save return value in R2 */

 " mov r0, #3\n"                /* R0=SYS_syscall_return */

 " svc %0\n"::"i"(SYS_syscall)  /* Return from the SYSCALL */

 " mov r0, %0\n"                /* R0=SYS_syscall_return */

 " svc %1\n"::"i"(SYS_syscall_return),

              "i"(SYS_syscall)  /* Return from the SYSCALL */

);
}
#endif

Can you share the detail cmds ?

@GUIDINGLI
$ st-flash --format ihex write ./nuttx_user.hex
$ st-flash --format ihex write ./nuttx.hex
$ st-flash reset

Can you share the detail cmds ?

@GUIDINGLI
$ st-flash --format ihex write ./nuttx_user.hex
$ st-flash --format ihex write ./nuttx.hex
$ st-flash reset

These cmds for real hardware board ?
Can this run on qemu ?

@GUIDINGLI
BTW, do you have the stm32f4discovery board?

@GUIDINGLI

These cmds for real hardware board ?

Yes.

Can this run on qemu ?

Unfortunately, no.

Then, without this patch, the ostest can run pass ?
Also, need open CONFIG_DEBUG_ASSERTIONS=y

Then, without this patch, the ostest can run pass ?
Also, need open CONFIG_DEBUG_ASSERTIONS=y

@GUIDINGLI
According to the latest upstream test logs, it passed with CONFIG_DEBUG_ASSERTIONS=y
However, I still suspect that my board has some issues.
I'm now preparing lm3s6965-ek:kostest with QEMU, so please wait.

I'm now preparing lm3s6965-ek:kostest with QEMU, so please wait.

@GUIDINGLI
See https://github.com/apache/incubator-nuttx/pull/5595
I confirmed that this PR works with the above lm3s6965-ek:qemu-kostest.
So let me merge this PR.

@GUIDINGLI
I found a new issue with sabre-6quad:netknsh which is not merged to the upstream.
Actually, if I run the getprime command, DEBUGASSERT happens when it exits.
The call stack is
(gdb) where
#0  up_assert (filename=0x10856468 "semaphore/sem_wait.c", lineno=80) at common/arm_assert.c:478
#1  0x1080d38c in _assert (filename=0x10856468 "semaphore/sem_wait.c", linenum=80) at assert/lib_assert.c:36
#2  0x10804354 in nxsem_wait (sem=0x1085ab34 <g_putc_lock>) at semaphore/sem_wait.c:80
#3  0x10800e30 in up_putc (ch=91) at chip/imx_serial.c:1135
#4  0x10849344 in syslog_default_putc (channel=0x1085ac20 <g_default_channel>, ch=91) at syslog/syslog_channel.c:177
#5  0x10848f70 in syslog_putc (ch=91) at syslog/syslog_putc.c:93
#6  0x10848e18 in syslogstream_putc (this=0x1086b9f4, ch=91) at syslog/syslog_stream.c:157
#7  0x1080f780 in vsprintf_internal (stream=0x1086b9f4, arglist=0x0, numargs=0, fmt=0x1085a101 "%5jd.%06ld] ", ap=...) at stdio/lib_libvsprintf.c:236
#8  0x10810da8 in lib_vsprintf (stream=0x1086b9f4, fmt=0x1085a100 "[%5jd.%06ld] ", ap=...) at stdio/lib_libvsprintf.c:1373
#9  0x1084a590 in lib_sprintf (obj=0x1086b9f4, fmt=0x1085a100 "[%5jd.%06ld] ") at stdio/lib_libsprintf.c:45
#10 0x10848db8 in nx_vsyslog (priority=6, fmt=0x108577ac "%s: tcb=%p\n", ap=0x1086ba24) at syslog/vsyslog.c:136
#11 0x10813500 in vsyslog (priority=6, fmt=0x108577ac "%s: tcb=%p\n", ap=...) at syslog/lib_syslog.c:68
#12 0x10813538 in syslog (priority=6, fmt=0x108577ac "%s: tcb=%p\n") at syslog/lib_syslog.c:100
#13 0x10819b40 in up_addrenv_kstackfree (tcb=0x10865c40) at armv7-a/arm_addrenv_kstack.c:167
#14 0x108073e4 in nxsched_release_tcb (tcb=0x10865c40, ttype=1 '\001') at sched/sched_releasetcb.c:159
#15 0x10846cfc in nxtask_terminate (pid=6, nonblocking=1 '\001') at task/task_terminate.c:184
#16 0x108465fc in nxtask_exit () at task/task_exit.c:168
#17 0x10816cd8 in up_exit (status=0) at common/arm_exit.c:125
#18 0x10805ffc in _exit (status=0) at task/exit.c:56
#19 0x10842384 in nx_pthread_exit (exit_value=0x0) at pthread/pthread_exit.c:112
#20 0x1080bec0 in STUB_nx_pthread_exit (nbr=107, parm1=0) at stubs/STUB_nx_pthread_exit.c:11
#21 0x10801f4c in dispatch_syscall () at armv7-a/arm_syscall.c:86

And
(gdb) up
#1  0x1080d38c in _assert (filename=0x10856468 "semaphore/sem_wait.c", linenum=80) at assert/lib_assert.c:36
36        up_assert(filename, linenum);
(gdb) up
#2  0x10804354 in nxsem_wait (sem=0x1085ab3c <g_putc_lock>) at semaphore/sem_wait.c:80
80        DEBUGASSERT(!OSINIT_IDLELOOP() || !sched_idletask());
(gdb) p *rtcb
$1 = {flink = 0x0, blink = 0x0, group = 0x10862b10, pid = 0, sched_priority = 0 '\000', init_priority = 0 '\000', start = 0x1080336c <nx_start>, entry = {pthread = 0x1080336c <nx_start>, main = 0x1080336c <nx_start>}, task_state = 2 '\002', flags = 6, lockcount = 1, errcode = 0, timeslice = 0, waitdog = {next = 0x0, func = 0x0, lag = 0, arg = 0}, adj_stack_size = 2024, stack_alloc_ptr = 0x1086115c, stack_base_ptr = 0x10861174, waitsem = 0x0, sigprocmask = 0, sigwaitmask = 0, sigpendactionq = {head = 0x0, tail = 0x0}, sigpostedq = {head = 0x0, tail = 0x0}, sigunbinfo = {si_signo = 0 '\000', si_code = 0 '\000', si_errno = 0 '\000', si_value = {sival_int = 0, sival_ptr = 0x0}}, msgwaitq = 0x0, mhead = 0x0, xcp = {sigdeliver = 0x0, saved_pc = 0, saved_cpsr = 0, sigreturn = 0, regs = {0, 277200652, 277230636, 0, 0, 9682944, 0, 0, 0, 0, 0, 277223732, 277223352, 277223732, 276839228, 276923088,<PHONE_NUMBER>, 0 <repeats 33 times>}, nsyscalls = 0 '\000', syscall = {{cpsr = 0, sysreturn = 0}, {cpsr = 0, sysreturn = 0}}, ustkptr = 0x0, kstack = 0x0, kstkptr = 0x0}, name = "Idle Task", '\000' <repeats 22 times>}

It seems that syslog flushes the internal buffers from the Idle task.

It seems that syslog flushes the internal buffers from the Idle task.

@GUIDINGLI
Actual code is inside up_addrenv_kstackfre.
So do you mean that this PR does not permit such a log?
int up_addrenv_kstackfree(FAR struct tcb_s *tcb)
{
=>binfo("tcb=%p\n", tcb);
  DEBUGASSERT(tcb);

So do you mean that this PR does not permit such a debug log?
If so, this would be a big restriction for debugging.

@GUIDINGLI @xiaoxiang781216
I found that up_putc() in imx_serial.c uses sem_wait().
I fixed the issue in https://github.com/apache/incubator-nuttx/pull/5633

It's good to know that this patch could catch the potential issue.


Update meta.yaml for version 1.0

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

It looks like the tests are failing because they require a c++ compiler. Could you add that to the test dependencies? I think you can do that by adding a line
- {{ compiler('cxx') }}

See here for more information.


Fix empty shader resource loading

Regression from https://github.com/godotengine/godot/pull/80705. String.parse_utf8() returns an error when given string size of 0 and null, so we have to manually check this first. Otherwise, loading a completely empty .gdshader or .gdshaderinc file will fail. The workaround is easy, just add a space or newline to the file using an external text editor and it will load normally again.

Thanks!

Cherry-picked for 4.1.2.


Change repo naming and description from SIG to task force

@andrew @jessicaschilling does either of you have the original image file (editable) for the fancy repo title in the README?

Yep, I'll send it under separate cover.

Done! (Also added link to Zenhub task board)


suggestion

would you saparate the lua binding from your project, into 2 subproject. Then the  architecture will be more clear.
And many people want just use the pcl in Lua without torch.
thanks.

@lanybass Currently our PCL wrapper relies heavily on the torch-tensor library, e.g. for directly accessing the point cloud memory. I understand that there might be interest for a lua-only PCL wrapper but the xamla/torch-pcl project was specifically planned and developed with torch as its backend.


Rationale for direction "in" meaning "no modifications allowed within the control/action/function/etc. body"?

My first quick guess would be "it makes it trivial for an optimizing compiler to know that it need not make a copy of the value, because it cannot be modified".
There is the workaround that a P4 developer can use to make modifications to a local copy where they declare a local variable and explicitly copy the value of the "in" parameter into that local variable, then modify the local variable.  One could argue that this makes the introduction of a local copy explicit as a cost that is visible to the P4 developer.
Is there any other rationale not described above?
One perhaps unintended consequence of direction in behavior in the language is that some architectures like TNA and PSA have used direction inout for some parameters, e.g. the type H struct containing headers, in their deparser controls, NOT because the headers are "passed forward" in the architecture to anywhere else after deparsing is complete, but because those architectures chose that to enable calculating IP checksums and modifying those checksum fields in things like IPv4/UDP/TCP headers within the deparser control.
One could argue that perhaps those architectures should instead use direction in for that struct of headers, and require the P4 developer to make a local copy of any headers they want to modify, and only emit the locally modified copy, not the one in the struct of headers that is an in parameter.
Aside: I know that there was mentioned once or twice the proposal for introducing a new direction that was like in, except that local modifications would be explicitly allowed, but did not cause the copy-out behavior of direction inout.  I am not proposing that with this question (but have no objections if people think that is a good idea to introduce such a thing -- it does not seem like a high priority thing to me).

Yes, I think this is the main reason: to enable the compiler to save a copy without doing a complicated analysis.

In the interest of tidying up the set of active issues on the P4 specification repository, I'm marking this as "stalled" and closing it. Of course, we can always re-open it in the future if there is interest in resurrecting it.


Rendering a hashref

I would like to be able to render an arbitrary hashref, without worrying about the data type / blessed class.

This is already do-able!


Warn users about suspicious filenames

'sample_{id}.txt' etc are valid filenames (at least under linux/mac) but in practice they are almost certainly user mistakes. It might make sense for SoS to warn users about suspicious filenames (e.g. with braces, dollars) in _input, _output etc.

There are two concerns:

Performance. The best place to check this is in the constructor of file_target, but a lot of tests would be performed for this common target type.

Repeated warning. There could be many many repeated warning messages if the same warning happens in a loop.

How to suppress the warning if path with { } is actually what users want.


Update README.md

Minor change to sentence structure.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 98.78%. Comparing base (901a78a) to head (f93fdb1).
Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #157   +/-   ##
=======================================
  Coverage   98.78%   98.78%
=======================================
  Files          45       45
  Lines        1893     1893
=======================================
  Hits         1870     1870
  Misses         23       23

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

@galenseilis Thank you for the suggestion.


Re-enable compiler checks

Add a -nostdlib specifically for the check to ensure that it builds successfully. The -nostdlib isn't needed normally, because linking against the pico SDK will add in definitions for the previously-missing function.
However, when CMake checks to see what features the compiler supports, it compiles a custom program with nothing but the implicit dependencies, like libc. Previously, this was worked around by disabling feature detection by setting CMAKE_C_COMPILER_FORCED=TRUE.
I think the best way to fix this is to unconditionally link all programs against pico_standard_link in the toolchain. However, this can't be done without precompiling the library (I think--my CMake-fu is quite weak). And we don't actually need an executable that can be installed for compiler feature detection.
I've tested this on Arch Linux with arm-none-eabi-gcc-12.2.0. I haven't tested on other systems, but this doesn't get super deep into platform-specific stuff.
Fixes #1096

moving to 1.5.0 as this requires quite a bit of testing on different platforms

What's the ideal testing matrix you'd like to see here?
On Thu, Nov 24, 2022, 10:04 Graham Sanderson @.***>
wrote:

moving to 1.5.0 as this requires quite a bit of testing on different
platforms
—
Reply to this email directly, view it on GitHub
https://github.com/raspberrypi/pico-sdk/pull/1097#issuecomment-1326566326,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABHY2HPYVHNUJRT7RYSYY5LWJ57WPANCNFSM6AAAAAAR4CQEGI
.
You are receiving this because you authored the thread.Message ID:
@.***>

Yeah probably want to test on

macOS
Linux
Windows (regular and cygwin)
Pi
with whatever versions of cmake come standard (and the latest on some platform)

I mean we do test the platforms b4 the release, but in this case, yes, testing this up front to make sure there aren't any weird issues would be helpful (as 1.4.1 is really just going to be a bug fix release)

I spent some time trying to test on Windows, and failing

Can you please post your full console output @peterharperuk ?

To be clear - I have some config problem that's unrelated to this change. I don't normally develop on Windows.
`C:\Users\peter\source\pico-examples\build\hello_world\serial>nmake VERBOSE=1
Microsoft (R) Program Maintenance Utility Version 14.34.31937.0
Copyright (C) Microsoft Corporation.  All rights reserved.
    cd C:\Users\peter\source\pico-examples\build
    "C:\Program Files\CMake\bin\cmake.exe" -SC:\Users\peter\source\pico-examples -BC:\Users\peter\source\pico-examples\build --check-build-system CMakeFiles\Makefile.cmake 0
    cd C:\Users\peter\source\pico-examples\build\hello_world\serial
    cd C:\Users\peter\source\pico-examples\build
    "C:\Program Files\CMake\bin\cmake.exe" -E cmake_progress_start C:\Users\peter\source\pico-examples\build\CMakeFiles C:\Users\peter\source\pico-examples\build\hello_world\serial\\CMakeFiles\progress.marks
    "C:\Program Files (x86)\Microsoft Visual Studio\2022\BuildTools\VC\Tools\MSVC\14.34.31933\bin\Hostx64\x64\nmake.exe"  -f CMakeFiles\Makefile2 /nologo -                   hello_world\serial\all
    "C:\Program Files (x86)\Microsoft Visual Studio\2022\BuildTools\VC\Tools\MSVC\14.34.31933\bin\Hostx64\x64\nmake.exe"  -f pico-sdk\src\rp2_common\boot_stage2\CMakeFiles\bs2_default.dir\build.make /nologo -L                  pico-sdk\src\rp2_common\boot_stage2\CMakeFiles\bs2_default.dir\depend
    "C:\Program Files\CMake\bin\cmake.exe" -E cmake_depends "NMake Makefiles" C:\Users\peter\source\pico-examples C:\Users\peter\source\pico-sdk\src\rp2_common\boot_stage2 C:\Users\peter\source\pico-examples\build C:\Users\peter\source\pico-examples\build\pico-sdk\src\rp2_common\boot_stage2 C:\Users\peter\source\pico-examples\build\pico-sdk\src\rp2_common\boot_stage2\CMakeFiles\bs2_default.dir\DependInfo.cmake --color=
    "C:\Program Files (x86)\Microsoft Visual Studio\2022\BuildTools\VC\Tools\MSVC\14.34.31933\bin\Hostx64\x64\nmake.exe"  -f pico-sdk\src\rp2_common\boot_stage2\CMakeFiles\bs2_default.dir\build.make /nologo -L                  pico-sdk\src\rp2_common\boot_stage2\CMakeFiles\bs2_default.dir\build

Built target bs2_default
"C:\Program Files (x86)\Microsoft Visual Studio\2022\BuildTools\VC\Tools\MSVC\14.34.31933\bin\Hostx64\x64\nmake.exe"  -f pico-sdk\src\rp2_common\boot_stage2\CMakeFiles\bs2_default_padded_checksummed_asm.dir\build.make /nologo -L                  pico-sdk\src\rp2_common\boot_stage2\CMakeFiles\bs2_default_padded_checksummed_asm.dir\depend
"C:\Program Files\CMake\bin\cmake.exe" -E cmake_depends "NMake Makefiles" C:\Users\peter\source\pico-examples C:\Users\peter\source\pico-sdk\src\rp2_common\boot_stage2 C:\Users\peter\source\pico-examples\build C:\Users\peter\source\pico-examples\build\pico-sdk\src\rp2_common\boot_stage2 C:\Users\peter\source\pico-examples\build\pico-sdk\src\rp2_common\boot_stage2\CMakeFiles\bs2_default_padded_checksummed_asm.dir\DependInfo.cmake --color=
"C:\Program Files (x86)\Microsoft Visual Studio\2022\BuildTools\VC\Tools\MSVC\14.34.31933\bin\Hostx64\x64\nmake.exe"  -f pico-sdk\src\rp2_common\boot_stage2\CMakeFiles\bs2_default_padded_checksummed_asm.dir\build.make /nologo -L                  pico-sdk\src\rp2_common\boot_stage2\CMakeFiles\bs2_default_padded_checksummed_asm.dir\build
cd C:\Users\peter\source\pico-examples\build\pico-sdk\src\rp2_common\boot_stage2
cd C:\Users\peter\source\pico-examples\build
Built target bs2_default_padded_checksummed_asm
"C:\Program Files (x86)\Microsoft Visual Studio\2022\BuildTools\VC\Tools\MSVC\14.34.31933\bin\Hostx64\x64\nmake.exe"  -f blink\CMakeFiles\ELF2UF2Build.dir\build.make /nologo -L                  blink\CMakeFiles\ELF2UF2Build.dir\depend
"C:\Program Files\CMake\bin\cmake.exe" -E cmake_depends "NMake Makefiles" C:\Users\peter\source\pico-examples C:\Users\peter\source\pico-examples\blink C:\Users\peter\source\pico-examples\build C:\Users\peter\source\pico-examples\build\blink C:\Users\peter\source\pico-examples\build\blink\CMakeFiles\ELF2UF2Build.dir\DependInfo.cmake --color=
"C:\Program Files (x86)\Microsoft Visual Studio\2022\BuildTools\VC\Tools\MSVC\14.34.31933\bin\Hostx64\x64\nmake.exe"  -f blink\CMakeFiles\ELF2UF2Build.dir\build.make /nologo -L                  blink\CMakeFiles\ELF2UF2Build.dir\build
Performing configure step for 'ELF2UF2Build'
cd C:\Users\peter\source\pico-examples\build\elf2uf2
echo >nul && "C:\Program Files\CMake\bin\cmake.exe" "-GNMake Makefiles" C:/Users/peter/source/pico-sdk/tools/elf2uf2
Re-run cmake no build system arguments
-- The C compiler identification is MSVC 19.34.31937.0
-- The CXX compiler identification is MSVC 19.34.31937.0
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - failed
-- Check for working C compiler: C:/Program Files (x86)/Microsoft Visual Studio/2022/BuildTools/VC/Tools/MSVC/14.34.31933/bin/Hostx64/x64/cl.exe
-- Check for working C compiler: C:/Program Files (x86)/Microsoft Visual Studio/2022/BuildTools/VC/Tools/MSVC/14.34.31933/bin/Hostx64/x64/cl.exe - broken
CMake Error at C:/Program Files/CMake/share/cmake-3.25/Modules/CMakeTestCCompiler.cmake:70 (message):
The C compiler
"C:/Program Files (x86)/Microsoft Visual Studio/2022/BuildTools/VC/Tools/MSVC/14.34.31933/bin/Hostx64/x64/cl.exe"

is not able to compile a simple test program.
It fails with the following output:
Change Dir: C:/Users/peter/source/pico-examples/build/elf2uf2/CMakeFiles/CMakeScratch/TryCompile-oq2ctk

Run Build Command(s):nmake -f Makefile /nologo cmTC_059ee\fast &&   "C:\Program Files (x86)\Microsoft Visual Studio\2022\BuildTools\VC\Tools\MSVC\14.34.31933\bin\Hostx64\x64\nmake.exe"  -f CMakeFiles\cmTC_059ee.dir\build.make /nologo -L                  CMakeFiles\cmTC_059ee.dir\build
Building C object CMakeFiles/cmTC_059ee.dir/testCCompiler.c.obj
    "C:\Program Files\CMake\bin\cmake.exe" -E cmake_cl_compile_depends --dep-file=CMakeFiles\cmTC_059ee.dir\testCCompiler.c.obj.d --working-dir=C:\Users\peter\source\pico-examples\build\elf2uf2\CMakeFiles\CMakeScratch\TryCompile-oq2ctk --filter-prefix="Note: including file: " -- C:\PROGRA~2\MICROS~2\2022\BUILDT~1\VC\Tools\MSVC\1434~1.319\bin\Hostx64\x64\cl.exe @C:\Users\peter\AppData\Local\Temp\nmE337.tmp
testCCompiler.c
Linking C executable cmTC_059ee.exe
    "C:\Program Files\CMake\bin\cmake.exe" -E vs_link_exe --intdir=CMakeFiles\cmTC_059ee.dir --rc=rc --mt=CMAKE_MT-NOTFOUND --manifests -- C:\PROGRA~2\MICROS~2\2022\BUILDT~1\VC\Tools\MSVC\1434~1.319\bin\Hostx64\x64\link.exe /nologo @CMakeFiles\cmTC_059ee.dir\objects1 @C:\Users\peter\AppData\Local\Temp\nmE376.tmp
Visual Studio Incremental Link with embedded manifests
Create CMakeFiles\cmTC_059ee.dir/manifest.rc
Create empty: CMakeFiles\cmTC_059ee.dir/embed.manifest
RC Pass 1:
rc /fo CMakeFiles\cmTC_059ee.dir/manifest.res CMakeFiles\cmTC_059ee.dir/manifest.rc
RC Pass 1: command "rc /fo CMakeFiles\cmTC_059ee.dir/manifest.res CMakeFiles\cmTC_059ee.dir/manifest.rc" failed (exit code 0) with the following output:
The system cannot find the file specifiedNMAKE : fatal error U1077: '"C:\Program Files\CMake\bin\cmake.exe"' : return code '0xffffffff'
Stop.
NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual Studio\2022\BuildTools\VC\Tools\MSVC\14.34.31933\bin\Hostx64\x64\nmake.exe"' : return code '0x2'
Stop.

CMake will not be able to correctly generate this project.
Call Stack (most recent call first):
CMakeLists.txt:2 (project)
-- Configuring incomplete, errors occurred!
See also "C:/Users/peter/source/pico-examples/build/elf2uf2/CMakeFiles/CMakeOutput.log".
See also "C:/Users/peter/source/pico-examples/build/elf2uf2/CMakeFiles/CMakeError.log".
NMAKE : fatal error U1077: 'echo' : return code '0x1'
Stop.
NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual Studio\2022\BuildTools\VC\Tools\MSVC\14.34.31933\bin\Hostx64\x64\nmake.exe"' : return code '0x2'
Stop.
NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual Studio\2022\BuildTools\VC\Tools\MSVC\14.34.31933\bin\Hostx64\x64\nmake.exe"' : return code '0x2'
Stop.
`

Ah that makes sense. I don't develop on windows either but it looks like it's trying to compile with a Microsoft toolchain against your native environment rather than a gcc targeting ARM.
No suggestions here on how to fix it, but I appreciate you taking a look when I haven't had a chance to

I've added some basic automated builds on Windows in #1209, see also #1208.
Not sure if that's something y'all want, but if it is, it could inspire more confidence in that this MR won't break anything.

I tested this on Windows with NMake / Ninja and it was happy too, so looks good to me
Thanks

I'm having an issue caused by this change, but I can't figure out exactly why: my project links to an interface library and it uses find_package to find the xxxTargets.cmake to load the library target. Now this seems to work until this commit is introduced in the pico SDK. With these changes the CMake configuration fails because it does not accept the xxxTargets.cmake file for the library, logging this error:
the following configuration files were considered but not accepted:

    /usr/local/share/<library_name>/cmake/<library_name>Config.cmake, version: 0.4.0 (64bit)

That (64bit) is suspicious but I am not sure why these changes would impact how libraries are found. Does anybody have a clue?


getClusterTopology error

Please answer these questions before submitting your issue.

Why do you submit this issue?
[ ] Question or discussion
[ ] Bug
[ ] Requirement
[ ] Feature or performance improvement

Question

What do you want to know?

Bug

Which version of SkyWalking, OS and JRE?
skywalking 5.0.0.RC   OS: centos6.9

Which company or project?

What happen?
please see the attachment. UI error: Cannot return null for non-nullable type: 'String' within parent 'Call' (/getClusterTopology/calls[147]/callType)

Requirement or improvement

Please describe about your requirements or improvement suggestions.

You need to provide the UI request and response for this particular  HTTP request.

hi sheng, i didn't save the error request and response. from the code it seems call.setCallType(nodeCompMap.get(referenceMetric.getTarget())); the calltype is null sometime in ClusterTopologyService.getClusterTopology. I just found our es run into some problems before. maybe that's because some docs are missing during the es problem. not sure yet. i will update it if issue persist.

Ok. Reopen this when you have problem.


[FR]: Support App Privacy Manifest

Description
With the introduction of App Privacy manifests we're forced to declare which APIs are used, Domains where user tracking can be performed and the purpose per SDK.
https://developer.apple.com/videos/play/wwdc2023/10060/
Additionally any Firebase SDK that contains an app privacy manifest must be signed.
We would like to adopt this change as otherwise it should be added per app, and as we don't know which APIs/domains/tracking logic you're currently using we can't fulfil the privacy manifest properly
Thanks!
API Proposal
No response
Firebase Product(s)
Analytics, Remote Config

Thanks for the request. We're actively investigating the implications of the WWDC 2023 Privacy Announcements.
In the meantime, https://firebase.google.com/docs/ios/app-store-data-collection is a reference for filling out the privacy manifest.

Just as a help, if you decide it is necessary to include the manifest as part of your libraries, you'll also need to sign the xcframeworks

This should be clear enough that it's your responsability as a SDK provider to provide a privacy manifest.

We're working on providing SDK privacy manifests for Firebase. I don't have an ETA to share, but stay tuned.

@morganchen12  Please provide privacy manifests for Firebase.

We're actively working on them and expect to deliver them in an upcoming release.

We are using both firebase analytics and firebase crashlytics.
When you are delivering, will it support both static and dynamic framework?
Also, do you have any set date for the release?

Since Firebase currently only ships static frameworks in its binary distributions, we plan to first support that in the first few months of the new year.
We plan to add dynamic framework support when Firebase does its next major release, sometime later in the year.

Do you have any plans for which major SDK version will support Privacy Manifest? I'm using Firebase iOS SDK 8. Due to cost considerations, it is difficult for us to immediately upgrade to the latest major version. I know you are considering this, but I would like to ask you about your current plans.

@spdysgr It will likely be done in a future minor version of major version 10, but if something unexpected comes up, could require a major version 11.

Just following along, but with respect to planning @spdysgr - if you are looking to plan + allocate resources, the upstream documentation from Apple says this:

From Spring 2024, apps that don’t describe their use of required reason API in their privacy manifest file won’t be accepted by App Store Connect

In terms of planning deadlines, the most pessimistic interpretation of "Spring 2024" is when it starts on March 19, 2024 (about 3 months from now) and the most optimistic interpretation is June 20, 2024 (about 6 months from now) before Apple begins enforcing this.
Last time I gambled on interpretations of vague dates with Apple they started enforcing something at the earliest / most pessimistic opportunity, which was unfortunate (for me). Something to keep in mind so that you're read for firebase-ios-sdk 10 (or maybe 11)

@paulb777 @mikehardy Thank you for your quick response. I understood that I need to upgrade to latest SDK version (currently 10, but could become 11 depending on the situation) as soon as possible. I will try planning to upgrade SDK in our team.

+1

FYI https://developer.apple.com/support/third-party-SDK-requirements/

Since Firebase currently only ships static frameworks in its binary distributions, we plan to first support that in the first few months of the new year.
We plan to add dynamic framework support when Firebase does its next major release, sometime later in the year.

@paulb777 Thank you for your reply. I've got a quick question. According to the document below
https://developer.apple.com/support/third-party-SDK-requirements/
Firebase is included in the list which Apple announced for the commonly used SDK list.
and you said that you plan to the support in the first few months of the new year.
I wonder If newly supported static framework is xcframework or framework?
If It's xcframework, SDK signature will be supported for static framework also?
The document said that SDKs in the list must support SDK Signature.
so we want to know if this new policy should be applied to static framework also.
We are waiting for new framework to fulfill Apple's new requirement.

Hi @cityfarmerNexon,

I wonder If newly supported static framework is xcframework or framework?

Static framework is equal to xcframework in the context of Paul's comment.

If It's xcframework, SDK signature will be supported for static framework also?

Yes, correct, the xcframework would be signed.

Please provide privacy manifests for Firebase.

Hello,
Is there a tentative date and target release version for privacy manifest to be included in the Firebase SDK?
Thanks

Hello,
am bumping for an ETA for privacymanifest and code signing requirements as well

Hi everyone, this is a top priority for the team and we are making progress. I do not have an ETA to share yet, but will keep this thread updated.
In the meantime, you can prepare by migrating to Firebase 10 if you're using an older major version.
If you're using Firebase 10, the eventual release containing manifests and SDK signatures will be a minor version release, so migration will consist of a package update and rebuild.

One thing that hasn't been mentioned so far, GoogleDataTransport is also on the list of frameworks Apple has outlined.
Since that's an 'internal Google framework', only Google employees can PR a privacy manifest, yet one will be needed since it is a dependency of this library.
I guess Firebase's maintainers may be aware since they've already commented on nanopb about this, but worth mentioning in case anyone wonders why this is going to take some time. For teams taking this dependency from a different build system (i.e., Bazel), you would have to update all these libraries at the same time to meet Apple's requirements.

+1

Hi, when can we expect an update regarding this issue?

Hi, when can we expect an update regarding this issue?

@lakshmankreditbee @kalsariyarahul
https://github.com/firebase/firebase-ios-sdk/issues/11490#issuecomment-1881994104

Hi everyone, this is a top priority for the team and we are making progress. I do not have an ETA to share yet, but will keep this thread updated.
In the meantime, you can prepare by migrating to Firebase 10 if you're using an older major version.
If you're using Firebase 10, the eventual release containing manifests and SDK signatures will be a minor version release, so migration will consist of a package update and rebuild.

I discovered a new fact while testing. Until now, most of the libraries that have added PrivacyInfo have not been marked in PrivacyReport.
However, when an item is added to the 'Personal Information Nutrition Label Type', the library name is displayed in the personal information protection report.
Many libraries have updated PrivacyInfo without adding anything from Privacy Nutrition Label Types.
Does anyone know about this? Is "Privacy Nutrition Label Types" a must-have item?
Please feel free to leave your opinion.

I discovered a new while testing.
Until now, most of the libraries that have added PrivacyInfo have not been marked in PrivacyReport.
However, when an item is added to the 'Privacy Nutrition Label Types', the library name is displayed in the PrivacyReport.
Many libraries have updated PrivacyInfo without adding anything from 'Privacy Nutrition Label Types'.
Does anyone know about this? Is 'Privacy Nutrition Label Types' a must-have item?
Or is it not necessary to display it in the privacy report?
Please feel free to leave opinion.
The 'PrivacyReport' I'm talking about can be downloaded as a PDF if you archive the app.
https://developer.apple.com/videos/play/wwdc2023/10060/ Please refer to 3:20.

Open your project in Xcode.
Choose Product > Archive. Xcode creates the archive and reveals it in the organizer.
Control-click the archive in the organizer and choose Generate Privacy Report.

(I used a translator.)

The "Privacy Nutrition Label Types" are going to help you to declare the different cards you currently have to manually fill on the App Store once you want to publish a new app. By implementing the "Privacy Nutrition Label Types" within the xcprivacy file, Apple is going to automatically generate those cards and keep them up to date with your code. So yes it should be a must have in the libraries

I discovered a new while testing.
Until now, most of the libraries that have added PrivacyInfo have not been marked in PrivacyReport.
However, when an item is added to the 'Privacy Nutrition Label Types', the library name is displayed in the PrivacyReport.
Many libraries have updated PrivacyInfo without adding anything from 'Privacy Nutrition Label Types'.
Does anyone know about this? Is 'Privacy Nutrition Label Types' a must-have item?
Or is it not necessary to display it in the privacy report?
Please feel free to leave opinion.
The 'PrivacyReport' I'm talking about can be downloaded as a PDF if you archive the app.
https://developer.apple.com/videos/play/wwdc2023/10060/ Please refer to 3:20.

Open your project in Xcode.
Choose Product > Archive. Xcode creates the archive and reveals it in the organizer.
Control-click the archive in the organizer and choose Generate Privacy Report.

(I used a translator.)

The "Privacy Nutrition Label Types" are going to help you to declare the different cards you currently have to manually fill on the App Store once you want to publish a new app. By implementing the "Privacy Nutrition Label Types" within the xcprivacy file, Apple is going to automatically generate those cards and keep them up to date with your code. So yes it should be a must have in the libraries

@AlbGarciam Do you know where it's stated that Apple will automatically generate the Privacy nutrition cards on App Store based on the privacy manifest file?
Correct me if I am wrong, It's our understanding (so far) that we will have to update those cards manually on app store based on the generated privacy report.
Thanks

I discovered a new while testing.

Until now, most of the libraries that have added PrivacyInfo have not been marked in PrivacyReport.

However, when an item is added to the 'Privacy Nutrition Label Types', the library name is displayed in the PrivacyReport.

Many libraries have updated PrivacyInfo without adding anything from 'Privacy Nutrition Label Types'.

Does anyone know about this? Is 'Privacy Nutrition Label Types' a must-have item?

Or is it not necessary to display it in the privacy report?

Please feel free to leave opinion.

The 'PrivacyReport' I'm talking about can be downloaded as a PDF if you archive the app.

https://developer.apple.com/videos/play/wwdc2023/10060/ Please refer to 3:20.

Open your project in Xcode.

Choose Product > Archive. Xcode creates the archive and reveals it in the organizer.

Control-click the archive in the organizer and choose Generate Privacy Report.

(I used a translator.)

The "Privacy Nutrition Label Types" are going to help you to declare the different cards you currently have to manually fill on the App Store once you want to publish a new app. By implementing the "Privacy Nutrition Label Types" within the xcprivacy file, Apple is going to automatically generate those cards and keep them up to date with your code. So yes it should be a must have in the libraries

@AlbGarciam Do you know where it's stated that Apple will automatically generate the Privacy nutrition cards on App Store based on the privacy manifest file?
Correct me if I am wrong, It's our understanding (so far) that we will have to update those cards manually on app store based on the generated privacy report.
Thanks

As far as they told me during WWDC yes

You could use the generated pdf as a guide but the privacy nutrition labels on App Store Connect MUST be updated manually. I confirmed this with Apple folks.

New release version of Firebase, still no privacy manifest, could you please help check?

We weren't able to complete the privacy manifests in time for 10.21.0 and are hopeful we can release in 10.22.0, due out the week of February 26th.

We weren't able to complete the privacy manifests in time for 10.21.0 and are hopeful we can release in 10.22.0, due out the week of February 26th.

Thank you for your continued support and the timely update regarding the privacy manifest situation.
However, as far as I know, Google Firebase provides multiple SDKs. May I confirm if all of these SDKs will include privacy manifest files in accordance with Apple's regulations?

We're working on privacy manifests for all Firebase SDKs and dependencies.

We're working on privacy manifests for all Firebase SDKs and dependencies.

Hi,
In that version, Will you support the sign for sdk frameworks?
Regards!

Signing will take longer and may not make the same release as the manifests, but it will follow as soon as we can. Signing is tracked at #12238.

Privacy manifests for the Firebase SDKs named in https://developer.apple.com/support/third-party-SDK-requirements/ have merged to main in #12407 and is planned to be part of the next release due out the week of March 5th.

Does the GoogleSignIn SDK support Privacy Manifests?

Privacy manifests for the Firebase SDKs named in https://developer.apple.com/support/third-party-SDK-requirements/ have merged to main in #12407 and is planned to be part of the next release due out the week of March 5th.

@paulb777 you'll need to update GoogleAppMeasurement as well, as it's currently pinning nanopb (one of the SDKs named on that list) to the version before the privacy manifest was introduced.
See https://github.com/google/GoogleAppMeasurement/blob/main/Package.swift#L43-L47

Privacy manifests for the Firebase SDKs named in https://developer.apple.com/support/third-party-SDK-requirements/ have merged to main in #12407 and is planned to be part of the next release due out the week of March 5th.

You'll need to update GoogleAppMeasurement as well, as it's currently pinning nanopb (one of the SDKs named on that list) to the version before the privacy manifest was introduced.
See https://github.com/google/GoogleAppMeasurement/blob/main/Package.swift#L43-L47

Hi @sylvia-tencent-wmt,

Does the support for Privacy Manifests include the GoogleSignIn SDK?

The GoogleSignIn SDK has a different release schedule, so GoogleSignIn SDK's support of privacy manifests may not exactly align with the upcoming Firebase release. I would continue to follow https://github.com/google/GoogleSignIn-iOS/issues/341 for updates.

Hi is it possible to get a date for release with privacyManifest and code signing signatures as well?

See https://github.com/firebase/firebase-ios-sdk/issues/11490#issuecomment-1962119838 for named Firebase privacy manifests. We're working on code signing, but don't have a date yet. Follow #12238 for updates on signing.

The 10.22.0 release added privacy manifests for the Firebase SDKs named in https://developer.apple.com/support/third-party-SDK-requirements/. Signing support will continue to be tracked in https://github.com/firebase/firebase-ios-sdk/issues/12238.

Hi @andrewheard,
I have added FirebaseABTesting.xcframework to the project and generate privacy report I am still getting error like "The archive does not contain any PrivacyInfo.xcprivacy files"
Any solution for this? Also I noticed you guys have added "FirebaseABTesting_Privacy.bundle" but when I archive it's not added in the final bundle of the app. I am using Xcode 15.
Any recommendations?

Hi @andrewheard,
FirebaseCrashlytics seems to be missing from release 10.22.0's Firebase.zip

@ManoharaReddyP @GH-Ong Please open separate issues with a completed template to make it easier to assess. I'm going to lock this issue for further comments.  Please open a new GitHub issue for any other issues .


Can I change sub-routes with main-routes in run-time

I use a DrawerNavigator which consists of only one StackNavigator.
Because of components (screens) re-rendering when the current stack is changed I use only one StackNavigator.
My setup like the below:
AppNavigator (StackNavigator)

    ->    mainDrawer (DrawerNavigator)

          ->  mainStack (StackNavigator)

              -> Home (Screen component)
              -> Profile (Screen component)
              -> Contact (Screen component)

I wonder that can I change sub-routes (Home, Profile and Contact) with main-routes (in this case there is only one route, mainStack)?
Details
With this setup, the app opens Home screen first. The components on the screen can be changed according to Redux state. Users can navigate the other screens by using drawer menu (DrawerNavigator). Also users can return to Home screen by pressing HeaderLeft back button.
And also users can back to Home screen directly by using drawer menu. I use the code below to perform this case:
_backToHome = () => {

	const navigateAction = NavigationActions.navigate({
		routeName: 'mainStack',
		action: NavigationActions.back()
	})

	let routes = this.props.navigation.state.routes[0].routes
	routes.forEach((currentValue, index, array) => {
		if (index < routes.length - 1) { // don't dispatch for the initial route
			this.props.navigation.dispatch(navigateAction)
		}
	})

}

(action option in navigate works like a charm!)
It works.
However, if I can set Home, Profile and Contact sub-routes as main-routes so instead of mainStack everything would be more easy.
For instance, this.props.navigation.state.routes[0].index gives the current route index. But I can find the current route index at  this.props.navigation.state.routes[0].routes[0].index with the code above.
Also I cannot use this.props.navigation.goBack() helper and cannot dispatch NavigationActions.back on DrawerNavigator because of the same reason.
Your Environment

software
version

react-navigation
^1.0.0-beta.11

react-native
0.44.2

node
v7.10.0

npm or yarn
4.2.0

Hi! In an effort to get the hundreds of issues on this repo under control I'm closing issues tagged as questions. Please don't take this personally - it's simply something we need to do to get the issues to a manageable point. If you still have a question I encourage you to re-read the docs, ask on StackOverflow, or ask on the #react-navigation Reactiflux channel. Thank you!


TeraRangerOne fails to start

Hi,
I am not able to run TeraRAngerOne with PX4 firmware 1.5.3 on Pixhawk 2.1.
1- I connected TeraRangerOne to Pixhawk2.1 I2C
2- I change the 'trone' parameter in QGC to 'Enable'
3- I restart the Pixhawk, but the I cannot see the sensor data in QGC
4- I use nsh> trone start
5- it fails with the following error: Trone driver start failed'
What is missing here?
Do I have to solder the JP1 on the I2C adapter?
the TeraRanger sensor version is 1601.
Thanks

Does the TROne work on other devices (e.g. via USB on your PC)?
When powering the Pixhawk, do you see the yellow LED on the TROne board flash once?
Is it possible that the I2C address has been changed on this device?
If you're familiar with building the firmware youself, I'd suggest adding some print statements (warnx) in the start routine to narrow down the source of the problem: https://github.com/PX4/Firmware/blob/b6b889260689cb340d6815fc68aea831751f48bc/src/drivers/trone/trone.cpp#L732

Does the TROne work on other devices (e.g. via USB on your PC)?
Yes

When powering the Pixhawk, do you see the yellow LED on the TROne board flash once?
Yes

Is it possible that the I2C address has been changed on this device?
How/where can I check that? datasheet? I wil double check on that.

I am familiar with building the firmware. I will check on that.  what are the places where [warnx] tags would be useful?
Thanks

A different I2C address is unlikely. Older versions of the TROne did not ship with I2C capabilities by default, so you had to request it from the manufacturer, and you could request a specific I2C address. Unless you asked for an alternate firmware with a changed I2C address, this is probably not the cause.
I would just place them in the various failure checks to see which part of the initialization process reports an error.

Thanks. We did not ask for special mods on the sensor. The sensor version is 1601.
I placed several checks in the code, and here where it gets stuck:
https://github.com/PX4/Firmware/blob/b6b889260689cb340d6815fc68aea831751f48bc/src/drivers/trone/trone.cpp#L280
	if (I2C::init() != OK) {
		goto out;
}
``

So, I did more debugging, and it fails here in the i2c_nuttx.cpp:
https://github.com/PX4/Firmware/blob/b6b889260689cb340d6815fc68aea831751f48bc/src/drivers/device/i2c_nuttx.cpp#L151
What could be the issue?

@mzahana: Are you sure that your i2c wiring is correct? Check the attached pictures for the wiring (note that the wires on extreme positions are swapped). Otherwise can you check the continuity in all the i2c wires?

Problem is solved. It was a combination of corrupted i2c cable and the i2c
adapter!
On Jan 12, 2017 4:39 PM, "Mateusz Sadowski"<EMAIL_ADDRESS>wrote:

@mzahana https://github.com/mzahana: Are you sure that your i2c wiring
is correct? Check the attached pictures for the wiring (note that the wires
on extreme positions are swapped). Otherwise can you check the continuity
in all the i2c wires?
[image: rangefinder_teraranger_one_pixhawk]
https://cloud.githubusercontent.com/assets/6543766/21891839/dd1e6374-d8d4-11e6-9b35-a75bd45a6e27.jpg
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/PX4/Firmware/issues/6259#issuecomment-272165135, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AIZT63Q97hAJRf1qbugsfMYIp65Jlsc9ks5rRi0LgaJpZM4LbXTp
.


Allow injecting the list of backend features in a root service.

Hey, I just made a Pull Request!
Allow injecting the list of BackendFeatureRegstrations in a root service by simply have the service implement a given interface.
This PR is the minimal change required to be able to further implement the requirement behind RFC https://github.com/backstage/backstage/issues/17538, possibly in different ways.
It is provided as a non-invasive, and non-opinionated alternative to PR https://github.com/backstage/backstage/pull/22332, which would let users have way to retrieve the list of local pluginIDs (and possibly moduleIDs) without imposing a given implementation choice for the whole RFC.
:heavy_check_mark: Checklist

[x] A changeset describing the change and affected packages. (more info)
[ ] Added or updated documentation
[x] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)
[ ] All your commits have a Signed-off-by line in the message. (more info)

cc @Rugvip

Yeah don't worry about the jest-dom errors. That's caused by a terribly broken release of theirs. In fact, almost all end-to-end errors you can just leave up to us to double check, if it looks unrelated it probably is.

Yeah don't worry about the jest-dom errors. That's caused by a terribly broken release of theirs. In fact, almost all end-to-end errors you can just leave up to us to double check, if it looks unrelated it probably is.

Thanks for your answer !

According to the work done by @sennyeya in PR https://github.com/backstage/backstage/pull/22671, which is based on my PR https://github.com/backstage/backstage/pull/22332 of which this PR was just a minimal derivative, I assume that the current PR could be considered an obsolete attempt, and the initial PR https://github.com/backstage/backstage/pull/22332 could hopefully be merged, and be a first step towards the Full Split Backends support proposed in PR  https://github.com/backstage/backstage/pull/22671 ?

Only one of #22332 and this should be open right? I posted an update over at https://github.com/backstage/backstage/pull/22332#pullrequestreview-1877492814


Missing locale script for postgres:15.3-alpine3.18

I'd like to initialize locale with ICU support and alpine latest.
Not sure if it's a problem, but there's a warning about missing locale script

Docker compose example:
version: '3'

services:
  postgres:
    image: postgres:15.3-alpine3.18
    environment:
      POSTGRES_USER: strapi
      POSTGRES_PASSWORD: strapi
      POSTGRES_DB: strapi_test
      POSTGRES_INITDB_ARGS: '--locale-provider=icu --icu-locale=en-US --no-sync'
    restart: always
    ports:
      - '5432:5432'
    volumes:
      - pgdata_test:/var/lib/postgresql/data:rw
    healthcheck:
      test: ["CMD-SHELL", "sh -c 'pg_isready -U strapi -d strapi_test'"]
      interval: 2s
      timeout: 5s
      retries: 5
volumes:
  pgdata_test:

Full log
strapi-postgres-1  | The files belonging to this database system will be owned by user "postgres".
strapi-postgres-1  | This user must also own the server process.
strapi-postgres-1  |
strapi-postgres-1  | The database cluster will be initialized with this locale configuration:
strapi-postgres-1  |   provider:    icu
strapi-postgres-1  |   ICU locale:  en-US
strapi-postgres-1  |   LC_COLLATE:  en_US.utf8
strapi-postgres-1  |   LC_CTYPE:    en_US.utf8
strapi-postgres-1  |   LC_MESSAGES: en_US.utf8
strapi-postgres-1  |   LC_MONETARY: en_US.utf8
strapi-postgres-1  |   LC_NUMERIC:  en_US.utf8
strapi-postgres-1  |   LC_TIME:     en_US.utf8
strapi-postgres-1  | The default database encoding has been set to "UTF8".
strapi-postgres-1  | The default text search configuration will be set to "english".
strapi-postgres-1  |
strapi-postgres-1  | Data page checksums are disabled.
strapi-postgres-1  |
strapi-postgres-1  | fixing permissions on existing directory /var/lib/postgresql/data ... ok
strapi-postgres-1  | creating subdirectories ... ok
strapi-postgres-1  | selecting dynamic shared memory implementation ... posix
strapi-postgres-1  | selecting default max_connections ... 100
strapi-postgres-1  | selecting default shared_buffers ... 128MB
strapi-postgres-1  | selecting default time zone ... UTC
strapi-postgres-1  | creating configuration files ... ok
strapi-postgres-1  | running bootstrap script ... ok
strapi-postgres-1  | sh: locale: not found
strapi-postgres-1  | 2023-05-14 11:03:30.936 UTC [30] WARNING:  no usable system locales were found
strapi-postgres-1  | initdb: warning: enabling "trust" authentication for local connections
strapi-postgres-1  | initdb: hint: You can change this by editing pg_hba.conf or using the option -A, or --auth-local and --auth-host, the next time you run initdb.
strapi-postgres-1  | performing post-bootstrap initialization ... ok
strapi-postgres-1  |
strapi-postgres-1  | Sync to disk skipped.
strapi-postgres-1  | The data directory might become corrupt if the operating system crashes.
strapi-postgres-1  |
strapi-postgres-1  |
strapi-postgres-1  | Success. You can now start the database server using:
strapi-postgres-1  |
strapi-postgres-1  |     pg_ctl -D /var/lib/postgresql/data -l logfile start
strapi-postgres-1  |
strapi-postgres-1  | waiting for server to start....2023-05-14 11:03:31.264 UTC [36] LOG:  starting PostgreSQL 15.3 on x86_64-pc-linux-musl, compiled by gcc (Alpine 12.2.1_git20220924-r10) 12.2.1 20220924, 64-bit
strapi-postgres-1  | 2023-05-14 11:03:31.265 UTC [36] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
strapi-postgres-1  | 2023-05-14 11:03:31.268 UTC [39] LOG:  database system was shut down at 2023-05-14 11:03:31 UTC
strapi-postgres-1  | 2023-05-14 11:03:31.270 UTC [36] LOG:  database system is ready to accept connections
strapi-postgres-1  |  done
strapi-postgres-1  | server started
strapi-postgres-1  | CREATE DATABASE
strapi-postgres-1  |
strapi-postgres-1  |
strapi-postgres-1  | /usr/local/bin/docker-entrypoint.sh: ignoring /docker-entrypoint-initdb.d/*
strapi-postgres-1  |
strapi-postgres-1  | waiting for server to shut down....2023-05-14 11:03:31.427 UTC [36] LOG:  received fast shutdown request
strapi-postgres-1  | 2023-05-14 11:03:31.428 UTC [36] LOG:  aborting any active transactions
strapi-postgres-1  | 2023-05-14 11:03:31.429 UTC [36] LOG:  background worker "logical replication launcher" (PID 42) exited with exit code 1
strapi-postgres-1  | 2023-05-14 11:03:31.429 UTC [37] LOG:  shutting down
strapi-postgres-1  | 2023-05-14 11:03:31.430 UTC [37] LOG:  checkpoint starting: shutdown immediate
strapi-postgres-1  | 2023-05-14 11:03:31.453 UTC [37] LOG:  checkpoint complete: wrote 918 buffers (5.6%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.010 s, sync=0.012 s, total=0.025 s; sync files=250, longest=0.001 s, average=0.001 s; distance=4222 kB, estimate=4222 kB
strapi-postgres-1  | 2023-05-14 11:03:31.458 UTC [36] LOG:  database system is shut down
strapi-postgres-1  |  done
strapi-postgres-1  | server stopped
strapi-postgres-1  |
strapi-postgres-1  | PostgreSQL init process complete; ready for start up.
strapi-postgres-1  |
strapi-postgres-1  | 2023-05-14 11:03:31.583 UTC [1] LOG:  starting PostgreSQL 15.3 on x86_64-pc-linux-musl, compiled by gcc (Alpine 12.2.1_git20220924-r10) 12.2.1 20220924, 64-bit
strapi-postgres-1  | 2023-05-14 11:03:31.583 UTC [1] LOG:  listening on IPv4 address "<IP_ADDRESS>", port 5432
strapi-postgres-1  | 2023-05-14 11:03:31.583 UTC [1] LOG:  listening on IPv6 address "::", port 5432
strapi-postgres-1  | 2023-05-14 11:03:31.585 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
strapi-postgres-1  | 2023-05-14 11:03:31.589 UTC [52] LOG:  database system was shut down at 2023-05-14 11:03:31 UTC
strapi-postgres-1  | 2023-05-14 11:03:31.592 UTC [1] LOG:  database system is ready to accept connections
strapi-postgres-1  | 2023-05-14 11:08:31.686 UTC [50] LOG:  checkpoint starting: time
strapi-postgres-1  | 2023-05-14 11:08:35.862 UTC [50] LOG:  checkpoint complete: wrote 44 buffers (0.3%); 0 WAL file(s) added, 0 removed, 0 recycled; write=4.119 s, sync=0.027 s, total=4.177 s; sync files=12, longest=0.024 s, average=0.003 s; distance=252 kB, estimate=252 kB

I don't think the Alpine images have ever included locale -- the end result appears to work successfully in spite of this?
$ docker run -it --rm --env POSTGRES_INITDB_ARGS='--locale-provider=icu --icu-locale=de-DE' --env LANG='de_DE.utf8' --env POSTGRES_PASSWORD=example postgres:15-alpine3.18
Unable to find image 'postgres:15-alpine3.18' locally
15-alpine3.18: Pulling from library/postgres
8a49fdb3b6a5: Already exists
397880efeff2: Pull complete
7981ad2d616c: Pull complete
521df6ab8516: Pull complete
46ac16d4613e: Pull complete
3c0b7c938b8a: Pull complete
230669f5a759: Pull complete
4dbd9486f09b: Pull complete
Digest: sha256:f632b07cad142a12360e5c4c084a3cf62fc95f3ee0be285647b4d3744840cade
Status: Downloaded newer image for postgres:15-alpine3.18
The files belonging to this database system will be owned by user "postgres".
This user must also own the server process.

The database cluster will be initialized with this locale configuration:
  provider:    icu
  ICU locale:  de-DE
  LC_COLLATE:  de_DE.utf8
  LC_CTYPE:    de_DE.utf8
  LC_MESSAGES: de_DE.utf8
  LC_MONETARY: de_DE.utf8
  LC_NUMERIC:  de_DE.utf8
  LC_TIME:     de_DE.utf8
The default database encoding has been set to "UTF8".
The default text search configuration will be set to "german".

Data page checksums are disabled.

fixing permissions on existing directory /var/lib/postgresql/data ... ok
creating subdirectories ... ok
selecting dynamic shared memory implementation ... posix
selecting default max_connections ... 100
selecting default shared_buffers ... 128MB
selecting default time zone ... UTC
creating configuration files ... ok
running bootstrap script ... ok
performing post-bootstrap initialization ... sh: locale: not found
2023-05-15 18:27:04.821 UTC [30] WARNING:  no usable system locales were found
ok
syncing data to disk ... ok

initdb: warning: enabling "trust" authentication for local connections
initdb: hint: You can change this by editing pg_hba.conf or using the option -A, or --auth-local and --auth-host, the next time you run initdb.

Success. You can now start the database server using:

    pg_ctl -D /var/lib/postgresql/data -l logfile start

waiting for server to start....2023-05-15 18:27:05.323 UTC [36] LOG:  starting PostgreSQL 15.3 on x86_64-pc-linux-musl, compiled by gcc (Alpine 12.2.1_git20220924-r10) 12.2.1 20220924, 64-bit
2023-05-15 18:27:05.325 UTC [36] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2023-05-15 18:27:05.331 UTC [39] LOG:  database system was shut down at 2023-05-15 18:27:05 UTC
2023-05-15 18:27:05.335 UTC [36] LOG:  database system is ready to accept connections
 done
server started

/usr/local/bin/docker-entrypoint.sh: ignoring /docker-entrypoint-initdb.d/*

waiting for server to shut down....2023-05-15 18:27:05.448 UTC [36] LOG:  received fast shutdown request
2023-05-15 18:27:05.454 UTC [36] LOG:  aborting any active transactions
2023-05-15 18:27:05.455 UTC [36] LOG:  background worker "logical replication launcher" (PID 42) exited with exit code 1
2023-05-15 18:27:05.455 UTC [37] LOG:  shutting down
2023-05-15 18:27:05.457 UTC [37] LOG:  checkpoint starting: shutdown immediate
2023-05-15 18:27:05.468 UTC [37] LOG:  checkpoint complete: wrote 3 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.004 s, sync=0.002 s, total=0.014 s; sync files=2, longest=0.001 s, average=0.001 s; distance=0 kB, estimate=0 kB
2023-05-15 18:27:05.471 UTC [36] LOG:  database system is shut down
 done
server stopped

PostgreSQL init process complete; ready for start up.

2023-05-15 18:27:05.575 UTC [1] LOG:  starting PostgreSQL 15.3 on x86_64-pc-linux-musl, compiled by gcc (Alpine 12.2.1_git20220924-r10) 12.2.1 20220924, 64-bit
2023-05-15 18:27:05.575 UTC [1] LOG:  listening on IPv4 address "<IP_ADDRESS>", port 5432
2023-05-15 18:27:05.575 UTC [1] LOG:  listening on IPv6 address "::", port 5432
2023-05-15 18:27:05.578 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2023-05-15 18:27:05.583 UTC [50] LOG:  database system was shut down at 2023-05-15 18:27:05 UTC
2023-05-15 18:27:05.587 UTC [1] LOG:  database system is ready to accept connections

And then in another terminal:
$ docker exec -it vigorous_albattani psql -U postgres
psql (15.3)
Type "help" for help.

postgres=# \l
                                                List of databases
   Name    |  Owner   | Encoding |  Collate   |   Ctype    | ICU Locale | Locale Provider |   Access privileges
-----------+----------+----------+------------+------------+------------+-----------------+-----------------------
 postgres  | postgres | UTF8     | de_DE.utf8 | de_DE.utf8 | de-DE      | icu             |
 template0 | postgres | UTF8     | de_DE.utf8 | de_DE.utf8 | de-DE      | icu             | =c/postgres          +
           |          |          |            |            |            |                 | postgres=CTc/postgres
 template1 | postgres | UTF8     | de_DE.utf8 | de_DE.utf8 | de-DE      | icu             | =c/postgres          +
           |          |          |            |            |            |                 | postgres=CTc/postgres
(3 rows)

Can't say for sure, but I can confirm on the postgres side it seems to work properly.

Link to https://github.com/gliderlabs/docker-alpine/issues/144

Closing since this appears to be working correctly / as intended.

Maybe I am missing something, but it looks like sorting is still done using default "C" locale even if I set custom one.
I set locale like this:
    environment:
      POSTGRES_INITDB_ARGS: "--locale-provider=icu --icu-locale=en-AU"
      LANG: en_AU.utf-8
      LC_COLLATE: en_AU.utf-8
      LC_CTYPE: en_AU.utf-8
      LC_ALL: en_AU.utf-8

Then in logs I see same thing as mentioned above:
The database cluster will be initialized with this locale configuration:
   provider:    icu
   ICU locale:  en-AU
   LC_COLLATE:  en_AU.utf-8
   LC_CTYPE:    en_AU.utf-8
   LC_MESSAGES: en_AU.utf-8
   LC_MONETARY: en_AU.utf-8
   LC_NUMERIC:  en_AU.utf-8
   LC_TIME:     en_AU.utf-8
 The default database encoding has been set to "UTF8".
 The default text search configuration will be set to "english".

 Data page checksums are disabled.

 fixing permissions on existing directory /var/lib/postgresql/data ... ok
 creating subdirectories ... ok
 selecting dynamic shared memory implementation ... posix
 selecting default max_connections ... 100
 selecting default shared_buffers ... 128MB
 selecting default time zone ... UTC
 creating configuration files ... ok
 running bootstrap script ... ok
 performing post-bootstrap initialization ... sh: locale: not found
 2024-10-29 06:58:55.692 UTC [30] WARNING:  no usable system locales were found

If I check datcollate, I see it is showing as set:
odoodb=# select datname, datcollate from pg_database;
  datname  | datcollate
-----------+-------------
 postgres  | en_AU.utf-8
 odoodb    | en_AU.utf-8
 template1 | en_AU.utf-8
 template0 | en_AU.utf-8

But sorting still works the same as using C:
odoodb=# select default_code from product_template
order by default_code;

I see this:
default_code
--------------
 A-HS
 AA-A
 E-COM06
 E-COM07
 E-COM08

If Australian locale would be used, it should have AA-A before A-HS as it should preffer letters first instead of special symbols, right?
Also if I try to explicitly use collate in sorting, I get error saying there is no such collate:
odoodb=# select default_code from product_template
order by default_code collate "en_AU.utf-8";
ERROR:  collation "en_AU.utf-8" for encoding "UTF8" does not exist
LINE 2: order by default_code collate "en_AU.utf-8";

Though it works if I explicitly specify "C"..
To me it looks that  2024-10-29 06:58:55.692 UTC [30] WARNING:  no usable system locales were found means that no locale is actually set, even if it is showing as set?..

See https://wiki.musl-libc.org/open-issues#Locale-limitations (it "works" but I don't know that it actually functions correctly, as you've experienced, and certainly isn't actually an officially supported platform by PostgreSQL upstream, to my knowledge)


Bagel Update 11.6

changelog
-medical now has some nanomeds
-door to genetics is now properly accessed
-added nitrile gloves to cmo's room (theyre good for diseases)
-deleted and then replaced RD server and point gen because some people said that might fix the bugs its been having??
-added a firelock to the smartfridge in chem so it won't get spaced if med is spaced. fear no more spaced-in-med
-replaced all saltern smes and subs with the basic, 4mw and 10mw updated version
-added the catwalk to the middle of the AME room because i saw on moose a lot of people using it to teach new players without having to pry tiles up or use a t ray
-added crim records computers to HoS office and bridge (they dont have functionality yet)
-skub

SignPods were renamed to SignEscapePods in #6401
you should just be able to find-replace in the yml.

ah ok thanks


[Hacktoberfest] A function to remove a project

Task
Implement a function to remove a project in JavaScript SDK.
Follow similar pattern as in the Python SDK.
Deliverables
Create a PR to this repository with the implementation.
:loudspeaker: Additional rewards :trophy:
This issue brings up to :five:  :zero:  points for SWAG and entry into the draw for a  :point_down: :

:three:  :x:   :computer:  Razer Blade 16 Gaming Laptop
:shirt: :bear:  MindsDB Swag

:information_source: For more info check out https://mindsdb.com/hacktoberfest :point_left:

@quest-bot embark

@quest-bot embark

Its unclear how to remove it, need more info
Python method for this:
https://github.com/mindsdb/mindsdb_python_sdk/blob/main/mindsdb_sdk/projects.py

Rest API:
No docs
https://docs.mindsdb.com/rest/projects/drop

@ea-rus @ZoranPandovski ^^

I am working on it i know how to implement it. I will complete it by today.

I am working on it i know how to implement it. I will complete it by today.

Tell me as well bro

#76 need to be merged before this can be implemented, otherwise it will cause merge conflict.


Updated the tool.

Updated the README for stack usage.
Updated the cabal file, to remove binaries, and include hint in the build of concepts.

@jrbeaumont Thank you, this looks good.


fix matplotlib requirement

See #115, this comment.

Huh the conda cloud versions must have changed :/


Backport "improvement: Replace synthetic decorations with inlay hints" to LTS

Backports #19754 to the LTS branch.
PR submitted by the release tooling.
[skip ci]

No regressions detected in the community build up to lts-19080.
Reference


Response Code

Hi, I am a bit of a noob with this, but it looks like there isn't a clear way to set a response code for an endpoint request. I was thinking I could maybe do it with RegisterModule, but it looks like it only allows the message to be sent back.

Yes, that's a bit outside the original idea for this (stand-in for a third party service that works reliably in production but not in a test environment).  What's your use case?  Maybe we can figure something out.

We were just keen to use it for mocking for testing a bridge API we are working on. But i think in order to facilitate it it would likely involve a breaking change.

If you're ok with the module hydrating a full response object, then I'm pretty sure I can make it work without breaking anything.  If nothing else I can give you a branch to start from: you can fork and make it your own.

I'm happy to fork, at the time I hadn't looked at the code thoroughly enough, if there is simple way to facilitate that then i'd certainly be happy with it :smile:

Ok, here's a rough cut at my idea:
You register a module just like before.  Instead of respond_to it should have a handle_request(request, response) method.  handle_request will receive the request (a hash with :body and :headers keys) and the Sinatra::Response object.
The handler will be responsible for hydrating the response and returning it.  You can see a very crude example in this test.
To test with this (I hope you're using Bundler), just replace your normal pinch_hitter line with:
:git => 'https://github.com/stevenjackson/pinch_hitter.git', :branch => 'with_headers'

If you're happy with it, I'll do some refactoring and docs and roll a new release.  I'm open to suggestions on either the request or response object; I went with the path of least resistance on both.
Let me know if it works!

this looks like it could work, I will have a play see how i get on

@sonewman Did this work out for you?

no not really, it seemed to make my previously passing test fail, i'm not sure why. So i just wrote a thin wrapper around Sinatra instead. Sorry I didn't get back to you.

No problem, glad you didn't get stuck.  I'll close this out unless there's a reason to pick it up again.

Cool, thanks for you help anyways I appreciate you getting back to me :smile:


[WIP] Adjust Velero to custom needs

Thank you for contributing to Velero!
Please add a summary of your change
Does your change fix a particular issue?
Fixes #(issue)
Please indicate you've done the following:
[ ] Accepted the DCO. Commits without the DCO will delay acceptance.
[ ] Created a changelog file or added /kind changelog-not-required.
[ ] Updated the corresponding documentation in site/content/docs/main.

Closed in favor of https://github.com/c445/velero/pull/2


crash linked to FPRNetworkTrace

Step 0: Are you in the right place?

For issues or feature requests related to the code in this repository
file a Github issue.

If this is a feature request please use the Feature Request template.

For general technical questions, post a question on StackOverflow
with the firebase tag.
For general (non-iOS) Firebase discussion, use the firebase-talk
google group.
For backend issues, console issues, and other non-SDK help that does not fall under one
of the above categories, reach out to
Firebase Support.
Once you've read this section and determined that your issue is appropriate for
this repository, please delete this section.

[REQUIRED] Step 1: Describe your environment

Xcode version: 12.0
Firebase SDK version: 7.0.0
Installation method: CocoaPods (select one)
Firebase Component:  Analytics, Crashlytics, Performance

[REQUIRED] Step 2: Describe the problem
Steps to reproduce:
What happened? How can we make the problem occur?
This could be a description, log/console output, etc.
I did not manage to reproduce the crash but as I looked around a little bit, I found that the crash occured when on another thread did some job related to Firebase.
If you have a downloadable sample project that reproduces the bug you're reporting, you will
likely receive a faster response on your issue.

It looks like a duplicate of #6734 from the first glance.

Looking at the crashing stack trace, this is a duplicate of #6734 .

Thanks @maksymmalyhin & @visumickey


Support optional ResourcePrefix parameter in deploy-data-collection.yaml

Summary:
The data-collection/deploy/deploy-data-collection.yaml
 template contains a parameter that is used in multiple resources.
Such as prefixing resource names, in IAM Role Paths, and to construct the MultiAccountRoleName parameter passed in nested stacks.
Issue:
There are use cases where customers may want to use an existing role and pass that Role Name through the MultiAccountRoleName parameter. However, this can cause complications/issues since that parameter is prefixed with the ResourcePrefix:
MultiAccountRoleName: !Sub "${ResourcePrefix}${MultiAccountRoleName}"
Attempts to get around this issue were to provide an empty string   for ResourcePrefix however this causes failures since IAM role paths are constructed using the ResourcePrefix
Path:
    Fn::Sub: /${ResourcePrefix}/ # resolves to // with empty string which is invalid

Workaround:
The only way around this issue if you want to provide your own Role is to split the role name between ResourcePrefix and MultiAccountRoleName.
For example: With a Role named: MyCustomIAMRole
ResourcePrefix: My
MultiAccountRoleName: CustomIAMRole
So that when it combines it becomes the correct full role name while also providing a value for ResourcePrefix
ResourcePrefix:
MultiAccountRoleName: !Sub "${ResourcePrefix}${MultiAccountRoleName}" # Resolves to MyCustomIAMRole
This is clearly not ideal as now other resources will be prefixed with My
Fix:
Update so that either ResourcePrefix is used conditionally in IAM Role Paths or MultiAccountRoleName is used without the ResourcePrefix when constructing/passing it as a parameter (e.g. MultiAccountRoleName: !Ref MultiAccountRoleName)

interesting idea, but i guess it will complexity code by alot

Right, but will fix the issue in hand.


Raidboss no longer working. Throwing thousands of errors

Raidboss plugin has now stopped working for some reason after I updated to the most recent release of the ACT FFXIV plugin.
I have tried downgrading the ACT FFXIV plugin and there has been no change. I have also tried re-installing Cactbot to no change.
The FSH overlay for Cactbot is still running just fine only raidboss has broken itself.
My parsing addon is running fine as well
Log file is filled with many errors:
21/08/2019 01:46:54: Info: LoadAddons: D:\ACT Plugins\OverlayPlugin\addons\CactbotOverlay.dll
21/08/2019 01:46:54: Info: LoadAddons: Cactbot.OverlayAddonMain: Initialized
21/08/2019 01:46:54: Info: InitPlugin: Initialized.
21/08/2019 01:46:55: Info: Raid-Cactbot: BrowserConsole: Uncaught SyntaxError: Unexpected token : (Source: file:///D:/ACT%20Plugins/OverlayPlugin/cactbot/ui/raidboss/raidboss.html, Line: 3)
21/08/2019 01:46:55: Info: Raid-Cactbot: BrowserConsole: Uncaught TypeError: Cannot read property 'OnDataFilesRead' of undefined (Source: file:///D:/ACT%20Plugins/OverlayPlugin/cactbot/ui/raidboss/popup-text.js, Line: 543)
21/08/2019 01:46:55: Info: Raid-Cactbot: BrowserConsole: Uncaught TypeError: Cannot read property 'SetDataFiles' of undefined (Source: file:///D:/ACT%20Plugins/OverlayPlugin/cactbot/ui/raidboss/raidboss.js, Line: 50)
21/08/2019 01:46:57: Info: Raid-Cactbot: BrowserConsole: Uncaught TypeError: Cannot read property 'OnInCombatChange' of undefined (Source: file:///D:/ACT%20Plugins/OverlayPlugin/cactbot/ui/raidboss/popup-text.js, Line: 537)
21/08/2019 01:46:57: Info: Raid-Cactbot: BrowserConsole: Uncaught TypeError: Cannot read property 'OnZoneChange' of undefined (Source: file:///D:/ACT%20Plugins/OverlayPlugin/cactbot/ui/raidboss/popup-text.js, Line: 534)
21/08/2019 01:46:57: Info: Raid-Cactbot: BrowserConsole: Uncaught TypeError: Cannot read property 'OnPlayerChange' of undefined (Source: file:///D:/ACT%20Plugins/OverlayPlugin/cactbot/ui/raidboss/popup-text.js, Line: 531)

21/08/2019 01:48:00: Info: Raid-Cactbot: BrowserConsole: Uncaught TypeError: Cannot read property 'OnLog' of undefined (Source: file:///D:/ACT%20Plugins/OverlayPlugin/cactbot/ui/raidboss/popup-text.js, Line: 540)
21/08/2019 01:48:00: Info: Raid-Cactbot: BrowserConsole: Uncaught TypeError: Cannot read property 'OnLogEvent' of undefined (Source: file:///D:/ACT%20Plugins/OverlayPlugin/cactbot/ui/raidboss/raidboss.js, Line: 47)

and then it just mostly repeats the line 531 error multiple times a second.

Is this still a problem with the latest update?

Yeah I still have the errors coming through but there are some different lines it has issues with.
24/08/2019 07:41:37: Info: Raid-Cactbot: BrowserConsole: Uncaught SyntaxError: Unexpected token : (Source: file:///D:/ACT%20Plugins/OverlayPlugin/cactbot/ui/raidboss/raidboss.html, Line: 3)
24/08/2019 07:41:40: Info: Raid-Cactbot: BrowserConsole: Uncaught TypeError: Cannot read property 'OnDataFilesRead' of undefined (Source: file:///D:/ACT%20Plugins/OverlayPlugin/cactbot/ui/raidboss/popup-text.js, Line: 551)
24/08/2019 07:41:40: Info: Raid-Cactbot: BrowserConsole: Uncaught TypeError: Cannot read property 'SetDataFiles' of undefined (Source: file:///D:/ACT%20Plugins/OverlayPlugin/cactbot/ui/raidboss/raidboss.js, Line: 50)
24/08/2019 07:41:40: Info: Raid-Cactbot: BrowserConsole: Uncaught TypeError: Cannot read property 'OnInCombatChange' of undefined (Source: file:///D:/ACT%20Plugins/OverlayPlugin/cactbot/ui/raidboss/popup-text.js, Line: 545)
24/08/2019 07:41:40: Info: Raid-Cactbot: BrowserConsole: Uncaught TypeError: Cannot read property 'OnZoneChange' of undefined (Source: file:///D:/ACT%20Plugins/OverlayPlugin/cactbot/ui/raidboss/popup-text.js, Line: 542)
24/08/2019 07:41:40: Info: Raid-Cactbot: BrowserConsole: Uncaught TypeError: Cannot read property 'OnLog' of undefined (Source: file:///D:/ACT%20Plugins/OverlayPlugin/cactbot/ui/raidboss/popup-text.js, Line: 548)
24/08/2019 07:41:40: Info: Raid-Cactbot: BrowserConsole: Uncaught TypeError: Cannot read property 'OnLogEvent' of undefined (Source: file:///D:/ACT%20Plugins/OverlayPlugin/cactbot/ui/raidboss/raidboss.js, Line: 47)
24/08/2019 07:41:46: Info: Raid-Cactbot: BrowserConsole: Uncaught TypeError: Cannot read property 'OnPlayerChange' of undefined (Source: file:///D:/ACT%20Plugins/OverlayPlugin/cactbot/ui/raidboss/popup-text.js, Line: 539)
24/08/2019 07:41:46: Info: Raid-Cactbot: BrowserConsole: Uncaught TypeError: Cannot read property 'OnLog' of undefined (Source: file:///D:/ACT%20Plugins/OverlayPlugin/cactbot/ui/raidboss/popup-text.js, Line: 548)
24/08/2019 07:41:46: Info: Raid-Cactbot: BrowserConsole: Uncaught TypeError: Cannot read property 'OnLogEvent' of undefined (Source: file:///D:/ACT%20Plugins/OverlayPlugin/cactbot/ui/raidboss/raidboss.js, Line: 47)
24/08/2019 07:41:56: Info: Raid-Cactbot: BrowserConsole: Uncaught TypeError: Cannot read property 'OnZoneChange' of undefined (Source: file:///D:/ACT%20Plugins/OverlayPlugin/cactbot/ui/raidboss/popup-text.js, Line: 542)
24/08/2019 07:41:56: Info: Raid-Cactbot: BrowserConsole: Uncaught TypeError: Cannot read property 'OnLog' of undefined (Source: file:///D:/ACT%20Plugins/OverlayPlugin/cactbot/ui/raidboss/popup-text.js, Line: 548)

and then it just repeats line 47 & 548.

The first line of Error messages tells you there is an Unexpected token : (a colon)
Did you check the raidboss.html? Is there a : that is not supposed to be there?
It should look like this:
<html>
<head>
  <meta charset="utf-8" />
  <title></title>
  <link rel="stylesheet" href="../../resources/defaults.css">
  <link rel="stylesheet" href="../../resources/resize_handle.css">

Click on show devtools in ACT and go to the Console tab.
You should find your error message here. Go to the first one and click on the source at the end of this first error message.  You should be redirected to the cause of your error.
Did you ever modify your raidboss.html?

I have not modified it at all. I overwrite all files when updating.
Line 3 of my raidboss.html is just the same as yours.

are you using custom triggers?

This looks similar to #430.  I think the cause of this is just a startup race where the plugin starts sending messages before the overlay is ready for it (but theoretically this should never happen because messages aren't sent until the overlay notifies the c# plugin).
I've tried to track this down some, but have been unable to figure out what's going on because this never happens for me locally.  The best thing I can recommend at the moment is if you see these errors to just reload the overlay that's complaining or to restart act.  I'm sorry I don't have a better answer for you.

I've seen this issue or at least similar errors while experimenting if UserConfig.getUserConfigLocation takes too long or just fails. In the case of Raidboss, the event handlers are already set up and try to call a method on an undefined value (since gTimelineController was never set).
The Unexpected token : message probably comes from the injected JavaScript. Since it's never executed, the onOverlayInitialized event is never fired and thus gTimelineController is never created.
@VaporMoon Do you have anything (except the example files) in your user folder?
The gLang.countdownEngageRegex issue mentioned in the other issue happens whenever
onOverlayInitialized was processed correctly but onPlayerChangedEvent wasn't or arrived before getUserConfigLocation finished.

I don't have any custom triggers. I do have raidboss.js file to change the pull timer sound which contains only
'use strict';

Options.PullSound: '../../resources/sounds/Overwatch/Reaper_-_Die_die_die.ogg';

and now today whenever I go to the OverlayPlugin.dll tab in ACT I now get unhandled exceptions errors. I didn't change anything since updating yesterday and I didn't get the errors then.
I will reinstall ACT and Cactbot and see what happens.

Uh, that's exactly where the syntax error is. That line should look like this:
Options.PullSound = '../../resources/sounds/Overwatch/Reaper_-_Die_die_die.ogg';
Change that and it should work again.

Thanks for solving this!