Question: How to retrieve the reason for an Authorization Policy Failure?

.Net Core 2.0
Take https://github.com/blowdart/AspNetAuthorizationWorkshop/tree/core2
and consider the case where the user has claims, but no Administrator Claim, in which case he is redirected to the Forbidden View when he hits [Authorize(Policy = "AdministratorOnly")]
. Is there a way I can retrieve in the forbidden view (or elsewhere) the reason why he has been redirected, i.e.
"You do not satisfy the AdminsitratorOnly policy"
or even more precise in the case this policy has several requirements
"You are not an Admin". ?

In 2.0, IAuthorizationService.Authorize was changed to return https://github.com/aspnet/Security/blob/rel/2.0.0/src/Microsoft.AspNetCore.Authorization/AuthorizationResult.cs instead of only a bool, when a failure occurs the Failure contains the failed requirements or if Fail() was called, but you will need to explicit authorization (use the service in the controller action manually) (as opposed to using [Authorize]) to look at the errors.

cc @blowdart @scottaddie we should add this to the docs somewhere as this was a commonly asked for scenario that we enabled in 2.0

.@Haok, do you have some code where I can check out explicit injection of the service with check ups for Fail etc?

Sure you can look at https://docs.microsoft.com/en-us/aspnet/core/security/authorization/resourcebased?tabs=aspnetcore2x
I believe the docs for 2.0 are being updated still, the 2.0 PR is here: https://github.com/aspnet/Docs/pull/4715#discussion_r149468638
Right now there's no example code around using the new failures, but basically its up to you to generate the appropriate error message based on the failed requirements. So I'd imagine you could just write a helper method that generates the appropriate error message to display for a given list of failed requirements.

I saw this page already but thought that was for resource based stuff, whereas you seem to say the IAuthorizationService.Authorize can be used beyond this .

@HaoK per our discussion, can you add this to the discussion about auth improvements and then close this bug as a dup of it?

Linked to #1359 and will be tracked as part of that


Rename AliasTuple to Pack

See forum discussion<EMAIL_ADDRESS>I propose Pack, which is inspired by C++'s Parameter Pack.
From the description:

A template parameter pack is a template parameter that accepts zero or more template arguments (non-types, types, or templates). A function parameter pack is a function parameter that accepts zero or more function arguments.
A template with at least one parameter pack is called a variadic template.

Given that that D has its roots in C++ and this construct is similar to the one in question, it seems like a good fit.
I prefer Pack over AliasPack or other variations because it's more general and allows us to be more specific in the future with TypePack, ExpressionPack, AliasPack, etc... later.
FYI: There was already a private template in std/meta.d named Pack explained as "Confines an alias tuple within a template", so I renamed it to Confine.  Sorry if that makes things more difficult to review.

Personally I'm not too opposed to it, but given the auto-expanding behaviour, and the fact that according to @deadalnix it was a major cause for confusion, there might be problems with this, because "pack" might potentially be interpreted as implying not auto-expanding. But personally I wouldn't necessarily interpret it this way, and it's as good as "tuple" for me, and way better than "seq(uence)".
In any case, please don't merge this one prematurely.

lgtm

Why did you close this? There was considerable support for this, also on the news group.

Why did you close this?

Because of this<EMAIL_ADDRESS>Here's how I see the governance in this community - There are only two opinions that matter: Walter's and Andrei's.  All other opinions are simply attempts to influence those two.  Once one of those two have made a call, everything else is futile.

There was considerable support for this, also on the news group.

Are we looking at the same thread? :-P  I didn't see much support.  Most chose not to voice any opinion at all for fear of being belittled as a "bikeshedder".


Alternative using NoShow

See discussion in #123

Looks like you based this on an outdated branch. I think you'll need to rebase.

Wait I didn't look at this probably, do we need a new typeclass here?
Can't we just have:
instance Show (NoShow a) where
  show x = unsafeStringify x

Closing this in favour of #125 that includes your comments.


Parse String using toDate(formatString: ) is incorrect

The example in README let date = "22/01/2015".toDate(formatString: "DD/MM/YYYY") will parse to Optional(2014-12-20 16:00:00 +0000)

According to Apple date formatting doc (you can see at the bottom of the readme file) day should be "dd" not "DD".

I found out already, it should be dd/MM/yyyy in order to parse correctly.
Please correct this in README.
Thanks.

Just fixed, thank you


[Autocomplete] Adds sx prop to ListboxProps

closes : https://github.com/mui/material-ui/issues/36214
before: https://codesandbox.io/s/confident-worker-5ek4x8
after: https://codesandbox.io/s/friendly-montalcini-lt0s57?file=/demo.tsx

[x] I have followed (at least) the PR section of the contributing guide.

Should we apply the same fix in Joy UI's Autocomplete?

@mnajdova In joy Autocomplete sx prop is added to listbox hence i didn't added.


WASM file size and lighter rive engine

Hi,
preloading the wasm file is great since it allow getting everything setup before users see animations. However, the file size is quite large and can have an impact on infrastructure (the file is 196 KB).
It would be great to see some size trimming on the wasm file to speed loading and reduce impact on infra. It could also be great to have a rive-lite.wasm engine that have a reduce set of features (state machines for examples) to avoid loading the whole file but a smaller one with less feature.
Is there some plan to reduce the file size or offer a slimmer version?

Hi @flavienbonvin ! The WASM file that gets built is already optimized for small size (especially using the canvas variant), but the bulk of the size comes from the bindings to JS from CPP (you can see in wasm/src/bindings.cpp most of the bindings to JS classes/methods/properties). We try to keep bindings down to a minimum and as-needed basis. Because a "lite" version would be hard to predict for a general user's needs, it'd be tricky to come up with an even lighter version for a WASM build.
However, what you can experiment with is forking this repo, and removing bindings you don't need for your own project. For example:

If you don't use LinearAnimations (you just use State Machines), you can remove the LinearAnimation binding
If you don't use the low-level runtimes or you don't need to track certain nodes in the Rive draw hierarchy, or bones, you can remove the Node and Bone (and RootBone) classes
If you reference state machines by name only (and not index), you can remove this function binding

It might shave off some kB to help lessen the impact


Ogre2.2 errors when launching ign gazebo

Environment

OS Version: Ubuntu 20.04
Source or binary build?

Source, main branch, commit: 7def756623029ef168cf159147d4df39e702ae3b
If this is a GUI or sensor rendering bug, describe your GPU and rendering system. Otherwise delete this section.

Rendering plugin: ogre2.2

[X] GUI rendering error.

When running ign gazebo -v 4 shapes.sdf, the following errors appear:
[GUI] [Msg] Loading plugin [ignition-rendering-ogre2]
[GUI] [Err] [Ogre2RenderEngine.cc:319] Failed to initialize render-engine
[GUI] [Dbg] [RenderUtil.cc:2267] Create scene [scene]
[GUI] [Err] [BaseRenderEngine.cc:215] Render-engine has not been initialized
[GUI] [Err] [MarkerManager.cc:156] Scene pointer is invalid
[GUI] [Err] [Scene3D.cc:2546] Unable to initialize renderer
[GUI] [Msg] Loading plugin [ignition-rendering-ogre2]
[GUI] [Wrn] [BaseRenderEngine.cc:42] Render-engine has already been loaded
[GUI] [Dbg] [RenderUtil.cc:2267] Create scene [scene]
Error at line 57: @piece 'FresnelSwizzle' already definedError at line 16: @piece 'getSpecularFresnel' already definedError at line 6: @piece 'NormalNonPremul' already definedError at line 6: @piece 'detail_swizzle0' already definedError at line 57: @piece 'FresnelSwizzle' already definedError at line 102: @piece 'FresnelSwizzle' already definedError at line 14: @piece 'getSpecularFresnel' already definedError at line 5: @piece 'NormalNonPremul' already definedError at line 6: @piece 'detail_swizzle0' already definedError at line 102: @piece 'FresnelSwizzle' already definedError at line 8: @piece 'SampleSpecularMap' already definedError at line 102: @piece 'FresnelSwizzle' already definedError at line 14: @piece 'getSpecularFresnel' already definedError at line 5: @piece 'NormalNonPremul' already definedError at line 6: @piece 'detail_swizzle0' already definedError at line 102: @piece 'FresnelSwizzle' already definedError at line 8: @piece 'SampleSpecularMap' already defined
[GUI] [Msg] Loading plugin [ignition-rendering-ogre2]

Rendering system info:

Rendering system info:

LANG=C lspci -nn | grep VGA
### Output
05:00.0 VGA compatible controller [0300]: NVIDIA Corporation TU116 [GeForce GTX 1660 SUPER] [10de:21c4] (rev a1)

echo "$DISPLAY"
### Output
:1

LANG=C glxinfo -B | grep -i '\(direct rendering\|opengl\|profile\)'
### Output
direct rendering: Yes
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: GeForce GTX 1660 SUPER/PCIe/SSE2
OpenGL core profile version string: 4.6.0 NVIDIA 460.91.03
OpenGL core profile shading language version string: 4.60 NVIDIA
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL version string: 4.6.0 NVIDIA 460.91.03
OpenGL shading language version string: 4.60 NVIDIA
OpenGL context flags: (none)
OpenGL profile mask: (none)
OpenGL ES profile version string: OpenGL ES 3.2 NVIDIA 460.91.03
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20

ps aux | grep Xorg
### Output
root        1345  0.0  0.1<PHONE_NUMBER>6 tty1     Sl+  08:24   0:02 /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/125/gdm/Xauthority -background none -noreset -keeptty -verbose 3
root        2923  2.1  0.2<PHONE_NUMBER>6 tty2     Sl+  08:27  10:09 /usr/lib/xorg/Xorg vt2 -displayfd 3 -auth /run/user/1000/gdm/Xauthority -background none -noreset -keeptty -verbose 3
osrf      105452  0.0  0.0   9040  2428 pts/4    S+   16:28   0:00 grep --color=auto --exclude-dir=.bzr --exclude-dir=CVS --exclude-dir=.git --exclude-dir=.hg --exclude-dir=.svn --exclude-dir=.idea --exclude-dir=.tox Xorg

