[Proposal] Add functions to use onQueue() delay() in Event Listeners

Laravel makes it really easy to push an event listener/handler onto a queue, but it is missing an easy way within that listener to specify what queue it should be pushed onto.
<?php

namespace App\Listeners;

use App\Events\PodcastWasPurchased;
use Illuminate\Queue\InteractsWithQueue;
use Illuminate\Contracts\Queue\ShouldQueue;

class EmailPurchaseConfirmation implements ShouldQueue
{
    // add methods to set onQueue and delay()
}

You don't push listeners to the queue, you push the event itself.
Can't you use classes for events and just implement Illuminate\Bus\Queueable ?

I'm firing off an event, but then I have several listeners responding to the same event. Some of those listeners are done right away, and others are queued using the auto-queue method above. But I don't want each listener to go on the same queue.
Using the DB driver there is a queue column which has the value of default, but I want those separate listeners to have different values for that column so I can process them differently. I don't know of an easy way of doing it yet .
Maybe I'm doing it wrong, but I'm desiring ShouldBroadcast's ease of use. :)

I don't think this needs changing.

I've been googling for a while to figure out how to do this.  At least now I know it's not supported.  @BrandonSurowiec the approach I'm now taking is to have an event listener that isn't queued which triggers a job on the queue that I specify.  It's an extra step, but it will provide the required functionality.

@glockops Thanks so much for the tip! Care to share some sample code?

I found an elegant solution that worked for my listener.
// 5.1
use Illuminate\Contracts\Queue\ShouldQueue

class MyExampleListener implements ShouldQueue {

    /**
     * Push a new job onto the queue.
     *
     * @param  string  $queue
     * @param  string  $job
     * @param  mixed   $data
     * @return mixed
     */
    public function queue($queue, $command, $data)
    {
    	dd($data);

        $queue->pushOn('facebook.agent', $command, $data);
        return $queue->pushOn('facebook.company', $command, $data);
    }
}

Just to confirm? I think you have a queued job that runs when the delay of the original job should happen then you just pushOn at that point in time when that delay should be effective?
I bump the fact that Queue::later should have the option to specify the tube

@BrandonSurowiec  Cool, still working perfectly on L5.7
My events, even though with redis on a dedicated i9, were slow by a one second delay, now they are so fast


MINOR: Update to Scala 2.11.12 (part 2)

Missed a few places in the previous commit.

SUCCESS
8059 tests run, 5 skipped, 0 failed.
--none--

SUCCESS
8059 tests run, 5 skipped, 0 failed.
--none--

Merged to trunk and 1.0 branches.

FAILURE
7951 tests run, 5 skipped, 1 failed.
--none--


Remote Start on home network only

Hi,
This is a great little tool, thank you for writing it. I am trying to get the remote start to work when I am off of my home network. I have port forwarded 5050 on my router and have also assigned a static IP address (on both the Xbox and Router). I have bridged my modem with the router so I am not going to be doubled NAT'd. It doesn't work for some reason. I have also placed the Xbox in the DMZ and still it does not work. I am using a Linksys router, not sure where to go to from here?
Thx

Sorry, can't help you with this.


shim: set ttrpcService and ttrpcServerOptioner to exported interfaces

Set shim.ttrpcService and shim.ttrpcServerOptioner to exported interfaces so that implementers can use them to check.
for https://github.com/containerd/containerd/pull/8746#discussion_r1243436939

/retest


Log softmax vs softmax

https://github.com/collabora/WhisperSpeech/blob/80b268b74900b2f7ca7a36a3c789607a3f4cd912/whisperspeech/vq_stoks.py#L344
Why use log softmax on the model logits, but softmax on the teacher logits?

You can configure the PyTorch loss function to take log of targets or just targets. By default the targets are not in log-space and so this is what I used. There may be numerical stability benefits but honestly I don’t remember if there was some rationale behind this.
There are examples of both in the docs: https://pytorch.org/docs/stable/generated/torch.nn.KLDivLoss.html


GetRoles function does not call with old session Cookie and new service

Describe the bug

When using the GetRoles function, the service doesn't call it when the user has the session cookie, but new deployment pushed.
Causing the user to lose all his roles until signs in again.
To Reproduce
Steps to reproduce the behavior:

Sign in with a user that has a custom role with GetRoles function.
Confirm that the user is authorized with the custom role.
Deploy a new version of the Azure Static Web App.
Navigate to the app.
The user is authenticated but the custom role has been removed. (issue)
Sign out and sign in again - the user got his roles again.

Expected behavior
The roles will remain, maybe by calling GetRoles again.
Screenshots
Device info (if applicable):

OS: Windows 11
Browser Edge
Version 99

Additional context

This should not be happening. I assume that by deploying a new version you mean updating some content?
Before and after updating the app can you verify the roles via /.auth/me https://docs.microsoft.com/en-us/azure/static-web-apps/user-information?tabs=javascript#direct-access-endpoint
If the roles change we can take a deeper look but this is unexpected.

This should not be happening. I assume that by deploying a new version you mean updating some content?

True

Before and after updating the app can you verify the roles via /.auth/me https://docs.microsoft.com/en-us/azure/static-web-apps/user-information?tabs=javascript#direct-access-endpoint

Yes, I tested that. Before I had userRoles: ["anonymous", "authenticated", "admin"], but after I deploy new deployment (new content) in the same website, the user is still logged on, but get userRoles: ["anonymous", "authenticated"].
Only after signing out and signing in the user get the admin role again...

So I tried reproing this, but wasn't able to. My roles persisted after content and function updates without the need to logout and log back in. Would you be able to share a .har file with us that shows your repro of this? If you don't feel comfortable posting this here, feel free to file a support ticket with Azure and we can help you there.

Will do in Azure support


RFE: Support more Host objects/parameters like psk related objects

@lebe-dev
I am hoping to create the host with PSK enabled on zabbix server side.

Existing host objects doesn't support PSK related objects.

  pub host: String,
    pub groups: Vec<ZabbixHostGroup, Global>,
    pub interfaces: Vec<ZabbixHostInterface, Global>,
    pub tags: Vec<ZabbixHostTag, Global>,
    pub templates: Vec<ZabbixTemplate, Global>,
    pub macros: Vec<ZabbixHostMacro, Global>,
    pub inventory_mode: u8,
    pub inventory: HashMap<String, String, RandomState>,

psk related objcts

Answered in another issue.
Details here: https://github.com/lebe-dev/zabbix-api-rs/issues/11#issuecomment-1919453804


Vivek! Does not work!

Hello, my android app shows me, the browser shows me, but the data is not exchanged. It is not working, spent all day, but it does not work. What is the problem?

Hello!
I have probably same issue talking of Step 3.
Signalling server is working and web part seems fine as I can see proper log output when open index.html in browser.
But the Android part had never establish a communication to signalling server.
logcat:
xyz.vivekc.webrtccodelab D/SignallingClient: init() called
xyz.vivekc.webrtccodelab D/SignallingClient: emitInitStatement() called with: event = [create or join], message = [vivek17]

and that's all. There is nothing in signalling server logs.

Did you change the ICE Servers configuration? The code was written for an older version of WebRTC and an older version of Node server. So it might not work as expected.


refactor: use Helm library instead of CLI

This refactor focuses on using the Helm library instead of Pods for installing/uninstalling the releases. Also, a small refactor to the listing of k8s resources that affects the Credential reconciliation loop.

We're dropping the provisioning / deprovisioning pods (at least for now), then?

Correct. Since the Credential logic required writing the Helm client, why not use it for everything? The pod strategy is more complex with more objects created and deleted.


Add examples using pkg and help mode respectively

It seems we should fix so that exit() (in the end of instructions) runs in julian mode.


docs: Fixup cargo docs

Codecov Report

Merging #4 (0b00182) into main (78ad397) will increase coverage by 0.20%.
The diff coverage is 80.00%.

:exclamation: Current head 0b00182 differs from pull request most recent head 7b8be5c. Consider uploading reports for the commit 7b8be5c to get more accurate results

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@            Coverage Diff             @@
##             main       #4      +/-   ##
==========================================
+ Coverage   76.91%   77.11%   +0.20%
==========================================
  Files          11       11
  Lines         589      590       +1
==========================================
+ Hits          453      455       +2
+ Misses        136      135       -1

Impacted Files
Coverage Δ

src/config.rs
54.83% <ø> (ø)

src/node/atoms.rs
80.00% <ø> (ø)

src/node/attribute.rs
72.09% <ø> (ø)

src/node/mod.rs
68.29% <ø> (+2.43%)
:arrow_up:

src/node/node_name.rs
72.58% <ø> (ø)

src/node/raw_text.rs
95.74% <ø> (ø)

src/lib.rs
27.27% <33.33%> (-39.40%)
:arrow_down:

src/parser/recoverable.rs
52.17% <77.77%> (+9.74%)
:arrow_up:

src/node/parse.rs
87.93% <100.00%> (ø)

src/parser/mod.rs
86.20% <100.00%> (-0.89%)
:arrow_down:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Fix/ignore matplotlibrc

Overwrite the matplotlibrc setting image.origin : lower for RasterPlot and its children
Remove orphaned ImagePlot

Thanks! Also good catch on the orphaned plot, must have been orphaned for a while.


Enable custom include directories for plugins

:notebook_with_decorative_cover: Description

Add an INCLUDE_DIRECTORIES argument that takes multiple relative paths to include directories to the VASTRegisterPlugin CMake function.
Safeguard against absolute CMAKE_INSTALL_*DIR variables, and annotate the cmake_parse_arguments call for easier understanding.
Change the VAST_REGISTER_PLUGIN macro to take between one and five arguments, making passing of the version optional. If just the plugin is passed to the macro, the VAST version is used as the plugin version. If at least the major version is specified, zeroes are used for the unspecified parts of the version.

:memo: Checklist

[x] All user-facing changes have changelog entries.
[x] The changes are reflected on docs.tenzir.com/vast, if necessary.
[x] The PR description contains instructions for the reviewer, if necessary.

:dart: Review Instructions
Commit-by-commit.

I rebased this to resolve the merge conflict.


server not starting properly

