init file update to support docker latest versions

Summary
Init file ./scripts/init.sh will not work with docker-compose version greater than 2.0, made changes to make it compatible with latest docker-compose version
Tests
Ran init script with docker-compose versions greater than and less than 2.0
cc:
@tommydangerous

👀👀👀

Can you make the same changes to the ./scripts/dev.sh file too please?

Can you make the same changes to the ./scripts/dev.sh file too please?
@tommydangerous updated ./scripts/dev.sh


Activate "Publish: no"

The Sample Community is displaying even though  "Publish: no" metadata is in place. BSSw plans on including unpublished content widely — for use as templates for their contributors. Can this function be activated in site content?

Should be active already - if this doesn't seem to be working, please let me know examples.

Oh whoops, just noticed you cited "Community." Should be active for resources, and I'll get on it for other types.

For this to work correctly we will also need "Publish: yes" in the metadata for the communities that are to be displayed.

Fixed; commit 5d9dda726a930c1eb850de2eae33cbd398688a3f

Ok, this should be working now!


Test that http2 settings frames with small max frame sizes are treated as errors

The test will need to be enabled for the auto run interop suite once #4233 is fixed.
Longer term, this will need to be a dashboard, rather than a full pass fail kind of test.

The interop tests have failed. Also, can you please squash the commits (the commit message "blah" is not very useful)?

Squashing before submitting is SOP no?

I believe it's SOP for grpc-java for grpc repo we don't enforce that.

I restarted the tests.

LGTM, thanks!


Adds support for NordicLargeAppbar

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


Ontology 2.0

TODO - to be specified by @geloro94.
Includes all the changes neccessary to support the fdpg+ ontology 2.0

To have a more flexible and scalable version of the ontology future versions will no longer be based on a JSON file. Instead, a db is employed that normalizes the repeating information.
Further, the latest version of the Ontology utilizes a "context" which is a TermCode Object (system, code, version, display) to make the combination of TermCode and context unique for each criterion. This is necessary as TermCodes on their own are not sufficient for the unique specification of a concept. For example, the code for heart attack can be a diagnosis or a cause of death.

The image pictures the db schema.
In https://github.com/medizininformatik-initiative/fhir-ontology-generator/blob/ontology-v2/database/DataBaseWriter.py you can find the SQL statements that create said schema. Verify the correctness and check if adjustments are required.
The goal is to generate a DB export that can be loaded by the backend. And in the future provides all information for the front end.
Once the schema and the DB export are provided adjust the API between the front and back end to send the UI-Tree instead of the current UI-Profile Json. Adjust the API https://feasibility.forschen-fuer-gesundheit.de/api/v2/terminology/ui_profile? to also use the context as a parameter: context_system, context_code, context_version.

My suggestion would be to change the db to the following:
CREATE TABLE IF NOT EXISTS termcode
(
    id      SERIAL PRIMARY KEY,
    system  TEXT NOT NULL,
    code    TEXT NOT NULL,
    version TEXT,
    UNIQUE (system, code, version),
    display TEXT NOT NULL
);

CREATE TABLE IF NOT EXISTS UI_PROFILE
(
    id      TEXT PRIMARY KEY,
    content JSON NOT NULL
);

CREATE TABLE IF NOT EXISTS CONTEXT
(
    id      SERIAL PRIMARY KEY,
    system  TEXT NOT NULL,
    code    TEXT NOT NULL,
    version TEXT,
    UNIQUE (system, code, version),
    display TEXT NOT NULL
);

CREATE TABLE IF NOT EXISTS CONTEXTUALIZED_CONCEPT_TO_UI_PROFILE
(
    context_id  INTEGER NOT NULL,
    termcode_id INTEGER NOT NULL,
    profile_id  TEXT    NOT NULL,
    CONSTRAINT CONTEXT_ID_FK FOREIGN KEY (context_id)
        REFERENCES CONTEXT (id) ON DELETE CASCADE,
    CONSTRAINT CONCEPT_ID_FK FOREIGN KEY (termcode_id)
        REFERENCES termcode (id) ON DELETE CASCADE,
    CONSTRAINT profile_id_FK FOREIGN KEY (profile_id) REFERENCES UI_PROFILE (id) ON DELETE CASCADE
);

CREATE TABLE IF NOT EXISTS MAPPING
(
    id      SERIAL PRIMARY KEY,
    name    TEXT NOT NULL,
    type    TEXT NOT NULL,
    UNIQUE (name, type),
    content JSON NOT NULL
);

CREATE TABLE IF NOT EXISTS CONTEXTUALIZED_CONCEPT_TO_MAPPING
(
    context_id  INTEGER NOT NULL,
    termcode_id INTEGER NOT NULL,
    mapping_id  INTEGER NOT NULL,
    CONSTRAINT CONTEXT_ID_FK FOREIGN KEY (context_id)
        REFERENCES CONTEXT (id) ON DELETE CASCADE,
    CONSTRAINT CONCEPT_ID_FK FOREIGN KEY (termcode_id)
        REFERENCES termcode (id) ON DELETE CASCADE,
    CONSTRAINT MAPPING_ID_FK FOREIGN KEY (mapping_id)
        REFERENCES MAPPING (id) ON DELETE CASCADE
);

CREATE TABLE IF NOT EXISTS VALUE_SET
(
    canonical_url TEXT NOT NULL,
    system        TEXT NOT NULL,
    code          TEXT NOT NULL,
    version       TEXT,
    PRIMARY KEY (canonical_url, system, code, version)
);

CREATE INDEX idx_mapping_name_mapping ON MAPPING (name);
CREATE INDEX idx_mapping_name_contextualized ON CONTEXTUALIZED_CONCEPT_TO_MAPPING (mapping_id);

which results in

This mostly adds some surrogate keys. I personally would also prefer adding one to the value_set table, but since this is not related to any other tables, I'm fine with leaving it as is.
I also changed some names in a way I found more suitable.

After further discussion, the value_set table shall be as follows:
    CREATE TABLE IF NOT EXISTS VALUE_SET(
    id SERIAL PRIMARY KEY,
    canonical_url TEXT NOT NULL,
    system TEXT NOT NULL,
    code TEXT NOT NULL,
    version TEXT,
    unique NULLS NOT DISTINCT (canonical_url, system, code, version)
    );

After further discussion, the db was changed to:
CREATE TABLE IF NOT EXISTS termcode
(
    id      SERIAL PRIMARY KEY,
    system  TEXT NOT NULL,
    code    TEXT NOT NULL,
    version TEXT,
    unique nulls not DISTINCT (system, code, version),
    display TEXT NOT NULL
);

CREATE TABLE IF NOT EXISTS UI_PROFILE
(
    id      TEXT PRIMARY KEY,
    content JSON NOT NULL
);

CREATE TABLE IF NOT EXISTS CONTEXT
(
    id      SERIAL PRIMARY KEY,
    system  TEXT NOT NULL,
    code    TEXT NOT NULL,
    version TEXT,
    unique nulls not DISTINCT (system, code, version),
    display TEXT NOT NULL
);

CREATE TABLE IF NOT EXISTS CONTEXTUALIZED_CONCEPT_TO_UI_PROFILE
(
    context_id  INTEGER NOT NULL,
    termcode_id INTEGER NOT NULL,
    profile_id  TEXT    NOT NULL,
    CONSTRAINT CONTEXT_ID_FK FOREIGN KEY (context_id)
        REFERENCES CONTEXT (id) ON DELETE CASCADE,
    CONSTRAINT CONCEPT_ID_FK FOREIGN KEY (termcode_id)
        REFERENCES termcode (id) ON DELETE CASCADE,
    CONSTRAINT profile_id_FK FOREIGN KEY (profile_id) REFERENCES UI_PROFILE (id) ON DELETE CASCADE
);

CREATE TABLE IF NOT EXISTS MAPPING
(
    id      SERIAL PRIMARY KEY,
    name    TEXT NOT NULL,
    type    TEXT NOT NULL,
    UNIQUE (name, type),
    content JSON NOT NULL
);

CREATE TABLE IF NOT EXISTS CONTEXTUALIZED_CONCEPT_TO_MAPPING
(
    context_id  INTEGER NOT NULL,
    termcode_id INTEGER NOT NULL,
    mapping_id  INTEGER NOT NULL,
    CONSTRAINT CONTEXT_ID_FK FOREIGN KEY (context_id)
        REFERENCES CONTEXT (id) ON DELETE CASCADE,
    CONSTRAINT CONCEPT_ID_FK FOREIGN KEY (termcode_id)
        REFERENCES termcode (id) ON DELETE CASCADE,
    CONSTRAINT MAPPING_ID_FK FOREIGN KEY (mapping_id)
        REFERENCES MAPPING (id) ON DELETE CASCADE
);

CREATE TABLE IF NOT EXISTS VALUE_SET
(
    id            serial primary key,
    canonical_url TEXT NOT NULL,
    system        TEXT NOT NULL,
    code          TEXT NOT NULL,
    version       TEXT,
    unique nulls not distinct (canonical_url, system, code, version)
);

CREATE INDEX idx_mapping_name_mapping ON MAPPING (name);
CREATE INDEX idx_mapping_name_contextualized ON CONTEXTUALIZED_CONCEPT_TO_MAPPING (mapping_id);

CREATE TABLE IF NOT EXISTS foo
(
    id            serial primary key,
    canonical_url TEXT NOT NULL,
    system        TEXT NOT NULL,
    code          TEXT NOT NULL,
    version       TEXT,
    unique (canonical_url, system, code, version)
);

Another slight change to the DDL script - adding indexes to the FK columns referencing termcode.id in CONTEXTUALIZED_CONCEPT_TO_UI_PROFILE and CONTEXTUALIZED_CONCEPT_TO_MAPPING
CREATE TABLE IF NOT EXISTS termcode
(
    id      SERIAL PRIMARY KEY,
    system  TEXT NOT NULL,
    code    TEXT NOT NULL,
    version TEXT,
    unique nulls not DISTINCT (system, code, version),
    display TEXT NOT NULL
);

CREATE TABLE IF NOT EXISTS UI_PROFILE
(
    id         TEXT PRIMARY KEY,
    ui_profile JSON NOT NULL
);

CREATE TABLE IF NOT EXISTS CONTEXT
(
    id      SERIAL PRIMARY KEY,
    system  TEXT NOT NULL,
    code    TEXT NOT NULL,
    version TEXT,
    unique nulls not DISTINCT (system, code, version),
    display TEXT NOT NULL
);

CREATE TABLE IF NOT EXISTS CONTEXTUALIZED_CONCEPT_TO_UI_PROFILE
(
    context_id  INTEGER NOT NULL,
    termcode_id INTEGER NOT NULL,
    profile_id  TEXT    NOT NULL,
    CONSTRAINT CONTEXT_ID_FK FOREIGN KEY (context_id)
        REFERENCES CONTEXT (id) ON DELETE CASCADE,
    CONSTRAINT CONCEPT_ID_FK FOREIGN KEY (termcode_id)
        REFERENCES termcode (id) ON DELETE CASCADE,
    CONSTRAINT profile_id_FK FOREIGN KEY (profile_id) REFERENCES UI_PROFILE (id) ON DELETE CASCADE
);

CREATE TABLE IF NOT EXISTS MAPPING
(
    id      SERIAL PRIMARY KEY,
    name    TEXT NOT NULL,
    type    TEXT NOT NULL,
    UNIQUE (name, type),
    content JSON NOT NULL
);

CREATE TABLE IF NOT EXISTS CONTEXTUALIZED_CONCEPT_TO_MAPPING
(
    context_id  INTEGER NOT NULL,
    termcode_id INTEGER NOT NULL,
    mapping_id  INTEGER NOT NULL,
    CONSTRAINT CONTEXT_ID_FK FOREIGN KEY (context_id)
        REFERENCES CONTEXT (id) ON DELETE CASCADE,
    CONSTRAINT CONCEPT_ID_FK FOREIGN KEY (termcode_id)
        REFERENCES termcode (id) ON DELETE CASCADE,
    CONSTRAINT MAPPING_ID_FK FOREIGN KEY (mapping_id)
        REFERENCES MAPPING (id) ON DELETE CASCADE
);

