Optimization: Making the display flush faster and other ideas

Hi Chris, this is working already great but I have some ideas that I wanted to share with you.
First I'm suspecting that most of the pages are rendering with MODE_GC16 update mode that is not the faster if you need to render only black/white text.
Adding a Serial output here:
void flush_display()
  {
    printf("needs_gray:%d\n", needs_gray_flush);
    epd_hl_update_screen(&m_hl, needs_gray_flush ? MODE_GC16 : MODE_DU, 20);
    needs_gray_flush = false;
  }

You can see that even on pages where is pure text, needs_gray is always true. This should be corrected since it will make navigating pages much faster!
Another optimization tip can be to use a smaller hourglass (Maybe half the size) that will also help to be a bit faster. But mainly the MODE_GC16 should be only used on the pages that render images and need grayscale.
As a resume:

[ ] MODE_GC16 only on pages that require it
[ ] Smaller visual indicator when a button is pressed (optional)
Showing a small visual indicator in the top bar is enough and it has the benefit that does not leave ghosting in the center of the screen as it is now.
[ ] Battery indicator is shown always full for me even if it's almost no power left (last wish, not important)

I took a look at that before and found that the text seems to be anti-alised and switching off the GC16 mode made it look a bit weird. If you have a look at the font files you can see that the bitmaps aren't always 00 of FF but have values in between.
I do wonder how much difference it actually makes - the display is quite high resolution so maybe the antialiasing is not adding that much? We could probably hack the epdiy code to draw the fonts in black and white.
I've noticed that issue with the battery indicator as well - I've split it out to a new issue: https://github.com/atomic14/diy-esp32-epub-reader/issues/22
Agreed on the indicator - it's bit horrible - I wonder if just showing something up in the header where the battery indicator is would be more subtle.

Agree on your view. Fonts do not look so nice, but as a benefit, navigating the pages updating this line to use only MODE_DU is much nicer.
I think there should be a way to make the fonts only black / white, maybe let's ask in the epdiy Slack?   For sure other libraries I used, like Adafruit GFX, render the fonts only in black and white without any problem since they are used in monochorome displays.
But not a problem, let's leave it like it is now, and I up-vote to move to a smaller hourglass placed maybe at the center of the top bar (Or at the right near the battery indicator?)

Might be an option that can added to the draw string functions of epdiy.
On Tue, Oct 5, 2021 at 1:32 PM Martin @.***> wrote:

Agree on your view. Fonts do not look so nice, but as a benefit,
navigating the pages updating this line to use only MODE_DU is much nicer.
I think there should be a way to make the fonts only black / white, maybe
let's ask in the epdiy Slack? For sure other libraries I used, like
Adafruit GFX, render the fonts only in black and white without any problem
since they are used in monochorome displays.
But not a problem, let's leave it like it is now, and I up-vote to move to
a smaller hourglass placed maybe at the center of the top bar (Or at the
right near the battery indicator?)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/atomic14/diy-esp32-epub-reader/issues/21#issuecomment-934367373,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAFMTACSUFSV4XUNKYRV4MDUFLV47ANCNFSM5FLUKIOA
.

Fixed with b2385362a4a6e426bc761db2225b4d2554e4d30f
Screen updates are much faster when changing pages - when there is only text on the screen.


First version of module

Description
This PR allows the module to deploy the IBM WebSphere Liberty operator into an IBM Cloud Openshift cluster.
It is possible to deploy the operator in all the configurations supported by the operator: OwnNamespace, SingleNamespace, and AllNamespaces (more information available at https://www.ibm.com/docs/en/was-liberty/core?topic=operator-installing-red-hat-openshift-cli)
The module supports also to deploy the Liberty sample app to verify its deployment.
Release required?

[ ] No release
[ ] Patch release (x.x.X)
[ ] Minor release (x.X.x)
[x] Major release (X.x.x)

Release notes content
Enable the module to deploy the IBM WebSphere Liberty operator into an IBM Cloud Openshift cluster in all the configurations supported by the operator: OwnNamespace, SingleNamespace, and AllNamespaces (more information available at https://www.ibm.com/docs/en/was-liberty/core?topic=operator-installing-red-hat-openshift-cli)
Support for deploy the Liberty sample app.
Run the pipeline
If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.
Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:
/run pipeline

Checklist for reviewers

[x] If relevant, a test for the change is included or updated with this PR.
[ ] If relevant, documentation for the change is included or updated with this PR.

For mergers

Use a conventional commit message to set the release level. Follow the guidelines.
Include information that users need to know about the PR in the commit message. The commit message becomes part of the GitHub release notes.
Use the Squash and merge option.

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

We need a test to test the extension DA. Also I suggest to rename directory chart -> charts

in order to do this we need to add the charts/ in the check-yaml precommit, that currently includes chart only

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

The apply completed successfully on the cluster, but there seemed to be an issue with the subsequent plan:
Error: [0m Error: [ERROR] Error downloading the cluster config [cn2khmaz0n010b7bbv3g]: Request failed with status code: 400, ServerErrorResponse: {"error":"server_error","error_description":"The authorization server encountered an unexpected condition that prevented it from fulfilling the request."}

It may have been a network or backend glitch, but since apply completed, we are going to force merge this in order to continue progress. We will be following this up with a cleanup PR anyway where we can address any issues we find.

:tada: This PR is included in version 1.0.0 :tada:
The release is available on:

GitHub release
v1.0.0

Your semantic-release bot :package::rocket:


Add pybind11 to environment dependencies of RNNT

I was unable to test RNNT model with the run.sh script since pybind11 was missing in dependencies. Installing it manually also didn't help only after adding it to dependencies test have run successfully.

@googlebot I signed it!

Hi @pavel-esir I wrote the original RNNT reference benchmark. Thank you for your message.
I suppose you are having trouble installing loadgen, which is the only thing that depends upon pybind11. You can see here that its setup.py file does include the pybind11 header files: https://github.com/mlperf/inference/blob/a6093d7c7dd2f267465eb80e3adcf6e77c5d9a13/loadgen/setup.py#L72 so I worry your change is not the right fix. In particular, when we ran the v0.7 benchmark, none of the submitters had a problem with installation of pybind11.
Pybind11 is a submodule in this repo. Can you check for me that your git submodules have been checked out?
Try this:
git submodule update --init --recursive

and then rebuild.
Note that the setup.py file is how loadgen is installed in the case of RNNT: https://github.com/mlperf/inference/blob/a6093d7c7dd2f267465eb80e3adcf6e77c5d9a13/speech_recognition/rnnt/run.sh#L36

@galv, thanks for your answer. With pybind11 from submodule it really worked. Closing the PR.


fix: changes to check team membership for main release permissions

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


Update ja_JP.po (POEditor.com)

My sincerest apologies, please do not merge this.
I was experimenting with "Poodle-ish" translation services, in an attempt to open translation up to less technical folks,
https://poeditor.com/join/project/GRir74KnBd
https://poeditor.com/join/project/GRir74KnBd
--
Apparently, it pushes a PR upstream, so my test lines came straight in here.
This was not my intention- I intended to set something up which did not bother you folks, until a translation was really ready to push in.
I'll adjust the settings and move on.

We are currently testing pootle internally. Perfect timing for the evaluation. I'll take a closer look. :)

Eeeeexellent.  I have no preference either way.
My intentions with this POEditor setup are:

Automate syncing to updated sources as much as possible
(important when multiple translators are chipping away simultaneously)
Be not-so-noisy to the "core" project
Attempting to get translator attribution into the repo commits, even for non-technical translators
Figure out how to moderate, attempting to keep sign-up as hands-off and open as possible.

Not sure if all those are quite possible out of the box with anything, but will see...


date_format using %w (day of week) returns incorrect values (1-7, not 0-6)

When using date_format, with the %w specifier (for day of week), we get incorrect values:
presto:default> select date_format(date_parse('2015-05-03 11:00', '%Y-%m-%d %H:%i'), '%w');
 _col0
-------
 7
(1 row)

According to the documentation:
%w	Day of the week (0 .. 6), where Sunday is the first day of the week

2015-05-03 was a Sunday, so we should expect this to return 0, not 7. Also, 7 is out of range of the values expected according to the documentation.
Testing with a date known to be a Monday:
presto:default> select date_format(date_parse('2015-05-04 11:00', '%Y-%m-%d %H:%i'), '%w');
 _col0
-------
 1
(1 row)

Is this a documentation bug, or an actual bug?
(Presto version is 0.101)

Looking at the test suite:
String dateTimeLiteral = "TIMESTAMP '2001-01-09 13:04:05.321'";
assertFunction("date_format(" + dateTimeLiteral + ", '%W')", VARCHAR, "Tuesday");
assertFunction("date_format(" + dateTimeLiteral + ", '%w')", VARCHAR, "2");

This is a documentation bug. Would you like a PR?

Looks like a real bug because we follow mysql's definition of format strings in date_format. @dain, do you have any insight on this?

We should make this work exactly like MySQL

It seems joda is using Monday as the first day of week.
Should day_of_week function also change the behavior?
MySQL's result is 1 for'2015-05-03'
mysql> select DAYOFWEEK(timestamp '2015-05-03');
+-----------------------------------+
| DAYOFWEEK(timestamp '2015-05-03') |
+-----------------------------------+
|                                 1 |
+-----------------------------------+
1 row in set (0.00 sec)

while presto's result is 7
presto:orc> select day_of_week(timestamp '2015-05-03');
 _col0
-------
     7
(1 row)

Query 20150527_083532_00015_vvwhd, FINISHED, 1 node
Splits: 1 total, 1 done (100.00%)
0:00 [0 rows, 0B] [0 rows/s, 0B/s]

day_of_week is defined to return the ISO day, so it is correct. The MySQL functions have (or should have) different behavior.


New Command: Create Bicep Config File

We provide intellisense for any file named "bicepconfig.json" , but a user has to:

Create this file
Type "{}" (if they don't type these brackets first, they will run into #5712)
Then use intellisense correctly to populate all of the rules

It would be great if we could instead, allow the user to select, create bicep config file, then ask them where they want to drop the file, and give them a full default file of all the rules to use.

This would be great to add.
We should think about where we add the new config file, though. The options are: current module's directory, parent dir, repo root.

Could always prompt for the folder or path within the workspace the user wants the file to be placed.

@wsmelton @ucheNkadiCode
The behavior we settled on in the meeting and that is implemented in https://github.com/Azure/bicep/pull/6187 is:

For the lightbulb on a linter issue ("Edit rule in bicepconfig.json"), I never ask the user, but save it in:
a) the root of the workspace containing the bicep file
b) if none, the root of the first workspace
c) if none, in the folder containing the bicep file
For the F1 -> Create Bicep Configuration File command, I bring up a save dialog for the user to indicate where to save the command.  Its defaults to the same folder that 1) uses above

