Updated python version matching to work with whole numbers too.

Before it would only match strings such as:
Programming Language :: Python :: 2.6

And not match strings such as:
Programming Language :: Python :: 3

Thanks for contributing!
There looks to be some mistake. The example badge, /pypi/pyversions/Django.svg, goes from 2.7, 3.2, 3.3, 3.4 to .2, .3, .4, .7.

Interesting. I'll check it again to see why it is matching wrong.

I think that may work now. Sorry that took so long.

I checked the Pypi list, and there is always a version after the Python ::
The ? was a sloppy way to only match one or zero patterns. So it would not match <IP_ADDRESS> and such. I was trying to make it explicit. So the numbers would have to be a valid version number. The ([\d\.]+) would technically work, but could match numbers such as 2....2.... Now that I think about it, a cleaner way, to get rid of the trailing ? would be to do:
var pattern = /^Programming Language \:\: Python \:\: (\d+\.?\d*)$/;

or the shorter version would be fine also:
var pattern = /^Programming Language \:\: Python \:\: ([\d\.]+)$/;

Which one would you like? Or something else?

([\d\.]+) is more future-proof. From experience, there are always surprising results that don't fit our restrictive assumptions, no matter how loose they are. i'm even tempted to suggest (v?\d\S*) but thay may be the paranoia talking.

That should work.

Thanks a lot!

With this change, my version badges make lense sense to me (e.g. 2, 2.6, 2.7) -- in other words, they contain unneeded clutter.
How about a change such that implied versions 2 and 3 are removed from the list (e.g. 2.6 implies 2, so the latter does not need to be displayed)?

@xflr6 So, if it had 2.6, it would need to check that 2 is also included, and hide it. What would it do if 2 wasn't included to show that?

It would show 2 only in case there is no 2.X in the tags.
I would consider the information whether a package owner who added 2.X or 3.X tags chose to also put in the 2 or 3 label or not relatively useless, right?

I still don't completely understand how your suggested algorithm works.
You're saying that {2, 2.4} → {2.4} and {2} → {2}, but what does {2.4} give? How do we determine whether 2 is supported?

Would be {2.4} -> {2.4}. Note that tere is no individual Python-release called 2 (only 2.X):
The 2 tag, as i understand it, more or less asserts that some 2.X version is supported (and hence looks redundant when the conrete supported 2.X-releases are also specified).

The 2 tag, as i understand it, more or less asserts that some 2.X version is supported

Do you have a link to back this up? I assumed it meant 2.0. If you're right, it makes sense to switch back.

Well, 2.0 is kind of archeological but if you look at the official list of tags here, you will see that there is both 3 and 3.0 (and 3 only).

@xflr6 You're right (and that list smells like legacy, I wonder what :: Only does).
@workhorsy No objection to a revert?

If you revert, these classifiers will be ignored:
Programming Language :: Python :: 3
Programming Language :: Python :: 2
Then we would be back to:
{2.6, 2.7, 3} -> {2.6, 2.7}
It is my understanding that the classifiers work like so:
Programming Language :: Python :: 3 - All 3.X versions (with option to add others)
Programming Language :: Python :: 3.0 - Only version 3.0 (with option to add others)
Programming Language :: Python :: 3 :: Only - All 3.X versions (with no option to add others)
I think dropping the 2/3 if there is already a 2.X/3.X would be best:
{2, 2.6, 2.7} -> {2.6, 2.7}
{3.0, 3} -> {3.0}

Because this branch is already merged, it would not show any changes. So here is a fix for this in another pull request.
https://github.com/badges/shields/pull/498


Bypassing gamerule showDeathMessages

When I have GP on, even with /gamerule showDeathMessages off the death messages will still appear but when I don't have it, it works fine.
    # Cooldown period for death messages (per player) in seconds.
    death-message-cooldown=0
    # Whether or not to monitor for spam.
    enable-spam-monitor=false

This is in the global config. enable-spam-monitor should follow everything under spam { }, but apparently the death message is not included.


How to train for RTL languages?

I'm trying to use code from this repo to train OCR for Arabic language. Additionally, the dataset has hand written text which makes it even complicated, but this is just for learning purposes.
I trained a model without any modifications to the workflow and the model architecture except for the dataset class. The model is giving me 0 WA and CA. So, I wanted to ask what possible changes we need to make the model learn?
So far, I'm trying to reverse the targets as Arabic is an RTL language unlike English. And to pad the images to the left instead of right. I'd like to hear your thoughts on this. Thanks.

Hi Nauman, sorry for the late response, but right now I don't have any ready solution for it. Maybe you can look at repos that already do Arabic OCR. I have never worked with Arabic, so I am not sure of the technical nuances that would be required to modify my code.

Hi @Deepayan137,
Thank you for your response. I've been working on my own solution for Arabic. Your repo was a help for me.


Add a JSON Path evaluator

What feature or new tool do you think should be added to DevToys?
I couldn't find a tool in DevToys, A tool that evaluates JSON Path from a Input.
Why do you think this is needed?
It would be nice to be able to enter a json path from a an input and see the result right away.
Solution/Idea
See https://jsonpath.com/

Comments
No response

This is funny, I'm currently implementing this tool here: https://github.com/veler/DevToys/pull/1017

Great minds think alike. I searched for an issue about this, but couldn't find it.


Helm chart is assuming a cluster.local domain

