Implement TLS Support in Indexify Server

Overview
This pull request introduces TLS (Transport Layer Security) support to the Indexify Server, enhancing its security for network communication.
Changes

Cargo.toml and Cargo.lock: Dependencies have been added for axum-server and rustls, which are necessary for TLS support.

.gitignore: Added entry for .dev-tls to prevent committing TLS keys and certificates.

Makefile: Included a new target local-dev-tls-insecure to generate self-signed TLS certificates for local development.

Server Configuration (YAML files): Added TLS configuration sections to local_server_config.yaml and sample_config.yaml.

Server Module (server.rs): Integrated TLS configuration handling. The server now checks for TLS config and initiates a TLS-enabled server if the configuration exists.

Server Config Struct (server_config.rs): Extended to include TlsConfig struct, which reads TLS-related settings from the configuration files.

Python SDK (sdk-py): Updated README with instructions related to environment variables for HTTPS configuration.

Testing and Validation

Executed cargo test and cargo build ensuring no compilation issues.
Generated self-signed certificates and tested server accessibility with TLS enabled.
Validated with curl command, confirming successful TLS handshake and secure connection establishment.

Curl Command
curl --cacert .dev-tls/ca.crt -H "Content-Type: application/json" -X GET https://localhost:8900/ --verbose

Curl Output

Connection successfully established on port 8900 with TLS.
Server certificate details verified and matched.
HTTP/2 protocol was successfully negotiated.
Received a 200 OK response, confirming the server is operational with TLS.

Key TODOs for Enhanced TLS Implementation

Client Support for Custom Certificates: Implement the ability in the Python SDK's IndexifyClient to handle self-signed or custom CA certificates for secure communication with the TLS-enabled server.

Expanded Documentation: Provide comprehensive documentation and examples for setting up and using TLS, including certificate generation and configuration steps.

Upgrade axum_server: Update to axum_server version 0.6 to utilize Hyper's graceful shutdown feature, improving shutdown process efficiency and reliability.

Automated TLS Testing: Develop automated tests to validate the TLS setup, including certificate handling and error scenarios, ensuring robust and secure functionality.

k8s deployment configuration will need to be updated to support https.

Conclusion
The addition of TLS support significantly improves the security posture of the Indexify Server. This implementation ensures encrypted communication, essential for protecting sensitive data during transit.

As discussed we will remove the branch in code when we upgrade Axum! Thanks :)


Confusing warning

I just enabled warnings in one of our projects and I keep receiving one that is highly confusing.
Warning: a promise was created in a  handler but was not returned from it
    at Queue$enqueue [as enqueue] (...\core\src\job\queue.js:32:9)

When I jump to that location, I see this code:
Queue.prototype.enqueue = function Queue$enqueue( job ) {
	return new Promise( function resolver( resolve, reject ) {…} );
};

Line 32 is the one with the return statement. So, what is the warning trying to tell me? From what I can tell, the promise is returned.

Do you have more lines in the stack trace? Just because enqueue returns the promise, doesn't mean its callers or callers' callers etc do.
For instance:
.then(function() {
     queue.enqueue(...);
});

Even though enqueue returned the promise, the then handler is not returning it.

Yeah, the trace is a lot longer actually.
Warning: a promise was created in a  handler but was not returned from it
    at Queue$enqueue [as enqueue] (…\core\src\job\queue.js:32:9)
    at requestHandler (…\core\src\modules\requestHandler.js:58:19)
    at Layer.handle [as handle_request] (…\core\node_modules\express\lib\router\layer.js:95:5)
    at next (…\core\node_modules\express\lib\router\route.js:131:13)
    at Layer.handle [as handle_request] (…\core\node_modules\express\lib\router\layer.js:91:12)
    at next (…\core\node_modules\express\lib\router\route.js:131:13)
    at checkAuthenticationResult (…\core\src\authentication\authentication.js:173:11)
    at complete (…\core\node_modules\passport\lib\middleware\authenticate.js:243:13)
    at …\core\node_modules\passport\lib\middleware\authenticate.js:250:15
    at pass (…\core\node_modules\passport\lib\authenticator.js:421:14)
    at Authenticator.transformAuthInfo (…\core\node_modules\passport\lib\authenticator.js:443:5)
    at …\core\node_modules\passport\lib\middleware\authenticate.js:247:22
    at IncomingMessage.req.login.req.logIn (…\core\node_modules\passport\lib\http\request.js:61:13)
    at Strategy.module.exports.strategy.success (…\core\node_modules\passport\lib\middleware\authenticate.js:228:13)
    at verified (…\core\node_modules\passport-http-bearer\lib\strategy.js:126:10)
    at checkResult (…\core\src\authentication\authentication.js:120:13)
From previous event:
    at Strategy.processBearerStrategy [as _verify] (…\core\src\authentication\authentication.js:107:6)
    at Strategy.authenticate (…\core\node_modules\passport-http-bearer\lib\strategy.js:132:10)
    at attempt (…\core\node_modules\passport\lib\middleware\authenticate.js:341:16)
    at authenticate (…\core\node_modules\passport\lib\middleware\authenticate.js:342:7)
    at enforceBearerToken (…\core\src\authentication\authentication.js:162:6)
    at Layer.handle [as handle_request] (…\core\node_modules\express\lib\router\layer.js:95:5)
    at next (…\core\node_modules\express\lib\router\route.js:131:13)
    at Route.dispatch (…\core\node_modules\express\lib\router\route.js:112:3)
    at Layer.handle [as handle_request] (…\core\node_modules\express\lib\router\layer.js:95:5)
    at …\core\node_modules\express\lib\router\index.js:277:22
    at Function.process_params (…\core\node_modules\express\lib\router\index.js:330:12)
    at next (…\core\node_modules\express\lib\router\index.js:271:10)
    at Function.handle (…\core\node_modules\express\lib\router\index.js:176:3)
    at router (…\core\node_modules\express\lib\router\index.js:46:12)
    at Layer.handle [as handle_request] (…\core\node_modules\express\lib\router\layer.js:95:5)
    at trim_prefix (…\core\node_modules\express\lib\router\index.js:312:13)
    at …\core\node_modules\express\lib\router\index.js:280:7
    at Function.process_params (…\core\node_modules\express\lib\router\index.js:330:12)
    at next (…\core\node_modules\express\lib\router\index.js:271:10)

The line in requestHandler also returns: return jobQueue.enqueue( functionRef ). Even though it doesn't really make sense, as it's an express middleware, which doesn't care about promises.
However, the enqueue call has a catch handler that already captures any possible failures. So I don't understand what the mistake here is or how I should change our code to avoid it.

What about at checkAuthenticationResult (…\core\src\authentication\authentication.js:173:11)? Is that inside a then handler and returning the promise created back at enqueue

That line is not in a .then handler, no. It's the last middleware before our actual request handler. Line 173 is just return next();, next here ending up as calling requestHandler.

What is at     at Strategy.processBearerStrategy [as _verify] (…\core\src\authentication\authentication.js:107:6)

Here's the entire function with line numbers:

checkResult is insode a then handler and calls done which ends up creating a promise further at enqueue but done is not returning it.
You can avoid the callback plumbing and the warning by using .asCallback:
.then(...).asCallback(done)
It will worry about turning rejections into err first callback and fulfillments into result callbacks, you just need to return the object from the .then

Actually there is a bug where asCallback emits the warming, ill fix that today

Wow, thanks a lot for your extensive help on this one :)


Add configure command to native messaging interface

Useful for benchmarking mostly

I marked it as draft because I just implemented this as a one-off for some benchmarking work. However, this functionality might be useful for other use cases as well.
There should be probably be a min(requested-threads, std::thread::hardware_concurrency()) or something.

Yeah, that's what I do: https://github.com/XapaJIaMnu/translateLocally/blob/master/src/settings/TranslatorSettingsDialog.cpp#L24
Should that be written to settings if changed?

Oeh note to self: it should do everything from the pointer reset line in std::async or something, because that's a blocking call that will wait for all still pending translations to finish. And that should not be blocking the event loop!
And then I need to think a bit about how it should treat translation requests that come in after the Configure command. They should be queued/processed after it, and not to the service that is about to be reset (thereby delaying the reset even more). So maybe the reset() should be blocking the event loop?


Update package.json

pogobuf (logon module) was updated

issue is not yet solved for a specific google account


[DO NOT MERGE] Testing pipeline runs

Related Issues/PRs

#xxx
What changes are proposed in this pull request?
Briefly describe the changes included in this Pull Request.
How is this patch tested?

[ ] I have written tests (not required for typo or doc fix) and confirmed the proposed feature/bug-fix/change works.

