Fix bugs where VCS/lists of dev-dependencies are poetry install/show even in --no-dev

Fixes https://github.com/sdispater/poetry/issues/599.
Pull Request Check List
This is just a reminder about the most common mistakes. Please make sure that you tick all appropriate boxes.  But please read our contribution guide at least once, it will save you unnecessary review cycles!

[ ] Added tests for changed code. (partially)
[ ] Updated documentation for changed code. (i think this changes code to match intended/documented behavior)

I added a "test that solver marks git dev-dependencies as dev".
I did not add a test that "solver marks dev-dependencies with lists of version conditions as dev".

I haven't used "lists of dependencies" in my own projects yet. (I just tried using Git dependencies today.)
tests/puzzle/test_solver.py doesn't hit either of 2 breakpoints in poetry.py if isinstance(constraint, list):.
tests/test_poetry.py test_poetry_with_multi_constraints_dependency() references directory tests/fixtures/project_with_multi_constraints_dependency and hits that above branch (but not the path with dev-dependencies). But it doesn't call solver.solve().

Where would that test go? Do I create a new directory fixture, or do I copy the general form of tests/puzzle/test_solver.py?

oops why are the tests failing? i swear it works on my machine... i think i've been living in a cozy and exclusively python 3.6 environment for too long
Do I edit VCSDependency.__init__() and put **kwargs after allows_prereleases=True? Force push?

i'm pretty sure i force pushed, why is appveyor still failing?

i'm pretty sure i force pushed, why is appveyor still failing?

It's exciting.

I did not add a test that "solver marks dev-dependencies with lists of version conditions as dev".

is that not a problem?

@jimbo1qaz No. It is included with the proper name.

Do you mean there is already a test that ensures "dependency with list of constraints" behaves properly? And what is it called? I have not tested the behavior of my change, neither manually nor by adding a unit test.

@jimbo1qaz I mean your test is included in because of the 'test_' prefix.
And it covers #599 properly.

I don't think my test (or any other test in test_solver.py) covers #599 (list of multiple version constraints), with or without dev enabled (but i could be wrong about how pendulum works). My added test covers the related Git-package issue. I need to sleep and can't discuss further.

@jimbo1qaz Good night.

Any updates?

I just ran into something that would be fixed by this (and got as far as writing my own fix). Any chance this will be merged soon?

I observe that this bug still exists, precluding dev dependencies sourced from git, which is a major pain. @sdispater  Any chance of merging the fix?

"lists of dev-dependencies" was fixed in develop by bb984807e9b1f70e143e5e68149ea501e7c62698. In fact, https://github.com/sdispater/poetry/pull/1005 was the exact same one-line change as I made, yet got merged quickly.
The changes I made to fix "VCS dependencies" are not in develop.
I rebased this branch on develop. I'm not working on Python projects at the moment, so I didn't test my rebase locally. I'm going to force-push and see if the tests pass.

Why this fix still can not be approved? We are facing this problem too

@drunkwcodes @sdispater Could you review and merge this PR ?


Improve determination-related fields

Related Issue(s): #31
Proposed Changes:

Added properties category and determination_details
Removed value administrative was removed from determination_method in favour of the new property category
Added descriptions to the allowed values for determination_method

PR Checklist:

[ ] This PR has no breaking changes.
[x] I have added my changes to the CHANGELOG
or a CHANGELOG entry is not required.

I've updated the PR to use the new property category instead of administrative. It's based on https://aggateway.org/Portals/1010/WebSite/About Us/FIELD BOUNDARY FLYER 122123.pdf?ver=2024-01-03-212959-590


Use ruamel.yaml to improve YAML line determination for JSONSchema errors

One of the most fragile parts of our current code is how we determine the line number of a problem found in the YAML. The JSON Schema validator takes a Python data structure as the input, and ValidationError objects contain path information pointing to the problematic part of the data structure, but when we use PyYAML to read the YAML the line numbers are lost. So we've got a system using regular expressions to try and follow the path to the relevant line of the YAML.
ruamel.yaml is a YAML parsing library designed to support round-trip conversion of YAML files through Python, including formatting and comments. This means that when it loads YAML, the data structure it returns still contains line and column numbers. So given the path to the problem, we can find that part of the data structure and then look up the line and column numbers. Here's an example:
import json
import jsonschema
import sys

from ruamel.yaml import YAML

yaml=YAML()
with open("obi.md") as f:
    data = yaml.load(f)

with open("registry_schema.json") as f:
    registry_schema = json.load(f)

try:
    jsonschema.validate(data, registry_schema)
    print("SUCCESS")
except jsonschema.exceptions.ValidationError as err:
    print(err.message)
    keys = list(err.path)
    if err.validator == "additionalProperties":
        m = err.message
        key = m[m.index("'")+1:m.rindex("'")] # get the added key name; this is hacky
        keys.append(key)
    if len(keys) > 1:
        subset = data
        while len(keys) > 1:
            subset = subset[keys.pop(0)] # follow the path, stopping with one key left
        pos = subset.lc.data[keys[0]] # get ruamel.yaml's line-column information
        print(f"at line {pos[0] + 1}, column {pos[1] + 1}")
    sys.exit(1)

I think this approach will be much more robust, and I hope that it won't be to hard to replace our current code.

Much better. It also handles the duplicate key validation. :-D


Grant submission creation not enforcing dollar limit client-side

I was able to create a grant requesting 1004$.

@Katee we had a bunch of client-side validation for things like grant dollar amount, can you help me figure out why that's not happening?
The bad value does get caught at .save time, but the error message there is useless.  We used to pop up an actionable error message and interrupt the submission.

"numericfilter" is a javascript function that was defined inline but was stripped out

Will be fixed by PR#65


Use lenient dependency verification for EC2 warmup builds

We run a resolveAllDependencies build to warm up the EC2 agent image.
However, sometimes the build fails with dependency verification failures,
which is not required because we just want to download all artifacts.
Example: https://builds.gradle.org/buildConfiguration/Gradle_Master_Util_WarmupEc2Agent/42994715?buildTab=log&focusLine=2&linesState=1616
The resolveAllDependencies task is injected by the baker: https://github.com/gradle/dev-infrastructure/blob/0b8b41ee845bd8b49cce1b3f86eb8754ebcbbe21/salt/ami-baker/ec2-build-vm-baker/provision_by_salt.sh#L150-L166

@lptr this resolveAllDependencies task very much looks like what you were looking for to ease the pain of upgrading the dependency verification file

@melix but this task resolves more configurations than expected - some configurations are not used in the build, but will still be resolved by this task.

There's no perfect solution in any case: either we do less and risk missing some dependencies, or we do too much and the file contains extra dependencies. Does this task also cover tasks which only resolve dependencies at execution time?

If dependency verification fails when downloading the dependencies, then that means the the build downloaded the wrong dependencies. Why would it work when we use this warmed up image for our own build? I think we shouldn't warm up the build with dependency verification set to lenient.

Does this task also cover tasks which only resolve dependencies at execution time?

I guess this task resolves ALL configurations seen by it, no matter they're used or not. This is fine as we just want to do a rough warmup to save some time.

If dependency verification fails when downloading the dependencies, then that means the the build downloaded the wrong dependencies.

It may also mean "it's downloading more dependencies than expected to be used in any GBT builds", which are correct dependencies but not approved by anyone. It's cumbersome and unnecessary to maintain such verification metadata. If it's downloading the wrong artifacts, we'll anyway know it in the future builds.

It may also mean "it's downloading more dependencies than expected to be used in any GBT builds", which are correct dependencies but not approved by anyone. It's cumbersome and unnecessary to maintain such verification metadata. If it's downloading the wrong artifacts, we'll anyway know it in the future builds.

Why do we have dependencies in our build which we don't use? Shouldn't we remove those instead? It seems like we should run a build which runs resolveAllDependencies in our CI pipeline to make sure we don't break the task.
I am not against disabling dependency verification for the warmup builds now to unblock us, though in the short-time I think we should be using dependency verification for the resolveAllDependencies task.

Yes, they should be removed, but without resolveAllDependencies in CI pipeline, they'll exist unnoticed. I'm still not sure if it's worthy to maintain these dependencies we're not going to use - but for now let's just use lenient to unblock the new AMI baking.

On May 5, 2021, at 10:04 PM, Stefan Wolf @.***> wrote:
It may also mean "it's downloading more dependencies than expected to be used in any GBT builds", which are correct dependencies but not approved by anyone. It's cumbersome and unnecessary to maintain such verification metadata. If it's downloading the wrong artifacts, we'll anyway know it in the future builds.
Why do we have dependencies in our build which we don't use? Shouldn't we remove those instead? It seems like we should run a build which runs resolveAllDependencies in our CI pipeline to make sure we don't break the task.
I am not against disabling dependency verification for the warmup builds now to unblock us, though in the short-time I think we should be using dependency verification for the resolveAllDependencies task.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub https://github.com/gradle/gradle/pull/17084#issuecomment-832714887, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADA2DK66ZDQKUT5W5UBJRRTTMFF7XANCNFSM44EVWJRQ.


working with generate react component

installing storybook in https://github.com/JedWatson/generator-react-component gets an error:
ERROR in ./.storybook/config.js
Module build failed: ReferenceError: [BABEL] /Users/max/workspace/react-component/packages/ahrefs-style-react-component/.storybook/config.js: Unknown option: direct.presets
    at Logger.error (/Users/max/workspace/react-component/packages/ahrefs-style-react-component/node_modules/babel-core/lib/transformation/file/logger.js:58:11)
    at OptionManager.mergeOptions (/Users/max/workspace/react-component/packages/ahrefs-style-react-component/node_modules/babel-core/lib/transformation/file/options/option-manager.js:126:29)
    at OptionManager.init (/Users/max/workspace/react-component/packages/ahrefs-style-react-component/node_modules/babel-core/lib/transformation/file/options/option-manager.js:216:10)
    at File.initOptions (/Users/max/workspace/react-component/packages/ahrefs-style-react-component/node_modules/babel-core/lib/transformation/file/index.js:147:75)
    at new File (/Users/max/workspace/react-component/packages/ahrefs-style-react-component/node_modules/babel-core/lib/transformation/file/index.js:137:22)
    at Pipeline.transform (/Users/max/workspace/react-component/packages/ahrefs-style-react-component/node_modules/babel-core/lib/transformation/pipeline.js:164:16)
    at transpile (/Users/max/workspace/react-component/packages/ahrefs-style-react-component/node_modules/babel-loader/lib/index.js:46:20)
    at /Users/max/workspace/react-component/packages/ahrefs-style-react-component/node_modules/babel-loader/lib/fs-cache.js:79:18
    at ReadFileContext.callback (/Users/max/workspace/react-component/packages/ahrefs-style-react-component/node_modules/babel-loader/lib/fs-cache.js:15:14)
    at FSReqWrap.readFileAfterOpen [as oncomplete] (fs.js:365:13)
 @ multi preview

