Cleanup and prepare v0.14.1

Minor Tasks

[x] Rename TestSheetRemoteSyncBase
[x] Move #1592 & #1817 under correct section in changelog
[x] Remove "todo" from samplesheets.plugins
[x] Remove reference to "sample sheets" from "No iRODS delete requests" message
[x] Unify text style in samplesheets details card "no sheets" message
[x] Add obolibrary.org URL recommendation for ontology terms in docs
[x] Clarify "editable" column config option in docs
[x] Fix Import  Ontology labels in ontologyaccess
[x] Update manual screenshot for column toggle modal
[x] Add LDAP_DEBUG to base.py

Issues to Add in CHANGELOG

[x] #1848
[x] #1849

Release Checklist

[x] Review code style and cleanup
[x] Review and update docs entries
[x] Update SODAR_API_DEFAULT_VERSION and SODAR_API_ALLOWED_VERSIONS
[x] Update Vue app version with npm version
[x] Update version in CHANGELOG and SODAR Release Notes doc
[x] Update version in docs conf.py
[x] Ensure both SODAR and SODAR Core API versioning is correct in API docs
[x] Ensure docs can be built without errors

Notes
N/A

Done.


The dimensions should be remembered when opening the file explorer again

Right now, if I open the application and change its dimensions, close it and then open it again, it goes back to its default size.

This was fixed in the latest snapshot. Thank you!


Authentication failed

HA core version
No response
Intergration version
0.3.22
Device type and model
211106240035945 (Bathroom Master)
Used App
美居
The description of problem

已获取到key及token ，连接设备提示授权失败！
The logs
No response

Hello. Authentication worked if you try the method I suggested https://github.com/georgezhao2010/midea_ac_lan/issues/497

