how i get opnesl.ld file each library version?

i am compiling openssl library.
i want add .gnu.version_d information.
so i did find openssl.ld file(example : https://gist.github.com/Scottmitch/71a89d98b3af272aab6ae6bfed122c5a) but i not found openssl.ld file.
how i get openssl.ld file each library version?

What version of OpenSSL are you compiling, and where do you get your sources from?
The normal place we hear about openssl.ld files is when the Debian packaging's build system is used; in that case, you might be better served by apt-get source openssl and making your modifications there, rather than trying to start from unmodified upstream OpenSSL (which is what this github repository is for).

Does not appear to be an OpenSSL problem. Closing this.


Add support for column27

Called "REFERENCE PLATCE" in XSD
Otherwise, the module crashes:
  File "/home/nijel/weblate-web/payments/backends.py", line 393, in fetch_payments
    for transaction in client.last(from_date=from_date):
  File "/home/nijel/weblate-web/.venv/lib/python3.7/site-packages/fiobank.py", line 135, in _parse_transactions
    field_name, convert = schema[column_name.lower()]
KeyError: 'column27'

Thanks! Could you please change the commit message to the following?
fix: add support for column27

Called "REFERENCE PLATCE" in XSD

This way, if I merge the PR, it's gonna auto-release a new version using the Semantic Release. Thanks!

Pushed with changed commit message and fixed tests.

Thanks! I wonder why the broken tests didn't manifest under the PR. I'll have to revisit the CI setup on the library soon. Hopefully the auto-release is going to work 🤔

it's gonna auto-release a new version using the Semantic Release.

Does that cover PyPI release as well? I can see there is 2.0.0 on GitHub, but 1.2.0 on PyPI....

It should! The v2 wasn't released and it's documented. But now I see Travis CI apparently gives up on running on this repo completely 🤯 This is going to take some time to fix.

Released as v3. I had to re-set the Travis connection and then drop Python 3.5 from supported versions as Travis won't install it out of the box anymore (end of life of 3.5 has been a month ago or so). I hope that's not an issue for you. Thanks for the fix and for the opportunity to revisit and fix the CI setup here 🚀

Dropping 3.5 support is definitely not an issue for me. Thanks for prompt release.


Add capability to the indexer to handle different file versions

As an administrator, I would like to handle different versions of each metadata file.
Right now the indexer assumes that all the files inside a bundle belong to a single version. However, as specified by the metadata group, we will have bundles with metadata files of mixed metadata versions.
As such, we need to add the capability to the indexer to detect the version for each file, and index accordingly.
DOD: The indexer takes bundles, detects the version of each metadata file, and indexes accordingly to a specified class for each metadata file and version combination. Includes Unit test

Superseded by #116.


[SPARK-48696][SQL][CONNECT] Also truncate the schema row for show function

What changes were proposed in this pull request?
This PR abbreviated the header/schema row for the show function to align the value rows
scala> spark.sql("select INTERVAL '10000' MONTH").show

+----------------------+
|INTERVAL '10000' MONTH|
+----------------------+
|  INTERVAL '10000' ...|
+----------------------+
scala> spark.sql("select typeof(INTERVAL '2021-07' YEAR TO MONTH)").show
+---------------------------------------+
|typeof(INTERVAL '2021-7' YEAR TO MONTH)|
+---------------------------------------+
|                   interval year to ...|
+---------------------------------------+

scala> spark.sql("select typeof(INTERVAL '2021-07' YEAR TO MONTH)").show(20, false)
+---------------------------------------+
|typeof(INTERVAL '2021-7' YEAR TO MONTH)|
+---------------------------------------+
|interval year to month                 |
+---------------------------------------+

Why are the changes needed?

Fix display issue when schema with long names
Does this PR introduce any user-facing change?

yes, but we have function parameters and configs to restore
How was this patch tested?

new tests
Was this patch authored or co-authored using generative AI tooling?

no

Thank you @allisonwang-db for your advice.
The behavior change is limited in the scope of our REPLs, does it sound overdesign to add a configuration for df.show() -> df.show(false)?

Instead of a configuration, what about a new parameter in dataframe.show()?
also cc @cloud-fan and @HyukjinKwon


Strengthen configuration change approval

Before asking a question, make sure you have

[X] Searched existing Stack Overflow questions
[X] Googled your question
[X] Searched open and closed GitHub issues
[X] Read the documentation

What is your question?
Strengthen configuration change approval
An approval process for the change to the file path scope of global variables and configurations will be deployed.
Why
Currently the reviewers and approvers in root OWNERS file are for git repository granularity, can not fine-grained control over changes in important areas. Configuration/variable changes can have a wide-ranging impact, affecting system stability and compatibility. Recently, there have been several online issues caused by configuration/variable changes.
To minimize the negative impact of configuration/variable changes, ensure that each change undergoes careful consideration and evaluation and comes with clear documentation, and reduce the risk of online issues, we plan to pilot pre-approval of configuration changes in the pingcap/tiflow repo and delegate the approval responsibility to the person in charge of maintaining the TiDB product.
What's new for developer
Same as before and no new actions introduced for the developers to perform. All the changes need to be approved by committers or maintainers as before except if there are configurations changes, the PRs need also to be approved by approvers inside /OWNERS_ALIASES file. The approvers will be notified automatically on GitHub.
Set up

Now we use prow's OWNERS mechanism to control the approving for pull requests, here is the PR review flow.
We setup an OWNERS_ALIASES file in root folder in repository to maintain the approver teams for variable or configuration changes.
We setup serval OWNERS files in sub folders to support approving by folder or file paths. And make it not inherit from parent OWNERS files to ensure the changes must be approved by the dedicated approvers.
The changes should be approved by the matched approvers that are configured in OWNERS files(layer by layer in folder level), and leaf approvers first.
All the changes must be approved before merging.
OWNERS and OWNERS_ALIASES files should be updated on time.
If file paths need to be updated, we should update the OWNERS files in the leaf folders.
If the approver member should be updated, we should update the /OWNERS_ALIASES file.

Role and Responsibility

For contributor

Assess the system's needs and requirements before making any configuration changes, considering factors such as performance, scalability, security, and compatibility.
Implement the configuration changes and verify that any changes made to the codebase or configuration maintain backward compatibility.
Conduct testing to verify the effects of configuration changes, checking for any adverse impact on system behavior, performance, or compatibility.
In case of any issues or unexpected outcomes resulting from the configuration changes, contributors actively troubleshoot and work towards resolving them.
Document the configuration parameters that affect user behavior and any system variable changes (adding, deleting, deprecating, modifying) by creating pull requests to documentation repositories (pingcap/docs, pingcap/docs-cn), adding the changes to release notes, and updating relevant documentation, to ensure that users have access to accurate and up-to-date information.

For approver

Thoroughly review all proposed configuration change pull requests. This involves examining the details of the proposed modifications, such as the purpose, impact, and potential risks associated with the configuration change.
Evaluate the impact these changes may have on the system or any related components. This includes considering potential risks, such as performance impact, security vulnerabilities, or conflicts with existing configurations.
Validate that the proposed configuration changes in the pull requests have undergone appropriate testing.
Confirm the necessary documentation PR has been created.
Grant approval for the PR.

/type enhancement

/remove-label question


[Question]: Is it possible to use LlamaIndex ReAct Agent with Citation Query Engine

Question Validation

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

Question
Good Evening,
I am trying to use the ReAct Agent from the documentation:
https://docs.llamaindex.ai/en/stable/examples/agent/react_agent_with_query_engine.html
with the Citation Query Engine from the documentation:
https://docs.llamaindex.ai/en/stable/examples/query_engine/citation_query_engine.html
My question is: Is it possible to use the CitationQueryEngine with the ReAct Agent? If so how can it be done?
I tried doing the following, but all I got was the ReAct Agent telling me that the information is unreadable or corrupted during the Observation phase:
control1_engine = CitationQueryEngine.from_args(
control_index,
llm=llm_35,
similarity_top_k=3,
)

control2_engine = CitationQueryEngine.from_args(
control_index,
llm=llm_35,
similarity_top_k=3,
)

query_tool_control1 = QueryEngineTool.from_defaults(
    query_engine = control1_engine,
    metadata = ToolMetadata(
        name = "information_controls_1",
        description = (
            f"Provides a set of building blocks for describing the tasks, knowledge, and skills that are needed to perform information work through the first set of controls."
            f"Control Set 1"
        ),
    ),
)
query_tool_control2 = QueryEngineTool.from_defaults(
    query_engine=control2_engine,
    metadata = ToolMetadata(
        name = "information_controls_2",
        description = (
            f"Provides a set of building blocks for describing the tasks, knowledge, and skills that are needed to perform information work through the second set of controls."
            f"Control Set 2"
        ),
    ),
)

query_engine_tools = [query_tool_control1, query_tool_control2]

agent = ReActAgent.from_tools(
    query_engine_tools,
    llm=llm_4,
    verbose=True,)

query_engine = MultiStepQueryEngine(
    query_engine = agent,
    query_transform=decompose_transform,
    index_summary=index_summary
)

🤖
Hey there, @JoseGHdz! Great to see you diving deep into the LlamaIndex toolkit again. How's everything going on your end?
Yes, it is possible to use the CitationQueryEngine with the ReAct Agent in LlamaIndex. The integration can be achieved by ensuring that the CitationQueryEngine is implemented as a BaseTool or AsyncBaseTool and then making it available to the ReAct Agent either directly through the tools parameter or via a tool_retriever that can dynamically fetch the tool based on the context or input.
Given your current implementation, the steps to integrate the CitationQueryEngine would involve:

Implementing the CitationQueryEngine as a BaseTool or AsyncBaseTool: Ensure that the CitationQueryEngine adheres to the interface expected by the ReAct Agent for tools. This means implementing the necessary methods such as call for synchronous tools or acall for asynchronous tools, and ensuring it returns a ToolOutput.

Making the CitationQueryEngine Available to the ReAct Agent:

If you have a static list of tools, including the CitationQueryEngine, you can pass them directly to the ReActAgentWorker constructor via the tools parameter.
If the tool needs to be dynamically selected based on the input or other criteria, implement an ObjectRetriever<BaseTool> that can fetch the appropriate tool (including the CitationQueryEngine) based on the given criteria. Pass this retriever to the ReActAgentWorker constructor via the tool_retriever parameter.

Handling the Tool Output: Ensure that the output of the CitationQueryEngine is in a format that the ReAct Agent can understand and process. This might involve formatting the output as a ToolOutput object and ensuring that any data returned is correctly interpreted by the ReAct Agent's reasoning steps or output parser.

Here is a simplified example of how you might implement the CitationQueryEngine as an AsyncBaseTool and integrate it:
from llama_index.legacy.tools.types import AsyncBaseTool, ToolOutput

class CitationQueryEngine(AsyncBaseTool):
    async def acall(self, query: str) -> ToolOutput:
        # Implement the logic to perform the citation query based on the input query
        # For example, querying a database or an external API
        result = await perform_query(query)
        return ToolOutput(result)

# Assuming you have an instance of CitationQueryEngine
citation_query_engine = CitationQueryEngine()

# When creating the ReActAgentWorker, pass the CitationQueryEngine as part of the tools list
react_agent_worker = ReActAgentWorker(tools=[citation_query_engine], llm=my_llm_instance)

In this example, perform_query would be a placeholder for the actual logic to perform the citation query. The key is to ensure that the CitationQueryEngine's output is compatible with the ReAct Agent's expectations, which typically means wrapping the result in a ToolOutput object.
If the ReAct Agent indicates that the information is unreadable or corrupted, it could be due to a mismatch in the expected output format or an error in the processing logic of the CitationQueryEngine. Ensure that the output is correctly formatted and that any exceptions or errors in the CitationQueryEngine are handled appropriately to produce a valid ToolOutput.
The expected format of the ToolOutput object that the CitationQueryEngine should return to be compatible with the ReActAgent is a string that includes:

A Thought: section, which is a textual representation of the reasoning or thought process behind the action or answer.
An Action: section, which specifies the action to be taken. This is expected to be a single word or a combination of alphanumeric characters and underscores.
An Action Input: section, which contains a JSON string representing the input to the action. This JSON string should be well-formed, but the parser attempts to handle cases where the JSON might be poorly formatted by using a more lenient JSON parser (dirtyjson) and a fallback method (action_input_parser) that can handle certain irregularities.

The Action Input: section is particularly important for the CitationQueryEngine as it would contain the necessary parameters or data the engine needs to perform its citation query. The JSON string in this section should be structured in a way that the CitationQueryEngine can understand and process.
Here is an example of how the ToolOutput string might be structured:
Thought: I need to query a citation database to find relevant sources.
Action: CitationQuery
Action Input: {"query": "example search terms", "limit": 5}

This string format allows the ReActAgent to parse the output using the parse_action_reasoning_step function and construct an ActionReasoningStep object with the thought process, the action to be taken (CitationQuery in this case), and the action input as a dictionary (parsed from the JSON string).
For more details, you can refer to the source code of the ReAct Agent and the output parser in the LlamaIndex repository:

llama-index-legacy/llama_index/legacy/agent/react/step.py
llama-index-legacy/llama_index/legacy/agent/react/output_parser.py

I hope this helps! If you have any further questions or need more clarification, feel free to ask.
Sources

llama-index-legacy/llama_index/legacy/agent/react/step.py
llama-index-legacy/llama_index/legacy/agent/react/output_parser.py

About Dosu
This response is meant to be useful and save you time. It is not meant to be a precise solution, but rather a starting point for your own research.
Help me be more useful! Please leave a 👍 if this is helpful and 👎 if it is irrelevant.
If you want to continue the conversation, start your reply with @dosu-bot.

Where is the ReActAgentWorker() coming from? What's the import for it.


Move Q004 to AST based checker

Summary
Continuing with #7595, this PR moves the Q004 rule to the AST checker.
Test Plan

[x] Existing test cases should pass
[x] No ecosystem updates

Thank you for the suggestion. That's a good idea. I'll just do the change for the string and bytes literal here and merge it.


Add syft tool

Closes #131

LGTM. Could you add syft to the table in "Supported tools" section in README.md? (like this)

Yes, I forgot

Published in 2.10.0.


Why not use yarn start?

The readme says use yarn install and npm start.
Why not use yarn start as well since you are using yarn already.  It does the same thing.

Might as well, it doesn't really matter since, as you say, they do the exact same thing; I just wanted to emphasize its use for dependencies where there is actually a difference. Will update for consistency.

Done: https://github.com/davezuko/react-redux-starter-kit/commit/97f0fd1fb5d9c368a0ea1b24e36725d8327db183
Going to leave the table of run commands as npm run just for simplicity, but will consider updating it next time I work on the readme.

FYI yarn has known issues..

I am aware; the nice part is it's not at all necessary to use it, just encouraged. Need to drive things forward somehow!

Yarn issues I've encountered are with install. X yarn start is the same thing as npm start


Monkit metrics for IPFS node

Monkit metrics + endpoint for the IPFS node with the Storj datastore plugin.

PR https://github.com/storj/ipfs-go-ds-storj/pull/38

Additional improvement with #39


Update welcome-back-to-cpp-modern-cpp.md

Fix comment leader.  The trailing comment was missing a / in the comment leader.

@compnerd : Thanks for your contribution! The author(s) have been notified to review your proposed change.

You’re welcome :)


