Requesting a file explorer add-ons feature

Description of the new feature / enhancement
I request you to add .webp file type for preview under file explorer add-ons.

Scenario when this would be used?
I'm a front-end developer and I've to work with a lot of images and most of them are .webp format. It is very irritating to open the files in a new tab of a browser again and again.
Having preview of that type of file will help me and a lot of persons like me.
Thanks, and Regards.

Supporting information
No response

/dup #3990

/dup #6392


Update README.md to fix URL that does not render as a link on http://www.covidhip.com/

Bare URL syntax could be used instead, but this approach seemed consistent with other links in the document.

Thanks David, good catch!


Keyword search polish: Build split keyword/location text entry field

See commit ac1c03eb14821a73632b415fcceb2735382913e6 and those preceding it, I had something like what is described here working, so there might be some ideas to be had.
1. Split search into two input fields. With the aim to allow users to search conveniently, we want to provide an updated search experience where users could adjust both the keyword and the location field together instead of having to navigate between one to another. Users may optionally specify location, so search works with or without location set.
Search is not "live", user has to click button "Search" (in upper right of mocks) to make the search happen.
Stretch goal is to support live search if it is easy. In this case, there is no "Search" button, there is a "Done" button that collapses the two input fields into one.

Initial screen:
https://zpl.io/VkzBBWW
With focus on key words input
https://zpl.io/Vq5ZZLG
With focus on location input
https://zpl.io/2ZB99ZE
With both fields are populated, note truncation of search strings to save screen space
https://zpl.io/a3DkZpN

Acceptance criteria:

[ ]  Incorrect font for both search input field - ensure it’s Avenir Book.
[ ]  Opacity for texts within search input fields should change according to its state: 1) with placeholder text - 60%, GreyishBrown, 2) with user input - 100%, Black.
[ ]  Search input fields are white (#ffffff) - the background, not the text.
[ ]  Typing indicator should be in black instead of green in iOS.
[ ]  “X” icon for both search input fields should be white instead of black.
[ ]  “My location” button should have a right-padding of 16dp. Refer to https://zpl.io/2ZB99ZE.
[ ]  Touch area for the “X” icon is too small, make sure it is easy to clickable.
[ ]  Back button is removed from Search
[ ]  'Show more service' button display the text properly (not cut off nor go to next line)
[ ]  Both search input icons are aligned and from MaterialIcon pack

Steps to QA:

Go to search screen
The search screen should have 2 input fields that look this mock
https://zpl.io/VkzBBWW
Type into search term input, the results should update live
Click on X to the right of the search term input and should clear the input field
Type in another search term
Click on the location input field and the My location button should appear. Refer to this mock:
https://zpl.io/2ZB99ZE
Accept permissions if necessary and the results should reflect your current location
Click on X to the right of location input should clear the field
Manually type in a city like 'Surrey' and the results should update
Scroll to the bottom of search results and there should be a find more services button if the results is longer than 20 item. Refer to this mock: https://app.zeplin.io/project/5bc7bfa42e72260acb03aa86/screen/5df04f8ad731a2a4441970ed
Click on the more services button and more related services should load.

@cherrielam @aron-chen-pg @rasmus-storjohann-PG
This is the updated search input fields based mostly on mock#2 that is in the issue.

Here is an update with the My Location button. It's here and functional.

Merged the PR, found one issue:

Open search page
Enter some search terms and get the results
Click on a service to open the service detail
Click the back button
Expected: The search terms are still there
Observed: The search screen input fields have been reset to empty

@ian-lin-PG the Done button that you see in the mocks is missing on Android. Is that intentional?

@ArtiBPG

The done button is omitted for now because live search is enabled and it's not necessary to click done to start the search. It can be included in this issue such that when click done the 2 input fields merge into 1. I will consult with you and @aron-chen-pg  when I get to that issue.

The empty state mock and the partial translation for the service listings are tracked here

Let me know if splitting up the issue this way is confusing.

@jparlina tested for Android, test on iPhone.

With the updated design, we no longer have the "Done" button. I've updated the Zeplin link within this issue to reflect the change.

Tested on iPhone X, aside from UI refinement and other concerns that were already raised, search inputs are functioning as expected.

This issue has been separated into various other issues in the past few months.
Related issues:
Search input field styling and collpasing: #957 and #1030
Show more services button: #1058
Closing.


Add PS5 DualSense support to Babylon.js

Once the DualSense gamepad is fully supported by PC and web, support for it should be added to Babylon.js' input systems.

@PolygonalSun can we close it??

@PolygonalSun can we close it??

None of the work for this has been merged into master but if we're fine with adding it now, I can have a PR up with a day or so.  It only required a new button enum,  value in the DeviceType enum, and updated detection logic (one additional line of code?).

Yes let's do it!


Speed up ForwardDiffExt with batched solve

See https://github.com/gdalle/ImplicitDifferentiation.jl/issues/71#issuecomment-1662287726 by @thorek1

here you can see nicely as well why its worth having different conditions_backends. if you go from m input elements to n output elements and m >>n you want to use reverse mode overall but the conditions go both ways in terms of dimensionality. once you go from m to n and once from n to m (solution as input). in that sense, the case with the potentially largest efficiency gain is the one where you diff the condition with respect to the solution (b). and if m >> n or vice versa it can make sense to use autodiff the other way compared to what you use on the implicit function. I hope this was clear :)

I'm struggling to make this work because gmres(A, B) doesn't work to perform parallel solve when B is a matrix. On the other hand, A \ B works fine

See the vec and reshape operations in my example.
I also gave it a try but was struggling with the operators. Working with realised matrices is somewhat easier for me...

I tried a bit myself and managed for the direct solver case but the linear operator dimensions are a bit tricky to figure out

This is an internal performance issue that can always be improved in a non breaking way, so I'm putting it on hold to focus on the design for v0.5

Fixed by #135 for the dense Jacobian case, see #129 for the lazy Jacobian case


Fix #51

Coverage decreased (-0.008%) to 3.141% when pulling ac1ff59022fb13ae9b9b82404ecfb41fc592d3b3 on name-dieref into 990dc7c8266c5102d265048990db970cb4089a54 on master.

Coverage decreased (-0.03%) to 3.117% when pulling 125dde87a065df4b1cd77d47f28424eecf3cde9b on name-dieref into 990dc7c8266c5102d265048990db970cb4089a54 on master.


[Suggestion] Make easy to find demo highlights

Hello! I started to use this is great tool to find professional players highlights from GOTV demos. Manager already has columns with 4K, 5K, 1vX situations but in current version need to do many clicks to find successful clutches. Maybe will it be useful in some way?

What do you propose?

A new major version has been released, closing the issue 🧹


Faster screen redraws by using NumPy for image_to_data conversion

Using NumPy in the image_to_data function speeds up screen redraws by 80%.

Just had some time to sit down and get an ILI9341 display connected to the Pi to test this.  It works great and is much, much faster than the non-numpy code.  Will update the tutorial to mention installing numpy now too.  Thanks for submitting the great pull and apologies it took a little while to be reviewed and merged.


Ideal Image element resizing doesn't seem to be happening with CameraRoll

I am trying to render out some images from the CameraRoll and am running into trouble with it rendering the full sized images. The Image element documentation says that it will choose the most optimal image size when loading images from a camera roll.

iOS saves multiple sizes for the same image in your Camera Roll, it is very important to pick the one that's as close as possible for performance reasons. You wouldn't want to use the full quality 3264x2448 image as source when displaying a 200x200 thumbnail. If there's an exact match, React Native will pick it, otherwise it's going to use the first one that's at least 50% bigger in order to avoid blur when resizing from a close size. All of this is done by default so you don't have to worry about writing the tedious (and error prone) code to do it yourself.

Documentation Reference
I tracked down the code that looks like it should resize the image and when I set a breakpoint it never gets hit. Here are the lines that never get hit. Note that this is for v0.11.0 and master is already different, so maybe this has been fixed.
Am I missing something like a property that I'm not passing to the Image element, or is the automatic most optimal image selection not working as I think it should?

Looks like @nicklockwood might have context on this.

Anyone have any more information on this?

Can you better summarize what is (or is not) happening on your end? (screenshots, etc)
Also, please try the latest release if possible. Version 0.12 just landed with additional CameraRoll refactoring. You'll need to add the RCTCameraRoll library and then link it under Build Phases. I can better help you then.

@aroth I can probably get a better description of what is going on in the next day or two. I'll try updating to 0.12 first to see if that resolves it. Thanks.

@aroth So after updating to 0.12 I am not seeing the same behavior. Whether that is because something was fixed or I was misunderstanding what was going on...who knows.
Thanks for the help!


sane defaults for lxd init

Please add sane defaults to the lxd init questions, like we do for the debconf questions for lxd networking:
⟫ sudo lxd init
Name of the storage backend to use (dir or zfs) [zfs]: zfs
Create a new ZFS pool (yes/no) [YES]? yes
Name of the new ZFS pool [lxd]: lxd
Would you like to use an existing block device (yes/no) [YES]? no
Size in GB of the new loop device (1GB minimum) [10]: 10
Would you like LXD to be available over the network (yes/no) [NO]? no
Do you want to configure the LXD bridge (yes/no) [YES]? yes
The idea here is that "just hitting enter" will get you a decent, sane working setup.  Don't try to be perfect for everything, but we should be able to get this working well enough for most people.
Also, let's smart about this, too.  If I do choose yes on the network question, then when I'm prompted for the address to bind to, please pre-populate with a sane ip address.  Same with the default port, 8443.

I came here to report the same bug.
The lxd 'getting started' guide doesn't contain this information either (https://linuxcontainers.org/lxd/getting-started-cli/). As a new lxd user, I have no idea what the correct answer to any of these questions is. As well as adding sane defaults to the cli, adding more information to the getting started guide would help new users pick sensible answers.

Defaults are always a good thing, but what about choosing something other than the default?   What are the implications?  And why and when to use something other than the defaults?  This information could ne even more important than using the default!


Fails to start on Windows 7

I'm getting this when running SourceGen.exe:

I also had to calm Symantec's nerves about WS.Reputatoin.1, but that's to be expected in this nanny state.

Hrm.  More assumptions -- I figured Microsoft shoved .net everywhere.
If you do Windows+R and type "dotnet", does it say it can't find anything by that name?  (If it's installed, it'll just pop open a window for a fraction of a second while the shell command runs.)
https://www.microsoft.com/net/download/dotnet-framework-runtime if you want to join the party.

No dotnet response from Run.  So, installing now - or, it says "do you want to repair or replace 4.7.2?" so maybe I had something on there at one time... we'll see what this gets me.

Back from reboot now - Run still can't find a dotnet.  Is there another way to query its existence?

