Resolve syncing conflicts from master-sync-work to master

Pull request opened by OPS to resolve syncing conflicts from master-sync-work to master.

:x: Validation status: errors
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/csharp/programming-guide/exceptions/how-to-execute-cleanup-code-using-finally.md
:white_check_mark:Succeeded
View

docs/csharp/programming-guide/exceptions/how-to-handle-an-exception-using-try-catch.md
:white_check_mark:Succeeded
View

docs/csharp/programming-guide/exceptions/index.md
:white_check_mark:Succeeded
View

docs/csharp/programming-guide/exceptions/using-exceptions.md
:white_check_mark:Succeeded
View

docs/csharp/programming-guide/file-system/how-to-copy-delete-and-move-files-and-folders.md
:white_check_mark:Succeeded
View

docs/csharp/programming-guide/file-system/how-to-create-a-file-or-folder.md
:white_check_mark:Succeeded
View

docs/csharp/programming-guide/file-system/how-to-create-a-key-in-the-registry.md
:white_check_mark:Succeeded
View

docs/csharp/programming-guide/file-system/how-to-get-information-about-files-folders-and-drives.md
:white_check_mark:Succeeded
View

docs/csharp/programming-guide/file-system/how-to-iterate-through-a-directory-tree.md
:white_check_mark:Succeeded
View

docs/csharp/programming-guide/file-system/how-to-provide-a-progress-dialog-box-for-file-operations.md
:white_check_mark:Succeeded
View

docs/csharp/programming-guide/file-system/how-to-read-a-text-file-one-line-at-a-time.md
:white_check_mark:Succeeded
View

docs/csharp/programming-guide/file-system/how-to-read-from-a-text-file.md
:white_check_mark:Succeeded
View

docs/csharp/programming-guide/file-system/how-to-write-to-a-text-file.md
:white_check_mark:Succeeded
View

docs/csharp/programming-guide/file-system/index.md
:white_check_mark:Succeeded
View

docs/csharp/programming-guide/inside-a-program/hello-world-your-first-program.md
:white_check_mark:Succeeded
View

docs/csharp/programming-guide/interop/example-com-class.md
:white_check_mark:Succeeded
View

docs/csharp/programming-guide/interop/index.md
:white_check_mark:Succeeded
View

docs/csharp/programming-guide/interop/interoperability.md
:white_check_mark:Succeeded
View

docs/csharp/programming-guide/interop/walkthrough-office-programming.md
:white_check_mark:Succeeded
View

docs/csharp/programming-guide/main-and-command-args/command-line-arguments.md
:white_check_mark:Succeeded
View

docs/csharp/programming-guide/main-and-command-args/how-to-access-command-line-arguments-using-foreach.md
:white_check_mark:Succeeded
View

docs/csharp/programming-guide/main-and-command-args/how-to-display-command-line-arguments.md
:white_check_mark:Succeeded
View

docs/csharp/programming-guide/main-and-command-args/index.md
:white_check_mark:Succeeded
View

docs/csharp/programming-guide/main-and-command-args/main-and-command-line-arguments.md
:white_check_mark:Succeeded
View

docs/csharp/programming-guide/main-and-command-args/main-return-values.md
:white_check_mark:Succeeded
View

docs/csharp/misc/cs1558.md
:white_check_mark:Succeeded
View

docs/csharp/misc/cs1559.md
:white_check_mark:Succeeded
View

docs/csharp/misc/cs5001.md
:white_check_mark:Succeeded
View

docs/csharp/programming-guide/index.md
:white_check_mark:Succeeded
View

docs/csharp/programming-guide/classes-and-structs/methods.md
:white_check_mark:Succeeded
View

docs/csharp/programming-guide/concepts/index.md
:white_check_mark:Succeeded
View

docs/csharp/programming-guide/concepts/async/async-return-types.md
:white_check_mark:Succeeded
View

docs/csharp/programming-guide/concepts/async/asynchronous-programming-with-async-and-await.md
:white_check_mark:Succeeded
View

docs/csharp/programming-guide/concepts/async/cancel-an-async-task-or-a-list-of-tasks.md
:white_check_mark:Succeeded
View

docs/csharp/programming-guide/concepts/async/cancel-async-tasks-after-a-period-of-time.md
:white_check_mark:Succeeded
View

docs/csharp/programming-guide/concepts/async/cancel-remaining-async-tasks-after-one-is-complete.md
:white_check_mark:Succeeded
View

docs/csharp/programming-guide/concepts/async/control-flow-in-async-programs.md
:white_check_mark:Succeeded
View

docs/csharp/programming-guide/concepts/async/fine-tuning-your-async-application.md
:white_check_mark:Succeeded
View

docs/csharp/programming-guide/concepts/async/handling-reentrancy-in-async-apps.md
:white_check_mark:Succeeded
View

docs/csharp/programming-guide/concepts/async/how-to-make-multiple-web-requests-in-parallel-by-using-async-and-await.md
:white_check_mark:Succeeded
View

docs/csharp/programming-guide/concepts/async/index.md
:white_check_mark:Succeeded
View

docs/csharp/programming-guide/concepts/async/start-multiple-async-tasks-and-process-them-as-they-complete.md
:white_check_mark:Succeeded
View

docs/csharp/programming-guide/concepts/async/using-async-for-file-access.md
:white_check_mark:Succeeded
View

docs/csharp/programming-guide/concepts/async/walkthrough-accessing-the-web-by-using-async-and-await.md
:white_check_mark:Succeeded
View

docs/visual-basic/language-reference/modifiers/assembly.md
:white_check_mark:Succeeded
View

docs/visual-basic/language-reference/modifiers/module-keyword.md
:white_check_mark:Succeeded
View

docs/csharp/programming-guide/statements-expressions-operators/lambda-expressions.md
:white_check_mark:Succeeded
View

docs/csharp/programming-guide/statements-expressions-operators/statements.md
:white_check_mark:Succeeded
View

docs/csharp/programming-guide/types/index.md
:white_check_mark:Succeeded
View

docs/csharp/programming-guide/unsafe-code-pointers/fixed-size-buffers.md
:white_check_mark:Succeeded
View

This comment lists only the first 50 files in the pull request.
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/csharp/misc/cs0255.md
:white_check_mark:Succeeded
View

docs/fsharp/using-fsharp-on-azure/blob-storage.md
:white_check_mark:Succeeded
View

docs/csharp/programming-guide/classes-and-structs/methods.md
:white_check_mark:Succeeded
View

docs/csharp/misc/cs0155.md
:white_check_mark:Succeeded
View

docs/csharp/misc/cs0156.md
:white_check_mark:Succeeded
View

docs/csharp/misc/cs0157.md
:white_check_mark:Succeeded
View

docs/csharp/misc/cs0160.md
:white_check_mark:Succeeded
View

docs/csharp/programming-guide/inside-a-program/hello-world-your-first-program.md
:white_check_mark:Succeeded
View

docs/csharp/programming-guide/interop/example-com-class.md
:white_check_mark:Succeeded
View

docs/csharp/programming-guide/interop/index.md
:white_check_mark:Succeeded
View

docs/csharp/programming-guide/interop/interoperability.md
:white_check_mark:Succeeded
View

docs/csharp/programming-guide/interop/walkthrough-office-programming.md
:white_check_mark:Succeeded
View

docs/samples-and-tutorials/index.md
:white_check_mark:Succeeded
View

docs/standard/managed-code.md
:white_check_mark:Succeeded
View

docs/standard/native-interop.md
:white_check_mark:Succeeded
View

docs/standard/base-types/composite-format.md
:white_check_mark:Succeeded
View

docs/visual-basic/programming-guide/language-features/statements.md
:white_check_mark:Succeeded
View

docs/fsharp/tutorials/getting-started/getting-started-vscode.md
:white_check_mark:Succeeded
View

docs/csharp/language-reference/compiler-options/target-winmdobj-compiler-option.md
:white_check_mark:Succeeded
View

docs/csharp/language-reference/keywords/try-catch.md
:white_check_mark:Succeeded
View

docs/visual-basic/language-reference/error-messages/extension-attribute-can-be-applied-only-to-module-sub-or-function-declarations.md
:white_check_mark:Succeeded
View

docs/visual-basic/language-reference/error-messages/first-statement-of-sub-new-must-be-explicit-call-to-mybase-new-or-myclass-new.md
:white_check_mark:Succeeded
View

docs/visual-basic/language-reference/error-messages/identifier-expected.md
:white_check_mark:Succeeded
View

docs/csharp/programming-guide/xmldoc/exception.md
:white_check_mark:Succeeded
View

docs/visual-basic/programming-guide/language-features/procedures/extension-methods.md
:white_check_mark:Succeeded
View

docs/csharp/programming-guide/concepts/async/handling-reentrancy-in-async-apps.md
:white_check_mark:Succeeded
View

docs/csharp/programming-guide/concepts/async/how-to-make-multiple-web-requests-in-parallel-by-using-async-and-await.md
:white_check_mark:Succeeded
View

docs/csharp/programming-guide/concepts/async/index.md
:white_check_mark:Succeeded
View

docs/csharp/programming-guide/concepts/async/start-multiple-async-tasks-and-process-them-as-they-complete.md
:white_check_mark:Succeeded
View

docs/csharp/programming-guide/concepts/async/using-async-for-file-access.md
:white_check_mark:Succeeded
View

docs/csharp/programming-guide/concepts/async/walkthrough-accessing-the-web-by-using-async-and-await.md
:white_check_mark:Succeeded
View

docs/visual-basic/language-reference/statements/parameter-list.md
:white_check_mark:Succeeded
View

docs/visual-basic/language-reference/error-messages/elementname-is-obsolete-visual-basic-warning.md
:white_check_mark:Succeeded
View

docs/csharp/programming-guide/exceptions/compiler-generated-exceptions.md
:white_check_mark:Succeeded
View

docs/csharp/programming-guide/exceptions/creating-and-throwing-exceptions.md
:white_check_mark:Succeeded
View

docs/csharp/programming-guide/exceptions/exception-handling.md
:white_check_mark:Succeeded
View

docs/csharp/programming-guide/exceptions/exceptions-and-exception-handling.md
:white_check_mark:Succeeded
View

docs/csharp/programming-guide/exceptions/how-to-catch-a-non-cls-exception.md
:white_check_mark:Succeeded
View

docs/csharp/programming-guide/exceptions/how-to-execute-cleanup-code-using-finally.md
:white_check_mark:Succeeded
View

docs/csharp/programming-guide/exceptions/how-to-handle-an-exception-using-try-catch.md
:white_check_mark:Succeeded
View

docs/csharp/programming-guide/exceptions/index.md
:white_check_mark:Succeeded
View

docs/csharp/programming-guide/exceptions/using-exceptions.md
:white_check_mark:Succeeded
View

docs/csharp/programming-guide/file-system/how-to-copy-delete-and-move-files-and-folders.md
:white_check_mark:Succeeded
View

docs/csharp/programming-guide/file-system/how-to-create-a-file-or-folder.md
:white_check_mark:Succeeded
View