it`s not working

又不行了，又得更新了大佬

Have any of you been able to make any progress here?
I have the same problem, but I don't understand the method of @StanislavNosov.

2024-06-02 17:19:55.619 DEBUG (MainThread) [custom_components.midea_ac_lan.midea.core.device] [210006727191360] Connecting to <IP_ADDRESS>:6444
2024-06-02 17:19:55.623 DEBUG (MainThread) [custom_components.midea_ac_lan.midea.core.device] [210006727191360] Connected
2024-06-02 17:19:55.624 DEBUG (MainThread) [custom_components.midea_ac_lan.midea.core.device] [210006727191360] Handshaking
2024-06-02 17:19:55.668 DEBUG (MainThread) [custom_components.midea_ac_lan.midea.core.device] [210006727191360] Authentication failed
2024-06-02 17:19:55.668 DEBUG (MainThread) [custom_components.midea_ac_lan.midea.core.device] [210006727191360] Status update: {'available': False}
2024-06-02 17:19:55.668 DEBUG (MainThread) [custom_components.midea_ac_lan.midea.core.device] [210006727191360] Connecting to <IP_ADDRESS>:6444
2024-06-02 17:19:55.674 DEBUG (MainThread) [custom_components.midea_ac_lan.midea.core.device] [210006727191360] Connected
2024-06-02 17:19:55.674 DEBUG (MainThread) [custom_components.midea_ac_lan.midea.core.device] [210006727191360] Handshaking
2024-06-02 17:19:55.731 DEBUG (MainThread) [custom_components.midea_ac_lan.midea.core.device] [210006727191360] Authentication failed
2024-06-02 17:19:55.731 DEBUG (MainThread) [custom_components.midea_ac_lan.midea.core.device] [210006727191360] Status update: {'available': False}
2024-06-02 17:19:55.732 DEBUG (MainThread) [custom_components.midea_ac_lan.midea.core.device] [210006727191360] Connecting to <IP_ADDRESS>:6444
2024-06-02 17:19:55.737 DEBUG (MainThread) [custom_components.midea_ac_lan.midea.core.device] [210006727191360] Connected
2024-06-02 17:19:55.737 DEBUG (MainThread) [custom_components.midea_ac_lan.midea.core.device] [210006727191360] Handshaking
2024-06-02 17:19:55.794 DEBUG (MainThread) [custom_components.midea_ac_lan.midea.core.device] [210006727191360] Authentication failed
2024-06-02 17:19:55.794 DEBUG (MainThread) [custom_components.midea_ac_lan.midea.core.device] [210006727191360] Status update: {'available': False}
添加烘干机时也遇到了相同的问题


fixes addon on apps with engines

Fixed build failing in applications with ember-engines.

update the yarn.lock file, thanks!
also, this is the same pr as https://github.com/html-next/ember-gestures/pull/124
I can merge but not release, so i'll defer to @rwwagner90

@eriktrom I feel like we should deprecate this package. I don't think it is necessary for modern web development anymore to add fast click hacks. I suppose for those still supporting IE maybe.

I feel like we should deprecate this package. I don't think it is necessary for modern web development anymore to add fast click hacks

I'm not opposed tbh - it was only for fast click on safari touch to begin with right? (thus don't think IE is an issue?)

@eriktrom I'm really not sure. I know all modern browsers and mobile browsers are supposedly the same, so I was just throwing out the possibility maybe someone supporting old browsers would need this.
If it only fixed mobile Safari specifically, I say we deprecate. Thoughts @runspired?

It was abstracted from ember-gestures a while ago - it was only for the 300ms delay on ios (are you hovering... 300ms... no, okay you actually want to 'click' that input, is basically what it did).
However, I'm not sure if it's still relevant for the older web views on ios.
Finally, ember-gestures has a dep on it, which is in our hands, I can handle that, if we decide to deprecated this.
and agree, @runspired -- in which version of ios did this become irrelevant - there is a webkit blogpost from a couple years back that claimed 300ms delay would be removed, but webkit tickets (of which i don't have links to on hand atm) did indicate at that time, that it was wasn't fully removed, I'd need to find such tickets and their status to confirm, but ideally, you just know everything™ so we'll decide based on your feedback. If I can help track things down, let me know. Cheers.

I know I haven't noticed any issues on mobile anymore, so whether it was officially fixed or not, I think it is no longer an issue.

@PrinceCornNM - make a perf profile .json file in safari when it's hooked up to the ios device in question. Click around, try to get the timeline to show the 300ms delay and I'll re-open.
Thanks

I think this was just to fix the build, which we could maybe merge, but we need to decide if we should deprecate this whole package.

@rwwagner90 - agree

@eriktrom and @rwwagner90
It fixed build, and it enabled me to use this in our library for our app.


Add Dockerfile

Build disque from source code in docker container, which makes sure everyone can use it easily and repeatable.
Usage:
docker build -t disque .
docker run -d --net=host disque

An official Docker image would be awesome.  I created a similar repository with a Dockerfile to accomplish the same thing.  I suggest removing the compilation dependencies after building in the Dockerfile, and stepping down from root when running disque-server.

Hello, I'm not a big fan of adding infrastructure related things into services source code, I mean if there is interest like for Redis a Docker image will happen and people can use it. Moreover currently Disque is not really compatible with Docker because of Docker port remapping stuff, but should be easy to fix, and I'm interested in fixing it at some point. Closing for now, thanks.

That's fine and we will try to help redis and disque easier to use when it's ready :smiley:

Thanks!

hi:
@antirez ,Currently Disque is not really compatible with Docker because of Docker port remapping stuff, I woder whether this problem is solved, i am now using docker-disque, but it can't get cluster info by calling hello(), the return ip is null.


test(html): do not wrap duplicated html

Description
When trying to add test for importmap in playground/html for https://github.com/vitejs/vite/pull/11492. I found that all the html will be wrapped into another html tag by pre-transform hook. Even there's already an existing  tag in the html file itself.
Files already have a html tag in playround/html

So, the transformed html of above looks like below (/emptyattr in dev mode)

<!DOCTYPE html>

    <meta name="description" content="a vite app">

    <meta charset="UTF-8">
    <meta name="viewport" content="width=device-width, initial-scale=1.0">
    <title>Test HTML transforms</title>
    <meta name="keywords" content="es modules">

  <!DOCTYPE html>

    <meta charset="UTF-8" />
    <meta http-equiv="X-UA-Compatible" content="IE=edge" />
    <meta name="viewport" content="width=device-width, initial-scale=1.0" />
    <title>Empty Attr</title>

This is injected

This is injected only during dev

after fixing, will be
<!DOCTYPE html>

    <meta name="description" content="a vite app">

    <meta charset="UTF-8" />
    <meta http-equiv="X-UA-Compatible" content="IE=edge" />
    <meta name="viewport" content="width=device-width, initial-scale=1.0" />
    <title>Empty Attr</title>
    <meta name="keywords" content="es modules">

This is injected

This is injected only during dev

Additional context

https://github.com/vitejs/vite/pull/11492 relies on this to add a test case with importmap, multiple heads in html will mess the test up.

What is the purpose of this pull request?

[ ] Bug fix
[ ] New Feature
[ ] Documentation update
[x] Other

Before submitting the PR, please make sure you do the following

[x] Read the Contributing Guidelines.
[x] Read the Pull Request Guidelines and follow the PR Title Convention.
[ ] Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
[x] Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
[ ] Ideally, include relevant tests that fail without this PR but pass with it.

Thanks!


Support HTTPS in etcd URL schemes

Right now it's not possible to use Calico with etcd cluster where all URLs use HTTPS. It would be great to have such option for security implications. The same is for Calico Kubernetes plugin, as everything I can do is to change the ETCD_AUTHORITY variable which is not enough to access the etcd store.

+1

We should prioritise fixing this. The code should be easy but we need to agree on a design. Any input would be appreciated.
One option would be to use another environment variable such as ETCD_SCHEME which defaults to http but can also take the value https
@loshkovskyi What are your thoughts?

Here is an example how I can access etcd store over HTTPS:
etcdctl --cert-file /etc/origin/master/master.etcd-client.crt \
--key-file /etc/origin/master/master.etcd-client.key \
--ca-file /etc/origin/master/master.etcd-ca.crt \
--peers https://osv3-master-01.example.com:2379,https://osv3-node-01.example.com:2379,https://osv3-node-02.example.com:2379 \
ls

So if I set ETCD_AUTHORITY to https, I need several more variables to set paths to the certificates.

I've been looking into a design for this.  Please touch base with me before tackling this one.

Fixed by #654


Can't find makeTestData()

Here it is:
https://github.com/petedodd/HEdtree/blob/c6a3a52c02fbc6a5e74c49aa4611cdaf8cba3264/R/showParmz.R#L54-L61
Maybe you forked from before I introduced?


Fix sitemap customergroup blocked categories

Description
Please describe your pull request:

Why is it necessary?
Same as in PR #869 only for categories :)

Questions
Answers

BC breaks?
no

Tests pass?
yes

Related tickets?

How to test?

Hello,
thank you for creating this pull request.
I have opened an issue on our Issue Tracker for you. See the issue link: https://issues.shopware.com/issues/SW-17568.
Please use this issue to track the state of your pull request.

Hi @shyim, your PR just got merged and will help make the 5.3.4-release even more awesome! 👍


[FLINK-22479][Kinesis][Consumer] Potential lock-up under error condition (Flink 1.12)

What is the purpose of the change
Pull in the following fixes from AWS fork:

Fix issue where KinesisDataFetcher.shutdownFetcher() hangs (issue, pull request)

Log error when shutting down Kinesis Data Fetcher (issue, pull request)

Treating TimeoutException as Recoverable Exception (issue, pull request)

Add time-out for acquiring subscription and passing events from network to source thread to prevent deadlock (pull request)

Brief change log

Added Timeout when blocking on queue between source and network thread
Catching exceptions during source teardown, to allow source to interrupt threads of executor

Verifying this change

Added unit tests for changes
Verified on AWS KDA with test applications

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): no
The public API, i.e., is any changed class annotated with @Public(Evolving): no
The serializers: no
The runtime per-record code paths (performance sensitive): yes
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn/Mesos, ZooKeeper: no
The S3 file system connector: no

Documentation

Does this pull request introduce a new feature? no
If yes, how is the feature documented? not applicable

@flinkbot run azure


Fix a bug in batch_eval

Fix #572 .
The problem is caused by the reason that batch_eval in utils_tf.py does not return any value.

I closed and reopened the PR to trigger a new Travis build.

@npapernot Should I do anything for the CLA?

No it just broke because I pushed a minor fix to your branch so we can still merge. Thanks for asking!


Add stint start and end times as an attribute

This allows to display the stint duration, e.g.
for monitoring battery degradation.

@osks Is there anything that prevents this PR from being merged? I'd be happy to adjust/update if necessary.

Hello,
i had not seen this merge request.
Is this still required ? Why clsing it ?
regards,
Jérémie


Select Variables

Selecting should automatically leave in ids.

More generally: it should not be possible to create a degenerate variable by some function.


chore!: break out BlobTx and IndexWrapper types into separate tx package

While updating celestia-app, it felt out of place that BlobTx and IndexWrapper should be part of the shares package. This moves them out

Do we also want to move the proto definitions for BlobTx and IndexWrapper from proto/blob/v1/blob.proto to something like proto/tx/blobtx.proto and proto/tx/indexwrapper.proto

Yeah it seems more logical to separate them but we don't need to


Add karl-police to contributor list

Pull request checklist:

[ ] CHANGELOG.md was updated, if applicable

Wait... did the format thing actually break?
I managed to build this in Visual Studio fine.

Rename your avatar file (and the reference in the contributors file) to have an underscore instead of -. C++ is interpretting your name as karl subtract police.

Rename your avatar file (and the reference in the contributors file) to have an underscore instead of -. C++ is interpretting your name as karl subtract police.

Does the auto generator, name the variables based on filename?

https://github.com/Chatterino/chatterino2/blob/master/resources/generate_resources.py#L51
looks like it

Wait... did the format thing actually break?
I managed to build this in Visual Studio just fine.

I wonder how VS didn't complain about it


Few improvements for SpriteFrames Editor

Added custom arrow step for Speed and Frame Duration fields.
Moved Animation Speed and Animation Looping to the top to increase the height of the animation list.
Fixed label position for empty frames.
Corrected label format (colon and decimals are not displayed unnecessarily).

Before:

After:

Closes godotengine/godot-proposals#6101.

Loops and FPS are tied to animation resources, but AutoPlay is tied to AnimatedSpriteNode.
If you select the SpriteFrames resource in the lower left file dock, only the PlaybackIcons and AutoPlay icons need to be removed.
New Del | FPS Loop | Autoplay
or
New Del FPS Loop | Autoplay
I suggest placing the icons and separators as shown above. In this case, only the [| Autoplay] parts needs to be hidden with a independence container.

Thanks!


Learning to rank relevant files for bug reports using domain knowledge

Learning to rank relevant files for bug reports using domain knowledge
Link to paper: http://dl.acm.org/citation.cfm?id=2635868.2635874&coll=DL&dl=GUIDE&CFID=464701544&CFTOKEN=55037057
Link to data: http://figshare.com/articles/The_dataset_of_six_open_source_Java_projects/951967
Xin Ye, Razvan Bunescu, Chang Liu
Pages: 689-699
doi>10.1145/2635868.2635874
Full text: PDFPDF
When a new bug report is received, developers usually need to reproduce the bug and perform code reviews to find the cause, a process that can be tedious and time consuming. A tool for ranking all the source files of a project with respect to how likely ... expand

Xin<EMAIL_ADDRESS>Razvan<EMAIL_ADDRESS>Chang<EMAIL_ADDRESS>Abstract
When a new bug report is received, developers usually need to reproduce the bug and perform code reviews to find the cause, a process that can be tedious and time consuming. A tool for ranking all the source files of a project with respect to how likely they are to contain the cause of the bug would enable developers to narrow down their search and poten- tially could lead to a substantial increase in productivity. This paper introduces an adaptive ranking approach that leverages domain knowledge through functional decomposi- tions of source code files into methods, API descriptions of library components used in the code, the bug-fixing history, and the code change history. Given a bug report, the ranking score of each source file is computed as a weighted combi- nation of an array of features encoding domain knowledge, where the weights are trained automatically on previously solved bug reports using a learning-to-rank technique. We evaluated our system on six large scale open source Java projects, using the before-fix version of the project for every bug report. The experimental results show that the newly introduced learning-to-rank approach significantly outper- forms two recent state-of-the-art methods in recommending relevant files for bug reports. In particular, our method makes correct recommendations within the top 10 ranked source files for over 70% of the bug reports in the Eclipse Platform and Tomcat projects.

Needs better context notes. See this example or this example as a reference.
Context notes are directly inserted into the actual repository (like this), so good context notes are necessary for putting the datasets into the repo in a timely fashion.

Categorization
bug report
Author list for the paper
Xin Ye<EMAIL_ADDRESS>Razvan Bunescu<EMAIL_ADDRESS>Chang<EMAIL_ADDRESS>General overview of the data
This dataset contains bug reports, commit history, and API descriptions of six open source Java projects including Eclipse Platform UI, SWT, JDT, AspectJ, Birt, and Tomcat. This dataset was used to evaluate a learning to rank approach that recommends relevant files for bug reports.
Dataset structure
File list:

AspectJ.[xls|xml] – The bug reports and commit history of AspectJ.
Birt.[xls|xml] – The bug reports and commit history of Birt.
Eclipse_Platform_UI.[xls|xml] – The bug reports and commit history of Eclipse Platform UI.
JDT.[xls|xml] – The bug reports and commit history of JDT.
SWT.[xls|xml] – The bug reports and commit history of SWT.
Tomcat.[xls|xml] – The bug reports and commit history of Tomcat.
XLS/XML Headings:
bug_id -- refers to the bug report id.
summary -- refers to the bug report summary.
description -- refers to the bug report description.
report_time -- refers to the bug report report time.
report_timestamp -- refers to the bug report report timestamp.
status -- refers to the status of the bug report.
commit -- refers to the SHA-1 hash id for the commit that fixed the bug report.
commit_timestamp -- refers to the commit timestamp.
files -- contains the full path of every Java file that was fixed in this commit.
￼￼* result -- contains the position of every positive instance in our ranked list result.

Link to the paper associated with the dataset
http://dl.acm.org/citation.cfm?id=2635868.2635874&coll=DL&dl=GUIDE&CFID=464701544&CFTOKEN=55037057
Paper abstract
When a new bug report is received, developers usually need to reproduce the bug and perform code reviews to find the cause, a process that can be tedious and time consuming. A tool for ranking all the source files of a project with respect to how likely they are to contain the cause of the bug would enable developers to narrow down their search and poten- tially could lead to a substantial increase in productivity. This paper introduces an adaptive ranking approach that leverages domain knowledge through functional decomposi- tions of source code files into methods, API descriptions of library components used in the code, the bug-fixing history, and the code change history. Given a bug report, the ranking score of each source file is computed as a weighted combi- nation of an array of features encoding domain knowledge, where the weights are trained automatically on previously solved bug reports using a learning-to-rank technique. We evaluated our system on six large scale open source Java projects, using the before-fix version of the project for every bug report. The experimental results show that the newly introduced learning-to-rank approach significantly outper- forms two recent state-of-the-art methods in recommending relevant files for bug reports. In particular, our method makes correct recommendations within the top 10 ranked source files for over 70% of the bug reports in the Eclipse Platform and Tomcat projects.
BibTeX reference for the paper
@inproceedings{Ye:2014,
author = {Ye, Xin and Bunescu, Razvan and Liu, Chang},
title = {Learning to Rank Relevant Files for Bug Reports Using Domain Knowledge},
booktitle = {Proceedings of the 22Nd ACM SIGSOFT International Symposium on Foundations of Software Engineering},
series = {FSE 2014},
year = {2014},
location = {Hong Kong, China},
pages = {689--699},
numpages = {11},
}
Link to the datasets
http://figshare.com/articles/The_dataset_of_six_open_source_Java_projects/951967
Is this dataset part of a larger series or collection?
no

Added as bugfiles.
http://localhost:4000/repo/issues/bugfiles.html

This is a good example of context notes. See WeiFu's comment from March 12th 2015.

Actually submitted, but keeping as example of good context notes at Summarized stage.


[BUG] unable to install longhorn

Describe the bug (🐛 if you encounter this issue)
I'm trying to deploy longhorn via kubectl but longhorn-manager pods go in CrashLoopBackOff  state
NAME                                        READY   STATUS             RESTARTS         AGE
longhorn-driver-deployer-54d5cddccc-qq7dn   0/1     Init:0/1           0                136m
longhorn-manager-84dkm                      0/1     CrashLoopBackOff   35 (3m35s ago)   136m
longhorn-manager-kmh85                      0/1     CrashLoopBackOff   18 (4m13s ago)   73m
longhorn-manager-n7ctg                      0/1     CrashLoopBackOff   35 (2m43s ago)   136m
longhorn-manager-qp4nh                      0/1     CrashLoopBackOff   35 (3m1s ago)    136m
longhorn-manager-x5c7n                      0/1     CrashLoopBackOff   35 (3m55s ago)   136m
longhorn-ui-5b974686f-bxppf                 1/1     Running            0                136m
longhorn-ui-5b974686f-zpbcn                 1/1     Running            0                136m
kubectl logs -n longhorn-system longhorn-manager-84dkm
watching at log I find this fatal error:
time="2023-11-17T11:14:19Z" level=fatal msg="Error starting manager: upgrade resources failed: Internal error occurred: failed calling webhook "validator.longhorn.io": failed to call webhook: Post "https://longhorn-admission-webhook.longhorn-system.svc:9502/v1/webhook/validaton?timeout=10s\": Forbidden" func=app.DaemonCmd.func1 file="daemon.go:83"
To Reproduce
i downloaded yaml file
wget https://raw.githubusercontent.com/longhorn/longhorn/v1.5.3/deploy/longhorn.yaml
and customize with the following settings
default-setting.yaml: |-
default-data-path: /mnt/longhorn/
default-data-locality: best-effort
orphan-auto-deletion: true
allow-volume-creation-with-degraded-availability: false
replica-auto-balance: best-effort
storage-minimal-available-percentage: 10
create-default-disk-labeled-nodes: true
Then i apply the yaml with
kubectl apply -f longhorn.yaml
Expected behavior
Successfull deployment
Support bundle for troubleshooting
n.a.
Environment

Longhorn version: 1.5.3
Installation method (e.g. Rancher Catalog App/Helm/Kubectl): kubectl
Kubernetes distro (e.g. RKE/K3s/EKS/OpenShift) and version: vanilla k8s

Number of management node in the cluster: 1
Number of worker node in the cluster: 5

Node config

OS type and version: linux rocky 8
Kernel version: 4.18.0-477.27.1.el8_8.x86_64
CPU per node: 4
Memory per node: 4 gb
Disk type(e.g. SSD/NVMe/HDD): NVMe
Network bandwidth between the nodes: 1 Gb

Underlying Infrastructure (e.g. on AWS/GCE, EKS/GKE, VMWare/KVM, Baremetal): vmware
Number of Longhorn volumes in the cluster:  n.a.
Impacted Longhorn resources: n.a.

Volume names: n.a.

This should be related to service name resolution, and it looks like the service endpoint is unable to reach out.
Go check a similar issue reported by another community https://github.com/longhorn/longhorn/issues/7100 or debug it first https://kubernetes.io/docs/tasks/administer-cluster/dns-debugging-resolution/.
cc @ChanYiLin

You are the man! I forgot i was behind a corporate proxy. Thanks

all is fine thx


Improve JobHistory and FlowHistory features to include runtime, waittime, resource used and resource wasted.

Amazing work!!
Suggestions, some of them already discussed.

Update the graph tooltips!
Can you also deploy this on the test cluster so that we can see the behavior in the cluster.
Make sure you test these across browsers!
Can we do something about the repeated code sections?
Make sure no mysql index is required for any fields.
We need to add some more tests. Utility tests! Not sure how to do the UI tests!

+1, amazing feature!!
Please make sure you update the Wiki page!

+1.


Initialize runs several times in a few games

I noticed that the ImguiRenderLoop initialize function will run several times if the DLL is injected early in certain games.
Examples: Mount & Blade: Warband (32bit, DX9), Niche (64bit, DX11), Oxygen Not Included (64bit, DX11).
Is this something you're aware of @veeenu or possibly have an idea of why that is happening?

https://github.com/veeenu/hudhook/blob/4c2968d23d70d963e094db1ffacc8eeeba40c8f6/src/hooks/dx11.rs#L77
I know next to nothing about swap chains, but it seems that the ImguiRenderer gets invoked more than once inside of it in some cases.

Hi! Sorry for the delay, been quite busy.
In some games (definitely DS3 and ER) not reinitializing the renderer means that the UI won't scale alongside resizing the window, at best, or crash, at worst.
The fact that it gets called multiple times with early injections makes me think that resize is just called pointlessly by the game/engine a number of times while nothing is still getting rendered yet -- I wouldn't say this is something hudhook should work around.

Hi! Sorry for the delay, been quite busy.

No worries, no pressure, just happy to get a response eventually!

In some games (definitely DS3 and ER) not reinitializing the renderer means that the UI won't scale alongside resizing the window, at best, or crash, at worst.

Aha! I suppose I should just make changes on my own end then. I have some functionality in the initialize function that I'd rather not have run more than once.

The fact that it gets called multiple times with early injections makes me think that resize is just called pointlessly by the game/engine a number of times while nothing is still getting rendered yet -- I wouldn't say this is something hudhook should work around.

Absolutely correct, thank you for the input mate. I'll close this one.


from pickle to joblib

Any plan to move to joblib, being more efficient in several situations?

I consider pickleshare to be in maintenance only mode, with updates only
for crucial bugfixes. So probably not. If you want to fork it
(joblibshare?), I'd be ok with that.
On 30 Mar 2017 3:04 p.m., "Fabio Stefanini"<EMAIL_ADDRESS>wrote:

Any plan to move to joblib, being more efficient in several situations?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/pickleshare/pickleshare/issues/25, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAUA9dgta2qCHjOPF1O0kxaRNpqumNhkks5rq7XLgaJpZM4MuZ02
.


std/sw: implement GLV (GLS) scalar multiplication in G2

From #222:

this GLV improvement works also for G2. So the same code should be used in g2.go (as in gnark-crypto). That is said, we can have a 4-dimensional GLV (GLS) in sw_bls12377/g2 and 8-dimensional in in sw_bls24315/g2 (instead of 2-dimensional in g1). This is low priority as it is not used in groth16 verifier gadget and it's not implemented in gnark-crypto yet. But it might be worth it once we implement PlonK verifier gadget (or just KZG verifier) as it involves a single scalar mul in G2.

#305 closes this.


⚠ Bofrost.be has degraded performance

In 7cd2342, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1577 ms

Resolved: Bofrost.be performance has improved in 4339586.


Upgrade the sdk, make the setup compatible with Google's OpenId Connect

Thanks for the big work you've done. I'd like to use this filter to protect the kubernetes dashboard and other applications like grafana. For that to work I'd like google oidc and ssl support for the filter. The changes started small, but I did a few improvements in the end. Sorry, there are a lot of changes in here, but the overall behaviour didn't change.

Upgrade to the newest sdk
Trim the cookie name as there are spaces if there are multiple cookies are present
By not doing any query mutations, we make the filter compatible with google auth
Make the cookie name and Authorization header configurable, so it's possible to use this service even when another Authorization header are present.
If we configure the target_header_name to e.g. x-oid-token, we can read that out again in the jwt filter.
Use the httpOnly and Secure flags on cookies based on X-Forwarded-Proto
Fix https protocol support using X-Forwarded-Proto
Implement a first nonce handshake. We're using a cookie to persist the data.
At the moment the data in the cookie isn't verified. I failed in setting up jwt or hmac for wasm.
I've also added a simpler example that directly uses an envoy and the google oidc api.
https://github.com/dgn/oidc-filter/blob/0c841440a0bdd01b3862c71a92e1aa9d53616ad8/examples/envoy.yaml

Please let me know if there are any changes needed. Also, I don't have any experience with rust, so there might be some issues with it.
One error I'm seeing sometimes is (also with the old version)
[2021-02-08 03:45:07.324][4830405][error][envoy_bug] [external/envoy/source/common/http/filter_manager.cc:494] envoy bug failure: !state_.local_complete_ || status == FilterHeadersStatus::StopIteration. Details: Filters should return FilterHeadersStatus::StopIteration after sending a local reply.

I think we'll need to make the redirect_uri configurable, so it can be static. Providers like google only support whitelisted urls. Only localhost supports completely custom urls in combination with the device-based oauth credentials.

I think we'll need to make the redirect_uri configurable, so it can be static. Providers like google only support whitelisted urls. Only localhost supports completely custom urls in combination with the device-based oauth credentials.

What scenario would that cover? Wouldn't the :authority header convey the correct hostname? Or is this meant for cases where internal hostname != external hostname?

Basically we only need to make the path of the redirect_uri configurable because wildcards aren't supported.
But at the same time I'd also support a fixed protocol & authority. So the setup gets simpler.
e.g. at the moment if there's no http to https redirect you'll need to register two callback urls. And with mixed protocols there's the issue that the secure cookie can't be overwritten and it causes a redirect loop (also in some other edge cases). If we have a fixed callback path, we can properly handle all errors there and never trigger a redirect on that route.

Basically we only need to make the path of the redirect_uri configurable because wildcards aren't supported.
But at the same time I'd also support a fixed protocol & authority. So the setup gets simpler.

I agree, it does make the setup simpler. And as you already implemented storing the origial request URL in the cookie, we can then redirect back to that. Do you want to do this in this PR or should we do it in a follow-up?

I can do it in this pull request, but I won't have time until the weekend.

I've pushed the update with the redirect_uri config support.
I think we can merge that for now.

Apache v2 is good 👍
Thanks

/test all

I've been following this PR and am glad to see it merged.  Would it be possible to include an example for using the filter with istio and google auth?  I'm having difficulty determining what the value for auth_cluster should be for google auth instead of keycloak in https://github.com/dgn/oidc-filter/blob/master/examples/istio/envoyfilter.yaml#L33.  The envoy example seems to reference clusters defined in https://github.com/dgn/oidc-filter/blob/master/examples/envoy/envoy.yaml which I'm not seeing a corollary for in istio.  Thanks

to get google working, you'll need a cluster entry in envoy. using istio you should be able to use an external service entry for that: https://istio.io/latest/docs/tasks/traffic-management/egress/egress-control/#access-an-external-http-service
not shure whether they use the same name pattern.

Yeah, you'll need a ServiceEntry to achieve the same in Istio. The naming syntax of the Envoy cluster will follow the same rules as the keycloak cluster (ie with the pipes)


Can the new error types be exported?

Hi @oleiade ,
WRT this, thanks for adding the additional error types. However, we're still unable to check for an instance of the new errors as they're not exported. Would it be possible for the new errors to be exported so we can check for an instance of NetworkError?
Thanks

Hey @ziltodian 👋🏻
For sure, we haven't managed to publish a new release yet, but we'll try to get that done as soon as possible. Errors will be exported both from the main index.js file, as well as client-specific ones 🙇🏻

Hi @ziltodian 👋🏻
We have published a new release of jslib-aws (v0.13.0). Error types are now exported from every bundles. Could you give it a spin, and let us know if that addresses the issue for you? 🙇🏻
PS: in order to keep the issue backlog manageable, without answer, I will close this in one week 👍🏻

Hi @oleiade , I've actually made the change to use NetworkError today. It's currently in review. I'll keep you posted.

Hi @oleiade , we've been able to update our code to check for an instance of NetworkError. Many thanks for the changes. Some feedback I have is that it might also be helpful to re-export the NetworkErrorName type and the *ErrorKind enums.

Hi @ziltodian 👋🏻
If you have the capacity to do so, I think that would be a good first issue to make a PR for.
Let me know if you don't and I'll find a moment to adress it myself 🙇🏻


Fix is_iterator for container algorithms

Fix is_iterator so that SFINAE can work
Call projection functions with invoke so that member functions
can be passed as arguments.

lgtm, thanks!

@hkaiser: just out of curiosity, what's benefit of using explicit quailification of hpx::util::invoke instead of using declarations?

@hkaiser: just out of curiosity, what's benefit of using explicit quailification of hpx::util::invoke instead of using declarations in this case?

This allows for things like this:
struct A {
    int foo() { return 42; }
};

std::vector<A> v(43);

parallel::for_each(
    par, begin(v), end(v)
    [](int i) { cout << i; },
    &A::foo);

what's benefit of using explicit quailification of hpx::util::invoke instead of using declarations in this case?

@AntonBikineev It avoids ADL havoc, qualified vs unqualified is always about avoiding ADL. For instance, when std:: arguments are used both hpx::util::invoke and std::invoke are viable matches and the unqualified call is ambiguous. Generic libraries should always do qualified calls unless they explicitly want a call to reach a customization point.

@K-ballo: thanks for the point. What about this:
using hpx::util::invoke;
(invoke)(something);
/joke/


misc typo

Headlines will only appear in Web client; they will not be shown on other client types.
should be
Headlines will only appear in the Web client; they will not be shown on other client types.
[Enter feedback here]

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

ID: 4e978f7d-5b1b-84f9-dec9-33fdf3792f8c
Version Independent ID: a2ad8189-852b-f76c-df36-c3fbcea8ce93
Content: Create a Role Center Headline - Business Central
Content Source: dev-itpro/developer/devenv-create-role-center-headline.md
Service: dynamics365-business-central
GitHub Login: @jswymer
Microsoft Alias: solsen

Thank you for your feedback! This will be fixed in the next doc update.


BUG: Some photos don't load

Kosta confirmed, check others

Fixed - missing profile pictures added to storage.


[BLUEPRINT] Local Zones

Example that demonstrates EKS Blueprints deploying cluster in Local Zones

closing due to lack of demand


New release from time to time

Hello,
it would be helpful to create a new release from time to time,
so that distributions / packagers can pick it and provide newer versions
from newsbeuter.
The last time a new release was created is Feb. 2015.
That's about two and a half year ago.
So, please create a new release, so that people, who want to use
pre-packaged releases could just use those and install with their package-manager.
Maybe releases could be provided in regular time intervals, if possible?

https://github.com/akrennmair/newsbeuter/issues/525

Closing this as duplicate of #525. Will post an update over there.


[Request] update inkscape to v1.0

Is it possible to add it?
https://inkscape.org/release/inkscape-1.0/

On it: https://github.com/lukesampson/scoop-extras/issues/3988


Raise system error subclasses

https://github.com/github/trilogy/pull/41 added a translation of ECONNREFUSED and ECONNRESET to Trilogy::BaseConnectionError.
We've got a few places at GitHub where we explicitly rescue these errors (or SystemCallError). Although it is possible to rework those rescues to check for particular error messages (like we did in
https://github.com/github/activerecord-trilogy-adapter/commit/03c16105c8ea5da4c90f837b607e97b1b2dcd6d0), it'd be a bit easier if we could maintain compatibility. I also worry that checking for specific error messages could be a bit brittle.
This commit introduces two new Trilogy errors, which inherit from the corresponding Errno errors. We've already done something like this for Errno::ETIMEDOUT.
This keeps Trilogy compatible with GitHub's existing rescues, while still raising something that is a Trilogy::Error and a Trilogy::ConnectionError (although NOT a
Trilogy::BaseConnectionError anymore).
A downside to this approach is that we might end up with a lot of Trilogy-specific Errno subclasses. If that gets annoying perhaps we could revisit when it comes time for a major release. Another approach might be a single Trilogy::SystemCallError that inherits from SystemCallError and then keeps a reference to the underlying Errno error.
cc @adrianna-chang-shopify

Yeah, I think it's fine to make further breaking changes. If the changes here are going in the wrong direction, I can try something else. The main thing is that we'd like to rescue these separately from other Trilogy errors, so Trilogy_BaseConnectionError isn't ideal.

Maintaining the parallel to the way we've handled Errno::ETIMEDOUT SGTM 👍


How do I serve a 404 error to the user (not in routes.js)

If I'm nested several containers/components deep and I want to serve an error 404 component instead of the component for the current route. How do I do that without a redirect.
I'm not talking about detecting an error in the api, EG https://github.com/erikras/react-redux-universal-hot-example/issues/518. https://github.com/erikras/react-redux-universal-hot-example/issues/729 Also explores this, but the solution is for the api.
I'm in a component, but due to the query string parameters being wonky, I need to serve a 404 page to the user.

I guess as long as you make sure to define a 404 state in your routing config you can do this:
const checkIfValid = (data) => {
  if (data.notValid) {
    this.props.pushState(null, `/404/`);
  }
};

Just make sure you pass pushState to your component with @connect

@janhoogeveen Unfortunately that changes the url. I need to render the 404 component whilst still displaying the url that is a 404!

I've solved this with the [https://github.com/Ambroos/react-nested-status](React Nested Status) module.
@erikas Would a pull request be welcome?
It's a very simple to use solution. Just requires a few edits to server.js to get it working:
at the top
import NestedStatus from 'react-nested-status';

at the bottom replace:
const status = getStatusFromRoutes(routerState.routes);
if (status) {
  res.status(status);
}
res.send('<!doctype html>\n' +
  ReactDOM.renderToString());

with:
const repsonse = ReactDOM.renderToString(

);

if (__SERVER__) {
  const status = getStatusFromRoutes(routerState.routes);
  if (status) {
	res.status(status);
  }

  const nestedStatus = NestedStatus.rewind();
  if (nestedStatus !== 200) {
	  res.status(nestedStatus);
  }
}

res.send('<!doctype html>\n' + repsonse);

Then in what ever container/component you need to serve a 404 :
import React, { Component, PropTypes } from 'react';
import { connect } from 'react-redux';
import connectData from 'helpers/connectData';
import { fetchApiData } from 'redux/modules/foo/fetchApiData';
import { NotFound } from 'containers';

@connectData(null, (getReduxState, dispatch, state, params) => {
  return dispatch(fetchApiData(params.fooId));
})
@connect(
  (reduxState) => ({
	fooData: reduxState.foo.data,
  })
)
export default class ProductType extends Component {
  static propTypes = {
	fooData: PropTypes.object,
  }

  render() {
	let content;
	// ... whatever your api sends back to indicate this is a 404
	if (!this.props.fooData.exists) {
	  content = <NotFound/>;
	} else {
	  content = (

		  Normal content...

	  );
	}
	return content;
  }
}

Finally replace /src/containers/NotFound/NotFound.js
import React, { Component } from 'react';
import NestedStatus from 'react-nested-status';

export default class NotFound extends Component {

  render() {
	return (
	  <NestedStatus code={404}>

Error 404! Page not found.

	  </NestedStatus>
	);
  }
}

The React Nested Status works not properly.


PDPDEVTOOL-4551: [U5] Issue 650319 SDF > Visual Studio Code > SuiteCl…

…oud: Import Files > Stuck in Loading File Cabinet folders

The pipeline is probably going to fail while the Java CLI hasn't been updated yet. Once the Java CLI code review is done and a new Java CLI build is created, the pipeline will become green.


Add Firefox check — replaces PR #257

What about when zoom is disabled using the @viewport at-rule?
See https://developer.mozilla.org/en-US/docs/Web/CSS/@viewport


CATiledLayer for large chunks of text

Idk how best to combine these, but would improve rendering huge chunks of text.

mmap bitmap from disk
All layers in memory defeats the purpose
LRUCache can store chunks?

http://www.cimgf.com/2011/03/01/subduing-catiledlayer/

Yeah, big fan of CATiledLayer for huge chunks of text. However, they are REALLY heavy weight on memory and bad for scroll perf if you have a bunch of them on the screen at once (I tested this awhile ago).  It's a kind of complicated dance that I'm sure could be simplified.
I pulled the impl from my old project:
https://gist.github.com/ocrickard/9892a28cfd733a84fed95b2a66f27615
Anyway, if you're looking for inspiration, that impl performs great both in tiny little labels, and in huuuge walls of text.

TIL!!
I've never used it before, spared me a lot of time figuring this out lol. I bet the async drawing will be a good quick win. Then if we (or someone else) is hitting huge perf issues from drawing giant bitmaps, then we can find a way to make this work.


Add The Ability To Mark Fixers As Conflicting

We need a way to stop fixers such as the concatenation fixers as incompatible with each other, and prevent them from being run at the same time.
It would also be useful to allow fixers that depend on each other, and thus fixer Y can only be run if fixer X is enabled.

Anyone willing to make PR for this?
I think that mark the fixers as conflicting is enough for us, at least for now.
We have FixerFactory which could handle it.
Perhaps @SpacePossum ?

I might give it a try, if I make it it will be this week as after that I have to focus on other (non PHP) development.
Btw. I was thinking about something and wonder what others think about it. What if we would mark some fixers as reversible (on 2.x line). That way some conflicts can be avoided by merging some of the fixers into one fixer that can be ran in reverse. For example;

Fixer
When ran in reversed acts as

SingleBlankLineBeforeNamespaceFixer
NoSingleBlankLineBeforeNamespaceFixer

concat_without_spaces
concat_with_spaces

phpdoc_type_to_var
phpdoc_var_to_type

There are others as well.
Using configuration you could set the fixer to ran in reverse. From the command line we could do something like fixers=~concat_without_spaces.
It won't fix all conflicts, but quite some and it might reduce the code base a bit.

It would not resolve conflicts at all (at least I can't see it).
If one one ruleset: {concat_without_spaces: true, concat_with_spaces: true} then the knowledge of the fact that they are reversable doesn't help.
Also, turning off fixer (like -foo) is sth different than wanting the reverse fixer (eg ~foo), but then one must to know that there is a reverse fixer, so he could as well simply use that explicitly.

{concat_without_spaces: true, concat_with_spaces: true}

The idea is no longer having those two fixers, but 1, which you could run in reverse.
So configure something like;
{ concat_spaces: true}
or
{ concat_spaces : reverse}
or leave out the fixing at all
{ concat_spaces : false}

ref #1443


update installation docs

go through the setup process for a fresh project (django-admin.py createproject) und update the docs to reflect all needed steps.
e.g:

settings MEDIA_URL and MEDIA_ROOT and STATIC_
...

I confirm such need.
I've spent some quality time before understanding that if MEDIA_URL is not set the file urls will be broken: they will be relative from current page, so from admin they will look like http://DOMAIN/filer/file/1/change/filer_public/HASH/FILENAME instead of http://DOMAIN/filer_public/HASH/FILENAME, which will result in a redirect appending /, then appending /change/ then 404.


sst cli doesn't run on readonly linux distros like nixOS

$ pnpm sst deploy --stage dev --print-logs
time=2024-09-23T18:11:47.901+02:00 level=INFO msg="checking for pulumi" path=/home/vt/.config/sst/bin/pulumi
time=2024-09-23T18:11:48.002+02:00 level=INFO msg="checking for bun" path=/home/vt/.config/sst/bin/bun
time=2024-09-23T18:11:48.003+02:00 level=INFO msg="bun install"
time=2024-09-23T18:11:48.003+02:00 level=INFO msg="bun downloading" url=https://github.com/oven-sh/bun/releases//download/bun-v1.1.29/bun-linux-x64-baseline.zip
time=2024-09-23T18:11:52.192+02:00 level=INFO msg="initializing project" version=3.1.35
time=2024-09-23T18:11:52.192+02:00 level=INFO msg="esbuild building" out=/home/vt/personal/trustpass-web/.sst/platform/sst.config.1727107912192.mjs
time=2024-09-23T18:11:52.195+02:00 level=INFO msg="esbuild built" outfile=/home/vt/personal/trustpass-web/.sst/platform/sst.config.1727107912192.mjs
time=2024-09-23T18:11:52.225+02:00 level=INFO msg="evaluating config"
time=2024-09-23T18:11:52.249+02:00 level=INFO msg="config evaluated"
time=2024-09-23T18:11:52.250+02:00 level=INFO msg="checking platform"
time=2024-09-23T18:11:52.250+02:00 level=INFO msg="installing deps"
⠋  Installing providers...time=2024-09-23T18:11:52.250+02:00 level=INFO msg="getting package" name=@sst-provider/aws version=latest
⠼  Installing providers...time=2024-09-23T18:11:52.692+02:00 level=INFO msg="getting package" name=@pulumi/aws version=latest
⠦  Installing providers...time=2024-09-23T18:11:52.939+02:00 level=INFO msg="writing package.json"
time=2024-09-23T18:11:52.939+02:00 level=INFO msg="adding dependency" name=aws
time=2024-09-23T18:11:52.939+02:00 level=INFO msg="fetching deps"
time=2024-09-23T18:11:52.939+02:00 level=ERROR msg="exited with error" err="failed to run bun install Could not start dynamically linked executable: /home/vt/.config/sst/bin/bun\nNixOS cannot run dynamically linked executables intended for generic\nlinux environments out of the box. For more information, see:\nhttps://nix.dev/permalink/stub-ld\n"
✕  Could not install dependencies

$ bun --version
1.1.27

I ran into a similar issue on NixOS with Bun. As a workaround, I used steam-run, which allowed me to run the necessary commands.
To streamline this, I added a couple of shell aliases:
{ hostname, ... }: {
  programs.bash = {
    enable = true;
    enableCompletion = true;

    shellAliases = {
      ...
      bun = "steam-run bun";
      bunx = "steam-run bunx";
    };
  };
}

This setup helps, but it would be fantastic to see an official fix that improves compatibility with Nix-like OSes. Thanks!


fix path separator in revision.

Resolve: https://github.com/istio/istio/issues/26095
[ ] Configuration Infrastructure
[ ] Docs
[ X ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Pull Request Attributes
Please check any characteristics that apply to this pull request.
[ ] Does not have any changes that may affect Istio users.

@morvencao: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
8adf3e1ea8eaebf9e5341df6f006d66e4c14f21b
link
/test release-notes_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@morvencao: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
8adf3e1ea8eaebf9e5341df6f006d66e4c14f21b
link
/test release-notes_istio

gencheck_istio
8adf3e1ea8eaebf9e5341df6f006d66e4c14f21b
link
/test gencheck_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@morvencao: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
8adf3e1ea8eaebf9e5341df6f006d66e4c14f21b
link
/test release-notes_istio

gencheck_istio
8adf3e1ea8eaebf9e5341df6f006d66e4c14f21b
link
/test gencheck_istio

unit-tests_istio
8adf3e1ea8eaebf9e5341df6f006d66e4c14f21b
link
/test unit-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@morvencao: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

gencheck_istio
8adf3e1ea8eaebf9e5341df6f006d66e4c14f21b
link
/test gencheck_istio

unit-tests_istio
8adf3e1ea8eaebf9e5341df6f006d66e4c14f21b
link
/test unit-tests_istio

release-notes_istio
d1b5720d33171b454286ffb13b01cab5cb6e50aa
link
/test release-notes_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

emm, I just recalled that k8s resource name doesn't allow ., we should add validation for revision, right? @howardjohn

Looks like the k8s name allows . in resource name from https://kubernetes.io/docs/concepts/overview/working-with-objects/names/

Yeah it is supported - but we don't need to allow it for revision if its going to cause issues. I don't feel strongly either way, as long as we can ensure it actually does work with .

Close this as . is not allowed in revision, need to replace it with -.


Persistent Service Logs

Support persistent service logs so each services logs can be viewed/retrieved

DoltLab Docs explain service log viewing/retrieval.


Check array inside an array function

let array1 = [1,2,3]
let array2 = [1,2]
array1.containsArray(array2) // return true or false
Need this extension for Array.

http://stackoverflow.com/a/25714995/4335588

extension Array {
func arrayContainsArray<S: SequenceType where S.Generator.Element: Equatable>(lookFor: S) -> Bool {
for item: S.Generator.Element in lookFor {
if self.contains(item) == false { // Cannot convert value of type 'S.Generator.Element' to expected argument type '@noescape _ throws -> Bool'
return false
}
}
return true
}
}
couldnt make it work as an extension

After a little bit of playing around, I got it right. Here is the code:
extension Array where Element : Equatable {
    func arrayContainsArray(lookFor:[Element]) -> Bool {
        for item in lookFor {
            if self.contains(item) == false {
                    return false
            }
        }
        return true
    }
}

The reason for previous issue is that when you referenced self.contains, the self's Element type may not be equatable. There is a type mismatch at self.contains(item). You could solve this by constraining the method to arrays whose elements are equatable.

Fix issue #17 is not working when I use
let arr = [1,2,3,4]
let arr2 = [1,2,3]

I'm just going to comment it out inside the code.

I think it does.


sensors couldn't be setup

Hi,
I've installed the APCUPSD correctly on a windows machine.
My model is a Back-UPS ES 850G2. The IP address indicated by the daemon is <IP_ADDRESS> but is different from the machine on which it is running. My Home Assistant is installed as VirtualBox image. So both programs are running on different systems.
The error logs can be found below.
Regards,
Jens
Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/components/apcupsd/__init__.py", line 49, in setup apcups_data.update(no_throttle=True) File "/usr/src/homeassistant/homeassistant/util/__init__.py", line 239, in wrapper result = method(*args, **kwargs) File "/usr/src/homeassistant/homeassistant/components/apcupsd/__init__.py", line 85, in update self._status = self._get_status() File "/usr/src/homeassistant/homeassistant/components/apcupsd/__init__.py", line 80, in _get_status return self._parse(self._get(host=self._host, port=self._port)) File "/usr/local/lib/python3.8/site-packages/apcaccess/status.py", line 37, in get sock.connect((host, port)) socket.timeout: timed out 2020-11-23 12:27:14 ERROR (MainThread) [homeassistant.setup] Setup failed for apcupsd: Integration failed to initialize. 2020-11-23 12:27:14 ERROR (MainThread) [homeassistant.setup] Unable to prepare setup for platform apcupsd.binary_sensor: Unable to set up component.

I have made the decision to archive this repository. Please see the README for more information.


-Confirm switch does not work for Remove-SPOSite and Remove-SPODeletedSite

In SharePointOnlinePowerShell for the commands Remove-SPOSite and Remove-SPODeletedSite, the -Confirm switch does not seem to work. When using them I still get prompted for confirmation, similair to not using the switch.
Name                                   Version
----                                   -------
Microsoft.Online.SharePoint.PowerShell 16.0.21411.12000

Hello @LuckyLub
How are you? tested to see if we have to impact any documentation, with the same exact version and did not experience that.
Keep in mind there is now a newer version of the module.

@get-itips Thank you very much for the contribution and sharing this explanation. @LuckyLub Hope this comment is helpful for you. If you see a documentation update is required, please feel free to open an issue for the same. We proceed here to close it. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.


Copy the login key then paste it into the CLI to manually login

Which Specific Feature is your question related to?
amplify pull --appId xxxx --envName staging
Couldn't automatically log you into the Amplify CLI
Copy the login key then paste it into the CLI to manually login.
Provide additional details e.g. code snippets

Hey @kumar-collab :wave: thanks for raising this! As we begin to investigate this I have a few follow-up questions:

what version of the CLI are you using?
how was the CLI installed?
are you hitting "enter" in the CLI prompt when attempting to pull the app?

what version of the CLI are you using?
Sanjiv:/MVS/release1 (master) $ aws --version
aws-cli/1.19.112 Python/2.7.18 Linux/4.14.294-220.533.amzn2.x86_64 botocore/1.20.112
how was the CLI installed?
npm install -g @aws-amplify/cli
Are you hitting "enter" in the CLI prompt when attempting to pull the app?
yes

I have tried the following as well.

amplify diagnose --auto-send-on
Sanjiv:/MVS/app/project1018 (master) $ amplify pull --appId ddz38i3fxhc48 --envName staging

Learn more at https://docs.amplify.aws/cli/reference/diagnose/
This project has been opted in automatically to share non-sensitive project configuration files. you can opt out by running 'amplify diagnose --auto-send-off'
⠋ Creating Zip
File at path: '/MVS/app/project1018/amplify/backend/backend-config.json' does not exist
✖ Creating Zip

Hey @kumar-collab, tried replicating the this in Amazon Linux 2 instance and using the AWS instance connect mechanism to SSH into the instance. Observed the following.
on running a headless amplify pull the CLI prompts for the following.
Confirm login in the browser or manually paste in your CLI login key:

as the terminal does not support opening a new tab in the browser the terminal stays on the prompt.
on hitting enter I observe the following.
⠼ Confirm login in the browser or manually paste in your CLI login key:
🛑 Failed to authenticate with Amplify Studio: Provided token was invalid.
✔ An unexpected error has occurred, opt in to send an error report to AWS Amplify with non-sensitive project configuration files. Confirm  (y/N) · no
? Select the authentication method you want to use: (Use arrow keys)
❯ Amplify Studio
  AWS profile
  AWS access keys

does this align with what you are experiencing?
additionally, on selecting the profile and access key options do you also experience the following errors?
🛑 Invalid config undefined
Failed to get profile: Cannot read property 'accessKeyId' of undefined

Hey @ykethan . This aligns with the issue.
However it got resolved by installing a package.
After you install the package - sudo yum -y install xdg-utils
you can copy the CLI login key and then proceed

I am not able to paste the login key to terminal, it is not accepting any manual entries, how to paste the key?

Hey @JKKholmatov, could you let us know what browser are you utilizing? when running this command, which should open a new tab in the browser does it provide a CLI login key or a prompt to select yes or no.
I was unable to reproduce the behaviour when utilizing windows powershell.

Hey @JKKholmatov, could you let us know what browser are you utilizing? when running this command, which should open a new tab in the browser does it provide a CLI login key or a prompt to select yes or no. I was unable to reproduce the behaviour when utilizing windows powershell.

Hi! @ykethan Thank You for your quick response, I appreciate it.
Browser: Chrome
New tab: Provided CLI login key to copy paste.
After a while, i successfully logged in , it was my bad sorry.
I tried "ctrl + v" to paste in VSCode terminal, but then I found out that i should use "ctrl + shift + v"))

Hey @JKKholmatov, could you let us know what browser are you utilizing? when running this command, which should open a new tab in the browser does it provide a CLI login key or a prompt to select yes or no. I was unable to reproduce the behaviour when utilizing windows powershell.

Hi! @ykethan Thank You for your quick response, I appreciate it. Browser: Chrome New tab: Provided CLI login key to copy paste. After a while, i successfully logged in , it was my bad sorry. I tried "ctrl + v" to paste in VSCode terminal, but then I found out that i should use "ctrl + shift + v"))

After copying the CLI login key, where do I paste it? in the vscode terminal that is already running? If yes, I tried pasting by using "ctrl + shift + v" but it is not working. I also tried using "ctrl + v". Thank you as I await a favourable response

After copying the CLI login key, where do I paste it? in the vscode terminal that is already running? If yes, I tried pasting by using "ctrl + shift + v" but it is not working. I also tried using "ctrl + v". Thank you as I await a favourable response

Yes copy the key and paste it to the running VSCode terminal after CLI login key:

In my case, "Ctrl + Shift+ V" worked,

hey @elkee2003, as @JKKholmatov had pointed out you may not see the token pasted. In my reproduction windows 11 environment with terminal CMD ctrl + c should paste the token.


The permissions requested by this app are way over the top

When attempting to log in via github I am presented with a shocking list of permissions

This application will be able to read and write all public and private repository data. This includes the following:
Code
Issues
Pull requests
Wikis
Settings
Webhooks and services
Deploy keys
Collaboration invites

Why do you need them?

If you choose to login issuehub enables you to filter your private repositories as well as public ones. However, I don't believe that their API offers more specific scopes but I could be missing something. If you know how to resolve this I would be happy to merge a relevant PR.
https://developer.github.com/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/

There is the repo scope which Grants full access to private and public repositories.
and there is the public_repo scope which Limits access to public repositories
https://developer.github.com/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/#available-scopes


[api-minor] Include the document /Lang attribute in the textContent-data

These changes will allow a simpler way of implementing PR #17770.

The /Lang attribute is fetched lazily, with the first getTextContent invocation. Given the existing worker-thread caching, this will thus only need to be done once per PDF document (and most PDFs don't included this data).

This makes the /Lang attribute directly available in the textLayer, which has the following advantages:

We don't need to block, and thus delay, overall viewer initialization on fetching it (nor pass it around throughout the viewer).

Third-party users of the textLayer will automatically benefit from this, once we start actually using the /Lang attribute in PR #17770.
Please note: This also, importantly, means that the text reference-tests will then cover this code (which wouldn't otherwise have been the case).

/botio test

/botio-linux unittest

/botio test


Remove template paremeter from slices

Currently slices take a template parameter for their value_type, however most of the code expects it to be std::ptrdiff_t. Using another type (like std::size_t for instance) prevents from using dynamic_view or strided_view directly, and requires conversion constructors to get a slice of std::ptrdiff_t if we have a slice of something else.

Should it not be some difference_type or size_type?

The slices can be created regardless of any expression, so we don't have access to any meaningful difference_type or size_type.

The slices are also used with regular std::vector in xframe so we actually need to keep that tempalte parameter.


Aruha 1099 reached max retries: 4

[ARUHA-1099: (reached max retries: 4)]
Description
Use exponential backoff with different max retries for AWS communication
Review

[ ] Tests
[ ] Documentation
[ ] CHANGELOG

Deployment Notes
There are no deployment notes, cause changed part is related only to aws deployment scripts, and not to service.

@adyach Renamed: https://github.com/zalando-nakadi/bubuku/pull/106/commits/1a16f9224be38521cababfde7e22ee7ff231e74d

👍

:+1:

:+1:

👍


Recieved memory warning When applying filter on multiple images (UITableview)

Hi all ,
I am using uitableview cells , there are 9 cells in a screen . i am applying filters on iamges added in uitablevire cell . But when it starts memory jheaps jumps to 450+ while adding filters and app is crashing after throwing a memory warning.
i uses [[GPUImageContext sharedFramebufferCache] purgeAllUnassignedFramebuffers]; but no success.
following is code for bluring my images
GPUImagePicture *stillImageSource = [[GPUImagePicture alloc] initWithImage:[UIImage imageWithData:self.imageData]];
GPUImageGaussianBlurFilter *blurFilter = [[GPUImageGaussianBlurFilter alloc] init];
blurFilter.blurRadiusInPixels = 40.0f;
blurFilter.blurPasses = 0;
blurFilter.texelSpacingMultiplier=4;
[stillImageSource addTarget:blurFilter];

[blurFilter useNextFrameForImageCapture];
[stillImageSource processImage];

if (self.isCancelled){
    self.imageData=nil;
    stillImageSource=nil;
    blurFilter=nil;
}else{
    if ([self.delegate respondsToSelector:@selector(imageDownloaderDidFinishImage:blurrImage:)]) {
        [self.delegate imageDownloaderDidFinishImage:[UIImage imageWithData:self.imageData]  blurrImage:[blurFilter imageFromCurrentFramebuffer]];
        self.imageData=nil;
        [stillImageSource removeAllTargets];
        stillImageSource=nil;
        blurFilter=nil;
    }
}

Any help would be appriciated .

The memory management issue likely has nothing to do with GPUImage but rather how you're implementing it in a reusable cell architecture (table view)
Where in the lifecycle of a cell are you calling the code above?

Thanks for reply.

Thanks for reply.
I was calling this in cell for row at index path. so if there were 10
images simultaneously processing app received memory warning . I solved
this via implementing local paging . 3 images at one time processed and
remains in queue. And completion of one i push next in to the queue.
On Thu, Apr 23, 2015 at 12:13 AM, MrBendel<EMAIL_ADDRESS>wrote:

The memory management issue likely has nothing to do with GPUImage but
rather how you're implementing it in a reusable cell architecture (table
view)
Where in the lifecycle of a cell are you calling the code above?
—
Reply to this email directly or view it on GitHub
https://github.com/BradLarson/GPUImage/issues/1953#issuecomment-95307735
.


Fix m_suppress_notifications

m_suppress notifications in the discord api is 1 << 12 (4096) but we have it as 1 << 9 (512) currently.

Please reopen your PR against the dev branch

thanks for the report, I've fixed this :)


Add component and subcomponent instance binding.

Changes:

Added functionality
Removed @ReflectBug
Added a test for subcomponent instance binding.

Related to: #136

I've reworked this a bit in #151 to prevent Scope and Scope.Builder from knowing anything about components or being mutable.


[Monitor] Bug fix for correcting the ISO values

Packages impacted by this PR
@azure/monitor-query
Issues associated with this PR

Customer reported over email thread

Describe the problem that is addressed by this PR
There was a bug in v 1.0.4 that the durations for Duration alias twentyFourHours and fortyEightHours missed a T in the ISO format. They should have been PT24H and PT48H respectively. This PR and the release for v1.1.1 is for fixing that.
Checklists

[x] Added impacted package name to the issue description
[x] Added a changelog (if necessary)

API change check
API changes are not detected in this pull request.

@KarishmaGhiya Please add the PR Description. This would help the reviewers to understand the underlying issue, design choices, chosen design, test cases, etc.

/azp check-enforcer evaluate

/check-enforcer evaluate


feat(noRestrictedImports): add import_names and allow_import_names settings

Summary
Extend noRestrictedImports with the option to use importNames and allowImportNames to specify the set of (dis)allowed imports.
Motivation:

The no-restricted-imports ESLint provides the feature.
Personal need: I needed it to make sure that when using the react-i18next library, I'm always retrieving the t function from the useTranslation hook, instead of using import { t } from 'i18next'.

Example Configuration
{
    "options": {
        "paths": {
            "lodash": "Using lodash is not encouraged",
            "underscore": "Using underscore is not encouraged",
            "import-foo": {
                "importNames": ["Bar"],
                "message": "Please use Bar from /import-bar/baz/ instead."
            },
            "import-bar": {
              "allowImportNames": ["Bar"],
              "message": "Please use only Bar from import-bar."
            }
        }
    }
}

Test Plan
Extensive snapshot tests for all different variations of import, import() and require() are included in this PR.

One thing which I'm not sure about, and which somebody else might be able to explain to me:
What is the reason for AnyJsImportLike (now renamed to AnyJsImportSourceLike) to target JsModuleSource instead of JsImport, just to then ignore all ocurrences of JsModuleSource that are not within a JsImport?

The compile errors must have snuck in during git rebase, will have a look at them later.

You may need to rebase, because currently there's a lot of unrelated commits included. Note that I recently did some work on the rule in the next branch, so it might be best to rebase on there instead of main.

You may need to rebase, because currently there's a lot of unrelated commits included.

There actually are no unrelated commits included, it's just a large amount of changes.
I'll split off the changes to framework code into one or more separate PRs to keep this PR cleaner.

Note that I recently did some work on the rule in the next branch, so it might be best to rebase on there instead of main.

Thanks for the pointer! I had a look at the changes in next. In my opinion, it might make sense to split off the extensions done in next into a fully separate noPackagePrivateImports rule altogether, because, except for the fact it's also analyzing imports, it's fully orthogonal to the rest of noRestrictedImports as implemented e.g. by the corresponding ESLint (and this PR).

In my opinion, it might make sense to split off the extensions done in next into a fully separate noPackagePrivateImports rule altogether, because, except for the fact it's also analyzing imports, it's fully orthogonal to the rest of noRestrictedImports as implemented e.g. by the corresponding ESLint (and this PR).

Hm, I just went in the other direction, but you make a fair point :sweat_smile:

What is the reason for AnyJsImportLike (now renamed to AnyJsImportSourceLike) to target JsModuleSource instead of JsImport, just to then ignore all ocurrences of JsModuleSource that are not within a JsImport?

The intention of that node was to query the actual specifier string. For top-level, JsModuleSource was the very node we need, however for dynamic import and require() there aren't specific nodes for that, so we needed to use the generic nodes.

Sorry about the rebase, I got rid of AnyJsImportSourceLike and had to adapt all code. All previous review comments should be resolved now, though.

Fixed the last few issues. Should be ready for merge now :+1:
Possible future work (in a separate PR):

Support for * and ** wildcards in import paths using biome_service::matcher::pattern (will follow up with that after this PR is merged)
Code action for removing the restricted imports (and/or replacing them with the correct import)
Separate severity per restricted import source and/or per restricted import name (useful for refactoring codebases). The noRestrictedImports lint is so flexible it is basic
Tweak schemars (and serde/biome_deserialize) such that the mutually exclusive nature of importNames and allowImportNames is respected/validated

Really nice work, @cr7pt0gr4ph7 !
Only thing I can think of is that the naming of importNames vs allowImportNames is a little weak. It sorta makes sense within the context, but I think it would be clearer of it were restrictedImportNames vs allowedImportNames (not also the change in tense).

I experimented with different possibilities (preventImportNames, rejectImportNames, forbidImportNames, denyImportNames and other synonyms), but I arrived at the conclusion that when looking at the resulting 'biome.jsonfiles, just usingimportNames` is more readable & still clear due to context:
{
	"$schema"<EMAIL_ADDRESS>	"linter": {
		"rules": {
			"nursery": {
				"noRestrictedImports": {
					"level": "error",
					"options": {
						"paths": {
							"node:fs": "Importing from node:fs is forbidden",
							"bare-forbidden": {
								"importNames": [
									""
								]
							},
							"default-forbidden": {
								"importNames": [
									"default"
								]
							},
							"namespace-forbidden": {
								"importNames": [
									"*"
								]
							},
							"member-forbidden": {
								"importNames": [
									"forbidden1",
									"forbidden2",
									"forbidden3",
									"forbidden4",
									"forbidden5",
									"forbidden6",
									"forbidden7",
									"forbidden8",
									"forbidden9"
								]
							},
							"bare-allowed": {
								"allowImportNames": [
									""
								]
							},
							"default-and-member-allowed": {
								"allowImportNames": [
									"default",
									"allowed1",
									"allowed2",
									"allowed3",
									"allowed4",
									"allowed5",
									"allowed6",
									"allowed7",
									"allowed8",
									"allowed9"
								]
							},
							"namespace-allowed": {
								"allowImportNames": [
									"*"
								]
							},
							"member-allowed": {
								"allowImportNames": [
									"allowed1",
									"allowed2",
									"allowed3",
									"allowed4",
									"allowed5",
									"allowed6",
									"allowed7",
									"allowed8",
									"allowed9"
								]
							}
						}
					}
				}
			}
		}
	}
}

