Rootmotion track problem

Tested versions
Godot4.2
System information
Windows10-Godot4.2
Issue description
Hi, I am using godot4.2 and I am facing this problem is that my character cant rotate when he is moving 45 degree angle he should also rotate aswell, here is the video.
Is there a way to fix this problem or that's how godot works.
Btw I also animated the root to rotate when he is moving in 45 degree angle, is that the cause of it or I have found a bug??? {Open for suggestions} ThankQ
https://github.com/user-attachments/assets/1ee35419-d37a-4763-9951-1ed5bb964575
Steps to reproduce
Please do let me know if that was a bug or some issue in blender while I animated the root bone to rotate 45 degree angle so that the character should look at 45degree angle when I press forward and left or right button
Minimal reproduction project (MRP)
RootMotionProblem.zip
I have exported the models with animation properly enabled all the necessary stuff
I am using godot4.2 i have the updated version in steam, so far it is the latest version, I have heard godot4.3 has come but it haven't came out yet in steam

Please upload an MRP to help with testing this:

A small Godot project which reproduces the issue, with no unnecessary files included. Be sure to not include the .godot folder in the archive (but keep project.godot).
Having an MRP is very important for contributors to be able to reproduce the bug in the same way that you are experiencing it. When testing a potential fix for the issue, contributors will use the MRP to validate that the fix is working as intended.
Drag and drop a ZIP archive to upload it (max 10 MB). Do not select another field until the project is done uploading.
Note for C# users: If your issue is not C#-specific, please upload a minimal reproduction project written in GDScript. This will make it easier for contributors to reproduce the issue locally as not everyone has a .NET setup available.

It is the expected behavior and nothing has changed from the past. The root motion must be applied to any Node3D transform by extracting the transform values from the AnimationTree using get_root_motion_xxx after setting the root motion track. Read the documentation.

Please upload an MRP to help with testing this:

A small Godot project which reproduces the issue, with no unnecessary files included. Be sure to not include the .godot folder in the archive (but keep project.godot).
Having an MRP is very important for contributors to be able to reproduce the bug in the same way that you are experiencing it. When testing a potential fix for the issue, contributors will use the MRP to validate that the fix is working as intended.
Drag and drop a ZIP archive to upload it (max 10 MB). Do not select another field until the project is done uploading.
Note for C# users: If your issue is not C#-specific, please upload a minimal reproduction project written in GDScript. This will make it easier for contributors to reproduce the issue locally as not everyone has a .NET setup available.

Should I give you tscn where there is  character and animation???

Please upload an MRP to help with testing this:

A small Godot project which reproduces the issue, with no unnecessary files included. Be sure to not include the .godot folder in the archive (but keep project.godot).
Having an MRP is very important for contributors to be able to reproduce the bug in the same way that you are experiencing it. When testing a potential fix for the issue, contributors will use the MRP to validate that the fix is working as intended.
Drag and drop a ZIP archive to upload it (max 10 MB). Do not select another field until the project is done uploading.
Note for C# users: If your issue is not C#-specific, please upload a minimal reproduction project written in GDScript. This will make it easier for contributors to reproduce the issue locally as not everyone has a .NET setup available.

here is my file
RootMotionProblem.zip

There is only bones of the rig that I can only select what do you mean
about any node3d??
On Sun, 11 Aug 2024, 6:52 pm Silc Lizard (Tokage) Renew, <
@.***> wrote:

It is the expected behavior and nothing has changed from the past. The
root motion must be applied to any Node3D transform by extracting the
transform values from the AnimationTree using get_root_motion_xxx after
setting the root motion track. Read the documentation.
—
Reply to this email directly, view it on GitHub
https://github.com/godotengine/godot/issues/95380#issuecomment-2282768495,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AWVWCWKOJQ4777TWUVJGYRTZQ5UCVAVCNFSM6AAAAABMKMDIQCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOBSG43DQNBZGU
.
You are receiving this because you authored the thread.Message ID:
@.***>

It is the expected behavior and nothing has changed from the past. The root motion must be applied to any Node3D transform by extracting the transform values from the AnimationTree using get_root_motion_xxx after setting the root motion track. Read the documentation: https://docs.godotengine.org/en/stable/classes/class_animationmixer.html#class-animationmixer-method-get-root-motion-position

This is tooo complicated 4 me, is there any other way where godot dev to fix this problem
I mean just imagine the root bone is perfectly moving but why does it cancel the root bone rotation.
I hope they fix in the latest update 🙏🙏🙏

It is the same in Unity and Unreal that RootMotion will no longer play the Root bone animation directly. You must get the RootMotion from the AnimationMixer and add it yourself in a script to the parent transform of any Skeleton.

It is the same in Unity and Unreal that RootMotion will no longer play the Root bone animation directly. You must get the RootMotion as Vector3 or Quaternion from the AnimationMixer and add it yourself in a script to the transform of the any ancestor object of Skeleton.
Since root motion is a relative value, if you want to add root_motion_position, simply use the following expression like: Node3D.position += AnimationTree.get_root_motion_position(). It is almost same for rotation/Quaternion as Node3D.rotation *= AnimationTree.get_root_motion_rotation(), just applying general 3D math.
For the advanced case, if you want to blend multiple animations, you will need an accumlator, so refer to the code in the documentation.

If I use mixamo animation it is fine like it rotates the way it needs but if I use my custom rig with animation it does not work.
If you see my video i did not even add a script  but I use an animation tree node to blend the strafing animation if I apply the root to the rootmotion track it stops rotating but if I use mixamo animation then it works perfectly fine.
I just hope the godot dev to fix this rootmotion track.
Isn't there other way to fix this problem without a code???

If you don't want to use the code, just apply the rotation in DCC software such as blender to replace/convert the rotation track with a position track.

If you don't want to use the code, just apply the root rotation in DCC software such as blender to replace/convert the rotation track with a position track. In other words, current MRP animations aren't following the optimal workflow for creating animations when using root motion.
The root motion considers only delta. This is the intended behavior, since a rotation track with only one key has no delta in the rotation. If you do not want to change the animation, the accumulator must be handled in code;
Application process of the accumulators depends on the use case, so users need to apply the accumulators in any order they want. For example, whether the rotation is consistently global, consistently local, or a mix of the two and thus the order of calculations needs to be changed depending on the state, is dependent on the use case.

In blender I will have to add another root bone and from that I can rotate my character, like this way.
One root bone will be use to move the character and the other root bone I will name it (root.z) that will be use to rotate the character.
I will export from blender to godot and if I assign the root bone (not root.z) to the rootmotion track hopefully that will work.
I will update it once it work.


Automated Tests with Azure blob storage using Azurite

This document is highlighting how to use Azurite in Azure blob store for automated tests.
Document covers how to run automated tests using python code snippet on local and pipeline with a YAML pipeline.
Hope this will be helpful for the community. Looking forward to hear your feedback.
Thanks

Microsoft authors of articles need to make updates through the private repository so the updates can be staged and validated by the current validation rules. After you review staging and fix all validation issues, you can add the sign-off comment to let the PR reviewers know the updates are ready to be merged.It's easy to access the private repo version of your articles in GitHub. Just add -pr to the URL, as follows:
Public repo URL: https://github.com/MicrosoftDocs/azure-docs
Private repo URL: https://github.com/MicrosoftDocs/azure-docs-pr
We have closed this pull request. Please resubmit the updates through the private repo. For more information, [see the contributor guide].(https://docs.microsoft.com/en-us/contribute/)

I couldn't reach to private repo, Do I need to create a PR to resubmit?


We have public edit!!

@JennieHubbard,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/linux/sql-server-linux-manage-ssms.md
:white_check_mark:Succeeded

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

Sudeep noted the 4 build warnings are ok.


mayhem integration

We'll need to explain that arbitrary was a necessary addition for fuzzing to upstream, but otherwise LGTM!


Servers

None of my server pictures show. There're just a bunch of boxes that say public. I cant access the servers either. Any ideas?

disable the public button in BD core settings (the feature is broken) then reload with ctrl+R


Git: Support display of more than one remote under Incoming section of SCM view

Type: Feature Request
As a contributor to OSS I have the following setup:
> git remote -v
origin  https://github.com/gjsjohnmurray/vscode.git (fetch)
origin  https://github.com/gjsjohnmurray/vscode.git (push)
upstream        https://github.com/microsoft/vscode.git (fetch)
upstream        https://github.com/microsoft/vscode.git (push)

To update my tracking branch I currently do the following while on 'main':

Run Fetch From All Remotes from the Pull, Push submenu (or from Command Palette)
Run Merge... from the Branch submenu
Pick upstream/main

It'd be nice to have 'upstream/main' inthe Incoming section as well as 'origin/main', and for it to offer 'Fetch' and 'Merge' buttons.
VS Code version: Code - Insiders 1.87.0-insider (442c133fe92b5e2606c8242caae4e68938faccc7, 2024-02-01T09:49:33.086Z)
OS version: Windows_NT x64 10.0.22621
Modes:

This feature request has not yet received the 20 community upvotes it takes to make to our backlog. 10 days to go. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

:slightly_frowning_face: In the last 60 days, this feature request has received less than 20 community upvotes and we closed it. Still a big Thank You to you for taking the time to create this issue! To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

@lszomoru please reconsider making improvements to the Incoming/Outgoing area to make it more useful for contributors to a project, who routinely work with two remotes.

Closing this issue since the incoming/outgoing section has been deprecated.


fix Gradle signing

Some lovely hacks for getting the signing plugin to work, copied from another of my projects.
https://github.com/adamko-dev/kotlinx-serialization-typescript-generator/blob/2914dd6256600671f37583c5371759cc8ec27393/buildSrc/src/main/kotlin/buildsrc/convention/maven-publish.gradle.kts
To test, run ./gradlew publishAllPublicationsToMavenProjectLocalRepository and check ./build/maven-project-local for .asc files.

Nice work :)

Yeah, if it works! 😅

Looks like we're getting there at least 😂


Update cats-effect, cats-effect-kernel, ... to 3.2.6

Updates

org.typelevel:cats-effect
org.typelevel:cats-effect-kernel
org.typelevel:cats-effect-laws
org.typelevel:cats-effect-std
org.typelevel:cats-effect-testkit

from 3.2.5 to 3.2.6.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.typelevel" } ]

labels: library-update, semver-patch

Superseded by #44.


Training script for StructLM-7B-Mistral.

Could you please provide the training script for StructLM-7B-Mistral? As I find there is a difference between the format of training data https://huggingface.co/datasets/TIGER-Lab/SKGInstruct-skg-only and test data skginstruct_test_file_mistral.json.
E.g., for the WTQ dataset,
Input format of training data