docs/csharp/programming-guide/file-system/how-to-create-a-key-in-the-registry.md
:white_check_mark:Succeeded
View

docs/csharp/programming-guide/file-system/how-to-get-information-about-files-folders-and-drives.md
:white_check_mark:Succeeded
View

docs/csharp/programming-guide/file-system/how-to-iterate-through-a-directory-tree.md
:white_check_mark:Succeeded
View

docs/csharp/programming-guide/file-system/how-to-provide-a-progress-dialog-box-for-file-operations.md
:white_check_mark:Succeeded
View

docs/csharp/programming-guide/file-system/how-to-read-a-text-file-one-line-at-a-time.md
:white_check_mark:Succeeded
View

docs/csharp/programming-guide/file-system/how-to-read-from-a-text-file.md
:white_check_mark:Succeeded
View

This comment lists only the first 50 files in the pull request.
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Shows HTML markup in message for registering an account that already exists

After pushing submit, says:
Account already exists! You may go ahead and login.

I fixed the bug and test with LOCAL user already. It looks like this now when you try to register the same user twice:

Basically I:

remove the html tag from Messages.properties file
insert the html tag again with jQuery code in eureka.registration.js file
Nothing change on JSP page and Servlet page
If you think the UI looks good, I will pull a request.


Upgrade storage pallet

[ ] Fixed renew price
[ ] Use formulas to convert storage space into power
[ ] Unexpected file deletion penalty

Not ready


Output to stderr

Is there a way to output text to stderr stream in windows? While gawk (EZWinPorts windows version) handles output to /dev/stderr, goawk fails
[C:\temp]:# echo test | goawk "{print $0 > '/dev/stderr' }"
output redirection error: open /dev/stderr: El sistema no puede encontrar la ruta especificada.

[C:\temp]:# echo test | gawk "{print $0 > \"/dev/stderr\" }"
test

Interesting -- that Gawk port must have a special-case handling for /dev/stderr on Windows, because otherwise I'm not sure how that would work. I'm not sure I want to add special cases like this to GoAWK.
One idea I had for a workaround was using type (the Windows equivalent of cat) with "redirect stdout to stderr" operators, like this:
C:\> echo test | goawk "{print $0 > 'type 1>&2' }"

Would that work? (I don't have handy access to a Windows machine.)

Thank you, no, type commnand in windows is an cmd internal command that does not read from stdin. Even if it could work (more is a suitable command for this task), the structure of the command implies the creation of a separate process for each line being written, something that is a expensive task in windows.
Output to stderr is a usual operation in awk scripts. To use it in windows we need a way to reference this stream, if not by adding a special case handling for the /dev/stderr stream, maybe enabling an alternate way to reference the stderr stream.

the structure of the command implies the creation of a separate process for each line being written, something that is a expensive task in windows.

Yes, that's true if you did it using >. However, if you pipe it using |, a single process will be started and the command will stay running as it converts output from stdout to stderr. But yeah, that won't work if type does not read from stdin. You might be able to use findstr, or perhaps Get-Content if you're using Powershell.
But I'll keep this open to think further about adding /dev/stderr support on Windows.

Dear @benhoyt, whatever you do, please refrain from using @golang 1.21 to compile goawk because those traitors have stopped supporting Windows 7. It would be ridiculous if the awk port for Windows continues to work and your tool stops working.

Hi @sergeevabc, I'm afraid that ship has passed, as v1.25.0 is built with Go 1.21 (in general, I use the latest version to build, so I'm probably going to build the next version with Go 1.22). However, two things:

It's easy to download the source and build yourself with Go 1.20. Just git clone it and then type go build (with Go 1.20 installed).
I'm not opposed to a change to scripts/make_binaries.sh (which is what I use for building the release binaries) that builds 32- and 64-bit versions for Windows 7 as well. It should probably use go1.20.13 (the latest 1.20.x release) to do so. If you'd like that, please put up a PR.

Alternatively, you can keep using goawk v1.24.0, which is built with Go 1.20.6, so should work fine on Windows 7.

@benhoyt, goawk 1.25 works fine on my end, hmm. Apparently, I was misled about the compilation peculiarities after Golang's press release on dropping Windows 7 support. Anyway, remember there are such users here and there is not a single feature in awk that requires a new OS. It is not for Microsoft to decide what is outdated and what is not. Good hammer continues to hammer nails even when the factory is closed — a good hammer continues to hammer nails even when the factory that produced it has ceased to exist.

@naalmlqpele Sorry for the delay. Does https://github.com/benhoyt/goawk/pull/225 work for you on Windows? It seems to work fine on Windows in CI, but I don't actually have a Windows machine handy to test it more thoroughly.

@benhoyt Trying to compile in windows to test it, but I get redeclared errors in several blocks. Is there any place from where to get the binary with the changes included to test?

Here's a GOOS=windows GOARCH=amd64 go build -ldflags="-w" build of this branch:
goawk-devstderr-windows-amd64.zip

@benhoyt , thank you for the build. Tested against multiple existing gnu awk scripts and several at hoc tests and working fine as expected without any problem. This includes outputs to stderr from print and printf, with and without ANSI escape sequences, with and without redirection to a file.
Any additional test you could think of, please, tell me.

No, that's good enough for me -- thanks! I've merged #225.

1.26.0 works fine on Windows 7, 1.27.0 throws an error as follows
$ goawk127.exe

Exception 0xc0000005 0x8 0x0 0x0
PC=0x0

runtime.asmstdcall(0xc0)
        /home/ben/sdk/go1.22.2/src/runtime/sys_windows_amd64.s:75 +0x7a fp=0x22fc80 sp=0x22fc60 pc=0x47621a
rax     0x0
rbx     0x6e90d8
rcx     0x76f7c8
rdx     0x20
rdi     0x7fffffdd000
rsi     0x22fe78
rbp     0x22fdc0
rsp     0x22fc58
r8      0x0
r9      0x22fee8
r10     0x88a2e8
r11     0xc000004000
r12     0x22fec8
r13     0xc000004008
r14     0x6e8760
r15     0x0
rip     0x0
rflags  0x10293
cs      0x33
fs      0x53
gs      0x2b

@sergeevabc I build the released GoAWK binaries using the latest version of Go (Go 1.22 for GoAWK 1.27.0). The binaries are provided as a help to most folks, but it's easy to build yourself from source using Go 1.20 (which is the last version that fully officially supports Windows 7).

@benhoyt There is a way to provide Windows 7 compatible builds via Github as @schollz did with his Croc.


Proxy sometimes hangs when request is disrupted

