A Question about Fig.3 in the paper

您好，源码中Parallel Partial Decoder部分的实现，只有最后卷积核的大小是11，其他的都是33，按照我的理解，这和论文图3中两种卷积核的标注似乎是相反的，如果我的理解有错误，恳请纠正

Hi,
You are right. Thanks for pointing out this issue and this issue may be incurring unnecessary misunderstanding. We will update accordingly.
Best,
Ge-Peng Ji


Ensure that MachineDeployment is compatible with OperatingSystemProfile

What this PR does / why we need it:
We need to ensure that the MachineDeployment is compatible with the OperatingSystemProfile it's supposed to consume. Check if OpeartingSystem and CloudProvider specified in the MachineDeployment match with the spec defined in OSP.
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #98
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

* Ensure that MD is compatible with OSP
* Use predicate for filtering out MachineDeployments

Closing this PR in favor of #106 which already covers all of this.


Quick Suggestions can no longer be disabled

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: code-1.69.1-1657615803.el7.x86_64
OS Version: Linux Fedora 32 64bit

Steps to Reproduce:

Create test.js
in settings.json set

    "editor.quickSuggestions": {
        "other": "off"
    }

and Quick Suggestions are still enabled, as they should not be.

Thanks for creating this issue! We figured it's missing some basic information or in some other way doesn't follow our issue reporting guidelines. Please take the time to review these and update the issue.
Happy Coding!

and Quick Suggestions are still enabled, as they should not be.

What exactly are you typing/doing which then triggers the unwanted suggestions?

If I create test.js and in it type console. then it pops up.
Just now I added
    "editor.suggestOnTriggerCharacters": false,
    "editor.wordBasedSuggestions": false

and it seams to have fixed the issue. Can that explain the issue?


KinematicBody2D move_and_slide() does not work properly in Polygon2D's segments mode

Godot version
v3.4.stable.official.206ba70f4
System information
Windows10
Issue description
v3.4.stable.official.206ba70f4
move_and_slide does not work properly in Polygon's segments mode. When I move KinematicBody2D to the edge, it stops at the edge and cannot move away from the edge.
By the way, does move_and_slide return a value of *delta in 3.4?
Steps to reproduce
Move to the edge and try to move away from the edge
Minimal reproduction project
issue_example.zip

By the way, does move_and_slide return a value of *delta in 3.4?

Yes, the automatic delta behavior remains unchanged in 3.x.

Yes, the automatic move_and_slide() delta behavior remains unchanged in 3.x.

But in 3.4, the value returned by move_and_slide is not a *delta value, which is also reflected in the demo

@LoserFox Did you find a solution to this problem? If so, please document it here by commenting :slightly_smiling_face:

I don't think I've really solved the problem, but I think I've found a temporary solution. Just do this: velocity=move_and_slide(velocity,Vector2.ZERO) position+=move_and_slide(velocity)

I have to say that I almost forgot about this problem for the past year, and today I took some tests again to determine the exact problem.
First, this approach is wrong:


Strip symbols from appleseed binaries

From Esteban:
"We do have symbols, by default all symbols are exported on Unix. But for a while we are hiding non-public symbols (HIDE_SYMBOLS CMake options, default to ON). I think we can close this ticket."


Transferring with seamless breaks grid control

pretty self explanatory, if you transfer to a different nexus instance using the seamless plugin you will no longer be able to control any grids using the controller. is it possible to fix this?

I'm assuming that the transfer isn't being handled correctly by the session component, I'll have to look into what the seamless plugin actually does on a transfer, but it feels like it shouldn't be impossible to solve.


cleanup(net): Group PeerSet fields into themes

Motivation
I did this work as a cleanup for some peer set changes, but I don't know if we need them any more.
So I just want to merge the cleanup separately.
Solution

Group peer set fields into themes
Add missing module comments

Review
Anyone can review this optional PR.
Reviewer Checklist

[ ] Existing tests pass

@mergifyio update


Dont exit on successful compilation if watching

This PR stops the process exiting on successful compilation your watching a file or directory.

Coverage remained the same when pulling a9b8dbb869533964f058cb5c9468dfa43c8dd1f8 on xzyfer:fix/dont-exit-if-watching into 845326cc3ef26e671415269e23ddfcc34a9f275c on sass:master.

Thanks! :tada:

ahhh, awesome! :)


client page alignment fixed

Notion card
https://www.notion.so/UI-changes-in-client-page-48fb0572542b48f0a71cd2d752b74955
Summary
Client page font and alignment fixed
Preview

Type of change
Please delete options that are not relevant.

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Refactor (non-breaking and retains the same functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to
not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
Checking the font size and client of all the text by inspecting on the browser.
Checklist:

[x] I have manually tested all workflows
[x] I have performed a self-review of my own code
[x] I have annotated changes in the PR that are relevant to the reviewer
[ ] I have added automated tests for my code

@Ankita012 Ignore the font size comment but fix the alignment of the "Outstanding" section.

@Ankita012 Please update the font size of hours-logged to 20px.
It's already there

@Ankita012 Ignore the font size comment but fix the alignment of the "Outstanding" section.

Fixed


Rename FTPStream, support multiple line replies, add buffered read

New pull request with all changes in one commit. And also @dbrgn 's commit, I'm not sure why.

To get rid of that commit, the following should do:
git remote add upstream https://github.com/mattnenterprise/rust-ftp
git fetch upstream
git rebase upstream/master

You'll probably have to force-push (-f) afterwards to overwrite your current commits.

Thanks for the tip! I was using Eclipse, and did not realize I could force the push. Done!

Sorry, I accidentally commented on the commit instead of the diff.
Regarding the number conversion:

The code uses 3 decimal digits, it is therefore guaranteed to be between 0 and 999. You'd have to be on a 8 bit platform to have a problem representing it with a isize :-) Would you rather have the method return a u32? Or something else?

The thing is that a "malicious" ftp server could crash your client by sending a code too high. Could that be possible? In doubt, I'd probably go with u32.

PS: I don't really have anything to say here, but in general I'd recommend to split up multiple changes (like the rename and the support for multiple line replies) into separate commits in the future, as that simplifies review and debugging :)

Sorry, I accidentally commented on the commit instead of the diff.

No problem :wink:

PS: I don't really have anything to say here, but in general I'd recommend to split up multiple changes

@dbrgn this is what I originally did, see here: https://github.com/mattnenterprise/rust-ftp/pull/15
I squashed all commits into one per @mattnenterprise's request, I suppose it makes the history easier to read once merged.

The thing is that a "malicious" ftp server could crash your client by sending a code too high. Could that be possible? In doubt, I'd probably go with u32.

No that cannot happen, since the code only parses the first three characters of the line:
line[0 .. 3].parse(). This is consistent with RFC 959, which states:

An FTP reply consists of a three digit number (transmitted as three alphanumeric characters) followed by some text.

By definition this will produce an unsigned number, hence the u32; it could also be usize. To support multiple line replies, the function will keep reading lines until it finds a line that begins with that exact same code followed by a space, per the spec:

Thus the format for multi-line replies is that the first line will begin with the exact required reply code, followed immediately by a Hyphen, "-" (also known as Minus), followed by text.  The last line will begin with the same code, followed immediately by Space , optionally some text, and the Telnet end-of-line code.

Note that the function is a bit more liberal, in the sense that it does not verify that the character following the 3-digit code is a hyphen. This is in line with the Robustness Principle defined by TCP, which I think can apply here: "implementations will follow a general principle of robustness:  be conservative in what you do, be liberal in what you accept from others."

I squashed all commits into one per @mattnenterprise's request, I suppose it makes the history easier to read once merged.

Ah, didn't see that. :)

No that cannot happen, since the code only parses the first three characters of the line: line[0 .. 3].parse()

Ah, then I guess it's fine :) A comment noting that might be a good idea though.
I just wondered why isize is used in the first place. The number doesn't have any relation with pointer size. So it might as well be an i16 or an u32.

I am going to go ahead and merge this.
@matt2xu It is easier to have more specific pull requests. Most projects prefer a specific change in each pull request. This could have been done with the changes made here. For example we could split this pull request into the following pull requests: multi-line replies, the usage example, and changing FTPStream to FtpStream. Keep this in mind in the future :smile:  and thanks for the changes!
@dbrgn I don't have any reason for why that is an isize. So after I merge this pull request you can make a pull-request for making changes.

@mattnenterprise thanks for the advice, next time I will do that (separate pull requests) :sunglasses:


No entities available in dev-state in 0.84.2

Home Assistant release with the issue:

0.84.2
Last working Home Assistant release (if known):
0.82.1
Operating environment (Hass.io/Docker/Windows/etc.):

HassIO in docker
Component/platform:

Description of problem:
Seem to have missed something essential. When upgrading from 0.82.1 to 0.84.2, no entities are available in dev-state. Automations seems to work fine thou.
Any breaking changes I have missed, that may cause this maybe?
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):

Traceback (if applicable):

Additional information:

I have the same issue. 84.1 to 84.2 removed all of the entries. All the automations still work.

Same for me, from 83.3 to 84.3, but seems like it was broken after 84.1. Investigating, but so far seems like hass/docker specific issue.

OK, problem is the with the auth information stored in local storage (browser), cleaning local storage will ask for a new login and then it starts working properly.

I finally got mine corrected. It was happening across any device even with private windows.
I removed the API password in the config file and enabled the -trusted_network and
-homeassistant as stated here https://www.home-assistant.io/docs/authentication/providers/ and everything came back online!

No progress. Would want to upgrade to 0.83, but don't know how to do that with HassIO in docker. Does anyone here know how to do that?
Made a post in the forum, but no answer yet:
https://community.home-assistant.io/t/how-to-downgrade-hassio-in-docker/87682

@non-senses the problem was that I had two user-profiles. When I logged in with my other user, everything come back to normal :)


Update email report [IMPORTANT] label

As per https://mulesoft.slack.com/archives/C8XR3MY4T/p1604677823040900, updated email report [IMPORTANT] label specifying under which circumstances it is possible or not to email report using BAT CLI.

Merged per GUS ticket W-12736386


Initial Implementation of FluentListSectionHeader and FluentListSectionFooter

Platforms Impacted

[X] iOS
[ ] visionOS
[ ] macOS

Description of changes
An initial swiftUI view for the section header and footer to be used in combination with FluentList.
This is a work in progress, so adding examples in the test app, implementing tokens, and updating the design to make fluent will be in future iterations.
Binary change
Total increase: 94,264 bytes
Total decrease: 0 bytes

File
Before
After
Delta

Total
30,757,792 bytes
30,852,056 bytes
🛑 94,264 bytes

 Full breakdown

File
Before
After
Delta