No such file or directory error from project.rs

The create-rust-app cli is always giving me this error:
thread 'main' panicked at 'failed to execute process: Os { code: 2, kind: NotFound, message: "No such file or directory" }', /Users/jarviskennedy/.cargo/registry/src/github.com-1ecc6299db9ec823/create-rust-app_cli-9.0.0/src/content/project.rs:274:10

hey @Jarvismkennedy, hope things are well :)
Sorry you ran into this. Could I ask which commands you ran exactly? For example, the following is working for me:
cargo install create-rust-app_cli

create-rust-app my-project
# all plugins enabled, using all permutations of actix-web/poem/sqlite/postgres

Hey, thanks for the response!
I ran cargo install create-rust-app_cli, and then create-rust-app my_project and I get this error with any permutation of options I choose. The error is always the same, at project.rs:274:10.

:thinking: that's really strange. Could you run:
create-rust-app --version

Yes, I am on version 9.0.0

What does the following return?
tree /Users/jarviskennedy/.cargo/registry/src/github.com-1ecc6299db9ec823/create-rust-app_cli-9.0.0/

(you can brew install tree if necessary)

I ended up finding and fixing a different bug -- please do share the output of
tree /Users/jarviskennedy/.cargo/registry/src/github.com-1ecc6299db9ec823/create-rust-app_cli-9.0.0/

when you get a chance. Again, you can brew install tree if necessary!

Update: It seems we've changed the order of git commands -- was this necessary for the CI setup @AnthonyMichaelTDM ? It's completely broken the normal flow (since we need to create an initialize the git directory before asking the user for their name/email). Hmm, continued to check and it shouldn't be necessary since we modify the global git config. Going to revert this move~

I changed it to set the git username/email before creating any files, the CI must not've caught issues that caused because of the issue brought up in #140 , which judging from the fact this error pops up now indicates that #140 may be fixed.
I'll start working on a bugfix to bring the order back to what it originally was right now

the specific issue is that part of checking for a git username/email is reading a git configuration in project_dir, which doesn't exist as it would be created in this code block
match std::fs::create_dir_all(&project_dir) {
    Ok(_) => {}
    Err(err) => logger::exit("std::fs::create_dir_all():", err),
}

the bug fix will move that block back before checking for username/email


add: content for challenge: match whitespace

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

Closed and Reopened this PR to attempt to resolve a specific Travis build failure.

The Travis CI build passed. What are you trying to resolve or what is the error?

Hi @iepur1lla,
There were about 3,100 PRs during Hacktoberfest which had build failures, but had nothing to do with the PR content.  It was a problem we had on our end.  The easiest way we found to resolve the issue was to close and reopen the PR.  Before the close/reopen the PR showed something like beloow instead of the message "All checks have passed" (like the PR now shows above).

Congrats @iepur1lla  on your first pull request (PR)! 🎉
Thank you for your contribution to the page! 👍
We're happy to accept these changes, and look forward to future contributions. 📝


Regenerate JavaKit Swift sources now that we have support for static fields

@jrosen081 FYI, this is the result of re-running the JavaKit generation now that your static field support has landed.

This is awesome! Is the plan to always commit these every time we add more support or in the future have the first step to using this be run the make (or Gradle when the Makefile gets removed)?

We should commit these every time we add more support, since we need them there to build the Java2Swift tool itself. It's also a nice validation step.


[BUG]

Project
MSIX SDK or Win7Msix
Describe the bug
When trying to sign an .MSIX with AzureSignTool, I was getting the following error:
The Publisher Identity in the AppxManifest.xml does not match the subject on the certificate for file D:\a\1\a\WPFMSIX.msix.
I copied the subject from the cert and set it to the Publisher in Package.appxmanifest, but MSIX build and package cannot parse it.
To Reproduce
Steps to reproduce the behavior:
Add the following to Package.appxmanifest

