Fix typo and Create Luadoc

Fixed a typo (symbol_in_winbar.dely --> delay)
Created luadoc so the LSP can validate your options

These docs are created from the latest init.lua, but using the descriptions from the website

thanks very nice.


New release has changed its gpg key without mentioning anywhere

Signature has been changed in 0.12.0 again and this has not been mentioned in release again and I'm not sure if this is my problem again and if I should I open a new issue again :)
I used to verify package with 963A2BEB02009608FE67EA4249FD77499570FF31 (Fedora 33), now it should be verified with 8C5BA6990BDB26E19F2A1A801161AE6945719A39 (Fedora 34).
This has happened and reported on https://github.com/coreos/butane/issues/173 before.

Yes, you're correct.  :disappointed:  Thanks for reporting this again.  I've updated the release notes and I'll start another discussion about https://github.com/coreos/butane/issues/174.


source generator for unity like memorypack?

hi,first I need to say arch is very  very performance and convenient to use!
memorypack from cysharp support source generator for unity,so may arch also support it. and it is also good for sterilization!

Thanks!
Well i have choosen Messagepack over Memorypack because Memorypack requires a lot for sourcegen.
All arch internal structs and classes would have to be annotated with the attributes and thus memorypack would have to reside directly in arch instead of it being an extension. This would only unnecessarily bloat arch itself and defeat the core aspect of arch. Arch itself is supposed to be bare-minimum.
Messagepack is only a little slower than memorypack, so I would find it unnecessary to upgrade to it. If you still want to have memorypack, you can easily fork arch and add that yourself ^^


get-script does not work when used with --version v2.10.0

Hi there,
I use the get-script to install helm, in this fashion:
curl https://raw.githubusercontent.com/kubernetes/helm/v2.10.0/scripts/get > get_helm.sh
chmod 700 get_helm.sh
./get_helm.sh
The script has a --version parameter, which according to documentation can be set to a specific helm version or to latest (which is the default). The following works fine:
./get_helm.sh --version v2.9.0
However, when using the currently released version v2.10.0, I get an error message (and in general: pretty weird output mentioning a version v2.15.0?)
./get_helm.sh --version latest
or
./get_helm.sh --version v2.10.0
results in this error message:
Helm v2.10.0
v2.15.0 is available. Changing from version v2.10.0.
Downloading https://kubernetes-helm.storage.googleapis.com/helm-v2.10.0
v2.15.0-linux-amd64.tar.gz
curl: (3) Illegal characters found in URL
Failed to install helm with the arguments provided: --version v2.10.0
Accepted cli arguments are:
[--help|-h ] ->> prints this help
[--version|-v <desired_version>] . When not defined it defaults to latest
e.g. --version v2.4.0  or -v latest
For support, go to https://github.com/helm/helm.

Some additional details:
The same issue occurs when retrieving the script from
https://raw.githubusercontent.com/kubernetes/helm/release-2.10/scripts/get
But the problem does not occur when retrieving the script from the master branch.
However, I wanted to make sure that the install script is compatible to the helm version I am trying to install, therefore I want to use the tagged version of the script.

I am seeing the same issue. It occurs for tags v2.9.1 and v2.10.0 but not on master:
Failure with v2.9.1:
$ curl https://raw.githubusercontent.com/kubernetes/helm/v2.9.1/scripts/get | bash
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  6737  100  6737    0     0  45413      0 --:--:-- --:--:-- --:--:-- 45520
Downloading https://kubernetes-helm.storage.googleapis.com/helm-v2.10.0
v2.15.0-linux-amd64.tar.gz
curl: (3) Illegal characters found in URL
Failed to install helm
	For support, go to https://github.com/kubernetes/helm.

Failure with v2.10.0:
$ curl https://raw.githubusercontent.com/kubernetes/helm/v2.10.0/scripts/get | bash
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  6685  100  6685    0     0  56976      0 --:--:-- --:--:-- --:--:-- 57136
Downloading https://kubernetes-helm.storage.googleapis.com/helm-v2.10.0
v2.15.0-linux-amd64.tar.gz
curl: (3) Illegal characters found in URL
Failed to install helm
	For support, go to https://github.com/helm/helm.

Success with master:
$ curl https://raw.githubusercontent.com/kubernetes/helm/master/scripts/get | bash
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  6709  100  6709    0     0  70118      0 --:--:-- --:--:-- --:--:-- 71372
Downloading https://kubernetes-helm.storage.googleapis.com/helm-v2.10.0-linux-amd64.tar.gz
Preparing to install into /usr/local/bin

There was a bug with the script which was fixed in master. https://github.com/helm/helm/pull/4484 was the fix. Please use the master branch for the get-script moving forward. Thanks! :)

Thanks for your prompt and friendly support, @bacongobbler!

Can someone please tell me the command to install helm in windows ? Do i need to have any prerequisites like kubernetes or something else, please let me know.
Reason why I want helm is to manually push property files (config maps) into Openshift server as our CI/CD pipeline is not yet ready for our current project.
I installed helm and the folder contains below, added it to the environmental variables path as well


Move weather files to separate directory

Currently, they are part of the country-specific db stuff (cea/db/CH/...)

@JIMENOFONSECA : Do you have input on this?

yes, we can do that. please feel free to move it to a separate directory in the databases.

on branch 235-move-weather-files-to-separate-directory but I need to wait for PR #423 to be merged first. @JIMENOFONSECA can you look into that?

done!

From: Daren Thomas<EMAIL_ADDRESS>Sent: Wednesday, December 07, 2016 11:33 PM
To: architecture-building-systems/CEAforArcGIS
Cc: Jimeno Fonseca; Mention
Subject: Re: [architecture-building-systems/CEAforArcGIS] Move weather files to separate directory (#235)
on branch 235-move-weather-files-to-separate-directory but I need to wait for PR #423https://github.com/architecture-building-systems/CEAforArcGIS/issues/423 to be merged first. @JIMENOFONSECAhttps://github.com/JIMENOFONSECA can you look into that?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/architecture-building-systems/CEAforArcGIS/issues/235#issuecomment-265478545, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AIjrgsovgN_p351hn1vgjJ8WC-p73o-qks5rFtG4gaJpZM4Iu-es.

fixed in PR #433


Wrong stats in multi-node local executor

Due to lack of node-level communication, the stats at the end of each pipeline step can only aggregate results from the current node, and what's being written to the disk is the status of the last finished worker, rather than the global info

Hey, this is resolved for slurm by running a stats merger after all substasks are finished. I don't think there is a way to accomplish same behavior, as the global orchestration in multi-node is not done by datatrove. Thus the responsibility of launching the merge script can't handled by datatrove.
If you log all stats into one folder you can use this script https://github.com/huggingface/datatrove/blob/main/src/datatrove/tools/merge_stats.py, which is exactly the script the slurm executor runs after all tasks have finished


Question: Infra dashboard resource providers requirements

Describe the bug
The following document says "least the Microsoft.Advisor and the Microsoft.Security resource providers", but the bullet list contains Microsoft.Resourcehealth. Is Microsoft.Resourcehealth optional or mis-documented?
https://github.com/Azure/ccodashboard/blob/master/dashboards/CCODashboard-Infra/InfraDeploymentGuide.md

Although some of the Resource Providers might be enabled by default, you need to make sure that at least the Microsoft.Advisor and the Microsoft.Security resource providers are registered across all the subscriptions that you plan analyze using the Dashboard.
Registering these 3 Resource Providers has no cost or performance penalty on the subscription:

Click on Subscriptions.
Click on the Subscription name you want to configure.
Click on Resource Providers.
Click on Microsoft.Advisor and Register.
Click on Microsoft.Resourcehealth and Register.
Click on Microsoft.Security and Register.

To Reproduce
n/a
Expected behavior
n/a
Screenshots
n/a
Desktop (please complete the following information):
n/a
Smartphone (please complete the following information):
n/a
Additional context
n/a

Currently this is not required.
In the first releases we're using resource health API calls, but it's not needed anymore because the same information can be extracted from other sources if something is not OK.


remove build_id and build_date from _app.js

Remove BUILD_ID and BUILD_DATE from metadata in _app.js
Title

Check out a preview of your pull request here: https://app-servicecanadalabs-dev-pr-preview-2.azurewebsites.net


[build] Fix some warnings on web builds and remove some redundant flags.

@lzralbu thanks for the update. @Peter0x44 thanks for the review


Block Explorer URL Incorrect

The https://filscan.io FIL address path has changed.
When clicking the asset in the MetaMask UI, filsnap currently redirects to: https://filscan.io/#/address/detail?address=ADDRESS
While the correct path is: https://filscan.io/#/tipset/address-detail?address=ADDRESS

As an additional note, maybe it would be better to direct the user to the Netlify Snap UI, since it's more interactive.

@rekmarks Thanks for the issue. I think it is more meaningful to keep the link on the Filscan address details. Netlify Snap UI is more of a demo app for FilSnap while Filscan shows transaction history for the specified address.


biscuit-cli: 0.4.0 -> 0.4.1

Description of changes
This PR upgrades biscuit-cli to its latest version: https://github.com/biscuit-auth/biscuit-cli/releases/tag/0.4.1
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.


DefaultAuthenticationListenerFactory creates own instance of OAuth2Server

I'm attempting to integrate Satellizer with Apigility.  Satellizer uses JWT Bearer, which requires some extra setup on the Apigility side (in bshaffer/oauth2-server-php, technically).  zf-mvc-auth's DefaultAuthenticationListenerFactory pulls all the pieces from zf-oauth2's configuration and builds a new OAuth2Server instance rather than pulling the pre-configured one that zf-oauth2 slaved long and hard to construct.  Would it be acceptable to modify the factory to pull the preconfigured instance?  (If yes, I can provide a PR)
Source: https://github.com/zfcampus/zf-mvc-auth/blob/master/src/Factory/DefaultAuthenticationListenerFactory.php#L75

Any updates on this ? We are planning to integrate Satellizer with Apigility as well


Update documentation: About Us | Resolves #17

Let me know if you think we need additional roles(or if you want a more glamorous photo)! :)