Input format of test data

There is no "### Response:\n" in the training dataset. Is there an anthor data preprocessing script in the training of StructLM-7B-Mistral?

Hi there, we use stanford Alpaca training script to train it. So it follows the alpaca prompt format. The library we are using is here at https://github.com/tatsu-lab/stanford_alpaca.

I got it, thanks for your replay!


Switch to using UIProtect library

With Unifi OS 4.0.3 I can't get the existing container to connect using either latest or dev branch (both with and without experimental downloader flag). I am using a valid SSL Cert too, so that's not an issue (with SSL Verify both on and off).
With latest I get AttributeError: 'NoneType' object has no attribute 'split' (in cookies)
With dev I get /proxy/protect/api/bootstrap - Status: 401 - Reason: {'code': 401, 'message': 'Unauthorized'}
I have tested the latest HomeAssistant Unifi Protect plugin which has recently switched to using UIProtect library and that connects fine to unifi, so it has to be an issue that still remains in the auth of pyunifiprotect, hence the attempt to upgrade.
I'm not a python dev and I'm Windows based so have taken this as far as I can, but this PR looks about 95% correct I think. I note it needs to use Python 3.10.
Doing a 'docker build .' gives lots of ': No such file or directory bash' but I'm pretty sure it would be an easy fix for someone who knows python, it's tooling and the existing codebase.
I'd do more to sort this but I'm a bit worn out. I'm trying to take live offsite backups of CCTV for a building right next door to a mosque where we have been given police intelligence it's likely to be targeted this evening by riots. Hopefully nothing happens as I've spent all day trying to get offsite backups working but I have failed meaning I won't have any CCTV if things do kick off. Fingers Crossed.

Hi,
So sorry to hear about the riots here in the UK affecting you, truly is shameful what they are doing.
Could you please open an issue to track the problem you are having separate to this?
I'm afraid the switch to uiprotect has been hung up on a PR to add the new experimental downloader. Unfortunately none of us involved have had the time to get that PR over the line. I think what I will do is roll back that feature and make the upgrade without it.

FWIW, regarding the initial issue: I am using Unifi OS 4.0.12 w/ Protect 4.0.33 with the latest tag of the docker container without issues. It might be worth trying to upgrade. (Sorry, I know that this comment should be on an issue, but mentioning it here in case it helps for tonight. I hope the riots don't materialise tonight!)

@ep1cman and @Sticklyman1936 thanks for the support. I have opened issue #161 to track the actual issue instead of solutionising here.
So far my community building is safe and I have partially managed to get it working by hooking up the RTSP fields on the external facing cameras to an ffmpeg dump so if something does happen at least I should get video of those involved. It's not an ideal solution though as it records everything rather than just motion or people so it's a temp workaround for the immediate crisis.

Thanks for this PR, I've tested this and suprisingly things seem to be working smoothly out of the box. I was expecting some level of breaking changes but it looks like we got lucky.
I have one question, why were dev/test dependencies made non optional? These really shouldn't be installed by anyone except people developing this tool

It might be my lack of knowledge of the dev tooling, but whenever I ran 'poetry install -E dev' or for -E test it couldn't find any dependencies. I think in newer versions of poetry the config for setting up optional groupings is probably different. I brute forced a fix by making them required so they installed correctly (for me). Someone who knows poetry better would probably be able to migrate to a newer config format that is understood by the tooling.

if you could undo that I will look into it and update as needed. I suspect I just need to change the command to run in the cotribution guide. In general that document needs some love

I've reverted the dev/test optional code now


THCI: update thci with new methods.

Add setRouterDowngradeThreshold() method support.
Add new sendBeacons() method to ensure compile pass temporarily.

Current coverage is 64.24% (diff: 100%)

Merging #602 into master will increase coverage by 0.02%

@@             master       #602   diff @@
==========================================
  Files            94         94
  Lines         14053      14053
  Methods        1916       1916
  Messages          0          0
  Branches       1659       1659
==========================================
+ Hits           9025       9029     +4
+ Misses         4514       4512     -2
+ Partials        514        512     -2

Powered by Codecov. Last update 5c28c02...34edbf5

notice that sendBeacons() has been added in #591.

@xiaom-GitHub Please include sendBeasons() in your PR, #591 is not ready for merge now.

@chshu got it, let me restore this.


Can I use create NFS Server  on jiva pool ? I Does not require high performance

I just want add some pictures and zips in NFS Server ,does not require high performance.

Hi @dingsongjie . Thanks for choosing OpenEBS for your particular use-case.
Yes, NFS server can be created on Jiva. We have written one document for cStor as OpenEBS volume. By changing the StorageClass mentioned for cStor with Jiva StorageClass, you can achieve this particular use case.
This is the reference doc : https://docs.openebs.io/docs/next/rwm.html
Note: Skip the select or create cStor pool and mention Jiva StorageClass name instead of cStor StorageClass. Let me know if any more information is needed.

Hi @dingsongjie . Thanks for choosing OpenEBS for your particular use-case.
Yes, NFS server can be created on Jiva. We have written one document for cStor as OpenEBS volume. By changing the StorageClass mentioned for cStor with Jiva StorageClass, you can achieve this particular use case.
This is the reference doc : https://docs.openebs.io/docs/next/rwm.html
Note: Skip the select or create cStor pool and mention Jiva StorageClass name instead of cStor StorageClass. Let me know if any more information is needed.

Thank you for your reply ，I would try this

It works fine ,thank you again !


libpng error: bad parameters to zlib

Issue:
$ wgrib2 file.grib2 -netcdf out.nc
libpng error: bad parameters to zlib

*** FATAL ERROR: unpk: png decode error -3 ***

Encountered with .grib2 files found here.

Environment (conda list):

$ conda list
# packages in environment at /root/miniconda3/envs/temp:
#
# Name                    Version                   Build  Channel
_libgcc_mutex             0.1                 conda_forge    conda-forge
_openmp_mutex             4.5                       1_gnu    conda-forge
bzip2                     1.0.8                h7f98852_4    conda-forge
c-ares                    1.17.1               h36c2ea0_0    conda-forge
ca-certificates           2020.11.8            ha878542_0    conda-forge
curl                      7.71.1               he644dc0_8    conda-forge
g2clib                    1.6.0                hf3f1b0b_9    conda-forge
hdf4                      4.2.13            h10796ff_1004    conda-forge
hdf5                      1.10.6          nompi_h6a2412b_1112    conda-forge
jasper                    1.900.1           h07fcdf6_1006    conda-forge
jpeg                      9d                   h36c2ea0_0    conda-forge
krb5                      1.17.2               h926e7f8_0    conda-forge
libcurl                   7.71.1               hcdd3856_8    conda-forge
libedit                   3.1.20191231         he28a2e2_2    conda-forge
libev                     4.33                 h516909a_1    conda-forge
libgcc-ng                 9.3.0               h5dbcf3e_17    conda-forge
libgfortran-ng            9.3.0               he4bcb1c_17    conda-forge
libgfortran5              9.3.0               he4bcb1c_17    conda-forge
libgomp                   9.3.0               h5dbcf3e_17    conda-forge
libnetcdf                 4.7.4           nompi_hefab0ff_106    conda-forge
libnghttp2                1.41.0               h8cfc5f6_2    conda-forge
libpng                    1.6.37               h21135ba_2    conda-forge
libssh2                   1.9.0                hab1572f_5    conda-forge
libstdcxx-ng              9.3.0               h2ae2ef3_17    conda-forge
mysql-connector-c         6.1.11            h6eb9d5d_1007    conda-forge
ncurses                   6.2                  h58526e2_4    conda-forge
openssl                   1.1.1h               h516909a_0    conda-forge
tk                        8.6.10               hed695b0_1    conda-forge
wgrib2                    2.0.8                h5a10b45_1    conda-forge
zlib                      1.2.11            h516909a_1010    conda-forge

Details about  conda and system ( conda info ):

$ conda info
 active environment : temp
    active env location : /root/miniconda3/envs/temp
            shell level : 3
       user config file : /root/.condarc
 populated config files : /root/.condarc
          conda version : 4.9.2
    conda-build version : not installed
         python version : 3.8.5.final.0
       virtual packages : __glibc=2.23=0
                          __unix=0=0
                          __archspec=1=x86_64
       base environment : /root/miniconda3  (writable)
           channel URLs : https://conda.anaconda.org/conda-forge/linux-64
                          https://conda.anaconda.org/conda-forge/noarch
                          https://repo.anaconda.com/pkgs/main/linux-64
                          https://repo.anaconda.com/pkgs/main/noarch
                          https://repo.anaconda.com/pkgs/r/linux-64
                          https://repo.anaconda.com/pkgs/r/noarch
          package cache : /root/miniconda3/pkgs
                          /root/.conda/pkgs
       envs directories : /root/miniconda3/envs
                          /root/.conda/envs
               platform : linux-64
             user-agent : conda/4.9.2 requests/2.24.0 CPython/3.8.5 Linux/5.4.0-52-generic ubuntu/16.04.7 glibc/2.23
                UID:GID : 0:0
             netrc file : None
           offline mode : False

I am seeing this on both xenial and bionic, but bizarrely it's working just fine (with the same files) on a production xenial machine (although I can't guarantee how that machine was configured).
The only notable difference is that it's using an older conda version: 4.3.30 vs 4.9.2.
Environment (conda list):

