Retrieval of OWLDataSomeValuesFrom

OWL Object Representation
OWLObjectIntersectionOf((OWLDataSomeValuesFrom(property=OWLDataProperty(IRI('http://dl-learner.org/mutagenesis#','act')),filler=OWLDatatypeRestriction(OWLDatatype(IRI('http://www.w3.org/2001/XMLSchema#','double')), (OWLFacetRestriction(OWLFacet.MAX_INCLUSIVE, OWLLiteral(0.014999999664723873)),))), OWLDataSomeValuesFrom(property=OWLDataProperty(IRI('http://dl-learner.org/mutagenesis#','logp')),filler=OWLDatatypeRestriction(OWLDatatype(IRI('http://www.w3.org/2001/XMLSchema#','double')), (OWLFacetRestriction(OWLFacet.MAX_INCLUSIVE, OWLLiteral(1.2350000143051147)),)))))

DL Representation
(∃ act.xsd:double[≤ 0.014999999664723873]) ⊓ (∃ logp.xsd:double[≤ 1.2350000143051147])

Retrieval Result with KnowlegeBase
frozenset({OWLNamedIndividual(IRI('http://dl-learner.org/mutagenesis#','d17')), OWLNamedIndividual(IRI('http://dl-learner.org/mutagenesis#','d70')), OWLNamedIndividual(IRI('http://dl-learner.org/mutagenesis#','d181')), OWLNamedIndividual(IRI('http://dl-learner.org/mutagenesis#','d150'))})

Let's take a look at respective assertion about http://dl-learner.org/mutagenesis#d17 in the input KG
    <owl:NamedIndividual rdf:about="http://dl-learner.org/mutagenesis#d17">
     <logp rdf:datatype="http://www.w3.org/2001/XMLSchema#double">2.52</logp>
    </owl:NamedIndividual>

Is there any reason of returning this individual given it does not satisfiy the second condition ?
Edit: KnowledgeBase is being used

An example from carcinogenesis dataset.
OWLNamedIndividual(IRI('http://dl-learner.org/carcinogenesis#','d204')) is not in the retrieval of expression:∃ amesTestPositive.{False}
The CE is an instance of OWLDataHasValue(property=...,value=OWLLiteral(False))

For the mutagenesis case, the individual d17 has the following relations:
<owl:NamedIndividual rdf:about="http://dl-learner.org/mutagenesis#d17">
        <rdf:type rdf:resource="http://dl-learner.org/mutagenesis#Compound"/>
        <hasAtom rdf:resource="http://dl-learner.org/mutagenesis#d17_1"/>
        <hasAtom rdf:resource="http://dl-learner.org/mutagenesis#d17_10"/>
        <hasAtom rdf:resource="http://dl-learner.org/mutagenesis#d17_11"/>
        <hasAtom rdf:resource="http://dl-learner.org/mutagenesis#d17_12"/>
        <hasAtom rdf:resource="http://dl-learner.org/mutagenesis#d17_13"/>
        <hasAtom rdf:resource="http://dl-learner.org/mutagenesis#d17_14"/>
        <hasAtom rdf:resource="http://dl-learner.org/mutagenesis#d17_15"/>
        <hasAtom rdf:resource="http://dl-learner.org/mutagenesis#d17_16"/>
        <hasAtom rdf:resource="http://dl-learner.org/mutagenesis#d17_17"/>
        <hasAtom rdf:resource="http://dl-learner.org/mutagenesis#d17_18"/>
        <hasAtom rdf:resource="http://dl-learner.org/mutagenesis#d17_2"/>
        <hasAtom rdf:resource="http://dl-learner.org/mutagenesis#d17_3"/>
        <hasAtom rdf:resource="http://dl-learner.org/mutagenesis#d17_4"/>
        <hasAtom rdf:resource="http://dl-learner.org/mutagenesis#d17_5"/>
        <hasAtom rdf:resource="http://dl-learner.org/mutagenesis#d17_6"/>
        <hasAtom rdf:resource="http://dl-learner.org/mutagenesis#d17_7"/>
        <hasAtom rdf:resource="http://dl-learner.org/mutagenesis#d17_8"/>
        <hasAtom rdf:resource="http://dl-learner.org/mutagenesis#d17_9"/>
        <hasBond rdf:resource="http://dl-learner.org/mutagenesis#bond2120"/>
        <hasBond rdf:resource="http://dl-learner.org/mutagenesis#bond2121"/>
        <hasBond rdf:resource="http://dl-learner.org/mutagenesis#bond2122"/>
        <hasBond rdf:resource="http://dl-learner.org/mutagenesis#bond2123"/>
        <hasBond rdf:resource="http://dl-learner.org/mutagenesis#bond2124"/>
        <hasBond rdf:resource="http://dl-learner.org/mutagenesis#bond2125"/>
        <hasBond rdf:resource="http://dl-learner.org/mutagenesis#bond2126"/>
        <hasBond rdf:resource="http://dl-learner.org/mutagenesis#bond2127"/>
        <hasBond rdf:resource="http://dl-learner.org/mutagenesis#bond2128"/>
        <hasBond rdf:resource="http://dl-learner.org/mutagenesis#bond2129"/>
        <hasBond rdf:resource="http://dl-learner.org/mutagenesis#bond2130"/>
        <hasBond rdf:resource="http://dl-learner.org/mutagenesis#bond2131"/>
        <hasBond rdf:resource="http://dl-learner.org/mutagenesis#bond2132"/>
        <hasBond rdf:resource="http://dl-learner.org/mutagenesis#bond2133"/>
        <hasBond rdf:resource="http://dl-learner.org/mutagenesis#bond2134"/>
        <hasBond rdf:resource="http://dl-learner.org/mutagenesis#bond2135"/>
        <hasBond rdf:resource="http://dl-learner.org/mutagenesis#bond2136"/>
        <hasBond rdf:resource="http://dl-learner.org/mutagenesis#bond2137"/>
        <hasStructure rdf:resource="http://dl-learner.org/mutagenesis#benzene-1131"/>
        <hasStructure rdf:resource="http://dl-learner.org/mutagenesis#nitro-1133"/>
        <hasStructure rdf:resource="http://dl-learner.org/mutagenesis#ring_size_6-1132"/>
        <act rdf:datatype="http://www.w3.org/2001/XMLSchema#double">-3.0</act>
        <hasFifeExamplesOfAcenthrylenes rdf:datatype="http://www.w3.org/2001/XMLSchema#boolean">false</hasFifeExamplesOfAcenthrylenes>
        <hasThreeOrMoreFusedRings rdf:datatype="http://www.w3.org/2001/XMLSchema#boolean">false</hasThreeOrMoreFusedRings>
        <logp rdf:datatype="http://www.w3.org/2001/XMLSchema#double">0.87</logp>
        <lumo rdf:datatype="http://www.w3.org/2001/XMLSchema#double">-0.529</lumo>
    </owl:NamedIndividual>

Notice that the logp dataproperty has the value 0.87 which means that the classification is correct.
Can you make sure this is also the case in your mutagenesis ontology, (maybe you confused it with individual d170)

An example from carcinogenesis dataset.
OWLNamedIndividual(IRI('http://dl-learner.org/carcinogenesis#','d204')) is not in the retrieval of expression:∃ amesTestPositive.{False}
The CE is an instance of OWLDataHasValue(property=...,value=OWLLiteral(False))

I tested that CE on carcinogenesis using the following code and individual d204 was among the printed result.
kb = KnowledgeBase(path="../../KGs/Carcinogenesis/carcinogenesis.owl")

ce = OWLDataHasValue(property=OWLDataProperty(IRI.create("http://dl-learner.org/carcinogenesis#amesTestPositive")),value=OWLLiteral(False))
print(list(kb.individuals(ce)))

I am wondering why it is not showing in your case :thinking:

Thank you. Which branch have you used ?

develop branch

Can you make sure this is also the case in your mutagenesis ontology, (maybe you confused it with individual d170)

I guess you are right.


GitHub-API compliance

Fixes a couple of issues with the Gogs API.
Also adds the undocumented endpoint /repositories/:id (which is used by Octokit)
Closes #3729

We have conflicts here, are you willing to fix?

@unknwon Done, and I renamed the function to align with the conflicing change :)

Thanks! Any idea why CI both are failing?

Thanks for the update, but code isn't seem compiling...

Closed by https://github.com/gogits/gogs/pull/4549.


Storage: Add convenience for File Upload

Add a convenience method to automatically upload an entire as a series of ranges

@amnguye, It might be good to ask @tg-msft what he has in mind for this.
I'm thinking maybe we add overloads for the following methods, swapping Stream content for File file:

BlobClient.Upload(Stream content)
BlobClient.UploadAsync(Stream content)
FileClient.UploadRange()
FileClient.UploadRangeAsync()

I'm thinking users using AppendBlobClient and PageBlobClient will know how to convert a File to a FileStream.  @tg-msft, what do you think?

@seanmcc-msft - I think you're looking at a different type of convenience method that we don't currently have a work item (or plan) for yet.
This bug is specifically about making it possible to upload a 1GB file to File Storage without having to manually split it into 4mb chunks that you individually pass to UploadRangeAsync.  We did this for the simple BlobClient at https://github.com/Azure/azure-sdk-for-net/blob/master/sdk/storage/Azure.Storage.Blobs/src/BlobClient.cs#L472 and need something similar for FileClient.
I think the names FileClient.Upload/FileClient.UploadAsync would fit pretty naturally next to FileClient.UploadRange/FileClient.UploadRangeAsync.

Oh never mind, I didn't understand what this issue was.  Please disregard.


[HelpDot] Remove #gsc.tab=0 from homepage

Details

#gsc.tab is appended by google search script for help dot. (Reference: https://stackoverflow.com/a/48903354)
It was fixed in PR https://github.com/Expensify/App/pull/31244, but it still appears on the home page.
I'm doing some trial and error to see if this PR removes it for the home page.
Fixed Issues
$ https://github.com/Expensify/App/issues/31246
PROPOSAL: N.A.
Tests

cd docs && npm run createDocsRoutes && bundle exec jekyll serve --livereload --safe
Go to home page
Verify that the url doesn't contain gsc.tab=0 in the end