Support for * and ** wildcards in import paths using biome_service::matcher::pattern (will follow up with that after this PR is merged)

You might be interested in what @Conaclos is about to land: https://github.com/biomejs/biome/pull/4609
We plan to use that crate internally in our configuration

Thanks for the thorough response!
Maybe I could still suggest denyImportNames? But I'm happy either way :)

denyImportNames is a bit more self-explanatory, but importNames has the big advantage of being visually distinguishable from allowImportNames due to the different length, even when just skimming over a configuration file, which avoids mistakes. I'm usually always in favor of the self-explanatory name, but considering that these configurations may get pretty long in some cases. So I'd favor keeping importNames, but if general consensus favors a different name, that's also okay.
If no objections are made, this should be ready for merge now IMO.

Support for * and ** wildcards in import paths using biome_service::matcher::pattern (will follow up with that after this PR is merged)

You might be interested in what @Conaclos is about to land: #4609
We plan to use that crate internally in our configuration

Good pointer! Though even before #4609, RestrictedGlob is already available in biome_js_analyze.
I also left some notes on #4609.


Always provide undos

Any one-way commands should be accompanied with ways to undo them.
For example, disabling Notification Center.
I also came across this, which attempts to restore things like this.

Thanks for this. Thanks for dotfiles os x too, but it did way more than I bargained for. Just spent quite a bit of time re-enabling dashboard (I use it), animations (I like them), color schemes (I like purple), 12 hour mode (I'm non-military), resume in OS X (I like it), and resume in sublime (essential for my workflow). (For sublime, it's "remember_open_files": true in the user preferences). Some things like the dashboard can't be re-enabled with the GUI. Perhaps an interactive keyboard mode would be better, where the user says yes to each one?
Also, isn't disabling time machine potentially harmful? And same with disabling the sudden motion sensor for those that still use magnetic drives?