FluentListSectionHeader.o
0 bytes
47,520 bytes
⚠ 47,520 bytes

FluentListSectionFooter.o
0 bytes
34,752 bytes
⚠ 34,752 bytes

__.SYMDEF
4,724,544 bytes
4,736,200 bytes
⚠ 11,656 bytes

Verification
(how the change was tested, including both manual and automated tests)

Visual Verification

Before
After

N/A

Pull request checklist
This PR has considered:

[ ] Light and Dark appearances
[ ] iOS supported versions (all major versions greater than or equal current target deployment version)
[ ] VoiceOver and Keyboard Accessibility
[ ] Internationalization and Right to Left layouts
[ ] Different resolutions (1x, 2x, 3x)
[ ] Size classes and window sizes (iPhone vs iPad, notched devices, multitasking, different window sizes, etc)
[ ] iPad Pointer interaction
[ ] SwiftUI consumption (validation or new demo scenarios needed)
[ ] Objective-C exposure (provide it only if needed)

Did you validate a longer footer label wouldn't get cropped on large text mode? That was an accessibility problem not too long ago with the TableViewHeaderFooterView.

Yes I tested, we aren't doing anything in particular different yet also, so we get the out of box accessibility support from it being a swiftUI view.


Split AutoCommandBuffer into primary and secondary

[x] Added an entry to CHANGELOG_VULKANO.md or CHANGELOG_VK_SYS.md if knowledge of this change could be valuable to users
[x] Updated documentation to reflect any user-facing changes - in this repository
[ ] Updated documentation to reflect any user-facing changes - PR to the guide that fixes existing documentation invalidated by this PR.
[x] Ran cargo fmt on the changes

The AutoCommandBuffer is split into PrimaryAutoCommandBuffer and SecondaryAutoCommandBuffer, and the trait CommandBuffer is also split into PrimaryCommandBuffer and SecondaryCommandBuffer. AutoCommandBufferBuilder is still one type, but it has a type parameter for which type it will build.
I've also renamed Kind and changed how it works a little, so that it now holds a CommandBufferInheritance for secondary command buffers. The SecondaryCommandBuffer::inheritance trait method returns this value.
Pros:

It turns out that there are actually no functions in Vulkano that can accept either type of command buffer. Functions can now specifically ask for one type or the other, giving the wrong type is a compile-time error. This removes a runtime check.
Likewise, the trait methods of CommandBuffer only make sense for primary or secondary command buffers, the only one that works for both is inner.
Some methods on AutoCommandBufferBuilder are now only implemented for AutoCommandBufferBuilder<PrimaryAutoCommandBuffer>, so this removes a runtime check.

Cons:

It's now a bit harder to write a function that works for both primary and secondary command buffer builders. You'd have to make it a generic function. Time will tell if this proves to be an obstacle?

I don't really understand why this branch is including a whole lot of commits that have already been merged. But I think it's ok? Git is still a bit magic to me.

@Rua This is not a strong requirement to accept this PR, but I detected false-positive issues with the IntelliJ Idea Rust plugin. This is a minimal example:
use std::sync::Arc;
use vulkano::command_buffer::{AutoCommandBufferBuilder, PrimaryAutoCommandBuffer};
use vulkano::device::{Device, Queue};

fn foo(device: Arc<Device>, queue: Arc<Queue>) -> PrimaryAutoCommandBuffer {
    AutoCommandBufferBuilder::primary(device, queue.family())
        .unwrap()
        .build()
        .unwrap()
}

This code compiles perfectly fine with Rust 1.51, there are no compile-time errors, but Idea plugin(I tried nightly and stable versions both) cannot resolve build method correctly:

Although, this error normally should be addressed to the plugin developers, I think this is an indication of some mess in the Vulkano internal reexports. And since Idea plugin is widely used by the users, I want to ask you to debug your code a little further and try to fix this issue. Even if this is a blame of Idea plugin, it would be good if we align our code such that it would be more ergonomic for Vulkano users.

The build method is implemented in this block
impl<P> AutoCommandBufferBuilder<PrimaryAutoCommandBuffer<P::Alloc>, P>
where
    P: CommandPoolBuilderAlloc,

I'm not really sure what the plugin is getting confused about, because at least in Rust this makes perfect sense. As you say, the compiler figures it out just fine. But Idea appears to not recognise that the builder matches this impl block, somehow. I don't know what to do about that other than poke the developers.

@Rua ok, it probably will be difficult to fix, and after talking to some people I figured out that the Idea plugin is not that widely used these days, so we probably shouldn't relay on it that much. Please resolve merging conflicts, and I will proceed with merging. Thank you!

Done.

@Rua Merged :+1:

Looks like someone already made an issue referencing this too, nice!

Yes, I reported it to developers in a chat, and they opened the issue :) Hope it will be resolved eventually, but I believe IDE plugin shouldn't be a blocker to push our project forward.


Updates specific to Jurnal Agribisnis Indonesia

[ ] Create page
[ ] Green area (or whatever alternative is decided upon)
[ ] Add papers
[ ] Share on socmed

Article is under review


Add CMS Wordpress and Ximdex

Add charts Wordpress and Ximdex

New: https://github.com/helm/charts/pull/94


[FEATURE REQUEST] Adjustable Epicbox Subscription Refresh

Allow changing Subscription Refresh cycle time with a minimum of no less than 15 sec to avoid dDoS attack like behavior and a maximum of no more than 3 minutes or it becomes pointless as transaction times become too long. -r 30, REFRESH=15, etc.

Added here: https://github.com/EpicCash/epic-wallet/pull/56


ignore file extension in regexp

Since the incoming list of file names already went through the *.md or *.txt glob or is a manual selection, we can safely ignore what the extension is. I adjusted the regexp to include everything up to the last . as the title.
201906190735 asdf.test.md will become the groups ['201906190735 asdf.test.md', '201906190735', 'asdf.test']

Thanks for the fix. I made a more general fix in #5, so I'll close this one.


Environment-based evaluation

Environment-based evaluation and refactoring of runtimes.

Environment-based evaluation and refactoring of runtime.


MINOR: [Java] Bump org.apache.hadoop dependencies from 3.3.6 to 3.4.0 in /java

Updates the Hadoop version to 3.4.0 to address vulnerabilities identified in https://deps.dev/maven/org.apache.hadoop%3Ahadoop-common/3.3.6

@github-actions crossbow submit -g java

@github-actions crossbow submit -g java


Opacity does not behave correctly

Describe the bug
Noticed by @VitezslavImrysek 🚀
When a parent has an Opacity applied to it, it is not applied to the "rendered" version of the contained children, which causes unexpected visual behavior.
Steps to reproduce the bug
<Canvas Width="300" Height="300" Opacity="0.5">
    <Rectangle Width="100" Height="100" Fill="Red" />
    <Rectangle Canvas.Left="50" Canvas.Top="50" Width="100" Height="100" Fill="Red" />
</Canvas>

WinUI

WPF

Expected behavior
The WPF behavior is the correct one, as the Rectangles are fully opaque so it does not make sense for them to create any kind of "overlap" area when their parent is semi-transparent.
Screenshots
See above.
Version Info
NuGet package version: 2.6.1
Windows app type:

UWP
Win32

Yes
Yes

Windows 10 version
Saw the problem?

Insider Build (xxxxx)

October 2020 Update (19042)
Yes

May 2020 Update (19041)

November 2019 Update (18363)

May 2019 Update (18362)

October 2018 Update (17763)

April 2018 Update (17134)

Fall Creators Update (16299)

Creators Update (15063)

Device form factor
Saw the problem?

Desktop
Yes

Xbox

Surface Hub

IoT

This is a Composition setting called OpacityMode, there are two options, push-down and Layered.  Pushdown opacity is significantly more efficient as the system simply multiplies numbers together to get the final opacity value for a pixel. Where as the layered opacity, which is what you are asking for, involves rendering all of the visuals on the same layer to a surface and then applying that opacity to that surface, and inserting that subrendered surface into the tree.
UWP xaml made the decision to always use push-down opacity for the performance benefits, there unfortunately isn't a way to change this and is by design.

@gegao18 @codendone and @adadi-MS Could expand on my explanation if I got something wrong.

@MikeHillberg for the Wpf mismatch


to_string optimization

to_string can eliminate some or all memory reallocations by first serializing to a local stack buffer, then copying the result to the output string

Done, and the function is now called serialize()


fixed overlapping

Fixes #425
Description
Fixed the patient portal , doctor section and appointment section. They were overlapping and patient portal section was appearing twice. I also enhanced the CSS for the appointment section to make it go in-line with the rest of the webpage
Related Issues
None
Type of PR

[x] Bug fix
[ ] Feature enhancement
[ ] Documentation update
[ ] Other (specify): _______________

Screenshots / videos (if applicable)
Before

After

Checklist

[x] I have gone through the contributing guide
[x] I have updated my branch and synced it with project main branch before making this PR
[x] I have performed a self-review of my code
[x] I have tested the changes thoroughly before submitting this pull request.
[x] I have provided relevant issue numbers, screenshots, and videos after making the changes.
[x] I have commented my code, particularly in hard-to-understand areas.

Additional context:
GSSoC24

Please review my pull request @Anishkagupta04 @varshith257

@samarsajad Can you create a new issue for fixing the responsiveness to the patient portal?  or maybe you can go with implementing a blood test feature as it is an important one.
cc: @Anjaliavv51 Have a look and create an issue for it.

@samarsajad I think you have deleted the appointment section. Have a look at the PR changes:

                <select name="hospital" id="hospital" class="form-select">
                  <option value="">Select Hospital</option>

                  <option value="Hospital 1">Hospital 1</option>
                  <option value="Hospital 2">Hospital 2</option>
                  <option value="Hospital 3">Hospital 3</option>

The code for patient portal existed twice just below one another. I deleted one of them as they were the same. Please take a look at the screenshot I attached with my pull request@varshith257 @Anishkagupta04

@samarsajad I think you have deleted the appointment section. Have a look at the PR changes:

                <select name="hospital" id="hospital" class="form-select">
                  <option value="">Select Hospital</option>

                  <option value="Hospital 1">Hospital 1</option>
                  <option value="Hospital 2">Hospital 2</option>
                  <option value="Hospital 3">Hospital 3</option>

No it's still there. Please take a look at the screenshot I attached. If you want, I can attach a demo video for the same @varshith257 @Anishkagupta04

The code for patient portal existed twice just below one another. I deleted one of them as they were the same. Please take a look at the screenshot I attached with my pull request@varshith257 @Anishkagupta04

@samarsajad Can you create a new issue for fixing the responsiveness to the patient portal?  or maybe you can go with implementing a blood test feature as it is an important one.
cc: @Anjaliavv51 Have a look and create an issue for it.