anyway to work with this package?

I have the same problem. I think the problem is in this library which was updated yesterday.
https://github.com/xzyfer/sass-graph/issues/77

Apologies for the break. We've unpublished the broken version.

@maxlibin @mskec does this work with the updated version mentioned above?

@shilman I didn't get this error while using storybook. I got here by googling error message :)
Since broken version was unpublished, I am no longer getting this error in my project. I guess storybook should also work, maybe @maxlibin can confirm.

uninstall and reinstall storybook in this package, still not working,


fix: Fix the doc comment.

This change is

Codecov Report

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

@@            Coverage Diff             @@
##           master     #677      +/-   ##
==========================================
- Coverage   94.56%   94.53%   -0.03%
==========================================
  Files          81       81
  Lines        3291     3294       +3
==========================================
+ Hits         3112     3114       +2
- Misses        179      180       +1

Impacted Files
Coverage Δ

...le/cloud/spanner/internal/instance_admin_logging.h
100% <ø> (ø)
:arrow_up:

...gle/cloud/spanner/internal/range_from_pagination.h
89.58% <0%> (-2.09%)
:arrow_down:

google/cloud/spanner/value.cc
97.04% <0%> (-0.6%)
:arrow_down:

google/cloud/spanner/transaction.h
100% <0%> (ø)
:arrow_up:

google/cloud/spanner/keys.h
98.66% <0%> (+0.03%)
:arrow_up:

...loud/spanner/internal/partial_result_set_reader.cc
92.42% <0%> (+1.51%)
:arrow_up:

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 ce63810...cbebcc0. Read the comment docs.


[bn] Localized the content/bn/event-driven-architecture.md

Describe your changes
Localize the content/bn/event-driven-architecture.md into bengali
Related issue number or link (ex: resolves #issue-number)
Tracking No: #410
Checklist before opening this PR (put x in the checkboxes)

[x] This PR does not contain plagiarism

don’t copy other people’s work unless you are quoting and contributing it to them.

[x] I have signed off on all commits

signing off (ex: git commit -s) is to affirm that commits comply DCO. If you are working locally, you could add an alias to your gitconfig by running git config --global alias.ci "commit -s".

@ai-naymul  You have done a very great job  Although I have asked for some changes here. Feel free to make those changes.

Thank You let me fix those :)

Great job @ai-naymul ! Glad that you contributed to this project. I hope to see you contribute more in this project.

Thanks a lot @mitul3737 bhaiya for giving me this opportunity and ofcourse I am also Looking forward to contribute more on this 😊


Wrappers for zero-arg v8::Value::BooleanValue(), etc.?

In upstream V8 it's no longer possible to call the zero-arg (no-context) value->BooleanValue(), value->ToBoolean(), value->NumberValue(), etc. methods without getting deprecation warnings.  Time to add wrappers for them?
Strawman proposal:
inline Maybe<bool> BooleanValue(v8::Local<v8::Value> value) {
  if (value.IsEmpty()) return Maybe<bool>();
  return value->BooleanValue(v8::Isolate::GetCurrent()->GetCurrentContext());
}

Already handled for the past two years or so. Nan::To does conversion both ways.
On February 15, 2017 9:33:48 PM GMT+02:00, Ben Noordhuis<EMAIL_ADDRESS>wrote:

In upstream V8 it's no longer possible to call the zero-arg
(no-context) value->BooleanValue(), value->ToBoolean(),
value->NumberValue(), etc. methods without getting deprecation
warnings.  Time to add wrappers for them?
Strawman proposal:
inline Maybe<bool> BooleanValue(v8::Local<v8::Value> value) {
 if (value.IsEmpty()) return Maybe<bool>();
return
value->BooleanValue(v8::Isolate::GetCurrent()->GetCurrentContext());
}

--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/nodejs/nan/issues/643

Oh, right you are.  Greppability isn't great but I suppose there is no substitute for reading the documentation.  I'll close, thanks.


curl ssl hatası unsafe legacy renegotiation

gib'in işleri
aşağıdaki hatayı alan varsa
PHP Fatal error:  Uncaught Mlevent\Fatura\Exceptions\BadResponseException: cURL error 35: OpenSSL/3.0.9: error:0A000152:SSL routines::unsafe legacy renegotiation disabled (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://earsivportal.efatura.gov.tr/earsiv-services/assos-login
openssl ayarlarından unsafe legacy renegotiation'ı enable ederek çözebilirler
sudo nano /etc/ssl/openssl.cnf
Then, add the following line to the top of the file:
openssl_conf = openssl_init
Next, at the bottom of the file, add:
[openssl_init]
ssl_conf = ssl_sect
[ssl_sect]
system_default = system_default_sect
[system_default_sect]
Options = UnsafeLegacyRenegotiation

Teşekkürler.  Connection refused for URI ...  hatası da aynı sebepten; #17

openssl_conf = openssl_init

OpenSSL example configuration file.
See doc/man5/config.pod for more info.

This is mostly being used for generation of certificate requests,
but may be used for auto loading of providers
Note that you can include other files from the main configuration
file using the .include directive.
#.include filename
This definition stops the following lines choking if HOME isn't
defined.
HOME			= .
Use this in order to automatically load providers.
openssl_conf = openssl_init
Comment out the next line to ignore configuration errors
config_diagnostics = 1
Extra OBJECT IDENTIFIER info:
oid_file       = $ENV::HOME/.oid
oid_section = new_oids
To use this configuration file with the "-extfile" option of the
"openssl x509" utility, name here the section containing the
X.509v3 extensions to use:
extensions		=
(Alternatively, use a configuration file that has only
X.509v3 extensions in its main [= default] section.)
[ new_oids ]
We can add new OIDs in here for use by 'ca', 'req' and 'ts'.
Add a simple OID like this:
testoid1=<IP_ADDRESS>
Or use config file substitution like this:
testoid2=${testoid1}.5.6
Policies used by the TSA examples.
tsa_policy1 = <IP_ADDRESS>.1
tsa_policy2 = <IP_ADDRESS>.5.6
tsa_policy3 = <IP_ADDRESS>.5.7
For FIPS
Optionally include a file that is generated by the OpenSSL fipsinstall
application. This file contains configuration data required by the OpenSSL
fips provider. It contains a named section e.g. [fips_sect] which is
referenced from the [provider_sect] below.
Refer to the OpenSSL security policy for more information.
.include fipsmodule.cnf
List of providers to load
[provider_sect]
default = default_sect
The fips section name should match the section name inside the
included fipsmodule.cnf.
fips = fips_sect
If no providers are activated explicitly, the default one is activated implicitly.
See man 7 OSSL_PROVIDER-default for more details.

If you add a section explicitly activating any other provider(s), you most
probably need to explicitly activate the default provider, otherwise it
becomes unavailable in openssl.  As a consequence applications depending on
OpenSSL may not work correctly which could lead to significant system
problems including inability to remotely access the system.
[default_sect]
activate = 1
####################################################################
[ ca ]
default_ca	= CA_default		# The default ca section
####################################################################
[ CA_default ]
dir		= ./demoCA		# Where everything is kept
certs		= $dir/certs		# Where the issued certs are kept
crl_dir		= $dir/crl		# Where the issued crl are kept
database	= $dir/index.txt	# database index file.
#unique_subject	= no			# Set to 'no' to allow creation of
# several certs with same subject.
new_certs_dir	= $dir/newcerts		# default place for new certs.
certificate	= $dir/cacert.pem 	# The CA certificate
serial		= $dir/serial 		# The current serial number
crlnumber	= $dir/crlnumber	# the current crl number
# must be commented out to leave a V1 CRL
crl		= $dir/crl.pem 		# The current CRL
private_key	= $dir/private/cakey.pem # The private key
x509_extensions	= usr_cert		# The extensions to add to the cert
Comment out the following two lines for the "traditional"
(and highly broken) format.
name_opt 	= ca_default		# Subject Name options
cert_opt 	= ca_default		# Certificate field options
Extension copying option: use with caution.
copy_extensions = copy
Extensions to add to a CRL. Note: Netscape communicator chokes on V2 CRLs
so this is commented out by default to leave a V1 CRL.
crlnumber must also be commented out to leave a V1 CRL.
crl_extensions	= crl_ext
default_days	= 365			# how long to certify for
default_crl_days= 30			# how long before next CRL
default_md	= default		# use public key default MD
preserve	= no			# keep passed DN ordering
A few difference way of specifying how similar the request should look
For type CA, the listed attributes must be the same, and the optional
and supplied fields are just that :-)
policy		= policy_match
For the CA policy
[ policy_match ]
countryName		= match
stateOrProvinceName	= match
organizationName	= match
organizationalUnitName	= optional
commonName		= supplied
emailAddress		= optional
For the 'anything' policy
At this point in time, you must list all acceptable 'object'
types.
[ policy_anything ]
countryName		= optional
stateOrProvinceName	= optional
localityName		= optional
organizationName	= optional
organizationalUnitName	= optional
commonName		= supplied
emailAddress		= optional
####################################################################
[ req ]
default_bits		= 2048
default_keyfile 	= privkey.pem
distinguished_name	= req_distinguished_name
attributes		= req_attributes
x509_extensions	= v3_ca	# The extensions to add to the self signed cert
Passwords for private keys if not present they will be prompted for
input_password = secret
output_password = secret
This sets a mask for permitted string types. There are several options.
default: PrintableString, T61String, BMPString.
pkix	 : PrintableString, BMPString (PKIX recommendation before 2004)
utf8only: only UTF8Strings (PKIX recommendation after 2004).
nombstr : PrintableString, T61String (no BMPStrings or UTF8Strings).
MASK:XXXX a literal mask value.
WARNING: ancient versions of Netscape crash on BMPStrings or UTF8Strings.
string_mask = utf8only
req_extensions = v3_req # The extensions to add to a certificate request
[ req_distinguished_name ]
countryName			= Country Name (2 letter code)
countryName_default		= AU
countryName_min			= 2
countryName_max			= 2
stateOrProvinceName		= State or Province Name (full name)
stateOrProvinceName_default	= Some-State
localityName			= Locality Name (eg, city)
0.organizationName		= Organization Name (eg, company)
0.organizationName_default	= Internet Widgits Pty Ltd
we can do this but it is not needed normally :-)
#1.organizationName		= Second Organization Name (eg, company)
#1.organizationName_default	= World Wide Web Pty Ltd
organizationalUnitName		= Organizational Unit Name (eg, section)
#organizationalUnitName_default	=
commonName			= Common Name (e.g. server FQDN or YOUR name)
commonName_max			= 64
emailAddress			= Email Address
emailAddress_max		= 64
SET-ex3			= SET extension number 3
[ req_attributes ]
challengePassword		= A challenge password
challengePassword_min		= 4
challengePassword_max		= 20
unstructuredName		= An optional company name
[ usr_cert ]
These extensions are added when 'ca' signs a request.
This goes against PKIX guidelines but some CAs do it and some software
requires this to avoid interpreting an end user certificate as a CA.
basicConstraints=CA:FALSE
This is typical in keyUsage for a client certificate.
keyUsage = nonRepudiation, digitalSignature, keyEncipherment
PKIX recommendations harmless if included in all certificates.
subjectKeyIdentifier=hash
authorityKeyIdentifier=keyid,issuer
This stuff is for subjectAltName and issuerAltname.
Import the email address.
subjectAltName=email:copy
An alternative to produce certificates that aren't
deprecated according to PKIX.
subjectAltName=email:move
Copy subject details
issuerAltName=issuer:copy
This is required for TSA certificates.
extendedKeyUsage = critical,timeStamping
[ v3_req ]
Extensions to add to a certificate request
basicConstraints = CA:FALSE
keyUsage = nonRepudiation, digitalSignature, keyEncipherment
[ v3_ca ]
Extensions for a typical CA
PKIX recommendation.
subjectKeyIdentifier=hash
authorityKeyIdentifier=keyid:always,issuer
basicConstraints = critical,CA:true
Key usage: this is typical for a CA certificate. However since it will
prevent it being used as an test self-signed certificate it is best
left out by default.
keyUsage = cRLSign, keyCertSign
Include email address in subject alt name: another PKIX recommendation
subjectAltName=email:copy
Copy issuer details
issuerAltName=issuer:copy
DER hex encoding of an extension: beware experts only!
obj=DER:02:03
Where 'obj' is a standard or added object
You can even override a supported extension:
basicConstraints= critical, DER:30:03:01:01:FF
[ crl_ext ]
CRL extensions.
Only issuerAltName and authorityKeyIdentifier make any sense in a CRL.
issuerAltName=issuer:copy
authorityKeyIdentifier=keyid:always
[ proxy_cert_ext ]
These extensions should be added when creating a proxy certificate
This goes against PKIX guidelines but some CAs do it and some software
requires this to avoid interpreting an end user certificate as a CA.
basicConstraints=CA:FALSE
This is typical in keyUsage for a client certificate.
keyUsage = nonRepudiation, digitalSignature, keyEncipherment
PKIX recommendations harmless if included in all certificates.
subjectKeyIdentifier=hash
authorityKeyIdentifier=keyid,issuer
This stuff is for subjectAltName and issuerAltname.
Import the email address.
subjectAltName=email:copy
An alternative to produce certificates that aren't
deprecated according to PKIX.
subjectAltName=email:move
Copy subject details
issuerAltName=issuer:copy
This really needs to be in place for it to be a proxy certificate.
proxyCertInfo=critical,language:id-ppl-anyLanguage,pathlen:3,policy:foo
####################################################################
[ tsa ]
default_tsa = tsa_config1	# the default TSA section
[ tsa_config1 ]
These are used by the TSA reply generation only.
dir		= ./demoCA		# TSA root directory
serial		= $dir/tsaserial	# The current serial number (mandatory)
crypto_device	= builtin		# OpenSSL engine to use for signing
signer_cert	= $dir/tsacert.pem 	# The TSA signing certificate
# (optional)
certs		= $dir/cacert.pem	# Certificate chain to include in reply
# (optional)
signer_key	= $dir/private/tsakey.pem # The TSA private key (optional)
signer_digest  = sha256			# Signing digest to use. (Optional)
default_policy	= tsa_policy1		# Policy if request did not specify it
# (optional)
other_policies	= tsa_policy2, tsa_policy3	# acceptable policies (optional)
digests     = sha1, sha256, sha384, sha512  # Acceptable message digests (mandatory)
accuracy	= secs:1, millisecs:500, microsecs:100	# (optional)
clock_precision_digits  = 0	# number of digits after dot. (optional)
ordering		= yes	# Is ordering defined for timestamps?
# (optional, default: no)
tsa_name		= yes	# Must the TSA name be included in the reply?
# (optional, default: no)
ess_cert_id_chain	= no	# Must the ESS cert id chain be included?
# (optional, default: no)
ess_cert_id_alg		= sha256	# algorithm to compute certificate
# identifier (optional, default: sha256)
[insta] # CMP using Insta Demo CA
Message transfer
server = pki.certificate.fi:8700
proxy = # set this as far as needed, e.g., http://<IP_ADDRESS>:8080
tls_use = 0
path = pkix/
Server authentication
recipient = "/C=FI/O=Insta Demo/CN=Insta Demo CA" # or set srvcert or issuer
ignore_keyusage = 1 # potentially needed quirk
unprotected_errors = 1 # potentially needed quirk
extracertsout = insta.extracerts.pem
Client authentication
ref = 3078 # user identification
secret = pass:insta # can be used for both client and server side
Generic message options
cmd = ir # default operation, can be overridden on cmd line with, e.g., kur
Certificate enrollment
subject = "/CN=openssl-cmp-test"
newkey = insta.priv.pem
out_trusted = apps/insta.ca.crt # does not include keyUsage digitalSignature
certout = insta.cert.pem
[pbm] # Password-based protection for Insta CA
Server and client authentication
ref = $insta::ref # 3078
secret = $insta::secret # pass:insta
[signature] # Signature-based protection for Insta CA
Server authentication
trusted = $insta::out_trusted # apps/insta.ca.crt
Client authentication
secret = # disable PBM
key = $insta::newkey # insta.priv.pem
cert = $insta::certout # insta.cert.pem
[ir]
cmd = ir
[cr]
cmd = cr
[kur]
Certificate update
cmd = kur
oldcert = $insta::certout # insta.cert.pem
[rr]
Certificate revocation
cmd = rr
oldcert = $insta::certout # insta.cert.pem
[openssl_init]
ssl_conf = ssl_sect
[ssl_sect]
system_default = system_default_sect
[system_default_sect]
Options = UnsafeLegacyRenegotiation
bu şekilde düzeltildi ama aynı hata devam ediyor.


