general terms not for direct annotation

I said I would start to submit terms to be flagged "not for direct annotations" as it should always be possible to be more specific.
Here is the first batch.
We plan to do this in stages. These are fairly no brainer.
I think it should probably be a sort check (warnings) in the first instance, then become a hard check later. if possible it would be good to enforce as a hard check for new annotations but give people a chance to improve legacy annotations.
For most of these the block should probably propagate to most parents except for the root node.
GO:0032502	developmental process (what type?)
GO:0051704	multi-organism process (what type)
GO:0022402	cell cycle process (what type?)
GO:0022411	cellular component disassembly (which  component?)
GO:0022414	reproductive process (what type?)
GO:0044703	multi-organism reproductive process (what type?) (1 direct annotation)
GO:0044764	multi-organism cellular process (what type?)

GO:0030281	structural constituent of cutaneous appendage (what type?)
GO:0022403	cell cycle phase (this entire  should be blocked anyway?)
GO:0016043	cellular component organization
GO:0006464	cellular protein modification process
GO:0009058	biosynthetic process
GO:0009059	macromolecule biosynthetic process
GO:0009109	coenzyme catabolic process
GO:0010638	positive regulation of organelle organization
GO:0010639	negative regulation of organelle organization
GO:0070925	organelle assembly
GO:0006996	organelle organization
GO:0005215	transporter activity
GO:0048518	positive regulation of biological process
GO:0048519	negative regulation of biological process
GO:0048522	positive regulation of cellular process
GO:0048523	negative regulation of cellular process (2 direct annotations)
GO:2000241	regulation of reproductive process
GO:1903506	regulation of nucleic acid-templated transcription
GO:1903507	negative regulation of nucleic acid-templated transcription
GO:1903508	positive regulation of nucleic acid-templated transcription
GO:1903649	regulation of cytoplasmic transport
GO:1903651	positive regulation of cytoplasmic transport
GO:0043900	regulation of multi-organism process
GO:0043902	positive regulation of multi-organism process

