📝 Add leonidasv.com to Users list

Adds leonidasv.com to Users page.

PS: I have another branch I'd like to submit a Pull Request from, so I've started a discussion, as detailed in the Contribution guidelines. So I'd like to ask for your brief attention to my proposal: https://github.com/jpanther/congo/discussions/512
PPS: I've also found some gaps in the documentation (fill="currentColor" for icons, mentioning that you add a custom icon and use it in languages.__.toml, some advanced CSS configs, such as importing Tailwind default colors and overriding the main.css, etc). Can I just submit a Pull Request with those additions or should I open a Discussion too?
Thanks for developing and making this theme open-source, this is the most well-crafted blog theme I've used in a long time.

Thanks for using Congo, @leonidasv! I'll merge this change in and your site will appear on the public list when the next theme release is published.
I'm happy for you to submit a PR with the documentation updates. There's lots of little things like the SVG fill that would be good to have in the docs as the questions come up frequently. I'll have a look at your discussion on the other changes and address those there.


Markdown: Sticky "Show Source" action

Steps to Reproduce (tried this from master with the grid work included):

open some files
open a markdown preview
move it into the first editor group (provided it opened to the side before)
close the markdown preview
🐛 notice how the next active editor gets a "Show Source" action

Another case:

Open markdown file
Open preview in same column
Close preview

Bug
Markdown: show source command still visible


ffmpeg_5,ffmpeg_5-full: cherry-pick IPFS default gateway removal

Description of changes
ffmpeg 5.1 introduced ipfs:// and ipns:// streaming support as part of
libavformat. This new implementation falls back to fetching from an
untrusted 3rd party internet service in the (likely) case where a user
doesn't have a local IPFS gateway running on their computer. This puts
an unaudited 3rd party provider in a position where they can log and
alter any IPFS content being streamed by the ffmpeg library. No user
consent is collected at any point by the library.
ffmpeg developers are currently discussing [1] how to better implement
this feature. In the meantime, cherry-pick the proposed patch to disable
the default gateway until a better alternative is released.
[1] https://ffmpeg.org/pipermail/ffmpeg-devel/2022-August/299924.html
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Changed this at @mweinelt's request to instead cherry-pick the WIP patch from @dwbuiten and keep the protocol support enabled, just without the default gateway.

(cc @zowoq for possible input since you took care of the last ffmpeg_5 version bump)

FWIW, Alpine has also cherry-picked the patch: https://git.alpinelinux.org/aports/commit/community/ffmpeg?id=26932f57b66ce3ccbad495562ac7c8e83f2ee47d

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

4 packages built:

ffmpeg_5
ffmpeg_5-full
jellyfin
jellyfin-ffmpeg


cant download libxml2 for windows 10

i know there are similar questions but i tried everything and nothing seems to work...
i cant download python3-saml without xmlsec, and cant download xmlsec without libxml2
for example after donwloading the file manually (libxml2-2.9.4.tar) and pip installing it i get the error :
(venv) C:\Users\user\PycharmProjects\onelogintest>pip install libxml2-2.9.4.tar.gz
Processing c:\users\user\pycharmprojects\onelogintest\libxml2-2.9.4.tar.gz
Complete output from command python setup.py egg_info:
Traceback (most recent call last):
File "", line 1, in
File "C:\Users\user\AppData\Local\Programs\Python\Python38-32\lib\tokenize.py", line 392, in open
buffer = _builtin_open(filename, 'rb')
FileNotFoundError: [Errno 2] No such file or directory: 'C:\Users\user\AppData\Local\Temp\pip-req-build-veuc4n_9\setup.py'
----------------------------------------

Command "python setup.py egg_info" failed with error code 1 in C:\Users\user\AppData\Local\Temp\pip-req-build-veuc4n_9\
please help im really stuck

It should be available.


Possible deadlock with SQLite backend

See: https://github.com/requests-cache/aiohttp-client-cache/discussions/146

Originally posted by AIGeneratedUsername January  4, 2023
0.7.3 version works fine, but when I install 0.8.0, my Pytest tests results in:
======================================================== test session starts =========================================================
platform linux -- Python 3.10.9, pytest-7.2.0, pluggy-1.0.0

[A LIST OF MY TESTS HERE, NOT IMPORTANT]

================================================= 1 passed, 208 deselected in 4.16s ==================================================

In other words, after all tests the session hangs forever.

Thank you. The described problem was fixed in 0.8.1.


Check for overlap

Codecov Report

Merging #62 (01b29a8) into master (9c3e0be) will increase coverage by 0.11%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master      #62      +/-   ##
==========================================
+ Coverage   92.54%   92.66%   +0.11%
==========================================
  Files          11       11
  Lines         872      886      +14
==========================================
+ Hits          807      821      +14
  Misses         65       65

Impacted Files
Coverage Δ

src/bonds.jl
94.26% <100.00%> (ø)

src/cordero.jl
100.00% <100.00%> (ø)

src/crystal.jl
90.27% <100.00%> (-0.10%)
:arrow_down:

src/distance.jl
93.24% <100.00%> (+2.17%)
: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 3bc26f2...01b29a8. Read the comment docs.

@ngantzler @eahenle you two ok with this? I worked on it more after group meeting.
interestingly the overlap tripped for CAXVII_clean.cif and indeed on closer inspection the O is a little too close to the C!
so it will be useful. not really a 100% principled way of searching for overlap but I think this is better than before. and still gives the option of using a r_crit that is different/custom. when this trips, just load the crystal with check_overlap=false which should be apparent from the error message.

Subsumed by #65.  Closing.


Rotate Gizmo's not showing in WSL 2

Environment

OS Version: Windows 10 Enterprice, with WSL 2 running Ubuntu 22.04.1 LTS (Ignition is running in WSL)

binary, version 6.12.0
- [ X ] running on a dual GPU machine (integrated GPU + discrete GPU)
- [ ] running on a multi-GPU machine (it has multiple discrete GPUs)
- [ ] running on real hardware
- [ ] running in virtual machine
- [ ] running in Docker/Singularity
- [ ] running remotely (e.g. via SSH)
- [ ] running in a cloud
- [ ] using VirtualGL, XVFB, Xdummy, XVNC or other indirect rendering utilities
- [ ] GPU is concurrently used for other tasks
  - [ ] desktop acceleration
  - [ ] video decoding (i.e. a playing Youtube video)
  - [ ] video encoding
  - [ ] CUDA/ROCm computations (Tensorflow, Torch, Caffe running)
  - [ ] multiple simulators running at the same time
- [ X ] other WSL 2

Rendering system info:

I use XLaunch for the visualization. In the Ubuntu box, I have entered the following:
export DISPLAY="`grep nameserver /etc/resolv.conf | sed 's/nameserver //'`:0"
export LIBGL_ALWAYS_SOFTWARE=1
export LIBGL_ALWAYS_INDIRECT=0

from Ubuntu
name of display: <IP_ADDRESS>:0
display: <IP_ADDRESS>:0  screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
    Vendor: Mesa/X.org (0xffffffff)
    Device: llvmpipe (LLVM 13.0.1, 256 bits) (0xffffffff)
    Version: 22.0.5
    Accelerated: no
    Video memory: 12652MB
    Unified memory: no
    Preferred profile: core (0x1)
    Max core profile version: 4.5
    Max compat profile version: 4.5
    Max GLES1 profile version: 1.1
    Max GLES[23] profile version: 3.2
OpenGL vendor string: Mesa/X.org
OpenGL renderer string: llvmpipe (LLVM 13.0.1, 256 bits)
OpenGL core profile version string: 4.5 (Core Profile) Mesa 22.0.5
OpenGL core profile shading language version string: 4.50
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile

OpenGL version string: 4.5 (Compatibility Profile) Mesa 22.0.5
OpenGL shading language version string: 4.50
OpenGL context flags: (none)
OpenGL profile mask: compatibility profile

OpenGL ES profile version string: OpenGL ES 3.2 Mesa 22.0.5
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20

From Windows:
NVIDIA Quadro T2000
DirectDraw: enabled
Direct3D: enabled
AGP Texture: enabled

- [ X ] Please, attach the ogre.log or ogre2.log file from  `~/.ignition/rendering`