$ conda list
# packages in environment at /home/alert/.conda/envs/radar:
#
asn1crypto                0.22.0                   py36_0    conda-forge
backports                 1.0                      py36_1    conda-forge
backports.functools_lru_cache 1.5                      py36_0    conda-forge
biggus                    0.15.0                   py36_0    conda-forge
boost                     1.66.0                   py36_1    conda-forge
boost-cpp                 1.66.0                        1    conda-forge
bzip2                     1.0.6                         1    conda-forge
ca-certificates           2018.1.18                     0    conda-forge
cairo                     1.14.10                       0    conda-forge
cartopy                   0.15.1                   py36_5    conda-forge
cdo                       1.3.5                     <pip>
cdo                       1.9.2                         0    conda-forge
certifi                   2018.1.18                py36_0    conda-forge
cf_units                  1.2.0                    py36_0    conda-forge
cffi                      1.11.2                   py36_0    conda-forge
chardet                   3.0.4                    py36_0    conda-forge
cryptography              2.1.4                    py36_0    conda-forge
curl                      7.55.1                        0    conda-forge
cycler                    0.10.0                   py36_0    conda-forge
dbus                      1.10.22                       0    conda-forge
eccodes                   2.6.0                         1    conda-forge
ecmwf-grib-api            1.23.1                        0    eumetsat
ecmwf_grib                1.23.1                        2    conda-forge
expat                     2.2.5                         0    conda-forge
fftw                      3.3.7                         0    conda-forge
fontconfig                2.12.4               h88586e7_1
freetype                  2.8.1                         0    conda-forge
freexl                    1.0.4                         0    conda-forge
g2clib                    1.6.0                         5    conda-forge
gdal                      2.2.3                    py36_0    conda-forge
geos                      3.6.2                         1    conda-forge
geotiff                   1.4.2                         1    conda-forge
gettext                   <IP_ADDRESS>                      0    conda-forge
giflib                    5.1.4                         0    conda-forge
glib                      2.55.0                        0    conda-forge
gst-plugins-base          1.8.0                         0    conda-forge
gstreamer                 1.8.0                         1    conda-forge
hdf4                      4.2.13               h3ca952b_2
hdf5                      1.10.1                        1    conda-forge
icu                       58.2                          0    conda-forge
idna                      2.6                      py36_1    conda-forge
intel-openmp              2018.0.0             hc7b2577_8
iris                      1.13.0                   py36_1    conda-forge
jasper                    1.900.1                       4    conda-forge
jpeg                      9b                            2    conda-forge
json-c                    0.12.1                        0    conda-forge
kealib                    1.4.7                         4    conda-forge
krb5                      1.14.2                        0    conda-forge
libdap4                   3.18.3                        2    conda-forge
libffi                    3.2.1                         3    conda-forge
libgcc                    7.2.0                h69d50b8_2
libgcc-ng                 7.2.0                h7cc24e2_2
libgdal                   2.2.3                         3    conda-forge
libgfortran               3.0.0                         1
libgfortran-ng            7.2.0                h9f7466a_2
libiconv                  1.15                          0    conda-forge
libkml                    1.3.0                         6    conda-forge
libmo_unpack              3.0                           1    conda-forge
libnetcdf                 <IP_ADDRESS>                      10    conda-forge
libpng                    1.6.34               hb9fc6fc_0
libpq                     9.6.3                         0    conda-forge
libspatialite             4.3.0a                       19    conda-forge
libssh2                   1.8.0                         2    conda-forge
libstdcxx-ng              7.2.0                h7a57d05_2
libtiff                   4.0.9                h28f6b97_0
libxcb                    1.12                          1    conda-forge
libxml2                   2.9.7                         0    conda-forge
libxslt                   1.1.32                        0    conda-forge
lxml                      4.1.1                    py36_0    conda-forge
matplotlib                2.1.2                    py36_0    conda-forge
mkl                       2018.0.1             h19d6760_4
mo_pack                   0.2.0                    py36_1    conda-forge
mysql-connector-c         6.1.6                         0    conda-forge
nc_time_axis              1.0.2                    py36_0    conda-forge
ncurses                   5.9                          10    conda-forge
netcdf4                   1.3.1            py36hfd655bd_2    anaconda
numpy                     1.14.0           py36h3dfced4_1
olefile                   0.45.1                   py36_0
openjpeg                  2.3.0                         2    conda-forge
openssl                   1.0.2n                        0    conda-forge
owslib                    0.16.0                     py_0    conda-forge
pcre                      8.39                          0    conda-forge
pillow                    5.0.0            py36h3deb7b8_0
pip                       9.0.1                    py36_1    conda-forge
pixman                    0.34.0                        1    conda-forge
poppler                   0.61.1                        3    conda-forge
poppler-data              0.4.8                         0    conda-forge
proj4                     4.9.3                         5    conda-forge
pycparser                 2.18                     py36_0    conda-forge
pyepsg                    0.3.2                    py36_0    conda-forge
pygrib                    2.0.2                    py36_3    conda-forge
pyhdf                     0.9.0                    py36_2    conda-forge
pyke                      1.1.1                    py36_0    conda-forge
pyopenssl                 17.4.0                   py36_0    conda-forge
pyparsing                 2.2.0                    py36_0    conda-forge
pyproj                    <IP_ADDRESS>                  py36_0    conda-forge
pyqt                      5.6.0                    py36_4    conda-forge
pyshp                     1.2.12                     py_0    conda-forge
pysocks                   1.6.8                    py36_1    conda-forge
python                    3.6.4                         0    conda-forge
python-dateutil           2.6.1                    py36_0    conda-forge
pytz                      2017.3           py36h63b9c63_0
qt                        5.6.2                         7    conda-forge
readline                  7.0                           0    conda-forge
requests                  2.18.4                   py36_1    conda-forge
scipy                     1.0.0            py36hbf646e7_0
setuptools                38.5.1                   py36_0    conda-forge
shapely                   1.6.4                    py36_0    conda-forge
sip                       4.18                     py36_1    conda-forge
six                       1.11.0                   py36_1    conda-forge
sqlite                    3.20.1                        2    conda-forge
tk                        8.6.7                         0    conda-forge
tornado                   4.5.3                    py36_0    conda-forge
udunits2                  2.2.25                        2    conda-forge
urllib3                   1.22                     py36_0    conda-forge
util-linux                2.21                          0
wgrib2                    2.0.5                         1    conda-forge
wheel                     0.30.0                   py36_2    conda-forge
xerces-c                  3.2.0                         0    conda-forge
xorg-libxau               1.0.8                         3    conda-forge
xorg-libxdmcp             1.1.2                         3    conda-forge
xz                        5.2.3                         0    conda-forge
zlib                      1.2.11                        0    conda-forge

Details about  conda and system ( conda info ):

$ conda info
Current conda install:

               platform : linux-64
          conda version : 4.3.30
       conda is private : False
      conda-env version : 4.3.30
    conda-build version : 3.0.27
         python version : 3.6.3.final.0
       requests version : 2.18.4
       root environment : /home/alert/anaconda3  (writable)
    default environment : /home/alert/.conda/envs/radar
       envs directories : /home/alert/anaconda3/envs
                          /home/alert/.conda/envs
          package cache : /home/alert/anaconda3/pkgs
                          /home/alert/.conda/pkgs
           channel URLs : https://repo.continuum.io/pkgs/main/linux-64
                          https://repo.continuum.io/pkgs/main/noarch
                          https://repo.continuum.io/pkgs/free/linux-64
                          https://repo.continuum.io/pkgs/free/noarch
                          https://repo.continuum.io/pkgs/r/linux-64
                          https://repo.continuum.io/pkgs/r/noarch
                          https://repo.continuum.io/pkgs/pro/linux-64
                          https://repo.continuum.io/pkgs/pro/noarch
            config file : None
             netrc file : None
           offline mode : False
             user-agent : conda/4.3.30 requests/2.18.4 CPython/3.6.3 Linux/4.15.0-107-generic debian/stretch/sid glibc/2.23
                UID:GID : 1000:1000

I was able to reproduce the error on with conda version 4.3.0.
If I copy the entire env dir from the machine where it works to a new machine, it works 🤪
diff on the wgrib2 binary confirms they differ, even though thought they should be identical.
The working version was created Feb 13 2018, so sometime between then and now it's become broken 😞

Workaround
After starting with the working env dir, and conda uninstalling backwards, I was able to produce this minimal set of dependencies which do work:
dependencies:
- python=3.6.4=0
- pyhdf=0.9.0
- numpy=1.14.0=py36h3dfced4_1
- pillow=5.0.0=py36h3deb7b8_0
- pytz=2017.3=py36h63b9c63_0
- scipy=1.0.0=py36hbf646e7_0
- wgrib2=2.0.5=1
- jasper=1.900.1=4
- libpng=1.6.34=hb9fc6fc_0
- zlib=1.2.11=0
- g2clib=1.6.0=5
- mysql-connector-c=6.1.6=0
- libnetcdf=<IP_ADDRESS>=10
- libgcc=7.2.0=h69d50b8_2
- libgcc-ng=7.2.0=h7cc24e2_2
- libgfortran=3.0.0=1
- libgfortran-ng=7.2.0=h9f7466a_2

Thanks for the detailed issue!
We have three build numbers for version 2.0.5 and it is odd that only 1 is working since not much changed in them.
Do you know what is preventing you from getting a newer version of wgrib2 in that environment? We also have 2.0.7 and 2.0.8. Either way, we can remove the builds 0 and 2 of 2.0.5. I just want to add a test to the feedstock first to avoid regressions in future updates.

@ocefpaf unfortunately it's some old code which has some monkey patches.
I was hoping to get a set of dependencies first, then start working forwards.
Turns out there are other dependencies for my this old code which are also missing and/or broken in forge, so it looks like I'm going to be starting from scratch anyway.
At least I caught this on the way 🤪

Thanks. I tried a few tests and combination of dependencies but nothing worked :-/
Let me know if you figure this one out.

I engaged the wgrib2 developer on this and the current indication is that only libpng=1.2 is supported.  Digging some more at this yet...

This issue no longer seems reproducible.


Added the first homework of the course.

Practice 1: Java IO

Hi @jmorales47 !
What is the status of your changes?

I haven't edit the code
I'm working with the new assigments
The NumberService is almost done


Github repos transitioning into local ones

The issue here seems to be that we only persist the state sometimes during the processing pipeline, which allows us losing information: If the user quits the app after the initial git sync, but before indexing completes, there's a chance we will not have saved the repo status.
Adding explicit persistence to these synchronization points should fix this.

nice find.


Tests fail under headless Centos7

Hello,
I have downloaded and tried this package under Centos7 (headless server) but the tests failed, any idea ?
[vagrant@localhost go-keyring]$ go test
--- FAIL: TestSet (0.04s)
        keyring_test.go:15: Should not fail, got: The name org.freedesktop.secrets was not provided by any .service files
--- FAIL: TestGet (0.00s)
        keyring_test.go:23: Should not fail, got: The name org.freedesktop.secrets was not provided by any .service files
        keyring_test.go:28: Should not fail, got: The name org.freedesktop.secrets was not provided by any .service files
        keyring_test.go:32: Expected password test-password, got
--- FAIL: TestGetNonExisting (0.00s)
        keyring_test.go:40: Expected error ErrNotFound, got The name org.freedesktop.secrets was not provided by any .service files
--- FAIL: TestDelete (0.00s)
        keyring_test.go:48: Should not fail, got: The name org.freedesktop.secrets was not provided by any .service files
FAIL
exit status 1
FAIL    github.com/zalando/go-keyring   0.043s

Thanks :)