Looks great! Added keywords: Resolves #17, for automatic closure of issue.
Good work 😄


PT-159960482 Test that minimum oracle response tx fee depends on orac…

…le response size

Please prefer merging (as opposed to squash or rebase) and not force pushing (if possible) in order not to require rebase of #1792


Database service does not work with ibmq_qasm_simulator

Informations

Qiskit Experiments version: b40cb9887061136e26bffd62ee07d5afe79af2b0
Python version: 3.9.10
Operating system: Arch Linux

What is the current behavior?
Database service does not work with ibmq_qasm_simulator
Steps to reproduce the problem
import json
from qiskit import IBMQ
from qiskit.providers.aer import AerSimulator
from qiskit_experiments.library import StandardRB

IBMQ.load_account()
provider = IBMQ.get_provider(hub='ibm-q-internal', group='deployed', project='default')
backend = provider.get_backend('ibmq_qasm_simulator')

exp = StandardRB(
    qubits=(0,),
    lengths=list(range(1, 5)),
    seed=123,
    backend=backend,
)
data = exp.run()

data.save()

Unable to save the experiment data: Traceback (most recent call last):
  File "/home/kjs/projects/qiskit-experiments/qiskit_experiments/database_service/utils.py", line 152, in save_data
    return True, new_func(**kwargs)
  File "/home/kjs/.local/share/virtualenvs/qiskit-research-4492DR1p/lib/python3.9/site-packages/qiskit/providers/ibmq/experiment/ibm_experiment_service.py", line 179, in create_experiment
    response_data = self._api_client.experiment_upload(json.dumps(data, cls=json_encoder))
  File "/usr/lib/python3.9/contextlib.py", line 137, in __exit__
    self.gen.throw(typ, value, traceback)
  File "/home/kjs/.local/share/virtualenvs/qiskit-research-4492DR1p/lib/python3.9/site-packages/qiskit/providers/ibmq/experiment/utils.py", line 33, in map_api_error
    raise IBMQApiError(f"Failed to process the request: {api_err}") from None
qiskit.providers.ibmq.exceptions.IBMQApiError: 'Failed to process the request: \'400 Client Error: Bad Request for url: https://api.quantum-computing.ibm.com/resultsdb/experiments. {"errors":["Device ibmq_qasm_simulator either does not exist or is not available"]}\''

What is the expected behavior?
It should work.
Suggested solutions
None yet.

This is intentional in the DB level; we need to make it fail gracefully.

Why is it intentional?

I don't know; maybe a slack discussion with the experiment DB people is in order.

It still appears to be an issue. Here is the updated repro and error message:
import json
from qiskit_aer import AerSimulator
from qiskit_experiments.library import StandardRB
from qiskit_ibm_provider import IBMProvider

hub = "ibm-q-internal"
group = "deployed"
project = "default"

provider = IBMProvider(instance=f"{hub}/{group}/{project}")
backend = provider.get_backend('ibmq_qasm_simulator')

exp = StandardRB(
    qubits=(0,),
    lengths=list(range(1, 5)),
    seed=123,
    backend=backend,
)
data = exp.run()

data.save()