Update autorest version to prerelease 3.0.0-alpha.20240715.3

Generated by Autorest Regen Preview build 20240715.3Triggered from pull request: https://github.com/Azure/autorest.csharp/pull/4917

API change check
API changes are not detected in this pull request.

API change check
API changes are not detected in this pull request.

API change check
API changes are not detected in this pull request.

API change check
API changes are not detected in this pull request.

API change check
API changes are not detected in this pull request.

API change check
API changes are not detected in this pull request.

API change check
API changes are not detected in this pull request.

API change check
API changes are not detected in this pull request.

API change check
API changes are not detected in this pull request.

API change check
API changes are not detected in this pull request.

API change check
API changes are not detected in this pull request.


Component Modal - this

Overview of the problem
Buefy version: [0.4.2]
Vuejs version: [2.3.4]
OS/Browser: Chrome 59.0.3071.115
Description
When opening the modal through script as a component modal the this stays mapped to the calling objects VueJS vm in DEV. However, in production the modal's this does not know anything about the calling objects vm, so plugins/components that are loaded to that vm are not usable.
For example, the <b-input> tags do not render.
createContact(event) {
    this.$modal.open({
        component: contactModal,
        width: 500,
        props: {
            id: this.$route.params.id,
            positions: this.positions
        },
        onCancel: this.updateContacts
    })
},

