Added support for search

Added support for search within the template as suggested in #581. I decided to go with a client side search based on Ninja keys, but using deepdub's fork as basis since it supports fuzzy search.
Had to do a bunch of changes to their code to make it work without using node to install everything. Also changed to use some colors defined in our side and using both pages' titles and descriptions for search. Also had to increase the template max width to better accomodate the new item in navigation bar.
Missing implementations:

[ ] One thing I'd love to do (but currently have no idea how) would be to change the text next to the search button depending on the platform. For example, if the user is accessing the site on a mac they should use ⌘k instead of ctrl k.
[x] Test how this looks like (and how it is supposed to work) on devices with smaller screens
[x] Support for offline mode

Some screenshots:

Dark version

Light version

Hi. @george-gca
Thanks for adding the great feature. Images look great.
Just a question. Do you know anyway so that I can test this online?

The easiest way that I can think of is for you to clone this branch and run from it. I want to add some kind of build and deploy from PR here, but I don't know if GitHub Pages support this. I saw this being done with netlify, as I commented in #1981, but never really looked into it.

Apparently Netlify and Vercel support this feature.

I've been trying to make Netlify work for our repo, but to no avail. Currently it fails with
Liquid Exception: No such file or directory @ rb_sysopen - /opt/build/repo/./_bibliography/references.bib in /opt/build/repo/_posts/en-us/2023-07-12-post-bibliography.md

Even though the string references.bib doesn't even exist in the repo.

I was FINALLY able to add the build to Netlify. I believe it would be a great addition to our repo to do builds based on PRs, and that can be done while automatically inserting the link to the build page here. Idk if I have the permission to add this in our repo, but I can teach the one with the right permissions @alshedivat @pourmand1376.
Here is the link to the test.

Thanks @george-gca .
I tested it and I like it.
I just have a proposal. If you could close the navbar after opening the search, it would give me a lot better experience as a user. Other than that it is very good.
Also, I don't have access to add Netlify. Only the owner could do it.

I just have a proposal. If you could close the navbar after opening the search, it would give me a lot better experience as a user. Other than that it is very good.

What do you mean?

Also, I don't have access to add Netlify. Only the owner could do it.

I think I'm going to open a new issue for this, then we can track that there.

What do you mean?

I mean on web version there is no problem. But on Android and smaller devices, I like to the navbar to automatically hide after pressing the search button. Otherwise, I first have to manually close the navbar then I can starting searching.

Ahhh ok, I can fix that. I will also make the z index of both the header and the footer be inferior to the one from the search. Just now realized that they are above the fade.

@pourmand1376 do you know how to do hide the navbar properly? I tried to simply remove the show class from it, but it have 2 side effects:

it hides abruptly and without animation
it keeps the icon on the navbar as it were opened

I think I am going to push this PR into our main branch already, and create 2 new issues:

improvement - change the text next to the search button depending on the platform. For example, if the user is accessing the site on a mac they should use ⌘k instead of ctrl k
bug - fix when on mobile devices

@pourmand1376 do you know how to do hide the navbar properly? I tried to simply remove the show class from it, but it have 2 side effects:

it hides abruptly and without animation
it keeps the icon on the navbar as it were opened

Nope. I don't know.

is it possible to do a site wide search instead of just he options which are shown in the search menu?

In situations like this it is recommended that you open a Q&A in discussions.
Yes, it is possible, but this search works locally, meaning you need to transfer a file with all the content that is going to be used for search. With only titles and descriptions, this file is small and the search is fast. Meanwhile if you give all the titles, descriptions, and contents, this file will increase in size, which will not only make your site heavier, but the search inside the file will be slower.

@george-gca okay, I’ll keep this in mind. But for now I don’t mind search being a bit slower, since I want to use my site as personal instruction repo for future references. Can you tell me how to put all the contents on the search or link to discussion which talks about this. Thanks

Sure. Can you open a Q&A for this? This way it is easier for more people to find the answer to this.

Is there a way to make the search a little more specific? For example when searching "code", it returns results that contain "c" "o" "d" or "e" as well. There has to be a setting or field to restrict results to more exact matches?

This was intentional, that's why it is based on deepdub's fork since it uses fuzzy search. If you want a more traditional search you can probably change the score function used, or change your code to use the original Ninja keys. Note that I made a bunch of changes to deepdub's code to make it work in our repo, so I don't think any of these changes are straightforward.


Sync master with Live

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/Consume-Packages/Dependency-Resolution.md
:white_check_mark:Succeeded

docs/Guides/Create-UWP-Controls.md
:white_check_mark:Succeeded

docs/Hosting-Packages/Overview.md
:white_check_mark:Succeeded

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


Update instructions to enter the account name, key

Hi
I have updated the instructions to make it more clear. You have to enter the name of the account as well as the key for the account. Please check at this line --> 3. Add the following JavaScript
Thanks
Sumit Sengupta, Cloud Solution Architect, US OCP

Hello I made some changes on what to enter in the maps subscription take a look. Thanks !


Wrong result running example textclassification

Hi, I was following this example here: text classification
I was using a AWS g2.8xlarge machine, and followed the same steps using same data set(DBPedia) and same model here, however I get the following result:

I have tried to run longer time (till epch 10), still the same result.
May I know which of my steps might be wrong?
Thanks a lot.

Hello, did you follow the instructions for model creation carefully (e.g. mean subtraction set to none, etc.)? The model generally starts learning something useful after epoch 0.5 (at which point you should see the accuracy above 20% and going up steadily).

Thank you so much for your quick reply!
Yes I did (also set 15 epoch, 0.25 validation, exponential decay learning rate), following is my setting, and you can also take a look here

Oh I think you're using an old version of DIGITS which has a bug in the exponential decay learning rate policy so the learning rate becomes ridiculously small very quickly. If you can upgrade to a newer version that would be nice, otherwise try using the default learning rate policy.

Thank you! It's indeed the exponential rate problem.
Another quick question, when building custom model from torch, it says multi-gpu is not supported, but I found getting started torch page it's supported.

I installed digits from pre-built packages for ubuntu, shall I install from source to use the latest version? Thanks

The latest packages are for 3.0 (tagged Jan 21). We haven't released packages for 4.0 yet.
So yes, you'll need to install from source if you want a newer version.

Thank you so much for your help!

OK, I ended up with the same problem wIth Digits 3.0. Thing is no matter what you put on for learning rate policy, you always end up with the same convergence to 2.5 loss.
Anyone else with the same problem?

build Digits from source instead of ubuntu package helps, this example is running fine with various learning rate policy, and with multi GPU support.


Info for New Layout

Hi all,
i would like to do my own Version of the german layout. For that i'm following Kertase's Commit
https://github.com/AnySoftKeyboard/LanguagePack/pull/314/files
Since I only want to add an xml and make minor changes I don't need Gradle or Android Studio, right? I'm struggeling with the new id in languages/german/pack/src/main/res/xml/german_keyboards.xml  though, how do I get it?
    <Keyboard nameResId="@string/de_keyboard_neo2" iconResId="@drawable/ic_status_german"               layoutResId="@xml/de_neo2" id="ad1b5ffa-15cc-4ba4-abb7-68df2c0874e7"
Any help appreciated!

Generate a random new id here. Hope that helps.

All right, thanks!

For anyone interested, I made my own repo for the german language pack
with layouts with more popup characters and functional keys:
https://github.com/si6ned/LanguagePack
These 3 keyboards were added:
https://github.com/si6ned/LanguagePack/blob/master/languages/german/pack/src/main/res/xml/de_qwertz_equal.xml
https://github.com/si6ned/LanguagePack/blob/master/languages/german/pack/src/main/res/xml/de_qwertz_broad.xml
https://github.com/si6ned/LanguagePack/blob/master/languages/german/pack/src/main/res/xml/de_qwertz_extra.xml


Unable to access "this" inside controllers

I have a simple controller with the following code
import expressAsyncHandler from 'express-async-handler'
import { Controller, ClassErrorMiddleware, Post, Wrapper } from '@overnightjs/core'
import { Logger } from '@overnightjs/logger'
import { OK } from 'http-status-codes'
import { myAsyncAction } from './actions'
import { LogErrorAndStop } from '../middleware/error-handlers'

@Controller("api/auth")
@ClassErrorMiddleware(LogErrorAndStop)
export class AuthController {
    private thingINeedFromClass: string

   constructor() {
       this.thingINeedFromClass = "TEST"
   }

    @Post("sign-up")
    @Wrapper(expressAsyncHandler)
    private async signUp(req: Request, res: Response): Promise<void> {
        Logger.Info("Sign up called")
        Logger.Info(req.body, true)

        console.log(this) // <----

        await myAsyncAction(this.thingINeedFromClass)

       res.status(OK)
    }
}

When I log this it's undefined. If I try and call the same function in this class without the Class decorator, this is accessible as expected.
overnight version 1.7.2
Thanks !

This was resolved by checking out an older state of my app, then checking master back out 🤔

I have this issue too with 1.7.2. Checking out older states dont solve this.

Hey @joeykilpatrick Sorry to keep calling you but this is due to another change in your pull request and I think it's helpful to point it out.
This change right here on line 156:
let callBack: (...args: any[]) => any = controller[member];

is what was causing 'this' to be undefined. I reverted it back to:
let callBack = (req: Request, res: Response, next: NextFunction) => {
    return controller[member](req, res, next);
};

Please test all methods in the Sample Project before doing pull-requests. Everyone version 1.7.3 should fix this issue.

Sorry @seanpmaxwell for this one, but reverting reopens #42, and causes tests to fail. Note that the actual method (callback) does not have to be of that type and can have an unlimited number of arguments of any type if a wrapper is used. The following change will fix the issue.
let callBack: (...args: any[]) => any = (...args: any[]): any => {
    return controller[member](...args);
};

I'm sorry that my pull request had these side effects. Without tests for the sample project, it is difficult to know what will break when additional code is written. This is a great library, but not having any tests makes it impossible to contribute without issues like this.
I can submit a pull request for the code above and an additional test for this behavior, but if you would rather I not make any more changes, please let me know. I really like this library and use it for some personal projects, but if you do not want any further contributions from me, then I will understand.

@joeykilpatrick  v1.7.4 has this change


Missing translations to spanish in order to enable es-MX as a language

Hm, looks like this is a less translated than I think we'd usually want in es-MX I think; it looks like arcade/target-strings.json is only about 25%, and it would be nice if arcade/core-strings.json, arcade/game-strings.json, arcade/screen-string.json, arcade/animation-strings.json, and arcade/mixer-strings.json were translated a bit more but I don't think that's required.
(Ideally it looks like we have a little more strings.json as it's currently 66% approved, but I'd believe it if most of the important ones are translated so not likely a big deal / will improve over time)
Originally posted by @jwunderl in https://github.com/microsoft/pxt-arcade/pull/4374#pullrequestreview-810581807