Add Badger as a pilot

@MaxPelly Updated to add Badger lore (also added signing keys so can finally be merged now ahaha)

Merged


Capitalization

Coverage remained the same at 54.78% when pulling 112eca94df2578edd1e04503825a4b2e38aada7d on rmcintosh:patch-1 into 1c65ade4b2d26d8d93f1739818c165ad25995dfd on linode:master.

Thanks!


Rename cheatnet create to cheatable_blockifier

For consistency with syscall handlers naming, cheatnet is an arbitrary name which does not make much sense in the context of the current architecture

I disagree, IMO this kind of change does not introduce anything other than organizational incovenience

Can be considered in the future


Implement sqlite support for server

Title says it all. For those wanting not to stand up Docker/Redis, sqlite is a great alternative for systems with simpler read/write latency requirements.
It will also allow installing and running the server with a single npx install command

This is now supported.


Incoming Messages : "550 Loop detected"

Hi Postal Team,
Thanks for the awesome SMTP tool that you have created.
I installed and setup the Postal SMTP tool in an OVH server separate from my Web server.
The outgoing messages are working fine.
However, for incoming messages, I am facing an issue where as soon as an incoming message is received, it's followed by a series of 3 messages sent from my 'return path' followed by "HARD FAIL" msg (2 Sent, 1 Hard Fail) . The error in the Hard Fail msg that I can see is  'Permanent SMTP delivery error ' with reason as '550 Loop detected'.
Can someone please help to resolve it?
Regards,
Rohit

that may be coming from Postal itself, https://github.com/postalhq/postal/blob/0fb323af3f37201eed492646007ed355f3617b51/lib/postal/smtp_server/client.rb#L389
Are you sending a message from your Postal server to itself or something?

No..  atleast not intentionally...
Following is the setup..
A, mail.mydomain.com points to IP of server where Postal is installed.
MX , mail.mydomain.com points to IP of server where Postal is installed.
A, rp.mail.mydomain.com points to IP of server where Postal is installed.
MX, rp.mail.mydomain.com points to mail.mydomain.com
CNAME, psrp points to  rp.mail.mydomain.com
MX, routes.mail.mydomain.com points to mx.mail.mydomain.com

Would anyone be able to help with the above DNS configuration if it's correct?? or is that the reason for the issue....

It sounds like the domain you're sending to has Postal as its MX records so Postal is trying to send a message to itself or something along those lines. Do you know the email provider of where you're trying to send an email?

I am sending email from GMAIL to postal (hosted on OVH server)..

on further investigation, i think it's due to the Address endpoint which points to the same domain address...

Sorry, I'didn't understand.
I'm having the same issue and I don't know how solving.


Swap to new eslint-config-condenast

This gist has the output before any code changes. If you want to be able to use this without making code changes, we could add these as overrides to the user-platform team. I'll leave that up to y'all.

I had a couple minor questions/notes but overall seems like a pretty straightforward change


Arf 105 create pull request api

Fixes #105  Create PullRequest Api integration