Steps to reproduce

Create a form component using Buefy elements
Create a calling component with an action button
Action button should trigger a method which calls this.$modal.open()
Run using npm run dev, and compare npm run build deployed behavior

Expected behavior
I expect that the Buefy components, the vuex state, and any other plugins to be available to the modal component as they are in DEV.
Actual behavior
The <b-input> tags are in the source code, but they do not render any visual objects.

This is a known issue, the programmatic modal is created outside of the main vue instance, that's why there is the non-programmatic modal. I will add a disclaimer for that on docs.

@rafaelpimpa , you should also include in your note that Buefy components will also not be available.


Atlast initial migration error

atlas migrate push pos-db --dev-url "docker://postgres/15/dev?search_path=public"
Error: sql/migrate: read migration directory state: sql/migrate: execute: executing statement "ALTER TABLE `posts` ADD INDEX `post_author` (`user_id`), DROP FOREIGN KEY `posts_ibfk_1`, ADD CONSTRAINT `post_author` FOREIGN KEY (`user_id`) REFERENCES `users` (`id`) ON UPDATE NO ACTION ON DELETE CASCADE;" from version "20230802063037": pq: syntax error at or near "`"

Hey. PostgreSQL is using double quotes ", not backticks ` for qualifying. Your SQL looks like MySQL, nit PostgreSQL.


