feature: Add a search box to filter request list entries.

This is the implementation for the solution suggested in #205
Might also help alleviate problems like the one mentioned in #203
Notes
Ive only used this addon in classic era (1.15.2) and i believe the addon only utilizes the Request tab in that client, and so i've only implemented the filtering for the request list.

Ill take a look at this when I figure out why the add-on broke for some people with the latest changes.

okay, Is there an issue for this on GH i can help check out?

I think I fixed it. Yea not everyone had the issue, me including and I struggled to reproduce it originally as well. Going to give the new version 1 more day to confirm though


Add crack

@PoolloverNathan what use does this have? you do not need a constant variable, just don't change it and let linker figure it out


[Patch] GH 3609: CMAKE_MODULE_PATH

Update the installed CMAKE_MODULE_PATH for the installed lib.
Adds https://github.com/AMReX-Codes/amrex/pull/3609

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

@conda-forge-admin, please rerender


ros1_bridge: 0.10.0-1 in 'rolling/distribution.yaml' [bloom]

Increasing version of package(s) in repository ros1_bridge to 0.10.0-1:

upstream repository: https://github.com/ros2/ros1_bridge.git
release repository: https://github.com/ros2-gbp/ros1_bridge-release.git
distro file: rolling/distribution.yaml
bloom version: 0.10.0
previous version for package: 0.9.4-2

Note to reviewers, I bumped the minor so that foxy can diverge on the 0.9.x branch.


How can set the message head data?

I want to send a Drafty type message, such as Image via SDK,  but cannot find where to set it

Hello,
This is not possible right now. If you need to send an image you can define a custom data structure that contains the image base64 data or url and parse your structure when reading the message.
The message content is not supposed to be only string and it's dynamic. So you can pass serialized json or a Map as your message content.

got it, thanks a lot.


Icons should be not SVG on the pinephone

The graphics drivers on a Pinephone render glitches into SVG icons for some reason. We might either improve or use other pictures like PNG in that case.

Hm given like almost 90% of Plasma UI is svg, svg itself might not be broken... Do you have specific example of what is broken?

Here is a screenshot! It renders fine on desktop, but on pinephone it has a distorted background somehow.

CC: @notmart any idea?

Marco Martin, [15.02.21 15:37]
(our svg graphics is done in sofware, rendered to qimage and the qimage cached on disk)

Mistakenly added ColorOverlay on top of Kirigami.Icon which was causing some rendering issues. Now icon color is set using the Kirigami.Icon.color property.
Initial testing shows images are rendering correctly now on pinephone.


[Feature Request] Add tags sort

I would like some tag to come first in API

Can you please clarify what you are trying to do, what the problem is, and what you would expect to happen instead?

Closing as stale.


0.1.2 - env.NewModule now local. Updated getTypeFromEnv & ModuleStmt

getTypeFromEnv now checks parent scope
ModuleStmt now uses NewModule
Added tests for type scope

Codecov Report

Merging #310 into master will decrease coverage by 0.13%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #310      +/-   ##
==========================================
- Coverage   92.02%   91.88%   -0.14%
==========================================
  Files           9        9
  Lines        2270     2281      +11
==========================================
+ Hits         2089     2096       +7
- Misses        118      122       +4
  Partials       63       63

Impacted Files
Coverage Δ

vm/env.go
98.16% <100%> (-1.84%)
:arrow_down:

vm/vm.go
86.83% <100%> (+0.68%)
:arrow_up:

vm/vmStmt.go
96.98% <100%> (-0.02%)
:arrow_down:

Continue to review full report at Codecov.

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

@mattn Good to merge. Could you make a release before merge and one after?

Thank you

@mattn Could you make a release?

Tagged. Thanks.


ValueError: not enough values to unpack (expected 3, got 2)

ValueError                                Traceback (most recent call last)
 in
113         else:
114             # segment the hand region
--> 115             hand = segment(gray)
116
117             # check whether hand region is segmented
 in segment(image, threshold)
34     # threshold the diff image so that we get the foreground
35     thresholded = cv2.threshold(diff, threshold, 255, cv2.THRESH_BINARY)[1]
---> 36     (_, cnts, _) = cv2.findContours(thresholded.copy(), cv2.RETR_EXTERNAL, cv2.CHAIN_APPROX_SIMPLE)
37     if len(cnts) == 0:
38         return
ValueError: not enough values to unpack (expected 3, got 2)

Change the line to:
(cnts, _) = cv2.findContours(thresholded.copy(), cv2.RETR_EXTERNAL,cv2.CHAIN_APPROX_SIMPLE)

@cardboardcode solution works as with OpenCV>=4.0. @anantSinghCross Please close this issue.


fixed handling of empty sketches

Coverage decreased (-0.008%) to 96.166% when pulling eb65ba95e2c7d898c02f342b8549d285617a5a16 on fix-merging-empty into daccea18f3b26eb228772160ef2b279918c9bc03 on master.


Feat/force permission

based on https://github.com/gogovan/flutter-force-permission/pull/1

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@a74009f). Click here to learn what that means.
Patch has no changes to coverable lines.

Additional details and impacted files
@@           Coverage Diff           @@
##             main       #2   +/-   ##
=======================================
  Coverage        ?   77.40%
=======================================
  Files           ?        9
  Lines           ?      177
  Branches        ?        0
=======================================
  Hits            ?      137
  Misses          ?       40
  Partials        ?        0

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Wifi connection showing not connected - even when it is

I've successfully installed Spyguard on RaspOs Bookworm on  Raspberry Pi 4.
All works fine but it shows as Wifi not connected at the bottom right of the capture screen.
However, it is connected, scans and creates reports correctly.
I've tried swapping round the on board WiFi with usb dongle for AP and Internet link, but it makes no difference in either configuration.
Everything looks correct in the new network manager for bookworm sudo nmtui
Anyone else seen this issue  and found a solution ?

OS? nmcli installed?