Also, please add the tests in [ApiSpec.scala](https://github.com/47deg/github4s/blob/master/github4s/jvm/src/test/scala/github4s/unit/ApiSpec.scala)

Codecov Report

Merging #109 into master will decrease coverage by 0.12%.
The diff coverage is 75%.

@@            Coverage Diff             @@
##           master     #109      +/-   ##
==========================================
- Coverage   88.14%   88.01%   -0.13%
==========================================
  Files          36       36
  Lines         506      534      +28
  Branches        3        3
==========================================
+ Hits          446      470      +24
- Misses         60       64       +4

Impacted Files
Coverage Δ

.../main/scala/github4s/free/domain/PullRequest.scala
100% <ø> (ø)
:arrow_up:

...n/scala/github4s/free/algebra/PullRequestOps.scala
60% <0%> (-40%)
:arrow_down:

...cala/github4s/free/interpreters/Interpreters.scala
83.87% <0%> (-1.38%)
:arrow_down:

...4s/shared/src/main/scala/github4s/GithubAPIs.scala
96.77% <100%> (+0.1%)
:arrow_up:

...ub4s/shared/src/main/scala/github4s/Encoders.scala
100% <100%> (ø)
:arrow_up:

...red/src/main/scala/github4s/api/PullRequests.scala
100% <100%> (ø)
:arrow_up:

...4s/shared/src/main/scala/github4s/HttpClient.scala
85.1% <0%> (+6.53%)
:arrow_up:

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 b869e17...11868ca. Read the comment docs.


feature link in the gene list of user-uploaded experiment is broken

We need to pass p2_feature_id for the link

fixed and available on alpha.


Add Shooting stars

Shooting stars would be cold to have in any form. Possible ideas for them include:

Terraria-like crafting ingredients
Mobs (enemies?) that fall from the sky

If that proves not too hard, an effect across the sky could be drawn to accompany the star

 Add Shooting stars


fix: fix Unrecognized field "id" (class io.atlasmap.v2.DataSourceMeta…

…data)
Fixes: #2449
fix: standalone tests fail to run
Fixes: #2451
springboot introduced JUnit5 and was conflicting with junit4 dependencies. Migrated standalone tests to JUnit5 jupiter.

Following up #2198 at runtime side


(BKR-1435) Add the fedora28-64, fedora28-32 platforms

Fedora 28 is only going to be a 64-bit platform, so you can remove the i386 versions.

@ScottGarman Ok, I added the 32-bit one b/c the ticket mentioned both.

Updated the PR to only add Fedora 28, 64.

Sorry for the confusion on the supported arches. Looks like the ticket generator was run with both arches listed, so all of the tickets are going to need to be updated.


Commit to apply Tizen to Splat for the first time

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Added the Tizen profile for the first time.
What is the current behavior? (You can also link to an open issue here)
Tizen has been added to Xamarin, but it is currently not available for Tizen development with Splat.
What is the new behavior (if this is a feature change)?
Added a Tizen Profile to Splat to make it available to developers.
What might this PR break?
Works independently of other Profiles.
Please check if the PR fulfills these requirements

[*] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

Other information:
This patch includes basic Splat functionality.
However, because the implemented Tizen Profile does not allow for the image to be transformed, the options fused with it do not work.

 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: ideallee sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

Got it. Thank you for letting us know.

Thanks @ideallee for the contribution. Modified a bit to get it to work with the MSBuild.Sdk.Extras and the new project format.


fix(tree): Fix draggable mismatch on SSR

solves(#5575)
If the attribute draggable is present it will be checked for hydration mismatch on vue >=v3.4.0 source.
The issue is that the draggable attribute is not a Boolean but rather an Enumerated of true and false source.
The proposed solution is to convert the boolean value to a string.

This is now solved on vue v3.4.11 https://github.com/vuejs/core/blob/main/CHANGELOG.md#3411-2024-01-12.


[SPAKR-34819][SQL]MapType supports orderable semantics

What changes were proposed in this pull request?
Currently MapType doesn't support orderable semantics, while it's supported in Hive/Presto. This makes it hard to migrate from Hive to SparkSQL if user have groupby/orderby map type in their sql.
Why are the changes needed?
Generally,  we compare two maps by the following steps:

If the size of two maps are not equal, compare them by size.
Otherwise, sort each map entry by map key, then compare two map entries one by one, first compare by key, then value.

We have to specially handle this in grouping/join/window because Spark SQL turns grouping/join/window partition keys into binary UnsafeRow and compare the binary data directly instead of using MapType's ordering. In this case, we have to insert a SortMapKey expression to sort map entry by key. This is very similiar to NormalizeFloatingNumbers
Does this PR introduce any user-facing change?
No
How was this patch tested?
Add more UTs

@hvanhovell  @cloud-fan @maropu Could you please help review this?

@c21 we should support this. I just ran out of time when I was working on it.

Can one of the admins verify this patch?

Ok to test

Test build #136556 has started for PR 31967 at commit a08356a.

Test build #136559 has started for PR 31967 at commit f60a5c4.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/41140/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/41140/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/41140/

Test build #136559 has finished for PR 31967 at commit f60a5c4.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/136559/

Test build #136556 has finished for PR 31967 at commit a08356a.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/136556/

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/41143/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/41143/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/41143/

Test build #136614 has started for PR 31967 at commit 58bb3cc.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/41196/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/41196/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/41196/

Test build #136614 has finished for PR 31967 at commit 58bb3cc.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/136614/

Link: #15970 and #19330

Any update?

@WangGuangxin If you cannot keep working on it, is it okay that I take this over?

@WangGuangxin If you cannot keep working on it, is it okay that I take this over?

Sure, I'm stuck with something else, you can take this over if you have time. Thanks


Development - org.jkiss.dbeaver.ext.ui.locks.model does not exist

I am trying to setup my development workspace to contribute to dbeaver. However, I stumbled upon a issue on one of the plugin on 'org.jkiss.dbeaver.ext.ui.locks'. The error says that the org.jkiss.dbeaver.ext.ui.locks.model doesn't exist in the plugin. Upon checking I can confirm that the package do not exist on the plugin. Was the package left out for some reason? Can we just remove it since it is blocking the startup of the UI from the export package manifest file?

Branch: devel

It is a non-critical warning in Eclipse IDE. Already fixed, thanks for bug report.


Design: Consistent mesh for page-level mutation logs

Currently the cache invalidation logic depends on FoundationDB. After each call to /batch/commit, we store the set of pages mutated by the transaction into a special keyspace in FDB, keyed by the commit versionstamp. When a later request to /stat comes in, keys in the range (client_last_known_commit_version, current_read_version) are scanned and returned to the client so that they can invalidate their caches.
This results in a lot of temporary data that is written once and read a few times. It is a waste to let these data go through the entire FDB transaction & storage systems, and a better design is possible.

The design is to form a mesh network of all mvstore instances so that they can synchronize cache invalidation logs directly. Metadata is still backed by FDB to keep things consistent.

Do you need any help with this?

@fire I haven't been able to get back to this yet... The idea I have in mind is that, we select one mvstore process in the cluster to be the "write proxy" and let all mutations go through the proxy. The proxy keeps an interval of mutated page numbers in memory (10min?). Readers can then query the proxy and invalidate their caches accordingly. In case the write proxy is not able to provide this information (for example if a new proxy is elected), the reader invalidates its entire cache.
Election of the write proxy happens through FDB. The FDB read version can be used to fence between write proxy generations. How to scale the role is still an open question though (maybe shard it like what FDB does for itself?)


[SPARK-42354][BUILD] Upgrade jackson to 2.14.2

What changes were proposed in this pull request?
This pr aims upgrade Jackson related dependencies to 2.14.2
Why are the changes needed?
This version include some bug fix and improvement of databind, such as:

https://github.com/FasterXML/jackson-databind/issues/3063
https://github.com/FasterXML/jackson-databind/issues/3699

The full release notes as follows:

https://github.com/FasterXML/jackson/wiki/Jackson-Release-2.14.2

Does this PR introduce any user-facing change?
No
How was this patch tested?
Pass Github Actions

Merged to master/3.4.

Thanks @dongjoon-hyun @HyukjinKwon


qt: Add missing placeholders

This PR ist part of a series of +-25 PRs related to UI redesigns. Its ancestor is #3574, its successor is  #3613. I did not screenshot every single PR and its changes, instead i made "walk through all screen" videos with the result of this PR series and also with the 0.15 UI. If there are any concrete screenshots wanted, just let me know. To build with the full set of changes you can build from the branch xdustinface:pr-ui-redesign which always contains all changes.
 -> Walk through 0.15
 -> Walk through Redesign
I tried to give the commits enough text to make things obvious without a lot description for each PR. Also here, if you want more description for this specific PR, let me know.
About this PR
See individual commit messages.

Ready for review!

Needs rebase

Rebased!


Add the possibility to add context from various files

Seems like tests are not stable..

@holdfenytolvaj They're very stable: https://travis-ci.org/rubenv/angular-gettext/builds
If they're failing, it's probably due to the code changes.

That is correct :), but not my changes. Apparently this test is not valid any more
it("Gracefully handles failure", function () {
        catalog.loadRemote("/strings/nl.json");
        $httpBackend.expectGET("/strings/nl.json").respond(404);
        $httpBackend.flush();
});

as angular (1.6.3) throws an error if the promise rejections is not handled.
catalog.loadRemote("/strings/nl.json").then(()=>{}, ()=>{console.error('rejected')});
would pass, or older versions of angular would make it pass.
But as you have the test:

    it("Returns a promise (failure)", function () {
        var successCalled = false;
        var failedCalled = false;
        var promise = catalog.loadRemote("/strings/nl.json");
        function success() {
            successCalled = true;
        }
        function failed() {
            failedCalled = true;
        }
        promise.then(success, failed);
        $httpBackend.expectGET("/strings/nl.json").respond(404);
        $httpBackend.flush();
        assert(!successCalled);
        assert(failedCalled);
    });

The first one (which is failing) should go as just not true anymore and with any changes would be redundant with this second one.

Re the Angular 1.6.3 change in behavior: probably best to just get rid of the test then. We'll follow the new behaviour that way, shouldn't be unexpected. Thanks for looking into this.

Merged, thanks a lot! Will roll release.

Thanks!


COF and SOD huge bugs?

Hi all. Something is happening that I cannot understand, I'm doing hyperparameter tuning to all proximity based algorithms with RandomSearchCV form sklearn and only COF and SOD have problems. What is happening is the following:  the constructor parameters are all None even though I'm passing values to it. I tried to change the code of SOD and hardcoded the values of the constructor and I'm still getting NoneType. Please help.

Can you please provide a reproducible example?

I have this code in a file called hypertuning.py in the "notebooks" folder, you can put it there and runs smoothly. I will explain the behaviour and it's easier if you run it: basically for all the algorithms I'm trying to optimize the parameters and the "print(clf)" line tells me, after fitting, the parameters that RandomSearch is using for the current model. For COF and SOD the parameters are None no matter what I do. This code saves the best parameters in best_params.txt file in the current folder, "notebooks".
`import warnings
warnings.filterwarnings("ignore")
from sklearn.model_selection import RandomizedSearchCV
import numpy as np
import pandas as pd
from pandas import read_excel
from pyod.models.lof import LOF
from pyod.models.cof import COF
from pyod.models.cblof import CBLOF
from pyod.models.hbos import HBOS
from pyod.models.knn import KNN
from pyod.models.sod import SOD
BASE_DIR = '../../'
datasets = [
'MED-WTG1-DATA.xlsx',
'MED-WTG2-DATA.xlsx',
'MED-WTG3-DATA.xlsx',
'MED-WTG4-DATA.xlsx',
'MED-WTG5-DATA.xlsx',
'MED-WTG6-DATA.xlsx',
'MED-WTG7-DATA.xlsx',
'MED-WTG8-DATA.xlsx',
]
lof_random = {
'n_neighbors': np.arange(1, 101),
'algorithm': ['ball_tree', 'kd_tree', 'auto'],
'leaf_size': np.arange(20, 41),
'metric': ['minkowski', 'euclidean']
}
cof_random = {
'n_neighbors': np.arange(1, 101)
}
cblof_random = {
'n_clusters': np.arange(2, 101),
'alpha': np.arange(0.5, 1, 0.05)
}
hbos_random = {
'n_bins': np.arange(1, 101)
}
knn_random = {
'n_neighbors': np.arange(1, 101),
'algorithm': ['ball_tree', 'kd_tree', 'auto'],
'leaf_size': np.arange(20, 41),
'metric': ['minkowski', 'euclidean'],
}
sod_random = {
'alpha': np.arange(0.5, 1, 0.05)
}
classifiers_params = {
'Local Outlier Factor (LOF)': [LOF(), lof_random],
'Connectivity-Based Outlier Factor (COF)': [COF(), cof_random],
'Clustering-Based Local Outlier Factor (CBLOF)': [CBLOF(), cblof_random],
'Histogram-based Outlier Score (HBOS)': [HBOS(), hbos_random],
'K Nearest Neighbors (KNN)': [KNN(), knn_random],
'Average K Nearest Neighbors (AvgKNN)': [KNN(method='mean'), knn_random],
'Median K Nearest Neighbors (MedKNN)': [KNN(method='median'), knn_random],
'Subspace Outlier Detection (SOD)': [SOD(), sod_random]
}
with open('best_params.txt', 'w', encoding='utf8') as pepi:
for j in range(len(datasets)):
    data_file = BASE_DIR + datasets[j]
    data_name = data_file[len(BASE_DIR):-5]
    data = read_excel(data_file).to_numpy()[:,[2,3,5,7,10,11]]
    data = np.array(data, dtype=np.float32)

    print("\n... Processing", data_name, '...')
    pepi.write(data_name + '\n')

    X = data[:,:-1]
    y = data[:,-1]

    for clf_name, clf in classifiers_params.items():
        print("... Hyper tuning", clf_name, "...")
        print(clf)

        cv = [(slice(None), slice(None))]
        rf_random = RandomizedSearchCV(estimator=clf[0], param_distributions=clf[1],
                                        n_iter=10, cv=cv, n_jobs=-1, scoring='roc_auc', verbose=2)
        rf_random.fit(X, y)
        best_params_dict = rf_random.best_params_
        best_score = round(rf_random.best_score_, 2)

        print('\n Best params for ' + clf_name)
        print(best_params_dict)
        print()
        pepi.write('Best params for ' + clf_name + ' with best AUC ' + str(best_score) + '\n')
        for k,v in best_params_dict.items():
            pepi.write(k + ': ' + str(v) + '\n')
        pepi.write('\n')

`

Hi there,
I just fixed the bug. It is just a naming inconvenience with Scikit-learn conversion.
It is all sorted out now, I tried your code and it's working.
I opened a Pull Request and waiting for Yue @yzhao062 to merge it.
Yahya.

I just saw the changes, thank you so much. Shall I close this issue or one of the contributors?

I just saw the changes, thank you so much. Shall I close this issue or one of the contributors closes it?

No problem. You're welcome. Yue shall close it once PR is merged.
Yahya.

Hey guys. I have another thought here...
The reason it is called n_neighbors_ is indeed following sklearn convention given the training samples are not enough...see an example of LOF here: https://scikit-learn.org/stable/modules/generated/sklearn.neighbors.LocalOutlierFactor.html
It is possible to add some additional lines to have:
self.n_neighbors = n_neighbors, so your printing will be running ok. The current version is actually running correctly, while the true parameter value is stored in n_neighbors_ instead.
Thoughts...?

Hi,
I don't have the knowledge nor the sensibility in these matters like you guys but I can give an honest oppinion. The idea of following sklearn convention sounds good and I would rather prefer that you add those lines since the variable I'm using is indeed called n_neighors. Another thing that I forgot to mention that is also weird for me is the fact: I also ran the COF and SOD examples in the "examples" folder, and I printed the model after the "fit" call and n_neighbors are indeed None again but the example runs smootlhy. Right now, as a temporary solution maybe, I will use the changes that @John-Almardeny did since I have work to do.
Thanks so far for all the help guys.

Sorry to bother guys but I already changed the files with the respective changes that @John-Almardeny did, on my local repo, tried to run without changing the code I posted here and still get the same error. I really can't figure out what is going on.

Change n_jobs to 1.

Just did and tried with other values for n_jobs for my RandomizedSearch and still the same error. Did I forget to change anything? I'm pretty I copied everything you changed.

Ok guys I found the problem! Since I'm running my project on a conda environment, even after I did your changes I need to run again "pip install ." to update my conda environment. Everything is working now.
I still think the changes you did are necessary. Sorry for the inconvenience.


Add logic for Last Run Duration in seconds to sysjobshistory documentation

It took longer than necessary for me to analyze and write the logic to determine the time the job finished using the run_date, run_time and run_duration columns.  Since I had to generate this for my use, I figured I would submit it as an enhancement to the documentation, so others can make use of it as well.
The sample below includes the formula for Last Run Duration Seconds, along with a refactor of the LastRunDateTime calculation to use math calculations instead of string functions.  It also calculates the Last Run Finish Date Time as well.
SELECT       sj.name AS Name,
             sh.step_name AS StepName,
             shp.LastRunStartDateTime,
             shp.LastRunDurationSeconds,
             CASE
               WHEN sh.run_duration > 235959
                 THEN CAST((CAST(LEFT(CAST(sh.run_duration AS VARCHAR), LEN(CAST(sh.run_duration AS VARCHAR)) - 4) AS INT) / 24 ) AS VARCHAR) + '.' + RIGHT('00' + CAST(CAST(LEFT(CAST(sh.run_duration AS VARCHAR), LEN(CAST(sh.run_duration AS VARCHAR)) - 4) AS INT) % 24 AS VARCHAR), 2) + ':' + STUFF(CAST(RIGHT(CAST(sh.run_duration AS VARCHAR), 4) AS VARCHAR(6)), 3, 0, ':')
               ELSE STUFF(STUFF(RIGHT(REPLICATE('0', 6) + CAST(sh.run_duration AS VARCHAR(6)), 6), 3, 0, ':'), 6, 0, ':')
             END AS [LastRunDuration (d.HH:MM:SS)],
             DATEADD(SECOND, shp.LastRunDurationSeconds, shp.LastRunStartDateTime) AS LastRunFinishDatetime
FROM         msdb.dbo.sysjobs       AS sj
  INNER JOIN msdb.dbo.sysjobhistory AS sh ON sj.job_id = sh.job_id
  CROSS APPLY (
        SELECT DATETIMEFROMPARTS(
                sh.run_date / 10000, /* years */
                sh.run_date % 10000 / 100, /* months */
                sh.run_date % 100, /* days */
                sh.run_time / 10000, /* hours */
                sh.run_time % 10000 / 100, /* minutes */
                sh.run_time % 100, /* seconds */
                0 /* milliseconds */
            ) AS LastRunStartDateTime,
            (sh.run_duration / 10000) * 3600 /* convert hours to seconds, can be greater than 24 */
		+ ((sh.run_duration % 10000) / 100) * 60  /* convert minutes to seconds */
		+ (sh.run_duration % 100) AS LastRunDurationSeconds
        ) AS shp

@wdhenrik Just to clarify, is this suggestion for a specific article? Thanks -

Yes, for the msdb.dbo.sysjobhistory table documtation.
https://learn.microsoft.com/en-us/sql/relational-databases/system-tables/dbo-sysjobhistory-transact-sql?view=sql-server-ver16

Thanks for the suggestion, @wdhenrik!
Hey @rwestMSFT @WilliamDAssafMSFT - Do you mind taking a look at this to see if we can use it as a sample?

Potentially yes. How about this for style?
SET NOCOUNT ON;

SELECT sj.name AS Name,
    sh.step_name AS StepName,
    shp.LastRunStartDateTime,
    shp.LastRunDurationSeconds,
    CASE
        WHEN sh.run_duration > 235959
            THEN CAST((CAST(LEFT(CAST(sh.run_duration AS VARCHAR),
                LEN(CAST(sh.run_duration AS VARCHAR)) - 4) AS INT) / 24) AS VARCHAR)
                    + '.' + RIGHT('00' + CAST(CAST(LEFT(CAST(sh.run_duration AS VARCHAR),
                LEN(CAST(sh.run_duration AS VARCHAR)) - 4) AS INT) % 24 AS VARCHAR), 2)
                    + ':' + STUFF(CAST(RIGHT(CAST(sh.run_duration AS VARCHAR), 4) AS VARCHAR(6)), 3, 0, ':')
        ELSE STUFF(STUFF(RIGHT(REPLICATE('0', 6) + CAST(sh.run_duration AS VARCHAR(6)), 6), 3, 0, ':'), 6, 0, ':')
        END AS [LastRunDuration (d.HH:MM:SS)],
    DATEADD(SECOND, shp.LastRunDurationSeconds, shp.LastRunStartDateTime) AS LastRunFinishDatetime
FROM msdb.dbo.sysjobs sj
INNER JOIN msdb.dbo.sysjobhistory sh ON sj.job_id = sh.job_id
CROSS APPLY (SELECT DATETIMEFROMPARTS(sh.run_date / 10000, --years
        sh.run_date % 10000 / 100, --months
        sh.run_date % 100, --days
        sh.run_time / 10000, --hours
        sh.run_time % 10000 / 100, --minutes
        sh.run_time % 100, --seconds
        0 -- milliseconds
    ) AS LastRunStartDateTime,
    (sh.run_duration / 10000) * 3600 -- convert hours to seconds, can be greater than 24
    + ((sh.run_duration % 10000) / 100) * 60 --convert minutes to seconds
    + (sh.run_duration % 100) AS LastRunDurationSeconds
) AS shp
GO

@wdhenrik We're happy to include this in our article, so if you open a pull request (using the pencil icon on the live article, and update the script there, we can give you proper credit as a contributor.
If you're happy to move without contribution, I can do an internal PR.
Let me know.

This issue will close automatically when our internal PR is merged.


[Event Request] Page 11310 "General Ledger Entries Apply" - OnAfterSetIncludeEntryFilter

Hello,
We would need a new event OnAfterSetIncludeEntryFilter on page 11310 "General Ledger Entries Apply":
internal procedure SetIncludeEntryFilter()
var
    IsHandled: Boolean;
begin
    IsHandled := false;
    OnBeforeSetIncludeEntryFilter(Rec, IncludeEntryFilter, IsHandled);
    if IsHandled then
        exit;

    SetCurrentKey("G/L Account No.", "Posting Date", "Entry No.", Open);
    case IncludeEntryFilter of
        IncludeEntryFilter::All:
            SetRange(Open);
        IncludeEntryFilter::Open:
            SetRange(Open, true);
        IncludeEntryFilter::Closed:
            SetRange(Open, false);
    end;

    OnAfterSetIncludeEntryFilter(Rec, IncludeEntryFilter); // new event
end;

[IntegrationEvent(false, false)]
local procedure OnAfterSetIncludeEntryFilter(var GLEntryApplicationBuffer: Record "G/L Entry Application Buffer"; var IncludeEntryFilter: Option)
begin
end;

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.


Jitter dimensions Vs Unity dimensions

Thanks for this great library.
I'm building a game server with Jitter physics. The clients receive the objects' transform information from the server.
I don't know how to make an object on Unity match the size of its related Jitter rigidbody. For example: my sphere on the server has 0.5 radius. On Unity, the sphere object that receives its transform information also has 0.5. It SEEMS to match the dimension on the server, but I'm not sure, and it's hard to debug that. Is there an exact formula or anything like that?

I do not know the way you couple Jitter and Unity but a general answer is that you can choose whatever units you like. Jitter is mostly tuned in such a way, that most of your objects in the world should be of size "1" (e.g. a sphere with radius 0.5 is perfect). Also the default gravity is set to 9.81 which "fit" the gravitational acceleration on earth, if you choose your unit of length to be "meter" [m] and your unit of time to be "second" [s]. Other than that Jitter has no "intrinsic scale". If you create a sphere of radius 5 (in whatever units) in Unity, you can just ask Jitter to simulate a sphere of radius 5 in Jitter.


Fix errors when productName contains spaces

Just an easy fix due to problems I was having in one of my projects

@eDexiam - thanks ;)


