Adding kernel code to the hash

Only the wrapper was used to evaluate the key for cache_manager, as a result, all kernels with same name and arguments did not recompile which caused a lot of simple tests to fail. For example, binary operations, swapping + for - inside the kernel resulted in the first compiled to be used.
With the change all binary tests are passing, before most of them failed because of improper caching.

@nhat-nguyen please take a look when you have a chance, thank you!

Just some thoughts on our testing strategy (we don't need to address it here). It would be great if we can somehow reuse the tests from the triton repository without having to duplicate them. Not a huge deal right now given we're only beginning to add the tests. But at one point it may become a bit hard to manage and sync with the upstream ones. Anyway, thank you again for this patch!

Just some thoughts on our testing strategy (we don't need to address it here). It would be great if we can somehow reuse the tests from the triton repository without having to duplicate them. Not a huge deal right now given we're only beginning to add the tests. But at one point it may become a bit hard to manage and sync with the upstream ones. Anyway, thank you again for this patch!

I agree, I was also thinking about that, I think I can write conftest.py for pytest in a way that we can reuse embed CPUBackend everywhere, the only thing is @pytest.mark.interpreter fixture, not sure yet if it would be possible to remove it. Anyway, if most of the core tests are passing now, I will look how to remove these copy-pasted files and use from triton.

I briefly checked, this decorator is relatively easy to neutralize, there are some other minor modifications in the code, but overall looks doable. In the worst case, I would suggest modifications in the triton repo to make these tests reusable. Anyway, will address that in subsequent PRs, thank you!

@nhat-nguyen since this PR wasn't merged yet, I decided to pile deduplication effort on top of it, let me know if I need to separate it. Here is the summary of the recent changes:

I put all CPUBackend custom logic into pytest configuration file, removed it from all the tests
Made previously copy-pasted files to be symlinks to triton repository
Added exclude list for coretests, it turned out that roughly half (by name) of them are still not passing, the plan is to expand the support and remove them from the list once the fixes are available.
Since device="cpu" is a fixture now, removed hardcoded value from the sources
Slightly refactored test sources since I touched them, removed debug prints

Current stats: 2774 passed, 9733 skipped. A lot of these skipped tests are variants.

Looks like these new tests exposed some missing symbols in the pipeline:
E   ImportError: /home/runner/.triton/cache/bd3cd9ef8032e186d41db6c8267a59d0/__triton_shared_ref_cpu_kernel_launcher.so: undefined symbol: __truncsfbf2

Looks like these new tests exposed some missing symbols in the pipeline:
E   ImportError: /home/runner/.triton/cache/bd3cd9ef8032e186d41db6c8267a59d0/__triton_shared_ref_cpu_kernel_launcher.so: undefined symbol: __truncsfbf2

I see, bfloat16 doesn't work for some reason, but it works for me, interesting. Let me see if I can mask these specific testcases that operate on bfloat16. Thank you!

I just pushed the fix, bfloat16 is now excluded from the test parameters, hopefully that would make test_core.py to pass. Thank you!

Failed twice in pre-commit checks, the reason looks unrelated to the changes, @nhat-nguyen could you please rerun the pipeline, I do not think I have permissions to do that, thank you!


0.8.0 fails to launch

Hi,
I was a few days late and pushed 0.7.0 into our repositories today and all was working fine.
Now, I've just built 0.8.0 but I'm getting
Error: No such file or directory (os error 2)
Exception: wthrr exited with 1

That's all.
Reverted to 0.7.0 and it's working. Any clues?
I'm currently building my whole system from source, no pre-compiled binaries and still don't have a web-browser. Besides, I'll be away from Thursday until next Tuesday.
Just an heads-up in case it takes sometime to reply :)

Hey @0323pin
It's good to get report on such errors. Since I'm limited resource wise it's not always possible for me to spot them. So thanks alot for your report, it really helps to improve the app!
Most probably I missed a clause when checking for the translations that can now be saved to a file.
When I have I free moment I'll investigate later this day else it'll be fixed tomorrow 👍

Cheers.
The error itself doesn't say much, hopefully it will be easy to spot. Thanks!

I can only reproduce this error if I delete the locales/ directory in the root of the repo. I should probably make sure in Cargo.toml that it is a dependency. I would like to keep it as a build file and save the users from having to fetch it or to have it stored on their machine post build. What is you thought on that?
And can you verify that building is possible when using the full repo?

@tobealive I see you have edited your original reply, it differs from the automatic e-mail github sends out.

And can you verify that building is possible when using the full repo?

We do fetch the full repo to build the package. But, then we/I do is,
${INSTALL_PROGRAM} ${WRKSRC}/target/release/wthrr \
		${DESTDIR}${PREFIX}/bin

You can find the full package Makefile here, rust dependencies are declared in a separate cargo-depends.mk file which, is called from the Makefile with .include "cargo-depends.mk"
Do you mean I should fetch and install locales/pure-rust-locales.txt somewhere in the root file system? In this case, where should it be located?

I definitely need to get the dependencies in Cargo.toml straight.

Let's try that, else it's possible to fetch it from the build directory and install it as a separate file. I usually do this with, e.g. .desktop files.

Yes, after realizing the silliness of this mistake, I changed the initial answer to reflect that this definitely needs to be fixed.

Do you mean I should fetch and install locales/pure-rust-locales.txt somewhere in the root file system? In this case, where should it be located?

Nope, that's not wanted.

I included it as a constant now which should make sure it's included in the build process. As far as I could check this did the trick.

@tobealive I've just built 0.8.2 locally and everything is working fine again, thanks!
Didn't have the time to merge the update yet. Need to get some sleep. I'll try to merge it in the morning, else Tuesday  late evening. Closing this now.

Done, https://mail-index.netbsd.org/pkgsrc-changes/2023/02/23/msg269887.html

Awesome :muscle: thank you 😊!

@ttytm Long time, no see. Sorry for posting on a closed thread but, I was just wondering if a new release is due anytime soon? 76 commits after latest! Any breaking stuff?
Thanks and regards.

Hey @0323pin, no worries, good to hear from you!
Yes it's planned. The wasn't happening much in the last time here.
The changes have been mostly small refactoring and dependency updates.
Next thing I'll work on is finishing the fix for #135 then a new version is ripe.

Nice, thanks!
I'll keep an eye on it. Hopefully, I'll remember to switch MASTER_SITES=	${MASTER_SITE_GITHUB:=tobealive/} to your new github repo :smile:

@ttytm @0323pin
Regarding the question of a new version being published, I created a poll (#248) on my idea to release at least a patch every month in order to benefit from the changes of the latest dependency updates.  Maybe we could continue the discussion of the next release's contents there, as well.


Active/Standby button doesn't work

Describe the bug
When attempting to trigger an active/standby action, the button in the UI does not work as previously.
To Reproduce
Steps to reproduce the behavior:

Open Chrome/Firefox
Go to an environment that is running Active/Standby
Click the button to trigger the action
Nothing happens

Expected behavior
The button should pop up a confirmation box asking the user to verify their action.

I did some quick digging, I think the following were reverted when problems were added
https://github.com/amazeeio/lagoon/blame/main/services/ui/src/components/ActiveStandbyConfirm/index.js#L6
This line should actually be uncommented
https://github.com/amazeeio/lagoon/blame/main/services/ui/src/components/ActiveStandbyConfirm/index.js#L69
And this line should be changed back to
export default withLogic(ActiveStandbyConfirm);


[Task]: Feature flagging research

Is there an existing issue for this?

[X] I have searched the existing issues

SubTasks
No response

Done.
POC here: https://theappsmith.slack.com/archives/C02JT9CSE6L/p1684760365838069


Sidecar Container  Image  Change

Resolves  Issue  #17
Sets the sidecar container images:

Driver registrar: v1.2.0
CSI Attacher: v1.2.1
CSI Provisioner: v1.5.0

I can't create a volume with any version of the containers in my environment:
  Warning  FailedAttachVolume  7s (x10 over 4m17s)  attachdetach-controller  AttachVolume.Attach failed for volume "pvc-e3594312-4395-457e-8365-5fbf2a581178" : rpc error: code = Internal desc = ControllerPublishVolume : SKIP_MOUNT_UNMOUNT == yes and either fs1 or fs1 in not mounted on node jdun-worker2.

I checked the troubleshoot and it looks like this is a node mapping  issue? But the node names are the same in kubectl and gpfs. Also all the have the filesystem mounted.
[root ~]# mmlsmount all -L
File system fs1 is mounted on 3 nodes:
  <IP_ADDRESS>   jdun-worker2
  <IP_ADDRESS>  jdun-worker1
  <IP_ADDRESS>   jdun-master
[root ~]# kubectl get nodes
NAME           STATUS   ROLES    AGE   VERSION
jdun-master    Ready    master   14d   v1.16.3
jdun-worker1   Ready    <none>   14d   v1.16.3
jdun-worker2   Ready    <none>   14d   v1.16.3

Outside of that everything else appears to be  operational and the pvc even gets created in the gpfs directory (this is with  the most  recent code level).
@smitaraut or @deeghuge  any thoughts?
If this works in your  environments please merge.

That was resolved with node mapping.

I'm still not able to deploy using the cr.

I think it's the csi-node-driver-registrar

I tried all of the images independently and  none  of them worked. I think the driver needs to be  updated to allow changes.

CSI Provisioner v1.0.0 -> v1.1.0 deprecated two command line options that we use (without bumping major versions...)
--connection-timeout
--provisioner

We'll have to change how the deployment is done by the operator.
Also, slightly related question (as provisioner name should match driver name now) - why is our drivername a command line variable?  Is there a good reason for this?

I have opened another PR #108 in 1.1.0 branch. Closing this one.


How does this compare to PLIER?

An important question to address is how this method differs from PLIER? Does it gives qualitatively and quantitatively similar results when used on gene data-sets? Is it faster? These are important questions to answer when arguing the utility of this tool.

[ ] Run PLIER w/same number of LVs as autoPLIER
[ ] Train logistic regression classifiers to predict cell type from PLIER embeddings and autoPLIER embeddings
[ ] How do the performances compare?

Also memory management too (does it blow up my server?)

Benchmark the reconstruction error as well

Transferred to https://github.com/Bishop-Laboratory/Cancer-Normal-Transformer-Analysis/issues/28


pythonPackages.alot: move to python-modules

Motivation for this change
To move pythonPackages.alot from python-packages.nix to python-modules.
#30929
Things done

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

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

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

@garbas @Profpatsch

I had started this here https://github.com/NixOS/nixpkgs/pull/30429/files . If you have nix+mac would be cool to test that one since it seems to be the blocking point.

Sorry, I don't have any mac.
Given that your PR updates the version and moves alot to pkgs, which seems to fit better, i will close this PR in favor of yours.


update answers for OOPS PR#1323

Description
update LETKF answers due to changes in the QC .
Dependencies

waiting on https://github.com/JCSDA-internal/oops/pull/1323

oops PR was merged; this can be merged now too.


Make it possible to run examples from anywhere in the source tree

Now you can call "cargo run --example " from any directory,
not only from the root "Cargo.toml" directory.

It might be a better idea to embed the shader code into the program instead using include_bytes! or otherwise.

Unless the intention is that the shaders are overridable?

@alteous we need flexible solution, to let users change their shaders easily. See #28

Thanks @nchashch !
We do need to change the way shaders are loaded - #28
This PR solves a part of the issue, but sacrificing the initialization ergonomics. If we don't merge it, and focus on the proper solution, I don't think this is going to block anyone from playing with thee-rs, right?

TL;DR: I think hardcoding shaders and keeping this format!(..., env!(...)) solution for assets would be ok.
Yes, this is a bit of a crutch. Note that apart from shaders '.obj' and '.gltf' assets in current examples have this "run from only root Cargo.toml directory" problem. It is a minor problem, so I don't think solving only this problem (without any other benefit to the user) will be worth any kind of significant engineering effort.
I still think that being able to run examples from anywhere in the source tree is important, because it will save frustration to people tinkering with them. This "unwrap error" because you are in a wrong directory can be quite confusing for a person new to Rust.
Are there any plans for asset management? Three-rs has ergonomics focus and is targeted at making simple things, so having brutalist bare bones asset management - loading files specified by hard coded filenames might make sense to keep the API simple.

@nchashch

I think hardcoding shaders and keeping this format!(..., env!(...)) solution for assets would be ok.

I don't think this is what we want to end up with, but I'm fine with it being a temporary change.

Are there any plans for asset management?

Not at the moment, but we are open to the idea.
bors r+


[VS Code] [Audio] Calling module not available. Cannot find module 'slimcore-1.7'

Error:
Calling module not available. Cannot find module 'slimcore-1.7'
Steps to Reproduce:

Version Data

extensionName
VSLS-Audio

extensionVersion
0.1.32

applicationName
VSCode

applicationVersion
1.22.2

platformName
MacOS

platformVersion
10.0.17134

@ShiroYahisa Hey! Could you try uninstalling the audio extension and reinstalling it? This issue may indicate that they install process failed for some reason.

does updating the application help?

it was resolved by re-installing vscode

This issue is has been closed due lack of any recent activity. We've made lots of improvements to Live Share since this issue. Please re-open the issue, if this issue persists.
🤖Live-Share-Clean-Up-Bot🤖


(refactor) Add workflows to pmtct summary in patient chart

Requirements

[ ] This PR has a title that briefly describes the work done including the ticket number. If there is a ticket, make sure your PR title includes the ticket number in the format OHRI-123 My PR title.
[ ] My work includes tests or is validated by existing tests.

Summary

-This pr refactors the code in the pmtct patient summary to use the new workflows approach
Screenshots

Related Issue

Other

Also I don't know if it is just on on my end but I see double navigations for pmtct and I can't open the summary

Also I don't know if it is just on on my end but I see double navigations for pmtct and I can't open the summary

Which hackend are you using?

Also I don't know if it is just on on my end but I see double navigations for pmtct and I can't open the summary

Which hackend are you using?

I just started the app so I think it was using the namibia backend.

Also I don't know if it is just on on my end but I see double navigations for pmtct and I can't open the summary

Which hackend are you using?

I just started the app so I think it was using the namibia backend.

use the openmrs-dev backend, namibia doesnt have the new app name, if you use it you will see both the old and new app

@CynthiaKamau sorry about the conflicts, I think they are from the Eslint rule PR that just got merged.


Use pre-release plugin to fix incorrect parameter info

Docs Build status updates of commit 3181a54:
:clock10: Full build: the average full build time is 28 min(s) 58 sec(s), this is based on the last 468 build(s) for this repository.

Docs Build status updates of commit 3181a54:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.publish.config.json
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


XY grid - discuss vw units instead of percentages for grid frame

I'd like to discuss an option to use vw units for grid when used within grid frame because of two reasons:

grid frame takes up 100% screen width in most cases (well, that's probably what it was meant for in a web app style interfaces),
when using vw units the specified column widths remain the same even when nesting grids, which in the case of grid frame happens a lot. When using percentages two columns that are placed side by side (but at different nesting levels) to have different widths. For instance, first one gets 20% of screen width, second one which we also set at 20% gets 20% of the nested grid's width, which results in narrower column. From developer's perspective this is probably not what he/she wanted when designing the layout (again, in general).

It would make sense to 1) switch to vw units when using .grid-frame class or 2) at least allow developer to turn on vw units via a special class.
What's Foundation's team take on this?

cc @kball @brettsmason

I guess this only makes sense as a new class to not break nested grids.


Wallaby cannot find a button

Hi there! First time using Wallaby on my first Phoenix app. I've written my first acceptance test but have run in to an issue I can't resolve on my own
It's very simple.. filling out a form to register a user.
The form
<%= form_for @changeset, organisation_path(@conn, :create), fn f -> %>
  <%= if @changeset.action do %>

Oh noes! Please check the errors below.

  <% end %>

  <%= inputs_for f, :users, fn u -> %>
    <%= error_tag u, :first_name %>
    <%= text_input u, :first_name, placeholder: "First name" %>

    <%= error_tag u, :first_name %>
    <%= text_input u, :last_name, placeholder: "Last name" %>

    <%= error_tag u, :email %>
    <%= text_input u, :email, placeholder: "Email" %>
  <% end %>

  <%= error_tag f, :name %>
  <%= text_input f, :name, placeholder: "Organisation name" %>

    <input type="submit" value="Submit" />
    Already signed up?

<% end %>

Acceptance test
defmodule Esteem.UserSignsUpTest do
  use Esteem.AcceptanceCase, async: true

  test "user signs up a new organisation", %{session: session} do
    welcome_message =
      session
      |> visit("/")
      |> find("form")
      |> fill_in("First name", with: "Luke")
      |> fill_in("Last name", with: "Rollans")
      |> fill_in("Email", with<EMAIL_ADDRESS>      |> fill_in("Organisation name", with: "Org name")
      |> click("Submit")
      |> find("p")
      |> text

    assert welcome_message =~ "Whelp"
  end
end

Error
  1) test user signs up a new organisation (Esteem.UserSignsUpTest)
     test/acceptance/user_signs_up_test.exs:4
     ** (Wallaby.ElementNotFound) Could not find element
     stacktrace:
       (wallaby) lib/wallaby/node.ex:342: Wallaby.Node.retry/2
       (wallaby) lib/wallaby/node.ex:192: Wallaby.Node.click/2
       test/acceptance/user_signs_up_test.exs:15

Seems that Wallaby cannot find the "Submit" button (line 15). I've tried using an ID, scoping a find to the actions wrapper, and other methods of detection to no vail.
Am I doing something glaringly wrong? I've read through the docs a few times and looked at test source code.. from what I can tell, it should work.

With the current version of the api you have to use the click_button helper. click is designed to work on Nodes directly. In the next release you actually won't be able to call click without the module name (Node.click) which should eliminate this confusion. Can you try again with the click_button helper?

@keathley when I try as you suggest, I'm getting undefined function click_button/2
Have I used it correctly?
defmodule Esteem.UsertSignsUpTest do
  use Esteem.AcceptanceCase, async: true

  test "user signs up", %{session: session} do
    session
    |> visit("/")
    |> fill_in("First name", with: "Luke")
    |> fill_in("Last name", with: "Rollans")
    |> fill_in("Email", with<EMAIL_ADDRESS>    |> fill_in("Password", with: "123456")
    |> fill_in("Organisation name", with: "Marvellous Mutants")
    |> click_button("Submit")

    notice =
      session
      |> find(".alert.info")
      |> text

    assert notice == "Signed up successfully"
  end
end

Ah, I was using Wallaby 0.5.0. click_button was introduced in 0.6.0

Glad you got it sorted. :+1:


Where is the Convolutional layer？

I saw that the same issues as me were raised, but I couldn't read the author's answer.

@alanlisten - TimeDistributed(Dense(hidden_dim_2, activation = "tanh") is the same thing as Conv1D(hidden_dim_2, kernel_size = 1, activation = "tanh"). I've updated the code to make it more obvious.


Fix ManagedCAObserver racing with CPO

Currently, the CPO races with the ManagedCAObserver in that it will
always remove the ca-checksum annotation on the openshift-apiserver
depoyment. Because the ManagedCAServer does not watch deployments, the
CPO always ends up "winning" the conflict.
This change:

Makes the ManagedCAObserver watch deployments in the control plane
namespace and enqueue its two configmaps if either of the
openshift-apiserver or openshift-controller-manager changes
Makes the CPO not clear other Annotations in the pod metadata of the
openshift-apiserver deployment

What this PR does / why we need it:
Which issue(s) this PR fixes (optional, use fixes #<issue_number>(, fixes #<issue_number>, ...) format, where issue_number might be a GitHub issue, or a Jira story:
Fixes #
Checklist

[ ] Subject and description added to both, commit and PR.
[ ] Relevant issues have been referenced.
[ ] This change includes docs.
[ ] This change includes unit tests.

/lgtm

/retest-required


Dynamic scan_interval

Is your feature request related to a problem? Please describe.
In the current setup, scan_interval can only be modified in xml. A restart is typically needed to apply the changes.
Describe the solution you'd like
It would be great if the scan_interval can be adjusted (get and set) using service calls.
This will make it easier to adhere to ethical and sustainable scraping practices.  Lower scan_intervals could be utilized for short periods as needed; higher scan_interval can be used at other times.
Describe alternatives you've considered
It can possibly be done by disabling the scan_interval (by setting to 0), and relying solely on service calls to refresh the scraped data. However, the proposed solution will make it easier and increase adoption.

The proposed solution will make the code more complex and harder to maintain with little advantage over the alternative you described :)
So closing this issue.


0.19.5 - ReactNativeBlobUtilRequest.mm:477:16: expected expression

Hi, after upgrading to 0.19.5 I'am not able to run my ios app from the command line.
I have this error.
▸ Compiling ReactNativeBlobUtilRequest.mm
❌  /Users/claudioz/Projects/myapp_rn0724/node_modules/react-native-blob-util/ios/ReactNativeBlobUtilRequest.mm:477:16: expected expression
           ]);

This is my current environment:
System:
OS: macOS 14.1.1
CPU: (12) arm64 Apple M2 Max
Memory: 12.25 GB / 64.00 GB
Shell:
version: "5.9"
path: /bin/zsh
Binaries:
Node:
version: 21.2.0
path: /var/folders/pv/51qh3b417f995x35c1dfpyd80000gn/T/yarn--1700178466961-0.7102813556842231/node
Yarn:
version: 1.22.21
path: /var/folders/pv/51qh3b417f995x35c1dfpyd80000gn/T/yarn--1700178466961-0.7102813556842231/yarn
npm:
version: 10.2.3
path: /opt/homebrew/bin/npm
Watchman: Not Found
Managers:
CocoaPods:
version: 1.13.0
path: /Users/xxxxxx/.rvm/rubies/ruby-3.1.4/bin/pod
SDKs:
iOS SDK:
Platforms:
- DriverKit 23.0
- iOS 17.0
- macOS 14.0
- tvOS 17.0
- watchOS 10.0
Android SDK: Not Found
IDEs:
Android Studio: 2022.3 AI-223.8836.35.2231.11005911
Xcode:
version: 15.0.1/15A507
path: /usr/bin/xcodebuild
Languages:
Java:
version: 17.0.9
path: /usr/bin/javac
Ruby:
version: 3.1.4
path: /Users/xxxxxxxxxxx/.rvm/rubies/ruby-3.1.4/bin/ruby
npmPackages:
"@react-native-community/cli": Not Found
react:
installed: 18.2.0
wanted: 18.2.0
react-native:
installed: 0.72.7
wanted: ^0.72.4
react-native-macos: Not Found
npmGlobalPackages:
"react-native": Not Found
Android:
hermesEnabled: true
newArchEnabled: false
iOS:
hermesEnabled: true
newArchEnabled: false
Thanks

I saw it sadly too late, thanks.
Will fix it later today


Resize thread pool and set TcpStream timeout

This fixes the trivial attack of slowloris'ing 10 threads and holding them open forever.

the thread count is dynamic (up to 400 threads in my example but that's not a hard limit and depends on use case; it also rescales back down based on demand)
the stream is killed after one second (also depends on use case)

Basically just proposing an idea that the thread pool be resized. :)

Awesome, thank you!

I had to revert this because I am getting random !! io:Error: Thread timeout (std::io::ErrorKind::WouldBlock) errors now when I run any of the examples or any Vial app. All I have to do is load a page and hit refresh a few times, and it will fail almost right away. Not sure what is happening. I bumped the timeout and removed it and still saw the same issue.


bounceInUp not working anymore - iPhone 6 Plus/iOS9

Just noticed looking at the my site today that bounceInUp is not working anymore on my iPhone 6 Plus. It was fine on my iOS8 but seem to have stopped working in iOS9. I tested this with the Github example page and it rendered the same result. Have not touched my code in any way in the last month.
This is just a heads up if you need to look into it, not sure what the fix is.

The same problem with Safari on iOS9.

I have added ' -webkit-transform-origin: 0 0;' to bounceInLeft:
0% {
opacity: 0;
-webkit-transform-origin: 0 0;
-webkit-transform: translate3d(-3000px, 0, 0);
transform: translate3d(-3000px, 0, 0);
}
and the animation worked.

See https://github.com/daneden/animate.css/pull/541


Some Operators are in incorrect location or namespace

We made a list of operators which are potentially in the wrong folder or namespace, check out
https://github.com/still-scene/t3/wiki/Operator-in-incorrect-location-or-namespace
@pixtur please correct and/or complete where the right location would be
I'm happy to do the cleanup and create a PR

@hollyhook I agree with all of you suggestions. Can you move them (either with the edit field in the parameter window or by dragging them with the symbol browser) to the correct locations and submit a pull request?

In some cases I don't know where to put the Operator.
@pixtur can you please look into the list and clarify the things marked with "?"

Ups. Just did so!

done


How to split a large request into smaller ones, then returning a response by merging smaller responses, In PipelineBehavior

Hi,
I have a request like this:
public class TimeSerriesQuery
{
    public DateTime From {get; set;}
    public DateTime To {get; set;}
}

and a response like this:
public class TimeSerries {
    public class DataPoint
    {
        public DateTime Time {get; set;}
        public double value {get; set;}
    }

    public DateTime LastTime {get; set;}
    public DataPoint[] DataPoints {get; set;}
}

I need to implement a IPipelineBehavior that split a TimeSerriesQuery with large time period into some queries with smaller time periods ,then send those requests to next handler in the pipeline, and then merge all small responses and return the final big response
I think the only possible way is to mutate the request to a smaller period and await on next, then mutate again and await again on next and do this until the whole period responses is ready, then merge them.
It seems it is not possible to call next multiple times concurrently with multiple split requests
How can I do that?

You'd need to design your own solution inside a single PipelineBehavior. Delegate to some other interfaces and do this yourself. There's no out-of-the-box solution here.
The request exception actions/handlers are in a similar boat, that's why there's a separate interface for them and a behavior that coordinates calling into those separate behaviors.

Jimmy,
After your comment on request exception actions/handlers, I checked the source of exception actions/handlers to see some sample code. I've found a mistake and requested pull #739
Thank you

Hi, to solve the problem its not easy for you to create a handler for your TimeSerriesQuery a handler that if the time periods is too large split the periods into smaller TimeSerriesQuery and then send it with
Task.WhenAll(_mediator.Send(subquery1), _mediator.Send(subquery2));?

Task.WhenAll(_mediator.Send(subquery1), _mediator.Send(subquery2));

yes, that makes sense. thank you 👍


Temperaments

ref #381, #382, #383, #384

Fix tempering examples.

Document changes in the commit message.

Test temperament equality and document it.


✨ Add token needed for checks in README

Add token needed for checks in README
No breaking changes
Add token needed for checks in README

friendly ping

friendly ping for reviews


Add common and monitoring labels

Tested on Gauss

did you tested update from the previous version as well?  playing with labels could result in errors with immutable fields

Does that not apply only if I change the selector?

Also, yes as I created a cluster first then I have overriden the app which "upgraded" it

Does that not apply only if I change the selector?

not sure that's why asked if the update was tested and there were no errors :)

Haha :D
It seems that it only applies to selectors yes https://kubernetes.io/docs/concepts/workloads/controllers/deployment/#label-selector-updates

and you do changes to the label selector as well :package:

I did not as I replaced app: {{ .Values.name }} with {{- define "labels.selector" -}} app: {{ .Values.name | quote }} {{- end -}}


Remove {{stringFormat}} helper

{{stringFormat}} helper uses the prinft-style variables (e.g. "My name is %s."). This contradicts with the variable style provided by the {{i18n}} helper (e.g. "My name is {0}." see issue #166). This contradiction confuses developers.

@this Please put the PR or commit reference when closing a issue.

@manuranga This issue is not closed :)

@vidurananayakkara Please attend to this issue.


Documentation for IAsync* Links are leading to 404 page

IAsyncActionWithProgress,
IAsyncOperation, and
IAsyncOperationWithProgress<TResult, TProgress>.
Respectively,
https://docs.microsoft.com/en-us/uwp/api/windows.foundation.iasyncactionwithprogress_tprogress_
https://docs.microsoft.com/en-us/uwp/api/windows.foundation.iasyncoperation_tresult_
https://docs.microsoft.com/en-us/uwp/api/windows.foundation.iasyncoperationwithprogress_tresult_tprogress_
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: db952f42-9d6e-d30b-0aed-e7de64a89987
Version Independent ID: bea24c9a-3e1e-405d-d7cc-5a080e62ece2
Content: Concurrency and asynchronous operations with C++/WinRT - UWP applications
Content Source: windows-apps-src/cpp-and-winrt-apis/concurrency.md
Product: uwp
Technology: platform
GitHub Login: @stevewhims
Microsoft Alias: stwhi

Thanks, @namar0x0309, the fix is now live. :)
-Steve