I posted on stackoverflow and somebody found the problem (https://github.com/fadden/6502bench/issues/3).  I've posted 1.0.0-alpha2 in releases; please give that a try.

And we're off!  Thanks!


Error Using More Than ~64KB of Storage in File System

Flash: Winbond W25Q32JV 32Mbit Serial Flash;
IDE: uVision (V<IP_ADDRESS>);
C complier: Keil C166.exe  (V<IP_ADDRESS>);
The file system mounts properly and runs as expected until using approximately 64KB of storage, whether it be a file larger than 64KB or multiple files adding up to over 64KB. At the point that I reached ~64KB, I receive a SPIFFS_ERR_DATA_SPAN_MISMATCH error (-10014). This error occurs within the spiffs_page_data_check() function (spiffs_nucleus.c line 4) as it is called in spiffs_object_append() function (spiffs_nucleus.c line 1477) during a write. I have included an output file of the print messages from opening and writing a large file until it breaks. Based off past posted issues similar to what i'm experiencing, I have SPIFFS_ALIGNED_OBJECT_INDEX_TABLES enabled. I use #pragma pack(1) and #pragma BYTEALIGN because my compiler does not use __attribute((aligned())). I have also included my spiffs_config.h file. I have checked my HAL layer as well. Any insight would be greatly appreciated.
Open_Write85KBFile.LOG
spiffs_config.txt

Closing this issue. This was a compiler issue.


[Bug]:  ERROR: You requested the 1st label, but the specified ZPL doesn't generate any labels

Is there an existing issue for this?

[X] I have searched the existing issues

Description
This error occurs when we try sending an HTTP request of post type, for some reason, Appsmith with rest API
isn't working as intended, it's important to mention that it actually works fine on Postman with the same configuration.
Steps To Reproduce
To Reproduce: Get on the Labelary bug test app, and go to the post pages, go to the APIs query and run the post example.
Public Sample App: https://app.appsmith.com/app/labelary-bug-test/get-64356de17c81ad7697465bf3
Public Sample App
No response
Environment
Production
Issue video log
No response
Version
Appsmith Version:Appsmith v1.9.15-SNAPSHOT

I was able to make the API work using the POST method. The API is very simple, follow these steps:

Copy this CURL code:

curl -X POST -H "Content-Type: application/x-www-form-urlencoded" -d "^xa^cfa,50^fo100,100^fdHello World^fs^xz" https://api.labelary.com/v1/printers/8dpmm/labels/4x6/0/

In Appsmith, create a new query and select the "New cURL Import" option.

Paste the CURL code that I provided earlier and save.

Run the API generated by the CURL import and you'll see that it works correctly.


CRI-O updates / run-through

CRI-O and Buildah seem to be broken as of the #113 PR, I believe that likely there are upstream changes to CRI-O and Buildah that may have impacted the functionality of these roles, and not due to the change in method for installing golang.
That being said, it needs to have a run-through to make sure it's functional.

#276 fixes the issue, I hope. Hence closed.


[cmake] optimize opencv.cmake to ensure find_package take affect

PR types

PR changes

Describe
find_package() 优先查找目录优化

LGTM


Fix HOB length bounds and TDX extraction

The SP800155 events fit in a single page, but the technical limit is UINT16. I've added a check at marshaling time too, so too-large events don't make it past signing.
The SEV-SNP client in the extraction CLI command needed to get swapped with the more general configfs-tsm client to account for TDX. We still should not expect to need the query provider if the signatures are provided through the event log, but better to cover our bases.

Ping :)


[Enhancement] Add integtest.sh to unify the integTest for k-NN in OpenSearch

Is your feature request related to a problem? Please describe.
[Enhancement] Add integtest.sh to unify the integTest for k-NN in OpenSearch
Describe the solution you'd like
In order to resolve the issues in ODFE where all plugins integTest saved in one yml,
we propose new OpenSearch solutions where every plugin repo host abstraction layer of integtest.sh
so that all plugins integTest can be run in the same ways with the same commands.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

Are we set on using this mechanism? We could be running a GitHub action like this.


Weird pylint format / default with all info

What is the "pylint" format based on?
The old default for pylint itself was "pylint --msg-template='{msg_id}:{line:3d},{column}: {obj}: {msg}'" and now is "{C}:{line:3d},{column:2d}: {msg} ({symbol})" (https://docs.pylint.org/en/1.6.0/output.html).
I would like to use pylama's pylint format, but it is missing the column.
    pattern = "%(filename)s:%(lnum)s:%(col)s: %(text)s"
    if options.format == 'pylint':
        pattern = "%(filename)s:%(lnum)s: [%(type)s] %(text)s"

What do you think about specifying --pattern?
And what about a default format that includes all information? (with type and col) :)

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/37620681-weird-pylint-format-default-with-all-info?utm_campaign=plugin&utm_content=tracker%2F394650&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F394650&utm_medium=issues&utm_source=github).

"pylint" seems to be derived from pylint's "parseable" format:

{path}:{line}: [{msg_id}({symbol}), {obj}] {msg}

?

Hello, historically I'd used this format for Jenkins plugin. Thank you for PR.


Should fix #966

Changes Unknown when pulling a346997efda3db0f758b16cc3a6b65b9351db9e5 on Jorge-C:966 into ** on biocore:master**.

:+1:

Coverage remained the same at 79.04% when pulling 704077ecd753a17491da78729d6873873c75054f on Jorge-C:966 into c36e38b7cf59fc0819f0f0e6090d616892412bd0 on biocore:master.

:+1: tested, works


Button similar to digital ocean hacktoberfest 🔥

added a button to open a new window for digital ocean site

Nice :)


support CommonJsSelfReferenceDependency

What problem does this feature solve?
https://github.com/webpack/webpack/blob/1f99ad6367f2b8a6ef17cce0e058f7a67fb7db18/lib/dependencies/CommonJsSelfReferenceDependency.js#L1-L158
What does the proposed API of configuration look like?
https://github.com/webpack/webpack/blob/1f99ad6367f2b8a6ef17cce0e058f7a67fb7db18/lib/dependencies/CommonJsSelfReferenceDependency.js#L1-L158

Support by #5114


Add install to instructions

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: TerryHowe
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

docs/OWNERS [TerryHowe]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: jaxesn, TerryHowe
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

docs/OWNERS [TerryHowe,jaxesn]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


How to return from two var?

new Clipboard('.btn-copy', {
target: function(trigger) {
var a = document.querySelector(".data-order");
var b = document.querySelector("#t");
return (a,b);
}
});
I wanna make somehing like above, but return wrong result, can u help?

Hey @agusesetiyono,
You can't set two targets, it needs to be only one Node. Please share an isolated code on JSFiddle that includes some isolated markup so I can help you better.

Looks dirty, but using text instead could work:
new Clipboard('.btn-copy', {
  text: function() {
    var v1 = document.querySelector('.data-order').value;
    var v2 = document.querySelector('#t').value;
    return '' + v1 + v2;
  }
});

Yep, that's an alternative. Thanks for sharing @TimPetricola :)

thanks all :)


Inspiration from Laravel

Adonis is heavilly inspired by Laravel, whay isnt there any name of laravel in the doc?

I agree it is , i said that on a thread here http://qr.ae/RP7kTn . But i do not want to use Laravel's popularity by saying it everywhere on the official website.

As a Laravel developer and new to the vue/nuxt world i really liked your framework, but I would also appreciate some kind of post? idk, that could describe the parallelism between AdonisJS and laravel, that would help to adopt it more quickly, something along "AdonisJS for Laravel developers" or "How do you do that thing that you've done in Laravel so many times but, on AdonisJS", since, in my case I find myself researching every line I don't fully understand (I've realized that my knowledge of node is very thin).


Request access for sunpy

Hello!
We (over at the sunpy project) want to provide a nightly wheel for our core package, sunpy.
I think we might come under the definition of core, at least within our little ecosystem in solar physics. Packages like astropy's reproject I think have CI that checks against dev sunpy, so a wheel there would be helpful.
Would it be possible to gain access?
Happy Holidays.