Add MSIX Build and package step to AzureDevops pipeline
When running that step, the following error occurs
D:\a\1\s\ProdVersion\bin\x64\Release\AppxManifest.xml : error APPX0501: Validation error. error C00CE169: App manifest validation error: The app manifest must be valid as per schema: Line 10, Column 26, Reason: 'SERIALNUMBER=0000000, C=US, ST=Massachusetts, L=MyTown, STREET=2 W Park Dr. #430, O=My Company Inc., CN=My Company Inc.' violates pattern constraint of '(CN|L|O|OU|E|C|S|STREET|T|G|I|SN|DC|SERIALNUMBER|Description|PostalCode|POBox|Phone|X21Address|dnQualifier|(OID.(0|[1-9][0-9])(.(0|[1-9][0-9]))+))=(([^,+="<>#;])+|".")(, ((CN|L|O|OU|E|C|S|STREET|T|G|I|SN|DC|SERIALNUMBER|Description|PostalCode|POBox|Phone|X21Address|dnQualifier|(OID.(0|[1-9][0-9])(.(0|[1-9][0-9]))+))=(([^,+="<>#;])+|".")))*'. The attribute 'Publisher' with value 'SERIALNUMBER=0000000, C=US, ST=Massachusetts, L=MyTown, STREET=2 W Park Dr. #430, O=My Company Inc., CN=My Company Inc.' failed to parse. [D:\a\1\s\ProdVersion\ProdVersion.wapproj]
Expected behavior
Should be able to use the certificate Subject as the Publisher as they need to match when signing with AzureSignTool
Screenshots
If applicable, add screenshots to help explain your problem.
Platform
Additional context
Add any other context about the problem here.

Hi @CraigMySeniorCenter
The string accepted for the publisher in the manifest has a couple of deviations from other string representations of certificate subjects. I believe it has to follow the same rules as the result of CertNameToStr
Looking at your subject I see two issues, the ST OID and the # in STREET:
SERIALNUMBER=0000000, C=US, ST=Massachusetts, L=MyTown, STREET=2 W Park Dr. # 430, O=My Company Inc., CN=My Company Inc.
Use S instead of ST for state, and quote the STREET field as it contains a #. Like this:
SERIALNUMBER=0000000, C=US, S=Massachusetts, L=MyTown, STREET="2 W Park Dr. #430", O=My Company Inc., CN=My Company Inc.
That should prevent the error when building and signing should also work.
If your certificate subject is not exactly the same as you used here, you may need to do other changes. E.g. quoting fields that include commas, or not quoting the street if it does not have a #.
Let me know if that helps.

Thank you for your suggestion.  After changing ST to S and putting quotes around the street address, the parsing no longer fails.
Unfortunately, Azure sign tool still gives the error: The Publisher Identity in the AppxManifest.xml does not match the subject on the certificate for file D:\a\1\a\WPFMSIX.msix
I opened up the msix file using MSIX Packaging Tool and verified that the only difference between the two is the ST instead of S and the quotes around the street address.  I will try opening up an issue with AzureSignTool.  Thanks again.

You could try to figure this out locally (not in the pipeline) using signtool.exe. There may be ways to do it with AzureSignTool but I'm not familiar with it.
You could download your .msix and your certificate (or create a self-signed certificate with the same subject just for diagnosing) then try signing the package with signtool.exe. If you set the environment variable APPXSIP_LOG=1 it should output more information, including what subject it expected from the certificate.
It would likely not help with the publisher/cert subject mismatch, but you could also try using the latest version of the MSIX Signing task from the MSIX Packaging Extension, which includes some support for integrating with the Azure Key Vault task. :)

Thank you for the additional troubleshooting tips
Very exciting that MSIX signing task has now has some support for Azure Key Vault.  How would I get that in AzureDevOps?  Do I need to wait until it's updated in the marketplace?  What task version is it in?

It should update automatically if you already have it installed. It is already in the marketplace, version 1.1.1.

I verified that I have version 1.1.1, but I don't see any options for Azure Keyvault under the Sign MSIX package task

Okay, you do have the option, but it's clearly not intuitive enough. Thank you for the feedback on that.
You can refer to the documentation on the signing task. If you have any feedback on that, you can submit it to https://github.com/MicrosoftDocs/msix-docs
You need to use the Azure Key Vault task to fetch the certificate and then pass the variable with the certificate to the signing task as a "String-encoded certificate".

Thanks for the information.  I think I'm close, but the signing isn't working.  I'm guessing that the format that my EVCert is coming out of KeyVault is not what the signing task is expecting.  Any idea what I'm doing wrong ?  I'm using the certificate name in Azure Key Vault as the Encoded Certificate File.  In my case the name is TibersoftEV and I'm using $(TibersoftEV) in the Sign MSIX package task.

Here is the output from the sign task:
2021-03-22T19:47:42.4534726Z ##[section]Starting: Sign MSIX package
2021-03-22T19:47:42.4740852Z ==============================================================================
2021-03-22T19:47:42.4741453Z Task         : MSIX package signing
2021-03-22T19:47:42.4741947Z Description  : Sign MSIX packages
2021-03-22T19:47:42.4742358Z Version      : 1.1.1
2021-03-22T19:47:42.4742809Z Author       : Microsoft Corporation
2021-03-22T19:47:42.4743288Z Help         : https://aka.ms/msix-cicd
2021-03-22T19:47:42.4743830Z ==============================================================================
2021-03-22T19:47:43.1290604Z [command]C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -NoLogo -NoProfile -NonInteractive -ExecutionPolicy Unrestricted "& 'D:\a_tasks\MsixSigning_501a9528-7fa4-4cb5-b8da-79ded62b74eb\1.1.1\ImportCert.ps1'" "***
2021-03-22T19:47:43.1292122Z ***
2021-03-22T19:47:43.1292885Z ***
2021-03-22T19:47:43.1293618Z ***
2021-03-22T19:47:43.1294361Z ***
2021-03-22T19:47:43.1295091Z ***
2021-03-22T19:47:43.1297028Z ***
2021-03-22T19:47:43.1298292Z ***
2021-03-22T19:47:43.1299518Z ***
2021-03-22T19:47:43.1300816Z ***
2021-03-22T19:47:43.1302169Z ***
2021-03-22T19:47:43.1303894Z ***
2021-03-22T19:47:43.1305324Z ***
2021-03-22T19:47:43.1307787Z ***
2021-03-22T19:47:43.1309000Z ***
2021-03-22T19:47:43.1310220Z ***
2021-03-22T19:47:43.1311564Z ***
2021-03-22T19:47:43.1312738Z ***
2021-03-22T19:47:43.1313875Z ***
2021-03-22T19:47:43.1315001Z ***
2021-03-22T19:47:43.1316571Z ***
2021-03-22T19:47:43.1317915Z ***
2021-03-22T19:47:43.1319127Z ***
2021-03-22T19:47:43.1320312Z ***
2021-03-22T19:47:43.1321486Z ***
2021-03-22T19:47:43.1323519Z ***
2021-03-22T19:47:43.1324554Z ***
2021-03-22T19:47:43.1325584Z ***
2021-03-22T19:47:43.1326946Z ***
2021-03-22T19:47:43.1328168Z ***
2021-03-22T19:47:43.1329330Z ***
2021-03-22T19:47:43.1330491Z ***
2021-03-22T19:47:43.1331660Z ***
2021-03-22T19:47:43.1332835Z ***
2021-03-22T19:47:43.1334005Z ***
2021-03-22T19:47:43.1335196Z ***
2021-03-22T19:47:43.1337418Z ***
2021-03-22T19:47:43.1353577Z ***
2021-03-22T19:47:43.1364098Z ***
2021-03-22T19:47:43.1366593Z ***
2021-03-22T19:47:43.1367753Z ***
2021-03-22T19:47:43.1368867Z ***
2021-03-22T19:47:43.1370008Z ***
2021-03-22T19:47:43.1371197Z ***
2021-03-22T19:47:43.1373358Z ***
2021-03-22T19:47:43.1374558Z ***
2021-03-22T19:47:43.1376047Z ***
2021-03-22T19:47:43.1377209Z ***
2021-03-22T19:47:43.1378391Z ***
2021-03-22T19:47:43.1379560Z ***
2021-03-22T19:47:43.1380724Z ***
2021-03-22T19:47:43.1382927Z ***
2021-03-22T19:47:43.1384128Z ***
2021-03-22T19:47:43.1385580Z ***
2021-03-22T19:47:43.1386741Z ***
2021-03-22T19:47:43.1387907Z ***
2021-03-22T19:47:43.1389069Z ***
2021-03-22T19:47:43.1390224Z ***
2021-03-22T19:47:43.1391339Z ***
2021-03-22T19:47:43.1393761Z ***
2021-03-22T19:47:43.1395072Z "
2021-03-22T19:47:43.7637895Z At line:28 char:5
2021-03-22T19:47:43.7639191Z + ***
2021-03-22T19:47:43.7640047Z +     ~
2021-03-22T19:47:43.7640983Z Missing expression after unary operator '--'.
2021-03-22T19:47:43.7643581Z At line:28 char:5
2021-03-22T19:47:43.7644685Z + ***
2021-03-22T19:47:43.7645813Z +     ~~~~
2021-03-22T19:47:43.7646815Z Unexpected token '-END' in expression or statement.
2021-03-22T19:47:43.7647949Z At line:28 char:10
2021-03-22T19:47:43.7648907Z + ***
2021-03-22T19:47:43.7649814Z +          ~~~~~~~
2021-03-22T19:47:43.7650798Z Unexpected token 'PRIVATE' in expression or statement.
2021-03-22T19:47:43.7651851Z At line:29 char:5
2021-03-22T19:47:43.7654022Z + ***
2021-03-22T19:47:43.7658100Z +     ~
2021-03-22T19:47:43.7659911Z Missing expression after unary operator '--'.
2021-03-22T19:47:43.7661069Z At line:29 char:5
2021-03-22T19:47:43.7663160Z + ***
2021-03-22T19:47:43.7666179Z +     ~~~~~~
2021-03-22T19:47:43.7668431Z Unexpected token '-BEGIN' in expression or statement.
2021-03-22T19:47:43.7669117Z At line:29 char:12
2021-03-22T19:47:43.7669716Z + ***
2021-03-22T19:47:43.7670262Z +            ~~~~~~~~~~~~~~~~
2021-03-22T19:47:43.7670903Z Unexpected token 'CERTIFICATE-----' in expression or statement.
2021-03-22T19:47:43.7674112Z At line:45 char:3
2021-03-22T19:47:43.7675433Z + ***
2021-03-22T19:47:43.7676073Z +   ~
2021-03-22T19:47:43.7676670Z You must provide a value expression following the '/' operator.
2021-03-22T19:47:43.7677330Z At line:45 char:3
2021-03-22T19:47:43.7677988Z + ***
2021-03-22T19:47:43.7678620Z +   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2021-03-22T19:47:43.7679477Z Unexpected token 'CT90wN/w51sDTAg8fbZjCFH29TUQIDAQABo4IBtTCCAbEwDgYDVR0PAQH/BAQD' in expression or statement.
2021-03-22T19:47:43.7680296Z At line:61 char:5
2021-03-22T19:47:43.7680878Z + ***
2021-03-22T19:47:43.7681361Z +     ~
2021-03-22T19:47:43.7681920Z Missing expression after unary operator '--'.
2021-03-22T19:47:43.7682523Z At line:61 char:5
2021-03-22T19:47:43.7683091Z + ***
2021-03-22T19:47:43.7683580Z +     ~~~~
2021-03-22T19:47:43.7684157Z Unexpected token '-END' in expression or statement.
2021-03-22T19:47:43.7685559Z Not all parse errors were reported.    Correct the reported errors and try again.
2021-03-22T19:47:44.4926866Z     + CategoryInfo          : ParserError: (:) [], ParentContainsErrorRecordException
2021-03-22T19:47:44.4927671Z     + FullyQualifiedErrorId : MissingExpressionAfterOperator
2021-03-22T19:47:44.4928316Z
2021-03-22T19:47:44.5071868Z ##[section]Finishing: Sign MSIX package