after installing and starting my server I get
[20:44:24] [ServerMain/INFO]: Environment: Environment[accountsHost=https://api.mojang.com, sessionHost=https://sessionserver.mojang.com, servicesHost=https://api.minecraftservices.com, name=PROD]
[20:44:34] [ServerMain/INFO]: Loaded 7 recipes
[20:44:35] [Server thread/INFO]: Starting minecraft server version 1.20.2
[20:44:35] [Server thread/INFO]: Loading properties
[20:44:36] [Server thread/INFO]: This server is running Paper version git-Paper-298 (MC: 1.20.2) (Implementing API version 1.20.2-R0.1-SNAPSHOT) (Git: e1cd9e5)
[20:44:38] [Server thread/INFO]: Server Ping Player Sample Count: 12
[20:44:38] [Server thread/INFO]: Using 4 threads for Netty based IO
[20:44:39] [Server thread/WARN]: [!] The timings profiler has been enabled but has been scheduled for removal from Paper in the future.
We recommend installing the spark profiler as a replacement: https://spark.lucko.me/
For more information please visit: https://github.com/PaperMC/Paper/issues/8948
[20:44:39] [Server thread/INFO]: [ChunkTaskScheduler] Chunk system is using 1 I/O threads, 1 worker threads, and gen parallelism of 1 threads
[20:44:40] [Server thread/INFO]: Default game type: SURVIVAL
[20:44:40] [Server thread/INFO]: Generating keypair
[20:44:41] [Server thread/INFO]: Starting Minecraft server on *:25565
[20:44:41] [Server thread/INFO]: Using epoll channel type
[20:44:41] [Server thread/INFO]: Paper: Using libdeflate (Linux aarch64) compression from Velocity.
[20:44:41] [Server thread/INFO]: Paper: Using OpenSSL 1.1.x (Linux aarch64) cipher from Velocity.
[20:44:41] [Server thread/INFO]: Server permissions file permissions.yml is empty, ignoring it
[20:44:41] [Server thread/INFO]: Preparing level "world"
[20:44:43] [Server thread/INFO]: Preparing start region for dimension minecraft:overworld
[20:44:44] [Server thread/INFO]: Time elapsed: 1031 ms
[20:44:44] [Server thread/INFO]: Preparing start region for dimension minecraft:the_nether
[20:44:45] [Server thread/INFO]: Time elapsed: 322 ms
[20:44:45] [Server thread/INFO]: Preparing start region for dimension minecraft:the_end
[20:44:45] [Server thread/INFO]: Time elapsed: 212 ms
[20:44:45] [Server thread/INFO]: Running delayed init tasks
[20:44:45] [Server thread/INFO]: Done (9.789s)! For help, type "help"
[20:44:45] [Server thread/INFO]: Timings Reset
and when I try to join the server it doesn't work

The server starts successfully according to the logs, so it doesn't seem to be a problem with the scripts.


Update README.md

Update UV Volume and L2G-NeRF

thanks:) congrats on your two papers accepted to CVPR 23!

Thank you!


Update to JupyterLab 3.0

Fixes #935
Opening early to start using JupyterLab 3.0 by default and leverage the new extension distribution system for faster builds.
TODO

[x] Update to JupyterLab 3.0 and ipywidgets 7.6 (which includes support for Jupyter Widgets in JupyterLab by default)
[x] Switch from nbresuse to jupyter-resource-usage
[ ] Update all the frozen environments with pip freeze.py
[ ] Update to jupyter-offlinenotebook==0.2.0
[ ] Package jupyter-offlinenotebook for conda forge? https://github.com/manics/jupyter-offlinenotebook/issues/154

I've opened https://github.com/jupyterhub/repo2docker/pull/997 to update the extension in this repo to 0.2.0
Based on the discussion in https://github.com/jupyterhub/zero-to-jupyterhub-k8s/issues/776#issuecomment-703903620 this PR probably won't be merged straight away, so updating just the extension now will make it easier for anyone who choose to upgrade to JupyterLab 3.
The conda-forge PR is in progress https://github.com/conda-forge/jupyter-offlinenotebook-feedstock/pull/2

I've opened https://github.com/jupyterhub/repo2docker/pull/997 to update the extension in this repo to 0.2.0
Based on the discussion in https://github.com/jupyterhub/zero-to-jupyterhub-k8s/issues/776#issuecomment-703903620 this PR probably won't be merged straight away, so updating just the extension now will make it easier for anyone who choose to upgrade to JupyterLab 3.
The conda-forge PR is in progress https://github.com/conda-forge/jupyter-offlinenotebook-feedstock/pull/2

FYI the failing Figshare tCI est is not due to this PR https://github.com/jupyterhub/repo2docker/issues/999

FYI the failing Figshare tCI est is not due to this PR https://github.com/jupyterhub/repo2docker/issues/999

Thanks @manics!
Yes it makes sense to first update jupyter-offlinenotebook so it's compatible with 3.0.

Thanks @manics!
Yes it makes sense to first update jupyter-offlinenotebook so it's compatible with 3.0.

Do you think we should add all language packs too? I presume there'll be no significant impact on image size or build time. Is there a way to add all languages in one go?

Do you think we should add all language packs too? I presume there'll be no significant impact on image size or build time. Is there a way to add all languages in one go?

Not sure the language packs have been published to PyPI yet, so maybe they could be added later if needed?
Or document how users could add the language packs of their choice just like other dependencies since they should be pip installable.

Not sure the language packs have been published to PyPI yet, so maybe they could be added later if needed?
Or document how users could add the language packs of their choice just like other dependencies since they should be pip installable.

Thanks for starting this PR only hours after the release :D
As I understand it lab extensions that work with lab v2 won't work with v3 unless they are upgraded. Is that correct?
Does someone know if all the extensions repo2docker uses (in particular nbresuse) are already compatible with lab v3?
A big task we need to tackle is how to transition repositories that rely on repo2docker using lab v2. In particular there are repos which install lab extensions but don't specify the version of lab that they want (or specify it not well enough). This is partly our fault because we recommend to people not to include things like lab in their environment.yml :-/
The ideal case would be that they "just keep working". I'm not sure we can achieve that, even if we reach to the very back of our bag of magic tricks.
Maybe some compromise we can actually implement is to detect that the repo isn't compatible, stop running and exit with a clear error message that links to documentation that explains how to get the repo working again.
Something I think is not acceptable is that these repos break with some random (long) error message. This is because repo2docker "sells" itself as a tool for making your work reproducible.
Maybe there are other options that we can think of that make this change as frictionless as possible for users.

Thanks for starting this PR only hours after the release :D
As I understand it lab extensions that work with lab v2 won't work with v3 unless they are upgraded. Is that correct?
Does someone know if all the extensions repo2docker uses (in particular nbresuse) are already compatible with lab v3?
A big task we need to tackle is how to transition repositories that rely on repo2docker using lab v2. In particular there are repos which install lab extensions but don't specify the version of lab that they want (or specify it not well enough). This is partly our fault because we recommend to people not to include things like lab in their environment.yml :-/
The ideal case would be that they "just keep working". I'm not sure we can achieve that, even if we reach to the very back of our bag of magic tricks.
Maybe some compromise we can actually implement is to detect that the repo isn't compatible, stop running and exit with a clear error message that links to documentation that explains how to get the repo working again.
Something I think is not acceptable is that these repos break with some random (long) error message. This is because repo2docker "sells" itself as a tool for making your work reproducible.
Maybe there are other options that we can think of that make this change as frictionless as possible for users.

As I understand it lab extensions that work with lab v2 won't work with v3 unless they are upgraded. Is that correct?

Right, although most extensions could start with the compatibility range update and publish a new release: https://jupyterlab.readthedocs.io/en/stable/extension/extension_migration.html#upgrading-library-versions-manually
Before switching to the new distribution system with pip and conda. This means the existing jupyter labextension install commands usually placed in the postBuild should still work.

A big task we need to tackle is how to transition repositories that rely on repo2docker using lab v2. In particular there are repos which install lab extensions but don't specify the version of lab that they want (or specify it not well enough). This is partly our fault because we recommend to people not to include things like lab in their environment.yml :-/

Fortunately, lab checks whether the extension is compatible before installing it. So if there is an extension that has been published to work with 2 and 3, lab will pick the correct one.

Maybe some compromise we can actually implement is to detect that the repo isn't compatible, stop running and exit with a clear error message that links to documentation that explains how to get the repo working again.

I think this should already happen if the postBuild is set to stop and exit on error. If repo2docker updates to JupyterLab 3 and the repo still uses jupyter labextension install commands in the postBuild to install extensions, then lab will do the compatibility check and output an error if it can't find a suitable version, that looks like the following:
Conflicting Dependencies:
JupyterLab              Extension        Package
>=3.0.0 <3.1.0          >=2.0.0 <3.0.0   @jupyterlab/application
>=3.0.0 <3.1.0          >=2.0.0 <3.0.0   @jupyterlab/apputils

As I understand it lab extensions that work with lab v2 won't work with v3 unless they are upgraded. Is that correct?

Right, although most extensions could start with the compatibility range update and publish a new release: https://jupyterlab.readthedocs.io/en/stable/extension/extension_migration.html#upgrading-library-versions-manually
Before switching to the new distribution system with pip and conda. This means the existing jupyter labextension install commands usually placed in the postBuild should still work.

A big task we need to tackle is how to transition repositories that rely on repo2docker using lab v2. In particular there are repos which install lab extensions but don't specify the version of lab that they want (or specify it not well enough). This is partly our fault because we recommend to people not to include things like lab in their environment.yml :-/

Fortunately, lab checks whether the extension is compatible before installing it. So if there is an extension that has been published to work with 2 and 3, lab will pick the correct one.

Maybe some compromise we can actually implement is to detect that the repo isn't compatible, stop running and exit with a clear error message that links to documentation that explains how to get the repo working again.

I think this should already happen if the postBuild is set to stop and exit on error. If repo2docker updates to JupyterLab 3 and the repo still uses jupyter labextension install commands in the postBuild to install extensions, then lab will do the compatibility check and output an error if it can't find a suitable version, that looks like the following:
Conflicting Dependencies:
JupyterLab              Extension        Package
>=3.0.0 <3.1.0          >=2.0.0 <3.0.0   @jupyterlab/application
>=3.0.0 <3.1.0          >=2.0.0 <3.0.0   @jupyterlab/apputils

Eventually most lab extensions will switch to the new distribution system and will be bundled in the Python package. Which would make the use of postBuild less necessary.

Eventually most lab extensions will switch to the new distribution system and will be bundled in the Python package. Which would make the use of postBuild less necessary.

