When switching to a page I lose all my page element edits

There are 3 options:

The application saves on page switches (quick-win for alpha release)
I get a warning that my work will be lost when switching
Data isn’t lost when I switch a page

(to be discussed)

Fixed in 1c96cafe2dcb4fc856576537bea699bdd6d8567b


Added genderqueer flag.

Hey ho!
Thought this would fit in nicely. Whether to include it or not, is your choice.
See ya',
Natamo

Looks good to me! I'll touch a few things up and merge it to master. Thank you for your contribution 🙂


Feat/string

Adds parsing for ASCII and utf8 strings as described here.
The limit to process long strings would depend on the device's input buffer capacity as long parameters would increase transaction size.
In the case a parsed clarity-value is a StringAscii longer than 60 characters, the first 60 ones will be shown on the string.
Utf8 strings are not shown(the screen is not able to render utf8 characters), but the device will indicate on the screen that the argument is a StringUtf8.
closes #78

I think it is important to bump the version number and update the corresponding screenshots before merging.


Await promise from Transitioner onTransitionStart

Motivation
This small PR enables a custom transitioner (using the Transitioner component) to delay the transition animation by returning a promise from onTransitionStart. The transition animation occurs after the promise resolves (or immediately, if not promise is returned).
This small feature enables the custom transitioner to perform some asynchronous work with the new scene before the animation begins (e.g., wait for an onLayout callback). It also enables the transitioner to delay the transition until certain data or images load.
In our app, we built a transitioner for variable-height 'sheets' that pop up from the bottom of the screen. In order to animate the presentation of the sheet correctly and consistently, we need to first measure the height of the sheet. With this patch, our transitioner can return a promise from onTransitionStart and then resolve the promise when the new sheet's height has been obtained, thus triggering the animation.
Not that it helps to elucidate much, but here's a GIF demonstrating this transitioner in action:

Test plan (required)
We've been using this patch for the past 4 months off a private branch to power the above custom transitioner. Given that there are not many tests for the Views directory, I hope this is sufficient. I'm happy to receive guidance on how to write a test for this.

This looks awesome, thanks for submitting!
I think maybe @vonovak can provide a more robust feedback than mine ^^

@vonovak — any time to take a look?

Hmm, I see this can be useful to delay the Animated.parallel(animations).start(this._onTransitionEnd); part, but am unsure about the API change - if we go ahead with this, onTransitionEnd should also have this possibility. What does @spencercarli think about this?

@vonovak, thanks for thinking about it.
Regarding onTransitionEnd, what behavior happens after the onTransitionEnd callback? From inspecting the _onTransitionEnd implementation, it appears that the only thing that after the callback is the invocation of any transitions that were issued and enqueued while the current one executes.
I'm struggling to think of a reason for delaying an unrelated transition, but I'm happy to implement the same promise-awaiting logic for onTransitionEnd if you'd prefer the APIs to be symmetrical in their behavior.

@jamesreggio yeah, good point. Let's wait for Spencer's thoughts.

Cool! A few thoughts

Even though adding it to onTransitionEnd may seem pointless I think, for the sake of consistency, it would be nice to add.
Would this have any breaking changes? Does a non-promise function automatically resolve with await? I can't remember 😄

@spencercarli a for 2, good question. I'm fairly certain that if you do not return anything, it will behave the as if you returned a promise, eg. the return value (undefined) will be wrapped in Promise.resolve().

The transition animation occurs after the promise resolves (or immediately, if not promise is returned).

I'm not sure it will be immediate, it would be nice to do some manual testing to make sure everything looks the same if a non-promise is returned.

@vonovak is correct — if you await a non-promise, it evaluates to an immediately resolved promise.
However, that does means that execution is deferred until the next tick (setImmediate on RN) per the promise spec. As I've learned with my RN app, waiting for setImmediate can sometimes take a while, so I'll revise the code to be truly immediate if no promise is returned.

@vonovak, @spencercarli — I think everything has been addressed.

@spencercarli — I'm not sure it's a good idea to just swallow rejected promises. That should only happen if there's a bug in the user's code, and the unhandled rejection handler is the perfect way for them to see that.

You're completely right - going to merge this as soon as CI is done. Thanks for adding this ability!

I'm not sure why codecov is saying there is a decreased code coverage as there are no tests for the Transitioner as it stands 🤔


[Feature] Update base docker image to .NET 7

Currently, docker images use mcr.microsoft.com/dotnet/sdk:6.0-* (jammy or focal) as the base image.
You can check it out on utils/docker/Dockerfile.jammy or utils/docker/Dockerfile.focal files.
Please upgrade them or add another option using mcr.microsoft.com/dotnet/sdk:7.0-* so we can use it on .NET 7 projects.

The Docker images are using the latest LTS release. If you want to use a different .NET version, you can either create your own Docker image or install .NET 7 inside ours.
As of today we don't plan to release it with different dotnet version matrix.

Thanks for your quick response, Max.
Sure, I have created my own image, but I imagined that would be good if there was already an image ready to use as .NET 7 is not a preview or something and there are official .NET 7.0 images provided by Microsoft.


Rewrite functorch's vmap plumbing codegen

Motivation

Error message on template failures is hard to understand
Right now, there is a roughly 1 "codegenned function" : many "batching rules" relationship. It's kind of annoying to add functionality for a specific batching rule in the codegen; we have to add more template arguments to the codegenned function.

Pitch
We should rewrite the codegen in the style of PyTorch codegen, using things like PyTorch's codegen model: https://github.com/pytorch/pytorch/blob/master/tools/codegen/model.py . This will give us less friction in the long-term as well when we need to upstream functorch into pytorch/pytorch.

I did this


Issue starting the server

Node version - v18.16.1
npm version - 9.5.1

