New users report widget

https://github.com/rainlab/user-plugin/issues/343

Please also provide some notes in the README about this and configuration, along with bumping the version.

All good points, I'll make these improvements tonight after work :)

Ok @LukeTowers, I think I've made all the desired changes. I also added a config option to select only active users, so that will need a review as well. Let me know if there is anything else you need from me!

I'm withdrawing this PR due to inactivity, if anyone wants it feel free to add as separate plugin.

@scottbedard I'm fine with including it in RainLab.User by default but I don't personally have a need for it so I would need to hear someone else say that they would find this useful. I like the recommendation for this as a separate plugin though, perhaps you could turn it into that instead?


Attach a Survey to a parent Model

How you would attach a survey model to another model that acts as its parent?
Eg:
A lesson has a survey
The survey belongs to the lesson (or anything)

Hi @risinglf,
I didn't understand well your suggestion. Could you try to explain your use-case in more detail?
Thank you.


Bad location for a type error

Given the simple file ex.mli:
type 'a t
val create: int -> t

gospel check reports:
$ gospel check ex.mli
File "ex.mli", line 1, characters 8-9:
1 | type 'a t
            ^
Error: The type `t' expects 1 argument(s) but was given 0 argument(s) here.

The wrong locations are the ones in dterm.ml, here and here.
These functions don't have the correct location available (they should!)


Test with an XML document

The test suite no longer tests XML since 03205bfaa453079f5efbb821edb3be4eadd53afa made isXML a private utility of the xpath module.
A better option would be to run the entire test suite on an XML document.

I don't think we can really have karma run in an XML document.


fixed typo 'nuber' to 'number'

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

Thank you @bernardosequeir for your contribution and congratulations on your first PR merge to this repo! 🎉
Hope to see more contributions from you in the future.


Segfault on parse when using "#pragma pack (push, 1)"

Description
Hi,
I just wanted to share this with the community. I do not see this as a bug or real issue. More a project related issue, but it took me several hours to find out what was the cause. You can probably directly close the issue. But this way other people with same kind of issue could have an idea what to look for
(i had a hard time to find info on segfault with the lib on the internet; which is a compliment :-))
I had a project that required to a #pragma pack (push, 1) in an include file for one of my structures.
This was incompatible with this json module and resulted in a segfault when calling parse()
Pretty hard to find the issue. I was thinking about os related issues, memory leak in my program, compiler options, ... none of that helped to solve the issue.
Wrote another small program that parsed json and this worked fine. So rules out all of these ideas.
Finally found out by copying some json parsing code in my project's main() function and comment all other code parts and includes. By uncommenting and re-including step by step, I drilled down to this #pragma directive that was the root cause.
Probably it's better not to use too much of this pragma pack (push,1) stuff anyway, or to normalize after the particular structure that needs it... lesson learned :-)
Reproduction steps
add a structure that need special packing and add "#prama pack (push, 1)" in front of it
Expected vs. actual results
no segfault when calling parse()
Minimal code example
Not applicable.

Error messages
segfault 11

Compiler and operating system
g++ / Mint 21.1 - 64bit
Library version
initially happens on 3.10.5
Validation

[X] The bug also occurs if the latest version from the develop branch is used.
[X] I can successfully compile and run the unit tests.

Were you using this library in multiple files and only doing the pragma in some of them?  That would definitely cause ODR (one definition rule) failures, as you would get different declarations of the same structure in different translation units (files), which is not allowed by the standard, but isn't required to be diagnosed.

Intresting.
I was using the library in different files, but they all include the same header file with the pragma.

Did they all include the two headers in the same order?  The pragma takes effect from that point forward, so if some files included the json header first, then they wouldn't be affected by it.


GUI crashes on macOS

Environment

OS Version: macOS Monterey 12.0.1 on Apple M1

Source or binary build?
source build: gz-gui7 branch, commit: a9605c0f61333411d057d1e8fca34ba9c28b02db

If this is a GUI or sensor rendering bug, describe your GPU and rendering system. Otherwise delete this section.

Rendering plugin: ogre2

[x] GUI rendering error.
[x] running on real hardware
On Mac OS, open a terminal and type system_profiler SPDisplaysDataType. Copy the output here.

Apple M1 Pro:

  Chipset Model: Apple M1 Pro
  Type: GPU
  Bus: Built-In
  Total Number of Cores: 16
  Vendor: Apple (0x106b)
  Metal Family: Supported, Metal GPUFamily Apple 7
  Displays:
    Color LCD:
      Display Type: Built-in Liquid Retina XDR Display
      Resolution: 3456 x 2234 Retina
      Main Display: Yes
      Mirror: Off
      Online: Yes
      Automatically Adjust Brightness: No
      Connection Type: Internal

[x] Please, attach the ogre.log or ogre2.log file from  ~/.gz/rendering

15:16:15: Creating resource group General
15:16:15: Creating resource group Internal
15:16:15: Creating resource group Autodetect
15:16:15: SceneManagerFactory for type 'DefaultSceneManager' registered.
15:16:15: Registering ResourceManager for type Material
15:16:15: Registering ResourceManager for type Mesh
15:16:15: Registering ResourceManager for type Mesh2
15:16:15: Registering ResourceManager for type OldSkeleton
15:16:15: MovableObjectFactory for type 'ParticleSystem' registered.
15:16:15: ArchiveFactory for archive type FileSystem registered.
15:16:15: ArchiveFactory for archive type Zip registered.
15:16:15: ArchiveFactory for archive type EmbeddedZip registered.
15:16:15: DDS codec registering
15:16:15: FreeImage version: 3.18.0
15:16:15: This program uses FreeImage, a free, open source image library supporting all common bitmap formats. See http://freeimage.sourceforge.net for details
15:16:15: 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
15:16:15: ETC codec registering
15:16:15: OITD codec registering
15:16:15: Registering ResourceManager for type HighLevelGpuProgram
15:16:15: MovableObjectFactory for type 'Decal' registered.
15:16:15: MovableObjectFactory for type 'InternalCubemapProbe' registered.
15:16:15: MovableObjectFactory for type 'Entity' registered.
15:16:15: MovableObjectFactory for type 'Item' registered.
15:16:15: MovableObjectFactory for type 'Light' registered.
15:16:15: MovableObjectFactory for type 'Rectangle2Dv2' registered.
15:16:15: MovableObjectFactory for type 'BillboardSet' registered.
15:16:15: MovableObjectFactory for type 'ManualObject2' registered.
15:16:15: MovableObjectFactory for type 'BillboardChain' registered.
15:16:15: MovableObjectFactory for type 'RibbonTrail' registered.
15:16:15: MovableObjectFactory for type 'WireAabb' registered.
15:16:15: *-*-* OGRE Initialising
15:16:15: *-*-* Version 2.3.1 (Daedalus)
15:16:15: OverlayElementFactory for type Panel registered.
15:16:15: OverlayElementFactory for type BorderPanel registered.
15:16:15: OverlayElementFactory for type TextArea registered.
15:16:15: Registering ResourceManager for type Font
15:16:15: Loading library /opt/homebrew/opt/ogre2.3/lib/OGRE-2.3/OGRE/RenderSystem_GL3Plus.dylib
15:16:15: Installing plugin: GL 3+ RenderSystem
15:16:15: OpenGL 3+ Rendering Subsystem created.
15:16:15: Plugin successfully installed
15:16:15: Loading library /opt/homebrew/opt/ogre2.3/lib/OGRE-2.3/OGRE/Plugin_ParticleFX.dylib
15:16:15: Installing plugin: ParticleFX
15:16:15: Particle Emitter Type 'Point' registered
15:16:15: Particle Emitter Type 'Box' registered
15:16:15: Particle Emitter Type 'Ellipsoid' registered
15:16:15: Particle Emitter Type 'Cylinder' registered
15:16:15: Particle Emitter Type 'Ring' registered
15:16:15: Particle Emitter Type 'HollowEllipsoid' registered
15:16:15: Particle Affector Type 'LinearForce' registered
15:16:15: Particle Affector Type 'ColourFader' registered
15:16:15: Particle Affector Type 'ColourFader2' registered
15:16:15: Particle Affector Type 'ColourImage' registered
15:16:15: Particle Affector Type 'ColourInterpolator' registered
15:16:15: Particle Affector Type 'Scaler' registered
15:16:15: Particle Affector Type 'Rotator' registered
15:16:15: Particle Affector Type 'DirectionRandomiser' registered
15:16:15: Particle Affector Type 'DeflectorPlane' registered
15:16:15: Plugin successfully installed
15:16:15: Loading library /opt/homebrew/opt/ogre2.3/lib/OGRE-2.3/OGRE/RenderSystem_Metal.dylib
15:16:15: Installing plugin: Metal RenderSystem
15:16:15: Metal: Devices Detection Starts
15:16:15: Metal: "Apple M1 Pro"
15:16:15: Metal: Devices Detection Ends
15:16:15: Plugin successfully installed
15:16:15: CPU Identifier & Features
15:16:15: -------------------------
15:16:15:  *   CPU ID: ARM64E
15:16:15:  *   Logical cores: 10
15:16:15:  *     NEON: yes
15:16:15: -------------------------
15:16:15: Metal: Devices Detection Starts
15:16:15: Metal: "Apple M1 Pro"
15:16:15: Metal: Devices Detection Ends
15:16:15: Metal: Requested "(default)", selected "Apple M1 Pro (system default)"
15:16:15: Supports: OSX_GPUFamily1_v1
15:16:15: Registering ResourceManager for type GpuProgram
15:16:15: DefaultWorkQueue('Root') initialising on thread main.
15:16:15: Particle Renderer Type 'billboard' registered
15:16:15: Added resource location '/Users/ian/code/ign_g_ws/install/share/gz/gz-rendering7/ogre2/media/2.0/scripts/Compositors' of type 'FileSystem' to resource group 'General'
15:16:15: Added resource location '/Users/ian/code/ign_g_ws/install/share/gz/gz-rendering7/ogre2/media/2.0/scripts/materials/Common' of type 'FileSystem' to resource group 'General'
15:16:15: Added resource location '/Users/ian/code/ign_g_ws/install/share/gz/gz-rendering7/ogre2/media/2.0/scripts/materials/Common/GLSL' of type 'FileSystem' to resource group 'General'
15:16:15: Added resource location '/Users/ian/code/ign_g_ws/install/share/gz/gz-rendering7/ogre2/media/2.0/scripts/materials/Terra' of type 'FileSystem' to resource group 'General'
15:16:15: Added resource location '/Users/ian/code/ign_g_ws/install/share/gz/gz-rendering7/ogre2/media/2.0/scripts/materials/Terra/GLSL' of type 'FileSystem' to resource group 'General'
15:16:15: Added resource location '/Users/ian/code/ign_g_ws/install/share/gz/gz-rendering7/ogre2/media/2.0/scripts/materials/Common/Metal' of type 'FileSystem' to resource group 'General'
15:16:15: Added resource location '/Users/ian/code/ign_g_ws/install/share/gz/gz-rendering7/ogre2/media/2.0/scripts/materials/Terra/Metal' of type 'FileSystem' to resource group 'General'
15:16:15: HLMS Library path '/Users/ian/code/ign_g_ws/install/share/gz/gz-rendering7/ogre2/media/Hlms/Gz' has no piece files. Are you sure you provided the right path with read access?
15:16:15: HLMS Library path '/Users/ian/code/ign_g_ws/install/share/gz/gz-rendering7/ogre2/media/Hlms/Gz' has no piece files. Are you sure you provided the right path with read access?
15:16:15: Added resource location '/Users/ian/code/ign_g_ws/install/share/gz/gz-rendering7/ogre2/media' of type 'FileSystem' to resource group 'General'
15:16:15: Added resource location '/Users/ian/code/ign_g_ws/install/share/gz/gz-rendering7/ogre2/media/materials/programs' of type 'FileSystem' to resource group 'General'
15:16:15: Added resource location '/Users/ian/code/ign_g_ws/install/share/gz/gz-rendering7/ogre2/media/materials/programs/GLSL' of type 'FileSystem' to resource group 'General'
15:16:15: Added resource location '/Users/ian/code/ign_g_ws/install/share/gz/gz-rendering7/ogre2/media/materials/programs/Metal' of type 'FileSystem' to resource group 'General'
15:16:15: Added resource location '/Users/ian/code/ign_g_ws/install/share/gz/gz-rendering7/ogre2/media/materials/scripts' of type 'FileSystem' to resource group 'General'
15:16:15: Added resource location '/Users/ian/code/ign_g_ws/install/share/gz/gz-rendering7/ogre2/media/materials/textures' of type 'FileSystem' to resource group 'General'
15:16:15: Parsing scripts for resource group Autodetect
15:16:15: Finished parsing scripts for resource group Autodetect
15:16:15: Creating resources for group Autodetect
15:16:15: All done
15:16:15: Parsing scripts for resource group General
15:16:15: Parsing script Quad.program
15:16:15: Shader Ogre/Compositor/Quad_vs_Metal compiled successfully.
15:16:15: Shader Ogre/Compositor/QuadCameraDir_vs_Metal compiled successfully.
15:16:15: Shader Ogre/Compositor/QuadCameraDirNoUV_vs_Metal compiled successfully.
15:16:15: Parsing script picker.program
15:16:15: Shader plaincolor_vs_Metal compiled successfully.
15:16:15: Shader plaincolor_fs_Metal compiled successfully.
15:16:15: Parsing script EsmGaussianBlurLogFilter.material
15:16:15: Shader ESM/GaussianLogFilterH_ps_Metal compiled successfully.
15:16:15: Shader ESM/GaussianLogFilterV_ps_Metal compiled successfully.
15:16:15: Parsing script DPSM.material
15:16:15: Shader Ogre/DPSM/CubeToDpsm_ps_Metal compiled successfully.
15:16:15: Shader Ogre/DPSM/CubeToDpsm_Colour_ps_Metal compiled successfully.
15:16:15: Parsing script DepthUtils.material
15:16:15: Shader Ogre/Depth/DownscaleMax_ps_Metal compiled successfully.
15:16:15: Parsing script Copyback.material
15:16:15: Shader Ogre/Copy/4xFP32_ps_Metal compiled successfully.
15:16:15: Shader Ogre/Copy/4xFP32_2DArray_ps_Metal compiled successfully.
15:16:15: Shader Ogre/Copy/1xFP32_ps_Metal compiled successfully.
15:16:15: Shader Ogre/Resolve/1xFP32_Subsample0_ps_Metal compiled successfully.
15:16:15: Parsing script GpuNormalMapper.material
15:16:15: Shader Terra/GpuNormalMapper_ps_Metal compiled successfully.
15:16:15: Parsing script selection_buffer.material
15:16:15: Shader selection_buffer_vs_Metal compiled successfully.
15:16:15: Shader selection_buffer_fs_Metal compiled successfully.
15:16:15: Parsing script gpu_rays.material
15:16:15: Shader GpuRaysScan1stVS_Metal compiled successfully.
15:16:15: Shader GpuRaysScan1stFS_Metal compiled successfully.
15:16:15: Shader Ogre/Compositor/High/Quad_vs_Metal compiled successfully.
15:16:15: Shader GpuRaysScan2ndFS_Metal compiled successfully.
15:16:15: Shader laser_retro_vs_Metal compiled successfully.
15:16:15: Shader laser_retro_fs_Metal compiled successfully.
15:16:15: Parsing script thermal.material
15:16:15: Shader ThermalCameraVS_Metal compiled successfully.
15:16:15: Shader ThermalCameraFS_Metal compiled successfully.
15:16:15: Shader heat_source_vs_Metal compiled successfully.
15:16:15: Shader heat_source_fs_Metal compiled successfully.
15:16:15: Shader HeatSignatureVS_Metal compiled successfully.
15:16:15: Shader HeatSignatureFS_Metal compiled successfully.
15:16:15: Parsing script picker.material
15:16:15: Parsing script skybox.material
15:16:15: Shader SkyBox_vs_Metal compiled successfully.
15:16:15: Shader SkyBox_fs_Metal compiled successfully.
15:16:15: Parsing script gaussian_noise.material
15:16:15: Shader GaussianNoiseVS_Metal compiled successfully.
15:16:15: Shader GaussianNoiseFS_Metal compiled successfully.
15:16:15: Shader GaussianNoiseDepthFS_Metal compiled successfully.
15:16:15: Parsing script depth_camera.material
15:16:15: Shader DepthCameraVS_Metal compiled successfully.
15:16:15: Shader DepthCameraFS_Metal compiled successfully.
15:16:15: Shader DepthCameraFinalVS_Metal compiled successfully.
15:16:15: Shader DepthCameraFinalFS_Metal compiled successfully.
15:16:15: Parsing script point_cloud_point.material
15:16:15: Shader PointCloudVS_Metal compiled successfully.
15:16:15: Shader PointCloudFS_Metal compiled successfully.
15:16:15: Parsing script TerraShadowGenerator.compositor
15:16:15: Parsing script GpuNormalMapper.compositor
15:16:15: Parsing script GpuRays.compositor
15:16:15: Parsing script EsmGaussianBlurLogFilter.material.json
15:16:15: Parsing script Mipmaps.material.json
15:16:15: Parsing script TerraShadowGenerator.material.json
15:16:15: Finished parsing scripts for resource group General
15:16:15: Creating resources for group General
15:16:15: All done
15:16:15: Parsing scripts for resource group Internal
15:16:15: Finished parsing scripts for resource group Internal
15:16:15: Creating resources for group Internal
15:16:15: All done
15:16:15: Added resource location '/Users/ian/code/ign_g_ws/install/share/gz/gz-rendering7/media/materials/textures/' of type 'FileSystem' to resource group 'General'
15:16:15: Can't assign material [Default] because this Material does not exist. Have you forgotten to define it in a .material script?
15:16:15: Can't assign material scene::Material(65503) because this Material does not exist. Have you forgotten to define it in a .material script?
15:16:15: Can't assign material scene::Material(65497) because this Material does not exist. Have you forgotten to define it in a .material script?
15:16:15: Can't assign material scene::Material(65491) because this Material does not exist. Have you forgotten to define it in a .material script?
15:16:15: Can't assign material scene::Material(65485) because this Material does not exist. Have you forgotten to define it in a .material script?
15:16:15: Can't assign material scene::Material(65478) because this Material does not exist. Have you forgotten to define it in a .material script?
15:16:15: Can't assign material scene::Material(65485) because this Material does not exist. Have you forgotten to define it in a .material script?
15:16:15: Can't assign material scene::Material(65466) because this Material does not exist. Have you forgotten to define it in a .material script?
15:16:15: OGRE EXCEPTION(3:RenderingAPIException): Fixed Function pipeline is no longer allowed nor supported. The material scene::Material(65518) must use shaders in HlmsLowLevel::calculateHashFor at /tmp/ogre2.3-20230123-25618-mko29m/ogre-next-2.3.1/OgreMain/src/OgreHlmsLowLevel.cpp (line 163)
15:16:15: OGRE EXCEPTION(3:RenderingAPIException): Fixed Function pipeline is no longer allowed nor supported. The material scene::Material(65518) must use shaders in HlmsLowLevel::calculateHashFor at /tmp/ogre2.3-20230123-25618-mko29m/ogre-next-2.3.1/OgreMain/src/OgreHlmsLowLevel.cpp (line 163)
15:16:15: Couldn't apply datablock '[Hash 0x973c97a7]' to this renderable. Using default one. Check previous log messages to see if there's more information.
15:16:15: OGRE EXCEPTION(3:RenderingAPIException): Fixed Function pipeline is no longer allowed nor supported. The material scene::Material(65518) must use shaders in HlmsLowLevel::calculateHashFor at /tmp/ogre2.3-20230123-25618-mko29m/ogre-next-2.3.1/OgreMain/src/OgreHlmsLowLevel.cpp (line 163)
15:16:15: OGRE EXCEPTION(3:RenderingAPIException): Fixed Function pipeline is no longer allowed nor supported. The material scene::Material(65518) must use shaders in HlmsLowLevel::calculateHashFor at /tmp/ogre2.3-20230123-25618-mko29m/ogre-next-2.3.1/OgreMain/src/OgreHlmsLowLevel.cpp (line 163)
15:16:15: Couldn't apply datablock '[Hash 0x973c97a7]' to this renderable. Using default one. Check previous log messages to see if there's more information.
15:16:15: OGRE EXCEPTION(3:RenderingAPIException): Fixed Function pipeline is no longer allowed nor supported. The material Default/TransGreen must use shaders in HlmsLowLevel::calculateHashFor at /tmp/ogre2.3-20230123-25618-mko29m/ogre-next-2.3.1/OgreMain/src/OgreHlmsLowLevel.cpp (line 163)
15:16:15: OGRE EXCEPTION(3:RenderingAPIException): Fixed Function pipeline is no longer allowed nor supported. The material Default/TransGreen must use shaders in HlmsLowLevel::calculateHashFor at /tmp/ogre2.3-20230123-25618-mko29m/ogre-next-2.3.1/OgreMain/src/OgreHlmsLowLevel.cpp (line 163)
15:16:15: Couldn't apply datablock '[Hash 0x4dac4408]' to this renderable. Using default one. Check previous log messages to see if there's more information.
15:16:15: Shader 100000000VertexShader_vs compiled successfully.
15:16:15: Shader 100000001VertexShader_vs compiled successfully.
15:16:15: Shader 100000001PixelShader_ps compiled successfully.
15:16:15: Shader 100000002VertexShader_vs compiled successfully.
15:16:15: Shader 100000002PixelShader_ps compiled successfully.
15:16:15: 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...
15:16:15: 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...
15:16:15: 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...
15:16:15: 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

Expected behavior:  gz gui launches fine
Actual behavior: gz gui crashes

Steps to reproduce

launch gz sim in server mode, e.g. gz sim -v 4 shapes.sdf -s
launch gz gui: gz sim -v 4 -g -> crash

Output
stack trace from console
Stack trace (most recent call last) in thread<PHONE_NUMBER>:
#7    Object "QtGui", at 0x103d6150f, in QRhiGles2InitParams::newFallbackSurface(QSurfaceFormat const&) + 87979
#6    Object "AGXMetalG13X", at 0x1ce7fd4ef, in AGXMetalG13X + 2794735
#5    Object "AGXMetalG13X", at 0x1ce7f9c97, in AGXMetalG13X + 2780311
#4    Object "AGXMetalG13X", at 0x1ce773227, in AGXMetalG13X + 2228775
#3    Object "AGXMetalG13X", at 0x1ce771d37, in AGXMetalG13X + 2223415
#2    Object "libsystem_platform.dylib", at 0x1892344e3, in _sigtramp + 55
#1    Object "libgz-tools2-backward.dylib", at 0x1007b678b, in backward::SignalHandling::sig_handler(int, __siginfo*, void*) + 19
#0    Object "libgz-tools2-backward.dylib", at 0x1007b67e3, in backward::SignalHandling::handleSignal(int, __siginfo*, void*) + 59

lldb backtrace
Process 67191 stopped
* thread #23, name = 'QSGRenderThread', stop reason = EXC_BAD_ACCESS (code=1, address=0x302433600)
    frame #0: 0x00000001ce771e8c AGXMetalG13X`___lldb_unnamed_symbol1378$$AGXMetalG13X + 456
