[lightbeam] panic due to panic! in microwasm.rs (line 294)

Issue description
wasmtime with lightbeam backend panic due to a call to panic!. This issue will make program calling lightbeam as 3rd party library to crash. Instead an error should be through to let the caller handle it properly.
Reproduction
wasmtime commit: 2109935fef6e0297b96b4d67a52e525290faad0b
Compilation with debug info:
$ RUSTFLAGS=-g cargo build --release --features lightbeam

Download & run testcase:
panic_unsupported_func_type.zip
$ unzip panic_unsupported_func_type.zip
$ ./target/release/wasmtime --lightbeam panic_unsupported_func_type.wasm
thread 'main' panicked at 'unsupported func type', crates/lightbeam/src/microwasm.rs:294:52
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace.

Related piece of code
Panic occurs because of the call to the macro panic!.
https://github.com/bytecodealliance/wasmtime/blob/2109935fef6e0297b96b4d67a52e525290faad0b/crates/lightbeam/src/microwasm.rs#L291-L296
Fix proposal
After applying the pull request 652, wasmtime will return:
$ ./target/release/wasmtime --lightbeam panic_unsupported_func_type.wasm
Error: failed to process main module `panic_unsupported_func_type.wasm`

Caused by:
    0: WebAssembly failed to compile
    1: Compilation error: Failed to translate function: Microwasm error: Unsupported func type

@fitzgen, you can add the fuzz tag for this one as well if you want.
Fixed/merged in master here:
https://github.com/bytecodealliance/wasmtime/commit/027f6117d6dc032855ae7f5278a77d6a36d1c4ec


[IMPROVEMENT] Update sizes in Engine and Volume resources less frequently

Is your improvement request related to a feature? Please describe (👍 if you like this request)
Per the investigation in https://github.com/longhorn/website/pull/875/files, an individual Engine or Volume under constant write I/O may cause the creation of millions of etcd revisions in a matter of months due to changes in its used space. While it is important to keep these size values updated, it may not be necessary to track them quite so closely.
The user who prompted the investigation reported seeing regular etcd defragmentations as a result. While defragmentations aren't generally problematic, they temporarily reduce etcd cluster availability and are better avoided when possible.
Describe the solution you'd like
The node controller already truncates the usable storage it reports to the nearest 100 MiB. This prevents it from prompting a Node resource update (and etcd revision) when the change is relatively small.
It looks like we can do the same thing for Engine and Volume space consumption (which is already potentially updated much more frequently than Node space anyway). 100 MiB is likely not the right value for truncation since these objects only consider a single volume and not an entire node, but some smaller value probably makes sense.
Describe alternatives you've considered
We could do nothing. The user did not report actual problems in their cluster as a result of the defragmentation, so this is a minor optimization.

We might need to modify the e2e test to have bigger write to observe the size change if we truncates the usable storage it reports to the nearest 100 MiB

The current plan is to change the approach used and create a new PR. See https://github.com/longhorn/longhorn-manager/pull/2817#issuecomment-2140632472 for details.

Verified pass on longhorn master(longhorn-manager 2f4628) with test steps

Write 1 MiB/s to longhorn volume, the enging controller will update size every 30 sec. following the value of sizeUpdateLimit
Write 12 MiB/s to longhorn volume, the enging controller will update size about every 5 secs.


Support all datatypes

Switch the display value of the reference that is appended to the questionnaire based upon the resource type of the incoming FHIR resource.
Within the mCODE IG, most resource types that we could expect to be passed in from the CQL will have a CodeableConcept type within its .code attribute. The exceptions are that a Specimen will have a CodeableConcept within its .type attribute, and a MedicationStatement will have a CodeableConcept within its .medicationCodeableConcept attribute.
I also increased functionality so that the display value can either come from the text attribute of the Codeable Concept, or from the display value within the Coding of the Codeable Concept (in the mCODE IG these are the same value, but neither of them are required so I figured I would check for both). If none are present, the display value defaults to the reference.

Is this properly rebased?

Is this properly rebased?

I just merged locally and pushed back up. It looks like it now incorporates all of the recent changes.

After rebase - the PR is good and the functionality works as intended.


Cannot build workspace with proc-macro lib as member

Describe the bug

I have a workspace containing a few binary, library and one proc-macro crate. However, when I want to build any package or use nix flake check, I get a weird build error:
       > error: `proc-macro` crate types currently cannot export any items other than functions tagged with `#[proc_macro]`, `#[proc_macro_derive]`, or `#[proc_macro_attribute]`
       >   --> core/macros/src/lib.rs:14:1
       >    |
       > 14 | pub fn main() {}
       >    | ^^^^^^^^^^^^^
       >
       > error: could not compile `macros` (lib) due to 1 previous error
       > warning: build failed, waiting for other jobs to finish...
       For full logs, run 'nix-store -l /nix/store/ymbh5xqg7z4cbiprgvs2i93fw93k27r7-cargo-package-deps-0.0.1.drv'.