We have a single-page-app with several proxies as we migrate off of rails, and we've found that sometimes, when a request hasn't completed (whether it's a proxied request or not, i think) and we make a new request (either by refreshing the page or, say, clicking another part of the page and triggering a new request), the proxy hangs, and we have to restart our server.  On a refresh, we see all locally served files, but requests to a proxied server hang without a response.  We're running proxy-middleware within browsersync, all within gulp.
If you have any insights about why this might happen, I'm happy to take a look and give a crack at it, but I figured I should post an issue about it to get some feedback first.
Thanks!

+1 to this. I'm using a 60-second long-polling interval from the client code to connect-proxy, and then to the backend. When I'm in rapid development and reloading often, these requests seem to get 'stuck' in the queue. No further requests are proxied until the one that's stuck is returned. I have to kill and restart the proxy server

@dshefchik what's your stack look like?

@noahgrant
node: 0.10.28,
gulp-webserver: 0.9.0,
gulp: 3.8.11
OSX 10.10.2

+1

I have also run into hanging issues with the proxy until restart - using Ionic Framework and livereload.   It would consistently fail after 5 reloads - For my case what is happening is that after 5 tries the http_agent_maxsockets limit is kicking in and further attempts block.  Have yet to be able to trackdown the root cause of why the http keep-alive sockets are not getting reused/blocking.
As a quick workaround I turned off keep-alive connection-pooling and no longer have hang ups.
  var opts = url.parse(proxy.proxyUrl);

  //opt out of the pooling
  opts.agent = false;
  app.use('/path/', proxy(opts));

thanks @mur-dog. I'm not sure setting opts.agent to false works for me, because the options headers get set to the request headers, so the request is sent with both agent: false as well as connection: keep-alive (the default connection header). For me, that made the response headers have connection: keep-alive.  setting, in your example:
opts = url.parse(proxy.proxyUrl);
opts.headers = {
   connection: 'close'
};

made the response headers give a connection: close.  This might hopefully be a workaround, but still doesn't solve the hanging issue :-/


Make it possible to break on breakpoints set in tangram cpp code.

When an android studio module (e.g. tangram-es/demo) is calling into a shared lib built by another one (e.g. tangram-es/tangram), it needs to declare the location of the shared lib for breakpoints to work in native code.
Here is a way to make it work, based on example found there 👍 https://github.com/googlesamples/android-ndk/tree/master/hello-libs
Note : this really is something that needs to be added in the build.gradle of any module integrating tangram.
Ideally Android Studio would have a way to just resolve native deps in a way that would make this redundant but it's not the case in the current version.
A twist on that change that could be considered cleaner is to set a proper LIBRARY_OUTPUT_DIRECTORY to hide the gory specifics of the internal build path by defining a proper distribution_dir :
set_target_properties(tangram                       PROPERTIES                       LIBRARY_OUTPUT_DIRECTORY "${distribution_DIR}/lib/${ANDROID_ABI}")
I did not include that in the present PR as it's a little more invasive (would require change in android.cmake).
Let me know what you think.

Hi Guillaume, thanks for the suggestion! I'll give this a try over the next few days and see if we can integrate it.

I believe that with the latest version of Android Studio one should be able to set and break on breakpoints in native code in 'libtangram' using the current master branch without any changes, at least that's the case when I try it - let me know if that's not true for you.
After looking closely at the NDK sample project you've linked, I think it is meant as an example for using native libraries from native code in your app itself. We're currently focused on the Java interface for our Android library and currently there aren't any plans for supporting a native interface on Android, so I don't think the recommendations in that sample apply for our exact situation.

It would also make more sense to me if Android Studio was able to debug seamlessly accross module boundaries but I am currently using both Android Studio 2.2 and 2.3 Beta 1 and that PR is the only way I managed to break in c++ code when I have some native code in a library module (e.g. tangram) and not directly in the app module (e.g. demo).

Within the context of a single module bundling the app and jni/cpp code I have observed that breaking in cpp code just works.
In the dual module setup I have since observed that outputting the libtangram.so in src/main/jniLibs makes breakpoint work without having to change anything in the build.gradle of dependant module, so it's nicer.

Anyway, feel free to ignore that PR.
As a side note, I have been pushing some of what's currently in the android java layer to the native side so I can leverage the c++ nature of tangram-es and maximise the amount of code reuse accross iOS and Android.
I have been using djinni (https://github.com/dropbox/djinni) to handle the JNI boiler plate and it's working quite nicely.
I understand it's not your focus right now but let me know if at some point that becomes PR material.


In the UI, when you click the refresh all button you are able to press it again right after

After clicking the refresh button, it should be invalid until the refresh has finished.

Change the button from a div with a link to an actual button, so that we can use ng-disabled when refreshingContainer is true.


Shaping nested objects in the query

Heya folks, thanks for making an awesome abstraction :)
I can't find any info or examples about shaping nested objects during a query.
For example, I've borrowed the query from our Arcade and edited it so that it contains an object at invented property stats, and then I assign values to it by providing every field's path explicitly - "attack": ["base.Attack", q.number()]
  q("*").filterByType("pokemon")
  .grab({
    name: q.string(),
    "stats": q.object({
      "attack": ["base.Attack", q.number()],
      "name-again": ["name", q.string()],
    }),
  })

Obviously, this doesn't work :D so, what am I missing?

The answer was fairly simple actually! We should probably add it to the docs somewhere. I can open a PR?
  q("*").filterByType("pokemon")
  .grab({
    name: q.string(),
    "stats": q("base")({
      "attack": ["Attack", q.number()],
    }),
  })

The only remaining question would be if i could somehow map fields that are outside of "base" into the new "stats". Any ideas?

Yes, you can do it with an empty "q" like this:
  q("*").filterByType("pokemon")
  .grab({
    name: q.string(),
    stats: q("").grab({
      "attack": ["base.Attack", q.number()],
      "name-again": ["name", q.string()],
    }),
  })


Re-encode KTX2s to have mipmaps, fix mipmap loading order

Description
This branch re-encodes all KTX2s used in the Bonza scene so that they have mipmaps, plus a higher level of quality for ASTC compression. It also fixes the loading order for mipmap levels, which is flipped in KTX2 vs. KTX1 (in KTX1, smaller mipmaps come last; in KTX2, they come first).
General Checklist:
Please ensure the following points are checked:

[x] My code follows the coding style
[x] I have reviewed file licenses
[x] I have updated the header Copyright to reflect the current year (CI build will fail if Copyright is out of date)
[x] I have commented any added functions (in line with Doxygen)
[x] I have commented any code that could be hard to understand
[x] My changes do not add any new compiler warnings
[x] My changes do not add any new validation layer errors or warnings
[x] I have used existing framework/helper functions where possible
[-] My changes build on Windows, Linux, macOS and Android. Otherwise I have documented any exceptions
[x] My changes do not add any regressions
[x] I have tested every sample to ensure everything runs correctly
[x] This PR describes the scope and expected impact of the changes I am making

LGTM, but one question: This does change assets, so shouldn't the asset part be a PR against the asset repo?

LGTM, but one question: This does change assets, so shouldn't the asset part be a PR against the asset repo?

thanks! that's right, this should be merged together with https://github.com/KhronosGroup/Vulkan-Samples-Assets/pull/16


Add support for CDDO SSO

What problem does the pull request solve?
Trello card: https://trello.com/c/75nMIWFC
We want to be able to test https://sso.service.security.gov.uk as a authentication provider for users.
This PR adds support using the OmniAuth strategy omniauth_openid_connect, which integrates OmniAuth with the openid_connect gem. We then integrate this strategy with our own Warden/OmniAuth framework.

As part of this PR I need to write up why I think it's okay to add these two new gems; I'm working on that at the moment.


added year

Docs Build status updates of commit affb040:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

mixed-reality-docs/galaxy-explorer.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Seed VIP: reward_player_message_no_vip is used as VIP name instead of player_name_format_not_current_vip

Example below

Hey ! Thanks for noticing.
This issue has already been fixed (see: https://github.com/MarechJ/hll_rcon_tool/pull/741) in the next release of CRCON !

Thanks!


issues - get issues/PRs by datetime range

tracing of relevant commits can be done through PR commits API, and issues/PRs comments API


Thanos Receive Memory Usage very high OOMKilled

Hi, I've been experiencing a lot of problems with Thanos Receive getting OOMKilled and going into a CrashBackupLoop anytime it tries to restart.
Thanos is deployed via Bitnami Helm Chart on EKS t3.2xlarge VMs (8vCPU 32GB RAM) across 6 nodes, the Thanos Receive deployment is configured in an AutoScaling group from 3-6 nodes and each replicas has 20Gi Memory, set to scale when Memory Usage hits 70%.
Almost instantly, Thanos Receive scales out to 6 pods and shortly after begins a CrashBackupLoop of OOMKilled for the termination reason.
k top pod -n thanos
NAME                                     CPU(cores)   MEMORY(bytes)
thanos-query-5445b5dc6d-lrqnq            1m           13Mi
thanos-query-5445b5dc6d-m65fr            1m           14Mi
thanos-query-5445b5dc6d-wqc9k            1m           14Mi
thanos-query-frontend-55d897f4dc-4fndg   1m           49Mi
thanos-receive-0                         94m          17907Mi
thanos-receive-1                         167m         17903Mi
thanos-receive-2                         501m         4667Mi
thanos-receive-3                         500m         3830Mi
thanos-receive-4                         84m          15356Mi
thanos-receive-5                         69m          13076Mi
thanos-storegateway-0                    1m           124Mi
thanos-storegateway-1                    4m           96Mi
thanos-storegateway-2                    1m           123Mi
k get pod thanos-receive-0 -o yaml
 containerStatuses:
  - containerID: containerd://fbcb35fa7b97ee38ab4ff480d4da33ab207d934d9f226fb3f3f74b8c580bbaf1
    image: docker.io/bitnami/thanos:0.29.0-scratch-r0
    imageID: docker.io/bitnami/thanos@sha256:e239696f575f201cd7f801e80945964fda3f731cd62be70772f88480bb428fcd
    lastState:
      terminated:
        containerID: containerd://10cc94abc68bc71a0fb6b59c762a25d3a9ba6521cbb684a511be47e77b3e9ecb
        exitCode: 137
        finishedAt: "2023-02-03T03:02:47Z"
        reason: OOMKilled
        startedAt: "2023-02-03T02:58:42Z"

In addition, when scraping pod metrics from OTEL Collector and sending to Thanos Receive, after Thanos Receive scales up to 6 nodes, the logs show issues with the TSDB not being ready which seems to occur as a result of the OOMKilled as well.
OTEL Collector
me": "prometheusremotewrite", "error": "Permanent error: remote write returned HTTP status 500 Internal Server Error; err = %!w(<nil>): store locally for endpoint <IP_ADDRESS>:10901: get appender: TSDB not ready\n", "dropped_items": 407}
go.opentelemetry.io/collector/exporter/exporterhelper.(*retrySender).send
	go.opentelemetry.io/collector@v0.66.0/exporter/exporterhelper/queued_retry.go:394
go.opentelemetry.io/collector/exporter/exporterhelper.(*metricsSenderWithObservability).send
	go.opentelemetry.io/collector@v0.66.0/exporter/exporterhelper/metrics.go:135
go.opentelemetry.io/collector/exporter/exporterhelper.(*queuedRetrySender).start.func1
	go.opentelemetry.io/collector@v0.66.0/exporter/exporterhelper/queued_retry.go:205
go.opentelemetry.io/collector/exporter/exporterhelper/internal.(*boundedMemoryQueue).StartConsumers.func1
	go.opentelemetry.io/collector@v0.66.0/exporter/exporterhelper/internal/bounded_memory_queue.go:61
2023-02-03T03:09:54.328Z	error	exporterhelper/queued_retry.go:394	Exporting failed. The error is not retryable. Dropping data.	{"kind": "exporter", "data_type": "metrics", "name": "prometheusremotewrite", "error": "Permanent error: remote write returned HTTP status 502 Bad Gateway; err = %!w(<nil>): \r\n<title>502 Bad Gateway</title>\r\n\r\n
502 Bad Gateway
\r\n\r\n\r\n", "dropped_items": 414}
go.opentelemetry.io/collector/exporter/exporterhelper.(*retrySender).send
	go.opentelemetry.io/collector@v0.66.0/exporter/exporterhelper/queued_retry.go:394
go.opentelemetry.io/collector/exporter/exporterhelper.(*metricsSenderWithObservability).send
	go.opentelemetry.io/collector@v0.66.0/exporter/exporterhelper/metrics.go:135
go.opentelemetry.io/collector/exporter/exporterhelper.(*queuedRetrySender).start.func1
	go.opentelemetry.io/collector@v0.66.0/exporter/exporterhelper/queued_retry.go:205
go.opentelemetry.io/collector/exporter/exporterhelper/internal.(*boundedMemoryQueue).StartConsumers.func1
	go.opentelemetry.io/collector@v0.66.0/exporter/exporterhelper/internal/bounded_memory_queue.go:61

Thanos Receive
level=debug ts=2023-02-03T03:10:29.706596677Z caller=main.go:67 msg="maxprocs: Updating GOMAXPROCS=[1]: using minimum allowed GOMAXPROCS"
level=info ts=2023-02-03T03:10:29.707099181Z caller=receive.go:125 component=receive mode=RouterIngestor msg="running receive"
level=info ts=2023-02-03T03:10:29.707127419Z caller=options.go:26 component=receive protocol=HTTP msg="disabled TLS, key and cert must be set to enable"
level=info ts=2023-02-03T03:10:29.707179527Z caller=factory.go:52 component=receive msg="loading bucket configuration"
level=info ts=2023-02-03T03:10:29.707534281Z caller=receive.go:702 component=receive msg="default tenant data dir already present, not attempting to migrate storage"
level=debug ts=2023-02-03T03:10:29.708346939Z caller=receive.go:264 component=receive msg="setting up TSDB"
level=debug ts=2023-02-03T03:10:29.708380296Z caller=receive.go:551 component=receive msg="removing storage lock files if any"
level=info ts=2023-02-03T03:10:29.711845832Z caller=multitsdb.go:415 component=receive component=multi-tsdb msg="a leftover lockfile found and removed" tenant=default-tenant
level=info ts=2023-02-03T03:10:29.711894552Z caller=receive.go:638 component=receive component=uploader msg="upload enabled, starting initial sync"
level=debug ts=2023-02-03T03:10:29.71190348Z caller=receive.go:626 component=receive component=uploader msg="upload phase starting"
level=debug ts=2023-02-03T03:10:29.711913101Z caller=receive.go:634 component=receive component=uploader msg="upload phase done" uploaded=0 elapsed=2.672µs
level=info ts=2023-02-03T03:10:29.711940043Z caller=receive.go:642 component=receive component=uploader msg="initial sync done"
level=debug ts=2023-02-03T03:10:29.711954049Z caller=receive.go:272 component=receive msg="setting up hashring"
level=debug ts=2023-02-03T03:10:29.712128372Z caller=receive.go:279 component=receive msg="setting up HTTP server"
level=debug ts=2023-02-03T03:10:29.71215783Z caller=receive.go:297 component=receive msg="setting up gRPC server"
level=info ts=2023-02-03T03:10:29.712170937Z caller=options.go:26 component=receive protocol=gRPC msg="disabled TLS, key and cert must be set to enable"
level=debug ts=2023-02-03T03:10:29.712567297Z caller=receive.go:362 component=receive msg="setting up receive HTTP handler"
level=debug ts=2023-02-03T03:10:29.712588469Z caller=receive.go:391 component=receive msg="setting up periodic tenant pruning"
level=info ts=2023-02-03T03:10:29.712603814Z caller=receive.go:422 component=receive msg="starting receiver"
level=info ts=2023-02-03T03:10:29.727142426Z caller=receive.go:460 component=receive msg="the hashring initialized with config watcher."
level=debug ts=2023-02-03T03:10:29.727324029Z caller=config.go:248 component=receive component=config-watcher msg="refreshed hashring config"
level=warn ts=2023-02-03T03:10:29.727358993Z caller=intrumentation.go:67 component=receive msg="changing probe status" status=not-ready reason="hashring has changed; server is not ready to receive requests"
level=info ts=2023-02-03T03:10:29.72738477Z caller=receive.go:597 component=receive msg="hashring has changed; server is not ready to receive requests"
level=info ts=2023-02-03T03:10:29.727391568Z caller=receive.go:599 component=receive msg="updating storage"
level=info ts=2023-02-03T03:10:29.727469101Z caller=multitsdb.go:498 component=receive component=multi-tsdb tenant=default-tenant msg="opening TSDB"
level=info ts=2023-02-03T03:10:29.72778871Z caller=intrumentation.go:75 component=receive msg="changing probe status" status=healthy
level=info ts=2023-02-03T03:10:29.727822311Z caller=http.go:73 component=receive service=http/server component=receive msg="listening for requests and metrics" address=<IP_ADDRESS>:10902
level=info ts=2023-02-03T03:10:29.728156151Z caller=tls_config.go:195 component=receive service=http/server component=receive msg="TLS is disabled." http2=false
level=info ts=2023-02-03T03:10:29.728208198Z caller=receive.go:349 component=receive msg="listening for StoreAPI and WritableStoreAPI gRPC" address=<IP_ADDRESS>:10901
level=info ts=2023-02-03T03:10:29.728241513Z caller=intrumentation.go:75 component=receive msg="changing probe status" status=healthy
level=info ts=2023-02-03T03:10:29.728280285Z caller=grpc.go:131 component=receive service=gRPC/server component=receive msg="listening for serving gRPC" address=<IP_ADDRESS>:10901
level=info ts=2023-02-03T03:10:29.728312044Z caller=handler.go:312 component=receive component=receive-handler msg="Start listening for connections" address=<IP_ADDRESS>:19291
level=info ts=2023-02-03T03:10:29.728407976Z caller=handler.go:339 component=receive component=receive-handler msg="Serving plain HTTP" address=<IP_ADDRESS>:19291
level=info ts=2023-02-03T03:10:29.749651877Z caller=head.go:551 component=receive component=multi-tsdb tenant=default-tenant msg="Replaying on-disk memory mappable chunks if any"
level=info ts=2023-02-03T03:10:29.749698686Z caller=head.go:595 component=receive component=multi-tsdb tenant=default-tenant msg="On-disk memory mappable chunks replay completed" duration=2.079µs
level=info ts=2023-02-03T03:10:29.749707636Z caller=head.go:601 component=receive component=multi-tsdb tenant=default-tenant msg="Replaying WAL, this may take a while"
level=debug ts=2023-02-03T03:10:34.415416434Z caller=handler.go:660 component=receive component=receive-handler msg="local tsdb write failed" err="get appender: TSDB not ready"
level=debug ts=2023-02-03T03:10:34.415521532Z caller=handler.go:660 component=receive component=receive-handler msg="local tsdb write failed" err="get appender: TSDB not ready"
level=debug ts=2023-02-03T03:10:34.415584461Z caller=handler.go:660 component=receive component=receive-handler msg="local tsdb write failed" err="get appender: TSDB not ready"
level=debug ts=2023-02-03T03:10:34.415607355Z caller=handler.go:515 component=receive component=receive-handler tenant=default-tenant msg="failed to handle request" err="store locally for endpoint <IP_ADDRESS>:10901: get appender: TSDB not ready"
level=error ts=2023-02-03T03:10:34.415631376Z caller=handler.go:526 component=receive component=receive-handler tenant=default-tenant err="store locally for endpoint <IP_ADDRESS>:10901: get appender: TSDB not ready" msg="internal server error"
level=debug ts=2023-02-03T03:10:34.415796197Z caller=handler.go:515 component=receive component=receive-handler tenant=default-tenant msg="failed to handle request" err="store locally for endpoint <IP_ADDRESS>:10901: get appender: TSDB not ready"
level=error ts=2023-02-03T03:10:34.415824016Z caller=handler.go:526 component=receive component=receive-handler tenant=default-tenant err="store locally for endpoint <IP_ADDRESS>:10901: get appender: TSDB not ready" msg="internal server error"
level=debug ts=2023-02-03T03:10:34.416297406Z caller=handler.go:515 component=receive component=receive-handler tenant=default-tenant msg="failed to handle request" err="store locally for endpoint <IP_ADDRESS>:10901: get appender: TSDB not ready"

Please find the values.yaml config Thanos Receive using the Bitnami Helm Chart below.
      receive:
        enabled: true
        livenessProbe:
          enabled: false
        readinessProbe:
          enabled: false
        resources:
          limits:
            memory: 18Gi
            cpu: 500m
        autoscaling:
          enabled: true
          minReplicas: 3
          maxReplicas: 6
          targetCPU: 80
          targetMemory: 70
        logLevel: info
        tsdbRetention: 2h
        persistence:
          size: 12Gi
        serviceAccount:
          annotations:
            eks.amazonaws.com/role-arn: arn:aws:iam::some_account_id:role/thanos-receive

Maybe you could try out the newest main version and this https://github.com/thanos-io/thanos/pull/5926 feature flag to see if it helps. What would the results look like?

It is hard to say whether this is a problem without knowing how much data you are sending to receivers.

It is hard to say whether this is a problem without knowing how much data you are sending to receivers. TSDB not being ready is highly unlikely to be the culprit.

We have the OTEL Collector set up as a Daemonset, across 38 nodes (multiple different clusters), collecting metrics from pods, eks nodes and kubeapi, I don't have exact numbers on the volume unfortunately.

It seems that it was related to the amount of data being received, I changed the OTEL Collector deployment from a Daemonset to a Replicaset with 5 nodes and the memory issues seem to have resolved themselves. Thanks for helping :)

That makes sense, thanks for providing the reason 👍


MOBS submission, phase1

hi @LucieContamin,
thanks for the checks. Yes the number of samples is correct.
And yes, each stochastic run is independent. My understanding is that run_grouping will become important in phase 2 in order to group "paired" stochastic runs in different scenarios. Am I correct?

HI @ngozzi ,
Thank you fro the additional information. I just have a minor issue with the file, would it be possible to set the output_type_id column to NA instead of an empty character, please?
Please let me know if any issues or questions,
Best,
Lucie

Hi @LucieContamin,
fixed the file in the last commit.
Thanks!
N

Thank you for the update!


DSU protocol support for Dolphin

Dolphin, a Wii emulator, uses DSU protocol for getting motion and input from compatible applications. This, can be used for motion capabilities of input devices on Dolphin.
The original PSMoveService isn't compatible with this protocol, so we can't use PS Move controllers on Dolphin using it. But also, there are no other way for PS Move which uses DSU protocol. If I know right, PCMoveService can get all information from a PS Move which Dolphin can get from a Wiimote. This means that if implemented, the only problem left would be the button setup. However, if it also supports the Navigation Controller, this can be solved.
If it's possible, can DSU protocol please be added to PSMoveServiceEx?

I know PSMoveService might be bit too overkill, but PSMoveAPI is harder to install, so it might be hard for some people to use. And, it would still need to be implemented, there is no info about it being implemented on PSMoveAPI, especially in it's Github repo(it doesn't even haves a question about it).

The DSU protocol will not be natively implemented into PSMS-EX because it already uses its own protocol.
Feel free to create an extension for PSMS-EX that uses its protocol and translates into DSU instead.

What i understand from what you said is you want to use PSmove controllers (button input and gyro motion data) for other DSU supported apps like Dolphin?

Exactly. They don't support any other protocol.


Add audio adc labview plugin with ac and frequency response measurements

Update README.md, github files and other docs
Add source code of measurements AC and Frequency Response
Add NIPM package build spec for the plugin
Tested the package with the hardware setup with two different DUTs

@jarnoldNI Could you review this PR to merge the commit to the 'NI-MeasurementLink-Plug-Ins : main' branch?

[like]  Srinivasan J reacted to your message:

From: inmeyyav @.>
Sent: Thursday, March 21, 2024 7:55:40 AM
To: NI-MeasurementLink-Plug-Ins/audio-adc-labview @.>
Cc: Srinivasan J @.>; Author @.>
Subject: Re: [NI-MeasurementLink-Plug-Ins/audio-adc-labview] Add audio adc labview plugin with ac and frequency response measurements (PR #1)
You don't often get email from @.*** Learn why this is importanthttps://aka.ms/LearnAboutSenderIdentification
@inmeyyav approved this pull request.
—
Reply to this email directly, view it on GitHubhttps://github.com/NI-MeasurementLink-Plug-Ins/audio-adc-labview/pull/1#pullrequestreview-1951041149, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BFSCXCPYNUNZIEU2CS6PPDDYZKG7ZAVCNFSM6AAAAABD4PGSL2VHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMYTSNJRGA2DCMJUHE.
You are receiving this because you authored the thread.Message ID: @.***>


setElementConverter for HttpSinkRequestEntry is deprecated ,what is alternate method or code we need to use

@Deprecated
@PublicEvolving
public HttpSinkBuilder setElementConverter(ElementConverter<InputT, HttpSinkRequestEntry> elementConverter) {
this.elementConverter = elementConverter;
return this;
}
code :
HttpSink.builder()
.setEndpointUrl("http://example.com/myendpoint")
.setElementConverter(
(s, _context) -> new HttpSinkRequestEntry("POST", s.getBytes(StandardCharsets.UTF_8)))
.setProperty("gid.connector.http.sink.header.X-Content-Type-Options", "nosniff")
.build();

Hi,
thanks for the question. Please use setElementConverter(SchemaLifecycleAwareElementConverter) instead.
SchemaLifecycleAwareElementConverter extends ElementConverter itnerface by adding open method to the API.
The info you are looking for is included in java dock of the deprecated method

I see that README and the examples were not updated... sorry :)

after updating i am getting compilation issue , added dependencies
org.apache.flink.flink-java
org.apache.flink.flink-clients
org.apache.flink.flink-connector-base
can you please suggest

after updating i am getting compilation issue , added dependencies
org.apache.flink.flink-java
org.apache.flink.flink-clients
org.apache.flink.flink-connector-base
can you please suggest

The SchemeLifecycleElementConverter is no longer a functional interface hence you cannot use lambda expression to represent it.
What you can do is implement the interface and pass its instance or use anonymous class like so:
private final SchemaLifecycleAwareElementConverter<String, HttpSinkRequestEntry>
        ELEMENT_CONVERTER_V2 = new SchemaLifecycleAwareElementConverter<>() {
            @Override
            public void open(InitContext context) {
                //noOp
            }

            @Override
            public HttpSinkRequestEntry apply(String element, Context context) {
                return new HttpSinkRequestEntry("POST", element.getBytes(StandardCharsets.UTF_8));
            }
        };

   HttpSink.<String>builder().setElementConverter(ELEMENT_CONVERTER_V2)...

The open method is called when SinkWriter is created.

Thank @kristoffSC for suggestion, i have tried it out getting serialize issue
Caused by: org.apache.flink.streaming.runtime.tasks.StreamTaskException: Could not serialize object for key serializedUDF.

functional interf

found issue
instead implement SchemaLifecycleAwareElementConverter  in same class created new class and call as shown below fixed the issue
public class ElementConverterCustom implements SchemaLifecycleAwareElementConverter<String, HttpSinkRequestEntry>{
@Override
public void open(InitContext context) {
  //noOp
}

@Override
public HttpSinkRequestEntry apply(String element, Context context) {
  return new HttpSinkRequestEntry("GET", element.getBytes(StandardCharsets.UTF_8));
}

}
var httpSink = HttpSink.builder()
.setEndpointUrl("("http://example.com/myendpoint")
.setElementConverter(
new  ElementConverterCustom())
.setSinkHttpClientBuilder(JavaNetSinkHttpClient::new)
.setProperty(
HttpConnectorConfigConstants.SINK_HEADER_PREFIX + "Content-Type",
contentTypeHeader)
.build();

Glad that worked, seems like straight forward Java <-> Flink case :)

instead implement SchemaLifecycleAwareElementConverter in same class

This will work but your "new inner class" must be declared static. If its not static then it holds an reference to the "outer" class which is not serializable.
Also if you use an Anonymous class  this will also work if defined in the same class.
Anyways the options are:

use static class or anonymous class if you wish to define SchemaLifecycleAwareElementConverter as inner class
implement SchemaLifecycleAwareElementConverter on a brand new class.


New Icon

A friend is designing a new icon for this project which will be 42 pixels square and meant to be pixel art in higher resolutions.
The general idea is to make a light bulb that shows the different states of color temperature over the day in one half plus a sun. And for the night the different color temperatures as well (blue hour etc) and stars + moon.
Hope you like the idea @basnijholt

this is now part of the Roadmap for Version 2.
Feel free to vote on the point which will fix this:
https://github.com/basnijholt/adaptive-lighting/discussions/291#discussioncomment-2946825


Widgets can't click by mouse in Windows Terminal

Describe the bug
Button widgets can't click by mouse in Windows Terminal
Screenshots
This is original cmd

This is Windows Terminal

System details (please complete the following information):

OS and version: [Windows 10]
Asciimatics version [1.11.0]

Have you looked at https://asciimatics.readthedocs.io/en/latest/troubleshooting.html#windows

No yet, but now I know. Thanks


Rename master to main

I don't have write permissions on this repo so I can't merge it. Would you merge it for me @AlphaGit ?

This repo has been migrated to use main as the default branch.


Fix: Code is actually reachable

This fixes an reachable unreachable!() statement.
This might not be the approprite fix, although it resulted in no panic
in the code I used to test it, so it seems appropriate as a first idea
for a proper fix.

If you think this is a good first idea, please release it as a patchlevel update (v0.16.1)!
Related to #285 (but there might be a better fix)

Turns out is_hidden must return false for ProgressDrawTarget::Remote because otherwise progress bars won't notify the MultiProgress about their state changes thus deadlocking the program. However, a progress bars notifies a MultiProgress by (among others) sending it's drawn state and to draw this state width is required (for wide_bar and wide_message). MultiProgress just forwards fn width to draw_state.width which actually might be Hidden and actually reaching the 'unreachable' branch. I believe this is the simplest solution to this issue as otherwise we'd need to add a new mechanism that skips drawing when a progress bar's draw target is remote and that remote's target is hidden, which seems relatively complex compared to this one line fix.
MCVE that deadlocks:
use indicatif::{MultiProgress, ProgressDrawTarget, ProgressBar};

fn main() {
    let mpb = MultiProgress::with_draw_target(ProgressDrawTarget::hidden());
    let pb = mpb.add(ProgressBar::new(123));
    pb.finish();
    mpb.join().unwrap();
}

I just published 0.16.1 which contains this fix (along with a few other ones).


Editor crashes when trying to edit a file collection type.

- Do you want to request a feature or report a bug?
bug
- What is the current behavior?
Editor crashes. Message:
Sorry! there's been an error - please report it!
this is printed in console
TypeError: t.get is not a function
Stack trace:
e/<@https://unpkg.com/netlify-cms@%5E1.0.0/dist/cms.js:182:135947
reduce/<@https://unpkg.com/netlify-cms@%5E1.0.0/dist/cms.js:1:50355
Me.prototype.__iterate@https://unpkg.com/netlify-cms@%5E1.0.0/dist/cms.js:1:36979
reduce@https://unpkg.com/netlify-cms@%5E1.0.0/dist/cms.js:1:50309
e@https://unpkg.com/netlify-cms@%5E1.0.0/dist/cms.js:182:135902
e/</<@https://unpkg.com/netlify-cms@%5E1.0.0/dist/cms.js:182:136067
Qe/r.__iterateUncached/<@https://unpkg.com/netlify-cms@%5E1.0.0/dist/cms.js:1:14816
Me.prototype.__iterate@https://unpkg.com/netlify-cms@%5E1.0.0/dist/cms.js:1:36979
Qe/r.__iterateUncached@https://unpkg.com/netlify-cms@%5E1.0.0/dist/cms.js:1:14775
z@https://unpkg.com/netlify-cms@%5E1.0.0/dist/cms.js:1:3696
N.prototype.__iterate@https://unpkg.com/netlify-cms@%5E1.0.0/dist/cms.js:1:23555
toArray@https://unpkg.com/netlify-cms@%5E1.0.0/dist/cms.js:1:47973
Me@https://unpkg.com/netlify-cms@%5E1.0.0/dist/cms.js:1:10243
st@https://unpkg.com/netlify-cms@%5E1.0.0/dist/cms.js:1:19098
map@https://unpkg.com/netlify-cms@%5E1.0.0/dist/cms.js:1:50206
e/<@https://unpkg.com/netlify-cms@%5E1.0.0/dist/cms.js:182:136042
reduce/<@https://unpkg.com/netlify-cms@%5E1.0.0/dist/cms.js:1:50355
Me.prototype.__iterate@https://unpkg.com/netlify-cms@%5E1.0.0/dist/cms.js:1:36979
reduce@https://unpkg.com/netlify-cms@%5E1.0.0/dist/cms.js:1:50309
e@https://unpkg.com/netlify-cms@%5E1.0.0/dist/cms.js:182:135902
value/a<@https://unpkg.com/netlify-cms@%5E1.0.0/dist/cms.js:182:202721
value@https://unpkg.com/netlify-cms@%5E1.0.0/dist/cms.js:182:202700
updateClassInstance@https://unpkg.com/netlify-cms@%5E1.0.0/dist/cms.js:182:281271
beginWork@https://unpkg.com/netlify-cms@%5E1.0.0/dist/cms.js:182:282996
o@https://unpkg.com/netlify-cms@%5E1.0.0/dist/cms.js:182:286941
a@https://unpkg.com/netlify-cms@%5E1.0.0/dist/cms.js:182:287261
l@https://unpkg.com/netlify-cms@%5E1.0.0/dist/cms.js:182:287499
_@https://unpkg.com/netlify-cms@%5E1.0.0/dist/cms.js:182:290830
b@https://unpkg.com/netlify-cms@%5E1.0.0/dist/cms.js:182:290558
h@https://unpkg.com/netlify-cms@%5E1.0.0/dist/cms.js:182:289801
p@https://unpkg.com/netlify-cms@%5E1.0.0/dist/cms.js:182:289211
enqueueSetState@https://unpkg.com/netlify-cms@%5E1.0.0/dist/cms.js:182:279756
o.prototype.setState@https://unpkg.com/netlify-cms@%5E1.0.0/dist/cms.js:182:285
o/</n</r.prototype.handleChange@https://unpkg.com/netlify-cms@%5E1.0.0/dist/cms.js:190:38885
l@https://unpkg.com/netlify-cms@%5E1.0.0/dist/cms.js:36:20198
d/</<@https://unpkg.com/netlify-cms@%5E1.0.0/dist/cms.js:182:3906
e.exports/</<@https://unpkg.com/netlify-cms@%5E1.0.0/dist/cms.js:190:52250
dispatch@https://unpkg.com/netlify-cms@%5E1.0.0/dist/cms.js:36:23493
ee/</<@https://unpkg.com/netlify-cms@%5E1.0.0/dist/cms.js:182:17178
a@https://unpkg.com/netlify-cms@%5E1.0.0/dist/cms.js:190:72320
M/<@https://unpkg.com/netlify-cms@%5E1.0.0/dist/cms.js:190:72442
u@https://unpkg.com/netlify-cms@%5E1.0.0/dist/cms.js:190:75567
 cms.js:182:288777
You tried to return focus to  but it is not in the DOM anymore cms.js:202:152545
TypeError: t.get is not a function
Stack trace:
e/<@https://unpkg.com/netlify-cms@%5E1.0.0/dist/cms.js:182:135947
reduce/<@https://unpkg.com/netlify-cms@%5E1.0.0/dist/cms.js:1:50355
Me.prototype.__iterate@https://unpkg.com/netlify-cms@%5E1.0.0/dist/cms.js:1:36979
reduce@https://unpkg.com/netlify-cms@%5E1.0.0/dist/cms.js:1:50309
e@https://unpkg.com/netlify-cms@%5E1.0.0/dist/cms.js:182:135902
e/</<@https://unpkg.com/netlify-cms@%5E1.0.0/dist/cms.js:182:136067
Qe/r.__iterateUncached/<@https://unpkg.com/netlify-cms@%5E1.0.0/dist/cms.js:1:14816
Me.prototype.__iterate@https://unpkg.com/netlify-cms@%5E1.0.0/dist/cms.js:1:36979
Qe/r.__iterateUncached@https://unpkg.com/netlify-cms@%5E1.0.0/dist/cms.js:1:14775
z@https://unpkg.com/netlify-cms@%5E1.0.0/dist/cms.js:1:3696
N.prototype.__iterate@https://unpkg.com/netlify-cms@%5E1.0.0/dist/cms.js:1:23555
toArray@https://unpkg.com/netlify-cms@%5E1.0.0/dist/cms.js:1:47973
Me@https://unpkg.com/netlify-cms@%5E1.0.0/dist/cms.js:1:10243
st@https://unpkg.com/netlify-cms@%5E1.0.0/dist/cms.js:1:19098
map@https://unpkg.com/netlify-cms@%5E1.0.0/dist/cms.js:1:50206
e/<@https://unpkg.com/netlify-cms@%5E1.0.0/dist/cms.js:182:136042
reduce/<@https://unpkg.com/netlify-cms@%5E1.0.0/dist/cms.js:1:50355
Me.prototype.__iterate@https://unpkg.com/netlify-cms@%5E1.0.0/dist/cms.js:1:36979
reduce@https://unpkg.com/netlify-cms@%5E1.0.0/dist/cms.js:1:50309
e@https://unpkg.com/netlify-cms@%5E1.0.0/dist/cms.js:182:135902
value/a<@https://unpkg.com/netlify-cms@%5E1.0.0/dist/cms.js:182:202721
value@https://unpkg.com/netlify-cms@%5E1.0.0/dist/cms.js:182:202700
updateClassInstance@https://unpkg.com/netlify-cms@%5E1.0.0/dist/cms.js:182:281271
beginWork@https://unpkg.com/netlify-cms@%5E1.0.0/dist/cms.js:182:282996
o@https://unpkg.com/netlify-cms@%5E1.0.0/dist/cms.js:182:286941
a@https://unpkg.com/netlify-cms@%5E1.0.0/dist/cms.js:182:287261
l@https://unpkg.com/netlify-cms@%5E1.0.0/dist/cms.js:182:287499
_@https://unpkg.com/netlify-cms@%5E1.0.0/dist/cms.js:182:290830
b@https://unpkg.com/netlify-cms@%5E1.0.0/dist/cms.js:182:290558
h@https://unpkg.com/netlify-cms@%5E1.0.0/dist/cms.js:182:289801
p@https://unpkg.com/netlify-cms@%5E1.0.0/dist/cms.js:182:289211
enqueueSetState@https://unpkg.com/netlify-cms@%5E1.0.0/dist/cms.js:182:279756
o.prototype.setState@https://unpkg.com/netlify-cms@%5E1.0.0/dist/cms.js:182:285
o/</n</r.prototype.handleChange@https://unpkg.com/netlify-cms@%5E1.0.0/dist/cms.js:190:38885
l@https://unpkg.com/netlify-cms@%5E1.0.0/dist/cms.js:36:20198
d/</<@https://unpkg.com/netlify-cms@%5E1.0.0/dist/cms.js:182:3906
e.exports/</<@https://unpkg.com/netlify-cms@%5E1.0.0/dist/cms.js:190:52250
dispatch@https://unpkg.com/netlify-cms@%5E1.0.0/dist/cms.js:36:23493
ee/</<@https://unpkg.com/netlify-cms@%5E1.0.0/dist/cms.js:182:17178
a@https://unpkg.com/netlify-cms@%5E1.0.0/dist/cms.js:190:72320
M/<@https://unpkg.com/netlify-cms@%5E1.0.0/dist/cms.js:190:72442
u@https://unpkg.com/netlify-cms@%5E1.0.0/dist/cms.js:190:75567
 cms.js:182:84585

- If the current behavior is a bug, please provide the steps to reproduce.

add a file collection type to config.yml
try to edit it and the editor crashes

- What is the expected behavior?
it should be showing the editor interface

Hugo : 0.37.1
Node.js: 8.10.0
Netlify CMS: 1.3.5
- Please link or paste your config.yml below if applicable.
backend:
  name: git-gateway

publish_mode: editorial_workflow

media_folder: "static/images/uploads"
public_folder: "/images/uploads"

collections:
  - name: "blog"
    label: "Blog"
    folder: "content/blog"
    create: true
    slug: "{{year}}-{{month}}-{{day}}-{{slug}}"
    fields: # The fields for each document, usually in front matter
      - {label: "Layout", name: "layout", widget: "hidden", default: "blog"}
      - {label: "Title", name: "title", widget: "string"}
      - {label: "Publish Date", name: "date", widget: "datetime"}
      - {label: "Draft", "name": "draft", widget: "boolean", default: true}
      - {label: "Body", name: "body", widget: "markdown"}
  - label: "Pages"
    name: "pages"
    files:
      - label: "Contacts"
        name: "contacts"
        file: "/data/contacts.yml"
        fields:
          - {label: Address, name: address, widget: string}
          - label: "Phone Numbers"
            name: phone_numbers
            widget: list
            fields:
            - {label: Number, name: "number", widget: string}
          - label: "Emails"
            name: emails
            widget: list
            fields:
            - {label: Email, name: "email", widget: string}

(edit by @tech4him1: fix formatting)

@zolamk Is your repo public, and can you link to it? I can't reproduce the error using your config.

Looks like you're using Netlify CMS 1.0.0 based on your stack trace - you'll want to upgrade to 1.3.5, as many bugs have been fixed since. Closing for now, but please comment if upgrading doesn't address this and we'll reopen.

Ah, @tech4him1 corrected me, didn't notice the url encoded caret, so you're probably using the latest version. I'm going to leave this closed since there hasn't been a response to the comment from four days ago, but we'll reopen if you comment.


[Feature][Zeta] Unify the triggering logic of job status related events

Search before asking

[X] I had searched in the feature and found no similar feature requirement.

Description
We already supported define some lifecycle event type.

But only FakeSource support produce these event.
https://github.com/apache/seatunnel/blob/1bba72385b6797dc5edd96fa5951376d0594e633/seatunnel-connectors-v2/connector-fake/src/main/java/org/apache/seatunnel/connectors/seatunnel/fake/source/FakeSourceReader.java#L77
We should support produce event in engine side, not connector side. Eg:
Produce reader open event in where invoke open method.

Usage Scenario
No response
Related issues
No response
Are you willing to submit a PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Can be assigned to me and I will complete it , thanks


Index on type text

How to reproduce

Using mariadb, create an index on a field of type text
Run prisma introspect
Run prisma generate
Prisma generate would fail, since index can not exists on field of type text

Expected behavior
The incorrectly setup index index should be commented out in the model and a console warning be displayed
Environment & setup
OS: Windows
Database: mariadb
Node.js version: 14.5.4
Prisma version:2.17.0

Can you show the code you are using to "create an index on a field of type text"?

When we tried integrating prisma to use for some of our surfaces the issue we faced was a dozen or  so errors, which most of them had no real impact but prevented us from using and running prospect which was essential to keep up with the db changes.
ALTER TABLE x ADD FULLTEXT KEY z (y);

Seems like a duplicate of https://github.com/prisma/prisma/issues/5434

Closing as duplicate of https://github.com/prisma/prisma/issues/5434


Aggregate pushdown for count(const) or count(non null) in JDBC connectors

Aggregate pushdown currently doesn't support the following use case when the count is done on a constant value.
select count(1) from jdbcdb.schema.table;
Current aggregate pushdown implementation generates this query on the datasource side -  select 1 from schema.table;.
Instead we like to see -  select count(1) from schema.table; or a flavor of it with count operation pushed down.
More details are here - slack link

We have SimplifyCountOverConstant rule. Does it mean the rule does not work properly? Looks like it supports simplifying the count over constant.

It looks like we run SimplifyCountOverConstant after PushAggregationIntoTableScan.

@kokosing How can we test the dependency of the rules? We can use BaseRuleTest or RuleTester to verify the rule independently. But I'm not sure how to check the final output of the sequence of multiple rules.

I think we need to add this case to io.prestosql.plugin.postgresql.TestPostgreSqlIntegrationSmokeTest#testAggregationPushdown and reorder rules. This will give us good enough coverage.

@kokosing
I tried to test the following queries. The former was correctly pushdown to the connector but the latter was not.
        assertPushedDown("SELECT count(*) FROM nation");
        assertPushedDown("SELECT count(1) FROM nation");

PushAggregationIntoTableScan optimizer was not triggered. It looks like the source of the aggregation node is not TableScanNode, actually ProjectNode. The plan of the latter SQL cannot be applied to the optimizer.
Do you have any idea why aggregation for count(1) is not over table scan? I guess it can be affected by other optimizers but not sure.

Hey @Lewuathe.  @findepi and I were taking a look at this today too. Can you try moving SimplifyCountOverConstant to run before columnPruningOptimizer. That should take care of the extra ProjectNode.

@alexjo2144 Thanks! I confirmed putting the SimplifyCountOverConstant before column pruning fixed the issue.


If pinpoint could catch the Execption from my webApp?

If Pinpoint could intercept the Execption from the webApp?Such as the Execptions thrown by JAVA and 400,500 errors when we request the web page.
I want to use pinpoint to catch the Exceptions and use these imformation .
Thanks for your team

Hi Eilikce,
We don't do anything with exceptions thrown inside an application. We simply record them if they are propagated up to a method we're tracing.
Is there anything you would like to do with the exceptions you catch in particular?

Hi Xylus,
I just want get the record from my webApp . I had saw that pinpoint record the Java Exceptions ,but I didn't find the 400 , 404 or 500 errors be recorded by pinpoint when I request the webApp page . If pinpoint can record such as 500 errors and show on the pinpoint-web ?
Thanks for your help


MRG: Use environment2.yml on CircleCI

Let's see if this fixes our recent failures.

CircleCI failure is due to https://github.com/scipy/scipy/issues/8118. I'll add a change here to fix it (hopefully).

This PR now:

Makes our environment2.yml almost the same as environment.yml (3 different lines I think?), and also makes the Python2 env more usably by using PyQt5 (using the same version-pinning trick as the Py3k env)
Fixes CircleCI -- it was breaking due to a SciPy 1.0.0 bug
Fixes a doctest error
Eliminates warnings in our examples except for one about creating a morph map (we should fix this the next time we have a good reason to update the sample dataset)

Green CircleCI build before fixing warnings here and build with just the fixed-warnings examples here (hopefully will be green, headed to bed now).
Ready for review/merge from my end.

Changed examples are easy to find in the index pages because they are the ones with thumbnails.
Examples here and tutorials here.

besides LGTM +1 for MRG

I'll make the suggested change by @agramfort then merge so that the CIs work again

Didn't fix my issue: https://circleci.com/gh/mne-tools/mne-python/6442?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link so I fear the error is on me.

You probably need to rebase (it merges with master but only after it's already loaded the circle.yml)

Oh I will try, thanks.
I can't cancel Appveyor builds, right?

BTW you can use new colormaps now, see:
https://6440-1301584-gh.circle-artifacts.com/0/tmp/circle-artifacts.1V7Oy5x/html/auto_tutorials/plot_background_statistics.html#visualize-and-compare-methods

I can't cancel Appveyor builds, right?

They should auto-cancel I think

Nope, error is on my part.


Added Kamesh Photo from Pod 2.1.1

Added My Photo from Pod 2.1.1
Kindly Review and Merge

@ksdkamesh99 bump

@wrussell1999 Sorry for the delay. I messed up with other works. Any way kindly review my PR and Merge


[HUDI-5540] Close write client after usage of DeleteMarker/RollbackTo…

…InstantTime/RunClean/RunCompactionProcedure
Change Logs
Close SparkRDDWriteClient after usage of DeleteMarker/RollbackToInstantTime/RunClean/RunCompactionProcedure so that the sparksql process can exit correctly
Impact
the sparksql process can exit correctly
Risk level (write none, low medium or high below)
None
Documentation Update
None
Contributor's checklist

[x] Read through contributor's guide
[x] Change Logs and Impact were stated clearly
[x] Adequate tests were added if applicable
[ ] CI passed

@hudi-bot run azure


community: Add pebblo safe document loader

Description: Pebblo opensource project enables developers to safely load data to their Gen AI apps. It identifies semantic topics and entities found in the loaded data and summarizes them in a developer-friendly report.
Dependencies: none
Twitter handle: srics

@hwchase17

@baskaryan, @eyurtsev, @hwchase17
Maintainers: can you pls review and provide your initial thoughts/comments? Thanks!

looks like some CI failures. otherwise, lgmt

Thanks, I will push a fix.

looks like some CI failures. otherwise, lgmt

Thanks, I will push a fix.

@hwchase17 CI lint issues fixed, pls review/merge

@hwchase17 fixed the CI issues,  pls review


Information on Integrating a UI Framework

A need for UI framework
Considering we the project will be serving real world users, It's is okay to integrate a UI framework that has native features.
Ionic is just okay
We need a brief research on using Ionic with React (current best practices should be considered). This will help guide us as we build.
PWA will be a good alternative
We can also use PWA if Ionic will not be applicable considering time.

@Aliyugambo we need this to guide us

Information on integrating UI framework
Considering we the project will be serving real world users,  integrating a UI framework that has native features is the bast.
Ionic Framework is an open source UI toolkit for building performance, high-quality mobile and desktop apps using web technologies — HTML, CSS, and JavaScript — with integrations for popular frameworks like React.
The documentation on how to integrate ionic with React can be found at
**https://ionicframework.com/**docs also the github page can be found at https://github.com/ionic-team/ionic-site
Alternatively
PWA (progressive web Apps ) documentation all required information can be found at
https://ionicframework.com/docs/react/pwa
all the required information about how we are to integrate ionic framework with react in our project can be found at the links provided above thanks

Okay thanks, so since using Ionic with React exposes the same tooling, we will ionic start --type=react --capacitor for issue#2
we will be using capacitor for android native build.
@aliyugambo please help us with issue#5 so we start documentation as we start main coding for frontend.


go 1.22+ support

fixes https://github.com/julz/importas/issues/21

@julz can you check this PR ?

thanks, looks like github actions has some complaints tho 🤔

welp need another approval 😞

idk how this is supposed :/
... go 1.22.0 is invalid for 1.20
but go 1.22 is invalid for 1.22 🫨

got it now 🤞
... can't use latest version of the tools because they need >1.22

awesome looks good now, thank you!


Firefox 65 supports WebP image format

https://bugzilla.mozilla.org/show_bug.cgi?id=1294490

Faster than me, damn :P
It's also in the changelog: https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Releases/65#APIs


Change directory more safely in unit tests

A slight improvement over the previous system since we now save the starting directory in setUp and return to it in tearDown. Previously, we did chdir('../..') in tearDown, which could go wrong if something unexpected happened in setUp or if an extra chdir() was used in the test functions themselves.
Some improvements that could be added here or in a future PR

Reduce duplication by moving the examples/ and workspace/ directories to the test utils module and making them Final.
run_psql() presumes that it is being called from the repo root directory. This doesn't feel good as it then matters which order you do the setUp calls in. Is there a way we can remove this reliance on the current working directory to run the db setup scripts with psql?

Update:

I have added a commit that changes how run_psql() works slightly. It can now be called from any location and takes a Path to the .dmp file to be run.


[DO NOT MERGE] Snippet Improvement Investigation

Description & motivation
This PR explores leveraging core functionality of MDX (what Docusaurus uses to generate markdown) and additional custom functionality to:

Make sure TOC links are rendering correctly within docs pages
Potentially extending the use of the Snippet component

As the functionality stands on prod, we cannot read/manipulate content data from inside snippets. With this new way, we can.

Refactoring of the DocItem theme component

Files of Interest

snippet/index.js - current version of the snippet component
newsnippet/index.js - The new snippet component implemented as a wrapper of every imported md file as a component
DocsItem/index.js - Swizzled component file that renders every docs page
website/docs/docs/get-started/getting-started/building-your-first-project/build-your-first-models.md - Main working file (rendered by DocsItem)
Preview of this page

Resources & Context

⭐  Using MDX components with the wrapper option
Context vs. State
React Context API

What We Know So Far

md files can be treated as components in Docusaurus’s implementation of mdx, and therefore can be imported into each other

build-your-first-models.md
import ModelsOnTop from<EMAIL_ADDRESS><ModelsOnTop components={{wrapper: ({...props}) => <NewSnippet {...props} />}} />

A toc object is automatically generated by Docusaurus in each mdx context (md file scope)
The main benefit of this new Direct Import Method (see item 1) is that the toc and markdown content data are available to work with from within a wrapper component. Please see these docs and the file /componets/newsnippet/index.js
functions do work in mdx files if you export them then immediately run them

export const hello = () => {
  console.log('hello!', toc)
}
hello()

Current Issues with Implementation

the TOCs that render are not in the correct order when there are multiple snippet files called with the new direct import method.

This is likely due to how the current TOC state (currentToc, tocContext) is currently implemented in the DocsItem component.

@breezyfasano Should we close this PR? I'm not sure if this is still relevant.

Closing due to age. @breezyfasano we can re-open if required.


Multi-texture/state symbols (eg. dice, arrows)

Is your feature request related to a problem? Please describe.
The modloader doesn't have support for multi-texture symbols.
Describe the solution you'd like
Add support for symbols with multiple textures/states.
Describe alternatives you've considered
N/A
Additional context
Not sure about how this would be implemented yet.

Am I misunderstanding the issue or doesn't the modloader already support this?
Take for example
extends "res://modloader/ModSymbol.gd"

const RESOURCE_PATH = "res://dev_console/"
var fruit = true

func init(modloader: Reference, params):
    self.modloader = modloader

    self.id = "reina"
    self.value = 2
    self.values = [20]
    self.rarity = "very_rare"

    self.texture = load_texture(RESOURCE_PATH + "dragonfruit.png")
    self.extra_textures["goose"] = load_texture(RESOURCE_PATH + "golden_goose.png")
    self.extra_textures["fruit"] = load_texture(RESOURCE_PATH + "dragonfruit.png")
    self.name = "TEST_ICON_I_FORGOT_TO_REMOVE"
    self.description = "i messed up"

func add_conditional_effects(symbol, adjacent):
    if fruit:
        symbol.set_texture(extra_textures["goose"])
        fruit = false
    else:
        symbol.set_texture(extra_textures["fruit"])
        fruit = true

This symbol swaps between the fruit and goose texture every spin. Unless you wanted it to like become part of the effect api builder?

I'm not sure if that would work the same way as vanilla multi-state symbols do. Also, internally instances of your mod symbol scripts are actually only created once, rather than once for each symbol. This will cause your symbol to have really weird behavior when multiple of that symbol are on the reels.
You could definitely implement multi-state symbols in the current version of the modloader, but it would be in a very roundabout way. For example, you'd probably have to create a new mod symbol for each state. I want to add some functionality to make this a lot more streamlined.


Physics hands separate from graphics hands

See this post: https://community.leapmotion.com/t/unity3d-orion-rigidhand-not-following-capsulehand-during-movement/4780

"I have a project setup where I interact with the controls inside of a spaceship using Orion.
Problem is that the RigidHand hitbox does not follow the model of the hand as it should when the ship starts moving forward.
When the ship is idle everything works perfectly, but as soon as it starts moving, the RigidHand always drags up behind. Problem is probably due to a simple timing between updating the model of the hand and its hitboxes."

Might be related to (or even the same as) #3.

@protodeep  and I discovered that it might simply be caused due to physics framerate being lower than render framerate.  When physics framerate is turned up higher than render framerate the judder and lag goes away completely.

Upon further investigation it also looks like setting the rigidbody's interpolation setting to None improves the behavior significantly, even without any core asset upgrades.  This might be something we can recommend to developers before the next release?

Has been addressed by #58, and is only a minor issue right now.  I am going to close out this issue because if there is anything else that needs to improve registration it will be caused by different issues


chore: Use Ops.CollectStatus Event

Description
This PR uses new ops feature CollectStatus Event to manage status Charm.  Event named "collect_unit_status" sets the status of charm automatically at the end of every hook.
Reference:

https://ops.readthedocs.io/en/latest/#ops.CollectStatusEvent
https://discourse.charmhub.io/t/how-to-set-a-charms-status/11771

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that validate the behaviour of the software
[x] I validated that new and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules
[ ] I have bumped the version of the library

Looks good. However, I would have expected tests to be updated with Harness.evaluate_status()?
Note also @gruyaume's comment here are probably waiting for the relation-broken fix in ops: canonical/sdcore-amf-operator#53 (comment)

https://juju.is/docs/sdk/scenario is used instead of Harness in unit tests. Hence, the unit tests are all valid without any modification.


Display magazine tag bar in between header components

#1266 #1121

[x] Improve title margin #1121

Hi @bhavi25 left some comments for you, please check :)

Hi @bhavi25, left a comment

LGTM!

@meols @NickHaggerty1 Can you please test this?
Magazine Tag bar in no more in between header components.
https://web-global-development-equinor-web-sites-dev.c2.radix.equinor.com/magazine/test1_magazine

@bhavi25 thanks. Looks good. One issue though, if the first component after the banner is set to have a coloured background the Title above it doesnt reflect that colour choice (as its not part of the component) so the colour extends a little behind the title. I have tested on the page you provided so please take a look... Is there a way an editor can adjust the colour/spacing behind the title also to match the first component choice? @meols

@meols @fernandolucchesi @bhavi25 I guess we could also create a bug for the above issue? And push the deploy with this card included? Dont want this issue to hold up getting the magazine changes published. It can be controlled / Managed by editors not selecting a background in the first text component. But should be looked at.

@bhavi25 thanks. Looks good. One issue though, if the first component after the banner is set to have a coloured background the Title above it doesnt reflect that colour choice (as its not part of the component) so the colour extends a little behind the title. I have tested on the page you provided so please take a look... Is there a way an editor can adjust the colour/spacing behind the title also to match the first component choice? @meols

Hi Nick, I thought this would be a requirement just for the magazineIndexPage, I will extend the functionality


[Toolkit feature]: Post processing volumes and increased post process support.

Contact Details (Optional)
<EMAIL_ADDRESS>What is the context of the feature/improvement?
...Hard to push scenes to that final level of polish.
Please describe the feature/improvement?
...Moving forward I'd love to see more support for post processing, using external tools for it is not only cumbersome but makes for a messy setup for modders and end users alike and provides only game-global post processes.
I'd love to see expanded functionality for Depth of Field, Convolution bloom, Film grain, vignetting and tonemapping
as well as a way to create post-process volumes inside the toolkit so that one can decide where exactly in the games these effects should take place, settings could also be applied to specific cameras.
What would be your solution? (optional)
...Expand post process functionality and move it towards per-volume and camera based settings instead of project wide.
Version
202x.x.x

bump

Hi,
It looks like the request is about the runtime (rendering) and not the ToolKit, right?

I suppose it's both given that these volumes would need to be placed and authored through the toolkit!

REMIX-2671 for tracking.


Koalas doesn't work with spatial dataframes

Hi,
I work with spatial dataframes which are created using the geopandas library. As the spatial dataframes contain geometries, they can get pretty massive. It would be awesome if Koalas can support Spatial DF's. Is there any plan to support geopandas - something like  ks.from_geopandas(spdf) in the future roadmap?

Looks interesting.
Let me investigate if there is any issue applying it to Koalas.
Thanks for the suggestion, @applecool :)

