fix[live-md bump]: scroll to new line after hit Enter key

Details

Fixed Issues

$ https://github.com/Expensify/App/issues/46389
PROPOSAL: https://github.com/Expensify/App/issues/46389#issuecomment-2255658889
Tests

Go to NewDot app
Click on the Green plus Icon
Click on Assign task
Insert a sample title
Click on Description
Insert multiple-line text until a scroll bar is shown on the right
On a new line insert a markdown text (eg. bold)
Hit the enter key on the keyboard

Verify that: When hitting the enter key after a mark down the new line becomes visible with the cursor seen visibly

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

Offline tests

QA Steps

Go to NewDot app
Click on the Green plus Icon
Click on Assign task
Insert a sample title
Click on Description
Insert multiple-line text until a scroll bar is shown on the right
On a new line insert a markdown text (eg. bold)
Hit the enter key on the keyboard

Verify that: When hitting the enter key after a mark down the new line becomes visible with the cursor seen visibly

[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 either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
[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(theme.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 the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:

[x] I verified that all the inputs inside a form are aligned with each other.
[x] I added Design label and/or tagged @Expensify/design so the design team can review the changes.

[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

Android: Native

https://github.com/user-attachments/assets/8c64f12a-561e-4498-8517-20f0f44a72d2

Android: mWeb Chrome

https://github.com/user-attachments/assets/5005d24f-8edd-4b64-a3e5-0990a9b95fee

iOS: Native

https://github.com/user-attachments/assets/96b0394e-fd9d-4ff1-a6b1-30f0d12885b7

iOS: mWeb Safari

https://github.com/user-attachments/assets/6ad3dbf6-3487-460f-a6e6-80583e36e19e

MacOS: Chrome / Safari

https://github.com/user-attachments/assets/e87737fa-73a1-4173-a95f-7a40c2f025b3

MacOS: Desktop

https://github.com/user-attachments/assets/e87737fa-73a1-4173-a95f-7a40c2f025b3

Hi, I've already bumped the version of the Live Markdown for web to 0.1.117 in this PR that is already merged. This version contains huge web implementation refactor changes. We modified the logic and structure behind the Live Markdown component.
I will add your test steps to my PR to make sure that the issue that you worked on is also fixed :D

Yes @dominictb, I think we can close this PR as it has already bumped to the latest version in the other PR.


Naming scheme for channel ranges

At the moment I am using the following naming scheme to indicate channel ranges when forming images with only a subset of channels:
SB59058.RACS_1626-84.beam18.round4.i.ch96-97

This would be supplied to the imager (wsclean -name) and output products would be formed around this prefix (e.g. the ImageSet will have its prefix set to this).
Two problems:

the scheme itself may not be the best. These should at the very least be zero-padded. There is a question around whether we want a range, or simply have the starting index. My feeling is the channel range may be useful in the future should we want to image multiple channels at a time, instead of a single. Same thought around doing the time-range imaging
The regex's that are used to separate the wsclean added naming components, and the general flint name parser both need to be expanded to recognise this chNNNN-NNNN field, should it be present. I believe it is this point that is creating files with names like:

SB59058.RACS_1626-84.beam18.round4.i.ch96-97-image.optimal.image.fits

in the spectral line workflow

@AlecThomson may have strong feelings on point 1.

Addressed as part of #196


Hab2 fixup : merging main and resolving conflicts

Motivation and Context

How Has This Been Tested

Types of changes

Docs change / refactoring / dependency upgrade
Bug fix (non-breaking change which fixes an issue)
New feature (non-breaking change which adds functionality)
Breaking change (fix or feature that would cause existing functionality to change)

Checklist

[ ] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have read the CONTRIBUTING document.
[ ] I have completed my CLA (see CONTRIBUTING)
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

May want to merge main again for the fixed mypy checks.

@vincentpierre Shouldn't this PR be tagged as [v0.2.3]?


Mark IndexerExecutionStatus.endTime x-nullable

Fixes live test run issues

/azp run net - search - tests

I also opened https://github.com/Azure/azure-rest-api-specs/issues/10226 to track getting the swagger fixed.


support for 0.90

@cliffordwolf
Hi Clifford, this pull request adds the support for all instructions covered as part of the 0.90 specification
Thx
Lee

Missed one reference to 0.37 Draft specification


Issue #89 - Added cat API documentation

Issue #89 - Add cat API documentation
Added a quick reference for cat API endpoints and a document listing common supported units.
Future work could/should include documenting all possible columns for each cat API endpoint.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Hi @oddlittlebird, this PR is so similar to the documentation from Elastic that I'm not comfortable merging it. I'm going to merge https://github.com/opendistro/for-elasticsearch-docs/pull/119. I encourage you to find content missing from https://github.com/opendistro/for-elasticsearch-docs/pull/119, rewrite your work here, and submit another PR. You've got a lot of useful content, but it needs to be original work based on testing rather than lightly tweaked versions of what Elastic offers.


kojiapi: ability to cancel compose

Currently there is no API to cancel a compose. But there is the ability to cancel a task in koji, which should then cancel the compose.

Makes sense. Under the hood we support cancellation, just a matter of hooking it up.


fix-49974-attachment-infinite-loading

Note : this PR is a follow up of PR https://github.com/Expensify/App/pull/50511 to avoid force pushing the branch. Please referer to PR https://github.com/Expensify/App/pull/50511 for all discussions prior creation of this PR
Details

Fixed Issues

$ https://github.com/Expensify/App/issues/49974
PROPOSAL: https://github.com/Expensify/App/issues/49974#issuecomment-2389704800
Tests

Launch the app.
Open a chat
Paste the text
Send the message
Click on the image
Verify that an icon and the text "No Attachment Found" are displayed

[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 either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
[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(theme.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 the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:

[x] I verified that all the inputs inside a form are aligned with each other.
[x] I added Design label and/or tagged @Expensify/design so the design team can review the changes.

[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

Android: Native

https://github.com/user-attachments/assets/5725c05c-3b5b-4ebb-ae35-424fbb3aef34

Android: mWeb Chrome

https://github.com/user-attachments/assets/7425877e-2d24-469c-8ea6-2259c3124a2a

iOS: Native

https://github.com/user-attachments/assets/98906f54-cac9-4800-b59d-53819a1a9965

iOS: mWeb Safari

MacOS: Chrome / Safari

https://github.com/user-attachments/assets/a0138782-b3c7-419f-a0be-7c3ac01a5dfc

MacOS: Desktop

I have read the CLA Document and I hereby sign the CLA

@dubielzyk-expensify this is the PR replacing PR https://github.com/Expensify/App/pull/50511. You can refer to this comment for more context https://github.com/Expensify/App/pull/50511#issuecomment-2461793516.

@hoangzinh yes i did some web tests.I will do some mobile tests also but i think we can keep the same screenshots and videos as it's the same, dont you think ?

This looks right to me. I'll let @dannymcclain gut check as he did the design for it. cc @shawnborton too

Yup, I dig it 👍

Looks like we have some ESLint errors:

@hoangzinh @MariaHCD sorry my computer had some issues with its network driver since this morning

Looks like this PR hasn't touched those files.

yes i confirm so
Also yes, merging the lastest main will fix the issue. I will do it right away.

@MariaHCD @hoangzinh the failure is from a file currently present on the main branch. Our PR didnt change that file. If it's there it means they bypass that ESlint check right ? If that's the case, can we do the same ?

Ideally, it would be good to fix it in this PR. Although I do agree, this PR hasn't really touched that file so not super sure why the ESLint error is being triggered.
In any case, we can merge this and handle the migration to useOnyx in this separate issue: https://github.com/Expensify/App/issues/52459

The migration to useOnyx will be handled in a separate issue: https://github.com/Expensify/App/issues/52459

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

@MariaHCD @hoangzinh i see the deployment on staging ios and hybrid envs have failed. Is there anything i can do to help ? I use to delete the whole node-modules folder and relauch an npm install when i encounter errors like that ie related to the application of patches, i dont know if that could help


Usage: Fruits and Vegetables

Matthew comments:

Yet another issue to think about (last one on this thread, promise)
revolves around is the notion that we need to define foods differently
depending on the context which they occur. A simple example of this is
the tomato https://en.wikipedia.org/wiki/Nix_v._Hedden. Botanically,
it is a fruit, yet for legal purposes in the United States and elsewhere,
it is considered a vegetable, legally. The reason for this is that
fruits--those sweet fruiting bodies from a plant--were generally considered
a delicacy, and taxed at a higher rate. tomatoes were considered to be
eaten with the meal, and therefor not taxed as heavily.

So the multiple categorizations of a particular food source arise in this case from "bending the rules", a colloquial usage in this case in favour of vegetable over fruit.  I've taken a peek at what ENVO has to say:
vegetable and fruit, and see the provisio:

editor note: This class represents a somewhat arbitrary grouping of plant products which varies along various axes (socio-political, economic, cultural, etc). It's likely we'll need to create more informative subclasses and use synonomy to tie them together.

So we're looking at annotating a [food item] "member of" ["vegetable"] relation probably, along taxonomic, cultural, legal etc. dimensions?

https://en.wikipedia.org/wiki/Nix_v._Hedden. Botanically, it is a
fruit, yet for legal purposes in the United States and elsewhere, it
is considered a vegetable, legally. The reason for this is that
fruits--those sweet fruiting bodies from a plant--were generally
considered a delicacy, and taxed at a higher rate. tomatoes were
considered to be eaten with the meal, and therefor not taxed as
heavily.

I believe for this, the best way will be to have two separate classes,
"vegetable (sensu botany)" and "vegetable (sensu law)" which will be
different. GO used to have these "sensu" classes a lot but mostly got
rid of them (no idea why), but we will likely need them or at least a
similar mechanism.
Rob.
--
BitMessage: BM-2cXWLPcqKLrdfGNHpBDgTxDNHKGTGb2mhz
PGP: 50D0 AF17 F0D1 873A 94B7  B232 81C3 CFA7 E090 F6A2

Sounds good!

I have added "vegetable (sensu law)" http://purl.obolibrary.org/obo/FOODON_03000000, and offer up this definition: A vegetable (sensu law) is a plant food source which is botanically categorized as a fruit, but which has been legally categorized by a given jurisdiction's lawmakers as a vegetable, usually for taxation purposes.
I seeAlso the Nix_vs_Hedden case above.
I think that does it for now.  (Animal feed has its own related subclasses which can be developed further later).


feat(operator): add toPromise operator. closes #159

I didn't add a configuration option yet, because I'm still unsure where we're going to put that. But for now, it's the basic implementation.
It might be worth adding a custom toPromise method on ScalarObservable for performance reasons, but I have my doubts that will be game-changing for anyone.

Merging after a week with no objections.


Vickel: Watch rootkit[\W_]+hacker(?:[\W_]+firm)?

Vickel requests the watch of the watch_keyword rootkit[\W_]*+hacker(?:[\W_]*+firm)?. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

rootkit[\W_]*+hacker(?:[\W_]*+firm)? has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by Jeff Schaller in Charcoal HQ


Type narrowing with isinstance and issubclass in match statement

 Environment data

Language Server version: 2021.4.4-pre.1
OS and version: darwin x64
Python version (and distribution if applicable, e.g. Anaconda): 3.10.0a7
python.analysis.indexing: true
python.analysis.typeCheckingMode: strict

 Expected behaviour
An isinstance or issubclass call in a match statement should narrow the type just like the same call in an if statement.
 Actual behaviour

 Logs
--
 Code Snippet / Additional information

class Custom:
    pass

class Derived(Custom):
    pass

def func(cls: Custom) -> Derived:
    var: Derived
    match isinstance(cls, Derived):
        case True:
            var = cls
        case _:
            var = Derived()

    return var

This looks like an incredibly contorted use of pattern matching when this would be much more straightforward, faster to run, and easier to read:
if isinstance(cls, Derived):
    var = cls
else:
    var = Derived()

I suppose one could take any simple conditional code flow statement with a boolean test and contort it into a pattern matching statement that matches on True or False, but why?
match value == 1:
    case True:
        print("value is 1!)
    case _:
       print("value is not 1!")

This is quite different from type narrowing used for other conditional statements because it requires an understanding of of subject type narrowing and pattern matching. It's theoretically possible to implement this, but it would be a lot of work, and I'm far from convinced this will be generally useful. I would need to have a lot of additional evidence from many more users before I could justify that additional development and code complexity.

True, for just one boolean check I wouldn't use pattern matching. That was only the example here. Originally it looked more like this:
def func(obj: type[Custom], var: bool, arg: int) -> Derived:
    default_bar: Derived
    list_bar: list[Derived] = []
    default_foo: Custom
    list_foo: list[Custom] = []

    match issubclass(obj, Derived), var:
        case True, True:
            default_bar = obj(arg)
        case True, False:
            list_bar.append(obj(arg))
        case False, True:
            default_foo = obj(arg)
        case False, False:
            list_foo.append(obj(arg))

Of course, even that could be expressed by an if statement, but this was just a first test for what pattern matching can do.

This case would be even more complicated for type narrowing because it involves multiple subexpressions within a tuple. Pyright doesn't perform type narrowing in complex cases like this, nor does any other Python type checker, to my knowledge.
if (issubclass(obj, Derived), var) == (True, True):
    ...

I might be missing something, but isn't that the same as:
def func3(obj: type[Custom], var: bool):
    default_bar: Derived
    list_bar: list[Derived] = []
    default_foo: Custom
    list_foo: list[Custom] = []

    if issubclass(obj, Derived) and var:
        default_bar = obj()
    elif issubclass(obj, Derived) and not var:
        list_bar.append(obj())
    elif not issubclass(obj, Derived) and var:
        default_foo = obj()
    elif not issubclass(obj, Derived) and not var:
        list_foo.append(obj())

That does work with Pyright.

That's not the same. The match statement in your sample above is equivalent to:
def func(obj: type[Custom], var: bool, arg: int) -> Derived:
    default_bar: Derived
    list_bar: list[Derived] = []
    default_foo: Custom
    list_foo: list[Custom] = []

    if (issubclass(obj, Derived), var) == (True, True):
        default_bar = obj(arg)
    elif (issubclass(obj, Derived), var) == (True, False):
        list_bar.append(obj(arg))
    elif (issubclass(obj, Derived), var) == (False, True):
        default_foo = obj(arg)
    elif (issubclass(obj, Derived), var) == (False, False):
        list_foo.append(obj(arg))

Closing issue, if you have any further questions let us know.


Refactor //flutter/dev/conductor to have two frontends: cli & flutter app

This is a tracking issue for creating a new, empty Flutter app that will be an alternative UI frontend for the conductor tool.

cc @Yugue


[Question] Allow additional data to be passed in on businesses-search

I just created a new v3 client for Node (https://github.com/parisbutterfield/node-yelp). It's a fork of a v2 client.
I'm often making two API calls and the data returned is pretty much the same. I'm displaying a list of results from /businesses/search and want the hours included on each row in the list.
Example/Problem:
I make a call to https://api.yelp.com/v3/businesses/search
Then I need the hours. There's another call to https://api.yelp.com/v3/businesses/{id}
The data returned from the businesses with the id, is nearly the same as what's in the search.
Potential Solution:
Because everyone doesn't need hours or photos in the /businesses/search/. Allow for an additional query parameter that when set, can include the requested data in the response.

Hey @parisbutterfield! We're trying to find ways to add more data without compromising performance. Having parameters for what you want in a response works well to start but could get hard to manage and cause the query to become huge if too many parameters do that.
#9 covers adding hours permanently to the search endpoint


Apollo 7.0 Planning Header Timestamp Bug

Describe the bug
The planning component modifies the header timestamp after the planning trajectory has been produced, and modifies relative timestamp for each path point in the trajectory.
However, in Apollo 7.0, because variable start_time was assigned at an incorrect location (after header timestamp already changed), variable dt is always 0. As a result, planning_component incorrectly modified the planning message that should be published to CyberRT.
https://github.com/ApolloAuto/apollo/blob/463fb82f9e979d02dcb25044e60931293ab2dba0/modules/planning/planning_component.cc#L188-L194
This bug was fixed in Apollo 8.0
https://github.com/ApolloAuto/apollo/blob/3ecbf3006d9a1c3d832c3d925dc838d2d762c571/modules/planning/planning_component.cc#L188-L194
Question
Since the trajectory as part of the planning module uses timestamp relative to the header timestamp, the output trajectory are essentially equivalent from the perspective of absolute time if (1) both header and relative time changes by a constant dt, or (2) both header and relative time remain unchanged (e.g., after FillHeader, revert the change to header timestamp).
Is there a specific reason why option (1) was chosen over option (2)?

@qwetqwe I found your fix commit at 9c764ed. Do you mind providing some feedback on if I can choose to not modify the relative times in the trajectory but revert header timestamp change?
 ADCTrajectory adc_trajectory_pb;
 planning_base_->RunOnce(local_view_, &adc_trajectory_pb);
 auto start_time = adc_trajectory_pb.header().timestamp_sec();
 common::util::FillHeader(node_->Name(), &adc_trajectory_pb);

 // modify trajectory relative time due to the timestamp change in header
 // const double dt = start_time - adc_trajectory_pb.header().timestamp_sec();

 // revert header timestamp change
 adc_trajectory_pb->mutable_header()->set_timestamp_sec(start_time);


Base color not applied when going outside the dashboard

Checklist:

[x] I updated to the latest version available
[x] I cleared the cache of my browser

Release with the issue: 3.0.0
Last working release (if known): N/A
Browser and Operating System:
Windows 11 24H2 with latest Chrome Stable 131.0.6778.205
Description of problem:
Steps to reproduce:

Open any page in HA instance (like settings) by link (except for dashboard)
Base color isn`t applied :(

Normal behaviour:

Open HA dashboard
Base color is applied

Go to any page (like settings) by buttons
Base color is still applied

Additional information:
I`ve tried to include material-rounded-theme.js in frontend section of configuration.yaml, but base color stops applying even if I open dashboard. I guess it loads too early that way. :-/

Is there a specific page URL that doesn't work for you if you open it by link? Going straight to various settings pages by URL still applies the user colors for me.

I do see the styles not applying to iframes like HACS and the add-ons page, but that's a separate issue I'll have to fix.


Question: Is the code in hook_xxx behaving differently in the saved state(.cache/dein/state_[g]vim.vim) intended?

Problems summary
The following operation produced different results, with the latter unintentionally polluting the global variable.
If that is what is intended, does that mean I should do the conflict avoidance and cleanup of each variable myself?
I have checked HELP but could not confirm that this is the case.
Expected
Environment Information (Required!)

dein.vim version(SHA1): 444b333ab3908ca49ca3b22ad15e4e1c0ae712f4

OS: Windows 10 Pro 1909 18363.752

Vim/neovim version:

VIM - Vi IMproved 8.2 (2019 Dec 12, compiled Mar  6 2020 07:51:55)
MS-Windows 64 ビット GUI/コンソール 版 with OLE サポート
適用済パッチ: 1-357

Provide a minimal .vimrc with less than 50 lines (Required!)
Invoke
gvim -N -u testvimrc.vim
set runtimepath^=~/.cache/dein/repos/github.com/Shougo/dein.vim
if dein#load_state('~/.vim/rc')
  call dein#begin('~/.vim/rc', [$MYVIMRC, '~/.vim/rc/test.toml'])

  call dein#load_toml('~/.vim/rc/test.toml', {'lazy': 0})

  call dein#end()
  call dein#save_state()

endif

[[plugins]]
repo = 'Shougo/dein.vim'
hook_add = '''
for [name, value] in [['a',0], ['b', 1]]
  echo name value
endfor
'''

The reproduce ways from Vim starting (Required!)

add the following code to hook_add of optional plugins
modify the toml file or call dein#clear_cache() (disable the cache).
vim startup
Try echo name or echo value -> it says undefined.
exit and start vim (using state_vim.vim)
Try echo name or echo value -> 'b' or 1 is given.

Screen shot (if possible)
nothing.
Upload the log messages by :redir and :message (if errored)
When using lightline var, broke Lightline setting in startup time.
(rename to recover).
Error user specific, not write in it.

Fixed.
Note: hook_add was executed, but it was silent.

call dein#clear_cache()

It must be dein#clear_state().

Thanks OK.


fixes for AQCU-663

https://internal.cida.usgs.gov/jira/browse/AQCU-663
Months are not always labelled if report period does not span a full month.
https://cida-eros-aqcudev.er.usgs.gov:8443/aqcu-front-end/service/reports/correctionsataglance/?primaryTimeseriesIdentifier=7e08a86850aa46c4a6b78b3d7d271fb1&station=01047200&startDate=2013-01-15&endDate=2013-02-15
Approval period is not showing if report period is short.
https://cida-eros-aqcudev.er.usgs.gov:8443/aqcu-front-end/service/reports/correctionsataglance/?primaryTimeseriesIdentifier=7e08a86850aa46c4a6b78b3d7d271fb1&station=01047200&startDate=2013-03-01&endDate=2013-03-30
Sometimes get an error and report will not generate if report period is short.
https://cida-eros-aqcudev.er.usgs.gov:8443/aqcu-front-end/service/reports/correctionsataglance/?primaryTimeseriesIdentifier=7e08a86850aa46c4a6b78b3d7d271fb1&station=01047200&startDate=2012-12-15&endDate=2012-12-31

travis failing on unrelated problems. gsplot version is fixed on server but not in travis.

Maybe set dateLim as null by default and if it's not passed in default to something


feat(operator): zitadel and database operator

:tada: This PR is included in version 0.112.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Failed in running gradient_descent.py.

Hello, I have installed all the Software Libraries required, and removed the header (the first line of Advertising.csv), removed the ids (the first column of Advertising.csv), and then replaced the comas by tabs (real tabs, not 2/4/8 spaces). However, I still failed in running it.
PS C:\Users\DELL> & C:/Users/DELL/AppData/Local/Programs/Python/Python36/python.exe "e:/Work/2020-Summer/other/Research Project/Report/ML/from future import print_function.py"
epoch:  0 loss: 92.32078294903626
w, b:  0.7412639000000002 0.028045000000000007
Traceback (most recent call last):
File "e:/Work/2020-Summer/other/Research Project/Report/ML/from future import print_function.py", line 74, in
w, b = train(x, y, 0.0, 0.0, 0.001, 15000)
File "e:/Work/2020-Summer/other/Research Project/Report/ML/from future import print_function.py", line 60, in train
fig1.savefig('../../Illustrations/gradient_descent-' + str(image_counter) + '.eps', format='eps', dpi=1000, bbox_inches = 'tight', pad_inches = 0)
File "C:\Users\DELL\AppData\Local\Programs\Python\Python36\lib\site-packages\matplotlib\figure.py", line 2203, in savefig
self.canvas.print_figure(fname, **kwargs)
File "C:\Users\DELL\AppData\Local\Programs\Python\Python36\lib\site-packages\matplotlib\backend_bases.py", line 2126, in print_figure
**kwargs)
File "C:\Users\DELL\AppData\Local\Programs\Python\Python36\lib\site-packages\matplotlib\backends\backend_ps.py", line 831, in print_eps
return self._print_ps(outfile, 'eps', *args, **kwargs)
File "C:\Users\DELL\AppData\Local\Programs\Python\Python36\lib\site-packages\matplotlib\backends\backend_ps.py", line 851, in _print_ps
orientation, papertype, **kwargs)
File "C:\Users\DELL\AppData\Local\Programs\Python\Python36\lib\site-packages\matplotlib\cbook\deprecation.py", line 358, in wrapper
return func(*args, **kwargs)
File "C:\Users\DELL\AppData\Local\Programs\Python\Python36\lib\site-packages\matplotlib\backends\backend_ps.py", line 1076, in _print_figure
with open(outfile, 'w', encoding='latin-1') as fh:
FileNotFoundError: [Errno 2] No such file or directory: '../../Illustrations/gradient_descent-2.eps'
PS C:\Users\DELL>
How to solve this problem.
Thank you very much.

You possibly just need to create the Illustrations folder two levels above the current working directory, indicated by ../../Illustrations/ so the plots can be saved.
FileNotFoundError: [Errno 2] No such file or directory: '../../Illustrations/gradient_descent-2.eps'


Add an endpoint with the costs of system transactions

@RitaMAllenCA commented on Mon Oct 24 2022

There are a couple txn costs fixed -- wasmless transfer, delegate/undelegate. These costs are specified in the chainspec.toml and then define how much should the user pay for the specific txn. As part of the Ledger Live interagtion, these txn costs have to be either estimated (in the Ledger Live) or hardcoded. The costs are fixed so there's no need for estimation BUT, in theory, they could also change in the next version. Ledger Live needs to be aware of these changes.
We propose addition of the special endpoint where these costs would be available for the Ledger Live to query so that users of the desktop wallet can create txns with proper fees.

this doesn't make sense; i can explain why but not concisely


Note about file seek altering stream read/write mode

Hi! We've recently had an issue with file IO.
We've did a read / write operations on a file and used seekp and seekg as follows:
if (iostream.tellg() != position1) { iostream.seekg(position1); }
...do the reading
if (iostream.tellp() != position2) { iostream.seekp(position2); }
...do the writing

the problem I found is that seekg implicitly alters stream in read mode and if condition stream.tellp() != position2 is not met - stream is remains in read mode and trying to write to it results in stream error without any description. Maybe it would be nice to have a note in the documentation about seekg / seekp modifying file stream read-write mode.

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

ID: 711d2223-7a8d-1054-89b3-69b5fa3bee0a
Version Independent ID: 9009fe6b-9771-dd3a-672a-44dd639d153c
Content: Input Stream Member Functions
Content Source: docs/standard-library/input-stream-member-functions.md
Product: visual-cpp
Technology: cpp-standard-libraries
GitHub Login: @TylerMSFT
Microsoft Alias: twhitney

I don't currently have msvc nearby. We do check the stream for error right after seek like this:
if (!iostream)
	throw std::runtime_error("Stream error");

and it was OK. Error occured only on writing.
There is also was no issue when running the code on linux.
Removing condition if (iostream.tellp() != position2) for some reason fixed the problem.
I've wrongly interpret this as stream mode modification. Looking at the STL source it seems to be not the case as seekpos openmode value is ignored in basic_filebuf.
Sorry for wrong assumption.
Just in case, we compiled the project using visual studio 2015

@Vineg
Thanks for the follow-up. Since this doesn't sound like a documentation bug, I'm closing the issue here.


[QUERY]Why doesn't Azure Blob Storage support Http 2?

Library name and version
Azure.Stoage.Blobs
Query/Question
We still have yet to hear a valid reason for why after so many years Azure Blob storage REST API or SDK does not support HTTP 2.0. Dont we think it high time to move on from HTTP 1.0/1.1? Of course, we understand we can use FrontDoor to do this but that actually cost a good deal of money just baseline. So, for dev/test environments it is not a good for a budget. This question has been asked many times in threads with no clear answer. The responses are it just does not and there is no plan for it. Can we at least have an answer as to why? It really does nto make sense. For example, one impact is if a website accesses a storage account directly the lighthouse tools ding the site for now using http 2.0.
See: Http 2.0 support for Azure Blob Storage
#42828
Environment
No response

Hi @chassq.  Thanks for reaching out and for your question.  As the issue that you've linked notes, per the service documentation , the Azure Storage REST API does not support HTTP/2 .  The Azure SDK client library cannot support offer support for a protocol that the service itself does not support.
While I understand that you're interested in understanding why the service has made this decision, the maintainers of the Azure SDK do not have insight nor influence over the REST API nor the decisions made regarding its design.  Unfortunately, the team responsible for the service does not monitor this repository nor provide support here.  To ensure that the right team has visibility and can help, your best path forward for would be to open an Azure support request or inquire on the Microsoft Q&A site.   To leave a feature suggestion for HTTP/2 support, you may also want to consider the Azure Feedback site.
I'm going to close this out; if I've misunderstood what you're describing, please let us know in a comment and we'd be happy to assist as we're able.


USD -> SDF: Added model tag

Signed-off-by: ahcorde<EMAIL_ADDRESS>🎉 New feature
Summary
USD -> SDF: Added model tag
Checklist

[ ] Signed all commits for DCO
[ ] Added tests
[ ] Added example and/or tutorial
[ ] Updated documentation (as needed)
[ ] Updated migration guide (as needed)
[ ] codecheck passed (See contributing)
[ ] All tests passed (See test coverage)
[ ] While waiting for a review on your PR, please help review another open pull request to support the maintainers

Note to maintainers: Remember to use Squash-Merge and edit the commit message to match the pull request summary while retaining Signed-off-by messages.

@ahcorde I made some changes and added tests, would you mind taking a look? Here are the changes I made: https://github.com/ignitionrobotics/sdformat/pull/876/files/af2ce4c6caf2cf1a7cf7be2214de94d4a1d03800..553b93b03bbd482dd0602a2c066547aaee125a0f


Documentation for async obervables?

It doesn't appear like RxJS's map method can be async - is there another operator that is?
function main(responses) {
  return {
    DOM: responses.DOM.get('textarea.input-value', 'keyup')
      .map(SOME_ASYNC_OPERATION)
      .map(value => h('div#wrap.flex', [
          h('div.px2.py2.bg-blue.white', 'documentation.js demo')
      ])
    };
}

My usecase is running a textarea worth of input through a documentation generator and showing the result on the right side of the page. The doc generator is async (a stream), and thus results aren't immediately available. Could there be an example of a cycle.js app interacting with an async API, whether AJAX or a local library?

flatMap

flatMap isn't in rxmarbles - going to the rxjs page ⇢ [dive in!](https://reactive-extensions.github.io/RxJS/#Dive In!) ⇢ documentation ⇢ api ⇢ err, core -> observable -> flatMap
It appears that flatMap is an alias for selectMany?

Yes I know flatMap isn't in RxMarbles because it's harder to render as a dynamic diagram. ReactiveX.io is the home for rx documentation. Tip: flatMap is often the only operator you need. You can mimic delay with flatMap. You can mimic filter with flatMap. Even map itself.

Don't use the selectMany alias. It's idiomatically a secondary alias while flatMap is the primary.

flayMap +1


Appstudio update test-component-pac-jozh

Pipelines as Code configuration proposal
To start the PipelineRun, add a new comment with content /ok-to-test
For more detailed information about running a PipelineRun, please refer to Pipelines as Code documentation Running the PipelineRun
To customize the proposed PipelineRuns after merge, please refer to Build Pipeline customization

Pipelines as Code CI/test-component-pac-jozh-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
6 seconds
init

✅ Succeeded
15 seconds
clone-repository

✅ Succeeded
36 seconds
build-container

✅ Succeeded
25 seconds
deprecated-base-image-check

✅ Succeeded
25 seconds
inspect-image

✅ Succeeded
3 minutes
clair-scan

✅ Succeeded
47 seconds
clamav-scan

✅ Succeeded
17 seconds
sbom-json-check

✅ Succeeded
12 seconds
label-check

✅ Succeeded
7 seconds
show-summary

✅ Succeeded
5 seconds
show-sbom

Pipelines as Code CI/test-component-pac-jozh-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
7 seconds
init

✅ Succeeded
19 seconds
clone-repository

✅ Succeeded
26 seconds
build-container

✅ Succeeded
13 seconds
deprecated-base-image-check

✅ Succeeded
13 seconds
inspect-image

✅ Succeeded
11 seconds
clair-scan

✅ Succeeded
39 seconds
clamav-scan

✅ Succeeded
9 seconds
sbom-json-check

✅ Succeeded
20 seconds
label-check

✅ Succeeded
6 seconds
show-sbom

✅ Succeeded
9 seconds
show-summary


Clean the .eslintignore

The node_modules/ and bower_components/ will be ignored by default like described in the ESLint documentation.

Thanks!

 :)


Fix Firestore conformance tests

Fixes #5343.
This should not be merged until we've seen a spec for update transforms.

Note: using the precondition to determine whether or not to use an empty update mask may not be a good idea. It may be as simple as depending on which method is calling it (so just have an extra flag...)

Amanda: I've added an extra commit to this based on internal guidance. Please could you have a look? If you're happy, we can merge this and we're done :)


Server tokens ungeneratable

From the developer dashboard, the documentation states to simply generate a server token. Now it says you  can only generate one by "reach[ing] out to your Uber Business Development representative for server token access."
My use case requires displaying realtime info on the Uber request a ride button in my app. Any ideas on how to generate the server token required to enable this SDK?

Hi, i'm having the same problem, i need to access the /estimates endpoint, but it looks like server tokens are no longer supported. And i can't find a support contact to request access to scopes. Support account @UberDevelopers seems inactive.

Good night, I'm the same exposing problem with login in my application, can someone tell me the solution?


feat: Exhaustive greedy rewrite strategy

This is a straight combination of the greedy and exhaustive strategies. Instead of applying each strategy separately, apply each one once but also include all the following strategies that do not modify the same nodes.
This is a draft, since for some reason combining multiple strategies at once is invalidating the hugr.
They may not be correctly reporting their modified nodes ?

This requires https://github.com/CQCL/hugr/pull/600 to check whether the rewrites are non-overlapping.
We get really nice results.
On my laptop, 1 thread, barenco_tof_10, 60s timeout, queue size 500:
Base cost: 192 CX gates, 326 gates.

Using HEAD:

With this branch:

Min cost: (120, 260)


error: request to https://[STORE].myshopify.com/admin/api/unstable/themes/166797738292.json?fields=id%2Cname%2Crole%2Cprocessing failed, reason: connect ECONNREFUSED <IP_ADDRESS>:443

Please confirm that you have:

[X] Searched existing issues to see if your issue is a duplicate. (If you’ve found a duplicate issue, feel free to add additional information in a comment on it.)
[X] Reproduced the issue in the latest CLI version.

In which of these areas are you experiencing a problem?
Theme
Expected behavior
shopify theme dev should work as normal.
Actual behavior
Instead I get an error: error: request to https://[STORE].myshopify.com/admin/api/unstable/themes/166797738292.json?fields=id%2Cname%2Crole%2Cprocessing failed, reason: connect ECONNREFUSED <IP_ADDRESS>:443
Verbose output
lesterdefreitas@Lesters-MacBook-Air naturvet % shopify theme dev --theme-editor-sync --store=https://naturvet.myshopify.com --verbose
2024-07-15T13:32:07.667Z: Running command theme dev
2024-07-15T13:32:07.685Z: Ensuring that the user is authenticated with the Theme API with the following scopes:
[]

2024-07-15T13:32:07.685Z: Ensuring that the user is authenticated with the Admin API with the following scopes for the store naturvet.myshopify.com:
[]

2024-07-15T13:32:07.686Z: Getting session store...
2024-07-15T13:32:07.687Z: Validating existing session against the scopes:
[
  "openid",
  "https://api.shopify.com/auth/shop.admin.graphql",
  "https://api.shopify.com/auth/shop.admin.themes",
  "https://api.shopify.com/auth/partners.collaborator-relationships.readonly",
  "https://api.shopify.com/auth/shop.storefront-renderer.devtools",
  "https://api.shopify.com/auth/partners.app.cli.access",
  "https://api.shopify.com/auth/destinations.readonly"
]
For applications:
{
  "adminApi": {
    "scopes": [],
    "storeFqdn": "naturvet.myshopify.com"
  }
}

2024-07-15T13:32:07.688Z: Sending Identity Introspection request to URL: https://accounts.shopify.com/oauth/introspection
2024-07-15T13:32:07.688Z: Sending POST request to URL https://accounts.shopify.com/oauth/introspection
With request headers:
 - User-Agent: Shopify CLI; v=3.64.0
 - Keep-Alive: timeout=30
 - Sec-CH-UA-PLATFORM: darwin
 - Content-Type: application/json

2024-07-15T13:32:08.357Z: Request to https://accounts.shopify.com/oauth/introspection completed in 660 ms
With response headers:
 - cache-control: no-cache, no-store, private, must-revalidate, max-age=0
 - content-type: application/json; charset=utf-8
 - etag: W/"6c2c34aaa45d5d340aad286de3bcb9ab"
 - x-request-id: 742902c5-b82b-4e61-9d86-e5474a1fde0a-1721050328

2024-07-15T13:32:08.359Z: The identity token is valid: true
2024-07-15T13:32:08.360Z:
The validation of the token for application/identity completed with the following results:
- It's expired: false
- It's invalid in identity: false

2024-07-15T13:32:08.360Z: The current session is valid but needs refresh. Refreshing...
2024-07-15T13:32:08.361Z: Sending POST request to URL https://accounts.shopify.com/oauth/token?grant_type=refresh_token&access_token=atkn_CjQI1cfUtAYQ9f_UtAZSJggBEhD9aVl0_xVAW47sfEV0qmYJGhCG6zsxTRpLVLQQIVSBg99DEkDmwvyUVO1R941T-_njM04K4hM9jI7zg-VwDv4I-YlWQbLwhOThlhh23kvIHOWc5PPEvE4pcFQCWwkl5jtJPhkA&refresh_token=atkn_CiEI1cfUtAYQ1eHytQaiARIKEIbrOzFNGktUtBAhVIGD30MSQNS0jZ6dSqlVhi7WqS5cu2cOwYjCKUsPxSQiDR13ZoBg8229OSD7HNCfu3TAtMPaJP5AgRo25ObnLIOhcy_ywQs&client_id=fbdb2649-e327-4907-8f67-908d24cfd7e3
With request headers:
 - User-Agent: Shopify CLI; v=3.64.0
 - Keep-Alive: timeout=30
 - Sec-CH-UA-PLATFORM: darwin
 - Content-Type: application/json

2024-07-15T13:32:09.106Z: Request to https://accounts.shopify.com/oauth/token?grant_type=refresh_token&access_token=atkn_CjQI1cfUtAYQ9f_UtAZSJggBEhD9aVl0_xVAW47sfEV0qmYJGhCG6zsxTRpLVLQQIVSBg99DEkDmwvyUVO1R941T-_njM04K4hM9jI7zg-VwDv4I-YlWQbLwhOThlhh23kvIHOWc5PPEvE4pcFQCWwkl5jtJPhkA&refresh_token=atkn_CiEI1cfUtAYQ1eHytQaiARIKEIbrOzFNGktUtBAhVIGD30MSQNS0jZ6dSqlVhi7WqS5cu2cOwYjCKUsPxSQiDR13ZoBg8229OSD7HNCfu3TAtMPaJP5AgRo25ObnLIOhcy_ywQs&client_id=fbdb2649-e327-4907-8f67-908d24cfd7e3 completed in 744 ms
With response headers:
 - cache-control: no-cache, no-store, private, must-revalidate, max-age=0
 - content-type: application/json; charset=utf-8
 - etag: W/"c145fb81a14c9d04e55a5b72e1f10e52"
 - x-request-id: ead9a156-7878-4edc-a25a-2be535c396f5-1721050328

2024-07-15T13:32:09.109Z: Sending POST request to URL https://accounts.shopify.com/oauth/token?grant_type=urn%3Aietf%3Aparams%3Aoauth%3Agrant-type%3Atoken-exchange&requested_token_type=urn%3Aietf%3Aparams%3Aoauth%3Atoken-type%3Aaccess_token&subject_token_type=urn%3Aietf%3Aparams%3Aoauth%3Atoken-type%3Aaccess_token&client_id=fbdb2649-e327-4907-8f67-908d24cfd7e3&audience=271e16d403dfa18082ffb3d197bd2b5f4479c3fc32736d69296829cbb28d41a6&scope=https%3A%2F%2Fapi.shopify.com%2Fauth%2Fpartners.app.cli.access&subject_token=****
With request headers:
 - User-Agent: Shopify CLI; v=3.64.0
 - Keep-Alive: timeout=30
 - Sec-CH-UA-PLATFORM: darwin
 - Content-Type: application/json

2024-07-15T13:32:09.109Z: Sending POST request to URL https://accounts.shopify.com/oauth/token?grant_type=urn%3Aietf%3Aparams%3Aoauth%3Agrant-type%3Atoken-exchange&requested_token_type=urn%3Aietf%3Aparams%3Aoauth%3Atoken-type%3Aaccess_token&subject_token_type=urn%3Aietf%3Aparams%3Aoauth%3Atoken-type%3Aaccess_token&client_id=fbdb2649-e327-4907-8f67-908d24cfd7e3&audience=ee139b3d-5861-4d45-b387-1bc3ada7811c&scope=https%3A%2F%2Fapi.shopify.com%2Fauth%2Fshop.storefront-renderer.devtools&subject_token=****
With request headers:
 - User-Agent: Shopify CLI; v=3.64.0
 - Keep-Alive: timeout=30
 - Sec-CH-UA-PLATFORM: darwin
 - Content-Type: application/json

2024-07-15T13:32:09.109Z: Sending POST request to URL https://accounts.shopify.com/oauth/token?grant_type=urn%3Aietf%3Aparams%3Aoauth%3Agrant-type%3Atoken-exchange&requested_token_type=urn%3Aietf%3Aparams%3Aoauth%3Atoken-type%3Aaccess_token&subject_token_type=urn%3Aietf%3Aparams%3Aoauth%3Atoken-type%3Aaccess_token&client_id=fbdb2649-e327-4907-8f67-908d24cfd7e3&audience=32ff8ee5-82b8-4d93-9f8a-c6997cefb7dc&scope=https%3A%2F%2Fapi.shopify.com%2Fauth%2Fdestinations.readonly&subject_token=****
With request headers:
 - User-Agent: Shopify CLI; v=3.64.0
 - Keep-Alive: timeout=30
 - Sec-CH-UA-PLATFORM: darwin
 - Content-Type: application/json

2024-07-15T13:32:09.109Z: Sending POST request to URL https://accounts.shopify.com/oauth/token?grant_type=urn%3Aietf%3Aparams%3Aoauth%3Agrant-type%3Atoken-exchange&requested_token_type=urn%3Aietf%3Aparams%3Aoauth%3Atoken-type%3Aaccess_token&subject_token_type=urn%3Aietf%3Aparams%3Aoauth%3Atoken-type%3Aaccess_token&client_id=fbdb2649-e327-4907-8f67-908d24cfd7e3&audience=7ee65a63608843c577db8b23c4d7316ea0a01bd2f7594f8a9c06ea668c1b775c&scope=https%3A%2F%2Fapi.shopify.com%2Fauth%2Fshop.admin.graphql+https%3A%2F%2Fapi.shopify.com%2Fauth%2Fshop.admin.themes+https%3A%2F%2Fapi.shopify.com%2Fauth%2Fpartners.collaborator-relationships.readonly&subject_token=****&destination=https%3A%2F%2Fnaturvet.myshopify.com%2Fadmin
With request headers:
 - User-Agent: Shopify CLI; v=3.64.0
 - Keep-Alive: timeout=30
 - Sec-CH-UA-PLATFORM: darwin
 - Content-Type: application/json

2024-07-15T13:32:09.633Z: Request to https://accounts.shopify.com/oauth/token?grant_type=urn%3Aietf%3Aparams%3Aoauth%3Agrant-type%3Atoken-exchange&requested_token_type=urn%3Aietf%3Aparams%3Aoauth%3Atoken-type%3Aaccess_token&subject_token_type=urn%3Aietf%3Aparams%3Aoauth%3Atoken-type%3Aaccess_token&client_id=fbdb2649-e327-4907-8f67-908d24cfd7e3&audience=271e16d403dfa18082ffb3d197bd2b5f4479c3fc32736d69296829cbb28d41a6&scope=https%3A%2F%2Fapi.shopify.com%2Fauth%2Fpartners.app.cli.access&subject_token=**** completed in 522 ms
With response headers:
 - cache-control: no-cache, no-store, private, must-revalidate, max-age=0
 - content-type: application/json; charset=utf-8
 - etag: W/"0099a8477e684c91216cc64fa675116a"
 - x-request-id: 82a5459c-7cea-4b89-a114-bc42daf93e47-1721050329

2024-07-15T13:32:09.842Z: Request to https://accounts.shopify.com/oauth/token?grant_type=urn%3Aietf%3Aparams%3Aoauth%3Agrant-type%3Atoken-exchange&requested_token_type=urn%3Aietf%3Aparams%3Aoauth%3Atoken-type%3Aaccess_token&subject_token_type=urn%3Aietf%3Aparams%3Aoauth%3Atoken-type%3Aaccess_token&client_id=fbdb2649-e327-4907-8f67-908d24cfd7e3&audience=32ff8ee5-82b8-4d93-9f8a-c6997cefb7dc&scope=https%3A%2F%2Fapi.shopify.com%2Fauth%2Fdestinations.readonly&subject_token=**** completed in 729 ms
With response headers:
 - cache-control: no-cache, no-store, private, must-revalidate, max-age=0
 - content-type: application/json; charset=utf-8
 - etag: W/"e07f4efdf5cea74e4eabd4163ba0d2df"
 - x-request-id: cf1cf5f5-52fb-4348-92d8-b1a2f7f7a899-1721050329

2024-07-15T13:32:09.922Z: Request to https://accounts.shopify.com/oauth/token?grant_type=urn%3Aietf%3Aparams%3Aoauth%3Agrant-type%3Atoken-exchange&requested_token_type=urn%3Aietf%3Aparams%3Aoauth%3Atoken-type%3Aaccess_token&subject_token_type=urn%3Aietf%3Aparams%3Aoauth%3Atoken-type%3Aaccess_token&client_id=fbdb2649-e327-4907-8f67-908d24cfd7e3&audience=7ee65a63608843c577db8b23c4d7316ea0a01bd2f7594f8a9c06ea668c1b775c&scope=https%3A%2F%2Fapi.shopify.com%2Fauth%2Fshop.admin.graphql+https%3A%2F%2Fapi.shopify.com%2Fauth%2Fshop.admin.themes+https%3A%2F%2Fapi.shopify.com%2Fauth%2Fpartners.collaborator-relationships.readonly&subject_token=****&destination=https%3A%2F%2Fnaturvet.myshopify.com%2Fadmin completed in 809 ms
With response headers:
 - cache-control: no-cache, no-store, private, must-revalidate, max-age=0
 - content-type: application/json; charset=utf-8
 - etag: W/"24330f3ec2bf886962093793e8aff5a2"
 - x-request-id: c1ffeec6-238c-43c6-a0b7-8a9890583e8a-1721050329

2024-07-15T13:32:09.960Z: Request to https://accounts.shopify.com/oauth/token?grant_type=urn%3Aietf%3Aparams%3Aoauth%3Agrant-type%3Atoken-exchange&requested_token_type=urn%3Aietf%3Aparams%3Aoauth%3Atoken-type%3Aaccess_token&subject_token_type=urn%3Aietf%3Aparams%3Aoauth%3Atoken-type%3Aaccess_token&client_id=fbdb2649-e327-4907-8f67-908d24cfd7e3&audience=ee139b3d-5861-4d45-b387-1bc3ada7811c&scope=https%3A%2F%2Fapi.shopify.com%2Fauth%2Fshop.storefront-renderer.devtools&subject_token=**** completed in 848 ms
With response headers:
 - cache-control: no-cache, no-store, private, must-revalidate, max-age=0
 - content-type: application/json; charset=utf-8
 - etag: W/"501f44fe4105f49c920064eb085191a8"
 - x-request-id: b4f6f96e-5dc9-497e-a0c5-6fa634c62fa6-1721050329

2024-07-15T13:32:09.961Z: Setting session store...
2024-07-15T13:32:09.969Z: Ensuring that the user is authenticated with the Storefront API with the following scopes:
[]

2024-07-15T13:32:09.969Z: Getting session store...
2024-07-15T13:32:09.970Z: Validating existing session against the scopes:
[
  "openid",
  "https://api.shopify.com/auth/shop.admin.graphql",
  "https://api.shopify.com/auth/shop.admin.themes",
  "https://api.shopify.com/auth/partners.collaborator-relationships.readonly",
  "https://api.shopify.com/auth/shop.storefront-renderer.devtools",
  "https://api.shopify.com/auth/partners.app.cli.access",
  "https://api.shopify.com/auth/destinations.readonly"
]
For applications:
{
  "storefrontRendererApi": {
    "scopes": []
  }
}

2024-07-15T13:32:09.970Z: Sending Identity Introspection request to URL: https://accounts.shopify.com/oauth/introspection
2024-07-15T13:32:09.970Z: Sending POST request to URL https://accounts.shopify.com/oauth/introspection
With request headers:
 - User-Agent: Shopify CLI; v=3.64.0
 - Keep-Alive: timeout=30
 - Sec-CH-UA-PLATFORM: darwin
 - Content-Type: application/json

2024-07-15T13:32:10.652Z: Request to https://accounts.shopify.com/oauth/introspection completed in 681 ms
With response headers:
 - cache-control: no-cache, no-store, private, must-revalidate, max-age=0
 - content-type: application/json; charset=utf-8
 - etag: W/"dc1ae599b101d84ec14abad972405129"
 - x-request-id: 26f67c6d-611e-473e-a312-643be8e9975d-1721050330

2024-07-15T13:32:10.653Z: The identity token is valid: true
2024-07-15T13:32:10.653Z:
The validation of the token for application/identity completed with the following results:
- It's expired: false
- It's invalid in identity: false

2024-07-15T13:32:10.660Z:
Running system process:
  · Command: ruby -v
  · Working directory: /Users/lesterdefreitas/Documents/GitHub/naturvet

2024-07-15T13:32:10.687Z:
Running system process:
  · Command: bundle -v
  · Working directory: /Users/lesterdefreitas/Documents/GitHub/naturvet

2024-07-15T13:32:10.819Z: Reading the content of file at<EMAIL_ADDRESS>2024-07-15T13:32:10.820Z:
Running system process:
  · Command: bundle install
  · Working directory: /opt/homebrew/lib/node_modules/@shopify/cli/dist/assets/cli-ruby

2024-07-15T13:32:11.015Z:
Running system process:
  · Command: bundle exec ruby /opt/homebrew/lib/node_modules/@shopify/cli/dist/assets/cli-ruby/bin/shopify theme token --admin atkn_Cp8DCNnJ1LQGEPmB1bQGYpADCAESEJaNOHjJ4k4qug5Nryk5ebEaqAFodHRwczovL2FwaS5zaG9waWZ5LmNvbS9hdXRoL3BhcnRuZXJzLmNvbGxhYm9yYXRvci1yZWxhdGlvbnNoaXBzLnJlYWRvbmx5IGh0dHBzOi8vYXBpLnNob3BpZnkuY29tL2F1dGgvc2hvcC5hZG1pbi5ncmFwaHFsIGh0dHBzOi8vYXBpLnNob3BpZnkuY29tL2F1dGgvc2hvcC5hZG1pbi50aGVtZXMgDSinUzIQWmnEDgofRGuHlaHhLP7IMTokZDRkN2VhNWEtNTI5Ny00N2Q1LTg5ZmItNmVjMzExMDJmMzI3QgdBY2NvdW50ShCDWG5aZyZK2JaliDxDaw3dUlN7InN1YiI6ImZiZGIyNjQ5LWUzMjctNDkwNy04ZjY3LTkwOGQyNGNmZDdlMyIsImlzcyI6Imh0dHBzOi8vYWNjb3VudHMuc2hvcGlmeS5jb20ifWIQhad5IZcxSyqpQcl8Vpw5ZmoQFQfpUI-VT8qnl3NfJ39t7BJA-ASAtxh0uPJ7QzqmYRebuXYVxPP92XNbeNVUbnm-2EmZYIcIr2KskUWt652NC1yyMDI7EqRvCZwdBtzY624XCQ --sfr atkn_CqMCCNnJ1LQGEPmB1bQGYpQCCAESEAwjdr-oA0oLsli3nHjbu7YaPmh0dHBzOi8vYXBpLnNob3BpZnkuY29tL2F1dGgvc2hvcC5zdG9yZWZyb250LXJlbmRlcmVyLmRldnRvb2xzINhSKKdTOiRkNGQ3ZWE1YS01Mjk3LTQ3ZDUtODlmYi02ZWMzMTEwMmYzMjdCB0FjY291bnRKEINYblpnJkrYlqWIPENrDd1SU3sic3ViIjoiZmJkYjI2NDktZTMyNy00OTA3LThmNjctOTA4ZDI0Y2ZkN2UzIiwiaXNzIjoiaHR0cHM6Ly9hY2NvdW50cy5zaG9waWZ5LmNvbSJ9YhCFp3khlzFLKqlByXxWnDlmahAVB-lQj5VPyqeXc18nf23sEkDglVccrkY_HC53WfrkDKTdH2YDQdz2q7rWwZj5oba0t44KhGwIUB1FUAfry65OHYOIrSh1gSWTVoxYOHBjZ-MF
  · Working directory: /Users/lesterdefreitas/Documents/GitHub/naturvet

2024-07-15T13:32:11.303Z: Getting development theme...
2024-07-15T13:32:27.448Z: Request to https://naturvet.myshopify.com/admin/api/unstable/themes/166797738292.json?fields=id%2Cname%2Crole%2Cprocessing completed in 16144 ms
With response headers:

╭─ error ────────────────────────────────────────────────────────────────────────────────────────╮
│                                                                                │
│  request to https://naturvet.myshopify.com/admin/api/unstable/themes/166797738292.json?fields  │
│  =id%2Cname%2Crole%2Cprocessing failed, reason: connect ECONNREFUSED <IP_ADDRESS>:443          │
│                                                                                │
╰────────────────────────────────────────────────────────────────────────────────────────────────╯

2024-07-15T13:32:27.488Z:
Running system process:
  · Command: npm prefix
  · Working directory: /Users/lesterdefreitas/Documents/GitHub/naturvet

2024-07-15T13:32:27.647Z: Obtaining the dependency manager in directory /Users/lesterdefreitas/Documents/GitHub/naturvet...
2024-07-15T13:32:27.736Z:
Running system process:
  · Command: ruby -v
  · Working directory: /Users/lesterdefreitas/Documents/GitHub/naturvet

2024-07-15T13:32:28.190Z: Request to https://monorail-edge.shopifysvc.com/v1/produce completed in 436 ms
With response headers:
 - x-request-id: a524323b-ebfd-495b-a9a3-9845678ca690

2024-07-15T13:32:28.192Z: Analytics event sent: {
  "command": "theme dev",
  "time_start":<PHONE_NUMBER>669,
  "time_end":<PHONE_NUMBER>484,
  "total_time": 19815,
  "success": false,
  "cli_version": "3.64.0",
  "ruby_version": "3.3.4",
  "node_version": "22.4.1",
  "is_employee": false,
  "uname": "darwin arm64",
  "env_ci": false,
  "env_plugin_installed_any_custom": false,
  "env_plugin_installed_shopify": "[\"@shopify/cli\"]",
  "env_shell": "zsh",
  "env_device_id": "da59676f07bfeb929e6d032e1000a952f7a4d2d8",
  "env_cloud": "localhost",
  "env_package_manager": "unknown",
  "env_is_global": true,
  "cmd_app_warning_api_key_deprecation_displayed": false,
  "cmd_all_timing_network_ms": 19286,
  "cmd_all_timing_prompts_ms": 0,
  "cmd_all_launcher": "unknown",
  "cmd_all_topic": "theme",
  "cmd_all_plugin": "@shopify/cli",
  "cmd_all_force": false,
  "cmd_all_verbose": true,
  "cmd_all_path_override": true,
  "cmd_all_path_override_hash": "8ab481c972c4d7958909f6c9741e40e9da4ffc6e",
  "cmd_all_timing_active_ms": 528,
  "cmd_all_exit": "expected_error",
  "args": "--theme-editor-sync --store=https://naturvet.myshopify.com --verbose",
  "error_message": "request to https://naturvet.myshopify.com/admin/api/unstable/themes/166797738292.json?fields=id%2Cname%2Crole%2Cprocessing failed, reason: connect ECONNREFUSED <IP_ADDRESS>:443",
  "env_plugin_installed_all": "[\"@shopify/cli\"]",
  "metadata": "{\"extraPublic\":{},\"extraSensitive\":{}}"
}
2024-07-15T13:32:28.203Z: Reporting handled error to Bugsnag: request to https://naturvet.myshopify.com/admin/api/unstable/themes/166797738292.json?fields=id%2Cname%2Crole%2Cprocessing failed, reason: connect ECONNREFUSED <IP_ADDRESS>:443
2024-07-15T13:32:28.259Z:
Running system process:
  · Command: npm prefix
  · Working directory: /Users/lesterdefreitas/Documents/GitHub/naturvet

2024-07-15T13:32:28.356Z: Obtaining the dependency manager in directory /Users/lesterdefreitas/Documents/GitHub/naturvet...
lesterdefreitas@Lesters-MacBook-Air naturvet %

### Reproduction steps

1. Run  `shopify theme dev`

### Operating System

Mac OS 14.0 (23A344)

### Shopify CLI version (check your project's `package.json` if you're not sure)

3.64.0

### Shell

zsh

### Node version (run `node -v` if you're not sure)

v22.4.1

### What language and version are you using in your application?

ruby 3.3.4 (2024-07-09 revision be1089c8ec) [arm64-darwin23]

Hi @lucyxiang, thanks for coming back. It was a dev store so it very well may have been deleted in the process as I tried a couple shopify auth logout and logging back in attempts, which I believe deletes dev themes, yes? Just to also add, this error is a bit intermittent for me. Switching networks has resolved it at times, even though the initial network was working. So it's a weird one. But extremely frustrating. Could it be a network related issue though?

@lesterdefreitas this error looks like to be coming from Shopify when we try to fetch for theme data, not the CLI itself. I suspected it's a network issue but if it works sometimes and doesn't work sometimes and you've changes nothing about your setup, that is strange. Does this error happen when you can access the theme in the admin (ie. connection error when using the CLI but not when using the browser)?

@lucyxiang it happens when we try to create a new dev theme (shopify theme dev) so the theme may or may not exist at the time of running the command. But either way the command should create a new theme if there isn't one, or at least that's been our experience.
Dev themes aren't visible in the admin theme library so we can't really check without starting up the theme and opening the theme editor link from the cli. But in this case it fails anyway, so we can't.
But, I definitely think this has something to do with network as it works after I restart our network and then shopify auth logout and try again.
It's weird and hard to explain. But I don't think it's a cli or Shopify issue actually. Must be something on our side. Annoying though.
I think this issue can be closed.

Same issue here

@TheGreatSimo have you tried different networks? I'm pretty sure the issue I was having was network related as I was working from a different location than usual. Since being back at the office I haven't experienced this issue again.

@lesterdefreitas I resolved it thank you!
For anyone else having this issue here’s how I fixed it (at least in my case):
I upgraded the Shopify CLI and Node to the latest versions. Then, I pushed the theme before running shopify theme dev


using a local .pth returns error

from transparent_background import Remover

# Load remover model
remover = Remover(device="cuda:0", ckpt='/content/latest_v2.pth')

---------------------------------------------------------------------------
RuntimeError                              Traceback (most recent call last)
[<ipython-input-1-9234ebeb83b8>](https://localhost:8080/#) in <cell line: 4>()
      2
      3 # Load remover model
----> 4 remover = Remover(device="cuda:0", ckpt='/content/latest_v2.pth')

2 frames
[/usr/local/lib/python3.10/dist-packages/torch/serialization.py](https://localhost:8080/#) in __init__(self, name_or_buffer)
    455 class _open_zipfile_reader(_opener):
    456     def __init__(self, name_or_buffer) -> None:
--> 457         super().__init__(torch._C.PyTorchFileReader(name_or_buffer))
    458
    459

RuntimeError: PytorchStreamReader failed reading zip archive: failed finding central directory

@plemeri btw, originally if we don't state a local.pth, it downloads from your google drive and sometimes it failed (because too many downloads)
is it still the case now?

Hi @wilfrediscoming, I moved from google drive to github release, so it is not a problem anymore and I tested myself last week. After some googling, your checkpoint latest_v2.pth seems corrupted. Please check if it is valid.

[transparent-background]，
Hello friend, can you specify object names to execute? When there are multiple objects in picture and I want to block out some objects, for example, there is a small dog next to me but I don't need it to show. I seem to not be able to find this step in the instructions, thank you!

@wwwtxhy You can try some image dectection library, but I am not sure if it fits your use case.
If you don't want a dog to show next to you, you can use inpainting to erase the dog, and any objects that you don't want.

@plemeri Thanks for letting me know, then I don't have to download from my own google drive anymore. Cheers! 👍


don't use transactions if writing single messages

Codecov Report

Merging #105 (8e6f761) into main (e79d136) will decrease coverage by 0.17%.
The diff coverage is 71.42%.

@@            Coverage Diff             @@
##             main     #105      +/-   ##
==========================================
- Coverage   69.46%   69.28%   -0.18%
==========================================
  Files         146      146
  Lines        2774     2784      +10
  Branches       68       65       -3
==========================================
+ Hits         1927     1929       +2
- Misses        847      855       +8

Impacted Files
Coverage Δ

.../surge/internal/kafka/KafkaProducerActorImpl.scala
82.52% <71.42%> (-2.81%)
:arrow_down:

...health/windows/actor/HealthSignalWindowActor.scala
93.10% <0.00%> (ø)

...a/surge/kafka/KafkaPartitionShardRouterActor.scala
62.77% <0.00%> (+0.72%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update e79d136...8e6f761. Read the comment docs.


post-quantizing and loading a a trained model in keras using tflite issue

System information

google colab ( intended to be used on raspberry pi)
TensorFlow 1.14
python 2.7 ( i know its old and not supported but i have to use it)

Provide the text output from tflite_convert
/usr/local/lib/python2.7/dist-packages/tensorflow_core/lite/python/convert.pyc in toco_convert_protos(model_flags_str, toco_flags_str, input_data_str, debug_info_str, enable_mlir_converter)

ConverterError: See console for info.
2021-02-11 22:29:16.405546: I tensorflow/lite/toco/import_tensorflow.cc:1336] Converting unsupported operation: AddV2
2021-02-11 22:29:16.424912: I tensorflow/lite/toco/graph_transformations/graph_transformations.cc:39] Before Removing unused ops: 57 operators, 100 arrays (0 quantized)
2021-02-11 22:29:16.425598: I tensorflow/lite/toco/graph_transformations/graph_transformations.cc:39] Before general graph transformations: 57 operators, 100 arrays (0 quantized)
2021-02-11 22:29:16.427571: I tensorflow/lite/toco/graph_transformations/graph_transformations.cc:39] After general graph transformations pass 1: 25 operators, 53 arrays (0 quantized)
2021-02-11 22:29:17.452115: I tensorflow/lite/toco/graph_transformations/graph_transformations.cc:39] After general graph transformations pass 2: 24 operators, 52 arrays (0 quantized)
2021-02-11 22:29:17.452530: I tensorflow/lite/toco/graph_transformations/graph_transformations.cc:39] After general graph transformations pass 3: 23 operators, 50 arrays (0 quantized)
2021-02-11 22:29:17.452823: I tensorflow/lite/toco/graph_transformations/graph_transformations.cc:39] Before Group bidirectional sequence lstm/rnn: 23 operators, 50 arrays (0 quantized)
2021-02-11 22:29:17.453000: I tensorflow/lite/toco/graph_transformations/graph_transformations.cc:39] Before dequantization graph transformations: 23 operators, 50 arrays (0 quantized)
2021-02-11 22:29:17.453320: I tensorflow/lite/toco/allocate_transient_arrays.cc:345] Total transient array allocated size: 16777216 bytes, theoretical optimal value: 16777216 bytes.
2021-02-11 22:29:17.453614: E tensorflow/lite/toco/toco_tooling.cc:456] We are continually in the process of adding support to TensorFlow Lite for more ops. It would be helpful if you could inform us of how this conversion went by opening a github issue at https://github.com/tensorflow/tensorflow/issues/new?template=40-tflite-op-request.md
 and pasting the following:

Some of the operators in the model are not supported by the standard TensorFlow Lite runtime. If those are native TensorFlow operators, you might be able to use the extended runtime by passing --enable_select_tf_ops, or by setting target_ops=TFLITE_BUILTINS,SELECT_TF_OPS when calling tf.lite.TFLiteConverter(). Otherwise, if you have a custom implementation for them you can disable this error with --allow_custom_ops, or by setting allow_custom_ops=True when calling tf.lite.TFLiteConverter(). Here is a list of builtin operators you are using: ADD, CONV_2D, FULLY_CONNECTED, MAX_POOL_2D, MUL, SOFTMAX. Here is a list of operators for which you will need custom implementations: AddV2.
Traceback (most recent call last):
  File "/usr/local/bin/toco_from_protos", line 8, in <module>
    sys.exit(main())
  File "/usr/local/lib/python2.7/dist-packages/tensorflow/lite/toco/python/toco_from_protos.py", line 59, in main
    app.run(main=execute, argv=[sys.argv[0]] + unparsed)
  File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/platform/app.py", line 40, in run
    _run(main=main, argv=argv, flags_parser=_parse_flags_tolerate_undef)
  File "/usr/local/lib/python2.7/dist-packages/absl/app.py", line 300, in run
    _run_main(main, args)
  File "/usr/local/lib/python2.7/dist-packages/absl/app.py", line 251, in _run_main
    sys.exit(main(argv))
  File "/usr/local/lib/python2.7/dist-packages/tensorflow/lite/toco/python/toco_from_protos.py", line 33, in execute
    output_str = tensorflow_wrap_toco.TocoConvert(model_str, toco_str, input_str)
Exception: We are continually in the process of adding support to TensorFlow Lite for more ops. It would be helpful if you could inform us of how this conversion went by opening a github issue at https://github.com/tensorflow/tensorflow/issues/new?template=40-tflite-op-request.md
 and pasting the following:

Some of the operators in the model are not supported by the standard TensorFlow Lite runtime. If those are native TensorFlow operators, you might be able to use the extended runtime by passing --enable_select_tf_ops, or by setting target_ops=TFLITE_BUILTINS,SELECT_TF_OPS when calling tf.lite.TFLiteConverter(). Otherwise, if you have a custom implementation for them you can disable this error with --allow_custom_ops, or by setting allow_custom_ops=True when calling tf.lite.TFLiteConverter(). Here is a list of builtin operators you are using: ADD, CONV_2D, FULLY_CONNECTED, MAX_POOL_2D, MUL, SOFTMAX. Here is a list of operators for which you will need custom implementations: AddV2.

Standalone code to reproduce the issue
WHOLE MODEL
import tensorflow as tf
from tensorflow import lite
from tensorflow import keras
from keras.models import load_model
import os
model=keras.models.load_model('/content/drive/MyDrive/disease classification/AGAIN/end_model_acc1.h5')
allow_custom_ops=True
#--enable_select_tf_ops
converter = tf.lite.TFLiteConverter.from_keras_model(model)
tfmodel = converter.convert()
open ("model.tflite" , "wb") .write(tfmodel)
#loading quantized model and interprete it
interpreter = tf.lite.Interpreter(model_content=tfmodel)
interpreter.allocate_tensors()
input_details = interpreter.get_input_details()
output_details= interpreter.get_output_details()
#interpreter.resize_tensor_input(input_details[0]['index'],(10, 224, 224, 3))
#interpreter.resize_tensor_input(output_details[0]['index'], (15, 224,224,3))
interpreter.allocate_tensors()
os.chdir("/content/drive/MyDrive/disease classification/The End/")
!pwd
Any other info / logs
the model is used for image classification of 10 classes using CNN to be performed on the raspberry pi , i would appreciate any feedback regarding the process as i am new to this. thank you.

There is an TF operator, that isn't covered by TFLite builtin kernels. You can enable select TF option for this case. https://www.tensorflow.org/lite/guide/ops_select
converter = tf.lite.TFLiteConverter.from_keras_model(model)
converter.target_spec.supported_ops = [
  tf.lite.OpsSet.TFLITE_BUILTINS, # enable TensorFlow Lite ops.
  tf.lite.OpsSet.SELECT_TF_OPS # enable TensorFlow ops.
]
tfmodel = converter.convert()

Thank you very much! it worked.


Exports should be prepared server-side

Currently we have a number of 'Export to XLSX' buttons in admin and these are all downloading full data to the client and then transforming it into the desired XLSX format. This is clunky. Instead we should be doing this on the server-side and perhaps saving the data to Google Drive as a Google Sheet instead of allowing a direct download.

Assigned to Halcyon in the March WO.

[]

There appear to be a number of pages with Export XYZ buttons on them that use the existing client-side downloadXLSX() function, which need moving to a server-side implementation:

[ ] Exercises
[ ] Applications - Export Contacts
[ ] Reports - Diversity Report
[ ] Reports - Handover
[ ] Reports - Outreach
[ ] Reports - Reasonable Adjustments
[ ] Reports - Qualifying Test Report
[ ] Qualifying Tests - Responses

Please confim that the above list is correct

Hi @HalcyonJAC the following pages are the ones to optimise:

[ ] Applications - Export Contacts
[ ] Reports - Handover
[ ] Reports - Reasonable Adjustments
[ ] Qualifying Tests - Responses

The following, mentioned above, are all ok as the data being converted to xlsx is already pre-generated or created server-side:

Exercises a cloud function does the heavy lifting here. NB this is also being worked on this month
Reports - Diversity Report report is pre-generated via a cloud function
Reports - Outreach report is pre-generated via a cloud function
Reports - Qualifying Test Report report is pre-generated via a cloud function

For now I think let's keep them as xlsx downloads.
We can consider exporting to google drive in a future ticket.

Thanks @warrensearle !

Please leave for my return on 22/03 for testing and approval for release.

@HalcyonJAC @JeremykJAC I have tested this and found the following:
•  Applications - Export Contacts: I was able to export the contacts. There was no refresh button, but i'm guessing that was because it doesn't fall under reports? as is the case with QT - Responses.
•   Reports – Handover: Refresh button was there and I was able to download the report.
•   Reports - Reasonable Adjustments: Refresh button was there and I was able to download, however the report listed two people within it, while the platform only listed one candidate as having reasonable adjustments (pictures below).
•   Qualifying Tests – Responses: Was able to dowload the responses. There was no refresh button - as above for applications - Export Contacts.

Hi @KateMJAC
I have spent some time today trying to replicate the problem you found with the Reasonable Adjustments report, on my workstation but have not managed to. This is could be down to my lack of knowledge on the lifecycle of an exercise and system workflow. I would have called one of the developers for help but didn't want to take much of their time up.
In any case I have some changes to the exports so that the export button is no longer enabled unless there is actually data to export at least, to avoid other possible errors.
I will speak to one of the dev team tomorrow and see if they can help me replicate this problem locally so I can get to the bottom of it.
Darrel

Positive result during testing by Tester User Group. I also tested with a positive result. This can move to reviewed,


runtime/race: complete race detector on netbsd/amd64

The new netbsd/amd64 race detector support is not 100% done yet, per https://github.com/golang/go/issues/19273#issuecomment-349474852
We also don't have a builder for it.
This is a tracking bug to see it completed.
/cc @krytarowski

I will work on it after squashing the remaining failures in C/C++ style check-tsan:
$ check-tsan

********************
Testing Time: 1336.74s
********************
Failing Tests (8):
    ThreadSanitizer-x86_64 :: dtls.c
    ThreadSanitizer-x86_64 :: getline_nohang.cc
    ThreadSanitizer-x86_64 :: ignore_lib5.cc
    ThreadSanitizer-x86_64 :: ignored-interceptors-mmap.cc
    ThreadSanitizer-x86_64 :: mutex_lock_destroyed.cc
    ThreadSanitizer-x86_64 :: signal_block.cc
    ThreadSanitizer-x86_64 :: strerror_r.cc
    ThreadSanitizer-x86_64 :: vfork.cc

  Expected Passes    : 288
  Expected Failures  : 1
  Unsupported Tests  : 85
  Unexpected Failures: 8

Other than that, golang/race seems to use the StopTheWorld() operation that is unimplemented in the upstream version for now. (We have got an implementation in downstream GCC copy).


Windows version of Kitematic

Current progress is visible at: https://github.com/kitematic/kitematic/pull/339
The status list:

[x] I recreated the deps and reset scripts for windows to install and remove external dependencies. They are written in powershell, coz my CMD skills really suck, and I am not sure if some steps could be done in CMD without at least invoking the PS commands. I was able to loose Chocolatey dependency though, which required administrator rights, so right now the whole setup can be done without admin rights.
[x] I have removed the pre and post install scripts from package.json as this is really discuraged by the NPM docs, and instead moved them to gulpfile. This also allowed me to port those scripts for Windows platform.
[x] I've updated the SetupStore and SetupUtil to prepare the application for windows, including the downloading and installation of VirtualBox. As mentioned before, it is done without Chocolatey, so it still might be a little shaky.
[x] Updated the list of directories used by the app, to proper Windows paths, so the docker and docker-machine binaries are placed on the user's directory. This might not be the best place for them, but it is a start.
[x] I noticed that docker-machine's boot2docker image, does not automatically share Users directory with the VM, so I created a workaround and invoke a VirtualBox command to do it manually during the VM initialization step in the SetupStore. This is a strange one though coz the regular boot2docker does that automatically. Maybe this is an issue to be raised in the docker-machine repo.
[x] I've rewritten a bit parts of code responsible for opening URLs or drive paths, and added an extra dependency node package called "open" which supports different platforms out of the box, so opening links and paths should now work on all platforms.
[x] Ability to open a CMD window with Docker env variables set up, and docker on the path.
[x] Tested the application setup process on WIndows 8.1 and it works as expected.
[x] File sharing and selecting directories in the app is flaky on windows, it still needs some magic to work properly. It works with the directory that is attached on container creation, but it is not possible yet, to change the default dir. Also the naming for the local directory in the container's settings should be changed, coz it is called "Mac Folder", so it is not really friendly for different platforms :)
[x] Application deploy in gulp file, is not ready for deploying windows version. I wanted to leave it as the last piece.
[x] Testing if any of my changes don't break any of the Mac functionality. Unfortunately I don't have access to Mac, so I am only testing the app on Windows, so I don't know if I didn't break anything.
[x] Probably some graphical changes to the app window itself to make it more Windows like :)
[x] Adding support for ssh terminal in ContainerSubHeader.
[x] Keyboard shortcuts support on Windows.
[x] Running reset scripts from the gulp task (npm run reset).
[ ] Auto updates
[x] Installer & Distribution