```
16:09:28: Creating resource group General
16:09:28: Creating resource group Internal
16:09:28: Creating resource group Autodetect
16:09:28: SceneManagerFactory for type 'DefaultSceneManager' registered.
16:09:28: Registering ResourceManager for type Material
16:09:28: Registering ResourceManager for type Mesh
16:09:28: Registering ResourceManager for type Mesh2
16:09:28: Registering ResourceManager for type OldSkeleton
16:09:28: MovableObjectFactory for type 'ParticleSystem' registered.
16:09:28: ArchiveFactory for archive type FileSystem registered.
16:09:28: ArchiveFactory for archive type Zip registered.
16:09:28: ArchiveFactory for archive type EmbeddedZip registered.
16:09:28: DDS codec registering
16:09:28: FreeImage version: 3.18.0
16:09:28: This program uses FreeImage, a free, open source image library supporting all common bitmap formats. See http://freeimage.sourceforge.net for details
16:09:28: 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:09:28: OITD codec registering
16:09:28: Registering ResourceManager for type HighLevelGpuProgram
16:09:28: MovableObjectFactory for type 'Decal' registered.
16:09:28: MovableObjectFactory for type 'InternalCubemapProbe' registered.
16:09:28: MovableObjectFactory for type 'Entity' registered.
16:09:28: MovableObjectFactory for type 'Item' registered.
16:09:28: MovableObjectFactory for type 'Light' registered.
16:09:28: MovableObjectFactory for type 'Rectangle2Dv2' registered.
16:09:28: MovableObjectFactory for type 'BillboardSet' registered.
16:09:28: MovableObjectFactory for type 'ManualObject2' registered.
16:09:28: MovableObjectFactory for type 'BillboardChain' registered.
16:09:28: MovableObjectFactory for type 'RibbonTrail' registered.
16:09:28: MovableObjectFactory for type 'WireAabb' registered.
16:09:28: *-*-* OGRE Initialising
16:09:28: *-*-* Version 2.2.5 (Cerberus)
16:09:28: OverlayElementFactory for type Panel registered.
16:09:28: OverlayElementFactory for type BorderPanel registered.
16:09:28: OverlayElementFactory for type TextArea registered.
16:09:28: Registering ResourceManager for type Font
16:09:28: Loading library /usr/lib/x86_64-linux-gnu/OGRE-Next/RenderSystem_GL3Plus.so
16:09:28: Installing plugin: GL 3+ RenderSystem
16:09:28: OpenGL 3+ Rendering Subsystem created.
16:09:28: Found Num EGL Devices: 1
16:09:28: EGL Device: EGL_MESA_device_software EGL_EXT_device_drm_render_node #0
16:09:28: Trying to init device: EGL_MESA_device_software EGL_EXT_device_drm_render_node #0...
16:09:28: Created GL 4.5 context for device EGL_MESA_device_software EGL_EXT_device_drm_render_node #0
16:09:28: Destroying device: EGL_MESA_device_software EGL_EXT_device_drm_render_node #0...
16:09:28: Plugin successfully installed
16:09:28: Loading library /usr/lib/x86_64-linux-gnu/OGRE-Next/Plugin_ParticleFX.so
16:09:28: Installing plugin: ParticleFX
16:09:28: Particle Emitter Type 'Point' registered
16:09:28: Particle Emitter Type 'Box' registered
16:09:28: Particle Emitter Type 'Ellipsoid' registered
16:09:28: Particle Emitter Type 'Cylinder' registered
16:09:28: Particle Emitter Type 'Ring' registered
16:09:28: Particle Emitter Type 'HollowEllipsoid' registered
16:09:28: Particle Affector Type 'LinearForce' registered
16:09:28: Particle Affector Type 'ColourFader' registered
16:09:28: Particle Affector Type 'ColourFader2' registered
16:09:28: Particle Affector Type 'ColourImage' registered
16:09:28: Particle Affector Type 'ColourInterpolator' registered
16:09:28: Particle Affector Type 'Scaler' registered
16:09:28: Particle Affector Type 'Rotator' registered
16:09:28: Particle Affector Type 'DirectionRandomiser' registered
16:09:28: Particle Affector Type 'DeflectorPlane' registered
16:09:28: Plugin successfully installed
16:09:28: CPU Identifier & Features
16:09:28: -------------------------
16:09:28:  *   CPU ID: GenuineIntel: Intel(R) Core(TM) i7-9850H CPU @ 2.60GHz
16:09:28:  *   Logical cores: 12
16:09:28:  *      SSE: yes
16:09:28:  *     SSE2: yes
16:09:28:  *     SSE3: yes
16:09:28:  *      MMX: yes
16:09:28:  *   MMXEXT: yes
16:09:28:  *    3DNOW: no
16:09:28:  * 3DNOWEXT: no
16:09:28:  *     CMOV: yes
16:09:28:  *      TSC: yes
16:09:28:  *      FPU: yes
16:09:28:  *      PRO: yes
16:09:28:  *       HT: no
16:09:28: -------------------------
16:09:28: ******************************
*** Starting GLX Subsystem ***
******************************
16:09:28: GL3PlusRenderSystem::_createRenderWindow "OgreWindow(0)_0", 1x1 windowed  miscParams: FSAA=0 border=none contentScalingFactor=1.000000 currentGLContext=true externalGLControl=true gamma=Yes parentWindowHandle=2097163 stereoMode=Frame Sequential
16:09:28: GLXWindow::create used FBConfigID = 238
16:09:28: GL Version = <IP_ADDRESS>
16:09:28: GL_VERSION = 4.5 (Compatibility Profile) Mesa 22.0.5
16:09:28: GL_VENDOR = Mesa/X.org
16:09:28: GL_RENDERER = llvmpipe (LLVM 13.0.1, 256 bits)
16:09:28: GL_EXTENSIONS =
16:09:28: GL_3DFX_texture_compression_FXT1
16:09:28: GL_AMD_conservative_depth
16:09:28: GL_AMD_draw_buffers_blend
16:09:28: GL_AMD_multi_draw_indirect
16:09:28: GL_AMD_pinned_memory
16:09:28: GL_AMD_query_buffer_object
16:09:28: GL_AMD_seamless_cubemap_per_texture
16:09:28: GL_AMD_shader_stencil_export
16:09:28: GL_AMD_shader_trinary_minmax
16:09:28: GL_AMD_texture_texture4
16:09:28: GL_AMD_vertex_shader_layer
16:09:28: GL_AMD_vertex_shader_viewport_index
16:09:28: GL_ANGLE_texture_compression_dxt3
16:09:28: GL_ANGLE_texture_compression_dxt5
16:09:28: GL_APPLE_packed_pixels
16:09:28: GL_ARB_ES2_compatibility
16:09:28: GL_ARB_ES3_1_compatibility
16:09:28: GL_ARB_ES3_2_compatibility
16:09:28: GL_ARB_ES3_compatibility
16:09:28: GL_ARB_arrays_of_arrays
16:09:28: GL_ARB_base_instance
16:09:28: GL_ARB_blend_func_extended
16:09:28: GL_ARB_buffer_storage
16:09:28: GL_ARB_clear_buffer_object
16:09:28: GL_ARB_clear_texture
16:09:28: GL_ARB_clip_control
16:09:28: GL_ARB_color_buffer_float
16:09:28: GL_ARB_compatibility
16:09:28: GL_ARB_compressed_texture_pixel_storage
16:09:28: GL_ARB_compute_shader
16:09:28: GL_ARB_conditional_render_inverted
16:09:28: GL_ARB_conservative_depth
16:09:28: GL_ARB_copy_buffer
16:09:28: GL_ARB_copy_image
16:09:28: GL_ARB_cull_distance
16:09:28: GL_ARB_debug_output
16:09:28: GL_ARB_depth_buffer_float
16:09:28: GL_ARB_depth_clamp
16:09:28: GL_ARB_depth_texture
16:09:28: GL_ARB_derivative_control
16:09:28: GL_ARB_direct_state_access
16:09:28: GL_ARB_draw_buffers
16:09:28: GL_ARB_draw_buffers_blend
16:09:28: GL_ARB_draw_elements_base_vertex
16:09:28: GL_ARB_draw_indirect
16:09:28: GL_ARB_draw_instanced
16:09:28: GL_ARB_enhanced_layouts
16:09:28: GL_ARB_explicit_attrib_location
16:09:28: GL_ARB_explicit_uniform_location
16:09:28: GL_ARB_fragment_coord_conventions
16:09:28: GL_ARB_fragment_layer_viewport
16:09:28: GL_ARB_fragment_program
16:09:28: GL_ARB_fragment_program_shadow
16:09:28: GL_ARB_fragment_shader
16:09:28: GL_ARB_framebuffer_no_attachments
16:09:28: GL_ARB_framebuffer_object
16:09:28: GL_ARB_framebuffer_sRGB
16:09:28: GL_ARB_get_program_binary
16:09:28: GL_ARB_get_texture_sub_image
16:09:28: GL_ARB_gl_spirv
16:09:28: GL_ARB_gpu_shader5
16:09:28: GL_ARB_gpu_shader_fp64
16:09:28: GL_ARB_gpu_shader_int64
16:09:28: GL_ARB_half_float_pixel
16:09:28: GL_ARB_half_float_vertex
16:09:28: GL_ARB_indirect_parameters
16:09:28: GL_ARB_instanced_arrays
16:09:28: GL_ARB_internalformat_query
16:09:28: GL_ARB_internalformat_query2
16:09:28: GL_ARB_invalidate_subdata
16:09:28: GL_ARB_map_buffer_alignment
16:09:28: GL_ARB_map_buffer_range
16:09:28: GL_ARB_multi_bind
16:09:28: GL_ARB_multi_draw_indirect
16:09:28: GL_ARB_multisample
16:09:28: GL_ARB_multitexture
16:09:28: GL_ARB_occlusion_query
16:09:28: GL_ARB_occlusion_query2
16:09:28: GL_ARB_parallel_shader_compile
16:09:28: GL_ARB_pipeline_statistics_query
16:09:28: GL_ARB_pixel_buffer_object
16:09:28: GL_ARB_point_parameters
16:09:28: GL_ARB_point_sprite
16:09:28: GL_ARB_polygon_offset_clamp
16:09:28: GL_ARB_post_depth_coverage
16:09:28: GL_ARB_program_interface_query
16:09:28: GL_ARB_provoking_vertex
16:09:28: GL_ARB_query_buffer_object
16:09:28: GL_ARB_robust_buffer_access_behavior
16:09:28: GL_ARB_robustness
16:09:28: GL_ARB_sample_shading
16:09:28: GL_ARB_sampler_objects
16:09:28: GL_ARB_seamless_cube_map
16:09:28: GL_ARB_seamless_cubemap_per_texture
16:09:28: GL_ARB_separate_shader_objects
16:09:28: GL_ARB_shader_atomic_counter_ops
16:09:28: GL_ARB_shader_atomic_counters
16:09:28: GL_ARB_shader_bit_encoding
16:09:28: GL_ARB_shader_draw_parameters
16:09:28: GL_ARB_shader_group_vote
16:09:28: GL_ARB_shader_image_load_store
16:09:28: GL_ARB_shader_image_size
16:09:28: GL_ARB_shader_objects
16:09:28: GL_ARB_shader_precision
16:09:28: GL_ARB_shader_stencil_export
16:09:28: GL_ARB_shader_storage_buffer_object
16:09:28: GL_ARB_shader_subroutine
16:09:28: GL_ARB_shader_texture_image_samples
16:09:28: GL_ARB_shader_texture_lod
16:09:28: GL_ARB_shader_viewport_layer_array
16:09:28: GL_ARB_shading_language_100
16:09:28: GL_ARB_shading_language_420pack
16:09:28: GL_ARB_shading_language_include
16:09:28: GL_ARB_shading_language_packing
16:09:28: GL_ARB_shadow
16:09:28: GL_ARB_spirv_extensions
16:09:28: GL_ARB_stencil_texturing
16:09:28: GL_ARB_sync
16:09:28: GL_ARB_tessellation_shader
16:09:28: GL_ARB_texture_barrier
16:09:28: GL_ARB_texture_border_clamp
16:09:28: GL_ARB_texture_buffer_object
16:09:28: GL_ARB_texture_buffer_object_rgb32
16:09:28: GL_ARB_texture_buffer_range
16:09:28: GL_ARB_texture_compression
16:09:28: GL_ARB_texture_compression_bptc
16:09:28: GL_ARB_texture_compression_rgtc
16:09:28: GL_ARB_texture_cube_map
16:09:28: GL_ARB_texture_cube_map_array
16:09:28: GL_ARB_texture_env_add
16:09:28: GL_ARB_texture_env_combine
16:09:28: GL_ARB_texture_env_crossbar
16:09:28: GL_ARB_texture_env_dot3
16:09:28: GL_ARB_texture_filter_anisotropic
16:09:28: GL_ARB_texture_filter_minmax
16:09:28: GL_ARB_texture_float
16:09:28: GL_ARB_texture_gather
16:09:28: GL_ARB_texture_mirror_clamp_to_edge
16:09:28: GL_ARB_texture_mirrored_repeat
16:09:28: GL_ARB_texture_multisample
16:09:28: GL_ARB_texture_non_power_of_two
16:09:28: GL_ARB_texture_query_levels
16:09:28: GL_ARB_texture_query_lod
16:09:28: GL_ARB_texture_rectangle
16:09:28: GL_ARB_texture_rg
16:09:28: GL_ARB_texture_rgb10_a2ui
16:09:28: GL_ARB_texture_stencil8
16:09:28: GL_ARB_texture_storage
16:09:28: GL_ARB_texture_storage_multisample
16:09:28: GL_ARB_texture_swizzle
16:09:28: GL_ARB_texture_view
16:09:28: GL_ARB_timer_query
16:09:28: GL_ARB_transform_feedback2
16:09:28: GL_ARB_transform_feedback3
16:09:28: GL_ARB_transform_feedback_instanced
16:09:28: GL_ARB_transform_feedback_overflow_query
16:09:28: GL_ARB_transpose_matrix
16:09:28: GL_ARB_uniform_buffer_object
16:09:28: GL_ARB_vertex_array_bgra
16:09:28: GL_ARB_vertex_array_object
16:09:28: GL_ARB_vertex_attrib_64bit
16:09:28: GL_ARB_vertex_attrib_binding
16:09:28: GL_ARB_vertex_buffer_object
16:09:28: GL_ARB_vertex_program
16:09:28: GL_ARB_vertex_shader
16:09:28: GL_ARB_vertex_type_10f_11f_11f_rev
16:09:28: GL_ARB_vertex_type_2_10_10_10_rev
16:09:28: GL_ARB_viewport_array
16:09:28: GL_ARB_window_pos
16:09:28: GL_ATI_blend_equation_separate
16:09:28: GL_ATI_draw_buffers
16:09:28: GL_ATI_fragment_shader
16:09:28: GL_ATI_separate_stencil
16:09:28: GL_ATI_texture_compression_3dc
16:09:28: GL_ATI_texture_env_combine3
16:09:28: GL_ATI_texture_float
16:09:28: GL_ATI_texture_mirror_once
16:09:28: GL_EXT_EGL_image_storage
16:09:28: GL_EXT_EGL_sync
16:09:28: GL_EXT_abgr
16:09:28: GL_EXT_bgra
16:09:28: GL_EXT_blend_color
16:09:28: GL_EXT_blend_equation_separate
16:09:28: GL_EXT_blend_func_separate
16:09:28: GL_EXT_blend_minmax
16:09:28: GL_EXT_blend_subtract
16:09:28: GL_EXT_compiled_vertex_array
16:09:28: GL_EXT_copy_texture
16:09:28: GL_EXT_direct_state_access
16:09:28: GL_EXT_draw_buffers2
16:09:28: GL_EXT_draw_instanced
16:09:28: GL_EXT_draw_range_elements
16:09:28: GL_EXT_fog_coord
16:09:28: GL_EXT_framebuffer_blit
16:09:28: GL_EXT_framebuffer_multisample
16:09:28: GL_EXT_framebuffer_multisample_blit_scaled
16:09:28: GL_EXT_framebuffer_object
16:09:28: GL_EXT_framebuffer_sRGB
16:09:28: GL_EXT_gpu_program_parameters
16:09:28: GL_EXT_gpu_shader4
16:09:28: GL_EXT_memory_object
16:09:28: GL_EXT_memory_object_fd
16:09:28: GL_EXT_multi_draw_arrays
16:09:28: GL_EXT_packed_depth_stencil
16:09:28: GL_EXT_packed_float
16:09:28: GL_EXT_packed_pixels
16:09:28: GL_EXT_pixel_buffer_object
16:09:28: GL_EXT_point_parameters
16:09:28: GL_EXT_polygon_offset_clamp
16:09:28: GL_EXT_provoking_vertex
16:09:28: GL_EXT_rescale_normal
16:09:28: GL_EXT_secondary_color
16:09:28: GL_EXT_separate_specular_color
16:09:28: GL_EXT_shader_framebuffer_fetch
16:09:28: GL_EXT_shader_framebuffer_fetch_non_coherent
16:09:28: GL_EXT_shader_integer_mix
16:09:28: GL_EXT_shadow_funcs
16:09:28: GL_EXT_stencil_two_side
16:09:28: GL_EXT_stencil_wrap
16:09:28: GL_EXT_subtexture
16:09:28: GL_EXT_texture
16:09:28: GL_EXT_texture3D
16:09:28: GL_EXT_texture_array
16:09:28: GL_EXT_texture_buffer_object
16:09:28: GL_EXT_texture_compression_dxt1
16:09:28: GL_EXT_texture_compression_latc
16:09:28: GL_EXT_texture_compression_rgtc
16:09:28: GL_EXT_texture_compression_s3tc
16:09:28: GL_EXT_texture_cube_map
16:09:28: GL_EXT_texture_edge_clamp
16:09:28: GL_EXT_texture_env_add
16:09:28: GL_EXT_texture_env_combine
16:09:28: GL_EXT_texture_env_dot3
16:09:28: GL_EXT_texture_filter_anisotropic
16:09:28: GL_EXT_texture_filter_minmax
16:09:28: GL_EXT_texture_integer
16:09:28: GL_EXT_texture_lod_bias
16:09:28: GL_EXT_texture_mirror_clamp
16:09:28: GL_EXT_texture_object
16:09:28: GL_EXT_texture_rectangle
16:09:28: GL_EXT_texture_sRGB
16:09:28: GL_EXT_texture_sRGB_R8
16:09:28: GL_EXT_texture_sRGB_decode
16:09:28: GL_EXT_texture_shadow_lod
16:09:28: GL_EXT_texture_shared_exponent
16:09:28: GL_EXT_texture_snorm
16:09:28: GL_EXT_texture_swizzle
16:09:28: GL_EXT_timer_query
16:09:28: GL_EXT_transform_feedback
16:09:28: GL_EXT_vertex_array
16:09:28: GL_EXT_vertex_array_bgra
16:09:28: GL_EXT_vertex_attrib_64bit
16:09:28: GL_IBM_multimode_draw_arrays
16:09:28: GL_IBM_rasterpos_clip
16:09:28: GL_IBM_texture_mirrored_repeat
16:09:28: GL_INGR_blend_func_separate
16:09:28: GL_KHR_blend_equation_advanced
16:09:28: GL_KHR_blend_equation_advanced_coherent
16:09:28: GL_KHR_context_flush_control
16:09:28: GL_KHR_debug
16:09:28: GL_KHR_no_error
16:09:28: GL_KHR_parallel_shader_compile
16:09:28: GL_KHR_robust_buffer_access_behavior
16:09:28: GL_KHR_robustness
16:09:28: GL_KHR_texture_compression_astc_ldr
16:09:28: GL_KHR_texture_compression_astc_sliced_3d
16:09:28: GL_MESA_framebuffer_flip_y
16:09:28: GL_MESA_pack_invert
16:09:28: GL_MESA_shader_integer_functions
16:09:28: GL_MESA_texture_signed_rgba
16:09:28: GL_MESA_window_pos
16:09:28: GL_MESA_ycbcr_texture
16:09:28: GL_NV_blend_square
16:09:28: GL_NV_conditional_render
16:09:28: GL_NV_copy_depth_to_color
16:09:28: GL_NV_copy_image
16:09:28: GL_NV_depth_clamp
16:09:28: GL_NV_fog_distance
16:09:28: GL_NV_half_float
16:09:28: GL_NV_light_max_exponent
16:09:28: GL_NV_packed_depth_stencil
16:09:28: GL_NV_primitive_restart
16:09:28: GL_NV_texgen_reflection
16:09:28: GL_NV_texture_barrier
16:09:28: GL_NV_texture_env_combine4
16:09:28: GL_NV_texture_rectangle
16:09:28: GL_OES_EGL_image
16:09:28: GL_OES_read_format
16:09:28: GL_S3_s3tc
16:09:28: GL_SGIS_generate_mipmap
16:09:28: GL_SGIS_texture_border_clamp
16:09:28: GL_SGIS_texture_edge_clamp
16:09:28: GL_SGIS_texture_lod
16:09:28: GL_SUN_multi_draw_arrays
16:09:28: **************************************
16:09:28: ***   OpenGL 3+ Renderer Started   ***
16:09:28: **************************************
16:09:28: Registering ResourceManager for type GpuProgram
16:09:28: RenderSystem capabilities
16:09:28: -------------------------
16:09:28: RenderSystem Name: OpenGL 3+ Rendering Subsystem
16:09:28: GPU Vendor: unknown
16:09:28: Device Name: llvmpipe (LLVM 13.0.1, 256 bits)
16:09:28: Driver Version: <IP_ADDRESS>
16:09:28:  * Fixed function pipeline: no
16:09:28:  * Hardware generation of mipmaps: yes
16:09:28:  * Texture blending: yes
16:09:28:  * Anisotropic texture filtering: yes
16:09:28:  * Dot product texture operation: yes
16:09:28:  * Cube mapping: yes
16:09:28:  * Hardware stencil buffer: yes
16:09:28:    - Stencil depth: 8
16:09:28:    - Two sided stencil support: yes
16:09:28:    - Wrap stencil values: yes
16:09:28:  * Hardware vertex / index buffers: yes
16:09:28:  * 32-bit index buffers: yes
16:09:28:  * Vertex programs: yes
16:09:28:  * Number of floating-point constants for vertex programs: 16384
16:09:28:  * Number of integer constants for vertex programs: 16384
16:09:28:  * Number of boolean constants for vertex programs: 16384
16:09:28:  * Fragment programs: yes
16:09:28:  * Number of floating-point constants for fragment programs: 16384
16:09:28:  * Number of integer constants for fragment programs: 16384
16:09:28:  * Number of boolean constants for fragment programs: 16384
16:09:28:  * Geometry programs: yes
16:09:28:  * Number of floating-point constants for geometry programs: 16384
16:09:28:  * Number of integer constants for geometry programs: 16384
16:09:28:  * Number of boolean constants for geometry programs: 16384
16:09:28:  * Tessellation Hull programs: yes
16:09:28:  * Number of floating-point constants for tessellation hull programs: 16384
16:09:28:  * Number of integer constants for tessellation hull programs: 16384
16:09:28:  * Number of boolean constants for tessellation hull programs: 16384
16:09:28:  * Tessellation Domain programs: yes
16:09:28:  * Number of floating-point constants for tessellation domain programs: 16384
16:09:28:  * Number of integer constants for tessellation domain programs: 16384
16:09:28:  * Number of boolean constants for tessellation domain programs: 16384
16:09:28:  * Compute programs: yes
16:09:28:  * Number of floating-point constants for compute programs: 16384
16:09:28:  * Number of integer constants for compute programs: 16384
16:09:28:  * Number of boolean constants for compute programs: 16384
16:09:28:  * Supported Shader Profiles: glsl glsl130 glsl140 glsl150 glsl330 glsl400 glsl410 glsl420 glsl430 glsl440
16:09:28:  * Texture Compression: yes
16:09:28:    - DXT: yes
16:09:28:    - VTC: no
16:09:28:    - PVRTC: no
16:09:28:    - ATC: no
16:09:28:    - ETC1: no
16:09:28:    - ETC2: yes
16:09:28:    - BC4/BC5: yes
16:09:28:    - BC6H/BC7: yes
16:09:28:    - ASTC: yes
16:09:28:  * Hardware Occlusion Query: yes
16:09:28:  * User clip planes: yes
16:09:28:  * VET_UBYTE4 vertex element type: yes
16:09:28:  * Infinite far plane projection: yes
16:09:28:  * Hardware render-to-texture: yes
16:09:28:  * Floating point textures: yes
16:09:28:  * Non-power-of-two textures: yes
16:09:28:  * 1d textures: yes
16:09:28:  * Volume textures: yes
16:09:28:  * Max Texture resolution (2D) 16384
16:09:28:  * Max Texture resolution (3D) 2048
16:09:28:  * Max Texture resolution (Cubemaps) 16384
16:09:28:  * Multiple Render Targets: 8
16:09:28:    - With different bit depths: yes
16:09:28:  * Point Sprites: yes
16:09:28:  * Extended point parameters: yes
16:09:28:  * Max Point Size: 255
16:09:28:  * Vertex texture fetch: yes
16:09:28:  * Number of world matrices: 0
16:09:28:  * Number of texture units: 16
16:09:28:  * Stencil buffer depth: 8
16:09:28:  * Number of vertex blend matrices: 0
16:09:28:    - Max vertex textures: 32
16:09:28:    - Vertex textures shared: yes
16:09:28:  * Render to Vertex Buffer : yes
16:09:28:  * Hardware Atomic Counters: yes
16:09:28:  * Compute max threads per threadgroup per axis: 1024, 1024, 64
16:09:28:  * Compute max threads per threadgroup total: 1024
16:09:28:  * GL 1.5 without VBO workaround: no
16:09:28:  * Frame Buffer objects: yes
16:09:28:  * Frame Buffer objects (ARB extension): no
16:09:28:  * Frame Buffer objects (ATI extension): no
16:09:28:  * PBuffer support: no
16:09:28:  * GL 1.5 without HW-occlusion workaround: no
16:09:28:  * Vertex Array Objects: yes
16:09:28:  * Separate shader objects: no
16:09:28:  * Using Reverse Z: yes
16:09:28: DefaultWorkQueue('Root') initialising on thread main.
16:09:28: Particle Renderer Type 'billboard' registered
16:09:28: Added resource location '/usr/share/ignition/ignition-rendering6/ogre2/media/2.0/scripts/Compositors' of type 'FileSystem' to resource group 'General'
16:09:28: Added resource location '/usr/share/ignition/ignition-rendering6/ogre2/media/2.0/scripts/materials/Common' of type 'FileSystem' to resource group 'General'
16:09:28: Added resource location '/usr/share/ignition/ignition-rendering6/ogre2/media/2.0/scripts/materials/Common/GLSL' of type 'FileSystem' to resource group 'General'
16:09:28: Added resource location '/usr/share/ignition/ignition-rendering6/ogre2/media/2.0/scripts/materials/Common/GLSLES' of type 'FileSystem' to resource group 'General'
16:09:28: Added resource location '/usr/share/ignition/ignition-rendering6/ogre2/media/2.0/scripts/materials/Terra' of type 'FileSystem' to resource group 'General'
16:09:28: Added resource location '/usr/share/ignition/ignition-rendering6/ogre2/media/2.0/scripts/materials/Terra/GLSL' of type 'FileSystem' to resource group 'General'
16:09:28: Added resource location '/usr/share/ignition/ignition-rendering6/ogre2/media' of type 'FileSystem' to resource group 'General'
16:09:28: Added resource location '/usr/share/ignition/ignition-rendering6/ogre2/media/materials/programs' of type 'FileSystem' to resource group 'General'
16:09:28: Added resource location '/usr/share/ignition/ignition-rendering6/ogre2/media/materials/programs/GLSL' of type 'FileSystem' to resource group 'General'
16:09:28: Added resource location '/usr/share/ignition/ignition-rendering6/ogre2/media/materials/programs/Metal' of type 'FileSystem' to resource group 'General'
16:09:28: Added resource location '/usr/share/ignition/ignition-rendering6/ogre2/media/materials/scripts' of type 'FileSystem' to resource group 'General'
16:09:28: Added resource location '/usr/share/ignition/ignition-rendering6/ogre2/media/materials/textures' of type 'FileSystem' to resource group 'General'
16:09:28: Parsing scripts for resource group Autodetect
16:09:28: Finished parsing scripts for resource group Autodetect
16:09:28: Creating resources for group Autodetect
16:09:28: All done
16:09:28: Parsing scripts for resource group General
16:09:28: Parsing script Quad.program
16:09:28: Parsing script DepthUtils.material
16:09:28: Parsing script Copyback.material
16:09:28: Parsing script EsmGaussianBlurLogFilter.material
16:09:28: Parsing script DPSM.material
16:09:28: Parsing script GpuNormalMapper.material
16:09:28: Parsing script gaussian_noise.material
16:09:28: Parsing script selection_buffer.material
16:09:28: Parsing script skybox.material
16:09:28: Parsing script thermal.material
16:09:28: Parsing script picker.material
16:09:28: Parsing script depth_camera.material
16:09:28: Parsing script gpu_rays.material
16:09:28: Parsing script point_cloud_point.material
16:09:28: Parsing script TerraShadowGenerator.compositor
16:09:28: Parsing script GpuNormalMapper.compositor
16:09:28: Parsing script EsmGaussianBlurLogFilter.material.json
16:09:28: Parsing script Mipmaps.material.json
16:09:28: Parsing script TerraShadowGenerator.material.json
16:09:28: Finished parsing scripts for resource group General
16:09:28: Creating resources for group General
16:09:28: All done
16:09:28: Parsing scripts for resource group Internal
16:09:28: Finished parsing scripts for resource group Internal
16:09:28: Creating resources for group Internal
16:09:28: All done
16:09:28: Added resource location '/usr/share/ignition/ignition-rendering6/media/materials/textures/' of type 'FileSystem' to resource group 'General'
16:09:28: Can't assign material scene::Material(65513) because this Material does not exist. Have you forgotten to define it in a .material script?
16:09:28: Vertex Shader: 100000001VertexShader_vs
Fragment Shader: 100000001PixelShader_ps
 GLSL validation result :
active samplers with a different type refer to the same texture image unit
16:09:29: 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:09:29: 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:09:29: 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:09:29: 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...
```