bug: ion-tabs + header issue

Type: bug
Platform: all
Hey,
I noticed some strange behaviour that involves ion-tabs (more specifically ion-tab) and a required header element.  Please see the following CodePen:
http://codepen.io/nokturnal/pen/pveKvw
Notice how everything works as expected.
If you comment out lines 58 to 60 things go a bit buggy:

Top view padding is not applied rendering part of the view behind the nav header.
Bottom view padding is not applied rendering part of the content behind the tab footer
Scrolling is disabled

Note: if you substitute the  with a  the above scenario still applies.
Is a header element (or ion-header-bar) mandatory now for ion-tab elements?

Greetings, @nokturnal!
We are now requiring all issues to be submitted through our custom issue form so that we have all of the information necessary to fix them as quickly as possible.
Your progress on this issue has been saved at the following url:
link to Ionic issue form
This issue will be closed if not resubmitted through the form. Please fill out the rest of the form so that we may assist you.
Thank you for allowing me to assist you.

Hey @nokturnal, I'm getting a lot of JS errors on the codepen. Did you do some debugging since posting this?

Having same problem.

Greetings @nokturnal!
My sensors indicate a reply was requested, but we have not received one yet, I am using my robot powers to close this issue. However, if you are still experiencing this issue, please feel free to reopen it by creating a new issue, and include any examples or necessary information.
Thank you for allowing me to assist you.