[x] Verify that no errors appear in the JS console

Offline tests

QA Steps

[x] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

deploy workflow will fail because it doesn't have permission to my fork

@rushatgabhane I assume, I am not required here.

@abdulrahuman5196 haha yea

context - https://expensify.slack.com/archives/C02QSAC6BJ8/p1699834547465169?thread_ts=1699660054.528539&cid=C02QSAC6BJ8

Created a build here: https://ed18b080.helpdot.pages.dev/
https://github.com/Expensify/App/pull/31278
It didn't seem to have the unwanted #gsc.tab 👍

Reviewer Checklist

[ ] I have verified the author checklist is complete (all boxes are checked off).
[ ] I verified the correct issue is linked in the ### Fixed Issues section above
[ ] I verified testing steps are clear and they cover the changes made in this PR

[ ] I verified the steps for local testing are in the Tests section
[ ] I verified the steps for Staging and/or Production testing are in the QA steps section
[ ] I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[ ] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)

[ ] I checked that screenshots or videos are included for tests on all platforms
[ ] I included screenshots or videos for tests on all platforms
[ ] I verified tests pass on all platforms & I tested again on:

[ ] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[ ] MacOS: Chrome / Safari
[ ] MacOS: Desktop

[ ] If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
[ ] I verified proper code patterns were followed (see Reviewing the code)

[ ] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
[ ] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[ ] I verified that comments were added to code that is not self explanatory
[ ] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[ ] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
[ ] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[ ] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[ ] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[ ] I verified the JSDocs style guidelines (in STYLE.md) were followed

[ ] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[ ] I verified that this PR follows the guidelines as stated in the Review Guidelines
[ ] I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
[ ] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[ ] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[ ] If a new component is created I verified that:

[ ] A similar component doesn't exist in the codebase
[ ] All props are defined accurately and each prop has a /** comment above it */
[ ] The file is named correctly
[ ] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[ ] The only data being stored in the state is data necessary for rendering and nothing else
[ ] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[ ] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[ ] All JSX used for rendering exists in the render method
[ ] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[ ] If any new file was added I verified that:

[ ] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[ ] If a new CSS style is added I verified that:

[ ] A similar style doesn't already exist
[ ] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG)

[ ] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[ ] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[ ] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[ ] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[ ] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[ ] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[ ] I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

Known issue with GitHub actions here: https://github.com/Expensify/App/pull/31254#issuecomment-1807296337
Not an emergency.

🚀 Deployed to staging by https://github.com/AndrewGable in version: 1.3.99-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/roryabraham in version: 1.3.99-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to staging by https://github.com/AndrewGable in version: 1.4.0-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


Release 2023 04 28

Release 2023-04-26
NB: this PR must be merged only by 'Create a merge commit'!
Checklist when preparing for release

[ ] Read or refresh the release flow guide
[ ] Ask in the cloud Slack channel that you are going to rollout the release. Any blockers?
[ ] Does this release contain any db migrations? Destructive ones? What is the rollback plan?

Checklist after release

[x] Make sure instructions from PRs included in this release and labeled manual_release_instructions are executed (either by you or by people who wrote them).

[ ] #3954

post-release: fix "broken" => "Broken" in prod alert

[ ] Based on the merged commits write release notes and open a PR into website repo (example)
[ ] Check #dev-production-stream Slack channel
[ ] Check stuck projects page
[ ] Check recent operation failures
[ ] Check cloud SLO dashboard
[ ] Check compute startup metrics dashboard

LGTM. Note that there is still 1 stuck project on staging.

This project has been relocating.


UseDotNetV2 Agent Tools Directory Structure for Non-Internet-Connected Agents

Required Information
Type: Question
Task Name: UseDotNet
Environment

Server - TFS on-premise (Azure DevOps Server 2020 Update 1.1)

Agent - Private (Windows 10.0.17763 x64, Agent v2.181.2)

Issue Description
I have several non-internet connected Windows Servers for use as build agents and wish to pre-populate the _tool directory with version 5 and 6 of the .NET SDK to ensure they can correctly be picked up by any agent trying to run a given build pipeline. The servers cannot be given internet access due to corporate security policy.
Having looked at the code for the UseDotNet task here and azure-pipelines-tool/tool.ts I cannot easily figure out what the correct structure should be to ensure the agent views the .NET SDK as being already cached and doesn't attempt to download it from the internet which will fail.
I can see the following structure for NuGet in the _tool directory:
...\_tool\<version>\<architecture>.complete
...\_tool\<version>\<architecture>\nuget.exe

I have tried to replicate it for the .NET 5 SDK (v5.0.408) by downloading the ZIP from the location referred to in the releases JSON, but have had no success:
...\_tool\dotnet\5.0.408\x64.complete
...\_tool\dotnet\5.0.408\x64\dotnet-sdk-5.0.408-win-x64.zip

The task definition is as follows:
- task: UseDotNet@2
  displayName: 'Use .NET 5 SDK'
  inputs:
    packageType: 'sdk'
    version: '5.0.408'
    performMultiLevelLookup: true

Unfortunately the Agent doesn't see the .NET SDK as being in the cache, attempts to download it from the internet and fails. I have also tried the following variations:

Use win-x64 for the architecture instead of x64 to match the ZIP name
Extract the contents of the ZIP inside the x64 or win-x64 directory
Try with and without performMultiLevelLookup

Questions:

What should the correct directory/file layout be?
Would it also be possible to have this added to the documentation in case others are also trying to use agents in disconnected environments?

Hi @MDendura, did you ever figure this one out?
Have the same issue now, with performMultiLevelLookup not honoring the default locations on offline servers, and nothing added to cache.


Deprecated mySQL driver is being loaded

Seeing this errr-level warning in the application logs at startup:
[ERR] Loading class com.mysql.jdbc.Driver'. This is deprecated. The new driver class is com.mysql.cj.jdbc.Driver'. The driver is automatically registered via the SPI and manual loading of the driver class is generally unnecessary.

The mysql-connector dependency is up to date
There is no explicit driver class in the configuration (Spring seems to just be auto-wiring)
The Hibernate MySQL dialect is being set in the application.properties

fixed in Dev


More infrastructure needed for wrapper code

The following features are still missing from the metadata code, I believe:

Ability to determine whether an extendr function has a return value or not. Functions without return value need to return invisible().
Ability to determine the name of the extendr module by calling a generic function (e.g., wrap__get_module_name). This is needed for rextendr.

@clauswilke,
Could you please explain what is the issue with Rust functions returning nothing?
Currently, such function is wrapped in invisible():
rextendr::rust_function("fn rust_fn() {}")
#> build directory: C:\Users\[redacted]\AppData\Local\Temp\RtmpkhrAfA\file398059da5d66
rust_fn()
print(rust_fn)
#> function() {
#>     invisible(.Call("wrap__rust_fn", PACKAGE = "rextendr1"))
#> }

Created on 2021-01-24 by the reprex package (v0.3.0)
This build uses commit daee5c88.

@clauswilke,
Could you please explain what is the issue with Rust functions returning nothing?
Currently, such function is wrapped in invisible():
rextendr::rust_function("fn rust_fn() {}")
#> build directory: C:\Users\[redacted]\AppData\Local\Temp\RtmpkhrAfA\file398059da5d66
rust_fn()
print(rust_fn)
#> function() {
#>     invisible(.Call("wrap__rust_fn", PACKAGE = "rextendr1"))
#> }

Created on 2021-01-24 by the reprex package (v0.3.0)
This build uses commit daee5c88.

The new wrapper framework that generates wrappers by a call to the compiled library doesn't add invisible(). Example:
library(extendrtests)

x <- MyClass$new()
x$set_a(10)
#> NULL
x$set_a
#> function(x) .Call(wrap__MyClass__set_a, self, x)
#> <environment: 0x7ff17c0b10b0>

Created on 2021-01-24 by the reprex package (v0.3.0)
I'd want to fix this before porting rextendr over.

The new wrapper framework that generates wrappers by a call to the compiled library doesn't add invisible(). Example:
library(extendrtests)

x <- MyClass$new()
x$set_a(10)
#> NULL
x$set_a
#> function(x) .Call(wrap__MyClass__set_a, self, x)
#> <environment: 0x7ff17c0b10b0>

Created on 2021-01-24 by the reprex package (v0.3.0)
I'd want to fix this before porting rextendr over.

Upon further reflection, maybe the second point is not a good idea. I'd like to be able to use multiple modules in one Rust library, and I believe the current code allows for that, but having a single function with unique name try to return multiple module names would be problematic (I think).
Fortunately I now see a fairly easy way to work around this in rextendr, so I think we're good. We do need point 1, though, information about whether the function returns a value or not.

Upon further reflection, maybe the second point is not a good idea. I'd like to be able to use multiple modules in one Rust library, and I believe the current code allows for that, but having a single function with unique name try to return multiple module names would be problematic (I think).
Fortunately I now see a fairly easy way to work around this in rextendr, so I think we're good. We do need point 1, though, information about whether the function returns a value or not.

If I read this line correctly, functions that don't return a value have a return type represented by the string "()":
https://github.com/extendr/extendr/blob/37791965c4c3fe99b048a5225ce4e57bbcfa4e96/extendr-macros/src/lib.rs#L226
This then gets set here:
https://github.com/extendr/extendr/blob/37791965c4c3fe99b048a5225ce4e57bbcfa4e96/extendr-macros/src/lib.rs#L390
And can be read here as func.return_type:
https://github.com/extendr/extendr/blob/37791965c4c3fe99b048a5225ce4e57bbcfa4e96/extendr-api/src/metadata.rs#L119

If I read this line correctly, functions that don't return a value have a return type represented by the string "()":
https://github.com/extendr/extendr/blob/37791965c4c3fe99b048a5225ce4e57bbcfa4e96/extendr-macros/src/lib.rs#L226
This then gets set here:
https://github.com/extendr/extendr/blob/37791965c4c3fe99b048a5225ce4e57bbcfa4e96/extendr-macros/src/lib.rs#L390
And can be read here as func.return_type:
https://github.com/extendr/extendr/blob/37791965c4c3fe99b048a5225ce4e57bbcfa4e96/extendr-api/src/metadata.rs#L119

