text:
13.6update

hey bro, the client is now 13.6, can you please update it? @hotline1337  @cjd0901

This software does not need to be updated with the game version.


text:
error plz help me

it happende when i open the R3nzSkin.dll

not related to the project.

source: gharchive/issue

license: MIT

license_type: permissive

license_source: github-api


text:
Investigate logged NPE during normal test run

https://travis-ci.org/RBMHTechnology/eventuate/builds/99603209#L1649

Seen again at https://travis-ci.org/RBMHTechnology/eventuate/builds/100780601#L1635

repo: RBMHTechnology/eventuate

license_source: bigquery


text:
[ Feature ] Create .txt files and images in a folder from custom data

Generating .txt files and images in a folder could be useful for some other purposes (like getting the standing of all the teams we entered to use them to generate/create a custom scene for an overall standing across a season or a tourney, for example.
Describe the solution you'd like
All the data/infos we enter in Teams, for example (team names, standing, coach, tag, etc., could be generated in differents text file (blueteamname.txt, blueteamstanding.txt, redteamscore.txt. etc) or in a folder with the team name (ex: T1 folder, having a name.txt, logo.png, standing.txt. etc) to be used more simply for other purpose without the need to double write them in custom scenes or other places in the broadcast.

I dunno if this is hard to implement, or a dumb suggestion. I've been using text files for many prods and differents needs and it always worked for me so...

The data entered in the teams module is saved to a "database" (which is just a .json file).
You can take a look at the data in ...\prod-toolkit\modules\plugin-database\data\league-prod-toolkit.json.
Is this already fit for your purpose? Or how would you be looking to access/use the text files?

I was looking to use the txt files for some custom purpose here and there, but yeah I already found the .json files with the data. Sadly it not usable as it is for my purpose. One example in my mind would be to use thoses .txt files in OBS to attach or read individual information to display them. (Read text files option from OBS). This is only an example about what I could use, sonce in my prod I have many other scenes (like schedule, records, all the teams in the league, etc.) I could enter them manually in my other scenes or graphics, but it just double my work since I already write them in the prod-tool-kit.

Could further elaborate on what you have in mind maybe with some simple graphics? so we might look to implement them directly, or if exposing data is the better option.

Well, for some people, using text files is simplier for broadcasting games or showing information on stream. For example, what if I need to show a team name on screen? I need to have it ready somewhere.

This is an example of using text files in a scene/layout in OBS. Information's need to be updated manually every time I change them. Some of theses informations are the same as in the toolkit (such as team names, score, standing, logo, etc.) It can save time and make it easier if the toolkit ALSO generate text files individually for each information so we can get them by reading the content of the text files. (easier for the prod to manage all the updated infos for the stream.
We could generate text files for the current blue team (name, logo, score, tag, coach, etc), current red team (same), the current round (Finals, Grand Finals, Round of 8, round of 16, etc), casters (full name, nickname, twitter, twitch, etc) and go on. Many softwares for streaming generate text files like this (example: for a recent donation, top donor, recent subs, etc)
It's an option to help people not familiar with CSS, HTML and JS to still use your tool, but still give flexibility to how to use the inputs and data generated from the toolkit (and maybe later go further and extract live stats, live current gold from each team, number of plating, drakes, experience, damage dealt etc. but this is for another project/later if we get there with the toolkit). I mostly ask this for the input we already add ourselves, so we only need to edit them in one place.
I dunno if it's clear or not XD Maybe it's harder to do than I think too. I was just an idea to add to the versatility of the toolkit.

Since we want to maintain central theming and be able to operate the toolkit 100% remotely, .txt files aren't necessarily the path we want to follow.
We plan to provide a series of additional browser sources that only display text based on information in the database:

Pages showing currently set blue/red teams in multiple formats (full name, team tag, logo, game score, standing etc.)
Pages showing the same infos for each team saved in the database
Pages showing infos for casters saved in the database

This way should allow for the same custom screens you already use, which automatically updates whenever something is changed in the teams module. Additionally, this maintains central theming, so text colors & fonts don't have to be set individually.
As a bonus, providing pages with these text variants also would allow for a small script to create text files if that is still desired :)
This shouldn't be a huge pain to implement, but won't be our highest priority at the moment.

repo: RCVolus/league-prod-toolkit


text:
add prez ontology annotations.

and update test data to reflect the new labels.

LGTM?

Looks good to me - sorry!

source: gharchive/pull-request

repo: RDFLib/prez


text:
Break sentences over 512 tokens into smaller chunks

This addresses DUG-459 (https://renci.atlassian.net/browse/DUG-459) where input text that tokenizes to sentences longer than 512 tokens overloads the model.
To fix this, if a sentence is over window_size tokens (usually 512), it is first split by semi-colon, and if that still results in oversized sentences, it is split again by tokens and then broken into roughly equal sized chunks that will fit inside the window.
A caveat with this: at present this final split first breaks the segment into tokens using text_to_tokens, and then re-assembles it in chunks of an appropriate size using tokens_to_text. This may add or remove spaces as the processes of splitting and then re-joining tokens are not perfect inverses of each other.

A rough version of this code is in testing here: https://nemo-jupyter.apps.renci.org/notebooks/notebooks/test_sliding_window_with_stack.ipynb

Hi Michael thanks this all works well but one slight issue is i think once the annotations are done when i re-constructs the final object to return it does return spans like
{
      "id": "I17-26",
      "span": {
        "begin": 7625,
        "end": 7633
      },
      "obj": "biolink:Cohort",
      "text": "children"
    },

And i believe some of the spans are a little offset

tool used to verify (https://textae.pubannotation.org/editor.html?mode=edit)

I believe the latest commit addresses these problems.

Most recent update should at least fix any problems with whitespace disappearance or token orphaning. (Which looks like ## appearing at the beginning of word fragments). Hopefully this actually gets us over the line.

authors: YaphetKG mbacon-renci

repo: RENCI-NER/nemo-serve


text:
DBAAS-104: add webhook validation for instance ID & InventoryRef on DBaaSConnectionSpec to immutable

Description

Add webhook validation for instance ID & InventoryRef on DBaaSConnectionSpec to immutable
Jira: https://issues.redhat.com/browse/DBAAS-104
Verification Steps

Type of change

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

Checklist (Definition of Done)

[ ] All acceptance criteria specified in JIRA or in issue number have been completed
[ ] Unit tests added that prove the fix is effective or the feature works
[ ] Documentation added for the feature
[ ] all relevant tests are passing
[ ] Code Review completed
[ ] Verified independently by reviewer

Need rebase on https://github.com/RHEcosystemAppEng/dbaas-operator/pull/18

Need rebase on #18

I'm ready to roll with this when you are @xieshenzh. Looks like there's a conflict after yesterday's PR, but LMK when you're ready and I'll get us merged up.

@jeremyary I have rebased the branch, it is ready to merge. Thanks.

authors: jeremyary xieshenzh

repo: RHEcosystemAppEng/dbaas-operator


text:
🛑 Activated Male is down

In ff5ce38, Activated Male (http://activatedmale.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Activated Male is back up in 408e713 after 11 minutes.

repo: RJVCA/uptime


text:
Added support for receiving and responding to lobby invites

This commit also fixes a bug that was present in the cache destroy function

Cool beans

authors: Crazy-Duck jimmydorry

license: mit


text:
Fix bug with cache unsubscribe

Small bug on my part. Should be owner_soid.

Also fix cache subscriptions with no owner_soid

Merged and published to npm with v0.7.1


text:
🛑 Sensor Tracker login is down

In c7ca65c, Sensor Tracker login (https://stg.ceotr.ca/sensor_tracker) was down:

HTTP code: 502
Response time: 43 ms

Resolved: Sensor tracker login is back up in 6daa377.

repo: RKTowse/upptime


text:
🛑 CEOTR Home Page loads is down

In b4af58c, CEOTR Home Page loads (https://stg.ceotr.ca CEOTR Home) was down:

HTTP code: 0
Response time: 0 ms

Resolved: CEOTR Home Page loads is back up in 12a24b1 after 2 minutes.


text:
🛑 Sensor Tracker login is down

In 111f273, Sensor Tracker login (https://stg.ceotr.ca/sensor_tracker) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Sensor tracker login is back up in 6aa7180 after 1 minute.


text:
🛑 Sensor Tracker login is down

In 713f16b, Sensor Tracker login (https://stg.ceotr.ca/sensor_tracker) was down:

HTTP code: 502
Response time: 94 ms

Resolved: Sensor tracker login is back up in 09f7270.


text:
🛑 Sensor Tracker login is down

In f5c66bf, Sensor Tracker login (https://stg.ceotr.ca/sensor_tracker) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Sensor tracker login is back up in d9c6af3 after 1 minute.


text:
🛑 Sensor Tracker login is down

In 9f7e5ac, Sensor Tracker login (https://stg.ceotr.ca/sensor_tracker) was down:

HTTP code: 502
Response time: 102 ms

Resolved: Sensor tracker login is back up in 292cd69.


text:
🛑 CEOTR Home Page loads is down

In 6985308, CEOTR Home Page loads (https://stg.ceotr.ca CEOTR Home) was down:

HTTP code: 0
Response time: 0 ms

Resolved: CEOTR Home Page loads is back up in ac4bd5e after 2 minutes.


text:
🛑 CEOTR Home Page loads is down

In bca2920, CEOTR Home Page loads (https://stg.ceotr.ca CEOTR Home) was down:

HTTP code: 0
Response time: 0 ms

Resolved: CEOTR Home Page loads is back up in 6d593f9 after 2 minutes.


text:
🛑 Sensor Tracker login is down

In d8d859e, Sensor Tracker login (https://stg.ceotr.ca/sensor_tracker) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Sensor tracker login is back up in ab7c973 after 1 minute.


text:
🛑 CEOTR Home Page loads is down

In dceea1d, CEOTR Home Page loads (https://stg.ceotr.ca CEOTR Home) was down:

HTTP code: 0
Response time: 0 ms

Resolved: CEOTR Home Page loads is back up in 6d8096d after 2 minutes.


text:
🛑 Sensor Tracker login is down

In 3c77114, Sensor Tracker login (https://stg.ceotr.ca/sensor_tracker) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Sensor tracker login is back up in 7aa18cf after .


text:
🛑 Sensor Tracker login is down

In 122b29d, Sensor Tracker login (https://stg.ceotr.ca/sensor_tracker) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Sensor tracker login is back up in 60324c6 after .


text:
🛑 Sensor Tracker login is down

In c7ff813, Sensor Tracker login (https://stg.ceotr.ca/sensor_tracker) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Sensor tracker login is back up in 4b3cb50 after .


text:
🛑 CEOTR Home Page loads is down

In 5a0651a, CEOTR Home Page loads (https://stg.ceotr.ca CEOTR Home) was down:

HTTP code: 0
Response time: 0 ms

Resolved: CEOTR Home Page loads is back up in 63b4362 after 2 minutes.


text:
🛑 CEOTR Home Page loads is down

In 928201b, CEOTR Home Page loads (https://stg.ceotr.ca CEOTR Home) was down:

HTTP code: 0
Response time: 0 ms

Resolved: CEOTR Home Page loads is back up in d3a5fbf after 35 days, 21 hours, 44 minutes.


text:
🛑 CEOTR Home Page loads is down

In b5d17ca, CEOTR Home Page loads (https://stg.ceotr.ca CEOTR Home) was down:

HTTP code: 0
Response time: 0 ms

Resolved: CEOTR Home Page loads is back up in c3eaf27 after 2 minutes.


text:
about 《FEND: A Future Enhanced Distribution-Aware Contrastive Learning Framework for Long-tail Trajectory Prediction》code

Dear author,
Hello, you gave to ‘’FEND: A Future Enhanced Distribution-Aware Contrastive Learning Framework for Long-tail Trajectory Prediction "code links to the code of other articles, Please check whether the link is incorrect

Hi,
I am the owner of that paper-list repo, sorry I put the wrong link. I already corrected it! I appreciate your interest in the repo.
Best,
Yi


text:
[Documentation]: Precision support - Libraries input/output type support

Description of errors
The support matrix discussed below needs to provide information on all ROCm libraries, not just the six provided.
Currently the documentation for precision support (here) aims to provide an overview for supported and unsupported precisions (e.g., float16) across various ROCm libraries. However, only 3 roc + 3 hip libraries are provided. This is a tiny amount of the actual number of ROCm libaries (here); particularly, the Math libraries, which are arguably some of the most relevant for non-standard precisions, are severely lacking in the supported/unsupported matrix.
Also, the libraries hipRAND and hipCUB have implied hyperlinks in the form of "(details)", but these are just text and do not link to anything.
Attach any links, screenshots, or additional evidence you think will be helpful.
No response

Hi @garrettbyrd, an internal ticket has been created to update/fix the documentation. Thanks!

@garrettbyrd, quick update on this issue. The hyperlinks for both hipRAND and hipCUB have been fixed and now link to the correct pages. We are also working on extending the list to cover more libraries, including the missing Math libraries. These changes will be live in an upcoming ROCm release.

authors: garrettbyrd harkgill-amd

repo: ROCm/ROCm


text:
Fix scipy signal tests for ROCm (SWDEV-446431)

This PR resolves https://ontrack-internal.amd.com/browse/SWDEV-446431

Passing logs:
signal_tests_w_fixes.log

repo: ROCm/cupy


text:
3D forward convolution solver with non-packed input tensors

Enable 3D forward convolution solver with non-packed input tensors using CK kernels.
The "make check" tests passed on mi200 development machine.
PR current blocked by MIOpen CI because of the "clinfo" issue.

@iq136boy please resolve the conflict by merging the latest develop into your feature branch. Thanks!

@iq136boy please resolve the conflict by merging the latest develop into your feature branch. Thanks!

@junliume conflict resolved.

It looks good, but it seems it has #2394 and #2334 included. Should it be merged sequentially?

It looks good, but it seems it has #2394 and #2334 included. Should it be merged sequentially?

Not necessarily. I have merged PR #2334. So this PR can be merged before #2334 if it pass the MIOpen CI.

@CAHEK7 @averinevg @DrizztDoUrden @atamazov @JehandadKhan @amberhassaan  :
CI has passed, last call for any blocking reviews before merging.

@junliume Please merge this PR before #2394.

@junliume Please merge this PR before #2394.

@iq136boy : that's the wrong order of merging. This PR was based on top of #2394, so we merge #2394 first and then this.

@junliume Please merge this PR before #2394.

@iq136boy : that's the wrong order of merging. This PR was based on top of #2394, so we merge #2394 first and then this.

@amberhassaan Yes. If we have enough time, the order should be #2394 first and then this one. But this PR is a p1 gating issue for rocm6.0 and today is the last day of branching date if I am correct. And the content of this PR should go in mainline. What I suggest and am doing now is that I create a backup PR that merge latest #2394 content into this PR and let that PR run through MIOpen CI separate. If that PR run through the CI without any issue, then we can merge 2394 first. Otherwise, I still suggest that this PR should be merged first to unblock the mainline gating status.
@junliume @JehandadKhan what do you think?

@atamazov Yes. The procedure that you mentioned is correct if we do not have a urgent hard deadline today. However, the MIOpen CI issue blocks the PR and caused some delay. So I proposed a solution here. Generally, I would like to merge 2394 into this PR and let it run through MIOpen CI. If something happened, then this PR should be a backup plan to unblock the rocm6.0 p1 gating.

@junliume @amberhassaan Well, it seems there is NO conflict between this PR and #2394. I merged #2394 with this PR and there is NO merge conflict. Also, I tested it on MI200 machine development machine locally and all tests passed. So we are good to merge the two PRs no matter the orders.

@iq136boy I understand your motives. However, I advise to never cut corners unless there is an explicit and specific request from management. From personal experience, I see that cutting corners to save time often leads to problems that then require more time, efforts, and stress to resolve than doing things the right way. 🤝

repo: ROCmSoftwarePlatform/MIOpen


text:
generate large 1D pow2, first version

generate large 1D kernels of pow2 from 8K to 64K (but the CPU calling part need to update, too)
add blockCompute feature in generator
modify offsetCalcBlock to make stride as a runtime parameter of kernels
remove stride check in generator, as stride is passed as an run-time variable of kernels
this pull request does not change small 1D (<= 4K) kernels.

need add device function TW3step in common.h, TW3step is used in large 1D.  Otherwise, "error: use of undeclared identifier 'TW3step'"

repo: ROCmSoftwarePlatform/rocFFT


text:
Evil Bob random event water is black

Describe the bug
The water in the Evil Bob fishing random event is black instead of blue. There is some texture in the black. Hard to see fishing spots.
To Reproduce
Steps to reproduce the behavior:

Go to Evil Bob fishing random event
Enable 117 HD plugin

Expected behavior
Water in Evil Bob random event should be blue like the rest of the game.
Screenshots

Environment (please complete the following information):

OS: Microsoft Windows 10 Home Version	10.0.19043 Build 19043
RuneLite version: 1.7.24

Additional context
client.log
Tried toggling plugin settings but could not find the culprit. Only fix was to turn the plugin off.

This can now be called as it was added


text:
Hey Does someone have this  "Pinterest error: bad status code 400 received " PLEASE HELP

Describe the bug
This the screenshot of the problem

Please Help me if you have the solution Thanks

Duplicate of #1368

authors: mahdiipin teromene

repo: RSS-Bridge/rss-bridge

license: unlicense


text:
Youtube: the videos.xml endpoint occasionally returns 404

It seems that Google broke or removed the endpoint that RSS Bridge uses. I get 404 both locally and on my server

They still have proper links in the head so there is still hope it's a broken release
<link rel="alternate" type="application/rss+xml" title="RSS" href="https://www.youtube.com/feeds/videos.xml?channel_id=...">

Ping @mitsukarenai as maintainer of this bridge. Please leave note, if you don't have time to maintain it.

Ping @mitsukarenai as maintainer of this bridge. Please leave note, if you don't have time to maintain it.

Btw, there is also another bug over there https://github.com/RSS-Bridge/rss-bridge/issues/1875
I forgot to ping you on that thread

Same here, even though on Youtube side, things seems to be operational
https://www.youtube.com/feeds/videos.xml?channel_id=UCcVSSE0tadIdtvtFQqm3M-g

@rmdes Probably they are rolling out the fix and some nodes have not been updated yet. That or you should clean cache on your instance of the bridge
Things seem starting to work for me. If nothing gets broken again in a day I will close this

Hi, on my side, my YouTube feeds are also working. Maybe something was temporarily broken at YouTube, or you IP got blacklisted.

Cleaned the cache, now it works with using channel ID : UCcVSSE0tadIdtvtFQqm3M-g
Thanks (forgot about the cache)

Ping @mitsukarenai as maintainer of this bridge. Please leave note, if you don't have time to maintain it.

That is correct, sorry I won't have the time and resources to maintain the bridge 🙁

Closing as false alert

Looks like return 404 again.

False alert again. I will leave issue open, 'cos we need to run fallback on 404.

Hi, I can confirm that my feeds are also still working but temporarily had this error due to API giving 404.

I don't know for you, but since september, I'm getting 404 errors when trying to fetch channel videos from https://www.youtube.com/feeds/videos.xml?channel_id=UCK4PgggS7ClfRwVkLIrcruw

Seems like those problems are known at scale https://www.reddit.com/r/rss/comments/nbznqx/youtube_rss_feeds_down/ but they always have seemed to be temporary https://www.reddit.com/r/rss/comments/pucaqc/youtube_stopped_supporting_rss_feeds_this_very/

@Riduidel "This account has been terminated because we received multiple third-party claims of copyright infringement regarding material that the user posted." Your case is an honest 404

Removed the sense of emergency from the title. So, should it be handled gracefully or what? I think it can be safely closed again

It should be handled. I will fix it, when I have time

one option is to not fail on 404. but that would make it hard to know whether the inputted channel name is wrong :p

authors: ORelio Riduidel arokettu dvikan em92 mitsukarenai rmdes


text:
XML parsing error: :668:138: not well-formed (invalid token)

I once in a while get a bug in my MarktplaatsBridge feed, where if I run it through a validator it says a line isn't well formed. (It also causes issues in TT-RSS)
I think it's caused by certain special characters, but don't know how to solve it.
The line it breaks on is this:
Zeer mooie gibson sg uit een goede periode, namelijk de 90's (januari 1990 om precies te zijn) een 'golden age' en

I think at the end it should be
 instead.
This is the line from the JSON of the API it generates the feed from:
"description": "Zeer mooie gibson sg uit een goede periode, namelijk de 90's (januari 1990 om precies te zijn) een 'golden age' en \u0003"

What is feed url, that generates those invalid chars?

What is feed url, that generates those invalid chars?

Sorry for the late reply.
The URL: http://rss-aggregator-mp.000webhostapp.com/?action=display&bridge=MarktplaatsGitaar&context=Search&format=Atom
It doesn't happen often though.

Still occuring once in a while. Here's a picture of the error:

What is feed url, that generates those invalid chars?

Sorry for the late reply. The URL: http://rss-aggregator-mp.000webhostapp.com/?action=display&bridge=MarktplaatsGitaar&context=Search&format=Atom
It doesn't happen often though.
The bridge was edited but only to add some parameters to the URL that it's requesting the data from.

I forgot to add: the unedited bridge gives the same error when it returns the same result.

Please give the form values that produces this result.

i believe this is non-valid utf8 data

authors: Pizzabroodje dvikan em92


text:
[core] Added IGNORE_CUSTOM_CACHE_TIMEOUT option

Explaining my usecase. For some reason I enabled custom_timeout in my config, but forgot to disable it back. Meanwhile some users already generated feed urls with _cache_timeout parameters. So if I disable custom_timeout back, those feed urls become invalid, which is not good.
So, I added option to ignore _cache_timeout param in url.

Thanks for the PR :+1:

So if I disable custom_timeout back, those feed urls become invalid, which is not good.

I agree, this is a server-side issue.

So, I added option to ignore _cache_timeout param in url.

This doesn't feel right to me and is confusing to new users. Users might also question if the parameter is even applied in their specific situation, which adds a layer of uncertainty.
An alternative to this is replying with the "301 Moved Permanently" header. Feed readers and browsers will automatically follow the location provided in the header. Here is some code for reference:
header('Location: index.php?action=...', true, 301);

Would that work for you?

Almost. Maybe I should have explained myself better.
You can remove ignore_custom_timeout entirely and just assume, that custom_timeout = false implies ignore_custom_timeout = true. That way, you only need to replace this line:
https://github.com/RSS-Bridge/rss-bridge/blob/78c69b08f0f544e0eb0caa16ae94771eabd33764/index.php#L129
by this:
unset($params['_cache_timeout']);
header('Location: ' . parse_url($_SERVER['REQUEST_URI'], PHP_URL_PATH) . '?' . http_build_query($params), true, 301);
die();

So, if custom_timeout = true, everything works fine.
If custom_timeout = false, everyone gets redirected.

Merged. Thanks for keeping it updated! :+1:


text:
Question: Why do you load xml files as tsx?

why not keep as xml OR provide a tool to convert to ts ?

Hello,
I don't really understand your question
On version 4, TMX/TSX files are loaded as XML.

authors: RSamaium jonniedarko

repo: RSamaium/RPG-JS


text:
Fix stackoverflow in GetEnumerableItemType

Fixes issue https://github.com/RSuter/NJsonSchema/issues/842
I simply adds a check in GetEnumerableItemType when going through the interface of a type to only consider the one that implement IEnumerable.

Thanks for the PR. I've added a test. Release (+ NSwag) soon.

v9.13.3

authors: RSuter tlg-bf

repo: RSuter/NJsonSchema


text:
Update semantic-ui to 2.4.2

closes https://github.com/RTLCSS/cdn/issues/1

@MohammadYounes can you review?

@felixmosh I wasn't able to build this branch, initially it's missing src/_site ... also 2.4.2 isn't released yet, the latest release as of now is 2.4.1 (a753d5b7841ab6adbe6d8a3b40086b452f0ba715).

authors: MohammadYounes felixmosh

repo: RTLCSS/Semantic-UI


text:
🛑 VIKA (.dev) is down

In aedb651, VIKA (.dev) (https://vika.rtuitlab.dev/api/about/vkgroupid) was down:

HTTP code: 0
Response time: 0 ms

Resolved: VIKA (.dev) is back up in c375173.

repo: RTUITLab/upptime


text:
Line Ending Problem Unix/DOS

I encountered the error first while I was building OpenRAM. If I run make pdk command in OpenRAM repo following error shows up.
...
make SHARED_PDKS_PATH=/pdk install"
sh: ./configure: /bin/bash^M: bad interpreter: No such file or directory

A WIndows-style line ending https://github.com/RTimothyEdwards/open_pdks/blob/d6c91b48a57fbe36eab06905211412327b0406dc/scripts/configure#L1  causes it. I can bypass it by running dos2unix over the open_pdks repo. But, then I have to follow make file instructions manually since specific commits are pulled and verified, which conflicts with the recent changes (dos2unix).
This is not a critical bug. Since the solution is obvious. But, I have encountered it on both Ubuntu 20.04 LTS, Ubuntu Server 22.04 LTS, and Ubuntu on WSL2. So, fixing it would be a mild convenience for the users.

I have no idea what you're seeing.  The line you're pointing to does not contain a DOS-style ending and does not match the reported error (which is on /bin/bash, not /bin/sh).  I don't use Windows, so I'm mystified.

TLDR: git automatically converts line endings if autocrlf = true is set in preferences. That was the case for me. I fixed it. All good.

The line you're pointing to does not contain a DOS-style ending

This is what lead me to find the problem. Running cat -e * was showing Windows line endings (^M$). How could two people see different line endings? -> Git can change the line endings.

and does not match the reported error (which is on /bin/bash, not /bin/sh). I don't use Windows, so I'm mystified.

I have changed it to bash and deleted the space between #! and /b... just to try. I apologize for not reverting it back before opening an issue.
I have set the git preferences correctly. Everything works now.
[core]
	autocrlf = false
	eol = lf

Always good to have a record of obscure problems!

authors: RTimothyEdwards hakan-demirli


text:
Show saved Time Spent Entries, for the current date

The default load should show the previously saved time entries.
Save data should get populated after saving new entries(after UPDATE)

This is now covered through the Weekly view card. so closing this.

repo: Raathigesh/Lazymine


text:
Fix typo

Avilable -> Available

Thank you 👍

authors: Raathigesh dextermb

repo: Raathigesh/retoggle


text:
fix workflows 2.0 test dependencies

Fix dependencies in the 2.0 workflows tests.  Also change the mock data values so the 1.1 tests do not affect the 2.0 tests.
This change will allow the 2.0 workflow tests to be successfully run independent of the 1.1 workflow tests.

@abildw @dalebremner @srinia6 @brianparry

+1

:+1:

+1

authors: abildw dalebremner geoff-reid yyscamper

repo: RackHD/RackHD


text:
esx-ks reboot delay fix for 5.5 support

Adjusted this value since it wasn't valid and causes the first boot config not to take place unless another reboot is manually applied.
Here is an error if you manually try to run the old command on 5.5
esxcli system shutdown reboot -d 5 -r "Rebooting after first boot host configuration"
Invalid data constraint for parameter 'delay'. Expected integer in the range 10-4294967295

:+1:

:+1:

:+1:

authors: benbp king-jam yyscamper zyoung51

repo: RackHD/on-http


text:
Windows os regression script enhancement

disable firewall to be able to test link after the static IP is assigned to the node as part of max payload

BUILD on-http #2793 : FAILURE

** BUILD build-config-setup  #145646: SUCCESS
** BUILD unit-tests  #9998: SUCCESS
** BUILD smoke-test  #3727: FAILURE


text:
R390 clinfo fails with dmesg failed to register MMU notifier

uname -a
Linux xfer 5.3.4 #1 SMP Sat Oct 5 22:39:14 CEST 2019 x86_64 GNU/Linux

grep HSA /boot/config-5.3.4
CONFIG_HSA_AMD=y

sudo lsmod | grep amdgpu
amdgpu               4677632  3
gpu_sched              36864  1 amdgpu
i2c_algo_bit           16384  1 amdgpu
ttm                   118784  1 amdgpu
drm_kms_helper        212992  1 amdgpu
drm                   548864  7 gpu_sched,drm_kms_helper,amdgpu,ttm
mfd_core               16384  2 lpc_ich,amdgpu

rocm-smi

========================ROCm System Management Interface========================
================================================================================
GPU  Temp   AvgPwr   SCLK    MCLK    Fan     Perf  PwrCap  VRAM%  GPU%
0    35.0c  15.201W  300Mhz  150Mhz  26.67%  auto  208.0W    0%   0%
1    30.0c  17.001W  300Mhz  150Mhz  26.67%  auto  208.0W    0%   0%
================================================================================
==============================End of ROCm SMI Log ==============================

I understand that atomics blocks the use of HCC, I dont' see why this extends to openCL tho
Please advise.
rocm-smi shows the GPUs correctly.

sudo dmesg | grep kfd
[sudo] password for philix:
[    6.291801] kfd kfd: Allocated 3969056 bytes on gart
[    6.293305] kfd kfd: added device 1002:67b1
[    6.713104] kfd kfd: Allocated 3969056 bytes on gart
[    6.713317] kfd kfd: added device 1002:67b1
[  392.761278] kfd2kgd: init_user_pages: Failed to register MMU notifier: -19
[  392.761290] kfd2kgd: init_user_pages: Failed to register MMU notifier: -19
[  392.761297] kfd2kgd: init_user_pages: Failed to register MMU notifier: -19
[  392.761304] kfd2kgd: init_user_pages: Failed to register MMU notifier: -19

R9 390 (Hawaii) has been broken since December. AMD refuse to recognize this and update the readme to show that it is broken. See this issue, you're not the only one. Solution is to use AMDGPU-PRO for OpenCL.
The problem is in the driver that is why OpenCL also fails. AMDGPU-PRO works fine for OpenCL.

I'm also seeing those dmesg errors on Linux 5.3.6 with an RX 580 (no ROCm components work; rocminfo bails out with an error at line 1102 of rocminfo.cc).
All is fine with Kernels 5.2.x.

I was able to resolve this for myself by changing my kernel config to add:
CONFIG_ZONE_DEVICE=y
CONFIG_HMM_MIRROR=y
CONFIG_DRM_AMDGPU_USERPTR=y

thanks @acowley I will try that

Hi All,
Hawaii is no more officially ROCm supported device. Please check for more details:
https://github.com/RadeonOpenCompute/ROCm#hardware-and-software-support
Thank you.

Hi All,
Hawaii is no more officially ROCm supported device. Please check for more details:
https://github.com/RadeonOpenCompute/ROCm#hardware-and-software-support
Thank you.

authors: Dekken JMadgwick PhilipDeegan ROCmSupport acowley

repo: RadeonOpenCompute/ROCm


text:
Announcements Template

Trying out the look for making announcements in a manner separate to the release notes where we can go deeper into a topic.

#2428 will implement this


text:
Vertical Scroll on Insider Mobile

I am on iOS and using the latest insider build. I am unable to swipe with my finger to scroll down and see cells that are not above the page fold.

Looks like if I rotate my device landscape I can scroll vertically but when it is not in landscape is when the scroll is disabled. Is this desired behavior?

I will test the problem with this issue https://github.com/RafaelGB/obsidian-db-folder/issues/435 done because the scroll logic was changed for all the plugin.
Thanks for the report!

awesome, thanks! love this plugin, super useful.

https://user-images.githubusercontent.com/11924043/200116294-96222aa2-76b8-4787-af1a-37bd648276a1.mp4
looks like its fixed with the scroll update
Could you confirm it to close this issue?

authors: RafaelGB iangeckeler

repo: RafaelGB/obsidian-db-folder


text:
🛑 RSOS服务控制面板 is down

In 9b04e1c, RSOS服务控制面板 (https://$US_SITE) was down:

HTTP code: 530
Response time: 206 ms

Resolved: RSOS服务控制面板 is back up in a6b3550 after 14 minutes.

repo: RainThings/uptime


text:
🛑 HK区服 is down

In 58df6c9, HK区服 (https://$HK_SERVER) was down:

HTTP code: 0
Response time: 0 ms

Resolved: HK区服 is back up in 9dd5a35.


text:
Primitive column types will not respect default values

DBFlow Version: 3.1.1
Issue Kind (Bug, Question, Feature): Bug
Description:
Hey guys, what is Primitive column types will not respect default values means?
I get this in the logcat when I noticed not all of the property is generated by @Column annotation:
@Table(database = MyDatabase.class)
public class Group extends BaseModel {

    @Column
    @PrimaryKey(autoincrement = true)
    private long id;

    @Column
    private String uid;

    @Column
    private String name;

    @Column
    private boolean haveGroupImg;

    @Column
    private String desc;

    @Column(defaultValue = "0")
    private boolean onlineGroup;

    @Column(defaultValue = "1")
    private boolean currentStatus;

    @Column
    private long timestamp;

    @Column
    private String currentProgress;

    @Column
    private String totalProgress;

    @Column(defaultValue = "0")
    private boolean isMute;

    @Column(defaultValue = "0")
    private boolean isSynced;

    // getters setters
}

In my case, currentStatus isn't generated.
Any fix to this?

Solved it.
Found out that my getters and setters for boolean type isn't properly named.
getCurrentStatus() whilst the correct one is isCurrentStatus(). The latter works fine with @Column annotation.
Before closing this issue, may I know why it behaves like this?

add @Table(useBooleanGetterSetters = true)

authors: agrosner aimanbaharum

repo: Raizlabs/DBFlow


text:
New Deployment Type: AppveyorModule

It might be helpful to abstract out module deployments (or maybe more generic?) to AppVeyor.  This way, we could allow deployments of dev / latest builds to AppVeyor, similar the DSC resources and a few other Microsoft repos.
Not tied to the name or any specifics, just spitballing:
Deploy MyModuleToAppveyor {
    By AppveyorModule {
        FromSource MyModule
        Tagged Dev
    }
}

Borrowed from Microsoft and various contributors, initial completely untested work is in the appveyor_deployment branch.

Marked this as experimental, minimal manual testing performed.  See docs for details on using this.
Major thanks to whomever wrote and contributed to the underlying code for this that we borrowed from the DSC Resources!

repo: RamblingCookieMonster/PSDeploy


text:
CI envtest flake: Error reported is "failed waiting for an updated DRPC. State FailedOver"

Flake instance: https://github.com/RamenDR/ramen/actions/runs/4500398508/jobs/7919477941
Failure:

• Failure [10.040 seconds]
DRPlacementControl Reconciler
/home/runner/work/ramen/ramen/controllers/drplacementcontrol_controller_test.go:1646
DRPlacementControl Reconciler Async DR using PlacementRule (Subscription)
/home/runner/work/ramen/ramen/controllers/drplacementcontrol_controller_test.go:1650
when DRAction is Failover during hub recovery
/home/runner/work/ramen/ramen/controllers/drplacementcontrol_controller_test.go:1680
Should reconstructs the DRPC state and points to Secondary (West1ManagedCluster) [It]
/home/runner/work/ramen/ramen/controllers/drplacementcontrol_controller_test.go:1681
  Timed out after 10.000s.
  failed waiting for an updated DRPC. State FailedOver
  Expected
      <bool>: false
  to be true

  /home/runner/work/ramen/ramen/controllers/drplacementcontrol_controller_test.go:1161

More detailed logs:
•STEP:
*** Failover after
2023-03-23T12:16:22.327Z	INFO	controllers.DRPlacementControl	Getting user placement object	{"DRPC": "drpc-namespace/drpc-name", "rid": "378fc166-1ed6-4a86-a78f-4876bc15e0c7", "placementRef": {"name":"user-placement-rule"}}
2023-03-23T12:16:22.327Z	INFO	controllers.DRPlacementControl	Trying user PlacementRule	{"DRPC": "drpc-namespace/drpc-name", "rid": "378fc166-1ed6-4a86-a78f-4876bc15e0c7", "usrPR": "user-placement-rule/"}
2023-03-23T12:16:22.327Z	INFO	controllers.DRPlacementControl	User PlacementRule replica count is not set to 1, reconciliation will only schedule it to a single cluster	{"DRPC": "drpc-namespace/drpc-name", "rid": "378fc166-1ed6-4a86-a78f-4876bc15e0c7"}
2023-03-23T12:16:22.327Z	INFO	controllers.DRPlacementControl	PlacementRule Status is: ({Decisions:[]})	{"DRPC": "drpc-namespace/drpc-name", "rid": "378fc166-1ed6-4a86-a78f-4876bc15e0c7"}
2023-03-23T12:16:22.327Z	INFO	controllers.DRPlacementControl	Trying user Placement	{"DRPC": "drpc-namespace/drpc-name", "rid": "378fc166-1ed6-4a86-a78f-4876bc15e0c7", "usrP": "user-placement-rule/"}
2023-03-23T12:16:22.327Z	INFO	controllers.DRPlacementControl	Get Placement returned: Placement.cluster.open-cluster-management.io "user-placement-rule" not found	{"DRPC": "drpc-namespace/drpc-name", "rid": "378fc166-1ed6-4a86-a78f-4876bc15e0c7"}
2023-03-23T12:16:22.327Z	INFO	controllers.DRPlacementControl	Using placement &{{PlacementRule apps.open-cluster-management.io/v1} {user-placement-rule  drpc-namespace  413b45a9-2dc2-4cda-9ebd-327f06441355 354 1 2023-03-23 12:16:12 +0000 UTC   map[] map[drplacementcontrol.ramendr.openshift.io/drpc-name:drpc-name drplacementcontrol.ramendr.openshift.io/drpc-namespace:drpc-namespace] [] [drpc.ramendr.openshift.io/finalizer] [{controllers.test Update apps.open-cluster-management.io/v1 2023-03-23 12:16:12 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{".":{},"f:drplacementcontrol.ramendr.openshift.io/drpc-name":{},"f:drplacementcontrol.ramendr.openshift.io/drpc-namespace":{}},"f:finalizers":{".":{},"v:"drpc.ramendr.openshift.io/finalizer"":{}}},"f:spec":{".":{},"f:clusterSelector":{".":{},"f:matchExpressions":{}},"f:schedulerName":{}}} } {controllers.test Update apps.open-cluster-management.io/v1 2023-03-23 12:16:22 +0000 UTC FieldsV1 {"f:status":{}} status}]} {ramen  {[] &LabelSelector{MatchLabels:map[string]string{},MatchExpressions:[]LabelSelectorRequirement{LabelSelectorRequirement{Key:key1,Operator:In,Values:[west1],},},}} []  []} {[]}}	{"DRPC": "drpc-namespace/drpc-name", "rid": "378fc166-1ed6-4a86-a78f-4876bc15e0c7"}
2023-03-23T12:16:22.327Z	INFO	controllers.DRPlacementControl	Preferred cluster is configured. Dynamic selection is disabled	{"DRPC": "drpc-namespace/drpc-name", "rid": "378fc166-1ed6-4a86-a78f-4876bc15e0c7", "PreferredCluster": "east1-cluster"}
2023-03-23T12:16:22.327Z	INFO	controllers.DRPlacementControl	VRG not found on "east1-cluster"	{"DRPC": "drpc-namespace/drpc-name", "rid": "378fc166-1ed6-4a86-a78f-4876bc15e0c7"}
2023-03-23T12:16:22.327Z	INFO	controllers.DRPlacementControl	VRG location	{"DRPC": "drpc-namespace/drpc-name", "rid": "378fc166-1ed6-4a86-a78f-4876bc15e0c7", "VRG on": "west1-cluster"}
2023-03-23T12:16:22.330Z	INFO	controllers.DRPlacementControl	Starting to process placement	{"DRPC": "drpc-namespace/drpc-name", "rid": "378fc166-1ed6-4a86-a78f-4876bc15e0c7"}
2023-03-23T12:16:22.330Z	INFO	controllers.DRPlacementControl	Process DRPC Placement	{"DRPC": "drpc-namespace/drpc-name", "rid": "378fc166-1ed6-4a86-a78f-4876bc15e0c7", "DRAction": "Failover"}
2023-03-23T12:16:22.330Z	INFO	controllers.DRPlacementControl	Entering RunFailover	{"DRPC": "drpc-namespace/drpc-name", "rid": "378fc166-1ed6-4a86-a78f-4876bc15e0c7", "state": "FailedOver"}
2023-03-23T12:16:22.330Z	INFO	controllers.DRPlacementControl	Check placement if needs fixing: PrD {east1-cluster drpc-namespace}, PlD &{ PlacementRule decision}, VRGs 1	{"DRPC": "drpc-namespace/drpc-name", "rid": "378fc166-1ed6-4a86-a78f-4876bc15e0c7"}
2023-03-23T12:16:22.330Z	INFO	controllers.DRPlacementControl	Phase: Current 'FailedOver'. Next 'Initiating'	{"DRPC": "drpc-namespace/drpc-name", "rid": "378fc166-1ed6-4a86-a78f-4876bc15e0c7"}
2023-03-23T12:16:22.330Z	INFO	controllers.DRPlacementControl	Progression: Current 'Initiating'. Next ''	{"DRPC": "drpc-namespace/drpc-name", "rid": "378fc166-1ed6-4a86-a78f-4876bc15e0c7"}
2023-03-23T12:16:22.330Z	INFO	controllers.DRPlacementControl	Phase: Current 'Initiating'. Next 'FailingOver'	{"DRPC": "drpc-namespace/drpc-name", "rid": "378fc166-1ed6-4a86-a78f-4876bc15e0c7"}
2023-03-23T12:16:22.330Z	INFO	controllers.DRPlacementControl	Progression: Current 'FailingOver'. Next 'FailingOverToCluster'	{"DRPC": "drpc-namespace/drpc-name", "rid": "378fc166-1ed6-4a86-a78f-4876bc15e0c7"}
2023-03-23T12:16:22.330Z	INFO	controllers.DRPlacementControl	switchToCluster	{"DRPC": "drpc-namespace/drpc-name", "rid": "378fc166-1ed6-4a86-a78f-4876bc15e0c7", "cluster": "west1-cluster", "restorePVs": true}
2023-03-23T12:16:22.330Z	DEBUG	events	next state not known	{"type": "Warning", "object": {"kind":"DRPlacementControl","namespace":"drpc-namespace","name":"drpc-name","uid":"959f5fd0-0fed-46b8-8422-d6df449b69f0","apiVersion":"ramendr.openshift.io/v1alpha1","resourceVersion":"353"}, "reason": "unknown state"}
2023-03-23T12:16:22.330Z	DEBUG	events	Failing over the application and VRG	{"type": "Warning", "object": {"kind":"DRPlacementControl","namespace":"drpc-namespace","name":"drpc-name","uid":"959f5fd0-0fed-46b8-8422-d6df449b69f0","apiVersion":"ramendr.openshift.io/v1alpha1","resourceVersion":"353"}, "reason": "DRPCFailingOver"}
2023-03-23T12:16:22.330Z	INFO	controllers.DRPlacementControl	create or update VRG if it does not exists or is not primary	{"DRPC": "drpc-namespace/drpc-name", "rid": "378fc166-1ed6-4a86-a78f-4876bc15e0c7", "cluster": "west1-cluster"}
2023-03-23T12:16:22.331Z	INFO	controllers.DRPlacementControl	VRG MW already Primary on this cluster	{"DRPC": "drpc-namespace/drpc-name", "rid": "378fc166-1ed6-4a86-a78f-4876bc15e0c7", "name": "drpc-name", "cluster": "west1-cluster"}
2023-03-23T12:16:22.331Z	INFO	controllers.DRPlacementControl	Checking if PVs have been restored	{"DRPC": "drpc-namespace/drpc-name", "rid": "378fc166-1ed6-4a86-a78f-4876bc15e0c7", "cluster": "west1-cluster"}
2023-03-23T12:16:22.331Z	INFO	controllers.DRPlacementControl	PVs Restored? true	{"DRPC": "drpc-namespace/drpc-name", "rid": "378fc166-1ed6-4a86-a78f-4876bc15e0c7"}
2023-03-23T12:16:22.331Z	INFO	controllers.DRPlacementControl	Updating user Placement user-placement-rule homeCluster west1-cluster	{"DRPC": "drpc-namespace/drpc-name", "rid": "378fc166-1ed6-4a86-a78f-4876bc15e0c7"}
2023-03-23T12:16:22.335Z	INFO	controllers.DRPlacementControl	Updated user PlacementRule status	{"Decisions": [{"clusterName":"west1-cluster","clusterNamespace":"west1-cluster"}]}
2023-03-23T12:16:22.335Z	INFO	controllers.DRPlacementControl	Progression: Current 'FailingOver'. Next 'UpdatedPlacement'	{"DRPC": "drpc-namespace/drpc-name", "rid": "378fc166-1ed6-4a86-a78f-4876bc15e0c7"}
2023-03-23T12:16:22.335Z	INFO	controllers.DRPlacementControl	Phase: Current 'FailingOver'. Next 'FailedOver'	{"DRPC": "drpc-namespace/drpc-name", "rid": "378fc166-1ed6-4a86-a78f-4876bc15e0c7"}
2023-03-23T12:16:22.335Z	INFO	controllers.DRPlacementControl	Failover completed	{"DRPC": "drpc-namespace/drpc-name", "rid": "378fc166-1ed6-4a86-a78f-4876bc15e0c7", "state": "FailedOver"}
2023-03-23T12:16:22.335Z	INFO	controllers.DRPlacementControl	Updating DRPC status	{"DRPC": "drpc-namespace/drpc-name", "rid": "378fc166-1ed6-4a86-a78f-4876bc15e0c7"}
2023-03-23T12:16:22.335Z	INFO	controllers.DRPlacementControl	Setting metric: (last_sync_timestamp_seconds)	{"DRPC": "drpc-namespace/drpc-name", "rid": "378fc166-1ed6-4a86-a78f-4876bc15e0c7"}
2023-03-23T12:16:22.335Z	DEBUG	events	Successfully failedover the application and VRG	{"type": "Normal", "object": {"kind":"DRPlacementControl","namespace":"drpc-namespace","name":"drpc-name","uid":"959f5fd0-0fed-46b8-8422-d6df449b69f0","apiVersion":"ramendr.openshift.io/v1alpha1","resourceVersion":"353"}, "reason": "DRPCFailoverSuccess"}
2023-03-23T12:16:22.343Z	ERROR	controllers.DRPlacementControl	failed to update status	{"DRPC": "drpc-namespace/drpc-name", "rid": "378fc166-1ed6-4a86-a78f-4876bc15e0c7", "error": "failed to update DRPC status: Operation cannot be fulfilled on drplacementcontrols.ramendr.openshift.io "drpc-name": the object has been modified; please apply your changes to the latest version and try again", "errorVerbose": "Operation cannot be fulfilled on drplacementcontrols.ramendr.openshift.io "drpc-name": the object has been modified; please apply your changes to the latest version and try again\nfailed to update DRPC status\ngithub.com/ramendr/ramen/controllers.(*DRPlacementControlReconciler).updateDRPCStatus\n\t/home/runner/work/ramen/ramen/controllers/drplacementcontrol_controller.go:1190\ngithub.com/ramendr/ramen/controllers.(*DRPCInstance).startProcessing\n\t/home/runner/work/ramen/ramen/controllers/drplacementcontrol.go:67\ngithub.com/ramendr/ramen/controllers.(*DRPlacementControlReconciler).reconcileDRPCInstance\n\t/home/runner/work/ramen/ramen/controllers/drplacementcontrol_controller.go:564\ngithub.com/ramendr/ramen/controllers.(*DRPlacementControlReconciler).Reconcile\n\t/home/runner/work/ramen/ramen/controllers/drplacementcontrol_controller.go:423\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Reconcile\n\t/home/runner/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.13.1/pkg/internal/controller/controller.go:121\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler\n\t/home/runner/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.13.1/pkg/internal/controller/controller.go:320\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem\n\t/home/runner/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.13.1/pkg/internal/controller/controller.go:273\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2\n\t/home/runner/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.13.1/pkg/internal/controller/controller.go:234\nruntime.goexit\n\t/opt/hostedtoolcache/go/1.18.10/x64/src/runtime/asm_amd64.s:1571"}
github.com/ramendr/ramen/controllers.(*DRPCInstance).startProcessing
/home/runner/work/ramen/ramen/controllers/drplacementcontrol.go:68
github.com/ramendr/ramen/controllers.(*DRPlacementControlReconciler).reconcileDRPCInstance
/home/runner/work/ramen/ramen/controllers/drplacementcontrol_controller.go:564
github.com/ramendr/ramen/controllers.(*DRPlacementControlReconciler).Reconcile
/home/runner/work/ramen/ramen/controllers/drplacementcontrol_controller.go:423
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Reconcile
/home/runner/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.13.1/pkg/internal/controller/controller.go:121
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler
/home/runner/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.13.1/pkg/internal/controller/controller.go:320
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem
/home/runner/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.13.1/pkg/internal/controller/controller.go:273
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2
/home/runner/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.13.1/pkg/internal/controller/controller.go:234
2023-03-23T12:16:22.343Z	INFO	controllers.DRPlacementControl	Finished processing	{"DRPC": "drpc-namespace/drpc-name", "rid": "378fc166-1ed6-4a86-a78f-4876bc15e0c7", "Requeue?": true}
2023-03-23T12:16:22.343Z	INFO	controllers.DRPlacementControl	Requeing...	{"DRPC": "drpc-namespace/drpc-name", "rid": "378fc166-1ed6-4a86-a78f-4876bc15e0c7"}
2023-03-23T12:16:22.343Z	INFO	controllers.DRPlacementControl	Exiting reconcile loop	{"DRPC": "drpc-namespace/drpc-name", "rid": "378fc166-1ed6-4a86-a78f-4876bc15e0c7"}
2023-03-23T12:16:22.343Z	INFO	controllers.DRPlacementControl	Entering reconcile loop	{"DRPC": "drpc-namespace/drpc-name", "rid": "60c37fb7-69cb-42fa-b57c-629c4bf4068e"}
2023-03-23T12:16:22.347Z	INFO	controllers.DRPlacementControl	Getting user placement object	{"DRPC": "drpc-namespace/drpc-name", "rid": "60c37fb7-69cb-42fa-b57c-629c4bf4068e", "placementRef": {"name":"user-placement-rule"}}
2023-03-23T12:16:22.347Z	INFO	controllers.DRPlacementControl	Trying user PlacementRule	{"DRPC": "drpc-namespace/drpc-name", "rid": "60c37fb7-69cb-42fa-b57c-629c4bf4068e", "usrPR": "user-placement-rule/"}
2023-03-23T12:16:22.347Z	INFO	controllers.DRPlacementControl	User PlacementRule replica count is not set to 1, reconciliation will only schedule it to a single cluster	{"DRPC": "drpc-namespace/drpc-name", "rid": "60c37fb7-69cb-42fa-b57c-629c4bf4068e"}
2023-03-23T12:16:22.347Z	INFO	controllers.DRPlacementControl	PlacementRule Status is: ({Decisions:[{ClusterName:west1-cluster ClusterNamespace:west1-cluster}]})	{"DRPC": "drpc-namespace/drpc-name", "rid": "60c37fb7-69cb-42fa-b57c-629c4bf4068e"}
2023-03-23T12:16:22.347Z	INFO	controllers.DRPlacementControl	Trying user Placement	{"DRPC": "drpc-namespace/drpc-name", "rid": "60c37fb7-69cb-42fa-b57c-629c4bf4068e", "usrP": "user-placement-rule/"}
2023-03-23T12:16:22.347Z	INFO	controllers.DRPlacementControl	Get Placement returned: Placement.cluster.open-cluster-management.io "user-placement-rule" not found	{"DRPC": "drpc-namespace/drpc-name", "rid": "60c37fb7-69cb-42fa-b57c-629c4bf4068e"}
2023-03-23T12:16:22.347Z	INFO	controllers.DRPlacementControl	Using placement &{{PlacementRule apps.open-cluster-management.io/v1} {user-placement-rule  drpc-namespace  413b45a9-2dc2-4cda-9ebd-327f06441355 355 1 2023-03-23 12:16:12 +0000 UTC   map[] map[drplacementcontrol.ramendr.openshift.io/drpc-name:drpc-name drplacementcontrol.ramendr.openshift.io/drpc-namespace:drpc-namespace] [] [drpc.ramendr.openshift.io/finalizer] [{controllers.test Update apps.open-cluster-management.io/v1 2023-03-23 12:16:12 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{".":{},"f:drplacementcontrol.ramendr.openshift.io/drpc-name":{},"f:drplacementcontrol.ramendr.openshift.io/drpc-namespace":{}},"f:finalizers":{".":{},"v:"drpc.ramendr.openshift.io/finalizer"":{}}},"f:spec":{".":{},"f:clusterSelector":{".":{},"f:matchExpressions":{}},"f:schedulerName":{}}} } {controllers.test Update apps.open-cluster-management.io/v1 2023-03-23 12:16:22 +0000 UTC FieldsV1 {"f:status":{".":{},"f:decisions":{}}} status}]} {ramen  {[] &LabelSelector{MatchLabels:map[string]string{},MatchExpressions:[]LabelSelectorRequirement{LabelSelectorRequirement{Key:key1,Operator:In,Values:[west1],},},}} []  []} {[{west1-cluster west1-cluster}]}}	{"DRPC": "drpc-namespace/drpc-name", "rid": "60c37fb7-69cb-42fa-b57c-629c4bf4068e"}
2023-03-23T12:16:22.347Z	INFO	controllers.DRPlacementControl	Preferred cluster is configured. Dynamic selection is disabled	{"DRPC": "drpc-namespace/drpc-name", "rid": "60c37fb7-69cb-42fa-b57c-629c4bf4068e", "PreferredCluster": "east1-cluster"}
2023-03-23T12:16:22.347Z	INFO	controllers.DRPlacementControl	VRG not found on "east1-cluster"	{"DRPC": "drpc-namespace/drpc-name", "rid": "60c37fb7-69cb-42fa-b57c-629c4bf4068e"}
2023-03-23T12:16:22.348Z	INFO	controllers.DRPlacementControl	VRG location	{"DRPC": "drpc-namespace/drpc-name", "rid": "60c37fb7-69cb-42fa-b57c-629c4bf4068e", "VRG on": "west1-cluster"}
2023-03-23T12:16:22.352Z	INFO	controllers.DRPlacementControl	Starting to process placement	{"DRPC": "drpc-namespace/drpc-name", "rid": "60c37fb7-69cb-42fa-b57c-629c4bf4068e"}
2023-03-23T12:16:22.352Z	INFO	controllers.DRPlacementControl	Process DRPC Placement	{"DRPC": "drpc-namespace/drpc-name", "rid": "60c37fb7-69cb-42fa-b57c-629c4bf4068e", "DRAction": "Failover"}
2023-03-23T12:16:22.352Z	INFO	controllers.DRPlacementControl	Entering RunFailover	{"DRPC": "drpc-namespace/drpc-name", "rid": "60c37fb7-69cb-42fa-b57c-629c4bf4068e", "state": ""}
2023-03-23T12:16:22.352Z	INFO	controllers.DRPlacementControl	Check placement if needs fixing: PrD { }, PlD &{west1-cluster PlacementRule decision}, VRGs 1	{"DRPC": "drpc-namespace/drpc-name", "rid": "60c37fb7-69cb-42fa-b57c-629c4bf4068e"}
2023-03-23T12:16:22.352Z	INFO	controllers.DRPlacementControl	Already "" to cluster west1-cluster	{"DRPC": "drpc-namespace/drpc-name", "rid": "60c37fb7-69cb-42fa-b57c-629c4bf4068e"}
2023-03-23T12:16:22.352Z	INFO	controllers.DRPlacementControl	Phase: Current ''. Next 'FailedOver'	{"DRPC": "drpc-namespace/drpc-name", "rid": "60c37fb7-69cb-42fa-b57c-629c4bf4068e"}
2023-03-23T12:16:22.352Z	INFO	controllers.DRPlacementControl	Checking if VRG is DataReady on cluster west1-cluster	{"DRPC": "drpc-namespace/drpc-name", "rid": "60c37fb7-69cb-42fa-b57c-629c4bf4068e"}
2023-03-23T12:16:22.352Z	INFO	controllers.DRPlacementControl	VRG status condition: &Condition{Type:DataReady,Status:True,ObservedGeneration:1,LastTransitionTime:2023-03-23 12:16:22.347805736 +0000 UTC m=+23.989080206,Reason:Replicating,Message:Testing VRG,}	{"DRPC": "drpc-namespace/drpc-name", "rid": "60c37fb7-69cb-42fa-b57c-629c4bf4068e"}
2023-03-23T12:16:22.352Z	INFO	controllers.DRPlacementControl	Checking if VRG is ClusterDataReady on cluster west1-cluster	{"DRPC": "drpc-namespace/drpc-name", "rid": "60c37fb7-69cb-42fa-b57c-629c4bf4068e"}
2023-03-23T12:16:22.352Z	INFO	controllers.DRPlacementControl	VRG status condition: &Condition{Type:ClusterDataReady,Status:True,ObservedGeneration:1,LastTransitionTime:2023-03-23 12:16:22.348043738 +0000 UTC m=+23.989318208,Reason:Restored,Message:Cluster Data Ready,}	{"DRPC": "drpc-namespace/drpc-name", "rid": "60c37fb7-69cb-42fa-b57c-629c4bf4068e"}
2023-03-23T12:16:22.352Z	INFO	controllers.DRPlacementControl	Progression: Current 'FailedOver'. Next 'Cleaning Up'	{"DRPC": "drpc-namespace/drpc-name", "rid": "60c37fb7-69cb-42fa-b57c-629c4bf4068e"}
2023-03-23T12:16:22.352Z	INFO	controllers.DRPlacementControl	Resetting RD VRG ownedby MW drpc-name-drpc-namespace-vrg-mw for cluster west1-cluster	{"DRPC": "drpc-namespace/drpc-name", "rid": "60c37fb7-69cb-42fa-b57c-629c4bf4068e"}
2023-03-23T12:16:22.352Z	INFO	controllers.DRPlacementControl	RDSpec for drpc-name has already been cleared on this cluster west1-cluster	{"DRPC": "drpc-namespace/drpc-name", "rid": "60c37fb7-69cb-42fa-b57c-629c4bf4068e"}
2023-03-23T12:16:22.352Z	INFO	controllers.DRPlacementControl	ensuring cleanup on secondaries	{"DRPC": "drpc-namespace/drpc-name", "rid": "60c37fb7-69cb-42fa-b57c-629c4bf4068e"}
2023-03-23T12:16:22.352Z	INFO	controllers.DRPlacementControl	Starting cleanup check	{"DRPC": "drpc-namespace/drpc-name", "rid": "60c37fb7-69cb-42fa-b57c-629c4bf4068e"}
2023-03-23T12:16:22.352Z	INFO	controllers.DRPlacementControl	PeerReady Condition &Condition{Type:PeerReady,Status:False,ObservedGeneration:2,LastTransitionTime:2023-03-23 12:16:22.352308166 +0000 UTC m=+23.993582636,Reason:Progressing,Message:Starting cleanup check,}	{"DRPC": "drpc-namespace/drpc-name", "rid": "60c37fb7-69cb-42fa-b57c-629c4bf4068e"}
2023-03-23T12:16:22.352Z	INFO	controllers.DRPlacementControl	Checking if there are PVCs for VolSync replication...	{"DRPC": "drpc-namespace/drpc-name", "rid": "60c37fb7-69cb-42fa-b57c-629c4bf4068e", "cluster": "west1-cluster"}
2023-03-23T12:16:22.352Z	INFO	controllers.DRPlacementControl	Ensuring MW for the VRG is deleted	{"DRPC": "drpc-namespace/drpc-name", "rid": "60c37fb7-69cb-42fa-b57c-629c4bf4068e", "cluster": "east1-cluster"}
2023-03-23T12:16:22.352Z	INFO	controllers.DRPlacementControl	MW has been deleted. Check the VRG	{"DRPC": "drpc-namespace/drpc-name", "rid": "60c37fb7-69cb-42fa-b57c-629c4bf4068e"}
2023-03-23T12:16:22.352Z	INFO	controllers.DRPlacementControl	Ensure VolSync replication has been setup for cluster west1-cluster	{"DRPC": "drpc-namespace/drpc-name", "rid": "60c37fb7-69cb-42fa-b57c-629c4bf4068e"}
2023-03-23T12:16:22.352Z	INFO	controllers.DRPlacementControl	Checking if there are PVCs for VolSync replication...	{"DRPC": "drpc-namespace/drpc-name", "rid": "60c37fb7-69cb-42fa-b57c-629c4bf4068e", "cluster": "west1-cluster"}
2023-03-23T12:16:22.352Z	INFO	controllers.DRPlacementControl	No PVCs found that require VolSync replication	{"DRPC": "drpc-namespace/drpc-name", "rid": "60c37fb7-69cb-42fa-b57c-629c4bf4068e"}
2023-03-23T12:16:22.352Z	INFO	controllers.DRPlacementControl	Progression: Current 'FailedOver'. Next 'Completed'	{"DRPC": "drpc-namespace/drpc-name", "rid": "60c37fb7-69cb-42fa-b57c-629c4bf4068e"}
2023-03-23T12:16:22.352Z	INFO	controllers.DRPlacementControl	Updating DRPC status	{"DRPC": "drpc-namespace/drpc-name", "rid": "60c37fb7-69cb-42fa-b57c-629c4bf4068e"}
2023-03-23T12:16:22.352Z	INFO	controllers.DRPlacementControl	Setting metric: (last_sync_timestamp_seconds)	{"DRPC": "drpc-namespace/drpc-name", "rid": "60c37fb7-69cb-42fa-b57c-629c4bf4068e"}
2023-03-23T12:16:22.358Z	INFO	controllers.DRPlacementControl	Updated DRPC Status {Phase:FailedOver ActionStartTime: ActionDuration:nil Progression:Completed PreferredDecision:{ClusterName: ClusterNamespace:} Conditions:[{Type:Available Status:True ObservedGeneration:2 LastTransitionTime:2023-03-23 12:16:22 +0000 UTC Reason:FailedOver Message:Completed} {Type:PeerReady Status:True ObservedGeneration:2 LastTransitionTime:2023-03-23 12:16:22 +0000 UTC Reason:Success Message:Cleaned}] ResourceConditions:{ResourceMeta:{Kind:VolumeReplicationGroup Name:drpc-name Namespace:drpc-namespace Generation:1 ProtectedPVCs:[fakePVC0 fakePVC1]} Conditions:[{Type:DataReady Status:True ObservedGeneration:1 LastTransitionTime:2023-03-23 12:16:22 +0000 UTC Reason:Replicating Message:Testing VRG}]} LastUpdateTime:2023-03-23 12:16:22 +0000 UTC LastGroupSyncTime:}	{"DRPC": "drpc-namespace/drpc-name", "rid": "60c37fb7-69cb-42fa-b57c-629c4bf4068e"}
2023-03-23T12:16:22.358Z	INFO	controllers.DRPlacementControl	Completed processing placement	{"DRPC": "drpc-namespace/drpc-name", "rid": "60c37fb7-69cb-42fa-b57c-629c4bf4068e", "requeue": false}
2023-03-23T12:16:22.358Z	INFO	controllers.DRPlacementControl	Finished processing	{"DRPC": "drpc-namespace/drpc-name", "rid": "60c37fb7-69cb-42fa-b57c-629c4bf4068e", "Requeue?": false}
2023-03-23T12:16:22.358Z	INFO	controllers.DRPlacementControl	Done reconciling	{"DRPC": "drpc-namespace/drpc-name", "rid": "60c37fb7-69cb-42fa-b57c-629c4bf4068e", "state": "FailedOver"}
2023-03-23T12:16:22.358Z	INFO	controllers.DRPlacementControl	Requeue time	{"DRPC": "drpc-namespace/drpc-name", "rid": "60c37fb7-69cb-42fa-b57c-629c4bf4068e", "duration": "10m0s"}
2023-03-23T12:16:22.358Z	INFO	controllers.DRPlacementControl	Exiting reconcile loop	{"DRPC": "drpc-namespace/drpc-name", "rid": "60c37fb7-69cb-42fa-b57c-629c4bf4068e"}
2023-03-23T12:16:22.358Z	INFO	controllers.DRPlacementControl	Entering reconcile loop	{"DRPC": "drpc-namespace/drpc-name", "rid": "71d2b053-0a6e-4c88-82dc-d7e195b9c26d"}
2023-03-23T12:16:22.360Z	INFO	controllers.DRPlacementControl	Getting user placement object	{"DRPC": "drpc-namespace/drpc-name", "rid": "71d2b053-0a6e-4c88-82dc-d7e195b9c26d", "placementRef": {"name":"user-placement-rule"}}
2023-03-23T12:16:22.360Z	INFO	controllers.DRPlacementControl	Trying user PlacementRule	{"DRPC": "drpc-namespace/drpc-name", "rid": "71d2b053-0a6e-4c88-82dc-d7e195b9c26d", "usrPR": "user-placement-rule/"}
2023-03-23T12:16:22.360Z	INFO	controllers.DRPlacementControl	User PlacementRule replica count is not set to 1, reconciliation will only schedule it to a single cluster	{"DRPC": "drpc-namespace/drpc-name", "rid": "71d2b053-0a6e-4c88-82dc-d7e195b9c26d"}
2023-03-23T12:16:22.360Z	INFO	controllers.DRPlacementControl	PlacementRule Status is: ({Decisions:[{ClusterName:west1-cluster ClusterNamespace:west1-cluster}]})	{"DRPC": "drpc-namespace/drpc-name", "rid": "71d2b053-0a6e-4c88-82dc-d7e195b9c26d"}
2023-03-23T12:16:22.360Z	INFO	controllers.DRPlacementControl	Trying user Placement	{"DRPC": "drpc-namespace/drpc-name", "rid": "71d2b053-0a6e-4c88-82dc-d7e195b9c26d", "usrP": "user-placement-rule/"}
2023-03-23T12:16:22.360Z	INFO	controllers.DRPlacementControl	Get Placement returned: Placement.cluster.open-cluster-management.io "user-placement-rule" not found	{"DRPC": "drpc-namespace/drpc-name", "rid": "71d2b053-0a6e-4c88-82dc-d7e195b9c26d"}
2023-03-23T12:16:22.360Z	INFO	controllers.DRPlacementControl	Using placement &{{PlacementRule apps.open-cluster-management.io/v1} {user-placement-rule  drpc-namespace  413b45a9-2dc2-4cda-9ebd-327f06441355 355 1 2023-03-23 12:16:12 +0000 UTC   map[] map[drplacementcontrol.ramendr.openshift.io/drpc-name:drpc-name drplacementcontrol.ramendr.openshift.io/drpc-namespace:drpc-namespace] [] [drpc.ramendr.openshift.io/finalizer] [{controllers.test Update apps.open-cluster-management.io/v1 2023-03-23 12:16:12 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{".":{},"f:drplacementcontrol.ramendr.openshift.io/drpc-name":{},"f:drplacementcontrol.ramendr.openshift.io/drpc-namespace":{}},"f:finalizers":{".":{},"v:"drpc.ramendr.openshift.io/finalizer"":{}}},"f:spec":{".":{},"f:clusterSelector":{".":{},"f:matchExpressions":{}},"f:schedulerName":{}}} } {controllers.test Update apps.open-cluster-management.io/v1 2023-03-23 12:16:22 +0000 UTC FieldsV1 {"f:status":{".":{},"f:decisions":{}}} status}]} {ramen  {[] &LabelSelector{MatchLabels:map[string]string{},MatchExpressions:[]LabelSelectorRequirement{LabelSelectorRequirement{Key:key1,Operator:In,Values:[west1],},},}} []  []} {[{west1-cluster west1-cluster}]}}	{"DRPC": "drpc-namespace/drpc-name", "rid": "71d2b053-0a6e-4c88-82dc-d7e195b9c26d"}
2023-03-23T12:16:22.360Z	INFO	controllers.DRPlacementControl	Preferred cluster is configured. Dynamic selection is disabled	{"DRPC": "drpc-namespace/drpc-name", "rid": "71d2b053-0a6e-4c88-82dc-d7e195b9c26d", "PreferredCluster": "east1-cluster"}
2023-03-23T12:16:22.361Z	INFO	controllers.DRPlacementControl	VRG not found on "east1-cluster"	{"DRPC": "drpc-namespace/drpc-name", "rid": "71d2b053-0a6e-4c88-82dc-d7e195b9c26d"}
2023-03-23T12:16:22.361Z	INFO	controllers.DRPlacementControl	VRG location	{"DRPC": "drpc-namespace/drpc-name", "rid": "71d2b053-0a6e-4c88-82dc-d7e195b9c26d", "VRG on": "west1-cluster"}
2023-03-23T12:16:22.363Z	INFO	controllers.DRPlacementControl	Starting to process placement	{"DRPC": "drpc-namespace/drpc-name", "rid": "71d2b053-0a6e-4c88-82dc-d7e195b9c26d"}
2023-03-23T12:16:22.363Z	INFO	controllers.DRPlacementControl	Process DRPC Placement	{"DRPC": "drpc-namespace/drpc-name", "rid": "71d2b053-0a6e-4c88-82dc-d7e195b9c26d", "DRAction": "Failover"}
2023-03-23T12:16:22.363Z	INFO	controllers.DRPlacementControl	Entering RunFailover	{"DRPC": "drpc-namespace/drpc-name", "rid": "71d2b053-0a6e-4c88-82dc-d7e195b9c26d", "state": "FailedOver"}
2023-03-23T12:16:22.363Z	INFO	controllers.DRPlacementControl	Check placement if needs fixing: PrD { }, PlD &{west1-cluster PlacementRule decision}, VRGs 1	{"DRPC": "drpc-namespace/drpc-name", "rid": "71d2b053-0a6e-4c88-82dc-d7e195b9c26d"}
2023-03-23T12:16:22.363Z	INFO	controllers.DRPlacementControl	Already "FailedOver" to cluster west1-cluster	{"DRPC": "drpc-namespace/drpc-name", "rid": "71d2b053-0a6e-4c88-82dc-d7e195b9c26d"}
2023-03-23T12:16:22.363Z	INFO	controllers.DRPlacementControl	Checking if VRG is DataReady on cluster west1-cluster	{"DRPC": "drpc-namespace/drpc-name", "rid": "71d2b053-0a6e-4c88-82dc-d7e195b9c26d"}
2023-03-23T12:16:22.363Z	INFO	controllers.DRPlacementControl	VRG status condition: &Condition{Type:DataReady,Status:True,ObservedGeneration:1,LastTransitionTime:2023-03-23 12:16:22.361012825 +0000 UTC m=+24.002287295,Reason:Replicating,Message:Testing VRG,}	{"DRPC": "drpc-namespace/drpc-name", "rid": "71d2b053-0a6e-4c88-82dc-d7e195b9c26d"}
2023-03-23T12:16:22.363Z	INFO	controllers.DRPlacementControl	Checking if VRG is ClusterDataReady on cluster west1-cluster	{"DRPC": "drpc-namespace/drpc-name", "rid": "71d2b053-0a6e-4c88-82dc-d7e195b9c26d"}
2023-03-23T12:16:22.363Z	INFO	controllers.DRPlacementControl	VRG status condition: &Condition{Type:ClusterDataReady,Status:True,ObservedGeneration:1,LastTransitionTime:2023-03-23 12:16:22.361182026 +0000 UTC m=+24.002456496,Reason:Restored,Message:Cluster Data Ready,}	{"DRPC": "drpc-namespace/drpc-name", "rid": "71d2b053-0a6e-4c88-82dc-d7e195b9c26d"}
2023-03-23T12:16:22.363Z	INFO	controllers.DRPlacementControl	Progression: Current 'FailedOver'. Next 'Cleaning Up'	{"DRPC": "drpc-namespace/drpc-name", "rid": "71d2b053-0a6e-4c88-82dc-d7e195b9c26d"}
2023-03-23T12:16:22.363Z	INFO	controllers.DRPlacementControl	Resetting RD VRG ownedby MW drpc-name-drpc-namespace-vrg-mw for cluster west1-cluster	{"DRPC": "drpc-namespace/drpc-name", "rid": "71d2b053-0a6e-4c88-82dc-d7e195b9c26d"}
2023-03-23T12:16:22.363Z	INFO	controllers.DRPlacementControl	RDSpec for drpc-name has already been cleared on this cluster west1-cluster	{"DRPC": "drpc-namespace/drpc-name", "rid": "71d2b053-0a6e-4c88-82dc-d7e195b9c26d"}
2023-03-23T12:16:22.363Z	INFO	controllers.DRPlacementControl	ensuring cleanup on secondaries	{"DRPC": "drpc-namespace/drpc-name", "rid": "71d2b053-0a6e-4c88-82dc-d7e195b9c26d"}
2023-03-23T12:16:22.363Z	INFO	controllers.DRPlacementControl	Condition values tallied, cleanup is considered complete	{"DRPC": "drpc-namespace/drpc-name", "rid": "71d2b053-0a6e-4c88-82dc-d7e195b9c26d"}
2023-03-23T12:16:22.363Z	INFO	controllers.DRPlacementControl	Ensure VolSync replication has been setup for cluster west1-cluster	{"DRPC": "drpc-namespace/drpc-name", "rid": "71d2b053-0a6e-4c88-82dc-d7e195b9c26d"}
2023-03-23T12:16:22.363Z	INFO	controllers.DRPlacementControl	Checking if there are PVCs for VolSync replication...	{"DRPC": "drpc-namespace/drpc-name", "rid": "71d2b053-0a6e-4c88-82dc-d7e195b9c26d", "cluster": "west1-cluster"}
2023-03-23T12:16:22.363Z	INFO	controllers.DRPlacementControl	No PVCs found that require VolSync replication	{"DRPC": "drpc-namespace/drpc-name", "rid": "71d2b053-0a6e-4c88-82dc-d7e195b9c26d"}
2023-03-23T12:16:22.363Z	INFO	controllers.DRPlacementControl	Progression: Current 'FailedOver'. Next 'Completed'	{"DRPC": "drpc-namespace/drpc-name", "rid": "71d2b053-0a6e-4c88-82dc-d7e195b9c26d"}
2023-03-23T12:16:22.363Z	INFO	controllers.DRPlacementControl	Updating DRPC status	{"DRPC": "drpc-namespace/drpc-name", "rid": "71d2b053-0a6e-4c88-82dc-d7e195b9c26d"}
2023-03-23T12:16:22.363Z	INFO	controllers.DRPlacementControl	Setting metric: (last_sync_timestamp_seconds)	{"DRPC": "drpc-namespace/drpc-name", "rid": "71d2b053-0a6e-4c88-82dc-d7e195b9c26d"}
2023-03-23T12:16:22.368Z	INFO	controllers.DRPlacementControl	Updated DRPC Status {Phase:FailedOver ActionStartTime: ActionDuration:nil Progression:Completed PreferredDecision:{ClusterName: ClusterNamespace:} Conditions:[{Type:Available Status:True ObservedGeneration:2 LastTransitionTime:2023-03-23 12:16:22 +0000 UTC Reason:FailedOver Message:Completed} {Type:PeerReady Status:True ObservedGeneration:2 LastTransitionTime:2023-03-23 12:16:22 +0000 UTC Reason:Success Message:Cleaned}] ResourceConditions:{ResourceMeta:{Kind:VolumeReplicationGroup Name:drpc-name Namespace:drpc-namespace Generation:1 ProtectedPVCs:[fakePVC0 fakePVC1]} Conditions:[{Type:DataReady Status:True ObservedGeneration:1 LastTransitionTime:2023-03-23 12:16:22 +0000 UTC Reason:Replicating Message:Testing VRG}]} LastUpdateTime:2023-03-23 12:16:22 +0000 UTC LastGroupSyncTime:}	{"DRPC": "drpc-namespace/drpc-name", "rid": "71d2b053-0a6e-4c88-82dc-d7e195b9c26d"}
2023-03-23T12:16:22.368Z	INFO	controllers.DRPlacementControl	Completed processing placement	{"DRPC": "drpc-namespace/drpc-name", "rid": "71d2b053-0a6e-4c88-82dc-d7e195b9c26d", "requeue": false}
2023-03-23T12:16:22.368Z	INFO	controllers.DRPlacementControl	Finished processing	{"DRPC": "drpc-namespace/drpc-name", "rid": "71d2b053-0a6e-4c88-82dc-d7e195b9c26d", "Requeue?": false}
2023-03-23T12:16:22.368Z	INFO	controllers.DRPlacementControl	Done reconciling	{"DRPC": "drpc-namespace/drpc-name", "rid": "71d2b053-0a6e-4c88-82dc-d7e195b9c26d", "state": "FailedOver"}
2023-03-23T12:16:22.368Z	INFO	controllers.DRPlacementControl	Requeue time	{"DRPC": "drpc-namespace/drpc-name", "rid": "71d2b053-0a6e-4c88-82dc-d7e195b9c26d", "duration": "9m59.631034722s"}
2023-03-23T12:16:22.368Z	INFO	controllers.DRPlacementControl	Exiting reconcile loop	{"DRPC": "drpc-namespace/drpc-name", "rid": "71d2b053-0a6e-4c88-82dc-d7e195b9c26d"}

• Failure [10.040 seconds]
DRPlacementControl Reconciler
/home/runner/work/ramen/ramen/controllers/drplacementcontrol_controller_test.go:1646
DRPlacementControl Reconciler Async DR using PlacementRule (Subscription)
/home/runner/work/ramen/ramen/controllers/drplacementcontrol_controller_test.go:1650
when DRAction is Failover during hub recovery
/home/runner/work/ramen/ramen/controllers/drplacementcontrol_controller_test.go:1680
Should reconstructs the DRPC state and points to Secondary (West1ManagedCluster) [It]
/home/runner/work/ramen/ramen/controllers/drplacementcontrol_controller_test.go:1681
  Timed out after 10.000s.
  failed waiting for an updated DRPC. State FailedOver
  Expected
      <bool>: false
  to be true

  /home/runner/work/ramen/ramen/controllers/drplacementcontrol_controller_test.go:1161

repo: RamenDR/ramen


text:
Etiquetas

Boa noite. Ao gerar etiquetas, teria como colocar vários códigos dos produtos para gerar etiquetas só invés de colocar um intervalos.
Se puderem me ajudar ou dar uma dica de como fazer.
Obrigado
** Sua solicitação de feature está relacionada a um problema? Por favor descreva.**
Uma descrição clara e concisa de qual é o problema. Ex. Fico sempre frustrado quando [...]
** Descreva a solução que você deseja **
Uma descrição clara e concisa do que você deseja que aconteça.
** Descreva as alternativas que você considerou **
Uma descrição clara e concisa de qualquer solução ou recurso alternativo que você tenha considerado.
** Contexto adicional **
Adicione qualquer outro contexto ou captura de tela sobre a solicitação de recurso aqui.

Olá...
As minhas O.S. eu personalizei de forma que gerem no fim delas 03 números para etiquetas.
Daí, ao imprimir a via do cliente, destaco o canhoto inferior e colo no(s) equipamento(s) e/ou peça(s)

No arquivo "imprimirOs.php" é só acrescentar na posição deseja o código abaixo:

                                                                   <?php echo $result->idOs?> - <?php echo $result->nomeCliente?>                                 	                                              <?php echo $result->idOs?> - <?php echo $result->nomeCliente?>                                 	                                              <?php echo $result->idOs?> - <?php echo $result->nomeCliente?>


text:
Update config.php

Corrige a hora da auditoria.
Corrige a hora de fechamento de caixa do dia que não lista a receita/despesas do dia à partir das 22:00.

Já adicionado em config através da PR #2108


text:
Tiny Tiny RSS account support

Are there any plans to add support for Tiny Tiny RSS account in a similar fashion as Feedbin.
https://tt-rss.org/wiki/ApiReference

We plan to support all of the various services.

Is this a duplicate of #388, or am I misinterpreting?

Seems like it. I guess I didn't search good enough.

All good—was searching through the sync issues too to see the status and just happened to notice the similarity, but wasn’t sure if you were requesting the same thing. Cheers!

Tiny-Tiny RSS is now usable with NetNewsWire. I recently published a plugin for Tiny Tiny RSS that will allow NetNewsWire to interface with it using the FreshRSS API here: https://github.com/eric-pierce/freshapi
I've got to say NNW is a really nice experience, better with TT-RSS as the server. If you give it a shot please provide any feedback or issues you find!

authors: brentsimmons eric-pierce parkr woble

repo: Ranchero-Software/NetNewsWire


text:
Which version of the kwikset lock are you using?

Hello,
I love your tutorial.  I almost have it working, lol. I am having a problem with the serial port staying connected due to an I/O error. The unlock clears just fine and unlocks the door.  when I issue the following lock command, I get the I/O error.
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "lock_api.py", line 61, in unlock
    ser.write(kwikset.generate_unlock_packet())
  File "/usr/lib/python2.7/site-packages/serial/serialposix.py", line 383, in write
    n = os.write(self.fd, d)
OSError: [Errno 5] Input/output error

But I wanted to ensure I had the correct pinout as my kwikset lock looks a little bit different than yours.
Other information.  I ported this to Arduino Yun instead of the Edison and I am using the Kwikset 909 lock which is Home Connect ready.
Any thoughts you might have would be great.  I would like to start by making sure the lock's pinouts are the same.
Kind Regards,
Jock

Actually, never mind.  I solved the problem with a minor workaround.  It ended up being the code 😄

repo: RandomWireTechnologies/KeyforallEdison


text:
v0.16 v0.17 Cleanup - Active SmartNode Updates

Reviewing PRs #88 and #105, I noted the following files that need review/cleanup:
The following files need updating to restore pr #58

src/evo/deterministicmns.cpp
ToJson - removed fields - review
removed IsMNValid logic (and in .h)
active at height logic removed
src/rpc/rpcevo - active at height removed
src/wallet/wallet.cpp - active at height removed

Reviewing PRs #88 and #105, I noted the following files that need review/cleanup:
The following files need updating to restore pr #58

src/evo/deterministicmns.cpp
ToJson - removed fields - review
removed IsMNValid logic (and in .h)
active at height logic removed
src/rpc/rpcevo - active at height removed
src/wallet/wallet.cpp - active at height removed

That issue had been resolved so we can close it I think.
Decision is yours

I think we're about half way there.  The optional height parameter was removed that fixed a bug with the active check/collateral in the past.  I need to review and re-apply some of those changes.

I think we're about half way there. The optional height parameter was removed that fixed a bug with the active check/collateral in the past. I need to review and re-apply some of those changes.

Fair enough for me then.
But I did re-add code which was removed by mistake during rebase-merge.
Will wait for the updates then

authors: CodeIsTheKey malbit


text:
Upgrade to Swift 5.1

An upgrade to latest Swift 5.1 would be great

Ok, ni problem I am on holyday right now but will update once I am back.

Upgraded to Swift 5 as of version 1.3

@RastislavMirek can you please push the latest release(s) to trunk? Pod is still on v1.2.1 on CocoaPods.

authors: RastislavMirek timbms weakfl

repo: RastislavMirek/FlexColorPicker


text:
Docs missing refernce for set_cookies and get_cookeis

I have been trying to set_cookies  but i can't any reference for the same in the docs. I have been trying with
"""
cookies_value='{"domain":"tester.com", "session":"zxvvdedadadda124"}
set_cookies $cookies_value
"""
Is this the correct way of doing it?

@jakre1234
Thanks your issue!
Sorry I forgot to create documentation.
I add new cookies functions! please see this PR!
And I create the document here.
https://shellnium-site.vercel.app/doc#cookies
Thanks!

repo: Rasukarusan/shellnium


text:
show 404 Error Page

Hi, when I run the app, it shows 404 error page.

I forgot to map the root context to any page.

authors: RawSanj donsunsoft

repo: RawSanj/spring-tiles-sample-app


text:
WIP: Update docs

Docs are old.
Seems that vtree and vnode repos have been moved?

And I think we can rewrite bin/copy-markdown.js without git but just download files from https://raw.github.com.

Thanks

authors: Raynos kuraga

repo: Raynos/mercury


text:
Server crash after player joining server

When i join my server, server start crash and plugin throw some error about "PlayerJoinEvent"
Logs: https://mclo.gs/SUrxqLr#L532
Folia 1.21.1
ProAntiTab v1.9.0

Thank you very much for letting me know!
It seems that my Plugin fails to work with Folia version you're using, which is really weird.
Could you perhaps send me the built Folia server-jar you're using? ^^

Sorry for late. I take folia from https://github.com/neokoni/folia_build_action/releases/tag/2024-12-04
and use 1.21.1 version

Ok that's weird. I compiled Folia myself and it was working on my side. The 1.21.4 and the 1.21.1.
Only this jar you sent me caused the issue.
I'll let you know if I can find more about it.

Ok. I create a test jar for ya. Please lemme know if it works! ^^
https://github.com/RayzsYT/ProAntiTab/releases/tag/v1.9.1-Experimental

authors: Dungjava RayzsYT

repo: RayzsYT/ProAntiTab


text:
Fix infinite loop in iteration of memory mapping lines

This fixes #242.
Iteration of the file's lines was broken in e1289162.

Strange how this could have worked for me then... 🤔


text:
Xcode 8b3 fixes

This PR extracts the leftovers from #132 & #133 that were originally destined to the swift-3 branch.

Adds required explicit let on conditional binding cascade as per SE-0099.
Adds conditional_binding_cascade to swiftlint's disabled_rules (at least until it gets removed from swiftlint altogether).

Thanks @agentk for the heads up on master being Swift 3 compatible!

[Current coverage][cc-pull] is 100%

Merging [#135][cc-pull] into [master][cc-base-branch] will not change coverage

@@           master   #135   diff @@
====================================
  Files           6      6
  Lines         169    169
  Methods         0      0
  Messages        0      0
  Branches        0      0
====================================
  Hits          169    169
  Misses          0      0
  Partials        0      0

Powered by Codecov. Last updated by [5050789...9f53e39][cc-compare]
[cc-base-branch]: https://codecov.io/gh/ReSwift/ReSwift/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/ReSwift/ReSwift/compare/5050789a1cdd194af53287af7f8718dcf82c112d...9f53e39a4ebb7a09217a1bc4030cff71ee7a279f?src=pr
[cc-pull]: https://codecov.io/gh/ReSwift/ReSwift/pull/135?src=pr

@cuva Hey Hugo, this is ready to be merged now. Could you please update it by rebasing off master to enable the merge. Cheers Karl.

Awesome - here you go @agentk !

Thank you! 🎉 We've decided to invite all contributors as collaborators to the GitHub Org!
Feel free to ignore if you're not interested!

authors: agentk codecov-io cuva

repo: ReSwift/ReSwift


text:
Add maxTimeMS behavior support for operations

As far as I know this functionality is not supported by ReactiveMongo driver.
Are you going to implement it?

Thanks a lot!

repo: ReactiveMongo/ReactiveMongo


text:
Rename switchLatest to switchMap

It's really switchMap. (same as flatMapLatest), but switchMap is the name we landed on from bikeshedding

Looks like this should be closed

Yes. Thank you, @pselle!

authors: blesh pselle

repo: ReactiveX/RxJS


text:
Add theme color for windows desktop app

hello，respect for every engineers.
can we change desktop app theme color to pink...it looks unharmonious

@pertrai1
theme_color in ngrx looks right

and I try to set theme_color in my own pwa,it is useful.

chrome70.0.3538.102
window 10

It's just a <meta> tag. Support doesn't matter because unsupported <meta name=x> values are ignored IIRC.

@def14nt that is correct. But I wonder why the need to file an issue for something that has very little support. And, because the issue was filed, I asked him to take it on. Anyone who sees this issue, it is open to tackle and do a PR.

@pertrai1 It's more of a niggle. It isn't important, but when you have extra time (when you're not working on smth important) you could file an issue I guess.
@vickmeng Thanks for filing the issue, but if you know how to fix this annoyance then you could have easily filed a pull request.

I'd like to provide a PR. I've noticed that a color is already defined because the default color in Chrome for Windows is gray, not the current blue. So it just need to be changed (instead of added).
But before I do that I have one question: I've noticed that the navigation header uses two different shades depending on which page is active. The homepage uses #d81b60 while the pages "Overview", "Reference" etc. use #c2185b which is slightly darker. (Is there a reason for that?)
I'd use the darker version if that's fine for everyone. I think a darker title bar over a lighter page header looks better than vice versa. On the sub pages the colors would match, which is also fine. Alternatively, I could use a third shade that's darker than the two other colors. What do you think?

This seems to be fixed:

repo: ReactiveX/rxjs


text:
iif subscriptions

Describe the bug
The documentation says, that only trueResult of the given observables will be subscribed, but both of the falseResult and trueResult will be subsrcibed to, and only returns the trueResult observable's value.
Expected behavior
Only subsrcibe to the trueResult observable.
Reproduction code
iif(() => false,
 firstObs(),
 secondObs()
)

function firstObs(): Observable<string> {
 console.log("Why?"); // <--- this got logged
 return of("one way");
}

function secondObs(): Observable<string> {
 console.log("Why not?"); // <--- this got logged
 return of("other way");
}

Reproduction URL
No response
Version
7.8.1
Environment
No response
Additional context
No response

Hi @borosbela,
If you subscribe to your iif Observable, you'll see that it only logs other way. one way is not logged and will not be logged as long as the function passed as the first parameter to iif returns falsy value. Please visit this link for demo.
The reason why Why? gets logged is because you're actually calling firstObs function when preparing the second parameter for iif which calls console.log("Why?") before returning of("one way"). This has nothing to do with RxJS, it's just how JavaScript works.
If you need to postpone execution of firstObs, you can use this:
import { defer, iif } from 'rxjs';

iif(() => false,
 defer(firstObs),
 defer(secondObs)
)

I'm gonna close this issue as there's no bug here.

authors: borosbela jakovljevic-mladen


text:
Chore: Fix typo on deprecation comments of merge

Description:
Fix typo on usage examples on comments.
A scheduled function called with scheduler.
Related issue (if exists):

Thank you, @kidkkr!

authors: benlesh kidkkr


text:
refactor: align tap sigs with subscribe

Description:
Does what it says in the title.
Related issue (if exists): Nope

Thanks (for everything) @cartant!

authors: benlesh cartant


text:
Refactor: Show loading state when tabs are clicked initially

Problem Statement

When a task tab is clicked on initially, No tasks found message is displayed when the tasks are loading
The message should not appear when the tasks are being fetched

The above issue is resolved in the following PR: https://github.com/Real-Dev-Squad/website-status/pull/755 where isFetching flag is used to show the loading indicator too.

repo: Real-Dev-Squad/website-status


text:
Why is minsdk 29? Couldn't it be lower?

Hi
Thanks for nice library, I was thinking about using it, but then minsdk version is set to 29.
And I'm not sure which part forces it to be so high? I've checked it out and compile with minsdk 23 and it compiles and jvm tests pass. Could you please reduce version requirement? since otherwise projects including it won't compile with error:
Execution failed for task ':androidApp:processDebugMainManifest'.
> Manifest merger failed : uses-sdk:minSdkVersion 21 cannot be smaller than version 29 declared in library [com.ashampoo:kim-android:0.1.1]

Hi,
thank you for testing that. Yes, We can lower the min SDK.
Ashampoo Photos needs API 29 and so I didn’t test something lower.

@shtolik I just pushed v0.1.3 to Maven Central and it should become available in the next couple of hours. Please let me know how it works for you.

@shtolik It is live now on Maven Central.

23 is good enough for me, thanks!

authors: StefanOltmann shtolik

repo: RealAshampoo/kim


text:
[Feature Suggestion] Chart System Swapping

Perhaps you could add support for charts too, since charts made in 1.0 use a different system and aren't compatible with previous releases.

I might add this idea but it might just take a while.

authors: Judipie Realmzer

repo: Realmzer/PsychSwitcher


text:
INFO: NPM Access

Hi ✋
This issue just to inform you that we have change access on realytics org on NPM.
@piotr-oles you now have read/write access on fork-ts-checker-webpack-plugin.
I think current token is still working but can you please generate your own token and use it instead of the current token.

Thank you for the update, I've changed this token - hope it will work :)

authors: etienne-dldc piotr-oles


text:
Feature: ResultCard component

This PR creates a new ResultCard component as well as more generic composable Card components. Closes #22.
IMPORTANT: There are edits to the homepage that should not be merged. These are intended to make it quick to review these components locally.
Component API:
<ResultCard
  // assumes these come from a list somewhere, most likely
  businessCategory="foodAndBeverage"
  businessName="Dad's Donuts"
  businessDescription="Blah blah blaaaah"
  businessLocation="Atlanta, GA"
  businessUrl="https://dobusiness.com"
  donationUrl="https://donatemoney.com"
  // overrides the default fallback image
  imageSrc="https://imagesrc.jpg"
  imageAlt="cool image you got there"
/>

Screenshots / video of changes

Steps to test
Run locally and check out the homepage.

OH and BTW, I added eslint dependencies because...well, there was no linting and I was making lots of mistakes. I can put this in another PR if it's too cluttery here, or if someone else is handling this elsewhere. Just let me know.

@chancestrickland this is looking solid - Is there any chance we can incorporate the work @kkemple did here https://github.com/Rebuild-Black-Business/RBB-Website/pull/35 - Just want to make sure we get proper schema markup baked into the ResultCard component for businesses.
Also very much appreciate you adding that linting. Need to have that in sooner rather than later for suuure.

@chancestrickland some linting was merged to master today, make sure to merge master in!

@magnificode I incorporated some of @kkemple's patterns, though it seems like we still need to flesh out the categories a bit. Left some todos in place but let me know those are going to be handled. I imagine we'll pull something from Airtable in whatever context these components are used rather than the component itself, so we can probably revisit this after merging.
@racedale I updated and merged with master.

@magnificode I incorporated some of @kkemple's patterns, though it seems like we still need to flesh out the categories a bit. Left some todos in place but let me know those are going to be handled. I imagine we'll pull something from Airtable in whatever context these components are used rather than the component itself, so we can probably revisit this after merging.
@racedale I updated and merged with master.

Yeah no worries at all, appreciate you keeping things flexible there and adding to-dos. This will continue to be a bit fluid as designs start rolling in. Very much appreciate the work here @chancestrickland !

@chancestrickland - feel free to remove the examples on the home page for now! If you wanted to turn the snippet you have in your original PR message into commented documentation in the Component file itself that would be awesome! Just to get a little usage example in the file itself.
Ping me when you've got that handled and I'll merge this in. Thank you again for the great work!

@magnificode Removed the homepage stuff, added that snippet in a JSDoc block. Holler if you need anything else to 🚢

authors: chancestrickland magnificode racedale

repo: Rebuild-Black-Business/RBB-Website


text:
Create hollowdiamond.java

A hollow diamond in java based on User choice

I accidently committed two codes in one pull request

repo: ReciHub/FunnyAlgorithms


text:
Please invite me to the Recode-Hive GitHub Community Organization

Name
Khaja
Discord Username (if applicable)
No response
Additional Context
No response

Invitation sent to join the GitHub Organisation. Welcome to the community 🎉
Don't forget after accepting to make it public so it appears on your GitHub profile for everyone else to see. You can do this by finding your name in the GitHub organisation list and change the dropdown to public https://github.com/orgs/Recode-Hive/people

repo: Recode-Hive/Support


text:
Set enabled to true by default

https://bugzilla.redhat.com/show_bug.cgi?id=1814021

Ivanchuk backport details:
$ git log -1
commit 7b6dc9065ed17b8f78df130ec443abb13cee07e5
Author: Milan Zázrivec <mzazrivec@redhat.com>
Date:   Mon Mar 16 20:04:02 2020 +0100

    Merge pull request #42 from mturley/enable-by-default

    Set enabled to true by default

    (cherry picked from commit b580ccf8a061276089aa91862d724667f7f5efbb)

    https://bugzilla.redhat.com/show_bug.cgi?id=1814021

Jansa backport details:
$ git log -1
Author: Milan Zázrivec <mzazrivec@redhat.com>
Date:   Mon Mar 16 20:04:02 2020 +0100

    Merge pull request #42 from mturley/enable-by-default

    Set enabled to true by default

    (cherry picked from commit b580ccf8a061276089aa91862d724667f7f5efbb)

    https://bugzilla.redhat.com/show_bug.cgi?id=1814021

authors: mturley simaishi


text:
RHINENG-7061: add intersystems field to system_profile

RHINENG-7061
Inventory-schema PR at https://github.com/RedHatInsights/inventory-schemas/pull/122

The local test looks good with:
--------------
Rules Executed
--------------
[META] src.puptoo.process.profile.system_profile
------------------------------------------------

    iris                   : {'iris_running_instances': [{'instance_name': 'IRIS',
                                                          'product': 'IRIS',
                                                          'version': '2023.1'},
                                                         {'instance_name': 'IRIS2',
                                                          'product': 'IRIS',
                                                          'version': '2023.1'}],
                              'iris_system': True}

Get the confirmation of the field name changes in Jira :

Use "intersystems" instead of "iris" as field name.

Updated the code accordingly: (Amended the commit message to include the "intersystems" word.)

The local test looks good with:
    intersystems           : {'is_intersystems': True,
                              'running_instances': [{'instance_name': 'IRIS',
                                                     'product': 'IRIS',
                                                     'version': '2023.1'},
                                                    {'instance_name': 'IRIS2',
                                                     'product': 'IRIS',
                                                     'version': '2023.1'}]}

inventory-schema local test also passed, against the latest code in https://github.com/RedHatInsights/inventory-schemas/pull/122 .

Updated the code accordingly after the field name changes confirmation in Jira .
And local test looks fine: details at https://github.com/RedHatInsights/insights-puptoo/pull/316#issuecomment-1907878622
Hi @r14chandra , could you kindly help review the changes?

Hi @xiangce , could you also have a look at this update?

repo: RedHatInsights/insights-puptoo


text:
./storage_test.go:571:18: ioutilDeprecated: ioutil.ReadFile is deprecated

./storage_test.go:571:18: ioutilDeprecated: ioutil.ReadFile is deprecated, use os.ReadFile instead

Fixed already


text:
Setup Golint GH Action for this repository

Setup Golint GH Action for this repository

Setup there https://github.com/RedHatInsights/insights-results-aggregator-exporter/blob/master/.github/workflows/golangci-lint.yml


text:
Description about DVO on updated overall architecture diagram

Description
Description about DVO on updated overall architecture diagram
Type of change

Documentation update

Testing steps
N/A (just click and test the diagram after merge)
Checklist

[ ] make before_commit passes
[ ] updated documentation wherever necessary
[ ] added or modified tests if necessary
[ ] updated schemas and validators in insights-data-schemas in case of input/output change

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (ed5e573) 69.59% compared to head (bbeef1a) 69.59%.

:exclamation: Current head bbeef1a differs from pull request most recent head 5107776. Consider uploading reports for the commit 5107776 to get more accurate results

Additional details and impacted files
@@           Coverage Diff           @@
##           master    #1172   +/-   ##
=======================================
  Coverage   69.59%   69.59%
=======================================
  Files          25       25
  Lines        3684     3684
=======================================
  Hits         2564     2564
  Misses        858      858
  Partials      262      262

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

authors: codecov-commenter tisnik


text:
rename to PROMETHEUS_PUSHGATEWAY to avoid re-mapping in app-interface config

Secure Coding Practices Checklist GitHub Link

https://github.com/RedHatInsights/secure-coding-checklist

Secure Coding Checklist

[x] Input Validation
[x] Output Encoding
[x] Authentication and Password Management
[x] Session Management
[x] Access Control
[x] Cryptographic Practices
[x] Error Handling and Logging
[x] Data Protection
[x] Communication Security
[x] System Configuration
[x] Database Security
[x] File Management
[x] Memory Management
[x] General Coding Practices

Codecov Report

Merging #88 (46be274) into master (810bce7) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master      #88   +/-   ##
=======================================
  Coverage   40.43%   40.43%
=======================================
  Files          13       13
  Lines         643      643
=======================================
  Hits          260      260
  Misses        364      364
  Partials       19       19

Flag
Coverage Δ

unittests
40.43% <100.00%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

base/utils/config.go
69.69% <100.00%> (ø)

Continue to review full report at Codecov.

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

authors: codecov-commenter jdobes


text:
Remove wget - 1

[Auto generated]
Number: [#1]

qe-tools-base-image(BtA25)[PR 1]: Closing issue for PR: Remove wget.
PR was closed.

repo: RedHatQE/qe-tools-base-image


text:
Labeled record types

A sort for labels, and rules and tactics for record types.

Good, I definitely want to have this too.

@jonsterling What is the parameter sort LBL used for? I was thinking maybe labels should have the sort ATOM or something.

@favonia That was for when I had started to implement records 😄 (Before RedPRL switched to CHiTT)

feel free to use whatever names you think are best though!

@jonsterling It is for crazy polymorphism we could probably have in the future... when atoms can be reasoned with in some fancy way. Maybe we should stick with LBL for the moment.

I realized in an untyped setting this can be done in millions of different ways. Maybe a value in a record is just a list? Or we have a special record constructor with possibly duplicate labels as parameters (and only the expression corresponding to the first occurrence of the label will be used)? @jonsterling I wonder which one is your favorite?

This is a great question; in Nuprl, records are "functions" from Atom to whatever... In practice, the proof obligations that arise for well-typedness are fairly difficult and hard to automate.
One option which is maybe a bit more tractable is to have records formed like with nil and cons[lbl](term; record) as constructors, and as you suggest, have the projections target the first occurrence of lbl. Then in the type system, records ought to be regarded extensionally and negatively.
I think it's also pretty important for automation / type "checking" that the labels be static, rather than internalized through a type of atoms, like in Nuprl.

My other idea is to have a "tuple" operator which takes a list of parameters, and the arity is the length of the parameter list. Do you prefer the nested version more than the flat version? (And I guess we don't want fancy record polymorphism (yet).)

@favonia Your tuple idea sounds very nice too, and it might be easier to type"check"; we can still make it extensible with another operator, so that's fine :)

@jonsterling Now I am thinking whether a pair should be a tuple with labels "1" and "2".

authors: favonia jonsterling

repo: RedPRL/sml-redprl