Let's don't add this support for now. geopandas itself is also a thirdparty library. We could think about leaving it as a thridparty unless there's a big needs for that.


Docs update to reflect sphinx progress on #34

It appears that the underlying issue in sphinx causing #34 (live reloading not working for autodoc'd code files and other static files) is at partially fixed. I get automatic rebuilds and browser reloads when I update my code files (as long as the directory they're in is watched). Still no reloads for other static files, but the code files were the biggest pain point since that's where most of the docs live for many of us using autodoc.
This PR updates the README "sphinx bugs" section accordingly. I also fixed a dead link to the EBP contributing guide.

@pradyunsg Do you need me to do anything else before you merge this?


Add option to browse files from Folders

In device tab it sync all photos. means all photos in phone's storage including Whatsapp, Telegram, Screenshots etc will be visible. It's difficult to find photos which are taken by phone camera only. Photos taken by phone camera is saved inside "DCIM" folder. But there is no way to browse files by folder. Please add this feature. Your app is amazing and top quality. Thanks

Yes, I agree with this. All photos are clutterd in one place. It's very hard to find a specific photo.
Here are some recommendations

Group photos by dates like a gallary app do
There should be a another tab listing all folders in phone that have photos.
I hope you understand my point. Thank you

I don't think the app currently listing all the photos in a device. I can't able to see my recent photos. Instead I am seeing old photos at first 😞