Your certificate seems to have PEM format (judging from the BEGIN CERTIFICATE and similar strings). Unfortunately the MSIX Package Signing task currently only supports PKCS12 (PFX) format so it fails. One option if you have control over the certificate you use is to use a PFX certificate.

Thank you for the clarification.  My certificate does not support PKCS12, so I'll have to figure out another way to sign.  I do appreciate all your help.

Thanks for the information. I think I'm close, but the signing isn't working. I'm guessing that the format that my EVCert is coming out of KeyVault is not what the signing task is expecting. Any idea what I'm doing wrong ? I'm using the certificate name in Azure Key Vault as the Encoded Certificate File. In my case the name is TibersoftEV and I'm using $(TibersoftEV) in the Sign MSIX package task.

You can't export HSM-backed private key material, so you are not allowed to export a base64 encoded PFX keypair bundle. EV CodeSigning certificates require HSM-backed key vaults, so I think this is the case.
MSIX signing task is only usable when you can and you accept the risk of moving unprotected private cert keys out of your keyvault
Proper way of signing via Azure Key Vault is to use AzureSignTool as documented in at https://learn.microsoft.com/en-us/windows/msix/desktop/cicd-keyvault but you should be aware that the Azure Portal does not show you the full correct certificate subject. You have to download the certificate and use some of the technics described here https://stackoverflow.com/questions/54868130/the-app-manifest-publisher-name-cn-digits-must-match-the-subject-name-of-the to get the actual subject string to use in the manifest publisher identity.


Easy (and correct) name capitalization, sub/turbo status

As you're using IRC to initially collect chat, you can actually enable IRCv3 tags for PRIVMSG and parse them for the correct name capitalization, and fetching the chatter's turbo and subscriber status for emulating chat just that little bit more.
First, send a CAP REQ :twitch.tv/tags to let the server know you understand the tags, then simply parse the new message, using the display-name, turbo and subscriber.
Before:
<EMAIL_ADDRESS>PRIVMSG #reninjakitteh :so far Kappa
After:
@color=;display-name=InaneCandor;emotes=25:7-11;subscriber=0;turbo=0;user-type=;user_type=<EMAIL_ADDRESS>PRIVMSG #reninjakitteh :so far Kappa
This is fully documented here and would be an awesome addition.
Thanks for making such a sweet and useful extension! Keep up the great work. :)

Thank's for pointing that out! First time I hear about Twitch's IRCv3. I will see what I can do.

Twitch did some changes related to this. Getting the EMOTESET using TWITCHCLIENT 3 does no longer work which forced me to use the new emote range supplied in the IRCv3 data (see https://github.com/pencil/rechat/commit/b17f8d4a0eb030f18066f98c72f579df202100d2). As a side effect, names should now be correctly capitalized (for messages as of today). Badges etc. will follow later.

Twitch did say they were planning on phasing out TWITCHCLIENT completely in favour of CAP, so that may be it.

Progress of chat badges implementation will be tracked in #20.


[webview_flutter] Physical keyboard: arrow keys not working

Steps to Reproduce

Execute flutter run on the code sample  (iOS Simulator or iPad with bluetooth keyboard)
Enter some text into the search field and press left arrow key

Expected results:
Cursor should move left
Actual results:
Cursor does not move

Code sample
import 'package:flutter/material.dart';
import 'package:webview_flutter/webview_flutter.dart';

void main() {
  runApp(const MyApp());
}

class MyApp extends StatelessWidget {
  const MyApp({Key? key}) : super(key: key);

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      home: WebView(
        initialUrl: 'https://duckduckgo.com/',
      ),
    );
  }
}

Logs

[✓] Flutter (Channel stable, 2.10.5, on macOS 12.3.1 21E258 darwin-x64, locale en-DE)
    • Flutter version 2.10.5 at /Users/***/dev/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 5464c5bac7 (7 days ago), 2022-04-18 09:55:37 -0700
    • Engine revision 57d3bac3dd
    • Dart version 2.16.2
    • DevTools version 2.9.2

[✓] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
    • Android SDK at /Users/devopsds/Library/Android/sdk
    • Platform android-31, build-tools 31.0.0
    • Java binary at: /Applications/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7281165)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 13.2.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • CocoaPods version 1.11.2

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2020.3)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7281165)

[✓] VS Code (version 1.66.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.38.1

[✓] Connected device (2 available)
    • iPad (9th generation) (mobile) • 35ED2CBC-915D-4737-93BD-13CC3F249CFD • ios            • com.apple.CoreSimulator.SimRuntime.iOS-15-2 (simulator)
    • Chrome (web)                   • chrome                               • web-javascript • Google Chrome 100.0.4896.127

[✓] HTTP Host Availability
    • All required HTTP hosts are available

• No issues found!

Hi @junglerobba, Thanks for filing the issue. I am able to reproduce the issue on stable and the master channel. Pressing arrow keys using the physical keyboard does not move the cursor. The issue is reproducible on both IOS and Android. Reproduces even with Hybrid composition on Android.

code sample
import 'dart:io';

import 'package:flutter/material.dart';
import 'package:webview_flutter/webview_flutter.dart';

void main() {
  runApp(const MyApp());
}

class MyApp extends StatefulWidget {
  const MyApp({Key? key}) : super(key: key);

  @override
  State<MyApp> createState() => _MyAppState();
}

class _MyAppState extends State<MyApp> {
  @override
  void initState() {
    super.initState();
    // Enable virtual display.
    if (Platform.isAndroid) WebView.platform = AndroidWebView();
  }

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      home: WebView(
        initialUrl: 'https://google.com/',
      ),
    );
  }
}

flutter doctor -v (mac)
[✓] Flutter (Channel stable, 2.10.5, on macOS 12.3 21E230 darwin-arm, locale en-IN)
    • Flutter version 2.10.5 at /Users/mahesh/Documents/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 5464c5bac7 (12 hours ago), 2022-04-18 09:55:37 -0700
    • Engine revision 57d3bac3dd
    • Dart version 2.16.2
    • DevTools version 2.9.2

[✓] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
    • Android SDK at /Users/mahesh/Library/Android/sdk
    • Platform android-32, build-tools 31.0.0
    • ANDROID_HOME = /Users/mahesh/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.11+0-b60-7772763)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 13.2.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • CocoaPods version 1.10.2

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2021.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.11+0-b60-7772763)

[✓] IntelliJ IDEA Community Edition (version 2021.2.1)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    • Flutter plugin version 61.2.4
    • Dart plugin version 212.5080.8

[✓] VS Code (version 1.65.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.39.20220405

[✓] Connected device (4 available)
    • Redmi K20 Pro (mobile) • <IP_ADDRESS>:55555                    • android-arm64  • Android 11 (API 30)
    • iPhone 12 Pro (mobile) • 535317A4-921C-488F-B234-C2CC6D4AE5A1 • ios            • com.apple.CoreSimulator.SimRuntime.iOS-14-5 (simulator)
    • macOS (desktop)        • macos                                • darwin-arm64   • macOS 12.3 21E230 darwin-arm
    • Chrome (web)           • chrome                               • web-javascript • Google Chrome 100.0.4896.88

[✓] HTTP Host Availability
    • All required HTTP hosts are available

• No issues found!

[✓] Flutter (Channel master, 2.13.0-0.0.pre.712, on macOS 12.3 21E230 darwin-arm, locale en-IN)
    • Flutter version 2.13.0-0.0.pre.712 at /Users/mahesh/Documents/flutter_master
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 8c22f5648a (77 minutes ago), 2022-04-25 05:34:07 -0400
    • Engine revision 10efa195bf
    • Dart version 2.18.0 (build 2.18.0-44.0.dev)
    • DevTools version 2.12.2

[✓] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
    • Android SDK at /Users/mahesh/Library/Android/sdk
    • Platform android-32, build-tools 31.0.0
    • ANDROID_HOME = /Users/mahesh/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.11+0-b60-7772763)
    • All Android licenses accepted.