Added:

Auto updates
Installer & Distribution

to the list.

I just stumbled upon AppVeyor as a CI server for Windows in the Chocolatey project.
Perhaps this is a useful service to build the Windows verison of Kitematic: http://www.appveyor.com

@StefanScherer thanks! Awesome. This will be huge for any integration testing we need to do. Unit tests usually run in Linux on CircleCI and just test each JS class independently and mock the rest.

@domderen So far so good, I checked off Testing if any of my changes don't break any of the Mac functionality after some extensive testing.

@jeffdm Great! And in terms of unit tests, I guess we can add a few of them with mocked process.platform equal to 'win32'. Maybe add such point to the list?

Status update: Merged the initial PR @domderen with a few tweaks to make sure Mac still works.

Status update: Windows alpha launched last friday! Everything done on this list except for auto updates.
@domderen this foundational work was critical to getting an initial version of Windows shipped last week. I wanted to say a huge thanks for the contributions. Many Windows users around the world are running containers for the first time!
Going to close this for now in favor of an issue only for windows auto-updates.

I have a working build for my Kitematic fork with AppVeyor, maybe this helps someone:
https://github.com/nuest/kitematic/blob/model-ui/appveyor.yml

@nuest Impressive! Thanks for sharing.


Fix logo for dark mode