👋 Thanks for the Issue. This is the right place to raise such a request, but we're unfortunately still deciding how to address them. Please join the discussion over on Issue #45.
(Apologies for the short response. I'm traveling at the moment and have a broken computer so I'm stuck on GitHub's mobile app till I fix that.)

I think it would make a lot of sense to do an openastronomy registry and serve wheels for sunpy, astropy, pyerfa, etc from there, as these are way less core packages in the sense of the whole ecosystem than e.g. awkward et al. But they are clearly and definitely domain ones.

I think it would make a lot of sense to do an openastronomy registry and serve wheels for sunpy, astropy, pyerfa, etc from there, as these are way less core packages in the sense of the whole ecosystem than e.g. awkward et al. But they are clearly and definitely domain ones.

That said, we should definitely go ahead and merge #47 as soon as possible, so the infrastructure can be shared and reused even for a different registry

That said, we should definitely go ahead and merge #47 as soon as possible, so the infrastructure can be shared and reused even for a different registry

Where would we host an openastronomy registry?
Happy to get involved in helping that if possible.

on anaconda, just as it's done for liberfa and astropy atm.

Makes sense to me. I see there is an https://anaconda.org/openastronomy I just need an access token to start uploading? I need to look at the workflow and see how it works.

@nabobalis Good news, we have the approval (https://github.com/scientific-python/upload-nightly-action/issues/30#issuecomment-1960037619) to add sunpy to the nightly wheels Anaconda Cloud org https://anaconda.org/scientific-python-nightly-wheels/ !
To get started on this can you please do the following:
Steps to gain upload access to https://anaconda.org/scientific-python-nightly-wheels/

[ ] Create an account on Anaconda Cloud
[ ] Reply here with the link to your account
[ ] Make a new Anaconda Cloud API token with permissions described in https://scientific-python.org/specs/spec-0004/#process-for-adding-new-projects

[ ] Save the API token as a repo GitHub Actions secret named ANACONDA_ORG_UPLOAD_TOKEN
[ ] Direct me (@matthewfeickert) to a sunpy nightly wheel for me to upload to create the package in the registry
[ ] Verify that I have added you to the sunpy team "Group" on https://anaconda.org/scientific-python-nightly-wheels
[ ] Verify that I have added the package scientific-python-nightly-wheels/sunpy to the sunpy team "Group"

If you'd also like to use the scientific/upload-nightly-action GitHub Action that this repository provides please check out this repo's README. If you need to collect wheels from different CI jobs, consider creating a new GitHub Actions workflow with logic similar to matplotlib's or Awkward's.
If you have any questions please just ask here!

@nabobalis Good news, we have the approval (#30 (comment)) to add sunpy to the nightly wheels Anaconda Cloud org anaconda.org/scientific-python-nightly-wheels !

Thank you!

Steps to gain upload access to anaconda.org/scientific-python-nightly-wheels

[X]  Create an account on Anaconda Cloud
[X]  Reply here with the link to your account

Would a sunpy (non-personal) account be ok? https://anaconda.org/sunpy/

[X]  Make a new Anaconda Cloud API token with permissions described in scientific-python.org/specs/spec-0004/#process-for-adding-new-projects
[X]  Save the API token as a repo GitHub Actions secret named ANACONDA_ORG_UPLOAD_TOKEN
[X]  Direct me (@matthewfeickert) to a sunpy nightly wheel for me to upload to create the package in the registry

Hopefully a dropbox link is ok: https://www.dropbox.com/scl/fi/mvauudyw1fihh1pegvy4n/sunpy-6.0.dev213-gbf6eb5884-cp310-abi3-linux_x86_64.whl?rlkey=vjlkynjuw1l5gmqlvq0310vix&dl=0
Our cron CI is having some issues at the moment.

[ ]  Verify that I have added you to the sunpy team "Group" on anaconda.org/scientific-python-nightly-wheels
[ ]  Verify that I have added the package scientific-python-nightly-wheels/sunpy to the sunpy team "Group"

Would a sunpy (non-personal) account be ok? https://anaconda.org/sunpy/

@nabobalis What matters is that the API token is associated with the account. Is the API token you currently use associated with the sunpy org account?
I used the wheel you linked me to create the project https://anaconda.org/scientific-python-nightly-wheels/sunpy, so once we have the info on the account+API token pair to use then you should be good to start uploading.

Would a sunpy (non-personal) account be ok? anaconda.org/sunpy

@nabobalis What matters is that the API token is associated with the account. Is the API token you currently use associated with the sunpy org account?

Yes it is.

I used the wheel you linked me to create the project anaconda.org/scientific-python-nightly-wheels/sunpy, so once we have the info on the account+API token pair to use then you should be good to start uploading.

@nabobalis Okay great. As long as you can see https://anaconda.org/scientific-python-nightly-wheels/groups/sunpy when logged in on the sunpy account then you should be good to go. :+1:

@nabobalis Okay great. As long as you can see anaconda.org/scientific-python-nightly-wheels/groups/sunpy when logged in on the sunpy account then you should be good to go. 👍

If I access that page, "I get You don't have permission to view this page." when I am logged into the sunpy account.

If I access that page, "I get You don't have permission to view this page." when I am logged into the sunpy account.

Hm. Let me look into that but, the sunpy account has all the permissions for the sunpy group as other accounts do, so even if you can't see the group for some reason you should be able to upload to it.

Our cron CI is having some issues at the moment.

Once your build job is working again can you try to do an upload and then report back here?

Will do. Thank you again.

So we changed our CI, I hope correctly to upload:
https://github.com/sunpy/sunpy/pull/7456
When our cronjob is back, we will hopefully find out if I added the correct token!

We restored our cron and it worked: https://anaconda.org/scientific-python-nightly-wheels/sunpy/files
Thank you again for giving us access. I have updated the job (https://github.com/sunpy/sunpy/pull/7457/files) to (hopefully) keep the lastest wheel only. Hopefully we will not fill up your storage space.

Great! And no worries about storage; as long as we delete old wheels we'll be fine.


[Feature]: Add 255. Verify Preorder Sequence in Binary Search Tree solution

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
255. Verify Preorder Sequence in Binary Search Tree
Given an array of numbers, verify whether it is the correct preorder traversal sequence of a binary search tree.
You may assume each number in the sequence is unique.
Consider the following binary search tree:
     5
    / \
   2   6
  / \
 1   3

Example 1:
Input: [5,2,6,1,3]
Output: false
Example 2:
Input: [5,2,1,3,6]
Output: true
Use Case

please assign me..

Benefits
No response
Add ScreenShots
No response
Priority
High
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[X] I have starred the repository

Hello @Ajay-Dhangar  please assign me..


Use Executioner Time Instead

I just realised that using serverTime() in the executioner result is unstable because sometimes testing happens after tested if the run is really fast. Can we use client time (the executioner) instead which is synced when the executioner starts up. It's not really affecting anything now because the frontend would just ignore testing when it sees tested.

Oh that's interesting. I encountered a problem a while ago where all the testing messages would be sent before the tested messages as everything was handled asynchronously. As checking the results would generally take longer, the testing messages resolved and sent before the tested messages did, hence the issue.
But this was fixed by messages requiring the previous message to already resolve before sending the next and I haven't had an issue since.
This does mean however that the time between messages is very small and could be what is causing the issue with ServerTime then

I see. I guess one thing you can try to do is to note down the time at a predictable and in order place and then handle everything afterward asynchronously.

Not sure why this is happening again. @Daniel5055 Can you look at it again? Btw it was running commit 768266e

The executioner now awaits for state updates and judge result additions for a message before sending the next message. I've also reverted back to using servertime now as that seems more fitting. This should fix the issue as it prevents race conditions yet this is quite hard to test.


Jenkins collector issue

I am trying to connect to my Jenkins instance which is using folder plugin. When I try with Jenkins default URL it is not collecting data from any jobs under different folders. and when I am giving complete folder path, Hygieia is recognizing the jobs but it is not collecting build data and I could see below errors at logs. How can I fix this issue?
2017-02-12 15:01:08,696 ERROR c.c.d.collector.DefaultHudsonClient - Unknown error in getting build details. URL=/job//job//job//job//1/
java.lang.NullPointerException: null
at com.capitalone.dashboard.collector.DefaultHudsonClient.getJsonArray(DefaultHudsonClient.java:281) ~[jenkins-build-collector-2.0.2-SNAPSHOT.jar!/:2.0.2-SNAPSHOT]
at com.capitalone.dashboard.collector.DefaultHudsonClient.addChangeSets(DefaultHudsonClient.java:230) ~[jenkins-build-collector-2.0.2-SNAPSHOT.jar!/:2.0.2-SNAPSHOT]
at com.capitalone.dashboard.collector.DefaultHudsonClient.getBuildDetails(DefaultHudsonClient.java:177) ~[jenkins-build-collector-2.0.2-SNAPSHOT.jar!/:2.0.2-SNAPSHOT]
at com.capitalone.dashboard.collector.HudsonCollectorTask.addNewBuilds(HudsonCollectorTask.java:193) [jenkins-build-collector-2.0.2-SNAPSHOT.jar!/:2.0.2-SNAPSHOT]
at com.capitalone.dashboard.collector.HudsonCollectorTask.collect(HudsonCollectorTask.java:95) [jenkins-build-collector-2.0.2-SNAPSHOT.jar!/:2.0.2-SNAPSHOT]
at com.capitalone.dashboard.collector.HudsonCollectorTask.collect(HudsonCollectorTask.java:32) [jenkins-build-collector-2.0.2-SNAPSHOT.jar!/:2.0.2-SNAPSHOT]
at com.capitalone.dashboard.collector.CollectorTask.run(CollectorTask.java:63) [core-2.0.2-SNAPSHOT.jar!/:2.0.2-SNAPSHOT]
at org.springframework.scheduling.support.DelegatingErrorHandlingRunnable.run(DelegatingErrorHandlingRunnable.java:54) [spring-context-4.1.7.RELEASE.jar!/:4.1.7.RELEASE]
at org.springframework.scheduling.concurrent.ReschedulingRunnable.run(ReschedulingRunnable.java:81) [spring-context-4.1.7.RELEASE.jar!/:4.1.7.RELEASE]
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) [na:1.8.0_101]
at java.util.concurrent.FutureTask.run(Unknown Source) [na:1.8.0_101]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(Unknown Source) [na:1.8.0_101]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source) [na:1.8.0_101]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [na:1.8.0_101]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [na:1.8.0_101]
at java.lang.Thread.run(Unknown Source) [na:1.8.0_101]

@eldojoseph Your log shows 2.0.2-SNAPSHOT. Try with the latest codebase and reopen if still an issue.

Thanks @satishc1 it worked fine.


ZmqPlugin incompatible to pyzmq 22.3.0 with delvewheel 0.0.12

Code of  _delvewheel_init_patch_ has changed signifcantly compared to 0.0.10 of delvewheel.
Anyone else faced this issue already? Or is there a patch available yet?
Using Nuitka <IP_ADDRESS>

Oppps, I think I was on the wrong track ... my Inno Setup Installshield didn't copy the .load-order-pyzmq-22.03.0 so I thought the ZmqPlugin was faultly. It seems the iscc.exe within wine doesn't see hidden files. -> closed.


Remove reference to an EC2 instance type.

Signed-off-by: dblock<EMAIL_ADDRESS>Description
Let's remove calling out an EC2 instance type, avoid AWS-specific things.
Check List

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

start gradle check

Would it makes sense to add another data point for comparison instead of removing it?

Would it makes sense to add another data point for comparison instead of removing it?

I had added this when I was revamping the developer guide, and it's not even correct as it takes <5m on that hardware. The actual time varies so dramatically setup by setup, and doesn't add anything useful to the developer IMHO. It's also a moving target as we will want to improve the time it takes to run these checks and will inevitably become out of date.

Would it makes sense to add another data point for comparison instead of removing it?

I've considered it and would rather not. I had added this when I was revamping the developer guide, and it's not even correct as it takes <5m on that hardware. The actual time varies so dramatically setup by setup, and doesn't add anything useful to the developer IMHO. It's also a moving target as we will want to improve the time it takes to run these checks and will inevitably become out of date.

Makes sense. I assume the original intent of that number being in there was so that folks didn't start doubting themselves when it took a long time.  So it might be worthwhile to put in a note to that effect (this can take some time, so don't panic).  But if you think folks have more patience/less self-doubt than me, feel free just to strike it ;)

Would it makes sense to add another data point for comparison instead of removing it?

I've considered it and would rather not. I had added this when I was revamping the developer guide, and it's not even correct as it takes <5m on that hardware. The actual time varies so dramatically setup by setup, and doesn't add anything useful to the developer IMHO. It's also a moving target as we will want to improve the time it takes to run these checks and will inevitably become out of date.

Makes sense. I assume the original intent of that number being in there was so that folks didn't start doubting themselves when it took a long time. So it might be worthwhile to put in a note to that effect (this can take some time, so don't panic). But if you think folks have more patience/less self-doubt than me, feel free just to strike it ;)

I'll strike it. You can clearly see that progress is being made as the workers are showing movement and logs, it's not like it's hanging with a spinner.


python37Packages.django-cors-headers: 2.4.0 -> 2.5.0

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/python3.7-django-cors-headers/versions.
meta.description for python37Packages.django-cors-headers is: '"Django app for handling server Cross-Origin Resource Sharing (CORS) headers"'.

Checks done (click to expand)

built on NixOS

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 2.5.0 with grep in /nix/store/md1v0w2m0wmi5631mgz3z695vhmr49mx-python3.7-django-cors-headers-2.5.0