Just updated to the latest jupyterlab which includes bug fixes, and to jupyter-offlinenotebook==0.2.0 (although this one could be updated separately first in https://github.com/jupyterhub/repo2docker/pull/997)
Also it looks like https://github.com/jupyterhub/repo2docker/pull/1001 should fix the failing Python 3.8 tests.

Just updated to the latest jupyterlab which includes bug fixes, and to jupyter-offlinenotebook==0.2.0 (although this one could be updated separately first in https://github.com/jupyterhub/repo2docker/pull/997)
Also it looks like https://github.com/jupyterhub/repo2docker/pull/1001 should fix the failing Python 3.8 tests.

With the figshare tests fixed by #1001, I think we should consider landing this one. It's a big change and there will likely be some repos with extensions that get caught out, but they should be able to add pins for jlab 2.x and/or update compatibility and be okay.
lab 3.0 is a big win for repo2docker with build times, so I think we should land this sooner rather than later.

Just rebased, and updated to the latest jupyterlab and ipywidgets.

Would you mind updating jupyter-offlinenotebook to 0.2.1 as it contains a minor UI fix?
If there are no objections from anyone else to getting this merged ASAP I'll close https://github.com/jupyterhub/repo2docker/pull/997 since the main motivation for that PR was to make it easy for users wanting to update to JupyterLab 3 in their requirements/environment files ahead of R2D.

The failing unit test in this PR is also failing on master: https://github.com/jupyterhub/repo2docker/runs/1885401808
 =========================== short test summary info ============================
FAILED unit/test_env.py::test_env - assert 'declare -x FOO="1613113980.512764...
====== 1 failed, 228 passed, 2 xpassed, 11 warnings in 822.25s (0:13:42) =======

Would you mind updating jupyter-offlinenotebook to 0.2.1 as it contains a minor UI fix?

Sure, will do :+1:

test_env is getting flaky (#1008) and shouldn't block this PR. It's the only failure

I've added this to the agenda for tomorrow's JupyterHub meeting: https://hackmd.io/YpwhVwbSSpCG19I0JNpqjQ

It would be amazing for this to land!

I've added this to the agenda for tomorrow's JupyterHub meeting: https://hackmd.io/YpwhVwbSSpCG19I0JNpqjQ

Thanks @manics, happy to join tomorrow's meeting to discuss the PR if needed.

per @jtpio's request, re-ran the benchmark from https://github.com/jupyterhub/repo2docker/pull/962 (i.e. manually extracting the time: lines from repo2docker output):

Since the jupyter labextension stage is entirely removed, this saves ~90 seconds or half of the time to set up the base environment. Excellent!

Nice, thanks @minrk for posting the benchmark!

Wow, this is amazing.
I don't understand why we still see "install mamba" in the benchmark, since we use mambaforge.

Hum, yes, it may just come from the mamba update...


Prevent nv.utils.windowResize handler memory leak

The chart directives attach event handlers to the window resize event through NVD3's nv.utils.windowResize but do not clean them up on $scope destroy. We should override the nv.utils.widowResize method to make it scope aware. See: https://github.com/novus/nvd3/issues/504

Also, each of the chart directive nv.addGraph NVD3 chart generation calls is inside a watch on data which fires multiple times when the data array is altered. Each time this watch fires, another event handler is added using nv.utils.windowResize. Previously attached handlers are not removed.

Fixes in #21.


Hugo compiled with go1.6 branch gives template errors with some themes

When using a hugo binary compiled with the go1.6 development branch, some themes give errors related to template parsing.  For example, with hugo -t casper, errors like these pop up:
ERROR: 2015/12/07 template: theme/partials/li.html:10:21:
  executing "theme/partials/li.html" at <index .Site.Data.aut...>:
    error calling index: value is nil; should be of type string in theme/partials/li.html

The line in question in themes/casper/layouts/partials/li.html is:
        {{$author := index .Site.Data.authors .Params.author }}

hugo-compiled-with-go1.6 still finishes rendering the website without aborting, though the layout/formatting was off.
Meanwhile, hugo compiled with go1.5.x runs hugo -t casper perfectly fine without error.

For reference, from https://golang.org/pkg/text/template/, the predefined template global function index does the following:

Returns the result of indexing its first argument by the
following arguments. Thus "index x 1 2 3" is, in Go syntax,
x[1][2][3]. Each indexed item must be a map, slice, or array.

So, at first glance, index .Site.Data.authors .Params.author would be interpreted in Go syntax as something like .SiteData.authors[.Params.author], which doesn't quite seem to make sense, so, perhaps the theme's li.html has an error that was left undetected in go1.5 but will be correctly detected in go1.6?  Not sure yet.  I still have to figure out how index work exactly.  :-)

Does this fix it?
{{ $author := index .Site.Data.authors (.Params.author) }}

The argument check was introduced at upstream https://github.com/golang/go/commit/6599450016244b9e3e074e87d7064219ee2e5cf8. According to this commit, index ignores nil second argument and returns reflect.Zero value silently till this commit so no error occurred. I guess there is an article which doesn't have author frontmatter value and it causes the error with go 1.6.


Move to Java 8

Hamcrest future
Bump minimum version of Java to Java 8.
Most projects in my view that are using Java 5, 6 or 7, are stable, they are happy with the features currently provided in Hamcrest v1.3, or would be find using version 1.3 if they wanted to use Hamcrest. Not bumping the version I feel holds back hamcrest as after decades of years between Java versions it is now only 6 months before potential new changes are out and hamcrest should be reworked to handle the sudden step change.
Rebel Labs via Zero Turnaround did a conference, and 86.9% are using Java 8 for their main production application, with 6% Java 7 and 2.8% Java 6 or older.
9:52 mark in this Devoxx UK 2018 video
https://www.youtube.com/watch?v=vPqMWPJNSoA&index=90&list=PLRsbF2sD7JVpRvLpv_Cub94zsM1aHm-Op

This is obviously an important move. I think that Java 8 is a big enough change that it probably should have a new version and an API that exploits new features. A first step, however, would be to get everything to compile.
What I'm seeing is that more people than you might expect still have Java 7 code, so we should be careful about leaving them behind.

What about starting multiple parallel branches per java version. Then merge into the correct branch and forward and fix as required.
v2.x Java 7 or newer
v3.x Java 8 or newer
v4.x Java 11 or newer [NOTE 1]
Not sure what else to suggest otherwise those that do more to Java 9/10/11 will experience potentially more and more issues and might not be able to use hamcrest depending what the issues are.
NOTE 1 - no point Java 9 as already EOL, Java 10 will be EOL sept 2018 when Java 11 is out and that is LTS. And it might take a few months to decied and agree what approach to take and start implementing changes required.

@sf105 what's the biggest hurdle or blockers for updating to java8? Is it technical like overcoming generics or having the capacity to work on it?
If it's technical, I like to better understand the root of the problem. If it's capacity, I keep looking for places where I can help, but I need to see what are the challenges.

challenges.

I fear we still need to support Java 7, but maybe that could just be frozen.
for similar reasons we probably ought to support Java 8 for a while.
it's screaming for a more functional solution, but I haven't quite got the confidence about how to get there from here.

I like @nhojpatrick's numbering scheme.

What I'm seeing is that more people than you might expect still have Java 7 code, so we should be careful about leaving them behind.

@sf105 @tumbarumba these people can still use java 7 compatible old versions. What you probably do not see is that java 8+ based projects use hamcrest 1.3 + 3rd party extensions or own matchers libraries. E.g. mine MoreMatchers class has about 10 new methods. It's a nice coding exercise, but I'd prefer to take it from the standard lib.
Also I still do not understand your argument. What is the problem to support two generations of hamcrest simultaneously (like spring does; spring 4 does not require java 8; spring 5 requires java 8+) with separate set of versions?

I am a person that was until recently still developing a Java 1.6 application, it was finally upgraded to Java 1.8. But the code changes were minor upgrades and patches.
I accepted that the project would be left behind as we are running on out of support java and frameworks. Also we would not be actively looking at new features from frameworks, we would be using new features as use cases as supporting reasons the project needs to be uplifted so it is in supported version...
Another reason we should upgrade to Java 1.8, you can no longer do a fresh checkout and build of hamcrest using Java 1.7.
$ java -version && rm -rf ~/.gradle/wrapper && ./gradlew --version
java version "1.7.0_80"
Java(TM) SE Runtime Environment (build 1.7.0_80-b15)
Java HotSpot(TM) 64-Bit Server VM (build 24.80-b11, mixed mode)
Downloading https://services.gradle.org/distributions/gradle-4.10.2-bin.zip

Exception in thread "main" javax.net.ssl.SSLException: Received fatal alert: protocol_version
	at sun.security.ssl.Alerts.getSSLException(Alerts.java:208)
	at sun.security.ssl.Alerts.getSSLException(Alerts.java:154)
	at sun.security.ssl.SSLSocketImpl.recvAlert(SSLSocketImpl.java:1979)
	at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:1086)
	at sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1332)
	at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1359)
	at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1343)
	at sun.net.www.protocol.https.HttpsClient.afterConnect(HttpsClient.java:559)
	at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:185)
	at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1301)
	at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:254)
	at org.gradle.wrapper.Download.downloadInternal(Download.java:66)
	at org.gradle.wrapper.Download.download(Download.java:51)
	at org.gradle.wrapper.Install$1.call(Install.java:62)
	at org.gradle.wrapper.Install$1.call(Install.java:48)
	at org.gradle.wrapper.ExclusiveFileAccessManager.access(ExclusiveFileAccessManager.java:69)
	at org.gradle.wrapper.Install.createDist(Install.java:48)
	at org.gradle.wrapper.WrapperExecutor.execute(WrapperExecutor.java:107)
	at org.gradle.wrapper.GradleWrapperMain.main(GradleWrapperMain.java:61)
$

Circa 2004-2012, everyone complained that Java was slow to update, it took a few more years but since Java 9 it is being rolled out every 6 months with LTS every 8 releases, and Java 17 LTS is out Sept 2021.
All open source projects need to start doing roadmaps regarding dropping older version and supporting newer versions. So users when picking up newer versions know how long they have that major version in support for. Like debian, it's clear https://wiki.debian.org/DebianReleases


add GET /health

When bootstrapping our webapp or job tracker background process, it would be handy to quickly check if the job registry API is reachable and auth tokens/headers are working as expected.
Can we add a simple GET /health  handler that returns something like
{"health": "ok", "auth": "ok"}

with the "auth" field :

"ok" when auth headers are valid
"invalid" when auth headers are invalid
"missing" when auth headers are missing

Added a /health endpoint based on the existing Terminus package in the NestJS framework. Next to the requested health checks, it also supports ES health checks. The output will be as follows:
{
    "status": "ok",
    "info": {
        "elasticsearch-ping": {
            "status": "up"
        },
        "elasticsearch-health": {
            "status": "up"
        },
        "auth": {
            "status": "up",
            "state": "ok"
        }
    },
    "error": {},
    "details": {}
}

The information auth status is available at info.auth with the following parameters:

Name
Description
Values

status
General health status of the bearer token that is included in the request headers
up if the bearer token is still valid; down if something is wrong with the token

state
More details on the token status
ok is the token is valid; expired if the token has expired; invalid if the token structure is invalid; missing if there is no token in the authorization header

great, thanks


Add Open Collective to Readme

Hi, I'm making updates for Open Collective. Either you or another core contributor signed this repository up for Open Collective. This pull request adds financial contributors from your Open Collective https://opencollective.com/arrow ❤
What it does:

adds a badge to show the latest number of financial contributors
adds a banner displaying contributors to the project on GitHub
adds a banner displaying all individuals contributing financially on Open Collective
adds a section displaying all organizations contributing financially on Open Collective, with their logo and a link to their website

P.S: As with any pull request, feel free to comment or suggest changes.
Thank you for your great contribution to the Open Source community. You are awesome! 🙌
And welcome to the Open Collective community! 😊
Come chat with us in the #opensource channel on https://slack.opencollective.com - great place to ask questions and share best practices with other Open Source sustainers!
Pull Request Checklist
Thank you for taking the time to improve Arrow! Before submitting your pull request, please check all appropriate boxes:

[ ] 🧪 Added tests for changed code.
[ ] 🛠 All tests pass when run locally (run tox or make test to find out!).
[ ] 📚 Updated documentation for changed code.
[ ] ⏩ Code is up-to-date with the master branch.

If you have any questions about your code changes or any of the points above, please submit your questions along with the pull request and we will try our best to help!
Description of Changes

Codecov Report

Merging #767 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff          @@
##           master   #767   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files          10     10
  Lines        1696   1696
  Branches      288    288
=====================================
  Hits         1696   1696

Continue to review full report at Codecov.

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

Hey @monkeywithacupcake, thanks for the contribution. It seems that our linting CI is failing because of trailing whitespace. You can run pre-commit run --all-files to fix the changes locally before pushing.

I made edits directly in github interface. I did not clone the project to my machine. I just tried to check for trailing whitespace. Hopefully, I caught it.

Closing in favor of: https://github.com/crsmithdev/arrow/pull/779


Add link

Add a link in the 404 pages text in the nav the link should be to the home page “/“

Can I do this?

Well if I can I am done


Add Scythebill.rb v12.6.0

Scythebill is a desktop application for birders to keep track of
their life lists and birding records.

Thank you for the contribution. It needed some fixes, so they were made in d2b9782d4baf11a701e1cbbff1b05c039a660f1b. Your contribution is still included (and still credited to you), with the appropriate modifications. Please feel free to ask about any of the changes.


SCRIPT ERROR in event `onResourceStart': Error: No such export SmartSigns:GetSigns in resource SmartSigns

Hi, it seems that the SmartSigns integration has a problem that it makes SmartSigns a mandatory dependency otherwise it throws errors every time someone views the Live Map or the resource is restarted with players on the server.
[ script:sna-live-map] Uncaught Error: No such export SmartSigns:GetSigns in resource SmartSigns
[ script:sna-live-map] citizen:/scripting/v8/main.js(549,15): get
[ script:sna-live-map] @sna-live-map/server/server.js(21783,53):
[ script:sna-live-map] node:events(394,28): emit
[ script:sna-live-map] @sna-live-map/server/server.js(18369,22): emitReserved
[ script:sna-live-map] @sna-live-map/server/server.js(19943,14): _doConnect
[ script:sna-live-map] @sna-live-map/server/server.js(19913,18):
[ script:sna-live-map] node:internal/process/task_queues(78,11): processTicksAndRejections
[ script:sna-live-map]
[ script:sna-live-map] Error: No such export SmartSigns:GetSigns in resource SmartSigns

Was the SmartSigns resource updated? Since this was the correct export previously

Ah, I see. I didn’t read the description correctly, will make sure it’s an optional dependency.

This has been fixed in 0.2.2. Please download here: https://github.com/SnailyCAD/live-map/releases/tag/0.2.2


DropdownItem exposes onClick but is useless with Dropdown

DropdownItem's docs and code has onClick as a prop but it isn't really. Dropdown's onChange is used instead.
From @chrisdhanaraj:

Still onChange - it's designed to mimic select/textinput/other inputs

DropdownItem does actually have onClick and uses it. However, Dropdown overwrites it with its own event handler rendering anything the user puts pointless

Hi there! 👋
Thanks so much for reporting this issue. I went ahead and added a simple PR for this in #272, let me know if it doesn't address everything that you've mentioned, or if the behavior doesn't match what you're expectation is for this component!


fix: try publicRuntimeConfig

:tada: This PR is included in version 1.5.2 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.5.2 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Integration with rn-indy-sdk

rn-indy-sdk is an implementation of the indy-sdk that matches the API of the NodeJS Wrapper.
We should add support and documentation to use Aries Framework JavaScript in a React Native application.

[ ] Add documentation on how to use the framework with RN Indy SDK
[ ] Run tests with RN Indy SDK?
[ ] Document packages and globals that are native to NodeJS and need special handling when using RN

buffer → https://www.npmjs.com/package/buffer
events → https://www.npmjs.com/package/events
base64 → https://www.npmjs.com/package/base64url (#95)

@TimoGlastra Has there been any progress on this? I have imported aries-framework-javascript into my react-native app but since there isn't any example I can refer to I'm having trouble figuring it out.
At first, I faced issues where aries-framework-javascript couldn't find certain modules. Installing those modules seemed to have helped but can't be certain until I get the Agent up and running.
The issue I am currently facing is with the InboundTransporter & OutboundTransporter. I am not sure how to initialize these and they are a requirement for initializing the Agent so I was wondering if there is an example for react-native where at least all the initializations are taken care of.


Check with Stacey about future web accessibility requirements

She thought the rules were getting stricter - if so we may need to switch to using .png files (not .eps) and using pdflatex not dvips and ps2pdf. So we'd want to know sooner rather than later, preferably before the JTC Dec meeting. Chris and I have resolved lots of these issues for our Canadian stock assessments.

Just wanted to document the location of a 40 min recent NOAA brown-bag seminar on Section 508 compliance. Disclaimer - I haven't watched it yet but I plan on watching it. The seminar is focused on what the end product should look like and not how to get there using LaTex, but I am looking into other resources on how to get there. @taylori also provided another tutorial that I plan on looking at.

As discussed on the phone this morning, a good next step might be to send one of the Canadian assessments to Stacey and/or the NOAA people who look for accessibility to see if it meets their standards. @andrew-edwards and @cgrandin can you send us an example?

We had some emails about this, but they got a bit confusing (and then shutdown occurred). Closing for now (no time to look into anyway) but expect we may have to revisit at some point.

I just chatted with Stacey (at 2020 SRG meeting). She said the version of the draft I sent the other week was more compliant than last year's submitted assessment (not sure why as I don't think we did anything different). They can make it compliant in Adobe, it might take a day, but that's good for us. Just noticed an old issue that says the published version had some figures messed up, so we should double check the final published version with what we submit (if file sizes are similar that's probably a good sign).

Yes, let's ask Stacey to send us the to-be-published version for a quick
check of figures/tables.  Even more reason to get the final document out to
her by COB Monday.
On Fri, Feb 28, 2020 at 9:41 AM Andrew Edwards<EMAIL_ADDRESS>wrote:

I just chatted with Stacey (at 2020 SRG meeting). She said the version of
the draft I sent the other week was more compliant than last year's
submitted assessment (not sure why as I don't think we did anything
different). They can make it compliant in Adobe, it might take a day, but
that's good for us. Just noticed an old issue that says the published
version had some figures messed up, so we should double check the final
published version with what we submit (if file sizes are similar that's
probably a good sign).
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/pacific-hake/hake-assessment/issues/452?email_source=notifications&email_token=AB4T76VOHGLZOWPST5O7N43RFFEDZA5CNFSM4EUTW3LKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOENJQT4Q#issuecomment-592644594,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AB4T76SK5XVE3NBH2IIGKOLRFFEDZANCNFSM4EUTW3LA
.

--
Aaron M. Berger, Ph.D. Research Mathematical Statistician
Fishery Resource Analysis and Monitoring Division
Northwest Fisheries Science Center
2032 SE OSU Dr. Bldg. 955
Newport, OR 97365-5275
<EMAIL_ADDRESS><EMAIL_ADDRESS>

Just re-opening in case anything comes back to us from the 2020 assessment, but I think they can do it all manually (adding tags etc.) on the final version.

@andrew-edwards can you send me the pdf document you made that was "compliant" for a different assessment.
Our 2021 document will have to be at least "largely" compliant this year and tags cannot be added manually. I have made lots of headway on this for other documents compiled from .Rmd scripts as well as LaTex. I am hoping to start working on the hake files soon. As noted above, we are going to have to change .png files and to using pdflatex (at least that is what I am doing in other work). Please reply with thoughts because I would like to make sure that I am not in la la land and that everyone is up to speed.

TASKS

[ ] check document for equations and change to written explanations
[ ] set language
[ ] bring in new packages (pdfx, tagpdf)
[ ] change to png files
[ ] change make file

Yes, we had to switch from .eps to .png else the 'read out loud' stuff reads all the labels in the .eps files.  I'll add something here at some point.

Here are some pages on fixing tables (tagging):
https://github.com/pbs-assess/csasdown/wiki/Table-tagging-for-the-PDF

I did a bunch of testing on tagging tables for accessibility, and it is not good news:
https://github.com/pbs-assess/herringsr/issues/77

I wrote a Wiki on the web accessibility: https://github.com/pacific-hake/hake-assessment/wiki/How-to-make-the-document-web-accessible
So I will close this since it is mostly completed. I will start a new issue on alternative text.


Invalid PrismaClient.user.findUnique() invocation with 5.6.0

Bug description
Trying to find the unique user by email which is an unique field defined in the prisma schema file.
Upgrading Prisma from 4.6.1 to 5.6.0 results in the mentioned error.
It works fine when downgrading to the previous version (4.6.1).
How to reproduce
Tried following methods that result all in the mentioned error:

findUnque
findUniqueOrThrow
findFirst

Expected behavior
It should return an unique object with prisma 5.6.0 as the previous version.
Prisma information

// Add your schema.prisma

Invalid `PrismaClient.userInfo.findFirst()` invocation in
/app/src/controllers/AuthController.ts:150:42

→ 150   user = await PrismaClient.userInfo.findUnique(
data did not match any variant of untagged enum GraphQlBody

Environment & setup

OS: macOS
Database: PostgreSQL
Node.js version: v18.17.0

Prisma Version
5.6.0

Hey @dyangcoding ,
Did you get a chance to have a look at @aqrln  comment? It'd be helpful for us to move your issue forward.
Without further information, we'll have to close this issue. Thank you 🙏

Hi @dyangcoding,
Since we couldn't reach out to you to get more information necessary for reproduction and investigation, we unfortunately have to close this issue at this time. Please open a new issue with more details if you are still facing this problem.


avoid .to() followed by inplace mutation to appease export

Export currently has a restriction, where inplace mutations on the output of a call to aten.to() results in an error.
We should really lift this restriction, but in the meantime, this PR avoids hitting that problem in the quantization logic.
I tested by adding the following lines to the bottom of https://github.com/hustvl/ViTMatte/blob/main/modeling%2Fbackbone%2Fvit.py and confirming that export did not error:
quantize_(m, int8_dynamic_activation_int8_weight())
m = unwrap_tensor_subclass(m)

x = torch.randn(4, 3, 128, 128)
m = torch.export.export(m, (x,))
m2 = m.run_decompositions()
print(m2)

Stack from ghstack (oldest at bottom):

-> #1387

fyi @tugsbayasgalan @yushangdi

/opt/conda/lib/python3.11/site-packages/torchao/dtypes/uintx/block_sparse_layout.py:        y += bias
/opt/conda/lib/python3.11/site-packages/torchao/dtypes/uintx/plain_layout.py:        y += bias
/opt/conda/lib/python3.11/site-packages/torchao/dtypes/uintx/semi_sparse_layout.py:        y += bias
/opt/conda/lib/python3.11/site-packages/torchao/dtypes/uintx/tensor_core_tiled_layout.py:        y += bias
/opt/conda/lib/python3.11/site-packages/torchao/dtypes/uintx/uint4_layout.py:                y += bias
```