I am also facing the same issue. :(

I'm facing the same error, whenever I try to set builder to swc imports are not being set correctly in dist/main.js file.

Trying to figure it out. I cloned the project fresh and run
npm install
npm run start:dev

And Nest starts without any issues.
Did you make any changes? A repo to reproduce the error would be helpful.

You can see what I had to change to make swc work correctly ba67287.
Imports cannot start with src/path/to/import it must be the correct path to the file ./path/to/import. Maybe this helps.

Trying to figure it out. I cloned the project fresh and run
npm install
npm run start:dev

And Nest starts without any issues.
Did you make any changes? A repo to reproduce the error would be helpful.

I was getting the same when using yarn. I switched to npm, and it started successfully.


PPLUS error handling isn't consistent with Ferret's

Reported by Ansley B Manke on 11 Dec 2003 18:31 UTC
Here is a syntax error reported by a PPLUS command
yes? use levitus_climatology
yes? shade/lev=(-2:35:1) temp[k=2]
Syntax error
LEV,()(-2:35:1)
But here is a Ferret error
yes? shade temp[k:1,8}
**ERROR: command syntax: unpaired quotation marks, grave accent or
brackets
And in particular, LAS does not see the PPLUS errors.  Note
that these PPLUS errors do not necessarily stop execution of
the command (in the above example, a plot IS made) so they
are not on the same level as those which get an **ERROR message
from Ferret, but more like the warnings from Ferret that
output the string *** NOTE.  What does LAS do with warnings?
In addition, PPLUS has a  number of points where there is a
STOP in the code, e.g. in taxis0.F
IF(ITIME(9:10).NE.'00)STOP ',1'
These are cases that are outside the normal operation
of commands, or we'd be hearing reports of this happening,
but should they be treated in a more modern way?
Migrated-From: http://dunkel.pmel.noaa.gov/trac/ferret/ticket/746

Comment by<EMAIL_ADDRESS>on 11 Dec 2003 19:23 UTC
It turns out that LAS does not trap Ferret error strings containing '***ERROR'.
LAS traps warning strings containing '***NOTE'.  Some specific error strings are
handled and LAS spits out a transcript of the Ferret session for error messages
not handled.  In the case of the PPLUS error message above, LAS spit out the
session transcript except for the error message -- not sure why.

Comment by<EMAIL_ADDRESS>on 11 Dec 2003 19:57 UTC
We need to define what is an ERROR, what is a NOTE and whether there are any
more categories.  As a general rule, anything that causes Ferret to halt
execution is an ERROR, should appear on STDERROR and should have the error
indicator string prepended.  All other messages should appear on STDOUT and have
the note indicator string prepended.  If there is another category, then it
should be identified, given a name, sent to either STDOUT or STDERR and
prepended with an appropriate string.
Consistency is the key if Ferret is to interact with other software.
If I had my druthers, I'd go so far as to make ' *** NOTE: ' and ' **ERROR: '
more consistent with eachother.  An example:
yes? define axis/t=1:12/unit=month t_month
*** NOTE: /UNIT=MONTHS is ambiguous ... using 1/12 of 365.2425 days
**ERROR: improper grid or axis definition: error in start,end,delta

Comment by<EMAIL_ADDRESS>on 16 May 2005 16:44 UTC
Removing Joe Mclean from the CC list after Joe's departure.


feat: more protocol metadata info

It would be cool to add more keys in the metadata section in order to document code versioning.
for instance add:
more details than what "source" now reports
protocol_validation = "draft" "in development" "verified/validated" "production"
info about the current code version
code_version or script_version = "1.00a"
.. script_date = "2021-08-12"
.. script_comment = "draft code, will be verified" or "verified / validated by<EMAIL_ADDRESS>this kind of things present in all well written shared bioinfo scripts!

Thanks for the feature request!
To clarify, are you expecting these additional keys to show up in the Opentrons App somewhere, or do you just want the extra keys for seeing in a Python protocol's source code?

Mainly in the source code but seeing it on screen when running would not hurt either
Thanks
Sent from my smartphone

From: Max Marrone @.>
Sent: Friday, August 13, 2021 7:51:26 PM
To: Opentrons/opentrons @.>
Cc: Stéphane Plaisance @.>; Author @.>
Subject: Re: [Opentrons/opentrons] feat: more metadata info (#8236)
Thanks for the feature request!
To clarify, are you expecting these additional keys to show up in the Opentrons App somewhere, or do you just want the extra keys for seeing in a Python protocol's source code?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/Opentrons/opentrons/issues/8236#issuecomment-898624565, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAGRTFDCP55ZA53PTOI5HYTT4VLR5ANCNFSM5CARY5BA.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email.

as discussed with Ethan, a similar metadata tag in the labware definition files would be essential as these also change upon time and you now may not know which version you are working with.

Today:

You can include arbitrary custom fields in metadata. Currently, only strings are allowed.
We haven't yet figured out a strategy for avoiding naming collisions between user-defined custom fields and official Opentrons fields. Until we figure that out, I strongly recommend giving your custom fields some unique prefix, like this:
 metadata = {
     apiLevel = "2.11",
     myCompanyProtocolVersion = "1.00a",
     myCompanyProtocolValidation = "draft",
 }

You can also, of course, record your custom information in a regular Python comment, like this:
# Protocol version: 1.00a
# Protocol validation: draft

metadata = {
    apiLevel = "2.11",
}

Or in some custom structure, like this:
my_company_metadata = {
    protocolVersion: "1.00a",
    protocolValidation: "draft",
}

metadata = {
    apiLevel = "2.11",
}

In the future:

We would like to formally specify what official metadata fields exist, to make it easier for protocol authors to use them correctly. See #8334. This will also include specifying a way for protocol authors to define their own custom metadata fields without worrying about naming collisions with our official ones.

Great implementation. I will use the proposed keys until more is announced.
Since it seems comment lines are not supported in json, how will we do the same in custom labware files?
Best regards and thanks for the nice work

OK, thank Max for the info


pydantic.mypy from_attributes config check does not work with deprecated .from_orm() and gives false positives for v1.BaseModel

Initial Checks

[X] I confirm that I'm using Pydantic V2

Description
pydantic.mypy.PydanticPlugin.get_method_hook that is supposed to run pydantic.mypy.from_attributes_callback for each from_orm invocation does not work with @typing_extensions.deprecated on pydantic.main.BaseModel.from_orm.
https://github.com/pydantic/pydantic/blob/4978ee235bf5f0fa11159b2dfe46068ef3deba0a/pydantic/mypy.py#L160
Furthermore, when using both v1 and v2 for migration period with both pydantic.v1.mypy and pydantic.mypy enabled the "<ModelName>" does not have from_attributes=True  [pydantic-orm] is getting raised for pydantic.v1.BaseModel models that should not be checked by pydantic.mypy plugin.
Minimal example provided.
First bug can be easily tested by commenting out the deprecation decorator and running mypy again.
Second bug can be easily tested by adding following snippet to pydantic.mypy.from_attributes_callback after if pydantic_metadata is None: check
    if not any(base.fullname == BASEMODEL_FULLNAME for base in model_type.type.mro):
        # not a Pydantic v2 model
        return ctx.default_return_type

Example Code
from dataclasses import dataclass
from typing import Optional

from pydantic import BaseModel, ConfigDict
from pydantic.v1 import BaseModel as BaseModelV1

@dataclass
class CustomObject:
    x: int
    y: Optional[int]

obj = CustomObject(x=1, y=2)

class CustomModel(BaseModel):
    model_config = ConfigDict(
        from_attributes=True,
        strict=True,
    )

    x: int

cm = CustomModel.from_orm(obj)

class CustomModelBadConfig(BaseModel):
    model_config = ConfigDict(
        strict=True,
    )

    x: int

cmnc = CustomModelBadConfig.from_orm(obj)
# should be a mypy error: "CustomModelBadConfig" does not have from_attributes=True  [pydantic-orm]

class CustomV1Model(BaseModelV1):
    class Config:
        orm_mode = True

    x: int

cmv1 = CustomV1Model.from_orm(obj)
# shouldn't be an error but gives: "CustomV1Model" does not have from_attributes=True  [pydantic-orm]

Python, Pydantic & OS Version
pydantic version: 2.8.2
        pydantic-core version: 2.20.1
          pydantic-core build: profile=release pgo=false
                 install path: /home/<redacted>/venv/lib/python3.11/site-packages/pydantic
               python version: 3.11.8 (main, Mar 12 2024, 09:06:51) [GCC 10.2.1 20210110]
                     platform: Linux-6.5.0-15-generic-aarch64-with-glibc2.31
             related packages: mypy-1.10.1 typing_extensions-4.12.2
                       commit: unknown

Added a PR with described changes, the decorator issue still remains.

@sydney-runkle Would be worth splitting it into the @deprecation bug causing false negatives for pydantic-orm error and the one with fix PR for false positives on v1.BaseModels?
Seems that the false negatives on current version are even more severe issue but that is out of my expertise and may need action on mypy side for https://github.com/python/mypy/issues/9915 like @dmontagu mentioned.

I also wonder if the from_attributes check is in good place, as it is only checked for True and never used. Seems it should be passed down to model_validate(obj, from_attributes=from_attributes) or taken from the config in there if not passed directly (and then checked by mypy for calls to model_validate not from_orm).


[ADD] Python subcategory under youtube

Category Name
none
Subcategory Name
Python
Additional Context
Also moving this link from Languages/Python to Youtube/Python

Checklist

[X] I have checked the existing issues
[X] I have read the Contributing Guidelines
[ ] I have checked that this category does not exist
[X] I have checked that this subcategory does not exist
[X] I am willing to work on this issue (optional)
[ ] I am a GSSoC'23 contributor

@CBID2 @ujjawaltyagii Should there be 2 seperate python subcategories or not ? I think would be better if all yt resources come under a single category.

@navharsh I get what you are trying to say about the moving that link then we will have two same sub-category but if we just move all Yt resources under a single Yt category then wouldn't it be hard for people to find the right resources, sub-categories make resources organized.

@ujjawaltyagii yeah I think that can also cause a problem , I guess I should let it how it is for now untill a better solution comes up.

yep !!


Playlist function not working

Expected Behavior
I tried to make a playlist out of a number of songs by clicking on the playlist button.
Actual Behavior
The loading bar came up and never left. I noticed that it created a playlist file in my drive, so I clicked on it and the loading bar did the same thing (see attached image).
Steps to Reproduce the Problem

Click on playlist button

Specifications

Browser: Chrome
OS: Mac 10.12.6

Bugger!
Google just have to link Google Play Music so songs dont have to be
re-uploaded and all is solved!! (probably harder than it seems).
You'd think there would be a big demand for a good quality cloud based
music player.
cheers
Sam
On Fri, Jan 4, 2019 at 11:23 AM moonfacedindividual <
<EMAIL_ADDRESS>wrote:

Yeah, join the club corefremantle. Many of us users have been complaining
about this since the second week of Dec both on this forum and in the
comments section in the Google Chrome store. Apparently, the site developer
is MIA, or else this is a problem that can’t be corrected. Perhaps Google
will come out with their own dedicated player designed exclusively for
Google Drive.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/nicolasgarnier/drive-music-player/issues/15#issuecomment-451344693,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ARaeNIQAH3sV_mGaq6Lvbjc_adY_1m6sks5u_skggaJpZM4ZpFox
.

oh and any luck with other apps? This one seems ok:
https://github.com/jakubroztocil/cloudtunes
On Fri, Jan 4, 2019 at 11:23 AM moonfacedindividual <
<EMAIL_ADDRESS>wrote:

Yeah, join the club corefremantle. Many of us users have been complaining
about this since the second week of Dec both on this forum and in the
comments section in the Google Chrome store. Apparently, the site developer
is MIA, or else this is a problem that can’t be corrected. Perhaps Google
will come out with their own dedicated player designed exclusively for
Google Drive.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/nicolasgarnier/drive-music-player/issues/15#issuecomment-451344693,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ARaeNIQAH3sV_mGaq6Lvbjc_adY_1m6sks5u_skggaJpZM4ZpFox
.

@corefremantle it appears to be working this morning for me, please give it a try and see if you have the same result.

Gave it a shot just now, no luck :/ Still working for you?
Know any developers who want to open up the project? :P Seriously thinking it would be a very successful app if someone put in a bit of effort.

It looks like the app doesn't have the correct permissions to create playlists this way. Digging into my Google account, Google Drive permissions for the app are:
- Add itself to Google Drive
- View and manage Google Drive files and folders that you have opened or created with this app

Creating a playlist from Google Drive itself works, I'm assuming because I explicitly opened with the driveplayer app.
Response from API when attempting to create a playlist from the driveplayer website:

Related: https://github.com/nicolasgarnier/drive-music-player/issues/24 https://github.com/nicolasgarnier/drive-music-player/issues/18 https://github.com/nicolasgarnier/drive-music-player/issues/17 https://github.com/nicolasgarnier/drive-music-player/issues/16 https://github.com/nicolasgarnier/drive-music-player/issues/27

Gave it a shot just now, no luck :/ Still working for you?
Know any developers who want to open up the project? :P Seriously thinking it would be a very successful app if someone put in a bit of effort.

@corefremantle, I have noted limited improvement since last Monday.  I am now able to set up and play files on the Drive Player for the first time in about two months but if I try to save them as a playlist, that is when I have problems.  Also, I can't get my existing playlists to open up and play.


example URL in 231 is block in PRC

Could we switch the link to a local file, or a link in github ?
https://ichef.bbci.co.uk/news/976/cpsprodpb/3970/production/_108240741_beatles-abbeyroad-square-reuters-applecorps.jpg

Internal ref CVS-105407


1.0.2? 1.1.0? release

Dont you want to release the new version?
The map is not rendered under https, as long as the css and js URL is cdn.leafletjs.com and not cdnjs.cloudflare.com.
Please release, it is a critical bug!

@szabogyula  not sure if you are still interested but I've added locally hosted files plus admin settings for the plugin here https://github.com/JohnMica/GetGrav-Leaflet-Map
not sure @magikcypress  is maintaining this plugin anymore


[Bug]: 500 Internal Server Error when running shopify app dev

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?
App
Expected behavior
Expected behavior
When running shopify app dev, the command should successfully start the development server and set up the environment.
Actual behavior
Actual behavior
The command fails with a 500 Internal Server Error.
I've had this issue before but has usually been solved on the Shopify side as a more global issue. To verify this time that it does not seem to be a "global" issue, I created a blank/new project and was able to successfully start the development server by running shopify app dev. When added the --verbose flag to the fresh project and current project with the 500 error, I noticed the area that the command seems to be failing. See the output below:
2024-11-21T15:52:15.016Z: Request to https://partners.shopify.com/api/cli/graphql completed in 584 ms
With response headers:
cache-control: max-age=0, private, must-revalidate
content-type: application/json; charset=utf-8
etag: W/"307ce8c20eb717c29fecaea0a7e9e910"
server-timing: processing;dur=404, socket_queue;dur=1.888, util;dur=0.3, cfRequestDuration;dur=510.999918
x-request-id: d6eba42a-65ba-4b37-98aa-2d5c6a328ee7-1732204334
Error message:
The Partners GraphQL API responded unsuccessfully with errors:
[
{
"message": "Unexpected system error",
"extensions": {
"code": "500"
}
}
]
Request ID: d6eba42a-65ba-4b37-98aa-2d5c6a328ee7-1732204334

Additional context

The error occurs after successfully setting up the Cloudflare tunnel
The app URLs are successfully updated before the error occurs
Shopify Support has confirmed seeing the 500 response but cannot determine the source
Also receive 500 error when trying to run shopify app deploy
Already attempted:

Re-running the command
Logging out and back in
Using --reset flag
Confirming env vars are correct
Confirmed appropriate configs are linked correctly
Confirmed all scopes match Partner Dashboard

Verbose output
Based on the verbose output, fails trying to fetch extension registrations from the Partners API.

### Verbose output

shopify app dev --verbose
2024-11-21T15:52:04.278Z: Running command app dev
2024-11-21T15:52:04.281Z: Notifications to show: 0
2024-11-21T15:52:04.290Z: Reading cached app information for directory /Users/**/Projects/Shopify Apps/matchbox...
2024-11-21T15:52:04.291Z: Reading the content of file at shopify.app.local.toml...
2024-11-21T15:52:04.293Z: Reading the content of file at shopify.app.local.toml...
2024-11-21T15:52:04.294Z: Ensuring that the user is authenticated with the Partners API with the following scopes:
[]

2024-11-21T15:52:04.295Z: Getting session store...
2024-11-21T15:52:04.296Z: 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:
{
  "partnersApi": {
    "scopes": []
  }
}

2024-11-21T15:52:04.296Z: Sending Identity Introspection request to URL: https://accounts.shopify.com/oauth/introspection
2024-11-21T15:52:04.296Z: Sending POST request to URL https://accounts.shopify.com/oauth/introspection
With request headers:
 - User-Agent: Shopify CLI; v=3.70.0
 - Keep-Alive: timeout=30
 - Sec-CH-UA-PLATFORM: darwin
 - Content-Type: application/json

2024-11-21T15:52:04.620Z: Request to https://accounts.shopify.com/oauth/introspection completed in 323 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/"0192dd5b26d018924fbd8c1b4a4e0601"
 - server-timing: processing;dur=30, socket_queue;dur=1.605, edge;dur=1.022, util;dur=0.05, cfRequestDuration;dur=210.000038
 - x-request-id: 639353d4-8948-411a-b8d5-9b12ea1202e4-1732204324

2024-11-21T15:52:04.624Z: The identity token is valid: true
2024-11-21T15:52:04.624Z:
The validation of the token for application/identity completed with the following results:
- It's expired: false
- It's invalid in identity: false

2024-11-21T15:52:04.625Z: Verifying that the user has a Partner organization
2024-11-21T15:52:04.626Z: Confirmed partner account exists from cache
2024-11-21T15:52:04.626Z: Getting partner account info from cache
2024-11-21T15:52:04.633Z: Sending "Partners" GraphQL request:
  query FindApp($apiKey: String!) {
    app(apiKey: $apiKey) {
      id
      title
      apiKey
      organizationId
      apiSecretKeys {
        secret
      }
      appType
      grantedScopes
      applicationUrl
      redirectUrlWhitelist
      requestedAccessScopes
      webhookApiVersion
      embedded
      posEmbedded
      preferencesUrl
      gdprWebhooks {
        customerDeletionUrl
        customerDataRequestUrl
        shopDeletionUrl
      }
      appProxy {
        subPath
        subPathPrefix
        url
      }
      developmentStorePreviewEnabled
      disabledFlags
    }
  }

With variables:
{
  "apiKey": "*****"
}

With request headers:
 - User-Agent: Shopify CLI; v=3.70.0
 - Keep-Alive: timeout=30
 - Sec-CH-UA-PLATFORM: darwin
 - Content-Type: application/json

to https://partners.shopify.com/api/cli/graphql
2024-11-21T15:52:06.213Z: Request to https://partners.shopify.com/api/cli/graphql completed in 1578 ms
With response headers:
 - cache-control: max-age=0, private, must-revalidate
 - content-type: application/json; charset=utf-8
 - etag: W/"2e0c92862c2ff2321c0fc539cf3569df"
 - server-timing: processing;dur=534, socket_queue;dur=2.558, util;dur=0.5, cfRequestDuration;dur=649.999857
 - x-request-id: 57bc0f19-6c36-44a1-9f64-a206c9d6d26a-1732204325

2024-11-21T15:52:06.218Z: Sending "Partners" GraphQL request:
  query FindOrganization($id: ID!) {
    organizations(id: $id, first: 1) {
      nodes {
        id
        businessName
      }
    }
  }

With variables:
{
  "id": "3809606"
}

With request headers:
 - User-Agent: Shopify CLI; v=3.70.0
 - Keep-Alive: timeout=30
 - Sec-CH-UA-PLATFORM: darwin
 - Content-Type: application/json

to https://partners.shopify.com/api/cli/graphql
2024-11-21T15:52:06.466Z: Request to https://partners.shopify.com/api/cli/graphql completed in 248 ms
With response headers:
 - cache-control: max-age=0, private, must-revalidate
 - content-type: application/json; charset=utf-8
 - etag: W/"e6e1e28f3b2e5bcc313e18c72106ff4b"
 - server-timing: processing;dur=73, socket_queue;dur=1.935, util;dur=0.3, cfRequestDuration;dur=171.000004
 - x-request-id: b26d8d0b-e0bc-4e33-8f39-da3ce61ff7dd-1732204326

2024-11-21T15:52:06.472Z: Sending "Partners" GraphQL request:
  query fetchSpecifications($api_key: String!) {
    extensionSpecifications(apiKey: $api_key) {
      name
      externalName
      externalIdentifier
      identifier
      gated
      experience
      options {
        managementExperience
        registrationLimit
      }
      features {
        argo {
          surface
        }
      }
      validationSchema {
        jsonSchema
      }
    }
  }

With variables:
{
  "api_key": "***"
}

With request headers:
 - User-Agent: Shopify CLI; v=3.70.0
 - Keep-Alive: timeout=30
 - Sec-CH-UA-PLATFORM: darwin
 - Content-Type: application/json

to https://partners.shopify.com/api/cli/graphql
2024-11-21T15:52:07.142Z: Request to https://partners.shopify.com/api/cli/graphql completed in 669 ms
With response headers:
 - cache-control: max-age=0, private, must-revalidate
 - content-type: application/json; charset=utf-8
 - etag: W/"13fe689d1191dc8864cfd658646d5359"
 - server-timing: processing;dur=194, socket_queue;dur=7.534, util;dur=0.5, cfRequestDuration;dur=335.999966
 - x-request-id: b937a53a-d7ed-4c10-94c4-b2040351a7bf-1732204326

2024-11-21T15:52:07.149Z: The following extension specifications were defined locally but not found in the remote specifications: data, payments_extension, tax_calculation
2024-11-21T15:52:07.151Z: Reading the content of file at shopify.app.staging.toml...
2024-11-21T15:52:07.151Z: Reading the content of file at shopify.app.toml...
2024-11-21T15:52:07.225Z: Reading the content of file at package.json...
2024-11-21T15:52:07.225Z: Reading the content of file at package.json...
2024-11-21T15:52:07.227Z:
Running system process:
  · Command: npm prefix
  · Working directory: /Users/**/Projects/Shopify Apps/matchbox

2024-11-21T15:52:07.327Z: Obtaining the dependency manager in directory /Users/**/Projects/Shopify Apps/matchbox...
2024-11-21T15:52:07.328Z:
Running system process:
  · Command: shopify version
  · Working directory: /Users/**/Projects/Shopify Apps/matchbox

2024-11-21T15:52:08.206Z: Reading the content of file at shopify.web.toml...
2024-11-21T15:52:08.209Z: Reading the content of file at package.json...
2024-11-21T15:52:08.209Z: Notifications to show: 0
2024-11-21T15:52:08.210Z: Reading cached app information for directory /Users/**/Projects/Shopify Apps/matchbox...
2024-11-21T15:52:08.210Z: Storing app information for directory /Users/**/Projects/Shopify Apps/matchbox:{
  "appId": "eff13ed96fe994087beac83f2a236180",
  "title": "Matchbox",
  "directory": "/Users/**/Projects/Shopify Apps/matchbox",
  "orgId": "***"
}
2024-11-21T15:52:08.220Z: Sending "Partners" GraphQL request:
  query FindOrganization($orgId: ID!, $shopDomain: String) {
    organizations(id: $orgId, first: 1) {
      nodes {
        id
        businessName
        stores(shopDomain: $shopDomain, first: 1, archived: false) {
          nodes {
            shopId
            link
            shopDomain
            shopName
            transferDisabled
            convertableToPartnerTest
          }
        }
      }
    }
  }

With variables:
{
  "orgId": "****",
  "shopDomain": "quickstart-6c746599.myshopify.com"
}

With request headers:
 - User-Agent: Shopify CLI; v=3.70.0
 - Keep-Alive: timeout=30
 - Sec-CH-UA-PLATFORM: darwin
 - Content-Type: application/json

to https://partners.shopify.com/api/cli/graphql
2024-11-21T15:52:08.580Z: Request to https://partners.shopify.com/api/cli/graphql completed in 360 ms
With response headers:
 - cache-control: max-age=0, private, must-revalidate
 - content-type: application/json; charset=utf-8
 - etag: W/"8fb965c09ebec0faac4f517808983934"
 - server-timing: processing;dur=170, socket_queue;dur=2.239, util;dur=0.3, cfRequestDuration;dur=277.000189
 - x-request-id: 72b2e035-ab42-4f6f-a552-1a3cb66ab756-1732204328

2024-11-21T15:52:08.581Z: Getting a random port...
2024-11-21T15:52:08.585Z: Random port obtained: 63710
2024-11-21T15:52:08.611Z: cloudflared already installed, skipping
2024-11-21T15:52:08.613Z:
Running system process:
  · Command: /Users/**/.nvm/versions/node/v20.16.0/lib/node_modules/@shopify/cli/bin/cloudflared tunnel --url http://localhost:63710 --no-autoupdate
  · Working directory: /Users/**/Projects/Shopify Apps/matchbox

2024-11-21T15:52:08.617Z: Sending "Partners" GraphQL request:
  query activeAppVersion($apiKey: String!) {
    app(apiKey: $apiKey) {
      activeAppVersion {
        appModuleVersions {
          registrationId
          registrationUuid
          registrationTitle
          type
          config
          specification {
            identifier
            name
            experience
            options {
              managementExperience
            }
          }
        }
      }
    }
  }

With variables:
{
  "apiKey": "*****"
}

With request headers:
 - User-Agent: Shopify CLI; v=3.70.0
 - Keep-Alive: timeout=30
 - Sec-CH-UA-PLATFORM: darwin
 - Content-Type: application/json

to https://partners.shopify.com/api/cli/graphql
2024-11-21T15:52:08.625Z: 2024-11-21T15:52:08Z INF Thank you for trying Cloudflare Tunnel. Doing so, without a Cloudflare account, is a quick way to experiment and try it out. However, be aware that these account-less Tunnels have no uptime guarantee. If you intend to use Tunnels in production you should use a pre-created named tunnel by following: https://developers.cloudflare.com/cloudflare-one/connections/connect-apps
2024-11-21T15:52:08Z INF Requesting new quick Tunnel on trycloudflare.com...

2024-11-21T15:52:09.158Z: Request to https://partners.shopify.com/api/cli/graphql completed in 541 ms
With response headers:
 - cache-control: max-age=0, private, must-revalidate
 - content-type: application/json; charset=utf-8
 - etag: W/"c61cddb9a761a0f1cfc597e5975b2b6c"
 - server-timing: processing;dur=306, socket_queue;dur=2.396, util;dur=0.3, cfRequestDuration;dur=448.999882
 - x-request-id: 23a1f973-e8f7-49ea-adb2-69abcc693939-1732204328

2024-11-21T15:52:09.162Z: Reading cached app information for directory /Users/**/Projects/Shopify Apps/matchbox...
╭─ info ───────────────────────────────────────────────────────────────────────╮
│                                                                              │
│  Using shopify.app.local.toml for default values:                            │
│                                                                              │
│    • Org:             Matchbox                                               │
│    • App:             Matchbox                                               │
│    • Dev store:       quickstart-6c746599.myshopify.com                      │
│    • Update URLs:     Yes                                                    │
│                                                                              │
│   You can pass  `--reset`  to your command to reset your app configuration.  │
│                                                                              │
╰──────────────────────────────────────────────────────────────────────────────╯

2024-11-21T15:52:09.204Z: Port 3457 is free
2024-11-21T15:52:09.206Z: Polling tunnel status for cloudflare (attempt 0): starting
2024-11-21T15:52:09.206Z: Getting a random port...
2024-11-21T15:52:09.207Z: Random port obtained: 63718
2024-11-21T15:52:09.708Z: Polling tunnel status for cloudflare (attempt 1): starting
2024-11-21T15:52:10.210Z: Polling tunnel status for cloudflare (attempt 2): starting
2024-11-21T15:52:10.711Z: Polling tunnel status for cloudflare (attempt 3): starting
2024-11-21T15:52:11.220Z: Polling tunnel status for cloudflare (attempt 4): starting
2024-11-21T15:52:11.724Z: Polling tunnel status for cloudflare (attempt 5): starting
2024-11-21T15:52:12.226Z: Polling tunnel status for cloudflare (attempt 6): starting
2024-11-21T15:52:12.729Z: Polling tunnel status for cloudflare (attempt 7): starting
2024-11-21T15:52:13.229Z: Polling tunnel status for cloudflare (attempt 8): starting
2024-11-21T15:52:13.346Z: 2024-11-21T15:52:13Z INF +--------------------------------------------------------------------------------------------+
2024-11-21T15:52:13Z INF |  Your quick Tunnel has been created! Visit it at (it may take some time to be reachable):  |
2024-11-21T15:52:13Z INF |  https://surplus-narrow-hanging-bear.trycloudflare.com                                     |
2024-11-21T15:52:13Z INF +--------------------------------------------------------------------------------------------+

2024-11-21T15:52:13.347Z: 2024-11-21T15:52:13Z INF Cannot determine default configuration path. No file [config.yml config.yaml] in [~/.cloudflared ~/.cloudflare-warp ~/cloudflare-warp /etc/cloudflared /usr/local/etc/cloudflared]
2024-11-21T15:52:13Z INF Version 2024.8.2
2024-11-21T15:52:13Z INF GOOS: darwin, GOVersion: go1.22.2-devel-cf, GoArch: arm64
2024-11-21T15:52:13Z INF Settings: map[ha-connections:1 no-autoupdate:true protocol:quic url:http://localhost:63710]

2024-11-21T15:52:13.347Z: 2024-11-21T15:52:13Z INF Generated Connector ID: 8b55ddb5-a58a-4104-a6ec-ade786e3f597

2024-11-21T15:52:13.394Z: 2024-11-21T15:52:13Z INF Initial protocol quic

2024-11-21T15:52:13.394Z: 2024-11-21T15:52:13Z INF ICMP proxy will use <IP_ADDRESS> as source for IPv4

2024-11-21T15:52:13.394Z: 2024-11-21T15:52:13Z INF ICMP proxy will use fe80::7f:c312:d4d2:9369 in zone en0 as source for IPv6

2024-11-21T15:52:13.394Z: 2024-11-21T15:52:13Z INF Created ICMP proxy listening on <IP_ADDRESS>:0
2024-11-21T15:52:13Z INF Created ICMP proxy listening on [fe80::7f:c312:d4d2:9369%en0]:0

2024-11-21T15:52:13.419Z: 2024-11-21T15:52:13Z INF Starting metrics server on <IP_ADDRESS>:63723/metrics

2024-11-21T15:52:13.486Z: 2024-11-21T15:52:13Z ERR update check failed error="no release found"

2024-11-21T15:52:13.634Z: 2024-11-21T15:52:13Z INF Registered tunnel connection connIndex=0 connection=ecc3a371-dca3-43d1-8e32-819ac900658e event=0 ip=<IP_ADDRESS> location=lax05 protocol=quic

2024-11-21T15:52:13.731Z: Polling tunnel status for cloudflare (attempt 9): connected
2024-11-21T15:52:13.731Z: Reading cached app information for directory /Users/**/Projects/Shopify Apps/matchbox...
2024-11-21T15:52:13.738Z: Sending "Partners" GraphQL request:
  mutation appUpdate($apiKey: String!, $applicationUrl: Url!, $redirectUrlWhitelist: [Url]!, $appProxy: AppProxyInput) {
    appUpdate(
      input: {
        apiKey: $apiKey
        applicationUrl: $applicationUrl
        redirectUrlWhitelist: $redirectUrlWhitelist
        appProxy: $appProxy
      }
    ) {
      userErrors {
        message
        field
      }
    }
  }

With variables:
{
  "apiKey": "*****",
  "applicationUrl": "https://surplus-narrow-hanging-bear.trycloudflare.com",
  "redirectUrlWhitelist": [
    "https://surplus-narrow-hanging-bear.trycloudflare.com/auth/callback",
    "https://surplus-narrow-hanging-bear.trycloudflare.com/auth/shopify/callback",
    "https://surplus-narrow-hanging-bear.trycloudflare.com/api/auth/callback"
  ]
}

With request headers:
 - User-Agent: Shopify CLI; v=3.70.0
 - Keep-Alive: timeout=30
 - Sec-CH-UA-PLATFORM: darwin
 - Content-Type: application/json

to https://partners.shopify.com/api/cli/graphql
2024-11-21T15:52:14.413Z: Request to https://partners.shopify.com/api/cli/graphql completed in 675 ms
With response headers:
 - cache-control: max-age=0, private, must-revalidate
 - content-type: application/json; charset=utf-8
 - etag: W/"76acb4e44b91f928c3744a856cacdd2e"
 - server-timing: processing;dur=482, socket_queue;dur=2.177, util;dur=0.4, cfRequestDuration;dur=599.999905
 - x-request-id: 62919c14-03db-495f-b878-58352bfe5c75-1732204333

2024-11-21T15:52:14.416Z: Reading the content of file at shopify.app.local.toml...
2024-11-21T15:52:14.422Z: Writing some content to file at shopify.app.local.toml...
2024-11-21T15:52:14.431Z: Sending "Partners" GraphQL request:
  query allAppExtensionRegistrations($apiKey: String!) {
    app(apiKey: $apiKey) {
      extensionRegistrations {
        id
        uuid
        title
        type
        draftVersion {
          config
          context
        }
        activeVersion {
          config
          context
        }
      }
      configurationRegistrations {
        id
        uuid
        title
        type
        draftVersion {
          config
          context
        }
        activeVersion {
          config
          context
        }
      }
      dashboardManagedExtensionRegistrations {
        id
        uuid
        title
        type
        activeVersion {
          config
          context
        }
        draftVersion {
          config
          context
        }
      }
    }
  }

With variables:
{
  "apiKey": "*****"
}

With request headers:
 - User-Agent: Shopify CLI; v=3.70.0
 - Keep-Alive: timeout=30
 - Sec-CH-UA-PLATFORM: darwin
 - Content-Type: application/json

to https://partners.shopify.com/api/cli/graphql
2024-11-21T15:52:15.016Z: Request to https://partners.shopify.com/api/cli/graphql completed in 584 ms
With response headers:
 - cache-control: max-age=0, private, must-revalidate
 - content-type: application/json; charset=utf-8
 - etag: W/"307ce8c20eb717c29fecaea0a7e9e910"
 - server-timing: processing;dur=404, socket_queue;dur=1.888, util;dur=0.3, cfRequestDuration;dur=510.999918
 - x-request-id: d6eba42a-65ba-4b37-98aa-2d5c6a328ee7-1732204334

╭─ error ──────────────────────────────────────────────────────────────────────╮
│                                                                              │
│                                                                              │
│  The Partners GraphQL API responded unsuccessfully with errors:              │
│                                                                              │
│  [                                                                           │
│    {                                                                         │
│      "message": "Unexpected system error",                                   │
│      "extensions": {                                                         │
│        "code": "500"                                                         │
│      }                                                                       │
│    }                                                                         │
│  ]                                                                           │
│                                                                              │
│  Request ID: d6eba42a-65ba-4b37-98aa-2d5c6a328ee7-1732204334                 │
│                                                                              │
│                                                                              │
│  To investigate the issue, examine this stack trace:                         │
│    at makeRequest (Users/**/.nvm/versions/node/v20.16.0/lib/nod  │
│    e_modules/@shopify/cli/dist/chunk-GDYKHT64.js:27240)                      │
│    at processTicksAndRejections (node:internal/process/task_queues:95)       │
│    at async makeVerboseRequest (Users/**/.nvm/versions/node/v20  │
│    .16.0/lib/node_modules/@shopify/cli/dist/chunk-GDYKHT64.js:27270)         │
│    at async retryAwareRequest (Users/**/.nvm/versions/node/v20.  │
│    16.0/lib/node_modules/@shopify/cli/dist/chunk-GDYKHT64.js:27346)          │
│    at (Users/**/.nvm/versions/node/v20.16.0/lib/node_modules/@s  │
│    hopify/cli/dist/chunk-5OP2SA7G.js:3269)                                   │
│    at (Users/**/.nvm/versions/node/v20.16.0/lib/node_modules/@s  │
│    hopify/cli/dist/chunk-PJKCWDDX.js:29947)                                  │
│                                                                              │
╰──────────────────────────────────────────────────────────────────────────────╯

2024-11-21T15:52:15.040Z:
Running system process:
  · Command: npm prefix
  · Working directory: /Users/**/Projects/Shopify Apps/matchbox

2024-11-21T15:52:15.146Z: Obtaining the dependency manager in directory /Users/**/Projects/Shopify Apps/matchbox...
2024-11-21T15:52:15.433Z: Request to https://monorail-edge.shopifysvc.com/v1/produce completed in 174 ms
With response headers:
 - x-request-id: 8f29ccba-da79-4b59-b0f1-309c3abfa76d

2024-11-21T15:52:15.434Z: Analytics event sent: {
  "command": "app dev",
  "time_start":<PHONE_NUMBER>279,
  "time_end":<PHONE_NUMBER>038,
  "total_time": 10759,
  "success": false,
  "cli_version": "3.70.0",
  "ruby_version": "",
  "node_version": "20.16.0",
  "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": "***",
  "env_cloud": "localhost",
  "env_package_manager": "npm",
  "env_is_global": true,
  "env_auth_method": "device_auth",
  "cmd_app_warning_api_key_deprecation_displayed": false,
  "cmd_app_all_configs_any": true,
  "cmd_app_all_configs_clients": "{\"shopify.app.local.toml\":\"eff13ed96fe994087beac83f2a236180\",\"shopify.app.staging.toml\":\"1a129c4a53d77ce25c9e81b043a6093f\",\"shopify.app.toml\":\"1a129c4a53d77ce25c9e81b043a6093f\"}",
  "cmd_app_linked_config_used": true,
  "cmd_app_linked_config_name": "shopify.app.local.toml",
  "cmd_app_linked_config_git_tracked": true,
  "cmd_app_linked_config_source": "cached",
  "cmd_app_linked_config_uses_cli_managed_urls": true,
  "project_type": "node",
  "app_extensions_any": false,
  "app_extensions_breakdown": "{}",
  "app_extensions_count": 0,
  "app_extensions_custom_layout": false,
  "app_extensions_function_any": false,
  "app_extensions_function_count": 0,
  "app_extensions_theme_any": false,
  "app_extensions_theme_count": 0,
  "app_extensions_ui_any": false,
  "app_extensions_ui_count": 0,
  "app_name_hash": "***",
  "app_path_hash": "***",
  "app_scopes": "[\"read_customers\",\"read_discounts\",\"read_fulfillments\",\"read_inventory\",\"read_orders\",\"read_price_rules\",\"read_product_listings\",\"read_products\",\"unauthenticated_read_customers\",\"unauthenticated_write_customers\",\"write_assigned_fulfillment_orders\",\"write_customers\",\"write_discounts\",\"write_fulfillments\",\"write_inventory\",\"write_orders\",\"write_price_rules\",\"write_products\"]",
  "app_web_backend_any": true,
  "app_web_backend_count": 1,
  "app_web_custom_layout": true,
  "app_web_framework": "remix",
  "app_web_frontend_any": true,
  "app_web_frontend_count": 1,
  "env_package_manager_workspaces": true,
  "partner_id": ****,
  "api_key": "****",
  "cmd_app_reset_used": false,
  "store_fqdn_hash": "***",
  "cmd_all_timing_network_ms": 4984,
  "cmd_all_timing_prompts_ms": 0,
  "cmd_all_launcher": "unknown",
  "cmd_all_topic": "app",
  "cmd_all_plugin": "@shopify/app",
  "cmd_all_verbose": true,
  "cmd_all_path_override": true,
  "cmd_all_path_override_hash": "***",
  "cmd_app_dependency_installation_skipped": false,
  "cmd_dev_tunnel_type": "cloudflare",
  "cmd_all_last_graphql_request_id": "62919c14-03db-495f-b878-58352bfe5c75-1732204333",
  "cmd_all_timing_active_ms": 5774,
  "cmd_all_exit": "unexpected_error",
  "user_id": "***",
  "args": "--verbose",
  "error_message": "\nThe Partners GraphQL API responded unsuccessfully with errors:\n\n\u001b[33m[\n  {\n    \u001b[0m\u001b[37m\"message\":\u001b[33m \u001b[0m\u001b[32m\"Unexpected system error\"\u001b[33m,\n    \u001b[0m\u001b[37m\"extensions\":\u001b[33m {\n      \u001b[0m\u001b[37m\"code\":\u001b[33m \u001b[0m\u001b[32m\"500\"\u001b[33m\n    }\n  }\n]\u001b[0m\n      \nRequest ID: d6eba42a-65ba-4b37-98aa-2d5c6a328ee7-1732204334\n",
  "app_name": "matchbox",
  "store_fqdn": "quickstart-6c746599.myshopify.com",
  "env_plugin_installed_all": "[\"@shopify/cli\"]",
  "metadata": "{\"extraPublic\":{},\"extraSensitive\":{}}"
}
2024-11-21T15:52:15.447Z: Reporting unhandled error to Bugsnag:
The Partners GraphQL API responded unsuccessfully with errors:

[
  {
    "message": "Unexpected system error",
    "extensions": {
      "code": "500"
    }
  }
]

Request ID: d6eba42a-65ba-4b37-98aa-2d5c6a328ee7-1732204334

2024-11-21T15:52:15.505Z:
Running system process:
  · Command: npm prefix
  · Working directory: /Users/***/Projects/Shopify Apps/matchbox

2024-11-21T15:52:15.608Z: Obtaining the dependency manager in directory /Users/***/Projects/Shopify Apps/matchbox...

Reproduction steps

Run shopify app dev --verbose
Command successfully sets up tunnel and updates app URLs
Fails when trying to fetch extension registrations

Operating System
Operating System: Mac OS Monterey
Shopify CLI version (check your project's package.json if you're not sure)
3.70.0
Shell
zsh
Node version (run node -v if you're not sure)
20.16.0
What language and version are you using in your application?
Node.js 20.16.0

Thank you for your detailed bug report! I'll pass this along to our team to investigate.


Separate asset storage classes

This is part one of a refactor I'm working on to try to make the attachment and asset code in Whitehall more maintainable. I'd suggest reviewing it commit by commit.
This PR breaks the Whitehall Asset storage class down into several separate classes. There are three main categories of assets:

Attachments, which require the "attachable" to be accessed in the create asset worker
Previewables (e.g.) images, where we want to pass auth bypass IDs so that they can be loaded in shared previews
Default asset types, which are not attachable or associated with things that can be previewed (e.g. people)

This allows to make some assumptions about what data is available from the uploder model (e.g. we must have an attachment because the attachment storage is only configured for the attachment uploader), which means we can simplify the code quite substantially.
One thing that is annoying is that I had to add the "attachable" everywhere when creating test AttachmentData objects. In a way it's annoying, but actually it's really exposing the fact that a large number of our tests were potentially incorrect because they were not invoking the full behaviour of the asset storage class. Attachment assets were being stored without the attachable being passed to the asset creation worker, which is not valid. In a future PR I intend to make this unnecessary.
In a future PR I will apply the same approach to the asset creation worker, which should be easier now that we can call a different worker depending on the type of asset we are storing.
Trello: https://trello.com/c/N1My8EtT

I think this all makes sense and it's a sensible break down of the assets.
Let's make sure to test on integration before deploying just to be sure :)

This was my test plan on integration. Any cases that I might have missed? https://docs.google.com/spreadsheets/d/1yYTOF7zZNA--KL05agGZWOKBCAi3PaULMXiqDiH0wn8/edit?usp=sharing

I can't think of any others off the top of my head. Happy to do some clicking on integration when it's up. We could even do a mob try to break it if we think we've missed some cases


Feature request: highlight stars on hover

Thank you for this extension. It would be great if stars would be highlighted both on click/select and Hover event. Could you add this feature?

Sorry but I don't plan on adding new features or supporting this extension
any time soon.
On Wed, Oct 19, 2016 at 1:59 PM, ktsixit<EMAIL_ADDRESS>wrote:

Thank you for this extension. It would be great if stars would be
highlighted both on click/select and Hover event. Could you add this
feature?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/srka/Srka-Magento-Review-Stars/issues/1, or mute the
thread
https://github.com/notifications/unsubscribe-auth/ABcQQpbfDBeiwA_av59yQMg5rc0oeXVDks5q1gYbgaJpZM4Ka4ks
.


Collective page: show a section title above tiers when not first

When Tiers (CONTRIBUTE section) are not the first item in their category, we currently don't display any section label. This is misleading because users could believe that they belong to another category. In the screenshot below, for example, they could be tricked into thinking they belong to "Connected Collectives".
I think we use to have something like "Financial contributions" in the past, we should bring it back.

I will work on it.


Update example RBAC

How to categorize this PR?

/area auto-scaling
/kind enhancement
What this PR does / why we need it:
@plkokanov reported that there are missing RBAC rules for leader election and events in the example RBACs.
Which issue(s) this PR fixes:
Part of https://github.com/gardener/gardener/issues/8259
Special notes for your reviewer:
N/A
Release note:

NONE

/assign

This is now slightly behind latest thinking (since the changes we made together yesterday on the RBAC entities created by gardenlet - e.g. name-based restrictions). But I think we should get this change in, and then we can reiterate later, for complete convergence.

Thanks for bringing up this! I now had a look in the context of https://github.com/gardener/gardener-custom-metrics/pull/23 and I think we won't be able to introduce such a name-based restriction for the list/watch verbs. In https://github.com/gardener/gardener-custom-metrics/pull/23 we add a label selector to the controller-runtime's cache which I believe should result in list/watch requests by label selector. Hence, we cannot add a restriction for the resource names at least for list and watch. We can add the resource name based restriction for the get but then it doesn't make much sense conceptually because you are able to list all resources from all namespaces but able to get only 2 because of the resourceNames restriction.
The endpoints name restriction that is possible after https://github.com/gardener/gardener-custom-metrics/pull/22 is applied in this PR.


Fix broken links to ingress-nginx

This change fixes broken links to referenced ingress-nginx YAML files, which were moved/deleted in the GitHub repo. I located the appropriate commit hash and replaced them with links that are pinned to those commits, which should be long-term stable.
Also applied style guide standards to headings.

Also recommend changing networking.k8s.io/v1beta1 → networking.k8s.io/v1.

Thanks so much for the review and suggestions. Applied all feedback as suggested.


arcadedb: Add version 23.6.1

This PR adds ArcadeDB, an OSS successor to OrientDB, multimodal high-performance database with HA capabilities.
Closes #11638

[x] I have read the Contributing Guide.

Comments on manifest
ArcadeDB is written in Java and comes with a structure that's similar to a lot of Java projects.
It contains two scripts console.bat and server.bat that are unfortunately very generic names, that's why I decided to come up with two shims with arcadedb- prefix. Also set ARCADEDB_HOME environment variable is a huge convenience required by launch scripts and position of following folders.
Folders config, database and log are persisted so they don't disapper between updates.

/verify


Asset manifest handling and non-root webapplications

I'm using these library versions:

ReactJS.NET: 5.2.4
JavaScriptEngineSwitcher: ChakraCore 3.5.6
react and react-dom: N/A
webpack: N/A
node: N/A

Runtime environment:

OS: Windows server 2016 64 bit
.NET Framework 4.7.2

Steps to reproduce
Our internal application is hosted at https://[OUR_BASE_URL]/[REACT_APPLICATION_NAME], with another webapplication being hosted at https://[OUR_BASE_URL].
I've followed the tutorial and have implemented the Asset manifest handling step.
Everything works while using localhost, but scripts can't be found on the production website after publishing the application.
Scripts and stylesheets are generated relative to https://[OUR_BASE_URL]/ instead of https://[OUR_BASE_URL]/[REACT_APPLICATION_NAME]/ (e.g.  instead of ).
Seems like the ~ in SetReactAppBuildPath("~/dist") isn't properly being converted to [REACT_APPLICATION_NAME] like it does for  inside the _Layout.cshtml.
I've found threads that say you have to specify "homepage": "." or "./" inside package.json, but this doesn't seem to be doing anything.

Try setting publicPath in webpack.config
https://github.com/reactjs/React.NET/blob/b97f80cb029e0863e64468e45af67655be315af9/src/React.Template/reactnet-webpack/webpack.config.js#L10

Doing that only kind of fixes the problem and creates a new one.
I changed it to '/[REACT_APPLICATION_NAME]/dist/'.
The backend searches for the files in the wwwroot/[REACT_APPLICATION_NAME]/dist/ folder (and it will throw an error if they aren't found), while it still tries to serve the files from the wwwroot/dist/ folder, since the [REACT_APPLICATION_NAME] is our application's name and not part of the wwwroot path.
This means I have to copy the files to both locations while publishing, or else it won't work.

Yeah makes sense.
In that case we can probably add an option to ReactConfiguration that
allows customizing the root path that the scripts are loaded from server
side. It is important that publicPath matches how the browser loads your
scripts in case you opt for using lazy loading in the future, otherwise
those chunks will fail to load.
Something like adding a serverRoot optional argument here on
SetReactAppBuildPath
https://github.com/reactjs/React.NET/blob/master/src/React.Core/ReactSiteConfiguration.cs
On Sun, Jul 12, 2020 at 13:57, aldrashan<EMAIL_ADDRESS>wrote:

Doing that only kind of fixes the problem and creates a new one.
I changed it to '/[REACT_APPLICATION_NAME]/dist/'.
The backend searches for the files in the
wwwroot/[REACT_APPLICATION_NAME]/dist/ folder (and it will throw an error
if they aren't found), while it still tries to serve the files from the
wwwroot/dist/ folder, since the [REACT_APPLICATION_NAME] is our
application's name and not part of the wwwroot path.
This means I have to copy the files to both locations while publishing, or
else it won't work.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/reactjs/React.NET/issues/1134#issuecomment-657274026,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAHGCFSFRMESZEKDVTACTWDR3IPTPANCNFSM4OVJFO3A
.

Would you be open to sending a PR to support this use case?
On Sun, Jul 12, 2020 at 14:21, Dustin Masters<EMAIL_ADDRESS>wrote:

Yeah makes sense.
In that case we can probably add an option to ReactConfiguration that
allows customizing the root path that the scripts are loaded from server
side. It is important that publicPath matches how the browser loads your
scripts in case you opt for using lazy loading in the future, otherwise
those chunks will fail to load.
Something like adding a serverRoot optional argument here on
SetReactAppBuildPath
https://github.com/reactjs/React.NET/blob/master/src/React.Core/ReactSiteConfiguration.cs
On Sun, Jul 12, 2020 at 13:57, aldrashan<EMAIL_ADDRESS>wrote:

Doing that only kind of fixes the problem and creates a new one.
I changed it to '/[REACT_APPLICATION_NAME]/dist/'.
The backend searches for the files in the
wwwroot/[REACT_APPLICATION_NAME]/dist/ folder (and it will throw an error
if they aren't found), while it still tries to serve the files from the
wwwroot/dist/ folder, since the [REACT_APPLICATION_NAME] is our
application's name and not part of the wwwroot path.
This means I have to copy the files to both locations while publishing,
or else it won't work.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/reactjs/React.NET/issues/1134#issuecomment-657274026,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAHGCFSFRMESZEKDVTACTWDR3IPTPANCNFSM4OVJFO3A
.

As in fork the code and add the code to do this myself, you mean?
Could probably do that, yeah.

See https://github.com/reactjs/React.NET/pull/1141 .
Only the last commit is relevant.
I reckon it still needs to be edited for the .net standard version of the library, but this works for the .net core versions.

I'm facing the same problem, and I can say I'm relieved to have found this issue report, because this was driving me crazy. I tried absolutely everything in terms of changing paths, using absolute and relative paths, trying to use server-relative paths, HTML page relative paths, etc. Nothing works, except for giving up on using scripts with dynamic names (names containing a hash part) and calling the fixed name scripts directly, as in:
<script src="~/dist/runtime.js"></script>
<script src="~/dist/vendor.js"></script>
<script src="~/dist/main.js"></script>

instead of calling:
@Html.ReactGetScriptPaths()

in the _Layout.cshtml file.
But this is only a workaround to make it work, I really WANT to use the dynamic script names (they are useful to avoid browser caching, for instance).
OBS: It's not a matter of being localhost or not, it's a matter of not being a root web app, EVEN on localhost. I'm publishing my web app on http://localhost/SampleWebpackApp and it doesn't work.
I'm using React.AspNet and React.Router versions 5.2.7.
Is there ay fix to this issue yet?
Thanks.

As mentioned in the other thread, the library wasn’t really designed to be
used like outside the domain root. However it’s something we’d like to
support!
Given that we work on this in our spare time, for free, there isn’t a
timeline when it will be added. If someone is willing to contribute the
time to implement setting the root path in the site config then I can help
guide that effort.
On Mon, Aug 17, 2020 at 3:23 PM, arrudamarcos78<EMAIL_ADDRESS>wrote:

I'm facing the same problem, and I can say I'm relieved to have found this
issue report, because this was driving me crazy. I tried absolutely
everything in terms of changing paths, using absolute and relative paths,
trying to use server-relative paths, HTML page relative paths, etc. Nothing
works, except for giving up on using scripts with dynamic names (names
containing a hash part) and calling the fixed name scripts directly, as in:

instead of calling:
@Html.ReactGetScriptPaths()
in the _Layout.cshtml file.
But this is only a workaround to make it work, I really WANT to use the
dynamic script names (they are useful to avoid browser caching, for
instance).
OBS: It's not a matter of being localhost or not, it's a matter of not
being a root web app, EVEN on localhost. I'm publishing my web app on http://localhost/SampleWebpackApp
http://localhost/SampleWebpackApp and it doesn't work.
I'm using React.AspNet and React.Router versions 5.2.7.
Is there ay fix to this issue yet?
Thanks.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/reactjs/React.NET/issues/1134#issuecomment-675144722,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAHGCFV4N7UQMLBRKAH34ZLSBGUVLANCNFSM4OVJFO3A
.


Update Lab00_Setup_Environment.md

Improve readability of note, fix typo #124
Module: 00
Lab/Demo: 00
Fixes # .
Changes proposed in this pull request:

Submitted by clifford-smith on behalf of MOC Labs Review.

This pull request is the same as pull request #124.


adds deferred variable cache to common.mk

Issue #, if available:
Description of changes:
We use a decent amount of shell calls in out makefiles. Because we currently defer these, they get resolved a number of times, every time they are used in the context of the makefile.  We could change these to immediately resolved variables, however that means we would exec these shell calls at the start of every make invocation, even tho they may not be needed for the specific target being called.  This PR introduces a caching mechanism for these deferred variables and a helper to overwrite variables by name to be automatically cached on their first resolution.
Commits:

adds helper and caches shell, or otherwise, expensive vars
changes all project makefiles to defer git_tag and golang version since these are now cached after first use

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/lgtm
/approve


Adding IDictionary support for binding parameters

In current master version IDictionary parameters does not supported

@ezirog, that`s really nice addition - thank you! I think I will cover it with tests a bit later, but everything looks good.


Add UTVCO

Name University: Universidad Tecnológica de los Valles Centrales de Oaxaca
Website: https://utvco.edu.mx/
Technology Courses:

https://utvco.edu.mx/tecnologias-de-la-informacion/
https://utvco.edu.mx/mecatronica/

@jsvictordev First stage of verification passed, official domain is utvco.edu.mx as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.

Thank you for your consideration, and we eagerly await approval

@jsvictordev Thank you for your patience while waiting for a review and processing your request. Pull request merged.


Timer Feature Added

The key additions include a Countdown Timer with audio notifications and two control buttons: "Pause/Resume" , "Reset" and "Got It!". The timer allows users to set a duration in minutes and seconds, which then starts counting down. When the timer reaches zero, a notification sound plays, a browser alert or notification is triggered, and a "Got It!" button appears. Clicking the "Got It!" button stops the audio, confirming the notification. The "Pause" button halts the countdown , "Resume" button continues the countdown and  "Reset" button resets the timer countdown. These features enhance user interactivity and provide clear indications when the timer completes.

@param-code Please review my PR.

Good!!

Thank you @param-code !!


Cut release 0.8.0

Since @mxinden doesn't seem to be available right now, and I cannot push to the branch in his GH account, I have recreated #906 with the correct release date and rebased on top of master.
@stuartnelson3 @w0rm

I take the thumbs on #906 as valid for this one, too.

Them thumbs be valid.
Godspeed.

@beorn7 I am sorry for taking so long with the release. Thanks for moving on, appreciate the help. Sorry for the trouble.

@mxinden No worries at all. Given my current job constraints, it actually makes me quite happy if my job needs and my activity here aligns nicely...


Any plans to support .NET 5.0?

Hi @flgatormike,
Good morning.
The ASP.NET Cognito Identity provider targets netstandard2.0 and it works for .NET 5.0 (also refer table at https://docs.microsoft.com/en-us/dotnet/standard/net-standard#net-implementation-support which states that netstandard2.0 supports .NET 5.0). Please advise if there is any specific issue that you are facing when using this library with ASP.NET Core Net 5.0 application.
Thanks,
Ashish

I haven't figured out how to add this to my startup:
services.AddCognitoIdentity();
I get this error:
'IServiceCollection' does not contain a definition for 'AddCognitoIdentity'
I have used this library successfully with a ASP .NET Core 3.1 project with these using statements, but can't figure out how to make it work with a .NET 5.0 project.
using Amazon.CognitoIdentityProvider;
using Amazon.Extensions.CognitoAuthentication;

I got it running. Not sure what I was doing wrong, maybe I had the wrong version.


go1.18: generics preview

Go 1.18 comes out in Feb 2022, with generics
This compiles with go1.18beta1

This won't compile with our CI yet

This is to give a preview of generics, and some of the changes we could make
Ignore the go.mod and go.sum files for now

@SwiftPush CI will work with:
    - name: Setup Go environment
      uses<EMAIL_ADDRESS>      with:
        stable: 'false'
        go-version: '1.18.0-beta1'


feat: move row-to-JSON serialization for initial shape data to PG

Improves performance heavily by moving row-to-JSON initial snapshot logic into PG. Currently utilizes hand-crafted JSON structure, but I'll make another test later if we can use a cleaner JSON building approach.
Currently, if used with "mixed storage pr", it gives good improvements:

Did we measure the performance penalty on PG? It's okay to move the cost to PG, but does it make orders of magnitude slower? Does it produce a memory usage spike? Does it fall of for large queries?

I suspect it's fine as postgres is already manipulating query results to return them so it's just a bit more fiddling with the data.


Fix usage of RedisCacheStore for rails 5.2.0

Fix https://github.com/kickstarter/rack-attack/issues/352.
Redis and Redis::Distributed patched by rails to support with https://github.com/rails/rails/blob/b7760eb75a9dd002260a361119aea0b255e1f573/activesupport/lib/active_support/cache/redis_cache_store.rb#L23-L30

Hi @le0pard, thanks for the fix.
I picked your commit on this PR (https://github.com/kickstarter/rack-attack/pull/354) in order to make additional changes and add tests on top.

Your commit was merged as part of this one https://github.com/kickstarter/rack-attack/pull/354.
Thanks again!


Filters: Add an author filter

Just like the Repo filter from #277, but for pull authors.
CR this one commit at a time.

Closes #283

deploy_block :+1:  on #277 going out because this is based on that branch.

dev_block ✊
The autofocus on the menu is making it difficult to close the menu. Clicking away also doesn't do anything.
https://user-images.githubusercontent.com/5289715/162257479-b3cc7805-7e3e-423a-bcd1-41b38ebf8d99.mp4

The autofocus on the menu is making it difficult to close the menu. Clicking away also doesn't do anything.

I'm having a tough time understanding here. The video seems to just show you scrolling up and down. I did notice that if you scroll down, Chakra will autoscroll back up so the menu is in view. A little odd that it does it ~1s after you stop scrolling instead of immediately, but it doesn't seem to impede the functionality at all. Clicking off works fine for me... curious. Let's get together so you can show me.

dev_block ✊
So it looks like the whitespace below pull requests isn't capturing click events, which is why I wasn't able to click away when there were a small number of pulls shown.

CR :rose: Sweet!

QA 🎬

Pulls can now be filtered by Authors
Author filter menu can now be exited by clicking in whitespace

CR :goat: through 19ce89e

I've closed the other pull and made the suggested fixes (from @andyg0808 ) here this pull significantly refactored the menu filter code.

un_deploy_block :+1:  other pull is folded into this one.

CR :goat: through e4d90ad

CR :flags:

QA 👍

Author filter works as expected individually and combined with repo filter
Click events outside of the dropdown closes it

I think these conversations are happening in other pulls or issues, so I'll deploy_block 🌵 here and @danielbeardsley feel free to un-deploy-block it.

The number of pulls associated with each author doesn't reflect the number of pulls displayed when filtering by that author while showing all repos.

When filtering on the old ui, the column counts are adjusted to show current, filtered counts

When filtering on the old ui, the column counts are adjusted to show current, filtered counts

I was thinking of https://github.com/iFixit/pulldasher/pull/289, but it looks like that only applies to the nav bar.

The number of pulls associated with each author doesn't reflect the number of pulls displayed when filtering by that author while showing all repos.

If we just used a count of "displayed pulls" all the unchecked items would have 0s which isn't that useful.

When filtering on the old ui, the column counts are adjusted to show current, filtered counts

Fixed in #290

un_deploy_block :+1:

CR :goat: through 2ce8db7

Looks like there are a few TS errors to be cleared up.

CR :goat: through 3373753

When testing this, I noticed that every author is marked as filtered initially. I think that this would make filtering by a pull author more difficult since there is no way to uncheck all the authors that are already selected.
I suggest that either:

the Show All action could toggle on/off

or

using the Author filter would have no authors selected at first, which allows someone to select a specific author by pull instead of having to deselect each author currently being shown.

Screen Capture:

Thank you @sterlinghirsh and @sctice-ifixit for the good suggestions. It's been implemented. Things now start out as not checked, so clicking one goes from everything to just that thing

CR :goat: through 615cc09

QA 🟢
No author is selected initially ☑
Show All unchecks any selected author(s) ☑

Suggestions:
Move the bar previously above Show All to the top

Additional Notes:

It appears that the counter for each author isn't 100% accurate

For example: some users are shown as having pulls, but when selecting them no pulls appear

It appears that the counter for each author isn't 100% accurate

I think this is because this count is of all open pulls. This includes those filtered out for other reasons (Cryo, search, repo filter, ...)

I'm gonna merge this cause I implemented Shawns suggestion and he'll be on a plane for a while.


issue installing vina with pip into conda environment

Hi, I've tried the following commands to install vina, taken directly from the Installation Tutorial.
$ conda create -n vina python=3
$ conda activate vina
$ conda config --env --add channels conda-forge
$ conda install -c conda-forge numpy swig boost-cpp sphinx sphinx_rtd_theme
$ pip install vina
$ which vina
$ vina

I get no response to 'which vina' and the following error to 'vina':
-bash: vina: command not found
I have tried using different versions of python (3.10, 3.7, 3.9.7) and running on both OSX and Linux.

Hi, pip install is to run Vina from Python. The executables are available on the releases page here on GitHub.

The

Hello , I'm trying to install an external app for usage from python , and it's one of the installments steps can I skip this safely ?
how I can check if its installed . do I need to add it to the system environment variable path? , thanks .

@PrestigeDevop I'm not sure I understood your question. Importing vina successfully in a Python interpreter usually means the Python bindings are installed correctly:
import vina


⚠ Bofrost.be has degraded performance

In 14e6fc1, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 2084 ms

Resolved: Bofrost.be performance has improved in c8e9b9b after 47 minutes.


Spring @Value annotatoin not recognized by the RestAssuredMockMvc

From<EMAIL_ADDRESS>on July 07, 2015 15:00:42
What steps will reproduce the problem? 1. Add the two classes into your workspace
2. Execute SpringValueAnnotationNotRecognizedTest
3. You will see that the test SpringValueAnnotationNotRecognizedTest.testControllerMethodThatWontRecognizeTheSpringValueAnnotation will fail, because the Spring's @Value Annotation is not recognized.
Attachment: SpringValueAnnotationNotRecognizedTest.java SpringValueAnnotationNotRecognizedController.java
Original issue: http://code.google.com/p/rest-assured/issues/detail?id=414

Does this work if you write the test in plain Spring MockMvc?

Hello, Johan
I faced the same problem and did some investigation. It works with plain Spring MockMvc.
It does not work with standalone setup because bean factory (DefaultListableBeanFactory) is not created and therefore BeanExpressionResolver is not accessible.
The above test can be slightly changed to run successfully: https://gist.github.com/Igor-Petrov/5d9d0f6d8d1a06062653

Hmm REST Assured Mock Mvc simply delegates "standaloneSetup" to MockMvc so I don't think there should to be any difference to using standaloneSetup in MockMvc. Are you absolutely sure that it works when using standalone setup with MockMvc!?

Hi, Johan
yes, You are right. It does not work when using standalone setup with MockMvc. Looks like spring-test issue.

I doubt that it's an issue though. You probably need to register a MockMvcConfigurer or something similar to get it working. Thanks for checking, I'll close the issue.


connect_read_pipe causes "Exception ignored in:" on program exit

The following program prints "Exception ignored in:" when exiting. I am using Python 3.5.1. In my real application, the problem also occurs with a inherited pipe file descriptor from the parent process (wrapped with open(fd, "rb", 0)) instead of sys.stdin.
import asyncio
import sys

loop = asyncio.get_event_loop()
reader = asyncio.StreamReader(loop=loop)
reader_protocol = asyncio.StreamReaderProtocol(reader, loop=loop)

# commenting this out makes the message disappear
loop.run_until_complete(loop.connect_read_pipe(lambda: reader_protocol, sys.stdin))

loop.close()

# to demonstrate message happens at exit
import time
time.sleep(5)

Hi,
Can you run your code with the environment variable PYTHONASYNCIODEBUG=1:
PYTHONASYNCIODEBUG=1 python your_test_case.py

It seems that since you don't close anything else than the loop, an exception happens in a del, and prevent the actual RessourceWarning to be displayed.

I had already tried PYTHONASYNCIODEBUG=1, but since it didn't print anything more I thought I was setting it wrong. Same behavior on 3.5.1 and 3.4.4rc1.

Ping

What's the FULL exception? Is there anything after the "Exception ignored in:"? Usually there's more there.
Your  problem is closing the loop while it's still referenced, that's not a good idea. E.g. you may want to close the pipe first.

No, there isn't more. This bug causes Python to print exactly that: "Exception ignored in:"

Modifying the program to close the pipe AND THEN run a dummy coroutine makes the message disappear.
import asyncio
import sys

loop = asyncio.get_event_loop()
reader = asyncio.StreamReader(loop=loop)
reader_protocol = asyncio.StreamReaderProtocol(reader, loop=loop)

r, w = loop.run_until_complete(loop.connect_read_pipe(lambda: reader_protocol, sys.stdin))
r.close()

@asyncio.coroutine
def workaround():
    yield
loop.run_until_complete(workaround())

loop.close()

I noticed this error a while ago. It is triggered by the following line in unix_events:
warnings.warn("unclosed transport %r" % self, ResourceWarning)

Full traceback:
Traceback (most recent call last):
  File "/usr/local/lib/python3.5/asyncio/unix_events.py", line 383, in __del__
    warnings.warn("unclosed transport %r" % self, ResourceWarning)
  File "/usr/local/lib/python3.5/asyncio/unix_events.py", line 336, in __repr__
    self._fileno, selectors.EVENT_READ)
  File "/usr/local/lib/python3.5/asyncio/selector_events.py", line 35, in _test_selector_event
    key = selector.get_key(fd)
AttributeError: 'NoneType' object has no attribute 'get_key'

At that time, _UnixReadPipeTransport()._loop._selector is None, so get_key fails.
However, I'm not sure why the exception is not printed completely.


new pypi release

Could you release a new release on pypi? This would unblock https://github.com/immersive-web/webxr/pull/1254 among other things (since the spec-prod github action relies on the pypi version of bikeshed)

Done! 3.4.3 is released now


[FEATURE]Use strong/em/s tags instead of b/i/strike

Currently the Summernote uses <b>, <i> and <strike> tags to style bold, italic, and strikeout text correspondingly, while more modern options for doing this are <strong>, <em> and <s>.
While according to the HTML5 specification, the <b> tag should be used as a last resort, the <strike> tag is not supported in HTML5 at all.
There's a corresponded issue in Summernote, but seems unlikely that necessary changes will be made.
Is it possible to modify Summernote's code in the editor, or add an appropriate option/config to the editor, to incorporate these imporovements?

What I have done is when I store data in database. I replace b tags with strong and i tags with em, if other tags I require I do the same. This reduced work for me on frontend.

Note: What I have done is when I store data in database. I replace b tags with strong and i tags with em, if other tags I require I do the same. This reduced work for me on frontend.


[2.2.0] Broken recipes for Polished Basalt Vertical Slab & Basalt Bricks Vertical Slab

Describe the Bug:
Polished Basalt Vertical Slab can't be crafted in the crafting table due to a typo. The item ID is supposed to be 'infernalexp:polished_basalt_slab' The letter h in polished is missing and therefore the crafting recipe doesn't work.
Basalt Bricks Vertical Slab can't be crafted in the Stonecutter because the recipe has no output.
I double-checked with JEI and it doesn't show the recipes for those 2 mentioned blocks.
How to Reproduce:
Install this mod and start Minecraft with the game output log. Once you load a world you get the following 2 error messages down below.
Expected Behavior:
Is there really an explanation necessary?
Screenshots:

Version Information:

Operating System: Windows 10 Pro
Mod Version: 2.2.0
Minecraft Version: 1.16.5
Forge Version: 36.0.2
Other mods that were running when the crash happened: No crash

Additional Context:
In case the images don't work here are the error messages from the log output:
Parsing error loading recipe infernalexp:crafting/crafting_shaped/polished_basalt_vertical_slab
com.google.gson.JsonSyntaxException: Unknown item 'infernalexp:polised_basalt_slab'
Recipe has no output. Infernal Expansion infernalexp:stonecutting/basalt_bricks_vertical_slab class net.minecraft.item.crafting.StonecuttingRecipe
Outputs:
net.minecraft.item.ItemStack: [[2 air minecraft:air]]
Inputs:
net.minecraft.item.ItemStack: [[1 basalt_bricks infernalexp:basalt_bricks]]

Duplicate of #260


Bionic Beaver, various errors during install

New features
Please visit http://feathub.com/htpcBeginner/AtoMiC-ToolKit
The problem
As already said down below, fresh install of the operating system (VM) and the first time use of the Toolkit.

There is a dependency that many packages use python-imaging does not exist anymore, replacement is python-pil. I have installed it manually, but there is still "unresolved dependancy issue" in the script.
Sonarr also has a problem, it can't find "nzbdrone" during the install. I resolved it by manually adding the repo
sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys FDA5DFFC sudo echo "deb http://apt.sonarr.tv/ master main" | sudo tee /etc/apt/sources.list.d/sonarr.list
and rerun the install. I also had to change the port of the app to other value. The service has started, but I did not get dynamic elements in WebGUI (just the theme, static text and those three big "loading" dots). After manually moving the port in the config file I got full WebGUI.
I could not connect rTorrent with Sonarr/Radarr/Lidarr, but with Deluge worked just fine (it may be lack of understanding on my part), I did not care which torrent app I use so I installed another and the connection worked fine.
"Install Emby" returns "Invalid option or feature not implemented yet"
Madsonic and Subsonic by default use the same port; Grafana and rTorrent also
{ip_address}/organizr returns 404, haven't yet tried to find out why

My Linux distribution and version is:

Ubuntu Server 18.04

I'm seeing this behaviour on:

A fresh install
First time using AtoMiC-ToolKit on an existing setup
First time ever using AtoMiC-ToolKit

Link to install logs

I'm not a dummy, so I've checked these!

I'm using the latest version of AtoMiC-ToolKit.
All my Linux distro packages are up to date and I don't see any errors while updating.
I've checked there are no current open issues relating to my problem!

Thanks for the quick answer. I knew I forgot something (to read the readme). It's a good package, next one can only be better. I have just a few days ago seen the AFK and it has given me the idea that I could avoid OMV for the server which is on the way. So, I am just testing, trying out apps and getting comfortable with command line and Linux altogether. I assume that my knowledge is far below what is needed to be able to help, but that may change.  In the meantime, I'll stick to  DockSTARTer Gitter chatroom in hope to learn something.
Regards,
Sasa

No problem at all,
We would love people to come and help us and its quick to pickup! You could help by adding apps you might want to use but we don't currently have... which is an easy task. If you want to help, come and give me or @nemchik a nod, even if its just testing! all levels of ability are welcome as we are still learning new things all the time ourselves. :smile:
Tom


Create documentation for Tenant Qualified URLs

Is your suggestion related to a missing or misleading document? Please describe.
Create documentation for the feature 'Tenant Qualified URLs' in WSO2 Identity Server.
Describe the improvement
The documentation should include the following areas:

Purpose of tenant qualified URLs
How does it work?
How to enable tenant qualified URLs
Outline the components that are tenant qualified
How to test out the feature

Related Issues:
https://github.com/wso2/product-is/issues/7902
https://github.com/wso2/product-is/issues/9051
https://github.com/wso2/product-is/issues/9068

This issue is being closed due to extended inactivity. Please feel free to reopen it if further attention is needed. Thank you for helping us keep the issue list relevant and focused!


Undefined symbols for architecture x86_64 - _RCTSetLogFunction referenced...

Build release failed with message
Ld /Users/user/Library/Developer/Xcode/DerivedData/[projectname]-dbcuopocesxwzyaxjpbtpqciwylm/Build/Intermediates.noindex/[projectname].build/Release-iphonesimulator/[projectname]Tests.build/Objects-normal/x86_64/[projectname]Tests normal x86_64 (in target: [projectname]Tests)
cd /Users/user/Apps/[projectname]/ios
export IPHONEOS_DEPLOYMENT_TARGET=9.0
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang -arch x86_64 -bundle -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator12.1.sdk -L/Users/user/Library/Developer/Xcode/DerivedData/[projectname]-dbcuopocesxwzyaxjpbtpqciwylm/Build/Products/Release-iphonesimulator -F/Users/user/Library/Developer/Xcode/DerivedData/[projectname]-dbcuopocesxwzyaxjpbtpqciwylm/Build/Products/Release-iphonesimulator -F/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/Library/Frameworks -filelist /Users/user/Library/Developer/Xcode/DerivedData/[projectname]-dbcuopocesxwzyaxjpbtpqciwylm/Build/Intermediates.noindex/[projectname].build/Release-iphonesimulator/[projectname]Tests.build/Objects-normal/x86_64/[projectname]Tests.LinkFileList -Xlinker -rpath -Xlinker @executable_path/Frameworks -Xlinker -rpath -Xlinker @loader_path/Frameworks -mios-simulator-version-min=9.0 -dead_strip -bundle_loader /Users/user/Library/Developer/Xcode/DerivedData/[projectname]-dbcuopocesxwzyaxjpbtpqciwylm/Build/Products/Release-iphonesimulator/[projectname].app/[projectname] -Xlinker -object_path_lto -Xlinker /Users/user/Library/Developer/Xcode/DerivedData/[projectname]-dbcuopocesxwzyaxjpbtpqciwylm/Build/Intermediates.noindex/[projectname].build/Release-iphonesimulator/[projectname]Tests.build/Objects-normal/x86_64/[projectname]Tests_lto.o -Xlinker -objc_abi_version -Xlinker 2 -fobjc-arc -fobjc-link-runtime -ObjC -lc++ -lstdc++ -framework JavaScriptCore -framework XCTest -Xlinker -sectcreate -Xlinker __TEXT -Xlinker __entitlements -Xlinker /Users/user/Library/Developer/Xcode/DerivedData/[projectname]-dbcuopocesxwzyaxjpbtpqciwylm/Build/Intermediates.noindex/[projectname].build/Release-iphonesimulator/[projectname]Tests.build/[projectname]Tests.xctest-Simulated.xcent -lPods-[projectname]Tests -Xlinker -dependency_info -Xlinker /Users/user/Library/Developer/Xcode/DerivedData/[projectname]-dbcuopocesxwzyaxjpbtpqciwylm/Build/Intermediates.noindex/[projectname].build/Release-iphonesimulator/[projectname]Tests.build/Objects-normal/x86_64/[projectname]Tests_dependency_info.dat -o /Users/user/Library/Developer/Xcode/DerivedData/[projectname]-dbcuopocesxwzyaxjpbtpqciwylm/Build/Intermediates.noindex/[projectname].build/Release-iphonesimulator/[projectname]Tests.build/Objects-normal/x86_64/[projectname]Tests
Undefined symbols for architecture x86_64:
"_RCTSetLogFunction", referenced from:
-[[projectname]Tests testRendersWelcomeScreen] in [projectname]Tests.o
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
React Native version:
System:
OS: macOS High Sierra 10.13.6
CPU: (8) x64 Intel(R) Core(TM) i7 CPU         870  @ 2.93GHz
Memory: 2.07 GB / 16.00 GB
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 10.16.0 - /usr/local/bin/node
Yarn: 1.3.2 - /usr/local/bin/yarn
npm: 6.9.0 - /usr/local/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
SDKs:
iOS SDK:
Platforms: iOS 12.1, macOS 10.14, tvOS 12.1, watchOS 5.1
Android SDK:
API Levels: 28, 29
Build Tools: 28.0.3, 29.0.0
System Images: android-24 | Google Play Intel x86 Atom
IDEs:
Xcode: 10.1/10B61 - /usr/bin/xcodebuild
npmPackages:
react: 16.8.6 => 16.8.6
react-native: 0.60.4 => 0.60.4
npmGlobalPackages:
react-native-cli: 2.0.1
react-native: 0.57.5
Steps To Reproduce

Generate a project (react-native init test).
Open the workspace on Xcode, change the scheme to release and press cmd + b to build.

Has to do with your code stripping. Turn that off.

How I can do that?

What version of Xcode are you using? Could possibly be fixed by updating to 10.3.

@wenq1 when I turned off works, what are the consequences of that?

@Echelpoel I can't update Xcode, it is limited to 10.1

@brunojs02 this issue seems to happen if you create a new RN project on > 0.60.
It will be solved once #25751 lands, but in the meanwhile you can apply the following changes to your /ios/{appname}Tests/{appname}Tests.m to make it work.

What the diference between turn off code stripping and following changes?

The change above will be the "official" one once it lands in a new version of RN.
Code stripping reduces the bundle size, so I will keep it on if possible.

I'm facing this issue with 60.5...

The same problem with 60.5. The fix https://github.com/facebook/react-native/issues/25911#issuecomment-517941867 removed 2 of 3 errors (undefined symbols _RCTSetLogFunction and RCTDefaultLogFunction ), but it I am still getting an error for RCTSharedApplication.

@mxs17 turn code stripping off, it's wokrs

@mxs17 How to turn off code stripping? What do you mean? Please explain

@roots-ai In Xcode, Command+1, select your project, go to Build Settings on the right, filter by 'strip' using Search input. I saw the recommendation to switch 'Dead code stripping' in Linking section to 'No' for Release. It did not work for me, so I unsuccessfully experimented with all the parameters on this tab, and moved my code to a newly created project. (Probably, something was broken in a different place.)

@mxs17 Thanks for your reply

Same issue for me

Same issue for me, "react-native": "0.60.5",

Are you resolved this problem. I have this for debug build


Move InverseDocReferenceConverterTest into test src folder

Codecov Report

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

@@             Coverage Diff              @@
##             master    #5257      +/-   ##
============================================
- Coverage      82.6%   82.56%   -0.04%
+ Complexity    11046    11042       -4
============================================
  Files          1330     1330
  Lines         44968    44968
  Branches       5626     5626
============================================
- Hits          37146    37129      -17
- Misses         5214     5227      +13
- Partials       2608     2612       +4

Impacted Files
Coverage Δ
Complexity Δ

...te/executor/transport/SubSelectSymbolReplacer.java
68.88% <0%> (-11.12%)
3% <0%> (ø)

...rc/main/java/io/crate/analyze/UnboundAnalyzer.java
75% <0%> (-10%)
2% <0%> (ø)

...ration/collect/collectors/OrderedDocCollector.java
90% <0%> (-10%)
5% <0%> (-1%)

...src/main/java/io/crate/jobs/UpsertByIdContext.java
77.5% <0%> (-7.5%)
8% <0%> (ø)

.../java/io/crate/blob/TransportDeleteBlobAction.java
75% <0%> (-5%)
5% <0%> (-1%)

.../collect/collectors/LuceneOrderedDocCollector.java
90.12% <0%> (-3.71%)
25% <0%> (-1%)

...ticsearch/indices/recovery/BlobRecoverySource.java
71.25% <0%> (-2.5%)
6% <0%> (ø)

...c/main/java/io/crate/jobs/JobExecutionContext.java
90.51% <0%> (-1.73%)
22% <0%> (-1%)

...io/crate/protocols/postgres/ConnectionContext.java
78.24% <0%> (-1.15%)
31% <0%> (ø)

...or/transport/distributed/DistributingConsumer.java
79.16% <0%> (-1.05%)
20% <0%> (ø)

... and 10 more

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 3be7420...97e471a. Read the comment docs.


Also open .dat files containing iq raw baseband data

https://github.com/aerospaceresearch/DirectDemod/blob/fd2ee400931a0a298b128d2a16e6c2d7805d3c3b/directdemod/source.py#L53
the .wav files we imported so far were recorded by SDR# programme.
the rtlsdr community uses also .dat files with the raw iq baseband output from the rtlsdr dongle.
DirectDemod shall be able to also import raw iq baseband. Then we also need to have either files with meta data of the recording, or the user need to provide the input data like center frequency, sample rate and so on that is stored in the .wav file.

commits SHA-562b266004522996d62f06024c91b4022df2a230 SHA-fa9a86277a69c068d3564033e053c5168e7c57f5 solve the issue.


modified wso2-intg-test-cfn.yaml

Modified  wso2-intg-test-cfn.yaml file default WSO2InstanceType and add c3.xlarge as a valid type

This is not a valid PR. Close the PR


Add pull to force refresh for movies and shows page

Movies and shows are fetched on every boot so this does not make a lot of sense.


All migrated Work Items went to "New" status

Hi
I used just a standard configuration.json
I enabled work items migration only and specify source and target connections (from on premise TFS 2019 to azure cloud)
Work Items migrated correctly but all been moved to "New" column in backlog, with each added tag containing previous status e.g
Work Item on TFS was Status Completed
Migrated Work Item on Azure Cloud is with Status "New" and tag:ScrumState:Completed
Process for each project looks the same so I dont understand why work items getting their status set to "new"

@hajtomoto - Thanks for your question. It looks like you're working through an issue with your scenario or implementation, rather than an issue with the documentation. Please consider these resources:

Azure DevOps Services
Azure DevOps Support Bot
Azure DevOps on Stack Overflow

If you do see documentation issues around this issue, please refer to the specific article where it occurs and we can reopen this.


LDAP authentication

Hi, I couldn't find any information about this, so this is either a question or a feature request. Does ElkArte support LDAP auth for member login yet? If not, are there any plans to support it?

At the moment Elk doesn't support LDAP.
Plans... I personally don't have any (so much stuff already to deal with... :roller_coaster: ).
AFAIR this is the first time LDAP is mentioned, but of course an addon or something would be very welcome! :smiley:
Notes (more a discussion) on how to integrate with another authentication system: http://www.elkarte.net/community/index.php?topic=3436.0


Building reladomo on Linux / JDK 8. Issues with  -XX:+UseSpinning jvm param

Hi,
Environment :  Ubuntu 16.04
Linux dvlp1 4.4.0-83-generic #106-Ubuntu SMP Mon Jun 26 17:54:43 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
--
java version "1.8.0_131"
Java(TM) SE Runtime Environment (build 1.8.0_131-b11)
Java HotSpot(TM) 64-Bit Server VM (build 25.131-b11, mixed mode)

Step:
$ git clone ...
$ cd reladomo
$ build/build.sh compile-reladomo
Issue:
Unrecognized VM option 'UseSpinning'
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.
Comments:
$ grep -r "UseSpinning"
build/antbuild.sh:JVM_ARGS="-ms16m -mx2000m -server -XX:MaxPermSize=128m -XX:+UseParallelGC -XX:MaxHeapFreeRatio=20 -XX:MinHeapFreeRatio=10 -XX:CompileThreshold=100 -XX:+UseSpinning"
Best Regards,
jj

The BUILD.md file states: Reladomo is currently built with JDK 1.6.

ok, overlooked that, sorry. Any chance, that Reladomo can be built with JDK 1.8 ? Any direct reasons why JDK 1.6 is required for compilation ?

Backward compatibility is one of our core deliverables. We'll eventually move to 1.8, but probably not in the near future.
Building with 1.8 requires changes because the JDK sql interfaces changed. I have a branch here that builds with 1.8, but it was just an experiment and I don't intend to keep it up to date.
Binaries are available in maven central, so as a user, there is no reason to build this yourself. If you're building because you intend to contribute, you're better off just downloading 1.6.


feat: update modsecurity to 3.0.12

Fixes CVE 2024-1019.

The update to the bake file was already worth it ;)


client-sdk: add persisten storage option

sqlite? it should be able to be cross-compile being native go

I added inmemory and jsonfile stores, they are enough for now. Any another implementation can be just passed as custom store, so there's no real need to support it natively.