Description
When I add a box, select that one, I can't rotate the box. Translate mode works fine. But Rotate mode does not show the gizmos. In the console I get an output that the rotate gizmo's can't be found (see below).
Steps to reproduce

Start ignition with ign gazebo
Select Empty and click the run button
Add a box (or something else) and select the added item.
Select Rotate mode

Now you don't see the gizmo's. Expected behavior is the the gizmos show.
Output
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-ros'
[GUI] [Err] [MeshDescriptor.cc:56] Mesh manager can't find mesh named [gizmo_rotate]
[GUI] [Err] [Ogre2MeshFactory.cc:562] Cannot load null mesh [gizmo_rotate]
[GUI] [Err] [Ogre2MeshFactory.cc:125] Failed to get Ogre item for [gizmo_rotate]
[GUI] [Err] [Ogre2Visual.cc:134] Cannot attach null geometry.
[GUI] [Err] [MeshDescriptor.cc:56] Mesh manager can't find mesh named [gizmo_rotate]
[GUI] [Err] [Ogre2MeshFactory.cc:562] Cannot load null mesh [gizmo_rotate]
[GUI] [Err] [Ogre2MeshFactory.cc:125] Failed to get Ogre item for [gizmo_rotate]
[GUI] [Err] [Ogre2Visual.cc:134] Cannot attach null geometry.
[GUI] [Err] [MeshDescriptor.cc:56] Mesh manager can't find mesh named [gizmo_rotate]
[GUI] [Err] [Ogre2MeshFactory.cc:562] Cannot load null mesh [gizmo_rotate]
[GUI] [Err] [Ogre2MeshFactory.cc:125] Failed to get Ogre item for [gizmo_rotate]
[GUI] [Err] [Ogre2Visual.cc:134] Cannot attach null geometry.
[GUI] [Err] [MeshDescriptor.cc:56] Mesh manager can't find mesh named [gizmo_rotate_full]
[GUI] [Err] [Ogre2MeshFactory.cc:562] Cannot load null mesh [gizmo_rotate_full]
[GUI] [Err] [Ogre2MeshFactory.cc:125] Failed to get Ogre item for [gizmo_rotate_full]
[GUI] [Err] [Ogre2Visual.cc:134] Cannot attach null geometry.
[GUI] [Err] [MeshDescriptor.cc:56] Mesh manager can't find mesh named [gizmo_rotate_handle]
[GUI] [Err] [Ogre2MeshFactory.cc:562] Cannot load null mesh [gizmo_rotate_handle]
[GUI] [Err] [Ogre2MeshFactory.cc:125] Failed to get Ogre item for [gizmo_rotate_handle]
[GUI] [Err] [Ogre2Visual.cc:134] Cannot attach null geometry.
[GUI] [Err] [MeshDescriptor.cc:56] Mesh manager can't find mesh named [gizmo_rotate_handle]
[GUI] [Err] [Ogre2MeshFactory.cc:562] Cannot load null mesh [gizmo_rotate_handle]
[GUI] [Err] [Ogre2MeshFactory.cc:125] Failed to get Ogre item for [gizmo_rotate_handle]
[GUI] [Err] [Ogre2Visual.cc:134] Cannot attach null geometry.
[GUI] [Err] [MeshDescriptor.cc:56] Mesh manager can't find mesh named [gizmo_rotate_handle]
[GUI] [Err] [Ogre2MeshFactory.cc:562] Cannot load null mesh [gizmo_rotate_handle]
[GUI] [Err] [Ogre2MeshFactory.cc:125] Failed to get Ogre item for [gizmo_rotate_handle]
[GUI] [Err] [Ogre2Visual.cc:134] Cannot attach null geometry.