/tmp/ipykernel_3258498/1888729725.py:13: DeprecationWarning: StandardRB.__init__ keyword argument qubits is deprecated and will be removed after Qiskit Experiments 0.5. It is now replaced with physical_qubits.
  exp = StandardRB(
Unable to save the experiment data: Traceback (most recent call last):
  File "/home/ksung/.local/share/virtualenvs/qiskit-rJgFZorW/lib/python3.10/site-packages/qiskit_experiments/framework/experiment_data.py", line 1354, in _save_experiment_metadata
    self.service.create_or_update_experiment(
  File "/home/ksung/.local/share/virtualenvs/qiskit-rJgFZorW/lib/python3.10/site-packages/qiskit_ibm_experiment/service/ibm_experiment_service.py", line 402, in create_or_update_experiment
    return self.create_or_update(
  File "/home/ksung/.local/share/virtualenvs/qiskit-rJgFZorW/lib/python3.10/site-packages/qiskit_ibm_experiment/service/ibm_experiment_service.py", line 1573, in create_or_update
    result = create_func(**params)
  File "/home/ksung/.local/share/virtualenvs/qiskit-rJgFZorW/lib/python3.10/site-packages/qiskit_ibm_experiment/service/ibm_experiment_service.py", line 342, in create_experiment
    with map_api_error(f"Experiment {data.experiment_id} creation failed."):
  File "/home/ksung/.pyenv/versions/3.10.13/lib/python3.10/contextlib.py", line 153, in __exit__
    self.gen.throw(typ, value, traceback)
  File "/home/ksung/.local/share/virtualenvs/qiskit-rJgFZorW/lib/python3.10/site-packages/qiskit_ibm_experiment/service/utils.py", line 45, in map_api_error
    raise IBMApiError(
qiskit_ibm_experiment.exceptions.IBMApiError: 'Failed to process the request: The server responded with \'400 Client Error: Bad Request for url: https://resultsdb.quantum-computing.ibm.com/experiments. {"errors":["Device ibmq_qasm_simulator is unavailable. Check your access permissions and that the device exists."]}\''

Could not save experiment metadata to DB, aborting experiment save
/home/ksung/.local/share/virtualenvs/qiskit-rJgFZorW/lib/python3.10/site-packages/numpy/lib/function_base.py:2455: RuntimeWarning: invalid value encountered in <lambda> (vectorized)
  outputs = ufunc(*inputs)

That looks like an old syntax. Can you update to the newest stable releases of experiments/qiskit-ibm-experiment/qiskit-ibm-provider? This code works for me:
from qiskit_experiments.library import StandardRB
from qiskit_ibm_provider import IBMProvider

hub = "ibm-q-internal"
group = "dev-sys-software"
project = "internal-test"

provider = IBMProvider(instance=f"{hub}/{group}/{project}")
backend = provider.get_backend('ibmq_qasm_simulator')

exp = StandardRB(
    physical_qubits=(0,),
    lengths=list(range(1, 5)),
    seed=123,
    backend=backend,
)
data = exp.run().block_for_results()
data.save()

And the experiment is at: https://quantum.ibm.com/experiments/ee0921ee-2ec2-4635-b70a-61c6d420659b

That doesn't work for me; I get the same error. Could it be due to the provider? Could you try using the provider I specified? I don't have access to the one you used. I am using the latest versions of the packages. Here is the output of pip list | grep qiskit:
qiskit                        0.45.1
qiskit-aer                    0.12.2
qiskit-dynamics               0.4.2
qiskit-experiments            0.5.4
qiskit-ibm-experiment         0.3.5
qiskit-ibm-provider           0.7.2
qiskit-ibm-runtime            0.16.1
qiskit-qasm3-import           0.2.0
qiskit-sphinx-theme           1.16.0
qiskit-terra                  0.45.1


Leetcode Question Number 1941

Leetcode Question Number 1941 solution needs to be added in the repo .
The link for the question is this.
Accepted Languages C++ / JAVA .
You Only need to add the  class Solution in the file.
Make Sure you have read the contributions guidelines before creating an PR.

I want to work on this issue.


[stable/prometheus-operator] Install fails on helm 3 and Kubernetes 1.16

Describe the bug
Install fails
Version of Helm and Kubernetes:
Helm: v3.0.1
Kubernetes: 1.16
Which chart:
stable/prometheus-operator
What happened:
manifest_sorter.go:175: info: skipping unknown hook: "crd-install" manifest_sorter.go:175: info: skipping unknown hook: "crd-install" manifest_sorter.go:175: info: skipping unknown hook: "crd-install" manifest_sorter.go:175: info: skipping unknown hook: "crd-install" manifest_sorter.go:175: info: skipping unknown hook: "crd-install" Error: unable to build kubernetes objects from release manifest: error validating "": error validating data: ValidationError(MutatingWebhookConfiguration.webhooks[0].clientConfig): missing required field "caBundle" in io.k8s.api.admissionregistration.v1beta1.WebhookClientConfig
What you expected to happen:
Install
How to reproduce it (as minimally and precisely as possible):
The install command used was: helm install prometheus stable/prometheus-operator
helm repo update also ran.
Anything else we need to know:
The kubernetes insteance was created by KOPS on AWS.
Thanks for any help getting this working!
As Helm 3 has been released, is it worth adding specific steps for Helm 3 on the README? The current command is only valid for helm 2.

Note that adding -v 5 gives no further logs, as does using  --set prometheusOperator.logLevel=all --set prometheus.prometheusSpec.logLevel=all.  The steps  here did not appear to make any difference.

Note that adding -v 5 gives no further logs, as does using --set prometheusOperator.logLevel=all --set prometheus.prometheusSpec.logLevel=all. The steps here did not appear to make any difference.

https://github.com/helm/charts/issues/17511 seems to cover this in the comments if not the original issue, will delete.


How to extract exact part of text data from the  tag ?

Example -

Location:  Washington, DC

I have to fetch only "Washington, DC". If I will extract data by paragraph tag then whole content will print as " Location: Washington, DC". I don't want Location word.
Please give me any solution.
Thnx.

Please post questions to Stack Overflow.


invalid memory address or nil pointer dereference while FileIterator.Next()

Description of the bug:
(affected by v0.14.0)
Listing uploaded video files with FileIterator.Next() leads to 'invalid memory address or nil pointer deference' error.
Actual vs expected behavior:
Expected:
It should iterate through uploaded video files,
Actual:
but when calling Next(), it panics with 'invalid memory address or nil pointer deference' error.
Any other information you'd like to share?
https://github.com/google/generative-ai-go/blob/07538e582a63fd3291d1615d2b097221887da95c/genai/files.go#L144-L149
f.Metadata is set to nil here,
so subsequent access to it (f.Metadata.Video) leads to nil pointer dereference.

Thanks for finding the buggy code!


Mist processes don't always terminate

It seems to be this specific process: /usr/local/bin/MistInMP4 -H<EMAIL_ADDRESS>-F<EMAIL_ADDRESS>-g

Issue seems to be that the input file has a size of 0 bytes. The MistInMP4 process does not seem to deal with this correctly and keeps trying to read until it reads 16 bytes of data. Should be an easy fix


Stopped tests show as successful

If I run a long running test (say, I ran the request and I am debugging server code locally) and click the Cancel Test Run button (the rectangle thing next to the TESTING view header), the test icon shows as green check mark to indicate that the test was successful, while it was not (basically, the testy/request did not complete).

Not a big deal, since when cancelling the run, one would know that it was not completed, but still.

cancelation of test run did not work correctly. I registered my cancellation logic on the token provided by the test api. but I needed to use token provided by test run object. I also forgot to add skipped test result if user canceled the executation.


Parse error with ADTs

I was adding tests to Topiary for the new Nickel or keyword, but the example code doesn't parse. Here is a minimal working example (extracted from the Nickel typecheck/or_patterns.ncl test):
f : forall a. [| 'Baz a |] -> Dyn

Removing the a resolves the parse issue:
f : forall a. [| 'Baz |] -> Dyn

Ah, good catch. I think the pattern extension doesn't have anything to do with that, the grammar just hasn't been properly extended on the static type side. Because most of those appears in tests, and tests are currently not checked for formatting I believe, this might have slipped under the rug. Let me fix that quickly


MGMT-13752: Add signatures for existing triage tickets as well

Currently, the code at assisted-installer-deployment adds signatures and edit the description & fields only for newly created tickets.
We want to do the same for existing tickets for 2 main reasons:

If the original job that created a ticket couldn't finish adding all signatures for that ticket (e.g. logs-collector server got down temporarily, we had a bug in one of the signatures that has been fixed, etc.) we want to give it another try in the next jobs.
The plan for moving to Jira attachments relies on us creating tickets with the attachments and processing them further afterwards.

In addition, this changes some other things:

Moving all triage-related logic to a directory tools/triage.
Instead of loading all issues and then matching them with the failure IDs, just search for each one individually.
Remove now redundant code for normalizing failure IDs.
Created a "openshift versions" signature, instead of setting it at ticket creation.
Invoke the description signature (named FailureDescription) just like any other signature (instead of invocation at ticket creation).

/test all

/hold until finalizing tests

/cc @adriengentil @omertuc

Thanks! Starting the testing phase in jenkins

I might do more changes. I'll let you know once it's all playing nicely in jenkins

@adriengentil it should be ready for another review

/unhold
test in jenkins passed, so unholding


VCCIO Labeling

In the schematic the jumper for VCCIO_3 is wired in the port on the chip labeled VCCIO_0. I don't know if this is a mistake or a strange convention, but it cost me several hours today :/

Yes, strange but true! I can see why this is confusing... This is the
original upduino 2.0 design, I have not made any schematic changes.
There's a new design: please see the upduino 3.0 github. Hope these and
other bugs are fixed there. Board build is in process.
https://github.com/tinyvision-ai-inc/UPduino-v3.0
On Thu, Dec 26, 2019, 2:56 PM Matty G<EMAIL_ADDRESS>wrote:

In the schematic the jumper for VCCIO_3 is wired in the port on the chip
labeled VCCIO_0. I don't know if this is a mistake or a strange
convention, but it cost me several hours today :/
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/tinyvision-ai-inc/UPduino-v2.1/issues/3?email_source=notifications&email_token=AHDV6C6XHBPXLTBMXVL6LTTQ2UZARA5CNFSM4J7RNS32YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4ICYY23A,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHDV6C6CB2MUMZ55W7HXWSLQ2UZARANCNFSM4J7RNS3Q
.


fix: type export issues

What kind of change does this PR introduce?
This PR didn't quite work right. Two issues:

@types/websocket is an actual dependency but marked as devDep
It's easier on devs if we re-export from index.d.ts

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


H1 heading for mobile layout to long

XXXYYYZZZ</span

My h1 headline is too long.
How can i adjust the size of smartphone layout?
Thanks

This question is rather unrelated to Pico, but HTML/CSS. If the default theme doesn't meet your needs (what's rather expected, Pico's default theme is intended as a starting point for creating a own theme), you can choose to use one of our great 3rd-party themes. You can find a selection of excellent themes on our website and a even greater list of themes in our Wiki.

Thanks for the tip.

@media (max-width: 360px)  {      #mt { font-size: 0.7em; }     #ea {  font-size: 1.2em; }     #mql { font-size: 0.7em; } }
Perfect for mobile screen.


Add an emoji keyboard layout

I think we need a new separate layout dedicated to emoji. There should be several groups, i.e. faces, tools, animals, etc. Some characters should be usable as modifiers, i.e. a man + a tool = a man having that job, or skin color modifier. So on the tools palette there should be a modifiers keys like shift. A tap changes the kind of modifier, a hold activates and deactivates. The keyboard should support font adjustment because emojis look different in different fonts.

This would make Hacker's Keyboard my only Android keyboard.
BTW is there a way to make the layout myself?

Don't know, I'm not a java or android dev.

Here is at least one off the shelf library:
https://github.com/edsilfer/emoji-keyboard

Duplicates #376


feat: Add opus file type

Adds support for Opus audio format.Opus is widely used and has replaced mp3 in many places.

(Hmm. I usually work with sourcehut. I wanted GitHub to use three branches for three separate PRs, but it merged my commits. I'll wait before I open the lass PR ...)

LGTM, thanks!


feat(Auth): Adding forceAliasCreation option during confirmSignUp

Description

Adding the ability to pass forceAliasCreation flag during confirming sign up. Usage:
      let pluginOptions = AWSAuthConfirmSignUpOptions(
            forceAliasCreation: true)
        let options = AuthConfirmSignUpRequest.Options(pluginOptions: pluginOptions)
        let result = try await self.plugin.confirmSignUp(
            for: "<username>",
            confirmationCode: "<confirmationCode>",
            options: options)

General Checklist

[x] Added new tests to cover change, if needed
[x] Build succeeds with all target using Swift Package Manager
[x] All unit tests pass
[x] All integration tests pass
[x] Security oriented best practices and standards are followed (e.g. using input sanitization, principle of least privilege, etc)
[ ] Documentation update for the change if required
[x] PR title conforms to conventional commit style
[ ] New or updated tests include Given When Then inline code documentation and are named accordingly testThing_condition_expectation()
[ ] If breaking change, documentation/changelog update with migration instructions

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

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (3c7fec5) 68.10% compared to head (9001d26) 68.11%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##             main    #3382   +/-   ##
=======================================
  Coverage   68.10%   68.11%
=======================================
  Files        1080     1080
  Lines       36343    36347    +4
=======================================
+ Hits        24753    24758    +5
+ Misses      11590    11589    -1

Flag
Coverage Δ

API_plugin_unit_test
67.50% <ø> (ø)

AWSPluginsCore
64.14% <ø> (ø)

Amplify
48.10% <ø> (ø)

Analytics_plugin_unit_test
81.16% <ø> (ø)

Auth_plugin_unit_test
78.99% <100.00%> (-0.05%)
:arrow_down:

CoreMLPredictions_plugin_unit_test
59.44% <ø> (ø)

DataStore_plugin_unit_test
81.59% <ø> (+0.08%)
:arrow_up:

Geo_plugin_unit_test
70.75% <ø> (ø)

Logging_plugin_unit_test
62.87% <ø> (ø)

Predictions_plugin_unit_test
37.16% <ø> (ø)

PushNotifications_plugin_unit_test
87.13% <ø> (ø)

Storage_plugin_unit_test
77.51% <ø> (ø)

unit_tests
68.11% <100.00%> (+<0.01%)
:arrow_up:

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

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Please fix mypy issues

When running mypy on my code it fails due to azure storage blob.
The error is
c:\repos\trading_analytics\fumo-engine\.venv\lib\site-packages\azure\storage\blob\_serialize.py:129: error: Type signature has too many arguments
c:\repos\trading_analytics\fumo-engine\.venv\lib\site-packages\azure\storage\blob\_blob_client.py:1407: error: Type signature has too few arguments
c:\repos\trading_analytics\fumo-engine\.venv\lib\site-packages\azure\storage\blob\aio\_blob_client_async.py:808: error: Type signature has too few arguments

Please fix. Thanks

@MarcSkovMadsen
In your mypy.ini you can specify ignoring by modules:
[mypy-tests.*]
ignore_errors = True

Thanks for trying to help @Santhoshkumard11
I've added the below to my pyproject.toml, but it does not change anything.

Ok. Changed to

I still would suggest fixing the underlying issue though. This is only a temporary workaround.

@MarcSkovMadsen Yes, will do.

Ok. Changed to

I still would suggest fixing the underlying issue though. This is only a temporary workaround.

This didn't work for me, but adding a mypy.ini file with the following contents did...
[mypy-azure.*]
ignore_errors = true


⚠ Bofrost.nl has degraded performance

In 03a30d0, Bofrost.nl (https://www.bofrost.nl) experienced degraded performance:

HTTP code: 200
Response time: 1387 ms

Resolved: Bofrost.nl performance has improved in 797a068.


FATAL:  --dbname requires a value (on macOS)

Hi guys,
following the tutorial for postgres on macOS and when trying to deploy the flipr_test schema i get the following error:
> sqitch deploy db:pg:flipr_test
Adding registry tables to db:pg:flipr_test
2018-02-26 00:30:24.869 GMT [41666] FATAL:  --dbname requires a value
"/usr/local/bin/postgres" unexpectedly returned exit value 1

~/.sqitch.conf
[engine "pg"]
	client = "/usr/local/bin/postgres"
[user]
    name = me
	email =<EMAIL_ADDRESS>
~/sqitch/.sqitch.conf
[core]
	engine = pg
	# plan_file = sqitch.plan
	# top_dir = .
# [engine "pg"]
	# target = db:pg:
	# registry = sqitch
	# client = psql

postgres
> /usr/local/bin/postgres --version
postgres (PostgreSQL) 10.2

sqitch.plan
> cat sqitch.plan
%syntax-version=1.0.0
%project=flipr
%uri=https://github.com/me/demo-sqitch/

appschema 2018-02-26T00:28:12Z john<EMAIL_ADDRESS># Add schema for all flipr objects.

Am i missing something?

Closing in favor of responding to your mail list posting.


[DOCS] Add breaking changes + RNs for 8.0.0-alpha1

Changes:

Adds breaking changes for 8.0.
Adds release notes for the 8.0.0-alpha1 release. Based on https://github.com/elastic/elasticsearch-hadoop/pulls?page=2&q=is%3Apr+label%3Av8.0.0+is%3Aclosed+-label%3Anon-issue+-label%3A>docs+-label%3Abackport.
Removes RNs for the 7.x releases.
Removes non-issue and docs issues from the RNs template. We typically don't include these type of issues/PRs in other RNs.

Thanks @jbaiera!


[S3] Allow configuring AWS SDK's logging level

Allows configuring the AWS CPP SDK's logging level correctly through the env variable AWS_LOG_LEVEL. This helps suppress verbose logs and allows access to debugging logs in the case of issues.
The current behavior takes in the TF log level and passes that along to the SDK. That has a few limitations. The logging levels don't map directly between AWS SDK (trace/debug/info/warning/error/fatal/off) and TF (info/warn/error). By passing TF level to SDK, we can never enable Debug and Trace.
Setting the AWS SDK's log level to Fatal by default. This is because in the regular flow of TF operations, many safe errors are seen. These confuse users into thinking their program is failing. Setting this to FATAL suppresses them.
In addition to the above, this PR adds VLOG statements helpful for debugging S3 issues.

@rahul003 Can you please resolve conflicts? Thanks!

@gbaned Fixed the conflict, please take a look

Both the test failures are from unrelated changes. I know one has been fixed on master. Other probably hasn't. I'm not sure.

Can you solve conflicts please?

@mihaimaruseac Please check

Removed the trailing whitespace

Can you take a look at the build failures please? Probably resync to master and run them again?

Failures seemed unrelated to the PR. Pulled from master


Feature/twitter

Update library for twitter.
Merge after Twitter goes live.

Let me know when, then I will merge this, raise version and release.

@EricSmekens This merge request is ready to be merged!


Feature/pex

Preliminary support for net-name annotation based device terminal recognition.
RemoveDuplicates now has an object called subinsts which stores instances in the form:
{ instance1name : { pin1name : {slr1, slr2 ... slrn},                                 pin2name : {slr1, slr2 ... slrn} },    instance2name : { pin1name : {slr1, slr2 ... slrn},                                 pin2name : {slr1, slr2 ... slrn} } }
There is no checking of these instance / pin names against schematic yet.
In addition, net names are now propagated down all the way to the edge of the connectivity stack (V0)

Ready for review & merge. Will work on LVS & device PEX on separate branch.


Added a skip_validation to speed up user/group/computer creation.

When creating a lot of users, groups, or computers, you only need to
validate the create location's existence once. After that, re-validating
on each create just wastes time and bandwidth.
This adds an option to skip that validation.

@TrinityDevelopers fyi - i thought you might want to use this. if you create a lot of users/groups, or just know that the location exists at the time of running a script, you can use this option to speed things up


Fix grammer in the open match demo script.

I created this PR against the release branch, but if it makes more sense to do it against master and cherry pick into the release branch let me know.

Please don't submit this yet until https://github.com/GoogleCloudPlatform/open-match/pull/295 goes in. There's conflicts.


Resolve authentication issues*

A small but significant number of students have issues with finding a free port when authenticating.

I don't know how to reproduce this issue, so I'm not 100% sure if this PR will help, although the student that provided the above screenshot was able to find an open port with s.bind(('localhost', 0)).
I'm also not sure if looking for an open port is always necessary -- it seems that this should only be happening when authentication actually happens.

A couple of things:

Have you verified that this doesn't break intended behavior?

This can run into race conditions where the student runs two OK sessions simultaneously. Session1 might pick portA. Session2 might then also pick portA. Then Session1 authenticates with portA. Session2 is then unable to authenticate with portA because it's already being used.
This problem seems unlikely (not sure if socket.bind picks ports uniformly at random), and it looks like the old solution would have suffered from it as well, so it's not a big deal to fix this.

Otherwise, LGTM.

Yep, I ran ok --authenticate and everything seemed to work as usual.
There's definitely a chance of that happening, although the bottom of this random website would seem to indicate that 0 would actually be a better thing to do here, at least on Linux.

...at least on Linux.

When a student runs OK on a Windows machine, we should print out "Use at your own risk!"
LGTM. Feel free to merge.

Doing some digging around, it looks like the code is equivalent- asking for a TCP port 0 is asking the system to dynamically allocate an unused port, which is what I was doing anyway. I don't think the Windows error is necessary.
Either way, LGTM. Nice catch!

I was joking about the Windows error :)

Interestingly, running s.bind(('localhost', 0)) interactively and then python3 ok --submit worked for the student. (Although they could be unrelated.) Thanks for the reviews!


fix: don't delete an existing conflist (#2115)

Reason for Change:
Backporting https://github.com/Azure/azure-container-networking/pull/2115 into release/v1.4.44 branch
Requirements:

[x] uses conventional commit messages

[ ] includes documentation
[x] adds unit tests
[x] relevant PR labels added

Notes:

Merged because CI mostly passed except for AKS-Engine tests, which are expected to fail at this point https://msazure.visualstudio.com/One/_build/results?buildId=78817067&view=results


Lay down starting pose

ocation? mini_ros\src\mini_ros\teleop.cpp
Example: Line 62 - Switch Trigger: Button A (having a different button control lay down / stand up)
Idea: Would it be possible to add another button command to direct spot to lay down (the positions are in the teensy code already - but would it be possible to transition from a standing state to a laying down state through a controller button press?  (similar to the BD spot) spot mini could start laying down and stand up on controller button press.

That's a great idea, and it'll make shutdown a lot easier too! I'll start working on this now.


Enforce single instance pool for all types except worker

Is this a BUG REPORT or FEATURE REQUEST?:
/kind bug
What happened: I can create multiple master/etcd/basition/vaul/jenkins instance pools in a single cluster. This doesn't make sense
What you expected to happen: Tarmak should error early (not just due to terraform templating) when creating multiple of the above instance pools
How to reproduce it (as minimally and precisely as possible): create multiple of any of the above instance pools

I would argue it makes sense to allow multiple masters/workers

@simonswine what sort of use cases? Just having different sizes of master?


0.10.0 Release

See RELEASES.md for detailed release notes.

Not yet published, would like to land the following first:

[ ] #490

Published but had to do some fuckery with dev-dependencies... will clean it up in the followup


Cannot load audio from pathlib.Path

🐛 Describe the bug
Running the following:
import torchaudio
from pathlib import Path

test_audio_path = Path('test.wav')
torchaudio.load(test_audio_path)

Produces the following error:
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/Users/pinea/miniconda3/envs/EveryVoice/lib/python3.10/site-packages/torchaudio/_backend/utils.py", line 203, in load
    return backend.load(uri, frame_offset, num_frames, normalize, channels_first, format, buffer_size)
  File "/Users/pinea/miniconda3/envs/EveryVoice/lib/python3.10/site-packages/torchaudio/_backend/sox.py", line 41, in load
    ret = torch.ops.torchaudio.sox_io_load_audio_file(
  File "/Users/pinea/miniconda3/envs/EveryVoice/lib/python3.10/site-packages/torch/_ops.py", line 692, in __call__
    return self._op(*args, **kwargs or {})
RuntimeError: torchaudio::sox_io_load_audio_file() Expected a value of type 'str' for argument '_0' but instead found type 'PosixPath'.
Position: 0
Value: PosixPath('test.wav')
Declaration: torchaudio::sox_io_load_audio_file(str _0, int? _1, int? _2, bool? _3, bool? _4, str? _5) -> (Tensor _0, int _1)
Cast error details: Unable to cast Python instance of type <class 'pathlib.PosixPath'> to C++ type '?' (#define PYBIND11_DETAILED_ERROR_MESSAGES or compile in debug mode for details)

But my understanding from the torchaudio.load type signature is that a pathlib.Path should be accepted here.
Versions
PyTorch version: 2.1.0
Is debug build: False
CUDA used to build PyTorch: None
ROCM used to build PyTorch: N/A
OS: macOS 12.5.1 (arm64)
GCC version: Could not collect
Clang version: 14.0.0 (clang-14<IP_ADDRESS>)
CMake version: Could not collect
Libc version: N/A
Python version: 3.10.13 (main, Sep 11 2023, 08:16:02) [Clang 14.0.6 ] (64-bit runtime)
Python platform: macOS-12.5.1-arm64-arm-64bit
Is CUDA available: False
CUDA runtime version: No CUDA
CUDA_MODULE_LOADING set to: N/A
GPU models and configuration: No CUDA
Nvidia driver version: No CUDA
cuDNN version: No CUDA
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: True
CPU:
Apple M1 Pro
Versions of relevant libraries:
[pip3] flake8==7.0.0
[pip3] mypy==1.8.0
[pip3] mypy-extensions==1.0.0
[pip3] numpy==1.26.4
[pip3] pytorch-lightning==2.2.0.post0
[pip3] torch==2.1.0
[pip3] torchaudio==2.1.0
[pip3] torchinfo==1.8.0
[pip3] torchmetrics==1.3.1
[conda] numpy                     1.26.4                   pypi_0    pypi
[conda] pytorch-lightning         2.2.0.post0              pypi_0    pypi
[conda] torch                     2.1.0                    pypi_0    pypi
[conda] torchaudio                2.1.0                    pypi_0    pypi
[conda] torchinfo                 1.8.0                    pypi_0    pypi
[conda] torchmetrics              1.3.1                    pypi_0    pypi

Hi @roedoejet,
The sox backend does not support file-like objects, which has been stated in the documentation.
https://pytorch.org/audio/2.1.0/torchaudio.html
Would recommend you use either ffmpeg or soundfile as the backend.


Navigation To Any Step

How can we navigate to any step i.e. independent from other.
If there is 5 steps, so how can I jump direct to step 3 from step 1 without navigating step 2.

First of all, sorry for the immense delay in my response; after a long period of abandonment it is only recently that I have found the time to work on this library again.
Regarding the issue, this functionality is now implemented in the new version of the library, so please go check it out if you are still interested.


Implement content transmission on AlexandriaNetworkAPI

replaces #165
What was wrong?
We need high level APIs for retrieving content in Alexandria
How was it fixed?
Implemented AlexandriaNetworkAPI.get_content_proof and AlexandriaNetworkAPI.get_content_from_nodes
Cute Animal Picture

Where does this stand after https://github.com/ethereum/ddht/pull/215?

This has been rebased and should be ready for review

test failure is unrelated.


worldenvironment glow not work properly

Godot version
4.0.3
System information
linux
Issue description
Currently, this only been tested in 4.0.3, but should be the same in 4.1+
from what I have told before, HDR threshold can prevent any node which raw number is under the threshold to glow, and only let the one who raw number is above  the threshold to glow.
But in 4.0.3, I cannot replicated that. higher raw number with higher threshold, you need more glow strength to make the glow work, but it also make node that under the threshold glow as well.
And sometimes the object will only glow in inspector, but not in game, at least not visible,  you can't tell it has glow.
Steps to reproduce
add 2 line2d
add world environment and setup glow property(increase threshold ), adjust glow strength
change one of the line2d raw color higher than threshold
Minimal reproduction project
test.zip

Thanks for the report! Consolidating in https://github.com/godotengine/godot/issues/62110.


ARROW-12827: [C++] Improve error message for dataset discovery failure

This adds a bit more context to the error messages, though maybe this is a bit wordy?
>>> ds.dataset('dataset4', format="ipc")
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/lidavidm/Code/upstream/arrow-12827/python/pyarrow/dataset.py", line 655, in dataset
    return _filesystem_dataset(source, **kwargs)
  File "/home/lidavidm/Code/upstream/arrow-12827/python/pyarrow/dataset.py", line 410, in _filesystem_dataset
    return factory.finish(schema)
  File "pyarrow/_dataset.pyx", line 2262, in pyarrow._dataset.DatasetFactory.finish
    return Dataset.wrap(GetResultValue(result))
  File "pyarrow/error.pxi", line 141, in pyarrow.lib.pyarrow_internal_check_status
    return check_status(status)
  File "pyarrow/error.pxi", line 97, in pyarrow.lib.check_status
    raise ArrowInvalid(message)
pyarrow.lib.ArrowInvalid: Error creating dataset. Could not read schema from 'dataset4/foo.parquet': Could not open IPC input source 'dataset4/foo.parquet': File is too small: 9. Is this a 'ipc' file?
>>> ds.dataset('dataset5', format="parquet")
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/lidavidm/Code/upstream/arrow-12827/python/pyarrow/dataset.py", line 655, in dataset
    return _filesystem_dataset(source, **kwargs)
  File "/home/lidavidm/Code/upstream/arrow-12827/python/pyarrow/dataset.py", line 410, in _filesystem_dataset
    return factory.finish(schema)
  File "pyarrow/_dataset.pyx", line 2262, in pyarrow._dataset.DatasetFactory.finish
    return Dataset.wrap(GetResultValue(result))
  File "pyarrow/error.pxi", line 141, in pyarrow.lib.pyarrow_internal_check_status
    return check_status(status)
  File "pyarrow/error.pxi", line 112, in pyarrow.lib.check_status
    raise IOError(message)
OSError: Error creating dataset. Could not read schema from 'dataset5/foo.parquet': Could not open Parquet input source 'dataset5/foo.parquet': Invalid: Parquet magic bytes not found in footer. Either the file is corrupted or this is not a parquet file.. Is this a 'parquet' file?

I think the "Is this a XYZ file?" is actually quite useful, and not too verbose. Because it's something easy to get when reading a non-parquet file and you forget to specify the format (the default is "parquet", and not to infer it from the file, as users might expect)
This relates to a PR @thisisnic did for improving this error message on the R side -> https://github.com/apache/arrow/pull/10326 (this PR might cover the custom handling you added in R?)

I think the "Is this a XYZ file?" is actually quite useful, and not too verbose

Of course the "Could not open Parquet input source" part also already gives a hint for that

This is even more wordy, but perhaps If reading a different format than 'Parquet', pass the intended format to the dataset/factory?

I think the "Is this a XYZ file?" conveys the information quite clearly (and invites the user to check).

Alright, I added back the 'Is this a XYZ file' message.

Is everyone happy with the error message here? :slightly_smiling_face:


next_action labels in board view

Hi,
when using a board, sections are turned into columns. Working on an item will move it to the next column without necessarily finishing it. Iiuc autodoist marks the first item in the list (leftmost column) as next_item. This leads to me having many next_item labels in this project.
Would it be possible to

remove that label if the task is not topmost in the column (first section)?
and maybe not have it at all in the rightmost column (usually done)?

If there is no plan to support the board view, please let me know (I like the board view but if I have to chose I'll prefer autodoist :) )

maybe fixed with https://github.com/Hoffelhas/autodoist/pull/21

also #22 fixes an interesting case when the "next" card has bee ignored due to being in the future ;-)

Hi there, sorry it took a while to get back at you.
Something like this is possible in v2.0.0 that will be released soon. You could do either of two things:

Specify that a section should be labelled sequentially by using '-'  in each section name, except for the last 'done' section.
If you have many sections, you could simply specify '=-' in the project name, such that all sections in parallel are labelled sequentially each. Labelling for the 'done' section can then be ignored by using '*' either at the start or end of its name.

If you have any more questions, feel free to reopen this thread. For now I will close it.


Parts of site "refused to connect"

Various containers have this issue, and it appears to affect pop-ups, iframes, etc: "sub.domain.com refused to connect"
Screenshot here: https://pasteboard.co/Ih0hI6j.png
I am using V1.7.11 via docker.
My toml is below. How can I fix this issue?
#debug = true

logLevel = "INFO" #DEBUG, INFO, WARN, ERROR, FATAL, PANIC
InsecureSkipVerify = true
defaultEntryPoints = ["https", "http"]

[traefikLog]
  filePath = "/etc/traefik/traefik.log"
  format   = "json"

[accessLog]
  filePath = "/etc/traefik/access.log"
  format = "json"

# WEB interface of Traefik - it will show web page with overview of frontend and backend configurations
[api]
  entryPoint = "traefik"
  dashboard = true
  address = ":8080"
  usersFile = "/shared/.htpasswd"

# Force HTTPS
[entryPoints]
  [entryPoints.http]
  address = ":80"
    [entryPoints.http.redirect]
    entryPoint = "https"
  [entryPoints.https]
  address = ":443"
    [entryPoints.https.tls]

[file]
  watch = true
  filename = "/etc/traefik/rules.toml"

# Let's encrypt configuration
[acme]
email =<EMAIL_ADDRESS>#any email id will work
storage="/etc/traefik/acme/acme.json"
entryPoint = "https"
acmeLogging=true
onDemand = false #create certificate when container is created
[acme.dnsChallenge]
  provider = "cloudflare"
  delayBeforeCheck = 0
[[acme.domains]]
   main = "domain.com"
[[acme.domains]]
   main = "*.comain.com"
[[acme.domains]]
   main = "*.files.domain.com"
[[acme.domains]]
   main = "*.transmission.domain.com"
# Connection to docker host system (docker.sock)
[docker]
endpoint = "unix:///var/run/docker.sock"
domain = "domain.com"
watch = true
# This will hide all docker containers that don't have explicitly
# set label to "enable"
exposedbydefault = false

I may have found an answer, after trial and Error. Can anyone confirm if this is the complete fix?
      - "traefik.frontend.passHostHeader:true"
      - "traefik.frontend.headers.customFrameOptionsValue=ALLOW-FROM https://www2.${DOMAINNAME}"


[coc.nvim] svelte not supported by prettier

is there any way to make prettier work with Svelte, cause Svelte file is considered as simple HTML file

Would also love to see this

Should be fixed on new release.

Your have to install svelte plugin for prettier and install it with your local prettier.


update shiki

the latest shiki is 0.9.x

Hi @Enter-tainer,
I’m checking in to let you know that I’ll tackle this as part of bringing shiki-latex into Shiki’s monorepo. I’ll get to this in the near future.


Some pages can't be found

Technology  page

wiki/foundation#/projects/foundation

source file : https://github.com/threefoldfoundation/info_foundation/blob/development/docs/projects/threefoldfoundation.md
wiki/foundation#/projects/freeflownation
wiki/foundation#/projects/harvested
wiki/foundation#/projects/nbhdigital

/wiki/foundation#/projects/openchat

Please make sure the problem is in our wiki lapis app, docsify, loading...etc, not the content.

For Technology page, we do not load tech wiki by default, @andrewayoub do we need to load it by default?

For wiki/foundation#/projects/foundation, this is a content problem, no document called foundation.md (not as you mentioned threefoldfoundation.md) inside projects folder.

For wiki/foundation#/projects/freeflownation, this file is empty!

For wiki/foundation#/projects/harvested , the file harvested.md is not found here.

For wiki/foundation#/projects/nbhdigital, the file nbhdigital.md is not found here.

For now, we load wiki from master branch as default, so when checking the content, make sure to check master branch.


Add a basic local proofreader

Interface looks good, but adding a basic local proofreader that can be overridden would make this package immediately useful on install.

@asontha Do you have an example using a local proofreader?

I created a local proofreader. It works but the word list is too short. Here is the word list I used. https://github.com/dwyl/english-words/blob/master/words_dictionary.json
interface WordList {
  [word: string]: number;
}

class Proofreader implements IProofreaderInterface {
  private wordList: WordList;

  constructor(wordListJson: WordList) {
      this.wordList = wordListJson;
  }

  async proofreadText(sentence: string): Promise<ITextWithPosition[]> {
      const wordsWithPosition: ITextWithPosition[] = [];
      let currentOffset = 0;

      const words = sentence.split(/\W+/);
      for (const word of words) {
          const lowerWord = word.toLowerCase().trim();
          const length = word.length;
          if (!this.wordList[lowerWord] && lowerWord !== "") {
              wordsWithPosition.push({
                  offset: currentOffset,
                  length,
                  word,
              });
          }
          currentOffset += length + 1; // +1 for the space after each word
      }

      return wordsWithPosition;
  }

  async getSuggestions(word: string): Promise<string[]> {
      // Example: just return similar words by replacing one character
      const suggestions: string[] = [];
      const alphabet = 'abcdefghijklmnopqrstuvwxyz';

      for (let i = 0; i < word.length; i++) {
          for (const char of alphabet) {
              const newWord = word.slice(0, i) + char + word.slice(i + 1);
              if (this.wordList[newWord]) {
                  suggestions.push(newWord);
              }
          }
      }

      return suggestions;
  }

  normalizeTextForLanguage(text: string): string {
      // You can implement language-specific text normalization here
      // For simplicity, let's just convert to lowercase
      return text.toLowerCase();
  }
}

SpellcheckerExtension.configure({
    proofreader: new Proofreader(wordListJson as WordList),
    uiStrings: {
      noSuggestions: "No suggestions found",
    },
  }),

I added two demo implementations in the demo folder.
One of them is yours, @bryanjtc. Thank you for providing it.


5.3 localization

Simple localization out of the box for Laravel 5.3
Part of https://github.com/laravel/internals/issues/2

Please release as a package.

@taylorotwell there are already some packages for this but they don't offer standartized simple solution and package can't change the behaviour of core.
It also was discussed many times and even in slack you told that PR could be acceptable if it would be simple.
From laravel website https://laravel.com/docs/5.1/localization

Laravel's localization features provide a convenient way to retrieve strings in various languages, allowing you to easily support multiple languages within your application.

Unfortunetaley this is not real. For years supporting multiple languages within app was never so easy. Laravel also has translation features but they are useless without any ability to use them without writing custom core code and injecting custom components.
Any modern application requires localization out of the box.
This package also renames lang folders to locales and en to en_US to make it clear because I agree wtih @sisve that working with locales is much simplier.

This isn't simple. There isn't even a description of how it works in the description. It's just a bunch of code with the label "simple localization".

@taylorotwell  All what this small extension to Laravel core does:

Ability to specify additional locales in app config
App locale, PHP locale and Carbon locale ar set automatically by LocaleServiceProvider which also gives freedom to add or remove any cusotm localization logic
1st URL segment containing locale slug is added automatically when using url(), redirect(), etc.
New helper trans_url() to change locale slug in URL if required
Option in app config to enable/disable default en_US presence in URL, which is disabled by default so no breaking changes at all.
Detects user agent's preffered language.

It does not contain route or model localization or anything else.
Main problem is because of this small function it is required to extend and inject Application, Request and UrlGenerator at least.
Please also take into account how many comments and upvotes this discussion has https://github.com/laravel/internals/issues/2 Everything is described there in details.

I will try to review this again this week but can not make any promises of it being merged.

I will try to review this again this week but can not make any promises of it being merged.

Of course, I also prefer code review and making everything perfect before release and probably there are still something to improve. If you will have any questions just PM me on slack or #internals (same user name: mevrael)
The idea and use case is very simple - Install new laravel app, add, for example, de_DE to additional locales and that's all, you can see same Laravel welcome page at laravelapp.dev/de-de, just add new de_DE lang folder and start translating, Carbon's diffForHumans() also will return in de_DE.


Testimonial Read more content

this content will populate with more info about the student and their needs and how we helped them

the content is basically done, once I get more recent statements and images from my current students I will update that


Exporters should be plural in docs

This change added exporters: https://github.com/spring-cloud-incubator/spring-cloud-sleuth-otel/commit/0042954d552b9428b90f11df91305392e52283c6
But it has it singular: "exporter".
Mavencentral has it plural: https://search.maven.org/artifact/io.opentelemetry/opentelemetry-exporters-zipkin/0.9.1/jar

That is not the correct library. See here: https://search.maven.org/artifact/io.opentelemetry/opentelemetry-exporter-zipkin/1.1.0/jar


Compiler crash when using crystal tool implementations --cursor

Input Source Code
class Foo(T)
  def value
    puts {{ T.methods.any? {|el| el == "to_u64".id} }}
  end
end

puts {{ Int32.methods.any? {|el| el == "foo".id} }}

a = Foo(Int32).new
a.value

Command
crystal tool implementations --cursor src/b.cr:9:16 src/b.cr

Expected
Print of path and line+column where the implementation is found.
Observed
Nil assertion failed
[4406852] ???
[4611021] ???
[11459740] ???
[11155427] ???
[10947929] ???
[4404578] ???
[10940341] ???
[140364077276869] __libc_start_main +245
[4387505] ???

Error: you've found a bug in the Crystal compiler. Please open an issue, including source code that will allow us to reproduce the bug: https://github.com/manastech/crystal/issues

The implementations tool does not map new to initialize (yet).
New methods are generated by the compiler to perform alloc + initialize when they are not present already.
class Foo
end

Foo.new

crystal tool implementations --cursor file.cr:4:6 file.cr
Also triggers this issue.

Update on this: @bcardiff's example works correctly on 0.22. I'm leaving this open because the original sample still fails, probably related to Foo being a generic class.

In Crystal 0.31.1 the printed info is better now, but it still says it's a bug in compiler and doesn't show  path the line+column where the implementation is found as expected.
$ crystal tool implementations --cursor src/b.cr:9:16 src/b.cr
Nil assertion failed (NilAssertionError)
  from Nil#not_nil!:NoReturn
  from Crystal::ASTNode+@Crystal::ASTNode#accept<Crystal::ImplementationsVisitor>:Nil
  from Crystal::ASTNode+@Crystal::ASTNode#accept<Crystal::ImplementationsVisitor>:Nil
  from Crystal::Command#tool:(Bool | Nil)
  from Crystal::Command#run:(Bool | Crystal::Compiler::Result | Nil)
  from __crystal_main
  from main
Error: you've found a bug in the Crystal compiler. Please open an issue, including source code that will allow us to reproduce the bug: https://github.com/crystal-lang/crystal/issues

Seems to no longer crash with 1.3.2
$ crystal tool implementations --cursor src/b.cr:9:16 src/b.cr
1 implementation found
/opt/homebrew/Cellar/crystal/1.3.2/src/primitives.cr:36:1


Add build-backend="setuptools.build_meta" in cvxpy pyproject.toml

Describe the bug
My organization deploys applications using virtualenv with --system-site-packages. I am hitting an error while installing an application which uses cvxpy. The error is:
AttributeError: module 'setuptools.build_meta' has no attribute 'legacy'
The issue is described at https://github.com/pypa/setuptools/issues/1694, however a later version of setuptools also does not fix it for cvxpy. Apparently a solution is to add
build-backend="setuptools.build_meta" in pyproject.toml file - which I see is missing for cvxpy. Could you please consider adding this?

CVXPY Version: All

Ok I made the requested change.

Steve, do you know when a next release is scheduled?

We decided in the dev channel to roll back this change. @ash0707 the desired change is present in version 1.1.14, but will rolled back in 1.1.15.


dev-guide: document using range_end for prefixes with json

Lack of a range_end example has caused some confusion.

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@1010b82). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master    #8245   +/-   ##
=========================================
  Coverage          ?   76.27%
=========================================
  Files             ?      346
  Lines             ?    26993
  Branches          ?        0
=========================================
  Hits              ?    20588
  Misses            ?     4924
  Partials          ?     1481

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 1010b82...da2f4bb. Read the comment docs.


Service discovery for published services

expectations
Is there any way to discover public ip/domain names of published services (publish-scope port in acorn word)?
Or to know in advance before the deployment?
use cases
Typical use cases are as follows:

web/api services can have whitelisted listening address configuration.
clustering applications should register its advertising address in their own internal service/member discovery table.
Without such a discovery function, we need to deploy acorn app and fetch the public address assigned and update the app again.

suggestions

If we can set load balancer ip or domain name in port definition in Acornfile and then Acorn consumes that address to publish the port
If we can fetch fields of acorn objects by using template variables, we can use that inside the other object, for instnace, container["web"].port["api"].public_address. if needed, we can mount and run custom shell scripts inside the container to wait till that field is assigned to the object.

This is at least partially linked to https://github.com/acorn-io/acorn/issues/725

Are you sure you want the public? If this is acorn-to-acorn traffix within the same cluster, I would assume you don't want to go out through the public internets

Are you sure you want the public? If this is acorn-to-acorn traffix within the same cluster, I would assume you don't want to go out through the public internets

I would argue that we should consider consumer running outside of the listener acorn app's k8s cluster, in such cases;

consumer runs as acorn app but on a different k8s cluster
consumer runs on other platform other than k8s, for instance, ML jobs running on aws sagemaker

Generally agree, just wanted to make sure I understood your use case before offering a response. Though, I don't think the clustered applications like etcd or redis being cross-cluster is a good idea. Haven't seen that work out well.
Nevertheless, you reminded me that I needed to open this issue: https://github.com/acorn-io/acorn/issues/733, which I think will at least partially address this.

As I mentioned in the usecases, I didn't consider clustered applications running across multiple clusters.

I don't see that explicitly anywhere in the usecases, but ok.
So then you don't want the "public ip address" for that use case, right? You want an internal IP or dns name?

Either public ip or dns is fine. I just want to know public endpoint in advance so it can be configured in acornfile.
Btw, I think  tcp endpoints are only exposed as IP now.

putting this in the bucket related to @ibuildthecloud's service work


Please cherry-pick , fix glitch mode longs trip

Steps to reproduce
https://github.com/Saud-97/TachiyomiS97/commit/9eab2bc694a6b76124f08dcf74ca4380606548ed
Expected behavior
Increased page split height to reduce flickering line issue in Webtoo…
…n reader
Actual behavior
.
Crash logs
.
Yōkai version
1.7.12(yokai)
Android version
Android 11
Device
Realme 7i
Other details
.
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open issue.
[X] I have written a short but informative title.
[X] If this is an issue with an extension, or a request for an extension, I should be contacting the extensions repository's maintainer/support for help.
[X] I am reporting an issue exclusive to this fork. I have also checked that is not an issue on the main version of Mihon
[X] I have tried the troubleshooting guide.
[X] I have updated the app to version 1.7.12.
[X] I have updated all installed extensions.
[ ] I have admitted that I am a clown by having checked this box, as I have not read these acknowledgements.
[X] I have filled out all of the requested information in this form.

I'm a bit hesitant to do this due to the maintainer's bad rep, but what could possibly go wrong eh? It's just one line of code anyway...


Unapplied effect on Explorer first startup and Titlebar after

Describe the bug
I'm sorry if it is, I don't know if this bug is caused by Windows.
When I first open Explorer, the Mica effect is not properly applied; it is just a blank Mica effect instead of one based on what is behind the window. When I un-focus the window or maximize/minimize it, then the correct Mica effect is applied, but then another bug occurs: The Titlebar goes back to the default titlebar.
To Reproduce
Steps to reproduce the behavior:

Go to taskbar or start menu
Click on File Explorer
See incorrectly applied Mica effect
Minimize (you can restore right after), maximize, or un-focus window
Observe: The effect now works properly within the window area, but the Titlebar is now back to the default None-effect.

Expected behavior
The Mica Effect to be properly applied when Explorer first opens.
The Titlebar to keep the Mica effect all the time Explorer is focused on.
Screenshots
When Explorer is first opened:

After un-focused:

Maximized to show Mica works in Window Area:

Windows Version
Windows 11 Build 22621.2283 (Non-Insider)
and
Windows 11 Build 22631.2338 (Beta Channel)
Additional context
StartAllBack is also installed: Win11 Command bar, Mica effect on top enabled (no difference between on/off), Colorize everything disabled

Mica isn't supposed to show the windows behind it, only the part of the wallpaper that the window covers.

That's nice to know, however you can tell through the screenshots that Mica isn't showing anything behind it (windows or wallpaper) when it first starts up. But I mean I do understand that this issue will likely go unresolved since it requires code that could easily be broken by a Microsoft Update.
Also I did try ExplorerFrame (since I already had it from my Acrylic days), but it just changes the window to use Acrylic instead so not the solution I want.
It does apply it on a newly created window though, so I might look at making a fork for Mica effect instead of Acrylic

Might be that you have the Explorer rule set to Acrylic/Blur Behind? ExplorerFrame doesn't affect those.

I did have Blur Behind on. Explorer frame now doesn't  change to acrylic, and Mica does work, but after I maximize or minimize/restore the window. Without Explorer frame or blur behind mica doesn't work.

I restarted to try to make it startup asap, and it works but it's inconsistent. Sometimes it works and is the Mica effect with the black background and titlebar, and sometimes it's not applied; in which case it will become the gray Mica after max or min/restoring the window.
I do have to say, now that the Mica effect works properly (black titlebar) it does look good. I'm not sure why it's inconsistent, consolewindowclass and global don't change the end result (of inconsistency)

As a possible cause, The effect applied when it doesn't initially work is the same as Enabling "Extend Frame into Client Area", and when it is enabled it never fails (at least with explorerframe).


neo-tree: fix window.mappings

In current code, filesystem.window.mappings, when set, became filesystem.window.mappings.mappings.
document_symbol can also receive its own custom mappings.

I prefered the solution in #725 (sorry for taking too long to review this one). Though that PR does not handle the document_symbol mappings, so if you could rebase only including that?
Though you need to add the window processing in the document_symbol = { ... } part of the file (around line 1206), see other windows

Done

You still to add the processing to the setup options (see around line 1200 of the file, and other window options)


Remove eLanguageFlag which is not used anywhere

@swift-ci test

Seems like it's only unused in upstream-with-swift and the thing was introduced in some swift-only clang refactoring in 5f3aa16203d308773108c4d03ed4d4ec8e4a47c2

We should see whether we can get rid of that.

Yeah, it seems that was done to kind of allow some form of unified setting thing between Clang and Swift. Working on it.


Name with spaces

When connecting to the server you can have your name have spaces within it. That shouldn't be possible.

fixed in new beta


Plugins list ?

Excuse me, is there any plugins list for GORM?
If no, may be we will create it?

I created wiki page with plugin list for GORM. Hope, it will useful.


Update tags

Can you please update tags number so it's easier to track bugs per release

Done! I'm going to be more diligent about this now


benchmarking datasets

Hi, thanks for the great benchmarking studies. I am wondering whether the collected real benchmarking datasets are available somewhere. If not, could you please kindly share me the lung dataset ''Lung_atlas_full.h5ad'' so that I can run your preprocessing pipeline here? Thank you so much!

Hi @sqjin,
Thanks for the compliment! The datasets are now available on Figshare (except mouse brain so far, as it takes quite some time to upload). You can find them here: https://figshare.com/articles/dataset/Benchmarking_atlas-level_data_integration_in_single-cell_genomics_-integration_task_datasets_Immune_and_pancreas/12420968
This will be in the revised manuscript, and I will tweet about it soon as well.

@LuckyMD Thank you for making it easier to access.

Hi, I was looking to download the Lung dataset as well. On the figshare site, the raw counts are available for the drop-seq cells of the lung dataset, but cells assayed using the 10X protocol do not appear to have raw counts:
>>> rna_data = anndata.read_h5ad('data/lung_atlas/data.h5ad')
>>> rna_data = rna_data[rna_data.obs.protocol != 'drop-seq']
>>> rna_data.X.data, rna_data.layers['counts'].data
(array([0.8457227 , 0.8489592 , 0.84656495, ..., 0.8000515 , 1.2165804 ,
        0.7779638 ], dtype=float32),
 array([1.1890177, 1.1957711, 1.190773 , ..., 1.1387753, 2.2072291,
        1.0936011], dtype=float32))

I was wondering if the raw counts were available.
Thanks,
AL

Hi @AllenWLynch,
For the 10X data of the lung cell atlas we used soupX corrected counts that we got from the data generators directly. This likely represents a better version of the count data (although potentially breaking with NB noise model assumptions). If you're looking for the uncorrected raw counts, it might be good to get in touch with the authors of the Vieira-Braga et al paper directly.


ruby_3_4: 3.4.0.preview2 -> 3.4.1

https://www.ruby-lang.org/en/news/2024/12/25/ruby-3-4-0-released/
https://www.ruby-lang.org/en/news/2024/12/25/ruby-3-4-1-released/

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[x] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
25.05 Release Notes (or backporting 24.11 and 25.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

The result of  nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD" is as follows
error: build log of '/nix/store/yljdg1g7kcwrdfib1z9c3nn25f841nhg-ruby3.4-gdk3-4.2.1.drv^*' is not available
error: build log of '/nix/store/20yvpbd83slj75b5ksmx125zfddlk0dq-ruby3.4-gdk3-4.2.1' is not available
error: build log of '/nix/store/0h9i84bkdf3kc3rhz2vfslgd7zrbxf20-ruby3.4-gtk3-4.2.1.drv^*' is not available
error: build log of '/nix/store/fx3xnx13q4mg951hwilfw83mm24vqbw5-ruby3.4-gtk3-4.2.1' is not available
error: build log of '/nix/store/2x1shwr9lf51gm7q14fahmfj9jds6cmv-ruby3.4-ruby-libvirt-0.8.2.drv^*' is not available
error: build log of '/nix/store/vc8qrs15li74bfp5ghvzlv6ksgia4pw3-ruby3.4-ruby-libvirt-0.8.2' is not available
error: build log of '/nix/store/8zh7r81zqikgrpw8cpdmwgfcavfpx02r-ruby3.4-ruby-lsp-0.15.0.drv^*' is not available
error: build log of '/nix/store/arcspn7f574da405cnj2qnqck5gj2dw5-ruby3.4-ruby-lsp-0.15.0' is not available

Add a :+1: reaction to pull requests you find important.

NixOS:staging

As I understand, Ruby 3.4.0 is not yet used in another package. So sending to master branch will be better?
previous PR for similar purpose: https://github.com/NixOS/nixpkgs/pull/276648

The result of nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD" is as follows

As a rule of thumb, if you can nixpkgs-review a PR, and you do not own a supercomputer, it shouldn't target staging.

Thanks, this is fast! However, I'd agree that this should target master instead.

Ruby 3.4.1 has been released.
https://www.ruby-lang.org/en/news/2024/12/25/ruby-3-4-1-released/

This fixes the version description.

Commit added.

As I understand, ruby_3_4 is not yet used in another package.

A nixpkgs-review runs shows me that's not true. This is well over 1300 rebuilds. I guess @masoo has a spare supercomputer lying around.

supercomputer, it shouldn't target staging. staging is for changes which cause a massive amount of rebuilds.

nixpkgs-review was done on the master branch
Should I rework the pull request for the master branch?

No, leave it on staging, and do not nixpkgs-review it. There are way too many rebuilds and it'll just use your computer's resources for no good reason.

Open another PR targeting master would be the easiest solution.

There was a broken package, and I wanted to provide an explanation.
I applied nixpkgs-review to it.
If I misunderstood or overlooked any rules, I sincerely apologize.

It's not a rule, you can certainly review staging PRs if you have the computational resources, but most people don't because you're simply stressing your computer for the same result Hydra will eventually give you.

The problem here is not that one should or shouldn't nixpkgs-review staging. The commits are based on the wrong (staging) branch, and the proper solution would be cherry-pick the commits onto a branch based off master.

On the other side, this is a really good first time contrib. Congrats!

Thank you for providing the solution.
I will close this pull request and create a new one targeting the master branch.


phpExtensions.opentelemetry: 1.0.0 -> 1.0.1

Description of changes
This PR updates PHP OpenTelemetry extension to its latest version: https://github.com/open-telemetry/opentelemetry-php-instrumentation/releases/tag/1.0.1
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

@GrahamcOfBorg build phpExtensions.opentelemetry


[bshoshany-thread-pool] Updated to v3.4.0

[X] Changes comply with the maintainer guide
[X] SHA512s are updated for each updated download
[X] The "supports" clause reflects platforms that may be fixed by this new version
[X] Any fixed CI baseline entries are removed from that file.
[X] Any patches that are no longer applied are deleted from the port's directory.
[X] The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
[X] Only one version is added to each modified port's versions file.

Thanks!

@bshoshany Note: I will be converting your PR to draft status. The above suggested changes are only recommendations. If you are willing to adopt them, please click "ready for review" after making the modifications. If you do not wish to make any changes, please click "ready for review" directly. That way, I can be aware that you've responded since you can't modify the tags.

Thanks! I accepted your changes, but now it's failing a check :(

I removed the line you indicated, but it's still failing a check - although maybe I didn't understand what you wanted me to change. Perhaps we should just revert to the original version? Thanks.

@bshoshany  The CI error was reported because the SHA value is incorrect. After making the changes, you should run the command again: \vcpkg.exe x-add-version bshoshany-thread-pool --overwrite-version.

In the end I decided to just revert to my original version, since unfortunately I don't have more time to devote to this PR. I will incorporate the REF "v${VERSION}" trick next time I update the package. Thanks again :)


aio rt:route:create is not working

Doc:
https://github.com/adobe/aio-cli#aio-runtimeroutecreate-basepath-relpath-apiverb-action
Problem:
There’s no error. When the command is run the create routes, it registers and shares the full route path.
But when you hit that route, it says that it doesn’t exist.
Example:
aio runtime:route:create /producer-api /languages get getLanguagesForHostApp

Might be an Adobe I/O Runtime issue (clarifying). When you specify the basepath as the argument to aio runtime route list, you can see the apis.

Update:
aio rt route create is working. However, there'a recent change to Gateway sync inteval to 60s. APIs will be available for use after 60s as the gateway sync refreshes. .
list api should work if you put in the basepath, but doesn't seem to work if you don't put it in as an argument.

closing this issue as this is not a bug. potential improvement for list is captured at #185


Report error in UI when API calls fail

Is your feature request related to a problem? Please describe.
When calls from DIMES to api.rockarch.org fail or time out, users just see endless loading in DIMES. We've seen from several researchers in the Reading Room (and staff attempting to help them troubleshoot) that it isn't clear to users what the problem is or why the page won't load, leading them to think it may be their own browser's or computer's error.
Describe the solution you'd like
When API calls fail, display an error message alerting the user that there is a problem with the system.
The error message when the Request Broker is unavailable is: "Sorry, our system is unable to process requests right now. We're working to fix this! Please try again later." I'd recommend a similar message appear on the page for failed API calls:
"Sorry, our system is unable to retrieve the information you requested right now. We're working to fix this! Please try again later."
This would appear on every page where a failed API call would prevent the page from loading:

Agent
MyList
Records
Search

Describe alternatives you've considered
Consideration: I'm wondering if stating "We're working to fix this!" would discourage our staff users from reporting the problem?

What if we surface a more specific error message like "The request to https://api.rockarch.org/search?q=chimpanzees failed with the status code 500"? That information isn't particularly useful to an end user but it does tell them that something went wrong, and hints that maybe they should pass along the specifics of that message? I think "our system" is too vague in this context to be meaningful, and doesn't necessarily help us diagnose either.

That makes a lot of sense. How about "The request to https://api.rockarch.org/search?q=chimpanzees failed with the status code 500. To report this problem, send us an email at archive.rockarch.org."

@ctgraham would you be able to check out #537 and see if that fixes this issue?


Cava Module is causing waybar to segfault when monitors get unplugged.

What was said in the title. I noticed that when I unplugged monitors from my laptop that waybar would segfault, and after doing some research, I noticed an older issue about Cava causing this, so I removed Cava from my waybar and suddenly it isn't crashing anymore.

Hi @techyporcupine , can you please update waybar. Make sure it is used libcava-0.10.3 and check again. Please let me know about results here.
Thanks

Hi @techyporcupine , have you had a chance to check ?

Oh, I'm so sorry I was busy at the time and totally forgot. I'll try it when I get home later!

How do I change the cava version used? I'm using the latest version of the Nix flake provided from this repo, but its on 0.10.2


Make sure BlockPipeline.validate_tx handles all exceptions

resolves #989
BlockPipeline was not handling the exceptions that can occur when calling Transaction.from_dict.

Codecov Report

Merging #1148 into master will increase coverage by <.01%.

@@            Coverage Diff             @@
##           master    #1148      +/-   ##
==========================================
+ Coverage   96.86%   96.86%   +<.01%
==========================================
  Files          49       49
  Lines        2230     2234       +4
==========================================
+ Hits         2160     2164       +4
  Misses         70       70

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 46aa903...c174271. Read the comment docs.


[Select] Menu does not focus without empty option

When there is not an empty option in the Select component and the select currently does not have a value, opening the menu (via mouse or keyboard) does not focus the menu at all, which results in the Up/Down arrow keys being useless.

[x] This is not a v0.x issue.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior 🤔
I expect the up and down arrows to be usable after opening the menu when there is not an empty option and the component does not have a value.
Current Behavior 😯
I am not able to navigate through the select option via the up/down keys when the menu does not have an empty option and the component does not have a value.
Steps to Reproduce 🕹

Code Sandbox (taken from the demo pages)

Context 🔦

To keep the Select component fully accessible via keyboard.
Your Environment 🌎

Tech
Version

Material-UI
v4.1.1

React
v16.9.0

Browser
any

Duplicate of #15973


Ensure that NaNs accross all fields stay NaN

By setting min_count to 1, it requires 1 non-na number to be present to produce a value.

 New York County, NY has all zeros for current_icu and current_hospitalized


Vimeo downloads fail on MacOS ElCapitan and Sierra

Noticed an error on my ElCapitan macOS build due to an old OpenSSL system version.
Also confirmed on Sierra.
openssl version
OpenSSL 0.9.8zh 14 Jan 2016
python --version
Python 2.7.10
Vimeo downloads fail with this error message:
ERROR: Unable to download webpage: <urlopen error [SSL: TLSV1_ALERT_PROTOCOL_VERSION] tlsv1 alert protocol version (_ssl.c:590)> (caused by URLError(SSLError(1, u'[SSL: TLSV1_ALERT_PROTOCOL_VERSION] tlsv1 alert protocol version (_ssl.c:590)'),))
Is there a way to tell youtube-dl to use the latest openssl without updating it on my system?
I tried changing PATH, PYTHONHOME, PYTHONPATH environment variables to my latest OpenSSL and LibreSSL builds, but this do not seem to help.
Any advise is appreciated.  Please see a full log below:
macoscapitan:TEST capitest$ youtube-dl -v https://vimeo.com/319558357
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: [u'-v', u'https://vimeo.com/319558357']
[debug] Encodings: locale UTF-8, fs utf-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2019.03.01
[debug] Python version 2.7.10 (CPython) - Darwin-15.6.0-x86_64-i386-64bit
[debug] exe versions: none
[debug] Proxy map: {}
[vimeo] 319558357: Downloading webpage
ERROR: Unable to download webpage: <urlopen error [SSL: TLSV1_ALERT_PROTOCOL_VERSION] tlsv1 alert protocol version (_ssl.c:590)> (caused by URLError(SSLError(1, u'[SSL: TLSV1_ALERT_PROTOCOL_VERSION] tlsv1 alert protocol version (_ssl.c:590)'),))
File "./vydl/youtube_dl/extractor/common.py", line 605, in _request_webpage
return self._downloader.urlopen(url_or_request)
File "./vydl/youtube_dl/YoutubeDL.py", line 2225, in urlopen
return self._opener.open(req, timeout=self._socket_timeout)
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/urllib2.py", line 431, in open
response = self._open(req, data)
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/urllib2.py", line 449, in _open
'_open', req)
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/urllib2.py", line 409, in _call_chain
result = func(*args)
File "./vydl/youtube_dl/utils.py", line 1140, in https_open
req, **kwargs)
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/urllib2.py", line 1197, in do_open
raise URLError(err)

Outdated OpenSSL.


Add auto merge

@conda-forge-admin, please add bot automerge

@conda-forge-admin, please add bot automerge

Hi! This is the friendly automated conda-forge-webservice.
I just wanted to let you know that I added bot automerge in conda-forge/dtoolai-feedstock#2.


Pad  chord-lyrics line pairs with whitespace so they are always wrap together properly

Need example of where this can be tested