thanks, we can't use ghstack in torchao btw, you can use https://github.com/modularml/stack-pr or just normal git push

I'm not sure if changing this would have perf implications actually, probably need to benchmark a bit for the popular code paths

I think it is better to have export coverage in the CI if we can.

Related https://github.com/pytorch/pytorch/pull/138606

/cc @yushangdi

Related pytorch/pytorch#138606

fyi, @jerryzh168 @bhack , the approach in the PR linked above doesn't work. I'm trying out a new approach, mostly this:
if we have a.to(b), and b has a different dtype with a, then it must be a copy. In this case, we do not need to freeze the tensor. Instead, we use torch.ops.aten._assert_tensor_metadata.default to ensure that a must not have the same dtype as b.


How disable align-repository-header feature?

It conflict with Gitako caused misalignment.
png:

I think the cause is on this.
https://github.com/sindresorhus/refined-github/compare/20.7.2...20.7.9#diff-765d4988f08edb45ad447cfeab8a3421R3
Could we have a switch to disable the padding left for those do not want it. And could we change it to something smaller like cal(10%) is what I found reasonable.

We can try to fix the conflict with it

This gets weirder at larger resolutions:

This is not due to Refined GitHub. It happens even after you disable it

Actually, that was incorrect, I had some extra CSS being applied even without Refined GitHub.
However, Gitako here is adding some styles (that do essentially the same thing) but probably shouldn't, because Gitako’s intent is supposedly to add a file tree, not change the layout.
So you can open an issue on their repo asking to drop this unrelated change.
Regular (no extensions)

Gitako
Notice the misaligned header and commit content