Greetings @nokturnal!
My sensors indicate a reply was requested, but we have not received one yet, I am using my robot powers to close this issue. However, if you are still experiencing this issue, please feel free to reopen it by creating a new issue, and include any examples or necessary information.
Thank you for allowing me to assist you.


Failed to deploy clamav chart with HPA memory

I try to configure HPA with memory limits, but Chart is invalid due to values.schema.json
https://github.com/wiremind/wiremind-helm-charts/blob/main/charts/clamav/values.schema.json#L216
Both values are null and we have an error like :
Error: values don't meet the specifications of the schema(s) in the following chart(s): clamav: - hpa.memory: Invalid type. Expected: null, given: string
I deploy with argocd

Indeed, schema is wrong here...
PR accepted!

Looks like #227 now.

For reference: https://github.com/wiremind/wiremind-helm-charts/pull/230 has been merged, but not the schema yet.


Fix org-tree-slide-mode keybindings

This is a pretty simple commit that just fixes the keybindings for org-tree-slide-mode.
One thing I find a bit curious is that additional keybindings are added identically to org-mode below in the file, yet those seem to work propertly without the mode specifiers:
  (map! :map org-mode-map
        "<f8>" #'+org-present/org-tree-slides
        "<f7>" #'+org-present/next)

Also, note that the +org-present/next function seems to be missing.
Used this mode successfully while giving a talk at an Emacs meetup last night, thanks for implementing it! :+1:

Sorry about the noise, just testing something. Anyhow, thanks for this, and I'm glad to know that org-present has been helpful!


Display an error message for deleting clinics with existing encounters

Display an error message for deleting clinics with existing encounters.
Should not allow deleting a clinic that already has active encounters, display a message for the user.

Merged in #130


I would to like set time limit for talos.scan model ?

Please suggest me how to set time limit or early stopping for talos model .
there is time format feature is there ,please suggest one example to set the time limit for talos.scan model.

talos.Scan(...time_limit=2020-02-25 08:00...) will stop the experiment no later than 25th of Feb, 2020 at 8 am.
To get most out of Talos, I encourage you to read through the documentation: https://autonomio.github.io/talos.
Closing this as resolved.


add go generate varlink to copr spec

Now that we make the varlink .go file on the fly, we need to have the
spec call go generate on it to build properly.
Signed-off-by: baude<EMAIL_ADDRESS>

LGTM

@rh-atomic-bot r+


Is there a way to change ProdID?

subject says it all. :)
Thanks
Greg

Never mind, I found it. I was looking on the event rather than the calendar. A quick trip to the source code found it pretty quickly.


Improve Cfd state assertions in actor-level tests

It was really hard to figure out which assertion was failing.
Add more descriptive logs and additional assertions.

bors r+

bors r+


resolve-crashes.py: remove "REQUIRES: asserts" as well

We keep doing this by hand and there's no reason to do so.

@swift-ci Please smoke test

@swift-ci Please Python lint

Looks good! :-)

Good call, thanks!


slow5 doesn't detect newline

If there is a newline at the end of a slow5 file, the parser detects this as an additional line / read.

@Koeng101 was this ever fixed?


Video not getting recorded

Video not getting recorded
While running tests using below, video not getting recorded
flashlight test
--bundleId=com.something
--beforeAllCommand="maestro test SetupFlow.yml"
--beforeEachCommand="maestro test PerfPropertyPageScrollBeforeEach.yml"
--testCommand="maestro test PerfPropertyPageScrollTest.yml"
--resultsTitle=AppSearchScroll
--iterationCount=2
--duration=10000
--record

Hi @dipak-amber, could you share your device model and OS version?
What happens? Do you get usual logs with "Recording started" and everything but then there's no video file generated?


Transaction configurable commit limit

As the 100 transaction it is a dynamodb, I decided to keep it as a hard limit and allowed the context manager to be able to accept smaller batches to commit.

Applied black, the errors in pytest are from areas that I didn't touch in this PR, probably some unpinned library was updated?

Done, all green now :heavy_check_mark:

Codecov Report

Merging #11 (11a815d) into main (4b90aaa) will not change coverage.
The diff coverage is 100.00%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
@@            Coverage Diff            @@
##              main       #11   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            6         6
  Lines          637       641    +4
  Branches       119       119
=========================================
+ Hits           637       641    +4

Files Changed
Coverage Δ

dyntastic/transact.py
100.00% <100.00%> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


x/tools/gopls/test, x/tools/internal/lsp: inscrutable test output on failure

What version of Go are you using (go version)?
https://golang.org/cl/258298
What did you do?
Run TryBots for x/tools.
What did you expect to see?
All tests passing, or a test log with a clear indication of what actually went wrong (per http://golang.org/wiki/CodeReviewComments#useful-test-failures).
What did you see instead?
https://storage.googleapis.com/go-build-log/624a58dc/linux-amd64_445ec507.log
which contains what appears to me as a wall of text followed by an otherwise-disconnected diff in an expected output count:
--- FAIL: TestCommandLine (31.97s)
    --- FAIL: TestCommandLine/Modules (16.61s)
        tests.go:884: test summary does not match:
            --- want
            +++ got
            @@ -7,7 +7,7 @@
             FuzzyCompletionsCount = 8
             RankedCompletionsCount = 157
             CaseSensitiveCompletionsCount = 4
            -DiagnosticsCount = 44
            +DiagnosticsCount = 43
             FoldingRangesCount = 2
             FormatCount = 6
             ImportCount = 8
FAIL
FAIL	golang.org/x/tools/gopls/test	32.066s

From that output, I have no idea which of the 44(!) expected diagnostics from the test was missing, or which line or source file was intended to produce that missing diagnostic.

CC @stamblerre @heschik @ianthehat

Closing as dupe of https://go.dev/issue/54845.


Prefer property name instead of title for class name

When the title of a schema object doesn't match its property name, reference resolution breaks. Simplest demonstration:
#!/usr/bin/env python3
from typing import Generic, TypeVar
from pydantic import BaseModel
from pydantic.generics import GenericModel
from fastapi import FastAPI

app = FastAPI()

T = TypeVar('T')

class GenericItem(GenericModel, Generic[T]):
    prop: T

@app.get("/int_item", response_model=GenericItem[int])
def get_int_item():
    return GenericItem[int](prop=88)

This will cause the client to produce a warning:
Warning(s) encountered while generating. Client was generated, but some pieces may be missing

WARNING parsing GET /int_item within default.

Cannot parse response for status code 200, response will be ommitted from generated client

Reference(ref='#/components/schemas/GenericItem_int_')

This pull request fixes this by prefering the property name as the class name for a model over its title.

The 3 failing tests and 8 warnings were already present before my modification

The 3 failing tests and 8 warnings were already present before my modification

Odd, main looks like it passed all checks on last build. I'll figure out what's going on there.
@bowenwr (and team) do you want to take a look at this to see if you disagree? I don't have a strong opinion either way, but it would be a breaking change to existing clients (meaning we'd do this in a 0.8.0).

Odd, main looks like it passed all checks on last build. I'll figure out what's going on there.
@bowenwr (and team) do you want to take a look at this to see if you disagree? I don't have a strong opinion either way, but it would be a breaking change to existing clients (meaning we'd do this in a 0.8.0).

I'm still playing catch-up on our other fixes to restore our integration tests. If I can get there, I'll take a look at this over the weekend to see if it has any implications for us. Thanks!

I'm still playing catch-up on our other fixes to restore our integration tests. If I can get there, I'll take a look at this over the weekend to see if it has any implications for us. Thanks!

@dbanty note that I also have no opinion on how the class name is determined. It's just that I think reference resolution is currently broken. I guess it would also be fine if the class_name is set to title, but then the schema.models dictionary should at least also have an entry with the attribute name of the model in #/components/schemas, so reference resolution works. Simplest json to demonstrate broken reference resolution:
{
  "openapi": "3.0.2",
  "info": {
    "title": "test",
    "version": "0.1.0"
  },
  "paths": {
    "/": {
      "get": {
        "responses": {
          "200": {
            "description": "Successful Response",
            "content": {
              "application/json": {
                "schema": {
                  "$ref": "#/components/schemas/Ham"
                }
              }
            }
          }
        }
      }
    }
  },
  "components": {
    "schemas": {
      "Ham": {
        "title": "Eggs",
        "type": "object",
      }
    }
  }
}

@dbanty note that I also have no opinion on how the class name is determined. It's just that I think reference resolution is currently broken. I guess it would also be fine if the class_name is set to title, but then the schema.models dictionary should at least also have an entry with the attribute name of the model in #/components/schemas, so reference resolution works. Simplest json to demonstrate broken reference resolution:
{
  "openapi": "3.0.2",
  "info": {
    "title": "test",
    "version": "0.1.0"
  },
  "paths": {
    "/": {
      "get": {
        "responses": {
          "200": {
            "description": "Successful Response",
            "content": {
              "application/json": {
                "schema": {
                  "$ref": "#/components/schemas/Ham"
                }
              }
            }
          }
        }
      }
    }
  },
  "components": {
    "schemas": {
      "Ham": {
        "title": "Eggs",
        "type": "object",
      }
    }
  }
}