It looks like you don't have gnome-keyring installed. But even if you do it might not work because gnome-keyring will ask you to unlock the keychain by showing a gtk3 dialogbox, which isn't possible on a headless server.
We also have this issue on travis and still haven't found a way to solve it #1.
Test should run fine on a desktop with gnome-keyring installed and configured though.

I do not think that it is related to gnome-keyring
[vagrant@localhost ~]$ sudo yum list | grep gnome-keyring
Repository sysdev-main is listed more than once in the configuration
gnome-keyring.x86_64                   3.14.0-1.el7               @centos
libgnome-keyring.x86_64                3.8.0-3.el7                @centos
gnome-keyring.i686                     3.14.0-1.el7               centos
gnome-keyring-pam.i686                 3.14.0-1.el7               centos
gnome-keyring-pam.x86_64               3.14.0-1.el7               centos
libgnome-keyring.i686                  3.8.0-3.el7                centos
libgnome-keyring-devel.i686            3.8.0-3.el7                centos
libgnome-keyring-devel.x86_64          3.8.0-3.el7                centos
[vagrant@localhost ~]$

My second guess would be that the dbus session isn't started when you are running headless. (It's usually started by your login manager [1]).
You could try to run the tests like this:
$ dbus-launch go test

[1] https://dbus.freedesktop.org/doc/dbus-launch.1.html

Thanks for your help, I have tried also this and the result remains the same.
[vagrant@localhost go-keyring]$ sudo systemctl status dbus
● dbus.service - D-Bus System Message Bus
   Loaded: loaded (/usr/lib/systemd/system/dbus.service; static; vendor preset: disabled)
   Active: active (running) since jeu. 2016-08-11 15:31:56 UTC; 6h ago
 Main PID: 597 (dbus-daemon)
   CGroup: /system.slice/dbus.service
           └─597 /bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation

août 11 20:11:11 localhost.localdomain dbus[597]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
août 11 20:11:11 localhost.localdomain dbus-daemon[597]: dbus[597]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
août 11 20:11:12 localhost.localdomain dbus[597]: [system] Activating via systemd: service name='org.freedesktop.machine1' unit='dbus-org.freedes...service'
août 11 20:11:12 localhost.localdomain dbus-daemon[597]: dbus[597]: [system] Activating via systemd: service name='org.freedesktop.machine1' unit=...ervice'
août 11 20:11:12 localhost.localdomain dbus[597]: [system] Successfully activated service 'org.freedesktop.machine1'
août 11 20:11:12 localhost.localdomain dbus-daemon[597]: dbus[597]: [system] Successfully activated service 'org.freedesktop.machine1'
août 11 21:04:04 localhost.localdomain dbus[597]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.fr...service'
août 11 21:04:04 localhost.localdomain dbus-daemon[597]: dbus[597]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' ...ervice'
août 11 21:04:05 localhost.localdomain dbus[597]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
août 11 21:04:05 localhost.localdomain dbus-daemon[597]: dbus[597]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Hint: Some lines were ellipsized, use -l to show in full.
[vagrant@localhost go-keyring]$ dbus-launch go test
--- FAIL: TestSet (0.00s)
	keyring_test.go:15: Should not fail, got: The name org.freedesktop.secrets was not provided by any .service files
--- FAIL: TestGet (0.00s)
	keyring_test.go:23: Should not fail, got: The name org.freedesktop.secrets was not provided by any .service files
	keyring_test.go:28: Should not fail, got: The name org.freedesktop.secrets was not provided by any .service files
	keyring_test.go:32: Expected password test-password, got
--- FAIL: TestGetNonExisting (0.00s)
	keyring_test.go:40: Expected error ErrNotFound, got The name org.freedesktop.secrets was not provided by any .service files
--- FAIL: TestDelete (0.00s)
	keyring_test.go:48: Should not fail, got: The name org.freedesktop.secrets was not provided by any .service files
FAIL
exit status 1
FAIL	github.com/zalando/go-keyring	0.006s

It would be great if we could make this library working with this case. Python manages its keyring lib with a dedicated dbus package.

Python DBUS : https://pypi.python.org/pypi/dbus-python/1.2.4
Python Keyring (works on headless Linux) : https://pypi.python.org/pypi/keyring

Your log shows the system bus being active. dbus-launch should start a session bus but maybe it doesn't do it here since it still doesn't find the service.
Does the python keyring lib work correctly on the same setup with the secret service backend? IIRC the python keyring library will fallback to a file based storage if the secret service (dbus) interface isn't available, so make sure that isn't happening.

Hi @ahmed-bacha, do you need anything else on this topic? I'll close it for now, but ping back if you still have questions. cc @mikkeloscar


VOTE: Do you or your clients use IE10?

Currently we have agreed to drop IE8 and IE9 support for SilverStripe 4. However, we had not yet decided whether IE10 or IE11 would be the minimum version.
Please note that when talking about browser support we refer only to CMS usage and not to the browser support of websites built with SilverStripe.
We will definitely support IE11 in SilverStripe as it is not possible to run newer versions of IE on Windows 7, and this is a common configuration for corporate IT environments.
IE11 is supported in Windows 7 service pack 1, and as best we can tell IE10 will auto-upgrade to IE11, so it is likely that IE10 use is limited, even in corporate environments.
We would like to get feedback on whether or not the SilverStripe community currently relies on IE10 support via votes on this card.
Please vote 👍 to one of the comments below to cast your vote.

VOTE: Neither I nor my clients currently use Internet Explorer 10. Dropping support for Internet Explorer 10 in SilverStripe 4 would not impact me.

VOTE: I or my clients currently use Internet Explorer 10, but we can upgrade. Dropping support for Internet Explorer 10 in SilverStripe 4 would be acceptable.

VOTE: I or my clients currently use Internet Explorer 10, and it is infeasible for us to stop using it. If SilverStripe 4 does not support IE10 then we won't be able to use it.

Some more references for this:

Capability differences: http://caniuse.com/#compare=ie+10,ie+11
"On Windows 7, 8.1, and 10, only Internet Explorer 11 will receive security updates for the remainder of those Windows versions' support lifecycles. " - https://en.wikipedia.org/wiki/Internet_Explorer_11
"On January 12, 2016, support ended for IE10 on Windows operating systems capable of running Internet Explorer 11, due to new support policies dictating that only the newest version of IE available for a supported version of Windows will be supported. IE10 will only be supported on Windows Server 2012[12][13] and Windows Embedded 8 Standard.[14]" -
https://en.wikipedia.org/wiki/Internet_Explorer_10

@xini do you have any information about why your clients are unable to upgrade to IE11?