@fregante I have a suggestion to remove !important because body:not(.full-width):not(.enterprise) .repohead> * { has sufficient priority.

@cipchk That element has a !important, so we must also use !important

This feature has now been dropped in https://github.com/refined-github/refined-github/pull/6247


Command line for windows to do chives plots

What is the command line to do chives plots? is the software available?

@Techdread https://github.com/stotiks/chia-plotter/releases, it says Chives release, does it mean it is suitable to create chia plot (not chives)?


Add The Swiftness

Adding information for my new blog, The Swiftness.

Fixed the feed URL and merged. Thanks!


⚠ Site ANTS has degraded performance

In 6dbc9f5, Site ANTS (https://ants.gouv.fr) experienced degraded performance:

HTTP code: 200
Response time: 3100 ms

Resolved: Site ANTS performance has improved in 58e44b2.


echarts5.0.1在线定制js下载不了

This issue is not created by echarts-issue-helper and will be soon closed.

谢谢反馈，已修复

谢谢反馈，已修复


Upon removing chromium is not uninstalled

Perhaps it would be beneficial to install chromium via dedicated helper, otherwise it's left dangling after app removal.

Ah you're right. I'm using the puppeteer script to install chromium but do nothing for uninstalling it.
I'll fix that

In fact I checked and a special version of chromium is being installed on cac-proxy/.cache directory and it gets removed on uninstall.
So I don't know what part of Chromium is left after desinstallation ?

No problem. it didn't fit to your needs ?

Haha no, I'm not the target audience, I was just testing some (CI?) issue reported somewhere IIRC.


multimodal inputs of clinical information in multiple instance learning

Feature
Multimodal inputs like clinical information in Multiple-instance learning
Pitch
When doing multiple-instance learning, as far as I read GitHub and the document, it seems we cannot use clinical information as input.  I would appreciate it if you could let me know how I can conduct such kinds of calculations.

"Multimodal models
In addition to training using image data, clinical data can also be provided as model input by passing annotation column headers to the variable input_header. This input is concatenated at the post-convolutional layer, prior to any configured hidden layers.
If desired, models can also be trained with clinical input data alone, without images, by using the hyperparameter argument drop_images=True."
https://slideflow.dev/training/
Per the github, this is included - I have not used it yet.  Hope this helps.

Thanks for suggesting this enhancement. At present, we have out-of-the-box support for multi-modal training (using clinical variables from the annotations file) for tile-based models only.
In version 2.3, we added a mm_attention_mil model that is designed to support multi-magnification input, by providing multiple bags (of arbitrary dimension) for each slide (https://slideflow.dev/mil/#multi-magnification-mil). In this design, each input modality has a separate attention head, and the attention-reduced feature vectors are reduced prior to being passed to the fully-connected layer at the end of the network.
Once could extend this existing multi-magnification functionality for arbitrary multi-modal support (e.g. clinical factors, gene expression, spatial transcriptomics, etc). To accomplish this, you'd need to generate bags for the new modality, then pass the folder of bags to the train_mil() function as described above.
With that said, it would be nice if Slideflow could perform this automatically to streamline easy multi-modal models trained on clinical data. We'd also like to be able to support muti-magnification & multimodal training for more architectures than just Attention_MIL. We are prioritizing development of more robust multimodal training tools for MIL and anticipate inclusion of a new toolset for this in version 2.5.


Possibilities to change settings directly as admin in browser

Gogs version (<IP_ADDRESS>6):
Git version: 2.7
Operating system:
Database (use [x]):

[ ] PostgreSQL
[x] MySQL
[ ] SQLite

Can you reproduce the bug at https://try.gogs.io:

[ ] Yes (provide example URL)
[ ] No
[x] Not relevant

Log gist:

Description
The possibilities to change all settings as admin directly in the web browser would be nice.
Regards
Gino
...

This is duplicated to https://github.com/gogits/gogs/issues/1072


Minor fixes

Please always provide the GitHub issue(s) your PR is for, as well as test URLs where your change can be observed (before and after):
Fix #514
Fix #486
Fix #516
Fix #358
Test URLs:

Before:

https://main--shredit--stericycle.aem.page/en-us/secure-shredding-services/one-off-shredding-service

After:

https://minor-fixes--shredit--stericycle.aem.page/en-us/secure-shredding-services/one-off-shredding-service

@MarquiseRosier the width issue is fixed, please check https://minor-fixes--shredit--stericycle.aem.page/en-us/secure-shredding-services/one-off-shredding-service


refactor: simplify to make seata-common more readable

Ⅰ. Describe what this PR did
I studied and read the seata source code in the seta-common module and found some optimization points.
Ⅱ. Does this pull request fix one issue?
Ⅲ. Why don't you add test cases (unit test/integration test)?
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

Codecov Report

Merging #2038 into develop will decrease coverage by 0.01%.
The diff coverage is 64.51%.

@@              Coverage Diff              @@
##             develop    #2038      +/-   ##
=============================================
- Coverage      55.03%   55.01%   -0.02%
- Complexity      2475     2477       +2
=============================================
  Files            444      444
  Lines          14794    14791       -3
  Branches        1746     1744       -2
=============================================
- Hits            8142     8138       -4
- Misses          5907     5908       +1
  Partials         745      745

Impacted Files
Coverage Δ
Complexity Δ

...rc/main/java/io/seata/common/util/StringUtils.java
24.39% <ø> (-1.81%)
16 <0> (ø)

...ain/java/io/seata/common/util/CollectionUtils.java
94.44% <100%> (ø)
32 <0> (ø)
:arrow_down:

...main/java/io/seata/common/util/ReflectionUtil.java
90.19% <100%> (ø)
14 <0> (ø)
:arrow_down:

...on/src/main/java/io/seata/common/util/NetUtil.java
54.92% <33.33%> (+0.76%)
15 <0> (ø)
:arrow_down:

.../java/io/seata/common/thread/RejectedPolicies.java
50% <50%> (ø)
2 <2> (+1)
:arrow_up:

.../io/seata/common/loader/EnhancedServiceLoader.java
63.55% <84.61%> (ø)
25 <3> (+1)
:arrow_up:

...server/store/file/FileTransactionStoreManager.java
56.5% <0%> (-0.64%)
29% <0%> (-1%)

Thanks!
Coming soon 1.0, priority review after 1.0.

@slievrly Thank you, can you review this pr when you are free?


Bug with screen orientation

When I scratch the scratch card and change the screen orientation a few times, it returns to initial state and I can not scratch again

Open the devtools, emulate a galaxy note 3, scrape a bit of the card and then change the orientation, the card will return to the initial state, but this happens randomly, sometimes with few changes of orientation, sometimes with many

Check the branch fix/screen-orientation.

Clone the repo git clone -b fix/screen-orientation git@github.com:Masth0/ScratchCard.git
yarn install
yarn dev (to start dev server :8080)
open localhost/dist

For me it works.

Worked for me too


feat(commands): Added /help and /merit commands

:tada: This PR is included in version 1.3.0 :tada:
Your semantic-release bot :package::rocket:


Add 'ID' field to credentials

Motivations:
Sometimes, a user has to specify different credentials for different
repositories that reside in the same host. In this case, we cannot
select the credentials based on hostname patterns, because their
hostnames are same.
Modifications:

Add id field to credentials.json
Add credentialId and defaultCredentialId field to mirrors.json
Update the documentation

Result:
Can specify different credentials for different repositories that reside
in the same host

Thanks for.reviewing :-)


ScreenEvaluation Indicator for game mode and play style

Something on the evaluation screen to tell the player what game mode and play style is currently active.

implemented in main branch, awaiting merge to new release


RFC: split write over multiple tapes

The Problem: Howto control/handle write operations, that consume multiple tapes?
I need to split up a btrfs-send/btrfs-receive pipe, since data will not fit on a single tape.
Solution proposel
LTFS should offer an api, advertising e.g.

"no space left",
" space left"

This will enable the callee to interrupt a write process without preprocessing the available free LTFS partition space.
The machanism how the EOT message is exchanged need to be discussed.
Callee needs to handle following tasks:

Write a mark/struct/file describing the active slice/parent/sibbling

LTO loader functions / manual operator intervention must be issued to unmount + unload the given tape

LTO loader functions / manual operator intervention must be issued to load + mount a new tape.

Write a mark/struct/file describing the active slice/parent/sibbling

continue to save the data pipe

this is just a rough starter. I haven't read any available solution on how to implement this featurerequest.
Any feedback is quite welcome.

I think you can use the extended attribute, ltfs.mediaDataPartitionAvailableSpace.
This EA shows the remaining capacity of data area actually. You can access this EA on user.ltfs.mediaDataPartitionAvailableSpace by getxattr(). Or you can use attr command with ltfs.mediaDataPartitionAvailableSpace.
See also https://github.com/LinearTapeFileSystem/ltfs/blob/f82968d6f5cf28d6e24499fc0d400080636153a5/src/libltfs/xattr.c#L1095

Another thought is you can use the extended attribute, ltfs.mediaDataPartitionAvailableSpace.
This EA shows the remaining capacity of data area actually. You can access this EA on user.ltfs.mediaDataPartitionAvailableSpace by getxattr(). Or you can use attr command with ltfs.mediaDataPartitionAvailableSpace.
See also https://github.com/LinearTapeFileSystem/ltfs/blob/f82968d6f5cf28d6e24499fc0d400080636153a5/src/libltfs/xattr.c#L1095

Thanks for the input.
For the backup process I'll try to calculate the needed space of given data beforehand sending it to the pipe. so roughtly

If source-len > ltfs.mediaDataPartitionAvailableSpace (on valid LTFS volume_name)

breakeup the source-data; source-len_trunk_(n) <= ltfs.mediaDataPartitionAvailableSpace on active volume_name)

send source-len_trunk_(n) down the pipe -> save to LTFS volume_name

check ltfs.mediaDataPartitionAvailableSpace >= 0 (successfully stored)

prepare new media (respect pool-membership, retension restrictions, etc for next volume_name)

get ltfs.mediaDataPartitionAvailableSpace on new active volume_name

if remaining source-data-len >  ltfs.mediaDataPartitionAvailableSpace

breakup the remaining source-data to source-len_trunk_(n+1)  <=  ltfs.mediaDataPartitionAvailableSpace

save parent LTFS volume_name on active LTFS volume_name

send source-len_trunk_(n+1) down the pipe -> save to LTFS volume_name

I have 2 things I would like to mention about capacity.
One is capacity, the other is sync.

For capacity, LTFS capacity is based on the remaining capacity information returned from the drive. So you need to take care about these things.

The Drive (at least IBM drive) returns native capacity
The "native" capacity means a capacity after H/W compression
LTFS formats a tape with compression on setting by default

So you may have bigger capacity than you expect after you write compressable data to LTFS.
For example, remaining capacity is 10GB. You write a 5GB file (2:1 compressable by the drive). Remaining capacity shall be 7.5GB.

For sync, I assume incremental snapshot you said is periodical index automatically committed by LTFS.
I recommend not to use periodical sync when you are using LTFS from another automated S/W.
You can commit (write an index) when your application want to commit all data if you use LTFS with -o sync_type=unmount and Access to ltfs.sync EA.
In my sense, you can get a reliable remaining capacity if you use the following sequence

Check a capacity
Write a file or some files
Write anything to ltfs.sync EA
Check a capacity (This value is reliable because new index shell be written in step3)

Close this issue because we don't have any additional comment from 12/19/2019.


Look up Kerberos auth on host when failed remotely

microsoft/vscode-copilot-release#1380

Is this PR included in the latest stable version 1.92.0? I still have problems when testing here, but the Insider is working.

Yes, this is in 1.92.


Can't run test:validateCoverage locally if mergeCoveragePath is set

Moving over to this from another Jest coverage module and so far, everything is going great except for one thing...
I've setup the config to use mergeCoveragePath: "some_folder" as the tests have been setup to run in parallel on the CI, however this has resulted in not being able to run tasks such as test:validateCoverage locally as I then get this error:
❯ npm run test:validateCoverage

><EMAIL_ADDRESS>test:validateCoverage
> npx jest-a-coverage-slip-detector

node:internal/fs/utils:350
    throw err;
    ^

Error: ENOENT: no such file or directory, scandir 'some_folder'

Wondering if there are any ways around this barring creating some_folder locally and copying the coverage.json out of the original coverage folder?

Thanks for reporting this issue! I've added extra validation to check if the directory exists with which gives a better error message in case you try to run the validation step when there isn't any output to process, what do you think of this approach?
https://github.com/GetJobber/jest-a-coverage-slip-detector/pull/32

The extra validation is good/better error message is definitely a good thing, however it doesn't help with our use case, which is that we can't run npm run test:validateCoverage locally if the tests are setup to run in parallel on the CI.
Having a look at the parallelism docs again though, is it the case that the mergeCoveragePath option could/should be ignored if the --merge argument isn't given?
Otherwise, there is no way to run the jest-a-coverage-slip-detector commands locally if using this setup.

Or maybe need coveragePath and mergeCoveragePath config options here?

The validate coverage command checks your latest persisted results against the targets and exceptions.

No, because jest is configured to store the coverage output in a coverage folder, so when npm run test:generateCoverage runs it outputs the coverage to that directory, but then when npm run test:validateCoverage runs it is looking for the mergeCoveragePath directory.
This is correct for the CI because we are doing the following:
# Run in parallel, generate multiple files
COVERAGE_REPORT_SHARD=final-coverage-files/coverage-final${CIRCLE_NODE_INDEX}.json
npm run test:ci $TESTFILES && mv coverage/coverage-final.json $COVERAGE_REPORT_SHARD

# In another job to validate all the test coverage
npm run test:validateCoverage -- --merge

But not locally, because final-coverage-files doesn't exist.

Just digging through the code, is it the case that currently https://github.com/GetJobber/jest-a-coverage-slip-detector/blob/main/src/mergeCoverage.js#L50 is running all the time but should only run if the --merge flag is present?

Oh and yes, merge actually happens all the time, by default (there is actually a config that defaults to true for that called alwaysMerge), which I had to add to compensate for incorrect coverage output from jest: https://github.com/GetJobber/jest-a-coverage-slip-detector/pull/19

So the root problem here is that in CI, the CI script has special knowledge of how to shift the jest coverage output to the desired target location, but when running locally, nothing has that knowledge.
What I'm thinking is that when running locally and the merge flag is absent, and the target folder doesn't exist, it should fallback to the coverage folder configured in jest (which should be detectable). Let me try that...

So it's actually not as easily detectable as I was imagining - and really, that's getting a bit complicated - on second thought, let's just turn the workaround into the solve - instead of allowing a configurable output directory that might be different than jest, let's just dictate that it needs to be the same. Easy peasy.
Check the PR for the updates to the documentation and let me know what you think!

Doesn't look like making those changes will work.
I've updated "mergeCoveragePath": "coverage" and the CI task is now:
cp -R coverage/coverage-final.json coverage/coverage-${CIRCLE_NODE_INDEX}.json

But now when the validate task runs a lot of the coverage is missing. I don't know if that is down to how CircleCI is attaching the workspace in the coverage job or not though.
We are using this to store the coverage on the CI (using CircleCI)
      - persist_to_workspace:
          root: .
          paths:
            - coverage

And then this in the coverage job
      - attach_workspace:
          at: .

Before this change it would have been persisting the merge directory "some_folder" and there would be no filename clashes between the JSON files. I wonder if now it is storing the entire coverage directory, with the same html files etc it is causing an issue.

I do have a hack around this issue...
    "test:ci:validateCoverage": "npx jest-a-coverage-slip-detector",
    "test:validateCoverage": "mkdir -p ci-coverage && cp coverage/coverage-final.json ci-coverage/ && jest-a-coverage-slip-detector"

But now when the validate task runs a lot of the coverage is missing.

It looks like you're outputting your sharded coverage as coverage-1.json, coverage-2.json - if so, you'll need to update the config input: { mergePrefix: "coverage-final" } to be "coverage", or else it will only pick-up the final shard's output
should be working locally though, right?

Did the above changes (used coverage-final-${CIRCLE_NODE_INDEX}.json) and was able to ditch the workaround too.
Thanks for the help.


Update breeding tutorial code snippets

Relation to PR: https://github.com/substrate-developer-hub/substrate-node-template/pull/297

This has been updated already.


Fixes flutter build ipa failure: Command line name "app-store" is deprecated. Use "app-store-connect"

Fixes https://github.com/flutter/flutter/issues/149369
Pre-launch Checklist

[x] I read the [Contributor Guide] and followed the process outlined there for submitting PRs.
[x] I read the [Tree Hygiene] wiki page, which explains my responsibilities.
[x] I read and followed the [Flutter Style Guide], including [Features we expect every widget to implement].
[x] I signed the [CLA].
[x] I listed at least one issue that this PR fixes in the description above.
[x] I updated/added relevant documentation (doc comments with ///).
[x] I added new tests to check the change I am making, or this PR is [test-exempt].
[x] I followed the [breaking change policy] and added [Data Driven Fixes] where supported.
[ ] All existing and new tests are passing.

🙏

Took the liberty to rebase on main since there shouldn't be golden changes on this PR.

Golden file changes have been found for this pull request. Click here to view and triage (e.g. because this is an intentional change).
If you are still iterating on this change and are not ready to resolve the images on the Flutter Gold dashboard, consider marking this PR as a draft pull request above. You will still be able to view image results on the dashboard, commenting will be silenced, and the check will not try to resolve itself until marked ready for review.
For more guidance, visit Writing a golden file test for package:flutter.
Reviewers: Read the Tree Hygiene page and make sure this patch meets those guidelines before LGTMing.
Changes reported for pull request #150407 at sha d9fb228

@jmagman what

Took the liberty to rebase on main since there shouldn't be golden changes on this PR.

thank youuuuuuuu

auto label is removed for flutter/flutter/150407, due to - The status or check suite Linux analyze has failed. Please fix the issues identified (or deflake) before re-applying this label.

Rebased onto https://github.com/flutter/flutter/pull/150882


Leaderboard

Leaderboard setup
In this project I:

Used Gitflow
Created an npm project with webpack.

@brytebee Thank you, I loved the gif :). There's just one thing I don't get, do I merge it only with the development branch or both the development & the main branch.


Gateway v2 - unable to setup Avalanche nodes getting error of "Please check your node URL, API Key, and internet connection.."

Describe the bug
While testing the gateway, the node used for the avalanche chain which is Moralis speedynode has been discontinued resulting in the gateway returning an error of Please check your node URL, API Key, and internet connection.. We tried to use the old avalanche node  setup from v1.4.0 but it is still returning the same error:

While it works for v1.4.0, it doesn't for development branch dev-1.6.0 and version 1.5.0
Steps To Reproduce

Clone and install development branch
Manually created docker gateway from /gateway folder for testing
Run gateway create
Run gateway config avalanche.networks.nodeURL https://api.avax.network/ext/bc/C/rpc

Release version
version 1.5 and development dev-1.6

fixed


Support Other Data Types

Changes getItem and setItem to support any data type for values, instead of only strings, like localforage. Also localstorage returns null when there's no value - never undefined - so update the MemoryStorage mock to reflect this.
fixes #21

Thanks for the PR.


MM-11024 Migrate to use plugin v2 system coming in Mattermost 5.2

Please don't merge until plugins-2 is merged into master of the server repo

Codecov Report

Merging #1 into master will decrease coverage by 1.08%.
The diff coverage is 87.5%.

@@            Coverage Diff            @@
##           master      #1      +/-   ##
=========================================
- Coverage   87.59%   86.5%   -1.09%
=========================================
  Files           3       3
  Lines         137     126      -11
=========================================
- Hits          120     109      -11
  Misses          9       9
  Partials        8       8

Impacted Files
Coverage Δ

main.go
0% <0%> (ø)
:arrow_up:

plugin.go
92.3% <100%> (-1.7%)
:arrow_down:

Continue to review full report at Codecov.

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


Refactor SQL generation, part 2

Coverage increased (+0.4%) to 83.657% when pulling fc0a17a163a39cb868d4172a47501257971cc657 on refactor-sql-generation-part-2 into 657ad8d04e4dfdc6cf895061fe900692853ebb2a on master.


Embed templates into binary

I can't tell what templates/graph/exp/ is for.
There is also no way to use full.tmpl rather than auto.tmpl in the current setup

thanks @remram44


Feature Request - Persistent Tokens for Services

Issue Name
Persistent Tokens for Services
Summary
At MAXIV and maybe also at other facilities we use functional accounts for different purposes. These services needs to log in with username and password to get a token every time they wants to push something to SciCat. I wonder if it is possible to get persistent token for there services.

One could extend the lifetime of the tokens generated. I dont know if there is a built in limit for this currently.

@stephan271  the server appears to have an expiresIn configuration for this.  https://github.com/SciCatProject/backend/blob/b8eeeb007c71a6bafa79af79db70775c788479af/server/boot/JWT.js#L6

@nguyenlinhlinh If I remember it correctly, if you sign in, the token you get back is valid forever, unless you sign in again with that same account. If that's not the case, here's how to set it up: https://stackoverflow.com/questions/32738285/creating-permanent-accesstoken-in-loopback

Thank you everyone for the input. Thank @henrikjohansson712, I will check it out.

I tried to generate persistent token by logging in with ttl: -1  and it didnt work. I can see in the db that ttl is set to -1 but after a week I tried to request proposals I got 401.
{"username": "archiveManager", "password": "xxxxx", "ttl": -1}


bugfix-align-episodes

There is a formula to calculate workers, episodes and round robin distance: -

The default DOTS parameters didn't follow that formula.  As the default workers is 2 to maximise use of g4dn.2xlarge default instances and 0.05 round robin distance matches the console experience of moving 5% along the track per episode the fix is to increase episodes to 40 so each worker gets 20 episodes per iteration.

fixes https://github.com/aws-deepracer-community/deepracer-on-the-spot/issues/75


Update CORS status for JSONBin.io

Thank you for taking the time to work on a Pull Request for this project!
To ensure your PR is dealt with swiftly please check the following:

[x ] Your submissions are formatted according to the guidelines in the contributing guide
[ x] Your additions are ordered alphabetically
[ x] Your submission has a useful description
[ x] The description does not end with punctuation
[ x] Each table column should be padded with one space on either side
[ x] You have searched the repository for any relevant issues or pull requests
[ x] Any category you are creating has the minimum requirement of 3 items
[ x] All changes have been squashed into a single commit

JSONBin.io has enabled CORS. Updating the CORS option to Yes which was previously set to Unknown.

Thanks!


Add "EXPLAIN" Button

When I'm debugging a query I need to see if the crazy query I just type will RUN and/or use the new index before waiting 10-75 seconds to know its "Bad" .   next to the RUN  play button have a "Explain" button

Hey, thanks for the suggestion, added a explain button next to the run query button in the latest release.


Bug: role field containing special characters cause unexpected behavior with add command

The role field in the add command is too lenient, allowing special characters like '/' and spaces. Roles like "Member /p999" are accepted but using add r/Member /p999 ... fails because /p is treated as a phone field instead of part of the role.
To reproduce:
add n/John Doe p/98765432<EMAIL_ADDRESS>t/johnDoe12 r/Exco Member p/999 f/
Suggestion:
Maybe restrict the role field to only accept alphanumeric and special characters like space, dash, underscore, up to your discretion.
^[a-zA-Z0-9 _-]+$

I think it might be better to not restrict the usage of /, since that could be considered a feature flaw.
We could explicitly state in the user guide instead that " n/", " p/", " t/", " r/" and " f/" are reserved keywords and cannot be used in as part of an existing parameter (even though the non spaced version e.g. "n/" can). This check is already implemented as part of ab3
I think this restriction gives more freedom to the user since we don't have to only allow a seemingly arbitrary subset of special characters, and we can also enforce this behaviour for names (in issue #113)


Revert "To deploy updates to website"

Reverts sudhay23/ShopOnline-Web-App#99

yes its not working


Create c4 diagram for satellite sites

I will add to the documentation once the diagram is reviewed

LGTM :thumbsup: Asked Nils Magne the c4 expert Lunde wether we need to include the existing DAM in this diagram, but I guess that's not necessary?

So this has probably been covered in discussions/meetings about the satellite sites, but just to confirm the way I understand this is as follows:

Global (EN/NO) has its own dataset and is hosted on Sanity servers
Satellite sites each get their own dataset (one per site) and these studios are hosted on their own Radix instance (one per site)

So there is a Brazil dataset with a Brazil studio hosted on Radix and a Brazil Next.js instance on Radix
Then there is a UK dataset with a UK studio hosted on Radix and a UK Next.js instance on Radix
etc

Codebase is the same across the global and satellite sites, same code same repo
We use env variables in the CI setup to deploy to each individual site accordingly

This has now been incorporated in the existing drawings. May use as reference for the architecture contract though.


run through supervisord (bug 1122190)

As noted in the related PR a bin dir seems odd for a conf file.
Otherwise r+wc.


fix: vercel api failure after revamp

Figure out why train is failing

@techyNonso use logs

Login with vercel with shared email

Made a pr already , the only issue I saw was that for some reason,  web3.storage was not resolved. Have reinstalled it and made a pr

@techyNonso link the pr with the issue by specifying Resolves or Fixes #

@techyNonso Blocked: not able to login in

Investiagtion complete: lighthouse apis are failing cuz env var missing in the vercel deployment

Resolved


protodoc: Add redirects for v2 protos to current version and links to old

Commit Message: protodoc: Add redirects for v2 protos to current version and links to old
Additional Description:
Risk Level:
Testing:
Docs Changes:
Release Notes:
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue] Fix #16297
[Optional Deprecated:]
[Optional API Considerations:]