Which is bogus, because the library does not include a pub fn main() {} at line 14.
Reproduction
I used the example init flake from your documentation (https://crane.dev/examples/quick-start-workspace.html) and replaced my-cli and my-server with my own binary crates from the workspace. Everything else is as it is in the example.
I traced down the error and found what was causing it. By looking at the derivation, I searched for the code inside the nix-store, that is used for the compilation:
nix show-derivation /nix/store/ymbh5xqg7z4cbiprgvs2i93fw93k27r7-cargo-package-deps-0.0.1.drv

This gave me quite a lot of output. Under the key "env/src" I found the link to the src repository:
"env":
     ...
     "src": "/nix/store/knwb69fg1gqwhlrz4zbn23pv187za27m-source",

And inside /nix/store/knwb69fg1gqwhlrz4zbn23pv187za27m-source I found the basic directory structure of my workspace, but the Code has been replaced with a dummy implementation (which seems to be something that crane does, although I don't know why or how I could influence this behaviour).
Here is the code of the proc-macro library that is causing the compilation error:
#![allow(clippy::all)]
#![allow(dead_code)]
#![cfg_attr(any(target_os = "none", target_os = "uefi"), no_std)]
#![cfg_attr(any(target_os = "none", target_os = "uefi"), no_main)]

#[allow(unused_extern_crates)]
extern crate core;

#[cfg_attr(any(target_os = "none", target_os = "uefi"), panic_handler)]
fn panic(_info: &::core::panic::PanicInfo<'_>) -> ! {
    loop {}
}

pub fn main() {}

And there we have the culprit - pub fn main() {} in line 14.
It seems to me, that this is the default dummy implementation that you guys use for everything. All other library crates had their  lib.rs content replaced with the same code above. For normal libraries it does not seem to be a problem that there is a main function defined though.

Hi @dsxmachina thanks for the report! Yes it does seem like there is something going wrong with the dummification, perhaps we have to treat proc-macro crates differently...
Do you have a(n ideally) minimal reproduction I can take a look at?
I tried to come up with a trivial proc-macro crate myself, but it built just fine (though now that I notice it, cleaning Cargo.tomls is stripping out lib.proc-macro = true which might be a separate bug) :thinking:

The proc-macro crate itself as a flake works fine, this seems only to be an issue with workspaces.
I created a small repo to reproduce the bug: https://github.com/dsxmachina/crane-bug-test
Hope this helps.

Ah thank you for the example, I found the issue! Apparently cargo accepts both lib.proc-macro = true and lib.proc_macro = true (even though the docs only describe the - variant). We're currently only stripping the - version but not the _. Will have this fixed up in a bit!


Bucket and Post should be on Same Line

the Bucket appears on Line 1 and then the post appears on Line 2 but indented as far in as the bucket. Can they start on the same line?

This should be ready to be deployed.


CAMEL-12519 add treeList option and the given PDU which has child ele…

…ments will be resulted as list or will be added to list

@onderson go for it


How to get token?

Please tell how to get token on Readme.md

You can copy fetch requests sent from the official Discord Client in the network, or get them from localStorage with the name of "token".


系统还原时候因为wsl的原因导致access denied

windows官方的说明:https://learn.microsoft.com/en-US/troubleshoot/windows-client/deployment/dism-apply-image-command-fails-error-code-5
似乎可以通过备份或者还原时添加exception来规避，请问是否可以添加exception选项

请问 exception选项是什么？能具体的说明吗？你给你URL里微软哪里说了真正的解决方案？

请问 exception选项是什么？能具体的说明吗？你给你URL里微软哪里说了真正的解决方案？

比如这篇文章里说的？
https://www.interfacett.com/blogs/windows-image-file-exclusions/
By default DISM will exclude the following file sets:
$ntfs.log\hiberfil.sys\pagefile.sys\swapfile.sys”\System Volume Information”\RECYCLER\Windows\CSC DISM also offers the option of creating a custom Exclusion and Exclusion Exception file, as long as it uses identical internal section headers and is saved as a .ini file. Any name or directory path may be applied using the /ConfigFile: argument. The  should incorporate the complete directory location and file name of the custom file, allowing the file to be located other than within directory containing the DISM command executable.

……
这个功能，设置，过滤文件就是了。
Get Outlook for Androidhttps://aka.ms/AAb9ysg

From: PatrickTscheng @.>
Sent: Monday, October 9, 2023 4:22:34 AM
To: Chuyu-Team/Dism-Multi-language @.>
Cc: mingkuang @.>; Comment @.>
Subject: Re: [Chuyu-Team/Dism-Multi-language] 系统还原时候因为wsl的原因导致access denied (Issue #1052)
请问 exception选项是什么？能具体的说明吗？你给你URL里微软哪里说了真正的解决方案？
比如这篇文章里说的？
https://www.interfacett.com/blogs/windows-image-file-exclusions/
By default DISM will exclude the following file sets:
$ntfs.log\hiberfil.sys\pagefile.sys\swapfile.sys”\System Volume Information”\RECYCLER\Windows\CSC DISM also offers the option of creating a custom Exclusion and Exclusion Exception file, as long as it uses identical internal section headers and is saved as a .ini file. Any name or directory path may be applied using the /ConfigFile: argument. The should incorporate the complete directory location and file name of the custom file, allowing the file to be located other than within directory containing the DISM command executable.
―
Reply to this email directly, view it on GitHubhttps://github.com/Chuyu-Team/Dism-Multi-language/issues/1052#issuecomment-1752153232, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AEX7GZJCTK7DO7GBM64XVEDX6MDQVAVCNFSM6AAAAAAWPWMFMGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONJSGE2TGMRTGI.
You are receiving this because you commented.Message ID: @.***>


md files show functions instead of code

The markdown files all refer to @functions instead of @code.

Closing as I believe this has already been addressed.


isotope with lazysizes doesn't work well

Hi im using isotope in my page and here is one part of the code:
$('.portfolio').isotope({
            itemSelector: '.portfolio-item',
            layoutMode: layoutMode
}).isotope('layout');

And the html part is :
   [named Part A, these images are not within the screen at the first sight]
   [named Part B, these images are not within the screen at the first sight either while they are not using isotope]

The problem is that when i visit the page it requests all the images rendered by isotope while the images
 should be requested when you scroll to Part A. And normally there is a ALL tab for isotope, hover no
 images displayed until you click ALL. The lazysizes works well for other images not using isotope. Im still
 looking into this while your help would be great appreciated. Please ask me if anything not clear, thanks.

Here is a codepen that demonstrates isotope in conjunction with lazySizes and here is another one with lazySizes and mixitup.

Hi aFarkas, i found the problem, thank you. By the way, is the 'async=""' a must in the script tag?

Hi aFarkas ,  i found the problem, thank u :)

What the answer? I'm having the same issue I believe.
Thanks.

Hi Kracheads, it's a long time since i got the problem, so im afraid i can't remember the details how i
solved problem. But i would like to share some key parts of the code which maybe give some hints for you. If problem still exists, paster your code here and we can give a further discuss.
[code]
initCases: function () {
if ($('.portfolio').length) {
var layoutMode = 'masonry';
if ($('.portfolio-4-columns').length) {
layoutMode = 'fitRows';
}
var $portfolio = $('.portfolio').imagesLoaded(function () {
$portfolio.isotope({
itemSelector: '.portfolio-item',
layoutMode: layoutMode,
filter:'*'
}).isotope('layout');
});
$('.filter').on('click', 'button', function () {
var filterValue = $(this).attr('data-filter');
$portfolio.isotope({filter: filterValue});
                $('.filter .selected').removeClass('selected');
                $(this).addClass('selected');
            });
            $('button[class=selected]').trigger('click');
        }
    },

[/code]


Websockets : 1006 Connection dropped by remote peer on chrome

Client Code:
<script>
            window.addEventListener("load",function(evt) {
                var chatbox = document.getElementById("chatbox");
                var send = document.getElementById("send");
                var chathistory = document.getElementById("chathistory");
                var socket = new WebSocket("ws://<IP_ADDRESS>:8000/wp",null);
                socket.addEventListener("open",function(evt) {
                    alert(JSON.stringify(evt));
                });
                socket.addEventListener("message",function(evt) {
                    chathistory.innerHTML += evt.data;
                    /*var msgType = jsonMsg['msgType'];
                    switch(msgType) {
                        case 'connectionstatus':
                            updatePlayerConnectionStatus(jsonMsg['payload']);
                            break;
                        case 'chatmsg':
                            updateChat(jsonMsg['payload']);
                            break;
                        case 'scoreupdate':
                            updateScores(jsonMsg['payload']);
                            break;
                    }*/
                });

                send.addEventListener("click",function(evt) {
                    socket.send(chatbox.value);
                    chatbox.value = "";
                });
            });
        </script>

Server:
var server = http.createServer(function(req,res) {
...
...
}
server.listen(8000);
sessionmgr.sessiongc();
var cons= []
wsServer = new websockserver({
    httpServer: server,
    autoAcceptConnections: false
});
wsServer.on('request', function (req) {
    //console.log(req);
    //accept directly because authenticity of request's origin already established
    var con = req.accept(null, req.origin);
    cons.push(con);
    console.log(cons.length);
    console.log('connection accepted req origin = '+req.origin);
    con.on('message', function(msg) {
        if(msg.type === 'utf8') {
            console.log('Message:='+msg.utf8Data);
            con.sendUTF('Hello'+" "+msg);
        }
        else if(msg.type === 'binary') {
            console.log('Message:='+msg.binary);
            con.sendBytes(msg.binaryData);
        }
    });

    con.on('close',function(reasonCode, description) {
        console.log(con.remoteAddress +'disconnected :: '+reasonCode+" "+description);
    });
});

Firefox Works fine. Chrome errors out.
Chrome Error Message:
WebSocket connection to 'ws://<IP_ADDRESS>:8000/wp' failed: Error during WebSocket handshake: Sent non-empty 'Sec-WebSocket-Protocol' header but no response was received

Chrome apparently handshakes differently, I guess, than Firefox and Node WebSocket Server is not handshaking with Chrome the way chrome wants ?
Any ideas on fixing for this ?

anyone ? really wished my app would work on chrome ...

Try using something other than null for your subprotocol.

@anupamkumar what exactly are you trying to achieve with a null valued protocol field? Are you saying I am NOT negotiating for a subprotocol or are you saying I am negotiating for the null subprotocol?
In the former case, leave the field out. In the latter case, choose something other than null like @theturtle32  suggests.
FYI both Chrome and Firefox generate a "Sec-WebSocket-Protocol:null" request header. However the node server leaves out that header in its response. Chrome interprets this as meaning that the server does not agree to serve with the specified protocol while Firefox does not seem to care.
The standard is not totally clear as to the server behavior when the Sec-WebSocket-Protocol request header is null. The part that is however is that if Sec-WebSocket-Protocol is present in a request and the server does not agree with any of the string values of the header then it does not include that header in its response. So to me Chrome behaves correctly and both Chrome and Firefox should not include a Sec-WebSocket-Protocol in the request if the specified value is null.
In summary, stay away from a null valued Sec-WebSocket-Protocol.

@theturtle32 , @braytak thanks for clearing this up. I asked this at stackoverflow too, but no one was able to explain it.
It makes sense now.


Implements Migration Based Approach

Task linked: CU-3ggurum Deploy Backend up to Production Build & Switch to Migration Based Approach


Circular Viewer: label for custom tracks

When I create custom feature tracks using keywords, those tracks are labeled as Custom Track 1, Custom track 2, etc, which is not very informative as legends. However, when I mouseover . on those labels, I get more detail about the keywords used in the tooltip.
For the tracks used using Keywords, we should use keywords as the track labels.
-Maulik

Is it better to provide an input text box "track name"  in "Add custom tracks" and "Upload your own data" to allow users to name their tracks?


Fix Helm chart.

Previously, CRDs were always installed, since there was no conditional.
Also adds missing default values to values.yaml and conditionally passed flags for specified durations.
Analogous to https://github.com/openebs/mayastor/pull/1106.

Hey @reitermarkus.
Some background information - the helm charts we're not yet "exposing" for direct consumption yet. For historical reasons, we've got a script on each repo that generates yamls based on the helm chart and some chosen parameters, eg tags and profiles.

We use conventional commits, do you mind changing your commits? eg: fix(helm): this and that

the helm charts we're not yet "exposing" for direct consumption yet

I am aware, that's why I'm trying to push it past that “yet” point. 😉

@tiagolobocastro, I updated the generate-yamls.sh script to also generate the values.yaml file in addition to the files in deploy.

thanks @reitermarkus I'll have a play with the chart tomorrow :+1:

I get an error running the generate-yaml script:
❯ ./scripts/deploy/generate-yamls.sh develop                                                                                ─╯ /nix/store/jgj50jymin33k7v1vzsl6njmah91nx1x-python3.9-yq-2.13.0/bin/yq usage: yq [-h] [--yaml-output] [--yaml-roundtrip] [--width WIDTH]           [--indentless-lists] [--in-place] [--version]           [jq_filter] [files ...] yq: error: argument files: can't open '. as $item ireduce ({}; . * $item )': [Errno 2] No such file or directory: '. as $item ireduce ({}; . * $item )'
Also, could you please add yq to the shell.nix buildInputs, and since you're there we're probably missing jq there as well, if you don't mind.

I added them.

/nix/store/jgj50jymin33k7v1vzsl6njmah91nx1x-python3.9-yq-2.13.0/bin/yq

I guess this (https://pypi.org/project/yq/) yq is not the same as https://mikefarah.gitbook.io/yq/.

I added them.

/nix/store/jgj50jymin33k7v1vzsl6njmah91nx1x-python3.9-yq-2.13.0/bin/yq

I guess this (https://pypi.org/project/yq/) yq is not the same as https://mikefarah.gitbook.io/yq/.
It should be the latter, v4.6.0+.

Ah... I'll have a look at nixpkgs to see if we can get that yq.

Sorry about the delay @reitermarkus, we've moved the chart to https://github.com/openebs/mayastor-extensions/tree/develop/chart.


Missing variable declaration

We are currently using this module and ran into an issue with this module where it seem to miss a variable declaration (missing var for matches) and pushes the variable to global scope (essentially global variable leak).
https://github.com/themikenicholson/passport-jwt/blob/master/lib/auth_header.js#L9

Merged #23  to fix


[BUG]:self-signed certificate in certificate chain

What version of drizzle-orm are you using?
0.28.6
What version of drizzle-kit are you using?
0.19.13
Describe the Bug
migrate: Error: self-signed certificate in certificate chain

I am using superbase+drizzle
with pool connection
Expected behavior
No response
Environment & setup
No response

not drizzle related + will need more context and repro example. If it's still an issue for you - feel free to create another ticket with more context, thanks!

I got this error on "drizzle-orm": "^0.31.2" and "drizzle-kit": "^0.22.6" on windows but not on "drizzle-orm": "^0.29.4" and "drizzle-kit": "^0.21.2"


Pagination daily code

PR Fixes:

Now can navigate to other pages from bottom of the page
Jump To ,Prev ,Next supported
Create new Pagination component to avoid code duplication

Resolves #[Issue Number if there]
#470
Checklist before requesting a review

[x] I have performed a self-review of my code
[x] I assure there is no similar/duplicate pull request regarding same issue

a good practice would be letting people know in the discussions that you are working on that issue .and also in pull request its a good practice to add images of the output of how the solution looks at the end . and thanks a lot for  contributing i wanted a feature like this so badly. thanks a lot @ShubhamGagare

I will make sure of this points in next one 🙂

Tested sirji, will be merging.
If this PR is suitable for a Bounty you will get it ASAP!


Loss for Training MS COCO

May I ask anyone to share what the loss curve looks like? I am using the COCO dataset, and the loss is around 2.3 (around 5,000 iterations already). Is this normal? I know COCO is a larger dataset than pascal and takes longer to converge. Thanks!

@jwyang would you please post your coco loss curve here? thank you.

@jwyang thank you so much for your amazing code. I was hoping you could share the voc and coco loss curves with me as well please, am wondering about convergence during training


Lint the code with pylama

As code in this repo is becoming more and more compliant with PEP8 it would be nice to use pylama to lint it - it's easy to configure Travis to run pylama on every PR and warn about style issues in PR changes. Existing and harder to resolve issues could be ignored in pylama configuration and resolved later.
To be done:

[ ] use pylint linter;
[ ] use mccabe linter;
[ ] use pycodestyle linter;
[ ] use pyflakes linter;
[ ] use pydocstyle linter;
[ ] configure Travis task;

Feel free to add a job on travis or circleci.com

I have made a pull request with simple pylama configuration (that will configure pylama with mccabe, pycodestyle and pyflakes linters). Next I'll figure out how to configure Travis (but I suppose you will have to enable travis builds yourself as a repo owner).

OK, I have also added a Travis configuration in #73. Could you enable build on Travis (it should hopefully detect this branch whenever there will be a new push)?

very good job, Thx!  I'll test it after work and do merge

Already merged

Could you reopen this? There is still pylint and pydocstyle to be enabled.
Have we checked that Travis CI runs pylama when pull request is made/updated?
Also, from now we shouldn't push directly to master (can we secure this branch from pushing and leave pull requests as the only way of updating this?).

ok, sorry : )

Yeah, check this out: https://travis-ci.org/igbt6/Packt-Publishing-Free-Learning

Thanks, Travis is configured indeed.


Definalize Amp\Socket\Server, or provide interfaces

Amp\Socket\Server was made final in release 1.0, which once again complicates my testing. I can no longer do $server->expects($this->exactly(1))->method('close');

Amp\Socket\SocketServer is now an interface in the upcoming v2 version.


BUG:header

Is there an existing issue for this?

[X] I have searched the existing issues

What went down?

Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

@aashkaaaaaa This issue is already there


Mesh UV Corruption when using SurfaceTool to copy mesh data

Godot version
4.2-beta3
System information
Windows 11, gl_compatibility, NVidia RTX 3070 TI
Issue description
I've been working on mesh combining scripts to "bake" multiple meshes into a single mesh for accelerated rendering on lower powered hardware. The technique used is fairly common in these sorts of scripts:

Create an empty ArrayMesh
Use SurfaceTool to copy source meshes (by surface)
Commit the SurfaceTool surface to the ArrayMesh

This technique works reliably on Godot 4.0 and 4.1; however it's now producing meshes with corrupt UV coordinates on Godot 4.2 if the mesh data comes from an imported mesh such as a glb file.
In the following screen-shot; the meshes in the back are the "source" meshes, and the meshes in the front are the "copies":

Steps to reproduce
A minimal reproducible project has been attached. To use it:

Open the project
Open main.tscn
Pick the "CopyGltfFile" node and click on the "Copy Mesh" boolean property to trigger mesh-cloning
Observe the duplicated mesh with corrupted UV coordinates - the mesh has been saved to "CopyGltfFile_export.mesh" for analysis
Replicate for the "CopyMeshFile" node and observe identical behavior
Replicate for the "CopyBuiltin" which uses a built-in BoxMesh and observe the UVs appear correct.

Minimal reproduction project
mesh_copy_bug.zip

I'm saving the good and bad meshes to tres files and I'm noticing a difference in the format attributes:

Good = "format":<PHONE_NUMBER>7, = 0x8_0000_1017
Bad = "format":<PHONE_NUMBER>9, = 0x8_2000_1017

My immediate concern is the "format" field is defined in the SurfaceData struct as being a uint32_t; and these values are roughly 10x the size of numbers that would fit in a 32-bit value. I'm wondering why bit 35 of a 32-bit number is set high.

cc @clayjohn

Even more fun - if I export the entire scene to gltf and load it in blender to take a closer look then the original "good" meshes show the same corruption:

As such this bug can probably be promoted to "Meshes are Broken" regardless of mesh combining/baking - it's visible in Blender on export, but only visible in Godot after mesh operations.

Tested with Master build from 93cdacbb0a30f12b2f3f5e8e06b90149deeb554b and it's fixed - both the mesh copying and the Blender export.


Authentication error, please check the SAS token during binary download

Describe the bug
fatal: [localhost]: FAILED! => {"changed": false, "msg": "Authentication error, please check the SAS token"}
To reproduce
Steps to reproduce the behavior:
Deploy region, library, workload zone and then download the binaries.
The error occurs during the ansible pipeline run playbook_bom_downloader.yaml
Expected behavior
A valid SAS token is available in the keyvault
Additional context
none

I was able to find a workaround by executing the update_sas_token.sh manually and providing the 3 variables inkl. the fist SAS-key of the storage account
azureadm@mgmtweeudep00deploy00:~/Azure_SAP_Automated_Deployment/WORKSPACES/BOMS$ ~/Azure_SAP_Automated_Deployment/sap-automation/deploy/scripts/update_sas_token.sh
Please provide the saplib storage account name (SAP_LIBRARY)? mgmtweeusaplib4a1
Please provide the saplib storage account account key (SAP_LIBRARY)? tXcxdh4JbgVYQe3u3uVh88Zu69pbsuxsBfGiXVV85iIEcTchPKw3yRGlTdelmb5KpAyy7N/m4KPurfD8ExYIRA==
Please provide the Deployer keyvault name? MGMTWEEUDEP00userE43

Hi @mimergel, thank you for raising the issue. This should be fixed as part of commit b40b4208f5fc827d423d7c4b637d50bece28f344. Kindly re-open the issue if the issue still persists.
Hi @enterprise-1701-d, thanks for suggesting the workaround. I removed your storage account accesskey from the comment.
🚨  Could you recycle your storage account access keys, please.

unfortunately I got the error again yesterday


In Emacs 25.x, the initial frame is automatically resized incorrectly

The height of the frame appears unchanged, but the final width of the frame is only a few lines, which is obviously nonoptimal.

Shockingly, this isn't actually caused by this config. I reproduces in emacs -Q.

So this looks like it was fixed sometime in the last month or so.

So this looks like it was fixed sometime in the last month or so.


add a function to allow for checking scrypt password hashes

This PR will expose crypto_pwhash_scryptsalsa208sha256_str_needs_rehash from libsodium for use by C# clients.

The appveyor integration is failing without a helpful message, anyone have an idea why?

I also have created a pull request, and I have the same problem. Does anybody know whether the repository is maintained by somebody now?


Feedback and bugs (mostly about Cloud)

Here's feedback and number of bugs I encountered while trying out evidently:
https://aguschin.notion.site/evidently-feedback-f1e932a60b6e46c1947f2df084f31e14?pvs=4.
It's in russian, try translating the page if necessary. Ping me if something is unclear.

Added another comment there. Please feel free to strikethrough issues/left comment there if that's easier for you to use it this way.


[Tab] Change the ripple color to follow the spec

The spec is at the very bottom of this page.

Noticed you're using all-caps for the const here, but (AFAIK?) none of the other consts in MUI are.
If we're going to change the code style, shouldn't do so consistently across library, and supported by an eslint rule?

I have removed the change regarding the const. I was going toward this rule http://eslint.org/docs/rules/no-magic-numbers. But that out of the scope of this PR.

Looks good! :+1:


content= argument for make_schema() and make_data()

To allow you to pass in a string of YAML in place of a file path.
Refs https://github.com/23andMe/Yamale/issues/104

I wonder if we can fix this error message:
yamale.validate(schema, data)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/Users/chrism/workspace/simonw/Yamale/yamale/yamale.py", line 49, in validate
    raise YamaleError(results)
yamale.yamale_error.YamaleError: Error validating data 'None' with 'None'
        age: '26a' is not a int.

Since there are no filenames, we get None for the data and schema. I think we have three cases:

No file for schema or data: Error validating data
No file for schema: Error validating data <filename>
No file for data: Error validating data with schema <filename>

I'm open to other phrasing too.

Good catch, I hadn't seen that. I like those three error messages.

OK, implemented those messages. Figuring out how to test it was a bit tricky but I'm happy with the solution I came up with: https://github.com/23andMe/Yamale/blob/ad676dbf9ad10bf7a827ba1c7027e90e10046f05/yamale/tests/test_functional.py#L325-L348

I think the rest looks great. We can merge this in after the last bit of message formatting. Thanks for contributing to Yamale!

Good catch, fixed.


redis_proxy: fix crash if catch_all_route is not defined

Commit Message: Fix proxy crash if catch_all_route is not defined
Additional Description: If an incoming redis key does not match against any of the prefix_routes that maybe defined, the proxy crashes if catch_all_route is not defined. This bug handles "no route" matching scenario.
Risk Level: Low
Testing: Unit test
Docs Changes:
Release Notes:
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue] https://github.com/envoyproxy/envoy/issues/29120
[Optional Fixes commit #PR or SHA] https://github.com/envoyproxy/envoy/pull/27902
[Optional Deprecated:]
[Optional API Considerations:]

@mattklein123 @weisisea - could you PTAL ? CC - @nickamorim

Looks like this needs a main merge.
/assign @mattklein123
/wait

hi @deveshkandpal1224 we had to revert this PR as it broke CI - im guessing the PR that landed immediately prior may have caused a bad merge - please do resubmit!

@phlax - will resubmit my changes.


Inconsistency between styled's implementation and types

Issue
The types allow for multiples arguments when styling a component. The following is correct based on the types.
const Component = styled('div')(
  { color: "blue" },
  (props) => ({ color: props.theme.palette.primary }),
  () => ({ color: "pink" }),
  // ...
);

We could expected that a textNode passed to Component would be pink, but with the current implementation the result is blue (the first argument).
It's due to the following lines:
https://github.com/solidjs/solid-styled-components/blob/dec99a0a51e1eaeb8783390291c09e4e436f046b/src/index.js#L47-L50
By looking at this code we could expected that the textNode would be blue. When we do the apply the second argument expected an array of arguments (see: apply doc). Here the args variable represents all the argument passed to style the div. It's like if we were doing the folowing:
// to simplify the `this` "assignment" isn't part of the example
css(
  { color: "blue" },
  (props) => ({ color: props.theme.palette.primary }),
  () => ({ color: "pink" }),
  // ...
);

The issue is that the css method from goober only take one argument. Everything after the first argument is ignored.
https://github.com/cristianbote/goober/blob/b2781bd9d76f5b386e50b5916216430f4532662c/src/css.js#L5-L9
/**
 * css entry
 * @param {String|Object|Function} val
 */
function css(val) {

Secondary issue: We could also take the time to improve the types, because currently there's no way to mark the theme prop as not optional an the as prop types should probably be ValidComponent instead of string | number | symbol | undefined

Proposed solution
Only tag function should be allowed to have multiple arguments
There's a way to make the tag function work while restricting regular function call to one argument. Based on what's happening in goober's css function, here's what the types could look like (without the generic type for the props):
import type { ValidComponent } from "solid-js";

type StylesGenerator = (props: {}) => CSSAttribute | string;
type StylesArg =
  | string
  | CSSAttribute
  | StylesGenerator
  | Array<CSSAttribute | StylesGenerator>;
type StylesFn = (styles: StylesArg) => Component
type TagStyleGenerator = (props: {}) => number | string | undefined;
type TagFn = (
  tag: TemplateStringsArray,
  ...args: Array<string | TagStyleGenerator>,
) => Component;

// This way we can both use a regular function call with
// one argument or a tag function with multiple arguments
type StylingFn = StylesFn & TagFn;

With these types the example at the beginning wouldn't be allowed and the types would fit the implementation.
Let me know what you think.

We can track the progress here: https://github.com/solidjs/solid-styled-components/pull/38

Also related to https://github.com/solidjs/solid-styled-components/issues/2

related issue: https://github.com/solidjs/solid-styled-components/issues/15


check and fail on duplicated defs

addresses #66

Sorry for leaving this dangling for so long. We'll want to take a different approach and support redefining vars in the future.


haiku: Add RLIMIT_STACK and fix RTLD_* definitions

This commit adds additional definitions for Haiku which fixes issues in building libc and backtrace-rs when cross-compiling Haiku using docker ci.

@bors: r+

:pushpin: Commit 353d645 has been approved by alexcrichton

:hourglass: Testing commit 353d64549df8ba8d789197d8f55bd12532c7ea16 with merge c8c3fb56ad3614724d901ca529a48101708d6105...

:sunny: Test successful - status-appveyor, status-travis
Approved by: alexcrichton
Pushing c8c3fb56ad3614724d901ca529a48101708d6105 to master...


Annotation Config doesn't specify the type

Expected Behavior

Actual Behavior
In the Docs related to the annotation in K8S is not clear which is the type of "dapr.io/config" if it is a string or array? in case of String how we can define multiple configurations?
Steps to Reproduce the Problem
go at page https://github.com/dapr/docs/tree/master/howto/configure-k8s
This is the current text for Config Annotation:

dapr.io/config
Tells Dapr which Configuration CRD to use

It's the name of the configuration instance.
An app can reference one config object.

Gotcha, but in this case each apllication need to have it own configuration, Could be interesting to enable an array of configurations, based on the fact that some apllications can share part of the configurations

Do you(@yaron2 ) think that can be interesting to add this feature as improvements in DAPR?

Yes, but we need to think through the design and user experience here.
/cc @msfussell


Rotation with mouse button

I am left-handed mouse user, so the mouse buttons are switched. (btw, consider using "main/secondary" in replace of "left/mouse" to describe the mouse buttons).
The instruction says that [Right mouse] for xy rotation and [Left mouse] for xz. In my case, it is the [Left mouse] button (the physical right button) controls rotations of all directions, and the [Right mouse] button (the physical left button) has no function at all.
Don't know if this is just me. I am using Linux Mint running Chrome. It'd be great if the 2nd button (the [Right mouse]) is set for panning like OpenCad does. In the current setting, the panning is set to either [Middle mouse](which doesn't work in my case, either 'cos it's the wheel in the middle and pushing in resulting in zooming) or Shift-[Left mouse], which works but needs both hands.

I submitted a patch that fixes right click dragging, so that Rotate XY works now.
I tested out the new rotation in the viewer for the first time (the alternative gesture of "Alt + Left click" is used to drag application windows on my Linux box, so it is unusable for rotation), and while it looks neat, it seems like something that would be used much less frequently than panning, if at all.
Also I have a touchpad on my laptop in which middle click + dragging emulates scrollwheel, so middle clicks drags are not possible to use for panning.
Shift + Left Mouse is the only panning option I can use, which is two handed as runsun mentioned.  I think switching Right Mouse to panning would be an improvement.

The standard mouse event has an indication of which button was pressed. This should standard should be followed. Also, the help should be changed as well to say 'main' and 'secondary' buttons.
https://developer.mozilla.org/en-US/docs/Web/API/MouseEvent/button
A number representing a given button:
0: Main button pressed, usually the left button or the un-initialized state
1: Auxiliary button pressed, usually the wheel button or themiddle button (if present)
2: Secondary button pressed, usually the right button
3: Fourth button, typically the Browser Back button
4: Fifth button, typically the Browser Forward button

For a mouse configured for left-handed use, the button actions are reversed. In this case, the values are read from right to left.

@runsun Can you try the current version of V1 JSCAD at www.openjscad.org ? I believe this has been fixed.
If so then please close.

@runsun Can you try the new version of V2 JSCAD at www.jscad.xyz ? I believe this issue has been fixed.


[Hotfix] the e2e exec error in win10, fix path separator

Purpose of this pull request
when run the e2e in win10 os,and docker in virtual-linux，it will error.
because the separate in win10 is // for paths.
besides the line feed of the start.sh must be \n in linux.
Check list

[ ] Code changed are covered with tests, or it does not need tests for reason:
[ ] If any new Jar binary package adding in your PR, please add License Notice according
New License Guide
[ ] If necessary, please update the documentation to describe the new feature. https://github.com/apache/incubator-seatunnel/tree/dev/docs

the lind feed is only in my os, I only need to fix in local

the lind feed is only in my os, I only need to fix in local

LGTM

close #2631


StatusCodeAndMessage test client sometimes receives "Received RST_STREAM err=8"

In the status_code_and_message interop test, after server-side handler correctly sets
StatusCode = Unknown and StatusDetail = "test status message",
client receives status code Unknown, but the message is sometimes set to "Received RST_STREAM err=8".
Test Failure : Grpc.IntegrationTesting.InteropClientServerTest.StatusCodeAndMessage
     Expected string length 19 but was 25. Strings differ at index 0.
  Expected: "test status message"
  But was:  "Received RST_STREAM err=8"

@murgatroid99 , have you seen a similar problem for Node?

Not that I can remember.

Same thing happends for UnimplementedMethod test.

node seems to have the same problem
https://grpc-testing.appspot.com/job/gRPC_interop_master/1614/testReport/junit/(root)/tests/cloud_to_cloud_node_csharp_server_status_code_and_message/

FYI @ctiller, this has been seen in both node & c#, so it looks more like a C core issue.

Reassigning to @murgatroid99 as I will be OOO for a while.

Seen again at https://grpc-testing.appspot.com/job/gRPC_interop_master/2172/testReport/junit/(root)/tests/cloud_to_cloud_csharp_csharp_server_unimplemented_method/

I am pretty sure this is a core bug. The bug is that this error is going on the wire, not that the libraries are reporting it.

https://grpc-testing.appspot.com/job/gRPC_interop_master/3143/testReport/junit/(root)/tests/cloud_to_cloud_node_csharp_server_status_code_and_message/

Similar thing happens for UnimplementedMethod interop test: https://grpc-testing.appspot.com/job/gRPC_interop_master/3133/testReport/junit/(root)/tests/cloud_to_cloud_csharp_csharp_server_unimplemented_method/

I will probably start looking into this.

Yang might be able to help (depending on load)
On Tue, Mar 1, 2016, 11:32 AM Jan Tattermusch<EMAIL_ADDRESS>wrote:

I will probably start looking into this.
—
Reply to this email directly or view it on GitHub
https://github.com/grpc/grpc/issues/4427#issuecomment-190866016.

https://http2.github.io/http2-spec/#ErrorCodes
CANCEL (0x8): Used by the endpoint to indicate that the stream is no longer needed.

How are C# and Node reporting the status to core? With a batch containing
send status, or with a call_cancel_with_status?
On Tue, Mar 1, 2016, 12:10 PM Jan Tattermusch<EMAIL_ADDRESS>wrote:

https://http2.github.io/http2-spec/#ErrorCodes
CANCEL (0x8): Used by the endpoint to indicate that the stream is no
longer needed.
—
Reply to this email directly or view it on GitHub
https://github.com/grpc/grpc/issues/4427#issuecomment-190881909.

I do e.g.
await responseStream.WriteStatusAsync(new Status(StatusCode.Unimplemented, ""), Metadata.Empty).ConfigureAwait(false);

I am actually invoking a "safety" call_cancel  in the serverside handler if the  "cancelled" flag is set when "recv_close_on_server" event is delivered. I recall this used to be necessary to correctly close the request stream if server wanted to just write the status and ignore all the requests.

It looks like the issue is caused by C# server  (that's why we were seeing it with both node and C# clients). My apologies for thinking it's a C core bug.
On the other hand, there might be a C core bug that is more subtle - it looks like if you concurrently try to perform write status and cancel operations, on the client side you'll some something in between - the status message "Received RST_STREAM err=8".

So that behavior is -kind of- expected: if a stream isn't fully closed, a
cancellation must put a RST_STREAM on the wire. There's no synchronization
mechanism that's low enough cost to allow anything other semantic (we don't
want to slow the write path to make allowances for cancellation). So... we
let the write status and the cancellation race down to the transport level,
and see which one arrives first to decide what we should do.
On Tue, Mar 1, 2016 at 2:30 PM Jan Tattermusch<EMAIL_ADDRESS>wrote:

It looks like the issue is caused by C# server (that's why we were seeing
it with both node and C# clients). My apologies for thinking it's a C core
bug.
On the other hand, there might be a C core bug that is more subtle - it
looks like if you concurrently try to perform write status and cancel
operations, on the client side you'll some something in between - the
status message "Received RST_STREAM err=8".
—
Reply to this email directly or view it on GitHub
https://github.com/grpc/grpc/issues/4427#issuecomment-190935579.

Hi,
I'm getting similar error message from golang (server and client) as well:
```error code = 13 - stream terminated by RST_STREAM with error code: 1````
Any advise?
Thanks,


Drop empty sections from python docs

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


Fastmail OAUTH2: unable to configure

Checklist

[X] I have used the search function to see if someone else has already submitted the same bug report.
[X] I will describe the problem with as much detail as possible.

App
Thunderbird for Android
App version
8.0b3
Where did you get the app from?
Google Play
Android version
Android 14
Device model
Pixel 6a
Steps to reproduce

Settings
Choose my Fastmail account
Fetching mail
Incoming Server
Change Authentication from Normal Password to OAUTH2
Next
Please sign in ... Sign in
OAuth sign in failed.  Oauth 2.0 is currently not supported with this provider

Expected behavior
I have OAUTH2 in Thunderbird desktop configured.  I know it works.
Their server is mail.messagingengine.com
My username is my core account, and is using one of their other domains they own, not the same as their server.
I'd like to migrate off of my application password to OAUTH2.
This also occurs in K-9.
Actual behavior
OAuth sign in failed
OAuth 2.0 is currently not supported with this provider
Retry
Logs
No response

Use these settings: https://autoconfig.fastmail.com/mail/config-v1.1.xml
Incoming server
Server: imap.fastmail.com
Security: SSL/TLS
Port: 993
Authentication: OAuth 2.0
Outgoing server
Server: smtp.fastmail.com
Security: SSL/TLS
Port: 465
Authentication: OAuth 2.0

Wow, my config predates the current service documentation.  Imagine that.  Thanks @cketti
I'm able to get OAuth2 working in Thunderbird Android 8.0b3.  Success and thanks!
However, K-9 6.804 still shows me the OAuth signin failed / ... not supported after tapping the Sign In button in the settings/config.  Autoconfig issue perhaps?  A future K-9 release for this to work?
Thank you!!

OAuth with Fastmail is only supported since 8.0b3


PseudoElement ignoring enable false in .scss-lint.yml

I updated to v0.48.0 today and started getting the following warning: [W] PseudoElement: Begin pseudo elements with double colons: '::'.  I previously did not have any PseudoElement rule in my .scss-lint.yml config file. I added the PseudoElement rule and enable: false, but it continues to issue warnings.
It does respect disabling in the source via //scss-lint:disable PseudoElement.
Commented on issue https://github.com/brigade/scss-lint/issues/678, moved here to a separate issue.

Did you try enabled: false? https://github.com/brigade/scss-lint#configuration

Good catch. Thanks @srawlins


Error with Android Studio 3 nad new gradle

Error while build apk development branch  Error:Execution failed for task ':app:transformDexArchiveWithExternalLibsDexMergerForDebug'. > java.lang.RuntimeException: java.lang.RuntimeException: com.android.builder.dexing.DexArchiveMergerException: Unable to merge dex

Yep, I have that problem, too. Downgrading to Android Studio 2.x should work. I have not figured out yet what is wrong. So if you do please let me know.

in module storageprovider, file build.gradle, Line:38, delete org.apache.commons:commons-io:1.3.2, and IOUtiols in ParcelFileDescriptorUtil.java, it will build ok in Android Studio 3x

A failure occurred while executing com.android.build.gradle.internal.transforms.JacocoTransform$JacocoWorkerAction
in andriod studio 3.1

Add         classpath 'org.codehaus.groovy:groovy-all:2.4.12'         classpath('com.dicedmelon.gradle:jacoco-android:0.1.2'){             exclude group: 'org.codehaus.groovy', module: 'groovy-all'         }
to build.gradle (Project: libaums-develop)


refactor(server): compile on first run if browserify files missing.

To support running karma directly out of the repo, 'browserify' is applied dynamically iff the static files are not already available.  The 'browserify' module is loaded only in the case where it will be used: users installing karma from the npm module will not need to apply it and installs using --production will not depend upon 'browserify' or its otherwise unused deps.
This provides an alternative fix for #2884, one that does not require every user to install the browserify deps.
Fixes #2921

I left this as a revert to highlight that the build-before-publish steps are simply copies of the older code.  Squashing seems reasonable as well, since half of the reverted code is pulled into the second commit.


Update node-forge dependency

npm audit generates the following error for node-forge < 1.0.0:
Prototype Pollution in node-forge debug API. - https://github.com/advisories/GHSA-5rrq-pxf6-6jx5

Another advisory was published that has to do with the node-forge dependency.
URL parsing in node-forge could lead to undesired behavior.

There was another advisory published a few days ago regarding firebase-admin and the node-forge dependency.
URL parsing in node-forge could lead to undesired behavior.

It does not look like firebase-admin uses the forge.util.parseUrl API directly. We also updated the dependency in #1533
Thank you.

@lahirumaramba
Appreciate you verifying vulnerable API is not used by firebase-admin :+1: I know I can ignore that one.
Any chance to release a patch version so we'll get a clean audit report? (or is it already planned for some future date?)

This change will be included (along with other updates) in a release planned for next week. I will update this issue once the release is out. In the meantime please update to node-forge 1.0.0 in your server environments. Thank you for your patience!

node-forge version update is included in today's release v10.0.2. Thank you for your patience everyone!


Set systemd.user.startServices = "sd-switch"

Just a note for me, https://github.com/nix-community/home-manager/issues/5452 did not fix https://github.com/kachick/dotfiles/issues/680


Git Command Line Disabled

Prerequisites
I am running on macOS
Description
"Git Command Line" under "Windows" does not appear to do anything. Has this been disabled? "src/com.spoiledcat.git.ui/Editor/UI/Menus.cs" suggests that it might be disabled.

Would also be nice to be able to configure the executable used for opening the Git Command Line.  Right now it pretty much just opens cmd.exe in the project directory.  An option to use git-bash.exe would be super helpful for me. :)


How to mock the same path but data in request's body are different ?

How to mock the same path but data in request's body are different ?

@up1  Sorry for the long wait.
Kindly help review the latest PR. https://github.com/depoon/SwiftLocalhost/pull/14
use the following in your podfile
pod 'SwiftLocalhost', :git => 'https://github.com/depoon/SwiftLocalhost.git', :branch => 'multiple-response-per-path-route'

I will merge the branch in 1 week time, or earlier if you can give me your feedback.

Hi @up1,
I've merged the feature to allow developers to mock multiple response for the same path. Note that this requires you to take note of the order of requests being fired and match the respective mock responses in the same order.
Meanwhile i will close this issue. Thanks


add groupByLabel function

This is convenient, but also necessary since the $fieldPath parameter to groupBy can't contain dots in map key names, and labels are typically reverse-domain-name prefixed.

I built something specific for grouping by the service name of the docker compose file:
https://github.com/troii/docker-gen/commit/e9eded7a42463db6014b33ca1bdfcb6c305c97e4
but this pull would make mine obsolete and make it more generic
my vote for this one! ;)

I tried to use groubByLabel like
{{ range $host, $containers := groupByLabel $ "com.docker.compose.service"  }}

but I always get
function "groupByLabel" not defined

@tompson I've successfully used the new function with a binary built by running make with this PR applied, e.g. make && ./docker-gen -only-exposed /path/to/my/tempate.tmpl. It sounds like you're probably not using the right docker-gen binary?

did exactly that, checked multiple times that I got the right binary
do you have an example template file?

You probably don't have this PR applied locally then. A simple example template would be:
{{range $project, $containers := groupByLabel $ "com.docker.compose.project"}}{{printf "%s %s\n" $project (first $containers).ID}}{{end}}

wow, that was hard to track down, problem was that in cmd/docker-gen/main.go the import
"github.com/jwilder/docker-gen"

caused that make did not build codekitchen/docker-gen or troii/docker-gen even when I ran make in my repository

Ah dang, that's a pain yeah. Glad you got it sorted out.

@tompson When I work on this project I add an additional Git remote to my checkout of github.com/jwilder/docker-gen to avoid this problem.

Thanks @codekitchen!


Include *.js files into binary

Hello!.
May be I have some incomprehension how this tool works.
Does it pack all .js files (my app and node_modules/ files) or not?
When I trying to build app using
pkg -t node8-linux-x64 package.json
command I get a binary that could be run only inside directory, where *.js files placed.
Thank you!

pkg -t node8-linux-x64 package.json -d to see if they are taken into executable. Be sure you explicitly require those files.

Thank you for answer.
Yes they are taken.
The problem was in config module - it loads configuration files dynamical, so i also should copy ./config directory with binary file.

Great! Feel free to reopen on something new :)


BigQuery: bytes processed should be logged for all dbt commands that perform queries

Describe the feature
With the release of dbt 0.18.0, launching a dbt run command against a bigquery database will output the bytes processed when a model is successfully deployed. However, to get a full picture of the amount of bytes dbt processes on bigquery (and hence to get an idea of the cost of running a specific dbt command), this should also be logged when launching dbt test, dbt source snapshot-freshness and dbt run-operation commands.
Additional context
For dbt run commands, this feature was discussed in #2526, it would be nice to extend this to also log this number for the other commands mentioned above.
Who will this benefit?
This is a bigquery specific issue.
Are you interested in contributing this feature?
Sure, happy to see how we could add this.

This makes sense to me! I think the long-term answer here still looks like giving users more control via configurable log output (https://github.com/fishtown-analytics/dbt/issues/2580). In the meantime, I see the value of reporting bytes processed for queries that can be sneakily expensive, such as schema tests or freshness checks that scan massive tables.
I think the change would need to happen in the "everything else" query result:
https://github.com/fishtown-analytics/dbt/blob/fa8a4f2020655c60bdb66270616f5654e168a729/plugins/bigquery/dbt/adapters/bigquery/connections.py#L306-L307
In particular, you'll want to pull in total_bytes_processed, as in the query types above. From a brief glance at BigQuery's docs:

Return total bytes processed from job statistics, if present.

Given that "if present" caveat, it'd be a good idea to add some handling in the event that total_bytes_processed is missing.
Take a swing at this, and let me know if you run into any trouble!

@jtcohen6 Is the STATUS produced in this else clause actually used in the log output for tests? Test log outputs look like [PASS in 1.63s] or [WARN 3 in 1.52s].

Looking at the BigQuery logs, I noticed that the statement_type cloud be the string "SELECT". So maybe we could just include it together with "CREATE_TABLE_AS_SELECT". and Keep the else part as a generic catchall.

@alepuccetti @bodschut. That sounds like a good approach. I knew this team would find a way :)

Hi guys
I've done some digging in the code and unfortunately I'm afraid it won't be as simple as we think :-) Let me explain what I found.
As you can see in the execute function of the bigquery connection, there is indeed a status string being built that contains the bytes processed since the last dbt release. This status string is returned by the execute function together with the result of the query, so far so good:
https://github.com/fishtown-analytics/dbt/blob/fa8a4f2020655c60bdb66270616f5654e168a729/plugins/bigquery/dbt/adapters/bigquery/connections.py#L309
For a normal dbt run, this connection is probably used when a macro is ran, as all materialisations are achieved through macros in dbt. I haven't looked into the details of how those macros are internally executed, but it's clear that the status string that contains the bytes processed is properly handled by the macro code, returned to the calling code and eventually used in the function that prints the log line on the terminal:
https://github.com/fishtown-analytics/dbt/blob/fa8a4f2020655c60bdb66270616f5654e168a729/core/dbt/task/printer.py#L137-L147
I'm pretty sure that the status string created in the execute function of the bigquery connection is accessed here in the get_printable_result function from the result object (which is of the class RunModelResult and then passed to the print_fancy_output_line function.
The issue with the dbt test command is that the code that calls the bigquery connection to execute the query doesn't put the status string in the status field of the result object (which is also of type RunModelResult in the case of a test run). Rather, the code sets the result.status field to the number of rows that do not pass the test predicate, as you can see in the snippet below (which is for the execute_data_test function, the same is true for the execute_schema_test function:
https://github.com/fishtown-analytics/dbt/blob/fa8a4f2020655c60bdb66270616f5654e168a729/core/dbt/task/test.py#L43-L58
As you can see, the adapter returns both the status string (catched here in the res variable) and the query output (catched in the table variable), but it only returns the table var to the calling code, so the status string containing the bytes processed info gets lost here ...
So, I think we will need to adapt how this status string is passed up the call chain, but as we're stepping out of the bigquery plugin and into the core dbt code, I'm a bit reluctant to start changing stuff... So @jtcohen6 could you maybe look for someone with knowledge of this part of the core code to see what we could do here?

Good catch @bodschut, and sorry for leading you astray further up. I believe this is the code responsible for printing data + schema test results:
https://github.com/fishtown-analytics/dbt/blob/4a21ea65759d78fe56f33b71b671948ca747161b/core/dbt/task/printer.py#L118-L135
To include bytes processed, I think we'd need to change execute_schema_test and execute_data_test to return a dictionary instead of just an integer status. That brings us within orbit of a much larger topic: changes to run_results.json(https://github.com/fishtown-analytics/dbt/issues/2493) that we already have on the short-term docket.
@beckjake Do you have thoughts about how we could incorporate structured representation of integer values (rows affected, byes processed) into the proposed run results spec? I wouldn't say that the way we've done this for model run results today is all that good, either: status is just a string value "CREATE TABLE (1.0 rows, 0.0 Bytes processed)"`.

The proposal in #2493 already handles the "status string vs status integer" issue, so that's nice.
For the bytes process/rows affected aspect, I see a couple ways we can do it:

add an unstructured dict of result data or something like it, populated on a per-adapter basis. The adapter is responsible for generating the status text and any extra result data it might think is appropriate, then that gets decorated with any task-specific result data that might be appropriate.
per-adapter per-task result types. This turns result types into a combination of the existing "what is this a result of" and a new axis that's "what adapter is this a result for".

I don't have strong feelings either way, both are probably valid. The first option is easier to implement and probably doesn't have to be a breaking change for adapters, the second option is probably more maintainable in the long run, gives more flexibility for adapters to implement custom result types, and probably is better for consumers on some level since they can know what they're consuming.
We could probably start with the first and transition to the second, though it'll be unpleasant to maintain if we have to preserve the schema and the total development time will surely be much longer than either of the choices on their own.

IIRC, after discussing this live, we decided we'd opt for:

an unstructured dict of result data ... populated on a per-adapter basis. The adapter is responsible for generating the status text and any extra result data it might think is appropriate, then that gets decorated with any task-specific result data that might be appropriate.

The trickiness will be in surfacing that data to stdout. While this isn't a blocker for #2493, it's highly related.

#2961 adds an adapter-specific dict to run_results.json. Let's consider that a partway resolution to this issue; meanwhile, I'll open a new issue to address the desire for recording bytes_processed for queries from other invocation types—namely dbt test—which we can revisit for v0.20.0.


Ver. <IP_ADDRESS> not Displaying "Pop-Up" TEMPS & BOOST On Fan Graph

Ver. <IP_ADDRESS> not Displaying "Pop-Up" TEMPS & BOOST On Graph when changing Fan Curves.
This feature is helpful when setting and matching curves of the different sensors.
Do not know if you removed this from this build so will not say is "bug". Thank you.

OMG... What a day for me... One guy blame me i broke keyboard (no, it's impossible). Even thinking about close this project.
No, it's displaying it at my gear. Both FX and Fan GUI. But i'll check what it can be.
BTW, what about fan stuck? Did it fixed?

Aye, catch it! Will be fixed next update.

Good day sir, I saw the comment regards the keyboard, lol. Sorry for your grief. PLEASE do not stop developing this project as it is the best thing since sliced bread. It can be frustrating and disheartening when folks attack your work in such a fashion, especially when you devote so much of your time and efforts for FREE.
I wonder if he has tried to connect the keyboard to another machine or completely uninstalled all related software and rebooted? So many questions...
Anyways, I appreciate you and your works. Peace.

Fixed in <IP_ADDRESS>.

Perfect! Don't change a Thing! Thank you.


Kubernetes explain should work for resources loaded from the cluster

As noted by @squillace, the current implementation of the Explain API does not activate when viewing resources loaded from the cluster, and only works when viewing resources loaded from the filesystem.

I think that this is something wiggy with the tooltip API (or maybe just our implementation of a tooltip provider)

Closed by #370


Theoxuan patch 1

Description
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Fixes # (issue)
Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How has this been tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[ ] local build the book
[ ] review the artifacts from local build
[ ] local build the slides if appliable
[ ] Unit test if appliable

Checklist:

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have applied tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules

Data quality refers to the state of qualitative or quantitative pieces of information. Generally speaking, high-quality data could "fit for [its] intended uses in operations, decision making and planning"{cite}redman2008data{cite}fadahunsi2019protocol{cite}fadahunsi2021information. Data quality is a widely used concept and is split into multiple dimensions traditionally. This section will discuss the most common ones to Machine Learning data engineering, including completeness, duplicates, outlier, and consistency.
:::{seealso}

The Overview and importance of data quality for machine learning tasks{cite}jain2020overview lecture recording at KDD 2020, Part 1, Part 2, Part 3.
Data Science for Beginners - Introduction to Data Ethics

:::

I just checked data-engineering.ipynb, I think the cite must be on COS, or delete them.And some cite in Data quality is invalid. It's better for you to check your file in JupyterLab.
According to error: "Figure caption must be a paragraph or empty comment" indicates a chart caption-related problem, usually caused by incorrectly formatted chart captions in the Markdown unit

If data-engineering.ipynb hinder you submit PR, just delete this file and resolve md file. I will check this file.

Please merge the contents of the latest main branch and build again, if you can't, save the file locally then create a new synchronized latest branch and commit a PR.

As I say in Wechat, Execution failed error is Github actions cannot run ipynb file successfully, so what you should do is running locally to see if this file can be executed successfully, or if it takes too long to be executed.
If you find ipynb files like what I say, please add them to execute.
Also you can refer the PR I submit: 'https://github.com/ocademy-ai/machine-learning/pull/604'


Updating skills installed with branch specs

With the ability to specify a branch in requirements, it seems like auto-updates after the fact should respect those branch specs but currently they utilize the values in skill.json. Looking for opinions on this and what the best method may be..
My current proposal would be to overwrite the skill.json url and branch at install time when a branch is specified.

osm has no concept of update really, an update just means installing again, it checks md5 sums to let you know if something changed, but there is no distinction between update and install, that would be up to the user... auto updates are out of scope for osm completely
in the context of neon the skills service is what handles auto updates, and this is only for default skills
not sure if i understood the issue correctly, does "specify a branch in requirements" mean a skill requiring a skill in skill_requirements.txt?

I hadn't considered the local changes questions, but that's a good point.. At the moment, I don't think we have any indication of local changes unless we start tracking OSM install time and comparing with last modified time. I believe this means the Neon Core updater implementaiton is already clobbering local changes.
I agree in general that devs just turn off auto-updates if they want to make local changes; FWIW my workflow would be to make changes in git and update the device anyway. From an integrator standpoint, I want to define my skills list and trust OSM to do what I tell it and update as specified to the branch I specified, regardless of local changes.
I think in the future this does become a broader question of what, when, and how to update skills with local changes; my initial thoughts regarding options are:

Update on startup/restart only and overwrite local changes (assume those changes were for testing and don't modify them while the module is still running)
Ignore all local changes and just update as scheduled (if devs don't want updates, they shouldn't have enabled them in the first place)
Track local changes and don't update modified skills (match MSM behavior, requires some VCS history)
Prompt for confirmation in either case (this has some UI questions and would probably belong to an installer skill)
Add a config parameter to overwrite on change (requires keeping some amount of version history like the MSM option)

osm has no concept of update really, an update just means installing again, it checks md5 sums to let you know if something changed, but there is no distinction between update and install, that would be up to the user... auto updates are out of scope for osm completely
in the context of neon the skills service is what handles auto updates, and this is only for default skills
not sure if i understood the issue correctly, does "specify a branch in requirements" mean a skill requiring a skill in skill_requirements.txt?

Sorry, requirements was the wrong term, I was referring to default_skills or essential_skills

should we move this issue to https://github.com/OpenVoiceOS/ovos-core then? or maybe even https://github.com/NeonJarbas/NeonCore/ ?
osm itself does not handle auto updates, thats using the event scheduler in repos above
i think that for all osm is concerned it treats all urls the same, and when told to install something, it does. maybe we want to make behavior configurable here?

skill exists -> overwrite
skill exists -> abort
skill exists -> prompt user (cli / skill / gui)

This is

should we move this issue to https://github.com/OpenVoiceOS/ovos-core then? or maybe even https://github.com/NeonJarbas/NeonCore/ ?
osm itself does not handle auto updates, thats using the event scheduler in repos above
i think that for all osm is concerned it treats all urls the same, and when told to install something, it does. maybe we want to make behavior configurable here?

skill exists -> overwrite
skill exists -> abort
skill exists -> prompt user (cli / skill / gui)

This is fine by me, really more of a core question than a skill manager one at this point; this really is behaving as programmed, unless we want to put update logic within OSM

fwiw, I'd posit that osm should handle auto-updates, and have implementations set its config, rather than leaving it to each implementation to write an update mechanism. It's Python. If somebody really hates it, they can override it, but the first people who will have to write it in separate downstreams are :wave: the people tagged in this issue =P

auto updates are handled by mycroft-core, mycroft does not want to support alternative appstores, it would be a bunch of work to make things compatible
i really am convinced auto updates are out of scope, those could be as simple as a cronjob passing urls to osm

Currently, auto-update is out of scope of this repo. Closing issue as current update implementation exists elsewhere. A new issue should probably be created if auto-update functionality is desired in OSM directly


[NEW] Implement save image to gallery

@RocketChat/android

Closes #1130

@leonardoaramaki Button looks misaligned to me. Take a look on that please.


Fixing the checked variable in radio buttons

This PR fixes #13907

Pull Request Test Coverage Report for Build 462971000

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 43.081%

Totals

Change from base Build 462048183:
0.0%

Covered Lines:
24165

Relevant Lines:
51399

💛  - Coveralls

Pull Request Test Coverage Report for Build 462971000

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 43.081%

Totals

Change from base Build 462048183:
0.0%

Covered Lines:
24165

Relevant Lines:
51399

💛  - Coveralls

@aasimkhan30 You have a compile error currently FYI
[18:41:19] Error: /home/runner/work/azuredatastudio/azuredatastudio/extensions/arc/src/test/ui/components/radioOptionsGroup.test.ts(42,4): Conversion of type 'RadioButtonComponent | undefined' to type 'StubRadioButton' may be a mistake because neither type sufficiently overlaps with the other. If this was intentional, convert the expression to 'unknown' first.
  Type 'RadioButtonComponent' is missing the following properties from type 'StubRadioButton': click, _onDidClickEmitter

@aasimkhan30 You have a compile error currently FYI
[18:41:19] Error: /home/runner/work/azuredatastudio/azuredatastudio/extensions/arc/src/test/ui/components/radioOptionsGroup.test.ts(42,4): Conversion of type 'RadioButtonComponent | undefined' to type 'StubRadioButton' may be a mistake because neither type sufficiently overlaps with the other. If this was intentional, convert the expression to 'unknown' first.
  Type 'RadioButtonComponent' is missing the following properties from type 'StubRadioButton': click, _onDidClickEmitter

please fix the compilation error

please fix the compilation error


Enforcement and report handling details in CoC

Add enforcement details in the CoC. I have recently edited a CoC using multiple reference, it is minimal (smaller than The Carpentries, but has explicit info around report handling and consequences): https://github.com/alan-turing-institute/reproducible-project-template/blob/main/CODE_OF_CONDUCT.md
Other option is here that uses restorative justice (and has the Mozilla content as currently in our CoC): https://github.com/alan-turing-institute/open-community-building/pull/3/files

@yochannah @bebatut @emmyft can one of you look at this when there is more time in our calendar?

Hello @malvikasharan would you like me to look into this and add enforcement details? This issue has been open for a while now.


Accept german umlauts for autocompletion

fixes #272.

i fixed the js by adding you piece of code to it, but it doesn't fix the problem on FF - i'm using 59.0.2. Any idea?

@dmorgenstern-init Thanks for help 👍


DEPRECATION WARNING: Using / for division outside of calc() is deprecated

This is part of the compilation warning :

14:58:22.395
Configuration file: /opt/buildhome/repo/_config.yml

14:58:22.418
Source: /opt/buildhome/repo

14:58:22.418
Destination: /opt/buildhome/repo/_site

14:58:22.418
Incremental build: disabled. Enable with --incremental

14:58:22.418
Generating...

14:58:22.473
Jekyll Feed: Generating feed for posts

14:58:22.856
DEPRECATION WARNING: Using / for division outside of calc() is deprecated and will be removed in Dart Sass 2.0.0.

14:58:22.856

14:58:22.856
Recommendation: math.div($spacer, 2) or calc($spacer / 2)

14:58:22.856

14:58:22.856
More info and automated migrator: https://sass-lang.com/d/slash-div

14:58:22.857

14:58:22.857
╷

14:58:22.857
302 │ $headings-margin-bottom:      $spacer / 2 !default;

14:58:22.857
│                               ^^^^^^^^^^^

14:58:22.857
╵

14:58:22.857
../../../../jekyll-theme-clean-blog-4.0.12/assets/vendor/bootstrap/scss/_variables.scss 302:31  @import

14:58:22.857
../../../../jekyll-theme-clean-blog-4.0.12/assets/vendor/bootstrap/scss/bootstrap.scss 9:9      @import

14:58:22.857
../assets/vendor/startbootstrap-clean-blog/scss/styles.scss 5:9                                 @import

14:58:22.858
styles.scss 2:9                                                                                @import

14:58:22.858
/opt/buildhome/repo/assets/main.scss 1:9                                                        root stylesheet

14:58:22.859
DEPRECATION WARNING: Using / for division outside of calc() is deprecated and will be removed in Dart Sass 2.0.0.

.

.

14:58:23.047
WARNING: 64 repetitive deprecation warnings omitted.

My solution:
Since it seemed to be solely due to bootstrap, I tried implementing the latest version of bootstrap (now 5.3.0), changing assets -> vendor -> bootstrap -> scss
Replacing the entire folder with the new version, so far I am not noticing any problems
After the upgrade I no longer have any compilation warnings

After upgrading bootstrap, the theme does not work graphically correctly, so I migrated the bootstrap version used by this repository.
I had to edit some files manually, but the majority was done using the automatic migration tool.
I leave a zip file with the modified files:
bootstrap.zip

I have the same issue

I have the same issue

Another user and I are using my fix, in my fork there is only this fix, you can try it and leave feedback
My Pending Pull Request


BridgeStan folder '/usr/local/lib/python3.9' does not contain file 'Makefile'

Hi, follow up on #68 , I successfully installed the bridge_stan on Google Colab. And set the Python version on Colab to 3.9.16 and used the following code to test indeed the version is correct.
import sys
print(sys.version)

3.9.16 (main, Dec  7 2022, 01:11:51) \n [GCC 9.4.0]

However, I still cannot run the example because I keep getting this error msg now:
ValueError: BridgeStan folder '/usr/local/lib/python3.9' does not contain file 'Makefile', please ensure it is built properly!
If you need to set a different location, call 'set_bridgestan_path()'

Below is the example python code:
import bridgestan as bs
import numpy as np
stan = "/content/bridgestan/test_models/bernoulli/bernoulli.stan"
data = "/content/bridgestan/test_models/bernoulli/bernoulli.data.json"
model = bs.StanModel.from_stan_file(stan, data)

I have also tried some recommendation in #68 , such as changing bridgestan to bridgestan_repo:
!pip install /content/bridgestan_repo/python

Here is the google colab file I'm running

Based on the error If you need to set a different location, call 'set_bridgestan_path()', I think the next thing to try is bs.set_bridgestan_path('/content/bridgestan/) before calling StanModel.from_stan_file

Thanks! It works now!


Moving to Maven Wrapper from local installation

The Maven Wrapper is an excellent choice for users that don't want to install Maven at all. Instead of installing many versions of it in the operating system, we can just use the project-specific wrapper script.
Below files needs to be added to the project as part of moving:

mvnw: it's an executable Unix shell script used in place of a fully installed Maven
mvnw.cmd: it's the Batch version of the above script
mvn: the hidden folder that holds the Maven Wrapper Java library and its properties file

The wrapper should work with different operating systems such as:

Linux
macOS
Windows
Solaris

After moving to Maven Wrapper OS specific commands needs to be executed instead of generic mvn command, hence the documentation needs to be updated with the commands for UNIX/Linux and Windows based operating systems.
@isopropylcyanide your thoughts on this? If needed I can work on this and submit a pull request.

@mmafrar I agree. This would help streamline the environment for all platforms. Yes, we can work towards it.


Improve frontend token rounding

Fixes #283
I believe this is basically a no-op from the user's perspective, but here's confirmation that the change works:

It's also used on the withdraw confirmation modal:

@davidlaprade hmm I don't think that's quite right. On the prior screen, we show the fee is 0 MATIC, but that's referring to OUR relayer fee. In the modal, what's being displayed is the gas fee that will be charged when the transaction is submitted. The real number is not zero, as you can see when you click the button to customize it.

@davidlaprade here's what this looks like on the live site, for comparison:

Okay, guys, thanks for bearing with me. I made a bunch of changes to hopefully make the code clearer and easier to reason about in the future. (Largely just fixing bad/ambiguous variable names that I picked when adding custom fee support.) Here's how things look like at this point:


cEUR: Decide on bucket sizes

It sounds like this parameter can be adjusted after the contracts release 3 deployment as part of the cEUR activation proposal, because even though the cEUR Mento will be deployed, it will be impossible to use due to no oracle reports.


checks version of deployment matches version go file

Task:
Change the controller to look for the serving.knative.dev/release label in the manifest and use that to set the status.version in the CR.
Add a test for that too

/assign @aliok

I will do the same thing in https://github.com/knative/eventing-operator/pull/42


Disable dates

how to disable certain date ranges

For now you can specifiy the option minDate and maxDate for example

$("#input")..hijriDatePicker({
    minDate: "2012-01-25"
    maxDate: "2013-02-24"
})

Thanks

How can i disable all Friday and Saturday?

How can i disable all Friday and Saturday?

Dears,
Is this project still active as there was no activity on this for long time.
There is an option in the source file of bootstrap-hijri-datetimepicker.js for disabledDates which takes an array but its not working. Any help would be appreciated,
Regards,

Dears,
Is this project still active as there was no activity on this for long time.
There is an option in the source file of bootstrap-hijri-datetimepicker.js for disabledDates which takes an array but its not working. Any help would be appreciated,
Regards,

How can i disable all Friday and Saturday?

There is an option daysOfWeekDisabled which takes range like [0,6] but it seems not working currently. @balbarak may advise.

How can i disable all Friday and Saturday?

There is an option daysOfWeekDisabled which takes range like [0,6] but it seems not working currently. @balbarak may advise.

Yup this project is under development and a new release will be out soon with many fixes and more options
Thanks

Yup this project is under development and a new release will be out soon with many fixes and more options
Thanks

Thanks for your quick reply. Appreciated.
When the new release is expected?

Thanks for your quick reply. Appreciated.
When the new release is expected?

Thanks for your quick reply. Appreciated.
When the new release is expected?

@balbarak

Thanks for your quick reply. Appreciated.
When the new release is expected?

@balbarak


ENH: signal: add Lanczos window function

Co-authored-by: Guillaume<EMAIL_ADDRESS>
Reference issue

Reviving #6837
What does this implement/fix?

5 years ago, PR #6837 tried to add the Lanczos windows function, but it has been stalled now.
Adding this new window function is already discussed in the mailing list,

https://mail.python.org/pipermail/scipy-dev/2017-January/021654.html

So, we can revive this PR again based on the latest code base.
I implemented these:

the new Lanczos windows function and its docstring
get_window support
unit tests.

This is the benchmark between non-symmetric and symmetric window functions. I think the symmetric version is good performance, especially in a big size window:
In [100]: import numpy as np

In [101]: def non_sym_lanczos(M):
     ...:     return np.sinc(2. * np.arange(0, M) / (M - 1) - 1.)
     ...:

In [102]: def sym_lanczos(M):
     ...:     def _calc_right_side_lanczos(n, m):
     ...:         return np.sinc(2. * np.arange(n, m) / (m - 1) - 1.0)
     ...:
     ...:     if M % 2 == 0:
     ...:         wh = _calc_right_side_lanczos(M/2, M)
     ...:         w = np.r_[np.flip(wh), wh]
     ...:     else:
     ...:         wh = _calc_right_side_lanczos((M+1)/2, M)
     ...:         w = np.r_[np.flip(wh), 1.0, wh]
     ...:     return w
     ...:

In [103]: %timeit non_sym_lanczos(100)
11.7 µs ± 127 ns per loop (mean ± std. dev. of 7 runs, 100000 loops each)

In [104]: %timeit sym_lanczos(100)
30.8 µs ± 378 ns per loop (mean ± std. dev. of 7 runs, 10000 loops each)

In [105]: %timeit non_sym_lanczos(1000)
26.7 µs ± 3.02 µs per loop (mean ± std. dev. of 7 runs, 10000 loops each)

In [106]: %timeit sym_lanczos(1000)
38.5 µs ± 938 ns per loop (mean ± std. dev. of 7 runs, 10000 loops each)

In [107]: %timeit non_sym_lanczos(10000)
128 µs ± 2.25 µs per loop (mean ± std. dev. of 7 runs, 10000 loops each)

In [108]: %timeit sym_lanczos(10000)
98.3 µs ± 6.05 µs per loop (mean ± std. dev. of 7 runs, 10000 loops each)

In [109]: %timeit non_sym_lanczos(100000)
1.08 ms ± 10.4 µs per loop (mean ± std. dev. of 7 runs, 1000 loops each)

In [110]: %timeit sym_lanczos(100000)
578 µs ± 2.57 µs per loop (mean ± std. dev. of 7 runs, 1000 loops each)

In [111]: %timeit non_sym_lanczos(1000000)
13.9 ms ± 49 µs per loop (mean ± std. dev. of 7 runs, 100 loops each)

In [112]: %timeit sym_lanczos(1000000)
6.97 ms ± 33.2 µs per loop (mean ± std. dev. of 7 runs, 100 loops each)

I realized the new function was missing the versionadded directive so I clumsily committed it. I'll merge when green, thanks in advance @AtsushiSakai !


Issues with installation

Hi I exactly followed the réadme, using the example project, but still:
When trying to run python manage.py syncdb , I get the following error:
ImportError: No module named example_project.settings.local
Any hints?

Hello vectorien,
Please confirm that there is a copy of:
django-timepiece > example_project > settings > local.py.example
renamed to local.py?

yep

@vectorien: I set up a new virtualenv with the cloned repo and ran across the error you see if I neglected to add the cloned repo to the virtualenv:
Can you verify that you performed Step 2 in the Installation Documentation?

Well I started here actually: http://django-timepiece.readthedocs.org/en/develop/index.html#installation

is it not possible to do it without a virtualenv?


cant run https adhoc

Hi.
for sometime i was able to run https using flask using tmp ssl cert. adhoc.
but now when i am trying to enable https back again from http. i face this issue.
  File "Z:\Python_Venv\env1\lib\site-packages\gevent\server.py", line 125, in __init__
    self.wrap_socket = ssl_context.wrap_socket
AttributeError: 'str' object has no attribute 'wrap_socket'

i am adding this to my code.
ssl_context='adhoc'
i am on Python 3.10.4 , flask 2.2.2
UPDATE :
i found that this issue occurs when :
from engineio.async_drivers import gevent
But this is important as since i am packing using pyinstaller. this line must be there

Don't use the development server outside of development. That said, it sounds like this is Flask-SocketIO.


Cannot list objects error

Which version of the AzCopy was used?
Note: The version is visible when running AzCopy without any argument
10.15.0
Which platform are you using? (ex: Windows, Mac, Linux)
Windows
What command did you run?
Note: Please remove the SAS to avoid exposing your credentials. If you cannot remember the exact command, please retrieve it from the beginning of the log file.
.\azcopy  copy 'https://s3-ca-central-1.amazonaws.com/devo-log-storage' 'https://ulsnapreprod.blob.core.windows.net/azcopy-test' --recursive=true
What problem was encountered?
Cannot list objects, Access Denied (this was the error)
How can we reproduce the problem in the simplest way?
Reproducing the problem may not be possible as the copy is done for a company that I do not own.  I'm hoping the solution is due to semantics or something I may not have done correctly.
Have you found a mitigation/solution?
No I have not.

I am facing same problem, any update on this?

Facing the same issue. any update on this?

Closing due to age. Please open a new  issue if you're seeing this.

Wow, so nobody from MS responded other that to close it due to age.
The problem appears to be due to AzCopy trying to enumerate the S3 bucket, however the permissions aren't sufficient.  Unfotunately this also happens when you only want a specific object. Our supplier can't grant enumerate permissions due to data sensitivity so we can't use AzCopy until the code is updated to not force --recursive=true on S3 sources.


E2e 2 clusters

Issue #, if available:
Description of changes:
Testing performed:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/test all

/retest

/lgtm


Switch to semantic versioning

What are your thoughts on making the next major release 16.0.0? Your changelogs are great, and I can easily pick out the breaking changes, but versioning to go along with that would be nice.

@stevewillard We are working on improving the Roadmap.md file which will tell the users about the upcoming versions and the path this project is heading towards. Stay tuned. Till then you can follow this update #4205

@stevewillard We are following semver, pre-1.0.0 minor versions are considered breaking (npm respects this too)

First, I just want to say that this project is great. Thank you!
NPM, Inc. recommends against using pre-1.0.0 semver: https://docs.npmjs.com/getting-started/semantic-versioning

Semver for publishers

If a project is going to be shared with others, it should start at 1.0.0, though some projects on npm don't follow this rule.

If I understand correctly, pre-1.0.0 is what you use before your push to npm. Sure you can do whatever you want but the community is moving away from 0.x.x releases I would hope that this project would be willing to follow the so-called standards of the community as well. Heck, even React itself recently gave it and went from 0.14 to 15.0.
Just my two cents on the subject. 😀


feat: add debug mode

Please see debug mode

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Failed to run with npx

> npx check-licenses
npx: installed 71 in 10.933s
Error: Cannot convert undefined or null to object

Tried on Windows 11 with<EMAIL_ADDRESS>

If you do ls does package-lock.json show up? check-licenses is using that to determine the project licenses, while if you want a more general checker (but also slower and with some minor hiccups) you can try instead legally.

I just published<EMAIL_ADDRESS>could you please try again and see if it gives you the same error (or a new one?)? Do you get any other output in the terminal besides what you showed me?

Yes. Tried legally and it worked without any issues.
I’ll try the new version when I get a chance.

Cool, thanks!

It seems like a npm@6 vs npm@7 issue:
https://docs.npmjs.com/cli/v8/configuring-npm/package-lock-json#lockfileversion
Unfortunately I'm going to suggest upgrading to npm@7 or higher (current version is 8) since I do not have the bandwidth to support older versions (recommended), or to use legally instead (not recommended).


⚠ ClamAV has degraded performance

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

HTTP code: 200
Response time: 80 ms

Resolved: ClamAV performance has improved in ac9351c.