Yes, I agree with this. All photos are clutterd in one place. It's very hard to find a specific photo.
Here are some recommendations

Group photos by dates like a gallary app do
There should be a another tab listing all folders in phone that have photos.
I hope you understand my point. Thank you

@beradeep any on this ?

I don't think the app correctly listing all the photos in a device. I can't able to see my recent photos. Instead I am seeing old photos at first 😞
Edit 2: So, I have 100588 photos on my phone, I downloaded a one more photo then the number is 100589 photos. The problem is the newly downloaded photo is at the bottom of the app 💀. Am I going to scroll that much everytime? 😭😭😭

Thanks for pointing it out. Yes, I'm aware of this. The photos aren't sorted right now. An option to sort by date needs to be implemented.

I don't think the app correctly listing all the photos in a device. I can't able to see my recent photos. Instead I am seeing old photos at first 😞
Edit 2: So, I have 100588 photos on my phone, I downloaded a one more photo then the number is 100589 photos. The problem is the newly downloaded photo is at the bottom of the app 💀. Am I going to scroll that much everytime? 😭😭😭

Thanks for pointing it out. Yes, I'm aware of this. The photos aren't sorted right now. An option to sort by date needs to be implemented.

Also it be will be great if you add something like this. (Group photos by dates like a gallary app and albums)