I assume that a mismatch between the schema name and title is fairly uncommon, so I don't foresee this being too bad of a breaking change to go around and fix. We need to support it regardless, so worst come to worst we could make it a config option but that feels a smidge icky - config shouldn't be required to generate a client from a valid openapi document.

I assume that a mismatch between the schema name and title is fairly uncommon, so I don't foresee this being too bad of a breaking change to go around and fix. We need to support it regardless, so worst come to worst we could make it a config option but that feels a smidge icky - config shouldn't be required to generate a client from a valid openapi document.

I wasn't able to get to this, so don't block on my account. Though I appreciate the opportunity!

I wasn't able to get to this, so don't block on my account. Though I appreciate the opportunity!

@dbanty note that I also have no opinion on how the class name is determined. It's just that I think reference resolution is currently broken. I guess it would also be fine if the class_name is set to title, but then the schema.models dictionary should at least also have an entry with the attribute name of the model in #/components/schemas, so reference resolution works.

I see, when we loop through components to register models prior to property parsing, we register whatever the "class_name" is of the model rather than the defined reference name. This is a bug for sure.
I think the right move then is to change parser.properties.build_model_property to register the name instead of the title. I believe this is dict key is only used for looking up references, so it really should match the component definition. There's no reason it as to match to class name as far as I can tell.
That should fix the resolution bug without changing anyone's existing generated code. @jrversteegh do you want to take a stab at this? If not then I can do it probably later this week.

@dbanty note that I also have no opinion on how the class name is determined. It's just that I think reference resolution is currently broken. I guess it would also be fine if the class_name is set to title, but then the schema.models dictionary should at least also have an entry with the attribute name of the model in #/components/schemas, so reference resolution works.

I see, when we loop through components to register models prior to property parsing, we register whatever the "class_name" is of the model rather than the defined reference name. This is a bug for sure.
I think the right move then is to change parser.properties.build_model_property to register the name instead of the title. I believe this is dict key is only used for looking up references, so it really should match the component definition. There's no reason it as to match to class name as far as I can tell.
That should fix the resolution bug without changing anyone's existing generated code. @jrversteegh do you want to take a stab at this? If not then I can do it probably later this week.

@dbanty OK, I'll have a look at it and update this pull request if I can find out how to do it.

@dbanty OK, I'll have a look at it and update this pull request if I can find out how to do it.

@dbanty I've updated the pull request to only modify the key in the schema dictionary, not the class name. I hope that is what you had in mind.
After looking at this some more, I feel using the "title" for the class_name is not appropriate however. According to json schema, the title is a "short description", which does not sound like it'd be generally suitable for a class name imho. Also it's just confusing, as this issue demonstrates ;)

@dbanty I've updated the pull request to only modify the key in the schema dictionary, not the class name. I hope that is what you had in mind.
After looking at this some more, I feel using the "title" for the class_name is not appropriate however. According to json schema, the title is a "short description", which does not sound like it'd be generally suitable for a class name imho. Also it's just confusing, as this issue demonstrates ;)

I checked out this code and poked around to figure out why the e2e tests are failing. There are a few other places in the code that we assume the generated class name to be the key of the model intentionally because we can't have two classes with the same name. So the schemas.models and schemas.enums dictionaries must continue to be named after the generated class name.
This is an issue because the class name will not always be equal to the ref name... so clearly more work is required to decouple the deduplication of classes from the registration & lookup of references. We could just loop through all models/enums when doing a deduplication check instead of looking up by key this just feels slow. Then again, having two separate dictionaries (lookup by Ref and lookup by class_name) feels wasteful.
If we went back to your idea of always naming on name and never title, that would solve the issue because class_name would always be derived from reference name and therefore it's still a single lookup. However, that means that someone with a deeply nested object somewhere would have to live with the autogenerated GrandParentParentPropertyName class instead of being able to provide a title with a more sensible name.
I don't have a recommended solution, just pointing out what the problem is at the moment.

I checked out this code and poked around to figure out why the e2e tests are failing. There are a few other places in the code that we assume the generated class name to be the key of the model intentionally because we can't have two classes with the same name. So the schemas.models and schemas.enums dictionaries must continue to be named after the generated class name.
This is an issue because the class name will not always be equal to the ref name... so clearly more work is required to decouple the deduplication of classes from the registration & lookup of references. We could just loop through all models/enums when doing a deduplication check instead of looking up by key this just feels slow. Then again, having two separate dictionaries (lookup by Ref and lookup by class_name) feels wasteful.
If we went back to your idea of always naming on name and never title, that would solve the issue because class_name would always be derived from reference name and therefore it's still a single lookup. However, that means that someone with a deeply nested object somewhere would have to live with the autogenerated GrandParentParentPropertyName class instead of being able to provide a title with a more sensible name.
I don't have a recommended solution, just pointing out what the problem is at the moment.

I'm going to close this PR just because the requirement here has changed a lot since inception. I think when we're ready to fix we can do a new PR closing #342.


Hide a tool's rendered cached stats or text

Prerequisites

[x] Are you running the latest version?
[x] Are you reporting to the correct repository?
[x] Did you perform a cursory search?

Description
I am currently developing an algorithm that creates a lot of Probe elements inside a RectangleRoi depending on the HU. This is to create segments of areas that are not air. Basically, automatically paint tumours or other parts of the body.
However, this Probe has of course the MO and SP data shown with the circle. I would like to know if it is possible to only show the circle without any cached stats text attached to it, because this algorithm is pixel by pixel so the stats are overlapped with each other (see pictures).

This is to create segments of areas that are not air. Basically, automatically paint tumours or other parts of the body.

While this is certainly something we can add support for (and it may already exist, I'd have to double check), why not "paint" using the brush tool instead? It is a much more common representations for segments.

Hi @dannyrb, as usual, thanks for your quick response.
My first choice was to use the Brush Tool. While the first thing I did was to check up what information it brings from getToolState, there is an error, you have to use 'brush' instead of 'Brush', and this is not stated, so I got confused. Next, I painted on my canvas and checked the tool state, it brings hundreds of thousands of arrays with value 0, so I don't really now what this represents. Next, for some reason, after activating the BrushTool, it makes the whole canvas in a state that it is constantly updating, for example, I have a renderTime function from state, that onImageRender() gets the time it took to render that image, and as onImageRender() is called once an image is rendered, this render time is somewhat static. When using the BrushTool, this render time is constantly being updated, like onImageRender() is being called every frame, I don't really know what is causing this, I just know is the BrushTool as this only happens with this tool. And finally, I don't know how to specify the brush tool an X and Y coordinate to paint to. This is something I can do with the other tools, but as I don't really understand the BrushTool structure, I don't know how to specify this information. So this is why I went with the ProbeTool instead of the BrushTool. If this points are something you can help me with, would be great, if not, then I would really be interested in an option for hiding/showing a tool's text.
Thanks again!

Brush is a bit of an odd beast. You're also correct that it's not documented well. The current version feels more like a work-in-progress prototype, and it's actually getting a decent overhaul in the coming months. That being said, it's likely a better candidate for what you're trying to accomplish. Both in it's current form, and it's upcoming one.

there is an error, you have to use 'brush' instead of 'Brush'

Good catch. I'll need to double check with @JamesAPetts that this is fixed in the rewrite.

tool state, it brings hundreds of thousands of arrays with value 0, so I don't really now what this represents.

The brush tool's data is really just an array of "pixels", where 0 indicates that there is no brush data at that position. This is similar-ish to how we render the pixelData for each image.

after activating the BrushTool, it makes the whole canvas in a state that it is constantly updating

This is caused by the brush tool's "cursor". You'll notice the red circle that travels with your mouse as it moved. When a tool with cursors is enabled, or if cursors are enabled globally, the canvas must re-render on mouseMove to show the updated cursor.
This is the advantage of native or SVG cursors, as they don't require us to force a re-render.

I don't know how to specify the brush tool an X and Y coordinate to paint to

The brush data is a 1D array of pixels. If your reference image is 512x512,  index 0 would map to the top left pixel of your image, and 262,144 (512 rows * 512 cols - 1 offset for 0-index) would map to the bottom right pixel of your image. You can find the position of the corresponding pixel in the array using x (your column) and y (your row).
It's a bit late for me and I'm saying the bulk of this from memory, so it may not all be 100% accurate, but it should be close. If you need me to expand on anything, please don't hesitate to reach out.

Hey @dannyrb, thanks again for your response.
This helps me a lot, I think now I understand how this tool works. It is very clear and I thank you for the detailed explanation. I have just two more question to finish this thought:

In case I use the BrushTool. How could I deactivate the cursor so I don't have this re-render stuff on mouse move? For me this is very important as the application I am building has a lot of processes and stuff that already makes it heavy, and this re-render makes it work slow and this completely destroys the UX I'm trying to keep. Is this something I can do?
In case I decided to keep the ProbeTool, did you have the chance to check if there is already an option to hide the text? Maybe for this particular case I'd stick with the BrushTool, but this hidden text would make other processes I have in mind a lot easier for the eye without this text.

Thanks again! :)

How could I deactivate the cursor?

I don't know that you can. We need some way to show you the size and placement of the brush for when you interact with the canvas. We've looked at SVG cursors, but providing an SVG to the browser hits a dimension limitation that we often need to surpass. We could add an "SVG layer" for rendering things like this that don't trigger canvas re-renders, but that would be far-future.
If you have other logic that fires on re-render, you may want to look into throttle, which is notably different from debounce, or finding a different hook/event to leverage.

is already an option to hide the text?

Here is where the probe tool renders its text boxes. You could update the render method to use a new property on the tool's options to conditionally render them. This would require a PR, but is one I would review.

Thanks for the information and the help. I will definitely work on a PR for this and then let you know.

Has anyone been able to hide annotation tool's cached stats and text like Area, Mean, and Std Dev?


fix(package): update inquirer-autocomplete-prompt to version 1.0.1

Closes #36

Pull Request Test Coverage Report for Build 153

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 88.571%

Totals

Change from base Build 152:
0.0%

Covered Lines:
27

Relevant Lines:
29

💛  - Coveralls


Provide higher-level self-typed traits for enumerations.

Use at Gawker has made it clear that people prefer to use traits rather than use EnumApi directly, e.g.
trait EnumAsString[Enum] { self: EnumApi[Enum] =>
  def asString(e : Enum) : String = asStringImpl(e)
}

Especially when combined with implicit wrapper classes, this really reduces boilerplate. Instead of redefining these all the time it would be better to add them into Macramé. I should also finally get around to publishing macrame-play and macrame-slick.

Doobie also looks interesting so probably a macrame-doobie too once I look into that more.

Adding to this list macrame-scalaz which implements scalaz.Enum.


Add meta to rejected action

I think it is necessary to pass meta informations to rejected aciton. It is not against FSA standart

Thanks!