[!] Xcode - develop for iOS and macOS (Xcode 13.2.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    ! CocoaPods 1.10.2 out of date (1.11.0 is recommended).
        CocoaPods is used to retrieve the iOS and macOS platform side's plugin code that
        responds to your plugin usage on the Dart side.
        Without CocoaPods, plugins will not work on iOS or macOS.
        For more info, see https://flutter.dev/platform-plugins
      To upgrade see https://guides.cocoapods.org/using/getting-started.html#installation for
      instructions.

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2021.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.11+0-b60-7772763)

[✓] IntelliJ IDEA Community Edition (version 2021.2.1)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    • Flutter plugin version 61.2.4
    • Dart plugin version 212.5080.8

[✓] VS Code (version 1.66.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.39.20220405

[✓] Connected device (3 available)
    • Redmi K20 Pro (mobile) • <IP_ADDRESS>:5533 • android-arm64  • Android 11 (API 30)
    • macOS (desktop)        • macos            • darwin-arm64   • macOS 12.3 21E230 darwin-arm
    • Chrome (web)           • chrome           • web-javascript • Google Chrome 100.0.4896.127

[✓] HTTP Host Availability
    • All required HTTP hosts are available

! Doctor found issues in 1 category.

cc @cyanglaz

On iOS:
Looks like there are some custom handling for the keyboard keys for iOS> 13.4 *, which never takes the super path, it leads to arrow keys being ignored on PlatformView. The arrow keys were actually handled in the flutter app for selecting elements. See below video where I'm hitting arrow keys and a highlight is moving between the Flutter Widgets.
See: https://github.com/flutter/engine/blame/main/shell/platform/darwin/ios/framework/Source/FlutterViewController.mm#L1318-L1326
https://user-images.githubusercontent.com/3756895/169106710-a9b96d2a-8d63-45d5-b441-818c5b33b1af.mov
cc @gspencergoog.fsaf

I create a quick prototype to demo a potential fix ( https://github.com/flutter/engine/pull/33458). I'm not familiar with how the keyboard keys are handled in other cases so this fix might missing corner cases. There should be a more elegant solution.
cc @hellohuanlin This could be related to the focus tree work you are current working on.

cc @dkwingsmt

@cyanglaz Thanks for the analysis! Although, the current code does take the super path in the callback, which is invoked if the framework decides not to handle key event. It seems that the framework did not dispatch the event to the WebView first but handled on its own. I'm reading WebView's source and see if I can find a better way.

@gspencergoog Have we ever tested keyboard on platform views? It seems to me that no platform views contain any focus at all. They can't be focused, and there are no ways to delegate key events to them.

No, I don't think we've ever done much with platform views and keyboard events.

@gspencergoog Have we ever tested keyboard on platform views? It seems to me that no platform views contain any focus at all. They can't be focused, and there are no ways to delegate key events to their native component.

Sounds like if PlatformView participants in the focus tree, this should be straightforward to wire up?
@hellohuanlin Is recently working on adding PlatformViews to the focus three. https://github.com/flutter/flutter/issues/34187.
Meanwhile, Android PlatformView already participants in the Focus Tree. So Android PlatformView is unblocked.

Kind of. There are three remaining points (which I'm playing with):

Check if it is possible to insert keyboard events to platform views.
Ideally store the original system event for insertion.
Change the framework focus API to allow async keyboard handling.

I saw @hellohuanlin 's work (https://github.com/flutter/engine/pull/33093 if I didn't misunderstand). It seems that they chose to operate specially for text input. If that's required we'll also need to figure out a way to incorporate text input and keyboard.

@dkwingsmt oh that engine PR is not complete change yet. A missing part is to detect platform view focus and send channel message to the framework.

Yeah I'm aware. I'm just curious what it takes on the engine side to make it work. Let me know your progress!

@tilemoon can you update to the latest version and see if it's fixed?

we are using v3.2 but still not working.

@hellohuanlin we are using v3.2 but still not working.

@tilemoon Gotcha. Looks like this issue turned out not related to my other fix related to platform view focus then.

I managed to get it working! https://github.com/flutter/flutter/issues/74044#issuecomment-948590848

Any update on Android?

any updates?

I managed to get it working! #74044 (comment)

From your workaround, it's simply overriding FlutterViewController's pressesBegan/Changed/Ended calls and removes the FlutterUIPressProxy part.

- (void)pressesBegan:(NSSet<UIPress*>*)presses
           withEvent:(UIPressesEvent*)event API_AVAILABLE(ios(9.0)) {
  if (@available(iOS 13.4, *)) {
    for (UIPress* press in presses) {
      [self handlePressEvent:[[[FlutterUIPressProxy alloc] initWithPress:press
                                                               withEvent:event] autorelease]
                  nextAction:^() {
                    [super pressesBegan:[NSSet setWithObject:press] withEvent:event];
                  }];
    }
  } else {
    [super pressesBegan:presses withEvent:event];
  }
}

I'm not familiar with this part, but from git history, @gspencergoog probably has some context.

We managed to come up with a work-around that works on both Android (including Chromebook) and iOS. The solution does not require editing platform-specific code (like was done in https://github.com/flutter/flutter/issues/74044#issuecomment-948590848).
Issue and solution
Apparently the arrow keys from the hardware keyboard get "eaten" by Flutter and never reach the included webview. By listening to the arrow keys and instructing Flutter to return them to the platform the arrow keys function again. The work-around does this by returning KeyEventResult.skipRemainingHandlers for the arrow keys. From the KeyEventResult.skipRemainingHandlers docs:

It will be returned to the platform embedding to be propagated to text fields and non-Flutter key event handlers on the platform.

Work-around code
We've created a new repository containing an updated code sample (the code in the first comment used on old version of webview_flutter) to demonstrate the original issue. After that, we have updated the repository with our work-around. The relevant file containing the work-around is lib/main.dart.
Remarks
Please note that on Android and Chromebook it is possible in input fields to move the cursor beyond the last character. When moving one character back (using the left arrow key), the entire text becomes selected. This behaviour is different to what happens when you choose Web as a build target and open the app in (for example) Chrome.

This solution (https://github.com/flutter/flutter/issues/102505#issuecomment-1653216824) will only work after double clicking on any of the arrows. Is there an alternative solution ?

This solution (#102505 (comment)) will only work after double clicking on any of the arrows.

In our app no double clicking is required; it works as expected.

I tested it on an emulator and a physical device, the behavior is the same. At the first start of the program, after clicking on the down arrow, only 1 ArrowDown RawKeyUpEvent event is generated, without RawKeyDownEvent. After that, everything is fine.

I tested it on an emulator and a physical device, the behavior is the same. At the first start of the program, after clicking on the down arrow, only 1 ArrowDown RawKeyUpEvent event is generated, without RawKeyDownEvent. After that, everything is fine.

I've just retested this and you're right. The very first event is missed unfortunately. We currently don't know a way how to work-around this.

Any updates on this please?

Same issue here.

Might be https://github.com/flutter/flutter/issues/147844 is also affected by this issue. My issue is that when I press enter or space and another "visual focused" widgets consume the space and enter pressed on a physical (bluetooth) keyboard. I'll check if the workaround mentioned here could fix my issue too.


Picking the right similarity_space_type name to create an inner product index

Hi ,
I am trying to create an ANN index that uses inner product as the similarity function. As far as I can see, the support for this has been implemented (#144). However, I have not found a value for knn.space_type that is accepted. The documentation here doesn't seem to list inner product.
For whatever value of knn.space_type I give, I am constantly getting
RequestError(400, 'invalid_parameter_exception', 'Unsupported space type: inner_product')

Any help would be greatly appreciated!

Hi @brandenchan
Inner product is not available in ODFE 1.13, which was our last ODFE release: https://github.com/opendistro-for-elasticsearch/k-NN/blob/opendistro-1.13/src/main/java/com/amazon/opendistroforelasticsearch/knn/index/SpaceTypes.java. We added it to main branch after ODFE 1.13, but then with the OpenSearch fork, it was decided there would be no more ODFE releases.
It is available in OpenSearch rc1 and will be available in OpenSearch GA. Sorry for the confusion.

Great thanks!


IndexResponseBase.SelectivityEstimate should be a double instead of an int

IndexResponseBase.SelectivityEstimate currently has a type of int whereas the server has it defined as a double.
It causes some errors when the SelectivityEstimate happens to be greater than 0 but less than 1.

Thank you @mark-comeau 👍 I opened a pull request to fix that.


Missing documentation in lib.d.ts

TypeScript Version:  2.2.1
While a lot of the available interfaces and functions have documentation in lib.d.ts, there is still a lot of documentation missing. I've noticed that most definitions are available and elaborately documented on http://devdocs.io/, which contains data scraped from the Mozilla MDN Web API.
I always find it rather handy to have documentation readily listed in intellisense, especially when I'm working with unfamiliar classes or interfaces.
Are there any rules/guidelines regarding documentation in lib.d.ts? How is it determined what gets documented and what doesn't? Is there an official source required?
I've looked up a few of the undocumented interfaces and I think it should be possible to match the documentation provided by devdocs.io for most cases where the current documentation is missing. I guess it should also be possible to verify if there aren't any missing properties in the lib.d.ts and use the browser compatibility mentioned in #3250 when the exact syntax is finalized.

Are there any rules/guidelines regarding documentation in lib.d.ts? How is it determined what gets documented and what doesn't? Is there an official source required?

The documented APIs are documented by hand. you can find the soruces for the JS built-in objects in https://github.com/Microsoft/TypeScript/tree/master/src/lib, and for the DOM APIs in https://github.com/Microsoft/TSJS-lib-generator/blob/master/inputfiles/comments.json.
If you want to contribute new docs, feel free to send us a PR.

I've looked up a few of the undocumented interfaces and I think it should be possible to match the documentation provided by devdocs.io for most cases where the current documentation is missing.

Let me get back to you on this. I need to ask our lawyers if there is any issue with using docs from an external source like devdocs.io

We pull in MDN docs now


2.25

What is guaranteed in an Azure Service Level Agreement (SLA)?
A. uptime
B. feature availability
C. bandwidth
D. performance

B


Update changelog for next release

Description
Update changelog in preparation for the next release

Hah, beat me to it! Good work sir!


For 'ashav-test-stgorg2' github org. newly added repos are stopped getting listed on EasyCLA UI

Steps:

For 'ashav-test-stgorg2' github org. newly added repos are stopped getting listed on EasyCLA UI. This Github Org. is added for project group 'Stage Foundation'.
This is discussed with @wanyaland and @rinkeshbhutwala

Expected Result: All newly added repos should be listed on EasyCLA UI.

@wanyaland @dealako I have verified the logs and also check the DB as well looks like there is one repo which is https://github.com/ashav-test-stgorg2/stg2-repo4 added twice on repo table with different projectSFID and also internally call list GitHub repo API using installation ID it returns only 4 repo instead of 6.

Closing issue due to inactivity.


Update TTGTagCollectionView.m

修复点击时 隐藏的tag响应问题

The right to Left layout direction is not working in the current latest version for the Arabic language.
Can you please help me with this to achieve the Right to Left Layout Direction for the Horizontal Scrollable(Collectionview) with two lines?


Cartitem

Assignee Tasks

[ ] added unit tests (or none needed)
[ ] written relevant docs (or none needed)
[ ] referenced any relevant issues (or none exist)

Guidelines
Please add a description of this Pull Request's motivation, scope, outstanding issues or potential alternatives, reasoning behind the current solution, and any other relevant information for posterity.

Your PR Notes Here

This line was adding an OrderId FK to the CartItem model, I think it should have been OrderItem instead of CartItem


NODE_ENV=production npm run build && rm -rf dist is unstable

Given the following script, I cannot run build && rm -rf dist && build
Per @patrick-steele-idem , it has to do with .cache directory and speeding up production builds.  (as a separate issue: invisible / hidden files are probably bad form! ... maybe ./dist-cache instead?)
Assuming marko create ... is the preferred and documented way of onboarding new people to using marko, I propose the following:

add a command npm run clean or npm run build-clean ... as-is, it's really nasty for someone new to marko to run npm run build && rm -rf dist && npm run build and assume marko is buggy / broken because no files are generated / built

default npm run build to avoid/skip/clear the cache directory or make it clear that marko-starter build --use-cache / --skip-cache / --cache=./.cache has caching going on.

From talking with Patrick it feels like the builds are expected to be done on prod machines, and only once.  For my general development practices, I often run "prod" builds on my local machine to verify file sizes, make a final test run before building/pushing, etc.
$ cat repro.sh
rm -rf ./try-to-repro
marko create try-to-repro
cd try-to-repro
yarn install > /dev/null
NODE_ENV=production npm run build > /dev/null
find ./dist/ -type f | xargs -n1 -I{} bash -c 'echo -n "{} " ; gzip -c {} | wc -c'
rm -rf ./dist
perl -p -i -e 's/Click.me/Do it/g' ./components/click-count/index.marko
perl -p -i -e 's/count:0/count:9/g' ./components/click-count/index.marko
NODE_ENV=production npm run build > /dev/null 2> /dev/null
find ./dist/ -type f | xargs -n1 -I{} bash -c 'echo -n "{} " ; gzip -c {} | wc -c'

I noticed the same thing. Removing dist/ folder and rebuilding would not rebundle the js files and assets. To mitigate this .cache folder needs to be removed as well.

The new @marko/serve command which is built on top of webpack and is also the default when using @marko/create no longer has these issues.


We either navigate top level or have old version of the navigated frame

I'm trying to get core-js usage statistics in the wild and check the top 10000 sites by puppeteer (1 browser, pages by the number of CPUs), script. In most cases, after some thousands of checked sites, I have this error and I can't catch it. Looks like an equal of #3309.
/***/core-js/node_modules/puppeteer/lib/cjs/puppeteer/common/assert.js:26
        throw new Error(message);
              ^

Error: We either navigate top level or have old version of the navigated frame
    at Object.assert (/***/core-js/node_modules/puppeteer/lib/cjs/puppeteer/common/assert.js:26:15)
    at FrameManager._onFrameNavigated (/***/core-js/node_modules/puppeteer/lib/cjs/puppeteer/common/FrameManager.js:196:21)
    at /***/core-js/node_modules/puppeteer/lib/cjs/puppeteer/common/FrameManager.js:57:64
    at /***/core-js/node_modules/puppeteer/lib/cjs/vendor/mitt/src/index.js:51:62
    at Array.map (<anonymous>)
    at Object.emit (/***/core-js/node_modules/puppeteer/lib/cjs/vendor/mitt/src/index.js:51:43)
    at CDPSession.emit (/***/core-js/node_modules/puppeteer/lib/cjs/puppeteer/common/EventEmitter.js:72:22)
    at CDPSession._onMessage (/***/core-js/node_modules/puppeteer/lib/cjs/puppeteer/common/Connection.js:225:18)
    at Connection._onMessage (/***/core-js/node_modules/puppeteer/lib/cjs/puppeteer/common/Connection.js:101:25)
    at WebSocket.<anonymous> (/***/core-js/node_modules/puppeteer/lib/cjs/puppeteer/node/NodeWebSocketTransport.js:13:32)

Steps to reproduce
Tell us about your environment:

Puppeteer version: 8.0.0
Platform / OS version: M1, MacOS 11.2.3
Node.js version: 15.12

What steps will reproduce the problem?

Copy script by the link above
Install dependencies
Run with param -l=10000

@zloirock ,I am also getting the same issue as above. Please let me know how this issue is resolved

@Saranya-v60 I solved it for myself by a restart of a browser each some pages.

@zloirock ,Thanks for the reply.
My scenario is ,I have 35 e2e test files and each file has approx. 2-7 test cases. for each test file, I am opening the new browser and closing after test cases execution. In pipeline some of the test files itself not running and giving error as "We either navigate top level or have old version of the navigated frame".
If I want to do the restart of browser means for each test case I need to open new browser instead of each test file?

Is there any alternative solution for this? in my scenario, i can not restart my browser/puppeteer

Also getting this error with puppeteer version 13.1.1
Tried downgrading to 13.0.1, didn't work

Same error on puppeteer-core version 13.1.3

I have the same error sporadically popping on different pages, version 13.4.1.

Did anyone find a solution to this?

My best solution was to create a wrapper, run the script invoking Puppeteer as a subproccess, and restart it when this error was encountered.  It is possible to catch and recognize this error on the uncaughtExceptionMonitor signal, but the process cannot recover so I had it send a signal to the parent process.  This does require setting up the capacity to save and resume state, which you might desire anyways but is extra work.
I have since moved onto working with a single page application where I don't encounter this error.

Wrapping as a subprocess is the only way I can think of solving it - at the moment I'm only using a single page just grabbing pages()[0], how would that make any difference?

A single page application doesn't involve using traditional links to traverse content, instead relying on JavaScript fetches of data and transforming the DOM (think Google Docs or Slack).  The fact that this error doesn't occur while working with one implies that it has something to do with the browser's handling of hyperlinks.  I don't have much information beyond that.

@Saranya-v60 I solved it for myself by a restart of a browser each some pages.

I just found that without restarting the browser but just creating a new page before jumping into that page will work.

Anyone has solution for this?

Anyone has solution for this?

you can try the solution, described there https://github.com/apify/apify-js/pull/1348
(launch with --disable-site-isolation-trials arg)
it fixed the same issue for me

Bumping this as I am also getting this error. Does anyone know exactly what brings on the error? I know very little about the error message itself

In my case, the error was resolved by using "load" and providing a timeout of 3 seconds:
await page.goto(<url>, { waitUntil: ["load", "domcontentloaded", "networkidle2"], timeout: 120000 });                 await page.waitForTimeout(3000);

How can I remove it or not to stop the process? try-catch doesn't help

@ggorlen are you still able to reproduce this issue? Latest versions do not have that assertion anymore and I was not able to reproduce it using the script you provided.

Alright, thanks, I am going to mark this one as closed then. Please file a new issue if there is a reproducible example for a similar issue. It does sound like it was a race condition. There is a similarly sounding issue with a newer versions https://github.com/puppeteer/puppeteer/issues/11246 but I have troubles reproducing it.


Format Not Validated

Given this schema.json:
{
    "type": "string",
    "format": "date-time"
}

And this bad.json:
"I am not a date-time"

jv does not complain about the invalid date-time:
$ ./cmd/jv/jv schema.json bad.json
$ echo $?
0

Shouldn't it?

format is treated as annotation in draft-2019 onwards. it needs to be explicitly enabled by compiler.AssertFormat = true.
I just need to add a flag to jv to enable this


Some refactorings

Hello, thank you for taking the time to contribute to this project! I really appreciate it.
Apologies for the response delay, it has been a busy few days for me. This pull request looks great, a lot of minor touch ups that this library needs. Unfortunately their is no way to test the ForgeSVC handler changes, but it looks good just by eyeballing it. We will be sure to keep these changes  in mind once the handlers that tap into the official curse forge API is written.
Thanks again!


The style of icon images is broken when using browser translation

Because browsers translate alt texts.
Turning on the translation feature breaks the layout. When I first came to this site, it was quite confusing because translation was turned on from the beginning.
I would suggest using class instead of attribute selector.

noodle dome


How to use the advanced mode of Pages Functions

https://developers.cloudflare.com/pages/platform/functions/advanced-mode/
Does vite-plugin-cloudflare-functions support this mode? And could you share an example?

It does not support it now.
When running the dev server, the only thing that this plugin will do is to automatically start a wrangler pages function dev server under the hood and "combine" it together with the original Vite dev server. The wrangler pages function proxy the original Vite dev server when handle request, i.e. GET /index.html -> wrangler dev server -> Vite dev server -> browser, POST /some-api-endpoints -> wrangler dev server -> browser.
But, if you use the advanced mode, the _worker.js will handle all the request including serving static assets. While development has no static assets.
// Example code from the cf pages document

export default {
  async fetch(request, env) {
    const url = new URL(request.url);
    if (url.pathname.startsWith('/api/')) {
      // TODO: Add your custom /api/* logic here.
      return new Response('Ok');
    }
    // Otherwise, serve the static assets.
    // Without this, the Worker will error and no assets will be served.
    // NOTE: When running dev server, I think it has no assets here, maybe we can proxy the html/js/css request and hmr websocket connection to the Vite dev server here?
    return env.ASSETS.fetch(request);
  },
}

If we want to support advanced mode, I think we can write a static assets handler function like this:
// _worker.js

import { handleStaticAssets } from 'vite-plugin-cloudflare-functions/worker';

export default {
  async fetch(request, env) {
    const url = new URL(request.url);
    if (url.pathname.startsWith('/api/')) {
      // TODO: Add your custom /api/* logic here.
      return new Response('Ok');
    }
    // Otherwise, serve the static assets.
    // Without this, the Worker will error and no assets will be served.
    return handleStaticAssets(request, env);
  },
}

// https://github.com/yjl9903/vite-plugin-cloudflare-functions/blob/main/packages/vite-plugin-cloudflare-functions/src/worker/index.ts

// ...

export function handleStaticAssets(request, env) {
  if (it is under dev environment) {
    // dev
    const url = new URL(request.url);
    url.host = <get the host of the dev server>;
    return fetch(url, request);
  } else {
    // prod
    return env.ASSETS.fetch(request);
  }
}

There is two things to be checked:

How to pass the env / host / ... configuration to the above handler, maybe use globalThis.__pages__ = { ... }?
Does the above fetch support websocket used for Vite HMR?

PR welcome :)


Basic support of partial  paths.

Most of this PR is pulled from #4539 which is outdated and has a lot of merge conflicts.
The implementation is simple: the matchPath method will infer that if options.path does not have a leading slash, then it is relative to the parent w/ the parent's matched url used as the base.
I'm hoping that this continues the conversation started in #5127 so that we can move closer to having a solution.
In my opinion, Route paths should not support ./ or ../. As for linking, relative links are already working as demonstrated by this comment.
Relative route paths should remain simple and straightforward and the logic around relative linking should be delegated to history as much as possible possible.

Any idea why CI is not passing? All tests are passing locally for me.

I am curious, why not to reuse existing implementation resolve-pathname? I am using that one and works perfectly fine.

@FredyC I think that may be a good candidate for making link resolution consistent across react-router-dom and react-router-native, however I don't feel that route definitions should behave the same behavior as url resolutions for links.
Consider the following:
<Route path="/some/absolute" component={ C1 }>
  <Route path="relative" component={ C2 } />
</Route>

Intuitively, we would consider C1 the parent route of C2. If we were to use the standard url resolution behavior for links, then C2 would essentially be overwriting the path declared for C1.
This means that for the pathname /some/relative, we would be rendering route [C1, C2]. The issue there is that the C1 route path would no longer be matching, meaning that none of its children would be rendered.
Going with link url resolution as the standard for route path declarations is not only unintuitive, but it would require significant changes to how routes are matched and rendered.

I have these test failing locally. Most probably, the deal is in npm dep versions - I've installed them from the scratch, while you probably have some heritage.

Resolved conflicts and added improvements made by @karevn in #6307.

I know this discussion is going on for a long time and I also see the reason why a nested route starting with ../ is a bad idea, but I think a sub-route starting with ./ makes things more clear (IMHO). And to prevent the use of ../ at the start we should throw an error, that this behaviour is not supported (maybe add a reason, but need not).
Why?
Well, in the <Route /> component for the path prop it does not work with a starting ../, but for <Link  /> and the to prop it makes sense. So why should we support ../ but not ./?

Why does this PR still have conflicts?
Just let me know if you want my help.

I have since abandoned react-router and have written my own router solution; I have no plans to move forward with this PR, but I will leave it open for reference and up to the maintainers to close.
I agree with what @MeiKatz has proposed regarding the relative path syntax and recommend following and/or building upon #6618 (his PR includes and builds upon my changes).

No worries. Thanks for opening it up @lukaswelinder!


Remove "Forums (coming soon)" from Community page

Fix #645

 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.Jeng seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

@nopcoder Will this get merged?


[editor] Add bindkey-all function to show all bound keys

Function which allows you to see all the bound keys for all of
the different keymaps. It does accept arguments and passes them
through to bindkey -m "$keymap" so you could set a shortcut to
all keymaps as well if you wished.
Makes it much easier to see and grep what keys are bound to each of
the different keymaps.

I was thinking of having bindkey -q be quiet and not print out the headings? Bindkey has no -q option. Or would that be too much?
function bindkey-all {
  local keymap=''
  local quiet=''
  if [[ "$1" == '-q' ]]; then quiet=1; shift; fi
  for keymap in $(bindkey -l); do
    [[ -z "$quiet" ]] && printf "#### %s\n" "${keymap}" 1>&2
    bindkey -M "${keymap}" "$@"
  done
}

It has been updated to only print the keymap headings if there are no arguments.


Not able to change API-Key via Docker

When I try to set my api key with this command
docker run -d -p 8080:8080 -p 8443:8443 -p 443:443 -p 8080:8080 -e LLM_API_KEY='my-Key' infosecb/galah:latest
I encounter this problem
Error generating OpenAI response: error, status code: 401, message: Incorrect API key provided: ks-7xvA2*******MPLE.
I know for a fact that is not my API-Key shown there because it does not start with ks.

Ah yes, because I recently pushed an update to the repo, but haven't updated the Docker image yet. Use API_KEY (instead of LLM_API_KEY) if you want to use the infosecb/galah image (old version), or build a new Docker image.

Updated the README.


Add TokenAuthenticator setup

Why
Most of the apps use API requests and have a refresh token mechanism to request new access tokens in case they expire. We don't have the setup for the initial TokenAuthenticator yet, so we should add it to our templates.
The initial Authenticator needs to contain:

max attempt/retry logic (normally set to 3).
make use of synchronized(this) {} when executing the refresh token and rebuild the request to handle multiple authenticator calls at a time.
try/catch wrapping to catch errors during token refreshing. The default action in case an error has occurred.

Who Benefits?
Developers who use this template to initialize their project with network requests.
I think this is essential because most of apps have API request and have refresh token mechanism. Having a standard setup would help us a lot in development and reduce mistakes.
Example of implementation: https://github.com/nimblehq/toyota-wallet-android/blob/main/data/src/main/java/co/omise/gcpf/service/authenticator/ApplicationRequestAuthenticator.kt

@ryan-conway @nimblehq/chapter-android According to some edge cases we have faced and resolved in the JFC and its brand projects regarding the refresh-token mechanism, this task should be in a higher priority to prepare the stable implementation for the following projects.


New version: TeamViewer.TeamViewer version 15.51.6

[ ] Have you signed the Contributor License Agreement?
[ ] Have you checked that there aren't other open pull requests for the same manifest update/change?
[ ] This PR only modifies one (1) manifest
[ ] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[ ] Does your manifest conform to the 1.6 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

@stephengillie are you able to approve this one please?


The Fantasy Trip: new features: blank saves from 2-8d6, pronoun tooltip, new image

Submission Checklist
Required

[x] The pull request title clearly contains the name of the sheet I am editing.
[x] The pull request title clearly states the type of change I am submitting (New Sheet/New Feature/Bugfix/etc.).
[x] The pull request makes changes to files in only one sub-folder.
[x] The pull request does not contain changes to any json files in the translations folder (translation.json is permitted)

New Sheet Details

The name of this game is: <   >  (i.e. Dungeons & Dragons 5th Edition, The Dresden Files RPG)

The publisher of this game is: <   > (i.e. Wizards of the Coast, Evil Hat)

The name of this game system/family is: <   > (i.e. Dungeons & Dragons, FATE)

[ ] I have followed the Character Sheets Standards when building this sheet.

[ ] This sheet has been made on behalf of, or by, the game's publisher.
[ ] This game is not a traditionally published game, but a copy of the game rules can be purchased/downloaded/found at: <   >
[ ] This sheet is for an unofficial fan game, modification to an existing game, or a homebrew system.

Changes / Description

Add blank saving-throws/checks from 2d6 through 8d6, to provide the critical tables.
Gender tooltip says "or pronouns", there's room in the input.

Character Sheet Info Roll20 Internal Use only.


Solid scope check

Right now signaldb-plugin-solid does not support reactive scope checking and automatic cleanup. Would Solid's getOwner function solve this? getOwner returns the current reactive scope or null if outside one.
The plugin could be changed to this:
import { createReactivityAdapter } from 'signaldb'
import { createSignal, getOwner,  onCleanup } from 'solid-js'

const solidReactivityAdapter = createReactivityAdapter({
  create: () => {
    const [depend, rerun] = createSignal(undefined, { equals: false })
    return {
      depend: () => {
        depend()
      },
      notify: () => {
        rerun()
      },
    }
  },
  isInScope: () => !!getOwner(),
  onDispose: (callback) => {
    onCleanup(callback)
  },
})

export default solidReactivityAdapter

I've been playing with the new SyncManager with solid and noticed a ton of warnings from solid about onCleanup not getting called. This change seems to fix those warnings.
There is one possible issue with this. The solid docs mention:

Note that the owning reactive scope isn't necessarily tracking. For example, untrack turns off tracking for the duration of a function (without creating a new reactive scope), as do components created via JSX (<Component ...>).

Is there a way to test if getOwner would actually fix this issue?

Thanks, that sound like a solution! 🙂 I think I've overseen this in the docs.

There is one possible issue with this. The solid docs mention:

Note that the owning reactive scope isn't necessarily tracking. For example, untrack turns off tracking for the duration of a function (without creating a new reactive scope), as do components created via JSX (<Component ...>).

I don't think that this is an issue in our case as we only scope if a scope is present and it doesn't make difference which scope exactly it is.

Is there a way to test if getOwner would actually fix this issue?

You could use you code as a reactivity adapter to test if everything works:
const collection  = new Collection({
  reactivity: createReactivityAdapter({
    create: () => {
      const [depend, rerun] = createSignal(undefined, { equals: false })
      return {
        depend: () => {
          depend()
        },
        notify: () => {
          rerun()
        },
      }
    },
    isInScope: () => !!getOwner(),
    onDispose: (callback) => {
      onCleanup(callback)
    },
  }),
})

It would be awesome if you could create a PR after your tests were successful 🙂


docs: link to new intro guide

We should also put the video+guide on doc.cognitedata.com

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Bug:Bad rendering in DuckDuckGo browser

Characters overlap in rendering on platform described below, as if all the character widths are too small.
Steps to Reproduce
Load https://mathjax.github.io/MathJax-demos-web/tex-chtml.html on the platform specified below.
This is a bug because the rendered math is illegible.
Technical details

Client OS: Android 11
Browser: DuckDuckGo 5.94.3 on
Galaxy Tab S5e SM-T727A
The same problem occurs within ObsidianApp 1.0.4 on the same tablet.
Everything works fine in Android 9/DuckDuckGo  5.7.2 on my phone.

I'm not able to reproduce the issue in DuckDuckGo 5.95.0 on Android 11 on a Samsung A32 phone.  I don't have access to a Galaxy Tab to try it there.  Can you try updating DuckDuckGo and see if that helps?


QueryCategory  - is it still internal use only?

Dear Team,
I think the description of QueryCategory property is not correct anymore. Since on yammer group it is stated it can be used. Also in other documentation page it is said:
With the SmartLists functionality that was added, we also made some underlying platform changes to make it possible to create SmartLists based on queries. With this functionality, you can now create your own lists through extensions. The created list can then be assigned to an entity by setting the QueryCategory property.
By being able to create a new list page based on a query, you can get the data you want on one list even if all the data isn’t in a single table in the database.
https://docs.microsoft.com/en-us/business-applications-release-notes/April19/dynamics365-business-central/enhancements-intelligent-cloud

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

ID: ecacafbf-bba5-f3e4-8da9-f408e7a17074
Version Independent ID: 77b1226e-488c-09c6-38ad-44fc2bdbb9ca
Content: QueryCategory Property - Business Central
Content Source: dev-itpro/developer/properties/devenv-querycategory-property.md
Service: dynamics365-business-central
GitHub Login: @blrobl
Microsoft Alias: t-blrobl

Thanks for this. Yes, the topic needs an update. We will provide one with the next doc refresh.

Hello, thanks for the feedback. The topic has been updated here: https://docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/properties/devenv-querycategory-property.


[release-2.8] ACM-9495 translation scripts

https://issues.redhat.com/browse/ACM-9495
Backport of https://github.com/stolostron/console/pull/3133 to set up translation scripts.

/cc @robdolares


conda-forge recipe with paraview-feedstock

First, I should get a conda-forge recipe up for PVGeo to avoid pip installation issues.
Then! I should figure out how to require https://github.com/conda-forge/paraview-feedstock as a dependency in that recipe and properly set the environment variable PV_PLUGIN_PATH in that conda environment so that users don't have to go through a painstaking installation process.
AND THEN, I should set up a CI build/testing process that installs ParaView from the conda feedstock and tests all the PVGeoPlugins in pvpython

Requires https://github.com/conda-forge/paraview-feedstock/issues/83

ParaView support has been dropped


Restructuring the code (Refactoring)

I love the library! I did an interesting demo that got quite some positive feedback. Will publish that.
The demo showed the performance problems and also that a 1 line change can make the library 22% faster. Now I look for more performance gains. However, there is one problem with the library that hinders the readability.
Rasterific does 4 different things:

Low level rendering
High level rendering API
Helper functions (e.g., "rectangle")
Coon (Gradient Mesh)

For me this is bad for readability and also from the standpoint of separation of concerns. I am probably going to rewrite a version of the library for myself to change that.
Minor things are copy/past code or code redundancy but this is a small detail.

Where can I see this 22% improvement? For the rest, I don't know where you're going with it, so I'll refrain on commenting.

Hi, I'd like to see the code for the performance improvement, especially if it's just one line :].
I'm aware of a low hanging fruit on optimization for the 64 bit version of GHC, as some types used during rendering are tuned for 32bits, there is some quick win to do on memory usage.
For the "readability" bit, I don't know where you're going to, so I'll refrain to comment.

Hi,
Yes, I will give you the one line. But need to check again if it improves only my code or all code. Did you see the video of my snowflake benchmark? The video on Youtube?
If you give me a bit of feedback, I can make the speed improvements quicker.
type Container a = DList a
One question is, why did you use dynamic lists? Was it more because it was easy? Or is it good to have lazy evaluation for speed? Would a Vector be better for speed?
After that I also have another question on how to improve the edge sorting in sortEdgeSamples.

The one line improvement is truing on strict evaluation on the modulate that allocates most; for instance, -X Strict on Rasterize.hs can help. But as you see, this is just a trick to know that there is some problem with perhaps lazy evaluation. This is not a fix.
The next big step is where to do the changes so that the edges are sorted in parallel. Where would you do that change?


hca roadmap - post meeting questions

After our HCA Roadmap 2024  we came up with questions to specific people before we try to prioratize our tasks and goals.

Tony: In core milestone 1 which costs are we aiming to reduce? Do we have a target?
John: Have we reached a decision on how to lower egress costs for the Data Portal? does it include download from ENA? bonus --> will it cover lattice datasets as well
John: Is there a case where we want to make metadata MA even if contributors have consent to release it as OA? Is there a minimum standard for metadata protection in HCA policies?
John/Lucia: What is the expectation around tier 2 and the atlas object? Will the atlas include tier 2? Would that make the atlas MA?
Jason: Is there any published cxg dataset with the full tier 1 metadata?
Jason + Lucia: Is there any network close to publicate T1 metadata?
Jason + Lucia: If datasets wrangled by lattice have been selected and need Tier 2 addition, how is it going to be handled? Does the lattice team have/ can have DPA?
Bobbie: Can we have a meeting to discuss what the partial updates are going to address?
Ida/Arsenios: How many projects from w1 & w2 are in a complete status? If a lot of them are we need a solution for updating files

About Q9:
There are 73 projects in complete state. Out of those:

15 project in wave1 or wave2
17 projects in wave1 or wave2 or wave3
How to update those?

Q8: working on the partial updates is not Bobbie's priority now but she shared the notes from the last discussion that was held around changing the importer's behaviour and the scenarios are broken down in this document
in theory scenario 2 should cover the case where file descriptors are presnt but the data files themselves aren't

@gabsie can you review the questions?

Here's an update for those questions as of today.

Tony: In core milestone 1 which costs are we aiming to reduce? Do we have a target?
Not to worry until 2025 Q1-Q2

John: Have we reached a decision on how to lower egress costs for the Data Portal? does it include download from ENA? bonus --> will it cover lattice datasets as well
Not to worry until 2025 Q1-Q2

John: Is there a case where we want to make metadata MA even if contributors have consent to release it as OA? Is there a minimum standard for metadata protection in HCA policies?

John/Lucia: What is the expectation around tier 2 and the atlas object? Will the atlas include tier 2? Would that make the atlas MA?
Not yet answered.

Jason: Is there any published cxg dataset with the full tier 1 metadata?
Yes, look in comments of #1252 for 3 examples

Jason + Lucia: Is there any network close to publish T1 metadata?
Lung is facing problems with embeddings but is getting there

Jason + Lucia: If datasets wrangled by lattice have been selected and need Tier 2 addition, how is it going to be handled? Does the lattice team have/ can have DPA?
Not yet answered. Lattice team can NOT deal with MA.

Bobbie: Can we have a meeting to discuss what the partial updates are going to address?
Not yet raised.

Ida/Arsenios: How many projects from w1 & w2 are in a complete status? If a lot of them are we need a solution for updating files
There are 15 projects from w1 & w2 that have submissions in complete state.
list of proj in complete state

27e2e0ae-5971-4927-aac1-19e81804097b
69324a96-a68a-4514-bbb4-f8f3ea4bd0f1
cbd3d276-9f24-4af9-8381-b11f6cdbdc4b
50154d1e-2308-44bf-9608-10c7afaa560b
7a8d45f1-353b-4508-8e89-65a96785b167
1dd552a5-eb4f-4b92-8088-7224bcbd0629
17cf943b-e247-454f-908b-da58665fcc56
415eb773-cadb-43d1-ab89-7d160d5cfc7d
28dd1438-8f40-40d0-8e53-ee3301b66218
222a92d5-277b-489c-aad8-a680d1fd2b12
c211fd49-d980-4ba1-8c6a-c24254a3cb52
73769e0a-5fcd-41f4-9083-41ae08bfa4c1
23509202-1e3c-4959-8a45-9c5b642a1066
031980e6-9f2b-433a-8f6e-081bd9aad0a3
894ae6ac-5b48-41a8-a72f-315a9b60a62e


use RNA-seq as base image

It seems travis has a space limit and we are hitting it. We do want to have RNA-seq tools in this flavor correct? Is it ok to merge and deactivate tests? Consider an other CI service? Ask travis for more space?

In my eyes 3 options,

ask travis for more space
get the travis test container running on own infrastructure, test locally (and manually I fear) and merge if tests pass
look for alternatives like jenkins, but I guess they have the same problem

btw: https://github.com/PacificBiosciences/pitchfork/issues/322 says
limits for travis docker containers:
2 cpus
50 minutes
20 G diskspace
And yes RNA-seq tools definitely should be in this flavor imho

Do you want to ask, they already know my name and have it probably on an index ;)

Feel free to merge if you think it is good to go.

I can contact them, guess it's not so easy during holidays, but we'll see