It wouldn't be hard to change 1) to also show a save dialog.

@ucheNkadiCode Oh, there was one minor scenario where I couldn't show a save dialog on 1), but it's an edge case - the language server can't show a save dialog, so it will have to ask the extension to do so.  That means if we're running in something other than vscode (not officially supported), then I would have to just save without asking.

@StephenWeatherford, I'm unsure of the difference between 1A and 1B.
@wsmelton do you think this could suit your needs?
Our default is if the user clicks on the red squiggly of a Bicep file in subfolder called app/deploy/bicep then clicks the Lightbulb and selects "edit in bicepconfig.json", if they do not have a bicep file in the app/deploy/bicep folder, we will look at a higher level folder (app/deploy) and higher (app/)until we reach the root of the workspace (/). At that point, if we still do not find a bicepconfig.json, we will create a file there and the user can move it as they see fit. This makes it such that users can have multiple config files throughout their repo and our default behavior is to edit the config files that are closest to the specific Bicep file you are targeting

Linked to https://github.com/Azure/bicep/issues/5712
@StephenWeatherford
I'd love to make sure the same exact configuration we paste with the Create Bicep Config File gets pasted whether or not the user opens a fresh empty bicep file and writes "{}" or simply hits Ctrl + Space in an empty file.
This command is P1, that issue would be P2 because it is not what we want users to do, but it should still be supported.

Also related to #5318

@wsmelton The team took your feedback into consideration and we've decided that when a user clicks "Edit in bicepconfig.json", if there is no bicepconfig anywhere in their workspace, we'll simply prompt the user to ask them where they want to put the file.
It makes total sense that you should have control over where the file is placed. Thank you for your feedback!

It's not in yet.

The team took your feedback into consideration and we've decided that when a user clicks "Edit in bicepconfig.json", if there is no bicepconfig anywhere in their workspace, we'll simply prompt the user to ask them where they want to save the new file.

Moved this part to https://github.com/Azure/bicep/issues/6280


feat(client) ✨: Add min/max players check

This PR will check if the minimum player count is met in order to start the current game session. It will also check if the maximum player count is met (lobby is full) and prevent more players from joining in. Each check will display an error accordingly.

on line 2  in Lobby.svelte you have an unused component


[Question]: The created knowledge graph does not have edge relationships neo4j

Question Validation

[ ] I have searched both the documentation and discord for an answer.

Question

Use the qwen large model deployed locally in VLLM and the API service launched by OpenAI
The data used ishttps://raw.githubusercontent.com/run-llama/llama_index/main/docs/docs/examples/data/paul_graham/paul_graham_essay.txt
Code

from llama_index.core import SimpleDirectoryReader
documents = SimpleDirectoryReader("./paul_graham/").load_data()

import nest_asyncio

nest_asyncio.apply()

from typing import Literal
from llama_index.core.indices.property_graph import SchemaLLMPathExtractor
from llama_index.llms.openai_like import OpenAILike

# best practice to use upper-case
entities = Literal["PERSON", "PLACE", "ORGANIZATION"]
relations = Literal["HAS", "PART_OF", "WORKED_ON", "WORKED_WITH", "WORKED_AT"]

# define which entities can have which relations
validation_schema = {
    "PERSON": ["HAS", "PART_OF", "WORKED_ON", "WORKED_WITH", "WORKED_AT"],
    "PLACE": ["HAS", "PART_OF", "WORKED_AT"],
    "ORGANIZATION": ["HAS", "PART_OF", "WORKED_WITH"],
}

kg_extractor = SchemaLLMPathExtractor(
    llm = OpenAILike(
                     model="Qwen2-72B-Instruct",
                     api_key="fake",
                     api_base="http://ip:18090/v1",
                     is_chat_model=True),
   possible_entities=entities,
    possible_relations=relations,
    kg_validation_schema=validation_schema,
    strict=True,
)

from llama_index.graph_stores.neo4j import Neo4jPGStore
# from llama_index.legacy.graph_stores.neo4j import Neo4jGraphStore
graph_store = Neo4jPGStore(
    username="neo4j",
    password="password",
    url="neo4j://ip:7687"
)

from llama_index.core import PropertyGraphIndex
from llama_index.embeddings.huggingface import HuggingFaceEmbedding
embedding_path = "~/embedding_model/multilingual-e5-large-instruct"
index = PropertyGraphIndex.from_documents(
    documents,
    kg_extractors=[kg_extractor],
    embed_model=HuggingFaceEmbedding(model_name=embedding_path),
    property_graph_store=graph_store,
    show_progress=True
)

I am using Llamaindex to build a knowledge graph and have defined entities, relations, and validation_stemplates, but the generated knowledge graph does not have edge relationships

@dosu It's not that problem. I started the opanai interface using Fastchat and didn't build it according to the entity and edge relationships I provided. Can LLM use the OpenAILike method to load the local model

@dosu The result of the constructed knowledge graph
Displaying 22 nodes, 0 relationships

@dosu
How to use locally deployed models
kg_extractor = SchemaLLMPathExtractor(
    llm=Ollama(model="llama3", json_mode=True, request_timeout=3600),
    possible_entities=entities,
    possible_relations=relations,
    kg_validation_schema=validation_schema,
    strict=True,
)

@dosu
Can the Olama method use local models and how to use them.
kg_extractor = SchemaLLMPathExtractor(
llm=Ollama(model="llama3", json_mode=True, request_timeout=3600),
possible_entities=entities,
possible_relations=relations,
kg_validation_schema=validation_schema,
strict=True,
)

@dosu
I have encountered a problem
Received notification from DBMS server: {severity: WARNING} {code: Neo.ClientNotification.Statement.FeatureDeprecationWarning} {category: DEPRECATION} {title: This feature is deprecated and will be removed in future versions.} {description: The procedure has a deprecated field. ('config' used by 'apoc.meta.graphSample' is deprecated.)} {position: line: 1, column: 1, offset: 0} for query: "CALL apoc.meta.graphSample() YIELD nodes, relationships RETURN nodes, [rel in relationships | {name:apoc.any.property(rel, 'type'), count: apoc.any.property(rel, 'count')}] AS relationships"

Hi @nuocheng, were you able to resolve the issue? I am also getting 22 nodes and no edges as you mentioned above. Thanks!

@KAI10 Until now, no solution has been found. I found during the testing process that when using Schema LLMPath Extractor, GPU computing resources were not utilized. I also look forward to someone solving this problem.

@dosu  Does the SchemaLLMPathExtractor method support OpenAI and how should it be used

@KAI10  I use the API of OpenAI to build node and edge relationships normally, but the locally launched model cannot be built.


Add remove with a movement function

Problem/Opportunity
Sometimes it is hard to use remove because it always selects the previous node in a depth-first traversal. So after removing a selection may move arbitrarily deep in the tree structure. I propose to have an alternative version that applies a given traversal function so that you have better control over the selected node after the deletion.
Proposed Solution
(z/remove zloc z/left) selects the left sibling node after removing the current node.
(z/remove zloc z/right) selects the right sibling node after removing the current node.
(z/remove zloc z/prev) matches the current behavior.
Similar changes for z/remove* function.

Thanks for raising this issue @mrkam2!
I agree remove can be tricky to use for the reason you described.
Your idea is interesting!
For (z/remove zloc z/left), I assume we'd throw when there is no left node?
And the same idea for (z/remove zloc z/right) when there is no right node?

I guess it could simply return nil just as movement functions do. Throwing
is also an option.
On Fri, Mar 15, 2024, 5:17 PM Lee Read @.***> wrote:

Thanks for raising this issue @mrkam2 https://github.com/mrkam2!
I agree remove can be tricky to use for the reason you described.
Your idea is interesting!
For (z/remove zloc z/left), I assume we'd throw when there is no left
node?
And the same idea for (z/remove zloc z/right) when there is no right node?
—
Reply to this email directly, view it on GitHub
https://github.com/clj-commons/rewrite-clj/issues/258#issuecomment-2000748470,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGXVI5QG4B632ZAZVEK3SPLYYOFR5AVCNFSM6AAAAABEY2G23KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMBQG42DQNBXGA
.
You are receiving this because you were mentioned.Message ID:
@.***>


add br1ck, unenrollment exploit

This looks viable! I can’t test it but once it gets proved, yeah.

Before merging, I will wait for others to test and verify this exploit is legitimate.


Add national id entity type

Most countries will have a social security number or national identifier. Currently there is US_SSN and UK_NHS that covers USA and UK. To support other countries a more generic 'NATIONAL_ID'  entity type is added.