I can do both , I guess. The more the merrier.

@samarsajad Can you create a new issue for fixing the responsiveness to the patient portal?  or maybe you can go with implementing a blood test feature as it is an important one.
cc: @Anjaliavv51 Have a look and create an issue for it.

Sure

@samarsajad Resolve conflicts

Resolved the conflicts @varshith257 @Anishkagupta04  Please take a look


[Bug]: Shopify theme dev => request to https://domain.myshopify.com/admin/api/unstable/themes/123456789.json?fields=id failed, reason: socket hang up

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
It should have worked. I did not change anything in my setup. So I upgrade to 3.46.4 but issue remains.
Actual behavior
Shopify theme dev returns error:
request to https://domain.myshopify.com/admin/api/unstable/themes/123456789.json?fields=id failed, reason: socket hang up
Verbose output
shopify theme dev --verbose
2023-06-13T08:09:43.503Z: Running command theme dev
  shopify:theme:dev init version<EMAIL_ADDRESS>argv: [ '--verbose' ] +0ms
2023-06-13T08:09:43.521Z: Ensuring that the user is authenticated with the Theme API with the following scopes:
[]

2023-06-13T08:09:43.522Z: Ensuring that the user is authenticated with the Admin API with the following scopes for the store storec-x57979521.myshopify.com:
[]

2023-06-13T08:09:43.523Z: Getting session store...
2023-06-13T08:09:43.526Z: 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"
]
For applications:
{
  "adminApi": {
    "scopes": [],
    "storeFqdn": "storec-x57979521.myshopify.com"
  }
}

2023-06-13T08:09:43.526Z: Sending Identity Introspection request to URL: https://accounts.shopify.com/oauth/introspection
2023-06-13T08:09:43.527Z: Sending POST request to URL https://accounts.shopify.com/oauth/introspection
With request headers:
 - User-Agent: Shopify CLI; v=3.46.4
 - Keep-Alive: timeout=30
 - Sec-CH-UA-PLATFORM: linux
 - Content-Type: application/json

2023-06-13T08:09:43.789Z: Request to https://accounts.shopify.com/oauth/introspection completed in 253 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/"14b61712349b2da73dbfd0082b642ddc"
 - x-request-id: 45fa1e15-85cc-459a-a599-c325301f337b

2023-06-13T08:09:43.792Z: The identity token is valid: true
2023-06-13T08:09:43.792Z:
The validation of the token for application/identity completed with the following results:
- It's expired: false
- It's invalid in identity: false

2023-06-13T08:09:43.792Z: The current session is valid but needs refresh. Refreshing...
2023-06-13T08:09:43.793Z: Sending POST request to URL https://accounts.shopify.com/oauth/token?grant_type=refresh_token&access_token=atkn_9ca9655ff8ffb12981df11116c7b0992ee647b28dfa80196a2ac06de9ee84f5a&refresh_token=atkn_1969b71b38c92f809a068771b2254ca0f3cfb42c76314fd30ba1b399627a17c9&client_id=fbdb2649-e327-4907-8f67-908d24cfd7e3
With request headers:
 - User-Agent: Shopify CLI; v=3.46.4
 - Keep-Alive: timeout=30
 - Sec-CH-UA-PLATFORM: linux
 - Content-Type: application/json

2023-06-13T08:09:44.131Z: Request to https://accounts.shopify.com/oauth/token?grant_type=refresh_token&access_token=atkn_9ca9655ff8ffb12981df11116c7b0992ee647b28dfa80196a2ac06de9ee84f5a&refresh_token=atkn_1969b71b38c92f809a068771b2254ca0f3cfb42c76314fd30ba1b399627a17c9&client_id=fbdb2649-e327-4907-8f67-908d24cfd7e3 completed in 336 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/"8c2f29b08fafde04391ca1bf89e6f292"
 - x-request-id: c16b21be-fb51-475c-b6d1-56497ef0263f

2023-06-13T08:09:44.132Z: 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=openid+https%3A%2F%2Fapi.shopify.com%2Fauth%2Fpartners.app.cli.access&subject_token=atkn_5ea65fd7fd95498814a9dfe64b64533d3ad0f978b3f0d7aba5d64f28398c98ae
With request headers:
 - User-Agent: Shopify CLI; v=3.46.4
 - Keep-Alive: timeout=30
 - Sec-CH-UA-PLATFORM: linux
 - Content-Type: application/json

2023-06-13T08:09:44.133Z: 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=openid+https%3A%2F%2Fapi.shopify.com%2Fauth%2Fshop.storefront-renderer.devtools&subject_token=atkn_5ea65fd7fd95498814a9dfe64b64533d3ad0f978b3f0d7aba5d64f28398c98ae
With request headers:
 - User-Agent: Shopify CLI; v=3.46.4
 - Keep-Alive: timeout=30
 - Sec-CH-UA-PLATFORM: linux
 - Content-Type: application/json

2023-06-13T08:09:44.381Z: 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=openid+https%3A%2F%2Fapi.shopify.com%2Fauth%2Fpartners.app.cli.access&subject_token=atkn_5ea65fd7fd95498814a9dfe64b64533d3ad0f978b3f0d7aba5d64f28398c98ae completed in 247 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/"e00135e3174cb4cdce67eba6a6d2bc39"
 - x-request-id: ca083cc0-4d3a-4057-b88f-4703f7f7f0fe

2023-06-13T08:09:44.630Z: 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=openid+https%3A%2F%2Fapi.shopify.com%2Fauth%2Fshop.storefront-renderer.devtools&subject_token=atkn_5ea65fd7fd95498814a9dfe64b64533d3ad0f978b3f0d7aba5d64f28398c98ae completed in 495 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/"28655255a75fca83f198c02fd5aaa4e8"
 - x-request-id: 0479e2a9-3c21-4c1a-ac04-1be39e8b1558

2023-06-13T08:09:44.631Z: 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=openid+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=atkn_5ea65fd7fd95498814a9dfe64b64533d3ad0f978b3f0d7aba5d64f28398c98ae&destination=https%3A%2F%2Fstorec-x57979521.myshopify.com%2Fadmin
With request headers:
 - User-Agent: Shopify CLI; v=3.46.4
 - Keep-Alive: timeout=30
 - Sec-CH-UA-PLATFORM: linux
 - Content-Type: application/json

2023-06-13T08:09:44.885Z: 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=openid+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=atkn_5ea65fd7fd95498814a9dfe64b64533d3ad0f978b3f0d7aba5d64f28398c98ae&destination=https%3A%2F%2Fstorec-x57979521.myshopify.com%2Fadmin completed in 253 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/"f60a76c9dcbeb61580ab89244c3e655e"
 - x-request-id: 52156d3b-5cb1-4aef-968a-fb2ab78ab622

2023-06-13T08:09:44.890Z: Setting session store...
2023-06-13T08:09:44.894Z: Ensuring that the user is authenticated with the Storefront API with the following scopes:
[]

2023-06-13T08:09:44.894Z: Getting session store...
2023-06-13T08:09:44.895Z: 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"
]
For applications:
{
  "storefrontRendererApi": {
    "scopes": []
  }
}

2023-06-13T08:09:44.895Z: Sending Identity Introspection request to URL: https://accounts.shopify.com/oauth/introspection
2023-06-13T08:09:44.895Z: Sending POST request to URL https://accounts.shopify.com/oauth/introspection
With request headers:
 - User-Agent: Shopify CLI; v=3.46.4
 - Keep-Alive: timeout=30
 - Sec-CH-UA-PLATFORM: linux
 - Content-Type: application/json

2023-06-13T08:09:45.101Z: Request to https://accounts.shopify.com/oauth/introspection completed in 204 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/"8427a56e54ab85f805c3c686365f7e49"
 - x-request-id: 0a9c9ed8-cbc4-4947-88cf-1f98166e5a52

2023-06-13T08:09:45.102Z: The identity token is valid: true
2023-06-13T08:09:45.102Z:
The validation of the token for application/identity completed with the following results:
- It's expired: false
- It's invalid in identity: false

2023-06-13T08:09:45.102Z: Getting development theme...
2023-06-13T08:10:00.163Z: Request to https://storec-x57979521.myshopify.com/admin/api/unstable/themes/149870412099.json?fields=id completed in 15059 ms
With response headers:

╭─ error ────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│                                                                                │
│  request to https://storec-x57979521.myshopify.com/admin/api/unstable/themes/149870412099.json?fields=id failed, reason: socket hang up        │
│                                                                                │
╰────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯

2023-06-13T08:10:00.247Z: Unable to log analytics event - no information on executed command

Reproduction steps

Shopify theme dev

Operating System
Windows 11
Shopify CLI version (check your project's package.json if you're not sure)
3.46.4
Shell
bash
Node version (run node -v if you're not sure)
v18.16.0
What language and version are you using in your application?
ruby 3.0.2p107 (2021-07-07 revision 0db68f0233) [x86_64-linux-gnu]

Somehow the error is now different, yet I did not do anything:
2023-06-13T08:31:45.531Z: Running command theme dev
  shopify:theme:dev init version<EMAIL_ADDRESS>argv: [ '--verbose' ] +0ms
2023-06-13T08:31:45.548Z: Ensuring that the user is authenticated with the Theme API with the following scopes:
[]

2023-06-13T08:31:45.548Z: Ensuring that the user is authenticated with the Admin API with the following scopes for the store storec-x57979521.myshopify.com:
[]

2023-06-13T08:31:45.549Z: Getting session store...
2023-06-13T08:31:45.552Z: 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"
]
For applications:
{
  "adminApi": {
    "scopes": [],
    "storeFqdn": "storec-x57979521.myshopify.com"
  }
}

2023-06-13T08:31:45.553Z: Sending Identity Introspection request to URL: https://accounts.shopify.com/oauth/introspection
2023-06-13T08:31:45.553Z: Sending POST request to URL https://accounts.shopify.com/oauth/introspection
With request headers:
 - User-Agent: Shopify CLI; v=3.46.4
 - Keep-Alive: timeout=30
 - Sec-CH-UA-PLATFORM: linux
 - Content-Type: application/json

2023-06-13T08:31:45.817Z: Request to https://accounts.shopify.com/oauth/introspection completed in 254 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/"f19b3087beaec2a894dc7008cdd57674"
 - x-request-id: f98a1182-0c8b-460a-bba0-c5f1bbd0b2a6

2023-06-13T08:31:45.820Z: The identity token is valid: true
2023-06-13T08:31:45.820Z:
The validation of the token for application/identity completed with the following results:
- It's expired: false
- It's invalid in identity: false