Is this still pending?


Request: please consider evaluating pareto-optimality of BiLLM

Hi!
Thank you for the paper! It is inspiring that you can compress weights to about 1 bit and the model still works better than random.
A practical sub-2-bit quantization algorithm would be a great boon to researchers and practitioners alike.
I'd appreciate if you could study the practical significance of BiLLM further by evaluating it in terms of pareto-optimality[1].
To do so, please compare perplexity of different methods for the same total model size(GB), but with different models.
For instance, one of the results you report in Table 2 has Llama-2 70B @ 1.08bits/weight score the perplexity of 8.41.
This has a total footprint of roughly 8.8GiB (70e9 * 1.08/8 / 2**30)
In comparison, the other ways a practitioner could achieve 8.8GiB footprint are:

take Llama-2 13B, quantize to ~5.8 bits (13e9 * 5.8/8 / 2**30)
take Llama-2 7B, quantize it to ~10.7 bits (13e9 * 10.7/8 / 2**30)

This comparison would present a more unified (and stricter) way to compare extreme (1-2 bit) quantization algorithms.
Notably, some recent works ([2, 3, 4]) that present 2-bit quantization schemes report that they are not pareto-optimal at 2 bits (i.e. it is still better to take a smalelr model and quantize it to 3- or 4- bits), and only achieve parity at, e.g., 2.5-3 bits[2]. By the way, [2,3,4] would also make for an interesting baseline to compare BiLLM against.
If it turns out that BiLLM is not optimal at 1.08bits, it would be insightful to learn what is the bitwidth where it becomes is pareto-optimal.
[1] https://arxiv.org/abs/2212.09720
[2] https://arxiv.org/abs/2401.06118
[3] https://cornell-relaxml.github.io/quip-sharp/
[4] https://arxiv.org/abs/2307.13304