AGXMetalG13X`___lldb_unnamed_symbol1378$$AGXMetalG13X:
->  0x1ce771e8c <+456>: ldr    x10, [x19, x10, lsl #3]
    0x1ce771e90 <+460>: add    x9, x9, x10, lsl #24
    0x1ce771e94 <+464>: str    x9, [x24], #0x8
    0x1ce771e98 <+468>: subs   w26, w26, #0x1            ; =0x1
Target 0: (ruby) stopped.
(lldb) bt
* thread #23, name = 'QSGRenderThread', stop reason = EXC_BAD_ACCESS (code=1, address=0x302433600)
  * frame #0: 0x00000001ce771e8c AGXMetalG13X`___lldb_unnamed_symbol1378$$AGXMetalG13X + 456
    frame #1: 0x00000001ce773228 AGXMetalG13X`___lldb_unnamed_symbol1384$$AGXMetalG13X + 812
    frame #2: 0x00000001ce7f9c98 AGXMetalG13X`___lldb_unnamed_symbol1918$$AGXMetalG13X + 5400
    frame #3: 0x00000001ce7fd4f0 AGXMetalG13X`___lldb_unnamed_symbol1929$$AGXMetalG13X + 516
    frame #4: 0x0000000119a39510 QtGui`___lldb_unnamed_symbol4455$$QtGui + 140
    frame #5: 0x0000000118086bd0 QtQuick`QSGBatchRenderer::Renderer::renderMergedBatch(QSGBatchRenderer::Renderer::PreparedRenderBatch*) + 236
    frame #6: 0x000000011808832c QtQuick`QSGBatchRenderer::Renderer::renderBatches() + 1212
    frame #7: 0x0000000118089f08 QtQuick`QSGBatchRenderer::Renderer::render() + 1292
    frame #8: 0x00000001180731b4 QtQuick`QSGRenderer::renderScene(QSGBindable const&) + 596
    frame #9: 0x0000000118072f48 QtQuick`QSGRenderer::renderScene(unsigned int) + 64
    frame #10: 0x000000011812ce98 QtQuick`QQuickWindowPrivate::renderSceneGraph(QSize const&, QSize const&) + 796
    frame #11: 0x00000001180dbdb8 QtQuick`___lldb_unnamed_symbol2615$$QtQuick + 1928
    frame #12: 0x00000001180dcdf4 QtQuick`___lldb_unnamed_symbol2624$$QtQuick + 312
    frame #13: 0x0000000119c3fe48 QtCore`___lldb_unnamed_symbol277$$QtCore + 340
    frame #14: 0x000000018921d4ec libsystem_pthread.dylib`_pthread_start + 148