Does this PR change any dependencies?

[ ] No. You can skip this section.
[ ] Yes. Make sure the dependencies are resolved correctly, and list changes here.

Does this PR add a new feature? If so, have you added samples on website?

[ ] No. You can skip this section.
[ ] Yes. Make sure you have added samples following below steps.

Find the corresponding markdown file for your new feature in website/docs/documentation folder.
Make sure you choose the correct class estimators/transformers and namespace.
Follow the pattern in markdown file and add another section for your new API, including pyspark, scala (and .NET potentially) samples.
Make sure the DocTable points to correct API link.
Navigate to website folder, and run yarn run start to make sure the website renders correctly.
Don't forget to add <!--pytest-codeblocks:cont--> before each python code blocks to enable auto-tests for python samples.
Make sure the WebsiteSamplesTests job pass in the pipeline.

/azp run

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 16.11%. Comparing base (6854b5f) to head (3a330b1).

Additional details and impacted files
@@             Coverage Diff             @@
##           master    #2292       +/-   ##
===========================================
- Coverage   83.70%   16.11%   -67.59%
===========================================
  Files         327      327
  Lines       16788    16788
  Branches     1500     1500
===========================================
- Hits        14052     2706    -11346
- Misses       2736    14082    +11346

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Hide 00 bytes

It would be really cool if there was a menu to hide all the 00 bytes.
Any chance this will get implemented? =)

Sounds reasonable, I'd merge such a pull request.
If you'd like something comparable immediately, you can turn on byte coloring with "Font > Color bytes" and tweak the byte-coloring code on HFTextRepresenter.m:264 to, for example, return black when byte == 0 and transparent for all other bytes.

Done in #56 :)

Thanks!

@adius Interesting! What application does this have?

Just to able to see at a glance which bytes are not 00.
Comes in handy for file-types which may have a lot of 00s.


[OPERATOR]Agent injection webhook

Please answer these questions before submitting your issue.

Why do you submit this issue?
[ ] Question or discussion
[ ] Bug
[ ] Requirement
[x] Feature or performance improvement

Requirement or improvement
SWCK operator supports provisioning skywalking backends to a kubernetes cluster. However, the agent that generally refer to java, C#, python, and nodejs automatic instruments is the last piece of the puzzle.
After a long period of discussion and investigation, we have a plan to introduce a new webhook to inject agent images to workload pods automatically(by the operator) or manually(by swctl).
A canonical path to trigger auto-injection is to insert dedicated annotations to workloads and namespaces, then operator intercepts the provision of their pods, injecting agent relevant pieces into pod template. The result of injection might like below:

Does this mean, we are going to release agent images separately? If so, seems there are several things to adjust the release processes and docker files.

Does this mean, we are going to release agent images separately? If so, seems there are several things to adjust the release processes and docker files.

Exactly. The basic idea of images is to follow the backend convention. That means putting agent manifests into the skywalking-docker repo, releasing agent images as one step of the entire image release process, documenting the new images on the README.md of skywalking-docker, the official docker hub repo and skywalking website.

The key is you need to adjust main repo docker file, to make sure they are voted in the release. Your mentioned things are after release.

The key is you need to adjust main repo docker file...

I didn't find any reason to introduce the agent docker file into the main repo. The E2E of webhook will be added into swck repo with the agent docker image built from a released agent version.
Even though we submit it into the main repo, it seems nothing special should be taken care of in the release vote process? If I missed something, feel free to correct me.

If the docker file is never voted, then images can't be pushed as it is not an official release source codes.

I didn't find any reason to introduce the agent docker file into the main repo.

Only reason is, this image will need to push with every release. This is a requirement from a release vote perspective.

Hi there, I am interested in this issue and would like to participate in contributing code to SkyWalking through the opensource summer 2021 project. I prepared a technical proposal and wanted to further discuss the specific implementation with mentor of this issue. I tried to send an email but didn't get a reply, thanks very much if someone could tell me how to get involved in the work😀.

@hanahmily I think it is on your hands, right?

@kagaya85 I have not received messages from you. Since several students who want to join iscas have contacted with me, you seem to send the wrong address. My mail address is<EMAIL_ADDRESS>or<EMAIL_ADDRESS>We could discuss the details through the mail.

@hanahmily Thank you very much, I will try again to submit my application.

Resolved by https://github.com/apache/skywalking-swck/pull/30


remove

Thank you for your Pull Request!
Before you submitting, please check that:

[ ] You added a brief description of the PR, e.g.:

What does it do?
What important points reviewers should know?
Is there something left for follow-up PRs?

[ ] You labeled the PR appropriately if you have permissions to do so:

[ ] A* for PR status (one required)
[ ] B* for changelog (one required)
[ ] C* for release notes (exactly one required)
[ ] D* for various implications/requirements
[ ] Github's project assignment

[ ] You mentioned a related issue if this PR related to it, e.g. Fixes #228 or Related #1337.
[ ] You asked any particular reviewers to review. If you aren't sure, start with GH suggestions.
[ ] Your PR adheres to the style guide

In particular, mind the maximal line length of 100 (120 in exceptional circumstances).
There is no commented code checked in unless necessary.
Any panickers have a proof or removed.

[ ] You bumped the runtime version if there are breaking changes in the runtime.
[ ] You updated any rustdocs which may have changed
[ ] Has the PR altered the external API or interfaces used by Polkadot? Do you have the corresponding Polkadot PR ready?

Refer to the contributing guide for details.
After you've read this notice feel free to remove it.
Thank you!
✄ -----------------------------------------------------------------------------

/bench runtime --chain dev --steps 5 --repeat 2 --pallet pallet_balances --extrinsic "*" --execution=wasm --wasm-execution=compiled --output

/benchmark pallet pallet_balances

/benchmark pallet pallet_balances

/benchmark pallet pallet_balances

/benchmark pallet pallet_balances

/benchmark pallet pallet_balances

/benchmark custom --chain dev --steps 5 --repeat 2 --pallet pallet_balances --extrinsic "*" --execution=wasm --wasm-execution=compiled --output

/benchmarking

/benchmark

/benchmark pallet

/benchmark pallet frame_system

/bench

/bench

/benchmark custom --chain dev --steps 50 --repeat 20 --extrinsic "*" --raw --execution=wasm --wasm-execution=compiled --pallet pallet_multisig

/benchmark custom --chain dev --steps 50 --repeat 20 --extrinsic "*" --raw --execution=wasm --wasm-execution=compiled --pallet pallet_multisig

/benchmark test

/benchmark test noop

/benchmark custom --chain dev --steps 50 --repeat 20 --extrinsic "*" --raw --execution=wasm --wasm-execution=compiled --pallet pallet_multisig

/benchmark custom --chain dev --steps 5 --repeat 2 --pallet pallet_balances --extrinsic "*" --execution=wasm --wasm-execution=compiled --output

/bench runtime

/bench runtime

/bench runtime

/bench runtime pallet

/bench runtime pallet pallet_balances

/bench runtime pallet pallet_balances

/bench runtime pallet pallet_balances

/bench runtime pallet pallet_balanc

/benchmark runtime custom --chain dev --steps 5 --repeat 2 --pallet pallet_balances --extrinsic "*" --execution=wasm --wasm-execution=compiled --output

/bench

/bench runtime pallet pallet_balanc

/bench runtime pallet pallet_balances

/bench runtime pallet pallet_balances


Update book pdf filename in theme

This will use the more sensible quantitative_economics_with_python.pdf name for the complete pdf

this is also the name of the file produced by ipynb_pdf_constructor

@AakashGfude would you mind to copy this adjustment to quantecon.lectures.theme and quantecon.build.lectures?


Compatibility data: electrum greenaddress jaxx ledger-live mycelium

rebased

Added mycelium

@moneyball - please review for typos/formatting/etc. Let me know if you can't review this week. Thanks!

pushed commits with:

changes to the captions prefixes made per #183 (comment)
changes to caption wording based on Bitcoin Core wallet example
moved images into /rbf/ sub folder to be consistent with /segwit/ usability images (and more clear)
changes to 'na' vs 'untested' for rbf sending tests when service doesn’t send via rbf

rebased on master to get the latest compatibility styling and templates

i noticed that whichever section was clicked through to gets this blue background. it looks a bit out of place when scrolling around the page. is it intentional?

i'm wondering if we should have X instead of ? for wallets that don't support BIP125...the remaining portions of sending RBF are known to not work, right, so should be X not ?

is the checkmark the same size as the X? my eyes tell me the X is bigger, which makes it more prominent, and almost fooled me into thinking that it was affirmative that the feature was supported.

