Fix bool commit

Codecov Report

Merging #54 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #54   +/-   ##
=======================================
  Coverage   90.05%   90.05%
=======================================
  Files          61       61
  Lines         855      855
  Branches      175      175
=======================================
  Hits          770      770
  Misses         39       39
  Partials       46       46

Impacted Files
Coverage Δ

packages/rawmodel-core/src/core/props.ts
88.4% <ø> (ø)
:arrow_up:


Call Component function from onEnter/onExit

Version

react-native-router-flux v4.0.0-beta.21 (v3 is not supported)
react-native v0.47.2

Hi there!
First of all, thanks for this awesome router.
Is there a way to call a component method in onEnter/onExit callback?
For example:
<Scene key="tab1" icon={LocationIcon} component={LocationsView} hideNavBar={true}>

Is possibile call a LocationView method from onEnter/onExit method specified in Scene or a sort of onFocus event?
Thank you!

Duplicate of #2298


update docs and unittests.

https://github.com/jaanauati/react-dfp/pull/158
https://github.com/jaanauati/react-dfp/pull/170

https://github.com/jaanauati/react-dfp-website/pull/41


Feature: store student replies in localstorage, when using auto-evaluation or email-submission mode

... so that they can come back to their copy later, and still see their answers.
=> then, we should provide a way to clear the copy, so that students can start an exam over again.

Closing in favor of #58.


K8 Edge App 2022 Hackathon: 'Plagariased Title Search Engine'

This closes #7559
Project Title
Articles Matcher
Project URL
http://millerjuma.com  or
https://jumamiller.xyz
Project Background
I joined EngEd in the summer of 2020, and I had my first article published in January 2021. My first challenge was deciding on what to write, given I was very green on technical writing.
I would come up with a topic, but later realise this topic is saturated on the internet. But wait, the title might be the same, but different contents? or let's say I would suggest a topic on how to install Nginx on Ubuntu 16.04, while the existing articles cover the Ubuntu 14.04?
The problem with google search has always been their algorithm that matches every single match content, even though the topics are far off unrelated. Yes, say, for instance, we can have the same title; How to build Tables in Vue, but down the road, one article may cover the tables using the Vuetify framework which uses the data tables while the other uses the HTML's tables. These are two distinct articles.
With Articles Matcher, we have a large database of articles available on the internet, from the most popular sites led by Section's EngEd, these articles are then listed on the site with a very reactive search engine where you type the article name, and it filters the results depending on your search.
Interestingly, this search engine provides you with the article title, author, brief description and the date it was posted on the internet. These are key features when it comes to plagiarism checks as an author may write an article for several companies with minor edits, which may lead to lawsuits. (the links to the actual writings are provided).
Moreover, it also provides an option to filter articles from a specific author, let's say, jumamiller, by searching my previous articles, you can easily tell whether I'm very repetitive in terms of my writings.
-Articles Matcher also has a special feature for active articles on the queue awaiting publishing, this makes it easy for the writers to search for the existing articles to avoid conflicts of ideas. Popular authors from EngEd are also listed.
Contributor
Full Name: Miller Juma
email<EMAIL_ADDRESS>Author link: https://www.section.io/engineering-education/authors/miller-juma/
Skills: Fullstack Developer >  with Vue 2 | Laravel as the current main stack.
Materials
Github Link:  https://github.com/jumamiller/smart-reservation
Video: coming soon!
Stack
Docker
Kubernetes
Vue 2
Github APIs
Deployment
The following steps were followed:

I first bought the domain millerjuma.com from a third party website host.
To make the DNS management simple, I opted for section NameServers, which I added to my third party host.
The process took a while before the site finally appeared online.
The next step involved setting up the domain of my Section console, (traffics).
The next stage involved setting up the KEI. This is a simple process as it had been set by the Section team.
I then set up my Vue 2 project YAML and Dockerfile files. I then published the docker image on a public docker hub.
The last step was deploying the application with k8s commands.

What a ride! I love KEI man!

Did you make booking.com?

no, just a placeholder..template...will be updating the images!

Glad to see that you managed to get it deployed successfully, @jumamiller. Shame it's just after the deadline.
Love the homepage design and the project idea is brilliant. How did you find using Vue? Have you had much experience with it, prior to this project? Any particular reason to use Vue 2 over 3? It's a framework, I'm very interested in learning more about.

Hi @louisefindlay23, I've been using Vue since January when I joined my current place of work for an internship.

The reason I chose Vue 2 is due to the problems with the Vue 3,  which is not yet stable enough to support a couple of packages. For instance, it doesn't support Vuetify (from the last time I checked).
Vue is very easy to use, in this case, I scaffolded this site within 30 mins, which would have not been the case if I used, say Angular.

👏

Super cool!

Super cool!

Thank you, sir.


Fatal error on npm install: 'poppler/qt4/poppler-form.h' file not found

I get this error when trying to npm install pdf-fill-form

<EMAIL_ADDRESS>install /Users/.../node_modules/pdf-fill-form
node-gyp rebuild
CXX(target) Release/obj.target/pdf_fill_form/src/pdf-fill-form.o
CXX(target) Release/obj.target/pdf_fill_form/src/NodePopplerAsync.o
CXX(target) Release/obj.target/pdf_fill_form/src/NodePoppler.o
../src/NodePoppler.cc:9:10: fatal error: 'poppler/qt4/poppler-form.h' file not
found
#include <poppler/qt4/poppler-form.h>
^
1 error generated.
make: *** [Release/obj.target/pdf_fill_form/src/NodePoppler.o] Error 1
gyp ERR! build error
gyp ERR! stack Error: make failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:276:23)
gyp ERR! stack     at emitTwo (events.js:87:13)
gyp ERR! stack     at ChildProcess.emit (events.js:172:7)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:200:12)
gyp ERR! System Darwin 15.5.0
gyp ERR! command "/usr/local/bin/node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"

I am using:
OS X El Capitan 10.11.5
NodeJS v4.5.0
npm 2.15.9
Dependencies installed using brew install qt4 cairo poppler --with-qt4. Same error occured before and after these installed.

I see now this is a duplicate of an already solved issue, worked for me too: https://github.com/tpisto/pdf-fill-form/issues/16


Dual Python 2 and 3 support (not ready to merge)

Currently the client only supports Python 2. The intention of this pull request is to introduce support for Python 3, whilst continuing support for Python 2 to minimise compatibility issues.

Removing this pending solutions in dependencies.


What to put for 'urls' when preprocessing new data with format_to_lines

For preprocessing in format_to_lines mode, it asks for a MAP_PATH which is the directory containing the urls files (../urls)
A sample text of the urls files in here
https://raw.githubusercontent.com/nlpyang/BertSum/master/urls/mapping_test.txt
However, I am using new data which doesn't have a urls file.

I would suggest to skip format to lines and run format to bert

Thanks! I saw that the urls are only involved with assigning data to train/val/test, so I made a fork to replace that part of the function with random assignments.
https://github.com/Santosh-Gupta/BertSum/blob/master/src/prepro/data_builder.py


Added Validator for allowedRegexvalues

Added a function to check if an env variable's value matches a given regex.
This was required for our project and I think is a nice addition to this amazing tool.
Also added a test for allowedRegexValues().
Also added a readme block.

Thanks for the PR. I wonder if we should require exactly one match, rather than at least 1? In your usage, which behaviour would be most useful?

@GrahamCampbell good point - that was an oversight on my part - updated the PR

Perfect. I've made some tweaks, and merged this into master (https://github.com/vlucas/phpdotenv/commit/1bdf24f065975594f6a117f0f1f6cabf1333b156). This will be included in the v3.6.0 release.

This will be included in the v3.6.0 release. Thanks for the contribution! 🎉


Clean up embedded node data if we can't start it

If embedded node can't be started, data need to be cleaned at:
mwc-qt-wallet/mwc-node/
Same for online Node. Temp wallet data can be cleaned as well.
mwc-qt-wallet/tmp/

Also mwc-node  stop was updated with graceful model.

Node is fixed on all layers.
Online node Wallet is not, because we don't have any reported issues, but implementation can be not safe. Let's get real problem first since solution can be problematic.


Tweaks to phrasing in non-article files

A quick pass through the common files to improve phrasing.

Cheers, dpt


Number format in table view

Hello,
Is there a way to change the number format in table view ?
For instance, I need to see my value as "1264" instead of "1,26k".

I seems to be simple setting that I was sure to find...    but I've searched and I've read the documentation with no success.
Thanks in advance.

Hi,
As a matter of fact, there currently isn't an option to change the number formatting, I'm afraid.
I can see how that would be useful to some use cases, however, so I'll track this as an enhancement request.
Thanks.

Thank you @fthevenet for the quick answer, the enhancement request, and this really great job.
That's a pity for my use, without this formatting the tool is not so convenient, and with it it will just be the perfect tool !


Better path management

Improve the way that QuintTest deals with paths of engines and outputs. Especially important when releasing QuintTest to work on PATH.

Closed by #33


browserify bundle too large and unable to be uglified

I just went to build my application bundle and NUglify (C#) is unable to uglify the js-ipfs-api package, I have had no problem with the other dozen or so packages.
I also noticed the browserified package is 1.3Mb, that is large just to be able to post and retrieve some JSON to IPFS... Is there anyway to produce a lighter version?

I just stumbled across this library which might do the trick.. https://www.npmjs.com/package/browser-ipfs

If you want to uglify it you will need to either transpile it to ES5 using something like babel, or use the harmony branch from UglifyJS as we do. The default installation of UglifyJS sadly does not have support for ES2015 yet.


Can't use ~ in less file to reference file in node_modules

Type of Issue
[x ] Bug Report
[ ] Feature Request

Description
When having a less file with ~-character in import, ie:
@stilguide-path: '~module/src';
@import<EMAIL_ADDRESS>It cannot resolve the path.
How To Reproduce
I guess adding a less-file with an import that references a module in node_modules but instead of using ........\node_modules\module\src\less\variables.less
it should be: ~module\src\less\variables.less
Expected Behaviour
BUILD ERROR
'~module/src/less/variabler.less' wasn't found. Tried - C:\Proj\git\my-module\src\app\modules\stuff~module\src\less\variabler.less,~module\src\less\variabler.
less
undefined
Version Information
ng-packagr: ^1.5.0-rc.1
node: v6.11.4
@angular: v4.2.4
rxjs:
zone.js:

HI @trashhead,
the "~" syntax for resolve relative to node_modules is only implemented for scss and was inspired by webpack's sass-loader

The "~" syntax works for LESS files when running ng build or ng build --prod though. Would be really nice if ng-packagr supported it too.


Begin migration to Vue 2.0 - #8

Think I've got everything
:dancing_men:

@Klowner Looks good, just one comment in the review.
I also get the following console error when switching tabs.
[Vue warn]: Avoid mutating a prop directly since the value will be overwritten whenever the parent component re-renders. Instead, use a data or computed property based on the prop's value. Prop being mutated: "active" (found in component <tab-set>)

After doing a bit of reading I can see that this is due to a change in the way Vue 2.0 rendering/props work. I'll open a new issue ticket for this once the pr is merged.

Whoops, good catch. Fixed


Fixed ESLint errors

#951  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @CatChen and the rest of your teammates on  Graphite


Modernise build and CI

build with jbuilder
use a modern Docker-based travis
use the new io-page-unix dependency

FYI this is in contrast to our discussions elsewhere, and #18 (opened in 2015) suggests that we can easily remove this io-page dependency (yes, once there is netmap support, there may be use for page-aligned buffers, but I barely see anyone working on unix+netmap)

I'm still keen to remove unnecessary dependencies but my focus today is
fixing the revdeps following the io-page depext removal (where the new
top-level package was created). I don't want to leave the master branches
of the repos out of sync with the published universe for too long. After
building is green I can take a look at this in more detail! I don't want my
PR to get so big that it kills datakit-ci ;-)
On 17 Jun 2017 12:57 pm, "Hannes Mehnert"<EMAIL_ADDRESS>wrote:

