Increase resolution

Hi
Can you advise the steps in order to handle a  resolution up to 1080 if possible? Which configuration settings should be changed? is re-training required?
Trying to achieve pose detection but at long distance.
Thanks

Hi jptalledo10,
Thanks for reaching out!
If you expect all objects will be of a similar scale, It may be worth trying the model directly on a larger image to figure out which scale works for your application.
At first, I would suggest doing this with the pre-trained model, simply changing the size of the image when you optimize with TensorRT.
If the scale of the objects varies greatly (like full image size - small block of pixels), it is unlikely the models would handle all scales out of the box.  You can consider they are good at detecting objects with a size of about 112-224 pixels tall (I'm assuming for the 224px image they detect objects down to about half the image height).
Please let me know if this helps or you have any questions.
Best,
John

@jaybdub
I assume you are suggesting to change the following:
WIDTH = 224
HEIGHT = 224
data = torch.zeros((1, 3, HEIGHT, WIDTH)).cuda()
To a bigger image size from the camera source? like 1920x1080?
Can you elaborate further about the pre-trained model?
Thanks

Hi @jaybdub, can you elaborate more on how to use larger size images?


fixed indentation in code sample in readme

Tiny change but appreciated, thanks :-)

@ZuBB out of nowhere but I will be visiting Ukraine and Kyiv in August. Happy to have a chat if you are around!

@oncletom since I am in Kyiv that's definitely possibly :)
Do you know (approximate) date when you will be here? (I am going to visit events in August, but all another days should be OK)


[v15] Initial faster blocks + Upgrade

Built off the v14 cleanup PR
TODO:

Faster block times (cherry pick / merge Jacobs line change here)
Ensure x/mint and the yearly 3rd-ing are good
Maybe get a TF feature in (use gas instead of denom price)? Will see

@Reecepbcups fyi I can't be certain it's the right cherry pick actually.
When testing that PR, I encountered oddity.

@faddat Alright Ill mess with it later with my setup and see

@faddat Yes, so on the load of the config.toml, I force set the Tendermint Commit Timeout. SDK v45 only supports changing the app.toml, so I had to pull out the functions from v45 and add that line
So no matter what is in your config.toml, 3 second commits is used
(I may add a bypass in the future for our CI pipelines and local testing, but 3s is fine for now)

I can swear we did it differently for EVMOS, but this is no matter.  Thanks for hacking the hack.

@faddat Evmos - SDK fork. Osmosis - SDK fork. Eve - v0.46
All who have overrides are not on v45. Only reason for the hacky hack rn.
When  we move to 47 in the future, my hacky here can be reverted

@Reecepbcups everything looks good, I muscle-memory'd "update branch"; revert freely if needed (but looks good from here)

It’s good - just MEV patch + fixed CI 👌🏼

nice work here ser

Since we've upgraded to v14 now, can we work to get this merged to main so that main becomes the default PR target?
Thanks!


feat(retain): enhance label propagation

don't sync labels like kubeadmiral.io/propagation-policy-name to members
merge desired and observed labels during update to allow controllers in member clusters to manipulate labels
propagate deletion of labels/annotation from template to members

Thanks
/lgtm


Upgrade pip

Description

Upgrade pip when venv is created
Fix a potential error in pip install

Should we add pip >= 21.0.1 to the requirements file?
The tests run fine on my machine but seem to be unstable on jenkins. The tests also become a lot slower. So what do we do about it? The current irt moduleset issues seem to be related to not having a pip that can install cryptography (which might be fixable with doing correct PYTHONPATH inheritance)
Self Check:
Strike through any lines that are not applicable (~~line~~) then check the box

[ ] Attached issue to pull request
[ ] Changelog entry
[ ] Type annotations are present
[ ] Code is clear and sufficiently documented
[ ] No (preventable) type errors (check using make mypy or make mypy-diff)
[ ] Sufficient test cases (reproduces the bug/tests the requested feature)
[ ] Correct, in line with design
[ ] End user documentation is included or an issue is created for end-user documentation (add ref to issue here: )

Reviewer Checklist:

[ ] Sufficient test cases (reproduces the bug/tests the requested feature)
[ ] Code is clear and sufficiently documented
[ ] Correct, in line with design

And longer means 3 times longer

what happens when we do venv.create(path, clear=True, with_pip=False)

This is my machine:
Results (1692.77s):
1270 passed

I don't think it will hurt if we add pip >= 21.0.1.

yes, but as it is we cannot merge it. So that  is why I made a draft to crowdsource ideas

Without pip works well, it will use the pip from the parent env


Incorrect wording in Forwarding Modules

The Forwarding Modules section currently says

If there's a member defined in the current source file named name with the same type as member, do nothing.

This implies that even nested member definitions shadow forwarded modules, which is incorrect. It's also largely redundant, since member declarations already override the previous values in the modules. It should instead just indicate that variables (the only members that can be defined before a @forward) that are already in the module should not be overridden by @forward.
It's probably also a good idea to have a non-normative note indicating that other local members override the @forwarded members.

It's also largely redundant, since member declarations already override the previous values in the modules.

This is actually inaccurate; it's important that all shadowed members return early so that they don't produce errors in case of conflicts.


Improvement for k8s.io/docs/reference/setup-tools/kubeadm/kubeadm-kubeconfig/

Hello, I propose to add how to create a config for success in creating a new kubeconfig and solve this problem (if exists put the link in the config param of the documentation):
test@test:/etc/kubernetes/pki$ sudo kubeadm kubeconfig user --client-name=test --v=5
required flag(s) "config" not set

The page already links to examples

For examples on how to use kubeadm kubeconfig user see Generating kubeconfig files for additional users.

/close
/sig cluster-lifecycle


Synchronization  problem

Hi,
I could not manage to sync,
In Chrome
There are  links in the side panel
In obsidian
The poop up slashed and told the synchronization was successful
But no file was created
Digging in the console:

a message confirming that the server responded

{
    "status": 200,
    "headers": {
        "access-control-allow-origin": "*",
        "content-encoding": "br",
        "content-type": "application/json",
        "date": "Mon, 21 Oct 2024 08:27:41 GMT",
        "fly-request-id": "01JAQ30TAQ66NYCBK8MW7R0507-fra",
        "server": "Fly/27d4b875a (2024-10-17)",
        "traceparent": "00-7937303a01360db585bb73d719d74872-ec59e32d1e5abf13-01",
        "tracestate": "",
        "vary": "origin, access-control-request-method, access-control-request-headers",
        "via": "2 fly.io"
    },
    "arrayBuffer": {},
    "json": [],
    "text": "[]"
}

But also, a page error "Ensure CORS response header values are valid"

Thanks for reporting! I just tested this on the latest version of Obsidian and didn't run into this. Can you share what version of Obsidian you're using and what OS you're on?

There are links in the side panel

Can you elaborate on what you mean by this?


Fix CanRCM5-SN

see further metadata in #42

@gnikulin This should fix the CanRCM5-SN source_id including further info url. The cmor CV table will also be updated...

looks good


3D of GLES2 does not really work on Android devices with GLES2 GPU

Godot version:
Godot 3.1 master branch at 2018-08-13
OS/device including version:
Tested on
Android 4.4.2 - MTK6592 - 1GB - GPU Mali 450 MP4 700Mhz - GL2.0
Android 4.4.2 - BCM23550 - 1GB - GPU VideoCore IV - GL2.0
(have fiew more devices like these but since errors are exacly same on those 2, then i assume that rest will be same) Note that Godot 2.1.5 works on these devices very well.
Issue description:
2D seems to work (not really tested yet since i mostly aim at 3D features. Just placed Label on screen to show FPS and its visible)
3D mode while on GLES2 GPU android device, shows only background (sky/ground color) and nothing more, no 3D objects are visible, and if more complex 3D objects are added it crashes after splash screen..
Most simple starting cube exported from blender are invisible on android and throws many errors
0:00:00:0369 - Directional shadow framebuffer status invalid
----------
Type:Error
Description:
Time: 0:00:00:0369
C Error: Directional shadow framebuffer status invalid
C Source: drivers\gles2\rasterizer_scene_gles2.cpp:2313
C Function: initialize

0:00:03:0482 - CubemapFilterShaderGLES2: Program linking failed:
ERROR:PREPROCESSOR-3 (line 2) #extension if a required extension extension_name is not supported, or if all is specified
----------
Type:Error
Description:
Time: 0:00:03:0482
C Error: CubemapFilterShaderGLES2: Program linking failed:
ERROR:PREPROCESSOR-3 (line 2) #extension if a required extension extension_name is not supported, or if all is specified
C Source: drivers\gles2\shader_gles2.cpp:509
C Function: get_current_version

0:00:03:0483 - Method/Function Failed, returning: __null
----------
Type:Error
Description:
Time: 0:00:03:0483
C Error: Method/Function Failed, returning: __null
C Source: drivers\gles2\shader_gles2.cpp:517
C Function: get_current_version

0:00:03:0483 - Condition ' !version ' is true. returned: false
----------
Type:Error
Description:
Time: 0:00:03:0483
C Error: Condition ' !version ' is true. returned: false
C Source: drivers\gles2\shader_gles2.cpp:133
C Function: bind

0:00:03:0521 - Condition ' !version ' is true. returned: -1
----------
Type:Error
Description:
Time: 0:00:03:0521
C Error: Condition ' !version ' is true. returned: -1
C Source: drivers\gles2/shader_gles2.h:509
C Function: _get_uniform
(this error repeated many times)

0:00:03:0747 - Too many errors! 165 errors were dropped.
----------
Type:Error
Description: Too many errors! 165 errors were dropped.
Time: 0:00:03:0747
C Error: TOO_MANY_ERRORS
C Source: :-137673423
C Function:

Attached Project with simple cube from blender
test7.zip
The same project contain another object a little more complex (Cube.tscn),
If you add it to scene, it will completly crash on android with GLES2 GPU after splash screen.
CSG objects are invisible on android also if you try to place them for test.
Basicaly - no 3D objects are visible in 3D mode on android with GLES2 GPU
Steps to reproduce:
Run example project (test7.zip attached above) on android device with GLES2 GPU

simple cube exported from blender will not be visible.
the more complex object Cube.tscn which is also available within project folder, after being added to scene will crash godot on android just after splash screen.
try to place CSG objects, they are also invisible on android.

Minimal reproduction project:

can use example project provided above test7.zip which contain simple cube exported from blender and another object which is a little more complex and crash godot.
Or you can export something from blender and try to display it on android device with GLES2 GPU

This seems related to #20734.

Will take a look

So the extension in CubemapFilterShaderGLES2 can be substituted for something that might work less good but at least it will run. That fix is easy to make.
The other problem is that your device doesn't seem to support depth textures, so renderbuffers have to be used (which are write only) with an additional color attachement to write to a shader-readable texture that can be used for shadows.
The first thing is an easy thing to fix, the second one might take some more, I'll work on it and report back!

