Unpacking artifact issue

Describe the issue
Similar to #1047. I cannot get it running to download the artifact and extract that one. Or better said the extract works, but the Rename-Item after that fails 99%. It seems that the us-tmp or platform-tmp folder is still in use of the operating system (probably our antivirus system which scans all zips). I cloned the navcontainerhelper and put a Start-Sleep -Seconds 15 after the Expand-Archive and in front of the Rename-Item in Download-Artifact.ps1. Then it works. But I think that's not a solution, is it (even if it would be fine for me)? ;) Don't know what's the best practice in such a case..
Script used to download artifact and cause the issue
Download-Artifacts -artifactUrl (Get-BCArtifactUrl -country "us") -includePlatform

Full output of scripts
see screenshot
Screenshots
"Der Zugriff auf den Pfad ... wurde verweigert" = "The access to the path ... was denied."

Additional context

did you try Flush-ContainerHelperCache and retry?

Did you get the issue resolved?

I tried the Flush-ContainerhelperCache, but it didn't solve the issue.

I think you are right in your assumption that this is a timing issue.
I will probably try the rename and if it fails - will pause and retry a few times.

What I will do is the following (for both platform and app artifacts)
        while (Test-Path "$platformArtifactPath-tmp") {
            try {
                Rename-Item -Path "$platformArtifactPath-tmp" -NewName ([System.IO.Path]::GetFileName($platformArtifactPath)) -Force
            }
            catch {
                Write-Host "Unable to get exclusive access to $platformArtifactPath-tmp - waiting 10 seconds and retrying..."
                Start-Sleep -Seconds 10
            }
        }

Thanks :)

fixed in <IP_ADDRESS>


Windows Unicode

Unicode input seems to be missing, at least for Windows. For example with
PowerShell, I can paste the character:
₧ (U+20A7)
with no issue, or input as Alt + 158. However Elvish does not accept paste
or keyboard input.

@nu8, Thanks for the bug report. Note that the support for MS Windows is rudimentary -- mostly limited to ensuring it builds, successfully runs the unit tests, and correctly executes Elvish scripts. I personally don't use Windows other than in the context of working on projects like Elvish. As far as I know none of the current Elvish users use it as their interactive shell on Windows. Help from people like yourself to improve the interactive behavior on Windows is appreciated. Even if it's just bug reports such as this issue.
P.S., An example of another problem is a SSH connection to a Windows system running Elvish results in the prompt being garbled. Specifically, displaying text that is meant to be Windows terminal compatible escape sequences.


Allocators

A general allocator utility specialised on the backend being used. Usage:

copcore::Allocator<Type, backend> myAlloc; // backends defined in Global.h, constructor takes optional device id
Type *obj_ptr = myAlloc.allocate(10, params...); // allocates an array of 10 Type objects, passing params... to their constructor
...
myAlloc.deallocate(obj_ptr, 10); // deallocates the array, calling optionally ~Type (if number of elements passed)

test_launcher extended to demonstrate usage of the new allocator for (basic) types. Added an example for launching lambda functions.

Tested it, looks fine! Ready to merge.


sbt SNAPSHOT dependency with classifiers not updating

I have a dependency on two jars, one with a classifier and one without.  When a new SNAPSHOT version is published the jar with the classifier is not updated in my local Ivy cache.
Steps to reproduce:

setup my project dependency
libraryDependencies += "group" %% "artifactA" % "1.0.0-SNAPSHOT" withSources() classifier("test") classifier("")
sbt update -- project is updated and both the jars are downloaded
publish a new version of 'artifactA' (a different project)
sbt update -- updated my project that has a dependency on 'artifactA'

The result is that group-artifactA_2.9.1-1.0.0-SNAPSHOT.jar is updated, but group-artifactA_2.9.1-1.0.0-SNAPSHOT-test.jar is not.
The expected result is that both jars are updated:

group-artifactA_2.9.1-1.0.0-SNAPSHOT.jar
group-artifactA_2.9.1-1.0.0-SNAPSHOT-test.jar

I have been using sbt 0.12.1.  This issue has also been confirmed to to exist in 0.12.2-RC2 and the 0.13 branch.

Hi guys. I can reproduce this bug in 0.13.5.

Also does not work in 0.13.8

Doesn't work for me either in 0.13.8

Does anyone have a automated repro steps for the regression?
I couldn't reproduce it in b1aa263b7f281496960e1bcf3534406e068277e5

I guess we can keep this closed and work on this in #1676. Note that the fix here was reverted in #1234 for a number of reasons.

