Storage persistence

Could someone review two methods from the storage API that chrome would like to ship? That is:
navigator.storage.requestPersistent()
navigator.storage.persistentPermission()
/cc @annevk

As a minimal subset of the Storage API, this looks good. A few questions:

these APIs look good, particularly as they don't put any constraints on browsers about UI and actual decisions about storage
would like to see a callout to the TAG finding on Unsanctioned User Tracking and positive user controls so that implementers understand that they need to allow users control over this.
what is the reflection of the persistentPermission() in the Permissions API? If there isn't one, I'd like to see it proposed soon.
the text in the Storage spec around quota is...odd? It doesn't seem to relate in any way to existing Quota drafts and proposes a whole set of box-specialized methods (estimate() and persistentEstimate()) without any sort of explainer or example code to illustrate how they'd work in common scenarios which developers encounter. Which brings us to...
...this spec doesn't have an explainer and a single example which covers almost none of the draft feature capability. This is a red flag.

As Chrome is only interested in requestPersistent() and persistentPermission() for now, the rest of the spec seems out of scope for this request and not controversial, but we'd like to be informed if implementers are considering the rest as it raises many concerns.
/cc @kinu @inexorabletrash @khuey @travisleithead

The ordering of persistentPermission and requestPersistent in https://storage.spec.whatwg.org/#dom-storagemanager-persistentpermission seems slightly odd. What's the rationale for that?
Also, is there a reason not to allow workers to requestPersistent?
/cc @wanderview @bakulf

Workers requesting permissions at all needs to be sorted in general, due to lack of UI surface. (Obviously they could delegate to owning window, etc, but no-one is doing that yet IIRC.) I think I saw some chatter recently about doing this for geolocation.

On Feb 8, 2016, at 2:05 PM, Kyle Huey<EMAIL_ADDRESS>wrote:
The ordering of persistentPermission and requestPersistent in https://storage.spec.whatwg.org/#dom-storagemanager-persistentpermission seems slightly odd. What's the rationale for that?
Also, is there a reason not to allow workers to requestPersistent?
/cc @wanderview @bakulf
—
Reply to this email directly or view it on GitHub.

Right. If the expectation is that we will change in the future, I am satisfied.

If you could file issues at https://github.com/whatwg/storage/issues that would help. Happy to change things.

Filed.

Thanks.

And addressed.

discussed at stockholm f2f and agreed to close


Community/Knausj conflicts

The problem
We have at least the following conflicts with stock knausj:

Uses of "that", eg "copy that", "paste that", "phones that", "indent that" etc
Uses of "line", eg "copy line", "clear line", etc, although these commands have roughly the same behaviour in knausj
"copy <number>" targets line number in knausj, but mark in Cursorless
"phones made", "phones whale", etc, where our "phones <target>" conflicts with knausj's "phones <homophone>"
"comment <number>" in community refers to line numbers not the decorated digit

Possible solutions

Change commands in cursorless
Change commands in knausj
Convert these commands to use an action, and redefine the action from cursorless

cc/ @AndreasArvidsson @knausj85 have I missed any conflicts?
Discussed in https://github.com/pokey/cursorless-vscode/discussions/314

Originally posted by codecat555 November  6, 2021
Loving cursorless!
I just ran into a knausj_talon compatibility issue with cursorless, and @pokey invited me to share it here. I'd be interested in hearing about any other tweaks people have made to avoid conflicts.
Cursorless placed an uncolored marker above the number 8 in my text and I wanted to clear that word, so I said 'clear 8'. Then, vscode jumped to line 8 (not the target line) and erased it - not what I expected.
I found this command and just changed it so the '[line]' part is not optional - https://github.com/knausj85/knausj_talon/blob/65ccd94b8fe97056a34b858b2f1f261cc5269c3f/text/line_commands.talon#L16 .

@codecat555 fwiw we fixed the specific issue you raised by changing the default term for "clear" to "change", but that's certainly not the only knausj conflict, so let's leave this discussion open.

I'm finding this type of thing increasingly jarring now that I'm using cursorless in neovim because the cursorless commands (at least for now) don't work or manipulating text on the actual command line, just whatever is in the rest of the buffer. But I'm constantly trying to use the same cursorless terminology there especially chuck, paint, token, etc.
I recall andreas maybe has an existing fallback mechanism so that if a command doesn't actually do anything on cursorless side it falls back to an action? seems like this in combination with proposed solution 3 would solve a lot of these problems? I'm not sure what the status of doing something in community is, or maybe it already exists and I missed it.
I'll probably start slowly poking at solving this on my repo/community, but wanted to see what the state of things is already.

The fallback mechanism is already in Cursorless proper. You(The neovim  implementation) just need to provide the command server interface which gives Cursorless the focused element type.
https://github.com/cursorless-dev/cursorless/blob/14291901a8d3a778e2dee47f2648fae4a69de068/packages/common/src/types/CommandServerApi.ts#L12
https://github.com/cursorless-dev/cursorless/blob/14291901a8d3a778e2dee47f2648fae4a69de068/cursorless-talon/src/fallback.py


Tuple support

Changes to support 0.18

Thanks! I don't know what happened, but I already had those changes. I thought I pushed them, but no. I think I did git push --tags but didn't push the branch itself, or something like that.

That fixed my issue.  Thanks!


docker-slim: init at 1.26.1

This PR is a replacement for #75564.
Besides fixing some issues, which occur due to building inside the nix build
environment, I also added a patch to fix path/casing-related issues until
docker-slim/docker-slim#121 is merged and a new version
is released.

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

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

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

Notify maintainers
cc @

@GrahamcOfBorg build docker-slim

You should probably add @filalex77 to the commit message. https://help.github.com/en/github/committing-changes-to-your-project/creating-a-commit-with-multiple-authors

@kalbasit Is this also to be applied although this patch was neither co-authored nor based on the other PR? I have no problem about giving credit if applicable, but wouldn't this express facts that are not true?

/cc @marsam @Ma27 as you reviewed the other PR before.

@mbrgm I managed to build it with custom preBuild phase on top of @filalex77's PR https://github.com/marsam/nixpkgs/blob/e6710f5c272a10894d73643a82acd634807dea75/pkgs/tools/misc/docker-slim/default.nix.
Do you mind integrating my changes or do you prefer it if I add them to @filalex77's PR?

@marsam I like your version better than mine, given you don't apply any patches. You'd still need to wrap the executable on installation; otherwise, docker-slim will try to create its state directory besides the binary (which will be in nix store). I'm going to integrate all of our changes in this PR. This should then also clarify the authorship question :D.

Ok, this should now have everything important in it. Incorporated @marsam's changes, set him and @filalex77 as co-author.

I have just seen this by browsing nixpkgs. The purpose of pkgs/build-support is to hold functions that are used to build other things, but docker-slim itself is just a derivation. Can you move it somewhere else like pkgs/applications/virtualization/docker-slim?

@zimbatm sorry about that, fixed in https://github.com/NixOS/nixpkgs/pull/80078


Fix argument count in deprecated this.mql.addListener()

This PR partially reverts an unreleased change from https://github.com/alphagov/govuk-frontend/commit/0663ab3373736943e1b29fcf95473205ec382d17#diff-bcd43b95b8acddb0071fa9f557046160278bb06b55b12a58bf76b6c0a2bbb17aR57
Browser testing in Safari 9.1 correctly spotted some recent MediaQueryList argument changes:
var mql = window.matchMedia('(min-width: 48.0625em)')

mql.addEventListener('change', handler)
mql.addListener(handler) // Legacy IE and Safari

See related change in:

https://github.com/alphagov/govuk-design-system/pull/2704


Capacitors are lost when resetting devices in crafting

Issue description:
Capacitors are permanently lost when resetting a device in a crafting window. This could be solved by giving the player the capacitor back when resetting a device in a crafting window.
However, this might be a non-issue, as the player should probably remember to take the capacitor out before resetting a device. Whether this is something that needs to be fixed is up to you.
Steps to reproduce:

Create an Ender IO device, such as an alloy smelter.
Provide it with a capacitor.
Break it, either by mining it or using the yeta wrench.
Put it in a crafting window, either in your inventory or a crafting table, with nothing else.
The capacitor is lost.

Affected versions

Ender IO: 5.0.40
EnderCore: 0.5.45
Minecraft: 1.12.2
Forge: <IP_ADDRESS>81
SpongeForge: No
OptiFine: Yes
Single-player or server: Server

Kinda intended.. capacitor data is stored in nbt and crafting it in the crafting grid is intended to remove nbt.

I guess so. It would be nice if the mod detected that the machine has a capacitor in it and gives it to you when you reset the NBT data, but I’m not expecting this to be implemented. Besides, most people will probably remember to remove the capacitor anyway (not me, though 🤷♂).

Clearing a machine does exactly what it's supposed to do: it clears the machine and resets it completely.
Sent from my iPhone

On 1. Apr 2019, at 15:48, Dimentive<EMAIL_ADDRESS>wrote:
Warning: This message has had one or more attachments removed
Warning: (msg-24420-4.html).
Warning: Please read the "j-e-b-Attachment-Warning.txt" attachment(s) for more information.
I guess so. It would be nice if the mod detected that the machine has a capacitor in it and gives it to you when you reset the NBT data, but I’m not expecting this to be implemented. Besides, most people will probably remember to remove the capacitor anyway (not me, though 🤷♂).
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/SleepyTrousers/EnderIO/issues/5092#issuecomment-478586729
This is a message from the MailScanner E-Mail Virus Protection Service
The original e-mail message contained potentially dangerous content,
which has been removed for your safety.
The content is dangerous as it is often used to spread viruses or to gain
personal or confidential information from you, such as passwords or credit
card numbers.
Due to limitations placed on us by the Regulation of Investigatory Powers
Act 2000, we were unable to keep a copy of the original attachment.
The content filters found this:
MailScanner: Found a script in HTML message
--
Postmaster
MailScanner thanks transtec Computers for their support