2023-06-13T08:31:45.820Z: The current session is valid but needs refresh. Refreshing...
2023-06-13T08:31:45.821Z: Sending POST request to URL https://accounts.shopify.com/oauth/token?grant_type=refresh_token&access_token=atkn_1ef1c825ebfae66545632510192924cabece16c01d02da673f91282e2db9bec9&refresh_token=atkn_05438aa6361cbb3c17870850671064f23727a778dc69c3408fd88954349e564b&client_id=fbdb2649-e327-4907-8f67-908d24cfd7e3
With request headers:
 - User-Agent: Shopify CLI; v=3.46.4
 - Keep-Alive: timeout=30
 - Sec-CH-UA-PLATFORM: linux
 - Content-Type: application/json

2023-06-13T08:31:46.150Z: Request to https://accounts.shopify.com/oauth/token?grant_type=refresh_token&access_token=atkn_1ef1c825ebfae66545632510192924cabece16c01d02da673f91282e2db9bec9&refresh_token=atkn_05438aa6361cbb3c17870850671064f23727a778dc69c3408fd88954349e564b&client_id=fbdb2649-e327-4907-8f67-908d24cfd7e3 completed in 328 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/"6ca75563c1703ea06db9bb97ac51f7a0"
 - x-request-id: 59699bb8-5f2f-4345-8963-75c35081c416

2023-06-13T08:31:46.152Z: 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=openid+https%3A%2F%2Fapi.shopify.com%2Fauth%2Fpartners.app.cli.access&subject_token=atkn_f170f802291f53cec50592eb21607b57756d5bf48d2b911a5507a0f38049aac7
With request headers:
 - User-Agent: Shopify CLI; v=3.46.4
 - Keep-Alive: timeout=30
 - Sec-CH-UA-PLATFORM: linux
 - Content-Type: application/json

2023-06-13T08:31:46.152Z: 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=openid+https%3A%2F%2Fapi.shopify.com%2Fauth%2Fshop.storefront-renderer.devtools&subject_token=atkn_f170f802291f53cec50592eb21607b57756d5bf48d2b911a5507a0f38049aac7
With request headers:
 - User-Agent: Shopify CLI; v=3.46.4
 - Keep-Alive: timeout=30
 - Sec-CH-UA-PLATFORM: linux
 - Content-Type: application/json

2023-06-13T08:31:46.390Z: 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=openid+https%3A%2F%2Fapi.shopify.com%2Fauth%2Fpartners.app.cli.access&subject_token=atkn_f170f802291f53cec50592eb21607b57756d5bf48d2b911a5507a0f38049aac7 completed in 236 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/"980dab921c2ca7eb9343054ebf1bfa70"
 - x-request-id: e3d28089-203e-4469-b2ac-986305bc00ba

2023-06-13T08:31:46.658Z: 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=openid+https%3A%2F%2Fapi.shopify.com%2Fauth%2Fshop.storefront-renderer.devtools&subject_token=atkn_f170f802291f53cec50592eb21607b57756d5bf48d2b911a5507a0f38049aac7 completed in 503 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/"0daa145d960e7a9b4c46cfec857081b9"
 - x-request-id: e72c7e7b-6091-4b57-92b3-44c3f11e3ee4

2023-06-13T08:31:46.659Z: 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=openid+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=atkn_f170f802291f53cec50592eb21607b57756d5bf48d2b911a5507a0f38049aac7&destination=https%3A%2F%2Fstorec-x57979521.myshopify.com%2Fadmin
With request headers:
 - User-Agent: Shopify CLI; v=3.46.4
 - Keep-Alive: timeout=30
 - Sec-CH-UA-PLATFORM: linux
 - Content-Type: application/json

2023-06-13T08:31:46.912Z: 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=openid+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=atkn_f170f802291f53cec50592eb21607b57756d5bf48d2b911a5507a0f38049aac7&destination=https%3A%2F%2Fstorec-x57979521.myshopify.com%2Fadmin completed in 252 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/"71e95e44e9e539389d6b487a2c993370"
 - x-request-id: be5131e0-c798-4eba-b483-682febc62293

2023-06-13T08:31:46.914Z: Setting session store...
2023-06-13T08:31:46.932Z: Ensuring that the user is authenticated with the Storefront API with the following scopes:
[]

2023-06-13T08:31:46.932Z: Getting session store...
2023-06-13T08:31:46.932Z: 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"
]
For applications:
{
  "storefrontRendererApi": {
    "scopes": []
  }
}

2023-06-13T08:31:46.933Z: Sending Identity Introspection request to URL: https://accounts.shopify.com/oauth/introspection
2023-06-13T08:31:46.933Z: Sending POST request to URL https://accounts.shopify.com/oauth/introspection
With request headers:
 - User-Agent: Shopify CLI; v=3.46.4
 - Keep-Alive: timeout=30
 - Sec-CH-UA-PLATFORM: linux
 - Content-Type: application/json

2023-06-13T08:31:47.148Z: Request to https://accounts.shopify.com/oauth/introspection completed in 214 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/"0f5315737c2fa55d463dc47b80a52e45"
 - x-request-id: 34e0c3e4-faaa-4304-a38e-961ec9bc09cf

2023-06-13T08:31:47.149Z: The identity token is valid: true
2023-06-13T08:31:47.149Z:
The validation of the token for application/identity completed with the following results:
- It's expired: false
- It's invalid in identity: false

2023-06-13T08:31:47.150Z: Getting development theme...
2023-06-13T08:31:47.491Z: Request to https://storec-x57979521.myshopify.com/admin/api/unstable/themes/149870412099.json?fields=id completed in 339 ms
With response headers:
 - content-type: application/json; charset=utf-8
 - x-request-id: 552d492d-8861-4819-9d58-8d98e95b5bee

╭─ success ──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│                                                                                │
│  Preview your theme                                                                                │
│    • http://<IP_ADDRESS>:9292                                                                                │
│                                                                                │
│  Next steps                                                                                │
│    • Customize your theme at the theme editor                                                                                │
│    • Share your theme preview                                                                                │
│                                                                                │
╰────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯

2023-06-13T08:31:47.611Z:
Running system process:
  · Command: ruby -v
  · Working directory: /home/maxdesign/shopify/stores/Dans ma Gamelle

2023-06-13T08:31:47.623Z:
Running system process:
  · Command: bundle -v
  · Working directory: /home/maxdesign/shopify/stores/Dans ma Gamelle

2023-06-13T08:31:47.742Z: Reading the content of file at /home/maxdesign/.nvm/versions/node/v18.16.0/lib/node_modules/<EMAIL_ADDRESS>2023-06-13T08:31:47.748Z:
Running system process:
  · Command: bundle config set --local path /home/maxdesign/.cache/shopify-gems-nodejs
  · Working directory: /home/maxdesign/.nvm/versions/node/v18.16.0/lib/node_modules/@shopify/theme/node_modules/@shopify/cli-kit/assets/cli-ruby

2023-06-13T08:31:47.877Z:
Running system process:
  · Command: bundle config set --local without development:test
  · Working directory: /home/maxdesign/.nvm/versions/node/v18.16.0/lib/node_modules/@shopify/theme/node_modules/@shopify/cli-kit/assets/cli-ruby

2023-06-13T08:31:48.002Z:
Running system process:
  · Command: bundle install
  · Working directory: /home/maxdesign/.nvm/versions/node/v18.16.0/lib/node_modules/@shopify/theme/node_modules/@shopify/cli-kit/assets/cli-ruby

2023-06-13T08:31:48.244Z:
Running system process:
  · Command: bundle exec ruby /home/maxdesign/.nvm/versions/node/v18.16.0/lib/node_modules/@shopify/theme/node_modules/@shopify/cli-kit/assets/cli-ruby/bin/shopify theme serve /home/maxdesign/shopify/stores/Dans ma Gamelle --live-reload hot-reload --theme<PHONE_NUMBER>99
  · Working directory: /home/maxdesign/shopify/stores/Dans ma Gamelle