Closes #556

I can probably remove the pngs and only keep the svgs. Let me try

I removed the PNGs, so there's only two files now.
They are the source files for the logo, so I think they should stay in the repo.


PyTorch implementation

Hi,
Thanks for the great work, many years later it is in fact still difficult to find this particular functionality and quality elsewhere.
Unfortunately, Caffe was never a tame dependency and this is not improving, to the point that it is harder to get it to work nicely with other dependencies as it is to rewrite full setups from scratch.
Fast forward to this moment, I've ported the model to PyTorch. Hopefully it can be helpful for others:
https://github.com/andres-fr/face_segmentation_pytorch
I'm happy to receive any feedback. Cheers!
Andres

Thank you！ Very useful.

Great work! Thank you!

Thank you! It helps a lot!


Terminal quick fixes in fish shell

In the October 2023 release the terminal quick fixes were released, but it seems that it only works in zsh, or at least not in the fish shell.

it works in bash and fish for me. If automatic shell integration isn't working for you, you can read about how to manually install them here.

https://code.visualstudio.com/docs/terminal/shell-integration#_manual-installation

Okay, thank you. It seems that Starship disables this somehow, for some reason.

Okay, thank you. It seems that Starship disables this somehow, for some reason.

Hi, I come with same issue, shell integration not work with starship. How did you fix this?

