Search for products among multiple providers

Original request made by @geonux :

To be able to search for all available data on all providers over a given AOI

We decided that the best way to approach this was to add a providers list parameter to the search method. A list of all the providers can be retrieved with dag.available_providers(). But a user could also provide a subset of the available providers:
dag.search(args, providers=["theia", "sobloo"])

Note that there is already a provider kwarg that the user can pass to search and that is used by _search_by_id (for performance reasons, if the user already knows if a given provider has this product available).
Note that the search command doesn't accept any --provider option.
For retrieving all the product types, we have to deal with the already used productType parameter. Options would be:

change search API and use productType as a list;
keep it as str, and if empty, use whoosh to find matching product types using other criteria (level, platform, ...)

Note here that dag.list_product_types(provider) could come in handy if productType accepts a list of product types.
TODOs before working on a MR:

[ ] Check whether dag.available_providers returns a correct list, and also whether they are ordered given their priority (if we want to preserver the providers priority here)
[ ] Analyze how whoosh currently influences the search with productType being defined or not
[ ] Make a decision about how to let the user select multiple product types at once and all of them

Here is a snippet that allows to search for all the products available on all the providers in a given area of interest (around Toulouse here) some time in August 2020:
from eodag import EODataAccessGateway
from eodag.api.search_result import SearchResult
from eodag.utils.logging import setup_logging
setup_logging(verbose=1)
dag = EODataAccessGateway()
search_criteria = dict(
    start='2020-08-01',
    end='2020-08-10',
    geom=[0, 43, 2, 45],
)
all_prods = SearchResult([])
for provider in dag.available_providers():
    product_types = (
        p["ID"]
        for p in dag.list_product_types(provider=provider)
        if p["ID"] != "GENERIC_PRODUCT_TYPE"
    )
    for product_type in product_types:
        dag.set_preferred_provider(provider=provider)
        try:
            results = dag.search_all(productType=product_type, **search_criteria)
        except Exception:
            print(f"Failed to collect '{product_type}' products with '{provider}'")
            results = []
        print(f"Got {len(results)} '{product_type}' products with '{provider}'")
        all_prods.extend(results)
print(f"Got a total of {len(all_prods)} products.")

(I got 1090 products)

@geonux since you're at the origin of this issue, I would like to ask you a few questions about it if I may.

To be able to search for all available data on all providers over a given AOI

I think it can be translated into two different ways:

To get all the products from all the providers
To get all the unique products from all the providers

Indeed, it is quite sure that were will be duplicate products (both provider A and B offer the same product i) from a search over the same AOI and time period.
If you are interested in 1., the snippet above should get you what want. Would it be enough to document it?
If you are interested in 2., this is trickier. We would need to remove duplicate products. We could rely on the product unique identifier, however, as shown in https://github.com/CS-SI/eodag/issues/136#issuecomment-808082569, we can't always make sure that different providers use the same id (surprisingly!). So there may still be some duplicates after an id filter. We could also rely on a combination of properties, and remove duplicates if 2 or more products share the same combination of, for instance, product_type / geometry / start date / end date.
Removing duplicates based on the id can be done as follows:
almost_unique_prods = SearchResult({p.properties["id"]: p for p in all_prods[::-1]}.values())

An attempt to remove potential duplicate products from almost_unique_prods could be done as follows:
unique_prods = SearchResult({
    (p.properties["startTimeFromAscendingNode"], p.geometry.wkt, p.product_type): p
    for p in almost_unique_prods[::-1]
}.values())

If we implement 2., internally we could add __eq__ (and __hash__?) to the EOProduct class, to specify how we define whether two products are the same or not.
Note the reverse order on all_prods and almost_unique_prods in the dict comprehension above. Its aim is to ensure that, if there are duplicate products, the one that end up in unique_prods is the one obtained from the first provider (the first one that offered this product). If we implement 2. we should ensure this priority is preserved, e.g. search_all(geom=..., start=..., end=..., providers=["peps", "sobloo"]) should return products from peps in priority.
If we decide to implement 1. or 2., where should add this?

search_all: it seems like an obvious candidate => Yes?
search: since it returns a given page of a search, I believe it assumes the search is done on a single provider => No?
search_iter_page: I see it being used by advanced users, who may want to implement this (search all products from all providers) in a different way than what we'll do => No?

Having differently formatted ids for the same products, depending on the providers must be fixed.
But this is also related to the fact that some providers are not (yet) configured to return Sentinel products in SAFE format. See #216  and #171


Docs: Update custom chat model

Clean up in the existing tutorial
Add model_name to identifying params
Add table to summarize messages

I have a mistake in the documentation --need to fix prior to landing


Add SearchableComboBox

Design TBD, but this is something I keep running into, and would really like to have out of the box.

Partially addressed in the upcoming Windows 10 Anniversary update.
Source: https://channel9.msdn.com/Events/Build/2016/B853 at about 48:00.

Did some brief prototyping, and it looks like just inheriting from ComboBox and playing with the styling a little bit isn't going to be enough. It looks like if we want this, we might have to completely reimplement a new ComboBox from scratch.


s2u-46 5.3.1: Update Messages_ca.properties

@DavidVegaSa Good job so far, do you think the CA translation is ready?

@DavidVegaSa Good job so far, do you think the CA translation is ready?

now yes


Fix missing LC supersampling

In evaluate_model(), when it gets a user-supplied time vector, supersampling parameters were never passed on to batman/catwoman, resulting in wrong lightcurves being generated. I saw this when plotting the lightcurve of a K2 planet with particularly long ingress/egress, which made it very visible .
In this pull request, I have taken the liberty of removing keyword arguments resampling, nresampling, and etresampling from evaluate_model(). Instead I make sure that it always gets the supersampling parameters that were used in the fit via self.dictionary, as it was already done some places.

Thanks for this @tronsgaard! Adding it to the dev branch and merging later to master!


Unable to Install Steem for Python (VS 2015/2017)

I am unable to install the Steem module for Python. I first attempted to install VS Community 2017 and the latest Build Tools and subsequently, VS Community 2015 and 2015 Build Tools. Each version and combination result in the same error.
I've also tried running the pip install -U steem command from the VS command line as well.
Version of Python you are running
3.6.5
Version of steem-python you are running
Installation Attempt - 1.0
Expected Behavior
Full Installation
Actual Behavior
**warning: GMP or MPIR library not found; Not building Crypto.PublicKey._fastmath.
building 'Crypto.Random.OSRNG.winrandom' extension
error: Microsoft Visual C++ 14.0 is required. Get it with "Microsoft Visual C++ Build Tools": http://landinghub.visualstudio.com/visual-cpp-build-tools**

----------------------------------------

Command "c:\python36\python.exe -u -c "import setuptools, tokenize;file='C:\Users\\AppData\Local\Temp\pip-install-h0xsk1qe\pycrypto\setup.py';f=getattr(tokenize, 'open', open)(file);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, file, 'exec'))" install --record C:\Users*\AppData\Local\Temp\pip-record-dlsh6zuo\install-record.txt --single-version-externally-managed --compile" failed with error code 1 in C:\Users***\AppData\Local\Temp\pip-install-h0xsk1qe\pycrypto\
Steps to reproduce
Attempt fresh install of steem

PyCrypto is broken and it is not possible to compile it on windows without patching it first. Patches can be found in the conda feedstock for example.

Try conda install steem

(base) C:\Users\A>conda install steem
Solving environment: failed
PackagesNotFoundError: The following packages are not available from current channels:

steem

Current channels:

https://repo.continuum.io/pkgs/main/win-64
https://repo.continuum.io/pkgs/main/noarch
https://repo.continuum.io/pkgs/free/win-64
https://repo.continuum.io/pkgs/free/noarch
https://repo.continuum.io/pkgs/r/win-64
https://repo.continuum.io/pkgs/r/noarch
https://repo.continuum.io/pkgs/pro/win-64
https://repo.continuum.io/pkgs/pro/noarch
https://repo.continuum.io/pkgs/msys2/win-64
https://repo.continuum.io/pkgs/msys2/noarch

(base) C:\Users\A>

Sorry, my tip was not complete:
conda config --add channels conda-forge
conda install steem

Thank you, this solved it!

@roadscape - Seems we need a spike or quick discussion how/if we're going to handle supporting Windows machines. I'm not sure if I want to be running tests against multiple environments as we already have 5 test suites to run, this would start driving our testing complexity way up, but it may be desirable if we want to have first class support for windows.

@cyon1c - not sure we need tests for Windows but thinking we might want to include these tips in the README.

I'm the maintainer of https://github.com/conda-forge/steem-feedstock.
@roadscape - You can find a detailed installation guide in the readme file.
Feel free to copy the badges.


Fixing the publish script to push to the new myget feed

Fixing the publish script to push to the new myget feed
/cc @KrzysztofCwalina @eerhardt

No code changes have occurred so no build is needed

LGTM

Thanks Eric!


Set NUnit.ConsoleRunner to latest version, 3.16.3.

Hopefully this will make the unit tests work again...

I agree about the deprecation. I got multiple warnings when creating it 😄

@SeanFeldman , I believe you missed that I deleted the ruleset file.


ScrollBehavior issue

Describe the bug
Hey!
You have a great library.
I have a few question, I don't know if it's a bug or a feature.
I was experimenting with the new option in nuxt definePageMeta.scrollToTop, and noticed that it is called several times if the schema-org module is activated.
Also, the scrollToTop function is called on the server side.
This behavior is also observed with npm run build && npm run preview
I tried changing the reactive option, it got better, instead of 3 triggers, it got 2, also it's still being called on the server.

npm run dev, reactivity:default, server:1, client:3

npm run dev, reactivity:false, server:1, client:1

npm run preview, reactivity:default, server:1, client:2

npm run preview, reactivity:false, server:1, client:2

Reproduction
https://stackblitz.com/edit/nuxt-starter-wxf2mo
System / Nuxt Info
No response

Hey @or2e, good catch! Thank you for the detailed issue.
This should hopefully be fixed in 3.1.6.


fix(isolated_declarations): Infer type of template literal expressions as string

In a "non-const" context, a template literal string can just be inferred a string. This is consistent with TypeScript's behavior.

The infer_type_from_expression method can infer TemplateLiteral as a string.  But there is a mistake here, when expression exists but can be inferred, we should infer that it is a string type
https://github.com/oxc-project/oxc/blob/adee7280d74a05e5443630ee52ee7b42017489b4/crates/oxc_isolated_declarations/src/inferrer.rs#L28-L34

@Dunqing I've updated the logic. Please have another look.