Consume onchain datasets fail if the view function called has input parameters

Describe the bug
Creating function call datasets fail if the function has input parameters. This is because the connectivity_check under pay_for_access_service fails with error AssetNonConsumable with code 2. This error can be traced to the call to the provider that responds with "missing parameters".  This error does not happens if the function call is made to a function without parameters. Please note that the error is not at the moment of consuming but when an attempt to pay for access is done
To Reproduce
Steps to reproduce the behavior:
Using: GORLI
Create two wallets alice_wallet and bob_wallet
 name = "Uniswap v2 function call"
contract_address = "0x7a250d5630B4cF539739dF2C5dAcb4c659F2488D"
contract_abi = {
 		"inputs": [
 			{
 				"internalType": "uint256",
 				"name": "amountIn",
 				"type": "uint256"
 			},
 			{
 				"internalType": "address[]",
 				"name": "path",
 				"type": "address[]"
 			}
 		],
 		"name": "getAmountsOut",
 		"outputs": [
 			{
 				"internalType": "uint256[]",
 				"name": "amounts",
 				"type": "uint256[]"
 			}
 		],
 		"stateMutability": "view",
 		"type": "function"
 	}

# #create asset
(data_nft, datatoken, asset) = ocean.assets.create_onchain_asset(name, contract_address, contract_abi, alice_wallet)
print(f"Just published asset, with did={asset.did}")

