Class \Illuminate\Support\Testing\Fakes\NotificationFacadeFake was not found while trying to analyse it

Larastan Version: 0.6.1
--level used: 0

Description
I've a custom setup for asserting notifications due to special requirements.

In \Tests\TestCase I add my \Tests\NotificationAssertionTrait
This trait makes use of a custom \Tests\NotificationFacade extending the one from Laravel
Has a custom fake method so I can use my own \Tests\NotificationFake

I've create a reproducible project with:

the code for all the above => https://github.com/mfn/larastan-notification-trait/tree/master/tests
a phpstan/larastan configuration => https://github.com/mfn/larastan-notification-trait/blob/master/phpstan-tests.neon
and a github action showing how it fails => https://github.com/mfn/larastan-notification-trait/runs/912461548?check_suite_focus=true#step:5:14

 ------ --------------------------------------------------------------------
  Line   TestCase.php
 ------ --------------------------------------------------------------------
         Class \Illuminate\Support\Testing\Fakes\NotificationFacadeFake was
         not found while trying to analyse it - discovering symbols is
         probably not configured properly.
         💡 Learn more at https://phpstan.org/user-guide/discovering-symbols
  18     Class \Illuminate\Support\Testing\Fakes\NotificationFacadeFake was
         not found while trying to analyse it - discovering symbols is
         probably not configured properly.
         💡 Learn more at https://phpstan.org/user-guide/discovering-symbols
 ------ --------------------------------------------------------------------

I even tried to minimize the code triggering this, removing actual body of code and such in this commit:

https://github.com/mfn/larastan-notification-trait/commit/3e25813dd8cc8b9377fe760cbd342522d70e75c0
but GHA still fails https://github.com/mfn/larastan-notification-trait/runs/912475272?check_suite_focus=true#step:5:13

I've literally no idea where it does come up with that name or the line number (!) and where the problem lies 🤷♀

Fun fact: in tests/NotificationFacade.php I could change
use Illuminate\Support\Facades\Notification;

class NotificationFacade extends Notification
{
}

to
use Illuminate\Support\Facades\Cache;

class NotificationFacade extends Cache
{
}

and then get

Class \Illuminate\Support\Testing\Fakes\CacheFake was not found while trying to analyse it

Class \Illuminate\Support\Testing\Fakes\NotificationFacadeFake was
not found

I think the classes name is Illuminate\Support\Testing\Fakes\NotificationFake
https://github.com/illuminate/support/blob/63a50a0ad26a336907b40bd59621b6b947c8eb41/Testing/Fakes/NotificationFake.php#L16
not NotificationFacadeFake

Of course, that's the perplexing thing 😄 You won't find the name NotificationFacadeFake anywhere in the sample repo!

I failed to mention but as @szepeviktor tried it themselves, removing larastan from the phpstan config "works":

https://github.com/mfn/larastan-notification-trait/pull/1/files
https://github.com/mfn/larastan-notification-trait/pull/1/checks#step:5:10

[OK] No errors

I'm only a himslef :)

Tried my best to not assume anything 😏

NotificationFacadeFake was coming from this method.
We weren't checking if the fake facade actually exists. Added the check with 852c131 Can you try the latest master?
Also, you need to add @method annotations to the NotificationFacade if you want PHPStan to understand the method calls. Or you can add @mixin \Tests\NotificationFake

I can confirm the issue is fixed with the change!

Also, you need to add @method annotations to the NotificationFacade if you want PHPStan to understand the method calls. Or you can add @mixin \Tests\NotificationFake

Awesome, phpstan even reminded me about that with a "call to an undefined static method"
Is there a release planned soon? Otherwise I can go with the dev alias 0.6-dev I guess.
All solved and so quickly, thank you very much 🙇

Is there a release planned soon?

I want to make a new release when there is new PHPStan version is released. There are some bug fixes there that Larastan benefits.

@canvural @szepeviktor I am having a similar issue using the Maatwerk Excel package's Excel facade calling the Excel::fake() during my tests and getting:
Class \Illuminate\Support\Testing\Fakes\ExcelFake was not found while trying to analyse it - discovering symbols is probably not configured properly.
         💡 Learn more at https://phpstan.org/user-guide/discovering-symbols

The actual facade is located in: Maatwebsite\Excel\Fakes.
Should that error also be fixed with https://github.com/nunomaduro/larastan/commit/852c1313e1c94feab8da8055d0abceda97a27586, or should I open a new issue?

@johanvanhelden Are you using 0.6.2?

I thought it was still unreleased because a composer update just now only updated to 0.6.1.
But after removing the package and re-requiring it's at 0.6.2 now and indeed the issue is fixed, thanks!


[WIP] - Use cloudflare-rs for Cloudflare API calls

Proposal
The Argo Tunnel team has put together an open source Rust library for interacting with Cloudflare's v4 API endpoints. It handles wrapping reqwest, constructing http requests to the various endpoints' specifications, and parsing / extracting both API success and API failure responses. Currently there is only partial support for WorkersKV (mostly untested), but extending the library is relatively straight forward in terms of pattern matching, though the Rust can be daunting to a beginner.
This PR illustrates one possible approach to wrapping and using this library in Wrangler.
To give a sense of the work involved in adopting this as our API client, I've linked the various artifacts of my process so far below:
Contributing to cloudflare-rs
A proposal PR I made to the tunnel team about how to structure service modules to better represent usage:
https://github.com/cloudflare/cloudflare-rs/pull/2
The meat of the proposal is in the Readme and the directory structure (specifically the zone module which has been broken out into a root with the domain data structures and files containing the individual endpoints)
Proposed WorkersKV module (cloudflare-rs module)
An active PR applying the above module structure to the existing WorkersKV module, as well as fixing a bug in the endpoint: https://github.com/cloudflare/cloudflare-rs/pull/7
Note: it is expected that this PR does not pass CI, due to the outstanding PR against the cloudflare-rs repo that updates the CreateNamespace endpoint.

closing in favor of #392


Removing odd docset info

:warning: Validation status: warnings

File
Status
Preview URL
Details

docs-ref-autogen/microsoft-cognitiveservices-speech-sdk/index.yml
:warning:Warning
View (azure-node-latest)
Details

previewtemp/breadcrumb/toc.yml
:white_check_mark:Succeeded

previewtemp/docfx.json
:white_check_mark:Succeeded

previewtemp/docs-ref-autogen/BoundingBox.yml
:white_check_mark:Succeeded

previewtemp/docs-ref-autogen/Map.yml
:white_check_mark:Succeeded

previewtemp/docs-ref-autogen/index.yml
:white_check_mark:Succeeded

previewtemp/docs-ref-autogen/toc.yml
:white_check_mark:Succeeded

docs-ref-autogen/microsoft-cognitiveservices-speech-sdk/index.yml

[Warning] Uid(microsoft-cognitiveservices-speech-sdk) has already been defined in docs-ref-autogen/microsoft-cognitiveservices-speech-sdk/index.yml.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:warning: Validation status: warnings

File
Status
Preview URL
Details

_dependentPackages/CommonPlugins/tools/JoinTOC.ps1
:warning:Warning

Details

docs-ref-autogen/microsoft-cognitiveservices-speech-sdk/index.yml
:warning:Warning
View (azure-node-latest)
Details

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

docfx.json
:white_check_mark:Succeeded

previewtemp/breadcrumb/toc.yml
:white_check_mark:Succeeded

previewtemp/docfx.json
:white_check_mark:Succeeded

previewtemp/docs-ref-autogen/BoundingBox.yml
:white_check_mark:Succeeded

previewtemp/docs-ref-autogen/Map.yml
:white_check_mark:Succeeded

previewtemp/docs-ref-autogen/index.yml
:white_check_mark:Succeeded

previewtemp/docs-ref-autogen/toc.yml
:white_check_mark:Succeeded

_dependentPackages/CommonPlugins/tools/JoinTOC.ps1

Line 165: [Warning] Error happened in execute customized script: Container cannot be copied onto existing leaf item.

docs-ref-autogen/microsoft-cognitiveservices-speech-sdk/index.yml

[Warning] Uid(microsoft-cognitiveservices-speech-sdk) has already been defined in docs-ref-autogen/microsoft-cognitiveservices-speech-sdk/index.yml.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Fix the docs to import designs in meshery

Notes for Reviewers
This PR aim to provide clearer and more accurate instructions for users.
Signed commits

Yes, I signed my commits.

🚀 Preview for commit 8d9971a36888202ffe0f117f61e9e37663984909 at: https://66119b8f2f17ff1ae1c0184f--meshery-docs-preview.netlify.app

@11happy Let's discuss this on Meshery Dev call, add this as an agenda item to the meeting minutes , if you would, please.

Sure @vishalvivekm

Hello @vishalvivekm can you please help me why the PR may be failing & also what if any changes are required.
Thank you


Data Management, representation and implementation

We are moving away from a config definition that is used by the DFK to initialize resources to a model in which the user uses a Config class that takes initialized resources as parameters. This discussion is here: https://github.com/Parsl/parsl/issues/133. Each executor in this model represents an elastic pool of compute resources. How data assets/methods should map to this model is unclear given only preliminary work has been done on the representation of data management in our current static config based system.
Some terminology

We have the concept of a DataManager(DM) which is an executor private to the DFK. The DM is simply responsible for moving files
An endpoint(EP) is a block of attributes that define the transfer methods and details like filepaths, ports, auth.
An executor represents a collection of resources gathered from a computation site. For a single computation site like NERSC you could have several executors that handle specific queues, node requirements etc.

The DM assumes that it can move files between any pair of EPs. Since the DM is generally hidden from the user one possibility is that it can be a default kwarg like this :
Config(data_manager=DataManager(threads=4), .... )
If the EP definition naturally matches to the notion of an executor, the new class structure and our implementation of the executors should be updated to match that. I do not know if this is the case.

So to summarize, I think the question is: is the current model (one EP / executor) sufficient, or do we need to tweak it?
@danielskatz @lukaszlacinski @kylechard Does this match your take on yesterday's Slack discussion? If not, can you flesh out your concerns here and we'll go from there?

where's the picture?

I think we should support multiple schemes for accessing the same physical location on disk. In that way the user can specify fallback methods for moving data, in case the primary method fails. This could also easily provide rudimentary load-balancing (have a transfer scheme chosen at random).

I am copying and pasting this from the current DataManager docstring. We shouldn't lose it, but it is not describing what is currently implemented, so I do not think it belongs in the docstring.