Yup, this works. See #153.

Yup, this works. See #153.


[Question] Migrate homeserver name

My Homeserver is at matrix.domain.com while my matrix domain (the part of the username) is domain.com
I accidentally configured matrix-media-repo like this:
homeservers:
  matrix.domain.com:
    csApi: 'https://matrix.domain.com'

However the documentation states that it should look like this (which makes sense):
homeservers:
  domain.com:
    csApi: 'https://matrix.domain.com'

I tried just changing the config but then all old images are lost and sending new images isn't working either. Is there a way to migrate this?

Domain migration isn't supported, much like how most homeservers don't support changing the name after installation, sorry.


@changesets/cli should be dev dependency

Hi, currently updating from rc9 to rc10 adds a whole load of new dependencies. As I understand it, @changesets/cli is only needed to create releases of this package so should not be needed for consumers of the package.

Good catch


fix(radiofield): remove check for the value

Based on this PR this conditional should be removed
https://github.com/zopaUK/react-components/pull/231

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Visual fluency

Hello, I have noticed that when the scene is slightly larger and the video memory usage is around 5G (my 4090), moving the scene position left and right can cause a bit of lag. Is there any way to solve this problem?

At a slightly closer distance, the FPS is high, but at a distance, the FPS is low and the visualization effect is poor (compared to web-based visualization algorithms such as superSplat). Is there a problem with the sorting algorithm?

The urgent task now is to increase the smoothness of visualization. In the same large-scale scene, when viewed from a medium to long distance, SuperSplat browsing is obviously smooth. It's not C++, why is it so smooth?

What OS are you using? Linux or Windows? I noticed an similar issue on Linux w.r.t. large scenes, where Windows did not have this issue.
Anyhow, I'm not sure what SuperSplat is doing, but I think they are using the WebGPU API, not WebGL.  This means they are using a more "modern" API that may not have the same issues as older OpenGL based APIs.  Specifically, the copying of buffers from compute shaders (for radix sort) to the rendering side. I'd like to try to port splatapult to Vulkan, but it's not something I can get to soon.

Thank you for your answer. I am using Windows, and the data visualization browsing at around 2GB is indeed quite laggy. The web version is not laggy. Personally, I am still quite confused, maybe it is a problem with my computer.


Custom icons for Evolution shortcuts editor

Is your feature request related to a problem? Please describe.
I would like to be able to set custom icons for switches created with the Evolution Editor perhaps based on the code of the free Font Awesome icons or similar icon sets.
Describe the solution you'd like
Add a field in which you can enter the icon code of the selected font set to display a customised icon and not the same one for each button or select from a preview of icons available.
Describe alternatives you've considered
Alternative icon set as TrueType Font:
https://fonts.google.com/icons
https://fontawesome.com/icons
https://lineicons.com/icons/
https://pictogrammers.com/library/mdi/

Hi @piersandro ,
Thank you for your ideas! Actually, I have the same plan, just don't have proper sources. I think you offer me a lot of awesome icons. I will implement this feature in 2.4.1 or 2.4.2.

feature Icons for evolution has been included in version 2.4.1, but I use apple SF symbol in this version.


Do not check cloud credentials

dvc should work out of box without any cloud credentials and error\warning messages.
Currently:
$ dvc run python code/df_to_matrix.py data/Posts-bin-fr-test.tsv data/Posts-test-matrix.p
Error. config 'dvc.conf' is not correctly setup.  Please fix:
Error.     can't find aws credentials.  TODO

Desired behavior:

by default, no cloud is set in config "Cloud = ". No checking.
if Cloud is set in config - dvc complains only in cloud related commands (sync currently and remove)

done; will push as part of another batch of config stuff


Refactor 'Running Spring Boot with Azure Cache for Redis' example

Is this issue resolved, as I'm neither able to see a description nor the resolution. Can someone please shed some light.

This issue is not resolved. Note that the work here is intended to be to align this example with how the rest of the repository is structured.


Release for Scala 3.0.0-RC1

There is a regression in macro
https://github.com/lampepfl/dotty/issues/11437

done with M3


[FLOC 2766] Doc changes from user feedback

Fixes 2766
Please allow @alicesowerby to review before merging

All looks good to go!


Fix build for missing last_modified_at tag

I was mistaken thinking this plugin was available in GH pages, but it is
not.

Build failed.

http://logs.bonnyci.com/check_github/BonnyCI/bonnyci.org/29/1487376795.71/bonnyci-run-check : FAILURE in 2m 16s


tap.throws leaking error

i'm getting some strange behavior with my tests:

any ideas or things i might be doing wrong?