some more
(when I looked at these a few weeks ago I checked some direct annotation numbers, they were very low so these should not be very  much annotation deepening, however I have >1000, some are quite specific I'm not sure they will all be able to be included as general rules for all systems)
GO:0033036	macromolecule localization
GO:0032879	regulation of localization
GO:0033043	regulation of organelle organization
GO:0051179	localization
GO:0033365	protein localization to organelle
GO:0051640	organelle localization
GO:0051641	cellular localization
GO:0008152	metabolic process
GO:0009056	catabolic process
GO:0009057	macromolecule catabolic process
GO:0009894	regulation of catabolic process
GO:0009987	cellular process
GO:0009889	regulation of biosynthetic process
GO:0009890	negative regulation of biosynthetic process
GO:0009891	positive regulation of biosynthetic process
GO:0009892	negative regulation of metabolic process
GO:0009893	positive regulation of metabolic process
GO:0031323	regulation of cellular metabolic process
GO:0031324	negative regulation of cellular metabolic process
GO:0031325	positive regulation of cellular metabolic process
GO:0031326	regulation of cellular biosynthetic process
GO:0031327	negative regulation of cellular biosynthetic process
GO:0031328	positive regulation of cellular biosynthetic process
GO:0031329	regulation of cellular catabolic process
GO:0032386	regulation of intracellular transport
GO:0032388	positive regulation of intracellular transport
GO:0046907	intracellular transport

Note to self, the submitted terms are documented at the bottom of
GO_terms_excluded_from_pombase.txt
under "submitted to GO"

Do we really want to do this in the era of GO-CAM models?

@ukemi - I am wondering why use of GO-CAMs would effect whether or not we want to make direct annotation to these terms. I don't think I'm following your line of thought here.

please can we keep the organelle terms as direct annotations allowable as I am not sure that we have the child terms for every organelle, therefore we will need to specify the organelle in some cases using the GO-CAM or AE options
Thanks
Ruth

In pombe 25% of process annotated proteins are annotated to "organelle organization" we need to be more specific than this!

So you want to create organelle specific terms for all of these terms:
GO:0070925	organelle assembly
GO:0006996	organelle organization
GO:0010638	positive regulation of organelle organization
GO:0010639	negative regulation of organelle organization
GO:1903649	regulation of cytoplasmic transport
GO:1903651	positive regulation of cytoplasmic transport
plus component specific terms for all of these (which includes complexes, but I guess in this case the complex general term can be used)
GO:0022411	cellular component disassembly
GO:0016043	cellular component organization
plus protein/complex specific terms for all of these:
GO:0009059	macromolecule biosynthetic process
GO:0009109	coenzyme catabolic process
GO:0005215	transporter activity
GO:0006464	cellular protein modification process

@RLovering  I think you have misunderstood what we are doing here.
The specific terms already exist. They should be used for annotation rather than the broad terms.
There terms are very rarely used, and that is good, but the point is that they should not be used at all, becasue they are not informative about the biology.

GO:0016043	cellular component organization
Again 26% of pombe proteins have this annotation. NONE are direct. Why would anyone want to annotate directly to this term, it doesn't tell you anything?

Hi @krchristie. For exactly the reason Ruth points out above. Although some specific terms already exist, I'm not sure they are exhaustive. So for a term like 'cellular component organization', to be exhaustive we would need to create a child for every type of cellular component that can be organized.

we would need to create a child for every type of cellular component that can be organized.

Surely we need to go beneath the granularity of  "GO:0016043	cellular component organization".....see above, this term is rarely used, and rightly so.
Eventually, you will need a precise process. Exactly what is being organized? the mitochondrial membrane? the crista? the respiratory chain? the genome? How is being organized (by assembly? disassembly? by fusion?).
I selected these terms very carefully because they should not require much, if any reannotation. However, they will force curators to think about how to annotate precisely and improve annotation consistency.

The other problem is that many components are dynamic, and it can be difficult to know if proteins are regulating the assembly or disassembly. ie pos reg of assembly may look the same as neg reg of disassembly.

cellular component organisation and biogenesis (0 direct annotations)
cellular component organization (2 direct annotations)
cellular component maintenance  (3 direct annotations)

regulation of cellular component organization (18)
positive regulation of cellular component biogenesis (8)
regulation of cellular component organization (2)
cellular component assembly (7)

I can migrate to a spereadsheet.
Will do it next week.
val

GO:0008219 cell death (type (need to know it is programmed death… necrosis, apoptosis etc)
GO:0007050 cell cycle arrest (mitotic? meiotic? phase?)
GO:0009987 cellular process (which process?) (393 direct annotations all evidence codes)
GO:0032501 multicellular organismal process (which process?) (2 direct annotations all evidence codes)
GO:0044764 multi organism cellular process (which process?) (0 direct annotations, any evidence code)
GO:0022607 cellular component assembly (of which component?) (7 direct annotations, any evidence code)
GO:0071840 cellular component organisation or biogenesis (of which component?) (0 direct annotations, any evidence code)
GO:0016043 cellular component organization (of which component?) (68 direct annotations, any evidence code)
GO:0044085 cellular component biogenesis (of which component?) (0)
GO:0051179 localization (or what, to where?) (0 direct annotations, any evidence code)
PLUS ALL CORRESPONDING REGULATION TERMS (same rationale)

I see I was going to transfer to a spreadsheet. I'll do this next week if I didn't do it already...

now in a spreadsheet in the QC directory called
High_level_terms_not_for_direct_annotation
https://docs.google.com/spreadsheets/d/1B_ItIn5bX_4gj41MQIQoBlpaxLT1co14ALBUYhEQahk/edit#gid=0

@pgaudet
re the recent discussion about high level terms- I suggest we  flag the ones in the spreadsheet above which already have this attribute.
Then add  restrictions to the ones without. After this, we can move on to mine and Christophe's longer lists and add them to this spreadsheet?
Is that a realistic plan?

Ok I have removed/changed some of UCL annotations,
cell death : 3 annotations
developmental process: 1 annotation
we have no annotations to regulation of developmental process (+/-) - which I assume are not acceptable.
But we have 51 annotations to the regulation of cell death terms - which I assume are not acceptable
https://www.ebi.ac.uk/QuickGO/annotations?goUsage=exact&goUsageRelationships=is_a,part_of,occurs_in&goId=GO:0010942,GO:0060548,GO:0010941&assignedBy=ARUK-UCL,Alzheimers_University_of_Toronto,BHF-UCL,HGNC-UCL,ParkinsonsUK-UCL,SynGO-UCL
However, these will take longer to assess and update. Are you planning to created a doc for us to record the edits?
Thanks
Ruth

Yes yes, this is a placeholder for now, no immediate action needed (lower priority than other items). Thanks for checking!
Pascale

Most of the above are now adressed.
Revised list below:
GO:0009057	macromolecule catabolic process
GO:0009056	catabolic process
GO:0009058	biosynthetic process
GO:0031325	positive regulation of cellular metabolic process
GO:0031326	regulation of cellular biosynthetic process
GO:0070925	organelle assembly
GO:0051640	organelle localization
GO:0033365	protein localization to organelle
GO:2000241	regulation of reproductive process
GO:0008152	metabolic process
GO:0033043	regulation of organelle organization
GO:0033036	macromolecule localization
GO:0044703	multi-organism reproductive process
GO:0019953	sexual reproduction
GO:0030281	structural constituent of cutaneous appendage
GO:0010639	negative regulation of organelle organization
GO:0010638	positive regulation of organelle organization
GO:0009889	regulation of biosynthetic process
GO:0022414	reproductive process
GO:0032502	developmental process (we probably need to allow for extensions)
GO:0046907	intracellular transport
GO:0009893	positive regulation of metabolic process
GO:0009892	negative regulation of metabolic process
GO:0009891	positive regulation of biosynthetic process
GO:0009890	negative regulation of biosynthetic process
GO:0009894	regulation of catabolic process
GO:0032388	positive regulation of intracellular transport
GO:0032386	regulation of intracellular transport
GO:0036211	protein modification process (we probably need to keep this)


Add the website to this one (or its own one)

I was hoping to suggest an edit around installation but couldn't make a PR (it was to log in & out as a user on macOS to pick up the new keyboard). Would you be up for making the website available in GitHub?

It's been a long time since the website has had an update, so I'm actually not 100% sure where I'm hosting it right now. I'm pretty sure it's github pages and you can do a PR against the gh-pages branch, and a merge would automatically publish. https://github.com/deekayen/norman/tree/gh-pages


add more Sinhala names for cities

Thank a lot brother for your contribution. Please remember always update your local files before sending a push request to the repository.


Updating PHP versions 7.3.23 and 7.2.34

Updating PHP versions 7.3.23 and 7.2.34

Did this not get deployed to App Engine flex? I just did a build and it installed 7.3.19.


Cow: Watch jokerwigs.in

Cow requests the watch of the watch_keyword jokerwigs\.in. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

jokerwigs\.in has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by VLAZ in Charcoal HQ


Opening modal from link

I am simply trying to open a modal window from a link:
Click Me
And with a simple modal pulled from the BS documentation:

Modal title

        <button type="button" class="btn-close" data-bs-dismiss="modal" aria-label="Close"></button>

        ...

        <button type="button" class="btn btn-secondary" data-bs-dismiss="modal">Close</button>
        <button type="button" class="btn btn-primary">Save changes</button>

When clicking the link I get a javascript error:
Uncaught TypeError: Cannot read properties of null (reading 'hide')
Does anyone have any ideas?
I have included jQuery but have tried without this and get the same issue.

Nevermind, I had an issue because I had copied several other modals from an older Bootstrap 4 setup, which had incorrect classes, but was causing an issue. This is working just fine for me now.


Unable to install 0.6 version

I am trying to install in python3.4 virtuanenv and it is failing with this error.
(34)
# anand at anand in ~/projects/python/ocr/chamanti_ocr on git:master x [15:46:38]
$ pip3 install cairocffi==0.6
Traceback (most recent call last):
  File "/home/anand/.virtualenvs/34/bin/pip3", line 7, in <module>
    from pip import main
  File "/home/anand/.virtualenvs/34/lib/python3.4/site-packages/pip/__init__.py", line 16, in <module>
    from pip.vcs import git, mercurial, subversion, bazaar  # noqa
  File "/home/anand/.virtualenvs/34/lib/python3.4/site-packages/pip/vcs/mercurial.py", line 9, in <module>
    from pip.download import path_to_url
  File "/home/anand/.virtualenvs/34/lib/python3.4/site-packages/pip/download.py", line 39, in <module>
    from pip._vendor import requests, six
  File "/home/anand/.virtualenvs/34/lib/python3.4/site-packages/pip/_vendor/requests/__init__.py", line 53, in <module>
    from .packages.urllib3.contrib import pyopenssl
  File "/home/anand/.virtualenvs/34/lib/python3.4/site-packages/pip/_vendor/requests/packages/urllib3/contrib/pyopenssl.py", line 54, in <module>
    import OpenSSL.SSL
  File "/home/anand/.virtualenvs/34/lib/python3.4/site-packages/OpenSSL/__init__.py", line 8, in <module>
    from OpenSSL import rand, crypto, SSL
  File "/home/anand/.virtualenvs/34/lib/python3.4/site-packages/OpenSSL/rand.py", line 12, in <module>
    from OpenSSL._util import (
  File "/home/anand/.virtualenvs/34/lib/python3.4/site-packages/OpenSSL/_util.py", line 6, in <module>
    from cryptography.hazmat.bindings.openssl.binding import Binding
  File "/home/anand/.virtualenvs/34/lib/python3.4/site-packages/cryptography/hazmat/bindings/openssl/binding.py", line 15, in <module>
    from cryptography.hazmat.bindings._openssl import ffi, lib
AttributeError: 'module' object has no attribute '_init_cffi_1_0_external_module'

Closing as it was a pip issue.


retina-agent pod initialization failed to no BTF found for kernel version

Describe the bug

installation commands:
make helm-install-with-operator

retina-agent pod status as follows:
kube-system            pod/retina-agent-bq6s8                          0/1     CrashLoopBackOff   5 (2m29s ago)
kube-system            pod/retina-agent-lkpgn                          0/1     CrashLoopBackOff   5 (2m23s ago)
kube-system            pod/retina-agent-psqgp                          0/1     CrashLoopBackOff   5 (2m29s ago)
kube-system            pod/retina-operator-8445c8c6f6-st5mq            1/1     Running            0

retina-agent containers error logs is:
ts=2024-04-09T09:19:38.229Z level=info caller=server/server.go:71 msg="HTTP server stopped with err: http: Server closed" goversion=go1.21.8 os=linux arch=amd64 numcores=1 hostname=k8s-node2 podname=retina-agent-bq6s8 version=v0.0.4 apiserver=https://<IP_ADDRESS>:443 plugins=dropreason,packetforward,linuxutil,dns
ts=2024-04-09T09:19:38.229Z level=panic caller=controllermanager/controllermanager.go:119 msg="Error running controller manager" goversion=go1.21.8 os=linux arch=amd64 numcores=1 hostname=k8s-node2 podname=retina-agent-bq6s8 version=v0.0.4 apiserver=https://<IP_ADDRESS>:443 plugins=dropreason,packetforward,linuxutil,dns error="failed to reconcile plugin dropreason: field InetCskAccept: program inet_csk_accept: apply CO-RE relocations: load kernel spec: no BTF found for kernel version 5.4.272-1.el7.elrepo.x86_64: not supported" errorVerbose="field InetCskAccept: program inet_csk_accept: apply CO-RE relocations: load kernel spec: no BTF found for kernel version 5.4.272-1.el7.elrepo.x86_64: not supported\nfailed to reconcile plugin dropreason\ngithub.com/microsoft/retina/pkg/managers/pluginmanager.(*PluginManager).Start\n\t/go/src/github.com/microsoft/retina/pkg/managers/pluginmanager/pluginmanager.go:169\ngithub.com/microsoft/retina/pkg/managers/controllermanager.(*Controller).Start.func1\n\t/go/src/github.com/microsoft/retina/pkg/managers/controllermanager/controllermanager.go:109\ngolang.org/x/sync/errgroup.(*Group).Go.func1\n\t/go/pkg/mod/golang.org/x/sync@v0.6.0/errgroup/errgroup.go:78\nruntime.goexit\n\t/usr/local/go/src/runtime/asm_amd64.s:1650"
panic: Error running controller manager

goroutine 145 [running]:
go.uber.org/zap/zapcore.CheckWriteAction.OnWrite(0x1?, 0x41a508?, {0x0?, 0x0?, 0xc000a05940?})
/go/pkg/mod/go.uber.org/zap@v1.26.0/zapcore/entry.go:196 +0x54
go.uber.org/zap/zapcore.(*CheckedEntry).Write(0xc0008f0c30, {0xc000830300, 0x1, 0x1})
/go/pkg/mod/go.uber.org/zap@v1.26.0/zapcore/entry.go:262 +0x3ec
go.uber.org/zap.(*Logger).Panic(0xc000830000?, {0x2b52d30?, 0x8fbec0?}, {0xc000830300, 0x1, 0x1})
/go/pkg/mod/go.uber.org/zap@v1.26.0/logger.go:284 +0x51
github.com/microsoft/retina/pkg/managers/controllermanager.(*Controller).Start(0xc000615ef0, {0x2f10a90?, 0xc000615ea0?})
/go/src/github.com/microsoft/retina/pkg/managers/controllermanager/controllermanager.go:119 +0x28c
created by main.main in goroutine 1
/go/src/github.com/microsoft/retina/controller/main.go:290 +0x28d0
Expected behavior

retina-agent pod status is normal.

Platform (please complete the following information):

OS: CentOS Linux 7 (Core)
Kernel Version: 5.4.272-1.el7.elrepo.x86_64
Kubernetes Version: 1.24.9
Host: local kubernets
Retina Version: v0.0.4

Reopened this to triage it with the team. Given CentOS 7 doesn't really support eBPF/BTF and will anyway be EOL in 2 months, we are closing this as wontfix.

@rbtr Thank you for your response. We found that the effectiveness of enabling BTF support on CentOS 7 through the BTFHub installation method is not satisfactory. We achieved eBPF support on CentOS 7 by upgrading the kernel version, but also discovered that BTF is not supported by default. Many of our servers are still running on CentOS 7, and we have also observed the lack of default BTF support on servers using the aarch architecture. We would like to suggest that Retina consider providing compatibility support for systems that do not have BTF support enabled by default. Thank you.

I think that's a reasonable ask, would you mind opening a new issue for this feature request? There we can further discuss the options for supporting more kernels/distros that ship without BTF


Filter spending/income by date range

As an organised user, I want to filter my spending/income by date range so that I can have an overview of the amount I spent in a given period

Also change date to LocalDate


Bug: Not all Tier-files are displayed

If the Tier files are to be aggregated as input by the Python script, sometimes only 3 files are aggregated for some parameters instead of the 4 files provided in Plotly.

I further analyzed the errors in the visualization and here are the details:
Process(es): OEM Verify Negotiation State, (OEM Verification Transfer State)
Error: No visualization, despite the fact that the values are >0
Reason: Visualization is based on median values - e.g. the maximum response time for Tier 3 is 67 ms, but the median is still 0
Process(es): Fleet Query Catalog
Error: No visualization of Tier 2 despite a value of 252 ms
Reason: Incorrect Y-scaling due to high differences between Tier 2 (252 ms) and Tier 3 (1724 ms)
Process(es): Get Negotiation State, Fleet Initiate Negotiation, Fleet Negotiation Complete, Fleet Transfer Complete, Fleet Initiate Transfer, Fleet Get Negotiation
Error: No visualization of Tier 5
Reason: There is no data for this intermediate process in Tier 5 (not even the process is mentioned in the metadata)
Process(es): Fleet Verify Negotiation State, (Fleet Verify Transfer State)
Error: No visualization of all tiers and tier 5 is not even listed
Reason: Visualization is again based on median values, which are 0, for Tier 5 there is no data on the process
The values are also all the same due to the basis of the median value, e.g. for OEM Get Supplier Asset.

Janis provided another review and the mentioned errors were fixed


use umd, update docs

This PR:

Wraps each Slick module in a UMD
Adds a compatibility build for consumers that expected Slick.Data.DataView (etc.) as opposed to just DataView

:+1:


Replace NetrcOnlyTrusted with list of trusted plugins for netrc

As noticed in several PRs the current option NetrcOnlyTrusted is limiting users, but on the other hand not really protecting them as well as netrc credentials could be stolen by a custom clone step with custom commands.

https://github.com/woodpecker-ci/woodpecker/pull/2585#issuecomment-1765756023
https://github.com/woodpecker-ci/woodpecker/pull/2214

To prevent this a pass-netrc-to-plugins option should replace the NetrcOnlyTrusted option. This option would contain list of images which will receive the netrc credentials if they are used as plugins. If the image however uses custom commands it wont get the credentials as those commands could be changed by others than the admin.
This will allow all steps and the clone step to use netrc credentials. It will however be breaking as it wont be possible anymore to use clone steps with custom commands.

If the image however uses custom commands it wont get the credentials

Then we're still missing an option that allows the use of credentials in custom steps/images. If the repo admin wants to allow it (e.g. in private repos).
Currently this is only possible on the instance level by setting the repo to "trusted" but not on the repo level.
So why not structure it like this:

Option to allow injecting netrc into plugins/trusted images
Option to allow injecting netrc into any image

The use case I had was a step executing arbitrary git commands, among them git push, to push back to the repo. Many people like this style instead of having to use a plugin as it "feels like freedom" ;)

is this not solved by simply make
https://github.com/woodpecker-ci/woodpecker/blob/26b77ed677bb6121f35cdba2731692d26bd5b3de/shared/constant/constant.go#L39-L42
as an configuration option?

an option only instance admins should change in any case

well that would allow any one to steal other users credentials at codeberg:

propose for ci acces
create own repo
let other users creat pulls
you got all there oauth2 tokens :tada:

you got all there oauth2 tokens 🎉

I am also not for exposing those secrets to easily (as commented before), but your point seems to be wrong.

Is cloning using the tokens of the pipeline authors? Shouldn't it use the repo users/owners?

It uses the oauth token of the first repo admin (might be updated to another repo admin later not 100% sure).

Maybe we should limit this to plugins?

An image filter would be for plugins only as otherwise it would not limit protect (similar to #2213).

For github forge, it would make the credentials non-sensitive, if it is converted to a github app, using short lived and restricted access tokens.
Is something similar possible on the other forges?

Do we know how other CI providers handle this? We should also take into account that this is a complicated situation for users if "too much" magic is happening behind the scenes or certain things only apply in some special situations. Also WRT to documentation.
A situation which is popular in the instances I managed (and which worked/still works in drone) is to use arbitrary git commands to apply some git modifications and then push back to the cloned repo. For this a git plugin would only partially help (unless it has a setting where one could input arbitrary git commands of infinite length).

How does drone handle this? It's a really critical security issue if you just expose some random oauth tokens.
Also, we can't say to just use the token of the pipeline author (e.g. PR author), because the pipeline author is not necessarily registered so we don't have a token.

I agree, not saying we should do the same. Just reporting how it works.
What I got as a reply from users when telling them to migrate their workflows was "Ugh, I don't like this, this is a step backwards. Can we stay with drone?" 🥴 -> which is why I opened the discussion in the first place as I want them to use/be happy with WP of course 😅

It's also not clear to me, unfortunately. The pipeline I am talking about does the following
kind: pipeline
type: kubernetes
name: CI

steps:
  - name: CI
    image: <some image with git>
    commands:
      - git fetch origin json
      [...]
      - git status
      - git diff --numstat
      - git remote -v
      - git add .
      - git commit --message "Automated import"
      - git push

and the git push just works. No manual secret added. I've checked the drone config itself and everything around (set up by myself) but I couldn't yet infer why this actually works. I know there is https://github.com/appleboy/drone-git-push for such use cases as it shouldn't work OOB. Maybe it's related to the drone kube runner which handles auth things differently compared to running drone on a single VM with the docker backend?

https://docs.drone.io/runner/docker/configuration/reference/drone-netrc-clone-only/

I am not 100% sure, but I think it is mounting /root/.netrc to steps.


Can't find file .bash_profile file or .zshrc

Can't find file .bash_profile file or .zshrc

Open terminal and type:
cd ~
sudo nano .bash_profile
or
 sudo nano .zshrc


[enhancement] add a link to synthetic efficiency

Found it finally. I suggest to have a link to the source: https://worksheets.codalab.org/bundles/0x17a361bc066b4b0e87d968069759d361

Classic is archived; won't fix.


fix: actiongroup wrapping

This PR modifies the CSS of ActionGroup to add top (block start) and right (inline-end) margins to fix the wrapping issue reported in Issue #749
Description

How and where has this been tested?

How this was tested:
Browser(s) and OS(s) this was tested with:

Screenshots

To-do list

[x] If my change impacts other components, I have tested to make sure they don't break.
[x] If my change impacts documentation, I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.

[x] This pull request is ready to merge.

Thanks again for your contribution @Martskin . I merged this in #755


Updating Required and Optional fields in Test schema

https://clkentik.atlassian.net/browse/KNTK-313

@mmac-m3a I was sending a POST request using postman and checked each API attribute. Whether the attribute is marked as optional or required depends on whether the request without the attribute was successful or not. Do you think it is a sufficient method of establishing if an attribute is required or not?

@mmac-m3a I was sending a POST request using postman and checked each API attribute. Whether the attribute is marked as optional or required depends on whether the request without the attribute was successful or not. Do you think it is a sufficient method of establishing if an attribute is required or not?

I think that we need to have a minimal test resource example in examples directory. That way a developer can easily check if a set of required fields is up-to-date. It would be also beneficial for users.
Having integration test that creates minimal test would be nice to have, but I worry that it would require fiddling with fake API server.

Bulk test create examples (which contain ~minimal set of fields) do not pass schema validation. However, they also do not work on master branch, so I just created a bug and it can be fixed then: https://clkentik.atlassian.net/browse/KNTK-337

I've created new PR pointing to my branch, where I continue the work: https://github.com/kentik/terraform-provider-kentik-synthetics/pull/53
This PR can be closed now.

No longer needed, superceeded by PR https://github.com/kentik/terraform-provider-kentik-synthetics/pull/53


Convert to libdnf plugin

The Python based plugin system is well established and documented. The downside is that it doesn't work with packagekit, or other tooling that directly interacts with libdnf (including dnf5 / microdnf)
I was originally going to supersede this code and project by doing a PR against libdnf. After more investigation I've found this isn't the right approach. While there is an example plugin in libdnf, it's not easily built. The expectation is that all libdnf plugins will be completely separate packages. To build said packages, you need libdnf-devel, but that's not provided on RHEL / CentOS today making this overly complex. You also need a distinct code base, so this repo continues to have purpose.
As the deadlines for Fedora 34 are looming, I will opt to do the following in the short term:

Establish a new package in rawhide called 'dnf-plugin-cow' with this code
Ship that. It will work with dnf as expected, and remains a limited, opt-in new feature for Fedora 34
Later I or someone else comes back around to this project, and re-implements it as a libdnf plugin. I think it's generally okay to call this project and package dnf-plugin-cow even if should really be called libdnf-plugin-cow. We can rename later if it's important.

How about this now that dnf is going to be the default at F41? https://github.com/rpm-software-management/dnf5/issues/389#issuecomment-2168568966

Yes, this is still planned.


[Bug] Wand Controles

When you buy a "Inventory mode" in Wand controles you will get the item in your hotbar. There are no errors in the console. I only want to let you know about his :D

Thanks, fixed in latest dev build! Configs were missing the "apply_to_wand" tag.


Forge only?

I run a Fabric server. Does this vulnerability affect it?

Yes. This is a core mod though, so it's compatible with both loaders. Check the installation instructions.

To give some context to this, the project was really only made with Forge in-mind as that is where most of the exploit users were coming from. We are working to ensure compatibility with other loaders and across versions as much as possible. It is compatible with lots of versions already, but we need more testers on more platforms to be sure and help work out any bugs.
In theory, the vulnerability could affect any mod that is using unsafe use of the Java serialization feature in network packets. While we haven't seen any cases yet, there is always the possibility. We just don't have enough information at this time to officially confirm anything.

Yes. This is a core mod though, so it's compatible with both loaders. Check the installation instructions.

I'm not using Forge, so I used the second set of instructions with the -javaagent: thing, but that just immediately crashes my server.
[17:49:37] [main/ERROR]: Failed to start the minecraft server joptsimple.UnrecognizedOptionException: a is not a recognized option 	at joptsimple.OptionException.unrecognizedOption(OptionException.java:108) ~[jopt-simple-5.0.4.jar:?] 	at joptsimple.OptionParser.validateOptionCharacters(OptionParser.java:633) ~[jopt-simple-5.0.4.jar:?] 	at joptsimple.OptionParser.handleShortOptionCluster(OptionParser.java:528) ~[jopt-simple-5.0.4.jar:?] 	at joptsimple.OptionParser.handleShortOptionToken(OptionParser.java:523) ~[jopt-simple-5.0.4.jar:?] 	at joptsimple.OptionParserState$2.handleArgument(OptionParserState.java:59) ~[jopt-simple-5.0.4.jar:?] 	at joptsimple.OptionParser.parse(OptionParser.java:396) ~[jopt-simple-5.0.4.jar:?] 	at net.minecraft.server.Main.main(Main.java:90) ~[server-intermediary.jar:?] 	at net.fabricmc.loader.impl.game.minecraft.MinecraftGameProvider.launch(MinecraftGameProvider.java:468) ~[fabric-loader-0.14.21.jar:?] 	at net.fabricmc.loader.impl.launch.knot.Knot.launch(Knot.java:74) ~[fabric-loader-0.14.21.jar:?] 	at net.fabricmc.loader.impl.launch.knot.KnotServer.main(KnotServer.java:23) ~[fabric-loader-0.14.21.jar:?] 	at net.fabricmc.loader.impl.launch.server.FabricServerLauncher.main(FabricServerLauncher.java:69) ~[fabric-loader-0.14.21.jar:?] 	at net.fabricmc.installer.ServerLauncher.main(ServerLauncher.java:69) ~[fabric-server-mc.1.20.1-loader.0.14.21-launcher.0.11.2.jar:0.11.2]

[17:49:36] [main/INFO]: Loading Minecraft 1.20.1 with Fabric Loader 0.14.21

I am guessing this will probably be fixed in #43

"C:\Program Files\Java\jdk-17.0.1\bin\java.exe" -server -Xmx8G -Xms1024M -jar fabric-server-mc.1.20.1-loader.0.14.21-launcher.0.11.2.jar nogui -javaagent:serializationisbad-1.3.jar

-javaagent has to be before -jar

-javaagent before -jar just immediately causes the server to crash without so much as generating a latest.log.

This issue is fixed in the 1.4 prerelease.

Thanks for the confirmation! Closing the issue.


Fix interactive message submit button by adding a default when none i…

…s defined
Summary
Previously, dialogs that did not define a submit_label did not show any name on the submit button on the navigation bar. This led to believe it was not showing he button, but the button was still there (but with empty content).
This PR adds a default text.
Ticket link
Fixes: https://github.com/mattermost/mattermost-mobile/issues/5543
Release Note
Fix error where the submit button on interactive dialogs was not shown when the dialog did not specify the `submit_label`.

Thanks a lot @larkox for the super quick investigation and fix!

/update-branch

Building app in separate branch.

@DHaussermann Friendly reminder to test this.
Regarding how to test, all dialogs on the test app on /test other open_dialog_from_interactive_message don't have set the submit label, so they could be used to test.

/update-branch

Building app in separate branch.


Did not compile on modern Linux, fix included

Support for matherr() ended in glibc 2.27. Changed the default in src/lisp.h to not use if on Linux, unless HASMATHERRFUNCTION is defined on compiler command line.
diff --git a/src/lisp.h b/src/lisp.h
index aea064d..7cecee6 100644
--- a/src/lisp.h
+++ b/src/lisp.h
@@ -212,7 +212,12 @@
 #define   SIGINTWORKS             1
 #define   SIGFPEWORKS             1
 #define   HASFCLOSEALL            1             /* has fcloseall() in stdio */
-#define   HASMATHERRFUNCTION      1
+/* Support for matherr() ended in glibc 2.27. Define HASMATHERRFUNCTION as 1
+   in Makefile, if you are using an older glibc, or some alternate libc that
+   supports the feature. */
+#ifndef HASMATHERRFUNCTION
+#define   HASMATHERRFUNCTION      0
+#endif
 #define   WANTERRNOTESTING        1             /* check errno after calls */
 #define   GRAPHICSAVAILABLE       0
 #define   NEEDNLAFTERBREAKEXIT    1

Thank you very much!  I'll integrate it ASAP.


Console Page Error

i upgrade crate version from 0.54 to 0.56.2
when i open then console page , excete sql ,the page is error
error msg:

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/38529267-console-page-error?utm_campaign=plugin&utm_content=tracker%2F505663&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F505663&utm_medium=issues&utm_source=github).

hi @foreachsky
a fix for this issue has already been applied on master and will be available with the next 0.56 hotfix release.
https://github.com/crate/crate-admin/issues/244


Support for non-static dimensionality?

For higher-dimensional problems it would be great to have support for non-static dimensionality and argument types like Vector in addition to SVector. E.g. a ProductDomain based on AbstractVector{IntervalSet} should allow for in(x::AbstractVector, d::ProductDomain). N-dimensional hyper-spheres with N not fixed at compile time would also come on very handy.

That sounds doable. Currently the spheres are hardcoded to be EuclideanDomain, but ProductDomain already mostly works more generically. If you comment out the two checks in the inner constructor here, then you get this behaviour:
julia> using DomainSets

julia> b = 0..1.0
0.0..1.0

julia> domains = [b for i in 1:10]
10-element Array{Interval{:closed,:closed,Float64},1}:
 0.0..1.0
 0.0..1.0
 0.0..1.0
 0.0..1.0
 0.0..1.0
 0.0..1.0
 0.0..1.0
 0.0..1.0
 0.0..1.0
 0.0..1.0

julia> p = DomainSets.ProductDomain{typeof(domains),Vector{Float64},Vector{Float64}}(domains)
0.0..1.0 x 0.0..1.0 x 0.0..1.0 x 0.0..1.0 x 0.0..1.0 x 0.0..1.0 x 0.0..1.0 x 0.0..1.0 x 0.0..1.0 x 0.0..1.0

julia> rand(10) ∈ p
true

julia> 2*rand(10) ∈ p
false

(The final test will succeed with some probability.)
I've invoked the constructor explicitly here. It would be a matter of modifying the computation of the element types, plus finding a nicer way of invoking the constructor. Perhaps when invoked with an array of domains, a ProductDomain could use array's as type. When invoked with an argument list of domains, it could be a tuple.
It is similar with the spheres: there could be an AbstractHyperSphere{T} <: Domain{T} and an AbstractEuclideanHyperSphere{N,T} <: AbstractHyperSphere{SVector{N,T}}. And some syntax for constructing them. Care to look at it?

Maybe, yes. I have something similar in BAT.jl, for boundaries for likelihoods and priors and I was looking for a solution that's more generic. DomainSets may be a great fit.

Cool, I hope using DomainSets works out. You suggested an interesting generalization that fits well in the package, because the whole aim is to be general and avoid repetition in other packages. I will try to get to this particular issue soon, and update here.

Great, thanks! I think this could be a valuable building block for statistics/fitting/optimization/etc. applications, to avoid redundant functionality across packages.

Working on it in #55. It motivated working on some other issues as well, and #55 will perhaps take some time and additional effort before we can merge it I'm afraid.

Thanks, @daanhb! I'l try to pitch in at some point, I'll try to get a clearer idea on requirements - and how to represent them more cleanly than I do at the moment - first, for such applications  (statistics/fitting/optimization/...).

The changes have been merged into version 0.3. The README is updated with a few examples of basic usage. Issues are to be expected - please report! :-)

Thanks a lot - will do!


Fix includes

Remove unused includes and forward declarations.

SonarQube analysis reported 13 issues

 13 minor

Top 10 extra issues
Note: The following issues were found on lines that were not modified in the pull request. Because these issues can't be reported as line comments, they are summarized here:

 AncientFungus:LGEPR: Cppcheck cannot find all the include files (use --check-config for details)
 RenderManager.cpp#L494: The function 'GetAnimations' is never used.
 RenderManager.cpp#L512: The function 'GetDirectionalLights' is never used.
 RenderManager.cpp#L531: The function 'GetLenses' is never used.
 RenderManager.cpp#L551: The function 'GetMaterials' is never used.
 RenderManager.cpp#L569: The function 'GetMeshes' is never used.
 RenderManager.cpp#L588: The function 'GetPointLights' is never used.
 RenderManager.cpp#L610: The function 'GetSpotLights' is never used.
 ScriptManager.cpp#L582: The function 'ClearBreakpoints' is never used.
 ScriptManager.cpp#L846: The function 'GetStringDeclarationID' is never used.


Provide complete initial downloadable archives

@tzaeru : This is mostly a note for me unless you do it sooner (although you'd certainly be much more capable at this than me)
Goal: Host complete initial game versions on this backend as well
Currently we'd still need to distribute the initial version someplace else.
Our download links could instead provide downloads with the spring-launcher + game dist_cfg included.
Basically, I want to transform the current download links to:

http://tzaeru.com:4445/download?path=Balanced-Annihilation-Linux.zip
http://tzaeru.com:4445/download?path=Balanced-Annihilation-Windows.zip
http://tzaeru.com:4445/download?path=SpringBoard-Linux.zip
http://tzaeru.com:4445/download?path=SpringBoard-Windows.zip

This would be done by taking the launcher (frozen) + dist_cfg files from a game (and using those files to overwrite the launcher), and providing this in one download
This would allow us to use the backend for initial downloads - which are always at the latest state of the launcher+game (don't need self-updates)
It also makes it easier for game devs, as they don't have to host their own initial files (i've been using google docs now and it feels like a bad idea, especially as it's not automated)
PS: Once this issue is done I would start using SpringBoard with this launcher-backend system completely.

Also, the executable file (launcher.exe or launcher) should be renamed to game-appropriate name, e.g. SpringBoard.exe, SpringBoard, Balanced-Annihilation.exe, Balanced-Annihilation, depending on the game (human) name and platform


rustup

With https://github.com/rust-lang/rust/pull/91323 landed, we can remove these intrinsics from Miri.

@bors r+

:pushpin: Commit 70dd979a44c5a2c79400285821f7ac0a06eaee55 has been approved by RalfJung

:hourglass: Testing commit 70dd979a44c5a2c79400285821f7ac0a06eaee55 with merge 5e9cf62b894a1df015d8601d8a5ffb5f04b44827...

:sunny: Test successful - checks-actions
Approved by: RalfJung
Pushing 5e9cf62b894a1df015d8601d8a5ffb5f04b44827 to master...


FPGA Addon Scripting API - Create FPGA Addon Unit Test

[x] This contribution adheres to CONTRIBUTING.md.

What does this Pull Request accomplish?

Created Unit Tests for the "Create FPGA  Addon.vi"
BugFix within the "Find FPGA  Addon.vi"
Creates the File/Folder structure for the Scripting API Unit Tests

Why should this Pull Request be merged?

Same as the above

What testing has been done?

Local testing has been done on the dev machine.
Manual testing has been done

Please remove testExample.vit

Please remove testExample.vit

Please remove testExample 1.vi (although I only see it in the diffbot's comment and not in the list of changed files).

Please remove testExample 1.vi (although I only see it in the diffbot's comment and not in the list of changed files).

Please rename the following files, according to our team's conventions:
test_Create FPGA Addon--Error.vi -> test_Create FPGA Addon_Error.vi
test_Create FPGA Addon--Group Scalars.vi -> test_Create FPGA Addon_Group Scalars.vi

Please rename the following files, according to our team's conventions:
test_Create FPGA Addon--Error.vi -> test_Create FPGA Addon_Error.vi
test_Create FPGA Addon--Group Scalars.vi -> test_Create FPGA Addon_Group Scalars.vi

Why is there a need for this new VI that does validation? FPGA Addon Test Class.lvclass--isValid FPGA Addon.vi
Since it is identical to the one in the Scripting API library, I would like for the tests to use that one as well, instead of duplicating the functionality.

Why is there a need for this new VI that does validation? FPGA Addon Test Class.lvclass--isValid FPGA Addon.vi
Since it is identical to the one in the Scripting API library, I would like for the tests to use that one as well, instead of duplicating the functionality.

One more thing: please rename the test class from "Scripting API Unit Tests.lvclass" to "FPGA Addon Scripting API Unit Tests.lvclass". The class name is how we identify the tests on the autotest runner and our convention is to always start with the CD name, to aid searching.

One more thing: please rename the test class from "Scripting API Unit Tests.lvclass" to "FPGA Addon Scripting API Unit Tests.lvclass". The class name is how we identify the tests on the autotest runner and our convention is to always start with the CD name, to aid searching.

Why is there a need for this new VI that does validation? FPGA Addon Test Class.lvclass--isValid FPGA Addon.vi
Since it is identical to the one in the Scripting API library, I would like for the tests to use that one as well, instead of duplicating the functionality.

In the Scripting Library, that subVI is set as private - I did this on purpose. It is not supposed to be used outside the library. Therefore it cannot be used in the test classes. I would like it to stay this way.

Why is there a need for this new VI that does validation? FPGA Addon Test Class.lvclass--isValid FPGA Addon.vi
Since it is identical to the one in the Scripting API library, I would like for the tests to use that one as well, instead of duplicating the functionality.

In the Scripting Library, that subVI is set as private - I did this on purpose. It is not supposed to be used outside the library. Therefore it cannot be used in the test classes. I would like it to stay this way.

Why is there a need for this new VI that does validation? FPGA Addon Test Class.lvclass--isValid FPGA Addon.vi
Since it is identical to the one in the Scripting API library, I would like for the tests to use that one as well, instead of duplicating the functionality.

In the Scripting Library, that subVI is set as private - I did this on purpose. It is not supposed to be used outside the library. Therefore it cannot be used in the test classes. I would like it to stay this way.

Personally, I believe that the need for that functionality outside of the library is the precise indication that the subVI should not be private, in this case. But since I see little chance that these two implementations could diverge, I'm ok with keeping the duplication code in the test class.

Why is there a need for this new VI that does validation? FPGA Addon Test Class.lvclass--isValid FPGA Addon.vi
Since it is identical to the one in the Scripting API library, I would like for the tests to use that one as well, instead of duplicating the functionality.

In the Scripting Library, that subVI is set as private - I did this on purpose. It is not supposed to be used outside the library. Therefore it cannot be used in the test classes. I would like it to stay this way.

Personally, I believe that the need for that functionality outside of the library is the precise indication that the subVI should not be private, in this case. But since I see little chance that these two implementations could diverge, I'm ok with keeping the duplication code in the test class.


Where do you implement the compatibility transform?

I cannot find the place you implement the transform function with the Potts model.

convcompat 1x1 convolution


Failed loading modules from CentOS8 to Rocky Linux

not able to convert the centOS 8 machine to rocky.
Getting these errors:

this keeps on repeating even though it tries to find the repos.

This is the failure.

there is nothing more in the logs then the uploaded information. Looking forward to have a fix so that can migrate asap.

After reboot and running the script again I am on ROCKY linux. CHeers!!!!

Cool, sounds like yo had a networking issue.

glad it worked out!


Not close the Dropdown menu content when Item, Checkbox, Radio is clicked in it.

Feature request
I think this is a feature request unless I'm somehow missing how to handle this.
Overview
I'd like if dropdown menu content doesn't close when dropdown menu item is clicked in it. I've tried event.stopPropogation() onClick on dropdown menu item but that didn't help.
Who does this impact? Who is this for?
This behaviour would be expected if using Checkboxes in the dropdown as multiple checkboxes can be selected at once and if dropdown menu content closes on every selection, it's not a great user experience.
Additional context
codesandbox: https://codesandbox.io/p/sandbox/peaceful-hertz-sqxlr5

Useevent.preventDefault() in onSelect.

@imri29 Thanks for the answer! Didn't think of this solution before 👍


[Feat]: Add TOTP support

What new feature are you looking for / expect?
https://crates.io/crates/totp-rs
Expectations
Opt-in Feature

#134


Expose firmware version as sensor

Would it be possible to have a home assistant sensor to show the firmware version of cameras? then I can write an automation to say if it needs updating. Like the Tasmota integration has.

hi,
all contributions are welcome :)


[paishare] add template examples and change job name in submission with timestamp information

add template examples change job name in submission to attach timestamp info

Coverage increased (+10.8%) to 76.132% when pulling 181deaff645e37a17edb6b6e25df72e9265961b1 on chenqi/paishare into<PHONE_NUMBER>8448602d957582304528e6fa9f745b on paishare.


Config for standard networks

Made config class and a function in network_generation for working with the standard LV networks shipped with pandapower. Added lots of options for storage being added, not yet for the load feeds. Still need to test

@bmeyers I added the option to add standard generators, changed the way dictionaries are added to (as per your suggestion), and added some documentation in the functions and methods. Let me know what you think!


[T2A3 && T2A4][W14-A3]Lee Han Cheng

Ready for review.

I think you can make it smellier than this :P


[fixed bug] callback now called after write() did it's job.

callback was called right after starting the write()-function. the correct behavior afaik should be to call a callback after a jobs has been done. i had some loading problems on a webpage with a file cache.

Looks good. Thanks for that!


[Bug]: Select breaks using older radix-vue version

Reproduction
https://stackblitz.com/edit/tpwezn
Describe the bug
Commented on #241 as the reference on when the bug might surface.
Here is the stackblitz link to repro:

Radix-vue 1.2.3 (breaks) https://stackblitz.com/edit/tpwezn
Radix-vue 1.4.0 (works) https://stackblitz.com/edit/tpwezn-zjzxqt

Not sure if this should be reported here or in the radix-vue repo.
So in SelectItem.vue (and maybe other components with similar approach), the problem is in this code
const props = defineProps<SelectItemProps & { class?: HTMLAttributes['class'] }>()

const delegatedProps = computed(() => {
  const { class: _, ...delegated } = props

  return delegated
})

const forwardedProps = useForwardProps(delegatedProps)
console.log('f', forwardedProps)

If I'm using radix-vue version 1.2.3 to 1.3.2, this breaks as the type of forwardedProps become CustomRefImpl when I console.log it, and the value of it becomes an object like this:
value: {
    "value": "pineapple",
    "disabled": false,
    "asChild": false
}

To get around this, I tested two solutions:

Upgrade radix-vue to 1.4.0, then the type of forwardedProps become the expected ComputedRefImpl and the value is the expected string value, which is "pineapple" in the above example. But in radix-vue changelog, it said that v1.3.0 required vue 3.4 (not sure if it's just for the treeshaking feature, I tested radix-vue 1.4.0 in this vue 3.3.8 app and it seemed to still work fine, haven't tested the whole app)

Stay in radix-vue 1.2.3 up to 1.3.2, remove the delegatedProps stuff, and directly use the props to pass to v-bind in SelectItem component, not sure if this is a good workaround.

Also, whenever i add a component using npx shadcn-vue@latest add select, it prompts me to upgrade the shadcn-vue version, but IIRC the radix-vue package is installed only during npx shadcn-vue@latest init. So if there are changes that require updates to radix-vue like this one, do I have to manually install the updated radix-vue or can it be automated in some way?
System Info
System:
    OS: macOS 13.3.1
    CPU: (8) arm64 Apple M1
    Memory: 50.83 MB / 8.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 18.17.1 - ~/.nvm/versions/node/v18.17.1/bin/node
    Yarn: 1.22.15 - ~/.nvm/versions/node/v18.17.1/bin/yarn
    npm: 9.6.7 - ~/.nvm/versions/node/v18.17.1/bin/npm
    pnpm: 6.11.0 - ~/.nvm/versions/node/v18.17.1/bin/pnpm
    bun: 1.0.7 - ~/.bun/bin/bun
  Browsers:
    Chrome: 121.0.6167.160
    Safari: 16.4
  npmPackages:
    @vueuse/core: ^10.1.2 => 10.4.1
    radix-vue: ^1.3.2 => 1.3.2
    vue: ^3.2.47 => 3.3.4

Contributes

[ ] I am willing to submit a PR to fix this issue
[ ] I am willing to submit a PR with failing tests

@hendrasan Hey there
Is there any reason not to update radix-vue?

Radix-vue 1.4.0 (works)

Related PR in radix-vue https://github.com/radix-vue/radix-vue/pull/628

Is there any reason not to update radix-vue and also vue?

Haven't checked the 3.4 upgrade guide yet, but just cautious of any breaking changes.
For my issue, I guess I can either update radix-vue to 1.4.0 (and ideally vue 3.4) and use the updated code with useForwardProps or stay in 1.2.3 and just to use props, since SelectItem is/was not using the const { class: className, ...rest } = useAttrs() or destructuring the props, it should be fine to just use props I guess, maybe use the delegatedProps to fix the duplicated class issue.
But for things like this, I wonder if there should be information about this in the docs. Since people (including me) might not update the radix-vue package all the time, but if the npx shadcn-vue@latest add <component> keeps using the latest code (which requires latest radix-vue, then it might be confusing when it works in shadcn-vue website but not on their app.


SCP-1897: STM-based version of process contract outboxes

Changes

Add a new, STM-based implementation of ProcessContractOutboxes to Plutus.PAB.Core.ContractInstance
Move the polling-related parts of ProcessContractOutboxes to Plutus.PAB.Core.ContractInstance.Polling
Add STM-based request handlers for waiting effects such as AwaitSlot and NextTxAt

Long-term plan for the PAB

Completely replace the old polling-based contract runner with the STM-based one
Replace eventful with a "normal" database lib. (maybe beam)
Port some of the types of the STM-based contract runner to the emulator in plutus-contract, so that the emulator actually emulates the PAB and not "a system very much like the PAB".

In the interest of splitting up the work into smaller pieces, I'm tempted to delete all of the old stuff without immediately replacing it with something new. The old contract runner just exist for the unit tests. So the unit tests don't actually give us any assurance about the system. And we specifically don't need persistence for the upcoming demo.

Pre-submit checklist:

Branch

[ ] Commit sequence broadly makes sense
[ ] Key commits have useful messages
[ ] Relevant tickets are mentioned in commit messages

PR

[ ] Self-reviewed the diff
[ ] Useful pull request description
[ ] Reviewer requested

If you updated any cabal files or added Haskell packages:

[ ] nix-shell shell.nix --run updateMaterialized to update the materialized Nix files
[ ] Update hie-*.yaml files if needed

If you changed any Haskell files:

[ ] nix-shell shell.nix --run fix-stylish-haskell to fix any formatting issues

If you changed any Purescript files:

[ ] nix-shell shell.nix --run fix-purty to fix any formatting issues

Pre-merge checklist:

[ ] Someone approved it
[ ] Commits have useful messages
[ ] Review clarifications made it into the code
[ ] History is moderately tidy; or going to squash-merge

Fixes SCP-1959

I would also like to know if this implementation is faster than the old one. It's probably a lot snappier (no timeouts), but I would expect that the TPS will converge to a fairly similar value for polling vs STM (because we already batched events in the old implementation, I think). If that is not the case I would like to understand why it is faster, if you have the time.

Seems like all I do these days is writing simulators. But this one actually feels quite nice to use.

At +3,653 −2,866  it's frankly impossible to me to review this adequately ;/


[BUG] Color issue

Hi! I think there is a bug in Chaos Color for Gold/XP/CSPM, I set up the color green but won't show up

Please use bug reporting template.
Also, looks like a case of delete ingame.json


Compile SwifteriOS with "Allow app extension API only" checked

Add a helper category on UIApplication to get the sharedApplication that returns nil inside an app extension.

Awesome, thanks!
Any chance you can write this in swift?

I'm not sure how exactly I'd go about it in Swift (pretty sure it'll get messy, though).

This is too old and no longer relevant, closing this now.


Moves to using BaggagePropagation internally

This makes 3.x only configure BaggagePropagation
ExtraFieldPropagation was never intended for end-user code (neither is baggage field), but the ExtraFieldPropagation apis internally forward to the new stuff.
There will be a bunch of doc work to do later, but I think this unblocks Monday.

sometimes before 3.0 final we owe a new doc, which is how not to use the baggage apis :)
basically users should always shield themselves from interfaces like this in business code. something like..
interface MyBaggage {
  String username();
  void setUsername(String username);
}

class MyBaggage {
  @Autowired
  MyBaggage(TraceContext currentTraceContext, List<BaggageField> allConfigured) {
  // do the initialization etc.
  }

  public String username() {
    if (usernameField == null) return null;
    return usernameField.getValue(currentTraceContext.get());
  }

  public void setUsername(String username) {
    if (usernameField == null) return null;
    usernameField.updateValue(currentTraceContext.get(), username);
  }
}

At some point, we can consider making user-safe interfaces like feign for baggage.
that way they don't get stuck in our code just to access scope properties.

cc'ing a zipkin java party to have a look as I know baggage is exciting! @jeqo @anuraaga @jorgheymans @reta @shakuzen @llinder @devinsba @michaelsembwever  @zeagord @kojilin

PS the apis underneath here were epic thanks to @anuraaga who spent many hours on this design and banging out kinks in code with me. he's awesome and patient

FYI the value in looking up baggage fields as beans is somewhat limited as sometime by the time sleuth 3 is done, we'll support dynamic baggage. this proves the concept https://github.com/openzipkin/brave/pull/1142
It will still be useful initial wiring, to know which fields are remote. dynamic ones will be virtual fields embedded in one header, such as "baggage"

blocked on https://github.com/openzipkin/brave/pull/1143

Added to https://github.com/spring-cloud/spring-cloud-sleuth/wiki/Spring-Cloud-Sleuth-3.0-Migration-Guide


MJML Mac Desktop app not Downloading update

Hi,
Observed behavior:
I am not able to update the MJML app. The Download Now button does not go anywhere.
Screenshots and GIFs

MJML version:

MJML App v2.4.0
MJML v3.3.3

Thanks for your help!

I think 2.7 was discontinued, you get get all versions here:
https://github.com/mjmlio/mjml-app
On 6 Dec 2017 5:34 p.m., "Maher El Aridi"<EMAIL_ADDRESS>wrote:
Hi,
Observed behavior:
I am not able to update the MJML app. The Download Now button does not go
anywhere.
Screenshots and GIFs
[image: screenshot 2017-12-06 10 28 04]
https://user-images.githubusercontent.com/2089136/33672745-9b1c9290-da70-11e7-8076-eac7742153f7.png
MJML version:

MJML App v2.4.0
MJML v3.3.3

Thanks for your help!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/mjmlio/mjml/issues/909, or mute the thread
https://github.com/notifications/unsubscribe-auth/AKxLOEwKSD0NjO3lCb6TesLkLdbdXs1gks5s9sH8gaJpZM4Q4M6m
.

Hey, indeed as stated by @dalefish 2.7.0 was discontinued so there's no update. Just so you know for next time, mjml-app has its dedicated repo: https://github.com/mjmlio/mjml-app


How to avoid storing my GH pass as plaintext?

Isn't there a way by which I won't store my password as plaintext on my disk?
GitHub supports public keys doesn't it?

Yes, GitHub supports public keys, but this feature not implemented yet.

Looking forward to it :)

Possibly use this instead? https://github.com/defunkt/gist

It seems that GitHub API supports only basic authentification and OAuth: http://developer.github.com/v3/#authentication
We can't use OAuth because Client Secret must not be shared with everyone.


Tax function parameter plots not working with new txfunc.py results

With the change to tax function parameters being in lists of lists rather than Numpy arrays in PR #819, the plotting capabilities in parameter_plots.py to plot tax functions are broken as they assume tax function parameters are in array format.  These function should be updated to deal with lists as well as tax_func_type==mono.

Completed with PR #881.


CDB_QuantileBins.sql

The total size of array is calculated incorrectly. The current operation return a value equal to length of array minus one.
In order to correct this issue, we can to use the array length function, this function return the correct length value.
Below i show some samples using the same array for compare both functions:
SELECT CDB_QuantileBins(ARRAY[1,2,3,4,5,6,7,8,9,10,11,12], Q)
Current function:
Q = 3

Return value
5
8
12

Quantile Bin
1,2,3,4,5
6,7,8
9,10,11,12

Q = 4

Return value
4
7
9
12

Quantile Bin
1,2,3,4
5,6,7
8,9
10,11,12

Q = 5

Return value
3
5
8
10
12

Quantile Bin
1,2,3
4,5
6,7,8
9,10
11,12

Proposal function:
Q = 3

Return value
4
8
12

Quantile Bin
1,2,3,4
5,6,7,8
9,10,11,12

Q = 4

Return value
3
6
9
12

Quantile Bin
1,2,3
4,5,6
7,8,9
10,11,12

Q = 5

Return value
2
5
7
10
12

Quantile Bin
1,2
3,4,5
6,7
8,9,10
11,12

cc @ohasselblad could you take a look?

Thanks @sariogonfer! You're totally right, it needs some improvement.
Looking more closely, maybe we could be more precise with the binning by splitting the difference if N*k/p is integer. That would give us these:
Q=3: 4.5, 8.5, 12
Q=4: 3.5, 6.5, 9.5, 12
Q=5: 3, 5, 8, 10, 12
I also noticed that the function incorrectly reduces the dataset to unique values.
Moved this over to #80


Using / for division is deprecated and will be removed in Dart Sass 2.0.0

Any update on this?

What's the status here? What's stopping this PR from being merged @sampotts ?

There seem to be concerns about folks using older versions of node-sass described here https://github.com/sampotts/plyr/issues/2230#issuecomment-879841048

I'll look at the logic suggested in https://github.com/sampotts/plyr/issues/2230#issuecomment-879841048


contribute to package.json to show the deps version of current installed

I would like to show the deps version of CWD, not only the latest version
if this feature looks good to you, I would like to send a PR for it

@meganrogge  hi, what do you think about this feature?

We try to keep VS Code lean and we think the functionality you're asking for is great for a VS Code extension. Maybe you can already find one that suits you in the VS Code Marketplace. Just in case, in a few simple steps you can get started writing your own extension. See also our issue reporting guidelines.
Happy Coding!

https://marketplace.visualstudio.com/items?itemName=HomyeeKing.hover-helper
I've add this feature in this plugin, if anybody need that, you can consider to install it


Updated erusev/parsedown to 1.7

I've updated the erusev/parsedown to 1.7 which is the latest stable version. I've ran all the tests and they are all passing.
There is currently a 1.8 beta for the package, however that's not been released and is still in testing.

Thanks for that.


this project is difficult to train on custom data

train on custom data document is too simple to follow,though the file exps/example/yolox_voc/yolox_voc_s.py can be trainning,but how  the file relate with yolox_s? I saw the code,and I could not find keyword about yolox_s.
the document only support VOC,How about COCO data trainning?I hope witer can improve train on custom data skills and simplify the trainning step.Now I will give up this project.It is difficult to use!

@futureflsl Thank you for your kind suggestion. We don't have many maintainers and we are now all working on more emergent issues and potential bugs. However, a more friendly tutorial is indeed in our plan for this week.

I would also love to see some simpler training procedures for COCO and VOC datasets. Honestly, it works fine if I want to train it on original coco images, but I did not find any annotation tool which produces exactly the format you expect. For example, I tried to export datasets from CVAT or from Roboflow. Both of them just provide me with a little different form of a dataset. On the other hand, export to tensorrt and other great things are really really great. Thanks for that!

I analyzed the annotation format of COCO dataset and converted VOC data into COCO. You can refer to README.md here https://github.com/zhangming8/yolox-pytorch

train on custom data document is too simple to follow,though the file exps/example/yolox_voc/yolox_voc_s.py can be trainning,but how the file relate with yolox_s? I saw the code,and I could not find keyword about yolox_s.
the document only support VOC,How about COCO data trainning?I hope witer can improve train on custom data skills and simplify the trainning step.Now I will give up this project.It is difficult to use!

I think the def init is the part you need to change in order to choose other architecture

want to have a function that loads data. If you need to train custom data, you just need to override this function, like https://mmdetection.readthedocs.io/en/latest/tutorials/customize_dataset.html


Avoid repetition when fetching constants and symbols from c++

The goal of this PR is to reduce the repetition when fetching constants and getting symbols from c++.

For the first problem, I've added 2 trivial utility functions to fetch a top-level or nested constant
Created a shorthand syntax to invoke SymbolValue::intern from a string (yeah, copied StringView from Natalie, I didn't even know you could do that :D )

Anything else that might be worth improving here?

Neat, thanks @seven1m !

No, thank you!!


bug with cloud_init_modules example

@danielsollondon : Thanks for your contribution! The author, @rickstercdn, has been notified to review your proposed change.

@RicksterCDN - there was a bug in the docs, can you approve asap? thanks

Looks good - #sign-off


Warning! Thermo MSFileReader is not version 3.0 SP2; a crash may result from searching this .raw file

there is no mention of having a specific MSFILEReader version anywhere???

That was the warning message I got when I uploaded RAW files:
Warning! Thermo MSFileReader is not version 3.0 SP2; a crash may result from searching this .raw file

Hello,
On the main page under "System Requirements" we ask that you have Thermo MSFileReader installed, and the particular version we recommend is v3.0 SP2. We've noticed that other versions of MSFileReader can cause crashes; 3.0 SP2 seems to be the best at not crashing.
You may of course ignore the warning and still "Run all tasks" if you don't want to install that particular version of MSFileReader. That's why it's a warning and not a requirement :)

thanks couldn't see it in the wiki page. although seems to affect the calibration step.
Search and new GTPMD working fine.
during the calibration step the error message is that there is not enough MS1 and MS2.

There may not be enough high-quality PSMs in your run to calibrate with; how many target PSMs with scores of at least 10 do you observe? Is it low-res MS2 data or a very simple sample (e.g., 1 digested protein)?

it is actually a complex sample (full cell lysate) run on an Orbitrap Fusion using a topN method, files were searched with Maxquant already and wanted to compare and use morpheus to id some glycos peptides and use LFQ.

Are you able to share this data with us? I can try to identify the problem. Please email a download link to<EMAIL_ADDRESS>. Include your .toml settings for search and calibration, results.txt from your search, your spectra file(s), and database(s). Thanks!

120K on the MS1 and 30K MS2

that should be perfect. suggest searching one injection where you know protein abundance was high and open the search tolerance for both MS1 (20 ppm) and MS2 (30 or 40 ppm). We sometime see bad calibration resulting in low PSMs. This should only take a couple minutes. If still low, I suggest that you give us access to a file and let us know what organism. We'll search it and get to the bottom of the problem. Let us know, we'll set up a box drive for you to place the file.

thanks, I used the default settings (15 and 25 ppm), will try to change the settings and see. if not I appreciate your help to do the search as I would like as well to understand how to set the LFQ search to compare between 2 datasets

we're happy to help. email to<EMAIL_ADDRESS>to request the link which will provide you a place to upload your raw file if necessary

Hello,
Any update on this? were you able to calibrate your files by opening up the tolerance?

I'm going to close this issue due to inactivity; if you can, please email us or comment here to let us know how this turned out.

Hey there,
sorry for the inactivity,
the issue is still standing, I'm waiting for new experiments to be run to
re-analyze data again, will try with the complete set and see how it goes,
thanks for your assistance.
regards
On Mon, Apr 23, 2018 at 3:09 PM, rmillikin<EMAIL_ADDRESS>wrote:

I'm going to close this issue due to inactivity; if you can, please email
us or comment here to let us know how this turned out.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/smith-chem-wisc/MetaMorpheus/issues/1090#issuecomment-383569206,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AkigwWrmdanYsfl7GFl9Y_XFCDf4viFXks5trdKhgaJpZM4TRZQh
.

--
Dr. Mohamed Ali Jarboui, PhD, M.Sc, Eng.
University Hospital Tübingen.
Department of Preclinical Imaging and Radiopharmacy.
Röntgenweg 13,
72076 Tübingen.
GERMANY
Office: +49 (7071) 29-83462
Fax: +49 (7071) 29-4451
<EMAIL_ADDRESS><EMAIL_ADDRESS>http://www.isct.uni-tuebingen.de/wsic/
http://www.isct.uni-tuebingen.de/wsic/group/staff/staff-member/mohamed-ali-jarboui/


new Validating in version 4 has error in typescript

hi shahab yazdi
thanks for this great component
I receiving this error on new version, Please advise
Type '(date: any, { validatedValue, input, isTyping }: any) => void' is not assignable to type '((selectedDates: DateObject | DateObject[] | null) => false | void) & ((selectedDates: DateObject | DateObject[] | null, validatedValue: string | string[], input: HTMLElement, isTyping: boolean) => false | void)'.
  Type '(date: any, { validatedValue, input, isTyping }: any) => void' is not assignable to type '(selectedDates: DateObject | DateObject[] | null) => false | void'.ts(2322)
index.d.ts(187, 5): The expected type comes from property 'onChange' which is declared here on type 'IntrinsicAttributes & CalendarProps & DatePickerProps'

<Controller
      name={props.name!}
      control={control}
      rules={rules}
      render={({ field, fieldState: { error } }) => (
        <DatePicker
          format="YYYY٫MM٫DD"
          weekDays={["ش", "ی", "د", "س", "چ", "پ", "ج"]}
          onOpenPickNewDate={false}
          calendar={persian}
          locale={persian_fa}
          plugins={[weekends()]}
          maxDate={new DateObject({ calendar: persian }).toLastOfYear()}
          render={<MaterialInput name={props.name} label={label} error={error !== undefined} />}
          value={field.value || ""}
          onChange={(date: any, { validatedValue, input, isTyping }: any) => {
            field.onChange(date?.isValid ? date : null);
          }}
          containerStyle={{
            width: "100%",
          }}
          {...props}
        />
      )}
    />

I will work on it and let you know the result.

Any sign of hope ?

Hi @perfeshnal ,
Apologies for the delayed response.
Could you please try v4.3.3 and let me know if that resolved the issue?

Thank you Shahab
problem is solved in version 4.3.3 and it works well 👍


Sensor Data normalization

Hi! I don't understand the normalization of collected data in your project. Could you explain me how that work please?

I am not getting correct epoch time in CSV file. Could anyone help?

@pantos06 which part exactly should be explained? On mobile we draw the real data, there isn't any high pass neither lowpass filter active right now.

Sir, can't we get the data of two sensors at a time in CSV?

@nandi9 you've to adjust the source code by yourself. This project is only a skeleton to work with wearable sensors


[Bug] input rules in inlineCode should keep code.

Describe the bug
All punctuation in an inline code should be reserved.
To Reproduce
Steps to reproduce the behavior:
input `*a*`
got a bold in an inline code.
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots

Milkdown version
List the versions of milkdown packages you have here.
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [chrome]
Version [6.3]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

https://codesandbox.io/s/eager-hypatia-2hpveu?file=/src/App.js
Just input three *

Just one line code

Just one line code

Not that simple, this will break something like bold code

if you mean bold the text in code . **bold**.
it should be break

bold code
**`bold code`**

I have same problem。when I want input someting like:
the data_name should not same with data_label
in other markdown software like typora，I should input:
the `data_name` should not same with `data_label`

It will be like this:

but in milkdown it will be like this:


Agree on solution for long checklists in search filters

This is a ticket for us to discuss a solution for long checklists in search filters:
https://www.figma.com/file/TnVsWy6VobbHzZdbHdx3Rb/ILO_Page_Templates_LIVING?type=design&node-id=1247-39057&mode=design&t=6GduJxevBVuxDETo-0
Zoocha suggested that when the user clicks 'View more', the section where the full list of checkboxes is shown with a maximum height. That means that if the list of checkboxes is too long, that section needs to show a scrollbar. If we agree on this, it has to be developed in the design system.

@inesdgomes This is a fine solution, the only question is what do the scroll bars look like? They look quite different between browsers. If we need custom ones, I'd suggest something very basic like this: https://codepen.io/zachleat/pen/oNvprpX

Closing in favour of #424


Initial work to get Fargate and Fargate_spot working

Where do I begin? It was actually much easier to integrate with Fargate than I imagined, as everything was reusable, just really adding some if/else statements and ignoring EC2 instances for tasks that are Fargate.
Please review the code below, and make any changes to it that you feel are necessary to align it with your standards. I'm certainly not a developer, I know enough to get around.
A few things to note.

For Fargate Spot, you'll need to make sure you have set up capacity providers in the cluster when you build it.
When you choose Fargate in the configuration, you MUST also set an Execution Role, also in the config.
When you choose Run as spot you can ignore the pricing piece, as ECS Fargate spot doesn't let you bid for prices.
When you choose Fargate, it doesn't matter if you choose Privileged or not, the code will not try to make a Fargate container privileged to avoid a failure.
When you choose Fargate, you cannot currently add your own Mount points to the instance. I didn't have time to work through that, as SourcePath is not a valid Fargate option and we don't need to mount things in our docker agents.
If you use docker in docker to build containers, switch to Kaniko or Buildah, because you'll lose the ability to do so in Fargate
Enjoy.

Cheers,
Timothy

Wow, thanks for the work here. I'm not sure when I'll have time to validate this in depth (in practice im mainly a one-man band here at the moment), but I appreciate the effort to submit a PR.
Would appreciate any feedback from anyone else who decides to build a custom plugin off this PR and tries it out.


Scaffolding sigstore architecture

This integration will provide a method to sigstore ecosystem:
Capabilities include:

Creation of new charts

ctlog
fulcio

Split out of trillian from rekor as a new standalone chart
Umbrella chart called scaffold that enables standing up the entire sigstore architecture
Updates of chart runner

+1 on sigstore/scaffolding

Today during the sigstore community call, I asked about this. I created this to see if we can get that repo:
https://github.com/sigstore/tac/issues/5

@cpanato @vaikas @strongjz @dlorenc This should be good to go!


adds option to externally define build, module and src directories

oh yes please.  I'd love for this to be done for most of the variables that are hard cleared or hard coded at the start of the script

Guys, I want to review, and discuss, this one carefully.
Give me some time though, I am overwhelmed these days.
Note it can already be done, see comment below

by design, right now, you can edit those in 2 ways

through maali module definition, or shell variable :
re-define MAALI_ROOT_DEFAULT, MAALI_ROOT_GROUP, MAALI_ROOT_WORKST, or MAALI_ROOT_SYSTEM , see lines 69 and following; these are then used to define MAALI_ROOT , which in turn is used for MAALI_BUILD_DIR and others

through a config file, redefine MAALI_ROOT , which in turn is used for MAALI_BUILD_DIR and others

would one of these options suit you guys? these would work in the hypothesis that you're happy with MAALI_BUILD_DIR, MAALI_MODULE_DIR and MAALI_SRC being under the same parent dir (MAALI_ROOT_DIR) (edited)

Yes but if I want my build directory to be someone completely different to that of where the modules and applications go, you can't do that as it's hardcoded to use MAALI_ROOT/*.
Ideally we should be building the software on the local fs rather than on /pawsey, so for my use case I have MAALI_BUILD_DIR set to /tmp/build in the .config file.

@wdavey , let me know how urgent this is, I can deploy a new maali version when needed


Add TDT data interface

This should close #13
This needs #67 before it can be merged and has that PR as a base.
There does not seem to be additional metadata that we can extract for this recorder.
I will add a conversion example gallery in a soon to come PR.
I am wondering, the data in the gin repository seem to be LFPs, should this be an LFP data interface?
Maybe someone who knows more about this data format can weight in?
Here are the information of some of the channels form the neo headers.
array([("b'LFPs' 1", '1',<PHONE_NUMBER>2, 'int16', 'V', 1., 0., '0'),
       ("b'LFPs' 2", '2',<PHONE_NUMBER>2, 'int16', 'V', 1., 0., '0'),
       ("b'LFPs' 3", '3',<PHONE_NUMBER>2, 'int16', 'V', 1., 0., '0'),
       ("b'LFPs' 4", '4',<PHONE_NUMBER>2, 'int16', 'V', 1., 0., '0'),
       ("b'LFPs' 5", '5',<PHONE_NUMBER>2, 'int16', 'V', 1., 0., '0'),
       ("b'LFPs' 6", '6',<PHONE_NUMBER>2, 'int16', 'V', 1., 0., '0'),
       ("b'LFPs' 7", '7',<PHONE_NUMBER>2, 'int16', 'V', 1., 0., '0'),
       ("b'LFPs' 8", '8',<PHONE_NUMBER>2, 'int16', 'V', 1., 0., '0'),

@h-mayorquin is this ready for review?

@h-mayorquin Probably the easiest way to answer the LFP question would be to share an NWBFile created from this branch using the example data

@h-mayorquin Probably the easiest way to answer the LFP question would be to share an NWBFile created from this branch using the example data
@CodyCBakerPhD

Sure, I shared it.
But what would you check to see if it should be LFP? The sampling rate is above there (595.46) is there something else that you would check?

@h-mayorquin Thanks for sharing. A few items of note from that file (though not all of these belong in this PR, but can you fix in subsequent ones?)

Device name is still Device_ecephys. Can you update that to CamelCase no underscore?
Similarly for ElectricalSeries name
So, I guess our approach to the TDT is much like our approach to SpikeGLX - if 'LFP' is indeed the signal that is acquired by the device, then it is treated as the raw signal (no change needed here by default), and it is sufficient to indicate the channel name as LFP (also already taken care of here). Even though it is LFP data, it is not 'processed' from a stored raw signal so it does not belong in processing. Just taking that from our previous attitude on SpikeGLX LF channels.
There are two electrode groups created by default here - one is named 'None(Hmm, that doesn't seem good...) and the other isdefault_group. I'd say the default name for an electrode group ought to be the classic ElectrodeGroup`, and that second spurious group should not be made. I assume this can be fixed by correcting the default metadata of this interface, but maybe a follow-up PR adjusting the default names in the core write functions would be merited as well.

@h-mayorquin Thanks for sharing. A few items of note from that file (though not all of these belong in this PR, but can you fix in subsequent ones?)

Device name is still Device_ecephys. Can you update that to CamelCase no underscore?
Similarly for ElectricalSeries name
So, I guess our approach to the TDT is much like our approach to SpikeGLX - if 'LFP' is indeed the signal that is acquired by the device, then it is treated as the raw signal (no change needed here by default), and it is sufficient to indicate the channel name as LFP (also already taken care of here). Even though it is LFP data, it is not 'processed' from a stored raw signal so it does not belong in processing. Just taking that from our previous attitude on SpikeGLX LF channels.
There are two electrode groups created by default here - one is named 'None(Hmm, that doesn't seem good...) and the other isdefault_group. I'd say the default name for an electrode group ought to be the classic ElectrodeGroup`, and that second spurious group should not be made. I assume this can be fixed by correcting the default metadata of this interface, but maybe a follow-up PR adjusting the default names in the core write functions would be merited as well.

Yes, I agree with all the changes there. They should be done in a separate PR as you say though.

@h-mayorquin I'd prioritize fixing (4) since that's likely an issue then with any recording interface

@h-mayorquin And maybe fix it first, then check back to see what this interface looks like with the fixes

@h-mayorquin I'd prioritize fixing (4) since that's likely an issue then with any recording interface

Yes, I think that's the most important and I have been wanting to take a look at the add_electrodes_groups function for a while.
Please open issues for the rest if you have time to keep a registry.
I will wait for what @bendichter says about priorities though.

Replaced by #135


FIX: Removed unnecessary .bind in worker_loader.js that broke Safari

bind wasn't required, code works as expected without it as this is the event callback scope.

@pdfjsbot test

line https://github.com/digitarald/pdf.js/blob/d22885a97c62e08ee9f6f7e2c89b839054a19c3a/src/worker_loader.js#L10 must be changed as well then

clearing the event is not bad, why should it be changed?

i see
trying to test again...
@pdfjsbot test

line https://github.com/digitarald/pdf.js/blob/d22885a97c62e08ee9f6f7e2c89b839054a19c3a/src/worker_loader.js#L10 must be changed as well then

What's this on that line? Is it the worker object? Add a self variable to get around this?


General diagonal operator

As mentioned in #8 a general way to create a diagonal operator with something like diagonaloperator(b, energies) would be useful.

I have implemented the discussed function in the operators_sparse.jl file. Please review #14 and merge if everything is in order.

Yep, the last version using parametric functions is much nicer!


About text lists Godot 3.2

Hello!
The About text for SmartShape2D still lists Godot 3.2 as the supported version.
When I first scanned if this project worked with Godot 4 this lead me to believe that it did not, luckily the Readme has more information that contradicted the About text.

Done


Test: generate and inspect manifests

This PR introduces a new github test job that generates all manifests with public sources (Fedora and CentOS) and inspects them using the new 'inspect-manifests' script.
This can be moved to gitlab runners with access to internal sources once we have that set up.
I want to see how long it takes to generate manifests and inspect them instead of reusing the ones in the repository to see if we can get rid of the test manifests in the repository.  It's not a very comprehensive test, but if it's fast enough, it can catch stage schema bugs early.

Cleaned out the tools/ directory.  I wanted to continue the cleanups in a separate PR, but the koji-composer.py script was failing linting so I decided to do it now.


support building boost 1.78.0 with ndk 23

ndk 21.4 has same problems as #225 , but ndk 23 works fine.

Happy new year


zero-length bit field must be unnamed when using M_IPTR OPS without

If i don't provide this two OP functions, I get zero-length bit field must be unnamed error:
SET(type_set M_IPTR)
INIT_SET(type_init_set M_IPTR)
Is that an expected behavior? I thought there would be some kind of valid default OPS for these.

Could you give a little bit more context on the error message?
As far as I can see, you are raising a static assertion failure detected by M*LIB in C99 mode, but I don't know which one. Something like this is reported by clang/gcc/cl in similar cases:
 error: named bit-field 'M_LIB_NOT_A_DEFAULT_TYPE' has zero width
Or you can also build in C11 mode to get a more verbose error message.

I see... So the errors can be vague actually? I'm now switched to c11 mode. Will provide more info as I go. Thank you.

This is a language limitation. The list of internal errors that are detected are:

M_LIB_NOT_AN_OPLIST: something has been given (directly or indirectly) and it doesn't reduce as a proper oplist. You need to give an oplist for this definition.
M_LIB_ERROR(ARGUMENT_OF_*_OPLIST_IS_NOT_AN_OPLIST, name, oplist): sub error of the previous error one, identying the root cause. The error is in the oplist construction of the given macro. You need to give an oplist for this oplist construction.
M_LIB_MISSING_METHOD: a required operator doesn't define any method in the given oplist. You need to complete the oplist with the missing method.
M_LIB_TYPE_MISTMACH: the given oplist and the type do not match each other. You need to give the right oplist for this type.
M_LIB_NOT_A_DEFAULT_TYPE: The oplist M_DEFAULT_OPLIST (directly or indireclty) has been used with the given type, but the given type is not a default type. You need to give the right oplist for this type.


docs(plugins) Fixing filtering for enterprise plugins

Based on slack thread in #docs, mainly:

Our hub lists ACME as being bundled with Kong Enterprise https://docs.konghq.com/hub/ - but it is not in the package.

Also happens with grpc-web and grpc-gateway plugins.
Filter tweak fixes the Enterprise plugin selector. Test by clicking "Bundled with Kong Enterprise".
Preview: https://deploy-preview-2166--kongdocs.netlify.app/hub/

@lena-larionova question for you: does bundled with Kong Enterprise mean that those plugins should all have the Enterprise label in the upper right? Are some of these plugins missing that label?  Or is the filter still not ideal?

@tlblessing

does bundled with Kong Enterprise mean that those plugins should all have the Enterprise label in the upper right? Are some of these plugins missing that label? Or is the filter still not ideal? Or is this a superset?

No, Kong Enterprise has both Community and Enterprise plugins bundled with it. The plugins labelled as "Enterprise" in the corner of the tile are Enterprise-only plugins.

Could we also have an option for Enterprise only plugins?

I get where you're coming from, but I'm not sure that this makes sense from a user perspective. Think of it this way: *

Community users want to see Community plugins, and the Enterprise label is actually for them to know what they don't have access to at a glance.
Enterprise users don't care about whether a plugin is Enterprise-only or Community but bundled with Enterprise; they just want to know that they have access to the plugin.


Consistent filename case

The CLI uses a kebab-case convention, while @netlify/build uses snake_case.
Should we keep it consistent between projects? If so, which one should we use?
I personally think snake_case is more idiomatic in Node.js, but I'm fine with any case, as long as we're consistent. What do you think @erezrokah?
Note: both currently lint this using the unicorn/filename-case ESLint rule, but with different options.

Let's go with snake_case

Not a priority


[flutter_conductor] Mac beta verify_binaries_codesigned failing with wrong path

https://ci.chromium.org/ui/p/flutter/builders/prod/Mac beta verify_binaries_codesigned/335/overview
This was likely broken by https://github.com/flutter/flutter/pull/90621

will be fixed by https://flutter-review.googlesource.com/c/recipes/+/19381

Fixed by https://flutter-review.googlesource.com/c/recipes/+/19381


[Hub Generated] Review request for Microsoft.HybridCompute to add version stable/2020-08-02

This is a PR generated at OpenAPI Hub. You can view your work branch via this link.
Contribution checklist:

[ ] I commit to follow the Breaking Change Policy of “no breaking changes
[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

[ ] Ensure to check this box if one of the following scenarios meet updates in the PR, so that label “WaitForARMFeedback” will be added automatically to involve ARM API Review. Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs, all “removals” and “adding a new property” no more require ARM API review.

Adding new API(s)
Adding a new API version
Adding a new service

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If there are following updates in the PR, ensure to request an approval from API Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in stable version
[ ] Removing properties in stable version
[ ] Removing API version(s) in stable version
[ ] Updating API in stable version with Breaking Change Validation errors
[ ] Updating API(s) in preview over 1 year

Please follow the link to find more details on PR review process.

/azp run automation - sdk

/azp run automation - sdk

/azp run unifiedPipeline

The "breaking changes" that were detected are all properties and response codes that were always there, but missing from the Swagger. This update is to make the KPI alerts happy, which required these to be added.

The "breaking changes" that were detected are all properties and response codes that were always there, but missing from the Swagger. This update is to make the KPI alerts happy, which required these to be added.

Please follow the action inside the https://github.com/Azure/azure-rest-api-specs/pull/11537#issuecomment-729345228

@dkirby017  any update ?

not yet. I'll circle back on this this week. Sorry for the delay


🧑💻 :  Addition of  DocXtract

:red_circle: Title : 🧑💻 :  Addition of  DocXtract
:red_circle: Enhancement Aim : 🧑💻 :  Addition of  DocXtract
:red_circle: Changes :
🧑💻 :  Addition of  DocXtract

✅ Details to Include When Taking the Issue:
Name : Shariq
Participant Role (Specify the Open Source Program name, e.g., GSSOC, Hacktoberfest, etc.):
GSSOC Ext

Happy Contributing! 🚀
Wishing you all the best on your open source journey. Enjoy! 😎

Also assign me sir


Plan password in case of user create crud[Bug]

Bug report
Created user crud while setting up, it registers users correctly but if I add new user after logging into admin panel, it saves plane password in db and of-course it will not in login form as login form encrypt and match password in db.
??
What I expected to happen
??
What happened
??
What I've already tried to fix it
??
Is it a bug in the latest version of Backpack?
After I run composer update backpack/crud the bug... is it still there?
Backpack, Laravel, PHP, DB version
When I run php artisan backpack:version the output is:

Hey @ghulammurtaza sorry I can't help you much here without proper information.
Backpack already comes with authentication, and if you are using Backpack authentication you will have the password encrypted in the password field.
You can have a look on how we do it and implement it yourself if you are building some custom auth controller. Have a look here: https://github.com/Laravel-Backpack/CRUD/blob/aff3509476dd0f8b236912e27ed79e120a9d7eb8/src/app/Http/Controllers/Auth/RegisterController.php#L77
I am going to close this as I don't think there is any bug in Backpack in this regard.
Wish you the best 🎅


[grammar] make the EBNF grammar file pretty

This PR pretties the tins.ebnf file by following the EBNF syntax.

@tianyuxf please help review the change.


F3-229: manifest provider, ec decoupling from f3, and dynamic manifest update

Partially tackles #229
Background
In #337 I did all of the exploration for the implementation end-to-end of #229, but as the PR was growing too big, reviewing would have been quite cumbersome, and rebasing was becoming a bit of a pain, I decided to start dividing the work into smaller self-contained PRs that can (hopefully) be reviewed and merged faster.
(This will really make my life easier every time that I need to rebase :) )
Implementation
This PR:

Decoupled EcBackend  and  FakeEC  from f3 into its own independent package so it can be used for the integration tests that I was writing in #337 without circular dependencies.
Implement a ManifestProvider interface that abstracts the specific manifest implementation used under the hood. This will hopefully simplify the removal of all the passive testing-specific logic in the future.

There are two implementation of ManifestProvider: Static , which doesn't accept any runtime changes and is just a bunch of accessors to the underlying manifest, and DynamicManifest  which will be the one used to trigger configuration changes in passive testing.
To simplify the review, I haven't pushed the whole implementation of DynamicManifest, this will come in the next PR.

As suggested by Alex here, moved network-specific types out of the gpbft  protocol

Coming Next

[x] Implementation of DynamicManifest  and integration in f3 to trigger configuration rebootstraps.
[x] Implementation of ManifestSender  responsible for periodically broadcasting the current manifest used by the network.
[x]  Integration tests for f3
[x]  Implementation of configuration changes without rebootstrap.

@masih, I think I addressed all of your comments, rebased again, and fixed tests. If you could have a final look and don't have any big blocker it would be great if we could get this one merged. It is getting harder and harder to maintain this branch with every new commit as the PR is getting huge :see_no_evil:. Thanks :pray:


[FLOC-3114] Intermittent deployer test failure

Fixes FLOC-3114 - this should make the two affected tests less flaky by a) ensuring the unit we assert on is the correct unit, rather than assuming it's the only unit and b) checking that an assertion on a unit definitely happened.

Thanks.  Minor comments inline.  Please address those and merge.


Configure Azure Pipelines

This pipeline configuration builds the application and produces a build for the Release configuration.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: lhomlung sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

ok

d


exec() command doesn't print all output

exec() command doesn't print all output.
Example (myfile exists, blah does not):
at the linux prompt:
-> diff myfile blah
diff: blah: No such file or directory
at the bsh prompt:
bsh % exec("diff myfile blah");
bsh %
Reported by: jswap
Original Ticket: "beanshell/bugs/135":https://sourceforge.net/p/beanshell/bugs/135

Currently the exec() command will only print the standard output of the command that is being executed.  Standard error is ignored.
This could be changed by using ProcessBuilder to create the task and merging the output and error streams.  This would change the behaviour of an existing command, and may break existing users.

Standard error should print to `interpreter.getErr()'

I don't think the process to execute will change anything for anyone, as long as the command can execute it should be transparent.

That said as far as the diff myfile blah is concerned:
bsh % exec("diff t8.java.txt t9.java.txt");
1,6c1,11
< public class t8 {
<   public static void main(java.lang.String[] $0s) {
<     byte b1;
<     b1 = 127;
<     return;
<   }
---
> public class t9 {
>     public static void main(java.lang.String[] $0s) {
>         setStrictJava(true);
>         byte b2 = 128; //should not compile
>         byte b1 = -b2; //should not compile
>         System.out.println("b1 = "+b1+"b2 = "+b2);
>         byte b3 = 1;
>         byte b4 = -b3; //should not compile
>         System.out.println("b3 = "+b3+"b4 = "+b4);
>         return;
>     }
--> void

Works as expected, we can also make improvements at a later stage.