onTapXX method called incorrect with TapCallbacks  on Flame 1.2.0+

Current bug behaviour
I am using  FlameGame and try to add a PositionComponent to game. onTapXX method called incorrect with TapCallbacks when I change the PositionComponent's position on version 1.2.1
I found the method componentsAtPoint in Component class is incorrectly pass the global point into containsLocalPoint.
Expected behaviour
I think the point need parentToLocal first when the component is CoordinateTransform and parent is not null.
Steps to reproduce
call parentToLocal before containsLocalPoint
    if (this is CoordinateTransform && parent != null) {
      localPoint = (this as CoordinateTransform).parentToLocal(point) ?? point;
    }
    if (containsLocalPoint(localPoint)) {
      yield this;
    }

Flutter doctor output
not need

More environment information

Flame version: 1.2.1

Log information
More information
I will make a pull request to fix this bug.

The method componentsAtPoint(point) is supposed to accept a point which is in the local coordinate space. So I believe that it works as it's supposed to.
The tap events do get dispatched as they are supposed to, as can be seen in demos at
https://docs.flame-engine.org/main/tutorials/klondike/step4.html and https://docs.flame-engine.org/main/flame/inputs/tap-events.html#demo.
If you did find a certain configuration which cause a buggy behavior, then a Minimum Reproducible Example would help greatly to debug it.

Tap the PeopleComponent first and the TapEvent will incorrect call when the Component moving down( Tap area is far from the drawed Rect).
class MainGame extends FlameGame with HasTappableComponents {
  @override
  Future<void>? onLoad() {
    add(PeopleComponent());
    return super.onLoad();
  }
}

class PeopleComponent extends PositionComponent with TapCallbacks {
  PeopleComponent() : super(size: Vector2(160, 160));

  Offset circleCenter = const Offset(0, 0);
  final Paint paint = Paint()..color = Colors.yellow;
  bool isMoving = false;

  var move = Vector2(0, 1);

  @override
  void render(Canvas canvas) {
    super.render(canvas);
    canvas.drawRect(Rect.fromCircle(center: center.toOffset(), radius: 80), paint);
  }

  @override
  void update(double dt) {
    super.update(dt);
    if (isMoving) {
      position = position += move;
    }
  }

  @override
  void onTapDown(TapDownEvent event) {
    super.onTapDown(event);
    isMoving = !isMoving;
  }
}

Override the follow method can resolve this bug, but I think that is not the origin design.
  @override
  bool containsLocalPoint(Vector2 point) {
    return super.containsLocalPoint(absoluteToLocal(point));
  }

The follow method called componentsAtPoint by pass canvasPosition value.
Is the canvasPosition is global position,not the local position?
@internal
  void deliverAtPoint<T extends Component>({
    required Component rootComponent,
    required void Function(T component) eventHandler,
    bool deliverToAll = false,
  }) {
    for (final child in rootComponent
        .componentsAtPoint(canvasPosition, renderingTrace)
        .whereType<T>()) {
      continuePropagation = deliverToAll;
      eventHandler(child);
      if (!continuePropagation) {
        CameraComponent.currentCameras.clear();
        break;
      }
    }
  }

If you turn on the debug mode add(PeopleComponent()..debugMode=true);, you'd see where the component is considered to be for the purposes of tap detection. You'll notice that the position of the component diverges from where the yellow square is rendered.
This is because PositionComponent's render() is executed after the canvas translation, i.e. in the component's local coordinate space. Thus, within the render() method you don't have to take into account the component's movement at all:
void render(Canvas canvas) {
  canvas.drawRect(const Rect.fromLTWH(0, 0, 160, 160), paint);
}

Once you do that, the taps will now work as you expect them to.

thanks for your anwser, I will try.


sample() fails when array contains middleclass classes

The sample(array, numSamples) function seems to be sensitive to datatypes allowed in the array argument, and fails to return any array elements when an array contains middleclass class instances.
Test using Busted:
local class = require 'middleclass'
local moses = require 'moses'

describe('moses sample()', function()

  it('works when array contains Vector classes', function()

    local DenseVector = class('DenseVector')
    function DenseVector:initialize(data)
      self.data = data
    end

    local vector1 = DenseVector:new({1,2,3})
    local vector2 = DenseVector:new({4,5,6})

    local sample = moses.sample({vector1, vector2}, 1)
    assert.equal(1, #sample) -- <== fails because #sample is 0
    assert.is_true(sample[1]:isInstanceOf(DenseVector)) -- <== never runs
  end)

end)

Oh I see. Functions that return different datatypes for n=1 are very unexpected, unchainable, and "not inspired by lodash". Such functions would also require the caller to have an "if n=1" condition. I suggest that such functions are unusable.

Strong point, taken into consideration. See commit d7e9618 which reflect the changes.

Looks better. The function still returns a non-array for n<1, which causes the same problem. What's the purpose of having special handling for n=1? Doesn't having different codepaths for different parameter values lead to inconsistencies?

It is fixed as of now.
Thanks for your feedback.

Sweet 👍

BTW, your last publish to LuaRocks was 225 days ago. You've worked on a lot of goodies since then! You can share more often -- we won't mind! :-)


Corrections and additions to powerfit tutorial

Please check whether all the points raised were added properly. If not let me know.

Nice work!

I notice that their still remain some small errors. I'll send another last fix soon, to properly address those.