CREATE TABLE IF NOT EXISTS VALUE_SET
(
    id            serial primary key,
    canonical_url TEXT NOT NULL,
    system        TEXT NOT NULL,
    code          TEXT NOT NULL,
    version       TEXT,
    unique nulls not distinct (canonical_url, system, code, version)
);

CREATE INDEX idx_mapping_name_mapping ON MAPPING (name);
CREATE INDEX idx_mapping_name_contextualized ON CONTEXTUALIZED_CONCEPT_TO_MAPPING (mapping_id);
CREATE INDEX idx_concept_to_mapping_termcode_fk ON CONTEXTUALIZED_CONCEPT_TO_MAPPING (termcode_id);
CREATE INDEX idx_concept_to_uiprofile_termcode_fk ON CONTEXTUALIZED_CONCEPT_TO_UI_PROFILE (termcode_id);

As there are ongoing discussion whether to change the value_set table, as a base for further discussion. (Please note that the name of the table "value_set" should probably change as well, which is not yet reflected in this post for a lack of a good name)

CREATE TABLE IF NOT EXISTS termcode
(
    id      SERIAL PRIMARY KEY,
    system  TEXT NOT NULL,
    code    TEXT NOT NULL,
    version TEXT,
    unique nulls not DISTINCT (system, code, version),
    display TEXT NOT NULL
);

CREATE TABLE IF NOT EXISTS UI_PROFILE
(
    id         TEXT PRIMARY KEY,
    ui_profile JSON NOT NULL
);

CREATE TABLE IF NOT EXISTS CONTEXT
(
    id      SERIAL PRIMARY KEY,
    system  TEXT NOT NULL,
    code    TEXT NOT NULL,
    version TEXT,
    unique nulls not DISTINCT (system, code, version),
    display TEXT NOT NULL
);

CREATE TABLE IF NOT EXISTS CONTEXTUALIZED_CONCEPT_TO_UI_PROFILE
(
    context_id  INTEGER NOT NULL,
    termcode_id INTEGER NOT NULL,
    profile_id  TEXT    NOT NULL,
    CONSTRAINT CONTEXT_ID_FK FOREIGN KEY (context_id)
        REFERENCES CONTEXT (id) ON DELETE CASCADE,
    CONSTRAINT CONCEPT_ID_FK FOREIGN KEY (termcode_id)
        REFERENCES termcode (id) ON DELETE CASCADE,
    CONSTRAINT profile_id_FK FOREIGN KEY (profile_id) REFERENCES UI_PROFILE (id) ON DELETE CASCADE
);

CREATE TABLE IF NOT EXISTS MAPPING
(
    id      SERIAL PRIMARY KEY,
    name    TEXT NOT NULL,
    type    TEXT NOT NULL,
    UNIQUE (name, type),
    content JSON NOT NULL
);

CREATE TABLE IF NOT EXISTS CONTEXTUALIZED_CONCEPT_TO_MAPPING
(
    context_id  INTEGER NOT NULL,
    termcode_id INTEGER NOT NULL,
    mapping_id  INTEGER NOT NULL,
    CONSTRAINT CONTEXT_ID_FK FOREIGN KEY (context_id)
        REFERENCES CONTEXT (id) ON DELETE CASCADE,
    CONSTRAINT CONCEPT_ID_FK FOREIGN KEY (termcode_id)
        REFERENCES termcode (id) ON DELETE CASCADE,
    CONSTRAINT MAPPING_ID_FK FOREIGN KEY (mapping_id)
        REFERENCES MAPPING (id) ON DELETE CASCADE
);

CREATE TABLE IF NOT EXISTS canonical_url
(
    id  SERIAL PRIMARY KEY,
    url TEXT UNIQUE NOT NULL
);

CREATE TABLE IF NOT EXISTS VALUE_SET
(
    id               SERIAL PRIMARY KEY,
    canonical_url_id INTEGER NOT NULL,
    termcode_id      INTEGER NOT NULL,
    constraint CANONICAL_URL_ID_FK foreign key (canonical_url_id)
        references canonical_url (id) on delete cascade,
    constraint TERMCODE_ID_FK foreign key (termcode_id)
        references termcode (id) on
            delete cascade
);

CREATE INDEX idx_mapping_name_mapping ON MAPPING (name);
CREATE INDEX idx_mapping_name_contextualized ON CONTEXTUALIZED_CONCEPT_TO_MAPPING (mapping_id);
CREATE INDEX idx_concept_to_mapping_termcode_fk ON CONTEXTUALIZED_CONCEPT_TO_MAPPING (termcode_id);
CREATE INDEX idx_concept_to_uiprofile_termcode_fk ON CONTEXTUALIZED_CONCEPT_TO_UI_PROFILE (termcode_id);
create index idx_value_set_termcode_fk on VALUE_SET (termcode_id);

After another review, the following schema is agreed upon.
CREATE TABLE IF NOT EXISTS termcode
(
    id      SERIAL PRIMARY KEY,
    system  TEXT NOT NULL,
    code    TEXT NOT NULL,
    version TEXT,
    unique nulls not DISTINCT (system, code, version),
    display TEXT NOT NULL
);

CREATE TABLE IF NOT EXISTS ui_profile
(
    id         SERIAL PRIMARY KEY,
    name       TEXT NOT NULL,
    ui_profile JSON NOT NULL
);

CREATE TABLE IF NOT EXISTS context
(
    id      SERIAL PRIMARY KEY,
    system  TEXT NOT NULL,
    code    TEXT NOT NULL,
    version TEXT,
    UNIQUE NULLS NOT DISTINCT (system, code, version),
    display TEXT NOT NULL
);

CREATE TABLE IF NOT EXISTS mapping
(
    id      SERIAL PRIMARY KEY,
    name    TEXT NOT NULL,
    type    TEXT NOT NULL,
    UNIQUE (name, type),
    content JSON NOT NULL
);

CREATE TABLE IF NOT EXISTS contextualized_termcode
(
    context_termcode_hash TEXT PRIMARY KEY,
    context_id            INTEGER NOT NULL,
    termcode_id           INTEGER NOT NULL,
    mapping_id            INTEGER,
    ui_profile_id         INTEGER,
    CONSTRAINT CONTEXT_ID_FK FOREIGN KEY (context_id)
        REFERENCES CONTEXT (id) ON DELETE CASCADE,
    CONSTRAINT CONCEPT_ID_FK FOREIGN KEY (termcode_id)
        REFERENCES termcode (id) ON DELETE CASCADE,
    CONSTRAINT mapping_id_fk FOREIGN KEY (mapping_id)
        REFERENCES mapping (id),
    CONSTRAINT ui_profile_id_fk FOREIGN KEY (ui_profile_id)
        REFERENCES ui_profile (id),
    UNIQUE (context_id, termcode_id)
);

CREATE TABLE IF NOT EXISTS contextualized_value_set
(
    id  SERIAL PRIMARY KEY,
    url TEXT UNIQUE NOT NULL
);

CREATE TABLE IF NOT EXISTS contextualized_termcode_to_contextualized_value_set
(
    context_termcode_hash       TEXT    NOT NULL,
    contextualized_value_set_id INTEGER NOT NULL,
    UNIQUE (context_termcode_hash, contextualized_value_set_id),
    CONSTRAINT CONTEXTUALIZED_VALUE_SET_ID_FK FOREIGN KEY (contextualized_value_set_id)
        REFERENCES CONTEXTUALIZED_VALUE_SET (id) ON DELETE CASCADE ,
    CONSTRAINT CONTEXTUALIZED_TERMCODE_ID_FK FOREIGN KEY (context_termcode_hash)
        REFERENCES CONTEXTUALIZED_TERMCODE (context_termcode_hash) ON DELETE CASCADE
);

CREATE INDEX idx_mapping_name_mapping ON mapping (name);
CREATE INDEX idx_contextualized_termcode_termcode_fk ON contextualized_termcode (termcode_id);

COMMENT ON COLUMN contextualized_termcode.context_termcode_hash IS 'This value is hashed using UUID-V3 (MD5) from the concatenated string of (context.system, context.code, context.version, termcode.system, termcode.code, termcode.version), omitting null values for version and without any delimiters.';

Resulting in:

Please be aware that if you previously started the backend with the associated branch, leading to the execution of the versioned sql script, you MUST delete the previously added tables manually AND remove the entry from the flyway table (`delete from flyway_schema_history where version = #7')

Thanks for noticing - I'll add it in the sql script


Wordpress boilerplate

set up Wordpress example with simple documentation

@foxyq is there any progress?

Changed the scripts mis-spelling, explained the build and manual copy instructions in comment.
Added (in progress) files for initializing CLI.


Filling in EuropeEastGrid

Fill in EuropeEastGrid in Core/ostrat.pEarth.EuropeEast.scala. Hopefully should be self explanatory.

Done!


influxd should use the logging config

Fixed by https://github.com/influxdb/influxdb/commit/3680b8769e72c9fee0eae757c20b734217db621d


PDF Format of Repor

Is your feature request related to a problem? Please describe.
As the current report is generated in html and with multiple folder which makes it harder to share it after zipping. the audiance also prefer have a single pdf file as replor.
Describe the solution you'd like
Conversion or generation of PDF version of the html report.

This is more like a question from you to see any possiblity.

Cluecumber is meant to be an HTML reporting library so PDF support is not planned as of now. You can probably use command line tools in your pipeline to achieve that, e.g. wkhtmltopdf


Properties Missing From Prototype chain

Hi, me again!
Thanks for sorting the last bug quickly.  I've come across another issue.  Not sure if this is a bug or I've done something wrong.  I'm leaning more towards bug.
I have this set up -
import jsep from 'jsep';
import jsepObject from '@jsep-plugin/object';
import jsepNew from '@jsep-plugin/new';
import {
  parse,
  evaluate as safeEval,
} from 'jse-eval';

jsep.plugins.register(jsepObject);
jsep.plugins.register(jsepNew);

And I'm wanting to evaluate this -
yup.object({
  name: yup.string().required().label('Name')
})

Where I'm passing "yup" in as context.  So
    import * as yup from "yup";
    const javascript = "yup.object({ name: yup.string().required().label('Name')})";
    const parsed = parse(javascript);
    const context = { yup };
    const yupObject = safeEval(parsed, context);

My yup object is no good.  Upon inspection in the console it turns out the reason is the whole prototype chain is missing!
This is how it should look -

This is how it looks with the yupObject returned from jse-eval.

Does this point to a flaw / bug in the evaluator or am I set up wrongly?

Hi @rossmeredith ! I tried adding your sample code to a node app and then comparing direct code versus jse-eval and didn't see any difference, or any issues with trying to run validate on the built yup schema object. jse-eval doesn't coerce tyes and only has a check to guard against accessing the prototype from the expression, but that's not going on here. Maybe you can set up a more detailed example?

Hi
Thanks for the quick response.
Apologies, it turns out that something I thought irrelevant is the problem.  "Unflatten" from the popular library "flat" is strangely causing the problem.  An issue for them therefore.
Thanks


Create scorecards.yml

Add OpenSSF scorecard github code checker.
Signed-off-by: Michael Lieberman<EMAIL_ADDRESS>

closes #370

@mlieberman85 You need Signed-off-by: ... in each commit.

Ughh, forgot that editing in Github doesn't automatically add the DCO.


RBAC: Get rid of provider type in custom params

via https://github.com/provectus/kafka-ui/issues/3832
It seems like OAuth2Provider#provider is not quite populated to spring's structure (com/provectus/kafka/ui/config/auth/OAuthPropertiesConverter.java:22), thus, it seems it might be non-unique and used by us in favor of "type" in custom-params.

Hello everyone, please tell me how soon you plan to complete the task?
Thanks for the answer.


Rewrite the Scripts API module and use it in the CLI to support the new script language version

This makes a change similar to the one we made with addresses recently.
With addresses we identified that there are two independent dimensions:
the address type (i.e. Byron vs Shelley address), and the era in which
the address is valid.
With scripts the dimensions are the language, and the era in which the
language is supported. So with this change we can talk about script
languages independently of the era in which those languages are
supported. We also gain a type covering all language, irrespective of
era, which is useful as an intermediate type for converting from weakly
typed input (e.g. in the CLI) to the strongly-typed internal types.
Another advantage of splitting the dimensions this way is that it will
be easier to add new eras that inherit all the earlier languages,
especially if they do not add new eras themselves.
Though right now we only support the simple script language, structure
the types so that it is clear where to add Plutus once it arrives.
Update the CLI to use this. The effect is that it now supports the
appropriate languages in each era.

bors merge


Wrong description

Expected behavior
Description in payment details as set. In this case order nr
Actual behavior
It works allright with creditcard payments, but not with ideal. With ideal payments the description is mol_339461f9774c9a5xxxxxxx
Steps to reproduce the behavior
Make a payment with ideal and have {orderNumber} set in description with payment api. Works with creditcard, but not ideal. Same api, same setting
Environment

PrestaShop version: <IP_ADDRESS>
Mollie module version: 5.0.0
PHP version: 7.3.33

I also had the issue in 4.4.3.

Hi @pic16f876! I hope that you are doing well.
Thank you for your query. We appreciate your interest in perfecting the Mollie module!
I have forwarded the details to the developer to check it out. We will keep you updated about the progress.
Best regards,
Invertus Support team

Hi @pic16f876!
Could you let us know how your iDeal set up looks like in the Prestashop Back Office? A screenshot would be great and would help us investigate.
Looking forward to your reply!
Best regards,
Invertus Support team

I added ideal and cc settings

I Added both screenshots for ideal and creditcard

Thank you @pic16f876!
I have forwarded the following information to the developer to investigate further. We will keep you updated!
Best regards,
Invertus Support team

Hi there @pic16f876! Hope that you are well.
Our developer has checked the issue and has added validation in the Settings page to now allow to save only empty spaces. Along with that, a validation was added to check if generated description is not empty and space only, if it is, then it changes it to the order reference so that the issue would not appear again.
We have included the fix in our latest 5.0.0 release, you can find it right here.
We are looking forward to your questions or feedback!
Best regards,
Invertus Support team

Hi there @pic16f876! I hope that you are doing well.
Let us know once you're ready to continue with this!
For now, we will mark this issue as resolved.
Best regards,
Invertus Support team


Show human-readable timestamp for long-running commands

Second try of #21.
There is a weird coloring issue - maybe we should have different colors for git time vs long running time
long running -> white -> yellow -> red
git time -> green -> white -> red

Git time is supposed to be green -> white/yellow -> red. I don't have any particular opinion on the colors for the long running commands. Not sure if I understood the issue.

The color thing is a non-issue, I was just thinking about it weird

Now this is super weird, I am getting "normal" as the string display for time elapsed. gonna see what the deal is.

OK fixed a few bugs: the :: separator not working as described, and the actual display. Should be ready to merge now

Just merged! Thanks again!


render: disallow wlr_renderer_destroy while rendering

This probably already felt apart, but let's make it explicit that
this is not allowed.

LGTM


Provide a clearer error message when using dataframe.backend if dask_cudf is not installed

I was trying to use Dask's new configurable DataFrame backend:
import dask.dataframe as dd
dask.config.set({"dataframe.backend": "cudf"})

On attempting to read a Parquet file w/ dd.read_parquet, I stumbled on:
ValueError: No backend dispatch registered for cudf

It turns out this is because dask_cudf was missing from my environment. It might help users if the error message was less generic and suggested your environment might be missing or have an otherwise unusable package for the configured backend.

cc @rjzamora

Thanks for the issue @randerzander. Totally agree that there's room for improvement on the error message raised here. For others, here's a small example that reproduces the issue (when dask-cudf isn't installed)
In [1]: import dask

In [2]: import dask.dataframe as dd

In [3]: dask.config.set({"dataframe.backend": "cudf"})
Out[3]: <dask.config.set at 0x10834f100>

In [4]: dd.from_dict({"x": range(10)})
---------------------------------------------------------------------------
ValueError                                Traceback (most recent call last)
Input In [4], in <cell line: 1>()
----> 1 dd.from_dict({"x": range(10)})

File ~/projects/dask/dask/dask/backends.py:123, in CreationDispatch.register_inplace.<locals>.decorator.<locals>.wrapper(*args, **kwargs)
    121 @wraps(fn)
    122 def wrapper(*args, **kwargs):
--> 123     func = getattr(self, dispatch_name)
    124     try:
    125         return func(*args, **kwargs)

File ~/projects/dask/dask/dask/backends.py:142, in CreationDispatch.__getattr__(self, item)
    138 def __getattr__(self, item: str):
    139     """
    140     Return the appropriate attribute for the current backend
    141     """
--> 142     backend = self.dispatch(self.backend)
    143     return getattr(backend, item)

File ~/projects/dask/dask/dask/backends.py:91, in CreationDispatch.dispatch(self, backend)
     89 else:
     90     return impl
---> 91 raise ValueError(f"No backend dispatch registered for {backend}")

ValueError: No backend dispatch registered for cudf

cc @rjzamora whenever you get a chance to take a look at this (I suspect you're still digging out of a notification hole from the holidays 🙂 )

Yeah - I was experimenting with an improved error message yesterday (https://github.com/rjzamora/dask/tree/clearer-dispatch-error-message), but didn't get the chance to follow through just yet.


Request from a NON Firefox Quantum user

I decided not to upgrade to Firefox Quantum so I use the old https://addons.mozilla.org/en-US/firefox/addon/popup-video/ addon. It works great on the Firefox 52 ESR and on the Basilisk browser.
Still, there's one problem on youtube videos. The popup video icon hides youtube's "watch it later" icon.
Can you please release another version of the 'old" addon with an option to decide the icon location (top-right, top-center or top-left).
If not, can you instruct me how to change the code of the xpi (is it on the launch-video.js file ?) so the icon will be shown on the top-left of the thumbnail.
Thanks in advance.
Win 7 x64
Basilisk 2018.06.01 (32-bit)

Update version 0.0.9

First, thanks a lot @ettoolong for updating the Non Quantum version. I really appreciate it.
Just one problem. Version 0.0.9 suddenly removed the overlay icon for the thumbnails.
Win 7 x64
Basilisk 2018.06.01 (32-bit) & Firefox 52 ESR


Suggestion

This app is great! It would be awesome to be able to choose a minimalist output with just the units and loadouts so your list can be shared on Discord and Reddit.

Other apps, like BattleScribe, can output minimalist output. Do those suffice for your use case? I've used PrettyScribe as a way to generate printouts and shareable PDFs, and minimal outputs seems less in line with that esp when there are alternatives.

The original intent of PrettyScribe was to provide a tool that produced 'familiar-looking' printable reference outputs for 40k and other games.
Is there something in particular about the minimalist Battlescribe output you find lacking?


Protractor test is not starting on Firefox

I have got a set of test that run fine on chrome but when I change the capabilities browserName  from chrome to firefox don't even get a  error info
Before
capabilities: {
'browserName': 'chrome',
'chromeOptions': { args: ['--test-type', 'show-fps-counter=true'] }
},
//After
capabilities: {
'browserName': 'firefox'
},

When I run my protractor scripts on Firefox, firefox window is opened but failed to open the target URL and getting the following error:
sing FirefoxDriver directly...
[launcher] Running 1 instances of WebDriver
c:\node_modules\protractor\node_modules\selenium-webdriver\http\util.js:89
Error('Timed out waiting for the WebDriver server at ' + url));
^
Error: Timed out waiting for the WebDriver server at http://<IP_ADDRESS>:49587/hub
at Error (native)
at onResponse (c:\node_modules\protractor\node_modules\selenium-webdriver\http\util.js:89:11)
at c:\node_modules\protractor\node_modules\selenium-webdriver\http\util.js:44:21
at c:\node_modules\protractor\node_modules\selenium-webdriver\lib\webdriver\http\http.js:140:5
at ClientRequest. (c:\node_modules\protractor\node_modules\selenium-webdriver\http\index.js:174:7)
at emitOne (events.js:77:13)
at ClientRequest.emit (events.js:169:7)
at Socket.socketErrorListener (http_client.js:258:9)
at emitOne (events.js:77:13)
at Socket.emit (events.js:169:7)
From: Task: WebDriver.createSession()
at Function.webdriver.WebDriver.acquireSession (c:\node_modules\protractor\node_modules\selenium-webdriver\lib\webdriver\webdriver.js:157:22)
at Function.webdriver.WebDriver.createSession (c:\node_modules\protractor\node_modules\selenium-webdriver\lib\webdriver\webdriver.js:131:30)
at new Driver (c:\node_modules\protractor\node_modules\selenium-webdriver\firefox\index.js:278:36)
at [object Object].DirectDriverProvider.getNewDriver (c:\node_modules\protractor\lib\driverProviders\direct.js:74:16)
at [object Object].Runner.createBrowser (c:\node_modules\protractor\lib\runner.js:190:37)
at c:\node_modules\protractor\lib\runner.js:280:21
at _fulfilled (c:\node_modules\protractor\node_modules\q\q.js:834:54)
at self.promiseDispatch.done (c:\node_modules\protractor\node_modules\q\q.js:863:30)
at Promise.promise.promiseDispatch (c:\node_modules\protractor\node_modules\q\q.js:796:13)
at c:\node_modules\protractor\node_modules\q\q.js:556:49
[launcher] Process exited with error code 1
Process finished with exit code 1
Can someone please help me out with this?
Regards,
Naresh Surya

Hi @nareshsurya!
I recently encountered the same error as you. The quick fix solution for me was to uninstall Firefox 47 and downgrade to Firefox 36. You can find older versions of Firefox here: https://ftp.mozilla.org/pub/firefox/releases/
I'm using selenium-webdriver 2.47.0. I'm not sure what's the latest version of Firefox we can use, but just wanted to give you a quick fix at the moment! Perhaps someone can expand upon this!

@b-mcrae I love you!! I have been stumped on this for a few hours. My tests were working fine yesterday but when I ran them today they weren't. I guess Firefox updated somewhere in between.

Any solution to the last error? I am experiencing the same!

Protractor is running on Firefox
I am using FireFox v44.01, with following settings
capabilities: {
'browserName': 'chrome',
chromeOptions: {
args: ['disable-extensions']
}
,
"browserName": "firefox",
"firefox_binary": "C:/Program Files/Mozilla Firefox/firefox",
"binary_": "C:/Program Files/Mozilla Firefox/firefox"
},
and its running fine with Firefox.
before starting with Firefox, disable the auto update of Firefox.

What would be the equivalent of this on a mac?
"browserName": "firefox",
"firefox_binary": "C:/Program Files/Mozilla Firefox/firefox",
"binary_": "C:/Program Files/Mozilla Firefox/firefox"

I tried, but it didn't work
    firefox_binary: '../../../../../Applications/firefox_v34',
    binary_: '../../../../../Applications/firefox_v34',

Locate where an executable of firefox is coming from the filesystem and write the fullpath.
The way you wrote the path, it seems fuzzy. So search on internet for the binary location of firefox on mac
and fix your problem.

Mac OSX 10.10.5
Firefox 50.1
I'm having the same problem with Firefox not running any tests and timing out.  I'm following the protractor tutorial, and Step 3 asks me to add Firefox to conf.js:
// conf.js
exports.config = {
  framework: 'jasmine',
  seleniumAddress: 'http://localhost:4444/wd/hub',
  specs: ['spec.js'],
  capabilities: {
    browserName: 'firefox'
  }
}

Here is the output when I do $ webdriver-manager start:
~/protractor_programs$ webdriver-manager start
[06:39:49] I/start - java -Dwebdriver.chrome.driver=/Users/7stud/.nvm/versions/node/v7.4.0/lib/node_modules/protractor/node_modules/webdriver-manager/selenium/chromedriver_2.26 -Dwebdriver.gecko.driver=/Users/7stud/.nvm/versions/node/v7.4.0/lib/node_modules/protractor/node_modules/webdriver-manager/selenium/geckodriver-v0.12.0 -jar /Users/7stud/.nvm/versions/node/v7.4.0/lib/node_modules/protractor/node_modules/webdriver-manager/selenium/selenium-server-standalone-2.53.1.jar -port 4444
[06:39:49] I/start - seleniumProcess.pid: 63927
06:39:49.859 INFO - Launching a standalone Selenium Server
06:39:49.892 INFO - Java: Oracle Corporation 25.40-b25
06:39:49.893 INFO - OS: Mac OS X 10.10.5 x86_64
06:39:49.903 INFO - v2.53.1, with Core v2.53.1. Built from revision a36b8b1
06:39:49.977 INFO - Driver provider org.openqa.selenium.ie.InternetExplorerDriver registration is skipped:
registration capabilities Capabilities [{ensureCleanSession=true, browserName=internet explorer, version=, platform=WINDOWS}] does not match the current platform MAC
06:39:49.978 INFO - Driver provider org.openqa.selenium.edge.EdgeDriver registration is skipped:
registration capabilities Capabilities [{browserName=MicrosoftEdge, version=, platform=WINDOWS}] does not match the current platform MAC
06:39:49.978 INFO - Driver class not found: com.opera.core.systems.OperaDriver
06:39:49.978 INFO - Driver provider com.opera.core.systems.OperaDriver is not registered
06:39:49.980 INFO - Driver class not found: org.openqa.selenium.htmlunit.HtmlUnitDriver
06:39:49.980 INFO - Driver provider org.openqa.selenium.htmlunit.HtmlUnitDriver is not registered
06:39:50.045 INFO - RemoteWebDriver instances should connect to: http://<IP_ADDRESS>:4444/wd/hub
06:39:50.045 INFO - Selenium Server is up and running

Guys, I have clearly mentioned above Firefox browser v44.01.
Currently, Protractor supports Firefox browser till v44.0.1, do not use above version.
My test environment is Windows not MAC, so guys above settings are for Windows environment.

First install Firefox browser v44
Currently, Protractor supports Firefox browser till v44, do not use above
version.
My test environment is Windows not MAC, so guys above settings are for
Windows environment.
Might this will help as I don't have a MAC, I can support you theoretically.
framework: 'jasmine',
seleniumAddress: 'http://localhost:4444/wd/hub',
specs: ['spec.js'],
capabilities: {
browserName: 'firefox',
platform: 'MAC',
firefox_binary: '/Applications/Firefox.app/Contents/MacOS/firefox'
}
}
Thanks
Ajitabh Ranjan
Mob:<PHONE_NUMBER>
On Wed, Oct 12, 2016 at 3:02 AM, Kathy Ems<EMAIL_ADDRESS>wrote:

What would be the equivalent of this on a mac?
"browserName": "firefox",
"firefox_binary": "C:/Program Files/Mozilla Firefox/firefox",
"binary_": "C:/Program Files/Mozilla Firefox/firefox"
I tried, but it didn't work
firefox_binary: '../../../../../Applications/firefox_v34',
binary_: '../../../../../Applications/firefox_v34',

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/angular/protractor/issues/886#issuecomment-253053158,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AOad5yvZ_1t48QPR_OAbx03DjST9FBK5ks5qzAB4gaJpZM4CAL2g
.

First install Firefox browser v44
Currently, Protractor supports Firefox browser till v44, do not use above
version.
My test environment is Windows not MAC, so guys above settings are for
Windows environment.
Thanks
Ajitabh Ranjan
Mob:<PHONE_NUMBER>
On Tue, Jan 17, 2017 at 7:15 PM, 7stud<EMAIL_ADDRESS>wrote:

Mac OSX 10.10.5
Firefox 50.1
I'm having the same problem with Firefox not running any tests and timing
out. I'm following the protractor tutorial
http://www.protractortest.org/#/tutorial, and Step 3
http://www.protractortest.org/#/tutorial%23step-3-changing-the-configuration
asks me to add Firefox to conf.js:
// conf.js
exports.config = {
framework: 'jasmine',
seleniumAddress: 'http://localhost:4444/wd/hub',
specs: ['spec.js'],
capabilities: {
browserName: 'firefox'
}
}
Here is the output when I do $ webdriver-manager start:
~/protractor_programs$ webdriver-manager start
[06:39:49] I/start - java -Dwebdriver.chrome.driver=/Users/7stud/.nvm/versions/node/v7.4.0/lib/node_modules/protractor/node_modules/webdriver-manager/selenium/chromedriver_2.26 -Dwebdriver.gecko.driver=/Users/7stud/.nvm/versions/node/v7.4.0/lib/node_modules/protractor/node_modules/webdriver-manager/selenium/geckodriver-v0.12.0 -jar /Users/7stud/.nvm/versions/node/v7.4.0/lib/node_modules/protractor/node_modules/webdriver-manager/selenium/selenium-server-standalone-2.53.1.jar -port 4444
[06:39:49] I/start - seleniumProcess.pid: 63927
06:39:49.859 INFO - Launching a standalone Selenium Server
06:39:49.892 INFO - Java: Oracle Corporation 25.40-b25
06:39:49.893 INFO - OS: Mac OS X 10.10.5 x86_64
06:39:49.903 INFO - v2.53.1, with Core v2.53.1. Built from revision a36b8b1
06:39:49.977 INFO - Driver provider org.openqa.selenium.ie.InternetExplorerDriver registration is skipped:
registration capabilities Capabilities [{ensureCleanSession=true, browserName=internet explorer, version=, platform=WINDOWS}] does not match the current platform MAC
06:39:49.978 INFO - Driver provider org.openqa.selenium.edge.EdgeDriver registration is skipped:
registration capabilities Capabilities [{browserName=MicrosoftEdge, version=, platform=WINDOWS}] does not match the current platform MAC
06:39:49.978 INFO - Driver class not found: com.opera.core.systems.OperaDriver
06:39:49.978 INFO - Driver provider com.opera.core.systems.OperaDriver is not registered
06:39:49.980 INFO - Driver class not found: org.openqa.selenium.htmlunit.HtmlUnitDriver
06:39:49.980 INFO - Driver provider org.openqa.selenium.htmlunit.HtmlUnitDriver is not registered
06:39:50.045 INFO - RemoteWebDriver instances should connect to: http://<IP_ADDRESS>:4444/wd/hub
06:39:50.045 INFO - Selenium Server is up and running
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/angular/protractor/issues/886#issuecomment-273162523,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AOad533en4K9qGj3uRTroGfO77aoMm1Qks5rTMYWgaJpZM4CAL2g
.

This is an ancient issue, and unrelated to the Firefox woes of the modern era. Please see #3823.
The underlying issue is the version of Selenium that Protractor uses. Protractor 4 uses selenium 2.53, and only supports Firefox 47 or older.
Protractor 5 can work with Firefox 50, but only with selenium 3.0.0-beta4. Also, Firefox 50 has a bug that might affect Protractor testing, so using the 51 beta is recommended. Protractor 5.1 will support using Firefox 51 with directConnect.

Guys,
Running automation in firefox has some issues with the different versions
of different framework.
I am running my automation on chrome and it works perfect.
I have also executed my automation suites on firefox, but having older
version of firefox there are some bugs with the design of angular js app
which I was executing.
I setup the chrome as a base and now I am happy.
I do manual testing on firefox for further test.
Thanks
Ajitabh Ranjan
Mob:<PHONE_NUMBER>
On Sat, Jan 21, 2017 at 1:23 PM, mgiambalvo<EMAIL_ADDRESS>wrote:

This is an ancient issue, and unrelated to the Firefox woes of the modern
era. Please see #3823 https://github.com/angular/protractor/issues/3823.
The underlying issue is the version of Selenium that Protractor uses.
Protractor 4 uses selenium 2.53, and only supports Firefox 47 or older.
Protractor 5 can work with Firefox 50, but only with selenium 3.0.0-beta4.
Also, Firefox 50 has a bug that might affect Protractor testing, so using
the 51 beta is recommended. Protractor 5.1 will support using Firefox 51
with directConnect.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/angular/protractor/issues/886#issuecomment-274246993,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AOad5wcRQIzDdsV33zGYnNKGS3rod9aUks5rUbmRgaJpZM4CAL2g
.

Hello All,
I am having same issue with latest Firefox version 52.0 32bit when I give directConnect: true nothing works seems like 2 firefox tabs are opened and test fails.

[09:54:22] Using gulpfile D:\projects\GIT hub\gulp-protractor fork\example\gulpfile.js
[09:54:22] Starting 'webdriver_update'...
[09:54:24] I/update - chromedriver: file exists D:\projects\GIT hub\gulp-protractor fork\node_modules\protractor\node_modules\webdriver
-manager\selenium\chromedriver_2.28.zip
[09:54:24] I/update - chromedriver: unzipping chromedriver_2.28.zip
[09:54:24] I/update - chromedriver: chromedriver_2.28.exe up to date
[09:54:24] I/update - selenium standalone: file exists D:\projects\GIT hub\gulp-protractor fork\node_modules\protractor\node_modules\we
bdriver-manager\selenium\selenium-server-standalone-3.3.1.jar
[09:54:24] I/update - selenium standalone: selenium-server-standalone-3.3.1.jar up to date
[09:54:26] I/update - geckodriver: file exists D:\projects\GIT hub\gulp-protractor fork\node_modules\protractor\node_modules\webdriver-
manager\selenium\geckodriver-v0.15.0.zip
[09:54:26] I/update - geckodriver: unzipping geckodriver-v0.15.0.zip
[09:54:26] I/update - geckodriver: geckodriver-v0.15.0.exe up to date
[09:54:26] Finished 'webdriver_update' after 3.91 s
[09:54:26] Starting 'protractor'...
[09:54:27] W/driverProviders - Using driver provider directConnect, but also found extra driver provider parameter(s): seleniumAddress
[09:54:27] I/launcher - Running 1 instances of WebDriver
[09:54:27] I/direct - Using FirefoxDriver directly...
[09:54:34] E/launcher - Unable to parse new session response: {"value": {"sessionId":"2ae0d0d4-bd6e-4683-bcd7-adccf83e66dd","value":{"a
cceptInsecureCerts":false,"browserName":"firefox","browserVersion":"52.0","moz:accessibilityChecks":false,"moz:processID":31788,"moz:pr
ofile":"C:\\Users\\Rahul\\AppData\\Local\\Temp\\rust_mozprofile.nMy4w0qmOZqL","pageLoadStrategy":"normal","platformName":"windows_nt","
platformVersion":"10.0","rotatable":false,"specificationLevel":0,"timeouts":{"implicit":0,"page load":300000,"script":30000}}}}
[09:54:34] E/launcher - WebDriverError: Unable to parse new session response: {"value": {"sessionId":"2ae0d0d4-bd6e-4683-bcd7-adccf83e6
6dd","value":{"acceptInsecureCerts":false,"browserName":"firefox","browserVersion":"52.0","moz:accessibilityChecks":false,"moz:processI
D":31788,"moz:profile":"C:\\Users\\Rahul\\AppData\\Local\\Temp\\rust_mozprofile.nMy4w0qmOZqL","pageLoadStrategy":"normal","platformName
":"windows_nt","platformVersion":"10.0","rotatable":false,"specificationLevel":0,"timeouts":{"implicit":0,"page load":300000,"script":3
0000}}}}
    at WebDriverError (D:\projects\GIT hub\gulp-protractor fork\node_modules\selenium-webdriver\lib\error.js:27:5)
    at doSend.then.response (D:\projects\GIT hub\gulp-protractor fork\node_modules\selenium-webdriver\lib\http.js:445:19)
    at process._tickCallback (internal/process/next_tick.js:103:7)
From: Task: WebDriver.createSession()

    at Function.createSession (D:\projects\GIT hub\gulp-protractor fork\node_modules\selenium-webdriver\lib\webdriver.js:777:24)
    at Function.createSession (D:\projects\GIT hub\gulp-protractor fork\node_modules\selenium-webdriver\firefox\index.js:640:55)
    at Direct.getNewDriver (D:\projects\GIT hub\gulp-protractor fork\node_modules\protractor\lib\driverProviders\direct.ts:112:25)
    at Runner.createBrowser (D:\projects\GIT hub\gulp-protractor fork\node_modules\protractor\lib\runner.ts:225:39)
    at q.then.then (D:\projects\GIT hub\gulp-protractor fork\node_modules\protractor\lib\runner.ts:391:27)
    at _fulfilled (D:\projects\GIT hub\gulp-protractor fork\node_modules\q\q.js:834:54)
    at self.promiseDispatch.done (D:\projects\GIT hub\gulp-protractor fork\node_modules\q\q.js:863:30)
    at Promise.promise.promiseDispatch (D:\projects\GIT hub\gulp-protractor fork\node_modules\q\q.js:796:13)
    at D:\projects\GIT hub\gulp-protractor fork\node_modules\q\q.js:556:49
    at runSingle (D:\projects\GIT hub\gulp-protractor fork\node_modules\q\q.js:137:13)
[09:54:34] E/launcher - Process exited with error code 199
{ [Error: protractor exited with code 199]
  message: 'protractor exited with code 199',
  showStack: false,
  showProperties: true,
  plugin: 'gulp-protractor',
  __safety: { toString: [Function: bound ] } }

But when I start selenium standalone server with gecko driver location and remove directConnect then it works fine.

Update your protractor and try again.
Thanks
Ajitabh Ranjan
Mob:<PHONE_NUMBER>
On Wed, Mar 15, 2017 at 9:59 AM, Rahul Raut<EMAIL_ADDRESS>wrote:

Hello All,
I am having same issue with latest Firefox version 52.0 32bit when I give
directConnect: true nothing works seems like 2 firefox tabs are opened and
test fails.
[09:54:22] Using gulpfile D:\projects\GIT hub\gulp-protractor fork\example\gulpfile.js
[09:54:22] Starting 'webdriver_update'...
[09:54:24] I/update - chromedriver: file exists D:\projects\GIT hub\gulp-protractor fork\node_modules\protractor\node_modules\webdriver
-manager\selenium\chromedriver_2.28.zip
[09:54:24] I/update - chromedriver: unzipping chromedriver_2.28.zip
[09:54:24] I/update - chromedriver: chromedriver_2.28.exe up to date
[09:54:24] I/update - selenium standalone: file exists D:\projects\GIT hub\gulp-protractor fork\node_modules\protractor\node_modules\we
bdriver-manager\selenium\selenium-server-standalone-3.3.1.jar
[09:54:24] I/update - selenium standalone: selenium-server-standalone-3.3.1.jar up to date
[09:54:26] I/update - geckodriver: file exists D:\projects\GIT hub\gulp-protractor fork\node_modules\protractor\node_modules\webdriver-
manager\selenium\geckodriver-v0.15.0.zip
[09:54:26] I/update - geckodriver: unzipping geckodriver-v0.15.0.zip
[09:54:26] I/update - geckodriver: geckodriver-v0.15.0.exe up to date
[09:54:26] Finished 'webdriver_update' after 3.91 s
[09:54:26] Starting 'protractor'...
[09:54:27] W/driverProviders - Using driver provider directConnect, but also found extra driver provider parameter(s): seleniumAddress
[09:54:27] I/launcher - Running 1 instances of WebDriver
[09:54:27] I/direct - Using FirefoxDriver directly...
[09:54:34] E/launcher - Unable to parse new session response: {"value": {"sessionId":"2ae0d0d4-bd6e-4683-bcd7-adccf83e66dd","value":{"a
cceptInsecureCerts":false,"browserName":"firefox","browserVersion":"52.0","moz:accessibilityChecks":false,"moz:processID":31788,"moz:pr
ofile":"C:\Users\Rahul\AppData\Local\Temp\rust_mozprofile.nMy4w0qmOZqL","pageLoadStrategy":"normal","platformName":"windows_nt","
platformVersion":"10.0","rotatable":false,"specificationLevel":0,"timeouts":{"implicit":0,"page load":300000,"script":30000}}}}
[09:54:34] E/launcher - WebDriverError: Unable to parse new session response: {"value": {"sessionId":"2ae0d0d4-bd6e-4683-bcd7-adccf83e6
6dd","value":{"acceptInsecureCerts":false,"browserName":"firefox","browserVersion":"52.0","moz:accessibilityChecks":false,"moz:processI
D":31788,"moz:profile":"C:\Users\Rahul\AppData\Local\Temp\rust_mozprofile.nMy4w0qmOZqL","pageLoadStrategy":"normal","platformName
":"windows_nt","platformVersion":"10.0","rotatable":false,"specificationLevel":0,"timeouts":{"implicit":0,"page load":300000,"script":3
0000}}}}
at WebDriverError (D:\projects\GIT hub\gulp-protractor fork\node_modules\selenium-webdriver\lib\error.js:27:5)
at doSend.then.response (D:\projects\GIT hub\gulp-protractor fork\node_modules\selenium-webdriver\lib\http.js:445:19)
at process._tickCallback (internal/process/next_tick.js:103:7)
From: Task: WebDriver.createSession()
at Function.createSession (D:\projects\GIT hub\gulp-protractor fork\node_modules\selenium-webdriver\lib\webdriver.js:777:24)
at Function.createSession (D:\projects\GIT hub\gulp-protractor fork\node_modules\selenium-webdriver\firefox\index.js:640:55)
at Direct.getNewDriver (D:\projects\GIT hub\gulp-protractor fork\node_modules\protractor\lib\driverProviders\direct.ts:112:25)
at Runner.createBrowser (D:\projects\GIT hub\gulp-protractor fork\node_modules\protractor\lib\runner.ts:225:39)
at q.then.then (D:\projects\GIT hub\gulp-protractor fork\node_modules\protractor\lib\runner.ts:391:27)
at _fulfilled (D:\projects\GIT hub\gulp-protractor fork\node_modules\q\q.js:834:54)
at self.promiseDispatch.done (D:\projects\GIT hub\gulp-protractor fork\node_modules\q\q.js:863:30)
at Promise.promise.promiseDispatch (D:\projects\GIT hub\gulp-protractor fork\node_modules\q\q.js:796:13)
at D:\projects\GIT hub\gulp-protractor fork\node_modules\q\q.js:556:49
at runSingle (D:\projects\GIT hub\gulp-protractor fork\node_modules\q\q.js:137:13)

[09:54:34] E/launcher - Process exited with error code 199
{ [Error: protractor exited with code 199]
message: 'protractor exited with code 199',
showStack: false,
showProperties: true,
plugin: 'gulp-protractor',
__safety: { toString: [Function: bound ] } }
But when I start selenium standalone server with gecko driver location and
remove directConnect then it works fine.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/angular/protractor/issues/886#issuecomment-286638073,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AOad5-VahANDTXAuEHBPEaUo-ymmeOW8ks5rl2kigaJpZM4CAL2g
.

It is latest one 5.1.1

I am not using the gulp to run the protector.
I am using the protractor directly with firefox configuration and it is
running.
How have you configured firefox????
On Mar 16, 2017 1:00 AM, "Rahul Raut"<EMAIL_ADDRESS>wrote:

It is latest one 5.1.1
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/angular/protractor/issues/886#issuecomment-286853565,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AOad53VXnGkxDg9j044VAjqtkkeorfQqks5rmDxZgaJpZM4CAL2g
.

Not able to Run Protractor Test on Firefox browser
Failed:
[INFO] Build info: version: '3.5.3', revision: 'a88d25fe6b', time: '2017-08-29T12:54:15.039Z'
[INFO] System info: host: 'MC0XSZYC', ip: '<IP_ADDRESS>', os.name: 'Windows 7', os.arch: 'amd64', os.version: '6.1', java.version: '1.8.0_131'
[INFO] Driver info: driver.version:
Eclipse raised these issue while running test on firefox

@makwanaparth94
Can you provide more info, like which version:

protractor
firefox
the firefox driver you are using

Yeah sure!
I am using Protractor v5.1,Firefox 55.0.3 and geckodriver: 0.18.0

@makwanaparth94 I ran into this issue while testing with protractor too. The problem was that firefox lost focus, because of me fiddeling around while protractor was running. When I left it do its thing everything went well.


The debugger exited without completing startup handshake. Python Error

Which OS:Ubuntu 18.04
Which VSCode version:  1.34.0
Which extension version: lldb
Which adapter type: Classic
Which LLDB version: lldb version 8.0.0
What is the problem and how did you get there:
Tried to launch debugger. Got error debugger exited without completing startup handshake. Appears to be a problem in the way python is being pulled in on the machine. Unclear how to proceed to debug problem
configuration: { type: 'lldb',
request: 'launch',
name: 'Launch hello_world_test',
program:
'${workspaceFolder}/bazel-bin/..../hello_world/cc/hello_world_test',
args: [],
cwd:
'${workspaceFolder}/bazel-bin/.../hello_world/cc/hello_world_test.runfiles/main/',
sourceMap: { '/proc/self/cwd': '${workspaceFolder}' },
stopOnEntry: false }
(lldb) command script import '/home//.vscode/extensions/vadimcn.vscode-lldb-1.2.3/adapter'
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python2.7/copy.py", line 52, in
import weakref
File "/usr/lib/python2.7/weakref.py", line 14, in
from weakref import (
ImportError: cannot import name remove_dead_weakref
Traceback (most recent call last):
File "", line 1, in
File "/home//external/sysroot-runtime/usr/lib/llvm-8/lib/python2.7/site-packages/lldb/formatters/init.py", line 3, in
import('lldb.formatters.' + x)
File "/home//external/sysroot-runtime/usr/lib/llvm-8/lib/python2.7/site-packages/lldb/formatters/cache.py", line 8, in
import lldb.formatters.metrics
File "/home//external/sysroot-runtime/usr/lib/llvm-8/lib/python2.7/site-packages/lldb/formatters/metrics.py", line 10, in
import datetime
ImportError: No module named datetime
Traceback (most recent call last):
File "", line 1, in
NameError: name 'pydoc' is not defined
error: module importing failed: cannot import name remove_dead_weakref
File "temp.py", line 1, in
File "/home//.vscode/extensions/vadimcn.vscode-lldb-1.2.3/adapter/init.py", line 16, in
from .main import run_pipe_session, run_stdio_session, run_tcp_session, run_tcp_server
File "/home/_/.vscode/extensions/vadimcn.vscode-lldb-1.2.3/adapter/main.py", line 4, in
import logging
File "/usr/lib/python2.7/logging/init.py", line 26, in
import sys, os, time, cStringIO, traceback, warnings, weakref, collections
File "/usr/lib/python2.7/weakref.py", line 14, in
from _weakref import (
Error: The debugger exited without completing startup handshake.
--- Checking version ---
lldb version 8.0.0
--- Checking Python ---
(lldb) script import sys, io, lldb
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python2.7/copy.py", line 52, in
import weakref
File "/usr/lib/python2.7/weakref.py", line 14, in
from weakref import (
ImportError: cannot import name remove_dead_weakref
Traceback (most recent call last):
File "", line 1, in
File "/home//external/sysroot-runtime/usr/lib/llvm-8/lib/python2.7/site-packages/lldb/formatters/init.py", line 3, in
import('lldb.formatters.' + x)
File "/home//external/sysroot-runtime/usr/lib/llvm-8/lib/python2.7/site-packages/lldb/formatters/cache.py", line 8, in
import lldb.formatters.metrics
File "/home/_/external/sysroot-runtime/usr/lib/llvm-8/lib/python2.7/site-packages/lldb/formatters/metrics.py", line 10, in
import datetime
ImportError: No module named datetime
Traceback (most recent call last):
File "", line 1, in
NameError: name 'pydoc' is not defined
(lldb) script print(lldb.SBDebugger.Create().IsValid())
True
(lldb) script print("OK")
OK
--- Done ---

Looks like corrupted lldb installation.   Can you please try switching to native adapter, i.e. put this in your workspace config:  "lldb.adapterType": "native"


Optimize store.get and store.set

In https://github.com/graphprotocol/graph-node/issues/1347#issuecomment-555539043 we have identified store.get/store.set to take up the majority of indexing time (~30-50%). Optimizing these should significantly boost indexing performance.
Next steps:

Plan specific optimizations (like for non-existent entities).
Implement them.

Discussing with @lutter, we decided to start with some straightforward improvements to the entity cache, which are not going to the DB for validation if we can help it, and loading entities in a single DB query in as_modifications. After these we can evaluate doing a bloom filter for non-existing entities or better caching for existing entities.
At least for now we don't see a need for a user-facing store.overwrite or store.insert, we'd like to optimize as much as possible without complicating things for the user.

Update: The optimizations for store.set are done, the next target is store.get, I'll evaluate the impact of the bloom filter and plan it in detail if it has the large impact.

Optimizations have now been implemented for store.set and store.get, so that they are no longer among the most time consuming sections. There is more that can be done, such as the bloom filter, but I feel we've done enough in the context of this issue.


Add missing filters to RecordsQuery

Added the following filters to RecordsQuery:
published
dataCid
datePublished
dateUpdated (messageTimestamp)

Codecov Report

Merging #578 (ccc90ab) into main (bea7bdf) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main     #578   +/-   ##
=======================================
  Coverage   97.68%   97.68%
=======================================
  Files          66       66
  Lines        7932     7959   +27
  Branches     1150     1161   +11
=======================================
+ Hits         7748     7775   +27
  Misses        178      178
  Partials        6        6

Files
Coverage Δ

src/handlers/records-query.ts
100.00% <100.00%> (ø)

src/utils/records.ts
100.00% <100.00%> (ø)

This PR addresses #535. Will jump back on this PR today.


Fatal error: Class 'Kirki_Controls_Slider_Control' not found on line 306

Hi arstath!
firstly congratulations for the Kirki toolkit, it is an amazing tool!
But I have a problem! Kirki throws me an error when I insert the slider field in the theme customizer
here is the code:

include_once( dirname( __FILE__ ) . '/kirki/kirki.php' );

function my_blog_kirki_configuration( $config ) {
    $config['url_path']     = get_stylesheet_directory_uri() . '/ini/kirki/';
    $config['logo_image']   = get_stylesheet_directory_uri() . '/images/world-map.png';
    $config['description']  = esc_html__( 'The Swallow blog is the best!!', 'tb_blog' );
    $config['color_accent'] = '#00bcd4';
    $config['color_back']   = '#455a64';
    $config['width']        = '20%';

    return $config;
}
add_filter( 'kirki/config', 'my_blog_kirki_configuration' );

function my_blog_add_settings( $wp_customize ){
.....
    $wp_customize->add_setting('img-blur', array(
        'type'              => 'theme_mod',
        'capability'        => 'edit_theme_options',
        'default'           => 0,
        'sanitize_callback' => 'my_blog_sanitize_blur_range',
    ) );
....
}
add_filter( 'customize_register', 'my_blog_add_settings' );

function blog_customizer_controls( $controls )
....
    $controls[] = array(
        'type'        => 'slider',
        'section'     => 'favicon_background_img',
        'settings'    => 'img-blur',
        'label'       => esc_html__( 'This is the range control of background image blur.', 'tb-blog' ),
        'help'        => esc_html__( 'Slide to change the background image blur', 'tb-blog' ),
        'priority'    => 30,
        'choices'     => array(
		    'min'   => 0,
            'max'   => 100,
            'step'  => 1,
            )
        );

...
}
add_action( 'kirki/fields', 'my_blog_customizer_controls' );

//custom sanitize function
function my_blog_sanitize_blur_range( $input ) {
    if( is_numeric( $input ) && $input >=0 && $input <= 100 ) {
        return intval( $input );
    } else {
        return 0;
    }
}

here is the output it throws:
Fatal error: Class 'Kirki_Controls_Slider_Control' not found in /home/ubuntu/workspace/wp-content/themes/tb/ini/kirki/includes/class-kirki.php on line 306

That's weird...
Do you have the complete code somewhere on github so that I may try to replicate this?

hi @aristath I sent you a mail to access my repo

I am facing the same problem. It gives no error when in local testing environment, but throw the error after uploading to the live site.
Fatal error: Class 'Kirki_Controls_Slider_Control' not found in /path/to/kirki/includes/class-kirki.php on line 306

@ZmagoD I just cloned your repository, added kirki in the theme's ini folder, and then examined the ini/traveler-customizer.php file.
I uncommented lines 416-431 to add the slider field and though I did not get a fatal error, the customizer was not loading.
I noticed that in that field, no default value was defined. As soon as I added that, everything started working perfectly fine.
Can you test if that works for you?

@aristath I found the source of my problem. Is that I had downloaded Kirki from the WordPress repository and that version make these error occur. Now I have downloaded it from github and all works fine.

Hi Aris, did you see the comment in another issue regarding a library that may give more function to the slider?

@cmwwebfx I did, and I replied there.
@ZmagoD I'm glad you managed to resolve this issue, I'm closing this thread. As soon as we implement a couple more features we need (see remaining tasks on https://github.com/aristath/kirki/issues?q=is%3Aopen+is%3Aissue+milestone%3A1.1) we'll be releasing the next version on w.org
Cheers!


Prepare for Spring Cloud Azure 4.9.0 release

Description
Update versions, changelog and readme
All SDK Contribution checklist:

[ ] The pull request does not introduce [breaking changes]
[ ] CHANGELOG is updated for new features, bug fixes or other significant changes.
[ ] I have read the contribution guidelines.

General Guidelines and Best Practices

[ ] Title of the pull request is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[ ] Pull request includes test coverage for the included changes.

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


[SPARK-8016] YARN cluster / client modes have different app names for python

[SPARK-8016] YARN cluster / client modes have different app names for python
Cause: Currently in YARN the only point where the name of the application can be set is when it gets submitted by the client. In yarn-cluster mode this is performed by the spark-submit, which uses org.apache.spark.deploy.yarn.Client. The name of the application is picked from --name, or by default from --class. In case of yarn-client mode, the name of the application is set by SparkContext.setAppName.
Solution: It is not feasible to read the name set with SparkContext.setAppName in yarn-cluster mode. Added additional notes to the arguments list of spark-submit.

Can one of the admins verify this patch?

@ehnalis my point in the JIRA is more to make these consistent rather than just document the differences. Since this patch doesn't fix the issue, would you mind closing it?

@ehnalis what happens if we set spark.app.name, which is passed to the AM process in cluster mode? There was some discussion on this before on #3557. cc @vanzin

@andrewor14 Currently the only place where you can set the name of your application is when you prepare an ApplicationSubmissionContext (YARN API) and you set the application name before submitting with YarnClient. This is what org.apache.spark.deploy.yarn.Client does. The problem is that the name of the Spark application has been set with SparkContext.setAppName usually in the user code (JAR) you wish to deploy to the cluster. When SparkContext wakes up on YARN as the AM process on container 0, your application already has an ID and a name, which you are not able to change as AM, neither as the client who submitted the application.
Check https://issues.apache.org/jira/browse/YARN-3772

I see, because in cluster mode the app name could be set in the jar itself. I'm inclined to close this issue as a "Won't Fix" then. I agree with @vanzin that this doesn't look like the best place to document the differences in app name behavior. Maybe it's not even that big of a deal that it is divergent.

It would be nice to have at least some clarification on this matter in the docs. Or we might consider deprecating the {{SparkContext.setAppName}}, since it can not provide a solution for every deployment scenario.


Automated cherry pick of #5186: feature(notify): Validate config

Cherry pick of #5186 on release/2.13.
#5186: feature(notify): Validate config

Codecov Report

:exclamation: No coverage uploaded for pull request base (release/2.13@d71f0ce). Click here to learn what that means.
The diff coverage is n/a.

@@              Coverage Diff               @@
##             release/2.13   #5229   +/-   ##
==============================================
  Coverage                ?   6.81%
==============================================
  Files                   ?     530
  Lines                   ?   90015
  Branches                ?       0
==============================================
  Hits                    ?    6137
  Misses                  ?   83370
  Partials                ?     508

Flag
Coverage Δ

#aFlag
6.81% <ø> (?)

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 d71f0ce...c14202d. Read the comment docs.

/lgtm

/approve


Fix errors with full url response

When full url is included in the response shown like below, some errors are apperred.
<d:multistatus xmlns:d="DAV:" xmlns:c="urn:ietf:params:xml:ns:caldav">
    <d:response>
        <d:href>http://cal.example.com/home/bernard/</d:href>
        <d:propstat>
            <d:prop>
                <c:calendar-home-set>
                    <d:href>http://cal.example.com/home/bernard/calendars/</d:href>
                </c:calendar-home-set>
            </d:prop>
            <d:status>HTTP/1.1 200 OK</d:status>
        </d:propstat>
    </d:response>
</d:multistatus>

from an example shown in https://tools.ietf.org/html/rfc4791#section-6.2.1
I fixed them with:

avoid quote from a target of url.join if it's full url because 'https://~' will be encoded to 'https%3A//~' occurred with a change of https://github.com/python-caldav/caldav/commit/8f0c0e5d7e4cdf88b5c2e4260f114b405d8e4085
use full url as key to get value from properties when nothing matched with path only key

I tried to write tests with a response includes full url like <d:href>http://cal.example.com/home/bernard/</d:href> but I couldn't configure radicale for this test use..

I should try to write up some unit tests that mocks up a response with absolute URLs - and it's also nice if we can run the functional tests towards a caldav server that gives absolute URLs.  What server do you use?

I added a unit test, and I've also verified that the unit test breaks towards 0.7.0.
I would still like to know what kind of caldav server you are using.


Add CI for spell check and other linters

Following up with https://github.com/coq/platform/pull/173#issuecomment-968280695 and https://github.com/coq/platform/issues/197#issuecomment-1018479798
The linters currently point out some typos etc, see https://github.com/k4rtik/platform/runs/5667821385?check_suite_focus=true#step:4:254 but I have not fixed them in this PR to test the tool's auto PR support for those fixes.
Once this PR is merged, we may want to change VALIDATE_ALL_CODEBASE: true to VALIDATE_ALL_CODEBASE: ${{ github.event_name == 'push' && github.ref == 'refs/heads/main' }} so that CI only tests the new changes.
I have also disabled certain linters that may involve stylistic choices, namely:
DISABLE_LINTERS:
  - SPELL_CSPELL
  - ACTION_ACTIONLINT
  - BASH_SHELLCHECK
  - C_CPPLINT
  - BASH_SHFMT
  - MARKDOWN_MARKDOWNLINT

I will let you decide about enabling them.

Lo, it ran but needs permission to create a PR:

Identified PR#231 from environment
[GitHub Comment Reporter] Unable to post pull request comment: 403 {"message": "Resource not accessible by integration", "documentation_url": "https://docs.github.com/rest/reference/issues#create-an-issue-comment"}.
To enable this function, please :

Create a Personal Access Token (https://docs.github.com/en/free-pro-team@latest/github/authenticating-to-github/creating-a-personal-access-token)
Create a secret named PAT with its value on your repository (https://docs.github.com/en/free-pro-team@latest/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-a-repository)3. Define PAT={{secrets.PAT}} in your GitHub action environment variables

@k4rtik : thanks I appreciate it - I belong to those people who have difficulties with languages which don't come with compilers.
I will take care of the access token.

@k4rtik : is there a way to avoid the chmod of the files in the shell-scripts folder? None of these files is intended to be called directly - they are all intended to be sourced. So the access mode 644 is intentional and a 755 mode would be more confusing than helpful.

Another issue is that issues in the auto generated Readme files should be flagged, but not corrected. All errors in auto generated files must be fixed somewhere else.

I added the secret, but it didn't do anything I guess because in the PR all changes are already fixed. So I guess to test the PR I need to undo all these changes?

@k4rtik : a last comment - can you please factor out the suggested changed from the CI procedure? The CI procedure I am happy to merge as is, but most of the suggested changes not.

@k4rtik : is there a way to avoid the chmod of the files in the shell-scripts folder? None of these files is intended to be called directly - they are all intended to be sourced. So the access mode 644 is intentional and a 755 mode would be more confusing than helpful.

Yes, pushing this change. Sorry about the confusion.

Another issue is that issues in the auto generated Readme files should be flagged, but not corrected. All errors in auto generated files must be fixed somewhere else.

They seem flagged, but there is still some permissions issue, see the error:
[GitHub Status Reporter] Error posting Status for MARKDOWNwith markdown-table-formatter: 401
GitHub API response: {"message":"Bad credentials","documentation_url":"https://docs.github.com/rest"}
[Text Reporter] Generated TEXT report: /github/workspace/report/linters_logs/SUCCESS-MARKDOWN_MARKDOWN_TABLE_FORMATTER.log

I think this might be because of the change you made at https://github.com/coq/platform/pull/231/commits/64269d4c0b5674c0d5ab7986ae196b20995f260d#diff-206ce5348d308a71dab8cdc132d6dc2babebc80b94a707a45a744909ed9367d4L44
-    GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+    GITHUB_TOKEN: ${{ secrets.PAT_LINT_SPELL }}

According to the doc, this does not need to be touched. "GITHUB_TOKEN" is automatically set by GitHub.

I added the secret, but it didn't do anything I guess because in the PR all changes are already fixed. So I guess to test the PR I need to undo all these changes?

I think this will also require that the correct GITHUB_TOKEN is passed. I am reverting that small change. The changes are not in the PR. :)

can you please factor out the suggested changed from the CI procedure? The CI procedure I am happy to merge as is, but most of the suggested changes not.

To be clear, the only suggested changes that I included in the PR were file permissions, and those that could not be fixed automatically such as bad links/were leading to false positives such as _CoqProject. I took another look but there is nothing else to factor out.

We can decide about keeping automatic fixing of suggestions once we test this feature out.

@k4rtik : thanks:
regarding factoring: I want to strictly separate the CI procedure as such (I would think 2 files) and any changes it produces. E.g. the link changes in the .MD files should also be done differently (by creating a new section which covers the two). But any way, introducing these checks in CI and actually fixing them should be separate, independent steps.

P.S.: Please abort the main CI processes when you do changes - for this PR only the new CI step needs to run.

Hi @MSoegtropIMC can you manually cancel these platform CI runs, ie, all except the Megalinter one? As it may not get queued until much later.

Is there a way for me to abort them? I don't think I have permission.
Or did you mean to disable them while making the PR?

Ah I forgot that you don't have permission for this. I think it is better then to disable them for the PR - I will then piggy back the PR and reenable it before I merge.

Hi @MSoegtropIMC
I am getting this error with my latest change:
Error: Input required and not supplied: token

Can you please double-check if the personal access token you created is called PAT_LINT_SPELL?
Unsure what's happening here.

AFAIK the secrets are not available in PRs from forks.

@k4rtik : can you please do the requested changes - or alternatively remove the ReadMe files from the commit.
Also can you please change the bad charter link in [maintainer_scripts/create_readme.sh] - I think this should go together with the same change in the auto generated files.
I will then take it from there - I guess this will run only on main (which I think is good enough).

AFAIK the secrets are not available in PRs from forks.

In that case let me try testing these features on my fork directly and then I will send a PR later.


Passing -Werror to pytest --nbmake has no effect

Describe the bug
Passing -Werror to pytest --nbmake has no effect.  It should, instead, cause the tests to fail if the code in a notebook causes a warning.
To Reproduce
Steps to reproduce the behavior:

Create a notebook which emits a warning.
Run it using pytest --nbmake --Werror **/*ipynb

Expected behavior
I expect tests to fail.

hi @garrison, thanks for this report. We generally intend to follow conventions in pytest so I'll mark this one as a bug.


Flag unsupported noqa directives when using M001.

Flag unsupported noqa directives when using M001.
Now it calls some noqa unused while they are needed for some flake8 plugins:
$ ruff --extend-select M001 .
...: M001 Unused `noqa` directive for: E101, W191

Some flag that indicates that those are not implemented (yet) would be nice:
$ ruff --extend-select M001 .
...: M001 Unused `noqa` directive for: E101, W191 (not implemented)

That's a nice idea.

M001 will still remove those "unknown" codes when autofixing -- not sure what the right behavior is there.

Works nicely.
One way would be to collect all known codes from the most common plugins to have a whitelist of things to not remove.


Fix #544

'whoami' is not POSIX-compliant, but 'id -un' is. This is true
at least since the 1003.1-2001 standard, I don't have a copy of the
previous 1003.2-1992 to verify it is true there too.
This causes problems in recent operating systems where 'whoami' is
not even shipped anymore.

Thanks, commented in #544.

You forgot to restore the SunOS ucb PATH extension. Other than that, I agree with the patch. Thanks again.

The ucb path should not be necessary now that id -un is used. There's no harm in adding it again, though.

Doesn't the whoami fallback require the ucb path?

Don't forget to append your name in THANKS.

The whoami fallback only requires the ucb path on SunOS systems that do not have id -un, and I don't know of any. Does not hurt having it there, so I put it back.

+1

@ferd?


(#26) Simplify local development of choco-theme

Description Of Changes
The changes here and the upgrade of choco-theme
are needed in order to utilize new commands that
will help the development of choco-theme.
More information on changes can be found at:
https://github.com/chocolatey/choco-theme/releases/tag/0.7.0
Motivation and Context
This will enhance the developer experience of choco-theme.
Testing
Follow instructions at https://github.com/chocolatey/choco-theme/pull/403.
Change Types Made

[ ] Minor fix (typos etc.).
[ ] Major change (refactoring post, refactoring code, reformatting etc.).
[ ] New post added.
[ ] Site code change

Change Checklist

[ ] Spelling checked
[ ] Changes follow writing guidelines
[ ] Author bio added

Related Issue

#26

This is in draft because choco-theme needs updated first, however this can be tested.


Go dep stack submission

Checklist:

[x] Read the Code of Conduct and Contributing Guidelines.

[x] Followed the commit message guidelines.

[x] Stack adheres to Appsody stack structure.

Modifying an existing stack:
n/a
Contributing a new stack:

Describe how application dependencies are managed:

This stack uses Go v1.11 format Modules for dependencies

Explain how Appsody file watcher is utilized:

File watcher watches .go and .toml files.

Describe other Appsody environment variables defined by the stack image:

Nothing other than the minimum that Appsody needs.

Describe any limitations and known issues:

appsody debug works despite seeing spurious messages like could not launch process: fork/exec /project/user-app/__debug_bin: inappropriate ioctl for device. Running with appsody debug -i helps in some cases.
Related Issues:
Originally submitted under PR #425 but was split out for clarity

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: jpapejr:x: rootroot seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

Disregard this one.. I screwed it up.. :(


Error using convert3to2

When using convert3to2 got FileNotFoundError: [Errno 2] No such file or directory: ...lib/python3.7/site-packages/sbol_utilities/sbolgraph-standalone.js. Is this an error on the library or I need to install something?

Looks like the file isn't making it into the egg for the pypi distribution for some reason... I will try to figure out why that is and get out a patch.
In the meantime, it will work if you install from source. Clone the repository, and then in its root directory run:
pip3 install .

OK, version 1.0-alpha13 is pushed with the distribution problem fixed, and I have tested it to see that it does install and run correctly. Please let me know if it's fixed for you as well.

I tried both options that you mention and cloning the repository and installing with pip install -e . . All of them retrieve the same error attached.

Well, we are progressing forward at least: now it's finding the Javascript but something's going wrong when it tries to run it.
I see that you are running in a virtual environment. Are you able to run other Javascript processes in there?
What happens if you just run the a test conversion using the sbol3to2 terminal command on a file in your user space from the command line?

Is it possible that node is not installed?
I get error code 127 from sbolgraph-standalone.js when node is not installed.
$ venv/lib/python3.8/site-packages/sbol_utilities/sbolgraph-standalone.js
env: node: No such file or directory
$ echo $?
127

Thanks Tom for your suggestion. I installed node and tried the code again. I think I've advanced in the error cascade and now I got the following error:

I review my SBOL3 document and it have some errors. I test with the document generated on the pySBOL3 circuit example (https://github.com/SynBioDex/pySBOL3/blob/main/examples/circuit.py). This example produce an SBOL3 document without error but once converted the SBOL2 document has 6 errors, is this expected?

After looking for ways inspect those errors I noticed that I used validate method in the same way in SBOL3 and SBOL2. So the 6 objects were nos errors but letter of Valid.. The function is working well thanks for your help!


Support for Softres.it CSV

Need to add another section inside of the Master Looter Settings tab for support for SoftRes.it CSV import.
Contents of section hidden / disabled unless user was Master Looter.
Contents of tab should clear whenever a user joins a Party / Raid.
Under Loot Destinations, above Ignored Items:

GogoLoot supports Softres.it; paste CSV code from website here to enable automatic distribution for this raid.

[Input box]

Format of Softres.it CSV
You can make a list here.
https://softres.it/
ItemId,Name,Class,Note,Plus
21503,Testname,Hunter,,2
21499,Testname,Hunter,,2

Output
On Save:
{standard loot destinations output}
{rt4} GogoLoot : Softres.it List Imported! {#} Reserves across {#} Items included.
On Loot:
When an item is looted:
{rt4} GogoLoot : Per Softres.it List, {item} goes to {Player1}!
or
{rt4} GogoLoot : Per Softres.it List, {item} will be rolled on by {Player1}, {Player2}, ...!

Few edge case thoughts.
When SR and Ignore conflict, SR wins and loot is handled by SR.
Once an item is looted via SR, it should be removed from the SR list. Possible for more than 1 item to drop, and not all are unique. Possible to get like 2 Cauterizing Bands... but only 1 should go via SR...
And again, if more than 1 person SR's an item, even if 2 drop off the same boss (super rare) we'd just toss the items in the ML's bag and announce a roll anyway.

What do you think about giving softres it's own tab? thats a lot to fit in vertically

Let's give SR it's own tab. Good call.
Also if it was meant to go to a player but we can't find that player...
{rt4} GogoLoot : Per Softres.it List, {item} goes to {Player1}... but we can't find {Player1}. The Master Looter will sort this out.

This is mostly implemented now, it just needs some testing

Need Checkbox for turning on SoftRes.it.


Highlight demo doesn't work in IE11

No cells are highlighted, nothing in console.

For some reason updateStyles doesn't work in IE11. Investigating further...


Fixed #27073 -- Fixed duplicated managers in _meta.managers.

Could you add a release note for 1.10.1?


Topographic bands mask_where modified: bottom bound <= band < top hav…

…ing previously both been <=
Reference issue if exists
Testing:

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

Failure caused by my failure to update expected results in unit tests. Amending these immediately.

new data will be required again after #324 is merged.

Just spotted that the epic description has these inequalities the other way around
https://exxreldocs:8099/display/TEPPV/Neighbourhood+Processing+and+spatial+filtering
:(

I've made many changes to this, rather than bounce it back and forth. I've added a concatenate cube call into the CLI so we get a cube out, rather than a cubelist. I've updated the unit tests to reflect the change in functionality (excluding the lower threshold value and including the upper), and I've recreated the acceptance test data. I've also fixed a pep8 problem. It needs another review before we merge it.

All done. We will need to revisit this for fuzzy masking at some point.


anonymous function called with unexpected argument 'target'

cargo2nix generates
# Cargo.nix
{
  drvs = genDrvsByProfile profilesByName (
    { profile, profileName }: mkRustCrate (
      { inherit release profile hostPlatformCpu hostPlatformFeatures
        target # FIXME
        profileOpts codegenOpts;
      } // (f profileName)
    )
  );
}

which throws
error: anonymous function at /nix/store/*/overlay/mkcrate.nix:10:1 called with unexpected argument 'target'

workaround: remove target from Cargo.nix

The overlay version & the cargo2nix used to generate the Cargo.nix must match.  Usually you need to update your overlay when this happens. :+1:


Closes #506

I've updated the version in pyproject.toml of main to 1.7.9 already.

Codecov Report

Merging #568 (9af9d9a) into main (63ebe48) will not change coverage.
The diff coverage is 86.66%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@           Coverage Diff           @@
##             main     #568   +/-   ##
=======================================
  Coverage   69.77%   69.77%
=======================================
  Files          97       97
  Lines       10422    10422
  Branches     1243     1243
=======================================
  Hits         7272     7272
  Misses       2865     2865
  Partials      285      285

Flag
Coverage Δ

unittests
69.77% <86.66%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...s/marc_rules_transformation/marc_file_processor.py
35.87% <ø> (ø)

...ols/marc_rules_transformation/rules_mapper_bibs.py
61.24% <0.00%> (ø)

...marc_rules_transformation/rules_mapper_holdings.py
67.58% <0.00%> (ø)

tests/test_mapping_file_mapper_base.py
97.95% <ø> (ø)

tests/test_rules_mapper_holdings.py
100.00% <ø> (ø)

src/folio_migration_tools/library_configuration.py
100.00% <100.00%> (ø)

...ols/marc_rules_transformation/rules_mapper_base.py
69.28% <100.00%> (ø)

...igration_tools/migration_tasks/bibs_transformer.py
67.92% <100.00%> (ø)

..._tools/migration_tasks/holdings_csv_transformer.py
30.12% <100.00%> (ø)

...tools/migration_tasks/holdings_marc_transformer.py
53.52% <100.00%> (ø)

... and 3 more

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


Seems some bad case

Expr: 0 0 */2 * 3
in https://crontab.guru/ expected:
at 2024-08-21 00:00:00
then at 2024-08-28 00:00:00
then at 2024-09-04 00:00:00
then at 2024-09-11 00:00:00
then at 2024-09-18 00:00:00
for this lib
import (
	"fmt"
	"testing"
	"time"

	"github.com/robfig/cron/v3"
)

func TestCronJob(t *testing.T) {
	expr, err := cron.ParseStandard("0 0 */2 * 3")
	fmt.Println(err)
	now := time.Now()
	for i := range 10 {
		nxt := expr.Next(now)
		fmt.Println("next", i, ":", nxt.String())
		now = nxt
	}
}

res:
next 0 : 2024-08-17 00:00:00 +0800 CST
next 1 : 2024-08-19 00:00:00 +0800 CST
next 2 : 2024-08-21 00:00:00 +0800 CST
next 3 : 2024-08-23 00:00:00 +0800 CST
next 4 : 2024-08-25 00:00:00 +0800 CST
next 5 : 2024-08-27 00:00:00 +0800 CST
next 6 : 2024-08-28 00:00:00 +0800 CST
next 7 : 2024-08-29 00:00:00 +0800 CST
next 8 : 2024-08-31 00:00:00 +0800 CST
next 9 : 2024-09-01 00:00:00 +0800 CST

I would claim both might be broken.  */2 maps to 1-31/2 which means all old days.  The day of week means Wednesday.  so do you OR the resulting sets or AND the resulting sets or do you ignore one of the resulting sets.   The GURU case is ignoring the day of the month and chose to use the day of the week only.
I would have said robfig ignored the day of the week, but I do not know where the 8-28 came from.

I would claim both might be broken. */2 maps to 1-31/2 which means all old days. The day of week means Wednesday. so do you OR the resulting sets or AND the resulting sets or do you ignore one of the resulting sets. The GURU case is ignoring the day of the month and chose to use the day of the week only.
I would have said robfig ignored the day of the week, but I do not know where the 8-28 came from since I do not know which crontab specification was used.
Using https://pubs.opengroup.org/onlinepubs/9699919799/utilities/crontab.html specification,
The opensgroup specification state it should be an OR, So guru is definitely broken and robfig is correct since 8-28 is an actual wednesday for the date range being shown.
There is a reason why the ? operator exists.

If so, I think this lib should return a error rather than a not correct result?

I would agree with you if we knew which specification this repo code was written to.   Since I did find a specification supporting  this cron's implementation, there is no error in this repo.   There is a very strong possibility that the guru repo has the error and should be generating an error.


Add more arguments to psense_summary

This also:

Reorder arguments, matching the order in arviz-plots. i.e. first general arguments like var_names and coords and then specific ones. Is this what we want? Or we want first the specific ones?
Add psense and psense_summary to the API documentation

📚 Documentation preview 📚: https://arviz-stats--34.org.readthedocs.build/en/34/

Regarding the last commit. Priorsense doesn't use a delta value. Instead, it allows users to pass lower and upper values for alpha independently.


Add guild scheduled events endpoints, gateway events, audit log, invite, and permissions changes.

Summary
Add something that has been documented in ddocs
What is the feature request for?
The core library
The Problem
https://github.com/discord/discord-api-docs/commit/1298152172d3359abf069d1b24d4bbc85532b735
The Ideal Solution
do it
The Current Solution
not doing it
Additional Context
https://canary.discord.com/channels/881118111967883295/881124672056467456/909890698873032745

ill have a go at this


Show event details on the left side

Instead of showing the calendar, let's show the event details.
Details Spec

repertoire
collaborators
map
link to external site

NOTE: by default, display closest upcoming event

After talking with daddy:
add day of week to list
also maybe add ability to share stuff via twitter/fb etc.

Both sounds like good ideas. I won't address them in this issue's PR though. I'll go ahead and add them as separate issues.


Cannot re-enable the submit button after failure.

General information

SDK version:     "braintree-web": "^3.62.1"
Environment: Sandbox 13.1, 146<IP_ADDRESS>.8, Mac OS X 10.14.6
Browser and OS: Safari

Issue description
Steps to reproduce:

Use the hosted fields to show CC#, CVV and expiration date.
Fill in the fields with valid test credit card values. When filled, notice that the Submit button is enabled, indicating the fields are valid.
Disconnect the computer from the network.
Press Submit.
Capture the network error in the JS.
Notice the fields are still filled and are still valid.
Set the disabled property of the Submit button to false to re-enable the button.
Hmmmm... sometimes it does not work; sometimes it works once or many times.

The entire JS code is below. Nothing is confidential.
Is there a better way to do this?
import braintree from "braintree-web"

//
// Begin custom JS for New Payment Method Page
//

const clientToken = document.getElementById('client_token').value;

braintree.client.create({
  authorization: clientToken
}, function (clientErr, clientInstance) {
  if (clientErr) {
    console.error(clientErr);
    return;
  }

  // This example shows Hosted Fields, but you can also use this
  // client instance to create additional components here, such as
  // PayPal or Data Collector.

  braintree.hostedFields.create({
    client: clientInstance,

    fields: {
      number: {
        selector: '#card_number',
        placeholder: ''
      },
      cvv: {
        selector: '#cvv',
        placeholder: ''
      },
      expirationDate: {
        selector: '#expiration_date',
        placeholder: ''
      }
    },

    styles: {
      'input': {
        'font-size': '14px',
        'box-shadow': 'inset 0 1px 2px rgba(0, 0, 0, 0.1)'
      },
      'input.invalid': {
        'color': 'red'
      },
      'input.valid': {
        'color': 'green'
      }
    },

  }, function (hostedFieldsErr, hostedFieldsInstance) {
    if (hostedFieldsErr) {
      console.error(hostedFieldsErr);
      return;
    }

    var form = document.querySelector('#braintree_form');
    var submit = document.querySelector('input[type="submit"][name="commit"]');
    $(submit).prop('disabled', true);

    hostedFieldsInstance.on('validityChange', function (event) {
      var fields = event.fields;
      var field = fields[event.emittedBy];
      var validState = fields.cvv.isValid && fields.expirationDate.isValid && fields.number.isValid;
      $(submit).prop('disabled', !validState);
    });

    form.addEventListener('submit', function (event) {
      event.preventDefault();

      hostedFieldsInstance.tokenize(function (tokenizeErr, payload) {
        if (tokenizeErr) {
          switch (tokenizeErr.code) {
            // occurs when the Braintree gateway cannot be contacted
            case 'HOSTED_FIELDS_TOKENIZATION_NETWORK_ERROR':
              // hostedFieldsInstance.clear('number');
              // hostedFieldsInstance.clear('cvv');
              // hostedFieldsInstance.clear('expirationDate');
              var state = hostedFieldsInstance.getState();
              var formValid = Object.keys(state.fields).every(function (key) {
                return state.fields[key].isValid;
              });

              $(submit).prop('disabled', !formValid);
              break;

            default:
              console.error('Something bad happened!', tokenizeErr);
          }
        }
        else {
          document.querySelector('#card_payment_method_nonce').value = payload.nonce;
          form.submit();
        }
      });
    }, false);
  });
});

//
// End custom JS for New Payment Method Page
//

Can you be more specific about what is happening when you try to submit again?
The Braintree SDK has no control over the disabled state of your button, so can you confirm that tokenize is being called on the hosted fields instance after you've re-enabled the button?
Does it pass back an error?

Thanks for your reply. Submit works just fine. There is no issue with that.
My issue is that something seems to interfere with the state of the button when I set disabled with the code $(submit).prop('disabled', !formValid);
It works intermittently -- so I was wondering if there are some machinations that are interfering.

I see. The issues is that you're setting the validity of the button based on the client side validity of the form.
In the case of a network based interruption, the client side validity would remain all valid, so the
button would always be disabled in this case.
In the case of a tokenization error, I would simply re-enable the button and disable it again only when tokenization is in process.


Python3 Compatibility

Hey there, I was doing some Python 3 transition work for my own code and since I was in the flow already I decided to port the Nuke implementation for Cryptomatte as well.
The changes are compatible with both Python 2 and Python 3. Integration tests run fine on Nuke 11 and 12 as well as the latest Nuke 13 Python3 Alphas (CentOS 7). I also encountered no problems in a bunch of manual testing in the meantime.

Hi, thanks for this contribution!
I found a couple issues with it, which I fixed in 1f5f3ba and c2cdf05. With those, I think everything works in both Python 2 and Python 3 nukes simultaneously. I have them in a python3 branch in this repo. I think this will mean changing what versions of Nuke we support as well, but I'm not sure.
Still needed, but I won't get to work on it for a bit - need to apply these changes to the wildcards branch for the beta version.

When this goes in I'm happy to add an entry to the VES Python 3 support tracker.

Thanks for looking into it. Regarding supported Nuke version, as far as I am aware Nuke 13 will be Python 3 only, so without the changes, the current master branch is only compatible to Nuke 7-12 as soon as that is released, the python3 changes do support Nuke 7+ as before.
Is it correct that the latest updates to the wildcard feature is in the dev branch? If I find the time I would look into merging the python3 changes into it.

Thanks for looking into it. Regarding supported Nuke version, as far as I am aware Nuke 13 will be Python 3 only, so without the changes, the current master branch is only compatible to Nuke 7-12 as soon as that is released, the python3 changes do support Nuke 7+ as before.
Is it correct that the latest updates to the wildcard feature is in the dev branch? If I find the time I would look into merging the python3 changes into it.

I made a small additional change to improve the support for older Nuke versions based on Python 2.6. I noticed the integration tests throw some errors on these, which is already the case for the latest master branch.

I made a small additional change to improve the support for older Nuke versions based on Python 2.6. I noticed the integration tests throw some errors on these, which is already the case for the latest master branch.

Thanks JF and @PumpingPixels.
I have updated both the Python3 and dev branches. The main branch will be released as 1.3.0 (e178e35), and the wildcards beta is released as 1.4.0-beta4. I think we're about ready to release the main one too, perhaps after doing a bit of manual testing to sanity check the automated tests.
As for Nuke 6, I can't test with it and I realized we already only claim support for Nuke 7+, so I think we can just say Nuke 6 is not supported.

Thanks JF and @PumpingPixels.
I have updated both the Python3 and dev branches. The main branch will be released as 1.3.0 (e178e35), and the wildcards beta is released as 1.4.0-beta4. I think we're about ready to release the main one too, perhaps after doing a bit of manual testing to sanity check the automated tests.
As for Nuke 6, I can't test with it and I realized we already only claim support for Nuke 7+, so I think we can just say Nuke 6 is not supported.

I am aware that only support for 7+ is claimed, but Nuke versions based on Python 2.6 include Nuke 7.  Having a quick look this seems to be due to the fact the the tests use assertion methods introduced in Python 2.7.
This is going a bit off topic, my point was hat with the latest additions, the Python3 compatibility doesn't introduce any errors that aren't already present in the master branch, at least in regards to the tests.

I am aware that only support for 7+ is claimed, but Nuke versions based on Python 2.6 include Nuke 7.  Having a quick look this seems to be due to the fact the the tests use assertion methods introduced in Python 2.7.
This is going a bit off topic, my point was hat with the latest additions, the Python3 compatibility doesn't introduce any errors that aren't already present in the master branch, at least in regards to the tests.

This is now released, thank you for the contribution!
I've increased the minimum version to Python 2.7 / put Nuke 8 in the release notes. Realistically, I can't test Nuke 8 anymore either.