This has been released as<EMAIL_ADDRESS>


chore: generation paths are fully dynamic & supports --flat for compo…

…nents/directives/pipes/services
This is a step in aligning with the style guide and will provide the flexibility needed
Related to #316

Nice!


how to save a png with alpha channel?

how to save a png with alpha channel?

Idk. Ask Google. The outputs are numpy arrays.


'shisubeshi' doesn't work

Fixed spell definition in spells.csv

Reopening.  Saw an exception.
Traceback (most recent call last):        ^                                  ^
File "/home/achiwa/py/dl/dl.py", line 5101, in
main()
File "/home/achiwa/py/dl/dl.py", line 5097, in main
dispatch(game)
File "/home/achiwa/py/dl/dl.py", line 5071, in dispatch
maze(game)
File "/home/achiwa/py/dl/dl.py", line 4945, in maze
game.battle.battle()
File "/home/achiwa/py/dl/dl.py", line 3493, in battle
self.game.spell.cast_spell_dispatch(
File "/home/achiwa/py/dl/dl.py", line 1626, in cast_spell_dispatch
self.attack(invoker, spell, target)
File "/home/achiwa/py/dl/dl.py", line 1937, in attack
self.death_single(target, disptarget)
File "/home/achiwa/py/dl/dl.py", line 1858, in death_single
regdeathp = (target.stat[3] + target.stat[5]) * 100//40
AttributeError: 'Monstergrp' object has no attribute 'stat'

Fixed.  Will be in the next push.


In place transposition for Matrix (and MatrixSliceMut)

We currently have a transpose(&self) -> Matrix<T> method. It would be nice if we could do this operation in place, i.e. in_place_transpose(&mut self).
We can achieve this by swapping places in the data. We could do this fairly easily by utilizing the existing slice::swap method. This is acceptable but will include unnecessary bound checking, to speed things up we could use the underlying technique from that swap method:
unsafe {
    let pa: *mut T = self.get_unchecked_mut(i);
    let pb: *mut T = self.get_unchecked_mut(j);
    ptr::swap(pa, pb);
}

It would be nice to have this method in place for both Matrix and MatrixSliceMut. The Matrix implementation could simply call self.as_mut_slice().in_place_transpose().
To resolve this issue

In place transposition for square Matrix.
In place transposition for square MatrixSliceMut.
Tests for both.

Bonus points

Using ptr::swap to avoid bounds checking.
Explore vectorization and cache-line utilization.
Explore more advanced techniques.
Use permutations to transpose non-square matrices.

This issue was moved to AtheMathmo/rulinalg#2


[Feature Request] When ACL is applied to a subnet, affects ACL rules based on security groups, such as pg group？

Description
Q1: VM1-->PG-x->Subnet-->VM2
If the ACL of the PG is rejected, the rule priority is low, but the ACL rule of the subnet is allowed to be moved and the rule priority is high, and the final action should be to reject the ACL on the PG instead of the highest priority
Q2: VM1<-x-PG<--Subnet<--VM2
If the ACL of the subnet is rejected, the rule priority is low, but the ACL rule of the PG is allowed to be moved and the rule has a high priority, and the final action should be to reject the ACL on the PG instead of the one with the highest priority
Who will benefit from this feature?
No response
Anything else?
No response

@BigCousin-z could  you please describe the feature in detail?  How do you use the feature after finishing it?


SentryError: An event processor returned null, will not send event.

Versions + Platform

[x] SDK version -<EMAIL_ADDRESS>[x] Electron version -<EMAIL_ADDRESS>[x] Platform - macOS

Description
webPreferences: {
      minimumFontSize,
      nodeIntegration: false,
      contextIsolation: true,
      preload: __dirname + '/preload.js',
}

In the main process
import * as Sentry from '@sentry/electron/main'
Sentry.init({
    dsn: 'xxxx',
})
setTimeout(() => {
  throw new Error('Some main error5678')
}, 5000)

in the proload.js
import "@sentry/electron/preload";

in the renderer process
import * as Sentry from '@sentry/electron/renderer'
Sentry.init({ debug: true })

setTimeout(() => {
  throw new Error('Some renderer error999')
}, 10000)

main log info

renderer log info

Result
'Some main error5678' report to Sentry, But 'Some renderer error999' can't report to Sentry

I'm going to close this since An event processor returned null is expected in the renderer since events are intercepted and send via the main process.
Please open further issues for any other problems!


Update documentation generation

Documentation should be easier to update, and using different pipeline
for this step seems to be a better choice than the old one.
I added ember-cli-yuidoc and an npm script to allow easy generation.
As for the theme, I choose to use yuidoc-ember-cli-theme used for the
ember-cli API documentation.
I also think there is no need to split code and documentation. They can
both coexist in the same branch, and documentation will be versioned with
the code. The only side-effect is to configure this repository to use
the docs directory for GitHub pages.

Ah nice, I didn't know about documentation.js.
Since GitHub renders markdown pretty properly, this looks like a pretty good alternative. This addon doesn't have too many files so I doubt it will ever be a problem, but do you know how well linking across files is managed?

but do you know how well linking across files is managed?

not sure what you mean 🤔
I think you can just use regular markdown links in the doc comments if you want to link to somewhere else.

Should I retire this PR in favor of an issue to revamp the documentation?

feel free to keep it open for now until we have an alternative


Does not work with Vite and incorrectly spelled functions in production build

When I try to import this package with Vite, I get the following error:

[plugin:vite:import-analysis] Failed to resolve entry for package "rangee". The package may have incorrect
main/module/exports specified in its package.json: Failed to resolve entry for package "rangee". The package may have
incorrect main/module/exports specified in its package.json.

Here's the patch that would fix  this issue:
diff --git a/node_modules/rangee/index.d.ts b/node_modules/rangee/index.d.ts
index cfce791..45d1e27 100644
--- a/node_modules/rangee/index.d.ts
+++ b/node_modules/rangee/index.d.ts
@@ -9,7 +9,7 @@ export declare class Rangee {
     onSerialization: (callback: (serialized: string) => void) => (serialized: string) => void;
     onCompression: (callback: (compressed: Uint8Array) => void) => (compressed: Uint8Array) => void;
     serializeAtomic: (range: Range) => string;
-    deserilaizeAtomic: (representation: string) => Range[];
+    deserializeAtomic: (representation: string) => Range[];
     serialize: (range: Range) => string;
     deserialize: (serialized: string) => Range;
     createAtomicRanges: (range: Range) => Range[];
diff --git a/node_modules/rangee/index.js b/node_modules/rangee/index.js
index 3ad8598..773411b 100644
--- a/node_modules/rangee/index.js
+++ b/node_modules/rangee/index.js
@@ -23,7 +23,7 @@ var Rangee = /** @class */ (function () {
             var encoded = RangeEncoder_1.encode(compressed);
             return encoded;
         };
-        this.deserilaizeAtomic = function (representation) {
+        this.deserializeAtomic = function (representation) {
             var decoded = RangeEncoder_1.decode(representation);
             var decompressed = RangeCompressor_1.decompress(decoded);
             var serializedRanges = decompressed
diff --git a/node_modules/rangee/package.json b/node_modules/rangee/package.json
index c6e7a10..5ecee77 100644
--- a/node_modules/rangee/package.json
+++ b/node_modules/rangee/package.json
@@ -2,8 +2,8 @@
   "name": "rangee",
   "version": "1.1.7",
   "description": "Serialize/deserialize Range in HTML.",
-  "main": "dist/index.js",
-  "types": "dist/index.d.ts",
+  "main": "./index.js",
+  "types": "./index.d.ts",
   "scripts": {
     "compile": "tsc --build tsconfig.json",
     "copy": "copy package.json dist"

Hi @vedantroy I just published new reworked version. Let me know if the issue you got persist. Thanks.


Initial position for confetti

Is it possible to have the confetti drop in from the top when starting? Calling startConfetti() right now just shows a screen with a lot of confetti in random positions, which is pretty jarring. New confetti appear from the top after that, so it would be cool if they initially had the same origin.

Okay I did some digging around and turns out if you modify the lifetime of the emitter and not the birthrate for starting and stopping, this behaves as I’m proposing.

It is possible, just set  emitter.emitterShape = kCAEmitterLayerLine and confetti will start drop from the top.

For me the solution was adding
    emitter.beginTime = CACurrentMediaTime();

to the startConfetti() method

For me after adding emitter.beginTime = CACurrentMediaTime();animation started behave really weird and working one in three/five times. In general, it seems bug by Apple, because before iOS 7 emitter was always starting from the initial position.


Currently pinocchio::impulseDynamics allocates internally memory, do not use it for multithreading

In GitLab by @cmastalli on Nov 9, 2019, 11:14
I have been working on #271, and I noticed that part of the non-deterministic behavior of the solver is that pinoccho::impulseDynamics allocates internally memory, and I reported it few weeks ago: https://github.com/stack-of-tasks/pinocchio/issues/881.
@wxmerkt and @proyan be aware of it, and do not waste your time.
For more elaborate discussion, I suggest to use the Pinocchio issue.

In GitLab by @cmastalli on Nov 9, 2019, 11:15
changed title from Currently {-impulse d-}ynamics creates interally memory, do not use for multithreading to Currently {+pinocchio::impulseD+}ynamics creates interally memory, do not use for multithreading

In GitLab by @cmastalli on Nov 9, 2019, 11:16
changed title from Currently pinocchio::impulseDynamics {-creates interally memory, do not use-} for multithreading to Currently pinocchio::impulseDynamics {+allocates internally memory, do not use it+} for multithreading

In GitLab by @cmastalli on Nov 9, 2019, 11:16
changed the description

In GitLab by @wxmerkt on Nov 9, 2019, 11:22
Thank you for the note, I wasn't aware of the upstream issue. It did already waste quite a lot of time.

In GitLab by @proyan on Nov 9, 2019, 18:14
Cool! Good work Carlos

solved in #765


Replace fandom references with new wiki

Objective

Replace references to the old Fandom wiki with the new wiki. See here for details

Solution

Replace references to the old Fandom wiki with the new wiki

this has not been updated on the docs.rs page yet, might aswell add it too


[BUG] Identify and access > Accounts - first and last name are not shown in the grid

Describe the bug
Identify and access > Accounts - first and last name are not shown in the grid
To Reproduce
Steps to reproduce the behavior:

Go to 'Identify and access > Accounts' and create a new account, entering first/last name.
Click on 'Refresh' and look at the newly created account

Expected behavior
First and last name should be visible in the grid.
Screenshots
None
Desktop (please complete the following information):

OS: Windows 10 Pro x64
Browser: Chrome
Version: 80.0.3987.116 (Official Build) (64-bit)

Additional context
I see in the JSON response that the backend is sending this information, we need to show it on the screen.

According to old UI, we should not show first/last name for accounts but only for users:

@vladimirpetrov can you test latest master and verify/close this?

Confirmed, closing the issue.