Please open this URL in your browser:
https://accounts.shopify.com/oauth/authorize?client_id=fbdb2649-e327-4907-8f67-908d24cfd7e3&scope=openid+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+https%3A%2F%2Fapi.shopify.com%2Fauth%2Fshop.storefront-renderer.devtools+https%3A%2F%2Fapi.shopify.com%2Fauth%2Fpartners.app.cli.access&redirect_uri=http%3A%2F%2F<IP_ADDRESS>%3A3456&state=65af67cc191175b46e841753542870644106572e883252598800450b85c1&response_type=code&code_challenge=n4w5bKV2JRh1jI7644oeMixSvPm3i2FG2VeSoK-ewfA&code_challenge_method=S256
✗ An unexpected error occurred.
        To submit an issue include the stack trace.
        To print the stack trace, add the environment variable SHOPIFY_CLI_STACKTRACE=1.```

Hi, we just shipped a fix, please update to version 3.46.5 and try again.

Hi, we just shipped a fix, please update to version 3.46.5 and try again.


fix bug #1312 Problem with File Names in Downloads

Task/Issue URL:
Tech Design URL:
CC:
Description:
Steps to test this PR:
1.
1.

Internal references:
Software Engineering Expectations
Technical Design Template

Task/Issue: https://github.com/duckduckgo/Android/issues/1312
Tech Design URL:
CC:
Description:  Detail about this bug https://github.com/duckduckgo/Android/issues/1312#issue-941495721
Steps to test this PR:

launch app and open the test url https://ddg-name-test-ubsgiobgibsdgsbklsdjgm.netlify.app/
click file links in the page, it will show download file name as below.


[Trivial] Fix std.outbuffer.[v]printf() for Visual Studio 2015+

MS conforms to the standard beginning with VS 2015, i.e., if the buffer is too small, vsnprintf() returns the number of required characters (excl. terminating null) [MSDN]. VS 2013 and earlier always returned -1 in that case.
So just use the generic (previous POSIX) version, it's compatible with older VS anyway.
Already unittested in line 380 ("hello world 6" vs. "hello world 62665").

Auto-merge toggled on


Factor out printing of fractional values

Avoid Double and "1.0s". Parameterize the routines by the number of fractional places to show. Round properly.

show64With2 :: Int64 -> Text is a related function already in the code. Ideally, it would be a part of a more general solution (here we actually consider Int64 to be divided by 1 million, as used for HP and Calm).

The grep, in particular, any calls to timeDeltaInSeconds and improve the display there.


add macro annotation to generate Prism for sealed trait

@Prisms
sealed trait Foo
case class Bar(i: Int) extends Foo
case class Baz(s: String) extends Foo

Should generate the following code:
object Foo {
  val bar: Prism[Foo, Bar] = GenPrism[Foo, Bar]
  val baz: Prism[Foo, Baz] = GenPrism[Foo, Baz]
}

I started work on this and got far enough to confirm (after discussing with @milessabin) that it's not possible with a macro annotation 😢
The macro relies on knownDirectSubclasses to find Bar and Baz, but because the macro annotation is expanded before the typer runs, the compiler doesn't know about those classes yet.
I'd like to come back to this if/when Miles's proposed fix for SI-7046 is merged.

We could test knownDirectSubclasses fix using https://github.com/typelevel/scala

Nb. it's your downstream users which would need to use Typelevel Scala, ie. it's the code which defines the ADT which needs to be compiled with TLS.

But, yes, please do try that :-)

FWIW, I'm going to recommend on shapeless's README that anyone working with ADTs and Generic should use TLS until my fix (or a better one) is merged. Risk is very low.

You're right, I was just suggesting to test your fix with @cb372 macro implementation as it is not part of monocle yet. If it works, we can add something in the readme to tell users to use typelevel scala for this macro annotation to work.

It works! Using TLS, knownDirectSubclasses now finds the subclasses as expected.
My macro annotation now appears to be generating sensible code but fails with a vague "macro annotation could not be expanded". I need to investigate further, but it's definitely caused by a separate issue. I can tell from my debug logging that knownDirectSubclasses is working fine.

@cb372 please add a :+1: to the PR if you haven't already :-)

@cb372 can I or anyone else help you with the error you got after the macro expanded?

I don't remember the details now, but I'll try to resurrect my branch and put together a StackOverflow question later this week

Awesome, thanks Chris

@julien-truffaut @milessabin http://stackoverflow.com/questions/39916994/please-help-me-debug-my-macro-annotation 🙏

we should give it another try with scala 2.12.1

I just couldn't let this one go 😄
Here's a proof of concept of something I got working by doing crazy things with a whitebox def macro and Dynamic. If this looks useful, I can make a PR.
https://github.com/cb372/prisms/blob/master/src/test/scala/example/Example.scala
/cc @davegurnell

@cb372 that's awesome! Does it need to be a maro annotation or could it be something like the macro Lens syntax from @cvogt https://github.com/julien-truffaut/Monocle/blob/master/macro/shared/src/main/scala/monocle/macros/syntax/GenApplyLensSyntax.scala#L6

@julien-truffaut No, it doesn't need to be an annotation. That implicit conversion is a nice idea, I'll try it.

This probably should be considered on another iteration but it would be great if we could compose .lens and .prism, e.g.
case class Computer(name: String, )
sealed trait OS
case class Linux(version: String) extends OS
case class Windows(version: String, licence: String) extends OS

val c = Computer("foo", Windows("7", "12345"))
c.lens(_.os).prism[Windows].lens(_.licence)

.lens currently only supports a.lens(_.b.c), but I'd be happy to contribute support for a.lens(_.b).lens(_.c).

No macro annotations in Scala 3


Indicator Import requires PascalCase for Category strings.

Attempting to import Indicators with specific categories requires the string to be written on Pascal Case convention and only accepts the category list available at the portal:

If you try "Suspicious Activity" with or without quotes will pop up an error while importing, however, "SuspiciousActivity" with no quotes at the Category column will succeed. If the second word does not have the uppercase in the first character, will fail as well.
The documentation has no reference to this, and the note at the end just confirms the categories are aligned with the MITRE conventions which does not specify the Pascal Case usage for the import. Document: https://learn.microsoft.com/en-us/microsoft-365/security/defender-endpoint/indicator-manage?view=o365-worldwide

@vxSpctr Thank you for your feedback. We have made changes to the document via PR#https://github.com/MicrosoftDocs/microsoft-365-docs/pull/10183
Once the author approves, the changes will be live.
Thanks
Sri

@yogkumgit This can be closed.

@msbemba Thank you very much for the contribution and updating the documentation with PR. @vxSpctr Hope this update is helpful for you. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.


Can't find my .ovpn config file

Hello
This morning i Uninstall the script and then install it again.
Since, I can't find the .ovpn files which are created.
The ssh tells me "Client sam added, certs available at ~/sam.ovpn"
And then I can't find it. Not in / , not in /home , not in /var/www, ....anywhere.
Of course, I ask because I know it should be located in ~ or root or / but nothing is there....
Some help would be appreciated :)
Thanks ;)

The .ovpn files where in ~ but i couldnt see them with Filezilla
So i did "ls ~" and then saw them and moved them to a place i could download them


"Loading remote data" drop-up detaches after second select

Prerequisites

[x] I have searched for similar issues in both open and closed tickets and cannot find a duplicate
[x] The issue still exists against the latest master branch of Select2
[x] This is not a usage question (Those should be directed to the community)
[x] I have attempted to find the simplest possible steos to reproduce the issue
[ ] I have included a failing test as a pull request (Optional)

Steps to reproduce the issue
Here are the Steps taken as well as gif to reproduce the behavior. Reproduced in my local project as well as The Select2 Example Page
GIF/video from Select2 page:

Occurs when a page is shortened or a dropdown is near the end of a page in which the dropdown reverses.

Type in a search
Select an option
Click the dropdown again (Menu appears at its last position)
4.) Reset by: clicking the dropdown again or scrolling

Expected behavior and actual behavior
When I follow those steps, I see...
I was expecting...
1.) The dropdown menu to open with its normal behavior
Environment
Browsers

[x] Google Chrome
[x] Mozilla Firefox
[x] Internet Explorer

Operating System

[ ] Windows
[x] Mac OS X
[ ] Linux
[ ] Mobile

Libraries

jQuery version: "jquery": "^2.2.3",
Select2 version: 4.02

Isolating the problem

[x] This bug happens on the examples page
[x] The bug happens consistently across all tested browsers
[x] This bug happens when using Select2 without other pluigns
[x] I can reproduce this bug in a jsbin

+1

+1

+1

+1

Yep same problem here. Its odd that it re-attaches when you click on it again for the 3rd time.

+1

This is actually a duplicate of https://github.com/select2/select2/issues/3905.


Follow up items from Nutanix provider implementation (#3291)

Follow-up items from #3291

[x] Allow insecure to be configurable https://github.com/aws/eks-anywhere/pull/3291#discussion_r977231477, https://github.com/aws/eks-anywhere/pull/3291#discussion_r982741478
[x] Base64 encode creds when applying https://github.com/aws/eks-anywhere/pull/3291#discussion_r977234524
[ ] Enable Kubernetes audit logs using apiServer extraArgs. Here's a reference https://github.com/aws/eks-anywhere/blob/main/pkg/providers/vsphere/config/template-cp.yaml#L133-L159

The insecure is already configurable but based on whether AdditionalTrustBundle is populated or not. The goal here is to remove insecure entirely and propagate AdditionalTrustBundle to CAPX. However, CAPX does not have that as a parameter so that needs to be addressed on CAPX first.
We are planning on swapping out the format of the credentials entirely and that would take care of base64 encoding too.
Interesting, will look into it and create another PR.

/assign @thunderboltsid

PR to update the credentials format - https://github.com/aws/eks-anywhere/pull/3669

/assign @adiantum

Feature will be included in EKS-A v0.18.4 release.


Qn: benefits of your solutions vs using kinesis firehose

Hello,
I am reviewing your stack https://aws.amazon.com/solutions/implementations/centralized-logging/ and also reviewing another solution using Kinesis Firehose.
Trying to understand the benefits of your solutions vs using kinesis firehose??
Thanks

Thanks for the question! At the time the solution was written, Amazon Kinesis Firehose was not yet available. We are considering use of Amazon Kinesis in a future release.

Please up-vote if you want this feature. Do not submit a new feature request.

Please see here for the updated architecture for release v4.0.0


Update configuration-manager-programming-fundamentals.md

Fixed Windows 2000 Scripting Guide links to point to docs.microsoft.com. Fixes #1473
#MMS2019Docathon
Summarize the change in the pull request title
Fixed Windows 2000 Scripting Guide links to point to docs.microsoft.com. Fixes #1473
Fixes #1473

@AndrewJNet : Thanks for your contribution! The author, @aczechowski, has been notified to review your proposed change.

Thanks @AndrewJNet for the contribution! I'll review after the MMS contest.
#hold-off
(Reviewers, please don't edit, I'll care of it.)

There's already a change for some of this in #1508. Let's wait until that's merged, and then see how bad of a conflict we get here. Sit tight...

Chris' change is merged and more encompassing, so I'm closing this pull request.


compatible with tensorflow lite file format

in the program, we use idx file to do inference, should we transfer to tensorflow lite ? I think that it will make program integrate easier ?

@Knight-X I think Flatbuffers can be used in place of the code generation + idx step, however I we need to evaluate flatbuffers impact on the code footprint. It's probably a good idea to add this as an optional feature


1.3.0

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/Azure/azure-docs-sdk-java, working directory: W:\3zow-s, target branch: master, target branch commit: 01aa6d53b9d0b005360e94645fd3311d06edbfa1, source branch: 1.3.0, source branch commit: .

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


output_dir defaults to Cargo OUT_DIR

Hi, thanks for this project!
I like Prost's default behavior to generate code in the OUT_DIR.
This PR retains the existing behavior of prost-serde (meaning it still respects the user's choice of output in the json config), but if output is missing from the config, then it is obtained from the OUT_DIR env var set by Cargo during build time.
I hope it makes sense to merge it.
Thanks in advance!

Thanks! LGTM


SP can ask for loa1

This issue is imported from pivotal - Originaly created at Feb 16, 2021 by Thijs Kinkhorst
An SP can also ask for loa1 in the authnrequest. This means first factor only.
In this case we do not perform any call out to the SFO endpoint (wasteful/useless and SFO does not support it). The behaviour is therefore the same as for any other unknown RequestedAuthnContext.

Verify this works when the Loa1 is configured in the supported LoA mapping in EB config. And verify this also works when it is not configured (unknown AuthnClassRef) (Michiel Kodde - Mar 24, 2021)


x/telemetry/cmd/gotelemetry: wrap output to 80 columns

% gotelemetry on
Telemetry uploading is now enabled and data will be periodically sent to https://telemetry.go.dev/. Uploaded data is used to help improve the Go toolchain and related tools, and it will be published as part of a public dataset.

For more details, see https://telemetry.go.dev/privacy.
This data is collected in accordance with the Google Privacy Policy (https://policies.google.com/privacy).

To disable telemetry uploading, but keep local data collection, run “gotelemetry local”.
To disable both collection and uploading, run “gotelemetry off“.
%

Those are some very long lines. Here is a better output (also slightly reworded):
% gotelemetry on
Telemetry uploading is now enabled.
Data will be sent periodically to https://telemetry.go.dev/.
Uploaded data is used to help improve the Go toolchain and related tools,
and it will be published as part of a public dataset.

For more details, see https://telemetry.go.dev/privacy.
This data is collected in accordance with the Google Privacy Policy
(https://policies.google.com/privacy).

To disable telemetry uploading, but keep local data collection, run “gotelemetry local”.
To disable both collection and uploading, run “gotelemetry off“.
%

Note that there is no need to do fancy wrapping or tty checks. Just hard-code something that looks reasonable in a reasonably-sized terminal.


glib: Remove type parameter from Object::has_property() and add separate has_property_with_type() and check for subtypes

commit 84cd3fd35f5675f4aa882b47c237a24923122cd1
Author: Sebastian Dröge<EMAIL_ADDRESS>Date:   Wed Nov 6 10:19:15 2024 +0200

    glib: Also check for subtypes in `Object::has_property_with_type()`

commit 41daf6c82b0ed26b2b589ef2caed7b7e42cadc8c
Author: Sebastian Dröge<EMAIL_ADDRESS>Date:   Wed Nov 6 10:17:00 2024 +0200

    glib: Remove type parameter from `Object::has_property()` and add separate `has_property_with_type()`

    Most of the time the property type is not interesting and the `None`
    makes the code harder to understand. Having a separate, more descriptive
    function for also checking the type seems better.

@bilelmoussaoui Any opinions? :)

Can you have a property with two types  with the same name?

No, but that also seems unrelated? :)


how to use objectTracking with MediaPipeUnityPlugin

Plugin Version or Commit ID
v0.14.4
Unity Version
2022.3.34f
Your Host OS
Windows10 home
Target Platform
UnityEditor, Android
Description
i just want to use Object Tracking without Object Detection,but i cannot find this case in unity examples.Could you share the idea of implementation，thank you
Code to Reproduce the issue
No response
Additional Context
No response

In order to perform Object Tracking, Object Detection should be necessary first, so I don't understand what is being asked. Could you please explain in more detail?

of course！Object Detection should be necessary first,but i Implement object Detection with Another technique（Large models in the cloud），now i can get Initial position with Object Detection results（Cloud） per second，but frequency will update very slowly，so i want to update position with local Object Tracking（with unity mediapipe）Until the next data arrives。

I'll close it because the Object Tracking solution is no longer supported officially.


Async block procedures

Currently, ResultProcedure, BlockProcedure and TransformProcedure are only suitable for non-concurrent work. Previously, in Operations, BlockOperation supported concurrent work. This issue is to bring back that functionality, with some additional features.

AsyncResultProcedure
These procedures are initialised with a closure which receives a finishing block, this block in turn receives a ProcedureResult<Output> value. So, they should be used like this in the happy case:
let procedure = AsyncResultProcedure { finishWithResult in
    asyncTask { result, _ in
        finishWithResult(.success(result))
    }
}

and in the failure case:
let procedure = AsyncResultProcedure { finishWithResult in
    asyncTask { _, error in
        finishWithResult(.failure(error))
    }
}

AsyncBlockProcedure
In the case of AsyncBlockProcedure the Output is Void - and ProcedureKit provides a special argument for the successful finishing case:
let procedure = AsyncBlockProcedure { finishWithResult in
    asyncTask {
        finishWithResult(success)
    }
}

but the un-happy failure is the same:
let procedure = AsyncBlockProcedure { finishWithResult in
    asyncTask { error in
        finishWithResult(error.map { .failure($0) } ?? success)
    }
}

AsyncTransformProcedure
In a similar vein, AsyncTransformProcedure, supports asynchronous transforms:
let procedure = AsyncTransformProcedure { input, finishWithResult in
    asyncTask(input) { output, error in
        finishWithResult(error.map { .failure($0) } ?? .success(output))
    }
}

I just tried AsyncBlockProcedure and ran into the same issue with my custom implementation earlier. finishWithResult is marks as non-escaping by default. Hence we'll get the compiler error Closure use of non-escaping paramter 'finishWithResult' may allow it to escape

@leotumwattana - sorry - fixed now!

@danthorpe - No worries at all. Thanks!


Feature/sqlite user

Implemented Sqlite backed UserService.
Closes #10.

Need to handle errors during ApiServer startup. The StartApiServer from cmd/api.go returns error but main.go ignores it.


GH-34949: [C++][Parquet] Enable page index by columns

Rationale for this change
Currently parquet writer only supports enabling page index for all columns. It would be good to enable/disable at the column level as sometimes it may not be useful for some columns but it pays to create them.
What changes are included in this PR?
Similar to WriterProperties::Builder::enable_dictionary/disable_dictionary, this patch adds WriterProperties::Builder::enable_write_page_index/disable_write_page_index and keep it backward compatible to enable/disable for all columns.
Are these changes tested?
Added ParquetPageIndexRoundTripTest::EnablePerColumn to cover the new settings.
Are there any user-facing changes?
Yes, users are now more flexible to enable/disable page index.

Closes: #34949

By the way, can we just disable the column index?
I've a case that I don't want to collect the Column Index, because statistics is not important for me. ( I'm sure I'll read the whole file), however, offset index can be used.

By the way, can we just disable the column index?
I've a case that I don't want to collect the Column Index, because statistics is not important for me. ( I'm sure I'll read the whole file), however, offset index can be used.

I have thought about this. However, it would be complex if we want to control ColumnIndex and OffsetIndex separately for individual columns. What about splitting WriterProperties::Builder::enable_write_page_index/disable_write_page_index into WriterProperties::Builder::enable_write_column_index/disable_write_column_index and WriterProperties::Builder::enable_write_offset_index/disable_write_offset_index`?