Okay, thank you. It seems that Starship disables this somehow, for some reason.

Hi, I come with same issue, shell integration not work with starship. How did you fix this?

I didn't fix it. You can disable starfix and it will work, though.

Thanks! I haven't found a solution either, looks like I should stop and live with it for now 🤷♂


Improve gene search

Description
Load all genes in memory and perform all operations such as searching and sorting on the client's side. This improves the performance as it removes the need to wait for the back-end to fetch the data and send it to the front-end.
Details
URL to issue
https://biomage.atlassian.net/browse/BIOMAGE-2024
Link to staging deployment URL (or set N/A)
https://ui-kristian-ui782.scp-staging.biomage.net/
Links to any PRs or resources related to this PR
Integration test branch
master
Merge checklist
Your changes will be ready for merging after all of the steps below have been completed.

Code updates
Have best practices and ongoing refactors being observed in this PR

[ ] Migrated any selector / reducer used to the new format.

Manual/unit testing

[ ] Tested changes using InfraMock locally or no tests required for change, e.g. Kubernetes chart updates.
[ ] Validated that current unit tests for code work as expected and are sufficient for code coverage or no unit tests required for change, e.g. documentation update.
[ ] Unit tests written or no unit tests required for change, e.g. documentation update.

Integration testing
You must check the box below to run integration tests on the latest commit on your PR branch.
Integration tests have to pass before the PR can be merged. Without checking the box, your PR
will not pass the required status checks for merging.