directory tree listing: https://gist.github.com/220269cbe4f2e103a633227a5062c9f0

du listing: https://gist.github.com/f0c20442199452443aa2db190b5911c6

Rebuild report (if merged into master) (click to expand)

8 total rebuild path(s)
2 package rebuild(s)
2 x86_64-linux rebuild(s)
2 i686-linux rebuild(s)
2 x86_64-darwin rebuild(s)
2 aarch64-linux rebuild(s)
First fifty rebuilds by attrpath
python27Packages.django-cors-headers
python37Packages.django-cors-headers

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/md1v0w2m0wmi5631mgz3z695vhmr49mx-python3.7-django-cors-headers-2.5.0 \
  --option binary-caches 'https://cache.nixos.org/ https://r-ryantm.cachix.org/' \
  --option trusted-public-keys '
  r-ryantm.cachix.org-1:gkUbLkouDAyvBdpBX0JOdIiD2/DP1ldF3Z3Y6Gqcc4c=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(r-ryantm's Cachix cache is only trusted for this store-path realization.)
Or, build yourself:
nix-build -A python37Packages.django-cors-headers https://github.com/r-ryantm/nixpkgs/archive/2c8b352e4a38bafc88972966b00b261f6f100a4c.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/md1v0w2m0wmi5631mgz3z695vhmr49mx-python3.7-django-cors-headers-2.5.0
ls -la /nix/store/md1v0w2m0wmi5631mgz3z695vhmr49mx-python3.7-django-cors-headers-2.5.0/bin

cc @ivegotasthma for testing.

I've tested it out, works well. :+1:


Add more prominence to a few things on the OpenSearchCon 2024 NA landing page

Describe the bug
The Submit CFP and Register buttons are not prominent on our OSC NA 2024 page and I'd like to make them stand out more.
To Reproduce
Steps to reproduce the behavior:

Go to 'OpenSearchCon North America'

Expected behavior
I should be able to prominently see two Register Now buttons on this page, both saying "Register Now" with identical text and button style.
The "CFP" buttons on the page should read "Submit CFP" or "Submit Presentation" or "Submit Talk" or some such thing. They should use identical text and button style.
All of the aforementioned buttons should stand out from the other elements on the page, please change button background and text to highly contrasting with the rest of the page elements. Use one of the light red or yellow/gold colors for good contrast. Consider using two different colors for the two actions (one color for Register Now, another color for Submit Talk) - I'm not sure what that will look like so have a gander at it and make a call :)
Additional context

Thanks for the issue @dimwetoth ! I'll see what I can come up with. We've got some prominent buttons on there now - but I do agree that the wording isn't quite clear.
Is the idea that you have in mind to change the coloring and presentation of the buttons in the actual content of the page here?

Or on the button stacks on the left?


Add CSS Units Level 4

In 2017 and 2018 the following css units have been added to allow sizing based on various font metrics and are part of the official css spec now:
https://www.w3.org/TR/css-values-4/#relative-lengths

unit
relative to

cap
cap height (the nominal height of capital letters) of the element’s font

ic
average character advance of a fullwidth glyph in the element’s font, as represented by the “水” (CJK water ideograph, U+6C34) glyph

lh
line height of the element

rlh
line height of the root element

vi
1% of viewport’s size in the root element’s inline axis

vb
1% of viewport’s size in the root element’s block axis

Could we please add them also to caniuse?

Duplicate of #4087 or rather already available: https://caniuse.com/#search=css length

Thanks 👍


Breaking API changes in MuJoCo 3.2.3 (Sep 16, 2024)

I just faced this small issue on a fresh installation.
Breaking API changes

The runtime options mpr_tolerance and mpr_iterations were renamed to ccd_tolerance and ccd_iterations, both in XML and in the mjOption struct. This is because the new convex collision detection pipeline (see below) does not use the MPR algorithm. The semantics of these options remain identical.

Fixed in #218, thank you for pointing this out!

Actually, dm_control version has to be 1.0.23 (not just 1.0.22). 1.0.23 is released only on PyPI. It has not been "released" on their GitHub repo yet. This confused me. I fixed it in eedc04f (directly on the dev branch for the next release here).
Also, I'm fixing the version requirements for MuJoCo and dm_control strictly with == to avoid similar problems in the future. I will just manually update the versions from time to time.


Operation can't be reconstituted using google.core.Operation

OS type and version: Debian Linux Jessie
Python version: 2.7
Env info: docker image, python:2.7
google-cloud-python version: 0.26 (google-cloud-video-intelligence)
Stacktrace:
AttributeError                            Traceback (most recent call last)
<ipython-input-6-f1af42ad4d48> in <module>()
----> 1 op.poll()

/usr/local/lib/python2.7/site-packages/google/cloud/operation.pyc in poll(self)
    265             raise ValueError('The operation has completed.')
    266
--> 267         operation_pb = self._get_operation()
    268         self._update_state(operation_pb)
    269

/usr/local/lib/python2.7/site-packages/google/cloud/operation.pyc in _get_operation(self)
    231         """
    232         if self._from_grpc:
--> 233             return self._get_operation_rpc()
    234         else:
    235             return self._get_operation_http()

/usr/local/lib/python2.7/site-packages/google/cloud/operation.pyc in _get_operation_rpc(self)
    208         """
    209         request_pb = operations_pb2.GetOperationRequest(name=self.name)
--> 210         return self.client._operations_stub.GetOperation(request_pb)
    211
    212     def _get_operation_http(self):

AttributeError: 'VideoIntelligenceServiceClient' object has no attribute '_operations_stub'

Steps to reproduce

Create Google Video Intelligence Client.
Start a job using VideoIntelligence client.
Use the operation name returned on the polling future and the client from above to re-fetch the operation using google.cloud.Operation.
Call operion.poll()

Code example
n [1]: from google.cloud.gapic.videointelligence.v1beta1 import video_intelligence_service_client

In [2]: from google.cloud import operation

In [3]: client = video_intelligence_service_client.VideoIntelligenceServiceClient()

In [4]: op = operation.Operation('not-an-op-123', client)

In [5]: op
Out[5]: <google.cloud.operation.Operation at 0x7f7d00d47190>

In [6]: op.poll()

@lukesneeringer What does LRO stand for in this case?

@chemelnucfin "long-running operation"

@tseaver thanks.


Fix attributes that do not change being removed

Fix for #172 (old attribute names kept)

There are two PR #177 and #178 have the same title, which one you want to merge? or both?

Either one is good to me. It up to you which one want to be merged.

Merged #177, close this one.


fix: rollback to old naming convention for scraped images, otherwise the climate augmentation step fails dramatically

@maany merging this directly

@maany merged this directly


Battery / Mileage update failed: Traceback (most recent call last)

Hallo zusammen,
seit 2 Tagen habe ich folgende Fehlermeldung im Log und es wird nichts mehr angezeigt:

2020-04-04 21:57:01 WARNING (SyncWorker_2) [custom_components.renaultze.sensor] Battery update failed: Traceback (most recent call last):
File "/config/custom_components/renaultze/sensor.py", line 152, in update
jsonresult = self._vehicle.battery_status()
File "/usr/local/lib/python3.7/site-packages/pyze/api/kamereon.py", line 204, in battery_status
return self._get('battery-status')
File "/usr/local/lib/python3.7/site-packages/pyze/api/kamereon.py", line 184, in _get
response.raise_for_status()
File "/usr/local/lib/python3.7/site-packages/requests/models.py", line 941, in raise_for_status
raise HTTPError(http_error_msg, response=self)
requests.exceptions.HTTPError: 401 Client Error: Unauthorized for url: https://api-wired-prod-1-euw1.wrd-aws.com/commerce/v1/accounts/kmr/remote-services/car-adapter/v1/cars/VF1AG00000000000/battery-status
2020-04-04 21:57:01 WARNING (SyncWorker_2) [custom_components.renaultze.sensor] Mileage update failed: Traceback (most recent call last):
File "/config/custom_components/renaultze/sensor.py", line 159, in update
jsonresult =  self._vehicle.mileage()
File "/usr/local/lib/python3.7/site-packages/pyze/api/kamereon.py", line 217, in mileage
return self._get('cockpit')
File "/usr/local/lib/python3.7/site-packages/pyze/api/kamereon.py", line 184, in _get
response.raise_for_status()
File "/usr/local/lib/python3.7/site-packages/requests/models.py", line 941, in raise_for_status
raise HTTPError(http_error_msg, response=self)
requests.exceptions.HTTPError: 401 Client Error: Unauthorized for url: https://api-wired-prod-1-euw1.wrd-aws.com/commerce/v1/accounts/kmr/remote-services/car-adapter/v1/cars/VF1AG00000000000/cockpit

Noch jemand oder liegt es an meinem Account?

I have the same issue.
Including the following:

HTTPError: 504 Server Error: Gateway Time-out for url: https://api-wired-prod-1-euw1.wrd-aws.com/commerce/v1/accounts/kmr/remote-services/car-adapter/v1/cars/VF1AGxxxxxxxxxxxx/cockpit

HTTPError: 500 Server Error: Internal Server Error for url: https://api-wired-prod-1-euw1.wrd-aws.com/commerce/v1/accounts/kmr/remote-services/car-adapter/v1/cars/VF1AGxxxxxxxxxxxx/cockpit

HTTPError: 403 Client Error: Forbidden for url: https://api-wired-prod-1-euw1.wrd-aws.com/commerce/v1/accounts/kmr/remote-services/car-adapter/v1/cars/VF1AGxxxxxxxxxxxx/cockpit

HTTPError: 401 Client Error: Unauthorized for url: https://api-wired-prod-1-euw1.wrd-aws.com/commerce/v1/accounts/kmr/remote-services/car-adapter/v1/cars/VF1AGxxxxxxxxxxxx/cockpit

Bonjour,
On vient de me dire que Renault a fermé son ancien serveur d’authentification la semaine dernière.
Pourriez vous mettre à jour le GitHub pour qu’il marche avec le nouveau serveur Renault?
Le problème vient de la...
Merci.

Hi,
Indeed, Renault removed the v1 endpoints over the weekend, and we need to move to the v2 endpoints (available in pyze 0.4.0).
If someone wants to provide a PR, I'll happilly merge or I'll do it myself later this week.

Ok, i've changed the code - can you give me the rights to provide a PR?
In my environment it works now without problems. ;-)

You should fork directly from Github, then push your branch to your Github fork, then request PR from your Github fork to this repository.
If not, you'll have to send me the file or the diff and I will merge it.

Merged PR #23


Split adjust estimates

Adds logic that split adjusts estimates. Also adds relevant tests.

Coverage increased (+0.03%) to 87.034% when pulling ca4aba4f5e2619dde1c2c56e7c358737f7d34288 on split_adjust_estimates into f1929342d90f36317044f62f0a940b987fb77824 on master.