Thank you for the suggestions - I have nmcli installed which was installed prior to installing Spyguard.
Hardware
Raspberry Pi 4 Model B Rev 1.4
OS
PRETTY_NAME="Debian GNU/Linux 12 (bookworm)"
NAME="Debian GNU/Linux"
VERSION_ID="12"
VERSION="12 (bookworm)"
VERSION_CODENAME=bookworm
ID=debian
Linux 6.1.0-rpi7-rpi-v8 #1 SMP PREEMPT Debian 1:6.1.63-1+rpt1 (2023-11-24) aarch64 GNU/Linux
eth0 and lo network Settings
eth0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
ether e4:5f:01:63:77:07  txqueuelen 1000  (Ethernet)
RX packets 0  bytes 0 (0.0 B)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 0  bytes 0 (0.0 B)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
inet <IP_ADDRESS>  netmask <IP_ADDRESS>
inet6 ::1  prefixlen 128  scopeid 0x10
loop  txqueuelen 1000  (Local Loopback)
RX packets 55405  bytes 5091882 (4.8 MiB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 55405  bytes 5091882 (4.8 MiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
Not sure if anything jumps out in the above ?  I have swapped over wlan0 and wlan1 but that doesn't seem to make any difference. The scan and reports work in either of these configurations although I understand the preferred arrangement is wlan1 for internet and wlan0 for AP which is how I've got it set up ?

Sorry if this is looping the same question/answer as above, but have you gone into raspi-config (opt 5 then AA from memory) and changed the network handler to nmcli?  This one got me repeatedly.

Yeah the raspi-config is different in bookworm.  Out of interest, do you have a USB WiFi stick you can plug in and see if you get the same issue?

Good News !  I've reinstalled Spyguard and it now appears to be working !
Thank you for the suggestion - I should have tried that first !
The only weird thing is if I use wlan0 as the access point and wlan1 for the internet connection it fails to create the access point.
If  I reverse the adapters in the backend  its works fine. Not sure why its behaving that way. But at least its working with Access point wlan1 and internet wlan0 .
Be nice to understand what causes that issue but at least its up and running.
Thank you

Just checked the syslog , and yes I see   nl80211 driver interface is not designed to be used with ap_scan=2  message.
I guess this is an issue with the particular usb wifi dongle I'm using ( RALINK 5370  802.11N)  I've also tried an Asus N150 -USB N10 Nano.
The RALINK will allow devices to connect and run scans but only when AP is set to Ralink adapter and Internet to onboard Wi-Fi (atheros 8495)
The ASUS creates the AP but nothing will connect,
I'm guessing this is a driver issue? Anyway to fix it or will I need to get hold of specific usb wifi adapter ?

I'll have a look at it in the next few days and then answer you here.


Plate replicate rollups and AbDisc assay re-import

Rationale
Introduces support for the calculation of standard deviation and mean values for replicate well groups for protocols that support plate metadata in LKB folders. Replicate aggregates are computed for numerical measures in the results domain and are automatically joined to the results views.
In support of LKB AB discovery scenarios (and potentially others), this also introduces the notion of the addition of assay run data over time through the existing assay run re-import feature. Plate set plate data can be added to a run over multiple imports. The server will attempt to combine / merge prior data with new data on a plate boundary within a single plate set during each subsequent import / re-import.
Changes

Create a protocol schema domain : AssayPlateReplicateStats to store the replicate standard deviation and mean values. One row per replicate well group per run will be created.
When the assay results domain changes, create fields in the AssayPlateReplicateStats domain to track any numeric measures.
On insert, compute and save replicate stat values to the protocol schema table.
Join the assay results table to the replicate stats table.
AssayPlateTriggerFactory to handle updates and deletes on the results table. Depending on whether the updates occur on replicate well group rows, recompute and update replicate stats. Unfortunately, assays handle inserts and updates via different code paths, the former happens in
AssayRunUploadContext.ReImportOption enum to control the server side re-import behavior. The parameter can be passed into the ImportRunApiAction and defaults to the current behavior of REPLACE.
AssayPlateMetadataServiceImpl.mergeReRunData handles the details of merging current and previous results data. If data is merged, the uploaded data is replaced with the tsv tabular representation of the combined data and the data output ExpData is updated to reflect the change. This is always the case regardless of whether previous or current data is in the graphical format.
Hit selections are now cleared from the previous run regardless of whether this is a straight re-import or the ABDisc re-import where plate set data can potentially be merged.
Hit selections are propagated in the merge case on a plate by plate basis if the new data is not replacing any existing plate data. The implementation was a little disjointed so here are the details:

Hit re-selection needs to be done after new assay results have been persisted because we need the result row IDs. This happens in PlateMetadataImportHelper.afterBatchInsert.
We only know about the incoming versus existing plate data during the parse phase of the new data file. This happens in AssayPlateMetadataServiceImpl.mergeReRunData. We end up removing all hit selections that we do not plan to carry forward based on our plate merge policy. Any remaining hits are carried forward in the ImportHelper.

Debug Notes

Until the client dev is in place, the assay run re-import behavior can be controlled by changing the default reImportOption in the ImportRunApiForm around ImportRunApiAction:356

implementation Details
Statistical values should appear automatically in the default view of the results table. Stats fields should be aligned close to their source.

After the re-import case if data is combined with a previous run

Related Pull Requests
https://github.com/LabKey/commonAssays/pull/813

One thing we may want to do is apply a standard format for decimal/float-based columns; with the default format we end up not rounding numbers we probably ought to round in our mean/stddev calculation column:


Improve Scroll Bar UI

Description
The current Scroll bar Ui has a very basic layout and outdated design. The Thumb and Track has outdated and default styling. Enhancing the colour scheme of Thumb and Track, improving spacing and modernizing the scroll bar design would greatly improve the user experience and website presentation
https://github.com/user-attachments/assets/e0951d25-9455-4271-980f-8f4b57410eb4
Tasks:
Redesign the Scroll bar for better visual appeal.
Improving the scroll bar thump and track.
@vivekvardhan2810  can you assign this issue to me

Okay @VidhanThakur09
Assigning this issue to you.
make sure to complete this issue for the next 2 days.
make sure to join discord channel: https://discord.gg/FZxBRpTEeH

Thank you for assigning this to me.
I will join the discord server.


[6.0] No upgrade path for authentication, NOT CSS, authentication, and app.css missing on new install.

Login in version 5.8 comes with app.css when you scaffold authentication.  Besides app.css I also have custom css for other views.
However I use the app.css for styling the login and register as is "out of box"
In another issue I got this for an answer:

This is only for new Laravel 6 apps. Existing apps are unaffected.

Wouldn't an upgrade from:
5.8 to 6.0
Be considered a new 6.0? Again, since this is an upgrade to 6.0, thus it should be considered as a new 6.0 after a proper upgrade,  there is nothing as to how to properly handle app.css.
Also I still don't understand why app.css needs compiling, as it's required to compile it in 6.0.
6.0 left out any sentence to the effect:

Compiling assets is optional.

I have used Laravel since ver 4.2 and compiling assets has never been mandatory.
If you search the chapter on authentication for the following words:

compile
mix
sass
less
node

None of those words show up.
The chapter does say:

The ui command will also create a resources/views/layouts directory containing a base layout for your application. All of these views use the Bootstrap CSS framework, but you are free to customize them however you wish.

So according to the chapter on authentication, this layout should be ready to use out of box without compiling anything.  There should at least be the standard app.cs as was in previous versions.
Yet even when I tested a new install, there was no app.css, yet in the layout it's calling for app.css.
The authentication chapter says nothing about having to compile anything.
One single file used for login and register to style, app.css, should be there ready to go, and should not have to be compiled.
Can more than one person look over this issue as having to compile one file only doesn't make sense.
That is forcing someone to have to install node js and npm.  Having to install two extra programs to only compile one single file?

I've been following all of your posts trying to understand, but just can't follow.  Compiling is never required. Concerning a new project, if you don't want to use any build tools, just drop your css in public and go to town. Also can't figure out why you seem to be the only one bringing this up. I could be missing something, but I've upgraded several apps, a couple of which do not use build tools, and everything just works.

just drop your css in public and go to town.

That does make sense, however in a brand-new install then, how do you get app. CSS.
You want the new one not an older one.
Seems you have to compile for that to be generated.
What I did on a new install is download bootstrap. CSS copy renamed to app.css.
Is this the correct way if not compiling assets.

What I did on a new install is download bootstrap. CSS copy renamed to app.css.

You can do exactly that.
Still, to always have the "most up-to-date" bootstrap css file for example, having it in package.json and compile it will always be best option since you don't have to download new versions yourself

@RFreij  thanks for the reply.  I figured that.  Weird that the docs for 5.8 had:
php artisan preset none

Yet 6.0 says nothing about compiling assets is optional.  Yes an experienced person knows this.  But in a fresh install, and a fresh scaffolded Auth, it would be nice to have the app.css "out of box" like previous versions had.
And app.css never needed compiling in the past.
The issue is there in no app.css out of box, it's only generated once you compile.
I can't seem to get that point across.
It seems as though the developers are in essence:

Forcing new to laravel folks to compile and use mix.  Those that don't realize it's optional.

If that is the case, not saying it is, why don't someone just say:
"Yes that's the case".  At least then I will know there is no true issue.  But if that's not the case, new to laravel folks should at least see that compiling assets is very optional.
I can see it on a large app, but smaller apps (intranets) I can't see having to compile custom css.
At least let me know the intent of not letting some know, "Hey compiling is optional".

whats the big problem with having to "compile" the css?
also i think part of the confusion here is you keep going on about "upgrade". while this has nothing to do with upgrading, it will only effect brand new laravel 6.0 apps

it will only effect brand new laravel 6.0 apps

I know.  I want, wish someone couls answer this:
Are the developers forcing compiling assets now on those new to laravel, who may not realize it's optional. As npm was never required in the past.
I've been doing this stuff 32 years now, so I know better.
Just answer the simple question:
Is it yes or no.
If yes, there's no issue, if no there needs to be at least a sentence to let newbie's know it's optional.
Please just be frank, please.


chore(functions): improve emulator debugging code

I wasn't able to isolate the cause of the flaky GCF tests. 🙁
This PR adds better debugging code, which should hopefully show us what the problem is.

Tests are passing; I'm going to re-run this to see if I can trigger a(nother) flake.

@ace-n This passes, should I merge it?

We can merge it for now; hopefully it will provide details should another flake occur.


add bun 1.1 runtime

This pr add bun 1.1 runtime, it's copied from 1.0 and updated Dockerfile and readme.

Closing this PR in favour of https://github.com/open-runtimes/open-runtimes/pull/301
This repository had a refactor regarding folder structure, and it would be hard to apply nessessary changes to existing PRs.


mailmap: fixed (all?) author names inconsistencies

Ran Levensthein diff on all author names to spot and fix inconsistencies. Used authors' most recently used name and emails as canonical.
This effectively removes 40+ phantom authors, like such as the infamous Marti Bolivar, Martí Bolívar's infamous doppelgänger. @mbolivar

@nashif does this have your +1? Thanks!

@nashif sorry, just force-pushed one last omission before seeing you had +1'd :/


Short solution needed: "How to get current timestamp" (nodejs)

Please help us write most modern and shortest code solution for this issue:
How to get current timestamp (technology: nodejs)
Fast way
Just write the code solution in the comments.
Prefered way

Create pull request with a new code file inside inbox folder.
Don't forget to use comments explain solution.
Link to this issue in comments of pull request.

How to get current timestamp


auxview focus + keybindings

A few fixes for focus and keybindings around auxview
currently aichat focus doesn't work correctly, but everything else works

Sorry for the delay, this looks good to me!!


Tweaks on isSingleHTMLFile

Move isSingleHTMLFile function to page-detect.ts (despite https://github.com/sindresorhus/refined-github/pull/2505#discussion_r339354154) add add tests
Handle edge cases (e.g. https://github.com/<user>/<name>.html)

Test

https://github.com/sindresorhus/refined-github/blob/master/source/options.html (is this fine?)

Argh, I wrote that comment incorrectly. I meant to say to keep that test in the feature's file since it's super specific to it.
The fixes to it are super welcome though.


BUG: mark command cannot handle sub-tasks well

will close all subtasks with same content, without care about the uplevel task

fixed by PR #21


Rebase PR #631 (history-specific permissions) onto latest master

No functional changes, just a mechanical rebase of the changes in jazzband/django-simple-history#631 onto the latest master branch in the hopes of helping move that PR along.

Thanks for doing that.  If you add "This closes #631" to the description of the PR, once it gets merged then #631 will close automatically.  Looks like there is an issue to resolve in the pre-commit (flake8).

@rolandcrosby-check this needs to be rebased on master.

Closing this now that #1017 (the successor to #631) has been merged.


Hunt SIGBUS from Tensor::drop

This is a weird bug I still cannot tell the reasons. The program runs in a forward backward loop and gets killed by SIGBUS in less than five minutes (sometimes immediately). It's only happens on specific machine. I opened rust-gdb to catch the SIGBUS and it says SIGBUS raised from Tensor::drop, and the line number points to the end of a function. I would bet it's somewhat a CUDA memory error, but gather further information. Let me paste the details and to see if anyhow has thoughts.

OS: CentOS 7
CPU: Intel Xeon Processor (Skylake)
GPU: Tesla P100-PCIE-16GB
Python 3.6 and PyTorch 1.6.0 installed by pip3 install --user
CUDA 10.2 and CUDNN 7

GDB points the error happens here.
The GDB backtrace.
#0  0x00007fffab4b1cf0 in c10::cuda::CUDACachingAllocator::DeviceCachingAllocator::free_block(c10::cuda::CUDACachingAllocator::(anonymous namespace)::Block*) ()
   from /home/centos/.local/lib/python3.6/site-packages/torch/lib/libc10_cuda.so
#1  0x00007fffab4b38bb in c10::cuda::CUDACachingAllocator::raw_delete(void*) () from /home/centos/.local/lib/python3.6/site-packages/torch/lib/libc10_cuda.so
#2  0x00007fffac8b59cd in c10::TensorImpl::release_resources() () from /home/centos/.local/lib/python3.6/site-packages/torch/lib/libc10.so
#3  0x000055555583bbdb in c10::intrusive_ptr<c10::TensorImpl, c10::UndefinedTensorImpl>::reset_ (this=0x7ffbf5313280) at /opt/rh/devtoolset-9/root/usr/include/c++/9/ext/atomicity.h:69
#4  c10::intrusive_ptr<c10::TensorImpl, c10::UndefinedTensorImpl>::~intrusive_ptr (this=0x7ffbf5313280, __in_chrg=<optimized out>)
    at /home/centos/.local/lib/python3.6/site-packages/torch/include/c10/util/intrusive_ptr.h:249
#5  at::Tensor::~Tensor (this=0x7ffbf5313280, __in_chrg=<optimized out>) at /home/centos/.local/lib/python3.6/site-packages/torch/include/ATen/core/TensorBody.h:86
#6  torch::autograd::AutogradMeta::~AutogradMeta (this=0x7ffbf5313270, __in_chrg=<optimized out>)
    at /home/centos/.local/lib/python3.6/site-packages/torch/include/torch/csrc/autograd/variable.h:189
#7  torch::autograd::AutogradMeta::~AutogradMeta (this=0x7ffbf5313270, __in_chrg=<optimized out>)
    at /home/centos/.local/lib/python3.6/site-packages/torch/include/torch/csrc/autograd/variable.h:189
#8  0x00007fffac8b59a0 in c10::TensorImpl::release_resources() () from /home/centos/.local/lib/python3.6/site-packages/torch/lib/libc10.so
#9  0x000055555584400a in c10::intrusive_ptr<c10::TensorImpl, c10::UndefinedTensorImpl>::reset_ (this=0x7ffbf5313330) at /opt/rh/devtoolset-9/root/usr/include/c++/9/bits/atomic_base.h:326
#10 0x00005555558440d7 in c10::intrusive_ptr<c10::TensorImpl, c10::UndefinedTensorImpl>::~intrusive_ptr (this=0x7ffbf5313330, __in_chrg=<optimized out>)
    at /home/centos/.local/lib/python3.6/site-packages/torch/include/c10/util/intrusive_ptr.h:248
#11 at::Tensor::~Tensor (this=0x7ffbf5313330, __in_chrg=<optimized out>) at /home/centos/.local/lib/python3.6/site-packages/torch/include/ATen/core/TensorBody.h:86
#12 at_free (t=0x7ffbf5313330) at libtch/torch_api.cpp:374
#13 0x000055555582bcbe in <tch::wrappers::tensor::Tensor as core::ops::drop::Drop>::drop (self=<optimized out>)
    at /home/centos/.cargo/registry/src/github.com-1ecc6299db9ec823/tch-0.2.0/src/wrappers/tensor.rs:470
#14 0x000055555571dd0f in core::ptr::drop_in_place () at /home/centos/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/ptr/mod.rs:175
#15 core::ptr::drop_in_place () at /home/centos/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/ptr/mod.rs:175
#16 <alloc::vec::Vec<T> as core::ops::drop::Drop>::drop (self=0x7fff4d7ed5a0)
    at /home/centos/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/alloc/src/vec.rs:2637
#17 core::ptr::drop_in_place () at /home/centos/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/ptr/mod.rs:175
#18 core::ptr::drop_in_place () at /home/centos/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/ptr/mod.rs:175
#19 core::ptr::drop_in_place () at /home/centos/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/ptr/mod.rs:175
#20 core::ptr::drop_in_place () at /home/centos/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/ptr/mod.rs:175
#21 alloc::sync::Arc<T>::drop_slow (self=0x7fffa837d2d8) at /home/centos/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/alloc/src/sync.rs:934
#22 0x00005555556432cc in train::train_worker (config=..., input_channels=<optimized out>, num_classes=<optimized out>, training_rx=...) at src/train/main.rs:134
#23 0x00005555556f1499 in train::main::main::{{closure}}::{{closure}} () at src/train/main.rs:61
#24 blocking::unblock::{{closure}}::{{closure}} () at /home/centos/.cargo/registry/src/github.com-1ecc6299db9ec823/blocking-1.0.0/src/lib.rs:303
#25 <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll (self=..., cx=0x7fffa837d6b0)
    at /home/centos/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/future/mod.rs:80
#26 blocking::Executor::spawn::{{closure}} () at /home/centos/.cargo/registry/src/github.com-1ecc6299db9ec823/blocking-1.0.0/src/lib.rs:187
#27 <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll (self=..., cx=0x7fffa837d6b0)
    at /home/centos/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/future/mod.rs:80
#28 0x00005555558deff4 in blocking::Runnable::run (self=...) at /home/centos/.cargo/registry/src/github.com-1ecc6299db9ec823/blocking-1.0.0/src/lib.rs:133
#29 0x00005555558df226 in blocking::Executor::main_loop::{{closure}} () at /home/centos/.cargo/registry/src/github.com-1ecc6299db9ec823/blocking-1.0.0/src/lib.rs:215
#30 std::panicking::try::do_call (data=<optimized out>) at /home/centos/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/panicking.rs:381
#31 std::panicking::try (f=...) at /home/centos/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/panicking.rs:345
#32 std::panic::catch_unwind (f=...) at /home/centos/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/panic.rs:382
#33 blocking::Executor::main_loop (self=0x555555b40050 <blocking::EXECUTOR+8>) at /home/centos/.cargo/registry/src/github.com-1ecc6299db9ec823/blocking-1.0.0/src/lib.rs:215
#34 0x00005555558dfa36 in blocking::Executor::grow_pool::{{closure}} () at /home/centos/.cargo/registry/src/github.com-1ecc6299db9ec823/blocking-1.0.0/src/lib.rs:267
#35 std::sys_common::backtrace::__rust_begin_short_backtrace (f=...)
    at /home/centos/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/sys_common/backtrace.rs:137
#36 0x00005555558e044a in std::thread::Builder::spawn_unchecked::{{closure}}::{{closure}} ()
    at /home/centos/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/thread/mod.rs:465
#37 <std::panic::AssertUnwindSafe<F> as core::ops::function::FnOnce<()>>::call_once (self=..., _args=<optimized out>)
    at /home/centos/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/panic.rs:308
#38 std::panicking::try::do_call (data=<optimized out>) at /home/centos/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/panicking.rs:381
#39 std::panicking::try (f=...) at /home/centos/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/panicking.rs:345
#40 std::panic::catch_unwind (f=...) at /home/centos/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/panic.rs:382
#41 std::thread::Builder::spawn_unchecked::{{closure}} () at /home/centos/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/thread/mod.rs:464
#42 core::ops::function::FnOnce::call_once{{vtable-shim}} () at /home/centos/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/ops/function.rs:227
#43 0x0000555555939f7a in <alloc::boxed::Box<F> as core::ops::function::FnOnce<A>>::call_once () at /rustc/fc2daaae610b5515438b551a2f3706196a997f35/library/alloc/src/boxed.rs:1042
#44 <alloc::boxed::Box<F> as core::ops::function::FnOnce<A>>::call_once () at /rustc/fc2daaae610b5515438b551a2f3706196a997f35/library/alloc/src/boxed.rs:1042
#45 std::sys::unix::thread::Thread::new::thread_start () at library/std/src/sys/unix/thread.rs:87
#46 0x00007fffab956ea5 in start_thread (arg=0x7fffa8384700) at pthread_create.c:307
#47 0x00007fffabf6b8dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

It was solved by restricting the GPU usage via reducing the batch size. It might ve related to power issues.
Not sure whether it stems from tch, so I'm closing this issue..


[SPARK-32564][SQL][TEST][FOLLOWUP] Re-enable TPCDSQuerySuite with empty tables

What changes were proposed in this pull request?

This is the follow-up PR of #29384 to address the @cloud-fan comment: https://github.com/apache/spark/pull/29384#issuecomment-670595111
This PR re-enables TPCDSQuerySuite with empty tables for better test coverages.
Why are the changes needed?

For better test coverage.
Does this PR introduce any user-facing change?

No.
How was this patch tested?

Existing tests.

Test build #127222 has started for PR 29391 at commit 2922680.

Merged build finished. Test PASSed.

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

Test build #127222 has finished for PR 29391 at commit 2922680.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
class TPCDSQueryWithStatsSuite extends TPCDSQuerySuite

Merged build finished. Test PASSed.

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

Test build #127230 has started for PR 29391 at commit 43fcf8a.

Merged build finished. Test PASSed.

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

Merged to master/3.0.

Thanks, @dongjoon-hyun !

Test build #127230 has finished for PR 29391 at commit 43fcf8a.

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

Merged build finished. Test PASSed.

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


⚠ Bofrost.at has degraded performance

In 523a819, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1930 ms

Resolved: Bofrost.at performance has improved in ca059c8 after 29 minutes.


MudSelect bad performance with slow Network and does not show text when loading

Bug type
Component
Component name
MudSelect
What happened?
https://user-images.githubusercontent.com/88079618/202713928-f4f1da0d-a4d2-4c0a-afdf-38f0cea21ace.mp4
Very slow operation of the component with a small list (50 elements).
It is noticeable in the video that an excessive amount of data is being receive, which causes noticeable friezes for a slow connection.
For example, I added components from other libraries that work much faster and have a filtering function at the same time.
Also, instead of the text of the drop-down list, the key of the drop-down list is displayed until the page is fully loaded.
Expected behavior
Reduce the amount of data sent when dropdown a static list selection.
Significantly speed up the drawing of the drop-down list.
The text of the selected dropdown value will be immediately displayed on load, instead of the key as it is now.
Reproduction link
https://try.mudblazor.com/snippet/cOmGPvbWSBLbGSiy
Reproduction steps

Сreate a page with code

					MudSelect

						<MudSelect T="int" @bind-Value=@CurrenttId
						           SelectedValuesChanged="OnSelectedValuesChanged"
						           Label="@R("MudSelect")"
						           Margin="Margin.Dense"
						           Variant="Variant.Outlined"
						           AnchorOrigin="Origin.BottomCenter">
							@foreach (var s in SelectList)
							{
								<MudSelectItem Value="<EMAIL_ADDRESS>							}
						</MudSelect>

					RadzenDropDown
					<RadzenDropDown TValue="int" @bind-Value=@CurrenttId Placeholder="RadzenDropDown"
					                FilterCaseSensitivity="FilterCaseSensitivity.CaseInsensitive" AllowFiltering="true"
					                Data=SelectList TextProperty="Value" ValueProperty="Key"
					                Change="@DropDownChanged">
						<Template Context="select">
							@(select.Value)
						</Template>
						<ValueTemplate Context="select">
							@(select.Value)
						</ValueTemplate>
					</RadzenDropDown>

					antblazor

						<Select @bind-Value="@CurrenttId"
						        DefaultValue="@CurrenttId"
						        TItemValue="int"
						        TItem="int"
						        LabelInValue="true"
								EnableSearch>
							<SelectOptions>
								@foreach (var s in SelectList)
								{
									<SelectOption TItemValue="int" TItem="int"<EMAIL_ADDRESS><EMAIL_ADDRESS>								}
							</SelectOptions>
						</Select>

				Selected id: @CurrenttId

			@code {

    public IDictionary<int, string> SelectList { get; set; }
    public int CurrenttId { get; set; }
    public string CurrenttText { get; set; }

    protected override async Task OnInitializedAsync()
    {
        SelectList = new Dictionary<int, string>();
        for (int i = 10; i < 60; i++)
        {
	        var text = $"Custom Text (id:{i})";
	        SelectList.Add(i, text);
        }

        CurrenttId = 30;
    }

    private async Task OnSelectedValuesChanged(IEnumerable<int> values)
    {        return;    }
    private async Task DropDownChanged(object obj)
    {     return;    }
    private void OnSelectedValuesChangedAntblazor(int obj)
    {	    return;    }

 Start the project

 Set emulation of a slow internet connection in devtools (3g slow)

 Open the MudBlazor dropdown

Relevant log output
No response
Version (bug)
6.1.2
Version (working)
No response
What browsers are you seeing the problem on?
Firefox, Chrome, Microsoft Edge, Safari, Other
On what operating system are you experiencing the issue?
Windows
Pull Request

[ ] I would like to do a Pull Request

Code of Conduct

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

It is WASM, right?

It is WASM, right?

No, ServerPrerendered.
I init a blazor component on a page, an MVC project.
@(await Html.RenderComponentAsync<ResultTable>(RenderMode.ServerPrerendered, new {CurrentId = Current.Id}))


click UI for linkml_round_trips/just_exacts.py

linkml_round_trips/just_exacts.py has been retired.
click CLIs have been added to

linkml_round_trips/just_exacts.py
use_modular_gd.py

but not

linkml_round_trips/modular_gd.py

some of this will be moot once we merge in #29


MUI datagrid v7 : issue with using sx in GridToolbarColumnsButton

Hi,
I am trying to use sx in GridToolbarColumnsButton but I am not able to use sx directly with GridToolbarColumnsButton, so i tried slotProps but it's not working. Please help.
Search keywords:

Hi,
How can I inherit GridColDef. Please help me fix this.

Below is my GridColDef :


Exceptions with the same domain as blocked requests unblock requests everywhere

Steps to reproduce

Add these rules:

||example.org^$replace=/<h1>[\s\S]*?<\/h1>/<iframe src="https:\/\/www.youtube.com\/embed\/dQw4w9WgXcQ"><\/iframe>/
||youtube.com/embed/
@@||youtube.com/embed/$domain=youtube.com|whatever.test

Go here - http://example.org/

Expected behavior

Iframe with youtube should be blocked.
Actual behavior

Requests are unblocked and iframe is not blocked.
Screenshot:

Your environment

AdGuard for Windows version 7.5 nightly 33 (build 3407, CL 1.7.114)

It seems like it is #1202 case. So the domain modifier matches not only the referrer domain but the target one also.

So, as far as I understand it's a correct behavior?
I checked it with another ad blockers (Adblock Plus and uBlock Origin) and it seems that both block this iframe with mentioned rules.

Yes, it is or at least it is intended behavior.
By the way, there is (still not merged) PR which adds the description: https://github.com/AdguardTeam/AdguardKnowledgeBase/pull/654/files

Maybe I don't understand something, but it's about blocking rules, not exceptions.
So what rule I should add if I want to unblock youtube.com/embed/ only on youtube.com and block it on any other website (without using ||youtube.com/embed/$domain=~youtube.com)?
If I'm not wrong, at the moment rule like this @@||youtube.com/embed/$domain=youtube.com is the same as just @@||youtube.com/embed/, what I think is strange.

The real case (this is a test website, but anyway) is here (canyoublockit.com) - https://github.com/AdguardTeam/AdguardFilters/issues/65132 and related to this (audiogon.com) - https://github.com/AdguardTeam/AdguardFilters/issues/64518
In Base filter is rule like this:
@@||cdn.bannersnack.com/banners/$image,subdocument,domain=cdn.bannersnack.com|audiogon.com
and it unblocks bannersnack.com ads on canyoublockit.com (and any other website I guess) due $domain=cdn.bannersnack.com, for me it looks weird.
It seems that we need to change exception rule to:
@@||cdn.bannersnack.com/banners/$~third-party,image,subdocument
@@||cdn.bannersnack.com/banners/$image,subdocument,domain=audiogon.com

and it will be works as expected.

If I'm not wrong, at the moment rule like this @@||youtube.com/embed/$domain=youtube.com is the same as just @@||youtube.com/embed/, what I think is strange.

Makes sense.
Let's make the scope of this $domain modifier quirk even narrower.
$domain modifier may be interpreted as a target domain when all these are true:

The target is of "DOCUMENT" type
The pattern does not target any domain (e.g. it does not start with ||)
We should support TLD in $document (see here)


Obj.magic unexpected behaviour

For following code snippet:
let x = "1";
let y = 2;
let z = Obj.magic(x) + y;
Js.log(z);

Expected Output: 3
Actual Output: 12
Is it expected behavior? or I am missing something.

That's logical, yeah. By using Obj.magic you tell the compiler that your string is an int, so it doesn't apply any treatment, leaving you with "1" + 2, which, in JS leaves you with "12".
You can do the following to ensure type safety:
let z = Belt.Int.fromString(x)->Belt.Option.getWithDefault(0) + y;


IE8 Event polyfill typo

https://github.com/Financial-Times/polyfill-service/blob/de07f9237ec4a73624e8f2479a1b308a7c8d56b0/polyfills/Event/polyfill-ie8.js#L99
The line:
listener = arguments[1].

Should be:
listener = arguments[1],

Thanks for reporting this.


chore: update node-sass

Fix #2660

@filipesilva Battling googlebot again? ;) The cla went bye bye.

@grizzm0 the struggle is real!


error "Can't remove headers after they are sent"

_http_outgoing.js:394
    throw new Error('Can\'t remove headers after they are sent');
     ^
Error: Can't remove headers after they are sent
    at ServerResponse.removeHeader (_http_outgoing.js:394:11)
    at clearHeaders (C:\Users\edupl\AppData\Roaming\npm\node_modules\serve\node_modules\send\index.js:908:9)
    at SendStream.error (C:\Users\edupl\AppData\Roaming\npm\node_modules\serve\node_modules\send\index.js:292:3)
    at SendStream.headersAlreadySent (C:\Users\edupl\AppData\Roaming\npm\node_modules\serve\node_modules\send\index.js:404:8)
    at SendStream.send (C:\Users\edupl\AppData\Roaming\npm\node_modules\serve\node_modules\send\index.js:625:10)
    at onstat (C:\Users\edupl\AppData\Roaming\npm\node_modules\serve\node_modules\send\index.js:737:10)

I just rolled back to version 5.0.4 and it fixed this for me

ok ... thanks gonna try this

How did you get this error? What's your setup and how does the command look?

@leo thanks!

:pray: 😊


use clang-16 && gcc-13 to build

Search before asking

[X] I had searched in the issues and found no similar issues.

Motivation
This issue has a request to use clang-16 and gcc-13 to build docker images or cmakelists.txt in local developing environment and use clang-tidy-16 and clang-format-16 to correct code formattings.
Solution
No response
Are you willing to submit a PR?

[ ] I'm willing to submit a PR!

@infdahai If Ubuntu 20.04 has clang-16 in its repository?

I have been using GCC 13 to build kvrocks for a long time and haven't encountered any issues so far.
Getting GCC 13 or Clang 16 in CI may require manual download and installation, but I don't object to adding new compiler builds in CI (currently, the default versions of GCC and Clang in both ubuntu20 and ubuntu22 are used in CI).

for clang-16, we can refer to
https://github.com/MikePopoloski/slang/blob/385e8e3a666551416fe76fcd9f0d6f0ba845b9bc/.github/workflows/build.yml#L40-L46
or
          wget https://apt.llvm.org/llvm.sh
          chmod +x llvm.sh
          sudo ./llvm.sh 16
          sudo apt-get install -y clang-tidy-16

for clang-16, we can refer to
https://github.com/MikePopoloski/slang/blob/385e8e3a666551416fe76fcd9f0d6f0ba845b9bc/.github/workflows/build.yml#L40-L46
or execute the shell script.
          wget https://apt.llvm.org/llvm.sh
          chmod +x llvm.sh
          sudo ./llvm.sh 16
          sudo apt-get install -y clang-tidy-16

But I havn't found a vaild example for gcc-13. What do you think @PragmaTwice or just pend for this?

We can add a PPA for ubuntu, refer to https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/ppa .

I was suggested to add a blank line at the end of the code when I submitted a PR, but now there are no rules for clang-format. I learned that the rule InsertNewlineAtEOF is supported in clang-format 16. Is it possible to update the clang-format version and add this rule?
https://clang.llvm.org/docs/ClangFormatStyleOptions.html#insertnewlineateof

I was suggested to add a blank line at the end of the code when I submitted a PR, but now there are no rules for clang-format. I learned that the rule InsertNewlineAtEOF is supported in clang-format 16. Is it possible to update the clang-format version and add this rule?
https://clang.llvm.org/docs/ClangFormatStyleOptions.html#insertnewlineateof


How can I assign values to slice of tensor object?

@sayakpaul  @gustheman
I am facing some issumes in the compute_mask() Code
I want to implement the code in the following way-
import tensorflow as tf

# following values are passed in the function from basic_layer
window_size = (2,7,7)
shift_size = (0,3,3)
D, H, W = 2, 14 , 14

img_mask = tf.zeros((1, D, H, W, 1))

cnt = tf.Variable(0, dtype= "float32")

for d in slice(-window_size[0]), slice(-window_size[0], -shift_size[0]), slice(-shift_size[0],None):
    for h in slice(-window_size[1]), slice(-window_size[1], -shift_size[1]), slice(-shift_size[1],None):
        for w in slice(-window_size[2]), slice(-window_size[2], -shift_size[2]), slice(-shift_size[2],None):
            img_mask[:, d, h, w, :] = cnt
            cnt = cnt + 1

It gives the following error-
TypeError                                 Traceback (most recent call last)
<ipython-input-6-d74222409084> in <module>()
     11     for h in slice(-window_size[1]), slice(-window_size[1], -shift_size[1]), slice(-shift_size[1],None):
     12         for w in slice(-window_size[2]), slice(-window_size[2], -shift_size[2]), slice(-shift_size[2],None):
---> 13             img_mask[:, d, h, w, :] = cnt
     14             cnt = cnt + 1

TypeError: 'tensorflow.python.framework.ops.EagerTensor' object does not support item assignment

Using np.zeros() instead of tf.zeros() runs the code successfully but it gives the following error while s initializing the model using tf.keras.Input() or saving the model-
TypeError: in user code:

    C:\Python\Python396\lib\site-packages\keras\saving\saving_utils.py:125 _wrapped_model  *
        outputs = model(*args, **kwargs)
    C:\Users\shoai\Codes\GSOC-22-Video-Swin-Transformers\VideoSwinTransformer\SwinTransformer3D.py:117 call  *
        x = layer(x)
    C:\Users\shoai\Codes\GSOC-22-Video-Swin-Transformers\VideoSwinTransformer\BasicLayer.py:169 call  *
        attn_mask = compute_mask(Dp.ref(), Hp.ref(), Wp.ref(), window_size, shift_size, None) #??
    C:\Users\shoai\Codes\GSOC-22-Video-Swin-Transformers\VideoSwinTransformer\BasicLayer.py:30 compute_mask  **
        img_mask = np.zeros((1, D, H, W, 1))

    TypeError: 'Tensor' object cannot be interpreted as an integer

This error occurs in the later case as D, H, W and elements of window_size & shift_size are passed into the function as Tensor object.
np.zeors() can not take Tensor object as input. So it has to be implemented using tf.zeros().
Now I need a way to assign values to slice of tensor object (img_mask).
Would you please suggest me how can I do the following assignment successully -
img_mask[:, d, h, w, :] = cnt

See how I am using a similar function here:
https://github.com/sayakpaul/swin-transformers-tf/blob/7a9be0c788e9ed0f2115d4744b302c2a1c8aac90/swins/blocks/swin_transformer_block.py#L98
I am pre-computing the attention masks and then initializing them so that numpy operations don't interfere with the TF graph:
https://github.com/sayakpaul/swin-transformers-tf/blob/7a9be0c788e9ed0f2115d4744b302c2a1c8aac90/swins/blocks/swin_transformer_block.py#L91

Also, I saw you're using PyTorch related stuff like .device. Please take care of those.
I think you won't be able to achieve einsum with einops within TensorFlow as those operations will become incompatible. Try using TensorFlow's einsum ops: https://www.tensorflow.org/api_docs/python/tf/einsum.

See how I am using a similar function here:
https://github.com/sayakpaul/swin-transformers-tf/blob/7a9be0c788e9ed0f2115d4744b302c2a1c8aac90/swins/blocks/swin_transformer_block.py#L98
I am pre-computing the attention masks and then initializing them so that numpy operations don't interfere with the TF graph:
https://github.com/sayakpaul/swin-transformers-tf/blob/7a9be0c788e9ed0f2115d4744b302c2a1c8aac90/swins/blocks/swin_transformer_block.py#L91

@sayakpaul  , I couldn't find a way to pre-compute the mask.
In the implementation of the PyTorch version of the Swin Transformer, the attention mask is also pre-calculated while initializing the SwinTransformerBlock. Link-
https://github.com/microsoft/Swin-Transformer/blob/main/models/swin_transformer.py#L223
But in the PyTorch implementation of Video Swin Transformer get_window_size  function is called from the forward call of BasicLayer. get_window_size returns  window_size and shift_size which are then used in compute_mask function.
Link-
https://github.com/SwinTransformer/Video-Swin-Transformer/blob/master/mmaction/models/backbones/swin_transformer.py#L400
This mask is computed at each of the BasicLayer and the same value is passed to all layers of SwinTransformerBlock3D of a BasicLayer.
Would you please give me some instructions on how I can pre-compute the mask or suggest any other way of implementing masking?

einsum

@sayakpaul  I haven't used einsum with einops. I have used einops's rearrange function.
In my code:
https://github.com/shoaib6174/GSOC-22-Video-Swin-Transformers/blob/main/VideoSwinTransformer/SwinTransformer3D.py#L119
PyTorch ref:
https://github.com/SwinTransformer/Video-Swin-Transformer/blob/master/mmaction/models/backbones/swin_transformer.py#L659
The documentation of einops states that it supports both PyTorch and TF.
Should I implement the rearrange function using tf.reshape or something else?

https://github.com/shoaib6174/GSOC-22-Video-Swin-Transformers/issues/3#issuecomment-1204405744
If einops works, I don't mind keeping it. But try doing it with native TensorFlow to see if it's possible to discard the dependence on einops.
Regarding precomputing masks, I think the resolution of the frames stays the same throughout training, right? If that's the case why can't we precompute the mask?

#3 (comment)
If einops works, I don't mind keeping it. But try doing it with native TensorFlow to see if it's possible to discard the dependence on einops.
Regarding precomputing masks, I think the resolution of the frames stays the same throughout training, right? If that's the case why can't we precompute the mask?

The resolution of the frames changes at each basic layer depending on the resolution of the input image. But I think pre-computing the mask will be possible if I provide the image_size as a parameter to the SwinTransformer3D while initializing.
The SwinTransformer takes image_size as a parameter  but The SwinTransformer3D does not.
Thank you for the hint @sayakpaul .
I am trying this.

@sayakpaul
I have successfully pre-compute the mask after passing the input shape as a parameter. I also used this parameter in padding and Patch Merging. Thank you for the suggestion.

Amazing!


Swift 4 version

Is there a swift 4 version in progress ?

@gwennguihal   check the latest version 0.5.2 its swift 4

@Alexookah I'm still getting errors in the new version :/
/Pods/AnimatedTextInput/AnimatedTextInput/Classes/AnimatedTextField.swift:104:75: Cannot convert value of type '[NSAttributedStringKey : Any]?' (aka 'Optional<Dictionary<NSString, Any>>') to expected argument type '[String : Any]?'
and many more...

@SLAppsDev do you use swift 4?

@Alexookah ohh no! :S, now that I've updated the pod it won't let me migrate to swift 4 because of the compile erros

remove from pods, migrate to swift 4 . then add again to pods ;)

@Alexookah all set thanks!!.

I think you guys might want to update the README file. The version info about installation was greatly misleading!


fix(deps): update terraform-module

This PR contains the following updates:

Package
Type
Update
Change

github.com/terraform-ibm-modules/terraform-ibm-watsonx-saas-da
module
minor
v1.7.15 -> v1.8.1

terraform-ibm-modules/cos/ibm (source)
module
patch
8.15.6 -> 8.15.9

Release Notes

terraform-ibm-modules/terraform-ibm-watsonx-saas-da (github.com/terraform-ibm-modules/terraform-ibm-watsonx-saas-da)
v1.8.1
Compare Source
Bug Fixes

updated the DA to claim controls from the IBM Cloud Framework for Financial Services version 1.7.0 profile (#228) (79defc7)

v1.8.0
Compare Source
Features

exposed the ability to set the provider_visibility in the DA Learn more(#227) (fced704), closes /registry.terraform.io/providers/IBM-Cloud/IBM/latest/docs#visibility-1

v1.7.17
Compare Source
Bug Fixes

increased the sleep from 5s to 10s to help prevent race condition (#199) (c9e8935)

v1.7.16
Compare Source
Bug Fixes

deps: update terraform terraform-ibm-modules/cos/ibm to v8.15.6 (#226) (58a46bc)

terraform-ibm-modules/terraform-ibm-cos (terraform-ibm-modules/cos/ibm)
v8.15.9
Compare Source
Bug Fixes

updated the DA to claim controls from the IBM Cloud Framework for Financial Services version 1.7.0 profile (#791) (861a0b1)

v8.15.8
Compare Source
Bug Fixes

revert "dependency_version_2": true until full migration path supported (#790) (16bd0ba)

v8.15.7
Compare Source
Bug Fixes

update the bucket DAs to opt into "dependency_version_2" features in catalog (#789) (6259ca4)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

/run pipeline

/run pipeline

/run pipeline

/run pipeline

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

GitHub release
v2.6.7

Your semantic-release bot :package::rocket:


4.2 breaks string literal conditional type checking.

Bug Report
In TypeScript 4.1, a type can be constrained conditionally to be a string literal.  In 4.2 conditionals can not enforce string literals
type StringLiteral<T> = T extends `${string & T}` ? T : never;

🔎 Search Terms
string literal, conditional types, breaking change
🕗 Version & Regression Information

This is a breaking change
This changed between versions 4.1 and 4.2
This is the behavior in every version I tried, and I reviewed the FAQ for entries about string literals
I was unable to test this on prior versions because string template literals were introduced in 4.1

⏯ Playground Link
Playground 4.1
Playground 4.2
💻 Code

// We want to only allow string literals
type StringLiteral<T> = T extends `${string & T}` ? T : never;

const literalToConstrainedLiteral : StringLiteral<'bob'> = 'bob'; // Should be allowed as bob is a string literal

// 4.1 and 4.2: Produces a GOOD compiler error as bob is constrained to be a literal.   No compiler error produced.
const stringToString : StringLiteral<string> = ('bob' as string);

// use case: Ensure that someone is only registering via a string literal.  Useful when using callback maps based on discriminated unions.
function registerAction<T>(action : StringLiteral<T>) {}

// This is good since 'clicked' is a literal
registerAction('clicked');

//4.1: GOOD: Produces a compiler error
//4.2: BAD: Compiler allows this
registerAction('clicked' as string);

🙁 Actual behavior
TypeScript 4.2 does not produce compiler errors when the type is too wide.
🙂 Expected behavior
Produces compiler errors when the type is too wide.

Seems like we didn't used to simplify `${string}` to string, which was probably a bug. I understand the desire for an "only assignable to string literals" operator, but I think the new behavior makes sense. I just can't look at the code that's provided and understand why `${string & T}` should ever reject string in the cases where T is instantiated with string.

Hmm, this was my train of thought - Since string literal templates should only allow literals as input then it makes sense that only a literal passed into a template can actually resolve to a literal type.
type AB<T extends string> = T extends `${string & T}AB` ? T : never;
type ABTest = AB<'foo'>; // makes sense that this is never.  The condition is: 'foo" extends 'fooAB'

type A<T extends string> = T extends `${string & T}A` ? T : never;
type ATest = A<'foo'>; // makes sense that this is never.  The condition is: 'foo" extends 'fooA'

type Same<T extends string> = T extends `${string & T}` ? T : never;
type SameTest = Same<'foo'>; // Should be 'foo' because -  The condition is: 'foo" extends 'foo'

playground
Next is for the sake of consistency and maintaining the spirt of literals being a narrowing mechanism.
//4.1: resolves in intellisense to `${string}`
//4.2: resolves in intellisense to string
type Foo = `${string & string}`;

//4.1: resolves in intellisense to `${number}`
//4.2: resolves in intellisense to `${number}`
type Num = `${number & number}`;

playground
I am using a string literal template, and I would hope that a string literal template would ALWAYS resolve to a string literal, and not promote the contents of the ${} outside the literal itself.  The input of a string literal template should always be a literal.  If it doesn't make sense for ${number} to widen, then neither should ${string}.
type NotReallyALiteral = `${string}`;
const someValue : NotReallyALiteral = ('something' as string);

Side note: this breaks all of my type declaration code if this is not a regression.

@ahejlsberg thoughts?

Daniel is correct, we used to not reduce `${string}` to string, but we now do--and it's the right thing to do. There should be no observable difference in behavior between those two types.
I'd suggesting writing the StringLiteral<T> type as this instead:
type StringLiteral<T> = T extends string ? string extends T ? never : T : never;

That works in both 4.1 and 4.2 and really makes more sense--it expresses anything that extends string but isn't string itself.

Thanks, and that's a super clever alternative.  Thank you all for your time on this!


Obtain user namespace from the extension instead of the controller config

Description:
The user namespace is obtained by the controller config file at the moment. But the user should be able to give the preferred namespace when executing the kubectl add api & kubectl update api commands. The microgateway deployment and service should be created in this namespace from the above commands.
Suggested Labels:

Suggested Assignees:

Affected Product Version:
OS, DB, other environment details and versions:
Steps to reproduce:
Related Issues:

This is added.


[20.09] samba: 4.12.5 -> 4.12.6, fix build on darwin

Upstream commit https://gitlab.com/samba-team/devel/samba/-/commit/6e263432
fixes compilation on BSD/macOS.
(cherry picked from commit 680bdea2f0a573a598f9b5714623043fa3724e3e, https://github.com/NixOS/nixpkgs/pull/98877)

Motivation for this change
ZHF 20.09 https://github.com/NixOS/nixpkgs/issues/97479
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[x] macOS
[x] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

@ofborg build smbclient python37Packages.pysmbc smbnetfs gvfs

WFM macos 10.14 too


[Feature][Manager] Support CLS data node

Description
Manager support CLS data node and CLS sink
Use case
No response
Are you willing to submit PR?

[X] Yes, I am willing to submit a PR!

Code of Conduct

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

there is no CLS user for InLong, all ClS PR and issues will close.


Could be optimized.

Hello,
I wonder if  the function scopeListsTranslations, could be optimized as who below:
In this way, we can save time calling once to $this->getTranslationsTable() and $this->getLocaleKey() and use the variables in anonymous functions
public function scopeListsTranslations(Builder $query, $translationField)
{
    $translationTable = $this->getTranslationsTable();
    $localeKey        = $this->getLocaleKey()
    $withFallback      = $this->useFallback();

    $query->
    select($this->getTable() . '.' . $this->getKeyName(), $translationTable . '.' . $translationField)->
    leftJoin($translationTable, $translationTable . '.' . $this->getRelationKey(), '=', $this->getTable() . '.' . $this->getKeyName())->
    where($translationTable . '.' . $this->getLocaleKey(), $this->locale());

    if ($withFallback)
    {
        $query->orWhere(function (Builder $q) use ($translationTable, $localeKey)
        {
            $q->
            where($translationTable . '.' . $localeKey, $this->getFallbackLocale())->
            whereNotIn($translationTable() . '.' . $this->getRelationKey(),
            function (QueryBuilder $q) use ($translationTable, $localeKey)
            {
                $q->
                    select($translationTable . '.' . $this->getRelationKey())->
                    from($translationTable)->
                    where($translationTable . '.' . $localeKey, $this->locale());
            });
        });
    }
}

I hope to help to optimize the code of this great package.
Kind Regards
Cayetano H. Osma

Added your suggestion to the code. Thanks!

Hi, thanks to keep in mind my suggestion. I hope to ear a new version from you soon.

On 31 Oct 2015, at 23:01, Dimitris Savvopoulos<EMAIL_ADDRESS>wrote:
Added your suggestion to the code. Thanks!
—
Reply to this email directly or view it on GitHub https://github.com/dimsav/laravel-translatable/issues/128#issuecomment-152779671.


chore: Add EC2 with ssh access from the world

this didn't work because the security group is doing inline rules, where as the policy is setup for working against the best practice of separate ingress / egress permissions definitions. we can add a separate policy specifically to target this best practice.


Events

Describe your bug here.
I'm trying to delete the events of a song from my week but the events keep triggering even though I delete the .JSON file, what do I do?
Command Prompt/Terminal logs (if existing)
No response
Are you modding a build from source or with Lua?
Lua
What is your build target?
Windows
Did you edit anything in this build? If so, mention or summarize your changes.
Yes, i make a KB Sawblade Event and a Saw Note (with Lua)

Have you tried the clear events button in the debug menu or deleted the "events" JSON file?

You could try to delete the events within the files in the data folder

it's maybe a script in the data folder, or in the scripts folder, or the custom event has a callback like on stepHit or onUpdate or something, or it's the events.json in the data folder.

yes, I have a script in the song and in the event there is a function onUpdate, what do I do?

i resolved my problem, i just moved the onUpdate function to the onEvent function and worked

it's on the .json file maybe


feat(firebase_messaging, android)!: android 13 notifications permission request

Description
PR checks if the app is running on android 13 and will check the app notification permissions. If none set or permissions not granted, a dialog box will appear requesting user notification permission.
I consider this a breaking change as there is certain configuration required such as targetSdkVersion & compileSdkVersion targeting android API 33.
Users will also need to have the android:exported="true" property set in app manifest on apps running on android 12 or higher.
Related Issues
closes https://github.com/firebase/flutterfire/issues/8720
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]).
This will ensure a smooth and quick review process. Updating the pubspec.yaml and changelogs is not required.

[ ] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[ ] My PR includes unit or integration tests for all changed/updated/fixed behaviors (See Contributor Guide).
[ ] All existing and new tests are passing.
[ ] I updated/added relevant documentation (doc comments with ///).
[ ] The analyzer (melos run analyze) does not report any problems on my PR.
[ ] I read and followed the Flutter Style Guide.
[ ] I signed the CLA.
[ ] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?

[X] Yes, this is a breaking change.
[] No, this is not a breaking change.

@russellwheatley According to msackman's comment, I think we also need to update getPermissions() method to check for:
final boolean areNotificationsEnabled = ContextHolder.getApplicationContext().checkSelfPermission(Manifest.permission.POST_NOTIFICATIONS) == PackageManager.PERMISSION_GRANTED;

@MarcinusX That makes sense. I'll update the PR 👍


Added amazon-freertos-—-esp32-support article to the blog

This PR adds a new article named amazon-freertos-—-esp32-support to the blog.

Deprecated, won't be migrated.


How to connect to Kafka with SSL endpoint enabled?

We are struggling with SSL configuration to connect to a SSL enabled endpoint.
It would be awesome to have an example on how to achieve that in the project README.md. Maybe an SSL connection section?

+1 on that, the Readme only mentions that it's necessary to pass a sslOptions object to the Client constructor but there are no documentation about what those options are.

We pass those options directly to tls.connect call. See node's TLS module
We also test SSL in our code. Hope that helps.


Inaccurate wallet balance

When autopilot opens channels for my node it does not refresh my wallet balance. Sometimes I try and send on-chain funds and Zap tells me I don't have sufficient balance. I then look and realize autopilot opened a few channels for me and the funds have gone to opening channels but my wallet balance doesn't reflect that

Another issue / possible explanation is that LND doesn't let you spend change until the transaction has a certain amount of depth in the chain (6 blocks, I think?). Would be nice to be able to either open several channels at once in pay-to-many, or issue unconfirmed transactions following from your own change (because unlike incoming funds, it won't disappear if the transaction is reverted in a 51% situation). Both would be changes to LND I believe.


Back / Forward navigation slow and unresponsive

Search before asking

[X] I had searched in the issues and found no similar issues.

Operating System

[X] macOS
[ ] Windows
[ ] Linux

Operating System Version
macOS 14.2.1
It happens on the web browser too?
No, it just happens on the Desktop app
Rocket.Chat Desktop App Version
3.9.14
Rocket.Chat Server Version
6.6.1
Describe the bug
Since one of the last few RC upgrades the Forward / Back action in the desktop client reacts very sluggishly or even not at all (sometimes pressing the shortcut 2 - 3 times is necessary).
Both the shortcuts as well as clicking the menu items result in the same behaviour.
How to Reproduce

Install the given versions
Navigate between a few channels
Try to use the Back / Forward actions

Describe your Expected behavior
Back / Forward to work without delay and every time, like it did for years prior.
Anything else
Happens every time
Are you willing to submit a code contribution?

[ ] Yes, I am willing to submit a Pull Request!

@jeanfbrito Yes, Apple Silicon (Macbook Air M2)
I'll have to check with colleagues if they also experience this.

@jeanfbrito Yes, Apple Silicon (Macbook Air M2) I'll have to check with colleagues if they also experience this.

Can't the process get lagged?

Not sure what you mean by that

Sorry, slowed I mean. Did you have any customization on the server?
Can you say if this happens on our server open.rocket.chat too?
Its the first time I see this kind of report.


fix: fix broken conflict resolver check

small fix to add a default to the conflictResolutionStrategy Interface. This means that if the user provides a resolution function for a specific mutation then they do not need to name all as the default can also be defined.

This looks fantastic! going to verify after test fix.


docs: broken protobuf links in reference documentation

See the Access Context Manager Client for both the new and previous surfaces - the descriptions should be linking to protobuf description pages, but they are broken.
This is also happening for some @see tags in the parameter descriptions

Confirmed these have been fixed!


get started on async functionality

This branch introduces async behavior. Fixes #138.
TODO:

[ ] create runner that converts all existing operation tests to be async

I'd like to propose design for this:

Separate operators and execution logic (#153).
Create AsyncExecutor. It probably will extend StaticExecutor behavior
AsyncExecutor waits for promises to resolve until pass the results into operators

@crcn any timeline when this async functionality feature will be added to master?


Ability to specify arguments for falcosidekick-ui via helm charts

Motivation
falcosidekick-ui offers multiple options like below which can be provided as arguments to executable. These options cannot be used by official falcosidekick helm  charts. I specifically wanted to use option -t to configure TTL for keys stored in redis but official helm charts are not allowing me to do so.
Usage of Falcosidekick-UI:
-a string
      Listen Address (default "<IP_ADDRESS>", environment "FALCOSIDEKICK_UI_ADDR")
-d    Enable dark mode as default
-p int
      Listen Port (default 2802, environment "FALCOSIDEKICK_UI_PORT")
-r string
      Redis server address (default "localhost:6379", environment "FALCOSIDEKICK_UI_REDIS_URL")
-t int
      TTL for keys (default 0, environment "FALCOSIDEKICK_UI_TTL")
-x    Allow CORS for development (environment "FALCOSIDEKICK_UI_DEV")

Feature
Below configurable option is nice to have to allow helm charts user to provide extra environment configuration to falcosidekick-ui
webui:
  extraEnv: []

OR
webui:
  extraArgs: []

OR BOTH
Alternatives
Every user create their own custom chart if they wish to use falcosidekick-ui options
Additional info
If you think this feature request is valid, please approve. I am happy to create a PR to include webui.extraArgs: [] or webui.extraEnv: []

FYI the TTL feature is in master branch but not yet released. When it will be available I'll update the helm for allowing extra args as requested.

Thanks @Issif

@Issif Any updates on this?

In the next weeks, I've a little more time to release the new versions of Falcosidekick and Falcosidekick-UI, I hope to do so before Christmas.

@Issif Any update on this ?

Hi,
I faced issues with the CI for the release of UI before my holidays, I'm back and the releases of sidekick and UI are my top prios. The chart update will follow, the PR is ready.

Hey @Issif, is this ttl value supposed to be in seconds? Chart says value should be an integer. But does not specify the unit.

Yes it is :sweat_smile:
https://redis.io/commands/ttl/

Unless I am missing something, but this looks like a related missing setting. I am using the ingress setting for the Falco Sidekick UI and it doesn't actually seem to work since I cannot set the FALCOSIDEKICK_UI_ADDR and it is not correctly set to the host name, and as a result, I am getting a 404 on all of the resources needed to load the UI. Is there any kind of workaround that you can think of for now? Or will I have to use a port-forward to access the Falco Sidekick UI?

@benglewis can you provide your config please.

'[{"driver": {"enabled": true, "kind": "modern-bpf"}, "collectors": {"enabled": true, "containerd": {"enabled": true, "socket": "/run/containerd/containerd.sock"}}, "falcoctl": {"artifact": {"install": {"enabled": true}, "follow": {"enabled": true}}, "config": {"artifact": {"install": {"refs": ["falco-rules:3"]}, "follow": {"refs": ["falco-rules:3"]}}}}, "tty": true, "falco": {"grpc": {"enabled": true}, "grpc_output": {"enabled": true}, "webserver": {"enabled": true, "k8s_healthz_endpoint": "/healthz", "listen_port": 8765, "prometheus_metrics_enabled": true, "ssl_enabled": false, "threadiness": 0}, "metrics": {"convert_memory_to_mb": true, "enabled": true, "include_empty_values": false, "interval": "1h", "kernel_event_counters_enabled": true, "libbpf_stats_enabled": true, "output_rule": true, "resource_utilization_enabled": true, "rules_counters_enabled": true, "state_counters_enabled": true}}, "falcosidekick": {"enabled": true, "webui": {"enabled": true, "user": "REDACTED:REDACTED", "service": {"type": "NodePort", "annotations": {"cloud.google.com/neg": "{\\"ingress\\": true}", "cloud.google.com/app-protocols": "{\\"http\\": \\"HTTP\\"}"}}, "ingress": {"enabled": true, "annotations": {"kubernetes.io/ingress.class": "gce-internal", "kubernetes.io/ingress.allow-http": "true", "networking.gke.io/v1beta1.FrontendConfig": "frontend-config"}, "hosts": [{"host": "falcosidekick-ui.falco.mvp.dev.hirundo.io", "paths": [{"path": "/"}]}]}}}}]'

Can you try by also setting the ingressClassname?
falcosidekick:
  webui:
    ingress:
      ingressClassName: "gce-internal"

Any reason why the service is using NodePort and not ClusterIP? Is that a requirement from GKE?

I think that I took the NodePort option due to this note on this GCP GKE page: https://cloud.google.com/kubernetes-engine/docs/concepts/ingress#multiple_backend_services
But I realize now that I actually can use container native load balancing from the looks of it, so I will try changing it to ClusterIP instead. I will also try the ingressClassName option. I need a few minutes to apply this and take a look. I will update here :)

I tried setting ClusterIP and ingressClassName and it didn't help. Here's what I see:


Add requirements

What python versions does it run on?
pip install selenium
download chromedrive.exe link

And maybe an alternative of chromedrive.exe for Mac/Linux


Clean up git history

I would suggest to squash the git history in order to clean up the issues there. Possibly into just a single commit. For example 4a754d5a798069a9e4af69f03d408bfdbba10835 commits a huge 42MB binary (executable) blob that unnecessary bloats the repo.
If you don't want to change master I suggest to push the squashed history into a new main branch, make it the default branch (and just delete master later on)

Done, Thanks


Add basic export features

[x] #8

Removed #9 from this epic as that feature was moved further back.


cmd Transform: InitConfig must happen first

InitConfig() block (cmd/transform.go#L3) must happen before InitLogger because the latter uses viperConfig.

Closing as this isn't an issue as memory for viper object is allocated in init() https://github.com/fusor/cpma/blob/master/pkg/env/env.go#L29


rdf-toolkit replaces "-x-" in private use language subtags with "-X-"

Private use subtags are represented with lowercase "-x-"; see https://www.w3.org/International/articles/language-tags/. My specific use case is the tag "bo-x-ewts" for Extended Wylie transliteration of Tibetan. The uppercasing of the "x" is turning this into a malformed private use tag that will not be recognized by the community.

Yes, this is obviously a bug - we will fix it soon.
@rjyounes thanks for your feedback - much appreciated/


Add: Channel sign and API sign method for client and update Readme

Hey @FZambia
Added channel sign and api method into Ruby client. Updated Readme with instructions to sign channels with a specific Rails example.
Please review and merge.
Cheers

@FZambia looks like authentication error, Please check.

@gauravtiwari thanks a lot for improvements! I think travis builds failed because you changed sign method (it not using project_key anymore) while process method in this line https://github.com/centrifugal/centrifuge-ruby/blob/master/lib/centrifuge/builder.rb#L13 calls it with just a body.
client.sign(body[:data])

I think if you pass project_key then everything will work. Unfortunately I am not skilled in Ruby, @arrowcircle, could you help us here?

Sure, let me fix this.

@FZambia I think should work now (all tests passing), once travis builds are finished. (Travis-CI is down at the moment).

generate_api_sign does the same as sign. I don't think we should add new method with the same functionality.

Okay I see. Cent python lib has this method.

But I see your point, we could use the same sign method to generate api_sign. Just need to pass the data, like so: client.sign(data)

@FZambia I have removed the duplicate sign method and improved docs. See here: https://github.com/gauravtiwari/centrifuge-ruby#channel-sign-token-generation , plus https://github.com/gauravtiwari/centrifuge-ruby#api-request-sign

Great, thank you very much for your work here!

@FZambia should I release new version of gem?

@arrowcircle I think it would be nice, I also started work in separate branch (https://github.com/centrifugal/centrifuge-ruby/tree/single_project) - I am planning to drop support for multiple projects registered in Centrifugo (see https://github.com/centrifugal/centrifugo/issues/33).  There are some refactoring to get rid of project_key. Will appreciate your point on this change.

@FZambia I think that's the ideal way for Centrifugo to work. In most cases, people would be using this for a single project in production environment so, it doesn't make sense to support multiple projects, which brings additional complexity - scaling, configuration etc.
Have you seen a gem called Slanger. It's based on Pusher protocol and uses all Pusher libraries except the server, and the server only work for a single project.

@gauravtiwari thanks for feedback, I have not seen Slanger before - looks great, and being compatible with pusher protocol is a great win in terms of client libraries for various languages.

@gauravtiwari If you are looking for pusher backend look at https://github.com/edgurgel/poxa

@arrowcircle It's very similar to Slanger, although written in Elixer. I have used Slanger in production and it works pretty good.
@FZambia May be we can extend Centrifugo client side libraries - borrow some ideas from Pusher? I noticed couple of bugs that I will report as a separate issue.

@gauravtiwari depends on what you want to borrow


DISCUSSION: Make pureComputed the default

From https://github.com/knockout/knockout/issues/2167  by @futpib
I'm moving this here since this is where it could be accepted (for ko-4).
Make pureComputed the default computed and make computed impureComputed or even `autorun

I find that, when choosing between pureComputed and computed, pureComputed is almost always the right one due to laziness and performance benefits.

You really want computed only when you want immediate and predictable evaluation for side-effects.

Also you almost certainly want to break your computed in two parts with ignoreDependencies to make sure evaluation happens only when you want:

ko.computed(() => {
    // register dependencies
    ko.ignoreDependencies(() => {
        // produce side-effects
    });
});

This is why I propose that computed is renamed to a longer (and scarier) impureComputed or autorun (like in mobx), possibly changing it's signature dividing "register dependencies" and "produce side-effects" parts. And pureComputed is renamed to computed to make it the go-to option for less experienced knockout.js developers. Of course this would break compatibility, so this is probably only feasible for the next major release.

If we could make documentation advise towards pureComputed and against computed when in doubt, that would be great.

If it were possible to ban any non-local mutation in pureComputed's read and write functions (except writing other observables in write), I'd also root for that.

agree!!


Search functionality in documentation

Documentation
Relevant Radix Component(s)

Examples from other doc sites

https://chakra-ui.com/

Also requested here with a recommendation for Algolia which looks super simple to integrate.


Reject SMASH URIs with paths

Issue Number
ADP-502
Overview

The idea was to use the servant types of SMASH, but that's pending due to https://github.com/input-output-hk/smash/issues/110

Comments
This was tested locally against testnet.
The sqlite serialisation is a little more permissive.

Looks right, although I believe is a breaking change with regard to the command-line arguments. cardano-launcher and the Daedalus config will need adjustments.

Yep

bors r+


Helm 3 beta3: go-client caching issue when installing chart resource which is based on a CRD

Output of helm version:
version.BuildInfo{Version:"v3.0.0-beta.3", GitCommit:"5cb923eecbe80d1ad76399aee234717c11931d9a", GitTreeState:"clean", GoVersion:"go1.12.9"}

Output of kubectl version:
Client Version: version.Info{Major:"1", Minor:"15", GitVersion:"v1.15.3", GitCommit:"2d3c76f9091b6bec110a5e63777c332469e0cba2", GitTreeState:"clean", BuildDate:"2019-08-19T12:36:28Z", GoVersion:"go1.12.9", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"15", GitVersion:"v1.15.2", GitCommit:"f6278300bebbb750328ac16ee6dd3aa7d3549568", GitTreeState:"clean", BuildDate:"2019-08-05T09:15:22Z", GoVersion:"go1.12.5", Compiler:"gc", Platform:"linux/amd64"}

Issue
When installing a Helm chart which includes a resource from a previously registered CRD (not included in helm chart), Helm throws an error like the following one.
Error: apiVersion "test.com/v1alpha1" in reproducer/templates/demo.yaml is not available

This problem was already handled in these issues & PR's:
https://github.com/helm/helm/issues/5654
https://github.com/helm/helm/pull/6049
The actual problem still exists. The reason is, that the client-go discovery cache doesn't gets invalidated before installing the chart.
Reproducer
Register a CRD out of the scope of Helm.
kubectl apply -f - << EOF
apiVersion: apiextensions.k8s.io/v1beta1
kind: CustomResourceDefinition
metadata:
  name: demos.test.com
spec:
  group: test.com
  names:
    kind: Demo
    listKind: DemoList
    plural: demos
    singular: demo
  scope: Namespaced
  subresources:
    status: {}
  version: v1alpha1
  versions:
  - name: v1alpha1
    served: true
    storage: true
EOF

Try to install or template (with --validate) a chart with the following resource.
apiVersion: test.com/v1alpha1
kind: Demo
metadata:
  name: default
spec: {}

This results in the error.
Error: apiVersion "test.com/v1alpha1" in reproducer/templates/demo.yaml is not available

After invalidating the client-go discovery cache it works as expected. As a workaround it's possible to invalidate the cache by executing kubectl api-versions, which internally invalidates the discovery cache (https://github.com/kubernetes/kubernetes/pull/48016/files), before installing the chart.
kubectl api-versions
...
helm template testchart --validate
---
# Source: reproducer/templates/demo.yaml
apiVersion: test.com/v1alpha1
kind: Demo
metadata:
  name: default
spec: {}

Possible fix
Currently Helm internally invalidates the discovery cache only if there are CRD's applied in the context of the Helm chart. (https://github.com/helm/helm/blob/v3.0.0-beta.3/pkg/action/install.go#L131)
A possible solution would be to always invalidate the discovery cache when installing a chart if the mode isn't clientOnly.
https://github.com/helm/helm/blob/v3.0.0-beta.3/pkg/action/install.go#L175
	if i.ClientOnly {
		// Add mock objects in here so it doesn't use Kube API server
		// NOTE(bacongobbler): used for `helm template`
		i.cfg.Capabilities = chartutil.DefaultCapabilities
		i.cfg.KubeClient = &kubefake.PrintingKubeClient{Out: ioutil.Discard}
		i.cfg.Releases = storage.Init(driver.NewMemory())
	} else {
		// Invalidate the discovery cache here
    }

Related issues and pull requests
https://github.com/helm/helm/issues/5654
https://github.com/helm/helm/pull/6049

thanks for identifying a potential fix! We'll see if we can address this issue in the next beta.

@mhofstetter Thanks for letting us know about this! So I did actually look at this option when I was messing around with this code last. My one concern is that invalidating the cache every single install (and possibly upgrade if we want to maintain consistency) is that the initial discovery cache fill takes multiple requests (according to comments in the code, possibly close to 100). This can add some delay and could add up for multiple chart installs in a CI/CD pipeline. We are definitely going to look at this, but we'll need to be careful so that every Helm command doesn't end up saturating the API server with requests

In Helm 2, how did Tiller fetch these capabilities? Was there no discovery cache used when dealing with service accounts?
I'm curious to see how kubectl approaches this problem. Do they invalidate the cache every time you attempt to apply a new resource into the cluster?

My lazy lookup skills seem to indicate that kubectl does indeed invalidate the discovery cache every time kubectl apply is called.
https://github.com/kubernetes/kubernetes/blob/5b496d2a25de5bd65512d8c8034f1cbc49e05b4d/staging/src/k8s.io/kubectl/pkg/cmd/apply/apply.go#L236

According to an older comment back when kubectl was a separate project, kubectl would check the cache first then invalidate and retry if a lookup failed. Here's the code that performed that lookup/cache invalidation: https://github.com/kubernetes/client-go/blob/668d7ca6dcbe8882483c3377d7e52f2d7dab18a3/discovery/restmapper.go#L197-L200

For context, @thomastaylor312's previous comment about the initial discovery cache filling taking ~50 requests to fill the cache seems in line with this comment in the cli-runtime package, which is what Helm uses to create the discovery client.
By default, the discovery cache is invalidated every 10 minutes, which is in line with my initial findings in #5654 where the cache would eventually resolve itself if you waited long enough. Trying to dig deeper on what's the recommended approach Helm should take here in the case where a CRD was installed out-of-band using kubectl create. Trying to look into kubectl apply's runtime logic because the following use case works without any issues:
kubectl apply -f - << EOF
apiVersion: apiextensions.k8s.io/v1beta1
kind: CustomResourceDefinition
metadata:
  name: demos.test.com
spec:
  group: test.com
  names:
    kind: Demo
    listKind: DemoList
    plural: demos
    singular: demo
  scope: Namespaced
  subresources:
    status: {}
  version: v1alpha1
  versions:
  - name: v1alpha1
    served: true
    storage: true
EOF

then
kubectl apply -f - << EOF
apiVersion: test.com/v1alpha1
kind: Demo
metadata:
  name: default
spec: {}
EOF

as seen in this example:
><> kubectl apply -f - << EOF
> ...
customresourcedefinition.apiextensions.k8s.io/demos.test.com created
><> kubectl apply -f - << EOF
> ...
demo.test.com/default created

@bacongobbler Thanks for digging deeper into the possible solution.
I don't see the invalidation of the cache in the code of kubectl. i think they are invalidating the cache only when the CRD isn't found in it. without having a closer look... (https://github.com/kubernetes/kubernetes/blob/5b496d2a25de5bd65512d8c8034f1cbc49e05b4d/staging/src/k8s.io/kubectl/pkg/cmd/apply/apply.go#L236 -> they are only getting the discoverycache)
But this would also match with the logs (loglevel 6) when trying to apply a resource first after registering its CRD.
applying the CRD
kubectl apply -f - << EOF
apiVersion: apiextensions.k8s.io/v1beta1
kind: CustomResourceDefinition
metadata:
  name: demos.test.com
spec:
  group: test.com
  names:
    kind: Demo
    listKind: DemoList
    plural: demos
    singular: demo
  scope: Namespaced
  subresources:
    status: {}
  version: v1alpha1
  versions:
  - name: v1alpha1
    served: true
    storage: true
EOF
customresourcedefinition.apiextensions.k8s.io/demos.test.com created

applying the resource first - the CRD isn't in the discovery cache - therefore the cache gets invalidated
kubectl apply -v 6 -f - << EOF
apiVersion: test.com/v1alpha1
kind: Demo
metadata:
  name: default
spec: {}
EOF
I0924 09:08:28.438139   16006 loader.go:375] Config loaded from file:  /Users/mhofstetter/.kube/config
I0924 09:08:28.576546   16006 round_trippers.go:443] GET https://<IP_ADDRESS>:8443/openapi/v2?timeout=32s 200 OK in 136 milliseconds
I0924 09:08:29.394087   16006 discovery.go:214] Invalidating discovery information
I0924 09:08:29.398295   16006 round_trippers.go:443] GET https://<IP_ADDRESS>:8443/api?timeout=32s 200 OK in 4 milliseconds
I0924 09:08:29.430778   16006 round_trippers.go:443] GET https://<IP_ADDRESS>:8443/apis?timeout=32s 200 OK in 14 milliseconds
I0924 09:08:29.472083   16006 round_trippers.go:443] GET https://<IP_ADDRESS>:8443/apis/autoscaling/v1?timeout=32s 200 OK in 23 milliseconds
I0924 09:08:29.474659   16006 round_trippers.go:443] GET https://<IP_ADDRESS>:8443/apis/authentication.k8s.io/v1beta1?timeout=32s 200 OK in 26 milliseconds
I0924 09:08:29.523478   16006 round_trippers.go:443] GET https://<IP_ADDRESS>:8443/apis/scheduling.k8s.io/v1?timeout=32s 200 OK in 75 milliseconds
I0924 09:08:29.528098   16006 round_trippers.go:443] GET https://<IP_ADDRESS>:8443/apis/apiextensions.k8s.io/v1beta1?timeout=32s 200 OK in 79 milliseconds
I0924 09:08:29.529543   16006 round_trippers.go:443] GET https://<IP_ADDRESS>:8443/apis/coordination.k8s.io/v1beta1?timeout=32s 200 OK in 80 milliseconds
I0924 09:08:29.540786   16006 round_trippers.go:443] GET https://<IP_ADDRESS>:8443/apis/cilium.io/v2?timeout=32s 200 OK in 92 milliseconds
I0924 09:08:29.548582   16006 round_trippers.go:443] GET https://<IP_ADDRESS>:8443/apis/storage.k8s.io/v1beta1?timeout=32s 200 OK in 100 milliseconds
I0924 09:08:29.548592   16006 round_trippers.go:443] GET https://<IP_ADDRESS>:8443/apis/node.k8s.io/v1beta1?timeout=32s 200 OK in 99 milliseconds
I0924 09:08:29.548649   16006 round_trippers.go:443] GET https://<IP_ADDRESS>:8443/apis/apiregistration.k8s.io/v1?timeout=32s 200 OK in 100 milliseconds
I0924 09:08:29.548626   16006 round_trippers.go:443] GET https://<IP_ADDRESS>:8443/apis/rbac.authorization.k8s.io/v1?timeout=32s 200 OK in 99 milliseconds
I0924 09:08:29.548650   16006 round_trippers.go:443] GET https://<IP_ADDRESS>:8443/apis/certificates.k8s.io/v1beta1?timeout=32s 200 OK in 100 milliseconds
I0924 09:08:29.548598   16006 round_trippers.go:443] GET https://<IP_ADDRESS>:8443/apis/rbac.authorization.k8s.io/v1beta1?timeout=32s 200 OK in 100 milliseconds
I0924 09:08:29.548607   16006 round_trippers.go:443] GET https://<IP_ADDRESS>:8443/apis/admissionregistration.k8s.io/v1beta1?timeout=32s 200 OK in 99 milliseconds
I0924 09:08:29.548669   16006 round_trippers.go:443] GET https://<IP_ADDRESS>:8443/apis/storage.k8s.io/v1?timeout=32s 200 OK in 100 milliseconds
I0924 09:08:29.548679   16006 round_trippers.go:443] GET https://<IP_ADDRESS>:8443/apis/apiregistration.k8s.io/v1beta1?timeout=32s 200 OK in 100 milliseconds
I0924 09:08:29.548724   16006 round_trippers.go:443] GET https://<IP_ADDRESS>:8443/apis/apiextensions.k8s.io/v1?timeout=32s 200 OK in 99 milliseconds
I0924 09:08:29.548736   16006 round_trippers.go:443] GET https://<IP_ADDRESS>:8443/apis/authorization.k8s.io/v1?timeout=32s 200 OK in 100 milliseconds
I0924 09:08:29.548749   16006 round_trippers.go:443] GET https://<IP_ADDRESS>:8443/apis/authorization.k8s.io/v1beta1?timeout=32s 200 OK in 100 milliseconds
I0924 09:08:29.548777   16006 round_trippers.go:443] GET https://<IP_ADDRESS>:8443/apis/scheduling.k8s.io/v1beta1?timeout=32s 200 OK in 100 milliseconds
I0924 09:08:29.548789   16006 round_trippers.go:443] GET https://<IP_ADDRESS>:8443/apis/networking.k8s.io/v1?timeout=32s 200 OK in 100 milliseconds
I0924 09:08:29.548803   16006 round_trippers.go:443] GET https://<IP_ADDRESS>:8443/apis/apps/v1?timeout=32s 200 OK in 99 milliseconds
I0924 09:08:29.548805   16006 round_trippers.go:443] GET https://<IP_ADDRESS>:8443/apis/networking.k8s.io/v1beta1?timeout=32s 200 OK in 100 milliseconds
I0924 09:08:29.548819   16006 round_trippers.go:443] GET https://<IP_ADDRESS>:8443/apis/autoscaling/v2beta2?timeout=32s 200 OK in 99 milliseconds
I0924 09:08:29.548770   16006 round_trippers.go:443] GET https://<IP_ADDRESS>:8443/apis/coordination.k8s.io/v1?timeout=32s 200 OK in 100 milliseconds
I0924 09:08:29.549755   16006 round_trippers.go:443] GET https://<IP_ADDRESS>:8443/apis/batch/v1?timeout=32s 200 OK in 100 milliseconds
I0924 09:08:29.549774   16006 round_trippers.go:443] GET https://<IP_ADDRESS>:8443/apis/batch/v1beta1?timeout=32s 200 OK in 100 milliseconds
I0924 09:08:29.549787   16006 round_trippers.go:443] GET https://<IP_ADDRESS>:8443/apis/policy/v1beta1?timeout=32s 200 OK in 101 milliseconds
I0924 09:08:29.550098   16006 round_trippers.go:443] GET https://<IP_ADDRESS>:8443/apis/rbac.istio.io/v1alpha1?timeout=32s 200 OK in 101 milliseconds
I0924 09:08:29.550221   16006 round_trippers.go:443] GET https://<IP_ADDRESS>:8443/apis/extensions/v1beta1?timeout=32s 200 OK in 101 milliseconds
I0924 09:08:29.550518   16006 round_trippers.go:443] GET https://<IP_ADDRESS>:8443/apis/autoscaling/v2beta1?timeout=32s 200 OK in 101 milliseconds
I0924 09:08:29.551168   16006 round_trippers.go:443] GET https://<IP_ADDRESS>:8443/api/v1?timeout=32s 200 OK in 102 milliseconds
I0924 09:08:29.551173   16006 round_trippers.go:443] GET https://<IP_ADDRESS>:8443/apis/admissionregistration.k8s.io/v1?timeout=32s 200 OK in 102 milliseconds
I0924 09:08:29.551488   16006 round_trippers.go:443] GET https://<IP_ADDRESS>:8443/apis/events.k8s.io/v1beta1?timeout=32s 200 OK in 102 milliseconds
I0924 09:08:29.551516   16006 round_trippers.go:443] GET https://<IP_ADDRESS>:8443/apis/authentication.istio.io/v1alpha1?timeout=32s 200 OK in 102 milliseconds
I0924 09:08:29.564650   16006 round_trippers.go:443] GET https://<IP_ADDRESS>:8443/apis/config.istio.io/v1alpha2?timeout=32s 200 OK in 115 milliseconds
I0924 09:08:29.564649   16006 round_trippers.go:443] GET https://<IP_ADDRESS>:8443/apis/networking.istio.io/v1alpha3?timeout=32s 200 OK in 115 milliseconds
I0924 09:08:29.564660   16006 round_trippers.go:443] GET https://<IP_ADDRESS>:8443/apis/test.com/v1alpha1?timeout=32s 200 OK in 115 milliseconds
I0924 09:08:29.564683   16006 round_trippers.go:443] GET https://<IP_ADDRESS>:8443/apis/authentication.k8s.io/v1?timeout=32s 200 OK in 115 milliseconds
I0924 09:08:30.316988   16006 round_trippers.go:443] GET https://<IP_ADDRESS>:8443/apis/test.com/v1alpha1/namespaces/default/demos/default 404 Not Found in 206 milliseconds
I0924 09:08:30.356083   16006 round_trippers.go:443] POST https://<IP_ADDRESS>:8443/apis/test.com/v1alpha1/namespaces/default/demos 201 Created in 38 milliseconds
demo.test.com/default created

deleting and reapplying the resource doesn't trigger an invalidation of the cache
kubectl delete demo default
demo.test.com "default" deleted

kubectl apply -v 6 -f - << EOF
apiVersion: test.com/v1alpha1
kind: Demo
metadata:
  name: default
spec: {}
EOF
I0924 09:13:08.033801   16449 loader.go:375] Config loaded from file:  /Users/mhofstetter/.kube/config
I0924 09:13:08.056170   16449 round_trippers.go:443] GET https://<IP_ADDRESS>:8443/openapi/v2?timeout=32s 200 OK in 21 milliseconds
I0924 09:13:08.136147   16449 round_trippers.go:443] GET https://<IP_ADDRESS>:8443/apis/test.com/v1alpha1/namespaces/default/demos/default 404 Not Found in 2 milliseconds
I0924 09:13:08.141915   16449 round_trippers.go:443] POST https://<IP_ADDRESS>:8443/apis/test.com/v1alpha1/namespaces/default/demos 201 Created in 5 milliseconds
demo.test.com/default created

as said with the newest version of kubectl
kubectl version
Client Version: version.Info{Major:"1", Minor:"16", GitVersion:"v1.16.0", GitCommit:"2bd9643cee5b3b3a5ecbd3af49d09018f0773c77", GitTreeState:"clean", BuildDate:"2019-09-19T13:57:45Z", GoVersion:"go1.12.9", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"16", GitVersion:"v1.16.0", GitCommit:"2bd9643cee5b3b3a5ecbd3af49d09018f0773c77", GitTreeState:"clean", BuildDate:"2019-09-18T14:27:17Z", GoVersion:"go1.12.9", Compiler:"gc", Platform:"linux/amd64"}

Nice find @mhofstetter! That particular log message points to this line in kubernetes/kubernetes:
https://github.com/kubernetes/kubernetes/blob/0541d0bb79537431421774465721f33fd3b053bc/staging/src/k8s.io/client-go/restmapper/discovery.go#L214
So now it's a matter of finding out where in pkg/kubectl it is calling .Reset() when the CRD is not in the discovery cache.

So after a long amount of time reviewing the code, it turns out that we want to force a cache invalidation anyways to ensure that the .Capabilities object always has the latest information from the server (Kubernetes server version, available API versions, etc). kubectl version forces a cache invalidation every time it's invoked so this seems like a safe change that is identical to kubectl's behaviour for fetching server information. PR incoming

Closing as #6486 is merged


Upgrade govuk_publishing_components and Plek to current versions.

Add the accessible-autocomplete component directly, since it was removed from govuk_publishing_components in version 18. This is the upgrade path recommended in the govuk_publishing_components changelog.
This unblocks upgrading from the now very outdated version 17 of govuk_publishing_components, which unblocks upgrading to the current version of Plek.
Removed the no-longer-necessary version constraints and ran bundle update to update to govuk_publishing_components 34.7.1 and Plek 5.0.0 (plus minor updates to some other gems).

@sengi I had not seen this PR until today but I think we did this work here
Can we close this one?

Yeah I never quite got around to getting this working in time unfortunately! Oh well :)


Added start page, added instructions on GitHub Pages

Great work, Natalia 👍
Hope you're doing well.
Ping me when you'll pull the Transifex trigger ;-)

Great work, Natalia 👍 Hope you're doing well. Ping me when you'll pull the Transifex trigger ;-)

Thanks, Jérémie! Yes, I remember )) I will.