I'd suggest taking the stance of officially supporting IE11+ and then make a "best effort" to support IE10 but not to do so at the sacrifice of features that would otherwise have to be reduced/removed in order to accomplish it.
For example: Don't spend more than maybe 10-30min to resolve a bug in IE10 (such as a quirk in flex box) and certainly don't avoid using native functionality in favor of a polyfill (or even include a polyfill) for IE10 when it's supported natively in IE11 (e.g. WebGL 3D graphics or something).
That being said: Chances are a majority of the functionality would probably be unaffected; they would just likely be left behind on newer features (if they don't break the CMS/page). Also, as an alternative, you could just remain on v3 until IE10 is upgraded.

@patricknelson

the latest version jQuery UI is IE11+. so we either need to not upgrade, or not support IE10
if we don't test IE10 then we'll probably break things and not realise. testing against IE10 is one of the bigger costs of supporting it

Best case scenario will be that we support IE10 for the basics and are more tolerant of minor visual degradations. But, depending on how this survey goes, we may just drop support for it. It's a security hazard to use IE10.

@sminnee one of my large clients is apparently stuck in the past by internal policies. The policies come from their headquaters in the US. Not much we can do from here. But I guess they will eventually come around. By the time SS4 is stabe and all modules are updated so that everything is actually ready to be used, I guess they might be ready to make the switch... might just take a while for them to be able to upgrade. no worries.

Cool, thanks for the info @xini

We have some IE10 users but we usually get them to install Chrome. So IE10 support isn't big for us, would rather see the development time better spent.

Some clients might use IE10 but they would have no problem installing another browser to use the CMS. As long as they get a warning that their current browser is not supported, dropping IE10 support would be totally acceptable for me.

The main area I foresee potential issues with removing IE10 support would be for Government clients. Not sure about in NZ, but here in AU, the upgrade time frame for departmental IT can be excruciatingly slow. For example, I have one Government client that has only just migrated to Windows 7 within the last 12 months, let alone Windows 8, 8.1 or 10. I think they were hitting the CMS with either IE8 or 9, blecch.  ☹
But, these are exceptional cases; personally I'm all for removing anything but the latest IE support! I urge caution though with dinosaur clients such as these, however.

Windows 7 and IE11 is a common government configuration here. Of 120 sites we checked only 1 had regular use of IE10.
It's worth noting that IT teams running IE10 are compromising their organisation's security.

OK on the basis that a significant minority would need some upgrading form IE10 I think the following would be okay:

Remove IE10 from the officially supported browser list
Show a clear warning if older versions of IE10 are used to access the CMS but don't lock people out
Accept IE10 bugfix PRs that don't substantially increase the code complexity
Allow the use of libraries that support IE11+

I just checked with the client and they're on W7/IE11 now, sweet! 😄 Your suggestions above sound pretty good, @sminnee. 👍

I've added this to the beta1 milestone, since we should be clearly communicating browser support at this point.

I have added #6719 to track the piece of dev work still necessary in response to this card, and closing this off.

I've documented this decision in core now: https://github.com/silverstripe/silverstripe-framework/pull/6764


Would I be able to use golang to produce the wasm file?

Summary
Is it possible to use this project to load a wasm file generated from golang?
Additional details
I tried but got
Message:
Use of undefined constant WASM_TYPE_F64 - assumed 'WASM_TYPE_F64' (this will throw an Error in a future version of PHP)
Location:
/var/www/leonardo/vendor/php-wasm/php-wasm/lib/Prelude.php on line 10

It is possible to load a Wasm module representing a Go program, yes.
What code generates your error?

I ran composer to import "php-wasm/php-wasm": "^0.5.0"
when I try to run
$instance = new Wasm\Instance(__DIR__ . '/wasm.wasm');
    var_dump(
        $instance->multiply(5, 37)
    );

I get the error described above.
The go code is the following
package main

func main(){

}

func multiply(x,y int) int {
	return x * y;
}

I used tinygo to build maybe that is the issue?
/usr/local/tinygo build -o wasm.wasm -target wasm ./main.go

Did you include the vendor/autoload.php?

My mistake, didn't compile extension properly


ansi-to-html has a lot of dependencies we don't need

Installing jupyter-js-plugins shows that ansi-to-html depends on karg for a command-line interface, which we definitely don't need. karg pulls in about 30 dependencies, many of which we don't need.
Webpack doesn't include karg, so that's good. If we stop using webpack and start bundling karg, it massively increases our npm dependencies. This is not a problem now, but I'm documenting it here so it's easier to find in the future.

Closing since webpack doesn't bundle karg.


Aura: Adds some compatibility mode to support old chains

In https://github.com/paritytech/substrate/pull/9132 we changed the way how we get the authorities from the runtime. Before this mentioned pr we would call initialize_block before calling the authorities runtime function. The problem with this was that when you have a block X that would switch the authority set, it would already be signed by an authority of the new set. This was wrong, as a block should only be signed by the current authority set. As this change is a hard fork, this pr brings back the possibility for users that have a chain running with this old logic to upgrade.
They will need to use:
CompatibilityMode::UseInitializeBlock { until: some_block_in_the_future }

Using this compatibility mode will make the node behave like the old nodes, aka calling initialize_block before doing the actual runtime call to authorities. Then when the given until block is being build/imported the node switches to the new behaviour of not calling initialize_block before. This is a hard fork, so the until block should be chosen wisely as a point where all nodes in the network have upgraded.
Closes: https://github.com/paritytech/substrate/issues/10103
cumulus companion: https://github.com/paritytech/cumulus/pull/1803

bot merge


prune error about non-existenent resources

Bug description
prune spits out a bunch of errors for deprecated resources
Expected behavior
Istio should not be using beta1 deployment nor app resources:
2019-11-24T22:13:57.359834Z     info    resource updated: admissionregistration.k8s.io/v1beta1, Kind=MutatingWebhookConfiguration
2019-11-24T22:13:59.151631Z     info    begin pruning
2019-11-24T22:13:59.942026Z     warn    retrieving resources to prune type apps/v1beta1, Kind=Deployment: no matches for kind "Deployment" in version "apps/v1beta1" not found
2019-11-24T22:14:02.148191Z     warn    retrieving resources to prune type apps/v1beta1, Kind=StatefulSet: no matches for kind "StatefulSet" in version "apps/v1beta1" not found
2019-11-24T22:14:04.349192Z     warn    retrieving resources to prune type extensions/v1beta1, Kind=DaemonSet: no matches for kind "DaemonSet" in version "extensions/v1beta1" not found
2019-11-24T22:14:06.542572Z     warn    retrieving resources to prune type extensions/v1beta1, Kind=Deployment: no matches for kind "Deployment" in version "extensions/v1beta1" not found
2019-11-24T22:14:08.743831Z     warn    retrieving resources to prune type certmanager.k8s.io/v1beta1, Kind=Certificate: no matches for kind "Certificate" in version "certmanager.k8s.io/v1beta1" not found
2019-11-24T22:14:10.941968Z     warn    retrieving resources to prune type certmanager.k8s.io/v1beta1, Kind=Challenge: no matches for kind "Challenge" in version "certmanager.k8s.io/v1beta1" not found
2019-11-24T22:14:13.142050Z     warn    retrieving resources to prune type certmanager.k8s.io/v1beta1, Kind=Issuer: no matches for kind "Issuer" in version "certmanager.k8s.io/v1beta1" not found
2019-11-24T22:14:15.341872Z     warn    retrieving resources to prune type certmanager.k8s.io/v1beta1, Kind=Order: no matches for kind "Order" in version "certmanager.k8s.io/v1beta1" not found
2019-11-24T22:14:17.541952Z     warn    retrieving resources to prune type rbac.istio.io/v1alpha1, Kind=AuthorizationPolicy: no matches for kind "AuthorizationPolicy" in version "rbac.istio.io/v1alpha1" not found
2019-11-24T22:14:19.742552Z     warn    retrieving resources to prune type certmanager.k8s.io/v1beta1, Kind=ClusterIssuer: no matches for kind "ClusterIssuer" in version "certmanager.k8s.io/v1beta1" not found
2019-11-24T22:14:20.120724Z     info    end pruning
2019-11-24T22:14:20.143136Z     info    end reconciling resources

Steps to reproduce the bug
IKS on 1.16 - deploy operator and viola the logs wlil reproduce for the operator.
Version (include the output of istioctl version --remote and kubectl version and helm version if you used Helm)
istio 1.1.4 IKS 1.16.3.
How was Istio installed?
ICP standalone operator
Environment where bug was observed (cloud vendor, OS, etc)
IBM Cloud

I'm speculating this is cert manager not being deployable resulting in a prune action because the controller belives these cert manager resources have been deployed.

I think there is just a list of stuff it tries to prune, and if they don't exist (like if cert manager is not installed) then you get this error

There are a few error conditions with prune I can think of off the top of my head:

The operator has things to prune, however, the prune fails in progress and should be completed on the next reconciliation.
The operator does not have this resource as a deployed resource prior, yet there are resources found indicative of duplicate resources deployed.
The operator has things to prune, but the prune fails to get started (which is similar to 1, but a subset).

In each of these cases, the operator should be printing different info level messages about why the prune is taking place.  At present, an error prune shows up in a grep of the logs as an error - which is clearly not desirable :)
Cheers
-steve
That second case

@howardjohn - to be more direct, a spew of 8 messages at WARN level that appear as if something went wrong, while the actual results are indeterminate is not an acceptable log message nor solution.  Even now, it is not possible to detect if this was a prune error on the human side, a prune error in our implementation, or a prune error in the infrastructure.
Cheers
-steve
Cheers
-steve

Yeah something is definitely wrong, just explaining the root cause. Those resources do not exist on your cluster, the k8s ones are because those were removed in k8s 1.16

@ostromart I think this is fixed, can yo confirm?

Hi, is there a solution/workaround for this error? I hit the same problem in Istioctl v1.5.2.
It appears there are .yaml file(s) somewhere that refers "apiVersion: extensions/v1beta1".
istioctl manifest apply --set profile=demo

Applying manifest for component Base...
✔ Finished applying manifest for component Base.
Applying manifest for component Pilot...
✔ Finished applying manifest for component Pilot.
Applying manifest for component EgressGateways...
Applying manifest for component IngressGateways...
Applying manifest for component AddonComponents...
2020-04-30T22:32:51.915154Z	error	installer	error running kubectl: exit status 1
2020-04-30T22:32:59.390184Z	error	installer	error running kubectl: exit status 1
✘ Finished applying manifest for component EgressGateways.
2020-04-30T22:33:00.453259Z	error	installer	error running kubectl: exit status 1
✘ Finished applying manifest for component IngressGateways.
2020-04-30T22:33:03.435010Z	error	installer	error running kubectl: exit status 1
✘ Finished applying manifest for component AddonComponents.

Component EgressGateways - manifest apply returned the following errors:
Error: error running kubectl: exit status 1
Error detail:
error: error retrieving RESTMappings to prune: invalid resource extensions/v1beta1, Kind=DaemonSet, Namespaced=true: no matches for kind "DaemonSet" in version "extensions/v1beta1" (repeated 1 times)
serviceaccount/istio-egressgateway-service-account created
deployment.apps/istio-egressgateway created
poddisruptionbudget.policy/istio-egressgateway created
service/istio-egressgateway created
Component IngressGateways - manifest apply returned the following errors:
Error: error running kubectl: exit status 1
Error detail:
error: error retrieving RESTMappings to prune: invalid resource extensions/v1beta1, Kind=DaemonSet, Namespaced=true: no matches for kind "DaemonSet" in version "extensions/v1beta1" (repeated 1 times)
serviceaccount/istio-ingressgateway-service-account created
gateway.networking.istio.io/istio-ingressgateway created
sidecar.networking.istio.io/default created
deployment.apps/istio-ingressgateway created
poddisruptionbudget.policy/ingressgateway created
role.rbac.authorization.k8s.io/istio-ingressgateway-sds created
rolebinding.rbac.authorization.k8s.io/istio-ingressgateway-sds created
service/istio-ingressgateway created
Component AddonComponents - manifest apply returned the following errors:
Error: error running kubectl: exit status 1
Error detail:
error: error retrieving RESTMappings to prune: invalid resource extensions/v1beta1, Kind=DaemonSet, Namespaced=true: no matches for kind "DaemonSet" in version "extensions/v1beta1" (repeated 1 times)
error: error retrieving RESTMappings to prune: invalid resource extensions/v1beta1, Kind=DaemonSet, Namespaced=true: no matches for kind "DaemonSet" in version "extensions/v1beta1" (repeated 1 times)

This has been fixed in master/1.6 now


feat(cli): add version command

Signed-off-by: Aldo Lacuku<EMAIL_ADDRESS>
What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind bug

/kind cleanup

/kind design

/kind documentation

/kind failing-test

/kind feature

/kind flaky-test

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area library

/area cli

/area tests

/area examples

What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

The go.mod and/or go.sum files appear not to be correctly tidied.
Please, rerun go mod tidy to fix the issues.


Chyt 2.16.0 return timestamp error

chyt 2.16.0
Select query that reads timestamps from dynamic ordered table
Error is "timestamp64" is not valid type_v3 simple type
UI shows query as completed, but Result has that error

Hi @Arustinal.
It's a backward compatibility issue.
CHYT 2.16.0 supports a bunch of new data types. Now it saves a DateTime64 ClickHouse value as a timestampt64 YT value. Unfortunately, timestamp64 has been introduced in a 24.1 YTsaurus release, so you get this not a valid type error because your YTsaurus version is older.
As a workaround, you can either update your YTsaurus version (the public announcement, change log and official docker images will be available in the nearest future), or downgrade a CHYT version to 2.14/2.15.
Anyway, I will add the note that CHYT 2.16 requires at least YTsaurus 24.1 to the release notes for now.
If this solution is not suitable for you and you need to use a new chyt version with older YTsaurus clusters - let us know, we will think about other workarounds here.

I am ok with downgrade chyt to 2.14, as 2.15 doesnt have published package. Waiting for 24.1 release.


Update Config “general”

Automatically generated by Netlify CMS

👷 Deploy Preview for sharp-meitner-f7c651 processing.
🔨 Explore the source changes: 19a9842dd6b2258bf77d2322ebd3b833b2c75313
🔍 Inspect the deploy log: https://app.netlify.com/sites/sharp-meitner-f7c651/deploys/61143199f8971400075a4633


Sprite filters, beta tab

added

HoxNorf's sprite filters
Beta Tab

Removed

Read only flag on flags text box

Approved merge


Documentation references .NET 6 "preview"