Coverage increased (+0.03%) to 87.034% when pulling 4d3e9d171f6a4392d891efda3925d8b1ef9c1600 on split_adjust_estimates into f1929342d90f36317044f62f0a940b987fb77824 on master.

Coverage increased (+0.03%) to 87.034% when pulling cd9f9ff24732f3e2f13b72f50ee73b5355e53475 on split_adjust_estimates into f1929342d90f36317044f62f0a940b987fb77824 on master.

Coverage increased (+0.03%) to 87.034% when pulling c5e9a9e28c8e27d8f6afbd31c6a6b5847900ff19 on split_adjust_estimates into f1929342d90f36317044f62f0a940b987fb77824 on master.

Coverage increased (+0.03%) to 87.027% when pulling 1e828a85f1d63ff0e8f6a91cf6528687f209cfc5 on split_adjust_estimates into f1929342d90f36317044f62f0a940b987fb77824 on master.

Coverage increased (+0.03%) to 87.031% when pulling 1467e1efb882646b6fbbf6592616933b2f4b8e3a on split_adjust_estimates into f1929342d90f36317044f62f0a940b987fb77824 on master.

Coverage increased (+0.03%) to 87.031% when pulling 1467e1efb882646b6fbbf6592616933b2f4b8e3a on split_adjust_estimates into f1929342d90f36317044f62f0a940b987fb77824 on master.

Coverage increased (+0.03%) to 87.035% when pulling f5787522f3ae91b83bb42c9e9825b85b79599c21 on split_adjust_estimates into f1929342d90f36317044f62f0a940b987fb77824 on master.

Coverage increased (+0.08%) to 87.077% when pulling afcdafd6057f571d4bea5b2e865e834164845d3b on split_adjust_estimates into f1929342d90f36317044f62f0a940b987fb77824 on master.

Coverage increased (+0.05%) to 87.031% when pulling d687a36000893675e8fc0ac911fd388a5bc9b6df on split_adjust_estimates into 2c819a672bfcffbd08996ff12ef7a02b37a6e50e on master.

Coverage increased (+0.09%) to 87.072% when pulling 17da473d64f39d4b2bb9622edd743c0eaab485d6 on split_adjust_estimates into 2c819a672bfcffbd08996ff12ef7a02b37a6e50e on master.

Coverage increased (+0.09%) to 87.072% when pulling 9f995d9bdb570cd4d991b5e59183fc533cef0fc1 on split_adjust_estimates into 2c819a672bfcffbd08996ff12ef7a02b37a6e50e on master.

Coverage increased (+0.05%) to 87.03% when pulling 9f995d9bdb570cd4d991b5e59183fc533cef0fc1 on split_adjust_estimates into 2c819a672bfcffbd08996ff12ef7a02b37a6e50e on master.

Coverage increased (+0.07%) to 87.047% when pulling a6da8fe6160f9f55a9dec59fd355dd812c5af0a3 on split_adjust_estimates into 2c819a672bfcffbd08996ff12ef7a02b37a6e50e on master.

Coverage decreased (-0.2%) to 86.73% when pulling 9c902accbb87e8f1f751b4dba3a0bb939456f0f7 on split_adjust_estimates into 2c819a672bfcffbd08996ff12ef7a02b37a6e50e on master.

Coverage increased (+0.1%) to 87.095% when pulling 17222c73c2f554859c3acb7e9de2ce637a2d47ea on split_adjust_estimates into 2c819a672bfcffbd08996ff12ef7a02b37a6e50e on master.

Coverage increased (+0.1%) to 87.136% when pulling b33de14c8b7c19892cf836158e53c026a0474424 on split_adjust_estimates into 8b8b4a811859e07615eab3db790652553bed460e on master.

Coverage increased (+0.1%) to 87.13% when pulling 325cb5894298d5b433c5f8fbfe023e639f16c913 on split_adjust_estimates into 8b8b4a811859e07615eab3db790652553bed460e on master.

Coverage increased (+0.1%) to 87.13% when pulling a22664956e188374d97f5a8035a7daa0f2ac9cda on split_adjust_estimates into 8b8b4a811859e07615eab3db790652553bed460e on master.

Coverage increased (+0.1%) to 87.13% when pulling 653d71ba983e72ebc513b16e857de6af9e1626c3 on split_adjust_estimates into 8b8b4a811859e07615eab3db790652553bed460e on master.

Coverage increased (+0.1%) to 87.121% when pulling a8a6fb0b03e496573233082012e52fcac61cb801 on split_adjust_estimates into 515db18793422d280d2dce8bb6512583bee06cbc on master.

Coverage increased (+0.1%) to 87.121% when pulling 757e1c6367fa10d19154d58fdbe6e069ae7e3459 on split_adjust_estimates into 515db18793422d280d2dce8bb6512583bee06cbc on master.

Coverage increased (+0.1%) to 87.121% when pulling 757e1c6367fa10d19154d58fdbe6e069ae7e3459 on split_adjust_estimates into 515db18793422d280d2dce8bb6512583bee06cbc on master.


Adding tests to ensure plugins for container monitoring are running fine.

Adding tests to make sure

omsagent daemonset is running
omsagent replicaset is running
kubepodinventory plugin is processing data successfully
kubenodeinventory plugin is processing data successfully

/assign @jackfrancis

Hi @rashmichandrashekar, the unit tests are failing at the lint step (you can run make test-style locally to repro)

/lgtm


Exclude uri?

Resolves warning with recent clojurescript builds
WARNING: uri? already refers to: cljs.core/uri? being replaced by: cognitect.transit/uri? at line 332 resources\public\js\dev\cognitect\transit.cljs
Ref Issue #39

Looks like this was fixed some time ago.


Console log error when navigating to container dashboard

ActionController::RoutingError (No route matches [GET] "/container_dashboard/%7B%7BproviderTypeIconImage%7D%7D"):
actionpack/lib/action_dispatch/middleware/debug_exceptions.rb:53:in `call'
actionpack/lib/action_dispatch/middleware/show_exceptions.rb:31:in `call'
railties/lib/rails/rack/logger.rb:36:in `call_app'
railties/lib/rails/rack/logger.rb:26:in `call'
...

@simon3z this might be core UI, can you take a look and see if this should be on @dclarizio

@zeari can you take a look?

@miq-bot add_label providers/containers, bug

@simon3z sure
@yaacov im fairly certain this is what we encountered about inserting empty data to those image/pod trend charts

it's a typo in:
app/views/shared/views/_show_containers_dashboard.html.haml
we used src =>
be we shuld have used ng-src =>
bad:
%img.provider-icon-large{"src" =>"{{providerTypeIconImage}}"}
god:
%img.provider-icon-large{"ng-src" =>"{{providerTypeIconImage}}"}

@miq-bot assign yaacov

bad:
%img.provider-icon-large{"src" =>"{{providerTypeIconImage}}"}
good:
%img.provider-icon-large{"ng-src" =>"{{providerTypeIconImage}}"}

@yaacov I stand corrected!


Window management

Found this module and it looks awesome! Would love window management stuff such as:

list app windows
bring window to front / focus
close window
bonus pts if we could peer into browser tabs :)

If this is something you would like to have but not do all yourself, I might be able to contribute some of the above or at least help out.

This is something I also want but its not a priority at the moment. Feel free to work on it if you want!

@octalmage  would this also include control over Virtual Desktops (Spaces)? Could be nice to add this in with window management.
I recently created a basic package (C++) to do this in W10, for a side-project I was doing with robotjs, based on some nice write-ups and samples (repo with src/links for interested). But, it would probably be nicer if this functionality was available through robotjs desktop automations.
Might be harder to get this right on Linux and play nice with the different desktop environments, I think, ex. Elementary handles desktops differently than Ubuntu. wmctrl seems to do a good job though. For OSX I have no idea.

A while back I started working on some code for Mac. I was able to get a list of windows and move one from Node. But I want to have the features for each os implemented before it's released, and that's a pretty large project. My current focus is on the screen/bitmap related code, but it's something I'd love to see down the road.
As far as controlling virtual desktops, I'm not sure if that would be in scope for this project. I want to keep the API and features consistent for each OS, if it could be done this way then it could be an option.

Would love to see this happen -- if only just a list of windows and the active window.

There is this:
https://github.com/octalmage/active-window
It's not great, but it works!

Ah ha! Thank you!

+1 would love to see support


animationend and animationstart not in lib.dom.d.ts ?

TypeScript Version:  2.6.2
It would seem that the HTMLElementEventMap does not have animationstart nor animationend yet there is an AnimationEvent type. Is this intentional ? The technology is starting to be pretty supported across browsers.

I believe this is fixed now
https://github.com/microsoft/TypeScript/blob/189c2b9e4a4fc35f8a66c4796c0653229c71829d/lib/lib.dom.d.ts#L6378
HTMLElementEventMap extends GlobalEventHandlersEventMap which does indeed have animationstart/animationend

Just looking at old issues; yes, this is fixed as of #25944.


Use Generic Name for SimplePool Connection Threads (1.6.x)

Issue: https://github.com/networknt/light-4j/issues/2089
Currently SimplePool connection threads are named either "Callback-HTTP11" or "Callback-HTTP11" depending on the type of connection.
However, since this threadpool is only named ONCE, then the name of all SimplePool connection threads is based on the first type of connection that SimplePool was asked to make (HTTP/1.1 or HTTP/2).
This can cause misleading messages in the logs, since if subsequent calls to the pool create different connection types, then the thread name and connection type won't match.
E.g.: If an HTTP/1.1 connection is the first connection the pool makes, then any subsequent HTTP/2 connection threads will have the name "Callback-HTTP11".

@miklish Are we ready to merge this PR? Thanks.

@stevehu yes this can be merged thank you


EJS extended

This will help with needing to pass stuff into the template
other changes

[ ] Every newly introduced function needs to have a documentation
[ ] The impure tests via nix run .#offchain:test were run and all are passing.
[ ] Where applicable, grammar, punctuation, and spelling within code and comments should be plausibly correct.
[ ] The issue(s) that the work is addressing should be linked in the PR description.
[ ] Any significant changes beyond what's clear from the linked issue(s) are documented in the PR description

@toastal @leomayleomay Looks like there are some conflicts from a recent merge. Will review after they're resolved.


REFACTOR: Renaming filter into filter_order

This PR renames order to filter_order to make it more meaningful.

Could you please avoid adding the link to tfs (at most refer the issue number).
If possible, could you provide a better explanation as to why you are proposing this changes ?

Could you please avoid adding the link to tfs (at most refer the issue number). If possible, could you provide a better explanation as to why you are proposing this changes ?

The link is removed.

Thanks @ramin4667, can you explain why this change is more meaningful ? That is not clear to me