It looks like the () => syncify(Promise.reject(new Error('this is an error')) function doesn't throw immediately when called.  My suspicion would be that, since Promise rejection is async, it's throwing after the current tick?

Oh, or maybe that's the point that syncify is supposed to be doing, making things sync?  What does this do?
try {
  syncify(Promise.reject(new Error('x')))
  t.fail('did not throw!')
} catch (er) {
  t.pass('got expected error')
}

yeah it might be leaking into the next tick (things get unpredictable when you start messing with uvloop) i'll close this for now, since it appears to not be a tap issue

i'm getting this issue again, and this time i'm not messing with the event loop.
here's my test:
const PromiseUtil = require('.');
const tap = require('tap');

tap.plan(3);

{
  const p = PromiseUtil.create();
  tap.same(PromiseUtil.getDetails(p), { state: 'pending' }, 'details for pending');
}

{
  const p = Promise.resolve(5);
  tap.same(PromiseUtil.getDetails(p), { state: 'resolved', result: 5 }, 'details for resolved');
}

{
  const e = new Error('error');
  const p = Promise.reject(e);
  tap.same(PromiseUtil.getDetails(p), { state: 'rejected', result: e }, 'details for rejected');
}

tap.end();

output:
TAP version 13
1..3
ok 1 - details for pending
ok 2 - details for resolved
ok 3 - details for rejected
# time=7.21ms
Error: error
    at Object.<anonymous> (test.js:17:13)
    at Module._compile (module.js:641:30)
    at Object.Module._extensions..js (module.js:652:10)
    at Module.load (module.js:560:32)
    at tryModuleLoad (module.js:503:12)
    at Function.Module._load (module.js:495:3)
    at Function.Module.runMain (module.js:682:10)
    at startup (bootstrap_node.js:191:16)
    at bootstrap_node.js:613:3
{ name: 'TAP', test: 'TAP' }

PromiseUtil.getDetails just wraps process.binding('util').getPromiseDetails
I haven't looked into the tap code but is it possible that it throws out the last error from process unhandled rejection?

@devsnek Can you please copy and paste the actual output between ``` blocks in issues, instead of screenshots? Your low-contrast semi-transparent terminal is quite lovely, but unfortunately nearly impossible for my eyeballs to parse properly :)
Anyway:
const PromiseUtil = require('.');
const tap = require('tap');

tap.plan(3);

{
  const p = PromiseUtil.create();
  tap.same(PromiseUtil.getDetails(p), { state: 'pending' }, 'details for pending');
}

{
  const p = Promise.resolve(5);
  tap.same(PromiseUtil.getDetails(p), { state: 'resolved', result: 5 }, 'details for resolved');
}

{
  const e = new Error('error');
  const p = Promise.reject(e);
  tap.same(PromiseUtil.getDetails(p), { state: 'rejected', result: e }, 'details for rejected');
}

tap.end();

output:
TAP version 13
1..3
ok 1 - details for pending
ok 2 - details for resolved
ok 3 - details for rejected
# time=7.21ms
Error: error
    at Object.<anonymous> (test.js:17:13)
    at Module._compile (module.js:641:30)
    at Object.Module._extensions..js (module.js:652:10)
    at Module.load (module.js:560:32)
    at tryModuleLoad (module.js:503:12)
    at Function.Module._load (module.js:495:3)
    at Function.Module.runMain (module.js:682:10)
    at startup (bootstrap_node.js:191:16)
    at bootstrap_node.js:613:3
{ name: 'TAP', test: 'TAP' }

My guess here is that the throw is indeed because of an unhandled promise rejection, especially as it comes on the next tick after tap has ended.  Add a p.catch(er => tap.equal(er, e)) or even more simply just tap.rejects(p, e), so that the rejection is handled.

Also, you don't have to call tap.end(), and in fact, it's probably better if you don't, and just let the top-level auto-end handle it, so that anything that happens on next tick is more usefully reported.


[RFC] Fix workflow level timeouts

issue: https://github.com/argoproj/argo/issues/848
mimic https://github.com/argoproj/argo/commit/133a23ce20b4570ded81fac76a430f0399c1eea1 . Set the pod ttl to template or wf ttl whichever is smaller.

 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.

#1357

I agree with @dtaniwaki comments. @zhujl1991 - If those are addressed we can merge it in.

Is it possible that the same issue breaks termination when retry is used? #1620


ReservedConcurrentExecutions decreases UnreservedConcurrentExecution below minimum value

I am encountering an error when trying to deploy a stack using AWS SAM on us-wesr-2. The error message is as follows:
"ReservedConcurrentExecutions for function decreases account's UnreservedConcurrentExecution below its minimum value of [10]. (Service: Lambda, Status Code: 400, Request ID: 204aa629-d46e-47b8a3f695fea8fcf590)" (RequestToken: a35c5eb0-d1a2-cc17-adff-8a1fd84cd738, HandlerErrorCode: InvalidRequest)
The error is causing a rollback of the stack, with the following message:
ROLLBACK_IN_PROGRESS AWS::CloudFormation::Stack alarm-context-tool The following resource(s) failed to create: [AlarmContextFunction]. Rollback requested by user"
To Reproduce
Steps to reproduce the behavior:

Installed all the dependencies as per: "pip install -r ./dependencies_layer/requirements.txt &&
pip install aws_lambda_powertools
Updated the template.yaml
Executed sam build && sam deploy --guided
Getting error as per screenshot attached

Expected behavior
The deployment should be sucessful since my Concurrent Execution is set to 10 as per default
OS: Cloud9 AmazonLinux 2023 AMI

You have exceeded a Lambda limit in your account. This Stack Overflow question explains it well. For a temporary fix to get yourself started, you can remove ReservedConcurrentExecutions: 10 from template.yaml. I recommend that you request a limit increase though, otherwise you risk an alarm not triggering the Lambda function.

I already requested increase of quota limit but getting the same error. It works by removing ReservedConcurrentExecutions: 10


Decoder Issue - Cannot decode "auth_header" anymore

If you see the comments of the method auth_header in the below code:
https://github.com/cloudfoundry/cf-uaa-lib/blob/master/lib/uaa/token_issuer.rb#L37-L39
you will notice that it generates a header segment which starts with something like "bearer ". But the decode method in the code below does not take into consideration this prefix.
https://github.com/cloudfoundry/cf-uaa-lib/blob/master/lib/uaa/token_coder.rb#L102-L107
This causes the following error to occur:
/usr/local/lib/ruby/gems/2.2.0/gems/cf-uaa-lib-3.2.5/lib/uaa/util.rb:178:in `rescue in decode64': invalid base64 encoding (CF::UAA::DecodeError)

Got it. It does not expected auth_header but access_token itself. The README was pointing to a deprecated method which threw me off a bit. but got the following working fine:
token_info = CF::UAA::TokenCoder.decode(token.info["access_token"], {:verify=>false})


fix #91 tokenizer load error

fix  #91 tokenizer load error  when using some hugging face models like clue/albert_chinese_small and other chinse albert model which need to load with BertTokenizer

Hello @WangHexie  I just saw you closed this.   Is this no longer the recommended solution for this issue?

@amaiya The fix still works but I made a commit to the branch which made it unable to merge automatically. The fix only change a few lines of codes and I think merging manually might be more complicated than adding these lines of codes when you are free to do it.
There's a print line in the code , delete it if you think it's needless.
Or you can create pull request from the commit point.


fix(static): allow to load .node files

e.g. canvas.node files

Hi @franzmoro coudl you point me to an example file I could test this with?


Add 'favorites' or pinning of frequently used/user chosen settings

Problem Statement

I go between DATA and Standard and Programmer quite a bit. It'd be nice to have a pinned area where these three are. Can we add that?
Evidence or User Insights

To make frequently used items easier to access.
Proposal

It makes it easier to use the app...
Goals

I can perform my tasks quicker.
Non-Goals

Solving world hunger. Calculator doesn't make food.
Low-Fidelity Concept

Requested Assignment

I'm just suggesting this idea.  I don't want to implement it.

This is your friendly Microsoft Issue Bot. I've seen this issue come in and have gone to tell a human about it.

Favorites is certainly one way to address the problem of having to navigate so many different calculator and converter modes, but I think we would prefer to address this in a couple different ways. Unit converters can be streamlined quite a bit (covered by #594) and there are ideas like #872 that propose exposing converters in other modes without navigating, which is really interesting, and I think would address your use case exactly. If these don't pan out, we can certainly revisit adding favorites/pinning of individual modes, though. Thanks again for your contribution!


[beta] Un-populated Challenges Not Disabled in Map

Learn Sass Challenges,
Learn React Challenges,
Learn D3 Challenges,
Learn Accessibility Challenges,
Learn Agile Challenges,
Learn Computer Science Challenges,
Learn Data Visualization Challenges,
Learn Embedded Internet of Things Challenges,
Learn Game Development Challenges,
Learn Gamification Challenges,
Learn Machine Learning Challenges,
Learn Math for Progrmmers Challenges,
Learn Mobile JavaScript Development Challenges,
Learn DevOps Challenges,
Learn Software Engineering Principles Challenges,
Learn Statistics Challenges,
Learn Tools Challenges,
Learn User Experience Design Challenges,
Learn Visual Design Challenges

@Bouncey Those challenges are not disabled during development, but yes they need to be disabled on the beta site.

Fixed in beta


Error: Requesting too quickly.

Describe the bug
Homebridge log is giving Error: Requesting too quickly. errors frequently
To Reproduce
Steps to reproduce the behavior:

Kill Home app
Start Home app
Homebridge log gives

Error: Requesting too quickly.
    at TuyaWebApi.discoverDevices (/usr/local/lib/node_modules/@milo526/homebridge-tuya-web/src/TuyaWebApi.ts:159:32)
    at process._tickCallback (internal/process/next_tick.js:68:7)

Expected behavior
Screenshots
Device

Plugin: @milo526/homebridge-tuya-web
Version: [See firmware in your homekit device]
Model : 0.4.1

Please remove the pollingInterval key from your config file and try not to open your Home.app for about an hour. This should reduce the number of errors you get.
The rest of this is an issue with Tuya which I can do very little about, the current release version of the plugin suppresses these errors, they are still very much there though.

i got these errors with the pollingInterval  disabled,
looking from these debug logs, i think it is trying to make http requests everytime i open Home app.
Will enabling pollingInterval help, since it will read device status from cache instead of making http request everytime i open Home app?
[7/30/2020, 10:40:08 AM] [MiOutletPlatform] [MiOutletPlatform][DEBUG]MiPlugBase - Outlet - getPower: off
[7/30/2020, 10:40:08 AM] [MiOutletPlatform] [MiOutletPlatform][DEBUG]MiPlugBase - Outlet - getOutletInUse: off
[7/30/2020, 10:40:08 AM] [TuyaWebPlatform] Sending HTTP GET request to /homeassistant/skill.
[7/30/2020, 10:40:09 AM] [TuyaWebPlatform] Error: Requesting too quickly.
    at TuyaWebApi.discoverDevices (/usr/local/lib/node_modules/@milo526/homebridge-tuya-web/src/TuyaWebApi.ts:159:32)
    at process._tickCallback (internal/process/next_tick.js:68:7)
[7/30/2020, 10:40:12 AM] [TuyaWebPlatform] Sending HTTP GET request to /homeassistant/skill.
[7/30/2020, 10:40:13 AM] [TuyaWebPlatform] Error: Requesting too quickly.
    at TuyaWebApi.discoverDevices (/usr/local/lib/node_modules/@milo526/homebridge-tuya-web/src/TuyaWebApi.ts:159:32)
    at process._tickCallback (internal/process/next_tick.js:68:7)

While what you state was true some time ago, this is no longer the case now. The cache is hard-coded to be 15 seconds. I strongly suspect that the pollingInterval will only actively hurt this issue, not help it (since it will just ensure that there are more request being made).

Thanks for making that clear!


Bug: Spacing issue in rendering

Expected:

Actual:

Log:
mosaic-3.log
cating the log file outside of mosaic gives expected output, so the bug seems to be in the rendering.
Also, this issue doesn't happen with normal files containing tabs/spaces.
This is the relevant part of the greeting prompt.
echo -ne (\
        df -l -h | grep -E 'dev/(xvda|sd|mapper)' | \
        awk '{printf "\\\\t%s\\\\t%4s / %4s  %s\\\\n\n", $6, $3, $2, $5}' | \
        sed -e 's/^\(.*\([8][5-9]\|[9][0-9]\)%.*\)$/\\\\e[0;31m\1\\\\e[0m/' -e 's/^\(.*\([7][5-9]\|[8][0-4]\)%.*\)$/\\\\e[0;33m\1\\\\e[0m/' | \
        paste -sd ''\
    )

NOTE: Pasting this directly to mosaic is also causing a panic, so for now, we need to create a shell script and run it with fish to test.

@henil - I merged a fix for this to main. For me your file looks properly with cat - can you please confirm?

@imsnif Thanks that fixes the issue.

For me your file looks properly with cat - can you please confirm?

Yes, they look the same(with and without mosaic) now :)
But pasting this code (not even running, just pasting) directly into mosaic causes a panic for me. At first I thought it was due to tab not being handled but its still happening.
echo -ne (\
        df -l -h | grep -E 'dev/(xvda|sd|mapper)' | \
        awk '{printf "\\\\t%s\\\\t%4s / %4s  %s\\\\n\n", $6, $3, $2, $5}' | \
        sed -e 's/^\(.*\([8][5-9]\|[9][0-9]\)%.*\)$/\\\\e[0;31m\1\\\\e[0m/' -e 's/^\(.*\([7][5-9]\|[8][0-4]\)%.*\)$/\\\\e[0;33m\1\\\\e[0m/' | \
        paste -sd ''\
    )

This is the error

Error: thread 'screen' panicked at 'swap_remove index (is 36) should be < len (is 1)': library/alloc/src/vec.rs:979

Should this go in a new issue?

Yes, please open a new issue. Otherwise it will be hard (especially for others) to follow.


Give better error message when trying to launch a kernel in a work-group that required too many vgprs

Perhaps this should rather go to HCC, but I'll start here:
I have ported a CUDA application to HIP, and it was failing with:
### HCC STATUS_CHECK Error: HSA_STATUS_ERROR_INVALID_ISA (0x100f) at file:mcwamp_hsa.cpp line:1192
After adding the ROCr Debugging Agent, I received the error message
Queue error state in GPU agent: AMD gfx906
Node: 1
Queue ID:<PHONE_NUMBER>24000 (Out of VGPRs;)

It seems this is related to a too large work-group, such that the GPU does not have sufficient VGPRs. At least it works when I reduce the work-group size. Unfortunately the original error message about HSA_STATUS_ERROR_INVALID_ISA is pretty misleading, it would be better to explicitly state that there are not enough GPU registers.

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

Sorry, don't have time to follow up and retest these old tickets, closing.


Add CI for DML backend

@BruceDai PTAL. Thanks.

LGTM， thanks.
@fujunwei Please help merge it, thanks.


feat: LandingPageEvent component

Screenshot

Link
https://www.figma.com/file/e6sfiMNbpYefqIeC6BDHYT/Ibadan-Techies-Website?node-id=53-113&t=5j4Iv0au5o65Bgeq-0
Dependencies
All dependencies are available.

.take

.take

closed by #51


BootROM reversing

I began reversing of the dumped BootROM.
If I correctly defined, the entry point of the BootROM is:
ROM:00001498             sub_1498
ROM:00001498 00 21                       MOVS    R1, #0
ROM:0000149A 0A 46                       MOV     R2, R1
ROM:0000149C 0B 46                       MOV     R3, R1
ROM:0000149E 0C 46                       MOV     R4, R1
ROM:000014A0 0D 46                       MOV     R5, R1
ROM:000014A2 0E 46                       MOV     R6, R1
ROM:000014A4 0F 46                       MOV     R7, R1
ROM:000014A6 88 46                       MOV     R8, R1
ROM:000014A8 89 46                       MOV     R9, R1
ROM:000014AA 8A 46                       MOV     R10, R1
ROM:000014AC 8B 46                       MOV     R11, R1
ROM:000014AE 8C 46                       MOV     R12, R1
ROM:000014B0 00 48                       LDR     R0, =0x14B9
ROM:000014B2 00 47                       BX      R0              ; loc_14B8
ROM:000014B2             ; End of function sub_1498

The BootROM actively uses the high addresses 0xe0000000 ...
These addresses are defined as CPU registers. What are actually these registers?
ROM:00001A8C             sub_1A8C                                ; CODE XREF: ROM:000014BC↑p
ROM:00001A8C 06 4A                       LDR     R2, =0xE000EDFC
ROM:00001A8E 13 68                       LDR     R3, [R2]
ROM:00001A90 03 F0 7E 43                 AND.W   R3, R3, #0xFE000000
ROM:00001A94 43 F0 80 73                 ORR.W   R3, R3, #0x1000000
ROM:00001A98 13 60                       STR     R3, [R2]
ROM:00001A9A 04 4A                       LDR     R2, =0xE0001000
ROM:00001A9C 13 68                       LDR     R3, [R2]
ROM:00001A9E 43 F0 01 03                 ORR.W   R3, R3, #1
ROM:00001AA2 13 60                       STR     R3, [R2]
ROM:00001AA4 70 47                       BX      LR
ROM:00001AA4             ; End of function sub_1A8C

And another one high address range is in 0x40000000 ... defined as HW registers. Whether I correctly understand that it is timers, watchdog, global control registers to configure, say, access to the memory regions, RSA HW accelerator registers, etc...?
ROM:00001B5C             sub_1B5C                                ; CODE XREF: sub_1B70:loc_1B7E↓p
ROM:00001B5C                                                     ; sub_1BE4+14↓p ...
ROM:00001B5C 03 4B                       LDR     R3, =0x40320030
ROM:00001B5E 18 68                       LDR     R0, [R3]
ROM:00001B60 80 F0 04 00                 EOR.W   R0, R0, #4
ROM:00001B64 C0 F3 80 00                 UBFX.W  R0, R0, #2, #1
ROM:00001B68 70 47                       BX      LR
ROM:00001B68             ; End of function sub_1B5C
ROM:00001B68
ROM:00001B68             ; ---------------------------------------------------------------------------
ROM:00001B6A 00                          DCB    0
ROM:00001B6B BF                          DCB 0xBF
ROM:00001B6C 30 00 32 40 off_1B6C        DCD 0x40320030          ; DATA XREF: sub_1B5C↑r

If you have already defined purpose of some HW and CPU registers, could you share it, please?

What we called CPU Registers are the ones defined by the Cortex-m3 architecture (there are public). HW registers are custom ones and correspond, as you mentioned to timers, watchdog, etc.
You will find some symbols in the Ghidra loader (symbols.xml). We don't plan to release more details for now.

Looks promising. Thanks!
SYMBOL ADDRESS="40224060" NAME="HW_KEY" Is it the SoC OTP storage of the 768 bit private key. For RSA it looks very small but for ECC very big.

Yes we played a bit with emulation, but we did not emulated these specific hw devices. It could definitely be interesting to do so.


No sensors in HA

Hi,
I've installed the integration with HACS, all good.
But I only get one new entity from it:
update.epex_spot_update
Any idea why I don't get the expected sensor? Do I need to configure something first?
Thanks!

Integration has not yet been installed. My fault, sorry


add base_url to reduce lag time for mobile app

Just curious, what's the theory behind why this might help reduce lag time?

Makes sure that it provides read-after-write consistency - is that correct, @sheydari-ds ?

Yes!
On Fri, Jul 24, 2015 at 1:14 PM, Chloe Lee<EMAIL_ADDRESS>wrote:

Makes sure that it provides read-after-write consistency - is that
correct, @sheydari-ds https://github.com/sheydari-ds ?
—
Reply to this email directly or view it on GitHub
https://github.com/DoSomething/northstar/pull/185#issuecomment-124583890
.

I couldn't find the code that this actually affects. Where does base_url get used?
Also, this feels nitpicky, but the newline is extraneous.

thanks for catching that, @jonuy ! Just deleted the extra line.
Using this file sets up all of the credentials needed to get into S3 I believe. Setting the base_url here should ensure the read-after-write is enabled and thinking that it should reduce lag time.
@sheydari-ds let me know if I'm incorrect about anything above or missing anything!

@chloealee Yes, that's correct. @jonuy Essentially, Amazon guarantees read-on-write consistency if we use a specific endpoint for S3, instead of the default one.

I was mostly just looking to see where in Northstar code it's being used, and it looks like it's actually in the aws-sdk-php library which is why I didn't see it initially when going through code just on :octocat:
:+1:


Crashes while Download

What steps will reproduce the problem?

1.1 Pressing Download all or Download selected after Get all
1.2 Downloading 3 or more pages
tag christmas
What is the expected behavior? What do you get instead?

1.1 Grabber is crashing while it is in the download process of the pictures, instead of running through.
1.2 Grabber is crashing on downloading the 3rd page, instead of loading all 3 pages,
What version of the program are you using? On what operating system?
Grabber 5.01
Win 7 Home Premium
Please provide any additional information below
here is all data you need
model.txt
settings.txt
settings2.txt
mainlog.txt

The crash occured when downloading a 173MB file (NFSW: file & page), so the crash is more than likely to be caused by the size of said file.
See issue #954 and #963 for follow-up, I'll be closing this issue.


Pack the StandardMaterialKey into a single scalar instead of a structure.

This commit changes the StandardMaterialKey to be based on a set of bitflags instead of a structure. We hash it every frame for every mesh, and #[derive(Hash)] doesn't generate particularly efficient code for large structures full of small types. Packing it into a single u64 therefore results in a roughly 10% speedup in queue_material_meshes on many_cubes --no-frustum-culling.

Once there's a migration guide I'm happy to merge this :)