Well, I think just having Offset Index can optimizing IO, but I don't know how can we do when we only have Column Index

Actually we can archive it by disabling statistics on all columns. Without column statistics, ColumnIndexes are dropped automatically.

Yes, but seems it's a bit trickey here :)
Maybe we can document it?


Enable jre tests for jdk11

Signed-off-by: Sophia Guo<EMAIL_ADDRESS>

https://ci.adoptopenjdk.net/view/Test_grinder/job/Grinder/448/

@llxia Latest run for 11.0.1+b13 Hotspot got this:
===============================================
Running test jdk_math_jre_0 ...
===============================================

jdk_math_jre_0 Start Time: Sat Nov 24 20:39:44 2018 Epoch Time (ms):<PHONE_NUMBER>934

variation: NoOptions

JVM_OPTIONS:

{ mkdir -p "/home/jenkins/workspace/openjdk11_hs_openjdktest_x86-64_linux/openjdk-tests/TestConfig/scripts/testKitGen/../../../TestConfig/test_output_15430909402529/jdk_math_jre_0"; \

cd "/home/jenkins/workspace/openjdk11_hs_openjdktest_x86-64_linux/openjdk-tests/TestConfig/scripts/testKitGen/../../../TestConfig/test_output_15430909402529/jdk_math_jre_0"; \

"/home/jenkins/workspace/openjdk11_hs_openjdktest_x86-64_linux/openjdkbinary/j2sdk-image/bin/java" -Xmx512m -jar "/home/jenkins/workspace/openjdk11_hs_openjdktest_x86-64_linux/openjdk-tests/TestConfig/scripts/testKitGen/../../../../jvmtest/openjdk_regression/jtreg/lib/jtreg.jar" \

-agentvm -a -ea -esa -v:fail,error,time,nopass -retain:fail,error -ignore:quiet -timeoutFactor:4 -xml:verify -concurrency:4  -vmoptions:"-Xmx512m  " \

-w "/home/jenkins/workspace/openjdk11_hs_openjdktest_x86-64_linux/openjdk-tests/TestConfig/scripts/testKitGen/../../../../jvmtest/openjdk_regression/work" \

-r "/home/jenkins/workspace/openjdk11_hs_openjdktest_x86-64_linux/openjdk-tests/TestConfig/scripts/testKitGen/../../../../jvmtest/openjdk_regression/report" \

-compilejdk:"/home/jenkins/workspace/openjdk11_hs_openjdktest_x86-64_linux/openjdkbinary/j2sdk-image/bin/.." \

-jdk:"/home/jenkins/workspace/openjdk11_hs_openjdktest_x86-64_linux/openjdkbinary/j2jre-image" \

-exclude:"/home/jenkins/workspace/openjdk11_hs_openjdktest_x86-64_linux/openjdk-tests/TestConfig/scripts/testKitGen/../../../openjdk_regression/openjdk-jdk/test/jdk/ProblemList.txt" \

-exclude:"/home/jenkins/workspace/openjdk11_hs_openjdktest_x86-64_linux/openjdk-tests/TestConfig/scripts/testKitGen/../../../../jvmtest/openjdk_regression/ProblemList_openjdk11.txt" \

"/home/jenkins/workspace/openjdk11_hs_openjdktest_x86-64_linux/openjdk-tests/TestConfig/scripts/testKitGen/../../../openjdk_regression/openjdk-jdk/test/jdk:jdk_math"; \

if [ $? -eq 0 ] ; then echo ""; echo "jdk_math_jre_0""_PASSED"; echo ""; cd /home/jenkins/workspace/openjdk11_hs_openjdktest_x86-64_linux/openjdk-tests/TestConfig/scripts/testKitGen/../../..;  else echo ""; echo "jdk_math_jre_0""_FAILED"; echo ""; fi; } 2>&1 | tee -a "/home/jenkins/workspace/openjdk11_hs_openjdktest_x86-64_linux/openjdk-tests/TestConfig/scripts/testKitGen/../../../TestConfig/test_output_15430909402529/TestTargetResult";

Error: JDK not found: /home/jenkins/workspace/openjdk11_hs_openjdktest_x86-64_linux/openjdkbinary/j2jre-image

jdk_math_jre_0_FAILED
jdk_math_jre_0 Finish Time: Sat Nov 24 20:39:45 2018 Epoch Time (ms):<PHONE_NUMBER>593

@karianna is this the test build that you are referring to? https://ci.adoptopenjdk.net/view/Test_openjdk/job/openjdk11_hs_openjdktest_x86-64_linux/83/consoleFull
If so, the upstream build only has 'jdk'. It does not contain jre: https://ci.adoptopenjdk.net/job/build-scripts/job/jobs/job/jdk11u/job/jdk11u-linux-x64-hotspot/26/

@karianna this jdk_jre test need jdk to comiple test. That is if there is no jdk, test will fail. When will  jdk11u builds have jre image available? I mixed up jdk11 and jdk11u. And enabled the test as JDK11 builds have jre image. If it takes time I will re-disable it.