This is not true for our clusters
☸ this ☁  maesh [master] ag cluster.local
internal/k8s/client.go
365:        name regex ([a-zA-Z0-9-_]*)\.([a-zv0-9-_]*)\.maesh maesh-{1}-{2}.maesh.svc.cluster.local
368:    kubernetes cluster.local in-addr.arpa ip6.arpa {

integration/kubedns_test.go
31:		"exec", "-it", pod.Name, "-n", pod.Namespace, "-c", pod.Spec.Containers[0].Name, "--", "curl", "whoami.whoami.svc.cluster.local", "--max-time", "5",

integration/resources/kubedns/kubedns.yaml
122:            - --domain=cluster.local.
163:            - --server=/cluster.local/<IP_ADDRESS>#10053
195:            - --probe=kubedns,<IP_ADDRESS>:10053,kubernetes.default.svc.cluster.local,5,SRV
196:            - --probe=dnsmasq,<IP_ADDRESS>:53,kubernetes.default.svc.cluster.local,5,SRV

integration/resources/coredns/coredns.yaml
58:        kubernetes cluster.local in-addr.arpa ip6.arpa {

Hello @feisuzhu,
Is this something that you would like to be configurable?
Out of curiosity, what do you use for your clusters?

Hello @feisuzhu,
Is this something that you would like to be configurable?
Out of curiosity, what do you use for your clusters?

Something like k8s.region1.in.example.com.
We have several k8s clusters each have a different in-cluster domain and pod & service ip range, in case of possible interconnect requirements in the future.

Sounds like a valid reason.


[Quality] Split dependencies into prod and dev, handle them better in general

Current Situation

Currently, when the production Apache Airflow webserver docker image is built, it uses the same requirements.txt file as we use for development.  This has some disadvantages:

There are testing requirements included in this file, e.g., pytest
This file freezes only explicitly imported (and therefore explicitly installed) versions of dependencies, which could mean possible breakage in prod without code changes on our part

Suggested Improvement

We should use different src/cc_catalog_airflow/requirements.txt files for prod and dev.
The dev version should freeze as little as possible (to help us stay up-to-date).
The prod version should freeze everything to avoid potential breakage upon rebuilding
The prod version should not have any dev- or testing-exclusive dependencies (e.g., pytest).
We should be able to update the prod version from a known working container easily (i.e., with a script).

Benefit

Fewer opportunities to break the prod container
Smaller prod container without dev dependencies
We can let dev dependencies update more freely, without worrying that we'll create a problem for ourselves in prod.

@mathemancer can you review this please?

Clarification:  In order to make this work smoothly, the docker-compose.yml and docker-compose.override.yml files need to be modified to use the correct requirements.txt file in the correct environment.

@mathemancer I want to take this issue.

Is anyone working on this? If not I would like to work on this. @mathemancer Please point out if there are some specific things I will need to pay attendtion to while working on this (apart from the ones mentioned in the discussions above and in the linked PRs).
Thank You!

@dravadhis Go for it.  I think the main thing is to take note of the clarification above.  Thanks!

Also (I should have been more specific in the issue, sorry about that), this split can't be used in its current form without some additional work. The dev requirements are currently hard-coded. It would be better to make that an ARG and use the already split docker-compose.yml and docker-compose.override.yml to change an argument appropriately.
Please see src/cccatalog_airflow/docker-compose.yml and src/cccatalog/docker-compose.override.yml. They are both applied when one runs docker-compose up -d for the dev environment, but only the first (docker-compose.yml) is applied when we deploy in prod.

This was mentioned by you(@mathemancer) in PR 365 (here). Does this mean that we should define ARG s in the docker-compose.yml file for production and override them during development by defining another ARGs set in docker-compose.override.yml (which would happen automatically since the .override file is run only during development)?
Also should the dependencies in files under cc_catalog_airflow be considered or under the cc_catalog_airflow/dags folder?

@dravadhis  WRT the ARG question, you can just set up two different requirements files, and use a variable in the Dockerfile that takes an ARG to define which requirements file to use.
As for dependencies, you need to get the dependencies from both places, but not the venv directory.  I suggest building the image with the current setup, and using pip freeze from within the running airflow webserver container to see all the dependencies at once.

@dravadhis WRT the ARG question, you can just set up two different requirements files, and use a variable in the Dockerfile that takes an ARG to define which requirements file to use.
As for dependencies, you need to get the dependencies from both places, but not the venv directory. I suggest building the image with the current setup, and using pip freeze from within the running airflow webserver container to see all the dependencies at once.

This is about the ARG. From what I understood the thing I need to do is define an ARG in the  Dockerfile and make a corresponding arg in the docker-compose.yml file. The default value will be requirements_prod.txt.
Then the requirement_dev.txt can be passed to docker-compose with the following command during development:
REQUIREMENTS_FILE=requirements_dev.txt docker-compose up -d.

@mathemancer I managed to get a list of the dependencies using pip freeze. I removed those used for testing (the bold ones) for the prod version but I am not clear about which ones to freeze (and which ones to not).
alembic==1.4.3
apache-airflow==1.10.9
apispec==1.3.3
argcomplete==1.12.0
attrs==19.3.0
Babel==2.8.0
backcall==0.2.0
boto3==1.15.5
botocore==1.18.5
cached-property==1.5.2
cattrs==0.9.2
certifi==2020.6.20
cffi==1.14.3
chardet==3.0.4
click==7.1.2
colorama==0.4.3
colorlog==4.0.2
configparser==3.5.3
coverage==5.3
croniter==0.3.34
cryptography==3.1.1
decorator==4.4.2
defusedxml==0.6.0
dill==0.3.2
dnspython==2.0.0
docutils==0.15.2
email-validator==1.1.1
Flask==1.1.2
Flask-Admin==1.5.4
Flask-AppBuilder==2.3.4
Flask-Babel==1.0.0
Flask-Caching==1.3.3
Flask-JWT-Extended==3.24.1
Flask-Login==0.4.1
Flask-OpenID==1.2.5
Flask-SQLAlchemy==2.4.4
flask-swagger==0.2.13
Flask-WTF==0.14.3
funcsigs==1.0.2
future==0.16.0
graphviz==0.14.1
gunicorn==19.10.0
idna==2.8
importlib-metadata==2.0.0
iniconfig==1.0.1
ipython==7.18.1
ipython-genutils==0.2.0
iso8601==0.1.13
itsdangerous==1.1.0
jedi==0.17.2
Jinja2==2.10.3
jmespath==0.10.0
json-merge-patch==0.2
jsonschema==3.2.0
lazy-object-proxy==1.5.1
lockfile==0.12.2
lxml==4.4.2
Mako==1.1.3
Markdown==2.6.11
MarkupSafe==1.1.1
marshmallow==2.21.0
marshmallow-enum==1.5.1
marshmallow-sqlalchemy==0.23.1
more-itertools==8.5.0
natsort==7.0.1
numpy==1.19.2
packaging==20.4
pandas==0.25.3
parso==0.7.1
pendulum==1.4.4
pexpect==4.8.0
pickleshare==0.7.5
pluggy==0.13.1
prison==0.1.3
prompt-toolkit==3.0.7
psutil==5.7.2
psycopg2-binary==2.8.6
ptyprocess==0.6.0
py==1.9.0
pycparser==2.20
Pygments==2.7.1
PyJWT==1.7.1
pyparsing==2.4.7
pyrsistent==0.17.3
pytest==6.0.2
pytest-cov==2.10.1
pytest-mock==3.3.1
pytest-socket==0.3.5
python-daemon==2.1.2
python-dateutil==2.8.0
python-editor==1.0.4
python3-openid==3.2.0
pytz==2020.1
pytzdata==2020.1
PyYAML==5.3.1
requests==2.22.0
requests-file==1.5.1
s3transfer==0.3.3
setproctitle==1.1.10
six==1.15.0
SQLAlchemy==1.3.15
SQLAlchemy-JSONField==0.9.0
SQLAlchemy-Utils==0.36.8
tabulate==0.8.7
tenacity==4.12.0
termcolor==1.1.0
text-unidecode==1.2
thrift==0.13.0
tldextract==2.2.2
toml==0.10.1
traitlets==5.0.4
typing-extensions==<IP_ADDRESS>
tzlocal==1.5.1
unicodecsv==0.14.1
urllib3==1.25.10
wcwidth==0.2.5
Werkzeug==0.16.1
WTForms==2.2.1
zipp==3.2.0
zope.deprecation==4.4.0
Please clarify. Sorry for asking so many doubts.
Thank You!

@dravadhis I think the best thing to do would be to
0. Build using the current requirements.txt and run the tests (to make sure it's a working state).

pip freeze in the container and save the result somewhere for future inspection.
Modify requirements.txt to contain only the  "prod" requirements:

apache-airflow[aws,crypto,postgres]==1.10.9
lxml==4.4.2
python-dateutil==2.8.0
requests==2.22.0
SQLAlchemy==1.3.15
WTForms==2.2.1
docutils==0.15.2
tldextract==2.2.2

Build the docker image using only that requirements.txt -- This way, no dependencies of testing dependencies are pulled in.
pip freeze from within the container.
Compare the results with what you saved before to make sure things look reasonable.
Use all dependencies in the requirements.txt frozen from the prod dependencies, (even dependencies of dependencies).  This should make it so that everything is frozen in a working state.


chore(op): simplify blob fields in newly built block header

Simplify some no-ops, replace an Ethereum hardfork check with OP's, and remove revm-primitives as a dependency for OP payload building.

unfortunately I can't push to org branches
this has a smol conflict that must be resolved first

@mattsse No worries, I've rebased 🙏.


nccl-2.16.5-1-cuda build failure on x86_64-linux as of a9b47d85

Issue description
Build of nccl-2.16.5-1-cuda failed on x86_64-linux as of a9b47d85504bdd199e90846622c76aa0bfeabfac. This is currently breaking python3Packages.wandb.
error: builder for '/nix/store/cjlj2ig6idycrh530mhqimxzm13bwwwc-nccl-2.16.5-1-cuda-11.drv' failed with exit code 2;
       last 10 log lines:
       > nvcc error   : 'cicc' core dumped
       > make[2]: *** [/build/source/build/obj/collectives/device/Makefile.rules:719: /build/source/build/obj/collectives/device/all_reduce_prod_bf16.o] Error 139
       > make[2]: *** Waiting for unfinished jobs....
       > nvcc error   : 'cicc' died due to signal 11 (Invalid memory reference)
       > nvcc error   : 'cicc' core dumped
       > make[2]: *** [/build/source/build/obj/collectives/device/Makefile.rules:728: /build/source/build/obj/collectives/device/all_reduce_min_i8.o] Error 139
       > make[2]: Leaving directory '/build/source/src/collectives/device'
       > make[1]: *** [Makefile:57: /build/source/build/obj/collectives/device/colldevice.a] Error 2
       > make[1]: Leaving directory '/build/source/src'
       > make: *** [Makefile:25: src.build] Error 2
       For full logs, run 'nix log /nix/store/cjlj2ig6idycrh530mhqimxzm13bwwwc-nccl-2.16.5-1-cuda-11.drv'.
       note: build failure may have been caused by lack of free disk space
error (ignored): error: cannot unlink '/tmp/nix-build-cudatoolkit-11.8.0.drv-0/pkg/builds': Directory not empty
error: 1 dependencies of derivation '/nix/store/20h7iv741n6dm8xj1phqb1yfd39xywb0-python3.10-tensorflow-gpu-2.11.1.drv' failed to build
error: 1 dependencies of derivation '/nix/store/aihc1y946nzdlh1xib8zqcbqdqik9w7y-python3.10-wandb-0.15.5.drv' failed to build

full build log
python3Packages.wandb maintainers cc: @samuela
nccl-2.16.5-1-cuda maintainers cc:
Other cc: n/a
Steps to reproduce

Checkout nixpkgs at commit a9b47d85504bdd199e90846622c76aa0bfeabfac
Run nix-build -A nccl-2.16.5-1-cuda

Technical details
 - system: `"x86_64-linux"`
 - host os: `Linux 5.15.0-1041-azure, Ubuntu, 22.04.2 LTS (Jammy Jellyfish), nobuild`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.16.1`
 - nixpkgs: `/nix/store/nm1pwp6b6k958c9rvs60kdkd3dqypqqf-source`

Contents of ~/.config/nixpkgs/config.nix:
{ allowUnfree = true; cudaSupport = true; cudaCapabilities = ["8.0"]; }

Misc.
This issue was automatically generated by nixpkgs-upkeep.

CI workflow that created this issue.
Internal tags: -5420625055623502936 -1261257704240495003

Can't reproduce with
nix build --impure -L nixpkgs/a9b47d85#cudaPackages.nccl

Contents of ~/.config/nixpkgs/config.nix:
{
  allowUnfree = true;
  cudaSupport = true;
  cudaCapabilities = [ "8.0" ];
}

Build log:
https://gist.github.com/ConnorBaker/90a43c0d10f729b7decd80a0c4d155b7
If this is reproducible on your end, please re-open this!


Create Feedback-and-Conclusion

hyphenate file title & add .md

done - all that's in title field is "Feedback-and-Conclusion" - now with .md
On 9 June 2017 at 17:05, Ann-Marie Grace<EMAIL_ADDRESS>wrote:

hyphenate file title & add .md
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/OWASP/owasp-summit-2017/pull/1156#issuecomment-307414175,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Ab3mwzfvXWBH6rIp4_A8OnlirjK0YiZqks5sCV9EgaJpZM4N1a7o
.


Fixed lint error in start.go file

fixes #90
Signed-off-by: Pathagama Kuruppuge Tharindu<EMAIL_ADDRESS>

Codecov Report

Merging #138 into master will decrease coverage by 0.13%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #138      +/-   ##
==========================================
- Coverage   55.77%   55.64%   -0.14%
==========================================
  Files          41       41
  Lines        1533     1533
==========================================
- Hits          855      853       -2
- Misses        621      623       +2
  Partials       57       57

Impacted Files
Coverage Δ

cmd/probe/udevprobe.go
60.18% <0%> (-1.86%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 6d07e0d...e8dfaaa. Read the comment docs.


GitHub Link removed from search results

Describe The Bug
I think the new UI is a big step forward, however, now when I do a search for a plugin I no longer see links to GitHub or NPM. In the past this was really useful when presented with several similar plugins, as it allowed you to read about each of them, before deciding which one to go with.
Logs
No response
Config
No response
Homebridge UI Version
4.54.1
Homebridge Version
1.7
Node.js Version
20.10
Operating System
Official Homebridge Raspberry Pi Image
Environment Info

[ ] Using Docker?
[ ] Using Hyper-V?
[ ] Using hb-service?

Raspberry Pi Model
4B 4GB

Hi @davidjbradshaw
The link has moved to the information modal that can be accessed by the (i) icon - it is the plugin homepage link.


Update references from CoreCLR repo to Runtime

Update links to new unified dotnet/runtime repo

We can incorporate the additional feedback in follow up PRs.


Wrong code highlight

Environment data

VS Code version:  1.50.0
Extension version (available under the Extensions sidebar): v2020.9.114305
OS and version: OSX 10.15.7
Python version (& distribution if applicable, e.g. Anaconda): Anaconda 3.8.3
Type of virtual environment used (N/A | venv | virtualenv | conda | ...): conda
Value of the python.languageServer setting: Pylance

[NOTE: If you suspect that your issue is related to the Microsoft Python Language Server (python.languageServer: 'Microsoft'), please download our new language server Pylance from the VS Code marketplace to see if that fixes your issue]
Actual behaviour

Steps to reproduce:
[NOTE: Self-contained, minimal reproducing code samples are extremely helpful and will expedite addressing your issue]

XXX

Logs

Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)

XXX

@wangkechun, was the file in this state when you opened it? Or was this after edit?
Also, would you please navigate to the token that is incorrect and "inspect editor tokens and scopes" (from the command palette?

No file edited.
Maybe after switching git branch or switching tabs multiple times.
I can’t reproduce this problem stably now, next time I reproduce it, I will try "inspect editor tokens and scopes"

cc @judej

It looks like this problem is no longer reproducible and hasn't been updated in 30 days. I'm going to close this ticket but if you run into this issue again, please re-open.


Core Priorities/Themes for February

@rajeshkamal5050 Before I plan the priorities, can you move over any work likely to be unfinished into the issue description? That'll help me gauge bandwidth


example of multiple instances (stages)

A proper solution for #177. This is the preferred way of doing things (I have had lots of back and forth with both the serverless core engineers and collaborators - see https://github.com/serverless/components/issues/481)
@danielcondemarin One thing that I do not have is any domain in Route53. Could you please test this with any domain you have lying around.

Can you elaborate on how this would look in a normal root level project?  I am unclear if I only need to install serverless-next.js or if I need to have the serverless dependencies specifically called out in the package.json.  I tried replacing the "component: ../../" with serverless-next.js:
myFrontend:
  component: serverless-next.js
  inputs:
    bucketName: ${env.bucket}
    domain: ${env.domain}

...but just got
  myFrontend:
    appUrl:     https://d2eavu990jpclq.cloudfront.net
    bucketName: luu51mr-n1fvfgc

Can you elaborate on how this would look in a normal root level project? I am unclear if I only need to install serverless-next.js or if I need to have the serverless dependencies specifically called out in the package.json.

The example is a normal root level project. But for your purposes, you would want a package.json file that refers to serverless-next.js

@barrysteyn Thank you for looking after this 🙏 Looks great! Just a few comments I'd like to clarify first.

@barrysteyn Thank you for looking after this 🙏 Looks great! Just a few comments above I'd like your input first.

Hi Dan
So I changed the code to your suggestions. Thinking about it more, it makes sense to have the remove and deploy work the same (by passing --stage=...). One thing to point out is the README that you refer to is not really official. It is just a README provided by one of the contributors. However it was given the blessing of the Serverless author, so it's official in that sense, but it seems to me that this should not be interpreted as set in stone.
That being said, this example is rock solid in terms of creating separate instances. By passing a seconds argument to the @serverless/template component, all state (in the .serverless folder) is prefixed with that argument. And so you really do create proper instances.
The one thing I can't test is the the domains because I don't have anything in Route53.

@barrysteyn Thank you for looking after this 🙏 Looks great! Just a few comments above I'd like your input first.

Hi Dan
So I changed the code to your suggestions. Thinking about it more, it makes sense to have the remove and deploy work the same (by passing --stage=...). One thing to point out is the README that you refer to is not really official. It is just a README provided by one of the contributors. However it was given the blessing of the Serverless author, so it's official in that sense, but it seems to me that this should not be interpreted as set in stone.
That being said, this example is rock solid in terms of creating separate instances. By passing a seconds argument to the @serverless/template component, all state (in the .serverless folder) is prefixed with that argument. And so you really do create proper instances.
The one thing I can't test is the the domains because I don't have anything in Route53.

Although it doesn't feel like environment configuration is a first class citizen yet, this is a good approach as it keeps separate state files per environment which is the main thing.
I wouldn't worry much about the domains, it should work as expected. I'm happy to merge this as is, thank you very much 👍

I think it's good to merge now. One thing: I removed the STAGE env variable, and so the example page won't display anything stage specific. But that is okay since this is all about configuration, not about what get's displayed in a next page.


Clearer error message for illegal characters

I get this error from install. Admin user name is alphabetic.
GoGits · Version: <IP_ADDRESS>2 Beta

We have docs for this: http://gogs.io/docs/intro/troubleshooting.html#form-validation

Perhaps you could make the error message clearer.

True point, I'll mark this as enhancement.

+1. I ran into this issue while installing yesterday. IMO, it would be better to tell the user that they tried to use a reserved word, instead of illegal characters. For example, none of the characters in 'admin' are disallowed.
The isLegalName (https://github.com/gogits/gogs/blob/master/models/repo.go#L259)[comment] and (https://github.com/gogits/gogs/blob/master/models/repo.go#L262)[for loop] have the same 'char' versus 'word' ambiguity.
IMO, it would be even better to tell the user which word or pattern they used. For example, "'Admin' is a reserved word and is not allowed". However, that could only be done by changing the function signature of repo.IsLegalName().
I'd be happy to submit a pull request in the next day or two if the core team is open to the idea.

@roberttstephens thanks for the info!
We can fix this in minutes, but it's good to leave chance to community in such cases.
Some hints:

We start using a new pattern as shown in https://github.com/gogits/gogs/blob/develop/models/error.go
You may want to add new code in line #L10, name a new type ErrReservedWord, then store corresponding pattern as a field Pattern string.

Ping me if you have any questions!

Hi @roberttstephens , do you still have time work on this?

Hey @Unknwon . I didn't realize how many places use ErrRepoNameIllegal. Also the error handling pattern is unfamiliar to me. Therefore, I'm not sure how IsLegalName, the list of disallowed names and suffixes, and the error struct, function, and method should play together.
Maybe it's best if someone else takes this task?

@roberttstephens no worries! I can understand your concerns. Try next time :wink:

Hi @roberttstephens @martinellison , I've pushed code to develop and you can also test on https://try.gogs.io/user/sign_up . Gogs nows tells you which word is reserved or which pattern is not allowed.

Close as implemented, feel free to continue discussion! :smile:


progress bar

Hi, me again :)
Im using the demo version here: http://www.yatahonga.com/yatatest/blueimp-jQuery-File-Upload-b1e81c5/
but the progress bar only show 100% or near, thus does not reflect the actual upload progress
is there something special to configure on server side ?
Thank you

This happens for me as well, but only with very small files, so i doesn't matter since the file is uploaded within seconds anyway, have you tried uploading a bigger file?

yes i did with larger file (>1mb) and several files upload as well. Each time its 100%.
I wonder how the data.loaded is known:

is it on client side by checking the current upload ?
or server side by checking the current size of the file uploaded

if its the later one, its maybe normal as the files are usually uploaded in a tmp dir and then moved to the destination. So if the ajax call is checking the filesize in the target directory: it cannot find it (as currently uploaded in tmp dir). So by default it maybe show a fake 100% progress.

its clientside, so it only works in modern browsers, see https://github.com/blueimp/jQuery-File-Upload/wiki/Browser-support
1 MB is what I would call a small file. Try 10, or 100.
I used a 400 MB and a 3 GB file to test, both worked well with progress (In FF8).

I have limited upload speed (<20kb / sec) so 1mb should give me a progress
I'm using ff9 and the demo "off the box" but not working
can you try upload a file on the link I provided and tell me if you see the progress ?
Thank you

Works fine for me.
Windows 7 x64 -> Firefox 9.0.1

Hmm really don't get it why its not working for me...
I tried to upload a 4mo file and as soon as I click on start upload button, the progress bar shows a 100% complete upload.
However, it still uploading in background (I monitored the query with firebug).
I'm using FF 9.0.1 and XP SP3
You really see the progress bar progressing along the upload ?!

I think somehow I have similar issue as this: http://vincesamios.com/stuff/jqfileuploadprogressbar.mov
(related to issue #507 https://github.com/blueimp/jQuery-File-Upload/issues/507)
However, Im trying with file of 4mo and with limited internet connexion

Yeah that's strange.
I uploaded a video called Test.mp4 that shows the progress bar working fine.
(When it finished it said there was an internal server error but I don't know why... the file uploaded fine, and when I uploaded the video it worked fine)

yes im still working on the php script too. For the moment, the internal error is normal
i really wonder why the progress bar is not working for me. I also tried with FF8 on mac and I have same issue :/
I also tried with a different internet access and yet still same :/

Hello everybody ,
I tested the upload with the basic plugin exemple (https://github.com/blueimp/jQuery-File-Upload/wiki/Basic-plugin) and the full exemple (http://www.yatahonga.com/yatatest/blueimp-jQuery-File-Upload-b1e81c5/) . All working fine but in firefox 10 files bigger than 250 mb failed !
Tested on  (with files > 250 mb):
-Linux ubuntu 11.0.4 / Firefox 10  -> failed
-win xp sp 3 /Firefox 10 ->ok
-Win 7 /firefox 10 -> failed
For other browser working fine .
I urgently need to find a solution .
Thank all .

What error were you getting?

Hello TheAwesome ,
I have a empty data.result and php script have no error by monitoring response with firebug .

thx.

Have you checked all your php settings?
->http://www.radinks.com/upload/config.php

It is a browser bug https://bugzilla.mozilla.org/show_bug.cgi?id=678648 & https://bugzilla.mozilla.org/show_bug.cgi?id=678648

I found a solution . Use non-multipart , maxchunsize option .


feat: use insertion effects when available

At sanity we use styled-components extensively, our @sanity/ui design system is built upon it, and most of the Sanity Studio codebase is as well. We've been testing the impact of implementing useInsertionEffect and see a noticeable performance improvement both on component mounting and rerender perf when the CSS is changed and it motivated us to open a PR 🙌
The new React docs explains useInsertionEffect really well, especially the section at the end:

Using Insertion Effects in StyledComponent
The work in this implementation builds upon @alexandernanberg's work in #3821 and how Emotion implements it.
By using useInsertionEffectAlwaysWithSyncFallback from @emotion/use-insertion-effect-with-fallbacks we are able to:

React 18 and later the useInsertionEffect hook is used to write to the CSSOM.
React 17 and older will continue to emit during render, ensuring the CSSOM is updated before userland useEffect and useLayoutEffect hooks are called.

Using Insertion Effects in createGlobalStyle
I'm using useInsertionEffectWithLayoutFallback from @emotion/use-insertion-effect-with-fallbacks to ensure that Insertion Effects are used while available, otherwise Layout Effects are used like it is now.
I saw that global styles used to opt-in to Insertion Effects in the past, but it was reverted in #4101.
It seems like the React team doesn't see the behaviour as a bug, and there's ways to make global styles mounted in a suspended component (like in a React.lazy) eagerly run teardown and remove global styles:

use a startTransition to wrap events that lead to React.lazy, or general suspense
change the key of the parent Suspense boundary when you load a different React.lazy or suspending component
if changing the suspense key isn't viable then separate suspense boundaries could be used.

I forked @mdeschamps codesandbox and modified it to demonstrate how using a key prop on the outer Suspense boundary solves it (using our speedy-styled-components fork that implements this PR), it also has commented out code that uses startTransition instead of changing the key.
Testing
To run the benchmark, and tests, I've bumped react from 17 to 18.  One doesn't simply bump test dependencies 😮💨 I changed it back to 17.
There's also a forked version of styled-components on npm that you can use to test the changes in this PR in userland: "styled-components"<EMAIL_ADDRESS>

Ran the benchmark suite

Seems like there's an unfortunate performance degradation compared to current main branch

@quantizor this is for React 17 which should still be updating styles in render, right?
I'll try a few things and see what's causing it 🤔

@quantizor I've updated the implementation so it no longer has a perf regress:

The benchmark is pushed to a different branch, and pits the latest v6 release on npm, with an npm published version of the changes in this branch (currently: speedy-styled-components@6.1.14): https://github.com/sanity-io/styled-components/tree/benchmark
When running the workspace version against v6 I get strange numbers, I tried to run a baseline (branch with repro), but for some reason the workspace version always gave worse numbers than the v6 published to npm:

Ok I found a discrepancy in the benchmark code that I fixed in main and we can properly test this now

Thanks @quantizor, I merged in your changes and re-run the benchmarks. I ran each separately, multiple times so I could compare the median times and variance for each. As the benchmark is on react 17 we should see no difference since the logic for useInsertionEffect, that requires looping over the rules twice, shouldn't be used there:

To gather them up during render.
Insert them into the styleSheet in a useInsertionEffect cycle.

Mount deep

The workspace version is slightly faster with a median of 03.13 ms compared to v6's 03.18 ms. The average variances are identical (00.67 ms), indicating similar stability in performance.
Mount wide

The workspace version is slightly faster (04.14 ms vs. 04.16 ms) with a slightly lower variance (±00.28 ms vs. ±00.31 ms).
Update dynamic styles

The workspace version is faster (01.63 ms vs. 01.81 ms) with lower variance (±00.93 ms vs. ±01.06 ms).
Conclusion
The workspace version is overall faster and more stable compared to v6 in the benchmarks provided. Which is a bit surprising to me as I don't think it's actually faster. But it's probably fine as the goal in any case was to make sure it didn't regress 🤷

@quantizor I altered the benchmark to use react 18, and ReactDOM.createRoot from react-dom/client instead of ReactDOM.render, to opt-in to concurrent rendering features, and got these results:

The workspace version is consistently faster, though the differences are very small, and variance is generally comparable.

@quantizor I've made a repro that demonstrates the perf impact:
https://github.com/user-attachments/assets/008c64fe-de67-4922-85b6-14d0da893380
Before / After

@quantizor I've made a repro that demonstrates the perf impact:
concurrent-styled-components.mov
Before / After

Thank you for making this! I really appreciate your effort and persistence here and will be happy to accept the enhancement 🚀

Out of curiosity, what type of computer are you using to run this test? I'm on an M2 Macbook Air and these were my results

Baseline
current
proposed

)

If anything it seems to perform slightly worse? This is with the force rerender flag turned on.

Out of curiosity, what type of computer are you using to run this test? I'm on an M2 Macbook Air and these were my results
Baseline	current	proposed
  )
If anything it seems to perform slightly worse? This is with the force rerender flag turned on.

The original implementation was focused on racing who can render the most iterations (1 iteration is when all cells have finished animating their background color) in total, even if it's at the cost of fps.
I've updated the benchmark to be more balanced, and configurable. It's still better to render the most iterations, but without sacrificing a stable, high, framerate.
In this video (before, after) I'm running two chrome (v128) windows in split screen on a M1 Pro at a 3456x2234 resolution, connected to a charger so there's no CPU throttling, running on macOS 14.5:
https://github.com/user-attachments/assets/201fb187-e6cc-411a-a461-b0e4009b87e2
As you can see it reaches the 20th iteration twice as fast, while maintaining a stable FPS ranging 35-102 compared to 28-87 when useInsertionEffect isn't used 🙌

Quick protip @quantizor, if you want to inspect in more detail what's happening, and what the React timeline looks like when the insert CSS during render version is tipping over and is taking too long to render, and you see the large chunks of tiles flashing, vs the insert CSS with useInsertionEffect is still able to finish in time, then you can add &maxIterations=3 to the URL so it's easier to use the React profiler.
I'm building the benchmark with next build --profile so you can use the React Devtools and its profiler on the deploy: https://concurrent-styled-components.sanity.dev

Hey @quantizor, anything I can do to help land this? 😄


Deleted account code is still available

I created my first FreeCodeCamp account in the summer of 2015.  I decided to start over so I could blog through the whole process.  I went through the process of clicking on my profile picture, scrolling to the bottom of the screen and clicking on the pinkish "Delete my Free Code Camp account".
I then created a (supposedly) new FreeCodeCamp account with the same GitHub account, and started going through the HTML and CSS Waypoints, and noticed that all of the code changes had already been made.  I am assuming this is simply the old code I modified with my deleted account surfacing in my current account.
Do I need to create another GitHub account in order truly start over?

I'm assuming you don't see any completed challenges in your profile that you wouldn't expect? If not then this is expected behavior because FCC saves your solution code in localStorage. You can clear this by following this article

Hey Logan, clearing my localStorage did, in fact, resolve the issue.
Thank you for this!
Doug


update_total_depth takes too long

Hi Bryce,
I have about 50 samples, and update_total_depth.py takes too long. From my test runs, it takes about 8-10h to process each sample. I tried to modify the scripts to use multiple threads, it used too much memory, and still needs > 10 days  (my estimate). Those are because fit spline step are quite time-consuming.
Could I run each sample individually for the fit splines steps? Then I combine all fit spines together, and finish the "update_total" step?  My concerns are, do you need all samples GC/peakness information when estimating the fit splines for each single sample? If not, then I just submit 50 jobs and finish analysis within a day.
Thanks a lot.
Liuyang

Hi Liuyang,
There are a couple things you might try.  How many loci are you fitting on?  You could use to skip option to fit on a subset of loci.  You could also change the tolerance of the fit function.  You should also be able to run each sample separately.
Best,
Bryce
Sent from my iPhone

On May 28, 2020, at 9:36 PM, Liuyang Wang<EMAIL_ADDRESS>wrote:

Hi Bryce,
I have about 50 samples, and update_total_depth.py takes too long. From my test runs, it takes about 8-10h to process each sample. I tried to modify the scripts to use multiple threads, it used too much memory, and still needs > 10 days (my estimate). Those are because fit spline step are quite time-consuming.
Could I run each sample individually for the fit splines steps? Then I each fit spines together, and finish the "update_total" step? My concerns are, do you need all samples GC/peakness information when estimating the fit splines for one sample? If not, then I just submit 50 jobs and finish analysis within a day.
Thanks a lot.
Liuyang
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

Hi Liuyang, There are a couple things you might try. How many loci are you fitting on? You could use to skip option to fit on a subset of loci. You could also change the tolerance of the fit function. You should also be able to run each sample separately. Best, Bryce
…
Sent from my iPhone
On May 28, 2020, at 9:36 PM, Liuyang Wang @.***> wrote:  Hi Bryce, I have about 50 samples, and update_total_depth.py takes too long. From my test runs, it takes about 8-10h to process each sample. I tried to modify the scripts to use multiple threads, it used too much memory, and still needs > 10 days (my estimate). Those are because fit spline step are quite time-consuming. Could I run each sample individually for the fit splines steps? Then I each fit spines together, and finish the "update_total" step? My concerns are, do you need all samples GC/peakness information when estimating the fit splines for one sample? If not, then I just submit 50 jobs and finish analysis within a day. Thanks a lot. Liuyang — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or unsubscribe.

Hi Bryce,
Thanks for your quick response. For each sample, I have ~ 2 million loci. As long as fit splines estimate for each sample is independent from each other, then it is feasible to run them separately.
Liuyang

I would definitely suggest downsampling during the fitting process.  A few thousand loci is plenty at that point.  This can be achieved with the skip option.
Bryce
Sent from my iPhone

On May 29, 2020, at 2:16 AM, Liuyang Wang<EMAIL_ADDRESS>wrote:

Hi Liuyang, There are a couple things you might try. How many loci are you fitting on? You could use to skip option to fit on a subset of loci. You could also change the tolerance of the fit function. You should also be able to run each sample separately. Best, Bryce
…
Sent from my iPhone
On May 28, 2020, at 9:36 PM, Liuyang Wang @.***> wrote:  Hi Bryce, I have about 50 samples, and update_total_depth.py takes too long. From my test runs, it takes about 8-10h to process each sample. I tried to modify the scripts to use multiple threads, it used too much memory, and still needs > 10 days (my estimate). Those are because fit spline step are quite time-consuming. Could I run each sample individually for the fit splines steps? Then I each fit spines together, and finish the "update_total" step? My concerns are, do you need all samples GC/peakness information when estimating the fit splines for one sample? If not, then I just submit 50 jobs and finish analysis within a day. Thanks a lot. Liuyang — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or unsubscribe.
Hi Bryce,
Thanks for your quick response. For each sample, I have ~ 2 million loci. As long as fit splines estimate for each sample is independent from each other, then it is feasible to run them separately.
Liuyang
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.

Hi Bryce,
This make sense. I have not paid attention to this option. This will definitely save lots of execution time. Thanks a lot.
Liuyang

I would definitely suggest downsampling during the fitting process. A few thousand loci is plenty at that point. This can be achieved with the skip option. Bryce
…
Sent from my iPhone
On May 29, 2020, at 2:16 AM, Liuyang Wang @.> wrote:  Hi Liuyang, There are a couple things you might try. How many loci are you fitting on? You could use to skip option to fit on a subset of loci. You could also change the tolerance of the fit function. You should also be able to run each sample separately. Best, Bryce … Sent from my iPhone On May 28, 2020, at 9:36 PM, Liuyang Wang @.> wrote:  Hi Bryce, I have about 50 samples, and update_total_depth.py takes too long. From my test runs, it takes about 8-10h to process each sample. I tried to modify the scripts to use multiple threads, it used too much memory, and still needs > 10 days (my estimate). Those are because fit spline step are quite time-consuming. Could I run each sample individually for the fit splines steps? Then I each fit spines together, and finish the "update_total" step? My concerns are, do you need all samples GC/peakness information when estimating the fit splines for one sample? If not, then I just submit 50 jobs and finish analysis within a day. Thanks a lot. Liuyang — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or unsubscribe. Hi Bryce, Thanks for your quick response. For each sample, I have ~ 2 million loci. As long as fit splines estimate for each sample is independent from each other, then it is feasible to run them separately. Liuyang — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.


$security.createJWT: Add custom headers

I need to add a custom header to JWT. Currently only payload is possible.

Thank you for your response, although I must admit I was a bit taken aback by the tone. I'm certainly not looking to spam the issues tracker and only posted here because I believe this functionality would be beneficial for many users.
To illustrate the necessity, consider the App Store Connect API, which requires specific JWT headers, including alg and kid. Without the ability to set custom headers directly in the JWT helper, it becomes challenging—if not impossible—to properly authenticate requests to the API. This is a standard requirement for many APIs that leverage JWT, where headers are part of the expected format for security and compatibility.
Additionally, if a JWT helper is included, it would make sense to support multiple algorithms, such as ES256, which is commonly used alongside RS256 in many authentication flows today. Flexibility in header customization and algorithm support would significantly broaden the utility of the helper across different APIs and use cases.
Thank you for considering these points, and please let me know if there’s a better place for discussions like this.
Example Docs: https://developer.apple.com/documentation/appstoreconnectapi/generating-tokens-for-api-requests

@ganigeorgiev Thank you for your detailed answer. I understand your points, especially because I have also managed some open source projects myself and therefore know the demands of many developers.
I didn't think about the fact that the functions are not implemented in Pocketbase at all, but only passed through. I have already started to implement the necessary functions directly in golang and understand that it is disproportionate to add more functions here.
Thanks for your advice on the next version!


typescript error: navigate and reload are never

Description
Hi @brillout,
The type casting below leads to an import error in our project:
https://github.com/brillout/vite-plugin-ssr/blob/64f684f8e8709b1e0fb8ae06570120b4291e72be/vite-plugin-ssr/node/client/router.ts#L7-L8
An import like the below leads to "This expression is not callable. Type never has no call signatures". Typescript imports the never cast.
import { navigate } from "vite-plugin-ssr/client/router"

See https://github.com/inlang/inlang/blob/22c4bb9fa7e04365640d828930e18cc8ef15a679/source-code/website/src/pages/editor/index.page.tsx#L3
The source-code for the website and vite plugin ssr config can be found here https://github.com/inlang/inlang/tree/main/source-code/website

"vite-plugin-ssr": "0.4.115"

Can you update to the latest version and try agin?
I'll re-open if you still get the error.

The bug occurs with VPS 0.4.120.
Ups, wrong link. Development is happening on the armageddon branch. VPS is updated to the latest version 0.4.120 on armageddon.

True latest version is 0.4.140
On Sun 3. Sep 2023 at 22:52, Samuel Stroschein @.***>
wrote:

The bug occurs with VPS 0.4.120.
Ups, wrong link. Development is happening on the armageddon branch
https://github.com/inlang/inlang/tree/armageddon/source-code/website.
VPS is updated to the latest version 0.4.120 on armageddon.
—
Reply to this email directly, view it on GitHub
https://github.com/brillout/vite-plugin-ssr/issues/1106#issuecomment-1704398826,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAHVQRXC2KRTWTC6EBDZQMLXYTUX3ANCNFSM6AAAAAA4JO2BZM
.
You are receiving this because you modified the open/close state.Message
ID: @.***>


Percentile resampling speed-up without Numba

@btrotta-bom thanks for your PR to speed up the percentile resampling plugin (#1548). There is some reticence here (not sure about at the Bureau) to including Numba in the code as we do not wish to rely on it on the HPC. As such I've had a bash at getting a similar speed up without using Numba, which is this draft PR.
The method here is not as fast as the Numba approach if there are say 100 percentiles, but it is as fast (or faster) if the number of percentiles is smaller (around 20 is typical for us).
I've largely tested this with real data, and I have run out of time to write it up here today, but let me know if you are amenable to this approach and I will finish it up tomorrow. There should be some crossover with the speed up of probabilities to percentiles I imagine (#1578).
Testing:

[x] Ran tests and they passed OK
[x] Added new tests for the new feature(s)

I am not sure what the team's overall desire is regarding Numba, and it's too quiet this Friday to reach a consensus 😄
Personally I am happy to have Numba as an option and use this approach as the fall back, but we will need @tjtg and @benfitzpatrick to weigh in I imagine.
Testing
I've co-opted your test code to compare all the methods together:
from numba.np.ufunc import parallel
import numpy as np
import time
from scipy import interpolate
from numba import njit, prange
from improver.ensemble_copula_coupling.utilities import flatten_and_interpolate, concatenate_array_with_array_endpoints

input_percentile_size = 20
target_percentile_size = 20

x1 = np.sort(np.random.random(input_percentile_size))
# Construct as 3D shape for use with new method
yorig = np.sort(np.random.random_sample((1000, 1000, len(x1))), axis=1) * 2

# Add end points as expected
x1 = concatenate_array_with_array_endpoints(x1, 0, 1)
yorig = concatenate_array_with_array_endpoints(yorig, 0, 2)

# Reshape to original test shape
y1 = yorig.reshape(1000000, len(x1))
x2 = np.linspace(0, 1, target_percentile_size)
np.random.shuffle(x2)

def slow_interp(x1, y1, x2):
    ans = np.zeros((y1.shape[0], len(x2)))
    for i in range(y1.shape[0]):
        ans[i, :] = np.interp(x2, x1, y1[i, :])
    return ans

@njit(parallel=True)
def fast_interp_same_x(x: np.ndarray, xp: np.ndarray, fp: np.ndarray) -> np.ndarray:
    index = np.searchsorted(xp, x)
    result = np.empty((fp.shape[0], len(x)))
    for row in prange(fp.shape[0]):
        for i, ind in enumerate(index):
            if ind == 0:
                result[row, i] = fp[row, 0]
            elif ind == len(xp):
                result[row, i] = fp[row, -1]
            elif xp[ind] - xp[ind - 1] >= 1e-15:
                result[row, i] = fp[row, ind - 1] + (x[i] - xp[ind - 1]) / (
                    xp[ind] - xp[ind - 1]
                ) * (fp[row, ind] - fp[row, ind - 1])
            else:
                result[row, i] = fp[row, ind - 1]
    return result

t = time.time()
slow_ans = slow_interp(x1, y1, x2)
print("old time: {}".format(time.time() - t))
t = time.time()
fast_ans = fast_interp_same_x(x2, x1, y1)
print("new time: {}".format(time.time() - t))
t = time.time()
vec_ans = flatten_and_interpolate(x2, x1, yorig, max_value=2)
vec_ans.data
print("vec time: {}".format(time.time() - t))

vec_reshape = np.moveaxis(vec_ans, 0, -1)

print("same answer: {}".format((np.isclose(slow_ans, fast_ans)).all()))
print("same answer: {}".format((np.isclose(slow_ans.astype(np.float32).flatten(), vec_reshape.flatten())).all()))

which on a run using a 1000x1000x20 type size grid (so 20 source percentiles) with 20 target percentiles gives this kind of result:
old time: 3.665600061416626
new time: 0.8652346134185791
vec time: 0.3963656425476074
same answer: True
same answer: True

Which looks pretty favourable for this approach. However, running some loops in a notebook to get slightly more solid timing it is clear that the Numba approach remains the fastest by a signficant margin:
%%timeit
slow_ans = slow_interp(x1, y1, x2)
slow_ans.data
3.67 s ± 106 ms per loop (mean ± std. dev. of 7 runs, 1 loop each)

%%timeit
fast_ans = fast_interp_same_x(x2, x1, y1)
fast_ans.data
63.8 ms ± 4.46 ms per loop (mean ± std. dev. of 7 runs, 10 loops each)

%%timeit
vec_ans = flatten_and_interpolate(x2, x1, yorig, max_value=2)
vec_ans.data
393 ms ± 3.53 ms per loop (mean ± std. dev. of 7 runs, 1 loop each)

However, both approaches trounce the original.
So if you are happy @btrotta-bom to wait until the technical leads give us a steer we can decide the way forward using one or a combination of these approaches. Thanks for the comments, they were helpful and drew my attention to the very odd reshaping I was doing all over the place.

So if you are happy @btrotta-bom to wait until the technical leads give us a steer we can decide the way forward using one or a combination of these approaches.

Sounds good!

numba won this fight....


The calculation of the central point in the force-directed layout has an issue

fixed : #401 #406


Incorrect results from calling read_digital_signal when opening more than one file

Calling read_digital_signal from the first EdfReader instance is alright. However, if calling it from the following instances, it will return incorrect results. After looking at the _pyedflib.pyx, self.handle causes the problem. It has never been assigned to any value but is used in read_digital_signal. If I added
def check_open_ok(self, result):
if result == 0:
self.handle = self.hdr.handle              <---- add this line
return True
else:
raise IOError, open_errors[self.hdr.filetype]
, everything seems to work correctly. I don't know why the code still needs self.handle. If removing "cdef int handle" and change self.handle to self.hdr.handle, I think _pyedflib.pyx should work as expected. Haven't tested though.

Thank you, i changed the source code.


Add method to add comment(s) to the generated xml

Dear Eric,
Here is a pull request to add a method to be able to comment the xml generated via galaxyxml. For instance, this can be pretty useful to keep tracks on the version of galaxyxml used for the generation.
Thank you,
Kenzo

Hi @khillion,
Thanks for the contribution! Would you mind updating the test data with the new change to example.py? Running something like the following will allow travis to build successfully:
python examples/example.py | xmllint --pretty 1 - > examples/tool.xml

Hi @erasche,
No problem, it should be fixed by now.


UI  Enhancement

hey can i work on this

Hey @shivshankar9  please asssign this issue to me, also I have a pending commit #171 to your repository


Jenkins Job - Mongo data-sync

We have a requirement to create a jenkins job that could used to
trigger the data-sync.

This change addresses the following.

a) govuk-backup is the group that has the ownership of the backup
location. Hence, we are adding the deploy user to this group to
inherit the permissions.
b) The backup dumps were stored with complete permissions to the owner.
Here we are issuing write permissions to the group.
https://trello.com/c/8wzAOsrV/1314-adapt-jenkins-jobs-to-run-mongo-backup-jobs
Solo: @suthagarht

@suthagarht Hey, we've hit a problem with this on the dev vm - the govuk-puppet group doesn't exist by default. I think we need something similar to: https://github.com/alphagov/govuk-puppet/blob/2778edd41113b2dd1a0d24eaab4fc367e27e98b0/modules/govuk/manifests/deploy/setup.pp#L42 and https://github.com/alphagov/govuk-puppet/blob/2778edd41113b2dd1a0d24eaab4fc367e27e98b0/modules/govuk/manifests/deploy/setup.pp#L45


Update unpackdiskimage under bin directory

in zcc, unpackdiskimage has error,  printError "Target disk is too small for specified image."
This is for https://github.ibm.com/zvc/planning/issues/4098 again.  There is already a PR https://github.com/openmainframeproject/feilong/pull/576 days ago which updated unpackdiskimage under scripts/.  BOE1 fba disk pool did not work till tonight, so just find that it is the copy under bin takes effect.
These 2 PRs are hard to be verified because the changed code are in deployFBAImage function.  In unpackdiskimage , there are deployFBAptImage and deployFBAImage functions handling fba image.  I have tested all 5 fba images under https://ibm.ent.box.com/folder/118943194912, but none of them calls deployFBAImage. The fix are using similar methods existed in other functions already.

Close this one, create https://github.com/openmainframeproject/feilong/pull/583 instead.

Tracking by #583


Remove automatic inbounds stuff

Ref: https://github.com/JuliaSIMD/StrideArrays.jl/issues/80
This PR takes the approach of just nuking the StrideArraysCore.checkbounds function entirely. If preferred though, I can change it so that it still exists but befaults to true.
Another thing we could do to avoid making this a breaking release is we could just define a stub
function checkbounds end

so that code in other packages that try and turn boundschecks on or off continues to function

Note: I haven't yet done any sort of audit yet to see if there are functions or chunks of code which could safely be marked inbounds but currently aren't due to the default being no bounds checks.

Thanks


Now the special characters in the search value are escaped before constructing the regexp.

Description
Fixes: #3051
Contribution Checklist:

[x] The pull request only addresses one issue or adds one feature.
[x] The pull request does not introduce any breaking changes
[ ] I have added screenshots or gifs to help explain the change if applicable.
[x] I have read the contribution guidelines.
[x] Create an issue and link to the pull request.

Note: Keeping the PR small and focused helps make it easier to review and merge. If you have multiple changes you want to make, please consider submitting them as separate pull requests.
Publishing to New Package Managers
Please see here for more information.

Merged! Thanks @sanjai0py !


After the Kosmos management service is stopped and restarted, the pod information is unstable.

What happened:
The information of pods in the same namespace in the main cluster and the sub-cluster are inconsistent
What you expected to happen:
host cluster:

member1 cluster:

member2 cluster:

How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:

Kosmos version:
Others:

/assign @OrangeBao


Unassigned owner after user deletion

Describe the bug
Suppose a user is assigned to some certificate as an owner.  When the user is deleted, the user remains as the certificate owner.
To Reproduce
Steps to reproduce the behavior:
Assign some user to a certificate
Delete the user
Go to the certificate detail
See the assigned owner
Expected behavior
The expected behavior is that the user deletion should be reflected in the certificate owner attribute - "Unassigned".

Fixed by implementing handling owner association separately


Does not readily build in linux

Downloading Avalonia into "Linux Mint 19.1" with DotNet Cli and VSCode with OmiSharp installed, clone the archive, then open the archive folder or src folder...
Some projects failed to load. Appears they weren't built. Avalonia.Themes.Default/Avalonia.Themes.Default.csproj, for example.

@gdennie do you want to develop / contribute to the framework or build your own application...
if its the latter then you dont need to clone the repo... see http://avaloniaui.net/docs/quickstart
if its the former, you need to follow the instructions here...
https://github.com/AvaloniaUI/Avalonia/blob/master/Documentation/build.md


set short git connection timeout and retry

Recently I'm facing tmt to hang on the git clone being stuck.
Setting quite short timeout, e.g. GIT_HTTP_CONNECT_TIMEOUT=5 and implementing some retry mechanism should help in such situation.

For git clone, there is a function git_clone in utils.py.
  4759	def git_clone(
  4760	        url: str,
  4761	        destination: Path,
  4762	        common: Common,
  4763	        env: Optional[EnvironmentType] = None,
  4764	        shallow: bool = False,
  4765	        can_change: bool = True,
  4766	        ) -> CommandOutput:
  4767	    """
  4768	    Git clone url to destination, retry without shallow if necessary
 ...<snip>...
  4776	    Url can be modified with hardcode rules unless can_change=False is set.
  4777	    """
  4778	    depth = ['--depth=1'] if shallow else []
  4779
  4780	    if can_change:
  4781	        url = clonable_git_url(url)
  4782	    try:
  4783	        return common.run(
  4784	            Command(
  4785	                'git', 'clone',
  4786	                *depth,
  4787	                url, destination
  4788	                ), env=env)
  4789	    except RunError:
  4790	        if not shallow:
  4791	            # Do not retry if shallow was not used
  4792	            raise
  4793	        # Git server might not support shallow cloning, try again (do not modify url)
  4794	        return git_clone(url, destination, common, env, shallow=False, can_change=False)

Let's try to enhance L4783-L4788 to support retry.


Add more timing histogram and gauge metrics to the Neon extension

We now also track:

Number of PS IOs in-flight
Number of pages cached by smgr prefetch implementation
IO timing histograms for LFC reads and writes, per IO issued

Problem
There's little insight into the timing metrics of LFC, and what the prefetch state of each backend is.
This changes that, by measuring (and subsequently exposing) these data points.
Summary of changes

Extract IOHistogram as separate type, rather than a collection of fields on NeonMetrics
others, see items above.

Checklist before requesting a review

[ ] I have performed a self-review of my code.
[ ] If it is a core feature, I have added thorough tests.
[ ] Do we need to implement analytics? if so did you add the relevant metrics to the dashboard?
[ ] If this PR requires public announcement, mark it with /release-notes label and add several sentences in this section.

Checklist before merging

[ ] Do not forget to reformat commit message to not include the above checklist

see also https://github.com/neondatabase/neon/issues/8926


fix(README.md): update vars link path

Fix broken link pointing to playbooks' vars.yaml file.

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: alacuku
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [alacuku]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

LGTM label has been added.  Git tree hash: c83d8c77f3f411a7d622abb47773265eabc385d1

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: alacuku, FedeDP
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [FedeDP,alacuku]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Hosting the database .json files locally

Describe the solution you'd like
The library always reaches out to the Internet to get the database .json files.  This is not ideal for performance or for a program that might not have an Internet connection.
I'd like a way to host the database files on my own local machine or intranet, and specify my own base URL for the .json database files.  Perhaps it could be an optional parameter called base_url for the select_ series of methods in FinanceDatabase.  I suppose the given base URL would just integrate and override the URLs you have hard-coded in json_picker.py.
Describe alternatives you've considered
Copying the files to my local machine and manually editing json_picker.py to use it.

This is a good suggestion and I will add this later this week.

Updated the package, please upgrade to version 0.1.10 and let me know if it doesn't work properly for you.

More context, check the section below (from README):
If you wish to store the database at a different location (for example your own Fork) you can do so with the variable
base_url which you can find in each of the above 'select' functions. An example would be:

select_funds(category='Africa Equity', base_url=<YOUR URL>)

You can also store the database locally and point to your local location with the variable base_url and by setting
use_local_location to True. An example would be:

select_etfs(category='Bank Loan, base_url=C:/Users/jerbo/FinanceDatabase/Database/ETFs/, use_local_location=True)


Bump crossbeam-utils

crossbeam-epoch was using a yanked version of crossbeam-utils, updated to latest released version

Could you explain why this is necessary? The "0.8.5" requirement means "^0.8.5" requirement and cargo does not select a yanked version when generating lockfile or updating versions. Also, if we do this, we should do the same for other yanked versions.

Could you explain why this is necessary? The "0.8.5" requirement means "^0.8.5" requirement and cargo does not select a yanked version when generating lockfile or updating versions. Also, if we do this, we should do the same for other yanked versions.

No this one's on me, was checking a lib with cargo deny and the lockfile remained unupdated on some version fixing, thanks for responding


viewerTransform

@NicoKiaru
What again is exactly the viewerTransform?
Is it from physical space to pixels on the screen?

From ViewerState:
       /**
	 * Transformation set by the interactive viewer. Transforms from global
	 * coordinate system to viewer coordinate system.
	 */
	private final AffineTransform3D viewerTransform;

So, I would say yes, from physical space to pixels. Does that work ?

I did some more tests yesterday and it looks like this indeed.


Add Lorem to Persian (fa_IR) language.

I've added Lorem.php to Persian (fa_IR) language.

Lorem is Locale invariable. Look for the Text provider for localized text.

I understand Lorem is invariable, but for Persian language which has different alphabet than Latin, it needs to be random words of Persian language, otherwise it would be useless.

It's a long time since this was posted but I think it needs to re-open.
As @nimahejazi said English Lorem is completely different from Persian (characters, direction, typography..) and using it is pointless!


Added pip support.

@cwhgn ,
https://github.com/tinyvision/DAMO-YOLO/issues/66

If you don't want to make big changes, I can create it as a personal repo(damo-yolo-pip).

I have noticed the configs of models in ./configs are deleted, what's that for?

I made the file name configs but got an error. So I did damo_configs. Can you check?


[stable/cert-manager] install fails on kubernetes v1.17.0

Version of Helm and Kubernetes:
helm: v2.16.1
kubernetes: v1.17.0
Which chart:
stable/cert-manager
What happened:
helm install stable/cert-manager --name cert-manager --namespace kube-system --version v0.6.0 --set createCustomResource=true
Error: validation failed: unable to recognize "": no matches for kind "Deployment" in version "apps/v1beta1"
What you expected to happen:
Installation without errors
How to reproduce it (as minimally and precisely as possible):
create a kubernetes cluster version v1.17.0
Anything else we need to know:
kubectl proxy
Starting to serve on <IP_ADDRESS>:8001
curl -s localhost:8001/ | grep "apps"
"/apis/apps",
"/apis/apps/v1",
From my point of view, v1beta1 was removed but
helm fetch --untar stable/cert-manager
grep -Rn 'apps/v1beta1'  cert-manager
cert-manager/webhook/templates/deployment.yaml:1:apiVersion: apps/v1beta1
cert-manager/charts/webhook/templates/deployment.yaml:1:apiVersion: apps/v1beta1
cert-manager/templates/deployment.yaml:1:apiVersion: apps/v1beta1

encountered the issue as well


restruct zap logger for CNI

Reason for Change:

This PR is to restruct zap logger for CNI and extend to easily create child zap loggers in other folders to define zap logger
Issue Fixed:

Requirements:

[ ] uses conventional commit messages

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

Notes:

Will this break the logging for store module currently ?


How to increase performance when combined with ListView

Hi im using react-native-router-flux and ListView. My code is something like this
render() {
	return (
		<SideMenu
			menu={<Sidebar />}
			isOpen={this.props.drawerOpen}
			onChange={this.handleOnChange.bind(this)}
		>
			<ReduxRouter scenes={scenes} />
		</SideMenu>
	);
}

inside my ReduxRouter i have scenes like this.
const scenes = (
	<Scene key='root'>
		<Scene key='main' component={MainComponent} hideNavBar />
	</Scene>
)

inside my MainComponent i have one ListView with 10 rows at initial and additional 5 rows after reach the bottom part.
But after loaded 20++ rows my app appeared to have jitter when i was trying to open my side menu.
What should i do to increase the performance?
Thanks

It could because of various reasons. For instance, you may perform some complex computations at the moment side menu is opening or smth like that. It's very hard for me to debug performance remotely, so I'd recommend to start with a built-in profiler, mb start debugging in Chrome just to check which functions takes most of JS thread time.
P.S. I never worked with react-native-router-flux and therefore can't really tell much about its performance or compatibility with side menu. Although, if you find a bug in side menu component that makes it slow (for some reason), I'll be happy to help fixing it.
P.P.S. Probably, StackOverflow would be a better place to ask this kind of questions.
Best of luck!

@sitompul any news about this?

@rochapablo im changing my routing method and my drawer approach using this
https://reactnavigation.org/docs/navigators/stack
https://reactnavigation.org/docs/navigators/drawer

@sitompul Thank you, maybe I change.
I figure out a way to use react-native-router-flux:
class App extends Component {
  constructor() {
    super()
    this.state = {
      isOpen: false
    }
    this.toggleSideMenu = this.toggleSideMenu.bind(this)
    this.closeSideMenu = this.closeSideMenu.bind(this)
  }

  onSideMenuChange(isOpen) {
    this.setState({
      isOpen: isOpen
    })
  }

  toggleSideMenu() {
    this.setState({
      isOpen: !this.state.isOpen
    })
  }

  closeSideMenu() {
    this.setState({
      isOpen: false
    })
  }

  render() {
    const menu = <Menu navigator={navigator} toggleSideMenu={this.toggleSideMenu} />;
    return (
      <SideMenu menu={menu} disableGestures={true} isOpen={this.state.isOpen}>
        <Router>
          <Scene key="main" hideNavBar={true}>
            <Scene key="login" component={Login} title="Login" onEnter={this.closeSideMenu} />
            <Scene key="chat" component={Chat} title="Chat" toggleSideMenu={this.toggleSideMenu} />
          </Scene>
        </Router>
      </SideMenu>
    );
  }
}

It's working, still I'm not sure if I'm doing in the right way.
Again, thank you.

@rochapablo be careful if you will use a long row ListView inside your Scene component. Because it will slow your performance.

@sitompul hi, did you find any way to solve the trouble?
i've tried with both FlatList and Listview, both brings out bad performance with side menu.
Any better side menu to work with Flatlist?

@Tom29 what kind of routing library do you use?
I managed my situation by changing my code to use sidemenu provided by reactnavigation


Expression type SegmentioOptions is ambiguous without more context

Report

The more information you provide, the faster we can help you.

When building the example project, I receive a compile error on line 95 of ExampleViewController.swift.
⚠ Select what you want report a bug*
Report a bug
What did you do?

Tried to build the examples repository

What did you expect to happen?

Compile

What happened instead?

Received an error in the ExampleViewController.swift on line 95. Expression type type SegmentioOptions is ambiguous without more context.

Your Environment

Version of the component: Most recent
Swift version: 3
iOS version: 10
Device: Simulators
Xcode version: 8

Project that demonstrates the bug
Examples in the current github project

try this branch
https://github.com/Yalantis/Segmentio/tree/issues_fixes

Thank you!

Thank you!

Any idea how to fix it within SegmentioBuilder.swift itself? Having difficulties integrating the file into my own project without getting the ambiguity error.

Isn't it fixed in the latest version?

@serejahh with the latest version pod 'Segmentio', '~> 2.1' i've managed to make it work though.

Sounds great 👍

I'm having this issue even when using the latest version of the pod.

Hi @bryanbartow! Could you provide a demo project all describe more details?

@serejahh My fault. I didn't realize there were more parameters to pass into the initializer now. Once I passed them in it works fine. Sorry for the false alarm.


kots app ls command

$ kubectl kots app ls -n default
SLUG            STATUS
app1            ready
app2            missing

I don't really like the kubectl kots app ls syntax. This feels like a Docker-style CLI, but it's in Kubernetes. The Kubernetes convention for CLIs is verb-noun, not noun-verb.
How about making this kubectl kots get apps to list the apps, then we could have a describe app and other verbs that are commonly used in built-in kubectl commands, lowering the learning curve?


Disable AMQP LinkAttachDetachMultipleOneSession test until it has been investigated.

Follow-up: https://github.com/Azure/azure-sdk-for-cpp/issues/5536
The goal here is to make a concerted effort to isolate the factors that are impacting the pipeline success rate here and discover if we have other unknown reliability concerns once we pause the flakiness caused by this particular test. I want to improve the noise-to-signal ratio for whenever a pipeline run fails, over the next 14-30 days. The other goal is to improve PR velocity.

This test has been causing our live and CI pipeline runs to fail quite often, causing jobs needing to be restarted and adding delays. It has a ~97% success rate and needs to be investigated further to root cause the issue as either test reliability improvement or SDK correctness. Given how frequently we run our pipelines and the number of OSes/flavors we have, we end up seeing failures almost daily:
https://dev.azure.com/azure-sdk/internal/_test/analytics?definitionId=1615&contextType=build
Otherwise, we have a 99.99% success rate for tests in the pipelines over the last 14 days.

1 test causing 19 failed test results

It is hurting our overall live test reliability, which impacts our release processes as well.
https://dev.azure.com/azure-sdk/internal/_pipeline/analytics/stageawareoutcome?definitionId=1615&contextType=build

This is the number one cause of our pipeline flakiness (~45%), with a gtest timeout build error coming in at number 2:

/azp run cpp - core

/azp run cpp - core

I provided the rationale and motivation in the PR description.

Do I read it correctly that the worst passing rate for this test is 99.98%?

Nope, it's 97%, you can look at the screenshot which lists the 19 failures out of 721. It fails at least once a day, if not more.

It has a ~97% success rate and needs to be investigated further to root cause the issue as either test reliability improvement or SDK correctness.

If so, shouldn't we actually investigate the test, or, the very least, run it in a loop with several retries, instead of disabling it right away?

Yes, we should investigate. That's why we have an existing issue for it to investigate. While that's on-going and being prioritized, I will re-state the answers to your question from the PR description. The test is quite complex and it isn't clear retries is the solution because there could be an underlying product issue (which running in a loop would hide). That's why it requires investigation, and that will take time. Pending that effort...

The goal here is to make a concerted effort to isolate the factors that are impacting the pipeline success rate here and discover if we have other unknown reliability concerns once we pause the flakiness caused by this particular test. I want to improve the noise-to-signal ratio for whenever a pipeline run fails, over the next 14-30 days. The other goal is to improve PR velocity.

@LarryOsterman please let me know if you are OK with this change going in, as the area owner.

@LarryOsterman please let me know if you are OK with this change going in, as the area owner.

I would rather that we take the fix for this problem, rather than disabling the test.

Sounds good, will wait for your test update. If you need me to revive this PR, to get more time, let me know.


Dynamically set object-property of Image component

Is your feature request related to a problem? Please describe.
The object-fit property of images should be set dynamically for situations where necessary
Describe the solution you'd like
<Image fit="cover" />

:tada: This issue has been resolved in version 2.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Cursor based pagination (backwards)

I noticed we have hasPreviousPage and startCursor in PageInfo, but in CursorInput, we only have limit.
In the implementation, we only call first() on SeaORM's cursor.
I was thinking, may be we also need a last bool on CursorInput?
That way we can make use of startCursor to go backwards.

Good observation. We can plan it to be added in later versions.


LRW + VoxCeleb

Hi Hang, did you combine the two dataset for training the lip-sync and test separately on each, or did you separate the training dataset - i wonder if voxceleb2 alone can achieve the good performance in terms of the lip-sync.
Thanks.

Voxceleb2 alone can already achieve good lip-sync performance. Our model is finetuned on LRW to improve the generation quality.


[Question] Support for @shopify/polaris v7*

Hi, @fourstacks
my question is related to the future of this really helpful and tiny library.
Will there be support for the next version of @shopify/polaris (v.7*) and React 17 ?
Thank you in advance.

Hi @g-costantini-it.
I set this library up to reduce boilerplate when I was working for a company building shopify apps.  I've actually recently moved on from this company and I'm pretty busy in a new role currently.  I wouldn't like to say when exactly I'll be able to get onto this (though of course I'd welcome any PRs).
I'll do my best to take a look at updating it for the latest react/polaris versions but I don't want to make any promises on times.


No installation instructions + getting started

I apologize if this is obvious to Go progammers - but how would one go about installing this on ubuntu (wsl2) with a fresh golang install?
As for getting started instructions, what is the shell command to use it?
Thanks!

Hello! Thanks for trying the package. Cloning the repo and running "go build" in the root directory should suffice for compilation. From there, I would just copy it into /usr/bin or something if you want it to be globally available. Let me know if that works for you!

The shell command to use it would be 'termdbms'. Here's a basic tl;dr; of the commands:
WASD to move around cells. Also mouse is supported.
Enter to view a cell in full screen
ESC or : to enter edit mode
[UP/K and DOWN/J] to navigate tables
[LEFT/H and RIGHT/L] to navigate columns if there are more than the screen allows.
Also to control the cursor of the text editor in edit mode
Enter in edit mode to save the contents of the cell
:s in edit mode to save a copy of the database with changes
:s! in edit mode to overwrite the original database with changes
the -h flag has the full list of commands.


Add additional parameters and support for repeated parameters

Add additional parameters:

Participation status
Delegate / Delegator
Status
Role
Members / groups
RSVP
etc.

Also adds core support for decoding and encoding repeated parameters.
and support for repeated parameters.

Codecov Report

Merging #59 (5038007) into main (3701109) will increase coverage by 0.04%.
The diff coverage is 96.00%.

@@            Coverage Diff             @@
##             main      #59      +/-   ##
==========================================
+ Coverage   96.28%   96.33%   +0.04%
==========================================
  Files          14       14
  Lines        1159     1201      +42
==========================================
+ Hits         1116     1157      +41
- Misses         43       44       +1

Impacted Files
Coverage Δ

ical/parsing/component.py
96.61% <ø> (ø)

ical/types.py
96.08% <96.00%> (+0.13%)
:arrow_up:

:mega: Codecov can now indicate which changes are the most critical in Pull Requests. Learn more


nslookup

after this nslook Im not able to go farword so please someone help who already did this

We also got struck after domain mapping (etc/hosts), Not able to access the web app. kindly help here.

Dear ManojKumarN001,

In order to provide you with the best guidance, please clarify the issues you are experiencing.
Assuming you have successfully completed all the previous steps, such as creating the deployment set, attaching the node port service, creating the ingress, and setting up the Nginx ingress controller.
the next step would be to map the Public IP obtained from the load balancer in the "/etc/hosts" file and associate it with the hostname created in the ingress.

Please refer to the following image for more clarification:

For additional information, you can watch this instructional video: https://www.youtube.com/watch?v=HGu9sgoHaJ0


Add a User Task to Your Workflow (Neo)

Tutorial URL: https://developers.sap.com/tutorials/cp-workflow-add-usertask.html
Step 1:
Fiori Launchpad (Default Site) does not find a My Inbox app, using the App finder.

Hi Hubert,
We are investigating the issue.
Regards,
Astrid

Hi Hubert,
Thanks for your feedback and please excuse the inconvenience.
Step 5 (Assign roles) from the first part of the tutorial went missing (https://developers.sap.com/tutorials/cp-workflow-getting-started.html). If you assign the roles, the apps should be visible in the launchpad.
Best regards,
Astrid


Any way to make font size smaller

Love the plug in. So nice to see line numbers in code snippet. My only ask is, is there an easy way to make the font size smaller? I am using the Obsidian Nord theme, and the font size of code blocks when using this plug in is too big — in fact, it's larger than the standard note text.

Because different themes may have different font sizes, in order to align line numbers and code blocks, I used font-size: var(--editor-font-size); as the code block style, which will be based on the editor font size.
If you want to customize the font size, one of the solutions is create a new file in Settings-Appearance-CSS snippets. For example, name it nord-code-block.css, and then use higher priority to specify styles or customize some other styles. In the Obsidian Nord theme, it may be like:
pre[class*=language-] > code[class*=language-].is-loaded {
  font-size: 0.9em !important;
  line-height: 1.4em !important;
}
pre[class*=language-] {
  font-size: 0.9em!important;
  line-height: 1.4em!important;
}
.code-block-linenum-wrap {
  font-size: 0.9em!important;
  line-height: 1.4em!important;
}

Thanks, that works great.


Unable to parse 2BEG.cif

Reporting an issue with libcifpp when reading a mmCIF file downloaded from the wwPDB: 2BEG. I get the following error when trying to use DSSP on this file:
  Missing residue for atom LEU A:17 N
  Missing residue for atom LEU A:17 CA
  Missing residue for atom LEU A:17 C
  Missing residue for atom LEU A:17 O
  Missing residue for atom LEU A:17 CB
  Missing residue for atom LEU A:17 CG
  Missing residue for atom LEU A:17 CD1
  Missing residue for atom LEU A:17 CD2
  Missing residue for atom VAL A:18 N
  Missing residue for atom VAL A:18 CA
  Missing residue for atom VAL A:18 C
  Missing residue for atom VAL A:18 O
  Missing residue for atom VAL A:18 CB
  Missing residue for atom VAL A:18 CG1
  Missing residue for atom VAL A:18 CG2

This goes on complaining for every single atom in the structure (900 heavy atoms per model, it's an NMR structure). Any pointers on what the issue might be? I can read 1GGR, which also an NMR structure just fine.
This is currently blocking https://github.com/biopython/biopython/pull/3775.

Yup, confirmed. This is a bug in libcifpp. I'll try to release a fix asap.
Thanks for reporting.

I've released version 4.2.2 which should fix this particular problem. Could you please have a look and let me know if this fixes your issue?

Fixed asap indeed, thanks!


Questions about the results

Dear author, thank you very much for your work! I am surprised and very interested in your ideas.After carefully reading your paper and reproducing the code, I am puzzled by the following two points：
Firstly, why do we perform inference before every training time?

In the test function, we passed through the feature extraction network, STN, siamese, and prediction network, and returned four values for calculating AUROC，after that, we started to train, and the training process is consistent with that in the test function.I noticed that AUROC did not have an impact on subsequent training during this process. What is the purpose of doing so? Can I directly select a certain category for aggregation training without using ground truth during training? I am eager to receive your suggestions and response.
Secondly,When I train my dataset, I set it to the same structure as mvtec.I have noticed the following situation: if I provide a more accurate mask, the prediction results and heat map obtained by the model during testing are more accurate, but when my mask is not so accurate, the results obtained are far inferior to the former. Why is this happening? In my understanding, the mask is only a tool for evaluating the quality of predictio
ns and should not have an impact on training. We look forward to your reply!

During the testing phase, the results of each epoch of training are observed without making any changes to the parameters.
While visualization code is not provided in this project, you may use the code found in issue #14. It is worth noting that this code was borrowed from RIAD, and their visualization code uses a collection of masks to determine a threshold for localization across the entire dataset. If you only use one image for visualization, it is incorrect to choose the threshold based on only one ground-truth mask.
We have tried using a deeper backbone such as Res50, and it results in better performance.

Thank you! I think I understand what you said. After using deeper networks for feature extraction, such as resnet50, the final feature dimensions are 1792(concat layer1~3), which do require more memory，have you used some dimensionality reduction methods? Furthermore，I only changed the parameters of conv1x1 in Encoder and Predictor to the corresponding dimensions(the dimention of layer3), and I would like to ask if I need to change anything else

We randomly selected a subset of the 1792 channels from Res50's features. The remaining number of channels was the same as that of Res18. Despite the loss of some channels due to random selection, we found that Res50 still outperformed Res18. Thus, we did not make any changes to the code parameters. We cannot confirm the performance that would result from using all dimensions of the features. May be better.

Thank you very much for your reply! Wishing you success in your work!

f there are no other problems I close this issue.


Add screen before 'Gift QR' screen with Note, Name, Greetings

Name(Editable), Greeting(Fixed Text) and add Note(Editable) should come in a screen before QR generation screen
and remove note form QR screen

https://xd.adobe.com/view/e8259038-6a8a-4b4f-b88f-780e311438a5-bd76/screen/b0a9fb76-99fa-45cc-ac25-eb9d19235aaa/