I don't think this is actually a breaking change. StandardMaterialKey is a public type, but all of its internals are private, and I only changed the internals.


ArchLinux CI is failing since 2024-10-10

https://github.com/lima-vm/lima/actions/runs/11263406944/job/31321212683
time="2024-10-09T22:01:04Z" level=info msg="[hostagent] Waiting for the essential requirement 2 of 4: \"user session is ready for ssh\""
time="2024-10-09T22:01:44Z" level=info msg="[hostagent] Waiting for the essential requirement 2 of 4: \"user session is ready for ssh\""
time="2024-10-09T22:02:24Z" level=info msg="[hostagent] Waiting for the essential requirement 2 of 4: \"user session is ready for ssh\""
time="2024-10-09T22:02:52Z" level=fatal msg="did not receive an event with the \"running\" status"
Error: ERROR] Failed to start "archlinux"

This might relate to the recent update of the cloud-init package: https://gitlab.archlinux.org/archlinux/packaging/packages/cloud-init/-/commit/08e804f7c41f7d742496aac6439ea8545d7202b6
https://github.com/canonical/cloud-init/compare/24.2...24.3.1
Potentially relevant:

https://github.com/canonical/cloud-init/pull/5536

https://github.com/canonical/cloud-init/commit/143bc9e40f7f33695216db60f73e10a900d1d1cd#diff-eb94d50ed1a0a76032438b4bc5bccb389e9cc03d6766d7881463d8ee75f21f8fR25 introduced the dependency on  nc.openbsd, but this binary seems missing on ArchLinux


Rebase all changes for HEVC to M70

This is cherry-picked from M70 commit: 49830ab5793298873341dc215d7699b3e63e61a8 : Rebase all changes for HEVC to M70.

@jianjunz Patches for iOS and Android HEVC enabling is not merged.


pm: Make device pm optional per state - V2

This is a proposal to make device power management (triggered when SoC is idle) completely optional.

Targets can select which power states should NOT  trigger device power management
If there is no power state with this property enabled, the pm subsystem won't trigger device power management
Removed the need for CONFIG_PM_DEVICE_RUNTIME_EXCLUSIVE

Notes:
This is an alternative version to https://github.com/zephyrproject-rtos/zephyr/pull/60939. This version is less intrusive and keep the current behavior. When device runtime pm is enabled, system managed device power management is disabled (can be enabled though).
In this version device pm is triggered by default and can have it disabled individually (instead of by default does not trigger device power management)
Additional context:
https://github.com/zephyrproject-rtos/zephyr/pull/60463
https://github.com/zephyrproject-rtos/zephyr/pull/60369
https://github.com/zephyrproject-rtos/zephyr/pull/60939

@JordanYates @erwango @nashif can you take a look on this please ?

folks, can I get some feedback here ? the original changes was already discussed in appropriated forum and there were no push-backs. This version is simpler and kept the current behavior but it adds more flexibility and organize device pm imho.
If there is no major block I would like to have it sooner than later to avoid regressions close to the release.

@JordanYates @erwango @nashif can you take a look on this please ?

I have no experience working with system PM, I don't feel I can provide any useful feedback.

@JordanYates @erwango @nashif can you take a look on this please ?

I have no experience working with system PM, I don't feel I can provide any useful feedback.

Sure thing. Thanks for replying it :)

Please rebase.
Some addiotinal comments: You're mentioning #60369, but I don't see a direct link, can you elaborate on this point ? It would be nice to have example of use case where it is interesting to make use of System Managed Device Power