crash report
Thread 0::  Dispatch queue: com.apple.main-thread
0   libsystem_kernel.dylib        	       0x1891e50c0 __psynch_cvwait + 8
1   libsystem_pthread.dylib       	       0x18921dab4 _pthread_cond_wait + 1228
2   QtCore                        	       0x103f7014c 0x103f44000 + 180556
3   QtCore                        	       0x103f700b4 QWaitCondition::wait(QMutex*, QDeadlineTimer) + 104
4   QtQuick                       	       0x10218ef3c 0x1020b0000 + 913212
5   QtQuick                       	       0x10218e9c8 0x1020b0000 + 911816
6   QtQuick                       	       0x10218e40c 0x1020b0000 + 910348
7   QtGui                         	       0x1039f0bac QWindow::event(QEvent*) + 660
8   QtQuick                       	       0x1021e393c QQuickWindow::event(QEvent*) + 264
9   QtWidgets                     	       0x10342f4a4 QApplicationPrivate::notify_helper(QObject*, QEvent*) + 292
10  QtWidgets                     	       0x103430848 QApplication::notify(QObject*, QEvent*) + 548
11  QtCore                        	       0x1041282dc QCoreApplication::notifyInternal2(QObject*, QEvent*) + 292
12  QtGui                         	       0x1039e4c1c QGuiApplicationPrivate::processExposeEvent(QWindowSystemInterfacePrivate::ExposeEvent*) + 256
13  QtGui                         	       0x1039c9518 void QWindowSystemInterface::handleExposeEvent<QWindowSystemInterface::SynchronousDelivery>(QWindow*, QRegion const&) + 256
14  libqcocoa.dylib               	       0x1031dc7bc 0x1031bc000 + 133052
15  libqcocoa.dylib               	       0x1031e4108 0x1031bc000 + 164104
16  QuartzCore                    	       0x19012c9d8 CA::Layer::display_if_needed(CA::Transaction*) + 776
17  QuartzCore                    	       0x19026eaac CA::Context::commit_transaction(CA::Transaction*, double, double*) + 528
18  QuartzCore                    	       0x19010ed78 CA::Transaction::commit() + 680
19  AppKit                        	       0x18bfa71c0 __62+[CATransaction(NSCATransaction) NS_setFlushesWithDisplayLink]_block_invoke + 304
20  AppKit                        	       0x18c706b04 ___NSRunLoopObserverCreateWithHandler_block_invoke + 64
21  CoreFoundation                	       0x1892e7dac __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 36
22  CoreFoundation                	       0x1892e7bf8 __CFRunLoopDoObservers + 572
23  CoreFoundation                	       0x1892e7130 __CFRunLoopRun + 764
24  CoreFoundation                	       0x1892e6694 CFRunLoopRunSpecific + 600
25  HIToolbox                     	       0x191e5c990 RunCurrentEventLoopInMode + 292
26  HIToolbox                     	       0x191e5c61c ReceiveNextEventCommon + 320
27  HIToolbox                     	       0x191e5c4c4 _BlockUntilNextEventMatchingListInModeWithFilter + 72
28  AppKit                        	       0x18be3baec _DPSNextEvent + 844
29  AppKit                        	       0x18be3a390 -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1332
30  AppKit                        	       0x18be2c3b0 -[NSApplication run] + 596
31  libqcocoa.dylib               	       0x1031f17d0 0x1031bc000 + 219088
32  QtCore                        	       0x104124298 QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) + 520
33  QtCore                        	       0x1041288f0 QCoreApplication::exec() + 132
34  libgz-sim7-gui.7.0.0.dylib    	       0x100d6de68 gz::sim::v7::gui::runGui(int&, char**, char const*, char const*, int, char const*) + 60 (Gui.cc:517)
35  libgz-sim7-gz.7.0.0.dylib     	       0x100995904 runGui + 52 (gz.cc:440)
36  libffi.dylib                  	       0x1972dc050 ffi_call_SYSV + 80
37  libffi.dylib                  	       0x1972e49e4 ffi_call_int + 948
38  fiddle.bundle                 	       0x1007456e8 0x100740000 + 22248
39  libruby.2.6.dylib             	       0x1ed32d524 0x1ed1de000 + 1373476
40  fiddle.bundle                 	       0x10074514c 0x100740000 + 20812
41  libruby.2.6.dylib             	       0x1ed3641e8 0x1ed1de000 + 1597928
42  libruby.2.6.dylib             	       0x1ed352154 0x1ed1de000 + 1524052
43  libruby.2.6.dylib             	       0x1ed3609e0 rb_vm_exec + 2016
44  libruby.2.6.dylib             	       0x1ed2411bc 0x1ed1de000 + 405948
45  libruby.2.6.dylib             	       0x1ed2410ac ruby_run_node + 72
46  ruby                          	       0x100567508 main + 92
47  dyld                          	       0x10083d0f4 start + 520

Other notes:

rendering sensors work fine
I've actually managed to launch the gui probably around 1 in ~5 times. There could be some race condition happening
Qt version:$ brew info qt@5
==> qt@5: stable 5.15.7 (bottled) [keg-only]

turns out the gui crash is a red herring. The crash was caused by the component inspector trying to display corrupt or null data received from the server. Closing this issue as it's not related to gui.


Upgrade to ABP 7.0

https://github.com/realLiangshiwei/Lsw.Abp.AntDesignUI/commit/dae169c536ace6bf4420ef9fe7dc2d7c3a2371dc


New version: DFControl v0.5.8

Registering package: DFControl
Repository: https://github.com/louisponet/DFControl.jl
Created by: @louisponet
Version: v0.5.8
Commit: 64854f592a6628b74450eb05f595b70a94c28e0c
Reviewed by: @louisponet
Reference: https://github.com/louisponet/DFControl.jl/commit/64854f592a6628b74450eb05f595b70a94c28e0c#commitcomment-85371397
Description: DFT control

@louisponet please see the message above.  Once you fix the automerge issues you can register again the new revision without changing the version number and this pull request will be automatically updated.
[noblock]


Optional @TypedParam Decorator

I want to use @TypedParam decorator as optional in this case.
for example.
@Get([
  '/user/:userId/:nickname',
  '/user/:userId'
])
async getUserInfo(
  @TypedParam('userId') userId: number,
  @TypedParam('nickname') nickname: string | undefined
  @TypedQuery() query: QueryType,
) {
  ...
}

but, this doesn't work.
this is the error message when I run e2e test.

In above picture, I want to make relationType to optional. but It's impossible.
and also, I can't set default value.

@Param works well both of situation.
In case of @Param decorator, It works.
@Get([
  '/user/:userId/:nickname',
  '/user/:userId'
])
async getUserInfo(
  @TypedParam('userId') userId: number,
  @Param('nickname') nickname: string | undefined
  @TypedQuery() query: QueryType,
) {
  ...
}

/// ------------------
@Get([
  '/user/:userId/:nickname',
  '/user/:userId'
])
async getUserInfo(
  @TypedParam('userId') userId: number,
  @Param('nickname') nickname: string | undefined = undefined
  @TypedQuery() query: QueryType,
) {
  ...
}

Make it nullable instead of optional.
It is the right decision, because path parameter can't be skipped.

@samchon
Can't I use 2 endpoint in one function of controller? like `@Get(['/:a/:b', '/:a'])
That's so sad news... thank you for your reply.

Have not considered that case.
Just define two methods please.

Okay. thank you!


Error in text

"File Size (Bytes) – Is Greater Than - In the text box, type a byte value, such as 1,048,576 (1MB in binary)."
Thats not 1 MB in binary, its 1 MB to bytes. Binary would be<PHONE_NUMBER>00000000000.
[Enter feedback here]

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

ID: cb9c9aae-ceaa-2e78-3752-2770327f49a7
Version Independent ID: acd2ddc9-6225-92e8-2636-2a02437c3d82
Content: Free up storage space - Power Platform
Content Source: power-platform/admin/free-storage-space.md
Service: power-platform
GitHub Login: @jimholtz
Microsoft Alias: jimholtz

@StuBeck32
Thanks for the suggestion. We'll revise for clarity.


[5.7] [Sema] Diagnose 'nonisolated' attribute on wrapped properties

Description: Diagnose use of nonisolated on wrapped properties, because we currently do not support it. This is because the backing property is a stored var and so cannot be marked as nonisolated at the moment.
Risk: Low, adding a new diagnostic to disallow execution of code that is not safe
Review by: @xedin, @hborla
Testing: PR Testing
Original PR: https://github.com/apple/swift/pull/60475

@swift-ci please test


[ESP32] Cannot commission lighting-app in WEP security network

Problem
When providing the credentials to the network from chip-tool to the commissionee, there is no information provided for for joiner on which security type to join. It looks like the platform assumes WPA2 as the security, which causes the device to never be able to successfully join into the network.
I (20075) NimBLE: GATT procedure initiated: notify;
I (20075) NimBLE: att_handle=14