arcade/target-strings.json is at 100%
The rest of the files are easier to fix with in context translation and there's also several strings that won't translate such as %img and C#7 so the percentages aren't entirely "correct". Additionally percentages are based on characters in the file so even if we've translated all but one of the strings, if the string is excessively long then it'll appear as a smaller percentage
arcade/core-strings.json is at 39%
arcade/game-strings.json is at 44%
arcade/screen-string.json is at 28%
arcade/animation-strings.json is at 79%
arcade/mixer-strings.json is at 86%
strings.json is now at 80% but most of the strings here are either error messages or text for tooltips


masonry weird spaces

Hi I put masonry code everything looks alright there are no console errors from javascript type etc.
but nothing happens (means there is no absolute on divs)
why?
there is something i lose here?
http://www.reading3.co.il/he/company/a/gallery/?ContentID=295
thanks

I think you are confused with a Javascript library. This github project is for the iOS library.

what did you mean?

You are talking about javascript and linking to a website.
This is for the Objective-C code library Masonry and has nothing to do with the Javascript one.

i am not using any objective c who are you?

You have to post this issue here: https://github.com/desandro/masonry Thanks


Experimental cell execution analysis

Re #14316.
This PR adds experiments for running code analysis upon cell execution, on top of which we can offer features like Gather Cells or Select/Run Dependent Cells. This requires the latest prerelease of Pylance extension for now.
The changes are contributed in standalone component and written in the same fashion as a standalone extension.

[x] Pull request represents a single change (i.e. not fixing disparate/unrelated things in a single PR).
[x] Title summarizes what is changing.
[x] Appropriate comments and documentation strings in the code.
[ ] Has sufficient logging.
[ ] Has telemetry for feature-requests.
[ ] Unit tests & system/integration tests are added/updated.
[ ] Test plan is updated as appropriate.
[ ] package-lock.json has been regenerated by running npm install (if dependencies have changed).

seems unusual to have another file named extension.ts


Ping doesn't work in web extension

Need to implement ping in the web version of the extension to keep the connection to the server alive.
Although we seem to continually request kernels. Not sure where that request is coming from.

Request is coming from jupyter lab services. It continually requests kernels while the document is open. Maybe this is good enough for pinging?
Looks like SessionManager lifetime is what controls the polling. We'd have to dispose our session manager.

HostJupyterServer keeps the session manager up. Kernels don't seem to ever go down (I waited 20 minutes) so I don't think this is necessary.


Add Rotational Cipher Exercise

We didn't agree on this, either. But here it is.
http://forum.exercism.org/t/implement-some-missing-php-exercises-for-48in24/9865/11

Thanks a lot for contributing! You must tell me, which AI you use to produce that good code so fast...

ChatGPT, it was that obvious. :) I'm taking existing exercises from other languages and convert the tests and example, and adjust to my liking. It's faster this way.

By default all prs are scored as a medium, I think mkmxp scored some of these as a large? Without tags they don't get attributed to a specific sub-category.

No Problem, thought it has something to do with the tagging, and you confirmed that.

@tomasnorre Yes, all my bad. Was too much in hurry this morning. Will take more time and be more cautious.

Tags can be added retroactively and it will update.

@tomasnorre Yes, all my bad. Was too much in hurry this morning. Will take more time and be more cautious.

Not a huge deal, but must admit the gamification motivates me too :)

Thanks for the info, @neenjaw !


Console warning: using deprecated parameters for the initialization function; pass a single object instead

When running a Leptos CSR app with Trunk in the browser, I always get this warning in the console:
using deprecated parameters for the initialization function; pass a single object instead

It is triggered by the __wbg_init function in the JS file:
async function __wbg_init(module_or_path) {
    if (wasm !== undefined) return wasm;

    if (typeof module_or_path !== 'undefined') {
        if (Object.getPrototypeOf(module_or_path) === Object.prototype) {
            ({module_or_path} = module_or_path)
        } else {
            console.warn('using deprecated parameters for the initialization function; pass a single object instead')
        }
    }
    ...
}

Because the argument to this function in index.html is a string instead of an object:
import init, * as bindings from '/c6ol-client-27e2b4451d2c072.js';
const wasm = await init('/c6ol-client-27e2b4451d2c072_bg.wasm');

I tracked this down to this commit in wasm-bindgen, which is shipped in v0.2.93 and onwards. The corresponding pull request is https://github.com/rustwasm/wasm-bindgen/pull/3995.
The corresponding code in Trunk are these lines:
https://github.com/trunk-rs/trunk/blob/ce872cedea867915f194c737b6024e47d4fdbebb/src/pipelines/rust/output.rs#L140-L141
I think we can maybe change the second line to pass an object instead of a string, but we need to be careful not to break compatibility with wasm-bindgen before v0.2.93. I might investigate this later and open a PR for this.

Would previous versions also accept an object?

Just checked, look like it doesn't. So we indeed need to eval the version.