@karroffel
I took some info from one of the android devices (GLES2 Mali450) mentioned above in bug report, that might be helpful.
Info taken taken by godot 2.1.5 debug
GL_ARM_mali_program_binary
GL_ARM_mali_shader_binary
GL_ARM_rgba8
GL_EXT_blend_minmax
GL_EXT_debug_marker
GL_EXT_discard_framebuffer
GL_EXT_multisampled_render_to_texture
GL_EXT_robustness
GL_EXT_shader_texture_lod
GL_EXT_texture_format_BGRA8888
GL_KHR_debug
GL_OES_EGL_image
GL_OES_EGL_image_external
GL_OES_EGL_sync
GL_OES_compressed_ETC1_RGB8_texture
GL_OES_depth24
GL_OES_depth_texture
GL_OES_depth_texture_cube_map
GL_OES_get_program_binary
GL_OES_packed_depth_stencil
GL_OES_rgb8_rgba8
GL_OES_standard_derivatives
GL_OES_texture_npot
GL_OES_vertex_half_float

info from same device taken by adb shell dumpsys SurfaceFlinger
GLES: ARM, Mali-450 MP, OpenGL ES 2.0
GL_EXT_debug_marker GL_OES_texture_npot GL_OES_compressed_ETC1_RGB8_texture GL_O
ES_standard_derivatives GL_OES_EGL_image GL_OES_depth24 GL_ARM_rgba8 GL_ARM_mali
_shader_binary GL_OES_depth_texture GL_OES_packed_depth_stencil GL_EXT_texture_f
ormat_BGRA8888 GL_OES_vertex_half_float GL_EXT_blend_minmax GL_OES_EGL_image_ext
ernal GL_OES_EGL_sync GL_OES_rgb8_rgba8 GL_EXT_multisampled_render_to_texture GL
_EXT_discard_framebuffer GL_OES_get_program_binary GL_ARM_mali_program_binary GL
_EXT_shader_texture_lod GL_EXT_robustness GL_OES_depth_texture_cube_map GL_KHR_d
ebug
EGL implementation : 1.4 Linux-r4p0-00rel0
EGL_KHR_image EGL_KHR_image_base EGL_KHR_image_pixmap EGL_KHR_gl_texture_2D_imag
e EGL_KHR_gl_texture_cubemap_image EGL_KHR_gl_renderbuffer_image EGL_KHR_fence_s
ync EGL_ANDROID_image_native_buffer EGL_ANDROID_recordable EGL_ANDROID_native_fe
nce_sync EGL_ANDROID_framebuffer_target EGL_EXT_create_context_robustness EGL_AN
DROID_blob_cache
info taken by OpenGL Extensions app from app store
ARM
Mali-450 MP
OpenGL ES 2.0
GL_EXT_debug_marker GL_OES_texture_npot GL_OES_compressed_ETC1_RGB8_texture GL_OES_standard_derivatives GL_OES_EGL_image GL_OES_depth24 GL_ARM_rgba8 GL_ARM_mali_shader_binary GL_OES_depth_texture GL_OES_packed_depth_stencil GL_EXT_texture_format_BGRA8888 GL_OES_vertex_half_float GL_EXT_blend_minmax GL_OES_EGL_image_external GL_OES_EGL_sync GL_OES_rgb8_rgba8 GL_EXT_multisampled_render_to_texture GL_EXT_discard_framebuffer GL_OES_get_program_binary GL_ARM_mali_program_binary GL_EXT_shader_texture_lod GL_EXT_robustness GL_OES_depth_texture_cube_map GL_KHR_debug

might be useful.
crash log has been taken from Mali450 MP4 device.
project used in test can be found in first post of this issue (test7.zip)
in crash test Cube.tscn has been added to scene (included in project folder but not added to scene)
godot_crash_log_android_mali450MP4_logcat.zip

closing since it seems fixed at current time.
(The objects are visible now, and error spam is gone)

So the extension in CubemapFilterShaderGLES2 can be substituted for something that might work less good but at least it will run. That fix is easy to make.

How do I do this?


Update functions.scala

What changes were proposed in this pull request?
Updated the description for the format_number description to indicate that it uses HALF_EVEN rounding.
How was this patch tested?
Just changing the function's comment so no testing involved.
Please review http://spark.apache.org/contributing.html before opening a pull request.

Can one of the admins verify this patch?

Have a look at http://spark.apache.org/contributing.html as the template says.
I think you'd want to describe this a little more, and consider whether other functions could use this detail?

Hmm @srowen do you mean describe HALF_EVEN round mode? Also, I know some of the other functions that use this type of rounding already include it in their definition.

No I really meant fill out the PR a little more (see link). The title isn't descriptive.
If you mean this is just making the docs consistent that's great, just note that in the description here. Helps reviewers understand why you think this change should happen.

Thanks for contributing to Spark @roxannemoslehi !
I think Sean just means updating the title to something more like [DOCS] Clarify round mode in format_number function.  It doesn't feel big enough to be worth a Jira ticket for such a small docs change.

Yea we definitely need a better title. Thanks for contributing though.

@roxannemoslehi can you fix the title? We can then merge this.

Yup! Sorry about that everyone. Looks like my intended commit message didn't make it through originally but should be fixed now!

How about the doc of the round(Column) method earlier, same thing?

Looks like round uses HALF_UP rounding mode

Thanks - merging in master.


Installation problem on pypy 7.3.0

OS: Ubuntu 19.10
Python: 2.7.13 (724f1a7d62e8, Dec 23 2019, 15:36:24)
CPU: Intel® Core™ i5-1035G4
The below is the error message during installation of scipy

Collecting scipy
Using cached https://files.pythonhosted.org/packages/04/ab/e2eb3e3f90b9363040a3d885ccc5c79fe20c5b8a3caa8fe3bf47ff653260/scipy-1.4.1.tar.gz
Installing build dependencies: started
Installing build dependencies: finished with status 'done'
Getting requirements to build wheel: started
Getting requirements to build wheel: finished with status 'done'
Preparing wheel metadata: started
Preparing wheel metadata: finished with status 'error'
ERROR: Command errored out with exit status 1:
command: /home/donguk/pypy/pypy3.6-v7.3.0-linux64/bin/pypy3 /home/donguk/.local/lib/pypy3.6/site-packages/pip/_vendor/pep517/_in_process.py prepare_metadata_for_build_wheel /tmp/tmpnnd9p80t
cwd: /tmp/pip-install-i254xydk/scipy
Complete output (124 lines):
lapack_opt_info:
lapack_mkl_info:
libraries mkl_rt not found in ['/home/donguk/pypy/pypy3.6-v7.3.0-linux64/lib', '/usr/local/lib', '/usr/lib64', '/usr/lib', '/usr/lib/x86_64-linux-gnu']
NOT AVAILABLE
openblas_lapack_info:
  libraries openblas not found in ['/home/donguk/pypy/pypy3.6-v7.3.0-linux64/lib', '/usr/local/lib', '/usr/lib64', '/usr/lib', '/usr/lib/x86_64-linux-gnu']
  NOT AVAILABLE

system_info:
  NOT AVAILABLE

atlas_3_10_threads_info:
Setting PTATLAS=ATLAS
  libraries tatlas,tatlas not found in /home/donguk/pypy/pypy3.6-v7.3.0-linux64/lib
  libraries lapack_atlas not found in /home/donguk/pypy/pypy3.6-v7.3.0-linux64/lib
  libraries tatlas,tatlas not found in /usr/local/lib
  libraries lapack_atlas not found in /usr/local/lib
  libraries tatlas,tatlas not found in /usr/lib64
  libraries lapack_atlas not found in /usr/lib64
  libraries tatlas,tatlas not found in /usr/lib
  libraries lapack_atlas not found in /usr/lib
  libraries tatlas,tatlas not found in /usr/lib/x86_64-linux-gnu
  libraries lapack_atlas not found in /usr/lib/x86_64-linux-gnu
<class 'numpy.distutils.system_info.atlas_3_10_threads_info'>
  NOT AVAILABLE

atlas_3_10_info:
  libraries satlas,satlas not found in /home/donguk/pypy/pypy3.6-v7.3.0-linux64/lib
  libraries lapack_atlas not found in /home/donguk/pypy/pypy3.6-v7.3.0-linux64/lib
  libraries satlas,satlas not found in /usr/local/lib
  libraries lapack_atlas not found in /usr/local/lib
  libraries satlas,satlas not found in /usr/lib64
  libraries lapack_atlas not found in /usr/lib64
  libraries satlas,satlas not found in /usr/lib
  libraries lapack_atlas not found in /usr/lib
  libraries satlas,satlas not found in /usr/lib/x86_64-linux-gnu
  libraries lapack_atlas not found in /usr/lib/x86_64-linux-gnu
<class 'numpy.distutils.system_info.atlas_3_10_info'>
  NOT AVAILABLE

atlas_threads_info:
Setting PTATLAS=ATLAS
  libraries ptf77blas,ptcblas,atlas not found in /home/donguk/pypy/pypy3.6-v7.3.0-linux64/lib
  libraries lapack_atlas not found in /home/donguk/pypy/pypy3.6-v7.3.0-linux64/lib
  libraries ptf77blas,ptcblas,atlas not found in /usr/local/lib
  libraries lapack_atlas not found in /usr/local/lib
  libraries ptf77blas,ptcblas,atlas not found in /usr/lib64
  libraries lapack_atlas not found in /usr/lib64
  libraries ptf77blas,ptcblas,atlas not found in /usr/lib
  libraries lapack_atlas not found in /usr/lib
  libraries ptf77blas,ptcblas,atlas not found in /usr/lib/x86_64-linux-gnu
  libraries lapack_atlas not found in /usr/lib/x86_64-linux-gnu
<class 'numpy.distutils.system_info.atlas_threads_info'>
  NOT AVAILABLE

atlas_info:
  libraries f77blas,cblas,atlas not found in /home/donguk/pypy/pypy3.6-v7.3.0-linux64/lib
  libraries lapack_atlas not found in /home/donguk/pypy/pypy3.6-v7.3.0-linux64/lib
  libraries f77blas,cblas,atlas not found in /usr/local/lib
  libraries lapack_atlas not found in /usr/local/lib
  libraries f77blas,cblas,atlas not found in /usr/lib64
  libraries lapack_atlas not found in /usr/lib64
  libraries f77blas,cblas,atlas not found in /usr/lib
  libraries lapack_atlas not found in /usr/lib
  libraries f77blas,cblas,atlas not found in /usr/lib/x86_64-linux-gnu
  libraries lapack_atlas not found in /usr/lib/x86_64-linux-gnu
<class 'numpy.distutils.system_info.atlas_info'>
  NOT AVAILABLE

lapack_info:
  libraries lapack not found in ['/home/donguk/pypy/pypy3.6-v7.3.0-linux64/lib', '/usr/local/lib', '/usr/lib64', '/usr/lib', '/usr/lib/x86_64-linux-gnu']
  NOT AVAILABLE

lapack_src_info:
  NOT AVAILABLE

  NOT AVAILABLE

/home/donguk/pypy/pypy3.6-v7.3.0-linux64/lib-python/3/importlib/_bootstrap.py:228: UserWarning: builtins.type size changed, may indicate binary incompatibility. Expected 872, got 416
  return f(*args, **kwds)
setup.py:420: UserWarning: Unrecognized setuptools command ('dist_info --egg-base /tmp/pip-modern-metadata-tl18226f'), proceeding with generating Cython sources and expanding templates
  ' '.join(sys.argv[1:])))
Running from scipy source directory.
/tmp/pip-build-env-0kojva8j/overlay/site-packages/numpy/distutils/system_info.py:572: UserWarning:
    Atlas (http://math-atlas.sourceforge.net/) libraries not found.
    Directories to search for the libraries can be specified in the
    numpy/distutils/site.cfg file (section [atlas]) or by setting
    the ATLAS environment variable.
  self.calc_info()
/tmp/pip-build-env-0kojva8j/overlay/site-packages/numpy/distutils/system_info.py:572: UserWarning:
    Lapack (http://www.netlib.org/lapack/) libraries not found.
    Directories to search for the libraries can be specified in the
    numpy/distutils/site.cfg file (section [lapack]) or by setting
    the LAPACK environment variable.
  self.calc_info()
/tmp/pip-build-env-0kojva8j/overlay/site-packages/numpy/distutils/system_info.py:572: UserWarning:
    Lapack (http://www.netlib.org/lapack/) sources not found.
    Directories to search for the sources can be specified in the
    numpy/distutils/site.cfg file (section [lapack_src]) or by setting
    the LAPACK_SRC environment variable.
  self.calc_info()
Traceback (most recent call last):
  File "/home/donguk/.local/lib/pypy3.6/site-packages/pip/_vendor/pep517/_in_process.py", line 257, in <module>
    main()
  File "/home/donguk/.local/lib/pypy3.6/site-packages/pip/_vendor/pep517/_in_process.py", line 240, in main
    json_out['return_val'] = hook(**hook_input['kwargs'])
  File "/home/donguk/.local/lib/pypy3.6/site-packages/pip/_vendor/pep517/_in_process.py", line 110, in prepare_metadata_for_build_wheel
    return hook(metadata_directory, config_settings)
  File "/tmp/pip-build-env-0kojva8j/overlay/site-packages/setuptools/build_meta.py", line 156, in prepare_metadata_for_build_wheel
    self.run_setup()
  File "/tmp/pip-build-env-0kojva8j/overlay/site-packages/setuptools/build_meta.py", line 237, in run_setup
    self).run_setup(setup_script=setup_script)
  File "/tmp/pip-build-env-0kojva8j/overlay/site-packages/setuptools/build_meta.py", line 142, in run_setup
    exec(compile(code, __file__, 'exec'), locals())
  File "setup.py", line 540, in <module>
    setup_package()
  File "setup.py", line 536, in setup_package
    setup(**metadata)
  File "/tmp/pip-build-env-0kojva8j/overlay/site-packages/numpy/distutils/core.py", line 135, in setup
    config = configuration()
  File "setup.py", line 435, in configuration
    raise NotFoundError(msg)
numpy.distutils.system_info.NotFoundError: No lapack/blas resources found.
----------------------------------------

ERROR: Command errored out with exit status 1: /home/donguk/pypy/pypy3.6-v7.3.0-linux64/bin/pypy3 /home/donguk/.local/lib/pypy3.6/site-packages/pip/_vendor/pep517/_in_process.py prepare_metadata_for_build_wheel /tmp/tmpnnd9p80t Check the logs for full command output.

@rgommers  how can I install OpenBLAS/MKL/ATLAS in a docker container?

You can install OpenBLAS (preferred) or ATLAS with your Linux distro's package manager.


Upgrade CI template for Visual Studio 2022

Azure CI has upgraded to Visual Studio 2022. Our template needs upgrade as well.

CI passed successfully now. But there is another problem.
vcpkg has upgraded openssl to 3.0.2, with which our current code does not work quite well.
Issues with openssl 3.0.2:

PKCS 12 API new algorithm
This means that we can't import P12 files created by softether built with openssl 1.x (which uses legacy algorithms). There must be a way to fix that but I don't know how. According to official docs, we need to load legacy provider first. I tried that but it's not working.
Related issue: https://github.com/openssl/openssl/issues/18046
Lots of deprecation warnings during compilation

@davidebeatrici @chipitsine What do you think? Shall we fix these before merging? Or shall we pin to openssl 1.1.1? How?

alternatively we can use "old" windows image

Let's merge this pull request and wait for an update in the linked issue.

alternatively we can use "old" windows image

We wouldn't solve the problem because we install OpenSSL using vcpkg. As a workaround we can checkout the last commit before the port got updated.

OK. I am merging it, as the main task is keeping CI working.
We can checkout an old commit of vcpkg for the time being, but eventually we need to live with openssl 3.0. Ubuntu 22.04 is coming this work with openssl 3.0.


Failed to produce diagnostic for invalid projected value in ForEach content

Description
The compiler reports Failed to produce diagnostic for expression when trying to use projected value in closure but the parameter is not actually a property wrapper.
Reproduction
struct User: Identifiable {
    let id = UUID()
    let name: String
}

struct ContentView: View {

    let users: [User] = []

    var body: some View {
        ForEach(users) { $user in
            Text(user.name)
        }
    }
}

Expected behavior
It would be good a diagnostic saying that the parameter type doesn't support projected value and a suggestion to remove the $, something like:
ForEach(users) { $user in // ❌ Type 'User' doesn't support projected value; did you mean to use 'user' instead? Remove '$'
    Text(user.name)
}

Environment
swift-driver version: <IP_ADDRESS> Apple Swift version 5.10 (swiftlang-<IP_ADDRESS> clang-15<IP_ADDRESS>)
Target: arm64-apple-macosx14.0
Additional information
No response

I tried running this code with Swift 6.0 toolchain in Xcode 15.3 and it does report Inferred projection type 'User' is not a property wrapper, but only for a second and then goes back to Failed to produce diagnostic for expression.


Cy.origin causes TypeError: Failed to construct 'URL': Invalid URL

Current behavior
Using cy.origin causes the exception (uncaught exception)TypeError: Failed to construct 'URL': Invalid URL And when using cy.origin in beforeEach() hook, the subsequent tests don't run due to this error. Here is the console error
index.bf30ee46.js:99332 TypeError: The following error originated from your test code, not from Cypress.

  > Failed to construct 'URL': Invalid URL

When Cypress detects uncaught errors originating from your test code it will automatically fail the current test.

Because this error occurred during a `before each` hook we are skipping all of the remaining tests.
    at Context.eval (cypress/support/e2e.js:20:7)
From previous event:
    at CommandQueue.run (https://google.com/__cypress/runner/cypress_runner.js:171640:21)
    at CommandQueue.run (https://google.com/__cypress/runner/cypress_runner.js:156283:15)
    at $Cy.runQueue (https://google.com/__cypress/runner/cypress_runner.js:157333:14)
    at cy.<computed> [as origin] (https://google.com/__cypress/runner/cypress_runner.js:157442:12)
    at __stackReplacementMarker (https://google.com/__cypress/runner/cypress_runner.js:156789:13)
    at runnable.fn (https://google.com/__cypress/runner/cypress_runner.js:157625:19)
    at callFn (https://google.com/__cypress/runner/cypress_runner.js:107910:21)
    at ../driver/node_modules/mocha/lib/runnable.js.Runnable.run (https://google.com/__cypress/runner/cypress_runner.js:107897:7)
    at https://google.com/__cypress/runner/cypress_runner.js:164934:30
From previous event:
    at Object.onRunnableRun (https://google.com/__cypress/runner/cypress_runner.js:164919:53)
    at $Cypress.action (https://google.com/__cypress/runner/cypress_runner.js:153707:28)
    at Runnable.run (https://google.com/__cypress/runner/cypress_runner.js:162582:13)
    at next (https://google.com/__cypress/runner/cypress_runner.js:108412:10)
    at https://google.com/__cypress/runner/cypress_runner.js:108456:5
    at timeslice (https://google.com/__cypress/runner/cypress_runner.js:102382:27)

Desired behavior
cy.origin shouldn't cause any errors.

Test code to reproduce
https://github.com/kiran-epic/CypressCucumber_Origin

Versions

Cypress version: 10.9.0
Preprocessor version: 13.0.2
Node version: 16.16.0

Checklist

[x] I've read the FAQ.
[x] I've read Instructions for logging issues.
[x] I'm not using<EMAIL_ADDRESS>(package name has changed and it is no longer the most recent version, see #689).

cy.origin shouldn't cause any errors.

While this might be true that it shouldn't, it doesn't appear to be related to preprocessing at all. Cypress' own issue tracker is more appropriate.

@badeball The issue only occurs when using the cucumber preprocessor, if I write the tests using mocha describe {} blocks, there is no such issue.

https://github.com/kiran-epic/Cypress_Vanilla

nvm. Cypress v10.10.0 fixes the issue!


proposal: go test -c should compile one test binary for all packages listed

Proposal Details
go test -c currently produces one test binary per package listed.  When running without -c, go test will run all tests for all packages listed.  I propose that go test -c mirror that behavior when compiling a test binary, and produce a single a.out that when executed does exactly the same thing as running go test directly without the -c flag.
The reason that I think this is a good idea is because this behavior would reduce the disparity between using the -c and not using it.  Concretely, this would make it easier to build and share test executables to run in a single command.  I have a concrete use case for this where we run integration tests in a container that's built on build machines.  Enabling this would reduce the image size transferred back and forth :)

This looks like an incompatible change in how the go command works.
It also looks infeasible as this would make the test executable built with multiple packages unlike that of one built with a single package, impacting things such as init, who gets the starting thread, which testmain is run, and more generally global resource setup/cleanup/error handling in a way which is likely to break user code.

This is not feasible in general. Two different packages can each define a test function with the same name, such as Example. How would the -test.run flag distinguish between those functions?
Contrast:

#60977


Fix typo

This appears to be a typo. While small, it may disrupt folks wanting to get started quickly with your project!

🤦♂


How to validate on Instances, not Class

Question
I know that validators are class methods. What if I wanted to validate on an instance? I've combed through the docs and examples and have not been able to find an answer.
Please complete:

OS: MacOS Mojave
Python version import sys; print(sys.version): 3.7.3
Pydantic version import pydantic; print(pydantic.VERSION): 0.32.1

class DateParams(BaseModel):
    begin_date: str
    end_date: str

    def __init__(self, args, max_years={}):
        super().__init__(**args)
        self.max_years = max_years

    def process_years(date, max_years):
        ...

    @validator("begin_date", always=True)
    def begin_date_validator(cls, begin_date):
        begin_date = validate_date_str(begin_date, "begin_date")
        process_years(begin_date, max_years)
        return begin_date

    @validator("end_date", always=True)
    def end_date_validator(cls, end_date):
        end_date = validate_date_str(end_date, "end_date")
        process_years(end_date, max_years)
        return end_date

Suppose I have a class such as above, and I wanted to instantiate multiple DateParams with different max_years, but the same process_years. How would I achieve this? This would be easily resolvable if I could call the validators on an instance instead of on the class.

@roykim98 Probably the easiest thing to do would be to add max_years as a field on the model (above the other two), and add another positional argument to the validators -- it will contain the values of the previously-parsed fields. Given you are trying to store it on the object anyway, maybe this is reasonable?
Another option would be to use pydantic.dataclasses.dataclass, which has support for dataclasses.InitVar, which would allow you to do validation in the __post_init_post_parse__ (though not in a validator).
Note: if you want to set additional properties which are not fields on the model instance, you'll need to set the Config to allow extra.

In general, because of how much pydantic handles transparently, if you want/need to substantially change the API for a model, it's probably worth thinking about if you could achieve the pattern with composition, rather than inheritance. Going "off-road" in subclasses of BaseModel like this; is likely to cause confusing and subtle (or not so subtle) errors. In this case, for example, it will be impossible for pydantic to parse any models using DateParams as a submodel due to the modification to the __init__ signature.

You want to do something like
from datetime import date
from typing import ClassVar

from pydantic import BaseModel, validator

class DateParams(BaseModel):
    max_years: ClassVar[int] = 123
    begin_date: date
    end_date: date

    @classmethod
    def process_years(cls, date):
        print(date, cls.max_years)

    @validator('begin_date', always=True)
    def begin_date_validator(cls, begin_date):
        cls.process_years(begin_date)
        return begin_date

    @validator('end_date', always=True)
    def end_date_validator(cls, end_date):
        cls.process_years(end_date)
        return end_date

DateParams(begin_date='2019-06-01', end_date='2019-06-02')

If you want to modify max_years you can:

inherit from DateParams and override max_years
remove ClassVar and make max_years a normal field you set at __init__(self, max_years=..., ...), then use another argument to the validators eg. values which will contain max_years.
or even, use create_model to dynamically create models with __base__=DateParams and max_years modified.

Is there a way to make an abstract attribute in Pydantic? Suppose I wanted to make max_years  as a field on the model, but have it be an abstract class property. Is this possible?


Increase size of map legend

Increase the size of the map legend so it accommodates the symbol styles being built for solution offerings.
@lindsayking - please review this issue and incorporate it in to next release of LWL.  Assign to dev team after you've reviewed ticket.  May want to also provide dev team a suggested height based on current symbol designs (min # of pixels).

@ScottOppmann
According to @HeatherEisan, the size of the new "small" eye drop/pin symbols are 28 pixels wide and 36 pixels high.  Considering this height and appropriate padding, I suggest legend height be set to 68 pixels.
Out of curiosity, have we ever considered making the legend height a configurable item?

Approach for legend should be the same as this issue
https://github.com/Esri/environmental-impact/issues/178

Use the same approach as https://github.com/Esri/environmental-impact/issues/178

@lindsayking @LindsayThomas
OK. We are following the same approach and shall deliver it in the next release.

LT- Verified on LG config


Python 3: define basestring, use bytes.decode()

@cclauss I realize this is an old PR but we would benefit greatly from it, would you mind rebasing this and re submitting please?, I think tests should pass now

Closing in favor of #705


Optimised Jetpack Dockerfile to reduce number of layers

There are 3 RUN commands in the Jetpack Dockerfile that each lead to the creation of one layer in the resulting image. This PR aims to reduce the number of layers created in the Jetpack image by combining the 3 RUN commands into 1 RUN command.

Can one of the admins verify this patch?

The order in which execution is triggered matters. Ansible should not be installed before epel-release, because it will not be found. I am closing this PR because of that.


V 0.09 - FC on honeycomb ctlr status

Still force closes for me.  Not sure what the problem is.  One thing I noticed is my tablet has a non-standard resolution.  Not sure if it makes a difference.

Don't think it is related to your resolution.  I knew the FC was there just
haven't had a chance to work the tablet much yet.  I think this is the
first case of something that works on the phone failing on the tablet.
It is also reproducible in the emulator so it is not your environment.
On Sat, Jan 28, 2012 at 8:21 PM, pcbroch <
<EMAIL_ADDRESS>
wrote:

Still force closes for me.  Not sure what the problem is.  One thing I
noticed is my tablet has a non-standard resolution.  Not sure if it makes a
difference.

Reply to this email directly or view it on GitHub:
https://github.com/AquaNotes/AquaNotesTest/issues/19#issuecomment-3705492

Patrick fixed this.


BackPressureObservable listener should be removed after failure

Description:
Outbound request and outbound response writability depends on the netty channel writablility. If the channel is active but not ready to write out the data(which could rarely happen), the request acquires a semaphore and waits. If the channel is closed or occurred with an exception, the request failure path should release the acquired semaphore. But when inspecting the code, it was identified that the error has only been notified to the application layer without releasing the semaphore.
Removing the listener from the BackPressureObservable after failure, will call onWritable on the listener which can potentially release the acquired semaphore
Steps to reproduce:
Not reproducible, only a possibility
Related Issues (optional):
Passthrough server hangs intermittently when IO exception occurs while writing outbound request. #34685

Outbound Request path is fixed via Remove backPressureObservable listener after failure #837


Added automatic CLA filtering option in Comm

Most of the applications check for the value of CLA byte of incoming APDUs and return an error status word when it is different from a constant.
This feature can help simplifying apps by removing the need to handle bad CLA errors, as there is not added value by the apps in dealing with this.

@kingofpayne you need to rebase your branch


Add the ability to specify global build args

Description
Using --build-arg is convenient for setting proxy settings for build but it isn't ideal in many scenario, most of all when using compose. To get our images to build behind corporate firewall, we have to add the arg section to all our compose file. Ex:
 args:
        - http_proxy=${HTTP_PROXY}
        - https_proxy=${HTTP_PROXY}
        - HTTP_PROXY=${HTTP_PROXY}
        - HTTPS_PROXY=${HTTP_PROXY}

This solves our own images but if we contribute on Dockefile from anyone else, we have to patch those files with these args to get them to build.
It would be nice if in addition to being able to specify command line build args, it was possible to specify global ones using DOCKER_BUILD_ environment variables. This would allow those of us unfortunate enough to be behind proxy to have our build arguments specific to our environment in env vars and not anywhere else. The DOCKER_BUILD_ vars could be merged with the cli --build-arg, with the cli options taking precedence.

/cc @sylus

if we can find the right syntax for this, it sounds good to me.
It might be nice to consider that some people may want to specify other docker build flags via env vars too - like --rm or -q so if we can either combine them into one or find a pattern that can be reused for others then that would be good.
e.g.
DOCKER_BUILD=-rm --build-arg foo=bar --quiet`

of course this can be tricky to get the parsing right but we have parsers in the builder we can reuse.

That would work for me as long as expansion works within so I could do something like:
DOCKER_BUILD=--build-arg http_proxy=$http_proxy`

we'd need to make sure the env var processing rules made sense, yea

Isn't this exactly where the multiple compose files / override files are implemented for? https://docs.docker.com/compose/extends/#/different-environments

The multiple compose file is for creating different containers for different environments. Our issues is that every Dockerfile we have to build, using container or otherwise, we have to pass --build-arg http_proxy=$http_proxy --build-arg https_proxy=$https_proxy. It's not exactly the same use case.

@LaurentGoderre AFAIK, it should be possible to use that to just override / append build-args. That way you can simply have a docker-compose.override.yml containing the build-args for your environment, without touching the regular docker-compose.yml.
Have you tried?

@thaJeztah yes it is possible but far than ideal because we'd have to create overrides for each docker compose file and each service within it. Not only that but we'd also have to create and maintain patches for all Makefile and scripts that invoke docker build to add these params.
I know our setup isn't ideal either but corporate proxy are pretty common and any help we can get to help us work efficiently within them would help us greatly.

You can just do "--build-arg http_proxy", without specifying a value, and docker-build will copy whatever setting it already has from it's parent environment.  This should simply things a bit.
The issue I am having with docker-compose, is that in my yml files, I had to do args: ["http_proxy", "https_proxy"] for each and every single build context.  It's acting like the internal default list of build-args that docker-build has it not being read when docker-compose is run.

hI like this. Global build arguments would also eliminate the necessity of running per-service docker-compose build calls when all of those services share the build-arg.   Currently, docker-compose requires a service to build when build-arg is passed.  That's not technically necessary if all services share the same build-args as mentioned above.
I might go a step further and introduce something like following syntax:
--build_arg SERVICE:KEY=VALUE

It would be nice if you could at least specify 2 build args, one for each service and it makes sense if the default behavior for build is to build all services.

Think about the option below to around this.
Environment variables:
# Proxy
export PROXY_HOST=$(ip route get 1 | awk '{print $NF;exit}')
export PROXY_PORT=3128

# HTTP Proxy
export http_proxy=http://$PROXY_HOST:$PROXY_PORT
export https_proxy=$http_proxy
export no_proxy=localhost,<IP_ADDRESS>

# Docker Build
export DOCKER_BUILD_OPTS="$DOCKER_BUILD_OPTS --build-arg http_proxy=$http_proxy --build-arg https_proxy=$https_proxy --build-arg no_proxy=$no_proxy"

Makefile:
SHELL := /bin/sh

DOCKER_BUILD_OPTS ?=

HBASE_VERSION := $(shell git describe --tags --abbrev=0 2> /dev/null)

DOCKER_REPO := rowupper
DOCKER_IMAGE := hbase
DOCKER_TAG := ${HBASE_VERSION}

.PHONY: docker/build docker/push

docker/build:
	docker build \
		${DOCKER_BUILD_OPTS} \
		--build-arg HBASE_VERSION=$(HBASE_VERSION) \
		-t $(DOCKER_REPO)/$(DOCKER_IMAGE):$(DOCKER_TAG) \
		-t $(DOCKER_REPO)/$(DOCKER_IMAGE):latest \
		.

docker/push:
	docker push $(DOCKER_REPO)/$(DOCKER_IMAGE):$(DOCKER_TAG)
	docker push $(DOCKER_REPO)/$(DOCKER_IMAGE):latest

Actually; looks like this is a duplicate of https://github.com/moby/moby/issues/36102, and for proxies, this was implemented;

https://github.com/docker/cli/pull/93 Allow Proxy Configuration in config.json

continuation of https://github.com/moby/moby/pull/30588

(related) https://github.com/moby/moby/pull/31584 Exclude “default” build-args from image history
(related topic); https://github.com/moby/moby/issues/30323 Improve UX around http-proxy for those in corporate environment

Docker 17.07 and up, you can set default proxy settings in the CLI configuration file (~/.docker/config.json) those settings will be applied both when starting a container (docker run) and during docker build (they will be automatically passed as --build-arg)
With that configuration in place, no changes would have to be made to the compose file, or build scripts (as the docker cli reads the configuration from its ~/.docker/config.json configuration file)
As to changes for the docker-compose, that would be best kept for the docker-compose issue tracker (https://github.com/docker/compose), but given that environment variables can already be substitutes in the docker-compose file I'm not sure if additional features should be added there (but; best left to the docker compose maintainers)
I'll close this issue, because I think the original request has been addressed.


logp: don't write to files by default if running in a container environment

What does this PR do?
The PR https://github.com/elastic/elastic-agent-libs/pull/208 introduced a bug that made  the -environment container flag stop writting to stderr on the default logger. This PR restores the old behavior as well as adding a test that observes that logs are properly written to stderr.
Why is it important?
Checklist

[x] My code follows the style guidelines of this project
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have added tests that prove my fix is effective or that my feature works

Related issues

Fixes https://github.com/elastic/beats/issues/41118

:green_heart: Build Succeeded

Buildkite Build
Commit: 0f7f948de3301187ae4c561f433b52c994f3c0f2

cc @mauri870

:green_heart: Build Succeeded

Buildkite Build
Commit: 3b10333be7bc6e45f358ed7dfde7c8d96be26671

History

:green_heart: Build #418 succeeded 0f7f948de3301187ae4c561f433b52c994f3c0f2

cc @mauri870

Could you also test the deb/systemd flow to make sure we fixed it in all cases?

Sure, I was able to build a deb package with PACKAGES=deb PLATFORMS=linux/amd64 mage package, I'll spin up a vm to test this case.

@belimawr From my testing with systemd, filebeat creates /var/log/filebeat/*.ndjson files and journalctl -u filebeat.service does contain any logs. The proper behavior would be for the logs to go to stderr in the systemd case as well and appear in the journalctl output, right?

:green_heart: Build Succeeded

Buildkite Build
Commit: 399ae3f5871d2c20821cec3e32d1d2155ec33480

History

:green_heart: Build #419 succeeded 3b10333be7bc6e45f358ed7dfde7c8d96be26671
:green_heart: Build #418 succeeded 0f7f948de3301187ae4c561f433b52c994f3c0f2

cc @mauri870

:hourglass_flowing_sand: Build in-progress, with failures

Buildkite Build
Commit: 3db5712782c71da75fe8045bac268bbc34c777ad

Failed CI Steps

:linux: Test Linux

History

:green_heart: Build #423 succeeded 399ae3f5871d2c20821cec3e32d1d2155ec33480
:green_heart: Build #419 succeeded 3b10333be7bc6e45f358ed7dfde7c8d96be26671
:green_heart: Build #418 succeeded 0f7f948de3301187ae4c561f433b52c994f3c0f2

cc @mauri870

:green_heart: Build Succeeded

Buildkite Build
Commit: 0d1574458bd89e71526e69a0e3c93830e9197f18

History

:broken_heart: Build #424 failed 3db5712782c71da75fe8045bac268bbc34c777ad
:green_heart: Build #423 succeeded 399ae3f5871d2c20821cec3e32d1d2155ec33480
:green_heart: Build #419 succeeded 3b10333be7bc6e45f358ed7dfde7c8d96be26671
:green_heart: Build #418 succeeded 0f7f948de3301187ae4c561f433b52c994f3c0f2

cc @mauri870

@belimawr From my testing with systemd, filebeat creates /var/log/filebeat/*.ndjson files and journalctl -u filebeat.service does not contain any logs. The proper behavior would be for the logs to go to stderr in the systemd case as well and appear in the journalctl output, right?

Yes, I believe this is the correct behaviour: when running under systemd, the logs go to stderr and can be seen using journalctl.
The best approach to be sure is to test an older version :sweat_smile:
I also saw your last comment, the behaviour looks correct.

I also saw your last comment, the behaviour looks correct.

Thanks, I did test with 8.14.3 and the behavior seems consistent with with filebeat main + this fix.


Issue #790 Update expiry contract with some value indirection

Enables to indicate that recovering a value in some cases may be
expensive, i.e. deserialization
Internal update of StoreEventSink contract to not have to do eager
deserialization when no listeners are registered.

I want the review to be about the API changes this introduces in addition to the technical aspect. I am still unsure if it should go in or not.
@lorban Might be interesting to get perf numbers with and without this

Well, in its current state, this is badly broken ... my bad. Will push an updated version soon - principle and ugliness can still be discussed ;-)

PR updated with a more correct handling of lazy value holders in off heap. This raises even more doubt for this PR as I had to explicitly request value deserialization in places because it no longer happens through expiry computation ... but the result really needs to be deserialized before being returned.
And in fact, while OnHeap deserialization happens on each invoke of the value, this is not relevant for OffHeap. So discussion to be continued on this topic ...

So as discussed in issue #790 we are going through with this. I have pushed an up to date version that should include all review comments.


[BUG?] - Latest commit cause Queue menu items and ComfyUI Manager menu to misalign

After installing the latest commit (which includes the new Label node), I noticed that various UI elements in both the Queue menu and in the ComfyUI Manager menu are misaligned:

Disabling your custom node suite reverts to the usual look.

The same happens to me.
It looks like this, without the extra Queue menu customizations.

Thanks, fixed.

All back to normal. Thank you @rgthree for the very quick fix.
But you should know that Context and Context Big nodes have restarted growing vertically, adding a lot of extra space at the bottom of the node. Not sure this is connected with their behaviour.


Feature request: better error reporting when mocha can't find tests (getting started)

The getting started tutorial on the home page looks pretty simple, but if you put the test in a different directory than "test" it's suddenly not very friendly:
/usr/local/lib/node_modules/mocha/lib/utils.js:628
throw new Error("cannot resolve path (or pattern) '" + path + "'");
^
Error: cannot resolve path (or pattern) 'test'
at Object.lookupFiles (/usr/local/lib/node_modules/mocha/lib/utils.js:628:15)
at /usr/local/lib/node_modules/mocha/bin/_mocha:326:30
at Array.forEach (native)
at Object. (/usr/local/lib/node_modules/mocha/bin/_mocha:325:6)
at Module._compile (module.js:413:34)
at Object.Module._extensions..js (module.js:422:10)
at Module.load (module.js:357:32)
at Function.Module._load (module.js:314:12)
at Function.Module.runMain (module.js:447:10)
at startup (node.js:142:18)
at node.js:939:3

Closing as duplicate of https://github.com/mochajs/mocha/issues/2194


webpage build GHA doesn't run on automated commits

This commit from the scheduled GHA didn't kick off the webpage building GHA.
https://github.com/ioos/ioos_metrics/commit/adc249a77174c89a2eb1e843304d350163185dc9
I had to run the webpage build manually:

https://github.com/ioos/ioos_metrics/actions/runs/5523809786

I'm befuddled as I thought the action was ran on any new commits to main with:
on:
  workflow_dispatch:
  push:
    branches:
      - main

see https://github.com/ioos/ioos_metrics/blob/main/.github/workflows/website_create_and_deploy.yml

@ocefpaf there was an automated commit to main https://github.com/ioos/ioos_metrics/commit/a4dcd2f19d65d96b2fc36b6d48a7f91685a9dd09
However, the Action to update the website didn't run https://github.com/ioos/ioos_metrics/actions
Why doesn't the push to main kick off the website_create_and_deploy workflow?
I feel like I'm missing something really simple here.

Could it be the paths? Maybe it will trigger only if those files/paths are touched?

I use paths in the collect metrics action, but not in the website create and deploy action:
https://github.com/ioos/ioos_metrics/blob/a4dcd2f19d65d96b2fc36b6d48a7f91685a9dd09/.github/workflows/website_create_and_deploy.yml#L6-L10
I wonder if it is because the automated push from the collect metrics action is done as Automated with some generic github noreply account?
https://github.com/ioos/ioos_metrics/blob/a4dcd2f19d65d96b2fc36b6d48a7f91685a9dd09/.github/workflows/metrics.yml#L48-L55
I suppose I could use workflow_run to trigger this action after the metrics gathering one? But, what happens when the webpage action should be ran without running the metrics action? https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows#workflow_run

@MathewBiddle I recall clicking on a bunch of permissions and digging into the settings to get this one to work properly. I don't have enough rights here to check but how is yout gh-pages config? Here is how mine looks:

looks like I have the same settings.

looks like I have the same settings.

I'll try to fork and debug it on my account. Will report soon...

I found this issue that may be related to what is happening here: https://github.com/orgs/community/discussions/27146


Feature/add company status validator

https://companieshouse.atlassian.net/browse/IDVA3-559

CI: Security warnings found!

CI: Security warnings found!


Include GFA assembly graphs in results

Fixes #46
I also wonder, for consistency's sake, if the ${sample}.scaffolds.fa and ${sample}.meta.scaffolds.fa files in results for spades and metaspades respectively should be renamed to match ${sample}.assembly.fa from unicycler?
PR checklist

[ ] This comment contains a description of changes (with reason)
[ ] If you've fixed a bug or added code that should be tested, add tests!
[ ] If necessary, also make a PR on the nf-core/viralrecon branch on the nf-core/test-datasets repo
[ ] Ensure the test suite passes (nextflow run . -profile test,docker).
[ ] Make sure your code lints (nf-core lint .).
[ ] Documentation in docs is updated
[ ] CHANGELOG.md is updated
[ ] README.md is updated

Learn more about contributing: CONTRIBUTING.md

Thanks @heuermh :) Please see minor comments above.

Fast-tracked this so I can add in the minimap2, seqwish and vg steps for the other assemblies ;)

Thank you, @drpatelh!


Add repr_latex for Jupyter notebooks

This allows better representation inside the browser:

Coverage decreased (-13.5%) to 64.872% when pulling 426215e82ab8ecbd91c02ea5b19ef32464c3efbd on alchemyst:master into 31e694441dbb101f7e601dce2b8dfa3e97ec2a1a on python-control:master.

Coverage decreased (-13.5%) to 64.872% when pulling 426215e82ab8ecbd91c02ea5b19ef32464c3efbd on alchemyst:master into 31e694441dbb101f7e601dce2b8dfa3e97ec2a1a on python-control:master.

Change looks fine, but getting a Travis CI error.
It would be nice to put in this type of functionality for the other LTI subtypes (StateSpace, FRD, etc).  Any chance you have the time and inclination to do that as well?

I'd be happy to take a run at it, but perhaps we could start by opening issues for the others? I'd specifically like to know what format you'd prefer for the state space.

@alchemyst Can you merge changes from latest master to get Travis CI working again (see PR #280 for more info).  Thanks.

@murrayrm ✅

Nice, looks good.
Would it be worthwhile to build the outstr as a list, and at the end return the string with
''.join(outstr)
I expect that to be faster.

@repagh Done.
My initial implementation was a copy-paste of the current __str__. Perhaps we should add an issue for someone to make the same changes there?

@murrayrm I think this looks OK to merge


VSL-245: add toast component

adds @chakra-ui/react and its dependencies
create useToastHook that wraps around chakra's useToast to render a custom "CAST" style toast design

Usage:
const { popToast } = useToast();
// ....
popToast("My toast message", {
  footerText: "My toast link", // optional
  footerLink: "/my-path", // optional ,only used with footerText
});

@mannynotfound Would it be possible to merged this with release-v1.6.0? so we can start incorporating chakra?

@germanurrus sure! opened here https://github.com/DapperCollectives/CAST/pull/659


Fix JavaDocs and ALL Checkstyle rules

I think right now your Eclipse should be fine with BDDMockito :smile:

Merged as 00b221bb8026999d93d756f694bb6a031ab6422e


testing file input size not equal to preds output size

Hi @andrewkern,
I am using an fvec of 500 sims (500 lines + header) for testing classification with a previously constructed model. When I run  'predict' with the option --simData the resulting file has fewer than 500 lines. E.g., 323. I also checked this for the empirical fvecs and the input and output files are also not the same size. Am I missing something here? Like a cutoff option for reporting?
thanks,
@stsmall
Edit: The output from predict prints '500 predictions complete', but only 322 are in the output file
Edit2: The length of preds and predictions (in the diploSHIC.py) are both 500.
Edit3: When I drop into the code (ipdb) right after preds to check the length, then 'c' to continue ... the resulting file is 500 lines! BUT once I remove the breakpoint and run it back to <500 ... lol, I think I am losing my mind

It seems the culprit is on Ln 319, there is not an () on outputFile.close. If I change it to outputFile.close() ... it works as expected.

well that's a crappy bug. @stsmall do you want to submit a little PR so that you can get credit for this bug fix?

No thanks. Glad to have helped out.


Don't hardcode the version in the "Get Started" button

See here: https://github.com/projectcalico/calico/pull/1193#issuecomment-336597491

Fixed by #1208


The platform "npm-package-arg" does not appear to be a valid cordova platform.

Hi everyone 👋,
I'm facing an issue using<EMAIL_ADDRESS>
I don't reproduce the issue locally (using Bitrise CLI) neither using the previous version of the step (0.9.2).
Any ideas how to fix it?
Thanks

Please run cordova platform rm android and cordova platform add android on your machine, and push the changes to config.xml and package.json.


build: osx: Fix incomplete framework packaging for codesigning

Starting with 10.9, Framework versions must be signed individually, rather
than as a single bundle version, in order to be properly codesigned. This
change ensures that the proper plist files and symlinks are present prior to
packaging.

Merging untested, as it seems to be universal enough for us. We don't have changes on that script anyway.


⚠ Bofrost.lu has degraded performance

In 77b0558, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1430 ms

Resolved: Bofrost.lu performance has improved in 770873d after 9 minutes.


removed some bugs

Related Issuse

Info about Issue or bug

Closes: #324
Describe the changes you've made

Footer has been added to homepage.

2)Signup page earlier looked like this.

And now looks like this

Our reach cards and vision cards in the homepage are now responsive throughout.

@codewithvk  @purnima143 please review this pr.

@purnima143 please review this.


Make postprocessing optional - disabled by default

Currently one of the biggest reasons why postprocessing is done is to ensure that the correct type of object is returned after the lattice's execution. There are several issues with doing that postprocessing, but they were deemed necessary at the time because of the value it provides. Some of these issues include:

In whatever executor the postprocessing will be done, it will need to have all the dependencies of all the electrons in the lattice. This is because the entire function will be run and the calls to those electrons will be replaced by their outputs.

If the outputs of the electrons are large enough, which happens to be the case in some recently encountered workflows, that will lead to a failure in postprocessing since all of those outputs will be stored in memory just for that purpose (to be put in place of electron calls in the workflow function).

Now, after some detailed discussions we realized that it might be time to get rid of postprocessing as the compromise isn't worth the benefit. So, it was decided that in order to determine the output of the lattice we can analyze it during build graph time.
So, in build_graph, in the case where the output isn't some form of electron:
# we are doing something like this
workflow_function(*args, **kwargs)

# instead we can do something like this
return_value = workflow_function(*args, **kwargs)

# then analyze it and add that info to the transport graph
# later on based on that info and after the electron executions,
# the result of the workflow can be created and returned

Since there still might be some contrived cases where performing postprocessing will be necessary, such as
@ct.lattice
def workflow(x):
    res = task(x)

    if isinstance(res, Electron):
        return 0
    else:
        return res

which is why in this issue the proposal is to add an argument to the lattice decorator postprocess whose default value is False to still allow postprocessing in the traditional sense.

Stages of processing the return value:

Preprocess Return Expression
Load in Result
Rebuild and Deserialize on Client

Implementation details for each stage:

Preprocess Return Expression

preprocess_return function

Right after getting the return value in build_graph,return_value = workflow_function(*args, **kwargs)

the return_value variable can be analyzed for its structure
This function will recursively go through the return_value's expression by evaluating it and storing the node_ids of all the electrons encountered
Whenever an Electron will be encountered, this should also replace it with a string :-{node_id}-:

return_info: Dict - Lattice attribute

Then the return_value and the electron_ids will be stored in this return_info Lattice attribute
return_value will be made into a TransportableObject when storing it in this dictionary
The json functions (serialize and deserialize) and encode_metadata functions will also need to be updated to account for this attribute's addition

Load in Result

After execution of all tasks has completed, and result object is being constructed on the dispatcher for returning, ensure that all the electron_ids's outputs are also loaded into the result object
The Lattice of that result object should also contain the result_info attribute

Rebuild and Deserialize on Client

Inside the property result of the Result object, the following things should be done

If _result is not None, then return _result
Otherwise, start evaluating the return_value expression and replace all the :-{node_id}-: strings with values of respective electron outputs
Once that's done, store the final result in _result and return the _result


⚠ ClamAV has degraded performance

In acfed38, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 667 ms

Resolved: ClamAV performance has improved in b20e004 after 5 minutes.


Test blacklist integrity duplicates

Run a check against duplicates entries as well while we are already scanning the blacklists.
Incidentally, also refactor to put the function inside a test_blacklist_integrity() function so it works like the other test/*.py scripts.

Sorry, the Git test commits had bleeded in here -- will supersede with another PR.

Force pushed the correct history, should be good to go now.  Sorry for the mess.


Changed request.path to request.path_info in middleware

Fix for issue #47

Doing some testing. Soon I'll merge and release a new version.


Suggestion: optional material design style

Much like the dark theme, could we have material design style on by default but optionally turned off? Personally I prefer dark theme with it off. Thanks

Unfortunately I'm probably going to keep Material on at all times. It's not that bad with the dark UI.


CADL+DPG support of basic types of cadl-azure-core

CADL provides a library of type part of "cadl-azure-core". This is an example.
When people are using "cadl-azure-core", it automatically creates a model called Azure.Core.Operations.Error which is always the same everywhere. This information should be used to link to an actual SDK Azure.Core class to avoid duplication.
This issue should fill two purposes:

Make sure Azure.Core has what it needs to represent Azure.Core.Operations.Error
Plug the codegen to use Azure.Core and not generated types when those classes are recognized.

This is not AugustMVP scoped.
Example of Swagger generated from those types for clarity:
    "Azure.Core.Operations.Error": {
      "type": "object",
      "properties": {
        "code": {
          "type": "string",
          "description": "One of a server-defined set of error codes."
        },
        "message": {
          "type": "string",
          "description": "A human-readable representation of the error."
        },
        "target": {
          "type": "string",
          "description": "The target of the error."
        },
        "details": {
          "$ref": "#/definitions/Azure.Core.Operations.Error",
          "description": "An array of details about specific errors that led to this reported error."
        },
        "innererror": {
          "$ref": "#/definitions/Azure.Core.Operations.InnerError",
          "description": "An object containing more specific information than the current object about the error."
        }
      },
      "description": "The error object.",
      "required": [
        "code",
        "message",
        "details"
      ]
    },
    "Azure.Core.Operations.ErrorResponse": {
      "type": "object",
      "properties": {
        "error": {
          "$ref": "#/definitions/Azure.Core.Operations.Error",
          "description": "The error object."
        }
      },
      "description": "A response containing error details.",
      "required": [
        "error"
      ]
    },
    "Azure.Core.Operations.InnerError": {
      "type": "object",
      "properties": {
        "code": {
          "type": "string",
          "description": "One of a server-defined set of error codes."
        },
        "innererror": {
          "$ref": "#/definitions/Azure.Core.Operations.InnerError",
          "description": "Inner error."
        }
      },
      "description": "An object containing more specific information about the error. As per Microsoft One API guidelines - https://github.com/Microsoft/api-guidelines/blob/vNext/Guidelines.md#7102-error-condition-responses.",
      "required": [
        "code"
      ]
    },

@srnagar
Do we need to mirror Page in azure-core?
Currently codegen will generate e.g. PageFoo, but they are not really used by user. We can either use a generic Page in azure-core, or try to move these PageFoo to implementation namespace.


Fix jupyter component name

The component is not jupyterhub, just jupyter.

This change is

/assign

/lgtm
/approve

/ok-to-test


No redirect with Foursquare

Hello !
I'm using a button to log-in with Foursquare on my IOS app built with Ionic, here is my code
$cordovaOauth.foursquare("CLIENT_ID", ["email"]).then(function(result) {
console.log("Response Object -> " + JSON.stringify(result));
}, function(error) {
console.log("Error -> " + error);
});
The problem is that the login window appears but when I enter my username and password nothing happens: I'm stuck on this webview.
Thanks !

What do your error logs say?

The problem is that I launch my app on Ionic View so I can see the error logs. But the problem isn't coming from Foursquare because my app redirect URL are correctly set.

The Ionic View has problems with the InAppBrowser plugin that this library depends on.  I recommend you build and install directly to your device or simulator.
Let me know how that goes for you.
Regards,


How to use django-upgrade in the Pipeline?

Python Version
3.10
Django Version
4.1.1
Package Version
1.10.0
Description
Hi there!
I installed your great package - thx for the update on DjangoCon! - and it works great with pre-commit. Additionally, I want to ensure via the pipeline that nobody smuggles in some deprecated code... but the best way I found was using pre-commit inside the pipeline step which feels a little off. If I run it directly, the tool will rewrite the files but not return error code 1 in case it did something.
Solution (on python-slim image):
    - apt-get update && apt-get install --no-install-recommends -y git
    - pip install pre-commit
    - pre-commit install -t pre-push -t pre-commit --install-hooks
    - pre-commit run --all-files --hook-stage push django-upgrade

Not working solution (on python-slim image):
    - apt-get update && apt-get install --no-install-recommends -y git
    - pip install django-upgrade
    - git ls-files -- '*.py' | xargs django-upgrade --target-version 4.1

Thx!

but the best way I found was using pre-commit inside the pipeline step which feels a little off.

pre-commit recommends running pre-commit run --all-files in CI - see docs. The author even created a CI service to do that, and more.
This is the way I recommend.
But yes, the tool should exit with code 1 if it rewrites any files.

Just tested and django-upgrade does exit 1 when it rewrites files. And xargs will exit if any invocation fails. I think you maybe missed something in your test. Closing for now but if you have more info.

Ok, thx for the super quick reply!


Add check mode and exit codes

Seems like a reasonable approach to me!

Alright, undrafted it then with a couple of minor changes.

Coverage increased (+0.02%) to 99.682% when pulling e9aa8dc47786d882b6ad5c8ee79b63d2bb97b3cf on kapsh:check_mode into 2a352f1b0379693ffb870e5f1b9213d3b8b06dc7 on myint:master.

Coverage increased (+0.02%) to 99.682% when pulling e9aa8dc47786d882b6ad5c8ee79b63d2bb97b3cf on kapsh:check_mode into 2a352f1b0379693ffb870e5f1b9213d3b8b06dc7 on myint:master.

Coverage increased (+0.02%) to 99.682% when pulling e9aa8dc47786d882b6ad5c8ee79b63d2bb97b3cf on kapsh:check_mode into 2a352f1b0379693ffb870e5f1b9213d3b8b06dc7 on myint:master.

Coverage increased (+0.02%) to 99.682% when pulling e9aa8dc47786d882b6ad5c8ee79b63d2bb97b3cf on kapsh:check_mode into 2a352f1b0379693ffb870e5f1b9213d3b8b06dc7 on myint:master.

Coverage increased (+0.02%) to 99.682% when pulling e9aa8dc47786d882b6ad5c8ee79b63d2bb97b3cf on kapsh:check_mode into 2a352f1b0379693ffb870e5f1b9213d3b8b06dc7 on myint:master.

Coverage increased (+0.02%) to 99.682% when pulling e9aa8dc47786d882b6ad5c8ee79b63d2bb97b3cf on kapsh:check_mode into 2a352f1b0379693ffb870e5f1b9213d3b8b06dc7 on myint:master.

Coverage increased (+0.02%) to 99.682% when pulling e9aa8dc47786d882b6ad5c8ee79b63d2bb97b3cf on kapsh:check_mode into 2a352f1b0379693ffb870e5f1b9213d3b8b06dc7 on myint:master.

Coverage increased (+0.02%) to 99.682% when pulling e9aa8dc47786d882b6ad5c8ee79b63d2bb97b3cf on kapsh:check_mode into 2a352f1b0379693ffb870e5f1b9213d3b8b06dc7 on myint:master.


Linux version asks to read /home//.local/share/yuzu/cahe/game_list/ but that directory does not exist on my install. I'm using Yuzu EA.

Describe the bug
Linux version asks to read /home//.local/share/yuzu/cahe/game_list/ but that directory does not exist on my install. I'm using Yuzu EA.
To Reproduce
Steps to reproduce the behavior:
Open app, error displays
Expected behavior
A list of games and available mods.
Screenshots/Videos
See attached.

OS: Nobara 37
Version 1.0.1
Emulator used Yuza
Emulator version EA3659

We just delivered a new release were this error should be fixed. :)
If CI is done with building you can just download the new version. 🥇
Should it still not be working, please come back and tell us.
Have fun! Thanks for using ModMopet <3


Flesh out unit test coverage

Overview
Let's get 90 percent plus coverage.

Work for this issue will begin begin on branch work-liquid-labs/react-window-context/14.


Run docker build on all PR builds

Similar to what builder does in its .travis.yml file, workflow should run make ... docker-build to ensure that the Dockerfile is correct

We run docker build to build the image pre-e2e runs, so this has been resolved.


[SPARK-13869][SQL] Remove redundant conditions while combining filters

What changes were proposed in this pull request?
[I'll link it to the JIRA once ASF JIRA is back online]
This PR modifies the existing CombineFilters rule to remove redundant conditions while combining individual filter predicates. For instance, queries of the form table.where('a === 1 && 'b === 1).where('a === 1 && 'c === 1) will now be optimized to  table.where('a === 1 && 'b === 1 && 'c === 1) (instead of  table.where('a === 1 && 'a === 1 && 'b === 1 && 'c === 1))
How was this patch tested?
Unit test in FilterPushdownSuite

cc @yhuai

Test build #52973 has started for PR 11670 at commit e946c1e.

Test build #52973 has finished for PR 11670 at commit e946c1e.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/52973/
Test FAILed.

Test build #53092 has started for PR 11670 at commit f9aba06.

Test build #53092 has finished for PR 11670 at commit f9aba06.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/53092/
Test PASSed.

 Are there other rules that are generating things like this?

https://github.com/apache/spark/pull/11665 could introduce redundant conditions.

Can you be more specific? When does this generate a redundant one? Let's make sure we don't continuously generate them and collapse them.

@sameeragarwal I plan to submit a PR for avoiding pushing redundant predicates through the operators, since it is blocking another PR: https://github.com/apache/spark/pull/11714. Are you doing this?

I actually found this issue while playing around with some tests. @gatorsmile can you give an example for a case where we generate redundant filters? The code does seem to check the constraints of its children (which are derived from their condition) before generating additional filters.

I thought you are doing this PR for avoiding to push down the redundant inferred/isnotnull conditions. It sounds like my understanding is wrong. As shown in the https://github.com/apache/spark/pull/11714, the test case failure is caused by this. That is what I plan to fix.

oh I see, a union --  that was a tricky one! The issue with union is that its constraints are an "intersection" of the constraints of its individual children (which means that our filter inference might push redundant filters to one of more of its child nodes). To fix this, we should make sure that we check the constraints of the children before pushing filters down. Should I make a fix?

I think we need a more general fix for all the predicate push down. I will submit a PR for a general issue instead of fixing Union only.

yes, I agree.


Feature request: custom style prompt

The included styles in this node are pretty good, but there're actually endless styles, it's impossible to include all, and if you include more the list will become too long to use easily. I propose to add a custom style prompt input, so that user can use an artist style, such as "breathtaking {prompt} by Anna Dittmann," weights can also be easily added by user. This should work as long as the simple format is followed, i.e., the style contains a {prompt} placeholder, which is simple to validate. When there're values in both the selected style and custom style, the custom one should take precedence. Please consider adding this feature., which will make this node the most powerful prompt styler.

It's been requested before in some form or another. See #18 #14. It only loads files named .json so splitting them into different files and just renaming them will prevent them from being loaded. Not the most elegant solution but it works.
I probably won't put the effort into doing something complex out of something that is simple, sorry. I think it would be better to build a frontend for ComfyUI that handles this instead like StableSwarmUI.

@twri Thanks for your excellent work! What I proposed is not multiselect, but a new input field that takes a plain string, using the same template as other styles you have in the JSON files, such as "breathtaking {prompt} by Anna Dittmann," Although it's up to user to enter the style text, you can do a simple validation to make sure a {prompt} placeholder to be present so that the text can be used as a style by your node, This should be a simple addition, but makes your node extendable with endless styles.


Release the evaluation code.

About the evaluation code:
Our reproduced version evaluates scores worse than the reported ones.
Hope to see the released version, which will help us improve our performance.
Thanks for your notification.

Please see this link.


can I use this tool to annotate my dataset like coco-style format ?

can I use this tool to annotate my dataset like coco-style format ?
I want to make a coco-style datasets for instance segmentation model training.
can I use this tool?
eh, how can I get a tool that can output coco-style instance segmentation annotations?
many thanks.

Yeah Please reply
Thanks


All functional tests builds with openj9 fail

The error:
https://github.com/AdoptOpenJDK/run-aqa/runs/1566377410?check_suite_focus=true
 [javac] error: error reading /home/runner/work/run-aqa/run-aqa/openjdk-tests/TKG/lib/org.eclipse.osgi_3.16.100.v20200904-1304.jar; error in opening zip file
    [javac] 1 error

     [exec] downloading  https://mirror.umd.edu/eclipse/equinox/drops/S-4.18M1a-202010120320/org.eclipse.osgi_3.16.100.v20200904-1304.jar
     [exec] --> file downloaded to /home/runner/work/runaqaTest/runaqaTest/openjdk-tests/TKG/../TKG/lib/org.eclipse.osgi_3.16.100.v20200904-1304.jar
     [exec] Expected sha is: e0c1c2fa5e5f520d2347f9e7a7d2873e3b96bab3,
     [exec] Actual sha is  : 55df4256e88dbe8795fea9f6ac50b2f8e0215eb1.
     [exec] ERROR: sha checksum error.

@llxia @LongyuZhang idea?

It looks like the mirror site cannot be found:  https://mirror.umd.edu/eclipse/equinox/drops/S-4.18M1a-202010120320/org.eclipse.osgi_3.16.100.v20200904-1304.jar

@sophia-guo It may be better to use Jenkins job to pre-download artifacts. Otherwise, run-aqa will depend on each 3rd party jar downloading.

Fixed by https://github.com/AdoptOpenJDK/TKG/pull/134. Close it.


Skipping deploy and site steps for google-cloud-dep-verification

Verified by running utilities/stage_release.sh

LGTM

Merging since this has been verified as part of a release


Native rails caching

My site's footer is static except for the asset links to e.g. social media icons. AFAIK, I can't use Rails caching for the entire footer because the asset fingerprints could change on the next reboot. I don't believe the Rails cache API has an option for that expiration type.

An approach you could use for native rails caching is to include something like the following into the cache-key:

when server was started
when the deploy happened
the commit-hash
the version number (if available)

Those are good ideas. I'd also want to configure a second Rails cache, a memory store. And then I'd want to configure it (if possible) to not impose a limit of the RAM it can use.
I'm not sure if that extra setup outweighs using this gem.


Flashing Error! Please re-run this script...

I am trying to flash firmware on raspbee with latest stable docker image following the guide. In issue solution seems to be installing wiringpi-latest.deb. How do I do that in docker? Thanks.
`docker run -it --rm --entrypoint "/firmware-update.sh" --privileged --cap-add=ALL -v /dev:/dev -v /lib/modules:/lib/modules -v /sys:/sys marthoc/deconz:stable
marthoc/deconz Firmware Flashing Script
Version: 0.6
Listing attached devices...
GCFFlasher V3_17 (c) dresden elektronik ingenieurtechnik gmbh
Path             | Vendor | Product | Serial     | Type
-----------------+--------+---------+------------+-------
/dev/ttyAMA0     | 0x0000 | 0x0000  |            | RaspBee
Enter the full device path, or press Enter now to exit.
Device Path : /dev/ttyAMA0

Firmware available for flashing:
deCONZ_ConBeeII_0x26660700.bin.GCF
deCONZ_ConBeeII_0x26680700.bin.GCF
deCONZ_RaspBeeII_0x26690700.bin.GCF
deCONZ_Rpi_0x26350500.bin.GCF
deCONZ_Rpi_0x26390500.bin.GCF
Enter the firmware file name from above, including extension.
Alternatively, you may enter the name of a firmware file to download
from http://deconz.dresden-elektronik.de/deconz-firmware/
or press Enter now to exit.
File Name : deCONZ_Rpi_0x26390500.bin.GCF

Device: /dev/ttyAMA0
Firmware File: deCONZ_Rpi_0x26390500.bin.GCF
Are the above device and firmware values correct?
Enter Y to proceed, any other entry to exit: y
Flashing...
GCFFlasher V3_17 (c) dresden elektronik ingenieurtechnik gmbh
Reboot device /dev/ttyAMA0 (RaspBee)
deCONZ firmware version 26330500
RaspBee Bootloader premium
Vers. 1.02
uild 2013/08/01
(4456 ms)
uild 2013/08/01
STARTING (4693 ms)
uild 2013/08/01
STARTING APP
(4695 ms)
uild 2013/08/01
STARTING APP
� (4751 ms)
uild 2013/08/01
STARTING APP
� (4755 ms)
uild 2013/08/01
STARTING APP
� (5266 ms)
uild 2013/08/01
STARTING APP
� (5267 ms)
could not sync with bootloader
Flashing Error! Please re-run this script...`

I suggest using a native OS instead of Docker/VM. Works way better :)

@danielandross are you still having this issue? You could just try some more runs.
There are options to the flasher that could initiate more trials in a single run. Actually there is an open pull request #376 wich addresses these options.

@Jo-Be-Co yes, I do. I tried it 5 times in a row just now:
GCFFlasher V3_17 (c) dresden elektronik ingenieurtechnik gmbh
Reboot device /dev/ttyAMA0 (RaspBee)
deCONZ firmware version 26330500
failed reset 19585
action: reset device RaspBee
wiringPi 2.52 initialized
Flashing Error! Please re-run this script...


New Filter

I'd like to see a 'Min vCPUs Count' please.
(Feature Request)

@ronpzenoss I guess it'd be useful for someone taking this up if you could point to the source AWS URIs to find the required 'Min vCPUs Count'.

@powdahound think this can be closed
https://github.com/powdahound/ec2instances.info/blob/5281faf2a9dfec2bff233ae375b6872f90e8f756/in/index.html.mako#L108

I'm not sure @ronpzenoss was asking for a filter, though I'm not sure what the request was actually for. Please reopen with more details if this is still wanted.


Azure SQL DB Output is not writing with INTO statement.

Hi Team, I am trying to

Get the data from Event Hub (Stream Analytics Input)
Stream Analytics query by selecting specific columns
Write the result back into Azure SQL DB with INTO statement.

But the data is not getting loaded into Azure SQL DB table which already exists. I am not able to debug on this. Tried with all possibilities as per the SQL query reference document.
SELECT name
FROM [src]
[tgt]
Any help would be much appreciated.

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

ID: 310af5df-d9b5-1508-3b47-3c4b37cf1cea
Version Independent ID: 15b93b2b-b6dc-c4a2-533e-f5b80950c237
Content: INTO (Azure Stream Analytics) - Stream Analytics Query
Content Source: stream-analytics-docs/into-azure-stream-analytics.md
Service: stream-analytics
GitHub Login: @mamccrea
Microsoft Alias: mamccrea

Hi @muruganbalan - I apologize for the delayed response.
Everything you mentioned should be supported. Have you reviewed Azure Stream Analytics output to Azure SQL Database?

@muruganbalan it looks like Mary has provided a thoughtful page that should cover your question.
Please let us know if you need anything else. I'll close the thread assuming its resolved, but happy to continue if you need further clarification. Thanks~ Jason


Fixes an issue with the node.image.pullSecrets property

This is related to https://github.com/CrowdStrike/falcon-helm/issues/92
The property, as defined, expects an object-type value. However, the Pod spec expects an array-type value for the "imagePullSecrets" property. Source: https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/#create-a-pod-that-uses-your-secret
In the current state, if we pass an object to node.image.pullSecrets, we pass schema validation but receive an error from Kubernetes:
Error: unable to build kubernetes objects from release manifest: error validating "": error validating data: ValidationError(DaemonSet.spec.template.spec.imagePullSecrets): invalid type for io.k8s.api.core.v1.PodSpec.imagePullSecrets: got "map", expected "array"

Conversely, if we pass an array, we fail schema validation:
coalesce.go:199: warning: cannot overwrite table with non table for pullSecrets (map[])
Error: values don't meet the specifications of the schema(s) in the following chart(s):
falcon-sensor:
- node.image.pullSecrets: Invalid type. Expected: object, given: array

Therefore it is impossible to deploy a private image in versions 1.4.1+ of the chart.

I just ran into the same thing and this solves the issue for me as well. Thanks a lot for the timely fix :)

To whoever has been approving all the GitHub action pipelines, I apologize for the collection of errors!

To whoever has been approving all the GitHub action pipelines, I apologize for the collection of errors!

No worries... That's one of the reasons for CI/CD in the first place!

thanks for your contribution!


Dense Dose-Fluence Matrix Calculation

Added storing of dose-fluence matrices in dense (i.e. not sparse) matrices.
To create new dose-fluence matrices, dose_fluence_matrix now needs takes the type as the first argument:
D = dose_fluence_matrix(Matrix, ...)
D = dose_fluence_matrix(SparseMatrixCSC, ...)

The existing in-place method, dose_fluence_matrix!, will specialise depending on matrix type.
Minor Changes

Added calibrate! to export list
Increased default maxradius for dose-fluence matrix computations to 100 mm
Added test for kernel_size

Codecov Report

Merging #48 (043213c) into main (1258df6) will decrease coverage by 0.18%.
The diff coverage is 0.00%.

:exclamation: Current head 043213c differs from pull request most recent head 8daeb84. Consider uploading reports for the commit 8daeb84 to get more accurate results

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@            Coverage Diff             @@
##             main      #48      +/-   ##
==========================================
- Coverage   18.80%   18.63%   -0.18%
==========================================
  Files          22       22
  Lines        1154     1170      +16
==========================================
+ Hits          217      218       +1
- Misses        937      952      +15

Impacted Files
Coverage Δ

...oseCalculationAlgorithms/FinitePencilBeamKernel.jl
0.00% <ø> (ø)

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

src/DoseFluenceMatrix.jl
1.21% <0.00%> (+1.21%)
:arrow_up:


No stripping occurs when function is called within console.log

Using the configuration
{test: /.js$/, loader: 'strip-loader?strip[]=console.log'}
For the below code snippet in the file, leads to no stripping
console.log(JSON.stringify(someObject));

Error
The console.log statement is not stipped off

This is biting me right now as well as I call the Immutable.js .toJS() on objects in quite a few of my log statements.


Fix iso_staggered rendering

fixed project_iso_staggered in helpers.rs
I am not 100% sure if this is the correct fix

Please check if this change is fixing it the correct way. It is working on my side.

@Affinator Oh, good catch! I'll check this out, and make it a 100% correct solution in case it isn't already.

@Affinator can you check out the hex-neighbours branch now, to confirm that the problem is fixed? Thanks for your PR! It was a helpful hint in figuring out where the error laid.

Still broken.
Not there is a gap between the chunks...

Still broken.
Now there is a gap between the chunks...

Weird, I thought I fixed precisely this issue....
Can I have a link to the example file that produces this?

Yeah, I am not able to reproduce this issue. I just tried out a quadrant size of 200, and am not seeing the gaps (in the iso diamond example)....

I just did a fresh git clone and checked out this branch and only edited the quadrant size of iso_staggered.rs to 80.

me problem.
Edit2: Iso-diamond is working as intended (even at large quadrant sizes).

Thank you! I was able to reproduce this, and I fixed the issue! Try it out now :D


v2rayn: init at 7.3.1

v2rayn: A GUI client for Windows and Linux, support Xray core and sing-box-core and others. https://github.com/2dust/v2rayN
Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

@aucub hello, seems the package has issues with right clicking (i can't select a server), thabks.


Does this crate have the ability to print pdf in windows?

On macos it prints well, however on windows, the file is printed in text mode and not in PDF.

You might be interested in this thread- shows an example of PDF printing on Windows: https://github.com/talesluna/rust-printers/issues/14
A future modification to this library might be to bundle Sumatra as alfianlensundev/tauri-plugin-printer currently does.


Decide whether or not to include ES6-style imports in package READMEs

This is a tracking issue.
We've been discussing whether or not to include ES module-style imports as alternatives in our READMEs, since require (which we landed on in all of the JavaScript samples) may not be friendly for bundlers.
CC @xirzec, since this could be part of the bundling docs.

require works fine in the bundlers I tested, but ultimately I would like to move away from it in favor of ES6.
The only hangup I have is node still views ES6 as experimental, right? https://nodejs.org/api/esm.html

Support is experimental and gated behind the --experimental-modules flag, and then it's only applied for .mjs files... The conventional solution to this problem was to use a transpiler like babel (or just write TypeScript). Using ESMs in JavaScript without a transpiler seems like it's still a can of worms.

cc @XiaoningLiu as he had the initial concerns from https://github.com/Azure/azure-sdk-for-js/pull/5936#discussion_r340419968

I'm closing this. (CC @xirzec, @XiaoningLiu, @ramya-rao-a).
Node 14 and up allow for the use of ESM syntax (import) without a flag. Node 12 only allows it with the --experimental-modules flag. Even with Node 14, the "type" field in package.json must be specified to be "module" (you can read all the convloluted rules on the Node docs). For better or worse, CJS is still the standard module system in Node.
For these reasons, in dev-tool, we've standardized around ES2020 x CommonJS (meaning ES2020 syntax/runtime features are allowed, but CommonJS modules should be preferred over ESM). It makes sense to me that the README sample standard should be the same. We can probably reconsider this after Node 12 reaches EOL.
If anyone on this issue feels strongly that we should reconsider this choice, please create a new issue in dev-tool about changing the JS sample code standard.
Thank you all!


[Bug]: ModuleNotFoundError: No module named 'llama_index.evaluation'

Bug Description
Evaluation module not found in llama index for usage.
Version
llama_index-0.11.3
Steps to Reproduce
Import the below line in a file
from llama_index.evaluation import DatasetGenerator
Relevant Logs/Tracbacks
from llama_index.evaluation import DatasetGenerator
ModuleNotFoundError: No module named 'llama_index.evaluation'

Did you run pip install llama-index-evaluation ?

Dosu is right @gowrijsuria -- that import is old and invalid

Yes , I tried pip install llama-index-evaluation. However, that did not work. The import statement suggestion by Dosu worked.
Thank you!