I (20075) chip[DL]: Confirm received for CHIPoBLE TX characteristic indication (con 1) status= 0
I (20895) chip[DL]: WIFI_EVENT_STA_DISCONNECTED
I (20895) chip[DL]: WiFi station state change: Connecting -> Connecting_Failed
I (20905) phy: chan:1,max_power:80
I (20905) phy: chan:2,max_power:80
I (20905) phy: chan:3,max_power:80
I (20915) phy: chan:4,max_power:80
I (20915) phy: chan:5,max_power:80
I (20925) phy: chan:6,max_power:80
I (20925) phy: chan:7,max_power:80
I (20925) phy: chan:8,max_power:80
I (20935) phy: chan:9,max_power:80
I (20935) phy: chan:10,max_power:80
I (20945) phy: chan:11,max_power:80
I (20945) phy: chan:12,max_power:80
I (20945) phy: chan:13,max_power:80
I (20955) phy: chan:14,max_power:80
W (20955) wifi:Haven't to connect to a suitable AP now!
I (20965) chip[DL]: WiFi station state change: Connecting_Failed -> NotConnected
I (20975) chip[DL]: Next WiFi station reconnect in 5000 ms
I (20975) chip[DL]: Done driving station state, nothing else to do...
I (20985) app-devicecallbacks: Current free heap: 128388

W (20995) wifi:Haven't to connect to a suitable AP now!
E (20995) chip[DL]: Failed to get configured network when updating network status: Error ESP32:0x0500300F
W (21005) wifi:Haven't to connect to a suitable AP now!
E (21015) chip[DL]: Failed to get configured network when updating network status: Error ESP32:0x0500300F
I (22595) CHIP[DL]: Write request received for CHIPoBLE RX characteristic con 1 12
I (25095) NimBLE: GATT procedure initiated: notify;
I (25095) NimBLE: att_handle=14

I (25095) chip[DL]: Confirm received for CHIPoBLE TX characteristic indication (con 1) status= 0
I (25975) phy: chan:1,max_power:80
I (25975) phy: chan:2,max_power:80
I (25975) phy: chan:3,max_power:80
I (25975) phy: chan:4,max_power:80
I (25985) phy: chan:5,max_power:80
I (25985) phy: chan:6,max_power:80
I (25995) phy: chan:7,max_power:80
I (25995) phy: chan:8,max_power:80
I (25995) phy: chan:9,max_power:80
I (26005) phy: chan:10,max_power:80
I (26005) phy: chan:11,max_power:80
I (26015) phy: chan:12,max_power:80
I (26015) phy: chan:13,max_power:80
I (26015) phy: chan:14,max_power:80
W (26025) wifi:Haven't to connect to a suitable AP now!
I (26025) chip[DL]: Attempting to connect WiFi station interface
I (26035) chip[DL]: WiFi station state change: NotConnected -> Connecting
I (26045) chip[DL]: Done driving station state, nothing else to do...
W (26055) wifi:Haven't to connect to a suitable AP now!
E (26055) chip[DL]: Failed to get configured network when updating network status: Error ESP32:0x0500300F
I (27625) CHIP[DL]: Write request received for CHIPoBLE RX characteristic con 1 12
I (29165) chip[DL]: WIFI_EVENT_STA_DISCONNECTED
I (29165) chip[DL]: WiFi station state change: Connecting -> Connecting_Failed
I (29165) phy: chan:1,max_power:80
I (29175) phy: chan:2,max_power:80
I (29175) phy: chan:3,max_power:80
I (29175) phy: chan:4,max_power:80
I (29185) phy: chan:5,max_power:80
I (29185) phy: chan:6,max_power:80
I (29195) phy: chan:7,max_power:80
I (29195) phy: chan:8,max_power:80
I (29195) phy: chan:9,max_power:80
I (29205) phy: chan:10,max_power:80
I (29205) phy: chan:11,max_power:80
I (29215) phy: chan:12,max_power:80
I (29215) phy: chan:13,max_power:80
I (29215) phy: chan:14,max_power:80
W (29225) wifi:Haven't to connect to a suitable AP now!
I (29225) chip[DL]: WiFi station state change: Connecting_Failed -> NotConnected
I (29235) chip[DL]: Next WiFi station reconnect in 5000 ms
I (29245) chip[DL]: Done driving station state, nothing else to do...
I (29255) app-devicecallbacks: Current free heap: 128392

W (29255) wifi:Haven't to connect to a suitable AP now!
E (29265) chip[DL]: Failed to get configured network when updating network status: Error ESP32:0x0500300F
W (29275) wifi:Haven't to connect to a suitable AP now!
E (29275) chip[DL]: Failed to get configured network when updating network status: Error ESP32:0x0500300F

Proposed Solution
Allow support/detection for WEP networks when provided with the network credentials from the Commissioner.

@s-mcclain I tried adding a wifi network with WEP-64 and WEP-128 security and it worked in both scenarios.
Please check the attached logs esp32_wep_commissioning.log.
Commit : ea78432ae48db5832e203fa282116332d90f64df
Examples : all-clusters-app/esp32
Device : ESP32C3
Also, for further debugging can you please provide the below details:

Make of your access point
WEP passphrase type
ESP32 target device
And if possible could you get the sniffer capture during commissioning process

@shubhamdp Hey there, I actually just tested this out again on WEP-64 security and it looks like it was able to work successfully after all. Sorry about the confusion, I'll go ahead and close this out as I cannot reproduce this issue.


[feature] Chinese font support

Hi, this lib is very convinient for developers to change font, but I saw there is not doc or relate description on how to using Chinese font.
Does it support for now? If so, how to use them?

Hi, the package now supports a number of Chinese fonts (e.g. ZCOOL, Ma Shan Zheng
, etc.) but not yet Noto. For that, please follow #126


Open Graph Protocol metadata for version pages

Renders OGP metadata for package documentation pages which could be used
to enable prettier rendering of Elm package links when shared at social
sites, chat rooms and forums.
For example elm/http would have following metadata section:
<meta property="og:site_name" content="Elm Packages">
<meta property="og:title" content="http 1.0.0">
<meta property="og:image" content="https://package.elm-lang.org/assets/elm_logo.svg">
<meta property="og:description" content="Make HTTP requests">

Following screenshot displays how Open Graph Preview extension for Chrome renders that metadata:

This could resolve #236.

I think it would probably be good if og:title included the username, since that's how packages are generally referred to both on the package site and when installing them.  So for this example, "elm/http 1.0.0" instead of just "http 1.0.0".

@avh4 Great point! That's definitely something I have to do here.

I have now made the change suggested by @avh4 to include author name in the og:title, PR description and example screenshot were updated to reflect this change.
I also squashed changes into single commit to keep history clean.


neil.el tests

Adds buttercup tests for neil.el. Also discovered a minor bug, fixed it.
This is ready for a review. One additional thing we may consider (it can be done in a separate PR) is to add caching around Emacs install in CI.

Thanks!


[perses] 0.5.1 build 3 : Stay away from latest broken numpy 1.18.1

Conda-forge has fixed this upstream.


[act] reduce memory footprint

currently it takes 2x video memory for act training compared to standard training process. Can we reduce the memory requirement so that the code can be run on more budget GPUs?

cub:rres18:ptripletN 2080Ti*2 memory consumption: 7165MB each.

before optimization: 2080Ti*3 (distributed data parallel)
mnist:rc2f2:ptripletN: 2067MB each GPU.
mnist:rc2f2d:ptripletN: 2067MB each GPU. (my code is already memory-efficient enough)
mnist:rc2f2p:ptripletN:

[ ] performance sanity: mnist:rc2f2p:ptripletN after memory footprint optimization.

after optimization:
cub:rres50:ptripletN
cub:rres50d:ptripletN
cub:rres50p:ptripletN

looks good.


Journal Manager can do crud actions on User entity

this must be in journal bundle. no usage of $this->get('ojs.journal_service') in adminbundle. this controller must be different


Fix typo: Shiek -> Sheik

Fixed a typo for amiibo character Sheik
https://zelda.gamepedia.com/Sheik

You are right! I didn't even notice before that the English name is different from the German and Japanese one.
Thanks for correcting!


Reset to Global Settings not working???

I think this could be a bug, but since am not 100% sure I am reporting it as a question.
It's possible that Reset do Global Settings (on a individual pair GUI settings page) is not working properly? Or maybe I don't know how to use it properly.
I am assuming that if you want a pair to be back to use global settings you must to the paid settings and click on the red button "Reset to Global Settings" and then click on the "Save" button. Is that assumption correct?
Assuming yes, what's happening is, after you reset a specific pair back to global settings, the pair goes back to "Customised" mode every time you made any change on the Global Settings.
Here's some screenshots:

Currently only 2 "customised" pairs in my setup.

11 "customised" pairs a few mins after changing my "Buy: Trigger %" in the Global Settings.
You can see by the timestamp from the Buy Signal that the bot already "processed" both coins and SOLUSDT is now in "customised" mode when it should be in "Global Settings" like BELUSDT.
I think this is happening to all pairs that I already adjusted individual settings before, so basically I can't or don't know how to actually reset a pair back to global settings.
Do you think you can try to reproduce this on your end?
Appreciate your help!

I think this is somewhat related to issue #52
If you change global settings and symbols had their own settings same as the global settings, then the bot will not update symbol settings to the global setting, but showing as customised.
When I get time, I will add an option to update all symbol configuration when you update the global configuration.

I don't think it's related to #52
Because I am using ""Reset to Global Settings" red button before I do this... so I am assuming the symbol is getting back to global with no "previous configuration"... again, maybe I am misunderstanding this functionality... for me it was like getting back to factory defaults which means, no previous configuration. But that's not happening here, looks like it is just copying global settings and saving them as individual setting in the symbol, hence why it goes to Customized after changing global settings later on.
I will try to check the code to see if I can understand it better and maybe propose some solution...
#52 seems to me like another feature, intended for when users want to clear all previous individual settings from all symbols at once. So, goes factory reset for all symbols and not just a single one like the "Reset to Global Settings".

In the symbol configuration, the button "Reset to Global Settings" will be effective in the next tick.
How many coins were you monitoring? If you had 10 coins, then you may see the UI changes 10 seconds later. But in the backend, the bot should already have reset to the global configuration.
Yeah, I may not understand what the exact problem is as well. Checkout the code and let me know if you find any bug.
Thanks.

I knew you would say that, that's why I've made the screenshot so you could see the timestamps :-D
In the screenshot you can see BELUSDT buy signal timestamp is "16:38:20" while SOLUSDT was last updated on "16:39:26", so after BEL.
Both should be using Global but only SOLUSDT was set to "customised" which at that point in time was already updated just like BELUSDT (which is correctly using Global)
The real problem here is that I think I've eddited SOLUSDT params. a few days before... and never touched BELUSDT, but even after using "Reset to Global Settings" the bot still think that SOLUSDT symbol has "modified" and hence considering it "customised"...
So, I insist that "Reset do Global Settings" is not working as intended.
But will try checking the code...

OK, please bear with me since I am JavaScript expert...
But I think the problem in is this line:
https://github.com/chrisleekr/binance-trading-bot/blob/1a308bbb00441e5ee0297e4cd80b437bc5b8920f/public/js/SymbolSettingIcon.js#L86
It seems to be just creating a copy of the global setting into a symbol setting instead of completely removing symbol setting to be like in a new and fresh installation where the symbol was never previously modified.
Not sure if my explanation makes sense for you.

It does make sense and I was planning to update the code to remove the symbol configuration instead of copying the global configuration.
When I get time, I will work on this configuration issue and release in next.

Thanks Chris.
I wish I knew how to code to be able to assist you.
Really appreciate your time and effort here.

I think I would not consider this a bug or even a question, if the button was labeled "Copy from Global Settings" instead of "Reset to Global Setting".

You are right. What I will do is, I will make the button working as expected.

Maybe both features could exists (copy and reset)...
I don't know. That's up to you.
For me only reset is really important, specially when you start using the bot and have no idea of what works and what no in terms of params.

For me only reset is really important, specially when you start using the bot and have no idea of what works and what no in terms of params.

I guess this is something that should be improved by showing a validation message or warning message in the frontend.
I thought I explain pretty in detail in the README.md. Looks like that is not enough.

It is very well explained indeed... both in the README and in the GUI Setting screen.
But yes, is definitely not enough for end users... you know how this goes... They have a thing for causing problems and always blame the software for it hahahaha