Puzzel (https://www.puzzel.com/) are implementing some additional recognizers to better handle Nordic and UK data. While developing recognizers for national identifiers in the Nordic countries (Norway, Sweden, Denmark, Finland, Iceland, Faroe Islands and Åland Islands) we did not find a good entity type to cover them. Currently there are "US_SSN" and "UK_NHS" for USA and UK, respectively. But the field type enum will grow very big if continuing to create a enum for each country to be supported. Maybe fields could be extended with a "country" property to specify which country the field type relates to, but we haven't followed that.
We plan to submit PRs in the 'presidio' project later for these recognizers, but we need the field type enum updated for internal testing which is why we submit that initially.

Hi @ahaeber, thanks for your PR.
Presidio lets you add custom recognizers either by code or API. The list here is for predefined recognizers. We are looking into extending the list of predefined recognizers, but in order to let the user filter out entities which are irrelevant for the use case, it's better to have one entity type per nation. Feel free to propose new recognizers on the main Presidio repo (github.com/microsoft/presidio)


Conflicting parameter requirements in Python SDK DataLakeFileClient

Type of issue
Typo
Description
Issue
The signature of methods and the corresponding Parameters section do not always align.
For example, the method upload_data has a signature of
upload_data(data: bytes | str | Iterable | IO, length: int | None = None, overwrite: bool | None = False, **kwargs) -> Dict[str, Any]
indicating length and overwrite both have defaults. However, the corresponding Parameters section states that these parameters are required.
Expected
To have the signature and descriptions align.
Page URL
https://learn.microsoft.com/en-us/python/api/azure-storage-file-datalake/azure.storage.filedatalake.datalakefileclient?view=azure-python#azure-storage-filedatalake-datalakefileclient-set-http-headers
Content source URL
https://github.com/MicrosoftDocs/azure-docs-sdk-python/blob/main/docs-ref-autogen/azure-storage-file-datalake/azure.storage.filedatalake.DataLakeFileClient.yml
Document Version Independent Id
5399f9d1-65df-b907-aee4-69584cc3e7f1
Article author
@lmazuel
Metadata

ID: 50acce08-5aa7-19f6-a652-d8606ad7595d
Service: azure-storage

Hi @award7 - thanks for opening an issue. We'll take a look asap.

Hi @award7 Aaron, thanks for your inquiry. We are currently working through a complete typing overhaul for the whole Python SDK, and have so far completed the overhaul for azure-storage-queue. With that being said, azure-storage-file-datalake will also be completed, but it is a rather large undertaking and I cannot give a great estimate for when the work will be completed.
And so, this issue will be addressed sometime in the future but likely will not be anytime in the immediate future (i.e. +/- 2 weeks). I assume that this is not a blocking issue (please let me know if otherwise) and so I will leave this issue to track the fix, but will likely not be closed until the typing overhaul work is done in the azure-storage-file-datalake package in its entirety.
Thanks!


config saml2

configure like this in /django-DefectDojo/dojo/settings/settings.dist.py
DD_SAML2_ENABLED=(bool, True),
    DD_SAML2_LOGIN_BUTTON_TEXT=(str, 'Login with SAML'),
    # Optional: display the idp SAML Logout URL in DefectDojo
    DD_SAML2_LOGOUT_URL=(str, 'https://simplesaml.mydomain.com/simplesaml/saml2/idp/SingleLogoutService.php'),
    # Metadata is required for SAML, choose either remote url or local file path
    DD_SAML2_METADATA_AUTO_CONF_URL=(str, 'https://simplesaml.mydomain.com/simplesaml/saml2/idp/metadata.php'),
    DD_SAML2_METADATA_LOCAL_FILE_PATH=(str, 'django-DefectDojo/dojo/settings/idp_metadata.xml'),  # ex. '/public/share/idp_metadata.xml'
    # Optional, default is SITE_URL + /saml2/metadata/
    DD_SAML2_ENTITY_ID=(str, ''),
    # Allow to create user that are not already in the Django database
    DD_SAML2_CREATE_USER=(bool, False),
    DD_SAML2_ATTRIBUTES_MAP=(dict, {
        # Change Email/UserName/FirstName/LastName to corresponding SAML2 userprofile attributes.
        # format: SAML attrib:django_user_model
        'mail': 'email',
        'sAMAccountName': 'username',
        'givenName': 'first_name',
        'sn': 'last_name'
    }),
    DD_SAML2_ALLOW_UNKNOWN_ATTRIBUTE=(bool, True),

but the "Login with SAML" button does not appear on the home page
What am I missing?

Ciao @emiemiemiemiemi
You need a login page with a template that links to this url
https://github.com/IdentityPython/djangosaml2/blob/5f956aab8d262cba84f1c52d78b710e059d9007d/djangosaml2/urls.py#L21

sorry for the delay I was offline.
I downloaded IdentityPython/djangosaml2
now I have :
si@si:~/django-DefectDojo/dojo/djangosaml2/djangosaml2/urls.py
but when restarting with docker-compose restart, the "Login with SAML" button still does not appear
this button should appear as the documentation says (https://defectdojo.github.io/django-DefectDojo/integrations/social-authentication/#saml-20)

I never implemented it in defect-dojo, I think that the login button is out of scope here.
I reopen this issue if I can help, I think that this issue could be shared with the dev team of defect-dojo if you agree

Yes I agree.
I need DefectDojo with saml2
Grazie mille

Grazie a te!

last question
How do I share it with the dev team of Defect-Dojo?

open an issue to defect-dojo e paste the link of this issue


Do we need to add composite index part in the included path

Hi,
do we need to explicitly add the part of the composite index in the included path if we excluded by default all path, because in the documentation all the example used for demonstrating the composite index are using the include everything path ?

So is this enough

or should we also need this

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: d3aeab4a-343d-b492-f9dc-a3233a117101
Version Independent ID: 075ccfaf-9b5c-aa6d-8a35-a57b4344773c
Content: Azure Cosmos DB indexing policies
Content Source: articles/cosmos-db/index-policy.md
Service: cosmos-db
Sub-service: nosql
GitHub Login: @seesharprun
Microsoft Alias: sidandrews

@Davilink
Thanks for your feedback! We will investigate and update as appropriate.

Hi @seesharprun,
Could you please look into this, thanks.

Thank you for reaching out,
Unfortunately, this is the documentation GitHub repository, and we cannot troubleshoot issues or provide technical support.
For technical support, please open a support ticket in the Azure portal. For questions about the product, please post them in Microsoft Q&A.
#please-close


http://kenju254.github.io/WordpressonGAE/#/1/3

"Ok . They why delpoy it on Google App Engine?" should be "Ok . Why deploy it on Google App Engine?"

@Johanndutoit fixed in the referenced commit . Closing this.


Explicit multi-tenancy support in @ResourceModels

Sometimes, particularly in a multi-tenant setup, it would be helpful if the @ResourceModel annotation could be made to apply only to some subtree in the content hierarchy. This could eliminate some problems with "competing" resource models that apply to the same resource type.
I envisage specifying an arbitrary number of Strings or even Patterns either as a "paths" parameter in the @ResourceModel annotation or in an extra annotation that can be combined with @ResourceModel. For the Strings, the method to check whether the criterion succeeds must not simply be "startsWith" but rather the one used in PagePathUtils.isPagePathInSubtree(String, String) [from the CQ Foundation library which is not part of this repository]. For Patterns, the code to decide wether a path matches would probably have to be something like this:
Matcher matcher = pattern.matcher(resourcePath);
boolean criterionMet;
if (matcher.lookingAt()) {
     if (matcher.end() <= 1) {
        criterionMet = true; // the pattern matched "" or "/"
     } else if (matcher.end() == resourcePath.length() || resourcePath.charAt(matcher.end()) == '/') {
        criterionMet = true; // the full path was matched, or the path continues with "/"
     } else {
        criterionMet = false;
     }
 } else {
    criterionMet = false;
 }

I think this should not be implemented because of two reasons.

It would make reasoning about matching Resource Models complex and error prone.
I don't see why this should be needed. If a multi-tenant project requires different resource models for different resources, those resources should simply use different ResourceTypes.

I agree with 1 - it will make matching significantly more complex. However, I definetly see valid cases for 2, for instance deviating models for common resource types such as nt:base or AEM specific types such as dam:Asset, cq:Page or cq:PageContent.
I am wondering whether we could make at an explicit "tenant" fwature out of this to simplify the resolution, something like
@Tenant("id"...)
And somehow map this to Sling's tenant support or some configuration of the form
tenantId -> root paths

Hi @DaniRey, could you have a quick look at the state of the Sling multi-tenancy support shipped with AEM 6.1?

I am closing this as won't fix. We'll get back to this once programmatic  multi-tenancy in sling is mature.


Bug: Profile -> Security -> Key Guardians

Describe the bug
They Key Guardians Card within Profile -> Security has a forever loading error where the loading icon is spinning without ever resolving.
To Reproduce
Steps to reproduce the behavior:

Go to 'Profile'
Click on 'Security Card'
See Key Guardians card
See error

Screenshots

Running on Android

@JGDoh Could you confirm if it still happens If not to close this issue.
I can't replicate it.
https://user-images.githubusercontent.com/42857405/129464678-3cd0cbc3-624d-4c9b-b39d-642d3beec08b.mp4

I’d be happy to try to reproduce and confirm 🤓 I’ll be online in a bit.
On Aug 15, 2021, 10:07 +0800, Raúl Urtecho @.***>, wrote:

@JGDoh Could you confirm if it still happens If not to close this issue.
I can't replicate it.
https://user-images.githubusercontent.com/42857405/129464678-3cd0cbc3-624d-4c9b-b39d-642d3beec08b.mp4
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

@buildc0de could you reproduce that? if not close this issue please

@buildc0de could you reproduce that? if not close this issue please

@buildc0de

Oh. Somehow this one fell off the radar 😊
Nope, I am unable to reproduce. Perhaps this was related to a specific build? @JGDoh Please let us know if you see it again. Closing for now.


Modify expired milestone for jxl

The expired milestone of jxl is set to 115, but I think this expired milestone is just a marker, it should not cause jxl to expire or become invalid in version 115, but I think it may be safer to change it to -1.
Related issue: https://github.com/Alex313031/thorium-libjxl/issues/3
@Alex313031

Should probably also modify the .patch file in the repo.


Prevent integer overflow in array_list_init functions

Description of changes:
Add error checking to the array_list_init* functions to avoid potential integer overflow.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Switched to the aws_fatal_assert() macro.  It was actually missing the stdio.h required for fprintf, so I had to add that too.

Didn't see Colden's comments and merged prematurely.  Can you create a new PR with the final fix?  Update seems small enough to warrant avoiding reverting and reapplying.

https://github.com/awslabs/aws-c-common/pull/251


Fix typos in "Ineffective mitigations" section

Remove unnecessary "is" and "ConsolidatedMessenger" in second paragraph

Thank you for the PR, @Geoff1900!


[Feature]: Leetcode  74. Search a 2D Matrix

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
I want to add a Solution for 74. Search a 2D Matrix Leetcode Question under Leetcode-solution Section.
Use Case
the viewer will be able to understand the logic behind the Question easily using their preferred Language.
Benefits
Easy to Understand | Solution in Cpp, Java, Pyhton | Briefly Answered
Add ScreenShots
NA
Priority
Medium
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[X] I have starred the repository

@ayushchaware08 Please complete your task otherwise I will close it.


[S3 Uploads] Wrap s3 copy in retries

Simple retries around the s3 cp commands
Also removes a redundant Airbrake below because the same line was being posted twice
Tested in local console by setting input_files.source to S3 paths and calling sample.initiate_s3_cp

Sad path
[2019-03-21T19:56:39] ERROR Rails : Try #0: Upload of S3 sample 'afewafdasfweafaewf' (12541) file 's3://test/bucket/here.fq.gz' failed with: download failed: s3://test/bucket/here.fq.gz to - An error occurred (403) when calling the HeadObject operation: Forbidden

gzip: stdin: unexpected end of file

[2019-03-21T19:56:50] ERROR Rails : Try #1: Upload of S3 sample 'afewafdasfweafaewf' (12541) file 's3://test/bucket/here.fq.gz' failed with: download failed: s3://test/bucket/here.fq.gz to - An error occurred (403) when calling the HeadObject operation: Forbidden

gzip: stdin: unexpected end of file

[2019-03-21T19:57:02] ERROR Rails : Try #2: Upload of S3 sample 'afewafdasfweafaewf' (12541) file 's3://test/bucket/here.fq.gz' failed with: download failed: s3://test/bucket/here.fq.gz to - An error occurred (403) when calling the HeadObject operation: Forbidden

gzip: stdin: unexpected end of file

[2019-03-21T19:57:17] ERROR Rails : Failed to upload S3 sample 'afewafdasfweafaewf' (12541): download failed: s3://test/bucket/here.fq.gz to - An error occurred (403) when calling the HeadObject operation: Forbidden

gzip: stdin: unexpected end of file

Happy path
[2019-03-21T19:58:10] DEBUG ActiveRecord::Base :   Sample Load (0.7ms)  SELECT  `samples`.* FROM `samples` ORDER BY `samples`.`id` DESC LIMIT 1
[2019-03-21T19:58:10] DEBUG ActiveRecord::Base :   InputFile Load (0.7ms)  SELECT `input_files`.* FROM `input_files` WHERE `input_files`.`sample_id` = 12541
[2019-03-21T19:58:10] DEBUG ActiveRecord::Base : Query Trace:
      app/models/sample.rb:249:in `initiate_s3_cp'
[2019-03-21T19:58:15] DEBUG ActiveRecord::Base :    (0.6ms)  BEGIN
[2019-03-21T19:58:15] DEBUG ActiveRecord::Base :   Project Load (2.7ms)  SELECT  `projects`.* FROM `projects` WHERE `projects`.`id` = 278 LIMIT 1
[2019-03-21T19:58:15] DEBUG ActiveRecord::Base : Query Trace:
      app/models/sample.rb:317:in `initiate_s3_cp'
[2019-03-21T19:58:15] DEBUG ActiveRecord::Base :   Sample Exists (2.9ms)  SELECT  1 AS one FROM `samples` WHERE `samples`.`name` = BINARY 'afewafdasfweafaewf' AND (`samples`.`id` != 12541) AND `samples`.`project_id` = 278 LIMIT 1
[2019-03-21T19:58:15] DEBUG ActiveRecord::Base : Query Trace:
      app/models/sample.rb:317:in `initiate_s3_cp'
[2019-03-21T19:58:15] DEBUG ActiveRecord::Base :   HostGenome Load (1.9ms)  SELECT  `host_genomes`.* FROM `host_genomes` WHERE `host_genomes`.`id` = 1 LIMIT 1
[2019-03-21T19:58:15] DEBUG ActiveRecord::Base : Query Trace:
      app/models/sample.rb:382:in `check_host_genome'
      app/models/sample.rb:317:in `initiate_s3_cp'
[2019-03-21T19:58:15] DEBUG ActiveRecord::Base :   PipelineRun Load (2.5ms)  SELECT  `pipeline_runs`.* FROM `pipeline_runs` WHERE `pipeline_runs`.`sample_id` = 12541 ORDER BY `pipeline_runs`.`created_at` DESC LIMIT 1
[2019-03-21T19:58:15] DEBUG ActiveRecord::Base : Query Trace:
      app/models/sample.rb:418:in `check_status'
      app/models/sample.rb:317:in `initiate_s3_cp'
[2019-03-21T19:58:15] DEBUG ActiveRecord::Base :   PipelineRun Exists (5.7ms)  SELECT  1 AS one FROM `pipeline_runs` WHERE `pipeline_runs`.`sample_id` = 12541 AND (job_status != 'FAILED' OR job_status IS NULL) AND `pipeline_runs`.`finalized` = 0 LIMIT 1
[2019-03-21T19:58:15] DEBUG ActiveRecord::Base : Query Trace:
      app/models/sample.rb:557:in `kickoff_pipeline'
      app/models/sample.rb:425:in `check_status'
      app/models/sample.rb:317:in `initiate_s3_cp'
[2019-03-21T19:58:15] DEBUG ActiveRecord::Base :   SQL (0.8ms)  UPDATE `samples` SET `status` = 'checked', `updated_at` = '2019-03-21 19:58:15' WHERE `samples`.`id` = 12541
[2019-03-21T19:58:15] DEBUG ActiveRecord::Base : Query Trace:
      app/models/sample.rb:317:in `initiate_s3_cp'
[2019-03-21T19:58:15] DEBUG ActiveRecord::Base :    (2.4ms)  COMMIT
=> true

@tfrcarvalho I think that's a possibility as well, but at that point we might want to look at AWS Managed Uploads because it seems like we'd be reimplementing that https://datalanguage.com/features/s3-managed-uploads


Shallow flatten incorrectly flattens map

When a Map is in a Seq, and the Seq is flattened, the Map will also be flattened. IMO this shouldn't happen.
Seq.of(Map([[1,2]])).flatten(true).get(0)
yields 2 (i.e. the value), not the Map.

I don't know about this...


Grant Application: Dante Network

Project Abstract
Dante Network is a middleware to empower multiple ecosystems to interoperate and interconnect in web3. In Dante Network, we define and offer a general protocol stack to realize interoperability and interconnection. This is an infrastructure bringing innovative experiences in web3, just as internet protocol is for today’s internet. With this infrastructure, participants in web3 can make general message transmission and contract invocation between multi-chains.
Keywords: middleware, infrastructure, multi-chains, internet protocol
For which grant level are you applying?

[ ] Level 1:  Up to $10,000, 2 approvals
[x] Level 2:  Up to $50,000, 3 approvals
[ ] Level 3:  Unlimited, 5 approvals (for > $100k Web3 Foundation Council approval)

Application Checklist

[x] The application template has been copied, renamed ( project_name.md) and updated.
[x] A BTC or Ethereum (DAI/USDT) address for the payment of the milestones is provided inside the application.
[x] I have read and acknowledged the terms and conditions.
[x] The software delivered for this grant will be released under an open-source license specified in the application.
[x] The initial PR contains only one commit (squash and force-push if needed).
[x] The grant will only be announced once the first milestone has been accepted.

Hi @xiyu1984, thank you for your application! We will look into it as soon as possible.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.0 out of 2 committers have signed the CLA.:x: JasonIn404:x: xiyu1984You have signed the CLA already but the status is still pending? Let us recheck it.

Thanks for the application. I have a few initial questions.

If I understand it correctly, you basically want to create a bridge between a lot of different ecosystems. How exactly do your routers (=relayers?) work? Are they trust minimising in any way or are they centralised?
Did you take a look at IBC?
What are potential attack vectors of your solution and how do you address these?

Thanks for the application. I have a few initial questions.

If I understand it correctly, you basically want to create a bridge between a lot of different ecosystems. How exactly do your routers (=relayers?) work? Are they trust minimising in any way or are they centralised?
Did you take a look at IBC?
What are potential attack vectors of your solution and how do you address these?

Reply
For the first question, yes, we are building a protocol stack to make lots of ecosystems connected, as the internet protocol stack did for the web2 internet.
The implementation of this protocol stack consists of smart contracts deployed on different public chains and lots of off-chain nodes. These could be considered similar situations in web2, which will be easy for readers to understand.
Generally, the off-chain nodes are decentralized and open, that is, they are working with a consensus mechanism combined with message verification algorithms, node selection and evaluation algorithms, and economic incentives, which are implemented by off-chain applications and on-chain smart contracts together. Simply speaking, every message from one chain to another is delivered by a subset of nodes, which are selected randomly according to the credibility evaluated along with their history behavior. The higher the credibility is, the higher the probability one will be chosen, and the more incentives one will get. This is the simplest way to present how Dante Network works. Nodes are selected each time when delivering messages, which is similar to the selection of routing in web2, so we call the off-chain nodes “routers”. The difference is that routers in web3 are working parallelly.
Details can be seen in our white paper.
For the second question, the Inter-Blockchain Communication Protocol. I think we have a similar philosophy but different starting points. IBC built an infrastructure and asked users to create surrounding it. But we are building an infrastructure to connect ecosystems that already exist. The difference is that we build out protocol stack “into” the existing ecosystems in the form of smart contracts, which is similar to TCP/IP, HTTPS protocols embedded in operating systems.
The third question is about security, I will explain more in detail.
We focus on the underlying communication between ecosystems, therefore, generally,  the attack vectors we consider are mainly about the messages, that is:
Exploiting faulty nodes to deliver incorrect messages.
Exploiting the vulnerabilities of smart contracts to cheat or make unauthorized operations.
Our security mechanism could be simply explained in the picture below. Details are in our white paper.

Generally speaking, we improve the security of the Dante protocol stack in two dimensions.
From the vertical perspective, we improve the security by bringing in randomness when selecting routers and multi-level message verification. For every message transported from one chain to another, there would be several routers to deliver message copies parallelly. These routers are selected randomly every time, thus decreasing the possibility of routers colluding to do malicious acts. Messages are verified based on many copies, and the trustworthiness of one message is aggregated according to the credibilities of the related working routers. Besides, for higher security demands, challenge mechanisms will be brought in to make more confirmation steps for verification, which would indeed increase the cost of malicious attacks(we’ve made simulations of this, details could be seen in the “Belif verification” chapter of our white paper.
From the horizontal perspective, we improve security by extensions. Firstly, for higher security demands, more routers and higher verification thresholds are needed. More routers increase the cost of collusion. The verification threshold is not only the number of routers, but also their credibilities, according to which the message’s belif is weighted. A new router with an initial credibility value cannot have enough weights to affect the result of message verification. Therefore, hypothetically, if  someone wanted to do something bad, he would improve his credibility first by successfully executing enough valid operations. Secondly, we provide a freaking high security level with the SQoS item “Cross Verification”, that is, besides Dante protocol stack’s build-in verification mechanism, we are able to import verification mechanisms of other similar multi-chain communication infrastructures to make cross-validation of the messages. This indeed satisfies very high security demands, but there is no free lunch, sacrifices in efficiency and expensive payments happen.
By the way, as we mentioned before, we focus on communication infrastructures between multi-ecosystems. And as an infrastructure, security is not the whole story, because there are many kinds of dApps, and not all of them need very high security level. But because of the blockchain trilemma in Web3, sometimes we cannot achieve both the security and efficiency. So in our protocol stack, we create a specialized mechanism called SQoS(Security Quality of Service) to make regulations. This could be regarded as the QoS in TCP/IP protocol suite.
Finally, the vulnerabilities of smart contracts is a general problem for all web3 projects. It will be fully tested on the testnet. And there will also be some special hackathon events related to security. Besides, a third party(like slowmist) code auditing will be made before the mainnet is launched.

@Noc2 @takahser
If there is anything else that I have not expressed clearly, please contact me, thank you.

Thanks for the application. I have a few initial questions.

If I understand it correctly, you basically want to create a bridge between a lot of different ecosystems. How exactly do your routers (=relayers?) work? Are they trust minimising in any way or are they centralised?
Did you take a look at IBC?
What are potential attack vectors of your solution and how do you address these?

Reply
For the first question, yes, we are building a protocol stack to make lots of ecosystems connected, as the internet protocol stack did for the web2 internet.
The implementation of this protocol stack consists of smart contracts deployed on different public chains and lots of off-chain nodes. These could be considered similar situations in web2, which will be easy for readers to understand.
Generally, the off-chain nodes are decentralized and open, that is, they are working with a consensus mechanism combined with message verification algorithms, node selection and evaluation algorithms, and economic incentives, which are implemented by off-chain applications and on-chain smart contracts together. Simply speaking, every message from one chain to another is delivered by a subset of nodes, which are selected randomly according to the credibility evaluated along with their history behavior. The higher the credibility is, the higher the probability one will be chosen, and the more incentives one will get. This is the simplest way to present how Dante Network works. Nodes are selected each time when delivering messages, which is similar to the selection of routing in web2, so we call the off-chain nodes “routers”. The difference is that routers in web3 are working parallelly.
Details can be seen in our white paper.
For the second question, the Inter-Blockchain Communication Protocol. I think we have a similar philosophy but different starting points. IBC built an infrastructure and asked users to create surrounding it. But we are building an infrastructure to connect ecosystems that already exist. The difference is that we build out protocol stack “into” the existing ecosystems in the form of smart contracts, which is similar to TCP/IP, HTTPS protocols embedded in operating systems.
The third question is about security, I will explain more in detail.
We focus on the underlying communication between ecosystems, therefore, generally, the attack vectors we consider are mainly about the messages, that is:

Exploiting faulty nodes to deliver incorrect messages.
Exploiting the vulnerabilities of smart contracts to cheat or make unauthorized operations.

Our security mechanism could be simply explained in the picture below. Details are in our white paper.

Generally speaking, we improve the security of the Dante protocol stack in two dimensions.
From the vertical perspective, we improve the security by bringing in randomness when selecting routers and multi-level message verification. For every message transported from one chain to another, there would be several routers to deliver message copies parallelly. These routers are selected randomly every time, thus decreasing the possibility of routers colluding to do malicious acts. Messages are verified based on many copies, and the trustworthiness of one message is aggregated according to the credibilities of the related working routers. Besides, for higher security demands, challenge mechanisms will be brought in to make more confirmation steps for verification, which would indeed increase the cost of malicious attacks(we’ve made simulations of this, details could be seen in the “Belif verification” chapter of our white paper.
From the horizontal perspective, we improve security by extensions. Firstly, for higher security demands, more routers and higher verification thresholds are needed. More routers increase the cost of collusion. The verification threshold is not only the number of routers, but also their credibilities, according to which the message’s belif is weighted. A new router with an initial credibility value cannot have enough weights to affect the result of message verification. Therefore, hypothetically, if someone wanted to do something bad, he would improve his credibility first by successfully executing enough valid operations. Secondly, we provide a freaking high security level with the SQoS item “Cross Verification”, that is, besides Dante protocol stack’s build-in verification mechanism, we are able to import verification mechanisms of other similar multi-chain communication infrastructures to make cross-validation of the messages. This indeed satisfies very high security demands, but there is no free lunch, sacrifices in efficiency and expensive payments happen.
By the way, as we mentioned before, we focus on communication infrastructures between multi-ecosystems. And as an infrastructure, security is not the whole story, because there are many kinds of dApps, and not all of them need very high security level. But because of the blockchain trilemma in Web3, sometimes we cannot achieve both the security and efficiency. So in our protocol stack, we create a specialized mechanism called SQoS(Security Quality of Service) to make regulations. This could be regarded as the QoS in TCP/IP protocol suite.
Finally, the vulnerabilities of smart contracts is a general problem for all web3 projects. It will be fully tested on the testnet. And there will also be some special hackathon events related to security. Besides, a third party(like slowmist) code auditing will be made before the mainnet is launched.

@Noc2 @takahser
If there is anything else that I have not expressed clearly, please contact me, thank you.

Sorry for the late reply here. Thanks for the detailed reply. I have to be honest, so far I haven’t seen anyone implement a feature or replacement of a consensus protocol based on “credibility ratings”, “trust scores” etc. that worked. Without looking into the research behind it my assumption would be that the main problem is that you can behave 99.9% honest and only misbehave in case of really valuable transactions or for your personal edge cases. However, the way I see it, the credibility feature in your case isn’t strictly necessary, since you also have a solution similar to optimistic roll-ups in which you try to leverage fraud proofs, which only works if you also implement a long enough lock period (window in which you can actually challenge the transactions). How long do you think this lock/waiting period needs to be?
Regarding the application itself, could you specify the programming/smart contract language of each deliverable. We usually don’t support the development of solidity smart contracts via our grants program. On the one hand, we are no experts when it comes to solidity. On the other hand, we don’t know what exists and what doesn’t. So, it would be nice if you could either use ink! or develop a pallet for this project.

We really appreciate your questions and suggestions.
Firstly, I can’t agree with you more, that “the credibility feature in your case isn’t strictly necessary” if we consider it separately. But if we make it work along with a PoS-like mechanism(I forgot to mention it before), the efficiency and robustness of our consensus will be improved. So next, I will list some more details of our consensus mechanism.
Our consensus mechanism is a combination of PoW and PoS. The credibility feature is part of the PoW(Strictly speaking, it should be proof of historical work). And the PoS part is not very different from others, where staking and slashing are defined. In our project, the key points of the consensus are as follows:
Staking and credibility work together to affect the probability of the off-chain routers to be selected(within a certain period) to work for rewards; The selection is implemented by smart contracts deployed on the receiving chain.
The reward for routers is affected by credibility, and so is the slashing. Generally, with higher credibility, the router will get more rewards for doing honest work and will be slashed more tokens for doing evil. So if a router “behaves 99.9% honest and only misbehaves in case”, it will be punished more. So “with great power comes great responsibility”.
Credibility is also related to the verification, it determines the weight of message copies, which may improve the efficiency of the network.
In general, with our consensus mechanism, the determination of the rights and benefits are divided into two parts: the one based on someone’s history work, another one is based on the staking amount. So maybe credibility is a complement to the staking mechanism. We have made some simulations about this in our technical white paper(in chapter 3.2). More tests will be made on the testnet and we have the confidence to get more evidence at that time.
Secondly, about the challenge time window. As mentioned before, we focus on communications infrastructure. So we provide choices for users to determine the balance of scalability and security by SQoS mechanisms. That is, users can choose the length of the window according to their security demands by setting the related SQoS Item. And we also provide a default value respectively for every public chain, that is affected by the average cost of transmission and the validation time of different public chains. The concrete default value will be adjusted after fully tested on testnet.
Thirdly, about the programming/smart contract technology stack. Generally, using ink! for contract development is no problem for us, and we are considering related parachain such as AStar, edgeware. We sincerely hope you can give us some advice.
Although I mentioned solidity-related points, actually it’s not the core of this grant. That’s just because the Dante protocol stack is for communication and interoperation of multi-chains, so after we complete it in the Polkadot ecosystem, we need some other ecosystems to test and prove the deliverable. I will modify the PR doc to make it more clear.
Lastly, about the pallet. We are glad to provide a pallet version of the Dante protocol stack in the future. And in this grant application, we would like to implement the ink! version first.
Anyway, if there are any other suggestions, we would love to discuss it with you anytime. We really appreciate it.
Looking forward to your reply.

Thanks again for the detailed reply and update of the application. I’m happy to go ahead with it and will share it with the rest of the team. I guess my biggest concern at this point is the overall complexity of your protocol, but that’s not necessarily a bad thing. Regarding ink! Smart contract chains, it’s up to you. I believe in the near future we will have additional chains that support ink! smart contracts. Now that ink! is in a very good stage.

Thank you very much~ Let's keep in touch.

The demo video link is updated~

Hi @xiyu1984 Thanks for your application and all the resources you've shared. Can you elaborate on the following or guid me where I can find any related information?

On a very high level, how does router credibility evaluation work?
On a very high level, how does the message verification algorithm work?
While it doesn't matter for the acceptance for this grant, is there any specific reason you're using PlatON? In contrary to some other projects you mention, it doesn't seem to be as popular, so I was wondering if they might have specific features to offer that are convenient to your use case.

Reply
First of all, thank you so much for the suggestions for changes to the document.
In general, the first and second questions are detailed in our technical white paper, Chapter 3.2 Data Routing for router credibility evaluation and Chapter 3.3 Information verification for message verification algorithm.
The router credibility evaluation is part of the Data Routing mechanism.

For high-level situations, after one router submitted a message copy and the data verification contract completes the verification, the validator scheduling contract will check the result and decide whether to make an increment or a decrement to the router. The increasing trend is an "S" curve, while the decreasing trend is an "L" curve. Because, once it gets punished due to malicious behaviors, it needs to complete more honest work to get back to the same score it used to have. The credibility will work along with the economical mechanism to affect the selection of validators and the staking/reward/slashing amount. As I introduced in the previous reply.
The whole story of the message verification algorithm includes two parts, one is Commitment verification and another is Belief verification.
Commitment verification is service-oriented, that is, I trust what you said because you can provide proof of the service according to a cryptographical commitment the receiver had previously. The instance of a commitment can be a hash value or Merkle tree root in data services or can be set up parameters along with the input of a ZK-proof-based computation. In this situation, messages can be delivered by only one router, but the utility scenarios are limited to the situation where the receiver needs the commitment in advance.
So Belief verification is brought in. One message is delivered by multiple routers parallelly, and as the name of it, the receiver makes aggregation of all the message copies according to the credibility of every router, so that the receiver can get the most trustworthy content of the message, or drop this message if the trustworthiness threshold is not achieved. This mechanism can be adapted to numerous situations, but of course, this brings in redundancy.
About the third question, we think that web3 world is diverse, open, and needs to be constructed together. PlatON has its edges on privacy-preserving computation. This capability is considered to be useful in the future digital world. That is also the reason we consider deploying Dante on it, we would like to integrate different kinds of resources and capabilities for users and developers in web3 and make it accessible for everyone. Actually, the privacy-related functions are still not carried out on PlatON’s mainnet, but we think it might be worth waiting.

Thank you for this application, @xiyu1984, and sorry for my late reply.
I am happy to support this project, although I agree with David and Seraya that its complexity is a bit of a risk factor. Just one minor request: can you modify the specification of deliverables 1.0d and 2.0e to be more precise? It currently contains our template text, and I think it would make sense to agree on a medium and rough direction beforehand.

Reply
Thank you very much for the suggestions. I’ve fixed 0b, 0d in the 1st milestone and 0b, 0e in the 2nd milestone to make it more precise.
We really appreciate your concern about the complexity, and we agree with you that this is not a simple thing. If we look into the development of the Internet, we will find that it’s also a complex system and is constructed step by step. We do not plan to complete the whole Dante protocol stack in a short time. There is a long way to go, and we want every step to have a solid foundation and make it worth it.
It will start with a basic working version on which to improve the algorithms, introduce more flexible SQoS items, and provide a more user-friendly SDK interface. For example, build-in random mechanisms (like ink_env::random) will be chosen to support routing selection algorithms at the early stage. And a third-party or more advanced VRF might be a better choice in the future.
Besides, Dante protocol stack is open-source, everyone skilled and interested in it can make their contributions to improve or optimize the protocol stack, any constructive suggestion deserves consideration and adoption, and many hands make light work.
We really appreciate your suggestions as Polkadot is a great pioneer in this field.
Thanks again. Looking forward to your reply. @semuelle @takahser @Noc2

Hey,
It's about one month since we start this project. We have made some progress now, and some details are as follows:

Our project repo is here. The main work is in the develop branch
We have completed the basic communication between ink! smart contracts and other chains(temporarily not Polkadot's ecosystem), including message definitions and basic smart contracts working for sending and receiving messages from and to ink! smart contract.
Some of the core algorithms of the protocol stack have been implemented and tested in ink! smart-contract deployed on local substrate node, including node selection algorithm, tokenomics related algorithm.

In general, everything goes well and we can complete our milestones on time.
Next work:

Next, we will develop an SDK(test version) to help other ink! smart contracts communicate to other chains not in the Polkadot ecosystem easily.
We will complete the development of the core algorithms mentioned in the first milestone.

@xiyu1984 Thanks a lot for the update. I added your ink! smart contracts already to our tech stack document: https://github.com/w3f/Grants-Program/blob/master/docs/polkadot_stack.md

Hey @Noc2 @takahser @semuelle :
We have submitted the delivery of milestone one here. Thanks for your time to check it~ :)

Hey @Noc2 @takahser @semuelle,
We've submitted our milestone one about 20 days ago, and now we are developing the next milestone. Please contact us if there's anything we can do to help you review milestone one. We are glad to discuss anything with you if it helps~

Hey @Noc2 @takahser @semuelle ,
We've submitted the delivery of Dante Network Milestone 2.
Feel free to check the details of the delivery and we will be very glad to receive your suggestions.
We really appreciate the help from W3F, and to achieve higher and more efficient security in Dante protocol there might be a long way to go. Generally speaking, we are planning to build a multi-layers gaming model based on the current Dante to improve security more efficiently. We also present our future works at the end of the delivery.
Hope for deeper collaboration with you.
Best wishes,
Xiyu,
Dante Network


[Enhancement] Improve load json array not set strip_outer_array error message

Why I'm doing:
load json to table
create table t1(k1 int);

[{"k1":  1 }, {"k1": 2}]

"Message": "Failed to iterate document stream as object. error: INCORRECT_TYPE: The JSON element does not have the requested type."

What I'm doing:
"Message": "The value is array type in json document stream, you can set strip_outer_array=true to parse each element of the array as individual rows, value: [{\"k1\":  1 }, {\"k1\": 2}]"

Fixes #issue
What type of PR is this:

[ ] BugFix
[ ] Feature
[x] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Does this PR entail a change in behavior?

[x] Yes, this PR will result in a change in behavior.
[ ] No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

[x] Interface/UI changes: syntax, type conversion, expression evaluation, display information
[ ] Parameter changes: default values, similar parameters but with different default values
[ ] Policy changes: use new policy to replace old one, functionality automatically enabled
[ ] Feature removed
[ ] Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

[x] I have added test cases for my bug fix or my new feature
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

[ ] This is a backport pr

Bugfix cherry-pick branch check:

[x] I have checked the version labels which the pr will be auto-backported to the target branch

[x] 3.3
[x] 3.2
[x] 3.1
[ ] 3.0
[ ] 2.5

ignore backport check: 3.3.2


setIconSizeFraction() missing in NavigationTabBar.java

navigationTabBar.setIconSizeFraction(0.5); in documentation does not work with compile:navigationtabbar1.2.3
setIconSizeFraction() is either missing or the documentation is incorrect and it has been removed/replaced?
The following picture displays the position from where the code is missing:
http://imgur.com/DZJZM4W
This is the code that is missing:
    public float getIconSizeFraction() {         return mIconSizeFraction;     }     // To reset scale fraction of icon to automatic just put in method AUTO_SCALE value     public void setIconSizeFraction(final float iconSizeFraction) {         mIconSizeFraction = iconSizeFraction;         requestLayout();     }
Thank you for making such a great resource!

Hello. Thanks for this issue. Id look it today and try to fix it.

Hello. Thanks for this issue.
I forget to update NTB to 1.2.4 on Bintray. Wait for this.


Themes support

Can you please implement themes support?

Done. Added two themes:

Default white theme.
Dark theme


adb.exe: error: closed when i run the react native app

Please provide all the information requested. Issues that do not follow this format are likely to stall.
I'm a new in react native so first thing I made is to install react native by running
npm install -g react-native-cli
and after running react-native info
I get this
C:\Users\husam\WebstormProjects\calculator>react-native info
info Fetching system and libraries information...
System:
    OS: Windows 10 10.0.18363
    CPU: (4) x64 Intel(R) Core(TM) i3-7020U CPU @ 2.30GHz
    Memory: 815.06 MB / 3.92 GB
  Binaries:
    Node: 12.16.1 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.1 - C:\Program Files (x86)\Yarn\bin\yarn.CMD
    npm: 6.14.4 - C:\Program Files\nodejs\npm.CMD
    Watchman: Not Found
  SDKs:
    Android SDK:
      API Levels: 10, 11, 12, 13, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 7, 8, 9
      Build Tools: 19.1.0, 28.0.3, 29.0.3
      System Images: android-19 | Intel x86 Atom, android-29 | Google Play Intel x86 Atom
      Android NDK: Not Found
  IDEs:
    Android Studio: Version  <IP_ADDRESS> AI-192.7<IP_ADDRESS>08749
  Languages:
    Java: 1.8.0_231
    Python: 3.7.6
  npmPackages:
    @react-native-community/cli: Not Found
    react: 16.11.0 => 16.11.0
    react-native: 0.62.2 => 0.62.2
  npmGlobalPackages:
    *react-native*: Not Found

after that I create a new project with webstorm from here
[https://www.jetbrains.com/help/webstorm/react-native.html
]
after that I launch the emulator with 19 API level
and then I run the App.js file and I get this
"C:\Program Files\nodejs\node.exe" C:\Users\husam\AppData\Roaming\npm\node_modules\react-native-cli run-android
info Running jetifier to migrate libraries to AndroidX. You can disable it using "--no-jetifier" flag.
Jetifier found 960 file(s) to forward-jetify. Using 4 workers...
info JS server already running.
info Installing the app...
> Task :app:generatePackageList
> Task :app:preBuild
> Task :app:preDebugBuild
> Task :app:compileDebugAidl NO-SOURCE
> Task :app:checkDebugManifest UP-TO-DATE
> Task :app:compileDebugRenderscript NO-SOURCE
> Task :app:generateDebugBuildConfig UP-TO-DATE
> Task :app:javaPreCompileDebug UP-TO-DATE
> Task :app:mainApkListPersistenceDebug UP-TO-DATE
> Task :app:bundleDebugJsAndAssets SKIPPED
> Task :app:generateDebugResValues UP-TO-DATE
> Task :app:generateDebugResources UP-TO-DATE
> Task :app:mergeDebugResources UP-TO-DATE
> Task :app:createDebugCompatibleScreenManifests UP-TO-DATE
> Task :app:processDebugManifest UP-TO-DATE
> Task :app:processDebugResources UP-TO-DATE
> Task :app:compileDebugJavaWithJavac UP-TO-DATE
> Task :app:mergeDebugShaders UP-TO-DATE
> Task :app:compileDebugShaders UP-TO-DATE
> Task :app:generateDebugAssets UP-TO-DATE
> Task :app:mergeDebugAssets UP-TO-DATE
> Task :app:copyDebugBundledJs SKIPPED
> Task :app:processDebugJavaRes NO-SOURCE
> Task :app:mergeDebugJavaResource UP-TO-DATE
> Task :app:checkDebugDuplicateClasses UP-TO-DATE
> Task :app:desugarDebugFileDependencies UP-TO-DATE
> Task :app:transformClassesWithDexBuilderForDebug UP-TO-DATE
> Task :app:validateSigningDebug UP-TO-DATE
> Task :app:signingConfigWriterDebug UP-TO-DATE
> Task :app:mergeExtDexDebug UP-TO-DATE
> Task :app:mergeDexDebug UP-TO-DATE
> Task :app:mergeDebugJniLibFolders UP-TO-DATE
> Task :app:mergeDebugNativeLibs UP-TO-DATE
> Task :app:stripDebugDebugSymbols UP-TO-DATE
> Task :app:packageDebug UP-TO-DATE

> Task :app:installDebug
10:21:40 V/ddms: execute: running am get-config
10:21:45 V/ddms: execute 'am get-config' on 'emulator-5554' : EOF hit. Read: -1
10:21:45 V/ddms: execute: returning
Installing APK 'app-debug.apk' on 'MY_phone(AVD) - 4.4.2' for app:debug
10:21:45 D/app-debug.apk: Uploading app-debug.apk onto device 'emulator-5554'
10:21:45 D/Device: Uploading file onto device 'emulator-5554'
10:21:45 D/ddms: Reading file permision of C:\Users\husam\WebstormProjects\calculator\android\app\build\outputs\apk\debug\app-debug.apk as: rwx------
10:21:49 V/ddms: execute: running pm install -r -t "/data/local/tmp/app-debug.apk"
10:22:25 V/ddms: execute 'pm install -r -t "/data/local/tmp/app-debug.apk"' on 'emulator-5554' : EOF hit. Read: -1
10:22:25 V/ddms: execute: returning
10:22:25 V/ddms: execute: running rm "/data/local/tmp/app-debug.apk"
10:22:26 V/ddms: execute 'rm "/data/local/tmp/app-debug.apk"' on 'emulator-5554' : EOF hit. Read: -1
10:22:26 V/ddms: execute: returning
Installed on 1 device.

Deprecated Gradle features were used in this build, making it incompatible with Gradle 7.0.
Use '--warning-mode all' to show the individual deprecation warnings.
See https://docs.gradle.org/6.0.1/userguide/command_line_interface.html#sec:command_line_warnings

BUILD SUCCESSFUL in 4m 49s
27 actionable tasks: 2 executed, 25 up-to-date
info Connecting to the development server...
adb.exe: error: closed
info Starting the app on "emulator-5554"...
warn Failed to connect to development server using "adb reverse": Command failed: C:\Users\husam\AppData\Local\Android\Sdk/platform-tools/adb -s emulator-5554 reverse tcp:8081 tcp:8081
WARNING: linker: libdvm.so has text relocations. This is wasting memory and is a security risk. Please fix.
Starting: Intent { cmp=com.calculator/.MainActivity }

the error as showing in the log Is about the adb but I can use the adb command to install and get logcat in both the emulator and the real devices without any error
after searching on the internet I tried to run this two commands
adb reconnect
adb reverse tcp:8081 tcp:8081
but I get the same error as following
C:\Users\husam\WebstormProjects\calculator>adb reconnect
reconnecting 4203605bb24a3200 [device]

C:\Users\husam\WebstormProjects\calculator>adb reverse tcp:8081 tcp:8081
adb.exe: error: closed

the code that I run is the default one that is created by react native
also the app is installed successfully on my emulator but when I run it
how I can solve this issue ?

⚠ Missing Environment Information ℹ Your issue may be missing information about your development environment. You can obtain the missing information by running react-native info in a console.

I already run react-native info

Facing the same issue

@hussam132 do you found The solution?

@SampaioPedro
Unfortunately no

I had the same problem, and it is solved when I changed the API of the emulator from 19 to 29. So, the problem is the API version.
But Also make sure that you run >npm install, and open two terminals, in the first one type >react-native start
and in another terminal type >npx react-native run-android. Moreover, make sure that you don't have any problem with the port.

@judy-D can you run react-native info in your terminal and show me

@hussam132
I changed my device and now everything is working fine, I was using Android 4.4.4 and now I'm using Android 6

I'm having same problem even with a new project. I'm unable to run my app in Android Emulators less then version 5.0.
I tried everything. At the end, I completely reinstalled my MACOS and tried again. Same result

yes the solution was about the API level of my android evaluator I discovered that the minimum level supported now  is 21

it happens because of diffrent version of adb in emulator and sdk. and using adb reverse works for andriod version 5 or higher.

it happens because of diffrent version of adb in emulator and sdk. and using adb reverse works for andriod version 5 or higher.


faye-browser-min.js.map on faye-rails (1.0.6)

While using Faye-rails time after time i get this error. Where is importing this file?


Fix produced events if patching a finalizer fails

The returned resource is broken (as nothing on it) if the Patch operation fails, which causes the produced event to be incomplete and in the wrong namespace (default).
Actually using a known-to-be-correct version of the object fixes the issue.
/assign @n3wscott

/test pull-knative-pkg-unit-tests


fix the font family of the paragraphs

can I work on it?

can I work on it?

yup assigned you this task


/opt/rocm-4.0.0/include/hip/hcc_detail/hip_vector_types.h:32:2: error: ("This version of HIP requires a newer version of HCC."); #error("This version of HIP requires a newer version of HCC.");

I build simple vectoradd_hip.cpp in docker and meeted this error. Accroding to error message, should I to upgrade hipcc ? What caused this problem?
docker environment:

Package: rocm-libs
Version: <IP_ADDRESS>000-23
Priority: optional
Section: devel
Maintainer: Advanced Micro Devices, Inc.
Installed-Size: 13.3 kB
Depends: hipblas, hipcub, hipsparse, miopen-hip, rocalution, rocblas, rocfft, rocprim, rocrand, rocsolver, rocsparse, rocthrust
Homepage: https://github.com/RadeonOpenCompute/ROCm
Download-Size: 826 B
APT-Manual-Installed: yes
APT-Sources: http://repo.radeon.com/rocm/apt/4.0 xenial/main amd64 Packages
Description: Radeon Open Compute (ROCm) Runtime software stack

$/opt/rocm/bin/hipcc --version

HIP version: 4.0.20496-4f163c68
clang version 12.0.0 (/src/external/llvm-project/clang dac2bfceaa8d4a90257dc8a6d58f268e172ce00e)
Target: x86_64-unknown-linux-gnu
Thread model: posix
InstalledDir: /opt/rocm-4.0.0/llvm/bin

@jianlongf,  Apologies for the lack of response. Can you please test with latest ROCm 6.0.2 (HIP 6.0.32831)? If resolved, please close ticket. Thanks!


Initiate an alerting module

Generating alerts based on user rules would provide a great added-value, something similar to https://openweathermap.org/triggers should not be too much hard to implement. Indeed, with probes we already have the element values for user POI. Triggering an alert is just a matter of running regularly a query to check the probe values against the rules. The hardest part is probably to manage a duration the rules have to be valid throughout, the MongoDB aggregation framework can probably help a lot here. Here the proposal for this system.
Service operation:

CREATE an alert requires a probe id, a set of rules (ie query) to be checked and a cron pattern to know when to check it
REMOVE an alert can be directly called or alerts will be automatically removed at each run if the associated probe does not exist anymore

Alert structure:

CRON pattern as supported by node-cron, it is not probably necessary to go under hours
QUERY is a list of conditions to be checked (like any weather conditions request we can already do now), a time range where to check these conditions, a duration the conditions must hold within this time range, and possibly a geometry query to limit the check area in the probe
CONDITION is a meteorological element, a comparison operator ($gt, $lt, etc.) and a target value
TIME RANGE is defined relatively to the execution time of the check, eg [T0+24h-T0+48h]

The final aggregated request might looks like:
probeResults.aggregate([
  { $geoNear: { area } }, // Geometry filtering
  { $match: { $and: [ conditions, time range ] }, // Filter probes
  { $sort: { forecastTime: -1 } }, // Order by time
  { $group: { _id: { xxx }, times: { $push: '$forecastTime' } }, // Group by probe
  { $replaceRoot: { newRoot: { fields, count: { $size: '$times' } } }, // Count forecast times raising alert for each probe
  { $match: { count: { $gt: duration / interval } } // Check if this is greater than alert duration
})

For instance an alert might raise if the temperature during the next 24h is above 35° during at least 6h.

Initiated repo https://github.com/weacast/weacast-alert.

See https://github.com/weacast/weacast-probe/issues/4#issuecomment-430748241 as a proof of concept for aggregation.


Ensuring that the host visible buffer to read compute data from is on the VRAM (device)

The selected memory type used to create the buffer memory "hostMemory" declared in line 235 was not necessarily corresponding to a device-local memory queue, i added the requirement for a device-local buffer memory.

I don't think this is correct. Your change always checks if the requested memory type supports VK_MEMORY_PROPERTY_DEVICE_LOCAL_BIT, even for the first host visible buffer where this won't work on most discrete GPUs that don't have shared memory.
That's not correct imo, so can you elaborate as to why this change would be correct?

Closing due to inactivity.


Create balanced_ternary.py

Balanced Ternary representation is too trivial to be included. Marking as invalid. Please come up with a better algorithm/program.


No Column Headers in CSV output

Hi when I output the scan result to csv, no column headers were there in the output.
default |<PHONE_NUMBER> | us-east-1 | 2.6 | PASS | Scored | Level 1 | [check26] Ensure S3 bucket access logging is enabled on the CloudTrail S3 bucket (Scored)  | Bucket access logging enabled in CloudTrail S3 bucket
What are the column headers for the above scan result. Is this a bug that headers are not in the csv file.

Thanks @S733  What is the command you do run? What are the steps to reproduce it? It is comma separated and comes with header...
Sent with GitHawk

Please use the latest code in master or latest release and you will see CSV header. See this as example:
./prowler -M csv

Generating "," delimited report on stdout for profile , account<PHONE_NUMBER>012
PROFILE,ACCOUNT_NUM,REGION,TITLE_ID,RESULT,SCORED,LEVEL,TITLE_TEXT,NOTES
<results here comma separated>

Please feel free to reopen this ticket if that is not your case and let us know how did you installed, run prowler, etc, to reproduce your issue.

pull latest code please, I added the header to the output file in addition to the stdout.


Removed the local implementation of application and implemented the required features directly into a kingpin fork

Simplified the configuration of environment variables & flag aliases
Changed the layout of the help to make it more readable
Removed the global variable app and the need to supply global variables to many function
Improved some tests to make them more robust
Better garbage collecting on test resources (there were some leaks)
Do not print stack on managed error unless TGF_DEBUG is set

Pull Request Test Coverage Report for Build 834

116 of 172 (67.44%)  changed or added relevant lines in 4 files are covered.
5 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-3.06%) to 40.183%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

cli.go
60
63
95.24%

main.go
0
15
0.0%

docker.go
12
30
40.0%

config.go
44
64
68.75%

Files with Coverage Reduction
New Missed Lines
%

main.go
2
0.0%

docker.go
3
23.48%

Totals

Change from base Build 806:
-3.06%

Covered Lines:
352

Relevant Lines:
876

💛  - Coveralls


Clean up Imports

Some of the import statements are becoming unruly. Many of these can be condensed using an alias (import * as vsc from 'vscode').

Fixed in eb43a46. This has also been documented in the CONTRIBUTING.md document.

PR #12


Navigator is deprecated and has been removed from this package

I get the following error when I use react-router-native.
Navigator is deprecated and has been removed from this package. It can now be installed and imported from react-native-deprecated-custom-components instead of react-native. Learn about alternative navigation solutions at http://facebook.github.io/react-native/docs/navigation.html
"dependencies": {
		"react": "16.0.0-alpha.6",
		"react-native": "0.44.0",
		"react-redux": "^5.0.5",
		"react-router": "^4.1.1",
		"react-router-native": "^4.1.1",
		"redux": "^3.6.0",
		"redux-thunk": "^2.2.0"
	}

Even I am getting the same.. What can i do?

In ur project package use "npm list | grep react" to show the package list.
and try running "npm install react-router-native"


Removed comma separator

Description
Fixes #5260
area: fr.free.nrw.commons.description.DescriptionEditActivity#updateDescription
The comma separator between descriptions in different languages has been removed from fr.free.nrw.commons.description.DescriptionEditActivity#updateDescription line 154. This also made line 157 redundant as its function was deleting the very last comma after all the descriptions were formatted.
Tests performed
Tested beta build on Xiaomi Redmi 9 using Android 11.

I seem to have caused that myself when I modified DescriptionEditActivity#updateDescription, I added the deleted line back in and now it's working as it should:
https://commons.wikimedia.org/w/index.php?title=File:Catedral_de_Aguascalientes.jpg&diff=prev&oldid=784872825


Add specification for new sparse vector query; deprecate specification for text_expansion and weighted_tokens queries

Adds specification for the new sparse_vector query and deprecates the specifications for text_expansion and weighted_tokens queries.

if I got this right every sparse query should have either query_vector or inference_id, the way we model this to have it checked client side is to add /** @variants container */ on top of the class and mark all properties that can always be added with @variant container_property, an example of this is PinnedQuery where you must set either ids or docs

if I got this right every sparse query should have either query_vector or inference_id, the way we model this to have it checked client side is to add /** @variants container */ on top of the class and mark all properties that can always be added with @variant container_property, an example of this is PinnedQuery where you must set either ids or docs

Thanks @l-trotta! I think I got this right?

almost! all properties that aren't query_vector or inference_id should be @variant container_property, so not just field. basically this is to assure that either query_vector or inference_id are set, but not both of them, while all the other properties are unaffected by this check.


Misc Typo

The following line contains a typo
Distributing reports in this manner means that refreshing data for reports will done individually by each user. This situation might impact Business Central performance.
should be
Distributing reports in this manner means that refreshing data for reports will be done individually by each user. This situation might impact Business Central performance.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: f562094f-cff2-2c71-c806-e548041718e2
Version Independent ID: 4f1e5021-2ea3-ba4b-8da8-a999589b8962
Content: Building Reports in Power BI Desktop to Display Business Central Data - Business Central
Content Source: business-central/across-how-use-financials-data-source-powerbi.md
Service: dynamics365-business-central
GitHub Login: @jswymer
Microsoft Alias: jswymer

Thanks for the feedback! This has been fixed and the update will be published soon.


Post terraform output to the PR

"The output of Terraform is not posted to the PR. It would be nice if that could be added"
https://developer.hashicorp.com/terraform/language/values/outputs
by @daanbosch

This is unrelated to terraform output. This seems like a bug in the CLI, it doesn't show the outputs which terraform prints post plan/apply. See this screenshot of the job and the comment posted as a result of that job (outputs missing in comment)


Update strategy matrix

The strategy matrix uses now only includes. This improves readability when several Elixir versions are tested. Furthermore, not all possible combinations are included in the matrix. However, the matrix will continue to include all Elixir versions with the latest patch and all OTP versions.

Pull Request Test Coverage Report for Build ba5d84d4850505c245f94d9da7e7f39699278760-PR-10
Details

17 of 20 (85.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.6%) to 94.286%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

lib/git_hub_actions/versions.ex
17
20
85.0%

Totals

Change from base Build d710244160f80f59640786e9c285bbfeaa302c31:
-0.6%

Covered Lines:
330

Relevant Lines:
350

💛  - Coveralls


BLE connectivity problem ESP-IDF-3.3.1 (IDFGH-2609)

Environment

Development Kit: Custom board with ESP32-Wrover-B
Module or chip used:  ESP32-WROVER-B
IDF version: v3.3.1
Build System:  Make
Compiler version: 5.2.0
Operating System: macOS v10.15.2
Using an IDE?: No
Power Supply: external 5V

Problem Description
Hi, I have faced BLE disconnection problem while sending data to device from Samsung Galaxy S10. This smartphone definitely does something different, compared to other smartphones, but I guess it could be handled. Bluedroid Bluetooth stack is being used. Problem is easy to reproduce using example from ESP-IDF v3.3.1 (GATT_SERVICE_TABLE_DEMO) and there is no such such problem with the same example provided in ESP-IDF v4.0-rc or master. Also there is no such problem using NimBLE (I have tried to create the same behaviour app, but with new stack).
Expected Behavior

Connecting to device
Requesting MTU
Sending large data block (more than 40-60 bytes)

Actual Behavior

Connecting to device
Requesting MTU (any size causes problem)
Trying to send data
Disconnecting with reason 0x8 (timeout)

Steps to reproduce

Connect to device flashed with GATT_SERVICE_TABLE_DEMO
Requesting MTU (for example 400)
Send large data block (more than 40-60 bytes)

Code to reproduce this issue
ESP-IDF v3.3.1 - GATT_SERVICE_TABLE_DEMO example
Debug Logs (nrfConnect)
Log text - failed sending
Log text - expected behaviour while sending

We have exactly the same issue. It also happens with the Samsung Galaxy Note10+

Hello, we have solved this problem before and the backport to release/v3.3 is in process. Thank you for your report. Please wait for our update.

@andrew-krv @Ben139348 are you using Android 10 OS on your devices?

@andrew-krv @Ben139348 are you using Android 10 OS on your devices?

Yes, we are. Issue seems to be reproducible only using Galaxy S10 or Galaxy Note 10 (any of their variation) and Android 10.

We have just flashed to the latest version on release/v3.3 and are no longer seeing this specific issue on our Galaxy S10+ devices running Android 10, but on one of the two (seemingly identical) devices we are finding that a similar but different issue has surfaced. More often than not, the mobile app that is connecting to the ESP32 will send a message but will never get a response (the BLE connection stays intact though). To complicate debugging this issue, when we have the ESP32 print all sent/received messages to the console, the issue disappears. We are thinking it might have something to do with message timing on the ESP32 side, but will need to do additional testing to confirm. Still no issue with other Android or iOS devices that we've tested with though.
@andrew-krv and @Ben139348, we'd love to hear if the latest version fixes your original issues and if you come across anything similar to what I've mentioned above. Thanks!

@rjcasson  Thank you for your information. We have indeed backported the solution in release / v3.3.  We did not encounter the new issue you mentioned. If you have a way to reproduce the problem, please let me know. Thank you.

@rjcasson issue seems to be fixed with latest release/v3.3 branch, currently works on our device.

@andrew-krv Glad to know that your issue is resolved @GYC-Espressif Thanks for the support. Feel free to reopen if the issue still happens. Thanks.


Dev documentation changes: Add slot to fieldset

📇 User story
As a developer, I want to add documentation about a slot in the fieldset component so that other developers can understand how to use it effectively.
✅ Definition of Done / Outcomes

[ ] Done when the website documentation is updated to have information about the default slot
[ ] Done when storybook event and properties page has been updated to include the default slot

📜 Acceptance criteria

[ ] The purpose of the slot in the gcds-fieldset component should be clearly described.
[ ] The documentation should explain what a slot is in the context of the fieldset component.

📝 More info
Do we need content updates on the fieldset documentation to describe the usage for the slot?
This issue was raised by a user through our contact us feedback form.

re: ticket 19078


How to pronounce k3ai?

An International Phonetic Alphabet expression would be useful to understand how to pronounce this interesting project!

fixed in https://github.com/kf5i/k3ai/commit/900dfdf5896ba047592a2a8357a02ff659a2078b latest documentation k3ai is pronounced keɪ3ai based on IPA standards


Added pieces to make carnival an official extension

Used the documentation to add the pieces that were missing.

Looks good. Please create a tag after you merge this.


How to move views inside ConstraintLayout?

In one activity where main layout is android.support.design.widget.CoordinatorLayout moving fab works fine. But in other activity root is android.support.constraint.ConstraintLayout and even though I added two buttons with setViewsToMove they don't seem affected in any way by showing SnackProgressBar.
Is it expected behavior? Maybe I'm doing sth wrong?
I can provide some minimal example if needed.

Just a quick question first. Did you have android:animateLayoutChanges="true" in your ConstraintLayout xml?

I didn't have that, but adding it doesn't seem to do a trick.

I just tried out with ConstraintLayout and have no issue with moving the buttons or even a mixture of different views. I guess this happened because you have a rather complicated layout. Are those buttons actually encapsulated by a Linear / Relative Layout that has "wrap_content"? Based on my experience, when animating a view, we are moving a view relative to a parent. So if the parent is already wrapping the view, nothing will happen. If that is the case, try moving the parent layout instead.
Post your xml here if it is still not working. I'll have a look when free.

Is your problem solved? I'm closing this soon.


[Quantum] [DRAFT - Do not merge] Convert max_poll_wait_secs to float

The initial type of the --max-poll-wait-secs parameter value from the az quantum job wait command is str.  It needs to be converted to float to avoid raising an exception in a logical expression that compares it to another float variable.

This checklist is used to make sure that common guidelines for a pull request are followed.

Quantum


TypeScript import/order regression

I've just upgraded to<EMAIL_ADDRESS>and<EMAIL_ADDRESS>and started to get import/order errors:

Any module defined in @types/* (e.g. @types/express in this case) is seen as "internal", while modules with their own types (e.g. http-status-codes) are seen as "external". I've tried with other modules as well.
Changing the default order to:
    'import/order': [
      'error',
      {
        groups: ['internal', 'external'],
      },
    ],

Gets rid of the error.
Can't understand the root cause though, but here's some logging from the resolver if it helps:

The import/order rule history doesn't seem to have anything suspicious. Could the new version of the resolver be causing this?
Re: https://github.com/alexgorbatchev/eslint-import-resolver-typescript/issues/33

And this is the resolver log with eslint-import-resolver-typescript:

As you see, the new version resolves the correct definition under<EMAIL_ADDRESS>while the old one resolved the original node_modules/**/*.js.

Yes, that sounds like it's due to the typescript resolver.

And the last evidence 🙂:

Will look at the code now.

So, the package name is express, path is<EMAIL_ADDRESS>
it passes the external regexp
but it's not external because path.indexOf('node_modules/express') == -1

We could simply use the import/external-module-folders setting to include the @types folder as ['node_modules', 'node_modules/@types'] in the typescript config, or change the isExternalPath logic to account for these scenarios.
@ljharb what do you think is best? I'm worried that with the setting it doesn't solve the problem for people that are already overriding it.

Answer from eslint-import-resolver-typescript:
https://github.com/alexgorbatchev/eslint-import-resolver-typescript/issues/34

I've also suddenly got this issue in our projects at work.
@Evalon's linked issue has been closed and locked and now @ljharb has closed this issue.
So what's actually the suggested solution here? Are we waiting on something to be merged or does something else need doing somewhere?

@South-Paw in fact, it was closed by the PR #1526, which has been released - do you not see that in the timeline entry?

@ljharb sorry I totally missed that 🤦♂
I think the issue I'm seeing is unrelated to this one though, so sorry for digging up the wrong issue to reply to 😟 - I've created #1643