In general a site where remote file is going to be staged in is unknown until
the Executer submits an app that depends on the file. However, in most practical
cases, a site where an app is executed and a file needs to be staged in is
known. Such cases should be detected by DataManager to optimize file
transfers. Possible cases are:
1. Config defines one site only.
2. Config defines several sites but all of the sites share the filesystem /
use the same Globus endpoint.
3. Config defines several sites with different Globus endpoints but a user
specified explicitely that apps must be executed on a particular site.

I believe this is safe to close with the assumption that the current implementation is being documented for 0.6.0.


[CT-583] [Bug] adapter.load_relation does not exist

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
On Spark, the following fails:
{% if  adapter.load_relation(this) is not none %}
{% endif %}

with this error:
'dbt.context.providers.RuntimeDatabaseWrapper object' has no attribute 'load_relation'

Expected Behavior
No error.
Steps To Reproduce
In DBT cloud or CLI with Spark connector.
dbt-core 1.0.4
dbt-spark 1.1.0
Paste the code into a Scratchpad and press compile, or put in any .sql and run dbt compile.
Relevant log output
No response
Environment
dbt-core 1.0.4
dbt-spark 1.1.0

What database are you using dbt with?
other (mention it in "Additional Context")
Additional Context
I'm not sure if this is Spark specific or applies to other adapters.
adapter.get_relation() can be used as a workaround.

Hey @jarno-r, thanks for opening!
load_relation isn't an adapter method, it's a macro in the global project here. So this should work if you just call it as load_relation (or dbt.load_relation) instead.
I also see you're using dbt-core v1.0.4 with dbt-spark v1.1.0, which are incompatible. Core + plugins are compatible at the minor-version level

@jarno-r You're totally right! Sorry about that. I just opened a quick PR to get those docs fixed: https://github.com/dbt-labs/docs.getdbt.com/pull/1399

Closing as resolved by update to user docs, rather than a code change


Cert Manager failing to renew certificate

Describe the bug:
We have two CNAMES pointing to the same Kubernetes endpoint. Cert-Manager created certificates for both of these. However, when it came to renewal only one of these has been renewed. The other one repeatedly fails. The logs show the following at the point of the first renewal attempt.
I0413 19:55:52.000605       1 conditions.go:173] Setting lastTransitionTime for Certificate "cname1-cert" condition "Issuing" to 2021-04-13 19:55:52.000594962 +0000 UTC m=+929621.340249207
E0413 19:55:52.206159       1 controller.go:158] cert-manager/controller/CertificateKeyManager "msg"="re-queuing item  due to error processing" "error"="Operation cannot be fulfilled on certificates.cert-manager.io "cname1-cert": the object has been modified; please apply your changes to the latest version and try again" "key"="prod1/cname1-cert"
E0413 19:55:52.219816       1 sync.go:132] cert-manager/controller/certificaterequests-issuer-acme "msg"="error issuing certificate request" "error"="found Order resource not owned by this CertificateRequest, retrying" "related_resource_kind"="ClusterIssuer" "related_resource_name"="letsencrypt-prod" "related_resource_namespace"="" "related_resource_version"="v1" "resource_kind"="CertificateRequest" "resource_name"="cname1-cert-76bvn" "resource_namespace"="prod1" "resource_version"="v1"
After this the logs show cert-manager retrying and each retry fails with the
‘found Order resource not owned by this CertificateRequest, retrying’ error.
There are two Certificate Requests in the cluster for the failing CNAME. The first is for the original creation of the certificate. The second is for the renewal. This does not have any events on it. Kubectl get certificaterequest shows it with no value under the Ready column. I suspect that deleting the Certificate Requests will probably get it to work. We haven’t done this as we would like to understand the root cause. Cert-Manager has renewed dozens of certificates over the past year this is the first time we have had an issue.
Expected behaviour:
The certificate to have been renewed
Steps to reproduce the bug:
We don't know how to reproduce
Anything else we need to know?:
Environment details::

Kubernetes version: 1.18.10
Cloud-provider/provisioner: Azure AKS
cert-manager version: 1.0.3
Install method: e.g. helm/static manifests Helm

/kind bug

We have the same issue sporadically happening on v1.2.0.
Have to manually fix via deleting CertificateRequest
Hopefully being able to set history to 1 might help here: https://github.com/jetstack/cert-manager/issues/3958

We are also affected by this bug.
We always use the latest version of cert-manager.

@harshaperera532 ss this issue a duplicate of #3501?

Hi, thanks for the issue and sorry for taking so long to reply.

One difference with this cert compared to the others on the cluster is that there are two ingresses using it. They have the same domain but different paths which is used to route to different services. Is this causing the problem?

Are these Certificates both created using ingress-shim?

Hello @irbekrm, Yes both of these ingresses use ingress shim (have cert manager annotations).

@harshaperera532 have you tried v1.5.2 of cert manager?

One difference with this cert compared to the others on the cluster is that there are two ingresses using it. They have the same domain but different paths which are used to route to different services. Is this causing the problem?

It seems like another accurence of a bug reported in https://github.com/jetstack/cert-manager/issues/1888, where two Ingress resources are configured with the same FQDN and pointing to different Secret resources.
For example:
kind: Ingress
spec:
  rules:
  - host: example.some.mael-valais-gcp.jetstacker.net
    http:
      paths:
      - path: /foo
  tls:
  - secretName: example-foo
    hosts:
    - example.some.mael-valais-gcp.jetstacker.net
---
kind: Ingress
spec:
  rules:
  - host: example.some.mael-valais-gcp.jetstacker.net
    http:
      paths:
      - path: /bar
  tls:
  - secretName: example-bar
    hosts:
    - example.some.mael-valais-gcp.jetstacker.net

The result is that one of the certificates becomes ready, and the other one stays unready:
NAME          READY   SECRET        AGE
example-foo   False   example-foo   60s
example-bar   True    example-bar   60s

I don't know any workaround for this issue, but #1888 has been marked as a good first issue! 😅

/remove-lifecycle stale

@pierluigilenoci was this issue resolved in a newer version of cert manager?

/remove-lifecycle stale

/remove-lifecycle stale

/remove-lifecycle stale

/remove-lifecycle stale

/remove-lifecycle stale

/remove-lifecycle stale

/remove-lifecycle stale

@harshaperera532, is this still an issue?

@harshaperera532, is this still an issue?


Upgrade to Scalacheck 1.15.0 and use Dotty build of it

Unlike #235, this PR adjusts the scalacheck dependency to use the Dotty version

Closing in favor of #231


Rakefile:94-103: Enable xcop when xml/html files will be added to the project. So far there is no profit. require "xcop/rake_task" desc "Validate all XML/XSL/XSD/HTML files for formatting" Xcop::RakeTask.new :xcop do |task| task.license =...

The puzzle DEV-b61521b4 from #DEV has to be resolved:
https://github.com/dgroup/lazylead/blob/effb8df7817ea687976e8c30f671cad79560b515/Rakefile#L94-L103
The puzzle was created by rultor on 21-Jun-22.
role: DEV.
If you have any technical questions, don't ask me, submit new tickets instead. The task will be "done" when the problem is fixed and the text of the puzzle is removed from the source code. Here is more about PDD and about me.

The puzzle DEV-b61521b4 has disappeared from the source code, that's why I closed this issue.


npm won't work/node bot.js won't work

(I crossed out my name in maroon)
When I ran the first command 'npm install discord.io winston --save', the "command prompt" in the top left corner changed to npm for a couple of seconds, then back to command prompt.
Then, I ran the second command 'node bot.js', and it couldn't find the file.
I have the bot file on my desktop and also in my personal folder. I have no idea what to do.

^bot file from my desktop^
P.S, I also changed 'winston' to my name, and it didn't work either.

This is what happened when I shift + right clicked inside of the file, and retyped the same commands. This is Windows Powershell.


feat(vehicle_velocity_converter): add speed_scale_factor

Description
Add speed_scale_factor parameter in vehicle_velocity_converter.
The parameter is intended to address several factors that induces velocity error, which include:

tire slip
tire radius calibration error

Related links

Tests performed
I tested on logging_simulator.launch.xml and verified that the speed_scale_factor is properly applied to the output topic.

Notes for reviewers

Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[x] I've confirmed the contribution guidelines.
[x] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.
[ ] The PR has been properly tested.
[ ] The PR has been reviewed by the code owners.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.
[ ] The PR is ready for merge.

After all checkboxes are checked, anyone who has write access can merge the PR.

@RyuYamamoto Thank you! I fixed it here: https://github.com/autowarefoundation/autoware.universe/pull/2641/commits/52009abf60e9becf30487dfd9a3e0750d667b41e


TagUI vs TagUI-Python

@kensoh, really excited by your new TagUI-Python as it opens up a whole new spectrum of possibilities in RPA applications, especially interfacing with those established machine learning and deep learning Python frameworks.
Not sure if the following have been documented somewhere,

I looked at the command sets between the two.
TagUI: https://github.com/kelaberetiv/TagUI#steps-description
TagUI-Python: https://github.com/tebelorg/TagUI-Python#api-reference
It seems that they are about the same. So is it correct to say that almost all the commands in TagUI are supported in TagUI-Python?

Can you highlight some major differences between the two (besides one written in TagUI script, and the other in Python)?

HI CK @ck81 thanks for your support and encouragement! Yes, I hope to bring TagUI automation features to a new user demographic - Python beginners to experts, data analytics folks, machine learning engineers, data scientists, etc. Below are comments on the commands set.
In this project's design, I try to bring over as much of the UI automation steps from TagUI as reasonably possible. Some steps will be not applicable because we are now in Python environment. For eg // or live step, py and r steps have no meaning in the context of Python environment.
There are also frame and popup step which is not portable over because TagUI live mode technically doesn't support that. api step is meaningless too, as Python's requests package is the typical way to access API on Python, with a mature ecosystem of tutorials and tried-and-tested robust functions.

The major difference would be TagUI for Python only has a subset of TagUI's features. TagUI is more like a framework by itself with features such as modules, repositories, datatables, auditing.
TagUI for Python is more like a foundational building block which Python users can develop to add their own preferred implementations of repositories, datatables, auditing etc as needed.
Though the features are lesser, when the project is less opinionated, it allows broader usage and easier customisation according to individual needs. Also, having the UI automation features of TagUI is already a big win for Python users, as the Python ecosystem amplifies its strengths and benefits.
The other difference as you pointed out would be the human languages syntax supporting 21 human languages versus TagUI for Python the functional declarations are base on English words.