to_address = bob_wallet.address
amt_tokens = ocean.to_wei(10)  # just need 1, send more for spare
datatoken.mint(to_address, amt_tokens, alice_wallet)

order_tx_id = ocean.assets.pay_for_access_service(
    asset,
    bob_wallet,
    service,
    consume_market_order_fee_address=bob_wallet.address,
    consume_market_order_fee_token=datatoken.address,
    consume_market_order_fee_amount=0,
)

This will produce the following error:
raise AssetNotConsumable(consumable_result)
ocean_lib.agreements.consumable.AssetNotConsumable: 2

Expected behavior
Access to the asset should be granted, the call should not fail
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: MacOS
Version 1.6.1

Additional context
Add any other context about the problem here.

To summarize:

pay_for_access_service  tries to call provider, to figure out if the asset is consumable
but since this asset requires userdata, provider will reply that the asset is NOT consumable

Fix:

add userdata to pay_for_access_service, since is_consumable is called (https://github.com/oceanprotocol/ocean.py/blob/ce8d275259dcc17636c871ffa68fca0b1c2cb970/ocean_lib/ocean/ocean_assets.py#L827)


Update the last three summit pages to point to YouTube playlist

Is your feature request related to a problem? Please describe.
The event pages read like the events are still in the future.
Describe the solution you'd like
The first paragraph should be clear the event was in the past, link to the new YT playlists, and note the details below are for reference.

[ ] APAC 2020 Summit Page
[ ] Fall 2020 Summit Page
[ ] Spring 2020 Summit Page

Additional context
Add any other context or screenshots about the feature request here.

Updates available here: https://innersourcecommons.net/events/

Thanks @voborgus


CI: sync NCTL upload wrapper from 1.4.5

Changes:

pulls working file from release-1.4.5

bors r+


v3.0.0

To-do
NOTE: This to-do list can be changed anytime soon.
Fixes

[x] #89
[x] #91
[x] #105

New features

[x] Add option to ignore missing chapters #70 #95
[x] Add support for oauth2 private client (I GOT THE PERSONAL TEST API CLIENT)
[x] #99
[ ] #106
[x] #104

Breaking changes

[x] Change --path behaviour to absolute path with placeholders support #67 #68 #85 #88
[x]  #77

Enhancements

[x] Show X-Request-ID (from last successful request) to users if they encountered Unhandled HTTP error
[x] Refactor base codes using ruff linter and black formatter
[x] Make sure missing dependencies error is closing the application (do not ignore it)
[x] #87
[x] #103

Documentation

[ ] Fix missing and typo documentation
[ ] Fix missing newly added options and features

[ ] Add new authentication method (oauth)
[ ] Add guide for new authentication (how to create client id and client secret in MangaDex auth)
[ ] Add all value explanation in --group option
[ ] will be added more...

[ ] Separate advanced usages (each advanced usage has it own page)
[ ] Add black formatter badge in README
[ ] Add migration guide from v2.x to v3.x

Deprecated

[ ] Remove --no-progress-bar option
[ ] Remove --verbose option (maybe ?)

Miscellaneous
Will be added soon....

All new features and bug fixes are almost finished !
Let's hope it didn't become dumpster fire when it's released.

please don't remove --no-progress-bar option
its useful when running in k8s

please don't remove --no-progress-bar option its useful when running in k8s

You can use --progress-bar-layout=none as alternative for --no-progress-bar. The --progress-bar-layout is created so user can choose the progress bar can be stacked or be as it is (default) or none at all (disabled).


Use azure for everything

Checklist

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

References:

fixes #22

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

Looks like it OoMs. bummer.