@karianna is this the test build that you are referring to? https://ci.adoptopenjdk.net/view/Test_openjdk/job/openjdk11_hs_openjdktest_x86-64_linux/83/consoleFull
If so, the upstream build only has 'jdk'. It does not contain jre: https://ci.adoptopenjdk.net/job/build-scripts/job/jobs/job/jdk11u/job/jdk11u-linux-x64-hotspot/26/

It was actually https://ci.adoptopenjdk.net/job/openjdk11_hs_openjdktest_x86-64_linux/82/console but it's the same error.

@karianna this jdk_jre test need jdk to comiple test. That is if there is no jdk, test will fail. When will jdk11u builds have jre image available? I mixed up jdk11 and jdk11u. And enabled the test as JDK11 builds have jre image. If it takes time I will re-disable it.

Hmm, you're right our pipeline did not build a jdk and a separate jre.  I assume the test pipeline expects one of each?

As there is a growing requirement for JRE image we suppose that build will produce both jdk and jre image?

The JRE will go away at some point. We're only actually able to build it for 11 because OpenJDK left a legacy 'make JRE' target.  But that could get taken away anytime from 12+.  Is it possible to skip those tests if no JRE is detected?


Close buffer given buffer number

Would love to see a way to close buffers given a buffer number. Something like BWipeout/BDelete <bufnr>

Hi @petertriho ,
Thanks for the issue. You can use :bd <bufnr><CR> or :bw <bufnr><CR> to delete a buffer based on a given buffer number.
Just thinking through the use-case atm, is it just for more coverage so that you can always rely on BWipeout/BDelete from close-buffers and not have to think about a different command?
Thanks,
Kevin

@kazhala My use case is to use BWipeout/BDelete with nvim-bufferline for the close_command and right_mouse_command. All good if you think it is out of scope as I still have famiu/bufdelete.nvim installed for it.

Hi @petertriho , it make sense now (was not thinking about window layout or any extra stuff). I'll see what I could do to support it over the weekend.


bugfix: server restart not recover max sessionId on db mode

Signed-off-by: slievrly<EMAIL_ADDRESS>
Ⅰ. Describe what this PR did
bugfix: server restart not recover max sessionId on db mode
Ⅱ. Does this pull request fix one issue?
fix #1851
Ⅲ. Why don't you add test cases (unit test/integration test)?
Ⅳ. Describe how to verify it

Ⅴ. Special notes for reviews

Codecov Report

Merging #1850 into develop will decrease coverage by 0.16%.
The diff coverage is 7.84%.

@@              Coverage Diff              @@
##             develop    #1850      +/-   ##
=============================================
- Coverage      55.05%   54.89%   -0.17%
- Complexity      2353     2357       +4
=============================================
  Files            422      421       -1
  Lines          14271    14315      +44
  Branches        1712     1719       +7
=============================================
+ Hits            7857     7858       +1
- Misses          5684     5729      +45
+ Partials         730      728       -2

Impacted Files
Coverage Δ
Complexity Δ

...io/seata/server/store/TransactionStoreManager.java
86.66% <ø> (ø)
0 <0> (ø)
:arrow_down:

...rver/store/db/DatabaseTransactionStoreManager.java
67.17% <0%> (-0.52%)
22 <0> (ø)

...server/store/file/FileTransactionStoreManager.java
59.01% <0%> (-1.19%)
29 <0> (ø)

...va/io/seata/core/store/db/LogStoreDataBaseDAO.java
54.74% <0%> (-4.33%)
21 <0> (ø)

...main/java/io/seata/core/store/db/LogStoreSqls.java
19.6% <0%> (-0.81%)
10 <0> (ø)

...eata/server/session/db/DataBaseSessionManager.java
32.78% <0%> (-2.31%)
11 <0> (ø)

...r/src/main/java/io/seata/server/UUIDGenerator.java
63.33% <60%> (+1.79%)
5 <1> (+1)
:arrow_up:

...io/seata/server/session/DefaultSessionManager.java
64.51% <9.09%> (-30.73%)
8 <1> (ø)

...rc/main/java/io/seata/common/util/LambdaUtils.java

... and 3 more


Jest snapshot testing and

Problem description
Looks like something in the <Toggle> component breaks while trying to run basic Jest snapshot tests.  jest.mock('material-ui/Toggle') prevents error and makes test work, though.
Anyone know if I can fix this? or is it something intrinsic to library?
Steps to reproduce
// component.test.js
import React from 'react';
import renderer from 'react-test-renderer';
import Toggle from 'material-ui/Toggle';
import MuiThemeProvider from 'material-ui/styles/MuiThemeProvider';

// to fix bug with accessing React.DOM()
//https://github.com/facebook/jest/issues/1353
jest.mock('react-dom')

test('Toggle should not blow up in snapshot test', () => {
  const component = renderer.create(
    <MuiThemeProvider>
      <Toggle
      label="simple"
        />
    </MuiThemeProvider>
  );
  let tree = component.toJSON();
  expect(tree).toMatchSnapshot();

});

### Versions

- Material-UI: 0.15.4
- React: 15.0.0
- Browser: n/a, node  v6.3.1

FAIL  src/components/ToggledCheckboxGrid/ToggledCheckboxGrid.test.js
 ● Toggle should not blow up in snapshot test

TypeError: Cannot read property 'checked' of null

  at EnhancedSwitch.componentDidMount (node_modules/material-ui/internal/EnhancedSwitch.js:205:50)
  at node_modules/react/lib/ReactCompositeComponent.js:264:25
  at measureLifeCyclePerf (node_modules/react/lib/ReactCompositeComponent.js:74:12)
  at node_modules/react/lib/ReactCompositeComponent.js:263:11
  at CallbackQueue._assign.notifyAll (node_modules/react/lib/CallbackQueue.js:67:22)
  at ReactTestReconcileTransaction.ON_DOM_READY_QUEUEING.close (node_modules/react/lib/ReactTestReconcileTransaction.js:37:26)
  at ReactTestReconcileTransaction.Mixin.closeAll (node_modules/react/lib/Transaction.js:204:25)
  at ReactTestReconcileTransaction.Mixin.perform (node_modules/react/lib/Transaction.js:151:16)
  at batchedMountComponentIntoNode (node_modules/react/lib/ReactTestMount.js:63:27)
  at ReactDefaultBatchingStrategyTransaction.Mixin.perform (node_modules/react/lib/Transaction.js:138:20)
  at Object.ReactDefaultBatchingStrategy.batchedUpdates (node_modules/react/lib/ReactDefaultBatchingStrategy.js:63:19)
  at Object.batchedUpdates (node_modules/react/lib/ReactUpdates.js:98:20)
  at Object.ReactTestMount.render [as create] (node_modules/react/lib/ReactTestMount.js:120:18)
  at Object.<anonymous> (src/components/ToggledCheckboxGrid/ToggledCheckboxGrid.test.js:15:73)
  at process._tickCallback (internal/process/next_tick.js:103:7)

 ✕ Toggle should not blow up in snapshot test (20ms)

Snapshot Summary
 › 1 obsolete snapshot found, run with `npm run test-jest -- -u` to remove them.

Test Suites: 1 failed, 1 total
Tests:       1 failed, 1 total
Snapshots:   0 total
Time:        1.043s
Ran all test suites.

npm ERR! Linux 4.4.0-38-generic
npm ERR! argv "/home/bmp/.nvm/versions/node/v6.3.1/bin/node" "/home/bmp/.nvm/versions/node/v6.3.1/bin/npm" "run" "test-jest"
npm ERR! node v6.3.1
npm ERR! npm  v3.10.3
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>test-jest: `jest`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>test-jest script 'jest'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the react-redux-starter-kit package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     jest
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs react-redux-starter-kit
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls react-redux-starter-kit
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /home/bmp/code/wayhome/homeseeker-fresh/npm-debug.log

Hey @brandonmp, I'm not sure what causes that issue, I strongly encourage you to open up a question on stackoverflow though. ;)

thanks, i'll cross-post there, and to the Jest repo
I'd like to leave it open here, however, because:
a) there isn't really any config to go into Jest that could be screwed up in my project, so i don't think it could be config user-error
b) when i generate snapshot tests for other components, it works fine. in fact, some components which include <Toggle> won't work until I delete <Toggle>
c) the other MUI components i've used in Jest snaps work fine
all of these suggest to me it may be some part of the <Toggle> src causing this, so i thought there's at least some chance it's a bug in the component

Okay, i dug into the <Toggle>, it turns out there's a bug in React that prevents components that use refs from being handled correctly by react-test-renderer.
Apparently, it'll be fixed in React 15.4.0. until then, the guidance is to just mock() components that use refs.
https://github.com/facebook/react/issues/7740

@brandonmp try enzyme-to-json instead of react-test-renderer for snapshot testing

Hi guys,
I tried updating React & auxiliaries to 15.4.0 but the render test still failed with

Cannot read property 'checked' of null

I also tried with Enzyme and now I'm getting the following empty snapshot:

exports[Login renders 1] = null;

(I'm writing tests for a redux-form that uses https://github.com/erikras/redux-form-material-ui)
Were you able to make it work somehow? If you could post a few tests with Jest, it would be most helpful. Thanks!

I faced the same issues with the following versions:
"react": "^15.4.2",
"react-test-renderer": "^15.4.2"
"jest": "^18.1.0",
"material-ui": "^0.16.7",
I had to mock the following internal modules to take a snapshot of the material-tabel
jest.mock('material-ui/internal/EnhancedSwitch')
jest.mock('material-ui/internal/Tooltip')

@jonas-e-medicus
How does this work?
import initStoryshots from '@storybook/addon-storyshots';

import jest from 'jest';

jest.mock('material-ui/LinearProgress');

initStoryshots();

I got this error after I add it into my code
Cannot read property 'default' of undefined


Issues loading next page of results

I almost entirely open pipe-viewer (CLI) with the -u or -sc options rather than searching all of YouTube, but when I do, the :n command almost never works on those results from a single user, displaying "[!] This is the last page!".  I know it's not, and it's generally not too much of an issue since the thirty or so videos I can access still give me plenty of viewing material, but I do occasionally want to pull up something older.  More egregiously, though, the same thing happens with the playlist view, which means I have a lot of trouble seeing any episode 21 or later.  I'm guessing it's some issue with pages sorted chronologically (forwards or reversed) since the -sc list itself also has no issue going to the next page, but I'm not exactly sure what would cause it.

Seems to work perfectly.  Thanks for the fix, and thanks for the wonderful tool!


on GitHub Actions, execute gradle build --scan

Enable Build Scan™ publishing
Gradle Build Scans are a great way to view your build results, and provide valuable insights into your build. In order to publish Build Scans from GitHub Actions, you’ll need to pre-approve the Terms & Conditions.
To do so, add the following content to the top of your settings.gradle[.kts] file. The "CI" environment variable is set by GitHub Actions:
plugins {
    id("com.gradle.enterprise") version("3.9")
}

gradleEnterprise {
    if (System.getenv("CI") != null) {
        buildScan {
            publishAlways()
            termsOfServiceUrl = "https://gradle.com/terms-of-service"
            termsOfServiceAgree = "yes"
        }
    }
}

Done at 0.7.0-SNAPSHOT


Typo in Readme.rst

Hi,
I'm working with OCPP for a few weeks now and I just noticed this due to PyCharm telling me.
There is a typo in the Readme - Quick start - Central system section.
It says on_boot_noti-t-ication instead of noti-f-ication.
class ChargePoint(cp):
@on('BootNotification')
async def on_boot_notitication(self, charging_station, reason, **kwargs):
...
I really don't want to be annoying, I just thought you would want to know :)
Keep up the great support 👍

Thanks for reporting @henbier


kInvalidBinNum error

Currently I am running tensorrtserver:19.01-py3 and I got following error message and stopped working:
E0213 17:49:43.688371 1 bfc_allocator.cc:458] Check failed: c->in_use() && (c->bin_num == kInvalidBinNum)
What is the source of this error? Can it be avoided somewhat?
If possible, can you tell when nvcr.io/nvidia/tensorrtserver:19.02-py3 image will be available?