FYI this is in contrast to our discussions elsewhere, and #18
https://github.com/mirage/mirage-net-unix/issues/18 (opened in 2015)
suggests that we can easily remove this io-page dependency (yes, once there
is netmap support, there may be use for page-aligned buffers, but I barely
see anyone working on unix+netmap)
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/mirage/mirage-net-unix/pull/42#issuecomment-309210807,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAMHutl6km-EEl8wPwHJy-eF0K82xfA9ks5sE789gaJpZM4N825h
.


Autocomplete Manager

As the amount of customization offered on autocompletable objects grows, it seems useful to organize the customizable attributes and methods into a single object. This idea grew out of the discussion in #47.
Currently you can customize autocomplete properties like so:
class MyAutocompletableModel(ClusterableModel):
    name = models.CharField(max_length=255)

    autocomplete_search_field = 'name'

    def autocomplete_label(self):
        return self.name

    @classmethod
    def autocomplete_create(kls: type, value: str):
        return kls.objects.create(name=value)

If implemented now, #36 would add yet another classmethod to the mix. To clean this up and keep it more organized, we'll introduce a new AutocompleteManager type. The default autocomplete manager would look something like this:
class AutocompleteManager(object):
    search_field = 'title'
    label_field = 'title'

    def search(self, model_class: type, value: str) -> QuerySet:
        query_kwargs = {'{}__icontains'.format(self.search_field): value}
        return model_class.objects.filter(**query_kwargs)

    def label(self, obj: models.Model) -> str:
        return getattr(obj, self.label_field)

A subclass of it might look like
class SearchingAutocompleteManager(AutocompleteManager):
    def search(self, model_class: type, value: str) -> QuerySet:
        return model_class.objects.search(value)

    # Notice that no `create` method is specified by default,
    # but can be specified on a subclass
    def create(self, model_class: type, value: str) -> models.Model:
        return model_class.objects.create(title=value)

    def label(self, obj: models.Model) -> str:
        return obj.__unicode__()

You would register a particular manager with a particular target either declaratively:
class MyAutocompletingPage(Page):
    # ...
    autocomplete_manager = SearchingAutocompleteManager()

or with a class decorator:
@autocompletable(SearchingAutocompleteManager())
class MyAutocompletingPage(Page):
    # ...

Veeeeeery preliminary proof of concept work for this exists on 50-manager

@harrislapiroff this is looking really good. I think a major benefit of breaking things off into a separate component like this is: It could give developers flexibility to list the same model in different ways.
For example:

Include product codes in an admin-facing list, but only show product names in a public-facing one
Include draft items in an admin-facing list, but not a public-facing one
Show the draft_title in an admin-facing list, but title in a public-facing one

How difficult do you think it would be to add support for this?


Simplifying concurrency model with kotlin coroutines

Description
Simplifies the concurrency model within the ingestors, replacing RxJava with Kotlin co-routines.
Type of change

[x] New feature (non-breaking change which adds functionality)
[x] Breaking change (fix or feature that would cause existing functionality to not work as expected)

How Has This Been Tested?
Manaul testing for now.
Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] New and existing unit tests pass locally with my changes
[x] Any dependent changes have been merged and published in downstream modules

@brianmcgee have you removed rxjava dependencies from gradle/dependencies and from being imported into ingestion/base?

Not yet, I will clean up the dependencies before marking the PR as no longer a draft.


Drop black from pre-commit hooks and add ruff-format

Overview

https://docs.astral.sh/ruff/formatter/

Details

None

LGTM

@pyvista-bot LGTM


feat: support mapping external types to internal input types

Problem
Json Schema Form supports internal types and treats them quite differently eg. group-array. If a system requires multiple kind of components to be treated internally as group-array, this would be impossible.
Solution
This PR adds support for mapping external input types as group array eg.
const headlessFormOutput = createHeadlessForm(schema, {
    ...,
    presentationMapping: {
      groupArray: ["array", "conditions"],
    }
  })

Hi @juicycleff! Forgive us for our delay with an answer. Could you better explain what you are trying to solve here (give us an example)? Perhaps we can propose a better solution that does not require adding a new config presentationMapping.

Hi @sandrina-p yes you are spot on and in a separate version for nested of any type. I will finish up. Thanks.

Hi @juicycleff, checking in when you plan to have this done :)

Hi @juicycleff, could you answer here? If we don't get an answer until the end of the year, we'll close the PR :)


Simple search functionality

Add the ability to search. We can keep the current params (so the f/e can control the search by post_type, etc) and add a "search" param. We would return any posts which matched the search string in their header, content or acf fields.

Search already works with the s param I'm going to add some docs about this but I think does not search on meta fields, just default WordPress search

Awesome! I think we do need to add acf fields though, considering how much we use them,

Ok cool I'm gong to take a look into that.

On Apr 3, 2016, at 7:58 PM, Adam Fenton<EMAIL_ADDRESS>wrote:
Awesome! I think we do need to add acf fields though, considering how much we use them,
—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub


Tolfun is not working in CMA-ES

algorithm = CMAES(x0=x0,                     sigma=0.25,                     tolfun=1000,                     restarts=9,                     popsize=30,                     restart_from_best='False',                     bipop=True)
My objective function is between 10^8 to 0. I set tolfun to 10^3, however, f_min freezed about 75 generations and CMA-ES still keeps running. And, the introduction https://pymoo.org/interface/termination.html is not detailed. Can anyone help me stop CMA-ES with tolfun? I just want to let bipop and restart work. And I set minimize(problem, algorithm, ('n_gen', 99999)). Does n_gen overwrite tolfun? The last question is, should sigma set smaller than 1? I ask this because the range of x is not normalized, it is confusing to set sigma in a normalized range between 0 and 1.
Thank you for your advice.

For details about the CMAES parameters please also see the original implementation: https://github.com/CMA-ES/pycma
In pymoo, we just interface this library for convenience, however,  not all functionalities are supported.
Is it possible that for you the issue is just restarts=9? Does it work if you set it so zero?

By default CMAES does normalize your X space, however, you can turn it off by setting normalize=False. I personally believe it is easier to set sigma in the normalized space, but if you turn off normalization all can be set in the original one.
No termination criterion is overwritten. But the pymoo once can be added in addition.

Thank you for your comments. I tried a larger tolfun like 5000 and CMAES restarted three times in thousands of iters, but I haven't figure out why CMAES doesn't restart precisely as I expected. The answer may be in PYCMA as you pointed. Anyway, it restarts. If you are interested in my work, you can check out opt_PYMOO.py.


countByCountry should be sortable.

either on the front-end or through the API.
@hellais @TylerJFisher

We should be able to perform sorting in the front-end - I'd like to avoid sorting in the API as much as possible in order to increase performance. IMO the API should be as lightweight, and flexible as possible - meaning that we can't guarantee that an order will be imposed on data in transit.
I'm blocked right now - but I'll try to get the data models set up as soon as I can (waiting for @hellais, @joelanders to reply to my e-mail with regards to local ooni-pipeline development).


Update to 1.0.8 and fixed nuget bug

closes #4
Please notice that I also set the dev branch as default branch for proper CI integration, furthermore I have changed the structure of the repository so that we can reuse the existing build script.

@Silv3rcircl3 thanks for that. I'll add the README when I have a moment


All users' userInfo are visible to any authenticated user

Issue Name
userInfo permissions
Summary
Information stored in the UserInfo collection, which includes accessGroups and email, is visible to any user as long as they have an authentication token.
Steps to Reproduce
Go to the explorer, set your access token and query the UserInfo table. All users' info are displayed
Current Behaviour
All users' info is displayed
Expected Behaviour
Only info limited to the current user should be displayed (if we want to limit its visibility)
Extra Details
Here you should include details about the system (if it is unique) and possible information about a fix (feel free to link to code where relevant). Screenshots/GIFs are also fine here.

I'm not able to reproduce the issue.
When I query our production instance with the following command:
curl -X GET --header 'Accept: application/json' 'https://scicat.ess.eu/api/v3/Users?access_token=<ACCESS_TOKEN>
and I get:
"error":{"statusCode":401,"name":"Error","message":"Authorization Required","code":"AUTHORIZATION_REQUIRED"}}


Manga demon not updating

Source information
Manga demon v1.4.8
Source language
English
Steps to reproduce
Go to extensions, you will see manga demon extension update, try updating it
Expected behavior
After clicking on update it should update normally
Actual behavior
The update fails
Mihon/Tachiyomi version
0.16.3
Android version
Android 14
Other details
The extension is not updating
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] I have updated the app to version 0.15.3.
[X] I have updated all installed extensions.
[X] I have tried the troubleshooting guide.
[ ] I have admitted that I am a clown by having checked this box, as I have not read these acknowledgements.
[X] If this is an issue with the app itself, I should be opening an issue in the app repository.
[X] I will fill out all of the requested information in this form.

https://demoncomics.org/ redirects to https://demontoon.com/ , which is down. Do you know if they moved elsewhere?

https://demontoon.com/ is working just fine for me
On Tue, 27 Feb 2024, 9:13 pm Vetle Ledaal, @.***> wrote:

https://demoncomics.org/ redirects to https://demontoon.com/ , which is
down. Do you know if they moved elsewhere?
—
Reply to this email directly, view it on GitHub
https://github.com/keiyoushi/extensions-source/issues/1577#issuecomment-1966852516,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOJCDGEAVTDOR2PAL4QYSHDYVX5I7AVCNFSM6AAAAABD34SHESVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNRWHA2TENJRGY
.
You are receiving this because you authored the thread.Message ID:
@.***>

My bad. DNS was acting up. I can see it's online now.

Have the same issue.

for extension update issue: uninstall existing extension and reinstall. Rest of the comments aren't related to the issue content.


Add support for Include categories in PostgresProvider#delete()

Landed in https://github.com/metarhia/globalstorage/commit/20f2fb18b13b87841592189ea4c20bead9b431d3.


Araxxor adjustments

Description:

Araxxor adjustments

Changes:

Adjust all CA to be closer to ingame rates
Add times for all time based arraxor CA
Remove a duplicated CA
Remove araxxor from wilderness slayer
Correct extended araxyte from going outside of 200-250
Adjust the Noxious halberd logic to always make the piece given the one thats missing from the next full halberd

ex: you have 6 blade, 6 pommel, 7 point and you get 3 blades to drop this trip. It will filter it so you have 8 blade 7 pommel 7 point. next trip you get a point and it filters to a pommel making it 8 blade 8 pommel 8 point.

Other checks:

[X] I have tested all my changes thoroughly.
closes: https://github.com/oldschoolgg/oldschoolbot/issues/6089
closes: https://github.com/oldschoolgg/oldschoolbot/issues/6091
closes: https://github.com/oldschoolgg/oldschoolbot/issues/6092