At some point the author mentioned that some power states shouldn't trigger device power management. I don't remember exactly the full context though.
What this pr does is basically organize device power management and make clear that there are two methods, system-managed and runtime.  It keeps exactly the same current behavior (if it doesn't it is a bug and I can fix it). The additional feature is just providing a way to fine tuning  system-managed device pm allowing one to disable this method per power state. We could do something like:
/ {
	cpus {
		power-states {
			state0: state0 {
				compatible = "zephyr,power-state";
				power-state-name = "suspend-to-idle";
			};
			state1: state1 {
				compatible = "zephyr,power-state";
				power-state-name = "standby";
				zephyr,pm-device-disabled;
			};
			state2: state2 {
				compatible = "zephyr,power-state";
				power-state-name = "standby";
			};
		};
	};
};

&cpu1 {
	cpu-power-states = <&state0 &state1>;
};
&cpu0 {
	cpu-power-states = <&state0 &state2>;
};

In this example only in the core devices will be suspended when the cpu transition to standby.
That is just to give an idea, the idea is that one can just disable device power management in any state that makes sense to their target.

@erwango ping :)

@erwango done. Can you take a look again please ?

@erwango thanks a lot for reviewing it. Have updated it with the suggestions. Would you mind look it again ?


create-react-app sass sourcemaps not working

Sass sourcemaps shows only on yarn build
Can we have sourcemaps enabled by default in development ! yarn start
Environment
Node: v11.1.0
yarn: v1.12.1
npm: v6.4.1
Chrome: v70

Any estimate for an official fix on this? Thanks.

Any Updates on this ?
Is there a working workaround ?

I suspect the team isn't moving particularly fast on this (btw team you are doing an excellent job!), because the react approach favours component level styling over a sass approach. However if sass is being support then source maps probably should be too. I'd certainly find it useful!