Member

@SMoraisAnsys The rest of the attributes start with filter_***, and the user could mistakenly use filter_order instead of order. This change makes attribute names consistent.


Add additional tricks

This adds 5 new tricks for OoT and 6 new tricks for MM, bringing the total for both games to 12. Most of these tricks are simple one-line implementations that do mostly very obvious things. The only unintuitive one is the ISTT Eyegore Skips which includes the recoil flip from the updraft room, the Deku spin or jump slash down to the pre-Gomess ledge, and the Goron rolls from the Eyegore bridge down to the ledges below. This room is just so many tricks rolled into one that heavily impacts how strong players approach the dungeon so I chose this approach to encapsulate it all. The Eyegore snipe is not included due to not being compatible properly with CSMC (to my knowledge).

Looks good!
Ideally the foolish item heuristic you added should take hints into account, but that can wait.


Add test for graceful stack upgrades

Summary

Part of #651, add integration test that ensures graceful stack upgrades are successful.
Per discussion on issue, no changes were needed to the Go language family buildpacks to enable graceful stack upgrades. However, a test has been added solely to ensure that this behaviour is not broken in the future, either by a new version of Go, or changes to the buildpack logic.
Use Cases

Checklist

[X] I have viewed, signed, and submitted the Contributor License Agreement.
[X] I have linked issue(s) that this PR should close using keywords or the Github UI (See docs)
[X] I have added an integration test, if necessary.
[X] I have reviewed the styleguide for guidance on my code quality.
[X] I'm happy with the commit history on this PR (I have rebased/squashed as needed).

stack ID check makes sense!
Thank you for fixing the app, those log lines were some leftovers I forgot about while messing around with the exploration work
running in parallel makes sense to me
Thanks frankie!

@sophiewigmore re: the stack ID check, I hadn't considered that my change would make the tests run on tiny and base. good point. I'd be satisfied with a check that says "if the stack is bionic base, run the upgrade tests". That way, users bringing their own bionic base builder can still run the tests.
This means we won't test upgrading from an arbitrary stack to the jammy stack. I think that's reasonable, because we're only guaranteeing Ubuntu Bionic --> Ubuntu Jammy graceful upgrades at the moment.
I'll put in a commit momentarily.

Thank you!!


Feature/change eventbus to typed service poc

Related issues

closes #
Short description and why it's useful

It's typed version of previous EventBus. If we add payload and eventNames types to types.ts we can have more predictable events. What you think about this? :)
interface Events {
  'modal-show': string,
  [key: string]: any
}

Which environment this relates to
Check your case. In case of any doubts please read about Release Cycle