Forgot to add, headless invisible mode is not enabled yet in TagUI for Python. It is technically possible to add a flag to support Chrome in headless mode, but I have not found a strong use case to do that.
Since the visible mode has its own Chrome TagUI user profile and session, it will not disrupt the user from working on something else while automation is running. Also, headless or not the resource consumption should be negligible.


Playing Error

Please describe your problem in as much detail as possible:
Further information:

Distube version: 3.3.2
discord.js version: 13.8
Node.js version: 16.13.2
Operating system: Ubuntu 20.04

Please provide the full error trace stack. I cannot reproduce this

And make sure you are using the latest @distube/ytdl-core version (4.11.4).

lite that error
evalmachine.<anonymous>:24
c[72],c[6]),(0,c[85])(c[11]),(0,c[41])(c[39],c[28],(0,c[66])()),(0,c[78])(c[Math.pow(6,2)+122+-119],c[new Date("Wednesday December 31 1969 19:00:14 CDT")/1E3])}catch(d){(0<c[0]||(((0,c[80])(c[60],c[88]),c[80])(c[21],c[88]),0))&&(0,c[17])((0,c[70])(c[6]),c[78],c[88],c[12])}try{2<c[91]&&(1<c[53]?(0,c[17])((0,c[80])(c[82],c[6]),c[78],c[39],c[5]):((0,c[45])(c[49],c[88]),c[78])(c[88],c[86])),(0,c[17])((0,c[85])(c[31]),c[41],c[88],c[75],(0,c[35])())}catch(d){}};Wka(ncode);
                                                                                ^
SyntaxError: Missing catch or finally after try
    at new Script (node:vm:100:7)
    at Object.exports.decipherFormats (/home/container/node_modules/@distube/ytdl-core/lib/sig.js:116:51)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async Promise.all (index 0)
    at async exports.getInfo (/home/container/node_modules/@distube/ytdl-core/lib/info.js:326:17) {
  name: 'PlayingError'
}

so that error only on linux system's
on my windows machine my bot haven't that error

Make sure you upgraded to<EMAIL_ADDRESS>Duplicated #271

i'll update it! but that's not wirking

working for me


ODC-7442: Integrate the tektonResults API in the PipelineRuns list

Story:
https://issues.redhat.com/browse/ODC-7442
Demo:
https://drive.google.com/file/d/1wOU249jQTvxGh1kX9QouOWPelp8_M0Us/view?usp=drive_link

/cc @vikram-raj

Updated the PR based on review comments. PTAL.

Ago repeat multiple time.

LGTM


About how to get backbone of RNA uesd in the fr3d_to_graph method

Dear carlos,
I've seen the question you proposed in the fr3d repository. Recently I tried and analysed the code on how to convert cif file to graph via fr3d. But I found the method you'v implemented through biopython didn't consider the non-standard residues. However in the RCSB PDB database there may exist non-standard residues because of natural mutations or modifications by human for some reasons. So you may get discontinuous graphs when you apply the  fr3d_to_graph method implemented in the present repository. What's more,  I'v also checked annot_df produced by fr3d and found that the annotation between base pairs do include non-standard residues if there are non-standard residues in the cif file.
I hope to have a discussion with you on that.

Hi @ghliu521 ! Thanks for getting in touch.
Yes I have not had a chance to carefully check the output of that function. Would you have a sample PDB we can focus on to start having a look?

Hi @cgoliver .You may try 1evv to have a look and check you code.
What I have forgotten to mention before is that although there are not so many non-standard residues, I think it's necessary to consider them when constructing RNA graph. If you don't consider non-standard residues in the get_bb method, you may get a final graph with some  nodes without atrributes. I've finished two ways to solve this bug, one is adding the  non-standard residues in the get_bb method, one is not considering the non-standard residues.
Look forward to hear from you.

Yes indeed. Should be an easy fix. The other thing to check is whether fr3d keeps base pairs for non-standard residues. Are you working on a PR?

Yes indeed. Should be an easy fix. The other thing to check is whether fr3d keeps base pairs for non-standard residues. Are you working on a PR?

Not Really.  I'd love to do that.

I asked because you said you had finished two ways to solve the bug. We are always happy to support contributions so if you feel they are in good shape for a PR please feel free. Otherwise we are planning on addressing the issue ourselves but might take a bit longer. Thanks!

Hi @cgoliver submit a PR. Please have a look.


add support for Mitsubishi AC SRK--ZMP-S serie (RKX502A007P remote control)

Home Assistant version 2022.6.7
SmartIR version 1.17.6
SmartIR configuration Base64 broadlink
Additional context
Created and tested by learning IR code of a RKX502A007P remote controller:
For the Mitsubishi AC SRK--ZMP-S serie ( SRK25ZMP-S, SRK35ZMP-S, SRK45ZMP-S)
Presently, includes "Operation Mode: Cool, Heat, Auto and Fan" with 4 "Fan Modes: Low, Mid, High, Auto"
With only the Swing mod
I propose the number code number 1136
1136.zip

Thanks!


ScalaDocChecker doesn't support comments inheritance

According to Scala documentation the comments have implicit inheritance:
http://docs.scala-lang.org/overviews/scaladoc/for-library-authors.html#comment-inheritance
https://wiki.scala-lang.org/display/SW/Syntax#Syntax-CommentInheritance
But ScalaDocChecker  requires comment for overridden methods in spite the fact that parent method has the correct one.

Scalastyle doesn't know about stuff outside of the current file, so if your parent class is in a different file, then there is no way for it to know if a method has already got scaladoc. One option would be to add a ignoreOverride parameter, which if true, ignores methods which have the override keyword. If this is acceptable, then a PR would be great :-)


Error in combined methods

Hi,
first of all I'd like to thank you for having shared your fixes on this project that seems abandoned by its first author.
We are experiencing some issue using the mongo new combined methods (like find_and_update, find_and_delete, etc.)
The reason seems related to the fact that the single wrapper method async_decorator cannot work with these kind of methods because, inside, mongomock actually calls two methods (i.e. find_one and delete) and both requires an await but the decorator is applied only on the outer method.
I attach below the stacktrace trying to call a find_one_and_delete:
old = <coroutine object async_decorator.<locals>.wrapped at 0x10ef8f140>

    def _find_and_modify(self, query, projection=None, update=None,
                         upsert=False, sort=None,
                         return_document=ReturnDocument.BEFORE, session=None, **kwargs):
        if session:
            raise_not_implemented('session', 'Mongomock does not handle sessions yet')
        remove = kwargs.get('remove', False)
        if kwargs.get('new', False) and remove:
            # message from mongodb
            raise OperationFailure("remove and returnNew can't co-exist")

        if not (remove or update):
            raise ValueError('Must either update or remove')

        if remove and update:
            raise ValueError("Can't do both update and remove")

        old = self.find_one(query, projection=projection, sort=sort)
        if not old and not upsert:
            return

>       if old and '_id' in old:
E       TypeError: argument of type 'coroutine' is not iterable

venv/lib/python3.9/site-packages/mongomock/collection.py:1328: TypeError

any idea on how this could be resolved?
Thank you
Matteo

My PR can fix this issue: https://github.com/gonzaloverussa/pytest-async-mongodb/pull/5

@maliffi can you confirm if the error was solved with the PR #5?


lnd_comp_mct code review and some minor changes

update iulog and shrlogunit implementation, update subname and write statements, add notes for nextsw_cday usage.

Thanks @apcraig!


Improve GetHashCode() implementations and their consistency with Equals()

#362 and more
make SourceLocation.Equals() and SourceLocation.CompareTo() consistent
use only immutable values in GetHashCode() calculations
avoid object.GetHashCode(); that calculates hash of reference
make a few more properties obviously immutable; remove private setters
BUT this leads to some static GetHashCode() values
add SyntaxTreeNode.GetEquivalenceHash()
correct important typo in TagHelperDescriptorComparer
ensure Equals() does not throw an NRE e.g. in LineMapping

Add lots of tests

not for all updated classes but enough to see impact of odd choices
assymetric Equals() implementations due to specificity in subclasses
some Equals() check for an interface implementation, not their class

nits:

remove redundant null checks e.g. when also done in base.Equals()
add StringComparer.Ordinal if StringComparison.Ordinal used in Equals()

@Eilon let's talk about the issues shown in new tests

@Eilon, @NTaylorMullen updated and ready to go.  would prefer to defer additional tests a bit...

:watch:

@NTaylor rebased and updated

:shipit:

Removed the shipit, looks like the casts to IReadOnlyCollection are breaking PR for travis-ci.
https://travis-ci.org/aspnet/Razor/builds/60466235

Added commit similar to that in aspnet/Mvc#2471

:shipit:

6384977


crash with Bookshelf

Issue description: The game crash when loading when using Bookshelf <IP_ADDRESS>9 and higher verion.
Steps to reproduce:

Have Bookshelf <IP_ADDRESS>9 or higher and Mekanism
Launch Minecraft

Version (make sure you are on the latest version before reporting):
Minecraft: 1.11.2
Forge: <IP_ADDRESS>5
Mekanism: <IP_ADDRESS>9
Crash log: https://pastebin.com/shfKZCcd

Please use the search as mentioned in the default issue template. #4473

This is on a different bit of code as the other ones though.
The other ones crash on a bit of unused text in OreDictManager.java.
This one crashes on a bit of used code in MekanismUtils.java.


doc: update changelog & bump cargo version

This commit will be used to release a new version

coverage: 94.328%. remained the same
when pulling 296f1548c224ae935768907b688244777f961395 on version-130-beta-1
into ee599838adb17684c745456c1c1b2e448c5cc907 on master.


fix: notify analytics sent before message sent

Analytics sent before message is actually sent.
It should only be sent after, and ideally should include the result of the send.

Fixed in https://github.com/WalletConnect/notify-server/pull/107


Check existence of virtual disk before subst

If the build was cancelled or something unexpected happens, the virtual
disk might not be unmounted successfully, failing all subsequent builds.
Let's check the existence of virtual disk before subst.
Example: https://builds.gradle.org/viewLog.html?buildId=41886577&buildTypeId=Gradle_Master_Check_PerformanceTest6bucket3&tab=buildLog&_focus=406#_state=406

@bot-gradle test RFN

OK, I've already triggered ReadyForNightly build for you.

@bot-gradle test AST

Sorry some internal error occurs, please contact the administrator @blindpirate

@bot-gradle test AST

Sorry some internal error occurs, please contact the administrator @blindpirate

@bot-gradle test AST

OK, I've already triggered AllSmokeTestsReadyForMerge build for you.

@bot-gradle test RFN

OK, I've already triggered ReadyForNightly build for you.

I merge master to this branch and fastforward on master to see if an already-built-commit triggers new build on master.