Anybody have temporarily solution ?  :(

The following did work for me:

open node_modules\react-scripts\config\webpack.config.js
replace "isEnvProduction" with "isEnvDevelopment" for the css-loader, css-module loader, sass loader and sass module loader
start development process with "npm start"

The following did work for me:

open node_modules\react-scripts\config\webpack.config.js
replace "isEnvProduction" with "isEnvDevelopment" for the css-loader, css-module loader, sass loader and sass module loader (between lines 443 - 500)
start development process with "npm start"

@agairing Those changes would be lost on every npm install so I would advice against ever editing anything inside node_modules

@NotAmaan Right. It's just intended as a temporary solution (if you need working source maps - like myself....).

@agairing That worked fine, Thank you 👍
@NotAmaan you could copy/paste webpack.config.js after every npm install 😂
or use node-sass-chokidar
"devDependencies": {
    "gh-pages": "^2.0.1",
    "node-sass-chokidar": "^1.3.4",
    "npm-run-all": "^4.1.5",
},
"scripts": {
    "build-css": "node-sass-chokidar src/assets/scss/ -o public/static/css --source-map=true --output-style=compressed",
    "watch-css": "npm run build-css && node-sass-chokidar --source-map=true --output-style=compressed src/assets/scss/ -o public/static/css --watch --recursive",
    "start-js": "react-scripts start",
    "start": "npm-run-all -p watch-css start-js",
    "build-js": "react-scripts build",
    "build": "npm-run-all build-css build-js",
    "test": "react-scripts test",
    "eject": "react-scripts eject",
    "predeploy": "npm run build",
    "deploy": "gh-pages -d build"
  }

you need to add <link rel="stylesheet" href="./static/App.css"> to the public/index.html

bump.

I tried the solution from @agairing - but the source maps all point to main.scss and not the individual scss files. So there is still something missing.

I just saw, that there are also 2 more spots in the "webpack.config.js" configuration file where I did replace isEnvProduction with isEnvDevelopment:

This is fixed in the latest release.

This will be reverted because of #6399.

Any news on this?

latest version can't work , but 2.1.5 can work.

@hqman So, no plans on bringing back Sourcemaps in an upcoming update? Is there a workaround in the current version?

A workaround would be very important for us !

Any official word on this? thanks!

Do we have any updates on this?

This will only be available after https://github.com/webpack/webpack/issues/8910 is resolved, please follow along there.

How are we in 2019 and there isn't a steadfast solution to this? This is one of the staples when debugging css issues.

Would it be ok to have SCSS source maps as opt-in in dev mode via an environment-variable until #8910 is resolved? I could create a MR.
Then developers could at least chose between SCSS source maps and working JS breakpoints.

It not just the sass, the css also inline the  page, this is difficult to debugger.

Is there any way to link this app.css file?

Our team is also interested by a workaround, it will be very useful !

Would love to have this functionality on a current project

You can override the configuration by installing CRACO (https://github.com/sharegate/craco) in connection with the attached config files. Please note that this will enable sourcemaps in all circumstances, also in production builds:
craco.config.js
const sassSourcemapsPlugin = require("./craco-plugin-sass-sourcemaps");
module.exports = {
plugins: [
{ plugin: sassSourcemapsPlugin }
]
};
craco-plugin-sass-sourcemaps.js
module.exports = {
overrideWebpackConfig: ({ webpackConfig, cracoConfig, pluginOptions, context: { env, paths } }) => {
function traverse(obj, callback) {
if (Array.isArray(obj)) {
obj.forEach(item => traverse(item, callback));
} else if ((typeof obj === 'object') && (obj !== null)) {
Object.keys(obj).forEach(key=>{
if (obj.hasOwnProperty(key)) {
callback(obj, key);
traverse(obj[key], callback);
}
})
}
}
    traverse(webpackConfig, (node, key) => {
        if (key === "loader") {
            if (
                (node[key].indexOf("sass-loader") !== -1) ||
                (node[key].indexOf("postcss-loader") !== -1) ||
                (node[key].indexOf("css-loader") !== -1)
            ) {
                if (node.options) {
                    node.options.sourceMap = true;
                }
            }
        }
    })

    return webpackConfig;
}

};

Are there any updates on this? This seems to still be an issue on Chrome even with CRA 3.0.0

Seems the PR above (https://github.com/facebook/create-react-app/pull/7114) is closed now, just posted to see if we can bring attention back to it.
After 8 months, an official word on this would be appreciated, if there is no interest in providing a fix in the short term, please make us aware.
Thank you.

Thanks for being patient and sorry for the slowness.  Personally I'm not keen on providing a solution that would cause issues when turned on even when it's behind a flag. People would just raise more issues against these problems. If you really need this feature you can use a third party solution like react-app-rewired.

Jack thanks so much for the reply!
Just to clarify from your post, a fix without breaking other stuff would not be feasible?
Also sorry for the ignorance, but how come it was working accordingly on older versions?
Has a proper fix for this issue been considered by the team at some point at all?
Thanks again.

We've attempted to release this change before, it isn't that it doesn't work (it does), but turns out it causes other significant problems like FOUC and perf degrading.  If we release the same change behind a flag, these issues will inevitably be raised again.

@bugzpodder Could you point to an upstream bug thats causing this? We could keep an eye on that to look for when it could be merged in. Source map support is one of those basic things that any web application development framework, plugin or tool should support. If it is not supported, it should be clearly mentioned in the README somewhere so people are sure what they're investing their personal/company resources in and how painful it would be to work with, don't you think?

Once other problems like #6399 no longer manifests we will revisit this issue.  Currently I am not aware of any upstream PRs that would fix any of these issues.

@bugzpodder
Can you please show an example of  How to use react-app-rewired to enable sourcemaps ?

@mostafaabobakr7 See https://github.com/facebook/create-react-app/issues/5707#issuecomment-503614767

Any estimate for an official fix on this? Thanks. (CRA 3.0.1)

@Oxygen66
I have been waiting for this to be resolved for more than half a year... Before it was resolved, we will always have to use the workaround here, but still, it is just a workaround, so it would still be better if there is an official solution as soon as possible.
This issue depends on https://github.com/facebook/create-react-app/issues/5707#issuecomment-503614767, which seems to be... promising in their 3.1 milestone (not sure about it)?

Hi all! I think I know what is going on and how to fix it.
Background
The ability to enable source maps during development was originally added in #5713 and released in v2.1.4. Unfortunately, enabling source maps during development caused a flash of unstyled content (FOUC), which was reported in #6399. To resolve that issue, support for source maps during development was removed in #6399 and released in v2.1.6.
Cause
The FOUC occured because JS rendered before CSS. JS rendered before CSS because style-loader injected <link> tags instead of <style> tags whenever source maps were enabled, and <link> tags render asynchronously when injected with JS.
Faulty Workaround
So, why ever inject <link> tags instead of <style> tags? That technique was originally used to work around a bug that preventing source maps in <style> tag from working in Chrome, but that bug was fixed in 2015.
This is why the <link> workaround was removed from style-loader in 2017, and also removed from vue-style-loader in 2016. Unfortunately, the removal never made it into the master branch of style-loader, mostly likely due to a simple branch management error.
Solution
The solution, I hope, is to share this history with the style-loader team and submit a PR to restore the original fix.
And here it is! https://github.com/webpack-contrib/style-loader/pull/383

@jonathantneal that's awesome!  Appreciate your effort here and hopefully we can find a resolution for this soon!

A couple updates

I am working with a maintainer of style-loader to get this merged very soon, and I am told that it is now prioritized.

Good news; this change will incidentally reduce repaints, which should improve performance during development.
For instance, I enabled paint flashing in order to see if there would be any impacts from switching from the Link Blob (<link href=CSSBLOB />) strategy to the Inline Style <style>CSS</style> strategy.
When I changed the color of some text, the Link Blob strategy sometimes caused the text and any of its containers affected by the same style sheet to unnecessarily repaint. When using the Inline Style strategy, only the text was repainted, and there were no additional, unnecessary repaints. 😄

I have an updated version of @zaderac's craco snippet. Here's my craco.config.js:
module.exports = {
  plugins: [{
      plugin: require('craco-plugin-react-hot-reload')
    },
    {
      // "craco-plugin-sass-sourcemaps" inline https://github.com/facebook/create-react-app/issues/5707#issuecomment-503614767
      plugin: {
        overrideWebpackConfig: ({
          webpackConfig,
          cracoConfig,
          pluginOptions,
          context: {
            env,
            paths
          }
        }) => {
          function traverse(obj, callback) {
            if (Array.isArray(obj)) {
              obj.forEach(item => traverse(item, callback));
            } else if (typeof obj === 'object' && obj !== null) {
              Object.keys(obj).forEach(key => {
                if (obj.hasOwnProperty(key)) {
                  callback(obj, key);
                  traverse(obj[key], callback);
                }
              });
            }
          }

          traverse(webpackConfig, (node, key) => {
            if (key === 'loader') {
              if (
                node[key].indexOf('sass-loader') !== -1 ||
                node[key].indexOf('postcss-loader') !== -1 ||
                node[key].indexOf('css-loader') !== -1
              ) {
                if (node.options) {
                  if (node[key].indexOf('sass-loader') !== -1) {
                    // adds /* line 88, src/app/foo.scss */ comments in sourcemaped css output
                    node.options.outputStyle = 'expanded';
                    node.options.sourceComments = true;
                    node.options.outFile = './css/theme.css';
                  }
                  node.options.sourceMap = true;
                }
              }
            }
          });

          return webpackConfig;
        }
      }
    }
  ],
  eslint: {
    // make cra read .eslintrc file
    mode: require('@craco/craco').ESLINT_MODES.file,
    loaderOptions: {
      // with this formatter with iTerm2/Guake/etc you can cmd+click
      // eslint warnings and it's open the file in your editor at the
      // specified line number!
      formatter: require('eslint-formatter-compassion')
      // eslint-formatter-friendly is also awesome
    }
  }
};

We merged style-loader in #7473, so I think we may be able to re-try merging #5713. Anyone interested should give it a shot.

So to officially move this forward does someone need to make a pull request that re-applies the changes from #5713?

@zhuoli99 Would you consider resending your PR to fix this issue? Can be quite a pain for quite a lot of people.

Would it violate any etiquette/rules (spoken or unspoken) if someone besides @zhuoli99 made a pull request that re-applies the changes from #5713?

@PsiRadish No, you're fine, just validate that the issue that caused it to be reverted is actually fixed! I'll commit to reviewing :)

Alternatively, you may use this script to manipulate the webpack config - doesn't require CRACO or its huge config.

add this script to scripts/enable-css-sourcemaps.js

const { writeFileSync, existsSync, readFileSync } = require('fs');

const path = 'node_modules/react-scripts/config/webpack.config.js';

const find = /(sourceMap: isEnvProduction && shouldUseSourceMap)/g;
const replace = 'sourceMap: isEnvDevelopment && shouldUseSourceMap';

if (existsSync(path)) {
  const buffer = readFileSync(path)
    .toString()
    .replace(find, replace);

  try {
    writeFileSync(path, buffer);
    console.info('enable-css-sourcemaps: active');
  } catch (e) {
    console.error(`enable-css-sourcemaps: ${path} manipulation failed!`);
  }
} else {
  console.warn(`enable-css-sourcemaps: ${path} does not exist`);
}

add this script to your package.json scripts:
"postinstall": "node ./scripts/enable-css-sourcemaps.js"

Hey, seems like there hasn't been any action on this thread in a while.  I just submitted a PR with (I think) the changes discussed above #8638

I think i found the issue in react-script\config\webpack-config.js
Line 503,517, 532 and 549 of style-loaders options:
{
test: cssRegex,
exclude: cssModuleRegex,
use: getStyleLoaders({
importLoaders: 1,
sourceMap: isEnvProduction && shouldUseSourceMap,
}),
// Don't consider CSS imports dead code even if the
// containing package claims to have no side effects.
// Remove this when webpack adds a warning or an error for this.
// See webpack/webpack#6571
sideEffects: true,
},
// Adds support for CSS Modules (https://github.com/css-modules/css-modules)
// using the extension .module.css
{
test: cssModuleRegex,
use: getStyleLoaders({
importLoaders: 1,
sourceMap: isEnvProduction && shouldUseSourceMap,
modules: {
getLocalIdent: getCSSModuleLocalIdent,
},
}),
},
// Opt-in support for SASS (using .scss or .sass extensions).
// By default we support SASS Modules with the
// extensions .module.scss or .module.sass
{
test: sassRegex,
exclude: sassModuleRegex,
use: getStyleLoaders(
{
importLoaders: 2,
sourceMap: isEnvProduction && shouldUseSourceMap,
},
'sass-loader'
),
// Don't consider CSS imports dead code even if the
// containing package claims to have no side effects.
// Remove this when webpack adds a warning or an error for this.
// See webpack/webpack#6571
sideEffects: true,
},
// Adds support for CSS Modules, but using SASS
// using the extension .module.scss or .module.sass
{
test: sassModuleRegex,
use: getStyleLoaders(
{
importLoaders: 2,
sourceMap: isEnvProduction && shouldUseSourceMap,
modules: {
getLocalIdent: getCSSModuleLocalIdent,
},
},
'sass-loader'
),
},
// "file" loader makes sure those assets get served by WebpackDevServer.
// When you import an asset, you get its (virtual) filename.
// In production, they would get copied to the build folder.
// This loader doesn't use a "test" so it will catch all modules
// that fall through the other loaders.
{
loader: require.resolve('file-loader'),
// Exclude js files to keep "css" loader working as it injects
// its runtime that would otherwise be processed through "file" loader.
// Also exclude html and json extensions so they get processed
// by webpacks internal loaders.
exclude: [/.(js|mjs|jsx|ts|tsx)$/, /.html$/, /.json$/],
options: {
name: 'static/media/[name].[hash:8].[ext]',
},
},
sourcemaps never get enabled in developement environement.
why **shouldUseSourceMap** variable isn't enough for sourcemaps control?
FIX:
modify those lines as:
sourceMap: shouldUseSourceMap
just get rid of isEnvProduction.

This fixed it for me for the moment. How can i avoid this problem in future projects?


How can I log between revision ranges?

The git log documentation mentions revision range where I can do git log hash1..hash2 to get all commits between those two. Is it possible to do this with git-log-parser and if it is, how?

Inspected the code and it should be doable by log.parse(['hash1..hash2']) but I get no output when doing that. If I execute the same command in the terminal commits are listed...

Might be able to do it with {_: 'hash1..hash2'}. Been a while since I've touched this though. If that's not it I can't help past that. Would welcome a docs PR if you figure it out.

That was it. Thanks!

:+1:


applying material at runtime

The following issue is currently a major problem in our project.
To play videos on textures, we need to apply a special material that supports external textures.
The material is pre-compiled via the matc-tool in the correct version and provided as Android resource, as seen in the code example.
The renderable is a loaded GLB model and successfully displayed in the scene.
Material.builder()
   .setSource(getContext(), R.raw.video_material)
   .build()
   .thenAccept(material -> {
      getRenderable().setMaterial(material);
      material.setExternalTexture("videoTexture", videoTexture);
   })
   .exceptionally(throwable ->  {
      throwable.printStackTrace();
      return null;
   });

However, the new material is not applied.
The visuals of the rendered model don't change at all.
No Exception or other error occurs.
It seems the material change by setMaterial() is simply ignored.
How can materials be set on renderables at runtime?
Note: We used a similiar approach in older Sceneform-versions by Google, but there the material was set in the SFA/SFB-import-process in build.gradle, so we never had to change materials at runtime.
I don't see a way to change the material of GLBs in the same way. Or is that possible instead?
Tested on version 1.18.11.

See the video-texture sample

You must apply the material to the ‘node.getRenderableInstance()‘ not to the model.

Ahh, thanks, that did the trick.
So, just for info, what is the difference between a renderable and the renderableInstance on a node?
Does the node create a copy of the renderable when it is applied?

‘RenderableInstance’ is like its name says : an ‘Instance‘ = no duplicate gltf parsing = Runtime costs minimized in a consuming context.


Clean Rules Directory

When I was reviewing code in order to see what rules were already
available, I was a bit confused regarding which classes were rules and
which were implementation details when I saw names such as ‘RuleBase’,
’ConfigurableRuleBase’,
This moves base classes and interfaces into a ‘Rules/Contracts’
directory. The remaining classes directly in the ‘Rules’ directory are
callable rules.
All changes have passed muster with the existing unit tests.

I moved the interfaces to separate directory as you suggested. Since your commit currently conflicts somehow with the existing implementation, I quickly rewrote it. But I used "Interfaces" as directory name, since I feel it is too abstract to call it Contract. Interface is the technical description of a contract between classes, so I'd like to stick with Interfaces :-)
But thank you for your valuable suggestion.
Another thing completely different from this issue:
Can you please use a clean branch for your PRs, because there are always those old commits for the beautified error messages. This makes Code Reviews much harder.
Thank you
Markus

Thanks. I've been learning GitHub as I go. I think I've got the whole branch thing figured out. ;)


Remove the expeditor config for chef infra server 13 pipeline

We will no longer be releasing a Chef Server 13. Remove the buildkite pipelines defined for the same.
Acceptance Criteria:
No chef-server 13 pipelines run in buildkite.
Aha! Link: https://chef.aha.io/features/SH-3023

This was done


Box component not rendered properly

Boxes are not showing as expected ( https://adminlte.io/docs/2.4/boxes) eg: white background.
I attached the style I am getting.
Do you have any idea if I am missing something?

You try the AdminLT v2 boxes example, but you need to use the AdminLTE v3 card examples from here

Thank you a lot! I am sorry, had the previous version bookmarked and did not notice I was not looking at the latest version.
Thank you a lot for the quick and kind help and for maintaining this great package!.  I really like it a lot, keep up the great work!
Thank you again to you and all the maintainers :D


Handle eventally consistent blob lists in storage ITs

This PR tries to make tests that involve listing blobs less fragile.
It adds a timeout to such tests and makes them wait for the list to be of the expected size. If the expected size is never reached the test fails due to the timeout.
After the size is reached the tests check for the proper blobs to be in the list.
We could consider removing timeout+size-check but that would make the tests pass also when an empty list is returned.

Looks good. Feel free to merge with or without my suggestion.


FieldValue.serverTimestamp() is not currently supported inside array

Xcode version: 9.3
Firebase SDK version: 4.13
Firebase Component: Firestore
Component version: 0.11.0

I am trying to update a document within a transaction and I'm calling
transaction.updateData(editedList, forDocument: listRef)

where editedList is a Dictionary and listRef is a DocumentReference to the appropriate list.
The contents of the editedList dictionary are as follows:
let editedList:[String:Any] = [
                                    "title": newTitle, // String
                              "description": newDescription, // String
                                     "tags": newTagsDictionary, // Dictionary of [String:Any]
                                 "listType": newListType, // String
                             "hasListImage": hasListImage, // Bool
                                "updatedAt": FieldValue.serverTimestamp()
        ]

If I include the last argument, my app crashes with the following error:

*** Terminating app due to uncaught exception 'FIRInvalidArgumentException', reason: 'FieldValue.serverTimestamp() is not currently supported inside arrays'

However, there are no arrays being used in this case so I'm not sure if this is a bug or something I am doing incorrectly.  I have another section of code where I call setData and include the same fields and the serverTimestamp and it does not create any issues.  I also have another section of code that uses updateData and includes just two key/value pairs (one of which is serverTimestamp) without any problems.
For now, I'm getting around the issue by removing the "updatedAt":FieldValue.serverTimestamp() argument from my editedList dictionary, calling updateData(editedList...), and then doing a second call with just updateData("updatedAt": FieldValue.serverTimestamp()) and this seems to work.  But I'm assuming this will double my write operations and cost me more over time, so it would be useful if the bug could be fixed.
Thanks,
Kent

I was unable to reproduce this error with the following code against the 4.13.0 Firebase iOS SDK:
    let editedList:[String:Any] = [
      "title": "new title", // String
      "description": "new description", // String
      "tags": ["tag": "value"],
      "listType": "new list type", // String
      "hasListImage": true, // Bool
      "updatedAt": FieldValue.serverTimestamp()
    ]

    db!.runTransaction({ (txn, error) -> Any? in
      txn.updateData(editedList, forDocument:self.db!.collection("foo").document("bar"));
    }) { (result, error) in
      print("Transaction completed: \(error)")
    }

The transaction succeeded and the expected values (including the server timestamp) showed up in the Firebase Console data viewer. Could you provide more detail on how you are reproducing this issue?

Here is some example code, with the problematic line being the last key/value pair in the "editedItem" dictionary:
let editedItem:[String:Any] = [
                            "title": newTitle as Any, // String
                      "description": newDescription as Any, // String
                             "tags": newTagsDictionary, // Dictionary with String:Bool
                     "hasItemImage": hasItemImage, // Bool
                      "updatedAt": FieldValue.serverTimestamp()
]

db.runTransaction({ (transaction, errorPointer) -> Any? in
            let listDoc: DocumentSnapshot
            do {
                try listDoc = transaction.getDocument(listRef)
            } catch let fetchError as NSError {
                errorPointer?.pointee = fetchError
                return nil
            }

            guard let orderedItems = listDoc.data()?["orderedItems"] as? NSMutableArray else {
                let error = NSError(
                    domain: "AppErrorDomain",
                    code: -1,
                    userInfo: [
                        NSLocalizedDescriptionKey: "Unable to retrieve orderedItems from snapshot \(listDoc)"
                    ]
                )
                errorPointer?.pointee = error
                return nil
            }

            //add new item to "Items" collection
            transaction.updateData(editedItem, forDocument: itemRef)
            // transaction.updateData(["updatedAt": FieldValue.serverTimestamp()], forDocument: itemRef) // this row is necessary after removing "updatedAt" from the editedItems dictionary

            //update orderedItems array within the Lists document
            for item in orderedItems {
                if (item as! NSDictionary).value(forKey: "itemID") as! String? == self.itemID {
                    (item as! NSDictionary).setValuesForKeys(editedItem)
                    break
                }
            }
            transaction.updateData(["orderedItems": orderedItems, "updatedAt": FieldValue.serverTimestamp()], forDocument: listRef) // this reference to "updatedAt" works fine

            return nil
        }) { (object, error) in
            if let error = error {
                print("Transaction failed: \(error)")
            } else {
                //Transaction successfully committed
                self.progress.animate(toAngle: 360, duration: 0.2, completion: nil)

                DispatchQueue.main.asyncAfter(deadline: .now() + 0.3) {
                    self.dismiss(animated: true, completion: nil)
                }
            }
        }

@axiom-media Ahh...  Yes, it looks like you are storing FieldValue.serverTimestamp() inside an updatedAt field that's part of a dictionary that's stored in your orderedItems array, and as the error says, FieldValue.serverTimestamp() is not currently supported in arrays.  We will hopefully relax this in the future, but currently it is not feasible (FieldValue.serverTimestamp() is implemented by "transforming" a specific field in your data, but the wire protocol currently doesn't have a way to reference specific fields within an array, so there's no way to apply the server timestamp once you are inside an array).
Sorry for the inconvenience, but this is currently a known limitation.

@mikelehen thanks for your reply.  This was a silly oversight on my part as I forgot I was using "editedItem" for two purposes (one inside an array and one outside) and was convinced the error was coming from the second case (i.e. outside an array).  Sorry about that!

@axiom-media No worries! Glad we could get it resolved. :-)


Named slot inside ai-dialog not working.

I'm submitting a bug report

Library Version:
<EMAIL_ADDRESS><EMAIL_ADDRESS>
Please tell us about your environment:

Operating System:
Windows 10

Browser:
Chrome 58

Language:
TypeScript

Current behavior:
I've created a custom element for dialogs and tried to use named slots inside like this:
<template>
  <ai-dialog-body>
     <slot name="dialog-body">BODY_CONTENT</slot>
  </ai-dialog-body>
</template>

But the slot is never filled. Even the fallback content "BODY_CONTENT" is never filled.
Workaround
If I surround the slot with span like this, everything is working.
<slot name="dialog-body">BODY_CONTENT</slot>

Not dialog related.
Also I don't see it as an issue. When using a custom element and adding a slot, with fallback content, as a direct child of it, you should do it to target a slot in that custom element - more here.
<my-element>
  <slot slot="slot-name-inside-my-element">new fallback content<slot>
</my-element>

Wrapping it in another element, in your case , works since that element, with its content, gets projected into the default slot of <ai-dialog-body>, creating the dialog-body slot inside it.
@PWKad Do you see anything wrong with the explanation?


My kingdom for a helicopter that works like plane?

In the wildfire business a good majority of the critical aircraft are rotary wing (Helicopters) This Map Node works great for wildfire Flight Following applications except I have to use planes to show helos, or I have to use my own icons which dont follow the heading like the plane icon, SO I guess Im asking for a helicopter icon (from the top) or else allow the direction to function on a custom icon.

Thank you for all the work you have done on this very cool node!

nice idea - will see what I can find. simple svg best if you have any you can point at.

thats great! I use this, and color it based on if its in the air or on the ground, but should work for you
https://www.dropbox.com/s/9tfrk61idko17tg/aff-rw-ground.svg?dl=0

Found this simple one ? - OK ?

pushed to npm as part of 2.0.4-beta

Looks great :D I will give that a go!

Works! Thank you!!!


fix: oxc_define

#7640  👈 (View in Graphite)
main

This stack of pull requests is managed by Graphite. Learn more about stacking.


In a densely mapped area, it's hard to pan the map

Description
Often you would accidentally drag a node instead.
By the way, JOSM has a warning when you drag a node more than a certain distance. This has saved me from unintended bad edits multiple times.
Version
2.00-alpha.3.3
What browser are you seeing the problem on? What version are you running?
Chrome v109.0
Steps to reproduce
No response
The browser URL at the time you encountered the bug
https://mapwith.ai/rapid-v2-alpha3#background=Bing&datasets=fbRoads,msBuildings&disable_features=boundaries&map=17.16/50.73303/7.09840

Yeah this is something I've wanted to improve for years, and every time it makes editing harder. 😭
I know this isn't a perfect solution but - you can do 2-finger panning on a Mac trackpad to pan the map around.  (Browsers convert this gesture to a wheel event which we can respond to).
Most Mac users have been conditioned to pan this way, but it's not universal, and also people switching from JOSM probably wouldn't know to try it.
This is frustrating too because I really thought we were training users about "2 finger panning" in the intro walkthrough, but I just checked and it is not mentioned. 😢

In JOSM you pan the map by holding RMB. I find this works well for mouse users like me. 2-finger panning on trackpad works in JOSM as well (but you have to "click" as well, not sure if that is because of a system gesture setting)

In 3ac0bbe14 I just made a change so that now if you drag while holding the right mouse button, it will only pan the map, not drag nodes.  I think this matches how JOSM works?
I'm going to leave the issue open for now - want to try it for a while and see if this feels better.

BTW there is still an issue where if the user is dragging the map with the right mouse button and releases it out of the window, we never get the pointerup and the map keeps dragging.  I don't know why - performing map drags with the left mouse button doesn't seem to have this issue.

In 3ac0bbe I just made a change so that now if you drag while holding the right mouse button, it will only pan the map, not drag nodes. I think this matches how JOSM works?

That does sound like the JOSM behavior, yes.


libev check broken

./configure is saying I need libev >= 4, but I have it:
./configure: line 13376: syntax error near unexpected token `libev,'
./configure: line 13376: `              PKG_CHECK_MODULES(libev, libev >= 4.0, :, :)'

This is a syntax error.
I would try to restart the installation :
make clean can help to clean previous builds.
autoreconf -f -i can rebuild your configure file.
https://github.com/ZmnSCPxj/clboss#installing

Didn't work.

Did you attempt this on a git checkout?  If so, you might not have the autoconf-archive, which is what contains PKG_CHECK_MODULES.
In properly generated configure there is no line with PKG_CHECK_MODULES, as that should only exist in configure.ac and be translated if you have autoconf-archive installed.

Yes, I tried it on a git checkout, and I tried the autoconf thing as there was no configure file.

Next time I will try downloading an archive from a release.

Looking again, PKG_CHECK_MODULES is installed as part of pkg-config, not autoconf-archive, at least on Debian.
Do note that README.md lists pkg-config as a dependency, so still not a bug. https://github.com/ZmnSCPxj/clboss#dependencies

That was it. Installing pkg-config fixed it. Sorry for the trouble.