@justheuristic See for example, llama-2-13b @ 4.90 bits is 7.86GB and scores a perplexity of 4.3 in exllamav2.
https://oobabooga.github.io/blog/posts/gptq-awq-exl2-llamacpp/

Thanks!
It is also curious if we could go in the opposite direction: find a pareto-optimal spot for BiLLM, even if it has a different bitwidth?
If any of the authors looked (or plan to look) in this direction, i'd appreciate it if you share what you find.

Hi, @justheuristic, thank you for your request!
In practical applications, it's important to look into how to balance the size of LLMs and the bit-width, just like [1] and [2] did with exploring quantization between 2 to 4 bits. The design of BiLLM aims to push the possibilities of compressing LLMs under 1-bit quantization, an extreme form of quantization that initially challenges the achievement of reasonable outputs under Post-Training Quantization (PTQ) methods, surpassing the existing PTQ binary methods.
As illustrated in Figure 1 of the paper, particularly at 1-bit, the model capability collapses, resulting in an extreme marginal effect. So, talking about the Pareto optimality of different model sizes and bit widths in binary quantization is not identical to the objective of BiLLM. However, we think that  Pareto exploration of binary quantization and mixed-precision non-binary quantization across different model scales presents a challenging and meaningful endeavor for the next step :-) .
Binary quantization and general bit-width quantization (2 to 8 bits) exhibit fundamental differences in their representation. Although the strategy of BiLLM is specifically tailored for binary weight design, we've also tested it at other sizes and give some preliminary data.

