Framebuffer and TCC compiler

Hello First of all, I'd like to thank for this Sendna update
I noticed that the TCC compiler was no longer available in this version, unfortunately.
is there a reason for this? and would it be possible to make it available again in the next version because this one we could compile from C and thus create our own program and flesh out what is already available.
secondly, I also noticed that there was no “/dev/fb0” or “/dev/framebuffer” file. I find this rather odd and it's a shame not to have access to it the framebuffer would allow us to have greater management of the graphics environment, which could be useful for managing specific pixels on the terminal and thus creating graphics libraries.
what is a framebuffer ? -> https://fr.wikipedia.org/wiki/Framebuffer_Linux
what can we do with ? -> https://www.youtube.com/watch?v=x1oXByIJcHU
I don't claim to have the knowledge to do it myself or even to understand exactly how it works, but if it could be added I think it would be a relevant addition.

Not sure why I didn't see this issue before, notifications are broken

TCC was removed because it was hard to use without libc headers, you can still compile C programs by using a riscv64-linux-musl toolchain on a host system, and then copying your programs over to the VM with the file import/export card.  I would like to have some kind of hard drive image you could apply to a drive, similarly to crafting a Linux drive with an 8 MB drive and a wrench, but instead of making a Linux drive it makes a drive with TCC and header files, but that would require support in the OC2 mod, and I don't know any java.
As for the framebuffer, I've not interacted with the /dev entries, but I've tested the projector and monitor and both seem to work fine.

I tested the projector again and found that /dev/fb0 does appear, but only when a monitor or projector are connected (you may have to reboot the VM after connecting one).  Since those devices are the only things that can display a framebuffer, it would be useless to have the /dev entries without them anyway.

I decided to re-add TCC in the latest release as demand was higher than expected.  I've also published libc headers, they take up about 2 MB, I recommend you put them on another drive that can be mounted at /usr/include, but you can extract them directly if your rootfs has more than 2 MB free.


UI: Disable string truncation

Please provide an option to disable string truncation, especially when strings are inlined.
00400e9d  puts("So you got that one.  Try this o…")

Option for max string annotation length added in 2.0.2196-dev - analysis.limits.maxStringAnnotationLength


chore: upstream rcases

I think it's important that we bring the test cases along too. I will need to separately PR Std's GuardExpr.lean tactics/commands for the tests.

I just want to make a remark about maintenance here for this and other PRs in this series: Please continue to route bug reports on these files with my name on them to me. I'm fine with them leaving the std repo but I hope this doesn't interfere with my continued maintenance of the files.

@digama0 This is a valid concern. Thanks for sharing it. Happy to hear you are willing to continue maintaining the file.
rcases has a nontrivial syntax, if you are planning to keep tweaking it, I suggest we avoid using rcases in this repo. Otherwise, you may waste a lot of time dealing with bootstrapping issues.

@semorrison I added only a few sanity checks. I agree with you that we should move the test file from Std as soon as we move GuardExpr.lean.

The syntax of rcases is not likely to change, unless it is changed as a part of upstreaming now (as was done for fun. syntax). But there are routinely issues that appear in how metavariables are handled, or how things are unfolded, whether it works on other inductive-like types, appearance of hover text, etc., much the same as with the cases tactic. Furthermore there is a big TODO still remaining in the code for implementing the rcases? tactic.


Added a twig extension

Hi,
Not really an issue, but I couldn't find it in the documentation.
How can I add Twig extensions, like MarkdownExtension ?
I use Webpack 5 and my config looks like this:
    module: {
        rules: [
            {
                test: /\.twig$/,
                use: [
                    'raw-loader',
                    {
                        loader: 'twig-html-loader',
                        options: {
                            data: {}
                        }
                    }
                ]
            },
        ],
    },
    plugins: [
        new HtmlWebpackPlugin({
            template: 'src/templates/index.twig'
        }),
    ],

I'm not sure how up-to-date this is but there is mention of a JavaScript markdown extension under Available Extensions in the docs.


test/provider_test.c: Add OSSL_PROVIDER_unload() to avoid memory leak

Add OSSL_PROVIDER_unload() when OSSL_PROVIDER_add_builtin() fails to avoid memory leak.
Fixes: 5442611dff ("Add a test for OSSL_LIB_CTX_new_child()")

Checklist

[ ] documentation is added or updated
[ ] tests are added or updated

This pull request is ready to merge

Merged to all the active branches. Thank you for your contribution.


different parsed result from README

Hi, I tried the example code in README but there is no comment element after parsed.
in README:
[
    // ignoring first element
    {
        type: "script",
        name: "script",
        attribs: {
            language: "javascript",
        },
        children: [
            {
                data: "var foo = '<bar>';<",
                type: "text",
            },
        ],
    },
    {
        data: "<!-- Waah! -- ",
        type: "comment",
    },
];

with<EMAIL_ADDRESS>&<EMAIL_ADDRESS>[
    // ignoring first element
    {
        type: "script",
        name: "script",
        attribs: {
            language: "javascript",
        },
        children: [
            {
                data: "var foo = '<<bar>>';< /  script><!--<!-- Waah! -- -->",
                type: "text",
            },
        ],
    }
];

I am not sure which should I expect.
Thanks in advance!

Good spot! Looks like some space were added here that shouldn't be there 👀


Implemented GroupDMChannel#setIcon as a usable method

Please describe the changes this PR makes and why it should be merged:
Added setIcon for a group DM as a usable method, albeit not mentioned on official discord documentation.
Acceptes a base64 hash string, a buffer, or a string with data:image/png;base64, already prefixed.
This is implemented for the ease of accessability, and adds or makes no breaking changes.
Semantic versioning classification:

[x] This PR changes the library's interface (methods or parameters added)

[ ] This PR includes breaking changes (methods removed or renamed, parameters moved or removed)

[ ] This PR only includes non-code changes, like changes to documentation, README, etc.

I see this is now being implemented in #1747, ill close this one if that PR passes, or if requested

close this pr


Daffio guides

PR Checklist
Please check if your PR fulfills the following requirements:

[ ] The commit message follows our guidelines: https://github.com/graycoreio/daffodil/blob/master/CONTRIBUTING.md#commit
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Other... Please describe:

What is the current behavior?

Touches: #336
What is the new behavior?
Does this PR introduce a breaking change?
[ ] Yes
[ ] No

Other information

What is the guides sidebar supposed to contain? It should be named differently, but I'm not sure I understand what its purpose is on the API docs page.

@xelaint the intent of the guides sidebar, as Nolan and I discussed offline, is to allow people to see guides for the Daffodil project as a whole. It's not limited to the API section. It will exist in the template across all the "docs" pages.

@damienwebdev So the guides sidebar will include navigation for components, design, etc?
Can we just call it the docs sidebar instead of guides?


Priority_Queue_using_Linked_List in C (GSSoC'21)

🚀 Feature
Have you read the Contributing Guidelines on Pull Requests?
Yes !
AIM :: IMPLEMENT PRIORITY QUEUE USING LINKED LIST in C.
Motivation
As i didn't found IMPLEMENTATION OF PRIORITY QUEUE USING LINKED LIST in C language , So i am willing to contribute it...
Pitch
Hi I am GSSoC'21 participant,
"I am looking to work on the implementation of Priority queue using Linked List in C language
I will use C.
I will write the clean and optimized code , by keeping best case time and space complexity in mind and
with  brief commenting and algorithm.

/assign

Fixes #3497


FunctionCache incorrectly caches dynamic static functions calls

After weeks, I finally managed to pinpoint the issue and produce a small testcase:
Starts to appear with e1a78ce707b408d1ce80740890478aef56a764ad
(as i already mentioned, this is the followup)
Zephir Code:
namespace Test;

class DebugBase
{
    public function doAction()
    {
        var s;
        let s = "Test\\DebugInstance1";
        echo({s}::returnHello());
        let s = "Test\\DebugInstance2";
        echo({s}::returnHello());
    }
}

namespace Test;

class DebugInstance1
{
    public static function returnHello()
    {
        return "hello";
    }
}

namespace Test;

class DebugInstance2
{
    public static function returnHello()
    {
        return "bye";
    }
}

PHP-Code:
<?php
namespace Test;
$d = new DebugBase();
$d->doAction();

Output:
hellohello

Expected:
hellobye

(Assumed) Cause of this bug:
https://github.com/phalcon/zephir/blob/3661e14c8495a129841fd11589033956b939647b/ext/kernel/fcall.c#L413
I think the problem is on a static function call the target of the call
is not used to generate a fcache-hash.
if (type != zephir_fcall_function && !object_pp) {  is automatically true on a static call,
so object_pp is set and therefor object_ce is ignored and not passed further,
leading to identicalhash keys and therefor to the
same cache result.
Therefore only the calling scope and function name is taken to account.
Hopefully someone who understands the internals, will be able to properly fix this.

@phalcon @andresgutierrez
Does my assumption there make sense?
If not, could you please take a look at this? :)


Selection Mode Grid

I have a problem with SelectionMode in Grid.
SelectionMode.SINGLE should select whole row and not just one cell and sidebars of ther cells with blue.
http://prntscr.com/gewp5j
SelectonMode.NONE select one cell and shuld select none
http://prntscr.com/gewop9
SelectionMode.MULTI should select all rows and cells
http://prntscr.com/gewo4s

Thank you for reporting. Unfortunatly I'm currently on holidays, I'm gonna fix this during the next week.

Fix is published. I hope this fixes the described problem let me know if it works. If not not you are welcome to reopen this issue

I have tested and in my case grid works. Thank you.


The UI shows a scroll bar for individual cells in input tables

Description
A scroll bar is present on the right hand side of a cell in an input table while data is being entered.
Steps to reproduce
Create an input table and enter data.
from deephaven import empty_table, InputTable

t = empty_table(10).update(["X = i"])
t2 = InputTable(t)

Then, add data to a table, and on the right hand side, a small block appears. It's a scroll bar, and you can slightly move the text up and down.
Expected results
No scroll bar.
Actual results
A scroll bar.
Additional details and attachments

Versions

Engine Version: 0.19 (latest)
Web UI Version: latest
Java Version: 11
Barrage Version: unknown
OS: OS X Catalina
Browser: Chrome
Docker: 20.10.13

@jjbrosnan this seems to be behaving correctly. No scrollbar with single line for me. Scrollbar appears once multi-lines are used. Can you see if you are still able to produce?

I can't reproduce this.


[BULK] DocuTune - Fix build validation issues: docs-link-absolute (part 1)

Global effort to fix build validation errors
The Microsoft Skilling team is fixing build validation errors and specific brand inconsistencies in Microsoft technical documentation for the rest of FY23 Q1. This will help address various accessibility, security, and usability issues. This PR was generated using DocuTune. It includes only targeted fixes and minor formatting adjustments.
DocuTune PRs improve quality of technical content by finding and automatically correcting a broad set of issues only where the correction is suitable. Please review within five business days and merge or comment in the PR with any changes you'd like to see. Thank you!
CorrelationId: 0df9c2d6-63f8-4d1e-8b57-b33611a06514
InitiativeId: docutune-build-validation-issues-2022-05
PointOfContact: Alex Buck

#docutune-draft

Docs Build status updates of commit 7906176:
:warning: Validation status: warnings

File
Status
Preview URL
Details

dynamicsax2012-technet/configure-sql-server-and-storage-settings.md
:warning:Warning
View
Details

dynamicsax2012-technet/data-import-export-framework-user-guide-dixf-dmf.md
:warning:Warning
View
Details

dynamicsax2012-technet/deploy-high-availability-environment-azure.md
:warning:Warning
View
Details

dynamicsax2012-technet/deploy-retail-ecommerce-devtest-environment-azure.md
:warning:Warning
View
Details

dynamicsax2012-technet/deploy-retail-essentials-demo-environment-azure.md
:warning:Warning
View
Details

dynamicsax2012-technet/deploy-retail-essentials-devtest-environment-azure.md
:warning:Warning
View
Details

dynamicsax2012-technet/deploy-retail-mobility-devtest-environment-azure.md
:warning:Warning
View
Details

dynamicsax2012-technet/find-ax-2012-content.md
:warning:Warning
View
Details

dynamicsax2012-technet/about-the-documentation.md
:bulb:Suggestion
View
Details

dynamicsax2012-technet/configure-sql-server-and-storage-settings.md

Line 2, Column 1: [Warning: ms-author-missing - See documentation] Missing required attribute: 'ms.author'. Add the current author's Microsoft alias.
Line 104, Column 1: [Warning: code-block-indented - See documentation] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```).
Line 164, Column 1: [Warning: code-block-indented - See documentation] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```).
Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.
Line 112, Column 170: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL.  Otherwise, remove the view parameter. URL: /sql/database-engine/configure-windows/configure-the-max-degree-of-parallelism-server-configuration-option?view=sql-server-ver15