[x] Started end-to-end tests on the latest commit.

Documentation updates

[ ] Relevant Github READMEs updated or no GitHub README updates required.
[ ] Relevant Wiki pages created/updated or no Wiki updates required.

Optional

[ ] Staging environment is unstaged before merging.
[ ] Photo of a cute animal attached to this PR.

Can you make the gene search ignore lowercase/uppercase letters? I want to be able to search for lyz and see Lyz2


Hardcoded lib directory

With Spark 2.x, the lib directory is no longer part of the distribution. It is now called jars. It would probably be better if the SPARK_LIB environment variable is used for pointing to the right lib directory. This will ensure that there are no class not found exceptions thrown.

from now spark2.x should be used. v1.2.0 changes the path to @SPARK_HOME@/jars/


Fix issue in examples/vae_train.py and remove unnecessary backslash

Unnecessary backslash removed & typo in docs resolved.
fix the issue in examples/vae_train.py

Hi, thanks for your pull request! Before we merge it, here are some suggestions:

For the unnecessary backclash removed:
You may want to check the code style by running pylint provided in the texar main directory. Just run this command
pylint texar/modules/decoders/transformer_decoders.py. You'd better move the parameters in the first line to the second line. Here is a great reference.

For the embedding dim.
Because there are some minor modifications to the hparams of Transformer modules, to keep the examples backward-compatible, you'd better change the trans_hparams in config_trans_ptb.py to