I don't think this completely fixes the issue. I've been getting this console warning when starting web workers with gloo-worker, and traced it back to a temporary file containing
importScripts("http://localhost:8080/web_worker.js"); wasm_bindgen("http://localhost:8080/web_worker_bg.wasm");
(The exact URLs don't matter.) I'm fairly certain the file was generated by
https://github.com/trunk-rs/trunk/blob/4c9d85f6f04a31a272c71db8df12e142c76311fb/src/pipelines/rust/mod.rs#L656-L658
wasm_bindgen refers to / runs __wbg_init, so the same issue as above occurs.


Alt-space doesn't generate an X11 KeyPress

Windows build number:
10.0.22621.1702
Your Distribution version:
22.04
Your WSL versions:
WSL version: <IP_ADDRESS>
Kernel version: <IP_ADDRESS>
WSLg version: 1.0.51
MSRDC version: 1.2.3770
Direct3D version: 1.608.2-61064218
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.22621.1702
Steps to reproduce:
xev -event keyboard
[type alt-space]
WSL logs:
No response
WSL dumps:
No response
Expected behavior:
KeyPress event, serial 25, synthetic NO, window 0x600001,
    root 0x390, subw 0x0, time 8639038, (132,-51), root:(1023,471),
    state 0x10, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES,
    XLookupString gives 0 bytes:
    XmbLookupString gives 0 bytes:
    XFilterEvent returns: False

KeyPress event, serial 28, synthetic NO, window 0x600001,
    root 0x390, subw 0x0, time 8639100, (132,-51), root:(1023,471),
    state 0x18, keycode 65 (keysym 0x20, space), same_screen YES,
    XLookupString gives 1 bytes: (20) " "
    XmbLookupString gives 1 bytes: (20) " "
    XFilterEvent returns: False

KeyRelease event, serial 28, synthetic NO, window 0x600001,
    root 0x390, subw 0x0, time 8639200, (132,-51), root:(1023,471),
    state 0x18, keycode 65 (keysym 0x20, space), same_screen YES,
    XLookupString gives 1 bytes: (20) " "
    XFilterEvent returns: False

KeyRelease event, serial 28, synthetic NO, window 0x600001,
    root 0x390, subw 0x0, time 8640190, (132,-51), root:(1023,471),
    state 0x18, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES,
    XLookupString gives 0 bytes:
    XFilterEvent returns: False

Actual behavior:
KeyPress event, serial 25, synthetic NO, window 0x600001,
    root 0x390, subw 0x0, time 8639038, (132,-51), root:(1023,471),
    state 0x10, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES,
    XLookupString gives 0 bytes:
    XmbLookupString gives 0 bytes:
    XFilterEvent returns: False

KeyRelease event, serial 28, synthetic NO, window 0x600001,
    root 0x390, subw 0x0, time 8640190, (132,-51), root:(1023,471),
    state 0x18, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES,
    XLookupString gives 0 bytes:
    XFilterEvent returns: False

If pressing alt-space brought up the usual Windows menu for the window, then I would assume that that was the intended behavior, but it doesn't do that either. It just does nothing. If it's supposed to bring up a Windows menu, and that bug gets fixed, then please consider this bug report to be a feature request for some way to turn that feature off and have the alt-space usable by X11 applications.

This is quite annoying, I managed to get a work-around for my use-case by using PowerToys Keyboard Manager, by rebinding Alt-Space shortcut to Escape, since in my application Escape is same as Alt, but then I always have to do Alt-Space Space to get Alt-Space. Would be really nice if this could be fixed somehow, wherever this get's lost.

@terlar, thank you for your response, which helped me find a workaround. In PowerToys Keyboard Manager, make a shortcut mapping Alt-Space to Alt-F13 for application "msrdc.exe", and in WSL map keycode 191 to space using "xmodmap -e 'keycode 191 = space'". This seems to work well, making all WSL windows see alt-space as the ordinary key combination alt-space, while it retains its usual meaning in Windows windows (pulling up the application menu).

Could there maybe be a way to configure keybindings for msrdc.exe? I would also like to use Alt-Space in many of my GUI applications (e.g., emacs).

Could there maybe be a way to configure keybindings for msrdc.exe? I would also like to use Alt-Space in many of my GUI applications (e.g., emacs).

The PowerToys Keyboard Manager does provide a way to configure keybindings for msrdc.  Are you saying you're unable to get my workaround to work? Or are you just saying there should be a more convenient way to do it?
Here's what my Keyboard Manager shortcut looks like in PowerToys:

And here's the operative line in my ~/.bash_profile:
xmodmap -e 'keycode 191 = space'

If you just want the default behavior for  emacs Alt-space, it's easier to remap F13 to the function just-one-space than messing with xmodmap.
(define-key global-map (kbd "<f13>") 'just-one-space)
In PowerToys, you would then map Alt-space to F13, not Alt-F13.

I'm also having this trouble with my emacs where I bind ALT+SPACE to specific function

Could there maybe be a way to configure keybindings for msrdc.exe? I would also like to use Alt-Space in many of my GUI applications (e.g., emacs).

The PowerToys Keyboard Manager does provide a way to configure keybindings for msrdc. Are you saying you're unable to get my workaround to work? Or are you just saying there should be a more convenient way to do it?
Here's what my Keyboard Manager shortcut looks like in PowerToys:
And here's the operative line in my ~/.bash_profile:
xmodmap -e 'keycode 191 = space'
With those measures in place, starting emacs with "emacs -Q" and then entering the key sequence Ctrl-h c Alt-space causes emacs to respond with "M-SPC runs the command just-one-space".

If you are using emacs in wslg, replace the second step in @aimfiz 's solution to add xmodmap setting in emacs.

Add Alt+Space-->Alt+F13 in PowerToys Keyboard Manager.
Add (eshell-command "xmodmap -e 'keycode 191 = space'") into your emacs init file, for example init.el.


language related font changes

In documents with more than one language/script it is sometimes also necessary to change some font features at a language change. polyglossia does it in some places with \addfontfeature. But \addfontfeature doesn't survive a \normalfont and so is not really suited for the task:
\documentclass[11pt]{memoir}

\usepackage{fontspec,xcolor}
\setmainfont{Linux Libertine O}

\begin{document}
In Turkish,  `\textsc{ı}' and `\textsc{i}' are different
letters.

\addfontfeature{Language=Turkish,Color=red}\selectfont
In Turkish,  `\textsc{ı}' and `\textsc{i}' are different
letters.

\addfontfeature{Language=Turkish,Color=red}\normalfont
In Turkish,  `\textsc{ı}' and `\textsc{i}' are different
letters.
\end{document}

Imho some interface is needed to change the font setup at language switches so that the fonts then stay stable as long as the language is active. Such a change can mean to add an open type feature like "Language=Turkish" to the current fonts, but it could also mean a completly different font should be used. I don't know if a unified interface for both tasks is possible.
I have some doubts that the font changes could (or should) be done with simple tex groups. But imho it would be okay to have something similar as for colors: a \font@begingroup and \font@endgroup pair that related package should then use to group a fontsetup.

Idle though — maybe "language" is sufficiently orthogonal to everything else that it should be an NFSS axis.
I had always assumed that code like babel and so on would do the legwork of defining the necessary font switches, but maybe I underestimated the difficulty (and whether the fontspec APIs are good enough). Changing the language of the font is just a special case of changing the font, and also needs to be accompanied by a change of hyphenation patterns, and so on, which is why I never saw this as fontspec's problem to solve.
But I'd definitely like to add sufficient features to help...

Now that you mention it I realize that I haven't look for quite some time at babel. Javier is really extending it and it has a  working frame to switch fonts:
\documentclass{article}
\usepackage[turkish,english]{babel}
\babelfont[english]{rm}[Language=Default]{Linux Libertine O}
\babelfont[turkish]{rm}[Language=Turkish]{Linux Libertine O}
\begin{document}
english  `\textsc{ı}' and `\textsc{i}' are different%
\footnote{english `\textsc{ı}' and `\textsc{i}'}

\selectlanguage{turkish}

turkish,  `\textsc{ı}' and `\textsc{i}'
\footnote{turkish,  `\textsc{ı}' and `\textsc{i}'}

\selectlanguage{english}
`\textsc{ı}' and `\textsc{i}'
\end{document}

(Without the Language=Default one gets a warning about non existing language "English").
I'm quite impressed, there is even a way to define new font families.

That does look really impressive! Given that, is there anything in fontspec that now needs to be addressed?


Andaconda Update

EPIC on Anaconda is still at 1.6. I'd like to include and cite it as part of a docker container, unfortunately I require the latest updated version of EPIC which has access to the "-cs" and "-sbw" options.
Thank you! (And sorry for posting so much here)

Uploading to anaconda is such a bother that I very seldom do it,
unfortunately. I'll try to do it tomorrow.
Endre
On Wednesday, January 11, 2017, Carlos Guzman<EMAIL_ADDRESS>wrote:

EPIC on Anaconda is still at 1.6. I'd like to include and cite it as part
of a docker container, unfortunately I require the latest updated version
of EPIC which has access to the "-cs" and "-sbw" options.
Thank you! (And sorry for posting so much here)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/endrebak/epic/issues/49, or mute the thread
https://github.com/notifications/unsubscribe-auth/AQ9I0gW6Xq6yfASfLEYK6qZDJw_xp0V7ks5rRPyOgaJpZM4Lgv3S
.

I have made a PR: https://github.com/bioconda/bioconda-recipes/pull/3459
The tests timed out. I will ask if someone has the time to maintain epic in bioconda, because I don't, unfortunately. (I was not the one who added it to begin with.)

Updated the README with "help wanted" info.

By the way, do not apologize for posting here. I appreciate all the feedback :)

I'll try again sometime this week. Sometimes the tests just time out supposedly, and then you should try again :)

The PR was merged :) 0.1.24 Should be out on bioconda.


0 is not a valid ProtocolVersion

HA core version
2024.9.3
Current integration version
0.6.0
Last known working integration version
0.5.9
Device type and model
Heat Pump Wi-Fi Controller 171H120F (0)
Working mobile app
iLetComfort
The description of problem
After upgrading to 0.6.0 I get the ValueError: 0 is not a valid ProtocolVersion. Please check the attached logs.
If you need more information I'm happy to help.
The logs
2024-10-03 08:40:43.770 DEBUG (Heat Pump) [midealocal.device] [153931628219814] Socket is None, try to connect
2024-10-03 08:40:43.771 DEBUG (Heat Pump) [midealocal.device] [153931628219814] Connecting to <IP_ADDRESS>:6444
2024-10-03 08:40:43.780 DEBUG (Heat Pump) [midealocal.device] [153931628219814] Connected
2024-10-03 08:40:43.780 DEBUG (Heat Pump) [midealocal.device] [153931628219814] Authentication handshaking
2024-10-03 08:40:43.834 DEBUG (Heat Pump) [midealocal.device] [153931628219814] Received auth response with 72 bytes:<PHONE_NUMBER>012649c6eee62450e61f3a4c5f2acf20273de8c352940936e1dd070402270d9d37c917d730d1a7e6cf6971649a737548eaa82059318d71ae46d16fa77bb907d9ad5b13
2024-10-03 08:40:43.842 DEBUG (Heat Pump) [midealocal.device] [153931628219814] Authentication success
2024-10-03 08:40:43.842 DEBUG (Heat Pump) [midealocal.device] [153931628219814] refresh_status with cmds: [<midealocal.message.MessageQueryAppliance object at 0xd53d6d80>, <midealocal.devices.c3.message.MessageQueryBasic object at 0xd53d6768>, <midealocal.devices.c3.message.MessageQuerySilence object at 0xd53d6c90>], check_protocol True
2024-10-03 08:40:43.842 DEBUG (Heat Pump) [midealocal.device] [153931628219814] Sending: {'_device_type': <DeviceType.C3: 195>, '_message_type': <MessageType.query_appliance: 160>, '_body_type': <BodyType.X00: 0>, '_protocol_version': <ProtocolVersion.V1: 1>, 'header': 'aa1dc3000000000001a0', 'body': '00000000000000000000000000000000000000', 'message_type': 'query_appliance', 'body_type': '00', 'self': <midealocal.message.MessageQueryAppliance object at 0xd53d6d80>}, query is True
2024-10-03 08:40:44.028 ERROR (Heat Pump) [midealocal.device] [153931628219814] Error in process message, msg = aa2ac3000000000000a000c3000000000000000000000000000000000000000000000000000000000000b0
Traceback (most recent call last):
  File "/usr/local/lib/python3.12/site-packages/midealocal/device.py", line 423, in parse_message
    cont = self.pre_process_message(decrypted)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/midealocal/device.py", line 389, in pre_process_message
    message = MessageApplianceResponse(msg)
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/midealocal/message.py", line 613, in __init__
    super().__init__(message)
  File "/usr/local/lib/python3.12/site-packages/midealocal/message.py", line 579, in __init__
    self.protocol_version = ProtocolVersion(self._header[-2])
                            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/enum.py", line 757, in __call__
    return cls.__new__(cls, value)
           ^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/enum.py", line 1171, in __new__
    raise ve_exc
ValueError: 0 is not a valid ProtocolVersion

@bprus di you mind joining HomeAssistant  on Discord and then contact me: chemelli74#2180 ?

Here're the logs with updated debugging:
2024-10-03 12:05:21.739 DEBUG (Heat Pump) [midealocal.device] [153931628219814] Socket is None, try to connect
2024-10-03 12:05:21.740 DEBUG (Heat Pump) [midealocal.device] [153931628219814] Connecting to <IP_ADDRESS>:6444
2024-10-03 12:05:21.763 DEBUG (Heat Pump) [midealocal.device] [153931628219814] Connected
2024-10-03 12:05:21.764 DEBUG (Heat Pump) [midealocal.device] [153931628219814] Authentication handshaking
2024-10-03 12:05:21.833 DEBUG (Heat Pump) [midealocal.device] [153931628219814] Received auth response with 72 bytes:<PHONE_NUMBER>012649ce6fa2609b3671de92b475ed208150597143bd70b9ac9352f9d4224514d2fa91e3f2377b3119dacc913f668cb82e5359ff23cce2a8a6567db55d2778e441bc05
2024-10-03 12:05:21.842 DEBUG (Heat Pump) [midealocal.device] [153931628219814] Authentication success
2024-10-03 12:05:21.842 DEBUG (Heat Pump) [midealocal.device] [153931628219814] refresh_status with cmds: [<midealocal.message.MessageQueryAppliance object at 0xd524fe58>, <midealocal.devices.c3.message.MessageQueryBasic object at 0xd524fd20>, <midealocal.devices.c3.message.MessageQuerySilence object at 0xd524f7e0>], check_protocol True
2024-10-03 12:05:21.842 DEBUG (Heat Pump) [midealocal.device] [153931628219814] Sending: {'_device_type': <DeviceType.C3: 195>, '_message_type': <MessageType.query_appliance: 160>, '_body_type': <BodyType.X00: 0>, '_protocol_version': <ProtocolVersion.V1: 1>, 'header': 'aa1dc3000000000001a0', 'body': '00000000000000000000000000000000000000', 'message_type': 'query_appliance', 'body_type': '00', 'self': <midealocal.message.MessageQueryAppliance object at 0xd524fe58>}, query is True
2024-10-03 12:05:22.038 DEBUG (Heat Pump) [midealocal.message] MessageResponse - message: b'\xaa*\xc3\x00\x00\x00\x00\x00\x00\xa0\x00\xc3\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\xb0'
2024-10-03 12:05:22.040 DEBUG (Heat Pump) [midealocal.message] MessageResponse - header: b'\xaa*\xc3\x00\x00\x00\x00\x00\x00\xa0'
2024-10-03 12:05:22.040 ERROR (Heat Pump) [midealocal.device] [153931628219814] Error in process message, msg = aa2ac3000000000000a000c3000000000000000000000000000000000000000000000000000000000000b0
Traceback (most recent call last):
  File "/usr/local/lib/python3.12/site-packages/midealocal/device.py", line 423, in parse_message
    cont = self.pre_process_message(decrypted)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/midealocal/device.py", line 389, in pre_process_message
    message = MessageApplianceResponse(msg)
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/midealocal/message.py", line 616, in __init__
    super().__init__(message)
  File "/usr/local/lib/python3.12/site-packages/midealocal/message.py", line 581, in __init__
    self.protocol_version = ProtocolVersion(self._header[-2])
                            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/enum.py", line 757, in __call__
    return cls.__new__(cls, value)
           ^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/enum.py", line 1171, in __new__
    raise ve_exc
ValueError: 0 is not a valid ProtocolVersion
2024-10-03 12:05:22.050 DEBUG (Heat Pump) [midealocal.device] [153931628219814] Sending: {'_device_type': <DeviceType.C3: 195>, '_message_type': <MessageType.query: 3>, '_body_type': <BodyType.X01: 1>, '_protocol_version': <ProtocolVersion.V1: 1>, 'header': 'aa0bc300000000000103', 'body': '01', 'message_type': 'query', 'body_type': '01', 'self': <midealocal.devices.c3.message.MessageQueryBasic object at 0xd524fd20>}, query is True
2024-10-03 12:05:22.156 DEBUG (Heat Pump) [midealocal.message] MessageResponse - message: bytearray(b'\xaa#\xc3\x00\x00\x00\x00\x00\x00\x03\x01\x01\x17\x90\x03\x03(\x1e(0A#\x19\x057\x19\x19\x05<"<\x14&\x00\x80\x86')
2024-10-03 12:05:22.158 DEBUG (Heat Pump) [midealocal.message] MessageResponse - header: bytearray(b'\xaa#\xc3\x00\x00\x00\x00\x00\x00\x03')
2024-10-03 12:05:22.158 ERROR (Heat Pump) [midealocal.device] [153931628219814] Error in process message, msg = aa23c300000000000003010117900303281e283041231905371919053c223c1426008086
Traceback (most recent call last):
  File "/usr/local/lib/python3.12/site-packages/midealocal/device.py", line 425, in parse_message
    status = self.process_message(bytes(decrypted))
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/midealocal/devices/c3/__init__.py", line 125, in process_message
    message = MessageC3Response(msg)
              ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/midealocal/devices/c3/message.py", line 271, in __init__
    super().__init__(bytearray(message))
  File "/usr/local/lib/python3.12/site-packages/midealocal/message.py", line 581, in __init__
    self.protocol_version = ProtocolVersion(self._header[-2])
                            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/enum.py", line 757, in __call__
    return cls.__new__(cls, value)
           ^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/enum.py", line 1171, in __new__
    raise ve_exc
ValueError: 0 is not a valid ProtocolVersion

Small clarification, it was:
<EMAIL_ADDRESS>

I have exactly the same error with 0.6.0.
With the adjustments from https://github.com/wuwentao/midea_ac_lan/issues/319, 0.5.9 worked again.
A 0.6.0 log is attached.
home-assistant.log

As I mentioned on Discord, I can't do that, because I use NetHome Plus cloud app and download_lua is not implemented there.

As I mentioned on Discord, I can't do that, because I use NetHome Plus cloud app and download_lua is not implemented there.

Share your device SN and we can download it

Shared with @chemelli74 via Discord.

Same problem with 0.6.0.
My SN is: 0000C3310171H120F2312410182205V3

I get an error for protocol 8:
ValueError: 8 is not a valid ProtocolVersion

Stack has:
homeassistant    | Traceback (most recent call last):
homeassistant    |   File "/usr/local/lib/python3.12/site-packages/midealocal/device.py", line 425, in parse_message
homeassistant    |     status = self.process_message(bytes(decrypted))
homeassistant    |              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
homeassistant    |   File "/usr/local/lib/python3.12/site-packages/midealocal/devices/ac/__init__.py", line 190, in process_message
homeassistant    |     message = MessageACResponse(bytearray(msg), self._power_analysis_method)
homeassistant    |               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
homeassistant    |   File "/usr/local/lib/python3.12/site-packages/midealocal/devices/ac/message.py", line 910, in __init__
homeassistant    |     super().__init__(message)
homeassistant    |   File "/usr/local/lib/python3.12/site-packages/midealocal/message.py", line 579, in __init__
homeassistant    |     self.protocol_version = ProtocolVersion(self._header[-2])
homeassistant    |                             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
homeassistant    |   File "/usr/local/lib/python3.12/enum.py", line 757, in __call__
homeassistant    |     return cls.__new__(cls, value)
homeassistant    |            ^^^^^^^^^^^^^^^^^^^^^^^
homeassistant    |   File "/usr/local/lib/python3.12/enum.py", line 1171, in __new__
homeassistant    |     raise ve_exc
homeassistant    | ValueError: 8 is not a valid ProtocolVersion
homeassistant    | 2024-10-05 08:02:23.992 ERROR (Air Conditioner) [midealocal.device] [151732604698822] Error in process message, msg = aa22ac00000000000805a05840660000003c0080000000000000000000000000217337

Midea AC unit.

closed via #343

I confirm that the new version solves the issue.
Thank you very much for the quick response!


Fix tables version number to match published spec

I signed it!

Jungshik, see #19, has freetype in Android been updated to match the spec?


Automated cherry pick of #11758: fix(region): baremetal spec condition

Cherry pick of #11758 on release/3.7.
#11758: fix(region): baremetal spec condition

/lgtm
/approve


Sometimes mode switcher disappears

It's not a bug, I think it's wanted

PR #581 is changing the button around, so this can be worked on once we see that pulled.

@akuma06 if it works as intended I'm fine with it. Just feels a bit strange.
@kipukun my bad, did not look at that PR.
I guess, guys, you should close this issue than.

@goonyaa All good friend. We'll see if it still applies once it merges. Or we can just update this issue if an issue still applies to the night/day button.

@goonyaa  Dunno if it is good to let it like that. I was just pointing out that it was thought like that (surely for having more space on the navbar for the search form)


Multiple subscriptions use case with Image and Git

Description
What exactly is happening when I configure multiple subscriptions - one with image and another with git,  as given below?
  `kind: Warehouse
  metadata:
    name: kargo-demo
    namespace: kargo-demo
  spec:
    subscriptions:
    - image:
        repoURL: xyz/kargo-demo-app
        semverConstraint: ^0.1.0
    - image:
        repoURL: xyz/kargo-show-app
        semverConstraint: ^0.0.0
    - git:
        repoURL: https://github.com/xyz/kargo-demo-deploy.git`

And I have a stage promotion as follows.
  `apiVersion: kargo.akuity.io/v1alpha1
  kind: Stage
  metadata:
    name: test
    namespace: kargo-demo
  spec:
    subscriptions:
      warehouse: kargo-demo
    promotionMechanisms:
      gitRepoUpdates:
      - repoURL: https://github.com/xyz/kargo-demo-deploy.git
        writeBranch: stage/test
        helm:
          images:
            - image: xyz/kargo-demo-app
              valuesFilePath: helm/stages/test/values.yaml
              key: "kargo-demo-app-charts.image.tag"
              value: Tag
            - image: xyz/kargo-show-app
              valuesFilePath: helm/stages/test/values.yaml
              key: "kargo-show-app-charts.image.tag"
              value: Tag

      argoCDAppUpdates:
      - appName: kargo-demo-test
        appNamespace: argocd
  `

Here, updates coming to the git repository is able to promote. But when a new image is released and promoted from kargo, its not taking effect. Target 'test' branch is not getting updated with the latest released image. I suspect the update being overridden by the old version in the master branch.
Any pointers ? or is it an invalid configuration?
Logs
No relevant logs

@geowalrus4gh the keys in your values files look suspicious to me...

Here is the values.yaml
Default values for sprout-app.
This is a YAML-formatted file.
Declare variables to be passed into your templates.
globals:
  kargo-demo-app-charts:
    enabled: true

kargo-demo-app-charts:
  image:
    tag: "0.1.20"
  replicaCount: 1
kargo-show-app-charts:
  image:
    tag: "0.0.3"
  replicaCount: 1

@geowalrus4gh
It's probably your semver constraints:
    - image:
        repoURL: xyz/kargo-demo-app
        semverConstraint: ^0.1.0
    - image:
        repoURL: xyz/kargo-show-app
        semverConstraint: ^0.0.0

The third-party semver package was recently upgraded and they fixed a bug regarding improper interpretation of the ^ comparison operator for versions < 1.0.0.
It is likely that with this fix, your warehouse cannot select anything newer than xyz/kargo-demo-app:0.1.x and xyz/kargo-show-app:0.0.x.
One of our own teammates was bit by this very issue just last night and that's when it came onto my radar.
References:

How it's supposed to have worked: https://github.com/masterminds/semver#caret-range-comparisons-major

The bug: https://github.com/Masterminds/semver/issues/180

The fix: https://github.com/Masterminds/semver/pull/181

Where we the fixed version made its way into Kargo: https://github.com/akuity/kargo/pull/1255

If you update those expressions, it will likely solve your problem.
Please lmk if this works.

It worked after the change as below.
  spec:
    subscriptions:
    - image:
        repoURL: xyz/kargo-demo-app
        semverConstraint: ^0
    - image:
        repoURL: xyz/kargo-show-app
        semverConstraint: ^0

Opened https://github.com/akuity/kargo/issues/1342


Error There is no variable named "dependency" when using dependency in Skip =.

We tend to use dependency outputs with Skip =. This was working with terragrunt version =< v0.31.5
An example of where we use a dependency value with Skip:
dependency "cluster" {
  config_path                   = "../cluster"
  mock_outputs_merge_with_state = true
  mock_outputs = {
    cluster_name                        = "mocked"
  }
}

skip = dependency.cluster.outputs.cluster_name == "mocked"

We are provisioning an EKS cluster and want to skip the current "config" module being called on the first ever plan. The config module expects a cluster to be present and accessible so that it can populate the provider credentials for kubernetes and helm.
The error I am experiencing with version v0.35.13 is Unknown variable; There is no variable named "dependency".

You can't recursively introspect a dependency in a dependency block.
Note that the way you wrote it also has a chicken-and-egg problem. The skip flag means skip pulling the dependency, but in order for terragrunt to know whether or not to skip, it has to fetch the dependency output. So even if we did support recursive look ups, it's not clear what terragrunt should do, because it can't decided whether to skip fetching outputs until it has fetched outputs.

You can't recursively introspect a dependency in a dependency block.
Note that the way you wrote it also has a chicken-and-egg problem. The skip flag means skip pulling the dependency, but in order for terragrunt to know whether or not to skip, it has to fetch the dependency output. So even if we did support recursive look ups, it's not clear what terragrunt should do, because it can't decided whether to skip fetching outputs until it has fetched outputs.

The skip in my example is outside the dependency and not within the dependency block.
Using debug logging, from version  =< v0.31.5 I noticed the outputs will be retrieved
DEBU[0000] Getting output of dependency

It seems in previous versions the output from the dependencies were being retrieved in the skip block. Still trying to find the change in behaviour in recent releases.

This would be useful for us as well. In our case, we have a Terraform module that deploys a HashiCorp Vault instance. It runs an external data source that inits Vault and returns the root token. We then have a separate module that installs configuration in Vault.
When running in reverse order in destroy-all, it will work the first time, but then get stuck if run again, because the Vault provider is being configured with dependency.vault.outputs.root_token, which is blank if the vault module has been destroyed.
It would be useful to be able to
skip = ! contains(dependency.vault.outputs, "root_token)

but when I try, I get
Unknown variable; There is no variable named "dependency"., and 1 other diagnostic(s)


Diff: shifted indentation

Hi! It looks like some lines are sometimes weirdly indented:

Here's what it looks like without Refined GitHub:

And here's the URL to reproduce:
https://github.com/vatesfr/xen-orchestra/pull/3155/files#diff-37458fb9e51d193ef360403ba893e2e2R47
(Might be related to #2085)

I don't see any weird indentation, I think you're just noticing the missing + sign, which leaves the empty space behind

Notice how line 50 is shifted right compared to line 49 while they should be aligned. And here's how it looks like when you select it:

Indeed, maybe #2088 will fix it

Hopefully :)

I tried to run the fix manually (simply adding the extra CSS directly in the browser) and it fixes #2085 but it doesn't seem to work for this issue so there might be something more to it.


Please update the README to describe how to fix initial install problems/fix installations issues

I have just attempted to get your template up and running, however, the intall process documented just resulted in a lot of errors and a failed attempt to install.
Please can you document your assumptions, eg what version of npm, version of gulp. This article shows how to uprgrade to Gulp V4, I'm not sure if  have to do this or not, but as it stands, the template does not currently work.
PS: I am using WSL2 on windows running ubuntu 20.04
here is my gulp install result:
 ✘ plastikfan@Janus  ~/dev/github/front/Dash-UI λ   main ±  npm install gulp-cli -g
npm WARN deprecated<EMAIL_ADDRESS>https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated<EMAIL_ADDRESS>Please see https://github.com/lydell/urix#deprecated
/home/plastikfan/.nvm/versions/node/v10.23.0/bin/gulp -> /home/plastikfan/.nvm/versions/node/v10.23.0/lib/node_modules/gulp-cli/bin/gulp.js
+<EMAIL_ADDRESS>added 252 packages from 165 contributors in 9.245s

and here is the result of running the gulp command:
 plastikfan@Janus  ~/dev/github/front/Dash-UI λ   main ±  gulp
TypeError: series is not a function
    at Object.<anonymous> (/home/plastikfan/dev/github/front/Dash-UI/gulpfile.js:181:19)
    at Module._compile (internal/modules/cjs/loader.js:778:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10)
    at Module.load (internal/modules/cjs/loader.js:653:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
    at Function.Module._load (internal/modules/cjs/loader.js:585:3)
    at Module.require (internal/modules/cjs/loader.js:692:17)
    at require (internal/modules/cjs/helpers.js:25:18)
    at requireOrImport (/home/plastikfan/.nvm/versions/node/v10.23.0/lib/node_modules/gulp-cli/lib/shared/require-or-import.js:19:11)
    at execute (/home/plastikfan/.nvm/versions/node/v10.23.0/lib/node_modules/gulp-cli/lib/versioned/^3.7.0/index.js:30:3)
 ✘ plastikfan@Janus  ~/dev/github/front/Dash-UI λ   main ± 

As you can see, I'm running node version: v10.23.0, but this also failed on node version: v14.15.0. I switched to trying v10 as a result of finding this on stackoverflow: gulp Package task -ReferenceError: primordials is not defined

This error was caused by the fact gulp 3.9.1 kept getting installed instead of the minimum of gulp 4. Had to also remove node_modules before proceeding with additional attempts otherwise it remains in a bad state. Perhaps the install guidelines should suggest checking that gulp 4 is installed not version 3.x, because that doesnt work.


Add pre-commit hooks enforcing a standard style

What kind of change does this PR introduce?
Enforces code consistency via pre-commit hooks and checks pushed code on all branches in CI
I left off the mypy check for now because there were some tricky type errors in the query builder
Resolves #26

The black hook is going to cause conflicts any time other stuff merges into develop before this PR. I can strip out the commit that applies the changes and limit this PR to just the pre-commit config, CI, and README files if you prefer.
The CI hooks would fail after merge but you'd be able to apply the hooks locally when you're ready. Would that be easier to deal with?

Hey @olirice,
Thanks for considering the downstream consequences of this PR, it is really thoughtful of you. No worries, I'll look into this Pull Request in a few hours so that we can get this merged before anything else gets merged.
Joel

LGTM


FIX knobs select to actually support rich values

Fixes: https://github.com/storybooks/storybook/issues/4402

@sapkra This should truly fix the issue.
The problem was indeed that trying to set a rich value as a value on <select> doesn't work.
So In this PR I'm mapping back to the object-key (which should always be a string).
Also simplified the code a bit.

If you'd like to review the code perhaps?


Add excerpts to blog posts

Details
Currently, the blog post index page shows all of the blog posts with all of their content in one big page.
This is not really desirable or useful for users, and mkdocs-material has a feature to solve it, excerpts.
This feature should be used to make the blog post index page useful.
Additionally, excerpts should also be set to be "required" in the mkdocs.yml configuration file.
(see this to find out how to set this to be required)

Hi @mowies
Can I please raise a PR making required changes, here?


Inactive users are displayed in the DCC page

now, there are two options in dcc nav-bar.
Active requests and approved requests..


Some albums cannot be deleted from the Favorites list, once added.

Expected behavior
The user expects to be able to add or delete albums from the Favorites list.
Actual behavior
The user cannot add or delete some albums from the Favorites list. Because when I try to add or delete albums from the Favorites list, some of them are not added or cannot be deleted from the list.
How to reproduce

Search some albums and add them to favorites.
Go to the albums favorite list and try to delete it.
close and open the application again.
Now we notice that the album recently removed, is again in the albums favorite list.

App version: MusiQ V 1.857
Operating system: Android 6.0

Recording Of The Bug
https://youtu.be/GlHuZTZBV4w

Thanks for the report. When you re-launch the application, were the albums in the favorites different than the ones you added?

It is my pleasure, No, after re-launch the albums are still the same.

I fixed this with 1.860. Took a lot of tweaking, but it should be okay now.


Memcached is not running

Hi,
First, I've pull memcached:
docker pull memcached
Then, like in the presentation page, I've runned it:
docker run --name my-memcache -d memcached
A docker ps -a shows me this:
CONTAINER ID        IMAGE               COMMAND                  CREATED             STATUS              PORTS                                                                                NAMES
43812fe9a62b        memcached           "docker-entrypoint.s…"   About an hour ago   Up About an hour    11211/tcp                                                                                my-memcache

But a netstat -nlp shows me that the 11211 port is not occupied.
My Docker version is:

Docker version 17.12.0-ce, build c97c6d6

My OS version is:

Distributor ID: Ubuntu
Release:        16.04
Codename:       xenial

Thanks,

You need the -P flag to expose default ports to the host, or -p port:port to manually assign exposed ports in host->container format.

I have already tried -p port:port. By the way this has worked: docker run -i -d -p 11211:11211 memcached for me. I think that the problem comes from a conflict between -p port:port and the other options --name my-memcache -d memcached

I am getting this output whenever I am using the docker instance:
echo "stats settings" | ncat -v <IP_ADDRESS> 11211
Ncat: Version 7.94 ( https://nmap.org/ncat )
Ncat: Connected to <IP_ADDRESS>:11211.
Ncat: 16 bytes sent, 0 bytes received in 0.45 seconds.

These are all the commands I used:

docker run -i -d -p 11211:11211 memcached:bookworm
docker run --network="host" --name my-memcached -p 11211:11211 -d memcached:bookworm memcached -l <IP_ADDRESS>,::1 -m 64 -c 1024 -vv
docker run --network="host" --name my-memcached -p 11211:11211 -d memcached:bookworm memcached -l <IP_ADDRESS> -m 64 -c 1024 -vv

The config files I used:
# memcached.conf
-l <IP_ADDRESS>   # Listen on all interfaces
-m 64        # Memory allocation for Memcached in MB
-c 1024      # Maximum simultaneous connections
-vv          # Verbose output

Other than this I have no clue what to do? Please help.


Missing entry for 0x3453

Arg 1 for this bugcheck can be 0x3453, but it is not listed in the table. Anyone know what it means?
Arg2 seems to be the EPROCESS
Arg3 seems to be a PFN index?

@arilou - Can you open this issue against a specific topic or a content area?

Please reopen if still needed and provide a URL of the page where you are seeing the problem.


Replace current testnet-preview deployment with new k8s deployment

Is your feature request related to a problem? Please describe.
We should try to move over to the new k8s deployment system built by Strangelove, and start with replacing testnet-preview.  The goal of testnet-preview is that it should be an exact preview of what would be deployed if the current state of the main branch were tagged as a release.  This ensures that there are no deployment surprises when tagging a release, and allows testing client protocols against the current state of the main branch.
The only difference between testnet-preview. and testnet. should be that when deploying testnet., we pass the --preserve-chain-id parameter to pd testnet generate to avoid randomizing the chain ID (since there should only be one deployment per tag).
Describe the solution you'd like

[x] Update k8s helm chart logic to support side-by-side deploys - https://github.com/penumbra-zone/penumbra/pull/1707
[x] Write new "deploy-preview-new" workflow for testnet-preview on k8s - https://github.com/penumbra-zone/penumbra/pull/1719
[x] Ensure the action is triggered on pushes to main and uses the latest container images (does it need to wait for them to be built?) - https://github.com/penumbra-zone/penumbra/pull/1730
[x] Merge new workflows into main, use GHA interface to trigger them
[x] Compare /status endpoints between e.g. http://testnet-preview.penumbra.zone:26657/status & http://fullnode.testnet-preview.penumbra.zone:26657/status
[ ] Ask for team testing against fullnode.testnet-preview.penumbra.zone
[x] Update DNS for cut-over on "testnet-preview" (can happen whenever, mostly internal use only)
[x] Update DNS for cut-over (will need to be coordinated with next testnet deploy, otherwise we lose state)

The current k8s deployment provides TLS access to the Tendermint RPC endpoint (load-balancing over fullnodes).  We should provide an additional endpoint that gives TLS access to the pd GRPC endpoint.
We are not in a position to use a TLS endpoint from pcli for kind of boring reasons (we hardcode "http" in a bunch of places, and assume that we have one host for both tendermint + pd with endpoints on different ports), but exposing a TLS pd endpoint is important to do now because we're trying to use grpc-web to access it, and without TLS, this is not really possible because of mixed content rules.

Took a look at what's required here for cut-over. We currently run two discrete testnets:

testnet.penumbra.zone (built from approximately-weekly tags)
testnet-preview.penumbra.zone  (built very frequently from latest HEAD of main branch)

Right now, the k8s deployment logic assumes there's only one testnet, and it destructively resets on updates. That's already a great match for how we manage testnet-preview, but we want to do both on k8s. I'll work on adding a few more knobs to the new deployment logic, so we can set HELM_RELEASE or similar and touch only the proper set of testnet resources during CI runs.

WIP branch coming together at https://github.com/penumbra-zone/penumbra/tree/1659-testnet-preview-via-k8s. Mostly that diff is adding comments, docs, and some refactoring of the test scripts to make more space for multiple environments. I haven't created a separate cluster, but the Terraform logic is already present to do so. Currently working on:

documenting the fullnode.* A record (DNS records are managed out of band) that relates to NodePort added https://github.com/penumbra-zone/penumbra/pull/1660
debugging unhealthy service backends (this is related to the refactoring work I've done; I broke it); for reference:

kubectl get ingress penumbra-testnet-ingress -o json | jq '.metadata.annotations["ingress.kubernetes.io/backends"]' -r -C
{"k8s-be-30563--0a5eab405c618cec":"HEALTHY","k8s1-0a5eab40-default-penumbra-testnet-26657-ed3f3817":"UNHEALTHY","k8s1-0a5eab40-default-penumbra-testnet-8080-5680cfee":"UNHEALTHY"}

Once those problems are resolved, I'll move on to creating side-by-side environments, and touch up the script as necessary to make sure that subsequent deployments don't clobber unwanted resources.

Cluster config for "testnet" setup is solid, will PR in some housekeeping changes with more docs, comments, and labels throughout. Encountered a problem when I tried to deploy "testnet-preview":

Error syncing to GCP: error running load balancer syncing routine: loadbalancer 86iwvh2x-default-penumbra-testnet-preview-ingr-tbg5eif4 does not exist: googleapi: Error 403: QUOTA_EXCEEDED - Quota 'IN_USE_ADDRESSES' exceeded.  Limit: 8.0 globally.

So it appears we've exhausted our account limit on global reserved IPs. I'll see if we can raise that limit, but more likely we'll need to switch to a lower tier of reserved IP to sidestep that limit.

Looked into the IP quota issue. There are actually two limits in play: STATIC_ADDRESSES (limit of 8) and IN_USE_ADDRESSES (also limit of 8). We're already careful about reserving only one static address per testnet, so it's not the STATIC_ADDRESSES limit we're hitting. Rather, it's IN_USE_ADDRESSES, since all external IPs in use by Services count toward that total—regardless of whether they're static or not. Requesting a quota bump (which we've had to do similarly for other resource types, such as persistence storage, back in 2022-09) which should unblock. They promise response in <2d, but I expect more like <2h. :crossed_fingers:

They promise response in <2d, but I expect more like <2h.

OK, it was actually <2m:

:upside_down_face:

Comparing the two testnet deployments for disparities, it looks like node_info.other.tx_index is set to "null" in k8s but "kv" in the testnet config template. Looks like maybe we want to set that to "kv".

uses the latest container images (does it need to wait for them to be built?)

Not yet implemented on https://github.com/penumbra-zone/penumbra/pull/1719; relevant docs are here https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows#workflow_run

Currently working on sorting out the implicit workflow dependencies, and making them explicit. For instance, do we want to build container images if the tests fail? We do not! However, that's currently how things work: the container images get built regardless of the state of other workflows.
Similarly, we must strictly order the workflows so that 1) tests pass; then 2) container image is built; then 3) a deploy is made to the relevant environment. GitHub Actions will allow us to chain up to a maximum of three (3) workflows:

You can't use workflow_run to chain together more than three levels of workflows.

Other potential footguns include the need to manually inspect a previous workflow run and inspect whether it failed: by default, a failed dependency workflow will still trigger execution of the dependent workflow, which I still find surprising; additionally, it may not be possible to inspect whether a dependency workflow was triggered due to a tag or a branch change (which is important for us because it's how we gate testnet vs testnet-preview deploys). In the short term, I may opt to copy/paste several workflows and embed them as jobs, to take advantage of more finegrained control of trigger events.
Next testnet is due Monday, 2022-12-12, and I'd very much like to use the new setup. Today, 2022-12-08, I plan to cut over testnet-preview.penumbra.zone as, ahem, a "preview" of what's to come.

Today, 2022-12-08, I plan to cut over testnet-preview.penumbra.zone

This is done: testnet-preview.penumbra.zone now points to the new k8s deployment. Post-merge it was automatically updated.

terminal output monitoring rollout, for those interested

NAME                                   READY   STATUS        RESTARTS   AGE
penumbra-testnet-fn-0-fvkfk            3/3     Running       0          25h
penumbra-testnet-preview-fn-0-j2hsp    3/3     Terminating   0          24h
penumbra-testnet-preview-val-0-7kghg   2/2     Terminating   0          24h
penumbra-testnet-preview-val-1-pjll9   2/2     Terminating   0          24h
penumbra-testnet-val-0-7fsq2           2/2     Running       0          25h
penumbra-testnet-val-1-lkvcj           2/2     Running       0          25h

❯ kubectl get pods
NAME                                   READY   STATUS    RESTARTS   AGE
penumbra-testnet-fn-0-fvkfk            3/3     Running   0          25h
penumbra-testnet-preview-fn-0-q7s8f    0/3     Pending   0          3s
penumbra-testnet-preview-val-0-qn5gc   0/2     Pending   0          3s
penumbra-testnet-preview-val-1-48mbn   0/2     Pending   0          3s
penumbra-testnet-val-0-7fsq2           2/2     Running   0          25h
penumbra-testnet-val-1-lkvcj           2/2     Running   0          25h

❯ kubectl get pods
NAME                                   READY   STATUS    RESTARTS   AGE
penumbra-testnet-fn-0-fvkfk            3/3     Running   0          25h
penumbra-testnet-preview-fn-0-q7s8f    3/3     Running   0          11m
penumbra-testnet-preview-val-0-qn5gc   2/2     Running   0          11m
penumbra-testnet-preview-val-1-48mbn   2/2     Running   0          11m
penumbra-testnet-val-0-7fsq2           2/2     Running   0          25h
penumbra-testnet-val-1-lkvcj           2/2     Running   0          25h

Still more work to do on the workflow dependencies for Monday's deployment; I'll pick that back up tomorrow.

Calling this done for now. Here's a recent automatic deploy of testnet-preview to the k8s cluster: https://github.com/penumbra-zone/penumbra/actions/runs/3661278131 Come Monday, we'll need to update the A record for testnet.penumbra.zone to point at the relevant IP:
❯ terraform output
testnet_preview_reserved_ip = "<IP_ADDRESS>" # already done
testnet_reserved_ip = "<IP_ADDRESS>" # this one still needs to be updated

We'll do that as part of the testnet deploy. Already lowered the TTL 30m -> 5m in prep for the cut-over.

Was not able to use the new cluster setup for testnet 038 today (#1743). In the interest of :shipit:, I fell back to reusing the legacy droplet, and configured pd and tendermint manually based on the 038 code. It was necessary to stand up the services "manually," because the deprecated workflows were removed in #1730; a bit prematurely, in retrospect.
The root cause of the botched cluster deployment lies in my oversight last week of mistakenly deploying the testnet tag to the preview environment (#1744); this was fixed this morning in https://github.com/penumbra-zone/penumbra/commit/17a3267f63e1765d40cd5d3d071292b8bd4f7fbe, but the late discovery of the misconfiguration means we did not have an adequate "preview" environment to observe the most recent cluster config. As such, I suspect we missed identifying some breaking changes recently.
As a result, the current state of our deployments is a bit brittle right now. To wit:

:rotating_light: testnet-preview.penumbra.zone is down; there's currently a CrashLoopBackoff on the relevant pods, due to an unhappy tendermint container
:warning: testnet.penumbra.zone is running on the legacy infra
:warning: the deployment workflows in GitHub Actions are manually disabled, to prevent automatic changes to state (:rainbow: per-PR CI runs remain unaffected)
:warning: galileo is unhappy; this has happened a few times after testnet deploys, but this time i suspect codechanges may be necessary; see https://github.com/penumbra-zone/penumbra/issues/1743#issuecomment-1347327463

Starting tomorrow, I'll focus on unbreaking testnet-preview, since that's our canary in the coal mine. Once preview is happy again, I'll resume deploys of testnet-on-k8s, and provide updates here.

This is done: testnet-preview is now served via k8s, and has been since 2022-12-12, via 5b42c45d3440b5d56723f392bded8e8cd7fa12cd. I'll open another issue tracking the transition of testnet (cf. testnet-preview) to k8s.


devcafe/ubuntu18.04-gcc7.3.0-openmpi2.1.0-mkl2017.4.239:latest - initialization of  MKL

Hi Roberto !
I just downloaded https://hub.docker.com/r/devcafe/ubuntu18.04-gcc7.3.0-openmpi2.1.0-mkl2017.4.239 ,  and I am trying to make MKL running.
I did
7ce34985$ . ./mklvars.sh intel64

ERROR: architecture is not defined. Accepted values: ia32, intel64, mic

Any help, please ?

I think I solved it: the key is the bash shell:
udocker run devcafe/ubuntu18.04-gcc7.3.0-openmpi2.1.0-mkl2017.4.239:latest  bash
mightybuilder@lxbk0197:~$ . /opt/intel/mkl/bin/mklvars.sh intel64 ilp64
mightybuilder@lxbk0197:~$ echo $MKLROOT
/opt/intel/compilers_and_libraries_2017.5.239/linux/mkl

Comments ? You can also close this ticket, if nothing to be added.

@miroi sorry for not replying before (the email notification was buried in the pile) I'm glad you managed to solve the issue, but I'm still puzzled as to why you couldn't find MKL in the first place. The entrypoint for the image does source  the compilervars.sh script already

Ah, compilervars.sh is the key... maybe I did not check it before.
I think that upon activating bash one also activates compilervars.sh, so this issue could be irrelevant.

It could be. I used the following command:
docker run -it devcafe/ubuntu18.04-gcc7.3.0-openmpi2.1.0-mkl2017.4.239:latest

and echo $MKLROOT printed the location of the library.


refactor: remove unnecessary codes in ts-jest-transformer

Summary

Remove unused INSPECT_CUSTOM
Remove unnecessary incremental id
Remove unnecessary baseOptions in constructor

Test plan

Green CI
Does this PR introduce a breaking change?

[ ] Yes
[x] No

N.A.
Other information

Pull Request Test Coverage Report for Build 6035

8 of 8 (100.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.03%) to 93.226%

Totals

Change from base Build 6034:
0.03%

Covered Lines:
1113

Relevant Lines:
1147

💛  - Coveralls


Router-link with slot and conditional component fails

Vue.js / vue-router versions
2.1.7 / 2.1.1
Reproduction Link
https://jsfiddle.net/fpyuz7f8/
Steps to reproduce
Create a two components. One should contain a router-link with a conditional on the first component and a slot.
What is Expected?
Render router-link with slot and conditional component
What is actually happening?
Uncaught TypeError: Cannot read property 'context' of undefined
Additional
I encountered this while working on my framework. When upgrading to<EMAIL_ADDRESS>I would get an error during render. An example of my component is here. This can be fixed by removing the conditional, placing the component as a child, and putting the conditional on the new parent, example:
<router-link>
  <div v-if="active">
    <component></component>
  </div>
  <slot></slot>
</router-link>

Seems to be fixed with vue 2.1.8 (the original fiddle doesn't give warnings anymore), please reopen if otherwise.


Add optional highAvailability feature for registry cache

How to categorize this PR?

/area high-availability
/kind enhancement
What this PR does / why we need it:
I reopend this PR due to some special A in the branch name of the other PR (#247)
This PR adds the optional highAvailability setting for the proxy cache. As mentioned in #246 in some cases the registry cache becomes more critical (like the proxy use case). In such cases it makes sense to scale the registry cache to more replicas. This PR uses the High Availability of Deployed Components feature to also set a working topologySpreadConstraints.
Which issue(s) this PR fixes:
N/A
Special notes for your reviewer:
Release note:

Add optional setting for a registry cache to scale the `StatefulSet` to 2 replicas with the [High Availability of Deployed Components](https://gardener.cloud/docs/gardener/high-availability/#system-components) feature.

/remove-lifecycle stale


Update avatar for the account

Describe the task
Update avatar for the account

Version test : http://<IP_ADDRESS>:8900/s/tkH4isbmSTJWe4f

[ ] Remove account address on Transfer confirm screen
Actual :

[ ] Add action to copy account address when clicking on account avatar


Cross Check Pagination Counts and Summary Endpoint and TermFacets and Log an Error to the Console if they Don't Match.

┆Issue Number: HCAB-194

closing not required


Move (SELECT 1) ordering from relational to SqlServer provider

We currently generate ORDER BY (SELECT 1) when Take is used, since SqlServer requires it. We should move that to the SqlServer provider.
We should probably test whether Sqlite is OK with not having this (like PostgreSQL).
Related: in the general case we can also elide OrderBy on constants as they're meaningless.

Duplicate of #19332


This plug in not working with 2.10

The menu File - does not show Export Layers To/ Export Layers after pasting the py file and the folder in the GIMP 2\lib\gimp\2.0\plug-ins as instructed in the readme, so it is not recognized or installed in GIMP.
Configuration
Version of Export Layers: Latest download
Version of GIMP: 2.10
Operating system: Windows 10 x64, (latest) update

By latest download, do you mean version 3.1?

I think the issue is with the plugin registry: http://registry.gimp.org/node/28268
It links anyone to the download of the 2.4 file. Updating the registry would help users getting the right version.

Unfortunately, I cannot remove or update the page in the GIMP Plugin Registry anymore as the site went static.
What I can do for now is to update the template for issues to make sure users download the plug-in from GitHub rather than the plugin registry.

Ok the issue was indeed using older version. Let's link the one that works with 2.10 and that is the plugin 3.1 (and onward)
https://github.com/khalim19/gimp-plugin-export-layers/releases


Fehler beim laden

Hat das etwas auszusagen? Fehler bedeuten ja meist etwas.
react-dom.development.js:88 Warning: Cannot update a component (`AnimatedLogo`) while rendering a different component (`Component`). To locate the bad setState() call inside `Component`, follow the stack trace as described in https://fb.me/setstate-in-render
    in Component (created by GLMap)
    in div (created by Context.Consumer)
    in div (created by AutoSizer)
    in AutoSizer (created by StaticMap)
    in div (created by StaticMap)
    in StaticMap (created by InteractiveMap)
    in div (created by InteractiveMap)
    in InteractiveMap (created by ForwardRef(HotLoaderLazyWrapper))
    in AppContainer (created by ForwardRef(HotLoaderLazyWrapper))
    in ForwardRef(HotLoaderLazyWrapper) (created by GLMap)
    in Suspense (created by GLMap)
    in GLMap (created by CovMap)
    in div (created by CovMap)
    in CovMap (created by Context.Consumer)
    in Route (created by App)
    in Switch (created by App)
    in div (created by ForwardRef(Container))
    in ForwardRef(Container) (created by WithStyles(ForwardRef(Container)))
    in WithStyles(ForwardRef(Container)) (created by App)
    in div (created by ForwardRef(Container))
    in ForwardRef(Container) (created by WithStyles(ForwardRef(Container)))
    in WithStyles(ForwardRef(Container)) (created by App)
    in Router (created by HashRouter)
    in HashRouter (created by App)
    in ThemeProvider (created by App)
    in App (created by HotExportedApp)
    in AppContainer (created by HotExportedApp)
    in HotExportedApp
    in Provider

Chrome 86.0.4240.75 (Official Build) (64-bit)

i made this #141

Ist nur eine Warnung die in dev auftaucht... sollten wir natuerlich fixen, wuerde ich aber gerade nicht hoch priorisieren da es die funktionialitaet nicht beeintraechtigt.

Fixed with #223


Update README.md

Tiny update because I realized my last PR had an incorrect statement about the github token.

I've quickly tested this and a token with no scopes works fine, the other statement is the wrong one I presume.

Thanks your contribution!!


[DOCS] Add contributing guidelines

so, you mean i have to add the git commands for contributing and explain the whole process

so, you mean i have to add the git commands for contributing and explain the whole process ?

No, add contributing guidelines that for ex, what kinda PR's will be accepted in this repo, but it's not really needed coz this repo is to share your journey, so you can close this issue :)

Okay, just leave it :)


Bounty: Wednesday Bounty

Reward Size in USD
10 USD
Bounty

Sign up to Mintycode

Acceptance Criteria
First who completed onboarding and signed up will receive bounty
Go to Mintycode to approve the Bounty.

I got signed up to mintycode. solved#31


ENH: Add standard deviation of welch

This adds standard deviation output for scipy.signal.welch and related functions. Can be useful for getting confidence intervals from the method.

This made me go look for a Bunch class again: gh-6335. If that's too much work now, then adding std with a keyword is fine with me. But at some point we have to stop using return_xxx keywords.
Test failure is real.

I'm something like -1/2 on this. These functions already have a ton of arguments, and this can be calculated simply enough from the spectrogram by users. Returning confidence intervals (as MATLAB can) takes a little more computation, so it makes a little more sense to spare the user that work.
In any case, if we do include this, the docstring for CSD should reflect that it returns the standard deviation of the absolute magnitude of the cross spectrum, since it is generally complex valued.

Is this just p.std() ?
(I don't know what kind of standard errors these are. Are these pointwise or some overall standard errors?)
In general, I like documented functions or options for one-liners if those are difficult to remember.
However, I would rather type p.std() than add return_xxx=True

this can be calculated simply enough from the spectrogram by users

@e-q do you know if the output of our spectrogram function is identical to that of the private _spectral_helper? If so then I agree is a sample std of the spectrogram output. But if spectrogram does something differently in terms of options to the private function, or uses different values (e.g., for normalization), then it won't be that simple. I'll have to check.

Returning confidence intervals (as MATLAB can) takes a little more computation, so it makes a little more sense to spare the user that work.

Maybe we should actually have it give the confidence intervals, instead. That might be more useful for users anyway.

Is this just p.std()

No, it's the standard deviation across windows used in the estimate. So right now welch returns x.mean(), the average of something internal to the function -- this allows returning x.std() as well.

In fact, spectrogram is nothing but a very thin wrapper of _spectral_helper. (see https://github.com/scipy/scipy/blob/master/scipy/signal/spectral.py#L514). In addition, the only test that we do for spectrogram is to make sure its average is identical to the output of welch. (https://github.com/scipy/scipy/blob/master/scipy/signal/tests/test_spectral.py#L809)
It has a different default window than welch, though.

Closing since I think we can get away with spectrogram instead


a couple of tweaks

make it an issue not on a previous merged PR

it's honestly quite likely that it's just not possible in the first place
there's a lot of things I have wanted to implement, but found that JCEF is just incapable of


Proposal: Support spread operator for tuples in function calls

With current versions of TypeScript, this is an error:
((_) => {})(...[null]); // ERROR: Expected 1 arguments, but got a minimum of 0.

In order to make this code work, the developer needs to tell the type checker to shut up, which could look like this:
(((_) => {}) as any)(...[null]); // Working fine.

This is unfortunate, as passing arguments for functions around in tuples is a common pattern in functional programming and there is currently no way to do it safely in TypeScript.
This was mentioned in #5296, which lead to the spread operator being supported for arrays.  Supporting tuples in addition to arrays is not a straightforward change, since tuples can currently have additional values, which are not type checked (there is proposal #6229, which aims to fix this):
function f(s: string, a: number, b: number, c: number,  ...rest: number[]) {
    // ...
}
// legal
let quad: [string, number, number, number, number] = ["foo", 1,2,3,4];
f(...quad); // and triple

quad = ["foo", 1, 2, 3, 4, "boo!"]; // it is legal currently
f(...quad); // now it blows up in run time because rest has a string

Here is a longer and more detailed example taken from #5296 showing the desired behavior in detail:

function f(s: string, a: number, b: number, c: number,  ...rest: number[]) {
    // ...
}
function g(s: string, a: number, b: number) {
}
// legal
let quad: [string, number, number, number, number] = ["foo", 1,2,3,4];
let triple: [string, number, number, number] = ["foo", 1,2,3];
let double: [string, number, number] = ["foo", 1,2];
f(...quad); // and triple
f(...double, 3);
f("foo", ...[1,2,3]);
f(...quad, 1, ...[1,2,3]); // and triple
g(...double);
// illegal
f(...double); // too short -- double doesn't match parameter 'c'
g(...triple); // too many parameters
g(...quad); // too many parameters

Seems related #5453 #17765 #17884 #17898.

The strict tuples should help, but wouldn't be sufficient; the request seems legitimate. afaik the code did have a check so as to match spreads in rest param positions, but yeah this may well be missing.

duplicate of https://github.com/Microsoft/TypeScript/issues/4130?

@mhegazy whoops... didn't notice that one was still open.  I'll close this.


yield select(...) seems to stop the saga tester from executing

I recently added auth to my application and I use the following to fetch the auth information to pass into API calls within my sagas:
const auth = yield select(makeSelectAuth());

I debugged the tests and noticed my selector was called and returning my mocked data, but then the next yield never calls. I can't figure out if this is a fault of the tester or my own. Any help is appreciated.

I'm pretty sure I am seeing the same behavior in my own experiments to integrate this into our saga testing. @TehBigA have you had any breakthroughs on this issue, by any chance?

const auth = yield select(makeSelectAuth());

are you sure that you want select ? usually you would pass a function to select does makeSelectAuth() return a function? it looks you might want
const auth = yield put(makeSelectAuth());

@erikvold thanks so much for the response! i took another look at my saga and realized that i was running the saga incorrectly and as a result my initial dispatch to the saga didn't trigger anything. 😒 i'm fine with closing this issue!

Closing the issue.
Indeed it seems you've been using select incorrectly (the parameter should be a function). It should probably be:
const auth = yield select(makeSelectAuth);

Or, as @erikvold suggested, some other side effect such as put.


[v2] Documentation (A little guidance needed)

@nolimits4web
Can you please add a little bit documentation of v2. I want to build apps on v2 beta version but i don't know how to start. A little guidance can help us. I know v2 is in development phase but still a little guidance can be really helpful.

Hi @danish1023,
Not sure if this will work for you but it helped me pretty well. Download the V2 and open up Kitchen Sink as a project using Atom. From there take a copy of the index page and the JS folder (Kitchen Sink) and place that in your project

Delete all the content in index that you dont want like the <ul> / <li> stuff and that will give you the base

Using Atom and the Preview HTML pluguin open up the kitchen sink index in preview, from there find the components you want to add and view the code to copy what you want or need to yours. For the most part @nolimits4web has all the JS and info you need in each page so it starts to come together really easy once you know where to look.
Ping me if your getting stuck and I can quickly do a walkthrough (Video or something) of what Im talking about

If i getting stuck... can u help us too @mitchellfranklin?

@alextapia007 sure


urxvtc sometimes stops working

Issue description
I call urxvtd like this.
After a reboot, it always works for a while, but then sometimes, when I try to run urxvtc, I get:
urxvt: can't fork, aborting.

Other times, I get:
unable to connect to the rxvt-unicode daemon: Connection refused

urxvtd -q -o -f is still running, taking up about 2G of RAM.
When I start another instance of urxvtd, urxvtc starts working again.
When I kill the original instance, all clients die, and a new (working) daemon starts.
Idk how to troubleshoot further.
Steps to reproduce
idk, sorry.
Technical details

System: 16.03.git.becde1fM (Emu)
Nix version: nix-env (Nix) 1.11.2
Nixpkgs version: 16.03.659.011ea84

Actually is a "normal" urxvtd behaviour, it have some incompatibles between running version of urxvtd and current urxvtc.  (same problem occurend in debian after urxvt upgrade).
Spawn new urxvtd is a fast and dirty solution.
More precious solution may require patching of urxvtd -- quit daemon if all terminal sessions ends (and enter into this mode by signal). Then it allow using  systemd activation and signal current (old) instance of daemon on upgrades.

@magnetophon Your first link in the issue description is broken, by the way. Press y on any Github page to get a versioned URL (rather than linking to master, which can break links).

@siddharthist Thanks, fixed now.

If this is the expected behavior of urxvtd, we might want to close this issue.


fix: JNI crash in FrameHostObject dtor

What
On android, upon FrameHostObject destructor running the app can crash with the following error:
12-31 14:03:24.076 10992 10992 F DEBUG   : Abort message: 'JNI DETECTED ERROR IN APPLICATION: JNI ERROR (app bug): jobject is an invalid local reference: 0x15 (stale reference with serial number 1 v. current 2)
12-31 14:03:24.076 10992 10992 F DEBUG   :     in call to GetObjectRefType
12-31 14:03:24.076 10992 10992 F DEBUG   :     from void com.mrousavy.camera.CameraView.frameProcessorCallback(androidx.camera.core.ImageProxy)'
12-31 14:03:24.076 10992 10992 F DEBUG   :     x0<PHONE_NUMBER>000000  x1<PHONE_NUMBER>002561  x2<PHONE_NUMBER>000006  x3  0000006f85bdd160

This seems to be caused because we store a local ref in the FrameHostObject and deallocate it in a JNI callback which might not happen synchronously in the dtor. After the dtor is run, the local ref will be invalidated and will crash upon further access. The reset of the jni ref still needs to happen inside the JNI WithClassLoader callback since otherwise it can crash when deallocating on another thread.
Changes
To fix this instead of using a local ref we can use a global ref to control when deallocation happens manually.
This is what is used in the hermes intl implementation https://github.com/facebook/hermes/blob/main/lib/Platform/Intl/PlatformIntlAndroid.cpp#L417.
Tested on
Android simulator, also used profiler tools to make sure memory is not leaking after this change.
Related issues

Fixes #587

🖤


Layout adapts on zoom, preventing useful zooming

Since the layout adapts to fit the available screen/window size, zooming results in the increase in size being immediately reversed, leaving everything except the text the same size as before the zoom. This prevents the interface being used in any setting where the standard sizes are not readable/touchable.
The layout should automatically adapt to changes of window size (including orientation changes), but should not adapt on zoom, allowing all elements to be displayed as large as the user chooses.

Consider in parallel with issue 8.


pkg/adaptor/libvirt: cloud init ISO file using native go

Fixes #1251
Fixes #1250
This PR uses a native go implementation of an tool to create the cloud init ISO file, removing the dependency on an external tool. It also creates the ISO in-memory. This makes sense because the ISO file is very small and the content is backed in memory anyway. Creating the ISO file in-memory reduces the potential of errors, since nothing has to be written to the file system of the hosting container.
ISO file generation as well as memory based image uploader are backed by unit tests.

@Carsten-Leue I will try to test this change still today.

My main concern at this point is with the changes on podvm/Dockerfile.podvm_builder.rhel and podvm/Dockerfile.podvm_builder.centos . I tried to build the podvm with those changes but it failed due to an unrelated problem. I will put a 'hold' tag that should be lifted as soon as I test this change, ok?

@wainersm would it help if I simply undo the changes for  podvm/Dockerfile.podvm_builder.rhel and podvm/Dockerfile.podvm_builder.centos?
The only reason I put them in was this comment https://github.com/confidential-containers/cloud-api-adaptor/pull/1268#discussion_r1277909344

@Carsten-Leue I will try to test this change still today.

My main concern at this point is with the changes on podvm/Dockerfile.podvm_builder.rhel and podvm/Dockerfile.podvm_builder.centos . I tried to build the podvm with those changes but it failed due to an unrelated problem. I will put a 'hold' tag that should be lifted as soon as I test this change, ok?

@wainersm would it help if I simply undo the changes for podvm/Dockerfile.podvm_builder.rhel and podvm/Dockerfile.podvm_builder.centos?
The only reason I put them in was this comment #1268 (comment)

Yes @Carsten-Leue , please, remove those changes as I am not able to test them at the moment.

@Carsten-Leue I will try to test this change still today.

My main concern at this point is with the changes on podvm/Dockerfile.podvm_builder.rhel and podvm/Dockerfile.podvm_builder.centos . I tried to build the podvm with those changes but it failed due to an unrelated problem. I will put a 'hold' tag that should be lifted as soon as I test this change, ok?

@wainersm would it help if I simply undo the changes for podvm/Dockerfile.podvm_builder.rhel and podvm/Dockerfile.podvm_builder.centos?
The only reason I put them in was this comment #1268 (comment)

Yes @Carsten-Leue , please, remove those changes as I am not able to test them at the moment.

Hi @wainersm
alright, I have undone the changes for the mentioned files on this PR.

Hi @Carsten-Leue , I tested this pull request (ignored the changes of the podvm/Dockerfile.*) and I am getting the same error as reported in https://github.com/confidential-containers/cloud-api-adaptor/pull/1262#issuecomment-1668389479 . I'm investigating what is going wrong, my first hypothesis is that an update on kata runtime broke peer-pod's libvirt adaptor.

hi @Carsten-Leue ! could you please re-send this PR with the conflicts resolved so that I can test it?

@snir911 @bpradipt we need one more eyes here :)

@wainersm @bpradipt I had to make another change to this PR, since I noticted that it was logging the content of the ISO file, which is not a good idea, since this could contain secrets.
logger.Printf("Uploading iso file: %s\n", isoVolName)

@wainersm @bpradipt I had to make another change to this PR, since I noticted that it was logging the content of the ISO file, which is not a good idea, since this could contain secrets.
logger.Printf("Uploading iso file: %s\n", isoVolName)

ok, thanks. My approval stands and CI will finish soon to test that version does not break x86_64 (which won't for sure)


Add dark mode

I kindly request comprehensive dark mode support for all components. Currently, not all components possess inherent dark mode functionality, necessitating manual implementation. Additionally, certain components lack 'customClass' properties, hindering the application of styles. So I think dark mode should be added

Hi @codeblitz97,
Thank you for your suggestion to add dark mode to our Keep React component library. We really appreciate your feedback and the interest in this feature.
I'm excited to inform you that we're actively working on implementing dark mode. The good news is that you won't have to wait long – we plan to release it in the next minor version of Keep React. This feature will provide users with the flexibility to switch between light and dark themes, enhancing the library's versatility.
We're thrilled to have you as part of our community and value your input. Your suggestions help us make Keep React even better. If you have any more ideas or feedback, please don't hesitate to share them with us.
Once again, thank you for your contribution, and we look forward to delivering the dark mode feature in the upcoming release.
Best regards,
Md Ariful Islam


Initial support of 2dx26

Based on<PHONE_NUMBER>.
What's working?

read song database
free mode with card inserted

What's not?

arena, other modes, etc.
still need further tests

Thanks for reviewing😀

Yes, most of the codes are came from sinobuz.py, I'm not familiar with the easrv honestly, so I left the part that needs some logic calculations, and only make it "works" for now😂
I'm playing 26 personally, and only tested in free mode (I'm a freshman to 2dx)
As above, I have no 25 and omni version; btw is that 26-omni means 25-omni plus the 26 songs?

This is just an initial version, it still has a lot of things to do. Thus I'm looking forward to any chances like this, thanks, appreciatively😉

I'm tempted to submit a massive pull request with all the stuff i've added but my code is an absolute mess and doesn't have any unit tests or anything so idk :/

Closing old pull requests that have no activity.


Switch to using podman, cleanup build logic

Special notes for your reviewer:
Depends on https://github.com/kubevirt/project-infra/pull/2196
Release note:

Switch build system to use podman instead of docker

/retest

looks good, just two questions in review comments

Edited to point out we don't depend on any project-infra PR, I forgot to remove that.
https://github.com/kubevirt/kubevirt-velero-plugin/pull/72/commits/c6e06410e7a898a42bb676f4a5de32f8cf8d63af is meant to allow running with docker still.

Looks like the memory set in config.sh does not work because it is done too late. So your addition to ci script was actually good.

/test pull-kvp-functional-test

/approve

/lgtm


Set up OLS instance

Config can be specified on Brain Data Standards ontology repo

See https://github.com/INCATools/ontology-development-kit/issues/360