@chopeta I have released version 0.0.65, which has a fix with reset to the global configuration for the symbol configuration.
https://github.com/chrisleekr/binance-trading-bot/releases/tag/v0.0.65
If you find any issue, please let me know.
If you think it's fixed, please close the isuse.

Testing now...

It seems to be working perfectly. Thanks for the fixes!!!!

@chrisleekr can we reopen this issue please?
I'm having the same problem, even on the latest version. Essentially when I reset a configuration to global settings, it still stays marked as "customized" and the configuration is not reset (it stays the same). I am resetting using the red button here:

After a bit of digging, I found that when the FE sends the reset request, the BE responds with;
{"result":false,"type":"error","message":"Command is not recognised."}

even though the original request has a payload command.

Here's the full payload that's being sent (I was trying to reset BTCEUR):
{ "command": "symbol-setting-delete", "data": { "globalConfiguration": { "_id": "REDACTED", "key": "configuration", "enabled": true, "cronTime": "* * * * * *", "symbols": [ "ETHEUR", "ADAEUR", "XLMEUR", "BNBEUR", "XRPEUR", "DOTEUR", "BCHEUR", "LTCEUR", "LINKEUR", "UNIEUR", "EOSEUR", "DOGEEUR", "BTCEUR" ], "supportFIATs": [ "EUR" ], "candles": { "interval": "1h", "limit": 84 }, "buy": { "enabled": true, "maxPurchaseAmount": 600, "triggerPercentage": 1.01, "stopPercentage": 1.012, "limitPercentage": 1.0121 }, "sell": { "enabled": true, "triggerPercentage": 1.075, "stopPercentage": 0.99, "limitPercentage": 0.989 } }, "symbol": "BTCEUR", "symbolConfiguration": { "_id": "REDACTED", "key": "BTCEUR-configuration", "candles": { "interval": "1h", "limit": 84 }, "buy": { "enabled": true, "maxPurchaseAmount": 600, "triggerPercentage": 1, "stopPercentage": 1.012, "limitPercentage": 1.0121 }, "sell": { "enabled": true, "triggerPercentage": 1.075, "stopPercentage": 0.99, "limitPercentage": 0.989 }, "enabled": true, "cronTime": "* * * * * *", "symbols": [ "ETHEUR", "ADAEUR", "XLMEUR", "BNBEUR", "XRPEUR", "DOTEUR", "BCHEUR", "LTCEUR", "LINKEUR", "UNIEUR", "EOSEUR", "DOGEEUR", "BTCEUR" ], "supportFIATs": [ "EUR" ] }, "accountInfo": { "makerCommission": 10, "takerCommission": 10, "buyerCommission": 0, "sellerCommission": 0, "canTrade": true, "canWithdraw": true, "canDeposit": true, "updateTime":<PHONE_NUMBER>218, "accountType": "SPOT", "balances": [ { "asset": "BNB", "free": "0.00834594", "locked": "0.00000000" }, { "asset": "DOGE", "free": "13.00000000", "locked": "0.00000000" }, { "asset": "EUR", "free": "REDACTED", "locked": "REDACTED" }, { "asset": "LDBTC", "free": "0.01655636", "locked": "0.00000000" }, { "asset": "LDETH", "free": "0.09303796", "locked": "0.00000000" }, { "asset": "LDXRP", "free": "REDACTED", "locked": "0.00000000" }, { "asset": "LDXLM", "free": "39.00000000", "locked": "0.00000000" }, { "asset": "LDADA", "free": "REDACTED", "locked": "0.00000000" }, { "asset": "DOT", "free": "0.01200000", "locked": "0.00000000" }, { "asset": "DODO", "free": "0.00075022", "locked": "0.00000000" }, { "asset": "ALICE", "free": "0.42660155", "locked": "0.00000000" } ], "permissions": [ "SPOT" ] }, "refreshAccountInfo": false, "indicators": { "lowestPrice": 48332.85, "lastCandle": { "openTime":<PHONE_NUMBER>000, "open": "50070.24000000", "high": "50115.42000000", "low": "50029.98000000", "close": "50100.00000000", "volume": "14.60996000", "closeTime":<PHONE_NUMBER>999, "quoteVolume": "731519.60714565", "trades": 1555, "baseAssetVolume": "8.99293200", "quoteAssetVolume": "450346.04185438" } }, "symbolInfo": { "symbol": "BTCEUR", "status": "TRADING", "baseAsset": "BTC", "baseAssetPrecision": 8, "quoteAsset": "EUR", "quotePrecision": 8, "filterLotSize": { "filterType": "LOT_SIZE", "minQty": "0.00000100", "maxQty": "9000.00000000", "stepSize": "0.00000100" }, "filterPrice": { "filterType": "PRICE_FILTER", "minPrice": "0.01000000", "maxPrice": "1000000.00000000", "tickSize": "0.01000000" }, "filterMinNotional": { "filterType": "MIN_NOTIONAL", "minNotional": "10.00000000", "applyToMarket": true, "avgPriceMins": 5 } }, "openOrders": [], "action": "not-determined", "baseAssetBalance": { "asset": "BTC", "free": 0, "locked": 0, "total": 0, "estimatedValue": 0, "updatedAt": "2021-04-01T19:59:27.218Z" }, "quoteAssetBalance": { "asset": "EUR", "free": "REDACTED", "locked": "REDACTED" }, "buy": { "currentPrice": 50100, "limitPrice": 50706.21, "lowestPrice": 48332.85, "triggerPrice": 48332.85, "difference": 3.6562089758828575, "openOrders": [], "processMesage": "", "updatedAt": "2021-04-01T20:15:50.759Z" }, "sell": { "currentPrice": 50100, "limitPrice": 49548.9, "lastBuyPrice": null, "triggerPrice": null, "difference": null, "currentProfit": null, "currentProfitPercentage": null, "openOrders": [], "processMessage": "", "updatedAt": "2021-04-01T20:15:50.759Z" } } }

If I update the configuration manually, it still gets applied correctly. Anything I should check for you?

Just FYI
I don't have such problem.
I've tested this many times with different symbols.
It's working fine for me here.


mod:simplify auth

What problem does this PR solve?
Can solve the two problems mentioned in https://github.com/pingcap/tispark/issues/2200
What is changed and how it works?
1.put e.injectResolutionRule(new TiAuthRuleFactory(getOrCreateTiContext)) in front of e.injectResolutionRule(new TiDDLRuleFactory(getOrCreateTiContext)). so that TiAuthorizationRule can work without catalogplugin because logical plan will't be replaced (happens in TiDDLRule)
2.some codes about auth are deleted in org.apache.spark.sql.execution.command.tables and org.apache.spark.sql.execution.command.databases because auth will be excute in TiAuthorizationRule. Delete the bug    which is described in the issue as well
Check List
Tests

Unit test
Integration test
Manual test (add detailed scripts or steps below)

Code changes

Has interface methods change

Related pr
https://github.com/pingcap/tispark/pull/2185

/run-all-tests

/run-all-tests

@sunxiaoguang @xuanyu66 @birdstorm PTAL

simplify typo

LGTM

/run-integration-tests

/run-integration-tests

/run-integration-tests

@sunxiaoguang cc can the pr be merged?

@birdstorm can you help merge this pr ?

/run-all-tests


data structures

Hi,
how would you transform items on just those specified indices without mutating the items?
var state = {
  items: [{...}, {...}, ...],
  indices: [3, 8]
};

This is just one example of how I use Ramda to manipulate state in my real world prototype based on React.
Haven't you thought about developing your own data structures? Or supporting for example Immutable.js?
Thanks

how would you transform items on just those specified indices without mutating the items?

you could use a lens to do this, or perhaps you could use evolve.

Haven't you thought about developing your own data structures? Or supporting for example Immutable.js?

Sounds good to me -- we try to be compatible with the fantasy-land spec (although there are gaps), but that means you can use ramda seamlessly with other functor-containing libraries, e.g. Bacon, Highland, etc. Also, please check out ramda-fantasy and Sanctuary.

As well as the suggestions from @buzzdecafe, I was going to suggest assoc, but as it turns out (#773), it doesn't work properly on arrays.
While, as Mike said, you can work seamlessly with other functors, I am very much interested in expanding our interoperability through the dispatch.  I'm thinking part of that might happen through the transducers effort, if we end up being able to support the Transformers Protocol.  More might happen simply by dispatching additional functions (and possibly, I'm afraid to say, by adding back certain aliases, or making it easy for users to hook into our aliasing feature.)  I'm less certain about creating our own data structures, however.  Working with lists and objects is difficult enough.  Adding further options to the library directly is a frightening prospect.

See #878

@kevinbeaty That's awesome!

@honzabrecka I'd be interested to know, how you use Ramda together with React. Did you have Ramda working together with Immutable.js? Or did you use Ramda directly and if so, does its immutability serve well with React?

Instead of using Immutable.js, consider https://github.com/rtfeldman/seamless-immutable
ramda should work well with this, will try this soon


Generalize Frog States into Components Scripts

Wouldn't it be cool if you assign a slide state component to a new enemy type and then that enemy would start sliding around the map just like that?

I sort of have implemented this just now but testing needs to be done for new enemy types.

This has been resolved.


helm template validation failure without --output-dir

When generating a template, validation may fails when --output-dir is not specified because of invalid ownership metadata errors. When generating the same template into an output dir, everything works fine.
# add cilium repo
helm repo add cilium  https://helm.cilium.io/
helm repo update
# generate and install cilium
helm template --validate -n kube-system -f ../components/cluster/cilium/values.yaml  cilium cilium/cilium | kubectl apply -f -

# generate the template again (using validate) -> failure
helm template --validate -n kube-system -f ../components/cluster/cilium/values.yaml  cilium cilium/cilium
Error: rendered manifests contain a resource that already exists. Unable to continue with install: ServiceAccount "cilium" in namespace "kube-system" exists and cannot be imported into the current release: invalid ownership metadata; label validation error: missing key "app.kubernetes.io/managed-by": must be set to "Helm"; annotation validation error: missing key "meta.helm.sh/release-name": must be set to "cilium"; annotation validation error: missing key "meta.helm.sh/release-namespace": must be set to "kube-system"

# generate the same template into an output-dir -> success
helm template --validate -n kube-system -f ../components/cluster/cilium/values.yaml --output-dir test cilium cilium/cilium
coalesce.go:163: warning: skipped value for eni: Not a table.
wrote test/cilium/templates/cilium-agent-serviceaccount.yaml
wrote test/cilium/templates/cilium-operator-serviceaccount.yaml
…

Output of helm version:
version.BuildInfo{Version:"v3.5.3", GitCommit:"041ce5a2c17a58be0fcd5f5e16fb3e7e95fea622", GitTreeState:"dirty", GoVersion:"go1.16"}

Output of kubectl version:
Client Version: version.Info{Major:"1", Minor:"19", GitVersion:"v1.19.7", GitCommit:"1dd5338295409edcfff11505e7bb246f0d325d15", GitTreeState:"clean", BuildDate:"2021-01-13T13:23:52Z", GoVersion:"go1.15.5", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"21+", GitVersion:"v1.21.0-rc.0", GitCommit:"6b526c57934f310f9039309098afaf7fc96a63c5", GitTreeState:"clean", BuildDate:"2021-03-26T21:44:24Z", GoVersion:"go1.16.1", Compiler:"gc", Platform:"linux/amd64"}

Cloud Provider/Platform (AKS, GKE, Minikube etc.):
Self hosted.

At first glance, this appears to be an issue with the cilium chart's templates. Can you please open a ticket with the cilium maintainers so they can look further into this?
If it determined that an issue is present in Helm, we can follow up after the issue has been isolated with a simple example. However since this is the first report of its kind I believe this is an isolated incident with the cilium chart.
https://github.com/cilium/cilium/issues
Thanks!