To fix the conflict, merge master then:
git rm --cached -r .
git add .

I feel like the new noxious pieces code could probably be simpler. e.g. sort the 3 items ascending by how many of each they own, and always give the first item in that list (the one they own least of)?

To fix the conflict, merge master then:
git rm --cached -r .
git add .

I feel like the new noxious pieces code could probably be simpler. e.g. sort the 3 items ascending by how many of each they own, and always give the first item in that list (the one they own least of)?

Fixed, and I took another go at the noxious piece code, I believe it's simpler now and I just tested it in testing server so its good to go.

Can you remove the
customMonsterHP: 575,
combatXpMultiplier: 1.2,

from Araxxor? I believe these were just copied from Scurrius. Not sure how the slayer xp is handled, but since that's correct I assume the bot knows about the +67.5% bonus xp, so my guess is removing those will make the combat xp accurate too (should be 4x the slayer xp, around ~240k/hr, which is now the best melee xp in osrs without alts).


go get: unknown revision

This is a valid URL:
https://github.com/noborus/ov/commit/6c884471d96a4bbb20557ddc06ade68ec0b3d4ef
However if I try to get the URL, it fails:
PS C:\> go get github.com/noborus/ov@6c884471d96a4bbb20557ddc06ade68ec0b3d4ef
go get: github.com/noborus/ov@6c884471d96a4bbb20557ddc06ade68ec0b3d4ef: invalid
version: unknown revision 6c884471d96a4bbb20557ddc06ade68ec0b3d4ef

go version go1.16 windows/amd64

Looks like this is a dup of https://github.com/golang/go/issues/31191
Also I am not sure my issue applied anymore, as the PR was merged.


convey driver' failedwhencontains to send command ops

failed-when-contains list is not preserved when send* opertaions are called.
This is a hot fix for that, but maybe you see wholes in that solution and there is a better way to do that

Fyi the failed test is an infra issue. But I couldn't rerun it, and didn't want to push new commits to re trigger


undervolt: service contains "unrecognized arguments"

Issue description
If you try to enable undervolt service it would fail with undervolt: error: unrecognized arguments: Restart=no
I solved the issue by removing Restart="no" and Type="oneshot' from undervolt.nix, but I still don't understand why it fails, since the syntax seems to be correct.
Steps to reproduce
add services.undervolt.enable = true; to configuration.nix
Technical details

system: "x86_64-linux"
host os: Linux 5.1.16, NixOS, 19.09pre184855.beff2f8d75e (Loris)
multi-user?: yes
sandbox: yes
version: nix-env (Nix) 2.2.2
channels(root): "nixos-19.09pre184855.beff2f8d75e, nixos-hardware"
nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos

The error is coming from the binary, not NixOS - kindly provide the full error from journalctl -e --unit undervolt.service.
I think I know what's happening - a backslash at the end of the line is causing systemd to read the next arguments as a continuation of ExecStart. But the error doesn't happen on 19.03, so systemd may have changed behaviour.
Please show the generated the service unit:
cat $(systemctl show undervolt.service -p FragmentPath | cut -d= -f2)
Mine on 19.03 looks like this:
[Unit]
Description=Intel Undervolting Service

[Service]
Environment="LOCALE_ARCHIVE=/nix/store/n21v70869vp3wl3c35lasy9r0dnh65sg-glibc-locales-2.27/lib/locale/locale-archive"
Environment="PATH=/nix/store/i8hgfj7pjjipn0zsqxx8ws5xv04s4nvl-undervolt-0.2.9/bin:/nix/store/d9s1kq1bnwqgxwcvv4zrc36ysnxg8gv7-coreutils-8.30/bin:/nix/store/krhqmaqal0gklh15rs2bwrqzz8mg9lrn-findutils-4.6.0/bin:/nix/store/wnjv27b3j6jfdl0968xpcymlc7chpqil-gnugrep-3.3/bin:/nix/store/x1khw8x0465xhkv6w31af75syyyxc65j-gnused-4.7/bin:/nix/store/b3n6imx9a3dr6ajbkdl2qidshcllssl1-systemd-239.20190219/bin:/nix/store/i8hgfj7pjjipn0zsqxx8ws5xv04s4nvl-undervolt-0.2.9/sbin:/nix/store/d9s1kq1bnwqgxwcvv4zrc36ysnxg8gv7-coreutils-8.30/sbin:/nix/store/krhqmaqal0gklh15rs2bwrqzz8mg9lrn-findutils-4.6.0/sbin:/nix/store/wnjv27b3j6jfdl0968xpcymlc7chpqil-gnugrep-3.3/sbin:/nix/store/x1khw8x0465xhkv6w31af75syyyxc65j-gnused-4.7/sbin:/nix/store/b3n6imx9a3dr6ajbkdl2qidshcllssl1-systemd-239.20190219/sbin"
Environment="TZDIR=/nix/store/0l3kl1z6zsh3x8d4372x2c1kzsdxnj86-tzdata-2019a/share/zoneinfo"

ExecStart=/nix/store/i8hgfj7pjjipn0zsqxx8ws5xv04s4nvl-undervolt-0.2.9/bin/undervolt \
   \
   \
   \
   \
   \
   \
   \
   \

Restart=no
Type=oneshot