This looks similar:

https://github.com/tensorflow/serving/issues/1206

That thread points to this:

https://github.com/tensorflow/tensorflow/issues/22581


Make the assets available to the docker image

Test failures on tip, will be fine once gb is thrown to the depths of hell


We need to publish some files around main.php?

There's a file can not be found .

I don't understand your problem.

What kind of file cookiejar.txt?

This is file created by curl.

ErrorException in main.php line 73:
file_get_contents(cookiejar.txt): failed to open stream: No such file or directory

It does not create a file cookiejar.txt

Look my pull request

Do you set chmod on 777 for data folder?
Thx for pull request.

The problem was that the file is searched near main.php and not there, where I have to keep.

Ok, problem has been fixed.


Remove bool from variable ops on GPU

See related discussion on https://github.com/tensorflow/tensorflow/pull/38848#issuecomment-623758481
/cc @mihaimaruseac @alextp this PR removes bool from the GPU. let me know if you prefer to revert first instead.
Signed-off-by: Yong Tang<EMAIL_ADDRESS>

Oh, the rollback landed so now there are conflicts

@mihaimaruseac @alextp I have updated the PR with content changed to:

Resubmit of PR #38848 but only support complex64 and complex128

Please take a look and see if it makes sense.


Not working on Windows: Cannot read property 'IsAndroid' of undefined

var RNSound = require('react-native').NativeModules.RNSound;
var IsAndroid = RNSound.IsAndroid;

I've tried to remove the node_modules and install again and reboot every thing! but still facing the the same error;
I've tried to log the require('react-native').NativeModules but the `RNSound wasn't there

https://stackoverflow.com/questions/70823585/react-native-sound-not-working-on-windows-cannot-read-property-isandroid-of-u/71161805#71161805

I am also facing this issue while running on windows.
What is the solution?

+1


[KYUUBI #6078] KSHC should handle the commit of the partitioned table as dynamic partition at write path

:mag: Description
Issue References 🔗

This pull request fixes https://github.com/apache/kyuubi/issues/6078, KSHC should handle the commit of the partitioned table as dynamic partition at write path, that's beacuse the process of writing with Apache Spark DataSourceV2 using dynamic partitioning to handle static partitions.
Describe Your Solution 🔧
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Types of changes :bookmark:

[x] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Test Plan 🧪
Behavior Without This Pull Request :coffin:
Behavior With This Pull Request :tada:
Related Unit Tests

Checklist 📝

[x] This patch was not authored or co-authored using Generative Tooling

Be nice. Be informative.

Please take a look if you have a time, @FANNG1 @pan3793

Codecov Report
Attention: Patch coverage is 29.82456% with 40 lines in your changes are missing coverage. Please review.

Project coverage is 61.14%. Comparing base (1adf392) to head (2ae1836).
Report is 2 commits behind head on master.

Files
Patch %
Lines

...bi/spark/connector/hive/write/HiveBatchWrite.scala
21.56%
39 Missing and 1 partial :warning:

Additional details and impacted files
@@             Coverage Diff              @@
##             master    #6082      +/-   ##
============================================
+ Coverage     61.12%   61.14%   +0.02%
  Complexity       23       23
============================================
  Files           623      623
  Lines         37206    37166      -40
  Branches       5041     5030      -11
============================================
- Hits          22743    22727      -16
+ Misses        12012    11995      -17
+ Partials       2451     2444       -7

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

Overall LGTM, let me merge it first, and address comment in follow-up PRs.


Limited support

Unfortunately, something like:
2 weeks ago

is not parsed. I think such expressions are one of the primary reasons to use a fuzzy parser. If I have actual dates, then I can just try common formats and one will eventually work.

Finally got around fixing this. Should be working in the newest version.


Enviromental Alarm trigger

Checklist

[x] I checked for similar existing requests (both open and closed) before posting.
[x] My request is generic, other users may benefit from it too.

Proposal
Would be good to have an alternative, so it can triggering a different message/alarm
Additional info
[some example of how the new functionality should look like]

+1

+1(0 😉)

I'm using Noonlight for monitoring which supports water and smoke. I'm interested in maybe adding this. I'd propose we do the following:

Extend the device type fields to include specific  (eg. smoke, water, fire, CO, maybe panic while we're at it)
Add a new Mode called "Always" to allow keeping the devices armed all the time; we can use the existing arm/disarm logic to allow temporarly disarming it for maintenance.
Add a new Condition in the Actions pane to only fire an action if the type matches

@stonegray
I like your proposal. At this moment always on is set implicitly by the device types (smoke, water etc). Making it an additional setting, on by default for these types, would be better.
I have a use case for that: windows that shall remain closed and emergency doors. I can only make them always on changing them into smoke or water types 🥹

I solve this problem with areas now. The purpose is being able to not have the siren fire when something is tampered or flooded. Problem is Alarmo won't allow areas with no armed modes activates (only disarmed with environmental triggers is not allowed.

due to the fact, that "windspeed is too high" is well as "rainrate is too high" are no supported deviceclasses, I tried to keep them as "problem". they would trigger the alarm, but when they get into normal state, the alarm stays triggered.
so maybe supporting the "problem" class would be a good idea for environmental sensors

This could do well with adding devices, instead of sensors. So that tamper and battery could be included with the alarm sensor itself. Result could be an elegant solution for different notifications and actions depending on tampering etc, without using areas.

I use the Ring Keypad, different types of alarms could for example be used for triggering different types of siren sounds/lights on the keypad itself.

@nielsfaber regarding #248 and this issue. Perhaps Alarmo could create three services. The calling of which could generate police/burglar, medical and fire alarms. A nice solution to this issue (896) could nicely be combined with panic button support.
Notifications should also, according to me not only include the tripped sensor and state, but also if the type of alarm is burglar/police, fire, or medical.

Still very interested 😀

🙏

+1

🙏

You can have different actions, if you put the sensors in another "Area"
For example, my Smoke Detectors are all in a "Smoke Detector" Area and can trigger a different action.
Same for my Water Leakage Detectors, the all go into "Water Detector" Area.
Here is an example screenshot (sorry only in german)


Simpler, better wkspawn implementation

As suggested by @vchuravy, and that mirrors the fix proposed in https://github.com/JuliaLang/julia/pull/47829.

Codecov Report
Base: 87.50% // Head: 89.23% // Increases project coverage by +1.73% :tada:

Coverage data is based on head (abf9c58) compared to base (43cec4e).
Patch coverage: 94.11% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #12      +/-   ##
==========================================
+ Coverage   87.50%   89.23%   +1.73%
==========================================
  Files           1        1
  Lines         168      130      -38
==========================================
- Hits          147      116      -31
+ Misses         21       14       -7

Impacted Files
Coverage Δ

src/WorkerUtilities.jl
89.23% <94.11%> (+1.73%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Command: refresh_folder_list

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/1197130-command-refresh_folder_list?utm_campaign=plugin&utm_content=tracker%2F282001&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F282001&utm_medium=issues&utm_source=github).

Migrated to limetext/lime-backend#20.


Update CSS token per new design system theming capability

Alaska Airlines Pull Request
Fixes: #97
Summary:

Update the design tokens to reflect the new theming conventions regarding tokens from the AuroDesignTokens and JetstreamDesignTokens repo.

Type of change:
Please delete options that are not relevant.

[x] Revision of an existing capability

Checklist:

[x] My update follows the CONTRIBUTING guidelines of this project
[x] I have performed a self-review of my own update

By submitting this Pull Request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
Pull Requests will be evaluated by their quality of update and whether it is consistent with the goals and values of this project. Any submission is to be considered a conversation between the submitter and the maintainers of this project and may require changes to your submission.
Thank you for your submission!
-- Auro Design System Team

The  npm ci is failing because some auro components have conflicting peer dependency for @aurodesignsystem/webcorestylesheets package. Should I hold of this until those components are updated?

This PR is BLOCKED until this PR is approved and shipped.

https://github.com/AlaskaAirlines/auro-badge/pull/85

This branch needs to be repointed from main to a new RC branch.

This PR also BLOCKED by:

https://github.com/AlaskaAirlines/auro-flightline/pull/59

until it is approved, merged, and released.

This PR also BLOCKED by:

Update CSS token per new design system theming capability auro-flightline#59

until it is approved, merged, and released.

Shipped. @fajar-apri-alaska please update repo and update status of issue to 'design review needed' to ensure that issue #102 has also been addressed.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Invert colors in depth image

Hi,
Is there a way to invert colors in a depth image?
When displaying this:
depth_image = np.asanyarray(depth_frame.get_data()) * depth_scale
I get a depth image where closer points to the camera are darker, but I want it to be exactly the opposite, without losing the distance information ( the closer the point the lighter).
Any idea? Thanks

There was a case in March 2020 where a RealSense user programming in Python was getting depth displayed as red in the near range and blue in the far range when they applied a colorizer to the depth data.  The approach taken to invert the colors was to load a different visual preset file.
https://github.com/IntelRealSense/librealsense/issues/3363
The case in the link above contains a link directing to a list of number codes for the visual presets.  The link below contains the correct jump-to point for the list.
https://github.com/IntelRealSense/librealsense/blob/master/include/librealsense2/hpp/rs_processing.hpp#L718

Thanks! This worked fine.

Great news - thanks for the update!