If you can reproduce the issue with another chart, we can reopen this and look into the issue at-hand.

That being said, as the error suggests it does appear that you already have a serviceaccount already installed. Please make sure to purge your cluster of any existing resources from prior installations before attempting to reinstall a chart. In this case, kubectl delete -n kube-system cilium ought to do the trick.

The service account is created by helm on the first invocation.
That's why I consider it being a bug that helm does report this error on second invocation.
Moreover, the inconsistency between invocation with and without --output-dir is also suspicious.

If you can reproduce the issue with another chart, we can reopen this and look into the issue at-hand.

Reduce test case attached here.
mychart.zip
helm template --validate -n default mychart ./mychart/ | kubectl apply -f -

# Generate the template into a dir works fine:
helm template --validate -n default --output-dir output mychart ./mychart/

# Generate the template without output dir fails:
helm template --validate -n default mychart ./mychart/
Error: rendered manifests contain a resource that already exists. Unable to continue with install: ServiceAccount "mychart" in namespace "default" exists and cannot be imported into the current release: invalid ownership metadata; label validation error: missing key "app.kubernetes.io/managed-by": must be set to "Helm"; annotation validation error: missing key "meta.helm.sh/release-name": must be set to "mychart"; annotation validation error: missing key "meta.helm.sh/release-namespace": must be set to "default"

Thank you. It was unclear from your first comment that you were specifically pointing out the inconsistency in behaviour between --validate and --validate --output-dir.
Re-opening. Please feel free to work on afix.

https://github.com/helm/helm/blob/a499b4b179307c267bdf3ec49b880e3dbd2a5591/pkg/action/action.go#L105

I've just run into this error as well. The template output has previously been applied to the cluster, so --validate performs the same checks as helm install would, and throws this "invalid ownership metadata" error. When using the --output-dir argument, the error is not thrown.
I'm curious how to fix this ownership metadata issue. It seems perhaps an inconsistency between the validation behavior and the templates in the output of helm create which do not create the annotations that seem to be required.


feat: add prerelease tag to cli

Addresses https://github.com/spicylobstergames/SpicyLauncher/issues/19

CI is failing. Can you run cargo clippy and apply the suggestions?

@orhun
magenta

red:

yellow:

purple:

cyan

Yellow seems the most natural to me, and matches GitHub:

My only hesitation is that the title is also yellow, but I think yellow's probably still the best color.

Is the name of the Release color able to change too? Seems off to have the same color per line

Yeah, feel free to play with the release color too. I agree with @zicklag, it would fit better if we have yellow for the prereleases.

Edit: Maybe it should also be pre-release instead of prerelease.

Indeed 👍🏼

@orhun  Went with the green layout for release name :)


Enhancement: Gemini 2.0 Flash support

What features would you like to see added?
https://developers.googleblog.com/en/the-next-chapter-of-the-gemini-era-for-developers/
More details
https://developers.googleblog.com/en/the-next-chapter-of-the-gemini-era-for-developers/
Which components are impacted by your request?
General
Pictures
No response
Code of Conduct

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

Already implemented here: #4951


BTN4 and BTN5 for moving up/down in settings

The buttons on the watch seem to be a weakpoint (at least to me). They tend to get stuck or get greased up if they don't get pushed regularly. I would like to avoid using them whenever possible.
Having said that: can we make the settings app additionally respond to BTN4 (touch left) for up and BTN5 (touch right) for down? So you would only have to press BTN3 to select/enter/exit a menu item.

I have the same issue with the buttons getting stuck and/or triggering neighbour button.
If you want to go full on touch event
Bangle.on('touch', function(button){
  // button == 1 : left side of the screen
  // button == 2 : right side of the screen
  // button == 3 : both together
})

There is also the swipe event
Bangle.on('swipe', dir => {
  // dir == 1 : right to left
})

You can take a look at "Toucher" (the launcher)

Yeah, I'm using Toucher as my launcher. But I'm talking about the settings app. It is using E.showMenu which renders the menu and is thus out of my control even if I wanted to modify it myself.

After playing around a bit (late night work well for me)
I discovered that when E.showMenu(something); is called it return a Instance of that menu
While looking at this link http://www.espruino.com/graphical_menu
I discovered that you can call .move()and .select()on a menu
Which mean that if you keep a reference to the current menu you can handle pretty easily the touch event for the settings app.
There is a simple example, I can try to implement it on the settings app if you don't feel like it ;)
var currentMenu;

var boolean = false;
var number = 420;

var mainmenu = {
  "" : { "title" : "-- Main Menu --" },
  "Backlight On" : function() { LED1.set(); },
  "Backlight Off" : function() { LED1.reset(); },
  "Submenu" : function() { currentMenu = E.showMenu(submenu); },
  "A Boolean" : {
    value : boolean,
    format : v => v?"On":"Off",
    onchange : v => { boolean=v; }
  },
  "A Number" : {
    value : number,
    min:0,max:100,step:10,
    onchange : v => { number=v; }
  },
  "Exit" : function() { currentMenu = E.showMenu(); },
};

// Submenu
var submenu = {
  "" : {
    "title" : "-- SubMenu --"
  },
  "One" : undefined,
  "Two" : undefined,
  "< Back" : function() { currentMenu = E.showMenu(mainmenu); },
};

// keep a reference to the current menu when you show it
currentMenu = E.showMenu(mainmenu);

// handle the touch
Bangle.on('touch', e => {
 if(!currentMenu) return;
  if(e == 1){
    currentMenu.move(-1);
  }else if(e==2){
    currentMenu.move(1);
  }else{
    currentMenu.select();
  }
});

Oh ok, thanks for investigating. It didn't read to documentation careful enough. I will have a look into this, hopefully without running into #206 again.

You could potentially override E.showMenu if you want to do this? Either add your own code and call the existing function, or set E.showMenu to https://github.com/espruino/Espruino/blob/master/libs/js/banglejs/E_showMenu.js with your mods in it

Just to add to this - if you did:
E.showMenu = ....

In a file called newmenu.boot.js then you could happily customise the menu however you see fit, and could even distribute that new menu as an app.

Thanks, I wasn't aware you could overwrite the function that easily. I'll give that a try.

Ok, so I added BTN4 and BTN5 like you suggested and uploaded it as newmenu.boot.js:
E.showMenu =
(function(items) {
  if (Bangle.btnWatches) {
    Bangle.btnWatches.forEach(clearWatch);
    Bangle.btnWatches = undefined;
  }
...
l.draw();
  Bangle.btnWatches = [
    setWatch(function() { l.move(-1); }, BTN1, {repeat:1}),
    setWatch(function() { l.move(-1); }, BTN4, {repeat:1}),
    setWatch(function() { l.move(1); }, BTN3, {repeat:1}),
    setWatch(function() { l.move(1); }, BTN5, {repeat:1}),
    setWatch(function() { l.select(); }, BTN2, {repeat:1})
  ];
  return l;
})

That works fine, however: what if I want to add touch (BTN4+BTN5) as select()?
If I add it through a Bangle.on("touch", e=> {if (e==3) l.select();}); it will be recreated for every submenu and I get double/triple touch events.
How can I delete the touch event at the start of the code once it is set?

http://www.espruino.com/Reference#l_Object_removeListener

Thanks @gfwilliams I got this working using Bangle.removeAllListeners('touch'). Closing the issue then.


gha: Fix x86-only statuses

Looks like I missed a line during refactoring, resulted in only x86 sizes being reported in GitHub statuses.
< Insert rant about GHA making a mess of commit histories >
Related: https://github.com/littlefs-project/littlefs/pull/1026

Tested in https://github.com/geky/littlefs-test-repo/pull/11


Update version

[Enter feedback here]
Missing update the version from net6.0 to net.70

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

ID: 80707602-f283-e796-d3b8-3287fbc011dc
Version Independent ID: 1d732b15-9e64-633a-000c-ad96d9d3818a
Content: Install .NET on Ubuntu - .NET
Content Source: docs/core/install/linux-ubuntu.md
Product: .net
Technology: dotnet-installation
GitHub Login: @adegeo
Microsoft Alias: adegeo

The section for 22.04 has the old version for the install command

The section for 22.04 has the old version for the install command

There is a note that you may have missed. The Ubuntu feed fro 22.04 will not include .NET 7. Only the Microsoft package feed for 22.04 does have .NET 7.

I checked and the MS feed 22.04 lists .NET 7.


Test make check

Make check was commented out. Just checking why.

Hi! This is the friendly conda-forge-admin automated user.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

 This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

Some tests appear to require libtool as demonstrated by this line.


Posts URLs

Hi,
Thanks for this great theme.
I was wondering if it is possible to create the URLs for the posts similar to the pages. Currently, the URL of the posts is based on the following patterns:
root/year/month/day/[title].html
Is there a way to make it look like the following?
root/posts/[title].html
Based on my experience, Google avoids indexing such pages ("Discovered - currently not indexed") due to (apparently) the link structure.
Besides, I am getting two // in the URLs. What can cause such a problem? (as an example, the URL of this post: https://sinaahmadi.github.io//2019/04/16/text-pre-processing-with-bash.html)
Thanks.

You should be able to use all the Jekyll config to override the config provided in the theme's config.yml... have a read of https://jekyllrb.com/docs/permalinks/ then you could initially just delete the 2nd line of config.yml (ie, remove the config and revert to the default, which is not date-based) or add your own config on this line.
ie, edit this:
permalink: /:categories/:year/:month/:day/:title.html
For the second one, what's the value of your base_url in the config file? If it is "/" then what happens if you set it to just an empty string ""` ?

Thanks very much for your response.


Code with no effect

By the way, following code will not change any state in app
https://github.com/holdennekt/chess_kursach/blob/main/src/script.js#L11-L25

Hurry up, guys!


Implement Mutex<T> syncronization primitive.

Mutex<T> acts kind of like a classical mutex, except that it doesn't block: lock() produces a future, which completes, when the lock can be grabbed.
It very simple. It consists of the data and then an atomic boolean. As there is no spin logic, there is no need for things like futex calls.

Welp. A timeout in some travis tests....

Thanks for the PR. Looking at the code, I don't think that the poll implementation satisfies the required guarantees of Poll::poll. Specifically, if poll returns NotReady, then the task must be notified when the state changes such that poll could succeed.

@carllerche

Thanks for the PR. Looking at the code, I don't think that the poll implementation satisfies the required guarantees of Poll::poll. Specifically, if poll returns NotReady, then the task must be notified when the state changes such that poll could succeed.

Could you elaborate on this. I am not sure I follow.

I'd recommend reading the documentation of the poll function, the implementation here is missing a crucial aspect of that documentation, namely:

When a future is not ready yet, the Async::NotReady value will be returned. In this situation the future will also register interest of the current task in the value being produced.

rtfm, ticki.


Formatting document and renaming variables no longer working

VSCode Version: 1.11
OS Version: archlinux latest

Formatting the document (using Ctrl-Shift-I) and renaming variables (using F2) are no longer working. It's not just the keyboard shortcuts that stopped working, the functionality doesn't work through the menu either. It stopped working a few months ago, possibly after an update but I'm not sure.
When I format the document, nothing changes, whereas before it used to indent the code appropriately. When I rename a variable using F2, nothing changes, and a progress bar appears at the top of the screen and the only way to remove it is to restart vscode.
I tried to reinstall vscode but the problem remains. I also tried disabling all the extension I'm using but the problem also remains. I have a minimal and straightforward user settings json file so I'm not sure if anything there could be causing this issue.
Is there anything I can try to fix it like clearing some cache or starting from scratch somehow?

What language are you working in?

Javascript/NodeJS

Are you still running into this issue. If so, can you please try collecting a trace of the TypeScript server to help investigate:
Can you please try collecting the typescript server trace to see if this is the case:

Set "typescript.tsserver.trace": "verbose"
Restart VSCode
Reproduce the issue
Go to the output panel and share the output from the TypeScript section