trans_hparams = {
    ...
    'dim': hidden_size,
    'position_embedder_hparams': {
        'dim': hidden_size,
    },
    ...
}

After you fix these issues, we can merge your pull request. Thanks!

Thanks for the pull request!
For the style of indentation, as in the guide. we prefer
foo = long_function_name(var_one, var_two,
                                             var_three, var_four)

or
foo = long_function_name(
    var_one, var_two, var_three, var_four)

but not
foo = long_function_name(var_one, var_two,
    var_three, var_four)

Thanks for fixing the bugs in vae_text. I'd merge the pull and fix the style issue.


Extension causes high cpu load

Issue Type: Performance
Extension Name: vscode-eslint
Extension Version: 2.1.13
OS Version: Windows_NT x64 10.0.18363
VSCode version: 1.51.1

:warning: Make sure to attach this file from your home-directory:
:warning:c:\Users\ps\AppData\Local\Temp\dbaeumer.vscode-eslint-unresponsive.cpuprofile.txt
Find more details here: https://github.com/microsoft/vscode/wiki/Explain-extension-causes-high-cpu-load

@Kirun1 can you please attach the cpu profile.


Confused on usage of S.Maybe

I get a TypeError from sanctuary-def saying
expected to return a value of type (Maybe Number); returned Nothing()`.

But I would have expected a Nothing to be a valid return type for a function written to return a Maybe($.Number)?
Simplified usage below, used with Node v5.20. Error at the bottom.
const R = require('ramda');
const S = require('sanctuary');
const $ = require('sanctuary-def');

// Maybe :: Type -> Type
const Maybe = $.UnaryType(
  'my-package/Maybe',
  x => x != null && x['@@type'] === 'my-package/Maybe',
  maybe => maybe.isJust ? [maybe.value] : []
);

const env = $.env.concat([Maybe]);

const def = $.create(env);

// Mock.
//
// availWarps :: Game -> Number -> [Number]
const availWarps =
  def('availWarps', {}, [$.Any, $.Number, $.Array($.Number)],
    (game, sid) => [1]);

// Mock. Would return a transformed game.
//
// move :: Game -> Number -> Number -> Game
const setSector = (game, pid, sid) => game;

// If `sid` appears in what `availWarps` returns: Just(sid). Else Nothing().
//
// isWarpAvailable :: Game -> Number -> Number -> Maybe Number
const isWarpAvailable =
  def('isWarpAvailable', {}, [$.Any, $.Number, $.Number, Maybe($.Number)],
    (game, pid, sid) =>
      S.Maybe.of(sid).filter(x => R.contains(sid, availWarps)));

// If `isWarpAvailable` returned a Just, run `setSector` and return the
// modified game, else return Nothing.
//
// move :: Game -> Number -> Number -> Maybe Game
const move =
  def('move', {}, [$.Any, $.Number, $.Number, Maybe($.Any)],
    (game, pid, sid) =>
      isWarpAvailable(game, pid, sid).extend(_ => setSector(game, pid, sid)));

// main

move({}, 1, 1);

/*
node_modules/sanctuary-def/index.js:714
            throw invalidReturnValue(name, [expRetType], returnValue);
            ^

TypeError: isWarpAvailable is expected to return a value of type (Maybe Number); returned Nothing()
    at invalidReturnValue (node_modules/sanctuary-def/index.js:534:12)
    at node_modules/sanctuary-def/index.js:714:19
    at node_modules/sanctuary-def/index.js:364:20
    at <this file>:64:7
*/

The predicate for your Maybe type is
x => x != null && x['@@type'] === 'my-package/Maybe'

but I imagine you want
x => x != null && x['@@type'] === 'sanctuary/Maybe'

since S.Nothing()['@@type'] evaluates to 'sanctuary/Maybe'.

Please reopen this issue, @Wideshanks, if the comment above does not solve your problem.


Can not install on SS4.1 via composer

Can not install on SS 4.1 via composer
composer require "dljoseph/silverstripe-maintenance-mode:*"

composer require thisisbd/silverstripe-maintenance-mode:dev-master
This worked for me, please update the docs I ran into the same problem


Cache file default naming convention

For some reason I'm unable to submit a pull request for this repository. I suggest changing line 49 of util.py from:
cache_path = cache_path or ".cache-" + username

to:
cache_path = cache_path or ".cache-" + username + "-" + str(scope)

Several issues have been opened regarding the need to interact with the browser more than once to refresh tokens when using util.py. I believe it is because  the token cache file is overwritten when tokens of different scopes are created using the default token cache file naming in util.py. Of course, users  of this library can manually enter a cache_path, but I believe other users ran into confusion, as I did. I don't believe the Spotipy documentation says enough about this function to justify making the default behavior of util.py nonfunctional for anyone creating multiple tokens.
Thank you for making this library. It is a useful tool for getting started interacting with the Spotify API quickly.


Added wizdom.xyz provider

wizdom.xyz is a new Hebrew subtitles provider meant to be an alternative to the many other Hebrew subtitles site who shut down.
The API provided by the site is really basic and requires imdb id to be present, but that's ok because subliminal has good refiners.

Already open and pending for a long time.. (#763 )


SignalR Support

Clear and concise description of the problem
For a long time I can’t find what and how to describe the API for signalR.
I think it would be great to add signalR support to typespec
SignalR docs
Checklist

[X] Follow our Code of Conduct
[X] Read the docs.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

It might be suitable to use as an AsyncAPI base

Hi @Kreash, thanks for your suggestion. I agree it would be nice, but I have to be honest, it's not likely to reach the top of our priority list any time soon. However, we'd be happy to accept a contribution If you'd like to add the support 👍

Hi @mario-guerra, I will be glad to take part in the development of SignalR support.
But since SignalR works via a websocket connection, it is probably worth thinking about supporting it first. I also think it is worth thinking about supporting asyncAPI.

@bterlson You indicated that the upcoming support for streaming APIs should be able to support SignalR, anything to add?