text:
Memory leak leads to heap overflow

14 Oct 15:06:57 - Received: :nova.esper.net PONG nova.esper.net :115367
<--- Last few GCs --->
[2539:0x4299a10] 1791041298 ms: Mark-sweep 1325.7 (1350.2) -> 1323.7 (1350.2) MB, 718.2 / 0.1 ms  allocation failure GC in old space requested
[2539:0x4299a10] 1791042276 ms: Mark-sweep 1323.7 (1350.2) -> 1323.6 (1350.2) MB, 977.4 / 0.0 ms  allocation failure GC in old space requested
[2539:0x4299a10] 1791043255 ms: Mark-sweep 1323.6 (1350.2) -> 1323.6 (1350.2) MB, 979.5 / 0.0 ms  last resort
[2539:0x4299a10] 1791044225 ms: Mark-sweep 1323.6 (1350.2) -> 1323.3 (1350.2) MB, 969.6 / 0.0 ms  last resort
<--- JS stacktrace --->
==== JS stack trace =========================================
Security context: 0x2a90f6a29891
2: heartbeat [/home/sfnet-discord-bot/node-v8.1.2-linux-x64/lib/node_modules/discord-irc/node_modules/discord.js/src/client/websocket/WebSocketConnection.js:~407] [pc=0x1141bd0b5fab](this=0x3bc473b2d581 <an EventEmitter with map 0x263359c3e3d1>,time=0x222777302311 )
3: arguments adaptor frame: 0->1
4: _onTimeout [/home/sfnet-discord-bot/node-v8.1.2-linux-x64/lib/node_modu...
FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory
1: node::Abort() [node]
2: 0x13647ec [node]
3: v8::Utils::ReportOOMFailure(char const*, bool) [node]
4: v8::internal::V8::FatalProcessOutOfMemory(char const*, bool) [node]
5: v8::internal::Factory::NewUninitializedFixedArray(int) [node]
6: 0xe90ca3 [node]
7: v8::internal::Runtime_GrowArrayElements(int, v8::internal::Object**, v8::internal::Isolate*) [node]
8: 0x1141bc30437d
Aborted

I don't understand much of what's written here. From the stack trace, it looks like… the very last… call… was from discord.js? I don't think that helps track the problem down, though.
Do you have any more information on the problem? I've never noticed it, so I wonder if you're doing something weird in your setup (are you on a low-memory machine?).

No, I was running into the Node v8 default heap limit. There's not enough info here, but you can probably find it fairly quickly if you try pulling in heapdump from npm and take some snapshots as the bot is running:
https://blog.risingstack.com/finding-a-memory-leak-in-node-js/
I'll look into it a bit more at some point, but my fix for now was to just stick discord-irc into a systemd unit so it autorestarts when this happens.

Have there been any updates on this?
I'm having what appears to be a similar issue as seen in the following log:
error Command failed with exit code 134.

Aborted
10: 0x15a8c4bc3b67
9: 0x8e62c6 [/nodejs/bin/node]
8: node::StringBytes::Encode(v8::Isolate*, char const*, unsigned long, node::encoding, v8::Local<v8::Value>*) [/nodejs/bin/node]
7: v8::String::NewFromUtf8(v8::Isolate*, char const*, v8::NewStringType, int) [/nodejs/bin/node]
6: v8::internal::Factory::NewStringFromUtf8(v8::internal::Vector<char const>, v8::internal::PretenureFlag) [/nodejs/bin/node]
5: v8::internal::Factory::NewRawTwoByteString(int, v8::internal::PretenureFlag) [/nodejs/bin/node]
4: v8::internal::V8::FatalProcessOutOfMemory(char const*, bool) [/nodejs/bin/node]
3: v8::Utils::ReportOOMFailure(char const*, bool) [/nodejs/bin/node]
2: 0x8ccf9c [/nodejs/bin/node]
1: node::Abort() [/nodejs/bin/node]

FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory

3: unpack [/app/node_modules/discord.js/src/client/websocket/WebSocketConnection.js:~170] [pc=0x15a8c49070bd](this=0x29ae8a484649 <EventEmitter map =…
2: arguments adaptor frame: 0->3
1: toString [buffer.js:~609] [pc=0x15a8c495b041](this=0x253f2b47cc99 <Uint8Array map = 0x32dd30a43a71>,encoding=0x282dd32822d1 <undefined>,start=0x282dd32822d1 <undefined>,end=0x282dd32822d1 <undefined>)

Security context: 0x2af5574a58b9 <JSObject>

==== JS stack trace =========================================

<— JS stacktrace —>
[27:0x3001070] 70137123 ms: Mark-sweep 1292.3 (1470.9) -> 1292.3 (1470.4) MB, 2666.6 / 0.0 ms  last resort GC in old space requested

[27:0x3001070] 70134456 ms: Mark-sweep 1292.3 (1511.9) -> 1292.3 (1470.9) MB, 2829.5 / 0.0 ms  last resort GC in old space requested

[27:0x3001070] 70131626 ms: Mark-sweep 1292.4 (1509.9) -> 1292.3 (1511.9) MB, 2763.2 / 0.0 ms  allocation failure GC in old space requested

<— Last few GCs —>

Looking through the discord.js issues related to memory leaks [0] it seems like they cache a lot of things without actually clearing the cache. It doesn't seem like this is something they intend to fix: https://github.com/discordjs/discord.js/issues/1409#issuecomment-433648959
It's on the other hand possible to disable some of these caches [1] so maybe that's what we want to do?
[0] https://github.com/discordjs/discord.js/search?q=memory+leak&type=Issues
[1] https://github.com/discordjs/discord.js/pull/2883

@ekmartin Have you had any luck with disabling the cache?
It looks like the fork was abandoned due to unexpected behavior when disabling stores. https://github.com/discordjs/discord.js/pull/2883#issuecomment-433649130
Our Discord Bot's heap can grow to 2gigs in a couple of hours resulting in a crash. And we have under 50 Discord groups using the bot, so this type of rapid memory expansion seems odd, given there are some bots with pretty massive usage.
Thanks for pointing me to those threads. 👍

Is this still an issue? I'm looking into updating discord.js, but I don't know if they've made any improvements here.

authors: Throne3d ekmartin pkovac sethlesky

repo: reactiflux/discord-irc


text:
Upgrade discord.js to version 12

Also updates test stubs.
WIP:

[ ] Manually test most main cases (pings of users + roles, emoji use, multi-channeling, join messages)
[x] Investigate hanging tests (looks to be due to Bot Events)

Coverage increased (+0.03%) to 96.884% when pulling 6a986152eddf95f1c1d67ea67daf28e687fd3010 on upgrade/discordjs-12 into ee2d70fac12860b9a78043b7f121979929842493 on master.

source: gharchive/pull-request

license: mit

license_type: permissive

license_source: bigquery


text:
Add Maintenance Page

Feature Name
Add Coming Soon and Maintenance Pages
Summary description
Provide two a pages for stores which are either (1) not yet launched or (2) undergoing maintenance. In both cases provide the user an experience that allows the user to take some action which continues to grow the business (e.g. a launch email sign-up form).
Rationale for why this feature is necessary
It's standard fare for e-commerce sites. The launch page is expecially helpful for allowing store operators users to log in and view the store in production but before it's launched.
Expected use cases
Prospective customers may sign-up for email notification/newsletter prior to launch.
Store operators may log-in from Coming Soon if they've been given the credentials by the admin.
Admins may demo a production-ready product to stakeholders and gather feedback.
Shoppers receive a more professional experience when the site is down.
Here's an example Coming Soon page I mocked up using Chakra UI:

Thanks for taking the time to file this issue and preparing a mockup @balibebas!
The example storefront, as the name says, is just an example implementation meant to be customized.
I don't really consider such a screen a priority at all as it is easy to add one based on individual requirements, although I also wouldn't consider it to be an issue to showcase this functionality if someone wants to do a PR.
The issue I see is, that this would either involve some more work or give a false sense of security. To offer a proper maintenance mode, there would me adjustments on the API to maybe store this on the shop document, some admin ui to toggle this and then it could be used during getStaticProps in the storefront to present such a maintenance screen. But the API would actually need to take that into consideration and deny acess to most of the queries apart from shop for non-authorized users.
Also, as we use static generation were possible, still allowing storefront access to some authenticated users could be another challenge and probably be solved by using nextjs preview mode.
Honestly I wouln't expect what I just described to be implemented anytime soon, although I guess such a maintenance mode would be a welcome addition if someone wants to provide PRs for that.
Wonder what @mikemurray and @focusaurus think about this.
A really quick and simple solution instead could be to just add some MAINTENANCE_MODE env variable and accompanying pages + redirects, if others agree that this provides any value to the way they work with the storefront.

Similar to how the IOU payment example works for the API plugins I feel it would be good to keep a custom landing page of some sort present so this rather typical use case will always be considered as refactoring of the app and docs occur. Given not everyone needs a fancy landing page providing some sort of experience for API outages or errors would be nice. So having a maintenance page which appears when one clicks a product during an outage would be useful for most uses.

Closing due to lack of activity

source: gharchive/issue

authors: balibebas janus-reith

repo: reactioncommerce/example-storefront

license_source: github-api


text:
Add segment compatible analytics event tracking to the Product Grid

We need to start tracking ecommerce analytics events in our starterkit. Initially we'll be tracking all of the Segment V2 Ecommerce Events. You can read the docs for that here: https://segment.com/docs/spec/ecommerce/v2/
Start by add documentation for the events tracked to our event tracking/analytics documentation, explaining the properties tracked and any mapping decisions that were made.
For our current implementation of the Product Grid, we'll need to track two events:
Product List Viewed
Product Clicked

@spencern The product price may be a range, should I take the min or max or neither?

I'd take the min if a range exists

maybe create a constant variable for this that we can permit customization of in the .env file later as well?

authors: mikemurray spencern


text:
Sync repo with latest from st2-chatops-aliases master

This PR syncs a few stray commits from st2-chatops-aliases master branch committed there after creating this cloned repo. This is the first step in shuttering the st2-chatops-aliases forked community repo and using this repo exclusively for our Stackstorm setups.
Boxed seems to have been using the use-existing-dyn-inventory branch on this repo. GMR has been using the st2-chatops-aliases repo master branch. With this sync up we can switch GMR over to this repo and delete the st2-chatops-aliases repo. We can decide how to handle Boxed's branch separately from this PR.

fwiw, the actions in Boxed branch will probably be moved into the boxed-infrastructure repo. they are highly customized in a way I'm not sure we can abstract out.

Looks good to me.

authors: davekonopka jmound sairez


text:
Refactor to ES6

Either simply write the entire source in ES6 and require node 4 in the package.json or implement transpilation with Bable.

This has been done in my recent clean up in https://github.com/reactivepod/fido/pull/4 via require('babel/register');.

authors: hglattergotz kahlil

repo: reactivepod/fido


text:
fix: remove duplicate ComponentModelTypeConverter

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
fix
What is the current behavior? (You can also link to an open issue here)
The ReactiveUI.Wpf project includes ComponentModelTypeConverter even though it's already in ReactiveUI.
What is the new behavior (if this is a feature change)?
Remove ComponentModelTypeConverter from ReactiveUI.WPF. Also, fix comments in the copy inside ReactiveUI because it actually has nothing to do with WPF.
What might this PR break?
Nothing realistic.
Please check if the PR fulfills these requirements

[ ] The commit follows our guidelines: https://github.com/reactiveui/reactiveui#contribute
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

Other information:

@kentcb,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by .NET Foundation. We will now review your pull request.
Thanks,
.NET Foundation Pull Request Bot

Changes Unknown when pulling 88a668b9490a0b9214b726cc1dc5d17e7eda0df7 on kentcb:component-model-type-converter into ** on reactiveui:develop**.

authors: coveralls dnfclas kentcb

repo: reactiveui/ReactiveUI

license: MIT


text:
Farewell

For all the details check out my Medium post.
The tl;dr is basically that I’m overwhelmed and out of time so I’m turning everything over to @diasbruno as I step away from React Modal.
Thanks for everything and goodbye!

Thank you so much for your time managing react-modal.

@claydiffrient Awesome work!

authors: claydiffrient diasbruno jamesjjk

repo: reactjs/react-modal


text:
[chore] added missing babel transformer plugin.

Running webpack --config webpack.config.js fails due to missing babel's spread transformer.
ERROR in ./examples/basic/app.js
Module build failed: SyntaxError: Unexpected token (16:20)

  14 |
  15 |   openModal: function() {
> 16 |     this.setState({ ...this.state, modalIsOpen: true });
     |                     ^
  17 |   },
  18 |
  19 |   closeModal: function() {

Acceptance Checklist:

[x] All commits have been squashed to one.
[x] The commit message follows the guidelines in CONTRIBUTING.md.
[x] Documentation (README.md) and examples have been updated as needed.
[x] If this is a code change, a spec testing the functionality has been added.
[x] If the commit message has [changed] or [removed], there is an upgrade path above.

This will no longer be necessary.


text:
🛑 Bellshade API is down

In 25eff64, Bellshade API (https://api.bellshade.org) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Bellshade API is back up in f1b4c07.


text:
[#2PlaysAMonth]: Image Gallery - Create a responsive image gallery by using the free Unsplash API

First thing, PLEASE READ THIS: ReactPlay Code Review Checklist

Description
The project contains use of Unsplash API, which is fetched using axios and then populated in the Photo Component.
Following things have been used in this project:

useState
useEffect
React Form
Component Refactoring
Material UI icon
Axios npm module
CSS Grid
Infinite scroll functionality(This feature is still not showing the react play app but is working on local file system. I am working on it)

The app is responsive and redirects to the individual images and profiles when clicked on it.
Fixes #910
Type of change

[ ] New feature (non-breaking change which adds functionality)

How Has This Been Tested?
To see working of the app repeat the following

Go to the app. Some images are loaded on the screen by default
Search for any keyword. The screen will update with new images.
Hover over any image, the cursor will turn to pointer.
On clicking any image, the page will re direct to that image.
On hovering, the profile name, likes will come in front of the image. On clicking the profile photo, the profile of the image contributor will open
The page on scrolling down should show more images.

Checklist:

[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] Any dependent changes have been merged and published in downstream modules

Screenshots or example output

@siddhantsiddh15 , Thanks for the PR.
I would request you change the PR title to "[#2PlaysAMonth]: Image Gallery - Create a responsive image gallery by using the free Unsplash API"
and the second thing is to link your PR with the issue by adding the below line in the PR description.
Example:
Fixes #910

Greetings,
I have updated the pull request name and linked the issue with the issue number

Thanks

@siddhantsiddh15 , Please format and lint the code by following this guide.
https://github.com/reactplay/react-play#format-the-code

Greetings
Have formatted the code as per the guidelines as mentioned here https://github.com/reactplay/react-play#format-the-code and then pushed the code in the branch.
Thanks

@siddhantsiddh15 Kindly resolve the merge conflict

These errors are not in my edited files, what can I do to run the react play?

@siddhantsiddh15 Catch me up on Discord today to close it.

Link to the video as I was facing repeated issue in creating an account on Stack Stream.

Thankyou for merging my branch into main. Can I close this pull request now?

Inspect

I have kicked off a build. Please check if it is successful and test if things are fine.

@siddhantsiddh15 here is the preview build.. I see the changes are breaking styles. Please take a look
https://react-play-git-fork-siddhantsiddh15-unsplash-8f3010-reactplayio.vercel.app/

Have recorded the video here .  The website is responsive and is working correctly.

@siddhantsiddh15 almost there..
please add a cover image

Also edit your play from localhost and add the stream recording.
Ping where when you done, will merge it.

@siddhantsiddh15 let us know when done

Have added the cover image.

Have added the cover image.

Thanks!

The cover image should be in KBs, please reduce the size.
Also confirm that your demo recording has been added to the play by editing it.

Greetings,
I have not added the demo recording in the Play. I have updated the size of the cover.png to 13 kb.
Regards

Greetings,
I have not added the demo recording in the Play. I have updated the size of the cover.png to 135 kb.
Regards

Can you please add the demo recording too.. then its al done.

Cannot do it. Having difficulty. Can we skip the recording portion?

Cannot do it. Having difficulty. Can we skip the recording portion?

Ok, no worries, no pressure. It's still valuable to get your work in.
I am just curious about what kind of issues you are facing. If you can post about it in our Discord, I may try the resolution.. In fact, you can add the recording after merge too...(before 5th March)

I am having slow internet connection due to the place I have travelled to,  recording is a big file to upload.

Hey @siddhantsiddh15 , this play looks cool. I will be waiting for the video link to updated before merging it to production branch

Okay, will update it by tonight.

Hey @siddhantsiddh15 , this play looks cool. I will be waiting for the video link to updated before merging it to production branch

I have uploaded here the updated video of the play. I have checked the responsiveness and working of my play. The delay from my side was unwanted, I have uploaded the video as soon as I got good internet connection.

Well the video should be on https://stack-stream.com/

I can get this play merged if everything is ok however please record a stackstream video before EOD

@atapas  you need to unblock in order to merge this PR
@siddhantsiddh15  please record demo on stackstream

authors: Sachin-chaurasiya atapas koustov siddhantsiddh15

repo: reactplay/react-play


text:
Reactstrap and React-router 4.0.0-beta.6 - active

Issue description

components: Navlink

Steps to reproduce issue

I'm using Reactstrap and React-router 4.0.0-beta.6 in the educational project that is located on gitlab with custom domain - http://harazd.org/.
According to Reactstrap docs: that's the way I should use active navlink

  import { NavLink } from 'reactstrap'
  ...
  <NavLink href="#" active = true >Link< /NavLink>

According to React-router v4 docs:
  import { NavLink } from 'react-router-dom'
  ...
  <NavLink to="/about" activeClassName="active">About</NavLink>

So how should I do implement navlink active state and use react-router?

The simplest answer is that you can't use reactstrap navlink active prop when passing in react-router navlink. And that's fine because it's just 1 class active and react-router NavLink can take care of that with the activeClassName prop.
To use both, you'll need to rename one of those and use the tag prop in reactstrap NavLink.
import { NavLink } from 'reactstrap';
import { NavLink as RRNavLink } from 'react-router-dom';

<NavLink to="/about" activeClassName="active" tag={RRNavLink}>About</NavLink>

Thanks for a quick solution (You can paste your answer here: http://stackoverflow.com/questions/42372179/reactstrap-and-react-router-4-0-0-beta-6-active-navlink). And one more thing : ... - root path is always active for some reason..

The root path is always active because '/' is in every path. I am not too fimilar with react-router-dom and it's NavLink, it looks like it has an exact prop which may be what you are looking for.

Here's my router code, so I do use exact for root path.
`      <BrowserRouter>
        <div className='app'>
          <Switch>
            <Route exact path='/' component={Landing} />
            <Route path='/products' component={Products} />
            <Route path='/services' component={Services} />
            <Route path='/price' component={Price} />
            <Route path='/contacts' component={Contacts} />
            <Route component={NoMatch} />
          </Switch>
        </div>
      </BrowserRouter>`

@TheSharpieOne yes adding exact to root Navlink helped)

Previously you were using <NavLink> from react-router-dom. From that file, it looks like it creates the Route and the Link for you in one go.
react-router v4 has a ton of changes and I am not familiar with it enough to know how to use it compared to previous version so I can only offer some limited help with it.

@Y-Taras @TheSharpieOne can you give me example code? a have try it but doesnt work so far.

@dhanyn10 here's a link to my working example
https://gitlab.com/ytaras/pinobeton2/blob/master/js/Navigation.js

Hi everyone,
Is there anyway to use NavLink from reactstrap alone to style the active link?
Thanks

@Y-Taras I can confirm your solution works here too. Thanks so much - you saved me many hours of pain.

@piavgh if you just want to use reactstrap's NavLink alone (without react-router-dom) you can use the active prop:
import { NavLink } from 'reactstrap';

<NavLink to="/about" active>About</NavLink>

I think you can add something like :
 <NavLink to="/about" active={window.location.hash === '/about'}>About</NavLink>

This works for me:
<NavItem active={window.location.pathname === "/thing"}>
  <NavLink href="/thing">Things</NavLink>
</NavItem>

authors: JonSilver TheSharpieOne Y-Taras dhanyn10 eddywashere nathfy piavgh softmixt

repo: reactstrap/reactstrap


text:
Proposal for environment context

This is a proposal for a new environment context which takes precedence of the config file.
We had the need for a context which can be configured for automation without touching files.
Happy to hear your feedback.

Hmm instead of going through all that trouble of creating and mapping config variables, you could also create an environment variable ESQUE_CONFIG_YAML that can hold the whole esque config as yaml string. That would be more dynamic, future proof and would only require minimal changes.

Hm. I get your point, in general. But that would only get rid of the need to write a file, not to create a YAML in general. :D

You wrote:

without touching files.

So I thought, that was your problem :smile:
Well, although I don't see how setting 15 environment variables is easier than creating a yaml string, I'm always a fan of "letting the user choose". So I'm not entirely against it.
I'm just afraid that we might have to rename, add and/or remove some of the variables while our config evolves. We do have a migration mechanism for file based configs but not for environment variables. Do you think a separate command to add a section to the config would help you?
Something like esque config add-context foo --bootstrap-servers broker1,broker2 --schema-registry registry ...
I think it's easier to keep a command stable than it is to keep the environment variables the same over time.

Guess I should have been clearer. Sorry for that. :D
I think you're right with your approach of not wanting to make it unnecessarily complicated and I think the idea of just adding another command is good. I'll see with what I can come up with over the weekend. 😊

authors: hfjn swenzel

repo: real-digital/esque


text:
C API

For easiest integration with Go (via cgo), Erlang, and Rust (via FFI), a C API (not C++) is needed. This is a simple wrapper around C++.

.NET users will also be very happy to use Aeron via P/Invoke! Do you have any ETA? A C API will instantly make Aeron as ubiquitous as ZMQ, native ports like #35 are not needed as much as a simple API.

This is still a plan. However, have not had time to get to it.

Any Update over the C API

Currently, a C API is planned for the media driver. And would like to extend that API to cover the Aeron client API. However, no timeline is set for that yet.

Closing until someone is willing to sponsor the work.

Now the C API are able to be happen:)

Preview in 1.28.X releases.

Should be feature complete from 1.30.0.

authors: Hemanth-Eduru buybackoff lygstate mjpt777 tmontgomery

repo: real-logic/Aeron


text:
Constrain Mailing list form in Sidebar

Is it possible to make the mailing list form only 300px wide, as the ads are?

There's a custom CSS field in the plugin settings. I entered
.et_bloom { width: 300px; }
but no result

Where did you enter that CSS? It's not a good idea to edit the stylesheets directly, as they are replaced with each new build of the theme. Changes that are not part of that build would be overwritten.
Do you need provisions for manually inserting css?

There's a CSS field within the plugin settings. In other words, when
designing the look of the plugin, there are a host of options for
customizing the colors and text fields. Then there is a "Custom CSS" field.
On Fri, Apr 17, 2015 at 3:29 PM, Dylan Kinnett notifications@github.com
wrote:

Where did you enter that CSS? It's not a good idea to edit the stylesheets
directly, as they are replaced with each new build of the theme. Changes
that are not part of that build would be overwritten.
Do you need provisions for manually inserting css?
—
Reply to this email directly or view it on GitHub
https://github.com/real-pants/Real-Pants/issues/81#issuecomment-94058258
.

Can this be closed? Dimensions look great now.

authors: dylan-k realpants

repo: real-pants/Real-Pants


text:
Crash on trying to run file on sparse3

Crash encountered when running file on sparse3 from ufs-big test image
Backtrace with RUST_LOG=trace and RUST_BACKTRACE=full: https://gist.github.com/casept/4f9f18b75458f4801746d3597e29c2d1

What system were you running it on?  Can you please show us uname -a?

Fedora 40, uname:
Linux l13 6.10.3-200.fc40.x86_64 #1 SMP PREEMPT_DYNAMIC Mon Aug  5 14:30:00 UTC 2024 x86_64 GNU/Linux

This is now fixed with #63.

authors: asomers casept realchonk

repo: realchonk/fuse-ufs


text:
Fix Unit Tests and Remove Usage of Unsigned Byte

Remove UByte Array usages since it was experimental
Remove Roboelectric
Update Unit Tests with Android mocking Base64
Tests successfully run in the terminal

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

authors: CLAassistant realeyes-mike-patterson


text:
Clarify error message

I just wanted to clarify the error message that shows up when the library can't find the .so/.dll
The previous error message implied that the error had something to do with the vulkan version (false, as far as I can tell) and also didn't really indicate that the library just may not have been in the loading path. It's a really small thing, but I thought I'd submit a PR anyways
Also, random question. Why is there so much code duplication between vulkan.template.py and init.py?

Hello @pipsqueaker.
Thank you very much for your pull request. You are right about the error message, your version is a lot better. Nevertheless, you don't need to update the __init__.py file. This file is automatically generated from the vulkan.template.py which is a jinja2 template. When you run the generator script, it will do it for you. So what you can do is only update the template file and then I will regenerate the module.
Thanks a lot for the contribution.

@realitix Alright, just messed with my history a bit so that only vulkan.template.py is edited

Thanks @pipsqueaker for the contribution !

authors: pipsqueaker realitix

repo: realitix/vulkan


text:
Could you publish it in Scala 2.12 ?

jwt-scala_2.11 and jwt-scala_2.10 are already published, but we want to use your library in 2.12.
Could you publish this library in Scala 2.12 ?

forked and published for Scala 2.12 and 2.13

https://github.com/xuwei-k/jwt-scala/tree/v1.4.0
https://repo1.maven.org/maven2/com/github/xuwei-k/jwt-scala_2.12/
https://repo1.maven.org/maven2/com/github/xuwei-k/jwt-scala_2.13/

repo: reallylabs/jwt-scala


text:
Change object store to allow sync user auth URL to be modified

With this PR, getting a user with a different auth URL than the one it was originally given updates the URL, instead of throwing an exception.
This fixes the issue (commonly encountered during development) when a user is opened with one URL, persisted, the server is moved or SSL is enabled, and an attempt to log in the user with the new address is made.
This does not fix the corner case where two different ROSes have users with the same user ID, and the user wishes to be logged into both simultaneously, but this case wasn't supported before, nor is it supported by any of the other subsystem code.

Did we get clarity on whether identity is expected to be unique across different servers? If that's not guaranteed, is this change safe?

It's complicated.
The default implementation of identity is a UUID. However, there's the possibility of plugging a module into ROS that allows you to specify arbitrary identities instead of using the built-in system, so a conflict is theoretically possible. Even if it is, though, using Realms across multiple servers concurrently is something we intentionally de-emphasized when designing v1 of ROS, so I don't think it's a supported use case anyways.

It's something that Realm Browser inherently needs to support.

Back to the drawing board, then.

authors: austinzheng bdash

repo: realm/realm-object-store


text:
Switch to using ocaml-ci-scripts

This seems like a more reliable CI until we can use ocaml-ci.
This will allow us to easily add revdeps builds btw which could prove useful once we want to stabilize mdx's API and avoid breaking users' tests!

Opam has a make built-in variable that opam lint suggests we use instead of the raw "make".
Now that we use the ci-scripts, it's properly picked up and triggers a build failure if we don't have a compliant opam file.

Ok I've read https://github.com/realworldocaml/mdx/pull/185#discussion_r330673627 which answers my question. However this is quite fragile as it will break if you run this in a duniverse setting (with a toplevel call to dune runtest).

What do you mean? Do you mean that it will break if we vendor mdx in a duniverse? Aliases aren't resolved within the duniverse so it won't run the tests in this case.
I agree it is a bit fragile and I wish there was a way to tell dune about the ocaml-mdx -> ocaml-mdx-test binary dependency but unfortunately there isn't any atm. I tried a couple things and they ended up suffering from the same race condition.
Also when using mdx in duniverse mode, ocaml-mdx rule adds a (package mdx) dependency to the generated rules, thus solving the dependecny issue. We can't do that outside a duniverse because (package ...) deps only work for local packages, not opam ones.
There's one last thing I can try which is to add an explicit dependency on the install alias for all runtest aliases that rely on ocaml-mdx but that is a bit tedious and doesn't solve the issue in a generic way either but at least running dune runtest should work then. Let's merge that as it already fix the opam test runs and I'll try that solution in a separate PR!

Just had a quick look and the (alias install) dependency propably won't work as we generate most of the rules for runtest.

I just mean that we should report that issue upstream as it should be fixed properly at one point :-)

authors: NathanReb samoht

repo: realworldocaml/mdx

license: ISC


text:
cli: reana-dev git-log

New command git-log showing information about commits.

Signed-off-by: Tibor Simko tibor.simko@cern.ch

Example output:
$ reana-dev git-log
[reana-workflow-engine-yadage] git log -n 5 --graph --decorate ...
*  (upstream/pr/91)  34b1c8e tasks: add stop_workflow from reana_commons, Diego Rodriguez,  6 hours ago
*  (HEAD -> master, tag: v0.4.0, upstream/pr/90, upstream/master, origin/master, origin/HEAD)  11305f8 release: v0.4.0, Dinos Kousidis,  2 weeks ago
*  (upstream/pr/88)  720819b installation: upgrade REANA-Commons, Diego Rodriguez,  5 weeks ago
*   8f13434 publisher: update to kombu producer, Diego Rodriguez,  5 weeks ago
*  (upstream/pr/89)  32251ab installation: bump reana-commons include pkg data, Diego Rodriguez,  6 weeks ago
[reana-workflow-engine-serial] git log -n 5 --graph --decorate ...
*  (upstream/pr/52)  e77af4e tasks: use stop_workflow from reana-commons, Diego Rodriguez,  5 hours ago
*   ada286d tasks: introduce a stop_workflow task, Diego Rodriguez,  21 hours ago
*   522d3f1 config: disable task prefetching by process, Diego Rodriguez,  27 hours ago
*   0e114d1 config: disable broker pool, Diego Rodriguez,  28 hours ago
*   08f28d2 tasks: add revoke handler, Diego Rodriguez,  7 days ago
[reana-job-controller] git log -n 5 --graph --decorate ...
*  (upstream/pr/98)  d660142 api: return a dict on k8s_instantiate_job, Diego Rodriguez,  21 hours ago
*   e4a18d1 global: use flask run to start application, Diego Rodriguez,  5 days ago
*   c6b1578 tests: make application testable, Jan Okraska,  8 days ago
*   82fc7bc api: add delete job endpoint, Diego Rodriguez,  8 days ago
*  (HEAD -> master, tag: v0.4.0, upstream/pr/97, upstream/master, origin/master, origin/HEAD)  527cc1b release: v0.4.0, Tibor Simko,  2 weeks ago
[pytest-reana] git log -n 5 --graph --decorate ...
*  (upstream/pr/31)  ff2f2df fixtures: renaming of operational parameters, Dinos Kousidis,  23 hours ago
*  (HEAD -> master, upstream/master, origin/master, origin/HEAD)  4ceb1e7 release: v0.5.0.dev201811191, Diego Rodriguez,  24 hours ago
| *  (upstream/pr/30)  70b1f6e release: v0.5.0.dev20181119.1, Diego Rodriguez,  24 hours ago
|/
*   d0d1920 fixtures: fix expose yadage workflow fixture, Diego Rodriguez,  24 hours ago
*  (upstream/pr/29)  ce31f8a release: v0.5.0.dev20181119, Dinos Kousidis,  27 hours ago
[reana-workflow-monitor] git log -n 5 --graph --decorate ...
*  (HEAD -> master, tag: v0.4.0, upstream/pr/26, upstream/master, origin/master, origin/HEAD)  c242d4f release: v0.4.0, Dinos Kousidis,  2 weeks ago
*  (upstream/pr/25)  b8d4d1c global: license change to MIT License, Tibor Simko,  6 weeks ago
*  (upstream/pr/24)  924ef8d docs: new logo, panel verbiage and links, Tibor Simko,  5 months ago
*  (upstream/pr/23)  c884a9b docs: author ORCID links, Tibor Simko,  7 months ago
*  (tag: v0.2.0, upstream/pr/22)  8f5b219 release: v0.2.0, Dinos Kousidis,  7 months ago
[reana-server] git log -n 5 --graph --decorate ...
*  (HEAD -> master, upstream/pr/109, upstream/master, origin/master, origin/HEAD)  698a34e installation: fix pytest-reana dependency version, Tibor Simko,  3 hours ago
*  (upstream/pr/104)  a2cb517 api: new rest api endpoint which returns wf params, Rokas Maciulaitis,  24 hours ago
| *  (upstream/pr/108)  a92b154 api: automatic openapi specs passing to reana-commons, Rokas Maciulaitis,  4 days ago
|/
| *  (upstream/pr/107)  cd155f9 api: automatic openapi specs passing to reana-commons, Rokas Maciulaitis,  4 days ago
| *   068441c api: new rest api endpoint which returns wf params, Rokas Maciulaitis,  5 days ago
|/
[reana-message-broker] git log -n 5 --graph --decorate ...
*  (HEAD -> master, tag: v0.4.0, upstream/pr/16, upstream/master, origin/master, origin/HEAD)  7f18a21 release: v0.4.0, Tibor Simko,  2 weeks ago
*  (upstream/pr/15, upstream/license-change)  1da1398 global: license change to MIT License, Tibor Simko,  6 weeks ago
*  (upstream/pr/14, upstream/docs-logo-panel-links)  9d0bee3 docs: new logo, panel verbiage and links, Tibor Simko,  5 months ago
*  (upstream/pr/13, upstream/docs-authors-orcid)  6661833 docs: author ORCID links, Tibor Simko,  7 months ago
*  (tag: v0.2.0, upstream/pr/12)  1f7b82d release: v0.2.0, Tibor Simko,  7 months ago
[reana-workflow-controller] git log -n 5 --graph --decorate ...
*  (upstream/pr/141)  c1f00aa tests: utilities, Dinos Kousidis,  3 hours ago
*   efca3e4 rest: set_workflow_status parameters description, Dinos Kousidis,  4 hours ago
*   120db5c rest: allow deletion of already deleted workflows, Dinos Kousidis,  4 hours ago
*   a9721db tests: workspace deletion, Dinos Kousidis,  5 hours ago
*   74f9e53 rest: allow access to deleted workflows, Dinos Kousidis,  5 hours ago
[reana-workflow-engine-cwl] git log -n 5 --graph --decorate ...
*  (upstream/pr/70)  c92165a tasks: add stop_workflow task from reana_commons, Diego Rodriguez,  6 hours ago
*  (HEAD -> master, tag: v0.4.0, upstream/pr/68, upstream/master, origin/master, origin/HEAD)  7b4b7d5 release: v0.4.0, Dinos Kousidis,  2 weeks ago
*  (upstream/pr/66)  e6cc7f9 installation: upgrade REANA-Commons, Diego Rodriguez,  5 weeks ago
*   a5bb2ee publisher: use Kombu publisher, Diego Rodriguez,  5 weeks ago
*  (upstream/pr/67)  696d526 installation: bump reana-commons version, Diego Rodriguez,  6 weeks ago
[reana-commons] git log -n 5 --graph --decorate ...
*  (upstream/pr/66)  1c6ccb5 tasks: introduce common task to stop workflows, Diego Rodriguez,  5 hours ago
*   cd856de api: update openapi specs, Jan Okraska,  20 hours ago
| *  (HEAD -> master, upstream/pr/65, upstream/master, origin/master, origin/HEAD)  e720eaa release: 0.5.0.dev20181116, Dinos Kousidis,  26 hours ago
| *   6cdb587 installation: bump pytest-reana, Dinos Kousidis,  27 hours ago
| *  (upstream/pr/63)  9746ec4 api: new rest api endpoint, Rokas Maciulaitis,  4 days ago
|/
[reana-db] git log -n 5 --graph --decorate ...
*  (HEAD -> master, upstream/pr/21, upstream/master, origin/master, origin/HEAD, installation-version)  0b0854b release: v0.5.0.dev20181116, Dinos Kousidis,  4 days ago
*  (upstream/pr/19)  4a5ebdf models: renaming operational parameters, Rokas Maciulaitis,  4 days ago
| *  (upstream/pr/20)  7f3621e models: addition of stopped WorkflowStatus, Diego Rodriguez,  6 days ago
|/
*  (upstream/pr/15)  3e7a812 models: addition of deleted WorkflowStatus, Dinos Kousidis,  12 days ago
*  (tag: v0.4.0, upstream/pr/17)  e2bb3e6 release: v0.4.0, Tibor Simko,  2 weeks ago

repo: reanahub/reana


text:
Playlist management: errors in cropping, appending or pasting

I have issues with the playlist manager
Once a playlist is made, it execute it finely
But once I chose for Crop or Append or Paste, the final result is totally incorrect.
Items are missing,  or partially copied and pasted.
I attached a .zip file containing a video that shows you the details.
I would like to know if this is an issue or it's me badly operating, and what do you suggest for the best.
Reaper-Playlist-Issue.zip

Interesting, can you share the project RPP? Are any media items grouped?

Interesting, can you share that TEST.RPP project? Are any media items grouped?

Sorry for the late reply
About the media items: not any group
Yes sure, the TEST.RPP is here in attachment in the ZIP file
TEST.zip

I cannot reproduce the bug with SWS v2.10.0. "Paste playlist at edit cursor" behaves as expected here with that project.
There is a possibility some REAPER setting is interfering. Can you share your reaper.ini as well?

I can reproduce if I have Preferences (-> Project) -> Media Items Defaults: Overlap and crossfade items when splitting (length is set to 0:00.010 here). enabled when pasting here.
I have that pref assigned to the toolbar button shown in the gif.
https://i.imgur.com/PeL633Z.gif

Fixed in this build: sws-2.11.0.0-Windows-x64-e12769f5.exe.

Yep it works perfectly. Thanks a million!

P.S. testing it closely I did notice that when you Crop project on new tab, the zones are replicated but not into the new position but they are referred to the original project.
Thus it will be necessary to manually move or recreate the zones.
Did you get the same result?

"Crop project to playlist" and "Crop project to playlist (new project tab)" should produce the same output.

authors: cfillion nofishonfriday tormyvancool

repo: reaper-oss/sws


text:
For Code Review

Check on Javascript best practices

Done .


text:
Calling treetagger with untokenized test?

Hi,
the example on the tt4j homepage shows tokenized input being handled by treetagger. How to I give a untokenized text to treetagger to both POS tag and tokenize?
Thanks
Shyam

See https://reckart.github.io/tt4j/tokenizer.html

authors: reckart shyamupa


text:
level 3 pull request not merged yet

@sanjay-kv please review and merge this pull request
https://github.com/Rakesh9100/CalcDiverse/pull/1820
This is the pull request i had created

@sanjay-kv I resolved the conflicts please review and merge when you are free

PR is getting reviewed one by one, you can check the PR before accepting the points request from the contributors @sanjay-kv You can remove the point label from here

repo: recodehive/resume-pitch


text:
Simplified arrow middleware definition

Issue
In https://github.com/oleksandr-danylchenko/text-annotator-js/commit/ce7014d6f74d929488cb0c277f7015a5abc90b0e#r148871559 I spotted that the arrow middleware definition can be simplified to its default form. That should be safe for the floating itself because the arrow is a "Data Middleware" that only populates the context with the positioning props, but doesn't change the behavior.
Demo
https://github.com/user-attachments/assets/ab1dab97-7e4e-41e5-8737-66a55e218372

Tested the same thing in Annotorious - yep, works :-) Thanks!

authors: oleksandr-danylchenko rsimon

repo: recogito/text-annotator-js


text:
Utilize GPT3 embedding / classification API for more automated bulk labelling

Keyword-based bulk labeling using Rubrix Rules is still too slow if I were to label thousands of texts for classification - at maximum, I can label 20 at a time since keyword match is noisy with regard to ground-truth label.
I have played with GPT3 embeddings, where applying UMAP on texts results in clear clusters with semantically similar texts in clusters. If one can create Rubrix Rules instead based on a selected area on a scatterplot of text embeddings, then one can label hundreds of texts at once, and can easily finish labeling 50,000 data points in a day with high quality. And that'd be a game-changer.
Adding on to that, I also played with GPT3 classification API, where it gives pretty accurate few-shot classifications. And if that is added to the pipeline, it'd expedite labeling even further. Making it possible to label thousands of texts at once.
I have the GPT3 embedding + classification pipeline done in a notebook, is there plan on Rubrix's side to look into utilizing GPT3?

Hey @whaowhao Thank you for bringing this up! We are working on a tutorial in which we show how you can use Epoxy to achieve the same goal you are mentioning. The workflow would be something like this:

Come up with a few rules trying to cover semantic diverse records
Provide the weak label matrix and your embeddings of choice to Epoxy (with some thresholds)
Get back an enhanced weak label matrix

Hopefully, we can share it with you soon, we would love to get your feedback.

Thanks @whaowhao ! Adding to what @dcfidalgo mentions, we've also been discussing the ability of "labelling-by-drawing" based on a 2-D embedding-based representation (UMAP or otherwise). This will be in the roadmap but not immediately.
Meanwhile I'd be really interested on collaboration/supporting you with experiments with GPT3, would you be interested?

Hi @dvsrepo yeah let's chat

authors: dcfidalgo dvsrepo whaowhao

repo: recognai/rubrix


text:
valuesAreSet field always is false.

Hi, I'm trying to create a RecommendItemsToUser request  and set the returnProperties  to true, but the valuesAreSet field in the recommendation response always comes as false.
When i try to execute recommendation.getValues() it always throws an IllegalStateException.
I checked the response  body from the Api call and it does not contain the valuesAreSet property in the payload.
Recombee Api Response Payload:
{"recommId": "8b904849-19ad-47d9-90f2-b024ca67726f", "recomms": [{"values": {"manufacturer_code": 1}, "id": "123"}]}
Request:
        final RecommendItemsToUser cf = new RecommendItemsToUser("CF", 5)
                .setReturnProperties(true);

I confirm the bug, we will fix it ASAP

Thanks @OndraFiedler

It is fixed in https://github.com/recombee/java-api-client/releases/tag/v2.0.1.
The new version has been pushed to the central repository, but it can take some time (up to few hours) before it is available.
Thanks for reporting!

authors: OndraFiedler alepinzon

repo: recombee/java-api-client


text:
docker-compose not recognising boolean values

When running docker-compose up -d the following error is observed:
ERROR: The Compose file './docker-compose.yml' is invalid because:
services.keycloak.environment.KC_HTTP_ENABLED contains false, which is an invalid type, it should be a string, number, or a null

Remediation is by encapsulating any boolean values in single quotes so they are treated as a string as noted here
Behaviour seen in commit 57d1665d323048c9feaf34a9fabe6cc454ec4ccc
Running Docker version 20.10.19, build d85ef84 on  Ubuntu 22.04.1

Just saw that a similar pull request has already been responded to

repo: reconmap/reconmap


text:
[references] Tweets with ❤

https://twitter.com/davert/status/1243285793709457411

https://github.com/shopsys/shopsys/pull/1392#issuecomment-555106644

https://twitter.com/afilina/status/1229406983486394369

https://twitter.com/davert/status/1243285793709457411

https://twitter.com/phpinsights/status/1248596452730953732

https://twitter.com/MrDanack/status/1248607716018282497

https://twitter.com/VotrubaT/status/1253631226163990529

https://twitter.com/rectorphp/status/1253432659075710977

https://twitter.com/gaborhojtsy/status/1256246616710885381

https://twitter.com/VotrubaT/status/1259164120148054016

https://twitter.com/utopicabsurd/status/1271075970712326144

https://twitter.com/LBajsarowicz/status/1272947900016967683
- https://github.com/magento/magento2/pull/27946/files

https://twitter.com/LBajsarowicz/status/1273024967349866497

https://twitter.com/jrrtgimli/status/1275332001566986241

https://twitter.com/VotrubaT/status/1275863668878688257

https://twitter.com/lulco/status/1342198519009046528

https://twitter.com/dantleech/status/1342213179334676490

https://tweetdeck.twitter.com/

https://twitter.com/VotrubaT/status/1343551843759255552

https://twitter.com/rectorphp/status/1352758017410936833

https://twitter.com/rectorphp/status/1352758017410936833

https://twitter.com/Ruud_/status/1356256886417461249

https://twitter.com/tomasnorre/status/1359934323206615040

https://www.reddit.com/r/PHP/comments/lw5kvz/code_analysis_tools_to_help_with_upgrading_an_app/gpfhde7/?utm_source=reddit&utm_medium=web2x&context=3

https://www.reddit.com/r/PHP/comments/lw5kvz/code_analysis_tools_to_help_with_upgrading_an_app/gpfem49/?utm_source=reddit&utm_medium=web2x&context=3

https://github.com/sabbelasichon/typo3-rector/issues/2094#issuecomment-805320205

https://twitter.com/vojtabiberle/status/1379127544067321872

https://twitter.com/el_stoffel/status/1384865872959975425

https://twitter.com/KPikaza/status/1386791253275299842

https://twitter.com/rsinnbeck/status/1394188533888339969

https://twitter.com/althaus_it/status/1394235695611396097

https://www.facebook.com/christophe.avonture/posts/10225263983294673?notif_id=1624954306250211&notif_t=page_tag&ref=notif

https://twitter.com/sarfraznawaz/status/1437335510213615617

https://twitter.com/Chemaclass/status/1459616944127201285

https://twitter.com/alex_s_/status/1464358800006299650

https://twitter.com/Guikingone/status/1465944064126300161

https://twitter.com/srogier/status/1473289580564647937

https://twitter.com/unagiunag/status/1478941430085459968

https://twitter.com/amakdessi/status/1479110174589603842

https://twitter.com/unagiunag/status/1494832218614935552

https://twitter.com/_stefanzweifel/status/1521922469111771136

https://twitter.com/Chemaclass/status/1531622088276156418

https://twitter.com/VotrubaT/status/1537142504839159808

https://twitter.com/Guikingone/status/1543927696274690049

https://twitter.com/tmotyl/status/1557397895388725249

https://twitter.com/brendt_gd/status/1559829464359600128

https://www.reddit.com/r/PHP/comments/wqnqs9/rector_reaches_10_million_downloads/

https://github.com/rectorphp/rector-src/pull/2778#issuecomment-1218534498

https://twitter.com/VotrubaT/status/1595734036487540736

https://twitter.com/tenmajkl/status/1596612085810876416

https://mobile.twitter.com/markusstaab/status/1592572730934980608

https://twitter.com/JustSteveKing/status/1666745322310172673

https://twitter.com/jan_linhart/status/1737386735430951208

https://twitter.com/aminetiyal/status/1746910353714204952

https://twitter.com/enunomaduro/status/1754929560112472521

https://twitter.com/ramageek/status/1754894293016391935

https://twitter.com/SlyFireFox/status/1754871230228758735

https://twitter.com/nuernberger_me/status/1754813770365337969

https://twitter.com/PatricioOnCode/status/1754860469171462399

https://github.com/rectorphp/rector/discussions/8848

repo: rectorphp/getrector-com


text:
[backport]: from 2.6 to 2.7  (#173)

fix(trustyai): prometheus rules for probe
update(trusty): prometheus to use job instead of instance name for record rules

this is missed to get into main before 2.7 branch out

repo: red-hat-data-services/rhods-operator


text:
Add support for MCG in client console

/lgtm

authors: SanjalKatiyar bipuladh

repo: red-hat-storage/odf-console


text:
Added async and sync client wrappers.

Added new async test mechanism.

See #196. This PR improves async/sync APIs.

Design decision
I choose public inheritance and void function()=delete approach.
Why don't use composition and forwarding?

This approach requires many forwarding functions. If the function parameter would change, many part of codes need to change. It is difficult to maintain.

Code image (details are omitted intentionally)
// existing classes
class client : public endpoint {};

// new classes by composition
class sync_client {
public:
    void publish(...) {
        c_->publish(...):
    }
private:
    std::shared_ptr<client> c_;
};

Why don't use private inheritance and using?

Class endpoint use std::enable_shared_from_this.

// existing classes
class endpoint : public std::enable_shared_from_this<endpoint> {};
class client : public endpoint {};

// new classes by private inheritance
class sync_client : private client {
public:
    using client::publish;
};

shared_from_this() throws bad_weak_ptr exception on runtime.
Why use void function_name() = delete ?

=delete only checks function name. So I choose the most simple signature and return type. Consider if I use the complete function signature and return type for =delete, if the function has overloads, which one should be chosen? I think there is no appropriate answer.

// existing classes
class endpoint : public std::enable_shared_from_this<endpoint> {};
class client : public endpoint {};

// new classes by public inheritance
class sync_client : public client {
public:
    void async_publish() = delete; // always no parameter and returns void
};

Why don't you create asnyc_client and sync_client as the base classes of client?

It requires big design change.
I don't have good design concept.


text:
Appstudio update test-component-pac-zvdm

Pipelines as Code configuration proposal
To start the PipelineRun, add a new comment with content /ok-to-test
For more detailed information about running a PipelineRun, please refer to Pipelines as Code documentation Running the PipelineRun
To customize the proposed PipelineRuns after merge, please refer to Build Pipeline customization

Pipelines as Code CI/test-component-pac-zvdm-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
7 seconds
init

✅ Succeeded
12 seconds
clone-repository

✅ Succeeded
29 seconds
build-container

✅ Succeeded
20 seconds
inspect-image

✅ Succeeded
1 minute
deprecated-base-image-check

✅ Succeeded
3 minutes
clair-scan

✅ Succeeded
52 seconds
clamav-scan

✅ Succeeded
17 seconds
sbom-json-check

✅ Succeeded
17 seconds
label-check

✅ Succeeded
8 seconds
show-sbom

✅ Succeeded
9 seconds
show-summary

Pipelines as Code CI/test-component-pac-zvdm-on-pull-request has failed.

StatusDurationName

---
---
init

Pipelines as Code CI/test-component-pac-zvdm-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
7 seconds
init

✅ Succeeded
21 seconds
clone-repository

✅ Succeeded
25 seconds
build-container

✅ Succeeded
12 seconds
deprecated-base-image-check

✅ Succeeded
12 seconds
inspect-image

✅ Succeeded
11 seconds
clair-scan

✅ Succeeded
37 seconds
clamav-scan

✅ Succeeded
11 seconds
sbom-json-check

✅ Succeeded
26 seconds
label-check

✅ Succeeded
6 seconds
show-sbom

✅ Succeeded
5 seconds
show-summary

Pipelines as Code CI/test-component-pac-zvdm-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
7 seconds
init

✅ Succeeded
21 seconds
clone-repository

✅ Succeeded
25 seconds
build-container

✅ Succeeded
12 seconds
deprecated-base-image-check

✅ Succeeded
12 seconds
inspect-image

✅ Succeeded
11 seconds
clair-scan

✅ Succeeded
37 seconds
clamav-scan

✅ Succeeded
11 seconds
sbom-json-check

✅ Succeeded
26 seconds
label-check

✅ Succeeded
6 seconds
show-sbom

✅ Succeeded
5 seconds
show-summary


text:
Appstudio update test-component-pac-kjnh

Pipelines as Code configuration proposal

Pipelines as Code CI/test-component-pac-kjnh-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
9 seconds
appstudio-init

✅ Succeeded
9 seconds
clone-repository

✅ Succeeded
18 seconds
appstudio-configure-build

✅ Succeeded
19 seconds
sast-snyk-check

✅ Succeeded
43 seconds
build-container

✅ Succeeded
20 seconds
sanity-inspect-image

✅ Succeeded
17 seconds
deprecated-base-image-check

✅ Succeeded
49 seconds
clamav-scan

✅ Succeeded
17 seconds
clair-scan

✅ Succeeded
23 seconds
sbom-json-check

✅ Succeeded
12 seconds
sanity-label-check

✅ Succeeded
11 seconds
sanity-optional-label-check

✅ Succeeded
8 seconds
show-summary

Pipelines as Code CI/test-component-pac-kjnh-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
9 seconds
appstudio-init

✅ Succeeded
9 seconds
clone-repository

✅ Succeeded
18 seconds
appstudio-configure-build

✅ Succeeded
19 seconds
sast-snyk-check

✅ Succeeded
43 seconds
build-container

✅ Succeeded
20 seconds
sanity-inspect-image

✅ Succeeded
17 seconds
clair-scan

✅ Succeeded
49 seconds
clamav-scan

✅ Succeeded
17 seconds
deprecated-base-image-check

✅ Succeeded
23 seconds
sbom-json-check

✅ Succeeded
11 seconds
sanity-optional-label-check

✅ Succeeded
12 seconds
sanity-label-check

✅ Succeeded
8 seconds
show-summary

Pipelines as Code CI/test-component-pac-kjnh-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
8 seconds
appstudio-init

✅ Succeeded
15 seconds
clone-repository

✅ Succeeded
13 seconds
sast-snyk-check

✅ Succeeded
14 seconds
appstudio-configure-build

✅ Succeeded
45 seconds
build-container

✅ Succeeded
24 seconds
sanity-inspect-image

✅ Succeeded
22 seconds
deprecated-base-image-check

✅ Succeeded
47 seconds
clamav-scan

✅ Succeeded
17 seconds
clair-scan

✅ Succeeded
27 seconds
sbom-json-check

✅ Succeeded
13 seconds
sanity-optional-label-check

✅ Succeeded
11 seconds
sanity-label-check

✅ Succeeded
6 seconds
show-summary

Pipelines as Code CI/test-component-pac-kjnh-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
8 seconds
appstudio-init

✅ Succeeded
15 seconds
clone-repository

✅ Succeeded
14 seconds
appstudio-configure-build

✅ Succeeded
13 seconds
sast-snyk-check

✅ Succeeded
45 seconds
build-container

✅ Succeeded
22 seconds
deprecated-base-image-check

✅ Succeeded
24 seconds
sanity-inspect-image

✅ Succeeded
47 seconds
clamav-scan

✅ Succeeded
17 seconds
clair-scan

✅ Succeeded
27 seconds
sbom-json-check

✅ Succeeded
13 seconds
sanity-optional-label-check

✅ Succeeded
11 seconds
sanity-label-check

✅ Succeeded
6 seconds
show-summary


text:
Appstudio update mvp-test-component

Pipelines as Code configuration proposal

Pipelines as Code CI/mvp-test-component-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
10 seconds
init

✅ Succeeded
18 seconds
clone-repository

✅ Succeeded
1 minute
build-container

✅ Succeeded
12 seconds
sanity-inspect-image

✅ Succeeded
11 seconds
deprecated-base-image-check

✅ Succeeded
58 seconds
clamav-scan

✅ Succeeded
16 seconds
clair-scan

✅ Succeeded
9 seconds
sbom-json-check

✅ Succeeded
17 seconds
sanity-label-check

✅ Succeeded
15 seconds
sanity-optional-label-check

✅ Succeeded
6 seconds
show-summary

repo: redhat-appstudio-qe/hacbs-test-project


text:
Added ppc64le support

This PR will add multi-architecture support to the application-service operator image

/retest

repo: redhat-appstudio/application-service


text:
KFLUXINFRA-651: Adding Instance Types for Multi-Platform Builds

Adding two types of instances

Higher Memory (1:4 ratio for cpu: memory)
Higher CPU (1:2 ratio for cpu: memory)

Note Some users may require more memory and less CPU, making Memory Optimized Instances the better choice for them. On the other hand, some users may need more CPU power but less memory, in which case CPU-optimized instances would be a good fit. Therefore, a combination of memory-optimized and CPU-optimized instances is essential to cater to different user needs. In the label naming, m refers to memory optimised and c refers to compute optimised.

Memory Optimised (not aws terminology, their memory optimized class starts from r)

Multi-Platform Label
Instance Type
Architecture
CPU
Memory(GB)

linux-mlarge/amd64
m5a.large
AMD64
2
8

linux-mxlarge/amd64
m6a.xlarge
AMD64
4
16

linux-m2xlarge/amd64
m6a.2xlarge
AMD64
8
32

linux-m4xlarge/amd64
m6a.4xlarge
AMD64
16
64

linux-m8xlarge/amd64
m6a.8xlarge
AMD64
32
128

linux-mlarge/arm64
m6g.large
ARM64
2
8

linux-mxlarge/arm64
m6g.xlarge
ARM64
4
16

linux-m2xlarge/arm64
m6g.2xlarge
ARM64
8
32

linux-m4xlarge/arm64
m6g.4xlarge
ARM64
16
64

linux-m8xlarge/arm64
m6g.8xlarge
ARM64
32
128

CPU Optimised (again not aws terminology)

Multi-Platform Label
Instance Type
Architecture
CPU
Memory(GB)

linux-clarge/amd64
c6a.xlarge
AMD64
4
8

linux-cxlarge/amd64
c6a.2xlarge
AMD64
8
16

linux-c2xlarge/amd64
c6a.4xlarge
AMD64
16
32

linux-c4xlarge/amd64
c6a.8xlarge
AMD64
32
64

linux-clarge/arm64
c6g.xlarge
ARM64
4
8

linux-cxlarge/arm64
c6g.2xlarge
ARM64
8
16

linux-c2xlarge/arm64
c6g.4xlarge
ARM64
16
32

linux-c4xlarge/arm64
c6g.8xlarge
ARM64
32
64

Suggestion We can minimize code duplication by utilizing default values for common parameters like imageId, subnetId, region, etc, unless specified otherwise.

One thought: we will have quay.io with AWS internal communication right? otherwise how about using enhanced network enabled instances (with *n) for better push pull speeds?

One thought: we will have quay.io with AWS internal communication right? otherwise how about using enhanced network enabled instances (with *n) for better push pull speeds?

ENA is enabled for the instance types we are using m6a.xxxxx, m6g.xxxxx, c6a.xxxxx and c6g.xxxxx. Reference AWS Document -- https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/enhanced-networking-ena.html

/lgtm

authors: bamachrn manish-jangra

repo: redhat-appstudio/infra-deployments


text:
Promote release-service from staging to production

Included PRs:

https://github.com/konflux-ci/release-service/pull/638
https://github.com/konflux-ci/release-service/pull/637
https://github.com/konflux-ci/release-service/pull/636
https://github.com/konflux-ci/release-service/pull/635
https://github.com/konflux-ci/release-service/pull/633
https://github.com/konflux-ci/release-service/pull/630
https://github.com/konflux-ci/release-service/pull/629
https://github.com/konflux-ci/release-service/pull/632
https://github.com/konflux-ci/release-service/pull/628
https://github.com/konflux-ci/release-service/pull/627
https://github.com/konflux-ci/release-service/pull/626
https://github.com/konflux-ci/release-service/pull/622

/lgtm

authors: johnbieren mmalina


text:
fix: increase timeout for e2e

Why
Currently there's a 1h (default) timeout for running e2e. Since the number of tests is growing and takes more time to finish, we are sometimes hitting the limit. If that happens, tests get interrupted and a CI check is marked as failed.
This is a temporary solution until we enable parallel e2e test run for infra-deployments (which was already enabled for e2e-tests repo)

/lgtm

Ran 87 of 92 Specs in 4424.652 seconds
SUCCESS! -- 87 Passed | 0 Failed | 0 Pending | 5 Skipped

authors: psturc tkdchen


text:
Add auth-option to authenticate as githubapp

Fixes #112.
Adds support for authenticating as github-app, which offers:

more narrow-grained permissions (avoiding PATs)
increased security, using a private key
increased API-quota

The github-client is now wired up/facilitated through the go-github-app library, which offers caching, metrics etc.
Note: Draft PR - not yet tested, for feedback.

go-githubapp now has convenience function to configure the transport.
I think this is good to go, but have not yet been able to test it.

That should be it. I've updated the docs and tested it in my 4.6.x cluster, using app-based auth:
group-sync-operator-controller-manager-54d5874d76-kh5cq manager 2021-09-06T17:31:04.501Z        INFO    controllers.GroupSync   Beginning Sync  {"groupsync": "group-sync-operator/github-groupsync", "Provider": "github"}
group-sync-operator-controller-manager-54d5874d76-kh5cq manager 2021-09-06T17:31:06.354Z        INFO    controllers.GroupSync   Sync Completed Successfully     {"groupsync": "group-sync-operator/github-groupsync", "Provider": "github", "Groups Created or Updated": 1}

CC @sabre1041 @raffaelespazzoli

@sabre1041 I think all points have been covered now - thanks for the input!

repo: redhat-cop/group-sync-operator


text:
Run go mod tidy on each pull request and fail the build if there are changes

We will be outputting the vendor directory in the midstream repo, and this will prevent any possible conflicts.

Actually this is not needed: https://github.blog/changelog/2020-10-19-dependabot-go-mod-tidy-and-vendor-support/

repo: redhat-developer/app-services-cli


text:
fix: add server side backed up metrics

Motivation
This change uses backend compiled metrics for consumer groups.
This have been in production for quite a while and have been extensively tested.
Verification

Get Kafka
Create new topic test
Create kcat.properties based of the kcat guide
kcat -b <yourhostname -F ./kcat.properties -P -t test`
run rhoas kafka consumer-group list
run rhoas kafka consumer-group describe

I have used latest version of SDK. We need to wait to make sure that it is currently deployed to production

@rkpattnaik780

FYI @mikeedgar API is working find and was tested end to end


text:
Provide simplified ability to switch between stagging and production environments

We can add env variable into OLM as example (can be empty) and then scripts can patch it (as discussed with @b1zzu)
I will verify if that really works and document this in contributing docs

Added env variable directly to the OLM

repo: redhat-developer/app-services-operator


text:
doc: OpenShift argocd CLI client command reference documentation

What type of PR is this?
/kind documentation
What does this PR do / why we need it:
Have you updated the necessary documentation?

[ ] Documentation update is required by this PR.
[ ] Documentation has been updated.

Which issue(s) this PR fixes:
Fixes #?
Test acceptance criteria:

[ ] Unit Test
[ ] E2E Test

How to test changes / Special notes to the reviewer:

@anandf How about the updates to these sections?
Update these existing sections:

Creating an application by using the oc tool

https://docs.openshift.com/gitops/1.11/argocd_applications/deploying-a-spring-boot-application-with-argo-cd.html#creating-an-application-by-using-the-oc-tool_deploying-a-spring-boot-application-with-argo-cd

https://docs.openshift.com/gitops/1.11/declarative_clusterconfig/configuring-an-openshift-cluster-by-deploying-an-application-with-cluster-configurations.html#creating-an-application-by-using-the-oc-tool_configuring-an-openshift-cluster-by-deploying-an-application-with-cluster-configurations

Synchronizing your application with your Git repository

https://docs.openshift.com/gitops/1.11/declarative_clusterconfig/configuring-an-openshift-cluster-by-deploying-an-application-with-cluster-configurations.html#synchronizing-your-application-application-with-your-git-repository_configuring-an-openshift-cluster-by-deploying-an-application-with-cluster-configurations

@anandf Can we add some content for these sections, if they are relevant at all?

About the OpenShift argo cd CLI (I think this is a nice to have section)
Logging in to the OpenShift argo cd CLI using a web browser
usage instructions - information that must go as admonitions such as Note, Important, Tip, caution, or warning.

@anandf How about the updates to these sections?
Update these existing sections:

Creating an application by using the oc tool

https://docs.openshift.com/gitops/1.11/argocd_applications/deploying-a-spring-boot-application-with-argo-cd.html#creating-an-application-by-using-the-oc-tool_deploying-a-spring-boot-application-with-argo-cd
https://docs.openshift.com/gitops/1.11/declarative_clusterconfig/configuring-an-openshift-cluster-by-deploying-an-application-with-cluster-configurations.html#creating-an-application-by-using-the-oc-tool_configuring-an-openshift-cluster-by-deploying-an-application-with-cluster-configurations

Synchronizing your application with your Git repository

https://docs.openshift.com/gitops/1.11/declarative_clusterconfig/configuring-an-openshift-cluster-by-deploying-an-application-with-cluster-configurations.html#synchronizing-your-application-application-with-your-git-repository_configuring-an-openshift-cluster-by-deploying-an-application-with-cluster-configurations

Added sections for creating and syncing app using CLI in both normal and core modes.

@anandf Can we add some content for these sections, if they are relevant at all?

Logging in to the OpenShift argo cd CLI using a web browser -> This is not applicable. One has to login via the CLI itself. Its not possible to login via web browser like its possible for oc login

authors: Srivaralakshmi anandf

repo: redhat-developer/gitops-operator


text:
odo dev add flag to run non-default build command.

User Story

As an odo user
I want to be able to execute alternative build command instead of the default one
So that I can run my with different options (different configuration, flags, runtime versions etc..) without modifying the default command.

Example:
Go devfile has the following default build command.
  - exec:
      commandLine: GOCACHE=${PROJECT_SOURCE}/.cache go build main.go
      component: runtime
      group:
        isDefault: true
        kind: build
      workingDir: ${PROJECT_SOURCE}
    id: build

In some situations, I want to pass arguments to linker to for example set string value of a variable.
This can be done adding -ldflags="-X github.com/redhat-developer/odo/pkg/segment.writeKey=foo".
Currently I have to edit the commandLine in order to be able to execute build with different arguments.
Instead of that it would be nice to be able to add extra run command like this:
  - exec:
      commandLine: GOCACHE=${PROJECT_SOURCE}/.cache go build -ldflags="-X github.com/redhat-developer/odo/pkg/segment.writeKey=foo" main.go
      component: runtime
      group:
        isDefault: false
        kind: build
      workingDir: ${PROJECT_SOURCE}
    id: build-with-key

And then simply execute odo dev --build-command build-with-key, when I want to switch back to using the default profile, I stop running odo dev command and start it again, but this time without --build-command flag.
Acceptance Criteria

[ ] odo dev should have --build-command flag that controls what command is used to build application.

/kind user-story

TODO (to not forget):
As commented out in [1]:

we should try to harmonize the behaviour between commands in pkg/libdevfile/libdevfile.go. Deploy is using getDefaultCommand, when Build/Test/Run is using getCommandAssociatedToGroup

[1] https://github.com/redhat-developer/odo/pull/5768#discussion_r895480523

repo: redhat-developer/odo


text:
fix release scripts - 'odo version' output changed

😞
forgot to change one place

similar to #451


text:
Provide tooltips on icon

As a user, the icons themselves are not going to be sufficient to tell me what actions are behind each buttons.
It would be nicer to provide tooltips behind the button, so that the user can discover what's the button will do, without having to click on it.

authors: fbricon slemeur

repo: redhat-developer/openshift-dd-ext


text:
RHIDP-3377: Adding cross-links to the Installation titles

IMPORTANT: Do Not Merge - To be merged by Docs Team Only
Version(s): 1.2, 1.3
Issue: RHIDP-3377
Reviews:

[x] Docs review: @hmanwani-rh

/cherry-pick release-1.3

/cherry-pick 1.2.x

authors: hmanwani-rh pabel-rh


text:
Added discover content

I’m creating this PR because the About RHDH title is already published on docs.redhat.com, but currently, it doesn’t contain any content. For now, I’m adding content to the page, which can be refined and improved later.
cc @jmagak

Closing this PR, since the title is now unpublished in Pantheon.


text:
Trigger a first build upon fling completion

Create a new Build resource from the generated BuildConfig resource in the OpenShift project.

Would adding this trigger (https://github.com/tnozicka/openshift-templates/blob/master/pipeline-template.yaml#L34) be enough?

6d85abfc3440d379e7135325f7005bbf4b80e57c

authors: ALRubinger tnozicka xcoulon

repo: redhat-kontinuity/catapult


text:
operator vfunction-server-operator (v2.3.594)

New operator bundle
Name: vfunction-server-operator
Version: v2.3.594
Certification project: 5f64dc1e0a4d06443d2818ad
Test result URL: https://catalog.redhat.com/api/containers/v1/projects/certification/test-results/id/61917043d115ef379a598e5e
Test logs URL: https://catalog.redhat.com/api/containers/v1/projects/certification/artifacts/id/61917042d6b39d004292bad1

Hi,
I'm sure 100% that my ci tests passed okay (even 3 times...) on my local OpenShift cluster with the most updated operator-ci-pipeline.yml and tasks from the operator-pipelines repo.
I did have some issues with timeout exceeding on both ScorecardBasicSpecCheck & ScorecardOlmSuiteCheck before I updated. (I couldn't access the test result URL nor the logs URL from above to see the exact errors for this run - to be sure they are the same, though)
Before starting the long journey of opening a support case for this, I just wanted to make sure that the errors are not on your end because the tests cluster is not updated correctly? Could you please verify that tests can pass at all now for ScorecardBasicSpecCheck & ScorecardOlmSuiteCheck on your testing cluster?
Thanks.

Now I could also see in the logs that both ScorecardBasicSpecCheck and ScorecardOlmSuiteCheck failed on the 30 seconds timeout (as I expected and mentioned in my previous comment).
As I also mentioned - I had this error too until I pulled a new version from operator-pipelines and applied all pipelines and tasks on the OpenShift cluster.
From the last Perflight.log:
time="2021-11-15T13:58:35Z" level=info msg="running check: ScorecardBasicSpecCheck"
time="2021-11-15T13:58:35Z" level=debug msg="Running operator-sdk scorecard check for quay.io/operator-pipeline-prod/vfunction-server-operator:v2.3.594"
time="2021-11-15T13:58:35Z" level=debug msg="--selector=[test=basic-check-spec-test]"
time="2021-11-15T13:58:35Z" level=trace msg="running scorecard with the following invocation[operator-sdk scorecard --output json --selector=test=basic-check-spec-test --kubeconfig /tmp/kubeconfig-3421170286 --namespace default --service-account default --config /tmp/scorecard-test-config-3472466720.yaml --verbose /tmp/preflight-3179944778/fs]"
time="2021-11-15T13:59:05Z" level=error msg="stdout: "
time="2021-11-15T13:59:05Z" level=error msg="stderr: time="2021-11-15T13:58:35Z" level=debug msg="Debug logging is set"\nError: error running tests context deadline exceeded\nUsage:\n  operator-sdk scorecard [flags]\n\nFlags:\n  -c, --config string            path to scorecard config file\n  -h, --help                     help for scorecard\n      --kubeconfig string        kubeconfig path\n  -L, --list                     Option to enable listing which tests are run\n  -n, --namespace string         namespace to run the test images in\n  -o, --output string            Output format for results. Valid values: text, json, xunit (default "text")\n  -l, --selector string          label selector to determine which tests are run\n  -s, --service-account string   Service account to use for tests (default "default")\n  -x, --skip-cleanup             Disable resource cleanup after tests are run\n  -b, --storage-image string     Storage image to be used by the Scorecard pod (default "docker.io/library/busybox@sha256:c71cb4f7e8ececaffb34037c2637dc86820e4185100e18b4d02d613a9bd772af")\n  -t, --test-output string       Test output directory. (default "test-output")\n  -u, --untar-image string       Untar image to be used by the Scorecard pod (default "registry.access.redhat.com/ubi8@sha256:910f6bc0b5ae9b555eb91b88d28d568099b060088616eba2867b07ab6ea457c7")\n  -w, --wait-time duration       seconds to wait for tests to complete. Example: 35s (default 30s)\n\nGlobal Flags:\n      --plugins strings   plugin keys to be used for this subcommand execution\n      --verbose           Enable verbose logging\n\ntime="2021-11-15T13:59:05Z" level=fatal msg="error running tests context deadline exceeded"\n"
time="2021-11-15T13:59:05Z" level=info msg="check completed: ScorecardBasicSpecCheck" ERROR="failed to run operator-sdk scorecard: exit status 1" result="failed to run operator-sdk scorecard: exit status 1"
time="2021-11-15T13:59:05Z" level=info msg="running check: ScorecardOlmSuiteCheck"
time="2021-11-15T13:59:05Z" level=debug msg="Running operator-sdk scorecard Check for quay.io/operator-pipeline-prod/vfunction-server-operator:v2.3.594"
time="2021-11-15T13:59:05Z" level=debug msg="--selector=[suite=olm]"
time="2021-11-15T13:59:05Z" level=trace msg="running scorecard with the following invocation[operator-sdk scorecard --output json --selector=suite=olm --kubeconfig /tmp/kubeconfig-3421170286 --namespace default --service-account default --config /tmp/scorecard-test-config-2813129432.yaml --verbose /tmp/preflight-3179944778/fs]"
time="2021-11-15T13:59:36Z" level=error msg="stdout: "
time="2021-11-15T13:59:36Z" level=error msg="stderr: time="2021-11-15T13:59:05Z" level=debug msg="Debug logging is set"\nError: error running tests context deadline exceeded\nUsage:\n  operator-sdk scorecard [flags]\n\nFlags:\n  -c, --config string            path to scorecard config file\n  -h, --help                     help for scorecard\n      --kubeconfig string        kubeconfig path\n  -L, --list                     Option to enable listing which tests are run\n  -n, --namespace string         namespace to run the test images in\n  -o, --output string            Output format for results. Valid values: text, json, xunit (default "text")\n  -l, --selector string          label selector to determine which tests are run\n  -s, --service-account string   Service account to use for tests (default "default")\n  -x, --skip-cleanup             Disable resource cleanup after tests are run\n  -b, --storage-image string     Storage image to be used by the Scorecard pod (default "docker.io/library/busybox@sha256:c71cb4f7e8ececaffb34037c2637dc86820e4185100e18b4d02d613a9bd772af")\n  -t, --test-output string       Test output directory. (default "test-output")\n  -u, --untar-image string       Untar image to be used by the Scorecard pod (default "registry.access.redhat.com/ubi8@sha256:910f6bc0b5ae9b555eb91b88d28d568099b060088616eba2867b07ab6ea457c7")\n  -w, --wait-time duration       seconds to wait for tests to complete. Example: 35s (default 30s)\n\nGlobal Flags:\n      --plugins strings   plugin keys to be used for this subcommand execution\n      --verbose           Enable verbose logging\n\ntime="2021-11-15T13:59:36Z" level=fatal msg="error running tests context deadline exceeded"\n"
time="2021-11-15T13:59:36Z" level=info msg="check completed: ScorecardOlmSuiteCheck" ERROR="failed to run operator-sdk scorecard: exit status 1" result="failed to run operator-sdk scorecard: exit status 1"

Thank you.  We are looking into this on our side.

Hi,
Any news regarding this?
Thanks.

authors: tonytcampbell vfunction


text:
operator neuvector-community-operator (1.3.5)

Signed-off-by: selvamt94 sthangaraj@neuvector.com
Thanks submitting your Operator. Please check below list before you create your Pull Request.
New Submissions

[x] Are you familiar with our contribution guidelines?
[x] Have you packaged and deployed your Operator for Operator Framework?
[x] Have you tested your Operator with all Custom Resource Definitions?
[x] Have you tested your Operator in all supported installation modes?
[x] Have you considered whether you want use semantic versioning order?
[x] Is your submission signed?
[x] Is operator icon set?

Updates to existing Operators

[x] Did you create a ci.yaml file according to the update instructions?
[x] Is your new CSV pointing to the previous version with the replaces property if you chose replaces-mode via the updateGraph property in ci.yaml?
[x] Is your new CSV referenced in the appropriate channel defined in the package.yaml or annotations.yaml ?
[x] Have you tested an update to your Operator when deployed via OLM?
[x] Is your submission signed?

Your submission should not

[x] Modify more than one operator
[x] Modify an Operator you don't own
[x] Rename an operator - please remove and add with a different name instead
[x] Modify any files outside the above mentioned folders
[x] Contain more than one commit. Please squash your commits.

Operator Description must contain (in order)

[x] Description about the managed Application and where to find more information
[x] Features and capabilities of your Operator and how to use it
[x] Any manual steps about potential pre-requisites for using your Operator

Operator Metadata should contain

[x] Human readable name and 1-liner description about your Operator
[x] Valid category name1
[x] One of the pre-defined capability levels2
[x] Links to the maintainer, source code and documentation
[x] Example templates for all Custom Resource Definitions intended to be used
[x] A quadratic logo

Remember that you can preview your CSV here.
--
1 If you feel your Operator does not fit any of the pre-defined categories, file an issue against this repo and explain your need
2 For more information see here

/merge possible

/merge possible


text:
operator cert-manager (1.10.1)

Signed-off-by: Richard Wall richard.wall@jetstack.io

/hold

Sanity checking the changes between 1.10.0 and 1.10.1
✦ $ git diff  --no-index 1.10.0 1.10.1
diff --git a/1.10.0/manifests/cert-manager.clusterserviceversion.yaml b/1.10.1/manifests/cert-manager.clusterserviceversion.yaml
index 4f298cca..402923d3 100644
--- a/1.10.0/manifests/cert-manager.clusterserviceversion.yaml
+++ b/1.10.1/manifests/cert-manager.clusterserviceversion.yaml
@@ -68,7 +68,8 @@ metadata:
     capabilities: Full Lifecycle
     categories: Security
     containerImage: quay.io/jetstack/cert-manager-controller:v1.10.0
-    createdAt: '2022-11-02T14:25:05'
+    createdAt: '2022-11-04T10:22:12'
+    olm.skipRange: '>=1.10.0 <1.10.1'
     operators.operatorframework.io/builder: operator-sdk-v1.25.0
     operators.operatorframework.io/internal-objects: |-
       [
@@ -83,7 +84,7 @@ metadata:
     operatorframework.io/arch.arm64: supported
     operatorframework.io/arch.ppc64le: supported
     operatorframework.io/arch.s390x: supported
-  name: cert-manager.v1.10.0
+  name: cert-manager.v1.10.1
   namespace: placeholder
 spec:
   apiservicedefinitions: {}
@@ -745,9 +746,9 @@ spec:
                 - --secure-port=10250
                 - --dynamic-serving-ca-secret-namespace=$(POD_NAMESPACE)
                 - --dynamic-serving-ca-secret-name=cert-manager-webhook-ca
-                - --dynamic-serving-dns-names=cert-manager-webhook
-                - --dynamic-serving-dns-names=cert-manager-webhook.$(POD_NAMESPACE)
-                - --dynamic-serving-dns-names=cert-manager-webhook.$(POD_NAMESPACE).svc
+                - --dynamic-serving-dns-names=cert-manager-webhook-service.$(POD_NAMESPACE).svc
+                - --tls-cert-file=/apiserver.local.config/certificates/apiserver.crt
+                - --tls-private-key-file=/apiserver.local.config/certificates/apiserver.key
                 env:
                 - name: POD_NAMESPACE
                   valueFrom:
@@ -879,7 +880,7 @@ spec:
   provider:
     name: The cert-manager maintainers
     url: https://cert-manager.io/
-  version: 1.10.0
+  version: 1.10.1
   webhookdefinitions:
   - admissionReviewVersions:
     - v1

/merge possible

/merge possible

/hold cancel

/merge possible

authors: framework-automation wallrj


text:
operator pulp-operator (1.0.0-beta.2)

Thanks for submitting your Operator. Please check the below list before you create your Pull Request.
New Submissions

[ ] Are you familiar with our contribution guidelines?
[ ] Have you packaged and deployed your Operator for Operator Framework?
[ ] Have you tested your Operator with all Custom Resource Definitions?
[ ] Have you tested your Operator in all supported installation modes?
[ ] Have you considered whether you want to use semantic versioning order?
[ ] Is your submission signed?
[ ] Is operator icon set?

Updates to existing Operators

[ ] Did you create a ci.yaml file according to the update instructions?
[ ] Is your new CSV pointing to the previous version with the replaces property if you chose replaces-mode via the updateGraph property in ci.yaml?
[ ] Is your new CSV referenced in the appropriate channel defined in the package.yaml or annotations.yaml ?
[ ] Have you tested an update to your Operator when deployed via OLM?
[ ] Is your submission signed?

Your submission should not

[ ] Modify more than one operator
[ ] Modify an Operator you don't own
[ ] Rename an operator - please remove and add with a different name instead
[ ] Modify any files outside the above mentioned folders
[ ] Contain more than one commit. Please squash your commits.

Operator Description must contain (in order)

[ ] Description of the managed Application and where to find more information
[ ] Features and capabilities of your Operator and how to use it
[ ] Any manual steps about potential pre-requisites for using your Operator

Operator Metadata should contain

[ ] Human readable name and 1-liner description about your Operator
[ ] Valid category name1
[ ] One of the pre-defined capability levels2
[ ] Links to the maintainer, source code and documentation
[ ] Example templates for all Custom Resource Definitions intended to be used
[ ] A quadratic logo

Remember that you can preview your CSV here.
--
1 If you feel your Operator does not fit any of the pre-defined categories, file an issue against this repo and explain your need
2 For more information see here

/merge possible

authors: framework-automation git-hyagi


text:
operator [CI] konveyor-operator

Just switching to use semver-mode.

/merge possible

/merge possible

authors: djzager framework-automation


text:
operator jaeger (1.52.0)

Thanks for submitting your Operator. Please check the below list before you create your Pull Request.
New Submissions

[ ] Are you familiar with our contribution guidelines?
[ ] Are you familiar with our operator pipeline?
[ ] Have you tested your Operator with all Custom Resource Definitions packaging?
[ ] Have you tested your Operator in all supported installation modes?
[ ] Have you considered whether you want to use semantic versioning order?
[ ] Is your submission signed?
[ ] Is operator icon set?

Your submission should not

[ ] Add more than one operator bundle per PR
[ ] Modify any operator
[ ] Rename an operator
[ ] Modify any files outside the above mentioned folders
[ ] Contain more than one commit. Please squash your commits.

Operator Description must contain (in order)

[ ] Description of the managed Application and where to find more information
[ ] Features and capabilities of your Operator and how to use it
[ ] Any manual steps about potential pre-requisites for using your Operator

Operator Metadata should contain

[ ] Human readable name and 1-liner description about your Operator
[ ] Valid category name1
[ ] One of the pre-defined capability levels2
[ ] Links to the maintainer, source code and documentation
[ ] Example templates for all Custom Resource Definitions intended to be used
[ ] A quadratic logo

Remember that you can preview your CSV here.
--
1 If you feel your Operator does not fit any of the pre-defined categories, file an issue against this repo and explain your need
2 For more information see here

/pipeline restart community-hosted-pipelin

/pipeline restart community-hosted-pipeline


text:
[DRAFT]: Manifests to install preGA sync operator from custom operator catalog

TODO: Understand where to ubicate the added extra-manifests for day2 installation as a policy.

We need to figure out how to add those manifests as Policies or PoliciesGenTemplate (PGT) objects referenced from the SiteConfig.


text:
add gcp image list command to CLI

Hey @major @FKolwa ,
I am a bit confused right now. We assign the registered github secret secrets.GOOGLE_APPLICATION_CREDENTIALS to an environment variable GCP_APP_CREDENTIALS, but we never use it.
In the get_google_images function we create an compute_v1.ImagesClient client, is he supposed to use those credentials?
I went to the google docs, but it also didn't really helped me. :)
Can you give me some hints? :sweat_smile:

@miyunari Yup that is correct! It isn't necessary to reference the ENV in code.
In fact you won't find any of the other secrets either (like AWS_ACCESS_KEY_ID).
Most (if not all) cloud provider CLIs authenticate using local configurations that are loaded into ENVs at runtime.
Usually you would use you user credentials to sign into Google Cloud but with an automated service like this a service account can be used.
The fact that "GOOGLE_APPLICATION_CREDENTIALS" is set for the workflow step means that the gcloud cli will be able to read it and use it to authenticate with the cloud provider API. I'll leave you a link in case you want to read more about Google Application Default Credentials (ADC): https://cloud.google.com/docs/authentication/provide-credentials-adc#local-key
A small hint though: The env needs to be mapped to "GOOGLE_APPLICATION_CREDENTIALS" in the workflow context as well for it to properly work.
Hope this helps a little!

Thank you @FKolwa ! That was exactly the information I was looking for :smile:
But now, there is another issue :sweat_smile:  Unfortunately it's now unclear to me, how to test my changes.
I got this reference from major, but I don't see the correlation:
https://github.com/redhatcloudx/rhelocator/blob/b97967e77354d0331f0f7bc4a607c00b4b1eea16/tests/test_cli.py#L77-L103

@miyunari Haha yes this is a bit confusing tbh!
The gcloud implementation is pretty rough at this point. get_google_images currently queries all images in the rhel-cloud project and returns everything that isn't deprecated.
In the scope of this ticket, my requirement for an end to end test would be

query the correct api endpoint by calling get_google_images by using 'runner.invoke'
parse the json data
confirm that all images that are returned do not contain the first level key status with the value 'DEPRECATED'
In this case you can copy / paste most of what @major wrote for the azure test!

For the offline test

copy the structure of the e2e test you just wrote
create a new mock for the google images in conftest (you can take a look at the AWS mockups. You need to create a new list of mocked images in a json format and create a new fixture that is passed to you offline test).

Now for the tricky part: How do you know what data structure to expect from the google API?
Well if you call gcloud and query for projects within 'rhel-cloud' you will receive something like this:
  {     "architecture": "X86_64",     "archiveSizeBytes": "4184623872",     "creationTimestamp": "2022-09-20T16:32:45.492-07:00",     "description": "Red Hat, Red Hat Enterprise Linux, 9, x86_64 built on 20220920, supports Shielded VM features",     "diskSizeGb": "20",     "family": "rhel-9",     "guestOsFeatures": [       {         "type": "UEFI_COMPATIBLE"       },       {         "type": "VIRTIO_SCSI_MULTIQUEUE"       },       {         "type": "SEV_CAPABLE"       },       {         "type": "GVNIC"       }     ],     "id": "2043557223711896434",     "kind": "compute#image",     "labelFingerprint": "42WmSpB8rSM=",     "licenseCodes": [       "7883559014960410759"     ],     "licenses": [       "https://www.googleapis.com/compute/beta/projects/rhel-cloud/global/licenses/rhel-9-server"     ],     "name": "rhel-9-v20220920",     "rawDisk": {       "containerType": "TAR",       "source": ""     },     "rolloutOverride": {       "defaultRolloutTime": "2022-09-25T15:32:42Z",       "locationRolloutPolicies": {         "zones/asia-east1-a": "2022-09-22T04:32:42Z",         ....         "zones/us-west4-c": "2022-09-25T04:32:42Z"       }     },     "selfLink": "https://www.googleapis.com/compute/beta/projects/rhel-cloud/global/images/rhel-9-v20220920",     "sourceType": "RAW",     "status": "READY",     "storageLocations": [       "eu",       "asia",       "us"     ]   }
At this point we don't extract any specific information from this returned data (like we do for AWS) and this is not within the scope of your ticket so feel free to create a minimal test mockup version of this data structure that only contains something like
{ "status": "READY" }

Oh boy, that was my mistake. I must have been looking at two things at the same time and put the wrong variable name in the actions workflow. 🤦🏻♂

@major I think you were right :smile: . I shortened the variable name, because I thought we have to store it in config.py and use it somewhere :woman_facepalming:

Oh, I see I have some merge conflicts, will try to resolve

authors: FKolwa miyunari

repo: redhatcloudx/rhelocator


text:
feat: use uber-go/mock instead of golang/mock

Resolves #297

Thanks @dlsrb6342!

repo: redis/rueidis


text:
Feature Request: Add possibility to make new post with custom date-time

I want to move many entries from my old blog to Hubzilla. I would like to set original date for this posts.
Is it possible to add a field for setting a specific date of publication during editing post?

I think we could send an invite once while creating the chatroom. We have a similar functionality for wikis and files already. We could ad a switch labeled Create a status post for this chat

This is possible at post creation time using the  'Delayed Posting' feature. You can set the post date (either forwards or backwards) during post creation. This is not available when editing an existing post because the posts would have already been delivered.
The feature requires an account level of 2; which you can find on your settings/account page; followed by activating the Delayed Posting feature at settings/features -> Post Composition Features

The feature requires an account level of 2

Thanks, i changed account level and found it, it works good.
I'll close this issue.

authors: git-marijus zlaxy zotlabs

repo: redmatrix/hubzilla


text:
update docs

The previous documentation is misleading, as OpenSSL 1.1.0 did not change the fact that contextSetVerificationMode is necessary for OpenSSL to check anything about the certificate. Also, I added a link to the (new) function enabling the OpenSSL built-in hostname validation instead of referring to a PDF.

Hi @amesgen, thanks for the PR.
You absolutely right, contextSetVerificationMode has to be called even with OpenSSL >= 1.1.0. When I changed that part of the documentation a few weeks ago I wasn't careful enough.
My only concern with the new phrasing that you propose is that I think it would be better to keep the note about old (<1.1.0) versions of OpenSSL not verifying automatically the peer's hostname, even with contextSetVerificationMode. How about if we added the following at the end of your version:

In addition to that, if you are using a version of OpenSSL older than 1.1.0, you also need to verify that the peer's hostname matches with one specified in the certificate. You can find information on how to do that here. Newer versions of OpenSSL (>=1.1.0) perform that check automatically.

or something like that.

Hmm, I am no expert in OpenSSL, but I think that, even in OpenSSL >= 1.1.0, setting contextSetVerificationMode to VerifyPeer only checks that there is a valid certificate chain (how should OpenSSL know about the correct hostname? It is not passed as an argument to contextSetVerificationMode.).
Hostname validation has to be enabled in addition to this, either manually or with the "new" functions added in OpenSSL 1.1.0 and 1.0.2, which I recently added to HsOpenSSL: enableHostnameValidation and vshabanov/HsOpenSSL#52, see https://wiki.openssl.org/index.php/Hostname_validation.

authors: amesgen redneb


text:
Added screenshots for some examples

Context:
Adds screenshots of examples.
I didn't manage to get the same window theme as seen in the calculator.
I took the pictures on win 10, I hope it's fine (at least it proves the lib is cross-platform :)
Fixes #318

Thank you. I think the basic ideas was to embed the images like the screenshot on the README. Would be nice if you can adjust it.

Images looks very very strange because there is not new line before and they seems to be aligned randomly

Yes, I see now.
I have checked the result in Visual Studio with a markdown plugin.
Seems like GitHub and the plugin render the markdown test differently.

authors: FloVanGH kivimango qarmin

repo: redox-os/orbtk


text:
[Bug] ...

Platform

Device: Phone, Laptop, Desktop, TV... windows 10 edge browser
OS: Windows, Android, iOS...
Browser: Chrome, Safari, Kiwi...
Browser Version:
Better xCloud Version:

Describe the bug
...doesnt work on gta oline, it says the session has expired
Screenshots/Videos
If applicable, add screenshots/videos to help explain your problem.

Report it to xCloud

authors: Nachhito redphx

repo: redphx/better-xcloud


text:
module is not defined

When building with webpack 5, this line gives a ReferenceError for module: https://github.com/erikras/redux-form/blob/f209539ea65e1b46534e701c635df31c100c3259/src/util/isHotReloading.js#L3
I'm not sure how to fix this, normally I would just put a if (typeof module === 'undefined') return false above that line, but after the webpack build it just gets transformed into if (false) {} so maybe this is a webpack 5 bug.

Update: Simply removing the castModule and using module directly makes it work properly. So it's a matter of the TypeScript workaround making it not work with Webpack 5.

Another fix is prefixing module with globalThis. I don't know Flow enough to create a merge request that passes the type system. But using patch-package I could simply change this line to get my app working with Vite.
 var castModule = globalThis.module

Another way I got it working was to define
module: undefined

in vite.config. However this might cause side-effects.

authors: sbaechler wmertens

repo: redux-form/redux-form


text:
Export all flow type aliases from root

We need to be able to use all of them in userland, absolutely any type alias declared anywhere in the flow type defs.  Making wrapper components is a huge hassle without these, because it's difficult to type props for our wrapper components.
import type { FieldInputProps, FieldArrayInputProps, Validator /* etc */ } from 'redux-form'

I'll try to make a PR for this soon