BiLLM-LLaMA-2
Weight Bits
WikiText-2

7B
2.00
7.62

7B
2.28
6.94

7B
4.26
5.52

13B
2.00
6.41

13B
2.29
5.89

13B
4.28
4.91

BiLLM explores the PTQ strategy for 1-bit quantization, as PTQ compression does not involve any training or backpropagation processes. So, we didn't compare our method with another type called Quantization Aware Training (QAT). We also discovered that the latest quantization methods achieved good performance at 2 to 4 bits, but since they were not designed for 1 bit, they all suffer from precision collapse at this level. We are pleased to focus on the latest advanced methodologies and enhance our subsequent research endeavors.
[1]https://arxiv.org/abs/2212.09720
[2]https://arxiv.org/pdf/2401.06118.pdf


Numbers as names in radio/checkboxes cause js error

Numbers as names in radios/checkboxes are valid but cause following error in handleMultiple method. This is an easy fix that converts a number to string.
VM1868:2024 Uncaught TypeError: this.options.multiple.replace is not a function
at Factory.handleMultiple (:2024:53)
at Factory.init (:1992:39)
at new Factory (:1976:17)
at HTMLInputElement. (:1396:31)
at Function.each (jquery.js:362)
at jQuery.fn.init.each (jquery.js:157)
at :1395:82
at Form._withoutReactualizingFormOptions (:1427:20)
at Form._bindFields (:1394:12)
at Factory.bind (:2061:127)

Thank you!!!!


shairport-sync: fixup airplay support in snapserver

Motivation for this change
This fixes the aircast support in snapserver which requires coverart support.
I'm enabling that by default since I believe this does not bring any additional dependencies.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

I believe this PR was superseded by https://github.com/NixOS/nixpkgs/pull/175860

correct


protocmp.Transform can not handle NaN

What version of protobuf and what language are you using?
Version: v1.28.1
What did you do?
	pb := &pb3.Scalars{
		SFloat:  float32(math.NaN()),
		SDouble: math.NaN(),
	}
	assert.Equal(t, "", cmp.Diff(pb, pb, protocmp.Transform()))

What did you expect to see?
PASS
What did you see instead?
        	            	Diff:
        	            	--- Expected
        	            	+++ Actual
        	            	@@ -1 +1,8 @@
        	            	+  (*textpb3.Scalars)(Inverse(protocmp.Transform, protocmp.Message{
        	            	+  	"@type":    s"pb3.Scalars",
        	            	+- 	"s_double": float64(NaN),
        	            	++ 	"s_double": float64(NaN),
        	            	+- 	"s_float":  float32(NaN),
        	            	++ 	"s_float":  float32(NaN),
        	            	+  }))

Anything else we should know about your project / environment?
No

protocmp.Transform simply transforms a proto.Message into a form that cmp understands. Afterwards, you can compose other options with the result to achieve the desired outcome. In this case, you could compose protocmp.Transform with cmpopts.EquateNaNs.


Add  NFT Creator tool to Showcase

Checklist

[x]  I have read the How to Contribute.
[x]  I have read the Showcase Requirements
[x]  I have run yarn build after adding my changes without getting any errors.

Showcase addition
Title: NFT Creator tool
Description: A Website that enables non-tech users to create NFT by themselves with a few simple clicks, it also allows the creator to customize the metadata of NFT, control the policy-id of assets, and use their images for each NFT"
Website: http://nft.easterntownhall.com:8088/
Tags:  nftsupport

Thank @rphair for your valued comment and suggestion.
I apologize for the incorrect wording in the description as well as for the website redirection as you said
I'm glad if there are other tools with the same functionality as ours listed on the website. I just highlight that our tool allows minting NFT from address pair from the user's wallet, the user can manage asset policyID, and low minting cost (1.18 ADA/NFT).
By the way, may I ask if we include this tool in the builder tool group, what conditions does the tool need to satisfy? we want to share code/docker image for the community to reuse
Regards


built: uf2: Flexible UF2 offset selection.

UF2 offset configurble to be either flash base reg + offset,
or simply the flash bare reg if the offset is configured
to be ignored.
Signed-off-by: Peter Johanson<EMAIL_ADDRESS>This tweaks the UF2 offset calculation based on the discussions in #34835 to allow properly incorporating the flash base addr (needed for RP2040 where this isn't 0x0) as well as the flash offset (needed for samd and nRF52 UF2 bootloaders).
On RP2040, we'll ignore the flash offset because even though the code is built to that offset, the second stage bootloader then gets bundled into the bin, and the UF2 by extension, so the UF2 needs to use an offset of only the tlash base address. There, I anticipate defaulting the new BUILD_OUTPUT_UF2_IGNORE_FLASH_OFFSET to y for the whole SoC.

LGTM, just one question

Closing, this was pulled into #34835 and merged as part of that work.