Multi-node multi-GPUs training is slower than single-node multi-GPUs training[BUG]

Describe the bug
I utilized zero-stage3 of Deepspeed for fine-tuning the Qianwen2-1.5b model and observed that the training speed of 2 nodes with total 4 A10 GPUs is one time slower than that of single node with total 2 A10 GPUs.  Here are some details.
The training speed of 2 nodes with total 4 A10 GPUs：

The training speed is about 8.68s/iter, and  the forward  latency, backward latency is 1.6s, 2.51s.
However, the training speed of single node with total 2 A10 GPUs：

The training speed is about 2.46s/iter, and  the forward  latency, backward latency is 357ms, 673ms.
The above results show that the training speed of 2-node 4GPUs is much slower than that of single-node GPUs in feedforward and feedback processes. I thought it was a bandwidth problem of network, but my calculations showed it wasn't as follws：
The average receiving and sending bandwidths during the training were 8.74Gbit/s and 9.28Gbit/s, respectively.
model weights size: 1.5*(10^8)*16bit, gradient size: 1.5*(10^8)*16bit, the communication consume is：
3*1.5*(10^8)*16bit/2/(8.74*(10^9))=0.41s.
So I want to know what's wrong with the results?  I'd like to ask for people's help.
Thanks!

@yangkang2318, the model weight size should be 1.5*(10^9)16 instead of 1.5(10^8)*16.

@yangkang2318, the model weight size should be 1.5*(10^9)16 instead of 1.5(10^8)*16.
Thanks! I'm so foolish!

@duli2012 Thanks! I'm so foolish!


'postgres' user not being created on Ubuntu Server 15.04

My chef/knife run completes successfully. When I ssh into my newly created system and 'sudo su - postgres' it seems that I am now the postgres user, but I'm not.
whoami   #=> postgres
id -u        #=> returns uid for user: uuid
id -g        #=> returns gid for group: ssh