The documentation at https://docs.microsoft.com/en-us/dotnet/csharp/whats-new/tutorials/top-level-statements still references .NET 6 "preview", but .NET 6 has now been released 🙂

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: af2939b6-ad9e-4116-c805-8f19ed994c31
Version Independent ID: ad23d124-a491-2b4f-3c51-0ed5d38d7eba
Content: Top-level statements - C# tutorial
Content Source: docs/csharp/whats-new/tutorials/top-level-statements.md
Product: dotnet-csharp
Technology: csharp-whats-new
GitHub Login: @BillWagner
Microsoft Alias: wiwagn

@BillWagner Thanks 🙂


Is it working on the lastest patch?

I can't make it work here since the last updade :(

Well now it should! https://github.com/Soreepeong/XivAlexander/releases
Make sure you change the corresponding entry in xivAlexander.dll.json if you use Steam version, Chinese client, or have installed the game at an another location


Simple email address format validation

The email RFCs are notoriously flexible, but this will at least catch some basic mistakes, e.g. trying to paste an HTTP URL in the field (at least, one without auth).

:+1:


Use component with USB-RS485 interface

Hi,
I would interested in trying out this component.
Currently I use a USB-RS485 stick with the Homeassistant modbus integration (https://github.com/StefanUG/nilan-hass-modbus/tree/master)
Would it be difficult to make it able to use the serial connection?
Thanks in advance!

At the moment the integration does not support usb adaptors, but it is possible to add. This is planned to be implemented in the future.

Just released initial version with serial support.

@magifi can you also test if this works for you?

@Magifi can you also test if this works for you?

I already ordered RS485->ethernet device. I think I will try to run Nilan in HA and in openhab at the same time as long as I get my HA in order and stable. Perhaps I could use them both in modbus. Other one with RS485->ethernet adapter and other one with RS485 -> usb adapter.
But I will try my RS485-USB dongle as well with HA and then report the results.

Waveshare USB to RS485 (https://www.waveshare.com/usb-to-rs485.htm) confirmed working.


Small code improvement in tests

Extracted helper

This change is

Current coverage is 81% (diff: 100%)

Merging #1790 into master will decrease coverage by <1%

@@             master      #1790   diff @@
==========================================
  Files           274        274
  Lines         18256      18256
  Methods        2834       2834
  Messages          0          0
  Branches       2091       2091
==========================================
- Hits          14876      14866    -10
- Misses         2898       2908    +10
  Partials        482        482

Powered by Codecov. Last update f5b08bd...5c37ff5


[front-end] crashes without visible user error when Metamask is locked

Uncaught (in promise) Error: gRPC failed (2): invalid owner specified: neither ASCII nor Raw form of address given
    at Object.onEnd (app.e16483494b1250262f36.js:16)
    at Array.<anonymous> (app.e16483494b1250262f36.js:16)
    at t (app.e16483494b1250262f36.js:1)
    at app.e16483494b1250262f36.js:1

No visible error shows-up for the user, and unlocking account doesn't resolve the issue - the website needs to be refreshed to work again.

This can be detected via

const c: Client;
const user = await c.currentUser();
if (user.ascii == undefined) {
    console.log("Unlock your metamask!");
}

I can add an async method to the client that will wait for an account to be unlocked, if necessary.

Verified, works now.


SourceKit: hoist decision for building InProc

The decision to whether build InProc or as an XPC service is needed for the
test tools as well.  Rather than recompute it for the tests as well, hoist it to
the top level for the SourceKit project.  This repairs the build of the
SourceKit tests on non-Darwin hosts.

Replace this paragraph with a description of your changes and rationale. Provide links to external references/discussions if appropriate.

Resolves SR-NNNN.

@swift-ci please test and merge


Scss require issue in view

I'm submitting a feature request

Aurelia Skeleton Version
skeleton-esnext-webpack 1.0.2

Framework Version:
aurelia-framework 1.0.6

Please tell us about your environment:

Operating System:
OSX 10.11.6

Node Version:
6.7.0

NPM Version:
3.10.8

JSPM OR Webpack AND Version
webpack 2.1.0-beta.22

Browser:
all

Language:
ESNext

Current behavior:
We have 2 versions of style import in view: one for SASS and one for SCSS (@easy-webpack/config-sass was added in webpack configuration)
<require from="./style1.sass"></require>
<require from="./style1.scss"></require>
webpack config:
require('@easy-webpack/config-css')         ({ filename: 'styles.css', allChunks: true, sourceMap: false }),
 require('@easy-webpack/config-sass')         ({ filename: 'styles.css', allChunks: true, sourceMap: false }),
SASS import works successfully but for SCSS it doesn't work at all:
Unhandled rejection Error: Cannot find module './style1.scss.html'.     at webpackContextResolve (http://localhost:9000/app.bundle.js:521:9)     at webpackContext (http://localhost:9000/app.bundle.js:516:29)     at http://localhost:9000/aurelia-bootstrap.bundle.js:15802:48
The reason is "*.scss.html" in file extension.
Expected/desired behavior:

Please advise why aurelia add unnecessary extension "html" to the module path.
What do we need to do for valid SCSS import?
Thanks in advance.

Both imports (SASS and SCSS) doesn't work for now, right? what configuration is needed?

There is a work around for this as you can switch to normal webpack instead of easy webpack and import sass inside javascrpit.
Detail at #626

@bigopon You can import SASS inside JavaScript using Easy Webpack, no problem. Just use easy-webpack/config-sass, or add the loader yourself.

@niieani  I realized my stupidity after hitting send button, deleted that comment.


Fix Go version in go.mod

Patches v14.0 since the go.mod file was still set at v13

This is mostly around as an FYI - the release has been set for 14.0.1.


helper classes to facilitate running code tests on FB checks in our test-suite

The benefit of this new approach is that the CheckRunner machinery
takes care of computing the conditions for a check, so that there's
less boilerplate code and thus less opportunity for a developer
to commit a mistake when crafting the code tests.
Followup to #2363 after 0.7.0 release introduced new non-numerical check IDs.

@felipesanches whats blocking this from merge? If nothing, what's the ETA? :)

This is experimental and actually does not completely work yet. I discussed this with Lasse some weeks ago and we had some ideas, but I have not put more effort in this. I intend to get back to it, since it would be really nice. Not top priority though.

since this is to far from being merge-ready I will close it and allocate more time to it later


up_squared: samples/portability/cmsis_rtos_v1/philosophers/ failed.

To Reproduce
Steps to reproduce the behavior:

west build -b up_squared -p auto samples/portability/cmsis_rtos_v1/philosophers/
west flash ~/up_squared.sh
see error

Logs and console output
*** Booting Zephyr OS build v2.4.0-rc2  ***
Running test suite test_cmsis_v2_apis
START - test_kernel_apis
PASS - test_kernel_apis
START - test_delay
PASS - test_delay
START - test_thread_apis
Assertion failed at WEST_TOPDIR/zephyr/tests/portability/cmsis_rtos_v2/src/thread_apis.c:131: thread_apis_common: (osThreadGetCount() not equal to 2)
Incorrect number of cmsis rtos v2 threads
FAIL - test_thread_apis
START - test_thread_apis_dynamic
Assertion failed at WEST_TOPDIR/zephyr/tests/portability/cmsis_rtos_v2/src/thread_apis.c:82: thread2: (num_threads not equal to 2)
PASS - test_thread_apis_dynamic
Incorrect number of cmsis rtos v2 threads
START - test_thread_prio^M
PASS - test_thread_prio^
Environment (please complete the following information):

OS: Fedora31
Toolchain: zephyr-sdk-0.11.4
Commit ID: 122bc38fad

This does not seem to be the correct log. Could you update?

This does not seem to be the correct log. Could you update?

sorry, pasted error log. I have updated the log.


Routinator resource usage

Based on this tweet I was asked to open a github issue about my routinator resource usage. This isn't an operational issue for me, the server can handle it, and I don't know whether there is an actual bug, but since I was asked to open an issue, here it is.
Here you can see when I started running routinator:

After running for about 38 hours, the routinator server is at 1h18m of CPU time, so that seems to match those graphs. It's running on a single core virtual machine.
I installed it following the quick start exactly, I am running routinator server with those parameters. There are three BIRD instances using it for RPKI validation, IPv6 only.
Here are my full logs from the last start, nothing in there seems unusual.

When you zoom in a bit, do you see short bursts of CPU usage? Typically, things should be a bit hectic for a minute or two and then calm for ten minutes. Given that each validation run includes validating signatures on around 100,000 objects, quite a bit of CPU usage is to be expected.
Similarly, these 100,000 objects – each is its own file –, are read every 10 minutes explaining the disk usage. I’d expect them to be mostly cached if the machine has enough memory, but if it is a VM on a busy host, ten minutes may be too long for them to stay in the cache.

Here's the closest zoom I can get, last 24 hours:

I have an operational issue with the RAM usage of the last release (0.9.0), it jumped from some megs to nearly 1G. It’s OOM-killed by the kernel every now and them. As a quick fix, I’m back on 0.8.3.
The upgrade has been done at the end of week 22.

Thanks for the report and the graphs! While we expected higher RAM usage due to the new database in 0.9, it certainly is too much now and consumption also seems to be growing over time. We are investigating both right now and hopefully will have a fix soon.

Please note that RAM usage in 0.10.0 is now significantly lower than in 0.9.0:
$ sudo systemctl status routinator
● routinator.service - Routinator 3000
   Loaded: loaded (/lib/systemd/system/routinator.service; enabled; vendor preset: disabled)
   Active: active (running) since Mon 2021-08-23 12:22:18 UTC; 1 weeks 3 days ago
     Docs: man:routinator(1)
 Main PID: 7389 (routinator)
    Tasks: 5 (limit: 2330)
   Memory: 1.4G
   CGroup: /system.slice/routinator.service
           └─7389 /usr/bin/routinator --config=/etc/routinator/routinator.conf --syslog server

$ cat /proc/7389/status | grep 'VmHWM\|VmRSS'
VmHWM:	  428368 kB
VmRSS:	  369752 kB

Yeah, I have upgraded last week and I confirm. Thanks a lot for the work done. It even seems to be lower than 0.8.0 ;)

It is a bit odd that this happens on every third validation run (assuming you’ve kept the refresh time at ten minutes), but otherwise not entirely unexpected if you have a lot of cores. Routinator uses a thread pool during validation that is by default configured to be the number of cores. Each thread processes one repository including updating the repository. If there is nothing to update and you have most of the files buffered (if you have enough memory), you can end up with all threads basically just validating signatures and using a lot of CPU. This would just be a short spike since most repositories are quite small and eventually there will be only two or three working threads left.
So, while seeing this every third run is certainly strange, I think this is normal. You can, however, limit the amount of threads (and thus cores used) via the validation-threads configuration option.


pkg/utils: minor clean up

Adding some necessary empty space for readability and for eye-health...
I also fix a minor error checking issue. I can separate them to two commits if you want.

LGTM


correct heuristic for -(N)

interpret "-(N)" as a negative term searching a positive number.

Thank you for checking.


Error in installation of eshell-syntax-highlighting

What's wrong
Can't install eshell-sysntax-highlighting
Directions to reproduce

I am trying to install eshell-syntax-highlighting using the following:
(use-package eshell-syntax-highlighting
  :after esh-mode
  :config
  (eshell-syntax-highlighting-global-mode +1))

But I am getting the following error:
straight--convert-recipe: Could not find package eshell-syntax-highlighting in recipe repositories: (org-elpa melpa gnu-elpa-mirror emacsmirror-mirror)

But the package is in MELPA: https://melpa.org/#/eshell-syntax-highlighting
What I am doing wrong?
Version information

Emacs version: GNU Emacs 27.1.50 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.20, cairo version 1.16.0) of 2020-09-05
Operating system: PopOS 20.10

Perhaps your recipe repository for MELPA needs to be updated?
First (setq debug-on-error t).
Then try M-x straight-pull-package melpa before re-evaluating the use-package declaration for eshell-syntax-highlighting. If you get an error or any messages that refer you to the *straight-process-buffer*, please copy the entire debug stacktrace and/or process buffer here.

Please also try evaluating the following test case in the *scratch* buffer.
It will build straight and attempt to install the minimal set of packages to reproduce your problem in a clean environment.
When it it does, another buffer will pop up which you can copy here.
For me the following test is passing:

Test Case
(straight-bug-report
  :pre-bootstrap
  (setq straight-repository-branch "develop")
  (setq straight-use-package-by-default t)
  :post-bootstrap
  (straight-use-package 'use-package)
  (use-package eshell-syntax-highlighting))

Test run at: 2020-12-03 00:19:23
system-type: gnu/linux
straight-version: prerelease (HEAD -> develop, origin/develop) 3277e1c 2020-11-24
emacs-version: GNU Emacs 28.0.50 (build 1, x86_64-pc-linux-gnu, X toolkit, cairo version 1.17.3, Xaw3d scroll bars) of 2020-11-24

Output
Bootstrapping straight.el...
Bootstrapping straight.el...done
Rebuilding all packages due to build cache schema change
Looking for gnu-elpa-mirror recipe → Cloning melpa...
Looking for gnu-elpa-mirror recipe → Cloning melpa...done
Looking for emacsmirror-mirror recipe → Cloning gnu-elpa-mirror...
Looking for emacsmirror-mirror recipe → Cloning gnu-elpa-mirror...done
Looking for emacsmirror-mirror recipe → Cloning el-get...
Looking for emacsmirror-mirror recipe → Cloning el-get...done
Looking for straight recipe → Cloning emacsmirror-mirror...
Looking for straight recipe → Cloning emacsmirror-mirror...done
Building straight...
Building straight...done

Test run with version: prerelease (HEAD -> develop, origin/develop) 3277e1c 2020-11-24
Cloning use-package...
Cloning use-package...done
Building use-package...
Building use-package → Building bind-key...
Building use-package → Building bind-key...done
Building use-package...
Building use-package...done
Cloning eshell-syntax-highlighting...
Cloning eshell-syntax-highlighting...done
Building eshell-syntax-highlighting...
Building eshell-syntax-highlighting...done

That fixed. Thank you. I was trying to run straight-pull-package RET eshell-syntax-highlighting RET without success, but now I can see that I need to use the repo name, not the package name.
My mistake

straight-pull-package should work for eshell-syntax-highlighting once the recipe is found, but if new packages are added to any recipe repositories (e.g. MELPA), you'll have to pull that recipe repository first. Glad you got it worked out. Thank you.


Comments from Brian Eastwood

[ ] Depict known Toxicology
[ ] Depict known confirmatory experiment coming out of a network model
[ ] Depict known safety implications

Also

[ ] Relevance to known biomarkers


Mock typing can be improved

Mockable class:
export class Widget {
    public static readonly doWork = async () => ...
}

Actual result:
The object returned by mock(import('./widget')) contains no IntelliSense properties in the typing.
Expected result:
Compare with mocked helper from ts-jest/utils: the object contains the doWork property which is typed correctly (both as a function and as a mock).
Notes:
As a workaround, I use mock(import(... independently (not assigning the result anywhere), and then, when I need to setup mocks, I separately use the mocked helper from ts-jest/utils, applied to the result of a "normal" import (to get the proper mock typing).
This is of course not too DRY...
Should we re-use the typings of the mocked helper from ts-jest/utils? It seems to be comprehensive and to work correctly in all cases.

@anilanar here are the relevant typings from ts-jest: https://github.com/kulshekhar/ts-jest/blob/master/src/utils/testing.ts
They never failed me, maybe it's a good idea to pull them? I can do a PR if you wish.

I'm actually planning to add a test infra. for mocked types so that we can safely pick the most appropriate type for it.


[5.7] Extract fixtures for Validation tests.

Extract fixtures for Validation tests.

I'm really fine with having these in the same class.


fprintd: set sysconfdir

Motivation for this change
Fixes https://github.com/NixOS/nixpkgs/issues/62083. The Arch config does this too.
I'm slightly unsure if this is the right thing to do: the alternative would be to set it to /etc and copy the config file over in the module. That would mean that other services could potentially modify it, I'm not sure if that's desirable.
cc @abbradar
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Assured whether relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

We could still change it to point to /etc later, but for now this fixes above issue


Selects and Autocompletes get "stuck" in deployed Blazor Server app (Azure)

Bug type
Component
Component name
MudAutocomplete, MudSelect
What happened?
I have a fairly simple web app with some user inputs - a couple Selects and an Autocomplete. My Users are reporting a consistent bug where either the autocomplete or the Selects won't close when you make a selection - they stay open indefinitely and block the rest of the UI, and don't close when you click outside of them.
Does this sound like a common issue to anyone who might know what the problem could be? I have added try/catch blocks to all of the methods bound to the ValueChanged and searchFunc properties of the inputs.
Here is the page that exhibits the unwanted behavior: https://eldenring.negator13.com/calculator
My app is Blazor Server (.NET 6) and is deployed as a Windows App Service in Azure.
Expected behavior
Whenever a user makes an input choice, I expect the input to close and allow interaction with other components on the page.
I am explicitly catching all exceptions in my ValueChanged and searchFunc implementations for these components, so I wouldn't expect any unhandled exceptions to be causing the issue.
Reproduction link
https://eldenring.negator13.com/calculator
Reproduction steps
This is not 100% reproducible by any specific course of action, but is typically happening on my production site after a few changes of selection.
Change the selections of the "Weapon Category", "Upgrade" or "Affinity" selects a few times, and/or type in some values into the "Weapon" autocomplete and choose some inputs. Generally one of the components will "freeze" after not too many tries, and not allow the user to click out of it.
Relevant log output
No response
Version (bug)
6.0.7
Version (working)
No response
What browsers are you seeing the problem on?
Firefox, Chrome
On what operating system are you experiencing the issue?
Windows
Pull Request

[ ] I would like to do a Pull Request

Code of Conduct

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

This bug shows only on mobile - touch devices? You should upgrade your application with the last release

This bug shows only on mobile - touch devices? You should upgrade your application with the last release

It happens for me (very often) on desktop (Chrome, Windows)

I have updated to v6.0.9 but the issue is still persisting.

Your website works in my phone

Here is a screenshot that I just took.
Repro steps:
Typed in "long" and selected Longsword, then changed the "Upgrade" select a few times. Screenshot shows the select being stuck - I clicked on and off the select before taking this picture and it does not close.

I see these like problems on touch but see first time on desktop

Yeah it is not consistently reproducible with any exact sequence of steps, and I cannot reproduce it locally either, so it has been difficult to understand what the problem is.

We have exactly the same problem with our new application (this is the first time we use MudBlazor). On my machine this problem never occures, but on one of my colleague's almost every two selections fails because of this. Interesting thing, if he uses the touchpad on his laptop, it never happenes.

We know about an issue that happens only on Server Side and only on mobile-touch. And prepared some fix that released with the last release. (only for select)
Also there is another fix for autocomplete on road and waiting for merge.
Any other information about this issue will be very useful. As you said its very strange bug

Just chiming in that this happens for us as well with autocompletes. Project is server side, but happens consistently (100%) on touch devices, both emulators and devices.
We're using a MudDrawer on the same page, which includes a MudOverlay. Could it be an event propagation problem with multiple MudOverlays?

To make it occur more consistently in the demo above, open the autocomplete, then click outside of it somewhere on the page. This makes the autocomplete blur (the little visual shadow disappears) and the property IsOpen is false, but the list stays open.

Just chiming in that this happens for us as well with autocompletes. Project is server side, but happens consistently (100%) on touch devices, both emulators and devices.

Yes, autocompletes has problem and i hope they will fixed with #4294.
@negator13 your select's work for me (both mobile and desktop). Could you check it again? If it still has problems, then you can prepare a try.mudblazor snippet that has your select's razor code and valuechanged - bindvalue methods

In a clean, new .NET 6 Blazor Server project, with only one page that only has one autocomplete in it, everything worked perfect until I configured the Azure SignalR Service. After that autocomplete does not close.
When I remove the Azure SignalR section in appsettings.json it works perfectly again.
I know it sounds crazy but it is true...

Same problem here. Happens consistently on several apps. Blazor 6.0.9 (server-side), Chrome 99.0.4844.82.

@negator13 your select's work for me (both mobile and desktop). Could you check it again? If it still has problems, then you can prepare a try.mudblazor snippet that has your select's razor code and valuechanged - bindvalue methods
try.mudblazor uses the wasm hosting model, and in my cases the autocomplete/select bug happens only on the server-side hosting + touch device, so I was unable to recreate this bug on try.mudblazor platform.

@mckaragoz has already started a PR with the fix - I can confirm that it fixes the bug on my cases. I hope that MudBlazor team will soon rollout another hotfix release, until then we can use this:
https://github.com/mckaragoz/MudBlazor/tree/AutocompleteTouchFix
@mckaragoz many thanks for that!

In a clean, new .NET 6 Blazor Server project, with only one page that only has one autocomplete in it, everything worked perfect until I configured the Azure SignalR Service. After that autocomplete does not close. When I remove the Azure SignalR section in appsettings.json it works perfectly again. I know it sounds crazy but it is true... This happens only in versions after 6.06.

This may be the case for me as well - I had experimented with adding Azure SignalR service for my app around the time that I added MudBlazor. I am removing the section altogether from appsettings (it was set to Enabled: false) and hopefully that will make a difference. UPDATE: Removed this but still seeing the issue in my deployed app.
@mckaragoz

@negator13 your select's work for me (both mobile and desktop). Could you check it again? If it still has problems, then you can prepare a try.mudblazor snippet that has your select's razor code and valuechanged - bindvalue methods

Please note again that it often takes a few tries of fiddling with the different inputs before this bug occurs. It's still happening for me. I'll work on a snippet, how/where do I link it to this issue?

@mckaragoz
Here is a snippet. It will not compile because I had to rip out a lot of stuff including the actual data sources, but it hopefully gives you enough information to work  with about how I have implemented the controls.
https://try.mudblazor.com/snippet/wEQQEdHbSXsmUPUo

Few more additions regarding the MudSelect won't close after selection:

running localhost the problem never occures, just when running on a remote server
when the problem occures, the MudOverlay inside MudSelect is closed, just the MudPopover is not

I think it is some kind of a rendering/diffing issue. In one case using MudPopover as standalone i had to use the @key attribute on the popover and change it when i needed it to close because just setting the Open parameter to false was not enough, maybe this is the case here too.

Few more additions regarding the MudSelect won't close after selection:

running localhost the problem never occures, just when running on a remote server
when the problem occures, the MudOverlay inside MudSelect is closed, just the MudPopover is not

I think it is some kind of a rendering/diffing issue. In one case using MudPopover as standalone i had to use the @key attribute on the popover and change it when i needed it to close because just setting the Open parameter to false was not enough, maybe this is the case here too.

Tried to add @key but didn't work.
And here is another question, same autocomplete work on WASM, Wasm-Mobile and Server Side, but not server side-mobile. Why?

I have the same problem on my site. Works when I run it from Visual Studio but when deployed to a production server a MudAutocomplete dropdown does not close when an item is selected.
If I click on a different MudSelect above this autocomplete it will close.
Another characteristic of this bug is that as you are typing values into the autocomplete field the options being offered in the dropdown are one character behind. For example, if I type ABC I get offered options that contain AB. Again this works fine locally. If I left-arrow on the ABC or focus leaves the page completely then the options are correctly restricted to options containing ABC.
I wonder if it is a timing issue. I am testing on a Windows machine with Chrome, Firefox and Edge. I am using MudBlazor 6.0.9.
This was working with an earlier version of MudBlazor but not sure when it broke. I think 6.0.4 was ok.

.

I have some news regarding the MudSelect won't close problem. We were on the 6.0.8 version and this produced the bug. But after i've upgraded the project to the latest 6.0.9 the MudSelect seems to be working fine as for now.

This did not help for me, I tried upgrading to 6.0.9 and was still having the issue consistently. I've now downgraded it to 6.0.4 as others have reported not having the problem before version 6.0.5.

I have some news regarding the MudSelect won't close problem. We were on the 6.0.8 version and this produced the bug. But after i've upgraded the project to the latest 6.0.9 the MudSelect seems to be working fine as for now.

This did not help for me, I tried upgrading to 6.0.9 and was still having the issue consistently. I've now downgraded it to 6.0.4 as others have reported not having the problem before version 6.0.5.

So no problem with 6.0.4?

So no problem with 6.0.4?

I am still seeing the "lag" that @woaksie describes above:

as you are typing values into the autocomplete field the options being offered in the dropdown are one character behind. For example, if I type ABC I get offered options that contain AB

The issue with the controls not closing seems better, although it still gets stuck open sometimes, I think when the choice are "lagging" like this.

What about this #4326

Using bisecting I found out that this PR causes the issue: 6ea9967c9f4b43ed7cce60eb5070890186b850f9 AutoComplete: Fix initial open with server-side and non-async search (https://github.com/MudBlazor/MudBlazor/pull/3776)

@henon Deployed the latest code with your fixes to my test instance https://eldenring-test.azurewebsites.net/calculator, I believe the problem is fixed. Thank you for taking the time to use git bisect to find the culprit


[bug] null is not an object (evaluating 'e[Q]=null')

Describe the bug
I'm seeing a sporadic error in our Sentry logs:
https://sentry.io/share/issue/13252ea1bdb84ec083803f1f55ad6a81/
To Reproduce
Sporadic error, can't reproduce.
Information

Versions - Look in your package.json for this information:
sortablejs = ^1.14.0
@types/sortablejs = ^1
This code is the culprit, I'm pretty sure. I'm not sure what expando is, as it's poorly named, but there's some assumption here that's causing the error.

expando is just a property set on the HTML element to attach the sortable object to, so it can be accessed by Sortable directly from the element. It's value is 'Sortable' + (new Date).getTime(). Hopefully this helps, I'm not sure why you would be getting that error without seeing more of your code. Expando will never be null.

You're probably right, I bet the Vue component is getting unmounted right before sortable.destroy() is called. There's too much complex code to share, so I'll just close this and investigate further. Thanks!


\Request::ip() returns load balancer's IP

When Laravel sits behind a load balancer, the Request::ip() returns the IP of the load balancer instead the IP of the client.
The Client IP should also return 'HTTP_X_FORWARDED_FOR'

This is known and is intended.

The Client IP should also return 'HTTP_X_FORWARDED_FOR'

No it shouldn't. We can't trust that information.

Check out https://github.com/fideloper/TrustedProxy.

Also, this: http://symfony.com/doc/current/components/http_foundation/trusting_proxies.html

@GrahamCampbell and @franzliedke thank you both for the links. I am running into the same snafu here and both links will solve my problems.

Did you guys manage to sort this out? I'm having a hard time getting this to work on Heroku.
I've configured the trustedproxy.php file, but no luck so far =/.
I can get the IP via $_SERVER['HTTP_X_FORWARDED_FOR'], but I obviously want to use Request::ip();

Nevermind. I've figured this out now.

@badcom How you solved this problem?

@saeedvaziry

Check out https://github.com/fideloper/TrustedProxy.


[5.0.0] - Unable to set "window open" settings values

The windows open detection windows to enter values, keeps on coming up and doesn't validate...

Hi,
Yes, I've this error in the log. We cannot finalize a configuration.
2023-12-18 08:02:24.683 ERROR (MainThread) [custom_components.versatile_thermostat.config_flow] Only one window detection method should be used. Use window_sensor or auto window open detection but not both

Hello, hum I see the problem.
You should uncheck the "Use central configuration" for the window and remove the values for auto window detection.
I will improve this but it should be working with that

Hello, hum I see the problem.
You should uncheck the "Use central configuration" for the window and remove the values for auto window detection. I will improve this but it should be working with that

if we delete the values of the auto detection window and validate. This resets the default values and we cannot continue to finalize the configuration.

I wonder why I don't run into this case. I will certainly not be able to fix today.

I try on my side.
On the "Central configuration" I've got this:

In the VTherm configuration itself, I've got this:

And this is working fine.
If I uncheck the "Use central configuration" :

I cannot validate this window because the both window mode are configured.

The error is not displayed and that is the bug for me.
And you are right, when I remove the auto detection open window parameters:

The error is still there (but not displayed).
So the workaround is to add a window sensor in the previous page and check "Use central configuration" or to deactivate "With window detection" in the first configuration page.

I used the central configuration and I was able to finalize the Vtherm configuration.
But you have seen that if we do not use the central configuration for the openings, we cannot finalize the configuration.

https://github.com/jmcollin78/versatile_thermostat/releases/tag/5.0.1


fixed some divs, double location in form, and datepicker background c…

…olor
This PR is necessary because merge conflicts suck and even though I ran it after I thought everything was resolved... there were still a few issues! a couple divs out of place were removed, a duplicate "location" field was removed from the event form, and the datepicker background color was changed to white.

looks good! we should add more styling to the search results and edit events page!


Helium explorer showing relayed when not

Today my helium explorer app started showing I'm in relayed mode when my sensecap dashboard shows everything is good and not in relayed mode I noticed my listen ip is missed up again showing Random reading instead of actual ip wasn't there an update for this recently please help

@haze94 this is a repository for blockchain governance, not hotspot issues. Please try the Discord #hotspot-issues channel instead


Update annotating-typed-datasets.md

Fixed typos.

CLA check seems stuck. I'll close and reopen this to see if it fixes that issue.


python310Packages.oci: 2.110.0 -> 2.110.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python310Packages.oci is: Oracle Cloud Infrastructure Python SDK
meta.homepage for python310Packages.oci is: https://github.com/oracle/oci-python-sdk
meta.changelog for python310Packages.oci is: https://github.com/oracle/oci-python-sdk/blob/v2.110.1/CHANGELOG.rst
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2.110.1 with grep in /nix/store/j1a1a1sgs1p1iymfqs4qk4lbs2wfdvcm-python3.10-oci-2.110.1
found 2.110.1 in filename of file in /nix/store/j1a1a1sgs1p1iymfqs4qk4lbs2wfdvcm-python3.10-oci-2.110.1

Rebuild report (if merged into master) (click to expand)

6 total rebuild path(s)

6 package rebuild(s)

First fifty rebuilds by attrpath
lexicon
oci-cli
python310Packages.oci
python310Packages.ocifs
python311Packages.oci
python311Packages.ocifs

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/j1a1a1sgs1p1iymfqs4qk4lbs2wfdvcm-python3.10-oci-2.110.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python310Packages.oci https://github.com/r-ryantm/nixpkgs/archive/505c9718cd465aad854b6131beb48cf20aa908ab.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/j1a1a1sgs1p1iymfqs4qk4lbs2wfdvcm-python3.10-oci-2.110.1
ls -la /nix/store/j1a1a1sgs1p1iymfqs4qk4lbs2wfdvcm-python3.10-oci-2.110.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

6 packages built:

lexicon
oci-cli
python310Packages.oci
python310Packages.ocifs
python311Packages.oci
python311Packages.ocifs

Maintainer pings
cc @ilian for testing.

Result of nixpkgs-review pr 249971 run on x86_64-linux 1

12 packages built:

lexicon
lexicon.dist
oci-cli
oci-cli.dist
python310Packages.oci
python310Packages.oci.dist
python310Packages.ocifs
python310Packages.ocifs.dist
python311Packages.oci
python311Packages.oci.dist
python311Packages.ocifs
python311Packages.ocifs.dist