docs rendered here - https://storage.googleapis.com/envoy-pr/16303/docs/index.html

this PR now requires jq which i think is a good thing to add in general
I have hacked it in here for now - but ive also raised a PR in envoy-build-tools to add https://github.com/envoyproxy/envoy-build-tools/pull/132
there is alternately a bazel recipe i found here https://github.com/kythe/kythe/blob/master/third_party/jq.BUILD
im happy to resolve in any of the above ways - as long as we can add it

Code looks good. Looking at the docs, the box on the RHS is a bit of an eye sore. I know you are thinking of tabs here, is there any way to make the docs less cluttered before landing them?

Code looks good. Looking at the docs, the box on the RHS is a bit of an eye sore. I know you are thinking of tabs here, is there any way to make the docs less cluttered before landing them?

this is the best i could come up with before shifting things to tabs - it needs to work in a few different situtations
this is far from ideal - but i would like to this landed and then work on the tabs - which will take some time in terms of figuring out how best to render - im working on it already tho...

/retest


Bot real slow to post / edit.

Hi,
I had great success with this project when using ollama.
I swapped to a model that runs on koboldai (openai compatible) and now the bot responses take ages.
It processes the input quick and has the answer ready in ~30 seconds max, but when the bot is posting the answer to discord, python3 starts running 100% on a single core and the bot takes ages to finish posting.
Any idea what I'm doing wrong?

I haven't tested with koboldai so I can't guarantee support for it. What specific model are you using? Have you tried others?


Added example which displays a clock.

Thank you for creating a pull request to contribute to Adafruit's GitHub code!
Before you open the request please review the following guidelines and tips to
help it be more easily integrated:

Added an additional example script.  It turns the display into a clock.

N/A

N/A

Thank you again for contributing!  We will try to test and integrate the change
as soon as we can, but be aware we have many GitHub repositories to manage and
can't immediately respond to every request.  There is no need to bump or check in
on a pull request (it will clutter the discussion of the request).
Also don't be worried if the request is closed or not integrated--sometimes the
priorities of Adafruit's GitHub code (education, ease of use) might not match the
priorities of the pull request.  Don't fret, the open source community thrives on
forks and GitHub makes it easy to keep your changes in a forked repo.
After reviewing the guidelines above you can delete this text from the pull request.

This is a good example to have

On my setup, the other examples work out of the box, but this clock example is upside down.
+1 from my point of view to have a clock example would be nice.

hiya, this library is being deprecated - we have a similar library that works with Python3 and modern linux computers. please check out this guide for more info
https://learn.adafruit.com/monochrome-oled-breakouts/python-wiring
https://github.com/adafruit/Adafruit_CircuitPython_SSD1306/blob/master/examples/ssd1306_pillow_clock.py


Verbose creating dumps + crashed the server

Good afternoon,
While looking for a permission using /lp verbose, I got spammed some WitherAC permissions and then when checking console I had some dumps until the server crashed
https://hasteb.in/imejuyeq.shell
LuckPerms version 5.1.82
Server: Tuinity version git-Tuinity-"7b639ea" (MC: 1.16.1)

Your paste seems to have expired.
Try using /lp verbose record instead, followed by /lp verbose paste to use the web viewer instead of ingame output, and/or filter out the witherac checks using !witherac at the end of the verbose command.


Remove unused components, classes.

Codecov Report

Merging #1 (faafd4f) into dev (7b54be7) will increase coverage by 3.75%.
Report is 5 commits behind head on dev.
The diff coverage is n/a.

:exclamation: Current head faafd4f differs from pull request most recent head 13a733e. Consider uploading reports for the commit 13a733e to get more accurate results

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files

@@            Coverage Diff             @@
##              dev       #1      +/-   ##
==========================================
+ Coverage   71.51%   75.26%   +3.75%
==========================================
  Files        1351      877     -474
  Lines       31873    17801   -14072
  Branches     6006     5002    -1004
==========================================
- Hits        22793    13398    -9395
+ Misses       8833     4403    -4430
+ Partials      247        0     -247

Flag
Coverage Δ