[x] Test version (https://test.storefrontcloud.io) - this is a new feature or improvement for Vue Storefront. I've created branch from develop branch and want to merge it back to develop
[ ] RC version (https://next.storefrontcloud.io) - this is a stabilisation fix for Release Candidate of Vue Storefront. I've created branch from release branch and want to merge it back to release
[ ] Stable version (https://demo.storefrontcloud.io) - this is an important fix for current stable version. I've created branch from hotfix or master branch and want to merge it back to hotfix

Upgrade Notes and Changelog

[x] No upgrade steps required (100% backward compatibility and no breaking changes)
[ ] I've updated the Upgrade notes and Changelog on how to port existing VS sites with this new feature

IMPORTANT NOTICE - Remember to update CHANGELOG.md with description of your change
Contribution and currently important rules acceptance

[x] I read and followed contribution rules

hmm looks better with a class and typings, but as I know we want to get rid of the EventBus. Even  now we don't use it in the new code and when we touch existing one, we try to remove EventBus calls as much as it is possible. Correct me if I'm wrong @filrak @patzick ?

how will you deal with many listeners? Events are great to decouple code. We don't need to check if any module is listening. To get the same effect, we would have to create coupled method calls.
someEvent(){
this.callMethodFromModule1()
this.callMethodFromModule2()
...

Were trying to replace EventBus with hooks proposed by @filrak https://github.com/DivanteLtd/vue-storefront/pull/2330
Example: #3438
It’s up to @filrak to decide if we’re closing or accepting this PR

Ok, now I see it. Hooks look very cool :) Maybe this PR is unnecessary

@gibkigonzo ok, it's nothing personal but I'm closing this PR as it duplicates the Hooks  :)


Suppress window resizing to the same size in vim.exe

In some terminal apps, requesting the same window size, the display will be corrupted.
(From vim_use discussion)

Codecov Report

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

@@            Coverage Diff             @@
##           master    #5343      +/-   ##
==========================================
- Coverage   82.25%   82.23%   -0.02%
==========================================
  Files         134      134
  Lines      147578   147578
==========================================
- Hits       121389   121361      -28
- Misses      26189    26217      +28

Impacted Files
Coverage Δ

src/ui.c
71.12% <0%> (-1.29%)
:arrow_down:

src/profiler.c
94.11% <0%> (-0.57%)
:arrow_down:

src/gui.c
63.78% <0%> (-0.52%)
:arrow_down:

src/if_xcmdsrv.c
86.17% <0%> (-0.18%)
:arrow_down:

src/sign.c
94.51% <0%> (-0.18%)
:arrow_down:

src/gui_gtk_x11.c
58.11% <0%> (-0.1%)
:arrow_down:

src/terminal.c
81.74% <0%> (-0.04%)
:arrow_down:

src/os_unix.c
63.37% <0%> (ø)
:arrow_up:

src/viminfo.c
90.55% <0%> (+0.32%)
:arrow_up:

Continue to review full report at Codecov.

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

I'll include this, but can a few people check that it doesn't introduce a new problem?

I will check with Windows 7 / Windows Vista from now on.

I used Windows 7 / Vista.
The test in testdir/ seems to have passed.
I saw the situation with :winsize, but it looks okay.


Lifecycle management for dependent resources in terraform plugin

Today, multiple resources can be defined in a single instance definition (for example, a VM resource and a volume resource).  These 2 resources will be included in a single .tf.json file and terraform handles the provision ordering.
This approach helps on the initial provision since these dependent resources are coupled together. However, when performing a rolling update, Infrakit will remove the single .tf.json file and then create a new one — this causes BOTH the VM and the associated volume to be destroyed and then replaced.
We need a mechanism to decouple the volume so that, during a rolling update, the volume will remain and only the VM will be destroyed and replaced.

I think at a minimum, we want to be able to have resources written in different .tf.json files so that their lifecycle can be independently managed.  For example, when the instance is to be terminated, we can simply remove its corresponding tf.json file without destroying, say, a volume that was provisioned with it but is intended to survive across instance terminations.
In the terraform plugin, we have a map of resource types and resource objects and currently everything is written as a single file named by the instance id -- https://github.com/docker/infrakit/blob/master/examples/instance/terraform/plugin.go#L485
Here the instance id originally had the connotation of a compute instance, but in the most general sense, the id is just a per-invocation identifier of the plugin.  So if the plugin has a template of N resources that are all related to each other, a single file of infrakit-xxxxx.tf.json would contain N resources.
So this is my suggestion:

let's come up with a way to support grouping of resources in separate files....  for example, I should be able to say something like:

    {
         "fileprefix1" : [ "softlayer_virtual_guest", "softlayer_ssh_key" ],
         "fileprefix2" : [ "softlayer_volume" ]
     }

This basically says, "put the resource types softlayer_virtual_guest and softlayer_ssh_key in a file named fileprefix1-<instance_id>.tf.json, while resource of the type softlayer_volume is written to a separate file fileprefix2-<instance_id>.tf.json.
To do this I think we can add a field here (say, Related or something)
https://github.com/docker/infrakit/blob/master/examples/instance/terraform/plugin.go#L145

Change the code here https://github.com/docker/infrakit/blob/master/examples/instance/terraform/plugin.go#L462 to write out multiple files based on the rule above.

Change the way DescribeInstances and Destroy work...  Since now we have multiple files, and not all files are to be searched during describe and removed during destroy, we'd need a way to associate the methods describe and destroy to the file prefixes.   Maybe we can add another field like above, but for associating verbs to file prefixes.

Thanks for the response @chungers. Can we get a concrete example of the new schema for the Properties of instance-terraform. For example, let’s use https://github.com/docker/infrakit/blob/master/examples/instance/terraform/plugin_test.go#L54-L93. This definition is basically:
{
	"resource" : {
		"softlayer_file_storage": {
			"worker_file_storage": {…}
		},
		"softlayer_block_storage": {
			"worker_block_storage": {…}
		},
		"softlayer_virtual_guest" : {
			"host": {…}
		}
	}
}

And this creates a single file like
# instance-12345.tf.json
{
    "resource": {
      "softlayer_block_storage": {
        "instance-12345-worker_block_storage": {…}
      },
      "softlayer_file_storage": {
        "instance-12345-worker_file_storage": {…}
      },
      "softlayer_virtual_guest": {
        “instance-12345”: {…}
      }
    }
}

Should the updated definition be:
{
	“<file-prefix1>”: [“softlayer_virtual_guest”],
	“<file-prefix2>”: [“softlayer_file_storage”, “softlayer_block_storage”],
	"resource" : {
		"softlayer_file_storage": {
			"worker_file_storage": {…}
		},
		"softlayer_block_storage": {
			"worker_block_storage": {…}
		},
		"softlayer_virtual_guest" : {
			"host": {…}
		}
	}
}

This would then create 2 files:
# <file-prefix1>-instance-12345.tf.json
{
    "resource": {
      "softlayer_virtual_guest": {
        “instance-12345”: {…}
      }
    }
}
# <file-prefix2>-instance-12345.tf.json
{
    "resource": {
      "softlayer_block_storage": {
        "instance-12345-worker_block_storage": {…}
      }
      "softlayer_file_storage": {
        "instance-12345-worker_file_storage": {…}
      }
    }
}

Is this what you are thinking?
Also, do you think that we need a top-level JSON key to identify the file groupings in the instance Properties (ie, a groupings key that is peer to resource)? This would then look like:
{
	“groupings”: {
		“<file-prefix1>”: [“softlayer_virtual_guest”],
		“<file-prefix2>”: [“softlayer_file_storage”, “softlayer_block_storage”]
	},
	"resource" : {
		"softlayer_file_storage": {
			"worker_file_storage": {…}
		},
		"softlayer_block_storage": {
			"worker_block_storage": {…}
		},
		"softlayer_virtual_guest" : {
			"host": {…}
		}
	}
}

@kaufers

Also, do you think that we need a top-level JSON key to identify the file groupings in the instance Properties (ie, a groupings key that is peer to resource)? This would then look like:

{
	“groupings”: {
		“<file-prefix1>”: [“softlayer_virtual_guest”],
		“<file-prefix2>”: [“softlayer_file_storage”, “softlayer_block_storage”]
	},
	"resource" : {
		"softlayer_file_storage": {
			"worker_file_storage": {…}
		},
		"softlayer_block_storage": {
			"worker_block_storage": {…}
		},
		"softlayer_virtual_guest" : {
			"host": {…}
		}
	}
}

That's exactly what I was talking about.  Thank you.
We also need to have a way to specify which file to look for in the case of DescribeInstances and Destroy.   In the code there's a function to look for VMs like here.   This code can now be made generic if we know which file to look for and for what resource type we should be used for listing and destroy.   Essentially with this support the terraform plugin can be an instance plugin of anything terraform can provision, not just for compute -- plus it can manage related resources that may have separate lifecycle.
As a aside, currently DescribeInstances doesn't take into account of other resource objects -- it just lists VM instances.  It'd be nice to get a list of everything...  maybe we can do that as Properties in the instance.Description.

@chungers Yes, this makes sense. How about something like this:
{
  "lifecycle": [
    ["softlayer_virtual_guest"],
    ["softlayer_file_storage", "softlayer_block_storage"]
  ],
  "actions" : {
    "describe" : ["softlayer_virtual_guest", "softlayer_file_storage", "softlayer_block_storage"],
    "destroy" : ["softlayer_virtual_guest"]
  },
  "resource" : {
    "softlayer_file_storage": {
      "worker_file_storage": {...}
    },
    "softlayer_block_storage": {
      "worker_block_storage": {...}
    },
    "softlayer_virtual_guest": {
      "host": {...}
    }
  }
}

lifecycle defines the groups of resources that map to individual JSON files; IMO the user shouldn't care about how we name the files so the value is just a list of resource type lists.
actions defines the behavior (as you stated) and it seems that we only need resource types here; can you think of anything else we'd need? We should be able to parse all files and pull the matching resource types.

IMO this is more refined but it does put the onus on the plugin to determine a naming convention and then we need to parse all files for the chosen action.
One issue that I can think of related to #562. Depending on how that one gets solved, I can envision defining both the shared and dedicated volume in the managers definition. If so, we'd want to be able to destroy a specific softlayer_file_storage resource (ie, the dedicated one) while leaving the shared one; in this case only defining the resource type in the actions is too coarse.
Thoughts?

@kaufers I like your proposal; I think it's much more refined than the example I gave.
I agree, however, that this design may need a bit of tweak to support #562.  In essence, a instance of a given resource type (e.g. softlayer_block_storage) can have different purposes: dedicated to a compute instance or shared.  So the actions that be taken against the instance are different -- destroy along with the compute instance in the former and preserve in the latter case.
I think instead of introducing new top level fields like lifecycle or grouping how about we just add a couple of fields to the resource struct to annotate what can be done for each resource?  Then the terraform plugin can look at the flags for each resource and group them into different files and operate on them accordingly (list and/or destroy)?   We can always remove these extra fields before feeding that to terraform so it won't complain.  If the extra fields are not provided, then every resource type instances get lumped into the same file.
So for example, previously we have
{
  "resource" : {
    "softlayer_file_storage": {
      "worker_file_storage": {...}
    },
    "softlayer_block_storage": {
      "worker_block_storage": {...}
    },
    "softlayer_virtual_guest": {
      "host": {...}
    }
}

Now it becomes
{
  "resource" : {
    "softlayer_file_storage": {
      "worker_file_storage": {...},
      "persistent" : false,   # <---- new extra field, if not set, defaults to false per golang zero value.
      "main" : false,  # this resource's id is not used as instance.ID when describing resources.
    },
    "softlayer_file_storage": {
      "shared_manager_storage": {...},   # <-- here we have a same resource type but now shared
      "persistent" : true,   # <---- write this resource to a separate file not touched during destroy
    },   # note here there's no `main` field.  Defaults to false
    "softlayer_block_storage": {
      "worker_block_storage": {...}   # no `persistent` nor `main`...  so write to same file that will be removed when destroying instances.
    },
    "softlayer_virtual_guest": {
      "host": {...},
      "persistent" : false,   # <---- this is the extra field
      "main" : true  # <-- means we'd search for this resource type and use its id for describe instances
    }
}

So we can get away with just two new booleans... persistent and main.  Persistent controls the behavior of destroy -- so we'd only need two files since it's a binary value -- let's just name them infrakit-<generated_id>.tf.json and infrakit-persistent-<generated_id>.tf.json.
When we describe instances, we open two files for each "instance" -- its destroyable and persistent versions.  We gather the resource objects and depending on which resource has the main set to true, we use that instance's ID as the instance id when returning the results of DescribeInstances.
When we destroy, we remote the non-persistent file for every instance.
As for this mapping of what resource is main/persistent, we can store that in memory, since that information can be reconstituted every time a Validate is called and we only need to cache that mapping information for describe and destroy calls which get nothing or only the id's as input.
Thoughts?

@chungers I like this new approach but I think that there is one more use case that we might want to consider: using dedicated volumes for workers. In this flow, we'd create a dedicated volume for worker-x and, if that worker died, the replacement worker would be associated with the existing volume (that was being used by worker-x). A few questions/comments on this use case:

Do you think that this is even valid?
We'd have think about how we name the instances so that we can correlate a worker to a specific volume (and ensure that rolling updates wire things up correctly). Maybe we change the naming convention from instance-<ts>.tf.json to something like instance-n.tf.json (where n is just a count that is incremented/decremented on scale up/down); by using n we'd simply have volume_n that would always map to instance-n (even when instance-n has a rolling update applied).

If this is valid, then how about supporting 3 values for a new @persistent property:

global: This resource is completely decoupled from the instance (like a shared volume) and would not be removed if the instance is removed.
dedicated: This resource is loosly coupled to a specific instance (ie, worker-n) and would be destroyed on scale down (only if worker-n was being removed) but would not be destroyed on a rolling update.
default: This resource is tightly coupled with the lifecycle of the resource and it is destroyed/recreated on a rolling update.

I'm also trying to understand the motivation for not included everything in DescribeInstances. Why wouldn't we want to include everything? Is it because a global resource may map to multiple resources?
Thanks!

@kaufers

Do you think that this is even valid?

Yes.  This is actually a really good point.  Currently the group controller will naively destroy an instance in a rolling update without regard to anything that's associated to the instance.   More specifically, the context is there (ie. this destroy for a rolling update) but that context isn't expressed in the SPI by the time the instance plugin is invoked.
In the flavor plugin, there's the notion of a 'Drain', but it has a higher-level semantic than what to do with the infrastructure resources like keeping a volume around or destroy it along with the instance.  So doing these low-level resource type of things doesn't make sense inside a Flavor plugin.
So, your insight leads me to think that we should change the SPI to give more context to certain operations -- in particular Destroy.  Even Provision can use a context -- so that it knows to reattach resources for those that are, as you call it below, "dedicated", in context of an update.

We'd have think about how we name the instances so that we can correlate a worker to a specific volume (and ensure that rolling updates wire things up correctly). Maybe we change the naming convention from instance-.tf.json to something like instance-n.tf.json (where n is just a count that is incremented/decremented on scale up/down); by using n we'd simply have volume_n that would always map to instance-n (even when instance-n has a rolling update applied).
If this is valid, then how about supporting 3 values for a new @persistent property:

global: This resource is completely decoupled from the instance (like a shared volume) and would not be removed if the instance is removed.
dedicated: This resource is loosely coupled to a specific instance (ie, worker-n) and would be destroyed on scale down (only if worker-n was being removed) but would not be destroyed on a rolling update.
default: This resource is tightly coupled with the lifecycle of the resource and it is destroyed/recreated on a rolling update.
I'm also trying to understand the motivation for not included everything in DescribeInstances. Why wouldn't we want to include everything? Is it because a global resource may map to multiple instances?

I like these three "enums" that you have defined.  I think they capture a wide swath of use cases in a general way.
While we can't support all these semantics properly until we make changes to the instance SPI, I think we can definitely start that with the Terraform plugin and implement using the approach you mentioned.   One thing we should look at is the handling of 'dedicated' resources because it may require creation / removal of some "attachment" type of object / structure that represent association of two resources in Terraform.  For example, on AWS there's a volume attachment object that needs to be created / destroyed.  So the handling of these pseudo resource objects need a bit of design and care.

@chungers I started implementing the .tf.json file decomposition based on the @persistence property.
What do you think about scoping global resources to the group that they are associated with?  This way we (in theory) could destroy them when the group is removed (analogous to removing dedicated resources on scale down). This would mean that global resources could only be created from a group commit (is this an acceptable restriction?).
Here's a concrete example (with a few bogus resource types to show the groupings):
{
  "resource" : {
    "softlayer_virtual_guest": {
      "host": {...}
    }
    "softlayer_file_storage": {
      "worker_fs": {
        "@persistence": "dedicated",
        ...
      }
    },
    "softlayer_block_storage": {
      "shared_block_storage": {
        "@persistence": "global",
        ...
      }
    },
    "another-dedicated-resource-type": {
      "another-dedicated-name": {
        "@persistence": "dedicated",
        ...
      }
    },
    "another-default-resource-type": {
      "another-default-name": {...}
    }
}

This created 3 files:
$ ls -l
total 24
-rw-r--r--  1 kaufer  staff  296 Jun  2 14:48 dedicated-1234.tf.json
-rw-r--r--  1 kaufer  staff  170 Jun  2 14:48 global-mygroup.tf.json
-rw-r--r--  1 kaufer  staff  330 Jun  2 14:48 instance-1234.tf.json

$ cat instance-1234.tf.json
{
    "resource": {
      "another-default-resource-type": {
        "instance-1234-another-default-name": {...}
      },
      "softlayer_virtual_guest": {
        "instance-1234": {
          "tags": {
            "infrakit.group": "mygroup"  <-- NOTE required tag for @global resources
          },
          ...
        }
      }
    }
  }

$ cat dedicated-1234.tf.json
{
    "resource": {
      "another-dedicated-resource-type": {
        "instance-1234-another-dedicated-name": {...}
      },
      "softlayer_file_storage": {
        "instance-1234-worker_fs": {...}
      }
    }
  }

$ cat global-mygroup.tf.json
{
    "resource": {
      "softlayer_block_storage": {
        "mygroup-shared_block_storage": {...} . <-- NOTE prefix is `infrakit.group` tag on main VM
      }
    }
  }

The file naming conventions are:

default resources: <id>.tf.json -- instance-1234.tf.json
dedicated resources: dedicated-<id-ts>.tj.json -- dedicated-1234.tf.json
global resources: global-<groupId>.tf.json -- global-mygroup.tf.json

The resource naming conventions are:

Main VM resource: <id> -- instance-1234
Other default resources: <id-ts>-<givenName> -- 1234-another-default-name
dedicated resources: ^ same
global resources: <groupId>-<givenName> -- mygroup-block-storage

What do you think about scoping global resources to the group that they are associated with? This way we (in theory) could destroy them when the group is removed (analogous to removing dedicated resources on scale down). This would mean that global resources could only be created from a group commit (is this an acceptable restriction?).

I like the idea but with a slight twist...  how about we label the resources using the following convention:
if Instance B1 of type B is to be attached to instance A1 of A, we label A1 with infrakit.attach which has a list of resource names to attach.  In this case, infrakit.attach=B1,name_of_something_else
Which file the resource should belong.... we can do with a field in the spec called scope instead of the @persistence.  The following values are possible for a scope field:

@default
@dedicated
a string.  This string is essentially a 'group-by' key of resources into a file that has this string as an identifier.

What do you think?

@chungers Updated example:
{
  "resource" : {
    "softlayer_virtual_guest": {
      "host": {...}
    }
    "softlayer_file_storage": {
      "worker_fs": {
        “@scope”: “@dedicated",
        ...
      }
    },
    "softlayer_block_storage": {
      "shared_block_storage": {
        “@scope”: “managers”,
        ...
      }
    }
}

This created 3 files:
$ ls -l
total 24
-rw-r--r--  1 kaufer  staff  330 Jun  2 14:48 instance-1234.tf.json
-rw-r--r--  1 kaufer  staff  296 Jun  2 14:48 instance-1234-dedicated.tf.json
-rw-r--r--  1 kaufer  staff  170 Jun  2 14:48 scope-managers.tf.json

$ cat instance-1234.tf.json
{
    "resource": {
      “softlayer_virtual_guest": {
        "instance-1234": {
          "tags": {
            "infrakit.attach”: [  <-- Filename of the associated `tf.json` files
              “instance-1234-dedicated”,
              “scope-managers”
            ]
          },
          ...
        }
      }
    }
  }

$ cat instance-1234-dedicated.tf.json
{
    "resource": {
      “softlayer_file_storage": {
        "instance-1234-worker_fs": {...}
      }
    }
  }

$ cat scope-managers.tf.json
{
    "resource": {
      "softlayer_block_storage": {
        "managers-shared_block_storage": {...}
      }
    }
  }

Some comments on this part:
$ cat instance-1234.tf.json
{
    "resource": {
      “softlayer_virtual_guest": {
        "instance-1234": {
          "tags": {
            "infrakit.attach”: [  <-- Filename of the associated `tf.json` files
              “instance-1234-dedicated”,
              “scope-managers”
            ]
          },
          ...
        }
      }
    }
  }

How about something like this:
$ cat instance-1234.tf.json
{
    "resource": {
      “softlayer_virtual_guest": {
        "user-provided-name": {         <-- I think this name gets replaced with the generated id right?
          "tags": {
            "infrakit.attach”: [  <-- Filename of the associated `tf.json` files
              “@dedicated”,  <-- since we don't know the id at the time of definition, just use this symbol to signify the file instance-xyz-dedicated.tf.json
              “managers”  <-- this will resolve to `scope-managers.json` file.
            ]
          },
          ...
        }
      }
    }
  }