Here is the journalctl log
Jul 10 09:48:36 vs-5530 systemd[1]: Starting Intel Undervolting Service...
Jul 10 09:48:36 vs-5530 undervolt[27101]: usage: undervolt [-h] [-v] [-f] [-r] [-t TEMP] [--te>
Jul 10 09:48:36 vs-5530 undervolt[27101]:                  [--throttlestop THROTTLESTOP] [--ts>
Jul 10 09:48:36 vs-5530 undervolt[27101]:                  [--core CORE] [--gpu GPU] [--cache >
Jul 10 09:48:36 vs-5530 undervolt[27101]:                  [--analogio ANALOGIO]
Jul 10 09:48:36 vs-5530 undervolt[27101]: undervolt: error: unrecognized arguments: Restart=no
Jul 10 09:48:36 vs-5530 systemd[1]: undervolt.service: Main process exited, code=exited, statu>
Jul 10 09:48:36 vs-5530 systemd[1]: undervolt.service: Failed with result 'exit-code'.
 Your one doesn't have the two spaces on the final line after the last \.
I guess this causes systemd to run the continuation over the two empty lines following.
Or did you run that output through an editor that stripped the trailing whitespace?
Could you paste this into a file indent.nix, with trailing whitespace intact
      ''
    test

  ''

and check nix eval '(import ./indent.nix)'?

OK, I rebuilt my system using beff2f8d75e and it reproduces. The spaces in the unit file are intact.
systemd behaviour has changed, then; someone should find out whether this is a bug. In any case, I think it would be better if the NixOS module didn't produce output like this.
@VlivesRaw hopefully you can work around it by configuring services.undervolt.tempBat, so that the last line is no longer only whitespace.

First of all thanks for the help!

The issue here is https://github.com/NixOS/nixpkgs/issues/63533.
This was fixed upstream in systemd https://github.com/systemd/systemd/pull/12890 and we've
backported those fixes to our fork in https://github.com/NixOS/systemd/commit/bcbaa8da9c6350cec98d888b0af8b0f6ec1ef2e1 https://github.com/NixOS/systemd/commit/aa4c4d39d75ce52664cb28d569b1ceafda7b4c06.
Pretty sure we updated systemd in nixpkgs to include that (#63929).

Yes, this was included in the latest staging next PR (https://github.com/NixOS/nixpkgs/pull/64236) which was merged 8 hours ago.

@VlivesRaw  If you need a quick patch #63777 should suffice until the channel advances.

Been resolved for a while now I guess.


✨ #33 optimize Horoscope

#33

Codecov Report

Merging #34 (0402ff7) into main (d06874a) will not change coverage.
The diff coverage is 100.00%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
@@           Coverage Diff           @@
##             main      #34   +/-   ##
=======================================
  Coverage   99.39%   99.39%
=======================================
  Files          69       69
  Lines        1327     1327
  Branches      221      221
=======================================
  Hits         1319     1319
  Misses          8        8

Files Changed
Coverage Δ

src/astro/FunctionalAstrolabe.ts
98.78% <100.00%> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Feature vectors

Hi,
I am not able to download the feature vectors from the links given in the page. I have permission issues to access dropbox files from my machine. Could you please share the files.

which one can't you download? It seems that others don't meet this issue.


Check bulk deletion result before posting success

Prior to this change, bulkDelete did not report success/error status to the caller. So from the calling context we always assumed success.
With this change, we now return a status boolean that is checked before notifying the user of a successful job run.
Fixes #1

Linting in C/I is currently failing. That will be fixed in #9


DOC: Update Returns section of optimize.linprog.

Update the description of the OptimizeResult object to
note that the return type of the individual fields depends on
whether the optimization terminates successfully.
Add recommendation for users to check the OptimizeResult.success
attribute prior to any subsequent analysis.
I thought this was less invasive than changing the parameter types for the individual fields to or None, but YMMV.
Closes #16466 as the result notes have already been updated.

Thanks @rossbar!


docs: update docs for YAML 1.2 compatibility mitigation

See https://github.com/iterative/dvc/issues/5971
adds note to parameter values section metioning scientific notation for SEO
use ruamel.yaml in example instead of PyYAML and add note

You may disregard these recommendations if you used the Edit on GitHub button from dvc.org to improve a doc in place.

❗ Please read the guidelines in the Contributing to the Documentation list if you make any substantial changes to the documentation or JS engine.
🐛 Please make sure to mention Fix #issue (if applicable) in the description of the PR. This causes GitHub to close it automatically when the PR is merged.
Please choose to allow us to edit your branch when creating the PR.
Thank you for the contribution - we'll try to review it as soon as possible. 🙏

Thank you @bobertlo! I left some comments but also open to merging as is and iterating since it's already an improvement.

Sure! I had similar thoughts about the structure of the changes and wasn’t
sure how to approach it.
How would you feel about making “parameter values” a (linkable) heading
with a full description and in a note offering solutions and the code
examples could just mention PyYAML briefly after the examples and link back?
I could send a revision back for review with that later and I will look for
the other examples using PyYAML at least to include them in this review.
On Mon, May 23, 2022 at 11:02 AM Dave Berenbaum @.***>
wrote:

Thank you @bobertlo https://github.com/bobertlo! I left some comments
but also open to merging as is and iterating since it's already an
improvement.
—
Reply to this email directly, view it on GitHub
https://github.com/iterative/dvc.org/pull/3579#issuecomment-1134861006,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAGWHGMAIMGPHOOWABEG7ELVLOT2BANCNFSM5WR2DC6A
.
You are receiving this because you were mentioned.Message ID:
@.***>

@bobertlo I'm not sure without seeing it but could be nice. As I mentioned before, I'm open to merging as is or in any form that's better than what we have today (no warning about YAML incompatibility).

Maybe it would be good to just merge this and the other points can be
addressed separately.
My first concern is catching the “dvc parameters scientific notation”
Google search with a solution ;)
On Mon, May 23, 2022 at 1:29 PM Dave Berenbaum @.***>
wrote:

@bobertlo https://github.com/bobertlo I'm not sure without seeing it
but could be nice. As I mentioned before, I'm open to merging as is or in
any form that's better than what we have today (no warning about YAML
incompatibility).
—
Reply to this email directly, view it on GitHub
https://github.com/iterative/dvc.org/pull/3579#issuecomment-1135003698,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAGWHGKSVJJJ4WOXTKDL4QLVLPFADANCNFSM5WR2DC6A
.
You are receiving this because you were mentioned.Message ID:
@.***>

I did my best to reconcile some of the ideas mentioned and got the other two places where import yaml was included in examples.
Feel free to make any language edits you feel are helpful if needed.


mysql: "show collation" cannot handle *uint64

Describe the bug
Given a MySQL source @sakila/my8, this error is returned.
$ sq --src @sakila/my8 sql "show collation"
sq: column 2 Id: unknown type db(*uint64) with kind(int), val(0x1400024c060)

Fixed in #253, released in v0.37.1.


Add type params list to method signature in completion popup

Depends on ensime/ensime-server#1504

Looks like the server side is coming along nicely in ensime/ensime-server#1539 / ensime/ensime-server#1546, nice work 👏

We will need to support server 2.0 to add this

Development of this task can be started after solving #300


forge script --verify --resume does not retry all latest transactions

Component
Forge
Have you ensured that all of these are up to date?

[X] Foundry
[X] Foundryup

What version of Foundry are you on?
forge 0.2.0 (63ed109 2022-08-09T00:20:50.211015Z)
What command(s) is the bug in?
forge script --verify
Operating System
macOS (Apple Silicon)
Describe the bug
I have deployed multiple contracts through scripting using forge script --broadcast --verify and ran into the problem
Error:
Etherscan could not detect the deployment.

Usually, I am able to continue contract verification by running forge script --verify --resume. This time, however, forge will only retry verification of only 1/5 contracts.

Re-running doesn't change this.
If I look into broadcast/../run-latest.json I see all of the CREATE transactions and nothing seems unusual to me.

So after troubleshooting over DMs, two issues came out of here.

Contract 1: one of the transaction receipts had the wrong transactionIndex. I'm not sure how this could have happened. It's important, since we sort the receipts using that field. This lead to mismatched bytecode/contract/transaction/receipt. (1)

Contract 2: we were comparing bytecodes of different compiled versions of the same contract. However, we didn't show any kind of information regarding that. We just skip that contract.

@joshieDo @0xPhaze is this still an issue, or have changes to the script code since august resolved the two issues above?

I think there might have been multiple confounding factors. The overall experience has improved a lot and I would not be able to reproduce this atm, so closing for now.


Add getOrders method

Please follow what we have in sdk-node https://github.com/smartpay-co/sdk-node/pull/10/files

@linmic hi

@othree
Here is the PR for this feature: https://github.com/smartpay-co/sdk-ruby/pull/9
Thanks!


Mutated Issue: Allele "N" is not being annotated

VEP is able to annotate allele 'N'. Seems like GN/annotator is not accepting it - no annotation returned.
Example:
in ov_pancan
No result when querying GN:
http://annotation.genomenexus.org/annotation/genomic/1%2C205068920%2C205068922%2CGAT%2CANA?isoformOverrideSource=uniprot&fields=hotspots%2Cmutation_assessor
VEP returned result: http://grch37.ensembl.org/Homo_sapiens/Tools/VEP/Results?tl=9cdceSKfKPbBAc66-6575311

For more examples and complete "mutated" variants stats, please check here:
https://docs.google.com/spreadsheets/d/1RFj8zzMPv4PCAs3sFM9ro3FP4vRg-Za-JI2AFlx6FHg/edit#gid=1944280727

Updated VEP return Link: https://grch37.ensembl.org/Homo_sapiens/Tools/VEP/Results?tl=jHzc3RYzAUWhB27T-9525994
No result when querying GN: https://www.genomenexus.org/annotation/genomic/1%2C205068920%2C205068922%2CGAT%2CANA?fields=annotation_summary

If we fix the annotator to provide variant classification most of these mutations would be filtered out (intronic etc)

Removing !id.contains("-") from https://github.com/genome-nexus/genome-nexus/blob/master/service/src/main/java/org/cbioportal/genome_nexus/service/cached/CachedVariantAnnotationFetcher.java#L37C16-L37C33 can fix the failing annotation


Add a hybrid mode to MultiDict

AFAIK, currently you can either convert a MultiDict to a dict of lists or a dict of single values.
An hybrid conversion would be great so that single values keep their values while repeated values are shown as lists.
Currently, this can be done with the Python cgi module and its form.getvalue method
m = MultiDict([('a', 'b'), ('a', 'c'), ('e', 'f')])
m.to_something()
{'a': ['b', 'c'], 'e': 'f'}

Or even better, to avoid confusion, being able to specify a list of exceptions to return as lists:
m.to_dict(as_list=['a'])
{'a': ['b', 'c'], 'e': 'f'}
m.to_dict(as_list=['e'])
{'a': 'b', 'e': ['f']}

In general, the developer know that such field of a form can return multiple values, type conversion at the early stages like that could be very useful.
FYI: I'm currently porting an app using the cgi module to flask and request.form is a MultiDict. I'd rather not to have to write a helper function to convert the MultiDict. All this to be able to use pyextdirect with a few lines of code.

I'm sure there was a good reason to having the multidict return only 1 value even though a key holds several, but I'm afraid I can't think of it.
Consider writing an API that accepts both form-data and json data requests. I have no way of easily converting the multidict to it's json equivalent, that is exactly what has been requested above:
 {'a': ['b', 'c'], 'e': 'f'}
So now I have to go through hoops to convert it into a simple dictionary that only has lists where lists are needed. This seems like an awkward thing to do. Any chance we can reconsider this?

@vitriol the whole problem is already malformed. What you are trying to do there is just dangerous.  Don't do that :)


terminate called after throwing an instance of 'std::system_error'

Hello!
I am getting this error:
terminate called after throwing an instance of 'std::system_error'
  what():  Enable multithreading to use std::thread: Operation not permitted

My OS is Ubuntu 14.04.
$ cmake --version
cmake version 3.10.2
CMake suite maintained and supported by Kitware (kitware.com/cmake).
$ gcc
gcc             gcc-4.8         gcc-ar          gcc-ar-4.8      gcc-nm          gcc-nm-4.8      gcc-ranlib      gcc-ranlib-4.8

Thanks!
Gabriel

Hi Gabriel,
please run gcc --version and paste the result. Might be a bug with a specific gcc version..
Best regards,
Robert

$ gcc --version
gcc (Ubuntu 4.8.4-2ubuntu1~14.04.3) 4.8.4
Copyright (C) 2013 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Thanks Robert!

Try adding -Wl,--no-as-needed to CMakeLists.txt at line 8 after -pedantic. Run cmake and compile with make.

As it is a compiler specific bug I won't add the flags to master branch. You can either update your compiler to 4.8.5 or have this fix in your local installation :)
Best,
Robert

@rvaser I face the similar issue while executing the exe from the cmake.
terminate called after throwing an instance of 'std::logic_error'
what():  basic_string::_S_construct null not valid
Aborted
My gcc version is:
gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-39)
Cmake version is:
cmake3 version 3.17.3
As per you suggestion in this post, I tried to add flags in the CMakeLists.txt but the error still persists. Can you please assist me on this?

Hi @divyakundala,
which version of Racon are you using?
Best regards,
Robert

Hi @rvaser ,
I don't have racon installed in my system.
racon --version
-bash: racon: command not found

Could you please paste all the commands you used for compilation? On the other hand, you can always use Racon from bioconda.

terminate called after throwing an instance of 'std::system_error'
what():  Invalid argument
how to solve


[Azure] Add sovereign cloud support for MySQL

The Base URI is incorrectly resolved for the MySQL client, and should be fixed to read from the environment.
Addresses #811

@yorinasub17 can we close it. the changes were merged in #884

Closing!


Comparison with Guidance?

I appreciate your effort for making LMQL. I've played with it a bit and found many of the concepts it does are similar to what Guidance does. But I'm not too tech-savvy to know the technical differences between the two. Before starting my project using one of these frameworks, I wanted you to please make a comparison of the two. I think that would clarify the strengths of each framework and help people like me make the right decision.
thank you!

This is a good question, LMQL and Guidance for sure have some similarities. We agree that a deeper comparison would be useful and will add a corresponding chapter to our documentation. I will keep this issue open, until then.

Hey, how about trying out some comparison between the both based on some of the simple BigBench tasks, maybe anachronism itself? I think Guidance claims to perform better than the few-shot + no chain-of-thought output structure cases.

Please feel free to have a look :). From a LLM performance perspective the implementation/tooling level will not really matter though, as long as the concrete tokens/constraints you give to the model are the same, the results will be the same, so I would expect the same gains as in the guidance experiments.
Still, using different capabilities of LMQL (e.g. scripting, constraining) we were able to show significant gains on a wide range of benchmarks across several papers we are currently working on. The experimental evaluation of this will of course be published in due time.

We have added a comprehensive comparison with guidance to the documentation. Please feel free to comment here, any additional questions that come up, so we can extend it.
https://docs.lmql.ai/en/latest/python/comparison.html

Thanks! This was informative. I admire the way you guys are working on LMQL. It feels like a serious package with all the comprehensive documentation and examples. Hope it gets more traction by the community.


Remote Debugging Filter Change and Azure Scenario Support

Changed attachable logic to use Get-PSHostProcessInfo as the filter for finding attachable processes. This is much more accurate than looking for the powershell.exe module. Added an alternative remote debugging transport which utilizes SSL. This will allow users to connect to Azure VMs. Also added the ability to specify a port. Not a very likely scenario, but Azure lets you change the PowerShell connection port so it may be useful to some users.
Resolves #673
@EricMSFT @AndreSayreMSFT @HuanhuanSunMSFT

Good work!

looks good


Actual behavior
It fails with:
  File "/Users/harshcasper/qhub/env/bin/qhub", line 8, in <module>
    sys.exit(main())
  File "/Users/harshcasper/qhub/qhub/__main__.py", line 7, in main
    cli(sys.argv[1:])
  File "/Users/harshcasper/qhub/qhub/cli/__init__.py", line 51, in cli
    args.func(args)
  File "/Users/harshcasper/qhub/qhub/cli/destroy.py", line 38, in handle_destroy
    destroy_configuration(config)
  File "/Users/harshcasper/qhub/qhub/destroy.py", line 173, in destroy_configuration
    stage_outputs = gather_stage_outputs(config)
  File "/Users/harshcasper/qhub/qhub/destroy.py", line 66, in gather_stage_outputs
    input_vars=input_vars.stage_07_kubernetes_services(stage_outputs, config),
  File "/Users/harshcasper/qhub/qhub/stages/input_vars.py", line 261, in stage_07_kubernetes_services
    "realm_id": stage_outputs["stages/06-kubernetes-keycloak-configuration"][
KeyError: 'realm_id'

How to Reproduce the problem?

Create a QHub deployment on GCP.

Command output
No response
Versions and dependencies used.
QHub: v0.4.4rc3
Compute environment
GCP
Integrations
No response
Anything else?
No response

Hi @HarshCasper, this issue normally happens when:

The first deployment did not fully complete
Or, when you run qhub destroy twice

Would you mind trying to reproduce this again?

I also had qhub destroy on GCP fail for me (v0.4.3). This was the end of my logs:
[terraform]: Destroy complete!  For cloud deployments of QHub typically only stages 01 and 02 need to succeed to properly destroy everything

Not sure if there was error that got lost somewhere in the terraform output.

Hi @kcpevey, this is an expected message, it means that all infrastructure-related resources managed directly by terraform were removed, but some resources created by the cloud provider (sometimes a network connection, security groups, etc) were not removed due to Terraform not knowing any information about these.
So, in short, that message means that you should confirm manually that there is no lingering resource in the cloud side.

The nebari destroy is working for GCP. Closing this issue.


feat: add .catch error

Introduction
Hey 👋🏻
This PR introduces a way to collect a ZodError when using .catch method, which can be useful in many case when wanting to collect logs whenever default value is used.
Example
const numberWithErrorCatch = z.number().catch((e) => {
  console.error(e);

  return 42;
});

// No error shown in console.
numberWithErrorCatch.parse(5); // => 5

// Default value is returned, an error will be shown in console.
numberWithErrorCatch.parse("tuna"); // => 42

Great stuff! Made a small tweak - passing a ctx object into the catch handler to leave room for future APIs and so we can avoid instantiating a ZodError instance if the validation passes. Creating Errors in JavaScript is slow/expensive.


[EXAMPLES]: add example of full inspection cycle

Add an example of a basic but full inspection cycle modeled after the following state diagram:
flowchart TD
    A(Start) --> B(Create new inspection)
    B --> C(Grab first part)
    C --> D(Take picture of first part)
    D --> E(Upload picture to API)
    E --> F{Inspection result for first part}
    F -->|Not good| G(Drop part)
    G --> C
    F -->|Good| H(Grab second part)

    H --> L(Take picture of second part)
    L --> M(Upload picture to API)
    M --> N{Inspection result for second part}
    N -->|Not good| O(Drop part)
    O --> K
    N -->|Good| P(Close inspection)
    P --> Q(End)

This is a comment on your flow diagram. You are missing the step to place the first and second part at the right location once they are good.

I removed it because this because it is very specific to the customer's inspection process. Remember that this repo is public (and all PRs and reviews as well)


fix(Cloud Databases): update database configuration options

PR summary
Adds missing database configuration options for various database types
PR Checklist
Please make sure that your PR fulfills the following requirements:

[x] The commit message follows the Angular Commit Message Guidelines.
[x] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been added / updated (for bug fixes / features)

PR Type

[x] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] New tests
[ ] Build/CI related changes
[ ] Documentation content changes
[ ] Other (please describe)

What is the current behavior?

What is the new behavior?

Does this PR introduce a breaking change?

[ ] Yes
[ ] No

Other information

:tada: This PR is included in version 0.3.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Update cats-effect and fs2 to non-RC versions

Codecov Report

Merging #882 (0a6c6ad) into series/0.6.x (e26bd16) will not change coverage.
The diff coverage is n/a.

@@              Coverage Diff              @@
##           series/0.6.x     #882   +/-   ##
=============================================
  Coverage         83.89%   83.89%
=============================================
  Files               126      126
  Lines              1757     1757
  Branches            154      154
=============================================
  Hits               1474     1474
  Misses              283      283


Getting SSH Handshake Failed on Alma 9

Hi, I'm trying to build Alma 9 images, but I'm encountering an SSH handshake error: 'ssh: handshake failed: read tcp <IP_ADDRESS>:59326-><IP_ADDRESS>:3346: read: connection reset by peer'. Can you please help?"

Hi Akash, Could you please share more information from you setup?

Which image are trying to build?
Host OS
Packer version

Hi @LKHN , below are the required details of my environment:

Which image are you trying to build?
qemu.almalinux-9-gencloud-x86_64

Host OS:
Kubuntu 22.04.4 LTS x86_64

Packer version:
Packer v1.10.3

Building BIOS images is working, but when I try for UEFI, it gets stuck on the SSH connection part.

Hi @LKHN , I tried building UEFI images and also opened a local VNC viewer. It shows on screen  "guest has not initialized the display (yet)", while the console is attempting to SSH into it.
Packer Logs:
2024/05/04 09:33:24 packer-plugin-qemu_v1.1.0_x5.0_linux_amd64 plugin: 2024/05/04 09:33:24 Special code '<enter>' found, replacing with: 0xFF0D
2024/05/04 09:33:24 packer-plugin-qemu_v1.1.0_x5.0_linux_amd64 plugin: 2024/05/04 09:33:24 [INFO] Waiting 1s
    qemu.almalinux-9-gencloud-x86_64: Not using a NetBridge -- skipping StepWaitGuestAddress
==> qemu.almalinux-9-gencloud-x86_64: Using SSH communicator to connect: <IP_ADDRESS>
2024/05/04 09:33:25 packer-plugin-qemu_v1.1.0_x5.0_linux_amd64 plugin: 2024/05/04 09:33:25 [INFO] Waiting for SSH, up to timeout: 1h0m0s
==> qemu.almalinux-9-gencloud-x86_64: Waiting for SSH to become available...
2024/05/04 09:33:25 packer-plugin-qemu_v1.1.0_x5.0_linux_amd64 plugin: 2024/05/04 09:33:25 [INFO] Attempting SSH connection to <IP_ADDRESS>:2291...
2024/05/04 09:33:25 packer-plugin-qemu_v1.1.0_x5.0_linux_amd64 plugin: 2024/05/04 09:33:25 [DEBUG] reconnecting to TCP connection for SSH
2024/05/04 09:33:25 packer-plugin-qemu_v1.1.0_x5.0_linux_amd64 plugin: 2024/05/04 09:33:25 [DEBUG] handshaking with SSH
2024/05/04 09:34:25 packer-plugin-qemu_v1.1.0_x5.0_linux_amd64 plugin: 2024/05/04 09:34:25 [DEBUG] SSH handshake err: Timeout during SSH handshake
2024/05/04 09:34:32 packer-plugin-qemu_v1.1.0_x5.0_linux_amd64 plugin: 2024/05/04 09:34:32 [INFO] Attempting SSH connection to <IP_ADDRESS>:2291...
2024/05/04 09:34:32 packer-plugin-qemu_v1.1.0_x5.0_linux_amd64 plugin: 2024/05/04 09:34:32 [DEBUG] reconnecting to TCP connection for SSH
2024/05/04 09:34:32 packer-plugin-qemu_v1.1.0_x5.0_linux_amd64 plugin: 2024/05/04 09:34:32 [DEBUG] handshaking with SSH
2024/05/04 09:35:32 packer-plugin-qemu_v1.1.0_x5.0_linux_amd64 plugin: 2024/05/04 09:35:32 [DEBUG] SSH handshake err: Timeout during SSH handshake
2024/05/04 09:35:39 packer-plugin-qemu_v1.1.0_x5.0_linux_amd64 plugin: 2024/05/04 09:35:39 [INFO] Attempting SSH connection to <IP_ADDRESS>:2291...
2024/05/04 09:35:39 packer-plugin-qemu_v1.1.0_x5.0_linux_amd64 plugin: 2024/05/04 09:35:39 [DEBUG] reconnecting to TCP connection for SSH
2024/05/04 09:35:39 packer-plugin-qemu_v1.1.0_x5.0_linux_amd64 plugin: 2024/05/04 09:35:39 [DEBUG] handshaking with SSH
2024/05/04 09:36:39 packer-plugin-qemu_v1.1.0_x5.0_linux_amd64 plugin: 2024/05/04 09:36:39 [DEBUG] SSH handshake err: Timeout during SSH handshake
2024/05/04 09:36:46 packer-plugin-qemu_v1.1.0_x5.0_linux_amd64 plugin: 2024/05/04 09:36:46 [INFO] Attempting SSH connection to <IP_ADDRESS>:2291...
2024/05/04 09:36:46 packer-plugin-qemu_v1.1.0_x5.0_linux_amd64 plugin: 2024/05/04 09:36:46 [DEBUG] reconnecting to TCP connection for SSH
2024/05/04 09:36:46 packer-plugin-qemu_v1.1.0_x5.0_linux_amd64 plugin: 2024/05/04 09:36:46 [DEBUG] handshaking with SSH
2024/05/04 09:37:46 packer-plugin-qemu_v1.1.0_x5.0_linux_amd64 plugin: 2024/05/04 09:37:46 [DEBUG] SSH handshake err: Timeout during SSH handshake
2024/05/04 09:37:53 packer-plugin-qemu_v1.1.0_x5.0_linux_amd64 plugin: 2024/05/04 09:37:53 [INFO] Attempting SSH connection to <IP_ADDRESS>:2291...
2024/05/04 09:37:53 packer-plugin-qemu_v1.1.0_x5.0_linux_amd64 plugin: 2024/05/04 09:37:53 [DEBUG] reconnecting to TCP connection for SSH
2024/05/04 09:37:53 packer-plugin-qemu_v1.1.0_x5.0_linux_amd64 plugin: 2024/05/04 09:37:53 [DEBUG] handshaking with SSH
2024/05/04 09:38:53 packer-plugin-qemu_v1.1.0_x5.0_linux_amd64 plugin: 2024/05/04 09:38:53 [DEBUG] SSH handshake err: Timeout during SSH handshake
2024/05/04 09:39:00 packer-plugin-qemu_v1.1.0_x5.0_linux_amd64 plugin: 2024/05/04 09:39:00 [INFO] Attempting SSH connection to <IP_ADDRESS>:2291...
2024/05/04 09:39:00 packer-plugin-qemu_v1.1.0_x5.0_linux_amd64 plugin: 2024/05/04 09:39:00 [DEBUG] reconnecting to TCP connection for SSH
2024/05/04 09:39:00 packer-plugin-qemu_v1.1.0_x5.0_linux_amd64 plugin: 2024/05/04 09:39:00 [DEBUG] handshaking with SSH
2024/05/04 09:40:00 packer-plugin-qemu_v1.1.0_x5.0_linux_amd64 plugin: 2024/05/04 09:40:00 [DEBUG] SSH handshake err: Timeout during SSH handshake
2024/05/04 09:40:07 packer-plugin-qemu_v1.1.0_x5.0_linux_amd64 plugin: 2024/05/04 09:40:07 [INFO] Attempting SSH connection to <IP_ADDRESS>:2291...
2024/05/04 09:40:07 packer-plugin-qemu_v1.1.0_x5.0_linux_amd64 plugin: 2024/05/04 09:40:07 [DEBUG] reconnecting to TCP connection for SSH
2024/05/04 09:40:07 packer-plugin-qemu_v1.1.0_x5.0_linux_amd64 plugin: 2024/05/04 09:40:07 [DEBUG] handshaking with SSH
2024/05/04 09:41:07 packer-plugin-qemu_v1.1.0_x5.0_linux_amd64 plugin: 2024/05/04 09:41:07 [DEBUG] SSH handshake err: Timeout during SSH handshake
2024/05/04 09:41:14 packer-plugin-qemu_v1.1.0_x5.0_linux_amd64 plugin: 2024/05/04 09:41:14 [INFO] Attempting SSH connection to <IP_ADDRESS>:2291...
2024/05/04 09:41:14 packer-plugin-qemu_v1.1.0_x5.0_linux_amd64 plugin: 2024/05/04 09:41:14 [DEBUG] reconnecting to TCP connection for SSH
2024/05/04 09:41:14 packer-plugin-qemu_v1.1.0_x5.0_linux_amd64 plugin: 2024/05/04 09:41:14 [DEBUG] handshaking with SSH
2024/05/04 09:42:14 packer-plugin-qemu_v1.1.0_x5.0_linux_amd64 plugin: 2024/05/04 09:42:14 [DEBUG] SSH handshake err: Timeout during SSH handshake
2024/05/04 09:42:21 packer-plugin-qemu_v1.1.0_x5.0_linux_amd64 plugin: 2024/05/04 09:42:21 [INFO] Attempting SSH connection to <IP_ADDRESS>:2291...
2024/05/04 09:42:21 packer-plugin-qemu_v1.1.0_x5.0_linux_amd64 plugin: 2024/05/04 09:42:21 [DEBUG] reconnecting to TCP connection for SSH
2024/05/04 09:42:21 packer-plugin-qemu_v1.1.0_x5.0_linux_amd64 plugin: 2024/05/04 09:42:21 [DEBUG] handshaking with SSH

@AkashRajvanshi
I just tested the the distros listed below because of the #176 . Haven't experienced any issue.
Can you clone the repo and test again with the recently merged changes?

Debian 12
Debian 11
Fedora 40
Fedora 39
Fedora 38
Ubuntu 24.04 LTS
Ubuntu 22.04 LTS
Ubuntu 20.04 LTS
OpenSUSE Leap 15.5

Hi @LKHN , I did the test with :
Packer 1.9.1
Host: Ubuntu 22.04
Image: qemu.almalinux-9-gencloud-x86_64
The only think that I changed is that it create LVM, but should not be an issue. As a result has the same SSH issue. Any suggestions?

@VladyslavTkachenkoDesy
Can you disable the headless mode to able to see whether the VM is booted after the installation or not?
export PKR_VAR_headless='false'


could kubegres made upgrade major posgresql version without downtime?

Hello guys, thanks for your great work ;) kubegres look like simple operator which cover most of my use cases, but
could kubegres made upgrade major posgresql version without downtime?
will you run pg_upgrade if I will change PostgreSQL image in custom resource to v14?