unittests
75.26% <ø> (+3.75%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.
see 522 files with indirect coverage changes


Kucoin - with order_refresh_time (15mins or more) got OSError executing request, error code 400002 Invalid KC-API-TIMESTAMP

Describe the bug
When running test on kucoin spot, we observed instances of these errors while the connector was fetching trade updates, balances or trying to cancel an active order
Failed to fetch trade updates:
2024-02-22 14:59:16,360 - 71791 - hummingbot.connector.exchange.kucoin.kucoin_exchange.KucoinExchange - WARNING - Failed to fetch trade updates. Error: Error executing request GET https://api.kucoin.com/api/v1/fills. HTTP status is 400. Error: {"code":"400002","msg":"Invalid KC-API-TIMESTAMP"}

Failed to cancel order:
2024-02-22 15:17:04,438 - 71791 - hummingbot.connector.exchange.kucoin.kucoin_exchange.KucoinExchange - ERROR - Failed to cancel order BSLUT611f300c7f139e43fde9f696090a26c784d
Traceback (most recent call last):
  File "/Users/rapcomia/github/hummingbot/staging/hummingbot/connector/exchange_py_base.py", line 520, in _execute_order_cancel
    cancelled = await self._execute_order_cancel_and_process_update(order=order)
  File "/Users/rapcomia/github/hummingbot/staging/hummingbot/connector/exchange_py_base.py", line 540, in _execute_order_cancel_and_process_update
    cancelled = await self._place_cancel(order.client_order_id, order)
  File "/Users/rapcomia/github/hummingbot/staging/hummingbot/connector/exchange/kucoin/kucoin_exchange.py", line 226, in _place_cancel
    cancel_result = await self._api_delete(
  File "/Users/rapcomia/github/hummingbot/staging/hummingbot/connector/exchange_py_base.py", line 875, in _api_delete
    return await self._api_request(*args, **kwargs)
  File "/Users/rapcomia/github/hummingbot/staging/hummingbot/connector/exchange_py_base.py", line 905, in _api_request
    request_result = await rest_assistant.execute_request(
  File "/Users/rapcomia/github/hummingbot/staging/hummingbot/core/web_assistant/rest_assistant.py", line 47, in execute_request
    response = await self.execute_request_and_get_response(
  File "/Users/rapcomia/github/hummingbot/staging/hummingbot/core/web_assistant/rest_assistant.py", line 99, in execute_request_and_get_response
    raise IOError(f"Error executing request {method.name} {url}. HTTP status is {response.status}. "
OSError: Error executing request DELETE https://api.kucoin.com/api/v1/orders/65d6f1206100db0007218806. HTTP status is 400. Error: {"code":"400002","msg":"Invalid KC-API-TIMESTAMP"}

Failed to update balance:
2024-02-22 17:09:16,591 - 71791 - hummingbot.connector.exchange.kucoin.kucoin_exchange.KucoinExchange - WARNING - Failed to update balances. Error: Error executing request GET https://api.kucoin.com/api/v1/accounts. HTTP status is 400. Error: {"code":"400002","msg":"Invalid KC-API-TIMESTAMP"}
Traceback (most recent call last):
  File "/Users/rapcomia/github/hummingbot/staging/hummingbot/connector/exchange_py_base.py", line 938, in _update_all_balances
    await self._update_balances()
  File "/Users/rapcomia/github/hummingbot/staging/hummingbot/connector/exchange/kucoin/kucoin_exchange.py", line 320, in _update_balances
    response = await self._api_get(
  File "/Users/rapcomia/github/hummingbot/staging/hummingbot/connector/exchange_py_base.py", line 863, in _api_get
    return await self._api_request(*args, **kwargs)
  File "/Users/rapcomia/github/hummingbot/staging/hummingbot/connector/exchange_py_base.py", line 905, in _api_request
    request_result = await rest_assistant.execute_request(
  File "/Users/rapcomia/github/hummingbot/staging/hummingbot/core/web_assistant/rest_assistant.py", line 47, in execute_request
    response = await self.execute_request_and_get_response(
  File "/Users/rapcomia/github/hummingbot/staging/hummingbot/core/web_assistant/rest_assistant.py", line 99, in execute_request_and_get_response
    raise IOError(f"Error executing request {method.name} {url}. HTTP status is {response.status}. "
OSError: Error executing request GET https://api.kucoin.com/api/v1/accounts. HTTP status is 400. Error: {"code":"400002","msg":"Invalid KC-API-TIMESTAMP"}

On the attached log file:

2024-02-22 17:57:19,179 - Failed to cancel error occurred
2024-02-22 18:02:24,273 - Connector fixed itself and orders canceled successfully
Took 5mins to cancel orders ok and seen happened again on later timeframes
This is also observed when stop command is initiated causing orders to be stuck on exchange.

Tried to run again stop command so it can try to recheck active orders but still same error

Steps to reproduce

Add Kucoin spot API keys
Setup a v1(Pure Market Making) or v2 strategy script with long refresh time (15mins or more)
Start and observe after couple of hours

Release version
dev-1.25.0
Type of installation
Source
Attach required files
logs_pmm-kucoin1.log

Not able to reproduce after testing 3/3 local and cloud

After reviewing logs of bot running on kucoin via hbot-deploy, found this issue occurred on most of the instances with more than 10mins refresh time. Test has been done on both local and cloud
Unexpected error while listening to user stream. Retrying after 5 seconds...
2024-06-20 23:03:07,725 - 14 - hummingbot.core.data_type.order_book_tracker - INFO - Initialized order book for XCAD-USDT. 1/1 completed.
2024-06-20 23:03:07,858 - 14 - hummingbot.connector.exchange.kucoin.kucoin_api_user_stream_data_source.KucoinAPIUserStreamDataSource - ERROR - Unexpected error while listening to user stream. Retrying after 5 seconds...
Traceback (most recent call last):
  File "/home/hummingbot/hummingbot/core/data_type/user_stream_tracker_data_source.py", line 45, in listen_for_user_stream
    self._ws_assistant = await self._connected_websocket_assistant()
  File "/home/hummingbot/hummingbot/connector/exchange/kucoin/kucoin_api_user_stream_data_source.py", line 34, in _connected_websocket_assistant
    connection_info = await rest_assistant.execute_request(
  File "/home/hummingbot/hummingbot/core/web_assistant/rest_assistant.py", line 47, in execute_request
    response = await self.execute_request_and_get_response(
  File "/home/hummingbot/hummingbot/core/web_assistant/rest_assistant.py", line 100, in execute_request_and_get_response
    raise IOError(f"Error executing request {method.name} {url}. HTTP status is {response.status}. "
OSError: Error executing request POST https://api.kucoin.com/api/v1/bullet-private. HTTP status is 400. Error: {"code":"400002","msg":"Invalid KC-API-TIMESTAMP"}

Failed to fetch updates
2024-06-20 22:59:19,860 - 14 - hummingbot.connector.exchange.kucoin.kucoin_exchange.KucoinExchange - WARNING - Failed to fetch trade updates. Error: Error executing request GET https://api.kucoin.com/api/v1/fills. HTTP status is 400. Error: {"code":"400002","msg":"Invalid KC-API-TIMESTAMP"}

Failed to fetch balances
2024-06-20 23:04:13,722 - 14 - hummingbot.connector.exchange.kucoin.kucoin_exchange.KucoinExchange - WARNING - Failed to update balances. Error: Error executing request GET https://api.kucoin.com/api/v1/accounts. HTTP status is 400. Error: {"code":"400002","msg":"Invalid KC-API-TIMESTAMP"}
Traceback (most recent call last):
  File "/home/hummingbot/hummingbot/connector/exchange_py_base.py", line 940, in _update_all_balances
    await self._update_balances()
  File "/home/hummingbot/hummingbot/connector/exchange/kucoin/kucoin_exchange.py", line 326, in _update_balances
    response = await self._api_get(
  File "/home/hummingbot/hummingbot/connector/exchange_py_base.py", line 863, in _api_get
    return await self._api_request(*args, **kwargs)
  File "/home/hummingbot/hummingbot/connector/exchange_py_base.py", line 906, in _api_request
    request_result = await rest_assistant.execute_request(
  File "/home/hummingbot/hummingbot/core/web_assistant/rest_assistant.py", line 47, in execute_request
    response = await self.execute_request_and_get_response(
  File "/home/hummingbot/hummingbot/core/web_assistant/rest_assistant.py", line 100, in execute_request_and_get_response
    raise IOError(f"Error executing request {method.name} {url}. HTTP status is {response.status}. "
OSError: Error executing request GET https://api.kucoin.com/api/v1/accounts. HTTP status is 400. Error: {"code":"400002","msg":"Invalid KC-API-TIMESTAMP"}

Unexpected error while fetching trading fees.
2024-06-20 23:05:50,691 - 14 - hummingbot.connector.exchange.kucoin.kucoin_exchange.KucoinExchange - NETWORK - Unexpected error while fetching trading fees.
Traceback (most recent call last):
  File "/home/hummingbot/hummingbot/connector/exchange_py_base.py", line 752, in _trading_fees_polling_loop
    await safe_gather(self._update_trading_fees())
  File "/home/hummingbot/hummingbot/core/utils/async_utils.py", line 22, in safe_gather
    return await asyncio.gather(*args, **kwargs)
  File "/home/hummingbot/hummingbot/connector/exchange/kucoin/kucoin_exchange.py", line 370, in _update_trading_fees
    resp = await self._api_get(
  File "/home/hummingbot/hummingbot/connector/exchange_py_base.py", line 863, in _api_get
    return await self._api_request(*args, **kwargs)
  File "/home/hummingbot/hummingbot/connector/exchange_py_base.py", line 906, in _api_request
    request_result = await rest_assistant.execute_request(
  File "/home/hummingbot/hummingbot/core/web_assistant/rest_assistant.py", line 47, in execute_request
    response = await self.execute_request_and_get_response(
  File "/home/hummingbot/hummingbot/core/web_assistant/rest_assistant.py", line 100, in execute_request_and_get_response
    raise IOError(f"Error executing request {method.name} {url}. HTTP status is {response.status}. "
OSError: Error executing request GET https://api.kucoin.com/api/v1/trade-fees. HTTP status is 400. Error: {"code":"400002","msg":"Invalid KC-API-TIMESTAMP"}

This should be fixed with #7103, can we close this issue?


Split ObjC tests

Follow-up of #18919. With the new organization of the tests, now we can further split the tests so that they can run parallel, reducing the total test time.

BasicTests ObjC expected to fail.
InteropCloud-to-* Tests failed due to infrastructure reason (Dart SDK version error)


Supporting Rust 1.12 for Rayon

In order to use Crossbeam in Rayon, we need to support Rust 1.12.  More discussions are in: https://github.com/rayon-rs/rayon/pull/480 .
I hope it is the only remaining blocker for Rayon.

Supporting this in crossbeam-utils turns out to be unnecessarily annoying, because the usage of #[repr(align(n))] syntax under the nightly feature breaks rustc 1.12, which does not recognise that syntax. Rustc also tries to parse the file even when the nightly implementation is put into a separate file, with that file's mod statement guarded by feature = "nightly". The only solution I see at the moment is to support two versions, i.e. first publish 0.3.0 without nightly support, but working for 1.12 and then 0.4.0 for more recent versions. If anyone figures out how to conditionally compile a file, that would avoid the version split.

@joshlf That actually worked, thanks!

Awesome, np!

We dedicated crossbeam-epoch 0.3.0 for Rust 1.13, and I think it's the best we can do for now: supporting Rust 1.12.1 will require a huge effort.  Closing it as won't fixed!


Github issues triaging

What
Review our current github issues triaging workflow so that we can continuously Iterate over reports and feature requests and identify what needs to be investigated and what can be closed. i.e. no longer relevant, no value, already fixed, already implemented, etc.
Tasks

[ ] Review triaging bug reports workflow
[ ] Review feature requests triaging workflow

Closing. Please re-open if still relevant.