Quickswap bottle y pressed

This is the simple version of not cycling through bottles with quickswap. It replaces the functionality of cycling through all the bottles with double-shoulder "Y presses".
I had originally added a check in ProcessBottleMenu to bypass the Y check, but it turns out that check doesn't seem to be necessary because the calling subroutine is already checking if Y is pressed so instead both items are commented out. This made the double-shoulder press for bottle as smooth as the one for shovel/flute.
It would also be possible to do a more complex version where the flag variable ( 0x30804B ) could be either:

0x00 == off
0x01 == old behavior
0x02 == new behavior

That would take front-end work that i'm not necessarily willing to do.

Hi, thanks for this PR!


Particle tracker

New module for tracking particles in datasets where particles can be followed.
command line useage:
silcam-track process   [--offset=]
silcam-track post-process
silcam-track plotting  [--gif=] [] [--boxplot]

use branch: dev-tracker instead


Background mode

Port forwarding works perfectly - all that's missing is a background mode to connect to the virtual machine through a good SSH client and test results on Safari.

Duplicate of #243
Please search before making a new ticket.


Splits imports between React and React Native to fix warnings in RN 0.25

Also fixes #9 because the scrollTo API changed with React-native 0.25

Thank you for your work!
Does the scrollTo modification mean RN version must >= 0.25 now?

Yes, that's the problem with this...


Client never finishes "Establishing tor circuit" on Windows 10 64bit system