Thanks

Thanks for following up, I've just tried with a brand new project and the issue wasn't happening, strangely deleting my .vscode/tasks.json seems to have solved the issue, must have been something strange I had in that file.


[ New Button ] : New Amazing Stylish Submit Button

This is a(Amazing Stylish Submit Button):

[ ] Update to an existing Animated Button
[ ] Any Error
[x] Proposal to the Repository
[ ] Documentation / README.md changes

Details:
Amazing Stylish Glowing loading button effect after clicking

@PoorviShetty @Spyware007 could you look in this matter and assign me this issue.

@PoorviShetty @Spyware007 Could you plz assing me this issue???


fixed grammar & spelling

Fixed a spelling error in the migration theme, and made readability changes to README.

Thank you!


Attribute selector with a regular expression ([attr~=[^xyz]]) not working as expected

The method org.jsoup.select.Evaluator.AttributeWithValueMatching.matches() actually uses the Matcher method find() instead of matches().
This causes many regular expressions not to function as expected like the negation expression in the title.

Just to give a more concrete example, say we have the html:

and use select([attr~=[^c]+]), we still get both elements because the regex matcher is performing a find()

I think it's better to keep the current implementation. You can still run your regex on negations like this: [attr~=^[^c]+$] (i.e., expand the regex to match the full string).
Otherwise, you're going to force everyone who has a regex like [attr~=a|b] to change it to [attr~=.*a|b.*]. It makes the common case harder, and it'll break backward compatibility.


How to set cursorline

It's a really beautiful plugin.   But when i try to set cursorline like this

I have  to input  this command after start neovim
:set cursorline.

I try to add this command in my config file  init.vim   but it doesn't work.
I still try to add the following in my config file
autocmd FileType alpha set cursorline

But this doesn't work either.  I think I must be missing something.       Could you tell me  how to  set cursorline in alpha ?

https://github.com/goolord/alpha-nvim/blob/dafa11a6218c2296df044e00f88d9187222ba6b0/doc/alpha.txt#L339
autocmd User AlphaReady setlocal cursorline should work fine


getstuff bat file not working for windows

Seems like the getstuff.bat file isnt working on windows.
I was debugging and found the link no longer works: https://build.ethdev.com/builds/windows-precompiled
Also, this causes my install to fail because it is not able to find the cryptopp stuff this link is suppose to download.

Same issue here. Server temporarily down?
ERROR CODE:    0x80072ee2 - The operation timed out
ERROR CONTEXT: 0x00000005 - The error occurred while the remote file was being processed.

See https://github.com/Genoil/cpp-ethereum/issues/183


September 2023 Update Adjustments

Resolves #798

I made some additional adjustments

My question still stands

It should be all now


Report: Cmdlet to post test results report to Teams channel

Hi @merill, I would love to help with this. It is something I've wanted to learn for our own internal reports.
I cant make any promises but if you let me know what your expecting as an outcome, I can try and sort this out!

It's alive!


Gradient shenanigans with Siddon's method

As far as I can tell, the gradients flowing through Siddon's method are broken for registration (from either #272 or #283).
In registration.ipynb, to get the image similarity metric to increase, I need to change maximize=False in the optimizer. That is, the gradients appear to be incorrectly pointing in the direction of steepest descent, for some mystical reason. Even after setting maximize=False, the image similarity metric maxes out at around 0.95 out of 1.
This hack isn't needed when using renderer="trilinear". The notebook works without issue with this backend (image similarity metric reaches 0.999 very quickly).
Siddon's method still works perfectly fine for reconstruction.ipynb, so I'm not sure what the issue is. Current best guess is that torch.nn.functional.grid_sample w/ mode="nearest" has broken something that previously worked with the custom implementation of nearest-neighbor interpolation?
Originally posted by @eigenvivek in https://github.com/eigenvivek/DiffDRR/issues/283#issuecomment-2200454691

https://discuss.pytorch.org/t/does-the-nn-funtional-grid-sample-backwards-grad-to-grid/31736/6

Changing the plane offsets from 0.5 to 0 alleviates this issue but NO IDEA why 😵💫
https://github.com/eigenvivek/DiffDRR/blob/7143964357b582a8962fe08365ac6bb47cb54afe/diffdrr/renderers.py#L92-L94

Also found a bug: pretty sure alpha1 should be computed from dims + 1
https://github.com/eigenvivek/DiffDRR/blob/7143964357b582a8962fe08365ac6bb47cb54afe/diffdrr/renderers.py#L124


Ingredient view can't be scrolled

am i just 3head? i can't scroll it @seowalex

also, recipe view doesn't "start to scroll" if items are added offscreen. repro:

start with some N recipes that fit entirely in the view without scrolling
start adding a few recipes. since we switch to the recipe detail view, the recipe list view is hidden
go back to the list view (in any way); the recipes now exceed the window height, but the view can't be scrolled
it starts scrolling only when the window is resized


chore(RingTheory/LocalRing): remove diamond

Can you add a test for this?

I'm not sure what you meant by tests. Do you mean a test that the instance still exists?

See MathlibTest/instance_diamonds

There were two instances of the same signature but with different implementations so I removed one.
I don't think the tests in that file applies here.

bors merge


Skip over zero-byte nodes