This problem still exists in latest version
sbt.version=0.13.11
and in my build.sbt :
libraryDependencies ++= Seq(
...
"com.rh.cores" % "treasury" % treasuryVer changing(),
  "com.rh.cores" % "treasury" % treasuryVer % Test classifier "tests" changing(),
...

but after executing sbt update only main dependencies updated and "tests" classified  dependencies does not update.
I should remove theme manually from .ivy2 folder

I think that this issue should be reopened. The problem is reproducible using sbt version 0.13.7.
Here is the dependency in my sbt file:
 "org.apache.spark" % "spark-mdlp-discretization_2.11" % "0.2-SNAPSHOT" changing(),
I have tried repeatedly to get the latest SNAPSHOT using "sbt update" but it does not pull it unless I explicitly removed the existing spark-mdlp-discretization_2.11-0.2-SNAPSHOT.jar from
~/.ivy2/cache/org.apache.spark/spark-mdlp-discretization_2.11/jars
I will try again with the latest version of sbt, but I am not hopeful given above post.

OK. I tried again with 0.13.12 and it seemed to work, so never mind...


procs-need-restart: invalid option: -c

Running on Alpine edge, no changes to default configuration. Getting the following error message. Packages are nevertheless updated, but of course relevant processes not restarted.
apk-autoupdate: Checking available updates...
apk-autoupdate: Upgrading packages:  busybox-initscripts
(1/1) Upgrading busybox-initscripts (3.1-r5 -> 3.1-r6)
Executing busybox-initscripts-3.1-r6.post-upgrade
OK: 250 MiB in 99 packages
procs-need-restart: invalid option: -c

Usage: procs-need-restart [options] [PID...]

Find processes that use (maps into memory) files which have been deleted
or replaced on disk (and the new files are not identical to the mapped ones).
If no PID is specified, scan all processes.

This program is part of apk-autoupdate.

Options:
  -f PATT*   Specify paths of mapped files to include/exclude from checking.
             Syntax is identical with fnmatch(3) with no flags, but with
             leading "!" for negative match (exclude). This option may be
             repeated.

  -v         Report all affected mapped files.

  -h         Show this message and exit.

  -V         Print program version and exit.

Please report bugs at <https://github.com/jirutka/apk-autoupdate/issues>
-----BEGIN SUMMARY-----
Upgraded packages:
  busybox-initscripts (3.1-r5 -> 3.1-r6)

-----END SUMMARY-----

Can confirm I have the same error.

https://github.com/jirutka/apk-autoupdate/commit/7476b9d184fec213487a97a3f35a662f89b32ca5

https://github.com/jirutka/apk-autoupdate/commit/7476b9d184fec213487a97a3f35a662f89b32ca5


Remove: Anaconda.Miniconda3 version py39_23.3.1-0

https://github.com/microsoft/winget-pkgs/issues/142606
Checklist for Pull Requests

[x] Have you signed the Contributor License Agreement?
[ ] Is there a linked Issue?

Manifests

[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[x] This PR only modifies one (1) manifest
[x] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[ ] Does your manifest conform to the 1.6 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

URL: https://repo.anaconda.com/miniconda/Miniconda3-py39_23.3.1-0-Windows-x86_64.exe
Status Code: 200
(Automated message - build 872)


hcxdumptools will not make- Kali 2020 OS not supported

Trying to Download hcxdumptool on kali linux 2020.
Kernel version is 5.4
i was able to successfully download hcxtools.
When I attempt to make
i get the following output:
OS not supported
cc-03 -Wall -Wextra -std=gnu99 -o hcxpioff.c -DVERSION_TAG="6.0.1-46-g4d5cdf3" -DVERSION_YEAR="2020"
cc-03 -Wall -Wextra -std=gnu99 -o hcxdumptool hcxdumptool.c -lcrypto -DVERSION_TAG="6.0.1-46-g4d5cdf3" -DVERSION_YEAR="2020"
Any help on why this issue might be occuring would be helpful

What's the output of "uname -s" ?

"make" retrieve information about the operating system and will only proceed if it detect Linux. We are doing this, because proprietary operating systems (MacOS and WINDOWS) doesn't support monitor mode and packet injection.
As @strasharo mentioned, uname -s will show you this information:
$ uname -s
Linux
exactly this output is tested by make:
ifeq ($(HOSTOS), Linux)
If uname -s return an empty string, you KALI installation is broken!
To compile it without os check, just remove this lines from the Makefile:
23 ifeq ($(HOSTOS), Linux)
24 INSTFLAGS += -D
25 endif

30 ifeq ($(HOSTOS), Linux)
34 endif

37 ifeq ($(HOSTOS), Linux)
40 else
41	$(info OS not supported)
42 endif

But I really suggest you to fix your installation!

Some words about KALI:
KALI is a professional penetration testing platform. It is not easy to configure.  It is not designed to be used by beginners. Nearly all reported issues are related to missing dependencies, drivers that doesn't support monitor mode and full packet injection, broken installations and misconfigured systems.
Before using KALI I suggest to read this:
https://kali.training/lessons/introduction/
https://kali.training/lessons/5-configuring-kali-linux/
https://www.tutorialspoint.com/kali_linux/kali_linux_installation_and_configuration.htm
https://www.kali.org/penetration-testing-with-kali-linux/
It is mandatory to know how to fix configure KALI, ti fix broken system and to solve KALI dependencies.

Closed because issue is not related to hcxdumptool, but you can still ask your questions, here.


interact.py killed on second run

I did:
git clone https://github.com/huggingface/transfer-learning-conv-ai
cd transfer-learning-conv-ai
pip install -r requirements.txt
python -m spacy download en
Then It run once as follows:
python3 interact.py
It downloaded the model and I could chat with the bot. I stop the execution with Ctrl+C and then
I did again:
python3 interact.py
to get:
INFO:pytorch_transformers.modeling_utils:loading weights file /tmp/tmpzwe_u3oz/pytorch_model.bin
INFO:pytorch_transformers.modeling_utils:Weights from pretrained model not used in OpenAIGPTLMHeadModel: ['multiple_choice_head.summary.weight', 'multiple_choice_head.summary.bias']
INFO:pytorch_transformers.tokenization_utils:Assigning  to the bos_token key of the tokenizer
INFO:pytorch_transformers.tokenization_utils:Assigning  to the eos_token key of the tokenizer
INFO:pytorch_transformers.tokenization_utils:Assigning  to the pad_token key of the tokenizer
INFO:pytorch_transformers.tokenization_utils:Assigning ('', '') to the additional_special_tokens key of the tokenizer
INFO:interact.py:Sample a personality
INFO:/home/jovyan/work/alela/dan_chatbots/transfer-learning-conv-ai/utils.py:Load tokenized dataset from cache at ./dataset_cache_OpenAIGPTTokenizer
Killed
And every time I run
pyhton3 interact.py, the same happens. Always Killed.
Somebody can explain?
On the other hand I have no way to exit the program while into the dialogue but to do Ctrl+C
Thank you,
Alejandro

Hi. Unfortunately I can't replicate this on my machine. What versions of pytorch-transformers and pytorch are you on?

I was able to avoid the Killed prompt and now the
python ./interact.py
works well by deleting dataset_cache_OpenAIGPTTokenizer from the local dir before running the command.
But if I Ctrl+C and then I run it again without erasing the file dataset_cache_OpenAIGPTTokenizer it fails.
I've tried a lot of usual commands into the dialogue prompt to exit clean, without any success.
Using Ctrl+Z works, but because the process is not canceled but paused (it continues after sending the fg command, as usually happens with any excution in linux).

Any idea how to finish the dialogue smoothly?

Interesting! This question might be relevant: https://stackoverflow.com/questions/726690/what-killed-my-process-and-why, specifically seeing whether dmesg -T| grep -E -i -B100 'killed process' says anything informative.

Thank you sshleifer!!! maybe that's the problem.


Stacktrace is unreadable for Flutter released app

Platform:

[x]  Dart: 2.18.6
[x]  Flutter Android or iOS: 3.3.10
[ ]  Flutter Web

IDE:

[x]  VSCode
[ ]  IntelliJ/AS
[ ]  XCode
[ ]  Other, which one?

split-debug-info and obfuscate (Flutter Android or iOS) or CanvasKit (Flutter Web):

[ ]  Enabled
[x]  Disabled

Platform installed with:

[x] pub.dev
[ ] GitHub

Output of the command flutter doctor -v below:
Doctor summary (to see all details, run flutter doctor -v):
[√] Flutter (Channel stable, 3.3.10, on Microsoft Windows [Version 10.0.19041.804], locale en-US)
[√] Android toolchain - develop for Android devices (Android SDK version 33.0.0-rc1)
[√] Chrome - develop for the web
[√] Visual Studio - develop for Windows (Visual Studio Community 2019 16.11.1)
[√] Android Studio (version 4.0)
[√] VS Code (version 1.74.2)
[√] Connected device (3 available)
[√] HTTP Host Availability
• No issues found!
The version of the SDK (See pubspec.lock):
6.18.1

I have the following issue:
The errors stacktrace is unreadable for the released Android build. It was working during development.
My build.gradle file looks like this
`buildTypes {
release {
signingConfig signingConfigs.release
        // Enables code shrinking, obfuscation, and optimization for only
        // your project's release build type.
        minifyEnabled true

        // Enables resource shrinking, which is performed by the
        // Android Gradle plugin.
        shrinkResources true

        // Includes the default ProGuard rules files that are packaged with
        // the Android Gradle plugin. To learn more, go to the section about
        // R8 configuration files.
        proguardFiles getDefaultProguardFile(
                'proguard-android-optimize.txt'),
                'proguard-rules.pro'

        ndk {
            debugSymbolLevel 'SYMBOL_TABLE'
        }
   }

}`
I have uploaded the proguard mapping.txt file and ran flutter packages pub run sentry_dart_plugin as well, it uploaded the debug symbols to Sentry. However, the stacktraces are still not updated.
How it looks:

@abdo400 this is a Dart error I believe, did you compile your app with split-debug-info and obfuscate?

I didn't compile with split-debug-info and obfuscate. I only had proguard, I think this is the main reason since it was working fine for iOS. I will try it out.

I didn't compile with split-debug-info and obfuscate. I only had proguard, I think this is the main reason since it was working fine for iOS. I will try it out.

The proguard mapping file is only for Java/Kotlin minified events, the screenshot isn't a Java/Kotlin event.
Can you link me to a sentry.io event so I can take a look?

It's locked behind the org account, not sure how to link it and you will be able to take a look?

https://sentry.io/share/issue/5a84c16198af4043aebe7be386ab90b3/

@abdo400 hard to tell, maybe you are using a pre-compiled library that is already obfuscated?

I don't think so, this is everywhere inside the app. I have released another build but with the obfuscated flags. And uploaded the symbols to Sentry. Waiting to see the results.

@abdo400 if you create a new app (using the template), and add sentry, do you experience the same issue?
a minimal reproducible example would help here since apps are not minified by default, so it should not be an issue at all.

Could it be because I set minifyEnabled true in by build.gradle script?

The proguard mapping file is only for Java/Kotlin minified events, the screenshot isn't a Java/Kotlin event.

Nope, as mentioned.

The proguard mapping file is only for Java/Kotlin minified events, the screenshot isn't a Java/Kotlin event.

After making the build with split-debug-info and obfuscate, and uploading the debug symbols. The errors are now decoded, but its not how it used to be though (it doesn't show the app stacktrace).
This is how it looks now:
https://sentry.io/share/issue/cd4f94be561741df874b3116549c6d13/
This is how it used to be for older builds
https://sentry.io/share/issue/7596260a96334aa6a77485c0214b3680/

1st. When you enable split and obfuscate, the stack traces look like this, this is not Sentry's fault, but rather how the Flutter tooling works https://docs.flutter.dev/deployment/obfuscate
Try to throw an error that happens within your App's code, for this one, everything is system frames, can you share the code snippet of this error? how did you throw and where in the app?
2nd. That's the standard way if split and obfuscate are not enabled, there's something in your setup/environment messing this up (we need a minimal reproducible example).
3rd. that's how it should be.

So, after some digging
I found out that this:
https://sentry.io/share/issue/654d712ab9274c5f8cd3a30a7bde5ba0/
Was actually caused by this line extra-gen-snapshot-options=--obfuscate in android/gradle.properties. (You can reproduce in a fresh project by only adding this line)
Which is good, now I can stack trace my errors again!
However, if I want to build with split-debug-info and obfuscate.
I still get this:
https://sentry.io/share/issue/6cbe95d01c1f4bbbbc67fcd312f3980a/
Which is unfortunately not good as its not showing my dart stack trace.
For an idea of how I think it should like, this is the same error but with no obfuscation:
https://sentry.io/share/issue/e18ced471a454e8db85f6bce5e4cca39/

Which is good, now I can stack trace my errors again!

That's on the Flutter tooling, not on Sentry's, if you enable the obfuscation features, the stack traces will look like native code (C/C++), because that's how the Dart and Flutter tooling work internally.
There's an issue with the Dart language to make it possible (revert back to Dart stack traces) but AFAIK there's no progress yet.
So removing the --obfuscate should work, or enabling split-debug-info and obfuscate but then you know about the stack traces, closing this issue, thanks for figuring it out.


Zephyr defines POSIX values which already appear in limits.h

Describe the bug
Upstream picolibc includes definitions for various minimum values in limits.h that are required by POSIX including _POSIX_NAME_MAX and _POSIX_PATH_MAX. Zephyr is redefining these in include/zephyr/posix/posix_features.h.
To Reproduce

Download toolchain built against current picolibc development branch: https://github.com/zephyrproject-rtos/sdk-ng/actions/runs/11503233418/artifacts/2100796287
west twister -p qemu_malta -s tests/lib/c_lib/thrd/libraries.libc.c11_threads.picolibc
See error

Expected behavior
Successful test run
Impact
Cannot migrate picolibc to upstream development version
Logs and console output
[81/147] Building C object zephyr/lib/posix/options/CMakeFiles/lib__posix__options.dir/sysconf.c.obj
FAILED: zephyr/lib/posix/options/CMakeFiles/lib__posix__options.dir/sysconf.c.obj
ccache /__w/sdk-ng/sdk-ng/tools/zephyr-sdk-0.17.0-8-g6fd2e1d/mips-zephyr-elf/bin/mips-zephyr-elf-gcc -DKERNEL -DK_HEAP_MEM_POOL_SIZE=1024 -DPICOLIBC_LONG_LONG_PRINTF_SCANF -DTC_RUNID=020f12a965888084e31d7f59ce1d46d3 -D__LINUX_ERRNO_EXTENSIONS__ -D__ZEPHYR__=1 -I/__w/sdk-ng/sdk-ng/zephyrproject/zephyr/kernel/include -I/__w/sdk-ng/sdk-ng/zephyrproject/zephyr/arch/mips/include -I/__w/sdk-ng/sdk-ng/test/twister-out/qemu_malta/tests/lib/c_lib/thrd/libraries.libc.c11_threads.picolibc/zephyr/include/generated/zephyr -I/__w/sdk-ng/sdk-ng/zephyrproject/zephyr/include -I/__w/sdk-ng/sdk-ng/test/twister-out/qemu_malta/tests/lib/c_lib/thrd/libraries.libc.c11_threads.picolibc/zephyr/include/generated -I/__w/sdk-ng/sdk-ng/zephyrproject/zephyr/soc/qemu/malta -I/__w/sdk-ng/sdk-ng/zephyrproject/zephyr/include/zephyr/posix -I/__w/sdk-ng/sdk-ng/zephyrproject/zephyr/soc/qemu/malta/. -I/__w/sdk-ng/sdk-ng/zephyrproject/zephyr/subsys/testsuite/include -I/__w/sdk-ng/sdk-ng/zephyrproject/zephyr/subsys/testsuite/coverage -I/__w/sdk-ng/sdk-ng/zephyrproject/zephyr/subsys/testsuite/ztest/include -isystem /__w/sdk-ng/sdk-ng/zephyrproject/zephyr/lib/libc/common/include -Os -DNDEBUG -Wshadow -fno-strict-aliasing -Werror -Os -imacros /__w/sdk-ng/sdk-ng/test/twister-out/qemu_malta/tests/lib/c_lib/thrd/libraries.libc.c11_threads.picolibc/zephyr/include/generated/zephyr/autoconf.h -fno-printf-return-value -fno-common -g -gdwarf-4 -fdiagnostics-color=always -EL -msoft-float -G0 -mno-gpopt -fno-pic -pipe --sysroot=/__w/sdk-ng/sdk-ng/tools/zephyr-sdk-0.17.0-8-g6fd2e1d/mips-zephyr-elf/mips-zephyr-elf -imacros /__w/sdk-ng/sdk-ng/zephyrproject/zephyr/include/zephyr/toolchain/zephyr_stdint.h -Wall -Wformat -Wformat-security -Wno-format-zero-length -Wdouble-promotion -Wno-pointer-sign -Wpointer-arith -Wexpansion-to-defined -Wno-unused-but-set-variable -Werror=implicit-int -fno-pie -fno-asynchronous-unwind-tables -fno-reorder-functions --param=min-pagesize=0 -fno-defer-pop -fmacro-prefix-map=/__w/sdk-ng/sdk-ng/zephyrproject/zephyr/tests/lib/c_lib/thrd=CMAKE_SOURCE_DIR -fmacro-prefix-map=/__w/sdk-ng/sdk-ng/zephyrproject/zephyr=ZEPHYR_BASE -fmacro-prefix-map=/__w/sdk-ng/sdk-ng/zephyrproject=WEST_TOPDIR -ffunction-sections -fdata-sections --specs=picolibc.specs -D_POSIX_THREADS -mips32 -std=c99 -MD -MT zephyr/lib/posix/options/CMakeFiles/lib__posix__options.dir/sysconf.c.obj -MF zephyr/lib/posix/options/CMakeFiles/lib__posix__options.dir/sysconf.c.obj.d -o zephyr/lib/posix/options/CMakeFiles/lib__posix__options.dir/sysconf.c.obj -c /__w/sdk-ng/sdk-ng/zephyrproject/zephyr/lib/posix/options/sysconf.c
In file included from /__w/sdk-ng/sdk-ng/zephyrproject/zephyr/include/zephyr/posix/signal.h:10,
                 from /__w/sdk-ng/sdk-ng/zephyrproject/zephyr/include/zephyr/posix/time.h:62,
                 from /__w/sdk-ng/sdk-ng/zephyrproject/zephyr/include/zephyr/posix/pthread.h:14,
                 from /__w/sdk-ng/sdk-ng/zephyrproject/zephyr/lib/posix/options/sysconf.c:9:
/__w/sdk-ng/sdk-ng/zephyrproject/zephyr/include/zephyr/posix/posix_features.h:241: error: "_POSIX_AIO_LISTIO_MAX" redefined [-Werror]
  241 | #define _POSIX_AIO_LISTIO_MAX               (2)
      |
In file included from /__w/sdk-ng/sdk-ng/tools/zephyr-sdk-0.17.0-8-g6fd2e1d/mips-zephyr-elf/picolibc/include/limits.h:6,
                 from /__w/sdk-ng/sdk-ng/zephyrproject/zephyr/include/zephyr/kernel_includes.h:22,
                 from /__w/sdk-ng/sdk-ng/zephyrproject/zephyr/include/zephyr/kernel.h:17,
                 from /__w/sdk-ng/sdk-ng/zephyrproject/zephyr/include/zephyr/posix/pthread.h:13:
/__w/sdk-ng/sdk-ng/tools/zephyr-sdk-0.17.0-8-g6fd2e1d/mips-zephyr-elf/picolibc/include/sys/syslimits.h:63: note: this is the location of the previous definition
   63 | #define _POSIX_AIO_LISTIO_MAX   2

Environment (please complete the following information):

OS: Linux
Toolchain Zephyr SDK development version

I would guess that an ifndef might not be sufficient here, since that value should probably be configurable via Kconfig (if it isn't already).
What are your thoughts here @keith-packard ?

All of these constants actually have fixed values defined by POSIX, so #ifndef would be completely fine. You probably only need to check one of them?

Just landed 🛬 - this should be easy enough to fix quickly.

as we both try to track the C23 changes in parallel. Thanks for taking a look; hope your travel is going well.


[SE-0111] Suppress the printing of argument labels in function types.

What's in this pull request?
When printing a function type, remove the argument labels. This is important when we print the types of declarations, because those still do have argument labels on them.
Resolved bug number: (SR-)

Before merging this pull request to apple/swift repository:

[ ] Test pull request on Swift continuous integration.

Triggering Swift CI
The swift-ci is triggered by writing a comment on this PR addressed to the GitHub user @swift-ci. Different tests will run depending on the specific comment that you use. The currently available comments are:
Smoke Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please smoke test
    All supported platforms     | @swift-ci Please smoke test and merge
    OS X platform               | @swift-ci Please smoke test OS X platform
    Linux platform              | @swift-ci Please smoke test Linux platform

A smoke test on macOS does the following:

Builds the compiler incrementally.
Builds the standard library only for macOS. Simulator standard libraries and
device standard libraries are not built.
lldb is not built.
The test and validation-test targets are run only for macOS. The optimized
version of these tests are not run.

A smoke test on Linux does the following:

Builds the compiler incrementally.
Builds the standard library incrementally.
lldb is built incrementally.
The swift test and validation-test targets are run. The optimized version of these
tests are not run.
lldb is tested.

Validation Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please test
    All supported platforms     | @swift-ci Please test and merge
    OS X platform               | @swift-ci Please test OS X platform
    OS X platform               | @swift-ci Please benchmark
    Linux platform              | @swift-ci Please test Linux platform

Lint Testing
    Language     | Comment
    ------------ | -------------
    Python       | @swift-ci Please Python lint

Note: Only members of the Apple organization can trigger swift-ci.

Argument labels still persist on the function types of declarations,
so suppress them entirely when printing function types.

@swift-ci please smoke test


List of options missing from run

Version - v0.1.1-rc1
Comments:  There are some options that are no longer supported in rio and i just want to make sure we intended to no longer support these options.

[ ] --cap-add & --cap-drop
[ ] --entrypoint
[ ] --expose
[ ] --group-add (changed to group?)
[ ] --health-retries (changed to health-failure-threshold?)
[ ] --init
[ ] --ipc
[ ] --memory-limit (changed to memory?)
[ ] --metadata
[ ] --network
[ ] --pid
[ ] --publish
[ ] --privilege
[ ] --ready-cmd, ready-interval, ready-retries, ready-start-period, ready-timeout, ready-url
[ ] --restart (how do I run once?)
[ ] --stop-timeout
[ ] --security-opt
[ ] --tmpfs
[ ] --unhealthy-retries
[ ] --unready-retries
[ ] --update-order
[ ] --update-strategy

All of these have been addressed in refactor. Looking through the new params list I don't see anything not in use.


4 | Median of Two Sorted Arrays | Python

Median of Two Sorted Arrays -
What will change -
Type of Issue -
Please add/delete options that are not relevant.

[x] Adding New Code
[ ] Improving Code
[ ] Improving Documentation
[ ] Bug Fix

Programming Language
Please add/delete options that are not relevant.

[x] Python
[ ] C++
[ ] Java
[ ] SQL

Self Check

Ask for issue assignment and wait to get assigned to it before making Pull Request.
Add your file in the proper folder
Clean Code and Documentation for better readability
Add Title and Description of the program in the file

:star2: Star it :fork_and_knife:Fork it :handshake: Contribute to it!
Discord server ✉ - https://discord.gg/CXksGdn
Happy Coding,

@Yashica7 @SSKale1 Hey, I'd like to work on this problem. Can you please assign it to me?

Please assign me this issue

Can you assign me this issue?

I'd like to work on this issue.

can you assign me?


Support for addition of Multiple Host Domains in K8s Ingress Rules

Yarp.Kubernetes.Controller
We currently use Nginx as Ingress controller for our endpoints in K8s. However, there are a few shortcomings and as our technology stack is .NET based, we consider using Yarp instead.
Our Nginx rules are 'project' based, hence we use subdomains to organize and target individual related services.
Ingress manifest with multiple host domains for one external IP:
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: repro-1-ingress
  namespace: foo
spec:
  ingressClassName: yarp-ingress
  rules:
    - host: 'subdomain1.example.com'
      http:
        paths:
          - path: /
            pathType: Prefix
            backend:
              service:
                name: repro-1-service
                port:
                  name: http
    - host: 'subdomain2.example.com'
      http:
        paths:
          - path: /
            pathType: Prefix
            backend:
              service:
                name: repro-2-service
                port:
                  name: http

Current workaround, split into two ingress manifests:
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: repro-1-ingress-for-subdomain1
  namespace: foo
spec:
  ingressClassName: yarp-ingress
  rules:
    - host: 'subdomain1.example.com'
      http:
        paths:
          - path: /
            pathType: Prefix
            backend:
              service:
                name: repro-1-service
                port:
                  name: http

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: repro-1-ingress-for-subdomain2
  namespace: foo
spec:
  ingressClassName: yarp-ingress
  rules:
    - host: 'subdomain2.example.com'
      http:
        paths:
          - path: /
            pathType: Prefix
            backend:
              service:
                name: repro-2-service
                port:
                  name: http

Include host domain as part of the route naming
Due to Ingress manifest parsing and Yarp route id naming, this is not currently possible.
Hence, suggestion is to include host domain as part of the route naming. This reduces duplicating Ingress manifests and additionally bundles related host domains in Azure Ingress overview.

Fixed by #1951


无法登录

it is failed when I san the QR code to login. the page is still not logged in.

应该是微信读书禁止了iframe嵌套，做了点击劫持的防御


Getting an error when show modal view controller

Hey,
First, awesome project!
Got an error when I try to use the modal viewController.
Using the example project, I try to show modal view controller and in the second time I get this error:

Thanks in advance!

As a temp hotfix, we've removed this error altogether in release 1.2.3
We will add complete unregister logic when controllers are dealloced and then we'll be able to bring back the error
Leaving this issue open as a reminder, but the error should go away for now (1.2.3)


Be consistent when formatting enums

Summary
There's mixed usage when formatting enums in our error wrapping, older code seems to use .String() while newer code does not. The result is the same (since we do not implement Format on them).
Would be nice to be consistent with this and probably use the version w/o the explicit calls to .String().

For Admin Use

[x] Not duplicate issue
[x] Appropriate labels applied
[ ] Appropriate contributors tagged/assigned

note: should probably be done after 04-channel-upgrades is merged.

Hey Jim, I've noticed that there are a lot of issues that I could handle here, and I'm really happy to do so.  Just a quick FYI for you and the ibc team, I have very very pending baby coming, so I may be in and out but happy to handle some of these on a best effort basis :).


Update models to match entity diagram changes

The changes:

remove size field from generic groups table (not needed!)
move quantity from generic reservables table to materials (boats are boats and do not have a quantity
Add type to boats

Update commit

resolved with #14


Predicate complete? should return boolean.

Hello,
IMHO I think when people use complete?, they expect to get true or false instead of 0 and nil :open_mouth:.
What do you think?
Also I would say that this method should called completed? :innocent:, but this will require a minor version bump.
Thanks!

@JuanitoFatas hi! Thanks for the contribution!
No argument here, a boolean response makes sense.
RE: "completed", the usage of "complete" is as an adjective, since the noun is the "task list item". Is the item complete?

RE: "completed", the usage of "complete" is as an adjective, since the noun is the "task list item". Is the item complete?

Sorry for my naive knowledge of English. I concur with your argument.
I have updated documentation in Tomdoc fashion.
The error is due to a gem install timed out.
Gem::RemoteFetcher::FetchError: Errno::ETIMEDOUT: Connection timed out - connect(2) for "rubygems.org" port 443 (https://rubygems.org/gems/tzinfo-1.2.2.gem)
An error occurred while installing tzinfo (1.2.2), and Bundler cannot continue.
Make sure that `gem install tzinfo -v '1.2.2'` succeeds before bundling.
The command "./script/bootstrap" failed and exited with 5 during .

But I did not find the place to restart the test. Could you restart the tests?
Thanks!

@JuanitoFatas restarted the build.


google.maps  has no exported member named  WebGLOverlayView . Did you mean  OverlayView

An error is thrown while building up with ng serve:
google.maps  has no exported member named  WebGLOverlayView . Did you mean  OverlayView
"@googlemaps/three": "^4.0.6"

If you would like to upvote the priority of this issue, please comment below or react on the original post above with :+1: so we can see what is popular when we triage.
@markokitanoski1 Thank you for opening this issue. 🙏
Please check out these other resources that might help you get to a resolution in the meantime:

Check the issue tracker - bugs and feature requests for Google Maps Platform APIs and SDKs
Open a support case - Get 1:1 support in Cloud Console.
Discord - chat with other developers
StackOverflow - use the google-maps tag

This is an automated message, feel free to ignore.

That sounds like a problem with the types-package you are using, can you run npm ls @types/google.maps to see which version is installed? The current version is 3.54.3, and WebGLOverlayView was added sometime around the 3.47 release.

closing this due to inactivity. If the problem persists, please re-open with additional information.


Seems like the giphy response changed

PS...this is really important to fix, my 4-year old needs animated gifs of Lightning McQueen every so often ;)

@SocalNick Just tested and it looks good! Very cool to see someone still using this. I'll get this merged in and the npm package updated. Thanks for contributing!


feat: docker support

What does this PR do?

[x] Adds a feature
[ ] Fixes a bug
[ ] Edits documentation
[ ] Edits this repository
[ ] Something else

Things to check

[ ] Have you tested changes locally?
[x] Have you followed our linter rules?

Notes

[ ] New dependencies added
[x] Unsure of functionality

Description
Adds support for Docker.

You told me not to merge this yet, so I'll wait for you to do proper tests etc.

Also, we need to account for initial rethinkdb setup. Either by hooking it into the bot or running "npm run setup"

I'll try to account for that - the reason why we're not merging yet is that I haven't implemented db.wait() which waits for the databases to come up; I already received a few errors in production because of this.

Sounds good, I completely forgot about .wait()

@smolespi This should be ready for review now.

I had trouble getting it to function under WSL but Docker on Windows + WSL is finicky. Works on proper Linux systems (@TTtie demonstrated) so I'll merge it.


Support for iTunes in Wine on Linux?

Hi in the future could there be support for iTunes in wine on GNU/Linux?

Hi, I don't think there's a way to connect with an application running in a Wine wrapper (or at least I have no idea how that could be done), sorry!


Page (/Tab) Title (Order)

When viewing the online documentation, every page title starts with "RabbitMQ - " (this can be further exacerbated if the document specific title also starts with RabbitMQ, such as "RabbitMQ Configuration", resulting in "RabbitMQ - RabbitMQ Configuration"). If you have a number of tabs open and/or a low width window, this can make it difficult to relocate specific documentation.
Suggestion: Reorder the document titles so that the site title, "RabbitMQ", appears at the end and the specific document title is first. This will make it easier to locate open tabs.

We would welcome a pull request for this. Please base it on the live branch.

Done.


Document how to use MPIJobs with Kueue

It should be very similar to the documentation for Flux MiniClusters

/kind documentation

I'm doing a bit more research into Kueue and I'd like to work on this.
I am running into some trouble with getting Kueue to work with MPIOperator.

So I basically took the pi example from MPIOperator:
apiVersion: kubeflow.org/v2beta1
kind: MPIJob
metadata:
  name: pi
  labels:
    kueue.x-k8s.io/queue-name: user-queue
spec:
  slotsPerWorker: 1
  runPolicy:
    cleanPodPolicy: Running
    ttlSecondsAfterFinished: 60
    suspend: true
...

I apply the simple CQ/Q yaml in config/samples but I see that my MPIJob stays in suspended.  Is there anything else I am missing?
I used 0.3.0 release of Kueue.

/assign

@kannon92 Have you uncomment the below?
https://github.com/kubernetes-sigs/kueue/blob/cd747c596b2b56929c71abe7c6f94ab5c73609f9/config/components/manager/controller_manager_config.yaml#L33

Actually, I'm using the following manifests :)
apiVersion: kustomize.config.k8s.io/v1beta1
kind: Kustomization
namespace: kueue-system
resources:
- https://github.com/kubernetes-sigs/kueue/releases/download/v0.3.1/manifests.yaml
configMapGenerator:
- namespace: kueue-system
  name: kueue-manager-config
  behavior: replace
  files:
  - controller_manager_config.yaml

apiVersion: config.kueue.x-k8s.io/v1beta1
kind: Configuration
....
controller:
  groupKindConcurrency:
    Job.batch: 5
    MPIJob.kubeflow.org: 5
...
integrations:
  frameworks:
  - "batch/job"
  - "kubeflow.org/mpijob"

Should this just be enabled by default?

No, because if the user doesn't install mpi-operator, Kueue will produce errors in the logs

So I'm trying to approach this as a user:
I install Kueue this way:
VERSION=v0.3.1
kubectl apply -f https://github.com/kubernetes-sigs/kueue/releases/download/$VERSION/manifests.yaml

Is there an easy way to modify the manifests to enable MPI-Operator?  I guess I could download these manifest files and uncomment that yaml file?  It just seems to be a bit confusing for a user to have to do this?

So I'm trying to approach this as a user:
I install Kueue this way:
VERSION=v0.3.1
kubectl apply -f https://github.com/kubernetes-sigs/kueue/releases/download/$VERSION/manifests.yaml

Is there an easy way to modify the manifests to enable MPI-Operator? I guess I could download these manifest files and uncomment that yaml file? It just seems to be a bit confusing for a user to have to do this?

You don't need to edit manifests.
You can use the below kustomization.
https://github.com/kubernetes-sigs/kueue/issues/764#issuecomment-1550289219

Thank you!!  After I figured out how to use Kustomize, I was able to get an example running with Kueue

@tenzen-y it might be useful to add to the documentation how to configure parameters via kustomize, as an alternative to https://kueue.sigs.k8s.io/docs/installation/#install-a-custom-configured-released-version

@alculquicondor Agree. I will create a PR to update the docs (probably this weekend).


[staging] clang_{11,12,13,git}: enable RTTI

Motivation for this change
The LLVM version was recently updated from 7 to 11 on x86_64-darwin and there is a proposal to do the same on *-linux (#142593).
In #91682 the RTTI was enabled for prior clang versions, but not these. That lead to a regressions, e.g. in castxml https://hydra.nixos.org/build/161748474
Things done

Built on platform(s)

[ ] 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.

Makes sense to me, diff doesn't show any surprises.

I doubt this is necessary. LLVM_ENABLE_RTTI is a flag for llvm which doesn't appear to be used at all by the clang build and if so, it would be inherited via ${libllvm.dev}/lib/cmake/. Grepping for LLVM_ENABLE_RTTI in the clang dir for LLVM 11 and HEAD gives no results.

Well, castxml does build on the current staging-next, which includes this. Regarding the llvm flags, my assumption was that clang is built as an LLVM tool using definitions from the LLVM's cmake files and that's why some LLVM_* flags work. I see the set(LLVM_ENABLE_RTTI ON) in the LLVMConfig.cmake. Could be still some issue with the order in which the flags are processed and the configuration is imported.


Pressing "shift" when resizing a rectangle sets the aspect ratio to square; releasing it does not reset to non-constrained, keeps square

Expected behavior:

When creating a rectangle, holding shift should make it a square (constrained aspect ratio), releasing shift should reset to unconstrained creating.
When resizing an existing rectangle, holding shift should constrain to the aspect ratio of the rectangle before resize (not square if it wasn't square); releasing shift should reset to unconstrained resizing.

Yep, we should align it with how most apps do it, as you say.

1st point:

2nd point:

Actually different drawing tools use different heuristics on this. I prefer Figma approach on the problem. They always use X axis and they shift between constraint and non constraint when pressing shift without need for movement.
I have implemented initial aspect ratio respect at #768 and if we want to move towards what Figma does we will need to do two things:

Store initial resize element and not mutate it. So if you free transform and the move to constraint you have the data required to interpolate the deltas into the constraint move and viceversa.
When clicking shift we should apply the heuristics described in previous step so the element being dragged (creation) or resized (edition) gets transformed without need for mouse movement.

What you're showing from figma is IMO identical to what I've shown from Affinity.

Resizing (second point), yes, creating (first point), no.
Notice that when switching between free and constraints in Affinity current mouseX is not respected (and it's rather a proportion based how much you moved the mouse since mouse down event) and in Figma mouseX is respected at all times (which I personally prefer).

You're right. What Figma does it better.

This should be fixed now!


Fix #1229: add managed dependency version (29.0-jre) for Guava

What this PR does:
Adds managed dependency version 29.0-jre for Guava, removes explicit version definitions from poms
Which issue(s) this PR fixes:
Fixes #1299
Checklist

[n/a] Changes manually tested -- dependency upgrade tested via existing unit, integ, func tests
[n/a] Automated Tests added/updated -- same as above
[n/a] Documentation added/updated -- should not change visible behavior.

Ready for review (CI passed).

@tatu-at-datastax also see Dependabot alert about the Guava version..

@ivansenic Ah yes. I was curious about shadowed guava and +1 for removing that if possible. I think I'd like to do that in a separate issue/PR.
Also agree with explicit dependency: I'll see if I can find usages, add those explicitly.
Guava as a dependency can be pretty gnarly.

Oh and Dependabot. Yeah, maybe it makes sense to boost default version to even higher -- if I recall, that CVE is not often actually relevant, but all security tools flag it so it's just easier to upgrade. We should be able to do that.

@ivansenic @dougwettlaufer I will do some of simple changes here still, moving back to WIP. Apologies for confusion. Will let you know once this is ready

@ivansenic @dougwettlaufer I did bit more work as suggested, added notes on changes -- please let me know if there's anything else to address here. I will create a new issue for removing/reducing use of shaded guava dependency for follow-up work (and maybe one for Jackson deps too)

@ivansenic I added explicit Guava dependency in cases where module itself depends on guava (grepped for imports), removed if not. So did not leave dependency for transitive usage.

@tatu-at-datastax What's the state with this and what path are we taking at the end.. Maybe we can talk shortly today?

@ivansenic yes, was about to add a note. Let's sync up today.
My plan was to remove usage of un-shaded Guava, along with reducing usage in general where applicable.

Closing this in favor of #1253 (although going through similar issues over there -- but finally making progress).


Using platform 'redhat' fails with 'Package curl cannot be queried'

The RedHat naming convention is inconsistent The documentation refers to RedHat Enterprise Linux as simply "redhat" and the platform code accepts 'redhat' and 'el' as possible values to define it but various code, including unix/pkg.rb only look for the 'el' platform and fail when a platform of 'redhat' is provided.
The name 'el' isn't really descriptive. My preference would be to gut all references to redhat and el and only use the platform of 'rhel' to avoid having to cater for duplicate names while keeping it descriptive.

There is definitely confusion in the code.  We settled on using 'el-' exclusively, but won't crash if you happen to call something rhel or centos (we just don't treat them properly).  It is unlikely that I can do a full renaming run due to all of our internal dependencies, would extending to el-/redhat/centos be better?

I think the easiest option would be just to change the documentation to tell users to specify "el-" for centos/redhat. Supporting el-/redhat/centos will also solve it.

Sounds reasonable.  I'll get that filed internally.

I have updated the documentation to indicate only el- as a supported platform name.  I would also like to get stricter enforcement in beaker itself.

Follow up here:
https://tickets.puppetlabs.com/browse/BKR-17


NIFI-7410 Fix CLOB would be unreadable code in ExecuteSql or QueryDataBaseTable

https://issues.apache.org/jira/browse/NIFI-7410
Description of PR
fixes bug NIFI-7410
when ExecuteSql or QueryDataBaseTable processor trigger below code in JdbcCommon.java ,clob would be unreadable code（with Chinese character）,because it used
InputStream is = clob.getAsciiStream(); and  rec.put(i - 1, new String(buffer));
Update JdbcCommon.java when javaSqlType is CLOB or NCLOB in convertToAvroStream method, use the DataTypeUtils.toString(clob/nClob,(String) null, StandardCharsets.UTF_8)) method to get the String
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[ √] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?

[ √] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

[ √] Has your PR been rebased against the latest commit within the target branch (typically master)?

[√ ] Is your initial contribution a single, squashed commit? Additional commits in response to PR reviewer feedback should be made on this branch and pushed to allow change tracking. Do not squash or use --force when pushing to allow for clean monitoring of changes.

For code changes:

[ √] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
[ √] Have you written or updated unit tests to verify your changes?
[ ] Have you verified that the full build is successful on both JDK 8 and JDK 11?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
[ ] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
[ ] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?

For documentation related changes:

[ ] Have you ensured that format looks appropriate for the output in which it is rendered?

Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.

Is there a way to add a unit test for this? Maybe inserting Chinese characters into a Derby table with a CLOB column and reading the results?

Is there a way to add a unit test for this? Maybe inserting Chinese characters into a Derby table with a CLOB column and reading the results?

Thanks for reply. I will add a unit test for this situation.

Is there a way to add a unit test for this? Maybe inserting Chinese characters into a Derby table with a CLOB column and reading the results?

Hi @mattyb149 I have added one unit test.Clould you help me to check the PR of the NIFI-7403 - PutSQL's transactions support #4239 if you have time? Thanks.

Hey @mattyb149 - does it look good to you?

Manually fixed the checkstyle violations and added the license to make the RAT check happy. Merging to main. Thanks @KuKuDeCheng (next time, please make sure to add the header and check the build with -Pcontrib-check)


Minor plotting fixes and additions, change symmetrize default

Reference Issues/PRs
Closes #224
Closes #223
Closes #214
Closes #210
What does this implement/fix? Explain your changes.

Adds a log10 option as one of the possible graph transformations for plotting
Fixes the behavior of block-separating lines for small graphs
Adds a kwarg sort_nodes to specify whether or not to sort nodes by degree for heatmap and gridplot, default is False (this is up for debate, but this has confused multiple people).
Changes the default for symmetrize to avg

Codecov Report

Merging #226 into master will decrease coverage by 0.04%.
The diff coverage is 59.09%.

@@            Coverage Diff             @@
##           master     #226      +/-   ##
==========================================
- Coverage      86%   85.96%   -0.05%
==========================================
  Files          31       31
  Lines        1887     1895       +8
==========================================
+ Hits         1623     1629       +6
- Misses        264      266       +2

Impacted Files
Coverage Δ

graspy/simulations/simulations.py
95.16% <100%> (ø)
:arrow_up:

graspy/utils/utils.py
91.17% <100%> (ø)
:arrow_up:

graspy/plot/plot.py
51.8% <55%> (+0.48%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 065eccf...ef12eff. Read the comment docs.


internal: remove accidental code re-use

internal: remove accidental code re-use
FragmentKind played two roles:

entry point to the parser
syntactic category of a macro call

These are different use-cases, and warrant different types. For example,
macro can't expand to visibility, but we have such fragment today.
This PR introduces ExpandsTo enum to separate this two use-cases.
I suspect we might further split FragmentKind into $x:specifier enum
specific to MBE, and a general parser entry point, but that's for
another PR!
bors r+
🤖

huh, looks like bors messed up the commit message in https://github.com/rust-analyzer/rust-analyzer/commit/b73b321478d3b2a98d380eb79de717e01620c4e9

It’s not bors, it’s me :-)


command/internal/help_common_display_v6: add entry for app delete

What Need Does It Address?

I found it slightly confusing to have the cli help text not explicitly show the app delete command
Who Is The Functionality For?

New Pivots or people who are just starting to learn how to use the cf command. I did not intuitively think to type cf delete to remove my cf pushed app
How Often Will This Functionality Be Used?

Often
Possible Drawbacks

It may not work; I was unsure where to make the change and was unable to verify that it worked after build
Why Should This Be In Core?

It's in the core help text
Description of the Change

Show delete,d in the help text for cf, which is hopefully as simple as including it in the CommonHelpCategoryList definition for the Application lifecycle category
Alternate Designs

None
Applicable Issues

How Urgent Is The Change?

Not urgent
Other Relevant Parties

Thank you @johncornish, much appreciate your help here.

Thanks @johncornish!


seed template

For migration we can define custom template via config e.g.
    'templates' => [
        'file' => __DIR__ . '/src/Database/Migration/MyCustomTemplate.txt.dist'
    ],

I searched documentation and for seeders we use only default template from
https://github.com/cakephp/phinx/blob/master/src/Phinx/Seed/Seed.template.php.dist
Question
How can we define custom template for seeder in config?
This is probably feature-request
Thank you

I'd like to be able to do this from the CLI also.

One more on the line. In our case, it's because code style differs and we don't use auto-fixers, just lint warnings - thus, any newly generated file will need manual fixing before submission.
Bonus: didn't find in the docs there was a config for templates, just aliases. Quite useful.


Creating Manifest file might be interrupted

Describe the bug
If an error happens here in the make_paths_relative(), manifest.json file will be empty.
Expected behaviour
The manifest file should be created correctly in any case even if the program ends with an error.
To Reproduce
Handle the possible errors when calling make_paths_relative() .

Actually I realised it, when this error happened.

We already have os.path, we need to make sure we use that so no pathlib objects are leaked into manifest paths, which are expected to be strings.
I would recommend refactoring the code that uses pathlib to use os.path.join operations instead


Create LICENSE

@asafonov

fdroid metadata has MIT license
this pr will add license in repo
please also let me know if license is incorrect

thank you!


helper for testing activations

This commit adds a test helper which captures a common pattern of extracting activation id, polling for activation to be completed, and then checking the result. This method will always the activation id, activation record, and any command failures should invariants fail. In doing this, turned some unnecessarily blocking activations to non-blocking ones. This makes the tests more focused and reduces likely hood of false failures.
@psuter should also review.
PPG 513.

Looks good to me, literally and figuratively.


Weird Strict-Transport-Security max-age value

https://github.com/quarkusio/registry.quarkus.io/blob/937bfc0d309099d46db04276dedfe2f3ee3e462c/src/main/resources/application.properties#L24
It seems 360 is not a good value for max-age, 1 year would be max-age=31536000:
https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Strict-Transport-Security

max-age=
The time, in seconds, that the browser should remember that a site is only to be accessed using HTTPS.

@ia3andy thanks for the ticket! Want to submit a PR fixing this?


eq-324 additional paradata

Changes

added analytics.js module to interface with google analytics event tracking
added hooks in template with data to be sent to analytics
fires events according to errors generated
fires events when user clicks guidance toggle

How to test

npm run compile
visit a page and submit with errors
verify events are being caught by analytics
click on guidance toggle
verify events are being caught by analytics

Who can test
@bennpearson

Be good for @bennpearson to CR and test this once @warrenbailey has done his bit.

@bennpearson ready for you to review.
We probably also want one of the backend devs to review my URL changes, so either @LJBabbage or @weapdiv-david

Your bits look fine Warren bar the default startup page. After running run_app.sh, you get a url that looks like http://localhost:5000/questionnaire/1/sid/introduction


Support aws Lambda function URLs

https://docs.aws.amazon.com/lambda/latest/dg/lambda-urls.html

@arthurchumak function urls worked for me, maybe they share the same payload?

I had to make such hotfix, to allow express router work


Replace Reflection in serializer for Closures

Should be faster... which is always good.
Inspiration: https://github.com/jimmyoak/arrayed-object/blob/master/src/ArrayedObject/ArrayedObjectFactory.php#L43-L53

Solved: https://github.com/nilportugues/serializer/commit/1a592692e2c8c7f421b521c4c38a05bf61d22f9e
Te dedico el commit @jimmyoak :+1:

Vaya tela 😅😂


Customer facial features vary.

Renamed features from 'near/far' into 'z0, z1, z2'.
Added ambient wiggle for beak mouth.

Turbo Fat.x86_64 does not belong in git.


Downstream components integration

This issue keeps track of the work required for integrating feature/utxo-hd with:

[ ] Mithril
[ ] Wallet (maybe not, confirm)
[ ] db-sync (maybe not, confirm)

We'll notify the downstream clients when we release the first version of UTxO-HD (#28) and open integration support issues on demand.


fix code error

refer https://issues.redhat.com/browse/ACM-7029

/assign @yanmxa

Nice Catch!
/LGTM


Create add.c

hello world
What the program do ?
it prints hello world
In what programming language it is written?
c language

This pull request do not contains files in specific folders. Please fix it and reopen


WIP: Start adding more DC stats

closing for now, can use as reference and revisit in beta explorer


OpenVPN: User specific client export view

The current OpenVPN client export view was made for admins only it seems.
Assigning this single view for access by a regular user will give more options than intended, which will not allow any kind of end-user self-service.
It would be great if there was a lightweight view for the end-user were s/he may only download a configuration file especially prepared for personal use, no access to other users certificates. Also, generating a certificate on the fly would be neat.
It might not be pretty straight forward though as the admin would need to be able to set some presets, e.g. a canonical hostname (basically everything that the current client export view will offer, just as a preset (maybe even hidden).

This issue has been automatically timed-out (after 180 days of inactivity).
For more information about the policies for this repository,
please read https://github.com/opnsense/core/blob/master/CONTRIBUTING.md for further details.
If someone wants to step up and work on this issue,
just let us know, so we can reopen the issue and assign an owner to it.


Question: MIME Content-Type Type with grammar files of *.pegjs file extension

Recently we've started adding support for this parser generator into our project and I'd like to say it is a godsend in making things a little more readable in our code. A Thank You goes out to your project maintainers from our maintainers. :)
Onto the question.
I've noticed that this project has picked the file extension of *.pegjs for the grammar files...

We were wondering if there is a standardized MIME Type that has been decided on for these grammar files?

Currently we are using text/javascript however I have noticed that there is some uniqueness in the grammar language that doesn't appear to conform fully to JavaScript specifications... so this may not be the right type but is somewhat close.
The reason why I ask is when we currently host a set of grammar files with an extension of .pegjs on the server. When it is typed into the address bar of the browser... the browser t typically attempts to download the file as a BIN file (default action for unknown Content-Type is binary in this browser). So rather than risk a security warning from some other site service we coerce its value to one that is clear text (so we can read it and possibly minify it at some future date) and the nearest match for what the syntax is.
This MIME type (a.k.a. Content-Type request header) can also be used in web and external editors to determine Syntax Highlighting. Since peg.js grammar files don't appear to registered with W3C/IANA/IETF I presume that the x- needs to be done. (see below possible suggestions if I may).
So basically the question reiterated is.... What should we be using according to this projects official specification for grammar files with MIME Type?
Possible suggested naming for MIME/Content Type:

text/x-pegjs-grammar (We haven't tried to see what the server/browser does with this natively yet but will notate when tested)
text/x-javascript-pegjs-grammar (not entirely sure about this one but may work with most programs out there that prefer MIME and start matching at the beginning and choose JavaScript as the nearest match for Syntax Highlighting or other operation.)

I’m glad that PEG.js serves you well :-)
As for the MIME type, PEG.js grammars are not JavaScript, so text/javascript is technically incorrect. I’d suggest text/x-pegjs.
For further questions please use the PEG.js Google Group. Issues are intended for bug reports and feature requests. Thanks.

I’d suggest text/x-pegjs.

Great... thank you so much.

Issues are intended for bug reports and feature requests. Thanks.

Awesome... feature request is to have this placed in the README.md or elsewhere for the docs then.

I just found that according to RFC 6838, Section 3.4 and RFC 6648, using the x- prefix for MIME types is deprecated. This makes the text/x-pegjs recommendation obsolete.
Now, reading through RFC 6838, Section 3 it doesn’t look like any registration tree is suitable for PEG.js grammars. The standards tree, vendor tree, and personal tree all require registration with IANA, which I’m not going to go through. And the unregistered x. tree is “for types intended exclusively for use in private, local environments”. So, at this point, I can’t really recommend any MIME type for PEG.js grammars beside text/plain.

Well that is something I seem to have missed too... a lot of developers aren't going to be happy with this... although finding the adoption date for the RFC (request for change) might be prudent... I don't exactly see that other than the RFC date itself.
3.1 in the below quote uses an abstract "magic" word of "SHOULD" as well... which doesn't mean absolute... but that's a grammar thing.

Recommendations for Creators of New Parameters

Creators of new parameters to be used in the context of application
protocols:

SHOULD assume that all parameters they create might become
standardized, public, commonly deployed, or usable across
multiple implementations.

SHOULD employ meaningful parameter names that they have reason to
believe are currently unused.

SHOULD NOT prefix their parameter names with "X-" or similar
constructs.

Note: If the relevant parameter name space has conventions about
associating parameter names with those who create them, a parameter
name could incorporate the organization's name or primary domain name
(see Appendix B for examples).

So, at this point, I can’t really recommend any MIME type for PEG.js grammars beside text/plain.

Well 3.1 "should" apply here. ;) Have something in mind that "should be created"?
Thanks for the followup. :)

although finding the adoption date for the RFC (request for change) might be prudent... I don't exactly see that other than the RFC date itself.

As far as I can tell, a RFC starts to apply immediately after it is published.

Well 3.1 "should" apply here. ;)

Well, the most authoritative text is RFC 6838, Section 3.4, which says quite clearly, that x- prefixed types do not belong to the unregistered tree. Together with the rest of Section 3 this implies they fall into the standards tree, which requires registration.

which says quite clearly, that x- prefixed types do not belong to the unregistered tree.

Semantics aside, because my comprehension seems a bit different than what you are saying... using text/plain may inhibit development of, at the very least, syntax highlighting routines, in which I have been assisting with development in other projects throughout the decades, and other MIME type applications for it. There is always the fallback to basename.extension detection but that methodology is also "strongly discouraged".  There are some projects I know for example that utilizes the x. tree and those additons are more recent than 1995.
I think the adoption rate for what "might" be used is determinate on how many people utilize a particular naming schema... and someone besides this project may register it for you at a later date... hence the magic word of "might" in the RFC. So if you were to "decide" on  a variant or exact of my original suggestion above we would definitely be a party to moving something forward with some "standardization". I understand that you may be reluctant to register... I'm not sure I would want to either but I think we're going to stick with it across the projects that I know use it... it is highly unlikely that a collision would occur especially with the grandfathering. My experienced guess is that the complaint in the RFC is because they are lazily coding with matches in whatever systems they use.

Here's an example of a newer x. tree addition....
x-matroska

that's part of the ogg system specific to audio with matroska. I am quite sure this post-dates the RFC. There appears to be hundreds in the *nix tree file associations as well... some older some newer.

As I said, I don’t want to go through the registration procedure, and that includes also helping somebody else going through it.
In any case, RFCs are just recommendations and you are free to ignore them. If you don’t care about compliance, you can use my original suggested type or e.g. application/pegjs freely. It’s just that I don’t want to encourage this officially (and put it into documentation). For private use, it’s completely legal to use e.g. application/x.pegjs. (I think application top-level type is better than text after reading through text in RFC 6838, Section 4.2.)
And yes, the media type registration procedure is inflexible and I think it undermines usability of media types. I’d much rather see something less rigid in place.


[2.6] Ingress, non accessible Certificates from other namespaces can be choosen

Rancher Server Setup

Rancher version: 2.6
Installation option (Docker install/Helm Chart):

RKE1, kubernetes 1.21

Describe the bug
Inhouse ingress is used.
If you create / update ingresses you can choose certificate secrets that do not belong to the current ingress namespace
To Reproduce

Create 2 namespaces e.g. foo & bar
Create certificate in foo namespace
Create ingress in bar namespace
Under Certificates you can choose foo secrets

Result
Ingress fails silently, because bar/test-certificate does not exist
Expected Result
Certificates should not be choosable, since they belong to another namespace

Per @vincent99 this is likely a UI bug, transferred to rancher/dashboard.

on 2.6-head commit id: 1a57856

For ingress, under certificates tab, only those available for that namespace is listed.


HEIMAN WarningDevice-EF-3.0 - settings a value crashes whole adapter

What happened?
When using the smart siren/router HEIMAN WarningDevice-EF-3.0, whenever I set a value (e.g. mode to "burglar"), the whole adapter crashes - all values go to orange/not connected.
Still, everything is working correct in Zigbee2MQTT itself!
What did you expect to happen?
The value I changed is not send to the alarm device - and it does crash the whole adapter / all device go offline in the adapter.
Still, everything is working correct in Zigbee2MQTT itself!
I can change values there directly! So it has to be a bug in the adapter.
Adapter then restarts automatically and sometimes it is then working again (for all other devices) and sometimes I have to reinstall the adapter...
How to reproduce it (minimal and precise)
Set any value will crash the adapter.
 Version 2.13.4 in /opt/iobroker/node_modules/iobroker.zigbee2mqtt, node: v18.16.1, js-controller: 5.0.16

zigbee2mqtt.0
2024-01-17 08:51:55.155
warn
Cannot 2 Lia/Noemi Temperatur create Device from Exposes!

zigbee2mqtt.0
2024-01-17 08:51:55.152
error
Cannot check file existence of "cfg.f.zigbee2mqtt.0$%$WSDCGQ11LM.jpg$%$data": Connection is closed.

zigbee2mqtt.0
2024-01-17 08:51:54.628
info
terminating

zigbee2mqtt.0
2024-01-17 08:51:54.443
info
Connect to Zigbee2MQTT over websocket connection.

zigbee2mqtt.0
2024-01-17 08:51:54.419
warn
Terminated (UNCAUGHT_EXCEPTION): Without reason

zigbee2mqtt.0
2024-01-17 08:51:53.432
warn
Start try again in 1 seconds...

zigbee2mqtt.0
2024-01-17 08:51:53.213
error
Cannot set properties of undefined (setting 'mode')

zigbee2mqtt.0
2024-01-17 08:51:53.212
error
TypeError: Cannot set properties of undefined (setting 'mode') at state.setter (/opt/iobroker/node_modules/iobroker.zigbee2mqtt/lib/exposes.js:1093:52) at Z2mController.createZ2MMessage (/opt/iobroker/node_modules/iobroker.zigbee2mqtt/lib/z2mController.js:35:36) at Zigbee2mqtt.onStateChange (/opt/iobroker/node_modules/iobroker.zigbee2mqtt/main.js:336:49) at Zigbee2mqtt.emit (node:events:513:28) at Immediate. (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/lib/adapter/adapter.js:8506:53) at process.processImmediate (node:internal/timers:476:21)

zigbee2mqtt.0
2024-01-17 08:51:53.210
error
unhandled promise rejection: Cannot set properties of undefined (setting 'mode')

zigbee2mqtt.0
2024-01-17 08:51:53.209
error
Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().

Log
No response

check now GIT version

Installed GIT Version, still same error
`

zigbee2mqtt.1 | 2024-01-26 12:21:36.467 | error | TypeError: Cannot set properties of undefined (setting 'mode') at state.setter (/opt/iobroker/node_modules/iobroker.zigbee2mqtt/lib/exposes.js:1120:54) at Z2mController.createZ2MMessage (/opt/iobroker/node_modules/iobroker.zigbee2mqtt/lib/z2mController.js:35:36) at Zigbee2mqtt.onStateChange (/opt/iobroker/node_modules/iobroker.zigbee2mqtt/main.js:336:49) at Zigbee2mqtt.emit (node:events:517:28) at Immediate. (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/lib/adapter/adapter.js:8516:53) at process.processImmediate (node:internal/timers:476:21)
-- | -- | -- | --
zigbee2mqtt.1 | 2024-01-26 12:21:36.464 | error | unhandled promise rejection: Cannot set properties of undefined (setting 'mode')
zigbee2mqtt.1 | 2024-01-26 12:21:36.463 | error | Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().

`


support for v2

Hey, any plan to support dialogflow v2? in particular the streaming option

+1

Hi @moshekr ,
I will check the technical specs of dialogflow v2 and give you a road map the next days.

+1

+1

Hey @spoeck any update ? :) Thanks for the useful work again! 🎉

Update:
I'm working on support for v2. I will release a beta next week!

Update:

Created a branch 'dialogflow-v2'
Because there is still no official sdk for android and javascript for v2 I separated the speech-to-text functionallity from dialogflow and just use the REST API (is working for v1)

For the REST calls for V2 I would need some help. Can someone give me a example REST POST? I don't understand the URL param ({session=projects//agent/sessions/})

Thanks @eggybot for the auth setup link!
requests with speech/text/events are working (see in the example app on android)
The link is something like this: https://dialogflow.googleapis.com/v2beta1/projects/testv2-3b5ca/agent/sessions/0:detectIntent

testv23b5ca is my ProjectId
0 is the sessionId which I create while setting the configuration (random number in real)

BUT: Contexts are NOT working. And I think there is a new mechanism. In V1 you just put the contexts into the request and everything fine. But in V2, do I have to create the contexts separatly before making a text request?
Does anyone know how to use the context endpoint? https://dialogflow.com/docs/reference/api-v2/rest/v2beta1/projects.agent.sessions.contexts/create

Ah damn !!! now I got it
When you wan't to set a context for example deals, instead of setting:
{
      "name": "deals",
      "lifespan": 1
}

in V2 you have to set
{
      "name": "projects/testv2-3b5ca/agent/sessions/0/contexts/deals",
      "lifespanCount": 1
}

so I will concat the path of the name in background so that you can set the context in V2 as below:
{
      "name": "deals",
      "lifespanCount": 1
}

Published v3.0.0 with Dialog-V2 support!

Thanks!

@spoeck : You mentioned about context being reset, and thats what I get when trying your sample on a flow that has a followup intent. The base intent seems to be working fine but when i speak into the app for the followup, it seems to not take the original context. Do we need to manually setup the contexts ?

@eggybot , Its the same in the sample (https://github.com/innFactory/react-native-dialogflow/tree/master/example). Tried to use it against one of my simple projects which only has 2 intents -- main and a followup. The main intent got recognized properly but the followup dint.


Which Chromium flavors to build on Hydra?

Currently we only build the following package on Hydra:

chromium (on both nixos-unstable and nixos-stable)

But since the build times are very high, it might make sense to add additional popular flavors.
Potential candidates (+ combinations):

ungoogled-chromium: Pretty popular and IIRC already includes the VA-API patches by default

Depends on https://github.com/NixOS/nixpkgs/pull/76082 (actually there are multiple PRs)

chromium-vaapi: With the VA-API patches

Would be great if we could enable these patches (actually only one small patch) by default
Last time it was disabled due to issues with the radeon driver (at least on some AMD GPUs)
I can confirm this issues with my HD 6950, but VA is only enabled with if I use --ignore-gpu-blacklist - i.e. if the blacklist is good enough it might be fine. -> Would be great if we could apply the patches but VA is disabled by default (independent of the GPU).
Very useful for laptops! Basically required e.g. for/beyond 1080p@60Hz on YouTube and Google Stadia.

chromium-widevine: Shouldn't require a rebuild (TODO: verify)
chromium-ozone: For native Wayland support

Alternative: https://github.com/colemickens/nixpkgs-chromium
Might soon be the default (finally): https://www.phoronix.com/scan.php?page=news_item&px=Ozone-Wayland-Next-Year

Unlikely candidates:

chromiumBeta, chromiumDev: Our support should focus on the stable channel.

Testing: chromium should always work, other flavors should be provided on a best effort basis (or have a dedicated maintainer).
Ideally we'd have at most two different flavors to keep it manageable and avoid unnecessary Hydra overhead.
What other distributions do: TODO, see e.g. https://repology.org/projects/?search=chromium
Additional resources:

https://chromium.googlesource.com/chromium/src/+/master/docs/gpu/vaapi.md#VaAPI-on-Linux

Suggests that at least --ignore-gpu-blacklist is always required

https://chromium.googlesource.com/chromium/src.git/+/master/docs/ozone_overview.md
...

Status: WIP, please add feedback, suggestions, general thoughts, etc.

This issue has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/would-it-be-possible-to-provide-binary-cache-for-chromium-vaapi/6229/2

Please that would be a very good improvement. It would have a positive effect on the battery. On my Intel NUC it takes over 16 hours to compile... I'd be delighted.

This issue has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/nixos-unstable-hasnt-been-updated-in-a-while/6584/13

There's now a draft for chromium-vaapi: https://github.com/NixOS/nixpkgs/pull/85076
But IMO (and as already discussed in that PR) chromium-vaapi isn't really worth the overhead (building +  maintaining). Therefore I'm more in favor of enabling VA-API by default (vs. an additional package)
As an alternative I considered adding chromium-experimental with Ozone + VA-API (and possibly additional features). I'd prefer that approach, but unfortunately that works less reliable and seems not ready for Nixpkgs yet (e.g. it required custom patches or a Nixpkgs package for minigbm when I tested it with M80).
Back to enabling VA-API by default:
One issue is that Chromium seems to lacks a more fine grained control than ignore-gpu-blacklist (which ignores all entries - not just VA-API - which is mainly important as some users might already use that flag for other purposes). Another issue is that VA-API causes some overhead to maintain (e.g. M81 required two additional patches: https://github.com/NixOS/nixpkgs/commit/b533f103452d5f39dace33a1b76ff88ac8f0f21f) and might break as it is not officially supported. Therefore I'd suggest that we try to enable it by default as an experimental feature, but disable it again if it causes too many problems. It is important to note that VA-API was already enabled once by default and that didn't work out. However, I think if we discuss this first, run some tests before enabling it, and don't backport it to stable right away we should be able to merge such a change without causing too many problems at once (which would require reverting that change).
E.g. one interesting possibility to look into would be to enable disable-accelerated-video-decode and disable-accelerated-video-encode by default. If that works as expected this shouldn't break any existing setups, even with ignore-gpu-blacklist.

E.g. one interesting possibility to look into would be to enable disable-accelerated-video-decode and disable-accelerated-video-encode by default. If that works as expected this shouldn't break any existing setups, even with ignore-gpu-blacklis

How about this:
chromium-vaapi = callPackage ../applications/networking/browsers/chromium ((config.chromium or {}) // { useVaapi = true; });
chromium = chromium-vaapi.override { commandLineArgs = "--disable-accelerated-video-decode --disable-accelerated-video-encode"; };

chromium-vaapi and chromium should only have different wrappers so no rebuilds required!

The situation has significantly improved since I opened this issue and (IMO) we can close it now :tada:
We currently build the following on Hydra:

chromium: With VA-API and Ozone support now :)
ungoogled-chromium (should also support VA-API and Ozone)


thread_pool_http_server crashes with multiple connections

When testing the thread_pool_http_server.cpp example using Apache Benchmark, the HTTP server crashes, e.g.:
ab -n 10000 -c 1000 <IP_ADDRESS>:80/hello

or
ab -n 10000 -c 1000 -k <IP_ADDRESS>:80/hello

Revert server.hpp to using an accept_handler without a socket parameter. next_socket_ member variable restored.
next_socket_  now created from next_strand_ when in thread safe mode.
Calls to ASIO::bind_executor removed from connection.hpp to match asio thread pool example HTTP Server 3.

This problem occurs using boost 1.84.0

This issue is now only observed in Visual Studio debug mode.
The issue does not occur in Visual Studio release mode nor GCC debug or release mode.


package.json's typings

why package.json's typings is "./typescript/typings.json"
while use vscode, import phaser = require("phaser");
it cannt solved it as a module.
Its ok while I replace it with ./typescript/phaser.comments.d.ts

Because it used to work fine this way, and then TS changed again. The latest version now uses a direct link to the defs file.


Icon alignment changes on small screens

I'm working on Emberjs App and installed ember-cli-materialize. It was working all fine until you pushed Google API fonts for icons. They works fine on screens above small but on small they gets stick to the top of the container.  I'm not using any explicit margin or padding. I'm importing http://fonts.googleapis.com/icon?family=Material+Icons in app.scss and using icons the usual way <i class="material-icons">search</i>
Check it out on this CodePen
Preview:

I went to inspect element and found out that there is one css property getting generated
nav ul{
  margin: 0;
}

If I remove this margin property icon comes back to center.

@cchandurkar If you do that you broke the icons outside the navbar.
The problem it's about the navbar:
nav i.material-icons {
  line-height: 56px;
}


Confetti Falling

Confetti falling on clicking the button using javascript.

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)

Checklist:

[ ] My code follows the style guidelines(Clean Code) of this project
[x] I have performed a self-review of my own code
[ ] I have made corresponding changes to the documentation
[x] I have added tests/screenshots(if any) that prove my fix is effective or that my feature works

Added Screenshot of Output in README files

Mention Your Issue no which you have to fixed

#265


Use react-dom for 0.14.0 compability.

Fixes React 0.14 warning.

#114 seems better to me

This is fixed in https://github.com/gaearon/redux-devtools-log-monitor that is being split away from the main repo. I don't intend to merge this here, so closing. See https://github.com/gaearon/redux-devtools/pull/132 to track the split.

You can track it here: https://github.com/gaearon/redux-devtools/issues/152

Please try 3.0 Beta 2 and leave feedback.
It includes React 0.14 support: https://github.com/gaearon/redux-devtools/releases/tag/v3.0.0-beta-2


Selecting a cell on one organism type and then switching organism type results in a page crash

Steps to reproduce:

Make sure "homo sapiens" is selected as the organism type
Select B-1A B cell in the cell filter
Switch the organism type to "mus musculus"
Page should crash

Desired outcome:

Keep Organism selection bar where it is currently
When user has any genes or filters selected, changing to a different organism will prompt a confirmation dialog.
If confirmed, page should reset to default page with all filters and settings reset

Figma designs
Prototype

@signechambers1 to propose a flow for switching organism when cell type filter is used cc @karenliang0

Options from @karenliang0:

Disable the ability to select the other organism with a hover over explanation as to why it's disabled
Or allow users to change to the other organism and the cell type filter that affects it will clear itself
we can also add a dialog that has them confirm the organism switch if there are cell types that will not be available in the organism they're switching to

I think the organism filter is a little misleading - it is more of a setting since genes and cell types don't transfer across organism (though filters do). If we go with optoin #1, when would organism filter be enabled?

Discussed with @karenliang0, we aligned on desired outcome listed in the ticket.

Morning @karenliang0 !
I just moved the Organism selector to the top. Does the spacing look good?
Thank you!
Private Zenhub Image

@karenliang0 curious what you think but I would put the organism selector above the filters header.

Yeah I thought about that either! But if we move the "Filters" header below organism selector, do we need another header in the Filters header's current place or just leave it blank?

https://github.com/chanzuckerberg/single-cell-data-portal/issues/5778 is a duplicate of this!
I think we can close #5777 and Seve's fix can still get merged, but keep #5778 open, so we can address the UI change
CC: @seve

Putting this back to disorder until design is finalized

@tihuan @signechambers1
Adjusted outcomes and added final designs and link to the prototype.
@tihuan sorry for the back and forth, we'll be keeping the organism selector where we previously had it (below filters but above the rest of the items in the panel). We're adding a confirmation dialog to inform folks that all genes and filters will be cleared if they try to change organism when they currently have any filters / genes selected. If they do not have anything selected, we will allow them to switch organism without a confirmation dialog prompt.
Let me know if there are any questions - more than happy to walk you through it in a call! Just let me know if that would be more helpful :)

@tihuan looks good except the spacing between tissues after you switch the organism is off - i think @seve fixed this in a separate PR. Otherwise LGTM

Awesome thanks so much, Signe! Yeah that should be addressed in https://github.com/chanzuckerberg/single-cell-data-portal/pull/5938 👍
Thank you!

Looks great, Timmy! Thanks so much 👏

Hurray! Thanks for the swift review, @karenliang0 !! ❤


Help text isn't working on subcommands

usenpalank3m1:yaas karthik$ yaas host --help
usage: yaas host [-h]

optional arguments:
  -h, --help  show this help message and exit

It should show the help texts of subcommands like list and show.

Will be fixed by https://github.com/dmtucker/yaas/pull/29

@karth295 if you mention an issue in the PR, it will close itself when the PR merges. I.e.:
Fixes #26. blah blah blah describe describe describe


installation

I was able to build thundergbm, but now how do I install it?

Do you mean installing ThunderGBM as a system library to allow access from "everywhere"? ThunderGBM doesn't support this currently. We will consider this in our future upgrade if many users have such requirements.

ThunderGBM now supports system wide installation using Python. Please check it out from the lastest code and instructions.


Can Timeline support author date as an option?

I'm trying out the new timeline view in production VS Code and loving it.
Looks like the entries for git commit history are showing committer date. Would it be possible to add an option to switch this to author date?
My use case is that we migrated our repo from Perforce to Git last year and in doing so we have a huge number of commits all with the same date, but each have the original perforce submit date preserved in the git author date field.
Cheers, Ben

Closed by d8b1776

Thank you!


[QUESTION] ProcessorLoop

Describe the question
Could you please explain below code in TaskResponseProcessor or TaskAckProcessor? What's the propose? Can it be removed?
` while (Stopper.isRunning()){
TaskInstance taskInstance = processService.findTaskInstanceById(taskResponseEvent.getTaskInstanceId());
        if (taskInstance != null && responseStatus.typeIsFinished()){
            break;
        }
        ThreadUtils.sleep(SLEEP_TIME_MILLIS);
    }

`
Which version of DolphinScheduler:
-[dev]

please refer [DISCUSS] fault-tolerant on dev mail
master synchronous wait asynchronous queue data flush to db prevent master down，then worker retry

can you give me a link?

Use your own mailbox to send an email to<EMAIL_ADDRESS>with arbitrary subject and content.

Receive confirmation email and reply. After completing step 1, you will receive a confirmation email from<EMAIL_ADDRESS>(if not received, please confirm whether the email is automatically included in the folder of spam, promotion mail, subscription mail, etc.) . Then reply directly to the email, or click the link in the email to reply quickly, the subject and content are arbitrary.

Receive a welcome email. After completing the above steps, you will receive a welcome email with the theme WELCOME to<EMAIL_ADDRESS>and you have successfully subscribed to the Apache DolphinScheduler (Incubating) mailing list

ok,thx.


Add in-depth guide to setting custom styling in /assets/css/style.scss

Please could an in-depth guide be added with details of what things can be changed/overridden and how to override them as currently it's non-existent and we have to read through the _sass/jekyll-theme-cayman.scss to find what we can change and how to

see _sass/variables.scss


UI does not account for timezones in challenge period handling

A user just sent a transaction before the challenge period was over because the UI told him otherwise.
See https://github.com/Proof-Of-Humanity/proof-of-humanity-web/issues/454

Apparently it does. This was an issue with the user's clock.
Reopen we have indication of otherwise.


Feature/google auth

This pull request implements Google OAuth authentication, enhancing the login experience with DaisyUI and updating the relevant URLs and requirements.

Well done.

ment

Good job


Separate API and update types

Codecov Report

Merging #35 (0cb7971) into main (ae4bdc5) will increase coverage by 3.14%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main      #35      +/-   ##
==========================================
+ Coverage   55.26%   58.41%   +3.14%
==========================================
  Files          39       39
  Lines         418      428      +10
  Branches       57       58       +1
==========================================
+ Hits          231      250      +19
+ Misses        172      164       -8
+ Partials       15       14       -1

Impacted Files
Coverage Δ

...olkovlabs-balenasupervisor-datasource/api/index.ts
100.00% <ø> (ø)

.../volkovlabs-balenasupervisor-datasource/api/api.ts
21.78% <100.00%> (-1.03%)
:arrow_down:

...c/volkovlabs-balenasupervisor-datasource/api/v1.ts
100.00% <100.00%> (ø)

...kovlabs-balenasupervisor-datasource/types/index.ts
100.00% <100.00%> (ø)

...rc/volkovlabs-balenasupervisor-datasource/utils.ts
70.00% <100.00%> (+3.33%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


as sugested by @zz123happy make cache_index_and_filter_blocks configurable

As sugested in https://github.com/arangodb/arangodb/issues/11577 add a configuration flag.
https://github.com/facebook/rocksdb/wiki/Write-Buffer-Manager upstream flag documentation.

http://jenkins01.arangodb.biz:8080/view/PR/job/arangodb-matrix-pr/10172/

Please also log the value of these config options as discussed!

http://<IP_ADDRESS>:8080/view/PR/job/arangodb-matrix-pr/10193/

http://<IP_ADDRESS>:8080/view/PR/job/arangodb-matrix-pr/10198/