After creating a new wallet (no password - left blank), I followed the directions in the readme to step 5 (wait for the headers to syncronize and my client remains more or less frozen as seen in the screenshot below.

Occasionally, the bottom notification box goes red and seems to lose connection, though after restarting the client, I am having trouble reproducing this issue.
However, the client is still not synchronizing. Each time I have tried to leave it sitting for over an hour.

@auldsyababua I see on your screenshot you are on the mainnet. Did you change that?

Occasionally, the bottom notification box goes red and seems to lose connection

When that happens HiddenWallet restarts Tor.

However, the client is still not synchronizing. Each time I have tried to leave it sitting for over an hour.

That's not expected (except if you have very bad internet). What does the status bar say?

Ah, then that may be a UI issue as I thought that was a check mark box with regard to being on mainnet (my reasoning was: no check - not on mainnet). I never saw a testnet button as shown in the screenshots in the set up guide.
Will get back to you about what status bar says

I see. Anyway this pull request will clear up this misunderstanding.

I have tried it by switching to testnet as instructed yet issue persists.

After about 4 hours, the wallet is finally syncing the headers.

I'm having the same issue on OSX too

Could you guys just simply run Tor in itself? This error came for someone with corrupted config file (syntax error in torrc)

Yup, tor works fine. And previously, the wallet worked fine for me, I participated in the testnet mixing. However, now I'm having this issue.

There is a new version of the wallet, called Wallet Wasabi, that's a complete reimplementation of the wallet. This part of the codebase will not be reused.


Map batch API

Close: https://github.com/aquasecurity/libbpfgo/issues/162
commit 9382e51652377376ef9459901c49abbcf39758b3 (HEAD -> map-batch, origin/map-batch)
fix(map)!: fix map batch methods

This breaks the API, returning a count of the number of elements
processed for each batch method.

It also fixes the check against ENOENT and E2BIG.

The selftest has been updated to reflect the new API.

@rafaeldtinoco I got the other refactors in (were getting dust), but this breaks API.

@rafaeldtinoco @geyslan We would love to be able to use batch APIs downstream @parca-dev.
How could we be helpful to push this thorough?
cc @javierhonduco

Hey @kakkoyun and @javierhonduco. We would love to get your review on this PR.

Sure thing! 👍

Sorry for the delay on this. Going to merge as it is, any required changes are welcome.


feat-logger-update

Fixes #1153

[x] separate log file for cortex.log and cortex-cli.log
[x] pruning log file only to save last 100,000 lines. The log file will be truncated if number of  line > max_lines.
[x] configurable log file location. save the config in the ~/.cortexrc

logFolderPath: C:\Users\jan\cortexcpp
dataFolderPath: C:\Users\jan\cortexcpp
host: <IP_ADDRESS>
port: 3928

@nguyenhoangthuan99 Please link this PR to issue via keyword

@nguyenhoangthuan99 A few questions:

Do we have a filesize estimate of how much space 100,000 log lines will equate to?
Should we make log lines pruning a variable in .cortexrc that users can configure?

I imagine cortex.cpp may have some embedded use-cases in the future, where devs may have diskspace constraints for logs (difficult for me to imagine now with >1gb model sizes, but this may change in the future)

Hi @dan-homebrew , Average each line will contains < 300 characters , each character is 1 byte. So 100,000 lines will be 300100,000/(10241024) ~ 30Mb

Hi @dan-homebrew , Average each line will contains < 300 characters , each character is 1 byte. So 100,000 lines will be 300 * 100,000/(1024*1024) ~ 30Mb

This looks good to me - let's include it as a default param in .cortexrc

Great job!


fix(executor): Do not delete local artifacts after upload. Fixes #4676

Signed-off-by: Alex Collins<EMAIL_ADDRESS>Checklist:

[x] My organization is added to USERS.md.

Left in draft pending testing by @antoniomo .

LGTM, thank you! Test results on the issue, here: https://github.com/argoproj/argo/issues/4676#issuecomment-743777218


make online demo scream DEMO

from Mike in email

Let's maintain a separate branch meant for deploying to the online demo.

:+1:


Optical flow rescaling

I want to use I3D for feature extraction purpose. After tvl1 flow calculation the range of optical flow is not in [-20,20] in lots of video in the dataset being used. Can I rescale optical flow between [-1,1] directly without truncating to [-20,20]?

@S-I-P What was your decision on this? I'm thinking about the same issue.

@S-I-P What was your decision on this? I'm thinking about the same issue.

Sorry for late reply. I mailed the author about this issue. Quoting his answer, "regarding the optical flow question i don't have a great answer, i'd suggest trying still clamping to [-20, 20] as that's what the model was trained on."

Thanks for your reply. I stuck with[-20,20] range as well. My current issue is the optical flow algorithm. The models seems to be training on TVL1,  but as it is very slow I wanted to use one of GPU enabled optical flows like farnerback which are much faster. With another algorithm, however I cannot get it to learn anything, i get absurd value.
So it seems to be quite sensitive to optical flow algorithm and I can't seem to retrain it from one to another.

No I only used opencv-python TVL1 optical flow calculation. If you want to use gpu for tvl1 flow, you could try https://github.com/google/mediapipe (the preprocessing libraries used for the kinetics dataset) or https://docs.opencv.org/3.4.9/d6/d39/classcv_1_1cuda_1_1OpticalFlowDual__TVL1.html#details

Thanks. I'll check out mediapipe. I've tried OpenCV's cuda enabled TVL1 and even that is significantly slower than farnerback.
I'm doing image augmentation + optical flow on the go during training and it's just too slow.


What would a concurrent Process do here --quoted text below?

"The declaration of w specifies that the program cannot change the value pointed to and that the program cannot modify the pointer."

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: e5a55527-20e0-3841-e3e3-e7250af5f088
Version Independent ID: dde4872e-68b2-7959-9041-3cef6066bad6
Content: Pointer Declarations
Content Source: docs/c-language/pointer-declarations.md
Product: visual-cpp
GitHub Login: @mikeblome
Microsoft Alias: mblome

@b1nch3f The wording here is accurate but not super clear. Think of a memory location that one process or thread can write to and another can only read from.  The first process might have access to that address by a non-const variable or pointer declaration. The second process has a variable that points to the same location, but cannot modify it due to "const" and also cannot assume the value is unchanged; "volatile" is used to tell the compiler that it read the value at that location every time it is used.


etcd-cpp-apiv3 with TLS and certs

I am trying to find an equivalent way of accessing etcd server which has TLS and certs configured:
In case ETCD is configured with TLS certificates support:

ETCDCTL_API=3 etcdctl --endpoints <etcd_ip>:2379 --cacert <ca_cert_path> --cert <cert_path> --key <cert_key_path> get / --prefix --keys-only

I could find the info related to auth with user/password.
Can anyone suggest the equivalent API/function in etcd-cpp-apiv3?

Hi @ashish-billore,
Authenticate using cartificates is not supported yet. Currently only user/password has been implementation.
That will be done in the next one or two month, but no promise.

Thanks for the info, I'll await this feature eagerly.
This is one of the requirement for our current usage.
Thanks!

Thanks for the info, I'll await this feature eagerly.
This is one of the requirement for our current usage.
Thanks!

Hi @ashish-billore TLS and certs support have been added in #42, please refer to README for how to use that feature.


anatomy:0.1.0

I am submitting

[x] a new package
[ ] an update for a package

Description: A package to visualise the metrics information (horizontal lines) of a font. Useful if user wants to confirm the position of top-edge and bottom-edge when calling text().

I have read and followed the submission guidelines and, in particular, I

[x] selected a name that isn't the most obvious or canonical name for what the package does
[x] added a typst.toml file with all required keys
[x] added a README.md with documentation for my package
[x] have chosen a license and added a LICENSE file or linked one in my README.md
[x] tested my package locally on my system and it worked
[x] excluded PDFs or README images, if any, but not the LICENSE

Thanks!


Investigate why --nothreading is required for Django debugging

Why do we disable threading in the debug configuration for django?
                    {
                        "name": "Python: Django",
                        "type": "python",
                        "request": "launch",
                        "program": "${workspaceFolder}/manage.py",
                        "console": "integratedTerminal",
                        "args": [
                            "runserver",
                            "--noreload",
                            "--nothreading"
                        ],
                        "django": true
                    },

#1874 suggests we don't want it. Microsoft/vscode-docs#1764 will also need updating if it turns out we don't want that setting.

I can't debug Django without --nothreading so it still seems to be needed.

I think we need to understand why it fails and if there's a bug in ptvsd, then we need to look into this.

Closing in favour of https://github.com/Microsoft/ptvsd/issues/1256


Trying to get the events

Will something like work? It returns nothing.
$event =  $contract->at($myContract)->getEvents("Transfer",function ($err, $data) use(&$results) {
    if($err) {
        echo 'error: ' . $err->getMessage() . "<br>";
    } else {
        $results = $data;
    }
});
echo "\$results = $data";

It's ok, I'm using this contract.php: https://github.com/Nanolucas/web3.php/blob/master/src/Contract.php
Although it works great, I did change:
if ($fromBlock !== 'latest') {
           if (!is_int($fromBlock) || $fromBlock < 1) {

to this:
if ($fromBlock !== 'latest') {
           if (!is_int($fromBlock)) {

because you may want to get the list of all your events from beginning, which is 0
Thanks @Nanolucas for the code!


Add mypy

add mypy
split general JSON and flattened JSON

@Viicos I've merged it at first. You can left comments on the PR.


Build Static HTML

If I have a bunch of Julia files that generate HTML strings and are served properly via Oxygen.jl serve() in the browser, how can I build these as static HTML files? For example, I have these files in my src/routes folder and I want to build them and then host them via GitHub pages as .html files

Hi @Dale-Black,
Sorry about the slow turn around, you should be able to host those static files by doing something like the following:
using Oxygen

# Step 1: build the static files
build_html_files()

# Step 2: mount all files inside the "src/routes" folder under the "/static" path
staticfiles("src/routes", "static")

# Step 3: start the web server
serve()

I guess the part I am confused about is the actual build_html_files() portion. Does Oxygen.jl provide this out of the box? If not, how could I go about something like that?

Hi @Dale-Black,
Could you tell me more about your workflow? Based on your initial comment,  If you have a bunch of files that generate html strings, just save them to a directory and mount the directory like in my previous example.
Oxygen doesn't include any helper functions to physically generate or save html at the moment. Granted, I do have some changes in the works to support templating. But if you want to physically generate HTML from code I'd recommend Hyperscript.jl or Cobweb.jl to do so.


many people killed by american army. the world not need american . armrcian have been destoired many people home, Libya 、Afghanistan 、Iraq。
In 2003, during a presentation to the UN Security Council, Powell laid out US version of the "evidence" that Iraq possessed weapons of mass destruction, which later turned out to be nonexistent. Even in the US, this presentation was controversial. Many wonder why the US resorted to such an inferior means to try to persuade the UN to back its military action against Iraq.

The United States has been involved in an armed conflict with al-Qaeda and affiliated groups in Yemen arguably since the October 2000 bombing of the USS Cole off the coast of Yemen, at the time one of al-Qaeda’s most significant attacks. However, Yemen did not become a first tier front in the U.S. counterterrorism campaign until 2009. In the intervening years, al-Qaeda elements in Yemen and Saudi Arabia united under seasoned leadership that had trained with Osama bin Laden to form al-Qaeda in the Arabian Peninsula (AQAP). On Christmas Day 2009, the group supplied Umar Farouk Abdulmutallab with an ingeniously designed explosive device concealed in his underwear in an attempt to bring down an airliner en route to Detroit, Michigan. The device malfunctioned and the crisis was averted, but the U.S. government sprang into action, launching a military campaign against AQAP in Yemen that continues to this day.


Could you provide the video_ids trained/tested from AudioSet-instrument?

Hi,
I found there are totally 116,405 unbalanced train videos for Musical instrument videos on AudioSet, which is much more than the amount of clips you mentioned in your paper. So, can you provide the video ids for those video for traning and testing in the experiment? Many thanks!

Hi,
We have uploaded the video id in  audioset-instrument/data/PartitionForAudioset.zip.
Best,
Di


API endpoint for creating and registering hubs

I would like to create hubs for people. It cannot be done in the app because if I ask for $ it breaks apple and google app policies. So it must be done somewhere else. I think just postman for now.
The API call will need.

user who owns node
admin token
node subdomain (off koto.ar)
(optional) notes (code of conduct field)
(optional) type - could be used later
(optional) transaction reference - could be a payment gateway number or bitcoin transaction number

When the call is made (by admin, with admin token) a message hub will be added as follows:
Create Hub

digital ocean api will be called (needs api token)
A record created for subdomain
new digital ocean s3 bucket
deployment YAML with subdomain s3
deployment YAML will include new db schema (I think maybe we use the same pg instance?)
kubectl deploy the new message hub
register and approve the hub automatically

We should also create API endpoints for
Delete hub

send subdomain as key
Deletes db
removes A record
deletes kubernetes deployment
unregisters / deletes message hub from koto

@falconandy here's one for you 😎

Domains
The Digital Ocean API for domain records is here:
https://developers.digitalocean.com/documentation/v2/#domain-records
You can see how to create an A record:
curl -X POST -H "Content-Type: application/json" -H "Authorization: Bearer b7d03a6947b217efb6f3ec3bd3504582" -d '{"type":"A","name":"mhub1234","data":"<IP_ADDRESS>","priority":null,"port":null,"ttl":1800,"weight":null,"flags":null,"tag":null}' "https://api.digitalocean.com/v2/domains/example.com/records"

Spaces (s3 buckets)
You can create / delete spaces using the normal S3 API and targeting https://ams3.digitaloceanspaces.com with a secret and key.
Deploying message hubs
You can deploy a new message hub by issuing 'kubectl apply -f message-hub.yaml' using this file:
https://github.com/mreider/koto/blob/master/.k8s/backend/message-hub.yaml
You will have to change the YAML settings to make it a unique message hub.
Deploying databases
I am thinking all message hubs should use the same postgres instance. Otherwise we'll be using much more memory / CPU than needed. I am not sure what is better - to create separate databases or separate schemas?
We could also pull the postgres databases off of the Kubernetes install and move to managed Postgres.

@falconandy I am going to start making this visual now.

@mreider API is ready but hub database isn't dropped (it seems, there are open connections to the database) - there is a new "force" option for "drop database" statement but it is available for Postgres 13 only (https://www.enterprisedb.com/postgres-tutorials/postgresql-13-new-feature-drop-database-forcefully)

Create:
POST https://central.orbits.at/rpc.MessageHubService/Create
Content-Type: application/json

{
  "owner": "USERNAME",
  "subdomain": "SUBDOMAIN"
}

Remove:
POST https://central.orbits.at/rpc.MessageHubService/Remove
Content-Type: application/json

{
  "subdomain": "SUBDOMAIN"
}


Add solution to rod cutting problem

What does the program do ?
It's solution to the famous rod cutting problem.

In what programming language it is written?
C++

Thank you for participating  in hacktoberfest ❣ if you liked working on this repo you can share it with friends and star this project for helping others


Go outside from inside private node

Hello again, the floating public ip address works properly from outside i can access private node, but when i try to reach internet or pinging <IP_ADDRESS> from inside private node it doesn't work.

hi, that is not an issue from ipfloater. The access to the network must be provided by means of nat or other mechanisms. A VM will not have knowledge about the existence of the public IP address. The traffic from the public IP address is redirected to the private IP address.

Hi, i'm sorry i'm not very familiar with github that's why i opened issue instead of question.
so how can i share internet with the VM, plus i want to get the attached public ip when calling $ curl 'https://api.ipify.org?format=json' for example, is that possible ? thank you

No, you can't use such services, because the IP does not belong to the VM. You'll get the IP address from your NAT service.


Test: Capture a single photo out of a channel

Make a console app that captures a single photo from a real NVR into a file.

Fixed in aab817ef79ed1c2cf57130c5904b5f6aeda0b730


Notify users of an update on the client

We already do this on the console

Add to the UI status bar as well

Done.


Always build static binaries

After seeing this forum thread I felt like it was important to move to static linkage for the Windows runtime (and avoid DLL hell).
As of June 2024, JUCE Projucer and CMake both default to dynamic linkage for the microsoft runtime. The reasoning is historical: https://forum.juce.com/t/important-breaking-change-juce-will-now-use-dynamic-linking-for-the-windows-runtime-by-default/25276
The FLS Slots issue was resolved in 2019, but the JUCE default was never updated again:
https://blogs.windows.com/windows-insider/2019/01/09/announcing-windows-10-insider-preview-build-18312/
To do dynamic linking right, one has to get every customer to install the latest runtime to ensure your executable will run. Games tend to do this, the UX is pretty unergonomic and awful. I believe you have to actually spawn the second installer for the runtime.
Although static linking creates a bit more duplication and binary bloat, it avoids DLL hell. It's the default for many devs I know, including open source repositories like Surge, so this should be the Pamplejuce (and IMO JUCE) default.

Pre static-linking branch:
C:\Program Files\Microsoft Visual Studio\2022\Community>dumpbin /dependents "C:\Program Files\Pamplejuce Company\Pamplejuce Demo\Pamplejuce Demo.exe"
Microsoft (R) COFF/PE Dumper Version 14.40.33811.0
Copyright (C) Microsoft Corporation.  All rights reserved.

Dump of file C:\Program Files\Pamplejuce Company\Pamplejuce Demo\Pamplejuce Demo.exe

File Type: EXECUTABLE IMAGE

  Image has the following dependencies:

    KERNEL32.dll
    USER32.dll
    GDI32.dll
    SHELL32.dll
    ole32.dll
    OLEAUT32.dll
    COMDLG32.dll
    MSVCP140.dll
    SHLWAPI.dll
    WINMM.dll
    d2d1.dll
    dxgi.dll
    d3d11.dll
    dcomp.dll
    IMM32.dll
    VCRUNTIME140.dll
    VCRUNTIME140_1.dll
    api-ms-win-crt-runtime-l1-1-0.dll
    api-ms-win-crt-heap-l1-1-0.dll
    api-ms-win-crt-math-l1-1-0.dll
    api-ms-win-crt-time-l1-1-0.dll
    api-ms-win-crt-string-l1-1-0.dll
    api-ms-win-crt-stdio-l1-1-0.dll
    api-ms-win-crt-convert-l1-1-0.dll
    api-ms-win-crt-locale-l1-1-0.dll
    api-ms-win-crt-environment-l1-1-0.dll
    api-ms-win-crt-utility-l1-1-0.dll

On the static-linking branch:
C:\Program Files\Microsoft Visual Studio\2022\Community>dumpbin /dependents "C:\Program Files\Pamplejuce Company\Pamplejuce Demo\Pamplejuce Demo.exe"
Microsoft (R) COFF/PE Dumper Version 14.40.33811.0
Copyright (C) Microsoft Corporation.  All rights reserved.

Dump of file C:\Program Files\Pamplejuce Company\Pamplejuce Demo\Pamplejuce Demo.exe

File Type: EXECUTABLE IMAGE

  Image has the following dependencies:

    KERNEL32.dll
    USER32.dll
    GDI32.dll
    SHELL32.dll
    ole32.dll
    OLEAUT32.dll
    COMDLG32.dll
    SHLWAPI.dll
    WINMM.dll
    d2d1.dll
    dxgi.dll
    d3d11.dll
    dcomp.dll
    IMM32.dll


fix doc bug for referencing old version docstring

will be able to generate reference from the right docstring.

I have tested this modification, the reference will automatically be modified with the modification of the source docstring.


Show closed tickets

Display closed tickets to staff users.

 Cannot view closed tickets in dashboard unless you are assigned to them.


Matlab interface

A Matlab interface similar to the Python interface could be useful to Matlab developers.
Potential users:

Control engineers who develop controllers in Matlab
Mechanical engineers who have a limited programming experience besides Matlab

I have a question related to this issue:
There seems to be an ongoing effort to provide Matlab support in swig. Did you give any thought to using swig for the python interface generation?

Hello,
Yes indeed. I lightly benchmarked several python interface systems in terms of ease of use and efficiency. Boost seemed to be the best option.
The binding of eigen and mummy is indeed quite tricky. I would be a priori very reluctant to spend time doing it a second time.
On the other hand, matlab interfaces are very light to implement. Do you really thing that swing would help, if not for capitalising on the python bindings?
N
Le 16 oct. 2015 19:14, Antonio El Khoury<EMAIL_ADDRESS>a écrit :I have a question related to this issue:
There seems to be an ongoing effort to provide Matlab support in swig. Did you give any thought to using swig for the python interface generation?
—Reply to this email directly or view it on GitHub.

A couple of questions:

What is mummy?
Is Eigen memory alignment the only tricky part or did you encounter other problems?

I am neither familiar with matlab interfaces nor with swig (at least not yet), and I am quite happy with the current state of the python bindings. So I would give swig a try only if it would make writing matlab interfaces faster than doing a raw binding (through mexFunction I guess).

One quick answer: mummy is in fact numpy.

Mummy is indeed the best my phone could propose to correct Numpy, as already corrected by Justin. Sorry for the typo.
The tricky part in boost::python was the memory alignment (or more exactly, the memory allocation of Eigen memory by boost::python, that does not respect Eigen alignment). The tricky part in general is to bind Eigen data in C with Numpy data in Python. It would be more straightforward to wrap Eigen data in Python. Wrapping is for example what is done for Pinocchio::Model or Pinocchio::Force classes: you are not using a Python object to make the equivalence with the C object, but directly manipulating the C object in Python.
I think binding Eigen with Numpy provides better functionalities in the end, however is more difficult to implement. For what I benchmarked initially, it seems equality tricky with the various Python wrapping/binding frameworks.
Again in my opinion, wrapping is much easier in Matlab, because Matlab is not strongly typed. Programming the matlab bindings could be done with much effort with the native MEX system of Matlab.

Thanks for the clarification, I will give the matlab MEX a try.

Have you implemented any Matlab interface? If not, are you still interested by such feature?

Sadly I haven't had the time to implement anything, but we are still clearly interested in such a feature.

I would like to add a comment to this discussion line. Indeed it's very tricky to bind Eigen data with Numpy. During the period at IIT, I used SWIG to bind Eigen data. Basically you need to write an interface file, this file can be re-used for any project. Here you find the file:
https://github.com/robot-locomotion/dwl/blob/master/swig/eigen.i

If anyone ever needs that, a possible strategy to test is to use the Pinocchio Python bindings in MATLAB. Recent version of MATLAB have quite advanced Python interoperability features, see https://www.mathworks.com/help/matlab/call-python-libraries.html, https://github.com/dic-iit/bipedal-locomotion-framework/issues/53#issuecomment-789058776 and https://github.com/robotology/robotology-superbuild/issues/760 .

Fantastic. I didn't know that.
We may give it a try once. @proyan Would you may give it a try?
@traversaro What is your feedback on it?

@traversaro What is your feedback on it?

We only tried it for some examples for now (see https://github.com/dic-iit/bipedal-locomotion-framework/issues/53#issuecomment-789058776) but it seems quite promising, but to be honest we never had any serious use of it (like, a student that did all the computation for a paper/thesis in it). To quickly test it, if you have access a possible option is to install pinocchio via conda in MATLAB Online. We have a simple script in https://github.com/robotology/robotology-superbuild/blob/0f82a33dca1fe46111945e09382df26e39c0efb5/doc/matlab-one-line-install.md#installation-on-matlab-online for installing conda packages in MATLAB Online with a few commands.
To use the script with Python Pinocchio bindings, probably it would be sufficient to:

the script should be modified around https://github.com/robotology/robotology-superbuild/blob/d94d8ca32e5b1e446ad9ec835565e315cceb7bac/scripts/install_robotology_packages.m#L68 to  install pinocchio via conda forge instead of the robotology packages
the selection of the python interpreter of conda should be added to the activation script around https://github.com/robotology/robotology-superbuild/blob/d94d8ca32e5b1e446ad9ec835565e315cceb7bac/scripts/install_robotology_packages.m#L72 , adding a line such as pyversion(fullfile(robotology_install_prefix,'/bin/python3')) or something similar.


Add conflict resolution / additional auth types to stack outputs

Description of changes
This PR adds values to optional awsAppsyncConflictResolutionMode and awsAppsyncAdditionalAuthenticationTypes to cfn stack outputs when they're available.
CDK / CloudFormation Parameters Changed
Outputs added:

awsAppsyncConflictResolutionMode
awsAppsyncAdditionalAuthenticationTypes

Issue #, if available
Associated PR: https://github.com/aws-amplify/samsara-cli/pull/355
Description of how you validated changes

Ran tests

Checklist

[x] PR description included
[x] yarn test passes
[x] Tests are changed or added
[x] Any CDK or CloudFormation parameter changes are called out explicitly

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Pending completion of E2E Tests https://us-east-1.console.aws.amazon.com/codesuite/codebuild/594813022831/projects/amplify-category-api-e2e-workflow/batch/amplify-category-api-e2e-workflow%3A78f2448d-843e-44cc-9391-defd31d7e5b1?region=us-east-1

There seem to be some issues w/ the ESModules again (which Ed had worked around), John and I will look into what might be causing that.


Autojoin everybody into #newbie by default, opt-out via settings.

The problem is that most longtime players probably dont even know that newbie chat exists, even if they would be willing to help out. We should make helping noobs one of the major reasons for why the chat exists, and therefore we should join everybody into it by default.
So basically add it to the auto-join options. People can remove it from there if they dont want to join it always.
Edit: We should also sync the #newbie channel to discord.

Not planned


Error on W3 script "w3-include-html"

Hi, sometimes I use a script from w3 when building a layout.
I was surprised that it is not validating.
Do you have any ideas?
Screenshot
Source script w3-include-html

Hi @mrakcw  ,your file is not validating because you are using the html attribute w3-include-html that does not exist.
More infos that may help you here :
https://stackoverflow.com/questions/50598507/w3-include-html-causing-error-in-validation-from-https-validator-w3-org
Also W3School is not affiliated with the W3C, so i guess sometimes they does not respect all this little tricky rules set by the W3C organization.
Thank you for using my extension, tell me if you need any more informations or help 😄


creation of 2 records with same DOI

Package version (if known): April
Not 100% sure if this is "expected": it seems to be possible to create a record, get its DOI and paste it in the DOI field for a new record and create that record. Will need double-checking (from a report).
Steps to Reproduce

Go to 'uploads/new'
Fill and publish
Copy generated DOI
Go to 'uploads/new'
Pass copied DOI into the "already have a DOI for this record field"
publish no problem

Expected behavior
Emit error about duplicate DOI (unless this is indeed fine)

It is "expected"/known issue because the deduplication was not merged last month... closing this since is duplicated and there is a PR https://github.com/inveniosoftware/invenio-rdm-records/pull/592


Use clang for target android

android ndk r18 remove gnu support, we should use clang instead of gcc

Thanks for the PR! In order to keep supporting older SDKs though (which rust-lang/rust may be using?) could this default to using clang but use gcc as a fallback if it's not detected?

I've updated my commit.
It will check for gnu first as it always has done

Thanks! Could the rustfmt changes be left for a later time as well? Additionally, could the logic of replacing strings in the target be deduplicated between the gcc/clang case?

Ok sorry for fmt, I used git add -u because of time :/
Thank you for seeing the duplication, everything should be right now

Thanks!


Cannot compile to arm devices

Version
├── ethers v2.0.7
│   ├── ethers-addressbook v2.0.7
│   │   ├── ethers-core v2.0.7
│   ├── ethers-contract v2.0.7
│   │   ├── ethers-contract-abigen v2.0.7
│   │   │   ├── ethers-core v2.0.7 ()
│   │   ├── ethers-contract-derive v2.0.7 (proc-macro)
│   │   │   ├── ethers-contract-abigen v2.0.7
│   │   │   │   ├── ethers-core v2.0.7
│   │   │   ├── ethers-core v2.0.7 ()
│   │   ├── ethers-core v2.0.7 ()
│   │   ├── ethers-providers v2.0.7
│   │   │   ├── ethers-core v2.0.7 ()
│   ├── ethers-core v2.0.7 ()
│   ├── ethers-etherscan v2.0.7
│   │   ├── ethers-core v2.0.7 ()
│   ├── ethers-middleware v2.0.7
│   │   ├── ethers-contract v2.0.7 ()
│   │   ├── ethers-core v2.0.7 ()
│   │   ├── ethers-etherscan v2.0.7 ()
│   │   ├── ethers-providers v2.0.7 ()
│   │   ├── ethers-signers v2.0.7
│   │   │   ├── ethers-core v2.0.7 ()
│   ├── ethers-providers v2.0.7 ()
│   └── ethers-signers v2.0.7 (*)
Platform
5.19.0-45-generic #46~22.04.1-Ubuntu x86
Description
I'm trying to compile a simple rust project with ethers-rs to arm architectures. In particular, the targets I'm using are armeabi-v7a and arm64-v8a (for android and ios). As soon as I installed ethers-rs and I inserted this simple code:
use ethers::prelude::*;
use ethers::providers::{Http, Provider};
use std::convert::TryFrom;

pub async fn get_current_block_number(rpc_url: String) -> u64 {
    let provider = match Provider::<Http>::try_from(rpc_url) {
        Ok(provider) => provider,
        Err(err) => return 0,
    };
    let block_number = match provider.get_block_number().await {
        Ok(block_number) => block_number,
        Err(err) => {
            return 0;
        }
    };
    println!("{block_number}");

    block_number.as_u64()
}

the command cargo ndk -t armeabi-v7a -t arm64-v8a -o ./dist build --release started to failed with the following error:

error: failed to run custom build command for ring v0.16.20
....
In file included from crypto/fipsmodule/aes/aes_nohw.c:15:
In file included from include/GFp/aes.h:52:
In file included from include/GFp/base.h:66:
/usr/bin/../lib/gcc/x86_64-linux-gnu/12/include/stdint.h:9:3: error: #include_next is a language extension [-Werror,-Wgnu-include-next]
# include_next <stdint.h>
^

However without ethers-rs it goes successfully. I'm wondering if it can be possibile to compile it to arm
My goal is to use it with ffi
Did someone have my same experience? Do you know if I'm doing something wrong?
P.s I changed that function to support ffi known type. cargo build runs successfully

The error occurs while running the ring build script. You probably want to check out their building documentation on how to cross compile. Also make sure your NDK version is >=25 since it the minimum has been recently updated.
Other than that, I can't tell you much since I don't have any experience cross compiling to Android or IOS.


install failed

my version are:
torch                         1.10.0
torchaudio                    0.10.0
torchvision                   0.11.0
but this error:
Traceback (most recent call last):
File "tools/test_omni.py", line 11, in
from mmdet.datasets import build_dataset
File "/home/yj/.local/lib/python3.7/site-packages/mmdet/init.py", line 18, in
f'MMCV=={mmcv.version} is used but incompatible. '
AssertionError: MMCV==1.4.6 is used but incompatible. Please install mmcv>=2.0.0rc4, <2.1.0.

The install instructions in https://github.com/MasterBin-IIAU/Unicorn/blob/master/assets/install.md don't specify a mmdet version, so it installs the latest version (I got 3+), which is incompatible with mmcv==1.4.6. Specifying a lower mmdet version (e.g. mmdet==2.25.0) seems to solve this issue.


Fix for: Web - FAB - "New Workspace" option is disabled after deleting Workspace in offline mode

Details

Fixed Issues

$ https://github.com/Expensify/App/issues/11825
PROPOSAL: https://github.com/Expensify/App/issues/11825#issuecomment-1294764577
Tests

Select FAB menu -> Create workspace. Create a workspace.
Disconnect internet.
Select Settings -> Workspace. Delete the workspace.
Verify "New workspace" button exists in FAB menu.
Select FAB menu -> Create workspace. Create a workspace.
Verify "New workspace" button no longer exists in the FAB menu.

[x] Verify that no errors appear in the JS console

QA Steps

Select FAB menu -> Create workspace. Create a workspace.
Disconnect internet.
Select Settings -> Workspace. Delete the workspace.
Verify "New workspace" button exists in FAB menu.
Select FAB menu -> Create workspace. Create a workspace.
Verify "New workspace" button no longer exists in the FAB menu.

[ ] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] iOS / native
[x] Android / native
[x] iOS / Safari
[x] Android / Chrome
[x] MacOS / Chrome
[x] MacOS / Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product was added in all src/languages/* files
[x] I verified any copy / text that was added to the app is correct English and approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] If a new component is created I verified that:

[x] A similar component doesn't exist in the codebase
[x] All props are defined accurately and each prop has a /** comment above it */
[x] The file is named correctly
[x] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[x] The only data being stored in the state is data necessary for rendering and nothing else
[x] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[x] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[x] All JSX used for rendering exists in the render method
[x] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG)

[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] I have checked off every checkbox in the PR author checklist, including those that don't apply to this PR.

PR Reviewer Checklist
The reviewer will copy/paste it into a new comment and complete it after the author checklist is completed

[ ] I have verified the author checklist is complete (all boxes are checked off).
[ ] I verified the correct issue is linked in the ### Fixed Issues section above
[ ] I verified testing steps are clear and they cover the changes made in this PR

[ ] I verified the steps for local testing are in the Tests section
[ ] I verified the steps for Staging and/or Production testing are in the QA steps section
[ ] I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[ ] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)

[ ] I checked that screenshots or videos are included for tests on all platforms
[ ] I included screenshots or videos for tests on all platforms
[ ] I verified tests pass on all platforms & I tested again on:

[ ] iOS / native
[ ] Android / native
[ ] iOS / Safari
[ ] Android / Chrome
[ ] MacOS / Chrome
[ ] MacOS / Desktop

[ ] If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
[ ] I verified proper code patterns were followed (see Reviewing the code)

[ ] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
[ ] I verified that comments were added to code that is not self explanatory
[ ] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[ ] I verified any copy / text shown in the product was added in all src/languages/* files
[ ] I verified any copy / text that was added to the app is correct English and approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[ ] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[ ] I verified the JSDocs style guidelines (in STYLE.md) were followed

[ ] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[ ] I verified that this PR follows the guidelines as stated in the Review Guidelines
[ ] I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
[ ] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[ ] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[ ] If a new component is created I verified that:

[ ] A similar component doesn't exist in the codebase
[ ] All props are defined accurately and each prop has a /** comment above it */
[ ] The file is named correctly
[ ] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[ ] The only data being stored in the state is data necessary for rendering and nothing else
[ ] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[ ] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[ ] All JSX used for rendering exists in the render method
[ ] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[ ] If a new CSS style is added I verified that:

[ ] A similar style doesn't already exist
[ ] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG)

[ ] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[ ] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[ ] I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots

Web

https://user-images.githubusercontent.com/11609254/199439372-52d12a40-8551-40d6-82fb-efab4fff6aae.mp4
Mobile Web - Chrome

https://user-images.githubusercontent.com/11609254/199439429-d678e24c-ca38-41d6-bc31-c51dc22b5951.mp4
Mobile Web - Safari

https://user-images.githubusercontent.com/11609254/199439487-f531c246-604e-4d7a-a256-45ff6770bd4a.mp4
Desktop

https://user-images.githubusercontent.com/11609254/199439563-ef2d31c2-44d0-4571-aa2b-e67ca0a32d75.mp4
iOS

https://user-images.githubusercontent.com/11609254/199439624-6f72e0d0-be71-4787-99cf-52e5d020b2e5.mp4
Android

https://user-images.githubusercontent.com/11609254/199439695-79dea4f7-e4ce-487e-9af0-dccd9504e7e5.mp4

  Screen Recordings
Screenshots

Desktop & Web
https://user-images.githubusercontent.com/85645967/200197031-37a09a49-2568-4650-b674-653ee21af16e.mov
Mobile Web - Chrome & Mobile Web - Safari
https://user-images.githubusercontent.com/85645967/200197801-73609c81-af30-4c60-b104-091431363b8f.mov
iOS & Android
https://user-images.githubusercontent.com/85645967/200197803-acd11807-8680-419f-afd6-e403fc2c3135.mov

PR Reviewer Checklist
The reviewer will copy/paste it into a new comment and complete it after the author checklist is completed

[x] I have verified the author checklist is complete (all boxes are checked off).
[x] I verified the correct issue is linked in the ### Fixed Issues section above
[ ] I verified testing steps are clear and they cover the changes made in this PR

[ ] I verified the steps for local testing are in the Tests section
[ ] I verified the steps for Staging and/or Production testing are in the QA steps section
[ ] I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[ ] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)

[x] I checked that screenshots or videos are included for tests on all platforms
[x] I included screenshots or videos for tests on all platforms
[x] I verified tests pass on all platforms & I tested again on:

[x] iOS / native
[x] Android / native
[x] iOS / Safari
[x] Android / Chrome
[x] MacOS / Chrome
[x] MacOS / Desktop

[x] If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
[x] I verified proper code patterns were followed (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product was added in all src/languages/* files
[x] I verified any copy / text that was added to the app is correct English and approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I verified that this PR follows the guidelines as stated in the Review Guidelines
[x] I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] If a new component is created I verified that:

[x] A similar component doesn't exist in the codebase
[x] All props are defined accurately and each prop has a /** comment above it */
[x] The file is named correctly
[x] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[x] The only data being stored in the state is data necessary for rendering and nothing else
[x] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[x] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[x] All JSX used for rendering exists in the render method
[x] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG)

[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[ ] I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

@Ollyws Testing steps can be improved, please add steps to verify New Workspaces button is not shown in FAB. if there are any pending add actions

Thanks for the quick update!

Recordings: https://github.com/Expensify/App/pull/12367#issuecomment-1304907152
Checklist: https://github.com/Expensify/App/pull/12367#issuecomment-1304907629
Looks good tests well!
C+ Reviewed
🎀 👀 🎀
All you @Julesssss

Spent my day on a few other issues, this is on my list for reviewing tomorrow 👍

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to staging by @Julesssss in version: 1.2.25-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by @yuwenmemon in version: 1.2.25-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


[GEARPUMP-275] Remove obsolete examples of 'stockcrawler' and 'transp…

…ort'
Be sure to do all of the following to help us incorporate your contribution
quickly and easily:

[x] Make sure the commit message is formatted like:
[GEARPUMP-<Jira issue #>] Meaningful description of pull request
[ ] Make sure tests pass via sbt clean test.
[x] Make sure old documentation affected by the pull request has been updated and new documentation added for new functionality.

Codecov Report

Merging #152 into master will increase coverage by 0.19%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #152      +/-   ##
==========================================
+ Coverage   71.56%   71.76%   +0.19%
==========================================
  Files         191      191
  Lines        6070     6070
  Branches      510      510
==========================================
+ Hits         4344     4356      +12
+ Misses       1726     1714      -12

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 df40cbd...9188fd3. Read the comment docs.

LGTM +1


Event publishing for LoadBalancer

Problem
No events are published for LoadBalancer
Modification
Publishing events for LoadBalancer
Result
More events, more insight!

@sgury I have addressed your comments.


Use the full-path hyperlink to indicate the raw file

All Submissions:

[x] Have you followed the guidelines stated in CONTRIBUTING.md file?
[x] Have you checked to ensure there aren't any other open Pull Requests for the desired changed?

Type of change
Please delete options that are not relevant.

[x] Bug fix (non-breaking change which fixes an issue)

New Feature Submission:
Changes To Core Features:
After these steps, you're ready to open a pull request.
a. Give a descriptive title to your PR.

b. Describe your changes.

c. Put `closes #XXXX` in your comment to auto-close the issue that your PR fixes (if such).

closes https://github.com/reflex-dev/reflex/issues/1558

Why do we need to use the full path? Is the image not showing up for you?

#1558

Why do we need to use the full path? Is the image not showing up for you?

@picklelo  Because this PR is to solve this issue

https://github.com/reflex-dev/reflex/issues/1558
You can see this issue and I post a command about how to resolve it.


toolchain/BUILD.tpl: add missing ':ar' dependency

When linking a static library, the following error could occur:
ERROR: BUILD.bazel:123:1: Linking of rule '//foo:libfoo' failed (Exit 1)
external/io_bazel/src/main/tools/process-wrapper-legacy.cc:58: "execvp(external/llvm_toolchain/bin/llvm-ar, ...)": No such file or directory

This was due to :linker_components missing a dependency on the :ar target.
This change add :ar to the :linker_components target.
Signed-off-by: Jason S. McMullan<EMAIL_ADDRESS>

Jason, is it possible for you to either update your bazel version to 1.0+, or to go to a commit before 2200d53?
I am thinking of a good way to message to people that going forward, this project is going to have a strict requirement on bazel 1.0 or up so we start relying on their shipped configurations. I guess I will have to load skylib to check bazel version when they register the toolchain using the provided method.

Let's merge this now, and I will do a new release when we actually start using features from bazel 1.0 onwards.


Add the support class for the Adjoint Jacobian to the new device

Before submitting
Please complete the following checklist when submitting a PR:

[X] All new features must include a unit test.
If you've fixed a bug or added code that should be tested, add a test to the
tests directory!

[X] All new functions and code must be clearly commented and documented.
If you do make documentation changes, make sure that the docs build and
render correctly by running make docs.

[X] Ensure that the test suite passes, by running make test.

[ ] Add a new entry to the .github/CHANGELOG.md file, summarizing the
change, and including a link back to the PR.

[X] Ensure that code is properly formatted by running make format.

When all the above are checked, delete everything above the dashed
line and fill in the pull request template.

Context:
Migrate LightningGPU to the new device API
Description of the Change:
Create the adjoint-jacobian class for the new device API to achieve the jacobian and vjp methods
Benefits:
Unlocking the adjoint-jacobian capabilities with the new device API for LGPU
Possible Drawbacks:
Related GitHub Issues:
Freezzed PR :warning: :snowflake:
To make a smooth integration of LightningGPU with the new device API, we set the branch gpuNewAPI_backend as the base branch target for future developments related to this big task.
The branch gpuNewAPI_backend has the mock of all classes and methods necessary for the new API. Also, several tests were disabled with
if device_name == "lightning.gpu":
    pytest.skip("LGPU new API in WIP.  Skipping.",allow_module_level=True)

However, these tests will unblocked as the implementation progresses.
After all the developments for integrating LightningGPU with the new API have been completed then the PR will be open to merge to master
[sc-70936] [sc-70939]

Hey @LuisAlfredoNu, is this PR ready for review? Apparently, we have several test fails.

Hey @LuisAlfredoNu, is this PR ready for review? Apparently, we have several test fails.

@AmintorDusko
Sorry, I realize that right now it has several errors after the merge of the last commit of simulate branch :disappointed:. I will fix it and call to review it again. :smile:

Hey @LuisAlfredoNu, is this PR ready for review? Apparently, we have several test fails.

@AmintorDusko Sorry, I realize that right now it has several errors after the merge of the last commit of simulate branch 😞. I will fix it and call to review it again. 😄

Thank you, @LuisAlfredoNu!


Iteration Plan for 1.0.x

This is a plan outlining all the changes to some detail about the development of the Firefox Quantum Themes based off of Firefox DevTools.
Language Support
One of the main focuses with this theme is readability, uniformity and ease of use. I have found the DevTools to be quite fragmented when it comes to syntax highlighting (and probably can say the same with others) and have swapped some of the colours for this reason.
Below is a checklist of all the default languages VSCode supports, tick means support has been completed and vice versa. I do not include their marketplace extensions.

[x] Batch
[x] C
[x] C#
[x] C++
[x] CSS
[x] Clojure
[x] CoffeeScript
[x] Diff
[x] Dockerfile
[x] F#
[x] Git Commit
[x] Git Rebase
[x] Go
[x] Groovy
[x] HLSL
[x] HTML
[x] Handlebars
[x] Ignore
[x] Ini
[x] JSON/C
[x] Java
[x] JavaScript/React
[x] Less
[x] Lua
[x] Makefile
[x] Markdown
[ ] Objective-C/C++
[x] PHP
[x] Perl/6
[x] Powershell
[x] Properties
[x] Pug
[x] Python
[x] R
[x] Razor
[ ] Ruby
[ ] Rust
[x] SCSS
[ ] SQL
[ ] Shaderlab
[ ] Shell Script
[ ] Swift
[x] TypeScript/React
[ ] Visual Basic
[x] XML + Additionals
[x] YAML
[x] log

UI Support
Syntad Highlighting doesn't mean anything if the UI has poor support. As someone who is crazy about UI, I will ensure that people can see clearly and use easily without any problems

[x] Editor

[x] Cursor
[x] Word/bracket match
[x] Selected text
[x] Scrollbars

[x] Sidebar
[x] Panels
[x] Menus/Dropdowns
[x] Inputs (inc. buttons, badges etc)
[x] Hover and State effects

The relevant checklist for the light version can be found in #4
Publishing Preparations
Currently the only way to use this theme is to clone this repo, and put it in the extensions folder of VSCode. However, there are still preps to do before it will be officially published.

[ ] Finish both Dark and Light
[ ] Check that all code is consistent and there are not lingering bugs
[ ] Finish code screenshots
[ ] Add full customisation documentation
[ ] Prepare for full release

[ ] Including resetting all pulls and issues

[x] Announce somewhere?

Remaining meta/repo cleanup moved to 1.1.x


Sets of 4 10-tuples with constant spacing between them

Updated the 7-10 tuple offsets to take advantage of the optimization when consecuting offsets have the same gap between them.

Cool, thank you :D !


CLI Improve Docstring Help Text

Improve help text generation for docstrings used in CLI help descriptions.
from argparse import HelpFormatter
from pydantic_settings import BaseSettings, CliSettingsSource

class Settings(BaseSettings):
    """
    My
    Multiline
    Doc
    """

# Default now preserves docstring formatting:
s = CliSettingsSource(Settings)
print(s.root_parser.format_help())
"""
usage: example.py [-h]

My
Multiline
Doc

options:
  -h, --help  show this help message and exit
"""

# Also fixed an issue where formatter_class was not getting applied when set.
# Previously, generated docstring help text would default to the below and would not preserve formatting:
s = CliSettingsSource(Settings, formatter_class=HelpFormatter)
print(s.root_parser.format_help())
"""
usage: example.py [-h]

My Multiline Doc

options:
  -h, --help  show this help message and exit
"""

@hramezani can you help with the mac OS failure? I'm not sure what that is about.

Thanks @kschwab

@hramezani can you help with the mac OS failure? I'm not sure what that is about.

Sure, I updated the github actions and it got fixed.


Memory issue, registering classes.

Registering classes have memory issue:

import Dip
let rootAssembly = DependencyContainer { (container) in
unowned let container = container
container.register(.weakSingleton, factory: RootPresenter.init)
    .implements(AnyObject.self,
                RootModuleInput.self,
                AppDelegateOutput.self,
                RootInteractorOutput.self)
    .resolvingProperties { container, presenter in
        presenter.delegate = UIApplication.shared.delegate as! AppDelegate
        presenter.router = try! container.resolve()
        presenter.interactor = try! container.resolve()
        presenter.deeplinkHandler = try! container.resolve()
        presenter.shortcutHandler = try! container.resolve()
}

...
or
import Dip
let rootAssembly = DependencyContainer { (container) in
unowned let container = container
container.register(.weakSingleton, type: RootPresenter.self, factory: RootPresenter.init)
    .implements(AnyObject.self,
                RootModuleInput.self,
                AppDelegateOutput.self,
                RootInteractorOutput.self)
    .resolvingProperties { container, presenter in
        presenter.delegate = UIApplication.shared.delegate as! AppDelegate
        presenter.router = try! container.resolve()
        presenter.interactor = try! container.resolve()
        presenter.deeplinkHandler = try! container.resolve()
        presenter.shortcutHandler = try! container.resolve()
}

...
or
import Dip
let rootAssembly = DependencyContainer { (container) in
unowned let container = container
container.register(.weakSingleton) { RootPresenter() }
    .implements(AnyObject.self,
                RootModuleInput.self,
                AppDelegateOutput.self,
                RootInteractorOutput.self)
    .resolvingProperties { container, presenter in
        presenter.delegate = UIApplication.shared.delegate as! AppDelegate
        presenter.router = try! container.resolve()
        presenter.interactor = try! container.resolve()
        presenter.deeplinkHandler = try! container.resolve()
        presenter.shortcutHandler = try! container.resolve()
}

I've fixed issue by this way:

import Dip
let rootAssembly = DependencyContainer { (container) in
unowned let container = container
container.register(.weakSingleton, type: RootModuleInput.self, factory: RootPresenter.init)
    .implements(AnyObject.self,
                AppDelegateOutput.self,
                RootInteractorOutput.self)
    .resolvingProperties { container, presenter in
        presenter.delegate = UIApplication.shared.delegate as! AppDelegate
        presenter.router = try! container.resolve()
        presenter.interactor = try! container.resolve()
        presenter.deeplinkHandler = try! container.resolve()
        presenter.shortcutHandler = try! container.resolve()
}

...
or
container.register(.weakSingleton) { RootPresenter() as RootModuleInput }
    .implements(AnyObject.self,
                AppDelegateOutput.self,
                RootInteractorOutput.self)
    .resolvingProperties { container, presenter in
        presenter.delegate = UIApplication.shared.delegate as! AppDelegate
        presenter.router = try! container.resolve()
        presenter.interactor = try! container.resolve()
        presenter.deeplinkHandler = try! container.resolve()
        presenter.shortcutHandler = try! container.resolve()
}

...
Also issue actual for scopes : shared, singleton, eagerSingleton, weakSingleton.
Please provide any solution, because for me very important registering classes not protocols.

Move rootAssembly to Application delegate class.
It will fix the most of problems.

I checked this way and it has not helped.

import Dip
class AppDelegate: UIResponder, UIApplicationDelegate, AppDelegateInput {
var window: UIWindow?
var serviceLocator: ServiceLocator?

var output: AppDelegateOutput?
var moduleInput: RootModuleInput?

//    let container: DependencyContainer = rootAssembly
let container = DependencyContainer { (container) in
    unowned let container = container

    container.register(.weakSingleton) { RootPresenter() }
        .implements(AnyObject.self,
                    RootModuleInput.self,
                    AppDelegateOutput.self,
                    RootInteractorOutput.self)
        .resolvingProperties { container, presenter in
            presenter.delegate = UIApplication.shared.delegate as! AppDelegate
            presenter.router = try! container.resolve()
            presenter.interactor = try! container.resolve()
            presenter.deeplinkHandler = try! container.resolve()
            presenter.shortcutHandler = try! container.resolve()
    }

...

Can you please state the problem more clear? What is expected, what is actual behaviour?

Expected:
If you register a class with the scope: weakSingleton, there must be one instance of this class in memory.
Actual behaviour:
I've registered class with scope: weakSingleton
let container = DependencyContainer { (container) in
    unowned let container = container

    container.register(.weakSingleton) { RootPresenter() }
        .implements(AnyObject.self,
                    RootModuleInput.self,
                    AppDelegateOutput.self,
                    RootInteractorOutput.self)
        .resolvingProperties { container, presenter in
            presenter.delegate = UIApplication.shared.delegate as! AppDelegate
            presenter.router = try! container.resolve()
            presenter.interactor = try! container.resolve()
            presenter.deeplinkHandler = try! container.resolve()
            presenter.shortcutHandler = try! container.resolve()
    }

...
But in memory app has 5 instances of this class.

Please provide any solution!


feat: upgrade @volar/vue-language-server to v1.0

These are references for the changes:

https://github.com/johnsoncodehk/volar/pull/1916
https://github.com/johnsoncodehk/volar/issues/2046#issuecomment-1287825923

Fix #53

Thanks @johnsoncodehk! I'll review it asap

Sorry if it took so long... I'll merge this right away and publish an update


Added financial contributors to the 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/slimphp ❤
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!

Coverage remained the same at 97.999% when pulling 45732da469aab21cef23cd562bf71b9988ed5721 on opencollective:opencollective into 609a1ff894c25a03d4700d830d01858de3f1bb34 on slimphp:3.x.

Thank you for doing this! This is great. I think we can remove the "Credits" section since the "Contributors" section takes care of it instead.
Also can we duplicate this PR for the Slim 4.x branch as well since we have an upcoming major release?

I think I created a new pull on 4.x. I am not sure what you want to adjust in the credits. Please feel free to delete/edit as best works for your team.

@monkeywithacupcake you pulled against the 3.x branch as shown in the header of the pull request:

Also, it seems that the contributors svg is now broken. You can access it directly just fine however when you navigate to the README on this pull it does not show anymore:
https://opencollective.com/slimphp/contributors.svg?width=890&button=false

I'm not going to merge until this is rectified from you guys' end


fix: check for "REQNACK" response from indy ledger

Solves #569
Signed-off-by: annelein<EMAIL_ADDRESS>

Codecov Report

Merging #626 (a384ed0) into main (beff6b0) will decrease coverage by 0.00%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main     #626      +/-   ##
==========================================
- Coverage   87.08%   87.08%   -0.01%
==========================================
  Files         334      334
  Lines        6994     6998       +4
  Branches     1083     1084       +1
==========================================
+ Hits         6091     6094       +3
- Misses        902      903       +1
  Partials        1        1

Impacted Files
Coverage Δ

...ore/src/modules/indy/services/IndyHolderService.ts
75.92% <ø> (ø)

...e/src/modules/indy/services/IndyVerifierService.ts
91.66% <ø> (ø)

packages/core/src/modules/ledger/IndyPool.ts
82.92% <100.00%> (ø)

packages/core/src/modules/ledger/ledgerUtil.ts
100.00% <100.00%> (ø)

...ckages/core/src/modules/routing/RecipientModule.ts
67.27% <0.00%> (-0.42%)
:arrow_down:

.../modules/connections/services/ConnectionService.ts
88.78% <0.00%> (+0.05%)
:arrow_up:

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 beff6b0...a384ed0. Read the comment docs.


Error at starting the app

Forgot to add .pck file in the zip
Fixed now, keep both files together


CORS issue for scatter plot.

Getting a CORS issue for when scatter plot is selected.
Uncaught (in promise) DOMException: Failed to read the 'cssRules' property from 'CSSStyleSheet': Cannot access rules
appears in the browser console log.
The Grafana version I am using is 7.3.3 deployed on a subdomain.

This has been affecting my instances as well. I'm on Grafana 7.5.5 Cloud Enterprise. Mind you, only the 2d scatterplots are prevented from rendering. The 3d ones still show.


remove scrub

https://github.com/lnbits/scrub

Codecov Report

Merging #1524 (f5256ee) into main (451c8f7) will decrease coverage by 0.23%.
The diff coverage is n/a.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff             @@
##             main    #1524      +/-   ##
==========================================
- Coverage   49.03%   48.80%   -0.23%
==========================================
  Files          97       90       -7
  Lines        8732     8558     -174
==========================================
- Hits         4282     4177     -105
+ Misses       4450     4381      -69

Impacted Files
Coverage Δ

lnbits/db.py
81.20% <0.00%> (-10.07%)
:arrow_down:

lnbits/commands.py
61.40% <0.00%> (-1.76%)
:arrow_down:

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


Update TransferAccessMessage.getMessageSequenceNumber()

Change to return byte, rather than int.

@leshi PTAL

The current tests test valid values for bytes, so they all pass, as you can compare ints from 0 to 255 with bytes.
The underlying value was already a byte, it was just returning an integer. The tests were not set up to try to assign non-byte values.

LGTM


What are these result output windows 'pool, weak, strong, tracked, result, all ' means respectively?

I'm new to the image processing filed, would you please help me to answer this problem?

Dear byliut,
I think:
pool is the Character candidates extraction with non-maximum suppression step.
weak is weak possibility of the bonding box to be a letter.
strong is strong possibility of the bonding box to be a letter.
tracked are the tracked letters that contains strong and maybe same weak letters.
result is the result after the OCR step.

Dear byliut,
I think:
pool is the Character candidates extraction with non-maximum suppression step.
weak is weak possibility of the bonding box to be a letter.
strong is strong possibility of the bonding box to be a letter.
tracked are the tracked letters that contains strong and maybe same weak letters.
result is the result after the OCR step.
that sounds right, thank you!


[FIX] Fix broken import (bounds)

There was a broken import in cassetta/core/typing.py which attempted to import from a module (bounds) that does not exist. This fixes the import by deleting it.

That does not make sense. bounds is the import name for the torch-bounds package, which is a dependency in setup.cfg. Why is it not installed on your end?

Oops! I thought it was a custom module - I see now 😅

Did you get it to work, can I close and discard this PR?

Yes, I am all good now :)


Create 'best effort' parameter explainer

Command parameters are now largely left dangling. We want to provide some context, but first we need to figure out how to get that information from cmdlet help and store it.
Also cmdlet parameter binding is harder than it looks.

first step: description is now provided for parameters that are being passed in by parameterName.


a couple decoration changes

H1 greeting to the user are now showing on the top in mobile screens
flash triangles for all links are dismissed
the triangle indicators on the subject menu are turning to yellow color when hovered. To increase accessibility
in screen size 768 and under, cards' width has not limitation. To have a balanced page layout

@Meng-MiamiOH -- thanks for these changes. The name placement works, and turning off the flash triangles is good.
But the yellow triangle isn't sufficient contrast -- consulting with @yarnetsky, I think we need some UI change that's more than just color there.
Similarly, the Black/Red color change on link hover in the main body is also insufficient -- do you think it would be possible to turn the three triangles solid on hover?


added docs for creating a pos privnet

Credits go to @Ruteri

I feel it's a bit too specific, maybe we should post the guide to github.com/flashbots/boost-geth-builder and link it here?

Codecov Report

Merging #146 (15c7313) into main (ff25f53) will decrease coverage by 0.58%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main     #146      +/-   ##
==========================================
- Coverage   71.56%   70.98%   -0.59%
==========================================
  Files           6        6
  Lines         517      517
==========================================
- Hits          370      367       -3
- Misses        121      123       +2
- Partials       26       27       +1

Flag
Coverage Δ

unittests
70.98% <ø> (-0.59%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

server/service.go
74.08% <0.00%> (-1.22%)
: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 ff25f53...15c7313. Read the comment docs.

I prefer this repository to be the main source of documentation and community, and think that having the docs here helps with that (instead of causing some fragmentation). The whole Builder FAQ and guides will also be in this repo.


Can't run "List Resources" a second time

I'm just getting started on building a custom server, so forgive me if I'm misunderstanding something.
I'm using the default example server that is created when running npx @modelcontextprotocol/create-server.
It seems that you can list the Notes by running "List Resources" and you can create a Note from the Tools tab.
But it doesn't seem to be possible to list the new notes after creating one.
Reproduction:

create a new server
build
run the inspector
connect
click the List Resources button
create a new note from the Tools tab
Try to list the resources again (not possible)

Fair callout! I think adding a Reset or Clear button to the top of the List Resources section could be useful here.


Monitor Nomad Health

In the context of #390 we remove misleading Sentry events. Those events also used to report errors within Nomad. Besides that, we may only notice a bad health due to an Ansible deployment if the host is not reachable at all.
With this issue, we want to create a monitoring for the Nomad hosts. This monitoring might include the information of sudo nomad node status such as the Status or the Eligibility of the agents.

This ticket might become obsolete by #471 and an additional health monitoring in Poseidon (see https://github.com/openHPI/poseidon/issues/470#issuecomment-1759723309).


Font Not Found if changing assetFileNames to something with [hash]

I've been trying today to change the $client rollupOptions to use only hashes in the names. Otherwise, the AdBlocker would block the chunks that they thought were ads.
Doing so (code below) all works well, but the fonts cannot be found. I need to remove the assetFileNames, and it works well.
I thought that maybe the Google Fonts module somehow needs to know about the fonts paths through the client manifest?! 🤔
export default defineNuxtConfig({
	vite: {
		$client: {
			build: {
				rollupOptions: {
					output: {
						chunkFileNames: '_nuxt/[hash].js',
						entryFileNames: '_nuxt/[hash].js',
						// This will make fonts 404 on the client
						assetFileNames: '_nuxt/[hash][extname]',
					},
				},
			},
		},
	},

	modules: ['@nuxtjs/google-fonts'],
	googleFonts: {
		families: {
			'Montserrat': [100, 200, 300, 400, 500, 600, 700, 800, 900],
		},
	},
});

I see that Nuxt, by default, is using only hash in filenames https://github.com/nuxt/nuxt/pull/26203, and they don't mention assets, so probably that is the correct way. Will close the issue in this case.


Sema: Allow collection downcast in cast pattern and remove the diagnostic that it is not implemented

Resolves SR-13742 (#56139)

Requesting Slava to review SIL tests.

@swift-ci please smoke test

@simanerush That is a false positive, a single-element array literal cannot possibly be heterogeneous. Looks like we need another issue report. The warning will have to be verified in the meantime.

@slavapestov could you take a look?

@swift-ci please smoke test macOS

@swift-ci please smoke test

@swift-ci please clean smoke test macOS

@swift-ci please smoke test macOS

@xedin Do you reckon this needs a changelog entry?


laravel back() no redirect preview page, redirecting to /

laravel back() no redirect preview page, redirecting to page /

Can you help me replicate this error in my machine?

I have a route
Route::get('/test/{id}/edit', 'TestController@test');
TestController
`
function test($id, Request $request) {
$validator = Validator::make($request->all(), [
'fieldname' => 'required',
]);
  if ($validator->fails()) {
      return back();
  }
 TestModel::update($request->all());
  return redirect('/test');

}
`
No redirect

I have a route
Route::post('/test/{id}/edit', 'TestController@test');
TestController
function test($id, Request $request) {
    $validator = Validator::make($request->all(), [
        'fieldname' => 'required',
    ]);

   if ($validator->fails()) {
       return back();
   }
  TestModel::find($id)->update($request->all());
   return redirect('/test');
}

This works fine form me in my pc. Double-check your env as the documentation says Since this feature utilizes the session, make sure the route calling the back function is using the web middleware group or has all of the session middleware applied

its return redirect()->back();

I think both of return redirect()->back(); and return back(); do the same job. @yordadev
https://github.com/laravel/framework/blob/7ccf0cf63931a8d8391aed90e6fc011381ea6838/src/Illuminate/Foundation/helpers.php#L178

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

Laracasts Forums
Laravel.io Forums
StackOverflow
Discord
Larachat
IRC

However, this issue will not be locked and everyone is still free to discuss solutions to your problem!
Thanks.


add binder in quick start

@renskegelderloos @ThomasHaine @asiddi24
I've added the badge in the quick start section. Please check it out and feel free to edit the new text, or move the badge elsewhere.

Here is the badge:


New theme: GNU dircolors (ls etc color configurator)

I added a theme for dircolors, the thing in GNU coreutils that generates LS_COLORS env var that GNU ls and some other related tools use to colorize their output.
https://github.com/scop/dracula-dircolors
I should probably delete the sample/ dir that the template brought in as I suppose it has no use in this theme.

Hey, very cool! ✨
I just sent you an invitation to join the organization.
I also cloned your repository for Dracula's organization, so you can go ahead and delete or archive yours:

Your repository.
New repository.

Thanks for building this! 🎉

Nice, removed mine, removed unneeded samples, and synced with new changes that I contributed to coreutils upstream.
I don't see this theme yet at https://draculatheme.com, and https://draculatheme.com/dircolors gives a 500. Anything I can do to help fix that?

Nice! Now I will be adding it, and soon it will be online on the site! ✨

It's live now https://draculatheme.com/dircolors ;)


Make interpolation and extrapolation behavior configurable

This adds interpolate and extrapolate keyword arguments to the Item types (Image, MaskBinary, MaskMulti) following the design described by @lorenzoh in #60.
Resolves #60
PR Checklist

[x] Tests are added
[x] Documentation, if applicable

this looks great!


TODO

[x] Test cron job
[x] Refactor code for modular approach
[x] Shift core logic for both post and get request to middlewares
[x] Add authentication
[x] Remove blocking code
[ ] API testing if possible
[ ] Add mailing/Notification service for events like Cron job started, stopped, cleanup done etc

Closing TODO as notification is not much of a feature right now, PRs are welcome :smiley:


implement socket.inet_pton, socket.inet_ntop

Thank you for your review. I revised it as you told me.


Incoming commands

Hey there, I implement the Slack outgoing webhook server.
And this PR is based on #7 I send.

Thank you a lot for this. Looks good with a quick glance, I am going to change a bit of the code and review it more over this weekend. Again, THANK YOU.

Could you explain your reasoning for jetty? Not disagreeing with you, just want to see why you choose it and if we can discuss alternatives to make sure we include the best option for Slack.

Alright, I merged this, just to mark progress but this pull request isn't done yet because we're going to have to change some stuff.

I will be rewriting this based on your contributions. Thanks!

Dynmap also use jetty so I think it's ok for bukkit plugins.

Ok.


add delete to savedpins

Add delete functionality to frontend savedpins

Delete button added but needs CSS updates to look prettier

@motosharpley this issue can be closed. There are a few functions duplicated in different locations to create the buttons and text in the markers that should be merged but I think that can be a new issue?

@steveone yes, please create an issue for refactoring to resolve duplication of code as detailed as you can. It will help facilitate maintaining, expanding, and effectively testing the code base. Thanks - will close this issue.