Should we put Segwit addresses section above RBF? I realize that isn't the order the research was conducted, but I would think we should order it based on what we believe will be of interest to our audience. I suspect there is more interest in Segwit support than RBF.

i noticed that whichever section was clicked through to gets this blue background. it looks a bit out of place when scrolling around the page. is it intentional?

Yep. We wanted to anchor link the user to the applicable section (based on the link they clicked on) and also visually indicate the section of the page that was referenced from the preceding page. Do you think there is something more we can do to clarify?

i'm wondering if we should have X instead of ? for wallets that don't support BIP125...the remaining portions of sending RBF are known to not work, right, so should be X not ?

I agree the ? might be confusing for the status of "untested" which is what those tests are. I think it is best to have a dash '-'. Which is actually the character that we use for "N/A" status in the table as well. The dash icon is still clickable through to the details of the test. I dont like the X because we really were not able to test it, so "untested" is correct, but I agree ? might not be best.

Should we put Segwit addresses section above RBF? I realize that isn't the order the research was conducted, but I would think we should order it based on what we believe will be of interest to our audience. I suspect there is more interest in Segwit support than RBF.

I dont have a strong preference on this. @jnewbery ?

I'd also slightly prefer Segwit before RBF.  Changing that only requires moving stuff around in one file, so it shouldn't be much work (I'm happy to do it).

Should we put Segwit addresses section above RBF?

I'd also slightly prefer Segwit before RBF. Changing that only requires moving stuff around in one file, so it shouldn't be much work (I'm happy to do it).

ACK. Let's do that.
I also find it slightly odd that now that the RBF and segwit tables link to #rbf and #segwit, there isn't a direct link to the top of the details page. One thing we could potentially do is change rbf and segwit to be tabs or collapsible sections.

@jnewbery

One thing we could potentially do is change rbf and segwit to be tabs or collapsible sections.

Putting the sections inside <details> tags would be easy for making them collapsible, but if they're collapsed by default then the links to the anchor targets couldn't automatically expand them without JS.  So far we've avoided any JS dependencies on the site except for special features like particular bech32 sending support sections.  (I don't know how to do tabs at all without JS, but even if there's a pure-CSS way, I suspect it would have the same problem.)

squashed commits to one per evaluated service

pushed a commit for the updated Blockstream Green logo vs older GreenAddress logo

I still see ? instead of dash.
My understanding is that the checkmark size will not be changed.

I still see ? instead of dash.

I think we can leave this as untested. If the icons become confusing for users (for this reason or others we have not thought of) we can revisit.

My understanding is that the checkmark size will not be changed.

Yep!

pushed a commit which removed segwitv1 usability examples, since we are not including segwitv1 data for now


Uf 11204

Types of changes

[x] Bug fix
[x] New feature
[x] Removed feature
[x] Code style update (formatting etc.)
[x] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] Documentation content changes
[ ] Content/Data

Does this PR introduce a breaking change?

[x] Yes (I have stepped the version number accordingly)
[ ] No

Checklist:

[x] My code follows the code style of this project.
[x] I have updated the documentation accordingly (if applicable).
[x] I have added/updated tests to cover my changes (if applicable).

Acted on review comments

Added circuit breakers


(Windows) Error when starting clean all-in-one example

I get Angular SSR Error: Error: Unknown asset: importsappapp.html when run npm run start.
Meteor version is 1.6
I guess this issue related to windows platform, I have windows 7 64x.
Any help to make it work?

Could you reproduce this?

@ardatan What do you mean? You can download all-in-one examples repo part and run start command. Well, if you have the same OS.

Same problem here (Windows 10 64bit) with the 'universal' and 'all-in-one' examples. After a clean install of Meteor 1.6 and cloning the angular-meteor repo both examples give the error:
Angular SSR Error: Error: Unknown asset: importsappapp.html
at getAsset (...\angular-meteor\examples\MeteorCLI\universal\.meteor\local\build\programs\server\boot.js:328:19)

The 'bare' and 'lazy-loading' don't have this problem, but won't run either. On the client i get the error:
clientimportsappapp.html:12 ERROR RangeError: Maximum call stack size exceeded

Yes, we have to fix that path issue on Windows. The fix will be released in a few days.

Cool! Great work!

@ardatan any update on this? Do we have a way to fix it temporary somehow?

We've updated angular-compilers and examples. This path issue on Windows has been fixed. You can update the packages:
meteor update --all-packages
And if you are still facing this problem, you can open a new issue.


"attach database" fails when file specified as URI

I'm trying to attach an existing database in read-only mode, thus using the URI form of the filepath.  This works from the sqlite command line:
kieffer$ sqlite3 :memory:
SQLite version 3.24.0 2018-06-04 14:10:15
Enter ".help" for usage hints.
sqlite> attach database 'file:/tmp/foo.sqlite?mode=ro' as foo_db;
sqlite> select count(*) from foo_db.events;
17249
sqlite> detach database foo_db;
sqlite> ^D

... however when I run() the command from sqlite3, it fails:
kieffer$ node
Welcome to Node.js v12.10.0.
Type ".help" for more information.
> sqlite3 = require('sqlite3')
{
  ...
  VERSION: '3.30.1',
  SOURCE_ID: '2019-10-10 20:19:45 18db032d058f1436ce3dea84081f4ee5a0f2259ad97301d43c426bc7f3df1b0b',
  ...
}
> db = new sqlite3.Database(':memory:')
Database { open: false, filename: ':memory:', mode: 65542 }
> db.run(`attach database 'file:/tmp/foo.sqlite?mode=ro' as foo_db`, console.log)
Database { open: true, filename: ':memory:', mode: 65542 }
> [Error: SQLITE_CANTOPEN: unable to open database: file:/tmp/foo.sqlite?mode=ro] {
  errno: 14,
  code: 'SQLITE_CANTOPEN'
}

FWIW,  I see the same issue when running this command in the "DB Browser for SQLite" app.

I'm just getting into sqlite3 for another project I'm contributing to, but what happens if you set the URI as file:/tmp/foo.sqlite without the ?mode=ro?

I faced the same problem in my project.
In my case, it causes built-in sqlite 'SQLITE_USE_URI' had be disabled.
A solution is to re-build with SQLITE_USE_URI flags.
export CPPFLAGS="-DSQLITE_USE_URI=1"; npm rebuild sqlite3 --build-from-source

DB.get('PRAGMA compile_options;') -->

[
...
  { compile_options: 'USE_URI' }
]

https://github.com/TryGhost/node-sqlite3/issues/1272#issuecomment-1030686397 is the valid fix for now. If there's sufficient demand, I'd accept a PR to add support for this 🙂


@shopify/shopify-api source maps don't point to source files

Issue summary
Before opening this issue, I have:

[x] Upgraded to the latest version of the relevant packages

@shopify/* package and version:
Node version:
Operating system:

[x] Set { logger: { level: LogSeverity.Debug } } in my configuration, when applicable
[x] Found a reliable way to reproduce the problem that indicates it's a problem with the package
[x] Looked for similar issues in this repository
[x] Checked that this isn't an issue with a Shopify API

If it is, please create a post in the Shopify community forums or report it to Shopify Partner Support

ESM source maps don't point to the source file because they go up 7 directories instead of the correct 5, for example:
../../../../../../../rest/admin/2024-04/index.ts instead of the correct ../../../../../rest/admin/2024-04/index.ts
Expected behavior
Source maps point to the source file.
Actual behavior
Source maps don't point to the source file because
Steps to reproduce the problem

yarn build

Debug logs
When building and aliasing to the local project, and running shopify app dev using the aliased local project:
Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-app-remix/dist/esm/server/index.mjs" points to
missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/adapters/web-api/index.mjs" points
to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-app-remix/dist/esm/server/shopify-app.mjs"
points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-app-remix/dist/esm/server/boundary/index.mjs"
points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/lib/index.mjs" points to missing
source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-app-remix/dist/esm/server/errors.mjs" points to
missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-app-remix/dist/esm/server/types.mjs" points to
missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-app-remix/dist/esm/r
eact/components/AppProvider/AppProvider.mjs" points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-app-remix/dist/esm/r
eact/components/AppProxyProvider/AppProxyProvider.mjs" points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-app-remix/dist/esm/r
eact/components/AppProxyLink/AppProxyLink.mjs" points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-app-remix/dist/esm/r
eact/components/AppProxyForm/AppProxyForm.mjs" points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/runtime/crypto/crypto.mjs" points
to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/runtime/http/index.mjs" points to
missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/runtime/crypto/types.mjs" points to
 missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/runtime
/platform/runtime-string.mjs" points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/runtime/http/headers.mjs" points to
 missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/runtime/http/cookies.mjs" points to
 missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/runtime/http/utils.mjs" points to
missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/runtime/crypto/utils.mjs" points to
 missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/adapters/web-api/adapter.mjs"
points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-app-remix/dist/esm/server/version.mjs" points to
 missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-app-remix/dist/esm/s
erver/authenticate/webhooks/register.mjs" points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-app-remix/dist/esm/s
erver/authenticate/admin/authenticate.mjs" points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-app-remix/dist/esm/server/override-logger.mjs"
points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-app-remix/dist/esm/s
erver/authenticate/login/login.mjs" points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-app-remix/dist/esm/s
erver/unauthenticated/admin/factory.mjs" points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-app-remix/dist/esm/s
erver/authenticate/helpers/add-response-headers.mjs" points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-app-remix/dist/esm/s
erver/authenticate/public/factory.mjs" points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-app-remix/dist/esm/s
erver/unauthenticated/storefront/factory.mjs" points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-app-remix/dist/esm/s
erver/authenticate/admin/strategies/auth-code-flow.mjs" points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-app-remix/dist/esm/s
erver/authenticate/admin/strategies/merchant-custom-app.mjs" points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-app-remix/dist/esm/s
erver/authenticate/admin/strategies/token-exchange.mjs" points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-app-remix/dist/esm/s
erver/authenticate/helpers/idempotent-promise-handler.mjs" points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-app-remix/dist/esm/s
erver/authenticate/flow/authenticate.mjs" points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-app-remix/dist/esm/s
erver/authenticate/fulfillment-service/authenticate.mjs" points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-app-remix/dist/esm/server/future/flags.mjs"
points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-app-remix/dist/esm/s
erver/authenticate/webhooks/authenticate.mjs" points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-app-remix/dist/esm/server/boundary/headers.mjs"
points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/rest/load-rest-resources.mjs"
points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-app-remix/dist/esm/server/boundary/error.mjs"
points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/lib/session/index.mjs" points to
missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/lib/auth/index.mjs" points to
missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/lib/utils/index.mjs" points to
missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/lib/webhooks/index.mjs" points to
missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/lib/clients/index.mjs" points to
missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/future/flags.mjs" points to missing
 source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/lib/billing/index.mjs" points to
missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/lib/config.mjs" points to missing
source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/lib/flow/index.mjs" points to
missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/lib/logger/index.mjs" points to
missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/lib/version.mjs" points to missing
source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/lib/clients/admin/rest/client.mjs"
points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/lib/fulfillment-service/index.mjs"
points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/lib/auth/oauth/types.mjs" points to
 missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/lib/session/session.mjs" points to
missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/lib/error.mjs" points to missing
source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/lib/types.mjs" points to missing
source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/lib/auth/oauth/token-exchange.mjs"
points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/lib/webhooks/types.mjs" points to
missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/lib/cli
ents/admin/graphql/client.mjs" points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/lib/clients/types.mjs" points to
missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/lib/utils/types.mjs" points to
missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-app-remix/dist/esm/react/const.mjs" points to
missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-app-remix/dist/esm/r
eact/components/RemixPolarisLink.mjs" points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-app-remix/dist/esm/s
erver/authenticate/helpers/ensure-cors-headers.mjs" points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-app-remix/dist/esm/s
erver/authenticate/helpers/reject-bot-request.mjs" points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-app-remix/dist/esm/s
erver/authenticate/helpers/respond-to-options-request.mjs" points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-app-remix/dist/esm/s
erver/authenticate/admin/billing/cancel.mjs" points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-app-remix/dist/esm/s
erver/authenticate/helpers/get-session-token-header.mjs" points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-app-remix/dist/esm/s
erver/authenticate/helpers/validate-session-token.mjs" points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-app-remix/dist/esm/s
erver/authenticate/admin/billing/require.mjs" points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-app-remix/dist/esm/s
erver/authenticate/admin/helpers/create-admin-api-context.mjs" points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-app-remix/dist/esm/s
erver/authenticate/admin/billing/request.mjs" points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-app-remix/dist/esm/s
erver/authenticate/admin/billing/check.mjs" points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-app-remix/dist/esm/s
erver/authenticate/admin/helpers/redirect.mjs" points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-app-remix/dist/esm/s
erver/authenticate/admin/helpers/ensure-app-is-embedded-if-required.mjs" points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-app-remix/dist/esm/s
erver/authenticate/admin/helpers/ensure-session-token-search-param-if-required.mjs" points to missing
source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-app-remix/dist/esm/s
erver/authenticate/admin/helpers/render-app-bridge.mjs" points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-app-remix/dist/esm/s
erver/authenticate/admin/scope/factory.mjs" points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-app-remix/dist/esm/s
erver/authenticate/admin/helpers/validate-shop-and-host-params.mjs" points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-app-remix/dist/esm/s
erver/clients/admin/factory.mjs" points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-app-remix/dist/esm/s
erver/unauthenticated/helpers/get-offline-session.mjs" points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-app-remix/dist/esm/s
erver/authenticate/public/checkout/authenticate.mjs" points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-app-remix/dist/esm/s
erver/authenticate/public/appProxy/authenticate.mjs" points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-app-remix/dist/esm/s
erver/authenticate/public/customer-account/authenticate.mjs" points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-app-remix/dist/esm/s
erver/authenticate/admin/helpers/redirect-to-shopify-or-app-root.mjs" points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-app-remix/dist/esm/s
erver/authenticate/admin/helpers/begin-auth.mjs" points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-app-remix/dist/esm/s
erver/authenticate/admin/helpers/handle-client-error.mjs" points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-app-remix/dist/esm/s
erver/authenticate/admin/helpers/redirect-to-auth-page.mjs" points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-app-remix/dist/esm/s
erver/authenticate/admin/helpers/redirect-with-exitiframe.mjs" points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-app-remix/dist/esm/s
erver/authenticate/admin/helpers/trigger-after-auth-hook.mjs" points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-app-remix/dist/esm/s
erver/authenticate/helpers/respond-to-invalid-session-token.mjs" points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-app-remix/dist/esm/s
erver/clients/storefront/factory.mjs" points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-app-remix/dist/esm/s
erver/authenticate/helpers/invalidate-access-token.mjs" points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-app-remix/dist/esm/s
erver/authenticate/helpers/create-or-load-offline-session.mjs" points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/lib/session/session-utils.mjs"
points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/lib/ses
sion/decode-session-token.mjs" points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/lib/auth/oauth/nonce.mjs" points to
 missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/lib/auth/oauth/oauth.mjs" points to
 missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/lib/auth/get-embedded-app-url.mjs"
points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/lib/auth/oauth/safe-compare.mjs"
points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/lib/utils/shop-validator.mjs"
points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/lib/utils/hmac-validator.mjs"
points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/lib/utils/version-compatible.mjs"
points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/lib/webhooks/registry.mjs" points
to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/lib/webhooks/register.mjs" points
to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/lib/webhooks/validate.mjs" points
to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/lib/webhooks/process.mjs" points to
 missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/lib/uti
ls/shop-admin-url-helper.mjs" points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/lib/cli
ents/graphql_proxy/graphql_proxy.mjs" points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/lib/clients/storefront/client.mjs"
points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/lib/billing/check.mjs" points to
missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/lib/billing/request.mjs" points to
missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/lib/billing/cancel.mjs" points to
missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/lib/billing/subscriptions.mjs"
points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/lib/flow/validate.mjs" points to
missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/lib/logger/log.mjs" points to
missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/lib/clients/common.mjs" points to
missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/lib/auth/scopes/index.mjs" points
to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/lib/ful
fillment-service/validate.mjs" points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/lib/utils/fetch-request.mjs" points
 to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/lib/auth/oauth/create-session.mjs"
points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-app-remix/dist/esm/s
erver/authenticate/const.mjs" points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-app-remix/dist/esm/s
erver/authenticate/admin/helpers/redirect-with-app-bridge-headers.mjs" points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-app-remix/dist/esm/s
erver/authenticate/admin/helpers/redirect-to-bounce-page.mjs" points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-app-remix/dist/esm/s
erver/authenticate/helpers/app-bridge-url.mjs" points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-app-remix/dist/esm/s
erver/authenticate/admin/helpers/validate-redirect-url.mjs" points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-app-remix/dist/esm/s
erver/authenticate/admin/scope/request.mjs" points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-app-remix/dist/esm/s
erver/clients/admin/graphql.mjs" points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-app-remix/dist/esm/s
erver/clients/admin/rest.mjs" points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-app-remix/dist/esm/s
erver/authenticate/public/extension/authenticate.mjs" points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/lib/utils/get-hmac-key.mjs" points
to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/lib/utils/processed-query.mjs"
points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/lib/auth/decode-host.mjs" points to
 missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/lib/webhooks/query-template.mjs"
points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-app-remix/dist/esm/s
erver/adapters/node/index.mjs" points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/rest/admin/2024-04/index.mjs"
points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-app-remix/dist/esm/s
erver/authenticate/admin/helpers/redirect-to-install-page.mjs" points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/rest/ad
min/2024-04/abandoned_checkout.mjs" points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/rest/ad
min/2024-04/access_scope.mjs" points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/rest/ad
min/2024-04/application_charge.mjs" points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/rest/ad
min/2024-04/application_credit.mjs" points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/rest/ad
min/2024-04/apple_pay_certificate.mjs" points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/rest/admin/2024-04/balance.mjs"
points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/rest/ad
min/2024-04/assigned_fulfillment_order.mjs" points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/rest/admin/2024-04/blog.mjs" points
 to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/rest/ad
min/2024-04/cancellation_request.mjs" points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/rest/admin/2024-04/article.mjs"
points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/rest/admin/2024-04/asset.mjs"
points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/rest/admin/2024-04/collection.mjs"
points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/rest/ad
min/2024-04/carrier_service.mjs" points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/rest/admin/2024-04/collect.mjs"
points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/rest/admin/2024-04/checkout.mjs"
points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/rest/ad
min/2024-04/collection_listing.mjs" points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/rest/admin/2024-04/comment.mjs"
points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/rest/ad
min/2024-04/custom_collection.mjs" points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/rest/admin/2024-04/country.mjs"
points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/rest/ad
min/2024-04/discount_code.mjs" points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/rest/admin/2024-04/currency.mjs"
points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/rest/admin/2024-04/customer.mjs"
points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/rest/admin/2024-04/dispute.mjs"
points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/rest/ad
min/2024-04/deprecated_api_call.mjs" points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/rest/ad
min/2024-04/customer_address.mjs" points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/rest/ad
min/2024-04/dispute_evidence.mjs" points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/rest/ad
min/2024-04/dispute_file_upload.mjs" points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/rest/admin/2024-04/event.mjs"
points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/rest/admin/2024-04/draft_order.mjs"
 points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/rest/admin/2024-04/fulfillment.mjs"
 points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/rest/ad
min/2024-04/fulfillment_event.mjs" points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/rest/ad
min/2024-04/fulfillment_request.mjs" points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/rest/ad
min/2024-04/fulfillment_order.mjs" points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/rest/ad
min/2024-04/fulfillment_service.mjs" points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/rest/admin/2024-04/gift_card.mjs"
points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/rest/ad
min/2024-04/inventory_item.mjs" points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/rest/admin/2024-04/image.mjs"
points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/rest/ad
min/2024-04/gift_card_adjustment.mjs" points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/rest/ad
min/2024-04/inventory_level.mjs" points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/rest/admin/2024-04/location.mjs"
points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/rest/admin/2024-04/metafield.mjs"
points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/rest/ad
min/2024-04/locations_for_move.mjs" points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/rest/ad
min/2024-04/marketing_event.mjs" points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/rest/admin/2024-04/order.mjs"
points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/rest/ad
min/2024-04/mobile_platform_application.mjs" points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/rest/admin/2024-04/order_risk.mjs"
points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/rest/ad
min/2024-04/payment_gateway.mjs" points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/rest/ad
min/2024-04/payment_transaction.mjs" points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/rest/admin/2024-04/payment.mjs"
points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/rest/admin/2024-04/policy.mjs"
points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/rest/admin/2024-04/payout.mjs"
points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/rest/admin/2024-04/price_rule.mjs"
points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/rest/admin/2024-04/product.mjs"
points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/rest/admin/2024-04/province.mjs"
points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/rest/ad
min/2024-04/recurring_application_charge.mjs" points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/rest/admin/2024-04/redirect.mjs"
points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/rest/ad
min/2024-04/product_listing.mjs" points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/rest/admin/2024-04/refund.mjs"
points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/rest/ad
min/2024-04/product_resource_feedback.mjs" points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/rest/ad
min/2024-04/resource_feedback.mjs" points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/rest/admin/2024-04/page.mjs" points
 to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/rest/admin/2024-04/script_tag.mjs"
points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/rest/ad
min/2024-04/tender_transaction.mjs" points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/rest/admin/2024-04/shop.mjs" points
 to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/rest/ad
min/2024-04/storefront_access_token.mjs" points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/rest/admin/2024-04/theme.mjs"
points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/rest/ad
min/2024-04/smart_collection.mjs" points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/rest/admin/2024-04/transaction.mjs"
 points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/rest/ad
min/2024-04/usage_charge.mjs" points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/rest/admin/2024-04/variant.mjs"
points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/rest/admin/2024-04/user.mjs" points
 to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/rest/ad
min/2024-04/shipping_zone.mjs" points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/rest/admin/2024-04/webhook.mjs"
points to missing source files
14:23:12 │ remix         │ Sourcemap for ".../shopify-app-js.nosync/packages/apps/shopify-api/dist/esm/rest/base.mjs" points to missing```

I can confirm the issue still occurs and is still valid. Do we have an update on this or were you able to resolve this?


Could not parse version for tool 7zip. Version string was: 19.00

Describe the bug
A clear and concise description of what the bug is.
Environment

OS: Windows 10
Compiler: vs2019

To Reproduce
Steps to reproduce the behavior:

./vcpkg install zlib:x64-windows
See error
Repro code when

Expected behavior
A clear and concise description of what you expected to happen.
Failure logs
Warning: Different source is available for vcpkg (2020.6.15 -> 9999.99.99). Use .\bootstrap-vcpkg.bat to update.
Computing installation plan...
The following packages will be built and installed:
zlib[core]:x64-windows
Warning: The following VS instances are excluded because the English language pack is unavailable.
D:\Applications\VisualStudio2017
C:\Program Files (x86)\Microsoft Visual Studio 12.0
Please install the English language pack.
Detecting compiler hash for triplet x64-windows...
A suitable version of powershell-core was not found (required v7.1.3). Downloading portable powershell-core v7.1.3...
Downloading powershell-core...
https://github.com/PowerShell/PowerShell/releases/download/v7.1.3/PowerShell-7.1.3-win-x86.zip -> D:\Code\vcpkg\downloads\PowerShell-7.1.3-win-x86.zip
Extracting powershell-core...
Could not parse version for tool 7zip. Version string was: 19.00
Additional context
I have installed VS2019 so I ignore the warning about VS2017

@BenXu86, could you get vcpkg latest source via 'git pull' and '.\bootstrap-vcpkg.bat', then try again?

@BenXu86, could you get vcpkg latest source via 'git pull' and '.\bootstrap-vcpkg.bat', then try again?

I try again. But I still get the same error.

@BenXu86, could you install English language pack via VS installer and try again? You can also reference https://www.cnblogs.com/vcpkg/p/14550099.html. BTW, we have many blogs posted about VCPKG in https://www.cnblogs.com/vcpkg/ for Chinese users, you can reference them if you needed.
Warning: The following VS instances are excluded because the English language pack is unavailable.

@BenXu86 I can confirm that both current master (e201002) and commit at 2021-08-21 (ab60f27) will not cause the problem you described. In fact, the only possible way I can come up with is that you updated your local vcpkg branch to track the remote branch yet forgot to run booststrap.bat and left your vcpkg.exe with a version released before 6 months ago. Do you still have this issue after syncing your local vcpkg branch to current master and rerunning booststrap.bat to update your vcpkg.exe?

@BenXu86, please reopen this issue if it still be a problem for you.


ESTOFS

ESTOFS is still found using the catalog search, but the returned URL seems to be down:
http://geoport-dev.whoi.edu/thredds/dodsC/estofs/atlantic
@rsignell-usgs any ideas?

OK.  ESTOFS is back online and I did not notice.  The logs show that the notebooks are picking it up.
However, the data is not being paired with any station.  I still have an issue somewhere else down the road...

It's not working even in the inundation notebook?

Nope.  I think I know where to problem is.  I will address that later today.

Is it related to this issue? https://github.com/ocefpaf/boston_light_swim/issues/2

Yep.  That is another bug fixed thanks to boston_light_swim!

See #209

nice!


Regarding https://github.com/zulip/zulip/pull/32361#discussion_r1844664525 -

Regarding https://github.com/zulip/zulip/pull/32361#discussion_r1844664525 -
If we want to do a single query we can do a union since we want to query fields from two different tables. We can do something like this -
    user_members = UserGroupMembership.objects.filter(user_group_id__in=group_ids).annotate(
        member_type=Value("user"),
        named_user_group=Q(user_group__named_user_group__isnull=False),
    ).values_list("member_type", "named_user_group", "user_group_id", "user_profile_id")

    group_subgroups = GroupGroupMembership.objects.filter(supergroup_id__in=group_ids).annotate(
        member_type=Value("group"),
        named_user_group=Q(supergroup__named_user_group__isnull=False),
    ).values_list("member_type", "named_user_group", "supergroup_id", "subgroup_id")

    all_members = user_members.union(group_subgroups)

And then we can just iterate through members list and form the object. Do we want to do something like this?
We can make the code more readable by doing a separate query for determining anonymous groups and then fetch members and subgroups only for anonymous groups.
Originally posted by @sahil839 in https://github.com/zulip/zulip/pull/32392#issuecomment-2486175645

This was already done in b6f895f61c99494e236af303f4bb6955c2e5f37d, I think.


Pressure Test：got error

What happened:
when I did pressure test on seata-go，I got Error：

What you expected to happen:   show right error info，not panic
How to reproduce it (as minimally and precisely as possible):
tps : 10, keep several sec
Anything else we need to know?:

the ExecContext have not use the conn pool( inited in my code), I have SetMaxOpenConns(2), but mysql have more conn
and when the conn amount bigger and bigger, it reach the max_connections


Feature/fix issue 540

Coverage increased (+0.08%) to 100.0% when pulling c2bc780f700e7a01efcf449972065bba1d85dc5b on feature/fix-issue-540 into b8a99d6c80c629fb3845e8953637fefc4cc09109 on develop.

Coverage increased (+0.08%) to 100.0% when pulling c2bc780f700e7a01efcf449972065bba1d85dc5b on feature/fix-issue-540 into b8a99d6c80c629fb3845e8953637fefc4cc09109 on develop.

Coverage increased (+0.08%) to 100.0% when pulling c2bc780f700e7a01efcf449972065bba1d85dc5b on feature/fix-issue-540 into b8a99d6c80c629fb3845e8953637fefc4cc09109 on develop.


It is not always automatic completion.

<script setup>
  import { ref } from 'vue'
  const value = ref(1)
</script>

<template>
  {{ value }}
</template>

<script setup>
  const value = ref(1)
</script>

<template>
  {{ value }}
</template>

But both can be used normally
I should choose the former, right?
The latter does not look like typescript support

Generate corresponding .eslintrc-auto-import.json file
I tried my best and didn't generate this file
I deleted the config... 😄

You need to enable dts for typescript support. Refer to https://github.com/antfu/vitesse


errors(ticdc): clean up unused errors

What problem does this PR solve?

Issue Number: close #8468
What is changed and how it works?
Clean up unused code in package errors.
Check List
Tests

Unit test
Integration test

Questions
Will it cause performance regression or break compatibility?
No
Do you need to update user documentation, design documentation or monitoring documentation?
No
Release note
None

/run-all-tests

/merge


Problem with Cloudant

I always getting the 403 error. This is my user documment in _users:
{
"_id": "3ae2b004f63f76a1d936b0cce2e96d2c",
"_rev": "3-77f93ee6a9e99d6769dc528c0bcb82bf",
"value": {
"rev": "3-77f93ee6a9e99d6769dc528c0bcb82bf"
},
"key": "3ae2b004f63f76a1d936b0cce2e96d2c",
"doc": {
"_id": "3ae2b004f63f76a1d936b0cce2e96d2c",
"_rev": "3-77f93ee6a9e99d6769dc528c0bcb82bf",
"name": "admin",
"roles": [
"_reader",
"_writer"
],
"type": "user",
"password": "37d6c5Qe"
}
}
I'm calling db.login('admin', '37d6c5Qe')

I don't believe pouchdb-authentication supports Cloudant. I'm told they were working on adding support, but last I heard it's not in yet. You can contact Cloudant customer support for more help.

Yes, I make a suppport request, I will come back here.

@sebrojas14 Any updates?

So, after playing a bit with cloudant Ionic2 and pouchdb-authentication I can tell you that they are 100% compatible.
The error is happening because Cloudant don't user the _user database as we expect.
When you signup a new user db.signup() with any cloudant database as remote, the user is created in the _user database but no entry is sent to the permission schema inside cloudant database.
Cloudant manage users differently by generating API keys and checking granted roles.
The catch is to add a user in the Permissions schema of the database through cloudant console where the actual user has been created and grant him some roles.
The way cloudant is actually creating users is to generate an API key for the database of your choice like explained here :
https://docs.cloudant.com/authorization.html
At the bottom of the previous link it's mentioned that is possible to use the _user database to manage users. I'll check that in a couple of hours and report here :

You can use the _users database to manage roles in Cloudant. However, you must turn off Cloudant security for those roles first. To do this, PUT a JSON document to the _security endpoint of the database. For example, https://.cloudant.com//_security.

You can use Node to do it for you :
https://github.com/cloudant/nodejs-cloudant#generate-an-api-key


The chart application version is not up to date

Looks like the chart version in the 0.13 shows the 0.9 version.
This is up to date: https://artifacthub.io/packages/helm/cert-manager/trust-manager
This is the 0.13 tag:
https://github.com/cert-manager/trust-manager/blob/v0.13.0/deploy/charts/trust-manager/Chart.yaml

Thanks for reporting this @evgeni-roif-gong! It appear like something isn't right. I will take a closer look.

@evgeni-roif-gong It seems like the version is overwritten when a release is cut, but I agree that this is confusing. WDYT of setting a dummy version in Git like 0.0.0? This should be improved, so I would like to keep this issue open - even if it is not a bug.


List/array of all form validation errors?

Looking for a way to get a list of all form validation errors. We tried what was suggested here:  http://stackoverflow.com/questions/22322925/angularjs-list-all-form-errors however... the outout on $error etc. was strange/unusable (i.e. key names of "{{form.key.slice(-1)[0]}}").
Is there a way to get an array of the errors (especially error messages) after validation?
We have a large form and would like to use growl to present a list rather than have the user have to hunt up and down the page exclusively to locate each of the error fields.

Yo can do some angular black magic and use the sfErrorMessages to get the actual error messages from the error code. Something like this:

var errors = [];
$('[schema-validate]').each(function() {
  // schema-validate directive puts the ngModelController on scope as `ngModel`
  // from that we can get error codes
  var scope = $(this).scope();
  var sfErrorMessage = $(this).injector().get('sfErrorMessage');
  var errs = angular.copy(scope.ngModel.$error);
  delete errs.parse;
  var error = Object.keys(errs)[0];

  if (error) {
    errors.push({
      title: scope.form.title,
      error: error,
      msg: sfErrorMessage.interpolate(
                error,
                scope.ngModel.$modelValue,
                scope.ngModel.$viewValue,
                scope.form,
                scope.options && scope.options.validationMessage
              )
    });
  }
});

console.log(errors);

When i put this code inside my controller $('[schema-validate]') is empty. So nothing to "each" about.

I had to wrap that inside a $timeout function to make this work!

Please re-open if you do not feel the question has been answered sufficiently.


fix .dockerignore to satisfy OCP specific requirements

Apparently, OSBS relies on adding specific Dockerfile during an image build. Having Dockerfile* pattern in .dockerignore cause issues.

/lgtm

This is great, it fixed the problem.
We're going to need this backported as far as it's relevant, because in the near future everything will be building on OSBS2.
/cherry-pick release-4.11

manually created https://github.com/openshift/cloud-provider-azure/pull/38


Extract deb and rpm without needing dkpg

Similar to https://gist.githubusercontent.com/ruario/a98005997f7c111ba44d908594f028dd/raw/0d1e78c669eb234ce9452f2cbed26dd2fd53b68a/appimage-vivaldi.sh

As discussed on IRC, a dependency on dpkg shouldn't be much of a problem, as we could just include that in an AppImage for the deb to AppImage conversion software.


Reword ending message in quickstart. Fix #108

Issue #108

@mkorakakis Looks good. Not sure, but Windows understands && right?

The accepted answer in http://superuser.com/questions/62850/execute-multiple-commands-with-1-line-in-windows-commandline confirms my doubt:

&& will execute command 2 when command 1 is complete providing it didn't fail

LGTM


Initial implementation

Changes

Add initial Dockerfile with script to run steamcmd and upload the build to steam.

Checklist

[X] I read the contribution guide and accept the code of conduct.
[x] Verify whether this works with a workflow
[ ] Probably delete and start over with a better approach

This is close to a working example. I'm counting this is the initial implementation, although some parts may not fully work yet.


Remove is_ground_truth and is_detection properties

The current BoundingBox class has properties is_ground_truth and is_detection that are basically just aliases for self.confidence is None and self.confidence is not None respectively. Some models may not produce confidence scores, which then causes issues during evaluate_boxes in evaluation.py. I could add fake confidence values when creating the detection AnnotationSet, but I think it would be better to not mandate users to provide confidence values.
I have tested locally and everything passes. You may want to consider altering the GitHub action to automate tests on pull requests? I can open this up as a separate PR.

I'm looking into this one more closely since it would change the existing behavior and could potentially introduce subtle bugs.
For instance the current behavior is to raise an error if the prediction bounding boxes do not have a confidence since it is probably a logic error from the user (e.g. it supplied a ground-truth set instead of the predictions one). The new behavior would not catch this error anymore. Maybe we could add a new optional ignore_confidence argument defaulting to False to COCOEvaluator to support your use case.
However, I wonder is this use case is very common. Do you have examples of object detectors that do not output confidence scores or is this just to support the use case where the user did not saved the scores?
I also need to make sure that this does not break the reproducibility of the evaluation since this would makes the prediction bounding boxes order dependent.

However, I wonder is this use case is very common. Do you have examples of object detectors that do not output confidence scores or is this just to support the use case where the user did not saved the scores?

Some models don't provide confidences by default. For example, traditional (non-neural network) computer vision detectors (see for example, online tutorials here  and here). Some neural network architectures don't provide confidences either unless extra post processing is applied (e.g., WPOD-NET for license plate detection). I imagine most users will be using more typical object detectors (e.g., YOLO, R-CNN etc.) where confidences are provided by default, but I think there would be enough demand for detectors that don't provide confidences.

For instance the current behavior is to raise an error if the prediction bounding boxes do not have a confidence since it is probably a logic error from the user (e.g. it supplied a ground-truth set instead of the predictions one).

The COCOEvaluator.__init__ uses mandatory keyword arguments via the * operator for ground truth and predictions AnnotationSet. We could look at expanding the use of mandatory keyword arguments to class methods such as COCOEvaluator.evaluate_annotations and COCOEvaluator.evaluate_boxes to minimise the chance of user error? Or maybe the underlying AnnotationSet should have a user-specified attribute for is_ground_truth, rather than using the presence of confidences as a proxy?

I also need to make sure that this does not break the reproducibility of the evaluation since this would makes the prediction bounding boxes order dependent.

Agreed. I don't love my current implementation that currently assigns minimum confidence to no-confidence predictions:
dets = sorted(predictions, key=lambda box: box._confidence if box._confidence is not None else -float("inf"), reverse=True)

I'm definitely open to exploring other solutions if you don't like the above behaviour.

So experimented with your implementation of the COCO evaluation without confidence scores and found that the metrics are dependent on the order of the bounding boxes. Here is a failing test case that illustrate this:
def test_evaluator_no_confidence_invariance_to_bboxes_order():
    gts = AnnotationSet(annotations=[
        Annotation("img_1", image_size=(100, 100), boxes=[
            BoundingBox(label="cat", xmin=0, ymin=0, xmax=3, ymax=3),
            BoundingBox(label="cat", xmin=1, ymin=0, xmax=4, ymax=3),
        ])
    ])

    dets_1 = AnnotationSet(annotations=[
        Annotation("img_1", image_size=(100, 100), boxes=[
            BoundingBox(label="cat", xmin=-1, ymin=0, xmax=2, ymax=3),
            BoundingBox(label="cat", xmin=0, ymin=0, xmax=3, ymax=3),
        ])
    ])

    dets_2 = AnnotationSet(annotations=[
        Annotation("img_1", image_size=(100, 100), boxes=[
            BoundingBox(label="cat", xmin=0, ymin=0, xmax=3, ymax=3),
            BoundingBox(label="cat", xmin=-1, ymin=0, xmax=2, ymax=3),
        ])
    ])

    evaluator_1 = COCOEvaluator(ground_truths=gts, predictions=dets_1)
    ap_1 = evaluator_1.ap_50()

    evaluator_2 = COCOEvaluator(ground_truths=gts, predictions=dets_2)
    ap_2 = evaluator_2.ap_50()

    assert isclose(ap_1, ap_2)

Here, the only difference between dets_1 and dets_2 is the order of the two bounding boxes in the (unique) annotation. This ends up in producing different AP 50 (100% vs 50%).
In fact, COCO evaluation requires the ranking of bounding boxes with their confidence score, thus, this would be inappropriate to modify the current implementation in the proposed way.
I think that the most correct way to handle predictions without confidence score is the one you suggested: assigning "fake" confidence scores to the bounding boxes. In this case, the value does not matter (assuming that the same value is assigned to all bounding boxes) but I suggest a value of 1.0. Note that you'll still have to deal with the dependence of the metrics on the order of the bounding boxes. You could sort the bounding boxes according to an arbitrary value, for instance xmin, to deal with this issue.

I see your point now. I didn't realise that the assignment between detection boxes and ground truth boxes was done by ordering the confidence values. I had previously assumed that this matching was done with a more global approach - something like a Hungarian algorithm to maximise average IOU. No worries, I'll close this PR :)


fix more unittests

testAdapter didn't have the actual .startTest() method which returns a promise.

@tomlm. The build is broken. :(

Pull Request Test Coverage Report for Build 1280

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.007%) to 69.59%

Totals

Change from base Build 1276:
0.007%

Covered Lines:
2192

Relevant Lines:
3009

💛  - Coveralls


Psycrometric calculations: Add extended docs

Closes #1746
Adds extended documentation for the new psychrometric calculations added for the hail-from-global-data work.
Best way to review the changes in their rendered form is to check-out the branch and run bin/improver-tests doc, then firefox doc/build/html/

The line length issue that @Kat-90 highlights is present in the web-rendered version as well.
This pre-exists this change (e.g. here) so is not specifically an issue with this PR, but if you can find a nice fix that would be great.

This page suggests a solution, so I've added add_module_names = False to conf.py. Let me know if you think this is an improvement.
https://stackoverflow.com/questions/60251546/sphinx-latex-break-line-autodoc


eslint-plugin-lit-a11y throws error with newer versions of peer packages

Expected behavior
Linting to work.
Actual Behavior
/node_modules/eslint-plugin-lit-a11y/lib/rules/accessible-emoji.js:85
                  ) ?? node.loc;
                     ^

SyntaxError: Unexpected token '?'
    at new Script (vm.js:88:7)
    at NativeCompileCache._moduleCompile (/home/acory/WORK/etools-infra/pmp/node_modules/v8-compile-cache/v8-compile-cache.js:240:18)
    at Module._compile (/home/acory/WORK/etools-infra/pmp/node_modules/v8-compile-cache/v8-compile-cache.js:184:36)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1027:10)
    at Module.load (internal/modules/cjs/loader.js:863:32)
    at Function.Module._load (internal/modules/cjs/loader.js:708:14)
    at Module.require (internal/modules/cjs/loader.js:887:19)
    at require (/home/acory/WORK/etools-infra/pmp/node_modules/v8-compile-cache/v8-compile-cache.js:159:20)
    at /home/acory/WORK/etools-infra/pmp/node_modules/requireindex/index.js:52:28

Additional context
Package  versions:
 "@typescript-eslint/eslint-plugin": "^5.7.0",
 "@typescript-eslint/parser": "^5.7.0",
 "@typescript-eslint/typescript-estree": "^5.7.0",
 "eslint": "^7.32.0",
 "eslint-config-prettier": "^8.3.0",
 "eslint-plugin-lit": "^1.6.1",
 "eslint-plugin-lit-a11y": "^2.2.0",
 "eslint-plugin-prettier": "^4.0.0",
 "prettier": "~2.5.1",
 "typescript": "^4.5.4"

Node version: 12.22.7

This seems more like an issue with your node version, than to do with packages. Are you using a node version that supports nullish coalescing?

Node version: 12.22.7.
Not sure if it supports nullish coalescing, probably not, because I just downgraded eslint-plugin-lit-a11y from 2.2.0, to 1.1.0, and it doesn't throw the error on the 1.1.0 version.

Seems like we introduced nullish coalescing somewhere between version 1.1.0 and 2.2.0 then. Nullish coalescing requires node 14. Since node 16 is LTS, i'll close this issue.


Consider using webpack-dashboard for easier development process.

Could we include webpack-dashboard into dev dependencies?
I feel like it would allow for easier development.

Duplicate of #449.

As explained in #449 we’ll hold off for now.

My bad, I only looked for issues, not PR's.


lax.scan fails for zero-length arrays

Reproducer:
>>> lax.scan(lambda acc, x: (acc, None), 0.0, jnp.arange(0))
...
TypeError: slice slice_sizes must be less than or equal to operand shape, got slice_sizes (1,) for operand shape (0,).

I expect lax.scan to return (0.0, []) in this case.

Unable to reproduce; got the following as output:
(0.0, None)

Feel free to reopen, if I'm mistaken. 🙂


is_cuda_available crash

Just installed this for fun on a computer without a GPU and found a bug, maybe easy to fix?
>>> import warp as wp
>>> wp.is_cuda_available()
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/usr/local/lib/python3.8/dist-packages/warp/context.py", line 871, in is_cuda_available
    return runtime.cuda_device != None
AttributeError: 'NoneType' object has no attribute 'cuda_device'

Oh, I have to call wp.init() first, not sure if this counts as a bug then.

Thanks, we handle this better now in 0.4.3.
Cheers,
Miles


Extremely large bundle size

Stat size: 486.25 KB,
Parsed size: 482.25 KB
Gzipped size: 100.87 KB
Is there any way to bring this module down?

Decided to go with individual modules https://github.com/RobinHerbots/Inputmask


[BUG] Decouple tests from source code structure/response values

Describe the bug
Our tests missed this breaking change: https://github.com/opensearch-project/index-management/issues/108
This is because the test imports the source code setting value and uses it in the test. So when the source code and test was changed it wasn't clear that the actual response of the API had changed as the tests continued passing with the new setting key value.
For these things that should not change, we should hardcode the value in the tests themselves to ensure that if someone accidentally changes the source code it is caught in the test.

Maybe we can get something methodical that records API requests and compares outputs?

Maybe this can be part of backward compatibility tests #125


renames all scalar function names to lowercase

CamelCase names are transformed to lowercase using _ as word boundary (affects mostly internal functions)

ack


Fix scienta txt reader

[x] use data model to validate types of reader data
[ ] update config file to latest NXmpes
[x] add example data
[x] add test data

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

69 of 128 (53.91%)  changed or added relevant lines in 4 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+1.2%) to 50.0%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pynxtools_xps/scienta/scienta_txt.py
12
71
16.9%

Totals

Change from base Build<PHONE_NUMBER>:
1.2%

Covered Lines:
1344

Relevant Lines:
2688

💛  - Coveralls


Set default number of threads to 2

As a temporary measure related to #1064, set default number of threads to 2 to avoid slowing things down on systems with lots of available threads.

Coverage increased (+0.7%) to 82.728% when pulling f07c1497a2b7f285fc2d0091162b5b210e679264 on gnafuthegreat:patch-1 into 71ccd911150eec3a095c883d3da289fac25d1ff7 on xiph:master.

Ok, let make the API threads aware and have everything use a custom threadpool.

Looks like @lu-zero handled this more thoroughly with #1083, so I'm closing this PR.


remove staging area functionality

@rly as we discussed, this removes all staging area functionality because this is now replaced by the writeable .lindi.tar and .lindi.d formats.
Also removed the File() class which was supposed to be a drop-in replacement for h5py.File including writing to a staging area.
Also removed the upload() capability. That should be handled separately, IMO.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 67.16%. Comparing base (3c1c976) to head (1da28ec).

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #97      +/-   ##
==========================================
- Coverage   69.10%   67.16%   -1.94%
==========================================
  Files          34       30       -4
  Lines        3046     2796     -250
==========================================
- Hits         2105     1878     -227
+ Misses        941      918      -23

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

Also removed the File() class which was supposed to be a drop-in replacement for h5py.File including writing to a staging area.

Just wanted to clarify, is this the same as the h5py.File type class that is being used for reading from HDF5 files or is this a separate class that was used just for writing data to a staging area?

Also removed the File() class which was supposed to be a drop-in replacement for h5py.File including writing to a staging area.

Just wanted to clarify, is this the same as the h5py.File type class that is being used for reading from HDF5 files or is this a separate class that was used just for writing data to a staging area?

It's confusing, sorry. The primary class for reading hdf5 files in lindi (and doing other manipulations) is LindiH5pyFile which has type h5py.File for compatibility purposes. This lindi.File that is being removed was different. It was supposed to be a drop-in replacement for h5py.File for both reading and writing with a staging area. But now that staging area is going away and there is a different mechanism for writing, this lindi.File needs to disappear as well. Hopefully with its demise the confusion will end here. :)

Looks good to me!


[BUG] Cannot use leading 0 in UE HPLMN MNC

When UE MNC is set to 010 the leading 0 is dropped. This results in the SUPI being incorrect. I am testing with 315010, when i set this MNC it becomes 315100
To Reproduce
Set the UE HPLMN MNC with a leading 0 (010) for example, try to perform a UE attach.
Expected behavior
The MNC remains as 010.
Screenshots
Configuration:

PCAP:

Architecture (please complete the following information):

OS: Ubuntu 22.04
Platform x86_64

Hi @jakekasper2,
Thank you for your report. Could you try this PR https://github.com/HewlettPackard/PacketRusher/pull/103? I should have solved this issue in this PR.
Thanks a lot!
Cheers,
Valentin

Hi @jakekasper2, Thank you for your report. Could you try this PR #103 / branch 3digitsmnc? I should have solved this issue in this PR.
git clone https://github.com/HewlettPackard/PacketRusher
cd PacketRusher
git checkout 3digitsmnc
# And then proceed with the usual installation steps

Thanks a lot! Cheers, Valentin

Thank you, even after moving to the 3digitsmnc the same behavior is observed.
Additionally, it appears that when using the 010 MNC it is making the SUPI too many digits and thus invalid.

@jakekasper2
Did you rebuild packetrusher binary with go build cmd/packetrusher.go after switching branch to 3digitsmnc?
I'll try to reproduce your issue.
Thanks!

@jakekasper2 Did you rebuild packetrusher binary with go build cmd/packetrusher.go after switching branch to 3digitsmnc? I'll try to reproduce your issue. Thanks!

I'm sorry for my ignorance. I just pulled the fresh package based on your steps above. It is running, however, it is now "stuck". It doesn't ever start the SCTP connection to the AMF. It just sits here forever.
This is the only output:
root@packetrusher:/usr/src/PacketRusher# ./packetrusher ue
INFO[0000] Selecting x.x.x.x for host x.x.x.x as AMF's IP address
INFO[0000] Selecting x.x.x.x for host x.x.x.x as gNodeB's N3/Data IP address
INFO[0000] Selecting x.x.x.x for host x.x.x.x as gNodeB's N2/Control IP address
INFO[0000] Loaded config at: /usr/src/PacketRusher/config/config.yml
INFO[0000] PacketRusher version 1.0.1
INFO[0000] ---------------------------------------
INFO[0000] [TESTER] Starting test function: Testing an ue attached with configuration
INFO[0000] [TESTER][UE] Number of UEs: 1
INFO[0000] [TESTER][UE] disableTunnel is false
INFO[0000] [TESTER][GNB] Control interface IP/Port: x.x.x.x/9487
INFO[0000] [TESTER][GNB] Data interface IP/Port: x.x.x.x/2152
INFO[0000] [TESTER][AMF] AMF IP/Port: x.x.x.x/38412
INFO[0000] ---------------------------------------

Hi @jakekasper2,
The main branch of the repository should have fixed your issue, you can try by switching back to the main branch, pulling latest changes and building the project again.
cd PacketRusher
git checkout main
git pull
go build cmd/packetrusher.go

Feel free to open another issue if you are still having problems!
Thanks and cheers,
Valentin


Remove outdated statement about IoT Plug and Play

The statement was only true in the 2019 preview of IoT Plug and Play. Since GA in 2020 the described behavior no longer applies and should be removed.

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

thanks for making these changes  @wickste. Looks good to be merged! #sign-off


updated docker compatibility in v4

In v4 the docker would not run unless it was modified. The dashboard.py had a typo in it that needed to be fixed. The requirements were updated to work with dashboard_new.py, but ended up removing needed requirements for dashboard.py.
The big changes mad in this pull request was adding handling in the entrypoint.sh via environment variable to be able to run either the dashboard.py or dashboad_new.py. In the docker-compose.yml it shows the lines you need if you want to use the newer dashboard.

@brandon-layton if you want we can work together to create the best possible Docker image. If you have time, please review: https://github.com/donaldzou/WGDashboard/issues/272


Suggest setting password on redis database and update instructions about what to pass to cf cups.

Fixes #31 .

Thanks, Leah!