The server does not start. Contents of /var/log/postgresql/*.log:
2015-08-12 12:10:51 GMT LOG:  database system was shut down at 2015-08-12 12:10:46 GMT
2015-08-12 12:10:51 GMT LOG:  MultiXact member wraparound protections are now enabled
2015-08-12 12:10:51 GMT LOG:  database system is ready to accept connections
2015-08-12 12:10:51 GMT LOG:  autovacuum launcher started
2015-08-12 12:10:51 GMT LOG:  incomplete startup packet
2015-08-12 12:11:21 GMT LOG:  received fast shutdown request
2015-08-12 12:11:21 GMT LOG:  aborting any active transactions
2015-08-12 12:11:21 GMT LOG:  autovacuum launcher shutting down
2015-08-12 12:11:21 GMT LOG:  shutting down
2015-08-12 12:11:21 GMT LOG:  database system is shut down
2015-08-12 12:11:22 GMT FATAL:  could not access private key file "/etc/ssl/private/ssl-cert-snakeoil.key": Permission denied

Some investigation into the referenced key:
postgres@cb-dbtest01:~$ ls -la /etc/ssl/private/ssl-cert-snakeoil.key
-rw-r----- 1 root ssl-cert 1704 Aug 12 08:10 /etc/ssl/private/ssl-cert-snakeoil.key
postgres@cb-dbtest01:~$ cat /etc/group | grep ssl
ssl-cert:x:120:postgres

My recipe/attributes is basically a copy-n-paste from the README... I don't think I'm committing any unnatural acts here. Thoughts?

UPDATE: I created an identical VM template based off Ubuntu Server 14.04.2 LTS and ran the same recipe and PostgreSQL installed and started just fine. Suspect this is, indeed, a Server 15.04 problem.

Log output from another run (cat /var/log/postgresql/*.log)
2015-08-13 17:27:56 GMT LOG:  could not bind IPv6 socket: Cannot assign requested address
2015-08-13 17:27:56 GMT HINT:  Is another postmaster already running on port 5432? If not, wait a few seconds and retry.
2015-08-13 17:27:56 GMT LOG:  database system was shut down at 2015-08-13 17:27:52 GMT
2015-08-13 17:27:56 GMT LOG:  MultiXact member wraparound protections are now enabled
2015-08-13 17:27:56 GMT LOG:  database system is ready to accept connections
2015-08-13 17:27:56 GMT LOG:  autovacuum launcher started
2015-08-13 17:27:57 GMT LOG:  incomplete startup packet
2015-08-13 17:28:03 GMT LOG:  received fast shutdown request
2015-08-13 17:28:03 GMT LOG:  aborting any active transactions
2015-08-13 17:28:03 GMT LOG:  autovacuum launcher shutting down
2015-08-13 17:28:03 GMT LOG:  shutting down
2015-08-13 17:28:03 GMT LOG:  database system is shut down
2015-08-13 17:28:04 GMT FATAL:  could not access private key file "/etc/ssl/private/ssl-cert-snakeoil.key": Permission denied


[BUG] Exit process when database init fails

Describe the bug
Flowise process continue to live if database initialisation raise an exception. To make the application works better with orchestrators such as Kubernetes, the process should exit.
To Reproduce
Configure Flowise with an SQL database with a wrong database hostname.
Expected behavior
The application should exit.
Setup

Installation [e.g. docker + kubernetes]
Flowise Version 1.3.1
OS: Linux

feel free to make a PR for that!


  Saying "install the  [coderefinery] conda environment" is quite similar to "install the anaconda environment" and it is easy to think it is already there.
A default anaconda environment seems to mostly work.
Ideas:

See what important packages are missing from the default environment [the only one I saw last week was myst-parser, note it is in conda-forge only]
Add a note saying "want to use your existing conda environment?  Do this."
Add notes in the relevant lessons saying what to do if you have a default conda environment (e.g. documentation: conda install -c conda-forge myst-parser)
reproducible-research exercise that explains the coderefinery environment and has people who haven't installed it yet install it?  Maybe do it as a demo with pointed reminder to do it before the next day?  Shouldn't make people feel bad if they have done it in advance and they are bored then, though.

This is a great idea and I will consider adding this as exercise.

I think the install instructions comment enough on this already. Moving this to "reproducible research" lesson for consideration whether it should be an exercise or not.


Should Bolt allow partial edits by default?

Consider this simple type and path.
path /private/{uid}/{id} is SecretMessage {
  read() { auth.uid == uid }
  write() { auth.uid == uid }
}

type SecretMessage {
    uid: String,
    message: String,
    timestamp: Number,
    isModerator: Boolean
}

This generates
{
  "rules": {
    "private": {
      "$uid": {
        "$id": {
          ".validate": "newData.hasChildren(['uid', 'message', 'timestamp', 'isModerator'])",
          "uid": {
            ".validate": "newData.isString()"
          },
          "message": {
            ".validate": "newData.isString()"
          },
          "timestamp": {
            ".validate": "newData.isNumber()"
          },
          "isModerator": {
            ".validate": "newData.isBoolean()"
          },
          "$other": {
            ".validate": "false"
          },
          ".read": "auth.uid == $uid",
          ".write": "auth.uid == $uid"
        }
      }
    }
  }
}

This requires that any create or update operation include ALL of those children. This means you cannot do partial updates. I would argue that this is too strict. The alternative is to make all those Type|Null which is too loose.
I suggest that we generate the offending .validate line as such:
 ".validate": "newData.hasChildren(['uid', 'message', 'timestamp', 'isModerator']) ||
 data.hasChildren(['uid', 'message', 'timestamp', 'isModerator']",

Nevermind, I think I'm doing something wrong.


thread 'main' panicked at 'Unable to find libudev

ERROR
thread 'main' panicked at 'Unable to find libudev: Command { command: ""pkg-config" "--libs" "--cflags" "libudev"", cause: Os { code: 2, kind: NotFound, message: "No such file or directory" } }', /home/oguz/.cargo/registry/src/github.com-1ecc6299db9ec823/hidapi-1.3.2/build.rs:55:54
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace
SOLUTION
sudo apt-get -y install libudev-dev

This comes up enough I'll add something to the docs, thanks.

Added to the docs.


some files are available by default even outside the webroot

Description
In my project which has no custom static files configuration, there are files that are available outside of the webroot;
they are located here:
contentroot\.well-known\acme-challenge\verylongfilename
I thought maybe .well-known is reserved, and I tried copy pasting the folder with a different name
contentroot\aaa\acme-challenge\verylongfilename
contentroot\bbb\acme-challenge\verylongfilename
and these new files were also available from the browser, just by writing
example.com\aaa\acme-challenge\verylongfilename
UPDATE:
I noticed this probably works because of a web.config file inside the acme-challenge folder,
however this file doesn't seem to have any effect when running the app via docker (not IIS)
Page URL
https://learn.microsoft.com/en-us/aspnet/core/fundamentals/static-files?view=aspnetcore-8.0
Content source URL
https://github.com/dotnet/AspNetCore.Docs/blob/main/aspnetcore/fundamentals/static-files.md
Document ID
3fec6e08-fc99-7a5c-796f-3f2347cad891
Article author
@Rick-Anderson

Can you post to a public GitHub repo the simplest possible sample that reproduces this problem?

@Rick-Anderson
Looks like it is an IIS specific feature,
when running with IISExpress, you can have a folder in your ContentRoot with a web.config like this:
<?xml version = "1.0" encoding="UTF-8"?>
 <configuration>
    <system.webServer>
        <staticContent>
            <mimeMap fileExtension="." mimeType="text/plain" />
        </staticContent>
        <handlers>
            <clear />
            <add name="StaticFile" path="*" verb="*" type="" modules="StaticFileModule,DefaultDocumentModule,DirectoryListingModule" scriptProcessor="" resourceType="Either" requireAccess="Read" allowPathInfo="false" preCondition="" responseBufferLimit="4194304" />
        </handlers>
     </system.webServer>
 </configuration>

and you can access via the url its files, but when running with http (kestrel) and docker also uses Kestrel, this web.config has no effect whatsoever


contexts feature for c-3po lib

According to this proposal https://github.com/c-3po-org/c-3po/issues/65 we should implement contexts feature.
Example:
import { c, t } from 'c-3po'
c('context').t`Hello ${ user.name }`

// maybe better to place it on a separate lines
c('context')
.t`Hello ${ user.name}`

done in 0.7.0-release branch


requirements.txt - HighRisk Vulnerability

Reference: werkzeug - Remote Code Execution (RCR)
Detailed paths and remediation
Introduced through<EMAIL_ADDRESS>›<EMAIL_ADDRESS>Fix: Upgrade werkzeug to version 3.0.3
Introduced through<EMAIL_ADDRESS>›<EMAIL_ADDRESS>›<EMAIL_ADDRESS>Fix: Pin werkzeug to version 3.0.3
Introduced through<EMAIL_ADDRESS>›<EMAIL_ADDRESS>›<EMAIL_ADDRESS>Fix: Pin werkzeug to version 3.0.3
…and 1 more
Security information
Factors contributing to the scoring:
Snyk: CVSS v3.1 7.5 - High Severity
NVD: Not available. NVD has not yet published its analysis.
Why are the scores different? Learn how Snyk evaluates vulnerability scores
Overview
Affected versions of this package are vulnerable to Remote Code Execution (RCE) due to insufficient hostname checks and the use of relative paths to resolve requests. When the debugger is enabled, an attacker can convince a user to enter their own PIN to interact with a domain and subdomain they control, and thereby cause malicious code to be executed.
The demonstrated attack vector requires a number of conditions that render this attack very difficult to achieve, especially if the victim application is running in the recommended configuration of not having the debugger enabled in production.

Fixed in https://github.com/CSGY-9223-Group4/lab1/pull/7


Add support of RocksDB options file

Change Description

Add RocksDB options file support. Options file is specified by command line argument --rdb-options-file-name. The file must follow INI file format. If --rdb-options-file-name is present, --rdb-threads and --rdb-max-files are ignored.
A sample file looks like
[DBOptions]
  create_if_missing=true
  max_open_files=768
  max_background_jobs=20
[CFOptions "default"]
  compaction_style=kCompactionStyleLevel
  level0_file_num_compaction_trigger= 0
  level0_slowdown_writes_trigger=20
  level0_stop_writes_trigger=40
  write_buffer_size=268435456
  target_file_size_base=268435456
  max_bytes_for_level_base=268435456
[TableOptions/BlockBasedTable "default"]
  format_version=4
  index_block_restart_interval=16

Change Type
Select ONE:

[ ] Documentation

[ ] Stability bug fix

[ ] Other

[ ] Other - special case

Testing Changes
Select ANY that apply:

[ ] New Tests

[ ] Existing Tests

[ ] Test Framework

[ ] CI System

[x] Other

Manual testing.
Consensus Changes

[ ] Consensus Changes

API Changes

[ ] API Changes

Documentation Additions

[ ] Documentation Additions

I tested this and it looks good.   I tested it for a few different scenarios:

Starting with a clean slate RocksDB (i.e. rodeos).

It reads the supplied OPTIONS file, and starts rodeos and creates a new OPTIONS file within its active working directory with the specified custom options implemented.

Restarting a Rodeos with updated changes.

It takes into account the new changes, creates a new OPTIONS file in its active working directory. Note: the first OPTIONS file is still present but not actively in use.

When options file can't be found.

Rodeos errors out with exception (options file <path/file_name> does not exist and Rodeos does not start.

With an invalid option specified in the OPTIONS file.

RocksDB throws an error when trying to OPEN the DB (rocksdb::DB::Open (options files): Invalid argument) and Rodeos does not start.

Rodeos responded in a positive way in all scenarios.


[rpc][structured-error-handling][2/n] State trait for AuthorityState, group AuthorityState-originating SuiErrors

Description
Part of the first set of PRs is to group the errors that are possible on the RPC today into a few categories transparently, setting us up to eventually standardize error strings and resolution. This PR specifically introduces a State trait which AuthorityState implements to centralize AuthorityState-originating SuiErrors so that we can disambiguate these errors from other sources of SuiError. This has the added benefit of helping w/ unit test writing, as demonstrated by coin_api and move_utils.
No change has been made to error strings, but StateReadError::Internal will now code to -32603 instead of -32000. But this can be negotiable too.
Test Plan
Existing tests

If your changes are not user-facing and not a breaking change, you can skip the following section. Otherwise, please indicate what changed, and then add to the Release Notes section as highlighted during the release process.
Type of Change (Check all that apply)

[ ] protocol change
[x] user-visible impact
[x] breaking change for a client SDKs
[ ] breaking change for FNs (FN binary must upgrade)
[ ] breaking change for validators or node operators (must upgrade binaries)
[ ] breaking change for on-chain data layout
[ ] necessitate either a data wipe or data migration

Release notes

Approved with the above suggestions applied


Release version 2.8.0

This is a component issue for 2.8.0.
Coming from opensearch-build#3434. Please follow the following checklist.
Please refer to the DATES in that post.
How to use this issue

This Component Release Issue
This issue captures the state of the OpenSearch release, on component/plugin level; its assignee is responsible for driving the release. Please contact them or @mention them on this issue for help.
Any release related work can be linked to this issue or added as comments to create visiblity into the release status.
Release Steps
There are several steps to the release process; these steps are completed as the whole component release and components that are behind present risk to the release. The component owner resolves the tasks in this issue and communicate with the overall release owner to make sure each component are moving along as expected.
Steps have completion dates for coordinating efforts between the components of a release; components can start as soon as they are ready far in advance of a future release. The most current set of dates is on the overall release issue linked at the top of this issue.
The Overall Release Issue
Linked at the top of this issue, the overall release issue captures the state of the entire OpenSearch release including references to this issue, the release owner which is the assignee is responsible for communicating the release status broadly.  Please contact them or @mention them on that issue for help.
What should I do if my plugin isn't making any changes?
If including changes in this release, increment the version on __2.x__ branch to __2.8.0__ for Min/Core, and __<IP_ADDRESS>__ for components. Otherwise, keep the version number unchanged for both.

Preparation

[ ] Assign this issue to a release owner.
[ ] Finalize scope and feature set and update the Public Roadmap.
[ ] All the tasks in this issue have been reviewed by the release owner.
[ ] Create, update, triage and label all features and issues targeted for this release with v2.8.0.

CI/CD

[ ] All code changes for 2.8.0 are complete.
[ ] Ensure working and passing CI.
[ ] Check that this repo is included in the distribution manifest.

Pre-Release

[ ] Update to the 2.8 release branch in the distribution manifest.
[ ] Increment the version on the parent branch to the next development iteration.
[ ] Gather, review and publish release notes following the rules and back port it to the release branch.git-release-notes may be used to generate release notes from your commit history.
[ ] Confirm that all changes for 2.8.0 have been merged.
[ ] Add this repo to the manifest for the next developer iteration.

Release Testing

[ ] Find/fix bugs using latest tarball and docker image provided in parent release issue and update the release notes if necessary.
[ ] Code Complete: Test within the distribution, ensuring integration, backwards compatibility, and performance tests pass.
[ ] Sanity Testing: Sanity testing and fixing of critical issues found.
[ ] File issues for all intermittent test failures.

Release

[ ] Complete documentation.
[ ] Verify all issued labeled for this release are closed or labelled for the next release.
[ ] Verify the release date mentioned in release notes is correct and matches actual release date.

Post Release

[ ] Prepare for an eventual security fix development iteration by incrementing the version on the release branch to the next eventual patch version.
[ ] Add this repo to the manifest of the next eventual security patch version.
[ ] Suggest improvements to this template.
[ ] Conduct a retrospective, and publish its results.

@monusingh-1

I will pick it up

Sanity test completed on release candidate opensearchstaging/opensearch:<IP_ADDRESS>29

@monusingh-1
We have failing integration tests for the 2.8 release.  These are causing the SQL integration tests for the 2.8 release to fail.
https://github.com/opensearch-project/cross-cluster-replication/issues/843, https://github.com/opensearch-project/cross-cluster-replication/issues/825, https://github.com/opensearch-project/cross-cluster-replication/issues/824
Is there anyone available to take a look at fix these failing integration tests?

As confirmed by you offline, CCR was not the reason for failures in SQL integration test.

As confirmed by you offline, CCR was not the reason for failures in SQL integration test.

That's correct.  The root cause of the issues did not involve CCR.


Speed up TabletExternallyReparented.

@alainjobart
This adds an alternate implementation of TabletExternallyReparented
that reduces the client-visible downtime for a reparent by making sure
the serving graph sees the new master ASAP. The rest of topology is
then reconciled as necessary.
The new implementation is only used when the -fast_external_reparent
flag is enabled on vttablet. This flag is currently off by default.

Coverage decreased (-0.21%) when pulling 021d4f2b8f08fb41c841431ad223b6614db3484f on fast-external-reparent into 80fe5a66539e746eefbf37d90bc274314a1f6f38 on master.

Looks good overall. Nice to have put all this behind a flag for easier roll out.
Can you please also update the unit test in wrangler/testlib to run with the new flag?

Coverage decreased (-0.12%) when pulling ba456ac17ccabf8e2db080b2c769441dc3211920 on fast-external-reparent into 80fe5a66539e746eefbf37d90bc274314a1f6f38 on master.

Coverage decreased (-0.1%) when pulling 0be6289887f277c50d3968c9bc56e158ccac5b4a on fast-external-reparent into 80fe5a66539e746eefbf37d90bc274314a1f6f38 on master.

Coverage decreased (-0.11%) when pulling a2e3d87a6b59e8c6a6de4dfd0f2144c77ab6be8b on fast-external-reparent into 80fe5a66539e746eefbf37d90bc274314a1f6f38 on master.

I added tests for the new flag in wrangler/testlib. PTAL.

LGTM


Django 1.9 support?

Django 1.9 is now officially out, is this on the near roadmap for feincms?
I'm getting an immediate bug after an upgrade:
  File "/home/ubuntu/workspace/parlhand/extra/pages/pages.py", line 31, in <module>
    ('main', _('Main content area'), 'inherited'),
  File "/usr/local/lib/python2.7/dist-packages/feincms/models.py", line 425, in register_templates
    field.default = field.choices[0][0]
IndexError: list index out of range

When calling this code which worked previously:
Page.register_templates({
    'title': _('Standard template'),
    'path': 'cms_page/page.html',
    'regions': (
        ('main', _('Main content area'), 'inherited'),
        #('sidebar', _('Sidebar'), 'inherited'),
    ),
},
{
    'title': _('Full page template'),
    'path': 'cms_page/fullpage.html',
    'regions': (
        ('main', _('Main content area'), 'inherited'),
        #('sidebar', _('Sidebar'), 'inherited'),
    ),
})

And printing field and field.choices gives:
page.Page.template_key []

+1
@LegoStormtroopr as @matthiask pointed out, the next branch fixes this issue, see https://github.com/feincms/feincms/commit/7e09d9c821d9dbd72cf60c19708f91a3248d3b95

Thanks. The next branch also contains many unrelated changes which will certainly break everyone's code.
We are working on a patch release for 1.11.x which will solve those issues soon, hopefully.

Progress here: https://github.com/feincms/feincms/tree/next_1.x

Thanks for the update @matthiask . FeinCMS is great :D
Having looked at a number of other packages, Django1.9 migration will be a slow process for a lot of people.

One of the problems we're facing is that there is no Django 1.9-compatible release of django-mptt yet.
(Help wanted! https://github.com/django-mptt/django-mptt/issues/415)

@matthiask thanks for your (fast) work on 1.11.12! are you taking about <class 'feincms.module.page.modeladmins.PageAdmin'>: (admin.E023) The value of 'radio_fields' refers to 'template_key', which is not an instance of ForeignKey, and does not have a 'choices' definition.?

Damn. Django really does not make it easy.
Try 1.11.3 :-) please.

looks good! thx a lot, now it's up to mptt :)

Great! So, let's close this issue :)


Changes according to breaking changes in OpenLayers 4.0.0

Changes according to breaking changes in OpenLayers 4.0.0 at https://github.com/openlayers/openlayers/releases/tag/v4.0.0
Change ol.View.fit to reflect changes in OpenLayers.
Use EventKey for Observable event listeners. Does not break anything as it extends JavaScriptObject, which was used before - but allows type additional type checking.
Cleanup methods deprecated more than two releases ago.
This helps to clean up OLUtil, OLFactory and MeasureEvent and reduces the number of helper methods on top of the original OpenLayers code.

Great! Thanks!


notify: remove wechat unit test

Fixes #1348.

:+1: Sad to not have any test coverage for the WeChat provider, but better than doing a call to a live system in a unit test.

True. But, part of the deal for adding wechat was that someone using it would maintain it. If it gets in the way of the rest of our test suite, the onus is on them.

Aggreed, thanks for investigating.
On Mon, 30 Apr 2018, 20:01 stuart nelson<EMAIL_ADDRESS>wrote:

Merged #1350 https://github.com/prometheus/alertmanager/pull/1350.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/prometheus/alertmanager/pull/1350#event-1602078566,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGuKs5MtqW9g1qr5WtXOKnQKzQ87jlq6ks5tt1GFgaJpZM4TsvtX
.

/cc @berlinsaint


way to use in iPhone and iPad App

I am newbie in the field of computer vision. I have gone through a lot of documentation and OpenCV docs. I tried to understand the algorithms also , even I also applied the FAST, SURF, SIFT, ORB and others for detecting key-points and descriptors and for match with the Image applied the BruteForce, FLANN (using Knnmatch also). They all are working fine for a single Image or a group of 10 Images. In the terms of iOS I stored the Images key-points and descriptors using the FIleManager in .yml format. and Later on fetch by using loop of number of count of Images to match one by one. When I tried to match with a 100 Images , it is taking approx 10 seconds to move through the whole loop.
can it possible to use this architecture for matching Image. I am working on scenario where I have 1000 of Images and then when I will take a picture from camera , it will go through the whole Image and return the best identical Image.

@AtulPrakash007 , such questions better be asked on the users forum: http://answers.opencv.org

I am agree with your concern. Actually I have seen the code of yours containing the file name matching_to_many_images.cpp . That's why I asked this question. So if you will help me in this concern , I am very thankful to you.


scope attach --inspect  from container to host can return error when successful

This is being observed when attaching from a container to a process on the host.  It looks like a failure to attach to 46941, but isn't a true failure:
Attaching to process 46941
It can take up to 1 minute to attach to a process in a parent namespace
Inspect PID fails: timeout with consume the message

Here's why we are confident that the attach has succeeded:

Subsequent scope inspect calls succeed
Edge receives traffic from pid 46941 if Edge is the configured destination

I've marked #1579 as resolving this issue.   I know that change will help this issue.  If it's not enough by itself, we can either reopen this or create a new ticket for addition work later.


[formrecognizer] design currency document field value type

@kristapratico commented on Fri Sep 10 2021
https://apiview.dev/Assemblies/Review/cf2c57b3d4c44ef08c2e8284f7441a2d?diffRevisionId=25f703d59676465684c5014a6fc7d9cb&doc=False&diffOnly=False#814fc6adcfc94303be1adcd7461c7605

@kristapratico commented on Fri Sep 17 2021
Currency won't be added until beta.2

Added in referenced PRs.


pull request for e2e test at 12/20/2016 12:26:21

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


Alpha Vantage is an unlicensed vendor

Hi,
Just want to bring it to you guys' attention that Alpha Vange is distributing market data illegally and legal actions have been taken against the company. I suggest you guys to switch to another provider immediately to avoid service disruption.
Original proof of illegal activity can be found here: https://www.reddit.com/r/algotrading/comments/hnxoy6/beware_alphavantage_is_not_a_licensed_provider/
The following market data has disappeared due to legal actions and more will be coming soon:

US real-time data (now they only have end of day data)
LSE
NSE
ASX
Torronto stock exchange (TSX)
All Nordic exchanges
All Baltic exchanges
Moscow stock exchange
Istanbul stock exchange

I'm just as disappointed as all of you that a great idea was so poorly executed and based on entirely illegal foundation to begin with.

Reddit post is deleted, is there any other proof to justify the claim ?

@myxfinance223  I can't find any confirmation of your statement + Reddit post was deleted


[meta] Update changelog for 7.8.1 / 7.9.0 / 6.8.11 / 6.8.12 releases

add missing changes for 7.9.0 / 6.8.12 release about Helm 3 beta support
add more details about an issue related to Logstash breaking change in 7.8.1 / 6.8.11

Related to #766 and #759

@jmlrt When I got to "update the changelog" step, I wasn't sure where to get the contents from. How do you compile the changelog?

How do you compile the changelog?

Well that's another manual step...
My current process is reviewing every commits on the released branch since the last released version.
The good thing is that we enforce squash and merge so one commit is always one PR now.
git lg 7.9 --since="$(git log -1 7.9.0 --pretty=%ad)" | cat
* acfe3cd - (HEAD -> 7.9, origin/7.9) Fix serviceAccount for APM server (#786) (Dat Tang 6 days ago)
* b8a1367 - [metricbeat] Add missing labels for deployment (#770) (Vadym Liubko 6 days ago)
* e1efa56 - [logstash] Fix headless service ports spec (#776) (Simon Gurcke 6 days ago)
* fc0168c - Remove duplicate "initialDelaySeconds" field (#763) (Thomas Decaux 6 days ago)
* dcc1350 - Missing deletion of "elastic-certificate-crt" (#752) (AhmedSamirAhmed 6 days ago)
* 6d68ec5 - Fix typo in FAQ (#744) (SlavaSubotskiy 6 days ago)
* 49b2346 - [helm] bump helm version to 2.16.10 (#797) (Julien Mailleret 6 days ago)
* e1b0ad9 - [release] bump 7.9 branch to 7.9.1-SNAPSHOT (#791) (Yuriy 7 days ago)
* ccd2e6c - [meta] drop gke 1.14 tests (#798) (Julien Mailleret 7 days ago)
* 6cfbe00 - (tag: 7.9.0) 7.9.0 release (#788) (Yuriy 2 weeks ago)

Then I copy/paste a section from the previous release and update it manually with the content of the relevant commits.
The current format of the CHANGELOG.md is:

commits/PRs related to feature/fix for one specific product are going to a table under the product sub-section

if a commit/PR is adding a feature/fix for more than one product, I duplicate the line under every related product sub-section
PR titles can be cleaned and edited in the table to be more explicit

changes not related to products feature/fix (example product or helm version bump, CI changes, process documentation...) can be listed if relevant (less details needed, author of the change is often mentionned but not necessarily the exact PR of the change (there is no real rule for that).
finally I run docker run --rm -it -v $(pwd)/CHANGELOG.md:/usr/src/CHANGELOG.md jorgeandrada/doctoc to update the table of content.

I had a little python script to retrieve all merged PR already formated as a table (thanks to @Crazybus), but then it requires manual steps to reorder them and filter only what was merged or backported on the good branch, and since the last release (some old PR could be at the top of the list if someone recently commented it after merge...), edit the PR title if needed, filter relevant PRs and add theM to the relevant product sub-sections...
So unfortunately, it is currently faster to fill changelog manually by copy/pasting as long as I don't have time to update the script.
At some time we should update the CHANGELOG format to make it easier to update and create process to automate it more (maybe by using PR tags or gitmoji to generate it for exemple...).
For the BREAKING_CHANGES.md, this is a mix of Elasticsearch breaking change notes and Elasticsearch release highlights.
I use it to document breaking changes, and important changes that would require more details than a line in the changelog and don't have their place in the charts README documentation, known bugs and their workarounds, ...
I fill it after checking the details of all PRs in the changelog and recent issues/user feedbacks.
This is typically something that should stay manual and can't be automated IMO.


[stable/datadog] Fix trace agent and useConfigMap

Is this a new chart
No
What this PR does / why we need it:
Version 2.0.0 of the stable/datadog introduced new issues.

If agents.useConfigMap is set to to true, it causes a templating error because .Values.image no longer exists.

Error: template: datadog/templates/datadog-yaml-configmap.yaml:38:28: executing "datadog/templates/datadog-yaml-configmap.yaml" at <.Values.image.tag>: nil pointer evaluating interface {}.tag

If agents.useConfigMap is false and agents.apm.enabled is true, the Datadog trace agent container fails to startup with this error:

trace-agent not enabled. Set the environment variable DD_APM_ENABLED=true or add "apm_config.enabled: true" entry to your datadog.yaml. Exiting...

Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Title of the PR starts with chart name (e.g. [stable/mychartname])

Just ran into this issue installing the new v2.0.1 Helm chart.
Not using the config maps and gives the error
trace-agent not enabled. Set the environment variable DD_APM_ENABLED=true or add "apm_config.enabled: true" entry to your datadog.yaml. Exiting...

/ok-to-test

@ggmaresca thank you for finding and  fixing this issue.
Could you please:

bump the version to 2.0.3
update changelog file with a short description: https://github.com/helm/charts/blob/master/stable/datadog/CHANGELOG.md

Hi @ggmaresca
I think something went wrong when you did the git rebase.
Could you fix it, and I will be happy to merge it.
Regards

Sorry I did't saw your new PR.


GH-1778: Properly Apply Client Post Processors

Resolves https://github.com/spring-projects/spring-kafka/issues/1778
Consumer/Producer post processors are Functions and the result should
be used; it was previously discarded.
cherry-pick to 2.6.x, 2.5.x

... and cherry-picked to 2.6.x & 2.5.x


Oracle 11.x download is no longer available.

Instructions for building the test environment involve downloading oracle-xe-11.2.0-1.0.x86_64.rpm.zip this does not appear to be present on Oracle's site any longer.
https://www.oracle.com/database/technologies/xe-downloads.html

Contains version 21
The previous version archive contains 18
The previous version archive on version 18's page dead-ends.

It is unclear how to produce a viable test environment for the oracle-enhanced project.

#44 should have fixed this issue.


HTMLElement.shadowRoot is deprecated.

The contents of atom-text-editor elements are no longer encapsulated
within a shadow DOM boundary. Please, stop using shadowRoot and access
the editor contents directly instead.
HTMLElement.shadowRoot (C:\Users\Evgen\AppData\Local\atom\app-1.19.0\resources\app\src\text-editor-element.js:13:10)
<unknown> (C:\Users\Evgen\.atom\packages\drag-drop-text\lib\drag-drop-text.coffee:29:45)
Workspace.observeTextEditors (<embedded>:26205:15)
DragDropText.activate (C:\Users\Evgen\.atom\packages\drag-drop-text\lib\drag-drop-text.coffee:26:43)
Package.activateNow (<embedded>:69370:25)
<unknown> (<embedded>:69342:38)

I got the issue as below
HTMLElement.shadowRoot - /snap/atom/247/usr/share/atom/resources/app.asar/src/text-editor-element.js:13:10
 - /home/classicsoft/.atom/packages/drag-drop-text/lib/drag-drop-text.coffee:29:45
Workspace.observeTextEditors - :11:428320
DragDropText.activate - /home/classicsoft/.atom/packages/drag-drop-text/lib/drag-drop-text.coffee:26:43
Package.activateNow - :11:3212513
measure - :11:3211925

Sorry, I abandoned atom a year ago and there is no support.
On Thu, Feb 27, 2020 at 9:27 PM utsavguptagit<EMAIL_ADDRESS>wrote:

I got the issue as below
HTMLElement.shadowRoot -
/snap/atom/247/usr/share/atom/resources/app.asar/src/text-editor-element.js:13:10
/home/classicsoft/.atom/packages/drag-drop-text/lib/drag-drop-text.coffee:29:45
Workspace.observeTextEditors - :11:428320
DragDropText.activate -
/home/classicsoft/.atom/packages/drag-drop-text/lib/drag-drop-text.coffee:26:43
Package.activateNow - :11:3212513
measure - :11:3211925
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/mark-hahn/drag-drop-text/issues/8?email_source=notifications&email_token=AAGGDP5IKVSYB7N6ZK5QRPTRFCOF7A5CNFSM4DXCTNM2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOENHBVOA#issuecomment-592321208,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAGGDP7YCI6Z636ZN7TVXSLRFCOF7ANCNFSM4DXCTNMQ
.

Uploaded an update to the drag-drop-text.coffee file (#11). This bug can be marked as closed after merging my branch back with main and releasing the new version by @mark-hahn.
FYI: This was a bit trickier to fix. I removed .shadowRoot from line 18.

Fixed in v1.0.0


Moving zk logic outside the pallet

@drewstone This PR includes only moving the pallet types from ScalarData to ScalarBytes (Vec). The artworks stuff will be added in separate PR


sh_linker_init failed on NoxPlayer <IP_ADDRESS>

ShadowHook Version
1.0.7
Android OS Version
5.1.1
Android ABIs
armeabi-v7a
Device Manufacturers and Models
NoxPlayer <IP_ADDRESS>
Describe the Bug
Hi,
shadowhook_init(SHADOWHOOK_MODE_UNIQUE, false) returned error code 12.
With api_level = 22, function xdl_dsym could not find __dl__Z9do_dlopenPKciPK17android_dlextinfo in linker, thus the result returned for sh_linker_dlopen_addr is null.
I have attached the linker binary file bellow
Regards.
linker.zip

Thanks for your feedback. ShadowHook has no plan to support android emulator yet.

Thank you~
I have also found some bugs in the Bluestacks emulator. I hope you have plans to support the emulator in the future.


Prl 1653 da resp orders

Before creating a pull request make sure that:

[ ] commit messages are meaningful and follow good commit message guidelines
[ ] README and other documentation has been updated / added (if needed)
[ ] tests have been updated / new tests has been added (if needed)

Please remove this line and everything above and fill the following sections:
JIRA link (if applicable)
Change description
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[ ] No

this PR and branch is not required as we will be pointing to different PR from citizen journey which has got the implementation to get the case details from the cos-api from citizen journey


doc(README): refined licensing documentation in README for enhanced clarity and professionalism

Hey @shengyu 👋
This is ready for review


Move utils bridged methods into their own ffi module

Discovered that we can use Pin<&mut ...> to allow mutation of Rust types defined in another cxx bridge module, based on:

https://cxx.rs/extern-c++.html#opaque-c-types

Unlike extern Rust types and shared types, an extern C++ type is not
permitted to be passed by plain mutable reference &mut MyType across the
FFI bridge. For mutation support, the bridge is required to use Pin<&mut
MyType>. This is to safeguard against things like mem::swap-ing the
contents of two mutable references, given that Rust doesn't have
information about the size of the underlying object and couldn't invoke
an appropriate C++ move constructor anyway.

https://github.com/dtolnay/cxx/issues/942

I'm already happy with this result (took me long enough to try a lot of different options which did not work).
If/when https://github.com/dtolnay/cxx/issues/353 is resolved, we might be able to (re)use these types again within boxes and return them (instead of using the mutable references).

coverage: 60.319% (+0.03%) from 60.294%
when pulling 9e45e5cac5cd712b2af535e7d3973de1f6887f53 on dennisschagt:use-pin-mut-ref-for-cxx-reuse
into 0f1b160c3af35263ce6067035e52c3ef5da2b21d on newsboat:feature/2326-filepath.


RawFile LocalPV provisioner does not actually delete PV folders

Steps to reproduce

Delete a rawfile LocalPV kubectl delete pvc myrawfile-pvc or kubectl delete pv pv-122133123

The PV folder will not be deleted on the host file system. It will only be marked deleted with timestamp in the metadata JSON file.

$ cat disk.meta {"schema_version": 2, "volume_id": "pvc-4b772e0e-9c16-4a1c-961d-9a9ba236de2f", "created_at":<PHONE_NUMBER>.6610372, "img_file": "/data/pvc-4b772e0e-9c16-4a1c-961d-9a9ba236de2f/disk.img", "size":<PHONE_NUMBER>0, "fs_type": "ext4", "deleted_at":<PHONE_NUMBER>.8736064}

Sorry for the late update.
This is a known behavior, and a culprit of rawfile being in an alpha-ish state. I was too afraid to delete anything back when I was developing this. Now that this has been running in different environments for months, I feel more confident doing it for real. Will update soon.

Sorry for the late update.
This is a known behavior, and a culprit of rawfile being in an alpha-ish state. I was too afraid to delete anything back when I was developing this. Now that this has been running in different environments for months, I feel more confident doing it for real. Will update soon.

Please also update helm charts

Bumping this issue  as well, as I understand something needs to invoke the gc entrypoint in rawfile.py but there is none.


Field labels in Collection model

The Field labels in the create collection page are not appearing in bold.
Some field names (Rights Statement, Arkivo Checksum, Bibliographic Citation, etc) are listed twice.

Appears to be resolved


fix: Set object does not start with /

fix:Fix // path problem; if object starts with /, the URL will be https://eg.casbin.org//object.txt
doc:Mark methods not supported by r2

@creaplus

Don't carry previous commits:

Resolve conflicts

@creaplus

Don't carry previous commits:

Resolve conflicts

I found that I couldn't modify this PR. I deleted it or drafted it and resubmitted it.

@creaplus follow the rules here: https://casdoor.org/docs/contributing/#modifying-prs
Re-use your existing PRs and don't open a 3rd PR again for this issue. Or your account will be banned from this organization


build: use LINK_COMPONENTS for linking LLVMSupport

Without this patch, in-tree builds of LLVM+MHLO fail with the following
message:
MhloRngUtils specifies LINK_LIBS LLVMSupport, but LINK_LIBS cannot be used
for LLVM libraries.  Please use LINK_COMPONENTS instead.

@sdasgup3 is oncall for MHLO this week

Hi @sdasgup3 Can you please review this PR ? Thank you!

Closing because commit 11b7c33 addresses the problem.


KOGITO-6448 async findById processInstance used by CloudEventConsumer

Async findById in ProcessInstances used by CloudEventConsumero avoid Thread Blocked Exception.
This issue was noticed using the latest PostgreSQL 14+ with the reactive client.
https://issues.redhat.com/browse/KOGITO-6448
Many thanks for submitting your Pull Request :heart:!
Please make sure that your PR meets the following requirements:

[ ] You have read the contributors guide
[ ] Your code is properly formatted according to this configuration
[ ] Pull Request title is properly formatted: KOGITO-XYZ Subject
[ ] Pull Request title contains the target branch if not targeting main: [0.9.x] KOGITO-XYZ Subject
[ ] Pull Request contains link to the JIRA issue
[ ] Pull Request contains link to any dependent or related Pull Request
[ ] Pull Request contains description of the issue
[ ] Pull Request does not include fixes for issues other than the main ticket

How to replicate CI configuration locally?

Build Chain tool does "simple" maven build(s), the builds are just Maven commands, but because the repositories relates and depends on each other and any change in API or class method could affect several of those repositories there is a need to use build-chain tool to handle cross repository builds and be sure that we always use latest version of the code for each repository.
build-chain tool is a build tool which can be used on command line locally or in Github Actions workflow(s), in case you need to change multiple repositories and send multiple dependent pull requests related with a change you can easily reproduce the same build by executing it on Github hosted environment or locally in your development environment. See local execution details to get more information about it.

How to retest this PR or trigger a specific build:

Run all builds
Please add comment: Jenkins retest this

Run (or rerun) specific test(s)
Please add comment: Jenkins (re)run [kogito-runtimes|optaplanner|kogito-apps|kogito-examples|optaplanner-quickstarts|optaweb-employee-rostering|optaweb-vehicle-routing] tests

Quarkus LTS checks
Please add comment: Jenkins run LTS

Run (or rerun) LTS specific test(s)
Please add comment: Jenkins (re)run [kogito-runtimes|optaplanner|kogito-apps|kogito-examples|optaplanner-quickstarts|optaweb-employee-rostering|optaweb-vehicle-routing] LTS

Native checks
Please add comment: Jenkins run native

Run (or rerun) native specific test(s)
Please add comment: Jenkins (re)run [kogito-runtimes|optaplanner|kogito-apps|kogito-examples|optaplanner-quickstarts|optaweb-employee-rostering|optaweb-vehicle-routing] native

Full Kogito testing (with cloud images and operator BDD testing)
Please add comment: Jenkins run BDD
This check should be used only if a big change is done as it takes time to run, need resources and one full BDD tests check can be done at a time ...

I've tested it locally and works fine. Regarding the changes LGTM, however I'm not 100% familiar the persistence mechanism and all the potential implicances of this change. So I prefer @cristianonicolai to take a look too.
Be sure please that this change is covered by the tests please.

Yeah, I can add some tests for the newly added methods, I just want to confirm that we go with this approach and it works. The impact should be minimal since the new methods are just wrapping the normal blocking call with CompletableFuture as the default impl.
see https://github.com/kiegroup/kogito-runtimes/pull/1816#discussion_r774491655
basically, we need to take a decision :)

@fjtirado to make the PR simpler and avoid modification in the ProcessInstances, I just changed the CloudEventConsumer to wrap the execution to run async in the executed already configured in this class.
But for the future to work more integrated with reactive libraries like reactive pg client and smallrye reactive messaging, we need to come with reactive APIs under ProcessInstances at least... and at some point the integration with the engine itself, but this is a more complex story.

The (build) kogito-apps check has failed. Please check the logs.

The (build) optaplanner-quickstarts check has failed. Please check the logs.

The (build) optaplanner check has failed. Please check the logs.

The (build) kogito-examples check has failed. Please check the logs.

The (build) kogito-runtimes check has failed. Please check the logs.

The (build) optaweb-vehicle-routing check has failed. Please check the logs.

The (build) optaweb-employee-rostering check has failed. Please check the logs.

jenkins retest this

The (build) kogito-runtimes check has failed. Please check the logs.

The (build) kogito-apps check has failed. Please check the logs.

Jenkins run kogito-apps tests

@cristianonicolai missing your review this one with the last changes.

all green @cristianonicolai, ok to merge?


Fixes ActionView::Template::Error: uninitialized constant ActionView::CompiledTemplates::BootstrapPagination

During development I noticed that in newer Ruby versions (I'm running ruby 2.2.3p173) I was getting the following error when using will_paginate-bootstrap:
ActionView::Template::Error: uninitialized constant ActionView::CompiledTemplates::BootstrapPagination
After some debugging I found out that the include didn't seem to work properly when loading the Rails version of the gem. I fixed this by implicitly defining which BootstrapRenderer to include.

Thanks! :+1:


[W6.1h][T09-B3] Niu Yunpeng

Add Printable Interface
Let phone, email, address and name implement Printable
Add test case

Go ahead and close the PR.

Reopening PR as I accidentally closed it.

Close this PR since it has been reviewed by the tutor.


[BP-1.16][FLINK-25554][test] Remove timeout to enable a thread dump in case the test times out again.

1.16 backport PR for PR #21066

e2e test failure related to FLINK-29671

The other test failure is related to FLINK-15661

I'm going ahead with merging the PR since this change actually doesn't really require a test run.


Setup & Deploy NextCloud

Write Kustomize configuration for NextCloud
Documentation available here
Docker image available on docker hub
Kubernetes guide available here

Depends on #46

Helm chart: https://github.com/nextcloud/helm


clientAppUnavailable from getDetails

Describe the bug
After calling await window.getDigitalGoodsService('https://play.google.com/billing'), getDetails(['pro']) returns a clientAppUnavailable error. I Googled "clientAppUnavailable" and got a single result. I've poked around a bit but don't appear to have made much progress, however, I'll continue to poke around.
I've had a PWA published in the Google Play Store for close to 18 months now. With the hopeful stabilisation of the Digital Goods and Payment APIs I'm trying to add in-app play billing support. Since my TWA codebase has remained fairly stable and has aged, I re-built from scratch using bubblewrap 1.15 late last week, followed the various prompts, reinstalled android and other deps as prompted (honestly, a very sweet experience - this is amazing!!! Well done guys!) I ticked yes to billing, alpha, notifications (the other clientAppUnavailable error) etc. Built the apk. Verified asset links remained correct. Joined v1 and v2 origin programs etc.
To Reproduce
Steps to reproduce the behavior:

Bubblewrap 1.15 init
Accept prompts for billing, alpha features etc.
Digital links already in place. TWA/PWA delivered over HTTPs into newly built app
Configured subscriptions within Play Billing. Setup Payments profile, verified, tax status etc. All the things afaik. "pro" is the Product ID of the subscription, and it's marked active.
Deployed to test device.
Call per screen shot

Have made zero progress unpicking what might be going on. Also pushed a version to internal track (in addition to existing)

Expected behavior
Returns a list of products.
Screenshots
N/A
Desktop (please complete the following information):

OS: Linux/WSL2
Browser N/A
Version: Node 16.13.1, NPM 8.1.2

Smartphone (please complete the following information):

Device: Pixel 4A 5G
OS: Android 12
Browser: Chrome
Version 97.0.4692.87

Additional context
Add any other context about the problem here.
Any pro-tips would be great! Thanks and awesome product!

It looks like DelegationService in AndroidManifest.xml is templated relatively as .DelegationService. I changed this to DelegationService without the period, rebuilt, and the call to getDetails(..) came alive.
However, what is insane is that after I made that single change I haven't been able to break it again. Even the known broken build I pushed to the Play Store Internal Track yesterday is working, and it also works on a different device too. So either something was very sad on my dev device (despite many uninstalls, reboots etc.), there was a transient issue with the Play Store, or perhaps there's some kind of trust relationship between the app and play store which needed to expire(?) or take effect. Very strange  - but seems to be working for me now.

As another update, I just installed my app onto another phone with a separate play account but which has access to the Internal Track and I receive the same error.
I'm not sure if users have to be added to the Licence Testing configs as well, so I've tried that and am waiting to see what happens in the morning after some time passes.

What helped me was using: adb logcat -v brief | grep -e TWAConnectionPool and adb logcat -v brief | grep -e OriginVerifier -e digital_asset_links it displayed a scoping issue that was causing the "clientAppUnavailable" issue.

@Stevie-Ray @tristan-morris, we also are hitting this error and have detailed it in https://github.com/GoogleChromeLabs/bubblewrap/issues/805, and using Stevie's logcat command we see that we also have a scoping issue, but we have no idea what needs fixing? Could you take a look?
Failed to connect to TWA to execute command
java.util.concurrent.ExecutionException: java.lang.IllegalArgumentException: No service exists for scope
	at K0.c(chromium-TrichromeChromeGoogle6432.aab-stable-573513033:21)
	at K0.get(chromium-TrichromeChromeGoogle6432.aab-stable-573513033:115)
	at vC3.run(chromium-TrichromeChromeGoogle6432.aab-stable-573513033:9)
	at android.os.MessageQueue.nativePollOnce(Native Method)
	at android.os.MessageQueue.next(MessageQueue.java:335)
	at android.os.Looper.loopOnce(Looper.java:186)
	at android.os.Looper.loop(Looper.java:313)
	at android.app.ActivityThread.main(ActivityThread.java:8757)
	at java.lang.reflect.Method.invoke(Native Method)
	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:571)
	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1067)
Caused by: java.lang.IllegalArgumentException: No service exists for scope
	at tC3.b(chromium-TrichromeChromeGoogle6432.aab-stable-573513033:67)
	at bg1.a(chromium-TrichromeChromeGoogle6432.aab-stable-573513033:311)
	at yC3.run(chromium-TrichromeChromeGoogle6432.aab-stable-573513033:28)
	at F60.a(chromium-TrichromeChromeGoogle6432.aab-stable-573513033:29)
	at C60.onResult(chromium-TrichromeChromeGoogle6432.aab-stable-573513033:58)
	at gB.run(chromium-TrichromeChromeGoogle6432.aab-stable-573513033:5)
	at android.os.Handler.handleCallback(Handler.java:942)
	at android.os.Handler.dispatchMessage(Handler.java:99)
	at android.os.Looper.loopOnce(Looper.java:226)
	at android.os.Looper.loop(Looper.java:313)
	at android.app.ActivityThread.main(ActivityThread.java:8757)
	at java.lang.reflect.Method.invoke(Native Method)
	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:571)
	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1067)

I just ran into a problem similar to this.  The problem was that my TWA was using 'http', but the app was registered to scope 'https'.  I was running my TWA at http://<IP_ADDRESS>:8080.
It looks like bubblewrap always assumes scope of https:
            <intent-filter android:autoVerify="true">
                <action android:name="android.intent.action.VIEW"/>
                <category android:name="android.intent.category.DEFAULT" />
                <category android:name="android.intent.category.BROWSABLE"/>
                <data android:scheme="https"
                    android:host="@string/hostName"/>
            </intent-filter>

https://github.com/GoogleChromeLabs/bubblewrap/blob/e90c0927c18f7260b2565193663daa37f7876b87/packages/core/template_project/app/src/main/AndroidManifest.xml#L193
I fixed things by manually editing <data android:scheme="https" to be https (delete the s) in my local app/src/main/AndroidManifest.xml and re-run bubblewrap build

I faced this problem and found out that in my case the problem was linked to Deep Link intent-filter. I removed android:autoVerify and android:sspPattern options, replacing the last one with android:pathPrefix. Also, check that android:host is specified correctly.


Noetic support

Changes since Melodic:

Only officially support Citadel onwards
Don't need https://packages.osrfoundation.org
This version will be officially released as upstream ROS packages

Commented out mav_msgs because that's not yet available on Noetic: https://github.com/ethz-asl/mav_comm/issues/86

Do we want to keep it?

I left the Ignition parts since they're already working. They're not very useful without the ROS side though. I guess at least we can keep it from rotting. If you think it's best to comment it out I can do that.

I made a branch

Thanks, merged it in.

I also rebased the noetic branch onto melodic after #72 and #96 - the noetic branch was just matching melodic before anyways, with no commits of its own.

I left the Ignition parts since they're already working. They're not very useful without the ROS side though. I guess at least we can keep it from rotting. If you think it's best to comment it out I can do that.

Nothing important, I thought on someone listing gz topics and found the Actuator in there. A part from a bit of compile/runtime overhead without real use.


chore: nits

Thanks! Going to spin out a second binary real quick for Optimism, think it will be best to ease concerns and we should probably get it done anyways. Will create a PR with the other changes cherry picked onto it 😄


Experimental: Platformer actor collision

Please check if the PR fulfills these requirements

[ ] The commit message follows our guidelines
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Feature

What is the current behavior? (You can also link to an open issue here)
Platform mode does not support solid collision between actors and the player

What is the new behavior (if this is a feature change)?
Actors have a 'solid' property, when it is enabled, the player will collide with them like a wall, and will move along with one that it is standing on.

Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
I don't believe so.

Other information:
Still need to investigate optimization. It works OK in color mode, but sprites get jittery in DMG mode. There are also issues with how the player moves with an actor it is standing on, and collision events currently do not trigger on solid actors.

Once you are done with this, could you please also do the same for the adventure mode? Code shouldn't be that much different tho in adventure the moving along with actor would have to go.
The reason for this is that in adventure mode currently there is no possibility of creating secret entrances that only become passable once certain conditions are met as map collision is static and you can pass through actors that would normally block players from entering before they met the necessary conditions.

Yes, I intend to port the changes to that mode.
On Wed, Feb 2, 2022, 7:17 AM darkhog @.***> wrote:

Once you are done with this, could you please also do the same for the
adventure mode? Code shouldn't be that much different tho in adventure the
moving along with actor would have to go.
The reason for this is that in adventure mode currently there is no
possibility of creating secret entrances that only become passable once
certain conditions are met as map collision is static and you can pass
through actors that would normally block players from entering before they
met the necessary conditions.
—
Reply to this email directly, view it on GitHub
https://github.com/chrismaltby/gb-studio/pull/1037#issuecomment-1027880862,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAC2YSSIXOKWWDGPITWS6UTUZEOFLANCNFSM5NFLE6CA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID:
@.***>

That's awesome. Thank you!

This is so cool. I hope you can get this implemented because we’ve needed this feature for a loooong time

Only now have I found it. This one sparks joy.

Will it make it into 3.1?

Will it make it into 3.1?

Looks like there are still some conflicts that must be resolved

Hi @um3k Just to let you know, after a very long time I have finally been testing this and definitely interested in merging.
Not sure it's going to be 3.1 though, I'm starting to feature freeze on what makes it in to 3.1 and I'm still having a few issues with it.

In Platform scenes if stood on a moving actor, that is solid in all directions, while it is moving upwards and you're either at the left edge jumping right, or the right edge jumping left you snap back to the side of the platform (think this is probably the horizontal collision detection kicking in when it shouldn't). From what I can tell as long as the vertical moving platform just has "Top" collisions turns on, or your fully solid actor is either stationary or only moving horizontally then it all works great.

https://user-images.githubusercontent.com/16776042/180873013-5aa43bb1-68c2-4a1b-bcef-786b9693b440.mp4

Possibly related vertical moving actors set to fully solid in Adventure also do some odd snapping when colliding with top / bottom edges (left/right work correctly)

https://user-images.githubusercontent.com/16776042/180874469-f46fc157-b609-4904-9b9c-ee8c3bd0d226.mp4

I think the quick check you do pre running the full collision check might be too small a range for some larger actors, if I'm understanding what you're doing correctly increasing to + 3 and > 6 help a bit

             ((UBYTE)((BYTE)(PLAYER.pos.x >> 8) - (BYTE)(sol_actor->pos.x >> 8) + 3) > 6) ||
            ((UBYTE)((BYTE)(PLAYER.pos.y >> 8) - (BYTE)(sol_actor->pos.y >> 8) + 3) > 6)) {

By the way the persistent actors feature ("Keep Running While Offscreen" checkbox on "On Update") and recent optimisations to actors_update() and vm_actor_move_to() + some better offscreen detection we wrote recently were to prepare for merging this feature.
Thanks for putting this PR together, definitely is a great feature that people will make lots of use of!

Hi Chris, thanks for checking in! I guess it's time to dust off the ol'
keyboard and find some time to reacquaint myself with the code.
I definitely experienced those collision bugs at some point during my
testing, it's possible I have more recent code in my local directory that
fixes them. I can't remember exactly where I left off in my endless
tinkering. So I'll look into that soon.
I agree, those numbers for the quick check are probably better. I was
hesitant to set them too high and potentially defeat the purpose of the
check. I wonder if it would be feasible to set them at compile time based
on the largest sprite in the project? Might need to look into that.
I'm humbled that that work was done in anticipation of this, now I'd better
pull it together and get it done!
On Mon, Jul 25, 2022, 5:14 PM Chris Maltby @.***> wrote:

Hi @um3k https://github.com/um3k Just to let you know, after a very
long time I have finally been testing this and definitely interested in
merging.
Not sure it's going to be 3.1 though, I'm starting to feature freeze on
what makes it in to 3.1 and I'm still having a few issues with it.

In Platform scenes if stood on a moving actor, that is solid in all
directions, while it is moving upwards and you're either at the left edge
jumping right, or the right edge jumping left you snap back to the side of
the platform (think this is probably the horizontal collision detection
kicking in when it shouldn't). From what I can tell as long as the vertical
moving platform just has "Top" collisions turns on, or your fully solid
actor is either stationary or only moving horizontally then it all works
great.

https://user-images.githubusercontent.com/16776042/180873013-5aa43bb1-68c2-4a1b-bcef-786b9693b440.mp4

Possibly related vertical moving actors set to fully solid in
Adventure also do some odd snapping when colliding with top / bottom
edges (left/right work correctly)

https://user-images.githubusercontent.com/16776042/180874469-f46fc157-b609-4904-9b9c-ee8c3bd0d226.mp4

I think the quick check you do pre running the full collision check
might be too small a range for some larger actors, if I'm understanding
what you're doing correctly increasing to + 3 and > 6 help a bit
    ((UBYTE)((BYTE)(PLAYER.pos.x >> 8) - (BYTE)(sol_actor->pos.x >> 8) + 3) > 6) ||
   ((UBYTE)((BYTE)(PLAYER.pos.y >> 8) - (BYTE)(sol_actor->pos.y >> 8) + 3) > 6)) {

By the way the persistent actors feature ("Keep Running While Offscreen"
checkbox on "On Update") and recent optimisations to actors_update() and
vm_actor_move_to() + some better offscreen detection we wrote recently were
to prepare for merging this feature.
Thanks for putting this PR together, definitely is a great feature that
people will make lots of use of!
—
Reply to this email directly, view it on GitHub
https://github.com/chrismaltby/gb-studio/pull/1037#issuecomment-1194638003,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAC2YSUJI4GN5L56XSHEEM3VV37TFANCNFSM5NFLE6CA
.
You are receiving this because you were mentioned.Message ID:
@.***>

I fixed the two merge conflicts locally and built an adventure scene. It works pretty well for 16x16 actors (I didn't try any larger actors). The one "bug" I found is that solid actors pushed with the "Push Actor Away From Player" event do not always collide with other actors that are set to solid on all sides. I was able to consistently push a solid box to the right and have it phase through another solid box. A solid box pushed vertically DOES stop properly when encountering another solid box.

That's impressive work, looks like it's closer than ever before :)

I just made my own PR branching off the content of this PR. Attempted to fix the merge conflicts and issues found by me and Chris mentioned in the comments above. https://github.com/chrismaltby/gb-studio/pull/1232


Support App Store Connect API keys and provisioning profiles

Closes #71.
Using an App Store Connect API key with Xcode >= 13 allows automatic device registration, certificate creation, and provisioning profile creation.
Users who want to use an existing provisioning profile, or who use Xcode < 13, can now pass a list of Base64-encoded Mac or iOS provisioning profiles.

I might be able to address the provisioning profile(s) with this, assuming Xcode will search for local profiles before checking the API for registration.

❌  error: Revoke certificate: Your account already has an Apple Development signing certificate for this machine, but its private key is not installed in your keychain. Xcode can create a new one after revoking your existing certificate

Looks like I may need to make use of actions/cache.

We should bump to v2 since we are removing code-sign-certificate.
Unless we can reasonably prove this only effects <2 projects. (Not sure we can prove anything).

I'm not planning to remove any inputs. I reorganized the README section on code signing a bit:

App Store Connect API key: Requires Xcode 13. Manages device registration, certificates and provisioning profiles automatically.
Certificates: Used to install a specific certificate to the macOS Keychain.
Provisioning Profiles: Used to install specific provisioning profiles.

None of these should be mutually exclusive, in theory. The simplest usage for most users should be the API key alone.
To Do:

[ ] Figure out how to address the private key is not installed error.

We could find a way to persist the certificate for a given GitHub Actions host (macOS Device UUID), perhaps using @actions/cache. What are the security implications of that?
Alternatively, we could call the App Store Connect API directly to revoke the existing certificate beforehand. This might have the effect of generating a long list of revoked certs on the developer's account.
Failing those ideas, maybe this is only useful for GHES and self-hosted runners? That would be disappointing.

[ ] Determine whether installing a Mac .provisionprofile is useful, or if only iOS-ish .mobileprovision profiles are useful. It's not clear to me, for instance, if a provisioning profile from a developer's Mac is meant to (or can) be copied to another Mac and remain useful. Mobile profiles clearly seem useful, as there are dozens of projects copying them around, and GitHub documents how to install them. Perhaps a .provisionprofile is only useful for Mac Catalyst development? I that's the case, I'll document it as such.

Sorry for the delay. It's been, uh, an unexpectedly busy few weeks. 😅
Still investigating the To Dos above.

nps dude; to me you’re an open source king 👑

I think I've convinced myself that the propagation of provisioning profiles is generally useful.
Unfortunately, I think the App Store Connect API functionality is only useful for self-hosted runners, where private keys persist. Would you be comfortable accepting this PR in order to support the functionality only for self-hosted runners?
Support for GitHub-hosted runners could be added in a later PR by persisting any private keys installed using the App Store Connect API. I want to err on the side of incremental progress, and I worry about letting this PR die on the vine.

Possibly the private key could be written to the repo as a secret?
Either way that can happen later. It’s fine that this only works for private runners provided we document it as such.

Sounds good. I'll add some clarifying documentation to the README and YAML, then merge. Probably tonight or tomorrow. I can (minor) release, too, if you like.


Added getTeam command

Added ?getTeam <player_name> command.
Takes a player name argument and returns an embedded roster for the users active team.

Format commit needs to be replaced, reopening.


Eject knex an objection to @lunox/eloquent

Lunox v1 has builtin ORM called eloquent, it's built on top of knex an objection. I use them because of my personal project and objection is highly customisable (we can create fillable, guarded, custom attribute like in laravel eloquent). But knex and objection is not user friendly, there are many popular database manager like typeorm and prisma that modern than objection.
I think it's better to exclude knex and objection to separate module @lunox/eloquent. But, maybe it will be hard because migration artisan command is also using knex for now. So it's likely migration will be removed from lunox and will be injected from @lunox/eloquent. It requires service provider to support load console command (TBD)

Bad news, we cannot use @lunox, so we will use @lunoxjs  for npm organization

Progress:

[v] make @lunoxjs/eloquent
[v] inject eloquentUserProvider from @lunoxjs/eloquent for auth guard (web guard)
[ ] inject migration and seeder command from @lunoxjs/eloquent to via service provider

Done, all feature already implemented including artisan command


Add 'Boost' version v1.69.0-p1

I've followed this guide
step by step carefully. Yes

I've tested this package remotely and have excluded all broken builds.
Here is the links to the Travis/AppVeyor with status "All passed":

https://ci.appveyor.com/project/Bjoe/hunter/builds/25778639
https://travis-ci.org/Bjoe/hunter/builds/554788267

This PR depends on https://github.com/hunter-packages/boost/pull/7

Released: https://github.com/ruslo/hunter/releases/tag/v0.23.199


Enable windows testing

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Closes #1
@conda-forge-admin please rerender

@ocefpaf The windows build log failures you were asking for :)  here's the first line
test_crypt.obj : error LNK2019: unresolved external symbol mz_crypt_pbkdf2 referenced in function "private: virtual void __cdecl crypt_pbkdf2_Test::TestBody(void)" (?TestBody@crypt_pbkdf2_Test@@EEAAXXZ) [%SRC_DIR%\test\gtest_minizip.vcxproj]

Looks like something related to the option MZ_WZAES. Maybe we can try to turn that one off? Not sure though...

Maybe we can try to turn that one off?

trying

BTW, I don't mean for you to waste your time here. I can take over later and this is definitely not a priority!

@conda-forge-admin please rerender

Windows error is different now
168/168 Test #168: gtest_minizip ....................Exit code 0xc0000135
 ***Exception:   0.02 sec
99% tests passed, 1 tests failed out of 168
 Total Test time (real) =   5.88 sec
 The following tests FAILED:
	168 - gtest_minizip (Exit code 0xc0000135
 )
 Errors while running CTest

I rebased this now
@conda-forge-admin please rerender

OK, windows error remains the same as last reported https://github.com/conda-forge/minizip-feedstock/pull/2#issuecomment-1867990106


b4 task fato

confirmed:B4
address:3k236xYosiPm9R7RuFDvjWYiMMUiRS6MqqMNQTFS8YB9cn8qa5
baker:550

confirmed:B4
address:3k236xYosiPm9R7RuFDvjWYiMMUiRS6MqqMNQTFS8YB9cn8qa5
baker:550


What went wrong: Execution failed for task ':shopify_flash-list:compileReleaseKotlin'. > 'compileReleaseJavaWithJavac' task (current target is 11) and 'compileReleaseKotlin' task (current target is 17) jvm target compatibility should be set to the same Java version.   Consider using JVM toolchain: https://kotl.in/gradle/jvm/toolchain

If add the kotlin version to build.gradle then react native gesture handler packages throws error. Kindly assist me

in your android>build.gradle file add
buildscript {
     ext {
        ....
        kotlinVersion = "1.8.10"
       ...

in your android>app>build.gradle add
android {
    .....
    composeOptions {
          kotlinCompilerExtensionVersion = "1.4.4"
    }
    .....

I hope this helps

+1

I fixed this by forcing flash-list to use Java 11.
~ java --version
openjdk 11.0.15 2022-04-19 LTS
OpenJDK Runtime Environment Zulu11.56+19-CA (build 11.0.15+10-LTS)
OpenJDK 64-Bit Server VM Zulu11.56+19-CA (build 11.0.15+10-LTS, mixed mode)

Here is a patch-package:
diff --git<EMAIL_ADDRESS><EMAIL_ADDRESS>index 0585d2a..f75cb04 100644
---<EMAIL_ADDRESS>+++<EMAIL_ADDRESS>@@ -44,8 +44,12 @@ android {
     }

     compileOptions {
-        sourceCompatibility JavaVersion.VERSION_1_8
-        targetCompatibility JavaVersion.VERSION_1_8
+      sourceCompatibility = JavaVersion.VERSION_11
+      targetCompatibility = JavaVersion.VERSION_11
+    }
+
+    kotlinOptions {
+      jvmTarget = JavaVersion.VERSION_11.toString()
     }

     sourceSets {

Dunno if this is right or wrong but project compiles and all my flashlist are working.
I'd love to know from expert what are the risks of forcing the usage of Java 11 though.


fix: json-rpc.allow-unprotected-txs

Description
json-rpc.allow-unprotected-txs is not take effect
Type of change

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
Send a Pre-EIP-155 transction and will not get an error of only replay-protected (EIP-155) transactions allowed over RPC

[ ] Tested CCTX in localnet
[ ] Tested in development environment
[ ] Go unit tests
[ ] Go integration tests
[ ] Tested via GitHub Actions

Checklist:

[ ] I have added unit tests that prove my fix feature works

good catch! thank you for the contribution.


Investigate if we can check arguments to the constructor with expectNew

From<EMAIL_ADDRESS>on October 13, 2008 19:24:58
Investigate if we can check arguments to the constructor with expectNew
Original issue: http://code.google.com/p/powermock/issues/detail?id=27

From<EMAIL_ADDRESS>on October 20, 2008 01:03:20
Labels: -Type-Defect Type-Enhancement

From<EMAIL_ADDRESS>on November 03, 2008 05:38:56
Status: Started

From<EMAIL_ADDRESS>on November 03, 2008 05:41:09
expectNew and createMockAndExpectNew takes expected arguments as the second parameter.
Status: Fixed


chore: fix typos

Codecov Report

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

@@            Coverage Diff             @@
##           master     #844      +/-   ##
==========================================
- Coverage   94.06%   92.53%   -1.54%
==========================================
  Files         252      250       -2
  Lines       10869    10886      +17
  Branches     1040     1064      +24
==========================================
- Hits        10224    10073     -151
- Misses        645      813     +168

Impacted Files
Coverage Δ

...s/opentelemetry-plugin-xml-http-request/src/xhr.ts
79.12% <ø> (ø)
:arrow_up:

packages/opentelemetry-plugin-express/src/types.ts
100% <ø> (ø)
:arrow_up:

...s/opentelemetry-core/test/context/B3Format.test.ts
47% <0%> (-53%)
:arrow_down:

packages/opentelemetry-core/test/utils/url.test.ts
50% <0%> (-50%)
:arrow_down:

...pentelemetry-api/src/context/propagation/getter.ts
0% <0%> (-50%)
:arrow_down:

...pentelemetry-api/src/context/propagation/setter.ts
0% <0%> (-50%)
:arrow_down:

...pentelemetry-core/test/internal/validators.test.ts
50% <0%> (-50%)
:arrow_down:

...elemetry-core/test/trace/spancontext-utils.test.ts
55.55% <0%> (-44.45%)
:arrow_down:

...lemetry-core/test/trace/ProbabilitySampler.test.ts
61.7% <0%> (-38.3%)
:arrow_down:

...s/opentelemetry-core/test/trace/tracestate.test.ts
65.06% <0%> (-34.94%)
:arrow_down:

... and 48 more


Address the warnings left by the Github actions

Need a few updates here and there...

solved now by dependabot

Thank you!


Update telemetry SDK to address CVE-2022-25647 with GSON library

com.google.code.gson 2.8.6 is affected by CVE-2022-25647. It is included in telemetry-core (shaded). This project needs to be updated to use the latest telemetry SDK 0.13.2 to address the issue.

Resolved by https://github.com/newrelic/newrelic-jfr-core/pull/219


Refactoring Result object

Making an object that can output results of a paragraph and update the results whenever the user wants using Zeppelin rest API


Tag replacement not working

Hi ,
I tried to replace the tag with the new amp-img tag, but its not replacing the tag.Could you please help on this asap.
`<?php
require "vendor/autoload.php";
use PHPHtmlParser\Dom\MockNode as Node;
use PHPHtmlParser\Dom;
use PHPHtmlParser\Dom\HtmlNode;
use PHPHtmlParser\Dom\TextNode;
use PHPHtmlParser\Dom\MockNode;
use PHPHtmlParser\Dom\InnerNode;
use PHPHtmlParser\Dom\Tag;
$dom = new Dom;
$dom->load('For the past few years, Bollywood actresses have been turning heads at the coveted Cannes Film Festival red carpet. While Aishwarya Rai Bachchan is all set to make her 16th appearance at the French Riviera, Huma Qureshi, who made her debut at the Cannes Film Festival, looked heavenly in a white customised Varun Bahl corset skirt and cape accessorised with Suhani Pittie earrings and Malone Souliers shoes. The actress opted for minimal makeup contrasted with a dark shade of lipstick with her hair pulled back in a neatly tied bun.  Huma Qureshi is attending the 71st Cannes Film Festival in association with liquor brand Grey Goose and will be a part of brand curated events at the festival. Niraj');
$a = $dom->find('.oembed-provider-instagram');
$tag = new Tag('amp-img');
    //$src = $a->getAttribute('src') ?: $a->getAttribute('data-src');
    $tag->setAttribute('src', 'https://www.dike.lib.ia.us/images/sample-1.jpg/image_view_fullscreen');

    $html = new HtmlNode($tag);

    $a->getParent()->replaceChild($a->id(), $html);
echo $html;`

$dom = new Dom;

foreach($dom->find('...') as $node) {
    $tmpl = new Dom;
    // do some stuff
    $node->getParent()->replaceChild($node->id(), $tmpl->root);
}

var_dump($dom->__toString()); // outputs string(1) " "

Can't do it either.

This issue appears to already be resolved. I am going to close this issue.
Please let me know if you are still experiencing this issue.


spacing problem when concatenating strings at nhs portal

When working with NHS portal I noticed a lot of wrongly concatenated strings (mostly in employees review) https://admin/employees
Screenshot attached

still same mistake


Youtube video on homepage not available

The YouTube video on the homepage can't be played because it doesn't exist anymore.
https://www.youtube.com/watch?v=quYrf9ssi1A

Thanks for the hint! This is fixed now.


Use Dropwizard 1.0.3 and Jetty 9.3.9.v20160517

Update to latest Dropwizard release and the Jetty it specifies.

Coverage remained the same at 82.941% when pulling 7fdd343b326291d5200284c5b2a473bc4a607ee8 on dinomite:master into 35384c6c954ad09690d483e17b487268ada57331 on LivePersonInc:master.

@eitan101 If you get a chance, could you cut an updated release to central?