From: Alexandre Bonvin<EMAIL_ADDRESS>Sent: Monday, March 07, 2016 3:15 PM
To: haddocking/haddocking.github.io
Cc: Zundert, G.C.P. van (Gydo)
Subject: Re: [haddocking.github.io] Corrections and additions to powerfit tutorial (#40)
Nice work!
—
Reply to this email directly or view it on GitHubhttps://github.com/haddocking/haddocking.github.io/pull/40#issuecomment-193264165.

Do update first - I had a new commit

On 07 Mar 2016, at 16:15, Gydo van Zundert<EMAIL_ADDRESS>wrote:
I notice that their still remain some small errors. I'll send another last fix soon, to properly address those.

From: Alexandre Bonvin<EMAIL_ADDRESS>Sent: Monday, March 07, 2016 3:15 PM
To: haddocking/haddocking.github.io
Cc: Zundert, G.C.P. van (Gydo)
Subject: Re: [haddocking.github.io] Corrections and additions to powerfit tutorial (#40)
Nice work!
—
Reply to this email directly or view it on GitHubhttps://github.com/haddocking/haddocking.github.io/pull/40#issuecomment-193264165.
—
Reply to this email directly or view it on GitHub.

==================================
Alexandre Bonvin
Talingweide 91, 3403 AC IJsseltstein, NL
Tel: +31-30-7525883
Email<EMAIL_ADDRESS>

Will do!

From: Alexandre Bonvin<EMAIL_ADDRESS>Sent: Monday, March 07, 2016 4:35 PM
To: haddocking/haddocking.github.io
Cc: Zundert, G.C.P. van (Gydo)
Subject: Re: [haddocking.github.io] Corrections and additions to powerfit tutorial (#40)
Do update first - I had a new commit

On 07 Mar 2016, at 16:15, Gydo van Zundert<EMAIL_ADDRESS>wrote:
I notice that their still remain some small errors. I'll send another last fix soon, to properly address those.

From: Alexandre Bonvin<EMAIL_ADDRESS>Sent: Monday, March 07, 2016 3:15 PM
To: haddocking/haddocking.github.io
Cc: Zundert, G.C.P. van (Gydo)
Subject: Re: [haddocking.github.io] Corrections and additions to powerfit tutorial (#40)
Nice work!
—
Reply to this email directly or view it on GitHubhttps://github.com/haddocking/haddocking.github.io/pull/40#issuecomment-193264165.
—
Reply to this email directly or view it on GitHub.

==================================
Alexandre Bonvin
Talingweide 91, 3403 AC IJsseltstein, NL
Tel: +31-30-7525883
Email<EMAIL_ADDRESS>—
Reply to this email directly or view it on GitHubhttps://github.com/haddocking/haddocking.github.io/pull/40#issuecomment-193302598.


Outdated seaborn dependency

Hello,
This is a fairly small problem, but I figured it's still best to create an issue for it- in the most recent tutorial (example/1_tutorial_tangram.ipynb), the following function is called:
tg.plot_training_scores(ad_map, bins=50, alpha=.5)
This in turn seems to call seaborn.histplot, a function specific to seaborn>0.11.1, but the environment.yml file in this repository installs seaborn 0.10.1. When following through the tutorial in my own python file, I get the following error:
Traceback (most recent call last):
  File "/dcl02/lieber/ajaffe/SpatialTranscriptomics/LIBD/spython/tangram_testing/example_orig_nick.py", line 55, in <module>
    tg.plot_training_scores(ad_map, bins=50, alpha=.5)
  File "/users/neagles/.conda/envs/tangram/lib/python3.8/site-packages/tangram/plot_utils.py", line 26, in plot_training_scores
    sns.histplot(data=df, y='train_score', bins=10, ax=axs_f[0]);
AttributeError: module 'seaborn' has no attribute 'histplot'

Thus I believe environment.yml should be updated to require seaborn 0.11.1 instead of 0.10.1 (this fixed the issue for me).
Best,
-Nick

Hi Nick,
Thanks for pointing this out! We have updated the environment.yml on master. I'm closing this issue.
Best,
Ziqing


rich document

We don't understand how to use it. so I modified
If you would not like BSD, change it.

I know pip is better.
But, why don't you register PYPI?
I tried some install, but never installed
pip install mezzanine-facebook
pip install mezzanine_facebook

I've not registered because I didn't know that anyone was using it. I'll take care of it this weekend and will comment here once it's on PyPi.


[numpy][doc-fix] sum, copy, tile, argmax, sign, log, degrees

Description
Updated documentation for sum, copy, tile, argmax, sign, log, degrees.
Added scalar as supported input type for sign, log, degrees.
Note: added scalar support for exp for test use. Doc is not added for exp. Please use Haozheng's wrapper and doc for exp.
Checklist
Essentials
Please feel free to remove inapplicable items for your PR.

[x] Changes are complete (i.e. I finished coding on this PR)
[x] Code is well-documented:
For user-facing API changes, API doc string has been updated.
For new C++ functions in header files, their functionalities and arguments are documented.
For new examples, README.md is added to explain the what the example does, the source of the dataset, expected performance on test set and reference to the original paper if applicable
[x] To the my best knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change

Changes

Updated documentation for sum, copy, tile, argmax, sign, log, degrees.
Added scalar as supported input type for sign, log, degrees.

Comments
-Added scalar support for exp for test use. Doc is not added for exp. Please use Haozheng's wrapper and doc for exp.

Docs for unary operators are updated in _op.py, _symbol.py and multiarray.py. Docs for other operators are updated in _numpy_op_doc.py.

@ haojin2

@haojin2 Please review changes. Thank you!

@zoeygxy Please fix sanity issue.


Fixes initvegc, initvegn, and cpart values for CMT21, PFT0

The old values were mis-entered, updated values from Helene.

Don't merge this PR quite yet - I would like to check the entire parameterization with Joy.

Replaced with PR #516


Added note about using Debug-VM with shielded VMs

@rpsqrd - thanks for update, appreciated! Confirmed with https://docs.microsoft.com/en-us/windows-server/security/guarded-fabric-shielded-vm/guarded-fabric-and-shielded-vms


fix: add referrerPolicy to the iframe

Description
This fixes the problem of iframe not connecting to https://secure.walletconnect.org/sdk?projectId=xxxx due to missing referrer
(this issue was not present with 5.1.1 somehow)
Type of change

[x] Bug fix (non-breaking change which fixes an issue)

Checklist

[x] Code in this PR is covered by automated tests (Unit tests, E2E tests)
[x] My changes generate no new warnings
[x] I have reviewed my own code
[x] I have filled out all required sections

@jd1378 is this still happening in latest versions?

default is not same as explicitly setting it
I am still patching this in latest versions, so I don't know if it still happens or not


[FEAT]: ChOA & SOA

Description
I think ChOA also borders on plagiarism, it is very similar to GWO and the size determining position change of μ mentioned in the paper is not mentioned at all in the code provided by the authors and in the improvement paper published by the authors about ChOA.
Moreover, SOA can also be considered as plagiarized, which is almost identical to WOA.
Additional Information
No response

@Wonder9988 ,
I think you can write a comment paper to the journal that accepted the ChOA and SOA, if the author cannot answer your question regarding plagiarism or fake results. The journal will surely retract the paper.
If you're interested in writing such a paper, we could collaborate together. You can send me an email at<EMAIL_ADDRESS>Please make sure to prepare proof and questions regarding the plagiarism.
It takes some effort to clean up the environment properly.


⚠ Young Discoverers has degraded performance

In bfd3850, Young Discoverers (https://youngdiscoverers.org.au) experienced degraded performance:

HTTP code: 200
Response time: 5614 ms

Resolved: Young Discoverers performance has improved in 3e4c491.


Scoop upgrade fails with wrong hash

This is what I get when I try to upgrade win-gpg-agent:
PS C:\Users\Alex> scoop update *
win-gpg-agent: 1.6.0 -> 1.6.1
Updating one outdated app:
Updating 'win-gpg-agent' (1.6.0 -> 1.6.1)
Downloading new version
win-gpg-agent.zip (9.5 MB) [===============================================] 100%
Checking hash of win-gpg-agent.zip ... ERROR Hash check failed!
App:         main/win-gpg-agent
URL:         https://github.com/rupor-github/win-gpg-agent/releases/download/v1.6.1/win-gpg-agent.zip
First bytes: 50 4B 03 04 14 00 08 00
Expected:    fe6301697b442fcfbf55b0a596e524c92ade4f1f65912d1ecce3168a1b8e83ae
Actual:      f3bbffe1a5c0a78c848508468299d62c2e8e5aa9ef7694f4d073815bb9a6c131

Please try again or create a new issue by using the following link and paste your console output:
https:////
PS C:\Users\Alex>

Bumped to 1.6.2 - checked hash in manifest. After scoop picks this up everything should be good. Not really sure what has happened.


Wait until async request completes

I have a form with submit button. On form submit, I want to disable the submit button (with loading status) until the async ajax request (which is submitting form data to server) completes (either succeed or fails). If request succeeds, I want to go to url with id of created resource (on server). I am using react-router v1.x (i.e. dynamic routes). How it can be done with fluxxor?
Following is a dummy example snippet to elaborate above problem:
var FormComponent = React.createClass({
mixins:  [
  History,
    Fluxxor.FluxMixin(React),
    Fluxxor.StoreWatchMixin("resource")
  ],

  getStateFromFlux: function() {
    // How to know whether submitted data request completed or not?
    // Or maybe following is the way?
    var lastSubmitted = this.getFlux().store("resource").getLastSubmitted();
    var lastSubmiitedID = lastSubmitted.id;
    if(lastSubmittedID !== PROGRESS_STATUS && lastSubmiitedID !== undefined) {
      history.replaceState("/resources/" + lastSubmitted.id);
      return;
    }

    return {
      submitting: lastSubmittedID === PROGRESS_STATUS
    };
  },

  onSubmit: function() {
    // omitted
    this.getFlux().actions.resource.add(data);
  },

  render: function() {
    return (
      <form>
        // omitted
        <SubmitButton submitting={this.state.submitting} />
      </form>
    )
  }
})

With traditional approach, I could have passed an async request promise to the component, which after resolving would yield the predictable status, and until it resolves, I could stay on same component displaying submitting status, and transit to created resource's url if request succeeds.
--
Beside -- FYI, I am able to show spinner while an async request for list of a resource completes. But above problem is very different, IMO.
I have also checked #112, and Dealing with Asynchronous Data, which are close but doesn't seem to fit for my problem.
I have actions, stores, constants, etc. all set. Please let me know if you need more on this, I can elaborate and provide more details.

Have you seen the discussion at #132, specifically my initial comment? I still think returning a promise from your action creators or passing in a callback is probably the most straightforward way to go:

Finally, I'm still not convinced the technique I originally used for the React Router example (before changing it) is actually that bad a practice; generally actions should be fire-and-forget, but for very side-effecty things like routing I'm not a smuch of a stickler:

  doThing: function() {
    flux.actions.thing.create(this.state.data, function(id) {
      this.context.router.transitionTo("/things/" + id);
    }.bind(this));
  },

  contextTypes: {
    router: React.PropTypes.object
  },

@BinaryMuse: Thanks, this approach looks neat.


Fixes for Custom Column Names

The unit tests didn't cover everything, so when trying to use this there were some errors with the escaping occurring for the query parameter identifiers too.
I have fixed this with some restructuring of the functions.

+1
Please merge. Unusable without this

@jasongrimes Please merge this. Its been several months now.

Unfortunately I think this project has been abandoned. This project has strange structure and implementation anyway...
Here are three better solutions than this project:

Use some external OAuth system that is relevant.
Some other more generic authentication library (Symfony Security, Sentry etc.)
Roll your own, be sure to use password_hash and good security practices.

Repo is dead. Closing PR


Scrawford dev

Adding base files copied from the iCache version of each module. While I left the ports and signals (with minor changes), the content of the module is empty. The purpose of this pull request is to make the bare files accessible to each of us as we start the project and to provide some experience with PRs.

As you can see, this PR can't be merged until all three of you approve. Currently, I only have two people assigned. If we find that getting approval from three people quickly is too difficult, I can change this to two. I would prefer not to go fewer than that.

I added the rest of the contents of neorve32_dcache.vhd and pulled down the latest updates from the parent repo.


WIP: RotateTool v3

TODO: Figured out a better way to handle mouseDown as I need to store the initialRotation and I am not able to store it only with mouseDrag callback.

Example URL: https://deploy-preview-506--cornerstone-tools.netlify.com/examples/00-test/


bioimageio.core.contrib

this is not yet finished, but already worth a look.
supersedes https://github.com/bioimage-io/core-bioimage-io-python/pull/312

closed in favor of new repo: https://github.com/bioimage-io/workflows-bioimage-io-python


fix mobile horizontal scroll bars when header takes up >100vw

Description
A horizontal scroll bar can appear when the page header is >100vw. This is what is reported in #5355. This PR sets the header to overflow onto the next lines so that the header is visible in its entirety, also removing the scrollbar.

Fixes #5355
Checklist

Is this feature complete?

[X] Yes. Ready to ship.
[ ] No. Follow-up changes expected.

Are you including unit tests for the changes and scenario tests if relevant?

[ ] Yes
[X] No

Did you add public API?

[ ] Yes

If yes, did you have an API Review for it?

[ ] Yes
[ ] No

Did you add <remarks /> and <code /> elements on your triple slash comments?

[ ] Yes
[ ] No

[X] No

Does the change make any security assumptions or guarantees?

[ ] Yes

If yes, have you done a threat model and had a security review?

[ ] Yes
[ ] No

[X] No

Does the change require an update in our Aspire docs?

[ ] Yes

Link to aspire-docs issue:

[X] No

Microsoft Reviewers: Open in CodeFlow

test failure is unrelated

/azp run

Check this works in metrics as well. There can be a long meter or instrument name in the header.

Yup, still works


Outdated download links

Hello,
The download links for the Windows versions of libjni_porcupine.so and libpv_porcupine.so seem to be outdated. The first download link points to a .dll file and the second download link no longer exists at all.

@11Some1 Looks like Porcupine moved the binaries to a new location. Thanks for letting me know. Links have been fixed.


Add group argument to server processes

This change elevates the group argument that was found in ScanServerOpts to ServerOpts, the options used as the base for all Accumulo server processes. The ScanServer used a different format for the lock data in ZooKeeper that comprised the host address and the group name, which allowed clients to find ScanServers that were part of a specific group. By moving the group from ScanServerOpts to ServerOpts it became necessary to embed the group name into the ZooKeeper lock data for all processes. Prior to this commit the ZooKeeper lock data was not using a defined structure, but a String that could be set to anything. I renamed the ServerServices class to ServiceLockData and created a well-defined structure for registering the Thrift Services that were exposed by the Accumulo server process to include the host, port, and group in this structure. Then, I modiified ServiceLock so that it expected and returned  a ServiceLockData object instead of a byte[].
Closes #3178

This will likely make debugging test failures harder - why the change? You can always set the level in your local copy, so the question becomes who is more inconvenienced by wanting to have the level at info vs debug.

The current levels haven't been a problem at all, as far as I'm aware. This PR should probably just keep the same value that's there now so there's no risk of bloating the logs and spamming us or filling disks on CI servers. If there's a compelling reason to change it, we can definitely change it, but it hasn't been a problem to this point and it doesn't seem to be related to this PR (at least, it wasn't clear whether it was related). If Dave found it compelling to lower it to debug for testing this PR, or if we end up needing to do that a lot, that's probably a compelling reason to change it... as long as it's not too spammy. It just wasn't clear to me why it was being done here.

I like the changes to the ServiceLockData abstraction. I think that's a useful change on its own. After that change is done, I think the changes to add the service group are probably relatively minimal, so it's probably okay (meaning, I think I'd be in favor), but I'd like to see what this PR looks like after the ServiceLockData abstraction is done first, without the addition of the group. Would you be willing to do that?

Yes, I would be willing to do that. However, if the ServiceLockData object doesn't support the group, then that will break the client and likely break the build.

I like the changes to the ServiceLockData abstraction. I think that's a useful change on its own. After that change is done, I think the changes to add the service group are probably relatively minimal, so it's probably okay (meaning, I think I'd be in favor), but I'd like to see what this PR looks like after the ServiceLockData abstraction is done first, without the addition of the group. Would you be willing to do that?

Yes, I would be willing to do that. However, if the ServiceLockData object doesn't support the group, then that will break the client and likely break the build.

I am imagining the ScanServer's current -g option would go in the second PR, along with adding support for groups for tserver as well, so nothing is broken. I just think it makes sense to apply the "ServiceLockData abstraction/serialization" change feature first, then the "replace scan server group option with group added to ServiceLockData" feature after that, because they seem like they are discrete changes. I don't think the build needs to break to separate those out.

Considering the information about the configuration, I think I'll work on a PR to get rid of server process arguments, and replace them with properties. Then, once that is merged in, I can update this PR which should just be the ServiceLockData changes.

Created #3192 to remove arguments from the server processes

I general this looks like a good change.  It may help if the internal representations of the lock data were more encapsulated so that the storage type was not visible outside of the LockData.
Looking at how to handle tservers and other processes that have locks when an upgrade occurs, one improvement could be if the lock data included either the data version or maybe the release version.  While added either of those at this point would be out of scope for this PR, designing it so that it is easier to extend could help limit changes in the future.

Full IT build passed

It may help if the internal representations of the lock data were more encapsulated so that the storage type was not visible outside of the LockData

Can you be more specific about what you think should be changed? The storage type is a JSON string. The only serialization / deserialization that happens is inside of ServiceLockData.

What caught my eye was ServiceLockData.parse(new String(data, UTF_8)); and was wondering if passing a byte[] would make it possible to isolate the internals more and then the rest was speculation on potential mods that could be able to use information stored within the lock itself.

Another Full IT build passed. I believe I resolved all issues. I'm going to merge this morning.


api: add missing audit mode enum values for EndpointPolicyEnabled

PR  #11011 added only the generated APIs, but not the changes to
openapi.yaml and embedded_spec.go. Otherwise the respective consts are
removed when regenerating the API. Add them to api/v1/openapi.yaml now.
Fixes: 514a38b11a6e ("Handle audit mode in cilium endpoint list and kubectl get cep")

Coverage increased (+0.03%) to 37.227% when pulling 0e80b726b0156e67d04cbbedfdfa39945b107b94 on pr/tklauser/api-add-audit-mod-values into 4e11ae1bb82d3e3f1cde535405e5e79f9ce1606e on master.

Coverage increased (+0.03%) to 37.227% when pulling 0e80b726b0156e67d04cbbedfdfa39945b107b94 on pr/tklauser/api-add-audit-mod-values into 4e11ae1bb82d3e3f1cde535405e5e79f9ce1606e on master.

test-me-please


Different results with different versions

Hi everybody,
Maybe it's already known, but I obtained different results with different versions of bedtools using intersect :
$ /opt/bedtools/bedtools --version
bedtools v2.21.0
$ /opt/bin/bedtools --version
bedtools 2.15.0
$ /opt/bedtools/bedtools intersect -a file1.bed -b file2.bed | wc -l
29233
$ /opt/bin/bedtools intersect -a file1.bed -b file2.bed | wc -l
29621
Someone could explain me why ? Something changed ? Which one should I believe ?
Thanks,
Fabien

Hi Fabien,
Thank you for reporting this. Sorry for the delay in response; I just returned from the holiday weekend. I would need to see your input files to give an accurate explanation. Can you please e-mail them to me at<EMAIL_ADDRESS>Thanks!
My guess in the meantime is that v2.21 did have a bug in the handling of zero-length records. This has since been fixed, and you could try updating to version v2.23 to see how it compares. That should be the most accurate of the versions, with emphasis on "should".
Please also note that v2.15 is quite old and deprecated at this point. We do strongly recommend upgrading for the many improvements we've made since.
Thanks,
Neil

Well, my files are zero-length records...  so it may be why there are these differences...

Ah, ok, great. So yeah, either send me those or try 2.23 and let me know how that works.
Thanks,
Neil

Hi Fabien,
When I run 2.15, 2.21, and 2.23, I get 29688, 29676, and 29688, respectively. 2.21 is indeed incorrect because of the zero length records.
As for the differing results, I did indeed also see what you're talking about. We get some errors where BOTH input files contain the same two ADJACENT zero length records. For example, both input files have:
chr1    29259403        29259403        2035    +
chr1    29259404        29259404        2035    -
v2.15 gives the intersection:
chr1    29259403        29259403        2035    +
chr1    29259403        29259403        2035    +
chr1    29259404        29259404        2035    -
chr1    29259404        29259404        2035    -
But v2.23 gives:
chr1    29259403        29259403        2035    +
chr1    29259404        29259404        2035    +
chr1    29259404        29259404        2035    -
chr1    29259404        29259404        2035    -
I don't honestly think either of these are correct, to be honest. Let me confirm with Aaron when he returns later this week, and if needed, we'll get out a patch as fast as possible. Sorry about that.

My understanding is that the correct results should have been:
chr1 29259403 29259403 2035 +
chr1 29259403 29259404 2035 +
chr1 29259403 29259404 2035 -
chr1 29259404 29259404 2035 -

No, the correct result should be :
chr1 29259403 29259403 2035 +
chr1 29259404 29259404 2035 -
In this case, the behavior of bedtools is indeed the problem, because it's not precise enought, it has a +/-1 base imprecision so it returns both entry for each entry and so, there are thus twice outputs as what expected....
In a correct bed files, entries should be constructed as follow :
chr1 29259403 29259404 2035 +
chr1 29259404 29259405 2035 -
And thus, my guess is that there is somewhere a -1 for the ending...
What is REALLY strange and I cannot explain is that a strand is changed for another :
if you look carefully entries : 29259403 is on strand + and 29259404 on strand -.
But in the v2.21 output, suddently, you have a 29259404 on strand +.......... (?????!!!!!!!)
I know these bed files are not standard, but they did like this in the lab before I arrived....
I thus created standard bed files and make again the intersect with version 2.21 and obtained :
29.377 and result seems to be good (at least for these 2 entries). Strand weird effect has disappeared too for these entries.
So I think all these problems emerged because of non standard bed files my group used until now...

I found the first behavior to persist in 2 cases :
Entries in both files
chr17   4224149 4224150 7326    +
chr17   4224149 4224150 7326    -
return
chr17   4224149 4224150 7326    +
chr17   4224149 4224150 7326    +
chr17   4224149 4224150 7326    -
chr17   4224149 4224150 7326    -
with bedtools intersect
and entries in both files
chr6    155605769       155605770       26230   +
chr6    155605769       155605770       26230   -
return
chr6    155605769       155605770       26230   +
chr6    155605769       155605770       26230   +
chr6    155605769       155605770       26230   -
chr6    155605769       155605770       26230   -
with bedtools intersect.
Why these 2 entries and not others? I do not know.... It should be due to this bug of zero-length intervals...
So I will have to wait for the informatician to come back from holidays to test new version of bedtools !

Ok, I get it. I did'nt used strandness. As intervals are the same, it's normal each entry has the two corresponding entries in other file. So this is normal. Thanks !


Add Table of Contents, Contributing and License to README

This pull request aims to improve the README by introducing a Table of Contents for easier navigation, a straightforward contribution message inviting users to open issues or submit pull requests, and a clear License section specifying the terms for code usage, modification, and distribution.
Changes proposed in this PR:

Table of Contents: Organize README sections for quick reference.
Contribution Message: Simplify the contribution message to encourage users to open issues or submit pull requests for bug fixes or feature requests.
License Section: Clearly define the project's license for transparent code usage, modification, and distribution.

LGTM merged

should we stick to conventional commits or the standard

Not sure what you mean by conventional vs standard

Conventional Commits:

Follows a format like "type(scope): description", where "type" specifies the nature of change (e.g., feat for feature, fix for bug fix), "scope" indicates the affected component, and "description" briefly describes the change.

Standard:

Follows a format like "Update README.md", just the normal way of writing commit messages.

Got ya.
As long as the individual commits are smaller in length, we don't need to make them super detailed.
A simple sentence to explain what the commit has done is fine.
If the commit is much larger, then it makes sense to follow the more conventional style you had mentioned.


Encryption between Client SPA and Websocket Server

This PR implements Option 2 from #7. The SPA generates an HMAC and AES key which are then injected into the Server and used to encypt/decrypt and validate the messages passed between them.
To make this work simpler the Server has moved to a nodejs backend from rustlang.

Think its safe to say I'm not finishing this one.


[Bug]: Cart events oddities

Please confirm that you have:

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

In which of these areas are you experiencing a problem?
Theme
Expected behavior
Add to cart or updating the cart provides visual / real-time feedback
Actual behavior
Cart doesn't appear to be updated on add/update.
I am running the snapshot for 3.67.1 mentioned here.
Video: https://vimeo.com/1012042809/b5724989c7?share=copy
Verbose output
shopify theme dev -s the-pages-media-webinars --verbose
2024-09-23T14:29:16.528Z: Running command theme dev
2024-09-23T14:29:16.538Z: Ensuring that the user is authenticated with the Theme API with the following scopes:
[]
2024-09-23T14:29:16.539Z: Ensuring that the user is authenticated with the Admin API with the following scopes for the store the-pages-media-webinars.myshopify.com:
[]
2024-09-23T14:29:16.539Z: Getting session store...
2024-09-23T14:29:16.540Z: Validating existing session against the scopes:
[
"openid",
"https://api.shopify.com/auth/shop.admin.graphql",
"https://api.shopify.com/auth/shop.admin.themes",
"https://api.shopify.com/auth/partners.collaborator-relationships.readonly",
"https://api.shopify.com/auth/shop.storefront-renderer.devtools",
"https://api.shopify.com/auth/partners.app.cli.access",
"https://api.shopify.com/auth/destinations.readonly"
]
For applications:
{
"adminApi": {
"scopes": [],
"storeFqdn": "the-pages-media-webinars.myshopify.com"
}
}
2024-09-23T14:29:16.541Z: Sending Identity Introspection request to URL: https://accounts.shopify.com/oauth/introspection
2024-09-23T14:29:16.541Z: Sending POST request to URL https://accounts.shopify.com/oauth/introspection
With request headers:

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

2024-09-23T14:29:16.758Z: Request to https://accounts.shopify.com/oauth/introspection completed in 217 ms
With response headers:

cache-control: no-cache, no-store, private, must-revalidate, max-age=0
content-type: application/json; charset=utf-8
etag: W/"94920e578113ba56b047b3d012170b3f"
server-timing: processing;dur=29, socket_queue;dur=2.041, edge;dur=1.023, util;dur=0.15, cfRequestDuration;dur=65.000057
x-request-id: b393164a-dbb9-44ff-8ac0-f904dfb82a40-1727101756

2024-09-23T14:29:16.762Z: The identity token is valid: true
2024-09-23T14:29:16.762Z:
The validation of the token for application/identity completed with the following results:

It's expired: false
It's invalid in identity: false

2024-09-23T14:29:16.762Z: The current session is valid but needs refresh. Refreshing...
2024-09-23T14:29:16.763Z: Sending POST request to URL https://accounts.shopify.com/oauth/token?grant_type=refresh_token&access_token=atkn_CjQI5PPFtwYQhKzGtwZSJggBEhA6eOD3B9VH-JEg-RbQpDyMGhAi3AzfaN1DarMh5j5Wp_n0EkA4LeIPSwgfPmKsPsaJfaGB6QNl7Cfn17afg_UYYGXw4SJRj-K5_8USbfGLwWQlkjZJHtlu9xnaTAM_toRWMqgF&refresh_token=atkn_CiEI5PPFtwYQ5I3kuAaiARIKECLcDN9o3UNqsyHmPlan-fQSQPpkx3kIrf9HsrK7QRaXQyDxrBMIk1Qx34rc7uow0vSB4qOuhJXQ6mVmPRiZeoRoodDnc6Ju-2PVmm95eLY2vgE&client_id=fbdb2649-e327-4907-8f67-908d24cfd7e3
With request headers:

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

2024-09-23T14:29:17.041Z: Request to https://accounts.shopify.com/oauth/token?grant_type=refresh_token&access_token=atkn_CjQI5PPFtwYQhKzGtwZSJggBEhA6eOD3B9VH-JEg-RbQpDyMGhAi3AzfaN1DarMh5j5Wp_n0EkA4LeIPSwgfPmKsPsaJfaGB6QNl7Cfn17afg_UYYGXw4SJRj-K5_8USbfGLwWQlkjZJHtlu9xnaTAM_toRWMqgF&refresh_token=atkn_CiEI5PPFtwYQ5I3kuAaiARIKECLcDN9o3UNqsyHmPlan-fQSQPpkx3kIrf9HsrK7QRaXQyDxrBMIk1Qx34rc7uow0vSB4qOuhJXQ6mVmPRiZeoRoodDnc6Ju-2PVmm95eLY2vgE&client_id=fbdb2649-e327-4907-8f67-908d24cfd7e3 completed in 278 ms
With response headers:

cache-control: no-cache, no-store, private, must-revalidate, max-age=0
content-type: application/json; charset=utf-8
etag: W/"80c7d59bc86cf58bdb7b8dfa19a9e738"
server-timing: processing;dur=82, socket_queue;dur=1.538, edge;dur=2.022, util;dur=0.2, cfRequestDuration;dur=140.000105
x-request-id: ca3fc2ea-ad9c-4e09-9894-ccaa0ecffca5-1727101756

2024-09-23T14:29:17.043Z: Sending POST request to URL https://accounts.shopify.com/oauth/token?grant_type=urn%3Aietf%3Aparams%3Aoauth%3Agrant-type%3Atoken-exchange&requested_token_type=urn%3Aietf%3Aparams%3Aoauth%3Atoken-type%3Aaccess_token&subject_token_type=urn%3Aietf%3Aparams%3Aoauth%3Atoken-type%3Aaccess_token&client_id=fbdb2649-e327-4907-8f67-908d24cfd7e3&audience=271e16d403dfa18082ffb3d197bd2b5f4479c3fc32736d69296829cbb28d41a6&scope=https%3A%2F%2Fapi.shopify.com%2Fauth%2Fpartners.app.cli.access&subject_token=****
With request headers:

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

2024-09-23T14:29:17.043Z: Sending POST request to URL https://accounts.shopify.com/oauth/token?grant_type=urn%3Aietf%3Aparams%3Aoauth%3Agrant-type%3Atoken-exchange&requested_token_type=urn%3Aietf%3Aparams%3Aoauth%3Atoken-type%3Aaccess_token&subject_token_type=urn%3Aietf%3Aparams%3Aoauth%3Atoken-type%3Aaccess_token&client_id=fbdb2649-e327-4907-8f67-908d24cfd7e3&audience=ee139b3d-5861-4d45-b387-1bc3ada7811c&scope=https%3A%2F%2Fapi.shopify.com%2Fauth%2Fshop.storefront-renderer.devtools&subject_token=****
With request headers:

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

2024-09-23T14:29:17.043Z: Sending POST request to URL https://accounts.shopify.com/oauth/token?grant_type=urn%3Aietf%3Aparams%3Aoauth%3Agrant-type%3Atoken-exchange&requested_token_type=urn%3Aietf%3Aparams%3Aoauth%3Atoken-type%3Aaccess_token&subject_token_type=urn%3Aietf%3Aparams%3Aoauth%3Atoken-type%3Aaccess_token&client_id=fbdb2649-e327-4907-8f67-908d24cfd7e3&audience=32ff8ee5-82b8-4d93-9f8a-c6997cefb7dc&scope=https%3A%2F%2Fapi.shopify.com%2Fauth%2Fdestinations.readonly&subject_token=****
With request headers:

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

2024-09-23T14:29:17.043Z: Sending POST request to URL https://accounts.shopify.com/oauth/token?grant_type=urn%3Aietf%3Aparams%3Aoauth%3Agrant-type%3Atoken-exchange&requested_token_type=urn%3Aietf%3Aparams%3Aoauth%3Atoken-type%3Aaccess_token&subject_token_type=urn%3Aietf%3Aparams%3Aoauth%3Atoken-type%3Aaccess_token&client_id=fbdb2649-e327-4907-8f67-908d24cfd7e3&audience=7ee65a63608843c577db8b23c4d7316ea0a01bd2f7594f8a9c06ea668c1b775c&scope=https%3A%2F%2Fapi.shopify.com%2Fauth%2Fshop.admin.graphql+https%3A%2F%2Fapi.shopify.com%2Fauth%2Fshop.admin.themes+https%3A%2F%2Fapi.shopify.com%2Fauth%2Fpartners.collaborator-relationships.readonly&subject_token=****&destination=https%3A%2F%2Fthe-pages-media-webinars.myshopify.com%2Fadmin
With request headers:

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

2024-09-23T14:29:17.255Z: Request to https://accounts.shopify.com/oauth/token?grant_type=urn%3Aietf%3Aparams%3Aoauth%3Agrant-type%3Atoken-exchange&requested_token_type=urn%3Aietf%3Aparams%3Aoauth%3Atoken-type%3Aaccess_token&subject_token_type=urn%3Aietf%3Aparams%3Aoauth%3Atoken-type%3Aaccess_token&client_id=fbdb2649-e327-4907-8f67-908d24cfd7e3&audience=ee139b3d-5861-4d45-b387-1bc3ada7811c&scope=https%3A%2F%2Fapi.shopify.com%2Fauth%2Fshop.storefront-renderer.devtools&subject_token=**** completed in 212 ms
With response headers:

cache-control: no-cache, no-store, private, must-revalidate, max-age=0
content-type: application/json; charset=utf-8
etag: W/"3cd5f84f3e5402c2a469715f0b0e8cea"
server-timing: processing;dur=40, socket_queue;dur=1.124, edge;dur=1.015, util;dur=0.05, cfRequestDuration;dur=90.999842
x-request-id: f72a26fd-f840-405b-84d4-30f4cf94f245-1727101757

2024-09-23T14:29:17.258Z: Request to https://accounts.shopify.com/oauth/token?grant_type=urn%3Aietf%3Aparams%3Aoauth%3Agrant-type%3Atoken-exchange&requested_token_type=urn%3Aietf%3Aparams%3Aoauth%3Atoken-type%3Aaccess_token&subject_token_type=urn%3Aietf%3Aparams%3Aoauth%3Atoken-type%3Aaccess_token&client_id=fbdb2649-e327-4907-8f67-908d24cfd7e3&audience=7ee65a63608843c577db8b23c4d7316ea0a01bd2f7594f8a9c06ea668c1b775c&scope=https%3A%2F%2Fapi.shopify.com%2Fauth%2Fshop.admin.graphql+https%3A%2F%2Fapi.shopify.com%2Fauth%2Fshop.admin.themes+https%3A%2F%2Fapi.shopify.com%2Fauth%2Fpartners.collaborator-relationships.readonly&subject_token=****&destination=https%3A%2F%2Fthe-pages-media-webinars.myshopify.com%2Fadmin completed in 215 ms
With response headers:

cache-control: no-cache, no-store, private, must-revalidate, max-age=0
content-type: application/json; charset=utf-8
etag: W/"6525a284488a67df0e5710da4e542271"
server-timing: processing;dur=47, socket_queue;dur=1.656, edge;dur=1.014, util;dur=0.0, cfRequestDuration;dur=92.000008
x-request-id: b829ec4f-0b72-40a1-9c5a-d45a0bcd3d88-1727101757

2024-09-23T14:29:17.260Z: Request to https://accounts.shopify.com/oauth/token?grant_type=urn%3Aietf%3Aparams%3Aoauth%3Agrant-type%3Atoken-exchange&requested_token_type=urn%3Aietf%3Aparams%3Aoauth%3Atoken-type%3Aaccess_token&subject_token_type=urn%3Aietf%3Aparams%3Aoauth%3Atoken-type%3Aaccess_token&client_id=fbdb2649-e327-4907-8f67-908d24cfd7e3&audience=271e16d403dfa18082ffb3d197bd2b5f4479c3fc32736d69296829cbb28d41a6&scope=https%3A%2F%2Fapi.shopify.com%2Fauth%2Fpartners.app.cli.access&subject_token=**** completed in 217 ms
With response headers:

cache-control: no-cache, no-store, private, must-revalidate, max-age=0
content-type: application/json; charset=utf-8
etag: W/"b960db7c2d1e1706403a81826b6f55dd"
server-timing: processing;dur=47, socket_queue;dur=1.724, edge;dur=2.027, util;dur=0.15, cfRequestDuration;dur=95.999956
x-request-id: 84fd242a-7795-4f69-8ec2-aa653d802e89-1727101757

2024-09-23T14:29:17.317Z: Request to https://accounts.shopify.com/oauth/token?grant_type=urn%3Aietf%3Aparams%3Aoauth%3Agrant-type%3Atoken-exchange&requested_token_type=urn%3Aietf%3Aparams%3Aoauth%3Atoken-type%3Aaccess_token&subject_token_type=urn%3Aietf%3Aparams%3Aoauth%3Atoken-type%3Aaccess_token&client_id=fbdb2649-e327-4907-8f67-908d24cfd7e3&audience=32ff8ee5-82b8-4d93-9f8a-c6997cefb7dc&scope=https%3A%2F%2Fapi.shopify.com%2Fauth%2Fdestinations.readonly&subject_token=**** completed in 273 ms
With response headers:

cache-control: no-cache, no-store, private, must-revalidate, max-age=0
content-type: application/json; charset=utf-8
etag: W/"20776f2610cc68eebefbf24bbd7c88fe"
server-timing: processing;dur=47, socket_queue;dur=1.355, edge;dur=2.015, util;dur=0.1, cfRequestDuration;dur=151.000023
x-request-id: 3c9cdcbf-21a8-4c8e-869a-f1b301556b57-1727101757

2024-09-23T14:29:17.318Z: Setting session store...
2024-09-23T14:29:17.325Z: Ensuring that the user is authenticated with the Storefront API with the following scopes:
[]
2024-09-23T14:29:17.325Z: Getting session store...
2024-09-23T14:29:17.327Z: Validating existing session against the scopes:
[
"openid",
"https://api.shopify.com/auth/shop.admin.graphql",
"https://api.shopify.com/auth/shop.admin.themes",
"https://api.shopify.com/auth/partners.collaborator-relationships.readonly",
"https://api.shopify.com/auth/shop.storefront-renderer.devtools",
"https://api.shopify.com/auth/partners.app.cli.access",
"https://api.shopify.com/auth/destinations.readonly"
]
For applications:
{
"storefrontRendererApi": {
"scopes": []
}
}
2024-09-23T14:29:17.328Z: Sending Identity Introspection request to URL: https://accounts.shopify.com/oauth/introspection
2024-09-23T14:29:17.328Z: Sending POST request to URL https://accounts.shopify.com/oauth/introspection
With request headers:

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

2024-09-23T14:29:17.521Z: Request to https://accounts.shopify.com/oauth/introspection completed in 193 ms
With response headers:

cache-control: no-cache, no-store, private, must-revalidate, max-age=0
content-type: application/json; charset=utf-8
etag: W/"9964b83d83e36c522310803fdb293258"
server-timing: processing;dur=30, socket_queue;dur=2.205, edge;dur=1.02, util;dur=0.2, cfRequestDuration;dur=77.000141
x-request-id: d9fb1d65-5b3f-4d53-920e-01874f721323-1727101757

2024-09-23T14:29:17.530Z: The identity token is valid: true
2024-09-23T14:29:17.530Z:
The validation of the token for application/identity completed with the following results:

It's expired: false
It's invalid in identity: false

2024-09-23T14:29:17.534Z: Getting development theme...
2024-09-23T14:29:17.861Z: Request to https://the-pages-media-webinars.myshopify.com/admin/api/unstable/themes/137376071842.json?fields=id%2Cname%2Crole%2Cprocessing completed in 325 ms
With response headers:

content-type: application/json; charset=utf-8
server-timing: processing;dur=151, cfRequestDuration;dur=232.999802
x-request-id: 29173db1-0304-421e-b290-f6451c14a037-1727101757

╭─ info ────────────────────────────────────────────────────────────────╮
│                                                                       │
│  You're using the new version of shopify theme dev.                 │
│                                                                       │
│  Run shopify theme dev --legacy to switch back to the previous      │
│  version.                                                             │
│                                                                       │
╰───────────────────────────────────────────────────────────────────────╯
[removed 'reading file at...' logs due to message on character limit ]
╭─ success ─────────────────────────────────────────────────────────────╮
│                                                                       │
│  Preview your theme                                                   │
│    • http://<IP_ADDRESS>:9292 [1]                                        │
│                                                                       │
│  Next steps                                                           │
│    • Customize your theme at the theme editor [2]                     │
│    • Share your theme preview [3] (https://the-pages-media-webinars.  │
│      myshopify.com/?preview_theme_id=137376071842)                    │
│                                                                       │
╰───────────────────────────────────────────────────────────────────────╯
[1] http://<IP_ADDRESS>:9292
[2] https://the-pages-media-webinars.myshopify.com/admin/themes/137376071
842/editor
[3] https://the-pages-media-webinars.myshopify.com/?preview_theme_id=1373
76071842
2024-09-23T14:29:19.138Z:
Running system process:
· Command: npm prefix
· Working directory: /Users/taylorpage/Testing/ShopifyCLICommands
2024-09-23T14:29:19.249Z: Obtaining the dependency manager in directory /Users/taylorpage/Testing/ShopifyCLICommands...
2024-09-23T14:29:19.358Z:
Running system process:
· Command: ruby -v
· Working directory: /Users/taylorpage/Testing/ShopifyCLICommands
2024-09-23T14:29:19.593Z: Request to https://monorail-edge.shopifysvc.com/v1/produce completed in 128 ms
With response headers:

x-request-id: 375a6a33-c8ad-4d67-9d00-4f5eba2c02a7

2024-09-23T14:29:19.593Z: Analytics event sent: {
"command": "theme dev",
"time_start":<PHONE_NUMBER>528,
"time_end":<PHONE_NUMBER>133,
"total_time": 2605,
"success": true,
"cli_version": "3.67.1",
"ruby_version": "3.2.2",
"node_version": "22.4.1",
"is_employee": false,
"uname": "darwin arm64",
"env_ci": false,
"env_plugin_installed_any_custom": false,
"env_plugin_installed_shopify": "["@shopify/cli"]",
"env_shell": "zsh",
"env_device_id": "c28c0222f9a1afaae2a40cda5d8351d493ef5f6c",
"env_cloud": "localhost",
"env_package_manager": "unknown",
"env_is_global": true,
"cmd_app_warning_api_key_deprecation_displayed": false,
"cmd_all_timing_network_ms": 2475,
"cmd_all_timing_prompts_ms": 0,
"cmd_all_launcher": "unknown",
"cmd_all_topic": "theme",
"cmd_all_plugin": "@shopify/theme",
"cmd_all_force": false,
"cmd_all_verbose": true,
"cmd_all_path_override": true,
"cmd_all_path_override_hash": "8b61cadb689dd9a15c5604d6178160df03b65e78",
"cmd_all_timing_active_ms": 129,
"cmd_all_exit": "ok",
"args": "-s the-pages-media-webinars --verbose",
"env_plugin_installed_all": "["@shopify/cli"]",
"metadata": "{"extraPublic":{},"extraSensitive":{}}"
}
2024-09-23T14:29:19.593Z: Completed command theme dev
2024-09-23T14:29:19.646Z: Request to https://the-pages-media-webinars.myshopify.com/admin/api/unstable/themes/137376071842/assets/bulk.json completed in 527 ms
With response headers:

content-type: application/json; charset=utf-8
server-timing: processing;dur=153, cfRequestDuration;dur=415.999889
x-request-id: 389f19ae-3667-412f-8302-7d7625e3f8f3-1727101759

2024-09-23T14:29:19.647Z: File Upload Results:
-locales/es.schema.json: success
2024-09-23T14:29:19.713Z: Request to https://the-pages-media-webinars.myshopify.com/admin/api/unstable/themes/137376071842/assets/bulk.json completed in 597 ms
With response headers:

content-type: application/json; charset=utf-8
server-timing: processing;dur=245, cfRequestDuration;dur=501.999855
x-request-id: 06bb2a70-b889-443a-9bd7-0da67945f722-1727101759

2024-09-23T14:29:19.713Z: File Upload Results:
-locales/fi.json: success
-locales/cs.schema.json: success
2024-09-23T14:29:19.715Z: Request to https://the-pages-media-webinars.myshopify.com/admin/api/unstable/themes/137376071842/assets/bulk.json completed in 601 ms
With response headers:

content-type: application/json; charset=utf-8
server-timing: processing;dur=219, cfRequestDuration;dur=482.999802
x-request-id: 0e22d22d-7a03-4c18-8215-ececd5f7a4b7-1727101759

2024-09-23T14:29:19.715Z: File Upload Results:
-locales/en.default.json: success
-locales/de.schema.json: success
2024-09-23T14:29:19.819Z: Request to https://the-pages-media-webinars.myshopify.com/admin/api/unstable/themes/137376071842/assets/bulk.json completed in 701 ms
With response headers:

content-type: application/json; charset=utf-8
server-timing: processing;dur=291, cfRequestDuration;dur=585.000038
x-request-id: 37d170b8-3b81-4e29-9487-09c44f3de333-1727101759

2024-09-23T14:29:19.820Z: File Upload Results:
-locales/fr.json: success
-locales/da.schema.json: success
2024-09-23T14:29:19.829Z: Request to https://the-pages-media-webinars.myshopify.com/admin/api/unstable/themes/137376071842/assets/bulk.json completed in 709 ms
With response headers:

content-type: application/json; charset=utf-8
server-timing: processing;dur=325, cfRequestDuration;dur=608.000040
x-request-id: d98429e6-56f0-4aa8-a9a7-d706c492ea62-1727101759

2024-09-23T14:29:19.829Z: File Upload Results:
-locales/es.json: success
-locales/hr.json: success
-locales/fi.schema.json: success
2024-09-23T14:29:19.965Z: Request to https://the-pages-media-webinars.myshopify.com/admin/api/unstable/themes/137376071842/assets/bulk.json completed in 853 ms
With response headers:

content-type: application/json; charset=utf-8
server-timing: processing;dur=428, cfRequestDuration;dur=803.999901
x-request-id: de0e0ade-8fa6-48f8-909a-be6b7650d42b-1727101759

2024-09-23T14:29:19.967Z: File Upload Results:
-locales/bg.json: success
-locales/cs.json: success
-locales/da.json: success
-locales/de.json: success
-locales/el.json: success
2024-09-23T14:29:20.717Z: Request to https://the-pages-media-webinars.myshopify.com/admin/api/unstable/themes/137376071842/assets/bulk.json completed in 581 ms
With response headers:

content-type: application/json; charset=utf-8
server-timing: processing;dur=289, cfRequestDuration;dur=539.999962
x-request-id: 126da9fd-87e0-4af2-91a9-5e375674b624-1727101760

2024-09-23T14:29:20.719Z: File Upload Results:
-locales/pl.json: success
-locales/pt-BR.json: success
-locales/nl.schema.json: success
2024-09-23T14:29:20.740Z: Request to https://the-pages-media-webinars.myshopify.com/admin/api/unstable/themes/137376071842/assets/bulk.json completed in 616 ms
With response headers:

content-type: application/json; charset=utf-8
server-timing: processing;dur=329, cfRequestDuration;dur=584.000111
x-request-id: 54b1a51b-1ad7-491b-a7cd-2ae32a0f01ae-1727101760

2024-09-23T14:29:20.741Z: File Upload Results:
-locales/hu.json: success
-locales/id.json: success
-locales/it.json: success
-locales/en.default.schema.json: success
2024-09-23T14:29:20.782Z: Request to https://the-pages-media-webinars.myshopify.com/admin/api/unstable/themes/137376071842/assets/bulk.json completed in 644 ms
With response headers:

content-type: application/json; charset=utf-8
server-timing: processing;dur=285, cfRequestDuration;dur=598.000050
x-request-id: 3de39f83-2dc5-4150-953d-ca6f048d1272-1727101760

2024-09-23T14:29:20.783Z: File Upload Results:
-locales/pl.schema.json: success
-locales/nb.schema.json: success
2024-09-23T14:29:20.911Z: Request to https://the-pages-media-webinars.myshopify.com/admin/api/unstable/themes/137376071842/assets/bulk.json completed in 780 ms
With response headers:

content-type: application/json; charset=utf-8
server-timing: processing;dur=415, cfRequestDuration;dur=743.999958
x-request-id: 28daf107-dd4c-4d53-a982-464e7d679291-1727101760

2024-09-23T14:29:20.912Z: File Upload Results:
-locales/ko.json: success
-locales/lt.json: success
-locales/nb.json: success
-locales/nl.json: success
-locales/it.schema.json: success
2024-09-23T14:29:20.922Z: Request to https://the-pages-media-webinars.myshopify.com/admin/api/unstable/themes/137376071842/assets/bulk.json completed in 794 ms
With response headers:

content-type: application/json; charset=utf-8
server-timing: processing;dur=403, cfRequestDuration;dur=763.000011
x-request-id: 6801a326-6546-422f-b53a-cd50d94388c4-1727101760

2024-09-23T14:29:20.922Z: File Upload Results:
-locales/ja.json: success
-locales/fr.schema.json: success
2024-09-23T14:29:21.430Z: Request to https://the-pages-media-webinars.myshopify.com/admin/api/unstable/themes/137376071842/assets/bulk.json completed in 1296 ms
With response headers:

content-type: application/json; charset=utf-8
server-timing: processing;dur=950, cfRequestDuration;dur=1259.999990
x-request-id: 620955e3-111d-4491-9f81-f32b759f4be8-1727101760

2024-09-23T14:29:21.432Z: File Upload Results:
-locales/ja.schema.json: success
-locales/ko.schema.json: success
2024-09-23T14:29:21.661Z: Request to https://the-pages-media-webinars.myshopify.com/admin/api/unstable/themes/137376071842/assets/bulk.json completed in 506 ms
With response headers:

content-type: application/json; charset=utf-8
server-timing: processing;dur=228, cfRequestDuration;dur=445.999861
x-request-id: a8f949a0-e96b-4492-b9ad-c64d80fa0c60-1727101761

2024-09-23T14:29:21.662Z: File Upload Results:
-locales/tr.schema.json: success
-locales/zh-TW.json: success
2024-09-23T14:29:21.671Z: Request to https://the-pages-media-webinars.myshopify.com/admin/api/unstable/themes/137376071842/assets/bulk.json completed in 527 ms
With response headers:

content-type: application/json; charset=utf-8
server-timing: processing;dur=282, cfRequestDuration;dur=496.999979
x-request-id: f86397e3-f1e3-41a1-a35e-438b9d133c5e-1727101761

2024-09-23T14:29:21.671Z: File Upload Results:
-locales/pt-PT.json: success
-locales/pt-BR.schema.json: success
2024-09-23T14:29:21.751Z: Request to https://the-pages-media-webinars.myshopify.com/admin/api/unstable/themes/137376071842/assets/bulk.json completed in 601 ms
With response headers:

content-type: application/json; charset=utf-8
server-timing: processing;dur=261, cfRequestDuration;dur=561.000109
x-request-id: 54a34e6a-095d-403c-aa3d-a319d8199bce-1727101761

2024-09-23T14:29:21.752Z: File Upload Results:
-locales/th.json: success
-locales/tr.json: success
-locales/sv.schema.json: success
2024-09-23T14:29:21.772Z: Request to https://the-pages-media-webinars.myshopify.com/admin/api/unstable/themes/137376071842/assets/bulk.json completed in 625 ms
With response headers:

content-type: application/json; charset=utf-8
server-timing: processing;dur=372, cfRequestDuration;dur=585.999966
x-request-id: c9732e75-cfa9-43dd-9bd3-757900aa681f-1727101761

2024-09-23T14:29:21.774Z: File Upload Results:
-locales/ro.json: success
-locales/ru.json: success
-locales/sk.json: success
-locales/sl.json: success
-locales/sv.json: success
2024-09-23T14:29:21.909Z: Request to https://the-pages-media-webinars.myshopify.com/admin/api/unstable/themes/137376071842/assets/bulk.json completed in 756 ms
With response headers:

content-type: application/json; charset=utf-8
server-timing: processing;dur=425, cfRequestDuration;dur=705.999851
x-request-id: de9871c2-a573-401e-8e84-90cc4f3e0011-1727101761

2024-09-23T14:29:21.910Z: File Upload Results:
-locales/vi.json: success
-locales/zh-CN.json: success
-locales/pt-PT.schema.json: success
2024-09-23T14:29:22.533Z: Request to https://the-pages-media-webinars.myshopify.com/admin/api/unstable/themes/137376071842/assets/bulk.json completed in 361 ms
With response headers:

content-type: application/json; charset=utf-8
server-timing: processing;dur=230, cfRequestDuration;dur=309.000015
x-request-id: 6d436ae7-d659-4e0c-af17-a9e5251e67a9-1727101762

2024-09-23T14:29:22.534Z: File Upload Results:
-sections/footer-group.json: success
-sections/header-group.json: success
2024-09-23T14:29:22.534Z: Uploading the following files:
-templates/404.json
-templates/article.json
-templates/blog.json
-templates/collection.json
-templates/cart.json
-templates/index.json
-templates/list-collections.json
-templates/page.contact.json
-templates/page.json
-templates/password.json
2024-09-23T14:29:22.534Z: Uploading the following files:
-templates/product.json
-templates/search.json
-templates/customers/account.json
-templates/customers/activate_account.json
-templates/customers/addresses.json
-templates/customers/order.json
-templates/customers/register.json
-templates/customers/login.json
-templates/customers/reset_password.json
2024-09-23T14:29:22.691Z: Request to https://the-pages-media-webinars.myshopify.com/admin/api/unstable/themes/137376071842/assets/bulk.json completed in 524 ms
With response headers:

content-type: application/json; charset=utf-8
server-timing: processing;dur=210, cfRequestDuration;dur=478.999853
x-request-id: 6d9c3317-b12d-4854-9182-6f89224350e8-1727101762

2024-09-23T14:29:22.693Z: File Upload Results:
-locales/zh-TW.schema.json: success
-locales/th.schema.json: success
2024-09-23T14:29:22.770Z: Request to https://the-pages-media-webinars.myshopify.com/admin/api/unstable/themes/137376071842/assets/bulk.json completed in 599 ms
With response headers:

content-type: application/json; charset=utf-8
server-timing: processing;dur=438, cfRequestDuration;dur=543.999910
x-request-id: c7d5362b-20fc-452d-b25c-8fadb888cc11-1727101762

2024-09-23T14:29:22.772Z: File Upload Results:
-assets/custom-styles.css: success
2024-09-23T14:29:22.866Z: Request to https://the-pages-media-webinars.myshopify.com/admin/api/unstable/themes/137376071842/assets/bulk.json completed in 703 ms
With response headers:

content-type: application/json; charset=utf-8
server-timing: processing;dur=257, cfRequestDuration;dur=651.999950
x-request-id: 692f662b-9c69-47a7-96f7-7659fc36fcc1-1727101762

2024-09-23T14:29:22.867Z: File Upload Results:
-locales/zh-CN.schema.json: success
-locales/vi.schema.json: success
2024-09-23T14:29:23.186Z: Request to https://the-pages-media-webinars.myshopify.com/admin/api/unstable/themes/137376071842/assets/bulk.json completed in 651 ms
With response headers:

content-type: application/json; charset=utf-8
server-timing: processing;dur=514, cfRequestDuration;dur=624.000072
x-request-id: e3d8a3bf-3260-4048-9407-55377eb39799-1727101762

2024-09-23T14:29:23.188Z: File Upload Results:
-templates/product.json: success
-templates/search.json: success
-templates/customers/account.json: success
-templates/customers/activate_account.json: success
-templates/customers/addresses.json: success
-templates/customers/order.json: success
-templates/customers/register.json: success
-templates/customers/login.json: success
-templates/customers/reset_password.json: success
2024-09-23T14:29:23.667Z: Request to https://the-pages-media-webinars.myshopify.com/admin/api/unstable/themes/137376071842/assets/bulk.json completed in 1133 ms
With response headers:

content-type: application/json; charset=utf-8
server-timing: processing;dur=1017, cfRequestDuration;dur=1105.000019
x-request-id: dbd33f3c-57fb-4d67-a2e4-15712641d8f7-1727101762

2024-09-23T14:29:23.668Z: File Upload Results:
-templates/404.json: success
-templates/article.json: success
-templates/blog.json: success
-templates/collection.json: success
-templates/cart.json: success
-templates/index.json: success
-templates/list-collections.json: success
-templates/page.contact.json: success
-templates/page.json: success
-templates/password.json: success
2024-09-23T14:29:23.670Z: Files to be deleted:
GET /
2024-09-23T14:29:27.001Z: → Rendering https://the-pages-media-webinars.myshopify.com/?_fd=0&pb=0 (with )...
2024-09-23T14:29:27.357Z: Request to https://the-pages-media-webinars.myshopify.com/?_fd=0&pb=0 completed in 355 ms
With response headers:

cache-control: no-cache, no-store
content-type: text/html; charset=utf-8
server-timing: processing;dur=169;desc="gc:32", db;dur=41, edge_cart;dur=1.44;desc="trips=1", parse;dur=8, render;dur=41, asn;desc="27364", edge;desc="PIT", country;desc="US", theme;desc="137376071842", pageType;desc="index", servedBy;desc="bhss", requestID;desc="f3f0d857-8599-44e0-b654-ba0a3e001255-1727101767", cfRequestDuration;dur=319.000006
x-request-id: f3f0d857-8599-44e0-b654-ba0a3e001255-1727101767

2024-09-23T14:29:27.358Z: ← 200 (request_id: f3f0d857-8599-44e0-b654-ba0a3e001255-1727101767)
GET /collections/all
2024-09-23T14:29:32.859Z: → Rendering https://the-pages-media-webinars.myshopify.com/collections/all?_fd=0&pb=0 (with )...
2024-09-23T14:29:33.361Z: Request to https://the-pages-media-webinars.myshopify.com/collections/all?_fd=0&pb=0 completed in 501 ms
With response headers:

cache-control: no-cache, no-store
content-type: text/html; charset=utf-8
server-timing: processing;dur=193;desc="gc:21", db;dur=52, edge_cart;dur=1.17;desc="trips=1", fetch;dur=22, parse;dur=6, render;dur=67, asn;desc="27364", edge;desc="PIT", country;desc="US", theme;desc="137376071842", pageType;desc="collection", servedBy;desc="jh8g", requestID;desc="ec1f6071-f5b3-4e3c-a76a-25e37ffdf198-1727101773", cfRequestDuration;dur=288.000107
x-request-id: ec1f6071-f5b3-4e3c-a76a-25e37ffdf198-1727101773

2024-09-23T14:29:33.361Z: ← 200 (request_id: ec1f6071-f5b3-4e3c-a76a-25e37ffdf198-1727101773)
GET /products/zipped-jacket
2024-09-23T14:29:38.321Z: → Rendering https://the-pages-media-webinars.myshopify.com/products/zipped-jacket?_fd=0&pb=0 (with )...
2024-09-23T14:29:38.613Z: Request to https://the-pages-media-webinars.myshopify.com/products/zipped-jacket?_fd=0&pb=0 completed in 291 ms
With response headers:

cache-control: no-cache, no-store
content-type: text/html; charset=utf-8
server-timing: processing;dur=162;desc="gc:49", db;dur=32, edge_cart;dur=1.36;desc="trips=1", parse;dur=10, render;dur=50, asn;desc="27364", edge;desc="PIT", country;desc="US", theme;desc="137376071842", pageType;desc="product", servedBy;desc="tmzr", requestID;desc="8a9a5643-d55e-4cd4-8c44-c6e4febf2d61-1727101778", cfRequestDuration;dur=256.999969
x-request-id: 8a9a5643-d55e-4cd4-8c44-c6e4febf2d61-1727101778

2024-09-23T14:29:38.614Z: ← 200 (request_id: 8a9a5643-d55e-4cd4-8c44-c6e4febf2d61-1727101778)
GET /recommendations/products?limit=4&product_id=7746476572834&section_id=template--17166537490594__related-products
2024-09-23T14:29:38.788Z: → Rendering https://the-pages-media-webinars.myshopify.com/recommendations/products?_fd=0&pb=0&limit=4&product_id=7746476572834&section_id=template--17166537490594__related-products (with )...
2024-09-23T14:29:39.001Z: Request to https://the-pages-media-webinars.myshopify.com/recommendations/products?_fd=0&pb=0&limit=4&product_id=7746476572834&section_id=template--17166537490594__related-products completed in 212 ms
With response headers:

cache-control: no-cache, no-store
content-type: text/html; charset=utf-8
server-timing: processing;dur=94, db;dur=41, edge_cart;dur=2.69;desc="trips=1", parse;dur=1, render;dur=21, asn;desc="27364", edge;desc="PIT", country;desc="US", theme;desc="137376071842", servedBy;desc="k4hs", requestID;desc="3af0991a-bcae-46fc-84f3-c1ea0909ec15-1727101778", cfRequestDuration;dur=179.999828
x-request-id: 3af0991a-bcae-46fc-84f3-c1ea0909ec15-1727101778

2024-09-23T14:29:39.001Z: ← 200 (request_id: 3af0991a-bcae-46fc-84f3-c1ea0909ec15-1727101778)
GET /products/zipped-jacket
2024-09-23T14:30:05.847Z: → Rendering https://the-pages-media-webinars.myshopify.com/products/zipped-jacket?_fd=0&pb=0 (with )...
2024-09-23T14:30:06.158Z: Request to https://the-pages-media-webinars.myshopify.com/products/zipped-jacket?_fd=0&pb=0 completed in 309 ms
With response headers:

cache-control: no-cache, no-store
content-type: text/html; charset=utf-8
server-timing: processing;dur=132;desc="gc:39", db;dur=26, edge_cart;dur=2.8;desc="trips=1", parse;dur=8, render;dur=37, asn;desc="27364", edge;desc="PIT", country;desc="US", theme;desc="137376071842", pageType;desc="product", servedBy;desc="v9fw", requestID;desc="37787887-1c6f-460a-a0d4-f60ee13a3e4b-1727101805", cfRequestDuration;dur=220.999956
x-request-id: 37787887-1c6f-460a-a0d4-f60ee13a3e4b-1727101805

2024-09-23T14:30:06.158Z: ← 200 (request_id: 37787887-1c6f-460a-a0d4-f60ee13a3e4b-1727101805)
GET /recommendations/products?limit=4&product_id=7746476572834&section_id=template--17166537490594__related-products
2024-09-23T14:30:06.356Z: → Rendering https://the-pages-media-webinars.myshopify.com/recommendations/products?_fd=0&pb=0&limit=4&product_id=7746476572834&section_id=template--17166537490594__related-products (with )...
2024-09-23T14:30:06.543Z: Request to https://the-pages-media-webinars.myshopify.com/recommendations/products?_fd=0&pb=0&limit=4&product_id=7746476572834&section_id=template--17166537490594__related-products completed in 186 ms
With response headers:

cache-control: no-cache, no-store
content-type: text/html; charset=utf-8
server-timing: processing;dur=60, db;dur=15, edge_cart;dur=1.56;desc="trips=1", parse;dur=1, render;dur=15, asn;desc="27364", edge;desc="PIT", country;desc="US", theme;desc="137376071842", servedBy;desc="42t6", requestID;desc="e382a8a5-482f-493a-8f1d-b6fe7d077168-1727101806", cfRequestDuration;dur=153.999805
x-request-id: e382a8a5-482f-493a-8f1d-b6fe7d077168-1727101806

2024-09-23T14:30:06.543Z: ← 200 (request_id: e382a8a5-482f-493a-8f1d-b6fe7d077168-1727101806)
GET /cart
2024-09-23T14:30:08.090Z: → Rendering https://the-pages-media-webinars.myshopify.com/cart?_fd=0&pb=0 (with )...
2024-09-23T14:30:08.321Z: Request to https://the-pages-media-webinars.myshopify.com/cart?_fd=0&pb=0 completed in 230 ms
With response headers:

cache-control: no-cache, no-store
content-type: text/html; charset=utf-8
server-timing: processing;dur=111;desc="gc:26", db;dur=13, edge_cart;dur=1.57;desc="trips=1", parse;dur=9, render;dur=44, asn;desc="27364", edge;desc="PIT", country;desc="US", theme;desc="137376071842", pageType;desc="cart", servedBy;desc="l9j9", requestID;desc="fb4e26a5-ee5e-4c6c-b4a0-f6ae1fed5b07-1727101808", cfRequestDuration;dur=200.000048
x-request-id: fb4e26a5-ee5e-4c6c-b4a0-f6ae1fed5b07-1727101808

2024-09-23T14:30:08.322Z: ← 200 (request_id: fb4e26a5-ee5e-4c6c-b4a0-f6ae1fed5b07-1727101808)
GET /cart
2024-09-23T14:30:25.582Z: → Rendering https://the-pages-media-webinars.myshopify.com/cart?_fd=0&pb=0 (with )...
2024-09-23T14:30:25.998Z: Request to https://the-pages-media-webinars.myshopify.com/cart?_fd=0&pb=0 completed in 414 ms
With response headers:

cache-control: no-cache, no-store
content-type: text/html; charset=utf-8
server-timing: processing;dur=161;desc="gc:5", db;dur=16, edge_cart;dur=1.67;desc="trips=1", parse;dur=11, render;dur=63, asn;desc="27364", edge;desc="PIT", country;desc="US", theme;desc="137376071842", pageType;desc="cart", servedBy;desc="nbwk", requestID;desc="994bb7ac-b7c7-4993-ba82-c9a784f498c7-1727101825", cfRequestDuration;dur=267.999887
x-request-id: 994bb7ac-b7c7-4993-ba82-c9a784f498c7-1727101825

2024-09-23T14:30:25.998Z: ← 200 (request_id: 994bb7ac-b7c7-4993-ba82-c9a784f498c7-1727101825)
GET /collections/all
2024-09-23T14:30:42.461Z: → Rendering https://the-pages-media-webinars.myshopify.com/collections/all?_fd=0&pb=0 (with )...
2024-09-23T14:30:42.824Z: Request to https://the-pages-media-webinars.myshopify.com/collections/all?_fd=0&pb=0 completed in 362 ms
With response headers:

cache-control: no-cache, no-store
content-type: text/html; charset=utf-8
server-timing: processing;dur=175;desc="gc:44", db;dur=39, edge_cart;dur=1.36;desc="trips=1", fetch;dur=23, parse;dur=8, render;dur=61, asn;desc="27364", edge;desc="PIT", country;desc="US", theme;desc="137376071842", pageType;desc="collection", servedBy;desc="ql6k", requestID;desc="9dae5881-0cc0-4e6e-91b8-36fd4bce016c-1727101842", cfRequestDuration;dur=270.999908
x-request-id: 9dae5881-0cc0-4e6e-91b8-36fd4bce016c-1727101842

2024-09-23T14:30:42.824Z: ← 200 (request_id: 9dae5881-0cc0-4e6e-91b8-36fd4bce016c-1727101842)
GET /products/yellow-wool-jumper
2024-09-23T14:30:44.437Z: → Rendering https://the-pages-media-webinars.myshopify.com/products/yellow-wool-jumper?_fd=0&pb=0 (with )...
2024-09-23T14:30:44.714Z: Request to https://the-pages-media-webinars.myshopify.com/products/yellow-wool-jumper?_fd=0&pb=0 completed in 277 ms
With response headers:

cache-control: no-cache, no-store
content-type: text/html; charset=utf-8
server-timing: processing;dur=157, db;dur=37, edge_cart;dur=1.6;desc="trips=1", parse;dur=11, render;dur=64, asn;desc="27364", edge;desc="PIT", country;desc="US", theme;desc="137376071842", pageType;desc="product", servedBy;desc="tkdl", requestID;desc="a10b9af0-c3a8-4660-81e4-2236cbbdd80b-1727101844", cfRequestDuration;dur=247.999907
x-request-id: a10b9af0-c3a8-4660-81e4-2236cbbdd80b-1727101844

2024-09-23T14:30:44.715Z: ← 200 (request_id: a10b9af0-c3a8-4660-81e4-2236cbbdd80b-1727101844)
GET /recommendations/products?limit=4&product_id=7746476310690&section_id=template--17166537490594__related-products
2024-09-23T14:30:44.887Z: → Rendering https://the-pages-media-webinars.myshopify.com/recommendations/products?_fd=0&pb=0&limit=4&product_id=7746476310690&section_id=template--17166537490594__related-products (with )...
2024-09-23T14:30:45.106Z: Request to https://the-pages-media-webinars.myshopify.com/recommendations/products?_fd=0&pb=0&limit=4&product_id=7746476310690&section_id=template--17166537490594__related-products completed in 219 ms
With response headers:

cache-control: no-cache, no-store
content-type: text/html; charset=utf-8
server-timing: processing;dur=94, db;dur=51, edge_cart;dur=1.87;desc="trips=1", parse;dur=1, render;dur=22, asn;desc="27364", edge;desc="PIT", country;desc="US", theme;desc="137376071842", servedBy;desc="khpr", requestID;desc="770c94be-bfb2-43dc-bc52-379a30c2cd67-1727101844", cfRequestDuration;dur=184.999943
x-request-id: 770c94be-bfb2-43dc-bc52-379a30c2cd67-1727101844

2024-09-23T14:30:45.107Z: ← 200 (request_id: 770c94be-bfb2-43dc-bc52-379a30c2cd67-1727101844)
Reproduction steps

Run shopify theme dev -s store-name on Dawn
Add product to cart and/or update quantity on cart page

Operating System
Mac OS Sonoma 14.6.1
Shopify CLI version (check your project's package.json if you're not sure)
3.67.1
Shell
zsh
Node version (run node -v if you're not sure)
v22.4.1
What language and version are you using in your application?
No response

@frandiox correct, I was using the snapshot version mentioned in #4494 and still running into this issue. Used clean install of Dawn 15.1.0 to reproduce borked cart interactions.

Just updated the shopify-cli via brew and ran into this issue. Is there a version of the package I can roll back to in the time being via brew?

Also still facing this in 3.67.2.

Just updated to 3.67.3 and still seeing the same sort of behavior/issues. Running --legacy flag fixes everything 😞

Verbose Logs
this is not on Dawn reproduction for sake of time so removed some client info
2024-09-30T15:31:06.412Z:
Running system process:
  · Command: npm prefix
  · Working directory: /Users/taylorpage/Client-Work/xxxx

2024-09-30T15:31:06.519Z: Obtaining the dependency manager in directory /Users/taylorpage/Client-Work/xxxx
2024-09-30T15:31:06.615Z:
Running system process:
  · Command: ruby -v
  · Working directory: /Users/taylorpage/Client-Work/xxxx

GET /products/product-handle?variant=41537853653076
2024-09-30T15:31:06.701Z: → Rendering https://store-handle.myshopify.com/products/product-handle?_fd=0&pb=0&variant=41537853653076 (with )...
2024-09-30T15:31:06.891Z: Request to https://monorail-edge.shopifysvc.com/v1/produce completed in 169 ms
With response headers:
 - x-request-id: 0a3a7e2f-67c1-4298-ac44-592318e86a60

2024-09-30T15:31:06.891Z: Analytics event sent: {
  "command": "theme dev",
  "time_start":<PHONE_NUMBER>686,
  "time_end":<PHONE_NUMBER>408,
  "total_time": 2722,
  "success": true,
  "cli_version": "3.67.3",
  "ruby_version": "3.2.2",
  "node_version": "22.4.1",
  "is_employee": false,
  "uname": "darwin arm64",
  "env_ci": false,
  "env_plugin_installed_any_custom": false,
  "env_plugin_installed_shopify": "[\"@shopify/cli\"]",
  "env_shell": "zsh",
  "env_device_id": "c28c0222f9a1afaae2a40cda5d8351d493ef5f6c",
  "env_cloud": "localhost",
  "env_package_manager": "unknown",
  "env_is_global": true,
  "cmd_app_warning_api_key_deprecation_displayed": false,
  "cmd_all_timing_network_ms": 2606,
  "cmd_all_timing_prompts_ms": 0,
  "cmd_all_launcher": "unknown",
  "cmd_all_topic": "theme",
  "cmd_all_plugin": "@shopify/theme",
  "cmd_all_force": false,
  "cmd_all_verbose": true,
  "cmd_all_path_override": true,
  "cmd_all_path_override_hash": "ed85afbcc8b4ff1fe933dfede1504f9b013ecd43",
  "cmd_all_timing_active_ms": 115,
  "cmd_all_exit": "ok",
  "args": "-s store-handle --verbose",
  "env_plugin_installed_all": "[\"@shopify/cli\"]",
  "metadata": "{\"extraPublic\":{},\"extraSensitive\":{}}"
}
2024-09-30T15:31:06.891Z: Completed command theme dev
2024-09-30T15:31:07.038Z: Request to https://store-handle.myshopify.com/products/product-handle?_fd=0&pb=0&variant=41537853653076 completed in 337 ms
With response headers:
 - cache-control: no-cache, no-store
 - content-type: text/html; charset=utf-8
 - server-timing: processing;dur=246;desc="gc:10", db;dur=51, edge_cart;dur=1.87;desc="trips=1", parse;dur=23, render;dur=102, asn;desc="27364", edge;desc="PIT", country;desc="US", theme;desc="128835453012", pageType;desc="product", servedBy;desc="6kgb", requestID;desc="ae3a4f85-0b5c-4d66-bd6e-2de875cf16ad-1727710266", cfRequestDuration;dur=305.000067
 - x-request-id: ae3a4f85-0b5c-4d66-bd6e-2de875cf16ad-1727710266

2024-09-30T15:31:07.039Z: ← 200 (request_id: ae3a4f85-0b5c-4d66-bd6e-2de875cf16ad-1727710266)
GET /products/product-handle?variant=41537853653076
2024-09-30T15:31:10.195Z: → Rendering https://store-handle.myshopify.com/products/product-handle?_fd=0&pb=0&variant=41537853653076 (with )...
2024-09-30T15:31:10.512Z: Request to https://store-handle.myshopify.com/products/product-handle?_fd=0&pb=0&variant=41537853653076 completed in 316 ms
With response headers:
 - cache-control: no-cache, no-store
 - content-type: text/html; charset=utf-8
 - server-timing: processing;dur=221;desc="gc:35", db;dur=30, edge_cart;dur=1.41;desc="trips=1", parse;dur=15, render;dur=95, asn;desc="27364", edge;desc="PIT", country;desc="US", theme;desc="128835453012", pageType;desc="product", servedBy;desc="gbhf", requestID;desc="6ef6c17b-7096-46b9-b0de-540dca40fb47-1727710270", cfRequestDuration;dur=277.999878
 - x-request-id: 6ef6c17b-7096-46b9-b0de-540dca40fb47-1727710270

2024-09-30T15:31:10.512Z: ← 200 (request_id: 6ef6c17b-7096-46b9-b0de-540dca40fb47-1727710270)

works fine in 3.68.0 🎉

Regarding the checkout page, that's currently not supported in the local development server for the legacy version nor the new version.

@karreiro Note, there is a minor bug introduced where the new CLI doesn't redirect http://<IP_ADDRESS>:9292/checkout/* to https://STORE_URL/checkout/* like the legacy CLI does. In legacy, one can POST to add items to cart then get redirected to checkout without hitting the 401 like the new CLI has. It did make for easier testing when bouncing between testing theme and checkout extensions.


🐛 BUG:workers.api.error.unauthorized

Which Cloudflare product(s) does this pertain to?
Workers for Platforms, Wrangler
What version(s) of the tool(s) are you using?
3.29.0
What version of Node are you using?
18.16.0
What operating system and version are you using?
Windows 11
Describe the Bug
Observed behavior
Please describe.
Unable to deploy the Cloudflare worker, which initially I am able to do it.
Expected behavior
Please describe.
Steps to reproduce
Please provide the following:

A minimal working subset of your worker code
A minimal working subset of your wrangler.toml
Commands used to start your local dev server, including custom env and cli args
Steps to be performed in the browser, curl commands, or a test we can run that reliably fails (at least a percent of the time)

A git repo we can clone and run a test suite on, or which has a README with step-by-step instructions, is even better. In this case, please use the field below to provide a link to the minimal repro.
Please provide a link to a minimal reproduction
No response
Please provide any relevant error logs
X [ERROR] A request to the Cloudflare API (/accounts/78bcd056079cc293ccb55ad04a79bccb/workers/scripts/vimeo-devhono) failed.
workers.api.error.unauthorized [code: 10023]

Hi thanks for the issue report. The unauthorized error suggests that the user you are logged into (with Wrangler, possibly via an API token) does not have access to the vimeo-devhono Worker in that account.
Please can you provide more information about your current logged in user by running wrangler whoami and also checking whether you have CLOUDFLARE_API_TOKEN set in your environment.

Closing due to lack of response.


pam module needs update after sbs changes

Pam module needs to be updated for changes in https://github.com/SURFscz/pam-weblogin/issues/91

I already created a branch for this
Will finish this tomorrow
Branch 'issue-#91'

works (that is: pam-weblogin demo on acc works correctly)


Custom examples not working when file is generated

Describe the bug
I defined custom payload example, but when I generate documentation from html template, the examples are generic ("string", 0, "timestamp").
How to Reproduce
I define my examples in messages like this:
HelpDeskTicketUserRaised:
name: HelpDeskTicketUserRaised
title: Help Desk Ticket User Raised
traits:
- $ref: './headers.yaml#/messageTraits/commonHeaders'
payload:
$ref: "./schemas.yaml#/UserRequestPayload"
example:
UserRequestId: 1
Number: T-2023/241
UserRequestMessage: '20'
ReportedBy:
User:
Id: 2
Email<EMAIL_ADDRESS>ExternalCode:
Expected behavior
Expected behaviour is that this data shows in generated html file instead of the generic examples. If I define the data in schema and for each attribute then it works, but in my case that is unacceptable since I have too much messages. Also I am using VS Code extension which uses the react-component and on the preview in VS Code the examples work fine. But once the html file is generated, only the generic examples show.

Hey there, please provide a full example, or at least a formatted message that can be copy/pasted
please use markdown code formatting

asyncapi: '2.6.0'
info:
  title: Message Queues Documentation
  version: '1.0.0'
  description: This is a documentation for message queues
  license:
    name: Apache 2.0
    url: https://www.apache.org/licenses/LICENSE-2.0
servers:
  test:
    url: test.mykafkacluster.org:8092
    protocol: kafka-secure
    description: Test broker
    security:
      - saslScram: []
defaultContentType: application/json
channels:

  #  Session

  "{operatorId}.*.session.started":
    description: desc
    parameters:
      operatorId:
        $ref: '#/components/parameters/operatorId'
    publish:
      operationId: sessionStarted
      traits:
        - $ref: '#/components/operationTraits/kafka'
      message:
        $ref: '#/components/messages/SessionStarted'
      tags:
        - name:  Session

components:
  messages:
    SessionStarted:
      name: SessionStarted
      title: Session Started
      contentType: application/json
      traits:
        - $ref: '#/components/messageTraits/commonHeaders'
      payload:
        $ref: "#/components/schemas/SessionPayload"
        example:
          SessionId: 660427
          SessionNumber: "S-2023/2673"
          SessionSourceId: 1
          ParkingFrom: null
          ParkingTo: null
          ConnectedFrom: "2023-10-30T07: 53: 03.557Z"
          ConnectedTo: null
          From: "2023-10-30T07: 53: 03.557Z"
          To: null
          MeterStart: 6804.3
          MeterEnd: null
          Consumption: null
          Power: null
          RoamingTypeId: 0
          RoamingSessionId: null
          InstanceRoamingPlatformId: null
          Object:
            Id: 75691
            ObjectFriendlyCode: "1"

  schemas:
    SessionPayload:
      type: object
      properties:
        SessionId:
          type: integer
          format: int64
          description: Unique ID of the  session
        SessionNumber:
          type: string
          description: Friendly ID of the  session
        SessionSourceId:
          type: integer
          format: int16
          description: 1 - Local charge point (CSO); 2 - Roaming CDR.
        ParkingFrom:
          type: string
          format: date-time
          description: Parking start time. Normally empty if charger is not able to detect parking time.
        ParkingTo:
          type: string
          format: date-time
          description: Parking end time. Normally empty if charger is not able to detect parking time.
        ConnectedFrom:
          type: string
          format: date-time
        ConnectedTo:
          type: string
          format: date-time
        From:
          type: string
          format: date-time
        To:
          type: string
          format: date-time
        MeterStart:
          type: string
          format: date-time
        MeterEnd:
          type: string
          format: date-time
        Consumption:
          type: number
          format: float
        Power:
          type: number
          format: float
        RoamingTypeId:
          type: integer
          format: int32
        RoamingSessionId:
          type: string
          description: Roaming session id, collected from roaming partner, used as reference when communicating with partner.
        InstanceRoamingPlatformId:
          type: integer
          format: int32
        Object:
          type: object
          properties:
            Id:
              type: integer
              format: int32
            ObjectFriendlyCode:
              type: string

  securitySchemes:
    saslScram:
      type: scramSha256
      description: Provide your username and password for SASL/SCRAM authentication
  parameters:
    operatorId:
      description: Instance ID. Every tenant has unique ID.
      schema:
        type: integer
        format: int32
  messageTraits:
    commonHeaders:
      headers:
        type: object
        properties:
          my-app-header:
            type: integer
            minimum: 0
            maximum: 100
  operationTraits:
    kafka:
      bindings:
        kafka:
          clientId: my-app-id

This is the sample document (full document is too long). There are no error, the file gets generated, but the examples are generic instead of the examples I listed. I want the generated html file to have the example I listed. When I preview the async file with VS Code Extension the examples are the ones I defined and not generated ones, but once I generate html file the genric examples show up. Also defining example for each attribute is really not an option, because the file is so long and examples are also very long.

@derberg sorry for such a late response but we were in the middle of asyncapi v3 release and then also christmas break
the problem is that you provide example in not a valid asyncapi way
your message should look like:
    SessionStarted:
      name: SessionStarted
      title: Session Started
      contentType: application/json
      traits:
        - $ref: '#/components/messageTraits/commonHeaders'
      payload:
        $ref: "#/components/schemas/SessionPayload"
      examples:
        - payload:
            SessionId: 660427
            SessionNumber: "S-2023/2673"
            SessionSourceId: 1
            ParkingFrom: null
            ParkingTo: null
            ConnectedFrom: "2023-10-30T07: 53: 03.557Z"
            ConnectedTo: null
            From: "2023-10-30T07: 53: 03.557Z"
            To: null
            MeterStart: 6804.3
            MeterEnd: null
            Consumption: null
            Power: null
            RoamingTypeId: 0
            RoamingSessionId: null
            InstanceRoamingPlatformId: null
            Object:
              Id: 75691
              ObjectFriendlyCode: "1"

since message can also have headers, then an example object has a structure that enable you to provide example of header and payload separately + you can have multiple examples -> https://v2.asyncapi.com/docs/reference/specification/v2.6.0#messageExampleObject
here you can see fixed document but still with errors as your example do not match provided AsyncAPI Schema

7 days passed. I think we can assume provided solution will work. Closing. Feel free to drop a comment in case it is not really resolved


Revisions to test data and readme

Consider merging this PR.
Review test and readme changes. #308 proves this is implementable as-is.

Thanks :)!


Changes for esp-idf-sys cmake build

Third batch for #8.
Steps

Refactor mcu detection (decouple it from platformio) (moved to build script)
[x] Git utilities

[x] Clone specific tag or branch

automatic pull if out of date
specify the tag or branch which should be kept up-to-date

[x] Apply patches

Maybe better python utilities

Detect python executable

[x] File utilities

[x] Copy directory/files if contents differ (only files for now)
[x] Remove directory with contents

Either use https://crates.io/crates/remove_dir_all or use built in cmake tool.
Note std::fs::remove_dir_all doesn't really work on windows.

[x] cmake utilities (add them here, commit them to the cmake crate, or both)

[x] cmake file api
[x] cmake toolchain file CMAKE_C_FLAGS/CMAKE_CXX_FLAGS/CMAKE_ASM_FLAGS extraction

currently they are silently overridden because the cmake crate sets these

[x] bindgen

[x] Create bindgen::Builder from cmake metadata

[x] Implement LinkArgsBuilder, CInclArgs, CfgArgs for cmake
[x] Test

Looks OK to me. If you want me to merge it, I'll merge it? cmake utils and "maybe better python" can be another iteration.

Not really sure about this file contents' comparison, but I assume your plan is to use this for small stuff, like sdkconfig's and similar?

Not really sure about this file contents' comparison, but I assume your plan is to use this for small stuff, like sdkconfig's and similar?

Yup.
If I copy the files every time the build script is executed, cmake detects that the file has been modified (even if its content didn't actually change) and reconfigures the project. To get around this I copy the file only if its content is different.
An addition to that would be to copy an entire directory if its content is different (and then only copy the files that are different), but I was too lazy to implement that just yet.

Looks OK to me. If you want me to merge it, I'll merge it? cmake utils and "maybe better python" can be another iteration.

I'd prefer to merge only after I can at least build the esp-idf-sys with this. I'm creating the esp-idf-sys native build script along with modifying embuild so that I can see what I still need to add or move here.

Okay, this should do it for now. I've also updated my PR on the esp-idf-sys repo.
The command-line length is  pretty close to the limit (31190 chars) because
- All cfg values from kconfig amount to about 8409 chars
- the linker args from cmake are about 19414 chars
- and the args purely from rust about 3367.
Now the linker invocation isn't the problem anymore but the rustc invocation from cargo.
We should probably switch to passing the linker args in a file and/or setting only select configuration options from the kconfig file.

Please let me know if you would like to have commit privileges.

I would very much appreciate that. We'd have to coordinate development then somehow, wouldn't we?

you can merge yourself before/after fixing these changes

Nope, github still says "Only those with write access to this repository can merge pull requests.".

Please let me know if you would like to have commit privileges.

I would very much appreciate that. We'd have to coordinate development then somehow, wouldn't we?

Indeed. For small bugfixes, I think no coordination necessary. For refactoring (big API breakages) as well as for introduction of new APIs, we should probably still file PRs, or at least write a short suggestion in the form of a new issue so that we can peer review.

you can merge yourself before/after fixing these changes

Nope, github still says "Only those with write access to this repository can merge pull requests.".

I've send you the invitation now. Once you confirm, you should be able to get write access.

Indeed. For small bugfixes, I think no coordination necessary. For refactoring (big API breakages) as well as for introduction of new APIs, we should probably still file PRs, or at least write a short suggestion in the form of a new issue so that we can peer review.

Agreed.
Ok, I'll squash merge this now, so that I can continue with solving the command-line length problem.


Doesn't work on chrome based browser

https://openuserjs.org/scripts/zackad/Manga_Reader_Offline/issues/Only_work_on_Firefox

fix with 912548375f1691a5689a6ff82e42d91f73b7003d


IE11 and Edge

This seems to cause the page to scroll to the wrong position in IE11 and Edge

Hi @neptunian! Looks like I'm having the same issue. Have you found a solution to that?


Release version 10.0

Let's track the preparation of 10.0 here.
(TBH I wanted to submit issue #1000.)

@aaugustin are you no longer using github milestones on this project? https://github.com/aaugustin/websockets/milestones?state=closed&direction=asc&sort=due_date

Indeed, I stopped using milestones. They didn't really help.

Pre-requisites:

[ ] Merge Sans-I/O howto & reference docs #999
[ ] Update changelog with git history
[ ] Review private TODO

From private TODO:

[x] Add security limits in Sans-I/O HTTP parser — security weakness in new feature = blocking bug
[ ] Randomize delay before reconnecting (see RFC) — new feature isn't spec-compliant = blocking bug
[ ] Change first argument of ClientConnection to a WebSocketURI (which requires making it a public API again...) — must stabilize the Sans-I/O API before making it public
[ ] Make Headers importable from websockets (= add lazy imports for the datastructures module) + review the new API reference for other similar cases

Done in 13eff12.


To demonstrate basic functionality, an integration test should be created

This integration test should demonstrate the basic functions of this module.

A small ViewModel with two properties
A small HTML document with some elements
Two binding activators:

A binding which sets the inner text of an element
A binding which sets the HTML class attribute

Some binding definitions for those elements which use those activators

This should set up the module, activate the bindings, test the state of the page, then make some changes to the VM and year the state of the page afterwards.

Dove at the same time as the text binding


[BUG]: Turso driver not working with latest ORM package and or drizzle kit or maybe libsql.

What version of drizzle-orm are you using?
0.30.10
What version of drizzle-kit are you using?
0.21.0
Describe the Bug
export default {
schema: "./drizzle/schema.ts",
out: "./drizzle/migrations",
driver: "turso", // or "postgresql" or "mysql" - "turso" doesnt work
dbCredentials: {
url: process.env.TURSO_DATABASE_URL,
authToken: process.env.TURSO_AUTH_TOKEN,
},
} satisfies Config;
results in this in terminal:
bunx drizzle-kit generate
drizzle-kit: v0.21.0
drizzle-orm: v0.30.10
No config path provided, using default 'drizzle.config.ts'
Reading config file '/abc/drizzle.config.ts'
_ZodError: [
{
"expected": "'postgresql' | 'mysql' | 'sqlite'",
"received": "undefined",
"code": "invalid_type",
"path": [
"dialect"
],
"message": "Required"
}
]
at get error [as error] (/abc/node_modules/drizzle-kit/bin.cjs:2122:28)
at drizzleConfigFromFile (/abc/node_modules/drizzle-kit/bin.cjs:14853:27)
at async prepareGenerateConfig (/abc/node_modules/drizzle-kit/bin.cjs:14467:31)
at async Command. (/abc/node_modules/drizzle-kit/bin.cjs:114251:18) {
issues: [
{
expected: "'postgresql' | 'mysql' | 'sqlite'",
received: 'undefined',
code: 'invalid_type',
path: [Array],
message: 'Required'
}
],
addIssue: [Function (anonymous)],
addIssues: [Function (anonymous)],
errors: [
{
expected: "'postgresql' | 'mysql' | 'sqlite'",
received: 'undefined',
code: 'invalid_type',
path: [Array],
message: 'Required'
}
]
}
Missing required params
Expected behavior
for it to work
I changed back to old version and it works.
"dependencies": {
"@libsql/client": "^0.5.2",
"@types/imap-simple": "^4.2.9",
"drizzle-orm": "^0.29.4",
"hono": "^4.2.8"
},
"devDependencies": {
"@types/bun": "latest",
"dotenv": "^16.4.5",
"drizzle-kit": "^0.20.14"
}
Environment & setup
No response

Please provide dialect: "sqlite" to your config file
https://orm.drizzle.team/kit-docs/config-reference#dialect


⚠ Turnos 24x7 has degraded performance

In c704f4d, Turnos 24x7 (https://reservas-dev.alternativasinteligentes.com/) experienced degraded performance:

HTTP code: 200
Response time: 1037 ms

Resolved: Turnos 24x7 performance has improved in 395fafc.


Rep templates

could you please fix the conflicts before I can review the PR, thanks

out of date pr


failure to install on  macos 13.2.1 (22D68)

run below
export ASDF_PYTHON_PATCH_URL="https://github.com/python/cpython/commit/8ea6353.patch?full_index=1"
asdf install python 3.9.6
( note: w or w/o export ASDF_PYTHON_PATCH_URL )
macos:
13.2.1 (22D68)
output:
python-build --patch 3.9.6 /Users/$USER/.asdf/installs/python/3.9.6
with patch file from: https://github.com/python/cpython/commit/8ea6353.patch?full_index=1
python-build: use<EMAIL_ADDRESS>from homebrew
python-build: use readline from homebrew
Downloading Python-3.9.6.tar.xz...
-> https://www.python.org/ftp/python/3.9.6/Python-3.9.6.tar.xz
Installing Python-3.9.6...
patching file 'Misc/NEWS.d/next/macOS/2020-06-24-13-51-57.bpo-41100.mcHdc5.rst'
patching file configure
1 out of 1 hunks failed--saving rejects to configure.rej
patching file configure.ac
1 out of 1 hunks failed--saving rejects to configure.ac.rej
BUILD FAILED (OS X 13.2.1 using python-build 2.3.15-1-g4ef81b5c)
expectation:
no error when installation

I am experiencing the same issue. Do you have any updates on this?
run below
export ASDF_PYTHON_PATCH_URL="https://github.com/python/cpython/commit/8ea6353.patch?full_index=1"
asdf install python latest

macOS
13.3.1 (22E261)
CPU
M1
output
python-build --patch 3.11.0 /Users/ewanxiao/.asdf/installs/python/3.11.0
with patch file from: https://github.com/python/cpython/commit/8ea6353.patch?full_index=1
python-build: use<EMAIL_ADDRESS>from homebrew
python-build: use readline from homebrew
Downloading Python-3.11.0.tar.xz...
-> https://www.python.org/ftp/python/3.11.0/Python-3.11.0.tar.xz
Installing Python-3.11.0...
patching file 'Misc/NEWS.d/next/macOS/2020-06-24-13-51-57.bpo-41100.mcHdc5.rst'
patching file configure
1 out of 1 hunks failed--saving rejects to configure.rej
patching file configure.ac
1 out of 1 hunks failed--saving rejects to configure.ac.rej

BUILD FAILED (OS X 13.3.1 using python-build 2.3.6-7-g19359de7)

Inspect or clean up the working tree at /var/folders/rk/skrcvx5x5375k0z9qz5135th0000gn/T/python-build.20230420052203.26201
Results logged to /var/folders/rk/skrcvx5x5375k0z9qz5135th0000gn/T/python-build.20230420052203.26201.log

Last 10 log lines:
/var/folders/rk/skrcvx5x5375k0z9qz5135th0000gn/T/python-build.20230420052203.26201 ~/Developer/IQHive/naas-apidocs/apps/backend-node-express
/var/folders/rk/skrcvx5x5375k0z9qz5135th0000gn/T/python-build.20230420052203.26201/Python-3.11.0 /var/folders/rk/skrcvx5x5375k0z9qz5135th0000gn/T/python-build.20230420052203.26201 ~/Developer/IQHive/naas-apidocs/apps/backend-node-express

@jdxcode could you help update the status of this ticket?


the size question

Hi,I wonder if the training data are the same size?If yes,what's the size?I think if i use the same size when i test,it will work better.

In my view doesnt really matter as the resize will happen on the go. Its more about detection and alignment than actual face recognition.