When I close Ignition, I also get a segmentation fault, but I am not sure if it is related. The output is:
Stack trace (most recent call last):
#30   Object "[0xffffffffffffffff]", at 0xffffffffffffffff, in
#29   Object "ign gazebo gui", at 0x55c40f5181c4, in _start
#28   Object "/lib/x86_64-linux-gnu/libc.so.6", at 0x7f5ec5b8de3f, in __libc_start_main
#27   Object "/lib/x86_64-linux-gnu/libc.so.6", at 0x7f5ec5b8dd8f, in
#26   Object "ign gazebo gui", at 0x55c40f51817e, in
#25   Object "/lib/x86_64-linux-gnu/libruby-3.0.so.3.0", at 0x7f5ec5e34e29, in ruby_run_node
#24   Object "/lib/x86_64-linux-gnu/libruby-3.0.so.3.0", at 0x7f5ec5e31327, in
#23   Object "/lib/x86_64-linux-gnu/libruby-3.0.so.3.0", at 0x7f5ec5fc631c, in rb_vm_exec
#22   Object "/lib/x86_64-linux-gnu/libruby-3.0.so.3.0", at 0x7f5ec5fc0ca6, in
#21   Object "/lib/x86_64-linux-gnu/libruby-3.0.so.3.0", at 0x7f5ec5fbdfd5, in
#20   Object "/lib/x86_64-linux-gnu/libruby-3.0.so.3.0", at 0x7f5ec5fbbc44, in
#19   Object "/lib/x86_64-linux-gnu/libruby-3.0.so.3.0", at 0x7f5ec5f07a2e, in
#18   Object "/lib/x86_64-linux-gnu/libruby-3.0.so.3.0", at 0x7f5ec5e329bc, in rb_protect
#17   Object "/lib/x86_64-linux-gnu/libruby-3.0.so.3.0", at 0x7f5ec5fcac71, in rb_yield
#16   Object "/lib/x86_64-linux-gnu/libruby-3.0.so.3.0", at 0x7f5ec5fc631c, in rb_vm_exec
#15   Object "/lib/x86_64-linux-gnu/libruby-3.0.so.3.0", at 0x7f5ec5fc0ca6, in
#14   Object "/lib/x86_64-linux-gnu/libruby-3.0.so.3.0", at 0x7f5ec5fbdfd5, in
#13   Object "/lib/x86_64-linux-gnu/libruby-3.0.so.3.0", at 0x7f5ec5fbbc44, in
#12   Object "/usr/lib/x86_64-linux-gnu/ruby/3.0.0/fiddle.so", at 0x7f5ec1e6f44b, in
#11   Object "/lib/x86_64-linux-gnu/libruby-3.0.so.3.0", at 0x7f5ec5f89098, in rb_nogvl
#10   Object "/usr/lib/x86_64-linux-gnu/ruby/3.0.0/fiddle.so", at 0x7f5ec1e6ed6b, in
#9    Object "/lib/x86_64-linux-gnu/libffi.so.8", at 0x7f5ec1e60492, in
#8    Object "/lib/x86_64-linux-gnu/libffi.so.8", at 0x7f5ec1e63e2d, in
#7    Object "/usr/lib/x86_64-linux-gnu/libignition-gazebo6-ign.so.6.12.0", at 0x7f5ec137986c, in runGui
#6    Object "/lib/x86_64-linux-gnu/libignition-gazebo6-gui.so.6", at 0x7f5ec11989db, in ignition::gazebo::v6::gui::runGui(int&, char**, char const*, char const*, int, char const*)
#5    Object "/lib/x86_64-linux-gnu/libignition-gui6.so.6", at 0x7f5ebff1416c, in ignition::gui::Application::~Application()
#4    Object "/lib/x86_64-linux-gnu/libQt5Core.so.5", at 0x7f5ec0269913, in QObject::~QObject()
#3    Object "/lib/x86_64-linux-gnu/libQt5Core.so.5", at 0x7f5ec025ea5d, in QObjectPrivate::deleteChildren()
#2    Object "/lib/x86_64-linux-gnu/libignition-gazebo6-gui.so.6", at 0x7f5ec11a0e1c, in ignition::gazebo::v6::GuiRunner::~GuiRunner()
#1    Object "/lib/x86_64-linux-gnu/libignition-gazebo6-gui.so.6", at 0x7f5ec11a0e01, in ignition::gazebo::v6::GuiRunner::~GuiRunner()
#0    Object "/lib/x86_64-linux-gnu/libignition-gazebo6-gui.so.6", at 0x7f5ec11af63b, in void ignition::utils::detail::DefaultDelete<ignition::gazebo::v6::GuiRunner::Implementation>(ignition::gazebo::v6::GuiRunner::Implementation*)
Segmentation fault (Address not mapped to object [0x7f5e4c249f18])

Closed this one, because it is the same as #1725


Run glfwinfo in github CI after build

Do not merge - this is just for illustrating when filing issue.

Closing as #2571 includes this and works.


additional view

Hello!
Nice work!
In addition to cmdline and flamegraph you might consider using this as view generator: https://github.com/01org/IntelSEAPI/wiki
It supports JIT symbols, stacks and many more things.
Please contact me if interested.

Looks interesting. Any suggestions on how to make this work with async-profiler?
As far as I understand from the project wiki, the tool relies on ITT_* instrumentation in the code, but this does not seem suitable, since async-profiler already collects samples with stack traces while running unmodified application.

It takes writing an importer from your data into IntelSEAPI internal representation. Examples are here: https://github.com/01org/IntelSEAPI/tree/master/runtool/importers
Please contact me using one of the ways shown in my profile? I will help you to write it.

async-profiler already supports a number of output formats, including

collapsed stack traces format which is as simple as CSV;
call tree / backtrace views;
Java Flight Recorder (.jfr).

JFR format is rich and extensible and supports nearly all features Java profilers can give. It has been recently open sourced along with its primary consumer - Java Mission Control. I assume that further development around presentation of profiler data should be based on this format.


PBKDF2 using CMAC feature support

Current mbedtls seems only support PBKDF2[rfc2898] using HMAC, but does not support PBKDF2 using CMAC. And I also noticed that AES-CMAC-128-PRF is already available.
May I ask that do you have any plan to support PBKDF2 using CMAC (AES-CMAC-128-PRF)? Thanks.

We have no immediate plans to implement this in the core team, but we'd be open to community contributions to do this.
cc: @yanesca


How to handle download automatically in webview

In README.md ur given this

Downloads are handled automatically and can be listened to
@Override
public void onDownloadRequested(String url, String userAgent, String contentDisposition, String mimetype, long contentLength) {
    // some file is available for download
    // either handle the download yourself or use the code below

    final String filename;
    // ...

    if (AdvancedWebView.handleDownload(this, url, filename)) {
        // download successfully handled
    }
    else {
        // download couldn't be handled because user has disabled download manager app on the device
        // TODO show some notice to the user
    }
}

Can you please provide how to handle download and what is  final String filename.

Thanks for your question!
You understood everything correctly and put this method in the right place. The only problem you have is the missing filename, right?
Well, that's easier than you might have thought:
Actually, you could just hard-code a filename into that method, which would look like this:
final String filename = "my-file.txt;
But this would always download and save any file under the name my-file.txt. That's probably not what you want, right?
But you can do everything you want with this filename. For example, you could add the current timestamp at the beginning of that name so that files have unique names:
final String filename = System.currentTimeMillis()+" my-file.txt";
Alternatively, you could include your app's name, etc.
But another important thing that you'd probably want to change is the file extension. If you know what extension the file must have, that's great, then you can hard-code it as in the examples above. But often, it won't always be a text file, so you could detect the file extension from the MIME type that is passed as a method parameter:
final String filename;
if (mimetype.equals("image/jpeg")) {
    filename = "my-photo.jpg";
}
else if (mimetype.equals("text/html")) {
    filename = "my-document.html";
}
else {
    // we didn't expect this MIME type and so we don't have any reasonable extension
    filename = "my-file";
}

Hope that helps!

Thanks for your suggestion it worked .:-)
But am unable to cancel the download once started .Can you please help on it.