sudo env LANG=C X -version
### Output
X.Org X Server 1.20.11
X Protocol Version 11, Revision 0
Build Operating System: linux Ubuntu
Current Operating System: Linux osrf-MS-7885 5.11.0-34-generic #36~20.04.1-Ubuntu SMP Fri Aug 27 08:06:32 UTC 2021 x86_64
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic root=UUID=5f4a51f9-a8a6-41f8-8317-6d55c97f96e9 ro quiet splash vt.handoff=7
Build Date: 06 July 2021  10:17:51AM
xorg-server 2:1.20.11-1ubuntu1~20.04.2 (For technical support please see http://www.ubuntu.com/support)
Current version of pixman: 0.38.4
	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.

ogre2.log
16:17:00: Creating resource group General
16:17:00: Creating resource group Internal
16:17:00: Creating resource group Autodetect
16:17:00: SceneManagerFactory for type 'DefaultSceneManager' registered.
16:17:00: Registering ResourceManager for type Material
16:17:00: Registering ResourceManager for type Mesh
16:17:00: Registering ResourceManager for type Mesh2
16:17:00: Registering ResourceManager for type OldSkeleton
16:17:00: MovableObjectFactory for type 'ParticleSystem' registered.
16:17:00: ArchiveFactory for archive type FileSystem registered.
16:17:00: ArchiveFactory for archive type Zip registered.
16:17:00: ArchiveFactory for archive type EmbeddedZip registered.
16:17:00: DDS codec registering
16:17:00: FreeImage version: 3.18.0
16:17:00: This program uses FreeImage, a free, open source image library supporting all common bitmap formats. See http://freeimage.sourceforge.net for details
16:17:00: Supported formats: bmp,ico,jpg,jif,jpeg,jpe,jng,koa,iff,lbm,mng,pbm,pbm,pcd,pcx,pgm,pgm,png,ppm,ppm,ras,tga,targa,tif,tiff,wap,wbmp,wbm,psd,psb,cut,xbm,xpm,gif,hdr,g3,sgi,rgb,rgba,bw,exr,j2k,j2c,jp2,pfm,pct,pict,pic,3fr,arw,bay,bmq,cap,cine,cr2,crw,cs1,dc2,dcr,drf,dsc,dng,erf,fff,ia,iiq,k25,kc2,kdc,mdc,mef,mos,mrw,nef,nrw,orf,pef,ptx,pxn,qtk,raf,raw,rdc,rw2,rwl,rwz,sr2,srf,srw,sti,x3f,webp,jxr,wdp,hdp
16:17:00: OITD codec registering
16:17:00: Registering ResourceManager for type HighLevelGpuProgram
16:17:00: MovableObjectFactory for type 'Decal' registered.
16:17:00: MovableObjectFactory for type 'InternalCubemapProbe' registered.
16:17:00: MovableObjectFactory for type 'Entity' registered.
16:17:00: MovableObjectFactory for type 'Item' registered.
16:17:00: MovableObjectFactory for type 'Light' registered.
16:17:00: MovableObjectFactory for type 'Rectangle2Dv2' registered.
16:17:00: MovableObjectFactory for type 'BillboardSet' registered.
16:17:00: MovableObjectFactory for type 'ManualObject2' registered.
16:17:00: MovableObjectFactory for type 'BillboardChain' registered.
16:17:00: MovableObjectFactory for type 'RibbonTrail' registered.
16:17:00: MovableObjectFactory for type 'WireAabb' registered.
16:17:00: --* OGRE Initialising
16:17:00: --* Version 2.2.6 (Cerberus)
16:17:00: OverlayElementFactory for type Panel registered.
16:17:00: OverlayElementFactory for type BorderPanel registered.
16:17:00: OverlayElementFactory for type TextArea registered.
16:17:00: Registering ResourceManager for type Font
16:17:00: Loading library /usr/lib/x86_64-linux-gnu/OGRE-2.2/OGRE/RenderSystem_GL3Plus.so
16:17:00: Installing plugin: GL 3+ RenderSystem
16:17:00: OpenGL 3+ Rendering Subsystem created.
16:17:00: Plugin successfully installed
16:17:00: Loading library /usr/lib/x86_64-linux-gnu/OGRE-2.2/OGRE/Plugin_ParticleFX.so
16:17:00: Installing plugin: ParticleFX
16:17:00: Particle Emitter Type 'Point' registered
16:17:00: Particle Emitter Type 'Box' registered
16:17:00: Particle Emitter Type 'Ellipsoid' registered
16:17:00: Particle Emitter Type 'Cylinder' registered
16:17:00: Particle Emitter Type 'Ring' registered
16:17:00: Particle Emitter Type 'HollowEllipsoid' registered
16:17:00: Particle Affector Type 'LinearForce' registered
16:17:00: Particle Affector Type 'ColourFader' registered
16:17:00: Particle Affector Type 'ColourFader2' registered
16:17:00: Particle Affector Type 'ColourImage' registered
16:17:00: Particle Affector Type 'ColourInterpolator' registered
16:17:00: Particle Affector Type 'Scaler' registered
16:17:00: Particle Affector Type 'Rotator' registered
16:17:00: Particle Affector Type 'DirectionRandomiser' registered
16:17:00: Particle Affector Type 'DeflectorPlane' registered
16:17:00: Plugin successfully installed
16:17:00: CPU Identifier & Features
16:17:00: -------------------------
16:17:00:  *   CPU ID: GenuineIntel: Intel(R) Core(TM) i7-5820K CPU @ 3.30GHz
16:17:00:  *   Logical cores: 12
16:17:00:  *      SSE: yes
16:17:00:  *     SSE2: yes
16:17:00:  *     SSE3: yes
16:17:00:  *      MMX: yes
16:17:00:  *   MMXEXT: yes
16:17:00:  *    3DNOW: no
16:17:00:  * 3DNOWEXT: no
16:17:00:  *     CMOV: yes
16:17:00:  *      TSC: yes
16:17:00:  *      FPU: yes
16:17:00:  *      PRO: yes
16:17:00:  *       HT: no
16:17:00: -------------------------
16:17:00: ******************************
*** Starting GLX Subsystem ***

16:17:00: GL3PlusRenderSystem::_createRenderWindow "OgreWindow(0)_0", 1x1 windowed  miscParams: FSAA=0 border=none contentScalingFactor=1.000000 currentGLContext=true externalGLControl=true gamma=Yes stereoMode=Frame Sequential
16:17:00: GLXWindow::create used FBConfigID = 173
16:17:00: GL Version = <IP_ADDRESS>
16:17:00: GL_VERSION = 3.3.0 NVIDIA 460.91.03
16:17:00: GL_VENDOR = NVIDIA Corporation
16:17:00: GL_RENDERER = GeForce GTX 1660 SUPER/PCIe/SSE2
16:17:00: GL_EXTENSIONS =
16:17:00: GL_AMD_multi_draw_indirect
16:17:00: GL_AMD_seamless_cubemap_per_texture
16:17:00: GL_AMD_vertex_shader_viewport_index
16:17:00: GL_AMD_vertex_shader_layer
16:17:00: GL_ARB_arrays_of_arrays
16:17:00: GL_ARB_base_instance
16:17:00: GL_ARB_bindless_texture
16:17:00: GL_ARB_blend_func_extended
16:17:00: GL_ARB_buffer_storage
16:17:00: GL_ARB_clear_buffer_object
16:17:00: GL_ARB_clear_texture
16:17:00: GL_ARB_clip_control
16:17:00: GL_ARB_color_buffer_float
16:17:00: GL_ARB_compressed_texture_pixel_storage
16:17:00: GL_ARB_conservative_depth
16:17:00: GL_ARB_compute_shader
16:17:00: GL_ARB_compute_variable_group_size
16:17:00: GL_ARB_conditional_render_inverted
16:17:00: GL_ARB_copy_buffer
16:17:00: GL_ARB_copy_image
16:17:00: GL_ARB_cull_distance
16:17:00: GL_ARB_debug_output
16:17:00: GL_ARB_depth_buffer_float
16:17:00: GL_ARB_depth_clamp
16:17:00: GL_ARB_depth_texture
16:17:00: GL_ARB_derivative_control
16:17:00: GL_ARB_direct_state_access
16:17:00: GL_ARB_draw_buffers
16:17:00: GL_ARB_draw_buffers_blend
16:17:00: GL_ARB_draw_indirect
16:17:00: GL_ARB_draw_elements_base_vertex
16:17:00: GL_ARB_draw_instanced
16:17:00: GL_ARB_enhanced_layouts
16:17:00: GL_ARB_ES2_compatibility
16:17:00: GL_ARB_ES3_compatibility
16:17:00: GL_ARB_ES3_1_compatibility
16:17:00: GL_ARB_ES3_2_compatibility
16:17:00: GL_ARB_explicit_attrib_location
16:17:00: GL_ARB_explicit_uniform_location
16:17:00: GL_ARB_fragment_coord_conventions
16:17:00: GL_ARB_fragment_layer_viewport
16:17:00: GL_ARB_fragment_program
16:17:00: GL_ARB_fragment_program_shadow
16:17:00: GL_ARB_fragment_shader
16:17:00: GL_ARB_fragment_shader_interlock
16:17:00: GL_ARB_framebuffer_no_attachments
16:17:00: GL_ARB_framebuffer_object
16:17:00: GL_ARB_framebuffer_sRGB
16:17:00: GL_ARB_geometry_shader4
16:17:00: GL_ARB_get_program_binary
16:17:00: GL_ARB_get_texture_sub_image
16:17:00: GL_ARB_gl_spirv
16:17:00: GL_ARB_gpu_shader5
16:17:00: GL_ARB_gpu_shader_fp64
16:17:00: GL_ARB_gpu_shader_int64
16:17:00: GL_ARB_half_float_pixel
16:17:00: GL_ARB_half_float_vertex
16:17:00: GL_ARB_imaging
16:17:00: GL_ARB_indirect_parameters
16:17:00: GL_ARB_instanced_arrays
16:17:00: GL_ARB_internalformat_query
16:17:00: GL_ARB_internalformat_query2
16:17:00: GL_ARB_invalidate_subdata
16:17:00: GL_ARB_map_buffer_alignment
16:17:00: GL_ARB_map_buffer_range
16:17:00: GL_ARB_multi_bind
16:17:00: GL_ARB_multi_draw_indirect
16:17:00: GL_ARB_multisample
16:17:00: GL_ARB_multitexture
16:17:00: GL_ARB_occlusion_query
16:17:00: GL_ARB_occlusion_query2
16:17:00: GL_ARB_parallel_shader_compile
16:17:00: GL_ARB_pipeline_statistics_query
16:17:00: GL_ARB_pixel_buffer_object
16:17:00: GL_ARB_point_parameters
16:17:00: GL_ARB_point_sprite
16:17:00: GL_ARB_polygon_offset_clamp
16:17:00: GL_ARB_post_depth_coverage
16:17:00: GL_ARB_program_interface_query
16:17:00: GL_ARB_provoking_vertex
16:17:00: GL_ARB_query_buffer_object
16:17:00: GL_ARB_robust_buffer_access_behavior
16:17:00: GL_ARB_robustness
16:17:00: GL_ARB_sample_locations
16:17:00: GL_ARB_sample_shading
16:17:00: GL_ARB_sampler_objects
16:17:00: GL_ARB_seamless_cube_map
16:17:00: GL_ARB_seamless_cubemap_per_texture
16:17:00: GL_ARB_separate_shader_objects
16:17:00: GL_ARB_shader_atomic_counter_ops
16:17:00: GL_ARB_shader_atomic_counters
16:17:00: GL_ARB_shader_ballot
16:17:00: GL_ARB_shader_bit_encoding
16:17:00: GL_ARB_shader_clock
16:17:00: GL_ARB_shader_draw_parameters
16:17:00: GL_ARB_shader_group_vote
16:17:00: GL_ARB_shader_image_load_store
16:17:00: GL_ARB_shader_image_size
16:17:00: GL_ARB_shader_objects
16:17:00: GL_ARB_shader_precision
16:17:00: GL_ARB_shader_storage_buffer_object
16:17:00: GL_ARB_shader_subroutine
16:17:00: GL_ARB_shader_texture_image_samples
16:17:00: GL_ARB_shader_texture_lod
16:17:00: GL_ARB_shading_language_100
16:17:00: GL_ARB_shader_viewport_layer_array
16:17:00: GL_ARB_shading_language_420pack
16:17:00: GL_ARB_shading_language_include
16:17:00: GL_ARB_shading_language_packing
16:17:00: GL_ARB_shadow
16:17:00: GL_ARB_sparse_buffer
16:17:00: GL_ARB_sparse_texture
16:17:00: GL_ARB_sparse_texture2
16:17:00: GL_ARB_sparse_texture_clamp
16:17:00: GL_ARB_spirv_extensions
16:17:00: GL_ARB_stencil_texturing
16:17:00: GL_ARB_sync
16:17:00: GL_ARB_tessellation_shader
16:17:00: GL_ARB_texture_barrier
16:17:00: GL_ARB_texture_border_clamp
16:17:00: GL_ARB_texture_buffer_object
16:17:00: GL_ARB_texture_buffer_object_rgb32
16:17:00: GL_ARB_texture_buffer_range
16:17:00: GL_ARB_texture_compression
16:17:00: GL_ARB_texture_compression_bptc
16:17:00: GL_ARB_texture_compression_rgtc
16:17:00: GL_ARB_texture_cube_map
16:17:00: GL_ARB_texture_cube_map_array
16:17:00: GL_ARB_texture_env_add
16:17:00: GL_ARB_texture_env_combine
16:17:00: GL_ARB_texture_env_crossbar
16:17:00: GL_ARB_texture_env_dot3
16:17:00: GL_ARB_texture_filter_anisotropic
16:17:00: GL_ARB_texture_filter_minmax
16:17:00: GL_ARB_texture_float
16:17:00: GL_ARB_texture_gather
16:17:00: GL_ARB_texture_mirror_clamp_to_edge
16:17:00: GL_ARB_texture_mirrored_repeat
16:17:00: GL_ARB_texture_multisample
16:17:00: GL_ARB_texture_non_power_of_two
16:17:00: GL_ARB_texture_query_levels
16:17:00: GL_ARB_texture_query_lod
16:17:00: GL_ARB_texture_rectangle
16:17:00: GL_ARB_texture_rg
16:17:00: GL_ARB_texture_rgb10_a2ui
16:17:00: GL_ARB_texture_stencil8
16:17:00: GL_ARB_texture_storage
16:17:00: GL_ARB_texture_storage_multisample
16:17:00: GL_ARB_texture_swizzle
16:17:00: GL_ARB_texture_view
16:17:00: GL_ARB_timer_query
16:17:00: GL_ARB_transform_feedback2
16:17:00: GL_ARB_transform_feedback3
16:17:00: GL_ARB_transform_feedback_instanced
16:17:00: GL_ARB_transform_feedback_overflow_query
16:17:00: GL_ARB_transpose_matrix
16:17:00: GL_ARB_uniform_buffer_object
16:17:00: GL_ARB_vertex_array_bgra
16:17:00: GL_ARB_vertex_array_object
16:17:00: GL_ARB_vertex_attrib_64bit
16:17:00: GL_ARB_vertex_attrib_binding
16:17:00: GL_ARB_vertex_buffer_object
16:17:00: GL_ARB_vertex_program
16:17:00: GL_ARB_vertex_shader
16:17:00: GL_ARB_vertex_type_10f_11f_11f_rev
16:17:00: GL_ARB_vertex_type_2_10_10_10_rev
16:17:00: GL_ARB_viewport_array
16:17:00: GL_ARB_window_pos
16:17:00: GL_ATI_draw_buffers
16:17:00: GL_ATI_texture_float
16:17:00: GL_ATI_texture_mirror_once
16:17:00: GL_S3_s3tc
16:17:00: GL_EXT_texture_env_add
16:17:00: GL_EXT_abgr
16:17:00: GL_EXT_bgra
16:17:00: GL_EXT_bindable_uniform
16:17:00: GL_EXT_blend_color
16:17:00: GL_EXT_blend_equation_separate
16:17:00: GL_EXT_blend_func_separate
16:17:00: GL_EXT_blend_minmax
16:17:00: GL_EXT_blend_subtract
16:17:00: GL_EXT_compiled_vertex_array
16:17:00: GL_EXT_Cg_shader
16:17:00: GL_EXT_depth_bounds_test
16:17:00: GL_EXT_direct_state_access
16:17:00: GL_EXT_draw_buffers2
16:17:00: GL_EXT_draw_instanced
16:17:00: GL_EXT_draw_range_elements
16:17:00: GL_EXT_fog_coord
16:17:00: GL_EXT_framebuffer_blit
16:17:00: GL_EXT_framebuffer_multisample
16:17:00: GL_EXTX_framebuffer_mixed_formats
16:17:00: GL_EXT_framebuffer_multisample_blit_scaled
16:17:00: GL_EXT_framebuffer_object
16:17:00: GL_EXT_framebuffer_sRGB
16:17:00: GL_EXT_geometry_shader4
16:17:00: GL_EXT_gpu_program_parameters
16:17:00: GL_EXT_gpu_shader4
16:17:00: GL_EXT_multi_draw_arrays
16:17:00: GL_EXT_multiview_texture_multisample
16:17:00: GL_EXT_multiview_timer_query
16:17:00: GL_EXT_packed_depth_stencil
16:17:00: GL_EXT_packed_float
16:17:00: GL_EXT_packed_pixels
16:17:00: GL_EXT_pixel_buffer_object
16:17:00: GL_EXT_point_parameters
16:17:00: GL_EXT_polygon_offset_clamp
16:17:00: GL_EXT_post_depth_coverage
16:17:00: GL_EXT_provoking_vertex
16:17:00: GL_EXT_raster_multisample
16:17:00: GL_EXT_rescale_normal
16:17:00: GL_EXT_secondary_color
16:17:00: GL_EXT_separate_shader_objects
16:17:00: GL_EXT_separate_specular_color
16:17:00: GL_EXT_shader_image_load_formatted
16:17:00: GL_EXT_shader_image_load_store
16:17:00: GL_EXT_shader_integer_mix
16:17:00: GL_EXT_shadow_funcs
16:17:00: GL_EXT_sparse_texture2
16:17:00: GL_EXT_stencil_two_side
16:17:00: GL_EXT_stencil_wrap
16:17:00: GL_EXT_texture3D
16:17:00: GL_EXT_texture_array
16:17:00: GL_EXT_texture_buffer_object
16:17:00: GL_EXT_texture_compression_dxt1
16:17:00: GL_EXT_texture_compression_latc
16:17:00: GL_EXT_texture_compression_rgtc
16:17:00: GL_EXT_texture_compression_s3tc
16:17:00: GL_EXT_texture_cube_map
16:17:00: GL_EXT_texture_edge_clamp
16:17:00: GL_EXT_texture_env_combine
16:17:00: GL_EXT_texture_env_dot3
16:17:00: GL_EXT_texture_filter_anisotropic
16:17:00: GL_EXT_texture_filter_minmax
16:17:00: GL_EXT_texture_integer
16:17:00: GL_EXT_texture_lod
16:17:00: GL_EXT_texture_lod_bias
16:17:00: GL_EXT_texture_mirror_clamp
16:17:00: GL_EXT_texture_object
16:17:00: GL_EXT_texture_shadow_lod
16:17:00: GL_EXT_texture_shared_exponent
16:17:00: GL_EXT_texture_sRGB
16:17:00: GL_EXT_texture_sRGB_R8
16:17:00: GL_EXT_texture_sRGB_decode
16:17:00: GL_EXT_texture_storage
16:17:00: GL_EXT_texture_swizzle
16:17:00: GL_EXT_timer_query
16:17:00: GL_EXT_transform_feedback2
16:17:00: GL_EXT_vertex_array
16:17:00: GL_EXT_vertex_array_bgra
16:17:00: GL_EXT_vertex_attrib_64bit
16:17:00: GL_EXT_window_rectangles
16:17:00: GL_EXT_x11_sync_object
16:17:00: GL_EXT_import_sync_object
16:17:00: GL_NV_robustness_video_memory_purge
16:17:00: GL_IBM_rasterpos_clip
16:17:00: GL_IBM_texture_mirrored_repeat
16:17:00: GL_KHR_context_flush_control
16:17:00: GL_KHR_debug
16:17:00: GL_EXT_memory_object
16:17:00: GL_EXT_memory_object_fd
16:17:00: GL_NV_memory_object_sparse
16:17:00: GL_KHR_parallel_shader_compile
16:17:00: GL_KHR_no_error
16:17:00: GL_KHR_robust_buffer_access_behavior
16:17:00: GL_KHR_robustness
16:17:00: GL_EXT_semaphore
16:17:00: GL_EXT_semaphore_fd
16:17:00: GL_NV_timeline_semaphore
16:17:00: GL_KHR_shader_subgroup
16:17:00: GL_KTX_buffer_region
16:17:00: GL_NV_alpha_to_coverage_dither_control
16:17:00: GL_NV_bindless_multi_draw_indirect
16:17:00: GL_NV_bindless_multi_draw_indirect_count
16:17:00: GL_NV_bindless_texture
16:17:00: GL_NV_blend_equation_advanced
16:17:00: GL_NV_blend_equation_advanced_coherent
16:17:00: GL_NVX_blend_equation_advanced_multi_draw_buffers
16:17:00: GL_NV_blend_minmax_factor
16:17:00: GL_NV_blend_square
16:17:00: GL_NV_clip_space_w_scaling
16:17:00: GL_NV_command_list
16:17:00: GL_NV_compute_program5
16:17:00: GL_NV_compute_shader_derivatives
16:17:00: GL_NV_conditional_render
16:17:00: GL_NV_conservative_raster
16:17:00: GL_NV_conservative_raster_dilate
16:17:00: GL_NV_conservative_raster_pre_snap
16:17:00: GL_NV_conservative_raster_pre_snap_triangles
16:17:00: GL_NV_conservative_raster_underestimation
16:17:00: GL_NV_copy_depth_to_color
16:17:00: GL_NV_copy_image
16:17:00: GL_NV_depth_buffer_float
16:17:00: GL_NV_depth_clamp
16:17:00: GL_NV_draw_texture
16:17:00: GL_NV_draw_vulkan_image
16:17:00: GL_NV_ES1_1_compatibility
16:17:00: GL_NV_ES3_1_compatibility
16:17:00: GL_NV_explicit_multisample
16:17:00: GL_NV_feature_query
16:17:00: GL_NV_fence
16:17:00: GL_NV_fill_rectangle
16:17:00: GL_NV_float_buffer
16:17:00: GL_NV_fog_distance
16:17:00: GL_NV_fragment_coverage_to_color
16:17:00: GL_NV_fragment_program
16:17:00: GL_NV_fragment_program_option
16:17:00: GL_NV_fragment_program2
16:17:00: GL_NV_fragment_shader_barycentric
16:17:00: GL_NV_fragment_shader_interlock
16:17:00: GL_NV_framebuffer_mixed_samples
16:17:00: GL_NV_framebuffer_multisample_coverage
16:17:00: GL_NV_geometry_shader4
16:17:00: GL_NV_geometry_shader_passthrough
16:17:00: GL_NV_gpu_program4
16:17:00: GL_NV_internalformat_sample_query
16:17:00: GL_NV_gpu_program4_1
16:17:00: GL_NV_gpu_program5
16:17:00: GL_NV_gpu_program5_mem_extended
16:17:00: GL_NV_gpu_program_fp64
16:17:00: GL_NV_gpu_shader5
16:17:00: GL_NV_half_float
16:17:00: GL_NV_light_max_exponent
16:17:00: GL_NV_memory_attachment
16:17:00: GL_NV_mesh_shader
16:17:00: GL_NV_multisample_coverage
16:17:00: GL_NV_multisample_filter_hint
16:17:00: GL_NV_occlusion_query
16:17:00: GL_NV_packed_depth_stencil
16:17:00: GL_NV_parameter_buffer_object
16:17:00: GL_NV_parameter_buffer_object2
16:17:00: GL_NV_path_rendering
16:17:00: GL_NV_path_rendering_shared_edge
16:17:00: GL_NV_pixel_data_range
16:17:00: GL_NV_point_sprite
16:17:00: GL_NV_primitive_restart
16:17:00: GL_NV_query_resource
16:17:00: GL_NV_query_resource_tag
16:17:00: GL_NV_register_combiners
16:17:00: GL_NV_register_combiners2
16:17:00: GL_NV_representative_fragment_test
16:17:00: GL_NV_sample_locations
16:17:00: GL_NV_sample_mask_override_coverage
16:17:00: GL_NV_scissor_exclusive
16:17:00: GL_NV_shader_atomic_counters
16:17:00: GL_NV_shader_atomic_float
16:17:00: GL_NV_shader_atomic_float64
16:17:00: GL_NV_shader_atomic_fp16_vector
16:17:00: GL_NV_shader_atomic_int64
16:17:00: GL_NV_shader_buffer_load
16:17:00: GL_NV_shader_storage_buffer_object
16:17:00: GL_NV_shader_subgroup_partitioned
16:17:00: GL_NV_shader_texture_footprint
16:17:00: GL_NV_shading_rate_image
16:17:00: GL_NV_stereo_view_rendering
16:17:00: GL_NV_texgen_reflection
16:17:00: GL_NV_texture_barrier
16:17:00: GL_NV_texture_compression_vtc
16:17:00: GL_NV_texture_env_combine4
16:17:00: GL_NV_texture_multisample
16:17:00: GL_NV_texture_rectangle
16:17:00: GL_NV_texture_rectangle_compressed
16:17:00: GL_NV_texture_shader
16:17:00: GL_NV_texture_shader2
16:17:00: GL_NV_texture_shader3
16:17:00: GL_NV_transform_feedback
16:17:00: GL_NV_transform_feedback2
16:17:00: GL_NV_uniform_buffer_unified_memory
16:17:00: GL_NV_vdpau_interop
16:17:00: GL_NV_vdpau_interop2
16:17:00: GL_NV_vertex_array_range
16:17:00: GL_NV_vertex_array_range2
16:17:00: GL_NV_vertex_attrib_integer_64bit
16:17:00: GL_NV_vertex_buffer_unified_memory
16:17:00: GL_NV_vertex_program
16:17:00: GL_NV_vertex_program1_1
16:17:00: GL_NV_vertex_program2
16:17:00: GL_NV_vertex_program2_option
16:17:00: GL_NV_vertex_program3
16:17:00: GL_NV_viewport_array2
16:17:00: GL_NV_viewport_swizzle
16:17:00: GL_NVX_conditional_render
16:17:00: GL_NV_gpu_multicast
16:17:00: GL_NVX_progress_fence
16:17:00: GL_NVX_gpu_memory_info
16:17:00: GL_NVX_nvenc_interop
16:17:00: GL_NV_shader_thread_group
16:17:00: GL_NV_shader_thread_shuffle
16:17:00: GL_KHR_blend_equation_advanced
16:17:00: GL_KHR_blend_equation_advanced_coherent
16:17:00: GL_OVR_multiview
16:17:00: GL_OVR_multiview2
16:17:00: GL_SGIS_generate_mipmap
16:17:00: GL_SGIS_texture_lod
16:17:00: GL_SGIX_depth_texture
16:17:00: GL_SGIX_shadow
16:17:00: GL_SUN_slice_accum
16:17:00: Supported GLX extensions: GLX_EXT_visual_info GLX_EXT_visual_rating GLX_EXT_import_context GLX_SGIX_fbconfig GLX_SGIX_pbuffer GLX_SGI_video_sync GLX_SGI_swap_control GLX_EXT_swap_control GLX_EXT_swap_control_tear GLX_EXT_texture_from_pixmap GLX_EXT_buffer_age GLX_ARB_create_context GLX_ARB_create_context_profile GLX_EXT_create_context_es_profile GLX_EXT_create_context_es2_profile GLX_ARB_create_context_no_error GLX_ARB_create_context_robustness GLX_NV_delay_before_swap GLX_EXT_stereo_tree GLX_ARB_context_flush_control GLX_NV_robustness_video_memory_purge GLX_NV_multigpu_context GLX_ARB_multisample GLX_NV_float_buffer GLX_ARB_fbconfig_float GLX_EXT_framebuffer_sRGB GLX_NV_copy_image GLX_ARB_get_proc_address
16:17:00: **************************************
16:17:00: ***   OpenGL 3+ Renderer Started   ***
16:17:00: **************************************
16:17:00: Registering ResourceManager for type GpuProgram
16:17:00: RenderSystem capabilities
16:17:00: -------------------------
16:17:00: RenderSystem Name: OpenGL 3+ Rendering Subsystem
16:17:00: GPU Vendor: nvidia
16:17:00: Device Name: GeForce GTX 1660 SUPER/PCIe/SSE2
16:17:00: Driver Version: <IP_ADDRESS>
16:17:00:  * Fixed function pipeline: no
16:17:00:  * Hardware generation of mipmaps: yes
16:17:00:  * Texture blending: yes
16:17:00:  * Anisotropic texture filtering: yes
16:17:00:  * Dot product texture operation: yes
16:17:00:  * Cube mapping: yes
16:17:00:  * Hardware stencil buffer: yes
16:17:00:    - Stencil depth: 8
16:17:00:    - Two sided stencil support: yes
16:17:00:    - Wrap stencil values: yes
16:17:00:  * Hardware vertex / index buffers: yes
16:17:00:  * 32-bit index buffers: yes
16:17:00:  * Vertex programs: yes
16:17:00:  * Number of floating-point constants for vertex programs: 4096
16:17:00:  * Number of integer constants for vertex programs: 4096
16:17:00:  * Number of boolean constants for vertex programs: 4096
16:17:00:  * Fragment programs: yes
16:17:00:  * Number of floating-point constants for fragment programs: 4096
16:17:00:  * Number of integer constants for fragment programs: 4096
16:17:00:  * Number of boolean constants for fragment programs: 4096
16:17:00:  * Geometry programs: yes
16:17:00:  * Number of floating-point constants for geometry programs: 2048
16:17:00:  * Number of integer constants for geometry programs: 2048
16:17:00:  * Number of boolean constants for geometry programs: 2048
16:17:00:  * Tessellation Hull programs: yes
16:17:00:  * Number of floating-point constants for tessellation hull programs: 2048
16:17:00:  * Number of integer constants for tessellation hull programs: 2048
16:17:00:  * Number of boolean constants for tessellation hull programs: 2048
16:17:00:  * Tessellation Domain programs: yes
16:17:00:  * Number of floating-point constants for tessellation domain programs: 2048
16:17:00:  * Number of integer constants for tessellation domain programs: 2048
16:17:00:  * Number of boolean constants for tessellation domain programs: 2048
16:17:00:  * Compute programs: yes
16:17:00:  * Number of floating-point constants for compute programs: 2048
16:17:00:  * Number of integer constants for compute programs: 2048
16:17:00:  * Number of boolean constants for compute programs: 2048
16:17:00:  * Supported Shader Profiles: glsl glsl130 glsl140 glsl150 glsl330
16:17:00:  * Texture Compression: yes
16:17:00:    - DXT: yes
16:17:00:    - VTC: yes
16:17:00:    - PVRTC: no
16:17:00:    - ATC: no
16:17:00:    - ETC1: no
16:17:00:    - ETC2: yes
16:17:00:    - BC4/BC5: yes
16:17:00:    - BC6H/BC7: yes
16:17:00:    - ASTC: no
16:17:00:  * Hardware Occlusion Query: yes
16:17:00:  * User clip planes: yes
16:17:00:  * VET_UBYTE4 vertex element type: yes
16:17:00:  * Infinite far plane projection: yes
16:17:00:  * Hardware render-to-texture: yes
16:17:00:  * Floating point textures: yes
16:17:00:  * Non-power-of-two textures: yes
16:17:00:  * 1d textures: yes
16:17:00:  * Volume textures: yes
16:17:00:  * Max Texture resolution (2D) 32768
16:17:00:  * Max Texture resolution (3D) 16384
16:17:00:  * Max Texture resolution (Cubemaps) 32768
16:17:00:  * Multiple Render Targets: 8
16:17:00:    - With different bit depths: yes
16:17:00:  * Point Sprites: yes
16:17:00:  * Extended point parameters: yes
16:17:00:  * Max Point Size: 2047
16:17:00:  * Vertex texture fetch: yes
16:17:00:  * Number of world matrices: 0
16:17:00:  * Number of texture units: 16
16:17:00:  * Stencil buffer depth: 8
16:17:00:  * Number of vertex blend matrices: 0
16:17:00:    - Max vertex textures: 32
16:17:00:    - Vertex textures shared: yes
16:17:00:  * Render to Vertex Buffer : yes
16:17:00:  * Hardware Atomic Counters: yes
16:17:00:  * Compute max threads per threadgroup per axis: 1024, 1024, 64
16:17:00:  * Compute max threads per threadgroup total: 1024
16:17:00:  * GL 1.5 without VBO workaround: no
16:17:00:  * Frame Buffer objects: yes
16:17:00:  * Frame Buffer objects (ARB extension): no
16:17:00:  * Frame Buffer objects (ATI extension): no
16:17:00:  * PBuffer support: no
16:17:00:  * GL 1.5 without HW-occlusion workaround: no
16:17:00:  * Vertex Array Objects: yes
16:17:00:  * Separate shader objects: no
16:17:00:  * Using Reverse Z: yes
16:17:00: DefaultWorkQueue('Root') initialising on thread main.
16:17:00: Particle Renderer Type 'billboard' registered
16:17:00: Added resource location '/home/osrf/Workspaces/ignFortress_ws/install/share/ignition/ignition-rendering6/ogre2/media/2.0/scripts/Compositors' of type 'FileSystem' to resource group 'General'
16:17:00: Added resource location '/home/osrf/Workspaces/ignFortress_ws/install/share/ignition/ignition-rendering6/ogre2/media/2.0/scripts/materials/Common' of type 'FileSystem' to resource group 'General'
16:17:00: Added resource location '/home/osrf/Workspaces/ignFortress_ws/install/share/ignition/ignition-rendering6/ogre2/media/2.0/scripts/materials/Common/GLSL' of type 'FileSystem' to resource group 'General'
16:17:00: Added resource location '/home/osrf/Workspaces/ignFortress_ws/install/share/ignition/ignition-rendering6/ogre2/media/2.0/scripts/materials/Common/GLSLES' of type 'FileSystem' to resource group 'General'
16:17:00: Added resource location '/home/osrf/Workspaces/ignFortress_ws/install/share/ignition/ignition-rendering6/ogre2/media' of type 'FileSystem' to resource group 'General'
16:17:00: Added resource location '/home/osrf/Workspaces/ignFortress_ws/install/share/ignition/ignition-rendering6/ogre2/media/materials/programs' of type 'FileSystem' to resource group 'General'
16:17:00: Added resource location '/home/osrf/Workspaces/ignFortress_ws/install/share/ignition/ignition-rendering6/ogre2/media/materials/scripts' of type 'FileSystem' to resource group 'General'
16:17:00: Added resource location '/home/osrf/Workspaces/ignFortress_ws/install/share/ignition/ignition-rendering6/ogre2/media/materials/textures' of type 'FileSystem' to resource group 'General'
16:17:00: Parsing scripts for resource group Autodetect
16:17:00: Finished parsing scripts for resource group Autodetect
16:17:00: Creating resources for group Autodetect
16:17:00: All done
16:17:00: Parsing scripts for resource group General
16:17:00: Parsing script Quad.program
16:17:00: Parsing script DepthUtils.material
16:17:00: Parsing script DPSM.material
16:17:00: Parsing script Copyback.material
16:17:00: Parsing script EsmGaussianBlurLogFilter.material
16:17:00: Parsing script gpu_rays.material
16:17:00: Parsing script thermal.material
16:17:00: Parsing script skybox.material
16:17:00: Parsing script picker.material
16:17:00: Parsing script gaussian_noise.material
16:17:00: Parsing script depth_camera.material
16:17:00: Parsing script GaussianNoise.compositor
16:17:00: Parsing script PbsMaterials.compositor
16:17:00: Compiler error: invalid parameters in PbsMaterials.compositor(4): Unrecognized PixelFormat
16:17:00: Compiler error: invalid parameters in PbsMaterials.compositor(8): Unrecognized PixelFormat
16:17:00: OGRE EXCEPTION(5:ItemIdentityException): Can't find texture with name: '[Hash 0x05f70bcc]' If it's a global texture, trying to use it in the output channel will fail. in CompositorNodeDef::getTextureSource at /home/jenkins/workspace/ogre-2.2-debbuilder/repo/OgreMain/src/Compositor/OgreTextureDefinition.cpp (line 214)
16:17:00: Compiler error: invalid parameters in PbsMaterials.compositor(25)
16:17:00: Parsing scripts for resource group Internal
16:17:00: Finished parsing scripts for resource group Internal
16:17:00: Creating resources for group Internal
16:17:00: All done
16:17:00: Added resource location '/home/osrf/Workspaces/ignFortress_ws/install/share/ignition/ignition-rendering6/media/materials/textures/' of type 'FileSystem' to resource group 'General'
16:17:00: Can't assign material scene::Material(65506) because this Material does not exist. Have you forgotten to define it in a .material script?
16:17:00: Can't assign material scene::Material(65500) because this Material does not exist. Have you forgotten to define it in a .material script?
16:17:00: Can't assign material scene::Material(65494) because this Material does not exist. Have you forgotten to define it in a .material script?
16:17:00: Can't assign material scene::Material(65488) because this Material does not exist. Have you forgotten to define it in a .material script?
16:17:00: Can't assign material scene::Material(65481) because this Material does not exist. Have you forgotten to define it in a .material script?
16:17:00: Can't assign material scene::Material(65488) because this Material does not exist. Have you forgotten to define it in a .material script?
16:17:00: Can't assign material scene::Material(65468) because this Material does not exist. Have you forgotten to define it in a .material script?
16:17:01: WARNING: Deleting mapped buffer without having it unmapped. This is often sign of a resource leak or a bad pattern. Umapping the buffer for you...
16:17:01: WARNING: Deleting mapped buffer without having it unmapped. This is often sign of a resource leak or a bad pattern. Umapping the buffer for you...
16:17:01: WARNING: Deleting mapped buffer without having it unmapped. This is often sign of a resource leak or a bad pattern. Umapping the buffer for you...
16:17:01: WARNING: Deleting mapped buffer without having it unmapped. This is often sign of a resource leak or a bad pattern. Umapping the buffer for you...

Also, when I try to expand the GUI, it crashes with:
ign gazebo gui: /home/osrf/Workspaces/ignFortress_ws/src/ign-rendering/ogre2/src/Ogre2Scene.cc:270: void ignition::rendering::v6::Ogre2Scene::StartRendering(): Assertion `("Started rendering without first calling Scene::PreRender. " "See Scene::SetCameraPassCountPerGpuFlush for details", this->dataPtr->frameUpdateStarted == true)' failed.
[Dbg] [SignalHandler.cc:141] Received signal[2].
[Dbg] [ServerPrivate.cc:108] Server received signal[2]
[Dbg] [ign.cc:353] Shutting down ign-gazebo-server
[Dbg] [SimulationRunner.cc:543] Exiting postupdate worker thread (0)

I ran into the issue with failing to initialize the engine a few times. We recently merged https://github.com/ignitionrobotics/ign-rendering/pull/272 that upgrades ogre 2.1 to 2.2. The error and crash for me was due to leftover ogre2.1 media files in the colcon install directory. Looking at the ogre2.log:
Compiler error: invalid parameters in PbsMaterials.compositor(4): Unrecognized PixelFormat

The PbsMaterials.compositor exists in ign-rendering versions <5 but should be removed in the latest ign-rendering main branch.  So it's trying to load a ogre 2.1 script that does work in ogre 2.2. So it may worth doing a clean rebuild and see if the issue still persists.

Thanks, a clean rebuild of the entire workspace worked for me. Yesterday I had only rebuilt rendering.


On the live site, only the src architecture is shown

You can only view details for the src architecture as of right now on the site. The other architectures (aarch64, armv7hl, i486, noarch) seem to have disappeared.
It's most likely a regression introduced in 0da67c5, while adding support for changelogs, as I modified the package loading logic

Fixed in f4d13db


inject mockk implementation supporting mocking fields with attributes…

… of non-same types and only through property injection

Codecov Report

Merging #28 into master will decrease coverage by 0.35%.
The diff coverage is 57.14%.

@@             Coverage Diff              @@
##             master      #28      +/-   ##
============================================
- Coverage     80.23%   79.88%   -0.36%
- Complexity      510      519       +9
============================================
  Files            62       62
  Lines          1361     1382      +21
  Branches        215      226      +11
============================================
+ Hits           1092     1104      +12
- Misses          172      174       +2
- Partials         97      104       +7

Impacted Files
Coverage Δ
Complexity Δ

...in/io/mockk/impl/annotations/JvmMockInitializer.kt
66.12% <57.14%> (-4.61%)
25 <4> (+9)

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 da73c3a...585711e. Read the comment docs.

I looked through the code. I'll do more detailed check in the evening. Thanks

Things to consider:

Mocks have names, and parameters in Kotlin have names.
It is possible to specify mock name via annotation (or if not specified it takes name of property AFAIK)
So we can try further resolution by name if two instances of the same type found.

Parameters can have defaults. We should allow to skip parameters with defaults I believe

Should we consider sub-classes, implemented/extended interfaces when resolving? I don't know how it works in Mockito. Would be pretty weird if yes.

Should we take primary constructor instead of max argument count? This would be more Kotlin style, but we still should support Java well. Good to have few Java tests for such kind of cases.

btw @itsryry seems it is pretty demanded feature. Just've recently one of the guys were asking it in gitter. I think around 4-5 people were asking so far.

already implemented


chore: remove api v1beta2

Do not delete .github/workflows/upgrade.yaml, should change v1beta2 to v1beta3 in this file


Clustering: Handling clusters in same location

Thank you very much for all your work on the library and the recent work on clustering.
I was having a play with the clustering library and wondered how we can handle pins when they're too close together.
E.g. in Bangkok I have the following 4 pins:
latitude=13.720681, longitude=100.515331
latitude=13.72066, longitude=100.515344
latitude=13.720681, longitude=100.515331
latitude=13.720681, longitude=100.515331
For the onClusterClick I have basically done this:
 cameraPositionState.animate(
                    CameraUpdateFactory.newLatLngZoom(
                        cluster.position,
                        cameraPositionState.position.zoom + 1))

But after a while it doesn't really do anything and after 20.0f zoom nothing changes. Are there some examples of how to explode these out once any further zoom will not expand the cluster? It would be nice if I could skip intermediate zoom levels that won't change the state of the cluster too, if I knew how to calculate whether a zoom would change the clustering.
Also does the zIndex actual work on the clusterItemContent? I tried doing this:
         Image(
                painterResource(drawable),
                contentDescription = item.title,
                Modifier.zIndex(if (isCurrent) 1f else 0f)
            )

but the pins never rearrange when one of them becomes current.

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

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

This is an automated message, feel free to ignore.

I found some work-arounds for old non-compose clustering like Make Your own Cluster Rendering or change maxZoom. But it doesn't work for the compose version.

i'm also missing the ability to set the zIndex of clusters and cluster items. Currently i have the problem that the clusters (and items) are overlayed by other markers where i need to define zIndex


Rewriting some parts of the README for english correctness

Just cleaning up the README for more natural english, thanks a bunch for writing this library :+1:

Merged as d7bb493 with a small commit message fix. Thanks for your contribution!


docs: update ai-module.mdx

Documentation for Knowledge Graph / Function tools usage

Nice docs @mmikita95 I'll certainly read them to add function calling to Workflows


Invalid API description for unbound functions

Hello,
in my CAP Java based service, I have defined the following CDS model:
db/db-model.cds:
entity TestEntity {
    key ID: String;
    name: String;
}

srv/test-service.cds:
using { TestEntity } from '../db/db-model';

service TestService {
  entity TestServiceEntity as projection on TestEntity;

  define type DataEntry {
    ID: String;
    name: String;
  }

  function getEntries(id: String not null, name: String not null) returns array of DataEntry;
}

When generating the openapi.json using this command:
cds compile srv/test-service.cds -2 openapi --openapi:url /odata/v4/TestService > openapi.json

I can see that the generated API description for the unbound function doesn't result in a conformant OData v4 URL. When using Swagger UI the following request URL is generated which is invalid:
http://localhost:8080/odata/v4/TestService/getEntries?id=%27k1%27&name=%27v1%27

The valid OData v4 request URL looks like this:
http://localhost:8080/odata/v4/TestService/getEntries(id=%27k1%27,name=%27v1%27)

This are the versions that are used in my project:

swaggerui-cds

@cap-js/asyncapi
1.0.2

@cap-js/openapi
1.0.5

@sap/cds
8.2.3

@sap/cds-compiler
5.2.0

@sap/cds-dk
8.2.3

@sap/cds-fiori
1.2.7

@sap/cds-foss
5.0.1

@sap/cds-mtxs
2.1.0

@sap/eslint-plugin-cds
3.0.5

CAP Java SDK
3.3.1

Java
21.0.5, home: /Library/Java/JavaVirtualMachines/sapmachine-21.jdk/Contents/Home

Maven
3.9.9, home: /Users/D021624/SAPDevelop/Tools/apache-maven-3.9.9

Node.js
v20.17.0

OS
Mac OS X, 15.1, arch: aarch64

Spring Boot
3.3.5

cds4j
3.3.1

home
/Users/D021624/SAPDevelop/CAPJava/Samples/swaggerui/node_modules/@sap/cds-dk/node_modules/@sap/cds

Can you please fix this issue?
Best regards
Thomas

Hello @RoshniNaveenaS,
are there any updates regarding this issue? Since it is related to an incident of an external customer, it is quite urgent.
Tanks & Best regards
Thomas

Hello @RoshniNaveenaS,
are there any updates regarding this issue? Since it is related to an incident of an external customer, it is quite urgent.
Tanks & Best regards Thomas

Hello @t-bonk ,
I will look into this on priority and get back to you

Hello @t-bonk,
Could you let us know what is the expected output URL from openAPI side?
@ralfhandl do you think we have to make any changes to the URLgeneration in this case?

Hello @RoshniNaveenaS,
in my opinion the metadata for a function should like this:
"/getEntries(id={id},name={name})": {
      "get": {
        "summary": "Invokes function getEntries",
        "tags": [
          "Service Operations"
        ],
        "parameters": [
          {
            "required": true,
            "in": "path",
            "name": "id",
            "description": "String value needs to be enclosed in single quotes",
            "schema": {
              "type": "string",
              "pattern": "^'([^']|'')*'$"
            }
          },
          {
            "required": true,
            "in": "path",
            "name": "name",
            "description": "String value needs to be enclosed in single quotes",
            "schema": {
              "type": "string",
              "pattern": "^'([^']|'')*'$"
            }
          }
        ],

for an unbound function defined in CDS like this:
function getEntries(id: String not null, name: String not null) returns array of DataEntry;

The URI for an OData V4 function call looks like this:
.../getEntries(id='k1',name='n1')
Best regards
Thomas

Hello @ralfhandl,
I haven't been looking at this property, to be honest. After compiling to openapi with the parameter --odata-version 4.0, the metadata is generated in way such that it is working with CAP Java.
@RoshniNaveenaS I'm closing this issue.
Best regards
Thomas

the generated API description says it was generated for
"x-odata-version": "4.01",

and OData 4.01 and later allow placing the function parameters in the query part of the request URL, see implicit parameter aliases and Example 97.
The OpenAPI generator uses OData 4.01 by default. You can force it back to 4.0 syntax with the command-line option --odata-version 4.0.

This is a bit unfortunate, because neither the our internal Olingo, nor the Open Source supports the syntax. I guess, both libraries (internal and OS) are relying on the ABNF, where the syntax from Example 97 is not present. We expect the (param=val) syntax.
But you say the command-line option --odata-version 4.0 may be a temporal solution, right? So if the client generates the OpenAPI description for 4.0 but sends the requests with OData-version: 4.01 header it should work, as expected?
Regards
Evgeny

the generated API description says it was generated for
"x-odata-version": "4.01",

and OData 4.01 and later allow placing the function parameters in the query part of the request URL, see implicit parameter aliases and Example 97.
The OpenAPI generator uses OData 4.01 by default. You can force it back to 4.0 syntax with the command-line option --odata-version 4.0.

This is a bit unfortunate, because neither the our internal Olingo, nor the Open Source supports the syntax. I guess, both libraries (internal and OS) are relying on the ABNF, where the syntax from Example 97 is not present. We expect the (param=val) syntax.
But you say the command-line option --odata-version 4.0 may be a temporal solution, right? So if the client generates the OpenAPI description for 4.0 but sends the requests with OData-version: 4.01 header it should work, as expected?
Regards Evgeny

Hello,
Regarding the generation of OpenAPI document , the CLI Option is used to change the version accordingly. This allows developers to customize the OpenAPI document according to the specific use case and requirements of their project. We recommend making appropriate changes to align the version and details with the intended use case to ensure accuracy and relevance for API consumers.
Thanks in advance!
Best Regards,
Roshni Naveena S


Adding support for the CosineAnnealingWarmRestarts scheduler

Fixes #2849
Seems like there is currently no support for the schedulers taking values to the step function.
This commit adds support for any scheduler (not particularly ReduceOnPlateau scheduler) taking in validation metrics value/epoch/step_progress.
Step progress is a float value that CosineAnnealingWarmRestarts scheduler takes in cases when a step function is called after each step, which is found as current_epoch+batch_idx/num_training_batches.
Now, the 'monitor' attribute in the schedulers dictionary can also take strings 'epoch' and 'iter_frac' (denotes step progress). As there will be the need for other input values, the dictionary of additional 'monitor' keys and short lambda functions implementing their computation can be extended or moved to the utils section.

Hello @Alicegaz! Thanks for opening this PR.

In the file pytorch_lightning/trainer/training_loop.py:

Line 272:42: E127 continuation line over-indented for visual indent
Line 274:34: E127 continuation line over-indented for visual indent
Line 274:58: E225 missing whitespace around operator

In the file tests/base/model_optimizers.py:

Line 65:37: E226 missing whitespace around arithmetic operator

Do see the Hitchhiker's guide to code style

@ananyahjha93 You might want to take a look at this since you recently added a scheduler to bolts.
https://github.com/PyTorchLightning/pytorch-lightning-bolts/pull/138

@Alicegaz closing this PR now, based on the discussions in #2849, we don't think this is the right way to go.

@ananyahjha93 what's the decision here?


Remove django.conf.urls.patterns from code

Need remove django.conf.urls.patterns, because it's deprecated.

Fixed by #12

Was fixed and merged. Thanks

Now in pypi v0.4.2


ref: GDrive supported by open()

Mention that gdrive now supports open() from https://github.com/iterative/dvc/pull/3916

This means that https://dvc.org/doc/api-reference/open supports GDrive now yes? That would be a very quick update prob.

I believe so... been so long ago I can barely remember :sweat_smile:


remove dev scripts in root directory

The following scripts do not function as intended. We should remove them from the primary package.json
dev:cleaninstall:calendar-tests
dev:cleaninstall:developer
dev:cleaninstall

Hey want to work on this issue allow me to proceed


People copying your mod

Well I came to talk about a serious matter, I always liked your mod (even if it is a mod that few people use) but to some people who are copying your mod giving no credit as for example a mod called MODDED, a mod that in reality I don’t even say that it’s a mod because it literally copies half of the mods and puts it on his mod without any credit like CrowdedMod that some prints he got from CrowdedMod and was saying that the CrowdedMod team help him put the mod on but in reality and everything lies about him:

Prints taken from the NodePolus server sent by przebot
Print the part he copied the mod from:

Prints of the mod "made" by Boss_GamerYT:

Discord server: https://discord.gg/dRMNZa7rcM
How to install tutorial by one of the server Administrators: https://youtu.be/ZG4hgUo7EBM
I sincerely just wanted you to talk to him on Discord, his Discord is: Boss_GamerYT# 0001
He will probably lie at first but then he will accept it and give credit

I agree that we have to do something with this. "EXTREME GAMER" is not respecting licenses nor our work.
He only added a little note "Mod made by CrowdedMods" after I told him that he has to do that (license).

Herysia is now fully able to submit DMCA infringement complaint to either Discord or Github.
I think we should also talk to them in Discord group chat first. @Herysia please notify me when you reply, we can collaborate on taking down license violators.

I can't take this guy anymore copying the mods and earning all the credits and still saying that the mod has "support" for mobile, as it does not modify the client side or the server (the server it just puts plugins that are also not made by him and yes plugins that people who made and put as open source on GitHub

I found another proof that he is copying his mod without giving any credit:


Support 2-way data binding (aka ng-model)

One of the first things I wanted to do in my {N} + Angular 2 app was add a simple form, but I found it difficult since <TextField [text]="foo"> only uses one-way data binding, and <TextField [(ngModel)]="foo"> doesn’t work.
Can we some up with some way to incorporate Angular 2’s two-way data binding, ideally with the same [(ngModel)] syntax?
Thanks.

[(ngModel)]="foo" desugars to [ngModel]="foo" (ngModelChange)="foo = $event", and we don't provide *Change events for most properties.
We could make this work for NativeScript dependency properties by attaching property change events automatically in the renderer whenever we get a fooChange event attach request.
This one needs more research, as I'm afraid we could easily end up with circular change events or zone exceptions (aka "causing a change during change detection").

@tjvantoll
After a #36 it is now possible to do two-way binding via '[ngModel]`. A sample usage should look similar to the following:
<Label [text]='model.test'></Label>
<TextField #name [ngModel]='model.test'></TextField>

Where model is {N} Observable.

How is this possible? I'm trying to build a simple login form and now after days learning and testing I found that 2 way DB is impossible with native script, so if this is not possible why TH NS released an angular version and it's promoting it as stable? Can you please provide an example? this is not working, if I place [ngModel] or [(ngModel)] or whatever I placed between brackets calling a model makes the application immediately crash, so, if this is not possible I wil have to alert the complete devs community to stay away from NS because honnestly it kind of feel like a scam. very disappointed.!!


Conversion to OG1: Variables missing attributes

This first conversion only renames variables.  But the OG1 format also expects attributes for the variables.  These haven't yet been added.  See tools.convert_to_og1() for ideas.

Added attributes in #11 but currently incomplete - missing some vocab details on the new velocity variables.

Added vocab details:
"GLIDE_ANGLE": {
     "long_name": "glide angle from hydrodynamic model",
     "units": "degrees",
     "observation_type": "calculated",
     "positive": "east",
     "comment": "Glide angle based on hdm",
 },
"GLIDE_SPEED": {
     "long_name": "glider speed from hydrodynamic model",
     "units": "m s-1",
     "observation_type": "calculated",
     "positive": "east",
     "comment": "Vehicle speed based on hdm",
 },
 "GLIDER_HORZ_VELO_MODEL": {
     "long_name": "glider_horizontal_speed_from_glider_flight_model",
     "standard_name": "horizontal_glider_speed",
     "units": "m s-1",
     "observation_type": "calculated",
     "sensor": "sensor_glider_model",
     "positive": "east",
     "comment": "Vehicle horizontal speed based on hdm",
 },
 "GLIDER_VERT_VELO_MODEL": {
     "long_name": "glider vertical speed from glider flight model",
     "standard_name": "vertical_glider_speed",
     "units": "m s-1",
     "observation_type": "calculated",
     "sensor": "sensor_glider_model",
     "positive": "up",
 },

Now completed with (#19)

Now addressed better with 'convertOG1.standardise_OG10()' which assigns the attributes now stored in 'vocabularies.vocab_attrs' which are read from 'config/OG1_vocab_attrs.yaml'.  See PR #33


fix: remove ISSUE_TEMPLATE dir name blank

hi @edeNFed ,sorry, the  ISSUE_TEMPLATE dir name  have blank.

@withlin no worries. thanks


Problem to access ASSISTments dataset

[Dataset]
ASSISTments dataset
[Question/Issue]
When using get_dataset("assistments"), I get an error (see screenshot). One dataset is downloaded, but not the proper one, I presume. Its name is skillbuilder-data-2009-2010.zip. I replicated the issue on two computers.
[Links to relevant documentation]
If applicable, provide links to any documentation you are following to access the data.
[Screenshots]

[Steps to reproduce]
Just try to get ASSISTments dataset with get_dataset("assistments").

I got the same problem. It occurs because the the code is trying to read a subset feather file. I just comment the comment/uncomment some lines.
https://github.com/ecostadelle/tableshift/commit/955927e613633f37f9de31fa2718cbb272fc498a


Usecase 7: Electric vehicles

This usecase tests the flexibility option of electric vehicles.

TODO

[x] Create Bev-facade
[x] Pass efficiency
[x] Pass tests
[x] Update Bev's attributes in component_atts
[x] Adapt update function
[x] Run the model
[x] Get complete results: I am not sure about what the scalars 'shifting' should mean. Will ask first. update: Got replaced by "Charging".
[x] Check results: Looks good. Only larger difference is in the marginal_cost: They are set on the vehicle-to-grid flow, not on the battery output flow. To set it in the latter way would require quite a lot of more work. Battery outflow comprises both the flow to drive power as well as the flow back to the grid. As the drive power is fixed exogenously, the part of the cost that really influences the results is similar (apart from the fact that there is an efficiency on vehicle-to-grid), so the main influence is in reporting. Will discuss this with the partners.

The usecase runs. Mapping results from oemoflex_scalars to the results template does not work yet - the numbers do not find their way into their place. This is because when filtering for the requested value, a series with an index is returned and not a float.
https://github.com/modex-flexmex/oemo-flex/blob/de08222b1cfd8eab3551eebaa86d6d180080ca4e/oemoflex/postprocessing.py#L547
I could not find out yet why this happens. This leads the script to fail transfering the data just a few lines below.
https://github.com/modex-flexmex/oemo-flex/blob/features/usecase-7/oemoflex/postprocessing.py#L560

Updated some files after changes on usecase 3 that affect this usecase here, too.
Since this usecase still needs some coding, here are the parts which may need a change if sequences from the Sink ('drive_power') subnode have to be processed.

Sink must be overwirtten just like Source and Transformer to let it have the carrier and tech property. Use the Source/inflow subnode as a template: https://github.com/modex-flexmex/oemo-flex/blob/991a08dd9a83ca29321d84c7178836fd78d01833/oemoflex/facades.py#L7-L19 and hand over the property values in init()
https://github.com/modex-flexmex/oemo-flex/blob/991a08dd9a83ca29321d84c7178836fd78d01833/oemoflex/facades.py#L488-L489

The drive_power subnode has to be kept in mind similar to... https://github.com/modex-flexmex/oemo-flex/blob/991a08dd9a83ca29321d84c7178836fd78d01833/oemoflex/postprocessing.py#L275-L276 ...and later, all nodes must be checked against it:
https://github.com/modex-flexmex/oemo-flex/blob/991a08dd9a83ca29321d84c7178836fd78d01833/oemoflex/postprocessing.py#L312-L313

An exception has to be added to the exclusion of bus subnodes: https://github.com/modex-flexmex/oemo-flex/blob/991a08dd9a83ca29321d84c7178836fd78d01833/oemoflex/postprocessing.py#L323-L324

Finally, the if conditions to rename the node at https://github.com/modex-flexmex/oemo-flex/blob/991a08dd9a83ca29321d84c7178836fd78d01833/oemoflex/postprocessing.py#L330-L338 have to be extended with:
         or isinstance(component, Source) and name[1] == 'drive_power'

...  if sequences from the Sink ('drive_power') subnode have to be processed.

They are fixed, so no new information on the drive power is created by running the model. So we will leave that out.


[FEATURE] ECM A-SOH objects should contain theoretical energy

Is your feature request related to a problem? Please describe.
No, everything works as it should. However, in some instances (especially when generating data from a pre-determined power profile that needs to be scaled by a maximum energy term), it becomes necessary to know the value of the maximum theoretical energy stored in the cell easily, instead of having to compute it separately.
Describe the solution you'd like
It would be nice if I could do energy = ECMASOH_obj.get_max_energy(temperature = temperature)
Describe alternatives you've considered
The main alternative is having this calculation being done on the application side.

Feature added by https://github.com/ROVI-org/auto-soh/pull/99


Fix warnings in dashboard theme

For a cleaner view of actual edits: https://github.com/concrete5/concrete5/pull/3218/files?w=1


crc16 is using internal crc with 32 bit size

https://github.com/EmbeddedRPC/erpc/blob/60a3cc1f84351cc3bf1af719d662e979a8f19b1c/erpc_c/infra/erpc_crc16.cpp#L32-L38
Maybe I am missing something.
Why can't the variables crc, temp, andValue , xorValue be uint32_t and byte be uint8_t ?
It makes things cleaner and I don't see it effects the algorithm

Hi @amgross , so only change you are suggesting is change byte to uint8_t correct?
I am not against it but we need be carefull. I think "byte<<8" can do undefined behavior. Compiler can throw away one byte. So we need recast it then ((uint16_t)(byte)) << 8

Oops, I wrote wrong, I mean:
Why can't the variables crc, temp, andValue , xorValue be uint16_t

About byte<<8,
Please see https://stackoverflow.com/questions/69143163/c-uses-different-data-type-for-arithmetic-in-the-middle-of-an-expression .
byte<<8 is equivalent to ((unsigned int)byte)<<8


:memo: README.md: why, purpose, api

You can see the render here: https://github.com/Trampss/trampss-redux-data-store/tree/readme

Thanks to all of you @delphinemillet  @Nebulis @guillaumecrespel @bpetetot
I merge this version.
Feel free to open issues if you'd like to.


Update clippy lint allow set.

This updates the clippy lints to default allow. We would prefer not to take clippy lint PRs at this time as there are a number of false positives and subjective style changes that we would rather not review.
I left a couple lints as warn that I have found useful when refactoring.

r? @Eh2406
(rust-highfive has picked a reviewer for you, use r? to override)

@bors r=Eh2406

:pushpin: Commit 376619d1765c558485bffabc33320841cd299394 has been approved by Eh2406

:hourglass: Testing commit 376619d1765c558485bffabc33320841cd299394 with merge 03e667f95c1ed925ab25929ca3325b7708ee9b0d...

:broken_heart: Test failed - checks-actions

@bors retry
macos job did not start

:hourglass: Testing commit 376619d1765c558485bffabc33320841cd299394 with merge e870eac9967b132825116525476d6875c305e4d8...

:sunny: Test successful - checks-actions
Approved by: Eh2406
Pushing e870eac9967b132825116525476d6875c305e4d8 to master...


Added OpsMx Spinnaker Operator support for v1.20.3

Signed-off-by: dvropsmx<EMAIL_ADDRESS>Thanks submitting your Operator. Please check below list before you create your Pull Request.

Flat operator directory structure is obsolete from 23-rd of October 2019, only nested directory structure will be accepted.

New Submissions

[ N ] Does your operator have nested directory structure?
[ Y ] Have you selected the Project Community Operator Submissions in your PR on the right-hand menu bar?
[ Y ] Are you familiar with our contribution guidelines?
[ Y ] Have you packaged and deployed your Operator for Operator Framework?

[ Y ] Is your submission signed?

Updates to existing Operators

[ ] Is your new CSV pointing to the previous version with the replaces property?
[ ] Is your new CSV referenced in the appropriate channel defined in the package.yaml ?
[ ] Have you tested an update to your Operator when deployed via OLM?
[ ] Is your submission signed?

Your submission should not

[ ] Modify more than one operator
[ ] Modify an Operator you don't own
[ ] Rename an operator - please remove and add with a different name instead
[ ] Submit operators to both upstream-community-operators and community-operators at once
[ ] Modify any files outside the above mentioned folders
[ ] Contain more than one commit. Please squash your commits.

Operator Description must contain (in order)

[ ] Description about the managed Application and where to find more information
[ ] Features and capabilities of your Operator and how to use it
[ ] Any manual steps about potential pre-requisites for using your Operator

Operator Metadata should contain

[ ] Human readable name and 1-liner description about your Operator
[ ] Valid category name1
[ ] One of the pre-defined capability levels2
[ ] Links to the maintainer, source code and documentation
[ ] Example templates for all Custom Resource Definitions intended to be used
[ ] A quadratic logo

Remember that you can preview your CSV here.
--
1 If you feel your Operator does not fit any of the pre-defined categories, file an issue against this repo and explain your need
2 For more information see here

@aswath2saru can you please sign it, since you are previous contributor. Thanks

@mvalahtv  I've Already Signed, Can you please approve ?

@dvropsmx Can i merge this one? It looks fine for me now.

@dvropsmx Can i merge this one? It looks fine for me now.

@mvalahtv , yes please. Thank you.


FitnessTrax: init at 0.1.0

Motivation for this change
This adds a fitness tracking application that I am developing.
Things done

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

[x] NixOS
[ ] macOS
[ ] other Linux distributions

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

Why doesn't your makefile do what is done in postInstall. I could see if I could find a project that does exactly this as an example.

Why doesn't your makefile do what is done in postInstall? I could see if I could find a project that does exactly this as an example.

I haven't seen makefiles in Rust projects before, but I've also not seen much in the way of Rust-based executables. Perhaps this is just a place where the ecosystem doesn't have sufficient known standards?
If you have an example, I would definitely follow it. Otherwise, I thought I had seen in my experiments that the shared/ folder just doesn't get copied into the destination.

Why doesn't your makefile do what is done in postInstall? I could see if I could find a project that does exactly this as an example.

GLib provides https://gitlab.gnome.org/GNOME/glib/-/blob/master/m4macros/gsettings.m4, but you 'd need to use autotools. In that case I would really just recommend using meson.

Oh, I thought you were using makefile somehow from looking at your project. Nevermind that then.

I think you might want to delete this file from your repo https://github.com/luminescent-dreams/fitnesstrax/blob/sol/share/glib-2.0/schemas/gschemas.compiled. It's compiled but not meant to be distributed in that sense.

I think you might want to delete this file from your repo https://github.com/luminescent-dreams/fitnesstrax/blob/sol/share/glib-2.0/schemas/gschemas.compiled. It's compiled but not meant to be distributed in that sense.

I'll do that in the next release. I recall needing it to get the derivation right, but it may have been an intermediate step while I was flailing.

Having addressed the changes, @worldofpeace and I get different sha256sums on the cargo file. I'm going to hold off until a few days and try stabilizing things on nixos-unstable, as suggested in IRC.

I noticed something up with your deps, which I actually fixed for you https://github.com/NixOS/nixpkgs/pull/83336/commits/a9f12d5f5ab2dd733f3cf43270d87f7e121f8a68.
Only system libs you'd need would have been for gtk-rs.

@worldofpeace I am not sure how to proceed. I had no idea that you could make a commit to a PR from a remote repository, so I don't know how to integrate this into my PR.
And, I don't understand the error that grahamcofborg-eval is reporting.
What do you advise as my next step?

@savannidgerinel Just pull from origin.
The error is a problem with ofborg that graham is fixing/maybe fixed.
Will try an eval
@GrahamcOfBorg build fitnesstrax
But generally, if you could build the package it should be fine.
(though the metadata could be messed up, but I don't think it is)

@savannidgerinel Squash merged, thanks :sparkles:


Test for array

Coverage remained the same at 100.0% when pulling 7266dbf762663e9f8848dbbdcb4a2ad9cb820ec6 on staging into 0f32728a92634befe9b9d0e07c07cd936ab42407 on master.

Coverage remained the same at 100.0% when pulling 7266dbf762663e9f8848dbbdcb4a2ad9cb820ec6 on staging into 0f32728a92634befe9b9d0e07c07cd936ab42407 on master.


Spawner module features not working

I'm playing on version 1.18.2 and simply the spawn egg was placed and it went back to the monster that was in the spawner. And there are also upgrades to the spawner that don't work like ignoring light.

1.18 was not developed by me and is not supported.


Zappr Demo

:+1:

:+1:

:+1:

:+1:

[Current coverage][cc-pull] is 52.19%

Merging [#433][cc-pull] into [master][cc-base-branch] will increase coverage by +5.74%

2 files (not in diff) in ...o/stups/fullstop/web were modified. more

Partials -6
Hits +6

2 files (not in diff) in ...lando/stups/fullstop were modified. more

Misses -5
Partials -2
Hits +7

2 files (not in diff) in ...tion/repository/impl were modified. more

Misses -1
Partials -20
Hits +21

5 files (not in diff) in ...top/violation/entity were modified. more

Misses -14
Partials -5
Hits +19

1 files (not in diff) in ...s/fullstop/violation were modified. more

Partials -4
Hits +4

2 files (not in diff) in ...tups/fullstop/domain were modified. more

Misses -2
Hits +2

2 files (not in diff) in ...lando/stups/fullstop were modified. more

Misses -1
Partials -2
Hits +3

2 files (not in diff) in ...ugin/unapproved/impl were modified. more

Misses -1
Partials -2
Hits +3

2 files (not in diff) in ...op/plugin/unapproved were modified. more

Partials -8
Hits +8

2 files (not in diff) in ...tups/fullstop/plugin were modified. more

Misses -1
Partials -4
Hits +5

@@             master       #433   diff @@
==========================================
  Files           133        133
  Lines          3102       3102
  Methods           0          0
  Messages          0          0
  Branches        257        257
==========================================
+ Hits           1441       1619   +178
+ Misses         1591       1483   -108
+ Partials         70          0    -70

Powered by Codecov. Last updated by [93725be...db35474][cc-compare]
[cc-base-branch]: https://codecov.io/gh/zalando-stups/fullstop/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/zalando-stups/fullstop/compare/93725be92dcb0f69155ff157b6d327fd4b334aca...db354741bf97b7c7c8dabec528f88ae4351b25dd
[cc-pull]: https://codecov.io/gh/zalando-stups/fullstop/pull/433?src=pr

:-1:

:-1:

:-1:


Handle multiple tokens in Connection header when routing WebSocket

Parse the Connection header, in case it comes with multiple tokens (as seen in WebSocket requests sent by Firefox).

fixes #2131

Checklist:

[x] Add tests that demonstrate the correct behavior of the change. Tests should fail without the change.
[ ] Add or update relevant docs, in the docs folder and in code.
[x] Add an entry in CHANGES.rst summarizing the change and linking to the issue.
[ ] Add .. versionchanged:: entries in any relevant code docs.
[x] Run pre-commit hooks and fix any issues.
[x] Run pytest and tox, no tests failed.

This can target the 2.0.x branch.


New version: Hugo.Hugo.Extended version 0.139.2

Created by 🥟 Dumplings in workflow run #9763.

Log
Updated: 0.139.1 → 0.139.2
Submitting WinGet manifests
Creating manifests
Uploading manifests and making commits
Creating a pull request

Microsoft Reviewers: Open in CodeFlow

Automatic Validation ended with:

Installation failed with exit code -1978335187
2024-11-23 08:19:40.772 [FAIL] Installer failed security check. Url: https://github.com/gohugoio/hugo/releases/download/v0.139.2/hugo_extended_0.139.2_windows-amd64.zip Result: 0x80004005

Automated error analysis suggests -1978335187 may mean Installer failed security check. Another script should retry this every 18 hours.
Automated error analysis suggests 80004005 may mean Resource missing
(Automated response - build 899.)

@stephengillie manual validation needed.


merge from arlac77/fetch-rate-limit-util

package.json

merge from template package.json

.travis.yml

chore(travis): (jobs.include.node_js)
chore(travis): remove --delete-- (jobs.include.deploy.skip_cleanup)

:tada: This PR is included in version 1.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


rename --yes to --auto-accept

--yes is not descriptive enough of the intent behind the feature flag.
closes #174

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

Codecov Report

Merging #204 into master will not change coverage.
The diff coverage is 0%.

@@           Coverage Diff           @@
##           master     #204   +/-   ##
=======================================
  Coverage   32.94%   32.94%
=======================================
  Files          18       18
  Lines        1108     1108
=======================================
  Hits          365      365
  Misses        694      694
  Partials       49       49

Impacted Files
Coverage Δ

cmd/draft/init.go
2.41% <0%> (ø)
: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 63a6da1...564cee0. Read the comment docs.


Add export to tsrafc

This PR adds an export to tsrafc to mirror its JavaScript version.

@Drakeoon bump 🙏


add release body

is it possible to add a release body? for example, with the actions/create-release@v1 action you can do this:
    - name: Create Release
      id: create_release
      uses: actions/create-release@v1
      env:
        GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} # This token is provided by Actions, you do not need to create your own token
      with:
        tag_name: ${{ github.ref }}
        release_name: Release ${{ github.ref }}
        body: |
          This is an automated release. See [the Changelog](link to my changelog) for more info.
        draft: false
        prerelease: false

electron-builder already supports a release-notes.md in the build resources folder, maybe there could be a setting to publish these release notes? That'd be awesome and save me a lot of manual work too.


chore(dependencies): Update dependencies.

Also updated --check flag to have an explicit off option.

@acederberg What's your use case for having --no-check? I would like to remove --no-check, because it makes --help and README.md easier to the eye. But I may be missing why --no-check is useful. Thanks!

I just thought it would be nice to give it explicitly for scripts and what not in case the default value changes. Mostly, I did this out of habit and we would probably be fine without it tbh.

@acederberg Thank you for information. I've removed --no-check and published made a new release. I've realized --check is not a 100% toggle. It mirrors the behavior of prettier --check.
https://github.com/shamrin/codeblocks/commit/773a83fe6fe59939427ea6c0a7102eab621fa11b


Add/improve labels in banner when viewing an entity from Docs

When viewing an entity from the Docs link, the banner may confuse users for the following reasons:

The "Component" label is misleading; a kind: Resource entity can also have documentation
The <> icon may not be intuitive to a non-technical users

Feature Suggestion

Update the "Component" label to "Entity"
Add source label below the <> icon

Possible Implementation

Context
As a new Backstage user, I was confused by the some of the labels when viewing an entity from the Docs link

@anilazaidi Great observations! Both of the suggestions definitely make sense 💯

These seem to be quick fixes that I can work on :)

Thank you so much!!

Hi @anilazaidi and @utkarsh867, for this item: "The "Component" label is misleading; a kind: Resource entity can also have documentation" should the solution not be to use the Kind name? So in the example should it not say Resource for a Resource or API for an API? I don't think "Entity" is generally used in the UI

Hi @awanlin , to be honest, and this is just a personal opinion, I wish the UI used the term "entity" rather than "component". Mainly b/c this is the term used in Backstage docs and it eliminates the confusion with kind: Component...

But it sounds like you're saying that the "Component" label is actually resolved per the kind of the entity? Is this true?

Hi @anilazaidi, that's fair and I agree with your original comment that having this say "Component" when you are looking at a "Resource" would be confusing, sorry if that wasn't clear. I see Entity as being a generic term for all Kinds, but if we have the information to provide the proper detail then we should. This also gets us a bit of consistency with the Catalog views where it does that already.

but if we have the information to provide the proper detail then we should.

Makes sense!

Thanks so much @Rugvip!!


Allow the user to override CNI namespace

Closes https://github.com/istio/istio/issues/18640.

unless this is a workaround for an operator limitations

I think each component has a namespace field, so something like cni.namespace=something? Not sure if that works

It seems cni.components.cni.namespace works, let me try.

It works, thanks.
(BTW, That's a lot confusing!)


Trace value set dependencies

In the data requirements gather, if a value set is composed of multiple value sets, those are not reported as dependencies during the requirements gather. The gather should trace dependencies of composes if the gather is recursive.

This fix is likely to be needed in the DataRequirementsProcessor in the translator.


ChangeSmartArt & SmartArtColorStyle package issues

Two classes have the wrong package declarations.
They are defined as;
package com.aspose.slides.examples.SmartArt.managingsmartartstyle;
But are in the structure for;
package com.aspose.slides.examples.SmartArt.ManageSmartArtStyle;

Fixed, please refresh again from GitHub.

Any reason why you picked camel case names for package names.
Just wondering as both Sun and now Oracle recommend package names are all lower case, so avoid potential conflict with classes and interfaces.
https://docs.oracle.com/javase/tutorial/java/package/namingpkgs.html

Thanks for asking. Yes, we know that lower case scheme is recommended for package names. But, we did this for our plugins for various platforms e.g. see https://plugins.jetbrains.com/plugin/7461?pr=idea. In one of the screenshots, you will notice there are categories like "Working with BarCode Image". The word detection in the plugins is dependent on our CamelCase package naming. If we use all lower case, the plugin would just show "workingwithbarcodeimage" which would be bad for UI and also a bad category name.
We also noticed at http://docs.oracle.com/javase/8/docs/api/ and there are many packages at the end, which use camel case scheme.


edge: Fixes integration tests

Unpins pytest-operator, the issue mentioned has been fixed and released. We've updated to juju v3.0, and thus, the juju actions work a bit differently.

Integration tests are passing.


the package currently favors an ssh setup that doesn't expect to be prompted for credentials

Also, the package currently favors an ssh setup that doesn't expect to be prompted for credentials in order to push/pull, .etc.

How do I setup my git / ssh to not ask for credentials ever more?

Here you go

I have done as written in your post (ssh-agent etc). It is still asking for my password. I am not using github, rather our own gitlab installation. What do I have to do?

I don't know. I don't use gitlab. My best suggestion is look for help in their help documentations


Generic Linux Build

I'm working on updating some of our impeller-cmake integration and decided to take some steps backwards to increase my familiarity with the codebase. First step in that area is building this repo.
I have a few questions about building this for generic linux (I'm currently working on GLinux though I think this should apply to most debian based distributions).

Do you think it's worthwhile attempting to build this for generic linux at all? That is, do you think adequate support for X11 or something else is in place to at least make it theoretically possible?

I previously wan't familiar with VSCode based CMake Tools, but I've read up on it some. I'll post an image of my config below but bascially I'm choosing the Ninja Debug configuration. Looking at the contents of the .vscode/settings.json it looks like the required CMake command is complex enough to require the use of CMake Tools rather than just invoking it on the command line. All that said, would you think the following configuration might support generic linux?

Building the example target in this way I seem to be defaulting to  clang++ (clang 16 on my system) as the default compiler, but I'm not  easily getting both  cmake and make logs from the vscode CMake Tools. Any suggestions where I can get those?

Next, my build currently fails on a trivial issue:

`/home/johnoneil/code/impeller-cmake-example/third_party/assimp/code/AssetLib/LWS/LWSLoader.cpp:519:49: error: variable 'num_object' set but not used [-Werror,-Wunused-but-set-variable]
   unsigned int num_light = 0, num_camera = 0, num_object = 0;

So I believe I can alleviate this by adding the -Wunused-but-set-variable flag, but where should I do this ? (if you don't have a better suggestion) I imagine I must enter the proper argument in .vscode/settings.json so that it will be passed to the cmake call, introducing the correct flags into the make build. I'll research this some but the levels of indirection are blocking me.

I'm very likely to want to build this with clang++-15 rather than my current default of clang++-16. Any suggestion for the best way to inject an alternate compiler in the the current workflow?

Any further suggestions are appreciated. If I can build and run this in my current Environment I'd probably submit a PR of my findings as additions to the current README.

Okay I believe I was able to get past all my issues via the following:

Did a clean checkout of repo, ensuring on I'm the latest, recursively fetching all submodules.
Ran deps.sh
Chose Ninja Debug configuration for CMake tools
**Manually edited the following line in CMakePresets.json to match the configuration of my current system (once again note I'm building on a debian based Linux):

"CMAKE_AR": "llvm-ar-16"

After that the example built and ran cleanly as per the following image:

I think this closes this issue, but I will experiment with building with clang++-15 the following:
If we think any additional pure linux instructions would be helpful in the README.md I can provide that.


Error on subclassing Dict[Any, ...]

Based on https://github.com/omry/omegaconf/pull/502#discussion_r605832350, it is proposed to deprecate support for structured configs that subclass Dict[Any, ...], with only subclasses of Dict[str, ...] being supported going forward.
For example, creating a structured config node based on the following dataclass would issue a deprecation warning,
@dataclass
class MyConf(Dict[int, Any]):
    ...

while a structured config node based on the following would be fully supported:
@dataclass
class MyConf(Dict[str, Any]):
    ...

class MyConf(Dict[int, Any])

This is not supported in 2.0, we can just straight to error with it.

I thought the idea was that subclassing Dict[str, str] is deprecated and subclassing Dict[int, str] or Dict[Any, str] should give an error message...
If you still want to go that route, I can try to get a PR ready tonight.

Oh yeah, sorry.

Closing since we've already deprecated subclassing Dict in general.


Beats icons

uploaded beats icons to https://helm.elastic.co/icons/beats.png
fixed icons name in *beats/Chart.yml

These icons will be available on https://hub.helm.sh/charts/elastic after next release.

skip ci

jenkins skip ci


not working on macOS

I've followed the instructions exactly but still can't transcribe audio file in a few minutes.
insanely-fast-whisper --file-name /[test].wav --device-id mps
🤗 Transcribing... ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 0:00:02You have passed task=transcribe, but also have set forced_decoder_ids to [[1, None], [2, 50360]] which creates a conflict. forced_decoder_ids will be ignored in favor of task=transcribe.
🤗 Transcribing... ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 0:00:17Passing a tuple of past_key_values is deprecated and will be removed in Transformers v4.43.0. You should pass an instance of EncoderDecoderCache instead, e.g. past_key_values=EncoderDecoderCache.from_legacy_cache(past_key_values).
🤗 Transcribing... ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 0:00:20The attention mask is not set and cannot be inferred from input because pad token is same as eos token. As a consequence, you may observe unexpected behavior. Please pass your input's attention_mask to obtain reliable results.
🤗 Transcribing... ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 0:00:46
it's getting stuck here and transcribing forever

same exact messages but not stuck, just slow

I'm having the same issue. Command is insanely-fast-whisper --file-name test.mp3 --device-id mps --model-name distil-whisper/distil-large-v3 or insanely-fast-whisper --file-name test.mp3 --device-id mps --model-name openai/whisper-large-v3-turbo, with or without --batch-size 4

I get these too, but it works still. About 30 minutes for an 90 minute episode of a show.


chore(monorepo): use --cache option when running eslint and prettier.

Overview
Speed up local development by using the cache option for eslint and prettier, which will only check changed files by default.

@sfoster1
Yeah, I see the same issue when running that snippet, I can't reproduce it when just running make lint-js manually though. We can do without thorough if we have reason to believe this will cause some issues.

I bet he was probably running into errors that kept mysteriously persisting, since he was focused on removing them. I don't think it works very well.

I looked at #15402 when I made the changes in bac3633 but I don't see in Brian's PR why he had to remove cache?

I think Brian removed cache option because of this

Sounds good, will close!


Extraneous printout when using posix polling engine

##It looks like the merge pull request #5456 causes some regression. When this latest change, I am getting the following code printed on the console 'Using polling engine: poll'  This seems to come from the following code in ev_posix.c - in order to work around this, I had to temporarily comment this log statement out.
static void try_engine(const char *engine) {
  for (size_t i = 0; i < GPR_ARRAY_SIZE(g_factories); i++) {
    if (is(engine, g_factories[i].name)) {
      if ((g_event_engine = g_factories[i].factory())) {
        gpr_log(GPR_DEBUG, "Using polling engine: %s", g_factories[i].name);
        return;
      }
    }
  }
}

yes, i meet it too  !

from here I found that using env var GRPC_VERBOSITY  can filter these outputs ...

i think the default should be info

If GRPC_VERBOSITY environment variable is not set, the default logging level is ERROR.
So this log statement will not be logged.
I am closing the issue.


[Enhancement - Notifications] Create the Notifications List View Screen

🙋 feature request
This feature will be a replacement for the Fix Central Screen. It will contain both Paladin Cloud notification + external sources

🤔 Expected Behavior

😯 Current Behavior

💁 Possible Solution

🔦 Context

💻 Examples

working on this

This screen was created internally


Change TablesNeedUpgradeSysCheck to check for re-index requirement

Summary of the changes / Why this improves CrateDB
The check with ID 3 was initially the sys-check that checked for tables
that need to be re-created (See commit da9a66e918b57c487d56a6ec3ae6bbed60b7db93)
This changes the logic of the check back to check for the re-index
requirement as a segment upgrade alone isn't sufficient to make tables
compatible for the next major version.
It also changes the severity to low (given that no action has to be
taken if there are no immediate upgrade plans).
Within CrateDB 4.x this will trigger for tables created in 3.x.
With a backport to 3.3 this will trigger for tables created in 2.x.
Checklist

[x] User relevant changes are recorded in CHANGES.txt
[x] Touched code is covered by tests
[x] Documentation has been updated if necessary
[x] CLA is signed
[x] This does not contain breaking changes, or if it does:

It is released within a major release
It is recorded in CHANGES.txt
It was marked as deprecated in an earlier release if possible
You've thought about the consequences and other components are adapted
(E.g. AdminUI)

but I'd drop the "re-index" and replace it with "recreate table"

right, I've adapted the wording.


Tab Color only works with 4+ tabs.

Less than 4 tabs the function to set color does not work.

any solution ?

Any solution for this? I don't this library is being maintained now :(

Any news?

no news :(

To change it, you'll have to change the variable in the BottomNavigationBar's BottomBar.cs file. The variable in question is private int _maxFixedTabCount = 3;, you'll need to change it to 2, 1, or 0. Then recompile, add the DLL to BottomNavigationBarXF, and then recompile this one, and add the DLLs to your Forms project.

@sme90 variant with DLL is good, but u can also create local nuget package: just type 'nuget pack' in the root folder and use it. [http://stackoverflow.com/questions/10240029/how-to-install-a-nuget-package-nupkg-file-locally](How to install let local nuget package)


Auto-format sometimes jumps to a different position if Editor > Display > Wrap lines is set

Issue Report Checklist

[x] Searched the issues page for similar reports
[x] Read the relevant sections of the Spyder Troubleshooting Guide and followed its advice
[ ] Reproduced the issue after updating with conda update spyder (or pip, if not using Anaconda)
[ ] Could not reproduce inside jupyter qtconsole (if console-related)
[x] Tried basic troubleshooting (if a bug/error)

[x] Restarted Spyder
[x] Reset preferences with spyder --reset
[ ] Reinstalled the latest version of Anaconda
[x] Tried the other applicable steps from the Troubleshooting Guide

[x] Completed the Problem Description, Steps to Reproduce and Version sections below

Problem Description
One of our users has reported that auto-format with Black still sometimes jumps to a different place in the file.  It's not as dramatic as in #19958 (closed), but it's still clearly unideal.
The full report, including a video showing the behaviour and a Python script exhibiting the behaviour are attached: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034085
Below I describe the minimum needed to trigger this bug with this Python script.  I am working with Spyder 5.4.2 on Linux (Debian is currently in freeze, so I can't update Spyder for a few months) and Spyder 5.4.3 on a Mac, and they both exhibit this behaviour.
What steps reproduce the problem?

Reset spyder preferences
Start spyder
In preferences, select Editor > Display > Wrap lines
Open practice.py (attached to this issue as practice.py.txt)
practice.py.txt
Go to line 270 and remove a space around the // operator
Right-click and select "Format file or selection with Autopep8"

What is the expected output? What do you see instead?
The cursor jumps back to line 264.  The same happens with Black.  The cursor shouldn't jump.
On the other hand, if I have a shorter file with only the sort_nums function, it doesn't exhibit this undesired behaviour.
Paste Traceback/Error Below (if applicable)
See the Debian bug report for a screencast.
 I was able to reproduce this. I think the wrap lines functionality has an issue open so my guess is that this could be related with that one (https://github.com/spyder-ide/spyder/issues/20802). We will try to fix this in a future release :+1.


Rename static method format to fromFormat for clarity

At the moment, the application exceptions are built using the method format, this method returns an new instance of the exception. I think it would be clearer to call this method fromFormat as this is a factory method.

The method will be renamed fromTemplate as it sounds better


Implement read-only state

Fixes #110
This might not be the best code, however it seems like a clean way to make a read-only state without using a hidden computed.

Marking this as a draft until unit tests are written.

This doesn't feel like the right implementation. If I'm reading the code correctly, using this method makes the Value read only for everyone, not just further consumers. To be able to make use of this, you'd end up needing a dummy Value anyway since you'll surely still need to update the original Value object.
Issue #110 suggests a ReadOnly(CanBeState) that returns a new read only state object, allowing you to still update the original CanBeState and passing the ReadOnly object to further consumers.
Frankly, it sounds like ReadOnly will operate nearly identical to just Computed(function() return use(CanBeState) end), but perhaps with some shortcuts internally.

Hmmm, I didn't want to use a computed but I might need to in this case unfortunately.

Closing until #216 is merged due to the update with dependencies.