This PR checks the byte-width of a node, when constructing the atom collection, to skip zero-width nodes. Along with a slight tweak to the Tree-Sitter Query formatting rules, this allows us to format parameter-less predicates without an undesired space.
(n.b., It would have been nicer to filter out zero-width nodes during the parse, but Tree-Sitter doesn't expose an API to clip nodes from the tree directly.)
Resolves #383

Note: This fixes the problem of a query matching a zero-byte node, then applying formatting that it shouldn't. It doesn't fix the problem of a query failing to match because a zero-byte node exists in the tree which the query doesn't account for (see #420).


Remove dead references to bluelist/blacklist classes

This propagates the term blacklist which holds negative racial connotations across a large set of projects. I initially came to replace this term, but I've now noticed it seems to be unused.

I would kindly ask you to remove the patronizing language from you commit message and only state the technical reasons for your changes.  In fact, it is the first time I hear that the technical term "blacklist" is now offensive.
Please do not understand my change request as a reason for starting a political discussion. In contrary, I ask you limit any discourse solely to technical issues. Thank you.

Obsoleted by #585.


Need a way to reposition suffix control to start (left) position after closing last tab

Is there a way to have the last (rightmost/suffix/add new) TabablzControl tab always repositioned to the far left (starting) position after removing the last content tab? Right now, that last tab does not appear to close the gap made after removing the last content tab. We do not close the window when the last tab is closed.  Setting FixedHeaderCount > 0 is not really an option for us as we don’t have an “always visible” tab to show.
As you mentioned, the gap is currently for allowing dropping an item--something for which we currently have no use.  We just allow for adding tabs via the always visible suffix control, which presents a menu of options for a new tab's content.
Thanks for providing such a cool control!

OK, the fact you have clarified the fact that you wont be dragging into your empty window is helpful: in this case I should be able to provide a single flag to get the behaviour you want.

Terrific!  Thank you.

I just wanted to point out that sometimes the suffix tab will also show a gap even when there still is a content tab showing (i.e. it's not just when the last content tab is removed that the gap can show).  For instance, adding two tabs shows <content 1> <content 2> ; after removing <content 2> the tab control will show <content 1> [gap] .  (Though, oddly enough, if another sequence was used this will not always be the case and a gap would not be shown)  My hope is that your new flag could control whether the suffix tab is always left-justified.  Thank you.

@AdrianKole Please see the new EmptyHeaderSizingHint property.
I think the other thing you have mentioned is more of a dispatcher thing where we need to kick off a new arrange....

I downloaded your changes from the last commits of yours I did not have (and also had to carefully edit the code to remove the null-conditional operator instances and replace them with explicit null tests as we are still using VS 2013).
Unfortunately, if I add the EmptyHeaderSizingHint attribute to a TabablzControl, I end up with a NullReferenceException thrown.  This happens regardless of the value assigned to it ('Collapse' or 'PreviousTab').  Removing the attribute allows the application to start up normally as before getting the latest commits.
The exception unfortunately doesn't have much in the way of detail.  InnerException is null.  The StackTrace property contains "   at System.Windows.Baml2006.Baml2006Reader.Process_PropertyWithConverter()".
Ideas?

OK, i'll have a look

It looks like it may be something different with my project that is causing the problem.  IIRC, earlier today I tried to use the new Dragablz.dll (with the merged in changes) instead with your demo application and even with the attribute added to one of your controls it worked without an exception thrown.  This may at least help rule out the possibility that I incorrectly merged in the new changes.
However, even after having commented-out most all of the XAML in the main window of my project and pasting in a TabablzControl element snippet adapted from your QuickStart example, I could still reproduce the problem if and only if I set the new EmptyHeaderSizingHint attribute on it!  Very strange.
I wish I had more details from the exception.  It would appear from the stack trace that core WPF code is trying to access some property (a new DependencyProperty that's not yet initialized?) and encountering the exception.  If you want, I could e-mail a screenshot of the debugger that provides a deeper stacktrace than just the top of the stack that is provided with the StackTrace property (please let me know the e-mail address to use if you want this--or if there is some way of posting that here).
I'm not sure if it's relevant, but in your projects I have added code signing to the binaries (our code is signed and in order to use your DLL, your DLL needs to be signed too).  This did not cause a problem before and your demo works with this setup too; I just thought I'd point that out.

If all you are doing with your fork is strong naming then I suggest you have a look at StrongNamer and then report back from the official build...

Thanks for the suggestion.  I can keep that in mind in possible future projects.  In this case, however, I do indeed need changes that I added.

I did find a bug, which is fixed and tested...but I don't see how it is related to the issue you are seeing.  If you can reproduce it, with the official nuget .dll then post a git repo and re-open this issue.

Silly me:  the application was loading an old version of the DLL from the new one that was referenced in the project.
I tried out the new behavior and it appears to work well!!
Thanks, ButchersBoy.  It's appreciated!

:+1:


fix: link to KongConsumer and KongCredential doc

What this PR does / why we need it:
fixes link to KongConsumer and KongCredential resources document

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Program exiting will leave controllers connected

If the program crashes/exits unexpectedly, controllers can be left connected. Is there any way to disconnect these controllers? I noticed I can't restart my computer either so I have to force shutdown every time, but this does disconnect the controllers on restart.

It bothers me, too. I try to solve it  by import atexit
Like this:
import atexit

vc = pyxinput.vController(False)

@atexit.register
def unPlug():
    print("Virtual Controller UnPlug")
    vc.UnPlug(True)


Changed build.fsx to make WindowsAzure.Storage a Nuget dependency - Take 2

It can be done,
by using nugets Reference spec http://docs.nuget.org/create/nuspec-reference#specifying-explicit-assembly-references we can bring the files over locally for the typeprovider to use but only reference dependent dlls from nuget.
Tested locally - works fine
fixes #51

@isaacabraham Just grabbing your attention in case you think this pull request is the same as https://github.com/fsprojects/AzureStorageTypeProvider/pull/54
I should have made a better title :)

Just testing this out. The thing I'm unsure of is this: OK, we're now referencing the Azure Storage SDK as a dependency, great. The "References" node - what actually does this do? (cc: @forki) Does it automatically copy the DLLs across from the dependent nuget package to the target folder?
Currently we're still bundling the actual assemblies with the nuget package - isn't the aim to remove them?
So, having a dependency on Azure 4.3.0 is a good first step - but we're still bundling the dependencies manually.

The default action for paket/nuget is to reference all the dlls in the pkg. "references" is a white list of what is allowed to be referenced by paket/nuget.
Yeah we still bundle the dependencies as well, this lets the type provider have a local copy (as our previous attempts to get the type provider to look else where for the files failed) of the files it needs to run. While at the same time the end user doesn't have another copy of them.

ok, i see what you're saying - so the design time TP would use the "internal" copies of the DLLs (that are included in the TP) but will be invisible to the user in terms of project references. OK - just testing it out here.

Pretty much yeah

OK, I've figured it out. I've needed to modify the .nuspec files as well - you have to add the @references@ item in there for the nuget package to be generated correctly. I'll commit and merge shortly.
Cheers :)


Example of using Photino for automation

Hi, is it possible to add an example of using Photino to populate HTML form, submit with redirect to another page, and get parameter from the URL?
Basically, some common tasks that previously could be done with Selenium and Web Driver?
To be clear, the question is about how to execute JS code for an external website, not local wwwroot.
Update
Tried to add JS code dynamically in page load event in Photino.NET, but got an exception, so probably it's a window creation event, not page load event. In this case, the question is, how do I know when it's safe to execute JS code?

Also, tried to execute method with delay, nothing happened, JS code didn't execute.

After searching for some time, I found that this feature is not implemented yet and not clear whether it will be.
https://github.com/tryphotino/photino.NET/issues/58#issuecomment-908549364


if password is changed on data share, password needs to be updated in /etc/fstab

Editing /etc/fstab is not for the faint of heart, so I should probably switch to using credential files, and put them in /vagrant so they can be edited from the host OS (if that's feasible).

https://wiki.ubuntu.com/MountWindowsSharesPermanently

Looks like we can completely avoid editing /etc/fstab by adding a subconfig in /etc/fstab.d

Well, we could have, but /etc/fstab.d support was removed from Ubuntu, even though the directory is present.

To allow for changes to the fstab file and avoid disaster it's probably necessary to manipulate it via scripts driven by a config file.

Looks like the best way to do this would be using dialog, so it looks and feels like a typical install wizard.

This is done.


jrebel & sbt auto reload when scala file changed.

i'm use jrebel & sbt that to auto reload when scala source file have changed.
but i have to open two console for do it,
one is：sbt ~compile    (for compile continuancelly.)
two is：sbt run              (for run main class)
but i'm won't to open console, because it's very bother.
i'm hope to only use  " sbt run " command can auto compile scala source file when that changed.

If I understand you correctly you may use the sbt revolver plugin for this.

Covered by sbt-revolver.


Import AutoBuilder Causes ValueError | Python 3.11

Describe the bug
When running any code with AutoBuilder imported, the following error is produced:
ValueError: mutable default <class 'wpimath.geometry._geometry.Translation2d'> for field positionMeters is not allowed: use default_factory
To Reproduce
Steps to reproduce the behavior:
Import AutoBuilder using the following code:
from pathplannerlib.auto import AutoBuilder
Expected behavior
Code should run with this import statement included as per example code on this page.
Screenshots
Here's the full stacktrace I'm getting with the error.

Versions: (please complete the following information):

OS: Windows 11
GUI Version: Not Applicable
PPLib Version: 2024.0.0b6.post1
PPLib Language: Python 3.11

Additional context
Sorry if this is something I'm doing wrong, but I'm not exactly a practiced Python developer and as far as I can tell from the error it's nothing my code is doing.

This seems to be a problem with python 3.11+. I've been doing dev and testing with 3.10 and that works fine. I'll update the project to be compatible with 3.11

Was a pretty minor fix. I'll push 2024.0.0b6.post2 when #518 gets merged which should fix this for you


Add location to Bigquery::Project#create_dataset

Although our current policy is not to include experimental Cloud Platform API features in gcloud-ruby, this was not our strict policy when we added support for BigQuery, and the ability to read dataset.location at that time, making it seem inconsistent to allow setting this property. Also, as @gramos74 commented today, adding the ability to set location will bring gcloud in line with other tools:

In fact, choosing a location is not only available via API, it is also a option when you create manually a dataset in the BigQuery web console.

[closes #571]

:metal:


.NET CLI Template produces error

Describe the bug
The project produced by the CLI does not run successfully.
To Reproduce
Steps to reproduce the behavior:

Following the documentation in https://hotchocolate.io/docs/dotnet-cli
Install template using "dotnet new -i HotChocolate.Templates.Server"
Generate a new project with "dotnet new graphql -n MyProjectName"
Run the project using Microsoft Visual Studio 2019 using IIS
Get error

Expected behavior
The project successfully run and shows "Hello World"
Desktop (please complete the following information):

Windows 10

Describe bug more precisely

The error is solved by adding additional code at ConfiguringServices() function in Startup.cs, referencing https://hotchocolate.io/docs/tutorial-01-gettingstarted
public void ConfigureServices(IServiceCollection services) {     services.AddGraphQL(services =>         SchemaBuilder.New()             .AddServices(services)             .AddQueryType<Query>()             .Create()); }


Change return type getFilePath to URL

Fixes #148

Will be keeping the string moving forward, this was a bug in the implementation that didn't properly stringified the result from the node API.


Detect when copied and original variable is used

I have the following code which I extracted from a test:
		for _, req := range testRequests {
			failingReq := req // <----- here
			failingReq.ExpectBody = test.ErrorCode(keppel.ErrTooManyRequests)
			failingReq.ExpectStatus = http.StatusTooManyRequests
			failingReq.Check(t, h)

			s.Clock.StepBy(time.Second)
			req.Check(t, h)
		}

req gets copied and modified and both are used. I think the linter should ignore this or at least add an option to ignore it.

@SuperSandro2000
There is the ignore-alias option. Have you tried it?"
linters:
  disable-all: true
  enable:
    - copyloopvar

linters-settings:
  copyloopvar:
    ignore-alias: true


Bad Goss sha256sum in generated verify.yml

Issue Type

Bug report

Molecule and Ansible details
ansible 2.7.1
  config file = None
  configured module search path = [u'/Users/vivienbrissat/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules']
  ansible python module location = /usr/local/lib/python2.7/site-packages/ansible
  executable location = /usr/local/bin/ansible
  python version = 2.7.15 (default, Sep 12 2018, 13:24:28) [GCC 4.2.1 Compatible Apple LLVM 9.1.0 (clang-9<IP_ADDRESS>)]
molecule, version 2.19.0

Molecule installation method (one of):

pip

Ansible installation method (one of):

OS package (brew)

Detail any linters or test runners used:
Actual sha256sum in verify.yml when generated via molecule init --verifier-name goss
goss_version: v0.3.6
goss_sha256sum: 2f6727375db2ea0f81bee36e2c5be78ab5ab8d5981f632f761b25e4003e190ec

This does not work with molecule test since it's a bad sha256sum, and the playbook can't download Goss.
It seems that the sha256sum has changed
i found that 53dd1156ab66f2c4275fd847372e6329d895cfb2f0bcbec5f86c1c4df7236dde is the actual sha256sum for Goss v0.3.6 (i don't know why ^^).
When i change the checksum in the playbook verify.yml it works fine.

Done!


Fix formatting issue when first line is blank.

For #11416

[x] Pull request represents a single change (i.e. not fixing disparate/unrelated things in a single PR).
[x] Title summarizes what is changing.
[x] Has a news entry file (remember to thank yourself!).
[ ] Appropriate comments and documentation strings in the code.
[ ] Has sufficient logging.
[ ] Has telemetry for enhancements.
[x] Unit tests & system/integration tests are added/updated.
[ ] Test plan is updated as appropriate.
[ ] package-lock.json has been regenerated by running npm install (if dependencies have changed).
[ ] The wiki is updated with any design decisions/details.

Codecov Report

Merging #11744 into master will decrease coverage by 0.05%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##           master   #11744      +/-   ##
==========================================
- Coverage   60.71%   60.66%   -0.06%
==========================================
  Files         629      628       -1
  Lines       33999    33907      -92
  Branches     4793     4774      -19
==========================================
- Hits        20643    20570      -73
+ Misses      12350    12339      -11
+ Partials     1006      998       -8

Impacted Files
Coverage Δ

src/client/common/editor.ts
8.25% <0.00%> (ø)

src/datascience-ui/react-common/arePathsSame.ts
75.00% <0.00%> (-12.50%)
:arrow_down:

src/client/common/utils/platform.ts
64.70% <0.00%> (-11.77%)
:arrow_down:

src/client/common/utils/misc.ts
63.63% <0.00%> (-10.73%)
:arrow_down:

src/client/logging/transports.ts
77.77% <0.00%> (-3.48%)
:arrow_down:

src/client/common/utils/decorators.ts
78.02% <0.00%> (-2.38%)
:arrow_down:

src/client/linters/pydocstyle.ts
86.66% <0.00%> (-2.23%)
:arrow_down:

src/client/datascience/debugLocationTracker.ts
76.56% <0.00%> (-1.57%)
:arrow_down:

src/client/common/process/proc.ts
14.49% <0.00%> (-0.73%)
:arrow_down:

src/client/datascience/jupyter/jupyterImporter.ts
15.90% <0.00%> (-0.57%)
:arrow_down:

... and 16 more

Continue to review full report at Codecov.

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


[rancher-compose] Add command to download current docker-compose.yml and rancher-compose.yml

I have more than once forgot to update the local copy of my {docker,rancher}-compose.yml file before running an upgrade.  It would be nice if I can programatically pull in the latest yml files from the rancher server given the rancher_access_key and rancher_secret_key.

This is supported in the new Rancher CLI which supports rancher export.


@vlcn.io/crsqlite@npm:0.9.0 couldn't be built successfully

Awesome library! Thanks for your work on this. Running into an error that I don't think I had seen pre 0.9:
Using yarn 3.2.1 on macos 11.6.7, upon running yarn add @vlcn.io/crsqlite, I see the following error:
@vlcn.io/crsqlite@npm:0.9.0 couldn't be built successfully (exit code 1, logs can be found here: /private/var/folders/k9/k1lmv1lx1jd4q_wsnrn732ch0000gn/T/xfs-c1f8d7ec/build.log)

The error log:
# This file contains the result of Yarn building a package (@vlcn.io/crsqlite@npm:0.9.0)
# Script name: install

node:internal/errors:464
    ErrorCaptureStackTrace(err);
    ^

TypeError [ERR_UNKNOWN_FILE_EXTENSION]: Unknown file extension ".json" for<EMAIL_ADDRESS>    at new NodeError (node:internal/errors:371:5)
    at Object.getFileProtocolModuleFormat [as file:] (node:internal/modules/esm/get_format:87:11)
    at defaultGetFormat (node:internal/modules/esm/get_format:102:38)
    at defaultLoad (node:internal/modules/esm/load:21:14)
    at ESMLoader.load (node:internal/modules/esm/loader:359:26)
    at ESMLoader.moduleProvider (node:internal/modules/esm/loader:280:58)
    at new ModuleJob (node:internal/modules/esm/module_job:66:26)
    at ESMLoader.#createModuleJob (node:internal/modules/esm/loader:297:17)
    at ESMLoader.getModuleJob (node:internal/modules/esm/loader:261:34)
    at async ModuleWrap.<anonymous> (node:internal/modules/esm/module_job:81:21) {
  code: 'ERR_UNKNOWN_FILE_EXTENSION'
}

Was able to get it installed with yarn 3 locally on my system so it is probably related to the node version being run. Can you let me know which version and if you can import a json file like what is done in nodejs-install-helper.js?

Works with node 19.7. :)


fast vector operation for pillar scatter

This PR introduces fast vector operations for pillar scatter module. The for loop in exisiting module make model forward very slow. Especially with larger batch sizes.
The code has been tested to check for equal outputs before and after the changes and included in this PR
latency experiments:

forward times as a function of batch_size

Overall training time before and after the change

Before -> Average per iteration training time ~2.9sec

After -> Average per iteration training time ~1.9sec

The training time per iteration reduces by 35% with this PR (for my set of parameters / dataset)

@dmund95 the pipeline stayed the same and training is working for your properly? Seems like an useful improvement.

Yes, I have been training and deploying models with this change and no issues.