🚧 Search implementation

I have started with a basic search implementation. Currently it is only possible to filter pages, but I also had in mind to have more global search. This would require parsing the page contents (search already returns a Promise) but also a different element as it would allow jumping to anchors etc.
To discuss:
Setting optional keywords in the catalog config to manually define groups:
{
  path: 'button',
  title: 'Button component',
  component: require('...'),
  keywords: ['UI', 'controls']
}

Roadmap

[x] Filter pages (basic search)
[ ] Finalize styling
[ ] Parse page content (return anchors for headings / specimens)
[ ] Check performance for full indexing (web-worker? cache index?)

As promised, here are my thoughts. Nothing conclusive but I see several challenges with implementing search well:
Modularity
Generally, I'd prefer an approach where we don't couple Catalog too closely to a particular implementation. I think it would be valuable to offer a built-in solution but it has to be lightweight and more importantly replaceable by the user, e.g. by an Algolia search. So we should focus primarily on providing the necessary hooks to make that happen and then building the built-in solution on top of those hooks.
Indexing
I'm pretty convinced that indexing in the browser is a bad idea, even when done in the background in a ServiceWorker. It would require to load all the content to create an index and disable the search while doing so.
Creating an index when running catalog build (or as a separate command) seems like the sensible thing to do but would require parsing of the content with something like #307 (but not exclusively).
In any case we have to deal with the fact that we don't just have Markdown files to index but also content in JS files (either JSX or markdown template literal).
Another approach that could work if we had SSR would be to generate HTML pages first and then index those.
User Interface
Just filtering the navigation doesn't always make it obvious why something's matched, especially if we only show top-level page titles when matching sub-pages (or keywords!). Search results need to be contextualized, maybe in a panel (Algolia does this pretty well IMHO)?

Very good points @herrstucki. I guess that going the extra mile on having a convincing search tool goes against the concept of having a flexible and replaceable search tool, so maybe we (I want to help!) can pinpoint where to draw the line and go from there.
BTW, I didn't know about Algolia, neat service! I was going to suggest something like Bootstrap provides but *surprise* they use Algolia 😄 I see they have a "Community" tier (I love when companies support open source), but going that way would be tieing Catalog to their service, so I guess the implementation should support the external decision about using it but I don't think it should come out-of-the-box.
Anyway, my feeling is that, as Catalog could be used for such a variety of projects, and Catalog by itself can't really infer the type of content beforehand; the searchable content, its context and its UI should be defined in an abstract way, so the implementation can tackle the searchability of that abstract concept, and then open up the possibility that people could hook up their own specific search abilities dependning on their requirements. Otherwise the search solution will never be good enough as the types of content will never cease to change with time.

Would love to have this as well.

Any progress on this? Would love a plug-and-play search experience.


CDN version

Please, add a CDN link version, so we can use this package with only vanilla js.

Hadn't thought about that. I will definitely do it.
I have never done so, do you have any recommendations? I mean, something that will also allow to manage and publish versions appropriately?
Thanks for the suggestion!

I have never done this too, but this guy made: https://github.com/apvarun/toastify-js. He made a feature like yours too.

I think it's a great idea so I'll leave this one open.

I just realized notyf is already getting 93k hits a month on jsdelivr! I updated the docs with the link to jsdelivr. Thanks again!
<html>
  <head>
    ...
    <link rel="stylesheet"<EMAIL_ADDRESS>  </head>
  <body>
    ...
    <script<EMAIL_ADDRESS>  </body>
</html>


1.20.1

Updated for 1.20.1
Substituted block materials with BlockTags, since Material was removed in Minecraft 1.20. Details: https://fabricmc.net/2023/05/25/120.html

Cool, are you using it to update mcdata ?

@rom1504 Yes, I'm using it to update mcData, and in doing so I get data that fixes this issue: https://github.com/PrismarineJS/minecraft-data/issues/757

ok please open a pr on mcdata

I removed the commented out code


Tests process stopping does not work

Describe the bug
Running devenv-run-tests tests does not stop the started processes and therefore the next test run will fail.
 Running tests in 2.6s.
• Stopping process with PID 171823
Stopping processes...
• Tests passed :)
cat: /home/shyim/Developer/devenv-test/devenv/tests/postgresql-localhost/.devenv.KLRlw3KTbbCd/state/devenv.pid: No such file or directory
kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec]
rm: cannot remove '/home/shyim/Developer/devenv-test/devenv/tests/postgresql-localhost/.devenv.KLRlw3KTbbCd/state/devenv.pid': No such file or directory
  Running up-uses-shell

there is no pid file, just the data of postgresql
and failing tests are marked as success.
• Running .test.sh...

ERROR 2002 (HY000): Can't connect to local server through socket '/home/shyim/Developer/devenv-test/devenv/tests/mysql/.devenv.Rld' (2)

✔ Running tests in 16.6s.
• Stopping process with PID 206429
• Tests passed :)

Can you try now with https://github.com/cachix/devenv/commit/47363a715ae95ad2118d642981604b9a3fa48428


Fix build error

appending the args correctly
creating the target directory if does not exist

@zcbenz pls note that electron submodules are not updated

Thanks!


Ability to deactivate gift cards

Add deactivated_at to gift card
Show deactivated status on shipments/cartons/cart + gift card edit pages
Deactivating makes gift card unredeemable

TODO: Refunding logic

:+1:

Looking good! Excited to see the refunding side

@athal7 would you mind :eyes: on the latest commits concerning inventory units + reimbursements?


Mesh3D's triangle indices should be [rerun.datatypes.UVec3D]

Requires some work to make it fit nicely with all our mandatory optimizations at this is effectively a List<List<FixedSizedList<u32, 3>>>, which isn't supported yet.

That's done.


Welcome screen title "Visual Studio Code" cut off at the top running in Xfce on Linux

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: 1.77.3
OS Version: Arch Linux x64 6.2.12-arch1-1
Desktop: Xfce 4.18 (which runs on Xorg)

Steps to Reproduce:

Start VS Code, VSCodium or Code OSS, installed on a Linux system with Xfce as a desktop.
Open the Welcome screen via the menu if it hasn't shown yet.

Screenshot of the issue:

I also experimented with tweaking some CSS settings using the Developer Tools, and clearly noticed that the "Visual Studio Code" text is bigger then what the configured space for it allows.
Here a copy of that CSS from how it showed up the Developer Tools:
.monaco-workbench .part.editor>.content .gettingStartedContainer h1 {
    padding: 5px 0 0;
    margin: 0;
    border: none;
    font-weight: 400;
    font-size: 2.7em;
    white-space: nowrap;
}

When I remove the margin: 0; then the space gets bigger and the entire text becomes correctly visible, but when I remove the padding: 5px 0 0; then the problem becomes worse and about twice the amount of cut off occurs.
Notes:

This problem exists for quite a while, actually as long as I am using Visual Studio Code on Xfce.
Problem does not happen on GNOME or KDE Plasma, I tried both with a Wayland session as well as with an Xorg session. But there exist a lot more desktop environments and window managers, so I am not sure if Xfce is the only one where this bug occurs.

Are you sure this happens only in XFCE? Doesn't show up in my RPI 3 clone when using XFCE.

We closed this issue because we are unable to reproduce the problem with the steps you describe. Chances are we've already fixed your problem in a recent version of VS Code. If not, please ask us to reopen the issue and provide us with more detail. Our issue reporting guidelines might help you with that.
Happy Coding!


[stable/redis-ha] One serviceMonitor for both redis-ha and haproxy

Is your feature request related to a problem? Please describe.
Extend serviceMonitor scope to support both haproxy metrics and redis-exporter
Describe the solution you'd like

Move serviceMonitor definition from exporter.serviceMonitor to the serviceMonitor
Add haproxy targetport to the serviceMonitor configuration

Additional context
Current configuration of serviceMonitor and haproxy service
kind: ServiceMonitor
metadata:
  creationTimestamp: 2019-11-10T17:25:30Z
  generation: 1
  labels:
    prometheus: service-monitor
  name: redis-ha
  namespace: monitoring
  resourceVersion: "219542275"
  selfLink: /apis/monitoring.coreos.com/v1/namespaces/monitoring/servicemonitors/redis-ha
  uid: 182244c3-03df-11ea-9d3f-0604b3339bd0
spec:
  endpoints:
  - targetPort: 9121
  jobLabel: redis-ha
  namespaceSelector:
    matchNames:
    - redis-ha
  selector:
    matchLabels:
      app: redis-ha
      release: redis-ha

redis-ha-haproxy service
apiVersion: v1
kind: Service
metadata:
  creationTimestamp: 2019-11-10T14:38:26Z
  labels:
    app: redis-ha
    chart: redis-ha-4.0.2
    heritage: Tiller
    release: redis-ha
  name: redis-ha-haproxy
  namespace: redis-ha
  resourceVersion: "220495791"
  selfLink: /api/v1/namespaces/redis-ha/services/redis-ha-haproxy
  uid: c165309f-03c7-11ea-9d3f-0604b3339bd0
spec:
  clusterIP: <IP_ADDRESS>
  ports:
  - name: haproxy
    port: 6379
    protocol: TCP
    targetPort: redis
  - name: http-exporter
    port: 9101
    protocol: TCP
    targetPort: exporter-port
  selector:
    app: redis-ha-haproxy
    release: redis-ha
  sessionAffinity: None
  type: ClusterIP
status:
  loadBalancer: {}

@pgdagenais what do you think about it?

That would reduce the templates file in the chart itself, but I don't really see a lot of values in doing that. I think it is a lot better to have a single serviceMonitor resource per service.


Remove version: CrystalDewWorld.CrystalDiskInfo.AoiEdition version 9.3.0

[Automated] It returns code over 400 in all urls
Microsoft Reviewers: Open in CodeFlow

URL: https://sourceforge.net/projects/crystaldiskinfo/files/9.3.0/CrystalDiskInfo9_3_0Aoi.exe/download
OK
(Automated message - build 923)

Close with reason: Package still available;


color & font theme for NEST website

Need to decide on a consistent color theme and font family for the NEST website.
Proposal: Use consistent color from NEST product logos & font

I think this is the most important aspect for the logos and website. Looking at this: https://visme.co/blog/website-color-schemes/. I suggest Blue based ones, so 1/3/4/20/23/24/25

really like Hex Codes: #8ecae6 // #219ebc // #023047 // #ffb703 // #fb8500 (https://venngage.com/blog/blue-color-palettes/#3

As a font I would use a monospaced one that is easier to center and it does imply different sizes for different letters. In particular I would use monoLisa: https://crocoblock.com/blog/best-programming-fonts/