Glad that it worked :)
Cancelling any download is not currently possible when you let this library handle the downloads automatically. This would be possible in the future, but it will require some small changes to the source code:
Here and here, DownloadManager#enqueue() is called, which returns a unique ID for each download. Those IDs would have to be stored and be passed to DownloadManager#remove() when a future method (potentially named stopDownloads() or something like this) would be called.
Is this really important? From what we know, cancelling downloads is only rarely needed.


How to delete all replicas of a specific shard?

In dragonboat, I can use nodehost.SyncRequestDeleteReplica to delete a replica of a specific shard. But it doesn't let me to delete the last replica of the shard. (code)
How can I delete a shard completely, in particular, remove all replicas of this shard?

I don't think you can remove all replicas of a shard, as a shard with 0 replica is not considered as valid in dragonboat.
To remove a shard completely, including all associated data of the shard, you can just stop all replicas and use the RemoveData() method on all involved machines to delete all associated data. Note that you are not suppose to restart those replicas once their data is removed.


The Binding of Isaac: Rebirth [PCSE00507]

Game summary

Game name: The Binding of Isaac: Rebirth
Game serial: PCSE00507

Vita3K summary

Version: v0.1
Build number: 523
Commit hash: https://github.com/vita3k/vita3k/commit/32e9a31

Test environment summary

Tested by: IllusionMan1212
OS: Windows 10 Pro
CPU: AMD Ryzen 5 1600
GPU: NVIDIA GTX 1050Ti
RAM: 8 GB

Issues
Crashes after sceNpTusInit
Screenshots
Not available at the moment
Log
vita3k.log
Recommended labels

Crash

Vita3K summary

Version: v0.1.6
Build number: 2841
Commit hash: https://github.com/vita3k/vita3k/commit/0c75bbb5
CPU backend: Dynarmic

Test environment summary

Tested by: othmanead
OS: Windows 11
CPU: Intel i5-10300H
GPU: RTX 3060 mobile
RAM: 16 GB

Issue:
Game plays with no issues
Screenshots:

Log
vita3k.log
Recommended labels

Playable

I have a question it may just be the zip I'm using but at the moms heart fight after beating mom it just crashes, gonna try a different zip because it likely isn't the same one used to test

Crashes and closes Emulator on first Level starting the Game Vita3K for Android (Release 7)

Does the game work on any android release? Can confirm that release 7 does not work.


[SVCMGR-510] Adjust broker names when they are overtaken from SM

Coverage remained the same at 90.215% when pulling ad6fff9d930ae10c94d5fd7da60a801460b29626 on SVCMGR-510 into 1752c94d4259fdb1d5dc0f6af3312819e0c809b7 on master.


ADD: args.substr & field comparaison

Small PR to add the option -f to be able to filter the fields one wants to check with giving a substr as argument. Only fields including the substings are then checked and not all of them. Allows to also compare one field or some types of fields quickly which speeds up the workflow quite a lot (for me at least).

Hi @elsagermann, sorry I missed this PR. Looks good. I need to fix the CI, then should be good to merge.

launch jenkins


fixfix bug of bound conjunct to wrong tuple

Proposed changes
pick from master https://github.com/apache/doris/pull/28811

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall


Set up code coverage

Coverage metrics work with tox locally, need to test it out with CI.
Resolves #1302.

@jaraco @benoit-pierre This is good to go. I more or less used the settings I used for dateutil.
I think the most controversial part might be that I have excluded xfail tests from coverage. The reason I've done this in the past on dateutil is that since xfails allow failures, it may mask the fact that we have no passing test that hits a given line.
I'm not sure how it deals with conditional xfails, though.

I'm not sure I agree with filtering out xfailed tests: IMHO the goal of the tests it not to show everything is working but rather to detect when things go wrong... And the point of coverage is to ensure all code paths are tested, an xfailed test fits the bill.

@benoit-pierre Filtering out xfails was a tough choice for me, but I don't see what the point of covering all code paths if the code paths are only covered down some blind alley that is allowed to fail. For example, if you hit lines 30-36, then it fails on line 37 because lines 30 and 36 were producing nonsense for a given input, you haven't actually tested that lines 30-36 work as expected, just that in a certain failure mode they seem to be hit.
Ideally there would be a way to just mark those lines as "hit in xfail", so we can have the best of both worlds.

This is an improvement but for some reason it's not omitting setuptools._vendor.

Not entirely sure what the problem is. I dug around in coverage's insides a bit and I am starting to suspect that coverage ended up picking the version of setuptools that was vendored somewhere or another, and that all the filenames are being collapsed down into one, which is why the omit= flag was not working. Using a * will cover anything under a _vendor folder (which we don't want to include anyway), so that solves the problem.
That said, this may indicate that some of the coverage is hitting not something within the test suite but some other version of setuptools that is installed somewhere. I'm not sure how we'd know the difference.

I haven't been following the discussion, but I can give some background on the _vendor. It's possible that packages in _vendor bypass the code coverage discovery protocols because they're loaded using a custom finder/loader in pkg_resources.extern. That is, you import pkg_resources.extern.six but get pkg_resources.vendor.six or six (depending on if the vendored package is present). I would not be surprised if that breaks the code coverage discovery.

@jaraco I don't think that's it - I dumped some logging into coverage.py and it seems like the matching all happens at the level of the filename, not the import name.

I'm not entirely sure why the pypy3 tests are failing, but I suspect it may be related to slower performance on pypy3 (though that issue seems resolved). Maybe the solution is to drop coverage for pypy3 until the situation improves?
The weird thing is it works fine on my laptop, even using the same version of pypy3 that Travis is using.

For now I've disabled coverage metrics on pypy3 which fixes the problem. I don't think it's a major problem because the other Python 3.x tests should be hitting all the same lines anyway.
I think coverage is also causing some signfiicant slowdown in the pypy build, but not actually failing, so I left that in.
@jaraco @benoit-pierre I think this is finally ready to merge if you agree.

Ping @benoit-pierre. I'd like to merge this, but I'm a bit gunshy after you found that glaring error where I was turning off 75% of the tests. Mind giving this a quick once over?

I'm looking into it right now.

OK, so after taking the time to look more into it, I'd like some changes:
commit d38a935425ce534c0d7ca011bc67e68464a2538d
Author: Benoit Pierre<EMAIL_ADDRESS>Date:   Mon Mar 26 18:34:40 2018 +0200

    tmp

diff --git a/.travis.yml b/.travis.yml
index fb659f13..544b8df3 100644
--- a/.travis.yml
+++ b/.travis.yml
@@ -8,29 +8,20 @@ python:
 - 3.5
 - &latest_py3 3.6
 - nightly
-- pypy
-env:
-    TOXENV=py

 jobs:
   fast_finish: true
   include:
   - python: *latest_py3
-    env: &cenv
-        global:
-            - LANG=C
-            - TOXENV=py
+    env: LANG=C
   - python: *latest_py2
-    env: *cenv
-  - python: pypy3
-    # Running coverage breaks the pypy3 build on Travis only.
-    # Until that's fixed the pypy3 build needs to be run without coverage
-    script: tox -e py -- $TRAVIS_BUILD_DIR
+    env: LANG=C
   - stage: deploy (to PyPI for tagged commits)
     if: tag IS present
     python: *latest_py3
     install: skip
     script: skip
+    after_success: skip
     before_deploy: python bootstrap.py
     deploy:
       provider: pypi
@@ -43,6 +34,13 @@ jobs:
       distributions: release
       skip_cleanup: true
       skip_upload_docs: true
+  # Don't run coverage on pypy.
+  - python: pypy
+    script: tox
+    after_success: skip
+  - python: pypy3
+    script: tox
+    after_success: skip

 cache: pip

@@ -56,8 +54,6 @@ install:
 # update egg_info based on setup.py in checkout
 - python bootstrap.py

-script: tox
-
-after_success:
-    - if [[ $TOXENV == "py" ]]; then tox -e coverage,codecov; fi
+script: tox -- --cov

+after_success: env TRAVIS_JOB_NAME="${TRAVIS_PYTHON_VERSION} (LANG=$LANG)" CODECOV_ENV=TRAVIS_JOB_NAME tox -e coverage,codecov
diff --git a/appveyor.yml b/appveyor.yml
index 2b659459..ff7122b4 100644
--- a/appveyor.yml
+++ b/appveyor.yml
@@ -1,10 +1,13 @@
 environment:

   APPVEYOR: True
+  CODECOV_ENV: APPVEYOR_JOB_NAME

   matrix:
-    - PYTHON: "C:\\Python35-x64"
-    - PYTHON: "C:\\Python27-x64"
+    - APPVEYOR_JOB_NAME: "python35-x64"
+      PYTHON: "C:\\Python35-x64"
+    - APPVEYOR_JOB_NAME: "python27-x64"
+      PYTHON: "C:\\Python27-x64"

 install:
   # symlink python from a directory with a space
@@ -20,10 +23,9 @@ cache:
 test_script:
   - "python bootstrap.py"
   - "python -m pip install tox"
-  - "tox -e py"
+  - "tox -- --cov"

 after_test:
     - tox -e coverage,codecov

 version: '{build}'
-
diff --git a/tox.ini b/tox.ini
index 42d01a2b..ee3fa902 100644
--- a/tox.ini
+++ b/tox.ini
@@ -4,28 +4,28 @@
 #
 # export TOXENV='py27,py3{3,4,5,6},pypy,pypy3'

+[tox]
+envlist=python
+
 [testenv]
 deps=-rtests/requirements.txt
 setenv=COVERAGE_FILE={toxworkdir}/.coverage.{envname}
 # TODO: The passed environment variables came from copying other tox.ini files
 # These should probably be individually annotated to explain what needs them.
 passenv=APPDATA HOMEDRIVE HOMEPATH windir APPVEYOR APPVEYOR_* CI CODECOV_* TRAVIS TRAVIS_*
-# These are separate so xfail tests don't count towards code coverage
-commands=pytest -m "not xfail" {posargs: "{toxinidir}" --cov-config={toxinidir}/tox.ini --cov=setuptools}
-         pytest -m "xfail"  {posargs: "{toxinidir}"}
+commands=pytest --cov-config={toxinidir}/tox.ini --cov-report= {posargs}
 usedevelop=True

 [testenv:coverage]
-description=Combine coverage data and create reports
+description=Combine coverage data and create report
 deps=coverage
 skip_install=True
 changedir={toxworkdir}
 setenv=COVERAGE_FILE=.coverage
 commands=coverage erase
          coverage combine
-         coverage report --rcfile={toxinidir}/tox.ini
-         coverage xml
+         coverage {posargs:xml}

 [testenv:codecov]
 description=[Only run on CI]: Upload coverage data to codecov
@@ -34,9 +34,9 @@ skip_install=True
 commands=codecov --file {toxworkdir}/coverage.xml

 [coverage:run]