High CPU usage for certain pattern of HTTP requests

Description:
CPU usage increases and persist even for a small load of requests which has the following pattern.
DEBUG - wire HTTPS-Listener I/O dispatcher-6 >> "GET /services/Version HTTP/1.0[\r][\n]"
DEBUG - wire HTTPS-Listener I/O dispatcher-6 >> "[\r][\n]"
DEBUG - wire HTTPS-Listener I/O dispatcher-6 >> "[\r][\n]"
Steps to reproduce:

Design a request which has the above mentioned pattern (With extra set of [\r][\n]).
Send few requests while monitoring the CPU usage.

Affected Product Version:
APIM-4.0.0

Please verify whether the issue is fixed with the dependency update

The current http-core version is 4.4.16.wso2v1 and the issue is fixed.


Add tag flag to export message tag comments

Some golang packages use struct tag to store infomation. For example, using go-playground/validator, you can define a validate rule like this
type Test struct {
	Field `validate:"max=10,min=1"`
}

It will be great convenient if struct generated by protoc-gen-go according to proto has these tags.
This PR promotes a simple way to achieve this goal.
First, we introduce a so called struct tag comment like
message User {
    int32 uid = 1 // `validator:"gt=0"`
}

When we generate the *.pb.go, we enable the tag flag by --go_out=tag=true:path, wewill get
type User struct {
    Uid int32 `protobuf:"varint,1,opt,name=uid,proto3" json:"mid,omitempty validator:gt=0"
}

So other packages could read the right struct tag.

There are some other solution like gogo using the protobuf extension. But this PR is a more lightweight one.

Issue #52 discuss various solutions that are related to this. Personally, I’m not in favor of adding validation tags to message fields, for reasons explained in one of my comments on #52. Especially not as comments in the proto file. I’m not sure what is the status of @dsnet’s proposal for go_tags, but seems like it has been put on hold, while the protobuf team resolves other issues.

@meling Thank you  for reply. This PR is not about the validation tags but generic tags. If it was accepted, any user defined tags in trailing comment can be added to the message struct tags. And it is the user's code's business to use these tags. And these does not have any meaning to the protoc-gen-go. And they are just comments in proto, there is no work to do for any util about proto.

Hi, thanks for the PR, but we cannot accept this change. As @meling mentioned, the proposal to add this is #52. However, we are busy working on proto reflection and are not considering various generator extensions at this time.
If we add #52, it would have to be a proto option similar to what gogo/protobuf does. A magical comment that has special meaning in Go does not scale well with other languages and proto is intended to be a cross-language serialization technology that is mostly agnostic towards the target language.

@meling @dsnet

A magical comment that has special meaning in Go does not scale well with other languages

[golang/protobuf] is golang only. And the tag comment is golang only. And the tag comment is just comment, so other utils can not be confused.

A comment is intended for human consumption and humans should be free to edit them as they please without accidentally breaking semantics. Machine interpretation of comments is a definite no-go. Proto options were invented to avoid hackery around comments.

@dsnet thank you


Consider making jest_preprocess_cache hierarchical

All of the files in jest_preprocess_cache are stored flat in the directory.
Does it maybe make sense to break those into folders, maybe based on the first two characters of the hash, like git does? Not sure that the performance wins here would be.
But at the very least, Atom wouldn't crash when I accidentally fat finger the directory ;-)

Done in 0.6.0.


Use binascii hexlify/unhexlify in storage instead of encode/decode

This is already done in lbryum-refactor branch and it's not possible to hit this issue unless you run the new wallet in python 3, create some claims and then switch to the old wallet in python 2 and try to view those claims.
Upgrading from old wallet+py2 lbrynet to the new wallet+py3 lbrynet is not a reversible operation so we don't need to support new wallet stuff in the old wallet.


html5 seems to load in the background

I've set YTC to only use Flash and it worked fine for a while, but with the past couple of dev updates something strange happens. Whenever I load a video in my Watch Later playlist the video starts running in the background (most likely in the html5 player) and it starts in the flashplayer. I can pause the flash one but html5 will keep running. It's pretty annoying and I hope you can fix it soon. Let me know if you need anymore information.
Otherwise, keep up the good work.

I've noticed that videos load very slow now, even if my connection is downloading data at full capacity. My guess is that two versions of the same video are downloading at once (HTML5 and Flash). Maybe this is related to issue #1724?


Public aggregation access by workflow config

Closes #1213 - Add per workflow aggregation config object and open up the index route to allow access if the supplied workflow id is public.

reworked - controller is a bit heavier now to allow access to the public show route as well. Tried refactoring to a module but was really just hiding code in another file.

@camallen this good to go?

Yeah should be if you're happy with it.


v1alpha2 validation fix/update

What type of PR is this?

/kind bug
/kind cleanup
What this PR does / why we need it:
Fix/Update v1alpha2 validation modules
Which issue(s) this PR fixes:

Fixes #
PR https://github.com/kubernetes-sigs/gateway-api/pull/780 is super slow
Fixes #https://github.com/kubernetes-sigs/gateway-api/issues/826
Does this PR introduce a user-facing change?:

Looks like this one is pretty close @ccfishk, any chance you could finish it up?

Hi, @youngnick  @robscott, need migrate this PR to a new PR to finish this up due to account issue, is this OK ?


Add UUSD to Gnosis bridge's token list

At https://bridge.gnosischain.com UBQ is listed as a bridgeable token, we should make UUSD appear on that list as well.

Its unclear to me how to add there but UBQ has been around for four years, perhaps its listed somewhere that Gnosis uses.

Its unclear to me how to add there but UBQ has been around for four years, unlike UUSD. Perhaps UBQ listed somewhere that Gnosis uses.

We can reach out to their team to find that out. If we prove we are a real project they should add that manually. The same should eventually be done to add the token to Rabby, DefiLlama and other wallets.

I don't think this bridge is open-source to make a contribution and add the token to the metadata most likely they only have tokens they like to make it look like an "official bridge" without aggregating others ERC20

https://discord.com/invite/gnosis
I also just ran a wget -r to surf the source code right now.


Update TT-NN to 0.53.1-rc4

This PR updates TT-NN wheel to the latest pre-release version.

Looks like these two models failed with conv2d OOM
ERROR tests/models/segformer/test_segformer.py::test_segformer[train] - TypeError: SegFormer-train compiled failed to run.
ERROR tests/models/segformer/test_segformer.py::test_segformer[eval] - TypeError: SegFormer compiled failed to run.

I'll regenerate the guard functions for them (and other models)

I found a regression on the broadcasting elementwise op: https://github.com/tenstorrent/tt-metal/issues/15585

I found a regression on the broadcasting elementwise op: tenstorrent/tt-metal#15585

Add a fallback for this specific broadcasting case, try to merge again


Test failed for default test

Getting this when running the default test:
> xo && ava

  1 failed

  echo back the text
  /Users/tyrion/devel/kube-client-micro/test.js:22

   21:
   22:   t.is(res.body.text, 'Hello!');
   23: });

  Actual:

    undefined

  Expected:

    "Hello!"

npm ERR! Test failed.  See above for more details.

Not sure what you mean 🤔

when I ran npm test I had to fix a myriad of linting problems (thinking about PRing those), then when the test finally run (hello/:who), I got undefined instead of Hello!Am 18.04.2018 19:03 schrieb Tim Neutkens notifications@github.com:Not sure what you mean 🤔
—You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or mute the thread.

Note that this is the zeit/micro repository for the micro npm package. (Just making sure we're on the same page)
There are no linting errors on this repository and it has 100% test coverage. It also doesn't have a test ;ole t.is(res.body.text, 'Hello!');

I know this is closed already, but for the sake of an useful example, could you help me on changing the default example, now really this project's one, to test a real endpoint? I looked around the Web for any working examples, but with no success.
I want to test this endpoint:
const dostuff = async (req, res) => {
	const pods = await controller.dostuff.someMethod(req.params.myParam);
	send(res, 200, dostuff);
};

module.exports = router(
	post('/dostuff/:,myParam', dostuff),
);

const micro = require('micro')
const test = require('ava')
const listen = require('test-listen')
const request = require('request-promise')
test('my endpoint', async t => {
const service = micro(async (req, res) => {
micro.send(res, 200, {
test: 'woot'
})
})
const url = await listen(service)
const body = await request(url)
t.deepEqual(JSON.parse(body).test, 'woot')
service.close()
})

req.params and req.body are both express specific things. Also you're sending a function send(res, 200, dostuff); dostuff is a function, not an object/string etc.

Ok for the sake of this example take this endpoint:
const hello = rateLimit({window: 5000, limit: 2}, (req, res) => {
	send(res, 200, `Hello, ${req.params.who}`);
});

module.exports = router(
	post('/hello/:who', hello)
);

How would you test it?


doublerendererror

https://rollbar.com/carto/CartoDB/items/41423/?utm_campaign=new_item_message&utm_medium=slack&utm_source=rollbar-notification
cc @amiedes not to fix it, just to track it and keep an eye to it

Closing in favor of https://app.clubhouse.io/cartoteam/story/83510/doublerendererror


Swin Transformer on CIFAR

Could you please let me know the hyperparameters you used to train Swin Transformer on CIFAR100?

Base lr 5e-4 and scaled by total batch size / 512. Trained on 2 GPUs.
Batch size per device is  64 for swin-s 128 for swin-t, and  32 for swin-b.

Thanks


Apple rejects app

Hello Apple just rejected the app because I ask the user after login to enter date of birth and gender. I need these data in the very first step. Is there any way to pick gender and d.o.b. from apple login? the plugin doesn't seem to have thia capability. Thank you

Hello @xale76, there is no way to get gender and DOB from apple login eithe using native code or plugin. If you can ask user to enter DOB and gender on profile section to avoid Apple rejection but you need to explain Apple why you are taking these details, if there is no use of these details in app but you are asking user to enter then Apple can reject your app.


Fix bug in eb_enc_msb_un_pack2d_sse2_intrin

shift the data before pack.

          1 Error

:no_entry_sign:
Code style violations detected.

Code Style Check

Code style violations detected in the following files:

Source/Lib/Common/ASM_SSE2/EbPackUnPack_Intrinsic_SSE2.c

Execute one of the following actions and commit again:

Run clang-format on the offending files
Apply the suggested patches with git apply patch.

Source/Lib/Common/ASM_SSE2/EbPackUnPack_Intrinsic_SSE2.c
--- Source/Lib/Common/ASM_SSE2/EbPackUnPack_Intrinsic_SSE2.c
+++ Source/Lib/Common/ASM_SSE2/EbPackUnPack_Intrinsic_SSE2.c
@@ -134,7 +134,9 @@
             outn0_U8 = _mm_packus_epi16(_mm_slli_epi16(_mm_and_si128(inPixel0, xmm_3), 6), _mm_slli_epi16(_mm_and_si128(inPixel1, xmm_3), 6));
             outn1_U8 = _mm_packus_epi16(_mm_slli_epi16(_mm_and_si128(inPixel2, xmm_3), 6), _mm_slli_epi16(_mm_and_si128(inPixel3, xmm_3), 6));
             outn2_U8 = _mm_packus_epi16(_mm_slli_epi16(_mm_and_si128(inPixel4, xmm_3), 6), _mm_slli_epi16(_mm_and_si128(inPixel5, xmm_3), 6));
-            outn3_U8 = _mm_packus_epi16(_mm_slli_epi16(_mm_and_si128(inPixel6, xmm_3), 6), _mm_slli_epi16(_mm_and_si128(inPixel7, xmm_3), 6));
+            outn3_U8 = _mm_packus_epi16(
+                _mm_slli_epi16(_mm_and_si128(inPixel6, xmm_3), 6),
+                _mm_slli_epi16(_mm_and_si128(inPixel7, xmm_3), 6));

             out8_0_U8 = _mm_packus_epi16(_mm_and_si128(_mm_srli_epi16(inPixel0, 2), xmm_00FF), _mm_and_si128(_mm_srli_epi16(inPixel1, 2), xmm_00FF));
             out8_1_U8 = _mm_packus_epi16(_mm_and_si128(_mm_srli_epi16(inPixel2, 2), xmm_00FF), _mm_and_si128(_mm_srli_epi16(inPixel3, 2), xmm_00FF));
@@ -175,7 +177,9 @@
             outn0_U8 = _mm_packus_epi16(_mm_slli_epi16(_mm_and_si128(inPixel0, xmm_3), 6), _mm_slli_epi16(_mm_and_si128(inPixel1, xmm_3), 6));
             outn1_U8 = _mm_packus_epi16(_mm_slli_epi16(_mm_and_si128(inPixel2, xmm_3), 6), _mm_slli_epi16(_mm_and_si128(inPixel3, xmm_3), 6));
             outn2_U8 = _mm_packus_epi16(_mm_slli_epi16(_mm_and_si128(inPixel4, xmm_3), 6), _mm_slli_epi16(_mm_and_si128(inPixel5, xmm_3), 6));
-            outn3_U8 = _mm_packus_epi16(_mm_slli_epi16(_mm_and_si128(inPixel6, xmm_3), 6), _mm_slli_epi16(_mm_and_si128(inPixel7, xmm_3), 6));
+            outn3_U8 = _mm_packus_epi16(
+                _mm_slli_epi16(_mm_and_si128(inPixel6, xmm_3), 6),
+                _mm_slli_epi16(_mm_and_si128(inPixel7, xmm_3), 6));

             out8_0_U8 = _mm_packus_epi16(_mm_and_si128(_mm_srli_epi16(inPixel0, 2), xmm_00FF), _mm_and_si128(_mm_srli_epi16(inPixel1, 2), xmm_00FF));
             out8_1_U8 = _mm_packus_epi16(_mm_and_si128(_mm_srli_epi16(inPixel2, 2), xmm_00FF), _mm_and_si128(_mm_srli_epi16(inPixel3, 2), xmm_00FF));

  Generated by :no_entry_sign: Danger

          1 Message

:book:
[ 35%] Building CXX object test/CMakeFiles/SvtAv1UnitTests.dir/FwdTxfm2dAsmTest.cc.o
[ 35%] Building CXX object test/CMakeFiles/SvtAv1UnitTests.dir/FwdTxfm2dTest.cc.o
[ 41%] Building CXX object test/CMakeFiles/SvtAv1UnitTests.dir/IntraBcUtilTest.cc.o
[ 41%] Building CXX object test/CMakeFiles/SvtAv1UnitTests.dir/InvTxfm1dTest.cc.o
[ 41%] Building CXX object test/CMakeFiles/SvtAv1UnitTests.dir/InvTxfm2dAsmTest.cc.o
[ 47%] Building CXX object test/CMakeFiles/SvtAv1UnitTests.dir/InversetransformTests.cc.o
[ 47%] Building CXX object test/CMakeFiles/SvtAv1UnitTests.dir/MotionEstimationTest.cc.o
In file included from /home/jenkins/workspace/Open-SVTAV1-Linux-GCC-Build/test/MotionEstimationTest.cc:13:0:
/home/jenkins/workspace/Open-SVTAV1-Linux-GCC-Build/Source/Lib/Common/Codec/EbMeSadCalculation.h:143:35: warning: ‘initialize_buffer32bits_func_ptr_array’ defined but not used [-Wunused-variable]
     static EbInializeBuffer32Bits initialize_buffer32bits_func_ptr_array[ASM_TYPE_TOTAL] = {
                                   ^
[ 52%] Building CXX object test/CMakeFiles/SvtAv1UnitTests.dir/NoiseExtractTest.cc.o
[ 52%] Building CXX object test/CMakeFiles/SvtAv1UnitTests.dir/PackUnPackTest.cc.o
/home/jenkins/workspace/Open-SVTAV1-Linux-GCC-Build/test/PackUnPackTest.cc:281:10: warning: ‘{anonymous}::TEST_CRASH_SIZES’ defined but not used [-Wunused-variable]
 AreaSize TEST_CRASH_SIZES[] = {AreaSize(65, 64), AreaSize(5, 4)};
          ^
[ 52%] Building CXX object test/CMakeFiles/SvtAv1UnitTests.dir/PictureAdditionTest.cc.o
[ 58%] Building CXX object test/CMakeFiles/SvtAv1UnitTests.dir/QuantAsmTest.cc.o
[ 58%] Building CXX object test/CMakeFiles/SvtAv1UnitTests.dir/ResidualTest.cc.o
[ 58%] Building CXX object test/CMakeFiles/SvtAv1UnitTests.dir/RestorationPickTest.cc.o
In file included from /home/jenkins/workspace/Open-SVTAV1-Linux-GCC-Build/test/RestorationPickTest.cc:14:0:
/home/jenkins/workspace/Open-SVTAV1-Linux-GCC-Build/Source/Lib/Common/ASM_AVX2/synonyms_avx2.h: In function ‘__m256i yy_load_256(const void)’:
/home/jenkins/workspace/Open-SVTAV1-Linux-GCC-Build/Source/Lib/Common/ASM_AVX2/synonyms_avx2.h:26:48: warning: AVX vector return without AVX enabled changes the ABI [-Wpsabi]
 static INLINE __m256i yy_load_256(const void *a) {
                                                ^
[ 64%] Building CXX object test/CMakeFiles/SvtAv1UnitTests.dir/SadTest.cc.o
[ 64%] Building CXX object test/CMakeFiles/SvtAv1UnitTests.dir/SelfGuidedUtilTest.cc.o
[ 64%] Building CXX object test/CMakeFiles/SvtAv1UnitTests.dir/SpatialFullDistortionTest.cc.o
[ 70%] Building CXX object test/CMakeFiles/SvtAv1UnitTests.dir/VarianceTest.cc.o
[ 70%] Building CXX object test/CMakeFiles/SvtAv1UnitTests.dir/compute_mean_test.cc.o
[ 70%] Building CXX object test/CMakeFiles/SvtAv1UnitTests.dir/convolve_2d_test.cc.o
In file included from /home/jenkins/workspace/Open-SVTAV1-Linux-GCC-Build/Source/Lib/Common/ASM_AVX2/convolve_avx2.h:18:0,
                 from /home/jenkins/workspace/Open-SVTAV1-Linux-GCC-Build/test/convolve_2d_test.cc:39:
/home/jenkins/workspace/Open-SVTAV1-Linux-GCC-Build/Source/Lib/Common/ASM_AVX2/EbMemory_AVX2.h: In function ‘__m256i load_u8_4x4_avx2(const uint8_t, uint32_t)’:
/home/jenkins/workspace/Open-SVTAV1-Linux-GCC-Build/Source/Lib/Common/ASM_AVX2/EbMemory_AVX2.h:26:26: warning: AVX vector return without AVX enabled changes the ABI [-Wpsabi]
     const uint32_t stride)
                          ^
[ 76%] Building CXX object test/CMakeFiles/SvtAv1UnitTests.dir/frame_error_test.cc.o
[ 76%] Building CXX object test/CMakeFiles/SvtAv1UnitTests.dir/intrapred_cfl_test.cc.o
[ 76%] Building CXX object test/CMakeFiles/SvtAv1UnitTests.dir/intrapred_dr_test.cc.o
[ 82%] Building CXX object test/CMakeFiles/SvtAv1UnitTests.dir/intrapred_edge_filter_test.cc.o
[ 82%] Building CXX object test/CMakeFiles/SvtAv1UnitTests.dir/intrapred_test.cc.o
[ 88%] Building CXX object test/CMakeFiles/SvtAv1UnitTests.dir/quantize_func_test.cc.o

  Generated by :no_entry_sign: Danger

merged, close it.


multiview component

https://github.com/BabylonJS/Babylon.js/issues/6015

can not reply in the conversation for some reasons. Understood for the callbacks, do not bother then


Upgrade restlet version to 2.3.4

Upgrade the version number of restlet to 2.3.4 from 2.2.1. Since we
use Jetty with restlet and 2.2.1 depends on Jetty 8 (which has been
EOL'ed for two years), upgrade to a version which uses a non-EOL'ed
Jetty.

Not going to do this one after all.


Unexpected token operator '?' when using the legacy build

Attach (recommended) or Link to PDF file here: N/A
Configuration:

Web browser and its version: N/A
Operating system and its version: macOS Monterey v12.6 (M1)
PDF.js version: v3.2.146 (legacy)
Is a browser extension: No

Other (perhaps) relevant info:

Bundler: Parcel 1.12.5
TypeScript: 4.7.4

What is the expected behavior?:
The application should be built
What went wrong?
I am getting the following error when bundling with parcel in production mode:
/app/node_modules/pdfjs-dist/legacy/build/pdf.js: Unexpected token: operator (?)
    at Z.get (/app/node_modules/terser/dist/bundle.min.js:1:525)
    at Object.errorToJson (/app/node_modules/@parcel/utils/src/errorUtils.js:9:20)
    at Pipeline.process (/app/node_modules/parcel-bundler/src/Pipeline.js:29:26)
    at async Object.run (/app/node_modules/parcel-bundler/src/worker.js:15:12)
    at async Child.handleRequest (/app/node_modules/@parcel/workers/src/child.js:60:26)

The stack-trace above does not provide any more details than that. However, upon further investigation in node_modules/pdfjs-dist/legacy/build/pdf.js I noticed the use of more modern features, such as  the nullish coalescing operator (??) and the let keyword.
The README in the mozilla/pdfjs-dist repository states:

For usage with older browsers or environments, without support for modern features such as optional chaining, nullish coalescing, and private class fields/methods; please see the legacy/ folder.

Is this bug or is the README wrong? We are using the legacy build.

When the application is not bundled in production mode (no minification). Then it works as expected.
If relevant, in the application, PDF.js is imported like this:
import { getDocument } from "pdfjs-dist/legacy/build/pdf"

Link to a viewer (if hosted on a site other than mozilla.github.io/pdf.js or as Firefox/Chrome extension)

The currently supported browsers/environments can always be found in https://github.com/mozilla/pdf.js/wiki/Frequently-Asked-Questions#faq-support and according to https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Nullish_coalescing#browser_compatibility all of them have native support for the ?? operator, hence why that's no longer polyfilled in the legacy-build.

Other (perhaps) relevant info:
* Bundler: Parcel 1.12.5
* TypeScript: 4.7.4

Most likely those tools are too old to support the necessary features, so you probably want to upgrade them to the latest releases.

The currently supported browsers/environments can always be found in https://github.com/mozilla/pdf.js/wiki/Frequently-Asked-Questions#faq-support and according to https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Nullish_coalescing#browser_compatibility all of them have native support for the ?? operator, hence why that's no longer polyfilled in the legacy-build.

Thanks for the clarification, that sounds reasonable. But that means that the README is wrong, no? Let me know if you need a contribution to change that text.

Other (perhaps) relevant info:

Bundler: Parcel 1.12.5
TypeScript: 4.7.4

Most likely those tools are too old to support the necessary features, so you probably want to upgrade them to the latest releases.

Yes. Parcel is outdated and needs to be updated to v2. Not a simple task I am afraid.
Thanks for the quick reply!

I was able to make the latest pdfjs-dist/legacy compatible down to Safari 12.1 (iOS) and Chrome (Windows/Mac OS) v69.
In my case we are using NextJS, what we had to do was use next-transpile-module and add pdfjs-dist in our next.config.js.
Additionally added this to babel config:
{
  "presets": [
    "next/babel",
    [
      "@babel/preset-env",
      {
        "useBuiltIns": "usage",
        "corejs": { "version": 3, "proposals": true }
      }
    ]
  ]
}

There are still some minor errors being logged but the pdf renders correctly in the versions mentioned.
Hopefully this helps something 🙂


doc: update "enable-authentication-and-restriction.md" doc, and examples of jwt-auth and wolf-rbac.

Type of change:

[ ] Bugfix
[ ] New feature provided
[x] Improve performance
[ ] Backport patches

What this PR does / why we need it:

Pre-submission checklist:
The doc update contains:

The jwt-auth  config and example.
The wolf-rbac config.
Optimize content.

[ ] Did you explain what problem does this PR solve? Or what new features have been added?
[ ] Have you added corresponding test cases?
[ ] Have you modified the corresponding document?
[ ] Is this PR backward compatible? If it is not backward compatible, please discuss on the mailing list first

cc @navendu-pottekkat
Please help review it.

Hi @navendu-pottekkat, please have a review when you have time, thanks!

a kind reminder  @navendu-pottekkat @juzhiyuan @hf400159
please help with review in order to complete this PR


octohat as a service

*dun dun dun*

Some initial notes from brainstorms with @freakboy3742, and the voices in my head:
Octohat as a service will be interesting, because of the rate-limiting issue.
Per GitHub's rating limiting, you get 60 requests/hour unauthenticated, or 5000 requests/hour authenticated. Authentication requires an unscoped personal access token. Trying to circumvent the ratelimiting is bad.
I know I'm probably being slightly wasteful with the use of requests at the moment, and could cut back on duplicates/unrequired calls, but it would be interesting to see the requests required to get a total scope of a project. It'd be something like count(users) + (count(issues)) + overhead where overhead is fixed and the users depends on who's found in the issues.
Also, for sufficiently large repos, you can't get all the information in one pass. I've already implemented --limit to go check the last x number of issues, but ideally we'd want a full check of a project, and then update it at some regular interval.
I'd also like to be able to have nice things like octohat.com/user/repo endpoints, where you could trigger a build, and then come back later to see the data, and when it was last updated.
Now, this is assuming I stick with the API-drive version.
What I could do is use the GitHub archive. There are a few problems with this approach

the archive is good for getting changes in a day, but historical parsing will be harder. If I want to use just the GitHub archive, I'd have to parse all data ever collected. Plus, the data formats change over time,
the data is event driven, so ensuring that all the events types (CommitComment, IssueComment, etc) match up to what's expected will be difficult.

I could take a hybrid approach - collect all the information once from the API, then update at x frequency from the archives.

The hacktoberfest verify checker from @erikaheidi appears to do just want I want - a github groking as a service \o/
https://github.com/erikaheidi/hacktoberfest-verify
Gotta think about caping things for the webmodel, for usability and not-exploding-the-server-ness

To deal with rate limiting, could you just make the service's user plug in their own API token? This could be done pretty transparently by having them oauth login to github when they start using the service, a la https://nightli.es/

Oh yes of course! Setting up octohatrack as an application would solve authentication and limiting concerns from a centralisation standpoint!

Now the question is timelength of results.
I'm tempted to say something like "Only look at the last month, or 20 issues", then detail the exact commands to run to use the CLI to get the whole version. I'm very worried about a bounce rate when it takes ~minutes to go through big repos in entirety, not to mention the larger scale caching issue.

Could adding some degree of asynchronous-ity improve the speed(say through asyncio), and possibly the option of providing partial results as they become available. Because the major speed problem is loading the issues and all the comments associated with them.
We could also implement various caching policies to speed up re-requesting a repository:

Cache based on E-Tags or Last-Updated headers, which would prevent re-downloading chunks of data and save rate-limited requests.
By checking the 'updated_at' key(on an issue), we can further reduce the number of requests needed. If the updated_at is the same as our cached one, then we know that no new comments have been made so we don't even need to check them.

To speed up providing information about recent contributors we could sort the issues by 'updated' so we get the most recently updated ones first, prioritising loading those before the others.
We could also store information about each contributor's last contribution to provide a quick mechanism to only display recent contributors.
Initial requests for data(where we have nothing cached) could be handed off to a task runner like Celery, and respond indicating that the data is being fetched, poll-back later(or we could do some websocket magic, which would be cool and interesting but also hard).
If we wanted to get really efficient we could simply request the first page of the /contributor and /issues APIs:

If there are any changes in the /issues then start a task running to update.
If there are any changes in the /contributors then asses how many

more than a page, pass off a task
less than a page, just update the DB and respond.

Added context here (because I didn't update this issue fast enough):
Lee has been awesome and made a proof of concept at https://github.com/leesdolphin/js-hatrack
All I did was fork this repo, and create a gh-pages branch for github hosting. so it's completely usable here: glasnt.github.io/js-hatrack

@leesdolphin would you like me to make you an organisation contributor?
With that level of access, you can move your proof of concept into the labhr organisation, and we can consolidate our efforts on the 'as a service' model.
I want to mock up some UI that I've been mulling over. Also, I'd like to figure out how to make the oauth things mentioned by @EDunham work, because at the moment throwing raw api keys around is not best practice.

Yeah, I'd love to move js-labhr under LABHR. And I'd love to help with aaS model too.

You should now have enough rights to enact a transfer of the repo into the organisation. Let me know if you need a hand :)

We now have a hat rack as a service!


[Discussion] Request for Guidance on Stage Two: Converting LLaVA-V1.6 into 4-bit GGUF Format (PAPER)

Discussion
LLaVA-Med V1.6: Training a Large Language-and-Vision Assistant for Biomedicine in Two and Half Hours
Abstract
Large Language Models (LLMs) have revolutionized natural language processing, but biomedical applications necessitate comprehension of both textual and visual data. General-purpose vision-language models struggle with biomedical domain-specific knowledge. Our novel approach, LLaVA-Med V1.6, significantly outperforms previous models, including Microsoft's Med-LLaVA, in visual question answering accuracy and precision. Achieved through visual instruction tuning (VIT) applied to LLaVA V1.6 using a substantial portion of the PMC-VQA dataset, the fine-tuning process on a four-A6000 GPU setup takes only 2.5 hours. LLaVA-Med V1.6 also supports any-resolution images and exhibits enhanced visual reasoning and Optical Character Recognition (OCR) capabilities.
1. Introduction
The release of GPT-4 has spurred intensive research into multimodal language models (MLLMs). While these models showcase impressive capabilities in general contexts, their effectiveness in biomedical scenarios is limited. Existing models may falter in addressing biomedical inquiries, risking inaccurate responses. LLaVA-Med V1.6, built upon the LLaVA V1.6 architecture with Mistral as the base model, leverages GPT-4 to generate diverse biomedical multimodal instruction-following data by synthesizing image-text pairs from the PMC-15M dataset. Utilizing novel curriculum learning techniques, LLaVA-Med V1.6 achieves remarkable performance enhancements.
2. Model Architecture
LLaVA-Med V1.6 employs a minimalist architectural design, similar to prefix tuning of language models. A novel trainable module seamlessly integrates a static image encoder with a dynamic language model (LM). The model trains a straightforward fully-connected projection layer on a modest dataset comprising 14k image-text pairs. Leveraging GPT-4 to autonomously curate biomedical task instructions from PubMed Central's extensive data repository, LLaVA-Med V1.6 achieves performance parity with state-of-the-art prefix tuning LMs.
3. Training and Dataset
The training process involved visual instruction tuning (VIT) applied to the latest version of LLaVA (v1.6) using a substantial portion of the PMC-VQA dataset. This fine-tuning was implemented on a four-A6000 GPU setup and took only 2.5 hours. The model increases input image resolution to capture finer visual details critical in the medical domain, supporting any-resolution images, including resolutions up to 672x672, 336x1344, and 1344x336.
4. Model Quantization and Format Conversion
To optimize the model for efficient deployment and inference, we converted the original 32-bit model to FP16 (16-bit), reducing the model size to 14 GB. Further, we quantized the FP16 model to 4 bits using the Q_4_K_M method from llama.cpp, reducing the model size to 5 GB. This quantized model was then converted to GGUF and subsequently to the Ollama format, facilitating deployment across multiple devices.
Benefits of Quantization and Format Conversion:

Reduced Model Size: From 14 GB to 5 GB.
Faster Inference: Increased speed and reduced VRAM requirements.
Multi-Device Compatibility: GGUF and Ollama formats enable efficient deployment on diverse devices.
Energy Efficiency: Lower computational demands reduce energy consumption.

Experimental Results:

Model Size: Reduced from 14 GB to 5 GB.
Inference Speed: Improved with less VRAM usage.
Accuracy: Maintained within 1% of the original model's accuracy.

5. Evaluation
LLaVA-Med V1.6 was evaluated on three standard biomedical visual question answering datasets. The model demonstrated superior visual conversation capabilities and enhanced OCR and visual reasoning abilities. It outperformed previous state-of-the-art models on specific metrics across these datasets, including Microsoft's Med-LLaVA.
6. Conclusion
LLaVA-Med V1.6 represents a significant advancement in biomedical conversational AI, offering enhanced performance in visual question answering and improved deployment efficiency. The quantization and format conversion processes ensure that the model is both high-performing and versatile, suitable for a wide range of medical applications. Our contributions pave the way for more sophisticated biomedical AI applications, enabling more accurate and informative responses to biomedical inquiries.
Query for Guidance
I am currently writing a paper on LLaVA-Med V1.6, which we have fine-tuned on medical images. The paper's first stage, detailing the fine-tuning process, is complete. I am now focusing on stage two: converting our fine-tuned model into a 4-bit GGUF format.
Could you please advise on what key points to include in this section? Additionally, could you suggest any relevant references or previous papers that discuss similar quantization processes?
Thank you for your assistance.
Best regards,
Rohith

Hi Rohith, have you got any updates on converting the fine-tuned model into GGUF format? As there are two GGUF models needed for LLAVA to run in LLAMA.CPP. Could you please provide some resources or suggestions if you have any? Thank you very much.

@Wangmmstar
yes we will be having two gguf files . One main gguf and other mm_projector gguf
u can refer to this:
https://github.com/ggerganov/llama.cpp/tree/master/examples/llava


Accuracy

How close does it get to a actual location of phone?

How close does it get to a actual location of phone?

I'm learning myself I don't know if I'm doing this correctly


Require "temporal/version" so Temporal::VERSION can be referenced

I ran across this after pulling the latest SHA.  This fixes #237 for me when I use this branch.

This is similar to a PR I just created at https://github.com/coinbase/temporal-ruby/pull/241, but I think mine is more correct since it more tightly scopes the require to only where it's strictly needed. What do you think? Does my version also allow you to load?

I would also go with #241.

Closing this since it's been fixed with #241

Closed because it's been fixed with #241


Inline GCN assembly in OpenCL kernel ?

Is this possible on ROCm ? I would like to use the new cross-lane functionality.

Yes
Get Outlook for iOShttps://aka.ms/o0ukef

From: Aaron Boxer<EMAIL_ADDRESS>Sent: Thursday, September 7, 2017 6:40:23 PM
To: RadeonOpenCompute/ROCm
Cc: Subscribed
Subject: [RadeonOpenCompute/ROCm] Inline GCN assembly in OpenCL kernel ? (#201)
Is this possible on ROCm ? I would like to use the new cross-lane functionality.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/RadeonOpenCompute/ROCm/issues/201, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AD8DuWpDIJ_ve4ipAn8335NhLbQ0rRlFks5sgH7lgaJpZM4PQhYp.

Thanks. Is there any documentation on how to do this? I would like to write a custom inclusive scan
method using cross-lane commands - currently I do this with LDS, but registers would be better.

Instead of scan across entire work group (there is OpenCL 2.0 method for this) I would like to scan over each quarter wave.

Here you may find an example:
https://github.com/zawawawa/gatelessgate/blob/master/Core/binary-kernel/equihash.cl
(not tested though)

Thanks, Mihai. It would also be nice for AMD to provide some examples as well.


How about add CocoaPods's  support

⬆⬆⬆⬆⬆⬆⬆⬆⬆⬆⬆⬆⬆⬆⬆⬆⬆⬆⬆⬆⬆⬆⬆⬆
============
Update
Oh, forget this. It can not be add to CocoaPods...

Actually this is something I've wanted to do for a long time. Will work on it when time permits.

I forked this project, and got it to work with cocoapods.   Unfortunately. I had to create a new project due to many issues I had, so i can't submit a Pull Request...   My fork is here https://github.com/edwardvalentini/AsyncMessagesViewController
it fully works with cocoapods now.


Convert compatibility module to binary module, fix compatibility with Azure environments

PR Summary
Resolves https://github.com/PowerShell/PSScriptAnalyzer/issues/1149.
The original compatibility check module was hastily implemented and was quite slow. It also needed CIM/WMI to be available. This meant it didn't work nicely with things like Azure Functions.
I rewrote it as a binary to be faster and to have a simpler, more composable, more semantically definite .NET API.
 There are also huge breaking changes in the PSCompatibilityAnalyzer module (I got rid of most of the commands), but that has never been released and is still below version 1.0, so that seems like less of a concern.
Basically there are no changes that break the PowerShell API of PSScriptAnalyzer unless people have gone hunting for types that are loaded (but aren't used directly by the module).
Also renames the PSCompatibilityAnalyzer module to PSCompatibilityCollector since that's more accurate and less confusing.
List of changes

Renamed PSCompatibilityAnalyzer to PSCompatibilityCollector, since that better describes what the module does. The module is now version 0.2.0.
Got rid of almost all the psm1 module implementation in favour of a binary module. This gets rid of all the command originally in that module in favour of a minimal set of cmdlets with a common noun prefix.
Added explicit JSON configuration to the serialiser. Extra fields in JSON are now explicitly ignored (this is the default, so the behaviour has not changed), and default values are now explicitly omitted from JSON and restored in C# when absent (again, this should not change any behaviours)
Added a JSON schema version, with a default version of 1.0. The current generated schema version is 1.1 (since there are additions but not breaking changes, breaking changes should start at 2.0)
Flattened the Query and Data namespaces. The Query namespace was already mostly like this. It made sense to me to flatten it all from a complexity standpoint.
Change the ConstituentProfiles field to be a ReadOnlySet<string> instead of a HashSet<string>
Change type dictionaries to be case-sensitive for collection and overriding (like PowerShell) for the query API (this is already done in https://github.com/PowerShell/PSScriptAnalyzer/pull/1195, but I need it on my machine). When https://github.com/PowerShell/PSScriptAnalyzer/pull/1195 is merged, I'll rebase this on top.
Move things out of the Microsoft.PowerShell.CrossCompatibility.Utility namespace and into the base namespace, Collection or Retrieval depending on what the class does, since I think Utility should be reserved for internal helpers
Omit the pre-existing profiles from the output PSCompatibilityCollector module, since they aren't needed for collection
Add profiles for Azure Functions and Azure Automation

PR Checklist

[x] PR has a meaningful title

Use the present tense and imperative mood when describing your changes

[x] Summarized changes
[ ] Change is not breaking
[x] Make sure all .cs, .ps1 and .psm1 files have the correct copyright header
[x] Make sure you've added a new test if existing tests do not effectively test the code changed and/or updated documentation
[x] This PR is ready to merge and is not Work in Progress.

If the PR is work in progress, please add the prefix WIP: to the beginning of the title and remove the prefix when the PR is ready.

@rjmholt I'm overall OK with the changes as they are mainly just in your module. But I think @JamesWTruher would be the better person to review the logic, etc. as he has more experience/knowledge in this area.


Remove .ci/resources.yaml when concourse dev-builds are enabled

How to categorize this PR?

/area delivery
/kind cleanup
What this PR does / why we need it:
After we started building dev-images in concourse again (see here), we don't need to specify additional resources anymore.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
/cc @rfranzke
/hold wait until https://github.com/gardener/ci-infra/pull/981 was merged
Release note:

NONE

/lgtm
/approve

/hold cancel


Add Unisat to the Bitcoin frontend tutorial

The blocker right now is that a tx submitted with Unisat isn't being registered on ZetaChain:
https://blockstream.info/testnet/tx/f239d7590e4f43743467aea690c73d301c1e5cfb3751633dde3aa4d428f0bd26
Not clear why.


Proxy not working after 1h

Bug description
Running capsule-proxy on AKS 1.30.3 integrated with microsoft entra ID. The proxy works properly during one hour, after this time we start getting errors regarding authentication
error: You must be logged in to the server (Unauthorized)

Restarting the proxy pod solve the issue. After some investigation it seems that the capsule-proxy lost the connectivity to the api-server once the cluster renew the service account token.
Capsule-proxy continues accepting requests and logs show groups/tenants are being detected but seems like the proxy is not capable of comunicate with the api-server.
- name: kube-api-access-bl4vt
      projected:
        defaultMode: 420
        sources:
          - serviceAccountToken:
              expirationSeconds: 3607
              path: token
          - configMap:
              items:
                - key: ca.crt
                  path: ca.crt
              name: kube-root-ca.crt
          - downwardAPI:
              items:
                - fieldRef:
                    apiVersion: v1
                    fieldPath: metadata.namespace
                  path: namespace

Expected behavior
Capsule-proxy continues working after the token is refreshed.
Logs
There are no error logs within the proxy logs.
capsule-proxy-7598b484d5-n65xw capsule-proxy {"level":"Level(-4)","ts":"2024-11-06T15:42:08.248Z","logger":"proxy","msg":"impersonating for the current request","username":"d2xxxxx-9f06-4ec88f0143e4","groups":["ac753c56-xxxxxx-8779023a437e","91ed29b0-1xxxxxxxxxe-ffbc39d049f4","system:authenticated"],"uri":"/api"}
capsule-proxy-7598b484d5-n65xw capsule-proxy {"level":"Level(-5)","ts":"2024-11-06T15:42:08.248Z","logger":"proxy","msg":"debugging request","uri":"/api?timeout=32s","method":"GET"}

Additional context

Capsule-Proxy version: 0.7.2
Helm Chart version: 0.7.2
Kubernetes version: 1.30.3 (AKS)

looking at the code, i would say this issue is related to the new service account management introduced in kubernetes 1.30 where the service account get a bound token which expires in 3607s.
The controller load the inClusterConfig on start but never refresh it, so it stop working after 1h.

Fixed by #569


Easy performance improvements

While looking for a way to detect when two objects stop colliding (instead of just the initial first collision) In World.prototype.internalStep function I found some potential performance bottlenecks:
// Now we know that i and j are in contact. Set collision matrix state
this.collisionMatrix.set(bi, bj, true);

if (this.collisionMatrix.get(bi, bj) !== this.collisionMatrixPrevious.get(bi, bj)) { ...

We just set bi / bj to true - why call a matrix lookup, if we already know its value.
Then, in the // Invoke pre-step callbacks we loop over every body to invoke .preStep, and then loop over them again to apply velocity, and then loop over them again to invoke .postStep, and then loop over them again to call sleepTick. All these could be combined into a single loop.
With large numbers of bodies the performance penalty can be quite severe in this function.

Thanks for the heads-up!
The first one is an easy fix.
The body preStep and postStep callbacks should probably be removed - I don't see why they are needed when there's the same events in the World. (But if I were to keep them, I'd switch to event dispatching instead - makes the API more uniform).
Not sure if I'd put the sleepTick in the same bodies-loop as postStep though - what if the user fiddles with other body sleep states in a .postStep callback, or sets the velocity of a body in a body sleep event (that is dispatched by .sleepTick())? No, they have to be in separate loops to guarantee a predictable state inside the callbacks.


Fixed -If night-shift is enabled, checkbox has to be clicked three times

Fixed -If night-shift is enabled, checkbox has to be clicked three times to disable
Closes #9471

added check for undefined value
fixed the condition in feature.js _setAdminTheme

@kevinansfield @kirrg001 Kindly have a look and let me know if there is anything for me to do. Thank You.


Implement creation of feeds with epoch-based indexing on feedPostHandler

Summary
Currently only sequence indexing is supported, but this is not specified on documentation or API.
Creating this issue to monitor implementation progress.
Motivation
This is currently undocumented missing feature.

Also feedGetHandler only support sequence feeds.


feat: update keyloak new version

feat: update keyloak new version

Thanks! Will approve when https://github.com/nwcdlabs/container-mirror/pull/127 is merged.

copy @wchaws

Hi @guan840912
When version 0.2.3 is published, can you help deploy cdk-keycloak again in your environment and make sure the keycloak 12.0.4 is working?
Thanks.

deploy version 0.2.3 .

working !!!
thanks
cc @pahud


Fix NaN or Inf after initializing Vicuna models (due to lack of bias weights)

As I mentioned in https://github.com/johnsmith0031/alpaca_lora_4bit/issues/124 I used this library to load vicuna models and at some point I started getting Inf/NaN results during inferencing these 2 models:

https://huggingface.co/TheBloke/vicuna-7B-GPTQ-4bit-128g
https://huggingface.co/TheBloke/vicuna-13B-1.1-GPTQ-4bit-128g/tree/main

After diving into the issue I realized it has no bias weights, so default initializer (as you mentioned correctly @johnsmith0031 ) was not overriden by loading weights.
So I replaced default initializer to zeros.
(p.s. still remains mistery for me why so different behaviour on different platforms - it should initialize biases with some garbage from memory, and I expected this garbage to have similar chance to go inf after converting from float32 to float16, but screw it)

UPD. Wrong branch


First integration test + jupyter notebook integration

Added jupyter notebook, and integrated it in yaetos command line, (using $ yaetos launch_docker_jupyter)
Related:

Added 2 jupyter notebook to show how to run things from there.
Attached df and config to "job" instance so it can be used in notebook directly
new Runner() class to allow running without parsing commandline, similar to Commandliner()

Other

added loading excel files directly from jobs_metadata.yml in pandas mode + updated excel_utils.py to run in pandas mode
added yaetos run_dockerized and yaetos run modes to execute jobs directly from yaetos command line, like $ yaetos run some/job.py --some=arg
added first integration test for job, with loading from fs, transform, drop to fs, and run dependencies, with ex4_dependency4_job_test.py and  + moved sample files to be compatible with jobs_metadata.yml paths and make them usable in this test.
removed need for env variable client side + cleaned LOCAL_APP_FOLDER situation
fix to remove yaml warnings in log

Published

v0.9.16: to integrate jupyter notebook and new yaetos launch_docker_jupyter mode + fix to yaetos setup
v0.9.17: to integrate yaetos run_dockerized and yaetos run modes + removed need for env variable client side + excel support

Running job and inspecting data from jupyter:

Hola @annafonte ! Other update that could be useful to you: running and inspecting jobs from jupyter, see above

Hey @arthurprevot, this looks super good -can't wait to use it. Thanks for the update


Interest in collaboration

Hi everyone,
Please add a comment to this thread if you're interested in helping out with developing this pipeline.
I'll start off by listing a few:

QBiC Tübingen (contact: @apeltzer, @sven1103)
NGI Stockholm (contact: @ewels)
NGI Uppsala (contact: @jessieno)

Perhaps we can have a conference call / google hangout in January to discuss how to proceed.
Phil

Hi Phil,
thanks for the organization!
From the QBiC side I am also very interested:

QBiC Tübingen: @subwaystation

Hey Phil,
conference call in January sounds good, probably in the week of 8th to 12th of January, as some of us are on leave.
Sven

Thanks, Phil, I am in with all my hands!
Sanger Institute: @wikiselev

Brilliant stuff!
I had a few hours free this afternoon so I made a new mini project: https://github.com/SciLifeLab/NGI-NFcookiecutter
It's a templating system for creating new Nextflow pipelines. Could make things a little easier to get started with here.

wtf, it works perfectly, just created a test workflow with cookiecutter! Thanks Phil, we will use it for this repo.

Has anybody looked at SCANPY (https://genomebiology.biomedcentral.com/articles/10.1186/s13059-017-1382-0)?

yes, I've seen SCANPY, looks like another good candidate for a NF pipeline. But probably it's worth waiting a bit until it becomes more widely used.


WAU tries to update uninstalled apps

This problem first happened with Whatsapp, so I've blacklisted it. Today WAU tried to update Playnite. Neither of them are actually installed (although I had installed them in the past).
updates.log

https://github.com/microsoft/winget-pkgs/blob/master/manifests/p/Playnite/Playnite/10.7/Playnite.Playnite.installer.yaml
Scope: user
This is where winget checks if it's installed or not:
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Uninstall\Playnite_is1
You could check if that reg exists and if it does delete it.

You could check if that reg exists (then it's installed in user context) and if it does delete it (or uninstall from Control Panel).

"HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Uninstall\Playnite_is1" does not exist nor Playnite is in the Control Panel uninstall list

My best shot...

My best shot...

Would it be helpful or a complete waste of time if I installed an older version of Playnite on a VM with WAU and then uninstalled it before running WAU?

I installed Playnite older vesion, with WingetUI - it installed in user context - ran a WAU check and it upgraded in user context.
Uninstalled via winget-installed and it's gone,
WAU doesn't detect it.
In your logs WAU detects it installed in System context...

Have you checked under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall if Playnite exists there?

Have you checked under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall if Playnite exists there?

nope

If you start a cmd and runs winget upgrade --source winget, is Playnite in the list?
This is the command WAU uses to find upgrades needed.

If you start a cmd and run winget upgrade --source winget, is Playnite in the list? This is the command WAU uses to find upgrades needed.

nope, I also tried winget list --source winget with no success

Then there's a Ghost in your Machine...

...or Romanitho can find out (maybe in the comparison between System/User installs)?

Tbh I don't actually know what is System/User install, I just click next when installing manually or use default option with Winget/WingetUI... Thanks for trying to figure it out tho

An user install is  when you as a user can install it in your own context (without being admin), in winget .yaml.terms: Scope: user:
https://github.com/microsoft/winget-pkgs/blob/master/manifests/p/Playnite/Playnite/10.7/Playnite.Playnite.installer.yaml
A system install is when it installs to every user on the machine (requires admin rights).

I might have accidentally installed or uninstalled Playnite as admin

Can you in WingetUI find it under:

I've it "installed" with Scoop (although it's a portable version and doesn't show in ctrl panel), but the Winget package is also no longer shown there

Hmm, Scoop Portable in the play then.. ..no more idea from me 🤯

Last try:
C:\Users%USERNAME%\scoop\apps
Is Playnite there?

Last try: C:\Users\%USERNAME%\scoop\apps Is Playnite there?

Yes, but it is the portable version

I've tried everything from installing different Playnite versions via Winget/Scoop/Web (as admin and std. user), but I can't replicate the problem with WAU wanting to upgrade it when it's not installed.
Ghost in the Machine...
...but, you're satisfied with WAU otherwise, thanks to @Romanitho?

I've tried everything from installing different Playnite versions via Winget/Scoop/Web (as admin and std. user), but I can't replicate the problem with WAU wanting to upgrade it when it's not installed. Ghost in the Machine... ...but, you're satisfied with WAU otherwise, thanks to @Romanitho?

Yes, I am pretty satisfied with WAU otherwise. I've had this problem only 2 times (with Playnite and Whatsapp) and it's pretty easy to workaround it by blacklisting the affected packages

Hi :) Is scoop able to uninstall apps ? This only way to uninstall properly I guess, is to uninstall it in system context.

Yes, Scoop version is just a portable one (it's not intalled in the context menu). You can only uninstall it by deleting manually the "install" folder or using scoop uninstall. Maybe there are some leftover registry entries...  Anyway, I've decided to reinstall Windows since my install was kinda old (3 years) and was getting a little bit slow. Hopefully this problem will also be fixed

Ok, good idea ;)


Device quantity issue

Hi @thatmattlove , When the number of devices exceeds 5, the following error will be triggered, causing the build to fail:

I've confirmed this in my development environment. Will start working on a fix.

@KincaidYang this should be fixed in cea421c.


Carousel Scroll Interference with Layout Scroll on Android

I am experiencing an issue with the carousel scroll interfering with the layout scroll exclusively on Android devices. When attempting to scroll through the carousel, the transition is not smooth and often stops midway. In some cases, there is no transition at all.
Steps to Reproduce:
Run the application on an Android device.
Add a carousel component inside a scrollable layout.
Attempt to scroll through the carousel.
Expected Behavior:
The carousel should scroll smoothly without interfering with the layout scroll, and transitions should complete as expected.
Actual Behavior:
The carousel scroll interferes with the layout scroll.
Transitions are not smooth and often stop midway.
Sometimes, no transition occurs.
Environment:
React Native version: 0.74.1
react-native-reanimated-carousel: 3.5.1
Additional Information:
This issue does not occur on iOS devices. I have tested with multiple Android devices and the problem persists. Any guidance or fixes would be greatly appreciated.
Videos:
https://github.com/dohooo/react-native-reanimated-carousel/assets/53793722/70888d4e-e343-4a35-9c37-2c22fd0ff6aa

It seems to be a nested ScrollView problem, I'm facing the same issue, and I'll be fixing it and committing a change soon.

@oliverloops any update on this? Facing the same problem.

 panGestureHandlerProps={{
        activeOffsetX: [-100, 100],
        activeOffsetY: [-100, 100],
      }}

did the trick for me

@oliverloops any updates? I checked and it's really a problem with ScrollView. If you scroll exactly in a horizontal line, the carousel works perfectly.


RFC: Functional API?

Would you accept a patch to convert the API to return immutable objects instead of mutating the base value?
Should make things like...

caching by sentence, so unchanged-sentences aren't re-parsed on keystroke

...easier to implement.
Would also obviate this:

some kind of thorough memory-leak test

Would be interested in helping to implement this if accepted.

hey guys, I like this idea too. It's a pretty big one. Join the conversation in #89 ? I think it's up your alley.
Right now the methods are sometimes mutable, sometimes not, which is brutal. it would definitely make sense to go one way or the other. Would love some help with this. I'm nearly-instantly confused by it.


reset unsaved warning after getSampleData() receives data

Simple fix to prevent the annoying bug where the unsaved warning erroneously appears whenever a sample or cell page is loaded a second time without a refresh.
closes #601

@ml-evs , can you deploy this to dev when you get a chance? Would like to test it on a real server with latency, etc.

@ml-evs , can you deploy this to dev when you get a chance? Would like to test it on a real server with latency, etc.

Deployed on dev


Clojure classpath problem

I am trying to access a clojure lein project in beaker.  I can do this in a simple form by including the uberjar (in beakertest/target/beakertest-0.1.0-SNAPSHOT-standalone.jar), but when I want to use an external jar, it seems to have issue and can't find the external jar.
[qtp1131040331-20] ERROR com.twosigma.beaker.clojure.util.ClojureEvaluator - java.lang.ClassNotFoundException: org.joda.time.ReadableDateTime, compiling:(clj_time/core.clj:1:1)
Wondering what I am missing.  org.joda.time.ReadableDateTime is in the jar file, but seems to not be in the classpath as per (println (seq (.getURLs (java.lang.ClassLoader/getSystemClassLoader))))
I have created a simple project by way of example:
https://github.com/dcmcshan/beakertest
Thanks for your help!  Really liking Beaker!

After some futher investigation, adding ALL the classes manually...
I get to this error:
ERROR com.twosigma.beaker.clojure.util.ClojureEvaluator - java.lang.Exception: namespace 'clj-time.format' not found, compiling:(clj_time/coerce.clj:1:1)
This might be a bit of clojure weirdness - the class name is "cli-time" but the file name is "cli_time".  Perhaps this is confusing your loader?
Thanks!

I have sorted that out, only to be confronted with
[qtp1131040331-17] ERROR com.twosigma.beaker.clojure.util.ClojureEvaluator - java.lang.IllegalAccessError: from-date does not exist, compiling:(beakertest/core.clj:1:1)
core.clj compiles normally in emacs/lein

I can now report that fully qualifying the references does "solve" the problem.  Still, this seems like something that should be fixed.
clj-time.coerce/from-long

thank you for the report and follow-up explanation.
sorry i don't have the bandwidth to handle this right now.
will look at it later.


println order in build.rs bug

Problem
in build.rs, it workds:
fn main() {
    println!("cargo:include=abc/src");
    println!("cargo:rustc-link-search=native=abc");
    println!("cargo:rustc-link-lib=static=abc");
    println!("cargo:rustc-link-lib=dylib=stdc++");
}

but it not works in:
fn main() {
    println!("cargo:rustc-link-lib=dylib=stdc++");
    println!("cargo:include=abc/src");
    println!("cargo:rustc-link-search=native=abc");
    println!("cargo:rustc-link-lib=static=abc");
}

the build can pass, but when run test, it will error:
error: linking with `cc` failed: exit status: 1
= note: /usr/bin/ld: abc/libabc.a(AbcGlucose.o): in function `glucose_solver_start()':
          /root/abc-glucose/abc/src/sat/glucose/AbcGlucose.cpp:63: undefined reference to `operator new(unsigned long)'
          /usr/bin/ld: /root/abc-glucose/abc/src/sat/glucose/AbcGlucose.cpp:63: undefined reference to `operator delete(void*, unsigned long)'
          /usr/bin/ld: abc/libabc.a(AbcGlucose.o): in function `Gluco::vec<Gluco::Lit>::capacity(int)':
          /root/abc-glucose/abc/./src/sat/glucose/Vec.h:103: undefined reference to `__cxa_allocate_exception'
          /usr/bin/ld: /root/abc-glucose/abc/./src/sat/glucose/Vec.h:103: undefined reference to `__cxa_throw'
          /usr/bin/ld: abc/libabc.a(AbcGlucose.o): in function `Gluco::vec<int>::capacity(int)':
          /root/abc-glucose/abc/./src/sat/glucose/Vec.h:103: undefined reference to `__cxa_allocate_exception'
          /usr/bin/ld: /root/abc-glucose/abc/./src/sat/glucose/Vec.h:103: undefined reference to `__cxa_throw'
  = note: some `extern` functions couldn't be found; some native libraries may need to be installed or have their path specified
  = note: use the `-l` flag to specify native libraries to link
  = note: use the `cargo:rustc-link-lib` directive to specify the native libraries to link with Cargo (see https://doc.rust-lang.org/cargo/reference/build-scripts.html#cargorustc-link-libkindname)

Steps
No response
Possible Solution(s)
No response
Notes
No response
Version
No response

The order that libraries are passed to the linker is significant (particularly when mixing dylib and static libs). Some resources on the web may help explain the details if you are interested, such as: https://eli.thegreenplace.net/2013/07/09/library-order-in-static-linking or https://stackoverflow.com/questions/45135/why-does-the-order-in-which-libraries-are-linked-sometimes-cause-errors-in-gcc.

The order that libraries are passed to the linker is significant (particularly when mixing dylib and static libs). Some resources on the web may help explain the details if you are interested, such as: https://eli.thegreenplace.net/2013/07/09/library-order-in-static-linking or https://stackoverflow.com/questions/45135/why-does-the-order-in-which-libraries-are-linked-sometimes-cause-errors-in-gcc.

I see, Thanks.

Closing as it is not a bug. Thanks for everyone's participation.


Update cards to use Card component

As part of form layout updates, common markup for cards was broken into a component. This issue is to ensure the component (src/components/Card.js) is used everywhere applicable.

If card is different from what the Card component defines, skip and document here.

combine card + secondary card, update places that don't use card


Regarding aggregation in openfl

Hi,
If we want to use privacy preserving technologies such as differential privacy in securing aggregation in openfl, are there any tutorials or class interfaces which we can override to include the added security?
Are there any tutorials or class interfaces in openfl in which custom aggregation algorithms can be included other than federated averaging? Edit: I just realize there is new documentation added to custom averaging at https://openfl.readthedocs.io/en/latest/overriding_agg_fn.html
Thanks.

@chanfm81 hi! Thanks for your interest in OpenFL.
Regarding first question - currently, there is no interface for differential privacy, DP features are in plans. If you can come up with a proposal how to integrate it to OpenFL - it would be great initial point to kick off DP discussion.
Regarding second point - you are absolutely right - you can check out the example here :)

@chanfm81 since I believe the question is answered I would close the issue.


Added issue, feature, and documentation templates

Explanation: I have created and added three new templates to the repository, aiming to improve the GitHub issue creation process, feature requests, and documentation contributions. These templates introduce a standardized format for creating issues, requesting features, and documenting project details. By implementing these templates, contributors and maintainers will be able to collaborate more effectively.
here is demo of templates. :

@tusharzalte  Please add the Gssoc23 label and level 2 label for this Contribution otherwise its not visible to the Gssoc leaderboard


[BugFix] Fix union query rewrite not work when use ttl mv for external table

What type of PR is this：

[x] BugFix
[ ] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Which issues of this PR fixes ：

Fixes #
Problem Summary(Required) ：

When create mv with ttl, it will remove outdated partition and related meta info for olap table, it should also remove mv related meta info for external table
Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr will affect users' behaviors
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[x] I have checked the version labels which the pr will be auto backported to target branch

[x] 3.0
[x] 2.5
[ ] 2.4
[ ] 2.3

@Mergifyio backport branch-2.5


Add hook for storage event

Would it be possible to add a way to hook into the HTML5 storage event with this library?
Demo of the functionality I'm looking for (but doesn't use store.js, obviously).
I'm thinking something like:
// All Windows / Tabs:
store.on('keyName', function(s){
    console.log(s.newValue);
});