As a font I would use a monospaced one that is easier to center and it does imply different sizes for different letters. In particular I would use monoLisa: https://crocoblock.com/blog/best-programming-fonts/

Is monospace font mostly used for coding/programming? I was considering fonts like "San Francisco Pro", "Helvetica", etc.

Yes it is mainly used in programming, but I thought it was cool to use something a bit "nerdy", but I do not have a strong opinion about this. Helvetica would be cool and makes sense:

Consolas:

San Francisco Pro (is this the one? seems a bit appley):

monoLisa (very nerdy I have to admit):

ps from that website: Here are some things to look out for in a good programming font:

The characters are clear and easy to read.
There is a clear difference between the letter “O” and zero, as well as the number 1 and lowercase “L”.

Font suggestions:
https://adobe-fonts.github.io/source-code-pro/
https://fonts.google.com/specimen/Roboto+Mono

I think we could still vote on this right?


DBeaver Mac Connection Settings Does Not Show SSH Tab

System information:

Operating system (distribution) and version:  MacOS Monterey 12.3.1 (21E258)
DBeaver version: <IP_ADDRESS>204170718
Additional extensions

Connection specification:

Database name and version: Postgres 14
Driver name
Do you use tunnels or proxies (SSH, SOCKS, etc)?  SSH with private key file

Describe the problem you're observing:
On creation of connection, SSH tab is there for setup. But once saved, there is no way to modify the SSH settings as the tab no longer shows in the Connection Settings. Only Main/PostgreSQL/Driver Properties are available.
Steps to reproduce, if exist:
Just try to edit any Postgres connection.
Include any warning/errors/backtraces from the logs

Hello @Kunthera,
Does resizing the connection dialog help?
Could you please send the log files? You can find instructions here: https://dbeaver.com/docs/wiki/Log-files/.


Add Mu Coin Logo

C-Chain Contract address for Mu Coin - 0xD036414fa2BCBb802691491E323BFf1348C5F4B

a

last char of contract address got seperated by the logo
C-Chain contract address is - 0xD036414fa2BCBb802691491E323BFf1348C5F4Ba


Support --color=always

[x] I have read through the manual page (man fzf)
[x] I have the latest version of fzf
[x] I have searched through the existing issues

Info

OS

[ ] Linux
[x] Mac OS X
[ ] Windows
[ ] Etc.

Shell

[ ] bash
[x] zsh
[ ] fish

Problem / Steps to reproduce
I am running fzf with the following command: rg . | fzf --filter=query through a Node.JS process. I want to make fzf output ANSI codes so I can parse them and determine where the matches are.
Have you considered adding a --color=always option?

rg --color=always . | fzf --filter=query

This doesn't work if you run it from a Node.JS process like the example below:
const result = execSync('rg --color=always . | fzf --filter=query').toString()

// result here doesn't have ANSI codes inside of it

If you want I can write a longer explanation and reasons why I think this flag can be useful. Just let me know.

This doesn't work if you run it from a Node.JS process

In this case, without --ansi option, fzf simply bypasses any ANSI escape sequences in the original string. They are printed unmodified. So maybe it's execSync stripping the codes. I don't know.
# Colored
rg .

# No color
rg . | cat

# Colored
rg --color=always . | cat

# Colored
rg --color=always . | fzf --filter=query

# Still colored
rg --color=always . | fzf --filter=query | cat

fzf matches are still not wrapped with ANSI codes

Coloring of --filter output was not implemented. Since I never use --filter option (I don't find it useful without UI), I'm not interested in implementing it.

This doesn't work if you run it from a Node.JS process

The way most other CLI tools I have seen written in Node.JS the program checks for process.stdout.isTTY and if it is true only then they return ANSI codes. Maybe there is some type of check in fzf somewhere?

fzf matches are still not wrapped with ANSI codes

Thanks, I understand. Do you have ideas on how can I use fzf outside of the terminal some other way? fzf has such a powerful searching algorithm that it is very sad it can't be used outside of the terminal for querying big amounts of data.


NUMA support and other warnings

WSL2
GPU: Radeon RX590
Hi I followed the installation step-by-step guide and the plugin seems to be working fin with my GPU. However I'm getting a few warnings such as:
2022-07-04 23:28:50.054002: I tensorflow/core/platform/cpu_feature_guard.cc:193] This TensorFlow binary is optimized with oneAPI Deep Neural Network Library (oneDNN) to use the following CPU instructions in performance-critical operations:  AVX2 FMA
To enable them in other operations, rebuild TensorFlow with the appropriate compiler flags.
2022-07-04 23:28:50.055064: I tensorflow/c/logging.cc:34] DirectML: creating device on adapter 0 (Radeon RX 590 Series)
2022-07-04 23:28:50.302803: I tensorflow/core/common_runtime/pluggable_device/pluggable_device_factory.cc:305] Could not identify NUMA node of platform GPU ID 0, defaulting to 0. Your kernel may not have been built with NUMA support.
2022-07-04 23:28:50.302872: W tensorflow/core/common_runtime/pluggable_device/pluggable_device_bfc_allocator.cc:28] Overriding allow_growth setting because force_memory_growth was requested by the device.
2022-07-04 23:28:50.302929: I tensorflow/core/common_runtime/pluggable_device/pluggable_device_factory.cc:271] Created TensorFlow device (/job:localhost/replica:0/task:0/device:GPU:0 with 6958 MB memory) -> physical PluggableDevice (device: 0, name: DML, pci bus id: <undefined>)

is NUMA available in wsl2 and tf2 ?

This warning is harmless for tensorflow-directml-plugin, but I can see how it can be confusing. This warning is located in the tensorflow codebase so we don't have much control over it, but I'll see if we can propose a change for the next version of TF to disable this message for pluggable devices that don't have any support for NUMA.


wrangler: 0.19.1 -> 0.19.2

Motivation for this change
upstream update https://github.com/cloudflare/wrangler/releases
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.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.

Since this is a patch update with nothing in particular, I'm going to go ahead and merge it.


Replace '.contains must equal true' with 'must include' in tests

Previously if a test ran and failed, it would just say 'true did not equal false' which is not helpful. This fix will show you the strings that it's comparing so it is easier to see what is incorrect

Waiting on Vimlesh's PR to get merged before I merge this just because he's had to deal a lot of merge conflicts while writing his code


help not available if CMenu ctor'ed with selector present

This is by design, though it sure is confusing. Should be changed to be more clear.

This is by design, though it sure is confusing. Should be changed to be more clear.

For reference, the actual fix for this issue is in #79


Add GraphQL Security

awesome-graphql-security
GraphQL Security is a niche ecosystem which get more and more attention as GraphQL grow.
We decided to create an awesome list to push this ecosystem ahead and we already reached a lot of people (55+ stars, 6 contributors, following guildelines and automated workflows...).
By submitting this pull request I confirm I've read and complied with the below requirements 🖖
Please read it multiple times. I spent a lot of time on these guidelines and most people miss a lot.
Requirements for your pull request

Don't waste my time. Do a good job, adhere to all the guidelines, and be responsive.
You have to review at least 2 other open pull requests.
Try to prioritize unreviewed PRs, but you can also add more comments to reviewed PRs. Go through the below list when reviewing. This requirement is meant to help make the Awesome project self-sustaining. Comment here which PRs you reviewed. You're expected to put a good effort into this and to be thorough. Look at previous PR reviews for inspiration. Just commenting “looks good” or simply marking the pull request as approved does not count! You have to actually point out mistakes or improvement suggestions.
You have read and understood the instructions for creating a list.
This pull request has a title in the format Add Name of List.

✅ Add Swift
✅ Add Software Architecture
❌ Update readme.md
❌ Add Awesome Swift
❌ Add swift
❌ add Swift
❌ Adding Swift
❌ Added Swift

Your entry here should include a short description about the project/theme of the list. It should not describe the list itself. The first character should be uppercase and the description should end in a dot. It should be an objective description and not a tagline or marketing blurb.

✅ - [iOS](…) - Mobile operating system for Apple phones and tablets.
✅ - [Framer](…) - Prototyping interactive UI designs.
❌ - [iOS](…) - Resources and tools for iOS development.
❌ - [Framer](…)
❌ - [Framer](…) - prototyping interactive UI designs

Your entry should be added at the bottom of the appropriate category.
The title of your entry should be title-cased and the URL to your list should end in #readme.