Thank you so much for your kind feedback. Excellent suggestion. I am going to add it to our backlog now.
Currently, Kubegres allows upgrading the versions of a Postgres container without any specific logics meaning it deleguates to that to postgres container .
Postgresql guarantees compatibilities between minor versions upgrade (e.g. 13.1 to 13.3) and consequently it's working fine with Kubegres.
However, as you rightly suggested, if there is an attempt to upgrade a Postgres container with a major version (e.g. from version 12 to 13), PostgreSql will not allow it.
We will add a logic to run the "pg_upgrade" command as you mentioned.
I am going to use this ticket as a feature enhancement.
Thank you!


Show Neoletter mailings in UI

This excludes mailing content from multi-site logic and grey the mailings site out in the UI.
Update: actually the UI actively hides the Mailing site.
https://github.com/Scrivito/scrivito-portal-app/pull/359#discussion_r1570356792

REVIEW
B/c of assumptions of the Neoletter mailing app's site config, at the moment editors can't select any other site after they switched to the mailings.


Stacker doesn't validate that key found in metadata explicitly matches project prefix.

The stacker module does fuzzy matching on the prefix from the bucket object metadata. This leads to unexpected results when multiple prefixes match what's in the taskcat config.
More validation is needed to ensure only the keys with the prefix explicitly matching the config variable are used to generate the template URL.
Examples are sanitized, but this is a duplicate of the stacker module, lines 407-412 (get_s3_url function).  The only difference is this, for debugging purposes.
foo.append(metdata[1])