dynamicsax2012-technet/data-import-export-framework-user-guide-dixf-dmf.md

Line 2, Column 1: [Warning: ms-author-missing - See documentation] Missing required attribute: 'ms.author'. Add the current author's Microsoft alias.
Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

dynamicsax2012-technet/deploy-high-availability-environment-azure.md

Line 1, Column 1: [Warning: author-missing - See documentation] Missing required attribute: 'author'. Add the current author's GitHub ID.
Line 1, Column 1: [Warning: title-missing - See documentation] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 1, Column 1: [Warning: ms-author-missing - See documentation] Missing required attribute: 'ms.author'. Add the current author's Microsoft alias.
Line 7, Column 6: [Warning: yaml-header-syntax-error] While parsing a flow sequence, did not find expected ',' or ']'.
Line 1, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.
Line 471, Column 5: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL.  Otherwise, remove the view parameter. URL: /powershell/module/remotedesktop/?view=win10-ps

dynamicsax2012-technet/deploy-retail-ecommerce-devtest-environment-azure.md

Line 1, Column 1: [Warning: author-missing - See documentation] Missing required attribute: 'author'. Add the current author's GitHub ID.
Line 1, Column 1: [Warning: title-missing - See documentation] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 1, Column 1: [Warning: ms-author-missing - See documentation] Missing required attribute: 'ms.author'. Add the current author's Microsoft alias.
Line 7, Column 6: [Warning: yaml-header-syntax-error] While parsing a flow sequence, did not find expected ',' or ']'.
Line 1, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

dynamicsax2012-technet/deploy-retail-essentials-demo-environment-azure.md

Line 1, Column 1: [Warning: author-missing - See documentation] Missing required attribute: 'author'. Add the current author's GitHub ID.
Line 1, Column 1: [Warning: title-missing - See documentation] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 1, Column 1: [Warning: ms-author-missing - See documentation] Missing required attribute: 'ms.author'. Add the current author's Microsoft alias.
Line 7, Column 6: [Warning: yaml-header-syntax-error] While parsing a flow sequence, did not find expected ',' or ']'.
Line 1, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

dynamicsax2012-technet/deploy-retail-essentials-devtest-environment-azure.md

Line 1, Column 1: [Warning: author-missing - See documentation] Missing required attribute: 'author'. Add the current author's GitHub ID.
Line 1, Column 1: [Warning: title-missing - See documentation] Missing required attribute: 'title'. Add a title string to show in search engine results.

This comment lists only the first 25 errors (including error/warning/suggestion) in the pull request.
For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

#docutune-ready

@buck1ey
Please merge the changes in this PR. For more information, see the description at the top of this PR.
Any pre-existing build validation issues or insufficient Acrolinx scores should be addressed in a separate PR.
#docutune-request-approval


MSL: RWBuffer is translated into a texture2d and buffer of atomic_int even though SPIRV-Cross can tell the original type

We're using DXC to turn the following  HLSL:
RWBuffer<uint> g_DispatchIndirectBuffer : register( u0 );

[numthreads(1, 1, 1)]
void CSMain()
{
    uint prevGroupCnt;
    InterlockedAdd(g_DispatchIndirectBuffer[0], 4, prevGroupCnt);
}

Into the following SPIR-V
; SPIR-V
; Version: 1.0
; Generator: Google spiregg; 0
; Bound: 15
; Schema: 0
               OpCapability Shader
               OpCapability SampledBuffer
               OpCapability ImageBuffer
               OpMemoryModel Logical GLSL450
               OpEntryPoint GLCompute %CSMain "CSMain"
               OpExecutionMode %CSMain LocalSize 1 1 1
               OpSource HLSL 630
               OpName %type_buffer_image "type.buffer.image"
               OpName %g_DispatchIndirectBuffer "g_DispatchIndirectBuffer"
               OpName %CSMain "CSMain"
               OpDecorate %g_DispatchIndirectBuffer DescriptorSet 0
               OpDecorate %g_DispatchIndirectBuffer Binding 0
       %uint = OpTypeInt 32 0
     %uint_0 = OpConstant %uint 0
     %uint_4 = OpConstant %uint 4
%type_buffer_image = OpTypeImage %uint Buffer 2 0 0 2 R32ui
%_ptr_UniformConstant_type_buffer_image = OpTypePointer UniformConstant %type_buffer_image
       %void = OpTypeVoid
          %9 = OpTypeFunction %void
%_ptr_Image_uint = OpTypePointer Image %uint
     %uint_1 = OpConstant %uint 1
%g_DispatchIndirectBuffer = OpVariable %_ptr_UniformConstant_type_buffer_image UniformConstant
     %CSMain = OpFunction %void None %9
         %12 = OpLabel
         %13 = OpImageTexelPointer %_ptr_Image_uint %g_DispatchIndirectBuffer %uint_0 %uint_0
         %14 = OpAtomicIAdd %uint %13 %uint_1 %uint_0 %uint_4
               OpReturn
               OpFunctionEnd

and then we use SPIRV-Cross to generate MSL:
#pragma clang diagnostic ignored "-Wunused-variable"

#include <metal_stdlib>
#include <simd/simd.h>
#include <metal_atomic>

using namespace metal;

kernel void CSMain(texture2d<uint> g_DispatchIndirectBuffer [[texture(0)]], device atomic_uint* g_DispatchIndirectBuffer_atomic [[buffer(0)]])
{
    uint _14 = atomic_fetch_add_explicit((device atomic_uint*)&g_DispatchIndirectBuffer_atomic[0u], 4u, memory_order_relaxed);
}

However, it creates a redundant texture2d and also changes the name of the buffer resource by appending _atomic at the end. Both of these could be avoided by doing something similar as done for RWStructuredBuffer, which would produce a regular MSL buffer of uint (not atomic_int) and would only cast to atomic where necessary (seen here). If I use SPIRV-Cross to generate HLSL instead of MSL it will produce the RWBuffer as in the original source:
RWBuffer<uint> g_DispatchIndirectBuffer : register(u0, space0);

void comp_main()
{
    uint _14;
    InterlockedAdd(g_DispatchIndirectBuffer[0u], 4u, _14);
}

[numthreads(1, 1, 1)]
void main()
{
    comp_main();
}

so it seems to have enough context to know that the texture won't be needed. This issue does not seem to be specific to DXC as I get the same output with glslang as seen here. Also to the point about context - using SPIRV-Cross reflection on the compiled MSL reports this resource as a SPVC_RESOURCE_TYPE_STORAGE_IMAGE and a dimensionality of buffer
spvc_type imageType = spvc_compiler_get_type_handle(spvCompiler, textureResource.base_type_id);
bool isBuffer = textureDimensionality == SpvDimBuffer;  //This is true for RWBuffers and not for RWTextures

The issue seems vaguely related to https://github.com/KhronosGroup/SPIRV-Cross/issues/950.
However I don't agree with the recommendation that instead of a RWBuffer we should use a RWStructuredBuffer or RWByteAddressBuffer since they produce the desired MSL buffer. This is not an option for us at Unity as our users can write their own shaders and thus the issue can't be fixed at the HLSL level.

This is a typed buffer, and not a raw buffer. MSL does not support typed buffers, and thus is emulated as a texture2D. In SPIR-V a typed buffer is expressed an image with buffer dimension, so this is all expected.
There is an option which enables native texture buffer support (minspec is Metal 2.1): https://github.com/KhronosGroup/SPIRV-Cross/blob/master/spirv_msl.hpp#L311
However, even with that, MSL does not support atomics on typed buffers/images, and thus we get the weirdness you see here. Another contributor added the atomic side buffer as a workaround for this problem.
I'm not sure what I can do, MSL is making it needlessly difficult to implement this as you'd expect.

Ok, I see another avenue here. The OpTypeImage format is declared as R32UI by DXC, that helps a lot. That might be enough to make this work. However, this can only possibly work for texel buffers, not RWTexture, just in case you were expecting that to work as well.

Actually, that won't work either ... Texture buffers in MSL are declared with [[texture()]] and not [[buffer()]]. We'd be silently rewriting the binding type, which breaks API side.

Here's an equivalent:
#version 450
layout(local_size_x = 1) in;

layout(set = 0, binding = 0, r32ui) uniform uimageBuffer uImg;

void main()
{
	imageAtomicAdd(uImg, 1, 2u);
}

With --msl-native-texture-buffer I get:
#pragma clang diagnostic ignored "-Wunused-variable"

#include <metal_stdlib>
#include <simd/simd.h>
#include <metal_atomic>

using namespace metal;

constant uint3 gl_WorkGroupSize [[maybe_unused]] = uint3(1u);

kernel void main0(texture_buffer<uint> uImg [[texture(0)]] /* :( */, device atomic_uint* uImg_atomic [[buffer(0)]])
{
    uint _17 = atomic_fetch_add_explicit((device atomic_uint*)&uImg_atomic[1], 2u, memory_order_relaxed);
}

From my perspective it's not clear why use a texture resource to emulate the buffer in the first place (and this might be lack of experience with Metal on my part), is it just that it's simpler to translate the SPIR-V that way? For more context, a snippet like this, which uses both atomic and regular writes:
RWBuffer<uint> g_DispatchIndirectBuffer : register( u0 );

#pragma never_use_dxc

[numthreads(1, 1, 1)]
void CSMain()
{
    uint prevGroupCnt;
    InterlockedAdd(g_DispatchIndirectBuffer[0], 4, prevGroupCnt);
    g_DispatchIndirectBuffer[5] += 6;
}

When passed through our existing MSL backend (which does HLSL -> [FXC]-> DXBC -> [HLSLcc] -> MSL, so there's no SPIR-V in the middle) produces the following MSL:
generates this MSL:
#include <metal_stdlib>
#include <metal_texture>
using namespace metal;

#if !(__HAVE_FMA__)
#define fma(a,b,c) ((a) * (b) + (c))
#endif

kernel void computeMain(
    device uint *g_DispatchIndirectBuffer [[ buffer(0) ]])
{
    int u_xlati0;
    atomic_fetch_add_explicit(reinterpret_cast<device atomic_uint *>(&g_DispatchIndirectBuffer[0x0]), 0x4u, memory_order::memory_order_relaxed);
    u_xlati0 = int(g_DispatchIndirectBuffer[(0x5)]);
    u_xlati0 = u_xlati0 + 0x6;
    g_DispatchIndirectBuffer[(0x5)] = uint(u_xlati0);
    g_DispatchIndirectBuffer[(0x5)] = uint(u_xlati0);
    g_DispatchIndirectBuffer[(0x5)] = uint(u_xlati0);
    g_DispatchIndirectBuffer[(0x5)] = uint(u_xlati0);
    return;
}

And I'm not clear why couldn't SPIRV-Cross produce the same/similar (at least in the fact that is would use [[buffer ()]] and not [[texture()]]), given that it can tell that the resource was originally a buffer. We'd highly prefer if we didn't have to change our resource types depending on what compiler backend we're using as shaders from both might need be used together.

Because again, it's a typed buffer. That means that pixel conversion is applied to the buffer's contents on every load and store. In Vulkan, you would create a VkBufferView and bind it to a descriptor of type STORAGE_TEXEL_BUFFER. In MoltenVK, this is implemented by creating an MTLTexture on the buffer and passing that to the shader; that's why we need a texture2d or texture_buffer parameter here.

Either HLSLCC or FXC must be applying some very special workaround here, because that MSL code rewrites the fact that the buffer is typed, and I don't see how that would work in a more interesting case. I'm open to adding support for a similar workaround in SPIRV-Cross, but it would have to be opt-in. E.g. something like, typed buffer with R32UI/I format declared will be treated as a plain buffer, but that's a very narrow workaround and not a general purpose solution.

I'm open to adding support for a similar workaround in SPIRV-Cross, but it would have to be opt-in. E.g. something like, typed buffer with R32UI/I format declared will be treated as a plain buffer

Opt-in flag to get that behavior would work just fine for our (Unity) use case.

I'm open to adding support for a similar workaround in SPIRV-Cross, but it would have to be opt-in.

As @aras-p said, having an opt-in would be great for us.

E.g. something like, typed buffer with R32UI/I format declared will be treated as a plain buffer, but that's a very narrow workaround and not a general purpose solution.

You might have already had this in mind, but to be explicit about it - we would need regular Buffer<> types to produce [[buffer()]] bindings as well (not just RWBuffer<> types)

All Buffer<> types? How would that work? Now I'm very confused.
E.g. for a Buffer<float4> type, you could bind almost any pixel format for it in the API, and get implicit format conversion through the descriptor when you load a value. There is no way we can work around that with a plain buffer. Note that we won't know the underlying format in SPIRV-Cross, Buffer<> is a texel buffer.
This workaround can only work iff:

For RWBuffer, shader seems to declare R32UI/R32I types in the SPIR-V. The SPIR-V you posted does this.
The type system could rewrite that type to be a buffer, but it can only meaningfully work for that particular type.

There is also the question of alignment. Texel buffers can support very tight alignment, but buffer objects often don't. Does Metal guarantee support for 4-byte aligned buffer descriptors?

I think all of this is actually for a fairly narrow case of: original HLSL source has a Buffer or RWBuffer declaration of int or uint type, and only ever does reads/writes into it (maybe even "all of the reads/writes are atomic" even).
Yes that's a very "unorthodox" use case, and arguably the original HLSL source should be rewritten to use structured buffer or byte address buffer. But as it is right now, whoever wrote original HLSL ("anyone can write it!" is an issue we have at Unity :)), would be "oh this works everywhere, except on Metal, Metal must be broken!". Or even more likely, not even test on Metal, only to find out their end users or someone entirely else find that it's broken on Metal.
Yes that's a very "non generic" use case, and would be kind of a gross hack. But a flag to SPIRV-Cross that would essentially allow saying "if you find buffer or rwbuffer with 4-byte integer type that only ever does atomic operations on it, please output that as a buffer and not a texture" would probably cover this specific case.

Buffer<> cannot use atomics, it's a read-only type. It should translate perfectly to a texture_buffer. We won't know the underlying format, so I cannot support that anyways. Even if HLSL declares it as Buffer all sampling still happens on float4 types. It will just pick the x component for convenience.
RWBuffer<> with explicitly declared R32UI/R32I types in the SPIR-V is narrow enough that it can be done. However, I assume you do some funky detection logic in engine side to see "This is a typed UAV with R32UI type, let's make this a plain buffer instead of a typed buffer".

However, I assume you do some funky detection logic in engine side to see "This is a typed UAV with R32UI type, let's make this a plain buffer instead of a typed buffer".

Not exactly, our current backend has the limitation that it tries to produce output from DXBC which essentially has very little type information when compared to SPIR-V from what I've seen. This results in minimal type information being left in the output MSL, the buffer is assumed to be packed in memory as it would be in DirectX and casts are performed on every access

There is no way we can work around that with a plain buffer, what kind of code do you emit in hlslcc for that case?

So for a Buffer<float4> from source like this:
Buffer<float4> roBuffer : register( t0 );
RWBuffer<uint> g_DispatchIndirectBuffer : register( u0 );

[numthreads(1, 1, 1)]
void CSMain()
{
    uint prevGroupCnt;
    InterlockedAdd(g_DispatchIndirectBuffer[0], uint(roBuffer[1].y), prevGroupCnt);
    g_DispatchIndirectBuffer[5] += 6;
}

it would still generate a buffer of uint and output the following:
#include <metal_stdlib>
#include <metal_texture>
using namespace metal;

#if !(__HAVE_FMA__)
#define fma(a,b,c) ((a) * (b) + (c))
#endif

kernel void computeMain(
    const device uint *roBuffer [[ buffer(1) ]],
    device uint *g_DispatchIndirectBuffer [[ buffer(0) ]])
{
    float u_xlat0;
    int u_xlati0;
    uint u_xlatu0;
    u_xlat0 = as_type<float>(roBuffer[(0x1)]);
    u_xlatu0 = uint(u_xlat0);
    atomic_fetch_add_explicit(reinterpret_cast<device atomic_uint *>(&g_DispatchIndirectBuffer[0x0]), u_xlatu0, memory_order::memory_order_relaxed);
    u_xlati0 = int(g_DispatchIndirectBuffer[(0x5)]);
    u_xlati0 = u_xlati0 + 0x6;
    g_DispatchIndirectBuffer[(0x5)] = uint(u_xlati0);
    g_DispatchIndirectBuffer[(0x5)] = uint(u_xlati0);
    g_DispatchIndirectBuffer[(0x5)] = uint(u_xlati0);
    g_DispatchIndirectBuffer[(0x5)] = uint(u_xlati0);
    return;
}

So that code translates roBuffer[1].y to as_type<float>(roBuffer[(0x1)]). How can that be correct? It does not take into account texel strides either, I'm somewhat puzzled by this.

Yes, I just noticed that myself, so as @aras-p  said we're most likely only meaningfully using Buffer in our code and Buffer seems like an untested case, just tried non zero offset with a Buffer and it's correct

So in that case, a workaround would look something like:

Any Buffer<> / UNIFORM_TEXEL_BUFFER or RWBuffer<> / STORAGE_TEXEL_BUFFER, no matter what is treated as being a scalar 32-bit value. Client side guarantees that the only texel formats will only be 32-bit scalar.
Any access to such a resource goes through a plain buffer pointer.
Certain features like GetResourceDimensions() will be unavailable (it's just a pointer).
Robustness is out the window (no resource size information, again, it's just a pointer).

It is still unclear to me why you would need to emit pointer types for Buffer though. There are several mechanisms you could use in Metal to implement this "correctly". The only real problem case I can see where this workaround would have made sense is RWBuffer with atomics, since Metal has no reasonable way to express this without ugly hackery.

Yeah that sounds like it would work for our case.
But all the discussion above has good points, our own particular (very occasional) usage of Buffer<uint> / RWBuffer<uint> in HLSL code is very much "unusual" and I'm actually surprised that we even use it in that way. Apparently someone did, and it has happened to (by accident) work with the previous compiler toolchain, but now with a "more proper" DXC + SPIRV-Cross one it has uncovered that our usage was kinda wrong. Maybe not worth doing this workaround, and instead we'll try to fix all the offending HLSL source code instead.

That would be much appreciated. Working around this in SPIRV-Cross is a last resort and I really don't want to do it, especially if it starts to affect all typed buffers like this. A SPIR-V -> SPIR-V transformation is more appropriate if possible, but the best fix is to fix the invalid shader code of course.


alert prow plugin for no cla PR merges

https://kubernetes.slack.com/archives/C01672LSZL0/p1726321799185879
A prow plugin that can support sending alert to slack when a PR with cncf-cla: no label was merged.

like https://github.com/search?q=org%3Akubernetes+is%3Apr+is%3Amerged+label%3A"cncf-cla%3A+no"+created%3A>2023-01-01+&type=pullrequests

In this a scope-limited form, this should not be hard to write. Get a GH webhook call about a merge, inspect the PR, send a notification (we already have Slack client code in Prow).
Notification systems love to grow in scope, though :thinking: Some people will almost certainly want notifications about other events. Some people will almost certainly want notifications to different destinations than Slack. Would we need per-org / per-repo configuration surface? Like disabling the notifications for certain repos, or routing the notifications to different slacks based on repos?
Given the current state of Prow maintenance, I think we should prefer building a very simple, single-purpose thing rather than trying to come up with a new generic notification system.
One alternative could be something that simply publishes interesting metrics through Prometheus and then we could set up standard alertmanager-backed alerts for events like this.

One alternative could be something that simply publishes interesting metrics through Prometheus and then we could set up standard alertmanager-backed alerts for events like this.

This seems to be a better solution to me, as the cncf-cla： no is not a general case and only occurs several time a year.

Adding a github action like thing for all PRs seems to be too heavy
An alert may be a lightweight solution.

If we want to go this direction, is there an example to add an alert policy?

@dims @BenTheElder which solution do you prefer?

@pacoxu see example in https://kubernetes.slack.com/archives/CJH2GBF7Y/p1724136124406689

An alert like that looks like a great thing to have

We shouldn't rely on the label, the status is the source of truth.
Statuses can change after PRs merge, so the alert is only a best effort warning in any case.
If we want to be 100% sure, the CNCF CLA tooling could run an audit mode and scan all commits in the repo against their CLA database (which would surely be cheaper than us attempting to scan the github API for commit statuses).
For a weak check:

Given the current state of Prow maintenance, I think we should prefer building a very simple, single-purpose thing rather than trying to come up with a new generic notification system.

Yes, I think we could reuse some tooling from the slack alerts but I think it should be a single purpose plugin if we implement this, to keep things as simple as possible.
I think the problem with using a metric is then we still need to track down where the bad merge happened, and now we have large cardinality on the metric if we're recording it there. Versus if we just push out a slack alert (and/or completely offload this to CNCF auditing).

(Poking some CNCF folks about the subject ...)

link to https://github.com/kubernetes/community/issues/7800

I disagree strongly with the linked issue and I think that's an unrelated topic for now.


MCreator

Project description
describe the project a little
Mcreator is a mod maker for minecraft. It is open-source. It is written in Java 11
Metadata

homepage URL: https://mcreator.net/
source URL:https://github.com/MCreator/MCreator
license: mit, bsd, gpl2+ , gpl3 modified
platforms: unix, linux, darwin, ... linux, darwin, windows

Anyone looking for a bandage, I made an impure flake for you to install it using FHS
nix profile install github:MathiasSven/MCreatorFlake --no-write-lock-file --impure

Bump - I'd love to see this


Props children no Longer Renders

The prop children used to work as expected, and would render controls that were passed via it. Now it appears to no longer render anything. This code used to display two buttons at the bottom of the notification:
const controls =
     <div>
         <button type="button" onClick={doSomething}>YES</button>
         <button type="button" >NO</button>
     </div>
const notification = {
     dismissible: true,
     title: 'some title',
     message: "some msg",
     level: 'warning',
     autoDismiss: 0,
     children: controls,
 }

Now no buttons render unless I use the action prop. For reference, I'm using React 15.6.2

Appears to have been fixed at some point; it's working as expected now in 0.2.17.


ACIR gen errors with some kinds of known failing constraints, changing expected errors in tests

Aim
Writing a test of a function that guards out of bounds accesses with a custom message, snippet:

    for i in 0..N {
        if i < collapsed.len() {
            let input_index = collapsed_to_input_index_mapping.get_unchecked(i);
            assert(input_index < N, "Out of bounds index hint"); // instead of here

            assert_eq(collapsed.get_unchecked(i), input[input_index].unwrap(), "Wrong collapsed vec content"); // erroring here

Expected Behavior
It should fail in assert(input_index < N, "Out of bounds index hint");
Bug
instead fails in input[input_index].
This is the SSA:
After Array Set Optimizations:
acir(inline) fn verify_collapse_hints_out_of_bounds_index_hint f0 {
  b0():
    constrain u1 0 == u1 1 'Out of bounds index hint'
    v66 = array_get [u1 1, Field 7, u1 0, Field 0, u1 1, Field 3], index u32 10
    v67 = array_get [u1 1, Field 7, u1 0, Field 0, u1 1, Field 3], index u32 11
    constrain v66 == u1 1
    constrain Field 3 == v67 'Wrong collapsed vec content'
    return
}

As you can see it should fail in the known to fail constraint (it's known to fail at compile time because this is a test)
Instead it fails in the array get with index 10, because ACIR generation evaluates array gets and errors directly, but apparently doesn't do so with assertions
To Reproduce

Project Impact
None
Impact Context
No response
Workaround
None
Workaround Description
No response
Additional Context
No response
Installation Method
None
Nargo Version
No response
NoirJS Version
No response
Would you like to submit a PR for this Issue?
None
Support Needs
No response

Minimal repro:
fn main(inputs: [Field; 4], index_hint: u32) {
    assert(index_hint < inputs.len(), "Out of bounds index hint");
    let hinted_value = inputs[index_hint];
    assert_eq(hinted_value, 27);
}

#[test(should_fail_with="Out of bounds index hint")]
fn test_bounds_check() {
    main([1, 2, 3, 4], 4);
}


-Use a single append to concatenate two slices

1.Describe what this PR did
-Use a single append to concatenate two slices
2.Does this pull request fix one issue?

NONE
3.Describe how you did it
Before:
for _, e := range y {
x = append(x, e)
}
After:
x = append(x, y...)
4.Describe how to verify it
NONE
5.Special notes for reviews
NONE

The codes are generated with swagger, We should not modify them. Thanks for your idea. @wgliang

Yeah, like skoo mentioned. This files are automatically generated.  I am afraid these files are OK. More api change, we can refer to https://github.com/alibaba/pouch/blob/master/apis/README.md
I am closing this, and feel free to tell us if you have more questions. Thanks a lot again for you contribution. @wgliang


Integrate recent dev updates into main to trigger a fresh readthedocs build.

To activate recent updates to ISOFIT's documentation, we merge dev into main to trigger a new readthedocs build, for now, without issuing a new release.

Checks have passed on dev, so merging right away.


Fix wait-for-desired-code-replication always choosing distributed mod…

…e regardless of actual cluster mode
Since total-storm-conf is the merge of daemon conf and topology conf, it more than likely doesn't reflect which STORM-CLUSTER-MODE Nimbus was started with.

Nevermind this, the right mode is set when using the local cluster from testing4j, so this is probably fine.


🐛Attempting to delete a Log without the correct access level gives incorrect feedback

:bug: Describe the bug
If a user does not have permission to delete a Log, but they attempt to delete one, they get a toast saying the Log was successfully deleted even though it is still there.
To Reproduce
Steps to reproduce the behavior:

Access a server where you do not have permission to delete Logs
Drill down to Log level.
Try to delete a Log.
Observe toast saying Log was deleted and that the Log is still there.

Expected behavior
An error message is displayed to the user telling them they do not have access to delete Logs.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

Device: Laptop
OS: Windows
Browser: Chrome
Version: 92.0.4515.159

A related issue in this respect (delete log).
If the connection is broken between the API and WITSML server, the log will still be removed from GUI and appear to have been deleted. No other feedback is then given to user.
In the image below Caliper seem to have been deleted when it has not.

The following message is shown when trying to delete a log with permission


shell_unittest OnPlatformViewDestroyWhenThreadsAreMerging is flaky

OnPlatformViewDestroyWhenThreadsAreMerging added in https://github.com/flutter/engine/commit/e7136c3 is flaky on linux
Log: https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket.appspot.com/8871327900817333536/+/steps/Host_Tests_for_host_debug_unopt/0/stdout?format=raw

Close in favor of https://github.com/flutter/flutter/issues/64562


Double-Checked Locking

https://github.com/Netflix/titus-control-plane/blob/cc89c5334fbfedede530e6209e45eede2cb1bc0e/titus-ext/aws/src/main/java/com/netflix/titus/ext/aws/AmazonClientProvider.java#L33-L35
https://github.com/Netflix/titus-control-plane/blob/cc89c5334fbfedede530e6209e45eede2cb1bc0e/titus-ext/aws/src/main/java/com/netflix/titus/ext/aws/AmazonClientProvider.java#L52-L55
double-Checked Locking is widely cited and used as an efficient method for implementing lazy initialization in a multithreaded environment.
Unfortunately, it will not work reliably in a platform independent way when implemented in Java, without additional synchronization.

Thanks, we do not target platform independency today. Closing


#/replication page does not work

The http://<IP_ADDRESS>:5984/_utils/#/replication page is not functional although it seems to work. No documents created in _replicator db.

working now that we've upgraded fauxton


feat(tool): include tooling to track excluded lint rules and their reasons

Status
READY
Description
Related to #99.
Creates a script that creates a table with those lint rules that are not enabled by default by Very Good Analysis, together with their reasons, if any.
Adds exclusion reasons for:

always_put_control_body_on_new_line
always_specify_types
discarded_futures (#74)
prefer_double_quotes
prefer_relative_imports
use_decorated_box
annotate_redeclares

Type of Change

[ ] ✨ New feature (non-breaking change which adds functionality)
[ ] 🛠 Bug fix (non-breaking change which fixes an issue)
[ ] ❌ Breaking change (fix or feature that would cause existing functionality to change)
[ ] 🧹 Code refactor
[ ] ✅ Build configuration change
[X] 📝 Documentation
[X] 🗑 Chore

Thanks @oaahmad that's precisely what I didn't like about it. Thanks for providing the old and new link!
https://github.com/dart-lang/sdk/issues/55977 sounds great! The current documented link was the one I was relying on (and scraping it was far from ideal). This said, I hope the Dart team is aware that people  might be consuming such file so they are conscious on the impact their changes can have (I think Irnh is already on the right track https://github.com/dart-lang/sdk/issues/55977#issuecomment-2159918349).


Required constraint in relationships and DTO option generate error in Angular

Overview of the issue

I have imported my JDL file and notice that in Angular when I tried to update or create a record I have got an error of missing field and the value does not appear for textbox.

Motivation for or Use Case

import-jdl
relationship ManyToOne  +  required
dto ENTITY with mapstruct
ERROR in the front

Reproduce the error

I imported a JDL file with below command:

mvn clean & jhipster import-jdl Books.jdl --force --debug & mvnw

This is my JDL model:
entity Book {
	name String,
	isbn String
}
entity Author {
  name String required
}

relationship ManyToOne {
  Book{author(name) required} to Author
}

dto * with mapstruct

Related issues

These are very close:

https://github.com/jhipster/generator-jhipster/issues/6835
https://github.com/jhipster/generator-jhipster/issues/1760

Suggest a Fix

The problem is that Angular code does not prepare to manage the structure of rest service with and without DTO:
Rest service without DTO:

Rest service with DTO:

Solution in book-update-component.ts is add authorName in editForm, updateForm, createFormForm

 editForm = this.fb.group({
    id: [],
    name: [],
    isbn: [],
    authorId: [null, Validators.required],
    authorName: []
  });

  updateForm(book: IBook) {
    this.editForm.patchValue({
      id: book.id,
      name: book.name,
      isbn: book.isbn,
      authorId: book.authorId,
      authorName: book.authorName
    });
  }

  private createFromForm(): IBook {
    const entity = {
      ...new Book(),
      id: this.editForm.get(['id']).value,
      name: this.editForm.get(['name']).value,
      isbn: this.editForm.get(['isbn']).value,
      authorId: this.editForm.get(['authorId']).value,
      authorName: this.editForm.get(['authorName']).value
    };
    return entity;
  }

Solution in book-update.component.html is change author for authorName

    Author
    <select class="form-control" id="field_author" name="authorName" formControlName="authorId">
        <option *ngIf="!editForm.get('authorName').value" [ngValue]="null" selected></option>
        <option [ngValue]="authorOption.id" *ngFor="let authorOption of authors; trackBy: trackAuthorById">{{authorOption.name}}</option>
    </select>

        This field is required.

JHipster Version(s)

6.0.1

JHipster configuration

JHipster Version(s)
<EMAIL_ADDRESS>C:\XXX\XXX\XXX\XX\jhipster\app
`--<EMAIL_ADDRESS>

JHipster configuration, a .yo-rc.json file generated in the root folder

.yo-rc.json file

{
  "generator-jhipster": {
    "promptValues": {
      "packageName": "com.demo",
      "nativeLanguage": "en"
    },
    "jhipsterVersion": "6.0.1",
    "applicationType": "monolith",
    "baseName": "app",
    "packageName": "com.demo",
    "packageFolder": "com/demo",
    "serverPort": "8080",
    "authenticationType": "jwt",
    "cacheProvider": "ehcache",
    "enableHibernateCache": true,
    "websocket": false,
    "databaseType": "sql",
    "devDatabaseType": "h2Memory",
    "prodDatabaseType": "postgresql",
    "searchEngine": false,
    "messageBroker": false,
    "serviceDiscoveryType": "eureka",
    "buildTool": "maven",
    "enableSwaggerCodegen": false,
    "jwtSecretKey": "[masked]",
    "clientFramework": "angularX",
    "clientTheme": "none",
    "clientThemeVariant": "",
    "useSass": true,
    "clientPackageManager": "npm",
    "testFrameworks": [],
    "jhiPrefix": "jhi",
    "entitySuffix": "",
    "dtoSuffix": "DTO",
    "otherModules": [],
    "enableTranslation": true,
    "nativeLanguage": "en",
    "languages": ["en"]
  }
}

JDL for the Entity configuration(s) entityName.json files generated in the .jhipster directory

JDL entity definitions

entity Book {
  name String,
  isbn String
}
entity Author {
  name String required
}
relationship ManyToOne {
  Book{author(name) required} to Author
}

dto Book, Author with mapstruct
service Book, Author with serviceClass

Environment and Tools
java version "12.0.1" 2019-04-16
Java(TM) SE Runtime Environment (build 12.0.1+12)
Java HotSpot(TM) 64-Bit Server VM (build 12.0.1+12, mixed mode, sharing)
git version 2.21.0.windows.1
node: v10.15.3
npm: 6.4.1
yeoman: 2.0.6
yarn: 1.16.0
INFO! Congratulations, JHipster execution is complete!
Entity configuration(s) entityName.json files generated in the .jhipster directory

Again

entity Book {
	name String,
	isbn String
}
entity Author {
  name String required
}

relationship ManyToOne {
  Book{author(name) required} to Author
}

dto * with mapstruct

Browsers and Operating System

Google Chrome

Windows 10

Hi, first of all, thanks for reporting this.
This is not the place for such an issue, it belongs to the generator. Can you open a new issue there and fill it with this one? thanks :)


feat: deny update/delete operations on tolerations

Description of your changes

Fixes #
I have:

[x] Run make reviewable to ensure this PR is ready for review.

How has this code been tested

Special notes for your reviewer
We only allow tolerations to be added to CRP. Existing tolerations cannot be updated or deleted.

Will wait for #685 to merge before this PR


Fix typo

Hi, I fixed a typo in the README file for the flame_gamepad module's description

Thanks a lot, @MauroCoppola !


access to the public folder in laravel

I bought a Laravel script and now I want to edit it. When I put a file like a jquery, I give a 404 error in the laravel public folder. But the files that were already in the public folder of laravel are running without problems, but when I create a file there, I encounter the error.
my laravel project cannot access to public folder in url like : http://basagan.com/js/jquery.js
but default file like : http://basagan.com/js/app.js is fine , work and run without problem

Hi there,
Looks like this is a question which can be asked on a support channel. Please only use this issue tracker for reporting bugs with the library. If you have a question on how to use functionality provided by this repo you can try one of the following channels:

Laracasts Forums
Laravel.io Forums
Discord
Larachat
IRC
StackOverflow


feat(InputMenu): allows to customize labels

❓ Type of change

[x] 📖 Documentation (updates to the documentation or readme)
[ ] 🐞 Bug fix (a non-breaking change that fixes an issue)
[x] 👌 Enhancement (improving an existing functionality)
[ ] ✨ New feature (a non-breaking change that adds functionality)
[ ] 🧹 Chore (updates to the build process or auxiliary tools and libraries)
[ ] ⚠ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description
Avoids to use slots or props to customize labels in InputMenu.
Request  https://github.com/nuxt/ui/pull/2266#issuecomment-2388017320.

Thanks! 😊


Won't compile (on newer Go versions?)

# go install github.com/crackcomm/cloudflare/cf
# github.com/crackcomm/cloudflare/cf/cmd
go/src/github.com/crackcomm/cloudflare/cf/cmd/cmd_firewalls_create.go:16:17: cannot use cli.StringFlag literal (type cli.StringFlag) as type cli.Flag in array or slice literal:
        cli.StringFlag does not implement cli.Flag (Apply method has pointer receiver)
go/src/github.com/crackcomm/cloudflare/cf/cmd/cmd_firewalls_create.go:20:17: cannot use cli.StringFlag literal (type cli.StringFlag) as type cli.Flag in array or slice literal:
        cli.StringFlag does not implement cli.Flag (Apply method has pointer receiver)
go/src/github.com/crackcomm/cloudflare/cf/cmd/cmd_firewalls_create.go:24:17: cannot use cli.StringFlag literal (type cli.StringFlag) as type cli.Flag in array or slice literal:
        cli.StringFlag does not implement cli.Flag (Apply method has pointer receiver)
go/src/github.com/crackcomm/cloudflare/cf/cmd/cmd_firewalls_create.go:28:17: cannot use cli.StringFlag literal (type cli.StringFlag) as type cli.Flag in array or slice literal:
        cli.StringFlag does not implement cli.Flag (Apply method has pointer receiver)
go/src/github.com/crackcomm/cloudflare/cf/cmd/cmd_firewalls_create.go:32:17: cannot use cli.StringFlag literal (type cli.StringFlag) as type cli.Flag in array or slice literal:
        cli.StringFlag does not implement cli.Flag (Apply method has pointer receiver)
go/src/github.com/crackcomm/cloudflare/cf/cmd/cmd_firewalls_create.go:36:17: cannot use cli.StringFlag literal (type cli.StringFlag) as type cli.Flag in array or slice literal:
        cli.StringFlag does not implement cli.Flag (Apply method has pointer receiver)
go/src/github.com/crackcomm/cloudflare/cf/cmd/cmd_firewalls_create.go:41:8: cannot use func literal (type func(*cli.Context)) as type cli.ActionFunc in field value
go/src/github.com/crackcomm/cloudflare/cf/cmd/cmd_firewalls_list.go:19:17: cannot use cli.StringFlag literal (type cli.StringFlag) as type cli.Flag in array or slice literal:
        cli.StringFlag does not implement cli.Flag (Apply method has pointer receiver)
go/src/github.com/crackcomm/cloudflare/cf/cmd/cmd_firewalls_list.go:23:17: cannot use cli.StringFlag literal (type cli.StringFlag) as type cli.Flag in array or slice literal:
        cli.StringFlag does not implement cli.Flag (Apply method has pointer receiver)
go/src/github.com/crackcomm/cloudflare/cf/cmd/cmd_firewalls_list.go:27:15: cannot use cli.BoolFlag literal (type cli.BoolFlag) as type cli.Flag in array or slice literal:
        cli.BoolFlag does not implement cli.Flag (Apply method has pointer receiver)
go/src/github.com/crackcomm/cloudflare/cf/cmd/cmd_firewalls_list.go:27:15: too many errors

(That is on Ubuntu 18.04's ancient Go 1.10) (I probably need to try newer versions as well though)
Possibly related to this: https://github.com/urfave/cli/blob/master/docs/migrate-v1-to-v2.md (Which would be a library issue rather than a Go version one) Via this

Hey, thanks for the report but this software is no longer maintained since cloudflare created their own client.

Thanks. (The CLI tool from here was useful for doing bulk operations)
This seems to be their library: https://github.com/cloudflare/cloudflare-go/
This seems to be their CLI tool: https://github.com/cloudflare/cloudflare-go/tree/master/cmd/flarectl


suggestions.

Hello, after a simple test, I have a few suggestions.

You can directly drag in pictures as input. and put the processed images into output
Add specified resolution options. There is almost no difference between the size of the processed image and the size before processing.
Add a function similar to ADetailer. In some photos, the face will become very blurry after processing.
Add the function of changing black and white pictures to color, similar to ioclab/control_v1p_sd15_brightness
Hope it gets better and better

Yeah. I'll probably move it into the Extras tab instead in the future. But this is not a high priority for me right now...
Out of scope. Use something else for upscaling.
There is already a Face Restoration option though?
Out of scope. I merely ported the original repo. If it doesn't do what you want, I can't help you either.


provide a "option group", i.e. only one button/option is allowed to be enabled on single-click, all other options are disabled

We will just add a "Group Column" and this will be allow to have only one active command:

Adding a "*" at the beginning will make it as "Default":

implement without default "*"


IAM particles support

Are there plans to support IAM particles (i.e. role, policies, etc) as outlined by boto?

yes. we had it in our backlog. We will add to this sprint.


[DNS] Make DNS response authoritative

This sets the appropriate bit (AA) in the response header.

http://www-inf.int-evry.fr/~hennequi/CoursDNS/NOTES-COURS_eng/msg.html

There is no description about what is authorative server and it's purpose.
Any more sources?

The Non-Authoritative response indicates that the server which responded to the DNS query doesn't own the zone data.
The setup below will make DNSSeeder node respond with authoritative response to any queries for seeder.mainnet1.stratisplatform.com
Script settings
dnshostname=seeder.mainnet1.stratisplatform.com
dnsnameserver=mainnet1.stratisplatform.com
<EMAIL_ADDRESS>
DNS Settings
seeder.mainnet1.stratisplatform.com.    IN      NS      mainnet1.stratisplatform.com.
mainnet1.stratisplatform.com.           IN      A       <IP_ADDRESS>

There is no description about what is authorative server and it's purpose.
Any more sources?

That answer should be authoritative because the seed node at address mainnetseeder1.stratisplatform.com is managing zone file for mainnet1.stratisplatform.com
nslookup mainnet1.stratisplatform.com mainnetseeder1.stratisplatform.com

With the corrected DNS settings we shouldn't need this PR

AA Authoritative Answer : 1 bit, reply from authoritative (1) or from cache (0)

This sems to indicate the origiin of the data probably some cached interim server of the original server, I guess this is correct then to add the AA flag.

With the corrected DNS settings we shouldn't need this PR

You mean correctly configuring the dns server or the dns hosting?


delete branches after merging

There's still an old testing branch in this repo, even after merging #1
Go to the Settings tab for this repo
Click the "Automatically delete head branches" setting
This will keep you from having a million branches :)

That's cool, I just changed it so it should automatically delete branches now


Addon Info: Remove broken prop type sort (keep defined order)

Issue: Prop Types sort is fundamentally broken. Following conversation in Discord, resolution was to remove sort (rather than add fixed name-based sort).
What I did

Removed the broken sort for prop types in the PropTable component within the Info addon.
Prop Types will now display in the order they are defined.

How to test
Put prop types for a component in a given order. They will display in that order.
Is this testable with jest or storyshots?
Yes (not currently tested for; tests for the Info addon are minimal and need fleshing out)
Does this need a new example in the kitchen sink apps?
No
Does this need an update to the documentation?
No

I really don't feel like the failing tests are anything to do with my change. Anyone care to comment on that?

looks good, thanks!

@mordentware @danielduan someone of you had to update storyshots (npm test -- -u)


change UserService::in_database to not be recursive

From @rafatower
app/models/carto/user_service.rb
I don't think this should be done recursively
I think it should be sth like:
def in_database(options = {}, &block)
  connection = foobar(blahbalh)
  if options[:statement_timeout]
    connection.execute(%Q{SET timeout TO ...})
  end

  yield(connection)

  if options[:statement_timeout]
    connection.execute(%Q{SET timeout TO DEFAULT})
  end
end

also bear in mind that if there's no block then it is responsibiltiy of the caller to set the timeout back to the default. Actually I'd not set the timeout if there's no block. (legacy stuff, I know, maybe this deserves a ticket on its own).

Also the current code is faulty, if not called with a block looks like the custom statement_timeout would have no effect (due to the ensure resetting it before returning the connection object)
we must change so all calls using this are done using procs, and/or make explicit the set statement timeout from calling code (another line inside the proc)


dart analyser has terminated

Analyzer Feedback from IntelliJ
Version information

IDEA AI-192.7<IP_ADDRESS>41897
2.8.2
AI-192.7<IP_ADDRESS>41897, JRE 1.8.0_212-release-1586-b4-5784211x64 JetBrains s.r.o, OS Mac OS X(x86_64) v10.14.6, screens 1440x900

Exception
Dart analysis server, SDK version 2.8.2, server version 1.27.4, FATAL error: UnimplementedError: name is an instance of _OperatorName in endClassConstructor
#0      Driver._captureExceptions.errorFunction (package:analysis_server/src/server/driver.dart:720:7)
#1      _CustomZone.handleUncaughtError (dart:async/zone.dart:1059:19)
#2      _CustomZone.runGuarded (dart:async/zone.dart:981:7)
#3      _CustomZone.bindCallbackGuarded.<anonymous closure> (dart:async/zone.dart:1019:23)
#4      _microtaskLoop (dart:async/schedule_microtask.dart:43:21)
#5      _startMicrotaskLoop (dart:async/schedule_microtask.dart:52:5)
#6      _runPendingImmediateCallback (dart:isolate-patch/isolate_patch.dart:118:13)
#7      _Timer._runTimers (dart:isolate-patch/timer_impl.dart:405:11)
#8      _Timer._handleMessage (dart:isolate-patch/timer_impl.dart:429:5)
#9      _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:168:12)

For additional log information, please append the contents of
file:///private/var/folders/gd/xgkrz9vs5wzdb5s511bz8k840000gn/T/report.txt.

Thanks for reporting this issue! This was also caught by our fuzz tester. Please follow along at https://github.com/dart-lang/sdk/issues/39032.

Duplicate of #39032


Read DOM feature

Description of Code

The readContent function returns an object containing the read function. The user can access it by calling that method.
The read function does few things:

Returns attributes value if present in the html element
Extra feature: Also returns DOM element property like innerHTML, innerText, textContent reading the html elements but properties which return objects like style, dataset is considered invalid and  they are handled in attributes section if and only if they are added to html elements.
all is true, returns an array of html elements if attributes not specified ,if a valid attribute is specified returns the array of value of those attributes
The read function can take two parameters like read(selector,all) or three parameters read(selector,attribute,all)
Extra functions are written to validate attributes and properties
The thought process is all that ---> property is valid if it returns a string, if returns an object it is invalid
and all attributes are valid if there exists one and they are added to html elements.

Any feedbacks or suggestions are gladly accepted and do ask the working of code if there are any clarifications

Hey, @sinster2003, thanks for your efforts on this feature. I appreciate your approach, but there are a few aspects that could use improvement.
The wording might have been a bit misleading in my initial instructions. The goal is not only to retrieve a specific attribute of an element but to access all of its properties. For instance, you used getAttribute() to obtain a property or attribute of an element. While getAttribute('class') will return the class names of an element, getAttribute('className') will return null. Similarly, getAttribute() returns null for other values like style, innerHTML, etc. Instead of using getAttribute(), you should use this syntax: element[propertyName]. To maintain clarity, we can rename the parameter from attributeName to propertyName.
Regarding the attributeValidation function, we don't need it to be overly complex. The key point is to throw an error if element[propertyName] is undefined.
Additionally, it's a convention to prefix all private methods and variables with an underscore. Please remember to document your method in the DOCS file. Thank you!

@lindelwa122 ya I got your point will improve on these aspects

As an update, @lindelwa122 worked on the improvements, removed all the complexities of the code and property syntax is used... working on the documentation will edit the pull request soon.

@lindelwa122 got some branch conflicts will resolve soon for a PR


Contact us form design

Description
I have designed a contact us page. As asked me in discord I will be raise PR for the design of other pages as well . If you find good with this PR then please merge it....
Type of change

[x] New feature (non-breaking change which adds functionality)
[x] This change requires a documentation update

Explain the Testing instructions
Test Configuration:

Operating system: Windows
Version: 10
Text-editors used: Figma wireframe

Checklist:

[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] My changes generate no new warnings
[x] New and existing unit tests pass locally with my changes

ATTACH SCREEN-SHOTS

Description
I have designed a contact us page. As asked me in discord I will be raise PR for the design of other pages as well . If you find good with this PR then please merge it....
Type of change

[x]  New feature (non-breaking change which adds functionality)
[x]  This change requires a documentation update

Explain the Testing instructions
Test Configuration:

Operating system: Windows
Version: 10
Text-editors used: Figma wireframe

Checklist:

[x]  I have performed a self-review of my own code
[x]  I have commented my code, particularly in hard-to-understand areas
[x]  My changes generate no new warnings
[x]  New and existing unit tests pass locally with my changes

ATTACH SCREEN-SHOTS

@himanshu007-creator Please review. Thanks in advance

@RuchiGitHu, as I said in #114 we have discussed on a design for the homepage and the color scheme and overall design elements in this design don't match with the one's in that design.
@SAHU-01 it would be great if you work with @RuchiGitHu to provide her with the details of the homepage design (like, color scheme and typography etc.) so that she can create the "contact us" page with same design.

@RuchiGitHu, as I said in #114 we have discussed on a design for the homepage and the color scheme and overall design elements in this design don't match with the one's in that design.
@SAHU-01 it would be great if you work with @RuchiGitHu to provide her with the details of the homepage design (like, color scheme and typography etc.) so that she can create the "contact us" page with same design.

Ok, I will be glad to update my contact us page according to @SAHU-01 design.

good job @RuchiGitHu

@RuchiGitHu, as I said in #114 we have discussed on a design for the homepage and the color scheme and overall design elements in this design don't match with the one's in that design.
@SAHU-01 it would be great if you work with @RuchiGitHu to provide her with the details of the homepage design (like, color scheme and typography etc.) so that she can create the "contact us" page with same design.

@SAHU-01 please let me know about font, color scheme of your design so that I can design contact us design according to that.
Looking for your reply...

You may look into this Figma board for some background -
https://www.figma.com/proto/YzTe1JXho4W9DwcM2LLXRp/Untitled?node-id=16%3A34&frame-preset-name=Desktop&scaling=min-zoom&page-id=0%3A1

You may look into this Figma board for some background -
https://www.figma.com/proto/YzTe1JXho4W9DwcM2LLXRp/Untitled?node-id=16%3A34&frame-preset-name=Desktop&scaling=min-zoom&page-id=0%3A1

Please review @1502shivam-singh, @himanshu007-creator

You may look into this Figma board for some background -
https://www.figma.com/proto/YzTe1JXho4W9DwcM2LLXRp/Untitled?node-id=16%3A34&frame-preset-name=Desktop&scaling=min-zoom&page-id=0%3A1

Please review @1502shivam-singh, @himanshu007-creator

hi @ruchi, the design is good, but you can take this week, and show me the best thing possible, work on the layout. You can make it better. Align the field descriptions on one side. On left hand side, please use another picture. Next update on PR will be final. If not found satisfactory, will not be merged. Best of luck

I would like to collaborate with @RuchiGitHu

You may look into this Figma board for some background -
https://www.figma.com/proto/YzTe1JXho4W9DwcM2LLXRp/Untitled?node-id=16%3A34&frame-preset-name=Desktop&scaling=min-zoom&page-id=0%3A1

Please review @1502shivam-singh, @himanshu007-creator

hi @ruchi, the design is good, but you can take this week, and show me the best thing possible, work on the layout. You can make it better. Align the field descriptions on one side. On left hand side, please use another picture. Next update on PR will be final. If not found satisfactory, will not be merged. Best of luck

Please review @himanshu007-creator @1502shivam-singh, I have to tried to make it dynamic.

I would like to collaborate with @RuchiGitHu

Sorry, but my designs is already done. Even at the time of previous review my design was 80% completed and after review only some changes were required according to previous review.

I would like to collaborate with @RuchiGitHu

Sorry, but my designs is already done. Even at the time of previous review my design was 80% completed and after review only some changes were required according to previous review.

Kindly check for typos in your design !

I would like to collaborate with @RuchiGitHu

Sorry, but my designs is already done. Even at the time of previous review my design was 80% completed and after review only some changes were required according to previous review.

I do not have any issues with you getting the points without a collaboration but it will be good if can finalize the code. If you want, I can unassign myself. That is not an issue😅
Now that we didn't collab, your header gets mismatched with the requirements of project..

I would like to collaborate with @RuchiGitHu

Sorry, but my designs is already done. Even at the time of previous review my design was 80% completed and after review only some changes were required according to previous review.

I do not have any issues with you getting the points without a collaboration but it will be good if we can finalize the code. If you want, I can unassign myself. That is not an issue😅
Now that we didn't collab, your header gets mismatched with the requirements of project..

@1502shivam-singh @himanshu007-creator whole thing is depend on the mentors. They will decide what we have to do, @SnehaVeerakumar your point of view and my point of view is here, let them decide. looking forward to collaborate with you Sneha in other issues.

I would like to collaborate with @RuchiGitHu

Sorry, but my designs is already done. Even at the time of previous review my design was 80% completed and after review only some changes were required according to previous review.

I do not have any issues with you getting the points without a collaboration but it will be good if we can finalize the code. If you want, I can unassign myself. That is not an issue😅
Now that we didn't collab, your header gets mismatched with the requirements of project..

@1502shivam-singh @himanshu007-creator whole thing is depend on the mentors. They will decide what we have to do, @SnehaVeerakumar your point of view and my point of view is here, let them decide. looking forward to collaborate with you Sneha in other issues.

It is us who is going to work together. Admin and mentor accepted as we both are assigned to this issue. Do you not want to collaborate with me in this issue?

I would like to collaborate with @RuchiGitHu

Sorry, but my designs is already done. Even at the time of previous review my design was 80% completed and after review only some changes were required according to previous review.

I do not have any issues with you getting the points without a collaboration but it will be good if we can finalize the code. If you want, I can unassign myself. That is not an issue😅
Now that we didn't collab, your header gets mismatched with the requirements of project..

@1502shivam-singh @himanshu007-creator whole thing is depend on the mentors. They will decide what we have to do, @SnehaVeerakumar your point of view and my point of view is here, let them decide. looking forward to collaborate with you Sneha in other issues.

It is us who is going to work together. Admin and mentor accepted as we both are assigned to this issue. Do you not want to collaborate with me in this issue?

Apologies for this @SnehaVeerakumar, due to shortage of time now a days, I am not able to collaborate with anyone. I could collaborate with you for another issue....

@RuchiGitHu check #136 for reference on my below mentioned points (updated design for homepage),
Some points of discussion -

Revisit #136 for navbar design, update your design's navbar according to that.
Match up letter-spacing and font face in your design with the one in #136
Aim for a minimalistic design, currently the design looks to crowded with all those big "Reach out to us" images. Check out some minimalistic contact form designs for inspiration. check these
Align the field names in the contact form to the left rather than right.
Watch out for typos in your design (Massage->Message)
No need for drop-shadow in "Contact us" title, but even if you want to add it try positioning the drop shadow in a more visually appealing way. Maybe you can try drop shadow on the rectangular field's for a nice elevation effect, though I am not absolutely sure whether if this would look good, so, optional for now.

And @rohank2502 do check the background of the PR and discuss before approving, there are still some points to cover.

@RuchiGitHu check #136 for reference on my below mentioned points (updated design for homepage),
Some points of discussion -

Revisit #136 for navbar design, update your design's navbar according to that.
Match up letter-spacing and font face in your design with the one in #136
Aim for a minimalistic design, currently the design looks to crowded with all those big "Reach out to us" images. Check out some minimalistic contact form designs for inspiration. check these
Align the field names in the contact form to the left rather than right.
Watch out for typos in your design (Massage->Message)
No need for drop-shadow in "Contact us" title, but even if you want to add it try positioning the drop shadow in a more visually appealing way. Maybe you can try drop shadow on the rectangular field's for a nice elevation effect, though I am not absolutely sure whether if this would look good, so, optional for now.

And @rohank2502 do check the background of the PR and discuss before approving, there are still some points to cover.

Yes I just said It is looking attractive

//cc @RuchiGitHu  sorry I could not respond earlier,as I was stuck up with another project,If you need any help or if the mentors want to assist her with the initial homepage colors and original designs I can do it, Let me know!!
From what I saw above the navbar on the initial page is a bit different, so I can provide you with the initial navbar design and those images used there.
And I don't know if I have the liberty to suggest the assigned person,but it would be great if you went through the original designs' footer section,I made a contact us there ,so rather than making two photocards we can one photocard, The frame below is just a suggestion for reference ,it's totally  your desicion Ruchi.

//cc @RuchiGitHu sorry I could not respond earlier,as I was stuck up with another project,If you need any help or if the mentors want to assist her with the initial homepage colors and original designs I can do it, Let me know!!
From what I saw above the navbar on the initial page is a bit different, so I can provide you with the initial navbar design and those images used there.
And I don't know if I have the liberty to suggest the assigned person,but it would be great if you went through the original designs' footer section,I made a contact us there ,so rather than making two photocards we can one photocard, The frame below is just a suggestion for reference ,it's totally your desicion Ruchi.

Thanks for your suggestion and for your referenced content. I will do as reviewed to me and will take care of your suggestion also in my mind while designing.
Thanks again to helping hands.....

@RuchiGitHu  Kindly wait before designing it. I don't want to waste your time. I have planned to make all the forms of this website to be neumorphic.
At last don't complaint that we have wasted your time.

@RuchiGitHu check #136 for reference on my below mentioned points (updated design for homepage),
Some points of discussion -

Revisit #136 for navbar design, update your design's navbar according to that.
Match up letter-spacing and font face in your design with the one in #136
Aim for a minimalistic design, currently the design looks to crowded with all those big "Reach out to us" images. Check out some minimalistic contact form designs for inspiration. check these
Align the field names in the contact form to the left rather than right.
Watch out for typos in your design (Massage->Message)
No need for drop-shadow in "Contact us" title, but even if you want to add it try positioning the drop shadow in a more visually appealing way. Maybe you can try drop shadow on the rectangular field's for a nice elevation effect, though I am not absolutely sure whether if this would look good, so, optional for now.

And @rohank2502 do check the background of the PR and discuss before approving, there are still some points to cover.

Yes I just said It is looking attractive

Please check @himanshu007-creator @1502shivam-singh, I have made changes according to that.

Allign "submit" properly
Remove the picture
Remove "Your"
Align everything to center
Make sure it works fine for dark mode.
@RuchiGitHu

Allign "submit" properly
Remove the picture
Remove "Your"
Align everything to center
Make sure it works fine for dark mode.
@RuchiGitHu

Please check @SnehaVeerakumar, thanks for your support...

Final remarks -

Match fonts of "message" with phone no. and others. Also, avoid using "Phone no.", write complete words.
Left align Submit button with the fields.
Remove those colons, no need
Watch for font uniformity or match up fonts that look good. This is for the "Contact Us" title. Either make it of the same font as email address and increase it size and apply some weight OR do the same thing but with different font.
Don't exaggerate the corner radii of the fields. Make it subtle. Similarly for the submit button.

For a better example, here's a example form I just designed in nimble time (Didn't hope I would need to do this, but anyway 😅)

Don't focus on colors, rest what I mentioned above, you can see in this.
This is most likely is final review, and after these issues are solved, @himanshu007-creator merge this.

Final remarks -

Match fonts of "message" with phone no. and others. Also, avoid using "Phone no.", write complete words.
Left align Submit button with the fields.
Remove those colons, no need
Watch for font uniformity or match up fonts that look good. This is for the "Contact Us" title. Either make it of the same font as email address and increase it size and apply some weight OR do the same thing but with different font.
Don't exaggerate the corner radii of the fields. Make it subtle. Similarly for the submit button.

For a better example, here's an example form I just designed in quick time (Didn't hope I would need to do this, but anyway 😅)

Don't focus on colors, rest what I mentioned above, you can see in this.
This is most likely is final review, and after these issues are solved, @himanshu007-creator merge this.

Thanks for your review @1502shivam-singh. I have made changes again to match requirements...

@RuchiGitHu  Great!, just do one last thing, create github pages and link this page to contact us button.
send the link here

@RuchiGitHu Great!, you wont be working on the coding part right?

Yes.


brew tap asks for git credentials

[x] ran brew update and can still reproduce the problem?
[x] ran brew doctor, fixed all issues and can still reproduce the problem?
[x] ran brew config and brew doctor and included their output with your issue?
[x] also ran brew update-reset

$ brew config

HOMEBREW_VERSION: 2.1.15-107-g5da322d
ORIGIN: https://github.com/Homebrew/brew
HEAD: 5da322d6be314e5f8b1729e91e60be743a1e7d8e
Last commit: 11 hours ago
Core tap ORIGIN: https://github.com/Homebrew/homebrew-core
Core tap HEAD: 8859bbe64cb9e735cd1ceb4efaf170eae5b21004
Core tap last commit: 22 minutes ago
HOMEBREW_PREFIX: /usr/local
HOMEBREW_DEV_CMD_RUN: 1
HOMEBREW_FORCE_BREWED_GIT: 1
HOMEBREW_GITHUB_API_TOKEN: set
HOMEBREW_NO_ANALYTICS: 1
HOMEBREW_VISUAL: nvim
CPU: octa-core 64-bit haswell
Homebrew Ruby: 2.6.3 => /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/bin/ruby
Clang: 11.0 build 1100
Git: 2.23.0 => /usr/local/opt/git/bin/git
Curl: 7.64.1 => /usr/bin/curl
Java: 1.8.0_222
macOS: 10.15.1-x86_64
CLT: 1<IP_ADDRESS>
Xcode: 11.2

$ brew doctor

Please note that these warnings are just used to help the Homebrew maintainers
with debugging if you file an issue. If everything you use Homebrew for is
working fine: please don't worry or file an issue; just ignore this. Thanks!

Warning: Putting non-prefixed coreutils in your path can cause gmp builds to fail.

What you were trying to do (and why)
brew tap dandavison/delta
What happened (include command output)
$ brew tap dandavison/delta
==> Tapping dandavison/delta
Cloning into '/usr/local/Homebrew/Library/Taps/dandavison/homebrew-delta'...
Username for 'https://github.com':

I'm already authenticated with Github using SSH
$ ssh -T<EMAIL_ADDRESS>Hi ahmedelgabri! You've successfully authenticated, but GitHub does not provide shell access.

And if I clone any repo using https it works fine without issues because credentials are cached in Keychain.
What you expected to happen
To be able to tap the formula
Step-by-step reproduction instructions (by running brew commands)
brew tap dandavison/delta

brew tap by default clones via HTTPS, not SSH. You will need to use the two-argument form to specify the e.g., git@github.com:... URL. See brew tap --help for details.

brew tap by default clones via HTTPS, not SSH. You will need to use the two-argument form to specify the e.g., git@github.com:... URL. See brew tap --help for details.

I mentioned already that cloning any http repo works fine. So, I dunno why is brew tap asking for my credentials?

I can't see https://github.com/dandavison/homebrew-delta, so I assume it's a private repository that you need to authenticate against.

This is the right URL https://github.com/dandavison/delta

$ brew tap --help
Usage: brew tap [options] user/repo [URL]

Tap a formula repository.

If no arguments are provided, list all installed taps.

With URL unspecified, tap a formula repository from GitHub using HTTPS. Since
so many taps are hosted on GitHub, this command is a shortcut for brew tap
user/repo https://github.com/user/homebrew-repo.

With URL specified, tap a formula repository from anywhere, using any
transport protocol that git(1) handles. The one-argument form of tap
simplifies but also limits. This two-argument command makes no assumptions, so
taps can be cloned from places other than GitHub and using protocols other than
HTTPS, e.g. SSH, GIT, HTTP, FTP(S), RSYNC.

With URL unspecified, tap a formula repository from GitHub using HTTPS. Since so many taps are hosted on GitHub, this command is a shortcut for brew tap user/repo https://github.com/user/homebrew-repo.

If you need further help: post on the Discourse forum.


HUB-813 Update dockerfiles to use GHCR

Travis failed with
toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit

🤦


Automatic Rotation = High CPU use?

Currently trying to implement automatic scene rotation in a react project.
My current approach is something like:
const loadAndRender = async () => {
  const url = "example.splat";
  await SPLAT.Loader.LoadAsync(url, scene, () => {});

  const animate = () => {
    for (let i = 0; i < scene.objects.length; i++) {
      scene.objects[i].rotation = <incremented_rotation>;
      scene.objects[i].update();
    }

    camera.update();
    renderer.render(scene, camera);
    requestAnimationFrame(animate);
  };

  animate();
};

loadAndRender();

But this seems to take an unyieldy amount of CPU. I imagine it would be more principled to use OrbitControls and increment the alpha/beta over time, but this doesn't seem to be a supported approach.
Is there a more standard way of doing this that I am not seeing? I found some old PRs/issues, but doesn't seem anything ever came of them.

Don't call update.
The update function applies the rotation to each gaussian on the CPU, which is useful for if you need to export a model with the rotation applied. For live animations just remove that line and your CPU usage will decrease significantly.


Devsre 151

Adding terraform 1.5.7 and 1.6.4

Updated and tested,
note stderr: rosetta error: due to M1 arm64.
`Linting Dockerfile...
Lint Successful!
Building images with AWS_CLI_VERSION=2.14.5 and TERRAFORM_VERSION=1.5.7...
Image successfully builded!
Generating test config with AWS_CLI_VERSION=2.14.5 and TERRAFORM_VERSION=1.5.7...
Test config successfully generated!
Executing container structure test...
==================================
====== Test file: tests.yml ======
=== RUN: Command Test: Check Git version
--- PASS
duration: 229.766625ms
stdout: git version 2.39.2
=== RUN: Command Test: Check JQ version
--- PASS
duration: 196.53625ms
stdout: jq-1.6
=== RUN: Command Test: Check OpenSSH client version
--- PASS
duration: 223.969791ms
stderr: OpenSSH_9.2p1 Debian-2+deb12u1, OpenSSL 3.0.11 19 Sep 2023
=== RUN: Command Test: Check Terraform CLI version
--- PASS
duration: 1.454684959s
stdout: Terraform v1.5.7
on linux_arm64
Your version of Terraform is out of date! The latest version
is 1.6.5. You can update by downloading from https://www.terraform.io/downloads.html
=== RUN: Command Test: Check AWS CLI version
--- FAIL
duration: 202.926416ms
stderr: rosetta error: failed to open elf at /lib64/ld-linux-x86-64.so.2
Error: Expected string 'aws-cli/2.14.5' not found in output ''
Error: Test 'Check AWS CLI version' exited with incorrect error code. Expected: 0, Actual: 133
=== RUN: File Existence Test: Check non-root user home
--- PASS
duration: 0s
=== RUN: File Existence Test: Check non-root user rights on /workspace folder
--- PASS
duration: 0s
=== RUN: Metadata Test
--- PASS
duration: 0s
===================================
============= RESULTS =============
Passes:      7
Failures:    1
Duration:    2.307884041s
Total tests: 8
FAIL`


logger for the forwarding handler

I added a logger for logging all binary related data from the forwarding handler.
A general problem I currently see with the handlers, is that is difficult to assemble related data. E.g. the HTTP request and response data is logged with a different method than the HTTP event having the metadata. I have used the same pattern for the forwarding logger, but how would the data merged again together to have a PCAP file in wireshark?

Thanks @koh-osug ! PR looks good to me.


If using adb push on Quest 2, conf.lua doesn't get read

Here's a sample conf.lua that doesn't get read:
function lovr.conf(t)
    t.headset.supersample = 0.015625
    t.headset.msaa = 1
    t.modules.graphics = false
end

(Workaround: conf.lua does get read by lodr.)

Another way to phrase this is that currently conf.lua can not be located in the save directory, since lovr.boot loads and runs the file before lovr.filesystem.setIdentity is called.  The identity normally comes from lovr.conf, so we have to do things in that order.
On Android though, the identity can not be changed and is always the package name.  So maybe that means Android can work different and mount the save directory earlier than other platforms.  It's a bit annoying to have special cases like that.
It's also good to consider if there are any "security" issues with allowing conf.lua to exist in the save folder.

Maybe allow sourcing of conf.lua from the save directory when the apk is marked as debuggable?  (LÖVR APKs are debuggable by default, so this would basically allow adb push'd conf.luas to always work -- but still give people the option to prevent conf.lua from being tampered with in a release build).


feat(bench): Make it easier to profile benchmarks

These are practices I pulled over from toml_edit when working on the performance regression caused by winnow-rs/winnow#98.  Feel free to pick and choose what you want from this.

Thanks. I read your recent blog post about testing, but I'm still not sure how this can help with profiling. Is it because you avoid the libtest/criterion layer here?

I see, thanks for the clarification!

@epage This has been sitting here for almost a year now because I was hesitant for a while and then I simply forgot about it. It's conflicted now. If you can spare some of your valueable time to rebase it, I'd be happy to merge it. :)

Eh, haven't had a need in this for a while


apply_along_axis infers output shape improperly

My environment:
Python: 3.6.6 |Anaconda custom (64-bit)
Dask: 0.18.1
This fails:
import dask.array as da
def testfun(v):
    return v[0] + v[1]
dar = da.random.randint(0,1, size=(2,2), chunks=('auto'))
da.apply_along_axis(testfun, 0, dar)

---------------------------------------------------------------------------
IndexError                                Traceback (most recent call last)
<ipython-input-2-43967c9b007c> in <module>
      3     return v[0] + v[1]
      4 dar = da.random.randint(0,1, size=(2,2), chunks=('auto'))
----> 5 da.apply_along_axis(testfun, 0, dar)

~/sandbox/dask/dask/array/routines.py in apply_along_axis(func1d, axis, arr, *args, **kwargs)
    321     # Test out some data with the function.
    322     test_data = np.ones((1,), dtype=arr.dtype)
--> 323     test_result = np.array(func1d(test_data, *args, **kwargs))
    324
    325     # Rechunk so that func1d is applied over the full axis.

<ipython-input-2-43967c9b007c> in testfun(v)
      1 import dask.array as da
      2 def testfun(v):
----> 3     return v[0] + v[1]
      4 dar = da.random.randint(0,1, size=(2,2), chunks=('auto'))
      5 da.apply_along_axis(testfun, 0, dar)

IndexError: index 1 is out of bounds for axis 0 with size 1

The reason why is because of this line in apply_along_axis, where the function arg in apply_along_axis is applied to non-representative test data (np.ones((1,))) for estimating output dimensionality and dtype.
At the least, the properties of the output being inferred here (shape and dtype) should be specifiable as kwargs to apply_along_axis so the user can dodge having them inferred.
If these properties are going to be inferred, the sample data fed into the test function should at least match the size (and probably the dtype) of the vectors the user wants to feed apply_along_axis .
If I have the time I can study how this is done for comparable functions (map_blocks comes to mind) and submit a PR, but I may not have the time soon.

apply_along_axis is decorated with @wraps(np.apply_along_axis), so it gets its docstring from np.apply_along_axis. Therefore dask-specific kwargs (like dtype and shape) can't be added to this function with a docstring.
Given this constraint, it seems reasonable to make a better inference of output shape and dtype by calling the test function on a more representative vector.

My apologies for the lack of response here (it's a busy week).  Removing the @wraps from any function is always a possibility.

I should mention that I'm working on a PR to add the shape and dtype kwargs to apply_along_axis

So it appears this issue wasn't resolved by the merged PR, correct? As such going to go ahead and reopen this. Though it appears there is another PR that attempts to address this issue, so we can keep the discussion over there and close this out when it is done.

For reference, in https://github.com/dask/dask/pull/3731 is was decided that the best approach here is to add keywords to apply_along_axis to specify the shape and dtype of the output.


[poco] Features for all poco components

Is your feature request related to a problem? Please describe.
I'm porting a legacy build system to vcpkg.
The legacy build system disables all but a few poco components as we don't need them.
This improves build times and helps with e.g. regulatory compliance.
Proposed solution
Add vcpkg features for poco components that are currently always enabled by vcpkg, e.g. Encodings, Xml, Json etc.
Having such features will allow us to disable the components we don't use.
Describe alternatives you've considered
We could build the components we don't need.
Undesirable for compliance reasons.
We could write an overlay port.
Undesirable as it means maintaining a separate port file.
We currently copy only the shared objects we need when packaging the binary, but this is less auditable than vcpkg features and doesn't improve build times.
Additional context
I looked at submitting a PR - adding a feature for each component listed in the portfile, and setting those options accordingly, seems easy enough, but I'm not sure:

how to identify interdependencies (e.g. the existing netssl feature depends on crypto)
how vcpkg tends to handle them.

In vpckg, we define additional components as features. If we do not actively call them during the installation process, we will not compile additional components, but only compile poco.

More options:

You disable the undesired components via options supplied in per-port customization in a custom triplet file.
You contribute the desired port features to control the package features you don't want.
Note that vcpkg CI will only test one representative feature set (default features plus requested dependencies).

In vpckg, we define additional components as features. If we do not actively call them during the installation process, we will not compile additional components, but only compile poco.

These are all components that make up the Poco library - see e.g. https://docs.pocoproject.org/current/00100-GuidedTour.html. If you consider "additional components" to be "optional components that may not be needed", then there are lots of additional components unconditionally compiled by the vcpkg port:
https://github.com/microsoft/vcpkg/blob/79a6c094989d1952da01a7bc3abf30198f8da860/ports/poco/portfile.cmake#L52-L82
e.g. the JSON component is always enabled even though it's not a core Poco component.