Django 3 support.

Closes #354.
Django 3 "remove[s] private Python 2 compatibility APIs", which is to say it removes a number of utility methods that were either already provided by six or otherwise were used in bridging the old and the new python.  This pull request makes django-waffle work with Django 3 by making just 3 changes.

Add six to the requirements.
Replace the result of callingavailable_attrs with functools.WRAPPER_ASSIGNMENTS (cf https://docs.djangoproject.com/en/2.2/_modules/django/utils/decorators/)
Use the python_2_unicode_compatible provided by six rather than the one vendored with django.

Not sure what the protocol is on bumping the version and amending the changelog; would be happy to do both.

Support for Python 2 was dropped already in Django 2.0. The latest Djang that supports Python 2.7 is Django 1.11. Since support for Django 1.11 will be dropped in early 2020, perhaps Waffle can drop support for Python 2?
Anyway, if six is used, it needs to be listed as a dependency in setup.py I think?

You're right, of course. I've updated the original post to be more accurate and clear. I do think dropping Python 2/Django 1.11 support is the right move, but I didn't want to attempt to make such prompt such a weighty decision given that the surface area for the fix is quite small.
Re: setup.py, I'll add six until a decision is made about whether to maintain Django 1.11 support.

Thanks for writing this PR, btw! 👍

To clarify, if waffle wants to keep up to date with django, it's now time to drop Python 2 support. From the release notes (https://docs.djangoproject.com/en/3.0/releases/3.0/#third-party-library-support-for-older-version-of-django):
"Following the release of Django 3.0, we suggest that third-party app authors drop support for all versions of Django prior to 2.2. At that time, you should be able to run your package’s tests using python -Wd so that deprecation warnings appear. After making the deprecation warning fixes, your app should be compatible with Django 3.0."

@clintonb I believe I've addressed all 3 issues!

Testing in Django 3.0 is blocked by https://github.com/niwinz/django-jinja/pull/237
Perhaps we can do these changes anyway and have unofficial 3.0 supports so projects depending on waffle can start Django 3.0 testing?

We need to wait for django-jinja before merging. Once this is merged, we'll drop support for older versions with #357.

Looks like django-jinja could be a while: https://github.com/niwinz/django-jinja/issues/240

Maybe we could make django-jinja an optional dependency? I am not familiar with django-waffle, but after a quick look at the code and the errors from travis, it seems like we could make it optional... This is blocking from upgrading to django 3.0 and after looking at django-jinja PR and issues from the link of @PetterS, it will take a while until somebody update that package.
In the documentation and release notes, we could mention that django-waffle[jinja] (thus, they would have to use pip install django-waffle[jinja] for the feature to be enable) is not compatible yet with django 3.0.
Thoughts?

I like that approach. Would you be willing to do that in a separate PR?
On Sun, Dec 15, 2019 at 2:44 AM NyanKiyoshi<EMAIL_ADDRESS>wrote:

Maybe we could make django-jinja an optional dependency? I am not familiar
with django-waffle, but after a quick look at the code and the errors from
travis, it seems like we could make it optional... This is blocking from
upgrading to django 3.0 and after looking at django-jinja PR and issues
from the link of @PetterS https://github.com/PetterS, it will take a
while until somebody update that package.
In the documentation and release notes, we could mention that
django-waffle[jinja] (thus, they would have to use pip install
django-waffle[jinja] for the feature to be enable) is not compatible yet
with django 3.0.
Thoughts?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/django-waffle/django-waffle/pull/355?email_source=notifications&email_token=AAG6JLVBIYEXXMT7VRSCQVDQYYC7LA5CNFSM4JT2MPZKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEG4WFKI#issuecomment-565797545,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAG6JLRGVERIFWEIRZRKUILQYYC7LANCNFSM4JT2MPZA
.

--
Clinton

Sure! I will whenever I have some spare time 👍

Maybe we could make django-jinja an optional dependency? I am not familiar with django-waffle, but after a quick look at the code and the errors from travis, it seems like we could make it optional... This is blocking from upgrading to django 3.0 and after looking at django-jinja PR and issues from the link of @PetterS, it will take a while until somebody updates that package.
In the documentation and release notes, we could mention that django-waffle[jinja] (thus, they would have to use pip install django-waffle[jinja] for the feature to be enabled) is not compatible yet with django 3.0.
Thoughts?

Nevermind about django-waffle[jinja] as we don't actually "ship" django-jinja directly in the package as a hard-coded dependency.
Opened https://github.com/django-waffle/django-waffle/pull/358 for optional testing of jinja templates.

Thanks for #358 @NyanKiyoshi!
@heydenberk once you rebase and resolve the conflicts, I can review and merge.

@clintonb done! Not sure, process-wise, whether I was meant to bump the minor version again or append to the existing v0.19.0 changelog entry. I've done the former but am happy to change it.

@heydenberk v0.19.0 hasn't been released, so add to that version.

Thanks for doing this. I hope this can be merged soon!

@PetterS the build errors seem to be about concurrent database users and I don't see how they're caused by this PR, so I'm sort of stumped. Are the tests non-deterministic? Am I misunderstanding the output?

How about rebasing and changing the version to 0.19? Perhaps the error was a flake?

Hmm... perhaps @clintonb knows?

Still looking. The issue is solely with Django 3.0.x builds. My initial hypothesis was that the builds were attempting to access the same database, but the builds are sufficiently isolated, so that hypothesis is out.

Alright. It seems the database connection is not being closed at some point in the tests. Splitting them out to be their own test runs (e.g. one job per Python-Django combination) works. I can resolve this later tonight (PDT) if no one else is available to further breakup the jobs.


genomicVariant.json fails validation against current Beacon v2 defaultSchema

Expected Behavior
All data in genomicVariations.json should be valid against the current default Beacon v2 schema for GenomicVariations, specifically against the LegacyVariation definition.
Current Behavior
Provided genomic variants fail validation for a number of reasons, explained in this google doc:
I used the python jsonschema package to validate a single genomic variant object ("_id": "62afade9676e4d25e5240835") against the current beacon v2 GenomicVariation schema
Briefly:

null values cause validation to fail
molecularAttributes.molecularEffects should be an array of ontologyTerms, not a string
variantLevelData.phenotypicEffects should be an array of PhenoClinicEffect objects, not a string
The required object field variation is missing with some fields incorporated into the root of the object, some are incorrect though, e.g. position instead of location

Possible Solution

Reformat the current json to meet the requirements of the schema
Check all other provided data passes schema validation

Context (Environment)
We are trying to understand the beacon model, how to set up a beacon and understand querying and filters. We were using the sample data provided here as a template for the data we need to submit to Beacon, but it seems like it isn't valid against the current v2 Schemas which causes confusion.

Hi Marion, I am chipping in, yet I am not the person responsible of this repo.
There is a factor that you may have not taken into account, which is versioning. It’s likely that the JSON you are trying to validate was created from v2.0.0 of the spec (or even before that).
When this JSON was created it validated against the schemas. I know it because I created it :smile:. We have a tool included in the ref. implementation that does validation.
I agree that versioning is something that needs improvement in beacon_v2. I am pushing on that myself.
Cheers!
Manu

Thanks Manu!
Is there any plan to update the jsons in line with the latest version of the spec?


[polish] Make sure CLI commands have the right verbs

There are some potential CLI changes we need to make, based on the demo. Feel free to contest any one of these:

[ ] Rename (or at least alias) ks prototype use to ks generate
[ ] Figure out how we want to deal with the other ks prototype * commands. Do we keep prototype in the command, and if so, is that inconsistent with ks generate?

There might be more questions as we finish up ksonnet params and environments, but want to make sure this is on our radar for the demo next week.

cc @jessicayuen @hausdorff

Good points, we should also review the output of the logging messages of each command to make sure they're not too verbose (or lacking).

Is there a demo and/or kubecon milestone we can use to organize these issues?
If you'd like, I can handle this---I'd just need admin permissions for this repo ;P

@abiogenesis-now  We have a feature complete milestone 0.7.0 - Feature Complete. Gave you permission!


WIP Enable rollout monitor for single node openshift

Includes fake bump of openshift/library-go#1116

/retest


Why are modversions ordered by number and not by date

Since modversions are ordered by number the modversions are all out of order. For example, in a list ordered from oldest to newest modversions, 4.2.19 comes before 4.2.2 (because 1 is smaller than 2, but 19 isn't smaller than 2). It should be the other way around, that's why I think modversions should be ordered by date and not by number.

Look, 1.2.12 is the latest version, though it's in the middle of the list. This makes it easy to make a dumb mistake when picking the correct modversion.

Dupe #492 - sort of

@spannerman79 Yeah I have that issue too. Really really annoying. Seems like an easy fix if all builds were dated and sorted by that and not by number.

Only issue is the weird way that some mod devs number their build versions.  Not to mention sometimes a modder (or two) just re-uploads the same version number when clearly there has been changes made.  CustomNPC is one such mod :frowning:

This
https://github.com/TechnicPack/TechnicSolder/blob/master/app/views/modpack/build/view.blade.php#L85
should be changed to sort by updated_at.


Tasks prevents checking off tasks on Canvas cards

Please check that this issue hasn't been reported before.

[X] I searched previous Bug Reports didn't find any similar reports.

Expected Behavior
When checking off a task that's on a Canvas card, task should become checked off
Current behaviour

A series of notifications pop up "Tasks: No file found for task engine. Retrying …"
The task never gets checked off

Steps to reproduce

Launch Obsidian Sandbox via the Open Sandbox Vault command
Install the Tasks plugin & Enable
Make a new Canvas
Click to make a new Card
Type out a task, e.g. - [ ] test task
Click the canvas background to deselect the card (Tasks words fine in the card when it is new and has not been deselected)
Click the card background to select the card
Attempt to tick the task checkbox

Which Operating Systems are you using?

[ ] Android
[ ] iPhone/iPad
[ ] Linux
[X] macOS
[ ] Windows

Obsidian Version
1.3.5
Tasks Plugin Version
4.2.0
Checks

[X] I have tried it with all other plugins disabled and the error still occurs

Possible solution
No response

Isn't this a duplicate of #2100  ?

Confirmed that I can reproduce it. Thanks for logging it, @Josh5A.

Isn't this a duplicate of #2100 ?

Good question, but no it isn't/.
#2100 is about include tasks from Canvas notes in Tasks search results.
This one is about interacting with tasks in Canvas notes in queries.
So I suspect that whilst someone is edited a canvas note, some temporary markdown file is created somewhere... And it looks like Tasks is detecting event completion in those notes, but cannot then find the note to update the task in it.

The crucial bit of the output is this:

So when a task in canvas card is toggled, the filename can be an empty string.
It should be easy to write special-case code for that.


modules: Fix warning in wiseconnect module

Updated wiseconnect module for version with fix for 'spi_is_ready' warning.
Signed-off-by: Jared Baumann<EMAIL_ADDRESS>

The following west manifest projects have been modified in this Pull Request:

Name
Old Revision
New Revision
Diff

wiseconnect
8c4ad06fd958ab76e3ec5dd6dec7b1d3e1f25926
b6993906c72709b5535cc96240f0ec552ea95e86
N/A

Note: This message is automatically posted and updated by the Manifest GitHub Action.


[Ubuntu 24.04] The futex facility returned an unexpected error code.

Description
There are futex related errors after upgrading to 24.04. Works fine on 22.04.
The futex facility returned an unexpected error code.
Aborted (core dumped)

Platforms affected

[ ] Azure DevOps
[X] GitHub Actions - Standard Runners
[ ] GitHub Actions - Larger Runners

Runner images affected

[ ] Ubuntu 20.04
[ ] Ubuntu 22.04
[X] Ubuntu 24.04
[ ] macOS 11
[ ] macOS 12
[ ] macOS 13
[ ] macOS 13 Arm64
[ ] macOS 14
[ ] macOS 14 Arm64
[ ] Windows Server 2019
[ ] Windows Server 2022

Image version and build link
  Image: ubuntu-24.04
  Version: 20240516.4.0

https://github.com/mpv-player/mpv/actions/runs/9354665913/job/25748023066
Is it regression?
Yes, works correctly on ubuntu-22.04 images.
Expected behavior
Things does not crash.
Actual behavior
During apt-get install there are futex errors. This also happens after when wine is used.
The futex facility returned an unexpected error code.
Aborted (core dumped)

Repro steps
You can see workflow in this PR https://github.com/mpv-player/mpv/pull/14169
To reproduce, use the same command:
sudo apt-get install -y ccache g++-mingw-w64 gcc-multilib meson nasm ninja-build pkg-config wine wine32

Closing as duplicate https://github.com/actions/runner-images/issues/9937

Closing as duplicate #9937

Cool, but it is completely different issue. I'm not reporting here Error: The operation was canceled., nor I mentioned it anywhere in my report. I'm reporting futex issue, that has been present since the beginning.
You can refer to this job https://github.com/mpv-player/mpv/actions/runs/9183725744/job/25254900078 if it makes easier.
Note that there are multiple aborts during dpkg configuration step (in Install Dependencies) and finally it crashes when trying to run the binary.

Same problem
https://github.com/lvgl/lvgl/actions/runs/9396173814/job/25876858344?pr=6241

Hello! That is expected as the CONFIG_COMPAT_32BIT_TIME kernel option is not enabled on ubuntu24 (and likely will never be), we do not patch kernel ourselves as we take the stock azure's sku, as a result we can not help solving this, unfortunately.

Thank you for looking into it, I expected it to be kernel configuration difference, as I tested locally and it was working ok. I kinda expected you spin custom kernel, but if it is stock linux-azure one, it make sense to keep it as-is. That's means we cannot run the 32-bit build and tests on 24.04, unfortunately. Well, at least 64-bit works if I don't enable multilib.

@mikhailkoliada I understand GitHub just takes the Azure VM, but losing support for building and running 32bit binaries is major thing (which also would break our CI in Zephyr). What would it take to have CONFIG_COMPAT_32BIT_TIME enabled back in these images' kernel?

I need to ask you to please reopen this ticket, because this ubuntu24.04 image is badly broken in this regard.
The issue may be inherited from the Azure's image but it is still present on the github runners,
so please reopen it and do not close it until it is resolved.
In very short the issue is the following:
The kernel image used in this VM is compiled with CONFIG_COMPAT_32BIT_TIME=n, unlike the vanilla Ubuntu 24.04 kernel images.
But, the glibc:i386 distributed for this image is compiled needing the syscalls enabled with that option.
i.e. This kernel configuration is just incompatible with the provided glibc
In detail:
glibc when built for 32bit, if not told which kernel is built for, will decide if the time_t value fits or not in a 32bit time_t, and do either the 32 or 64bit syscall:
https://sourceware.org/git/?p=glibc.git;a=blob;f=nptl/futex-internal.c;h=0bb1dd51f66802521afd71b9246222ed0ea0d862;hb=refs/heads/release/2.39/master#l90
calls with no deadline (NULL) fit in the 32bit version, but as the kernel does not provide this syscall, glibc will just get  a ENOSYS, and glibc will error out aborting the program
abort (abort.c:79)
__libc_message_impl.cold (libc_fatal.c:132)
__libc_fatal (libc_fatal.c:141)
futex_fatal_error (futex-internal.h:87)
__futex_abstimed_wait_common (futex-internal.c:119)

after printing "The futex facility returned an unexpected error code.\n":
https://sourceware.org/git/?p=glibc.git;a=blob;f=sysdeps/nptl/futex-internal.h;h=0e87e92d15ab92f5069463719a494e97d9800431;hb=refs/heads/release/2.39/master#l87
For reference, this is the current vanilla ubuntu24.04 kernel for x86_64 and this config:
$ uname -a
Linux <redacted> 6.8.0-35-generic #35-Ubuntu SMP PREEMPT_DYNAMIC Mon May 20 15:51:52 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
$ grep CONFIG_COMPAT_32BIT_TIME /boot/config-$(uname -r)
CONFIG_COMPAT_32BIT_TIME=y

On the other hand this is the kernel and config for this ubuntu 24.04 image now:
Linux <> 6.8.0-1008-azure #8-Ubuntu SMP Fri May 17 10:44:55 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
# CONFIG_COMPAT_32BIT_TIME is not set

Please note that building and running 32bit binaries in a 64bit system is not a weird thing.
It is how one tests that a program works for 32bit targets even though the test machine is a 64bit machine.
It is how we test embedded SW designed for 32bit systems on a 64bit machine.
It is something you need to run your old 32bit libraries for which porting them to 64bits is not reasonable.
These are not bizarre usecases, and it is clearly going to affect lots of major projects as you can see from the issues already linked to this issue.
One can have a perfectly correct 32bit binary in all regards (including no Y2039 issues), but due to the glibc and kernel distributed with this image end up with this error.

Maybe we should report this issue to Canonical. I don't think it is GitHub issue specifically. I think it is reasonable to use linux-azure kernel for the cloud applications. It is unfortunate that i386 multilib is not working in this case.

The fixes kernel is now on https://github.com/actions/runner-images/releases/tag/ubuntu24%2F20240811.1
=> the issue is resolved in this version.
Thanks


math.h not found while executing "pip install git+https://github.com/NVlabs/tiny-cuda-nn/#subdirectory=bindings/torch"

Describe the bug
As title says "pip install git+https://github.com/NVlabs/tiny-cuda-nn/#subdirectory=bindings/torch" errors with not finding math.h (see below).
Is there an easy solution to fix that? Just write what you need for logs and other files and I am happy to provide them.
Thanks!
Steps to reproduce the behavior:

Install Visual Studio 2022 Community Edition
Install CUDA 11.7
Follow the installation tutorial for nerfstudio
error occurs during pip install git+https://github.com/NVlabs/tiny-cuda-nn/#subdirectory=bindings/torch

Expected behavior
pip should finish without any errors
Output from console
`(nerfstudio) C:\Users\svenf>pip install git+https://github.com/NVlabs/tiny-cuda-nn/#subdirectory=bindings/torch
Collecting git+https://github.com/NVlabs/tiny-cuda-nn/#subdirectory=bindings/torch
Cloning https://github.com/NVlabs/tiny-cuda-nn/ to c:\users\svenf\appdata\local\temp\pip-req-build-nnrc7hfw
Running command git clone --filter=blob:none --quiet https://github.com/NVlabs/tiny-cuda-nn/ 'C:\Users\svenf\AppData\Local\Temp\pip-req-build-nnrc7hfw'
Resolved https://github.com/NVlabs/tiny-cuda-nn/ to commit 14053e9a87ebf449d32bda335c0363dd4f5667a4
Running command git submodule update --init --recursive -q
Preparing metadata (setup.py) ... done
Building wheels for collected packages: tinycudann
Building wheel for tinycudann (setup.py) ... error
error: subprocess-exited-with-error
× python setup.py bdist_wheel did not run successfully.
│ exit code: 1
╰─> [36 lines of output]
Building PyTorch extension for tiny-cuda-nn version 1.7
Obtained compute capability 86 from PyTorch
running bdist_wheel
C:\Users\svenf\anaconda3\envs\nerfstudio\lib\site-packages\torch\utils\cpp_extension.py:411: UserWarning: Attempted to use ninja as the BuildExtension backend but we could not find ninja.. Falling back to using the slow distutils backend.
warnings.warn(msg.format('we could not find ninja.'))
running build
running build_py
creating build
creating build\lib.win-amd64-cpython-310
creating build\lib.win-amd64-cpython-310\tinycudann
copying tinycudann\modules.py -> build\lib.win-amd64-cpython-310\tinycudann
copying tinycudann_init_.py -> build\lib.win-amd64-cpython-310\tinycudann
running egg_info
creating tinycudann.egg-info
writing tinycudann.egg-info\PKG-INFO
writing dependency_links to tinycudann.egg-info\dependency_links.txt
writing top-level names to tinycudann.egg-info\top_level.txt
writing manifest file 'tinycudann.egg-info\SOURCES.txt'
reading manifest file 'tinycudann.egg-info\SOURCES.txt'
writing manifest file 'tinycudann.egg-info\SOURCES.txt'
copying tinycudann\bindings.cpp -> build\lib.win-amd64-cpython-310\tinycudann
running build_ext
C:\Users\svenf\anaconda3\envs\nerfstudio\lib\site-packages\torch\utils\cpp_extension.py:813: UserWarning: The detected CUDA version (11.7) has a minor version mismatch with the version that was used to compile PyTorch (11.3). Most likely this shouldn't be a problem.
warnings.warn(CUDA_MISMATCH_WARN.format(cuda_str_version, torch.version.cuda))
building 'tinycudann_bindings_86._C' extension
creating build\dependencies
creating build\dependencies\fmt
creating build\dependencies\fmt\src
creating build\src
creating build\temp.win-amd64-cpython-310
creating build\temp.win-amd64-cpython-310\Release
creating build\temp.win-amd64-cpython-310\Release\tinycudann
"C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.34.31933\bin\HostX86\x64\cl.exe" /c /nologo /O2 /W3 /GL /DNDEBUG /MD -IC:\Users\svenf\AppData\Local\Temp\pip-req-build-nnrc7hfw/include -IC:\Users\svenf\AppData\Local\Temp\pip-req-build-nnrc7hfw/dependencies -IC:\Users\svenf\AppData\Local\Temp\pip-req-build-nnrc7hfw/dependencies/cutlass/include -IC:\Users\svenf\AppData\Local\Temp\pip-req-build-nnrc7hfw/dependencies/cutlass/tools/util/include -IC:\Users\svenf\AppData\Local\Temp\pip-req-build-nnrc7hfw/dependencies/fmt/include -IC:\Users\svenf\anaconda3\envs\nerfstudio\lib\site-packages\torch\include -IC:\Users\svenf\anaconda3\envs\nerfstudio\lib\site-packages\torch\include\torch\csrc\api\include -IC:\Users\svenf\anaconda3\envs\nerfstudio\lib\site-packages\torch\include\TH -IC:\Users\svenf\anaconda3\envs\nerfstudio\lib\site-packages\torch\include\THC "-IC:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.7\include" -IC:\Users\svenf\anaconda3\envs\nerfstudio\include -IC:\Users\svenf\anaconda3\envs\nerfstudio\Include "-IC:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.34.31933\include" "-IC:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.34.31933\ATLMFC\include" "-IC:\Program Files\Microsoft Visual Studio\2022\Community\VC\Auxiliary\VS\include" "-IC:\Program Files (x86)\Windows Kits\NETFXSDK\4.8\include\um" /EHsc /Tp../../dependencies/fmt/src/format.cc /Fobuild\temp.win-amd64-cpython-310\Release../../dependencies/fmt/src/format.obj /MD /wd4819 /wd4251 /wd4244 /wd4267 /wd4275 /wd4018 /wd4190 /EHsc /std:c++14 -DTCNN_MIN_GPU_ARCH=86 -DTORCH_API_INCLUDE_EXTENSION_H -DTORCH_EXTENSION_NAME=_C -D_GLIBCXX_USE_CXX11_ABI=0
format.cc
C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.34.31933\include\cstdlib(12): fatal error C1083: Cannot open include file: 'math.h': No such file or directory
error: command 'C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.34.31933\bin\HostX86\x64\cl.exe' failed with exit code 2
[end of output]
note: This error originates from a subprocess, and is likely not a problem with pip.
ERROR: Failed building wheel for tinycudann
Running setup.py clean for tinycudann
Failed to build tinycudann
Installing collected packages: tinycudann
Running setup.py install for tinycudann ... error
error: subprocess-exited-with-error
× Running setup.py install for tinycudann did not run successfully.
│ exit code: 1
╰─> [23 lines of output]
Building PyTorch extension for tiny-cuda-nn version 1.7
Obtained compute capability 86 from PyTorch
running install
C:\Users\svenf\anaconda3\envs\nerfstudio\lib\site-packages\setuptools\command\install.py:34: SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and pip and other standards-based tools.
warnings.warn(
running build
running build_py
running egg_info
writing tinycudann.egg-info\PKG-INFO
writing dependency_links to tinycudann.egg-info\dependency_links.txt
writing top-level names to tinycudann.egg-info\top_level.txt
C:\Users\svenf\anaconda3\envs\nerfstudio\lib\site-packages\torch\utils\cpp_extension.py:411: UserWarning: Attempted to use ninja as the BuildExtension backend but we could not find ninja.. Falling back to using the slow distutils backend.
warnings.warn(msg.format('we could not find ninja.'))
reading manifest file 'tinycudann.egg-info\SOURCES.txt'
writing manifest file 'tinycudann.egg-info\SOURCES.txt'
running build_ext
C:\Users\svenf\anaconda3\envs\nerfstudio\lib\site-packages\torch\utils\cpp_extension.py:813: UserWarning: The detected CUDA version (11.7) has a minor version mismatch with the version that was used to compile PyTorch (11.3). Most likely this shouldn't be a problem.
warnings.warn(CUDA_MISMATCH_WARN.format(cuda_str_version, torch.version.cuda))
building 'tinycudann_bindings_86._C' extension
"C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.34.31933\bin\HostX86\x64\cl.exe" /c /nologo /O2 /W3 /GL /DNDEBUG /MD -IC:\Users\svenf\AppData\Local\Temp\pip-req-build-nnrc7hfw/include -IC:\Users\svenf\AppData\Local\Temp\pip-req-build-nnrc7hfw/dependencies -IC:\Users\svenf\AppData\Local\Temp\pip-req-build-nnrc7hfw/dependencies/cutlass/include -IC:\Users\svenf\AppData\Local\Temp\pip-req-build-nnrc7hfw/dependencies/cutlass/tools/util/include -IC:\Users\svenf\AppData\Local\Temp\pip-req-build-nnrc7hfw/dependencies/fmt/include -IC:\Users\svenf\anaconda3\envs\nerfstudio\lib\site-packages\torch\include -IC:\Users\svenf\anaconda3\envs\nerfstudio\lib\site-packages\torch\include\torch\csrc\api\include -IC:\Users\svenf\anaconda3\envs\nerfstudio\lib\site-packages\torch\include\TH -IC:\Users\svenf\anaconda3\envs\nerfstudio\lib\site-packages\torch\include\THC "-IC:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.7\include" -IC:\Users\svenf\anaconda3\envs\nerfstudio\include -IC:\Users\svenf\anaconda3\envs\nerfstudio\Include "-IC:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.34.31933\include" "-IC:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.34.31933\ATLMFC\include" "-IC:\Program Files\Microsoft Visual Studio\2022\Community\VC\Auxiliary\VS\include" "-IC:\Program Files (x86)\Windows Kits\NETFXSDK\4.8\include\um" /EHsc /Tp../../dependencies/fmt/src/format.cc /Fobuild\temp.win-amd64-cpython-310\Release../../dependencies/fmt/src/format.obj /MD /wd4819 /wd4251 /wd4244 /wd4267 /wd4275 /wd4018 /wd4190 /EHsc /std:c++14 -DTCNN_MIN_GPU_ARCH=86 -DTORCH_API_INCLUDE_EXTENSION_H -DTORCH_EXTENSION_NAME=_C -D_GLIBCXX_USE_CXX11_ABI=0
format.cc
C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.34.31933\include\cstdlib(12): fatal error C1083: Cannot open include file: 'math.h': No such file or directory
error: command 'C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.34.31933\bin\HostX86\x64\cl.exe' failed with exit code 2
[end of output]
note: This error originates from a subprocess, and is likely not a problem with pip.
error: legacy-install-failure
× Encountered error while trying to install package.
╰─> tinycudann
note: This is an issue with the package mentioned above, not pip.
hint: See above for output from the failure.
(nerfstudio) C:\Users\svenf>`

Some users have reported issues using TCNN with visual studio 2022. People have had better luck with the 2019 version.

Closing. Feel free to reopen if needed.


Camera not released in some conditions

What

Camera not released in some conditions
https://photos.app.goo.gl/6B2XEHbWqCJbKLws8

I manage to reproduce by opening a product from the scan screen and then suspending the application
And reopening the app
Part of

#526

See #4045

I'm also able to reproduce it, from some specific screens.
Is-it a recent behavior or did you have it before?

The problem is reproducible on iOS on profile/release builds only.
I'm currently working on it

I think we can now close this issue.


Make model identifiers start by a letter

We should make all the identifiers start by a letter, and let the _ only for stateful and external elements (_integ_name...)
The easiest way is to check the beginning of an identifier and if it starts by an underscore or number are a fixed series of letters
for example, if we have:
"$ value" = 10 ~~|
this will be translated as _value to the python file
we can set a string like "nvcs" (non-valid character string) to make this be translated as nvcs_value in the python file. This would not affect the regular user performance as they will use the name given by the Vensim model. But will keep the underscore beginning only for automatically generated objects by the builder. We just need to decide which beginning we want to implement.

yes, I agree. I hadn't even considered this case. Good catch.
pep8 suggests that a leading underscore is an indicator that a function or variable is for internal use. We expect users to access the functions that they define in their model, and (generally) ignore the extra machinery we have to build in order to make everything work. So, direct imports from the model should be as easy to find as possible.


 Please tell me the regulation of hepcidin by lactate. You are not allowed to cite or make any literature which can not be found in Pubmed, Google Scholar, and other scientific database.
problem: all provided literature can not be found in Pubmed and Google Scholar, no matter I selected Academic mode or not.
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.

That is normal ... the LLMs hallucinate. It is excessively annoying.
They are now claiming they can't show sources due to "privacy/security" concerns ....


Protect Main Branch

Please protect the main branch to prevent accidental or unauthorized changes to the repository. This is a best practice recommended by GitHub and helps ensure the stability and integrity of the codebase.

Preventing accidental commits to main. other protections are out of scope today


Fix signal duplication bug when duplicating node with instanced children

node::duplicate() recreates all descendants of node. However, it does not necessarily duplicate all signals between members of the subtree rooted at that node, even if the DUPLICATE_SIGNALS flag is passed.
The issue occurs due to the error check in duplicate_signals(), because it only checks for common ownership 1 or 2 levels up, which need not always be the case. To fix, for any given node, the code now checks if it belongs to the subtree rooted at the node on which duplicate() is initially called. This more closely matches how duplicate() itself works.
If this seems alright, I can make a separate PR for 3.2.
Closes #39119

Thanks!


Android final project

SRC.com Viewer
Layouts

[ ] LinearLayout
[ ] FrameLayout
[ ] DrawerLayout

Widgets

[ ] ListAdapter
[ ] Buttons
[ ] TextViews
[ ] ImageButton
[ ] Spinner
[ ] ScrollView

Activities

[ ] Main Search Page Tab
[ ] Browsing Tab
[ ] Favourites Tab
[ ] External Activity to Browser

Fragment

[ ] All activities are fragments and can be switched between with bottom task bar

Firebase / SQLite

[ ] Store the APIs game names for auto complete field
[ ] Store favourites

Additional Requirements

[ ] Works well in landscape / portrait
[ ] Contain a dialog (confirm favourites or open the link)
[ ] Notifications - notify when runs of favourited games are verified.
[ ] Support french

to periodically check for notifications http://stackoverflow.com/questions/10207612/android-execute-code-in-regular-intervals#10207775

for the navigation sidebar https://developer.android.com/training/implementing-navigation/nav-drawer.html


feat(ApiAuth): reduce probability of token expiry moments after retrieval

There is currently no buffer on the time after getting tokens.
That being said, if you complete the .requests_auth flow and the token expired 1 second after that - you're running around with an expired set of creds being none the wiser.
Example out in the wild:

@richardkeit you will likely need to rebase or merge from master to get some updates to the codecov github action, apologies


As a user I want to delete existing content on my notice board

Acceptance criteria (As follows #54 )

[ ] The creator can delete existing content
[ ] The content is updated for users who have access to it
[ ] Content can be deleted by using a "Delete"-Button for every element

Duplicate of #52?

Duplicate of #52?

YES!


fips: Edwards curves are approved for signatures only

Edwards curves 25519 and 448 can be used in many contexts. NIST approved their usage for digital signatures only. And not (yet) for key aggrement.
Specifically see NIST CMVP Implementation Guidance C.K Transition from FIPS 186-4 to FIPS 186-5 and and SP 800-186 (pages 114-116)
Resolution:

The publication of SP 800-186 does not impact the curves
permitted under SP 800-56Arev3. Curves that are included in SP
800-186 but not included in SP 800-56Arev3 are not approved for key
agreement.  E.g., the ECDH X25519 and X448 key agreement schemes
(defined in RFC 7748) that use Curve25519 and Curve448,
respectively, are not compliant to SP 800-56Arev3. The corresponding
Montgomery curves Curve25519 and Curve448 are included in SP 800-186
only for use within digital signatures as alternative
representations of the Edwards25519 and Edwards448 curves, as shown
in Table 2 of SP 800- 186.

Additional Comments:

FIPS 186-5 uses Ed25519 and Ed448 to mean the signature schemes
and not the curves themselves, while SP 800-186 uses Edwards25519
and Edwards448 to mean the curves themselves.

SP 800-186 Table 2 says that the following curves are not to be
used for ECDSA or EdDSA directly: Curve25519, W-25519, Curve448,
E448, W-448. SP 800-186 B.1 explains: “Implementations may take
advantage of these mappings to carry out elliptic curve group
operations that were originally defined for a twisted Edwards curve
on the corresponding Montgomery curve, or vice-versa, and
translating the result back to the original curve to potentially
allow code reuse”. This is permitted in the approved mode, as long
as “procedures […] include all cryptographic checks included with
the specifications in this document. This is important because the
checks are essential for the prevention of subtle attacks”.  For
example, an implementation may start on one of the permitted curves
given in Table 2 of SP 800-186, then map to a different curve,
perform some operation(s), and map back to the original permitted
curve.  This should not impact the CAVP testing which will test the
final signature on the original curve.

FIPS 186-5 uses Ed25519 and Ed448 to mean the signature schemes
and not the curves themselves, while SP 800-186 uses Edwards25519
and Edwards448 to mean the curves themselves.

This reverts 759ab5984eb981f2dd165979a7abb950ddad81ae - Marking Signatures unapproved. @paulidale
This reverts 8948b5749410084ed1dfabf17a90df65efcf0f82 - Marking Key change approved. @paulidale

Checklist

[ ] documentation is added or updated
[ ] tests are added or updated

Pauli, this is certainly not a bug fix, so not eligible for stable branches.

Alternative (not a real replacement though) PR that should solve the FIPS problem in #24099

We cannot re-enable EDDSA without adding self tests. And for that there is a different PR already. https://github.com/openssl/openssl/pull/22112

We cannot re-enable EDDSA without adding self tests.

this bit is surprising to me. even unapproved things should have KAT self-tests.... are there none for 25519/448 things in the fips provider?


启动问题

输入npm start后显示error TS6059: File 'D:/git/Git/bilive_client/app.ts' is not under 'rootDir' 'D:/git/Git/bilive_client/bilive'. 'rootDir' is expected to contain all source files.
12:30:04 - Found 1 error. Watching for file changes.
这个怎么办？

额，app.ts的路径我很早就变了，怀疑你的版本太久了，建议重新clone一遍
发送自 Windows 11

发件人: Linger12<EMAIL_ADDRESS>发送时间: Sunday, May 19, 2019 12:33:54 PM
收件人: Vector000/bilive_client
抄送: Subscribed
主题: [Vector000/bilive_client] 启动问题 (#27)
输入npm start后显示error TS6059: File 'D:/git/Git/bilive_client/app.ts' is not under 'rootDir' 'D:/git/Git/bilive_client/bilive'. 'rootDir' is expected to contain all source files.
12:30:04 - Found 1 error. Watching for file changes.
这个怎么办？
―
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/Vector000/bilive_client/issues/27?email_source=notifications&email_token=AH6IONGRASEWFDIMHN55IJLPWDKDFA5CNFSM4HN3UFDKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4GUSBUOA, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AH6IONHLW5FY5BCJ33XXDVDPWDKDFANCNFSM4HN3UFDA.


Add ability to specify additional parameters for searchOwned

There is a white list of allowed parameters. Any other parameters
will throw an exception
Resolves #87

@arubacao This is released as https://github.com/Nexmo/nexmo-php/releases/tag/1.1.2 now


⚠ Samsung has degraded performance

In 3efb75c, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2518 ms

Resolved: Samsung performance has improved in 4692395.


User registration

Hi,
I get 403 errors when testing with a new matrix server instance. Is there a user registration function, or is it planned to support this?

Not for now. PRs welcome.


Only ever getting one result...

No idea what I'm doing wrong. Please send help :-)
On 1.4.0.
Setup looks like:
const JsSearch = require('js-search')

const search = new JsSearch.Search()
search.addIndex('title')
search.addIndex('body')

search.addDocuments(posts) // There's about 2000 posts there.

// Regardless of what I search for, it returns just one result.
// The results are sensible and seem accurate and come from any of the documents
// but there's always just one.
search.search('a')

Haha, hey Kyle. How's it going?
Could I see at least a sample of your posts data?

Doing well, doing well thanks :-) Yourself?
So... it's from my journal so I can't show too much but here's a random entry that I'm not entirely sure where I was going with it but isn't super private so anyways each post has a body and title where the body is an excerpt from what I wrote capped at I think 600 characters.
{
  body: "Philosopher William James once wrote that mental life is controlled by noticing. Climbing out of the sea and onto the windy beach, my skin purple and my mind in a reverie provoked by shock, I find myself thinking of a checklist Wozniak wrote a few years ago describing how to become a genius. His advice was straightforward yet strangely terrible: You must clarify your goals, gain knowledge through spaced repetition, preserve health, work steadily, minimize stress, refuse interruption, and never resist sleep when tired. This should lead to radically improved intelligence and creativity. The only..."
  title: "Recipe for becoming a genius"
}

Glad to hear. I'm good, thanks! 😄
You forgot to specify a UID field (as a constructor param). (Actually from the looks of your sample post, your data may not have such a field?)

const JsSearch = require('js-search')

const posts = [
  {
    id: 1,
    body: "First book",
    title: "Book 1"
  },
  {
    id: 2,
    body: "Second book",
    title: "Book 2"
  },
  {
    id: 3,
    body: "Third book",
    title: "Book 3"
  }
]

const search = new JsSearch.Search('id')
search.addIndex('title')
search.addIndex('body')

search.addDocuments(posts);
search.search('book')

Ooo... it's working! Thanks! Super fast & nice.
Yeah, my data has an ID but I didn't think about how the search indexer would need an ID. Added that in and things are good.
Perhaps js-search could just auto-add ids if one isn't added? Or do you support updating documents so need ids to overwrite old documents with new documents?
Perhaps it should throw an error if you don't pass in the UID argument?

Sweet! Thanks!
Yeah I should definitely throw an error if you omit that param. It's pretty
important.
By the way, if you're using all default search settings, you might want to
consider js-worker-search. Same API but the index runs in a web worker
(when available) so it's faster still.
On Apr 24, 2017 8:34 PM, "Kyle Mathews"<EMAIL_ADDRESS>wrote:

Ooo... it's working! Thanks! Super fast & nice.
Yeah, my data has an ID but I didn't think about how the search indexer
would need an ID. Added that in and things are good.
Perhaps js-search could just auto-add ids if one isn't added? Or do you
support updating documents so need ids to overwrite old documents with new
documents?
Perhaps it should throw an error if you don't pass in the UID argument?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/bvaughn/js-search/issues/34#issuecomment-296888056,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AABznbP4R4l6O3RVfq6oeSwlgaHQ4usQks5rzWm9gaJpZM4NG76g
.

Does it just work with webpack?

It should. Uses the worker loader if workers are acceptable on the current
browser. (It's what redux-search uses under the hood, if you're interested
in an example integration.)
On Apr 24, 2017 8:48 PM, "Kyle Mathews"<EMAIL_ADDRESS>wrote:

Does it just work with webpack?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/bvaughn/js-search/issues/34#issuecomment-296891825,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AABznVnZ66Dub-9q5Ty8tWd-srO9U2Ksks5rzW0QgaJpZM4NG76g
.

Cool! Will try this in the morning! (and will close this issue now)

FYI v1.4.2 throws if you omit this parameter 😉


Java 1.3: Evolution of Java

Description 📜
Added Video to Evolution of Java. Video gives a gist of Java's evolution and its versions. Duration- 1:30min approx
Issue #1107

Type of change 📝

[x] Video (Animations, screen-recordings, presentations and regular explanatory films are all possibilties etc)

Domain of Contribution 📊

[x] Java_Domain

Checklist ✅

[X] I follow Contributing Guidelines & Code of conduct of this project.
[X] I have performed a self-review of my own code or work.
[X] I have commented my code, particularly in hard-to-understand areas.
[X] My changes generates no new warnings.
[X] I'm GWOC'21 contributor

Screenshots / Gif (Optional) 📸
Video link

@AkMo3

@sakshamlamba109 Please start the review process. @Yashesvinee Congratulations on start of journey 🥳

@sakshamlamba109 Please start the review process. @Yashesvinee Congratulations on start of journey 🥳

Thank you

@Yashesvinee pls use the tool which doesn't have a watermark if you are making slides then prefer PowerPoint
try to find out something from there.
Rest content is good just com back with the changes

hi i have removed the watermark
is it fine now?

@Yashesvinee The video is great. Just one problem, the image you have used is actually a copyright image and we cannot use that.
Can you please add your own graphic. There are still 6 days left so lets not hurry up the merge the PR.
PS: I am talking about this image.

Okay

Also, the latest version is JDK 17. Please see https://openjdk.java.net/projects/jdk/17/

@Yashesvinee whats the progress and update

I am making some changes in my video
It will be ready by tomorrow

@Yashesvinee Please share some updates on it.

hi there are some conflicts that i am unable to solve can I open another pull request after I make some changes in my repo?

@Yashesvinee Just rename your file to Evolution_Of_Java_Video. It would solve the merge conflict.

Hi I made the changes
the link is not from google drive but canva
is it okay?

Done!!

\assign Document


support for mysql 8.0

Is there support for mysql 8.0?
I'm getting many errors when trying to set the engine to 8.0, wondering if is supported

Yes, there should be a support for Mysql 8.0 according to AWS release notes:

Amazon RDS for MySQL now supports MySQL Community Edition major version 8.0 in all AWS Regions.

See more https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/CHAP_MySQL.html#MySQL.Concepts.VersionMgmt


Update async-std and bytes dependencies

We can tackle hyper 0.13 next, but let's get the low hanging fruit first.

Hey @jeff-hiner; thanks for opening this PR. Apologies for not getting around to it sooner; we're trying to become better at addressing issues on time. It seems there merge conflicts have been introduced in the interim. I'm going to go ahead and close this patch since we can't land it as-is, but if you'd like to re-submit a patch to bump our deps, that'd be much appreciated still!


Standardise development infrastructure

As a developer I want a safe place to roll-out new infrastructure and releases in an automated way.
Background
To support testing and development of the platform/portal, we need to have additional private infrastructure running so that we don't accidentally break anything in production. This development infrastructure is currently in two duplicated forms:

App Engine (AE) running an API with VMs providing CH and ES instances
xyz which is a full copy of the production version using less powerful machines.

The front-end uses AE for testing because it provides a stable URL for netlify.
We want to remove the AE instance and the associated VMs because they are all manually managed and are prone to falling out of sync with the xyz versions which are managed via Terraform.
Tasks

[x] Clean-up: remove AE from GCP and related files, notes in API repository
[x] Provide FE with stable URL for developmental API: proposed is https://platform.dev.opentargets.xyz/ and a similar one for genetics
[ ] (Ambitious!) Update Travis so that when a new API is tagged it gets deployed to the development environment automatically.

We'll leave the automation from source code to deployment for its own issue and process, as it's not trivial.


v-model not working

when i try using v-model on a styled-component is not working
<Select v-model="TransactionDetail.country">
      <option v-for="country in countries" :key="country.id">{{country.name}}</option>
 </Select>

Thanks for reporting, this was obviously a critical issue and solved in 1.2.2, just update your repo.
👋

Thanks

I'm running into this issue on 1.5.1. My inputs are returning as empty.
Thanks for port!

Wanted to know if it was specifically fixed within v1.2.3; tried it out with this example just now:
<Column style="flex: 1;">
                <Row>
                    <Input type="text" v-model="privateKey" @input="validatePrivateKey"/>
                </Row>
                <Row>
                    <Input type="text" v-model="publicKey" disabled/>
                </Row>
            </Column>

const Input = styled.input`
        width: 100%;
    `

Sorry @iwasaki-kenta I didn't get the problem.

@liqueflies With the code above, styled text inputs w/ v-model privateKey and publicKey seem to have null/empty values (they don't seem to be passed in).
I tried it out on both v1.2.2 and v1.2.3; I'm not too sure but it could be because in your commit:
on: {
              input: (event) => {
                this.$emit('input', event.target.value)
              }
            }

it does not take into account the additional input listener I attached to text input w/ v-model privateKey.

@iwasaki-kenta I've done it exactly how docs said:
https://vuejs.org/v2/guide/components-custom-events.html#Binding-Native-Events-to-Components
the <Input> component is not a native input right?
If yes, you have to bridge up native event in the same way, so in your Input component do something like:
<input class="my-fancy-input" @input="$emit('input', $event)" />

I have a fix for this problem. https://github.com/styled-components/vue-styled-components/pull/45.

Hello,
Thanks to @fsodano #88 do the job.
Thank you.


Improve article 1705.03178

Exact location of issue
The table at the end of section 3:
https://ar5iv.labs.arxiv.org/html/1705.03178#S3.T1.3
Problem details
There is a particular use of "parbox" that leads to a very small width requirement in the HTML (5.7pt), in turn leading to the table heading getting chunked to 1 letter per line.
The long-term latexml fix would be to debug and correct the way this width gets computed.
The short-term CSS fix would be to completely ignore the set widths of ltx_parbox that are descendants of span.ltx_text.

Resolve for the short-term with a CSS patch, now live.


Array Combine error when not using v1, v2, ..., vn in API_VERSION

I tried to set the API_VERSION env variable to develop and when accessing the API all I would get was
array_combine(): Both parameters should have an equal number of elements
I found out that I'm bound to use the letter v followed by a number. Ideally, the error message would be more meaningful in this case, but it seems a silly problem to go about changing source code to achieve a better error message.
Instead, should this be added to the Wiki?
I've been following the Wiki step by step and I've proposed a change in the Wiki for the API_NAME variable. This seems to be a good case for it too, right?

I'll work on better reporting for some of these errors so they're more meaningful.

Versions are no longer required to begin with v.


NamespaceSelector for ClusterQueue

What type of PR is this?
/kind feature
What this PR does / why we need it:
Implements NamespaceSelector for clusterQueue
Which issue(s) this PR fixes:
Part of #4
Special notes for your reviewer:

/assign @alculquicondor
/hold
I will send a separate PR for integration tests

A small nit, maybe not even for this PR, can we use caps for the first letter of commits? ;)

/retest

/retest

I added the integration test in this PR now that we have the refactor to ClusterQueue merged.

/lgtm

/hold cancel


feat(web): integrate rocket.chat

It integrates the Rocket.Chat webhook to current notification system.
And fixes the bug in the deployment by fixing the NotificationMessageTypes to align exactly with the file names in the web/crux/assets/notificationTemplates

can you please check now @robot9706

can you please check now @robot9706

Linter is still failing.


guake: 3.2.0 -> 3.2.1

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/guake/versions.
These checks were done:

built on NixOS
ran ‘/nix/store/p6q5wvny65jwxx2v1gq6gwbnrv587a1n-guake-3.2.1/bin/guake -h’ got 0 exit code
ran ‘/nix/store/p6q5wvny65jwxx2v1gq6gwbnrv587a1n-guake-3.2.1/bin/guake --help’ got 0 exit code
ran ‘/nix/store/p6q5wvny65jwxx2v1gq6gwbnrv587a1n-guake-3.2.1/bin/..guake-wrapped-wrapped -h’ got 0 exit code
ran ‘/nix/store/p6q5wvny65jwxx2v1gq6gwbnrv587a1n-guake-3.2.1/bin/..guake-wrapped-wrapped --help’ got 0 exit code
ran ‘/nix/store/p6q5wvny65jwxx2v1gq6gwbnrv587a1n-guake-3.2.1/bin/.guake-wrapped -h’ got 0 exit code
ran ‘/nix/store/p6q5wvny65jwxx2v1gq6gwbnrv587a1n-guake-3.2.1/bin/.guake-wrapped --help’ got 0 exit code
found 3.2.1 with grep in /nix/store/p6q5wvny65jwxx2v1gq6gwbnrv587a1n-guake-3.2.1
directory tree listing: https://gist.github.com/507c9c542414dc20262767a01f4ba0d9

cc @msteen for review

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: guake
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

Failure on x86_64-linux (full log)
Attempted: guake
Partial log (click to expand)
        install -Dm644 "$f" "//nix/store/p6q5wvny65jwxx2v1gq6gwbnrv587a1n-guake-3.2.1/share/locale/$lb/LC_MESSAGES/guake.mo"; \
done;
# you probably want to execute this target with sudo:
# sudo make install
Installing from on your system is not recommended.
Please prefer you application package manager (apt, yum, ...)
/nix/store/xn5gv3lpfy91yvfy9b0i7klfcxh9xskz-bash-4.4-p19/bin/bash: /usr/bin/env: No such file or directory
make: *** [Makefile:77: install-guake] Error 127
builder for '/nix/store/azn6g3bysris2y0xx4z9jd7379arsk2m-guake-3.2.1.drv' failed with exit code 2
error: build of '/nix/store/azn6g3bysris2y0xx4z9jd7379arsk2m-guake-3.2.1.drv' failed

Failure on aarch64-linux (full log)
Attempted: guake
Partial log (click to expand)
        install -Dm644 "$f" "//nix/store/2gsnv6pm2b5n3j4hjvl1jalxpn3ahxdf-guake-3.2.1/share/locale/$lb/LC_MESSAGES/guake.mo"; \
done;
# you probably want to execute this target with sudo:
# sudo make install
Installing from on your system is not recommended.
Please prefer you application package manager (apt, yum, ...)
/nix/store/a4qslf0yfs44mhnbagarn232sjnckhy0-bash-4.4-p19/bin/bash: /usr/bin/env: No such file or directory
make: *** [Makefile:77: install-guake] Error 127
builder for '/nix/store/5lsbisa7mj86qm60pscmpi1zjwa2gcay-guake-3.2.1.drv' failed with exit code 2
error: build of '/nix/store/5lsbisa7mj86qm60pscmpi1zjwa2gcay-guake-3.2.1.drv' failed

Changes, https://github.com/Guake/guake/releases/tag/3.2.1
@ryantm Are you not building the apps in sandbox? It should fail with it.

Success on x86_64-linux (full log)
Attempted: guake
Partial log (click to expand)
glibPreFixupPhase
post-installation fixup
Wrapping program /nix/store/8h9ckrz9cwnyk8rnlyqsnka7sw3npa8f-guake-3.2.1/bin/guake
shrinking RPATHs of ELF executables and libraries in /nix/store/8h9ckrz9cwnyk8rnlyqsnka7sw3npa8f-guake-3.2.1
strip is /nix/store/j75dgadrff2d1fyc4fczmcgqkid2imdx-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/8h9ckrz9cwnyk8rnlyqsnka7sw3npa8f-guake-3.2.1/lib  /nix/store/8h9ckrz9cwnyk8rnlyqsnka7sw3npa8f-guake-3.2.1/bin
patching script interpreter paths in /nix/store/8h9ckrz9cwnyk8rnlyqsnka7sw3npa8f-guake-3.2.1
checking for references to /build in /nix/store/8h9ckrz9cwnyk8rnlyqsnka7sw3npa8f-guake-3.2.1...
wrapping `/nix/store/8h9ckrz9cwnyk8rnlyqsnka7sw3npa8f-guake-3.2.1/bin/.guake-wrapped'...
/nix/store/8h9ckrz9cwnyk8rnlyqsnka7sw3npa8f-guake-3.2.1

Success on aarch64-linux (full log)
Attempted: guake
Partial log (click to expand)
glibPreFixupPhase
post-installation fixup
Wrapping program /nix/store/xrmfi9m1cfm5708m1p4y78iiib4821jc-guake-3.2.1/bin/guake
shrinking RPATHs of ELF executables and libraries in /nix/store/xrmfi9m1cfm5708m1p4y78iiib4821jc-guake-3.2.1
strip is /nix/store/gp7fylxwn18b7pl2c18ks89hsiaxyfvf-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/xrmfi9m1cfm5708m1p4y78iiib4821jc-guake-3.2.1/lib  /nix/store/xrmfi9m1cfm5708m1p4y78iiib4821jc-guake-3.2.1/bin
patching script interpreter paths in /nix/store/xrmfi9m1cfm5708m1p4y78iiib4821jc-guake-3.2.1
checking for references to /build in /nix/store/xrmfi9m1cfm5708m1p4y78iiib4821jc-guake-3.2.1...
wrapping `/nix/store/xrmfi9m1cfm5708m1p4y78iiib4821jc-guake-3.2.1/bin/.guake-wrapped'...
/nix/store/xrmfi9m1cfm5708m1p4y78iiib4821jc-guake-3.2.1

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: guake
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

@jtojnar added issue


Validation for rancher cli version - v0.4.0

Validate new features introduced in  rancher cli version - v0.4.0.
Automate p1 work flows.

@soumyalj Please use the merged PR to find the new features in CLI.


[PSA for PR authors] Update your pre-commit hooks to use the newly merged pre-commit framework

We just replaced our hand-written shell scripts for pre-commit hooks with a set of hooks defined using the pre-commit Python framework:

#88866

Previous hooks should still work if you copied the scripts manually from misc/hooks/, but if you used to symlink them, they will be broken as of #88866 so you should remove them from .git/hooks/.
To use the new system, remove old hooks from .git/hooks/, and apply the new hooks with:
pip install pre-commit
pre-commit install

That's all, it should then automatically download dependencies (currently clang-format and black) the first time you try to commit, or when running pre-commit run manually.
If you want to apply the hooks to all your local changes before committing, you can use pre-commit run. You can also apply the hooks to all files in the repository regardless of their changed status by adding the -a option (pre-commit run -a).
The main workflow difference with the previous set of hooks is that if some changes are needed to pass the checks, they will be made automatically in place (at least for clang-format and black currently). Let's see if that workflow is fine, or if we need to figure out ways to bring back some interactivity.

We should also update the godot docs, as they point to the old way: https://docs.godotengine.org/en/latest/contributing/development/code_style_guidelines.html#pre-commit-hook and https://docs.godotengine.org/en/latest/contributing/development/code_style_guidelines.html#id3; when opening a PR it also points to one of these URLs

I am getting the following errors about encoding on windows when running these:
  File "C:\Users\rookee\scoop\apps\python\current\Lib\encodings\cp1252.py", line 23, in decode
    return codecs.charmap_decode(input,self.errors,decoding_table)[0]
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
UnicodeDecodeError: 'charmap' codec can't decode byte 0x9d in position 5068: character maps to <undefined>

It seems to read files in cp1252 instead of utf8 which gives me this garbled mess when running pre-commit run -a:

Might be either something wrong with your specific file, if you added one you might have accidentally added an encoding to it, check your editor, otherwise this is likely a configuration error in your terminal

I did not touch these files at all. I am running from powershell, I think it's reading the files in the standard platform encoding (which is cp1252 on windows if I recall):
Traceback (most recent call last):
  File "D:\dev\godot\misc\scripts\copyright_headers.py", line 92, in <module>
    line = fileread.readline()
           ^^^^^^^^^^^^^^^^^^^
  File "C:\Users\rookee\scoop\apps\python\current\Lib\encodings\cp1252.py", line 23, in decode
    return codecs.charmap_decode(input,self.errors,decoding_table)[0]
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

readline is not passed any encoding, so it makes sense its trying to use the platform encoding (I am not proficient in python though).

Assuming you're working on #89826, can you check that the new file you added is encoded in utf8? Just to double check that isn't throwing it off somehow
I don't know how to alter the encoding in python though, there is an encoding="utf-8" directive, this might be missing from our files, I'll take a look

I see you came to the same conclusion as me, that fixed the encoding issues but I am getting these changes added by copyright_headers now:

This doesn't look like an encoding issue and I manually checked said file: its UTF-8 without BOM.
Will dig deeper later, the encoding = "utf-8" directive should definitely be added in copyright_header.py

Could be that you changing that file broke some encoding in it so it has that error now, unsure

Now ran into this myself, unsure why it didn't happen before, will look at a fix while I'm working on other code

Adding here for potential future reference (maybe worth adding a note in the documentation?):
When using msys2 on Windows, directly installing pre-commit inside msys2 (either as pre-packaged or using pip) won't work (see https://github.com/pre-commit/pre-commit/issues/3234).
The workaround I've found is installing pre-commit under Windows and invoking that binary inside msys2. In a nutshell:

on Windows: pip install pre-commit (having installed Python on Windows first, of course)
on msys2 add alias pre-commit='/c/Users/foo/AppData/Local/Programs/Python/Python312/Scripts/pre-commit.exe' (update to its correct path for each setup) to ~/.bash_profile or similar


DNM: Add tests for unordered container listing

Add tests for unordered container listing, which is not a standard
part of swift, but is included as it's much less resource intensive
and can be useful in some circumstances.
Adds use of attribute @attr('fails_on_swift') to mark that this test
is not standard for swift.
Signed-off-by: J. Eric Ivancich<EMAIL_ADDRESS>

Should not be merged until ceph PR is merged (https://github.com/ceph/ceph/pull/21026).

pushed to ceph-master branch too


Reversed order of add post (INS6) and add like to post (INS2)

In the updateStream_0_26_forum.csv file of the dataset, when listing all updates related to post-70368991551179 through
$ grep -w<PHONE_NUMBER>1179 updateStream_0_26_forum.csv
1349790181752|1278281267146|2|6597069905389|70368991551179|1349790181752
1349790181752|1289052676356|6|70368991551179||1349790181752|<IP_ADDRESS>|Internet Explorer|uz|About Niki Lauda, er Formula One racing driver and three-time F1 World Champion. More recently an aviati|104|10995116536216|21990277706324|57|164
1349790237878|1291770543934|2|10995116326590|70368991551179|1349790237878
1349790272484|1327084360170|2|26388279332421|70368991551179|1349790272484
1349790380456|1322943558393|2|24189256307723|70368991551179|1349790380456

(Vertex post-70368991551179 doesn't appear in any other streams and the initial snapshot.)
The first insert query related to post-70368991551179 is adding a like edge (INS2) to this post, and the second one is adding the post (INS6).
Though these two queries have a same timestamp, they will be issued by driver sequentially.
So there will be an adding edge query to the post vertex before the vertex is added.
Similar problem also found in the sf300 dataset when adding like edge to a comment (INS3).

I'm 99% sure the issue is at this line
https://github.com/ldbc/ldbc_snb_datagen_hadoop/blob/9355de48a19ee2b17bd1713a97ad9d37bd8adce2/src/main/java/ldbc/snb/datagen/generator/generators/LikeGenerator.java#L73
or in this line
https://github.com/ldbc/ldbc_snb_datagen_hadoop/blob/9355de48a19ee2b17bd1713a97ad9d37bd8adce2/src/main/java/ldbc/snb/datagen/generator/generators/LikeGenerator.java#L75
where DatagenParams.deltaTime should be added, similar to other generators. Note also how the assert at line
https://github.com/ldbc/ldbc_snb_datagen_hadoop/blob/9355de48a19ee2b17bd1713a97ad9d37bd8adce2/src/main/java/ldbc/snb/datagen/generator/generators/LikeGenerator.java#L77
should be extended like
assert ((membership.person().creationDate() + DatagenParams.deltaTime) < date && message.creationDate() < date);
So for the particular example updates, my hypothesis is that the minDate is set to be the POST.creationDate (since this is created after the person membership to the forum), and we are so unlucky that the call to random.nextDouble() used to add an offset to that minDate returns 0.0.

I've made a pull request with  a fix here https://github.com/ldbc/ldbc_snb_datagen_hadoop/pull/25

Hello, I ran the generator with Arnau's patch and it fixed the problem:
$ grep -w<PHONE_NUMBER>1179 updateStream_0_26_forum.csv | head -n 5
1349790181752|1289052676356|6|70368991551179||1349790181752|<IP_ADDRESS>|Internet Explorer|uz|About Niki Lauda, er Formula One racing driver and three-time F1 World Champion. More recently an aviati|104|10995116536216|21990277706324|57|164
1349790191752|1278281267146|2|6597069905389|70368991551179|1349790191752
1349790247878|1291770543934|2|10995116326590|70368991551179|1349790247878
1349790282484|1327084360170|2|26388279332421|70368991551179|1349790282484
1349790390456|1322943558393|2|24189256307723|70368991551179|1349790390456

I've been thinking because I was quite baffled how this error never surfaced before. I think the reason is that this timestamp (corresponding to events on 2012-10-12) is quite far back in the update stream whose events occur between 2010-09-13 and 2012-12-31. So most systems never made it this far because they ran for 2+ hours with updates before this date.

Yeah, and on top of that, we were very unlucky with the random generator producing a 0.0. Well, I don't know if we were unlucky since the larger the SF, the more likely it will happen. It could also be that other datasets had dependent likes with a timestamp difference less than deltaTime, but larger than 0

In any case, the patch alters all data sets by changing the creationdates of the posts. I'm regenerating all data sets (with various serializers) and update streams (with different numparts between 1 and 1024).


Compilation Error for MenuItem multiple inclusion

With Flutter 3.x and slide_drawer: ^1.0.3, getting this below compilation issue while building the project.
../../../../Program_Installs/flutter/.pub-cache/hosted/pub.dartlang.org/slide_drawer-1.0.3/lib/src/container.dart:3:1: Error: 'MenuItem' is imported from both 'package:flutter/src/widgets/platform_menu_bar.dart' and 'package:slide_drawer/src/item.dart'.
import 'package:slide_drawer/src/item.dart';
^^^^^^^^
../../../../Program_Installs/flutter/.pub-cache/hosted/pub.dartlang.org/slide_drawer-1.0.3/lib/src/drawer.dart:6:1: Error: 'MenuItem' is imported from both 'package:flutter/src/widgets/platform_menu_bar.dart' and 'package:slide_drawer/src/item.dart'.
import 'package:slide_drawer/src/item.dart';
^^^^^^^^
../../../../Program_Installs/flutter/.pub-cache/hosted/pub.dartlang.org/slide_drawer-1.0.3/lib/src/drawer.dart:196:25: Error: The method 'SlideDrawerContainer' isn't defined for the class '_SlideDrawerState'.

'_SlideDrawerState' is from 'package:slide_drawer/src/drawer.dart' ('../../../../Program_Installs/flutter/.pub-cache/hosted/pub.dartlang.org/slide_drawer-1.0.3/lib/src/drawer.dart').
Try correcting the name to the name of an existing method, or defining a method named 'SlideDrawerContainer'.
Widget get _drawer => SlideDrawerContainer(
^^^^^^^^^^^^^^^^^^^^

FAILURE: Build failed with an exception.

facing this issue too on flutter 3.0.1

Seems the package is no longer maintained.
You can fork it and make the necessary changes.
or maybe use my fork.
slide_drawer:
    git:
      url: https://github.com/ndungudedan/slide_drawer.git


Upgrade Example App to Expo SDK v37

@SConaway
Thanks for PR and you can also use better implementation with better maintainability:  https://github.com/retyui/react-native-confirmation-code-field


Remove custom map_err

Implement From and TryFrom for PtlcSecret as is done for the other
variants of Message. With this done we can remove the now unused custom
map_err function.

I think this is done in #53.

I think this is done in #53.

So it is, thanks.


[BUG] Link to contribution guide is broken

Describe the bug
Line 8 of CONTRIBUTING.md links to http://azure.github.com/guidelines.html, which redirects to a 404 page.
Exception or Stack Trace
N/A
To Reproduce
Follow the link
Code Snippet
N/A
Expected behavior
Based on other azure projects, I'm assuming this should link to https://opensource.microsoft.com/collaborate.
Screenshots
N/A
Setup (please complete the following information):
N/A
Additional context
N/A
Information Checklist
Kindly make sure that you have added all the following information above and checkoff the required fields otherwise we will treat the issuer as an incomplete report

[X] Bug Description Added
[X] Repro Steps Added
[X] Setup information Added

We have migrated the link to our root contributing.md. https://github.com/Azure/azure-sdk-for-java/tree/master/sdk/core/azure-core-http-netty#contributing
Let us know if you have further questions. Thanks!


Add "trim" utility to trim strings to long for the api

The Discord api has limitations on how long embedded messages are:
https://discordjs.guide/popular-topics/embeds.html#embed-limits
We can add a trim utility that can be used to trim long strings in the raw edge case the values we are sending can be long. (like article descriptions, or even titles)

This can just be done using splice or something.


chore: normalize http api

Which issue does this PR close?
Closes #
Rationale for this change
Make

All internal apis begin with debug
Admin related apis begin with admin

What changes are included in this PR?

Are there any user-facing changes?

Yes
How does this change test
No need

Codecov Report

Merging #659 (d4a6b04) into main (3865c1b) will decrease coverage by 0.02%.
 Consider uploading reports for the commit 741e219 to get more accurate results

@@            Coverage Diff             @@
##             main     #659      +/-   ##
==========================================
- Coverage   66.95%   66.94%   -0.02%
==========================================
  Files         283      283
  Lines       43969    43969
==========================================
- Hits        29441    29436       -5
- Misses      14528    14533       +5

Impacted Files
Coverage Δ

...ry_engine/src/logical_optimizer/type_conversion.rs
90.25% <ø> (ø)

server/src/config.rs
37.20% <0.00%> (ø)

server/src/http.rs
0.00% <0.00%> (ø)

analytic_engine/src/sst/parquet/meta_data.rs
83.61% <100.00%> (ø)

sql/src/planner.rs
93.83% <100.00%> (ø)

components/skiplist/src/list.rs
98.87% <0.00%> (-0.46%)
:arrow_down:

common_types/src/column.rs
61.03% <0.00%> (-0.28%)
:arrow_down:

analytic_engine/src/instance/write_worker.rs
71.81% <0.00%> (-0.20%)
:arrow_down:

analytic_engine/src/row_iter/merge.rs
88.58% <0.00%> (-0.19%)
:arrow_down:

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


[adguard-home] externalTrafficPolicy is not set when using service with type NodePort

Helm chart name
adguard-home
Helm chart version
5.2.0
Container name
adguard/adguard-home
Container tag
v0.107.6
Description
The values.yaml file provided for adguard-home includes by default two services with type NodePort and externalTrafficPolicy set to Local.
The common chart only includes externalTrafficPolicy if the type is set to LoadBalancer and will therefore not be applied.
Expected result
That the externalTrafficPolicy is set as stated in the values file.
Helm values to reproduce
service:
    dns-tcp:
        enabled: true
        type: NodePort
        ports:
            dns-tcp:
                enabled: true
                port: 53
                protocol: TCP
                targetPort: 53
        externalTrafficPolicy: Local
    dns-udp:
        enabled: true
        type: NodePort
        ports:
            dns-udp:
                enabled: true
                port: 53
                protocol: UDP
                targetPort: 53
        externalTrafficPolicy: Local

Additional Information
No response
Repo link
No response

This is in a sense a duplicate of https://github.com/k8s-at-home/library-charts/issues/125, but we can keep it open for visibility.

This will be fixed with the imminent chart update


SW-4796 Generalize plot replacement tests

In preparation for making monitoring plot replacement create new plots on the fly,
update the tests to focus on the desired properties of the end result rather than
on the details of the existing implementation.
The existing implementation involves swapping permanent cluster numbers such that
a given cluster number refers to different plots after the replacement. We only
actually care that the original cluster no longer has the number, and that some
other cluster does, not that the two clusters' numbers were switched.
The updated tests continue to pass with the existing implementation; a subsequent
change will update the implementation without touching the tests to ensure that
existing functionality hasn't been broken.

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#1862
#1861  👈
#1860
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @sgrimm and the rest of your teammates on  Graphite

Merge activity

Apr 17, 6:26 PM EDT: @sgrimm started a stack merge that includes this pull request via Graphite.


Importing issue after upgrading from 0.23.3 to 0.24.0

First of all, thanks for this amazing package, been looking for something this for Vue 3 or even pure JS.
Describe the bug
I'm use Nuxt 3 which uses Vue 3.
Just like I said in title, I can't import the components after upgrading. it throws error.
import { Virtualizer, VList } from 'virtua/vue'

Hi, could you show me the detailed error?

Closing because it was not reproduced.
Feel free to reopen it if you have any additional information or reproduction.


Source code was not found for app:///index.bundle

OS:

[ ]  Windows
[x]  MacOS
[ ]  Linux

Platform:

[ ]  iOS
[x]  Android

Output of node -v && npm -v && npm ls --prod --depth=0
v6.11.3
3.10.10
<EMAIL_ADDRESS>/Users/khaledalqasrawi/Development/namshi-android
├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├── UNMET PEER DEPENDENCY<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>└──<EMAIL_ADDRESS>
Config:
Sentry.config(
'🔑',
      { logLevel: SentryLog.Verbose },
    ).install();

I have following issue:
I get the "Source code was not found for app:///index.bundle" error on sentry.io dashboard
I added sentry to my react native app inside an existing Android app, I used the react-native link react-native-sentry command to integrate sentry in the project and I added:
apply from: "../../node_modules/react-native-sentry/sentry.gradle"

to app/build.gradle
The map file isn't uploaded to sentry and therefore the code is not reported with the crashes, only the stack trace.
Steps to reproduce:

add sentry to the existing project using react-native link command
add the sentry gradle file to the app's build.gradle file
run the app and throw an error inside the javascript code

Actual result:

only the javascript stacktrace is reported not the code

Expected result:

the javascript code should be reported as well with the stacktrace

Should I upload the bundle and the source map manually to sentry ? is there any other information I should provide with the ticket ?
I tried uploading the bundle and the source map manually and I got a "Invalid token (401)" error
Command used to generate the bundle and the source map:
react-native bundle --platform android --entry-file index.js --bundle-output <path-to-assets>/index.bundle --sourcemap-output <path-to-assets>/index.bundle.map --assets-dest <path-to-resources> --dev false

Command used to upload the bundle and the source map to sentry:
./node_modules/.bin/sentry-cli --auth-token <auth-token> --url http://sentry.mm.taou.com releases -o <organization-name> -p <project-name> files 6.7 upload-sourcemaps --rewrite --validate <path-to-assets>/index.bundle <path-to-assets>/index.bundle.map --strip-prefix <path-to-assets>/

Hey, so it seems like you are using the wrong Auth Token.
This is not your DSN, did you call react-native link react-native-sentry?
This command should start the wizard and help you with the setup.
You can find your auth token here:
https://sentry.io/settings/account/api/auth-tokens/

Thanks for the reply, I managed to execute the upload command with the correct information, the files are uploaded now to sentry.io but I still get this error on sentry:
Source code was not found for app://index.bundle

the build artifacts names are the following:
~/index.bundle
~/index.bundle.map

Can you link an event here so I can take a look at it?

As mentioned in Issue 338 I forgot to add the RNSentryPackage:
reactInstanceManager = ReactInstanceManager.builder()
                .setApplication(getActivity().getApplication())
                .addPackage(new MainReactPackage())
                .addPackage(new RNSentryPackage(null))
                .......
                .build();

P.S: I am integrating react native in an existing Android app, the react instance is managed inside a fragment, I didn't need to implement ReactApplication anywhere, I checked the source code for RNSentryPackage and the ReactApplication constructor argument is never used in the code. that's why I used null in the constructor.

@Alqasrawi are you able to get the line number on sentry.
I need a serious help on this, but no one on the forums helping. Even the sentry people are not helping  👎

@vivek-walecha-657 Hey, no reason to be upset, I see your comment for the first time :)
What command are you running to upload the source maps? This error indicates that they are not uploaded?
Which version of react-native-sentry are you running?
Can you link me to one of your issues so I can take a look in your account?

@HazAT I have successfully generated sourcemaps via:-
react-native bundle --platform ios --entry-file index.js --dev true --bundle-output ./index.bundle --assets-dest ./dist/sourcemap.js
And then uploaded the generated sourcemap.js to sentry (this works)
sentry-cli releases files BUILDNAME upload-sourcemaps ./dist/ --dist BUILDNUMBER --strip-prefix ABSOLUTE_PATH_TO/index.js --no-rewrite
But still in the sentry console it tells me app:///index.bundle is missing. What am I doing wrong please?

For me, this https://github.com/getsentry/sentry-cli/issues/233 helped, as the path I was using was just ./build and the correct one to use was ./build/codePush.


Live plotting with Managed window cannot read the updated parameters after new experiment queued

I am using the managedwindow to live plot IV from a keithley2420.  It works but for some reason i cannot pass a parameter defined in the IVprocedure class into the queue function. here i define a parameter mode that takes the nature of the measurement 2 or 4 wires. when i queue experiments i can change that parameter in the GUI and record a new set of data. i can check in the keithley that the 4w mode is on and in the data file i do see the right mode parameter. i am trying to get that parameter as a string for my filename so i typed in str(self.mode), but the mode is stuck to the default value defined in the parameter, it is not updated after typing in the new value in the GUI whereas the right data appears in the file?.  i use fake data to test the code below.
import logging
log = logging.getLogger(__name__)
log.addHandler(logging.NullHandler())

import sys
import tempfile
from tempfile import NamedTemporaryFile
import random
import datetime
from datetime import datetime as dt, timedelta
import time
from time import sleep
import pandas as pd
from pymeasure.log import console_log
from pymeasure.display.Qt import QtGui
from pymeasure.display.windows import ManagedWindow
from pymeasure.experiment import Procedure, Results
from pymeasure.experiment import IntegerParameter, FloatParameter, Parameter

class RandomProcedure(Procedure):
    iterations = IntegerParameter('Loop Iterations', default=10)
    delay = FloatParameter('Delay Time', units='s', default=0.2)
    seed = Parameter('Random Seed', default='20')
    mode = IntegerParameter('2 or 4 probes measurement', default=2)

    DATA_COLUMNS = ['Iteration', 'Timecode', 'Elapsed', 'Random Number']

    def startup(self):
        log.info("Setting the time of the random number generator")
        random.seed(self.seed)

    def execute(self):
        log.info("Starting the loop of %d iterations" % self.iterations)
        start = datetime.datetime.now()
        for i in range(self.iterations):
            timecode = dt.now()
            elapsed = (datetime.datetime.now() - start).total_seconds()
            data = {
                # 'Mode': self.mode,
                'Iteration': i,
                'Timecode': timecode,
                'Elapsed': elapsed,
                'Random Number': random.randint(1, 100)
            }
            self.emit('results', data)
            log.debug("Emitting results: %s" % data)
            sleep(self.delay)
            if self.should_stop():
                log.warning("Caught the stop flag in the procedure")
                break

class MainWindow(ManagedWindow, RandomProcedure):

    def __init__(self):
        super(MainWindow, self).__init__(
            procedure_class=RandomProcedure,
            inputs=['iterations', 'delay', 'seed', 'mode'],
            displays=['iterations', 'delay', 'seed', 'mode'],
            x_axis='Iteration',
            y_axis='Random Number',
            sequencer=True,  # Added line
            sequencer_inputs=['iterations', 'delay', 'seed', 'mode'],  # Added line
            # sequence_file="gui_sequencer_example_sequence.txt",  # Added line, optional
        )
        self.setWindowTitle('GUI Example')
        self.count = 0

    def queue(self, *, procedure=None):
        self.count = self.count + 1
        filename = 'D:\\test\\' + str(dt.now().strftime("%m%d%Y"))+'_' + 'mode_' + str(self.mode) + '_' + str(self.count) + '.csv'
        log.info("Constructing the Results with a data file: %s" % filename)
        if procedure is None:
            procedure = self.make_procedure()
        results = Results(procedure, filename)
        experiment = self.new_experiment(results)
        self.manager.queue(experiment)
        # mode = self.mode

if __name__ == "__main__":
    app = QtGui.QApplication(sys.argv)
    window = MainWindow()
    window.show()
    sys.exit(app.exec_())

Hi! I may have a suggestion for your issue which is probably more a workaround than a proper solution ...
Since both the inputs and sequencer_inputs objects defined in the init istance of your ManagedWindow class belong to qt textbox widgets, you could resort to the textbox method text() to recover the string in the textbox.
In a nutshell: filename = 'D:\test\' + str(dt.now().strftime("%m%d%Y"))+'' + 'mode' + self.sequencer_inputs.mode.text() + '_' + str(self.count) + '.csv' if the mode input is given as a sequencer input, or rather self.inputs.text() if the mode is specified in the ManagedWindow textbox widget
I hope this helps you out with your problem!

Thanks for your time @Daivesd , tested it , it does work for the update of the filename but then the execute is stuck so i believe the variable is not updated in the queue or the format is wrong. I ve been proposed a working solution here Trouble with scoping #302. I am now able to run various experiments and save with different filenames and modes.

Ok sorry I didn't realize this issue was already solved in another topic! Actually the 'real' solution is even more general and will work even when using sequencer in ManagedWindow as it sets the relevant parts of the filename in the procedure itself!
thank you very much for pointing that topic out


executor: both collide and fault injection are enabled error

Syzbot has recently found a way to crash syz-executor with the "both collide and fault injection are enabled" error. It has even found a reliable reproducer for that.
#{"repeat":true,"procs":1,"slowdown":1,"sandbox":"none","fault_call":-1,"tun":true,"netdev":true,"resetnet":true,"cgroups":true,"binfmt_misc":true,"close_fds":true,"usb":true,"vhci":true,"wifi":true,"ieee802154":true,"sysctl":true,"tmpdir":true,"segv":true}
r0 = openat(0xffffffffffffff9c, &(0x7f0000000000)='/proc/self/exe\x00', 0x0, 0x0)
perf_event_open(&(0x7f0000000300)={0x6, 0x80, 0x1, 0x0, 0x0, 0x0, 0x4, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, @perf_bp={&(0x7f0000000000), 0xdc17}}, 0x0, 0x0, 0xffffffffffffffff, 0x0)
mmap(&(0x7f0000000000/0x800000)=nil, 0x800000, 0x1800003, 0x12, r0, 0x0)

I verified it by manual execution and it reproduces in 100% cases. Commenting the perf_event_open or mmap out prevents the crash from happening.

The fuzzer found lots of creative ways to exploit itself in the past. I don't see any 100% bulletproof way to prevent such corruptions other than moving all state/coverage/shmem to a separate parent process and using the test process only to execute syscalls. But this looks like lots of complexity and potential additional slowdown (?).
Other related issues #487 and #502
But we can address both particular ways to exploit and detect particular corruptions. Some of these changes may be useful for other reasons. But I would like to not over-engineer these protections and not add too much complex code because (1) most of these are still best-effort and (2) some of these will need to present in the generated C reproducers so that they behave the same way as executor.
One of the protections that would be useful for other reasons (will also fix #477) is this "prog: don't morph calls into other known calls":
https://github.com/dvyukov/syzkaller/commit/cd4daf14452ee65caaf268f92e3242e338647533
It turned out to be quite complex in the whole generality so I never finished it, but maybe there is a way to limit scope and generality.
One other thing I always wanted to do is to enable ASLR. It may prevent false coverage as we execute the test several times before adding to the corpus and it will also prevent harmful corpus pollution/inflation. But unfortunately ASLR can't be enabled for static binaries, which we use because host/target has different glibc versions. Maybe there is some way to make a binary dynamic, but not dependent on any libraries.
Additionally we could do manual randomization for shmem mmaps (currently mapped at hard-to-guess, but fixed addresses).
Re /proc/self/exe, I wonder if there is a way to chmod as read-only somehow, that should prevent writable mmaps and writes. But we also need to somehow prevent the test from chmod'ing it back.

Maybe there is some way to make a binary dynamic, but not dependent on any libraries.

-static-pie may do what we want.
cat /tmp/test.c
#include <stdio.h>
int main() {
	printf("%p\n", &main);
}

~💻 gcc /tmp/test.c -static-pie
~💻 ./a.out
0x7f28632c7db5
~💻 ./a.out
0x7fbf741e2db5
~💻 ./a.out
0x7fd9b5a26db5

Tested on a local syzkaller instance - -static-pie works. 17 hours of fuzzing time and my intentionally introduced and regularly checked global syz-executor variables have not been corrupted. Also, no output from test machine errors have become noticeably less frequent.
I'll prepare a pull request.

After ASLR was merged, the issue haven't popped up anymore. Closing the issue.


[ENH] Add random_state to statsmodels adapter

Reference Issues/PRs
#2388
What does this implement/fix? Explain your changes.
Adds random_state to statsnmodels so that it can be called internally by any model.
Does your contribution introduce a new dependency? If yes, which one?
No
What should a reviewer concentrate their feedback on?

[x] Have passed random_state to statsmodeladapter
[x]  Passed it as an argument to get_predictions method.

PR checklist

For all contributions

[ ] I've added myself to the list of contributors.
[ ] Optionally, I've updated sktime's CODEOWNERS to receive notifications about future changes to these files.
[ ] I've added unit tests and made sure they pass locally.
[ ] The PR title starts with either [ENH], [DOC] or [BUG] indicating wether the PR topic is related to enhancement, documentation or bug

For new estimators

[ ] I've added the estimator to the online documentation.
[ ] I've updated the existing example notebooks or provided a new one to showcase how my estimator works.

@fkiraly I have added the parameter to all the models.

@fkiraly I checked with the AutoETS model (the model in which the problem existed) and I'm still getting the randomness in the results as in #2320

I set random_state =0 and still, there is some randomness in the results.

might be the **kwargs where you have to pass it also?

oh thos are prediction intervals that you showed, that might not be related to the estimator. Can you pls add a test for testing the predictions for random? You would have to fit and predict the same estimator twice and make assert_frame_equal or assert_series_equal

I tried to loop through the models by creating a models list and iterating through it but I got an error unknown keyword argument random_state error thus I did not loop through the models .

are you using the all_estimators utility?
You may want to check whether random_state is in get_params().keys()

Is this implementation okay or should I make some changes?

@fkiraly , @aiwalter  Sorry for disturbing ; but could you please review the changes I have made ?

@fkiraly I think I made the suggested changes . Pls review them .

we need the tests ro pass before merge of course


[v0.6.5] No icon in the search results

I've updated hain to the latest release(0.6.5) and found there are no icons in the search results list, like the screenshot below:

Thank you for the reporting, I think i've missed rebuilding native module for Windows (because I'm using macOS only for now)
I'll try to fix it soon


NIFI-6374 ConsumeEWS fails when email attachment has no content type

Thank you for submitting a contribution to Apache NiFi.
Please provide a short description of the PR here:
In the ews API Attachment.getContentType may return null.
In that case, we get an exception when writting message file.
Description of PR
fixes bug NIFI-6374.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

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

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

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

[x] 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:

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

@jf-beauvais Thanks for the fix. Change looks good. +1. Merging to master!


Fix Github Action Dependency Error

Potential fix to solve issue in #74
This is untested so could run into errors down the road.

Thanks, this seems to work for now. I'll need to resolve the source of the issue or switch back to yarn at some point. Thanks!


Feature/travisci build

Summary
Adds a travis-ci build configure to the project. This will allow us to see if commit code actually builds. Eventually we will be able to configure travis-ci to run all of our unit tests.
NOTE This will not work until the .travis.yml file is merged into the default branch ie master.
Details
.travis.yml is used to tell travis-ci how to build the Android project and eventually it will configured to run the project's unit tests.
gradle.build is only used to tell travis-ci how to build the Android project. It should not affect importing the project.

Did not want to merge into master


Potential label leakage Issue: Label strings are in inputs for both training and inference.

Reminder

[X] I have read the README and searched the existing issues.

System Info
Latest version.
Reproduction
TRAINING INPUTS:
<|im_start|>user
INPUT_STRING
<|im_end|>
<|im_start|>assistant
LABELS_STRING <|im_end|>

TRAINING OUTPUTS:
LABELS_STRING

The training inputs contain LABELS_STRING to LLMs. The input should not contain 'LABELS_STRING', otherwise there is an overlap between input_ids and label_ids (due to 'LABELS_STRING' in both)!
This holds true for QWEN25 model. There could be a label leakage.
Expected behavior
The LABELS_STRING ('output') field should not be in the input string during training and inference.
From training log, however, it is found that the 'output' field (which should be the model response/label string) from the data file gets concat to the input string to LLMs (causing label leakage) during training.
This issue applies to many models, including Qwen25 and many others.
Others
Could you please investigate this issue (on why the 'output'/response field are inside the input string to LLMs during training/inference)?

Please learn the concept of training casual language models, there is no bug in current implementation.


Set version to 2.0.0; add release GitHub Workflow

This PR updates stac-pydantic to version 2.0.0 in preparation for the upcoming release. It modified the CHANGELOG accordingly, and adds a GitHub Workflow for releases. The action is based on what PySTAC and pystac-client use for their own releases.
Related #91

Codecov Report

Merging #92 (86e7961) into master (089e30e) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #92   +/-   ##
=======================================
  Coverage   96.06%   96.06%
=======================================
  Files          20       20
  Lines         457      457
=======================================
  Hits          439      439
  Misses         18       18

Flag
Coverage Δ

unittests
96.06% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

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 089e30e...86e7961. Read the comment docs.


Move phpcs to Github actions

Codecov Report

Merging #3 into 2.1.x will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##              2.1.x       #3   +/-   ##
=========================================
  Coverage     82.12%   82.12%
  Complexity     3835     3835
=========================================
  Files           128      128
  Lines          8630     8630
=========================================
  Hits           7087     7087
  Misses         1543     1543

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 5ac210b...37a320f. Read the comment docs.


Adding ROCm support to run_pip_tests.sh

Need to quickly fix an issue with bazel-based PIP unit testing in the r1.15-rocm branch.  This PR adds ROCm support to run_pip_tests.sh

Can one of the admins verify this patch?


Clone not happening properly.

Clone is not proper.
The width of the original thead is not replicated in the cloned one.
see the attached snapshot

Yeah I did notice that.  I'm not personally developing in Angular anymore,
I've switch to react.  However I'm still attempting to maintain this, and
as such, I accepted a pull request from someone that fixed some other
issues and this bug was introduced.  If you'd like to fix it and submit a
pull request, I'd be happy to pull it in.
Thanks,
Keith.
On Tue, May 10, 2016 at 3:58 AM himanshuchaudhary<EMAIL_ADDRESS>wrote:

Clone is not proper.
The width of the original thead is not replicated in the cloned one.
see the attached snapshot
[image: issue]
https://cloud.githubusercontent.com/assets/16831718/15142692/d27b16f2-16c3-11e6-95da-ff3c9f7335bf.PNG
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/FutureStateMobile/sticky-header/issues/41


Emqx 30 acl cache v2

cache using process process dictionary
An improvement solution of https://github.com/emqtt/emqttd/pull/1732.
Remove the ordered circular buffer, using an FIFO keys-queue instead.
The cache is still implemented using process dictionary, and each cache entry in the cache is of following format:
|-- CacheK --|-- CacheV --|

where:

CacheK: {Access :: publish | subscribe, Topic :: topic()}
CacheV: {AclResult :: allow | deny, TimeNow :: timestamp()}

The CacheK are also stored in the keys-queue, in the order of their insertion.
cache replacement and eviction

If the max-size reached, the oldest cache entry will be replaced first, and then the 2nd oldest one. This is called replacement or eviction.
It would try to remove all the expired cache entries if the result returned by get_acl_cache/2 was expired. This is called cleanup.
If the cache is full and also the newest cache entry is expired, all the entries will be deleted. This called empty.

avg algorithm complexity:

cache put: O(1)
cache get: O(1)
replacement: O(1)
cleanup: O(N/2)
empty: O(N)

updated some test cases