Example: - [Software Architecture](https://github.com/simskij/awesome-software-architecture#readme) - The discipline of designing and building software.

The suggested Awesome list complies with the below requirements.

Requirements for your Awesome list

Has been around for at least 30 days.That means 30 days from either the first real commit or when it was open-sourced. Whatever is most recent.
Don't open a Draft / WIP pull request while you work on the guidelines. A pull request should be 100% ready and should adhere to all the guidelines when you open it. Instead use #2242 for incubation visibility.
Run awesome-lint on your list and fix the reported issues. If there are false-positives or things that cannot/shouldn't be fixed, please report it.
The default branch should be named main, not master.
Includes a succinct description of the project/theme at the top of the readme. (Example)

✅ Mobile operating system for Apple phones and tablets.
✅ Prototyping interactive UI designs.
❌ Resources and tools for iOS development.
❌ Awesome Framer packages and tools.

It's the result of hard work and the best I could possibly produce.
If you have not put in considerable effort into your list, your pull request will be immediately closed.
The repo name of your list should be in lowercase slug format: awesome-name-of-list.

✅ awesome-swift
✅ awesome-web-typography
❌ awesome-Swift
❌ AwesomeWebTypography

The heading title of your list should be in title case format: # Awesome Name of List.

✅ # Awesome Swift
✅ # Awesome Web Typography
❌ # awesome-swift
❌ # AwesomeSwift

Non-generated Markdown file in a GitHub repo.
The repo should have awesome-list & awesome as GitHub topics. I encourage you to add more relevant topics.
Not a duplicate. Please search for existing submissions.
Only has awesome items. Awesome lists are curations of the best, not everything.
Does not contain items that are unmaintained, has archived repo, deprecated, or missing docs. If you really need to include such items, they should be in a separate Markdown file.
Includes a project logo/illustration whenever possible.

Either centered, fullwidth, or placed at the top-right of the readme. (Example)
The image should link to the project website or any relevant website.
The image should be high-DPI. Set it to maximum half the width of the original image.

Entries have a description, unless the title is descriptive enough by itself. It rarely is though.
Includes the Awesome badge.

Should be placed on the right side of the readme heading.

Can be placed centered if the list has a centered graphics header.

Should link back to this list.

Has a Table of Contents section.

Should be named Contents, not Table of Contents.
Should be the first section in the list.
Should only have one level of nested lists, preferably none.
Must not feature Contributing or Footnotes sections.

Has an appropriate license.

We strongly recommend the CC0 license, but any Creative Commons license will work.

Tip: You can quickly add it to your repo by going to this URL: https://github.com/<user>/<repo>/community/license/new?branch=main&template=cc0-1.0 (replace <user> and <repo> accordingly).

A code license like MIT, BSD, Apache, GPL, etc, is not acceptable. Neither are WTFPL and Unlicense.
Place a file named license or LICENSE in the repo root with the license text.
Do not add the license name, text, or a Licence section to the readme. GitHub already shows the license name and link to the full text at the top of the repo.
To verify that you've read all the guidelines, please comment on your pull request with just the word unicorn.

Has contribution guidelines.

The file should be named contributing.md. Casing is up to you.
It can optionally be linked from the readme in a dedicated section titled Contributing, positioned at the top or bottom of the main content.
The section should not appear in the Table of Contents.

All non-important but necessary content (like extra copyright notices, hyperlinks to sources, pointers to expansive content, etc) should be grouped in a Footnotes section at the bottom of the readme. The section should not be present in the Table of Contents.
Has consistent formatting and proper spelling/grammar.

The link and description are separated by a dash. Example: - [AVA](…) - JavaScript test runner.
The description starts with an uppercase character and ends with a period.
Consistent and correct naming. For example, Node.js, not NodeJS or node.js.

Doesn't use hard-wrapping.
Doesn't include a Travis badge.You can still use Travis for list linting, but the badge has no value in the readme.
Doesn't include an Inspired by awesome-foo or Inspired by the Awesome project kinda link at the top of the readme. The Awesome badge is enough.

Go to the top and read it again.

unicorn

Thanks for making an Awesome list! 🙌
It looks like you didn't read the guidelines closely enough. I noticed multiple things that are not followed. Try going through the list point for point to ensure you follow it. I spent a lot of time creating the guidelines so I wouldn't have to comment on common mistakes, and rather spend my time improving Awesome.

Thanks for making an Awesome list! raised_hands
It looks like you didn't read the guidelines closely enough. I noticed multiple things that are not followed. Try going through the list point for point to ensure you follow it. I spent a lot of time creating the guidelines so I wouldn't have to comment on common mistakes, and rather spend my time improving Awesome.

Hello @sindresorhus,
I reviewed the guideline one more time and nothing related to the list itself is uncompliant.
May you share what you noticed?

Hi @c3b5aw,
Hope you are doing well. I noticed just a couple formatting-related issues but nothing too crazy.

Includes a project logo/illustration whenever possible. It might be a good idea to include a header image that links back to a relevant site (maybe GraphQL's official site?)
The table of contents needs a title. It should be titled "Contents".
The table of contents should not include the "Contributing" section.
The table of contents "Should only have one level of nested lists, preferably none."
Some of your listed links have a few grammatical errors. I see "graphQL" and "graphql" when it should be "GraphQL".
A few list descriptions do not end with a period.

Hope that helps. 😎

Hi @c3b5aw,
Hope you are doing well. I noticed just a couple formatting-related issues but nothing too crazy.
* Includes a project logo/illustration whenever possible. It might be a good idea to include a header image that links back to a relevant site (maybe GraphQL's official site?)

* The table of contents needs a title. It should be titled "Contents".

* The table of contents should not include the "Contributing" section.

* The table of contents "Should only have one level of [nested lists](https://commonmark.org/help/tutorial/10-nestedLists.html), preferably none."

* Some of your listed links have a few grammatical errors. I see "graphQL" and "graphql" when it should be "GraphQL".

* A few list descriptions do not end with a period.

Hope that helps. sunglasses

Thanks for catching theses point. Will improve right away.

Hello @sindresorhus,
This is ready for review.

Hi,
Thanks for the list!
See just a few issues:

Seems you don't review any PRs as for "You have to review at least 2 other open pull requests."

https://github.com/sindresorhus/awesome/pulls?q=type%3Apr+reviewed-by%3Ac3b5aw

"GraphQL security frameworks, libraries, software and resources." it looks like a bad example from requirements "iOS - Resources and tools for iOS development."

It sounds as describing the list itself, which is not good.

You are reviewing a closed PR though.

Sorry @c3b5aw
Are you going to reopen it or it's closed forever?
I saw this

Hello @sindresorhus,
This is ready for review.

and think that it's ready for review again


select-dropdown component

Environment

Ember Version:
Ember CLI Version: 2.18.2
Ember CP Validations Version: 3.x

First of all thanks for great addon.!!
I am finding difficulty with validations against select-dropdown component.
Can someone point me to example with all the HTML elements covered??
Thanks in advance.
P.S This is not a issue!!

@jsamuel89 I'm closing the issue because it's quite old. Feel free to reopen if you still need help.


Feature Idea: Support fetching the repository contents from a Flux GitRepository

Since I'm running Flux in my cluster already, it would be nice to not have multiple copies of my infrastructure repo. (Using a monorepo approach to put both terraform files and kubernetes manifests together.)
Flux has a well-tested GitRepository CRD and the controller exposes the repository as a .tar.gz in-cluster URL.
What do you think?

Hey @nogweii this is an idea we had when we first started working on burrito, initially we wanted to solely rely on the fluxcd source controller, we figured out in the end we didn't want burrito to have such a dependency and we scrapped the idea.
However thinking about it now we could implement a feature to source git bundles from Flux alongside our default way of retrieving those bundles using a GitRepository reference, I don't think it'd be too much of a hassle to implement.
I'll look into it for 0.5 we will be working on some features related to repositories and that might be the best time to include this kind of feature :)
Feel free to contribute if you have any idea how the yaml spec would have to look like on our TerraformRepository CRD, I'd guess something along the lines of this :
source:
  git:
  ....
  flux:
    kind: GitRepository
    name: repo
    namespace: default


Allow pattern-matching for function arguments

Would be nice to write e.g. let trans _ x = x + 1 instead of having to declare an unused variable for the edge. It would also be easier to e.g. unpack tuples automatically.

This seems like a worthwhile change outside of functions too: if we could make the left-hand side of a let binding be a pattern, instead of an identifier, we could then destruct data into multiple identifiers with one let, e.g.:
let trans e (x1, _) =
  let u~v = e in
  let { a; b; c } = x1 in
  if u = 0n then a + b else a + c

Yeah, this is a nice QoL feature to have. I think we already allow this in let-statements, it just gets turned into a match statement during parsing. We could possibly implement it for function arguments by creating fresh variable for each argument pattern during parsing, then starting the body with a match to destruct it according to the user's pattern.

From what I can see, this is only done for tuples in let statements right now. Parsing throws an error for both patterns above. That being said, I would think they would both be implementable using that desugaring approach you describe.


fix(withdrawFromVault): Add another withdrawFromVault fixture

What this PR does / why we need it:
There are only 2 fixtures for withdrawFromVault DFTX.
Add 1 more fixture as the minimum requirement is at least 3 fixtures.
Which issue(s) does this PR fixes?:

Fixes #1398
Additional comments?:

There are 2 files in this PR. Both have the same content except one line has a different import. They are to test both refactored and deprecated rpcs.


[Language Support] ObjectPascal

This extension doesn't support ObjectPascal language. I'm using OmniPascal extension and Free Pascal to write Pascal programs on VS Code. So, how to make this extension works with ObjectPascal language, especially on the begin … end pair?
Thank you. 😊

I don't use Pascal, but I added keyword support for it in v1.0.56
Try something like
	"bracketPairColorizer.consecutivePairColors": [
		"()",
		"[]",
		"{}",
		["type","end"],
		["begin","end"],
		[
			"Gold",
			"Orchid",
			"LightSkyBlue"
		],
		"Red"
	],

It still doesn't work with Pascal files. 😟


invalid memory access when if-statement is used

Here is the minimal reproducer from a bug detected by QMCPACK. Affecting ROCM 4.5 and AOMP.
https://github.com/ye-luo/openmp-target/blob/4b3c157fc903024b6b46ea7ef9646a20d2982b42/tests/math/modf_in_branch.cpp#L27
The branch caused invalid memory access in the kernel.
$ clang++ -ffast-math -march=native -fopenmp -fopenmp-targets=amdgcn-amd-amdhsa -Xopenmp-target=amdgcn-amd-amdhsa -march=gfx906 -O3 -DNDEBUG -std=c++17 main.cpp
$ ./a.out
[GPU Memory Error] Addr: 0x0 Reason: Page not present or supervisor privilege.
Memory access fault by GPU node-1 (Agent handle: 0x1b18b50) on address (nil). Reason: Page not present or supervisor privilege.
Aborted (core dumped)

if the printf is uncommented, ptr value is 0x8 which is wrong.

Thank you for the test case.  I have been able to reproduce the problem that you described with the ROCm 4.5 llvm.  I have also verified that the bug you ran into has already been fixed and will be available in the next AFAR release.  We are currently in the process of finishing up the changes for that release.  It should be available within a month.
If you would like to try out the fix sooner, it would also be possible for you to build a AOMP llvm compiler containing the same changes that will be in the upcoming AFAR release.  If you are interested in doing this, just follow these instructions:
https://github.com/ROCm-Developer-Tools/aomp/blob/aomp-dev/docs/SOURCEINSTALL.md
If you have any questions, just let me know.

I confirm that the bug has been resolved.


Fix: refactor and reorganize modules

This pr is an attempt to clean up and reorganize the various elements of this package. it does the following.

it moves all of the pydantic models to a single models.py module. Then all of the pydantic things are only imported in that module.
It moves the small cleaning functions that i created to a separate clean.py module. that way it's clear where they come from.
it keeps the process_issue and process_contributors classes in separate modules by themselves.

I have a question however. Right now #3 above - both modules need to call the github API. And as such i share the token authentation between the two classes. I wondered if it might make more sense to create a new github module that just handles github things? and i'd love some feedback on this.
The goal here is to make the code easier to maintain and read.

@lwasser Can you please provide a brief note for the PR on what changes are here ☀

@willingc done!! i also have a question about organization.

@lwasser Let's do this. Let me review this PR as is. We can then tackle simplifying the GitHub token use and naming in separate iterative PRs. Each PR can be small and tested with the goal of keeping the functionality working with minimal changes at once 👍🏼

@willingc that would be wonderful. i really appreciate your reviewing!!  🙌

i really see the value of smaller pr's. this one feels big big BUT it's mostly my moving things around and renaming. (and i removed some comments from my prior less create an issue savy self)


[plot] Glitch when displaying image containing only inf and 0

When displaying an image containing only inf and 0.0 (there is also maybe -inf) the colorbar displays [1.0 ... 1.0], while the only finite value is 0.0.

closing as fixed in the tip.


.github/workflows: add golangci-lint workflow

Before sending a pull request, please review Contribution Guidelines:
https://github.com/google/syzkaller/blob/master/docs/contributing.md

Codecov Report

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

@@           Coverage Diff           @@
##           master    #1717   +/-   ##
=======================================
  Coverage   56.64%   56.64%
=======================================
  Files         148      148
  Lines       27669    27669
=======================================
  Hits        15673    15673
  Misses      11205    11205
  Partials      791      791

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 8742a2b...5610162. Read the comment docs.

Some docs would be nice.

Some docs would be nice.

Added a section to contributing.md.

I am going to merge this. I suspect we will uncover more problems only as it will start working on PRs and more users will try it. Don't want to sit on this pile of local changes. @melver but review is still welcome.

It's green. Fingers crossed.
(since it's green maybe errors reporting is broken entirely :))
Amusingly this found 2 very old bugs that nobody observed because nobody was ever able to build these arches (32-bit builds were broken on my machine for some time now):
https://github.com/google/syzkaller/pull/1717/commits/fd068804612a589e83d8de0edc3762e6435a4d60
https://github.com/google/syzkaller/pull/1717/commits/a46bf99f18490a7a0b9b23ee22f53dbb53356d04

LGTM


picqer/moneybird-php-client outdated

Hello,
Can you update the picqer/moneybird-php-client version so 'due_date' is availeble
(see https://github.com/picqer/moneybird-php-client/pull/93/files)
in/vendor/picqer/moneybird-php-client/src/Picqer/Financials/Moneybird/Entities/SalesInvoice.php
Sincerely Dennis

Hi,
v1.1.0 will use any version above 0.15.0.


Empty iterator in lab 22

Lab/Demo: 22
Task: Run the web app
Step: 3
When I searched "London hotel" in the search box, the page navigated to an error page, displaying :
Oops! An error occurred
() Invalid expression: Could not find a property named 'url' on type 'search.document'. Parameter name: $select Code: Message: Invalid expression: Could not find a property named 'url' on type 'search.document'. Parameter name: $select

I tried to print the search result in python code app.py :
        # Submit search query
        results =  search_client.search(search_text,
                                        search_mode="all",
                                        include_total_count=True,
                                        filter=filter_by,
                                        order_by=sort_order,
                                        facets=['metadata_author'],
                                        highlight_fields='merged_content-3,imageCaption-3',
                                        select = "url,metadata_storage_name,metadata_author,metadata_storage_size,metadata_storage_last_modified,language,sentiment,merged_content,keyphrases,locations,imageTags,imageCaption")
        print(results.__dict__) # Print search result
        return results

I got this :
{'_args': (
        <azure.search.documents._internal._generated._search_index_client.SearchIndexClient object at 0x000001EF3CB31E48>,
        <SearchQuery [London hotel]>,
        {'headers':
            {'api-key': 'xxx',
            'Accept': 'application/json;odata.metadata=none'}
        }
    ),
'_kwargs': {},
'_page_iterator': None,
'_page_iterator_class': <class 'azure.search.documents._internal._paging.SearchPageIterator'>,
'_first_page_iterator_instance': None}

It's seems like page iterator is empty. But I searched the same string in Search Explorer, it works well.

@sunyiming I wasn't able to reproduce your error. Which means that it could be the issue is occuring because something is wrong with your index and it can't find the variable in your index that it wants to display. Could you delete the index, indexer and data source in Cognitive Search (in the Azure portal) and try to run the lab again. Also please clone the repo again as we made some changes yesterday.
I'm assuming you did update the .env file as otherwise the error shows: The value provided for the url part endpoint was incorrect, and resulted in an invalid url

It's my indexer problem. Thanks for your help.


MEI 3 to 4 conversion: authority attributes not always converted correctly

inside <perfResList>, @authority and @authURI are not converted to their new names

Fixed by commit https://github.com/Det-Kongelige-Bibliotek/MerMEId/commit/d46569491ed5f7c7c6a3ce9f98b89ca55ec9f098


Frequency of data collection and export

May I ask a question? How often does your code get the data collected? Could it be exported to excel with time? Because I want to use it to record the data in  a period. Thanks a lot!

或许可以写个函数写入到文本中，频率我没测试过

May I ask a question? How often does your code get the data collected? Could it be exported to excel with time? Because I want to use it to record the data in a period. Thanks a lot!

或许可以写个函数写入到文本中，频率我没测试过

好的，非常感谢您，请问您这边接受有偿开发吗？

非常感谢您！冒昧地请问一下您，您这边能够有时间接受有偿开发吗？


WIP: Update deps: tokio, hyper

This is WIP
I tried to update the dependencies (tokio, hyper), as tokio 1.0.0 came out tonight.
Unfortunately, it is not as simple as I thought it would be. Can we please work together to update these dependencies?

See #79


Add anchors to changelog page

Hi All 👋  I was trying to show a changelog today, and I realized that the changelog page doesn't have anchors to quickly link someone to the changelog i'm trying to reference,
https://http4s.org/changelog/
Thoughts on adding those ?

There is JavaScript that could do it automatically.  My front end skills are abysmal, but I'm :+1: to the idea.

I have been using paradox in http4s-jdk-http-client, whose material theme gives us this for free.  I'd like to port the https docs to that.

We have these now:
https://http4s.org/changelog.html


apulse does not work with the snap version of Firefox

After having installed Firefox as a snap package with the command "snap install firefox", if I try to run "apulse firefox", I don't get any sound on YouTube. To get sound, I have to bypass the sandbox by directly calling "apulse /snap/firefox/137/firefox" (but then I cannot use my Firefox profile located in the folder ~/snap/firefox/). I am not sure if this can be fixed on the apulse side or if it should be fixed by the snapd program.

As far as I know, Snap packages are using (compressed) filesystem image. There are not only application itself, but all the libraries it depends on. That's why the same package works on various versions of Ubuntu. And there is libpulse.so.0 → libpulse.so.0.19.0 in the Firefox Snap package. So, it uses that instead of any other library from your OS.
I don't think it can be "fixed", as it's exactly what Snap was built for — to make applications self-consistent.

Ok, so there is no way to hack and use ALSA instead of PulseAudio with the Firefox Snap package?
Maybe if apulse is directly called inside of the Snap filesystem image?

Ok, so there is no way to hack and use ALSA instead of PulseAudio with the Firefox Snap package?

I don't think it's possible.

Maybe if apulse is directly called inside of the Snap filesystem image?

If one replaces libpulse.so.0 from PulseAudio by libpulse.so.0 from apulse, I would expect that to work. But then you'll need to repack snap package, and probably, to sign it again. After all that work, it's not so much harder to go further, and to build Firefox from source code with ALSA enabled.


Modifying the Circular Reference Problem in WKNavigationDelegateEvents

issue: #38
I have corrected the circular reference problem of WKNavigationDelegateEvents.
A duplicate code occurs in the parameter section, but I changed it to handle the parameter directly to correct the circular reference problem.
After modification, I confirmed that "deinit" is invoked normally even if we Subscribe the Observable related to WKNavigationDelegateEvents.
Please check PR.

@freak4pc  Can you review this request?

remind for you @freak4pc
Or is there a related reviewer?


Some funds fail during loads

Laurie: Yes, I still can’t load anything with the leigh app using fund p2651.  It is a fund in FOLIO and I can change the fund I load the records with to that fund once they are in FOLIO.

Ive been taking a look at this and have a test for retrieving the fund code data using the p2651 id, compared it the the result of another id and am not seeing anything unusual.  I modified one of  the marc files to use p2651, but can't test it further because there isn't a budget associated with it on the training server.

Thanks, John! I didn't realize you were already looking at this. So you've hit the nail on the head.... the app says this fund/budget doesn't exist but it does. What is happening now is the person loading the files but it's a different fund in the marc record and then changes it by hand to this fund in the FOLIO UI after it is loaded. This seems to happen with only this fund. 220 and p2853 (I was wondering at first if the 'p' was the problem but I guess not).

that helps and I think I see what the issue is.  The fundCode name in the budgets data is a concatenation of the fundCode and the fiscal year code (eg. p2651-FY2023).  The fiscal year code is hardcoded in the application.properties file.  I don't know what that value is in the production instance.  I will have to look to see if I can find a way to obtain the Fiscal year code from Folio.

That makes sense to me except for the fact that other funds work!

Do you have an example of one that is still working?   I'm guessing that the application.properties file on the production server has the fiscalYear property set to FY2021.  I have a test that returns all Budgets and many of them have FY2022, but p2651 has FY2023.  I'm guessing that if the properties file is changed to use FY2023, that p2651 will work (but it would brake others that still have FY2021)

p2853 still works. But if it is just checking for the existence of an FY and this fund was created after that FY but others were created before it would make sense that they would work and it doesn't. FOLIO correctly charges for the current FY but the app check is for an old budget. This also makes sense because if I don't use the app and just do an API create of an order using this fund, it works fine. So yes, I think you are probably right!

I'm testing against the training server and seeing this: There is a budget for p2853-FY2022 and p2853-FY2023.  There is also one for p2651-FY2023 (29723.48 available) and there is a 2651-FY2023 (without the p) with 0.0 available.
We shouldn't be hardcoding the physical year in a properties file.  If it's not changed, the old budget would be used after the rollover to the new fiscal year.  Presumably, the current fiscal year is stored somewhere in folio and updated somehow.

So I think they originally put this check into the app so that it wouldn't let people make orders on funds without budgets. But I think the chances of us doing that are relatively low. So we could either take out the hardcoding of the FY or just remove the budget check altogether.
As far as selecting the current FY it looks to me like FOLIO only identifies it by date range and not by a flag indicating it is current. The FY has properties:
"periodStart": "2022-07-01T00:00:00.000+00:00",
"periodEnd": "2023-06-30T00:00:00.000+00:00",
from {{ okapi_url }}/finance/fiscal-years

I think I can iterate over the fiscal year list and select the one for which the current date is in between periodStart and periodEnd.  I am doing something similar for the course reserves service.

I've got an implementation of an API request that will return the current fiscal year based upon the period start dates.  However, in testing, I have encountered an issue with the order post request which I have created as issue #99

This was fixed in the issue-96-redux branch that has been merged into main


Fix docs of matomo

Due to some improper usage of markdown. At the bottom of player.matomo.tracking.md, some messages cannot be properly displayed.
And even more messages are missing in the official guide.
Angle brackets are usually used as URLs or Email addresses.
This PR fix the problem.
Your pull request should…

[ ] have a concise title
[ ] close an accompanying issue if one exists
[ ] be against the correct branch (features can only go into develop)
[ ] include migration scripts and documentation, if appropriate
[ ] pass automated testing
[ ] have a clean commit history
[ ] have proper commit messages (title and body) for all commits
[ ] have appropriate tags applied

Also cherry-picked this into r/8.x and r/9.x


Help: Commands

All the commands (layout here, info site)

since we're moving over to slash commands, I will make the docs a little differently than what we currently have

sure, if you need me to help with the commands tab, just say so.


Webpack error, development environment

Hello,
I am trying to prepare developement environment according to https://opencv.github.io/cvat/v2.3.0/docs/contributing/development-environment/. In the end after the setup and installation part when I am trying to launch CVAT using this command
yarn run start:cvat-ui
I get errors like this
<e> [webpack-dev-server] [HPM] Error occurred while proxying request <IP_ADDRESS>:3000/api/server/health/?format=json&org= to http://localhost:7000/ [ECONNREFUSED] (https://nodejs.org/api/errors.html#errors_common_system_errors)
I was trying to launch it on WSL1 with Ubuntu 18.04, WSL2 Ubuntu 20.04, and Ubuntu 22.04 and pure Ubuntu 22.04
Is it a problem with a webpack version or something else?
Thanks.

@MPiecuch
Hi, be sure you have run CVAT server part. As you can see, it cannot reach localhost:7000.

Thanks a lot!.
Now everything is up and running but there are some problems with openpolicyagent container. I ran it as it is written in manual but in logs I get:
{"level":"error","msg":"Bundle load failed: request failed: Get \"http://host.docker.internal:7000/api/auth/rules\": dial tcp: lookup host.docker.internal on <IP_ADDRESS>:53: no such host","name":"cvat","plugin":"bundle","time":"2023-01-20T08:26:37Z"}

Try to run Open Policy Agent this way:
docker run -d --rm  --name cvat_opa_debug -p 8181:8181 -v ${PWD}/cvat/apps/iam/rules:/rules --network=host openpolicyagent/opa:0.45.0-rootless     run --server --set=decision_logs.console=true /rules

Thanks, this works.
In the meantine I figured out similar solution:
docker run -d --rm --net=host --name cvat_opa_debug -p 8181:8181 openpolicyagent/opa:0.34.2-rootless run --server --set=decision_logs.console=true --set=services.cvat.url=http://localhost:7000 --set=bundles.cvat.service=cvat --set=bundles.cvat.resource=/api/auth/rules
I'm closing this task, thanks for help.


why i can't reproduce the effect with provided trained model

I try to test the model on Set 5 X4 with provided trained models.When i calculate the psnr in RGB channel i got psnr =30.xxx  which seems not right.When i calculate the psnr in Y channel,i got psnr = 31.xxx. Both of them seems lower than psnr presented in the paper(32.47)。Is there anyone got the results presented in the paper?

Run python3 eval.py, no SR picture. Only the following sentences, can you achieve it? What do I need to change?
Namespace(chop_forward=True, gpu_mode=True, gpus=1, input_dir='Input', model='models/DBPN_x4.pth', model_type='DBPNL', output='Results/', seed=123, self_ensemble=True, testBatchSize=1, test_dataset='Set5_LR_x4', threads=1, upscale_factor=4)
===> Loading datasets
===> Building model
Pre-trained SR model is loaded

There are several models in the paper. Perhaps the X4 model that the author gives is not the best one. just guess.

@liuiyilang when i just use trained model weights "DBPN_x2.pth", I get wrong result, the result picture is green, did u get normall result?

@liuiyilang when i just use trained model weights "DBPN_x2.pth", I get wrong result, the result picture is green, did u get normall result?

I got the normal results ,but seems the model doesn't performs that good with psnr.

Run python3 eval.py, no SR picture. Only the following sentences, can you achieve it? What do I need to change?
Namespace(chop_forward=True, gpu_mode=True, gpus=1, input_dir='Input', model='models/DBPN_x4.pth', model_type='DBPNL', output='Results/', seed=123, self_ensemble=True, testBatchSize=1, test_dataset='Set5_LR_x4', threads=1, upscale_factor=4)
===> Loading datasets
===> Building model
Pre-trained SR model is loaded

Sorry i can't help you,because i use my own dataloader and test code,while i just use dbpn.py and base_networks.py provided.

@liuiyilang thx, I have fixed it

I try to test the model on Set 5 X4 with provided trained models.When i calculate the psnr in RGB channel i got psnr =30.xxx  which seems not right.When i calculate the psnr in Y channel,i got psnr = 31.xxx. Both of them seems lower than psnr presented in the paper(32.47)。Is there anyone got the results presented in the paper?


Added emojis to Headings of README.md

The strategic use of emojis throughout the document enhances readability by providing visual cues that guide the reader through sections.

Ha ha this is amazing! Can we put the emojis on the left side?

Okay I will put them on the left side
Btw, I am new to open source and have some frontend knowledge, so I am contributing in this kind of things

Done! Can you please merge this PR, Sir?


Enable engine context

Codecov Report
Base: 100.00% // Head: 99.95% // Decreases project coverage by -0.04% :warning:

Coverage data is based on head (62c8d7c) compared to base (eb5b7cc).
Patch coverage: 88.88% of modified lines in pull request are covered.

Additional details and impacted files
@@             Coverage Diff             @@
##            master     #394      +/-   ##
===========================================
- Coverage   100.00%   99.95%   -0.05%
===========================================
  Files          114      114
  Lines        10609    10628      +19
===========================================
+ Hits         10609    10623      +14
- Misses           0        5       +5

Impacted Files
Coverage Δ

fugue/__init__.py
100.00% <ø> (ø)

fugue_ray/_utils/dataframe.py
100.00% <ø> (ø)

fugue/execution/execution_engine.py
98.21% <60.00%> (-1.79%)
:arrow_down:

fugue/execution/factory.py
98.68% <94.11%> (-1.32%)
:arrow_down:

fugue/exceptions.py
100.00% <100.00%> (ø)

fugue/interfaceless.py
100.00% <100.00%> (ø)

fugue_dask/registry.py
100.00% <100.00%> (ø)

fugue_duckdb/dask.py
100.00% <100.00%> (ø)

fugue_duckdb/execution_engine.py
100.00% <100.00%> (ø)

fugue_duckdb/registry.py
100.00% <100.00%> (ø)

... and 2 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Screenshots missing from Clipy history

Hi there, I'm currently on Catalina <IP_ADDRESS> and Clipy 1.2.9 beta12. I noticed that I'm unable to retrieve screenshots from Clipy with all these settings checked:

Is this a known issue? Thanks for help!

Have you tried the latest release version? I am not sure where is the problem. In my device the latest release version is work perfect.

The latest version being 1.2.9.beta12 right? Yeah I'm using that one, and can't get the screenshot. I even tried rolling back to 1.2.6, but couldn't get screenshot work neither.

You can disable Save screenshots in history and the re-enable it and try again.

uncheck the "Save screenshots in history" and restart the app it works well in 10.15 w/latest Clipy app.

The suggestion above worked for me
(uncheck "Save screenshots in history" in the Beta pane, restart, check again "Save screenshots in history", restart again)
Running on 10.15.7


freeze bug

Hello Jeff
Since last update of sandify, I Have a lot of preview freeze. this happen when I upload a new thr file or when I try to move the slider to see the path. I have try with many computer, many thr file, many web explorer but still the same!
https://drive.google.com/file/d/1XAHuc2YL_oD9vhEKur5XW-4n9AQV_394/view?usp=sharing 1
I have made a very small video to let see what happen! Any idea? same to you?
thanks a lot

Thanks for reporting this.
That looks a lot like a bug I found recently. I think it has to do with the fact the preview window progress bar was computing based on a larger data length (when all three layers were present). Then the layer was deleted and that length wasn't recomputed. Then it was looking for a value in an array outside of the bounds of the array.
Can you share the thr files so I can reproduce it and make sure it is the same bug?
If it is the same bug, then it is fixed in the development branch (or will be shortly when Bobs latest branch gets merged).
Do you have a work around? I think if you changed the first layer to a point, or didn't adjust the progress slider before deleting the layer, then I think it would be ok. I am not planning a release in the near future, so it may just stay a bug for a while.

hi. So for sure after deleted the first standar layer, and then moving the slider, le preview freeze. But sometime only when updating a new drawing or adding a mask make the same freeze. is it the same problem? I don't know. Bellow the 2 thr file for yours tests!
contour2022-02-08222636 (2).thr.txt
centre4.thr.txt
You mention trying with develop branch but how can I test it? is there a web like to the develop branch?


"Getting started" issue

To help CLI users get started with Ludwig, it would be great if you could include an example with an associated downloadable .csv file and a matching model file to train it with.
The current "Getting started" documentation (and the associated examples section) all give a sketch of what the .csv file could look like for a particular scenario, but without a specific file that users can try.  Providing a starting "hello world" pair of .csv /model files help eliminate these as a source of error when users are trying to establish their first successful run with ludwig.

Check out the example about Kaggle's Titanic: Predicting survivors.

The kaggle link confused me (since it doesn't mention ludwig anywhere), but then I found the ludwig Titanic example.  OK, nice!  But its buried way down in the examples.  Can you make it so there is an example with a downloadable pair of files at the top of the examples (and preferably also in the "Getting Started") section?  Thanks!

It's a good suggestion, will do it, thank you!

We added many examples with reference datasets, so i consider this solved.


NVP/SOAP API was deprecated

Hi Peter!
This module should be updated as soon as possible because, for live accounts, is not possible to create API signature anymore.
This is the new PayPal REST API: https://developer.paypal.com/docs/api/overview/.
I would like to help to update this module, but I'm not able to do it from scratch. If you could implement the new authorization method (request token etc.), I can make the following work.
Many thanks

@petersirka Hello Peter! Is this module still going to be updated ??

Hi, is there any hope of this package being maintained in the future?

Hi @Lioness100 - currently, we are busy updating of code. But we want to update all of our unmaintained repositories. Thank you!


Is there a full screen button available to watch the videos in full screen.

Is there a full screen button available to watch the videos in full screen??/

The is a button on the native iOS control. Not on the others currently.

Duplicate of #14