/////
>>> for s3obj in contents:
...     for metadata in s3obj.items():
...             if metadata[0] == 'Key':
...                     if key in metadata[1]:
...                             foo.append(metadata[1])
...
>>> foo
['example.old/LICENSE.txt', 'example/LICENSE.txt']

PR Forthcoming.

Fixed in https://github.com/aws-quickstart/taskcat/commit/7360917585f5a0f24027259950cbd82c344f0aa1


Implement real-time face recognition

This is our current long-term goal of the project, and I'm not sure how far off it is. The idea is that this system receives a video stream, and for each frame it extracts faces, attempts to classify each face, and reports the results. This system will probably be a combination of our current code, the pre-processing scripts that will be developed, and probably a server that watches the stream, delegates tasks, and displays results. The server might have the following behavior:
initialize()

on_receive (video_frame):
  images = detect_faces(video_frame)  # run detect-faces.py
  images = normalize(images)  # run normalize.py
  for img in images:
    class = face_rec(img)  # run face-rec
    print(class)

Hey, that's starting to look a lot like Python code! Anyway, we can use this thread to discuss details of this task as it becomes more relevant.

We should be able to call ./face-rec from a python script and use the --stream option to run inference on images as they come int:
# train a model
./face-rec --train train_data --pca --pca_n1=50

# (in the python script)
# - start streaming server
./face-rec --stream stream_data --pca --pca_n1=50

# - save detected images to stream_data
# - run inference on detected images (send '1' to ./face-rec)
# - read predictions from ./face-rec output

Real-time detection and recognition is now implemented by scripts/face-det/face-rec.py. There are still performance issues on the Jetson which we may try to work out, and we should try to run it on a faster system to make sure it runs smoothly there.


change fmt.Errorf to errors.NewBadRequest

What type of PR is this?

/kind api-change
What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #
Special notes for reviewers:

Please check the following list before waiting reviewers:

[ ] Already committed the CRD files to the Helm Chart if you created some new CRDs
[ ] Already added the permission for the new API
[ ] Already added the RBAC markers for the new controllers

Does this PR introduce a user-facing change??

change fmt.Errorf to errors.NewBadRequest

/lgtm
/approve

/cherrypick release-3.4


Install file broken

Downloaded the latest release and it says the file i changed or broken

https://support.techsmith.com/hc/en-us/articles/203732398-Snagit-Mac-You-can-t-open-the-application-Snagit-app-because-it-may-be-damaged-or-incomplete


Collated Code

Not included:

Imports
Refactorings
Trivial stuff
Stuff added in v1.4, since this is a test run only.

Coverage remained the same at 92.056% when pulling 515cf1d9a8c2af6641a8acd0a456d566ecbc3ca7 on ZY-Ang:Collated into d4017e08a3baf681673001fc2db51292f1b4d9ea on CS2103AUG2017-W11-B2:master.

Coverage remained the same at 92.056% when pulling 2abb68271b4bd480f65e0619b13885b9b96db1b7 on ZY-Ang:Collated into d4017e08a3baf681673001fc2db51292f1b4d9ea on CS2103AUG2017-W11-B2:GeneralDocumentation.


Recursion error when unpickling Lineups/Players

I wanted to save some lineups to disk, so I wrote them to a pickle file
import pickle

lineups = []
for lu in optimizer.optimize(20):
    lineups.append(lu)

with open('/home/sansbacon/workspace/pangadfs-pydfsoptimizer/lineups.pkl', 'wb') as f:
    pickle.dump(lineups, f, protocol=5)

However, when I tried to unpickle the Lineup/Player objects, I got a recursion error, which appears to stem from the implementation of Player.__getattr__.
<ipython-input-19-2f24190ed9b3> in <module>
      1 with open('/home/sansbacon/workspace/pangadfs-pydfsoptimizer/lineups.pkl', 'rb') as f:
----> 2     data = pickle.load(f)
      3

~/miniconda3/envs/pynfldfscash/lib/python3.8/site-packages/pydfs_lineup_optimizer/player.py in __getattr__(self, attr_name)
    134
    135     def __getattr__(self, attr_name):
--> 136         return getattr(self._player, attr_name)
    137
    138     def __eq__(self, other):

... last 1 frames repeated, from the frame below ...

~/miniconda3/envs/pynfldfscash/lib/python3.8/site-packages/pydfs_lineup_optimizer/player.py in __getattr__(self, attr_name)
    134
    135     def __getattr__(self, attr_name):
--> 136         return getattr(self._player, attr_name)
    137
    138     def __eq__(self, other):

RecursionError: maximum recursion depth exceeded

A workaround for this issue is to change the implementation of getattr in LineupPlayer
    def __getattr__(self, attr_name):
        return vars(self._player).get(attr_name)
        #return getattr(self._player, attr_name)


Add to Package Control

Awesome work!!!!! 💯
Do you plan on adding this to packagecontrol.io?

Still not available in-app


Add remaining 1.6 release features

The following items need to be documented on the release-1.6 branch:

[ ] Remove preview labels from 1.5 features
[ ] Double underscore cursor - https://github.com/microsoft/terminal/pull/7827
[ ] Startup actions - https://github.com/microsoft/terminal/pull/8770
[ ] move-focus subcommand - https://github.com/microsoft/terminal/pull/8546
[ ] size parameter for splitPane and split-pane - https://github.com/microsoft/terminal/pull/8543
[ ] Custom pixel shaders - https://github.com/microsoft/terminal/pull/8565
[ ] Open settings UI command - https://github.com/microsoft/terminal/pull/8048
[ ] Navigating panes by MRU - https://github.com/microsoft/terminal/pull/8183
[ ] scrollhome and scrollend actions - https://github.com/microsoft/terminal/pull/8459
[ ] launchMode on commandPalette action - https://github.com/microsoft/terminal/pull/8382
[ ] tabColor parameter - https://github.com/microsoft/terminal/pull/8102
[ ] Tab switcher defaults to inOrder - https://github.com/microsoft/terminal/pull/8326
[ ] Bell style - https://github.com/microsoft/terminal/pull/8215

Many of these already have associated pull requests. Should we link them here?

Many of these already have associated pull requests. Should we link them here?

Yep! That’s my next step. :)

Yep! That’s my next step. :)


[Bug] Flaky DeploymentNotFound Error when deploying subgraphs

Bug report
Running a self hosted graph-node on v0.31.0.
Noticed a flaky siutation where sometimes the subgraph deployment would fail due to the DeploymentNotFound error.  Even though graph-cli reports an error, the subgraph seems to start indexing properly.
Subsequent deploys of the same IPFS hash will result in a different error: duplicate key value violates unique constraint "subgraph_deployment_id_key".
Traced down into the code to see that it is likely coming from create_deployment_internal.
set_on_sync called by create_deployment is one potential spot, but checking the subgraph_manifest table shows no missing rows.
create_subgraph_version is another possible spot, but the subgraph_deployment table looks fine as well.
Perhaps these tables were not populated correctly at time of the error due to a race condition or database issue?  Looking at metrics, the database was not under a lot of load at the time.
Would appreciate any second eyes on this, as it is a flaky error that has not been successfully reproduced yet while debugging.
Relevant log output
# Log from graph-node on first deployment
Jul 11 16:44:26.941 ERRO subgraph_deploy failed, params: SubgraphDeployParams { name: SubgraphName("c47020ff-bcc6-44f4-8296-9b0ec6cb783b"), ipfs_hash: DeploymentHash("QmYSk536LvM4fqqqCVDzjCqsNochPcnwPGXFkWbUCHzLBP"), node_id: None, debug_fork: None, history_blocks: None }, error: SubgraphDeploymentError(DeploymentNotFound("QmYSk536LvM4fqqqCVDzjCqsNochPcnwPGXFkWbUCHzLBP")), component: JsonRpcServer

# Log from graph-node on subsequent deployment
Jul 12 10:14:25.099 ERRO subgraph_deploy failed, params: SubgraphDeployParams { name: SubgraphName("d94932a4-daca-4443-84dd-fddc1169cab7"), ipfs_hash: DeploymentHash("QmYSk536LvM4fqqqCVDzjCqsNochPcnwPGXFkWbUCHzLBP"), node_id: None, debug_fork: None, history_blocks: None }, error: SubgraphDeploymentError(Unknown(duplicate key value violates unique constraint "subgraph_deployment_id_key")), component: JsonRpcServer