// Window / Tab 1:
store.set('keyName', 'testValue');

// All other Windows / Tabs:
// 'testValue' is logged.

I'm implementing my own solution for this with the following code:
// All Windows / Tabs:
// Hook into the storage event
$(window).on('storage', function(e){
    // Keys we actually care about.
    var keys = ['timeStamp', 'key', 'oldValue', 'newValue', 'url'], newEvent = {};
    e = e.originalEvent; // jQuery puts the original event here
    for (var i in keys) {
        i = keys[i];
        if (i.substr(3) === 'Value') {
            // Get the value back just like we put it into store.set()
            newEvent[i] = store.deserialize(e[i]);
        } else {
            newEvent[i] = e[i];
        }
    }

    // Send the event to global listeners that want to know about all storage changes.
    newEvent.type = 'localStorage';
    $(document).trigger(newEvent);
    // Send the event to listeners for this key only.
    newEvent.type = newEvent.key + '.localStorage';
    $(document).trigger(newEvent);
});

$(document).on('keyName.localStorage', function(e){console.log(e.newValue);});

// Window / Tab 1:
store.set('keyName', 'testValue');

// All other Windows / Tabs:
// 'testValue' is logged.

This seems like the perfect addition to this library. It would make cross-window/tab communication with store.js dead-simple. Want all of your web app tabs to know you just got a new message in the current tab? Just call store.set('newMessage', 'hey!');.
Of course, it would only work when localStorage is supported, but it would be easy enough to indicate in the .on() function's return value whether or not listening is enabled.
I can submit a pull request if you're interested.

Store.js v2.0 has been released with support for storage events and storage value observations: https://github.com/marcuswestin/store.js#user-content-list-of-all-plugins
If you update  you will get this functionality plus a bunch more :)