-source=setuptools
-omit=*/_vendor/*
-
-[coverage:report]
-skip_covered=True
-show_missing=True
+source=
+	pkg_resources
+	setuptools
+omit=
+	*/_vendor/*
+	*/tests/*

Rational:

using tox should work as before (same as tox -e python, by adding envlist=python to tox.ini)
coverage is not enabled by default (it's slow)
disable coverage for pypy and pypy3 (way too slow)
add coverage info for pkg_resources, and make sure tests are ignored (fix coverage:run section in tox.ini)
make sure all CI jobs are identifiable (using CODECOV_ENV/APPVEYOR_JOB_NAME/TRAVIS_JOB_NAME)
again, I don't see the point in treating xfailed tests differently, especially when this results in executing the tests suite 2 times: now I have to parse 2 different reports, and what about the interaction with pytest options (like --last-failed, or --last-failed-no-failures)?
disable report on terminal: for the CI jobs, that's what codecov is for, and locally, it's much more user-friendly to call tox -e coverage -- html and look at the output for example

@benoit-pierre I would generally agree, other than the last one. The only reason tox -e coverage -- html is nicer to view for now is because we have a lot of lines of code untested (so the output gets a bit noisy). And doing that also forces the user to fire up a browser just to see what's happening :thinking:

I guess it's a matter of preference: I have to open a tab, but then I can refresh it between runs to see the changes. Anyway, you can also use tox -- -k egg_info --cov-report term --cov, or use another format with the coverage pass or ask for the report tox -e coverage -- report . The important point, IMHO, is that, particularly for the CI jobs, showing the coverage data on the "terminal" just add unnecessary noise.

It does not help that the full path to each source file is shown... I've not found a way to change that.

@benoit-pierre I'm basically fine with all that, but I don't really know how to turn that patch into a commit. Can you just push it to my branch?
The big thing I still disagree with is xfail tests, but admittedly it's not a big problem (and to some extent it's actually a bit weird in setuptools because many xfail tests actually only fail on a specific platform). I think the best way to articulate how I feel about xfail tests is that they aren't actual tests. They're more like "TODO" list options because you don't actually test any behavior. The only guarantee you get out of an xfail is that the application doesn't have the expected behavior. You're not actually testing that it fails in any specific way, so the nature of the failure could change from version to version. Nothing that is only hit by a failing tests is actually covered, which is why I exclude them from coverage metrics.
With regards to them being a separate output, I actually like that, because when I run the test suite, I want to see all '......s....' for the covered portion and all 'xxxxxxx' in the un-covered portion.

I would generally agree, other than the last one. The only reason tox -e coverage -- html is nicer to view for now is because we have a lot of lines of code untested (so the output gets a bit noisy). And doing that also forces the user to fire up a browser just to see what's happening thinking

@gaborbernat This may be true, but in a lot of libraries you have some paths that are only taken on one interpreter or the other, not both, so 100% coverage on each platform is not possible even if you can get 100% combined coverage. As such, you're always going to see a mess of lines on any one platform (unless we define some complicated per-platform coverage pragma, which would likely make the code messier).

@pganssle true, I consider that a limitation of tox. though You should be able to instead define dependencies between your tox tasks, in which case one would make all interpreter version run with coverage but don't output anything and then just specify a post task that puts it together and prints the coverage. Hopefully the next iteration of tox will support such flow.

@benoit-pierre I reformatted your diff a bit to get it into a git format-patch format and then applied it, so no need to push to my branch now I guess.
One thing I noticed that I didn't see originally and that I disagree with is that you are now ignoring the tests folder. I quite disagree with this choice. The reason I explicitly include tests in the test coverage is that every line of every test should be hit during the run, and if it's not then part of your test suite isn't running.
This has pointed out a bug for me when submitting a PR to CPython - I accidentally shadowed an earlier test in the test suite, making it so the first one never actually ran (oops). It also would have helped me notice the issue with test_dist.py if codecov were actually showing what lines of code are getting hit and missed (this is either due to a misconfiguration or due to the fact that we have no code coverage on the master branch, I'm not sure). When I went to improve test coverage, I would have seen that most of the tests were not being run at all.
I strongly suggest that we include the test suite in the coverage.

But you would know you overshadowed a test because the test coverage decreased, no? If not then it could be argued said shadowed test is unnecessary. And with tests included the coverage percentage does not answer the question of how much of the pkg_resources/setuptools code is covered since this now includes the testsuite... I did try to split and group coverage info with flags on codecov but the results were not as expected!
Anyway, note that changing the current working directory can have an impact on whether or not an include/ommit pattern match.
Also, at the very least if tests are included, setuptools/tests/mod_with_constant.py should be excluded.

But you would know you overshadowed a test because the test coverage decreased, no? If not then it could be argued said shadowed test is unnecessary.

In that case no because I either added both tests in the same PR or the tests were hitting the C api which doesn't have any code coverage metrics set up. Still, it's also not true in the general case, consider:
def my_func(x, y):
    return x + y

def test_my_func():
    assert my_func(3, 7) == 10

def test_my_func():
    a = my_func(1, float('nan'))
    assert a != a

Say I accidentally copy-pasted or auto-completed the second "def test_my_func", when it should have been test_my_func_nan. Both tests are necessary and both induce the same line coverage, but I'd only detect this accidental shadowing if I have coverage on the tests themselves.

And with tests included the coverage percentage does not answer the question of how much of the pkg_resources/setuptools code is covered since this now includes the testsuite... I did try to split and group coverage info with flags on codecov but the results were not as expected!

You can get those actual numbers from the detailed breakdowns - the bulk number is more or less meaningless anyway, what's important is that the number trends towards 100% over time. If someone adds a test to the test suite, I want to be able to look at the diff, see which lines are covered both in their test and in the library itself, and see that every line of their patch was executed as part of the test suite. Excluding tests hurts that in favor of having the arbitrary metric of "library code coverage" be more "accurate", which I think is not a useful goal.

OK.

Pushed a new version that now covers the tests as well. I think we're in general agreement. @benoit-pierre or @jaraco you can merge when ready (assuming the tests all pass).
Thanks for the help with this all.


What's the difference between ShapeContextNet and Point-Attention?

It is about the residual connection that attached to the final output.


Replace crontab with celery periodic task

https://docs.celeryproject.org/en/latest/userguide/periodic-tasks.html

Work in progress branch: celery-crontab.


feat(oxc): add Compiler and CompilerInterface

This PR adds a full compiler pipeline to the oxc crate, to stop us from implementing the same pipeline over and over again.
relates #4455

This is a clean abstraction, I'm in favor of it.


[RULE] No Destructuring props

As mentioned in the docks here, destructuring props will cause you to lose reactivity, so so making a rule against it would be very useful to catch such unexpected errors

Thanks for the suggestion! I have a plan to implement a rule like this, but it may be a part of a larger rule to track proper use of reactivity in general—it's a complex topic so the best approach is still up in the air. A PR is welcome, and I'll prioritize work on this.

Personally I'd check if the first argument of a function that returns jsx is being destructured and only then error.
I dislike the idea of a big rule, as the point of a rule is to check for a single mistake, and having a rule check for multiple mistakes is anoying for multiple reasons.
I'd love to make a PR, However I have no experience writing eslint rules, so I might have to learn a bit.

I'm curious if you have experience using the react-hooks/rules-of-hooks or react-hooks/exhaustive-deps rules? If so, do you dislike them, and why? These rules check for multiple mistakes, but these mistakes are related to a single concern, as "reactivity" would be the concern here.
Either way, I may still implement a rule like you described, if only in the short term. I'm sure it will provide value even if it doesn't check reactivity everywhere.

I don't have experience with the rules you mentioned
Personally I'd dislike a rule like the one you have right now, because something like destructured props is a diffrent issue that a computation outside a root.
Also it would be a pain to maintain, as you'd have a massive file.
I think a better idea would be to have a config that contains all the reactivity rules (which is then added to the default config once the rules are finalized)

I appreciate the input, thanks again. I suppose multiple rules could offer better error messages. One of my concerns was potentially duplicating computationally expensive work across multiple rules, but there should be a way to address that problem.

It seems like eslint plugin react has a rule for consistency with destructuring:
https://github.com/yannickcr/eslint-plugin-react/blob/HEAD/docs/rules/destructuring-assignment.md

Thanks for the tip, I’ve used that one before. You could certainly use that rule for now before my no-destructure rule is finished, but I’m not sure it works in the parameter list. I’m making progress on it, but there’s a lot to do:
Reporting:

[x] Detecting components
[x] Detecting prop destructuring in the parameter list
[ ] Detecting prop destructuring in the component body

Fixing:

[x] Replacing destructured parameter list with props
[ ] Replacing usages of destructured props with accesses to props fields
[ ] Inserting a call to mergeProps where an AssignmentPattern ({ x = 5 }) is used
[ ] Inserting a call to splitProps where rest is used

Hopefully at least the reporting part of it doesn’t take much longer.

Got this finished and released with version 0.3.0! I'd love any feedback if you give it a try.

Are you sure the rule is included? It doesn't seem like it!

Really? I see it getting loaded up in the NPM package<EMAIL_ADDRESS>I'll try to reproduce in a bit.

Really? I see it getting loaded up in the NPM package<EMAIL_ADDRESS>I'll try to reproduce in a bit.

Nevermind, I just missed it in the src/index.ts, Sorry for bothering you

No problem, better safe than sorry!


Zones cachePurge > Add support for prefixes

The Cloudflare API supports cache purge by URL, Tags, Hosts, and Prefixes: https://api.cloudflare.com/#zone-purge-files-by-cache-tags,-host-or-prefix
This Bundle only supports URL, Tags, and Hosts. Please add support for Prefixes.
Without support for purging cache by prefixes, there is no way to delete all cache starting with the same URL+URI (ex: https://example.com/everything/in/this/dir/path)

Note, there is an existing PR to address this, but it requires some refactoring to enable Ci to pass: https://github.com/cloudflare/cloudflare-php/pull/147/files
@spenserhale Is there any way you'd be willing to make the necessary changes?
@IcyApril is there any way to get priority on the PR listed above, once CI is passing?


[bump_20.10] Fix issue where service doesn't roll back

Signed-off-by: Adam Williams<EMAIL_ADDRESS>Cherry pick of 3003

@dperny @thaJeztah Could either of you restart the tests? They passed in my test runs.

kicked CI 👍

@thaJeztah The tests failed again can this be restarted again? Are these typically flaky tests? They pass for me multiple times.

Let me try it again
For posterity; failure was:
--- FAIL: TestUpdaterRollback (32.34s)
    --- FAIL: TestUpdaterRollback/continue/spec_version_unset (30.00s)
        update_test.go:272: service was updated
        update_test.go:324: test timed out before watchServiceUpdate provided an event
FAIL

Could this get merged please?


implement multiprocessing for ensembleFBA

Implement multiprocessing for ensembleFBA. Solving this will partially address #3 as well.
Alongside multiprocessing, create an example notebook demonstrating the speedup.

CI passed in latest commit to master.


Add button show or hide article

be careful, the demo css has been modified, it will have to be deployed on the server

good job, very useful! many thanks


Add Saint Ignatius' College

@shreejitmurthy First stage of verification passed, official domain is facebook.com as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision. Proof of domain ownership: https://www.facebook.com/ParentsAndFriendsCommittee/

@shreejitmurthy Thank you for your patience while waiting for a review and processing your request. Pull request merged.


Add common emojis to help command

Why did you close the pr??

Please make sure your code compiles and is formatted as per go conventions before you open a PR :)


Fix main thread/background thread issue.

Fix warning thrown by main thread checker around opening URL in background thread, by queuing up opening of website in main thread.
=================================================================
Main Thread Checker: UI API called on a background thread: -[UIApplication openURL:options:completionHandler:]
PID: 3556, TID: 1127479, Thread name: (none), Queue name: com.facebook.react.ATHMovilQueue, QoS: 0
Backtrace:
4   miprepay                            0x00000001029fd298 $s17athmovil_checkout9URLOpenerV11openWebsite3url12alternateURL10completiony10Foundation0H0V_AJySbcSgtF + 732
5   miprepay                            0x00000001029e87dc $s17athmovil_checkout12ATHMCheckoutC0B04withyAA11ATHMPaymentC_tKF + 2244
6   miprepay                            0x00000001029e8bb8 $s17athmovil_checkout12ATHMCheckoutC0B04withyAA11ATHMPaymentC_tKFTo + 112
7   miprepay                            0x0000000102613544 -[AthMovilModule _pay:total:subtotal:tax:metadata1:metadata2:items:] + 564
8   miprepay                            0x0000000102613f8c -[AthMovilModule pay:publicToken:total:subtotal:tax:metadata1:metadata2:items:isProd:errorFn:] + 356

This issue sometimes causes ATHMovil to take 1-10 seconds to load up with a requested transaction.

Hello
The class ATHMCheckout.swift is not in version 3.0 anymore so please update to this version. The SDK is still using UIApplication so you must use the request in the main thread or inside the button event. You can see the example in the class CheckoutViewController method payWithATHMovil
We are going to add the validation to check if it is in the main thread. This it is going to be in the next release. Meanwhile this issue can be closed because it is for a deprecated version.
Regards
Thank you for comment 👍🏽


Hide MediaLibraryPicker fields

In Dashboard or admin panel, How we can hide MediaLibraryPicker fields in Content Items List?

You can update the Placement.info for this field targeting the SummaryAdmin. The default value should be in the Orchard.MediaLibrary folder, and you can also define the new value ("-") in the Admin theme.
You can also define it per field if you prefer.


 element overlaps at mobile sizes

Visit http://beta.consumerfinance.gov/budget/performance-plan-report
Resize window down to a small screen size.
Observe this:

While this is super weird, this text shouldn't be in a sub element. This is not a problem in real-world content scenarios.

While this is super weird, this text shouldn't be in a sub element. This is not a problem in real-world content scenarios.

So there are two issues? (a) Sub shouldn't be wrapping text like this on one line, and (b) this particular content shouldn't be in a sub in the first place. Is that right?

(a) Probably not, but in properly-marked up content, you'll never have sub with more than 2 characters in it. (b) Correct.


Fix dark theme for filters and add searchable filter for repo name

This fixes the dropdowns for the filters to correctly apply background colors.
This also turns the repo name filter into a searchable input like the one used for repo names

I was wondering what we should do about the All option. I'm open to any/all suggestions and we start up a thread in slack too

Sounds good! FWIW I'm still good to merge this as is - don't let perfect be the enemy of the good and what not


"Key 'use_ema_weights_to_init_param' is not in struct"/"please ensure that the architectures match" when trying to fine-tune ofa-base

Hello and thank you for releasing the code of OFA model(s).
I'm currently trying to fine-tune OFA-base on the custom image caption dataset. For this purpose, I'm using slightly modified version of train_caption_stage1.sh script, where I set arch=ofa_base and restore_file=../../checkpoints/ofa_base.pt (downloaded from your checkpoints.md page yesterday). As the result, I get the following error:
 /home/laida/miniconda3/lib/python3.8/site-packages/torch/distributed/launch.py:178: FutureWarning: The module torch.distributed.launch is deprecated
and will be removed in future. Use torchrun.
Note that --use_env is set by default in torchrun.
If your script expects `--local_rank` argument to be set, please
change it to read from `os.environ['LOCAL_RANK']` instead. See
https://pytorch.org/docs/stable/distributed.html#launch-utility for
further instructions

  warnings.warn(
/home/laida/miniconda3/lib/python3.8/site-packages/torch/functional.py:568: UserWarning: torch.meshgrid: in an upcoming release, it will be required to pass the indexing argument. (Triggered internally at  ../aten/src/ATen/native/TensorShape.cpp:2228.)
  return _VF.meshgrid(tensors, **kwargs)  # type: ignore[attr-defined]
/home/laida/miniconda3/lib/python3.8/site-packages/torchvision/transforms/transforms.py:332: UserWarning: Argument interpolation should be of type InterpolationMode instead of int. Please, use InterpolationMode enum.
  warnings.warn(
Traceback (most recent call last):
  File "/home/laida/new_SSD/NLP_in_RL_experiments/OFA/trainer.py", line 504, in load_checkpoint
    if self.cfg.checkpoint.use_ema_weights_to_init_param and "extra_state" in state and "ema" in state["extra_state"]:
  File "/home/laida/miniconda3/lib/python3.8/site-packages/omegaconf/dictconfig.py", line 305, in __getattr__
    self._format_and_raise(key=key, value=None, cause=e)
  File "/home/laida/miniconda3/lib/python3.8/site-packages/omegaconf/base.py", line 95, in _format_and_raise
    format_and_raise(
  File "/home/laida/miniconda3/lib/python3.8/site-packages/omegaconf/_utils.py", line 629, in format_and_raise
    _raise(ex, cause)
  File "/home/laida/miniconda3/lib/python3.8/site-packages/omegaconf/_utils.py", line 610, in _raise
    raise ex  # set end OC_CAUSE=1 for full backtrace
  File "/home/laida/miniconda3/lib/python3.8/site-packages/omegaconf/dictconfig.py", line 303, in __getattr__
    return self._get_impl(key=key, default_value=DEFAULT_VALUE_MARKER)
  File "/home/laida/miniconda3/lib/python3.8/site-packages/omegaconf/dictconfig.py", line 361, in _get_impl
    node = self._get_node(key=key)
  File "/home/laida/miniconda3/lib/python3.8/site-packages/omegaconf/dictconfig.py", line 383, in _get_node
    self._validate_get(key)
  File "/home/laida/miniconda3/lib/python3.8/site-packages/omegaconf/dictconfig.py", line 135, in _validate_get
    self._format_and_raise(
  File "/home/laida/miniconda3/lib/python3.8/site-packages/omegaconf/base.py", line 95, in _format_and_raise
    format_and_raise(
  File "/home/laida/miniconda3/lib/python3.8/site-packages/omegaconf/_utils.py", line 694, in format_and_raise
    _raise(ex, cause)
  File "/home/laida/miniconda3/lib/python3.8/site-packages/omegaconf/_utils.py", line 610, in _raise
    raise ex  # set end OC_CAUSE=1 for full backtrace
omegaconf.errors.ConfigAttributeError: Key 'use_ema_weights_to_init_param' is not in struct
        full_key: checkpoint.use_ema_weights_to_init_param
        reference_type=Any
        object_type=dict

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "../../train.py", line 528, in <module>
    cli_main()
  File "../../train.py", line 521, in cli_main
    distributed_utils.call_main(cfg, main)
  File "/home/laida/miniconda3/lib/python3.8/site-packages/fairseq/distributed/utils.py", line 354, in call_main
    distributed_main(cfg.distributed_training.device_id, main, cfg, kwargs)
  File "/home/laida/miniconda3/lib/python3.8/site-packages/fairseq/distributed/utils.py", line 328, in distributed_main
    main(cfg, **kwargs)
  File "../../train.py", line 157, in main
    extra_state, epoch_itr = checkpoint_utils.load_checkpoint(
  File "/home/laida/new_SSD/NLP_in_RL_experiments/OFA/utils/checkpoint_utils.py", line 249, in load_checkpoint
    extra_state = trainer.load_checkpoint(
  File "/home/laida/new_SSD/NLP_in_RL_experiments/OFA/trainer.py", line 524, in load_checkpoint
    raise Exception(
Exception: Cannot load model parameters from checkpoint ../../checkpoints/ofa_base.pt; please ensure that the architectures match.
ERROR:torch.distributed.elastic.multiprocessing.api:failed (exitcode: 1) local_rank: 0 (pid: 31950) of binary: /home/laida/miniconda3/bin/python3
Traceback (most recent call last):
  File "/home/laida/miniconda3/lib/python3.8/runpy.py", line 194, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File "/home/laida/miniconda3/lib/python3.8/runpy.py", line 87, in _run_code
    exec(code, run_globals)
  File "/home/laida/miniconda3/lib/python3.8/site-packages/torch/distributed/launch.py", line 193, in <module>
    main()
  File "/home/laida/miniconda3/lib/python3.8/site-packages/torch/distributed/launch.py", line 189, in main
    launch(args)
  File "/home/laida/miniconda3/lib/python3.8/site-packages/torch/distributed/launch.py", line 174, in launch
    run(args)
  File "/home/laida/miniconda3/lib/python3.8/site-packages/torch/distributed/run.py", line 715, in run
    elastic_launch(
  File "/home/laida/miniconda3/lib/python3.8/site-packages/torch/distributed/launcher/api.py", line 131, in __call__
    return launch_agent(self._config, self._entrypoint, list(args))
  File "/home/laida/miniconda3/lib/python3.8/site-packages/torch/distributed/launcher/api.py", line 245, in launch_agent
    raise ChildFailedError(
torch.distributed.elastic.multiprocessing.errors.ChildFailedError:
============================================================
../../train.py FAILED

I ensured that I use the latest OFA code and ofa_base.pt, as well as re-installed fairseq, as it was suggested in this issue: https://github.com/OFA-Sys/OFA/issues/126 . But nothing helped.
Here is some info about my setup:

My HEAD is on OFA's commit  630e193986824ab90bce659a747994a3d0667bf4 from Jun 23, 2022
My fairseq version is 0.12.2
My omegaconf version is 2.0.6 (I tried to update omegaconf to 2.2.2, but got error ImportError: cannot import name 'get_ref_type' from 'omegaconf._utils' , so I had to roll back to 2.0.6)
My torchvision version is 0.12.0+cu102
My torch version is 1.11.0+cu102
My pip version is 21.2.4

@SilverSolver Hi, I think you should install Fairseq library provided in our repo instead of the official Fairseq repo.
pip install -e ./fairseq/

@logicwong Thank you for a quick answer! I installed Fairseq from your repo as suggested. Now it's version is 1.0.0a0+630e193. However, now I see another error, connected with architecture mismatch:
/home/laida/miniconda3/lib/python3.8/site-packages/torch/distributed/launch.py:178: FutureWarning: The module torch.distributed.launch is deprecated
and will be removed in future. Use torchrun.
Note that --use_env is set by default in torchrun.
If your script expects `--local_rank` argument to be set, please
change it to read from `os.environ['LOCAL_RANK']` instead. See
https://pytorch.org/docs/stable/distributed.html#launch-utility for
further instructions

  warnings.warn(
/home/laida/miniconda3/lib/python3.8/site-packages/torch/functional.py:568: UserWarning: torch.meshgrid: in an upcoming release, it will be required to pass the indexing argument. (Triggered internally at  ../aten/src/ATen/native/TensorShape.cpp:2228.)
  return _VF.meshgrid(tensors, **kwargs)  # type: ignore[attr-defined]
/home/laida/miniconda3/lib/python3.8/site-packages/torchvision/transforms/transforms.py:332: UserWarning: Argument interpolation should be of type InterpolationMode instead of int. Please, use InterpolationMode enum.
  warnings.warn(
Traceback (most recent call last):
  File "/home/laida/new_SSD/NLP_in_RL_experiments/OFA/trainer.py", line 511, in load_checkpoint
    self.model.load_state_dict(
  File "/home/laida/new_SSD/NLP_in_RL_experiments/OFA/fairseq/fairseq/models/fairseq_model.py", line 125, in load_state_dict
    return super().load_state_dict(new_state_dict, strict)
  File "/home/laida/miniconda3/lib/python3.8/site-packages/torch/nn/modules/module.py", line 1497, in load_state_dict
    raise RuntimeError('Error(s) in loading state_dict for {}:\n\t{}'.format(
RuntimeError: Error(s) in loading state_dict for OFAModel:
        Unexpected key(s) in state_dict: "encoder.layers.0.attn_ln.weight", "encoder.layers.0.attn_ln.bias", "encoder.layers.0.ffn_layernorm.weight", "encoder.layers.0.ffn_layernorm.bias", "encoder.layers.0.self_attn.c_attn", "encoder.layers.1.attn_ln.weight", "encoder.layers.1.attn_ln.bias", "encoder.layers.1.ffn_layernorm.weight", "encoder.layers.1.ffn_layernorm.bias", "encoder.layers.1.self_attn.c_attn", "encoder.layers.2.attn_ln.weight", "encoder.layers.2.attn_ln.bias", "encoder.layers.2.ffn_layernorm.weight", "encoder.layers.2.ffn_layernorm.bias", "encoder.layers.2.self_attn.c_attn", "encoder.layers.3.attn_ln.weight", "encoder.layers.3.attn_ln.bias", "encoder.layers.3.ffn_layernorm.weight", "encoder.layers.3.ffn_layernorm.bias", "encoder.layers.3.self_attn.c_attn", "encoder.layers.4.attn_ln.weight", "encoder.layers.4.attn_ln.bias", "encoder.layers.4.ffn_layernorm.weight", "encoder.layers.4.ffn_layernorm.bias", "encoder.layers.4.self_attn.c_attn", "encoder.layers.5.attn_ln.weight", "encoder.layers.5.attn_ln.bias", "encoder.layers.5.ffn_layernorm.weight", "encoder.layers.5.ffn_layernorm.bias", "encoder.layers.5.self_attn.c_attn", "decoder.layers.0.self_attn_ln.weight", "decoder.layers.0.self_attn_ln.bias", "decoder.layers.0.cross_attn_ln.weight", "decoder.layers.0.cross_attn_ln.bias", "decoder.layers.0.ffn_layernorm.weight", "decoder.layers.0.ffn_layernorm.bias", "decoder.layers.0.self_attn.c_attn", "decoder.layers.0.encoder_attn.c_attn", "decoder.layers.1.self_attn_ln.weight", "decoder.layers.1.self_attn_ln.bias", "decoder.layers.1.cross_attn_ln.weight", "decoder.layers.1.cross_attn_ln.bias", "decoder.layers.1.ffn_layernorm.weight", "decoder.layers.1.ffn_layernorm.bias", "decoder.layers.1.self_attn.c_attn", "decoder.layers.1.encoder_attn.c_attn", "decoder.layers.2.self_attn_ln.weight", "decoder.layers.2.self_attn_ln.bias", "decoder.layers.2.cross_attn_ln.weight", "decoder.layers.2.cross_attn_ln.bias", "decoder.layers.2.ffn_layernorm.weight", "decoder.layers.2.ffn_layernorm.bias", "decoder.layers.2.self_attn.c_attn", "decoder.layers.2.encoder_attn.c_attn", "decoder.layers.3.self_attn_ln.weight", "decoder.layers.3.self_attn_ln.bias", "decoder.layers.3.cross_attn_ln.weight", "decoder.layers.3.cross_attn_ln.bias", "decoder.layers.3.ffn_layernorm.weight", "decoder.layers.3.ffn_layernorm.bias", "decoder.layers.3.self_attn.c_attn", "decoder.layers.3.encoder_attn.c_attn", "decoder.layers.4.self_attn_ln.weight", "decoder.layers.4.self_attn_ln.bias", "decoder.layers.4.cross_attn_ln.weight", "decoder.layers.4.cross_attn_ln.bias", "decoder.layers.4.ffn_layernorm.weight", "decoder.layers.4.ffn_layernorm.bias", "decoder.layers.4.self_attn.c_attn", "decoder.layers.4.encoder_attn.c_attn", "decoder.layers.5.self_attn_ln.weight", "decoder.layers.5.self_attn_ln.bias", "decoder.layers.5.cross_attn_ln.weight", "decoder.layers.5.cross_attn_ln.bias", "decoder.layers.5.ffn_layernorm.weight", "decoder.layers.5.ffn_layernorm.bias", "decoder.layers.5.self_attn.c_attn", "decoder.layers.5.encoder_attn.c_attn".

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "../../train.py", line 528, in <module>
    cli_main()
  File "../../train.py", line 521, in cli_main
    distributed_utils.call_main(cfg, main)
  File "/home/laida/new_SSD/NLP_in_RL_experiments/OFA/fairseq/fairseq/distributed/utils.py", line 374, in call_main
    distributed_main(cfg.distributed_training.device_id, main, cfg, kwargs)
  File "/home/laida/new_SSD/NLP_in_RL_experiments/OFA/fairseq/fairseq/distributed/utils.py", line 348, in distributed_main
    main(cfg, **kwargs)
  File "../../train.py", line 157, in main
    extra_state, epoch_itr = checkpoint_utils.load_checkpoint(
  File "/home/laida/new_SSD/NLP_in_RL_experiments/OFA/utils/checkpoint_utils.py", line 249, in load_checkpoint
    extra_state = trainer.load_checkpoint(
  File "/home/laida/new_SSD/NLP_in_RL_experiments/OFA/trainer.py", line 524, in load_checkpoint
    raise Exception(
Exception: Cannot load model parameters from checkpoint ../../checkpoints/ofa_base.pt; please ensure that the architectures match.
ERROR:torch.distributed.elastic.multiprocessing.api:failed (exitcode: 1) local_rank: 0 (pid: 13396) of binary: /home/laida/miniconda3/bin/python3
Traceback (most recent call last):
  File "/home/laida/miniconda3/lib/python3.8/runpy.py", line 194, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File "/home/laida/miniconda3/lib/python3.8/runpy.py", line 87, in _run_code
    exec(code, run_globals)
  File "/home/laida/miniconda3/lib/python3.8/site-packages/torch/distributed/launch.py", line 193, in <module>
    main()
  File "/home/laida/miniconda3/lib/python3.8/site-packages/torch/distributed/launch.py", line 189, in main
    launch(args)
  File "/home/laida/miniconda3/lib/python3.8/site-packages/torch/distributed/launch.py", line 174, in launch
    run(args)
  File "/home/laida/miniconda3/lib/python3.8/site-packages/torch/distributed/run.py", line 715, in run
    elastic_launch(
  File "/home/laida/miniconda3/lib/python3.8/site-packages/torch/distributed/launcher/api.py", line 131, in __call__
    return launch_agent(self._config, self._entrypoint, list(args))
  File "/home/laida/miniconda3/lib/python3.8/site-packages/torch/distributed/launcher/api.py", line 245, in launch_agent
    raise ChildFailedError(
torch.distributed.elastic.multiprocessing.errors.ChildFailedError:
============================================================
../../train.py FAILED

@SilverSolver Looks like you removed --scale-attn, --scale-fc, --scale-heads? If so, adding them back will solve your problem.

@logicwong Okay, it seems that now stage 1 training is going as it should. Thank you for quick answers, once again!


Create Fluid Force Computation class

Description

Resolves #307

https://github.com/UBCSailbot/boat_simulator/pull/76
Verification

Resources

https://www1.grc.nasa.gov/beginners-guide-to-aeronautics/foilsimstudent/

Looks great! Can you add one more picture where the apparent wind lies in the first quadrant?


Make website field optional from users

The frontend says that the website is optional but if we send blank in website field, the backend sends that website cannot be empty and hence form cannot be submitted

We shouldn't save empty strings as website value.  This is an issue from the UI. The UI shouldn't be sending empty strings for website value.

The UI should have the empty string checks and all the validation required before sending the data.
@swarajpure can you confirm this?
We can then close this issue.

Handling the issue on UI level.
Closing this issue


Control sidebar titles, sort order with front matter

control the title, incl. capitalization with the title from the frontmatter
set the order / priority using a frontmatter option

See "pre-frontmatter" discussion: #416


MinKNOW configuration for Nanopolish

Hi Guys,
We ran several samples with theMinION a couple months ago, and I think we made a number of mistakes in terms of best practices for the basecalling. We are gearing up again, and I'd like to make sure I'm going about the data handling the correct way. Here's what I plan to do:

Download latest MinKNOW
Run MinION without local basecalling
Call bases with Albacore once the run is finished.
Run Nanopolish

Is this the right approach?
Are there any things that need to be configured on MinKNOW such that the fast5 files are usable by Nanopolish?
Thanks,
Robert

Yep, that approach looks good. As long as you basecall with Albacore the reads should work with nanopolish later.

Excellent, thanks Jared, best!
Robert
On Wed, Sep 6, 2017 at 1:20 PM, Jared Simpson<EMAIL_ADDRESS>wrote:

Yep, that approach looks good. As long as you basecall with Albacore the
reads should work with nanopolish later.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/jts/nanopolish/issues/217#issuecomment-327553768, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AePFqDAfxM6blJvCchZT6gw0UwzfBxTHks5sftRTgaJpZM4POso2
.


duct-suite pretty-print|pp

We should establish helper command which would help rendering our records. Similarly to git show I might need help to see a specific record, but nicely indented and possibly colored and with sizes and times being "humanized" (ref #116) ,e.g. invocation like
duct-suite pp duct/logs/2024.08.07T14.06.25-106169_info.json

info.json should be a straightforward pretty print
usage.json should be a little more involved, reorganizing from NLJSON to a nice table or something

Let's consider closed by #122


Enabling containerd service

As the master instance might be restarted intentionally, kubelet service could not start unless containerd service was started

due to worker nodes are being managed by ASG, thus they will be replaced by other ones once been shut down or restarted,  so it means Kubelet is always in running state

Ok, thanks for the PR.


Update KGraphViewer for KDE 5

KGraphViewer development continues upstream, but the older KDE 4-based version in Nixpkgs obstructs removal of its dependencies.
Attn. @lethalman

Done: 3fa6afdb35c94a02d6f5a01fb1c8927814877fac

@ttuegel as this has been fixed can you please close?


Spelling mistake.

https://github.com/SpongePowered/SpongeAPI/blob/bleeding/src/main/java/org/spongepowered/api/world/ChunkTicketManager.java#L289
Not sure if this is intentional?
It says "dickets" more than once in the class javadocs too.

Not it is not. I have mentioned it to blood, who wrote this code. It should be fixed in the next formatting/warning fix commit.

On Jul 20, 2016, at 10:46 PM, Connor Hartley<EMAIL_ADDRESS>wrote:
https://github.com/SpongePowered/SpongeAPI/blob/bleeding/src/main/java/org/spongepowered/api/world/ChunkTicketManager.java#L289
Not sure if this is intentional?
It says "dickets" more than once in the class javadocs too.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

#1000


fix nodelocal path

This change is

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/bf34e6221f650d931297599c8ecaa13be34473a8/

Thank you for editing!


Sitemap - Exclude versioned paths and their future tracking

To re-generate the new sitemap we might have to change the build step on Vercel @masci but I am not sure about this. The sitemap is generated with the postbuild step (from package.json)

When I ran the postbuild step myself I was able to create the correct sitemap - reviewed by @aantti


Its works in my machine and not in production server

After using this gaming engine in my machine it works like a charme but can't make it run in production.
as you can see here's my no config

Thanks,

Add this
`
`

The problem is that the coding style was not strictly followed. Check the linter for more information.
Anyway, this works:


Initial cut of an org/package icon

The org and package could use an icon, had this SVG, picked a bright color... thoughts? Other color suggestions welcome :-)

It looks amazing ;)


Fbinfer.com contains wrong information about registering checkers

Hi.
I am trying to register the SimpleChecker already available in "/infer/src/SimpleChecker.ml" (didn’t change the code), following the instruction from https://fbinfer.com/docs/adding-checkers.html (adding to "all_checkers" in registerCheckers.ml):
let all_checkers =
[ { name= "my simple checker"
; active= true
; callbacks= [(Procedure SimpleChecker.checker, Language.Java)] }
; (* the rest of the list as it was there *)
... ]
While compiling (doing “sudo ./build-infer.sh java”) the following error occurs:
https://gist.github.com/Rui1995/11f9d297bc980bbb4df07052639c64bb
I’m running on Ubuntu 18.04 and the Infer version is  v0.17.0-75e52f1f1.
Apologies if there’s not enough information or wrong formatting, this is the first issue that I’ve opened.

Hi,
You can't directly register the existing SimpleChecker because, albeit the name, it is not a checker but a checker maker. In other words, it contains a functor that takes a domain specification and returns a checker.
To get a checker, you need to first implement your appropriate domain specification (which contains type of your state, how to compare your states, your transfer functions, and when to report). Then, instantiate the functor SimpleChecker.Make with this spec.
For instance, if you call your domain spec MyDomainSpec, then SimpleChecker.Make(MyDomainSpec) will give you the checker, which can be registered.
A very simple checker which does nothing would be:
module MyDomainSpec = struct
  (** dummy state *)
  type t = unit

  let initial  = ()

  let exec_instr astate instr node proc_name env : t = astate
  (** dummy transfer function that simply returns given state.  *)

  let report astate loc proc_name  = ()
  (** log errors here. *)

  let compare astate1 astate2 = 0
  (** dummy compare *)
end

module MySimpleChecker = SimpleChecker.Make(MyDomainSpec)

Now, you can register your checker by refering to MySimpleChecker.checker.
Obviously, the above checker is useless. You want to pick the appropriate domain type and implement the comparison, reporting and transfer functions correspondingly.

Thanks you for your answer.
I believe I understand it now.
Best Regards.


Custom dialog

I want to use my own dialog labels, I overrode string xml resources in my app but its not working. Still I have a polish default words. Please help!

+1

Hi, I faced the same situation yesterday and i fixed this. You should be create values-?? named file under res folder and create your own styles.xml file inside it. If you open "Project View" left side, I think you make this more easier. Good luck.

Hi @Palusiniak , @Jsaiao , @ermankuruoglu
See https://github.com/Vorlonsoft/AndroidRate - it currently supports 37 languages

@AlexanderLS How do you use a custom dialog. The documentation is not clear enough.


Error with 7.1.0-39

Rebuilt the Heroku app today and came across errors (below) ... setting the Heroku to use 7.1.0-25 buildpack fixes it.
Heroku Buildpack Link: https://github.com/yespark/heroku-imagemagick-buildpack#154c8c240df1d3fefe362221cac3ae4614e93ab0
Errors:
MiniMagick::Error: `magick convert /tmp/ActiveStorage-146013-20220621-3-2ytkha.jpg[0] -auto-orient -resize 250x250> /tmp/image_processing20220621-3-8o0w3g.jpg` failed with error:
convert: UnableToOpenConfigureFile `delegates.xml' @ warning/configure.c/GetConfigureOptions/709.
convert: NoDecodeDelegateForThisImageFormat `JPEG' @ error/constitute.c/ReadImage/741.
convert: NoImagesDefined `/tmp/image_processing20220621-3-8o0w3g.jpg' @ error/convert.c/ConvertImageCommand/3325.

Thanks for the feedback. I'm looking for a fix in very short delay. I will let you know.

I deployed yesterday and saw similar errors. Output below:
`magick convert /tmp/ActiveStorage-9939-20220623-52-hdsude.png[0] -auto-orient -resize 560x560> /tmp/image_processing20220623-52-rrj9u7.png` failed with error:
convert: UnableToOpenConfigureFile `delegates.xml' @ warning/configure.c/GetConfigureOptions/709.
convert: NoDecodeDelegateForThisImageFormat `PNG' @ error/constitute.c/ReadImage/741.
convert: NoImagesDefined `/tmp/image_processing20220623-52-rrj9u7.png' @ error/convert.c/ConvertImageCommand/3325.

I'm using ImageMagick through the MiniMagick Ruby gem, so the rest of the trace is through other libraries. It looks like the original poster is doing the same. I also noticed that identify -list format produces no output on my Heroku dyno, so that seems to imply that the problem is in the ImageMagick build rather than the gem.

I'm using the latest buildpack (commit #2553f7ddc039e1b75a95e3112c74aa2237f2779b, v7.1.0-39) and we are good :)