IPFS hash
No response
Subgraph name or link to explorer
No response
Some information to help us out

[ ] Tick this box if this bug is caused by a regression found in the latest release.
[ ] Tick this box if this bug is specific to the hosted service.
[X] I have searched the issue tracker to make sure this issue is not a duplicate.

OS information
Linux

Hey @kevin-satsuma can you elaborate when does this DeploymentNotFound error occur? Is it random?

Sure!  The DeploymentNotFound error seems to be random so far.  When the error occurs, resource usage on the indexer and database both look normal as well.  This has made it difficult to investigate without the ability to reproduce the error on demand.

hey @kevin-satsuma is this running in combined mode, with a single database (i.e. not using Graph Node sharding)?

@azf20 The graph-node instance showing this error is running with default node_role of combined-node, but we do not send any queries to it.  It uses a single database and does not use Graph Node sharding.


[feat] Make hook-related machinery available as class directives

This PR builds on #1929 to simplify and improve the syntax when writing test libraries. The run_before, run_after and require_deps decorators are now available as class directives, so there is no need for the preceding rfm. anymore:
class Foo(rfm.RegressionTest):
    ...
    @run_before('compile')
    def a_pre_compile_hook(self):
        # do something

    # The standard way is still supported
    @rfm.run_after('run')
    def a_post_run_hook(self):
        # do something else

This PR also introduces the bind directive, which binds an external function with the regression test class. This allows to write pipeline hooks as standalone unary functions, which can then be safely "imported" by several other classes.
# file handy_hooks.py
def ext_fn(x):
    # do something handy

# file mytest.py
from handy_hooks import ext_fn

class MyTest(rfm.RegressionTest):
    run_before('compile')(bind(ext_fn))

    # It is possible to bind the hook with a different name
    run_after('run')(bind(ext_fn, name='new_name'))

Not using the bind directive here might lead to problems because the function object ext_fn would be shared by multiple classes.
Issues with the current implementation
By moving these directives into the reframe/core/hooks.py I feel that the mapping of the argument to the run_before and run_after should be done in the metaclass and not by any of the functions in the hooks.py file. It's a bit strange to me that these hook functions are aware of the pipeline stages. It would feel a lot more natural if the directives exposed by the metaclass would preprocess this argument and do the mapping before calling any of the functions in hooks.py.
Alternatively, we could add some syntactic sugar into this and get rid of the mapping problem altogether by exposing directives to the pre_ and post_ steps of each individual pipeline stage. IMO, this would vastly improve the syntax above:
from handy_hooks import ext_fn

class MyTest(rfm.RegressionTest):
    pre_compile(bind(ext_fn))
    post_run(bind(ext_fn, name='new_name'))

Hello @jjotero, Thank you for submitting the Pull Request!

In the file reframe/core/meta.py:

Line 102:80: E501 line too long (85 > 79 characters)

Do see the ReFrame Coding Style Guide

Codecov Report

Merging #1969 (27e1768) into master (b457f82) will decrease coverage by 0.54%.
The diff coverage is 73.41%.

@@            Coverage Diff             @@
##           master    #1969      +/-   ##
==========================================
- Coverage   87.86%   87.32%   -0.55%
==========================================
  Files          50       50
  Lines        8668     8748      +80
==========================================
+ Hits         7616     7639      +23
- Misses       1052     1109      +57

Impacted Files
Coverage Δ

reframe/core/meta.py
84.67% <47.22%> (-15.33%)
:arrow_down:

reframe/core/hooks.py
93.85% <95.23%> (-0.74%)
:arrow_down:

reframe/core/decorators.py
77.77% <100.00%> (-5.42%)
:arrow_down:

reframe/core/logging.py
77.55% <0.00%> (-7.32%)
:arrow_down:

reframe/core/schedulers/pbs.py
47.26% <0.00%> (-0.33%)
:arrow_down:

reframe/frontend/runreport.py
92.98% <0.00%> (ø)

reframe/frontend/cli.py
75.64% <0.00%> (+0.04%)
:arrow_up:

Continue to review full report at Codecov.

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

@jjotero, I am not sure how this feature will evolve or be utilized...
I understand that there is potential to reuse hooks. I do not see any other benefit and I wonder if the gain compensates for the costs...
Do you have a proper use case for this feature?
Because when I check the cscs-checks folder, I  see that the hooks are test-dependent and cannot be used in any other check. Ok, this may be because we miss this feature, but at first glance, I cannot find any test that would really benefit from "hook reuse". It is possible that in my search I may have missed the key tests that would benefit, but still,  it looks to me that they are not the majority.
So, what's the other benefit of this feature?
Furthermore, I agree that the syntactic-sugar syntax is required. And I wonder if, in the simplified form, there could be an implicit bind call. So, instead of having
from handy_hooks import ext_fn

class MyTest(rfm.RegressionTest):
    pre_compile(bind(ext_fn))
    post_run(bind(ext_fn, name='new_name'))

one could write
from handy_hooks import ext_fn

class MyTest(rfm.RegressionTest):
    pre_compile(ext_fn)
    post_run(ext_fn, name='new_name')

So, what's the other benefit of this feature?

In the gpu microbenchmarks, the dgemm, shmem, kernel_latency, pointer_chase, memory_bandwidth and gpu_burn checks share the two hooks in /cscs-checks/microbenchmarks/hooks.py. In the current version, these checks manually bind the external hook by wrapping the external function; but that's a lot of typing :) So there the bind directive becomes very handy.
There is quite a lot of room at the hpctestlib level to use the bind directive there also on the same microbenchmarks from above. All the GPU microbenchmarks there also share some hooks.
Regarding the syntax, I agree that binding an external hook doing
class MyTest(rfm.RegressionTest):
    run_before('compile')(bind(ext_fn, name='local_fn'))

is perhaps worse than a manual bind such as
class MyTest(rfm.RegressionTest):
    @run_before('compile')
    def local_fn(self):
        ext_fn(self)

So that's why I think that the least we should do here is expose the pre_ & post_ decorators bound to a specific stage so we can do
from handy_hooks import ext_fn

class MyTest(rfm.RegressionTest):
    pre_compile(bind(ext_fn))
    post_run(bind(ext_fn, name='new_name'))

If you want to go further and make the bind transparent to the user, I'm fine with that, but I'd probably go for a more explicit name such as this
from handy_hooks import ext_fn

class MyTest(rfm.RegressionTest):
    inject_before_compile(ext_fn)
    inject_after_run(ext_fn, name='new_name'))

or instead
from handy_hooks import ext_fn

class MyTest(rfm.RegressionTest):
    inject_before('compile', ext_fn)
    inject_after('run', ext_fn, name='new_name'))

Here's another and perhaps a bit of a different use-case. Look at the affinity_check. It's got a few "utility" functions in there such as get_sibling_cpus.
https://github.com/eth-cscs/reframe/blob/8bd06ea60a55b00c31c1fc999749ad3619823148/cscs-checks/prgenv/affinity_check.py#L154
If this function is factored out into a test utils library, other tests could use it as follows
from hpctestlib.utils.topo import get_sibling_cpus

@rfm.simple_test
class MyTest(rfm.RegressionTest):
    ...
    bind(get_sibling_cpus)

    @run_before('run')
    def get_logical_cpus_per_core(self):
        self.num_cpus_per_core = len(self.get_sibling_cpus(0, by='core'))

I personally see the value of this proposal in this PR. Here are my general comments:

Do we still allow the rfm.run_before syntax?
I would vote against yet another syntax with the same meaning, such as pre_compile, inject_pre_compile etc. It will create more confusion. I like that the current proposal uses the same syntax and functionality: run_before() does exactly what it is expected to do as a decorator.
I don't see a problem with the bind() function: it takes a free function accepting at least one argument and binds it to the object.
I wouldn't argue that the one liner syntax is worse than the multiline, but again this is a matter of taste and, in fact, users can choose which one to use! I would definitely be one of those choosing the one liner.
I think adding the option to set the name of the bounded function is good, because it would avoid conflicts with other local methods.

I'd vote to schedule the drop for 4.0.
I think the current run_before & run_after decorators would make the one-liner syntax very (very) hard to read for non-Python people. When you use a decorator as @deco, all you need to know is that this decorator does something to the function below and the user might not know/care how that happens. However, if you use it as deco(...)(...), the user must know how decorators work in order to understand the syntax. That's something far more advanced, I think. In any case, I think that the syntax we use for the decorators is a full discussion on its own (I agree that the inject syntax probably causes more problems than solutions). So I'd say we get this PR done and we have that chat at some other time :)

I think the current run_before & run_after decorators would make the one-liner syntax very (very) hard to read for non-Python people. When you use a decorator as @deco, all you need to know is that this decorator does something to the function below and the user might not know/care how that happens.

That's why there is the more verbose option to define a function and decorate it. I don't see the point in exposing the hooks as pre_compile, post_compile etc... That would mean another major syntax change with very little value and without a strong reason.

I'd vote to schedule the drop for 4.0.

Meanwhile, we need to deprecate it since 3.7.0, I guess.

Meanwhile, we need to deprecate it since 3.7.0, I guess.

Done
I've also intercepted all these directives to not make their way into the class and the instance, since something like self.bind(...) or self.parameter(...) does not make sense.

I think there is sth wrong with this PR git-wise. I see 67 files changed 🤔

@vkarak I've updated all the @rfm.run_before and so on to the @run_before syntax in all the cscs-checks. I can revert that if you think that should go in a separate PR.

Oh, I see! No, keep it, because we don't want tons of deprecation warnings. We already have enough with the parameterized_test decorator :-)

Implementation-wise, I'm still not 100% happy that the file hooks.py is aware of the pipeline stages. Perhaps it would make sense to have the run_after and run_before functions specialising the _runx function inside the metaclass.

I feel this now looks a lot better. The backend _runx function to attach the hooks to the stages has now been renamed to attach_to. Decorators run_before and run_after have now live in the metaclass, and they use the attach_to function after mapping the pipeline stages.

@jjotero I've fine tuned the documentation as follows:

Remove duplicate documentation; use pointers in the code to the actual user documentation.
Move pipeline hooks section under the builtins.
Add a warning box for the deprecation of former syntax.

If you agree with the changes, I am ready to merge it.

If you agree with the changes, I am ready to merge it.

Yeah, docs look far cleaner now.
I've also made the parameters and variables to show as RegressionMixin.parameter (instead of RegressionTest.parameter) for consistency with all the other builtins.


curl POST of an iRODS object ?

Dear iRODS team,
I installed irods-microservice-plugin-curl yesterday and it works very well with the example provided in curlPost.r:
https://github.com/irods/irods_microservice_plugins_curl/blob/master/rules/curlPost.r
But would it be possible, instead of posting *data="Sent from iRODS", to post an actual iRODS object, say /ZONE/ home/rods/test, to some URL ? I tried some options like "*postFields."data" = "-F @*data"" with *data pointing to an iRODS object, but I'm not sure it worked, I need to test it some more.
Or is the cURL plugin only compatible with physical files outside of iRODS ?
Best regards, (and take care)
Samuel, from CINES (Montpellier, France)