What do you think?  This has the benefit of being consistent with the @scope field.  In fact the allowed values are the same.  So it's easier to figure out what's going on.

Sorry I got confused.  I forgot you are showing the tf.json after they are created.  Therefore, the instance ids will have been known and the attach tag should have the full filenames.

@chungers Now that the SPI has been updated to pass the RollingUpdate context we need to figure out the naming convention issue here: https://github.com/docker/infrakit/issues/561#issuecomment-305282790
The basic problem is when we have instance-1234 with dedicated resource worker-fs-1234 and issue a rolling update. We will remove instance-1234 but leave the dedicated worker-fs-1234 resource.
We need to know that the replacement instance (call it instance-5678) should wire up to use the existed dedicated worker-fs-1234 resource.
Seems like the group plugin (that knows the it just destroyed instance-1234 with RollingUpdate) needs to pass that context on the next provision. Any ideas how we should handle this?
Maybe set the LogicalID to the original instance-1234?
Or add a custom tag?
Or update the instance.Spec with a new prop that contains the previous ID?
Or use the Attachments prop?
Thanks!


CVPR2022 call for demos

Hi, there is a call for demos this year for cvpr 2022
https://cvpr2022.thecvf.com/call-demos
where a demo can be added to the Hugging Face organization here: https://huggingface.co/cvpr
As there is already a Gradio demo for Tokencut on Hugging Face https://huggingface.co/spaces/akhaliq/TokenCut, would you be interested in submitting a demo for this?

Hi AK,
Thank you for your nice suggestion. However, it seems that the the paper registration deadline Round 2 is March 18, 2022, thus we might not be able to submit our demo for this event.  If you have other suggestions, don't hesitate to contact us.
Best,
Yangtao


IP-1556: Add support for EOD in PST

Please view commit by commit
JIRA: https://clever.atlassian.net/browse/IP-1551
Overview: Extends s3-to-redshift to allow treating Redshift timestamps (without timezone) as PST timestamps. This ultimately allows us to implement EOD as midnight PST for historical tables by simply changing the data date column to _record_timestamp_in_pst for non-streaming record-keeper jobs (to be implemented).
Testing:

[x] Wrote tests for new functionality

Roll Out:

[ ] Remember to deploy both s3-to-redshift and s3-to-redshift-fast

@schimmy really good point that startEndFromGranularity changes are required (otherwise the data would have been truncating!)
Updated in 8ea157f - PTAL


ALSA lib pcm.c:7843:(snd_pcm_recover) underrun occurred

Hi there,
I got 2 error messages while running start.sh:
ALSA lib pcm.c:7843:(snd_pcm_recover) underrun occurred
It seems it have something to do with sound. I don't need sound.
How could I completely turn off sound transmission via USB in your script please?

Adbmirror does not do anything with sound.
On Sat, Mar 17, 2018, 15:57 pete111<EMAIL_ADDRESS>wrote:

Hi there,
I got 2 error messages while running start.sh:
ALSA lib pcm.c:7843:(snd_pcm_recover) underrun occurred
It seems it have something to do with sound. I don't need sound.
How could I completely turn off sound transmission via USB in your script
please?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/fhorinek/adbmirror/issues/4, or mute the thread
https://github.com/notifications/unsubscribe-auth/AIpwLGYJSCDZWJesl2hqE3XxFgP9IF0Aks5tfSRvgaJpZM4Su1UW
.


RsPrint.java:45-53: Continue removing Guava's code from...

The puzzle 968-1f63803d from #968 has to be resolved:
https://github.com/yegor256/takes/blob/6a770dd8b9feab1fa480dcd0e90f9874eccc5069/src/main/java/org/takes/rs/RsPrint.java#L45-L53
The puzzle was created by @rultor on 01-Jun-19.
Estimate: 30 minutes,  role: DEV.
If you have any technical questions, don't ask me, submit new tickets instead. The task will be "done" when the problem is fixed and the text of the puzzle is removed from the source code. Here is more about PDD and about me.

@paulodamaso/z please, pay attention to this issue

Job #984 is now in scope, role is DEV

The job #984 assigned to @lucasmessias9898/z, here is why; the budget is 30 minutes, see §4; please, read §8 and §9; if the task is not clear, read this and this; there will be no monetary reward for this job

The puzzle 968-1f63803d has disappeared from the source code, that's why I closed this issue.

@0pdd 2 puzzles #1054, #1055 are still not solved.

Job #984 is not in the agenda of @lucasmessias9898/z, can't set title

@sereshqua/z please review this job completed by @lucasmessias9898/z, as in §30; the job will be fully closed and all payments will be made when the quality review is completed

Job #984 is not in the agenda of @lucasmessias9898/z, can't set title

@0crat quality good

@0pdd the puzzle #1054 is still not solved; solved: #1055.

@0pdd 3 puzzles #1073, #1074, #1075 are still not solved; solved: #1054, #1055.

@0pdd the puzzle #1073 is still not solved; solved: #1054, #1055, #1074, #1075.

@0pdd all 5 puzzles are solved here: #1054, #1055, #1073, #1074, #1075.


Fix 'createEach' snippet

The objects for createEach snippet should be in an array.

[{ }, { }, { }]

Hello, I would like to work on this issue.

This issue has successfully been resolved by @Dipsaint1 , thanks


iOS support

Excuse me, is it working on iOS Safari (iPhone/iPad) ?
Thanks!

Dash.js (the library this plugin adapts) only works on MSE supported browsers (http://caniuse.com/#feat=mediasource), iOS is not supported

the videojs dash player works very well in all browsers
see the demo
https://filmsgratos.site/suplayernuevo2.html

solution
https://codepen.io/vsalema/pen/xxJxWxQ


Validate Gateway inheritance possibility

Feature Request
It is needed to implement a proof generation and validation in the gateway that communicates with the layer two. To do so, we will test the viability of inherit the EVM Gateway properties and functions on our own gateway.
This task aim to answer if it is possible or not to do this process.
Describe Preferred Solution
We want to instantiate the gateway in the format we are currently doing. In other words, preferably we only want to modify the newApp function than it can import the EVMGateway and uses its structure. The function code should look something like this:
export function NewApp(
  handlers: ccip.HandlerDescription[],
  middlewares: RequestHandler[],
) {
  const server = NewServer(...handlers, withQuery())
  const l1Provider = process.env.LAYER_ONE_RPC
  const l2Provider = process.env.LAYER2_RPC
  const l2Rollup = '0xd80810638dbDF9081b72C1B33c65375e807281C8'

  const evmGateway = new EVMGateway(
    new ArbProofService(
      new JsonRpcProvider(l1Provider),
      new JsonRpcProvider(l2Provider),
      l2Rollup,
      new InMemoryBlockCache(),
    ),
  )
  evmGateway.add(server)

  return server.makeApp('/', ...middlewares)
}

Describe Alternatives
There are two possible Alternatives.

Include EVM Gateway repository as a git submodule in our repository. Then, import the gateway structure and use it with our gateway.

git submodule add https://github.com/ensdomains/evmgateway

Clone the EVM Gateway repository in our repository. This will not allow us to be update to the evmGateway modifications, but allow us to modificate their code and make the files more custom.

cd packages && git clone https://github.com/ensdomains/evmgateway

Related Code
For the task, it is important to undrustand and take a look at EVM Gateway code:
https://github.com/ensdomains/evmgateway

Upon studying the feasibility of inheriting properties from the EVM gateway into our gateway framework, it was discovered that there is an incompatibility between the two. This happens from the necessity to modify the CCIP server and make certain adjustments. Since the EVM gateway relies on the original CCIP as a dependency, it's not feasible to simply inherit its functions.
Therefore, we will need to either adapt our gateway to utilize the original CCIP or fork the EVM gateway and modify it to be compatible with our changes.