Global quotient penalties [isolated]

Isolated penalties via a global quotient feature.
Pulled out of #2159. Branch based on/dependent on account-reform (#2176)

Copied from #2150:
This PR changes the way that we process inactivity penalties (both in the "normal case" and in the "inactivity leak" case). Currently, we process such penalties by directly adjusting all active validators' balances, going through all validators in a loop at the end of each epoch. However, this poses the risk that even a chain with a very low level of participation (eg. 100 empty epochs followed by a single block) requires O(N) work per epoch, leading to a potential DoS vector via an attacker proposing many such chains.
This PR fixes this by moving all validator penalties into a single global quotient, balance_denominator, which starts at 10**9 gwei and increments from there. For example, if in some epoch, participating validators are to gain a reward of 0.02% and nonparticipating validators a penalty of 0.03%, the balance_denominator increases by 1.0003x, and participating validators are assigned a reward of 0.05%. If no one (or almost no one) is participating, then very little work needs to be done except for the single O(1) operation of adjusting the balance_denominator.
We make effective balances reflect the denominator as part of hysteresis: when the balance_denominator increases, the thresholds needed for a validator to be assigned a particular EB level change. For example, for an EB of 20 ETH, at the start (balance_denominator == 1), the hysteresis thresholds are 19.75 ETH to drop below and 21.25 ETH to go above 20 ETH. But when the balance_denominator increases by 1.0003x, those thresholds shift to 19.755925 ETH to drop below and 21.256375 ETH to go above. The buckets themselves shift.
When the balance_denominator goes above 2, we perform the extremely rare procedure of halving both the balance_denominator and everyone's balances (so the effective balances stay the same).
This approach is slightly different from #1340 in that balances are reconciled during hysteresis and not during the first block after a series of empty slots; this arguably increases efficiency for low-participation chains (and not just "nearly zero participation chains") further.

Some comments that arose based on a conversation with @paulhauner

not-yet-activated and exited validators are currently subject to changes in the penalty quotient even though they can’t get rewards [for exits, maybe balances can be calculated against current penalty quotient and frozen at exit. similar for activation]
deposited ETH amount needs to be adjusted for the current penalty quotient when creating / topping up a validator
there are still a couple of O(N) loops (i.e. updating effective balances and process registry updates) <— maybe these can be optimized more on client side but unclear and cost could be significant at times
[related to 3] depending on what might change in the state due to some of the loops still present, intermittent calculation of state_roots might still be a problem [thus not storing of empty state roots would be a huge savings but at a cost to funtionality]

Some comments that arose based on a conversation with @paulhauner

not-yet-activated and exited validators are currently subject to changes in the penalty quotient even though they can’t get rewards [for exits, maybe balances can be calculated against current penalty quotient and frozen at exit. similar for activation]
deposited ETH amount needs to be adjusted for the current penalty quotient when creating / topping up a validator
there are still a couple of O(N) loops (i.e. updating effective balances and process registry updates) <— maybe these can be optimized more on client side but unclear and cost could be significant at times
[related to 3] depending on what might change in the state due to some of the loops still present, intermittent calculation of state_roots might still be a problem [thus not storing of empty state roots would be a huge savings but at a cost to funtionality]

I think the remaining O(N) loops can be optimized by using priority queues to store who will soon be activated/exited and who is the closest to needing an effective balance update. Agree that (1) and (2) can be managed with changes to the spec (though I'll probably make a different PR that uses a multiplication factor instead of a balance numerator; can fix those issues while doing that).

I think the remaining O(N) loops can be optimized by using priority queues to store who will soon be activated/exited and who is the closest to needing an effective balance update. Agree that (1) and (2) can be managed with changes to the spec (though I'll probably make a different PR that uses a multiplication factor instead of a balance numerator; can fix those issues while doing that).


test_pubmed_to_pmc is failing inconsistently

See https://github.com/monarch-initiative/curategpt/actions/runs/11411477151/job/31756021093
This may be some kind of PubMed API issue - completes as expected on my local system with Python 3.10

let's just do some @pytest.mark.integration or @pytest.mark.pubmed etc


Add way to easily navigate to the quota increase screen

Once a user has identified a quota that needs to be modified they need to navigate away from the dashboards to a different screen to request an update to the quota. Can we provide a link next to the metric on Dashboard to raise Quota Increase Request

Hi @bgood , May I please work on this issue?

@nikhil6624 Thanks for extending help. We need APIs to programmatically create QIR. We are in touch with the Product Management for the API release.
Meanwhile, we can point back to the page and based on user's access, user might be able to access QIR. Please let me know how are you planning to integrate.


Swagger-related code missing from section "Register the database context"

Under the section titled "Register the database context" #register-the-database-context
In the listed code for Startup.cs, the code for Swagger is not included. This probably won't confuse anyone but a very new user. (I'm using .NET 5.0).
The following lines are missing:
From the using statements at the top of the code:
using Microsoft.OpenApi.Models;
From ConfigureServices:
services.AddSwaggerGen(c =>
            {
                c.SwaggerDoc("v1", new OpenApiInfo { Title = "ToDoAPI", Version = "v1" });
            });

From Configure:
Within the if(env.IsDevelopment()) if statement:
app.UseSwagger();
app.UseSwaggerUI(c => c.SwaggerEndpoint("/swagger/v1/swagger.json", "ToDoAPI v1"));

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

ID: 583ae3e7-5915-f22b-e54c-6c100cf2a7da
Version Independent ID: 95f2549e-29f9-e31a-b4d0-432b971643ff
Content: Tutorial: Create a web API with ASP.NET Core
Content Source: aspnetcore/tutorials/first-web-api.md
Product: aspnet-core
Technology: aspnetcore-tutorials
GitHub Login: @Rick-Anderson
Microsoft Alias: riande

Per the doc:
The preceding code:
Removes the Swagger calls.


sdl-freerdp on wayland still confused with more than 2 monitors

Describe the bug
I am running a 3 monitor setup and am unable to use monitors 1 and 2 with /multimon.
Monitor layout:
sdl-freerdp  +monitor-list
[...]
listing 3 monitors:
     * [0] [HDMI-A-1 29"] 3840x2160     +3840+0
       [1] [DP-3 29"] 3840x2160 +0+0
       [2] [DP-1 29"] 3840x2160 +7680+0

sdl-freerdp-output:
sdl-freerdp   /monitors:0,2 /multimon [host, password etc.]
[...]
Supplied monitor ID[1]=2 is invalid, only [0-1] are allowed

When using /monitors 0,1 or 1,0 two windows are opened on monitor 1.
To Reproduce
Steps to reproduce the behavior:
see above
Expected behavior
The windows should be created as fullscreen-windows on the selected screens, and one should be able to select those screens.
Screenshots
Application details

FreeRDP version (xfreerdp /version)

* [20:22:46:499] [14337:00003801] [WARN][com.freerdp.core.rdp] - [log_build_warn][0x563b81c29b10]: *************************************************
[20:22:46:499] [14337:00003801] [WARN][com.freerdp.core.rdp] - [log_build_warn][0x563b81c29b10]: This build is using [experimental] build options:
[20:22:46:499] [14337:00003801] [WARN][com.freerdp.core.rdp] - [log_build_warn][0x563b81c29b10]: * 'WITH_VAAPI=ON'
[20:22:46:499] [14337:00003801] [WARN][com.freerdp.core.rdp] - [log_build_warn][0x563b81c29b10]:
[20:22:46:499] [14337:00003801] [WARN][com.freerdp.core.rdp] - [log_build_warn][0x563b81c29b10]: [experimental] build options might crash the application
[20:22:46:499] [14337:00003801] [WARN][com.freerdp.core.rdp] - [log_build_warn][0x563b81c29b10]: *************************************************
[20:22:46:499] [14337:00003801] [WARN][com.freerdp.core.rdp] - [log_build_warn][0x563b81c29b10]: *************************************************
[20:22:46:499] [14337:00003801] [WARN][com.freerdp.core.rdp] - [log_build_warn][0x563b81c29b10]: This build is using [debug] build options:
[20:22:46:499] [14337:00003801] [WARN][com.freerdp.core.rdp] - [log_build_warn][0x563b81c29b10]: * 'WITH_DEBUG_ALL=ON'
[20:22:46:499] [14337:00003801] [WARN][com.freerdp.core.rdp] - [log_build_warn][0x563b81c29b10]: * 'WITH_DEBUG_CAPABILITIES=ON'
[20:22:46:499] [14337:00003801] [WARN][com.freerdp.core.rdp] - [log_build_warn][0x563b81c29b10]: * 'WITH_DEBUG_CERTIFICATE=ON'
[20:22:46:499] [14337:00003801] [WARN][com.freerdp.core.rdp] - [log_build_warn][0x563b81c29b10]: * 'WITH_DEBUG_CHANNELS=ON'
[20:22:46:499] [14337:00003801] [WARN][com.freerdp.core.rdp] - [log_build_warn][0x563b81c29b10]: * 'WITH_DEBUG_CLIPRDR=ON'
[20:22:46:499] [14337:00003801] [WARN][com.freerdp.core.rdp] - [log_build_warn][0x563b81c29b10]: * 'WITH_DEBUG_CODECS=ON'
[20:22:46:499] [14337:00003801] [WARN][com.freerdp.core.rdp] - [log_build_warn][0x563b81c29b10]: * 'WITH_DEBUG_DVC=ON'
[20:22:46:499] [14337:00003801] [WARN][com.freerdp.core.rdp] - [log_build_warn][0x563b81c29b10]: * 'WITH_DEBUG_KBD=ON'
[20:22:46:499] [14337:00003801] [WARN][com.freerdp.core.rdp] - [log_build_warn][0x563b81c29b10]: * 'WITH_DEBUG_LICENSE=ON'
[20:22:46:499] [14337:00003801] [WARN][com.freerdp.core.rdp] - [log_build_warn][0x563b81c29b10]: * 'WITH_DEBUG_NEGO=ON'
[20:22:46:499] [14337:00003801] [WARN][com.freerdp.core.rdp] - [log_build_warn][0x563b81c29b10]: * 'WITH_DEBUG_NLA=ON'
[20:22:46:499] [14337:00003801] [WARN][com.freerdp.core.rdp] - [log_build_warn][0x563b81c29b10]: * 'WITH_DEBUG_RAIL=ON'
[20:22:46:499] [14337:00003801] [WARN][com.freerdp.core.rdp] - [log_build_warn][0x563b81c29b10]: * 'WITH_DEBUG_RDP=ON'
[20:22:46:499] [14337:00003801] [WARN][com.freerdp.core.rdp] - [log_build_warn][0x563b81c29b10]: * 'WITH_DEBUG_RDPDR=ON'
[20:22:46:499] [14337:00003801] [WARN][com.freerdp.core.rdp] - [log_build_warn][0x563b81c29b10]: * 'WITH_DEBUG_RDPEI=ON'
[20:22:46:499] [14337:00003801] [WARN][com.freerdp.core.rdp] - [log_build_warn][0x563b81c29b10]: * 'WITH_DEBUG_RDPGFX=ON'
[20:22:46:499] [14337:00003801] [WARN][com.freerdp.core.rdp] - [log_build_warn][0x563b81c29b10]: * 'WITH_DEBUG_REDIR=ON'
[20:22:46:499] [14337:00003801] [WARN][com.freerdp.core.rdp] - [log_build_warn][0x563b81c29b10]: * 'WITH_DEBUG_RFX=ON'
[20:22:46:499] [14337:00003801] [WARN][com.freerdp.core.rdp] - [log_build_warn][0x563b81c29b10]: * 'WITH_DEBUG_RINGBUFFER=ON'
[20:22:46:499] [14337:00003801] [WARN][com.freerdp.core.rdp] - [log_build_warn][0x563b81c29b10]: * 'WITH_DEBUG_SCARD=ON'
[20:22:46:499] [14337:00003801] [WARN][com.freerdp.core.rdp] - [log_build_warn][0x563b81c29b10]: * 'WITH_DEBUG_SND=ON'
[20:22:46:499] [14337:00003801] [WARN][com.freerdp.core.rdp] - [log_build_warn][0x563b81c29b10]: * 'WITH_DEBUG_SVC=ON'
[20:22:46:499] [14337:00003801] [WARN][com.freerdp.core.rdp] - [log_build_warn][0x563b81c29b10]: * 'WITH_DEBUG_TIMEZONE=ON'
[20:22:46:499] [14337:00003801] [WARN][com.freerdp.core.rdp] - [log_build_warn][0x563b81c29b10]: * 'WITH_DEBUG_TRANSPORT=ON'
[20:22:46:499] [14337:00003801] [WARN][com.freerdp.core.rdp] - [log_build_warn][0x563b81c29b10]: * 'WITH_DEBUG_TSG=ON'
[20:22:46:499] [14337:00003801] [WARN][com.freerdp.core.rdp] - [log_build_warn][0x563b81c29b10]: * 'WITH_DEBUG_WND=ON'
[20:22:46:499] [14337:00003801] [WARN][com.freerdp.core.rdp] - [log_build_warn][0x563b81c29b10]: * 'WITH_DEBUG_X11=ON'
[20:22:46:499] [14337:00003801] [WARN][com.freerdp.core.rdp] - [log_build_warn][0x563b81c29b10]: * 'WITH_DEBUG_X11_LOCAL_MOVESIZE=ON'
[20:22:46:499] [14337:00003801] [WARN][com.freerdp.core.rdp] - [log_build_warn][0x563b81c29b10]: * 'WITH_DEBUG_XV=ON'
[20:22:46:499] [14337:00003801] [WARN][com.freerdp.core.rdp] - [log_build_warn][0x563b81c29b10]:
[20:22:46:499] [14337:00003801] [WARN][com.freerdp.core.rdp] - [log_build_warn][0x563b81c29b10]: [debug] build options might leak sensitive information (credentials, ...)
[20:22:46:499] [14337:00003801] [WARN][com.freerdp.core.rdp] - [log_build_warn][0x563b81c29b10]: *************************************************
This is FreeRDP version 3.8.1-dev0 (60609251f)

Command line used
Output of xfreerdp /buildconfig

Build configuration: BUILD_TESTING=OFF WINPR_HAVE_AIO_H=1 WINPR_HAVE_EXECINFO_BACKTRACE=1 WINPR_HAVE_EXECINFO_BACKTRACE_SYMBOLS=1 WINPR_HAVE_EXECINFO_BACKTRACE_SYMBOLS_FD=1 WINPR_HAVE_EXECINFO_HEADER=1 WINPR_HAVE_FCNTL_H=1 WINPR_HAVE_GETLOGIN_R=1 WINPR_HAVE_GETPWUID_R=1 WINPR_HAVE_INTTYPES_H=1 WINPR_HAVE_POLL_H=1 WINPR_HAVE_PTHREAD_MUTEX_TIMEDLOCK_LIB=1 WINPR_HAVE_PTHREAD_MUTEX_TIMEDLOCK_LIBS= WINPR_HAVE_PTHREAD_MUTEX_TIMEDLOCK_SYMBOL=1 WINPR_HAVE_STDBOOL_H=1 WINPR_HAVE_STDINT_H=1 WINPR_HAVE_STRERROR_R=1 WINPR_HAVE_STRNDUP=1 WINPR_HAVE_SYSLOG_H=1 WINPR_HAVE_SYS_EVENTFD_H=1 WINPR_HAVE_SYS_FILIO_H= WINPR_HAVE_SYS_SELECT_H=1 WINPR_HAVE_SYS_SOCKIO_H= WINPR_HAVE_SYS_TIMERFD_H=1 WINPR_HAVE_TM_GMTOFF=1 WINPR_HAVE_UNISTD_H=1 WINPR_HAVE_UNWIND_H=1 WITH_AAD=ON WITH_ABSOLUTE_PLUGIN_LOAD_PATHS=ON WITH_ADD_PLUGIN_TO_RPATH=OFF WITH_ALSA=ON WITH_AVX2=ON WITH_AVX2_AVAILABLE=1 WITH_BINARY_VERSIONING=OFF WITH_CAIRO=OFF WITH_CCACHE=OFF WITH_CHANNELS=ON WITH_CJSON_REQUIRED=OFF WITH_CLANG_FORMAT=ON WITH_CLIENT=ON WITH_CLIENT_AVAILABLE=1 WITH_CLIENT_AVAILABLE=1 WITH_CLIENT_CHANNELS=ON WITH_CLIENT_CHANNELS_AVAILABLE=1 WITH_CLIENT_CHANNELS_AVAILABLE=1 WITH_CLIENT_COMMON=ON WITH_CLIENT_INTERFACE=OFF WITH_CLIENT_SDL=ON WITH_CLIENT_SDL2=ON WITH_CLIENT_SDL3=OFF WITH_CLIENT_SDL_AVAILABLE=1 WITH_CLIENT_SDL_AVAILABLE=1 WITH_CLIENT_SDL_VERSIONED=OFF WITH_CUPS=ON WITH_DEBUG_ALL=ON WITH_DEBUG_CAPABILITIES=ON WITH_DEBUG_CERTIFICATE=ON WITH_DEBUG_CHANNELS=ON WITH_DEBUG_CLIPRDR=ON WITH_DEBUG_CODECS=ON WITH_DEBUG_DVC=ON WITH_DEBUG_EVENTS=OFF WITH_DEBUG_KBD=ON WITH_DEBUG_LICENSE=ON WITH_DEBUG_MUTEX=OFF WITH_DEBUG_NEGO=ON WITH_DEBUG_NLA=ON WITH_DEBUG_NTLM=OFF WITH_DEBUG_RAIL=ON WITH_DEBUG_RDP=ON WITH_DEBUG_RDPDR=ON WITH_DEBUG_RDPEI=ON WITH_DEBUG_RDPGFX=ON WITH_DEBUG_REDIR=ON WITH_DEBUG_RFX=ON WITH_DEBUG_RINGBUFFER=ON WITH_DEBUG_SCARD=ON WITH_DEBUG_SCHANNEL=OFF WITH_DEBUG_SDL_EVENTS=OFF WITH_DEBUG_SDL_KBD_EVENTS=OFF WITH_DEBUG_SND=ON WITH_DEBUG_SVC=ON WITH_DEBUG_SYMBOLS=OFF WITH_DEBUG_THREADS=OFF WITH_DEBUG_TIMEZONE=ON WITH_DEBUG_TRANSPORT=ON WITH_DEBUG_TSG=ON WITH_DEBUG_TSMF=OFF WITH_DEBUG_TSMF=OFF WITH_DEBUG_TSMF_AVAILABLE=0 WITH_DEBUG_TSMF_AVAILABLE=0 WITH_DEBUG_URBDRC=OFF WITH_DEBUG_WND=ON WITH_DEBUG_X11=ON WITH_DEBUG_X11_LOCAL_MOVESIZE=ON WITH_DEBUG_XV=ON WITH_DOCUMENTATION=OFF WITH_DSP_EXPERIMENTAL=OFF WITH_DSP_FFMPEG=ON WITH_DSP_FFMPEG_AVAILABLE=1 WITH_DSP_FFMPEG_AVAILABLE=1 WITH_EVENTFD_READ_WRITE=1 WITH_FAAC=OFF WITH_FAAD2=OFF WITH_FDK_AAC=OFF WITH_FFMPEG=ON WITH_FREERDP_DEPRECATED=OFF WITH_FREERDP_DEPRECATED_COMMANDLINE=ON WITH_FULL_CONFIG_PATH=OFF WITH_FUSE=ON WITH_GFX_FRAME_DUMP=OFF WITH_GFX_H264=ON WITH_GFX_H264=ON WITH_GPROF=OFF WITH_GSM=OFF WITH_GSTREAMER_1_0=OFF WITH_INTERNAL_MD4=OFF WITH_INTERNAL_MD5=OFF WITH_INTERNAL_RC4=OFF WITH_IPP=OFF WITH_JPEG=ON WITH_JSONC_REQUIRED=OFF WITH_JSON_DISABLED=OFF WITH_KEYBOARD_LAYOUT_FROM_FILE=OFF WITH_KRB5=OFF WITH_KRB5_NO_NTLM_FALLBACK=OFF WITH_LAME=OFF WITH_LIBRARY_VERSIONING=ON WITH_LIBRESSL=OFF WITH_LIBSYSTEMD=OFF WITH_LODEPNG=OFF WITH_MACAUDIO=OFF WITH_MACAUDIO=OFF WITH_MACAUDIO_AVAILABLE=0 WITH_MACAUDIO_AVAILABLE=0 WITH_MANPAGES=ON WITH_MBEDTLS=OFF WITH_NATIVE_SSPI=OFF WITH_NEON=OFF WITH_OPAQUE_SETTINGS=OFF WITH_OPENCL=OFF WITH_OPENH264=OFF WITH_OPENSSL=ON WITH_OPUS=OFF WITH_OSS=OFF WITH_PCSC=OFF WITH_PKCS11=OFF WITH_POLL=ON WITH_PROFILER=OFF WITH_PULSE=ON WITH_SAMPLE=ON WITH_SANITIZE_ADDRESS=OFF WITH_SANITIZE_ADDRESS_AVAILABLE=1 WITH_SANITIZE_ADDRESS_AVAILABLE=1 WITH_SANITIZE_MEMORY=OFF WITH_SANITIZE_MEMORY_AVAILABLE=1 WITH_SANITIZE_MEMORY_AVAILABLE=1 WITH_SANITIZE_THREAD=OFF WITH_SANITIZE_THREAD_AVAILABLE=1 WITH_SANITIZE_THREAD_AVAILABLE=1 WITH_SDL_IMAGE_DIALOGS=OFF WITH_SDL_LINK_SHARED=ON WITH_SERVER=OFF WITH_SERVER_INTERFACE=ON WITH_SMARTCARD_EMULATE=ON WITH_SMARTCARD_INSPECT=OFF WITH_SMARTCARD_PCSC=ON WITH_SOXR=OFF WITH_SSE2=ON WITH_SWSCALE=ON WITH_SYSTEMD=OFF WITH_THIRD_PARTY=OFF WITH_TIMEZONE_COMPILED=ON WITH_TIMEZONE_FROM_FILE=OFF WITH_TIMEZONE_ICU=OFF WITH_UNICODE_BUILTIN=OFF WITH_URIPARSER=OFF WITH_VAAPI=ON WITH_VAAPI_AVAILABLE=1 WITH_VAAPI_AVAILABLE=1 WITH_VALGRIND_MEMCHECK=OFF WITH_VALGRIND_MEMCHECK_AVAILABLE=1 WITH_VALGRIND_MEMCHECK_AVAILABLE=1 WITH_VERBOSE_WINPR_ASSERT=ON WITH_VIDEO_FFMPEG=ON WITH_VIDEO_FFMPEG_AVAILABLE=1 WITH_VIDEO_FFMPEG_AVAILABLE=1 WITH_WAYLAND=ON WITH_WEBVIEW=OFF WITH_WINPR_DEPRECATED=OFF WITH_WINPR_JSON=ON WITH_WINPR_TOOLS=ON WITH_WIN_CONSOLE=ON WITH_X11=ON WITH_XCURSOR=ON WITH_XEXT=ON WITH_XFIXES=ON WITH_XI=ON WITH_XINERAMA=OFF WITH_XRANDR=ON WITH_XRENDER=ON WITH_XV=ON
Build type:          Debug
CFLAGS:               -fPIC -Wall -fvisibility=hidden -Wimplicit-function-declaration -Wredundant-decls -g -fno-omit-frame-pointer
Compiler:            GNU, 13.3.1
Target architecture: x64

OS version connecting to (server side)
n/a
If available the log output from a run with /log-level:trace 2>&1 | tee log.txt
If you built it yourself add some notes which tag/commit/branch you have used, also your cmake parameters and
compiler can help
the current master as of 2024-10-15 20:10 CEST (60609251fb121733104c7120cdf8f18691506d9f)

Environment (please complete the following information):

OS: Linux
Version/Distribution: Gentoo
Architecture: x86_64
wayland
KDE 6.2

Additional context
This should be reproducible with /multimon /monitors:1 on a dual monitor setup

your second issue is already known with https://github.com/FreeRDP/FreeRDP/issues/10526 (and most likely a SDL bug, but working on a workaround)

your second issue is already known with #10526 (and most likely a SDL bug, but working on a workaround)
Ah, sorry - i assumed this was a side-effect of the monitors not being correctly assigned and did not search for this


flag for returning non-zero exit code on hints

It would be great if you could have dartanalyzer return a non-zero exit code if it found hints, right now in our automated processes we have to scrape the logs to look if there were hints.

this was already addressed here d3b33ce85e524868105f55b3a76154cc391e9408


FLAUI .netcore compatibilty

Hi Roemer,
Can you please tell in how much time we can expect FLAUI would be fully compatible with core as we need to decide for which framework to use for windows automation.
Thanks
Preeti

Hi Roemer,
I tried to use FLAUI UIA3 alpha version to check if we can use it in with following code in our .netcore project.
FlaUI.Core.Application app = FlaUI.Core.Application.Attach("JAVAW");
var automation = new UIA3Automation();
        Window[] windows = app.GetAllTopLevelWindows(automation);

But getting following exception:
System.IO.FileNotFoundException occurred
HResult=0x80070002
Message=Could not load file or assembly 'Accessibility, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'. The system cannot find the file specified.
Source=
StackTrace:
at FlaUI.UIA3.UIA3PatternLibrary.get_LegacyIAccessiblePattern()
at FlaUI.UIA3.UIA3PatternLibrary.get_AllForCurrentFramework()
at FlaUI.Core.AutomationBase..ctor(IPropertyLibrary propertyLibrary, IEventLibrary eventLibrary, IPatternLibrary patternLibrary)
at FlaUI.UIA3.UIA3Automation..ctor()
at testingFlaui.Program.Main(String[] args) in c:\users\e3005457\source\repos\testingFlaui\testingFlaui\Program.cs:line 13
Can you please help with the same.
Thanks

So I investigated a bit.
The following things needed to be removed:

Capture / Capture Image
Overlay Manager (for painting a highlighting rectangle)
IAccessible interface
WPF Point / Rectangle / Color
Registry access (For the operation system)
All in all actually not that much.
I have build some experimental nugetpackages with netcore2.0 and netstandard2.0 assemblies. I will attach them here. Do you mind testing them?

FlaUI.Core&UIA3.NetCore&Standard.zip

FYI: I used the nuget package and it works for dotnetstandard2.0. You have any plans to officially support it? Probably some thigs can be resolved by using the Windows.Compatibility package

Thank you for that feedback! Glad it works. Yes I have this on my list, probably for the 3.0.0 release as 2.0.0 will be out soon (rc1 is now on nuget).

I am pretty much finished with the changes.
There are two things missing:

Get the CI working
Publish the new depencency Interop.UIAutomationClient to Nuget.

The PR with the changes is https://github.com/Roemer/FlaUI/pull/268

The progress is pretty good. I now even implemented all the new UIA features up to the most recent UIA version and fixed some bugs. I have to wait until the nuget team hands me over the Interop.UIAutomationClient nuget package so I can deploy my versioned, fixed interops for UIA3 from https://github.com/Roemer/UIAutomation-Interop. This should be on the 9th of September. I hope to stabilize the CI until then and then you should be prepared for FlaUI v3 with NET Core/Standard compatility!

Also interested in .netcore support. Can I help? dual-targeting netcore3 as well as net461 is not too difficult

It is pretty much ready. I am now only waiting for NuGet so I can deploy the automation interop packages as a separate package (there is already a package with that name, I want to take that over). I should have that within the next days and then I will release at least an RC.
If you want, you can already try the nuget from here: https://ci.appveyor.com/project/RomanBaeriswyl/flaui/builds/28721339/artifacts
Just don't forget to add the interop nuget from here: https://github.com/Roemer/FlaUI/tree/feature/NetStandard/src/libs as well.

Your 2nd Link is broken.
I will give it a try and give feedback

Ah yes, I merged the branch. The nuget can be found here for now: https://github.com/Roemer/FlaUI/tree/master/src/libs

nice! thanks for letting me know about netcore3 support.
On Fri, Nov 15, 2019 at 7:11 PM Roman<EMAIL_ADDRESS>wrote:

Ah yes, I merged the branch. The nuget can be found here for now:
https://github.com/Roemer/FlaUI/tree/master/src/libs
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Roemer/FlaUI/issues/141?email_source=notifications&email_token=ADLEDVLSPJQI6MDIHKDN6CTQT3X6RA5CNFSM4EQHSOSKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEEGNSYQ#issuecomment-554490210,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADLEDVN43SK3AEQ4YGDCI3TQT3X6RANCNFSM4EQHSOSA
.

when i am installing FlaUI.UIA2 i get the NU1701 error, that the package got recreated by .NET Framework 4.6.1

when i am installing FlaUI.UIA2 i get the NU1701 error, that the package got recreated by .NET Framework 4.6.1

Are you using the 3.0.0 version from the appveyor link I posted above? If so, could you upload your project?

Maybe a problem, that i am using .NET Core 2.2?

Yes, UIA2 does only work in .NET Core 3.0 upwards as System.Windows.Automation only exists in 3.0 or higher. So either go to Core 3.0 or try UIA3.

Version 3.0.0-rc.1 with .NET Core/Standard compatibility is now on NuGet! Please give it a try and report feedback to me (here or on gitter).

Everything seems to work, the final 3.0.0 will be released this week. If you encounter problems, feel free to create new issues.


Test how issues works

Does this work?
@GitKarIn @chriskkwan @mirbell @kelsranj @trinhxuann @bclifton2 @saw8579

received :)

got it!


cmd/vendor/golang.org/x/arch/arm64/arm64asm: test zero register mismatch

I got this when testing near HEAD:
--- FAIL: TestObjdumpARM64Testdata (2.20s)
	ext_test.go:195: decode(744bbf38) = "ldrsb x20, [x27,wzr,uxtw]", 4, want "ldrsb x20, [x27,w31,uxtw]", 4

	ext_test.go:195: decode(29493fbc) = "str s9, [x9,wzr,uxtw]", 4, want "str s9, [x9,w31,uxtw]", 4

	ext_test.go:195: decode(225bff38) = "ldrsb w2, [x25,wzr,uxtw #0]", 4, want "ldrsb w2, [x25,w31,uxtw #0]", 4

	ext_test.go:195: decode(cad8bf78) = "ldrsh x10, [x6,wzr,sxtw #1]", 4, want "ldrsh x10, [x6,w31,sxtw #1]", 4

	ext_test.go:195: decode(a278ff3c) = "ldr q2, [x5,xzr,lsl #4]", 4, want "ldr q2, [x5,x31,lsl #4]", 4

	ext_test.go:195: decode(a278ff3c) = "ldr q2, [x5,xzr,lsl #4]", 4, want "ldr q2, [x5,x31,lsl #4]", 4

	ext_test.go:201: 9203 test cases, 686 expected mismatches, 6 failures; 5781 cases/second
	ext_test.go:202: decoder coverage: 95.5%;
	ext_test.go:201: 9203 test cases, 0 expected mismatches, 0 failures; 17619 cases/second
	ext_test.go:202: decoder coverage: 95.5%;
FAIL
FAIL	cmd/vendor/golang.org/x/arch/arm64/arm64asm	10.074s

From ARMv8 ARM: "In instruction encodings, the value 0b11111 (31) is used to indicate the ZR (zero register)."
So this appears to be a disagreement with objdump about whether to call registers w/xzr or w/x31.
I'm not sure exactly which version of objdump was running on this machine. I can dig around to find it if it would help.

@prattmic what revision were you testing at? Were you running all.bash?


Fix create_bucket tests as per new bucket naming conventions

As per amazon s3 spec -
https://docs.aws.amazon.com/awscloudtrail/latest/userguide/cloudtrail-s3-bucket-naming-requirements.html
The s3 bucket names should not contain upper case letters or underscore.
Name cannot end with dash or have consecutive periods, or dashes adjacent to periods
Name length shouldn't exceed 63 characters.
These rules are being enforced via

https://github.com/ceph/ceph/pull/26787

This patch is to update the respective testcases as well.
Note: check_invalid_bucket_name() seem to be not functioning properly.
Hence tagged those tests with 'fails_on_rgw' for now.
Signed-off-by: Soumya Koduri<EMAIL_ADDRESS>

@cbodley @alimaredia ..kindly review the changes.


Keeping annotations order

My actions before raising this issue

[x] Read/searched the docs
[x] Searched past issues

Expected Behaviour
I expect the order of the annotations objects to stay the same after saving and doing a page refresh.
Current Behaviour
The order doesn't stay the same after a page refresh (the IDs of the annotations are overwritten).
Possible Solution
Add an option to keep annotations order or make this a default behavior.
Steps to Reproduce (for bugs)

Create a project and add a task
Create 4-5 annotations on the first image (see the right column and remember the annotations order)
Save and refresh
The order of annotation IDs has changed (see the right column again)

Context
When working on a multi-column document layout detection or a similar project, the order of the annotations is mandatory to keep the flow of the content chaining.
Your Environment

Git hash commit: ba4175bf5b4467bf0fbf89a3fd645cceef7f7c23
Docker version: Docker 20.10.14
Are you using Docker Swarm or Kubernetes: Not using any of them
Operating System and version: Ubuntu 20.04 (WSL2 for Windows 11)

Hi @naourass
That is architecture solution that had lots of discussions in the past. IDs you see in client are clientID, they are not constant. Also each object has server ID that received after the object was saved for the first time. You do not see them, but these IDs are keep.
It would be impossible to keep client ID because we do not strict parallel annotation process somehow within one job .

@bsekachev Thanks for letting me know that it's a dev decision. I may take some time and inspect the code architecture further to see if I can find any reliable workaround for special use cases like mine.

@aelkin
The root reasons because we do not keep original ids I believe: these IDs are primary keys in the database, so it would cause lots of issues if we tried to keep them. Also annotations compatibility between different CVAT instances is important (I mean we need to be able to dump annotations from one CVAT instance and upload it to another CVAT instance what generally would be impossible). And what's more we support multiple annotations formats where these IDs are not assumed to be according to the formats specification.
You can try to save original IDs as an attribute, but I would say there are not convenient way to get these IDs.
If it is important, it might be a feature request, like automatic creation of an attribute with server ID when saving objects on the server. So, in this case you would be able to trace objects.

I do have a lot of issues with annotations orders. I have 7 figures containing 18 annotations in each. After saving and refreshing they are all reordered in way that I have not figured out its logic. Has there been any solutions to this? Thanks!


Create bztgoldenburgde.txt

Added link to the office login instructions and a picture of the page with the office login email you get when you log-in with your student account.
Reworked pull request, since I don't know how to re-open one.

@mirrorhot Thank you for the clarification. Pull request merged.


Update example of to_editor to current arguments

L43 of example in "Simple example of creating a single annotation" section of
https://sys-bio.github.io/libOmexMeta/docs-build/singular_annotations/index.html
editor = rdf.to_editor(sbml, "sbml")

Interesting - this is actually valid syntax since the second argument is a bool and bool("sbml") evaluates to True - hence no error when building the docs examples. Thanks for pointing it out.


Automatic handling of empty, error, and loading states

When I call APIs in Ensemble, I want Ensemble to handle loading, error, and empty state automatically so I dont have to define those myself.

@amin-nas please respond to Vinoth's question above

Duplicate of #833


Fix concurrent Write / Read Performance Regression (introduced in v1.16.0)

What's being changed:

Repairs "broken concurrency" in indexLock
closes #2351

Review checklist

[ ] Documentation has been updated, if necessary. Link to changed documentation:
[ ] Chaos pipeline run or not necessary. Link to pipeline:
[ ] All new code is covered by tests where it is reasonable.
[ ] Performance tests have been run or not necessary.


Manjaro Gnome issues

Manjaro Gnome terminals
I'm trying to display a custom image (same as desktop) in Manjaro, Gnome. It's not working.
I have no issues on i3 but, as soon as I get back to Gnome, it stops working. Config file is edited, is it a terminal issue ?
It works in xterm, but not on gnome terminal and Tilix.
Using Neofetch 5.0.0
Screenshot

Please provide logs from all 3 terminal programs.

@konimex I'm also having this issue on gnome terminal on manjaro. I'd be happy to provide the log but I'm having trouble doing so. Piping the -vv output to a txt file just fills it with garbage and I'm unable to copy and paste it all here. Could you advise how to capture the log? Thanks.

@nickschiffer

Run neofetch -vv 2> neofetchlog
Upload the contents of neofetchlog to pastebin, gist or equivalent


Made colours better

i did the #thing, absolutely cracked at this omg
Accept the request bozo

Looks good


[crypto] Consolidate P-384 OTBN binaries.

Analogous to the P-256 refactor in https://github.com/lowRISC/opentitan/pull/25326 but more dramatic, because P-384 was split into more pieces previously. With larger IMEM, we can use only one binary for P-384 operations, instead of the previous four (keygen/sign/verify/ecdh).
There's again a lot of code churn here, but the vast majority of it is only moved around, not changed. Like with P-256, some names had to be changed to fit the naming convention of definitions from the same C header starting with the same prefix (so e.g. "ecdsa_p384" became "p384_ecdsa").
This saves about 16.4 kB (!) of code size in the cryptolib.

I take it that this passes cryptotest?

P-384 isn't currently set up with cryptotest -- at the time Ryan went through and set up most of the existing tests, it wasn't fully hooked up and available in cryptolib. But for the analogous P-256 changes, yes, everything passes cryptotest :slightly_smiling_face:


[Bug] Using all-in-one prompt prevents normal image grids from being generated

Issue Feedback

[X] I confirm that I have searched for a solution to this issue in the FAQ and couldn't find a solution.
[X] I confirm that I have searched for this issue in the Issues list (including closed ones) and couldn't find a solution.
[X] I confirm that I have read the Wiki and couldn't find a solution.

Describe the Issue
Under normal circumstances when more than one image is batch generated, either through batch count or batch size >1, A1111 produces a single image grid of all generated images.
When using the all-in-one prompt, this grid is not generated at all with a batch count of >1 and batch size of 1.
If both count and size are >1, multiple grids are produced with the number of images in each corresponding to batch size.
The grid is generated normally when the extension is inactive.
Steps to Reproduce
Produce any images using the extension in a batch count of more than one.
Screenshot or log
No warnings in console.
Extension unloaded:

Extension loaded with batch size 1:

Extension loaded with batch size >1:

OS
Windows
Browser
Edge
Stable Diffusion WebUI version
1.8.0
Extension version
2cd8bf2c
Python version
3.10.6
Gradio version
3.41.2

I have not reproduced this issue. In theory, this plugin should not affect parameters such as the batch size and should not impact the generation results.


[BUG]: RuntimeError: CUDA error: an illegal memory access was encountered

🐛 Describe the bug
I run the bert from huggingface with zero, but get RuntimeError: CUDA error: an illegal memory access was encountered, I found that this problem seemed to be caused by initial_scale in config.py
Traceback (most recent call last):
File "colossalai/run.py", line 463, in
train(args)
File "colossalai/run.py", line 252, in train
trainer(model,
File "colossalai/run.py", line 127, in trainer
engine.backward(loss)
File "/home/paulzhang/miniconda3/lib/python3.8/site-packages/colossalai/engine/_base_engine.py", line 163, in backward
ret = self.optimizer.backward(loss)
File "/home/paulzhang/miniconda3/lib/python3.8/site-packages/colossalai/zero/sharded_optim/sharded_optim_v2.py", line 169, in backward
self.model.backward(loss)
File "/home/paulzhang/miniconda3/lib/python3.8/site-packages/colossalai/zero/sharded_model/sharded_model_v2.py", line 233, in backward
loss.backward()
File "/home/paulzhang/miniconda3/lib/python3.8/site-packages/torch/_tensor.py", line 307, in backward
torch.autograd.backward(self, gradient, retain_graph, create_graph, inputs=inputs)
File "/home/paulzhang/miniconda3/lib/python3.8/site-packages/torch/autograd/init.py", line 154, in backward
Variable._execution_engine.run_backward(
RuntimeError: CUDA error: an illegal memory access was encountered
terminate called after throwing an instance of 'c10::CUDAError'
what():  CUDA error: an illegal memory access was encountered
Exception raised from create_event_internal at ../c10/cuda/CUDACachingAllocator.cpp:1211 (most recent call first):
frame #0: c10::Error::Error(c10::SourceLocation, std::string) + 0x42 (0x7f9d1dfa2d62 in /home/paulzhang/miniconda3/lib/python3.8/site-packages/torch/lib/libc10.so)
frame #1:  + 0x1c5f3 (0x7f9d6164f5f3 in /home/paulzhang/miniconda3/lib/python3.8/site-packages/torch/lib/libc10_cuda.so)
frame #2: c10::cuda::CUDACachingAllocator::raw_delete(void*) + 0x1a2 (0x7f9d61650002 in /home/paulzhang/miniconda3/lib/python3.8/site-packages/torch/lib/libc10_cuda.so)
frame #3: c10::TensorImpl::release_resources() + 0xa4 (0x7f9d1df8c314 in /home/paulzhang/miniconda3/lib/python3.8/site-packages/torch/lib/libc10.so)
frame #4:  + 0x29adb9 (0x7f9de496cdb9 in /home/paulzhang/miniconda3/lib/python3.8/site-packages/torch/lib/libtorch_python.so)
frame #5:  + 0xae0c91 (0x7f9de51b2c91 in /home/paulzhang/miniconda3/lib/python3.8/site-packages/torch/lib/libtorch_python.so)
frame #6: THPVariable_subclass_dealloc(_object*) + 0x292 (0x7f9de51b2f92 in /home/paulzhang/miniconda3/lib/python3.8/site-packages/torch/lib/libtorch_python.so)
frame #7:  + 0x15893b (0x56473bab593b in /home/paulzhang/miniconda3/bin/python)
frame #8:  + 0x193141 (0x56473baf0141 in /home/paulzhang/miniconda3/bin/python)
frame #9:  + 0x15893b (0x56473bab593b in /home/paulzhang/miniconda3/bin/python)
frame #10:  + 0x193141 (0x56473baf0141 in /home/paulzhang/miniconda3/bin/python)
frame #11:  + 0x158415 (0x56473bab5415 in /home/paulzhang/miniconda3/bin/python)
frame #12:  + 0x15893b (0x56473bab593b in /home/paulzhang/miniconda3/bin/python)
frame #13:  + 0x193141 (0x56473baf0141 in /home/paulzhang/miniconda3/bin/python)
frame #14:  + 0x1592ac (0x56473bab62ac in /home/paulzhang/miniconda3/bin/python)
frame #15:  + 0x158e77 (0x56473bab5e77 in /home/paulzhang/miniconda3/bin/python)
frame #16:  + 0x158e60 (0x56473bab5e60 in /home/paulzhang/miniconda3/bin/python)
frame #17:  + 0x158e60 (0x56473bab5e60 in /home/paulzhang/miniconda3/bin/python)
frame #18:  + 0x176057 (0x56473bad3057 in /home/paulzhang/miniconda3/bin/python)
frame #19: PyDict_SetItemString + 0x61 (0x56473baf43c1 in /home/paulzhang/miniconda3/bin/python)
frame #20: PyImport_Cleanup + 0x9d (0x56473bb32aad in /home/paulzhang/miniconda3/bin/python)
frame #21: Py_FinalizeEx + 0x79 (0x56473bb64a49 in /home/paulzhang/miniconda3/bin/python)
frame #22: Py_RunMain + 0x183 (0x56473bb66893 in /home/paulzhang/miniconda3/bin/python)
frame #23: Py_BytesMain + 0x39 (0x56473bb66ca9 in /home/paulzhang/miniconda3/bin/python)
frame #24: __libc_start_main + 0xf3 (0x7f9e409e50b3 in /lib/x86_64-linux-gnu/libc.so.6)
frame #25:  + 0x1e21c7 (0x56473bb3f1c7 in /home/paulzhang/miniconda3/bin/python)
Environment
No response

Could you share me your code?

This usually occurs because of CUDA out-of-memory.

@ver217 this is my code
def trainer(train_dataloader, args, val_dataloader=None):
    start_epoch = 0

    shard_strategy = TensorShardStrategy()
    with ZeroInitContext(target_device=torch.cuda.current_device(), shard_strategy=shard_strategy,
                         shard_param=True):
            config = BertConfig.from_pretrained(args.model_name_or_path, num_labels=200)
            model = BertForSequenceClassification.from_pretrained(args.model_name_or_path, config=config)

    optimizer = HybridAdam(model.parameters(), weight_decay=1e-4)
    criterion = nn.CrossEntropyLoss()

    # 开始colossal初始化
    engine, train_dataloader, val_dataloader, _ = colossalai.initialize(model,
                                                                        optimizer,
                                                                        criterion,
                                                                        train_dataloader,
                                                                        val_dataloader,
                                                                        )

    for epoch in range(start_epoch, args.num_epochs):
        epoch_loss = 0

        train_iter = tqdm(
            train_dataloader, desc=f'Epoch:{epoch + 1}', total=len(train_dataloader))

        engine.train()

        torch.cuda.empty_cache()

        for step, inputs in enumerate(train_iter):
            labels = inputs['labels'].view(-1).to(args.device)
            inputs = {key: inputs[key].to(args.device)
                      for key in inputs.keys() if key not in ['labels']}

            output = engine(inputs['text_input_ids'], attention_mask=inputs['text_mask'])
            loss = engine.criterion(output.logits, labels)

            engine.backward(loss)
            engine.step()
            epoch_loss += loss

            train_iter.set_postfix_str(
                f'loss: {epoch_loss / (step+1):.4f}')

This usually occurs because of CUDA out-of-memory.
Yes, after open the zero, seems to have happened the memory overflow, memory growth until oom.
and after turning on Zero, colossalai will output inf during zero

I have the same problem, I'm sure the GPU memory is enough

It means that the cuda and the graphics card are not compatible, just replace one of them


Azure DevOps pipeline breaks as soon as new version of dotnet-coverage tool is published

Description
I have the dotnet-coverage tool installed locally and configured in the dotnet-tool.json file and I use dotnet tool restore to restore all the tools in the pipeline.
As per the title, as soon as a new version is pushed to NuGet, my builds fail.
I had this issue when the 17.9.1 was pushed and I opened this issue https://github.com/microsoft/azure-pipelines-agent/issues/4472
The issue was solved by changing the dotnet-tool.json to point to the latest version.
{
  "version": 1,
  "isRoot": true,
  "tools": {
    "dotnet-coverage": {
      "version": "17.9.1",
      "commands": [
        "dotnet-coverage"
      ]
    }
  }
}

Today, a new version was pushed, 17.9.3, and the build failed again.
I don't think this is the expected behavior, hence the issue.
Configuration
I use .NET SDK 8 RC2
Regression?
It's a new project started after 17.8.6 was pushed to NuGet.
Other information
Everything works fine on my local machine but fails on Azure DevOps pipeline using default agent and ubuntu-latest.

@dsplaisted do you have any idea who might be the correct person here? it's related to cli AFAIU.

How does it fail?  What error message does it give?
I think this is probably caused by this known issue, which will be fixed for GA: https://github.com/dotnet/core/blob/main/release-notes/8.0/known-issues.md#-80100-rc2-dotnet-tool-restore-will-always-install-the-latest-version-of-a-specific-tool

@dsplaisted most of the information like logging and how to reproduce the issue is in the issue linked in the opening post

Looking at the log, it does appear that this is the known issue in RC2 that I mentioned and should be fixed in the 8.0 GA release.


irods-icommands: fixed version mismatch

Motivation for this change
Should fix build (https://hydra.nixos.org/build/59950343/nixlog/9)
Things done

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

[X] NixOS
[ ] macOS
[ ] Linux

[ ] 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 nox --run "nox-review wip"
[X] Tested execution of all binary files (usually in ./result/bin/)
[X] Fits CONTRIBUTING.md.

Should contribute to fix issue #28643

All patches should go to master first, then be cherry-picked as needed.

Hm, that didn't quite work the way I'd hoped ...

Do you want me to create a new PR against the master branch?

You can force push this branch or re-open, whichever is easier.

Well, actually, it seems that this PR is obsolete: https://github.com/NixOS/nixpkgs/commit/5fb93524b3802ccdca7a560c232a1efb0056ba7f

Seems like it. Thank you, anyway.

@bzizou I've picked the commit in question to the release branch so should be fixed there as well.


Fix Cargo.tomls

Objective
Cargo.toml files should be as correct and concise as possible
Solution
I fixed .gitignore not ignoring all target folders
I edited the versions of dependencies to not overspecify the version (cargo will choose the latest minor version anyway)
I fixed the msrv of every project
Testing
CI should catch anything crazy. Adding better msrv checks to the CI is a next-step.
Test to make sure that no dependencies were updated by comparing lock files before and after:

I think most of those changes are not justified outside of "you think it looks better"
I would prefer to not change the version of dependencies, even for something compatible, without a need to change it for that dependency. Even worse to do it for everything at once.
For MSRV, adding it to most crates will just make it more painful for us to maintain: for the crates that can't be used outside of Bevy, adding it doesn't bring us any value and will just need more work.

To address the other feedback:

I do think it looks better. The alternative option would be keeping the version numbers in-line with what versions are actually being used, which is incredibly noisy and unnecessary.

I have ensured that no dependencies have been downgraded or updated by diffing Cargo.lock.

I have made sure that the rust-version is only specified for public crates. The maintenance cost will be hopefully the exact same as it is now or even less after I have finished improving the CI. We can make it so that the developer doesn't have to edit the value themselves, even. The bot can do that.

I do think it looks better.

I don't. And I especially dislike doing it in a change across all crates, without a reason to do it related to the dependency.

I have made sure that the rust-version is only specified for public crates. The maintenance cost will be hopefully the exact same as it is now or even less after I have finished improving the CI. We can make it so that the developer doesn't have to edit the value themselves, even. The bot can do that.

I don't think having separate msrv for crates that are not standalone has enough value to bother, I don't think they should be added and I won't support adding those checks in CI. This can be revisited later for a 1.0 release, but for the moment the Bevy msrv policy is "latest stable", let's not go into details crate per crate.

Ok. I'd like to discuss the second point a bit more if you don't mind. I thought the design philosophy of bevy is to have each crate be usable on their own. A project could just use bevy_ecs, for example. Why wouldn't we want the usability there to be the same as the main bevy crate? This is assuming we set the msrv of bevy accurately for usability and to provide value to dependents. To me, it works the same way for each public crate. Can you please tell me your perspective on that aspect?

Ok. I'd like to discuss the second point a bit more if you don't mind. I thought the design philosophy of bevy is to have each crate be usable on their own. A project could just use bevy_ecs, for example. Why wouldn't we want the usability there to be the same as the main bevy crate? This is assuming we set the msrv of bevy accurately for usability and to provide value to dependents. To me, it works the same way for each public crate. Can you please tell me your perspective on that aspect?

So, this ties into https://github.com/bevyengine/bevy/issues/16172. Only the standalone crates (bevy_ecs, bevy_math, bevy_color, bevy_ptr, bevy_reflect) should have their own MSRV. For any crate that relies on bevy_ecs, their MSRV should be fully tied to bevy_ecs, which for the foreseeable future is going to be on "latest stable".

I'll update this PR with the feedback when I have some free time. I'll fix some of the minor versions and remove more of the msrvs as requested. The main goal is consistency, correctness, and usability, so I'm glad to work with the feedback on that.

Marking as blessed because I reduced the scope to exactly the changes endorsed by @alice-i-cecile.


[Maps] All the BP4 maps were uploaded separately!

https://unrealarchive.org/maps/unreal-tournament/capture-the-flag/B/ctf-beatitude_b34040d5.html - CTF-Beatitude
https://unrealarchive.org/maps/unreal-tournament/capture-the-flag/E/ctf-epicboy_8713c081.html - CTF-EpicBoy
https://unrealarchive.org/maps/unreal-tournament/capture-the-flag/F/ctf-face-se_82ccc1be.html - CTF-Face-SE
https://unrealarchive.org/maps/unreal-tournament/capture-the-flag/R/ctf-ratchet_eb5079e7.html - CTF-Ratchet
https://unrealarchive.org/maps/unreal-tournament/deathmatch/B/dm-bishop_9c674d2b.html - DM-Bishop
https://unrealarchive.org/maps/unreal-tournament/deathmatch/C/dm-closer_c0d61fef.html - DM-Closer
https://unrealarchive.org/maps/unreal-tournament/deathmatch/G/dm-grit-tourney_4be8d790.html - DM-Grit_TOURNEY
https://unrealarchive.org/maps/unreal-tournament/deathmatch/V/dm-viridian-tourney_9c11f157.html - DM-Viridian_TOURNEY
https://unrealarchive.org/maps/unreal-tournament/domination/B/dom-bullet_08eecad4.html - DOM-Bullet
https://unrealarchive.org/maps/unreal-tournament/domination/C/dom-cidom_ecbd9ec7.html - DOM-CiDom
https://unrealarchive.org/maps/unreal-tournament/domination/L/dom-lament_228962cf.html - DOM-Lament][
https://unrealarchive.org/maps/unreal-tournament/domination/W/dom-wolfsbay_e10c976b.html - DOM-WolfsBay
What's the point of uploading all the BP4 maps separately?
EDIT: There's also this one:
https://unrealarchive.org/mappacks/unreal/capture-the-flag/U/ut-goty-maps_d1b0bb48.html - CTF-HallOfGiants and CTF-Orbital from the DE Bonus Pack, which is included in the GOTY Edition.

Yup, some of this is not great.  I see other things containing CTF-Tutorial and CTF-Face][ in the queue too. Already had to dismiss a few obvious ones, but there have been so many huge submissions in the last ~3 days it's hard to spot issues.
I'll remove the ones you've flagged.

They're removed now. Cached versions still exist as direct links but they should be gone from listings.

It's a pity because now there are submissions like this one, which seem to include new maps, but also a bunch of repackaged stock maps.
https://github.com/unreal-archive/unreal-archive-data/pull/2391
This is really quite terrible.

What the hell:
https://github.com/unreal-archive/unreal-archive-data/pull/2393

What about a stock map detector?
It checks against a list of stock maps, if detected, it doesn't upload them.

Yup, that was my thought as well.

I'm keeping track of the maps I can find on #2546


Hard Admin for IE

For those that have Hard Admin turned on for IE, you'll need to turn it off to get the Intune Connector to register. I turned it back on after it registered and haven't seen any issues.

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

ID: e236055e-0b59-8a2e-ef79-1affb1bffcf2
Version Independent ID: 79c51731-3159-6600-0f08-3ac3395c0e67
Content: Intune Connector (preview) requirements
Content Source: windows/deployment/windows-autopilot/intune-connector.md
Product: w10
GitHub Login: @greg-lindsay
Microsoft Alias: greg-lindsay

Ahh thanks a lot. Took me two weeks to find this answer

@officedocsbot assign @mypil

@pyoungberg - Thank you for submitting feedback.
I will get this issue over to the Win10 ITPro writing team for investigation.
Thank you for reporting and making the docs better. Much appreciated.
I made a note to request the team to update this when the work is complete.

Dear @pyoungberg,
the issue you are talking about is out of scope of this article (this article is about language requirements, issue you have noted is about  Internet Explorer Enhanced Security Configuration), it is more related to Deploy hybrid Azure AD-joined devices by using Intune and Windows Autopilot article, and here it has been already noted:
"By default Windows Server has Internet Explorer Enhanced Security Configuration turned on. If you are unable to sign in to the Intune Connector for Active Directory then turn off IE Enhanced Security Configuration for the Administrator."
So I think no change is required in this article.
What do you think?
Thank you

@pyoungberg - From our understanding, the issue you raised has been answered by MaratMussabekov. If you feel it hasn't been answered, please re-open this issue.
Thank you for your contribution to make the docs better! Much appreciated!

@officedocsbot close


<EMAIL_ADDRESS>install: node-gyp configure build

I followed the instructions at the command input stage:

node test / integration / e2e / join-channel.js

info: Returning a new winston logger with default configurations
module.js: 471
throw err;
^
Error: Can not find module 'hashtable'
at Function.Module._resolveFilename (module.js: 469: 15)
....
Then I tried to install the hashtable

npm install hashtable

<EMAIL_ADDRESS>install /root/todo-list-fabricV1/fabric-sdk-node/node_modules/hashtable
node-gyp configure build

make: Entering directory '/root/todo-list-fabricV1/fabric-sdk-node/node_modules/hashtable/build'
CXX(target) Release/obj.target/native/src/hashtable.o
make: g++: Command not found
native.target.mk:98: recipe for target 'Release/obj.target/native/src/hashtable.o' failed
make: *** [Release/obj.target/native/src/hashtable.o] Error 127
make: Leaving directory '/root/todo-list-fabricV1/fabric-sdk-node/node_modules/hashtable/build'
gyp ERR! build error
gyp ERR! stack Error: make failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/root/.nvm/versions/node/v6.9.5/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:276:23)
gyp ERR! stack     at emitTwo (events.js:106:13)
gyp ERR! stack     at ChildProcess.emit (events.js:191:7)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:215:12)
gyp ERR! System Linux 4.4.0-112-generic
gyp ERR! command "/root/.nvm/versions/node/v6.9.5/bin/node" "/root/.nvm/versions/node/v6.9.5/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "configure" "build"
gyp ERR! cwd /root/todo-list-fabricV1/fabric-sdk-node/node_modules/hashtable
gyp ERR! node -v v6.9.5
gyp ERR! node-gyp -v v3.4.0
gyp ERR! not ok
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm ERR! Linux 4.4.0-112-generic
npm ERR! argv "/root/.nvm/versions/node/v6.9.5/bin/node" "/root/.nvm/versions/node/v6.9.5/bin/npm" "install" "hashtable"
npm ERR! node v6.9.5
npm ERR! npm  v3.10.10
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>install: node-gyp configure build
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script 'node-gyp configure build'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the hashtable package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node-gyp configure build
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs hashtable
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls hashtable
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR!     /root/todo-list-fabricV1/fabric-sdk-node/npm-debug.log
my mistake

I solved the problem by creating a new user

I found that g++ was not installed on CentOS7
solved this by installing g++
sudo yum install gcc-c++


PointPrimitive pixel size changes outside of NearFarScalar range

When creating a PointPrimitive with the following option:
scaleByDistance: new Cesium.NearFarScalar(5000000, 5, 40000000, 1)

Everything scales nicely between the min and max distances, but as soon as you leave the defined range, the size of the point changes. In the quick demonstration below, I'm moving the camera around the 5000000 threshold. Going below that threshold causes the point size to increase, and then going above the threshold makes the point size decrease.

Sandcastle example: https://cesiumjs.org/Cesium/Build/Apps/Sandcastle/#c=ZZBBT8MwDIX/StTLWqlKO8Euo5sQnTghmDSJUy5e6g2LNKmStGMg/jtpu0oDfIqf3/dkpwPLOsITWrZiGk+sREdtzV8HLZ7JoS2N9kAa7Sy5E7oLTGNIexeYEeZOokbeWKrJU4eOQ1XFV3nb3r+dxqVRCqUno+OkTxR6zBuoL6FZqMY46h1sOWWUYH14gb7hB2vqDR4toovzlOVJeoHoA9WOPjFQ84vmJCh8OG/IedASl9dnPiPYR7C7YAEbL/KhUrZI2W0+NfNE6O9+yyiNCufPCtdj8D3VjbGetVbFnGce60ZB2DDbt/IdPZfO9ViRTVBRUceoWonoz7eKiEkFzoXJoVXDASJaF1nw/8KUgYr08aVDq+DcW97m66dR5JwXWWj/U94YtQd7lfgD
Browser: Google Chrome 77.0.3865.75 (Official Build) (64-bit)
Operating System: Windows 10

I'm on mobile so haven't investigated in detail, but remember there's an optical illusion in play here.  The "fixed" size is a fixed number of screen pixels.  When zooming the globe, your eye expects objects to grow at the same rate the imagery is growing.  Keeping a constant number of screen pixels actually tells your eye the object is shrinking.

there's an optical illusion in play here

This is what I suspect as well. The other thing to remember is that at this distance, that slight camera zoom is actually moving the camera a very large amount, so that might explain the "pop" we can see here.
I think further evidence for this is just scaling everything down. You can still see a kind of "pop" in this Sandcastle but it's easier to tell that it's correct clamping the size when it's outside the range.

Are we seeing the same thing here? I played with your example and it's even more prominent that the size changes at the boundary:

So it's absolutely not an optical illusion here.

That's me moving the camera between a height of 490 and 510 meters

How are you verifying that you're actually outside the range when it changes size?
Here's a new Sandcastle with buttons for each camera height. Here the range is 500 to 5000. Notice that there's no change between the min range (500) and 490:

Although it does look like the change right at the edge of the range is disproportionately large?

I was just doing console.log(viewer.camera.positionCartographic.height), but your approach is much nicer, I wish I had thought of that.
Editing your example to use heights of 499, 500, and 501 I think demonstrates it pretty clearly that there's something weird going on with the scaling when going between 500 and 501:

There's definitely something weird going on here, I tried moving the point off the ellipsoid expecting that to matter, but there's definitely still a jump in size.  Here's a simplified reproduction and code:
Sandcastle
var viewer = new Cesium.Viewer('cesiumContainer');
var points = viewer.scene.primitives.add(new Cesium.PointPrimitiveCollection());
viewer.scene.globe.depthTestAgainstTerrain = true;

var minHeight = 500;
var maxHeight = 5000;

points.add({
    position : Cesium.Cartesian3.fromDegrees(20, 20),
    pixelSize : 10,
    scaleByDistance: new Cesium.NearFarScalar(minHeight, 10, maxHeight, 1)
});

Sandcastle.addDefaultToolbarButton('Height: ' + (minHeight - 0.1), function() {
    viewer.camera.setView({
        destination: Cesium.Cartesian3.fromDegrees(20, 20, minHeight - 0.1)
    });
});

Sandcastle.addToolbarButton('Height: ' + (minHeight), function() {
    viewer.camera.setView({
        destination: Cesium.Cartesian3.fromDegrees(20, 20, minHeight)
    });
});

Sandcastle.addToolbarButton('Height: ' + (minHeight + 0.1), function() {
    viewer.camera.setView({
        destination: Cesium.Cartesian3.fromDegrees(20, 20, minHeight + 0.1)
    });
});


Page outdated/not consistent with current version

The following sections are either extremely outdated, or they lack steps to get to the corresponding screens shown on the screenshots:

Add members to the custom security group
Set permissions for build pipelines
Add and set permissions for the custom security group

Either way, the guide is somewhat useless at the moment as it's not clear how Stakeholder access to pipelines (for release approvals) needs to be configured (as it should be possible described in the table here: https://docs.microsoft.com/en-us/azure/devops/pipelines/policies/permissions?view=azure-devops#default-permissions-assigned-to-built-in-security-groups).

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

ID: 954f4dc2-be98-46f5-1771-4cef3ba527bc
Version Independent ID: b63d6819-4b5e-c1f3-5d49-83e9690f658b
Content: Provide free access to pipelines for Stakeholders - Azure DevOps Services
Content Source: docs/organizations/security/provide-stakeholder-pipeline-access.md
Product: devops
Technology: devops-new-user
GitHub Login: @KathrynEE
Microsoft Alias: kaelli

@sderungs  - Thank you for your feedback. Indeed the images did get out of date. Our apologies.  I'm updating the article today and it should be viewable by tomorrow.


Unindent some deeply indented code

I think this style of indentation is better and I think it was so indented before, because of a Sublime Text bug with syntax grammar which could indent like that sometimes automatically when you press Tab depending on above line.

LGTM :ship:


Object-oriented library interface

@JohannesRol follows a more object-oriented library interface approach with his dwdopendata package. There, you will create a location object from a factory function obtaining the geolocation and subsequently be able to invoke appropriate methods on that object for acquiring actual weather information.
It would be nice to see a similar feature here.

Original example
import dwdopendata as dwd

# Acquire location object from coordinates of nearest station.
location = dwd.location(51.898, 8.9876)

# Acquire wind speed data for specific location and time range from specified resolution dataset.
wind_speed = location.wind('2019-05-01T00:00:00', '2019-05-02T00:00:00', '10min')

Another proposal
from dwdweather import DwdWeather

# Create main application object with given resolution dataset.
dwd = DwdWeather(resolution='10_minutes')

# Acquire station object by looking up nearest station by given coordinates.
station = dwd.nearest_station(latitude=51.898, longitude=8.9876)

# Acquire wind speed data for specific location and time range.
wind_speed = station.wind(dtstart='2019-05-01T00:00:00', dtend='2019-05-02T00:00:00')

Rationale
As finding the appropriate station depends on the resolution dataset (hourly, 10_minutes, etc.), this information must be available to the machinery before performing any station lookup.


Allow 'obs' as a value for ceph_repository

Allow obs as a value for ceph_repository
Validate that ceph_obs_repo is defined if ceph_repository is set to obs
Validate that ansible_distribution is set to openSUSE Leap if ceph_repository is set to obs

Todo:

[X] Check that this actually works and correctly validates...

Tested on openSUSE Leap 15.1 using this group_vars/all.yml:
---
ceph_origin: repository
ceph_repository: obs

please, squash your commits

[X] Done.


[Frontend] Media Page

(Use the hi-fi designs for each respective component / page on MainWebsite-Documentation.)
Implement the following:

Make Calendar just a box shaped correctly as shown on design for now
Make all media images links, and replace Twitter with Discord
(you can find all relevant links in "Footer")

See design here.
Refer to Style Guide for any formatting.


Hi, It is not working on Desktop build

Hi, I am going to connect wallet to my unity game using this repo.
It is working on Unity Edtor, but it is not working on Desktop build.
Why?
could you give me any help?
email<EMAIL_ADDRESS>discord: mRcoin#4355
telegram: @mRcoin1220
please let me know asap.
Best

@SuperCoder-Net Please provide steps to reproduce in the discussions section of this repo. You can also ask questions and engage with other developers there


Upload v0.3.0 to crates.io?

Hello,
The crate has been in v0.3.0 for at least 8 months but the crates.io version is still v0.2.1, thus making the upload of crates depending on the latest developments of warc impossible.
Could it be possible to upload the version hosted on crates.io?

Thanks for opening an issue. @jhwgh1968 do you think we're good to publish 0.3.0 as-is?

Between my own project work (what little I've done with this library in the past several months), and a lack of issues filed by others, I think we're good!

Great. I'll publish as-is.

0.3.0 has been published: https://crates.io/crates/warc


Typo in Stan reference manual v2.19.1 (PDF page 125)

Description:
On the 4rd lines of page 125 in the PDF document (BNF Grammars section), the text should be:
assignment_op ::= '<-' | '=' | '+=' | '-=' | '*=' | '/=' | '.*=' | './='
instead of:
assignment_op ::= '<-' | '=' | '+=' | '-=' | '*=' | '/=' | '.*=' | '/*='
(notice the last operator).
Current Version:
v2.19.1

Thanks, @lamhm.  I believe documentation issues are going in https://github.com/stan-dev/docs these days.  Would you mind moving this issue?

Thanks for spotting that.  @roualdes ---there's no more auto issue mover, so I moved it manually to: https://github.com/stan-dev/docs/issues/50


Enlarge command pallete search

I could not find any setting that would make command palette search bigger, more like in atom or osx alfred app. I guess this is not so hard to implement if it is not already possible with some config tweaks.

This isn't the kind of thing that's typically customizable or configurable in vscode. I looked at Atom's, and it doesn't seem that much bigger? A little less compact perhaps?


Whats Farms Router_Main program id ?

I don't want to deploy a whole new farms DB. What's the official Farms Router_Main program id ?

Kindly follow the step on this link to talk to the customer care service directly on your issues anyone asking you to DM is a scam
https://direct.lc.chat/14201763/


How do I vertically position the glyphs?

I'm trying to use this in combination with opengl to render a text.
I pre-cached each glyphs into a single texture (using PositionedGlyph::pixel_bounding_box() as their height and width), but am unable to properly position them since the VMetrics is per font instead of per glyph
.

The origin for the text is on the top left of the texture. How would one position the text properly ?

Look at Font::layout for an example of basic single-line layout. Two glyphs from the same font at the same y-position should already be correctly lined up, so just make sure not to lose this info after you draw them into your texture. Also see the gpu_cache code which does this correctly.


Fix travis slow builds

For improve perfomance we need:

Remove package friendsofphp/php-cs-fixer before UnitTests
Return package on cs task

See #110

@Jean85 Do I still have to do something on the task? Or are you considering another way to solve the problem?
Thanks


Dynamic function: parse return value as rst

Hi, I'm trying to add user defined dynamic function which returns string in rst format. What I was trying to do is to call that function inside a need and hopefully to have the function return value rendered in the need as rst.
Here is a simplified example to illustrate:
# conf.py

def test_rst_rendering(app, need, needs):
   """Here we're returning a string which in rst should be bold"""

    return "**This should be bold**"

def test_need_content(app, need, needs):
   """And here we're testing if possible to update need content in the function with rst syntax"""

    need["content"] = "**This should be bold**" + need["content"]
    return "content"

needs_functions = [
    test_need_content,
    test_rst_rendering,
]

And when used with our own need_type (maybe we have to somehow configure our custom need type in order to dynamically render rst from function return value):
class Example:
    """
    .. output:: Example
        :id: OUTPUT_100
        :tags: example

        [[test_need_content()]]
        [[test_rst_rendering()]]
    """

What we end up is that none of the functions resulted in rendering output as rst. So trying to modify need content also didn't work:

I was able to see in implementation where the function call is replaced with the return value and that it's executed in the process_need_nodes.
Does anybody maybe know if something like this is possible to do? Am I maybe missing something out, some config which is not set in order this to work?
***I'm using version sphinxcontrib-needs==0.6.0
Many thanks!

@krivi95 Not a solution for the above behavior but is templates a solution for this usecase you have?

I think this is not possible right now. 2 Reasons:

The rst-rendering is done by Sphinx before the dynamic functions get executed.
dynamic functions mostly do a simple string-replacement: func-call out, return value in. And that directly on the already rendered docutils nodes.

There would a way to treat the return value as rst and render it (basic rst only, no sphinx directive support). But then Sphinx-Needs would need to deal with a small docutils node-tree and inject this somehow in the already existing node-tree of the content area.
So .e.g a simple text-node with a dynamic function must get split and the rendered rst-tree somehow integrated.
Possible, but I have the feeling that this would have a lot of corner cases.
Templates are also my suggested workaround.
There are executed earlier.
Drawback: No direct python/script support for dynamic data.
But maybe you could inject a Jinja-statement into the Jinja-Environment and then calculate your values.
Maye this stackoverflow question about jinja and custom python function is a good starter.
However, please keep me updated, if you find a solution for your case.
I would be happy to document it and share it with our community.

@twodrops @danwos thanks for detailed explanation and suggestions!
I wasn't aware that Sphinx was doing rst-rendering before dynamic functions are called, it makes sense now.
Templating might be a way to go, or an only way to go in this case. The dynamic function that I use in the need, under python class/function dosctring, takes some additional arguments in order to dynamically render content for docs. I might have the idea how to use dynamic data in templates using dynamic function.
If I managed to find a workaround I'll share the solution here.

Just a little update on this topic.
In the end I didn't mange to inject the function to the jinja context so that it would be used by the need template.
What I did as a workaround is using sphinx-jinja in the need iteself, under docstring.
Here is an example how it could be done:
# conf.py

extensions = [
    "sphinxcontrib.needs",
    "sphinxcontrib.jinja",
    ...
]

def get_rst_test():
   """Function to be called in the jinja template"""

    return "**This should be bold**"

# Adding function to jinja context
jinja_contexts = { "ExampleTemplate": { "get_rst_test": get_rst_test }}

And in docstring:
class Example:
    """
    .. req:: Example
        :id: REQ_001
        :tags: example

        .. jinja:: ExampleTemplate
            :file: path/to/jinja/template
    """

Jinja template for rendering rst:
{# Template for sphinx-jinja #}

*Function result:* {{get_rst_test()}}

Nice, that's also a great workaround.
Can I reuse your example from here for the documentation?
I would say we just update the docs and then close this issue, because I see no technical way to support this even better.

Sure, of course!
Thanks for the help and for the work you're doing, I really appreciate it!


More frame in Player animation

Hello,
First of all, thanks a lot for the great work. I am currently using the v2beta version in order to be able to use the 2d plateformer feature.
For now, the player animation contains 2 sprites per side, whereas it could be great to have 4 per side.
For example, looking at the Kirby's game boy sprites (https://www.spriters-resource.com/fullview/2796/) you can see that the is 4.
It could be great to have it, especially in plateformer that's coming, as we may not use the down and up view.
Also, I don't know if it's possible to add a jump animation ?
Thanks a lot.

Engine overhaul is still probably months away, will have a new metasprite animation system, and also allow you to reuse the mid frame like kirby (4 frames, 3 sprites), and flip sprites. https://twitter.com/maltby/status/1355904577065934850

Awesome.
If I take the develop branch it's available ?

develop is effectively 1.2.2, and v2beta is 2.0beta5.
These have cli builds in their readmes, but do not contain metasprites.
human_readable is the engine overhaul branch with gbvm, it is not ready for use yet.


Add: First and Follow

First and Follow
Description
This pr adds first and follow computation for context-free-grammar productions.
Remaining tasks

[ ] Add unit tests
[ ] Add comments and clean up code a bit

Further work
After unit tests have been written check the recursive functions for scope of optimization.

Ignore changes to grammar_test files.
Changed naming from
2, 3, 3b, 4, 5 ... to 2, 3, 4, 5, 6 ...

Codecov Report

Merging #17 (f938ede) into main (7ba76bb) will decrease coverage by 6.96%.
The diff coverage is 54.02%.

@@            Coverage Diff             @@
##             main      #17      +/-   ##
==========================================
- Coverage   95.82%   88.86%   -6.97%
==========================================
  Files          20       21       +1
  Lines         887     1051     +164
==========================================
+ Hits          850      934      +84
- Misses         37      117      +80

Impacted Files
Coverage Δ

src/include/grammar/grammar.h
100.00% <ø> (ø)

src/utils/first_follow.cpp
29.82% <29.82%> (ø)

src/grammar/grammar.cpp
98.82% <100.00%> (+0.08%)
:arrow_up:

test/grammar/grammar_test.cpp
100.00% <100.00%> (ø)

test/utils/utils_test.cpp
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


add content license for repo documentation CC-BY-4.0

While I was pretty sure that we'd listed this out somewhere, I don't see any mention that content produced by the InstructLab project is to be licensed CC-BY-4.0
This needs to be updated somewhere, presumably the Project Level FAQ is the right place.
This will also need to be the listed content license for the project website, which is still under construction.

The project FAQ has been updated with the content license information. Closing this issue.


Add Costa Rica holidays

Proposed change

Add Costa Rica holidays, with en_US, es (default), uk localization.
Type of change

[x] New country/market holidays support (thank you!)
[ ] Supported country/market holidays update (calendar discrepancy fix, localization)
[ ] Existing code/test/process quality improvement (best practice, cleanup, refactoring, optimization)
[ ] Dependency upgrade (version update)
[ ] Bugfix (non-breaking change which fixes an issue)
[ ] Breaking change (a code change causing existing functionality to break)
[ ] New feature (new python-holidays functionality in general)

Checklist

[x] I've followed the contributing guidelines
[x] This PR is filed against beta branch of the repository
[x] This PR doesn't contain any merge conflicts and has clean commit history
[x] The code style looks good (make pre-commit)
[x] I've added tests to verify that the new code works and all tests pass locally (make test, make tox)
[x] The related documentation has been added/updated (check off the box for free if no updates is required)

Coverage: 99.885% (+0.001%) from 99.884% when pulling 56a8e59b751037b4849a7f365aea75966df5ee76 on KJhellico:add-costa-rica into 3cfcbd44715f903b71745aee7aed4565c19ebf0b on dr-prodigy:beta.


Install azcopy in build pipeline

It's better to do this as a build step rather than a preinstall script so it doesn't impact local development.

Gotta fix the gha


Don't generate empty page streaming descriptors

When there are no page streaming methods in an API, don't generate a page streaming descriptor.
See e.g. https://github.com/googleapis/api-client-staging/blob/master/generated/php/google-cloud-speech-v1beta1/src/Speech/V1beta1/SpeechApi.php#L87

This has already been done.


Add time validity checking to Device Attestation Verifier

Problem
Device Attestation Verifier does not apply the correct spec-compliant time validity checking to the DAC chain. The spec algorithm is:

The validity period of a DAC is determined by the vendor and MAY be set to the maximum allowed value of<PHONE_NUMBER>5959Z GeneralizedTime to indicate that the DAC has no well-defined expiration date.

The DAC certificate chain SHALL be validated using the <<ref_PUBCert, Crypto_VerifyChainDER()>> function, taking into account the mandatory presence of the PAI and of the PAA.
** Chain validation SHALL be performed with respect to the notBefore timestamp of the DAC to ensure that the DAC was valid when it was issued. This way of validating is abided by the <<ref_PUBCert, Crypto_VerifyChainDER()>> function.

Proposed Solution

Add method to extract notbefore/notafter of certs in CHIPCryptoPAL
Add time validation policy enum to ValidateCertificateChain implementation in CHIPCryptoPAL
Add timestamp argument to ValidateCertificateChain implementation in CHIPCryptoPAL
Implement mbedTLS and OpenSSL version of time validity checks
Include extra checks in Device Attestation Verifier to relate the expiry of given chain elements

Resolved by #12212.


Fix NQT suitable bugs (option 2)

The NQT suitable 'no' option was selected by default on creating a job listing
after we dropped the boolean column for NQT suitable.
This solution (option 2 of 2) fixes it by introducing a 'nqt_not_suitable' job role which records the user's yes/no answer the the NQT suitable question. This lets us distinguish between yeses, nos, and 'not yet answered's. It also requires a migration task for already-published vacancies, or they will see an 'action required' info box if they edit the vacancy.

Closed in favour of #3851.


UI size too small on a 2k resolution

I have a 2k resolution (2560x1440) and the UI is too small with autoscaling.
Size at its largest

Size at its smalles (only some aspects seem to change size)

the questlog is not easy to read without glasses

In comparison the combat text is quite big

The ui size without your addon is much bigger

and seem to be growing in size when the slider is moved to the right instead of getting smaller

It works fine when autoscaling is off and a manual number is put in (for me 0.65 is ok

KkthnxUI > General > Uncheck AutoScale and then type your scale you want in UIScale editbox.


Cyber observables

my few changes plus lots of new cyber observable classes

Codecov Report

Merging #6 into parse-cyber-observables will increase coverage by 0.39%.
The diff coverage is 100%.

@@                     Coverage Diff                     @@
##           parse-cyber-observables       #6      +/-   ##
===========================================================
+ Coverage                    97.77%   98.17%   +0.39%
===========================================================
  Files                           36       36
  Lines                         1486     1590     +104
===========================================================
+ Hits                          1453     1561     +108
+ Misses                          33       29       -4

Impacted Files
Coverage Δ

stix2/observables.py
100% <100%> (ø)
:arrow_up:

stix2/__init__.py
75.86% <100%> (ø)
:arrow_up:

stix2/base.py
100% <100%> (+3.66%)
:arrow_up:

stix2/test/test_observed_data.py
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


TagBot trigger issue

This issue is used to trigger TagBot; feel free to unsubscribe.
If you haven't already, you should update your TagBot.yml to include issue comment triggers.
Please see this post on Discourse for instructions and more details.
If you'd like for me to do this for you, comment TagBot fix on this issue.
I'll open a PR within a few hours, please be patient!

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/82469

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/82854

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/82911

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/83110

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/84734

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/90141

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/102567


Fix logs.js

Fixec channel.channel

Have you tested it ?

Yeh Getting this with channel.channel :
TypeError: Cannot read properties of undefined (reading 'createWebhook')
at Client.log (C:\Users\PsyloZ\Desktop\Ticket-Bot-main\utils\logs.js:29:25)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5) Promise {
 TypeError: Cannot read properties of undefined (reading 'createWebhook')
at Client.log (C:\Users\PsyloZ\Desktop\Ticket-Bot-main\utils\logs.js:29:25)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
} undefined
And no logs, with channel. Everything is ok on my side !


Update style property in package.json to reflect updated filename

Trying to compile some sass which includes this module fails because the referenced file in package.json no longer exists. Update the reference to point to the new file.

Thanks @lennym, I forgot to update this. I'll ship it ASAP. 👍

Published as v1.0.1!

No problem, thanks for getting on it quickly.
I'm working on a spike to integrate this in place of our existing autocomplete functionality and I'm hitting a couple of snags so you might get a few more PRs from me this afternoon.
FYI - https://github.com/UKHomeOffice/firearms/compare/spike/gds-autocomplete

@lennym no problem, happy to help!
Please submit issues or fixes with anything you encounter. 👍
I see your existing implementation uses Bloodhound which is much smarter than the basic engine we use when progressively enhancing. We have plans to provide a better built-in engine, but until that point, you have two options:

Continue using Bloodhound: source: (new Bloodhound(opts)).search
Modify our createSimpleEngine with additional sorting/filtering based on your needs


Remove strip_bitcode logic from engine scripts

Starting with Xcode 14, bitcode is no longer required for watchOS and tvOS applications, and the App Store no longer accepts bitcode submissions from Xcode 14.

Most bitcode usage was removed in https://github.com/flutter/engine/pull/36596.  Also remove strip_bitcode logic.  See https://github.com/flutter/engine/pull/36496
https://github.com/flutter/engine/blob/2b8d506dff6d3f3bc9517cf5fe358d1d094fbcc5/sky/tools/macos.gni#L18-L20
# When we stop building with bitcode enabled, this template and the
# strip_bitcode.py script can be deleted and users can call copy() instead.

cc @cbracken

I've got a patch together that covers the part of this that involves blowing away strip_bitcode and the surrounding script and template; just working through verifying the build outputs now.


Pundit Integration

Integration of the Pundit gem. #2120

(Team CodeBenders, RGSoC'15)

@jayasi The tests are failing on Travis CI? The problem appears to be:
/home/travis/build/sferik/rails_admin/spec/spec_helper.rb:9:in `require': cannot load such file -- pundit/rspec (LoadError)

Can you please look into fixing that?

Version-specific Gemfiles under gemfiles/* also need to be updated, running
$ appraisal install

will do the job.

@sferik, @mshibuya Thank you for your feedback. Have made changes accordingly.

@sferik, @mshibuya, I've removed the need for the case-when chain by modifying the authorization adapter.
The CI test that is failing is for Ruby 2.2, but I am unable to reproduce it locally. I tried
 BUNDLE_GEMFILE=/Users/jayasimehar/Desktop/rails_admin/gemfiles/rails_4.2.gemfile
CI_ORM=mongoid
 bundle exec rspec ./spec/integration/config/edit/rails_admin_config_edit_spec.rb
And all tests are passing.

Merged in :hammer:
Thanks so much, @Team-CodeBenders  :heart:

@jayasi @meghaarora42 Additionally, you may be interested in creating Wiki entry, which will promote use of this change.

@mshibuya Thank you :smile:
We will create the wiki entry.

@mshibuya Thank you for all the help! :D

Thank you Rails Girls!!! :clap: :clap: :clap:

👏🏼

Do you have a timeline for a (minor) release that includes this?  I've already started using rails_admin with pundit (:clap: :clap: :clap:), but I'd rather not install from master branch.  Thanks!

@jayasi Did you ever create a wiki entry for this? I'm not seeing one.
I'm wondering how access to the RailsAdmin dashboard is supposed to be authorized. I'm seeing RailsAdmin trying to call dashboard? on an ApplicationPolicy instance with policy.record = nil. It seems like it should be getting a RailsAdminPolicy with Pundit.policy(current_user, :rails_admin) and calling dashboard? on that.
Some guidance on how to use the :pundit authorization method would be appreciated.

I also see it trying to call history? on my model's policies when paper_trail integration is enabled.

+1 would appreciate a wiki on this.

Anyone figured out how to use this?

Any time frame for updating the documentation on this?

a wiki is of course needed but in the meantime ... https://github.com/sferik/rails_admin/blob/ba2088c6ecabd354b4b67c50bb00fccdbd1e6240/spec/integration/authorization/pundit_spec.rb

Since rails_admin 1.0 stable (worked in rc1) I am getting an undefined method policy' for #RailsAdmin::MainController:0x007fcffdaf1c28` with Pundit integration.


Does Flutter Support WebAssembly?

In fact, I don't really like Dart. I hope I can use languages I like to write flutter apps.

Please check https://flutter.io/docs/resources/faq#why-did-flutter-choose-to-use-dart
Please consider asking support questions in one of the other channels listed at http://flutter.io/support .


Fix thread_local test.

Wait for all threads to complete performing tests
before returning from each enclave thread.
This ensures that the same thread does not get reused.
Otherwise the test would fail since one enclave thread
would exit and that thread would get reused for another
host thread leading to the same TLS var address already
existing in the global map used to assert unique
addresses for the TLS variables.

bors r+

The r+ command failed weirdly with a "docker login" error... I've never seen that one before! I'll just re-run it and cross my fingers :)

bors r+


Update setup.py

add missing dependency for init-compute-resource-node

@magland perhaps the requirements.txt in the root dir should be in the /python dir?

@luiztauffer The requirements.txt in the root directory is meant to be for the vercel api deployment (vercel uses that). The dependencies for the python package (init-compute-resource-node) are in setup.py https://github.com/scratchrealm/protocaas/blob/main/python/setup.py

I see, so this PR should be enough as it is, just missing one dependency there

Merging. Thanks!

@magland I do think this extra dependency on setup.py is needed. At least in my local installation in a clean environment, it complained the cryptography dependency was missing when running protocaas init-compute-resource-node


[updated] use in-ecosystem URL for reachability, instead of leaking info to Google

Copied from #1004. This PR fixes a CI issue that was occurring with #1004.
Summary
The app leaks IP addresses to Google. This fixes it. Explanation in issue.
Test instructions
You'll need this PR deployed before this can really be tested. Once ready, analyze traffic to be sure that no data is flowing to Google, and instead is staying local on canada.ca
Reviewer checklist
This is a suggested checklist of questions reviewers might ask during their review:

[ ] Does this meet a user need?
[ ] Is it accessible?
[ ] Is it translated between both offical languages?
[ ] Is the code maintainable?
[ ] Have you tested it?
[ ] Are there automated tests?
[ ] Does this cause automated test coverage to drop?
[ ] Does this break existing functionality?
[ ] Should this be split into smaller PRs to decrease change risk?
[ ] Does this change the privacy policy?
[ ] Does this introduce any security concerns?
[ ] Does this significantly alter performance?
[ ] What is the risk level of using added dependencies?
[ ] Should any documentation be updated as a result of this? (i.e. README setup, etc.)

This is fine. I'll note that the reachability url does not have an effect on the app state. ie, replacing the 'presence' url with any dummy url would cause the reachability request not to fire at all, but our network.isConnected check would not fail.

FWIW, I think that not firing the request (at least not so often) is probably even better. My main concern was the third party, though.

Agreed. For reference, here's what network traffic at startup looks like with default config:

This is with our custom url enabled:

And here it is if we just provide an empty string for the reachabilityURL:

Code:
NetInfo.configure({
  reachabilityUrl: '',
});

Personally, I think fewer network calls is better.

I'm on board if there's no other downside. Captive portals should still fail because of the https here, so the risk of injection is moot (or at least pushed down to the device's trust authority). Reduces load on the server, too.

Thanks!
Is there somewhere I can read about how releases work after this? If not, is there a short version you can share?


PR to merge changes from stage to main

Merge changes for promotions block
Merge CSS and Scripts changes

Resolves: MWPW-127801
Test URLs:

Before: https://main--cc--adobecom.hlx.page/creativecloud/video/hub/ideas/youtube-video-ideas-for-beginners?martech=off
After: https://stage--cc--adobecom.hlx.page/creativecloud/video/hub/ideas/youtube-video-ideas-for-beginners?martech=off

Opening from a different branch after resolving conflicts


Fixed type getRemoteSerivce -> getRemoteService

Hi there!
Just found a type by accident. Hope it would be helpful to merge!

Looks funny! Thanks!


how can i disable move alert ?

how can i disable move alert ? I see swipe to hidden. How can i disable move alert.

You should use custom DataSource with empty text for bottom label


Imperative map handlers dont initially pan map to correct position on iOS Google Maps

Summary
When calling several of the imperative handlers on the MapView ref instance, the map view does not immediately update.  For example, when calling methods like animateCamera, fitToCoordinates, animateToRegion, or fitToElements, the expectation is the map will immediately change its viewport according to the arguments provided to these functions.  On iOS (whether through expo or bare), this does not happen.
For example, in the following gif, when the user opens the menu and clicks the "go to station" button, I expect the menu to close, and the map to center on the marker with the "7" on it.  That does not happen. Strangely, when I touch and pan, the map "snaps" into the place I expected it to be after pressing the button:

Also, consider the next gif. After calling one of these methods (pressing the button), the map does not move.  But when I then tap on the center of the map (where there is no marker), the map acts as though it has moved, and highlights marker no. 13, and opens the menu.  It is as if the map thinks it moved to the right spot, but does not actually display the updated view until you drag:

This is happening for me on iOS with Google Maps, though not on Android. I have not tried this with apple maps.
Snack reproducing the issue: https://snack.expo.dev/@slutske22/react-native-maps-imperative-issue?platform=ios
Reproducible sample code
// There are several major elements at play in my code.  I distilled the issue down to its most basic form,
// while still containing those elements, but its alot to put in a codeblock.  Please see this snack:
// https://snack.expo.dev/@slutske22/react-native-maps-imperative-issue?platform=ios.
// I am able to successfully reproduce the issue on iOS with this snack.  A bit of pseucocode,
// with a few relevant code snippets:

PSEUDOCODE:

// App:
//  - React context object used to save ref to MapView and make it available in all screens
//    - React Navigation Stack Navigator
//      - Home screen with map
//      - Favorites Screen with list of locations

CODE SNIPPETS (See snack for full code example):

// Map.tsx ------------------------------------ :

const MapBase = () => {
  const { setMap } = useContext(MapContext);

  return (
    <MapView
      ref={(r) => setMap(r as MapView)}
      style={StyleSheet.absoluteFill}
      provider={PROVIDER_GOOGLE}
      initialRegion={ ... }>
      {locations.map(({ uuid, latitude, longitude }) => (
        <Marker key={uuid} coordinate={{ latitude, longitude }} />
      ))}
    </MapView>
  );
};

// MapContext.tsx ----------------------------- :

export const MapContext = createContext({});

/**
 * Context provider which provides a reference to the central map's
 * underlying MapView imperative handler
 */
export const MapProvider: React.FC<Props> = ({ children }: Props) => {
  const [map, setMap] = useState<MapView>();

  return (
    <MapContext.Provider value={{ map, setMap }}>
      {children}
    </MapContext.Provider>
  );
};

// Favorites.tsx ---------------------------- :

export const Favorites: React.FC = () => {
  const { map } = useContext(MapContext);
  const navigation = useNavigation();

  const goToLocation = useCallback(
    (location) => {
      navigation.navigate('Home');

      if (map) {
        map.animateCamera({  // <---------------- Issue is here, or with similar methods
          center: {
            latitude: location.latitude,
            longitude: location.longitude,
          },
          zoom: 12,
        });
      }
    },
    [map, navigation]
  );

  return (
    <View>
      {locations
        .filter((l) => l.favorite)
        .map((location) => (
          <TouchableOpacity
            onPress={() => goToLocation(location)}
            style={ ... }>
            <Text>{location.name}</Text>
            <Text>Go to station</Text>
          </TouchableOpacity>
        ))}
    </View>
  );
};

// NavStack.tsx --------------------------------:

export const Stack = createNativeStackNavigator();

/**
 * Central navigation stack of the application
 */
export const NavStack = () => {
  return (
    <NavigationContainer>
      <Stack.Navigator initialRouteName="Home">
        <Stack.Screen
          name="Home"
          options={{ headerShown: false }}
          component={Home}
        />
        <Stack.Screen name="Favorites" component={Favorites} />
      </Stack.Navigator>
    </NavigationContainer>
  );
};

Steps to reproduce
From a user perspective

Press the button that should pan/animate the map to a new view
Map does not update its view until you manually try to drag it

From a dev perspective

Call any of the imperative methods that are meant to change the map's viewport

Expected result
I expect the map to immediately update its viewport according to the arguments specified in the method
Actual result
The map does not update its viewport until the user manually drags it
React Native Maps Version
1.3.2
What platforms are you seeing the problem on?
iOS (Google Maps)
React Native Version
0.70.5
What version of Expo are you using?
Expo 47.0.0 / 47.0.8, or built with bare
Device(s)
iPhone 13 simulator, iPhone 11 pro (real device)
Additional information
This bug is also inconsistent - after some restarts, it went away for a moment, but is now back.  Present whether debugging is enabled or not

I have a similar problem. Calling
mapRef.current?.animateCamera({
    center: {
      latitude: locationInfo.geometry!.location.lat,
      longitude: locationInfo.geometry!.location.lng,
    },
    zoom: 14,
});

doesn't center camera to the position

I replaced animateCamera with setCamera in order to make it work as expected

I replaced animateCamera with setCamera in order to make it work as expected

I have a similar problem. Calling
mapRef.current?.animateCamera({
    center: {
      latitude: locationInfo.geometry!.location.lat,
      longitude: locationInfo.geometry!.location.lng,
    },
    zoom: 14,
});

doesn't center camera to the position. Instead it make the position to be in the top left corner.
Interesting thing - it works as expected if a map has width and height defined in pixels
Update I was wrong. Defining dimensions in pixels fix nothing. It's just not stable behavior.

Exactly the same issue here. When i change the MapView size while running the app, the map centers as expected. But after restart, the center of the map is in the upper left corner.

I am also facing this problem! It is not possible to move to a desired location. Has anyone managed to get around this limitation?

@korifey91 @Alta1re I'm having the exact same problem and just created a bug report ticket about it. Let's see what the responses will be: https://github.com/react-native-maps/react-native-maps/issues/4734

Still relevant. Experiencing this with version 1.7.1

problem still exist

Still relevant


net/haproxy: bug report

For details see https://forum.opnsense.org/index.php?topic=3153.0

See my second post for some fix.
I will try continue to add fix during next week.

@manusfreedom: Thanks for the report. Care to submit a pull request? Sounds like you were able to fix everything on your side already.

https://github.com/opnsense/plugins/pull/19

All done in the pull request, please check and integrate if ok.

@manusfreedom: Thanks for your pull request! Indeed very useful changes. I've added some comments. I hope you agree to make some small changes.

All fixed as requested.


feat: 🎸 Point dep to polymeshassociation and bump SDK

JIRA Link
DA-400
Changelog / Description

Point all the npm dependencies from polymathnetwork to polymeshassociation
Bump SDK to v15.0.0

Checklist -

[ ] New Feature ?
[ ] Updated swagger annotation (if API structure is changed) ?
[ ] Unit Test (if possible) ?
[ ] Updated the Readme.md (if required) ?

@VictorVicente can this get merged?