Dear iRODS team,
I also posted a message on the forum:
https://groups.google.com/forum/#!topic/irod-chat/AXJOFwWoAqc
Best regards,
Samuel

I'm closing this issue, it's no longer necessary.
Cheers, Samuel


fix build by working around #1600238

fix build by working around LP: #1600238 - duplicate files in usr/share/pkgconfig

This change is

Reviewed 1 of 1 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable


[compose] figma connect create command not working

Code Connect CLI version  --> 1.0.5
Operating system --> Mac OS

figma.config.json file:

I'm running this command
figma connect create "https://www.figma.com/design/example/2024-New-Atomic-Design-System-WIP?node-id=6516-64792&m=dev" --token ***redacted**** --verbose
And I'm getting the following error:
Failed to create: TypeError: Cannot read properties of undefined (reading 'name')
I'm not sure what/where the 'name' property is coming from?

Hi @cairacshields, to better debug this issue we'd like to have access to the linked figma design file. Would you mind opening a ticket with our support team to follow up on that? Thanks!

I had this issue. I had to select the purple "Component set", not one of the variants inside the set


Ensure that required flag works for object types

Codecov Report

Merging #266 into master will increase coverage by 0.05%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #266      +/-   ##
==========================================
+ Coverage   98.79%   98.84%   +0.05%
==========================================
  Files          14       14
  Lines        1158     1217      +59
==========================================
+ Hits         1144     1203      +59
  Misses         14       14

Impacted Files
Coverage Δ

opwen_email_server/actions.py
100% <0%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Remove icub-common

Fix #10.

I can't provide this as a suggestion as it is not part of the modified lines, but I guess we need to add:
sudo bash ./scripts/install_apt_dependencies.sh

after the clone of the right version of the superbuild to install the dependencies, xref: https://github.com/robotology/robotology-superbuild?tab=readme-ov-file#system-dependencies  .

Sure, I forgot about the replacement!

Done, @traversaro


updateHead add's the changed meta instead of updating

I use the updateHead function to change the meta data when the language is changed. But instead of updating the current meta, the tags get added.
I use a mixin to set the meta and watch the language state:
export const meta = {
  head: {
    title: function () {
      var title = this.$store.state.activePage.Main.Meta[this.$store.state.language].Title
      if (title && title !== '') {
        return {
          inner: title
        }
      }
    },
    meta: function () {
      var meta = []
      var page = this.$store.state.activePage.Main
      var items = ['Title', 'Description', 'Image']
      for (var i = 0; i < items.length; i++) {
        var content = page.Meta[this.$store.state.language][items[i]]
        var name = items[i].toLowerCase()
        if (content && content !== '') {
          meta.push({ name: name, content: content })
          meta.push({ name: 'twitter:' + name, content: content })
          meta.push({ property: 'og:' + name, content: content })
        }
      }
      return meta
    }
  },
  watch: {
    '$store.state.language' (val) {
      this.$emit('updateHead')
    }
  }
}

The watch function is triggered when the language is changed. And as I said, the meta is added instead of updated.

@sstenn
You can add an id attribute
https://github.com/ktquez/vue-head#replace-content-the-elements

I closed the issue, but if you still have questions, just open again, ok?

Issue is solved. Thanks for your response


[Feature Request] Configure Pastebin URL slug length through CLI args

nanoid supports generating an ID of a certain length, all you have to do is pass the length as an argument. Can we have this? We can pass the slug length as a CLI arg to pastebin.
This does bring in additional complexity in the form of potential namespace collisions, so we might want to generate a new ID until we avoid collision, and in the edge case that the whole namespace is exhausted, fail to create a paste.

Hey @acherunilam,
sounds good (y)

The '-slug-len' is now available, but there is no namespace collision check yet (#6)

I am closing this issue, though I think that once the Transactions support lands:
https://github.com/rust-rocksdb/rust-rocksdb/pull/250
I'll use the transaction mechanism as the protection against key collision

@mkaczanowski Shall we fail to start the app up front in the off chance that a user mistakenly specifies a slug length of zero?
$ cargo build

# validation works as expected, application fails fast
$ ./target/debug/pastebin --slug-len=-1
error: Invalid value for '--slug-len <slug-len>': invalid digit found in string

# whoops, app starts and gets stuck after getting the first request instead of failing up front
$ ./target/debug/pastebin --slug-len=0
...
🚀 Rocket has launched from http://localhost:8000
$ echo "hello World $RANDOM" | curl -q -L -d @- -o - http://localhost:8000/
# both server and client are stuck doing the POST request

I assumed people would know what they're doing (ie. setup slug len to be above 0). But one extra check at the startup doesn't hurt anyone, so I'll add this as well


Consider port overrides when constructing server URLs

Proposed changes:
I found that when using the cmdline channel, a possible port override passed to serve_application will not be considered as the hardcoded URL that is already formatted with the default port is being passed here: https://github.com/RasaHQ/rasa_core/blob/a26dd755492a0c3d3516229967b38bf8930e8179/rasa_core/run.py#L209
creating a possible mismatch between listener and caller. Instead, always consider possible port overrides when passing the server URL.
Status (please check what you already did):

[x] made PR ready for code review
[ ] added some tests for the functionality
[ ] updated the documentation
[ ] updated the changelog

Thanks for the fix :+1:


Issue1158

Fixes #1158
Having a small issue with the JQuery-UI datePicker polyfill.
@Bodacious, @xsrust and @johnpinto1 maybe one of you can see what I'm doing wrong here. I was originally using the jquery-ui theme that's already located in node_modules but the 'prev' and 'next' text and icons were not visible in the UI (although the links were there and you could click on them, there was just no visual cue for the user).
I then went out to the JQuery-ui site and pulled down a custom theme containing only the bits necessary for datePicker. I added them into the application.scss (although I think its probably preferable to use the node_modules one) this seemed to work but the 'prev' 'next' icons are still missing. Its at least now has a background-url (see screenshot) but its looking in an odd place.
I think its probably just an issue with the webpacker config but I don't have bandwidth for the rest of the week to dig deeper. If either of you has any time to take a look I would appreciate it
To do this: open this branch locally in Safari and create a plan based off of a template that has a date field (you may need to add a question to an existing template). Then edit the plan and expand the section. The datePicker polyfill will open when the field gets focus.

@briri @xsrust @Bodacious I have added missing icons and fonts based on these errors I found on Safari. See image

The issue I am finding is that the assets  for the JQuery-UI are being precompiled to the wrong folder, e.g, images copied to public/assets/jquery-ui folder instead of public/assets/jquery-ui.
So http://localhost:3000/assets/jquery-ui/datepicker/images/ui-icons_FFF_256x240.png works but the datepicker is expects http://localhost:3000/assets/vendor/jquery-ui/datepicker/images/ui-icons_FFF_256x240.png
Also the missing font which I added is not being copied so http://localhost:3000/fonts/GillSans-Light.ttf fails.
Also I had to rename ui-icons_ffffff_256x240.png to http://localhost:3000/fonts/GillSans-Light.ttf. Will continue investigating.

took a stab at adding jquery-ui-rails gem but it didn't work. I think due to a config or load timing issue with web packer. The jquery-ui docs instruct you to add a //= require 'query-ui' line to your application.js which uses some gem magic to do all the necessary wiring. We are using webpacker though so the application.js lives outside the normal asset pipeline infrastructure.
We are also already making use of jquery-ui's sortable functionality via webpacker so we would likely need to rethink our asset management strategy.
Going to try to do some css hacking to get the proper images in place.


cuelang.org: Chinese Translation Tracker

Related to https://github.com/cue-lang/cue/issues/970
I'm going to work on Chinese translation.
I list all the subdirectories to track the progress.
If someone wants to contribute one of them, please comment this issue.

[x] about https://github.com/cue-lang/cuelang.org/pull/238
[ ] concepts

[ ] language
[ ] packages
[ ] patterns
[ ] scripting

[x] contribution_guidelines https://github.com/cue-lang/cuelang.org/pull/217
[ ] examples
[x] install https://github.com/cue-lang/cuelang.org/pull/217
[ ] integrations
[ ] references
[ ] tutorials

[ ] expressions
[ ] intro
[ ] packages
[ ] references
[ ] types

[ ] usecases

This issue was created against the "old" instance of https://cuelang.org.
Work on translations for the new site is being tracked via https://github.com/cue-lang/cue/issues/3107, so closing this.
@h1z3y3 - thanks again for your original work here, as I said in https://github.com/cue-lang/cuelang.org/pull/238#issuecomment-2088251795.


python311Packages.google-cloud-securitycenter: 1.23.0 -> 1.23.1

Changelog: https://github.com/googleapis/python-securitycenter/blob/v1.23.1/CHANGELOG.md
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 241885 run on x86_64-linux 1

4 packages built:

python310Packages.google-cloud-securitycenter
python310Packages.google-cloud-securitycenter.dist
python311Packages.google-cloud-securitycenter
python311Packages.google-cloud-securitycenter.dist


docs(content/actions): contexts.md environment variables logging

Was it intended that the job logs actual $GITHUB_CONTEXT (and others) as a string? Should it print the actual data inside that variable? Because single quotes in bash does not allow environment variable substitution, only double quotes do.
Why:
Closes: #26604
What's being changed (if available, include any code snippets, screenshots, or gifs):
Current production article section
Changes in the PR
Check off the following:

[X] I have reviewed my changes in staging, available via the View deployment link in this PR's timeline.

For content changes, you will also see an automatically generated comment with links directly to pages you've modified. The comment won't appear if your PR only edits files in the data directory.

[X] For content changes, I have completed the self-review checklist.

@bernizhel Thank you for opening a PR and linking it to your issue! ✨
Thanks for context and links, too. I'll get this triaged for review ⚡
In the meantime, if you'd like to find other ways to contribute, check out our help wanted section to find open issues you can work on. 👍
Oh, and welcome to the community! 🎉


A dependency of this repository contains a critical VM escape vulnerability

Details here:

https://gist.github.com/arkark/e9f5cf5782dec8321095be3e52acf5ac
https://nvd.nist.gov/vuln/detail/CVE-2023-32314

Dependency tree:

ibm-openapi-validator
@stoplight/spectral-cli
proxy-agent
pac-proxy-agent
pac-resolver
degenerator
vm2

Vulnerable code does not seem to be used at any point in the dependency stack, for reference this is where it's called: https://github.com/TooTallNate/proxy-agents/blob/95729e1563fb4d6edcb7287bdd7e1a8126016da4/packages/pac-resolver/src/index.ts#L48-L53
Related issues:

https://github.com/stoplightio/spectral/issues/2510
https://github.com/TooTallNate/proxy-agents/issues/218

@Southclaws Thanks for opening the issue.  We are waiting a bit in hopes that the @stoplight/spectral-cli package will have a new release soon which addresses this vulnerability.  Alternatively, if one of its transitive dependencies (proxy-agent, pac-proxy-agent, etc.) publishes a new version that no longer uses vm2, we could potentially use "overrides" in package.json to force the use of a new transitive dependency by spectral-cli.
Rest assured, we're keeping an eye on this situation.

:tada: This issue has been resolved in version 1.2.0 :tada:
The release is available on npm package (@latest dist-tag)
Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version 1.2.0 :tada:
The release is available on npm package (@latest dist-tag)
Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version 1.2.0 :tada:
The release is available on npm package (@latest dist-tag)
Your semantic-release bot :package::rocket: